On Fri, Mar 08, 2013 at 09:51:32PM +0100, Wolfgang Denk wrote:
The "mtest" command is of little practical use (if any), and experience has shown that a large number of board configurations define useless or even dangerous start and end addresses. If not even the board maintainers are able to figure out which memory range can be reliably tested, how can we expect such from the end users? As this problem comes up repeatedly, we rather do not enable this command by default, so only people who know what they are doing will be confronted with it.
As this changes the user interface, we allow for a grace period before this change takes effect. For now, we make "mtest" configurable through the CONFIG_CMD_MEMTEST variable, which is defined in include/config_cmd_default.h; we also add an entry to doc/feature-removal-schedule.txt which announces the removal of this default setting in two releases from now, i. e. with v2013.07.
Signed-off-by: Wolfgang Denk wd@denx.de Cc: Tom Rini trini@ti.com
v2: - Fix spelling errors in doc/README.memory-test; kudos to Ira W. Snyder
Applied to u-boot/master, thanks!