Merge tag 'u-boot-imx-next-20241126' of https://gitlab.denx.de/u-boot/custodians...

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

diff --git a/doc/feature-removal-schedule.txt b/doc/feature-removal-schedule.txt
index ffe261513c86867b3b6a0c53191ad868e02b4532..546d2da17d986d411b52e03d046fec2b38c806c6 100644 (file)
--- a/doc/feature-removal-schedule.txt
+++ b/doc/feature-removal-schedule.txt
@@ -6,50 +6,15 @@ 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
 
-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.
+What:  Users of the legacy miiphy_* code
+When:  undetermined
 
-       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.
+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.
 
-       Please see the commit message of commit f1d2b31 for details:
-
-       http://git.denx.de/?p=u-boot.git;a=commit;h=f1d2b31
-
-       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 <[email protected]>
+Who:   Andy Fleming <[email protected]> and driver maintainers
 
 ---------------------------