On 12/19/06, Hans Verkuil <[EMAIL PROTECTED]> wrote: > Hi all, > > I think it is getting time for people to start testing the ivtv trunk > from subversion. I've been running it for quite some time now and it > looks to be pretty solid. Ian Armstrong has added lots of goodies in > the framebuffer department (be sure to read the README notes!), so that > can use some testing as well. > > Regarding DMA problems: I think that these are solved for the PVR500. I > haven't yet done a REALLY long duration test but from the shorter tests > I did it is looking good. The DMA errors still occur for other cards: > it is a hardware issue with the cx23415/6 and there probably isn't > anything I can do about it. Just don't use CPU freq. changers and > sometimes using a RAID array also messes up the DMA. > > The reason that it works for the PVR500 is that the PVR500 has a PCI > bridge that seems to isolate the cx23416 chips from the main PCI bus. > It still could fail on the 0.9 drivers due to the way DMA was handled > in the driver. With the new trunk driver all DMA is now done in the > interrupt handler. > > Note: ivtv trunk requires the 2.6.19 kernel. It is probably very easy to > backport it to 2.6.18, it may even compile out of the box. I just > haven't tested it myself. When this driver version is released I'll > definitely backport it to 2.6.18. > > The trunk driver can be obtained here: > > http://ivtvdriver.org/viewcvs/ivtv/trunk.tar.gz?view=tar
Hans, I've been running the trunk on Linux 2.6.19-gentoo for a couple of days and it seems to be running fine. I added enc_mpg_buffers=8 to the module options because of the occasional "All encoder MPEG stream buffers are full. Dropping data." and I hope this will solve it. This error appears to occur when a recording is running and a 2nd one starts so it might be MythTV writing to the database. The trunk gives me these occasional errors: ivtv3: Invalid API call: cmd = 0xb1, args = 1 ivtv3: Invalid API call: cmd = 0xb1, args = 1 ivtv3 warning: ENC DMA ERROR b ivtv3 warning: encoder MPEG: offset 0 -> 128 ivtv3 warning: encoder MPEG: offset 128 -> 0 They appear harmless, i.e. I don't notice anything in the recordings. I've also re-enabled the CPU-frequency scalers and I haven't noticed the problems that occurred in the older version. Great job :-) N. _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
