On Wed, 2003-08-06 at 22:45, Jon Smirl wrote: > > --- Denis Oliver Kropp <[EMAIL PROTECTED]> wrote: > > > When multitasking, how does the context get > > changed? > > > > I don't know how that's handled by others, > > but DirectFBGL applications have to Lock() and > > Unlock() the context. > > Only one context can be locked at the same time (in > > each DirectFB session). > > The Lock() method acquires DirectFB's graphics card > > lock and makes > > the context the current one, like > > glXMakeCurrent(non-null). > > The Unlock() method clears the current context, like > > glXMakeCurrent(null), > > and releases the graphics card lock. > > Does unlock really clear the context? There are loops > all over the drivers doing lock/unlock while waiting > on things to finish. Wouldn't it be better to track > which context is loaded?
The DRI drivers do this, you may be confusing GL and DRM contexts and whatnot here. > > Applications usually lock/unlock the context once > > around initialization and > > once for each complete frame, most probably calling > > IDirectFBSurface::Flip() > > afterwards or doing DirectFB graphics operations on > > the buffer in between. > > So is DRI vunerable to an app seg faulting while it > holds the context lock? No, the DRM cleans up after a process when it dies. -- Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
