Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-doc-cvs
Navigation:
Lists: gentoo-doc-cvs: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-doc-cvs@g.o
From: "Sven Vermeulen (swift)" <swift@g.o>
Subject: gentoo commit in xml/htdocs/doc/en: gentoo-mips-faq.xml
Date: Mon, 15 Aug 2011 20:13:16 +0000 (UTC)
swift       11/08/15 20:13:16

  Modified:             gentoo-mips-faq.xml
  Log:
  Fix bug #379319 - Updated gentoo-mips-faq.xml thanks to Matt Turner (mattst88) and Kumba

Revision  Changes    Path
1.5                  xml/htdocs/doc/en/gentoo-mips-faq.xml

file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/gentoo-mips-faq.xml?rev=1.5&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/gentoo-mips-faq.xml?rev=1.5&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/gentoo-mips-faq.xml?r1=1.4&r2=1.5

Index: gentoo-mips-faq.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-mips-faq.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- gentoo-mips-faq.xml	21 May 2008 19:47:28 -0000	1.4
+++ gentoo-mips-faq.xml	15 Aug 2011 20:13:16 -0000	1.5
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-mips-faq.xml,v 1.4 2008/05/21 19:47:28 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-mips-faq.xml,v 1.5 2011/08/15 20:13:16 swift Exp $ -->
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 <guide link="/doc/en/gentoo-mips-faq.xml">
@@ -9,6 +9,9 @@
 <author title="Author">
   <mail link="redhatter@g.o">Stuart Longland</mail>
 </author>
+<author title="Editor">
+  <mail link="mattst88">Matt Turner</mail>
+</author>
 
 <abstract>
 This FAQ is intended to answer some of the most frequently asked questions
@@ -19,11 +22,11 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>1.1</version>
-<date>2005-09-08</date>
+<version>2</version>
+<date>2011-08-14</date>
 
 <faqindex>
-<title>About this document</title>
+<title>About this Document</title>
 <section>
 <title>Introduction</title>
 <body>
@@ -36,9 +39,9 @@
 </p>
 
 <p>
-If you have anything to contribute to the FAQ or, having read this guide, you
+If you'd like to contribute to the FAQ or, having read this guide, you
 still have questions that are left unanswered, feel free to
-<uri link="http://mips.gentoo.org">drop us a line</uri>.
+<uri link="http://www.gentoo.org/proj/en/base/mips/">drop us a line</uri>.
 </p>
 
 </body>
@@ -52,10 +55,8 @@
 <body>
 
 <p>
-Gentoo/MIPS is a small project within the Gentoo Foundation, responsible for
-looking after the MIPS port of Gentoo Linux.  We currently look after two main
-sub architectures of the MIPS family specifically: Silicon Graphics systems and
-MIPS-based Cobalt servers.
+Gentoo/MIPS is a small project responsible for looking after the MIPS port of
+Gentoo Linux.
 </p>
 
 </body>
@@ -96,17 +97,12 @@
 
 <p>
 Hey, great idea.  Unfortunately, a lot of the Gentoo/MIPS team already have
-their hands full looking after Linux/MIPS as well as other commitments.
-However, you're welcome to give it a try.  May I suggest raising this on the
-<uri link="http://forums.gentoo.org/viewforum-f-32.html">Gentoo Forums</uri> and
-see what the interest is first.  Also, have a look at some of the other threads
-on porting Gentoo to other architectures such as <uri
-link="http://forums.gentoo.org/viewtopic-t-113387.html">Solaris/SPARC</uri>,
-<uri link="http://forums.gentoo.org/viewtopic-t-319607.html">IBM OS/2</uri> and
-<uri link="http://forums.gentoo.org/viewtopic-t-319691.html">Microsoft Services
-For Unix</uri> for hints on how to proceed.  If after some hacking you get
-something useful out of it... chances are a few developers will pick up on this
-and help you get it to the next stage.
+their hands full looking after Linux/MIPS as well as other commitments. A
+project like this would fall under the umbrella of the
+<uri link="http://www.gentoo.org/proj/en/gentoo-alt/prefix/">Gentoo Prefix
+project</uri>.  Some work has been done for IRIX, the remnants of which can be
+found in <uri
+link="https://bugs.gentoo.org/buglist.cgi?quicksearch=irix">bugzilla</uri>.
 </p>
 
 </body>
