From: Chris Wilson <chris@chris-wilson.co.uk>
To: zhigang.gong@linux.intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] uxa/glamor: Enable the rest glamor rendering functions.
Date: Tue, 13 Dec 2011 18:44:47 +0000 [thread overview]
Message-ID: <aefc95$2i59vr@orsmga001.jf.intel.com> (raw)
In-Reply-To: <1323786701-29955-1-git-send-email-zhigang.gong@linux.intel.com>
On Tue, 13 Dec 2011 22:31:41 +0800, zhigang.gong@linux.intel.com wrote:
> From: Zhigang Gong <zhigang.gong@linux.intel.com>
>
> This commit enable all the rest glamor rendering functions.
> Tested with latest glamor master branch, can pass rendercheck.
Hmm, it exposes an issue with keeping a bo cache independent of mesa and
trying to feed it our own handles:
Region for name 6 already exists but is not compatible
The w/a for this would be:
diff --git a/src/intel_glamor.c b/src/intel_glamor.c
index 0cf8ed7..2757fd6 100644
--- a/src/intel_glamor.c
+++ b/src/intel_glamor.c
@@ -91,6 +91,7 @@ intel_glamor_create_textured_pixmap(PixmapPtr pixmap)
priv = intel_get_pixmap_private(pixmap);
if (glamor_egl_create_textured_pixmap(pixmap, priv->bo->handle,
priv->stride)) {
+ drm_intel_bo_disable_reuse(priv->bo);
priv->pinned = 1;
return TRUE;
} else
but that gives up all pretense of maintaining a bo cache.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-12-13 19:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 14:31 [PATCH] uxa/glamor: Enable the rest glamor rendering functions zhigang.gong
2011-12-13 18:20 ` Chris Wilson
2011-12-14 3:30 ` Zhigang Gong
2011-12-13 18:44 ` Chris Wilson [this message]
2011-12-14 4:08 ` Zhigang Gong
2011-12-14 11:12 ` Chris Wilson
2011-12-14 11:44 ` Zhigang Gong
2011-12-14 12:08 ` Chris Wilson
2011-12-14 11:54 ` Chris Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='aefc95$2i59vr@orsmga001.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=zhigang.gong@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox