Establishing a Software-Defined Multi-Display Framework with Unified HMI
summary
Open-source Unified HMI claims to separate display software from hardware by streaming GPU command streams over IP so a single RBGPU proxy and RB GPU lender pair can render apps on remote ECUs. It pairs that with a distributed display framework (DDFW) that maps multiple physical displays into one virtual surface, controlled via virtual screen JSON files and Wayland/Weston tools. Verified on x86, Raspberry Pi and reference boards, it runs apps across displays, syncs via command replay, and is network-bandwidth bound but functionally working.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:49Unified HMI necessity
- 4:43Automotive display trends
- 5:50Software-defined unified HMI
- 6:36Value of unified HMI
- 8:02Unified HMI framework
- 15:48Unified HMI on AGL UCB
- 24:50Verification procedure summary
- 25:10Future vision for HMI
- 27:59Q&A
- 32:02Future zonal architecture
- 34:17Network requirements
- 38:37Bandwidth and support
- 40:03Closing
related talks
26mUnified HMI v2.0: Platform-Agnostic Architecture and Unified APIs for Multi-Display...
34mServer Driven UIs: the future of cross-platform rendering
34mA conceptual future for the multi-device web
34mFunctional UIs and Unidirectional Dataflow
43mMulti-screen development with QtQuick
27mModern 3D user interface design with Qt Quick
43mReproducible Multi Element System Composition with Linux, Xen & Zephyr
29mServer Driven UI (BFF)