aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/feature-removal-schedule.txt
diff options
context:
space:
mode:
authorWim Van Sebroeck <wim@iguana.be>2007-05-01 02:53:01 -0400
committerWim Van Sebroeck <wim@iguana.be>2007-05-01 02:53:01 -0400
commit48a7afe314bfc4d7f50e1608632f503dbba7e013 (patch)
tree4a80e6b96321a71affd1bacea817de93be08894b /Documentation/feature-removal-schedule.txt
parentfb8f7ba077b5c665432082ab205bcd2cb01f6a3c (diff)
parentdc87c3985e9b442c60994308a96f887579addc39 (diff)
Merge /pub/scm/linux/kernel/git/torvalds/linux-2.6
Diffstat (limited to 'Documentation/feature-removal-schedule.txt')
-rw-r--r--Documentation/feature-removal-schedule.txt72
1 files changed, 31 insertions, 41 deletions
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index 0bc8b0b2e103..5c88ba1ea262 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -6,6 +6,18 @@ be removed from this file.
6 6
7--------------------------- 7---------------------------
8 8
9What: V4L2 VIDIOC_G_MPEGCOMP and VIDIOC_S_MPEGCOMP
10When: October 2007
11Why: 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.
16Who: Hans Verkuil <hverkuil@xs4all.nl> and
17 Mauro Carvalho Chehab <mchehab@infradead.org>
18
19---------------------------
20
9What: /sys/devices/.../power/state 21What: /sys/devices/.../power/state
10 dev->power.power_state 22 dev->power.power_state
11 dpm_runtime_{suspend,resume)() 23 dpm_runtime_{suspend,resume)()
@@ -39,17 +51,6 @@ Who: Dan Dennedy <dan@dennedy.org>, Stefan Richter <stefanr@s5r6.in-berlin.de>
39 51
40--------------------------- 52---------------------------
41 53
42What: dv1394 driver (CONFIG_IEEE1394_DV1394)
43When: June 2007
44Why: Replaced by raw1394 + userspace libraries, notably libiec61883. This
45 shift of application support has been indicated on www.linux1394.org
46 and developers' mailinglists for quite some time. Major applications
47 have been converted, with the exception of ffmpeg and hence xine.
48 Piped output of dvgrab2 is a partial equivalent to dv1394.
49Who: Dan Dennedy <dan@dennedy.org>, Stefan Richter <stefanr@s5r6.in-berlin.de>
50
51---------------------------
52
53What: Video4Linux API 1 ioctls and video_decoder.h from Video devices. 54What: Video4Linux API 1 ioctls and video_decoder.h from Video devices.
54When: December 2006 55When: December 2006
55Why: V4L1 AP1 was replaced by V4L2 API. during migration from 2.4 to 2.6 56Why: V4L1 AP1 was replaced by V4L2 API. during migration from 2.4 to 2.6
@@ -145,15 +146,6 @@ Who: Arjan van de Ven <arjan@linux.intel.com>
145 146
146--------------------------- 147---------------------------
147 148
148What: mount/umount uevents
149When: February 2007
150Why: These events are not correct, and do not properly let userspace know
151 when a file system has been mounted or unmounted. Userspace should
152 poll the /proc/mounts file instead to detect this properly.
153Who: Greg Kroah-Hartman <gregkh@suse.de>
154
155---------------------------
156
157What: USB driver API moves to EXPORT_SYMBOL_GPL 149What: USB driver API moves to EXPORT_SYMBOL_GPL
158When: February 2008 150When: February 2008
159Files: include/linux/usb.h, drivers/usb/core/driver.c 151Files: include/linux/usb.h, drivers/usb/core/driver.c
@@ -222,15 +214,6 @@ Who: Adrian Bunk <bunk@stusta.de>
222 214
223--------------------------- 215---------------------------
224 216
225What: IPv4 only connection tracking/NAT/helpers
226When: 2.6.22
227Why: The new layer 3 independant connection tracking replaces the old
228 IPv4 only version. After some stabilization of the new code the
229 old one will be removed.
230Who: Patrick McHardy <kaber@trash.net>
231
232---------------------------
233
234What: ACPI hooks (X86_SPEEDSTEP_CENTRINO_ACPI) in speedstep-centrino driver 217What: ACPI hooks (X86_SPEEDSTEP_CENTRINO_ACPI) in speedstep-centrino driver
235When: December 2006 218When: December 2006
236Why: Speedstep-centrino driver with ACPI hooks and acpi-cpufreq driver are 219Why: Speedstep-centrino driver with ACPI hooks and acpi-cpufreq driver are
@@ -305,18 +288,6 @@ Who: Richard Purdie <rpurdie@rpsys.net>
305 288
306--------------------------- 289---------------------------
307 290
308What: Wireless extensions over netlink (CONFIG_NET_WIRELESS_RTNETLINK)
309When: with the merge of wireless-dev, 2.6.22 or later
310Why: The option/code is
311 * not enabled on most kernels
312 * not required by any userspace tools (except an experimental one,
313 and even there only for some parts, others use ioctl)
314 * pointless since wext is no longer evolving and the ioctl
315 interface needs to be kept
316Who: Johannes Berg <johannes@sipsolutions.net>
317
318---------------------------
319
320What: i8xx_tco watchdog driver 291What: i8xx_tco watchdog driver
321When: in 2.6.22 292When: in 2.6.22
322Why: the i8xx_tco watchdog driver has been replaced by the iTCO_wdt 293Why: the i8xx_tco watchdog driver has been replaced by the iTCO_wdt
@@ -324,3 +295,22 @@ Why: the i8xx_tco watchdog driver has been replaced by the iTCO_wdt
324Who: Wim Van Sebroeck <wim@iguana.be> 295Who: Wim Van Sebroeck <wim@iguana.be>
325 296
326--------------------------- 297---------------------------
298
299What: Multipath cached routing support in ipv4
300When: in 2.6.23
301Why: Code was merged, then submitter immediately disappeared leaving
302 us with no maintainer and lots of bugs. The code should not have
303 been merged in the first place, and many aspects of it's
304 implementation are blocking more critical core networking
305 development. It's marked EXPERIMENTAL and no distribution
306 enables it because it cause obscure crashes due to unfixable bugs
307 (interfaces don't return errors so memory allocation can't be
308 handled, calling contexts of these interfaces make handling
309 errors impossible too because they get called after we've
310 totally commited to creating a route object, for example).
311 This problem has existed for years and no forward progress
312 has ever been made, and nobody steps up to try and salvage
313 this code, so we're going to finally just get rid of it.
314Who: David S. Miller <davem@davemloft.net>
315
316---------------------------