diff options
author | Mauro Carvalho Chehab <mchehab@redhat.com> | 2009-08-31 21:28:58 -0300 |
---|---|---|
committer | Mauro Carvalho Chehab <mchehab@redhat.com> | 2009-08-31 21:28:58 -0300 |
commit | b13aae56fe48c89e3b1dbefaf165cbab0102216b (patch) | |
tree | 1fa560699f394247610a9a8ebc0cc4b9d5ce45df /v4l2-spec/vidioc-enuminput.sgml | |
parent | 939633eb8afe2f03adab25337d2f57f0b8ed642d (diff) | |
download | mediapointer-dvb-s2-b13aae56fe48c89e3b1dbefaf165cbab0102216b.tar.gz mediapointer-dvb-s2-b13aae56fe48c89e3b1dbefaf165cbab0102216b.tar.bz2 |
v4l2-spec: convert it to use DocBook XML 4.1.2
From: Mauro Carvalho Chehab <mchehab@redhat.com>
DocBook XML 4.1.2 is the docbook dialect spoken at Linux kernel. By
using it, we can now consider adding V4L2 API docs at the kernel tree.
As a bonus, added support for xmlto, with seems to be better supported
nowadays.
Another additional bounus is that two new Makefile targets were added:
make man - Create V4L2 API man pages
make man_install - Install V4L2 API man pages
By allowing the addition of V4L2 manpages, it is now easier for
developer to quickly check about a V4L2 API or libv4l2 call syntax and
expected return values.
Priority: normal
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'v4l2-spec/vidioc-enuminput.sgml')
-rw-r--r-- | v4l2-spec/vidioc-enuminput.sgml | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/v4l2-spec/vidioc-enuminput.sgml b/v4l2-spec/vidioc-enuminput.sgml index 824b47e5f..414856b82 100644 --- a/v4l2-spec/vidioc-enuminput.sgml +++ b/v4l2-spec/vidioc-enuminput.sgml @@ -79,7 +79,7 @@ for the user, preferably the connector label on the device itself.</entry> <entry>__u32</entry> <entry><structfield>type</structfield></entry> <entry>Type of the input, see <xref - linkend="input-type">.</entry> + linkend="input-type" />.</entry> </row> <row> <entry>__u32</entry> @@ -94,7 +94,7 @@ shall not interpret this as lack of audio support. Some drivers automatically select audio sources and do not enumerate them since there is no choice anyway.</para><para>For details on audio inputs and how to select the current input see <xref - linkend="audio">.</para></entry> + linkend="audio" />.</para></entry> </row> <row> <entry>__u32</entry> @@ -104,7 +104,7 @@ demodulators). When the <structfield>type</structfield> is set to <constant>V4L2_INPUT_TYPE_TUNER</constant> this is an RF connector and this field identifies the tuner. It corresponds to &v4l2-tuner; field <structfield>index</structfield>. For details on -tuners see <xref linkend="tuner">.</entry> +tuners see <xref linkend="tuner" />.</entry> </row> <row> <entry>&v4l2-std-id;</entry> @@ -112,13 +112,13 @@ tuners see <xref linkend="tuner">.</entry> <entry>Every video input supports one or more different video standards. This field is a set of all supported standards. For details on video standards and how to switch see <xref -linkend="standard">.</entry> +linkend="standard" />.</entry> </row> <row> <entry>__u32</entry> <entry><structfield>status</structfield></entry> <entry>This field provides status information about the -input. See <xref linkend="input-status"> for flags. +input. See <xref linkend="input-status" /> for flags. With the exception of the sensor orientation bits <structfield>status</structfield> is only valid when this is the current input.</entry> </row> @@ -162,11 +162,11 @@ is OK." --> <table frame="none" pgwide="1" id="input-status"> <title>Input Status Flags</title> <tgroup cols="3"> - <colspec colname="c1"> - <colspec colname="c2" align="center"> - <colspec colname="c3"> + <colspec colname="c1" /> + <colspec colname="c2" align="center" /> + <colspec colname="c3" /> <spanspec namest="c1" nameend="c3" spanname="hspan" - align="left"> + align="left" /> <tbody valign="top"> <row> <entry spanname="hspan">General</entry> |