Rethinking U-Boot Devicetree Story
summary
Argues for a single canonical device tree shared from the Linux snapshots into U-Boot to eliminate fragmented DTS imports, using git subtree to pull full-tree snapshots and an opt-in Kconfig plus a build rule make dtbs_check to run bindings checks during U-Boot builds. Shows a cherry-pick script for fixes, recommends syncing only on major kernel releases to reduce DT ABI breakages, and proposes an ABI-checking tool and workflow so firmware (SPL/TF) can ship the authoritative DT instead of distro packaging.
AI-written summary · about
chapters (7)
- 0:00Introduction to device tree
- 0:54Fragmentation issues
- 1:33Embedded ecosystem context
- 2:30Improving the device tree
- 31:29Question and answer session
- 32:15Discussion on compatibility
- 50:02Closing remarks
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
43mReproducible Multi Element System Composition with Linux, Xen & Zephyr
44mDependencies; Devil or Darling?
43mGoing West: How We Develop and Maintain a Zephyr-based Microcontroller SDK