Re: Clip Lists

Keith Packard <[EMAIL PROTECTED]> writes: > On Wed, 2007-11-28 at 06:19 +0100, Soeren Sandmann wrote: > > > - When a client wishes to copy something to the frontbuffer (for > > whatever reason - glXSwapBuffers(), glCopyPixels(), etc), it uses > > plain old XCopyArea() with the generated pixma

Re: Clip Lists

Stephane Marchesin wrote: > > > On 11/28/07, *Keith Whitwell* <[EMAIL PROTECTED] > > wrote: > > Stephane Marchesin wrote: > > > > > > On 28 Nov 2007 06:19:39 +0100, *Soeren Sandmann* > <[EMAIL PROTECTED] > > mailto

Re: Clip Lists

On 11/28/07, Keith Whitwell <[EMAIL PROTECTED]> wrote: > > Stephane Marchesin wrote: > > > > > > On 28 Nov 2007 06:19:39 +0100, *Soeren Sandmann* <[EMAIL PROTECTED] > > > wrote: > > > > "Stephane Marchesin" <[EMAIL PROTECTED] > > > writes:

Re: Clip Lists

Stephane Marchesin wrote: > > > On 28 Nov 2007 06:19:39 +0100, *Soeren Sandmann* <[EMAIL PROTECTED] > > wrote: > > "Stephane Marchesin" <[EMAIL PROTECTED] > > writes: > > > I fail to see how this works with a lockless design. How

Re: Clip Lists

On 28 Nov 2007 06:19:39 +0100, Soeren Sandmann <[EMAIL PROTECTED]> wrote: > > "Stephane Marchesin" <[EMAIL PROTECTED]> writes: > > > I fail to see how this works with a lockless design. How do you ensure > the X > > server doesn't change cliprects between the time it has written those in > the > >

Re: Clip Lists

On Wed, 2007-11-28 at 06:19 +0100, Soeren Sandmann wrote: > - When a client wishes to copy something to the frontbuffer (for > whatever reason - glXSwapBuffers(), glCopyPixels(), etc), it uses > plain old XCopyArea() with the generated pixmap. The X server is > then responsible for any clip

Clip Lists

"Stephane Marchesin" <[EMAIL PROTECTED]> writes: > I fail to see how this works with a lockless design. How do you ensure the X > server doesn't change cliprects between the time it has written those in the > shared ring buffer and the time the DRI client picks them up and has the > command fired