Linux in Cars: So What?
summary
Linux runs in cars but most infotainment remains proprietary, causing vendor lock‑in, long maintenance and stale forks; industry groups exist—GENIVI (2009), AGL (2016) and Google’s Android Automotive from 2017—but OEMs still freeze component versions for 3–5 years instead of upstreaming. Practical hurdles include hypervisor graphics/audio sharing, integrating PipeWire/PulseAudio, meeting a legal 2‑second rear‑camera boot target while full UI lands in ~4–6s, and coordinating safety renderers like Qt Safe Renderer with screen collaboration tools such as KDE Connect and Kirigami.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker intro
- 1:27Current infotainment system architecture
- 3:56Industrial challenges with open source
- 6:03Open source organizations in automotive
- 9:12Automotive industry structure
- 11:00Why OEMs must drive open source
- 12:26KDE technologies for car systems
- 15:39Performance and boot time requirements
- 17:05Hypervised systems and safety
- 19:53Call to contribute and collaborate
- 20:13Q&A session
related talks
49mOpen Source in Every Car with Automotive Grade Linux
35mEmbedded Linux is a Glorious Lie
49mOpen Source in Every Car with Automotive Grade Linux
41mResolve and standardize early access to hardware for automotive industry with Linux
19mDriving Automotive with Open Source: From Compliance to Collaboration
27mHow to Implement an Automotive Infotainment System using Qt Quick
21mQtinUse - Introducing Qt IVI (1/5)
48mAn Introduction to Android Automotive OS