How I Survived to a SoC with a Terrible Linux BSP
summary
Describes problems with vendor-provided Linux BSPs for SoCs—outdated kernels, broken drivers, missing bootloaders, poor code quality, Windows-only tools and bad support—and recounts real examples of spending weeks fixing and working around them. Explains the impact of such BSPs on product quality and outlines possible responses: options developers can take when stuck with a bad BSP and concrete suggestions for both embedded hackers and SoC vendors to improve the situation.
AI-written summary · about
related talks
27mInsights on the Re-Architecting to a Single Codebase, Running on Different Hardware...
35mBoosting Product Development With the Zephyr RTOS – a Critical Reflection
43mSponsored Session: Why Don't You Love Me Back, Open-source Software?
43mAccelerated Porting of Linux, U-Boot and Yocto for Production Ready Emb...
42mFrom Growing Trend to Gold Standard: Tooling Linux for the Future of Embedded Systems
14mAOSP Devboards
25mChallenging Hardware Contests With Zephyr and Lessons Learned
55mOvercoming C++ Embedded Development Tooling Challenges