2009/3/25 Michel Dänzer <[email protected]>: > On Tue, 2009-03-24 at 16:31 -0700, Eric Anholt wrote: >> We can work around the cost by suppressing the getbuffers for internal >> glViewport calls (it was the plan before he came up with the clever >> hack). > > I'm not sure that's necessary; the patch I included limits the number of > GetBuffers round-trips to one per frame regardless of where they were > triggered from. Do you or anyone see any problem with this? > > OTOH I think the driver wouldn't need to update the buffers from > MakeCurrent.
Do this from the flushExtension instead. Keep the cached flag inside the DRI driver and clear it when the flush entry point is called. That's exactly the semantics you want, and one of the things the flush extension was added for. cheers, Kristian ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Mesa3d-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
