/[gxemul]/trunk/doc/experiments.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/experiments.html

Parent Directory | Revision Log | View Patch Patch

-revision 11 by dpavlin,
Mon Oct  8 16:18:27 2007 UTC
+revision 12 by dpavlin,
Mon Oct  8 16:18:38 2007 UTC
 Line 1
- <html>
+ <html><head><title>Gavare's eXperimental Emulator:&nbsp;&nbsp;&nbsp;Experimenting with GXemul</title>
- <head><title>GXemul documentation: Experimenting with GXemul</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>Gavare's eXperimental Emulator:&nbsp;&nbsp;&nbsp;</b></font>
  <font color="#000000" size="6"><b>Experimenting with GXemul</b>
  </font></td></tr></table></td></tr></table><p>
  <!--
- $Id: experiments.html,v 1.76 2005/06/24 09:33:32 debug Exp $
+ $Id: experiments.html,v 1.89 2005/08/09 18:29:20 debug Exp $
  Copyright (C) 2003-2005  Anders Gavare.  All rights reserved.
-Line 168 
 learn more about how MIPS programs run,
+Line 166 
 learn more about how MIPS programs run,
          a800000000030038: 00021600      sll     v0,v0,24
          GXemul&gt; <b>print v0</b>
          v0 = 0x0000000048000000
-         GXemul&gt; <b><blink>_</blink></b>
+         GXemul&gt; <b>_</b>
  </pre>
- <p>
+ <p>The syntax of the single-step debugger shouldn't be too hard to grasp.
- The syntax of the single-step debugger shouldn't be too hard to grasp.
+ Type "<tt>s</tt>" to single-step one instruction. For some commands (e.g.
- Type 's' to single-step one instruction. Just pressing enter after that
+ the single-step command), just pressing enter on a blank line will cause
- will repeat the 's' command. Type 'quit' to quit.
+ the last command to be repeated. Type "<tt>quit</tt>" to quit.
  <p>
  Hopefully this is enough to get you inspired. :-)
- <p><br>
- <h4>Hello World for GXemul's PPC mode</h4>
- GXemul also has an experimental PowerPC emulation mode.
- <a href="hello_ppc.c"><tt>hello_ppc.c</tt></a> is similar to
- <tt>hello_mips.c</tt>, but should be compiled and run as follows:
- <p>
- <pre>
-         $ <b>ppc-unknown-elf-gcc -O2 hello_ppc.c -c</b>
-         $ <b>ppc-unknown-elf-ld -e f hello_ppc.o -o hello_ppc</b>
-         $ <b>file hello_ppc</b>
-         hello_ppc: ELF 32-bit MSB executable, PowerPC or cisco 4500,
-           version 1 (SYSV), statically linked, not stripped
-         $ <b>gxemul -q -E testppc hello_ppc</b>
-         Hello world
- </pre>
- <p>
- [&nbsp;2005-02-18: I haven't yet been able to build a GCC for ppc64 (only the
- binutils toolchain), because the gcc sources seem to include Linux header files
- that aren't present on my FreeBSD system. 32-bit PPC works ok, though.&nbsp;]
-Line 217 
 It can either run in "bare" mode, where
+Line 191 
 It can either run in "bare" mode, where
  (just the CPU), or in a "test" mode where some simple devices are
  emulated.
- <p>
+ <p>The test machines (<tt>testmips</tt>, <tt>testppc</tt>, etc) have the
- The <tt>testmips</tt> machine has the following experimental devices:
+ following experimental devices:
  <p>
  <center><table border="0" width="80%">
-Line 226 
 The <tt>testmips</tt> machine has the fo
+Line 200 
 The <tt>testmips</tt> machine has the fo
    <tr>
      <td align="left" valign="top" width="200">
          <b><tt>cons</tt>:</b>
-         <p>This is a simple console device, for writing
+         <p>A simple console device, for writing
-         characters to the controlling terminal.
+         characters to the controlling terminal
+         and receiving keypresses.
          <p>Source code:&nbsp;&nbsp;<font color="#0000f0"><tt>src/devices/dev_cons.c</tt></font>
          <br>Default physical address:&nbsp&nbsp;<font color="#0000f0">0x10000000</font>
      </td>
-Line 239 
 The <tt>testmips</tt> machine has the fo
+Line 214 
 The <tt>testmips</tt> machine has the fo
              <td align="left" valign="top"><i><u>Effect:</u></i></td>
            </tr>
            <tr>
-             <td align="left" valign="top">0x0000</td>
+             <td align="left" valign="top"><tt>0x00</tt></td>
              <td align="left" valign="top">
-                 Read: <b><tt>getchar()</tt></b> (non-blocking)<br>
+                 Read: <b><tt>getchar()</tt></b> (non-blocking; returns
+                 <tt>0</tt> if no char was available)<br>
                  Write: <b><tt>putchar(ch)</tt></b></td>
            </tr>
            <tr>
-             <td align="left" valign="top">0x0010</td>
+             <td align="left" valign="top"><tt>0x10</tt></td>
              <td align="left" valign="top">Read or write: <b><tt>halt()</tt></b><br>
                  (Useful for exiting the emulator.)</td>
            </tr>
