On Fri, 2 Feb 2007 00:21:57 +0100
Hans Verkuil <[EMAIL PROTECTED]> wrote:

> Hi all,
> 
> Recently I've seen several comments that PVR350 support would not work 
> or would be removed from MythTV. While it is true that there is no 
> current maintainer for the PVR350 code in MythTV (AFAIK), that doesn't 
> mean that it doesn't work. The ivtv API is still unchanged and as long 
> as the code remains in MythTV it should work just fine.

Well, working is relative.  It's quite buggy at times.  I spent weeks
working on patches with some maintainers, but they unfortunately didn't
have cards handy to test anything at their end.

0.19 had several bugs in the on screen menu and PIP, that could cause
crashes or outright lockups.  Menus could cause lockups.  I saw
nothing in 0.20 release notes to indicate that there had been other
changes to fix such things.  

FF, REW and other live tv controls had issues, were fixed, but remained
buggy at times.  Realistically, the code is broken, but it will work if
you only do specific things, and never move outside of a specific
framework.

I can understand any maintainer's point of view.  The IVTV X driver
isn't really that much of a burn on CPU cycles, compared to the
framebuffer driver.  Considering the sad state of the IVTV framebuffer
code in Myth right now, it would probably make everyone's life easier if
it was just removed.

Of course, that doesn't mean it _will_ be removed. :P


> 
> The support of the ivtv Xdriver is more problematic since the official 
> maintainer of that code (John Harvey) is very busy with other things 
> and hasn't had the opportunity to update this package to newer X11 
> versions.
> 
> Hopefully he will have more time to do this in the near future. If not, 
> then I'll try to find someone else to do the job or I'll do it myself.
> 
> At the moment I'm working hard to get a new ivtv release finished: this 
> release is substantially redesigned/cleaned up and should be much more 
> stable. At the same time I'm also working on moving the ivtv-specific 
> ioctl calls (i.e. the driver API) to new well-designed ioctls that will 
> be included in the linux V4L2 specification. When that is finished I 
> will ensure that the MythTV code is updated to the new (standardized) 
> API and this will include the PVR350 code.
> 
> Hopefully this clarifies the current situation.
> 
> Should the PVR350 support in MythTV break for whatever reason, then 
> please post a report to [EMAIL PROTECTED] I'll try my best to 
> fix it. 
> 

_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

Reply via email to