Embedded Linux BOF
summary
Group discussion catalogs concrete wins and pain points: prioritized boot time, system size, testing and build systems; practical tactics include U-Boot HTTP boot, uread-ahead, XIP where used, aggressive modular drivers with deferred probes and device-links, runtime-PM and offloading firmware to reduce an eight‑second camera startup, and using tracing/boot‑chart/logic probes to measure gains. The room notes a rapid shift to 64‑bit, 64 MB as a realistic minimum, Yocto LTS/resource gaps, the elinux wiki funding need (~$6k/yr), and a clear demand for more maintainers and upstream investment.
AI-written summary · about
chapters (13)
- 0:00Introduction and welcome
- 2:34Embedded Linux focus areas
- 8:19Boot time reduction techniques
- 19:55Why embedded Linux is hard
- 23:05File systems and system size
- 24:09System size challenges
- 30:55No libc and Yocto Project
- 33:08Yocto Project LTS and resources
- 36:22Testing and community issues
- 37:06Embedded Linux Leadership Summit
- 41:07Community and ecosystem gaps
- 43:55elinux Wiki funding and future
- 46:49Open discussion and Q&A
related talks
39mBoF: The Yocto Project and OpenEmbedded
01h 04mFundamentals of Embedded Linux
46mStatus of Embedded Linux
42mBoF: The Yocto Project and OpenEmbedded
42mBooting Automotive ECUs Really Fast with Modern Security Features
35mMake Your System Firmware Faster, More Flexible and Reliable with LinuxBoot
33mU-Boot's New Standard Boot and What's Next
37mBoF: Challenges of Low Spec Embedded Linux
