Aligning Automotive Standards with Open Source Excellence
summary
Company claims a practical method to qualify Linux for automotive by treating distributions as integration, not implementation, trimming ~70% of features to a quality managed Linux baseline and partnering with Canonical for packaging and monitoring. Strategy maps ASPICE deviations to compensation measures: ISO 15288 decision records, IEC 61508 black‑box testing, LTP and fuzzing in a layered verification chain, plus a 15‑year maintenance promise and frozen kernel releases with only a few staged updates over vehicle lifetime. Numbers cited: 600M vehicles, 5B devices, kernel churn ~9 changes/hour.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:04Automotive standards and open source
- 4:19Automotive architecture and Linux
- 10:02ASPice challenges with open source
- 12:30ASPice deviations and justification
- 17:25Solution approach and measures
- 19:56Future of mobility and open source
- 22:11Q&A: Kernel updates and vulnerabilities
- 24:23Q&A: ASPice tailoring and ISO 26262
- 28:17Q&A: Legacy OEMs and Linux
- 33:52Q&A: Open source collaboration
related talks
36mAligning Automotive Standards with Open Source Excellence
49mOpen Source in Every Car with Automotive Grade Linux
42mAccelerating Software Defined Vehicles Through Open Source Software
19mDriving Automotive with Open Source: From Compliance to Collaboration
35mAccelerating Software Defined Vehicles Through Open Source Software
39mPanel Discussion: Open Source as a Path for a Competitive Automotive Industry
15mLightning Talk: Lessons Learned From 10 Years of Automotive Grade Linux
35mOpen Sesame! Why Functional Safety is the Master Key to Open the Door for Linux into Automotive