Linux OpenGL ABI discussion

2005-09-28 Thread Andy Ritger
I apologize for the cross posting, but I'd like to call attention to the discussion on updating the Linux OpenGL ABI that Jon Leech initiated on the lsb-desktop email alias: http://base4.freestandards.org/pipermail/lsb-desktop/2005-September/000146.html Some of the topics raised include:

Re: [Xorg] Re: Damage/Composite + direct rendering clients

2004-05-24 Thread Andy Ritger
On Mon, 24 May 2004, Ian Romanick wrote: Andy Ritger wrote: The other concern (how to make sure direct rendering has completed by the time the drawable is used as a source in a composite operation) conceptually would be solved as you describe, but I expect the implementation would

Re: [Xorg] Damage/Composite + direct rendering clients

2004-05-18 Thread Andy Ritger
On Mon, 17 May 2004, Keith Packard wrote: Around 15 o'clock on May 17, Andy Ritger wrote: [snip] The tricky part here is that the damage event shouldn't be sent to Damage clients until the hardware has completed the damage, but that is the vendor's problem... I'm just trying to make

Re: [Xorg] Damage/Composite + direct rendering clients

2004-05-18 Thread Andy Ritger
On Tue, 18 May 2004, Soeren Sandmann wrote: Keith Packard [EMAIL PROTECTED] writes: As long as the compositing manager holds the server grabbed (which presumably locks out direct clients as well) while it updates the screen, there shouldn't be any tearing. No need to drain the event

Re: [Xorg] Re: Damage/Composite + direct rendering clients

2004-05-18 Thread Andy Ritger
On Mon, 17 May 2004, Jim Gettys wrote: On Mon, 2004-05-17 at 16:03, Andy Ritger wrote: 2) some damage occurs, composite manager sends composite request, additional rendering is performed, part of which the composite operation picks up, but the rest

Re: [Xorg] Damage/Composite + direct rendering clients

2004-05-18 Thread Andy Ritger
On Tue, 18 May 2004, Keith Packard wrote: Around 1 o'clock on May 18, Andy Ritger wrote: I'm debating whether it is better for the X server to not even know of the damage until it has completed in hardware, or if it is better to tell the X server as soon as the rendering has kicked

Re: [Xorg] Re: Damage/Composite + direct rendering clients

2004-05-17 Thread Andy Ritger
On Mon, 17 May 2004, Alex Deucher wrote: --- Andy Ritger [EMAIL PROTECTED] wrote: [snip] - A Video Overlay Xv Adaptor is obviously fundamentally incompatible with Damage/Composite. Should X drivers no longer advertise Video Overlay Xv adaptors if they are running in an X

Damage/Composite + direct rendering clients

2004-05-17 Thread Andy Ritger
I've given some thought to how best to integrate direct rendering clients with Damage/Composite. For the below discussion, I'll focus on GLX as the direct rendering client but the same concepts should apply to XvMC or any other direct rendering client. For anyone not already familiar with the

Re: [Xorg] Damage/Composite + direct rendering clients

2004-05-17 Thread Andy Ritger
On Mon, 17 May 2004, Keith Packard wrote: Around 11 o'clock on May 17, Andy Ritger wrote: How should a direct rendering client interact with Damage/Composite? There seem to be two pieces to this: damage notification, and synchronization. Thanks for getting this topic started

Re: [Xorg] Re: Damage/Composite + direct rendering clients

2004-05-17 Thread Andy Ritger
On Mon, 17 May 2004, Jim Gettys wrote: On Mon, 2004-05-17 at 11:41, Andy Ritger wrote: I've given some thought to how best to integrate direct rendering clients with Damage/Composite. For the below discussion, I'll focus on GLX as the direct rendering client but the same concepts should