What about glxCopyContext

[Michel Danzer]

On Tue, 2005-05-17 at 11:13 -0400, Brian Paul wrote:
> Matthias Hopf wrote: 
> > On May 15, 05 19:24:44 -0600, Brian Paul wrote: 
> >  
> >>Jon Smirl wrote: 
> >> 
> >>>Do we need an eglCopyContext()? 
> >> 
> >>I don't recall ever seeing a GLX application that used
> glXCopyContext.  
> >> Does XGL need it? 
> >  
> >  
> > Not really. 
> >  
> > We need a mechanism for sharing texture data between different 
> > *processes*. As the implications and exact requirements for that are
> not 
> > completely clear so far, we decided to delay this until Xgl matured
> a 
> > bit. Then we'll come up with a proposal for another extension.
> 
> I guess I'm not fully aware of the issues yet.  In terms of  
> *processes* there's:
> 
> 1. The EGL layer/driver + XGL server + compositor 
> 2. The OpenGL/Xlib application(s)
> 
> Right?  Or is the compositor in a different process?

The compositing manager is an X client much like the window manager (in
fact, it will usually make sense for the two to be one and the same).


-- 
Michel Danzer, Linux Software Engineering       \   Tel: +1 905-882-2600
ATI Technologies Inc., Markham, Ontario, Canada  \       Extension: 3550
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freedesktop.org/archives/dri-egl/attachments/20050517/f8ac10b7/attachment.htm