On Wed, Nov 02, 2005 at 06:38:34PM +0000, Mark Adams wrote: > On 01/11/05, Ville Syrjälä <[EMAIL PROTECTED]> wrote: > > > And here's version 3 of the triple buffering/field parity ioctl thing. > > I've just had a bash at implementing something similar for the > unichrome overlay layer, with some success. > > The same structure is appropriate in that case too so it would be nice > to give the ioctl a more generic name (FBIO_FLIPONVSYNC?) and an > number in the 'F' range (0x21?).
Feel free to clean it up. I was just hacking around to see if the results were worth moving the flipping completely into the kernel. Clearly it does pay off so the interface should be cleaned up and extended to handle waiting (with or without actually flipping). > What's causing me trouble at the moment is the fact that I've only got > a VBLANK interrupt to work with and the VBLANK-VSYNC interval is too > short to guarantee I can get the new buffer set up in time. When the > machine is heavily loaded, it can miss and that gives a repeated > field. How does the hardware work exactly? Can you write the registers at any time but they actually take effect at vsync time? -- Ville Syrjälä [EMAIL PROTECTED] http://www.sci.fi/~syrjala/ _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
