On vr, 2007-08-10 at 20:27 -0400, Sam Varshavchik wrote: > I don't recall your initial post, regarding your actual intentions with > PVR350's TV-Out. You did not indicate if you had it working before, in which > case you already know everything below. But I guess you're trying to get > this to work for the first time. > > MythTV's support for sending video playback through PVR350's TV-Out is, for > all intents and purposes has been abandoned and obsoleted.
At the moment only for kernel 2.6.22 as this changed the api. Quoting Hans below about the mythtv support for kernel <2.6.22. I am not sure if he found someone willing to write mythtv support for 2.6.22 and up. On vr, 2007-02-02 at 00:21 +0100, Hans Verkuil wrote: > 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. ----- And also: On vr, 2007-02-02 at 00:21 +0100, Hans Verkuil wrote: > 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. ---- > The only use for > PVR350's TV-Out involves running X on PVR350's framebuffer, essentially > running your desktop on the TV display, instead of your VGA monitor. Then, > you run MythTV normally, just like always, but since the video is now going > to the TV-Out, that's where you see the video. I've been doing this for > years, and it works fine, but this means that, pretty much, you have to > dedicate your machine to MythTV's duties. Only rcently the official xdriver code on ivtvdriver.org was updated with autotooled building, Xorg 7.1 support and lots of fixes. > Configuring X to run on ivtv_fb is tedious. First of all, you need to > reconfigure your grub configuration to boot using the VESA framebuffer for > the system console. Some bug in the Linux kernel, whose nature is not clear > to me, results in a completely unusable console if you try to start the > ivtv_fb framebuffer with the default system console, unless you boot in VESA > mode. I am sure Hans would appreciate a bug report report for the issues you see with the ivtv-fb module. Most of the instruction in this email are already documented on the wiki [1] but it could use some love from an experienced user. Care updating it? Greets Sander [1] http://ivtvdriver.org/index.php/Howto:XDriver _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
