/[gxemul]/trunk/TODO

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/TODO

Parent Directory | Revision Log | View Patch Patch

-revision 32 by dpavlin,
Mon Oct  8 16:20:58 2007 UTC
+revision 40 by dpavlin,
Mon Oct  8 16:22:11 2007 UTC
 Line 1
- $Id: TODO,v 1.410 2006/11/06 05:32:38 debug Exp $
+ $Id: TODO,v 1.489 2007/05/01 04:05:06 debug Exp $
- This file is my list of things I want to work on in the future. It is in
+ --------------------------------------------
- random order, and some parts of it are probably out-to-date by now.
+ Testing for the next release (0.4.5.1):
+ TEST DISK OVERLAY IMAGES
+ TEST LANDISK/SUPERH EMULATION MODES
+ REGRESSION TESTS FOR ALL OTHER SUPPORTED GUEST OSES
+ # NetBSD/pmax 3.1 or 1.6.2      OK
+ # NetBSD/arc 1.6.2              OK
+ # NetBSD/hpcmips 3.1            OK
+ # NetBSD/cobalt 3.1             OK
+ # NetBSD/evbmips 3.1            OK
+ # NetBSD/algor 3.1              OK
+ # NetBSD/sgimips 3.1            OK
+ # NetBSD/cats 3.1               OK
+ # NetBSD/evbarm 2.1             OK
+ # NetBSD/netwinder 3.1          OK
+ # NetBSD/prep 2.1               OK
+ # NetBSD/macppc 3.1             OK
+ # NetBSD/dreamcast 3.1 MD       OK
+ # NetBSD/dreamcast 3.1 LiveCD   OK
+ # Linux/dreamcast Live CD       OK
+ # OpenBSD/pmax 2.8-BETA         not tested because of lack of time
+ # OpenBSD/cats 4.0              OK
+ # OpenBSD/landisk 4.1           OK
+ # Ultrix/RISC 4.5               OK
+ # Sprite for DECstation         OK
+ # Debian GNU/Linux for pmax     not tested because of lack of time
+ Optional:
+ # OpenBSD/sgi                   FAILED to boot after setup (as expected)
+ --------------------------------------------
+ Some things, in totally random order, that I'd like to fix:
+ (Some items in this list are possibly out-of-date by now.)
  Dyntrans:
          x)  Instruction combination collisions? How to avoid easily...
-Line 16 
 Dyntrans:
+Line 50 
 Dyntrans:
              kludgy very fast.)
          x)  Dyntrans with SMP... lots of work to be done here.
          x)  Dyntrans with cache emulation... lots of work here as well.
+         x)  Remove the concept of base RAM completely; it would be more
+             generic to allow RAM devices to be used "anywhere".
          o)  dev_mp doesn't work well with dyntrans yet
          o)  In general, IPIs, CAS, LL/SC etc must be made to work with dyntrans
          x)  Redesign/rethink the delay slot mechanism used for e.g. MIPS,
-Line 36 
 Dyntrans:
+Line 72 
 Dyntrans:
              (containing code)
          x)  16-bit encodings? (MIPS16, ARM Thumb, 32-bit SH on SH64)
          x)  Lots of other stuff: see src/cpus/README_DYNTRANS
-         x)  true recompilation backend? think carefully about this,
+         x)  Native code generation backends:
-             experiment in a separate project (not in GXemul)
+                 o)  think carefully about this.
-                 o) First test would be to just implement a simple
+                 o)  simple syntax for emitting opcodes; backend implementation
-                    instruction such as MIPS' addiu or lui, on AMD64
+                     must be optional, so I don't have to write more code
-                    hosts...
+                     than necessary. after all, the non-native (C) code should
+                     always work.
+                 o)  convert into native code only after an entire
+                         block has been translated? probably best.
+                 o)  the "almost native" opcodes may be rearranged,
+                     "peep-hole optimized", etc. and then as a separate step
+                     this list of almost native opcodes is written out
+                     as native code.
+                 o)  think about delay slots at the end of a block!
+                 o)  x86/amd64 code generator can be very similar... perhaps
+                 o)  NOTE that generation is per _ABI_, not per host arch!
+                     the configure script must detect ABI!!!
+                 o)  branches to already translated code blocks can
+                         link the blocks together
+                 o)  load/store are the most important to optimize
  Simple Valgrind-like checks?
          o)  Mark every address with bits which tell whether or not the address
-Line 86 
 MIPS:
+Line 136 
 MIPS:
                  x)  watchhi/watchlo exceptions, and other exception
                      handling details
          o)  R10000 and others:  (R12000, R14000 ?)
