lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 04 Mar 2010 12:55:50 +0100 From: Hans de Goede <hdegoede@...hat.com> To: Erik Andrén <erik.andren@...il.com> CC: LKML <linux-kernel@...r.kernel.org>, Jean-Francois Moine <moinejf@...e.fr>, Linux Media Mailing List <linux-media@...r.kernel.org>, Gabriel C <nix.or.die@...glemail.com> Subject: Re: Gspca USB driver zc3xx and STV06xx probe the same device .. Hi, On 03/04/2010 12:36 PM, Erik Andrén wrote: > 2010/3/4 Hans de Goede<hdegoede@...hat.com>: >> Hi, >> >> On 03/03/2010 02:17 PM, Erik Andrén wrote: >>> >>> 2010/3/3 Gabriel C<nix.or.die@...glemail.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 ? >> > Either way is fine by me. > I can try to do it tonight. > If you could take care of this that would be great! Thanks, Hans -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists