<?xml version='1.0' encoding='utf-8' ?>
<!-- Made with love by pretalx v2026.1.1. -->
<schedule>
    <generator name="pretalx" version="2026.1.1" />
    <version>0.6</version>
    <conference>
        <title>Yocto Project Workshop at Embedded Recipes 2026</title>
        <acronym>yocto-embedded-recipes-2026</acronym>
        <start>2026-05-29</start>
        <end>2026-05-29</end>
        <days>1</days>
        <timeslot_duration>00:05</timeslot_duration>
        <base_url>https://pretalx.com</base_url>
        
        <time_zone_name>Europe/Paris</time_zone_name>
        
        
    </conference>
    <day index='1' date='2026-05-29' start='2026-05-29T04:00:00+02:00' end='2026-05-30T03:59:00+02:00'>
        <room name='Mistral' guid='921bda50-8268-5df6-b7ef-d5b457211f91'>
            <event guid='0100173f-341e-51a2-90bc-4024b8dc5bcb' id='95609' code='DLFBCL'>
                <room>Mistral</room>
                <title>Good morning and welcome</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-05-29T09:00:00+02:00</date>
                <start>09:00</start>
                <duration>00:20</duration>
                <abstract>In which we will welcome all attendees and kick off the day!</abstract>
                <slug>yocto-embedded-recipes-2026-95609-good-morning-and-welcome</slug>
                <track></track>
                
                <persons>
                    <person id='99005'>Josef Holzmayr</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://pretalx.com/yocto-embedded-recipes-2026/talk/DLFBCL/</url>
                <feedback_url>https://pretalx.com/yocto-embedded-recipes-2026/talk/DLFBCL/feedback/</feedback_url>
            </event>
            <event guid='87e447f9-eabd-5dba-90d2-c58a5f8861cd' id='95008' code='FABH7C'>
                <room>Mistral</room>
                <title>meta-riscv: current status and call for contributions</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-05-29T09:20:00+02:00</date>
                <start>09:20</start>
                <duration>00:30</duration>
                <abstract>Learn about the meta-riscv layer, its achievements, its lessons learned, its limitations and how you can help.</abstract>
                <slug>yocto-embedded-recipes-2026-95008-meta-riscv-current-status-and-call-for-contributions</slug>
                <track></track>
                
                <persons>
                    <person id='94761'>Michael Opdenacker</person>
                </persons>
                <language>en</language>
                <description>The RISC-V architecture is now officially supported by the Yocto project, but like on most other architectures, OpenEmbedded Core only supports emulated QEMU targets. Support for real hardware boards is brought by the &quot;meta-riscv&quot; layer.

Since his first contributions to the layer in October 2025, Michael Opdenacker has contributed to the addition of new boards, expanding or updating support for existing ones, and seen similar contributions from others too.

This talk will cover the current status of &quot;meta-riscv&quot; in terms of board support, the challenges faced, and the lessons learned maintaining a layer supporting different SoCs at the same time (unlike what happens in the ARM world). It will also highlight multiple areas in which further contributions are needed.

Even though the layer was created in 2017, it can still be considered as young, as it targets a booming hardware architecture, and offers many opportunities to get involved, for all levels of experience. In particular, if you have never contributed to Yocto, it&apos;s a perfect place to get started. New code doesn&apos;t have to be perfect to be accepted, and what matters is to make progress together.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://pretalx.com/yocto-embedded-recipes-2026/talk/FABH7C/</url>
                <feedback_url>https://pretalx.com/yocto-embedded-recipes-2026/talk/FABH7C/feedback/</feedback_url>
            </event>
            <event guid='c797532d-ff05-5244-abc6-556e6828f82f' id='95374' code='9G3V3D'>
                <room>Mistral</room>
                <title>Building a Security-Hardened Raspberry Pi Image with Yocto: From Secure Boot to Secure Applications</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-05-29T09:50:00+02:00</date>
                <start>09:50</start>
                <duration>00:30</duration>
                <abstract>This talk presents meta-raspberrypi-secure, an open-source Yocto layer that turns a  Raspberry Pi 4/5 into a production-grade security-hardened platform. 
