On Tue, Jun 25, 2013 at 10:34 AM, Xiaofan Chen <[email protected]> wrote: > On Mon, Jun 24, 2013 at 7:17 PM, Paul Fertser <[email protected]> wrote: >> Moreover, have you seen my commit >> 6be2a55bde5531de9897fd844c6db13e49213ae8? For the usual Windows builds >> it'll make jlink, osbdm, opendous and aice use libusb-1.x api (via the >> common layer inside OpenOCD), so do you mean it'll break the >> functionality for those who are using e.g. jlink with old vendor's >> drivers? What can be done about it? > > No it should not really break things. For single interface > device, libusb-win32 filter seems to work fine with libusbx > as well. And for those who want to use WinUSB, it is > still possible to do driver switching.
BTW, I myself will support moving to libusbx/libusb-1.0 API since it is better than libusb-0.1/libusb-win32 API. I think OpenOCD should move to use libusbx/libusb-1.0 API as much as possible. And libusb-win32 project's recommendation on the filter driver is that it should only used by more experienced users (developers). Ref: http://sourceforge.net/apps/trac/libusb-win32/wiki And right now the best supported driver for libusbx is still WinUSB, so yes it makes sense to recommend users to use Zadig to install WinUSB drivers. -- Xiaofan ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
