Hi, On 05/14/2012 12:41 AM, Pete Batard wrote: > So, in summary, the issue is: > - you have developed a custom solution/layer to add hotplug to libusbx, > even as libusbx is going to officially implement the very same feature, > internally, in a manner that is likely to be quite different from yours.
Yes and no, yes we do hotplug, no we've not added hotplug to libusbx, just like we currently do in Linux, we listen to OS generated events telling us that a new device has shown up and we act on that, we do this completely outside libusbx. Only once we have learned there is a new device, we want to use libusbx to talk to it. In essence what happens from the libusbx pov is: 1) libusbx gets initialized 2) libusb_get_device_list() gets called 3) a new USB device gets plugged in 4) that new device gets the winusb driver bound to it 5) libusb_get_device_list() gets called again And after 5 we expect libusbx to both know about the device, and for the app to be able to use the device through libusbx. This seems like a reasonable thing to expect to me, even of a not hotplug aware libusbx. Regards, Hans ------------------------------------------------------------------------------ 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
