/[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.3 - (show annotations) (download) (as text)
Sun Apr 11 10:52:16 2004 UTC (10 years, 5 months ago) by cam
Branch: MAIN
Changes since 1.2: +11 -11 lines
File MIME type: application/xml
Fixed coding style due to the forthcoming DTD enforcement.
Sorry for all the translators :) (including me, argh)

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
14 <license/>
15
16 <version>0.1</version>
17 <date>December 15, 2003</date>
18
19 <chapter>
20 <title>Supported and Unsupported Hardware</title>
21 <section>
22 <title>Introduction</title>
23 <body>
24
25 <p>
26 Not many sites give you a quick overview on the supported MIPS hardware. To be
27 able to give you an idea on how the MIPS support is progressing we will list as
28 much hardware-information as possible. If you still have questions, don't
29 hesitate to ask <mail link="kumba@gentoo.org">Joshua Kinard</mail>.
30 </p>
31
32 <p>
33 In the support-list, we use "[...]" with <c>blue</c> color to denote
34 experimental support. Unsupported items are embraced by "(...)" and colored in
35 <brite>red</brite>.
36 </p>
37
38 </body>
39 </section>
40 <section>
41 <title>MIPS Systems</title>
42 <body>
43
44 <table>
45 <tr>
46 <th>System</th>
47 <th>CPUs</th>
48 <th>Architectures</th>
49 <th>Kernels</th>
50 </tr>
51 <tr>
52 <ti>Indy</ti>
53 <ti>R4000, R4400, R4600, R5000</ti>
54 <ti>32-bit, [<c>64-bit (kernel)</c>]</ti>
55 <ti>2.4, (<brite>2.6</brite>)</ti>
56 </tr>
57 <tr>
58 <ti>Indigo2</ti>
59 <ti>R4000, R4400, R4600, (<brite>R8000</brite>), (<brite>R10000</brite>)</ti>
60 <ti>32-bit, [<c>64-bit (kernel) IP22</c>]</ti>
61 <ti>2.4, (<brite>2.6</brite>)</ti>
62 </tr>
63 <tr>
64 <ti>Challenge S</ti>
65 <ti>R4000, R4400, R4600, R5000</ti>
66 <ti>32-bit, [<c>64-bit (kernel)</c>]</ti>
67 <ti>2.4, (<brite>2.6</brite>)</ti>
68 </tr>
69 <tr>
70 <ti>[<c>O2</c>]</ti>
71 <ti>
72 [<c>R5000</c>], [<c>RM5200</c>], (<brite>R10000</brite>), [<c>R12000</c>]
73 </ti>
74 <ti>[<c>32-bit (userland)</c>], [<c>64-bit (kernel)</c>]</ti>
75 <ti>(<brite>2.6</brite>), [<c>2.6</c>]</ti>
76 </tr>
77 <tr>
78 <ti>[<c>Origin</c>]</ti>
79 <ti>[<c>R10000</c>]</ti>
80 <ti>[<c>32-bit (userland), 64-bit (kernel)</c>]</ti>
81 <ti>[<c>2.4</c>], [<c>2.6</c>]</ti>
82 </tr>
83 <tr>
84 <ti>(<brite>Indigo</brite>)</ti>
85 <ti></ti>
86 <ti></ti>
87 <ti></ti>
88 </tr>
89 <tr>
90 <ti>(<brite>Octane</brite>)</ti>
91 <ti></ti>
92 <ti></ti>
93 <ti></ti>
94 </tr>
95 <tr>
96 <ti>(<brite>Octane2</brite>)</ti>
97 <ti></ti>
98 <ti></ti>
99 <ti></ti>
100 </tr>
101 <tr>
102 <ti>(<brite>Fuel</brite>)</ti>
103 <ti></ti>
104 <ti></ti>
105 <ti></ti>
106 </tr>
107 <tr>
108 <ti>(<brite>Tezro</brite>)</ti>
109 <ti></ti>
110 <ti></ti>
111 <ti></ti>
112 </tr>
113 </table>
114
115 </body>
116 </section>
117 <section>
118 <title>Accessories</title>
119 <body>
120
121 <table>
122 <tr>
123 <th>Supported</th>
124 <th>Experimental</th>
125 <th>Unsupported</th>
126 </tr>
127 <tr>
128 <ti>GIO32 Slots on Indy</ti>
129 <ti>Indy I2C subsystem &amp; IndyCam</ti>
130 <ti>Impact &amp; Extreme graphics chipsets (1)</ti>
131 </tr>
132 <tr>
133 <ti>XL Graphics Card (Newport) [Indy &amp; Indigo2]</ti>
134 <ti></ti>
135 <ti>WD33C95A SCSI Adapter/RJ-45 Daughter Card [Challenge S] (2)</ti>
136 </tr>
137 <tr>
138 <ti></ti>
139 <ti></ti>
140 <ti>GIO64 Slots on Indigo2/Challenge S</ti>
141 </tr>
142 <tr>
143 <ti></ti>
144 <ti></ti>
145 <ti>Phobos G130 10/100Mbps NIC [Indy]</ti>
146 </tr>
147 <tr>
148 <ti></ti>
149 <ti></ti>
150 <ti>Phobos G160 10/100Mbps NIC [Indigo2]</ti>
151 </tr>
152 </table>
153
154 <note>
155 (1): If you lack an appropriate Framebuffer, you will be required to use serial
156 console. Serial console programs for linux include minicom and xc, and for
157 Windows, HyperTerminal and Tera Term Pro. If you are running Windows, and intend
158 to use HyperTerminal, it is advised that you seek out an updated client from the
159 program's website instead of the one installed by default. An upgraded client
160 provides much better serial support than the default one installed by Windows.
161 </note>
162
163 <note>
164 (2): The Challenge S has its RJ-45 connector on a daughter board linked with an
165 unsupported SCSI adapter, a WD33C95A. In order for this network connector to
166 function, this SCSI bus needs to be activated, however it is not yet supported
167 by Linux. As a result of this, the Challenge S can only get network connectivity
168 via its AUI connector.
169 </note>
170
171 <table>
172 <tr><th>Supported Indogo2 EISA Slots (3)</th></tr>
173 <tr><ti>ISA Parallel Port Card (PC-Style)</ti></tr>
174 <tr><ti>ISA NE2000 Compatible 10Mbps NIC (RTL8019)</ti></tr>
175 </table>
176
177 <note>
178 (3): Indigo2 EISA Support is <e>highly</e> experimental. It isn't very well
179 tested and may not work with all hardware. Hardware that it is known to function
180 with is listed, and as more compatible hardware is discovered, it will be added.
181 Please note that hardware requiring DMA support is currently not functional.
182 This includes EISA/ISA-based soundcards. EISA Video cards requiring an
183 x86-compatible BIOS are also not functional.
184 </note>
185
186 <p>
187 The maximum amount of RAM supported in the Indigo/Indy systems is 256MB, due to
188 no HIGHMEM support in 32-bit kernels. Only a 64-bit kernel can properly detect
189 RAM amounts greater than 256MB on these systems.
190 </p>
191
192 <p>
193 MIPS Little-Endian (mipsel) is currently being tested on a Cobalt RaQ2, however
194 progress is currently hindered by a flaky Tulip NIC driver in the 2.4.21 mips
195 kernels that makes running Gentoo a bit difficult. Any help in this effort is
196 appreciated.
197 </p>
198
199 <p>
200 The Playstation 2 is a specialized MIPS system, using an R5900 MIPS processor.
201 The support for this processor is extremely limited, and only found in the
202 development toolchains available in the PS2 Linux Kit and via some patches
203 available on the PS2 Linux Homepage. There was a limited amount of work done on
204 porting Gentoo to the PS2 Linux Kit, however it is incomplete as of this
205 writing. Those interested may visit
206 <uri>http://playstation2-linux.com/projects/gentoo-ps2/</uri> if they are
207 interested in assisting or completing the port. Additional information on PS2
208 Compiler Toolchains can be found at <uri>http://ps2dev.sf.net/</uri>.
209 </p>
210
211 <p>
212 Gentoo/MIPS has also been installed on a SiByte BCM1250 Machine, a Big-endian,
213 dual-processor MIPS machine. Currently, only one person to date has done this,
214 but more people willing to test Gentoo on such hardware are welcomed to try and
215 report results.
216 </p>
217
218 </body>
219 </section>
220 </chapter>
221 <chapter>
222 <title>Minimum Requirements</title>
223 <section>
224 <body>
225
226 <ul>
227 <li>
228 128MB RAM - More ram is better, as Gentoo currently uses the gcc-3.2.x and
229 greater versions of gcc. These versions of gcc tend to consume more memory
230 than their older 2.95.x counterparts, and on the merging of large packages,
231 anything less than 128MB of ram could make gcc fail to compile the package,
232 or mysteriously stop in the middle of compiliation. A recommended amount of
233 ram is 160MB.
234 </li>
235 <li>
236 9GB Hard Drive Space - 9GB is more or less the recommended minimum. It is
237 enough space to install Gentoo on and leaves extra space for daily
238 activities on the machine. Gentoo has been installed on smaller drives, the
239 smallest being a 3.2GB drive, but it does not leave alot of room for much
240 else.
241 </li>
242 </ul>
243
244 </body>
245 </section>
246 </chapter>
247 <chapter>
248 <title>MIPS Optimizations</title>
249 <section>
250 <title>CFLAGS and CXXFLAGS</title>
251 <body>
252
253 <p>
254 Although unusual in a "requirements" document, we just don't want to hide this
255 from you :-) Discussed in more detail below are the MIPS ISA Levels, which
256 enable or disable certain features in the processor, depending on what ISA level
257 the processor conforms to.
258 </p>
259
260 <ul>
261 <li>
262 MIPS1 (<c>-march=mips1</c>) enables instructions from level 1 of the MIPS
263 ISA. This is the default. r3000 is the default cpu-type at this ISA level.
264 </li>
265 <li>
266 MIPS2 (<c>-march=mips2</c>) enables instructions from level 2 of the MIPS
267 ISA (branch likely, square root instructions). r6000 is the default
268 cpu-type at this ISA level.
269 </li>
270 <li>
271 MIPS3 (<c>-march=mips3</c>) enables instructions from level 3 of the MIPS
272 ISA (64-bit instructions). r4000 is the default cpu-type at this ISA
273 level.
274 </li>
275 <li>
276 MIPS4 (<c>-march=mips4</c>) enables instructions from level 4 of the MIPS
277 ISA (conditional move, prefetch, enhanced FPU instructions). r8000 is the
278 default cpu-type at this ISA level.
279 </li>
280 </ul>
281
282 </body>
283 </section>
284 </chapter>
285 </guide>

  ViewVC Help
Powered by ViewVC 1.1.20