On Fri, 2009-09-11 at 00:00 -0400, Devin Heitmueller wrote: > Hello Mauro, > > Please PULL from http://kernellabs.com/hg/~dheitmueller/em28xx-vbi3 > for the following > > em28xx: better describe vinctrl registers > em28xx: make video isoc stream work when VBI is enabled > em28xx: add raw VBI support for NTSC + /* FIXME: hard-coded for NTSC support */ + format->fmt.vbi.sampling_rate = 6750000 * 4 / 2; /* FIXME: ??? */ The BT.656 Pixel clock for both 60 Hz and 50 Hz systems is 13.5 Mpixels/sec. Unless you switch to PAL or NTSC square pixel timing for some reason, I would expect this particular number to stay the same for both PAL and NTSC. A pixel in BT.656 consists of 1 Y sample and 1 U or V sample. So, in the VBI active line regions, I would have expected 2 * 13.5 Msamples/sec for VBI data. I don't know if any app in userland actually pays attention to this number though.... Regards, Andy > em28xx: fix mmap_mapper with vbi > em28xx: restructure fh/dev locking to handle both video and vbi > em28xx: remove unreferenced variable > em28xx: do not create /dev/vbiX device if VBI not supported > em28xx: only advertise VBI capability if supported > em28xx: implement g_std v4l call > em28xx: remove unneeded code that set VINCTRL register > em28xx: fix unused variable warning > > Note: the support currently only works for NTSC. I will be getting > PAL support working in the next couple of weeks as I get an > environment setup for testing. > > Special thanks go out to EyeMagnet Limited for sponsoring this work. > > Thanks, > > Devin > -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
