aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/DocBook
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/DocBook')
-rw-r--r--Documentation/DocBook/v4l/capture.c.xml4
-rw-r--r--Documentation/DocBook/v4l/common.xml2
-rw-r--r--Documentation/DocBook/v4l/remote_controllers.xml9
3 files changed, 10 insertions, 5 deletions
diff --git a/Documentation/DocBook/v4l/capture.c.xml b/Documentation/DocBook/v4l/capture.c.xml
index acf46b6dac23..1c5c49a2de59 100644
--- a/Documentation/DocBook/v4l/capture.c.xml
+++ b/Documentation/DocBook/v4l/capture.c.xml
@@ -4,8 +4,8 @@
4 * 4 *
5 * This program can be used and distributed without restrictions. 5 * This program can be used and distributed without restrictions.
6 * 6 *
7 * This program were got from V4L2 API, Draft 0.20 7 * This program is provided with the V4L2 API
8 * available at: http://v4l2spec.bytesex.org/ 8 * see http://linuxtv.org/docs.php for more information
9 */ 9 */
10 10
11#include <stdio.h> 11#include <stdio.h>
diff --git a/Documentation/DocBook/v4l/common.xml b/Documentation/DocBook/v4l/common.xml
index dd598ac9a450..d6744b77e591 100644
--- a/Documentation/DocBook/v4l/common.xml
+++ b/Documentation/DocBook/v4l/common.xml
@@ -802,7 +802,7 @@ optional.</para>
802a special ioctl to enumerate all image formats supported by video 802a special ioctl to enumerate all image formats supported by video
803capture, overlay or output devices is available.<footnote> 803capture, overlay or output devices is available.<footnote>
804 <para>Enumerating formats an application has no a-priori 804 <para>Enumerating formats an application has no a-priori
805knowledge of (otherwise it could explicitely ask for them and need not 805knowledge of (otherwise it could explicitly ask for them and need not
806enumerate) seems useless, but there are applications serving as proxy 806enumerate) seems useless, but there are applications serving as proxy
807between drivers and the actual video applications for which this is 807between drivers and the actual video applications for which this is
808useful.</para> 808useful.</para>
diff --git a/Documentation/DocBook/v4l/remote_controllers.xml b/Documentation/DocBook/v4l/remote_controllers.xml
index eb669537a641..985325cbc9ad 100644
--- a/Documentation/DocBook/v4l/remote_controllers.xml
+++ b/Documentation/DocBook/v4l/remote_controllers.xml
@@ -2,8 +2,13 @@
2<section id="Remote_controllers_Intro"> 2<section id="Remote_controllers_Intro">
3<title>Introduction</title> 3<title>Introduction</title>
4 4
5<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> 5<para>Currently, most analog and digital devices have a Infrared input for remote controllers. Each
6<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> 6manufacturer has their own type of control. It is not rare for the same manufacturer to ship different
7types of controls, depending on the device.</para>
8<para>Unfortunately, for several years, there was no effort to create uniform IR keycodes for
9different devices. This caused the same IR keyname to be mapped completely differently on
10different IR devices. This resulted that the same IR keyname to be mapped completely different on
11different IR's. Due to that, V4L2 API now specifies a standard for mapping Media keys on IR.</para>
7<para>This standard should be used by both V4L/DVB drivers and userspace applications</para> 12<para>This standard should be used by both V4L/DVB drivers and userspace applications</para>
8<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> 13<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>
9 14