neysx       05/07/05 09:00:46

  Modified:    xml/htdocs/doc/en mips-requirements.xml
  Log:
  Improved coding style, fixed typos  **No Content Change**

Revision  Changes    Path
1.10      +44 -49    xml/htdocs/doc/en/mips-requirements.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/mips-requirements.xml?rev=1.10&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/mips-requirements.xml?rev=1.10&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/mips-requirements.xml.diff?r1=1.9&r2=1.10&cvsroot=gentoo

Index: mips-requirements.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/mips-requirements.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- mips-requirements.xml       5 Jul 2005 08:56:31 -0000       1.9
+++ mips-requirements.xml       5 Jul 2005 09:00:46 -0000       1.10
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/mips-requirements.xml,v 
1.9 2005/07/05 08:56:31 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/mips-requirements.xml,v 
1.10 2005/07/05 09:00:46 neysx Exp $ -->
 
 <guide link="/doc/en/mips-requirements.xml">
                                
@@ -16,8 +16,8 @@
 </author>
 
 <abstract>
-This document provides an overview of the status of various MIPS-based systems 
-for installing Gentoo Linux. If you find errors or ommissions please email the
+This document provides an overview of the status of various MIPS-based systems
+for installing Gentoo Linux. If you find errors or omissions please email the
 maintainer or an editor.
 </abstract>
 
@@ -36,9 +36,9 @@
 <body>
 
 <p>
-The exact requirements will largely depend on what you intend to use the 
machine
-for and how you wish to go about installing Gentoo.  The following table should
-give you a rough idea.
+The exact requirements will largely depend on what you intend to use the
+machine for and how you wish to go about installing Gentoo.  The following
+table should give you a rough idea.
 </p>
 
 <table>
@@ -65,7 +65,6 @@
 </body>
 
 </section>
-
 <section>
 <title>A Note about serial consoles</title>
 <body>
@@ -120,12 +119,10 @@
     <b>Processor Options (Stable):</b>
     <ul>
       <li>
-        <e>(on Indy and Challenge S)</e>
-        R4000, R4400, R4600, R5000
+        <e>(on Indy and Challenge S)</e> R4000, R4400, R4600, R5000
       </li>
       <li>
-        <e>(on Indigo 2)</e>
-        R4000, R4400
+        <e>(on Indigo 2)</e> R4000, R4400
       </li>
     </ul>
   </li>
@@ -155,26 +152,25 @@
     <b>Notes:</b>
     <ol>
       <li>
-        At present, only the Newport (XL) graphics framebuffer is
-        supported in Linux.  Therefore on systems with other framebuffers,
-        you will need to use serial console.
+        At present, only the Newport (XL) graphics framebuffer is supported in
+        Linux.  Therefore on systems with other framebuffers, you will need to
+        use serial console.
       </li>
       <li>
         The Challenge S has its RJ-45 connector on a daughter board (Mezz)
-        linked with an unsupported SCSI adapter, a WD33C95A.  In order for
-        this network connector to function, this SCSI bus needs to be
-        activated, however it is not yet supported by Linux.  As a result
-        of this, the Challenge S can only get network connectivity via its
-        AUI connector.
+        linked with an unsupported SCSI adapter, a WD33C95A.  In order for this
+        network connector to function, this SCSI bus needs to be activated,
+        however it is not yet supported by Linux.  As a result of this, the
+        Challenge S can only get network connectivity via its AUI connector.
       </li>
       <li>
-        Indigo2 EISA Support is <e>highly</e> experimental.  It isn't very
-        well tested and may not work with all hardware.  Hardware that it
-        is known to function with is listed, and as more compatible
-        hardware is discovered, it will be added.  Please note that
-        hardware requiring DMA support is currently not functional.  This
-        includes EISA/ISA-based soundcards.  EISA Video cards requiring an
-        x86-compatible BIOS are also not functional.
+        Indigo2 EISA Support is <e>highly</e> experimental.  It isn't very well
+        tested and may not work with all hardware.  Hardware that it is known
+        to function with is listed, and as more compatible hardware is
+        discovered, it will be added.  Please note that hardware requiring DMA
+        support is currently not functional.  This includes EISA/ISA-based
+        soundcards.  EISA Video cards requiring an x86-compatible BIOS are also
+        not functional.
       </li>
     </ol>
   </li>
@@ -222,7 +218,7 @@
     <ol>
       <li>
         The O2 RM7000 Processor support is limited in Linux currently, as it
