OSS + ELC EU 2026

Modern SoCs have a variety of CPU cores on board - e.g. on ARM we often see Cortex A, plus Cortex M, plus System Controllers. The number of cores is as increasing as the demands. Concepts like 'Software Defined Vehicle' (SDV) from the automotive sector is just one example for such complex demands. One obvious requirement is to run other OS than Linux on dedicated cores. Which means that resources like memory, clocks, pin control, power domains, etc. may not be under the sole control of Linux anymore. They now need to be shared and synchronized between all the participants. How does this work in practice? How do technologies like remoteproc, rpmsg, mailboxes, hardware spinlocks, virtio, and devicetree come into play here? How is their status-quo? And what about the non-Linux sides? What is open, what is proprietary, and how does this affect actual solutions? This talk is the result of a journey trying to support LinuxZephyr based AMP using a complete FreeSoftware stack on a Renesas community board.

All active components require power. The device tree should properly describe these supplies so that the software can control power to the devices. On the other side of things, regulators also have their power inputs, and constraints on their power outputs. The device tree should also describe this. Nothing should be left to default.

This session will present how to fully describe the regulator tree of a system, how to identify missing bits, and how to properly describe regulator constraints.

AI agents are evolving from simple chatbots to coordinated systems that plan, collaborate, and execute real-world tasks. But moving from a working prototype to a production-grade multi-agent system is where most teams struggle.

In this session, two practitioners share battle-tested patterns from deploying agent swarms in industrial environments. We cover:
The architectural shift from single-agent to multi-agent: when and why you need a swarm
Comparing open source frameworks (LangChain, AutoGen, Strands Agents SDK) — strengths, trade-offs, and selection criteria
Practical orchestration patterns: task delegation, shared memory, tool coordination via MCP (Model Context Protocol)
Live demo: building a multi-agent system that collaborates to solve a real task
Safety-first design: guardrails, execution boundaries, and observability for production
Attendees will leave with a reusable architectural blueprint applicable to any open source agent framework.