/[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!

Diff of /trunk/doc/intro.html

Parent Directory | Revision Log | View Patch Patch

-revision 10 by dpavlin,
Mon Oct  8 16:18:27 2007 UTC
+revision 44 by dpavlin,
Mon Oct  8 16:22:56 2007 UTC
 Line 1
- <html>
+ <html><head><title>Gavare's eXperimental Emulator:&nbsp;&nbsp;&nbsp;Introduction</title>
- <head><title>GXemul documentation: Introduction</title>
+ <meta name="robots" content="noarchive,nofollow,noindex"></head>
- <meta name="robots" content="noarchive,nofollow,noindex">
- </head>
  <body bgcolor="#f8f8f8" text="#000000" link="#4040f0" vlink="#404040" alink="#ff0000">
  <table border=0 width=100% bgcolor="#d0d0d0"><tr>
  <td width=100% align=center valign=center><table border=0 width=100%><tr>
  <td align="left" valign=center bgcolor="#d0efff"><font color="#6060e0" size="6">
- <b>GXemul documentation:</b></font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+ <b>GXemul:</b></font>&nbsp;&nbsp;
  <font color="#000000" size="6"><b>Introduction</b>
  </font></td></tr></table></td></tr></table><p>
  <!--
- $Id: intro.html,v 1.53 2005/06/26 08:42:26 debug Exp $
+ $Id: intro.html,v 1.125 2007/06/30 14:02:02 debug Exp $
- Copyright (C) 2003-2005  Anders Gavare.  All rights reserved.
+ Copyright (C) 2003-2007  Anders Gavare.  All rights reserved.
  Redistribution and use in source and binary forms, with or without
  modification, are permitted provided that the following conditions are met:
-Line 47 
 SUCH DAMAGE.
+Line 45 
 SUCH DAMAGE.
  <h2>Introduction</h2>
  <p>
+ <table border="0" width="99%"><tr><td valign="top" align="left">
  <ul>
    <li><a href="#overview">Overview</a>
    <li><a href="#free">Is GXemul Free software?</a>
    <li><a href="#build">How to compile/build the emulator</a>
    <li><a href="#run">How to run the emulator</a>
-   <li><a href="#cpus">Which CPU types does GXemul emulate?</a>
+   <li><a href="#cpus">Which processor architectures does GXemul emulate?</a>
+   <li><a href="#hosts">Which host architectures/platforms are supported?</a>
    <li><a href="#accuracy">Emulation accuracy</a>
    <li><a href="#emulmodes">Which machines does GXemul emulate?</a>
-   <li><a href="#guestos">Which guest OSes are possible to run in GXemul?</a>
  </ul>
+ </td><td valign="center" align="center">
+ <a href="20050317-example.png"><img src="20050317-example_small.png"></a>
+ <p>NetBSD/pmax 1.6.2 with X11<br>running in GXemul</td></tr></table>
-Line 66 
 SUCH DAMAGE.
+Line 67 
 SUCH DAMAGE.
  <a name="overview"></a>
  <h3>Overview:</h3>
- GXemul is an experimental instruction-level machine emulator. It can be
+ GXemul is a framework for full-system computer architecture emulation.
- used to run binary code for (among others) MIPS-based machines, regardless
+ Several processor architectures and machine types have been implemented.
- of host platform. Several emulation modes are available. For some modes,
+ It is working well enough to allow <a href="#emulmodes">unmodified
- processors and surrounding hardware components are emulated well enough to
+ "guest" operating systems to run inside the emulator</a>, as if they were
- let unmodified operating systems run as if they were running on a real
+ running on real hardware.
- machine.
+ <p>The emulator emulates (networks of) real machines. The machines may
- <p>Devices and CPUs are not simulated with 100% accuracy. They are only
+ consist of <a
- ``faked'' well enough to make operating systems (e.g. NetBSD) run without
+ href="http://en.wikipedia.org/wiki/ARM_architecture">ARM</a>, <a
- complaining too much. Still, the emulator could be of interest for
+ href="http://en.wikipedia.org/wiki/MIPS_architecture">MIPS</a>, <a
- academic research and experiments, such as when learning how to write
+ href="http://en.wikipedia.org/wiki/Powerpc">PowerPC</a>, and <a
+ href="http://en.wikipedia.org/wiki/SuperH">SuperH</a> processors, and
+ various surrounding hardware components such as framebuffers, busses,
+ interrupt controllers, ethernet controllers, disk controllers, and serial
+ port controllers.
+ <p>GXemul, including the dynamic translation system, is implemented in
+ portable
+ <a href="http://en.wikipedia.org/wiki/C_(programming_language)">C</a>,
+ which means that the emulator will run on practically any 64-bit or 32-bit
+ <a href="http://en.wikipedia.org/wiki/Unix-like">Unix-like</a> systems,
+ with few or no modifications.
+ <p>Devices and processors are not simulated with 100% accuracy. They are
+ only "faked" well enough to allow guest operating systems to run without
+ complaining too much. Still, the emulator could be of interest for
+ academic research and experiments, such as when learning how to write
  operating system code.
- <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. (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.)
  <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
+ in the emulator. For some emulation modes, PROM calls are handled by the
  emulator itself, so you do not need to use any ROM image at all.
- <p>You can use pre-compiled kernels (for example NetBSD kernels, or
+ <p>You can use pre-compiled kernels (for example <a href="http://www.netbsd.org/">NetBSD</a>
- Linux), or other programs that are in binary format, and in some cases
+ 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
+ even actual ROM images. A couple of different file formats are supported:
- (ELF, a.out, ECOFF, SREC, and raw binaries).
+ <a href="http://en.wikipedia.org/wiki/Executable_and_Linkable_Format">ELF</a>,
+ <a href="http://en.wikipedia.org/wiki/A.out">a.out</a>,
+ <a href="http://en.wikipedia.org/wiki/COFF">COFF</a>/<a href="http://en.wikipedia.org/wiki/ECOFF">ECOFF</a>,
+ <a href="http://en.wikipedia.org/wiki/SREC_%28file_format%29">SREC</a>, and raw binaries.
  <p>If you do not have a kernel as a separate file, but you have a bootable
  disk image, then it is sometimes possible to boot directly from that
- image. (This works for example with DECstation emulation, or when booting
+ image. This works for example with DECstation emulation, <a href="dreamcast.html">Dreamcast
- from ISO9660 CDROM images.)
+ emulation</a>, or when booting from generic <a href="http://en.wikipedia.org/wiki/ISO9660">ISO9660</a>
+ CDROM images if the kernel is included in the image as a plain file.
+ <p>Thanks to (in no specific order) Joachim Buss, Olivier Houchard, Juli
+ Mallett, Juan Romero Pardines, Carl van Schaik, Miod Vallat, Alec Voropay,
+ G�ran Weinholt, Alexander Yurchenko, and everyone else who has provided me
+ with feedback.
-Line 119 
 confusing to you, you might want to read
+Line 137 
 confusing to you, you might want to read
  four freedoms associated with Free software, <a
  href="http://www.gnu.org/philosophy/free-sw.html">http://www.gnu.org/philosophy/free-sw.html</a>.)
- <p>
+ <p>The code I have written is released under a 3-clause BSD-style license
- The code I have written is released under a 3-clause BSD-style license
+ (or "revised BSD-style" if one wants to use <a
- (or "revised BSD-style" if one wants to use
+ href="http://www.gnu.org/philosophy/bsd.html">GNU jargon</a>). Apart from
- <a href="http://www.gnu.org/philosophy/bsd.html">GNU jargon</a>).
+ the code I have written, some files are copied from other sources such as
- Apart from the code I have written, some files are copied from other sources
+ NetBSD, for example header files containing symbolic names of bitfields in
- such as NetBSD, for example header files containing symbolic names of
+ device registers. They are also covered by similar licenses, but with some
- bitfields in device registers. They are also covered by similar licenses,
+ additional clauses. The main point, however, is that the licenses require
- but with some additional clauses. If you plan to redistribute GXemul
+ that the original Copyright and license terms are included when you make a
- (for example as a binary package), or reuse code from GXemul,
+ copy or modification.
- then you should check those files for their license terms.
+ <p>If you plan to redistribute GXemul <i>without</i> supplying the source
- <p>
+ code, then you need to comply with each individual source file some other
- (The licenses usually require that the original Copyright and license
+ way, for example by writing additional documentation containing copyright
- terms are included when you make a copy or modification. The "easiest way
+ notes. I have not done this, since I do not plan on making distributions
- out" if you plan to redistribute code from GXemul is to simply supply
+ without source code. You need to check all individual files for details.
- the source code. You should however check individual files for details.)
+ The "easiest way out" if you plan to redistribute code from GXemul is, of
+ course, to let it remain Free Software and simply include the source code.
+ <p>In case you want to reuse parts of GXemul, but you need to do that
+ under a different license (e.g. the
+ <a href="http://www.gnu.org/licenses/gpl.html">GPL</a>), then contact me and
+ I can probably re-license/dual-license files on a case-by-case basis.
-Line 150 
 Uncompress the .tar.gz distribution file
+Line 174 
 Uncompress the .tar.gz distribution file
          $ <b>make</b>
  </pre>
- <p>
+ <p>This should work on most Unix-like systems. GXemul does not require any
- This should work on most Unix-like systems. If it doesn't, then
+ specific libraries to build, however, if you build on a system which does
- mail me a bug report.
+ not have X11 libraries installed, some functionality will be lost.
+ <p>The emulator's performance is highly dependent on both runtime settings
+ and on compiler settings, so you might want to experiment with using
+ different <tt>CC</tt> and <tt>CFLAGS</tt> environment variable values when
+ running the <tt>configure</tt> script.
+ <p>On some platforms, it is possible that building GXemul will fail
+ because of too high optimization. When using GCC (the GNU compiler),
+ <tt>-O3</tt> is the default optimization level. This works fine on e.g.
+ amd64 and i386 systems, but on some more uncommon platforms, <tt>-O3</tt>
+ might trigger internal bugs in GCC itself. If this happens, try setting
+ <tt>CFLAGS</tt> to <tt>-O2</tt> before running <tt>./configure</tt>, and
+ try again,
+ <p>Note that there is no <tt>make install</tt> functionality; package
+ maintainers for individual operating systems solve this for their
+ corresponding OSes.
- <p>
- (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
- and on compiler settings, so you might want to experiment with different
- CC and CFLAGS environment variable values. For example, on a modern PC,
- you could try the following:
- <p>
- <pre>
-         $ <b>CFLAGS="-mcpu=pentium4 -O3" ./configure</b>
-         $ <b>make</b>
- </pre>
- <p>
- Run <b><tt>./configure --help</tt></b> to get a list of configure options. (The
- possible options differ between different releases and snapshots.)
-Line 187 
 Running <tt><b>gxemul</b></tt> without a
+Line 210 
 Running <tt><b>gxemul</b></tt> without a
  <b><tt>-h</tt></b> or <b><tt>-H</tt></b> command line options) will
  display a help message.
- <p>
+ <p>To get some ideas about what is possible to run in the emulator, please
- To get some ideas about what is possible to run in the emulator, please
  read the section about <a href="guestoses.html">installing "guest"
- operating systems</a>. If you are interested in using the emulator to
+ operating systems</a>. The most straight forward guest operating to
- develop code on your own, then you should also read the section about
+ install is NetBSD/pmax; the instructions provided <a
- <a href="experiments.html#hello">Hello World</a>.
+ href="guestoses.html#netbsdpmaxinstall">here</a> should let you install
+ NetBSD/pmax in a way very similar to how it is done on a real DECstation.
+ <p>If you are interested in using the emulator to develop code on your
+ own, then you should also read the section about <a
+ href="experiments.html#hello">Hello World</a>.
- <p>
+ <p>To exit the emulator, type CTRL-C to enter the
- To exit the emulator, type CTRL-C to enter the
  single-step debugger, and then type <tt><b>quit</b></tt>.
- <p>
+ <p>If you are starting an emulation by entering settings directly on the
- If you are starting an emulation by entering settings directly on the
+ command line, and you are not using the <tt><b>-x</b></tt> option, then
- command line, and you are not using the <tt><b>-x</b></tt> option, then all
+ all terminal input and output will go to the main controlling terminal.
- terminal input and output will go to the main controlling terminal.
  CTRL-C is used to break into the debugger, so in order to send CTRL-C to
- the running (emulated) program, you may use CTRL-B.
+ the running (emulated) program, you may use CTRL-B. (This should be a
- (This should be a reasonable compromise to allow the emulator to be usable
+ reasonable compromise to allow the emulator to be usable even on systems
- even on systems without X Windows.)
+ without X Windows.)
- <p>
+ <p>There is no way to send an actual CTRL-B to the emulated program, when
- There is no way to send an actual CTRL-B to the emulated program, when
+ typing in the main controlling terminal window. The solution is to either
- typing in the main controlling terminal window. The solution is to either
+ use <a href="configfiles.html">configuration files</a>, or use
- use <a href="configfiles.html">configuration files</a>, or use
  <tt><b>-x</b></tt>. Both these solutions cause new xterms to be opened for
  each emulated serial port that is written to. CTRL-B and CTRL-C both have
  their original meaning in those xterm windows.
-Line 221 
 their original meaning in those xterm wi
+Line 245 
 their original meaning in those xterm wi
  <p><br>
  <a name="cpus"></a>
- <h3>Which CPU types does GXemul emulate?</h3>
+ <h3>Which processor architectures does GXemul emulate?</h3>
- <h4>MIPS:</h4>
+ The architectures that are emulated well enough to let at least one
+ guest operating system run (per architecture) are
+ <a href="http://en.wikipedia.org/wiki/ARM_architecture">ARM</a>,
+ <a href="http://en.wikipedia.org/wiki/MIPS_architecture">MIPS</a>,
+ <a href="http://en.wikipedia.org/wiki/Powerpc">PowerPC</a>, and
+ <a href="http://en.wikipedia.org/wiki/SuperH">SuperH</a>.
+ <p>Please read the sections about <a href="#emulmodes">emulation
+ modes</a> and <a href="guestoses.html">guest operating
+ systems</a> for more information about the machines and operating systems,
+ respectively, that can be considered "working" in the emulator.
+ <p>(There is some code in GXemul for emulation of other architectures, but
+ they are not stable or complete enough to be listed among the "working"
+ architectures.)
- Emulation of R4000, which is a 64-bit CPU, was my initial goal.
- R2000/R3000-like CPUs (32-bit), R1x000, and generic MIPS32/MIPS64-style
- CPUs are also emulated, and are hopefully almost as stable as the R4000
- emulation.
- <p>
- I have written an experimental dynamic binary translation subsystem.
- This gives higher total performance than interpreting one instruction at a
- time and executing it. (If you wish to enable bintrans, add <b>-b</b> to
- the command line, but keep in mind that it is still experimental.)
- <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.)
+ <p><br>
+ <a name="hosts"></a>
+ <h3>Which host architectures/platforms are supported?</h3>
+ GXemul should compile and run on any modern host architecture (64-bit or
+-bit word-length). I generally test it on
+ <a href="http://www.freebsd.org/platforms/amd64.html">FreeBSD/amd64</a> 6.x,
+ <a href="http://www.freebsd.org/platforms/alpha.html">FreeBSD/alpha</a> 4.x,
+ sometimes also on Linux (various platforms), and every
+ now and then also on <a href="http://www.netbsd.org/">NetBSD</a> or
+ <a href="http://www.openbsd.org/">OpenBSD</a> inside the emulator itself
+ (various platforms).
+ <p>Note 1: The <a href="translation.html">dynamic translation</a> engine
+ does <i>not</i> require backends for native code generation to be written
+ for each individual host architecture; the intermediate representation
+ that the dyntrans system uses can be executed on any host architecture.
+ <p>Note 2: Although GXemul may build and run on non-Unix-like platforms,
+ such as <a href="http://www.cygwin.com/">Cygwin</a>, Unix-like systems are
+ the primary platform. Some functionality may be lost when running on Cygwin.
- <h4>Other CPU types:</h4>
- Some other CPU architectures can also be partially emulated. These are not
- working well enough yet to run guest operating systems.
-Line 262 
 working well enough yet to run guest ope
+Line 302 
 working well enough yet to run guest ope
  <h3>Emulation accuracy:</h3>
  GXemul is an instruction-level emulator; things that would happen in
- 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 (e.g. pipe-line
  stalls or out-of-order execution). Still, instruction-level accuracy seems
  to be enough to be able to run complete guest operating systems inside the
  emulator.
- <p>
+ <p>The existance of instruction and data caches is "faked" to let
- Caches are by default not emulated. In some cases, the existance of caches
+ operating systems think that they are there, but for all practical
- is "faked" to let operating systems think that they are there. (There is
+ purposes, these caches are non-working.
- some old code for R2000/R3000 caches, but it has probably suffered from
- bitrot by now.)
+ <p>The emulator is in general <i>not</i> timing-accurate, neither at the
+ instruction level nor on any higher level. An attempt is made to let
+ emulated clocks run at the same speed as the host (i.e. an emulated timer
+ running at 100 Hz will interrupt around 100 times per real second), but
+ since the host speed may vary, e.g. because of other running processes,
+ there is no guarantee as to how many instructions will be executed in
+ each of these 100 Hz cycles.
+ <p>If the host is very slow, the emulated clocks might even lag behind
+ the real-world clock.
- <p>
- The emulator is <i>not</i> timing-accurate. It can be run in a
- "deterministic" mode, <tt><b>-D</b></tt>. The meaning of deterministic is
- simply that running two emulations with the same settings will result in
- identical runs. Obviously, this requires that no user interaction is
- taking place, and that clock speeds are fixed with the <tt><b>-I</b></tt>
- option. (Deterministic in this case does <i>not</i> mean that the emulation
- will be identical to some actual real-world machine.)
-Line 295 
 are emulated well enough to run at least
+Line 336 
 are emulated well enough to run at least
  <p>
  <ul>
-   <li><b>DECstation 5000/200</b>&nbsp;&nbsp;("3max")
+   <li><b><u>ARM</u></b>
-         <br>Serial controller (including keyboard and mouse), ethernet,
+   <ul>
-         SCSI, and graphical framebuffers.
+     <li><b>CATS</b> (<a href="guestoses.html#netbsdcatsinstall">NetBSD/cats</a>,
-   <p>
+         <a href="guestoses.html#openbsdcatsinstall">OpenBSD/cats</a>)
-   <li><b>Acer Pica-61</b>&nbsp;&nbsp;(an ARC machine)
+     <li><b>IQ80321</b> (<a href="guestoses.html#netbsdevbarminstall">NetBSD/evbarm</a>)
-         <br>Serial controller, "VGA" text console, and SCSI.
+     <li><b>NetWinder</b> (<a href="guestoses.html#netbsdnetwinderinstall">NetBSD/netwinder</a>)
+   </ul>
    <p>
-   <li><b>NEC MobilePro 770, 780, 800, and 880</b>&nbsp;&nbsp;(HPCmips machines)
+   <li><b><u>MIPS</u></b>
-         <br>Framebuffer, keyboard, and a PCMCIA IDE controller.
+   <ul>
+     <li><b>DECstation 5000/200</b> (<a href="guestoses.html#netbsdpmaxinstall">NetBSD/pmax</a>,
+         <a href="guestoses.html#openbsdpmaxinstall">OpenBSD/pmax</a>,
+         <a href="guestoses.html#ultrixinstall">Ultrix</a>,
+         <a href="guestoses.html#declinux">Linux/DECstation</a>,
+         <a href="guestoses.html#sprite">Sprite</a>)
+     <li><b>Acer Pica-61</b> (<a href="guestoses.html#netbsdarcinstall">NetBSD/arc</a>)
+     <li><b>NEC MobilePro 770, 780, 800, 880</b> (<a href="guestoses.html#netbsdhpcmipsinstall">NetBSD/hpcmips</a>)
+     <li><b>Cobalt</b> (<a href="guestoses.html#netbsdcobaltinstall">NetBSD/cobalt</a>)
+     <li><b>Malta</b> (<a href="guestoses.html#netbsdevbmipsinstall">NetBSD/evbmips</a>, Linux/Malta <font color="#0000e0">(<super>*1</super>)</font>)
+     <li><b>Algorithmics P5064</b> (<a href="guestoses.html#netbsdalgorinstall">NetBSD/algor</a>)
+     <li><b>SGI O2 (aka IP32)</b> <font color="#0000e0">(<super>*2</super>)</font>
+         (<a href="guestoses.html#netbsdsgimips">NetBSD/sgi</a>)
+   </ul>
    <p>
-   <li><b>Cobalt</b>
+   <li><b><u>PowerPC</u></b>
-         <br>Serial controller and PCI IDE.
+   <ul>
+     <li><b>IBM 6050/6070 (PReP, PowerPC Reference Platform)</b> (<a href="guestoses.html#netbsdprepinstall">NetBSD/prep</a>)
+     <li><b>MacPPC (generic "G4" Macintosh)</b> (<a href="guestoses.html#netbsdmacppcinstall">NetBSD/macppc</a>)
+     <li><b>Artesyn PM/PPC</b> <font color="#0000e0">(<super>*2</super>)</font>
+         (<a href="guestoses.html#netbsdpmppc">NetBSD/pmppc</a>)
+   </ul>
    <p>
-   <li><b>Malta (evbmips)</b>
+   <li><b><u>SuperH</u></b>
-         <br>Serial controller and PCI IDE.
+   <ul>
-   <p>
+     <li><b>Sega Dreamcast</b> (<a href="dreamcast.html#netbsd_generic_md">NetBSD/dreamcast</a>, <a href="dreamcast.html#linux_live_cd">Linux/dreamcast</a>)
-   <li><b>SGI O2 ("IP32")</b>
+     <li><b>Landisk I-O DATA USL-5P</b> (<a href="guestoses.html#openbsdlandiskinstall">OpenBSD/landisk</a>)
-         <br>Serial controller and ethernet.&nbsp;&nbsp;<small>(Enough for
+   </ul>
-         root-on-nfs, but not for disk boot.)</small>
  </ul>
- <p>There is code in GXemul for emulation of many other machine types; the
+ <p>
+ <small><font color="#0000e0">(<super>*1</super>)</font> =
+ Linux/Malta may be run as a guest OS, however I have not yet found any stable
+ URL to pre-compiled Linux/Malta kernels. Thus, Linux/Malta emulation is not
+ tested for every release of the emulator; sometimes it works, sometimes
+ it doesn't.</small>
+ <br><small><font color="#0000e0">(<super>*2</super>)</font> =
+ The emulation is enough for root-on-nfs, but no disk controller (SCSI nor
+ IDE) is emulated yet for this machine type.</small>
+ <p>Note that of all of the machines above, none of them is emulated to
+%. The most complete emulation mode is probably the DECstation
+/200. Things that will most likely <b>not</b> work include running
+ raw PROM images for most machines, SGI IRIX, MacOS X or Darwin, Windows
+ NT, or Dreamcast games.
+ <p>There is code in GXemul for emulation of several other machine types; the
  degree to which these work range from almost being able to run a complete
- OS, to almost completely unsupported (perhaps just enough support to
+ OS, to almost completely unsupported, perhaps just enough support to
- output a few boot messages via serial console).
+ output a few boot messages via serial console. (See the end of
+ <a href="guestoses.html#generalnotes">this section</a> on the Guest OSes
+ page for some examples, but remember that these do not necessarily work.)
  <p>In addition to emulating real machines, there is also a "test-machine".
  A test-machine consists of one or more CPUs and a few experimental devices
-Line 330 
 such as:
+Line 408 
 such as:
    <li>a console I/O device (putchar() and getchar()...)
    <li>an inter-processor communication device, for SMP experiments
    <li>a very simple linear framebuffer device (for graphics output)
+   <li>a simple disk controller
+   <li>a simple ethernet controller
+   <li>a simple interrupt controller
+   <li>a real-time clock device
  </ul>
  <p>This mode is useful if you wish to run experimental code, but do not
-Line 344 
 href="experiments.html#expdevices">here<
+Line 426 
 href="experiments.html#expdevices">here<
- <p><br>
- <a name="guestos"></a>
- <h3>Which guest OSes are possible to run in GXemul?</h3>
- This table lists the guest OSes that run well enough to be considered
- working in the emulator. They can boot from a harddisk image and be
- interacted with similar to a real machine.
- <p>
- <center><table border="0">
-         <tr>
-           <td width="10"></td>
-           <td align="center"><a href="20050317-example.png"><img src="20050317-example_small.png"></a></td>
-           <td width="15"></td>
-           <td><a href="http://www.netbsd.org/Ports/pmax/">NetBSD/pmax</a>
-                 <br>DECstation 5000/200</td>
-           <td width="30"></td>
-           <td align="center"><a href="20041024-netbsd-arc-installed.gif"><img src="20041024-netbsd-arc-installed_small.gif"></a></td>
-           <td width="15"></td>
-           <td><a href="http://www.netbsd.org/Ports/arc/">NetBSD/arc</a>
-                 <br>Acer Pica-61</td>
-         </tr>
-         <tr><td height="10"></td></tr>
-         <tr>
-           <td></td>
-           <td align="center"><a href="openbsd-pmax-20040710.png"><img src="openbsd-pmax-20040710_small.png"></a></td>
-           <td></td>
-           <td><a href="http://www.openbsd.org/pmax.html">OpenBSD/pmax</a>
-                 <br>DECstation 5000/200</td>
-           <td></td>
-           <td align="center"><a href="20041024-openbsd-arc-installed.gif"><img src="20041024-openbsd-arc-installed_small.gif"></a></td>
-           <td></td>
-           <td><a href="http://www.openbsd.org/arc.html">OpenBSD/arc</a>
-                 <br>Acer Pica-61</td>
-         </tr>
-         <tr><td height="10"></td></tr>
-         <tr>
-           <td></td>
-           <td align="center"><a href="ultrix4.5-20040706.png"><img src="ultrix4.5-20040706_small.gif"></a></td>
-           <td></td>
-           <td>Ultrix/RISC<br>DECstation 5000/200</td>
-           <td></td>
-           <td align="center"><a href="20041213-debian_4.png"><img src="20041213-debian_4_small.gif"></a></td>
-           <td></td>
-           <td><a href="http://www.debian.org/">Debian&nbsp;GNU/Linux</a>&nbsp;<super>*</super>
-                 <br>DECstation 5000/200</td>
-         </tr>
-         <tr><td height="10"></td></tr>
-         <tr>
-           <td></td>
-           <td align="center"><a href="sprite-20040711.png"><img src="sprite-20040711_small.png"></a></td>
-           <td></td>
-           <td><a href="http://www.cs.berkeley.edu/projects/sprite/retrospective.html">Sprite</a>
-                 <br>DECstation 5000/200</td>
-           <td></td>
-           <td align="center"><a href="20041129-redhat_mips.png"><img src="20041129-redhat_mips_small.png"></a></td>
-           <td></td>
-           <td>Redhat&nbsp;Linux&nbsp;<super>*</super>
-                 <br>DECstation 5000/200</td>
-         </tr>
-         <tr><td height="10"></td></tr>
-         <tr>
-           <td></td>
-           <td align="center"><a href="20050427-netbsd-hpcmips-2.png"><img src="20050427-netbsd-hpcmips-2_small.png"></a></td>
-           <td></td>
-           <td><a href="http://www.netbsd.org/Ports/hpcmips/">NetBSD/hpcmips</a>
-                 <br>NEC MobilePro 770, 780, 800, 880</td>
-           <td></td>
-           <td align="center"><a href="20050413-netbsd-cobalt.png"><img src="20050413-netbsd-cobalt_small.png"></a></td>
-           <td></td>
-           <td><a href="http://www.netbsd.org/Ports/cobalt/">NetBSD/cobalt</a>
-                 <br>Cobalt</td>
-         </tr>
-         <tr><td height="10"></td></tr>
-         <tr>
-           <td></td>
-           <td align="center"><a href="20050626-netbsd-sgimips-netboot.png"><img src="20050626-netbsd-sgimips-netboot_small.png"></a></td>
-           <td></td>
-           <td><a href="http://www.netbsd.org/Ports/sgimips/">NetBSD/sgimips</a>
-                 <br>SGI O2 ("IP32")</td>
-           <td></td>
-           <td align="center"><a href="20050622-netbsd-evbmips-malta.png"><img src="20050622-netbsd-evbmips-malta_small.png"></a></td>
-           <td></td>
-           <td><a href="http://www.netbsd.org/Ports/evbmips/">NetBSD/evbmips</a>
-                 <br>5Kc (and 4Kc) Malta<br>evaluation boards</td>
-           <td></td>
-         </tr>
- </table></center>
- <p><br>
- <super>*</super> Although Linux runs under DECstation emulation, the
- default 2.4.27 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.
  </body>
  </html>

 Legend:



Removed from v.10
 


changed lines


 
Added in v.44
 Legend:



Removed from v.10
 


changed lines


 
Added in v.44
-Removed from v.10
+Added in v.44

	ViewVC Help
Powered by ViewVC 1.1.26