On Sunday 12 Aug 2007, Rob Clark wrote:
> This is a follow-up to the discussion about the X driver; I have run up
> against this myself while building a new mythtv box
> (New PVR-350, Slackware 12, kernel 2.6.22.1, ivtv-1.01 compiled from
> source with all the appropriate kernel options per the README).  I
> downloaded the trunk version of the X driver yesterday and tried it with
> "ivtv-fb osd_compat=1."  Cannot use the ivtvdev because of
> "ivtvHWProvbe failed to do IVTVFB_IOCTL_GET_STATE for device /dev/fb0"
> Unfortunately, fbdev is too slow on a Celeron D 2.8.   The MythTV
> documentation led me to believe that this wouldn't be a problem with the
> marvelous PVR-350 because of hardware decoding to TV-Out.

The trunk version no longer contains that error message. Assuming you really 
did compile the trunk, check the files installed into the correct place. On 
my setup (Slackware 8 upgraded to 12), the ivtv X driver gets installed into
'/usr/local/lib/xorg/modules/drivers/', but by default X is only looking in 
'/usr/lib/xorg/modules/drivers/'. You can either move the files or edit the 
module path for X.

> So I have two points of confusion:
>
> 1) When the next version of everything comes out, will this be
> significantly better than fbdev speed-wise?

In what way was fbdev slow?

> 2) Will an upcoming version make the "Use the PVR-350's TV out / MPEG
> decoder" truly usable?

It's more a case of 'usable again'. MythTV should work fine with ivtv 0.10.x
Personally, I no longer use the mpeg decoder, but let MythTV use the Xv 
overlay instead (not available with fbdev).

> 3) Is there a combination of kernel/mythtv/ivtv that I could revert to
> to take advantage of TV-Out today?

If you want to use the mpeg decoder within MythTV, Linux 2.6.21.x & ivtv 
0.10.x should work fine. If you just want to use the Xv overlay, then Linux 
2.6.22 is fine. Either way, the trunk version of the X driver should work 
fine,

-- 
Ian

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

Reply via email to