Hi, Paul-Kenji! >>>>> "PCF" == Paul-Kenji Cahier Furuya writes: > Here is the trace from usbmon: [...] > 12s later(with the device still emitting data): fails with cat: /dev/ttyACM0: > Input/output error > Sat Oct 23 23:17:45 CEST 2010 -- ef306e80 249746600 S Ii:2:009:2 -115:128 64 < > Sat Oct 23 23:17:45 CEST 2010 -- ee60bb00 249747326 S Co:2:009:0 s 21 22 0003 > 0000 0000 0 > Sat Oct 23 23:17:52 CEST 2010 -- ee60bb00 256737621 C Co:2:009:0 -84 0 Strange, int the log it was: [496322.483695] drivers/usb/class/cdc-acm.c: acm_control_msg: rq: 0x22 val: 0x0 len: 0x0 result: 0 > Sat Oct 23 23:17:52 CEST 2010 -- ef306e80 256739105 C Ii:2:009:2 -2:128 0 And this is full_bailout: usb_kill_urb(acm->ctrlurb); > Sat Oct 23 23:17:57 CEST 2010 -- ee854880 256754727 S Co:2:009:0 s 21 22 0000 > 0000 0000 0 > Sat Oct 23 23:17:57 CEST 2010 -- ee854880 261765255 C Co:2:009:0 -84 0 But well, my guess was wrong. And you can try to hack cdc-acm driver to ignore the control transfer result to start bulk readings. It may help in you case. -- WBR, Yauheni Kaliuta -- 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
