doc/en/mips-requirements.xml

<?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.14 2010/09/02 06:03:02 nightmorph Exp $ -->

<guide>
<title>Gentoo/MIPS Linux Hardware Requirements</title>

<author title="Author">
  <mail link="kumba@gentoo.org">Joshua Kinard</mail>
</author>
<author title="Editor">
  <mail link="redhatter@gentoo.org">Stuart Longland</mail>
</author>
<author title="Editor">
  <mail link="mattst88">Matt Turner</mail>
</author>

<abstract>
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>

<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
<license />

<version>2</version>
<date>2011-08-14</date>

<chapter>
<title>Silicon Graphics Systems &ndash; Stable</title>
<section>
<body>

<p>
The following systems are known to be very stable overall.  Just about all the
core hardware is supported in these systems, and there are very few outstanding
stability issues at this time.
</p>

</body>
</section>
<section>
<title>IP22: Indy, Indigo 2 and Challenge S</title>
<body>

<ul>
  <li>
    <b>Processor Options (Stable):</b>
    <ul>
      <li>
        <e>(on Indy and Challenge S)</e> R4000, R4400, R4600, R5000
      </li>
      <li>
        <e>(on Indigo 2)</e> R4000, R4400
      </li>
    </ul>
  </li>
  <li>
    <b>Kernel Architecture Support:</b>
    <ul>
      <li>32-bit: <e>Stable</e></li>
      <li>64-bit: <e>Experimental</e></li>
    </ul>
  </li>
  <li>
    <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.
      </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.
      </li>
      <li>
        Indigo2 EISA Support 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>
</ul>

</body>
</section>
<section>
<title>IP32: O2</title>
<body>

<ul>
  <li>
    <b>Processor Options:</b>
    <ul>
      <li><b>Stable:</b> R5000, RM5200</li>
      <li><b>Experimental:</b> RM7000</li>
      <li><b>Unsupported:</b> R10000</li>
    </ul>
  </li>
  <li>
    <b>Kernel Architecture Support:</b>
    <ul>
      <li>32-bit: <e>Unsupported in Kernel</e></li>
      <li>64-bit: <e>Stable</e></li>
    </ul>
  </li>
</ul>

</body>
</section>
</chapter>

<chapter>
<title>Silicon Graphics Systems &ndash; Experimental/Unstable</title>
<section>
<body>

<p>
The systems listed here are known to run Linux, however in many
cases, there are known stability issues and major gaps in the hardware
support. In short, it will be a rough and bumpy ride.
</p>

</body>
</section>
<section>
<title>IP27: Origin 200 and 2000</title>
<body>

<ul>
  <li>
    <b>Processor Options <e>(Experimental)</e>:</b> R10000, R12000
  </li>
  <li>
    <b>Kernel Architecture Support:</b>
    <ul>
      <li>32-bit: <e>Unsupported in Kernel</e></li>
      <li>64-bit: <e>Experimental</e></li>
    </ul>
  </li>
</ul>

</body>
</section>
<section>
<title>IP28: Indigo 2 Impact (a.k.a Indigo 2 R10k)</title>
<body>

<ul>
  <li>
    <b>Processor Options <e>(Experimental)</e>:</b> R10000
  </li>
  <li>
    <b>Kernel Architecture Support:</b>
    <ul>
      <li>32-bit: <e>Unsupported in Kernel</e></li>
      <li>64-bit: <e>Experimental</e></li>
    </ul>
  </li>
  <li>
    <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 was
        done by Peter Fuerst, who maintains patches on his <uri
        link="http://www.pfrst.de/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>)
            <uri>http://techpubs.sgi.com/library/manuals/2000/007-2490-001/pdf/007-2490-001.pdf</uri>
          </li>
          <li>
            Post to NetBSD sgimips Mailing List on 29 Jun 2000
            <uri>http://mail-index.netbsd.org/port-sgimips/2000/06/29/0006.html</uri>
          </li>
        </ul>
      </li>
    </ol>
  </li>
</ul>

</body>
</section>
<section>
<title>IP30: Octane &ndash; Dead</title>
<body>

