/[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 22 by dpavlin,
Mon Oct  8 16:19:37 2007 UTC
+revision 40 by dpavlin,
Mon Oct  8 16:22:11 2007 UTC
 Line 1
- $Id: TODO,v 1.209 2006/02/18 21:03:09 debug Exp $
+ $Id: TODO,v 1.489 2007/05/01 04:05:06 debug Exp $
- Hm. This file is in random order, and not all parts of it are up-to-date.
+ --------------------------------------------
- Algor:  PCI and ISA and LOCAL interrupts! --> wdc could start working
+ Testing for the next release (0.4.5.1):
-         Add interrupt controller in dev_algor.c.
+ 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:
-         TOP Priority:
+         x)  Instruction combination collisions? How to avoid easily...
-                 x)  64-bit stuff: good generic virtual memory translation, and
+         x)  Think about how to do both SHmedia and SHcompact in a reasonable
-                     other structures. not all 64 bits need to be used
+             way! (Or AMD64 long/protected/real, for that matter.)
-                     (e.g. Alpha)
+         x)  68K emulation; think about how to do variable instruction
-                 x)  Delay slots!
+             lengths across page boundaries.
-                 x)  Old MIPS -> dyntrans!
+         x)  Dyntrans with valgrind-inspired memory checker. (In memory_rw,
-         Other stuff:
+             it would be reasonably simple to add; in each individual fast
+             load/store routine = a lot more work, and it would become
+             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,
+                 so that it caches a translation (that is, an instruction
+                 word and the instr_call it was translated to the last
+                 time), so that it doesn't need to do slow
+                 to_be_translated for each end of page?
+         x)  Program Counter statistics:
+                 Per machine? What about SMP? All data to the same file?
+                 A debugger command should be possible to use to enable/
+                 disable statistics gathering.
+                 Configuration file option!
+         x)  Breakpoints:
+                 o) Physical vs virtual addresses!
+                 o) 32-bit vs 64-bit sign extension for MIPS, and others?
          x)  INVALIDATION should cause translations in _all_ cpus to be
              invalidated, e.g. on a write to a write-protected page
              (containing code)
-         x)  Think about sharing code between CPUs of the same
+         x)  16-bit encodings? (MIPS16, ARM Thumb, 32-bit SH on SH64)
-             arch/bitlength/endianness (the translation caches).
-             (Eg. a little-endian R4000 and a little-endian R5000 could
-             share code, but not an R3000 and an R4000.)
-         x)  better (meaningful) instr call statistics
-         x)  Call/return hints?
-         x)  16-bit encodings? (MIPS16, ARM Thumb, SH3, ...)
-         x)  PPC optimizations; instr combs
-         x)  Alpha
-         x)  SPARC
-         x)  PPC (64-bit stuff)
          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)  simple syntax for emitting opcodes; backend implementation
