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 | ||
1ebfd79e PM |
9 | What: /sys/devices/.../power/state |
10 | dev->power.power_state | |
11 | dpm_runtime_{suspend,resume)() | |
12 | When: July 2007 | |
13 | Why: Broken design for runtime control over driver power states, confusing | |
14 | driver-internal runtime power management with: mechanisms to support | |
15 | system-wide sleep state transitions; event codes that distinguish | |
16 | different phases of swsusp "sleep" transitions; and userspace policy | |
17 | inputs. This framework was never widely used, and most attempts to | |
18 | use it were broken. Drivers should instead be exposing domain-specific | |
19 | interfaces either to kernel or to userspace. | |
20 | Who: Pavel Machek <pavel@suse.cz> | |
21 | ||
22 | --------------------------- | |
23 | ||
98e7f294 AB |
24 | What: RAW driver (CONFIG_RAW_DRIVER) |
25 | When: December 2005 | |
26 | Why: declared obsolete since kernel 2.6.3 | |
27 | O_DIRECT can be used instead | |
28 | Who: Adrian Bunk <bunk@stusta.de> | |
29 | ||
30 | --------------------------- | |
31 | ||
aafda4e0 AB |
32 | What: drivers that were depending on OBSOLETE_OSS_DRIVER |
33 | (config options already removed) | |
34 | When: before 2.6.19 | |
cecd1ca0 AB |
35 | Why: OSS drivers with ALSA replacements |
36 | Who: Adrian Bunk <bunk@stusta.de> | |
37 | ||
38 | --------------------------- | |
39 | ||
a1446c7f | 40 | What: raw1394: requests of type RAW1394_REQ_ISO_SEND, RAW1394_REQ_ISO_LISTEN |
d0aef39f | 41 | When: November 2006 |
a1446c7f JM |
42 | Why: Deprecated in favour of the new ioctl-based rawiso interface, which is |
43 | more efficient. You should really be using libraw1394 for raw1394 | |
44 | access anyway. | |
d0aef39f | 45 | Who: Jody McIntyre <scjody@modernduck.com> |
937df8df GC |
46 | |
47 | --------------------------- | |
48 | ||
875c296b | 49 | What: Video4Linux API 1 ioctls and video_decoder.h from Video devices. |
48c06d5e | 50 | When: December 2006 |
875c296b MCC |
51 | Why: V4L1 AP1 was replaced by V4L2 API. during migration from 2.4 to 2.6 |
52 | series. The old API have lots of drawbacks and don't provide enough | |
53 | means to work with all video and audio standards. The newer API is | |
54 | already available on the main drivers and should be used instead. | |
55 | Newer drivers should use v4l_compat_translate_ioctl function to handle | |
56 | old calls, replacing to newer ones. | |
57 | Decoder iocts are using internally to allow video drivers to | |
58 | communicate with video decoders. This should also be improved to allow | |
59 | V4L2 calls being translated into compatible internal ioctls. | |
60 | Who: Mauro Carvalho Chehab <mchehab@brturbo.com.br> | |
61 | ||
62 | --------------------------- | |
63 | ||
35fa2048 EB |
64 | What: sys_sysctl |
65 | When: January 2007 | |
66 | Why: The same information is available through /proc/sys and that is the | |
67 | interface user space prefers to use. And there do not appear to be | |
68 | any existing user in user space of sys_sysctl. The additional | |
69 | maintenance overhead of keeping a set of binary names gets | |
70 | in the way of doing a good job of maintaining this interface. | |
71 | ||
72 | Who: Eric Biederman <ebiederm@xmission.com> | |
73 | ||
74 | --------------------------- | |
75 | ||
bf45d9b0 DB |
76 | What: PCMCIA control ioctl (needed for pcmcia-cs [cardmgr, cardctl]) |
77 | When: November 2005 | |
78 | Files: drivers/pcmcia/: pcmcia_ioctl.c | |
79 | Why: With the 16-bit PCMCIA subsystem now behaving (almost) like a | |
80 | normal hotpluggable bus, and with it using the default kernel | |
81 | infrastructure (hotplug, driver core, sysfs) keeping the PCMCIA | |
82 | control ioctl needed by cardmgr and cardctl from pcmcia-cs is | |
83 | unnecessary, and makes further cleanups and integration of the | |
84 | PCMCIA subsystem into the Linux kernel device driver model more | |
85 | difficult. The features provided by cardmgr and cardctl are either | |
86 | handled by the kernel itself now or are available in the new | |
87 | pcmciautils package available at | |
88 | http://kernel.org/pub/linux/utils/kernel/pcmcia/ | |
89 | Who: Dominik Brodowski <linux@brodo.de> | |
7af4cc3f HW |
90 | |
91 | --------------------------- | |
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> | |
49705b77 CH |
102 | |
103 | --------------------------- | |
104 | ||
ac515898 CH |
105 | What: remove EXPORT_SYMBOL(kernel_thread) |
106 | When: August 2006 | |
107 | Files: arch/*/kernel/*_ksyms.c | |
108 | Why: kernel_thread is a low-level implementation detail. Drivers should | |
109 | use the <linux/kthread.h> API instead which shields them from | |
110 | implementation details and provides a higherlevel interface that | |
111 | prevents bugs and code duplication | |
112 | Who: Christoph Hellwig <hch@lst.de> | |
113 | ||
114 | --------------------------- | |
115 | ||
a9df3d0f IM |
116 | What: CONFIG_FORCED_INLINING |
117 | When: June 2006 | |
118 | Why: Config option is there to see if gcc is good enough. (in january | |
119 | 2006). If it is, the behavior should just be the default. If it's not, | |
120 | the option should just go away entirely. | |
121 | Who: Arjan van de Ven | |
122 | ||
123 | --------------------------- | |
124 | ||
e8a00334 N |
125 | What: START_ARRAY ioctl for md |
126 | When: July 2006 | |
127 | Files: drivers/md/md.c | |
128 | Why: Not reliable by design - can fail when most needed. | |
129 | Alternatives exist | |
130 | Who: NeilBrown <neilb@suse.de> | |
e0c9b797 RB |
131 | |
132 | --------------------------- | |
133 | ||
c0d3c0c0 B |
134 | What: eepro100 network driver |
135 | When: January 2007 | |
136 | Why: replaced by the e100 driver | |
137 | Who: Adrian Bunk <bunk@stusta.de> | |
3c9b3a85 JG |
138 | |
139 | --------------------------- | |
140 | ||
1e5f5e5c AB |
141 | What: drivers depending on OSS_OBSOLETE_DRIVER |
142 | When: options in 2.6.20, code in 2.6.22 | |
143 | Why: OSS drivers with ALSA replacements | |
144 | Who: Adrian Bunk <bunk@stusta.de> | |
145 | ||
146 | --------------------------- | |
147 | ||
051d9897 RK |
148 | What: pci_module_init(driver) |
149 | When: January 2007 | |
150 | Why: Is replaced by pci_register_driver(pci_driver). | |
151 | Who: Richard Knutsson <ricknu-0@student.ltu.se> and Greg Kroah-Hartman <gregkh@suse.de> | |
c5e3fbf2 JD |
152 | |
153 | --------------------------- | |
154 | ||
7d99b7d6 TG |
155 | What: Usage of invalid timevals in setitimer |
156 | When: March 2007 | |
157 | Why: POSIX requires to validate timevals in the setitimer call. This | |
158 | was never done by Linux. The invalid (e.g. negative timevals) were | |
159 | silently converted to more or less random timeouts and intervals. | |
160 | Until the removal a per boot limited number of warnings is printed | |
161 | and the timevals are sanitized. | |
162 | ||
163 | Who: Thomas Gleixner <tglx@linutronix.de> | |
164 | ||
165 | --------------------------- | |
166 | ||
c5e3fbf2 JD |
167 | What: I2C interface of the it87 driver |
168 | When: January 2007 | |
169 | Why: The ISA interface is faster and should be always available. The I2C | |
170 | probing is also known to cause trouble in at least one case (see | |
171 | bug #5889.) | |
172 | Who: Jean Delvare <khali@linux-fr.org> | |
fa675765 GKH |
173 | |
174 | --------------------------- | |
175 | ||
f71d20e9 AV |
176 | What: Unused EXPORT_SYMBOL/EXPORT_SYMBOL_GPL exports |
177 | (temporary transition config option provided until then) | |
178 | The transition config option will also be removed at the same time. | |
179 | When: before 2.6.19 | |
180 | Why: Unused symbols are both increasing the size of the kernel binary | |
181 | and are often a sign of "wrong API" | |
182 | Who: Arjan van de Ven <arjan@linux.intel.com> | |
183 | ||
184 | --------------------------- | |
185 | ||
fa675765 GKH |
186 | What: mount/umount uevents |
187 | When: February 2007 | |
188 | Why: These events are not correct, and do not properly let userspace know | |
189 | when a file system has been mounted or unmounted. Userspace should | |
190 | poll the /proc/mounts file instead to detect this properly. | |
191 | Who: Greg Kroah-Hartman <gregkh@suse.de> | |
cf028d17 RB |
192 | |
193 | --------------------------- | |
194 | ||
b87ba0a3 GKH |
195 | What: USB driver API moves to EXPORT_SYMBOL_GPL |
196 | When: Febuary 2008 | |
197 | Files: include/linux/usb.h, drivers/usb/core/driver.c | |
198 | Why: The USB subsystem has changed a lot over time, and it has been | |
199 | possible to create userspace USB drivers using usbfs/libusb/gadgetfs | |
200 | that operate as fast as the USB bus allows. Because of this, the USB | |
201 | subsystem will not be allowing closed source kernel drivers to | |
202 | register with it, after this grace period is over. If anyone needs | |
203 | any help in converting their closed source drivers over to use the | |
204 | userspace filesystems, please contact the | |
205 | linux-usb-devel@lists.sourceforge.net mailing list, and the developers | |
206 | there will be glad to help you out. | |
207 | Who: Greg Kroah-Hartman <gregkh@suse.de> | |
208 | ||
209 | --------------------------- | |
93fac704 NP |
210 | |
211 | What: find_trylock_page | |
212 | When: January 2007 | |
213 | Why: The interface no longer has any callers left in the kernel. It | |
214 | is an odd interface (compared with other find_*_page functions), in | |
215 | that it does not take a refcount to the page, only the page lock. | |
216 | It should be replaced with find_get_page or find_lock_page if possible. | |
217 | This feature removal can be reevaluated if users of the interface | |
218 | cannot cleanly use something else. | |
219 | Who: Nick Piggin <npiggin@suse.de> | |
220 | ||
221 | --------------------------- | |
127fe6af | 222 | |
127fe6af RB |
223 | What: Support for the Momentum / PMC-Sierra Jaguar ATX evaluation board |
224 | When: September 2006 | |
225 | Why: Does no longer build since quite some time, and was never popular, | |
226 | due to the platform being replaced by successor models. Apparently | |
227 | no user base left. It also is one of the last users of | |
228 | WANT_PAGE_VIRTUAL. | |
229 | Who: Ralf Baechle <ralf@linux-mips.org> | |
230 | ||
231 | --------------------------- | |
232 | ||
233 | What: Support for the Momentum Ocelot, Ocelot 3, Ocelot C and Ocelot G | |
234 | When: September 2006 | |
235 | Why: Some do no longer build and apparently there is no user base left | |
236 | for these platforms. | |
237 | Who: Ralf Baechle <ralf@linux-mips.org> | |
238 | ||
239 | --------------------------- | |
240 | ||
241 | What: Support for MIPS Technologies' Altas and SEAD evaluation board | |
242 | When: September 2006 | |
243 | Why: Some do no longer build and apparently there is no user base left | |
244 | for these platforms. Hardware out of production since several years. | |
245 | Who: Ralf Baechle <ralf@linux-mips.org> | |
246 | ||
247 | --------------------------- | |
248 | ||
249 | What: Support for the IT8172-based platforms, ITE 8172G and Globespan IVR | |
250 | When: September 2006 | |
251 | Why: Code does no longer build since at least 2.6.0, apparently there is | |
252 | no user base left for these platforms. Hardware out of production | |
253 | since several years and hardly a trace of the manufacturer left on | |
254 | the net. | |
255 | Who: Ralf Baechle <ralf@linux-mips.org> | |
256 | ||
257 | --------------------------- | |
6e213616 TG |
258 | |
259 | What: Interrupt only SA_* flags | |
260 | When: Januar 2007 | |
261 | Why: The interrupt related SA_* flags are replaced by IRQF_* to move them | |
262 | out of the signal namespace. | |
263 | ||
264 | Who: Thomas Gleixner <tglx@linutronix.de> | |
265 | ||
266 | --------------------------- | |
5a017483 JD |
267 | |
268 | What: i2c-ite and i2c-algo-ite drivers | |
269 | When: September 2006 | |
270 | Why: These drivers never compiled since they were added to the kernel | |
271 | tree 5 years ago. This feature removal can be reevaluated if | |
272 | someone shows interest in the drivers, fixes them and takes over | |
273 | maintenance. | |
274 | http://marc.theaimsgroup.com/?l=linux-mips&m=115040510817448 | |
275 | Who: Jean Delvare <khali@linux-fr.org> | |
276 | ||
277 | --------------------------- | |
10ea6ac8 PM |
278 | |
279 | What: Bridge netfilter deferred IPv4/IPv6 output hook calling | |
280 | When: January 2007 | |
281 | Why: The deferred output hooks are a layering violation causing unusual | |
282 | and broken behaviour on bridge devices. Examples of things they | |
283 | break include QoS classifation using the MARK or CLASSIFY targets, | |
284 | the IPsec policy match and connection tracking with VLANs on a | |
285 | bridge. Their only use is to enable bridge output port filtering | |
286 | within iptables with the physdev match, which can also be done by | |
287 | combining iptables and ebtables using netfilter marks. Until it | |
288 | will get removed the hook deferral is disabled by default and is | |
289 | only enabled when needed. | |
290 | ||
291 | Who: Patrick McHardy <kaber@trash.net> | |
292 | ||
293 | --------------------------- | |
080f22c0 SH |
294 | |
295 | What: frame diverter | |
296 | When: November 2006 | |
297 | Why: The frame diverter is included in most distribution kernels, but is | |
298 | broken. It does not correctly handle many things: | |
299 | - IPV6 | |
300 | - non-linear skb's | |
301 | - network device RCU on removal | |
302 | - input frames not correctly checked for protocol errors | |
303 | It also adds allocation overhead even if not enabled. | |
304 | It is not clear if anyone is still using it. | |
305 | Who: Stephen Hemminger <shemminger@osdl.org> | |
306 | ||
d81d9d6b KS |
307 | --------------------------- |
308 | ||
309 | ||
310 | What: PHYSDEVPATH, PHYSDEVBUS, PHYSDEVDRIVER in the uevent environment | |
311 | When: Oktober 2008 | |
312 | Why: The stacking of class devices makes these values misleading and | |
313 | inconsistent. | |
314 | Class devices should not carry any of these properties, and bus | |
315 | devices have SUBSYTEM and DRIVER as a replacement. | |
316 | Who: Kay Sievers <kay.sievers@suse.de> | |
317 | ||
318 | --------------------------- | |
6c805d2c JD |
319 | |
320 | What: i2c-isa | |
321 | When: December 2006 | |
322 | Why: i2c-isa is a non-sense and doesn't fit in the device driver | |
323 | model. Drivers relying on it are better implemented as platform | |
324 | drivers. | |
325 | Who: Jean Delvare <khali@linux-fr.org> | |
326 | ||
327 | --------------------------- |