summaryrefslogtreecommitdiff
path: root/v4l_experimental
diff options
context:
space:
mode:
authorHans Verkuil <devnull@localhost>2005-12-14 22:05:02 +0000
committerHans Verkuil <devnull@localhost>2005-12-14 22:05:02 +0000
commita4db01916e0ed8ce17c255805505e8f6bf403673 (patch)
treee0f185f5436098fb274dd8accdbd6dd6bf5e4da0 /v4l_experimental
parentd53188a9c5cbe6cf8875135fe8ba02b0d7251bc8 (diff)
downloadmediapointer-dvb-s2-a4db01916e0ed8ce17c255805505e8f6bf403673.tar.gz
mediapointer-dvb-s2-a4db01916e0ed8ce17c255805505e8f6bf403673.tar.bz2
bttv VBI fixes
From: Michael H. Schimek <mschimek@gmx.at> - 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>
Diffstat (limited to 'v4l_experimental')
0 files changed, 0 insertions, 0 deletions