<h2>Extensions</h2>
<p>
-The following MESA-specific extensions are implemented in the Xlib driver.
+The following Mesa-specific extensions are implemented in the Xlib driver.
</p>
<h3>GLX_MESA_pixmap_colormap</h3>
--------------------------------
Good question, given there are already three (swrast, softpipe,
-llvmpipe) in the Mesa3D tree. Two important reasons for this:
+llvmpipe) in the Mesa tree. Two important reasons for this:
* Architecture - given our focus on scientific visualization, our
workloads are much different than the typical game; we have heavy
* Historical - Intel had developed a high performance software
graphics stack for internal purposes. Later we adapted this
graphics stack for use in visualization and decided to move forward
- with Mesa3D to provide a high quality API layer while at the same
+ with Mesa to provide a high quality API layer while at the same
time benefiting from the excellent performance the software
rasterizerizer gives us.
*
* See also:
* - Direct3D's D3DLOCK_DONOTWAIT flag.
- * - Mesa3D's MESA_MAP_NOWAIT_BIT flag.
+ * - Mesa's MESA_MAP_NOWAIT_BIT flag.
* - WDDM's D3DDDICB_LOCKFLAGS.DonotWait flag.
*/
PIPE_TRANSFER_DONTBLOCK = (1 << 9),
}
/**
- * Builds the MESA version string.
+ * Builds the Mesa version string.
*/
static void
create_version_string(struct gl_context *ctx, const char *prefix)