<ul>
  <li><b>Processor Options (Experimental):</b> R10000, R12000, R14000A</li>
  <li>
    <b>Kernel Architecture Support:</b>
    <ul>
      <li>32-bit: <e>Unsupported in Kernel</e></li>
      <li>64-bit: <e>Experimental</e></li>
    </ul>
  </li>
  <li>
    <b>Notes:</b>
    <ol>
      <li>
        Octane support in Linux should be regarded as broken. Stanislaw
        Skowronek did the reverse engineering and bring up. <uri
        link="http://www.linux-mips.org/~skylark/">His page</uri> is available
        but has not been updated since October 2006.
      </li>
      <li>
        The serial ports on the Octane currently only support 9600 baud rate,
        8-bits, no parity, 1 stop bit.  Other baud rates do not currently work
        at present.
      </li>
      <li>
        Dead due to issues porting the IRQ handling to newer Linux kernels.
        Help is welcome.
      </li>
    </ol>
  </li>
</ul>

</body>
</section>
</chapter>

<chapter>
<title>Silicon Graphics Systems &ndash; Unsupported</title>
<section>
<body>

<p>
Just about all of these systems are totally unsupported at the kernel level &ndash;
making a full Linux system totally impossible.  Little is known about a lot of
the systems listed here &ndash; therefore any support in the near future is highly
unlikely.  You may wish to keep an eye on the <uri
link="http://www.linux-mips.org">Linux/MIPS website</uri> for any news of ports
&ndash; either that, or start your own. :-)
</p>

<ul>
  <li>IP12: Iris Indigo (R3000 CPU)</li>
  <li>IP20: Iris Indigo (R4000 or R4400 CPU)</li>
  <li>IP26: Indigo 2 Power (R8000 CPU)</li>
  <li>IP34: Fuel (R14000A or R16000 CPU)</li>
  <li>IP35: Origin 3000 (R14000 or R14000A CPU)</li>
  <li>IP45: Origin 300 (R14000 CPU)</li>
  <li>IP53: Origin 350 &amp; Tezro (R16000 CPU)</li>
</ul>

</body>
</section>
</chapter>

<chapter>
<title>Silicon Graphics Accessories</title>
<section>
<body>

<p>
As with most systems, there is quite wide array of peripherals that one can
obtain for Silicon Graphics systems.  While a lot of these work in IRIX, Linux
support is a bit touch-and-go on some of these items.  The following table
lists the support for each device.
</p>

<table>
  <tr>
    <th>Stable Support</th>
    <th>Experimental Support</th>
    <th>Unsupported/Untested</th>
  </tr>
  <tr>
    <ti>
      Indy/Indigo2: XL Graphics Card (Newport)<br/>
      Indy/Indigo2: SGI Seeq Ethernet 10Mbps<br/>
      Indy/Indigo2: WD33C93 SCSI<br/>
      Indy/Indigo2: HAL2 Sound/Audio<br/>
      Indy/Indigo2: Parallel Port<br/>
      Indy/Indigo2: Serial Port<br/>
      O2: SGI MACE Ethernet 10/100Mbps<br/>
      O2: Adaptec AIC7880 SCSI<br/>
      O2: Serial Port<br/>
      O2: GBE Framebuffer (4MB Framebuffer memory only!)<br/>
      Indigo2 ISA: Parallel Port Card (PC-Style)<br/>
      Indigo2 ISA: NE2000 Compatible 10Mbps NIC (RTL8019)
    </ti>
    <ti>
      Indy: I2C/VINO subsystem &amp; IndyCam<br/>
      Indigo2 EISA: 3COM 3c597 10/100Mbps<br/>
      O2: PCI Slot<br/>
      Origin: IOC3 Ethernet 10/100Mbps<br/>
      Origin: QLogic ISP1020 SCSI<br/>
      O2 PCI: ALi 5273 USB 2.0 (Req. Kernel &gt;=2.6.8.1)
    </ti>
    <ti>
      (1)Indy/Indigo2: Impact &amp; Extreme/XZ graphics chipsets<br/>
      Indy: Phobos G130 10/100Mbps NIC<br/>
      Indy ThunderLAN card<br/>
      Indigo2: GIO64 Slots<br/>
      Indigo2: Phobos G160 10/100Mbps NIC<br/>
      Challenge S: WD33C95A SCSI Adapter/RJ-45 Daughter Card<br/>
      O2: VICE Subsystem
      Octane: Keyboard<br/>
      Octane: Mardi Gras (MGRAS) Graphics<br/>
      Octane: QLogic ISP1040B SCSI<br/>
      Octane: RAD1 Audio<br/>
      Octane: SMP Support<br/>
      Octane: V6/V8/V10/V12 Graphics (Odyssey)<br/>
    </ti>
  </tr>
