John, I want to make sure I am chasing the right dog. I only get the freeze problem if I am using the framebuffer for tv-out. If I don't use the framebuffer and just play the output to my vga monitor I get no freeze problem.
So my question is can it still be an ivtv problem and not a xdriver problem if it only happens when using frambuffers? I just don't understand the architecture well enough to draw a sharp line in the sand to say which one is broken, ivtv or xdriver. Steve -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of John Harvey Sent: Sunday, November 13, 2005 12:03 PM To: 'Discussion list for development of the IVTV driver' Subject: RE: [ivtv-devel] ivtv framebuffer is broken with PVR350 > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:ivtv-devel- > [EMAIL PROTECTED] On Behalf Of Steve & Laurie Sanders > Sent: 13 November 2005 16:02 > To: Discussion list for development of the IVTV driver > Subject: RE: [ivtv-devel] ivtv framebuffer is broken with PVR350 > > Well, I tried to revert to fbdev as my framebuffer to see if the xdriver > errors could be resolved that way. But alas no joy. When I switch from > ivtvdev to fbdev I get the following errors in Xorg.0.log > > (EE) FBDEV(0): mmap fbmem: Invalid argument > (EE) FBDEV(0): Map vid mem failed > > I don't know enough about the code to narrow the problem down any further > without help. I think there is pretty good evidence for a problem with the > xdriver (ivtvdev_drv.o) in my system configuration based on the errors I > see > in Xorg.0.log when the ivtvdev is used as the Driver in xorg.conf. > > (EE) IVTVDEV_TST(0)Framebuffer id from dev /dev/fb1is 1 > (EE) IVTVDEV_TST(0)open /dev/video48 returned 6 > (EE) IVTVDEV_TST(0)get_fb returned 0 fbid 1 > > It spits out these three errors but seems to work all right after that > with > exception to the recoverable freeze on playback. These aren't actually errors. These were informational items to help me get things working. I will remove them before releasing it properly. I would be fairly confident the problem is not the Xdriver. It is more likely to be ivtv itself or a problem interacting with your hardware. Either are possible. John _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
