Home Verkennen Help
Registreren Inloggen
phyus
/
uboot-vybrid_public
8
0
Vork 0
Bestanden Issues 0 Pull-aanvragen 0 Wiki
Boom: a790b5b232
Aftakkingen Labels
uboot-vybrid_pu...
/
doc
/
feature-removal-schedule.txt

feature-removal-schedule.txt 2.7 KB
Geschiedenis Ruwe

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566 
  1. The following is a list of files and features that are going to be
    2. 

  2. removed from the U-Boot source tree.  Every entry should contain what
    3. 

  3. exactly is going away, when it will be gone, why it is being removed,
    4. 

  4. and who is going to be doing the work.	When the feature is removed
    5. 

  5. from U-Boot, its corresponding entry should also be removed from this
    6. 

  6. file.
    7. 

  7. 

  8. ---------------------------
    9. 

  9. What:	CONFIG_SYS_ARM_WITHOUT_RELOC option
    10. 

  10. When:	After Release 2011.03
    11. 

  11. 

  12. Why:	The implementation of U-Boot for the ARM architecture has
    13. 

  13. 	been reworked to support relocation. This allows to
    14. 

  14. 	efficiently use the same U-Boot binary image on systems with
    15. 

  15. 	different RAM sizes, and brings the implementation much more
    16. 

  16. 	in line with the code used for example on Power Architecture
    17. 

  17. 	systems (eventually allowing to merge into common code). This
    18. 

  18. 	seems especailly interesting now that ARM is getting Device
    19. 

  19. 	Tree support as well.
    20. 

  20. 

  21. 	All ARM boards need to be adapted to this new code, which
    22. 

  22. 	requires testing on the actual hardware, so this is a task
    23. 

  23. 	for the respective board maintainers or other users.
    24. 

  24. 

  25. 	Please see the commit message of commit f1d2b31 for details:
    26. 

  26. 

  27. 	http://git.denx.de/?p=u-boot.git;a=commit;h=f1d2b31
    28. 

  28. 

  29. 	Support for CONFIG_SYS_ARM_WITHOUT_RELOC will be removed
    30. 

  30. 	after release v2011.03; all boards that have not been
    31. 

  31. 	converted by then, i. e. that are still broken then, are
    32. 

  32. 	considered unmaintained and without interest for the
    33. 

  33. 	community and will be removed as well.
    34. 

  34. 

  35. ---------------------------
    36. 

  36. 

  37. What:	CONFIG_NET_MULTI option
    38. 

  38. When:	Release 2009-11
    39. 

  39. 

  40. Why:	U-boot currently implements two network driver APIs.  New drivers with
    41. 

  41. 	the older-style implementation have not been accepted for a while, and
    42. 

  42. 	this parallel system makes the code confusing and hard to augment.
    43. 

  43. 

  44. 	All existing in-tree boards will be converted to use CONFIG_NET_MULTI
    45. 

  45. 	over the span of two releases (2009-07 and 2009-09).
    46. 

  46. 	In the 2009-11 release, all code that is compiled when CONFIG_NET_MULTI
    47. 

  47. 	is not set will be removed, and all references to CONFIG_NET_MULTI
    48. 

  48. 	will be removed, effectively making it the only API.  This should
    49. 

  49. 	provide ample time for out-of-tree users to adjust, and for tools on
    50. 

  50. 	all architectures to be made to work with weak functions.
    51. 

  51. 

  52. Who:	Ben Warren <biggerbadderben@gmail.com>
    53. 

  53. 

  54. ---------------------------
    55. 

  55. 

  56. What:	GPL cleanup
    57. 

  57. When:	August 2009
    58. 

  58. Why:	Over time, a couple of files have sneaked in into the U-Boot
    59. 

  59. 	source code that are either missing a valid GPL license
    60. 

  60. 	header or that carry a license that is incompatible with the
    61. 

  61. 	GPL.
    62. 

  62. 	Such files shall be removed from the U-Boot source tree.
    63. 

  63. 	See http://www.denx.de/wiki/pub/U-Boot/TaskGplCleanup/u-boot-1.1.2-files
    64. 

  64. 	for an old and probably incomplete list of such files.
    65. 

  65. 

  66. Who:	Wolfgang Denk <wd@denx.de> and board maintainers
    67.