On Fri, 2010-01-15 at 16:43 +0800, Chia-I Wu wrote: 
> 2010/1/15 Michel Dänzer <mic...@daenzer.net>:
> > On Fri, 2010-01-15 at 12:05 +0800, Chia-I Wu wrote:
> >>
> >> > enum st_framebuffer_attachment {
> >> >    ST_SURFACE_FRONT_LEFT,
> >> >    ST_SURFACE_BACK_LEFT,
> >> >    ST_SURFACE_FRONT_RIGHT,
> >> >    ST_SURFACE_BACK_RIGHT,
> >> >    ST_SURFACE_DEPTH_STENCIL,
> >> > };
> >> In my version, there is no depth/stencil attachment.  It is created by the
> >> state tracker from the pipe screen.
> >>
> >> The idea is, the display server provides only those potentially visible to 
> >> the
> >> users.  The depth/stencil buffer is an artifact.  I am not sure if this is
> >> correct, but I would like to find out if depth/stencil is really needed to 
> >> be
> >> allocated by the display server.
> > It is for GLX, as Keith pointed out before.
> Why is that?  For direct and indirect rendering, under Gallium, the 
> application
> or the server is capable of creating the depth/stencil buffer from the pipe
> screen.
> 
> The problem I can see here is that the depth/stencil buffer is no longer
> shareable between contexts.  But I am curious to know if this is a real
> problem?

As the colour buffers are shared, I don't see why depth/stencil
shouldn't be.

> Another question I have is, if depth/stencil should be shareable, how
> about other buffers like multisample buffer?  (This is a real question that 
> has
> bothered me for a while.  I am eager for an answer here.)

Unfortunately I don't know the answer to that, hopefully someone else
can jump in.


-- 
Earthling Michel Dänzer           |                http://www.vmware.com
Libre software enthusiast         |          Debian, X and DRI developer

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Reply via email to