-Line 273 
 The <tt>testmips</tt> machine has the fo
+Line 249 
 The <tt>testmips</tt> machine has the fo
              <td align="left" valign="top"><i><u>Effect:</u></i></td>
            </tr>
            <tr>
-             <td align="left" valign="top">0x0000</td>
+             <td align="left" valign="top"><tt>0x0000</tt></td>
              <td align="left" valign="top">Read: <b><tt>whoami()</tt></b>.
                  Returns the id of the CPU doing the read.</td>
            </tr>
            <tr>
-             <td align="left" valign="top">0x0010</td>
+             <td align="left" valign="top"><tt>0x0010</tt></td>
              <td align="left" valign="top">Read: <b><tt>ncpus()</tt></b>.
                  Returns the number of CPUs in the system.</td>
            </tr>
            <tr>
-             <td align="left" valign="top">0x0020</td>
+             <td align="left" valign="top"><tt>0x0020</tt></td>
              <td align="left" valign="top">Write: <b><tt>startupcpu(i)</tt></b>.
                  Starts CPU i. It begins execution at the address
                  set by a write to startupaddr (see below).</td>
            </tr>
            <tr>
-             <td align="left" valign="top">0x0030</td>
+             <td align="left" valign="top"><tt>0x0030</tt></td>
              <td align="left" valign="top">Write: <b><tt>startupaddr(addr)</tt></b>.
                  Sets the starting address for CPUs.</td>
            </tr>
            <tr>
-             <td align="left" valign="top">0x0040</td>
+             <td align="left" valign="top"><tt>0x0040</tt></td>
              <td align="left" valign="top">Write: <b><tt>pause_addr(addr)</tt></b>.
                  Sets the pause address. (TODO: This is not
                  used anymore?)</td>
            </tr>
            <tr>
-             <td align="left" valign="top">0x0050</td>
+             <td align="left" valign="top"><tt>0x0050</tt></td>
              <td align="left" valign="top">Write: <b><tt>pause_cpu(i)</tt></b>.
                  Stops all CPUs <i>except</i> CPU i.</td>
            </tr>
            <tr>
-             <td align="left" valign="top">0x0060</td>
+             <td align="left" valign="top"><tt>0x0060</tt></td>
              <td align="left" valign="top">Write: <b><tt>unpause_cpu(i)</tt></b>.
                  Unpauses all CPUs <i>except</i> CPU i.</td>
            </tr>
            <tr>
-             <td align="left" valign="top">0x0070</td>
+             <td align="left" valign="top"><tt>0x0070</tt></td>
              <td align="left" valign="top">Write: <b><tt>startupstack(addr)</tt></b>.
                  Sets the startup stack address. (CPUs started with
                  startupcpu() above will have their stack pointer
                  set to this value.)</td>
            </tr>
            <tr>
-             <td align="left" valign="top">0x0080</td>
+             <td align="left" valign="top"><tt>0x0080</tt></td>
              <td align="left" valign="top">Read: <b><tt>hardware_random()</tt></b>.
                  This produces a "random" number.</td>
            </tr>
            <tr>
-             <td align="left" valign="top">0x0090</td>
+             <td align="left" valign="top"><tt>0x0090</tt></td>
              <td align="left" valign="top">Read: <b><tt>memory()</tt></b>.
                  Returns the number of bytes of RAM in the system.</td>
            </tr>
            <tr>
-             <td align="left" valign="top">0x00a0</td>
+             <td align="left" valign="top"><tt>0x00a0</tt></td>
              <td align="left" valign="top">Write: <b><tt>ipi_one((nr &lt;&lt; 16) + cpuid)</tt></b>.
                  Sends IPI <tt>nr</tt> to a specific CPU.</td>
            </tr>
            <tr>
-             <td align="left" valign="top">0x00b0</td>
+             <td align="left" valign="top"><tt>0x00b0</tt></td>
              <td align="left" valign="top">Write: <b><tt>ipi_many((nr &lt;&lt; 16) + cpuid)</tt></b>.
                  Sends IPI <tt>nr</tt> to all CPUs <i>except</i>
                  the specified one.</td>
            </tr>
            <tr>
