Michael Fischer wrote: > The instruction can be found here, and use libftdi and libftd2xx: > http://forum.sparkfun.com/viewtopic.php?t=11221 > > But the problem is that the normal user want to have a working solution > and do not / can not build OpenOCD by itself. > > I think if libftdi will be used with the less performance as ftd2xx > the new OpenOCD will not be used. Therefore the performance problem > and the 64 bit problem must be solved to get an equivalent to the > FTD2XX driver. Here I think the performance is the problem not the > 64 bit first. > There is no difference between 0.1 and 0.2 - neither licensing nor performance has changed, so I do not see why users would choose not to use the new version?
BTW: one possible solution for 64-bit windows would be to ship an openocd appliance - ie. a VM image containing a minimal linux system together with openocd & libraries. Users would need to install VMware player or SUN Virtualbox to use that, but would get a clean, 100% legal and working solution without the need to compile/install anything beside the VM. cu Michael _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
