> How about a warning when it's _not_ explicitly enabled or disabled by > the user? Specifically, tell the users to try enabling those features > or to add explicit commands to stop the warnings. Scripts for boards > where that feature will be safe by default could add the required > commands, and users for others will be able to read the documentation > for those commands decide for themselves. > > This keeps the default safe while giving users the nudge in the > direction that you feel they will want to be headed -- eventually.
I think this is a good way to go forward. Here is a though on implementation: each target defines a default post-reset script, there is some suitable event that exists currently I'm sure. This post reset script does checks and prints out hints and warnings. -- Øyvind Harboe US toll free 1-866-980-3434 / International +47 51 63 25 00 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