@@ -121,9 +117,10 @@
 
 <p>
 <uri link="http://www.mips.com">MIPS Technologies</uri> is a company that
-produce a number of RISC CPU cores which implement the MIPS Instruction Set
-Architecture.  These processors appear in all sorts of hardware ranging from
-small embedded devices to large servers.
+produce a number of RISC CPU cores which implement the <uri
+link="http://en.wikipedia.org/wiki/MIPS_architecture">MIPS Architecture</uri>.
+These processors appear in all sorts of hardware ranging from small embedded
+devices to large servers.
 </p>
 
 <p>
@@ -138,7 +135,7 @@
 <body>
 
 <p>
-Good question.  In short... Heaps.  MIPS Processors see use inside all sorts
+In short... lots.  MIPS Processors see use inside all sorts
 of machines, ranging from small PDAs (such as the early Windows CE powered Casio
 PDAs), X Terminals (e.g. Tektronix TekXPress XP330 series), through to
 workstations such as the Silicon Graphics Indy and O2 and even high end servers
@@ -146,105 +143,12 @@
 </p>
 
 <p>
-Here is a list of some of the more famous MIPS-based systems in use.  A more
-comprehensive list can be found on the <uri
+A comprehensive list can be found on the <uri
 link="http://www.linux-mips.org/wiki/index.php/Systems">Linux/MIPS website</uri>
 </p>
 
-<table>
-<tr>
-  <th>Sony Game Consoles</th>
-  <ti>
-    <uri link="http://www.linux-mips.org/wiki/index.php/PS1">
-    PlayStation</uri><br />
-    <uri link="http://www.linux-mips.org/wiki/index.php/PS2">
-    PlayStation 2</uri><br />
-    <uri link="http://www.linux-mips.org/wiki/index.php/PSP">
-    PlayStation Pocket</uri>
-  </ti>
-</tr>
-<tr>
-  <th>Nintendo Game Consoles</th>
-  <ti>
-    <uri link="http://www.linux-mips.org/wiki/index.php/Nintendo_64">
-      Nintendo 64
-    </uri>
-  </ti>
-</tr>
-<tr>
-  <th>Silicon Graphics Machines</th>
-  <ti>
-    <uri link="http://www.linux-mips.org/wiki/index.php/IP12">
-    Iris Indigo</uri><br />
-    <uri link="http://www.linux-mips.org/wiki/index.php/IP19">
-    Challenge</uri><br />
-    <uri link="http://www.linux-mips.org/wiki/index.php/IP19">
-    Onyx</uri><br />
-    <uri link="http://www.linux-mips.org/wiki/index.php/IP22">
-    Indy</uri><br />
-    <uri link="http://www.linux-mips.org/wiki/index.php/IP22">
-    Indigo 2</uri><br />
-    <uri link="http://www.linux-mips.org/wiki/index.php/IP22">
-    Challenge S</uri><br />
-    <uri link="http://www.linux-mips.org/wiki/index.php/IP27">
-    Origin 200</uri><br />
-    <uri link="http://www.linux-mips.org/wiki/index.php/IP27">
-    Origin 2000</uri><br />
-    <uri link="http://www.linux-mips.org/wiki/index.php/IP27">
-    Onyx 2</uri><br />
-    <uri link="http://www.linux-mips.org/wiki/index.php/IP30">
-    Octane</uri><br />
-    <uri link="http://www.linux-mips.org/wiki/index.php/IP30">
-    Octane 2</uri><br />
-    <uri link="http://www.linux-mips.org/wiki/index.php/IP32">
-    O2</uri><br />
-    <uri link="http://www.linux-mips.org/wiki/index.php/IP34">
-    Fuel</uri><br />
-    <uri link="http://www.linux-mips.org/wiki/index.php/IP35">
-    Origin 3000</uri><br />
-    <uri link="http://www.linux-mips.org/wiki/index.php/IP45">
-    Origin 300</uri><br />
-    <uri link="http://www.linux-mips.org/wiki/index.php/IP53">
-    Origin 350</uri><br />
-    <uri link="http://www.linux-mips.org/wiki/index.php/IP53">
-    Tezro</uri>
-  </ti>
-</tr>
-<tr>
-  <th>DECStations</th>
-  <ti>
-    <uri link="http://www.linux-mips.org/wiki/index.php/Deskstation_rPC44">
-    rPC44</uri><br />
-    <uri link="http://www.linux-mips.org/wiki/index.php/Deskstation_Tyne">
-    Tyne</uri>
-  </ti>
-</tr>
-<tr>
-  <th>Cobalt Microservers</th>
-  <ti>
-    <uri link="http://www.linux-mips.org/wiki/index.php/Cobalt">
-    Qube 2700</uri><br />
-    <uri link="http://www.linux-mips.org/wiki/index.php/Cobalt">
-    Qube 2800</uri><br />
-    <uri link="http://www.linux-mips.org/wiki/index.php/Cobalt">
-    RaQ</uri><br />
-    <uri link="http://www.linux-mips.org/wiki/index.php/Cobalt">
-    RaQ 2</uri>
-  </ti>
-</tr>
-<tr>
-  <th>
-    Broadcom-based 802.11g<br />
-    Broadband Internet Routers
-  </th>
-  <ti>
-    <uri link="http://openwrt.org/">Linksys WRT54G</uri>
-  </ti>
-</tr>
-</table>
-
 <p>
