TMF Hg

Make the page table volatile (it may change behind gcc's back) experimental_memory_mapper_v2

  • Fri, 12 Apr 2013 12:37:13 +0100
  • by Philip Pemberton <philpem@philpem.me.uk> [Fri, 12 Apr 2013 12:37:13 +0100] rev 142
  • Make the page table volatile (it may change behind gcc's back)

Make mapper debug logic more verbose (but disable by default) experimental_memory_mapper_v2

  • Fri, 12 Apr 2013 12:36:28 +0100
  • by Philip Pemberton <philpem@philpem.me.uk> [Fri, 12 Apr 2013 12:36:28 +0100] rev 141
  • Make mapper debug logic more verbose (but disable by default)

Fix read-after-write logic experimental_memory_mapper_v2

  • Fri, 12 Apr 2013 12:34:32 +0100
  • by Philip Pemberton <philpem@philpem.me.uk> [Fri, 12 Apr 2013 12:34:32 +0100] rev 140
  • Fix read-after-write logic

    In some cases (notably reading from a page after having written to it), the
    mapper may change the pagestate from "accessed and written" ("dirty"; PS0,PS1)
    to "accessed but not written" (clean; PS1,!PS0). This should never, ever, EVER
    happen. Once a page is dirty, it remains so until the 68k clears the DIRTY
    bit.

    Once again, this wonderful bit of logic was missing from the TRM.

Fix potential unassigned variable

  • Thu, 11 Apr 2013 09:37:25 +0100
  • by Philip Pemberton <philpem@philpem.me.uk> [Thu, 11 Apr 2013 09:37:25 +0100] rev 139
  • Fix potential unassigned variable

Check return value of fread()

  • Thu, 11 Apr 2013 09:37:11 +0100
  • by Philip Pemberton <philpem@philpem.me.uk> [Thu, 11 Apr 2013 09:37:11 +0100] rev 138
  • Check return value of fread()

Enable code optimisation to improve quality of GCC warnings

  • Thu, 11 Apr 2013 09:36:53 +0100
  • by Philip Pemberton <philpem@philpem.me.uk> [Thu, 11 Apr 2013 09:36:53 +0100] rev 137
  • Enable code optimisation to improve quality of GCC warnings

Code cleanup

  • Thu, 11 Apr 2013 09:18:31 +0100
  • by Philip Pemberton <philpem@philpem.me.uk> [Thu, 11 Apr 2013 09:18:31 +0100] rev 136
  • Code cleanup

    * Fix some compiler warnings --
    * string format
    * shift greater than type size,
    * unused variable.

merge changes from default experimental_memory_mapper_v2

  • Wed, 13 Mar 2013 01:10:34 +0000
  • by Philip Pemberton <philpem@philpem.me.uk> [Wed, 13 Mar 2013 01:10:34 +0000] rev 135
  • merge changes from default

[wd2010,main] WD2010 disc geometry fixes

  • Wed, 13 Mar 2013 00:43:25 +0000
  • by Philip Pemberton <philpem@philpem.me.uk> [Wed, 13 Mar 2013 00:43:25 +0000] rev 134
  • [wd2010,main] WD2010 disc geometry fixes

    I believe I have fixed the geometry problem with FreeBee. The geometry was set
    to 17 sectors per track instead of 16, which obviously throws off addressing.
    I changed it to use 16 sectors per track. However, s4diag tries to format
    sector 17, so I changed the WD2010 emulation to accept any address when
    formatting (since the format command doesn't actually do anything, it doesn't
    matter). It is now possible to format the hard disk, initialize the file
    system, and mount it. However, cpio still fails to copy the system to the hard
    disk.

    Author: Andrew Warkentin <andreww591 gmail com>

use MAP_ADDR_TO_PAGE for memory mapping experimental_memory_mapper_v2

  • Wed, 13 Mar 2013 00:40:42 +0000
  • by Philip Pemberton <philpem@philpem.me.uk> [Wed, 13 Mar 2013 00:40:42 +0000] rev 133
  • use MAP_ADDR_TO_PAGE for memory mapping

merge in changes from default branch experimental_memory_mapper_v2

  • Fri, 18 Jan 2013 22:52:43 +0000
  • by Philip Pemberton <philpem@philpem.me.uk> [Fri, 18 Jan 2013 22:52:43 +0000] rev 132
  • merge in changes from default branch

add TODO

  • Fri, 18 Jan 2013 18:51:50 +0000
  • by Philip Pemberton <philpem@philpem.me.uk> [Fri, 18 Jan 2013 18:51:50 +0000] rev 131
  • add TODO

[wd2010] disable DMA pagefault workaround (no longer required)

  • Fri, 18 Jan 2013 17:20:07 +0000
  • by Philip Pemberton <philpem@philpem.me.uk> [Fri, 18 Jan 2013 17:20:07 +0000] rev 130
  • [wd2010] disable DMA pagefault workaround (no longer required)

[memory] Emulate main memory read wrap-around

  • Fri, 18 Jan 2013 17:18:50 +0000
  • by Philip Pemberton <philpem@philpem.me.uk> [Fri, 18 Jan 2013 17:18:50 +0000] rev 129
  • [memory] Emulate main memory read wrap-around

    3B1s with 512K or 1MB of base memory have a decoding quirk which causes reads
    to 'wrap around'. That is to say, on a 512K machine, reading from addresses 0,
    512K, 1024K or 1536K will address the same RAM byte. On a 1MB machine,
    addresses 0 and 1024K address the same RAM byte.

    Emulating this incorrectly causes P4TEST to report an incorrect amount of
    available base RAM.

experimental memory mapper, not quite working experimental_memory_mapper_v2

  • Fri, 18 Jan 2013 17:03:48 +0000
  • by Philip Pemberton <philpem@philpem.me.uk> [Fri, 18 Jan 2013 17:03:48 +0000] rev 128
  • experimental memory mapper, not quite working

fix default HDD sectors-per-track

  • Wed, 16 Jan 2013 00:41:51 +0000
  • by Philip Pemberton <philpem@philpem.me.uk> [Wed, 16 Jan 2013 00:41:51 +0000] rev 127
  • fix default HDD sectors-per-track

    The 64MB Micropolis drive we're trying to emulate in FreeBee has 17 sectors
    per track. Fix this in main.c to avoid tripping the sector range checks.

[wd2010] allow seek delay to be overridden at compile time

  • Wed, 16 Jan 2013 00:40:18 +0000
  • by Philip Pemberton <philpem@philpem.me.uk> [Wed, 16 Jan 2013 00:40:18 +0000] rev 126
  • [wd2010] allow seek delay to be overridden at compile time

[wd2010] properly constrain R/W ops based on end sector

  • Wed, 16 Jan 2013 00:38:13 +0000
  • by Philip Pemberton <philpem@philpem.me.uk> [Wed, 16 Jan 2013 00:38:13 +0000] rev 125
  • [wd2010] properly constrain R/W ops based on end sector

[wd2010] display 'number of sectors' for sector R/W ops, display WrLBA in bytes not sectors

  • Wed, 16 Jan 2013 00:36:51 +0000
  • by Philip Pemberton <philpem@philpem.me.uk> [Wed, 16 Jan 2013 00:36:51 +0000] rev 124
  • [wd2010] display 'number of sectors' for sector R/W ops, display WrLBA in bytes not sectors

[wd2010] fix confusing expressions used for multisector mode

  • Wed, 16 Jan 2013 00:35:10 +0000
  • by Philip Pemberton <philpem@philpem.me.uk> [Wed, 16 Jan 2013 00:35:10 +0000] rev 123
  • [wd2010] fix confusing expressions used for multisector mode