96Boards CE Software Compliance - How and Why it is needed?
summary
New 96Boards CE software compliance defines concrete requirements and a quarterly upstreaming roadmap: Q1 basic SOC patches, Q2 onboard storage and distro boot, Q3 kernel and bootloader upstreaming, Q4 full display and audio support. Mandatory items include boot recovery tools (JTAG or vendor tool), recent longterm stable kernels (last three releases) with bootloader source, and documentation; recommended items include EBBR/UEFI and GPU acceleration. Vendors must post patches, add board support to the mraa library, and provide graphics drivers within four weeks of major kernel releases.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:5696Boards CE Software Compliance - How and Why it is needed?
- 7:15Board Recovery • Possible to recover a "bricked" board Without specialized hardware like JTAG debugger • Open or proprietary SW tools can be used
- 17:16Objective: On-board memory support • Outcome: Board should boot a distro with mainline kernel from any one of the on-board storage mediums (eMMC, UFS, USD, USB, PCI-E Flash) • Subsystems to be covered: Regulators
- 18:29Objective: On board display and full bootloader support ⚫ Outcome: Board should drive any on-board display interface (HDMI, LCD) with any means of audio out (HDMI, LS-12S)
related talks
39mEBBR: Standard Boot for Embedded Platforms
54mSponsored Session: Creating Products with Upstream SW - Fireside Chat with TI & Friends
40mWorking with the Community: A Timeline for Adding Support for a New Board in Zephyr
55mThe Embedded Linux Problem
03mIntroduction
40mWorking with the Community: A Timeline for Adding Support for a New Board in Zephyr
43mSponsored Session: Why Don't You Love Me Back, Open-source Software?
45mBOF: Corporate Use of Embedded Linux