From: Zhigang Gong <zhigang.gong@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 3/3] glamor: Route fillspans and polyfillrects to glamor.
Date: Fri, 11 Nov 2011 16:31:21 +0800 [thread overview]
Message-ID: <1321000281-5097-3-git-send-email-zhigang.gong@linux.intel.com> (raw)
In-Reply-To: <1321000281-5097-1-git-send-email-zhigang.gong@linux.intel.com>
If GLAMOR is enabled, we route UXA's fillspans and
polyfillrects to glamor by default. And if glamor
fail to accelerate it, UXA continue to handle it.
Signed-off-by: Zhigang Gong <zhigang.gong@linux.intel.com>
---
uxa/uxa-accel.c | 13 ++++++++++++-
1 files changed, 12 insertions(+), 1 deletions(-)
diff --git a/uxa/uxa-accel.c b/uxa/uxa-accel.c
index 516834f..18fa63b 100644
--- a/uxa/uxa-accel.c
+++ b/uxa/uxa-accel.c
@@ -27,7 +27,6 @@
* Michel Dänzer <michel@tungstengraphics.com>
*
*/
-
#ifdef HAVE_DIX_CONFIG_H
#include <dix-config.h>
#endif
@@ -37,6 +36,10 @@
#include "uxa.h"
#include "mipict.h"
+#ifdef GLAMOR
+#include "glamor.h"
+#endif
+
static void
uxa_fill_spans(DrawablePtr pDrawable, GCPtr pGC, int n,
DDXPointPtr ppt, int *pwidth, int fSorted)
@@ -49,6 +52,10 @@ uxa_fill_spans(DrawablePtr pDrawable, GCPtr pGC, int n,
int nbox;
int x1, x2, y;
int off_x, off_y;
+#ifdef GLAMOR
+ if (glamor_fill_spans_nf(pDrawable, pGC, n, ppt, pwidth, fSorted))
+ return;
+#endif
if (uxa_screen->swappedOut || uxa_screen->force_fallback)
goto fallback;
@@ -673,6 +680,10 @@ uxa_poly_fill_rect(DrawablePtr pDrawable,
int n;
RegionPtr pReg = RECTS_TO_REGION(pScreen, nrect, prect, CT_UNSORTED);
+#ifdef GLAMOR
+ if (glamor_poly_fill_rect_nf(pDrawable, pGC, nrect, prect))
+ return;
+#endif
/* Compute intersection of rects and clip region */
REGION_TRANSLATE(pScreen, pReg, pDrawable->x, pDrawable->y);
REGION_INTERSECT(pScreen, pReg, pClip, pReg);
--
1.7.4.4
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2011-11-11 8:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 8:31 [PATCH 1/3] glamor: Initial commit to introduce glamor acceleration Zhigang Gong
2011-11-11 8:31 ` [PATCH 2/3] glamor: turn on glamor Zhigang Gong
2011-11-11 9:11 ` Chris Wilson
2011-11-11 10:52 ` Zhigang Gong
2011-11-11 13:12 ` Chris Wilson
2011-11-14 5:01 ` Zhigang Gong
2011-11-14 9:07 ` Chris Wilson
2011-11-14 12:02 ` Zhigang Gong
2011-11-11 12:58 ` Eugeni Dodonov
2011-11-14 5:05 ` Zhigang Gong
2011-11-11 8:31 ` Zhigang Gong [this message]
2011-11-11 9:07 ` [PATCH 3/3] glamor: Route fillspans and polyfillrects to glamor Chris Wilson
2011-11-11 10:48 ` Zhigang Gong
2011-11-11 13:54 ` Chris Wilson
2011-11-14 3:32 ` Zhigang Gong
2011-11-11 12:56 ` [PATCH 1/3] glamor: Initial commit to introduce glamor acceleration Eugeni Dodonov
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=1321000281-5097-3-git-send-email-zhigang.gong@linux.intel.com \
--to=zhigang.gong@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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