CC libusbx. Maybe Pete and others can give you better answers there.

On Tue, Jun 5, 2012 at 11:09 PM, Liam Staskawicz <lst...@gmail.com> wrote:
> Hi,
>
> I'm using libusb 1.0.9 on windows7 (building a Qt app with msvc2010), and
> things are largely working just as expected - thanks for a lovely library
> with winusb support!
>
> My device is vendor specific, with one IN and out OUT bulk endpoint, each 64
> bytes. When my device is opened, I submit 16 IN transfers to make sure I can
> keep the system busy servicing usb IN traffic. Sending and receiving using
> the asynchronous API is no problem, however, when my device is unplugged, I
> would ideally like to cancel all outstanding transfers, wait for them to
> complete, and then close the device. This works as intended on OS X, but on
> Windows I only ever see 3 transfers complete so I don't have a good way to
> know whether all outstanding transfers are complete. If I limit the
> outstanding requests to 3, then I can detect the case in which all requests
> have completed, and close the device successfully.
>
> A couple questions:
>
> is this an appropriate way to manage the process of closing my device?
> does this issue sound familiar to anybody?
> any suggested workarounds?
>

libusbx-2.0 will add hotplug support and that should help.
http://sourceforge.net/apps/trac/libusbx/roadmap

More about libusbx:
http://www.libusbx.org/

libusbx mailing list subscription:
https://lists.sourceforge.net/lists/listinfo/libusbx-devel


-- 
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

Reply via email to