Paul Fertser wrote: > > Maybe clean out the ft2232 ones? > > I hope the runtime warning as proposed by Andreas will be enough;
I think it's a bad thing to teach any users to use ftdi/ if that directory is intended to ever go away. > those users that are already using ft2232 are not having real issues > (since they're using it) so why break it for them? Because nobody wants to (and rightfully so!) spend more time on the ft2232 code, and it is old cruft. If the config files are swapped (interfaces/ftdi/* vs. same in interfaces/) then I don't see what would break, except perhaps on Windows where users would then discover the Windows driver situation. //Peter ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
