X-Git-Url: https://git.libre-soc.org/?a=blobdiff_plain;f=docs%2Ffaq.html;h=4e79bb167f6553ae98dbaf1cf9f0230c3176b95b;hb=6a1cce20b605aee4f8787b6d5ad59ee25ac7550f;hp=97b6491a7bd2aaf6d47abc3810988221e9ae6445;hpb=5abb1f8bdee611b365fcd35f5a7adc9af9dc179f;p=mesa.git diff --git a/docs/faq.html b/docs/faq.html index 97b6491a7bd..4e79bb167f6 100644 --- a/docs/faq.html +++ b/docs/faq.html @@ -16,7 +16,7 @@
Yes. Specifically, Mesa serves as the OpenGL core for the open-source DRI -drivers for XFree86/X.org. See the DRI -website for more information. -
--There have been other hardware drivers for Mesa over the years (such as -the 3Dfx Glide/Voodoo driver, an old S3 driver, etc) but the DRI drivers -are the modern ones. +drivers for X.org.
+@@ -68,7 +72,7 @@ operating systems today. Still, Mesa serves at least these purposes:
Yes, SGI's -OpenGL Sample Implemenation (SI) is available. +OpenGL Sample Implementation (SI) is available. The SI was written during the time that OpenGL was originally designed. Unfortunately, development of the SI has stagnated. Mesa is much more up to date with modern features and extensions.
-Vincent is +Vincent is an open-source implementation of OpenGL ES for mobile devices.
@@ -148,12 +152,12 @@ an open-source implementation of OpenGL ES for mobile devices. is a subset of OpenGL for PalmOS devices.
@@ -232,15 +236,22 @@ Basically you'll want the following: Mesa version number.
-After installing XFree86/X.org and the DRI drivers, some of these files
-may be symlinks into the /usr/X11R6/ tree.
+When configuring Mesa, there are three autoconf options that affect the install
+location that you should take care with: --prefix
,
+--libdir
, and --with-dri-driverdir
. To install Mesa
+into the system location where it will be available for all programs to use, set
+--prefix=/usr
. Set --libdir
to where your Linux
+distribution installs system libraries, usually either /usr/lib
or
+/usr/lib64
. Set --with-dri-driverdir
to the directory
+where your Linux distribution installs DRI drivers. To find your system's DRI
+driver directory, try executing find /usr -type d -name dri
. For
+example, if the find
command listed /usr/lib64/dri
,
+then set --with-dri-driverdir=/usr/lib64/dri
.
-The old-style Makefile system doesn't install the Mesa libraries; it's -up to you to copy them (and the headers) to the right place. -
-
-The GLUT header and library should go in the same directories.
+After determining the correct values for the install location, configure Mesa
+with ./configure --prefix=/usr --libdir=xxx --with-dri-driverdir=xxx
+and then install with sudo make install
.
-Stand-alone Mesa (downloaded as MesaLib-x.y.z.tar.gz) doesn't have any -support for hardware acceleration (with the exception of the 3DFX Voodoo -driver). -
--What you really want is a DRI or NVIDIA (or another vendor's OpenGL) driver -for your particular hardware. +If Mesa can't use its hardware accelerated drivers it falls back on one of its software renderers. +(eg. classic swrast, softpipe or llvmpipe)
You can run the glxinfo
program to learn about your OpenGL
library.
-Look for the GL_VENDOR and GL_RENDERER values.
-That will identify who's OpenGL library you're using and what sort of
+Look for the OpenGL vendor
and OpenGL renderer
values.
+That will identify who's OpenGL library with which driver you're using and what sort of
hardware it has detected.
+If you're using a hardware accelerated driver you want direct rendering: Yes
.
+
If your DRI-based driver isn't working, go to the -DRI website for trouble-shooting information. +DRI website for trouble-shooting information.
@@ -318,19 +327,6 @@ Basically, applying a translation of (0.375, 0.375, 0.0) to your coordinates will fix the problem. --These can be overridden by using the --with-max-width and ---with-max-height options. The two need not be equal. -
-Do note that Mesa uses these values to size some internal buffers, -so increasing these sizes will cause Mesa to require additional -memory. Furthermore, increasing these limits beyond 4096 -may introduce rasterization artifacts; see the leading comments in -src/mesa/swrast/s_tritemp.h. -
-The -OpenGL Specification is the bible for OpenGL implemention work. +OpenGL Specification is the bible for OpenGL implementation work. You should read it.
Most of the Mesa development work involves implementing new OpenGL @@ -361,12 +357,12 @@ target hardware/operating system.
The best way to get started is to use an existing driver as your starting point. -For a software driver, the X11 and OSMesa drivers are good examples. -For a hardware driver, the Radeon and R200 DRI drivers are good examples. +For a classic hardware driver, the i965 driver is a good example. +For a Gallium3D hardware driver, the r300g, r600g and the i915g are good examples.
The DRI website has more information about writing hardware drivers. The process isn't well document because the Mesa driver interface changes -over time, and we seldome have spare time for writing documentation. +over time, and we seldom have spare time for writing documentation. That being said, many people have managed to figure out the process.