xorg: Changes to 'xsf-docs'
xsf-docs/howtos/build-mesa.mdwn | 184 +++++++++++++++++++++++++++++++++++++++
xsf-docs/howtos/report-bugs.mdwn | 7 +
xsf-docs/index.mdwn | 1
xsf-docs/xsf.css | 12 ++
4 files changed, 201 insertions(+), 3 deletions(-)
New commits:
commit 796951486a245084068fc4ee910054948922e9c7
Author: Cyril Brulebois <kibi@debian.org>
Date: Thu Feb 10 01:04:34 2011 +0100
index: Link to build-mesa.
diff --git a/xsf-docs/index.mdwn b/xsf-docs/index.mdwn
index f9dcfcb..75fc2d1 100644
--- a/xsf-docs/index.mdwn
+++ b/xsf-docs/index.mdwn
@@ -14,6 +14,7 @@ metapackage (under `/usr/share/doc/xorg`), starting with `wheezy`.
* [How to use GDB](howtos/use-gdb.html)
* [How to configure input](howtos/configure-input.html)
* [How to configure outputs](howtos/use-xrandr.html)
+ * [How to build mesa locally](howtos/build-mesa.html)
## Reference documentation
commit 3cf5eec54f92eec79834acb3553a64b956746f91
Author: Cyril Brulebois <kibi@debian.org>
Date: Thu Feb 10 01:03:02 2011 +0100
build-mesa: The end (hopefully).
diff --git a/xsf-docs/howtos/build-mesa.mdwn b/xsf-docs/howtos/build-mesa.mdwn
index 76a8aa4..829c9cf 100644
--- a/xsf-docs/howtos/build-mesa.mdwn
+++ b/xsf-docs/howtos/build-mesa.mdwn
@@ -177,3 +177,8 @@ are used.
libEGL debug: DRI2: dlopen(lib/i915_dri.so)
↪ Yes: No system directory, paths are relative to `lib/`.
+
+
+### The end.
+
+Now you should be ready to test upstream’s suggestions!
commit 1400b5a6a5fd5e9be514ef1563c68b2663582dd4
Author: Cyril Brulebois <kibi@debian.org>
Date: Thu Feb 10 00:50:51 2011 +0100
build-mesa: Mention the lack of EGL-aware applications.
diff --git a/xsf-docs/howtos/build-mesa.mdwn b/xsf-docs/howtos/build-mesa.mdwn
index c7cf609..76a8aa4 100644
--- a/xsf-docs/howtos/build-mesa.mdwn
+++ b/xsf-docs/howtos/build-mesa.mdwn
@@ -168,8 +168,8 @@ are used.
*Did this work?*
- **FIXME:** Is there any EGL test application? If so, running the
- following should do:
+ **FIXME: We should be shipping EGL-aware applications through
+ `mesa-utils`.**
$ EGL_LOG_LEVEL=debug test_application 2>&1 >/dev/null | grep '\.so'
libEGL debug: added lib/egl/egl_gallium.so to module array
commit c1c85b15ff3c0b5a0c4778c1071ef6630f58c1dd
Author: Cyril Brulebois <kibi@debian.org>
Date: Thu Feb 10 00:48:21 2011 +0100
build-mesa: rename from debug-mesa.
It's mostly about building, not really debugging.
diff --git a/xsf-docs/howtos/build-mesa.mdwn b/xsf-docs/howtos/build-mesa.mdwn
new file mode 100644
index 0000000..c7cf609
--- /dev/null
+++ b/xsf-docs/howtos/build-mesa.mdwn
@@ -0,0 +1,179 @@
+# How to build mesa
+
+Cyril Brulebois <kibi@debian.org>
+
+
+## Foreword
+
+Mesa is a special package since many flavours are built, which means
+it takes quite some time to get all packages ready, as well as some
+disc space (over 2GB for the `build/` directory alone).
+
+Also, trying to figure out whether latest `master` is also affected,
+or backporting some bug fixes might lead to some painful I/O while
+generating the `.deb` files, and then installing/unpacking them. This
+is why this document was written: Helping users test other mesa
+releases, branches, bug fixes without having to build full packages,
+and without having to mess with their systems (*i.e.* no root access
+is needed once the build dependencies are installed).
+
+We’ll focus on the DRI (Direct Rendering Infrastructure) flavour
+(`libgl1-mesa-dri`), which is the most common.
+
+It might be possible to adapt the following steps to another flavour,
+in which case the appropriate options to be passed to `./configure`
+should be looked up in the `debian/rules` file of the Debian source
+package.
+
+
+## Gathering information
+
+Get started by installing `mesa-utils`, which contains `glxinfo`.
+
+ * *Is direct rendering enabled?*
+
+ $ glxinfo | grep ^direct
+ direct rendering: Yes
+
+ ↪ Yes.
+
+ * *Is this the classic or
+ [Gallium](http://en.wikipedia.org/wiki/Gallium3D) driver?*
+
+ $ glxinfo | grep 'renderer string'
+ OpenGL renderer string: Mesa DRI Intel(R) 945GM GEM 20100330 DEVELOPMENT
+
+ ↪ No “Gallium” here, therefore: “classic”.
+
+ * *Which driver is this, and where is it located?*
+
+ $ LIBGL_DEBUG=verbose glxinfo 2>&1 >/dev/null | grep so$
+ libGL: OpenDriver: trying /usr/lib/dri/tls/i915_dri.so
+ libGL: OpenDriver: trying /usr/lib/dri/i915_dri.so
+
+ ↪ `i915`, from the system directory: `/usr/lib/dri` (likely
+ installed through a Debian package).
+
+ * *How can I get more debugging information?*
+
+ export LIBGL_DEBUG=verbose
+ export MESA_DEBUG=1
+ export EGL_LOG_LEVEL=debug
+
+
+## Preparing mesa sources
+
+To get started, installing all build dependencies of the `mesa` source
+package should be sufficient, along with the essential build tools,
+and `git`:
+
+ $ sudo apt-get install build-essential git
+ $ sudo apt-get build-dep mesa
+
+Grab the upstream mesa sources:
+
+ $ git clone git://anongit.freedesktop.org/mesa/mesa mesa.git
+ $ cd mesa.git
+ $ autoreconf -vfi
+
+Here’s what the `./configure` call will look like:
+
+ $ ./configure --enable-driglx-direct \
+ --enable-gallium \
+ --enable-gles-overlay \
+ --enable-gles1 \
+ --enable-gles2 \
+ --enable-glx-tls \
+ --with-driver=dri \
+ --with-dri-driverdir=/usr/lib/dri \
+ --with-egl-platforms='drm x11' \
+ --with-state-trackers=egl,glx,dri,vega \
+ …
+
+Now, what are the parameters to replace “`…`” with? Basically, if
+you determined an Intel driver (`i915` or `i965`), you want to use the
+classic drivers and to disable the Gallium drivers. If you saw a
+Radeon driver (`r300` or `r600`), you should prefer the Gallium
+drivers. *[Note: Nouveau is a bit special since it may fail to build
+(both API and ABI are still changing), and since we’re currently not
+shipping `nouveau_vieux.so`.]*
+
+Examples for common drivers:
+
+ * For `i915`, you need:
+
+ --with-dri-drivers=i915
+
+ * For `i965`, you need:
+
+ --with-dri-drivers=i965
+
+ * For `nouveau`, you may want to try:
+
+ --with-dri-drivers=nouveau --enable-gallium-nouveau
+
+ * For `r300` (the options are named `radeon`), you need:
+
+ --with-dri-drivers=radeon --enable-gallium-radeon
+
+ * For `r600`, you need:
+
+ --with-dri-drivers=r600 --enable-gallium-r600
+
+Now, once you’ve run `./configure`, time for your favorite beverage:
+
+ $ make
+
+
+## Running the newly-built mesa libraries
+
+Shared libraries end up in the `lib/` directory. It contains the
+classic drivers, while Gallium drivers end up under `lib/gallium`. If
+you’re not an Intel user, overwrite the classic drivers with the
+Gallium ones:
+
+ $ mv lib/gallium/* lib/
+
+Now, 3 variables need to be set, so that the locally-built libraries
+are used.
+
+ * To begin with, libGL itself and its drivers:
+
+ $ export LIBGL_DRIVERS_PATH=lib
+
+ *Did this work?*
+
+ $ LIBGL_DEBUG=verbose glxinfo 2>&1 >/dev/null | grep so$
+ libGL: OpenDriver: trying lib/tls/i915_dri.so
+ libGL: OpenDriver: trying lib/i915_dri.so
+
+ ↪ Yes: No system directory, paths are relative to `lib/`.
+
+ * Set `LD_LIBRARY_PATH` to make sure the locally-built libraries
+ (including those pulled through library dependencies) are used,
+ instead of system ones:
+
+ $ export LD_LIBRARY_PATH=lib
+
+ *Did this work?*
+
+ $ ldd lib/libGLESv2.so | grep glapi
+ libglapi.so.0 => lib/libglapi.so.0 (0x00007fee3192e000)
+
+ ↪ Yes: Path is relative to `lib`.
+
+ * Set the EGL search path:
+
+ $ export EGL_DRIVERS_PATH=lib/egl
+
+ *Did this work?*
+
+ **FIXME:** Is there any EGL test application? If so, running the
+ following should do:
+
+ $ EGL_LOG_LEVEL=debug test_application 2>&1 >/dev/null | grep '\.so'
+ libEGL debug: added lib/egl/egl_gallium.so to module array
+ libEGL debug: dlopen(lib/egl/egl_gallium.so)
+ libEGL debug: DRI2: dlopen(lib/i915_dri.so)
+
+ ↪ Yes: No system directory, paths are relative to `lib/`.
diff --git a/xsf-docs/howtos/debug-mesa.mdwn b/xsf-docs/howtos/debug-mesa.mdwn
deleted file mode 100644
index 6f46d79..0000000
--- a/xsf-docs/howtos/debug-mesa.mdwn
+++ /dev/null
@@ -1,179 +0,0 @@
-# How to debug mesa
-
-Cyril Brulebois <kibi@debian.org>
-
-
-## Foreword
-
-Mesa is a special package since many flavours are built, which means
-it takes quite some time to get all packages ready, as well as some
-disc space (over 2GB for the `build/` directory alone).
-
-Also, trying to figure out whether latest `master` is also affected,
-or backporting some bug fixes might lead to some painful I/O while
-generating the `.deb` files, and then installing/unpacking them. This
-is why this document was written: Helping users test other mesa
-releases, branches, bug fixes without having to build full packages,
-and without having to mess with their systems (*i.e.* no root access
-is needed once the build dependencies are installed).
-
-We’ll focus on the DRI (Direct Rendering Infrastructure) flavour
-(`libgl1-mesa-dri`), which is the most common.
-
-It might be possible to adapt the following steps to another flavour,
-in which case the appropriate options to be passed to `./configure`
-should be looked up in the `debian/rules` file of the Debian source
-package.
-
-
-## Gathering information
-
-Get started by installing `mesa-utils`, which contains `glxinfo`.
-
- * *Is direct rendering enabled?*
-
- $ glxinfo | grep ^direct
- direct rendering: Yes
-
- ↪ Yes.
-
- * *Is this the classic or
- [Gallium](http://en.wikipedia.org/wiki/Gallium3D) driver?*
-
- $ glxinfo | grep 'renderer string'
- OpenGL renderer string: Mesa DRI Intel(R) 945GM GEM 20100330 DEVELOPMENT
-
- ↪ No “Gallium” here, therefore: “classic”.
-
- * *Which driver is this, and where is it located?*
-
- $ LIBGL_DEBUG=verbose glxinfo 2>&1 >/dev/null | grep so$
- libGL: OpenDriver: trying /usr/lib/dri/tls/i915_dri.so
- libGL: OpenDriver: trying /usr/lib/dri/i915_dri.so
-
- ↪ `i915`, from the system directory: `/usr/lib/dri` (likely
- installed through a Debian package).
-
- * *How can I get more debugging information?*
-
- export LIBGL_DEBUG=verbose
- export MESA_DEBUG=1
- export EGL_LOG_LEVEL=debug
-
-
-## Preparing mesa sources
-
-To get started, installing all build dependencies of the `mesa` source
-package should be sufficient, along with the essential build tools,
-and `git`:
-
- $ sudo apt-get install build-essential git
- $ sudo apt-get build-dep mesa
-
-Grab the upstream mesa sources:
-
- $ git clone git://anongit.freedesktop.org/mesa/mesa mesa.git
- $ cd mesa.git
- $ autoreconf -vfi
-
-Here’s what the `./configure` call will look like:
-
- $ ./configure --enable-driglx-direct \
- --enable-gallium \
- --enable-gles-overlay \
- --enable-gles1 \
- --enable-gles2 \
- --enable-glx-tls \
- --with-driver=dri \
- --with-dri-driverdir=/usr/lib/dri \
- --with-egl-platforms='drm x11' \
- --with-state-trackers=egl,glx,dri,vega \
- …
-
-Now, what are the parameters to replace “`…`” with? Basically, if
-you determined an Intel driver (`i915` or `i965`), you want to use the
-classic drivers and to disable the Gallium drivers. If you saw a
-Radeon driver (`r300` or `r600`), you should prefer the Gallium
-drivers. *[Note: Nouveau is a bit special since it may fail to build
-(both API and ABI are still changing), and since we’re currently not
-shipping `nouveau_vieux.so`.]*
-
-Examples for common drivers:
-
- * For `i915`, you need:
-
- --with-dri-drivers=i915
-
- * For `i965`, you need:
-
- --with-dri-drivers=i965
-
- * For `nouveau`, you may want to try:
-
- --with-dri-drivers=nouveau --enable-gallium-nouveau
-
- * For `r300` (the options are named `radeon`), you need:
-
- --with-dri-drivers=radeon --enable-gallium-radeon
-
- * For `r600`, you need:
-
- --with-dri-drivers=r600 --enable-gallium-r600
-
-Now, once you’ve run `./configure`, time for your favorite beverage:
-
- $ make
-
-
-## Running the newly-built mesa libraries
-
-Shared libraries end up in the `lib/` directory. It contains the
-classic drivers, while Gallium drivers end up under `lib/gallium`. If
-you’re not an Intel user, overwrite the classic drivers with the
-Gallium ones:
-
- $ mv lib/gallium/* lib/
-
-Now, 3 variables need to be set, so that the locally-built libraries
-are used.
-
- * To begin with, libGL itself and its drivers:
-
- $ export LIBGL_DRIVERS_PATH=lib
-
- *Did this work?*
-
- $ LIBGL_DEBUG=verbose glxinfo 2>&1 >/dev/null | grep so$
- libGL: OpenDriver: trying lib/tls/i915_dri.so
- libGL: OpenDriver: trying lib/i915_dri.so
-
- ↪ Yes: No system directory, paths are relative to `lib/`.
-
- * Set `LD_LIBRARY_PATH` to make sure the locally-built libraries
- (including those pulled through library dependencies) are used,
- instead of system ones:
-
- $ export LD_LIBRARY_PATH=lib
-
- *Did this work?*
-
- $ ldd lib/libGLESv2.so | grep glapi
- libglapi.so.0 => lib/libglapi.so.0 (0x00007fee3192e000)
-
- ↪ Yes: Path is relative to `lib`.
-
- * Set the EGL search path:
-
- $ export EGL_DRIVERS_PATH=lib/egl
-
- *Did this work?*
-
- **FIXME:** Is there any EGL test application? If so, running the
- following should do:
-
- $ EGL_LOG_LEVEL=debug test_application 2>&1 >/dev/null | grep '\.so'
- libEGL debug: added lib/egl/egl_gallium.so to module array
- libEGL debug: dlopen(lib/egl/egl_gallium.so)
- libEGL debug: DRI2: dlopen(lib/i915_dri.so)
-
- ↪ Yes: No system directory, paths are relative to `lib/`.
commit a5e23323c196e3acdfcc782fc30a61bb1ef297c1
Author: Cyril Brulebois <kibi@debian.org>
Date: Thu Feb 10 00:47:27 2011 +0100
debug-mesa: Some review.
diff --git a/xsf-docs/howtos/debug-mesa.mdwn b/xsf-docs/howtos/debug-mesa.mdwn
index 60eb594..6f46d79 100644
--- a/xsf-docs/howtos/debug-mesa.mdwn
+++ b/xsf-docs/howtos/debug-mesa.mdwn
@@ -14,8 +14,8 @@ or backporting some bug fixes might lead to some painful I/O while
generating the `.deb` files, and then installing/unpacking them. This
is why this document was written: Helping users test other mesa
releases, branches, bug fixes without having to build full packages,
-and without having to mess with their systems (*i.e.* you won’t need
-root access).
+and without having to mess with their systems (*i.e.* no root access
+is needed once the build dependencies are installed).
We’ll focus on the DRI (Direct Rendering Infrastructure) flavour
(`libgl1-mesa-dri`), which is the most common.
@@ -51,7 +51,8 @@ Get started by installing `mesa-utils`, which contains `glxinfo`.
libGL: OpenDriver: trying /usr/lib/dri/tls/i915_dri.so
libGL: OpenDriver: trying /usr/lib/dri/i915_dri.so
- ↪ `i915`
+ ↪ `i915`, from the system directory: `/usr/lib/dri` (likely
+ installed through a Debian package).
* *How can I get more debugging information?*
@@ -75,7 +76,7 @@ Grab the upstream mesa sources:
$ cd mesa.git
$ autoreconf -vfi
-Here’s how `./configure` arguments will look like:
+Here’s what the `./configure` call will look like:
$ ./configure --enable-driglx-direct \
--enable-gallium \
@@ -89,7 +90,7 @@ Here’s how `./configure` arguments will look like:
--with-state-trackers=egl,glx,dri,vega \
…
-Now, what are the last options to replace “`…`” with? Basically, if
+Now, what are the parameters to replace “`…`” with? Basically, if
you determined an Intel driver (`i915` or `i965`), you want to use the
classic drivers and to disable the Gallium drivers. If you saw a
Radeon driver (`r300` or `r600`), you should prefer the Gallium
@@ -126,10 +127,10 @@ Now, once you’ve run `./configure`, time for your favorite beverage:
## Running the newly-built mesa libraries
-Shared libraries end up in the `lib/` directory. The top-level
-contains the classic drivers, while Gallium drivers end up under
-`lib/gallium`. If you’re not an Intel user, overwrite the classic
-drivers with the Gallium ones:
+Shared libraries end up in the `lib/` directory. It contains the
+classic drivers, while Gallium drivers end up under `lib/gallium`. If
+you’re not an Intel user, overwrite the classic drivers with the
+Gallium ones:
$ mv lib/gallium/* lib/
@@ -150,7 +151,7 @@ are used.
* Set `LD_LIBRARY_PATH` to make sure the locally-built libraries
(including those pulled through library dependencies) are used,
- instead of system-wide ones:
+ instead of system ones:
$ export LD_LIBRARY_PATH=lib
commit d94af202090ab8ea8f66f299b6c83aaefa770ff2
Author: Cyril Brulebois <kibi@debian.org>
Date: Thu Feb 10 00:19:49 2011 +0100
debug-mesa: More or less ready for a review.
diff --git a/xsf-docs/howtos/debug-mesa.mdwn b/xsf-docs/howtos/debug-mesa.mdwn
index 7069365..60eb594 100644
--- a/xsf-docs/howtos/debug-mesa.mdwn
+++ b/xsf-docs/howtos/debug-mesa.mdwn
@@ -3,9 +3,32 @@
Cyril Brulebois <kibi@debian.org>
+## Foreword
+
+Mesa is a special package since many flavours are built, which means
+it takes quite some time to get all packages ready, as well as some
+disc space (over 2GB for the `build/` directory alone).
+
+Also, trying to figure out whether latest `master` is also affected,
+or backporting some bug fixes might lead to some painful I/O while
+generating the `.deb` files, and then installing/unpacking them. This
+is why this document was written: Helping users test other mesa
+releases, branches, bug fixes without having to build full packages,
+and without having to mess with their systems (*i.e.* you won’t need
+root access).
+
+We’ll focus on the DRI (Direct Rendering Infrastructure) flavour
+(`libgl1-mesa-dri`), which is the most common.
+
+It might be possible to adapt the following steps to another flavour,
+in which case the appropriate options to be passed to `./configure`
+should be looked up in the `debian/rules` file of the Debian source
+package.
+
+
## Gathering information
-Install `mesa-utils`, which contains `glxinfo`.
+Get started by installing `mesa-utils`, which contains `glxinfo`.
* *Is direct rendering enabled?*
@@ -22,7 +45,7 @@ Install `mesa-utils`, which contains `glxinfo`.
↪ No “Gallium” here, therefore: “classic”.
- * *Which driver is this?*
+ * *Which driver is this, and where is it located?*
$ LIBGL_DEBUG=verbose glxinfo 2>&1 >/dev/null | grep so$
libGL: OpenDriver: trying /usr/lib/dri/tls/i915_dri.so
@@ -66,22 +89,90 @@ Here’s how `./configure` arguments will look like:
--with-state-trackers=egl,glx,dri,vega \
…
-Now, what are the last options to replace the `…` with? Basically, if
+Now, what are the last options to replace “`…`” with? Basically, if
you determined an Intel driver (`i915` or `i965`), you want to use the
classic drivers and to disable the Gallium drivers. If you saw a
Radeon driver (`r300` or `r600`), you should prefer the Gallium
-drivers.
+drivers. *[Note: Nouveau is a bit special since it may fail to build
+(both API and ABI are still changing), and since we’re currently not
+shipping `nouveau_vieux.so`.]*
-Examples:
+Examples for common drivers:
- * For `i915`, you need to add:
+ * For `i915`, you need:
--with-dri-drivers=i915
- * For `r300`, the options are named `radeon`. You need:
+ * For `i965`, you need:
+
+ --with-dri-drivers=i965
+
+ * For `nouveau`, you may want to try:
+
+ --with-dri-drivers=nouveau --enable-gallium-nouveau
+
+ * For `r300` (the options are named `radeon`), you need:
--with-dri-drivers=radeon --enable-gallium-radeon
* For `r600`, you need:
--with-dri-drivers=r600 --enable-gallium-r600
+
+Now, once you’ve run `./configure`, time for your favorite beverage:
+
+ $ make
+
+
+## Running the newly-built mesa libraries
+
+Shared libraries end up in the `lib/` directory. The top-level
+contains the classic drivers, while Gallium drivers end up under
+`lib/gallium`. If you’re not an Intel user, overwrite the classic
+drivers with the Gallium ones:
+
+ $ mv lib/gallium/* lib/
+
+Now, 3 variables need to be set, so that the locally-built libraries
+are used.
+
+ * To begin with, libGL itself and its drivers:
+
+ $ export LIBGL_DRIVERS_PATH=lib
+
+ *Did this work?*
+
+ $ LIBGL_DEBUG=verbose glxinfo 2>&1 >/dev/null | grep so$
+ libGL: OpenDriver: trying lib/tls/i915_dri.so
+ libGL: OpenDriver: trying lib/i915_dri.so
+
+ ↪ Yes: No system directory, paths are relative to `lib/`.
+
+ * Set `LD_LIBRARY_PATH` to make sure the locally-built libraries
+ (including those pulled through library dependencies) are used,
+ instead of system-wide ones:
+
+ $ export LD_LIBRARY_PATH=lib
+
+ *Did this work?*
+
+ $ ldd lib/libGLESv2.so | grep glapi
+ libglapi.so.0 => lib/libglapi.so.0 (0x00007fee3192e000)
+
+ ↪ Yes: Path is relative to `lib`.
+
+ * Set the EGL search path:
+
+ $ export EGL_DRIVERS_PATH=lib/egl
+
+ *Did this work?*
+
+ **FIXME:** Is there any EGL test application? If so, running the
+ following should do:
+
+ $ EGL_LOG_LEVEL=debug test_application 2>&1 >/dev/null | grep '\.so'
+ libEGL debug: added lib/egl/egl_gallium.so to module array
+ libEGL debug: dlopen(lib/egl/egl_gallium.so)
+ libEGL debug: DRI2: dlopen(lib/i915_dri.so)
+
+ ↪ Yes: No system directory, paths are relative to `lib/`.
commit a7c026139ce868d36d5b3827bfb6056beba62a1d
Author: Cyril Brulebois <kibi@debian.org>
Date: Wed Feb 9 23:20:39 2011 +0100
debug-mesa: New how-to.
diff --git a/xsf-docs/howtos/debug-mesa.mdwn b/xsf-docs/howtos/debug-mesa.mdwn
new file mode 100644
index 0000000..7069365
--- /dev/null
+++ b/xsf-docs/howtos/debug-mesa.mdwn
@@ -0,0 +1,87 @@
+# How to debug mesa
+
+Cyril Brulebois <kibi@debian.org>
+
+
+## Gathering information
+
+Install `mesa-utils`, which contains `glxinfo`.
+
+ * *Is direct rendering enabled?*
+
+ $ glxinfo | grep ^direct
+ direct rendering: Yes
+
+ ↪ Yes.
+
+ * *Is this the classic or
+ [Gallium](http://en.wikipedia.org/wiki/Gallium3D) driver?*
+
+ $ glxinfo | grep 'renderer string'
+ OpenGL renderer string: Mesa DRI Intel(R) 945GM GEM 20100330 DEVELOPMENT
+
+ ↪ No “Gallium” here, therefore: “classic”.
+
+ * *Which driver is this?*
+
+ $ LIBGL_DEBUG=verbose glxinfo 2>&1 >/dev/null | grep so$
+ libGL: OpenDriver: trying /usr/lib/dri/tls/i915_dri.so
+ libGL: OpenDriver: trying /usr/lib/dri/i915_dri.so
+
+ ↪ `i915`
+
+ * *How can I get more debugging information?*
+
+ export LIBGL_DEBUG=verbose
+ export MESA_DEBUG=1
+ export EGL_LOG_LEVEL=debug
+
+
+## Preparing mesa sources
+
+To get started, installing all build dependencies of the `mesa` source
+package should be sufficient, along with the essential build tools,
+and `git`:
+
+ $ sudo apt-get install build-essential git
+ $ sudo apt-get build-dep mesa
+
+Grab the upstream mesa sources:
+
+ $ git clone git://anongit.freedesktop.org/mesa/mesa mesa.git
+ $ cd mesa.git
+ $ autoreconf -vfi
+
+Here’s how `./configure` arguments will look like:
+
+ $ ./configure --enable-driglx-direct \
+ --enable-gallium \
+ --enable-gles-overlay \
+ --enable-gles1 \
+ --enable-gles2 \
+ --enable-glx-tls \
+ --with-driver=dri \
+ --with-dri-driverdir=/usr/lib/dri \
+ --with-egl-platforms='drm x11' \
+ --with-state-trackers=egl,glx,dri,vega \
+ …
+
+Now, what are the last options to replace the `…` with? Basically, if
+you determined an Intel driver (`i915` or `i965`), you want to use the
+classic drivers and to disable the Gallium drivers. If you saw a
+Radeon driver (`r300` or `r600`), you should prefer the Gallium
+drivers.
+
+Examples:
+
+ * For `i915`, you need to add:
+
+ --with-dri-drivers=i915
+
+ * For `r300`, the options are named `radeon`. You need:
+
+ --with-dri-drivers=radeon --enable-gallium-radeon
+
+ * For `r600`, you need:
+
+ --with-dri-drivers=r600 --enable-gallium-r600
commit 3f994f975fa72eb4642e8d02bdd086d566a479c2
Author: Cyril Brulebois <kibi@debian.org>
Date: Wed Feb 9 20:03:49 2011 +0100
css: Avoid too much margin within lists.
diff --git a/xsf-docs/xsf.css b/xsf-docs/xsf.css
index 0f30cef..9b4b6d2 100644
--- a/xsf-docs/xsf.css
+++ b/xsf-docs/xsf.css
@@ -47,6 +47,14 @@ p {
text-align: justify;
}
+/* Avoid too much margin within lists. */
+li p {
+ margin-left: 0px;
+}
+li pre {
+ margin-left: 0px;
+}
+
ul {
margin-left: 40px;
margin-right: 40px;
commit 842a60c7a074bd3444c905ca849f81d42d6893bc
Author: Cyril Brulebois <kibi@debian.org>
Date: Wed Feb 9 19:02:47 2011 +0100
css: Try and improve readability.
diff --git a/xsf-docs/xsf.css b/xsf-docs/xsf.css
index 5c070c4..0f30cef 100644
--- a/xsf-docs/xsf.css
+++ b/xsf-docs/xsf.css
@@ -70,11 +70,11 @@ pre {
code {
color: darkred;
- font-weight: bold;
+ font-size: 90%;
}
code, pre {
- font-family: FreeMono;
+ font-family: Mono;
}
/* Assume it's the author(s) paragraph */
commit f600e14b75807cc5827dfde3957a722173a36abc
Author: Cyril Brulebois <kibi@debian.org>
Date: Wed Feb 9 16:32:40 2011 +0100
report-bugs: xorg/xserver-xorg might be missing.
diff --git a/xsf-docs/howtos/report-bugs.mdwn b/xsf-docs/howtos/report-bugs.mdwn
index 03cc13b..6fc7140 100644
--- a/xsf-docs/howtos/report-bugs.mdwn
+++ b/xsf-docs/howtos/report-bugs.mdwn
@@ -17,6 +17,11 @@ this package triggers a bug script which is going to collect X-related
information, be it installed packages, running kernel, X
configuration, X log, and so on.
+Note: In case this metapackage wasn’t used to install your X stack,
+report a bug against `xserver-xorg` instead. And if that one isn’t
+installed either, go for `xserver-xorg-core`.
+
+
### Follow-up with more info
If you reported a bug against another package and if that bug was
@@ -24,7 +29,7 @@ reassigned to an X-related package, we might need more
information. You can run the bug script manually and attach its output
to your mail to the bug report:
- /usr/share/bug/xorg/script 3>/tmp/script.log
+ /usr/share/bug/xserver-xorg-core/script 3>/tmp/script.log
Note: Make sure there’s no space between `3` and `>`, that’s a shell
redirection.
Reply to: