On Thu, Oct 21, 2010 at 10:12 AM, Eric Shattow "Eprecocious" <lucent@xxxxxxxxx> wrote: > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0002 1x 2 bytes > bInterval 2 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x82 EP 2 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval 1 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x02 EP 2 OUT > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0010 1x 16 bytes > bInterval 1 > Device Status: 0x0000 > (Bus Powered) Seems to be very strange that device use Interrupt IN endpoint for data IN transfer. Typically for USB serial converter (CDC-ACM or Custom class), you use Bulk In endpoint for data IN transfer. I am not so sure if this the reason of the following error? [ 712.005908] mct_u232 ttyUSB0: usb_submit_urb(read bulk) failed pipe 0x40410480 err -22 -- Xiaofan -- 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
