What's New with U-Boot?
summary
U-Boot now includes a driver model, Kconfig/Kbuild integration, categorized logging, EFI support and Android AVB plus a sandbox for host testing; the tree is ~2.2M LOC but per-board binaries are much smaller. Automated testing via ptest and a growing test farm runs unit and functional tests (make check finishes in about a minute) and remote rigs can run real-hardware tests. A device-tree-in-C trick shrinks SPL DT to ~3KB (overlays usually add 3–4KB). The buildman system can build ~1,300 boards across 145 commits (a full run took ~24 hours).
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:16Goals of this talk
- 1:03U-Boot Overview
- 1:48What's not new?
- 3:47Driver model
- 5:33Bootstage and Tracing
- 6:10Buildman
- 7:55New things ( 2 years)
- 8:15Device tree overlays
- 12:21Example of platdata driver code
- 12:45Android and OP TEE
- 13:59New hardware / automated testing
- 17:49Documentation format
- 21:21Logging
- 22:35Patman
- 23:06How might U-Bootlook in a few years?
- 26:35Thank you for listening
related talks
33mU-Boot's New Standard Boot and What's Next
50mRethinking U-Boot Devicetree Story
55mImplementing State-of-the-Art U-Boot Port, 2018 Edition
43mU-Boot - Bootloader for IoT Platform?
49mEmbedded Linux BOF
43mU-Boot - Bootloader for IoT Platform?
55mThe Embedded Linux Problem
01h 04mFundamentals of Embedded Linux
