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: Refine CloseScreen and InitScreen process.
Date: Wed, 08 Feb 2012 09:12:13 +0000 [thread overview]
Message-ID: <e39f63$3knqn9@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <1328096848-20599-1-git-send-email-zhigang.gong@linux.intel.com>
On Wed, 1 Feb 2012 19:47:28 +0800, zhigang.gong@linux.intel.com wrote:
> From: Zhigang Gong <zhigang.gong@linux.intel.com>
>
> The previous version calls glamor_egl_close_screen and
> glamor_egl_free_screen manually which is not align with
> standard process. Now glamor change the way to follow
> standard method:
>
> glamor layer and glamor egl layer both have their internal
> CloseScreens. The correct sequence is after the I830CloseScreen
> is registered, then register glamor_egl_close_screen and
> the last one is glamor_close_screen. So we move out the
> intel_glamor_init from the intel_uxa_init to I830ScreenInit
> and just after the registration of I830CloseScreen.
>
> As the glamor interfaces changed, we need to check the
> glamor version when load the glamor egl module to make
> sure we are loading the right glamor module. If
> failed, it will switch back to UXA path.
>
> Signed-off-by: Zhigang Gong <zhigang.gong@linux.intel.com>
I added the note about the glamor commit to this and the following patch
and pushed. Thanks,
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
prev parent reply other threads:[~2012-02-08 9:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 11:47 [PATCH] uxa/glamor: Refine CloseScreen and InitScreen process zhigang.gong
2012-02-02 9:44 ` Zhigang Gong
2012-02-08 6:14 ` Zhigang Gong
2012-02-08 9:12 ` Chris Wilson [this message]
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='e39f63$3knqn9@fmsmga002.fm.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