clients/dmabuf-v4l: explain vivid setup
Add very short explanation on how to set up Vivid driver, when you don't have suitable V4L2 device to use. Using the XR24 (DRM_FORMAT_XRGB8888) format practically guarantees that you can test direct scanout on a hardware overlay, too. At least on PC hardware that has overlays. Tested to work on Intel. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk> Reviewed-by: Quentin Glidic <sardemff7+git@sardemff7.net>
This commit is contained in:
parent
2eda27b7fb
commit
dbb85d7173
|
@ -896,6 +896,23 @@ usage(const char *argv0)
|
|||
"The default for both formats is YUYV.\n"
|
||||
"If the V4L2 and DRM formats differ, the data is simply "
|
||||
"reinterpreted rather than converted.\n", argv0);
|
||||
|
||||
printf("\n"
|
||||
"How to set up Vivid the virtual video driver for testing:\n"
|
||||
"- build your kernel with CONFIG_VIDEO_VIVID=m\n"
|
||||
"- add this to a /etc/modprobe.d/ file:\n"
|
||||
" options vivid node_types=0x1 num_inputs=1 input_types=0x00\n"
|
||||
"- modprobe vivid and check which device was created,\n"
|
||||
" here we assume /dev/video0\n"
|
||||
"- set the pixel format:\n"
|
||||
" $ v4l2-ctl -d /dev/video0 --set-fmt-video=width=640,pixelformat=XR24\n"
|
||||
"- launch the demo:\n"
|
||||
" $ %s /dev/video0 XR24 XR24\n"
|
||||
"You should see a test pattern with color bars, and some text.\n"
|
||||
"\n"
|
||||
"More about vivid: https://www.kernel.org/doc/Documentation/video4linux/vivid.txt\n"
|
||||
"\n", argv0);
|
||||
|
||||
exit(0);
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in New Issue