~/talk

Device Tree Metadata: How Bootloaders Pick DTBs and Apply Overlays

links:none on file
slides:none on file

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

  1. 0:00Introduction to Device Tree Metadata
  2. 1:04Consumer Electronics SKU Problem
  3. 3:59Overlay Composition Challenges
  4. 7:06Top-Level Compatible String Purpose
  5. 10:15Config Node Proposal
  6. 14:31FIT Images and Compatibility
  7. 18:30Android DTB and DTBO Formats
  8. 20:37Loader-Specific DTBO Properties
  9. 22:49Vendor-Specific Property Discussion
  10. 28:13Conclusion and Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.