The Need to Drive Towards Frequent and Sustained Software Updates
summary
Claims that cars need 10–15 years support and that European vehicles average 11.8 years on the road drive the argument: kernel CVEs are frequent, many Linux-based ECUs already require dealer firmware flashes (recall example), and Ford reports about 1M OTA-capable vehicles. Recommended tactics are concrete: use declarative systems like NixOS or Yocto fragments, isolate kernel vs SDK work, adopt robust A/B OTA update frameworks and design-for-change modular architecture to enable long-term, reversible updates across multiple hardware generations.
AI-written summary · about
chapters (4)
- 0:00Start
- 13:56Software Challenges for Automotive
- 19:57Design for Change - Tactics
- 23:13Robust Update Frameworks
related talks
51mApproaches to Ultra-Long Software Maintenance
17mAccelerating Development and Deployment of Updatable Linux-based Edge AI devices in the CRA era
34mSafety vs Security: A Tale of Two Updates
43mSecuring the Connected Car
17mSustaining Yesterday’s Linux: Delivering Security for Today’s Workloads
15mDevice Security Matters More Than Ever
26mEngineering for the Long Haul: Operating Open Source at Scale
39mLinux IoT: From Prototype to Production