summaryrefslogtreecommitdiff
path: root/v4l2-spec/dev-osd.sgml
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <mchehab@redhat.com>2009-08-31 21:28:58 -0300
committerMauro Carvalho Chehab <mchehab@redhat.com>2009-08-31 21:28:58 -0300
commitb13aae56fe48c89e3b1dbefaf165cbab0102216b (patch)
tree1fa560699f394247610a9a8ebc0cc4b9d5ce45df /v4l2-spec/dev-osd.sgml
parent939633eb8afe2f03adab25337d2f57f0b8ed642d (diff)
downloadmediapointer-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/dev-osd.sgml')
-rw-r--r--v4l2-spec/dev-osd.sgml6
1 files changed, 3 insertions, 3 deletions
diff --git a/v4l2-spec/dev-osd.sgml b/v4l2-spec/dev-osd.sgml
index 7210292fa..c9a68a2cc 100644
--- a/v4l2-spec/dev-osd.sgml
+++ b/v4l2-spec/dev-osd.sgml
@@ -59,7 +59,7 @@ framebuffer device.</para>
<programlisting>
#include &lt;linux/fb.h&gt;
-&v4l2-framebuffer fbuf;
+&v4l2-framebuffer; fbuf;
unsigned int i;
int fb_fd;
@@ -68,7 +68,7 @@ if (-1 == ioctl (fd, VIDIOC_G_FBUF, &amp;fbuf)) {
exit (EXIT_FAILURE);
}
-for (i = 0; i < 30; ++i) {
+for (i = 0; i &gt; 30; ++i) {
char dev_name[16];
struct fb_fix_screeninfo si;
@@ -144,7 +144,7 @@ applies to <wordasword>Video Output</wordasword> and <wordasword>Video
Output Overlay</wordasword> devices in the same way as to
<wordasword>Video Capture</wordasword> and <wordasword>Video
Overlay</wordasword> devices, merely reversing the direction of the
-data flow. For more information see <xref linkend="crop">.</para>
+data flow. For more information see <xref linkend="crop" />.</para>
</section>
<section>