We walk through a defense-in-depth architecture built entirely with OpenEmbedded tooling covering secure boot with signed boot images, Dmcrypt full-disk encryption with hardware-bound key derivation, IMA/EVM file integrity enforcement, dm-verity, kernel module signing, A/B atomic updates and kernel hardening options all with a single kas build command.</abstract>
                <slug>yocto-embedded-recipes-2026-95374-building-a-security-hardened-raspberry-pi-image-with-yocto-from-secure-boot-to-secure-applications</slug>
                <track></track>
                
                <persons>
                    <person id='95062'>Ayoub Zaki</person>
                </persons>
                <language>en</language>
                <description>We will cover:

* Secure boot: signing boot images with RSA-2048 and provisioning the RPi EEPROM
* Full-disk encryption : Dmcrypt with hardware-bound key derivation (OTP HMAC), including in-place first-boot encryption.
* System integrity using AVB dm-verity and IMA/EVM 
* OS hardening: kernel lockdown, firewall, USBGuard, audit rules, hardened mounts, and SSH certificate authority support
* **dev** vs. **prod** security profiles managing security posture from a single layer configuration
The talk includes a live demo on a Raspberry Pi 5 and closes with guidance on adapting the layer for your own rpi based products.

Target audience: Yocto/OE developers and BSP engineers interested in practical embedded Linux security.

[1] https://github.com/embetrix/meta-raspberrypi-secure</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://pretalx.com/media/yocto-embedded-recipes-2026/submissions/9G3V3D/resources/meta-raspberrypi-secure-10_4RvbQVD.pdf">Presentation</attachment>
                </attachments>

                <url>https://pretalx.com/yocto-embedded-recipes-2026/talk/9G3V3D/</url>
                <feedback_url>https://pretalx.com/yocto-embedded-recipes-2026/talk/9G3V3D/feedback/</feedback_url>
            </event>
            <event guid='7376263d-d738-5188-b042-52b63a351d9c' id='95581' code='UTZAZQ'>
                <room>Mistral</room>
                <title>Megan&apos;s polling</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-05-29T10:35:00+02:00</date>
                <start>10:35</start>
                <duration>00:20</duration>
                <abstract>Megan will survey the participants for pain points, and for tools that they love and others they would like to go.
She will also share the actions that were taken and project items that got support thanks to feedback from earlier surveys.
Your opportunity to speak up as a user or contributor!</abstract>
                <slug>yocto-embedded-recipes-2026-95581-megan-s-polling</slug>
                <track></track>
                
                <persons>
                    <person id='92541'>Megan Knight</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://pretalx.com/yocto-embedded-recipes-2026/talk/UTZAZQ/</url>
                <feedback_url>https://pretalx.com/yocto-embedded-recipes-2026/talk/UTZAZQ/feedback/</feedback_url>
            </event>
            <event guid='c9c601f3-fd11-5d54-995d-b2dc52a51e56' id='92266' code='CRHTUM'>
                <room>Mistral</room>
                <title>Creating Yocto Project Compatible layers</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-05-29T10:55:00+02:00</date>
                <start>10:55</start>
                <duration>00:30</duration>
                <abstract>One of the key benefits of the Yocto Project is the ecosystem of layers providing reusable hardware support, software packages and configuration policy - saving you the work of re-implementing everything from scratch yourself. But with many layers available, there is an almost uncountable number of different combinations of layers that may be encountered in a Yocto Project build. The challenge is - how do we ensure that these different combinations will work as expected?

