On Sat, 2008-02-02 at 14:58 +0100, Sander Sweers wrote: > On vr, 2008-02-01 at 15:42 -0500, Daniel Kristjansson wrote: > > It's already not a good idea to use a kernel > 2.6.17 anyway, since > > VBI is broken in later ivtv drivers for PVR-250 and PVR-350 cards. > > We'll just recommend Linux 2.6.17 or earlier in the MythTV 0.21 > > release notes. When we release 0.21.1 hopefully both problems will be > > resolved in a newer kernel. > > Are you referring to the breakage when capturing at *non native* > pal/ntsc which causes bad video and bad VBI data on cards with a cx25840 > (for example PVR150 and 500)? > > If so then it would be far easier to start capturing at native pal/ntsc > resolution instead of the 480x480 which is currently default (maybe > changed now).
Huh? A hack to work around PVR-150 breakage at reasonable capture resolutions was added to both MythTV and the ivtv drivers a long time ago. I think I was pretty clear if you reread that, it is PVR-250 and PVR-350 cards which no longer capture much VBI since 0.10.6 or so. Hans knows about the problem and I've sent several people over to this list who have volunteered their machines for testing. I really don't understand why there are people complaining about ivtv not working in kernels 2.6.18+. This is the ivtv-devel mailing list, not ivtv-users. Lets just fix the problems and get it over with, instead of bickering about it. It's really a godsend that the ivtv driver is in the kernel at all. For years Hauppauge cards users have needed to compile their own out-of-kernel ivtv drivers. If they need to do that for another year or so, so be it. The MythTV distro's will use the patched modules so most users won't even know there is a problem with the drivers in the kernels. And when the in-kernel driver becomes more usable that will remove one of the many tweaking burdens that MythTV distro makers have to put up with. Besides, the problems are relatively minor. This problem itself has do to a fix for a long standing problem that has affected me as well. And I believe VBI broke because of some changes to the DMA engine that were made to stop driver lockups. Fixes often break other functionality, that is simply the nature of complex systems. -- Daniel _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
