rpi: Use RPi OS' config.txt for RPi devices - #193
Merged
Merged
Conversation
Going to use RPi linux kernel from rpi OSTree branch on RPi devices to have better hardware support. Then, the system should use the device tree from the RPi kernel and composed by the RPi firmware. Because, there is already the RPi kernel, install the device tree blobs and overlays from the OSTree deployment into boot partition directly, instead of those original prepared dtbs. To include more RPi devices' device tree blobs and overlays, enlarge the boot partition size to 512 MB, just like RPi OS image. https://app.asana.com/1/1203676861188277/project/1211061530470838/task/1211622697341771
RPi firmware composes the device tree with overlays. Not only the single device tree blob. So, teach u-boot pass the device tree composed by RPi firmware to kernel. Other arm64 platforms keep use the device tree deployed by OSTree commit directly. https://app.asana.com/1/1203676861188277/project/1211061530470838/task/1211725762061813
RPi firmware coworks with device tree to decide the CMA size automatically. Then, kernel allocates the CMA memory. So, there is no need to insert the customized cma argument into the boot command. https://app.asana.com/1/1203676861188277/project/1211061530470838/task/1211645002178218
starnight
marked this pull request as draft
November 17, 2025 07:04
EOS has decides using RPi Linux kernel, including the device tree & overlays to have better hardware support on RPi devices, including RPi 500. So, here uses RPi OS' config.txt for composing the device tree by the RPi firmware. Got the config.txt from image 2025-10-01-raspios-trixie-arm64.img.xz downloaded from Raspberry Pi OS downloads [1]. [1]: https://www.raspberrypi.com/software/operating-systems/ https://app.asana.com/1/1203676861188277/project/1211061530470838/task/1211943756834438
U-Boot cannot boot systems on RPi 4 series until enable UART. But, U-Boot cannot boot systems on RPi 5 series until disable UART. So, make it only enable UART on RPi 4 series devices. https://phabricator.endlessm.com/T30780#883184 https://app.asana.com/1/1203676861188277/project/1211061530470838/task/1211943756834438
…ition PRi 5 series devices, including RPi 500 cannot boot u-boot until install RPi 5 series device tree blobs into RPi image's boot partition. Note: RPi 500 uses device tree blob bcm2712-rpi-5-b.dtb, too. https://app.asana.com/1/1203676861188277/project/1211061530470838/task/1211800919141751 https://app.asana.com/1/1203676861188277/project/1211061530470838/task/1211943756834438
starnight
force-pushed
the
enable-rpi5-boot
branch
from
November 17, 2025 09:03
f9e574c to
a943e9c
Compare
Contributor
Author
|
This is blocked on #192. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
EOS has decides using RPi Linux kernel, including the device tree & overlays to have better hardware support on RPi devices, including RPi
500. So, here uses RPi OS' config.txt for composing the device tree by the RPi firmware.
Got the config.txt from image 2025-10-01-raspios-trixie-arm64.img.xz downloaded from Raspberry Pi OS downloads 1.
https://app.asana.com/1/1203676861188277/project/1211061530470838/task/1211943756834438