From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx3.redhat.com (mx3.redhat.com [172.16.48.32]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id mB2N3oIG007376 for ; Tue, 2 Dec 2008 18:03:50 -0500 Received: from smtp1.versatel.nl (smtp1.versatel.nl [62.58.50.88]) by mx3.redhat.com (8.13.8/8.13.8) with ESMTP id mB2N3XBV005631 for ; Tue, 2 Dec 2008 18:03:33 -0500 Message-ID: <4935C04E.8090200@hhs.nl> Date: Wed, 03 Dec 2008 00:10:06 +0100 From: Hans de Goede MIME-Version: 1.0 To: Linux and Kernel Video , SPCA50x Linux Device Driver Development Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: libv4l release: 0.5.7 (The fix "the UVC release" release) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: video4linux-list-bounces@redhat.com Errors-To: video4linux-list-bounces@redhat.com List-ID: 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