On Tue, Sep 21, 2010 at 10:50 AM, Peter Stuge <[email protected]> wrote: > Spencer Oliver wrote: >>>> If mingw-64 are already using usb.h then that creates a bit of a >>>> problem for any interface that is expecting libusb usb.h. >>> >>> Or stop using libusb-0.1. I know it's a little too soon for 1.0 >>> everywhere just yet, but Real Soon Now. ;) >> >> I agree, but openocd will need updating to support this. > > Yes, that is true. > >> And i an not sure of the status of the win32 backend for libusb-1.0. > > A lot of code has been written and it works. Some is already in > libusb.git, but more needs to be done. There are very full-featured > binaries from the main development repo libusb-pbatard.git, they > should be working quite well, but all that code hasn't yet made it to > libusb.git and unfortunately that process is far from a simple matter > of applying patches. There's also some unrelated work which should go > into the mix, such as support for the libusb-win32 kernel driver. > > Hence, Real Soon Now. :)
I agree that going to libusb-1.0 is a good solution. I think it is possible to switch to the current libusb-1.0 WinUSB backend for libftdi-1.0 and OpenOCD. Last time I tried this combination and it worked fine. In this case, Winusb driver needs to be used. However, there are some limitations for Microsoft's WinUSB kernel driver documented in the libusb.org site (no Win2k support, no XP64 support, no 32bit/64bit Windows 2003 support, no real libusb_reset_device support). The OS limitation may not affect too many users since XP, Vista and Win7 users are not affected. No support of libusb_reset_device() may be a problem for some JTAG debuggers like J-Link. The current codes of J-Link support (and maybe others) call for usb_reset_device(). libusb_reset_device() is the corresponding libusb-1.0 API for usb_reset_device() in the libusb-0.1 API. libusb-win32 driver does not have the above OS limit and it supports usb_reset_device(). The direction for the libusb-win32 project is that we will encourage existing users to switch to libusb-1.0 API once the integration of libusb0.sys backend is done. I hope that the support of libusb0.sys (libusb-win32 kernel driver) for libusb-1.0 Windows will be integrated "Really Soon". ;-) The main focus for libusb-win32 project has been shift to mainly focus on the driver and driver installation now. -- Xiaofan _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
