Working with the Community: A Timeline for Adding Support for a New Board in Zephyr
summary
Timeline and concrete checklist for upstreaming a board: create or get a toolchain merged (budget one month for toolchain), add board YAML/DTS and minimal drivers to run hello world on hi4 DSP, wire West target names and CI (allow one week for CI integration), keep PRs small — limit PRs to five patches — and expect reviews needing two approvals and roughly expect four to five weeks to merge; run checkpatch.pl, per‑commit CI, and iterate on maintainer comments.
AI-written summary · about
chapters (9)
- 0:00Introduction and overview
- 2:00Zephyr release cycle
- 4:34Toolchain setup
- 7:30Hardware modeling concepts
- 13:20Layered board implementation
- 16:28Adding board support
- 26:07Running the application
- 27:18Upstreaming contributions
- 35:27Q&A and closing
related talks
40mWorking with the Community: A Timeline for Adding Support for a New Board in Zephyr
40mBoF: Zephyr: Meet the Maintainers
40mContributing to Zephyr vs (Linux and U-boot)
36mHow to Get Your Zephyr Patches Merged
39mBoF: Meet the Zephyr Community
40m9 Years in the Making, the Story of Zephyr, Starting with Commit Nr. 1
36mNo, It's (Still) Never Too Late to Upstream Your Legacy Linux Based Platforms
41mZephyr Documentation BoF