diff options
author | Hans Verkuil <hverkuil@xs4all.nl> | 2010-08-06 12:48:00 -0300 |
---|---|---|
committer | Mauro Carvalho Chehab <mchehab@redhat.com> | 2010-10-21 01:05:48 -0200 |
commit | 226c0eeaea6732c686a5f4e06f25e5850cd5dd61 (patch) | |
tree | e956053de69a2d17d8194945247b853b5c38848d /Documentation/ioctl | |
parent | 563711f16f5d5ee8b639a3d6ee4cef199617009c (diff) | |
download | linux-stable-226c0eeaea6732c686a5f4e06f25e5850cd5dd61.tar.gz linux-stable-226c0eeaea6732c686a5f4e06f25e5850cd5dd61.tar.bz2 linux-stable-226c0eeaea6732c686a5f4e06f25e5850cd5dd61.zip |
V4L/DVB: videotext: remove this obsolete API
Remove the vtx (aka videotext aka teletext) API from the v4l2 core.
This API was scheduled for removal in kernel 2.6.35.
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.
Signed-off-by: Hans Verkuil <hverkuil@xs4all.nl>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'Documentation/ioctl')
0 files changed, 0 insertions, 0 deletions