On Tue, Jun 26, 2012 at 4:52 AM, Nathan Hjelm <hje...@me.com> wrote: > If the transaction should be working the user could try to change how far in > the future the isoc transaction is scheduled for. He can do this by changing > line 1370 (in 1.0.9) from: > > frame += 4; > to > frame += 6; > > or something similar.
Now I remember there was a past discussion about this and you change the code from "frame += 2" to "frame += 4". Ref: http://libusb.6.n5.nabble.com/BUG-Darwin-isochronous-transfers-td396026.html It seems to me that different device may need to use different number. I am not so sure how to make this number user-changeable without adding a new API since it seems to be a Mac OS X only parameter. BTW, in the last post the above thread, the proposed patch seems good to have. What is your opinion? case kIOUSBTransactionTimeout: return "transaction timed out"; + case kIOUSBNotSent1Err: + return "transaction not sent"; + case kIOReturnIsoTooOld: + return "isochronous I/O request for distant past"; + case kIOReturnIsoTooNew: + return "isochronous I/O request for distant future"; case kIOReturnBadArgument: return "invalid argument"; case kIOReturnAborted: -- Xiaofan ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
