Am Mittwoch, 25. Januar 2012, 00:09:28 schrieb Dan Williams: > > One oddity is that cdc-wdm seems to be looking at interfaces 3 and 4 > > too, but it shouldn't because the device list says to look only at > > interface 5 (ff/f0/ff). Any idea why that's happening? 3 and 4 should > > be driven by 'qcaux' not cdc-wdm. > > > > [ 5524.707877] cdc_acm 2-1:1.0: ttyACM0: USB ACM device > > [ 5524.708969] qcaux 2-1:1.2: qcaux converter detected > > [ 5524.709205] usb 2-1: qcaux converter now attached to ttyUSB1 > > [ 5524.709346] cdc_wdm 2-1:1.3: failed to find interrupt endpoint > > [ 5524.709356] cdc_wdm: probe of 2-1:1.3 failed with error -22 > > [ 5524.709484] cdc_wdm 2-1:1.4: failed to find interrupt endpoint > > [ 5524.709493] cdc_wdm: probe of 2-1:1.4 failed with error -22 > > [ 5524.709793] cdc_wdm 2-1:1.5: cdc-wdm0: USB WDM device > > I'm also able to talk to my Gobi 2000 card, but I need to restrict the > driver to interface 0 because there are two interfaces with interrupt > endpoints, and both are ff/ff/ff so USB_DEVICE_AND_INTERFACE_INFO > matching doesn't help us there. I suppose we could start putting the > interface number into the driver_data field and using that in > wdm_probe() if it's present. No. We are not starting with a kludge. If the existing macros for binding don't do the job, define a new macro in usbcore. Regards Oliver PS: Please trim your posts a bit -- 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
