/[gxemul]/trunk/doc/intro.html
This is repository of my old source code which isn't updated any more. Go to git.rot13.org for current projects!
ViewVC logotype

Diff of /trunk/doc/intro.html

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

revision 2 by dpavlin, Mon Oct 8 16:17:48 2007 UTC revision 12 by dpavlin, Mon Oct 8 16:18:38 2007 UTC
# Line 1  Line 1 
1  <html>  <html><head><title>Gavare's eXperimental Emulator:&nbsp;&nbsp;&nbsp;Introduction</title>
2  <head><title>GXemul documentation: Introduction</title>  <meta name="robots" content="noarchive,nofollow,noindex"></head>
3  </head>  <body bgcolor="#f8f8f8" text="#000000" link="#4040f0" vlink="#404040" alink="#ff0000">
4  <body bgcolor="#ffffff" text="#000000" link="#4040f0" vlink="#404040" alink="#ff0000">  <table border=0 width=100% bgcolor="#d0d0d0"><tr>
5  <p>  <td width=100% align=center valign=center><table border=0 width=100%><tr>
6  <table width="100%">  <td align="left" valign=center bgcolor="#d0efff"><font color="#6060e0" size="6">
7    <tr><td width="100%" bgcolor="#808070"><font color="#ffffe0" size="6">  <b>Gavare's eXperimental Emulator:&nbsp;&nbsp;&nbsp;</b></font>
8    <b>GXemul documentation: Introduction</b></font></td></tr>  <font color="#000000" size="6"><b>Introduction</b>
9  </table>  </font></td></tr></table></td></tr></table><p>
 <p>  
 <!-- The first 10 lines are cut away by the homepage updating script.  -->  
   
10    
11  <!--  <!--
12    
13  $Id: intro.html,v 1.30 2005/04/07 15:43:15 debug Exp $  $Id: intro.html,v 1.61 2005/08/16 05:15:24 debug Exp $
14    
15  Copyright (C) 2003-2005  Anders Gavare.  All rights reserved.  Copyright (C) 2003-2005  Anders Gavare.  All rights reserved.
16    
# Line 50  SUCH DAMAGE. Line 47  SUCH DAMAGE.
47  <p>  <p>
48  <ul>  <ul>
49    <li><a href="#overview">Overview</a>    <li><a href="#overview">Overview</a>
50    <li><a href="#free">Is GXemul free software?</a>    <li><a href="#free">Is GXemul Free software?</a>
51    <li><a href="#build">How to compile/build the emulator</a>    <li><a href="#build">How to compile/build the emulator</a>
52      <li><a href="#run">How to run the emulator</a>
53    <li><a href="#cpus">Which CPU types does GXemul emulate?</a>    <li><a href="#cpus">Which CPU types does GXemul emulate?</a>
54    <li><a href="#accuracy">Emulation accuracy</a>    <li><a href="#accuracy">Emulation accuracy</a>
55    <li><a href="#emulmodes">Which machines does GXemul emulate?</a>    <li><a href="#emulmodes">Which machines does GXemul emulate?</a>
56    <li><a href="#guestos">Which guest OSes are possible to run?</a>    <li><a href="#guestos">Which guest OSes are possible to run in GXemul?</a>
57  </ul>  </ul>
58    
59    
# Line 66  SUCH DAMAGE. Line 64  SUCH DAMAGE.
64  <a name="overview"></a>  <a name="overview"></a>
65  <h3>Overview:</h3>  <h3>Overview:</h3>
66    
67  GXemul is a machine emulator, which can be used to experiment with  GXemul is an experimental instruction-level machine emulator. It can be
68  binary code for (among others) MIPS-based machines. Several emulation  used to run binary code for MIPS-based machines, regardless of host
69  modes are available. For some emulation modes, processors and surrounding  platform. Several emulation modes are available. For some modes,
70  hardware components are emulated well enough to let unmodified operating  processors and surrounding hardware components are emulated well enough to
71  systems run as if they were running on a real machine.  let unmodified operating systems run as if they were running on a real
72    machine.
73    
74    <p>(Non-MIPS emulation modes are also under development, but so far none
75    of those modes has reached the completeness required to run unmodified
76    operating systems.)
77    
78    <p>Devices and CPUs are not simulated with 100% accuracy. They are only
79    ``faked'' well enough to make operating systems (e.g. NetBSD) run without
80    complaining too much. Still, the emulator could be of interest for
81    academic research and experiments, such as when learning how to write
82    operating system code.
83    
84    <p>The emulator is written in C, does not depend on external libraries
85    (except X11, but that is optional), and should compile and run on most
86    Unix-like systems. If it doesn't, then that is a bug.
87    
88    <p>The emulator contains code which tries to emulate the workings of CPUs
89    and surrounding hardware found in real machines, but it does not contain
90    any ROM code. You will need some form of program (in binary form) to run
91    in the emulator. For many emulation modes, PROM calls are handled by the
92    emulator itself, so you do not need to use any ROM image at all.
93    
94  <p>  <p>You can use pre-compiled kernels (for example NetBSD kernels, or
95  It is important to keep in mind that devices and CPUs are not really  Linux), or other programs that are in binary format, and in some cases
96  emulated correctly, they are only "faked" well enough to make eg. NetBSD  even actual ROM images. A couple of different file formats are supported
97  run. Still, the emulator could be of interest for academic research and  (ELF, a.out, ECOFF, SREC, and raw binaries).
98  experiments, such as when learning how to write an OS for a real machine,  
99  or profiling SMP, memory, or system call usage.  <p>If you do not have a kernel as a separate file, but you have a bootable
100    disk image, then it is sometimes possible to boot directly from that
101    image. (This works for example with DECstation emulation, or when booting
102    from ISO9660 CDROM images.)
103    
 <p>  
 The emulator is written in C, does not depend on external libraries (except  
 X11, but that is optional), and should compile and run on most Unix-like  
 systems. If it doesn't, then that is a bug.  
