mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-11-10 15:14:43 +00:00
config_cmd_default.h: Remove CONFIG_CMD_MEMTEST
As per doc/feature-removal-schedule.txt, remove CONFIG_CMD_MEMTEST from default list of commands. Signed-off-by: Tom Rini <trini@ti.com>
This commit is contained in:
parent
d10f68ae47
commit
79cd2f814b
2 changed files with 0 additions and 18 deletions
|
@ -7,23 +7,6 @@ file.
|
|||
|
||||
---------------------------
|
||||
|
||||
What: Remove CONFIG_CMD_MEMTEST from default list
|
||||
When: Release v2013.07
|
||||
|
||||
Why: The "mtest" command is of little practical use (if any), and
|
||||
experience has shown that a large number of board configu-
|
||||
rations 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.
|
||||
|
||||
Who: Wolfgang Denk <wd@denx.de>
|
||||
|
||||
---------------------------
|
||||
|
||||
What: Remove CONFIG_SYS_ENABLE_PADS_ALL and CONFIG_SYS_CLOCKS_ENABLE_ALL
|
||||
When: Release v2013.07
|
||||
|
||||
|
|
|
@ -31,7 +31,6 @@
|
|||
#define CONFIG_CMD_LOADB /* loadb */
|
||||
#define CONFIG_CMD_LOADS /* loads */
|
||||
#define CONFIG_CMD_MEMORY /* md mm nm mw cp cmp crc base loop */
|
||||
#define CONFIG_CMD_MEMTEST /* mtest */
|
||||
#define CONFIG_CMD_MISC /* Misc functions like sleep etc*/
|
||||
#define CONFIG_CMD_NET /* bootp, tftpboot, rarpboot */
|
||||
#define CONFIG_CMD_NFS /* NFS support */
|
||||
|
|
Loading…
Reference in a new issue