On Thu, 2005-10-27 at 17:40 +0100, Mark Adams wrote: > > Have there been any changes to your viafb patch? I'll try to give your > > CVS version a go to see if it does anything to my A-V sync / speed > > problem. > > Please do. > > The version of viafb I'm using has a few improvements on the one > referred to at the beginning of this thread but nothing too major: the > only real issue is that you'll very occasionally find you get the > opposite field parity due to a race condition.
Feel free to send me any updated patches to viafb, especially if it fixes a field parity problem! > I can't remember whether you're a TV-out user or not but the unichrome > code now in CVS will not do frame synchronisation unless you ask it to > by enabling the DLOP_FIELD_PARITY option. If the code you're using > relies on it just happening automatically, you'll need a slight > modification. I am using S-video out so field parity is important to me. This is with vdr and softdevice. I'm pretty sure it doesn't make proper use of the field sync stuff except for Matrox cards. How do I enable DLOP_FIELD_PARITY? I presume that has to be somewhere in the DirectFB initialisation bits of the code. What flags do I want for the flip calls? Cheers, Laz _______________________________________________ directfb-users mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
