diff options
| author | Pekka Paalanen <pekka.paalanen@collabora.co.uk> | 2016-07-04 16:25:15 +0300 |
|---|---|---|
| committer | Quentin Glidic <sardemff7+git@sardemff7.net> | 2016-08-15 18:24:52 +0200 |
| commit | dbb85d717355f872e1fd71c4e63a66a1b52d81a2 (patch) | |
| tree | 9722fd57e5359ea09fc4aee9a55ac0f7571d956e | |
| parent | 2eda27b7fbc6cde9ac8beb04cd0af2d4d04f73c6 (diff) | |
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>
| -rw-r--r-- | clients/simple-dmabuf-v4l.c | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/clients/simple-dmabuf-v4l.c b/clients/simple-dmabuf-v4l.c index ce124cc9..de77e36d 100644 --- a/clients/simple-dmabuf-v4l.c +++ b/clients/simple-dmabuf-v4l.c @@ -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); } |