Commit | Line | Data |
---|---|---|
1da177e4 LT |
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 | ||
9e402102 JS |
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 | ||
3f3f6a59 HV |
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 | ||
1ebfd79e PM |
29 | What: /sys/devices/.../power/state |
30 | dev->power.power_state | |
31 | dpm_runtime_{suspend,resume)() | |
32 | When: July 2007 | |
33 | Why: Broken design for runtime control over driver power states, confusing | |
34 | driver-internal runtime power management with: mechanisms to support | |
35 | system-wide sleep state transitions; event codes that distinguish | |
36 | different phases of swsusp "sleep" transitions; and userspace policy | |
37 | inputs. This framework was never widely used, and most attempts to | |
38 | use it were broken. Drivers should instead be exposing domain-specific | |
39 | interfaces either to kernel or to userspace. | |
40 | Who: Pavel Machek <pavel@suse.cz> | |
41 | ||
42 | --------------------------- | |
43 | ||
98e7f294 AB |
44 | What: RAW driver (CONFIG_RAW_DRIVER) |
45 | When: December 2005 | |
46 | Why: declared obsolete since kernel 2.6.3 | |
47 | O_DIRECT can be used instead | |
48 | Who: Adrian Bunk <bunk@stusta.de> | |
49 | ||
50 | --------------------------- | |
51 | ||
a1446c7f | 52 | What: raw1394: requests of type RAW1394_REQ_ISO_SEND, RAW1394_REQ_ISO_LISTEN |
9868e0ec SR |
53 | When: June 2007 |
54 | Why: Deprecated in favour of the more efficient and robust rawiso interface. | |
55 | Affected are applications which use the deprecated part of libraw1394 | |
56 | (raw1394_iso_write, raw1394_start_iso_write, raw1394_start_iso_rcv, | |
57 | raw1394_stop_iso_rcv) or bypass libraw1394. | |
58 | Who: Dan Dennedy <dan@dennedy.org>, Stefan Richter <stefanr@s5r6.in-berlin.de> | |
937df8df GC |
59 | |
60 | --------------------------- | |
61 | ||
a6bcbc2f CH |
62 | What: old NCR53C9x driver |
63 | When: October 2007 | |
64 | Why: Replaced by the much better esp_scsi driver. Actual low-level | |
65 | driver can ported over almost trivially. | |
66 | Who: David Miller <davem@davemloft.net> | |
67 | Christoph Hellwig <hch@lst.de> | |
68 | ||
69 | --------------------------- | |
70 | ||
875c296b | 71 | What: Video4Linux API 1 ioctls and video_decoder.h from Video devices. |
48c06d5e | 72 | When: December 2006 |
875c296b MCC |
73 | Why: V4L1 AP1 was replaced by V4L2 API. during migration from 2.4 to 2.6 |
74 | series. The old API have lots of drawbacks and don't provide enough | |
75 | means to work with all video and audio standards. The newer API is | |
76 | already available on the main drivers and should be used instead. | |
77 | Newer drivers should use v4l_compat_translate_ioctl function to handle | |
78 | old calls, replacing to newer ones. | |
79 | Decoder iocts are using internally to allow video drivers to | |
80 | communicate with video decoders. This should also be improved to allow | |
81 | V4L2 calls being translated into compatible internal ioctls. | |
82 | Who: Mauro Carvalho Chehab <mchehab@brturbo.com.br> | |
83 | ||
84 | --------------------------- | |
85 | ||
bf45d9b0 DB |
86 | What: PCMCIA control ioctl (needed for pcmcia-cs [cardmgr, cardctl]) |
87 | When: November 2005 | |
88 | Files: drivers/pcmcia/: pcmcia_ioctl.c | |
89 | Why: With the 16-bit PCMCIA subsystem now behaving (almost) like a | |
90 | normal hotpluggable bus, and with it using the default kernel | |
91 | infrastructure (hotplug, driver core, sysfs) keeping the PCMCIA | |
92 | control ioctl needed by cardmgr and cardctl from pcmcia-cs is | |
93 | unnecessary, and makes further cleanups and integration of the | |
94 | PCMCIA subsystem into the Linux kernel device driver model more | |
95 | difficult. The features provided by cardmgr and cardctl are either | |
96 | handled by the kernel itself now or are available in the new | |
97 | pcmciautils package available at | |
98 | http://kernel.org/pub/linux/utils/kernel/pcmcia/ | |
99 | Who: Dominik Brodowski <linux@brodo.de> | |
7af4cc3f HW |
100 | |
101 | --------------------------- | |
102 | ||
ac515898 CH |
103 | What: remove EXPORT_SYMBOL(kernel_thread) |
104 | When: August 2006 | |
105 | Files: arch/*/kernel/*_ksyms.c | |
106 | Why: kernel_thread is a low-level implementation detail. Drivers should | |
107 | use the <linux/kthread.h> API instead which shields them from | |
108 | implementation details and provides a higherlevel interface that | |
109 | prevents bugs and code duplication | |
110 | Who: Christoph Hellwig <hch@lst.de> | |
111 | ||
112 | --------------------------- | |
113 | ||
a9df3d0f IM |
114 | What: CONFIG_FORCED_INLINING |
115 | When: June 2006 | |
116 | Why: Config option is there to see if gcc is good enough. (in january | |
117 | 2006). If it is, the behavior should just be the default. If it's not, | |
118 | the option should just go away entirely. | |
119 | Who: Arjan van de Ven | |
120 | ||
121 | --------------------------- | |
122 | ||
c0d3c0c0 B |
123 | What: eepro100 network driver |
124 | When: January 2007 | |
125 | Why: replaced by the e100 driver | |
126 | Who: Adrian Bunk <bunk@stusta.de> | |
3c9b3a85 JG |
127 | |
128 | --------------------------- | |
129 | ||
1e5f5e5c AB |
130 | What: drivers depending on OSS_OBSOLETE_DRIVER |
131 | When: options in 2.6.20, code in 2.6.22 | |
132 | Why: OSS drivers with ALSA replacements | |
133 | Who: Adrian Bunk <bunk@stusta.de> | |
134 | ||
135 | --------------------------- | |
136 | ||
f71d20e9 AV |
137 | What: Unused EXPORT_SYMBOL/EXPORT_SYMBOL_GPL exports |
138 | (temporary transition config option provided until then) | |
139 | The transition config option will also be removed at the same time. | |
140 | When: before 2.6.19 | |
141 | Why: Unused symbols are both increasing the size of the kernel binary | |
142 | and are often a sign of "wrong API" | |
143 | Who: Arjan van de Ven <arjan@linux.intel.com> | |
144 | ||
145 | --------------------------- | |
146 | ||
b87ba0a3 | 147 | What: USB driver API moves to EXPORT_SYMBOL_GPL |
a2ffd275 | 148 | When: February 2008 |
b87ba0a3 GKH |
149 | Files: include/linux/usb.h, drivers/usb/core/driver.c |
150 | Why: The USB subsystem has changed a lot over time, and it has been | |
151 | possible to create userspace USB drivers using usbfs/libusb/gadgetfs | |
152 | that operate as fast as the USB bus allows. Because of this, the USB | |
153 | subsystem will not be allowing closed source kernel drivers to | |
154 | register with it, after this grace period is over. If anyone needs | |
155 | any help in converting their closed source drivers over to use the | |
156 | userspace filesystems, please contact the | |
157 | linux-usb-devel@lists.sourceforge.net mailing list, and the developers | |
158 | there will be glad to help you out. | |
159 | Who: Greg Kroah-Hartman <gregkh@suse.de> | |
93fac704 NP |
160 | |
161 | --------------------------- | |
127fe6af | 162 | |
6e213616 | 163 | What: Interrupt only SA_* flags |
0e8638e2 | 164 | When: September 2007 |
6e213616 TG |
165 | Why: The interrupt related SA_* flags are replaced by IRQF_* to move them |
166 | out of the signal namespace. | |
167 | ||
168 | Who: Thomas Gleixner <tglx@linutronix.de> | |
169 | ||
170 | --------------------------- | |
5a017483 | 171 | |
d81d9d6b | 172 | What: PHYSDEVPATH, PHYSDEVBUS, PHYSDEVDRIVER in the uevent environment |
acbd39fb | 173 | When: October 2008 |
d81d9d6b KS |
174 | Why: The stacking of class devices makes these values misleading and |
175 | inconsistent. | |
176 | Class devices should not carry any of these properties, and bus | |
177 | devices have SUBSYTEM and DRIVER as a replacement. | |
178 | Who: Kay Sievers <kay.sievers@suse.de> | |
179 | ||
180 | --------------------------- | |
6c805d2c JD |
181 | |
182 | What: i2c-isa | |
183 | When: December 2006 | |
184 | Why: i2c-isa is a non-sense and doesn't fit in the device driver | |
185 | model. Drivers relying on it are better implemented as platform | |
186 | drivers. | |
187 | Who: Jean Delvare <khali@linux-fr.org> | |
188 | ||
189 | --------------------------- | |
31e7e1a8 | 190 | |
fccb56e4 | 191 | What: i2c_adapter.list |
b119dc3f | 192 | When: July 2007 |
fccb56e4 JD |
193 | Why: Superfluous, this list duplicates the one maintained by the driver |
194 | core. | |
b119dc3f DB |
195 | Who: Jean Delvare <khali@linux-fr.org>, |
196 | David Brownell <dbrownell@users.sourceforge.net> | |
197 | ||
198 | --------------------------- | |
199 | ||
5aab0ad5 AB |
200 | What: drivers depending on OBSOLETE_OSS |
201 | When: options in 2.6.22, code in 2.6.24 | |
202 | Why: OSS drivers with ALSA replacements | |
203 | Who: Adrian Bunk <bunk@stusta.de> | |
204 | ||
205 | --------------------------- | |
206 | ||
83d0515b VP |
207 | What: ACPI hooks (X86_SPEEDSTEP_CENTRINO_ACPI) in speedstep-centrino driver |
208 | When: December 2006 | |
209 | Why: Speedstep-centrino driver with ACPI hooks and acpi-cpufreq driver are | |
210 | functionally very much similar. They talk to ACPI in same way. Only | |
211 | difference between them is the way they do frequency transitions. | |
212 | One uses MSRs and the other one uses IO ports. Functionaliy of | |
213 | speedstep_centrino with ACPI hooks is now merged into acpi-cpufreq. | |
214 | That means one common driver will support all Intel Enhanced Speedstep | |
215 | capable CPUs. That means less confusion over name of | |
216 | speedstep-centrino driver (with that driver supposed to be used on | |
217 | non-centrino platforms). That means less duplication of code and | |
218 | less maintenance effort and no possibility of these two drivers | |
219 | going out of sync. | |
220 | Current users of speedstep_centrino with ACPI hooks are requested to | |
221 | switch over to acpi-cpufreq driver. speedstep-centrino will continue | |
222 | to work using older non-ACPI static table based scheme even after this | |
223 | date. | |
224 | ||
225 | Who: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com> | |
226 | ||
227 | --------------------------- | |
1bb67c25 | 228 | |
1bb67c25 LB |
229 | What: /sys/firmware/acpi/namespace |
230 | When: 2.6.21 | |
231 | Why: The ACPI namespace is effectively the symbol list for | |
232 | the BIOS. The device names are completely arbitrary | |
233 | and have no place being exposed to user-space. | |
234 | ||
235 | For those interested in the BIOS ACPI namespace, | |
236 | the BIOS can be extracted and disassembled with acpidump | |
237 | and iasl as documented in the pmtools package here: | |
238 | http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils | |
1bb67c25 LB |
239 | Who: Len Brown <len.brown@intel.com> |
240 | ||
241 | --------------------------- | |
242 | ||
b981c591 ZR |
243 | What: ACPI procfs interface |
244 | When: July 2007 | |
245 | Why: After ACPI sysfs conversion, ACPI attributes will be duplicated | |
246 | in sysfs and the ACPI procfs interface should be removed. | |
247 | Who: Zhang Rui <rui.zhang@intel.com> | |
248 | ||
249 | --------------------------- | |
250 | ||
1bb67c25 LB |
251 | What: /proc/acpi/button |
252 | When: August 2007 | |
253 | Why: /proc/acpi/button has been replaced by events to the input layer | |
254 | since 2.6.20. | |
255 | Who: Len Brown <len.brown@intel.com> | |
256 | ||
257 | --------------------------- | |
54b290a2 | 258 | |
ac38dfc3 SH |
259 | What: sk98lin network driver |
260 | When: July 2007 | |
261 | Why: In kernel tree version of driver is unmaintained. Sk98lin driver | |
262 | replaced by the skge driver. | |
263 | Who: Stephen Hemminger <shemminger@osdl.org> | |
264 | ||
ff141a03 RP |
265 | --------------------------- |
266 | ||
267 | What: Compaq touchscreen device emulation | |
268 | When: Oct 2007 | |
269 | Files: drivers/input/tsdev.c | |
270 | Why: The code says it was obsolete when it was written in 2001. | |
271 | tslib is a userspace library which does anything tsdev can do and | |
272 | much more besides in userspace where this code belongs. There is no | |
273 | longer any need for tsdev and applications should have converted to | |
274 | use tslib by now. | |
275 | The name "tsdev" is also extremely confusing and lots of people have | |
276 | it loaded when they don't need/use it. | |
277 | Who: Richard Purdie <rpurdie@rpsys.net> | |
278 | ||
279 | --------------------------- | |
cc2cccae | 280 | |
49e9f70f DM |
281 | What: Multipath cached routing support in ipv4 |
282 | When: in 2.6.23 | |
283 | Why: Code was merged, then submitter immediately disappeared leaving | |
284 | us with no maintainer and lots of bugs. The code should not have | |
285 | been merged in the first place, and many aspects of it's | |
286 | implementation are blocking more critical core networking | |
287 | development. It's marked EXPERIMENTAL and no distribution | |
288 | enables it because it cause obscure crashes due to unfixable bugs | |
289 | (interfaces don't return errors so memory allocation can't be | |
290 | handled, calling contexts of these interfaces make handling | |
291 | errors impossible too because they get called after we've | |
292 | totally commited to creating a route object, for example). | |
293 | This problem has existed for years and no forward progress | |
294 | has ever been made, and nobody steps up to try and salvage | |
295 | this code, so we're going to finally just get rid of it. | |
296 | Who: David S. Miller <davem@davemloft.net> | |
297 | ||
298 | --------------------------- | |
52706ec9 CH |
299 | |
300 | What: read_dev_chars(), read_conf_data{,_lpm}() (s390 common I/O layer) | |
301 | When: December 2007 | |
302 | Why: These functions are a leftover from 2.4 times. They have several | |
303 | problems: | |
304 | - Duplication of checks that are done in the device driver's | |
305 | interrupt handler | |
306 | - common I/O layer can't do device specific error recovery | |
307 | - device driver can't be notified for conditions happening during | |
308 | execution of the function | |
309 | Device drivers should issue the read device characteristics and read | |
310 | configuration data ccws and do the appropriate error handling | |
311 | themselves. | |
312 | Who: Cornelia Huck <cornelia.huck@de.ibm.com> | |
313 | ||
314 | --------------------------- | |
315 | ||
11de70bd JD |
316 | What: i2c-ixp2000, i2c-ixp4xx and scx200_i2c drivers |
317 | When: September 2007 | |
318 | Why: Obsolete. The new i2c-gpio driver replaces all hardware-specific | |
319 | I2C-over-GPIO drivers. | |
320 | Who: Jean Delvare <khali@linux-fr.org> | |
321 | ||
322 | --------------------------- | |
274ee1cd AB |
323 | |
324 | What: drivers depending on OSS_OBSOLETE | |
325 | When: options in 2.6.23, code in 2.6.25 | |
326 | Why: obsolete OSS drivers | |
327 | Who: Adrian Bunk <bunk@stusta.de> | |
328 | ||
329 | --------------------------- | |
330 | ||
d9aca22c | 331 | What: libata spindown skipping and warning |
920a4b10 | 332 | When: Dec 2008 |
d9aca22c TH |
333 | Why: Some halt(8) implementations synchronize caches for and spin |
334 | down libata disks because libata didn't use to spin down disk on | |
335 | system halt (only synchronized caches). | |
336 | Spin down on system halt is now implemented. sysfs node | |
337 | /sys/class/scsi_disk/h:c:i:l/manage_start_stop is present if | |
338 | spin down support is available. | |
920a4b10 | 339 | Because issuing spin down command to an already spun down disk |
d9aca22c TH |
340 | makes some disks spin up just to spin down again, libata tracks |
341 | device spindown status to skip the extra spindown command and | |
342 | warn about it. | |
343 | This is to give userspace tools the time to get updated and will | |
344 | be removed after userspace is reasonably updated. | |
920a4b10 TH |
345 | Who: Tejun Heo <htejun@gmail.com> |
346 | ||
347 | --------------------------- | |
348 |