Hello Johannes,
No. "xawtv" comes with it's own set of videodev.h, videodev2.h (old - pre-2.5.x-version) and videodev2.h (2.5.x version) header files and has modules for all three apis out there. So it should work.My xawtv is a binary package from Debian unstable. Must I recompile with the new videodev.h for grabdisplay to work?
I can confirm your problem with xawtv-3.81, I'll have a look at it tomorrow.
Yes, heavy i2c access can cause high system load, that's true.One other thing I noticed: The new I2C driver causes a higher system load, most visible when you pull out the SAT cable and let the kdvb-fe thread do its zig-zag scanning work. In theory the approach with schedule() should perform better than the old mdelay() stuff, but it seems it doesn't. Maybe not enough to worry about, but maybe we could use one of the saa's register sequencers for I2C timing?
In my current design, RPS0 is used for video capture, RPS1 is used for vbi capture.
If you can tell me for sure, that you never ever want to capture vbi (is it re-inserted at all?) with a dvb card, then I can add a "use RPS1 for DVB I2C access" mode.
Regards, Johannes
CU Michael. -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
