From: Andreas Boll Date: Tue, 12 Jun 2012 07:05:36 +0000 (+0200) Subject: docs: prefer lowercase html tags X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=210a27d8c33634c6b676a8a1d35d5fec98213181;p=mesa.git docs: prefer lowercase html tags Signed-off-by: Brian Paul --- diff --git a/docs/banner.html b/docs/banner.html index 10ace2c7d3b..43e302544d5 100644 --- a/docs/banner.html +++ b/docs/banner.html @@ -3,27 +3,27 @@ Banner - + -

The -Mesa 3D Graphics Library

+

The +Mesa 3D Graphics Library

diff --git a/docs/contents.html b/docs/contents.html index 08ec97799a9..a255b256920 100644 --- a/docs/contents.html +++ b/docs/contents.html @@ -27,7 +27,7 @@ a:visited { Developer Topics diff --git a/docs/devinfo.html b/docs/devinfo.html index 06322d1ce4d..c4b719469ce 100644 --- a/docs/devinfo.html +++ b/docs/devinfo.html @@ -53,7 +53,7 @@ To add a new GL extension to Mesa you have to do at least the following. -

Coding Style

+

Coding Style

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.

-

Making a New Mesa Release

+

Making a New Mesa Release

These are the instructions for making a new Mesa release.

-

Get latest source files

+

Get latest source files

Use git to get the latest Mesa files from the git repository, from whatever branch is relevant.

-

Verify and update version info

+

Verify and update version info

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 relnotes.html. @@ -193,7 +193,7 @@ Then: git push origin mesa_X_Y

-

Make the tarballs

+

Make the tarballs

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.
 

-

Update the website and announce the release

+

Update the website and announce the release

Follow the directions on SourceForge for creating a new "release" and uploading the tarballs. diff --git a/docs/dispatch.html b/docs/dispatch.html index 1d3283aa6cc..e80a480659b 100644 --- a/docs/dispatch.html +++ b/docs/dispatch.html @@ -11,10 +11,10 @@

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 overview of Mesa's implementation.

+with the issues around GL dispatch can safely skip ahead to the overview of Mesa's implementation.

-

1. Complexity of GL Dispatch

+

1. Complexity of GL Dispatch

Every GL application has at least one object called a GL context. 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.

similar function. Mesa provides a wrapper function called _glapi_get_dispatch that is used by default.

-

3. Optimizations

+

3. Optimizations

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.

-

3.1. Dual dispatch table pointers

+

3.1. Dual dispatch table pointers

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.

Improved GET_DISPATCH Implementation -

3.2. ELF TLS

+

3.2. ELF TLS

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 GLX_USE_TLS. Any platform capable of using TLS should use this as the default dispatch method.

-

3.3. Assembly Language Dispatch Stubs

+

3.3. Assembly Language Dispatch Stubs

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 below).

+space optimization (see below).

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 glapi_x86-64.S versus 1,155 lines for glapi_x86.S) and causes simple changes to the function implementation to generate many lines of diffs. Since the assmebly files -are typically generated by scripts (see below), this +are typically generated by scripts (see below), this isn't a significant problem.

Once a new assembly file is created, it must be inserted in the build diff --git a/docs/download.html b/docs/download.html index 207d879f0f2..3d543281f4b 100644 --- a/docs/download.html +++ b/docs/download.html @@ -21,7 +21,7 @@ When a new release is coming, release candidates (betas) may be found

-

Unpacking

+

Unpacking

Mesa releases are available in three formats: .tar.bz2, .tar.gz, and .zip @@ -80,7 +80,7 @@ instructions.

-

Demos and GLUT

+

Demos and GLUT

A package of Mark Kilgard's GLUT library is available diff --git a/docs/envvars.html b/docs/envvars.html index ee0a37d49bd..fffb50a4718 100644 --- a/docs/envvars.html +++ b/docs/envvars.html @@ -16,7 +16,7 @@ sometimes be useful for debugging end-user issues.

-

LibGL environment variables

+

