-
Notifications
You must be signed in to change notification settings - Fork 61
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
meta-rauc-raspberrypi: Kirkstone update #93
Conversation
leon-anavi
commented
Apr 3, 2024
- Cherry pick relevant Raspberry Pi specific patches from branch master to branch kirkstone. This brings a lot of important features, including 'verity' bundle format, linux kernel configuration update, use MACHINE variable instead of the hard-coded RaspberryPi4 for RAUC bundle and system.conf
- Drop EOL releases and support only release kirkstone with branch kirkstone.
Taken from https://rauc.readthedocs.io/en/latest/integration.html#kernel-configuration Do not manually set squashfs options that only reflect defaults. Also enforcing single-threaded squashfs decompression might unnecessary slow things down. Signed-off-by: Enrico Jorns <[email protected]>
The legacy 'plain' format should not be used for new setups. Signed-off-by: Enrico Jorns <[email protected]>
RAUC uses NBD internally for its streaming helper process. Signed-off-by: Enrico Jorns <[email protected]>
Signed-off-by: Enrico Jorns <[email protected]>
With the current service, only the extended partition is expanded to fill the space. This also extends partition 6 which is the current /home and the last partition on the disk. Signed-off-by: Drew Moseley <[email protected]>
Instead of hard-coding RaspberryPi4, use a MACHINE variable in the update bundle and system.conf to support builds of other RPi platforms and avoiding a mismatch of configs. Signed-off-by: Dan Walkes <[email protected]>
Remove EOL release and support only release Kirkstone with branch Kirkstone of layer meta-rauc-raspberrypi. Use branch master with newer releases. Signed-off-by: Leon Anavi <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine to me.
As a suggestion: We tend to use git cherry-pick -xs
in other rauc-related repos that add a "cherry picked from xxxx" line to better point out the cherry-pick background and history of a commit.
Thanks for the recommendation! I will merge this GitHub pull request as it is but I use this approach with |