Automotive Collaboration: What's Really Going On? Has Something Improved During the Last Year?
summary
Community projects show concrete wins: multiple vendors merge working code into AGL and GENIVI (including Raspberry Pi reference builds) and several teams integrate a common software update flow for atomic OTA across ECU networks. Pain points remain practical: Yocto/Qt licensing shifts (notably Qt 5.7 GPLv3), limited OEM participation, CI and legacy-platform support, and the scaling challenge from ~1M to ~100M lines of code. Small hypervisors (Jailhouse) and adaptive AUTOSAR packaging are being trialed but full production adoption is not yet widespread.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:52Meet the team
- 3:33Who are they
- 9:09Open Source for Automotive
- 10:56Collaboration
- 14:17Audience Comments
- 21:21Atomic Updates
- 28:31Negatives
- 31:23Biggest pain point
- 34:21Standardization
- 35:58Open Interconnect
- 38:00Key Messages
- 39:58Conclusion
- 40:54Call to Action
- 42:48Key Message
- 45:13Show of Hands
- 49:03Collabera
- 50:46Final Thoughts
related talks
49mOpen Source in Every Car with Automotive Grade Linux
43mContributing to Automotive Grade Linux and GENIVI Development Platform
35mIntroduction to AGL Architecture and Roadmap
22mKeynote: AGL State of the Alliance: Looking Toward 2024 and Beyond
26mAutomotive Grade Linux (AGL) Update
38mBoF: Automotive Grade Linux Developer Community
50mLinux You Can Drive My Car
35mAutomotive Grade Linux State of the Union