Hello all,
let's assume that we have a fully v4l2-compliant driver, ie. it handles
all opens (video,vbi,whatever) via /dev/video0. This means that you
always have some sort of type informations for the buffer the driver is
actually processing. For streaming video or vbi capture everything is fine.
But how does the read() call work now?
If the user application has set up both video and vbi formats, what does
a read() call return? Video or vbi data?
In former times, the driver had some sort of "I-am-a-vbi-open"
informations. Nowadays, bttv/saa7134 accept opens of /dev/vbi0 and
remember that it's a vbi open in the read() call.
But how about legacy free v4l2 drivers?
CU
Michael.
