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.
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? 2) Will an upcoming version make the "Use the PVR-350's TV out / MPEG decoder" truly usable? 3) Is there a combination of kernel/mythtv/ivtv that I could revert to to take advantage of TV-Out today? Wow, that's three. I really am confused. Thanks to the ivtv developers for their work. This stuff is mind-boggling and makes me appreciate what went into creating the TiVo! --Rob Clark _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