</table>

</body>
</section>
</chapter>

<chapter>
<title>Cobalt Servers &ndash; Stable</title>
<section>
<body>

<p>
The Cobalt servers are a set of machines all based around the QED RM523[01]
CPU.  They came in two varieties, the RaQ &ndash; a rackmounted model, and the Qube,
a small desktop model (1ft. cube).  The big difference between these systems
and the SGI systems above, is that these systems are <e>little endian</e>
(<c>mipsel</c>) as opposed to <e>big endian</e> (<c>mips</c>).
</p>

<p>
These were also sold under an OEM arragement to other companies, examples of
this are the Gateway Microserver (Qube 2) and the Seagate NasRaQ (RaQ 2).
</p>

</body>
</section>
<section>
<title>Qube/Raq 2800 (a.k.a Qube/Raq 2)</title>
<body>

<ul>
  <li><b>Processor:</b> QED RM5231 @ 250MHz</li>
  <li>
    <b>Kernel Architecture Support:</b>
    <ul>
      <li>32-bit: <e>Stable</e></li>
      <li>64-bit: <e>Highly Experimental</e></li>
    </ul>
  </li>
</ul>

</body>
</section>
</chapter>

<chapter>
<title>Cobalt Servers &ndash; Experimental</title>
<section>
<title>Raq 2700 (a.k.a Raq 1)</title>
<body>

<ul>
  <li><b>Processor:</b> QED RM5230 @ 150MHz</li>
  <li>
    <b>Kernel Architecture Support:</b>
    <ul>
      <li>32-bit: <e>Experimental</e></li>
      <li>64-bit: <e>Untested In Gentoo</e></li>
    </ul>
  </li>
</ul>

</body>
</section>
</chapter>

<chapter>
<title>Cobalt Servers &ndash; Unsupported</title>
<section>
<title>Qube 2700 (a.k.a Qube 1)</title>
<body>

<p>
The Qube 2700 was the first of this whole subarchitecture.  Unfortunately, it
lacks a serial port, making installation at present, damn near impossible. You
may wish to have a look at <uri
link="http://web.archive.org/web/20060716160139/http://metzner.org/projects/qube/">
Jan Metzner's page</uri> for more information.
</p>

<ul>
  <li><b>Processor:</b> QED RM5230 @ 150MHz</li>
  <li>
    <b>Kernel Architecture Support:</b>
    <ul>
      <li>32-bit: <e>Untested In Gentoo</e></li>
      <li>64-bit: <e>Untested In Gentoo</e></li>
    </ul>
  </li>
</ul>