+                 x)  The code before the line
+                         /*  reg[COP0_PAGEMASK] = cpu->cd.mips.coproc[0]->tlbs[0].mask & PAGEMASK_MASK;  */
+                     in cpu_mips.c is not correct for R10000 according to
+                     Lemote's Godson patches for GXemul. TODO: Go through all
+                     register definitions according to http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi/hdwr/bks/SGI_Developer/books/R10K_UM/sgi_html/t5.Ver.2.0.book_263.html#HEADING334
+                     and make sure everything works with R10000.
+                     Then test with OpenBSD/sgi?
+                 x)  Entry LO mask (as above).
                  x)  memory space, exceptions, ...
                  x)  use cop0 framemask for tlb lookups
                      (http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi/hdwr/bks/SGI_Developer/books/R10K_UM/sgi_html/t5.Ver.2.0.book_284.html)
  SuperH:
-         x)  DMA (0xffa00000)
+         x)  SH4 performance is VERY low when running user-space instructions,
-         x)  Instruction tracing should include symbols for branch targets,
+             because I actually simulate the 4-entry ITLB as being separate
-             and so on...
+             from the 64-entry DTLB. This is correct, but VERY slow. I need
+             to experiment with _not_ simulating it in too much detail.
          x)  SH4 interrupt controller:
-                 x)  Implement correct priorities of interrupts
+                 x)  MASKING should be possible!
+         x)  SH4 DMA (0xffa00000)
+         x)  SH4 UBC (0xff200000)
+         x)  Store queues can copy 32 bytes at a time, there's no need to
+             copy individual 32-bit words. (Performance improvement.)
          x)  SH4 BSC (Bus State Controller)
-         x)  NetBSD/evbsh3, dreamcast, mmeye, hpcsh! Linux?
+         x)  Instruction tracing should include symbols for branch targets,
+             and so on, to make the output more human readable.
+         x)  SH3-specific devices: Pretty much everything!
+         x)  NetBSD/evbsh3, mmeye, hpcsh! Linux?
          x)  Replace pc-relative loads with immediate load, if within the
              same page. (Similar to the same optimization for ARM.)
-         x)  Floating point exception correctness.
          x)  Floating point speed!
+         x)  Floating point exception correctness.
+         x)  NetBSD HEAD (as of April 2007) hangs during bootup, because it
+             turns on/off interrupts in an unfortunately synchronized way
+             with dyntrans. This needs to be fixed.
+         x)  Exceptions for unaligned load/stores. OpenBSD/landisk uses
+             this mechanism for its reboot code (machine_reset).
          x)  Think carefully about how to implement SH5/SH64 (for evbsh5).
+ Landisk SH4:
+         x)  When NetBSD/landisk 4.0 has been released, make sure it works
+             in the emulator. (Update documentation, etc.)
  Dreamcast:
-         x)  CD image bootup:
+         x)  G2 DMA
-)  Find IP.BIN, and load it to 0x8c008000.
+         x)  LAN adapter (dev_mb8696x.c).  NetBSD root-on-nfs.
-)  Run code at 0x8c008300 (SEGA license code).
-)  When the license code runs a "boot menu" syscall,
-                     load the 1ST_READ.BIN file (unscrambled?) to 0x8c010000.
-)  Run code at 0x8c00b800 (Bootstrap 1). This will in turn
-                     jump to 0x8c00e000 (Bootstrap 2), and then jump to
-x8c010000, to start the program.
-                 (Try with e.g. Comstedt's Serial IP Slave, to make sure it
-                 works as expected.)
-         x)  LAN adapter.
          x)  PVR:  Lots of stuff. See dev_pvr.c.
+         x)  Better GDROM support
+         x)  Modem
+         x)  PCI bridge/bus?
          x)  Maple bus:
                  x)  Correct controller input
                  x)  Mouse input
-         x)  PROM/BIOS calls:
+         x)  Software emulation of BIOS calls:
-                 x)  GD-ROM emulation
+                 x)  GD-ROM emulation: Use the GDROM device.
-         x)  NetBSD/dreamcast: Root on nfs?
+                 x)  Use the VGA font as a fake ROM font. (Better than
-         x)  Linux/dreamcast? (The gentoo kernel currently crashes.)
+                     nothing.)
+         x)  Make as many as possible of the KOS examples run!
          x)  More homebrew demos/games.
