On Tue, Jan 04, 2011 at 08:16:18AM -0800, ext Keith Packard wrote: > On Tue, 4 Jan 2011 17:55:53 +0200, [email protected] wrote: > > From: Ville Syrjälä <[email protected]> > > > > Use CopyArea in compWindowUpdateAutomatic if the window and parent > > depths match. It appears EXA Composite op can already switch to > > a straight copy when the conditions are right, but non-EXA drivers > > would fall back to software rendering. > > XAA also handles this case, so I don't think this is necessary.
Ah, so it does. I just assumed it didn't, based on the fact that compNewPixmap already had the CopyArea path in addition to the CompositePicture path. Is there another reason why compNewPixmap should be treated differently, or could we just eliminate the CopyArea path there? -- Ville Syrjälä _______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