</body>
</section>
</chapter>
</guide>
1	<?xml version='1.0' encoding="UTF-8"?>
2	<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/mips-requirements.xml,v 1.14 2010/09/02 06:03:02 nightmorph Exp $ -->
4
5	<guide>
6	<title>Gentoo/MIPS Linux Hardware Requirements</title>
7
8	<author title="Author">
9	<mail link="kumba@gentoo.org">Joshua Kinard</mail>
10	</author>
11	<author title="Editor">
12	<mail link="redhatter@gentoo.org">Stuart Longland</mail>
13	</author>
14	<author title="Editor">
15	<mail link="mattst88">Matt Turner</mail>
16	</author>
17
18	<abstract>
19	This document provides an overview of the status of various MIPS-based systems
20	for installing Gentoo Linux. If you find errors or omissions please email the
21	maintainer or an editor.
22	</abstract>
23
24	<!-- The content of this document is licensed under the CC-BY-SA license -->
25	<!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
26	<license />
27
28	<version>2</version>
29	<date>2011-08-14</date>
30
31	<chapter>
32	<title>Silicon Graphics Systems – Stable</title>
33	<section>
34	<body>
35
36	<p>
37	The following systems are known to be very stable overall. Just about all the
38	core hardware is supported in these systems, and there are very few outstanding
39	stability issues at this time.
40	</p>
41
42	</body>
43	</section>
44	<section>
45	<title>IP22: Indy, Indigo 2 and Challenge S</title>
46	<body>
47
48	<ul>
49	<li>
50	<b>Processor Options (Stable):</b>
51	<ul>
52	<li>
53	<e>(on Indy and Challenge S)</e> R4000, R4400, R4600, R5000
54	</li>
55	<li>
56	<e>(on Indigo 2)</e> R4000, R4400
57	</li>
58	</ul>
59	</li>
60	<li>
61	<b>Kernel Architecture Support:</b>
62	<ul>
63	<li>32-bit: <e>Stable</e></li>
64	<li>64-bit: <e>Experimental</e></li>
65	</ul>
66	</li>
67	<li>
68	<b>Notes:</b>
69	<ol>
70	<li>
71	At present, only the Newport (XL) graphics framebuffer is supported in
72	Linux. Therefore on systems with other framebuffers, you will need to
73	use serial console.
74	</li>
75	<li>
76	The Challenge S has its RJ-45 connector on a daughter board (Mezz)
77	linked with an unsupported SCSI adapter, a WD33C95A. In order for this
78	network connector to function, this SCSI bus needs to be activated,
79	however it is not yet supported by Linux. As a result of this, the
80	Challenge S can only get network connectivity via its AUI connector.
81	</li>
82	<li>
83	Indigo2 EISA Support isn't very well
84	tested and may not work with all hardware. Hardware that it is known
85	to function with is listed, and as more compatible hardware is
86	discovered, it will be added. Please note that hardware requiring DMA
87	support is currently not functional. This includes EISA/ISA-based
88	soundcards. EISA Video cards requiring an x86-compatible BIOS are also
89	not functional.
90	</li>
91	</ol>
92	</li>
93	</ul>
94
95	</body>
96	</section>
97	<section>
98	<title>IP32: O2</title>
99	<body>
100
101	<ul>
102	<li>
103	<b>Processor Options:</b>
104	<ul>
105	<li><b>Stable:</b> R5000, RM5200</li>
106	<li><b>Experimental:</b> RM7000</li>
107	<li><b>Unsupported:</b> R10000</li>
108	</ul>
109	</li>
110	<li>
111	<b>Kernel Architecture Support:</b>
112	<ul>
113	<li>32-bit: <e>Unsupported in Kernel</e></li>
114	<li>64-bit: <e>Stable</e></li>
115	</ul>
116	</li>
117	</ul>
118
119	</body>
120	</section>
121	</chapter>
122
123	<chapter>
124	<title>Silicon Graphics Systems – Experimental/Unstable</title>
125	<section>
126	<body>
127
128	<p>
129	The systems listed here are known to run Linux, however in many
130	cases, there are known stability issues and major gaps in the hardware
131	support. In short, it will be a rough and bumpy ride.
132	</p>
133
134	</body>
135	</section>
136	<section>
137	<title>IP27: Origin 200 and 2000</title>
138	<body>
139
140	<ul>
141	<li>
142	<b>Processor Options <e>(Experimental)</e>:</b> R10000, R12000
143	</li>
144	<li>
145	<b>Kernel Architecture Support:</b>
146	<ul>
147	<li>32-bit: <e>Unsupported in Kernel</e></li>
148	<li>64-bit: <e>Experimental</e></li>
149	</ul>
150	</li>
151	</ul>
152
153	</body>
154	</section>
155	<section>
156	<title>IP28: Indigo 2 Impact (a.k.a Indigo 2 R10k)</title>
157	<body>
158
159	<ul>
160	<li>
161	<b>Processor Options <e>(Experimental)</e>:</b> R10000
162	</li>
163	<li>
164	<b>Kernel Architecture Support:</b>
165	<ul>
166	<li>32-bit: <e>Unsupported in Kernel</e></li>
167	<li>64-bit: <e>Experimental</e></li>
168	</ul>
169	</li>
170	<li>
171	<b>Notes:</b>
172	<ol>
173	<li>
174	IP28 Indigo2 Impact support (classified as an Indigo2 system w/ an
175	R10000 Processor) is <e>very experimental</e>. Most of the work was
176	done by Peter Fuerst, who maintains patches on his <uri
177	link="http://www.pfrst.de/download.html">website</uri>. This kernel is
178	<e>not</e> intended for stable, day-to-day use. The Indigo2 IP28 system
179	suffers from an issue known as <e>Speculative Execution</e>, a feature
180	of the R10000 Processor that is problematic on machines that are <e>Non
181	Cache Coherent</e>, such as the IP28 Indigo2 and on R10000/R12000-based
182	IP32 O2 systems. Details on the nature of Speculative Execution, and
183	the issues it poses to the Indigo2 can be found at the following URLs:
184	<ul>
185	<li>
186	MIPS R10000 Microprocessor User's Manual (See <e>PDF Pages
187	51-55</e>)
188	<uri>http://techpubs.sgi.com/library/manuals/2000/007-2490-001/pdf/007-2490-001.pdf</uri>
189	</li>
190	<li>
191	Post to NetBSD sgimips Mailing List on 29 Jun 2000
192	<uri>http://mail-index.netbsd.org/port-sgimips/2000/06/29/0006.html</uri>
193	</li>
194	</ul>
195	</li>
196	</ol>
197	</li>
198	</ul>
199
200	</body>
201	</section>
202	<section>
203	<title>IP30: Octane – Dead</title>
204	<body>
205
206	<ul>
207	<li><b>Processor Options (Experimental):</b> R10000, R12000, R14000A</li>
208	<li>
209	<b>Kernel Architecture Support:</b>
210	<ul>
211	<li>32-bit: <e>Unsupported in Kernel</e></li>
212	<li>64-bit: <e>Experimental</e></li>
213	</ul>
214	</li>
215	<li>
216	<b>Notes:</b>
217	<ol>
218	<li>
219	Octane support in Linux should be regarded as broken. Stanislaw
220	Skowronek did the reverse engineering and bring up. <uri
221	link="http://www.linux-mips.org/~skylark/">His page</uri> is available
222	but has not been updated since October 2006.
223	</li>
224	<li>
225	The serial ports on the Octane currently only support 9600 baud rate,
226	8-bits, no parity, 1 stop bit. Other baud rates do not currently work
227	at present.
228	</li>
229	<li>
230	Dead due to issues porting the IRQ handling to newer Linux kernels.
231	Help is welcome.
232	</li>
233	</ol>
234	</li>
235	</ul>
236
237	</body>
238	</section>
239	</chapter>
240
241	<chapter>
242	<title>Silicon Graphics Systems – Unsupported</title>
243	<section>
244	<body>
245
246	<p>
247	Just about all of these systems are totally unsupported at the kernel level –
248	making a full Linux system totally impossible. Little is known about a lot of
249	the systems listed here – therefore any support in the near future is highly
250	unlikely. You may wish to keep an eye on the <uri
251	link="http://www.linux-mips.org">Linux/MIPS website</uri> for any news of ports
252	– either that, or start your own. :-)
253	</p>
254
255	<ul>
256	<li>IP12: Iris Indigo (R3000 CPU)</li>
257	<li>IP20: Iris Indigo (R4000 or R4400 CPU)</li>
258	<li>IP26: Indigo 2 Power (R8000 CPU)</li>
259	<li>IP34: Fuel (R14000A or R16000 CPU)</li>
260	<li>IP35: Origin 3000 (R14000 or R14000A CPU)</li>
261	<li>IP45: Origin 300 (R14000 CPU)</li>
262	<li>IP53: Origin 350 & Tezro (R16000 CPU)</li>
263	</ul>
264
265	</body>
266	</section>
267	</chapter>
268
269	<chapter>
270	<title>Silicon Graphics Accessories</title>
271	<section>
272	<body>
273
274	<p>
275	As with most systems, there is quite wide array of peripherals that one can
276	obtain for Silicon Graphics systems. While a lot of these work in IRIX, Linux
277	support is a bit touch-and-go on some of these items. The following table
278	lists the support for each device.
279	</p>
280
281	<table>
282	<tr>
283	<th>Stable Support</th>
284	<th>Experimental Support</th>
285	<th>Unsupported/Untested</th>
286	</tr>
287	<tr>
288	<ti>
289	Indy/Indigo2: XL Graphics Card (Newport)<br/>
290	Indy/Indigo2: SGI Seeq Ethernet 10Mbps<br/>
291	Indy/Indigo2: WD33C93 SCSI<br/>
292	Indy/Indigo2: HAL2 Sound/Audio<br/>
293	Indy/Indigo2: Parallel Port<br/>
294	Indy/Indigo2: Serial Port<br/>
295	O2: SGI MACE Ethernet 10/100Mbps<br/>
296	O2: Adaptec AIC7880 SCSI<br/>
297	O2: Serial Port<br/>
298	O2: GBE Framebuffer (4MB Framebuffer memory only!)<br/>
299	Indigo2 ISA: Parallel Port Card (PC-Style)<br/>
300	Indigo2 ISA: NE2000 Compatible 10Mbps NIC (RTL8019)
301	</ti>
302	<ti>
303	Indy: I2C/VINO subsystem & IndyCam<br/>
304	Indigo2 EISA: 3COM 3c597 10/100Mbps<br/>
305	O2: PCI Slot<br/>
306	Origin: IOC3 Ethernet 10/100Mbps<br/>
307	Origin: QLogic ISP1020 SCSI<br/>
308	O2 PCI: ALi 5273 USB 2.0 (Req. Kernel >=2.6.8.1)
309	</ti>
310	<ti>
311	(1)Indy/Indigo2: Impact & Extreme/XZ graphics chipsets<br/>
312	Indy: Phobos G130 10/100Mbps NIC<br/>
313	Indy ThunderLAN card<br/>
314	Indigo2: GIO64 Slots<br/>
315	Indigo2: Phobos G160 10/100Mbps NIC<br/>
316	Challenge S: WD33C95A SCSI Adapter/RJ-45 Daughter Card<br/>
317	O2: VICE Subsystem
318	Octane: Keyboard<br/>
319	Octane: Mardi Gras (MGRAS) Graphics<br/>
320	Octane: QLogic ISP1040B SCSI<br/>
321	Octane: RAD1 Audio<br/>
322	Octane: SMP Support<br/>
323	Octane: V6/V8/V10/V12 Graphics (Odyssey)<br/>
324	</ti>
325	</tr>
326	</table>
327
328	</body>
329	</section>
330	</chapter>
331
332	<chapter>
333	<title>Cobalt Servers – Stable</title>
334	<section>
335	<body>
336
337	<p>
338	The Cobalt servers are a set of machines all based around the QED RM523[01]
339	CPU. They came in two varieties, the RaQ – a rackmounted model, and the Qube,
340	a small desktop model (1ft. cube). The big difference between these systems
341	and the SGI systems above, is that these systems are <e>little endian</e>
342	(<c>mipsel</c>) as opposed to <e>big endian</e> (<c>mips</c>).
343	</p>
344
345	<p>
346	These were also sold under an OEM arragement to other companies, examples of
347	this are the Gateway Microserver (Qube 2) and the Seagate NasRaQ (RaQ 2).
348	</p>
349
350	</body>
351	</section>
352	<section>
353	<title>Qube/Raq 2800 (a.k.a Qube/Raq 2)</title>
354	<body>
355
356	<ul>
357	<li><b>Processor:</b> QED RM5231 @ 250MHz</li>
358	<li>
359	<b>Kernel Architecture Support:</b>
360	<ul>
361	<li>32-bit: <e>Stable</e></li>
362	<li>64-bit: <e>Highly Experimental</e></li>
363	</ul>
364	</li>
365	</ul>
366
367	</body>
368	</section>
369	</chapter>
370
371	<chapter>
372	<title>Cobalt Servers – Experimental</title>
373	<section>
374	<title>Raq 2700 (a.k.a Raq 1)</title>
375	<body>
376
377	<ul>
378	<li><b>Processor:</b> QED RM5230 @ 150MHz</li>
379	<li>
380	<b>Kernel Architecture Support:</b>
381	<ul>
382	<li>32-bit: <e>Experimental</e></li>
383	<li>64-bit: <e>Untested In Gentoo</e></li>
384	</ul>
385	</li>
386	</ul>
387
388	</body>
389	</section>
390	</chapter>
391
392	<chapter>
393	<title>Cobalt Servers – Unsupported</title>
394	<section>
395	<title>Qube 2700 (a.k.a Qube 1)</title>
396	<body>
397
398	<p>
399	The Qube 2700 was the first of this whole subarchitecture. Unfortunately, it
400	lacks a serial port, making installation at present, damn near impossible. You
401	may wish to have a look at <uri
402	link="http://web.archive.org/web/20060716160139/http://metzner.org/projects/qube/">
403	Jan Metzner's page</uri> for more information.
404	</p>
405
406	<ul>
407	<li><b>Processor:</b> QED RM5230 @ 150MHz</li>
408	<li>
409	<b>Kernel Architecture Support:</b>
410	<ul>
411	<li>32-bit: <e>Untested In Gentoo</e></li>
412	<li>64-bit: <e>Untested In Gentoo</e></li>
413	</ul>
414	</li>
415	</ul>
416
417	</body>
418	</section>
419	</chapter>
420	</guide>