Fri, 12 Apr 2013 12:34:32 +0100
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.
1 #define VER_COMPILE_DATETIME "@@datetime@@"
2 #define VER_COMPILE_DATE "@@date@@"
3 #define VER_COMPILE_TIME "@@time@@"
4 #define VER_COMPILE_BY "@@whoami@@"
5 #define VER_COMPILE_HOST "@@hostname@@"
6 #define VER_COMPILER "@@compiler@@"
7 #define VER_BUILD_TYPE "@@buildtype@@"
8 #define VER_CFLAGS "@@cflags@@"
10 #define VER_MAJOR @@majorver@@
11 #define VER_MINOR @@minorver@@
12 #define VER_BUILDNUM @@buildnum@@
13 #define VER_EXTRA "@@extraver@@"
14 #define VER_VCSREV "@@vcsstr@@"
16 #define VER_FULLSTR "@@fullverstr@@"