From 205f960e08d7b13ea529782e0e744c657bf1771f Mon Sep 17 00:00:00 2001 From: Erik Faye-Lund Date: Thu, 6 Jun 2019 10:16:36 +0200 Subject: [PATCH] docs: add missing code-tags Looks like I missed a few cases when I recently added more code-tags here. So let's add these cases as well. Signed-off-by: Erik Faye-Lund Reviewed-by: Eric Engestrom --- docs/devinfo.html | 12 +++++++----- docs/envvars.html | 29 +++++++++++++++-------------- docs/faq.html | 15 ++++++++------- 3 files changed, 30 insertions(+), 26 deletions(-) diff --git a/docs/devinfo.html b/docs/devinfo.html index a636e37..0f1d5ac 100644 --- a/docs/devinfo.html +++ b/docs/devinfo.html @@ -60,8 +60,9 @@ To add a new GL extension to Mesa you have to do at least the following. as an example.
  • - If the new extension adds new GL state, the functions in get.c, enable.c - and attrib.c will most likely require new code. + If the new extension adds new GL state, the functions in + get.c, enable.c and attrib.c + will most likely require new code.
  • To determine if the new extension is active in the current context, @@ -69,9 +70,10 @@ To add a new GL extension to Mesa you have to do at least the following. defined in src/mesa/main/extensions.h.
  • - The dispatch tests check_table.cpp and dispatch_sanity.cpp - should be updated with details about the new extensions functions. These - tests are run using meson test. + The dispatch tests check_table.cpp and + dispatch_sanity.cpp should be updated with details about + the new extensions functions. These tests are run using + meson test.
    • diff --git a/docs/envvars.html b/docs/envvars.html index c41820b..ce3be81 100644 --- a/docs/envvars.html +++ b/docs/envvars.html @@ -133,13 +133,14 @@ sometimes be useful for debugging end-user issues.
    3.0FC
    select a Core+Forward Compatible profile with GL version 3.0.
    3.1
    -
    select GL version 3.1 with GL_ARB_compatibility enabled per the - driver default.
    +
    select GL version 3.1 with GL_ARB_compatibility + enabled per the driver default.
    3.1FC
    select GL version 3.1 with forward compatibility and - GL_ARB_compatibility disabled.
    + GL_ARB_compatibility disabled.
    3.1COMPAT
    -
    select GL version 3.1 with GL_ARB_compatibility enabled.
    +
    select GL version 3.1 with GL_ARB_compatibility + enabled.
    X.Y
    override GL version to X.Y without changing the profile.
    X.YFC
    @@ -164,9 +165,9 @@ sometimes be useful for debugging end-user issues.
    MESA_GLSL_VERSION_OVERRIDE
    changes the value returned by glGetString(GL_SHADING_LANGUAGE_VERSION). - Valid values are integers, such as "130". Mesa will not really implement - all the features of the given language version if it's higher than what's - normally reported. (for developers only) + Valid values are integers, such as 130. Mesa will not + really implement all the features of the given language version if + it's higher than what's normally reported. (for developers only)
    MESA_GLSL_CACHE_DISABLE
    if set to true, disables the GLSL shader cache
    @@ -362,8 +363,8 @@ Mesa EGL supports different sets of environment variables. See the
    GALLIUM_HUD
    draws various information on the screen, like framerate, cpu load, driver statistics, performance counters, etc. - Set GALLIUM_HUD=help and run e.g. glxgears for more - info.
    + Set GALLIUM_HUD=help and run e.g. + glxgears for more info.
    GALLIUM_HUD_PERIOD
    sets the hud update rate in seconds (float). Use zero to update every frame. The default period is 1/2 second.
    @@ -467,12 +468,12 @@ Mesa EGL supports different sets of environment variables. See the
    for dumping shaders, constant buffers, etc. See the code for details.
    SVGA_EXTRA_LOGGING
    -
    if set, enables extra logging to the vmware.log file, such as the - OpenGL program's name and command line arguments.
    +
    if set, enables extra logging to the vmware.log file, + such as the OpenGL program's name and command line arguments.
    SVGA_NO_LOGGING
    -
    if set, disables logging to the vmware.log file. This is useful when - using Valgrind because it otherwise crashes when initializing the host - log feature.
    +
    if set, disables logging to the vmware.log file. This is + useful when using Valgrind because it otherwise crashes when + initializing the host log feature.

    See the driver code for other, lesser-used variables.

    diff --git a/docs/faq.html b/docs/faq.html index 67eda94..00c17ea 100644 --- a/docs/faq.html +++ b/docs/faq.html @@ -96,17 +96,17 @@ the Xlib API:
  • The GLX wire protocol is not supported and there's no OpenGL extension loaded by the X server.
  • There is no hardware acceleration. -
  • The OpenGL library, libGL.so, contains everything (the programming API, - the GLX functions and all the rendering code). +
  • The OpenGL library, libGL.so, contains everything (the + programming API, the GLX functions and all the rendering code).

    Alternately, Mesa acts as the core for a number of OpenGL hardware drivers within the DRI (Direct Rendering Infrastructure):

      -
    • The libGL.so library provides the GL and GLX API functions, a GLX - protocol encoder, and a device driver loader. -
    • The device driver modules (such as r200_dri.so) contain a built-in - copy of the core Mesa code. +
    • The libGL.so library provides the GL and GLX API functions, + a GLX protocol encoder, and a device driver loader. +
    • The device driver modules (such as r200_dri.so) contain + a built-in copy of the core Mesa code.
    • The X server loads the GLX module. The GLX module decodes incoming GLX protocol and dispatches the commands to a rendering module. @@ -189,7 +189,8 @@ Mesa's not the solution.

      2.3 Where is the GLUT library?

      -GLUT (OpenGL Utility Toolkit) is no longer in the separate MesaGLUT-x.y.z.tar.gz file. +GLUT (OpenGL Utility Toolkit) is no longer in the separate +MesaGLUT-x.y.z.tar.gz file. If you don't already have GLUT installed, you should grab freeglut.

      -- 2.7.4