On 05/01/2012 08:54 PM, Peter Stuge wrote:
> Uri Lublin wrote:
>> Only if old backend api is UNSUPPORTED.
>>
>> This happens when a libusb driver (e.g. WinUSB) is installed
>> after a device has been setup/discovered (with get_device_list).
>> Is there a better way to change the backend api for a specific
>> libusb device, after WinUsb driver has been installed for that
>> device ?
> My only idea is to have a look at the hotplug code for Windows,
> perhaps it can provide some inspiration; maybe it handles this
> case, or if not then maybe a similar one.
>
Maybe there is an driver-installed event that libusb can listen to.
There may still be a race between libusb handling that event and the
application trying to access that device.
With my patch things are synchronous, so there is no race.
Thanks,
Uri.
------------------------------------------------------------------------------
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
