On Thu, Sep 11, 2014 at 12:56:26PM +0800, Xiaofan Chen wrote:
> Under Windows, if using libusb-1.0 API, then the preferred driver
> is WinUSB and it does not support setting non-default configuration
> anyway. The other supported driver libusbK.sys is the same. Only
> libusb0.sys supports setting non-default configuration but it is not
> stable to be used with libusb (1.0 API).

Do I understand it right that if we remove it altogether we'll break
jlink support on windows when libusb-win32 driver is used (which some
people prefer because it can be used as a filter driver)? JLinks are
not composite devices anyway, so currently they can work just fine
with libusb-1.0 + libusb-win32 backend, right?

Would a better solution be to call libusb_get_configuration() and only
if it returns 0 in config proceed to set_configuration(), will it work
universally?

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:[email protected]

------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to