xorg: Changes to 'xsf-docs'
xsf-docs/howtos/build-mesa.mdwn | 17 ++++++++++++++---
xsf-docs/howtos/configure-input.mdwn | 4 ++--
xsf-docs/howtos/use-gdb.mdwn | 2 +-
3 files changed, 17 insertions(+), 6 deletions(-)
New commits:
commit 662580ccf81ad9817346fa68f2b60458fbab2f56
Author: Cyril Brulebois <kibi@debian.org>
Date: Thu Feb 10 11:27:45 2011 +0100
Fix apostrophes.
diff --git a/xsf-docs/howtos/configure-input.mdwn b/xsf-docs/howtos/configure-input.mdwn
index e705d30..bd00f3e 100644
--- a/xsf-docs/howtos/configure-input.mdwn
+++ b/xsf-docs/howtos/configure-input.mdwn
@@ -104,7 +104,7 @@ Line by line walkthrough:
* To avoid specifying any device under `/dev/input` (`event$N` might
change, remember it’s about hotplug support!), we use an
`InputClass`.
- * We need an identifier, the actual name doesn‘t matter.
+ * We need an identifier, the actual name doesn’t matter.
* We match everything that looks like a touchpad. Meaning no generic
pointer, keyboard, or tablet.
* We specify the driver we want to use for the matched device(s).
@@ -144,7 +144,7 @@ Line by line walkthrough:
* To avoid specifying any device under `/dev/input` (`event$N` might
change, remember it’s about hotplug support!), we use an
`InputClass`.
- * We need an identifier, the actual name doesn‘t matter.
+ * We need an identifier, the actual name doesn’t matter.
* We match everything that looks like a touchpad. Meaning no generic
pointer, keyboard, or tablet.
* We specify the driver we want to use for the matched device(s).
diff --git a/xsf-docs/howtos/use-gdb.mdwn b/xsf-docs/howtos/use-gdb.mdwn
index 648c867..df7152d 100644
--- a/xsf-docs/howtos/use-gdb.mdwn
+++ b/xsf-docs/howtos/use-gdb.mdwn
@@ -15,7 +15,7 @@ with a single machine.
### One-machine approach
-From a console (let‘s assume it’s `vt1`), open a `root`
+From a console (let’s assume it’s `vt1`), open a `root`
terminal. Then, start a loop which will bring you back to this console
after a given delay (in the following example, every 60 seconds), just
in case. The ampersand (`&`) at the end makes it a background job.
commit 3ad130a6d78f2191a623f873ce84604a029c25d2
Author: Cyril Brulebois <kibi@debian.org>
Date: Thu Feb 10 11:25:42 2011 +0100
build-mesa: Add a note about nouveau.
diff --git a/xsf-docs/howtos/build-mesa.mdwn b/xsf-docs/howtos/build-mesa.mdwn
index 829c9cf..7dac557 100644
--- a/xsf-docs/howtos/build-mesa.mdwn
+++ b/xsf-docs/howtos/build-mesa.mdwn
@@ -25,6 +25,17 @@ 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.
+*Note:* Before reading further, be aware that `nouveau` is a bit
+ special.
+
+ * It’s considered experimental, and shipped in the
+ `libgl1-mesa-dri-experimental` package accordingly.
+ * It may fail to build (both API and ABI are still changing).
+ * We’re not shipping `nouveau_vieux_dri.so` yet (for cards from NV04
+ to NV2X; `nouveau_dri.so` is for NV30 and later). See the upstream
+ [FeatureMatrix](http://nouveau.freedesktop.org/wiki/FeatureMatrix)
+ page to determine a card’s series.
+
## Gathering information
@@ -94,9 +105,9 @@ 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`.]*
+drivers. If you’re using `nouveau`, make sure you read the note in the
+**Foreword**. The following assumes you’re using `nouveau_dri.so`.
+
Examples for common drivers:
Reply to: