From: "Zhigang Gong" <zhigang.gong-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: xorg-devel-go0+a7rfsptAfugRpC6u6w@public.gmane.org,
intel-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Glamor update
Date: Fri, 11 Nov 2011 16:42:32 +0800 [thread overview]
Message-ID: <055401cca04d$db738a10$925a9e30$@linux.intel.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1157 bytes --]
Hi folks,
During the last discussion about glamor’s plan in this list, we got a
conclusion that to extract glamor from xorg and
build a separate glamor library to be used by any possible DDX driver. And
Eric suggested I can incrementally
merge glamor into Intel video driver. Now here is the update.
The separate glamor library is at :
git://people.freedesktop.org/~gongzg/glamor,it provides two interfaces:
1. glamor : Rendering library. All the rendering functions are
implemented in this package.
2. glamor-egl : EGL support library. This package provides functions
to create and initialize OpenGL/EGL context.
There are a little bit more details to introduce glamor in the README file.
The Intel video driver to merge glamor is at
git://people.freedesktop.org/~gongzg/xf86-video-intel’s “glamor” branch.
I just started the merging stage. Only finished 3 patches to enable glamor
in UXA code path. Currently, only migrate
fillspans and polyfillrect to glamor. Will continue to migrate the rest
functions.
I will submit the patches to intel-gfx mail list soon.
[-- Attachment #1.2: Type: text/html, Size: 7263 bytes --]
[-- Attachment #2: Type: text/plain, Size: 219 bytes --]
_______________________________________________
xorg-devel-go0+a7rfsptAfugRpC6u6w@public.gmane.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel
next reply other threads:[~2011-11-11 8:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 8:42 Zhigang Gong [this message]
2011-11-11 21:47 ` Glamor update Jamey Sharp
2011-11-14 5:03 ` Zhigang Gong
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='055401cca04d$db738a10$925a9e30$@linux.intel.com' \
--to=zhigang.gong-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=intel-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=xorg-devel-go0+a7rfsptAfugRpC6u6w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.