fc78c7c7a1
Instead of using c:type:`struct foo <foo>`, use:
struct c:type:`foo`
This patch was generated via this shell script:
for i in `find Documentation/media -type f`; do perl -ne 'if (m/\:c\:type\:\`struct\s+(\S+)\s*\<(\S+)\>\`/) { $s=$1; $r=$2; if ($s eq $r) { s/\:c\:type\:\`struct\s+(\S+)\s*\<(\S+)\>\`/struct :c:type:`$2`/; s/struct\s+struct/struct/; s/(struct\s+\:c\:type\:\`\S+\`)\s+structure/$1/; }} print $_' <$i >a && mv a $i; done
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
37 lines
948 B
ReStructuredText
37 lines
948 B
ReStructuredText
.. -*- coding: utf-8; mode: rst -*-
|
|
|
|
.. _pixfmt:
|
|
|
|
#############
|
|
Image Formats
|
|
#############
|
|
The V4L2 API was primarily designed for devices exchanging image data
|
|
with applications. The struct :c:type:`v4l2_pix_format` and
|
|
struct :c:type:`v4l2_pix_format_mplane` structures define the
|
|
format and layout of an image in memory. The former is used with the
|
|
single-planar API, while the latter is used with the multi-planar
|
|
version (see :ref:`planar-apis`). Image formats are negotiated with
|
|
the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. (The explanations here
|
|
focus on video capturing and output, for overlay frame buffer formats
|
|
see also :ref:`VIDIOC_G_FBUF <VIDIOC_G_FBUF>`.)
|
|
|
|
|
|
.. toctree::
|
|
:maxdepth: 1
|
|
|
|
pixfmt-002
|
|
pixfmt-003
|
|
pixfmt-004
|
|
colorspaces
|
|
pixfmt-006
|
|
pixfmt-007
|
|
pixfmt-008
|
|
pixfmt-indexed
|
|
pixfmt-rgb
|
|
yuv-formats
|
|
depth-formats
|
|
pixfmt-013
|
|
sdr-formats
|
|
tch-formats
|
|
pixfmt-reserved
|