+                     must be optional, so I don't have to write more code
+                     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
+             has been written to.
+         o)  What should happen when programs are loaded?  Text/data, bss (zero
+             filled). But stack space and heap is uninitialized.
+         o)  Uninitialized local variables:
+                 A load from a place on the stack which has not previously
+                 been stored to => warning. Increasing the stack pointer using
+                 any available means should reset the memory to uninitialized.
+         o)  If calls to malloc() and free() can be intercepted:
+                 o)  Access to a memory area after free() => warning.
+                 o)  Memory returned by malloc() is marked as not-initialized.
+                 o)  Non-passive, but good to have: Change the argument
+                     given to malloc, to return a slightly larger memory
+                     area, i.e.  margin_before + size + margin_after,
+                     and return the pointer  + margin_before.
+                     Any access to the margin_before or _after space results
+                     in warnings. (free() must be modified to free the
+                     actually allocated address.)
+ MIPS:
+         o)  Nicer MIPS status bits in register dumps.
+         o)  Alignment exceptions.
+         o)  Floating point exception correctness.
+         o)  Fix this? Triggered by NetBSD/sgimips? Hm:
+                 to_be_translated(): TODO: unimplemented instruction:
+                 000000000065102c: 00200800 (d)  rot_00  at,zr,0
+         o)  Some more work on opcodes.
+                 x) MIPS64 revision 2.
+                         o)  Find out which actual CPUs implement the rev2 ISA!
+                         o)  DROTR32 and similar MIPS64 rev 2 instructions,
+                             which have a rotation bit which differs from
+                             previous ISAs.
+                         o)  EI and DI instructions for MIPS64/32 rev 2.
+                             NOTE: These are _NOT_ the same as for R5900!
+                 x) _MAYBE_ TX79 and R5900 actually differ in their
+                    opcodes? Check this carefully!
+         o)  Dyntrans: Count register updates are probably not 100% correct yet.
+         o)  Refactor code for performance and readability/maintainability.
+         o)  (Re)implement 128-bit loads/stores for R5900.
+         o)  R4000 and others:
+                 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)  SH4 performance is VERY low when running user-space instructions,
+             because I actually simulate the 4-entry ITLB as being separate
+             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)  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)  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 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)  G2 DMA
+         x)  LAN adapter (dev_mb8696x.c).  NetBSD root-on-nfs.
+         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)  Software emulation of BIOS calls:
+                 x)  GD-ROM emulation: Use the GDROM device.
+                 x)  Use the VGA font as a fake ROM font. (Better than
+                     nothing.)
+         x)  Make as many as possible of the KOS examples run!
+         x)  More homebrew demos/games.
+         x)  SPU: Sound emulation (ARM cpu).
+         x)  VME processor emulation? "(Sanyo LC8670 "Potato")" according to
+             Wikipedia, LC86K87 according to Comstedt's page. See
+             http://www.maushammer.com/vmu.html for a good description of
+             the differences between LC86104C and the one used in the VME.
+ Alpha:
+         x)  OSF1 PALcode, Virtual memory support.
+         x)  PALcode replacement! PAL1E etc opcodes...?
+         x)  Interrupt/exception/trap handling.
+         x)  Floating point exception correctness.
+         x)  More work on bootup memory and register contents.
+         x)  More Alpha machine types, so it could work with
+             OpenBSD, FreeBSD, and Linux too?
+ SPARC (both the ISA and the machines):
+         o)  Implement Adress space identifiers; load/stores 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)  Disassemly of some more instructions?
+         o)  Are sll etc 32-bit sign-extending or zero-extending?
+         o)  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"?
+                 What if the guest OS (running on an emulated SMP machine)
+                 has a usertask running, with userland threads?
+         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
+                         +)  Alpha/MIPS/SPARC zero registers
+                         +)  x86 64/32/16-bit registers
+                 x)  Value formatter for resulting output.
+         o)  see src/debugger.c for more
+ POWER/PowerPC:
+         x)  Fix DECR timer speed, so it matches the host.
+         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,..)>
+                 <0x26c550(&ata_xfer_pool,2,0,8,..)>
+                 <0x35c71c(0x3f27000,0,52,8,..)>
+               <ata_exec_xfer(0xd005e4c8,0x3f27000,0,13,..)>
+                 <atastart(0xd005e4c8,0x3f27000,0,13,..)>
+                   <__wdccommand_start(0xd005e4c8,0x3f27000,0,13,..)>
+                     <bsw1(&prep_isa_io_space_tag,0x800001f6,0,176,..)>
+                 [ wdc: write to SDH: 0xb0 (sectorsize 2, lba=1, drive 1, head 0) ]
+                     <wdcwait(0xd005e4c8,72,64,0xbb8,..)>
+                       <0x198120(0xd005e4c8,72,64,0xbb8,..)>
+                         <bsr1(&prep_isa_io_space_tag,0,0,0xbb8,..)>
+                         <delay(100,0,0,0xbb8,..)>
+             Note: <bsr1(&prep_isa_io_space_tag,0,0,0xbb8,..)>
+         x)  PPC optimizations; instr combs
+         x)  64-bit stuff: either Linux on G5, or perhaps some hobbyist
+                 version of AIX? (if there exists such a thing)
+         x)  macppc: adb controller; keyboard (for framebuffer mode)
+         x)  make OpenBSD/macppc work (PCI controller stuff)
+         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.
+ 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 or 4.x running (iq80321)
+         o)  make the xscale counter registers (ccnt) work
+         o)  make the ata controller usable for FreeBSD!
+         o)  Zaurus emulation:
+                 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:
+         o)  dev_fb block fill and copy
+         o)  dev_fb draw characters (from the built-in font)?
+         o)  dev_fb input device? mouse pointer coordinates and buttons
+                 (allow changes in these to cause interrupts as well?)
+         o)  Redefine the halt() function so that it stops "sometimes
+             soon", i.e. usage in demo code should be:
+                 for (;;) {
+                         halt();
+                 }
+ Better CD Image file support:
+         x)  Support CD formats that contain more than 1 track, e.g.
+             CDI files (?). These can then contain a mixture of e.g. sound
+             and data tracks, and booting from an ISO filesystem path
+             would boot from [by default] the first data track.
+             (This would make sense for e.g. Dreamcast CD images, or
+             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!
+         x)  Test with lower than 100 max tcp/udp connections,
+             to make sure that reuse works!
+         x)  Make OpenBSD work better as a guest OS!
+         x)  DHCP? Debian doesn't actually send DHCP packets, even
+                 though it claims to? So it is hard to test.
+         x)  Multiple networks per emulation, and let different
+             NICs in machines connect to different networks.
+         x)  Support VDE (vde.sf.net)? Easiest/cleanest (before a
+             redesign of the network framework has been done) is
+             probably to connect it using the current (udp) solution.
+         x)  Allow SLIP connections, possibly PPP, in addition to
+             ethernet?
+ Cache simulation:
+         o)  Command line flags for:
+                 o)  CPU endianness?
+                 o)  Cache sizes? (multiple levels)
+         o)  Separate from the CPU concept, so that multi-core CPUs sharing
+             e.g. a L2 cache can be simulated (?)
+         o)  Instruction cache emulation is easiest (if separate from the
+             data cache); similar hack as the S;I; hack in cpu_dyntrans.c.
+             NOTE: if the architecture has a delay slot, then an instruction
+             slot can actually be executed as 2 instructions.
+         o)  Data cache emulation = harder; each arch's load/store routines
+             must include support? running one instruction at a time and
+             having a cpu-dependant lookup function for each instruction
+             is another option (easier to implement, but very very slow).
+ Documentation:
+         x)  Note about sandboxing/security:
+                 Not all emulated instructions fail in the way they would
+                 do on real hardware (e.g. a userspace program writing to
+                 a system register might work in GXemul, but it would
+                 fail on real hardware).  Sandbox = contain from the
+                 host OS. But the emulated programs will run "less
+                 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)  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
+             use cases, etc. Mention demo files that use the various
+             features?)
+         x)  "a very simple linear framebuffer device (for graphics output)"
+             under "which machines does gxemul emulate" ==> better
+             description?
+         x)  Better description on how to set up a cross compiler?
+             Example for MIPS64.
+         o)  Automagic documentation generation?
+                 x)  machines, cpus, devices.
+                 x)  REMEMBER that several machines/devices can be in
+                         the same source file!
+         o)  Try to rewrite the install instructions for those machines
+             that use 3MAX into using CATS or hpcmips? (To remove the need
+             to use a raw ffs partition, using up all of the disk image.)
  More generic out_of_memory error reporting, and check everywhere!
          Causes: OpenBSD has low default limits for normal users.
