Audi leads $28M Series C round in Silvercar; developing Audi Shared Fleet
GM to invest $500M in Lyft; creating integrated network of on-demand autonomous vehicles

Ford, Mazda, Mitsubishi Motors & Subaru Join Linux Foundation and Automotive Grade Linux; new unified code base distribution

Automotive Grade Linux (AGL), a collaborative open source project developing a common, Linux-based software stack for the connected car, announced that Subaru (Fuji Heavy Industries, Ltd.), Mitsubishi Motors, Mazda Motor Corporation and Ford Motor Company are joining The Linux Foundation and AGL. Ford Motor Company is the first US car manufacturer to join AGL. These latest automakers join existing members Toyota Motor Corporation, Nissan Motor Company Ltd. and Linux Foundation board member Jaguar Land Rover.

AGL also announced a new Unified Code Base (UCB) distribution built specifically for the automotive industry. This new Linux distribution was built from the ground-up to address automotive-specific applications and leverages the best software components from AGL and other existing open source projects such as Tizen and GENIVI Alliance.

Members. AGL also announced that Toyota Motor Corporation, Panasonic Corporation, DENSO CORPORATION, and Renesas Electronics are upgrading to the Platinum level, while NTT DATA MSE is upgrading to the Gold level. The increased financial commitment will go primarily toward software development activities within the AGL open-source project.

AGL has four classes of corporate membership: Platinum, Gold, Silver, and Bronze. AGL has more than 50 members representing leading car manufacturers, auto suppliers, system integrators and OSVs that are actively collaborating on the AGL Unified Code Base Linux Distribution also announced today.

Unified Code Base. AGL suggests that by customizing the distribution to meet specific automotive requirements, its new UCB distribution is in a position to become the de facto standard for the industry, allowing developers and carmakers to leverage a software stack based on Linux for creating in-vehicle software. Automakers and suppliers are able to collaborate directly with AGL’s global community of developers to advance the software for connected car applications.

Several members of AGL, including Toyota, Aisin AW, DENSO, Fujitsu Ten, HARMAN, Panasonic, Pioneer and Renesas Electronics are planning to use the AGL Unified Code Base distribution to deliver a modern in-vehicle infotainment and connected car experience for consumers. Jaguar Land Rover, a Linux Foundation board member, also delivers a Linux-based infotainment system in its vehicles.

The announcement of this new AGL Unified Code Base distribution is the significant first step in creating an open ecosystem based around a common platform that will accelerate rapid innovation of infotainment features. Toyota plans to support contiguous enhancement of the distribution for future infotainment systems to deliver cutting edge connected car experiences to our customers.

—Ken-ichi Murata, General Manager of BR Connected Strategy & Planning department of Toyota Motor Corporation

Although initially focused on In-Vehicle-Infotainment (IVI), the new distribution has been architected to allow different profiles to be created from the same code base to address all applications in the car, such as instrument cluster, heads up display, telematics and connected car.

Suited for deploying “smart car” navigation, communications, safety, security, and infotainment functionality, the AGL UCB distribution is supported by a broad community of participants from the automotive, communications, and semiconductor Industries as well as individual developers.

Based on the Yocto Project, a complete embedded Linux development environment with tools, metadata, and documentation, the new AGL distribution includes:

  • Complete Linux-based distribution based on Yocto Project.

  • Common IVI layer that can be shared by multiple projects (AGL, GENIVI, others).

  • Complete open source development infrastructure including Git code repositories, Gerrit code review and Jira bug and issues tracking, all hosted by the Linux Foundation.

  • Continuous integration via Jenkins.

  • Automated testing infrastructure.

  • Westin IVI shell with Wayland IVI extension (from GENIVI).

  • Support for QT multimedia and QML applications.

  • Demo applications for Home Screen, Media Browser, HVAC Control and Display, AM/FM Radio and Navigation.

  • First open source MOST device driver developed by Microchip Technology.

  • Option for both native and HTML5 applications.

The AGL distribution initially supports the following platforms, with more to be added in the coming months:

  • Renesas R-CAR M2 PORTER
  • Renesas R-CAR E2 SILK
  • Various Intel boards such as the MinnowBoard MAX
  • QEMU x86
AGL UCB, which is hosted on Linux Foundation servers and open to anyone, is available for download here.

At CES 2016, the AGL UCB will be featured as part of the GENIVI CES 2016 Demonstration Showcase in the Trump International Hotel. Demo applications for navigation, HVAC control, radio, media player and browser, settings and home screen are on display this week.

AGL has also released a White Paper that addresses Linux Security in the Connected Car.



Anything to get rid of Microsoft and Sync.  That crap isn't even courteous enough to do its rebooting for housekeeping when the car is switched off; it just goes bye-bye for a minute or so even when you need e.g. the radio or heater controls.


Better days ahead.


It remains to be seen what they do with the user interface.


SJC,This is the important bit

"The announcement of this new AGL Unified Code Base distribution is the significant first step in creating an --
-open ecosystem- based around a -common - platform -"

Suggests we should be saying WHAT WE DO, rather than what "they do" even though 'they' do say it is a first step.

But then I'm not a lawyer or legal interpreter.

E-P is already "in the loop" on creative commons.


based around a -common - platform
Linux is an operating system, not an application.


Of course,
Linux is 'an' operating system with the difference being it is the operating system or more correctly to the layperson: the 'open source' operating system of choice used by people in the creative commons community.

It supports non propriety software developers and programmers through the full range of technical and service applications.

Although propriety apps are equally possible. The option is there to lock out hackers (in the benign sense) it can also be left open for development by the hacker community.

The language used in the article is ambiguous.

References to various membership categories according (no doubt) to the level of investment.

Whether this is direct financial or in kind development is not clear.

Whether there are special privileges is also unclear.

What is clear is that linux is a versatile expansive and essentially user owned platform.
It will be able to accommodate the many tweaks and modifications that will be required and join 'seamlessly?' and integrate with existing programs as well as being familiar to the majority of programmers both private individuals as well as the largest companies currently operating.

The alternatives are really not. They would be like trying to integrate education in using imperial and metric in every possible language from english mandarin russin and 3,000 other minority and extinct versions.

It has been the future since day one.


For private developers wanting to access privileges.

I'm suggesting that there will be an ongoing demand from modifiers including small educational facilities , private tinkers requiring personalised system options, mining co's (now operate entire autonomous sites and rail networks) among others using in house (bespoke) systems, There will be demand for increasing accessibility.

Assuming that the trend towards single computer vehicles continues with area specific modular components facilitating the various user requirements, there could be sufficient demand for registering the 'unlocking'of production versions or even building a limited run of 'dual boot' optioned devices.

This would add extra cost owing to smaller production runs. The trade off between added security for production versions and versatility.

There may be a need for system authentication network providers in any case as malfunctioning and unauthorized usage would risk harm to other end users (drivers or service techs) even if not risking multiple vehicle errors to propagate.

The comments to this entry are closed.