Commit 210a27d8 authored by Andreas Boll's avatar Andreas Boll Committed by Brian Paul

docs: prefer lowercase html tags

Signed-off-by: Brian Paul's avatarBrian Paul <>
parent cc418889
......@@ -3,27 +3,27 @@
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<style type="text/css" >
BODY { BACKGROUND: BLACK; COLOR: WHITE } TABLE { width: 94%; text-align: left; }
TD { vertical-align: top }
H1 {
body { background: black; color: white } table { width: 94%; text-align: left; }
td { vertical-align: top }
h1 {
font: x-large sans-serif; text-align: center;
height: 75px; margin-left: 100px; margin-right: 100px }
.gears { width: 100px; height: 73px; float: left; background: url('gears.png') right no-repeat }
div + .gears { float: right; background-position: left }
This should happen in the future instead:
H1 {
border-image: url(gears.png) 100%; -WEBKIT-border-image: url(gears.png) 100%;
h1 {
border-left: 71px solid #c11800; border-right: 71px solid #00c130;
border-top: 0px; border-bottom: 0px;
border-image: url(gears.png) 100%; -webkit-border-image: url(gears.png) 100%;
</style >
<body ><DIV CLASS="gears" ></DIV ><DIV CLASS="gears" ></DIV ><H1 >The
Mesa 3D Graphics Library</H1 >
<body ><div class="gears" ></div ><div class="gears" ></div ><h1 >The
Mesa 3D Graphics Library</h1 >
......@@ -27,7 +27,7 @@ a:visited {
<li><a href="intro.html" target="MainFrame">Introduction</a>
<li><a href="news.html" target="MainFrame">News</a>
<LI><A HREF="developers.html" target="MainFrame">Developers</A>
<li><a href="developers.html" target="MainFrame">Developers</a>
<li><a href="systems.html" target="MainFrame">Platforms and Drivers</a>
<li><a href="license.html" target="MainFrame">License &amp; Copyright</a>
<li><a href="faq.html" target="MainFrame">FAQ</a>
......@@ -57,16 +57,16 @@ a:visited {
<li><a href="egl.html" target="MainFrame">EGL</a>
<li><a href="opengles.html" target="MainFrame">OpenGL ES</a>
<li><a href="openvg.html" target="MainFrame">OpenVG / Vega</a>
<LI><A HREF="envvars.html" target="MainFrame">Environment Variables</A>
<LI><A HREF="osmesa.html" target="MainFrame">Off-Screen Rendering</A>
<LI><A HREF="debugging.html" target="MainFrame">Debugging Tips</A>
<LI><A HREF="perf.html" target="MainFrame">Performance Tips</A>
<LI><A HREF="extensions.html" target="MainFrame">Mesa Extensions</A>
<LI><A HREF="mangling.html" target="MainFrame">Function Name Mangling</A>
<LI><A href="llvmpipe.html" target="MainFrame">Gallium llvmpipe driver</A>
<LI><A href="vmware-guest.html" target="MainFrame">VMware SVGA3D guest driver</a>
<LI><A href="postprocess.html" target="MainFrame">Gallium post-processing</A>
<LI><A href="viewperf.html" target="MainFrame">Viewperf Issues</A>
<li><a href="envvars.html" target="MainFrame">Environment Variables</a>
<li><a href="osmesa.html" target="MainFrame">Off-Screen Rendering</a>
<li><a href="debugging.html" target="MainFrame">Debugging Tips</a>
<li><a href="perf.html" target="MainFrame">Performance Tips</a>
<li><a href="extensions.html" target="MainFrame">Mesa Extensions</a>
<li><a href="mangling.html" target="MainFrame">Function Name Mangling</a>
<li><a href="llvmpipe.html" target="MainFrame">Gallium llvmpipe driver</a>
<li><a href="vmware-guest.html" target="MainFrame">VMware SVGA3D guest driver</a>
<li><a href="postprocess.html" target="MainFrame">Gallium post-processing</a>
<li><a href="viewperf.html" target="MainFrame">Viewperf Issues</a>
<b>Developer Topics</b>
......@@ -53,7 +53,7 @@ To add a new GL extension to Mesa you have to do at least the following.
<H2>Coding Style</H2>
<h2>Coding Style</h2>
Mesa's code style has changed over the years. Here's the latest.
......@@ -149,20 +149,20 @@ src/mesa/state_tracker/st_glsl_to_tgsi.cpp can serve as examples.
<H2>Making a New Mesa Release</H2>
<h2>Making a New Mesa Release</h2>
These are the instructions for making a new Mesa release.
<H3>Get latest source files</H3>
<h3>Get latest source files</h3>
Use git to get the latest Mesa files from the git repository, from whatever
branch is relevant.
<H3>Verify and update version info</H3>
<h3>Verify and update version info</h3>
Create/edit the docs/relnotes-x.y.html file to document what's new in the release.
Add the new relnotes-x.y.html file to <a href="relnotes.html">relnotes.html</a>.
......@@ -193,7 +193,7 @@ Then: <code>git push origin mesa_X_Y</code>
<H3>Make the tarballs</H3>
<h3>Make the tarballs</h3>
Make the distribution files. From inside the Mesa directory:
......@@ -211,7 +211,7 @@ Copy the distribution files to a temporary directory, unpack them,
compile everything, and run some demos to be sure everything works.
<H3>Update the website and announce the release</H3>
<h3>Update the website and announce the release</h3>
Follow the directions on SourceForge for creating a new "release" and
uploading the tarballs.
......@@ -11,10 +11,10 @@
<p>Several factors combine to make efficient dispatch of OpenGL functions
fairly complicated. This document attempts to explain some of the issues
and introduce the reader to Mesa's implementation. Readers already familiar
with the issues around GL dispatch can safely skip ahead to the <A
HREF="#overview">overview of Mesa's implementation</A>.</p>
with the issues around GL dispatch can safely skip ahead to the <a
href="#overview">overview of Mesa's implementation</a>.</p>
<H2>1. Complexity of GL Dispatch</H2>
<h2>1. Complexity of GL Dispatch</h2>
<p>Every GL application has at least one object called a GL <em>context</em>.
This object, which is an implicit parameter to ever GL function, stores all
......@@ -89,14 +89,14 @@ overhead that it adds to every GL function call.</p>
similar function. Mesa provides a wrapper function called
<tt>_glapi_get_dispatch</tt> that is used by default.</p>
<H2>3. Optimizations</H2>
<h2>3. Optimizations</h2>
<p>A number of optimizations have been made over the years to diminish the
performance hit imposed by GL dispatch. This section describes these
optimizations. The benefits of each optimization and the situations where
each can or cannot be used are listed.</p>
<H3>3.1. Dual dispatch table pointers</H3>
<h3>3.1. Dual dispatch table pointers</h3>
<p>The vast majority of OpenGL applications use the API in a single threaded
manner. That is, the application has only one thread that makes calls into
......@@ -131,7 +131,7 @@ the common case.</p>
<tr><td>Improved <tt>GET_DISPATCH</tt> Implementation</td></tr></table>
<H3>3.2. ELF TLS</H3>
<h3>3.2. ELF TLS</h3>
<p>Starting with the 2.4.20 Linux kernel, each thread is allocated an area
of per-thread, global storage. Variables can be put in this area using some
......@@ -161,7 +161,7 @@ extern __thread struct _glapi_table *_glapi_tls_Dispatch
<tt>GLX_USE_TLS</tt>. Any platform capable of using TLS should use this as
the default dispatch method.</p>
<H3>3.3. Assembly Language Dispatch Stubs</H3>
<h3>3.3. Assembly Language Dispatch Stubs</h3>
<p>Many platforms has difficulty properly optimizing the tail-call in the
dispatch stubs. Platforms like x86 that pass parameters on the stack seem
......@@ -170,7 +170,7 @@ routines are very short, and it is trivial to create optimal assembly
language versions. The amount of optimization provided by using assembly
stubs varies from platform to platform and application to application.
However, by using the assembly stubs, many platforms can use an additional
space optimization (see <A HREF="#fixedsize">below</A>).</p>
space optimization (see <a href="#fixedsize">below</a>).</p>
<p>The biggest hurdle to creating assembly stubs is handling the various
ways that the dispatch table pointer can be accessed. There are four
......@@ -235,7 +235,7 @@ implementation of each function. This makes the assembly file considerably
larger (e.g., 29,332 lines for <tt>glapi_x86-64.S</tt> versus 1,155 lines for
<tt>glapi_x86.S</tt>) and causes simple changes to the function
implementation to generate many lines of diffs. Since the assmebly files
are typically generated by scripts (see <A HREF="#autogen">below</A>), this
are typically generated by scripts (see <a href="#autogen">below</a>), this
isn't a significant problem.</p>
<p>Once a new assembly file is created, it must be inserted in the build
......@@ -21,7 +21,7 @@ When a new release is coming, release candidates (betas) may be found
Mesa releases are available in three formats: .tar.bz2, .tar.gz, and .zip
......@@ -80,7 +80,7 @@ instructions</a>.
<H1>Demos and GLUT</H1>
<h1>Demos and GLUT</h1>
A package of Mark Kilgard's GLUT library is available
......@@ -16,7 +16,7 @@ sometimes be useful for debugging end-user issues.
<H2>LibGL environment variables</H2>
<h2>LibGL environment variables</h2>
<li>LIBGL_DEBUG - If defined debug information will be printed to stderr.
......@@ -29,7 +29,7 @@ sometimes be useful for debugging end-user issues.
<H2>Core Mesa environment variables</H2>
<h2>Core Mesa environment variables</h2>
<li>MESA_NO_ASM - if set, disables all assembly language optimizations
......@@ -71,11 +71,11 @@ if it's higher than what's normally reported. (for developers only)
<H2>Mesa Xlib driver environment variables</H2>
<h2>Mesa Xlib driver environment variables</h2>
The following are only applicable to the Mesa Xlib software driver.
See the <A HREF="xlibdriver.html">Xlib software driver page</A> for details.
See the <a href="xlibdriver.html">Xlib software driver page</a> for details.
<li>MESA_RGB_VISUAL - specifies the X visual and depth for RGB mode
......@@ -71,7 +71,7 @@ the needed dependencies:
<H1 id="autoconf">2. Building with autoconf (Linux/Unix/X11)</H1>
<h1 id="autoconf">2. Building with autoconf (Linux/Unix/X11)</h1>
The primary method to build Mesa on Unix systems is with autoconf.
......@@ -92,7 +92,7 @@ for more details.
<H1 id="scons">3. Building with SCons (Windows/Linux)</H1>
<h1 id="scons">3. Building with SCons (Windows/Linux)</h1>
To build Mesa with SCons on Linux or Windows do
......@@ -126,21 +126,21 @@ Put them all in the same directory to test them.
<H1 id="other">4. Building for other systems</H1>
<h1 id="other">4. Building for other systems</h1>
Documentation for other environments (some may be very out of date):
<li><a href="README.VMS">README.VMS</a> - VMS
<li><a href="README.CYGWIN">README.CYGWIN</a> - Cygwin
<li><a href="README.WIN32">README.WIN32</a> - Win32
<H1 id="libs">5. Library Information</H1>
<h1 id="libs">5. Library Information</h1>
When compilation has finished, look in the top-level <code>lib/</code>
......@@ -184,7 +184,7 @@ versions of libGL and device drivers.
<H1 id="pkg-config">6. Building OpenGL programs with pkg-config</H1>
<h1 id="pkg-config">6. Building OpenGL programs with pkg-config</h1>
Running <code>make install</code> will install package configuration files
......@@ -31,7 +31,7 @@ systems.
<H1>Project History</H1>
<h1>Project History</h1>
The Mesa project was originally started by Brian Paul.
......@@ -157,7 +157,7 @@ of the OpenGL specification.
<H1>Major Versions</H1>
<h1>Major Versions</h1>
This is a summary of the major versions of Mesa.
......@@ -166,7 +166,7 @@ of the OpenGL specification is implemented.
<H2>Version 8.x features</H2>
<h2>Version 8.x features</h2>
Version 8.x of Mesa implements the OpenGL 3.0 API.
The developers at Intel deserve a lot of credit for implementing most
......@@ -175,14 +175,14 @@ the i965 driver.
<H2>Version 7.x features</H2>
<h2>Version 7.x features</h2>
Version 7.x of Mesa implements the OpenGL 2.1 API. The main feature
of OpenGL 2.x is the OpenGL Shading Language.
<H2>Version 6.x features</H2>
<h2>Version 6.x features</h2>
Version 6.x of Mesa implements the OpenGL 1.5 API with the following
extensions incorporated as standard features:
......@@ -222,7 +222,7 @@ OpenGL specification</a> for more details.
<H2>Version 5.x features</H2>
<h2>Version 5.x features</h2>
Version 5.x of Mesa implements the OpenGL 1.4 API with the following
extensions incorporated as standard features:
......@@ -248,7 +248,7 @@ extensions incorporated as standard features:
<H2>Version 4.x features</H2>
<h2>Version 4.x features</h2>
Version 4.x of Mesa implements the OpenGL 1.3 API with the following
......@@ -267,7 +267,7 @@ extensions incorporated as standard features:
<H2>Version 3.x features</H2>
<h2>Version 3.x features</h2>
Version 3.x of Mesa implements the OpenGL 1.2 API with the following
......@@ -283,7 +283,7 @@ features:
<H2>Version 2.x features</H2>
<h2>Version 2.x features</h2>
Version 2.x of Mesa implements the OpenGL 1.1 API with the following
......@@ -35,7 +35,7 @@ target="_parent">Silicon Graphics Incorporated</a>.
<H1>License / Copyright Information</H1>
<h1>License / Copyright Information</h1>
The Mesa distribution consists of several components. Different copyrights
<H1>Attention, Contributors</H1>
<h1>Attention, Contributors</h1>
When contributing to the Mesa project you must agree to the licensing terms
......@@ -84,7 +84,7 @@ and their respective licenses.
<H1>Mesa Component Licenses</H1>
<h1>Mesa Component Licenses</h1>
Component Location License
......@@ -63,7 +63,7 @@ DRI wiki</a>.
<H1>OpenGL Forums</H1>
<h1>OpenGL Forums</h1>
Here are some other OpenGL-related forums you might find useful:
......@@ -20,7 +20,7 @@ One potential application is to use Mesa as an off-line, batch-style renderer.
The <B>OSMesa</B> API provides three basic functions for making off-screen
The <b>OSMesa</b> API provides three basic functions for making off-screen
renderings: OSMesaCreateContext(), OSMesaMakeCurrent(), and
OSMesaDestroyContext(). See the Mesa/include/GL/osmesa.h header for
more information about the API functions.
......@@ -32,7 +32,7 @@ directory.
<H2>Deep color channels</H2>
<h2>Deep color channels</h2>
For some applications 8-bit color channels don't have sufficient
......@@ -26,7 +26,7 @@ Multiple filters can be used together.
<H2>PP environment variables</H2>
<h2>PP environment variables</h2>
<li>PP_DEBUG - If defined debug information will be printed to stderr.
......@@ -13,82 +13,82 @@
The release notes summarize what's new or changed in each Mesa release.
<LI><A HREF="relnotes-8.0.3.html">8.0.3 release notes</A>
<LI><A HREF="relnotes-8.0.2.html">8.0.2 release notes</A>
<LI><A HREF="relnotes-8.0.1.html">8.0.1 release notes</A>
<LI><A HREF="relnotes-8.0.html">8.0 release notes</A>
<LI><A HREF="relnotes-7.11.html">7.11 release notes</A>
<LI><A HREF="relnotes-7.10.3.html">7.10.3 release notes</A>
<LI><A HREF="relnotes-7.10.2.html">7.10.2 release notes</A>
<LI><A HREF="relnotes-7.10.1.html">7.10.1 release notes</A>
<LI><A HREF="relnotes-7.10.html">7.10 release notes</A>
<LI><A HREF="relnotes-7.9.2.html">7.9.2 release notes</A>
<LI><A HREF="relnotes-7.9.1.html">7.9.1 release notes</A>
<LI><A HREF="relnotes-7.9.html">7.9 release notes</A>
<LI><A HREF="relnotes-7.8.3.html">7.8.3 release notes</A>
<LI><A HREF="relnotes-7.8.2.html">7.8.2 release notes</A>
<LI><A HREF="relnotes-7.8.1.html">7.8.1 release notes</A>
<LI><A HREF="relnotes-7.8.html">7.8 release notes</A>
<LI><A HREF="relnotes-7.7.1.html">7.7.1 release notes</A>
<LI><A HREF="relnotes-7.7.html">7.7 release notes</A>
<LI><A HREF="relnotes-7.6.1.html">7.6.1 release notes</A>
<LI><A HREF="relnotes-7.6.html">7.6 release notes</A>
<LI><A HREF="relnotes-7.5.2.html">7.5.2 release notes</A>
<LI><A HREF="relnotes-7.5.1.html">7.5.1 release notes</A>
<LI><A HREF="relnotes-7.5.html">7.5 release notes</A>
<LI><A HREF="relnotes-7.4.4.html">7.4.4 release notes</A>
<LI><A HREF="relnotes-7.4.3.html">7.4.3 release notes</A>
<LI><A HREF="relnotes-7.4.2.html">7.4.2 release notes</A>
<LI><A HREF="relnotes-7.4.1.html">7.4.1 release notes</A>
<LI><A HREF="relnotes-7.4.html">7.4 release notes</A>
<LI><A HREF="relnotes-7.3.html">7.3 release notes</A>
<LI><A HREF="relnotes-7.2.html">7.2 release notes</A>
<LI><A HREF="relnotes-7.1.html">7.1 release notes</A>
<LI><A HREF="relnotes-7.0.4.html">7.0.4 release notes</A>
<LI><A HREF="relnotes-7.0.3.html">7.0.3 release notes</A>
<LI><A HREF="relnotes-7.0.2.html">7.0.2 release notes</A>
<LI><A HREF="relnotes-7.0.1.html">7.0.1 release notes</A>
<LI><A HREF="relnotes-7.0.html">7.0 release notes</A>
<LI><A HREF="relnotes-6.5.3.html">6.5.3 release notes</A>
<LI><A HREF="relnotes-6.5.2.html">6.5.2 release notes</A>
<LI><A HREF="relnotes-6.5.1.html">6.5.1 release notes</A>
<LI><A HREF="relnotes-6.5.html">6.5 release notes</A>
<LI><A HREF="relnotes-6.4.2.html">6.4.2 release notes</A>
<LI><A HREF="relnotes-6.4.1.html">6.4.1 release notes</A>
<LI><A HREF="relnotes-6.4.html">6.4 release notes</A>
<li><a href="relnotes-8.0.3.html">8.0.3 release notes</a>
<li><a href="relnotes-8.0.2.html">8.0.2 release notes</a>
<li><a href="relnotes-8.0.1.html">8.0.1 release notes</a>
<li><a href="relnotes-8.0.html">8.0 release notes</a>
<li><a href="relnotes-7.11.html">7.11 release notes</a>
<li><a href="relnotes-7.10.3.html">7.10.3 release notes</a>
<li><a href="relnotes-7.10.2.html">7.10.2 release notes</a>
<li><a href="relnotes-7.10.1.html">7.10.1 release notes</a>
<li><a href="relnotes-7.10.html">7.10 release notes</a>
<li><a href="relnotes-7.9.2.html">7.9.2 release notes</a>
<li><a href="relnotes-7.9.1.html">7.9.1 release notes</a>
<li><a href="relnotes-7.9.html">7.9 release notes</a>
<li><a href="relnotes-7.8.3.html">7.8.3 release notes</a>
<li><a href="relnotes-7.8.2.html">7.8.2 release notes</a>
<li><a href="relnotes-7.8.1.html">7.8.1 release notes</a>
<li><a href="relnotes-7.8.html">7.8 release notes</a>
<li><a href="relnotes-7.7.1.html">7.7.1 release notes</a>
<li><a href="relnotes-7.7.html">7.7 release notes</a>
<li><a href="relnotes-7.6.1.html">7.6.1 release notes</a>
<li><a href="relnotes-7.6.html">7.6 release notes</a>
<li><a href="relnotes-7.5.2.html">7.5.2 release notes</a>
<li><a href="relnotes-7.5.1.html">7.5.1 release notes</a>
<li><a href="relnotes-7.5.html">7.5 release notes</a>
<li><a href="relnotes-7.4.4.html">7.4.4 release notes</a>
<li><a href="relnotes-7.4.3.html">7.4.3 release notes</a>
<li><a href="relnotes-7.4.2.html">7.4.2 release notes</a>
<li><a href="relnotes-7.4.1.html">7.4.1 release notes</a>
<li><a href="relnotes-7.4.html">7.4 release notes</a>
<li><a href="relnotes-7.3.html">7.3 release notes</a>
<li><a href="relnotes-7.2.html">7.2 release notes</a>
<li><a href="relnotes-7.1.html">7.1 release notes</a>
<li><a href="relnotes-7.0.4.html">7.0.4 release notes</a>
<li><a href="relnotes-7.0.3.html">7.0.3 release notes</a>
<li><a href="relnotes-7.0.2.html">7.0.2 release notes</a>
<li><a href="relnotes-7.0.1.html">7.0.1 release notes</a>
<li><a href="relnotes-7.0.html">7.0 release notes</a>
<li><a href="relnotes-6.5.3.html">6.5.3 release notes</a>
<li><a href="relnotes-6.5.2.html">6.5.2 release notes</a>
<li><a href="relnotes-6.5.1.html">6.5.1 release notes</a>
<li><a href="relnotes-6.5.html">6.5 release notes</a>
<li><a href="relnotes-6.4.2.html">6.4.2 release notes</a>
<li><a href="relnotes-6.4.1.html">6.4.1 release notes</a>
<li><a href="relnotes-6.4.html">6.4 release notes</a>
Versions of Mesa prior to 6.4 are summarized in the
<a href="versions.html">versions file</a> and the following release notes.
<li><a href="RELNOTES-6.3.2">RELNOTES-6.3.2</a>
<li><a href="RELNOTES-6.3">RELNOTES-6.3</a>
<li><a href="RELNOTES-6.2.1">RELNOTES-6.2.1</a>
<li><a href="RELNOTES-6.2">RELNOTES-6.2</a>
<li><a href="RELNOTES-6.1">RELNOTES-6.1</a>
<li><a href="RELNOTES-6.0">RELNOTES-6.0</a>
<li><a href="RELNOTES-5.1">RELNOTES-5.1</a>
<li><a href="RELNOTES-5.0.2">RELNOTES-5.0.2</a>
<li><a href="RELNOTES-5.0.1">RELNOTES-5.0.1</a>
<li><a href="RELNOTES-5.0">RELNOTES-5.0</a>
<li><a href="RELNOTES-4.1">RELNOTES-4.1</a>
<li><a href="RELNOTES-4.0.3">RELNOTES-4.0.3</a>
<li><a href="RELNOTES-4.0.2">RELNOTES-4.0.2</a>
<li><a href="RELNOTES-4.0.1">RELNOTES-4.0.1</a>
<li><a href="RELNOTES-4.0">RELNOTES-4.0</a>
<li><a href="RELNOTES-3.5">RELNOTES-3.5</a>
<li><a href="RELNOTES-3.4.2">RELNOTES-3.4.2</a>
<li><a href="RELNOTES-3.4.1">RELNOTES-3.4.1</a>
<li><a href="RELNOTES-3.4">RELNOTES-3.4</a>
<li><a href="RELNOTES-3.3">RELNOTES-3.3</a>
<li><a href="RELNOTES-3.2.1">RELNOTES-3.2.1</a>
<li><a href="RELNOTES-3.2">RELNOTES-3.2</a>
<li><a href="RELNOTES-3.1">RELNOTES-3.1</a>
......@@ -92,7 +92,7 @@ Once your account is established:
<H2>Windows Users</H2>
<h2>Windows Users</h2>
If you're <a href="" target="_parent">
......@@ -131,7 +131,7 @@ Questions about branch status/activity should be posted to the
mesa3d-dev mailing list.
<H2>Developer Git Tips</H2>
<h2>Developer Git Tips</h2>
<li>Setting up to edit the master branch
......@@ -10,7 +10,7 @@
<h1>Source Code Documentation</h1>
<A HREF="" target="_parent">Doxygen</A>
<a href="" target="_parent">Doxygen</a>
is used to automatically
produce cross-referenced documentation from the Mesa source code.
......@@ -28,11 +28,11 @@ such as <a href="
If you're reading this page from your local copy of Mesa, and have
run the doxygen scripts, you can read the documentation
<A HREF="../doxygen/main/index.html" target="_parent">here</A>
<a href="../doxygen/main/index.html" target="_parent">here</a>