Will it Boot? -- The Case for Platform Standards in Embedded
summary
Argues that embedding three concrete interfaces cuts per-platform engineering: have firmware (U-Boot) supply a runtime Device Tree provided by U-Boot, implement a minimal UEFI subset (EBBR) so distros get predictable boot services and variables via UEFI EBBR subset, and use Update Capsule + DFU/LVFS for firmware updates. Implements these with mainline-friendly tools (U-Boot, EDK2 tests, FIT images, fwupd), runs UEFI SCT and Firmware Test Suite, has an ARM SystemReady ACS image and two certified platforms, and requires booting at least two unmodified distros.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 0:32What am I trying to solve
- 5:29System Ready Program
- 7:10Embedded Linux Ecosystem
- 9:35Linux Distros
- 13:48Architecture
- 15:03UEFI
- 19:10UFI API
- 22:07UFI Behavior
- 23:13Runtime Services
- 24:06UEFI Secure Boot
- 25:34Firmware Update
- 27:35Device Tree
- 30:20Linux
- 30:36Embedded Linux
- 31:53Testing
- 34:32System Ready
- 37:26Shoutouts
- 39:45Certification Program
related talks
39mEBBR: Standard Boot for Embedded Platforms
33mU-Boot's New Standard Boot and What's Next
49mEmbedded Linux BOF
42mImplementing UEFI-based Secure Boot + OTA Update for Embedded ARM De...
35mMake Your System Firmware Faster, More Flexible and Reliable with LinuxBoot
01h 04mFundamentals of Embedded Linux
40mArm SystemReady IR Band – “Making Software Just Work!”
41mResolve and standardize early access to hardware for automotive industry with Linux