On Sun, Apr 18, 2010 at 3:31 AM, Wander Lairson <wander.lair...@gmail.com> wrote:
>> You can probably remove "reset" from the test cases as it is >> problematic anyway. Normally it is only used as a last resort >> (often only under Linux). > > Actually I do it to have known device state when changing the backend > in the tests. > I see. Unfortunately this may not work now. Pete just flag it as unsupported for Windows due to problems with different behaviors across different Windows versions. http://git.libusb.org/?p=libusb-pbatard.git;a=commitdiff;h=a14e247af5f196aa9578c5b1d63f073c1e21dfb5 @@ -1368,6 +1368,7 @@ API_EXPORTED int LIBUSB_API libusb_reset_device(libusb_device_handle *dev) * \returns 0 if no kernel driver is active * \returns 1 if a kernel driver is active * \returns LIBUSB_ERROR_NO_DEVICE if the device has been disconnected + * \returns LIBUSB_ERROR_NOT_SUPPORTED on Windows * \returns another LIBUSB_ERROR code on other failure * \see libusb_detach_kernel_driver() */ -- Xiaofan http://mcuee.blogspot.com ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ pyusb-users mailing list pyusb-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pyusb-users
