Actually the best thing to do would be looking at diffs between the key files, ivtv-irq.c, ivtv-kthreads.c, ivtv-osd.c. Actually not a lot has changed, really the main differences are consolidating the code which was reused in multiple places to single functions reused instead. The differences other than that are a few decoder ordering changes (easy to see in a diff) and listening for interrupts before saying the DMA is done for decoding. If the interrupts are a problem area it may be from Myth using an ioctl to stop/start decoding, instead of open/close interface calls, it's a completely different and free-floating way of controlling the decoder instead of simple write methods used by cat/dd. So in theory it could say 'stop decoder' then 'start decoder' and not wait for that interrupt which could trip up the decoder and cause it to malfunction. This interrupt saves VIA systems and other DMA sensitive situations that have come up to be alot more stable on system crashes, may 'stop' the decoder in situations which before hung the system or did other worse outcomes than just stoping your decoding session. When the decoding session stops, it sounds like Myth is basically sitting there and doesn't restart it, but stop/start of the front end fixes it. So that tells me, even though in 0.2 it may not happen 'as often', but it still happens, that there could be more agressive client code to restart the decoder when it dies. I also want to know if .16 does this for you, mine works flawless, lots of ff/rw, have to make sure you can repeat it there too, the ff/rw code changed totally since then, so have to discern that just to see, even though 0.2 may do it alot less, it still does it, so have to look at that to help figure out what is going wrong in the driver. I actually would love to have logs of Myth and what it is saying, where is it hanging, what is it doing, so I know where in the driver to look for a bug, oddly there has been 0 Myth logging of this problem (there are debug modes, have to be doing something in the application, want to see a timeline of the activity of code traversal before this happens (is it stuck in a loop, and from *what* ioctl or function of using the driver is it stuck at???). So either looking at diffs, trying to reverse one thing at a time, or debugging the application and driver would help out everyone greatly, someone could easily do either who have more time and experience with debugging things in Myth.
Thanks, Chris On Fri, Apr 22, 2005 at 02:11:11AM +0000, Louie Ilievski wrote: > On Thursday 21 April 2005 06:46 am, John Harvey wrote: > > Try changing the code in videoout_ivtv.cpp to do PREP_FRAME instead of > > BLT_FILL in ClearOSD.c. > > Or alternatively apply my patch sent to myth-dev mailing list about 4 weeks > > ago that was to fix this and other problems. > > > Finally re-compiled MythTV CVS tonight with that patch. The EPG problem is > solved as you stated in that post a while back, but I still get very frequent > freezes on playback, and the timestamp problem still persists. So, one small > step forward, I suppose. Also, now when I restart X to get the frontend > back, the screen stays black (or I guess whatever frame it froze on, it > happened to be black frames cause I was doing commercial skips when it > froze), and the only way to get anything to come up is just to assume myth is > back and loaded, and hit enter to go to live tv and clear things up again. > > Also, this time, when trying to pause/unpause it, like before it sometimes > works. But when it doesn't, I get a message in the frontend log stating it > waited too long for the decoder to pause. In dmesg I get: > > ivtv: i2c client addr: 0x21 not found! > ivtv: i2c client addr: 0x21 not found! > ivtv: i2c client addr: 0x21 not found! > ivtv: i2c client addr: 0x21 not found! > ivtv: i2c client addr: 0x21 not found! > ivtv: i2c client addr: 0x21 not found! > ivtv: i2c client addr: 0x21 not found! > ivtv: i2c client addr: 0x21 not found! > ivtv: i2c client addr: 0x40 not found! > ivtv: i2c client addr: 0x40 not found! > ivtv: i2c client addr: 0x21 not found! > ivtv: i2c client addr: 0x40 not found! > ivtv: i2c client addr: 0x21 not found! > ivtv: i2c client addr: 0x40 not found! > ivtv: i2c client addr: 0x40 not found! > > That may have been from more than one occurance from the freeze since I > tested > it a couple of times. > > Chris, > > Is there an easy way for me to revert to the pre-DMA code, but get the > featues > of the new cx25840 stuff as well? Can I just use the older driver and copy > over the cx25840 files? If not, how can I go about this? > > Thanks, > > ~Lou -- --- Chris Kennedy / [EMAIL PROTECTED] Engineer KMOS-TV/KTBG-FM Broadcasting Services Department Central Missouri State University ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