-         x)  Sound emulation (ARM cpu).
+         x)  SPU: Sound emulation (ARM cpu).
-         x)  VME processor emulation?
+         x)  VME processor emulation? "(Sanyo LC8670 "Potato")" according to
+             Wikipedia, LC86K87 according to Comstedt's page. See
- Transputer:
+             http://www.maushammer.com/vmu.html for a good description of
-         x)  Implement support for Helios binaries.
+             the differences between LC86104C and the one used in the VME.
-         x)  Stack and register contents at startup?
-         x)  Figure out how to boot an entire Helios distribution.
-         x)  Implement all instructions. :)
- RCA1802/RCA1805, CHIP8:
-         x)  CHIP8 -> RCA180x conversion
-                 x)  Think about how to do dual-mode, variable-instr-length
-                     ISAs, and switch between modes.
-                 x)  1805 "extended" opcode -> trigger CHIP8 emulation?
-                         That is, all calls 0NNN could point to 0x68 opcodes,
-                         which, if running on a 1802 in CHIP8-emulation-mode,
-                         would be manually interpreted.
-                 x)  Better solution:
-                         CHIP8 calls to 00xx => handle at high level,
-                               calls to 0xxx in general = call 180X machine code
-                                 (0000 = reboot?)
-         x)  1802 info: http://www.nyx.net/~lturner/public_html/Cosmac.html
-             and:  http://www.elf-emulation.com/1802.html
-         x)  1805 extended opcodes: Implement at least disassembly support!
-         x)  Keyboard input.
-         x)  Sound (beep only).
-         x)  Slow-down to correct speed? Wikipedia: "it was usually operated
-             at 3.58 MHz/2 to suit the requirements of the 1861 chip which
-             gave a speed of a little over 100,000 instructions per second"
-             (Note that _CHIP8_ emulation would then be even slower.)
-         x)  SCHIP48 (Super) emulation:
-                 Some more opcodes, 128x64 framebuffer, larger
-                 sprites and fonts.
  Alpha:
          x)  OSF1 PALcode, Virtual memory support.
-Line 168 
 Alpha:
+Line 210 
 Alpha:
          x)  More Alpha machine types, so it could work with
              OpenBSD, FreeBSD, and Linux too?
- SPARC:
+ SPARC (both the ISA and the machines):
          o)  Implement Adress space identifiers; load/stores etc.
-         o)  Save/restore register windows etc!
+         o)  Exception/trap/interrupt handling.
+         o)  Save/restore register windows etc! Both v9 and pre-v9!
          o)  Finish the subcc and addcc flag computation code.
          o)  Add more registers (floating point, control regs etc)
-         o)  Exception/trap handling.
          o)  Disassemly of some more instructions?
          o)  Are sll etc 32-bit sign-extending or zero-extending?
-         o)  Finish the GDB register stuff.
+         o)  Floating point exception correctness.
-         x)  Floating point exception correctness.
          o)  SPARC v8, v7 etc?
+         o)  More machine modes and devices.
  Debugger:
          o)  How does SMP debugging work? Does it simply use "threads"?
-Line 187 
 Debugger:
+Line 229 
 Debugger:
          o)  Try to make the debugger more modular and, if possible, reentrant!
          o)  Remove the emul command? (But show network info if showing
                  machines?)
+         o)  Evaluate expressions within []? That would allow stuff like
+                 cpu[x] where x is an expression.
          o)  Settings:
                  x)  Special handlers for Write!
                          +)  MIPS coproc regs
-Line 196 
 Debugger:
+Line 240 
 Debugger:
          o)  see src/debugger.c for more
  POWER/PowerPC:
-         x)  find and fix the bug which causes NetBSD/macppc to fail after
+         x)  Fix DECR timer speed, so it matches the host.
-             an install!
          x)  NetBSD/prep 3.x triggers a possible bug in the emulator:
              <wdc_exec_command(0xd005e514,0xd60cdd30,0,8,..)>
                <ata_get_xfer(0,0xd60cdd30,0,8,..)>
-Line 221 
 POWER/PowerPC:
+Line 264 
 POWER/PowerPC:
          x)  Floating point exception correctness.
          x)  Alignment exceptions.
+ PReP:
+         x)  Clock time! ("Bad battery blah blah")
  Algor:
          o)  Other models than the P5064?
          o)  PCI interrupts... needed for stuff like the tlp NIC?
+ BeBox:
+         o)  Interrupts. There seems to be a problem with WDC interrupts
+             "after a short while", although a few interrupts get through?
+         o)  Perhaps find a copy of BeOS and try it?
  HPCmips:
          x)  Mouse/pad support! :)
          x)  A NIC? (As a PCMCIA device?)
+ M88K:
+         o)  Everything. :)
+                 o)  More instruction disassembly!
+                 o)  Implement more instructions.
+                 o)  has-delay-slot (for debugging)
+                 o)  Find manuals!
+                 o)  MMU stuff
+                 o)  Exceptions
+                 o)  FPU
+                 o)  Control registers
  AVR:
          o)  Everything.
