Difference between revisions of "Project Status"

From ES40 Emulator
Jump to: navigation, search
(Snapshot 20080503_1030)
Line 24: Line 24:
 
|-
 
|-
 
|style="color:#000;"|  
 
|style="color:#000;"|  
 +
* 16-MAR-2009: David Hittner has fixed a problem in the [[CPU]]'s handling of super-page bits.
 +
* 16-MAR-2009: [[User:Camiel|Camiel Vanderhoeven]] and Volker Halle have fixeded a problem in the [[CPU]] that caused decnet to crash on booting.
 
* 29-APR-2008: [[User:Bdwheele|Brian Wheeler]] has implemented a mostly-working [[floppy]] controller.
 
* 29-APR-2008: [[User:Bdwheele|Brian Wheeler]] has implemented a mostly-working [[floppy]] controller.
 
* 29-APR-2008: [[User:Camiel|Camiel Vanderhoeven]] has made non-[[PCI Device|PCI]] [[Disk Controller]]s possible.  
 
* 29-APR-2008: [[User:Camiel|Camiel Vanderhoeven]] has made non-[[PCI Device|PCI]] [[Disk Controller]]s possible.  
* 29-APR-2008: [[User:Bdwheele|Brian Wheeler]] has added checking for memory range overlapping.
 
* 18-APR-2008: [[User:Bdwheele|Brian Wheeler]] has re-written the [[DMA]] code to be the basis for a more functional DMA controller that will enable [[Floppy]] support.
 
 
|-
 
|-
 
! <h2 style="margin:0; background:#cef2e0; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Working on...</h2>
 
! <h2 style="margin:0; background:#cef2e0; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Working on...</h2>

Revision as of 04:06, 17 March 2009

Working Towards: Version 0.19 release

The most noticeable change in version 0.19 will be increased use of threading. In version 0.19, almost every device will run it's own execution thread, which will allow the emulator to make better use of multiple processor cores (if available), and will open up the way to emulating an ES40 with multiple CPU's.

The latest development snapshot available is Snapshot 20080503_1030.

ES40 Emulator Project Status
Current: Version 0.18

Recent changes

Working on...

Problem areas

We know of shortcomings in the following areas:
  • Timing problems introduced with the new threading model (needs research)
  • Multiple CPU's exhibit strange behaviour or refuse to become members of the active set (would love to have better SRM specs)
  • Ethernet has problems with non-trivial amounts of data (FTP, for instance) (needs research)
  • TCP/IP does not work with DHCP (needs research)
  • Problems in floating-point emulation (would love to have a CPU test suite)
  • Unexpected access and alignment faults (needs research)

Wannahaves

These are some of the things we'd love to do in the future:
  • Dynamic Translation rather than Interpretation of CPU Instructions (this is complex and host-platform-dependent, but will provide a significant performance increase)