Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 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 | --------------------------- |
| 8 | |
Jiri Slaby | 9e40210 | 2007-05-08 00:36:28 -0700 | [diff] [blame] | 9 | What: MXSER |
| 10 | When: December 2007 |
| 11 | Why: Old mxser driver is obsoleted by the mxser_new. Give it some time yet |
| 12 | and remove it. |
| 13 | Who: Jiri Slaby <jirislaby@gmail.com> |
| 14 | |
| 15 | --------------------------- |
| 16 | |
Hans Verkuil | 3f3f6a5 | 2007-03-10 08:10:11 -0300 | [diff] [blame] | 17 | What: V4L2 VIDIOC_G_MPEGCOMP and VIDIOC_S_MPEGCOMP |
| 18 | When: October 2007 |
| 19 | Why: Broken attempt to set MPEG compression parameters. These ioctls are |
| 20 | not able to implement the wide variety of parameters that can be set |
| 21 | by hardware MPEG encoders. A new MPEG control mechanism was created |
| 22 | in kernel 2.6.18 that replaces these ioctls. See the V4L2 specification |
| 23 | (section 1.9: Extended controls) for more information on this topic. |
| 24 | Who: Hans Verkuil <hverkuil@xs4all.nl> and |
| 25 | Mauro Carvalho Chehab <mchehab@infradead.org> |
| 26 | |
| 27 | --------------------------- |
| 28 | |
Alan Stern | 471d055 | 2007-07-12 16:55:07 -0400 | [diff] [blame] | 29 | What: dev->power.power_state |
Pavel Machek | 1ebfd79 | 2006-08-30 13:50:27 -0700 | [diff] [blame] | 30 | When: July 2007 |
| 31 | Why: Broken design for runtime control over driver power states, confusing |
| 32 | driver-internal runtime power management with: mechanisms to support |
| 33 | system-wide sleep state transitions; event codes that distinguish |
| 34 | different phases of swsusp "sleep" transitions; and userspace policy |
| 35 | inputs. This framework was never widely used, and most attempts to |
| 36 | use it were broken. Drivers should instead be exposing domain-specific |
| 37 | interfaces either to kernel or to userspace. |
| 38 | Who: Pavel Machek <pavel@suse.cz> |
| 39 | |
| 40 | --------------------------- |
| 41 | |
Christoph Hellwig | a6bcbc2 | 2007-04-30 00:05:48 +0200 | [diff] [blame] | 42 | What: old NCR53C9x driver |
| 43 | When: October 2007 |
| 44 | Why: Replaced by the much better esp_scsi driver. Actual low-level |
Christoph Hellwig | ed56047 | 2007-05-13 22:48:31 +0200 | [diff] [blame] | 45 | driver can be ported over almost trivially. |
Christoph Hellwig | a6bcbc2 | 2007-04-30 00:05:48 +0200 | [diff] [blame] | 46 | Who: David Miller <davem@davemloft.net> |
| 47 | Christoph Hellwig <hch@lst.de> |
| 48 | |
| 49 | --------------------------- |
| 50 | |
Mauro Carvalho Chehab | 875c296 | 2005-11-08 21:38:53 -0800 | [diff] [blame] | 51 | What: Video4Linux API 1 ioctls and video_decoder.h from Video devices. |
Mauro Carvalho Chehab | 48c06d5 | 2006-09-06 09:29:00 -0300 | [diff] [blame] | 52 | When: December 2006 |
Andy Whitcroft | 0a920b5 | 2007-06-01 00:46:48 -0700 | [diff] [blame] | 53 | Files: include/linux/video_decoder.h |
Andy Whitcroft | f0a594c | 2007-07-19 01:48:34 -0700 | [diff] [blame] | 54 | Check: include/linux/video_decoder.h |
Mauro Carvalho Chehab | 875c296 | 2005-11-08 21:38:53 -0800 | [diff] [blame] | 55 | Why: V4L1 AP1 was replaced by V4L2 API. during migration from 2.4 to 2.6 |
| 56 | series. The old API have lots of drawbacks and don't provide enough |
| 57 | means to work with all video and audio standards. The newer API is |
| 58 | already available on the main drivers and should be used instead. |
| 59 | Newer drivers should use v4l_compat_translate_ioctl function to handle |
| 60 | old calls, replacing to newer ones. |
| 61 | Decoder iocts are using internally to allow video drivers to |
| 62 | communicate with video decoders. This should also be improved to allow |
| 63 | V4L2 calls being translated into compatible internal ioctls. |
| 64 | Who: Mauro Carvalho Chehab <mchehab@brturbo.com.br> |
| 65 | |
| 66 | --------------------------- |
| 67 | |
Dominik Brodowski | bf45d9b0 | 2005-07-07 17:58:58 -0700 | [diff] [blame] | 68 | What: PCMCIA control ioctl (needed for pcmcia-cs [cardmgr, cardctl]) |
| 69 | When: November 2005 |
| 70 | Files: drivers/pcmcia/: pcmcia_ioctl.c |
| 71 | Why: With the 16-bit PCMCIA subsystem now behaving (almost) like a |
| 72 | normal hotpluggable bus, and with it using the default kernel |
| 73 | infrastructure (hotplug, driver core, sysfs) keeping the PCMCIA |
| 74 | control ioctl needed by cardmgr and cardctl from pcmcia-cs is |
| 75 | unnecessary, and makes further cleanups and integration of the |
| 76 | PCMCIA subsystem into the Linux kernel device driver model more |
| 77 | difficult. The features provided by cardmgr and cardctl are either |
| 78 | handled by the kernel itself now or are available in the new |
| 79 | pcmciautils package available at |
| 80 | http://kernel.org/pub/linux/utils/kernel/pcmcia/ |
| 81 | Who: Dominik Brodowski <linux@brodo.de> |
Harald Welte | 7af4cc3 | 2005-08-09 19:44:15 -0700 | [diff] [blame] | 82 | |
| 83 | --------------------------- |
| 84 | |
Christoph Hellwig | ac51589 | 2006-03-24 03:18:22 -0800 | [diff] [blame] | 85 | What: remove EXPORT_SYMBOL(kernel_thread) |
| 86 | When: August 2006 |
| 87 | Files: arch/*/kernel/*_ksyms.c |
Andy Whitcroft | f0a594c | 2007-07-19 01:48:34 -0700 | [diff] [blame] | 88 | Check: kernel_thread |
Christoph Hellwig | ac51589 | 2006-03-24 03:18:22 -0800 | [diff] [blame] | 89 | Why: kernel_thread is a low-level implementation detail. Drivers should |
| 90 | use the <linux/kthread.h> API instead which shields them from |
| 91 | implementation details and provides a higherlevel interface that |
| 92 | prevents bugs and code duplication |
| 93 | Who: Christoph Hellwig <hch@lst.de> |
| 94 | |
| 95 | --------------------------- |
| 96 | |
Ingo Molnar | a9df3d0 | 2006-01-14 13:21:33 -0800 | [diff] [blame] | 97 | What: CONFIG_FORCED_INLINING |
| 98 | When: June 2006 |
| 99 | Why: Config option is there to see if gcc is good enough. (in january |
| 100 | 2006). If it is, the behavior should just be the default. If it's not, |
| 101 | the option should just go away entirely. |
| 102 | Who: Arjan van de Ven |
| 103 | |
| 104 | --------------------------- |
| 105 | |
Bunk | c0d3c0c | 2006-02-07 01:43:31 -0500 | [diff] [blame] | 106 | What: eepro100 network driver |
| 107 | When: January 2007 |
| 108 | Why: replaced by the e100 driver |
| 109 | Who: Adrian Bunk <bunk@stusta.de> |
Jeff Garzik | 3c9b3a8 | 2006-02-07 01:47:12 -0500 | [diff] [blame] | 110 | |
| 111 | --------------------------- |
| 112 | |
Arjan van de Ven | f71d20e | 2006-06-28 04:26:45 -0700 | [diff] [blame] | 113 | What: Unused EXPORT_SYMBOL/EXPORT_SYMBOL_GPL exports |
| 114 | (temporary transition config option provided until then) |
| 115 | The transition config option will also be removed at the same time. |
| 116 | When: before 2.6.19 |
| 117 | Why: Unused symbols are both increasing the size of the kernel binary |
| 118 | and are often a sign of "wrong API" |
| 119 | Who: Arjan van de Ven <arjan@linux.intel.com> |
| 120 | |
| 121 | --------------------------- |
| 122 | |
Greg Kroah-Hartman | b87ba0a | 2006-03-20 13:17:13 -0800 | [diff] [blame] | 123 | What: USB driver API moves to EXPORT_SYMBOL_GPL |
Matt LaPlante | a2ffd27 | 2006-10-03 22:49:15 +0200 | [diff] [blame] | 124 | When: February 2008 |
Greg Kroah-Hartman | b87ba0a | 2006-03-20 13:17:13 -0800 | [diff] [blame] | 125 | Files: include/linux/usb.h, drivers/usb/core/driver.c |
| 126 | Why: The USB subsystem has changed a lot over time, and it has been |
| 127 | possible to create userspace USB drivers using usbfs/libusb/gadgetfs |
| 128 | that operate as fast as the USB bus allows. Because of this, the USB |
| 129 | subsystem will not be allowing closed source kernel drivers to |
| 130 | register with it, after this grace period is over. If anyone needs |
| 131 | any help in converting their closed source drivers over to use the |
| 132 | userspace filesystems, please contact the |
| 133 | linux-usb-devel@lists.sourceforge.net mailing list, and the developers |
| 134 | there will be glad to help you out. |
| 135 | Who: Greg Kroah-Hartman <gregkh@suse.de> |
| 136 | |
| 137 | --------------------------- |
Nick Piggin | 93fac70 | 2006-03-31 02:29:56 -0800 | [diff] [blame] | 138 | |
Nick Piggin | 54cb882 | 2007-07-19 01:46:59 -0700 | [diff] [blame] | 139 | What: vm_ops.nopage |
Nick Piggin | d0217ac | 2007-07-19 01:47:03 -0700 | [diff] [blame] | 140 | When: Soon, provided in-kernel callers have been converted |
Nick Piggin | 54cb882 | 2007-07-19 01:46:59 -0700 | [diff] [blame] | 141 | Why: This interface is replaced by vm_ops.fault, but it has been around |
| 142 | forever, is used by a lot of drivers, and doesn't cost much to |
| 143 | maintain. |
| 144 | Who: Nick Piggin <npiggin@suse.de> |
| 145 | |
| 146 | --------------------------- |
| 147 | |
Thomas Gleixner | 6e21361 | 2006-07-01 19:29:03 -0700 | [diff] [blame] | 148 | What: Interrupt only SA_* flags |
Thomas Gleixner | 0e8638e | 2007-05-08 00:28:56 -0700 | [diff] [blame] | 149 | When: September 2007 |
Thomas Gleixner | 6e21361 | 2006-07-01 19:29:03 -0700 | [diff] [blame] | 150 | Why: The interrupt related SA_* flags are replaced by IRQF_* to move them |
| 151 | out of the signal namespace. |
| 152 | |
| 153 | Who: Thomas Gleixner <tglx@linutronix.de> |
| 154 | |
| 155 | --------------------------- |
Jean Delvare | 5a01748 | 2006-07-01 17:13:37 +0200 | [diff] [blame] | 156 | |
Kay Sievers | d81d9d6 | 2006-08-13 06:17:09 +0200 | [diff] [blame] | 157 | What: PHYSDEVPATH, PHYSDEVBUS, PHYSDEVDRIVER in the uevent environment |
Dominik Brodowski | acbd39f | 2006-09-30 22:41:43 -0400 | [diff] [blame] | 158 | When: October 2008 |
Kay Sievers | d81d9d6 | 2006-08-13 06:17:09 +0200 | [diff] [blame] | 159 | Why: The stacking of class devices makes these values misleading and |
| 160 | inconsistent. |
| 161 | Class devices should not carry any of these properties, and bus |
| 162 | devices have SUBSYTEM and DRIVER as a replacement. |
| 163 | Who: Kay Sievers <kay.sievers@suse.de> |
| 164 | |
| 165 | --------------------------- |
Jean Delvare | 6c805d2 | 2006-08-13 23:45:52 +0200 | [diff] [blame] | 166 | |
Jean Delvare | fccb56e | 2007-05-01 23:26:27 +0200 | [diff] [blame] | 167 | What: i2c_adapter.list |
David Brownell | b119dc3 | 2007-01-04 13:07:04 +0100 | [diff] [blame] | 168 | When: July 2007 |
Jean Delvare | fccb56e | 2007-05-01 23:26:27 +0200 | [diff] [blame] | 169 | Why: Superfluous, this list duplicates the one maintained by the driver |
| 170 | core. |
David Brownell | b119dc3 | 2007-01-04 13:07:04 +0100 | [diff] [blame] | 171 | Who: Jean Delvare <khali@linux-fr.org>, |
| 172 | David Brownell <dbrownell@users.sourceforge.net> |
| 173 | |
| 174 | --------------------------- |
| 175 | |
Adrian Bunk | 5aab0ad | 2007-02-10 01:45:50 -0800 | [diff] [blame] | 176 | What: drivers depending on OBSOLETE_OSS |
| 177 | When: options in 2.6.22, code in 2.6.24 |
| 178 | Why: OSS drivers with ALSA replacements |
| 179 | Who: Adrian Bunk <bunk@stusta.de> |
| 180 | |
| 181 | --------------------------- |
| 182 | |
Zhang Rui | b981c59 | 2007-01-29 11:02:30 +0800 | [diff] [blame] | 183 | What: ACPI procfs interface |
Zhang Rui | 8b8eb7d | 2007-07-18 17:23:24 +0800 | [diff] [blame] | 184 | When: July 2008 |
| 185 | Why: ACPI sysfs conversion should be finished by January 2008. |
| 186 | ACPI procfs interface will be removed in July 2008 so that |
| 187 | there is enough time for the user space to catch up. |
Zhang Rui | b981c59 | 2007-01-29 11:02:30 +0800 | [diff] [blame] | 188 | Who: Zhang Rui <rui.zhang@intel.com> |
| 189 | |
| 190 | --------------------------- |
| 191 | |
Len Brown | 1bb67c2 | 2007-01-11 01:49:44 -0500 | [diff] [blame] | 192 | What: /proc/acpi/button |
| 193 | When: August 2007 |
| 194 | Why: /proc/acpi/button has been replaced by events to the input layer |
| 195 | since 2.6.20. |
| 196 | Who: Len Brown <len.brown@intel.com> |
| 197 | |
| 198 | --------------------------- |
Jeff Garzik | 54b290a | 2007-01-23 00:29:01 -0500 | [diff] [blame] | 199 | |
Richard Purdie | ff141a0 | 2007-02-10 01:29:11 -0500 | [diff] [blame] | 200 | What: Compaq touchscreen device emulation |
| 201 | When: Oct 2007 |
| 202 | Files: drivers/input/tsdev.c |
| 203 | Why: The code says it was obsolete when it was written in 2001. |
| 204 | tslib is a userspace library which does anything tsdev can do and |
| 205 | much more besides in userspace where this code belongs. There is no |
| 206 | longer any need for tsdev and applications should have converted to |
| 207 | use tslib by now. |
| 208 | The name "tsdev" is also extremely confusing and lots of people have |
| 209 | it loaded when they don't need/use it. |
| 210 | Who: Richard Purdie <rpurdie@rpsys.net> |
| 211 | |
| 212 | --------------------------- |
Johannes Berg | cc2ccca | 2007-03-05 00:30:27 -0800 | [diff] [blame] | 213 | |
Cornelia Huck | 52706ec | 2007-05-04 18:47:50 +0200 | [diff] [blame] | 214 | What: read_dev_chars(), read_conf_data{,_lpm}() (s390 common I/O layer) |
| 215 | When: December 2007 |
| 216 | Why: These functions are a leftover from 2.4 times. They have several |
| 217 | problems: |
| 218 | - Duplication of checks that are done in the device driver's |
| 219 | interrupt handler |
| 220 | - common I/O layer can't do device specific error recovery |
| 221 | - device driver can't be notified for conditions happening during |
| 222 | execution of the function |
| 223 | Device drivers should issue the read device characteristics and read |
| 224 | configuration data ccws and do the appropriate error handling |
| 225 | themselves. |
| 226 | Who: Cornelia Huck <cornelia.huck@de.ibm.com> |
| 227 | |
| 228 | --------------------------- |
| 229 | |
Jean Delvare | 11de70b | 2007-05-01 23:26:34 +0200 | [diff] [blame] | 230 | What: i2c-ixp2000, i2c-ixp4xx and scx200_i2c drivers |
| 231 | When: September 2007 |
| 232 | Why: Obsolete. The new i2c-gpio driver replaces all hardware-specific |
| 233 | I2C-over-GPIO drivers. |
| 234 | Who: Jean Delvare <khali@linux-fr.org> |
| 235 | |
| 236 | --------------------------- |
Adrian Bunk | 274ee1cd | 2007-05-08 00:27:14 -0700 | [diff] [blame] | 237 | |
Randy Dunlap | e84845c | 2007-07-15 23:40:25 -0700 | [diff] [blame] | 238 | What: 'time' kernel boot parameter |
| 239 | When: January 2008 |
| 240 | Why: replaced by 'printk.time=<value>' so that printk timestamps can be |
| 241 | enabled or disabled as needed |
| 242 | Who: Randy Dunlap <randy.dunlap@oracle.com> |
| 243 | |
| 244 | --------------------------- |
| 245 | |
Adrian Bunk | 274ee1cd | 2007-05-08 00:27:14 -0700 | [diff] [blame] | 246 | What: drivers depending on OSS_OBSOLETE |
| 247 | When: options in 2.6.23, code in 2.6.25 |
| 248 | Why: obsolete OSS drivers |
| 249 | Who: Adrian Bunk <bunk@stusta.de> |
| 250 | |
| 251 | --------------------------- |
| 252 | |
Tejun Heo | d9aca22 | 2007-05-17 16:43:26 +0200 | [diff] [blame] | 253 | What: libata spindown skipping and warning |
Tejun Heo | 920a4b1 | 2007-05-04 21:28:48 +0200 | [diff] [blame] | 254 | When: Dec 2008 |
Tejun Heo | d9aca22 | 2007-05-17 16:43:26 +0200 | [diff] [blame] | 255 | Why: Some halt(8) implementations synchronize caches for and spin |
| 256 | down libata disks because libata didn't use to spin down disk on |
| 257 | system halt (only synchronized caches). |
| 258 | Spin down on system halt is now implemented. sysfs node |
| 259 | /sys/class/scsi_disk/h:c:i:l/manage_start_stop is present if |
| 260 | spin down support is available. |
Tejun Heo | 920a4b1 | 2007-05-04 21:28:48 +0200 | [diff] [blame] | 261 | Because issuing spin down command to an already spun down disk |
Tejun Heo | d9aca22 | 2007-05-17 16:43:26 +0200 | [diff] [blame] | 262 | makes some disks spin up just to spin down again, libata tracks |
| 263 | device spindown status to skip the extra spindown command and |
| 264 | warn about it. |
| 265 | This is to give userspace tools the time to get updated and will |
| 266 | be removed after userspace is reasonably updated. |
Tejun Heo | 920a4b1 | 2007-05-04 21:28:48 +0200 | [diff] [blame] | 267 | Who: Tejun Heo <htejun@gmail.com> |
| 268 | |
| 269 | --------------------------- |
| 270 | |
Jean Delvare | ba7fbb7 | 2007-07-12 14:12:29 +0200 | [diff] [blame] | 271 | What: Legacy RTC drivers (under drivers/i2c/chips) |
| 272 | When: November 2007 |
| 273 | Why: Obsolete. We have a RTC subsystem with better drivers. |
| 274 | Who: Jean Delvare <khali@linux-fr.org> |
| 275 | |
| 276 | --------------------------- |
| 277 | |
Patrick McHardy | 3569b62 | 2007-07-07 22:38:07 -0700 | [diff] [blame] | 278 | What: iptables SAME target |
| 279 | When: 1.1. 2008 |
| 280 | Files: net/ipv4/netfilter/ipt_SAME.c, include/linux/netfilter_ipv4/ipt_SAME.h |
| 281 | Why: Obsolete for multiple years now, NAT core provides the same behaviour. |
| 282 | Unfixable broken wrt. 32/64 bit cleanness. |
| 283 | Who: Patrick McHardy <kaber@trash.net> |
| 284 | |
| 285 | --------------------------- |
Linus Torvalds | 489de30 | 2007-07-16 17:58:08 -0700 | [diff] [blame] | 286 | |
Josh Boyer | 0b7dbfb | 2007-07-03 23:25:46 +1000 | [diff] [blame] | 287 | What: The arch/ppc and include/asm-ppc directories |
| 288 | When: Jun 2008 |
| 289 | Why: The arch/powerpc tree is the merged architecture for ppc32 and ppc64 |
| 290 | platforms. Currently there are efforts underway to port the remaining |
| 291 | arch/ppc platforms to the merged tree. New submissions to the arch/ppc |
| 292 | tree have been frozen with the 2.6.22 kernel release and that tree will |
| 293 | remain in bug-fix only mode until its scheduled removal. Platforms |
| 294 | that are not ported by June 2008 will be removed due to the lack of an |
| 295 | interested maintainer. |
| 296 | Who: linuxppc-dev@ozlabs.org |
| 297 | |
| 298 | --------------------------- |
Roland Dreier | f6be6fb | 2007-07-17 18:37:41 -0700 | [diff] [blame] | 299 | |
| 300 | What: mthca driver's MSI support |
| 301 | When: January 2008 |
| 302 | Files: drivers/infiniband/hw/mthca/*.[ch] |
| 303 | Why: All mthca hardware also supports MSI-X, which provides |
| 304 | strictly more functionality than MSI. So there is no point in |
| 305 | having both MSI-X and MSI support in the driver. |
| 306 | Who: Roland Dreier <rolandd@cisco.com> |
| 307 | |
| 308 | --------------------------- |