diff options
| author | Michael H. Schimek <mschimek@gmx.at> | 2006-01-09 15:25:27 -0200 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab@brturbo.com.br> | 2006-01-09 15:25:27 -0200 |
| commit | 67f1570a0659abba5efbf55cc986187af61bdd52 (patch) | |
| tree | a7c0fe1bbfecfcd418c6549e9eee82b79106f0ba /Documentation/cpu-freq | |
| parent | 7e57819169d4f9a1d7af55fb645ece3fb981e2e3 (diff) | |
| download | blackbird-op-linux-67f1570a0659abba5efbf55cc986187af61bdd52.tar.gz blackbird-op-linux-67f1570a0659abba5efbf55cc986187af61bdd52.zip | |
V4L/DVB (3178): bttv VBI fixes
- V4L2_(G|S|TRY)_FMT returned incorrect VBI start lines for PAL-M,
NTSC-JP, and PAL-60. They also returned an inaccurate VBI offset.
- V4L2_(G|S)_FMT and V4L2_TRY_FMT disagreed about the start of VBI
capturing in PAL and SECAM second field. Note the start line fixes
may break applications using VIDIOCSVBIFMT because this ioctl fails
when the driver does not support exactly the requested parameters.
- V4L2_TRY_FMT did not clear the reserved field in struct
v4l2_vbi_format.
- V4L2_(S|TRY)_FMT did not expect very large or small VBI start or
count values, returning wrong (but safe) counts due to an overflow.
- VIDIOCGVBIFMT confused V4L and V4L2 VBI flags. However this had no
effect because the flags have the same value and bttv never sets
them.
- In v4l_compat_translate_ioctl() the VIDIOC(G|S)VBIFMT code did not
expect V4L2 drivers supporting VBI formats besides V4L2_PIX_FMT_GREY.
Signed-off-by: Michael H. Schimek <mschimek@gmx.at>
Signed-off-by: Hans Verkuil <hverkuil@xs4all.nl>
Signed-off-by: Mauro Carvalho Chehab <mchehab@brturbo.com.br>
Diffstat (limited to 'Documentation/cpu-freq')
0 files changed, 0 insertions, 0 deletions
