On Mon, 10 Oct 2011, Klaus Schwarzkopf wrote: > >> + .bDeviceClass = USB_CLASS_COMM, > >> + .bDeviceSubClass = 0, > >> + .bDeviceProtocol = 0, > > Should bDeviceClass, bDeviceSubClass, and bDeviceProtocol have the same > value like in the file multi.c? > > .bDeviceClass = USB_CLASS_MISC /* 0xEF */, > .bDeviceSubClass = 2, > .bDeviceProtocol = 1, This may or may not be relevant... The USB 2.0 spec (Table 9-8) says that if bDeviceClass is 0 then each interface specifies its own class information and the interfaces operate independently. Isn't that what you want? Alan Stern -- 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
