This same issue was raised last year about this time. It seems that there are not many
people out there dealing with VBI data and V4L2, so any fresh thoughts are appreciated.
Regarding multiple VBI data types, how about allowing a driver to advertise different
devices. For example,
/dev/atvef
/dev/cc
/dev/tt
/dev/nabts
/dev/vbi (raw)
/dev/...
A read from either of these devices would return a requested amount of data from
the queued data of the corresponding data type (and from the corresponding VBI
line(s)) in the appropriate format.
Thoughts?
-- Peter
sojan_james@h
otmail.com To: video4linux-list@xxxxxxxxxx@Internet
cc: (bcc: Peter Lohmann/Americas/NSC)
08/13/01 Subject: VBI interface
04:44 AM
Hi All,
A new member here. The V4L2 VBI interface assumes that the VBI data
which is captured will be raw samples. The SAA7114 decoder can slice several
formats simultaneously. It would be useful to be able to open different
instances of the driver and program each instance to return different
formats on different lines. I feel that the current interface is a little
too simple for this kind of capture.
Since each capture will have data from diffent lines, I feel we could
prepend each line of data with a couple of bytes indicating the data type,
validity and the line number. Has anyone worked on this? Comments?
Thanks and regards
Sojan.
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
_______________________________________________
Video4linux-list mailing list
Video4linux-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/video4linux-list