-... and that's only just scratching the surface.  These machines are wide and
+... and that's only scratching the surface.  These machines are wide and
 varied.  Many of them do not currently run Linux.  Of those that do, we only
 support a handful, although you're welcome to port Gentoo/MIPS to any MIPS
 machine if you so wish.  Some of these machines are also the focus of the <uri
@@ -259,24 +163,10 @@
 <body>
 
 <p>
-This question is difficult to answer.  Your machine could fall into one of three
-different baskets:
-</p>
-
-<ul>
-  <li>Your machine is supported by Gentoo/MIPS</li>
-  <li>Your machine is supported by Linux/MIPS, but not by Gentoo/MIPS (yet)</li>
-  <li>Your machine is not supported by Linux/MIPS</li>
-</ul>
-
-<p>
 For the first one an easy way to find out is to have a look at the
 <uri link="/doc/en/mips-requirements.xml">Gentoo/MIPS
 requirements page</uri>.  This will tell you if the system you've got can
-theoretically run Gentoo/MIPS.  Stuart has also written a
-<uri link="http://stuartl.longlandclan.hopto.org/gentoo/mips/">hardware support
-database</uri> in which users may contribute their experiences.  This can help
-measure how well Gentoo/MIPS runs on a particular machine.
+theoretically run Gentoo/MIPS.
 </p>
 
 <p>
@@ -296,14 +186,14 @@
 
 <p>
 If you've looked at the Gentoo/MIPS Hardware Requirements page, you've probably
-noticed there are a LOT of machines we don't support.  In the case of SGI
+noticed there are a lot of machines we don't support.  In the case of SGI
 hardware, very little is known about some of them, not enough
 to successfully port Linux to them.
 </p>
 
 <p>
 If you managed to get Linux working on a box currently listed as
-<e>unsupported</e> however, feel free to tell us.  We'd be interested to know.
+<e>unsupported</e> however, please tell us.  We'd be interested to know.
 </p>
 
 </body>
@@ -322,58 +212,46 @@
 </p>
 
 <pre caption="Stage Tarball Naming Scheme">
