From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: Thierry Merle <thierry.merle@free.fr>
Cc: video4linux-list@redhat.com, v4l2 library <v4l2-library@linuxtv.org>
Subject: PATCH: libv4l-update-documentation.patch
Date: Fri, 04 Jul 2008 13:20:38 +0200 [thread overview]
Message-ID: <486E0786.9050807@hhs.nl> (raw)
[-- Attachment #1: Type: text/plain, Size: 162 bytes --]
Hi,
Some documentation updates to bring the documentation up2date with the latest
changes.
Signed-off-by: Hans de Goede <j.w.r.degoede@hhs.nl>
Regards,
Hans
[-- Attachment #2: libv4l-update-docs.patch --]
[-- Type: text/plain, Size: 2401 bytes --]
Some documentation updates to bring the documentation up2date with the latest
changes.
Signed-off-by: Hans de Goede <j.w.r.degoede@hhs.nl>
diff -r 5a184775625e v4l2-apps/lib/libv4l/INSTALL
--- a/v4l2-apps/lib/libv4l/INSTALL Fri Jul 04 13:09:05 2008 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,4 +0,0 @@
-To compile simply type "make" after that you can find the compiled libraries
-and wrappers under the lib dir, public headers are under the include dir.
-
-Sorry no make install target for now.
diff -r 5a184775625e v4l2-apps/lib/libv4l/README
--- a/v4l2-apps/lib/libv4l/README Fri Jul 04 13:09:05 2008 +0200
+++ b/v4l2-apps/lib/libv4l/README Fri Jul 04 13:18:59 2008 +0200
@@ -62,10 +62,18 @@
applications is called v4l1compat.so. The preloadable libv4l1 wrapper which
adds v4l2 device compatibility to v4l1 applications is called v4l2convert.so
-Example usage:
-$ export LD_LIBRARY_PATH=`pwd`/lib
-$ export LD_PRELOAD=`pwd`/lib/v4l1compat.so
+Example usage (after install in default location):
+$ export LD_PRELOAD=/usr/local/lib/v4l1compat.so
$ camorama
+
+
+Installation Instructions
+-------------------------
+
+Simple type the following commands from the libv4l-x.y.z directory
+(adjusting DESTDIR as desired):
+make
+make install DESTDIR=/usr/local
FAQ
diff -r 5a184775625e v4l2-apps/lib/libv4l/TODO
--- a/v4l2-apps/lib/libv4l/TODO Fri Jul 04 13:09:05 2008 +0200
+++ b/v4l2-apps/lib/libv4l/TODO Fri Jul 04 13:18:59 2008 +0200
@@ -1,11 +1,3 @@
--protect open() against being called from different threads simultaniously,
- we are then thread safe except for the jpeg decompression under the following
- assumption:
- * We assume all device setup (for a single device) is done from a single
- thread
- * We assume that at the time an videodev fd gets closed all other threads
- which may have been using it have stopped using it.
-
-add support for setting / getting the number of read buffers
-add code to v4l2_read to not return frames more then say 5 seconds old
@@ -15,12 +7,6 @@
impossible for overlays) can be done, so that it will no longer be
necessary to implement CGMBUF in the kernel for each driver.
--add (configurable) support for alsa faking enum_fmt to libv4l2 ?
-
-check v4l2_field during conversion
--add make install target
-
-add conversion from bgr24 to yuv420
-
--add v4l2_dup, make re-entrant safe (for gstreamer v4l2 support)
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
reply other threads:[~2008-07-04 11:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=486E0786.9050807@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--cc=thierry.merle@free.fr \
--cc=v4l2-library@linuxtv.org \
--cc=video4linux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox