The ELCE 2016 session most closely matching “Introduction to Automotive Grade Linux” was listed as “Open Source in Every Car with Automotive Grade Linux,” presented by Walt Miner of the Linux Foundation. The supplied wording is not confirmed as the official session title. A separate talk addressed how AGL was built and tested, so the two should not be treated as one presentation.
Read the session as a snapshot of an emerging effort to create shared, open automotive Linux infrastructure—not as a claim that every car already used AGL or as a guide to today’s AGL releases. The surviving conference listing confirms the session and speaker, while technical details about nearby GENIVI and GDP work come from a separate contemporaneous presentation.
As an Amazon Associate I earn from qualifying purchases.
What was the ELCE 2016 session?
Embedded Linux Conference Europe (ELCE) took place in Berlin in October 2016. A contemporaneous conference video roundup lists Walt Miner of the Linux Foundation speaking on “Open Source in Every Car with Automotive Grade Linux.” It also lists Jan-Simon Moeller’s separate session, “Building and Testing an Automotive Platform — How Automotive Grade Linux is Built and Tested.” The listing establishes that both talks were part of the event; it does not provide a full transcript or enough detail to reconstruct either presentation slide by slide. The ELCE 2016 session listing is the basis for identifying the closest matching title and distinguishing the talks.
Recommended Free Tools
That distinction matters: an introduction to AGL and a presentation about its build-and-test process address related but different questions. The most defensible account of Miner’s session is therefore about AGL’s purpose and collaborative model, not specific commands, test results, or features that the surviving listing does not verify.
#1 Best Overall
Why automakers were interested in shared Linux
By 2016, in-vehicle infotainment (IVI) systems were taking on work associated with general-purpose computing: graphical interfaces, media, navigation, connectivity, and applications. Automakers and suppliers had to integrate increasingly complex software, often on fragmented, proprietary foundations. Building the same low-level capabilities repeatedly could consume engineering effort without making each vehicle meaningfully distinct.
AGL offered a collaborative alternative: a common open-source foundation that participating companies could develop together and adapt to their products. The intended division was not “one identical system in every car.” Shared platform software could provide reusable infrastructure; manufacturers and suppliers could still differentiate through hardware choices, user experience, services, integration, and vehicle-specific features.
“Open source in every car” was an ambition, not evidence that all cars—or even a specific production model—ran the AGL software shown or discussed at ELCE. Nor does an open Linux base by itself settle production concerns such as cybersecurity response, long-term maintenance, supplier accountability, functional-safety work, validation, or regulatory compliance. Those require engineering and program processes beyond choosing a shared platform.
Rank #2
- Official Record Book: This hardcover log book is designed to record the purchase, sale, or exchange of new and used motor vehicles.
- Comprehensive Tracking: With 975 vehicle record entries, it allows for meticulous documentation of automotive transactions.
- Durable Construction: The sturdy hardcover binding ensures long-lasting use and protection of important records.
- Convenient Size: Measuring 11.5 x 9.5 inches, this book offers ample space for detailed vehicle information.
- Essential Tool: An indispensable resource for car dealers, ensuring proper documentation and compliance with regulations.
What AGL meant in the 2016 context
Automotive Grade Linux was a Linux Foundation collaboration focused on automotive software. Its value proposition was to bring automakers, suppliers, chip vendors, software companies, and developers into shared work on an automotive Linux platform rather than leaving every organization to assemble all common infrastructure independently.
That collaboration model can make reusable code and integration work visible to more participants, and can create a route for fixes to be contributed upstream. It does not mean that every component in a vehicle must be open source, that every participant uses the same product configuration, or that an OEM gives up control of releases, security decisions, branding, or product differentiation.
The available session listing does not establish a complete inventory of what Miner covered. In the broader 2016 automotive-Linux context, the technical work around such platforms could span kernel and board support, boot and system integration, graphics, application frameworks, middleware, connectivity, and image creation. These are useful areas for understanding the ecosystem, but they should not be presented as a verified agenda for this particular talk.
How AGL, GENIVI, GDP, and Yocto differed
AGL, GENIVI, and the GENIVI Development Platform (GDP) belonged to the same broader open automotive-software landscape, but they were not interchangeable names. A contemporaneous GENIVI presentation describes GDP as a Yocto-based development and demonstration platform. Its account helps explain adjacent work at ELCE, not the exact contents of Miner’s AGL session.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →| Project or technology | Role described in the 2016 context | How to interpret it |
|---|---|---|
| Automotive Grade Linux (AGL) | Linux Foundation automotive collaboration initiative | A collaborative effort around an open automotive Linux platform. |
| GENIVI | Industry organization focused on open IVI software and automotive middleware | A separate organization and ecosystem with overlapping interests and participants. |
| GENIVI Development Platform (GDP) | Packaged development and demonstration platform incorporating automotive software | A way to make integrated components easier for developers and newcomers to try; not another name for AGL. |
| Yocto Project | Embedded Linux build foundation used by GDP | Build and customization infrastructure, rather than an automotive product by itself. |
The GDP presentation distinguishes a rolling Master integration branch, aimed at system developers and contributors, from packaged GDP releases aimed more at application developers and users who wanted a comparatively stable environment. A packaged release traded some immediacy for a more approachable, integrated starting point; Master offered newer integration work but carried greater change and maintenance risk. The contemporaneous GDP presentation documents this distinction and the dated technical details below.
What the GDP 11 materials show about the 2016 stack
GDP provides a concrete neighboring example of what developers could encounter in the 2016 automotive-Linux ecosystem. These versions and targets are a historical snapshot, not current recommendations or proof of production qualification.
Rank #4
- The preinstalled USB stick allows you to learn how to learn use Linux, boot and load Linux without uninstalling your current OS! 30 day money back guarantee no questions asked! See s://.gnu.org/philosophy/selling.en.html for more info about open source software!
- Comes with easy to follow install guide. 24/7 software support via email included. (Only USB flash drives sold by the seller Linux Builder include this)
- Ubuntu 22.04 - 'Jammy Jellyfish'
- Comprehensive installation includes lifetime free updates and multi-language support, productivity suite, Web browser, instant messaging, image editing, multimedia and email for your everyday needs
- Boot repair is a very useful tool! This USB drive will work on all modern day computers, laptops or desktops, custom builds or manufacture built!
- GDP 11 RC2: The presentation dates this release to October 4, 2016, and says it was demonstrated at ELCE. Its listed components included Yocto 2.1, Qt 5.6, Automotive Message Broker 7.0,
wayland-ivi-extension1.10.9 (with 1.11 described as a prerelease), andmeta-ivi11. - Targets and build options: The materials list QEMU, Raspberry Pi 2 and 3, Intel MinnowBoard MAX/Turbot, and Qualcomm DragonBoard 410c. Renesas Porter and Silk were also mentioned, with some builds performed from source. A listed or buildable target is not necessarily a prebuilt image, a board supported in the same way as another, or a vehicle-qualified platform.
- GDP 11 RC3: The presentation dates this release to October 18, 2016. It added an application launcher and demo applications and changed Wi-Fi configuration for Raspberry Pi 3. The slides said the planned final release would support MinnowBoard MAX/Turbot, Raspberry Pi 2/3, and DragonBoard 410c; Renesas boards could be built from Master.
In this stack, Yocto supplied a way to compose and customize embedded Linux images; Qt gave application developers a UI framework; and Wayland with IVI extensions addressed display composition needs. QEMU made some early experimentation possible without a physical board, while the listed boards offered routes to test on real hardware. The GDP packaging effort was itself significant: a complex integration could be made more accessible to application developers than a collection of unrelated source trees.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What developers could do with a development platform
A 2016 GDP- or AGL-era platform was useful for learning, prototyping, application work, integration experiments, and upstream contribution. A historically grounded workflow would look like this:
Free tools Windows power users keep installed
One-click scans. No signup required.
- Choose an environment: Select a target listed for the relevant release, or QEMU where an emulator image was available.
- Obtain matching artifacts: Use the release’s source, configuration, and prebuilt image where provided. The dated GDP materials establish release and target information, but not a complete reproducible download procedure for current systems.
- Boot and explore: Start the image, inspect the launcher and demo applications, and learn how the integrated environment behaves.
- Develop or adapt an application: Work within the software and toolchain available for that release, including its UI and middleware components.
- Customize the image: Use Yocto layers and configuration to integrate changes rather than treating a development image as a finished vehicle system.
- Test on the intended target and contribute fixes: Validate behavior on actual hardware where possible, then share applicable changes through the project’s collaborative development process.
The historical material does not establish a current installation path, exact commands, or present-day board support. QEMU can help with early software work, but emulation cannot expose every graphics, peripheral, boot, networking, power, or driver behavior of a physical board. Likewise, a successful board demonstration shows that some integration worked; it does not demonstrate vehicle-grade reliability.
Why building and testing were separate concerns
The separate ELCE session on building and testing AGL signals that producing an image was only one part of the platform problem. In general, an automotive Linux integration effort must bring together upstream components, create coherent images, and check that system services, graphics, middleware, and applications continue to work together as pieces change.
Testing on an emulator and on representative hardware answer different questions. Automated builds can catch integration failures early; regression testing can reveal whether a change broke previously working behavior; hardware testing can expose issues that simulation does not reproduce. None of these alone establishes suitability for a specific vehicle program, and the surviving conference listing does not report coverage, pass rates, or a particular CI design for the talk.
What the 2016 approach made possible—and what it left open
Where shared development helped
- Organizations could work from common Linux infrastructure instead of duplicating every platform layer.
- Developers could experiment with a packaged platform and contribute improvements to shared components.
- Yocto-based customization, Qt applications, Wayland/IVI graphics, and multiple emulator or board targets offered practical entry points for prototyping.
- Open collaboration could make integration work and problems visible across a broader industry community.
Where the hard work remained
- Hardware enablement varied by target; “listed,” “buildable,” “demonstrated,” and production-qualified are different claims.
- A common Linux base did not remove OEM needs for differentiation, release control, security processes, lifecycle support, or vehicle-specific integration.
- Development images and demos were not substitutes for extensive validation, safety-related engineering, or regulatory compliance.
- The GDP presentation itself identified needs for better newcomer documentation, more integration and use cases, stronger testing and infrastructure, and greater focus on automotive developers.
How to read the session today
The enduring point of the ELCE 2016 AGL session is the collaboration model: industry participants were exploring how shared open-source infrastructure could reduce duplicated platform work while leaving product-level decisions to manufacturers and suppliers. The technical details around it—GDP 11, Yocto 2.1, Qt 5.6, particular boards, and the Master-versus-release distinction—belong to October 2016. They explain that moment in the ecosystem, not today’s AGL architecture, release names, APIs, or hardware support.
For historians and developers, the session is best treated as an entry point to the period’s debate over open automotive software. The conference listing verifies the related talk titles and speaker; the GDP presentation supplies useful adjacent technical context. Neither warrants inventing a verbatim account of Miner’s presentation or treating a demonstration platform as a production vehicle stack.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
