Re: bttv driver bug: VIDIOC_ENUMSTD returns wrong NTSC value

[Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxx>]

Hi Cláudio,

On Sat, 26 Jan 2008 22:30:07 -0300
Cláudio da Silveira Pinheiro <taupter@xxxxxxxxx> wrote:

> Hello Mauro and all,
> 
> 
> I found this issue and reported about it Sat, 19 Jan 2008 06:16:20 -0300.
> I got no feedback from this issue for a full week.
> 
> It refers to a discrepancy between what the V4L2 specification says is NTSC 
> and what bttv driver reports as being NTSC.
> The same problem doesn't occur with other bttv-supported standards, as PAL, 
> PAL-M, PAL-N, SECAM and others.
> 
> I'd like to know if this is an invalid bug or if it will be fixed upstream, or 
> if I should send a patch.

> bttv reports NTSC as 36864  0x9000  1001000000000000
> ( V4L2_STD_NTSC_M | V4L2_STD_NTSC_M_KR )
> 
> videodev2.h says NTSC is 45056  0xB000  1011000000000000
> ( V4L2_STD_NTSC_M |  V4L2_STD_NTSC_M_JP | V4L2_STD_NTSC_M_KR )

ENUMSTD returns a bit mask of the supported video standards. In this case, bttv is known to
work with both American (V4L2_STD_NTSC_M) and Korean NTSC versions (V4L2_STD_NTSC_M_KR).

Probably, it would also work with NTSC/M format in Japan (V4L2_STD_NTSC_M_JP),
but maybe some special configuration would be needed for the audio decoder
chips. For us to add also V4L2_STD_NTSC_M_JP, we would need a positive feedback
from someone in Japan.

Cheers,
Mauro

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list