-Line 39 
 More generic out_of_memory error reporti
+Line 410 
 More generic out_of_memory error reporti
                  Unix systems usually allow processes to allocate virtual
                  memory beyond the amount of RAM in the machine.)
- Breakpoints: 32-bit vs 64-bit sign extension for MIPS, warnings, etc.
-         Use the debugger's symbolic name stuff. (which will have to be
-         extended soon to support stuff like  "2*x + symbol + y" etc. cool
-         stuff)
- Sprite (guest OS for DECstation emulation)
-         x)  Timing problems during bootup?
  The Device subsystem:
          x)  allow devices to be moved and/or changed in size (down to a
-             minimum size, etc, or up to a max size)
+             minimum size, etc, or up to a max size); if there is a collision,
+             return false. It is up to the caller to handle this situation!
+         x)  NOTE: Translations must be invalidated, both for
+             registering new devices, and for moving existing ones.
+             cpu->invalidate translation caches, for all CPUs that
+             are connected to a specific memory.
          x)  keep track of interrupts and busses? actually, allowing any device
-             to be a bus might be a nice idea
+             to be a bus might be a nice idea.
+         x)  turn interrupt controllers into devices? :-)
          x)  refactor various clocks/nvram/cmos into one device?
- ARM:
-         o)  add ID for "i80321 600MHz rev 2 (XScale core)"
-         o)  make the ata controller usable for FreeBSD!
-         x)  zaurus for openbsd...
  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?)
          x)  add support for address fixups
