Jeremiah C. Foster

What is the "safety-critical" domain? What challenges does it present to Free Software with regard to process? Can FOSS become "safety-critical"? What are the implications of using copyleft licenses in safety-critical software? What is the roadmap? What resources to engage in the discussion is available?

I will try and have a short presentation on what safety-critical software is, where its used, and why its important that software freedom is part of the domain. I will discuss some concrete results towards a GNU/Linux software stack that may be a candidate for certification for safety-critical use. Lastly, I'd like very much to engage the audience on the subject matter, particularly on the dynamic of copyleft and how it may provide a greater level of transparency than proprietary software not just into the actual code but in the entire process and supply chain and hardware. Copyleft may be an effective mechanism to ensure a necessary level of transparency as well as adequate protection for source cod e that is expensive to produce and maintain.

There are now two major organizations developing automotive FOSS software and a third may be contributing as well. This means there is lots of automotive software available and now its able to run on cheap, available hardware like the Raspberry Pi.

This talk will take us through the available FOSS software stacks that are available for automotive. This last year has produced a lot of working software from fiber-optic networking drivers in the Linux kernel, complete In-Vehicle Infotainment stacks, to a newly released Qt Automotive. There has also been a change in available hardware to run this software on, new boards like the Minnowboard Max, Renesas' Porter board, and even the Raspberry Pi 2. This talk will try and cover the entire software ecosystem and how it matches to hardware, how you can get involved today, and what the future holds.

A quick overview of the state of Open Source Automotive software.

There are a number of initiatives around Open Source automotive software. In this short introduction we will take a look at them and the projects which are part of them. The Automotive devroom will also dig deeper into a number of areas: In-vehicle Infotainment, autonomous driving, automotive networks, and graphical interfaces in both "native" and HTML 5.

Safety Critical Devices.

We rely on software more and more for critical functionality in our society. Medical Devices and Cars are two areas where our lives literally depend on the safety of this software. As more exploits are demonstrated on cars, pacemakers and insulin pumps that show them to be vulnerable, the industries are evaluating their technology and some are advocating for free software as partial solution to these problems. This panel will discuss free software in Safety critical devices. including the implications of different licenses, issues regarding warranties and indemnities and liability issues for manufacturers The panel will discuss automotive and medical devices and consider regulatory issues.

Other people: Karen Sandler John Sullivan Amanda Brock

This talk describes how the automotive industry has moved to embedded Linux and Open Source to develop the next generation of In-Vehicle Infotainment (IVI) and how it has met the challenges along the way.

This talk describes how the automotive industry has moved to embedded Linux and Open Source to develop the next generation of In-Vehicle Infotainment (IVI). IVI is increasingly important as everyone wants to be connected all the time and cars are no exception. Cars are a natural fit for modern mobility software and customers expect that nearly anything they purchase nowadays has smart mobility baked in.

How does it happen that an industry known for its mechanical engineering and cautious approach can suddenly become a leader in smart mobility? How can the auto industry jump over a generation of consumer electronics and right into the smart phone era?

One approach is to join together, create a common platform, and innovate on top. This is what the GENIVI alliance has done. That common platform is embedded Linux and it comes with a number of challenges for the automotive industry. License compliance, fast start-up times, mobile connectivity to the internet, interaction with a wide variety of cell phones; all these things are challenges that the GENIVI alliance has tried to tackle head on.

We'll discuss some the technical solutions, the resultant software stack, and the work that still needs to be done to realize modern IVI in every car.