On Fri, 4 Sep 2009 13:25:43 -0700 Ian Romanick <i...@freedesktop.org> wrote:
> > +can wait for a specific frame count or divisor/remainder before > > continuing +its processing. With the DRI2WaitSBC request, clients > > can block until a given +swap count is reached (as incremented by > > DRI2SwapBuffers). Finally, using +DRI2SwapBuffers, clients will be > > throttled to a frame interval specified by +an earlier swap > > interval call (currently only available through GLX). > > + > > glXSwapBuffersMscOML doesn't throttle the application. It sets the > rate that new frames will be displayed, but it doesn't necessarily > block the application. In the absence of other extensions that we've > talked about, our implementation will. However, the implementation > will do this by possibly blocking on the first draw call after the > glXSwapBuffersMscOML. Right? Right, it won't block immediately; and in a good implementation shouldn't block until the latest possible moment, if at all. I'll fix up the text (I should have said "limit the framerate" or something) -- Jesse Barnes, Intel Open Source Technology Center ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
