All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: nasty bug at qv4l2
Date: Fri, 24 Dec 2010 15:41:10 +0100	[thread overview]
Message-ID: <4D14B106.2000502@redhat.com> (raw)
In-Reply-To: <201012241520.01460.hverkuil@xs4all.nl>

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?
>>
>> I'm pretty sure this is not a libv4l issue (other apps which allows witching
>> the source work fine), but rather a qv4l2 problem, esp. as it uses libv4lconvert
>> directly rather then going through libv4l (iirc).
>
> And I'm pretty sure it isn't a qv4l2 issue :-)
>
> For the record: qv4l2 can open a device node either in 'raw' mode bypassing libv4l
> and using v4lconvert to convert unsupported pixformats, or in 'wrapped' mode where
> libv4l is used for all device node accesses.
>

Interesting, how does it switch between the modes? Mauro were you using wrapped mode
or raw mode when you saw this ?

Regards,

hans

  reply	other threads:[~2010-12-24 14:35 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 [this message]
2010-12-24 18:54       ` Hans Verkuil
2010-12-25  9:14         ` Mauro Carvalho Chehab
2010-12-25 14:09           ` Mauro Carvalho Chehab
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=4D14B106.2000502@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@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 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.