Upgrade Cherryba-m1 to latest u-boot, move patch to new folder

[igorpecovnik]

Description

Adjusting for Noble host compatibility.

@IsMrX

How Has This Been Tested?

• Build test

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

[coderabbitai]

Caution

Review failed

The pull request is closed.

"""

Walkthrough

The configuration file for the CherryBa M1 board has been updated by modifying two variables: BOOTBRANCH_BOARD and BOOTPATCHDIR. Both variables previously referenced version "v2024.01" and have now been updated to "v2025.04". No additional changes or logic modifications were introduced in this update, and the changes are limited strictly to updating these version references within the configuration file.

Possibly related PRs

• nanopi-r3s: bump uboot to v2025.04 #8070: Updates the bootloader version variables BOOTBRANCH and BOOTPATCHDIR to "v2025.04" in another board-specific configuration file.
• station-p2: bump u-boot to 2025.04 #8081: Updates the BOOTBRANCH_BOARD and BOOTPATCHDIR variables to "tag:v2025.04" in a different board configuration file.
• rock-3a: bump mainline uboot to v2025.04 #8072: Updates the boot branch and patch directory version strings to "v2025.04" in another board configuration file.

Suggested labels

ready to merge

Suggested reviewers

• igorpecovnik
• joekhoobyar
• rpardini
• amazingfate
  """

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7a46d09 and 62613fc.

⛔ Files ignored due to path filters (1)

• patch/u-boot/v2025.04/board_cherryba-m1/add_and_fix_cherryba-m1_uboot.patch is excluded by !patch/**

📒 Files selected for processing (1)

• config/boards/cherryba-m1.csc (1 hunks)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.