Teach RPi platform uses RPi OSTree #192
Merged
Conversation
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
Contributor
Author
|
This is blocked on https://github.com/endlessm/eos-build/pull/1576. So, I convert it to draft. |
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
force-pushed
the
rpi-uses-rpi-ostree
branch
from
2dcf440 to
ebd233b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
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.
Then, make 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/1211622697341771
https://app.asana.com/1/1203676861188277/project/1211061530470838/task/1211725762061813