Automotive engineers and open source developers are talking different languages. The former are experts in their domain, understand the requirements of their companies' products but, let's be honest, have frequently been drinking their own Kool-Aid and are encumbered by the industry's “not invented here syndrome.” The latter think the automotive engineers are crazy with their stuff and don't know jack about doing software right. Ok, that's a little polarizing but you get the idea.
Let's get the two groups together in workshops and talk shop and work on solutions for certain topics that are the most pressing. The Linux Plumbers 2013 Automotive Microconference track is focusing on the key challenges on the infotainment platform. That's where the most code in the car is and where the industry needs great solutions fast.
Here are some topics that we think are important to discuss. It's not a complete nor the final list. Ideas are welcome.
Bluetooth, NFC, WiFi Direct, Connectivity
Ethernet adapted to automotive (i.e. return ground, power-over-ethernet, cable packaging)
802.11p wireless and IEEE-1609 (Wireless Access in the Vehicular Environment Short Message Protocol)
Media and document indexing, search and retrieval
CE Device Management
Automotive IVI needs to deal with different types of devices including smart phones that are connected in a special way
medical diagnostic device end systems (taken from ICU and put into ambulance)
A udev based solution leads to fragmented set of utilities
There is a need for alternative solution.
An open source version is in the works by GENIVI and will be available soon
Software updates management and platform configuration over the air. Authenticity of updates to prevent malware infiltration.
The package manager level with many megabytes large packages that only update a single file is too heavyweight; consider a variant of small linux distro, like puppylinux.
Updates need to be transactional so that they can be rolled back if something goes wrong
Updates must be secure
(Persistent) storage: filesystem, security/encryption
Service management, platform lifecycle (boot/shutdown), systemd
Location based services: Positioning, navigation, …
Graphic subsystem: Wayland, LayerManager
Vehicle data
Inter Process Communication (IPC)
Automotive engineers are used to IPC mechanisms typically found in RTOS. Do we need them in Linux?
Linux's interface to AUTOSAR protocol and FlexRay and EthernetAVB used for Electronic Control Units (ECUs).
Scheduling and
QoS in systems with both time-critical and best-effort message delivery requirements.
kernel based D-Bus: why the industry thinks they need it and why the kernel community thinks the suggested implementation AF_BUS is not the right one.
new proposals / alternative concepts from GregKH and Lennart: pros and cons, major advantages to be expected compared to AF_BUS
Alternative udev implementations, how to integrate into systemd.
Locked bootloaders, trusted platform modules, application signing in automotive
The structure will be … (defined later…)
Please propose all topics via: http://www.linuxplumbersconf.org/2013/submitting-topic/
Alison Chaiken: 802.11p wireless and IEEE-1609 network stack
Jeremiah C. Foster (jeremiah.foster AT pelagicore.com): Libudev hacking for an automotive environment (Jeremiah is the proposer, Sriram will likely hold the presentation since he's doing the work.)
Matt Jones, Rudi Streif: Changing the Automotive Industry One Bit at a Time
Imagine directly participating in the development and engineering of the next generation of your favorite vehicle make and model. Imagine working with automotive companies outside the traditional supply chain. Imagine developing cool new applications that directly interact with in-vehicle systems. Imagine designing a sophisticated user interface for in-vehicle infotainment.
Since the inception of the motor vehicle and throughout its history until today, modifying and improving their ride has inspired many enthusiasts and created a large ecosystem of suppliers, professional and hobby garages, car shows and much more. However, these efforts have been limited to aftermarket, mechanical and, to some extend, electrical modifications.
Join Matt Jones, Senior Technical Specialist at Jaguar Land Rover, and Rudi Streif, Director of Embedded Solutions at the Linux Foundation, for our vision on how opening up the software design process for in-vehicle infotainment and inviting developers and engineers around the globe to participate and collaborate in automotive open source projects will change the industry one bit at a time. We will outline how Automotive Grade Linux through making source code available, providing ready-to-run system images and documentation will enable a era of broad collaboration that extends much beyond the industry itself.
These are exciting times for hackers and car freaks alike! Come and join the revolution!
-
The non-Android fast boot topic will be part of the Boot and Core
OS topic
Richard Röjfors (richard.rojfors AT pelagicore.com) proposes a discussion on Automotive diagnostic, what is missing, where are we now, what are the next steps?
Mikael Söderberg (mikael.soderberg AT pelagicore.com) proposes a talk on Ethernet AVB in an Automotive context. What are the requirements of an ethernet AVB stack in an automobile? How would you implement it to fit with the rest of a well structured system, what is the impact on ConnMan and audio services?
Marcel Holtemann
Johannes Berg
Kay Sievers
The schedule of the 2013 Automotive Microconference Plumbers Micro Conference is as follows. Note presentation slides can be found on the Plumbers page by following the links to the abstracts:
Session 1 - Presenter 1
Session 2 - Presenter 2
etc…
This is a good place to record notes from your session. All too often, if notes were not written down, the session might as well not have happened.
