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:20:01 +0000 [thread overview]
Message-ID: <aefc95$2i50f7@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.
>
> One thing need to be pointed out is the picture's handling.
> Pictures support many different color formats, but glamor's
> texture only support a few color formats. And the most common
> scenario is that we create a pixmap with a color depth and
> then attach it to a picture which has a specific color format
> with the same color depth. But there is no way to change a
> texture's internal format after the texture was allocated.
> If you do that, the OpenGL will allocate a new texture. And
> then the glamor side and UXA side will be inconsitence. So
> for all the picture related operations, we can't fallback to
> UXA path directly, even it is rather a strainth forward
> operation. So for the get_image, Addtraps.., we have to add
> wrappers function for them to jump into glamor firstly.
Can we create multiple textures referencing the same bo but with
different formats? Or are we going to run afoul of the coherency model
with GL?
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-12-13 18:34 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 [this message]
2011-12-14 3:30 ` Zhigang Gong
2011-12-13 18:44 ` Chris Wilson
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$2i50f7@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 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.