Re: EXA and migration [was: shrink xrender featureset]

2009-01-07 Thread Michel Dänzer
On Tue, 2009-01-06 at 22:08 +0100, Clemens Eisserer wrote: Hi Michael, Ahem. ;) I can definitely see how diagonal lines would cause migration ping-pong, but for gradients without blending, as of xserver 1.6 they should just get rendered by the CPU to the system memory copy without any

Re: EXA and migration [was: shrink xrender featureset]

2008-11-26 Thread Michel Dänzer
On Wed, 2008-11-26 at 06:48 +1000, Dave Airlie wrote: Yeah I'm with this, EXA really needs optimisations that know you have composite, and just to render the stuff with the CPU and composite it on. Generally it does stupid things like fill on the GPU, then render with CPU then composite.

Re: EXA and migration [was: shrink xrender featureset]

2008-11-26 Thread Michel Dänzer
On Tue, 2008-11-25 at 20:38 +0100, Clemens Eisserer wrote: That's not 'strong vocabulary' but simply baseless flamebait. Would it make sence to implement some fallback-optimizations like: - Copy pictures without drawables (gradients) to a temporary surface, if the driver supports

Re: EXA and migration [was: shrink xrender featureset]

2008-11-26 Thread Stephane Marchesin
On Wed, Nov 26, 2008 at 10:09, Michel Dänzer [EMAIL PROTECTED] wrote: On Wed, 2008-11-26 at 06:48 +1000, Dave Airlie wrote: Yeah I'm with this, EXA really needs optimisations that know you have composite, and just to render the stuff with the CPU and composite it on. Generally it does

Re: EXA and migration [was: shrink xrender featureset]

2008-11-25 Thread Clemens Eisserer
That's not 'strong vocabulary' but simply baseless flamebait. Would it make sence to implement some fallback-optimizations like: - Copy pictures without drawables (gradients) to a temporary surface, if the driver supports composition? - Support solid write-only operations (X11 core drawing) for