The Yocto Project Compatible program and the `yocto-check-layer` script have been created to address this challenge. By following best practices and testing the compatibility of your layers, you can ensure that they work well in combination with the rest of the Yocto Project ecosystem.</abstract>
                <slug>yocto-embedded-recipes-2026-92266-creating-yocto-project-compatible-layers</slug>
                <track></track>
                
                <persons>
                    <person id='92500'>Paul Barker</person>
                </persons>
                <language>en</language>
                <description>This talk will introduce the Yocto Project Compatible v3 program and the requirements for achieving Compatible status. It will explain how to run the `yocto-check-layer` scripts to test different types of layer and how best to automate this test within a CI/Autobuild system. Best practices to ensure layer compatibility will be discussed, building on my &quot;Creating Friendly Layers&quot; talks from past Yocto Project summits. The talk will finish with conclusions and future work which may be expected in these areas.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://pretalx.com/yocto-embedded-recipes-2026/talk/CRHTUM/</url>
                <feedback_url>https://pretalx.com/yocto-embedded-recipes-2026/talk/CRHTUM/feedback/</feedback_url>
            </event>
            <event guid='9a559bfe-882e-5396-898d-557b222db314' id='95233' code='XJGTFB'>
                <room>Mistral</room>
                <title>Beyond the Release: Managing Long-Term Risk and Compliance in Embedded Linux with Yocto</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-05-29T11:40:00+02:00</date>
                <start>11:40</start>
                <duration>00:30</duration>
                <abstract>The embedded systems of the future will be judged by their long-term resilience and security. For many manufacturers, however, the shift from a product release to continuous lifecycle management is a significant operational hurdle. Regulations like the EU&apos;s Cyber Resilience Act (CRA) are formalizing this challenge, demanding ongoing vulnerability management and creating a backdraft of responsibility that impacts the entire supply chain.

This presentation highlights that a robust and reproducible build system is the cornerstone of any sustainable product strategy in this new environment. It will explore how the Yocto Project provides the essential framework for building future-proof and maintainable systems. The discussion will cover how its architecture enables the critical features needed to manage long-term risk: full-stack patchability for targeted CVE fixes, reproducible builds for maintaining legacy devices, and automated Software Bill of Materials (SBOM) generation for regulatory transparency.
Attendees will gain actionable strategies for implementing lifecycle-aware embedded development and transforming existing product portfolios to meet evolving regulatory requirements.</abstract>
                <slug>yocto-embedded-recipes-2026-95233-beyond-the-release-managing-long-term-risk-and-compliance-in-embedded-linux-with-yocto</slug>
                <track></track>
                
                <persons>
                    <person id='94924'>Anna-Lena Marx</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://pretalx.com/media/yocto-embedded-recipes-2026/submissions/XJGTFB/resources/2026_Beyond-the-Release-Reviewe_rPdwx4P.pdf">Slides</attachment>
                </attachments>

                <url>https://pretalx.com/yocto-embedded-recipes-2026/talk/XJGTFB/</url>
                <feedback_url>https://pretalx.com/yocto-embedded-recipes-2026/talk/XJGTFB/feedback/</feedback_url>
            </event>
            <event guid='93de53ec-6986-5aec-92cd-383b948fffca' id='94800' code='89DDPP'>
                <room>Mistral</room>
                <title>From source to hardware: Hands off continuous integration to hardware</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-05-29T12:10:00+02:00</date>
                <start>12:10</start>
                <duration>00:30</duration>
                <abstract>Over the years, I&apos;ve been working on automating as much testing as possible for GNURadio based images for various pieces of hardware. This is a fairly complex application with many dependencies so there are many sources of potential failure.  This talk shows how to automate the build and test process.</abstract>
                <slug>yocto-embedded-recipes-2026-94800-from-source-to-hardware-hands-off-continuous-integration-to-hardware</slug>
                <track></track>
                
                <persons>
                    <person id='94601'>Philip Balister</person>
                </persons>
                <language>en</language>
                <description>Testing the final product helps protect against regressions in the software stack. Testing strategies evolved from manual tests, to Jenkins and qemu, and finally to gitlab ci and on hardware testing. This talk focuses on using gitlab CI and labgrid to build and test images on real hardware without any manual steps.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments>
                    <attachment href="https://pretalx.com/media/yocto-embedded-recipes-2026/submissions/89DDPP/resources/lg-ci_LbciPJT.pdf">Slides</attachment>
                </attachments>

                <url>https://pretalx.com/yocto-embedded-recipes-2026/talk/89DDPP/</url>
                <feedback_url>https://pretalx.com/yocto-embedded-recipes-2026/talk/89DDPP/feedback/</feedback_url>
            </event>
            <event guid='cbc1e163-c31b-566b-a3de-5987aaa09dbf' id='94623' code='39YTU9'>
                <room>Mistral</room>
                <title>Config Fragments: Cure or Curse?</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-05-29T13:55:00+02:00</date>
                <start>13:55</start>
                <duration>00:30</duration>
                <abstract>We build the kernel so systems behave predictably. For most servers, desktops, and laptops, the default architecture defconfig is &#8220;good enough.&#8221; Embedded boards and mobile devices are different: they often rely on device-specific configuration fragments maintained out-of-tree, and even a &#8220;close-to-mainline&#8221; kernel can require a bespoke fragment just to boot reliably. Meanwhile, selecting a mainline kernel with &#8220;similar&#8221; support frequently yields only partially working hardware.</abstract>
                <slug>yocto-embedded-recipes-2026-94623-config-fragments-cure-or-curse</slug>
                <track></track>
                
                <persons>
                    <person id='94414'>David Heidelberg</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://pretalx.com/yocto-embedded-recipes-2026/talk/39YTU9/</url>
                <feedback_url>https://pretalx.com/yocto-embedded-recipes-2026/talk/39YTU9/feedback/</feedback_url>
            </event>
            <event guid='124403c3-035a-5f53-a101-a4675d59679e' id='95018' code='SJ7KDU'>
                <room>Mistral</room>
                <title>The case for the APK package format</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-05-29T14:25:00+02:00</date>
                <start>14:25</start>
                <duration>00:30</duration>
                <abstract>This presentation tries to make the case to add APK to eventually remove IPK/OPKG from Openembedded.</abstract>
                <slug>yocto-embedded-recipes-2026-95018-the-case-for-the-apk-package-format</slug>
                <track></track>
                
                <persons>
                    <person id='94766'>Rouven Czerwinski</person>
                </persons>
                <language>en</language>
                <description>Openembedded Core currently supports several package archive formats:
