On Saturday 09 May 2009 12:36:56 Øyvind Harboe wrote: > > Will this increase the number of help mails or decrease them ? > > > > It is not a bad idea, but may I suggest that the speed command also > > prints the > > name and value of all config settings used, or do we use speed info for > > that ? > > The idea about this tcl proc is that the target script can contain > documentation and pointers in the right direction for optimizing > performance of openocd for that target, while providing a > simple way to enable those optimisations. > > A good implementation would then provide both help & sensible > output when setting speed and querying the current speed > settings. > > Precise names/syntax tbd...
Except for the usual eye-bleeding I get from looking at tcl code (or rather the thought of having to look at tcl, in this case), that might be a good idea, if the speed->option mapping is done right. Especially having a "speed 0" that disables any optimization might be nice, as it's easier to tell a user with problems to try that option first. > the default implementation will disable ircapture and > jtag verify at speed 2. The decision whether disabling the checks is a good idea should be based on profiling results of a revision from before slaughtering (sorry, that's the way I feel here) the JTAG layer. See my other mail on the difference between IR and DR verification. Regards, Dominic
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
