On Sat, May 26, 2012 at 12:52 PM, Xiaofan Chen <xiaof...@gmail.com> wrote: > Currently J-Link and ST-Link use the existing libusb-1.0 infrastructure > (libusb_common.h). > > There are some advantages to use libusb-win32 filter (libusb0) for > J-Link and ST-Link V1 (so that the original driver can be > used as well) compared to libusb-1.0/libusbx which use WinUSB. > > For ST-Link V2, then it is better to use libusb-1.0 > since it uses WinUSB driver which works out of the box for > libusb-1.0 Windows (tested with libusbx-1.0.11). On the > other hand, it is possible to use the libusb-win32 filter as well. > > The problem is that you can only use the same option for > ST-Link V1 and V2. >
One potential solution is to split the two in two configure option. On the other hand, this is not a big issue. Once libusb0.sys is integrated into libusbx-1.0.13 (in about three months time as per the libusbx roadmap), the way to go will be to use libusb-1.0/libusbx anyway. I think the 2nd option (to wait) is probably the preferred solution. -- 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
