Paul Fertser wrote: > > I think it's a bad thing to teach any users to use ftdi/ if that > > directory is intended to ever go away. > > I'm not anyone to decide, but my personal preference would be for it > to stay forever. ... I think it's easier to have them grouped > together for OpenOCD-related development.
I would like to get rid of the subdirectory so that the config file layout is uniform again. I don't think it's neccessarily bad to introduce structure among the files but.. > I'd prefer to avoid changing any project openocd.cfg configs again ..remember that you are an early adopter. What about the users who have interface/$file.cfg in their configs? They'll get a warning.. > > > 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. > > User complaints do not make anybody spend more time on the code, but I > agree writing another email to explain them ft2232 deprecation takes > time. Hopefully, that won't be needed often after the runtime warning > is merged. I also hope windows users will read README.Windows before > asking. ..when instead they could be using the new and improved driver without having to change anything. (Warn on Windows, pointing to the README.) //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
