What Small Teams Should Know when Building Embedded Linux Systems
Talkat Embedded Linux Conference + OpenIoT Summit North America 2017 · on Wednesday, 2017-02-22· at 16:20· Grand Ballroom I/II·
summary
Small teams building embedded Linux use vendor SDKs and reference boards, then record deltas, update device trees and add drivers; Virgin Galactic uses OpenEmbedded/Yocto with a private layer to port forward updates and report large time savings. Maintain a separate downstream kernel git tree for added drivers, run CI with local mirrors and package repos (TFTP/apt/rpm) for fast deploys, enforce version control and code review, and upstream fixes to cut long‑term maintenance.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:34Where do you start?
- 4:00Vendor-provided SDK (and/or BSP)
- 8:19Things to watch for
- 12:04Keep track of the differences, and note impact on project
- 13:51Work with the visible derivations, note differences
- 14:47Figure out what you'll need to update
- 18:16Finally, integrate your application
- 22:51Why is upstreaming important? (aka how do I convince my boss?)
- 25:24Build system tips
- 29:39Summary
related talks
30mStrategies for Developing and Deploying your Embedded Applications and Images
38mkernel: build system outputs and workflows (and how to balance them)
37mContinuous Delivery for Embedded Systems
45mSoftware Updates for Connected Devices: Key Considerations
49mThe 5 Key Success Factors to Deploy Yocto for “Production Grade” Embedded/IoT Devices
31mDebian or Yocto Project? Which is the Best for your Embedded Linux Project?
49mLong-Term Maintenance, or How to (Mis-)Manage Embedded Systems for 10+ Years
41mYocto or Debian for Your Embedded System? Yes.