104    
 <p>  
 The emulator contains code which tries to emulate the workings of CPUs and  
 surrounding hardware found in real machines, but it does not contain any  
 ROM code. You will need some form of program (in binary form) to run in  
 the emulator. For many emulation modes, PROM calls are handled by the  
 emulator itself, so you do not need to use any ROM image at all.  
105    
 <p>  
 You can use pre-compiled kernels (for example NetBSD kernels, or Linux),  
 or other programs that are in binary format, and in some cases even actual  
 ROM images. A couple of different file formats are supported (ELF, a.out,  
 ECOFF, SREC, raw binaries).  
   
 <p>  
 (You do not need any MIPS compiler toolchain to build or use GXemul.  
 If you need to compile MIPS binaries from sources, then of course you need  
 such a toolchain, but that is completely separate from GXemul. There  
 is a <a href="technical.html#regtest">regression testing</a> framework,  
 which requires that a GNU CC for mips64-unknown-elf or similar is available.  
 For simply building and using the emulator, it is not required.)  
106    
107    
108    
# Line 111  For simply building and using the emulat Line 110  For simply building and using the emulat
110    
111  <p><br>  <p><br>
112  <a name="free"></a>  <a name="free"></a>
113  <h3>Is GXemul free software?</h3>  <h3>Is GXemul Free software?</h3>
114    
115  Yes. I have released GXemul under a free license.  Yes. I have released GXemul under a Free license. The code in GXemul is
116  (For a definitions of the four freedoms associated with free software,  Copyrighted software, it is <i>not</i> public domain. (If this is
117  please read <a href="http://www.gnu.org/philosophy/free-sw.html">  confusing to you, you might want to read up on the definitions of the
118  http://www.gnu.org/philosophy/free-sw.html</a>.)  four freedoms associated with Free software, <a
119    href="http://www.gnu.org/philosophy/free-sw.html">http://www.gnu.org/philosophy/free-sw.html</a>.)
120    
121    <p>The code I have written is released under a 3-clause BSD-style license
122    (or "revised BSD-style" if one wants to use <a
123    href="http://www.gnu.org/philosophy/bsd.html">GNU jargon</a>). Apart from
124    the code I have written, some files are copied from other sources such as
125    NetBSD, for example header files containing symbolic names of bitfields in
126    device registers. They are also covered by similar licenses, but with some
127    additional clauses. The main point, however, is that the licenses require
128    that the original Copyright and license terms are included when you make a
129    copy or modification.
130    
131    <p>If you plan to redistribute GXemul <i>without</i> supplying the source
132    code, then you need to comply with each individual source file some other
133    way, for example by writing additional documentation containing copyright
134    notes. I have not done this, since I do not plan on making distributions
135    without source code. You need to check all individual files for details.
136    The "easiest way out" if you plan to redistribute code from GXemul is, of
137    course, to let it remain open source and simply supply the source code.
138    
139    <p>(If a stable release of GXemul is packaged into binary form, and it is
140    obvious which version of GXemul was used to build the package, then it can
141    be argued that the source code is available, just not in that specific
142    package. Common sense should be used in this case, and not pedanticism.)
143    
 <p>  
 The code I have written is released under a 3-clause BSD-style license  
 (or "revised BSD-style" if one wants to use  
 <a href="http://www.gnu.org/philosophy/bsd.html">GNU jargon</a>.)  
 Apart from the code I have written, some files are copied from other sources  
 such as NetBSD, for example header files containing symbolic names of  
 bitfields in device registers. They are also covered by similar licenses,  
 but with some additional clauses. If you plan to redistribute GXemul  
 (for example as a binary package), or reuse code from GXemul,  
 then you should check those files for their license terms.  
144    
 <p>  
 (The licenses usually require that the original Copyright and license  
 terms are included when you make a copy or modification. The "easiest way  
 out" if you plan to redistribute code from GXemul is to simply supply  
 the source code. You should however check individual files for details.)  
145    
146    
147    
# Line 149  Uncompress the .tar.gz distribution file Line 157  Uncompress the .tar.gz distribution file
157          $ <b>make</b>          $ <b>make</b>
158  </pre>  </pre>
159    
160  <p>  <p>This should work on most Unix-like systems. If it doesn't, then
 This should work on most Unix-like systems. If it doesn't, then please  
161  mail me a bug report.  mail me a bug report.
162    
163  <p>  <p>The emulator's performance is highly dependent on both runtime settings
 (Note for Windows users: there is a possibility that some releases  
 and/or snapshots will also work with Cygwin, but I can't promise that.)  
   
 <p>  
 The emulator's performance is highly dependent on both runtime settings  
164  and on compiler settings, so you might want to experiment with different  and on compiler settings, so you might want to experiment with different
165  CC and CFLAGS environment variable values. For example, on a modern PC,  CC and CFLAGS environment variable values. For example, on a modern PC,
166  you could try the following:  you could try the following:
167  <p>  <p><pre>
168  <pre>          $ <b>CFLAGS="-mcpu=pentium4 -O3" ./configure</b>
169          $ <b>CFLAGS="-mcpu=pentium4 -O3" ./configure</b>          $ <b>make</b>
         $ <b>make</b>  
170  </pre>  </pre>
171    
172    
173    
174    
175    
176    
177    
178    <p><br>
179    <a name="run"></a>
180    <h3>How to run the emulator:</h3>
181    
182    Once you have built GXemul, running it should be rather straight-forward.
183    Running <tt><b>gxemul</b></tt> without arguments (or with the
184    <b><tt>-h</tt></b> or <b><tt>-H</tt></b> command line options) will
185    display a help message.
186    
187  <p>  <p>
188  Run <b>./configure --help</b> to get a list of configure options. (The  To get some ideas about what is possible to run in the emulator, please
189  possible options differ between different releases and snapshots.)  read the section about <a href="guestoses.html">installing "guest"
190    operating systems</a>. If you are interested in using the emulator to
191    develop code on your own, then you should also read the section about
192    <a href="experiments.html#hello">Hello World</a>.
193    
194  <p>  <p>
 Once you have built GXemul, running it should be rather straight-forward.  
195  To exit the emulator, type CTRL-C to enter the  To exit the emulator, type CTRL-C to enter the
196  single-step debugger, and then type <b>quit</b>. By typing CTRL-B instead,  single-step debugger, and then type <tt><b>quit</b></tt>.
 a CTRL-C is sent to the emulated program.  
197    
198    <p>
199    If you are starting an emulation by entering settings directly on the
200    command line, and you are not using the <tt><b>-x</b></tt> option, then all
201    terminal input and output will go to the main controlling terminal.
202    CTRL-C is used to break into the debugger, so in order to send CTRL-C to
203    the running (emulated) program, you may use CTRL-B.
204    (This should be a reasonable compromise to allow the emulator to be usable
205    even on systems without X Windows.)
206    
207    <p>
208    There is no way to send an actual CTRL-B to the emulated program, when
209    typing in the main controlling terminal window. The solution is to either
210    use <a href="configfiles.html">configuration files</a>, or use
211    <tt><b>-x</b></tt>. Both these solutions cause new xterms to be opened for
212    each emulated serial port that is written to. CTRL-B and CTRL-C both have
213    their original meaning in those xterm windows.
214    
215    
216    
# Line 189  a CTRL-C is sent to the emulated program Line 222  a CTRL-C is sent to the emulated program
222    
223  <h4>MIPS:</h4>  <h4>MIPS:</h4>
224    
225  Emulation of R4000, which is a 64-bit CPU, was my initial goal. Right  Emulation of R4000, which is a 64-bit CPU, was my initial goal.
226  now, R2000/R3000-like CPUs are also emulated (32-bit), and emulation of  R2000/R3000-like CPUs (32-bit), R1x000, and generic MIPS32/MIPS64-style
227  R1x000 (at least the parts that are similar to R4000) is beginning to work  CPUs are also emulated, and are hopefully almost as stable as the R4000
228  as expected. Code targeted for MIPS32 and MIPS64 also often work.  emulation.
229    
230  <p>  <p>I have written an experimental dynamic binary translation subsystem.
 I have written an experimental dynamic binary translation subsystem.  
231  This gives higher total performance than interpreting one instruction at a  This gives higher total performance than interpreting one instruction at a
232  time and executing it. (If you wish to enable bintrans, add <b>-b</b> to  time and executing it. (If you wish to disable bintrans, add <b>-B</b> to
233  the command line, but keep in mind that it is still experimental.)  the command line.)
   
   
   
 <h4>URISC:</h4>  
   
 I have implemented an <a href="http://en.wikipedia.org/wiki/URISC">URISC</a>  
 emulation mode, just for fun. The only instruction available in an URISC  
 machine is "reverse subtract and skip on borrow". (It is probably not  
 worth trying to do bintrans with URISC, because any reasonable URISC  
 program relies on self-modifying code, which is bad for bintrans  
 performance.)  
   
   
234    
235    
236  <h4>Other CPU types:</h4>  <h4>Other CPU types:</h4>
237    
238  There is some code for 64-bit (and 32-bit) POWER/PowerPC emulation too,  Some other CPU architectures can also be partially emulated. These are not
239  but it only works for "Hello World" and similarly trivial programs. (There  working well enough yet to run guest operating systems.
240  are some other CPU modes too, but they are working even less.)  
241    
242    
243    
# Line 228  are some other CPU modes too, but they a Line 247  are some other CPU modes too, but they a
247  <a name="accuracy"></a>  <a name="accuracy"></a>
248  <h3>Emulation accuracy:</h3>  <h3>Emulation accuracy:</h3>
249    
250  GXemul is an instruction-level simulator; things that would happen in  GXemul is an instruction-level emulator; things that would happen in
251  several steps within a real CPU are not taken into account (eg. pipe-line  several steps within a real CPU are not taken into account (eg. pipe-line
252  stages or out-of-order execution). Still, instruction-level accuracy seems  stalls or out-of-order execution). Still, instruction-level accuracy seems
253  to be enough to be able to run complete guest operating systems inside the  to be enough to be able to run complete guest operating systems inside the
254  emulator.  emulator.
255    
256    <p>Caches are by default not emulated. In some cases, the existance of
257    caches is "faked" to let operating systems think that they are there.
258    (There is some old code for R2000/R3000 caches, but it has probably
259    suffered from bitrot by now.)
260    
261    <p>The emulator is <i>not</i> timing-accurate. It can be run in a
262    "deterministic" mode, <tt><b>-D</b></tt>. The meaning of deterministic is
263    simply that running two emulations with the same settings will result in
264    identical runs. Obviously, this requires that no user interaction is
265    taking place, and that clock speeds are fixed with the <tt><b>-I</b></tt>
266    option. (Deterministic in this case does <i>not</i> mean that the
267    emulation will be identical to some actual real-world machine.)
268    
269    
270    
271    
# Line 242  emulator. Line 274  emulator.
274  <a name="emulmodes"></a>  <a name="emulmodes"></a>
275  <h3>Which machines does GXemul emulate?</h3>  <h3>Which machines does GXemul emulate?</h3>
276    
277  A few different machine types are emulated. The machine types that are  A few different machine types are emulated. The following machine types
278  emulated best at the moment are:  are emulated well enough to run at least one "guest OS":
279    
280  <p>  <p>
281  <ul>  <ul>
282    <li><b>DECstation 5000/200</b>&nbsp;&nbsp;("pmax")    <li><b>DECstation 5000/200</b>&nbsp;&nbsp;("3max")
283          <br>(Serial controller (including keyboard and mouse), ethernet,          <br>Serial controller (including keyboard and mouse), ethernet,
284          SCSI, and graphical framebuffers.)          SCSI, and graphical framebuffers.
285    <p>    <p>
286    <li><b>Acer Pica-61</b>&nbsp;&nbsp;(an ARC machine)    <li><b>Acer Pica-61</b>&nbsp;&nbsp;(an ARC machine)
287          <br>(Serial controller, "VGA" text console, and SCSI.)          <br>Serial controller, "VGA" text console, and SCSI.
288    <p>    <p>
289    <li><b>NEC MobilePro 770, 780, 800, and 880</b>&nbsp;&nbsp;(HPCmips machines)    <li><b>NEC MobilePro 770, 780, 800, and 880</b>&nbsp;&nbsp;(HPCmips machines)
290          <br>(Framebuffer, keyboard, and a PCMCIA IDE controller.)          <br>Framebuffer, keyboard, and a PCMCIA IDE controller.
291      <p>
292      <li><b>Cobalt</b>
293            <br>Serial controller and PCI IDE.
294      <p>
295      <li><b>Malta (evbmips)</b>
296            <br>Serial controller and PCI IDE.
297      <p>
298      <li><b>SGI O2 ("IP32")</b>
299            <br>Serial controller and ethernet.&nbsp;&nbsp;<small>(Enough for
300            root-on-nfs, but not for disk boot.)</small>
301  </ul>  </ul>
302    
303  <p>  <p>There is code in GXemul for emulation of many other machine types; the
304  There is code in GXemul for emulation of many other machine types;  degree to which these work range from almost being able to run a complete
305  the degree to which these work range from "almost" being able to run  OS, to almost completely unsupported (perhaps just enough support to
306  a complete OS, to almost completely unsupported (perhaps just enough  output a few boot messages via serial console).
307  support to output a few boot messages via serial console).  
308    <p>In addition to emulating real machines, there is also a "test-machine".
309  <p>  A test-machine consists of one or more CPUs and a few experimental devices
310  In addition to specific machine types, a "test-machine" can be emulated.  such as:
 A test-machine consists of one or more CPUs and a few experimental  
 devices such as:  
311    
312  <p>  <p>
313  <ul>  <ul>
314    <li>a console I/O device (putchar() and getchar()...)    <li>a console I/O device (putchar() and getchar()...)
315    <li>an inter-processor communication device, for SMP experiments    <li>an inter-processor communication device, for SMP experiments
316    <li>a very simple linear framebuffer device (for graphics output)    <li>a very simple linear framebuffer device (for graphics output)
317      <li>a simple SCSI disk controller
318      <li>a simple ethernet controller
319  </ul>  </ul>
320    
321  <p>  <p>This mode is useful if you wish to run experimental code, but do not
 This mode is useful if you wish to run experimental code, but do not  
322  wish to target any specific real-world machine type, for example for  wish to target any specific real-world machine type, for example for
323  educational purposes.  educational purposes.
324    
325  <p>  <p>You can read more about these experimental devices <a
326  You can read more about these experimental devices  href="experiments.html#expdevices">here</a>.
 <a href="experiments.html#expdevices">here</a>.  
327    
328    
329    
# Line 293  You can read more about these experiment Line 333  You can read more about these experiment
333    
334  <p><br>  <p><br>
335  <a name="guestos"></a>  <a name="guestos"></a>
336  <h3>Which guest OSes are possible to run?</h3>  <h3>Which guest OSes are possible to run in GXemul?</h3>
337    
338  This table sums up the guest OSes that run well enough to be considered  This table lists the guest OSes that run well enough to be considered
339  working in the emulator. They can boot from a harddisk image and be  working in the emulator. They can boot from a harddisk image and be
340  interacted with similar to a real machine:  interacted with similar to a real machine.
   
 <p><br>  
  <center>  
   <table border="0">  
     <tr><td>  
       <table border="0">  
         <tr><td align="center">  
           <table border="0">  
             <tr>  
               <td valign="top"><b><u>Guest&nbsp;OS:</u></b></td>  
               <td width="15">&nbsp;</td>  
               <td valign="top"><b><u>Emulation&nbsp;mode:</u></b></td>  
               <td width="35">&nbsp;</td>  
               <td valign="top"><b><u>Guest&nbsp;OS:</u></b></td>  
               <td width="15">&nbsp;</td>  
               <td valign="top"><b><u>Emulation&nbsp;mode:</u></b></td>  
             </tr>  
   
             <tr>  
               <td height="1"></td>  
             </tr>  
   
             <tr>  
               <td valign="top"><a href="http://www.netbsd.org/Ports/pmax/">NetBSD/pmax</a></td>  
               <td></td>  
               <td valign="top">DECstation</td>  
               <td></td>  
               <td valign="top"><a href="http://www.netbsd.org/Ports/arc/">NetBSD/arc</a></td>  
               <td></td>  
               <td valign="top">ARC&nbsp;(Acer&nbsp;Pica)</td>  
             </tr>  
   
             <tr>  
               <td valign="top"><a href="http://www.openbsd.org/pmax.html">OpenBSD/pmax</a></td>  
               <td></td>  
               <td valign="top">DECstation</td>  
               <td></td>  
               <td valign="top"><a href="http://www.openbsd.org/arc.html">OpenBSD/arc</a></td>  
               <td></td>  
               <td valign="top">ARC (Acer Pica)</td>  
             </tr>  
   
             <tr>  
               <td valign="top">Ultrix/RISC</td>  
               <td></td>  
               <td valign="top">DECstation</td>  
               <td></td>  
               <td valign="top"><a href="http://www.cs.berkeley.edu/projects/sprite/retrospective.html">Sprite</a></td>  
               <td></td>  
               <td valign="top">DECstation</td>  
             </tr>  
   
             <tr>  
               <td valign="top">Redhat&nbsp;Linux<super>*</super></td>  
               <td></td>  
               <td valign="top">DECstation</td>  
               <td></td>  
               <td valign="top"><a href="http://www.debian.org/">Debian&nbsp;GNU/Linux</a><super>*</super></td>  
               <td></td>  
               <td valign="top">DECstation</td>  
             </tr>  
   
             <tr>  
               <td valign="top"><a href="http://www.netbsd.org/Ports/hpcmips/">NetBSD/hpcmips</a></td>  
               <td></td>  
               <td valign="top">NEC MobilePro</td>  
             </tr>  
           </table>  
         </td></tr>  
   
         <tr><td height="15">&nbsp;</td></tr>  
   
         <tr><td>  
           <center>  
             <table border="0">  
               <tr>  
                 <td width=160 align=center><a href="netbsd-pmax-20040630.png"><img src="netbsd-pmax-20040630_small.png"></a></td>  
                 <td width=160 align=center><a href="openbsd-pmax-20040710.png"><img src="openbsd-pmax-20040710_small.png"></a></td>  
                 <td width=160 align=center><a href="ultrix4.5-20040706.png"><img src="ultrix4.5-20040706_small.gif"></a></td>  
               </tr>  
               <tr>  
                 <td align=center>NetBSD/pmax&nbsp;1.6.2</td>  
                 <td align=center>OpenBSD/pmax&nbsp;2.8</td>  
                 <td align=center>Ultrix&nbsp;4.5</td>  
               </tr>  
               <tr>  
                 <td height=10>&nbsp;</td>  
               </tr>  
               <tr>  
                 <td width=160 align=center><a href="20041024-netbsd-arc-installed.gif"><img src="20041024-netbsd-arc-installed_small.gif"></a></td>  
                 <td width=160 align=center><a href="20041024-openbsd-arc-installed.gif"><img src="20041024-openbsd-arc-installed_small.gif"></a></td>  
                 <td width=160 align=center><a href="sprite-20040711.png"><img src="sprite-20040711_small.png"></a></td>  
               </tr>  
               <tr>  
                 <td align=center>NetBSD/arc&nbsp;1.6.2</td>  
                 <td align=center>OpenBSD/arc&nbsp;2.3</td>  
                 <td align=center>Sprite</td>  
               </tr>  
               <tr>  
                 <td height=10>&nbsp;</td>  
               </tr>  
               <tr>  
                 <td width=160 align=center><a href="20041129-redhat_mips.png"><img src="20041129-redhat_mips_small.png"></a></td>  
                 <td width=160 align=center><a href="20041213-debian_4.png"><img src="20041213-debian_4_small.gif"></a></td>  
                 <td width=160 align=center><a href="20050331-netbsd-hpcmips.png"><img src="20050331-netbsd-hpcmips_small.png"></a></td>  
               </tr>  
               <tr>  
                 <td align=center>Redhat&nbsp;Linux<super>*</super></td>  
                 <td align=center>Debian&nbsp;GNU/Linux<super>*</super></td>  
                 <td align=center>NetBSD/hpcmips</td>  
               </tr>  
             </table>  
           </center>  
         </td></tr>  
       </table>  
     </td></tr>  
   </table>  
  </center>  
   
 <p><br>  
   
 (<super>*</super> Although Linux runs under DECstation emulation, the  
 default kernel in Debian GNU/Linux does not support keyboards on the 5000/200  
 (the specific DECstation model being emulated), so when the login prompt  
 is reached you cannot interact with the system.  
 Kaj-Michael Lang has compiled and made available a newer kernel from the  
 current mips-linux development tree. You can find it here:  
 <a href="http://home.tal.org/~milang/o2/kernels/">http://home.tal.org/~milang/o2/kernels</a>/<a href="http://home.tal.org/~milang/o2/kernels/vmlinux-2.4.29-rc2-r3k-mipsel-decstation">vmlinux-2.4.29-rc2-r3k-mipsel-decstation</a>  
 This newer kernel supports keyboard input, but it does not have Debian's  
 ethernet patches, so you will not be able to use keyboard/framebuffer  
 <i>and</i> networking at the same time.)  
   
341    
342  <p>  <p>
343  It is non-trivial to get a specific operating system or OS kernel to  <center><table border="0">
344  run in the emulator, so don't expect the list above to grow too quickly.          <tr>
345              <td width="10"></td>
346  <p>            <td align="center"><a href="20050317-example.png"><img src="20050317-example_small.png"></a></td>
347  There is no guarantee that anything specific will run in the emulator, but            <td width="15"></td>
348  NetBSD is a good starting point for someone who wants to experiment.            <td><a href="http://www.netbsd.org/Ports/pmax/">NetBSD/pmax</a>
349                    <br>DECstation 5000/200</td>
350              <td width="30"></td>
351              <td align="center"><a href="20041024-netbsd-arc-installed.gif"><img src="20041024-netbsd-arc-installed_small.gif"></a></td>
352              <td width="15"></td>
353              <td><a href="http://www.netbsd.org/Ports/arc/">NetBSD/arc</a>
354                    <br>Acer Pica-61</td>
355    
356            </tr>
357    
358            <tr><td height="10"></td></tr>
359    
360            <tr>
361              <td></td>
362              <td align="center"><a href="openbsd-pmax-20040710.png"><img src="openbsd-pmax-20040710_small.png"></a></td>
363              <td></td>
364              <td><a href="http://www.openbsd.org/pmax.html">OpenBSD/pmax</a>
365                    <br>DECstation 5000/200</td>
366              <td></td>
367              <td align="center"><a href="20041024-openbsd-arc-installed.gif"><img src="20041024-openbsd-arc-installed_small.gif"></a></td>
368              <td></td>
369              <td><a href="http://www.openbsd.org/arc.html">OpenBSD/arc</a>
370                    <br>Acer Pica-61</td>
371            </tr>
372    
373            <tr><td height="10"></td></tr>
374    
375            <tr>
376              <td></td>
377              <td align="center"><a href="ultrix4.5-20040706.png"><img src="ultrix4.5-20040706_small.gif"></a></td>
378              <td></td>
379              <td>Ultrix/RISC<br>DECstation 5000/200</td>
380              <td></td>
381              <td align="center"><a href="20041213-debian_4.png"><img src="20041213-debian_4_small.gif"></a></td>
382              <td></td>
383              <td><a href="http://www.debian.org/">Debian&nbsp;GNU/Linux</a>&nbsp;<super>*</super>
384                    <br>DECstation 5000/200</td>
385            </tr>
386    
387            <tr><td height="10"></td></tr>
388    
389            <tr>
390              <td></td>
391              <td align="center"><a href="sprite-20040711.png"><img src="sprite-20040711_small.png"></a></td>
392              <td></td>
393              <td><a href="http://www.cs.berkeley.edu/projects/sprite/retrospective.html">Sprite</a>
394                    <br>DECstation 5000/200</td>
395              <td></td>
396              <td align="center"><a href="20041129-redhat_mips.png"><img src="20041129-redhat_mips_small.png"></a></td>
397              <td></td>
398              <td>Redhat&nbsp;Linux&nbsp;<super>*</super>
399                    <br>DECstation 5000/200</td>
400            </tr>
401    
402            <tr><td height="10"></td></tr>
403    
404            <tr>
405              <td></td>
406              <td align="center"><a href="20050427-netbsd-hpcmips-2.png"><img src="20050427-netbsd-hpcmips-2_small.png"></a></td>
407              <td></td>
408              <td><a href="http://www.netbsd.org/Ports/hpcmips/">NetBSD/hpcmips</a>
409                    <br>NEC MobilePro 770, 780, 800, 880</td>
410              <td></td>
411              <td align="center"><a href="20050413-netbsd-cobalt.png"><img src="20050413-netbsd-cobalt_small.png"></a></td>
412              <td></td>
413              <td><a href="http://www.netbsd.org/Ports/cobalt/">NetBSD/cobalt</a>
414                    <br>Cobalt</td>
415            </tr>
416    
417            <tr><td height="10"></td></tr>
418    
419            <tr>
420              <td></td>
421              <td align="center"><a href="20050626-netbsd-sgimips-netboot.png"><img src="20050626-netbsd-sgimips-netboot_small.png"></a></td>
422              <td></td>
423              <td><a href="http://www.netbsd.org/Ports/sgimips/">NetBSD/sgimips</a>
424                    <br>SGI O2 ("IP32")</td>
425              <td></td>
426              <td align="center"><a href="20050622-netbsd-evbmips-malta.png"><img src="20050622-netbsd-evbmips-malta_small.png"></a></td>
427              <td></td>
428              <td><a href="http://www.netbsd.org/Ports/evbmips/">NetBSD/evbmips</a>
429                    <br>5Kc (and 4Kc) Malta<br>evaluation boards</td>
430              <td></td>
431            </tr>
432    
433    </table></center>
434    
435    
436    <p><br>
437    
438    <super>*</super> Although Linux runs under DECstation emulation, the
439    default 2.4.27 kernel in Debian GNU/Linux does not support keyboards on
440    the 5000/200 (the specific DECstation model being emulated), so when the
441    login prompt is reached you cannot interact with the system. Kaj-Michael
442    Lang has compiled and made available a newer kernel from the current
443    mips-linux development tree. You can find it here: <a
444    href="http://home.tal.org/~milang/o2/kernels/">http://home.tal.org/~milang/o2/kernels</a>/<a
445    href="http://home.tal.org/~milang/o2/kernels/vmlinux-2.4.29-rc2-r3k-mipsel-decstation">vmlinux-2.4.29-rc2-r3k-mipsel-decstation</a>
446    This newer kernel supports keyboard input, but it does not have Debian's
447    ethernet patches, so you will not be able to use keyboard/framebuffer
448    <i>and</i> networking at the same time.
449    
 </p>  
450    
451  </body>  </body>
452  </html>  </html>

Legend:
Removed from v.2  
changed lines
  Added in v.12

  ViewVC Help
Powered by ViewVC 1.1.26