- AVR32:
-         o)  Everything. It would be good if there was NetBSD/avr32 to
-             experiment with...
  ARM:
          o)  See netwinder_reset() in NetBSD; the current "an internal error
              occured" message after reboot/halt is too ugly.
          o)  ARM "wait"-like instruction?
-         o)  try to get netbsd/evbarm 3.x running (iq80321)
+         o)  try to get netbsd/evbarm 3.x or 4.x running (iq80321)
          o)  make the xscale counter registers (ccnt) work
          o)  make the ata controller usable for FreeBSD!
-         o)  zaurus for openbsd...
+         o)  Zaurus emulation:
-         o)  debian/cats crashes because of unimplemented coproc stuff.
+                 x)  OpenBSD/zaurus
+                 x)  NetBSD/zaurus? See the following URL:
+                     http://mail-index.netbsd.org/port-arm/2006/11/19/0000.html
+         o)  Debian/cats crashes because of unimplemented coproc stuff.
              fix this?
  Test machines:
-         + dev_fb block fill and copy
+         o)  dev_fb block fill and copy
-         + dev_fb draw characters (from the built-in font)?
+         o)  dev_fb draw characters (from the built-in font)?
-         + dev_fb input device? mouse pointer coordinates and buttons
+         o)  dev_fb input device? mouse pointer coordinates and buttons
                  (allow changes in these to cause interrupts as well?)
-         + Redefine the halt() function so that it stops "sometimes
+         o)  Redefine the halt() function so that it stops "sometimes
-           soon", i.e. usage in demo code should be:
+             soon", i.e. usage in demo code should be:
                  for (;;) {
                          halt();
                  }
-Line 267 
 Better CD Image file support:
+Line 328 
 Better CD Image file support:
              possibly other live-CD formats.)
  Networking:
+         x)  Redesign of the networking subsystem, at least the NAT translation
+                 part. The current way of allowing raw ethernet frames to be
+                 transfered to/from the emulator via UDP should probably be
+                 extended to allow the frames to be transmitted other ways as
+                 well.
+         x)  Also adding support for connecting ttys (either to xterms, or to
+                 pipes/sockets etc, or even to PPP->NAT or SLIP->NAT :-).
+         x)  Documentation updates (!) are very important, making it easier to
+                 use the (already existing) network emulation features.
          x)  Fix performance problems caused by only allowing a
              single TCP packet to be unacked.
          x)  Don't hardcode offsets into packets!
-Line 308 
 Documentation:
+Line 378 
 Documentation:
                  securely".
          x)  Try NetBSD/arc 4.x! (It seems to work with disk images!)
          x)  NetBSD/pmax 4 install instructions: xterm instead of vt100!
-         x)  DEVICE_TICK in technical.html
+         x)  BETTER DEVICE EXAMPLES!
+                 o)  Move away from technical.html to somewhere new.
+                 o)  DEVICE_TICK
+                 o)  Implement example devices using interrupts, dyntrans
+                     memory access, etc.?
+         x)  Document the dyntrans core?
          x)  Rewrite the section about experimental devices, after the
              framebuffer acceleration has been implemented, and demos
              written. (Symbolic names instead of numbers; example
-Line 349 
 The Device subsystem:
+Line 424 
 The Device subsystem:
          x)  refactor various clocks/nvram/cmos into one device?
  PCI:
+         x)  Pretty much everything related to runtime configuration, device
+             slots, interrupts, etc must be redesigned/cleaned up. The current
+             code is very hardcoded and ugly.
+         o)  Allow cards to be added/removed during runtime more easily.
+         o)  Allow cards to be enabled/disabled (i/o ports, etc, like
+             NetBSD needs for disk controller detection).
+         o)  Allow devices to be moved in memory during runtime.
+         o)  Interrupts per PCI slot, etc. (A-D).
+         o)  PCI interrupt controller logic... very hard to get right,
+             because these differ a lot from one machine to the next.
          x)  last write was ffffffff ==> fix this, it should be used
              together with a mask to get the correct bits. also, not ALL
              bits are size bits! (lowest 4 vs lowest 2?)
-Line 356 
 PCI:
+Line 441 
 PCI:
          x)  generalize the interrupt routing stuff (lines etc)
  Clocks and timers:
+         x)  Fix the PowerPC DECR interrupt speed! (MacPPC and PReP speed, etc.)
          x)  DON'T HARDCODE 100 HZ IN cpu_mips_coproc.c!
          x)  Test the 8253? Right now it doesn't seem to be used?
