hollalinux
/
linux-sg2042
mirror of https://github.com/sophgo/linux-riscv.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

DocBook/media: Some typo fixes 

Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
This commit is contained in:
Mauro Carvalho Chehab 2009-09-15 20:27:18 -03:00
parent b131e04eae
commit 9aa08855a4
3 changed files with 10 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Documentation/DocBook/v4l/capture.c.xml
View File

@ -4,8 +4,8 @@
* *
* This program can be used and distributed without restrictions. * This program can be used and distributed without restrictions.
* *
* This program were got from V4L2 API, Draft 0.20 * This program is provided with the V4L2 API
* available at: http://v4l2spec.bytesex.org/ * see http://linuxtv.org/docs.php for more information
*/ */
#include &lt;stdio.h&gt; #include &lt;stdio.h&gt;

2
Documentation/DocBook/v4l/common.xml
View File

@ -802,7 +802,7 @@ optional.</para>
a special ioctl to enumerate all image formats supported by video a special ioctl to enumerate all image formats supported by video
capture, overlay or output devices is available.<footnote> capture, overlay or output devices is available.<footnote>
<para>Enumerating formats an application has no a-priori <para>Enumerating formats an application has no a-priori
knowledge of (otherwise it could explicitely ask for them and need not knowledge of (otherwise it could explicitly ask for them and need not
enumerate) seems useless, but there are applications serving as proxy enumerate) seems useless, but there are applications serving as proxy
between drivers and the actual video applications for which this is between drivers and the actual video applications for which this is
useful.</para> useful.</para>

9
Documentation/DocBook/v4l/remote_controllers.xml
View File

@ -2,8 +2,13 @@
<section id="Remote_controllers_Intro"> <section id="Remote_controllers_Intro">
<title>Introduction</title> <title>Introduction</title>
<para>Currently, most analog and digital devices have a Infrared input for remote controllers. Each manufacturer has their own type of control. It is not rare that the same manufacturer to ship different types of controls, depending on the device.</para> <para>Currently, most analog and digital devices have a Infrared input for remote controllers. Each
<para>Unfortunately, during several years, there weren't any effort to uniform the IR keycodes under different boards. This resulted that the same IR keyname to be mapped completely different on different IR's. Due to that, V4L2 API now specifies a standard for mapping Media keys on IR.</para> manufacturer has their own type of control. It is not rare for the same manufacturer to ship different
types of controls, depending on the device.</para>
<para>Unfortunately, for several years, there was no effort to create uniform IR keycodes for
different devices. This caused the same IR keyname to be mapped completely differently on
different IR devices. This resulted that the same IR keyname to be mapped completely different on
different IR's. Due to that, V4L2 API now specifies a standard for mapping Media keys on IR.</para>
<para>This standard should be used by both V4L/DVB drivers and userspace applications</para> <para>This standard should be used by both V4L/DVB drivers and userspace applications</para>
<para>The modules register the remote as keyboard within the linux input layer. This means that the IR key strokes will look like normal keyboard key strokes (if CONFIG_INPUT_KEYBOARD is enabled). Using the event devices (CONFIG_INPUT_EVDEV) it is possible for applications to access the remote via /dev/input/event devices.</para> <para>The modules register the remote as keyboard within the linux input layer. This means that the IR key strokes will look like normal keyboard key strokes (if CONFIG_INPUT_KEYBOARD is enabled). Using the event devices (CONFIG_INPUT_EVDEV) it is possible for applications to access the remote via /dev/input/event devices.</para>