On Thu, Jul 09, 2009 at 05:25:50PM -0400, Alan Stern wrote: > The problem is that Daniel's device doesn't seem to fit this model. > However I don't recall seeing any usbmon logs for it. Daniel, can you > show us exactly how your device behaves? The problem were device models which did not have the STRING descriptor type 0x3 after the length information but a 0x4. This bug slipped in after we did our compliance tests, unfortunately. This firmware bug is fixed now, but there is still a number of devices out there that have the problem. The problem is: we never saw that bug anywhere else because both Windows as well as Mac OS X silently swallow that bug and default to some other value which works fine for us. But Linux failed entirely to retrieve any string from that device. So my intention was to make the Linux kernel more robust against such protocol errors, and I hope a finally did that now with my latest patch. Sorry for the hazzle. Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