-        requires a fairly recent kernel version (&gt;2.6.7), and has several 
+        requires a fairly recent kernel version (&gt;2.6.7), and has several
         notable issues.  The first issue is a problem with SCSI at the moment,
         making the internal disks unusable at the current time.  The Level 3
         (Tertiary) Cache is also disabled due to there being no support for
@@ -231,7 +227,7 @@
       <li>
         Please be aware that this note only applies to the official SGI RM7000
         running at 350MHz, not the 600MHz RM7000 that can be assembed using an
-        RM5200 board.  These "modded" CPU modules for O2 systems are not 
+        RM5200 board.  These "modded" CPU modules for O2 systems are not
         supported/tested, although, in theory, they should be functional, but
         may suffer from the same problems listed above.
       </li>
@@ -262,8 +258,7 @@
 
 <ul>
   <li>
-    <b>Processor Options <e>(Experimental)</e>:</b>
-    R10000, R12000
+    <b>Processor Options <e>(Experimental)</e>:</b> R10000, R12000
   </li>
   <li>
     <b>Kernel Support:</b>
@@ -297,8 +292,7 @@
 
 <ul>
   <li>
-    <b>Processor Options <e>(Experimental)</e>:</b>
-    R10000
+    <b>Processor Options <e>(Experimental)</e>:</b> R10000
   </li>
   <li>
     <b>Kernel Support:</b>
@@ -326,21 +320,21 @@
     <b>Notes:</b>
     <ol>
       <li>
-        IP28 Indigo2 Impact support (classified as an Indigo2 system w/ an 
-        R10000 Processor) is <e>very experimental</e>.  Most of the work is 
-        currently being done by Peter Fuerst who maintains patches on his 
-        <uri 
link="http://home.alphastar.de/fuerst/download.html";>website</uri>.
-        This kernel is <e>NOT</e> intended for stable, day-to-day use.  The 
-        Indigo2 IP28 system suffers from an issue known as <e>Speculative 
+        IP28 Indigo2 Impact support (classified as an Indigo2 system w/ an
+        R10000 Processor) is <e>very experimental</e>.  Most of the work is
+        currently being done by Peter Fuerst who maintains patches on his <uri
+        link="http://home.alphastar.de/fuerst/download.html";>website</uri>.
+        This kernel is <e>NOT</e> intended for stable, day-to-day use.  The
+        Indigo2 IP28 system suffers from an issue known as <e>Speculative
         Execution</e>, a feature of the R10000 Processor that is problematic on
         machines that are <e>Non Cache Coherent</e>, such as the IP28 Indigo2
         and on R10000/R12000-based IP32 O2 systems.  Details on the nature of
         Speculative Execution, and the issues it poses to the Indigo2 can be
         found at the following URLs:
-
         <ul>
           <li>
-            MIPS R10000 Microprocessor User's Manual (See <e>PDF Pages 
51-55</e>)
+            MIPS R10000 Microprocessor User's Manual (See <e>PDF Pages
+            51-55</e>)
             
<uri>http://techpubs.sgi.com/library/manuals/2000/007-2490-001/pdf/007-2490-001.pdf</uri>
           </li>
           <li>
@@ -388,12 +382,13 @@
     <ol>
       <li>
         Octane support in Linux should be regarded as experimental. Support for
-        this particular machine from SGI has been progressing quite well and 
-        the Linux kernel functions reasonably well. The current status for 
this 
-        system may be found on 
-        <uri link="http://helios.et.put.poznan.pl/~sskowron/ip30/";>Stanislaw 
Skowronek's page</uri>.
-        Wider support in Gentoo for this system will be available in the 
future,
-        so watch this space closely for more details.
+        this particular machine from SGI has been progressing quite well and
+        the Linux kernel functions reasonably well. The current status for this
+        system may be found on <uri
+        link="http://helios.et.put.poznan.pl/~sskowron/ip30/";>Stanislaw
+        Skowronek's page</uri>.  Wider support in Gentoo for this system will
+        be available in the future, so watch this space closely for more
+        details.
       </li>
       <li>
         The serial ports on the Octane currently only support 9600 baud rate,
@@ -497,10 +492,10 @@
 <note>
 (1) Work has begun on porting the ImpactSR to the Indigo2 Impact (IP28)
 workstation.  At the moment, it's early days, and the driver is not functional
-yet, but this may change in the comming months.<br/>
+yet, but this may change in the coming months.<br/>



-- 
[email protected] mailing list

Reply via email to