On 2013.05.29 01:17, qse drf wrote: >> WinUsb_GetAssociatedInterface should be the magic you need. > Thanks, I'll try that.
I'm also curious with the results you'll get from bypassing libusbx altogether. As you may expect, the fact that you seem to be seeing the same behaviour with very different driver and library implementations (the libusb-win32 and libusbx-Windows backend have almost no code in common) makes me a bit suspicious about this being a libusbx/Windows issue. Especially, there's no extra logic to try to merge transfers, and we pass the data to WinUSB (or the other driver) as soon as we have it. > That's the problem. The supposedly synchronous function calls each return > success > as I call them in order: OUT 1KB, IN 16B, OUT 1KB, IN 16B > But the bus trace shows: OUT 2KB, IN 16B, IN 16B > This is the case even if I add a 5 second delay after each call to > libusb_bulk_transfer. I suppose when you do that, you don't get a 5 seconds wait for the first OUT to return success, right? If that's the case, this would tend to indicate that the issue is outside of libusbx... Hopefully, we can find out more once you try direct WinUSB calls. Regards, /Pete ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
