On Mon, Jul 14, 2003 at 01:08:03PM +0200, Denis Oliver Kropp wrote: > DirectFB and DRI drivers are cooperating nearly automatically. The DirectFBGL > core acquires the graphics lock of DirectFB before acquiring the lock of DRI > and pumping the last DRI state to the hardware. This is typically done before > rendering a whole frame. After that both locks are released and the application > most probably flips the surface. The DirectFB driver is told to (re)initialize > the engine when the next graphics lock is done by DirectFB .
BTW there's at least one outstanding problem with DirectFBGL & mga. glScissors() doesn't work as it should because SwapBuffers() is not used and it does something with the cliprects. If I add SwapBuffers to IDirectFBGL and use that instead of IDirectFBSurface::Flip() things start working but of course I can't see anything when rendering to a window :) Oh and btw I have glean ported to DirectFBGL. The patch has been lying on my disk for weeks now. I'll dig it up and post it somewhere... > The fixes to the MGA driver are obsolete after I redid > all embedded-2 changes using the DRI trunk instead > of the XFree trunk. I just posted some more patches for MGA driver to dri-devel. Hopefully they'll find their way to both trees... -- Ville Syrj�l� [EMAIL PROTECTED] http://www.sci.fi/~syrjala/ -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-dev" as subject.
