diff options
| author | Brian Paul <[email protected]> | 2006-04-19 16:55:27 +0000 |
|---|---|---|
| committer | Brian Paul <[email protected]> | 2006-04-19 16:55:27 +0000 |
| commit | 6e542f11c9cc792123992446900df919d6ea1a83 (patch) | |
| tree | 0ad61666f906fcb26e05a3335ce3e6970815a2bb /docs/xlibdriver.html | |
| parent | 53f8b7190eaf84ba549c9d442b24ec0442fa610e (diff) | |
minor updates
Diffstat (limited to 'docs/xlibdriver.html')
| -rw-r--r-- | docs/xlibdriver.html | 11 |
1 files changed, 6 insertions, 5 deletions
diff --git a/docs/xlibdriver.html b/docs/xlibdriver.html index 7734542dcb9..6bb6532533b 100644 --- a/docs/xlibdriver.html +++ b/docs/xlibdriver.html @@ -22,7 +22,7 @@ software-only drivers. <p> Since the Xlib driver <em>emulates</em> the GLX extension, it's not -totally conformance with a true GLX implementation. +totally conformant with a true GLX implementation. The differences are fairly obscure, however. </p> @@ -31,7 +31,7 @@ The unique features of the Xlib driver follows. </p> -<H2>X Display Modes</H2> +<H2>X Visual Selection</H2> <p> Mesa supports RGB(A) rendering into almost any X visual type and depth. </p> @@ -68,7 +68,7 @@ Here are some examples: </pre> -<H2>Double buffering</H2> +<H2>Double Buffering</H2> <p> Mesa can use either an X Pixmap or XImage as the backbuffer when in double buffer mode. Using GLX, the default is to use an XImage. The @@ -107,7 +107,7 @@ significant. </p> -<H2>Gamma correction</H2> +<H2>Gamma Correction</H2> <p> To compensate for the nonlinear relationship between pixel values and displayed intensities, there is a gamma correction feature in @@ -171,11 +171,12 @@ SERVER_OVERLAY_VISUALS property: </pre> -<H2>HPCR glClear(GL_COLOR_BUFFER_BIT) dithering</H2> +<H2>HPCR Dithering</H2> <p> If you set the <b>MESA_HPCR_CLEAR</b> environment variable then dithering will be used when clearing the color buffer. This is only applicable to HP systems with the HPCR (Color Recovery) feature. +This incurs a small performance penalty. </p> |