Device Tree Metadata: How Bootloaders Pick DTBs and Apply Overlays
summary
Bootloaders need concrete metadata to pick a base DTB and the exact DTBOs: FIT image uses a configuration that maps a compatible string to kernel + DTB + DTBOs, Android DTBO uses up to six 32‑bit integers for matching, and current overlays cannot append compatible strings. Practical proposals include embedding a small config node listing applied DTO filenames inside overlays (prototype in U‑Boot) or recording mapping next to DTS sources for make-fit tooling; ChromeOS already bundles base DTBs + DTOs with an auto‑select script.
AI-written summary · about
chapters (10)
- 0:00Introduction to Device Tree Metadata
- 1:04Consumer Electronics SKU Problem
- 3:59Overlay Composition Challenges
- 7:06Top-Level Compatible String Purpose
- 10:15Config Node Proposal
- 14:31FIT Images and Compatibility
- 18:30Android DTB and DTBO Formats
- 20:37Loader-Specific DTBO Properties
- 22:49Vendor-Specific Property Discussion
- 28:13Conclusion and Q&A
related talks
51mShipping Multiple Devicetrees: How to Identify Which DTB Is for My Board?
44mBoF: Devicetree
01h 10mBoF: Devicetree
01h 13mDevice Tree for Dummies!
50mRethinking U-Boot Devicetree Story
25mDevice-tree overlay feature allows for runtime modification
40mSecond Source Component Probing on Device Tree Platforms
54mBoot Loader Specification + sd-boot
