Merge branch 'master' of git://git.denx.de/u-boot-i2c

[karo-tx-uboot.git] / doc / feature-removal-schedule.txt

diff --git a/doc/feature-removal-schedule.txt b/doc/feature-removal-schedule.txt
index 13d7d9aaa1bcfccdb1a507a271b88b70a17cf413..1c79c14a3b4f7e9e7f0b715a0d397241e6c56522 100644 (file)
--- a/doc/feature-removal-schedule.txt
+++ b/doc/feature-removal-schedule.txt
@@ -7,38 +7,42 @@ file.
 
 ---------------------------
 
-What:  boards with xxx_config targets in top level Makefile
-When:  Release v2012.03
+What:  Remove unused CONFIG_SYS_MEMTEST_START/END
+When:  Release v2013.10
 
-Why:   We have a boards.cfg file which the vast majority of boards have
-       converted over to.  Boards that still manually run mkconfig in the
-       top level Makefile are either dead, or the maintainer doesn't care,
-       or they are doing something weird/wrong that should be fixed in a
-       different way, or they need to extend boards.cfg syntax (unlikely).
+Why:   As the 'mtest' command is no longer default, a number of platforms
+       have not opted to turn the command back on and thus provide unused
+       defines (which are likely to be propogated to new platforms from
+       copy/paste).  Remove these defines when unused.
 
-       In any case, if no one cares about these boards to figure out how
-       to make boards.cfg work, then we'll just punt them.
-
-Who:   Mike Frysinger <vapier@gentoo.org>
+Who:   Tom Rini <trini@ti.com>
 
 ---------------------------
 
-What:  CONFIG_NET_MULTI option
-When:  Release 2009-11
+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>
+
+---------------------------
 
-Why:   U-boot currently implements two network driver APIs.  New drivers with
-       the older-style implementation have not been accepted for a while, and
-       this parallel system makes the code confusing and hard to augment.
+What:  Users of the legacy miiphy_* code
+When:  undetermined
 
-       All existing in-tree boards will be converted to use CONFIG_NET_MULTI
-       over the span of two releases (2009-07 and 2009-09).
-       In the 2009-11 release, all code that is compiled when CONFIG_NET_MULTI
-       is not set will be removed, and all references to CONFIG_NET_MULTI
-       will be removed, effectively making it the only API.  This should
-       provide ample time for out-of-tree users to adjust, and for tools on
-       all architectures to be made to work with weak functions.
+Why:   We now have a PHY library, which allows everyone to share PHY
+       drivers. All new drivers should use this infrastructure, and
+       all old drivers should get converted to use it.
 
-Who:   Ben Warren <biggerbadderben@gmail.com>
+Who:   Andy Fleming <afleming@freescale.com> and driver maintainers
 
 ---------------------------