Keynote: Building Bridges, Not Barriers: Embracing Upstream Support for Lasting...
summary
TI traces upstream work back to 2003 and says the A6 platform from five years ago forces a bigger commitment because it must support 10,000s of developers and long-lived embedded systems. The company measures success with two metrics — high-quality software and 100% Upstream — and reports moving SDKs and drivers into mainline, releasing hardware-facing tools and docs, and investing in upstream performance and safety improvements so customers get immediate, durable software support.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 0:45Why is upstream support important to TI
- 2:23What does upstream support mean for TI
- 3:38How did TI arrive at upstream support
- 5:33Open source software isnt enough
- 6:36Whats next
related talks
09mKeynote: Building Bridges, Not Barriers: Embracing Upstream Support for Lasting...
08mKeynote: Zephyr as the Foundation for a Microcontroller SDK
28mKeynote - Leading in Open Source, a Strategic Approach
36mNo, It's (Still) Never Too Late to Upstream Your Legacy Linux Based Platforms
54mSponsored Session: Creating Products with Upstream SW - Fireside Chat with TI & Friends
57mKeynote: The Demarcation of the Edge of Innovation
21mKeynote: Software Drives Hardware, lessons learned and future directions
18mKeynote: Challenges in Industrializing OSS and How Siemens Tackles Them