From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: Linux and Kernel Video <video4linux-list@redhat.com>,
SPCA50x Linux Device Driver Development
<spca50x-devs@lists.sourceforge.net>
Subject: libv4l release: 0.5.6 (The UVC release)
Date: Sun, 23 Nov 2008 19:44:14 +0100 [thread overview]
Message-ID: <4929A47E.4030302@hhs.nl> (raw)
Hi All,
And another release, well 2 actually, so close together I never got a change to
release 0.5.5, but as it is out there, I decided to things properly and jump to
0.5.6 for the second fix in this announcement.
So these 2 releases are all about UVC, uvc cams support the enum_framesize
ioctrl, and gstreamer uses this and then also tries the enum_framerate ioctrl,
libv4l used to generate lots of try_fmt calls for each (emulated)
enum_framerate call, as try_fmt actually generates IO on UVC cams, this made
things slow, and worse made some buggy cams crash.
The second UVC related fix, is a work around for some UVC cams not liking
libv4l not sending a setfmt before starting the stream, if the current format
matches the to set format. This is fixed in at the driver level for 2.6.28, but
in the mean time I've added a workaround to make these cams work with libv4l
and older kernels.
libv4l-0.5.6
------------
* Always do a s_fmt on uvc cams even if this changes nothing, as not doing
the s_fmt triggers a bug in the uvcvideo driver in kernel <= 2.6.28
(with certain cams)
libv4l-0.5.5
------------
* Avoid the use of try_fmt as much as possible on UVC cams, instead use the
results of the enum_framesizes ioctl. This is because:
1) try_fmt actually causes IO with UVC cams making apps which do lot of
querrying of device capabilities slow (cheese)
2) some buggy cams don't like getting lots of UVC video probes and crash
when they do
Get it here:
http://people.atrpms.net/~hdegoede/libv4l-0.5.6.tar.gz
Regards,
Hans
--
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-11-23 18:39 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=4929A47E.4030302@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--cc=spca50x-devs@lists.sourceforge.net \
--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