[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0704281702480.7370@jikos.suse.cz>
Date: Sat, 28 Apr 2007 17:06:11 +0200 (CEST)
From: Jiri Kosina <jkosina@...e.cz>
To: Vincent ETIENNE <ve@...ienne.net>
Cc: Greg KH <greg@...ah.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Paul Walmsley <paul@...yaka.com>,
linux-usb-devel@...ts.sourceforge.net
Subject: Re: USB HID bug (was [PROBLEM] Bonding driver in linux-2.6.21-rc6-mm1)
On Sat, 28 Apr 2007, Vincent ETIENNE wrote:
> > I now don't immediately see how this could happen - the vendor ID
> > seems to be propagated properly from hid_probe() (nothing has been
> > changed in this codepath), so this would mean that hid_probe() has
> > been passed usb_interface for which
> > le16_to_cpu(interface_to_usbdev(intf).dev->descriptor.idVendor) is
> > equal to zero ... and this definitely shouldn't happen for any sane
> > device (could the original poster please verify with lsusb, just to be
> > 100% sure?).
> You could download the result of lsusb -vvv from
> http://mail1.vetienne.net/linux/lsusb.log
Hi Vincent,
thanks for the report. It's pretty awesome though - all the USB devices
seem to have vendor and product id set to 0x0000. Greg, have you ever met
this?
linux-usb-devel added to CC (full thread here:
http://lkml.org/lkml/2007/4/27/496)
So this definitely isn't a HID-specific problem, something is confusing
the USB VID/PIDs.
--
Jiri Kosina
SUSE Labs
-
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