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

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

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.1 - (show annotations) (download) (as text)
Mon Dec 15 20:54:30 2003 UTC (10 years, 8 months ago) by swift
Branch: MAIN
File MIME type: application/xml
MIPS Requirements (hardware)

1 <?xml version='1.0' encoding="UTF-8"?>
2 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3 <guide link="/doc/en/mips-requirements.xml">
4 <title>Gentoo MIPS Hardware Requirements</title>
5 <author title="Author">
6 <mail link="kumba@gentoo.org">Joshua Kinard</mail>
7 </author>
8
9 <abstract>
10 This document informs you about the supported MIPS hardware and the issues you
11 can come across.
12 </abstract>
13 <version>0.1</version>
14 <date>December 15, 2003</date>
15 <license/>
16 <chapter>
17 <title>Supported and Unsupported Hardware</title>
18 <section>
19 <title>Introduction</title>
20 <body>
21
22 <p>
23 Not many sites give you a quick overview on the supported MIPS hardware. To be
24 able to give you an idea on how the MIPS support is progressing we will list as
25 much hardware-information as possible. If you still have questions, don't
26 hesitate to ask <mail link="kumba@gentoo.org">Joshua Kinard</mail>.
27 </p>
28
29 <p>
30 In the support-list, we use "[...]" with <c>blue</c> color to denote
31 experimental support. Unsupported items are embraced by "(...)" and colored in
32 <brite>red</brite>.
33 </p>
34
35 </body>
36 </section>
37 <section>
38 <title>MIPS Systems</title>
39 <body>
40
41 <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>
69 [<i>R5000</i>], [<i>RM5200</i>], (<brite>R10000</brite>), [<i>R12000</i>]
70 </ti>
71 <ti>[<i>32-bit (userland)</i>], [<i>64-bit (kernel)</i>]</ti>
72 <ti>(<brite>2.6</brite>), [<i>2.6</i>]</ti>
73 </tr>
74 <tr>
75 <ti>[<i>Origin</i>]</ti>
76 <ti>[<i>R10000</i>]</ti>
77 <ti>[<i>32-bit (userland), 64-bit (kernel)</i>]</ti>
78 <ti>[<i>2.4</i>], [<i>2.6</i>]</ti>
79 </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>
111
112 </body>
113 </section>
114 <section>
115 <title>Accessories</title>
116 <body>
117
118 <table>
119 <tr>
120 <th>Supported</th>
121 <th>Experimental</th>
122 <th>Unsupported</th>
123 </tr>
124 <tr>
125 <ti>GIO32 Slots on Indy</ti>
126 <ti>Indy I2C subsystem &amp; IndyCam</ti>
127 <ti>Impact &amp; Extreme graphics chipsets (1)</ti>
128 </tr>
129 <tr>
130 <ti>XL Graphics Card (Newport) [Indy &amp; Indigo2]</ti>
131 <ti></ti>
132 <ti>WD33C95A SCSI Adapter/RJ-45 Daughter Card [Challenge S] (2)</ti>
133 </tr>
134 <tr>
135 <ti></ti>
136 <ti></ti>
137 <ti>GIO64 Slots on Indigo2/Challenge S</ti>
138 </tr>
139 <tr>
140 <ti></ti>
141 <ti></ti>
142 <ti>Phobos G130 10/100Mbps NIC [Indy]</ti>
143 </tr>
144 <tr>
145 <ti></ti>
146 <ti></ti>
147 <ti>Phobos G160 10/100Mbps NIC [Indigo2]</ti>
148 </tr>
149 </table>
150
151 <note>
152 (1): If you lack an appropriate Framebuffer, you will be required to use serial
153 console. Serial console programs for linux include minicom and xc, and for
154 Windows, HyperTerminal and Tera Term Pro. If you are running Windows, and intend
155 to use HyperTerminal, it is advised that you seek out an updated client from the
156 program's website instead of the one installed by default. An upgraded client
157 provides 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
162 unsupported SCSI adapter, a WD33C95A. In order for this network connector to
163 function, this SCSI bus needs to be activated, however it is not yet supported
164 by Linux. As a result of this, the Challenge S can only get network connectivity
165 via 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
176 tested and may not work with all hardware. Hardware that it is known to function
177 with is listed, and as more compatible hardware is discovered, it will be added.
178 Please note that hardware requiring DMA support is currently not functional.
179 This includes EISA/ISA-based soundcards. EISA Video cards requiring an
180 x86-compatible BIOS are also not functional.
181 </note>
182
183 <p>
184 The maximum amount of RAM supported in the Indigo/Indy systems is 256MB, due to
185 no HIGHMEM support in 32-bit kernels. Only a 64-bit kernel can properly detect
186 RAM amounts greater than 256MB on these systems.
187 </p>
188
189 <p>
190 MIPS Little-Endian (mipsel) is currently being tested on a Cobalt RaQ2, however
191 progress is currently hindered by a flaky Tulip NIC driver in the 2.4.21 mips
192 kernels that makes running Gentoo a bit difficult. Any help in this effort is
193 appreciated.
194 </p>
195
196 <p>
197 The Playstation 2 is a specialized MIPS system, using an R5900 MIPS processor.
198 The support for this processor is extremely limited, and only found in the
199 development toolchains available in the PS2 Linux Kit and via some patches
200 available on the PS2 Linux Homepage. There was a limited amount of work done on
201 porting Gentoo to the PS2 Linux Kit, however it is incomplete as of this
202 writing. Those interested may visit
203 <uri>http://playstation2-linux.com/projects/gentoo-ps2/</uri> if they are
204 interested in assisting or completing the port. Additional information on PS2
205 Compiler Toolchains can be found at <uri>http://ps2dev.sf.net/</uri>.
206 </p>
207
208 <p>
209 Gentoo/MIPS has also been installed on a SiByte BCM1250 Machine, a Big-endian,
210 dual-processor MIPS machine. Currently, only one person to date has done this,
211 but more people willing to test Gentoo on such hardware are welcomed to try and
212 report results.
213 </p>
214
215 </body>
216 </section>
217 </chapter>
218 <chapter>
219 <title>Minimum Requirements</title>
220 <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>
245 <title>MIPS Optimizations</title>
246 <section>
247 <title>CFLAGS and CXXFLAGS</title>
248 <body>
249
250 <p>
251 Although unusual in a "requirements" document, we just don't want to hide this
252 from you :-) Discussed in more detail below are the MIPS ISA Levels, which
253 enable or disable certain features in the processor, depending on what ISA level
254 the processor conforms to.
255 </p>
256
257 <ul>
258 <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>
262 <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>
267 <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>
272 <li>
273 MIPS4 (<c>-march=mips4</c>) enables instructions from level 4 of the MIPS
274 ISA (conditional move, prefetch, enhanced FPU instructions). r8000 is the
275 default cpu-type at this ISA level.
276 </li>
277 </ul>
278
279 </body>
280 </section>
281 </chapter>
282 </guide>

  ViewVC Help
Powered by ViewVC 1.1.20