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