blob: 181bff00516784e3b4bc0c8a7f2b94ed47b76e70 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001The following is a list of files and features that are going to be
2removed in the kernel source tree. Every entry should contain what
3exactly is going away, why it is happening, and who is going to be doing
4the work. When the feature is removed from the kernel, it should also
5be removed from this file.
6
7---------------------------
8
Jiri Slaby9e402102007-05-08 00:36:28 -07009What: MXSER
10When: December 2007
11Why: Old mxser driver is obsoleted by the mxser_new. Give it some time yet
12 and remove it.
13Who: Jiri Slaby <jirislaby@gmail.com>
14
15---------------------------
16
Alan Stern471d0552007-07-12 16:55:07 -040017What: dev->power.power_state
Pavel Machek1ebfd792006-08-30 13:50:27 -070018When: July 2007
19Why: Broken design for runtime control over driver power states, confusing
20 driver-internal runtime power management with: mechanisms to support
21 system-wide sleep state transitions; event codes that distinguish
22 different phases of swsusp "sleep" transitions; and userspace policy
23 inputs. This framework was never widely used, and most attempts to
24 use it were broken. Drivers should instead be exposing domain-specific
25 interfaces either to kernel or to userspace.
26Who: Pavel Machek <pavel@suse.cz>
27
28---------------------------
29
Christoph Hellwiga6bcbc22007-04-30 00:05:48 +020030What: old NCR53C9x driver
31When: October 2007
32Why: Replaced by the much better esp_scsi driver. Actual low-level
Christoph Hellwiged560472007-05-13 22:48:31 +020033 driver can be ported over almost trivially.
Christoph Hellwiga6bcbc22007-04-30 00:05:48 +020034Who: David Miller <davem@davemloft.net>
35 Christoph Hellwig <hch@lst.de>
36
37---------------------------
38
Mauro Carvalho Chehab875c2962005-11-08 21:38:53 -080039What: Video4Linux API 1 ioctls and video_decoder.h from Video devices.
Mauro Carvalho Chehab11a5a102007-10-17 15:32:36 -020040When: December 2008
41Files: include/linux/video_decoder.h include/linux/videodev.h
42Check: include/linux/video_decoder.h include/linux/videodev.h
43Why: V4L1 AP1 was replaced by V4L2 API during migration from 2.4 to 2.6
Mauro Carvalho Chehab875c2962005-11-08 21:38:53 -080044 series. The old API have lots of drawbacks and don't provide enough
45 means to work with all video and audio standards. The newer API is
46 already available on the main drivers and should be used instead.
47 Newer drivers should use v4l_compat_translate_ioctl function to handle
48 old calls, replacing to newer ones.
49 Decoder iocts are using internally to allow video drivers to
50 communicate with video decoders. This should also be improved to allow
51 V4L2 calls being translated into compatible internal ioctls.
Mauro Carvalho Chehab11a5a102007-10-17 15:32:36 -020052 Compatibility ioctls will be provided, for a while, via
53 v4l1-compat module.
54Who: Mauro Carvalho Chehab <mchehab@infradead.org>
Mauro Carvalho Chehab875c2962005-11-08 21:38:53 -080055
56---------------------------
57
Dominik Brodowskibf45d9b02005-07-07 17:58:58 -070058What: PCMCIA control ioctl (needed for pcmcia-cs [cardmgr, cardctl])
59When: November 2005
60Files: drivers/pcmcia/: pcmcia_ioctl.c
61Why: With the 16-bit PCMCIA subsystem now behaving (almost) like a
62 normal hotpluggable bus, and with it using the default kernel
63 infrastructure (hotplug, driver core, sysfs) keeping the PCMCIA
64 control ioctl needed by cardmgr and cardctl from pcmcia-cs is
65 unnecessary, and makes further cleanups and integration of the
66 PCMCIA subsystem into the Linux kernel device driver model more
67 difficult. The features provided by cardmgr and cardctl are either
68 handled by the kernel itself now or are available in the new
69 pcmciautils package available at
70 http://kernel.org/pub/linux/utils/kernel/pcmcia/
71Who: Dominik Brodowski <linux@brodo.de>
Harald Welte7af4cc32005-08-09 19:44:15 -070072
73---------------------------
74
Eric W. Biederman7058cb02007-10-18 03:05:58 -070075What: sys_sysctl
76When: September 2010
77Option: CONFIG_SYSCTL_SYSCALL
78Why: The same information is available in a more convenient from
79 /proc/sys, and none of the sysctl variables appear to be
80 important performance wise.
81
82 Binary sysctls are a long standing source of subtle kernel
83 bugs and security issues.
84
85 When I looked several months ago all I could find after
86 searching several distributions were 5 user space programs and
87 glibc (which falls back to /proc/sys) using this syscall.
88
89 The man page for sysctl(2) documents it as unusable for user
90 space programs.
91
92 sysctl(2) is not generally ABI compatible to a 32bit user
93 space application on a 64bit and a 32bit kernel.
94
95 For the last several months the policy has been no new binary
96 sysctls and no one has put forward an argument to use them.
97
98 Binary sysctls issues seem to keep happening appearing so
99 properly deprecating them (with a warning to user space) and a
100 2 year grace warning period will mean eventually we can kill
101 them and end the pain.
102
103 In the mean time individual binary sysctls can be dealt with
104 in a piecewise fashion.
105
106Who: Eric Biederman <ebiederm@xmission.com>
107
108---------------------------
109
Andi Kleen8e9073e2007-10-16 23:26:48 -0700110What: a.out interpreter support for ELF executables
111When: 2.6.25
112Files: fs/binfmt_elf.c
113Why: Using a.out interpreters for ELF executables was a feature for
114 transition from a.out to ELF. But now it is unlikely to be still
115 needed anymore and removing it would simplify the hairy ELF
116 loader code.
117Who: Andi Kleen <ak@suse.de>
118
119---------------------------
120
Christoph Hellwigac515892006-03-24 03:18:22 -0800121What: remove EXPORT_SYMBOL(kernel_thread)
122When: August 2006
123Files: arch/*/kernel/*_ksyms.c
Andy Whitcroftf0a594c2007-07-19 01:48:34 -0700124Check: kernel_thread
Christoph Hellwigac515892006-03-24 03:18:22 -0800125Why: kernel_thread is a low-level implementation detail. Drivers should
126 use the <linux/kthread.h> API instead which shields them from
127 implementation details and provides a higherlevel interface that
128 prevents bugs and code duplication
129Who: Christoph Hellwig <hch@lst.de>
130
131---------------------------
132
Ingo Molnara9df3d02006-01-14 13:21:33 -0800133What: CONFIG_FORCED_INLINING
134When: June 2006
135Why: Config option is there to see if gcc is good enough. (in january
136 2006). If it is, the behavior should just be the default. If it's not,
137 the option should just go away entirely.
138Who: Arjan van de Ven
139
140---------------------------
141
Bunkc0d3c0c2006-02-07 01:43:31 -0500142What: eepro100 network driver
143When: January 2007
144Why: replaced by the e100 driver
145Who: Adrian Bunk <bunk@stusta.de>
Jeff Garzik3c9b3a82006-02-07 01:47:12 -0500146
147---------------------------
148
Arjan van de Venf71d20e2006-06-28 04:26:45 -0700149What: Unused EXPORT_SYMBOL/EXPORT_SYMBOL_GPL exports
150 (temporary transition config option provided until then)
151 The transition config option will also be removed at the same time.
152When: before 2.6.19
153Why: Unused symbols are both increasing the size of the kernel binary
154 and are often a sign of "wrong API"
155Who: Arjan van de Ven <arjan@linux.intel.com>
156
157---------------------------
158
Greg Kroah-Hartmanb87ba0a2006-03-20 13:17:13 -0800159What: USB driver API moves to EXPORT_SYMBOL_GPL
Matt LaPlantea2ffd272006-10-03 22:49:15 +0200160When: February 2008
Greg Kroah-Hartmanb87ba0a2006-03-20 13:17:13 -0800161Files: include/linux/usb.h, drivers/usb/core/driver.c
162Why: The USB subsystem has changed a lot over time, and it has been
163 possible to create userspace USB drivers using usbfs/libusb/gadgetfs
164 that operate as fast as the USB bus allows. Because of this, the USB
165 subsystem will not be allowing closed source kernel drivers to
166 register with it, after this grace period is over. If anyone needs
167 any help in converting their closed source drivers over to use the
168 userspace filesystems, please contact the
169 linux-usb-devel@lists.sourceforge.net mailing list, and the developers
170 there will be glad to help you out.
171Who: Greg Kroah-Hartman <gregkh@suse.de>
172
173---------------------------
Nick Piggin93fac702006-03-31 02:29:56 -0800174
Nick Piggin54cb8822007-07-19 01:46:59 -0700175What: vm_ops.nopage
Nick Piggind0217ac2007-07-19 01:47:03 -0700176When: Soon, provided in-kernel callers have been converted
Nick Piggin54cb8822007-07-19 01:46:59 -0700177Why: This interface is replaced by vm_ops.fault, but it has been around
178 forever, is used by a lot of drivers, and doesn't cost much to
179 maintain.
180Who: Nick Piggin <npiggin@suse.de>
181
182---------------------------
183
Kay Sieversd81d9d62006-08-13 06:17:09 +0200184What: PHYSDEVPATH, PHYSDEVBUS, PHYSDEVDRIVER in the uevent environment
Dominik Brodowskiacbd39f2006-09-30 22:41:43 -0400185When: October 2008
Kay Sieversd81d9d62006-08-13 06:17:09 +0200186Why: The stacking of class devices makes these values misleading and
187 inconsistent.
188 Class devices should not carry any of these properties, and bus
189 devices have SUBSYTEM and DRIVER as a replacement.
190Who: Kay Sievers <kay.sievers@suse.de>
191
192---------------------------
Jean Delvare6c805d22006-08-13 23:45:52 +0200193
Zhang Ruib981c592007-01-29 11:02:30 +0800194What: ACPI procfs interface
Zhang Rui8b8eb7d2007-07-18 17:23:24 +0800195When: July 2008
196Why: ACPI sysfs conversion should be finished by January 2008.
197 ACPI procfs interface will be removed in July 2008 so that
198 there is enough time for the user space to catch up.
Zhang Ruib981c592007-01-29 11:02:30 +0800199Who: Zhang Rui <rui.zhang@intel.com>
200
201---------------------------
202
Len Brown1bb67c22007-01-11 01:49:44 -0500203What: /proc/acpi/button
204When: August 2007
205Why: /proc/acpi/button has been replaced by events to the input layer
206 since 2.6.20.
207Who: Len Brown <len.brown@intel.com>
208
209---------------------------
Jeff Garzik54b290a2007-01-23 00:29:01 -0500210
Len Brown14e04fb2007-08-23 15:20:26 -0400211What: /proc/acpi/event
212When: February 2008
213Why: /proc/acpi/event has been replaced by events via the input layer
214 and netlink since 2.6.23.
215Who: Len Brown <len.brown@intel.com>
216
217---------------------------
218
Randy Dunlape84845c2007-07-15 23:40:25 -0700219What: 'time' kernel boot parameter
220When: January 2008
221Why: replaced by 'printk.time=<value>' so that printk timestamps can be
222 enabled or disabled as needed
223Who: Randy Dunlap <randy.dunlap@oracle.com>
224
225---------------------------
226
Adrian Bunk274ee1c2007-05-08 00:27:14 -0700227What: drivers depending on OSS_OBSOLETE
228When: options in 2.6.23, code in 2.6.25
229Why: obsolete OSS drivers
230Who: Adrian Bunk <bunk@stusta.de>
231
232---------------------------
233
Tejun Heod9aca222007-05-17 16:43:26 +0200234What: libata spindown skipping and warning
Tejun Heo920a4b12007-05-04 21:28:48 +0200235When: Dec 2008
Tejun Heod9aca222007-05-17 16:43:26 +0200236Why: Some halt(8) implementations synchronize caches for and spin
237 down libata disks because libata didn't use to spin down disk on
238 system halt (only synchronized caches).
239 Spin down on system halt is now implemented. sysfs node
240 /sys/class/scsi_disk/h:c:i:l/manage_start_stop is present if
241 spin down support is available.
Tejun Heo920a4b12007-05-04 21:28:48 +0200242 Because issuing spin down command to an already spun down disk
Tejun Heod9aca222007-05-17 16:43:26 +0200243 makes some disks spin up just to spin down again, libata tracks
244 device spindown status to skip the extra spindown command and
245 warn about it.
246 This is to give userspace tools the time to get updated and will
247 be removed after userspace is reasonably updated.
Tejun Heo920a4b12007-05-04 21:28:48 +0200248Who: Tejun Heo <htejun@gmail.com>
249
250---------------------------
251
Josh Boyer0b7dbfb2007-07-03 23:25:46 +1000252What: The arch/ppc and include/asm-ppc directories
253When: Jun 2008
254Why: The arch/powerpc tree is the merged architecture for ppc32 and ppc64
255 platforms. Currently there are efforts underway to port the remaining
256 arch/ppc platforms to the merged tree. New submissions to the arch/ppc
257 tree have been frozen with the 2.6.22 kernel release and that tree will
258 remain in bug-fix only mode until its scheduled removal. Platforms
259 that are not ported by June 2008 will be removed due to the lack of an
260 interested maintainer.
261Who: linuxppc-dev@ozlabs.org
262
263---------------------------
Roland Dreierf6be6fb2007-07-17 18:37:41 -0700264
Stephen Hemminger5ad887f2007-09-15 19:35:14 -0400265What: sk98lin network driver
266When: Feburary 2008
267Why: In kernel tree version of driver is unmaintained. Sk98lin driver
268 replaced by the skge driver.
269Who: Stephen Hemminger <shemminger@linux-foundation.org>
270
271---------------------------
Thomas Gleixner914d97f2007-10-11 11:20:05 +0200272
273What: i386/x86_64 bzImage symlinks
274When: April 2008
275
276Why: The i386/x86_64 merge provides a symlink to the old bzImage
277 location so not yet updated user space tools, e.g. package
278 scripts, do not break.
279Who: Thomas Gleixner <tglx@linutronix.de>
Linus Torvalds038a5002007-10-11 19:40:14 -0700280
281---------------------------
282
Linus Torvalds038a5002007-10-11 19:40:14 -0700283---------------------------
Jean Delvare0f79b722008-01-27 18:14:47 +0100284
285What: i2c-i810, i2c-prosavage and i2c-savage4
286When: May 2008
287Why: These drivers are superseded by i810fb, intelfb and savagefb.
288Who: Jean Delvare <khali@linux-fr.org>
289
290---------------------------
John W. Linville003faaa2008-01-27 22:48:37 -0800291
292What: bcm43xx wireless network driver
293When: 2.6.26
294Files: drivers/net/wireless/bcm43xx
295Why: This driver's functionality has been replaced by the
296 mac80211-based b43 and b43legacy drivers.
297Who: John W. Linville <linville@tuxdriver.com>
298
299---------------------------
John W. Linvilleedae58e2007-11-21 15:24:35 -0500300
Stefano Brivioa1464ab2007-12-19 01:46:53 +0100301What: ieee80211 softmac wireless networking component
John W. Linvilleedae58e2007-11-21 15:24:35 -0500302When: 2.6.26 (or after removal of bcm43xx and port of zd1211rw to mac80211)
303Files: net/ieee80211/softmac
304Why: No in-kernel drivers will depend on it any longer.
305Who: John W. Linville <linville@tuxdriver.com>
306
307---------------------------
Stefano Brivioc21b39a2007-12-19 01:26:16 +0100308
309What: rc80211-simple rate control algorithm for mac80211
310When: 2.6.26
311Files: net/mac80211/rc80211-simple.c
312Why: This algorithm was provided for reference but always exhibited bad
313 responsiveness and performance and has some serious flaws. It has been
314 replaced by rc80211-pid.
315Who: Stefano Brivio <stefano.brivio@polimi.it>
Jan Engelhardtf9ef8a22008-01-14 23:43:34 -0800316
317---------------------------
318
319What (Why):
320 - include/linux/netfilter_ipv4/ipt_TOS.h ipt_tos.h header files
321 (superseded by xt_TOS/xt_tos target & match)
322
323 - "forwarding" header files like ipt_mac.h in
324 include/linux/netfilter_ipv4/ and include/linux/netfilter_ipv6/
325
326 - xt_CONNMARK match revision 0
327 (superseded by xt_CONNMARK match revision 1)
328
329 - xt_MARK target revisions 0 and 1
330 (superseded by xt_MARK match revision 2)
331
332 - xt_connmark match revision 0
333 (superseded by xt_connmark match revision 1)
334
335 - xt_conntrack match revision 0
336 (superseded by xt_conntrack match revision 1)
337
338 - xt_iprange match revision 0,
339 include/linux/netfilter_ipv4/ipt_iprange.h
340 (superseded by xt_iprange match revision 1)
341
342 - xt_mark match revision 0
343 (superseded by xt_mark match revision 1)
344
345When: January 2009 or Linux 2.7.0, whichever comes first
346Why: Superseded by newer revisions or modules
347Who: Jan Engelhardt <jengelh@computergmbh.de>
Michael Buescheb189d82008-01-28 14:47:41 -0800348
349---------------------------
350
351What: b43 support for firmware revision < 410
352When: July 2008
353Why: The support code for the old firmware hurts code readability/maintainability
354 and slightly hurts runtime performance. Bugfixes for the old firmware
355 are not provided by Broadcom anymore.
356Who: Michael Buesch <mb@bu3sch.de>