On Sat, 28 Apr 2007, Vincent ETIENNE wrote:
No, it isn't a problem in the USB core. The device itself is messed up;
it really does report idVendor and idProduct both equal to 0.
So is it just a scary trace but without consequence that i could ignored
? May i ask you what is the device
Le Sunday 29 April 2007 13:18:31 Jiri Kosina, vous avez écrit :
Hi Vincent,
Hi Jiri,
yes, the device is messed up, but it shouldn't have any consequences for
you - the HID driver is able to correctly handle that, so as soon as we
don't need to add any extra quirks for such device,
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
On Sat, 28 Apr 2007, Jiri Kosina wrote:
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
Le Saturday 28 April 2007 21:50:30 Alan Stern, vous avez écrit :
No, it isn't a problem in the USB core. The device itself is messed up;
it really does report idVendor and idProduct both equal to 0.
Jiri, don't worry about all those other devices in the listing that also
have idVendor and
