On Thu, Feb 6, 2014 at 2:42 PM, Peter Stuge <pe...@stuge.se> wrote:
> What about the users who
> have interface/$file.cfg in their configs? They'll get a warning..
> ..when instead they could be using the new and improved driver
> without having to change anything.
>
However, placing the ftdi configs in a separate dir was as much a cleanup
as a way of keeping them out of the way. The old ft2232 configs have
inconsistent naming and several duplicates. Sure, it would be nice to
seamlessly transition to the ftdi driver but is it worth keeping the
clutter? And by now, the same logic can be applied to the ftdi-configs. We
wouldn't want to move them to interface/ at this point.
By the way, it's useful to place an 'interface.cfg' in your private config
dir (~./openocd or %APPDATA%\OpenOCD) and sourcing it from the projects'
openocd.cfg. So you only have to change in one place if you switch adapters.
/Andreas
------------------------------------------------------------------------------
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