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.txt23
1 files changed, 0 insertions, 23 deletions
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index 842aa9de84a6..2372fb221969 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -498,29 +498,6 @@ When: April 2011
498Why: Superseded by xt_CT 498Why: Superseded by xt_CT
499Who: Netfilter developer team <netfilter-devel@vger.kernel.org> 499Who: Netfilter developer team <netfilter-devel@vger.kernel.org>
500 500
501---------------------------
502
503What: video4linux /dev/vtx teletext API support
504When: 2.6.35
505Files: drivers/media/video/saa5246a.c drivers/media/video/saa5249.c
506 include/linux/videotext.h
507Why: The vtx device nodes have been superseded by vbi device nodes
508 for many years. No applications exist that use the vtx support.
509 Of the two i2c drivers that actually support this API the saa5249
510 has been impossible to use for a year now and no known hardware
511 that supports this device exists. The saa5246a is theoretically
512 supported by the old mxb boards, but it never actually worked.
513
514 In summary: there is no hardware that can use this API and there
515 are no applications actually implementing this API.
516
517 The vtx support still reserves minors 192-223 and we would really
518 like to reuse those for upcoming new functionality. In the unlikely
519 event that new hardware appears that wants to use the functionality
520 provided by the vtx API, then that functionality should be build
521 around the sliced VBI API instead.
522Who: Hans Verkuil <hverkuil@xs4all.nl>
523
524---------------------------- 501----------------------------
525 502
526What: IRQF_DISABLED 503What: IRQF_DISABLED