Video4Linux2 camera capture. More...

Video4Linux2 camera capture.

The camerav4l2 driver captures images from V4L2-compatible cameras.

Compile-time dependencies
Provides
Requires
Configuration requests
Configuration file options

Note that some of these options may not be honoured by the underlying V4L2 kernel driver (it may not support a given image size, for example).

Example
driver
(
  name "camerav4l2"
  provides ["camera:0"]
)
Channel 2 explicitly selected:
driver
(
  name "camerav4l2"
  sources [2]
  norm "PAL"
  size [384 288]
  mode "BGR4"
  buffers 4
  sleep_nsec 10000
  provides ["ch2:::camera:1"]
)
driver
(
  name "cameracompress"
  requires "camera:1"
  provides "camera:0"
)
Two channels at the same time:
driver
(
  name "camerav4l2"
  sources [0 2]
  norm "PAL"
  provides ["ch2:::camera:0" "ch0:::camera:1"]
)
sn9c1xx-based USB webcam (it accepts one buffer and only 352x288 size!):
driver
(
  name "camerav4l2"
  norm "UNKNOWN"
  mode "BA81"
  size [352 288]
  buffers 1
  provides ["camera:1"]
)
driver
(
  name "cameracompress"
  requires ["camera:1"]
  provides ["camera:0"]
)
LogiLink USB 2.0 Video Grabber (two sources: 0 = composite, 1 = s-video).

driver ( name "camerav4l2" port "/dev/video0" sources [0] norm "UNKNOWN" size [720 480] mode "YUYV" buffers 2 sleep_nsec 10000 provides ["ch0:::camera:0"] )

driver
(
  name "camerav4l2"
  port "/dev/video0"
  sources [0 1]
  norm "PAL60"
  size [720 480]
  mode "YUYV"
  buffers 2
  sleep_nsec 10000
  settle_time 0.1
  skip_frames 7
  provides ["ch0:::camera:0" "ch1:::camera:1"]
)

WARNING! This device uses very unstable driver (usbtv.ko), e.g. setting norm to "PAL" always resulted in kernel panic. Use "PAL60" instead. Buffers should be always set to 2, it won't initialize otherwise. The settle_time and skip_frames in two cameras scenario were chosen experimentally, may require some tweaking. Sizes different than 720x480 seem to be unsupported (messy image).

Author
Paul Osmialowski, Takafumi Mizuno