---------------------------
-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: Users of the legacy miiphy_* code
When: undetermined
drivers. All new drivers should use this infrastructure, and
all old drivers should get converted to use it.
-Who: Andy Fleming <afleming@freescale.com> and driver maintainers
-
----------------------------
-
-What: boards with xxx_config targets in top level Makefile
-When: Release v2012.03
-
-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).
-
- 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: Andy Fleming <afleming@gmail.com> and driver maintainers
---------------------------
projects / oweals / u-boot.git / blobdiff