On Fri, 4 Dec 2009, Marian wrote: > It produces this output with usbmon: > [...] lines produced by libusb-init > dcab9b00 2859906422 S Co:2:003:0 s 40 0c 5003 00f0 0001 1 = 10 > dcab9b00 2859910310 C Co:2:003:0 0 1 > > dcab9b00 2859917974 S Co:2:003:0 s 40 0c 5003 ffff 0001 1 = d0 > dcab9b00 2859921313 C Co:2:003:0 0 1 > > dcab9b00 2859921742 S Co:2:003:0 s 40 04 5001 0000 0005 5 = 91010001 93 > dcab9b00 2859930306 C Co:2:003:0 0 5 > > dcab9b00 2859938572 S Ci:2:003:0 s c0 04 5002 0000 0fa0 4000 < > dc7ce700 2861983481 C Ii:1:001:1 -2:2048 0 > dc7ce500 2862869772 C Ii:3:001:1 -2:128 0 > dcab9b00 2864939765 C Ci:2:003:0 -2 0 > > The urb status -2 is -ENOENT and shall mean: "URB was synchronously unlinked by > usb_unlink_urb" This indicates that the message timed out. You can verify this by looking at the timestamps; the URB completed 5 seconds after it was submitted. > Finally the question: How do I do "control in transfers" with libusb? Is there > some kind of example/documentation? Use the usb_control_msg() function. libusb has plenty of documentation. 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
