The Salmon Diet: Up-Streaming Drivers as a Form of Optimization
summary
Up-streaming an existing out‑of‑tree Arm CryptoCell driver into the kernel yields concrete quality gains: iterative community review and use of kernel APIs and tools such as checkpatch and the staging tree remove redundant, wrong or legacy code, eliminate macro layers and dead auto‑generated register blobs, and simplify backward‑compat handling via backporting. The driver shrinks as reviews land, ending with 30% fewer lines while preserving functionality and reducing bugs, and the upstreamed driver is accepted into the crypto tree.
AI-written summary · about
chapters (6)
- 0:00Start
- 13:09Reinventing the wheel
- 16:21Backwards compatibility
- 26:59Duct Tape Engineering
- 31:01Macro Gymnastics
- 34:19Zombie Code
related talks
32mHow (Not) to Get the Vendor Driver Merged Upstream
45mBOF: Corporate Use of Embedded Linux
36mNo, It's (Still) Never Too Late to Upstream Your Legacy Linux Based Platforms- 36mNo, It's (Still) Never Too Late to Upstream Your Legacy Linux Based Platforms
36mNo, It's Never Too Late to Upstream Your Legacy Linux Based Platform- 32mHow (Not) to Get the Vendor Driver Merged Upstream
54mSponsored Session: Creating Products with Upstream SW - Fireside Chat with TI & Friends
43mSponsored Session: Why Don't You Love Me Back, Open-source Software?