From: "Sven Vermeulen" <swift@lark.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: dri-howto.xml
Date: Wed, 13 Jul 2005 12:57:52 +0000 [thread overview]
Message-ID: <200507131257.j6DCv3aC002516@robin.gentoo.org> (raw)
swift 05/07/13 12:57:52
Modified: xml/htdocs/doc/en dri-howto.xml
Log:
#98034 - Use the insecure-drivers USE flag for certain kinds of chipsets
Revision Changes Path
1.22 +19 -3 xml/htdocs/doc/en/dri-howto.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/dri-howto.xml?rev=1.22&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/dri-howto.xml?rev=1.22&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/dri-howto.xml.diff?r1=1.21&r2=1.22&cvsroot=gentoo
Index: dri-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/dri-howto.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- dri-howto.xml 6 Apr 2005 09:39:59 -0000 1.21
+++ dri-howto.xml 13 Jul 2005 12:57:52 -0000 1.22
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/dri-howto.xml,v 1.21 2005/04/06 09:39:59 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/dri-howto.xml,v 1.22 2005/07/13 12:57:52 swift Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/dri-howto.xml">
@@ -18,8 +18,8 @@
<license/>
-<version>1.0.9</version>
-<date>2005-02-14</date>
+<version>1.0.10</version>
+<date>2005-07-13</date>
<chapter>
<title>Introduction</title>
@@ -219,6 +219,22 @@
<body>
<p>
+Some chipsets require you to rebuild <c>xorg-x11</c> with
+<c>USE="insecure-drivers"</c>. This applies to mach64, unichrome and savage
+chipsets on xorg-x11-6.8.2, and to mach64 and unichrome on xorg-x11-6.8.99.x.
+Savage users should not try xorg-x11-6.8.99.x as support for the savage there
+is broken.
+</p>
+
+<pre caption="Rebuilding xorg-x11">
+# <i>vim /etc/portage/package.use</i>
+<comment>(Add the following line if you use one of the abovementioned chipsets)</comment>
+x11-base/xorg-x11 insecure-drivers
+
+# <i>emerge xorg-x11</i>
+</pre>
+
+<p>
Open <path>/etc/X11/xorg.conf</path> with your favorite text editor and edit
it to enable DRI and GLX.
</p>
--
gentoo-doc-cvs@gentoo.org mailing list
next reply other threads:[~2005-07-13 12:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 12:57 Sven Vermeulen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-27 12:45 [gentoo-doc-cvs] cvs commit: dri-howto.xml Shyam Mani
2005-07-30 9:47 Xavier Neys
2005-07-30 21:48 Xavier Neys
2005-10-11 3:46 swift
2005-12-16 7:30 Shyam Mani
2006-02-01 11:58 Xavier Neys
2006-05-07 12:39 Josh Saddler
2006-05-12 19:32 Josh Saddler
2006-07-31 19:37 Jan Kundrat
2006-10-09 13:41 Josh Saddler
2006-10-09 13:43 Josh Saddler
2006-10-10 9:35 Xavier Neys
2006-10-10 9:36 Xavier Neys
2007-02-18 23:44 Josh Saddler
2007-04-26 3:45 Josh Saddler
2008-05-21 19:29 Sven Vermeulen
2008-09-10 21:20 Joshua Saddler
2008-11-06 9:42 Joshua Saddler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200507131257.j6DCv3aC002516@robin.gentoo.org \
--to=swift@lark.gentoo.org \
--cc=docs-team@lists.gentoo.org \
--cc=gentoo-doc-cvs@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox