summaryrefslogtreecommitdiff
path: root/doc/indevs.texi
diff options
context:
space:
mode:
authorStefano Sabatini <stefano.sabatini-lala@poste.it>2011-03-07 18:54:52 +0100
committerMichael Niedermayer <michaelni@gmx.at>2011-03-08 17:33:23 +0100
commit1a204f07602bca48cfa867db8c9f2037a8c221c7 (patch)
tree1c9c4193405153c0590f717bcc66f3fd00c68d64 /doc/indevs.texi
parentf56c4850e7d3903eb31499edb3ef8352905c6cc2 (diff)
framebuffer device demuxer
Diffstat (limited to 'doc/indevs.texi')
-rw-r--r--doc/indevs.texi25
1 files changed, 25 insertions, 0 deletions
diff --git a/doc/indevs.texi b/doc/indevs.texi
index 8e862ff6bc..1cd2dd63cb 100644
--- a/doc/indevs.texi
+++ b/doc/indevs.texi
@@ -59,6 +59,31 @@ BSD video input device.
Linux DV 1394 input device.
+@section fbdev
+
+Linux framebuffer input device.
+
+The Linux framebuffer is a graphic hardware-independent abstraction
+layer to show graphics on a computer monitor, typically on the
+console. It is accessed through a file device node, usually
+@file{/dev/fb0}.
+
+For more detailed information read the file
+Documentation/fb/framebuffer.txt included in the Linux source tree.
+
+For example, to record from the framebuffer device @file{/dev/fb0} with
+@file{ffmpeg}:
+@example
+ffmpeg -f fbdev -r 10 -i /dev/fb0 out.avi
+@end example
+
+You can take a single screenshot image with the command:
+@example
+ffmpeg -f fbdev -vframes 1 -r 1 -i /dev/fb0 screenshot.jpeg
+@end example
+
+See also @url{http://linux-fbdev.sourceforge.net/}, and fbset(1).
+
@section jack
JACK input device.