public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
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.7 (The fix "the UVC release" release)
Date: Wed, 03 Dec 2008 00:10:06 +0100	[thread overview]
Message-ID: <4935C04E.8090200@hhs.nl> (raw)

<resent with correct version no in subject, sorry about the spam>

Hi All,

So after 2 days of debugging (many thanks for the patience of all reporters and
for all the tests they have run) I've finally managed to pinpoint and fix a
nasty (and stupid, completely my fault) bug in the special try_fmt handling for
uvc cams.

This bug is present in the 0.5.5 and 0.5.6 releases every one is urged to
upgrade to 0.5.7 asap!

The problem is that the enumframesize results try_fmt replacement for uvccams
was dependend upon the enumframesize results being sorted in a particular
order, which happened to be the case with my test cam.

This was causing issues with quite a few uvc cams, this release fixes this.

libv4l-0.5.7
------------
* Fix a nasty (and stupid) bug in the special try_fmt handling for UVC cams
* Add some more verbose logging of various calls when asking libv4l to log
   calls to a file, to assist in (future) debugging

Get it here:
http://people.atrpms.net/~hdegoede/libv4l-0.5.7.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-12-02 23:03 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=4935C04E.8090200@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