Android Boot, DRTM, UKIs
summary
Android introduces a UEFI application called GBL Rust UEFI app that runs no_std, compiles with Bazel, and already boots Cuttlefish and several vendor devboards; it links ATF, AVB, BoringSSL, libfdt and ships as an EFI SPAB partition. New GBL protocols actually implemented include boot control and OS configuration protocols, boot memory, AVF, AVB, fastboot hooks and DT fixup. For measured launch the plan is a multi-stage DRTM/DLME that measures kernel, ramdisk, DT overlays, RNG seeds, keys, rollback indices and PVM firmware; a UKI-based hypervisor-loader path (PKVM) is prototyped.
AI-written summary · about
chapters (7)
- 0:00Introduction to Android boot
- 3:15Android bootloader GBL overview
- 9:50DRTM and its challenges
- 16:58ACPI vs Device Tree for DRTM
- 21:55DLME and multi-stage boot
- 26:27UKIs and hypervisor loading
- 30:21Q&A and closing remarks
related talks
33mGeneric BootLoader on Android Platforms
26mBootloops & Coffee: The Daily Grind of an AOSP Developer
20mExploration of Productization of Android on RISC-V
09mCuttlefish and Kernel Dev
28mAndroid boot verification to ensure integrity of OS and parti…
38mHow to Enable Android (AOSP) on Your Developer Board
25mBootStomp: On the Security of Bootloaders in Mobile Devices
43mEmbedded Android #3 - Native Android user-space