From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Hans de Goede <hdegoede@redhat.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: nasty bug at qv4l2
Date: Sat, 25 Dec 2010 12:09:43 -0200 [thread overview]
Message-ID: <4D15FB27.7080302@redhat.com> (raw)
In-Reply-To: <4D15B5ED.8020801@redhat.com>
Em 25-12-2010 07:14, Mauro Carvalho Chehab escreveu:
> Em 24-12-2010 16:54, Hans Verkuil escreveu:
>> On Friday, December 24, 2010 15:41:10 Hans de Goede wrote:
>>> Hi,
>>>
>>> On 12/24/2010 03:20 PM, Hans Verkuil wrote:
>>>> On Friday, December 24, 2010 15:19:26 Hans de Goede wrote:
>>>>> Hi,
>>>>>
>>>>> On 12/22/2010 12:30 PM, Mauro Carvalho Chehab wrote:
>>>>>> Hans V/Hans G,
>>>>>>
>>>>>> There's a nasty bug at qv4l2 or at libv4l: it is not properly updating
>>>>>> all info, if you change the video device. On my tests with uvcvideo (video0)
>>>>>> and a gspca camera (pac7302, video1), it was showing the supported formats
>>>>>> for the uvcvideo camera when I changed from video0 to video1.
>>>>>>
>>>>>> The net result is that the image were handled with the wrong decoder
>>>>>> (instead of using fourcc V4L2_PIX_FMT_PJPG, it were using BGR3), producing
>>>>>> a wrong decoding.
>>>>>>
>>>>>> Could you please take a look on it?
<snip>
>> I wonder if Mauro got confused by the different behavior as well.
>
> I think I used the libv4l way. I'll re-try on both modes. This way, we'll know for sure if
> the issue is at libv4l or not.
Double checked: when opening in raw mode, everything works fine. However, when
opening with "libv4l" mode, it doesn't update the supported formats.
Cheers,
Mauro
next prev parent reply other threads:[~2010-12-25 14:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 11:30 nasty bug at qv4l2 Mauro Carvalho Chehab
2010-12-24 14:19 ` Hans de Goede
2010-12-24 14:20 ` Hans Verkuil
2010-12-24 14:41 ` Hans de Goede
2010-12-24 18:54 ` Hans Verkuil
2010-12-25 9:14 ` Mauro Carvalho Chehab
2010-12-25 14:09 ` Mauro Carvalho Chehab [this message]
2010-12-28 22:53 ` Hans de Goede
2010-12-29 18:40 ` Hans Verkuil
2010-12-25 8:54 ` Mauro Carvalho Chehab
2010-12-31 15:02 ` Hans de Goede
2010-12-31 15:08 ` Hans Verkuil
2010-12-31 16:18 ` Mauro Carvalho Chehab
2010-12-24 20:06 ` [PATCH] Adds the Lego Bionicle to existing sq905c Theodore Kilgore
2010-12-24 19:55 ` Hans de Goede
2010-12-25 9:20 ` Mauro Carvalho Chehab
2010-12-25 9:36 ` Hans de Goede
2010-12-25 9:52 ` Jean-Francois Moine
2010-12-25 10:24 ` Mauro Carvalho Chehab
2010-12-25 18:14 ` Theodore Kilgore
2010-12-25 18:44 ` Jean-Francois Moine
2010-12-25 17:59 ` Theodore Kilgore
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=4D15FB27.7080302@redhat.com \
--to=mchehab@redhat.com \
--cc=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.