Android Boot: Next Steps
summary
Google pushes GBL UEFI app as a reusable Android bootflow to reduce vendor work and enable features like bootconfig and PVMF loading. Current problems are Android-specific header formats, DT table limits (no metadata, no alignment), and verifying huge vendor_boots (examples up to 150 MB wasted). Proposal uses FIT in DTBO with external images, 8‑byte alignment, per-image compression and verification, a UEFI hook for firmware-led configuration selection, U-Boot fit tooling for image generation, and initial support limited to new devices.
AI-written summary · about
chapters (7)
- 0:00Introduction to Android bootflow
- 1:25Current Android bootflow recap
- 4:15Problems with current approach
- 6:23FIT image structure explained
- 8:32Current FIT adoption plans
- 10:22Future FIT improvements
- 13:10Q&A session
related talks
22mBoot Requirements and Strategies for the Edge
40mRecent Advances in U-Boot
28mExtending EFI support in Linux to new architectures
54mBoot Loader Specification + sd-boot
35mMake Your System Firmware Faster, More Flexible and Reliable with LinuxBoot
53mMarrying U-Boot, uEFI and grub2
48mUnified Boot Time Measurement: A Precise, Scalable Framework for Multi-Processor Systems
34mTweaking the Linux Boot Flow for an Accelerated ADAS Experience