This BOF session will analyze architectural challenges migrating Chromium from the desktop to embedded devices. The impacts of different GPU libraries with their respective limitations will be discussed. We welcome audience participation in an open discussion on the V4L2 adaptation in Chromium.

1. Presented by
Date
Event
Chromium with V4L2 playback
- is it ready today?Christophe Priouzeau
BKK16-209 March 8, 2016
Linaro Connect BKK

2. Overview
● Goal:
○ hardware video acceleration on chromium for
security implementation
● Kernel interface for hardware video decode
○ V4L2
● Hardware
○ STiH410 B2120 from STMicroelectronics
○ DragonBoards from Qualcomm (96boards)

3. GPU
● STiH410 B2120
○ ARM Mali 400
■ R4p1: ST Wayland
■ R6p0:
● EGL_EXT_image_dma_buf_import
● ARM wayland
● DragonBoard
○ Mesa
■ 11.0:
● EGL_EXT_image_dma_buf_import
(Only RGB/BGR are supported)
● wayland

4. Chromium
● Challenge
○ Desktop to embedded device
○ Configuration
■ Android, Chrome OS, Linux, OS X
■ drm, egl, wayland, x11
○ Build and binary size
■ debug file are around 3.2GB
○ How to use YUV data

5. Chromium Video decode
● WebMediaPlayer interface
● Render thread, Gpu Thread
FFMPEG
VPX
VT: Video toolbox
VA Api
V4l2
Ozone
Android

6. Video Frame format for decoder
● FFMPEG
○ YV12, YV16, YV24
● Vpx
○ YV12, YV24
● V4L2
○ NV12, I420, ARGB
● VA Api
○ RGB

7. GPU video decode: way to pass video frame
● V4l2
○ eglCreateImageKHR / EGL_LINUX_DMA_BUF_EXT
○ (tegra:
eglCreateImageKHR/EGL_GL_TEXTURE_2D_KHR)
● VA api
○ x11: Texture GL_TEXTURE_2D
○ ozone: Texture GL_TEXTURE_EXTERNAL_OES
● Android
○ Texture GL_TEXTURE_EXTERNAL_OES

8. Open Discussion

9. Thanks