- DEB created by debian
- RPM created by Red Hat
- IPK from NSLU2 Optware

Both DEB and RPM are well supported by their respective communities, while the IPK format is supported nowadays by the opkg package manager. The opkg package manager however is not that well supported any more. The OpenWRT project which heavily used opkg before has since moved on to use the Alpine Linux Package Keeper (APK) format.

This talk explores the existing package manager integration within OE core and will try to provide an initial investigation on how to add APK to Openembedded Core.</description>
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://pretalx.com/yocto-embedded-recipes-2026/talk/SJ7KDU/</url>
                <feedback_url>https://pretalx.com/yocto-embedded-recipes-2026/talk/SJ7KDU/feedback/</feedback_url>
            </event>
            <event guid='73a55d5e-2a7d-5151-abad-2c6d0d3fcabf' id='95357' code='QFK9UH'>
                <room>Mistral</room>
                <title>Securing the Software Supply Chain: Automated SBOM Signing in Yocto</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-05-29T15:10:00+02:00</date>
                <start>15:10</start>
                <duration>00:30</duration>
                <abstract>The EU Cyber Resilience Act (CRA) and U.S. Executive Order 14028 have transformed Software Bills of Materials (SBOMs) from optional documentation into mandatory
compliance artifacts. However, most Yocto-based projects generate SBOMs without cryptographic signatures, leaving them vulnerable to tampering to bypass security
reviews. An unsigned SBOM provides transparency but not integrity or authenticity.

