On Sat, May 26, 2012 at 2:13 PM, Liviu Ionescu <i...@livius.net> wrote: > > On May 26, 2012, at 07:52 , Xiaofan Chen wrote: > >>> libusb-1.0 (default) or libusb-0.1. >>> >>> The configure option to use libusb-0.1 (instead of the default libusb-1.0) >>> for stlink and Jlink is as followed. >>> --enable-libusb0 Use libusb-0.1 library for USB JTAG devices > > Peter certainly has more arguments, but, as a general comment, > wouldn't be preferable to deprecate the use of 0.1 and promote > only the newer 1.0?
Not for now, until the integration of libusb0.sys into libubsx-1.0.13 Windows, I would not recommend to deprecate 0.1, at least for Windows. The reason is that Vendor tools use their own driver and usually that driver is not WinUSB (ST-Link V2 is an exception). In order to use the vendors tools, you can not use WinUSB. In order to use OpenOCD with libusb-1.0, you can not use Vendor driver. Switching driver can be a pain if you want to use both. I mentioned the above to Peter in another reply. With integration of libusb0.sys into libusbx-1.0.13 (libusbx is a fork of libusb-1.0), then you can use libusb-win32 filter to use OpenOCD and keep the vendor driver intact. libusbx roadmap: http://sourceforge.net/apps/trac/libusbx/roadmap Disclaim: I am part of the admin team of libusb-win32, and libusbx even though I am not a developer but mainly contribute by testing and supporting. -- 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/ _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
