Makefile: Move SHELL setup to config.mk

[oweals/u-boot.git] / doc / feature-removal-schedule.txt

diff --git a/doc/feature-removal-schedule.txt b/doc/feature-removal-schedule.txt
index e04ba2dda5a35f09479b26120ee18e63dbda66f4..58db44070f244925bbbe2527c8175ee5c7526ee2 100644 (file)
--- a/doc/feature-removal-schedule.txt
+++ b/doc/feature-removal-schedule.txt
@@ -7,6 +7,39 @@ 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
+
+Why:   When set these options enable "all" of the pads and clocks found
+       on OMAP4/5 platforms, so that the Linux Kernel does not have to.
+       It has been agreed that this goes against the U-Boot design
+       philosophy and since f3f98bb0 we have not enabled more than is
+       used in U-Boot.  The kernel has been updating drivers to enable
+       rather than assume pads/clocks have been enabled already.  Our
+       expectation is that by v2013.07 a suitable kernel shall exist that
+       does not need these options set for a reasonable I/O set to function.
+
+Who:   Tom Rini <trini@ti.com> and Sricharan R <r.sricharan@ti.com>
+
+---------------------------
+
 What:  Users of the legacy miiphy_* code
 When:  undetermined