#X11 video output xcb download 1080p
#X11 video output xcb download driver
#X11 video output xcb download Patch
#X11 video output xcb download code

Specifying the right nodes when another V4L2 driver is loaded:.

Decoding frames as fast as possible in a loop:.

Decoding frames at 25 fps in a loop, with information:.

V4l2-request-test usage is displayed when the tool is called with the -h argument.Д®xamples of v4l2-request-test use include: More presets can be added from the data dumped with libva-dump. The tool currently contains a single preset with slices that allow decoding the first 25 frames of the sample MPEG2 Big Buck Bunny video. Since the tool uses the DRM KMS device directly, no graphical session (not even a login manager) must be running concurrently. V4l2-request-test is preferably used from its repository directory: the default path to the video slices is relative from the root of the repository. Vlc -no-audio -no-autoscale -no-osd -play-and-exit path/to/video.mpeg

Remote testing without audio, scaling and OSD:.

Here are some examples of VLC usage for specific use cases: While OpenGL video output might be supported (with GPU support installed), it was not tested at this point.ДЄlthough VLC has been configured to use VAAPI for video decoding, libVA must be instructed to use libva-v4l2-request through the LIBVA_DRIVER_NAME environment variableВ :

Tools > Preferences > Video > Display > Output > X11 video output (XCB).

Tools > Preferences > Input / Codecs > Codecs > Hardware-accelerated decoding > VA-API video decoder.

VLC must also be configured to use VAAPI for video decoding, through the following menus: In order to use VLC with Cedrus, the libva-v4l2-request VAAPI backend must be installed on the system. In order to access the device nodes created by the Cedrus kernel driver, the user that will be decoding videos needs to be added to the video group.ДЄlternatively, the permissions of the /dev/video0 and /dev/media0 nodes can be changed to allow access by this user. It can be built on the host or the target device through the following steps: The libva-dump VAAPI backend is available at: It can be built on the target device through the following steps: The v4l2-request-test tool is available at: autogen.sh -prefix=/usr & make & sudo make installДЄlternatively to building libdrm-sun4i, the sun4i_drm.h file can be placed into /usr/include/drm directly. It can be built and installed on the target device through the following steps: Libdrm-sun4i imports the updated sun4i-drm Linux kernel driver definitions for installation in userspace and is available at: This is deprecated and no longer needed for other components to build.

The backend can be built and installed on the target device by following these steps: The main userspace component that supports the Cedrus VPU driver is the libva-v4l2-request VAAPI backend.

#X11 video output xcb download code

Newer Cedrus code is available in the bootlin git repository linked above. The first mainline kernel release containing Cedrus support is 4.20 (scheduled for release December 2018 or Jan 2019).

#X11 video output xcb download 1080p

For instance, 256 MiB should be enough to decode 1080p H.264 videos: cma=256M. using the cma kernel command line parameter. Note that the associated kernel headers must be installed to the target device for the userspace components to build.Дecoding H.264/H.265 videos can require a large amount of CMA memory, so it is recommended to set a large CMA pool, e.g.

In addition, the target device must contain the proper description for display engine support in its device-tree source.Дetails about building a mainline Linux kernel are available on the Mainline Kernel Howto page. The following kernel configuration options must be selected: A tree with all the required patches is available at:

#X11 video output xcb download Patch

The first step to installing Cedrus support is to build a Linux kernel with the latest patch series for the driver. The following players were tested with the v4l2-request libVA backend: Support for specific SoCs in the V4L2 M2M kernel driver is presented in the following table: Support status for specific codecs in the v4l2-request libVA backend is presented in the following table: See Player Support for the status of tested players.

However, details in implementations might result in incompatibility with certain players. Video players that support libVA should be compatible with the v4l2-request libVA backend.

the dump libVA backend, that allows dumping metadata and slices from videos.

the sun4i-specific libdrm, with support for allocating buffers in the MB32-tiled NV12 format used by the VPU.

the v4l2-request-test standalone tool, that allows testing the -Cedrus VPU driver.

Support for Sunxi-Cedrus is implemented through various components, either in kernel space or userspace:ДЄdditional userspace components are also available, for development purposes:

7.4 Technical details and implementation.