Oliver Neukum <oliver@xxxxxxxxxx> writes: > Am Dienstag, 10. Januar 2012, 22:09:35 schrieb Jonathan Nieder: >> > E.g. there is a bFirstInterface. I think this might be the >> > information to start with. But how to get this from the USB stack? I >> > don't know up to now. >> [...] >> > I don't know if this is really a bug in Linux kernel driver. Maybe the >> > USB standard says the master interface need to start with 0. > > The interfaces should be described in a union descriptor. Do you have > a full "lsusb -v" for the device? There's one in the launchpad bug: https://launchpadlibrarian.net/73443645/lsusb_v_v.txt Looks like somebody screwed up the descriptors, giving the wrong interface numbers (4 and 5 instead of 0 and 1) in the union descriptor: Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 2 Communications bInterfaceSubClass 2 Abstract (modem) bInterfaceProtocol 255 Vendor Specific (MSFT RNDIS?) iInterface 8 RNDIS Communications Control CDC Header: bcdCDC 1.10 CDC Call Management: bmCapabilities 0x00 bDataInterface 1 CDC ACM: bmCapabilities 0x00 CDC Union: bMasterInterface 4 bSlaveInterface 5 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x86 EP 6 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 9 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 10 CDC Data bInterfaceSubClass 0 Unused bInterfaceProtocol 0 iInterface 9 RNDIS Ethernet Data Bjørn -- 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
