Lightning Talk: Lessons Learned From 10 Years of Automotive Grade Linux
summary
Automotive Grade Linux unifies multiple OEMs and Tier‑1s into a single distribution (the UCB) built with Yocto, using systemd, pipewire and wireplumber, Flutter and Jenkins, and ships in millions of vehicles since 2018 with nine OEM members. Lessons: consolidate communication and a unified codebase; embrace replacing homegrown stacks with upstream projects; OSPO processes often delay contributions by two-plus years; developer engagement needs cheap hardware and emulators; BSP/kernel update lag from dev boards to production hardware remains unsolved.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:22What is Automotive Grade Linux
- 3:47Early challenges
- 5:50Get everybody aligned
- 7:14Unified codebase
- 9:20Embrace change
- 11:08Educate the industry
- 12:10Engage outsiders
- 13:58Dev vs production boards
- 15:04Closing & Q&A
related talks
38mAutomotive Grade Linux - Evolution and Lessons Learned From 10 Years of Community Management
49mOpen Source in Every Car with Automotive Grade Linux
42mAccelerating Software Defined Vehicles Through Open Source Software
37mBoF: Automotive Grade Linux Developer Community
35mAccelerating Software Defined Vehicles Through Open Source Software
27mKeynote Session: AGL State of the Alliance
36mAligning Automotive Standards with Open Source Excellence
39mPanel Discussion: Open Source as a Path for a Competitive Automotive Industry
