Jan Kiszka

The nature of embedded devices is that they are generally hiding from their users. This is even more true for those that are part of our critical infrastructure. Therefore it is rarely publicly known what is actually running inside. At Siemens, we are developing a broad portfolio of such devices. A lot of them are using Linux these days - and an many of those are now Debian-based. In this talk, we will try to lift the curtains a bit and present some Debian-based product examples, from small IoT gateways up magnetic resonance imaging solutions. We will talk about why Debian was chosen, how it is being integrated and maintained, what our engineers are happy about and where they see room for improvements. Furthermore, we will talk about which contributions to the Debian ecosystem evolved out of this already and how we want to do more.

Debian has a long history in embedded usage. But today many people first think of Yocto when it comes to embedded Linux. The reasons are not only related to the countless Yocto-based board support packages on the market. There are benefits over standard distributions. However, if you step back from the messy details you easily run into when doing this for profit, you may wonder: "Do I really need to build EVERYTHING from scratch when the degree of customization gets less and less?" Combining the best of both worlds is the goal of the Isar image build system: a huge pool of pre-built, well tested, long maintained Debian packages with the flexibility and reusability of image descriptions via bitbake and Yocto-like layers. In this talk, we will provide an introduction to this approach, explaining the motivation based on first industrial application scenario. When does it take more than a simple bootstrap script while building product images? We will furthermore point out why we were specifically choosing Debian as foundation, and were we see a place of this approach and its tooling inside Debian, embedded and maybe also beyond.

Other people: Baurzhan Ismagulov

This talk will introduce the architecture of Jailhouse, describe typical use cases, demonstrate the development progress on a target system and sketch the project road map.

The Jailhouse project provides a minimal-sized hypervisor for running demanding real-time, safety or security workloads on fully isolated CPU cores aside Linux. In contrast to other commercial and open source hypervisors of similar scope, it is booted and managed via a standard Linux system. Its focus is on keeping the core code base as small as feasible, generally trading simplicity over features.

Jailhouse has been released under GPLv2 and is being developed in an open manner. The talks aims at attracting further users and contributors, specifically from the embedded domain, but may also trigger discussions about additional use cases.

• motivation & use cases
• architecture and design principles
• current state
• short demonstration
• outlook