-         x)  NetWinder timeofday is incorrect!
+         x)  NetWinder timeofday is incorrect! It seems to be exactly
+day ahead of actual time?
          x)  Cobalt TOD is incorrect!
          x)  Go through all other machines, one by one, and fix them.
- Busses:
-         o)  Redesign the entire "mainbus" concept!
-                 x)  Busses should be placed in a hierarchical tree (?)
-                 x)  Specific clock/bus speeds, cpu speeds etc.
-         o)  Interrupt routing subsystem:
-                 x)  IF POSSIBLE, try to make the new system work with the
-                     current system, but print annoying warning messages. :)
-                     Think carefully about this.
-                 x)  Registry for all available interrupts.
-                         +)  Each interrupt controller (including CPU cores
-                             that can handle interrupts) should register its
-                             interrupts, e.g.
-                                 cpu[0].irq[3]
-                                 cpu[0].irq[3].pcmcia_slot[1]
-                                 cpu[0].irq.pci[3]
-                         +)  Note: MIPS cpus have multiple irqs in the core,
-                             while some other CPUs only have one (irq[0]
-                             or just irq).
-                 x)  Users should use interrupt _names_ instead of integers
-                     when attaching to an interrupt controller, but when
-                     asserting/deasserting irq lines, small integers must
-                     still be used (for obvious performance reasons).
-                     Figure out a way to do this nicely!
-                 x)  Any users need to say whether they need the interrupt line
-                     exclusively or allow shared access.
-                 x)  Must work with everything from native IRQs to
-                     TurboChannel/PCI/ISA/ADB/PCMCIA/...
-                 x)  Must work with SMP emulation!
-                 x)  Make it with device_add(). How does the end user find
-                     out the name of an interrupt controller/line in e.g.
-                     a configuration file?
-         o)  Synchronization over network? or at least in dyntrans within
-             one emulated machine
-         o)  Convert to real busses: TurboChannel, PCMCIA, ADB
  Config file parser:
          o)  Rewrite it from scratch!
          o)  Usage of any expression available through the debugger
+         o)  Allow interrupt controllers to be added! and interrupts
+             to be used in more ways than before
          o)  Support for running debugger commands (like the -c
              command line option)
-Line 410 
 Floating point layer:
+Line 464 
 Floating point layer:
          o)  non-IEEE modes (i.e. x86)?
  Userland emulation:
-         x)  Lots of stuff; freebsd and netbsd (and linux?) syscalls.
+         x)  Dynamic linking!
-         x)  Dynamic linking? Hm.
+         x)  Lots of stuff; freebsd, netbsd, linux, ... syscalls.
+         x)  Initial register/stack contents (environment, command line args).
+         x)  Return value (from main).
+         x)  mmap emulation layer
+         x)  errno emulation layer
+         x)  struct conversions for may syscalls
  Sound:
          x)  generic sound framework
          x)  add one or more sound cards as devices; add a testmachine
              sound card first?
+         x)  Dreamcast sound? Generic PCI sound cards?
  ASC SCSI controller:
          x)  NetBSD/arc 2.0 uses the ASC controller in a way which GXemul
-Line 442 
 Caches / memory hierarchies: (this is mo
+Line 502 
 Caches / memory hierarchies: (this is mo
              possible.
  File/disk/symbol handling:
+         o)  Make sure that disks can be added/removed during runtime!
+             (Perhaps this needs a reasonably large re-write.)
          o)  Remove some of the complexity in file format guessing, for
                  Ultrix kernels that are actually disk images?
          o)  Better handling of tape files
          o)  Read function argument count and types from binaries? (ELF?)
          o)  Better demangling of C++ names. Note: GNU's C++ differs from e.g.
              Microsoft's C++, so multiple schemes must be possible. See
-Line 453 
 File/disk/symbol handling:
+Line 515 
 File/disk/symbol handling:
  Userland ABI emulation:
          o)  see src/useremul.c
- Terminal/console:
-         o)  allow emulated serial ports to be connected to the outside
-             world in a more generic way, or even to other emulated
-             machines(?)
- Save state of the whole emulated machine, to be able to load it back
-         in later?  (Memory, all device's states, all registers and
-         so on.  Like taking a snapshot. (SimOS seems to do this,
-         according to its website.))
  Better framebuffer and X-windows functionality:
          o)  Generalize the update_x1y1x2y2 stuff to an extend-region()
              function...

 Legend:



Removed from v.32
 


changed lines


 
Added in v.40
 Legend:



Removed from v.32
 


changed lines


 
Added in v.40
-Removed from v.32
+Added in v.40

	ViewVC Help
Powered by ViewVC 1.1.26