Stuart is correct here. The timeout of 500ms might be confusing the code. Try 5 or 10 seconds and see if things get better.
Also, with respect to your regressions: Are you sure that it’s a 10.10 / 10.9 issue, as opposed to your device attaching to the XHCI controller instead of the EHCI controller. If I were a betting man, I’d wager on the latter. HTH, Woof, Nano Urbina Build Slave Razz Software http://www.razzsoftware.com > On Feb 2, 2015, at 1:02 PM, Stuart Smith <[email protected]> wrote: > > Steve, > a couple of things. > First is, where are you specifying a timeout of just 500ms, and for what > call? Although the completion and no-data timeout parameters to > ReadPipeAsyncTO are in milliseconds, the granularity of timeout handling > is 1 second, so there's nothing gained by specifying a timeout less than > one second. > > I don't think you should ever see overrun errors for bulk transactions. An > overrun doesn't mean that your device has more data to deliver, it means > that you supplied a buffer smaller than, or not an integer multiple of the > endpoint size. Are your buffers page-aligned? > > We routinely queue up 8 to 16 bulk requests (generally calculated to keep > the controller buy for about a second), and have no problems on 10.10. I > suspect that the behavior of ReadPipeAsyncTO has not changed. Your device > is misbehaving immediately after initialization - perhaps it is being > initialized differently? I know this isn't much help, it is a bit of a > head-scratcher. > > We assign our buffers an index so we can keep track of them. We don't lose > any under various circumstances (unplugging devices, calling Abort on the > pipe, timeouts because the device has hung). > > What version of the IOUSBInterfaceInterface and IOUSBDeviceInterface are > you talking to? > > Stuart _______________________________________________ Do not post admin requests to the list. They will be ignored. Usb mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/usb/archive%40mail-archive.com This email sent to [email protected]
