Using Yocto as a Method to Upstream, Maintain, and Track Patches
summary
Uses Yocto to turn a vendor tarball and ancient kernel (4.4 from 2016) into a bootable image by committing sources to git, writing kernel/u-boot recipes and a meta layer, and extracting binaries into the image when sources are missing. Migrates to generic upstream trees with git rebase (hundreds of vendor commits squashed then split), tracks changes with git-send-email, and publishes the layer to OE layer index; result is a reproducible distro and a patch queue that progressively shrinks as patches land.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:18Problem
- 2:24Get it working under Yocto
- 3:25Write recipes
- 6:01Linux kernel recipe
- 7:44Verify bootable image is created
- 7:56Migrate to generic sources
- 8:15Updating u-boot recipe (example)
- 10:51Updating kernel recipe
- 11:59Split into patches
- 13:07Upstreaming Process
- 16:09Using Yocto to Track patches
- 17:11Using Yocta to maintain
related talks
45mBuilding and Maintaining Binary Distributions with Yocto
53mReal-World Yocto: Getting the Most out of Your Build System
32mSoftware Supply Chain with the Yocto Project
38mkernel: build system outputs and workflows (and how to balance them)
39mYocto Project: 5 Year Plan, Now What?
01h 00mOpen Software Updates for IoT
50mUsing the Yocto Autobuilder for Build and Release Management
30mStrategies for Developing and Deploying your Embedded Applications and Images