[Intel-gfx] [PATCH] manage pixmaps with EXA

Eric Anholt eric at anholt.net
Thu Apr 9 19:04:37 CEST 2009

On Wed, 2009-04-08 at 16:56 -0700, Jesse Barnes wrote:
> I started looking at #20739 and it appears to be a server bug in the
> EXA migration code somewhere.  Rather than digging through that when
> we're likely to remove EXA support soon, I just added support for
> driver managed pixmaps, which fixes also fixes the bug.
> This is a fairly significant change so close to release, but I thought
> I'd post it for comments.
> The patch isn't actually as big as it appears; it mainly moves the UXA
> pixmap create/destroy routines up above the EXA init call so they can
> be used for both cases.


If you have kernel memory management, you should be using UXA.
Non-kernel memory management is the only reason we have EXA around at
all, since we get stuck with non-kernel memory management on the second
server pre-KMS.  This patch would remove that support, so we might as
well just remove EXA entirely in that case.

We should figure out how to reliably determine if we can do kernel
memory management early enough in init to choose acceleration
architecture based on it.  Or figure out how late we can push AA

(It's kind of tricky, last time I was looking at doing that)

Eric Anholt
eric at anholt.net                         eric.anholt at intel.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/intel-gfx/attachments/20090409/e410d1f2/attachment.sig>

More information about the Intel-gfx mailing list