public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Zhigang Gong" <zhigang.gong@linux.intel.com>
To: 'Jamey Sharp' <jamey@minilop.net>
Cc: intel-gfx@lists.freedesktop.org, xorg-devel@lists.x.org
Subject: Re: Glamor update
Date: Mon, 14 Nov 2011 13:03:40 +0800	[thread overview]
Message-ID: <065501cca28a$c6fa22d0$54ee6870$@linux.intel.com> (raw)
In-Reply-To: <20111111214700.GC3224@oh.minilop.net>

> -----Original Message-----
> From: Jamey Sharp [mailto:jamey@minilop.net]
> Sent: Saturday, November 12, 2011 5:47 AM
> To: Zhigang Gong
> Cc: xorg-devel@lists.x.org; intel-gfx@lists.freedesktop.org
> Subject: Re: Glamor update
> 
> Hello!
> 
> On Fri, Nov 11, 2011 at 04:42:32PM +0800, Zhigang Gong wrote:
> > 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've looked over all the source in your glamor repo, and your patches to
> the Intel driver. This work looks very promising! I'm eager to see more
> progress.
> 
> I don't speak for the Intel graphics team or anything, but I noticed a couple
> minor things you might clean up. In the "glamor: turn on glamor."
> commit, there's a patch hunk that just adds an empty ifdef:
> 
> -
> +#ifdef GLAMOR
> +#endif
Fixed.
> 
> You might want to remove that. Also, the call to
> intel_glamor_create_textured_pixmap in intel_uxa_create_pixmap is
> inconsistently indented; it should just be tabs, looks like.
Fixed.
I will submit the new version patch again latter. Thanks for your carefully 
reviewing.

> 
> Any chance you'll add some of the Xephyr/glamor functionality to
> xf86-video-nested, too? I think that should be easier to test and hack on.

Currently, we don't have enough bandwidth to do that. If anyone in the 
community want to do that, I'd be happy to provide help. 

> 
> Jamey

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2011-11-14  5:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-11  8:42 Glamor update Zhigang Gong
2011-11-11 21:47 ` Jamey Sharp
2011-11-14  5:03   ` Zhigang Gong [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='065501cca28a$c6fa22d0$54ee6870$@linux.intel.com' \
    --to=zhigang.gong@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jamey@minilop.net \
    --cc=xorg-devel@lists.x.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