-         x)  generalize the interrupt routing stuff (lines etc). this should
+         x)  generalize the interrupt routing stuff (lines etc)
-             be per machine? or per bus, that's better
- MacPPC:
-         x)  dev_zs / interrupts?
-         x)  adb controller; keyboard
-         x)  make OpenBSD/macppc work (PCI controller stuff)
- Network layer:
+ Clocks and timers:
-         o)  DHCP (for Debian and BSD installers :-)
+         x)  Fix the PowerPC DECR interrupt speed! (MacPPC and PReP speed, etc.)
-         o)  increase performance
+         x)  DON'T HARDCODE 100 HZ IN cpu_mips_coproc.c!
-         o)  don't rely on NetBSD-ish usage
+         x)  Test the 8253? Right now it doesn't seem to be used?
-         o)  Multiple networks per emulation, and let different
+         x)  NetWinder timeofday is incorrect! It seems to be exactly
-             NICs in machines connect to different networks.
+day ahead of actual time?
-         o)  many other issues: see src/net.c
+         x)  Cobalt TOD is incorrect!
+         x)  Go through all other machines, one by one, and fix them.
- Busses:
-         o)  Redesign the entire "mainbus" concept!
-         o)  Busses should be placed in a hierarchical tree!
-         o)  Easily configurable interrupt routing in SMP systems.
-         o)  Specific clock/bus speeds, cpu speeds etc.
-         o)  Synchronization over network? or at least in dyntrans within
-             one emulated machine
-         o)  dev->bus: TurboChannel, PCMCIA, ADB?
  Config file parser:
-         o)  Refresh/rewrite it :)
+         o)  Rewrite it from scratch!
          o)  Usage of any expression available through the debugger
-         o)  Expressions such as "add device" would be nice to be able
+         o)  Allow interrupt controllers to be added! and interrupts
-             to do on the command line manually.
+             to be used in more ways than before
-         o)  Allow machine() entries even if there is no emul() entry (but
-             then don't allow any emul() entries at all).
          o)  Support for running debugger commands (like the -c
              command line option)
  Floating point layer:
          o)  make it common enough to be used by _all_ emulation modes
+         o)  implement correct error/exception handling and rounding modes
+         o)  implement more helper functions (i.e. add, sub, mul...)
          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
+         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
+             cannot yet handle. (NetBSD 1.6.2 works ok.) (Possibly a problem
+             in NetBSD itself, http://mail-index.netbsd.org/source-changes/
+/11/06/0024.html suggests that.)
+             NetBSD 4.x seems to work? :)
  Caches / memory hierarchies: (this is mostly MIPS-specific)
-         o)  MIPS coproc.c: bits in config registers should reflect
-             correct cache sizes for _all_ CPU types. (currently only
-             implemented for R4000, R1x000, and a few others)
          o)  src/memory*.c: Implement correct cache emulation for
              all CPU types. (currently only R2000/R3000 is implemented)
-             (per CPU, multiple levels should be possible,
+             (per CPU, multiple levels should be possible, associativity etc!)
-             associativity etc!)
          o)  R2000/R3000 isn't _100%_ correct, just almost correct :)
          o)  Move the -S (fill mem with random) functionality into the
              memory.c subsystem, not machine.c or wherever it is now
