Shipping Multiple Devicetrees: How to Identify Which DTB Is for My Board?
summary
Proposal adds a board-id property in the DT root so bootloaders can match hardware IDs (CDT/MSM registers) to the correct blob, replacing fragile compatible-string parsing. Implementations target U-Boot, coreboot, GRUB and can embed the value in a FIT image or read hardware registers; Qualcomm reports shipping 20 DTBs and 100+ overlays across reference SKUs. RFCs exist and the work is in early stages seeking community consensus, not yet a finished, widely deployed solution.
AI-written summary · about
chapters (7)
- 0:00Multiple device trees intro
- 2:46Shipping multiple device trees
- 10:53Device tree selection challenges
- 18:35Unified board ID proposal
- 27:47Board ID implementation discussion
- 42:04Backward compatibility & future
- 49:20Q&A
related talks
37mStable Devicetree ABI: it's possible!
15mIs the Zephyr Device Tree Too Complicated?
27mInsights on the Re-Architecting to a Single Codebase, Running on Different Hardware...
37mHow to Get Your DT Schema Bindings Accepted in Less than 10 Iterations
35mBoosting Product Development With the Zephyr RTOS – a Critical Reflection
15mTraits Architecture
15mvBOIDs: Taming Chaos via Coarse-Grained Scheduling Abstraction for Containers
41mBootable applications - an introduction