bootloader: Add an aboot (Android) bootloader backend #2793
Conversation
|
Hi @ericcurtin. Thanks for your PR. I'm waiting for a ostreedev member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
ericcurtin
force-pushed
the
aboot-bootloader-support
branch
from
a6a9912
to
8ceada2
Compare
ericcurtin
changed the title
|
Related one-liner PR: |
ericcurtin
force-pushed
the
aboot-bootloader-support
branch
from
8ceada2
to
b634ceb
Compare
|
Related commit for aboot-deploy: |
|
Related PR for aboot-update: https://gitlab.com/CentOS/automotive/rpms/aboot-update/-/merge_requests/1 which creates the image file to be written to the boot partition. |
aboot is special in that it packages kernel, initrd, cmdline, dtb and signature one combined image (similar to upcoming unified kernel images). This is then loaded as an image into an aboot partition. This image is signed by the OS vendor and covers everything in the image. So locally on the deployed system it should not be possible to boot an unsigned image (unless signature checking is turned off). We call a shell script aboot-deploy when it is required to write a new image to the aboot partition (a file typically starting with aboot and ending in .img extension). This shell script may also read some configurations from a .cfg file. Signed-off-by: Eric Curtin <ecurtin@redhat.com>
ericcurtin
force-pushed
the
aboot-bootloader-support
branch
from
b634ceb
to
9711775
Compare
|
Thanks for looking at this @cgwalters we boot from an Android boot partition (which is unrecognizable in a normal Linux userspace, it's just data in a a partition), which is where the aboot.img file essentially gets written to. U-boot actually has some nice documentation on how it works, I test using that... Although this will really be loaded from the Qualcomm Android Bootloader in real life. u-boot has some documentation on this: https://u-boot.readthedocs.io/en/latest/android/boot-image.html |
aboot is special in that it packages kernel, initrd, cmdline dtb and signature one combined image (similar to upcoming unified kernel images). This is then loaded as an image into an aboot partition.
This image is signed by the OS vendor and covers everything in the image. So locally on the deployed system it should not be possible to boot an unsigned image (unless signature checking is turned off).
We call a shell script aboot-deploy when it is required to write a new image to the aboot partition (a file typically starting with aboot and ending in .img extension). This shell script may also read some configurations from a .cfg file.
Signed-off-by: Eric Curtin ecurtin@redhat.com