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, 23 insertions, 0 deletions
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index a1c6e9277986..e592dade6420 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -626,3 +626,26 @@ Files: net/netfilter/xt_NOTRACK.c
626When: April 2011 626When: April 2011
627Why: Superseded by xt_CT 627Why: Superseded by xt_CT
628Who: Netfilter developer team <netfilter-devel@vger.kernel.org> 628Who: Netfilter developer team <netfilter-devel@vger.kernel.org>
629
630---------------------------
631
632What: video4linux /dev/vtx teletext API support
633When: 2.6.35
634Files: drivers/media/video/saa5246a.c drivers/media/video/saa5249.c
635 include/linux/videotext.h
636Why: The vtx device nodes have been superseded by vbi device nodes
637 for many years. No applications exist that use the vtx support.
638 Of the two i2c drivers that actually support this API the saa5249
639 has been impossible to use for a year now and no known hardware
640 that supports this device exists. The saa5246a is theoretically
641 supported by the old mxb boards, but it never actually worked.
642
643 In summary: there is no hardware that can use this API and there
644 are no applications actually implementing this API.
645
646 The vtx support still reserves minors 192-223 and we would really
647 like to reuse those for upcoming new functionality. In the unlikely
648 event that new hardware appears that wants to use the functionality
649 provided by the vtx API, then that functionality should be build
650 around the sliced VBI API instead.
651Who: Hans Verkuil <hverkuil@xs4all.nl>