Página inicial Explorar Ajuda
Registrar Entrar
phyus
/
uboot-vybrid_public
8
0
Fork 0
Arquivos Issues 0 Pull Requests 0 Wiki
Tree: c82730cb8e
Branches Tags
uboot-vybrid_pu...
/
doc
/
feature-removal-schedule.txt

feature-removal-schedule.txt 2.5 KB
Histórico Raw

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364 
  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. 

  10. What:	Remove CONFIG_CMD_MEMTEST from default list
    11. 

  11. When:	Release v2013.07
    12. 

  12. 

  13. Why:	The "mtest" command is of little practical use (if any), and
    14. 

  14. 	experience has shown that a large number of board configu-
    15. 

  15. 	rations define useless or even dangerous start and end
    16. 

  16. 	addresses.  If not even the board maintainers are able to
    17. 

  17. 	figure out which memory range can be reliably tested, how can
    18. 

  18. 	we expect such from the end users?  As this problem comes up
    19. 

  19. 	repeatedly, we rather do not enable this command by default,
    20. 

  20. 	so only people who know what they are doing will be confronted
    21. 

  21. 	with it.
    22. 

  22. 

  23. Who:	Wolfgang Denk <wd@denx.de>
    24. 

  24. 

  25. ---------------------------
    26. 

  26. 

  27. What:	Remove CONFIG_SYS_ENABLE_PADS_ALL and CONFIG_SYS_CLOCKS_ENABLE_ALL
    28. 

  28. When:	Release v2013.07
    29. 

  29. 

  30. Why:	When set these options enable "all" of the pads and clocks found
    31. 

  31. 	on OMAP4/5 platforms, so that the Linux Kernel does not have to.
    32. 

  32. 	It has been agreed that this goes against the U-Boot design
    33. 

  33. 	philosophy and since f3f98bb0 we have not enabled more than is
    34. 

  34. 	used in U-Boot.  The kernel has been updating drivers to enable
    35. 

  35. 	rather than assume pads/clocks have been enabled already.  Our
    36. 

  36. 	expectation is that by v2013.07 a suitable kernel shall exist that
    37. 

  37. 	does not need these options set for a reasonable I/O set to function.
    38. 

  38. 

  39. Who:	Tom Rini <trini@ti.com> and Sricharan R <r.sricharan@ti.com>
    40. 

  40. 

  41. ---------------------------
    42. 

  42. 

  43. What:	Users of the legacy miiphy_* code
    44. 

  44. When:	undetermined
    45. 

  45. 

  46. Why:	We now have a PHY library, which allows everyone to share PHY
    47. 

  47. 	drivers. All new drivers should use this infrastructure, and
    48. 

  48. 	all old drivers should get converted to use it.
    49. 

  49. 

  50. Who:	Andy Fleming <afleming@freescale.com> and driver maintainers
    51. 

  51. 

  52. ---------------------------
    53. 

  53. 

  54. What:	GPL cleanup
    55. 

  55. When:	August 2009
    56. 

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

  57. 	source code that are either missing a valid GPL license
    58. 

  58. 	header or that carry a license that is incompatible with the
    59. 

  59. 	GPL.
    60. 

  60. 	Such files shall be removed from the U-Boot source tree.
    61. 

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

  62. 	for an old and probably incomplete list of such files.
    63. 

  63. 

  64. Who:	Wolfgang Denk <wd@denx.de> and board maintainers
    65.