/[gentoo]/xml/htdocs/doc/en/mips-requirements.xml
Gentoo

Diff of /xml/htdocs/doc/en/mips-requirements.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.1 Revision 1.7
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3
4<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/mips-requirements.xml,v 1.7 2005/03/12 17:36:22 neysx Exp $ -->
5
3<guide link="/doc/en/mips-requirements.xml"> 6<guide link="/doc/en/mips-requirements.xml">
7
4<title>Gentoo MIPS Hardware Requirements</title> 8<title>Gentoo/MIPS Linux Hardware Requirements</title>
9
5<author title="Author"> 10<author title="Author">
6 <mail link="kumba@gentoo.org">Joshua Kinard</mail> 11 <mail link="kumba@gentoo.org">Joshua Kinard</mail>
7</author> 12</author>
8 13
14<author title="Editor">
15 <mail link="stuartl@longlandclan.hopto.org">Stuart Longland</mail>
16</author>
17
9<abstract> 18<abstract>
10This document informs you about the supported MIPS hardware and the issues you 19This document provides an overview of the status of various MIPS-based systems
11can come across. 20for installing Gentoo Linux. If you find errors or ommissions please email the
21maintainer or an editor.
12</abstract> 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
13<version>0.1</version> 28<version>0.5</version>
14<date>December 15, 2003</date> 29<date>2005-03-08</date>
15<license/>
16<chapter>
17<title>Supported and Unsupported Hardware</title>
18<section>
19<title>Introduction</title>
20<body>
21 30
22<p> 31<chapter>
23Not many sites give you a quick overview on the supported MIPS hardware. To be 32<title>General Requirements</title>
24able to give you an idea on how the MIPS support is progressing we will list as
25much hardware-information as possible. If you still have questions, don't
26hesitate to ask <mail link="kumba@gentoo.org">Joshua Kinard</mail>.
27</p>
28 33
29<p>
30In the support-list, we use "[...]" with <c>blue</c> color to denote
31experimental support. Unsupported items are embraced by "(...)" and colored in
32<brite>red</brite>.
33</p>
34
35</body>
36</section> 34<section>
37<section> 35<title>System Requirements</title>
38<title>MIPS Systems</title>
39<body> 36<body>
37
38<p>
39The exact requirements will largely depend on what you intend to use the machine
40for and how you wish to go about installing Gentoo. The following table should
41give you a rough idea.
42</p>
40 43
41<table> 44<table>
42<tr>
43 <th>System</th>
44 <th>CPUs</th>
45 <th>Architectures</th>
46 <th>Kernels</th>
47</tr>
48<tr>
49 <ti>Indy</ti>
50 <ti>R4000, R4400, R4600, R5000</ti>
51 <ti>32-bit, [<i>64-bit (kernel)</i>]</ti>
52 <ti>2.4, (<brite>2.6</brite>)</ti>
53</tr>
54<tr>
55 <ti>Indigo2</ti>
56 <ti>R4000, R4400, R4600, (<brite>R8000</brite>), (<brite>R10000</brite>)</ti>
57 <ti>32-bit, [<i>64-bit (kernel) IP22</i>]</ti>
58 <ti>2.4, (<brite>2.6</brite>)</ti>
59</tr>
60<tr>
61 <ti>Challenge S</ti>
62 <ti>R4000, R4400, R4600, R5000</ti>
63 <ti>32-bit, [<i>64-bit (kernel)</i>]</ti>
64 <ti>2.4, (<brite>2.6</brite>)</ti>
65</tr>
66<tr>
67 <ti>[<i>O2</i>]</ti>
68 <ti> 45 <tr>
69 [<i>R5000</i>], [<i>RM5200</i>], (<brite>R10000</brite>), [<i>R12000</i>] 46 <ti/>
47 <th>Minimum</th>
48 <th>Recommended</th>
49 <th>Ideal</th>
70 </ti> 50 </tr>
71 <ti>[<i>32-bit (userland)</i>], [<i>64-bit (kernel)</i>]</ti> 51 <tr>
72 <ti>(<brite>2.6</brite>), [<i>2.6</i>]</ti> 52 <th>RAM:</th>
53 <ti>48~64MB</ti>
54 <ti>&gt;128MB</ti>
55 <ti>~256MB</ti>
73</tr> 56 </tr>
74<tr> 57 <tr>
75 <ti>[<i>Origin</i>]</ti> 58 <th>HDD:</th>
76 <ti>[<i>R10000</i>]</ti> 59 <ti>4GB</ti>
77 <ti>[<i>32-bit (userland), 64-bit (kernel)</i>]</ti> 60 <ti>&gt;8GB</ti>
78 <ti>[<i>2.4</i>], [<i>2.6</i>]</ti> 61 <ti>18GB</ti>
79</tr> 62 </tr>
80<tr>
81 <ti>(<brite>Indigo</brite>)</ti>
82 <ti></ti>
83 <ti></ti>
84 <ti></ti>
85</tr>
86<tr>
87 <ti>(<brite>Octane</brite>)</ti>
88 <ti></ti>
89 <ti></ti>
90 <ti></ti>
91</tr>
92<tr>
93 <ti>(<brite>Octane2</brite>)</ti>
94 <ti></ti>
95 <ti></ti>
96 <ti></ti>
97</tr>
98<tr>
99 <ti>(<brite>Fuel</brite>)</ti>
100 <ti></ti>
101 <ti></ti>
102 <ti></ti>
103</tr>
104<tr>
105 <ti>(<brite>Tezro</brite>)</ti>
106 <ti></ti>
107 <ti></ti>
108 <ti></ti>
109</tr>
110</table> 63</table>
111 64
112</body> 65</body>
113</section> 66
114<section> 67</section>
115<title>Accessories</title> 68
69<section>
70<title>A Note about serial consoles</title>
71<body>
72
73<p>
74If you lack an appropriate Framebuffer, you will be required to use serial
75console. Serial console programs for linux include <c>minicom</c> and
76<c>xc</c>, and for Windows, <c>HyperTerminal</c> and <c>Tera Term Pro</c>. If
77you are running Windows, and intend to use HyperTerminal, it is advised that
78you seek out an updated client from the program's website instead of the one
79installed by default. An upgraded client provides much better serial support
80than the default one installed by Windows.
81</p>
82
116<body> 83</body>
84</section>
85<section>
86<title>User Testimonies &amp; Kernel Configurations</title>
87<body>
88
89<p>
90As an aid to the project, a <uri
91link="http://stuartl.longlandclan.hopto.org/gentoo/mips/">hardware support
92database</uri> has been set up. This support database is intended to provide a
93quick and easy way to determine how well certain configurations are supported.
94The system also allows people to contribute their comments and kernel configs.
95</p>
96
97</body>
98</section>
99</chapter>
100
101<chapter>
102<title>Silicon Graphics Systems -- Stable</title>
103<section>
104<body>
105
106<p>
107The following systems are known to be very stable overall. Just about all the
108core hardware is supported in these systems, and there are very few outstanding
109stability issues at this time.
110</p>
111
112</body>
113</section>
114<section>
115<title>IP22: Indy, Indigo 2 and Challenge S</title>
116<body>
117
118<ul>
119 <li>
120 <b>Processor Options (Stable):</b>
121 <ul>
122 <li>
123 <e>(on Indy and Challenge S)</e>
124 R4000, R4400, R4600, R5000
125 </li>
126 <li>
127 <e>(on Indigo 2)</e>
128 R4000, R4400
129 </li>
130 </ul>
131 </li>
132 <li>
133 <b>Kernel Support:</b>
134 <ul>
135 <li>Linux 2.4: <e>Stable</e></li>
136 <li>Linux 2.6: <e>Experimental</e></li>
137 </ul>
138 </li>
139 <li>
140 <b>Kernel Architecture Support:</b>
141 <ul>
142 <li>32-bit: <e>Stable</e></li>
143 <li>64-bit: <e>Experimental</e></li>
144 </ul>
145 </li>
146 <li>
147 <b>Userland Support:</b>
148 <ul>
149 <li>o32: <e>Stable</e></li>
150 <li>n32: <e>Experimental</e> (Only on Linux 2.6 R5000/RM5200)</li>
151 <li>n64: <e>Not Available In Gentoo</e></li>
152 </ul>
153 </li>
154</ul>
155
156<p>
157At present, only the Newport (XL) graphics framebuffer is supported in Linux.
158Therefore on systems with other framebuffers, you will need to use serial
159console.
160</p>
161
162<p>
163The Challenge S has its RJ-45 connector on a daughter board (Mezz) linked with
164an unsupported SCSI adapter, a WD33C95A. In order for this network connector
165to function, this SCSI bus needs to be activated, however it is not yet
166supported by Linux. As a result of this, the Challenge S can only get network
167connectivity via its AUI connector.
168</p>
169
170<p>
171Indigo2 EISA Support is <e>highly</e> experimental. It isn't very well tested
172and may not work with all hardware. Hardware that it is known to function with
173is listed, and as more compatible hardware is discovered, it will be added.
174Please note that hardware requiring DMA support is currently not functional.
175This includes EISA/ISA-based soundcards. EISA Video cards requiring an
176x86-compatible BIOS are also not functional.
177</p>
178
179</body>
180</section>
181<section>
182<title>IP32: O2</title>
183<body>
184
185<ul>
186 <li>
187 <b>Processor Options:</b>
188 <ul>
189 <li><b>Stable:</b> R5000, RM5200</li>
190 <li><b>Experimental:</b> RM7000</li>
191 <li><b>Unsupported:</b> R10000</li>
192 </ul>
193 </li>
194 <li>
195 <b>Kernel Support:</b>
196 <ul>
197 <li>Linux 2.4: <e>Unsupported in Kernel</e></li>
198 <li>Linux 2.6: <e>Stable</e></li>
199 </ul>
200 </li>
201 <li>
202 <b>Kernel Architecture Support:</b>
203 <ul>
204 <li>32-bit: <e>Unsupported in Kernel</e></li>
205 <li>64-bit: <e>Stable</e></li>
206 </ul>
207 </li>
208 <li>
209 <b>Userland Support:</b>
210 <ul>
211 <li>o32: <e>Stable</e></li>
212 <li>n32: <e>Experimental</e> (Only on Linux 2.6)</li>
213 <li>n64: <e>Not Available In Gentoo</e></li>
214 </ul>
215 </li>
216</ul>
217
218<p>
219The O2 RM7000 Processor support is limited in Linux currently, as it requires a
220fairly recent kernel version (>2.6.7), and has several notable issues. The
221first issue is a problem with scsi at the moment, making the internal disks
222unusable at the current time. The Level 3 (Tertiary) Cache is also disabled
223due to there being no support for this cache in the linux kernel.
224</p>
225
226<p>
227Please be aware that this note only applies to the official SGI RM7000 running
228at 350MHz, not the 600MHz RM7000 that can be assembed using an RM5200 board.
229These "modded" CPU modules for O2 systems are not supported/tested, although,
230in theory, they should be functional, but may suffer from the same problems
231listed above.
232</p>
233
234</body>
235</section>
236</chapter>
237
238<chapter>
239<title>Silicon Graphics Systems -- Experimental/Unstable</title>
240<section>
241<body>
242
243<p>
244The systems listed here are known to run Linux... <e>HOWEVER</e>, in many
245cases, there are known stability issues, and major gaps in the hardware
246support. In short, it will be a rough and bumpy ride.
247</p>
248
249</body>
250</section>
251<section>
252<title>IP27: Origin 200 and 2000</title>
253<body>
254
255<ul>
256 <li>
257 <b>Processor Options <e>(Experimental)</e>:</b>
258 R10000, R12000
259 </li>
260 <li>
261 <b>Kernel Support:</b>
262 <ul>
263 <li>Linux 2.4: <e>Unsupported in Kernel</e></li>
264 <li>Linux 2.6: <e>Experimental</e></li>
265 </ul>
266 </li>
267 <li>
268 <b>Kernel Architecture Support:</b>
269 <ul>
270 <li>32-bit: <e>Unsupported in Kernel</e></li>
271 <li>64-bit: <e>Experimental</e></li>
272 </ul>
273 </li>
274 <li>
275 <b>Userland Support:</b>
276 <ul>
277 <li>o32: <e>Stable</e></li>
278 <li>n32: <e>Experimental</e></li>
279 <li>n64: <e>Not Available In Gentoo</e></li>
280 </ul>
281 </li>
282</ul>
283
284</body>
285</section>
286<section>
287<title>IP28: Indigo 2 Impact (a.k.a Indigo 2 R10k)</title>
288<body>
289
290<ul>
291 <li>
292 <b>Processor Options <e>(Experimental)</e>:</b>
293 R10000
294 </li>
295 <li>
296 <b>Kernel Support:</b>
297 <ul>
298 <li>Linux 2.4: <e>Experimental</e></li>
299 <li>Linux 2.6: <e>Experimental</e></li>
300 </ul>
301 </li>
302 <li>
303 <b>Kernel Architecture Support:</b>
304 <ul>
305 <li>32-bit: <e>Unsupported in Kernel</e></li>
306 <li>64-bit: <e>Experimental</e></li>
307 </ul>
308 </li>
309 <li>
310 <b>Userland Support:</b>
311 <ul>
312 <li>o32: <e>Stable</e></li>
313 <li>n32: <e>Experimental</e> (Only on Linux 2.6)</li>
314 <li>n64: <e>Not Available In Gentoo</e></li>
315 </ul>
316 </li>
317</ul>
318
319<p>
320IP28 Indigo2 Impact support (classified as an Indigo2 system w/ an R10000
321Processor) is <e>very experimental</e>. Most of the work is currently being
322done by Peter Fuerst who maintains patches on his <uri
323link="http://home.alphastar.de/fuerst/download.html">website</uri>. This
324kernel is <e>NOT</e> intended for stable, day-to-day use. The Indigo2 IP28
325system suffers from an issue known as <e>Speculative Execution</e>, a feature
326of the R10000 Processor that is problematic on machines that are <e>Non Cache
327Coherent</e>, such as the IP28 Indigo2 and on R10000/R12000-based IP32 O2
328systems. Details on the nature of Speculative Execution, and the issues it
329poses to the Indigo2 can be found at the following URLs:
330</p>
331
332<ul>
333 <li>
334 MIPS R10000 Microprocessor User's Manual (See <e>PDF Pages 51-55</e>)
335 <uri>http://techpubs.sgi.com/library/manuals/2000/007-2490-001/pdf/007-2490-001.pdf</uri>
336 </li>
337 <li>
338 Post to NetBSD sgimips Mailing List on 29 Jun 2000
339 <uri>http://mail-index.netbsd.org/port-sgimips/2000/06/29/0006.html</uri>
340 </li>
341</ul>
342
343</body>
344</section>
345<section>
346<title>IP30: Octane</title>
347<body>
348
349<ul>
350 <li>
351 <b>Processor Options:</b>
352 <ul>
353 <li><b>Experimental:</b> R10000, R12000</li>
354 <li><b>Unsupported:</b> R14000A</li>
355 </ul>
356 </li>
357 <li>
358 <b>Kernel Support:</b>
359 <ul>
360 <li>Linux 2.4: <e>Unsupported in Kernel</e></li>
361 <li>Linux 2.6: <e>Experimental</e></li>
362 </ul>
363 </li>
364 <li>
365 <b>Kernel Architecture Support:</b>
366 <ul>
367 <li>32-bit: <e>Unsupported in Kernel</e></li>
368 <li>64-bit: <e>Experimental</e></li>
369 </ul>
370 </li>
371 <li>
372 <b>Userland Support:</b>
373 <ul>
374 <li>o32: <e>Stable</e></li>
375 <li>n32: <e>Experimental</e></li>
376 <li>n64: <e>Not Available In Gentoo</e></li>
377 </ul>
378 </li>
379</ul>
380
381<p>
382Octane support in Linux should be regarded as experimental. Support for this
383particular machine from SGI has been progressing quite well and the Linux
384kernel functions reasonably well. The current status for this system may be
385found on <uri link="http://helios.et.put.poznan.pl/~sskowron/ip30/">Stanislaw
386Skowronek's page</uri>. Wider support in Gentoo for this system will be
387available in the future, so watch this space closely for more details.
388</p>
389
390</body>
391</section>
392</chapter>
393
394<chapter>
395<title>Silicon Graphics Systems -- Unsupported</title>
396<section>
397<body>
398
399<p>
400Just about all of these systems are totally unsupported at the kernel level --
401making a full Linux system totally impossible. Little is known about a lot of
402the systems listed here -- therefore any support in the near future is highly
403unlikely. You may wish to keep an eye on the <uri
404link="http://www.linux-mips.org">Linux/MIPS website</uri> for any news of ports
405-- either that, or start your own. :-)
406</p>
407
408<ul>
409 <li>IP12: Iris Indigo (R3000 CPU)</li>
410 <li>IP20: Iris Indigo (R4000 or R4400 CPU)</li>
411 <li>IP26: Indigo 2 Power (R8000 CPU)</li>
412 <li>IP34: Fuel (R14000A or R16000 CPU)</li>
413 <li>IP35: Origin 3000 (R14000 or R14000A CPU)</li>
414 <li>IP45: Origin 300 (R14000 CPU)</li>
415 <li>IP53: Origin 350 &amp; Tezro (R16000 CPU)</li>
416</ul>
417
418</body>
419</section>
420</chapter>
421
422<chapter>
423<title>Silicon Graphics Accessories</title>
424<section>
425<body>
426
427<p>
428As with most systems, there is quite wide array of peripherals that one can
429obtain for Silicon Graphics systems. While a lot of these work in IRIX, Linux
430support is a bit touch-and-go on some of these items. The following table
431lists the support for each device.
432</p>
117 433
118<table> 434<table>
119<tr> 435 <tr>
120 <th>Supported</th> 436 <th>Unsupported/Untested</th>
121 <th>Experimental</th> 437 <th>Experimental Support</th>
122 <th>Unsupported</th> 438 <th>Stable Support</th>
123</tr> 439 </tr>
124<tr> 440 <tr>
125 <ti>GIO32 Slots on Indy</ti> 441 <ti>Indy/Indigo2: Impact &amp; Extreme/XZ graphics chipsets</ti>
126 <ti>Indy I2C subsystem &amp; IndyCam</ti> 442 <ti>Indy: I2C/VINO subsystem &amp; IndyCam</ti>
127 <ti>Impact &amp; Extreme graphics chipsets (1)</ti> 443 <ti>Indy/Indigo2: XL Graphics Card (Newport)</ti>
128</tr> 444 </tr>
129<tr> 445 <tr>
130 <ti>XL Graphics Card (Newport) [Indy &amp; Indigo2]</ti> 446 <ti>Indy: Phobos G130 10/100Mbps NIC</ti>
131 <ti></ti> 447 <ti>O2: GBE Framebuffer</ti>
132 <ti>WD33C95A SCSI Adapter/RJ-45 Daughter Card [Challenge S] (2)</ti> 448 <ti>Indy/Indigo2: SGI Seeq Ethernet 10Mbps</ti>
133</tr> 449 </tr>
134<tr> 450 <tr>
135 <ti></ti> 451 <ti>Indigo2: GIO64 Slots</ti>
136 <ti></ti> 452 <ti>O2: PCI Slot</ti>
137 <ti>GIO64 Slots on Indigo2/Challenge S</ti> 453 <ti>Indy/Indigo2: WD33C93 SCSI</ti>
138</tr> 454 </tr>
139<tr> 455 <tr>
140 <ti></ti>
141 <ti></ti>
142 <ti>Phobos G130 10/100Mbps NIC [Indy]</ti> 456 <ti>Indigo2: Phobos G160 10/100Mbps NIC</ti>
457 <ti>Octane: Keyboard</ti>
458 <ti>Indy/Indigo2: HAL2 Sound/Audio</ti>
143</tr> 459 </tr>
144<tr> 460 <tr>
145 <ti></ti> 461 <ti>Challenge S: WD33C95A SCSI Adapter/RJ-45 Daughter Card</ti>
146 <ti></ti> 462 <ti>Octane: Mardi Gras (MGRAS) Graphics</ti>
147 <ti>Phobos G160 10/100Mbps NIC [Indigo2]</ti> 463 <ti>Indy/Indigo2: Parallel Port</ti>
148</tr> 464 </tr>
465 <tr>
466 <ti>O2: VICE Subsystem</ti>
467 <ti>Octane: QLogic ISP1040B SCSI</ti>
468 <ti>Indy/Indigo2: Serial Port</ti>
469 </tr>
470 <tr>
471 <ti>Octane: SMP Support</ti>
472 <ti>Octane: RAD1 Audio</ti>
473 <ti>O2: SGI MACE Ethernet 10/100Mbps</ti>
474 </tr>
475 <tr>
476 <ti>Octane: V6/V8/V10/V12 Graphics (Odyssey)</ti>
477 <ti>Origin: IOC3 Ethernet 10/100Mbps</ti>
478 <ti>O2: Adaptec AIC7880 SCSI</ti>
479 </tr>
480 <tr>
481 <ti/>
482 <ti>Origin: QLogic ISP1020 SCSI</ti>
483 <ti>O2: Serial Port</ti>
484 </tr>
485 <tr>
486 <ti/>
487 <ti>Indigo2 EISA: 3COM 3c597 10/100Mbps</ti>
488 <ti>Indigo2 ISA: Parallel Port Card (PC-Style)</ti>
489 </tr>
490 <tr>
491 <ti/>
492 <ti>O2 PCI: ALi 5273 USB 2.0 (Req. Kernel >=2.6.8.1)</ti>
493 <ti>Indigo2 ISA: NE2000 Compatible 10Mbps NIC (RTL8019)</ti>
494 </tr>
149</table> 495</table>
150 496
151<note>
152(1): If you lack an appropriate Framebuffer, you will be required to use serial
153console. Serial console programs for linux include minicom and xc, and for
154Windows, HyperTerminal and Tera Term Pro. If you are running Windows, and intend
155to use HyperTerminal, it is advised that you seek out an updated client from the
156program's website instead of the one installed by default. An upgraded client
157provides much better serial support than the default one installed by Windows.
158</note>
159
160<note>
161(2): The Challenge S has its RJ-45 connector on a daughter board linked with an
162unsupported SCSI adapter, a WD33C95A. In order for this network connector to
163function, this SCSI bus needs to be activated, however it is not yet supported
164by Linux. As a result of this, the Challenge S can only get network connectivity
165via its AUI connector.
166</note>
167
168<table>
169<tr><th>Supported Indogo2 EISA Slots (3)</th></tr>
170<tr><ti>ISA Parallel Port Card (PC-Style)</ti></tr>
171<tr><ti>ISA NE2000 Compatible 10Mbps NIC (RTL8019)</ti></tr>
172</table>
173
174<note>
175(3): Indigo2 EISA Support is <e>highly</e> experimental. It isn't very well
176tested and may not work with all hardware. Hardware that it is known to function
177with is listed, and as more compatible hardware is discovered, it will be added.
178Please note that hardware requiring DMA support is currently not functional.
179This includes EISA/ISA-based soundcards. EISA Video cards requiring an
180x86-compatible BIOS are also not functional.
181</note>
182
183<p>
184The maximum amount of RAM supported in the Indigo/Indy systems is 256MB, due to
185no HIGHMEM support in 32-bit kernels. Only a 64-bit kernel can properly detect
186RAM amounts greater than 256MB on these systems.
187</p>
188
189<p>
190MIPS Little-Endian (mipsel) is currently being tested on a Cobalt RaQ2, however
191progress is currently hindered by a flaky Tulip NIC driver in the 2.4.21 mips
192kernels that makes running Gentoo a bit difficult. Any help in this effort is
193appreciated.
194</p>
195
196<p>
197The Playstation 2 is a specialized MIPS system, using an R5900 MIPS processor.
198The support for this processor is extremely limited, and only found in the
199development toolchains available in the PS2 Linux Kit and via some patches
200available on the PS2 Linux Homepage. There was a limited amount of work done on
201porting Gentoo to the PS2 Linux Kit, however it is incomplete as of this
202writing. Those interested may visit
203<uri>http://playstation2-linux.com/projects/gentoo-ps2/</uri> if they are
204interested in assisting or completing the port. Additional information on PS2
205Compiler Toolchains can be found at <uri>http://ps2dev.sf.net/</uri>.
206</p>
207
208<p>
209Gentoo/MIPS has also been installed on a SiByte BCM1250 Machine, a Big-endian,
210dual-processor MIPS machine. Currently, only one person to date has done this,
211but more people willing to test Gentoo on such hardware are welcomed to try and
212report results.
213</p>
214
215</body> 497</body>
216</section>
217</chapter>
218<chapter>
219<title>Minimum Requirements</title>
220<section> 498</section>
221<body>
222
223<ul>
224 <li>
225 128MB RAM - More ram is better, as Gentoo currently uses the gcc-3.2.x and
226 greater versions of gcc. These versions of gcc tend to consume more memory
227 than their older 2.95.x counterparts, and on the merging of large packages,
228 anything less than 128MB of ram could make gcc fail to compile the package,
229 or mysteriously stop in the middle of compiliation. A recommended amount of
230 ram is 160MB.
231 </li>
232 <li>
233 9GB Hard Drive Space - 9GB is more or less the recommended minimum. It is
234 enough space to install Gentoo on and leaves extra space for daily
235 activities on the machine. Gentoo has been installed on smaller drives, the
236 smallest being a 3.2GB drive, but it does not leave alot of room for much
237 else.
238 </li>
239</ul>
240
241</body>
242</section>
243</chapter>
244<chapter> 499</chapter>
245<title>MIPS Optimizations</title> 500
501<chapter>
502<title>Cobalt Servers -- Stable</title>
503<section>
504<body>
505
506<p>
507The Cobalt servers are a set of machines all based around the QED RM523[01]
508CPU. They came in two varieties, the RaQ -- a rackmounted model, and the Qube,
509a small desktop model (1ft. cube). The big difference between these systems
510and the SGI systems above, is that these systems are <e>little endian</e>
511(<c>mipsel</c>) as opposed to <e>big endian</e> (<c>mips</c>).
512</p>
513
514<p>
515These were also sold under an OEM arragement to other companies, examples of
516this are the Gateway Microserver (Qube 2) and the Seagate NasRaQ (RaQ 2).
517</p>
518
519</body>
246<section> 520</section>
247<title>CFLAGS and CXXFLAGS</title> 521<section>
522<title>Qube/Raq 2800 (a.k.a Qube/Raq 2)</title>
248<body> 523<body>
249 524
250<p>
251Although unusual in a "requirements" document, we just don't want to hide this
252from you :-) Discussed in more detail below are the MIPS ISA Levels, which
253enable or disable certain features in the processor, depending on what ISA level
254the processor conforms to.
255</p>
256
257<ul> 525<ul>
258 <li> 526 <li><b>Processor:</b> QED RM5231 @ 250MHz</li>
259 MIPS1 (<c>-march=mips1</c>) enables instructions from level 1 of the MIPS
260 ISA. This is the default. r3000 is the default cpu-type at this ISA level.
261 </li> 527 <li>
528 <b>Kernel Version Support:</b>
529 <ul>
530 <li>Linux 2.4: <e>Stable</e></li>
531 <li>Linux 2.6: <e>Stable</e></li>
532 </ul>
262 <li> 533 </li>
263 MIPS2 (<c>-march=mips2</c>) enables instructions from level 2 of the MIPS
264 ISA (branch likely, square root instructions). r6000 is the default
265 cpu-type at this ISA level.
266 </li> 534 <li>
535 <b>Kernel Architecture Support:</b>
536 <ul>
537 <li>32-bit: <e>Stable</e></li>
538 <li>64-bit: <e>Highly Experimental</e></li>
539 </ul>
267 <li> 540 </li>
268 MIPS3 (<c>-march=mips3</c>) enables instructions from level 3 of the MIPS
269 ISA (64-bit instructions). r4000 is the default cpu-type at this ISA
270 level.
271 </li> 541 <li>
542 <b>Userland Support:</b>
543 <ul>
544 <li>o32: <e>Stable</e></li>
545 <li>n32: <e>Not Available In Gentoo</e></li>
546 <li>n64: <e>Not Available In Gentoo</e></li>
547 </ul>
272 <li> 548 </li>
273 MIPS4 (<c>-march=mips4</c>) enables instructions from level 4 of the MIPS 549</ul>
274 ISA (conditional move, prefetch, enhanced FPU instructions). r8000 is the 550
275 default cpu-type at this ISA level. 551</body>
552</section>
553</chapter>
554
555<chapter>
556<title>Cobalt Servers -- Experimental</title>
557<section>
558<title>Raq 2700 (a.k.a Raq 1)</title>
559<body>
560
561<ul>
562 <li><b>Processor:</b> QED RM5230 @ 150MHz</li>
563 <li>
564 <b>Kernel Version Support:</b>
565 <ul>
566 <li>Linux 2.4: <e>Experimental</e></li>
567 <li>Linux 2.6: <e>Untested In Gentoo</e></li>
568 </ul>
569 </li>
570 <li>
571 <b>Kernel Architecture Support:</b>
572 <ul>
573 <li>32-bit: <e>Experimental</e></li>
574 <li>64-bit: <e>Untested In Gentoo</e></li>
575 </ul>
576 </li>
577 <li>
578 <b>Userland Support:</b>
579 <ul>
580 <li>o32: <e>Experimental</e></li>
581 <li>n32: <e>Not Available In Gentoo</e></li>
582 <li>n64: <e>Not Available In Gentoo</e></li>
583 </ul>
584 </li>
585</ul>
586
587</body>
588</section>
589</chapter>
590
591<chapter>
592<title>Cobalt Servers -- Unsupported</title>
593<section>
594<title>Qube 2700 (a.k.a Qube 1)</title>
595<body>
596
597<p>
598The Qube 2700 was the first of this whole subarchitecture. Unfortunately, it
599lacks a serial port, making installation at present, damn near impossible.
600We're looking into ways we can support this system, but as none of the
601developers have access to one of these machines, we have no way to test our
602efforts. You may wish to have a look at <uri
603link="http://www.metzner.org/projects/qube/">Jan Metzner's page</uri> for more
604information.
605</p>
606
607<ul>
608 <li><b>Processor:</b> QED RM5230 @ 150MHz</li>
609 <li>
610 <b>Kernel Version Support:</b>
611 <ul>
612 <li>Linux 2.4: <e>Untested In Gentoo</e></li>
613 <li>Linux 2.6: <e>Untested In Gentoo</e></li>
614 </ul>
615 </li>
616 <li>
617 <b>Kernel Architecture Support:</b>
618 <ul>
619 <li>32-bit: <e>Untested In Gentoo</e></li>
620 <li>64-bit: <e>Untested In Gentoo</e></li>
621 </ul>
622 </li>
623 <li>
624 <b>Userland Support:</b>
625 <ul>
626 <li>o32: <e>Untested In Gentoo</e></li>
627 <li>n32: <e>Not Available In Gentoo</e></li>
628 <li>n64: <e>Not Available In Gentoo</e></li>
629 </ul>
276 </li> 630 </li>
277</ul> 631</ul>
278 632
279</body> 633</body>
280</section> 634</section>

Legend:
Removed from v.1.1  
changed lines
  Added in v.1.7

  ViewVC Help
Powered by ViewVC 1.1.20