-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
coolpi-genbook: Add Support for vendor branch #8275
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
WalkthroughThe configuration for the CoolPi GenBook board was updated to change the Possibly related PRs
Suggested labels
Suggested reviewers
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Um...why mainline uboot with vendor kernel? Doesn't edge use mainline uboot too? This looks confusing. |
The main reason is that Coolpi's vendor u-boot has do heavily modifications. They even imported the cross-compiler toolchain into the u-boot repository. Moreover, due to some modifications to the memory layout in there vendor u-boot, it is impossible to start armbian. Based on my current tests, using the mainline to start both the vendor and the mainline branch works perfectly. Therefore, I will simply use a single u-boot to keep things simple. |
OK, that is understandable. Why two configs / functions with different u-boot tag? Won't one function config cover both? Seems like a lot of doubled code in the board config. |
Yes, they should use the same u-boot tag. It would be even better if the one function/hook could be used to achieve this. I just don't know how to write it yet. Will try.... |
Try from |
Signed-off-by: Andy Yan <[email protected]>
Yeah,it works, thanks。 I updated a new version now。 |
Description
The dts for vendor kernel has been merged .
Add vendor branch support for Cool Pi Genbook
And use mainline u-boot for vendor branch。
How Has This Been Tested?
Compiled with command:
./compile.sh build BOARD=coolpi-genbook BRANCH=vendor BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED='browsers chat desktop_tools editors email internet multimedia office programming remote_desktop' DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base DOWNLOAD_MIRROR=bfsu EXPERT=yes EXTRAWIFI=no KERNEL_CONFIGURE=no RELEASE=noble
flash the img to sdcard, insert the sdcard to a usb disk, insert usb disk to genbook,the Armbian system can boot from
usb disk。
Checklist: