swift       05/07/02 12:51:40

  Modified:    xml/htdocs/doc/en ati-faq.xml
  Log:
  #96570 - Language fixes, no content change, first set

Revision  Changes    Path
1.28      +27 -24    xml/htdocs/doc/en/ati-faq.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/ati-faq.xml?rev=1.28&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/ati-faq.xml?rev=1.28&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/ati-faq.xml.diff?r1=1.27&r2=1.28&cvsroot=gentoo

Index: ati-faq.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/ati-faq.xml,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- ati-faq.xml 28 Jun 2005 16:04:36 -0000      1.27
+++ ati-faq.xml 2 Jul 2005 12:51:39 -0000       1.28
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/ati-faq.xml,v 1.27 
2005/06/28 16:04:36 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/ati-faq.xml,v 1.28 
2005/07/02 12:51:39 swift Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide link="/doc/en/ati-faq.xml">
@@ -35,10 +35,10 @@
 Almost every ATI board is supported by <uri 
 link="http://www.freedesktop.org/Software/xorg";>xorg-x11</uri>, at least for 
 the 2D accelerated features.  The 3D support is provided either by <uri 
-link="http://dri.sf.net";>the DRI project</uri>, which is already present 
inside 
-the xorg-x11, or by closed source drivers <uri 
-link="http://mirror.ati.com/support/drivers/linux/radeon-linux.html";>
-provided</uri> by ATI.
+link="http://dri.sf.net";>the DRI project</uri> which is part of xorg-x11, 
+or by ATI's <uri 
+link="http://mirror.ati.com/support/drivers/linux/radeon-linux.html";>closed
+source drivers</uri>.
 </p>
 
 <table>
@@ -78,41 +78,42 @@
 <body>
 
 <p>
-The multimedia features are actually supported by <uri 
-link="http://gatos.sf.net";>the GATOS project</uri>, the GATOS drivers will be 
+The board's multimedia features are supported by <uri 
+link="http://gatos.sf.net";>the GATOS project</uri>. These drivers will be 
 merged in the xorg tree shortly.
 </p>
 
 </body>
 </section>
 <section>
-<title>I'm not using an x86.  What are my options?</title>
+<title>I'm not using an x86-based architecture.  What are my options?</title>
 <body>
 
 <p>
-You have almost the same x11 support on PPC or Alpha platform but you can't 
-use the ATI closed source drivers.  That means that you can't use the r300 3d 
-features at all. If you have such a board and you want it supported by x11, 
-you should contact <uri link="http://www.ati.com";>ATI</uri> and ask them to 
open
-the specs. Recently the AMD64 closed source driver has been released. AMD64 
-users can use it as the x86 users.
+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.
 </p>
 
 <impo>
-In order to enable the agpgart for certain AMD64 chip sets you have to disable 
-the K8 IOMMU support
+To enable agpgart support for certain AMD64 chip sets, you have to disable 
+support for the K8 IOMMU.
 </impo>
 
 </body>
 </section>
 <section>
-<title>I have a laptop.  Is my "mobility" ATI model supported?</title>
+<title>I have a laptop.  Is my ATI Mobility model supported?</title>
 <body>
 
 <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 
file
-yourself or use the <c>xorgconfig</c>.
+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 file
+yourself or use the <c>xorgconfig</c> utility.
 </p>
 
 </body>
@@ -167,8 +168,9 @@
 <body>
 
 <p>
-It is suggested the use of <c>xorgcfg</c>, <c>xorgconfig</c> or directly by
-using the Xorg auto configuration option:
+The use of <c>xorgcfg</c> or <c>xorgconfig</c> to generate the 
+<path>xorg.conf</path> configuration file is suggested. Alternatively, you
+may use the Xorg auto configuration option:
 </p>
 
 <pre caption="Autoconfiguring X">
@@ -182,11 +184,12 @@
 </p>
 
 <note>
-Users of the ati-drivers can also use <c>fglrxconfig</c>.
+You can use <c>fglrxconfig</c> if you have installed the <c>ati-drivers</c>
+package.
 </note>
 
 <impo>
-PPC users could use the <c>Xautoconf</c> stand alone configuration tool by
+PPC users could use the <c>Xautoconf</c> stand-alone configuration tool by
 emerging the <c>Xautoconf</c> ebuild, but isn't required.
 </impo>
 



-- 
[email protected] mailing list

Reply via email to