summaryrefslogtreecommitdiff
path: root/staging-specs/v4l/dev-effect.xml
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <mchehab@redhat.com>2009-09-13 20:45:57 -0300
committerMauro Carvalho Chehab <mchehab@redhat.com>2009-09-13 20:45:57 -0300
commitf4980c5e8ea66cca3a0966a35b36ba5932e5dca1 (patch)
tree583b540f02cbfd154d54cd89c5f9a6c817a878dc /staging-specs/v4l/dev-effect.xml
parentbaf2c601d974ae7d46859426c35fdae28a0e7033 (diff)
downloadmediapointer-dvb-s2-f4980c5e8ea66cca3a0966a35b36ba5932e5dca1.tar.gz
mediapointer-dvb-s2-f4980c5e8ea66cca3a0966a35b36ba5932e5dca1.tar.bz2
staging-specs: Add a staging tree for Documentation/DocBook
From: Mauro Carvalho Chehab <mchehab@redhat.com> This patch basically copies V4L and DVB DocBook specs into a single file, under a temporary staging tree. This is meant to add the set of V4L/DVB API specifications at Linux Kernel. For now, it just renames the *sgml files to *xml and creates a common body for both API's, dividing them into two parts. Later patches will add some glue for the two specs, move IR to a common part (since IR keycodes are common to both API's) and add it into linux/Documentation/DocBook. Comments and reviews are welcome. Priority: normal Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'staging-specs/v4l/dev-effect.xml')
-rw-r--r--staging-specs/v4l/dev-effect.xml25
1 files changed, 25 insertions, 0 deletions
diff --git a/staging-specs/v4l/dev-effect.xml b/staging-specs/v4l/dev-effect.xml
new file mode 100644
index 000000000..9c243beba
--- /dev/null
+++ b/staging-specs/v4l/dev-effect.xml
@@ -0,0 +1,25 @@
+ <title>Effect Devices Interface</title>
+
+ <note>
+ <title>Suspended</title>
+
+ <para>This interface has been be suspended from the V4L2 API
+implemented in Linux 2.6 until we have more experience with effect
+device interfaces.</para>
+ </note>
+
+ <para>A V4L2 video effect device can do image effects, filtering, or
+combine two or more images or image streams. For example video
+transitions or wipes. Applications send data to be processed and
+receive the result data either with &func-read; and &func-write;
+functions, or through the streaming I/O mechanism.</para>
+
+ <para>[to do]</para>
+
+ <!--
+Local Variables:
+mode: sgml
+sgml-parent-document: "v4l2.sgml"
+indent-tabs-mode: nil
+End:
+ -->