-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jerome Glisse wrote: | 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
Which will fail because A has it mapped. Or do you mean some drawing operation not involving the mapped object? | A unmap | A submit draw cmd which change obj | B want to draw at mapped obj Which will fail because B has it mapped. | 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. The result is undefined. I think part of the confusion here, and this is my fault, is the difference between the data contents of the object and the object itself. There is no guarantees about the data contents (i.e., the texels of a texture) of an object. Bind is the synchronization point for things that affect the object itself (i.e., using glTexImage2D to change the size of a texture). We're going to update the GLX spec after OpenGL 3.0 ships, and we're going to make a lot of this more explicit. Right now it's mostly implied by language spread through section 2.3, 2.4, 2.5, and 2.7. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFINGiQX1gOwKyEAw8RAlBEAKCbmp3E3n82EY3OjPwhYQB+lTkaggCbB0Lb G98ypfRM76k2H8KJNCBf5QM= =WIwW -----END PGP SIGNATURE----- ------------------------------------------------------------------------- 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
