Alan Cox wrote:
Actually, it's more like this: libGL talks to the X server via the DRI X extension to determine if direct rendering is enabled and to determine the name of the driver to use. We load the DRI driver during screen initialization and pass control to it via glXCreateContext, glXMakeCurrent, etc. The libGL dispatcher routes gl*() function calls into the driver. The DRI driver uses Mesa (or another OpenGL core) to manage state and do rendering tasks which the hardware can't perform.On Sun, 2003-01-12 at 19:54, Erling A. Jacobsen wrote:Perhaps the dri-devel list isn't the right place to be, because what I have in mind is indeed not a DRI driver, rather a modification of the version of Mesa which DRI uses if there's no hardware-accelerated DRI-driver available. But still, this is where the people who know most about Mesa, XFree86, DRI and the integration between these systems are ...Mesa talks to the X server Mesa figures out if their is suitable direct rendering available If there is Mesa uses it If not Mesa renders and issues 2D commands to the Xserver
If direct rendering is not available, we use indirect rendering (send GL drawing commands over the wire to the Xserver). The Xserver in turn executes the GL commands.
A DRI driver may be based on Mesa or another implementation of OpenGL. All the open-source DRI drivers are Mesa-based, but not the closed, proprietary drivers.
Mesa (currently unaccelerated) also exists in the Xserver to handle GLX
requests (clients remotely asking for 3D drawing to be done). Unlike
the DRI drivers this is done by the Xserver in Xserver context so
doesn't require trusted hardware and can relax locking rules a lot.
Currently XFree86 server side GLX handling doesn't include hardware
3D acceleraton.
At least as I follow it - I am no expert here.
-Brian ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
