EGL for X
brian.paul at tungstengraphics.com
Mon Sep 8 08:30:50 PDT 2008
mustafizur.rahaman at azingo.com wrote:
> Hi Brian,
> I took a look at the Gallium code & following are my analysis till now..
> 1>So, there is now libEGl.so,libEGLdri.so & also egl_xdri.so.That means
> my client program first talks to libEGL.so which in turn talk to either
> of libEGLdri.so OR egl_xdri.so(for EGL with X).And then
> libEGLdri.so/egl_xdri.so loads the actual H/W dri driver e.g.
> radeon_dri.so.It means even though i can complile both libEGLdri.so &
> egl_xdri.so together, but only of them will be present in a system, and
> not both of them..Is this correct understanding?
yes, I think so.
> 2>Right now, i can there is three path from which the actual driver(h/w
> dri.so)'s bootstrap function can be called. 1>From glX/x11 path, 2>From
> libEGLdri.so Or 3>From egl_xdri.so.But i can see as of now, egl_xdri.so
> is not directly calling the hw_dri.so , rather it is going via glX/x11
> to initialize the driver.So, for everything egl_xdri.so is talking to
> the hw dri driver through glX.Why is it so?
Well, we're operating with the X server so we need to go through GLX.
It's simplest just to re-use the existing GLX code.
> 3>When vendor will provide the GL implementation, what all library we
> should expect from the vendor?
All that should be needed is a *_dri.so driver module.
More information about the xorg