-  stage3-mipsel4-2005.0.tar.bz2
-  \____/ \_____/ \____/
+  stage3-mipsel4_multilib-20110627.tar.bz2
+  \____/ \_____/ \_____/  \______/
+     |      |       |        |
+     |      |       |        `-- Gentoo Release (date of creation)
      |      |       |
-     |      |       `--- Gentoo Release (e.g. 1.4, 2004.3, 2005.0)
+     |      |       `--- ABI: multilib, n32, n64 (nothing for o32)
      |      |
      |      `----------- Endianness and ISA Level
      |                     mips   ==> Big Endian
      |                     mipsel ==> Little Endian
      |
-     |                     R3xxx and earlier: ISA Level 1
-     |                     R4xxx series:      ISA Level 3
-     |                     R5000 and above:   ISA Level 4
-     |
      `------------------ Stage Tarball type: 1, 2 or 3.
 </pre>
 
 <p>
-So for those of you who are running R4000-class CPUs, try a <c>mips3</c> or
-<c>mipsel3</c> stage tarball.
-</p>
-
-<p>
-For those running R5000-class or later CPUs, try a <c>mips4</c> or
-<c>mipsel4</c> stage tarball.
+For R4000-class CPUs, use a <c>mips3</c> or <c>mipsel3</c> stage tarball.
 </p>
 
 <p>
-Sometimes the filename will have <c>n32</c> or <c>n64</c> in the filename as
-well.  These refer to 64-bit userland images.  At the moment, support for 64-bit
-userlands is still quite flaky and a lot of packages are broken.  I'd suggest
-leaving these alone unless you're particularly brave and don't mind a rather
-bumpy ride.
+For R5000-class or later CPUs, use a <c>mips4</c> or <c>mipsel4</c> stage
+tarball.
 </p>
 
 </body>
 </section>
 <section id="chroot">
-<title>I got told "Illegal Instruction" or "Cannot Execute Binary
-File" when chrooting.  What did I do wrong?</title>
+<title>I got an "Illegal Instruction" or "Cannot Execute Binary
+File" error message when chrooting.  What did I do wrong?</title>
 <body>
 
 <p>
 This is generally caused by using the wrong stage tarball.  If you try to run a
 <c>mips4</c> userland on a <c>mips3</c> CPU, you'll get an <e>illegal
 instruction</e> error message.  Likewise, if you have a Big Endian CPU and you
-try running Little Endian code on it, you'll get told <e>cannot execute binary
+try to run Little Endian code on it, you'll get <e>cannot execute binary
 file</e>.
 </p>
 
 <p>
-The fix is simple... clean out your partition, then unpack the correct tarball.
-Which one is that I hear you ask?  Have a read of the previous FAQ entry.
+The fix is simple: clean out your partition, then unpack the correct tarball.
 </p>
 
 </body>
@@ -455,7 +333,7 @@
 </section>
 <section id="serial">
 <title>The machine downloads the kernel, but then "hangs" (using a monitor and
-keyboard -- not serial console)</title>
+keyboard &ndash; not serial console)</title>
 <body>
 
 <p>
@@ -535,8 +413,7 @@
 The Qube 2700 was the first of the Cobalt servers.  While they are very nice
 machines, unfortunately, they lack a serial port.  In other words, any
 interaction with the machine has to be done through a network.  At present, our
-netboot images do not support this, although plans are in the works that may
-enable support for this machine.
+netboot images do not support this.
 </p>
 
 </body>





Navigation:
Lists: gentoo-doc-cvs: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
gentoo commit in xml/htdocs/doc/en: gentoo-alpha-faq.xml
Next by thread:
gentoo commit in xml/htdocs/doc/en: vi-guide.xml
Previous by date:
gentoo commit in xml/htdocs/doc/en: gentoo-alpha-faq.xml
Next by date:
gentoo commit in xml/htdocs/doc/en: mips-requirements.xml


Updated Jun 29, 2012

Summary: Archive of the gentoo-doc-cvs mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.