aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/feature-removal-schedule.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/feature-removal-schedule.txt')
-rw-r--r--Documentation/feature-removal-schedule.txt40
1 files changed, 16 insertions, 24 deletions
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index f3da8c0a3af2..d8f36f984faa 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -98,7 +98,7 @@ Who: Pavel Machek <pavel@ucw.cz>
98--------------------------- 98---------------------------
99 99
100What: Video4Linux API 1 ioctls and from Video devices. 100What: Video4Linux API 1 ioctls and from Video devices.
101When: July 2009 101When: kernel 2.6.38
102Files: include/linux/videodev.h 102Files: include/linux/videodev.h
103Check: include/linux/videodev.h 103Check: include/linux/videodev.h
104Why: V4L1 AP1 was replaced by V4L2 API during migration from 2.4 to 2.6 104Why: V4L1 AP1 was replaced by V4L2 API during migration from 2.4 to 2.6
@@ -116,6 +116,21 @@ Who: Mauro Carvalho Chehab <mchehab@infradead.org>
116 116
117--------------------------- 117---------------------------
118 118
119What: Video4Linux obsolete drivers using V4L1 API
120When: kernel 2.6.38
121Files: drivers/staging/cpia/* drivers/staging/stradis/*
122Check: drivers/staging/cpia/cpia.c drivers/staging/stradis/stradis.c
123Why: There are some drivers still using V4L1 API, despite all efforts we've done
124 to migrate. Those drivers are for obsolete hardware that the old maintainer
125 didn't care (or not have the hardware anymore), and that no other developer
126 could find any hardware to buy. They probably have no practical usage today,
127 and people with such old hardware could probably keep using an older version
128 of the kernel. Those drivers will be moved to staging on 2.6.37 and, if nobody
129 care enough to port and test them with V4L2 API, they'll be removed on 2.6.38.
130Who: Mauro Carvalho Chehab <mchehab@infradead.org>
131
132---------------------------
133
119What: sys_sysctl 134What: sys_sysctl
120When: September 2010 135When: September 2010
121Option: CONFIG_SYSCTL_SYSCALL 136Option: CONFIG_SYSCTL_SYSCALL
@@ -470,29 +485,6 @@ When: April 2011
470Why: Superseded by xt_CT 485Why: Superseded by xt_CT
471Who: Netfilter developer team <netfilter-devel@vger.kernel.org> 486Who: Netfilter developer team <netfilter-devel@vger.kernel.org>
472 487
473---------------------------
474
475What: video4linux /dev/vtx teletext API support
476When: 2.6.35
477Files: drivers/media/video/saa5246a.c drivers/media/video/saa5249.c
478 include/linux/videotext.h
479Why: The vtx device nodes have been superseded by vbi device nodes
480 for many years. No applications exist that use the vtx support.
481 Of the two i2c drivers that actually support this API the saa5249
482 has been impossible to use for a year now and no known hardware
483 that supports this device exists. The saa5246a is theoretically
484 supported by the old mxb boards, but it never actually worked.
485
486 In summary: there is no hardware that can use this API and there
487 are no applications actually implementing this API.
488
489 The vtx support still reserves minors 192-223 and we would really
490 like to reuse those for upcoming new functionality. In the unlikely
491 event that new hardware appears that wants to use the functionality
492 provided by the vtx API, then that functionality should be build
493 around the sliced VBI API instead.
494Who: Hans Verkuil <hverkuil@xs4all.nl>
495
496---------------------------- 488----------------------------
497 489
498What: IRQF_DISABLED 490What: IRQF_DISABLED