blob: b1c921c27519a0953591b6a64159e46856e7558d [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
Len Brown3b70b2e2011-04-01 15:08:48 -04009What: x86 floppy disable_hlt
10When: 2012
11Why: ancient workaround of dubious utility clutters the
12 code used by everybody else.
13Who: Len Brown <len.brown@intel.com>
14
15---------------------------
16
Len Brown99c63222011-04-01 15:19:23 -040017What: CONFIG_APM_CPU_IDLE, and its ability to call APM BIOS in idle
18When: 2012
19Why: This optional sub-feature of APM is of dubious reliability,
20 and ancient APM laptops are likely better served by calling HLT.
21 Deleting CONFIG_APM_CPU_IDLE allows x86 to stop exporting
22 the pm_idle function pointer to modules.
23Who: Len Brown <len.brown@intel.com>
24
25----------------------------
26
Len Browncdaab4a2011-04-01 15:41:17 -040027What: x86_32 "no-hlt" cmdline param
28When: 2012
29Why: remove a branch from idle path, simplify code used by everybody.
30 This option disabled the use of HLT in idle and machine_halt()
31 for hardware that was flakey 15-years ago. Today we have
32 "idle=poll" that removed HLT from idle, and so if such a machine
33 is still running the upstream kernel, "idle=poll" is likely sufficient.
34Who: Len Brown <len.brown@intel.com>
35
36----------------------------
37
Len Brown5d4c47e2011-04-01 15:46:09 -040038What: x86 "idle=mwait" cmdline param
39When: 2012
40Why: simplify x86 idle code
41Who: Len Brown <len.brown@intel.com>
42
43----------------------------
44
Luis R. Rodriguez4d8cd262009-09-08 12:09:47 -070045What: PRISM54
46When: 2.6.34
47
48Why: prism54 FullMAC PCI / Cardbus devices used to be supported only by the
49 prism54 wireless driver. After Intersil stopped selling these
50 devices in preference for the newer more flexible SoftMAC devices
51 a SoftMAC device driver was required and prism54 did not support
52 them. The p54pci driver now exists and has been present in the kernel for
53 a while. This driver supports both SoftMAC devices and FullMAC devices.
54 The main difference between these devices was the amount of memory which
55 could be used for the firmware. The SoftMAC devices support a smaller
56 amount of memory. Because of this the SoftMAC firmware fits into FullMAC
57 devices's memory. p54pci supports not only PCI / Cardbus but also USB
58 and SPI. Since p54pci supports all devices prism54 supports
59 you will have a conflict. I'm not quite sure how distributions are
60 handling this conflict right now. prism54 was kept around due to
61 claims users may experience issues when using the SoftMAC driver.
62 Time has passed users have not reported issues. If you use prism54
63 and for whatever reason you cannot use p54pci please let us know!
64 E-mail us at: linux-wireless@vger.kernel.org
65
66 For more information see the p54 wiki page:
67
68 http://wireless.kernel.org/en/users/Drivers/p54
69
70Who: Luis R. Rodriguez <lrodriguez@atheros.com>
71
72---------------------------
73
Robin Getz9d9b8fb2009-06-17 16:25:54 -070074What: IRQF_SAMPLE_RANDOM
75Check: IRQF_SAMPLE_RANDOM
76When: July 2009
77
78Why: Many of IRQF_SAMPLE_RANDOM users are technically bogus as entropy
79 sources in the kernel's current entropy model. To resolve this, every
80 input point to the kernel's entropy pool needs to better document the
81 type of entropy source it actually is. This will be replaced with
82 additional add_*_randomness functions in drivers/char/random.c
83
84Who: Robin Getz <rgetz@blackfin.uclinux.org> & Matt Mackall <mpm@selenic.com>
85
86---------------------------
87
Jiri Slabyb694e522010-01-27 23:47:50 +010088What: Deprecated snapshot ioctls
89When: 2.6.36
90
91Why: The ioctls in kernel/power/user.c were marked as deprecated long time
92 ago. Now they notify users about that so that they need to replace
93 their userspace. After some more time, remove them completely.
94
95Who: Jiri Slaby <jirislaby@gmail.com>
96
97---------------------------
98
Luis R. Rodriguez6ee7d332009-03-20 23:53:06 -040099What: The ieee80211_regdom module parameter
Luis R. Rodriguez8a5117d2009-03-24 21:21:07 -0400100When: March 2010 / desktop catchup
Luis R. Rodriguez6ee7d332009-03-20 23:53:06 -0400101
102Why: This was inherited by the CONFIG_WIRELESS_OLD_REGULATORY code,
103 and currently serves as an option for users to define an
104 ISO / IEC 3166 alpha2 code for the country they are currently
105 present in. Although there are userspace API replacements for this
106 through nl80211 distributions haven't yet caught up with implementing
107 decent alternatives through standard GUIs. Although available as an
108 option through iw or wpa_supplicant its just a matter of time before
109 distributions pick up good GUI options for this. The ideal solution
110 would actually consist of intelligent designs which would do this for
111 the user automatically even when travelling through different countries.
112 Until then we leave this module parameter as a compromise.
113
114 When userspace improves with reasonable widely-available alternatives for
115 this we will no longer need this module parameter. This entry hopes that
116 by the super-futuristically looking date of "March 2010" we will have
117 such replacements widely available.
118
119Who: Luis R. Rodriguez <lrodriguez@atheros.com>
120
121---------------------------
122
Alan Stern471d0552007-07-12 16:55:07 -0400123What: dev->power.power_state
Pavel Machek1ebfd792006-08-30 13:50:27 -0700124When: July 2007
125Why: Broken design for runtime control over driver power states, confusing
126 driver-internal runtime power management with: mechanisms to support
127 system-wide sleep state transitions; event codes that distinguish
128 different phases of swsusp "sleep" transitions; and userspace policy
129 inputs. This framework was never widely used, and most attempts to
130 use it were broken. Drivers should instead be exposing domain-specific
131 interfaces either to kernel or to userspace.
Pavel Macheka2531292010-07-18 14:27:13 +0200132Who: Pavel Machek <pavel@ucw.cz>
Pavel Machek1ebfd792006-08-30 13:50:27 -0700133
134---------------------------
135
Eric W. Biederman7058cb02007-10-18 03:05:58 -0700136What: sys_sysctl
137When: September 2010
138Option: CONFIG_SYSCTL_SYSCALL
139Why: The same information is available in a more convenient from
140 /proc/sys, and none of the sysctl variables appear to be
141 important performance wise.
142
143 Binary sysctls are a long standing source of subtle kernel
144 bugs and security issues.
145
146 When I looked several months ago all I could find after
147 searching several distributions were 5 user space programs and
148 glibc (which falls back to /proc/sys) using this syscall.
149
150 The man page for sysctl(2) documents it as unusable for user
151 space programs.
152
153 sysctl(2) is not generally ABI compatible to a 32bit user
154 space application on a 64bit and a 32bit kernel.
155
156 For the last several months the policy has been no new binary
157 sysctls and no one has put forward an argument to use them.
158
159 Binary sysctls issues seem to keep happening appearing so
160 properly deprecating them (with a warning to user space) and a
161 2 year grace warning period will mean eventually we can kill
162 them and end the pain.
163
164 In the mean time individual binary sysctls can be dealt with
165 in a piecewise fashion.
166
167Who: Eric Biederman <ebiederm@xmission.com>
168
169---------------------------
170
David Rientjes51b1bd22010-08-09 17:19:47 -0700171What: /proc/<pid>/oom_adj
172When: August 2012
173Why: /proc/<pid>/oom_adj allows userspace to influence the oom killer's
174 badness heuristic used to determine which task to kill when the kernel
175 is out of memory.
176
177 The badness heuristic has since been rewritten since the introduction of
178 this tunable such that its meaning is deprecated. The value was
179 implemented as a bitshift on a score generated by the badness()
180 function that did not have any precise units of measure. With the
181 rewrite, the score is given as a proportion of available memory to the
182 task allocating pages, so using a bitshift which grows the score
183 exponentially is, thus, impossible to tune with fine granularity.
184
185 A much more powerful interface, /proc/<pid>/oom_score_adj, was
186 introduced with the oom killer rewrite that allows users to increase or
187 decrease the badness() score linearly. This interface will replace
188 /proc/<pid>/oom_adj.
189
190 A warning will be emitted to the kernel log if an application uses this
191 deprecated interface. After it is printed once, future warnings will be
192 suppressed until the kernel is rebooted.
193
194---------------------------
195
Andres Salomoncf8e9082011-01-12 17:00:12 -0800196What: CS5535/CS5536 obsolete GPIO driver
197When: June 2011
198Files: drivers/staging/cs5535_gpio/*
199Check: drivers/staging/cs5535_gpio/cs5535_gpio.c
200Why: A newer driver replaces this; it is drivers/gpio/cs5535-gpio.c, and
201 integrates with the Linux GPIO subsystem. The old driver has been
202 moved to staging, and will be removed altogether around 2.6.40.
203 Please test the new driver, and ensure that the functionality you
204 need and any bugfixes from the old driver are available in the new
205 one.
206Who: Andres Salomon <dilinger@queued.net>
207
208--------------------------
209
Christoph Hellwigac515892006-03-24 03:18:22 -0800210What: remove EXPORT_SYMBOL(kernel_thread)
211When: August 2006
212Files: arch/*/kernel/*_ksyms.c
Andy Whitcroftf0a594c2007-07-19 01:48:34 -0700213Check: kernel_thread
Christoph Hellwigac515892006-03-24 03:18:22 -0800214Why: kernel_thread is a low-level implementation detail. Drivers should
215 use the <linux/kthread.h> API instead which shields them from
216 implementation details and provides a higherlevel interface that
217 prevents bugs and code duplication
218Who: Christoph Hellwig <hch@lst.de>
219
220---------------------------
221
Arjan van de Venf71d20e2006-06-28 04:26:45 -0700222What: Unused EXPORT_SYMBOL/EXPORT_SYMBOL_GPL exports
223 (temporary transition config option provided until then)
224 The transition config option will also be removed at the same time.
225When: before 2.6.19
226Why: Unused symbols are both increasing the size of the kernel binary
227 and are often a sign of "wrong API"
228Who: Arjan van de Ven <arjan@linux.intel.com>
229
230---------------------------
231
Kay Sieversd81d9d62006-08-13 06:17:09 +0200232What: PHYSDEVPATH, PHYSDEVBUS, PHYSDEVDRIVER in the uevent environment
Dominik Brodowskiacbd39f2006-09-30 22:41:43 -0400233When: October 2008
Kay Sieversd81d9d62006-08-13 06:17:09 +0200234Why: The stacking of class devices makes these values misleading and
235 inconsistent.
236 Class devices should not carry any of these properties, and bus
237 devices have SUBSYTEM and DRIVER as a replacement.
238Who: Kay Sievers <kay.sievers@suse.de>
239
240---------------------------
Jean Delvare6c805d22006-08-13 23:45:52 +0200241
Zhang Ruib981c592007-01-29 11:02:30 +0800242What: ACPI procfs interface
Zhang Rui8b8eb7d2007-07-18 17:23:24 +0800243When: July 2008
244Why: ACPI sysfs conversion should be finished by January 2008.
245 ACPI procfs interface will be removed in July 2008 so that
246 there is enough time for the user space to catch up.
Zhang Ruib981c592007-01-29 11:02:30 +0800247Who: Zhang Rui <rui.zhang@intel.com>
248
249---------------------------
250
Zhang Rui6d855fc2011-01-10 11:16:30 +0800251What: CONFIG_ACPI_PROCFS_POWER
252When: 2.6.39
253Why: sysfs I/F for ACPI power devices, including AC and Battery,
Justin P. Mattock70f23fd2011-05-10 10:16:21 +0200254 has been working in upstream kernel since 2.6.24, Sep 2007.
Zhang Rui6d855fc2011-01-10 11:16:30 +0800255 In 2.6.37, we make the sysfs I/F always built in and this option
256 disabled by default.
257 Remove this option and the ACPI power procfs interface in 2.6.39.
258Who: Zhang Rui <rui.zhang@intel.com>
259
260---------------------------
261
Len Brown14e04fb2007-08-23 15:20:26 -0400262What: /proc/acpi/event
263When: February 2008
264Why: /proc/acpi/event has been replaced by events via the input layer
265 and netlink since 2.6.23.
266Who: Len Brown <len.brown@intel.com>
267
268---------------------------
269
Thomas Gleixner914d97f2007-10-11 11:20:05 +0200270What: i386/x86_64 bzImage symlinks
Ingo Molnar19b4e7f2008-04-10 10:12:27 +0200271When: April 2010
Thomas Gleixner914d97f2007-10-11 11:20:05 +0200272
273Why: The i386/x86_64 merge provides a symlink to the old bzImage
274 location so not yet updated user space tools, e.g. package
275 scripts, do not break.
276Who: Thomas Gleixner <tglx@linutronix.de>
Linus Torvalds038a5002007-10-11 19:40:14 -0700277
278---------------------------
279
David Brownell8a0cecf2009-04-02 16:57:06 -0700280What: GPIO autorequest on gpio_direction_{input,output}() in gpiolib
281When: February 2010
282Why: All callers should use explicit gpio_request()/gpio_free().
283 The autorequest mechanism in gpiolib was provided mostly as a
284 migration aid for legacy GPIO interfaces (for SOC based GPIOs).
285 Those users have now largely migrated. Platforms implementing
286 the GPIO interfaces without using gpiolib will see no changes.
287Who: David Brownell <dbrownell@users.sourceforge.net>
288---------------------------
289
Michael Buescheb189d82008-01-28 14:47:41 -0800290What: b43 support for firmware revision < 410
Michael Bueschc5572892008-12-27 18:26:39 +0100291When: The schedule was July 2008, but it was decided that we are going to keep the
292 code as long as there are no major maintanance headaches.
293 So it _could_ be removed _any_ time now, if it conflicts with something new.
Michael Buescheb189d82008-01-28 14:47:41 -0800294Why: The support code for the old firmware hurts code readability/maintainability
295 and slightly hurts runtime performance. Bugfixes for the old firmware
296 are not provided by Broadcom anymore.
297Who: Michael Buesch <mb@bu3sch.de>
David S. Millere88bb412008-02-09 23:08:53 -0800298
299---------------------------
300
Ravikiran G Thirumalai2584e512009-03-31 15:21:26 -0700301What: Ability for non root users to shm_get hugetlb pages based on mlock
302 resource limits
303When: 2.6.31
304Why: Non root users need to be part of /proc/sys/vm/hugetlb_shm_group or
305 have CAP_IPC_LOCK to be able to allocate shm segments backed by
306 huge pages. The mlock based rlimit check to allow shm hugetlb is
307 inconsistent with mmap based allocations. Hence it is being
308 deprecated.
309Who: Ravikiran Thirumalai <kiran@scalex86.org>
310
311---------------------------
312
Rene Herman16d75232008-06-24 19:38:56 +0200313What: CONFIG_THERMAL_HWMON
314When: January 2009
315Why: This option was introduced just to allow older lm-sensors userspace
316 to keep working over the upgrade to 2.6.26. At the scheduled time of
317 removal fixed lm-sensors (2.x or 3.x) should be readily available.
318Who: Rene Herman <rene.herman@gmail.com>
Johannes Berg22bb1be2008-07-10 11:16:47 +0200319
320---------------------------
321
322What: Code that is now under CONFIG_WIRELESS_EXT_SYSFS
323 (in net/core/net-sysfs.c)
324When: After the only user (hal) has seen a release with the patches
325 for enough time, probably some time in 2010.
326Why: Over 1K .text/.data size reduction, data is available in other
327 ways (ioctls)
328Who: Johannes Berg <johannes@sipsolutions.net>
Krzysztof Piotr Oledzki58401572008-07-21 10:01:34 -0700329
330---------------------------
331
Dave Jones753b7ae2009-03-09 15:14:37 -0400332What: sysfs ui for changing p4-clockmod parameters
333When: September 2009
334Why: See commits 129f8ae9b1b5be94517da76009ea956e89104ce8 and
335 e088e4c9cdb618675874becb91b2fd581ee707e6.
336 Removal is subject to fixing any remaining bugs in ACPI which may
337 cause the thermal throttling not to happen at the right time.
338Who: Dave Jones <davej@redhat.com>, Matthew Garrett <mjg@redhat.com>
Thomas Gleixner0e57aa12009-03-13 14:34:05 +0100339
340-----------------------------
341
Alex Chiangf110ca42009-03-20 14:56:56 -0600342What: fakephp and associated sysfs files in /sys/bus/pci/slots/
343When: 2011
344Why: In 2.6.27, the semantics of /sys/bus/pci/slots was redefined to
345 represent a machine's physical PCI slots. The change in semantics
346 had userspace implications, as the hotplug core no longer allowed
347 drivers to create multiple sysfs files per physical slot (required
348 for multi-function devices, e.g.). fakephp was seen as a developer's
349 tool only, and its interface changed. Too late, we learned that
350 there were some users of the fakephp interface.
351
352 In 2.6.30, the original fakephp interface was restored. At the same
353 time, the PCI core gained the ability that fakephp provided, namely
354 function-level hot-remove and hot-add.
355
356 Since the PCI core now provides the same functionality, exposed in:
357
358 /sys/bus/pci/rescan
359 /sys/bus/pci/devices/.../remove
360 /sys/bus/pci/devices/.../rescan
361
362 there is no functional reason to maintain fakephp as well.
363
364 We will keep the existing module so that 'modprobe fakephp' will
365 present the old /sys/bus/pci/slots/... interface for compatibility,
366 but users are urged to migrate their applications to the API above.
367
368 After a reasonable transition period, we will remove the legacy
369 fakephp interface.
370Who: Alex Chiang <achiang@hp.com>
Jean Delvare3f307fb2009-04-13 17:02:13 +0200371
372---------------------------
373
Johannes Bergc64fb012009-06-02 13:01:38 +0200374What: CONFIG_RFKILL_INPUT
375When: 2.6.33
376Why: Should be implemented in userspace, policy daemon.
377Who: Johannes Berg <johannes@sipsolutions.net>
David S. Miller9cbc1cb2009-06-15 03:02:23 -0700378
Andi Kleen45f458e2009-04-28 23:18:26 +0200379----------------------------
380
Tejun Heo93fe4482009-08-06 18:14:26 +0900381What: sound-slot/service-* module aliases and related clutters in
382 sound/sound_core.c
383When: August 2010
384Why: OSS sound_core grabs all legacy minors (0-255) of SOUND_MAJOR
385 (14) and requests modules using custom sound-slot/service-*
386 module aliases. The only benefit of doing this is allowing
387 use of custom module aliases which might as well be considered
388 a bug at this point. This preemptive claiming prevents
389 alternative OSS implementations.
390
391 Till the feature is removed, the kernel will be requesting
392 both sound-slot/service-* and the standard char-major-* module
393 aliases and allow turning off the pre-claiming selectively via
394 CONFIG_SOUND_OSS_CORE_PRECLAIM and soundcore.preclaim_oss
395 kernel parameter.
396
397 After the transition phase is complete, both the custom module
398 aliases and switches to disable it will go away. This removal
399 will also allow making ALSA OSS emulation independent of
400 sound_core. The dependency will be broken then too.
401Who: Tejun Heo <tj@kernel.org>
Alok Katariad0153ca2009-09-29 10:25:24 -0700402
403----------------------------
404
florian@mickler.org69c86372010-02-24 12:05:16 +0100405What: sysfs-class-rfkill state file
406When: Feb 2014
407Files: net/rfkill/core.c
408Why: Documented as obsolete since Feb 2010. This file is limited to 3
409 states while the rfkill drivers can have 4 states.
410Who: anybody or Florian Mickler <florian@mickler.org>
411
412----------------------------
413
414What: sysfs-class-rfkill claim file
415When: Feb 2012
416Files: net/rfkill/core.c
417Why: It is not possible to claim an rfkill driver since 2007. This is
418 Documented as obsolete since Feb 2010.
419Who: anybody or Florian Mickler <florian@mickler.org>
420
421----------------------------
422
Avi Kivitydb358792010-01-26 16:30:06 +0200423What: KVM paravirt mmu host support
424When: January 2011
425Why: The paravirt mmu host support is slower than non-paravirt mmu, both
426 on newer and older hardware. It is already not exposed to the guest,
427 and kept only for live migration purposes.
428Who: Avi Kivity <avi@redhat.com>
Linus Torvaldsc812a512010-03-05 13:12:34 -0800429
430----------------------------
Len Brown4c81ba42010-03-14 16:28:46 -0400431
Wey-Yi Guy2b068612010-03-22 09:17:39 -0700432What: iwlwifi 50XX module parameters
433When: 2.6.40
434Why: The "..50" modules parameters were used to configure 5000 series and
435 up devices; different set of module parameters also available for 4965
436 with same functionalities. Consolidate both set into single place
437 in drivers/net/wireless/iwlwifi/iwl-agn.c
438
439Who: Wey-Yi Guy <wey-yi.w.guy@intel.com>
Wey-Yi Guyd34a5a62010-03-23 10:17:03 -0700440
441----------------------------
442
443What: iwl4965 alias support
444When: 2.6.40
445Why: Internal alias support has been present in module-init-tools for some
446 time, the MODULE_ALIAS("iwl4965") boilerplate aliases can be removed
447 with no impact.
448
449Who: Wey-Yi Guy <wey-yi.w.guy@intel.com>
Patrick McHardy62910552010-04-20 16:02:01 +0200450
Jan Engelhardt0cb47ea2010-03-16 18:25:12 +0100451---------------------------
452
453What: xt_NOTRACK
454Files: net/netfilter/xt_NOTRACK.c
455When: April 2011
456Why: Superseded by xt_CT
457Who: Netfilter developer team <netfilter-devel@vger.kernel.org>
David S. Miller278554b2010-05-12 00:05:35 -0700458
Linus Torvalds6e0b7b22010-05-19 17:09:40 -0700459----------------------------
460
Thomas Gleixner6932bf32010-03-26 00:06:55 +0000461What: IRQF_DISABLED
462When: 2.6.36
463Why: The flag is a NOOP as we run interrupt handlers with interrupts disabled
464Who: Thomas Gleixner <tglx@linutronix.de>
Linus Torvalds6e0b7b22010-05-19 17:09:40 -0700465
466----------------------------
467
FUJITA Tomonori17583362010-08-10 18:03:26 -0700468What: PCI DMA unmap state API
469When: August 2012
470Why: PCI DMA unmap state API (include/linux/pci-dma.h) was replaced
471 with DMA unmap state API (DMA unmap state API can be used for
472 any bus).
473Who: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
474
475----------------------------
FUJITA Tomonoria35274c2010-08-10 18:03:26 -0700476
477What: DMA_xxBIT_MASK macros
478When: Jun 2011
479Why: DMA_xxBIT_MASK macros were replaced with DMA_BIT_MASK() macros.
480Who: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
481
482----------------------------
483
Wey-Yi Guy72645ef2010-10-06 07:42:43 -0700484What: iwlwifi disable_hw_scan module parameters
485When: 2.6.40
486Why: Hareware scan is the prefer method for iwlwifi devices for
487 scanning operation. Remove software scan support for all the
488 iwlwifi devices.
489
490Who: Wey-Yi Guy <wey-yi.w.guy@intel.com>
491
492----------------------------
Linus Torvalds43901102010-10-26 09:55:25 -0700493
NeilBrownc67874f2010-09-22 12:55:07 +1000494What: access to nfsd auth cache through sys_nfsservctl or '.' files
495 in the 'nfsd' filesystem.
496When: 2.6.40
497Why: This is a legacy interface which have been replaced by a more
498 dynamic cache. Continuing to maintain this interface is an
499 unnecessary burden.
500Who: NeilBrown <neilb@suse.de>
501
502----------------------------
Jean Delvaree1e18ee2010-11-15 22:40:38 +0100503
Tejun Heoed413902010-12-14 16:23:10 +0100504What: cancel_rearming_delayed_work[queue]()
505When: 2.6.39
506
507Why: The functions have been superceded by cancel_delayed_work_sync()
508 quite some time ago. The conversion is trivial and there is no
509 in-kernel user left.
510Who: Tejun Heo <tj@kernel.org>
511
512----------------------------
Jean Delvare632bdb22011-01-12 21:55:10 +0100513
514What: Legacy, non-standard chassis intrusion detection interface.
515When: June 2011
516Why: The adm9240, w83792d and w83793 hardware monitoring drivers have
517 legacy interfaces for chassis intrusion detection. A standard
518 interface has been added to each driver, so the legacy interface
519 can be removed.
520Who: Jean Delvare <khali@linux-fr.org>
521
522----------------------------
Michal Hocko552b3722011-02-01 15:52:31 -0800523
Jan Engelhardtcc4fc022011-01-18 17:32:40 +0100524What: xt_connlimit rev 0
525When: 2012
526Who: Jan Engelhardt <jengelh@medozas.de>
527Files: net/netfilter/xt_connlimit.c
528
529----------------------------
David S. Millerda935c62011-02-19 19:17:35 -0800530
Michal Hocko552b3722011-02-01 15:52:31 -0800531What: noswapaccount kernel command line parameter
532When: 2.6.40
533Why: The original implementation of memsw feature enabled by
534 CONFIG_CGROUP_MEM_RES_CTLR_SWAP could be disabled by the noswapaccount
535 kernel parameter (introduced in 2.6.29-rc1). Later on, this decision
536 turned out to be not ideal because we cannot have the feature compiled
537 in and disabled by default and let only interested to enable it
538 (e.g. general distribution kernels might need it). Therefore we have
539 added swapaccount[=0|1] parameter (introduced in 2.6.37) which provides
540 the both possibilities. If we remove noswapaccount we will have
541 less command line parameters with the same functionality and we
542 can also cleanup the parameter handling a bit ().
543Who: Michal Hocko <mhocko@suse.cz>
544
545----------------------------
David S. Miller31111c22011-03-15 13:03:27 -0700546
Florian Westphalde81bbe2011-03-15 20:16:20 +0100547What: ipt_addrtype match include file
548When: 2012
549Why: superseded by xt_addrtype
550Who: Florian Westphal <fw@strlen.de>
551Files: include/linux/netfilter_ipv4/ipt_addrtype.h
552
553----------------------------
Jean Delvarefe6fc252011-03-20 14:50:53 +0100554
555What: i2c_driver.attach_adapter
556 i2c_driver.detach_adapter
557When: September 2011
558Why: These legacy callbacks should no longer be used as i2c-core offers
559 a variety of preferable alternative ways to instantiate I2C devices.
560Who: Jean Delvare <khali@linux-fr.org>
561
562----------------------------
Laurent Pinchart1dc8ddf2010-10-12 12:11:30 -0300563
564What: Support for UVCIOC_CTRL_ADD in the uvcvideo driver
565When: 2.6.42
566Why: The information passed to the driver by this ioctl is now queried
567 dynamically from the device.
568Who: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
569
570----------------------------
571
572What: Support for UVCIOC_CTRL_MAP_OLD in the uvcvideo driver
573When: 2.6.42
574Why: Used only by applications compiled against older driver versions.
575 Superseded by UVCIOC_CTRL_MAP which supports V4L2 menu controls.
576Who: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
577
578----------------------------
579
580What: Support for UVCIOC_CTRL_GET and UVCIOC_CTRL_SET in the uvcvideo driver
581When: 2.6.42
582Why: Superseded by the UVCIOC_CTRL_QUERY ioctl.
583Who: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
584
585----------------------------
Hans Verkuil62936982011-06-13 09:38:54 -0300586
587What: For VIDIOC_S_FREQUENCY the type field must match the device node's type.
588 If not, return -EINVAL.
589When: 3.2
590Why: It makes no sense to switch the tuner to radio mode by calling
591 VIDIOC_S_FREQUENCY on a video node, or to switch the tuner to tv mode by
592 calling VIDIOC_S_FREQUENCY on a radio node. This is the first step of a
593 move to more consistent handling of tv and radio tuners.
594Who: Hans Verkuil <hans.verkuil@cisco.com>
595
596----------------------------
597
598What: Opening a radio device node will no longer automatically switch the
599 tuner mode from tv to radio.
600When: 3.3
601Why: Just opening a V4L device should not change the state of the hardware
602 like that. It's very unexpected and against the V4L spec. Instead, you
603 switch to radio mode by calling VIDIOC_S_FREQUENCY. This is the second
604 and last step of the move to consistent handling of tv and radio tuners.
605Who: Hans Verkuil <hans.verkuil@cisco.com>
606
607----------------------------