-<p>There are two categories of EGL drivers: Gallium and classic.</p>
-
-<p>Gallium EGL drivers supports all rendering APIs specified in EGL 1.4. These
-drivers depend on the <code>egl</code> state tracker to build. The available
-drivers are</p>
-
-<ul>
-<li><code>egl_<dpy>_i915</code></li>
-<li><code>egl_<dpy>_i965</code></li>
-<li><code>egl_<dpy>_nouveau</code></li>
-<li><code>egl_<dpy>_radeon</code></li>
-<li><code>egl_<dpy>_swrast</code></li>
-<li><code>egl_<dpy>_vmwgfx</code></li>
-</ul>
-
-<p><code><dpy></code> is given by <code>--with-egl-platforms</code> at
-configuration time. There is usually one EGL driver for each combination of
-the platforms listed and the pipe drivers enabled. When the platform is pure
-software or pure hardware, non-working combinations will not be built.</p>
-
-<p>Classic EGL drivers, on the other hand, support only a subset of the
-available rendering APIs. They can be found under
-<code>src/egl/drivers/</code>. There are 3 of them</p>
-
-<ul>
-<li><code>egl_glx</code>
-
-<p>This driver provides a wrapper to GLX. It uses exclusively GLX to implement
-the EGL API. It supports both direct and indirect rendering when the GLX does.
-It is accelerated when the GLX is. As such, it cannot provide functions that
-is not available in GLX or GLX extensions.</p>
-</li>