This talk introduces a drop-in Yocto layer that automatically signs every generated SBOM using Cosign (from the Sigstore project) and enables
downstream users, customers, and auditors to cryptographically verify SBOM authenticity. Developers simply add the layer and configure a signing key
every image build then produces a signed SBOM alongside standard artifacts. 

The solution integrates seamlessly with existing workflows and requires no changes to application code.

Attendees will learn how to implement end-to-end SBOM signing in their Yocto projects and provide customers with
cryptographic proof that their SBOMs are authentic and unmodified.</abstract>
                <slug>yocto-embedded-recipes-2026-95357-securing-the-software-supply-chain-automated-sbom-signing-in-yocto</slug>
                <track></track>
                
                <persons>
                    <person id='95045'>Yogesh Hegde</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://pretalx.com/yocto-embedded-recipes-2026/talk/QFK9UH/</url>
                <feedback_url>https://pretalx.com/yocto-embedded-recipes-2026/talk/QFK9UH/feedback/</feedback_url>
            </event>
            <event guid='4bdbe68e-fae7-5ed8-87da-238cc80f2268' id='95342' code='C7M9PZ'>
                <room>Mistral</room>
                <title>Automatically updating stable releases with Auto Upgrade Helper and meta-binaryaudit</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-05-29T15:40:00+02:00</date>
                <start>15:40</start>
                <duration>00:30</duration>
                <abstract>The world is focusing more on secure systems. When maintaining a Linux distribution, there is a challenge between stability and security corrections. While released versions must not break backward compatibility, they must remain secure. Some components provide patch releases but sometimes they add features that break things.
This talk presents the latest changes that we made to enable Yocto Auto Upgrade Helper [1] to be compatible with Yocto Scarthgap LTS, update patched versions automatically, and add changelog information. Then in combination with the update on the layer meta-binaryaudit [2], we can validate that the version upgrade does not have any ABI changes and therefore be backward compatible.
This combination can allow the Yocto Project or distributions teams to update components more frequently on stable branches and be more secure but backward compatible.
References:
[1] https://git.yoctoproject.org/auto-upgrade-helper/
[2] https://github.com/Nordix/meta-binaryaudit/</abstract>
                <slug>yocto-embedded-recipes-2026-95342-automatically-updating-stable-releases-with-auto-upgrade-helper-and-meta-binaryaudit</slug>
                <track></track>
                
                <persons>
                    <person id='95031'>Daniel Turull</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://pretalx.com/yocto-embedded-recipes-2026/talk/C7M9PZ/</url>
                <feedback_url>https://pretalx.com/yocto-embedded-recipes-2026/talk/C7M9PZ/feedback/</feedback_url>
            </event>
            <event guid='b836d132-25d1-5e1a-8366-1506756db74f' id='95463' code='M9AX7Q'>
                <room>Mistral</room>
                <title>How to not maintain a BSP Layer</title>
                <subtitle></subtitle>
                <type>Talk</type>
                <date>2026-05-29T16:10:00+02:00</date>
                <start>16:10</start>
                <duration>00:30</duration>
                <abstract>We all know meta-st-stm32mp and we already covered how it is developed and how we can optimize it for a specific project use. Recently in the scarthgap-r3 release of ST, lot has changed and no backward-compatibility is now available. This talk is about the bad practices of maintaining a BSP layer and how we should always do not forget about the community expectations.</abstract>
                <slug>yocto-embedded-recipes-2026-95463-how-to-not-maintain-a-bsp-layer</slug>
                <track></track>
                
                <persons>
                    <person id='95154'>Talel BELHAJSALEM</person>
                </persons>
                <language>en</language>
                
                <recording>
                    <license></license>
                    <optout>false</optout>
                </recording>
                <links></links>
                <attachments></attachments>

                <url>https://pretalx.com/yocto-embedded-recipes-2026/talk/M9AX7Q/</url>
                <feedback_url>https://pretalx.com/yocto-embedded-recipes-2026/talk/M9AX7Q/feedback/</feedback_url>
            </event>
            
        </room>
        
    </day>
    
</schedule>
