Use MEMRQ = 6 to signify interrupt handled write #67
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
MEMRQ = 5 just takes Address and Value from MEMADDR and LADD, before performing the write itself.
If the user wanted to cancel a write request or perform another operation on write instead, they would still end up having the operation perform, and a byte written to the trapped page by default(the write is non-negotiable, it HAS to go somewhere, and preventing a value changing from write requires hacky workarounds).
MEMRQ = 6, which is new, will outright cancel a write request instead of just changing the address and value, allowing you to prevent any write happening at all without having to do a workaround.