From: Hans de Goede <hdegoede@redhat.com>
To: "Erik Andrén" <erik.andren@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Jean-Francois Moine <moinejf@free.fr>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Gabriel C <nix.or.die@googlemail.com>
Subject: Re: Gspca USB driver zc3xx and STV06xx probe the same device ..
Date: Thu, 04 Mar 2010 12:19:38 +0100 [thread overview]
Message-ID: <4B8F974A.4090001@redhat.com> (raw)
In-Reply-To: <62e5edd41003030517g6fa9b64awdf18578d6c5db7e@mail.gmail.com>
Hi,
On 03/03/2010 02:17 PM, Erik Andrén wrote:
> 2010/3/3 Gabriel C<nix.or.die@googlemail.com>:
>> Hello,
>>
>> I own a QuickCam Messanger webcam.. I didn't used it in ages but today
>> I plugged it in..
>> ( Device 002: ID 046d:08da Logitech, Inc. QuickCam Messanger )
>>
>> Now zc3xx and stv06xx are starting both to probe the device .. In
>> 2.6.33 that result in a not working webcam.
>> ( rmmod both&& modprobe zc3xx one seems to fix that )
>>
>> On current git head zc3xx works fine even when both are probing the device.
>>
>> Also I noticed stv06xx fails anyway for my webcam with this error:
>> ....
>>
>> [ 360.910243] STV06xx: Configuring camera
>> [ 360.910244] STV06xx: st6422 sensor detected
>> [ 360.910245] STV06xx: Initializing camera
>> [ 361.161948] STV06xx: probe of 6-1:1.0 failed with error -32
>> [ 361.161976] usbcore: registered new interface driver STV06xx
>> [ 361.161978] STV06xx: registered
>> .....
>>
>> Next thing is stv06xx tells it is an st6422 sensor and does not work
>> with it while zc3xx tells it is an HV7131R(c) sensor and works fine
>> with it.
>>
>> What is right ?
>
> Hans,
> As you added support for the st6422 sensor to the stv06xx subdriver I
> imagine you best know what's going on.
>
I took the USB-ID in question from the out of tree v4l1 driver I was basing my
st6422 work on. Looking at the other ID's (which are very close together) and
combining that with this bug report, I think it is safe to say that the USB-ID
in question should be removed from the stv06xx driver.
Erik will you handle this, or shall I ?
Regards,
Hans
next prev parent reply other threads:[~2010-03-04 11:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 12:45 Gspca USB driver zc3xx and STV06xx probe the same device Gabriel C
2010-03-03 13:17 ` Erik Andrén
2010-03-04 11:19 ` Hans de Goede [this message]
2010-03-04 11:36 ` Erik Andrén
2010-03-04 11:55 ` Hans de Goede
2010-03-06 19:46 ` Erik Andrén
2010-03-07 14:36 ` Gabriel C
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=4B8F974A.4090001@redhat.com \
--to=hdegoede@redhat.com \
--cc=erik.andren@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=moinejf@free.fr \
--cc=nix.or.die@googlemail.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.