I do not have a test setup to effectively testing this patch. We also know that
this is a work around for some 3rd party xhci controller driver/firmware bugs
where the new driver may already fix the issues.
Ref:
http://libusbx.1081486.n5.nabble.com/Libusbx-devel-Reading-device-descriptor-and-co
A few other things.
1) Warning message
$ ./examples/listdevs.exe
libusbx: warning [force_hcd_device_descriptor] could not infer VID/PID of HCD hu
b from '\\.\USB#VID_413C&PID_2513#6&2DA13301&0&2'
libusbx: warning [force_hcd_device_descriptor] could not infer VID/PID of HCD hu
b from '\\.\USB#VID_
I tried your tree, it caused stress test to fail.
$ ./tests/stress.exe
Failed to open null handle: 2
Interesting thing is that if I set LIBUSB_DEUG=4 and then run
"./tests/stress.exe -v" it will pass the tests. In that case, it will keep
printing an error message.
libusbx: error [windows_hotplu
/*
* libusb strerror code
* Copyright © 2013 Hans de Goede
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of the GNU Lesser General Public
* License as published by the Free Software Foundation; either
* version 2.1 of the License, or (at you
