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.
| philpem@0 | 1 | From private email, dated 2010-Nov-26, 20:43 GMT: |
| philpem@0 | 2 | |
| philpem@0 | 3 | From: Karl Stenerud <kstenerud@gmail.com> |
| philpem@0 | 4 | Subject: Re: Musashi 68k emulator |
| philpem@0 | 5 | |
| philpem@0 | 6 | On 2010-11-26, at 12:36 PM, Philip Pemberton wrote: |
| philpem@0 | 7 | |
| philpem@0 | 8 | > > I do have one question, though more related to licensing than the core itself... |
| philpem@0 | 9 | > > |
| philpem@0 | 10 | > > I was planning to release my emulator under an open-source licence, probably the GPL or something along those lines (the worst case scenario IMO would be someone adding a ton of nice features then refusing to release the source). |
| philpem@0 | 11 | > > |
| philpem@0 | 12 | > > The "non-commercial use only" restriction in the Musashi license would seem to be at odds with the GPL, and would make it somewhat more difficult to tie in GPL-licensed libraries. Is there any possibility of getting v3.31 released under a less restrictive license, maybe GPL or LGPL? |
| philpem@0 | 13 | > > |
| philpem@0 | 14 | |
| philpem@0 | 15 | Sure, no problem. I usually release stuff under an Apache license nowadays, but feel free to pick any FOSS license. |
| philpem@0 | 16 |