On 2012.06.19 08:28, Peter Stuge wrote:
Pete Batard wrote:
the API is really only one part of it
In a library the API is almost the only thing that matters.
Ergo, you are stating that the resources a project can muster, and users
requests don't matter, as per the exact elements I was
On 2012.06.18 15:37, Peter Stuge wrote:
Hotplug isn't there yet, and Liam's problem is because the Windows
backend doesn't currently implement what the libusb-1.0 API currently
offers. Without hotplug. This is a bug in the Windows backend.
After 2 similar issues, you still don't get it, so let
On 2012.06.18 16:31, Johannes Stezenbach wrote:
Doesn't Windows (WinUSB to be precise) return an error code
indicating the device was unplugged for the submitted transfers?
If Windows only returns unlugged status for one transfer
and forgets the other ones, can't you just fix this up in the
Johannes Stezenbach wrote:
Doesn't Windows (WinUSB to be precise) return an error code
indicating the device was unplugged for the submitted transfers?
Can you provide a debug log? I assume you check for submit errors,
and I'm interested in seeing what happens to those later 13.
Thanks!
On 2012.06.18 20:31, Peter Stuge wrote:
What does GetLastError() return in the relevant cases after the
WinUsb functions return FALSE?
I'd expect [22] The device does not recognize the command.
In any case, if transfers have been submitted and are on the flying
list, and if timeouts are
