On 05/20/09 00:25, David Brownell wrote: > . . . >> Here is the host dmesg output: >> >> usb 1-2.7: new full speed USB device using ehci_hcd and address 44 >> usb 1-2.7: configuration #1 chosen from 2 choices >> usb 1-2.7: unsupported MDLM descriptors >> > > Means the "zaurus" driver was kicking in; that's what emits > that message. I'm a bit puzzled what it would have been > complaining about though, I guess something got mangled. > Enable DEBUG (by hand, sigh) in that driver to get a bit > more debug information. > >> usb 1-2.7: New USB device found, idVendor=0525, idProduct=a4a2 >> > > ... while in fact the "cdc_subset" driver should apply. > I'm not sure why that says > > USB_DEVICE_VER (0x0525, 0xa4a2, 0x0203, 0x0203), > > That version code is making it kick in only for pxa25x, and > at this point I have no clue why that restriction would apply. > Best to make it be USB_DEVICE(0x0525, 0xa4a2). > I was finally able to take the time to try this out, and you are correct about the versioning. If I use 'USB_DEVICE(0x0525, 0xa4a2)' in cdc_subset.c, the proper driver is loaded, and it works. Below is the dmesg output. The fact that the zaurus driver is still being loaded is a bit strange to me, but perhaps that's expected. usb 5-1: new full speed USB device using uhci_hcd and address 8 usb 5-1: configuration #1 chosen from 1 choice usb 5-1: New USB device found, idVendor=049f, idProduct=505a usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 5-1: Product: Ethernet Gadget usb 5-1: Manufacturer: Linux 2.6.28-sdg with pxa27x_udc usb0: register 'cdc_subset' at usb-0000:00:1d.0-1, Linux Device, 06:69:61:0f:65:f0 usbcore: registered new interface driver cdc_subset usbcore: registered new interface driver zaurus -- 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
