/[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 41 by dpavlin,
Mon Oct  8 16:21:17 2007 UTC
+revision 42 by dpavlin,
Mon Oct  8 16:22:32 2007 UTC
 Line 10
  <!--
- $Id: experiments.html,v 1.105 2006/12/30 13:30:50 debug Exp $
+ $Id: experiments.html,v 1.110 2007/06/15 18:07:08 debug Exp $
  Copyright (C) 2003-2007  Anders Gavare.  All rights reserved.
 Line 65 
 that you do two things:
  <p>
  <ul>
-   <li>Build and install a cross-compiler for your chosen target.
+   <li>Build and install a cross-compiler for your chosen target,
+         e.g. <tt>mips64-unknown-elf</tt>.
          GCC is usually a good compiler choice, because it is portable
          and in wide-spread use. (Other compilers should work too.)
-Line 231 
 following experimental devices:
+Line 232 
 following experimental devices:
            <tr>
              <td align="left" valign="top"><tt>0x00d0</tt></td>
              <td align="left" valign="top">Read: <b><tt>ncycles()</tt></b>.
-                 Returns approximately the number of cycles executed.
+                 Returns approximately the number of cycles executed on
-                 Note: this value is not updated for every instruction,
+                 this CPU. Note: this value is not updated for every instruction,
                  so it cannot be used for small measurements.</td>
            </tr>
          </table>
-Line 415 
 following experimental devices:
+Line 416 
 following experimental devices:
      </td>
    </tr>
+   <tr height="15">
+     <td height="15">&nbsp;</td>
+   </tr>
+   <tr>
+     <td align="left" valign="top">
+         <a name="expdevices_irqc"><b><tt>irqc</tt>:</b></a>
+         <p>An Interrupt Controller. (Note: Not used for the MIPS test machine.)
+         <p>Source code:&nbsp;&nbsp;<font color="#0000f0"><tt>src/devices/dev_irqc.c</tt></font>
+         <p>Include file:&nbsp;&nbsp;<font color="#0000f0"><tt>dev_irqc.h</tt></font>
+         <br>Default physical address:&nbsp&nbsp;<font color="#0000f0">0x16000000</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>0x0</tt></td>
+             <td align="left" valign="top">Read: IRQ status as a 32-bit word, one bit per interrupt source.</td>
+           </tr>
+           <tr>
+             <td align="left" valign="top"><tt>0x4</tt></td>
+             <td align="left" valign="top">Write: Mask one interrupt source. Value should be an integer 0..31.</td>
+           </tr>
+           <tr>
+             <td align="left" valign="top"><tt>0x8</tt></td>
+             <td align="left" valign="top">Write: Unmask one interrupt source. Value should be an integer 0..31.</td>
+           </tr>
+         </table>
+     </td>
+   </tr>
  </table></center>
- <p>
+ <p>The include files for the test machine devices are found in
- While these devices may resemble real-world hardware, they are
+ <a href="../src/include/testmachine/"><tt>src/include/testmachine/</tt></a>.
+ <p>While these devices may resemble real-world hardware, they are
  intentionally made simpler to use. (An exception is the framebuffer;
  some machines actually have simple linear framebuffers like this.)
-Line 428 
 means that it can be accessed at virtual
+Line 466 
 means that it can be accessed at virtual
  <tt>0xffffffff90000000</tt> too, but devices should usually be accessed in
  a non-cached manner.)
- <p>When using the Alpha, ARM, or PPC test machines, the addresses are
+ <p>When using the ARM or PPC test machines, the addresses are
  <tt>0x10000000</tt>, <tt>0x11000000</tt> etc., so no need to add any
  virtual displacement.
-Line 462 
 what kind of IPI it was.
+Line 500 
 what kind of IPI it was.
  <p><center>
  <table border="1">
          <tr><td align="center">
-                 <b><tt>testmips</tt></b>
+                 <b><tt>testmips</tt></b> (as native MIPS interrupts)
          </td></tr>
          <tr><td>
                  <table border="0">
-Line 481 
 what kind of IPI it was.
+Line 519 
 what kind of IPI it was.
                  </table>
          </td></tr>
  </table>
+ <p><table border="1">
+         <tr><td align="center">
+                 <b><tt>testarm</tt> and others</b> (via the <tt>irqc</tt> device)
+         </td></tr>
+         <tr><td>
+                 <table border="0">
+                 <tr><td align="center">IRQ:</td><td>&nbsp;</td>
+                         <td>Used for:</td></tr>
+                 <tr><td align="center">6</td><td></td>
+                         <td><tt>mp</tt> (inter-processor interrupts)</td></tr>
+                 <tr><td align="center">4</td><td></td>
+                         <td><tt>rtc</tt></td></tr>
+                 <tr><td align="center">3</td><td></td>
+                         <td><tt>ether</tt></td></tr>
+                 <tr><td align="center">2</td><td></td>
+                         <td><tt>cons</tt></td></tr>
+                 </table>
+         </td></tr>
+ </table>
  </center>
- <p>Other machines:  TODO
  <p><br>

 Legend:



Removed from v.41
 


changed lines


 
Added in v.42
 Legend:



Removed from v.41
 


changed lines


 
Added in v.42
-Removed from v.41
+Added in v.42

	ViewVC Help
Powered by ViewVC 1.1.26