7.2. Changes of the V4L2 API¶
Soon after the V4L API was added to the kernel it was criticised as too inflexible. In August 1998 Bill Dirks proposed a number of improvements and began to work on documentation, example drivers and applications. With the help of other volunteers this eventually became the V4L2 API, not just an extension but a replacement for the V4L API. However it took another four years and two stable kernel releases until the new API was finally accepted for inclusion into the kernel in its present form.
7.2.1. Early Versions¶
1998-08-20: First version.
1998-08-27: The select() function was introduced.
1998-09-10: New video standard interface.
VIDIOC_NONCAP ioctl was replaced by the otherwise
O_TRUNC open() flag, and the
O_NOIO were defined. Applications can set
this flag if they intend to access controls only, as opposed to capture
applications which need exclusive access. The
identifiers are now ordinals instead of flags, and the
video_std_construct() helper function takes id and
1998-09-28: Revamped video standard. Made video controls individually enumerable.
id field was removed from struct
video_standard and the color subcarrier fields were
renamed. The ioctl VIDIOC_QUERYSTD ioctl was
renamed to ioctl VIDIOC_ENUMSTD,
ioctl VIDIOC_ENUMINPUT. A first draft of the
Codec API was released.
1998-11-08: Many minor changes. Most symbols have been renamed. Some
material changes to struct
1998-11-12: The read/write directon of some ioctls was misdefined.
V4L2_PIX_FMT_RGB24 changed to
V4L2_PIX_FMT_RGB32 changed to
controls are now accessible with the
VIDIOC_S_CTRL ioctls under names starting
V4L2_MAJOR define was removed from
videodev.h since it was only used once in the
YUV411 planar image formats were added.
1998-11-28: A few ioctl symbols changed. Interfaces for codecs and video output devices were added.
1999-01-14: A raw VBI capture interface was added.
VIDIOC_NEXTBUF ioctl was removed.
7.2.2. V4L2 Version 0.16 1999-01-31¶
1999-01-27: There is now one QBUF ioctl, VIDIOC_QWBUF and VIDIOC_QRBUF are gone. VIDIOC_QBUF takes a v4l2_buffer as a parameter. Added digital zoom (cropping) controls.
7.2.3. V4L2 Version 0.18 1999-03-16¶
Added a v4l to V4L2 ioctl compatibility layer to videodev.c. Driver writers, this changes how you implement your ioctl handler. See the Driver Writer’s Guide. Added some more control id codes.
7.2.4. V4L2 Version 0.19 1999-06-05¶
1999-03-18: Fill in the category and catname fields of v4l2_queryctrl objects before passing them to the driver. Required a minor change to the VIDIOC_QUERYCTRL handlers in the sample drivers.
1999-03-31: Better compatibility for v4l memory capture ioctls. Requires changes to drivers to fully support new compatibility features, see Driver Writer’s Guide and v4l2cap.c. Added new control IDs: V4L2_CID_HFLIP, _VFLIP. Changed V4L2_PIX_FMT_YUV422P to _YUV422P, and _YUV411P to _YUV411P.
1999-04-04: Added a few more control IDs.
1999-04-07: Added the button control type.
1999-05-02: Fixed a typo in videodev.h, and added the V4L2_CTRL_FLAG_GRAYED (later V4L2_CTRL_FLAG_GRABBED) flag.
1999-05-20: Definition of VIDIOC_G_CTRL was wrong causing a malfunction of this ioctl.
1999-06-05: Changed the value of V4L2_CID_WHITENESS.
7.2.5. V4L2 Version 0.20 (1999-09-10)¶
Version 0.20 introduced a number of changes which were not backward compatible with 0.19 and earlier versions. Purpose of these changes was to simplify the API, while making it more extensible and following common Linux driver API conventions.
Some typos in
V4L2_FMT_FLAGsymbols were fixed. struct
v4l2_clipwas changed for compatibility with v4l. (1999-08-30)
V4L2_TUNER_SUB_LANG1was added. (1999-09-05)
All ioctl() commands that used an integer argument now take a pointer to an integer. Where it makes sense, ioctls will return the actual new value in the integer pointed to by the argument, a common convention in the V4L2 API. The affected ioctls are: VIDIOC_PREVIEW, VIDIOC_STREAMON, VIDIOC_STREAMOFF, VIDIOC_S_FREQ, VIDIOC_S_INPUT, VIDIOC_S_OUTPUT, VIDIOC_S_EFFECT. For example
err = ioctl (fd, VIDIOC_XXX, V4L2_XXX);
int a = V4L2_XXX; err = ioctl(fd, VIDIOC_XXX, &a);
All the different get- and set-format commands were swept into one VIDIOC_G_FMT and VIDIOC_S_FMT ioctl taking a union and a type field selecting the union member as parameter. Purpose is to simplify the API by eliminating several ioctls and to allow new and driver private data streams without adding new ioctls.
This change obsoletes the following ioctls:
VIDIOC_G_VBIFMT. The image format structure struct
v4l2_formatwas renamed to struct
v4l2_pix_format, while struct
v4l2_formatis now the envelopping structure for all format negotiations.
Similar to the changes above, the
VIDIOC_S_PARMioctls were merged with
typefield in the new struct
v4l2_streamparmselects the respective union member.
This change obsoletes the
Control enumeration was simplified, and two new control flags were introduced and one dropped. The
catnamefield was replaced by a
Drivers can now flag unsupported and temporarily unavailable controls with
groupname indicates a possibly narrower classification than the
category. In other words, there may be multiple groups within a category. Controls within a group would typically be drawn within a group box. Controls in different categories might have a greater separation, or may even appear in separate windows.
timestampwas changed to a 64 bit integer, containing the sampling or output time of the frame in nanoseconds. Additionally timestamps will be in absolute system time, not starting from zero at the beginning of a stream. The data type name for timestamps is stamp_t, defined as a signed 64-bit integer. Output devices should not send a buffer out until the time in the timestamp field has arrived. I would like to follow SGI’s lead, and adopt a multimedia timestamping system like their UST (Unadjusted System Time). See http://web.archive.org/web/*/http://reality.sgi.com /cpirazzi_engr/lg/time/intro.html. UST uses timestamps that are 64-bit signed integers (not struct timeval’s) and given in nanosecond units. The UST clock starts at zero when the system is booted and runs continuously and uniformly. It takes a little over 292 years for UST to overflow. There is no way to set the UST clock. The regular Linux time-of-day clock can be changed periodically, which would cause errors if it were being used for timestamping a multimedia stream. A real UST style clock will require some support in the kernel that is not there yet. But in anticipation, I will change the timestamp field to a 64-bit integer, and I will change the v4l2_masterclock_gettime() function (used only by drivers) to return a 64-bit integer.
sequencefield was added to struct
sequencefield counts captured frames, it is ignored by output devices. When a capture driver drops a frame, the sequence number of that frame is skipped.
7.2.6. V4L2 Version 0.20 incremental changes¶
1999-12-23: In struct
reserved1 field became
offset. Previously drivers were required
to clear the
V4L2_FMT_FLAG_NOT_INTERLACED flag was added.
linux/poll.h header is now included by
videodev.h for compatibility with the original
V4L2_TYPE_VBI_INPUT was added.
2000-12-04: A couple typos in symbol names were fixed.
2001-01-18: To avoid namespace conflicts the
fourcc macro defined in
videodev.h header file was renamed to
2001-01-25: A possible driver-level compatibility problem between the
videodev.h file in Linux 2.4.0 and the
videodev.h file included
videodevX patch was fixed. Users of an earlier version of
videodevX on Linux 2.4.0 should recompile their V4L and V4L2
2001-01-26: A possible kernel-level incompatibility between the
videodev.h file in the
videodevX patch and the
file in Linux 2.2.x with devfs patches applied was fixed.
2001-03-02: Certain V4L ioctls which pass data in both direction although they are defined with read-only parameter, did not work correctly through the backward compatibility layer. [Solution?]
2001-04-13: Big endian 16-bit RGB formats were added.
V4L2_BUF_TYPE_VBI was added. This may break
compatibility as the VIDIOC_G_FMT and
VIDIOC_S_FMT ioctls may fail now if the struct
type field does not contain
V4L2_BUF_TYPE_VBI. In the documentation of the struct
offset field the
ambiguous phrase “rising edge” was changed to “leading edge”.
7.2.7. V4L2 Version 0.20 2000-11-23¶
A number of changes were made to the raw VBI interface.
- Figures clarifying the line numbering scheme were added to the V4L2
API specification. The
start fields no longer count line numbers beginning at zero. Rationale: a) The previous definition was unclear. b) The
start values are ordinal numbers. c) There is no point in inventing a new line numbering scheme. We now use line number as defined by ITU-R, period. Compatibility: Add one to the start values. Applications depending on the previous semantics may not function correctly.
- The restriction “count > 0 and count > 0” has been relaxed to
“(count + count) > 0”. Rationale: Drivers may allocate
resources at scan line granularity and some data services are
transmitted only on the first field. The comment that both
countvalues will usually be equal is misleading and pointless and has been removed. This change breaks compatibility with earlier versions: Drivers may return
EINVAL, applications may not function correctly.
- Drivers are again permitted to return negative (unknown) start values
as proposed earlier. Why this feature was dropped is unclear. This
change may break compatibility with applications depending on the
start values being positive. The use of
EINVALerror codes with the VIDIOC_S_FMT ioctl was clarified. The
EBUSYerror code was finally documented, and the
reserved2field which was previously mentioned only in the
- New buffer types
V4L2_TYPE_VBI_OUTPUTwere added. The former is an alias for the old
V4L2_TYPE_VBI, the latter was missing in the
7.2.8. V4L2 Version 0.20 2002-07-25¶
Added sliced VBI interface proposal.
7.2.9. V4L2 in Linux 2.5.46, 2002-10¶
Around October-November 2002, prior to an announced feature freeze of Linux 2.5, the API was revised, drawing from experience with V4L2 0.20. This unnamed version was finally merged into Linux 2.5.46.
As specified in Related Devices, drivers must make related device functions available under all minor device numbers.
The open() function requires access mode
O_RDWRregardless of the device type. All V4L2 drivers exchanging data with applications must support the
O_NOIOflag, a V4L2 symbol which aliased the meaningless
O_TRUNCto indicate accesses without data exchange (panel applications) was dropped. Drivers must stay in “panel mode” until the application attempts to initiate a data exchange, see Opening and Closing Devices.
v4l2_capabilitychanged dramatically. Note that also the size of the structure changed, which is encoded in the ioctl request code, thus older V4L2 devices will respond with an
EINVALerror code to the new ioctl VIDIOC_QUERYCAP ioctl.
There are new fields to identify the driver, a new RDS device function
V4L2_CAP_AUDIOflag indicates if the device has any audio connectors, another I/O capability
V4L2_CAP_ASYNCIOcan be flagged. In response to these changes the
typefield became a bit set and was merged into the
V4L2_FLAG_TUNERwas renamed to
V4L2_FLAG_WRITEwere merged into
The somewhat volatile and therefore barely useful fields
maxframeratewere removed. This information is available as described in Data Formats and Video Standards.
V4L2_FLAG_SELECTwas removed. We believe the select() function is important enough to require support of it in all V4L2 drivers exchanging data with applications. The redundant
V4L2_FLAG_MONOCHROMEflag was removed, this information is available as described in Data Formats.
assoc_audiofield and the
capabilityfield and its only flag
V4L2_INPUT_CAP_AUDIOwas replaced by the new
audiosetfield. Instead of linking one video input to one audio input this field reports all audio inputs this video input combines with.
New fields are
tuner(reversing the former link from tuners to video inputs),
stdwhere added instead.
audiowas renamed to
index, for consistency with other structures. A new capability flag
V4L2_AUDCAP_STEREOwas added to indicated if the audio input in question supports stereo sound.
V4L2_AUDCAP_EFFECTSand the corresponding
V4L2_AUDMODEflags where removed. This can be easily implemented using controls. (However the same applies to AVL which is still there.)
Again for consistency the struct
audiowas renamed to
inputfield was replaced by an
indexfield, permitting devices with multiple tuners. The link between video inputs and tuners is now reversed, inputs point to their tuner. The
stdsubstructure became a simple set (more about this below) and moved into struct
typefield was added.
Accordingly in struct
outputwas replaced by an
portfield was replaced by a
tunerfield containing the respective tuner or modulator index number. A tuner
typefield was added and the
reservedfield became larger for future extensions (satellite tuners in particular).
The idea of completely transparent video standards was dropped. Experience showed that applications must be able to work with video standards beyond presenting the user a menu. Instead of enumerating supported standards with an ioctl applications can now refer to standards by v4l2_std_id and symbols defined in the
videodev2.hheader file. For details see Video Standards. The VIDIOC_G_STD and VIDIOC_S_STD now take a pointer to this type as argument. ioctl VIDIOC_QUERYSTD was added to autodetect the received standard, if the hardware has this capability. In struct
indexfield was added for ioctl VIDIOC_ENUMSTD. A v4l2_std_id field named
idwas added as machine readable identifier, also replacing the
transmissionfield. The misleading
frameratefield was renamed to
frameperiod. The now obsolete
colorstandardinformation, originally needed to distguish between variations of standards, were removed.
v4l2_enumstdceased to be. ioctl VIDIOC_ENUMSTD now takes a pointer to a struct
v4l2_standarddirectly. The information which standards are supported by a particular video input or output moved into struct
The struct v4l2_queryctrl fields
groupdid not catch on and/or were not implemented as expected and therefore removed.
fmtunion was extended to contain struct
v4l2_window. All image format negotiations are now possible with
VIDIOC_TRY_FMT; ioctl. The
VIDIOC_S_WINioctls to prepare for a video overlay were removed. The
typefield changed to type enum
v4l2_buf_typeand the buffer type names changed as follows.
Old defines enum
Omitted for now
Omitted for now
Omitted for now
Omitted for now
Omitted for now
V4L2_BUF_TYPE_PRIVATE(but this is deprecated)
typewas added as in struct
VIDIOC_ENUM_FBUFFMTioctl is no longer needed and was removed. These calls can be replaced by ioctl VIDIOC_ENUM_FMT with type
depthfield was removed, assuming applications which recognize the format by its four-character-code already know the color depth, and others do not care about it. The same rationale lead to the removal of the
V4L2_FMT_FLAG_SWCONVECOMPRESSEDflag was removed because drivers are not supposed to convert images in kernel space. A user library of conversion functions should be provided instead. The
V4L2_FMT_FLAG_BYTESPERLINEflag was redundant. Applications can set the
bytesperlinefield to zero to get a reasonable default. Since the remaining flags were replaced as well, the
flagsfield itself was removed.
The interlace flags were replaced by a enum
v4l2_fieldvalue in a newly added
Old flag enum
The color space flags were replaced by a enum
v4l2_colorspacevalue in a newly added
colorspacefield, where one of
typefield was properly defined as enum
v4l2_buf_type. Buffer types changed as mentioned above. A new
memoryfield of type enum
v4l2_memorywas added to distinguish between I/O methods using buffers allocated by the driver or the application. See Input/Output for details.
typefield was properly defined as enum
v4l2_buf_type. Buffer types changed as mentioned above. A
fieldfield of type enum
v4l2_fieldwas added to indicate if a buffer contains a top or bottom field. The old field flags were removed. Since no unadjusted system time clock was added to the kernel as planned, the
timestampfield changed back from type stamp_t, an unsigned 64 bit integer expressing the sample time in nanoseconds, to struct
timeval. With the addition of a second memory mapping method the
offsetfield moved into union
m, and a new
memoryfield of type enum
v4l2_memorywas added to distinguish between I/O methods. See Input/Output for details.
V4L2_BUF_REQ_CONTIGflag was used by the V4L compatibility layer, after changes to this code it was no longer needed. The
V4L2_BUF_ATTR_DEVICEMEMflag would indicate if the buffer was indeed allocated in device memory rather than DMA-able system memory. It was barely useful and so was removed.
basearray anticipating double- and triple-buffering in off-screen video memory, however without defining a synchronization mechanism, was replaced by a single pointer. The
V4L2_FBUF_CAP_SCALEDOWNflags were removed. Applications can determine this capability more accurately using the new cropping and scaling interface. The
V4L2_FBUF_CAP_CLIPPINGflag was replaced by
heightfield moved into a
csubstructure of type struct
yfields were renamed to
top, i. e. offsets to a context dependent origin.
The digital zoom interface, including struct struct
v4l2_zoomcap, struct struct
V4L2_ZOOM_WHILESTREAMINGwas replaced by a new cropping and scaling interface. The previously unused struct struct
v4l2_cropwhere redefined for this purpose. See Image Cropping, Insertion and Scaling for details.
SAMPLE_FORMATfield now contains a four-character-code as used to identify video image formats and
reservedfield was extended.
v4l2_captureparmthe type of the
timeperframefield changed from unsigned long to struct
v4l2_fract. This allows the accurate expression of multiples of the NTSC-M frame rate 30000 / 1001. A new field
readbufferswas added to control the driver behaviour in read I/O mode.
Similar changes were made to struct
VIDIOC_G_PERFioctl were dropped. Except when using the read/write I/O method, which is limited anyway, this information is already available to applications.
The example transformation from RGB to YCbCr color space in the old V4L2 documentation was inaccurate, this has been corrected in Image Formats.
7.2.10. V4L2 2003-06-19¶
A new capability flag
V4L2_CAP_RADIOwas added for radio devices. Prior to this change radio devices would identify solely by having exactly one tuner whose type field reads
An optional driver access priority mechanism was added, see Application Priority for details.
The audio input and output interface was found to be incomplete.
Previously the VIDIOC_G_AUDIO ioctl would enumerate the available audio inputs. An ioctl to determine the current audio input, if more than one combines with the current video input, did not exist. So
VIDIOC_G_AUDIOwas renamed to
VIDIOC_G_AUDIO_OLD, this ioctl was removed on Kernel 2.6.39. The ioctl VIDIOC_ENUMAUDIO ioctl was added to enumerate audio inputs, while VIDIOC_G_AUDIO now reports the current audio input.
Until further the “videodev” module will automatically translate between the old and new ioctls, but drivers and applications must be updated to successfully compile again.
The ioctl VIDIOC_OVERLAY ioctl was incorrectly defined with write-read parameter. It was changed to write-only, while the write-read version was renamed to
VIDIOC_OVERLAY_OLD. The old ioctl was removed on Kernel 2.6.39. Until further the “videodev” kernel module will automatically translate to the new version, so drivers must be recompiled, but not applications.
Video Overlay Interface incorrectly stated that clipping rectangles define regions where the video can be seen. Correct is that clipping rectangles define regions where no video shall be displayed and so the graphics surface can be seen.
The VIDIOC_S_PARM and VIDIOC_S_CTRL ioctls were defined with write-only parameter, inconsistent with other ioctls modifying their argument. They were changed to write-read, while a
_OLDsuffix was added to the write-only versions. The old ioctls were removed on Kernel 2.6.39. Drivers and applications assuming a constant parameter need an update.
7.2.11. V4L2 2003-11-05¶
In RGB Formats the following pixel formats were incorrectly transferred from Bill Dirks’ V4L2 specification. Descriptions below refer to bytes in memory, in ascending address order.
Symbol In this document prior to revision 0.5 Corrected
B, G, R R, G, B
R, G, B B, G, R
B, G, R, X R, G, B, X
R, G, B, X B, G, R, X
V4L2_PIX_FMT_BGR24example was always correct.
In Image Properties the mapping of the V4L
VIDEO_PALETTE_RGB32formats to V4L2 pixel formats was accordingly corrected.
Unrelated to the fixes above, drivers may still interpret some V4L2 RGB pixel formats differently. These issues have yet to be addressed, for details see RGB Formats.
7.2.12. V4L2 in Linux 2.6.6, 2004-05-09¶
- The ioctl VIDIOC_CROPCAP ioctl was incorrectly
defined with read-only parameter. It is now defined as write-read
ioctl, while the read-only version was renamed to
VIDIOC_CROPCAP_OLD. The old ioctl was removed on Kernel 2.6.39.
7.2.13. V4L2 in Linux 2.6.8¶
- A new field
reserved) was added to the struct
v4l2_bufferstructure. Purpose of this field is to alternate between video inputs (e. g. cameras) in step with the video capturing process. This function must be enabled with the new
flagsfield is no longer read-only.
7.2.14. V4L2 spec erratum 2004-08-01¶
- The return value of the V4L2 open() function was incorrectly documented.
- Audio output ioctls end in -AUDOUT, not -AUDIOOUT.
- In the Current Audio Input example the
VIDIOC_G_AUDIOioctl took the wrong argument.
- The documentation of the ioctl VIDIOC_QBUF, VIDIOC_DQBUF and
VIDIOC_DQBUF ioctls did not mention the
memoryfield. It was also missing from examples. Also on the
EIOerror code was not documented.
7.2.15. V4L2 in Linux 2.6.14¶
- A new sliced VBI interface was added. It is documented in Sliced VBI Data Interface and replaces the interface first proposed in V4L2 specification 0.8.
7.2.16. V4L2 in Linux 2.6.15¶
- The ioctl VIDIOC_LOG_STATUS ioctl was added.
- New video standards
V4L2_STD_SECAM_DK(a set of SECAM D, K and K1), and
V4L2_STD_ATSC(a set of
V4L2_STD_ATSC_16_VSB) were defined. Note the
V4L2_STD_525_60set now includes
V4L2_STD_NTSC_443. See also typedef v4l2_std_id.
VIDIOC_S_COMPioctl were renamed to
VIDIOC_S_MPEGCOMPrespectively. Their argument was replaced by a struct
VIDIOC_S_MPEGCOMPioctls where removed in Linux 2.6.25.)
7.2.17. V4L2 spec erratum 2005-11-27¶
The capture example in Video Capture Example called the VIDIOC_S_CROP ioctl without checking if cropping is supported. In the video standard selection example in Video Standards the VIDIOC_S_STD call used the wrong argument type.
7.2.18. V4L2 spec erratum 2006-01-10¶
V4L2_IN_ST_COLOR_KILLflag in struct
v4l2_inputnot only indicates if the color killer is enabled, but also if it is active. (The color killer disables color decoding when it detects no color in the video signal to improve the image quality.)
- VIDIOC_S_PARM is a write-read ioctl, not write-only as stated on its reference page. The ioctl changed in 2003 as noted above.
7.2.19. V4L2 spec erratum 2006-02-03¶
7.2.20. V4L2 spec erratum 2006-02-04¶
7.2.21. V4L2 in Linux 2.6.17¶
- New video standard macros were added:
V4L2_STD_NTSC_M_KR(NTSC M South Korea), and the sets
V4L2_STD_SECAMsets now include
- A new
V4L2_TUNER_MODE_LANG1_LANG2was defined to record both languages of a bilingual program. The use of
V4L2_TUNER_MODE_STEREOfor this purpose is deprecated now. See the VIDIOC_G_TUNER section for details.
7.2.22. V4L2 spec erratum 2006-09-23 (Draft 0.15)¶
- In various places
V4L2_BUF_TYPE_SLICED_VBI_OUTPUTof the sliced VBI interface were not mentioned along with other buffer types.
- In VIDIOC_G_AUDIO it was clarified that the struct
modefield is a flags field.
- ioctl VIDIOC_QUERYCAP did not mention the sliced VBI and radio capability flags.
- In VIDIOC_G_FREQUENCY it was clarified that applications
must initialize the tuner
typefield of struct
v4l2_frequencybefore calling VIDIOC_S_FREQUENCY.
reservedarray in struct
v4l2_requestbuffershas 2 elements, not 32.
- In Video Output Interface and Raw VBI Data Interface the device file names
/dev/voutwhich never caught on were replaced by
- With Linux 2.6.15 the possible range for VBI device minor numbers was
extended from 224-239 to 224-255. Accordingly device file names
/dev/vbi31are possible now.
7.2.23. V4L2 in Linux 2.6.18¶
- New ioctls VIDIOC_G_EXT_CTRLS,
VIDIOC_TRY_EXT_CTRLS were added, a
flag to skip unsupported controls with
ioctls VIDIOC_QUERYCTRL, VIDIOC_QUERY_EXT_CTRL and VIDIOC_QUERYMENU, new control types
v4l2_ctrl_type), and new control flags
V4L2_CTRL_FLAG_SLIDER(Control Flags). See Extended Controls for details.
7.2.24. V4L2 in Linux 2.6.19¶
- In struct
v4l2_sliced_vbi_capa buffer type field was added replacing a reserved field. Note on architectures where the size of enum types differs from int types the size of the structure changed. The VIDIOC_G_SLICED_VBI_CAP ioctl was redefined from being read-only to write-read. Applications must initialize the type field and clear the reserved fields now. These changes may break the compatibility with older drivers and applications.
- The ioctls ioctl VIDIOC_ENUM_FRAMESIZES and ioctl VIDIOC_ENUM_FRAMEINTERVALS were added.
- A new pixel format
V4L2_PIX_FMT_RGB444(Packed RGB Image Formats) was added.
7.2.25. V4L2 spec erratum 2006-10-12 (Draft 0.17)¶
V4L2_PIX_FMT_HM12(Reserved Image Formats) is a YUV 4:2:0, not 4:2:2 format.
7.2.26. V4L2 in Linux 2.6.21¶
videodev2.hheader file is now dual licensed under GNU General Public License version two or later, and under a 3-clause BSD-style license.
7.2.27. V4L2 in Linux 2.6.22¶
Two new field orders
V4L2_FIELD_INTERLACED_BTwere added. See
Three new clipping/blending methods with a global or straight or inverted local alpha value were added to the video overlay interface. See the description of the VIDIOC_G_FBUF and VIDIOC_S_FBUF ioctls for details.
global_alphafield was added to
v4l2_window, extending the structure. This may break compatibility with applications using a struct struct
v4l2_windowdirectly. However the VIDIOC_G/S/TRY_FMT ioctls, which take a pointer to a
v4l2_formatparent structure with padding bytes at the end, are not affected.
The format of the
chromakeyfield in struct
v4l2_windowchanged from “host order RGB32” to a pixel value in the same format as the framebuffer. This may break compatibility with existing applications. Drivers supporting the “host order RGB32” format are not known.
7.2.28. V4L2 in Linux 2.6.24¶
- The pixel formats
7.2.29. V4L2 in Linux 2.6.25¶
- The pixel formats V4L2_PIX_FMT_Y16 and V4L2_PIX_FMT_SBGGR16 were added.
- New controls
V4L2_CID_BACKLIGHT_COMPENSATIONwere added. The controls
- A Camera controls class was added, with
the new controls
VIDIOC_S_MPEGCOMPioctls, which were superseded by the extended controls interface in Linux 2.6.18, where finally removed from the
7.2.30. V4L2 in Linux 2.6.26¶
- The pixel formats
- Added user controls
7.2.31. V4L2 in Linux 2.6.27¶
- The ioctl VIDIOC_S_HW_FREQ_SEEK ioctl
V4L2_CAP_HW_FREQ_SEEKcapability were added.
- The pixel formats
7.2.32. V4L2 in Linux 2.6.28¶
V4L2_MPEG_AUDIO_ENCODING_AC3MPEG audio encodings.
V4L2_MPEG_VIDEO_ENCODING_MPEG_4_AVCMPEG video encoding.
- The pixel formats
7.2.33. V4L2 in Linux 2.6.29¶
VIDIOC_G_CHIP_IDENTioctl was renamed to
VIDIOC_DBG_G_CHIP_IDENTwas introduced in its place. The old struct struct
v4l2_chip_identwas renamed to struct
- The pixel formats
- Added camera controls
7.2.34. V4L2 in Linux 2.6.30¶
- New control flag
- New control
7.2.35. V4L2 in Linux 2.6.32¶
- In order to be easier to compare a V4L2 API and a kernel version, now V4L2 API is numbered using the Linux Kernel version numeration.
- Finalized the RDS capture API. See RDS Interface for more information.
- Added new capabilities for modulators and RDS encoders.
- Add description for libv4l API.
- Added support for string controls via new type
- Added FM Modulator (FM TX) Extended Control Class:
V4L2_CTRL_CLASS_FM_TXand their Control IDs.
- Added FM Receiver (FM RX) Extended Control Class:
V4L2_CTRL_CLASS_FM_RXand their Control IDs.
- Added Remote Controller chapter, describing the default Remote Controller mapping for media devices.
7.2.36. V4L2 in Linux 2.6.33¶
- Added support for Digital Video timings in order to support HDTV receivers and transmitters.
7.2.37. V4L2 in Linux 2.6.34¶
V4L2_CID_IRIS_RELATIVEcontrols to the Camera controls class.
7.2.38. V4L2 in Linux 2.6.37¶
- Remove the vtx (videotext/teletext) API. This API was no longer used and no hardware exists to verify the API. Nor were any userspace applications found that used it. It was originally scheduled for removal in 2.6.35.
7.2.39. V4L2 in Linux 2.6.39¶
- The old VIDIOC_*_OLD symbols and V4L1 support were removed.
- Multi-planar API added. Does not affect the compatibility of current drivers and applications. See multi-planar API for details.
7.2.40. V4L2 in Linux 3.1¶
VIDIOC_QUERYCAP now returns a per-subsystem version instead of a per-driver one.
Standardize an error code for invalid ioctl.
7.2.41. V4L2 in Linux 3.2¶
- V4L2_CTRL_FLAG_VOLATILE was added to signal volatile controls to userspace.
- Add selection API for extended control over cropping and composing. Does not affect the compatibility of current drivers and applications. See selection API for details.
7.2.42. V4L2 in Linux 3.3¶
V4L2_CID_ALPHA_COMPONENTcontrol to the User controls class.
- Added the device_caps field to struct v4l2_capabilities and added the new V4L2_CAP_DEVICE_CAPS capability.
7.2.43. V4L2 in Linux 3.4¶
- Added JPEG compression control class.
- Extended the DV Timings API: ioctl VIDIOC_ENUM_DV_TIMINGS, VIDIOC_SUBDEV_ENUM_DV_TIMINGS, ioctl VIDIOC_QUERY_DV_TIMINGS and ioctl VIDIOC_DV_TIMINGS_CAP, VIDIOC_SUBDEV_DV_TIMINGS_CAP.
7.2.44. V4L2 in Linux 3.5¶
- Added integer menus, the new type will be V4L2_CTRL_TYPE_INTEGER_MENU.
- Added selection API for V4L2 subdev interface: ioctl VIDIOC_SUBDEV_G_SELECTION, VIDIOC_SUBDEV_S_SELECTION and VIDIOC_SUBDEV_S_SELECTION.
V4L2_COLORFX_ARBITRARY_CBCRmenu items to the
- Added camera controls
7.2.45. V4L2 in Linux 3.6¶
7.2.46. V4L2 in Linux 3.9¶
7.2.47. V4L2 in Linux 3.10¶
- Removed obsolete and unused DV_PRESET ioctls VIDIOC_G_DV_PRESET, VIDIOC_S_DV_PRESET, VIDIOC_QUERY_DV_PRESET and VIDIOC_ENUM_DV_PRESET. Remove the related v4l2_input/output capability flags V4L2_IN_CAP_PRESETS and V4L2_OUT_CAP_PRESETS.
- Added new debugging ioctl ioctl VIDIOC_DBG_G_CHIP_INFO.
7.2.48. V4L2 in Linux 3.11¶
- Remove obsolete
7.2.49. V4L2 in Linux 3.14¶
- In struct
v4l2_rect, the type of
heightfields changed from _s32 to _u32.
7.2.50. V4L2 in Linux 3.15¶
- Added Software Defined Radio (SDR) Interface.
7.2.51. V4L2 in Linux 3.16¶
- Added event V4L2_EVENT_SOURCE_CHANGE.
7.2.52. V4L2 in Linux 3.17¶
7.2.53. V4L2 in Linux 3.18¶
7.2.54. V4L2 in Linux 3.19¶
7.2.55. V4L2 in Linux 4.4¶
V4L2_TUNER_SDR. The use of
V4L2_TUNER_ADCis deprecated now.
V4L2_CID_RF_TUNER_RF_GAINRF Tuner control.
- Added transmitter support for Software Defined Radio (SDR) Interface.
7.2.56. Relation of V4L2 to other Linux multimedia APIs¶
18.104.22.168. X Video Extension¶
The X Video Extension (abbreviated XVideo or just Xv) is an extension of the X Window system, implemented for example by the XFree86 project. Its scope is similar to V4L2, an API to video capture and output devices for X clients. Xv allows applications to display live video in a window, send window contents to a TV output, and capture or output still images in XPixmaps . With their implementation XFree86 makes the extension available across many operating systems and architectures.
Because the driver is embedded into the X server Xv has a number of advantages over the V4L2 video overlay interface. The driver can easily determine the overlay target, i. e. visible graphics memory or off-screen buffers for a destructive overlay. It can program the RAMDAC for a non-destructive overlay, scaling or color-keying, or the clipping functions of the video capture hardware, always in sync with drawing operations or windows moving or changing their stacking order.
To combine the advantages of Xv and V4L a special Xv driver exists in
XFree86 and XOrg, just programming any overlay capable Video4Linux
device it finds. To enable it
/etc/X11/XF86Config must contain these
Section "Module" Load "v4l" EndSection
As of XFree86 4.2 this driver still supports only V4L ioctls, however it should work just fine with all V4L2 devices through the V4L2 backward-compatibility layer. Since V4L2 permits multiple opens it is possible (if supported by the V4L2 driver) to capture video while an X client requested video overlay. Restrictions of simultaneous capturing and overlay are discussed in Video Overlay Interface apply.
Only marginally related to V4L2, XFree86 extended Xv to support hardware YUV to RGB conversion and scaling for faster video playback, and added an interface to MPEG-2 decoding hardware. This API is useful to display images captured with V4L2 devices.
22.214.171.124. Digital Video¶
V4L2 does not support digital terrestrial, cable or satellite broadcast. A separate project aiming at digital receivers exists. You can find its homepage at https://linuxtv.org. The Linux DVB API has no connection to the V4L2 API except that drivers for hybrid hardware may support both.
126.96.36.199. Audio Interfaces¶
[to do - OSS/ALSA]
7.2.57. Experimental API Elements¶
The following V4L2 API elements are currently experimental and may change in the future.
7.2.58. Obsolete API Elements¶
The following V4L2 API elements were superseded by new interfaces and should not be implemented in new drivers.
VIDIOC_S_MPEGCOMPioctls. Use Extended Controls, Extended Controls.
- VIDIOC_G_DV_PRESET, VIDIOC_S_DV_PRESET, VIDIOC_ENUM_DV_PRESETS and VIDIOC_QUERY_DV_PRESET ioctls. Use the DV Timings API (Digital Video (DV) Timings).
VIDIOC_SUBDEV_S_SELECTION, ioctl VIDIOC_SUBDEV_G_SELECTION, VIDIOC_SUBDEV_S_SELECTION.
|||This is not implemented in XFree86.|