Nevermind! Re: [mythtv] Experimental pvr 350 output patch

[Chris Delis]

Nevermind!!!!!  I'm a bonehead!!!

Let me guess... it's:


ivtv-031125A

:-)

Sorry to bother you.


On Mon, Dec 15, 2003 at 08:28:39PM -0600, Chris Delis wrote:
> Hi David,
> 
> What version of ivtv are you patching against?  I tried to patch
> against the latest cvs and it's a no-go... ivtv.h failed and
> ivtv-driver.c failed 4 out of 7 hunks.
> 
> Thanks,
> Chris
> 
> On Mon, Dec 15, 2003 at 04:13:13PM -0600, David Engel wrote:
> > FYI, if you have not tried this patch yet, now might be a good
> > time. All known issues have been addressed and the improved
> > functionality is, IMHO, well worth the effort.
> > 
> > On Tue, Dec 09, 2003 at 10:45:45PM -0600, David Engel wrote:
> > > Another day, another version.  The major changes in this version are
> > > as follows.
> > 
> > After many trials and tribulations with the ivtv driver and trying to
> > understand the idiosyncracies of the itvc15 decoder with very little
> > documentation, here is the latest version of my pvr350 patch.  The
> > major changes from the previous version (as best I remember) are as
> > follows.
> > 
> > Moved some funtionality from the video thread to the decoder thread to
> > avoid race conditions while pausing and unpausing.  The video thread
> > now exclusively controls the OSD aspects of the pvr350 and the decoder
> > thread exclusively controls the decoding aspects.
> > 
> > Finished seeking to exact frames with video update.  It's kind of
> > klugy because I have to single step the decoder to the desired frame.
> > As a result, exact seeks other than one frame forward will look a
> > little funny, but at least it works.  Since I still have concerns
> > about the flakiness of the decoder, debug output is still enabled for
> > this code.  As far as I can tell, the only way to improve on this way
> > of doing exact seeks is to do a more complete parsing of the mpeg2
> > stream and only feeding the decoder exactly what is needed.
> > 
> > Some driver issues could not be worked around from user space, so the
> > pvr350 patch now requires an ivtv driver patch.  The ivtv patch is
> > also attached.  It fixes output polling and adds support for
> > non-blocking output flushing queued data.  Once I get some feedback
> > from others on how well this works, I will address the issues with the
> > ivtv developers.
> > 
> > Again, if you have a pvr350 and haven't tried this yet, please
> > consider doing so.  It seems to work pretty well for me.
> > 
> > David
> > -- 
> > David Engel
> > dlengel at attbi.com
> > 
> 
> 
> 
> > _______________________________________________
> > mythtv-dev mailing list
> > mythtv-dev at mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>