|author||Hans Verkuil <firstname.lastname@example.org>||2010-03-22 05:43:08 -0300|
|committer||Mauro Carvalho Chehab <email@example.com>||2010-05-06 19:20:50 -0300|
V4L/DVB: feature-removal: announce videotext.h removal
Signed-off-by: Hans Verkuil <firstname.lastname@example.org> Signed-off-by: Mauro Carvalho Chehab <email@example.com>
Diffstat (limited to 'Documentation/feature-removal-schedule.txt')
1 files changed, 23 insertions, 0 deletions
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index ed511af0f79..05df0b7514b 100644
@@ -589,3 +589,26 @@ Why: Useful in 2003, implementation is a hack.
Generally invoked by accident today.
Seen as doing more harm than good.
Who: Len Brown <firstname.lastname@example.org>
+What: video4linux /dev/vtx teletext API support
+Files: drivers/media/video/saa5246a.c drivers/media/video/saa5249.c
+Why: The vtx device nodes have been superseded by vbi device nodes
+ for many years. No applications exist that use the vtx support.
+ Of the two i2c drivers that actually support this API the saa5249
+ has been impossible to use for a year now and no known hardware
+ that supports this device exists. The saa5246a is theoretically
+ supported by the old mxb boards, but it never actually worked.
+ In summary: there is no hardware that can use this API and there
+ are no applications actually implementing this API.
+ The vtx support still reserves minors 192-223 and we would really
+ like to reuse those for upcoming new functionality. In the unlikely
+ event that new hardware appears that wants to use the functionality
+ provided by the vtx API, then that functionality should be build
+ around the sliced VBI API instead.
+Who: Hans Verkuil <email@example.com>