summaryrefslogtreecommitdiff
path: root/v4l2-spec/vidioc-g-fmt.sgml
diff options
context:
space:
mode:
Diffstat (limited to 'v4l2-spec/vidioc-g-fmt.sgml')
-rw-r--r--v4l2-spec/vidioc-g-fmt.sgml20
1 files changed, 10 insertions, 10 deletions
diff --git a/v4l2-spec/vidioc-g-fmt.sgml b/v4l2-spec/vidioc-g-fmt.sgml
index 0a466b2c7..7c7d1b72c 100644
--- a/v4l2-spec/vidioc-g-fmt.sgml
+++ b/v4l2-spec/vidioc-g-fmt.sgml
@@ -72,7 +72,7 @@ When the requested buffer type is not supported drivers return an
initialize the <structfield>type</structfield> field and all
fields of the respective <structfield>fmt</structfield>
union member. For details see the documentation of the various devices
-types in <xref linkend="devices">. Good practice is to query the
+types in <xref linkend="devices" />. Good practice is to query the
current parameters first, and to
modify only those parameters not suitable for the application. When
the application calls the <constant>VIDIOC_S_FMT</constant> ioctl
@@ -108,17 +108,17 @@ this ioctl.</para>
<table pgwide="1" frame="none" id="v4l2-format">
<title>struct <structname>v4l2_format</structname></title>
<tgroup cols="4">
- <colspec colname="c1">
- <colspec colname="c2">
- <colspec colname="c3">
- <colspec colname="c4">
+ <colspec colname="c1" />
+ <colspec colname="c2" />
+ <colspec colname="c3" />
+ <colspec colname="c4" />
<tbody valign="top">
<row>
<entry>&v4l2-buf-type;</entry>
<entry><structfield>type</structfield></entry>
<entry></entry>
<entry>Type of the data stream, see <xref
- linkend="v4l2-buf-type">.</entry>
+ linkend="v4l2-buf-type" />.</entry>
</row>
<row>
<entry>union</entry>
@@ -129,7 +129,7 @@ this ioctl.</para>
<entry>&v4l2-pix-format;</entry>
<entry><structfield>pix</structfield></entry>
<entry>Definition of an image format, see <xref
- linkend="pixfmt">, used by video capture and output
+ linkend="pixfmt" />, used by video capture and output
devices.</entry>
</row>
<row>
@@ -137,14 +137,14 @@ devices.</entry>
<entry>&v4l2-window;</entry>
<entry><structfield>win</structfield></entry>
<entry>Definition of an overlaid image, see <xref
- linkend="overlay">, used by video overlay devices.</entry>
+ linkend="overlay" />, used by video overlay devices.</entry>
</row>
<row>
<entry></entry>
<entry>&v4l2-vbi-format;</entry>
<entry><structfield>vbi</structfield></entry>
<entry>Raw VBI capture or output parameters. This is
-discussed in more detail in <xref linkend="raw-vbi">. Used by raw VBI
+discussed in more detail in <xref linkend="raw-vbi" />. Used by raw VBI
capture and output devices.</entry>
</row>
<row>
@@ -152,7 +152,7 @@ capture and output devices.</entry>
<entry>&v4l2-sliced-vbi-format;</entry>
<entry><structfield>sliced</structfield></entry>
<entry>Sliced VBI capture or output parameters. See
-<xref linkend="sliced"> for details. Used by sliced VBI
+<xref linkend="sliced" /> for details. Used by sliced VBI
capture and output devices.</entry>
</row>
<row>