Sponsored Session: Creating Products with Upstream SW - Fireside Chat with TI & Friends
summary
European CRA forces products to ship recent software or face up to 2.5% global revenue fines and strict 24/72/30-day CRA deadlines for vulnerability reporting, so vendors push upstream-first kernels and continuous updates. Silicon vendors run kernel CI and publish CI/CD board-farm logs and SDK test reports (LAVA, Yocto/“Yakto” builds) to prove regressions are caught; some chips (AM65/AM64) are already mainline supported, but gaps remain in bootloader, graphics and power features.
AI-written summary · about
chapters (8)
- 0:00Welcome
- 3:12Cyber Resilience Act impact
- 13:52Upstream kernel support importance
- 25:52Testing vendor vs upstream kernels
- 33:15Security testing and CVE handling
- 41:20Yakto’s upstream vs downstream role
- 44:10TI silicon for open-source
- 47:47Closing and Q&A
related talks
45mBOF: Corporate Use of Embedded Linux
09mKeynote: Building Bridges, Not Barriers: Embracing Upstream Support for Lasting...
24mThe CRA Challenge: Can Open Source and IoT Stay Agile Under Regulation?
09mKeynote: Building Bridges, Not Barriers: Embracing Upstream Support for Lasting...
45mCollaboration Breakfast
26mFrom Tapeouts to Products: Why Open-Source Silicon Must Solve Real Problems to Survive
43mSponsored Session: Why Don't You Love Me Back, Open-source Software?
14mWill the CRA Break Open Source in IoT — or Make It Stronger?
