From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: v4l2 library <v4l2-library@linuxtv.org>,
video4linux-list@redhat.com,
SPCA50x Linux Device Driver Development
<spca50x-devs@lists.sourceforge.net>
Subject: Announcing libv4l 0.3.8
Date: Sun, 03 Aug 2008 18:42:23 +0200 [thread overview]
Message-ID: <4895DFEF.1010105@hhs.nl> (raw)
Hi All,
I've installed a pci bttv tv card in my machine to test libv4l xawtv patches
and I've found that libv4l was being to strict with the circumstances under
which it allowed changing the fmt and changing between read / mmap mode.
This new version fixes this:
http://people.atrpms.net/~hdegoede/libv4l-0.4.0.tar.gz
Full list of changes:
libv4l-0.4.0
------------
* Be more relaxed in our checks for mixing read and mmap access, we were
being more strict in this then certain kernel drivers (bttv) making xawtv
unhappy
* With some drivers the buffers must be mapped before queuing, so when
converting map the (real) buffers before calling the qbuf ioctl
* Add support for conversion to RGB24 (before we only supported BGR24) based
on a patch by Jean-Francois Moine
* When the hardware supports a format natively prefer using the native
version over converting from another supported format
* Various Makefile and pkgconfig file improvements by Gregor Jasny (Debian)
* Drop the appl-patches dir, all application patches are now available and
tracked here: http://linuxtv.org/v4lwiki/index.php/Libv4l_Progress
Regards,
Hans
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next reply other threads:[~2008-08-03 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-03 16:42 Hans de Goede [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-29 22:01 Announcing libv4l 0.3.8 Hans de Goede
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=4895DFEF.1010105@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--cc=spca50x-devs@lists.sourceforge.net \
--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