Spencer Oliver wrote: >>> This code was added for cases where high speed support is not >>> detected by configure and BUILD_FT2232_HIGHSPEED is not defined. >> >> Why? So that OpenOCD can be built against three year old versions >> of the FTDI driver? Is that a high priority? > > Feel free to make that change if you feel it is important.
I just might, but libusb-1.0 Windows support is blocking that in my thinking. > My point is that autoconf will take care of all this if the correct > usb header is installed/found. Except that there's stuff in the code too. > This is not the cause of the problem Xiaofan has, his toolchain is > causing the problem. Nod, I got that. >>> 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. :) //Peter _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
