From: "Joshua Saddler (nightmorph)" <nightmorph@gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en: ati-faq.xml
Date: Tue, 13 Jul 2010 20:08:03 +0000 (UTC) [thread overview]
Message-ID: <20100713200803.7A88D2CE14@corvid.gentoo.org> (raw)
nightmorph 10/07/13 20:08:03
Modified: ati-faq.xml
Log:
clean up the ATI faq, add R800 (evergreen) support info. inspired by bug 307481.
Revision Changes Path
1.48 xml/htdocs/doc/en/ati-faq.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/ati-faq.xml?rev=1.48&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/ati-faq.xml?rev=1.48&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/ati-faq.xml?r1=1.47&r2=1.48
Index: ati-faq.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/ati-faq.xml,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -r1.47 -r1.48
--- ati-faq.xml 30 Nov 2009 08:35:32 -0000 1.47
+++ ati-faq.xml 13 Jul 2010 20:08:03 -0000 1.48
@@ -1,8 +1,8 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/ati-faq.xml,v 1.47 2009/11/30 08:35:32 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/ati-faq.xml,v 1.48 2010/07/13 20:08:03 nightmorph Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<guide link="/doc/en/ati-faq.xml">
+<guide>
<title>Gentoo Linux ATI FAQ</title>
<author title="Author">
@@ -27,8 +27,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.8</version>
-<date>2009-11-30</date>
+<version>2</version>
+<date>2010-07-13</date>
<chapter>
<title>Hardware Support</title>
@@ -43,7 +43,7 @@
ATI's <uri
link="http://mirror.ati.com/support/drivers/linux/radeon-linux.html">closed
source drivers</uri>. ATI's closed source driver only supports R600 and newer
-GPUs. Older GPUs will use the mature xorg-x11 driver.
+GPUs. Older GPUs will use the mature open source xorg-x11 driver.
</p>
<table>
@@ -79,17 +79,22 @@
</tr>
<tr>
<ti>R600</ti>
- <ti>Radeon HD 2000 series</ti>
+ <ti>RadeonHD 2000 series</ti>
<ti>ATI DRI, xorg</ti>
</tr>
<tr>
<ti>RV670</ti>
- <ti>Radeon HD 3000 series</ti>
+ <ti>RadeonHD 3000 series</ti>
<ti>ATI DRI, xorg</ti>
</tr>
<tr>
<ti>RV770</ti>
- <ti>Radeon HD 4000 series</ti>
+ <ti>RadeonHD 4000 series</ti>
+ <ti>ATI DRI, xorg</ti>
+</tr>
+<tr>
+ <ti>R800</ti>
+ <ti>RadeonHD 5000 series, "Evergreen"</ti>
<ti>ATI DRI, xorg</ti>
</tr>
</table>
@@ -103,9 +108,7 @@
<body>
<p>
-The board's multimedia features are supported by <uri
-link="http://gatos.sf.net">the GATOS project</uri>. These drivers have been
-merged into the Xorg tree. You don't need to use anything special;
+You don't need to use anything special for the board's multimedia features;
<c>x11-drivers/xf86-video-ati</c> will work just fine.
</p>
@@ -117,16 +120,14 @@
<p>
X11 support on the PPC or Alpha platforms is quite similar to x86 X11 support.
-However, ATI's closed source drivers are not supported on the PPC or Alpha, so
-you cannot use the 3D features of the R300 Graphics Processing Unit (GPU). If
-you have such a board and want it supported by X11, contact <uri
-link="http://www.ati.com">ATI</uri> and ask them to release the specifications
-for your system's GPU. The closed source driver for the AMD64 was released, so
-AMD64 users can now enjoy the same features as x86 users.
+However, ATI's closed source Catalyst drivers are not supported on the PPC or
+Alpha, so you will have to use the open source drivers. The Catalyst drivers are
+only available for x86 and AMD64. The open source xorg-x11 drivers should work
+well on all architectures.
</p>
<impo>
-To enable agpgart support for certain AMD64 chip sets, you have to disable
+To enable agpgart support for certain old AMD64 chipsets, you have to disable
support for the K8 IOMMU.
</impo>
@@ -138,7 +139,7 @@
<p>
It should be, but you may have a configuration issue due to the OEM PCI id that
-such chips may have. In most cases, you may have to write the configuration
+such chips may have. In such cases, you may have to write the configuration
file yourself.
</p>
next reply other threads:[~2010-07-13 20:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 20:08 Joshua Saddler (nightmorph) [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-29 19:21 [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en: ati-faq.xml Joshua Saddler (nightmorph)
2012-06-29 16:20 Sven Vermeulen (swift)
2012-06-14 6:43 Joshua Saddler (nightmorph)
2011-03-23 9:26 Joshua Saddler (nightmorph)
2011-03-02 8:00 Joshua Saddler (nightmorph)
2011-03-02 7:46 Joshua Saddler (nightmorph)
2010-08-02 20:54 Joshua Saddler (nightmorph)
2009-11-30 8:35 Joshua Saddler (nightmorph)
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=20100713200803.7A88D2CE14@corvid.gentoo.org \
--to=nightmorph@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