-             <td align="left" valign="top">0x00c0</td>
+             <td align="left" valign="top">0x00c0</tt></td>
              <td align="left" valign="top">Read: <b><tt>ipi_read()</tt></b>.
                  Returns the next pending IPI. 0 is returned if there is no
                  pending IPI (so 0 shouldn't be used for valid IPIs).
-Line 370 
 The <tt>testmips</tt> machine has the fo
+Line 346 
 The <tt>testmips</tt> machine has the fo
              <td align="left" valign="top"><i><u>Effect:</u></i></td>
            </tr>
            <tr>
-             <td align="left" valign="top">...</td>
+             <td align="left" valign="top"><tt>0x00000-</tt><br><tt>0xe0fff</tt></td>
              <td align="left" valign="top">Read: read pixel values.
                  <br>Write: write pixel values.</td>
            </tr>
-Line 378 
 The <tt>testmips</tt> machine has the fo
+Line 354 
 The <tt>testmips</tt> machine has the fo
      </td>
    </tr>
+   <tr height="15">
+     <td height="15">&nbsp;</td>
+   </tr>
+   <tr>
+     <td align="left" valign="top">
+         <b><tt>disk</tt>:</b>
+         <p>Disk controller, which can read from and write
+         to disk images. It does not use interrupts; read and
+         write operations finish instantaneously.
+         <p>Source code:&nbsp;&nbsp;<font color="#0000f0"><tt>src/devices/dev_disk.c</tt></font>
+         <br>Default physical address:&nbsp&nbsp;<font color="#0000f0">0x13000000</font>
+     </td>
+     <td></td>
+     <td align="left" valign="top">
+         <table border="0">
+           <tr>
+             <td align="left" valign="top"><i><u>Offset:</u></i>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
+             <td align="left" valign="top"><i><u>Effect:</u></i></td>
+           </tr>
+           <tr>
+             <td align="left" valign="top"><tt>0x0000</tt></td>
+             <td align="left" valign="top">Write: Set the offset (in bytes) from the beginning
+                 of the disk image. This offset will be used for the next read/write operation.</td>
+           </tr>
+           <tr>
+             <td align="left" valign="top"><tt>0x0010</tt></td>
+             <td align="left" valign="top">Write: Select the SCSI ID to be used in the next
+                 read/write operation.</td>
+           </tr>
+           <tr>
+             <td align="left" valign="top"><tt>0x0020</tt></td>
+             <td align="left" valign="top">Write: Start a read or write operation.
+                 (Writing <tt>0</tt> means a Read operation, a <tt>1</tt> means a
+                 Write operation.)</td>
+           </tr>
+           <tr>
+             <td align="left" valign="top"><tt>0x0030</tt></td>
+             <td align="left" valign="top">Read: Get status of the last operation.
+                 (Status 0 means failure, non-zero means success.)</td>
+           </tr>
+           <tr>
+             <td align="left" valign="top"><tt>0x4000-</tt><br><tt>0x41ff</tt>&nbsp;&nbsp;&nbsp;</td>
+             <td align="left" valign="top">Read/Write: 512 bytes data buffer.</td>
+           </tr>
+         </table>
+     </td>
+   </tr>
+   <tr height="15">
+     <td height="15">&nbsp;</td>
+   </tr>
+   <tr>
+     <td align="left" valign="top">
+         <b><tt>ether</tt>:</b>
+         <p>A simple ethernet controller, enough to send
+         and receive packets on a simulated network.
+         <p>Source code:&nbsp;&nbsp;<font color="#0000f0"><tt>src/devices/dev_ether.c</tt></font>
+         <br>Default physical address:&nbsp&nbsp;<font color="#0000f0">0x14000000</font>
+     </td>
+     <td></td>
+     <td align="left" valign="top">
+         <table border="0">
+           <tr>
+             <td align="left" valign="top"><i><u>Offset:</u></i>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
+             <td align="left" valign="top"><i><u>Effect:</u></i></td>
+           </tr>
+           <tr>
+             <td align="left" valign="top"><tt>0x0000-</tt><br><tt>0x3fff</tt></td>
+             <td align="left" valign="top">Read/write buffer for the packet to be sent/received.</td>
+           </tr>
+           <tr>
+             <td align="left" valign="top"><tt>0x4000</tt></td>
+             <td align="left" valign="top">Read: status word, one or more of these:
+                 <br><tt>0x01</tt>&nbsp;=&nbsp;something was received (because of
+                 the last command)
+                 <br><tt>0x02</tt>&nbsp;=&nbsp;more packets are available
+                 <br><i>NOTE:</i> Whenever the status word is non-zero,
+                         an interrupt is asserted. Reading the status word
+                         clears it, and deasserts the interrupt.</td>
+           </tr>
+           <tr>
+             <td align="left" valign="top"><tt>0x4010</tt></td>
+             <td align="left" valign="top">Read: get the Length of the received packet
+                 <br>Write: set the Length of the next packet to transmit</td>
+           </tr>
+           <tr>
+             <td align="left" valign="top"><tt>0x4020</tt></td>
+             <td align="left" valign="top">Write: command:
+                 <br><tt>0x00:</tt>&nbsp;receive a packet
+                 <br><tt>0x01:</tt>&nbsp;send a packet</td>
+           </tr>
+         </table>
+     </td>
+   </tr>
  </table></center>
  <p>
-Line 385 
 While these devices may resemble real-wo
+Line 458 
 While these devices may resemble real-wo
  intentionally made simpler to use. (An exception is the framebuffer;
  some machines actually have simple linear framebuffers like this.)
- <p>
+ <p>If the physical address is <tt>0x10000000</tt>, then for MIPS that
- If the physical address is 0x10000000, then for MIPS that means that it
+ means that it can be accessed at virtual address
- can be accessed at virtual address 0xffffffffb0000000. (Actually it can be
+ <tt>0xffffffffb0000000</tt>. (Actually it can be accessed at
- accessed at 0xffffffff90000000 too, but devices should usually be accessed
+ <tt>0xffffffff90000000</tt> too, but devices should usually be accessed in
- in a non-cached manner.)
+ a non-cached manner.)
- <p>
+ <p> (When using the PPC test machine (<tt>testppc</tt>), the addresses are
- (When using the PPC test machine (<tt>testppc</tt>), the addresses are
+ <tt>0x10000000</tt>, <tt>0x11000000</tt> etc., so no need to add any
-x10000000, 0x11000000 etc., so no need to add any virtual displacement.)
+ virtual displacement.)
- <p>The <b><tt>mp</tt></b> device is agnostic when it comes to word-length.
+ <p>The <b><tt>mp</tt></b>, <b><tt>disk</tt></b>, and <b><tt>ether</tt></b>
- For example, when reading offset 0x0000 of the <b><tt>mp</tt></b> device,
+ devices are agnostic when it comes to word-length. For example, when
- you may use any kind of read (an 8-bit read will work just as well as a
+ reading offset <tt>0x0000</tt> of the <b><tt>mp</tt></b>
--bit read, although the value will be truncated to 8 bits in the first
+ device, you may use any kind of read (an 8-bit read will work just as well
- case).
+ as a 64-bit read, although the value will be truncated to 8 bits in the
+ first case). You can <i>not</i>, however, read one byte from <tt>0x0000</tt>
+ and one from <tt>0x0001</tt>, and combine the result. The read from
+ <tt>0x0001</tt> will be invalid.
  <p>The <b><tt>cons</tt></b> device should be accessed using 8-bit reads
- and writes. Doing a getchar() (ie reading from offset 0x0000) returns 0x00
+ and writes. Doing a getchar() (ie reading from offset <tt>0x00</tt>)
- if no character was available.
+ returns <tt>0</tt> if no character was available.
  <p>On MIPS, the <b><tt>cons</tt></b> device is hardwired to interrupt 2
  (the lowest hardware interrupt). Whenever a character is available, the
-Line 411 
 interrupt is asserted. When there are no
+Line 487 
 interrupt is asserted. When there are no
  interrupt is deasserted. (Remember that the interrupt has to be enabled in
  the status register of the system coprocessor.)
- <p>The IPIs controlled by the <b><tt>mp</tt></b> device are hardwired to
+ <p>The <b><tt>ether</tt></b> device is hardwired to interrupt 3.
- interrupt 6. Whenever an IPI is "sent", interrupt 6 is asserted on the
- target CPU(s), and the IPI number is added last in the IPI queue for that
+ <p>The IPIs controlled by the <b><tt>mp</tt></b> device are hardwired to
- CPU. It is then up to that CPU to read from offset 0x00c0, to figure out
+ interrupt 6. Whenever an IPI is "sent", interrupt 6 is asserted on the
- what kind of IPI it was.
+ target CPU(s), and the IPI number is added last in the IPI queue for that
+ CPU. It is then up to that CPU to read from offset <tt>0x00c0</tt>, to
+ figure out what kind of IPI it was.
+ <p>A simple tutorial on how to use the <tt>disk</tt> device, if not clear
+ from the description above, can be found here: <a
+ href="test_disk.c"><tt>test_disk.c</tt></a>
-Line 435 
 price on ebay or at a flea market.
+Line 517 
 price on ebay or at a flea market.
  <p>
  <font color="#ff0000">
  NOTE: This is <i>not</i> a list of kernels that work in the emulator.
- It is a list of kernels that I experiment with.
+ It is a list of kernels that I have experimented with.
  </font>
  <p>
-Line 451 
 probably doesn't work in GXemul.
+Line 533 
 probably doesn't work in GXemul.
        <li><a href="http://www.netbsd.org/Ports/pmax/">NetBSD/pmax</a>:
          <br><a href="ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0/pmax/binary/kernel/netbsd-INSTALL.gz">ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0/pmax/binary/kernel/netbsd-INSTALL.gz</a>
          <br><a href="ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0/pmax/binary/kernel/netbsd-INSTALL.symbols.gz">ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0/pmax/binary/kernel/netbsd-INSTALL.symbols.gz</a>
-         <br>gunzip the files, and run the emulator with <b><tt>-E dec -e 3max -q -N -XY2</tt></b>
+         <br>gunzip the files, and run the emulator with <b><tt>-e 3max -q -N -XY2</tt></b>
          for a graphical framebuffer console. Remove <b><tt>-XY2</tt></b> and <b><tt>-N</tt></b> to use serial (stdin/stdout) console.
          Read <a href="guestoses.html#netbsdinstall">this section</a> about how to install NetBSD/pmax onto a harddisk image.
        <p>
        <li><a href="http://www.openbsd.org/pmax.html">OpenBSD/pmax</a>:
          <br><a href="ftp://ftp.se.openbsd.org/pub/OpenBSD/2.8/pmax/bsd">ftp://ftp.se.openbsd.org/pub/OpenBSD/2.8/pmax/bsd</a>
-         <br>This is an old OpenBSD kernel in a.out format. Try <b><tt>-E dec -e 3max</tt></b>.
+         <br>This is an old OpenBSD kernel in a.out format. Try <b><tt>-e 3max</tt></b>.
          <br>Read <a href="guestoses.html#openbsdinstall">this section</a> about how to install OpenBSD/pmax onto a harddisk image.
          It's a bit more complicated than installing NetBSD/pmax, but
          it usually works.
-Line 485 
 probably doesn't work in GXemul.
+Line 567 
 probably doesn't work in GXemul.
          <br>Also important: This is broken right now. :-(
          <br>Download <a href="http://lost-contact.mit.edu/afs/athena/user/d/a/daveg/Info/Links/Mach/src/release/">http://lost-contact.mit.edu/afs/athena/user/d/a/daveg/Info/Links/Mach/src/release</a>/<a href="http://lost-contact.mit.edu/afs/athena/user/d/a/daveg/Info/Links/Mach/src/release/pmax.tar.Z">pmax.tar.Z</a>
          <br><tt><b>tar xfvz pmax.tar.Z pmax_mach/special/mach.boot.MK83.STD+ANY</b></tt>
-         <br><tt><b>gxemul -E dec -e 3max -X pmax_mach/special/mach.boot.MK83.STD+ANY</b></tt>
+         <br><tt><b>gxemul -e 3max -X pmax_mach/special/mach.boot.MK83.STD+ANY</b></tt>
      </ul>
    </li>
-Line 496 
 probably doesn't work in GXemul.
+Line 578 
 probably doesn't work in GXemul.
        <li><a href="http://www.netbsd.org/Ports/sgimips/">NetBSD/sgimips</a>:
          <br><a href="ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0/sgimips/binary/kernel/netbsd-INSTALL32_IP3x.gz">ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0/sgimips/binary/kernel/netbsd-INSTALL32_IP3x.gz</a>
          <br><a href="ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0/sgimips/binary/kernel/netbsd-INSTALL32_IP3x.symbols.gz">ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0/sgimips/binary/kernel/netbsd-INSTALL32_IP3x.symbols.gz</a>
-         <br>gunzip, and try running with <b><tt>-E sgi -e ip32</tt></b>.
+         <br>gunzip, and try running with <b><tt>-e ip32</tt></b>.
          <br><a href="ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0/sgimips/binary/kernel/netbsd-INSTALL32_IP2x.gz">ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0/sgimips/binary/kernel/netbsd-INSTALL32_IP2x.gz</a>
          <br><a href="ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0/sgimips/binary/kernel/netbsd-INSTALL32_IP2x.symbols.gz">ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0/sgimips/binary/kernel/netbsd-INSTALL32_IP2x.symbols.gz</a>
-         <br>gunzip, and try running with <b><tt>-E sgi -e ip22</tt></b> (or <b><tt>ip24</tt></b> or <b><tt>ip20</tt></b>).
+         <br>gunzip, and try running with <b><tt>-e ip22</tt></b> (or <b><tt>ip24</tt></b> or <b><tt>ip20</tt></b>).
        <p>
        <li>Linux/SGI:
          <br>Some kernels are available here: <a href="http://www.linux-mips.org/~glaurung/">http://www.linux-mips.org/~glaurung/</a>
-         <br>Try running with <b><tt>-E sgi -e ip32 -X</tt></b> for a graphical framebuffer, or
+         <br>Try running with <b><tt>-e ip32 -X</tt></b> for a graphical framebuffer, or
-                 <b><tt>-E sgi -e ip32 -o 'console=ttyS0'</tt></b> for serial console.
+                 <b><tt>-e ip32 -o 'console=ttyS0'</tt></b> for serial console.
          <br>Adding <b><tt>-b</tt></b> (bintrans) might work sometimes.
          <br>(You need to add <b><tt>-CR5000</tt></b> if you're trying to run
                  a kernel compiled for R5000, because Linux doesn't autodetect
                  the CPU type at runtime.)
          <br>Also: <a href="http://www.tal.org/~milang/o2/kernels/">http://www.tal.org/~milang/o2/kernels</a>/<a href="http://home.tal.org/~milang/o2/kernels/vmlinux64-2.6.8.1-IP32">vmlinux64-2.6.8.1-IP32</a>
-         <br>Try <b><tt>-E sgi -e ip32 -X -CR5000 vmlinux64-2.6.8.1-IP32</tt></b>.
+         <br>Try <b><tt>-e ip32 -X -CR5000 vmlinux64-2.6.8.1-IP32</tt></b>.
          <br>And also some IP27 kernels:
                  <a href="http://www.total-knowledge.com/progs/mips/kernels/vmlinux.ip27-20040428">http://www.total-knowledge.com/progs/mips/kernels/vmlinux.ip27-20040428</a>
                  and
                  <a href="http://www.total-knowledge.com/progs/mips/kernels/vmlinux.ip27-20040528.bz2">http://www.total-knowledge.com/progs/mips/kernels/vmlinux.ip27-20040528.bz2</a>
                  (but unfortunately these lack symbols).
-         <br>Try the IP27 kernels with <b><tt>-E sgi -e ip27 -t</tt></b>.
+         <br>Try the IP27 kernels with <b><tt>-e ip27 -t</tt></b>.
        <p>
        <li><a href="http://www.openbsd.org/sgi.html">OpenBSD/sgi</a>:
          <br><a href="ftp://ftp.openbsd.org/pub/OpenBSD/3.7/sgi/bsd.rd">ftp://ftp.openbsd.org/pub/OpenBSD/3.7/sgi/bsd.rd</a>
          <br>More recent snapshots can be found at <a href="ftp://ftp.OpenBSD.org/pub/OpenBSD/snapshots/sgi/">ftp://ftp.OpenBSD.org/pub/OpenBSD/snapshots/sgi/</a>.
-         <br>Try <b><tt>gxemul -E sgi -e ip32 bsd.rd</tt></b>
+         <br>Try <b><tt>gxemul -e ip32 bsd.rd</tt></b>
        <p>
        <li><a href="http://www.freebsd.org/platforms/mips.html">FreeBSD/MIPS</a>:
                  I don't think public binary snapshots are available yet.
-Line 529 
 probably doesn't work in GXemul.
+Line 611 
 probably doesn't work in GXemul.
        <li>arcdiag:
          <br>The NetBSD people have also made available an "arcdiag" for SGI-IP22:
          <br><a href="ftp://ftp.netbsd.org/pub/NetBSD/arch/sgimips/arcdiag.ip22">ftp://ftp.netbsd.org/pub/NetBSD/arch/sgimips/arcdiag.ip22</a>
-         <br>Try running <tt><b>gxemul -E sgi -e ip22 -x arcdiag.ip22</b></tt>.
+         <br>Try running <tt><b>gxemul -e ip22 -x arcdiag.ip22</b></tt>.
      </ul>
    </li>
-Line 540 
 probably doesn't work in GXemul.
+Line 622 
 probably doesn't work in GXemul.
        <li><a href="http://www.netbsd.org/Ports/arc/">NetBSD/arc</a>:
          <br><a href="ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0/arc/binary/kernel/netbsd-RAMDISK.gz">ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0/arc/binary/kernel/netbsd-RAMDISK.gz</a>
          <br><a href="ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0/arc/binary/kernel/netbsd-RAMDISK.symbols.gz">ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0/arc/binary/kernel/netbsd-RAMDISK.symbols.gz</a>
-         <br>gunzip, and try with <b><tt>-E arc -e rd94</tt></b>.
+         <br>gunzip, and try with <b><tt>-e rd94</tt></b>.
          <br>(You may also try other ARC models.)
          <br>Read <a href="guestoses.html#netbsdarcinstall">this section</a> about how
                  to install NetBSD/arc 1.6.2 onto a harddisk image.
-Line 548 
 probably doesn't work in GXemul.
+Line 630 
 probably doesn't work in GXemul.
        <p>
        <li><a href="http://www.openbsd.org/arc.html">OpenBSD/arc</a>:
          <br><a href="ftp://ftp.se.openbsd.org/pub/OpenBSD/2.3/arc/bsd.rd.elf">ftp://ftp.se.openbsd.org/pub/OpenBSD/2.3/arc/bsd.rd.elf</a>
-         <br>Try running with <b><tt>-X -E arc -e pica</tt></b> or <b><tt>-X -E arc -e tyne</tt></b>.
+         <br>Try running with <b><tt>-X -e pica</tt></b> or <b><tt>-X -e tyne</tt></b>.
          <br>Read <a href="guestoses.html#openbsdarcinstall">this section</a> about how
                  to install OpenBSD/arc onto a harddisk image.
        <p>
        <li>Linux:
          <br><a href="ftp://ftp.linux-mips.org/pub/linux/mips/mipsel-linux/boot/vmlinux-m700-2.1.131.gz">ftp://ftp.linux-mips.org/pub/linux/mips/mipsel-linux/boot/vmlinux-m700-2.1.131.gz</a>
-         <br>gunzip, and run with <b><tt>-v -J -X -N -E arc -e m700</tt></b> (Olivetti M700)
+         <br>gunzip, and run with <b><tt>-v -J -X -N -e m700</tt></b> (Olivetti M700)
          <br>(This probably doesn't work anymore.)
        <p>
        <li>Pandora:
          <br><a href="ftp://ftp.linux-mips.org/pub/linux/mips/ancient/milo/">ftp://ftp.linux-mips.org/pub/linux/mips/ancient/milo</a>/<a href="ftp://ftp.linux-mips.org/pub/linux/mips/ancient/milo/milo-0.27.1.tar.gz">milo-0.27.1.tar.gz</a>
          <br>A generic test/diagnostics program for ARC-based machines.
-         <br>Run with <b><tt>-E arc -e r94 milo-0.27.1/pandora</tt></b>
+         <br>Run with <b><tt>-e r94 milo-0.27.1/pandora</tt></b>
        <p>
        <li>arcdiag:
          <br>Precompiled binary:<a href="ftp://ftp.netbsd.org/pub/NetBSD/arch/arc/arcdiag">ftp://ftp.netbsd.org/pub/NetBSD/arch/arc/arcdiag</a>
          <br>(alternative: <a href="http://www.sensi.org/~alec/mips/arcdiag">http://www.sensi.org/~alec/mips/arcdiag</a>)
          <br>A generic test/diagnostics program for ARC-based machines.
-         <br>Run with <b><tt>-E arc -e pica arcdiag</tt></b> (or some other ARC mode).
+         <br>Run with <b><tt>-e pica arcdiag</tt></b> (or some other ARC mode).
          <br>Example arcdiag output (from real machines):
          <br><a href="http://mail-index.netbsd.org/port-arc/2000/10/18/0001.html">http://mail-index.netbsd.org/port-arc/2000/10/18/0001.html</a> (Olivetti M700-10)
          <br><a href="http://www.sensi.org/~alec/mips/arcdiag.txt">http://www.sensi.org/~alec/mips/arcdiag.txt</a> (PICA-61)
-Line 586 
 probably doesn't work in GXemul.
+Line 668 
 probably doesn't work in GXemul.
          <br>I have tried this with the Swedish version, but it might
                  work with other versions too.<pre>
          $ <b><tt>dd if=/dev/zero of=winnt_test.img bs=1024 count=1 seek=999000</tt></b>
-         $ <b><tt>gxemul -X -Earc -epica -d winnt_test.img -d bc6:/dev/cd0c -j MIPS\\ARCINST</tt></b>
+         $ <b><tt>gxemul -X -e pica -d winnt_test.img -d bc6:/dev/cd0c -j MIPS\\ARCINST</tt></b>
-         $ <b><tt>gxemul -X -Earc -epica -d winnt_test.img -d bc6:/dev/cd0c -j MIPS\\SETUPLDR</tt></b>
+         $ <b><tt>gxemul -X -e pica -d winnt_test.img -d bc6:/dev/cd0c -j MIPS\\SETUPLDR</tt></b>
  </pre>  <br><tt>ARCINST</tt> tries to prepare the disk image for installation. (It <i>almost</i> works.)
          <br><tt>SETUPLDR</tt> should load some drivers from the cdrom, but then it crashes with a bluescreen.
      </ul>
-Line 599 
 probably doesn't work in GXemul.
+Line 681 
 probably doesn't work in GXemul.
      <ul>
        <li><a href="http://www.netbsd.org/Ports/hpcmips/">NetBSD/hpcmips</a>:
          <br><a href="ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0/hpcmips/installation/">ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0/hpcmips/installation</a>/<a href="ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0/hpcmips/installation/netbsd.gz">netbsd.gz</a>
-         <br>Try <b><tt>gxemul -X -E hpc -e mobilepro770 netbsd</tt></b>
+         <br>Try <b><tt>gxemul -X -e mobilepro770 netbsd</tt></b>
          <br><a href="ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0/hpcmips/binary/kernel/netbsd-GENERIC.gz">ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0/hpcmips/binary/kernel/netbsd-GENERIC.gz</a>
-         <br>Try <b><tt>gxemul -X -E hpc -e mobilepro770 netbsd-GENERIC</tt></b>
+         <br>Try <b><tt>gxemul -X -e mobilepro770 netbsd-GENERIC</tt></b>
        <p>
        <li>Linux for BE300:
          <br><a href="http://www.linux4.be/2004/linux4be20040908.zip">http://www.linux4.be/2004/linux4be20040908.zip</a>
-         <br>Try <b><tt>gxemul -X -E hpc -e be300 vmlinux</tt></b>
+         <br>Try <b><tt>gxemul -X -e be300 vmlinux</tt></b>
        <p>
        <li>Linux for Agenda VR3:
          <br>Download <a href="http://agenda-snow.sourceforge.net/kernel-old-versions/binary/">http://agenda-snow.sourceforge.net/kernel-old-versions/binary</a>/<a href="http://agenda-snow.sourceforge.net/kernel-old-versions/binary/root1.2.6.kernel-8.00">root1.2.6.kernel-8.00</a>
          <br>and <a href="http://vr3.uid0.sk/cd/Software/VR3_Distributions/H2O/">http://vr3.uid0.sk/cd/Software/VR3_Distributions/H2O</a>/<a href="http://vr3.uid0.sk/cd/Software/VR3_Distributions/H2O/root1.2.6.cramfs">root1.2.6.cramfs</a>.
          <br>(or <a href="http://www.ipsec.info/~www/agenda/dream-1-noxip.cramfs">http://www.ipsec.info/~www/agenda/dream-1-noxip.cramfs</a>)
-         <br>Try <b><tt>gxemul -X -E hpc -e vr3 -x 0xbf200000:root1.2.6.cramfs 0xbf000000:0:0xbf0005e0:root1.2.6.kernel-8.00</tt></b>
+         <br>Try <b><tt>gxemul -X -e vr3 -x 0xbf200000:root1.2.6.cramfs 0xbf000000:0:0xbf0005e0:root1.2.6.kernel-8.00</tt></b>
          <br>(or replace root1.2.6.cramfs with dream-1-noxip.cramfs)
          <br>Remove <b><tt>-X</tt></b> to try with serial console instead of X, and
                  remove <b><tt>-b</tt></b> to try without (old) bintrans.
-Line 623 
 probably doesn't work in GXemul.
+Line 705 
 probably doesn't work in GXemul.
        <li>Linux for MobilePro etc.:
          <br><a href="http://pc1.peanuts.gr.jp/~kei/Hard-Float/Kernels/">http://pc1.peanuts.gr.jp/~kei/Hard-Float/Kernels/</a>
          <br>Uncompress the archive to get a kernel, vmlinux-800 for example.
-         <br>Try <b><tt>./gxemul -X -o 'root=/dev/hda1' -d r:disk.img -d r:disk.img -Ehpc -e mobilepro800 vmlinux-800</tt></b>
+         <br>Try <b><tt>./gxemul -X -o 'root=/dev/hda1' -d r:disk.img -d r:disk.img -e mobilepro800 vmlinux-800</tt></b>
          <br>where disk.img is an ext2fs filesystem with contents from
          <a href="http://pc1.peanuts.gr.jp/~kei/Hard-Float/Miniroots/miniroot-20010330.tar.bz2">http://pc1.peanuts.gr.jp/~kei/Hard-Float/Miniroots/miniroot-20010330.tar.bz2</a>
          <br>(Note the double disk arguments.)
-Line 631 
 probably doesn't work in GXemul.
+Line 713 
 probably doesn't work in GXemul.
        <p>
        <li><a href="http://www.disorder.ru/openbsd/be300/">OpenBSD/be300</a>:
          <br><a href="http://www.disorder.ru/openbsd/be300/bsd.rd">http://www.disorder.ru/openbsd/be300/bsd.rd</a>
-         <br>Try <b><tt>gxemul -X -E hpc -e be300 bsd.rd</tt></b>
+         <br>Try <b><tt>gxemul -X -e be300 bsd.rd</tt></b>
          <br>Note: bintrans might be buggy, so you can try with -B if you want to.
      </ul>
    </li>
-Line 649 
 probably doesn't work in GXemul.
+Line 731 
 probably doesn't work in GXemul.
        <li>Linux:
          <br><a href="http://people.debian.org/~pm/mips-cobalt/nfsroot/vmlinux_raq-2800.gz">http://people.debian.org/~pm/mips-cobalt/nfsroot/vmlinux_raq-2800.gz</a>
          <br>gunzip, and run with <b><tt>-E cobalt</tt></b>
+         <p>
+         <br><a href="http://dev.gentoo.org/~kumba/mips/cobalt/netboot/cobalt-netboot-20040428.img.gz">http://dev.gentoo.org/~kumba/mips/</a>
+         <br>    <a href="http://dev.gentoo.org/~kumba/mips/cobalt/netboot/cobalt-netboot-20040428.img.gz">cobalt/netboot/cobalt-netboot-20040428.img.gz</a>
+         <br><b><tt>gxemul -E cobalt cobalt-netboot-20040428.img.gz</tt></b>
        <p>
        <li>CoLo:
          <br><a href="http://www.colonel-panic.org/cobalt-mips/colo/colo-1.19.tar.gz">http://www.colonel-panic.org/cobalt-mips/colo/colo-1.19.tar.gz</a>
-Line 682 
 probably doesn't work in GXemul.
+Line 768 
 probably doesn't work in GXemul.
      <ul>
        <li><a href="http://www.netbsd.org/Ports/evbmips/">NetBSD/evbmips</a>:
          <br><a href="ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0.2/evbmips-mipseb/binary/kernel/">ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0.2/evbmips-mipseb/binary/kernel</a>/<a href="ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0.2/evbmips-mipseb/binary/kernel/netbsd-MALTA.gz">netbsd-MALTA.gz</a>
-         <br><b><tt>gxemul -E evbmips -e malta netbsd-MALTA</tt></b>
+         <br><b><tt>gxemul -e malta netbsd-MALTA</tt></b>
          <br>The default CPU is a 5Kc (MIPS64). Add
                  <tt>-C 4Kc</tt> to use a MIPS32 CPU instead.
          <br>(NetBSD/evbmips runs in 32-bit mode on MIPS64 anyway...)
-Line 690 
 probably doesn't work in GXemul.
+Line 776 
 probably doesn't work in GXemul.
          section</a> on how to install NetBSD/evbmips onto a harddisk image.
          <br>or
          <br><a href="ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0.2/evbmips-mipseb/binary/kernel/">ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0.2/evbmips-mipseb/binary/kernel</a>/<a href="ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-2.0.2/evbmips-mipseb/binary/kernel/netbsd-PB1000.gz">netbsd-PB1000.gz</a>
-         <br><b><tt>gxemul -E evbmips -e pb1000 netbsd-PB1000</tt></b>
+         <br><b><tt>gxemul -e pb1000 netbsd-PB1000</tt></b>
      </ul>
    </li>
-Line 837 
 The following don't work at all, or just
+Line 923 
 The following don't work at all, or just
    </li>
  </ul>
- <p>
- The URISC emulation mode is just for fun. (Read
- <a href="http://en.wikipedia.org/wiki/URISC">http://en.wikipedia.org/wiki/URISC</a>
- for more info.)
- <p>
- <ul>
-   <li>URISC:
-     <ul>
-       <li>I've placed a small test program in the experiments directory.
-         <br>Start like this: <tt><b>gxemul -E testurisc 0:urisc_test.bin</b></tt>
-         <br>or, if you want to single-step:
-                 <b><tt>gxemul -V -E testurisc 0:urisc_test.bin</b></tt>
-         <br>2005-03-01: All outputed characters are printed twice. I'll
-         try to make a pseudo-device for outputing to "normal" devices
-         later.
-     </ul>
-   </li>
- </ul>

 Legend:



Removed from v.11
 


changed lines


 
Added in v.12
 Legend:



Removed from v.11
 


changed lines


 
Added in v.12
-Removed from v.11
+Added in v.12

	ViewVC Help
Powered by ViewVC 1.1.26