-Line 128 
 Caches / memory hierarchies: (this is mo
+Line 501 
 Caches / memory hierarchies: (this is mo
              memory latencies should be emulated as correctly as
              possible.
- MIPS CPU emulation:  (note: this is for the OLD mips stuff)
-         o)  i386 bintrans backend: movn etc, slt[u] for
--bit mode, 64-bit shifts etc
-         o)  Instructions:
-                 o)  All ISAs:
-                         o)  Floating point exception handling, and
-                                 add more instructions.
-                         o)  Finish the MIPS16 translator, and test it!
-                         o)  MIPS ISA I, II, III, IV
-                         o)  MIPS V (SIMD vector stuff?)
-                         o)  MDMX  (MIPS Digital Media Extension)
-                         o)  MIPS 3D
-                         o)  MIPS MT (Multi-thread stuff) (What's this?)
-                 o)  Warn about mis-used bit fields (ie bits that
-                     should be all zeroes, warn about if they are not)!
-                     Both for coprocessor registers and for instruction
-                     opcodes.
-                 o)  the special2 stuff is a mess right now
-                 o)  warn and/or cause exceptions for unimplemented
-                     instructions (depending on CPU type)
-         o)  R2000/R3000:
-                 x)  R3000 "tri-byte stores". (What's this?)
-         o)  R4000 and others:
-                 x)  watchhi/watchlo exceptions, and other exception
-                     handling details
-         o)  R10000 and others:  (R12000, R14000 ?)
-                 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)
-         o)  Implement load delays?  Warnings on interlocks.
-         o)  Implement all coprocessor 0 bits / functions.
-                 x)  coproc 0 selectors! (R4000 ?)
-         o)  R4300 (nintendo64, no mmu?), R5900 (playstation2, weird
-                 TLB/cache? 128-bit GPRs, new instructions),
-K (note: NOT R4000), 5K (note: NOT R5000),
-                 R6000 (ISA II), R8000
-         o)  Multi-cpu stuff:
-                 +)  Interrupt routing (ie devices vs mainbus, or
-                     connect each device to a fixed cpu)
-                 +)  SGI's NUMA architecture. Study
-                         x)  Linux sources
-                         x)  SGI's specs on NUMA address space
-                 +)  Ultrix?  NetBSD doesn't do SMP on MIPS yet :-(
-                 +)  Own experiments with ycx2.
  File/disk/symbol handling:
-         o)  Better handling of tape files
+         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)  Demangle C++ names.
+         o)  Better demangling of C++ names. Note: GNU's C++ differs from e.g.
+             Microsoft's C++, so multiple schemes must be possible. See
- Debugger:
+             URL at top of src/symbol_demangle.c for more info.
-         o)  see src/debugger.c for more
  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...
          o)  -Yx sometimes causes crashes.
          o)  Simple device access to framebuffer_blockcopyfill() etc,
              and text output (using the built-in fonts), for dev_fb.
-Line 205 
 Better framebuffer and X-windows functio
+Line 528 
 Better framebuffer and X-windows functio
          o)  Non-resizable windows?  Or choose scaledown depending
                  on size (and center the image, with a black border).
          o)  Different scaledown on different windows?
+         o)  Non-integral scale-up? (E.g. 640x480 -> 1024x768)
          o)  Switch scaledown during runtime? (Ala CTRL-ALT-plus/minus)
+         o)  Bug reported by Elijah Rutschman on MacOS with weird
+             keys (F5 = cursor down?).
          o)  Keyboard and mouse events:
                  x)  Do this for more machines than just DECstation
                  x)  more X11 cursor keycodes
-Line 216 
 Better framebuffer and X-windows functio
+Line 542 
 Better framebuffer and X-windows functio
          o)  Generalize the framebuffer stuff by moving _ALL_ X11
                  specific code to src/x11.c!
- Statistics:  (this could be interesting)
-         o)  Save to file and show graphics. It should be possible to
-             run gxemul after a simulation to just show the graphics,
-             or convert to a .ppm or .tga or similar.
-         o)  memory accesses (to measure cache efficiency and
-                 page coloring efficiency)
-         o)  nr of simultaneous ASIDs in use in the TLB, for MIPS
-         o)  percentage of time spent in different "states", such as
-             running userland code, kernel code, or idling (for CPUs
-             that have such an instruction, or whenever the PC is
-             inside a specific idle-function (address range)).
-             Possible additional state (for example on R3000): caches
-             disabled.
-         o)  position of read/write on (SCSI) disks

 Legend:



Removed from v.22
 


changed lines


 
Added in v.40
 Legend:



Removed from v.22
 


changed lines


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

	ViewVC Help
Powered by ViewVC 1.1.26