On Sat, Jun 20, 2009 at 9:04 AM, Zach Welch<z...@superlucidity.net> wrote: > The community would be well advised to avoid these risks: use libftdi.
I think it is not that difficult for people under Linux to use libftdi. But it is certainly not so easy to do that under Windows. Maybe a mini-howto will help for Windows user who want to libftdi. (for those who want to follow the GPL, accept the extra steps and potential performance penalties). But as it stands now, FTD2XX library is the nature choices for Windows users. So probably a more detailed document to build OpenOCD under Windows with FTD2XX is needed. The GPL issue can be highlighted and that the users can only use it as a private build and not distribute the binaries. > P.S. At least one technical solution does exist that would allow FTD2XX > to be used with OpenOCD, without loading libftd2xx inside OpenOCD. > However, I think developing this feature will cost much more than simply > fixing any bugs and deficiencies with libusb and libftdi, and fixing > those libraries has more value for the broader open source community. > For this reason, my technical solution deserves to be rejected as well. Just curious what is your technical solution and how difficult it is? It may be easier than fixing libusb+libftdi. You use the word 'simply". In reality it might be not that simple to fix libusb-win32+libftdi. -- Xiaofan http://mcuee.blogspot.com _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
