On Sat, Mar 21, 2009 at 4:34 PM, Andy Walls <[email protected]> wrote: > The cx25840 module code has been reorganized, but the reorganization > should not have mucked witht these values at all. > > I can tell you that I have done major rework of the VBI line settings in > the cx18 driver that you may find inseresting. The A/V digitizer in the > CX23418 is *extremely* similar to the stand alone CX25843. > > Anyway, if you look in linux/driver/media/video/cx18/, the files > > cx18-av-core.c and cx18-av-vbi.c > > should look very similar to > > cx25840-core.c and cx25840-vbi.c > > in linux/drivers/media/video/cx25840/ except with updated values for > NTSC and comments that you may find helpful. > > The problem with putting the "right" values in the cx25840 module, is > that the changes will ripple through the VBI handling in the ivtv > module. > > For the cx18 module, changes in cx18-av-*c, for VBI, rippled through > > cx18-driver.h cx18-streams.c and cx18-vbi.c > > in a non-trivial manner. > > I did a lot of research and experimenting to figure out how then encoder > was packing in the raw samples (for both sliced and raw VBI) from the > digitizer. The important thing is a) capturing the right amount of > lines and b) knowing the number of the first line the encoder is sending > you as VBI when you twiddle the line count values in cx25840-*.c > digitizer setup. > > I needed a copy of the VESA VIP 2 standard (which has BT.656 field > diagarms in it) to figure it all out. :P > > Regards, > Andy >
Interesting. It sounds like at the very least it would be worth trying a test install onto a USB thumb drive to see if anything changes in my setup. Thanks, Jim _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
