aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/feature-removal-schedule.txt
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2010-05-10 05:59:37 -0400
committerThomas Gleixner <tglx@linutronix.de>2010-05-10 08:20:42 -0400
commitdbb6be6d5e974c42bbecd183effaa0df69e1dd8b (patch)
tree5735cb47e70853d057a9881dd0ce44b83e88fa63 /Documentation/feature-removal-schedule.txt
parent6a867a395558a7f882d041783e4cdea6744ca2bf (diff)
parentb57f95a38233a2e73b679bea4a5453a1cc2a1cc9 (diff)
Merge branch 'linus' into timers/core
Reason: Further posix_cpu_timer patches depend on mainline changes Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
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 8f8e4241bd90..b93b7810c8bd 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -599,3 +599,26 @@ Why: Useful in 2003, implementation is a hack.
599 Generally invoked by accident today. 599 Generally invoked by accident today.
600 Seen as doing more harm than good. 600 Seen as doing more harm than good.
601Who: Len Brown <len.brown@intel.com> 601Who: Len Brown <len.brown@intel.com>
602
603----------------------------
604
605What: video4linux /dev/vtx teletext API support
606When: 2.6.35
607Files: drivers/media/video/saa5246a.c drivers/media/video/saa5249.c
608 include/linux/videotext.h
609Why: The vtx device nodes have been superseded by vbi device nodes
610 for many years. No applications exist that use the vtx support.
611 Of the two i2c drivers that actually support this API the saa5249
612 has been impossible to use for a year now and no known hardware
613 that supports this device exists. The saa5246a is theoretically
614 supported by the old mxb boards, but it never actually worked.
615
616 In summary: there is no hardware that can use this API and there
617 are no applications actually implementing this API.
618
619 The vtx support still reserves minors 192-223 and we would really
620 like to reuse those for upcoming new functionality. In the unlikely
621 event that new hardware appears that wants to use the functionality
622 provided by the vtx API, then that functionality should be build
623 around the sliced VBI API instead.
624Who: Hans Verkuil <hverkuil@xs4all.nl>