On Mon, 19 May 2008 12:04:16 -0700 Ian Romanick <[EMAIL PROTECTED]> wrote:
> > The GLX spec says, basically, that the results of changes to a shared > object in context A are guaranteed to be visible to context B when > context B binds the object. It leaves a lot of slack for changes to > show up earlier. This is part of the reason that app developers want > NV_fence-like functionality. I quickly browsed glx spec and failed to spot where this topic appear. And what does B binds mean in this context, i am thinking to this use: A & B share obj A map B map A do some drawing A unmap A submit draw cmd which change obj B want to draw at mapped obj Here does B should the old content of obj before A modified it or should it map to the actual object (even if there is a drawing going on) Note that i explicitly didn't include anysynchronization btw A & B where i believe this 2 applications should sync together. Cheers, Jerome Glisse ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
