1The following is a list of files and features that are going to be
2removed from the U-Boot source tree.  Every entry should contain what
3exactly is going away, when it will be gone, why it is being removed,
4and who is going to be doing the work.	When the feature is removed
5from U-Boot, its corresponding entry should also be removed from this
6file.
7
8---------------------------
9
10What:	Remove CONFIG_CMD_MEMTEST from default list
11When:	Release v2013.07
12
13Why:	The "mtest" command is of little practical use (if any), and
14	experience has shown that a large number of board configu-
15	rations define useless or even dangerous start and end
16	addresses.  If not even the board maintainers are able to
17	figure out which memory range can be reliably tested, how can
18	we expect such from the end users?  As this problem comes up
19	repeatedly, we rather do not enable this command by default,
20	so only people who know what they are doing will be confronted
21	with it.
22
23Who:	Wolfgang Denk <wd@denx.de>
24
25---------------------------
26
27What:	Remove CONFIG_SYS_ENABLE_PADS_ALL and CONFIG_SYS_CLOCKS_ENABLE_ALL
28When:	Release v2013.07
29
30Why:	When set these options enable "all" of the pads and clocks found
31	on OMAP4/5 platforms, so that the Linux Kernel does not have to.
32	It has been agreed that this goes against the U-Boot design
33	philosophy and since f3f98bb0 we have not enabled more than is
34	used in U-Boot.  The kernel has been updating drivers to enable
35	rather than assume pads/clocks have been enabled already.  Our
36	expectation is that by v2013.07 a suitable kernel shall exist that
37	does not need these options set for a reasonable I/O set to function.
38
39Who:	Tom Rini <trini@ti.com> and Sricharan R <r.sricharan@ti.com>
40
41---------------------------
42
43What:	Users of the legacy miiphy_* code
44When:	undetermined
45
46Why:	We now have a PHY library, which allows everyone to share PHY
47	drivers. All new drivers should use this infrastructure, and
48	all old drivers should get converted to use it.
49
50Who:	Andy Fleming <afleming@freescale.com> and driver maintainers
51
52---------------------------
53
54What:	boards with xxx_config targets in top level Makefile
55When:	Release v2012.03
56
57Why:	We have a boards.cfg file which the vast majority of boards have
58	converted over to.  Boards that still manually run mkconfig in the
59	top level Makefile are either dead, or the maintainer doesn't care,
60	or they are doing something weird/wrong that should be fixed in a
61	different way, or they need to extend boards.cfg syntax (unlikely).
62
63	In any case, if no one cares about these boards to figure out how
64	to make boards.cfg work, then we'll just punt them.
65
66Who:	Mike Frysinger <vapier@gentoo.org>
67
68---------------------------
69
70What:	GPL cleanup
71When:	August 2009
72Why:	Over time, a couple of files have sneaked in into the U-Boot
73	source code that are either missing a valid GPL license
74	header or that carry a license that is incompatible with the
75	GPL.
76	Such files shall be removed from the U-Boot source tree.
77	See http://www.denx.de/wiki/pub/U-Boot/TaskGplCleanup/u-boot-1.1.2-files
78	for an old and probably incomplete list of such files.
79
80Who:	Wolfgang Denk <wd@denx.de> and board maintainers
81