No subject

3D-enabled XServer with GLX extension and without DRI extension (and module)
?

On "Introduction to the Direct Rendering Infrastructure" (
http://dri.sourceforge.net/doc/DRIintro.html), it says about "XFree86 DRI
Extension":

    The XFree86-DRI X server extension is basically used for communication
between the other DRI
    components (the X server, the kernel module, libGL.so and the 3D DRI
drivers).

    The DRI module maintains DRI-specific data structures related to
screens, windows, and rendering
    contexts. When the user moves a window, for example, the other DRI
components need to be informed
    so that rendering appears in the right place.

Does it means any OGL implementation within the server-side must supply a
DRI module ?
What about the OGL Mesa library with SW rasterization only ? Does it supply
a DRI module (for managing a lock on the framebuffer) ?
Is it possible to use Mesa driver with a non-DRI backend in the server-side
?

Thanks,
Olivier

--001636c5a2a55c3ae5046a2c50c0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Just a little question to clarify my understanding of XServer design ...<br=
><br>From the DRI website, I can read this article about &quot;DRI without =
X&quot; (<a href=3D"http://dri.freedesktop.org/wiki/DriWithoutX">http://dri=
.freedesktop.org/wiki/DriWithoutX</a>). But is it possible to have a 3D-ena=
bled XServer with GLX extension and without DRI extension (and module) ?<br=
>
<br>On &quot;Introduction to the Direct Rendering Infrastructure&quot; (<a =
href=3D"http://dri.sourceforge.net/doc/DRIintro.html">http://dri.sourceforg=
e.net/doc/DRIintro.html</a>), it says about &quot;XFree86 DRI Extension&quo=
t;:<br>
<br>=A0=A0=A0 The XFree86-DRI X server extension is basically used for comm=
unication between the other DRI<br>=A0=A0=A0 components (the X server, the =
kernel module, libGL.so and the 3D DRI drivers).<br><br>=A0=A0=A0 The DRI m=
odule maintains DRI-specific data structures related to screens, windows, a=
nd rendering<br>
=A0=A0=A0 contexts. When the user moves a window, for example, the other DR=
I components need to be informed<br>=A0=A0=A0 so that rendering appears in =
the right place.<br><br>Does it means any OGL implementation within the ser=
ver-side must supply a DRI module ?<br>
What about the OGL Mesa library with SW rasterization only ? Does it supply=
 a DRI module (for managing a lock on the framebuffer) ?<br>Is it possible =
to use Mesa driver with a non-DRI backend in the server-side ?<br><br>Thank=
s,<br>
Olivier<br>

--001636c5a2a55c3ae5046a2c50c0--