On Tue, Jun 26, 2012 at 4:52 AM, Rich von Lehe <[email protected]> wrote: > In lieu of set_configuration in this case (there is only one config), > one process would claim_interface 0 and the other process would > claim_interface 1. I have a suspicion that the underlying > implementation in Libusb is locking the device with the first call to > claim_interface, since I get permission errors when making that call > from the 2nd process. I saw an email on this list saying as much for > the OpenBSD implementation, though I'm on Windows/WinUSB. > > Is it best to go to the Libusb code and see if I can figure if that's > really the case? >
BTW, pyusb supports libusb-win32 under Windows as well, so you can use that one instead of WinUSB to see if that helps or not. -- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/libusbx-devel
