feature-removal-schedule.txt 4.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123
  1. The following is a list of files and features that are going to be
  2. removed in the kernel source tree. Every entry should contain what
  3. exactly is going away, why it is happening, and who is going to be doing
  4. the work. When the feature is removed from the kernel, it should also
  5. be removed from this file.
  6. ---------------------------
  7. What: devfs
  8. When: July 2005
  9. Files: fs/devfs/*, include/linux/devfs_fs*.h and assorted devfs
  10. function calls throughout the kernel tree
  11. Why: It has been unmaintained for a number of years, has unfixable
  12. races, contains a naming policy within the kernel that is
  13. against the LSB, and can be replaced by using udev.
  14. Who: Greg Kroah-Hartman <greg@kroah.com>
  15. ---------------------------
  16. What: ACPI S4bios support
  17. When: May 2005
  18. Why: Noone uses it, and it probably does not work, anyway. swsusp is
  19. faster, more reliable, and people are actually using it.
  20. Who: Pavel Machek <pavel@suse.cz>
  21. ---------------------------
  22. What: PCI Name Database (CONFIG_PCI_NAMES)
  23. When: July 2005
  24. Why: It bloats the kernel unnecessarily, and is handled by userspace better
  25. (pciutils supports it.) Will eliminate the need to try to keep the
  26. pci.ids file in sync with the sf.net database all of the time.
  27. Who: Greg Kroah-Hartman <gregkh@suse.de>
  28. ---------------------------
  29. What: io_remap_page_range() (macro or function)
  30. When: September 2005
  31. Why: Replaced by io_remap_pfn_range() which allows more memory space
  32. addressabilty (by using a pfn) and supports sparc & sparc64
  33. iospace as part of the pfn.
  34. Who: Randy Dunlap <rddunlap@osdl.org>
  35. ---------------------------
  36. What: RAW driver (CONFIG_RAW_DRIVER)
  37. When: December 2005
  38. Why: declared obsolete since kernel 2.6.3
  39. O_DIRECT can be used instead
  40. Who: Adrian Bunk <bunk@stusta.de>
  41. ---------------------------
  42. What: RCU API moves to EXPORT_SYMBOL_GPL
  43. When: April 2006
  44. Files: include/linux/rcupdate.h, kernel/rcupdate.c
  45. Why: Outside of Linux, the only implementations of anything even
  46. vaguely resembling RCU that I am aware of are in DYNIX/ptx,
  47. VM/XA, Tornado, and K42. I do not expect anyone to port binary
  48. drivers or kernel modules from any of these, since the first two
  49. are owned by IBM and the last two are open-source research OSes.
  50. So these will move to GPL after a grace period to allow
  51. people, who might be using implementations that I am not aware
  52. of, to adjust to this upcoming change.
  53. Who: Paul E. McKenney <paulmck@us.ibm.com>
  54. ---------------------------
  55. What: IEEE1394 Audio and Music Data Transmission Protocol driver,
  56. Connection Management Procedures driver
  57. When: November 2005
  58. Files: drivers/ieee1394/{amdtp,cmp}*
  59. Why: These are incomplete, have never worked, and are better implemented
  60. in userland via raw1394 (see http://freebob.sourceforge.net/ for
  61. example.)
  62. Who: Jody McIntyre <scjody@steamballoon.com>
  63. ---------------------------
  64. What: raw1394: requests of type RAW1394_REQ_ISO_SEND, RAW1394_REQ_ISO_LISTEN
  65. When: November 2005
  66. Why: Deprecated in favour of the new ioctl-based rawiso interface, which is
  67. more efficient. You should really be using libraw1394 for raw1394
  68. access anyway.
  69. Who: Jody McIntyre <scjody@steamballoon.com>
  70. ---------------------------
  71. What: i2c sysfs name change: in1_ref, vid deprecated in favour of cpu0_vid
  72. When: November 2005
  73. Files: drivers/i2c/chips/adm1025.c, drivers/i2c/chips/adm1026.c
  74. Why: Match the other drivers' name for the same function, duplicate names
  75. will be available until removal of old names.
  76. Who: Grant Coady <gcoady@gmail.com>
  77. ---------------------------
  78. What: PCMCIA control ioctl (needed for pcmcia-cs [cardmgr, cardctl])
  79. When: November 2005
  80. Files: drivers/pcmcia/: pcmcia_ioctl.c
  81. Why: With the 16-bit PCMCIA subsystem now behaving (almost) like a
  82. normal hotpluggable bus, and with it using the default kernel
  83. infrastructure (hotplug, driver core, sysfs) keeping the PCMCIA
  84. control ioctl needed by cardmgr and cardctl from pcmcia-cs is
  85. unnecessary, and makes further cleanups and integration of the
  86. PCMCIA subsystem into the Linux kernel device driver model more
  87. difficult. The features provided by cardmgr and cardctl are either
  88. handled by the kernel itself now or are available in the new
  89. pcmciautils package available at
  90. http://kernel.org/pub/linux/utils/kernel/pcmcia/
  91. Who: Dominik Brodowski <linux@brodo.de>
  92. ---------------------------
  93. What: ip_queue and ip6_queue (old ipv4-only and ipv6-only netfilter queue)
  94. When: December 2005
  95. Why: This interface has been obsoleted by the new layer3-independent
  96. "nfnetlink_queue". The Kernel interface is compatible, so the old
  97. ip[6]tables "QUEUE" targets still work and will transparently handle
  98. all packets into nfnetlink queue number 0. Userspace users will have
  99. to link against API-compatible library on top of libnfnetlink_queue
  100. instead of the current 'libipq'.
  101. Who: Harald Welte <laforge@netfilter.org>