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>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Announcing libv4l 0.2
Date: Sat, 28 Jun 2008 12:07:36 +0200 [thread overview]
Message-ID: <48660D68.8040506@hhs.nl> (raw)
<now with link to the new version included, sorry for the spam>
Hi All,
I'm happy to announce version 0.2 of libv4l:
http://people.atrpms.net/~hdegoede/libv4l-0.2.tar.gz
This release has the following changes (mostly bugfixes):
libv4l-0.2
----------
*** API change ***
* Change v4lconvert api so that the v4lconvert struct always gets allocated
by the library, this to make it opaque, so that we can avoid future API
and ABI changes
* Add support for yuv420 -> bgr24 conversion
* When converting from v4l2 pixelformat to v4l12 palette return
VIDEO_PALETTE_YUV420P instead of VIDEO_PALETTE_YUV420 for
V4L2_PIX_FMT_YUV420 as that is what most apps seem to expect
* override kernel v4l1 compat min / max size with our own more accurate values
* fix v4l1 munmap bug where it didn't recognise the buffer being unmapped was
our fake buffer (fixes gstreamer v4l1 support, checked with cheese)
* add support for reporting the emulated pixelformats with ENUM_FMT, this
defaults to off, and can be activated by passing a flag to enable it to
v4l2_fd_open. This gets enabled by default the wrappers.
* v4l2: mmap the real device buffers before doing conversion when DQBUF gets
called before the application has called mmap (avoid crash).
The big improvement here is that gstreamer using applications now work as long
as they use v4l1, you can force this by [re]moving
/usr/lib[64]/gstreamer-0.10/libgstvideo4linux2.so
Getting gstreamer v4l2 working is planned for 0.3, this requires adding a
v4l2_dup function (and catching dup() in the wrapper), and probably also making
things threadsafe.
Regards,
Hans
p.s.
Thierry I know you're still working on getting 0.1 into the v4l-dvb no worries,
I can split the work from 0.1 in a few seperate patches and submit those once
0.1 is in the v4l1-dvb tree.
--
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-06-28 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-28 10:07 Hans de Goede [this message]
2008-06-28 11:16 ` [Spca50x-devs] Announcing libv4l 0.2 Jean-Francois Moine
2008-06-28 11:03 ` Hans de Goede
2008-06-28 17:20 ` Gregor Jasny
2008-06-28 19:37 ` Hans de Goede
-- strict thread matches above, loose matches on Subject: below --
2008-06-28 10:06 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=48660D68.8040506@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--cc=mchehab@infradead.org \
--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