Tom Rini
4595600007
Merge patch series "bootstd: Add Android support"
Mattijs Korpershoek <mkorpershoek@baylibre.com> says:
Android boot flow is a bit different than a regular Linux distro.
Android relies on multiple partitions in order to boot.
A typical boot flow would be:
1. Parse the Bootloader Control Block (BCB, misc partition)
2. If BCB requested bootonce-bootloader, start fastboot and wait.
3. If BCB requested recovery or normal android, run the following:
a. Get slot (A/B) from BCB
b. Run AVB (Android Verified Boot) on boot partitions
c. Load boot and vendor_boot partitions
d. Load device-tree, ramdisk and boot
The AOSP documentation has more details at [1], [2], [3]
This has been implemented via complex boot scripts such as [4].
However, these boot script are neither very maintainable nor generic.
Moreover, DISTRO_DEFAULTS is being deprecated [5].
Add a generic Android bootflow implementation for bootstd.
For this initial version, only boot image v4 is supported.
This has been tested on sandbox using:
$ ./test/py/test.py --bd sandbox --build -k test_ut
This has also been tested on the AM62X SK EVM using TI's Android SDK[6]
To test on TI board, the following (WIP) patch is needed as well:
https://gitlab.baylibre.com/baylibre/ti/ti-u-boot/-/commit/84cceb912bccd7cdd7f9dd69bca0e5d987a1fd04
[1] https://source.android.com/docs/core/architecture/bootloader
[2] https://source.android.com/docs/core/architecture/partitions
[3] https://source.android.com/docs/core/architecture/partitions/generic-boot
[4] https://source.denx.de/u-boot/u-boot/-/blob/master/include/configs/meson64_android.h
[5] https://lore.kernel.org/r/all/20230914165615.1058529-17-sjg@chromium.org/
[6] https://software-dl.ti.com/processor-sdk-android/esd/AM62X/09_02_00/docs/android/Overview.html
2024-07-18 17:03:47 -06:00
..
2024-05-20 13:35:03 -06:00
2024-07-03 07:36:33 +01:00
2024-07-18 07:49:14 -06:00
2024-06-07 16:20:25 -06:00
2024-07-18 07:50:13 -06:00
2024-07-16 13:01:46 -06:00
2024-05-20 13:35:03 -06:00
2024-07-11 16:12:39 -06:00
2024-07-05 13:57:02 -06:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-07-15 00:17:27 +01:00
2024-06-13 16:30:48 -06:00
2024-07-18 07:40:30 -06:00
2024-05-20 13:35:03 -06:00
2024-07-18 13:51:30 -06:00
2024-06-24 13:34:52 -06:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-06-16 12:13:44 +02:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-06-07 10:47:59 -06:00
2024-05-20 13:35:03 -06:00
2024-06-10 11:43:37 +02:00
2024-07-16 17:09:33 -06:00
2024-06-30 13:58:31 +02:00
2024-07-16 17:09:33 -06:00
2024-06-14 12:59:07 -06:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-06-07 14:05:03 -06:00
2024-07-09 09:15:37 +02:00
2024-06-28 17:30:45 -06:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-05-24 13:40:03 -06:00
2024-05-24 13:40:04 -06:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-07-18 13:51:30 -06:00
2024-05-20 13:35:03 -06:00
2024-06-19 12:07:44 -06:00
2024-06-19 12:07:44 -06:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-07-05 13:57:02 -06:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-06-13 16:27:07 -06:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-05-20 13:35:03 -06:00
2024-06-17 16:02:29 +02:00
2024-05-20 13:35:03 -06:00
2024-05-22 08:55:29 -06:00
2024-06-20 11:41:43 -06:00
2024-06-30 13:58:31 +02:00
2024-06-30 13:58:31 +02:00
2024-05-20 13:35:03 -06:00
2024-05-22 08:55:29 -06:00
2024-06-16 12:14:18 +02:00