The following is a list of files and features that are going to be
removed from the U-Boot source tree. Every entry should contain what
exactly is going away, when it will be gone, why it is being removed,
-and who is going to be doing the work. When the feature is removed
+and who is going to be doing the work. When the feature is removed
from U-Boot, its corresponding entry should also be removed from this
file.
---------------------------
+What: CONFIG_SYS_ARM_WITHOUT_RELOC option
+When: After Release 2011.03
-What: "autoscr" command
-When: Release 2009-09
+Why: The implementation of U-Boot for the ARM architecture has
+ been reworked to support relocation. This allows to
+ efficiently use the same U-Boot binary image on systems with
+ different RAM sizes, and brings the implementation much more
+ in line with the code used for example on Power Architecture
+ systems (eventually allowing to merge into common code). This
+ seems especailly interesting now that ARM is getting Device
+ Tree support as well.
-Why: "autosrc" is an ugly and completely non-standard name.
- The "autoscr" command is deprecated and will be replaced by
+ All ARM boards need to be adapted to this new code, which
+ requires testing on the actual hardware, so this is a task
+ for the respective board maintainers or other users.
- the "source" command as used by other shells such as bash.
+ Please see the commit message of commit f1d2b31 for details:
- Starting with March 2009, both commands will be supported for
- a transition period of 6 months after which "autoscr" will be
- removed. During the transition period existing scripts and
- environment variable names remain untouched for maximum
- compatibiltiy; thse will be changed when support for the
- "autoscr" command get's finally dropped.
+ http://git.denx.de/?p=u-boot.git;a=commit;h=f1d2b31
-Who: Peter Tyser <ptyser@xes-inc.com>
+ Support for CONFIG_SYS_ARM_WITHOUT_RELOC will be removed
+ after release v2011.03; all boards that have not been
+ converted by then, i. e. that are still broken then, are
+ considered unmaintained and without interest for the
+ community and will be removed as well.
+
+---------------------------
+
+What: CONFIG_NET_MULTI option
+When: Release 2009-11
+
+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.
+
+ 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.
+
+Who: Ben Warren <biggerbadderben@gmail.com>
---------------------------
for an old and probably incomplete list of such files.
Who: Wolfgang Denk <wd@denx.de> and board maintainers
-
----------------------------
-
-What: Individual I2C commands
-When: April 2009
-Why: Per the U-Boot README, individual I2C commands such as "imd", "imm",
- "imw", etc are deprecated. The single "i2c" command which is
- currently enabled via CONFIG_I2C_CMD_TREE contains the same
- functionality as the individual I2C commands. The individual
- I2C commands should be removed as well as any references to
- CONFIG_I2C_CMD_TREE.
-Who: Peter Tyser <ptyser@xes-inc.com>
-
----------------------------
-
-What: Legacy NAND code
-When: April 2009
-Why: Legacy NAND code is deprecated. Similar functionality exists in
- more recent NAND code ported from the Linux kernel.
-Who: Scott Wood <scottwood@freescale.com>
projects / platform / kernel / u-boot.git / blobdiff