Step by Step, What Should We Do for the Kernel Ecosystem?
summary
Linux kernel LTS support shifts to a two-year LTS projected EOL, forcing embedded teams to either keep many branches (examples: 5.15, 4.9, 4.4, even 2.x) or accelerate upgrades. A Japan study group called Linux Kernel LTS Study Group catalogs pain points: testing cost, compatibility with BSP/vendor trees, secret binary blobs, and branch management. Practical actions are run upstream-aligned kernel test suites (use KiDev and kernel test frameworks), backport fixes from mainline to LTS, and join CIP LTS working group.
AI-written summary · about
chapters (9)
- 0:00Linux kernel ecosystem proposal
- 3:17Linux kernel release models
- 7:15LTS kernel timelines changes
- 9:30Long-term kernel maintenance challenges
- 10:59LTS sustainability in Japan
- 21:44In-house developer key issues
- 35:30Contributing to kernel ecosystem
- 41:27Sustainable kernel development call
- 43:15Q&A on kernel compliance
related talks
43mUsing Linux as Long Term Working with the Community
36mStatus of Embedded Linux
27mActivities of Super Long Term Support Kernel Workgroup in Civil Infrastructure Platform Project
24mKeynote: The Kernel Report
21mCommunities, Enterprises and All the Rest
51mPanel Discussion: Industrial Linux Beyond 2022
45mBOF: Corporate Use of Embedded Linux
36mNo, It's (Still) Never Too Late to Upstream Your Legacy Linux Based Platforms