On 13/06/12 14:36, Xiaofan Chen wrote: > On Wed, Jun 13, 2012 at 6:13 PM, Toby Gray<toby.g...@realvnc.com> wrote: >> Once you've opened, used and then closed the accessory (in your Android >> code) on the device then you can't open the accessory again until the device >> has sent another SET_CONFIGURATION message. > So you kind of use the SET_CONFIGURATION message as kind of > "light-weight reset".
Yes, that's it exactly. My whole email could have been summarized as enabling support for "light-weight reset" :) > libusbk.sys is based on KMDF and has the same limitation as > WinUSB in this regard (set configuration). > WinUSB seems happy to issue the SET_CONFIGURATION control transfer and as it isn't actually changing the active configuration everything seems to work fine. Is there something else which can go wrong when using WinUSB and issuing SET_CONFIGURATION which I've just been lucky in missing? Regards, Toby ------------------------------------------------------------------------------ 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
