kernel: build system outputs and workflows (and how to balance them)
summary
Describes how the Yocto/OpenEmbedded kernel integration actually works: build outputs are kernels, modules, DTBs, firmware, Linux-lipsy uapi headers, SBOM and traceability metadata; upgrades force rebuilding tightly coupled user‑space (about seven packages routinely break) so a kernel bump can take days unless automated; project runs three reference kernels (dev/release/LTS) per release to drive testing; unexpected issues (serial‑port race, FPU init bugs) appear during validation; proposes uapi-check integration, expanded runtime tests, and offering flexible workflows rather than mandating one.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 1:04Balancing build system requirements
- 8:30Defining build system personas
- 14:52Reference kernel in build systems
- 22:01Challenges of kernel workflows
- 30:56Future directions and thoughts
- 37:25Q&A and closing
related talks
28mBuild System Analysis for Kernel Development and Customization
53mWorking with the Linux Kernel in the Yocto Project
30mStrategies for Developing and Deploying your Embedded Applications and Images
53mReal-World Yocto: Getting the Most out of Your Build System
24mContinuously Integrating the Upstream Linux Kernel on Hardware
41mDebian & Yocto: State of the Art
33mUsing Open Source Software to Build an Industrial-grade Embedded Linux Platform...
24mKeynote: Status of Embedded Linux