On Jul 20, 2013, at 11:23 AM, Lilk <notificati...@github.com> wrote:
> Ok. When is 1.0.17 due?
> We are using libusbx in a multi-platform application and it would be neat to
> be able to use the new hotplug api in our application (without the
> application crashing), with a graceful fallback, enabling us to just replace
> libusbx with the new version when you support Windows hotplugging). I guess
> what I am asking for if 1.0.17 if more than a couple of weeks away, if it
> would be possible to release and build something like a 1.0.16.1 with your
> weekend work patch? :D
>
There are two patches that need to be integrated. One for dealock in the Linux
backend and this one. I see no reason to get the 1.0.17 release out early in
the week if there are no objections.
A little more detail about what is happening in this case. When the device gets
disconnected the hotplug backend calls usbi_handle_disconnect which then
“completes” (makes all outstanding transfers as failed) all in-flight
transfers. The darwin backend then gets notification for the OS that
transfer(s) have failed. This is tricky to deal with because the user may have:
freed the transfer, released the device, etc. I think the best course of action
is to leave the hotplug backend code in place and “complete" any outstanding
transfers and then ignore the completion callback from the OS. I should have
the patch ready later today or sometime tomorrow.
-Nathan
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