LibGL environment variables

  • LIBGL_DEBUG - If defined debug information will be printed to stderr. @@ -29,7 +29,7 @@ sometimes be useful for debugging end-user issues. -

    Core Mesa environment variables

    +

    Core Mesa environment variables

    • 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)
    -

    Mesa Xlib driver environment variables

    +

    Mesa Xlib driver environment variables

    The following are only applicable to the Mesa Xlib software driver. -See the Xlib software driver page for details. +See the Xlib software driver page for details.

    • MESA_RGB_VISUAL - specifies the X visual and depth for RGB mode diff --git a/docs/install.html b/docs/install.html index 53164973205..c7995c860a8 100644 --- a/docs/install.html +++ b/docs/install.html @@ -71,7 +71,7 @@ the needed dependencies: -

      2. Building with autoconf (Linux/Unix/X11)

      +

      2. Building with autoconf (Linux/Unix/X11)

      The primary method to build Mesa on Unix systems is with autoconf. @@ -92,7 +92,7 @@ for more details. -

      3. Building with SCons (Windows/Linux)

      +

      3. Building with SCons (Windows/Linux)

      To build Mesa with SCons on Linux or Windows do @@ -126,21 +126,21 @@ Put them all in the same directory to test them. -

      4. Building for other systems

      +

      4. Building for other systems

      Documentation for other environments (some may be very out of date):

      - + -

      5. Library Information

      +

      5. Library Information

      When compilation has finished, look in the top-level lib/ @@ -184,7 +184,7 @@ versions of libGL and device drivers.

      -

      6. Building OpenGL programs with pkg-config

      +

      6. Building OpenGL programs with pkg-config

      Running make install will install package configuration files diff --git a/docs/intro.html b/docs/intro.html index f4e0f01c7e5..ef04f357ed9 100644 --- a/docs/intro.html +++ b/docs/intro.html @@ -31,7 +31,7 @@ systems. -

      Project History

      +

      Project History

      The Mesa project was originally started by Brian Paul. @@ -157,7 +157,7 @@ of the OpenGL specification. -

      Major Versions

      +

      Major Versions

      This is a summary of the major versions of Mesa. @@ -166,7 +166,7 @@ of the OpenGL specification is implemented.

      -

      Version 8.x features

      +

      Version 8.x features

      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.

      -

      Version 7.x features

      +

      Version 7.x features

      Version 7.x of Mesa implements the OpenGL 2.1 API. The main feature of OpenGL 2.x is the OpenGL Shading Language.

      -

      Version 6.x features

      +

      Version 6.x features

      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 for more details. -

      Version 5.x features

      +

      Version 5.x features

      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:

    -

    Version 4.x features

    +

    Version 4.x features

    Version 4.x of Mesa implements the OpenGL 1.3 API with the following @@ -267,7 +267,7 @@ extensions incorporated as standard features:

  • GL_ARB_transpose_matrix
-

Version 3.x features

+

Version 3.x features

Version 3.x of Mesa implements the OpenGL 1.2 API with the following @@ -283,7 +283,7 @@ features: -

Version 2.x features

+

Version 2.x features

Version 2.x of Mesa implements the OpenGL 1.1 API with the following features. diff --git a/docs/license.html b/docs/license.html index a840a69327f..f0ac28ccfe8 100644 --- a/docs/license.html +++ b/docs/license.html @@ -35,7 +35,7 @@ target="_parent">Silicon Graphics Incorporated. -

License / Copyright Information

+

License / Copyright Information

The Mesa distribution consists of several components. Different copyrights @@ -74,7 +74,7 @@ CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

-

Attention, Contributors

+

Attention, Contributors

When contributing to the Mesa project you must agree to the licensing terms @@ -84,7 +84,7 @@ and their respective licenses.

-

Mesa Component Licenses

+

Mesa Component Licenses

 Component         Location               License
diff --git a/docs/lists.html b/docs/lists.html
index d288cc81458..d89bcffbd11 100644
--- a/docs/lists.html
+++ b/docs/lists.html
@@ -63,7 +63,7 @@ DRI wiki.
 
 
-

OpenGL Forums

+

OpenGL Forums

Here are some other OpenGL-related forums you might find useful: diff --git a/docs/osmesa.html b/docs/osmesa.html index fafdc83dec3..2207641eded 100644 --- a/docs/osmesa.html +++ b/docs/osmesa.html @@ -20,7 +20,7 @@ One potential application is to use Mesa as an off-line, batch-style renderer.

-The OSMesa API provides three basic functions for making off-screen +The OSMesa 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.

-

Deep color channels

+

Deep color channels

For some applications 8-bit color channels don't have sufficient diff --git a/docs/postprocess.html b/docs/postprocess.html index b99ef2b9f5c..06a45930eed 100644 --- a/docs/postprocess.html +++ b/docs/postprocess.html @@ -26,7 +26,7 @@ Multiple filters can be used together.

-

PP environment variables

+

PP environment variables

-

Double Buffering

+

Double Buffering

Mesa can use either an X Pixmap or XImage as the back color buffer when in double-buffer mode. @@ -96,7 +96,7 @@ for your application.

-

Colormaps

+

Colormaps

When using Mesa directly or with GLX, it's up to the application writer to create a window with an appropriate colormap. The GLUT @@ -117,7 +117,7 @@ significant.

-

Gamma Correction

+

Gamma Correction

To compensate for the nonlinear relationship between pixel values and displayed intensities, there is a gamma correction feature in @@ -170,7 +170,7 @@ the Gamma FAQ

-

Overlay Planes

+

Overlay Planes

Hardware overlay planes are supported by the Xlib driver. To determine if your X server has overlay support you can test for the @@ -181,7 +181,7 @@ SERVER_OVERLAY_VISUALS property: -

HPCR Dithering

+

HPCR Dithering

If you set the MESA_HPCR_CLEAR environment variable then dithering will be used when clearing the color buffer. This is only applicable @@ -190,7 +190,7 @@ This incurs a small performance penalty.

-

Extensions

+

Extensions

The following MESA-specific extensions are implemented in the Xlib driver.

@@ -249,7 +249,7 @@ just before an X window is destroyed. For example: This extension was added in Mesa 2.0.

-

GLX_MESA_copy_sub_buffer

+

GLX_MESA_copy_sub_buffer

This extension adds the glXCopySubBufferMESA() function. It works like glXSwapBuffers() but only copies a sub-region of the window @@ -262,7 +262,7 @@ instead of the whole window. This extension was added in Mesa 2.6

-

Summary of X-related environment variables

+

Summary of X-related environment variables

    MESA_RGB_VISUAL - specifies the X visual and depth for RGB mode (X only)
    MESA_CI_VISUAL - specifies the X visual and depth for CI mode (X only)