nightmorph    07/05/01 06:28:29

  Modified:             hb-install-mips-kernel.xml
  Log:
  mips updates, bug 176526

Revision  Changes    Path
1.15                 xml/htdocs/doc/en/handbook/draft/hb-install-mips-kernel.xml

file : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-kernel.xml?rev=1.15&view=markup
plain: 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-kernel.xml?rev=1.15&content-type=text/plain
diff : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-kernel.xml?r1=1.14&r2=1.15

Index: hb-install-mips-kernel.xml
===================================================================
RCS file: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-kernel.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- hb-install-mips-kernel.xml  8 Apr 2007 15:54:05 -0000       1.14
+++ hb-install-mips-kernel.xml  1 May 2007 06:28:29 -0000       1.15
@@ -4,12 +4,12 @@
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-kernel.xml,v
 1.14 2007/04/08 15:54:05 nightmorph Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-kernel.xml,v
 1.15 2007/05/01 06:28:29 nightmorph Exp $ -->
 <!-- :vim:ts=2:sts=2:et:tw=80: -->
 <sections>
 
 <version>8.0</version>
-<date>2007-02-26</date>
+<date>2007-04-30</date>
 
 <section>
 <title>Timezone</title>
@@ -49,75 +49,23 @@
 
 <p>
 MIPS-based systems have just the one kernel tree to choose from,
-<c>mips-sources</c>. <!--Special patches are needed to make certain systems 
work.
-The table below displays the USE flags required to enable the patchsets. Note
-that Indy, Indigo2 (R4k) and Challenge S systems do not require any additional
-patchsets.-->  This patchset differs from the ones available for other
-architectures, in that it has lots of patches specific to the MIPS 
architecture.
+<c>mips-sources</c>. This patchset differs from the ones available for other
+architectures, in that it has lots of patches specific to the MIPS
+architecture.
 </p>
 
-<!--
-<table>
-<tr>
-  <th>USE flag</th>
-  <th>System</th>
-</tr>
-<tr>
-  <ti><c>cobalt</c></ti>
-  <ti>Cobalt Qube/RaQ support</ti>
-</tr>
-<tr>
-  <ti><c>ip27</c></ti>
-  <ti>SGI Origin 200/2000 support (1)</ti>
-</tr>
-<tr>
-  <ti><c>ip28</c></ti>
-  <ti>SGI Indigo2 Impact (R10000) support (1,2)</ti>
-</tr>
-<tr>
-  <ti><c>ip30</c></ti>
-  <ti>SGI Octane/Octane2 support (1)</ti>
-</tr>
-</table>-->
-
 <pre caption="Merging kernel sources...">
-<!-- Done by profile?
-<comment>(Substitute cobalt with the appropriate USE flag for your system if 
required)</comment>
-# <i>mkdir /etc/portage</i>
-# <i>echo "sys-kernel/mips-sources cobalt" &gt;&gt; 
/etc/portage/package.use</i>
-
-<comment>(Unpack &amp; install the kernel sources)</comment>
--->
 # <i>emerge mips-sources</i>
 </pre>
 
 <impo>
-<!--(1)--> On the Origin 200/2000, Indigo2 Impact (R10000), Octane/Octane2 and
-O2, a 64-bit kernel is required to boot these systems. For these machines, you
-should <!--switch to the <path>default-linux/mips/mips64/RELEASE</path>
-profile by altering the <path>/etc/make.profile</path> symlink.
-Then you can --><c>emerge
-kgcc64</c> to create a cross-compiler for building 64-bit kernels.
+On the Origin 200/2000, Indigo2 Impact (R10000), Octane/Octane2 and O2, a 
64-bit
+kernel is required to boot these systems. For these machines, you should
+<c>emerge kgcc64</c> to create a cross-compiler for building 64-bit kernels.
 </impo>
 
-<!--<impo>
-(2) The Indigo2 Impact is a special case in that it requires special patch to
-be applied to <c>gcc</c> before it will build an IP28 kernel correctly. This
-patch adds support for the <c>-mip28-cache-barriers</c> CFLAG, which is used
-when building kernels to work around the inherent hardware bug brought on by
-speculative execution. This USE flag can be set in <path>/etc/make.conf</path>.
-This is done for you by setting your profile to
-<path>default-linux/mips/mips64/ip28/RELEASE</path>, which also takes care of
-(1).
-</impo>-->
-
 <pre caption="Installing kgcc64...">
-<!--<comment>(This assumes PORTDIR is in the usual location; 
/usr/portage)</comment>
-# <i>rm /etc/make.profile</i>
-# <i>ln -s /usr/portage/profiles/default-linux/mips/mips64/2005.0</i> 
<comment>(or .../mips64/ip28/2005.0)</comment>
-
-<comment>(Install the 64-bit kernel toolchain)</comment>
---># <i>emerge kgcc64</i>
+# <i>emerge kgcc64</i>
 </pre>
 
 <p>
@@ -183,7 +131,7 @@
 <tr>
   <ti>Indigo2 Impact (R10k)</ti>
   <ti>
-    <c>make ip28_defconfig</c> (requires <c>mips-sources-2.6.14.5</c> or later)
+    <c>make ip28_defconfig</c>
   </ti>
 </tr>
 <tr>



-- 
[EMAIL PROTECTED] mailing list

Reply via email to