bttv driver bug: VIDIOC_ENUMSTD returns wrong NTSC value

[Cláudio da Silveira Pinheiro <taupter@xxxxxxxxx>]

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.


Thanks in advance,


Cláudio da Silveira Pinheiro



----------  Mensagem reenviada  ----------

Assunto: bttv driver bug: VIDIOC_ENUMSTD returns wrong NTSC value
Data: Sábado 19 Jan 2008
De: Cláudio da Silveira Pinheiro <taupter@xxxxxxxxx>
Para: "video4linux-list: redhat.com" <video4linux-list@xxxxxxxxxx>

Hello all,


bttv driver is returning a strange value to the VIDIOC_ENUMSTD call:

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 )

Using kernel 2.6.22-14 in Kubuntu 7.10 (amd64) here.


Best regards,


Cláudio

-------------------------------------------------------

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