Billy Biggs <vektor@xxxxxxxxxxxx> writes: > > > Is there a simple programmatic way to retreive data from /dev/vbi > > > regardless of what is happening on /dev/video? > > > > It just works ... > > Are you sure about this? Yes. Running a TV application (xawtv, kwintv, ...) and a vbi application (nxtvepg, alevt) at the same time works just fine for me, also with bttv 0.7.x. Using /dev/vbi alone works too. There are a few minor glitches which are not easily fixable within 0.7.x and which are gone in 0.9.x. But it isn't that bad that it isn't working at all. There where some initialization order issues some time ago: The PLL wasn't initialized correctly with just /dev/vbi, so you had to open /dev/video once to get /dev/vbi working. > Using the bttv driver in 2.4.19 in tvtime I get the next video frame > then read() from /dev/vbi to get the associated VBI frame (yes I know > this will be nice and sync'ed in V4L2 but one must support one's users > :) and anyway, if I do the read() at the wrong place it ends up > blocking forever. Is this a bug? Maybe. The 0.7.x code is somewhat confusing, have to check what is going on there. The fifo for vbi data is very small, one frame only. Maybe there is a bug in overrun handling (i.e. app not reading vbi data fast enougth to make room for the new vbi data). Gerd -- Weil die späten Diskussionen nicht mal mehr den Rotwein lohnen. -- Wacholder in "Melanie"
