dv4l(1) [debian man page]
DV4L(1) General Commands Manual DV4L(1) NAME
dv4l - make a dv1394 camcorder available for video4linux programs SYNOPSIS
dv4l [options] options (shortest form): [-cdrsvh] DESCRIPTION
dv4l enables programs using the video4linux API to access a dv1394 (Firewire) camcorder. It pushes the video stream to an input device pro- vided by the vloopback kernel module. Before starting dv4l , make sure that the vloopback module is present in the kernel. See http://www.lavrsen.dk/twiki/bin/view/Motion/VideoFourLinuxLoopbackDevice (without the dash) for information about this kernel module. Check your 1394 driver config by starting $ gst-launch-0.10 dv1394src ! dvdemux ! dvdec ! xvimagesink from your shell. After turning on your camera, a video window should appear. If this works, dv4l should work as well. Make sure that your camera is on before starting a video4linux program. OPTIONS
-c, --color-correction Set this option if red objects look blue. -d, --device device-name Use device-name as vloopback input device. If this option is omitted, dv4l will automatically look for an appropriate device. -r, --rgb-only Set this option to prevent V4L applications from choosing YUV palettes. Try this option if you get low frame rates. -s, --size WxH Set capture size and use slower copy mode, only required for some V4L applications. When using this option, V4L applications can't change the capture size. -v, --verbose level Set the amount of debugging messages. A level of 0 means no output at all, 1 is the default, 3 enables all messages. -h, --help displays a help message EXAMPLES
In most cases, dv4l can be started without any options. Kopete, however needs the --size option, with a resolution of 320x240: dv4l -s 320x240 Like kopete, gqcam needs the --size option, but supports arbitrary resolutions: dv4l -s 635x360 dv4l will do the scaling. LIMITATIONS
dv4l does not support adjustment of color, brightness and similar parameters. It supports only RGB24 and YUV420P palettes. Some V4L programs may not work as they require different palettes. It supports only a single dv1394 camera. Skype v2.0beta seems to have problems with vloopback and does NOT work with dv4l. Try dv4lstart instead. SEE ALSO
dv4lstart(1) DV4L(1)
Check Out this Related Man Page
VGA(4) BSD Kernel Interfaces Manual VGA(4) NAME
vga -- generic video card interface SYNOPSIS
options VESA options VESA_DEBUG=N options VGA_ALT_SEQACCESS options VGA_NO_FONT_LOADING options VGA_NO_MODE_CHANGE options VGA_SLOW_IOACCESS options VGA_WIDTH90 device vga In /boot/device.hints: hint.vga.0.at="isa" DESCRIPTION
The vga driver is a generic video card driver which provides access to video cards. This driver is required for the console driver syscons(4). The console driver will call the vga driver to manipulate video hardware (changing video modes, loading font, etc). The vga driver supports the standard video cards: MDA, CGA, EGA and VGA. In addition, the driver can utilize VESA BIOS extensions if the video card supports them. VESA support can either be statically included in the kernel or can be loaded as a separate module. In order to statically link the VESA support to the kernel, the VESA option (see below) must be defined in the kernel configuration file. The vesa module can be dynamically loaded into the kernel using kldload(8). DRIVER CONFIGURATION
Kernel Configuration Options The following kernel configuration options (see config(8)) can be used to control the vga driver. These options provide compatibility with certain VGA cards. VGA_ALT_SEQACCESS You may want to try this option if the mouse pointer is not drawn correctly or the font does not seem to be loaded properly on the VGA card. However, it may cause flicker on some systems. VGA_SLOW_IOACCESS Older VGA cards may require this option for proper operation. It makes the driver perform byte-wide I/O to VGA registers and slow down a little. VGA_WIDTH90 This option enables 90 column modes: 90x25, 90x30, 90x43, 90x50, 90x60. These modes are not always supported by the video card and the display. It is highly likely that LCD display cannot work with these modes. The following options add optional features to the driver. VESA Add VESA BIOS support to the driver. If the VGA card has the VESA BIOS extension 1.2 or later, this option will utilize the VESA BIOS service to switch to high resolution modes. VESA_DEBUG=N Set the VESA support debug level to N. The default value is zero, which suppresses all debugging output. The following options will remove some features from the vga driver and save kernel memory. VGA_NO_FONT_LOADING The vga driver can load software font to EGA and VGA cards. This option removes this feature. Note that if you use this option and still wish to use the mouse on the console then you must also use the SC_ALT_MOUSE_IMAGE option. See syscons(4). VGA_NO_MODE_CHANGE This option prevents the driver from changing video modes. EXAMPLES
Your kernel configuration should normally have: device vga And you need the following line in /boot/device.hints. hint.vga.0.at="isa" The following lines should be included in the kernel configuration file in order to enable the VESA BIOS Extension support. options VESA device vga If you do not want VESA support included in the kernel, but want to use occasionally, do not add the VESA option. And load the vesa module as desired: kldload vesa SEE ALSO
vgl(3), syscons(4), config(8), kldload(8), kldunload(8) STANDARDS
Video Electronics Standards Association, VESA BIOS Extension (VBE). HISTORY
The vga driver first appeared in FreeBSD 3.1. AUTHORS
The vga driver was written by Soren Schmidt <sos@FreeBSD.org> and Kazutaka Yokota <yokota@FreeBSD.org>. This manual page was written by Kazutaka Yokota. BSD
June 30, 1999 BSD