SDV BoF
summary
AGL claims it already provides the building blocks for software‑defined vehicles: downloadable binaries for Kimu and multiple boards, and a demonstrated same executable running on Renesas, Qualcomm and the cloud. The group pushes a vehicle hardware abstraction (VERIO) to enable hardware‑agnostic updates and zonal consolidation, argues for 70–80% shared open source stack, and warns of massive telemetry — 25 GB/car/day × 400M vehicles — as a scaling challenge.
AI-written summary · about
chapters (11)
- 0:00SDV BoF introduction
- 1:47Defining the software defined vehicle
- 6:53Software defined products examples
- 10:50Hardware upgradability challenges
- 16:13Key requirements for SDVs
- 19:06Monetizing post-delivery features
- 23:01Open source reducing development costs
- 26:15Maturity of post-delivery updates
- 28:47Telecom lessons for hardware upgrades
- 30:33AGL’s SDV role next year
- 32:21Future vision for AGL in software defined vehicles
related talks
01h 00mAutoSD: A Linux Development and Prototyping Framework for the Automotive Community
49mOpen Source in Every Car with Automotive Grade Linux
53mAutomotive Collaboration: What's Really Going On? Has Something Improved During the Last Year?
38mBoF: Automotive Grade Linux Developer Community
28mLinux in Cars! CentOS AutoSD, SDVs, and more
26mAutomotive Grade Linux (AGL) Update
35mAutomotive Grade Linux State of the Union
51mOpen Source for Automotive Developed in the Open becomes Real: GENIVI Development Platform