Commit b75396a4ea473a2cd4f2fb99a81b2289265a8021
Committed by
Mauro Carvalho Chehab
Mauro Carvalho Chehab
1 parent
6a4f0623a4
Exists in
master
and in
7 other branches
V4L/DVB: feature-removal: announce videotext.h removal
Signed-off-by: Hans Verkuil <hverkuil@xs4all.nl> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Showing 1 changed file with 23 additions and 0 deletions Side-by-side Diff
Documentation/feature-removal-schedule.txt
| ... | ... | @@ -589,4 +589,27 @@ |
| 589 | 589 | Generally invoked by accident today. |
| 590 | 590 | Seen as doing more harm than good. |
| 591 | 591 | Who: Len Brown <len.brown@intel.com> |
| 592 | + | |
| 593 | +---------------------------- | |
| 594 | + | |
| 595 | +What: video4linux /dev/vtx teletext API support | |
| 596 | +When: 2.6.35 | |
| 597 | +Files: drivers/media/video/saa5246a.c drivers/media/video/saa5249.c | |
| 598 | + include/linux/videotext.h | |
| 599 | +Why: The vtx device nodes have been superseded by vbi device nodes | |
| 600 | + for many years. No applications exist that use the vtx support. | |
| 601 | + Of the two i2c drivers that actually support this API the saa5249 | |
| 602 | + has been impossible to use for a year now and no known hardware | |
| 603 | + that supports this device exists. The saa5246a is theoretically | |
| 604 | + supported by the old mxb boards, but it never actually worked. | |
| 605 | + | |
| 606 | + In summary: there is no hardware that can use this API and there | |
| 607 | + are no applications actually implementing this API. | |
| 608 | + | |
| 609 | + The vtx support still reserves minors 192-223 and we would really | |
| 610 | + like to reuse those for upcoming new functionality. In the unlikely | |
| 611 | + event that new hardware appears that wants to use the functionality | |
| 612 | + provided by the vtx API, then that functionality should be build | |
| 613 | + around the sliced VBI API instead. | |
| 614 | +Who: Hans Verkuil <hverkuil@xs4all.nl> |