Move IO ports-mapped registers handling to their respective modules #69
Comments
mzal
pushed a commit
that referenced
this issue
Sep 15, 2020
Add a mechanism for registration of memory read/write handlers for particulat addresses within IO ports range and for IE register. Refactor joypad, gpu and ints modules to use the new mechanism and use internal memory for their own logic instead of calling mem APIs.
mzal
pushed a commit
that referenced
this issue
Sep 18, 2020
Add a mechanism for registration of memory read/write handlers for particulat addresses within IO ports range and for IE register. Refactor joypad, gpu and ints modules to use the new mechanism and use internal memory for their own logic instead of calling mem APIs.
mzal
pushed a commit
that referenced
this issue
Sep 18, 2020
Add a mechanism for registration of memory read/write handlers for particulat addresses within IO ports range and for IE register. Refactor joypad, gpu and ints modules to use the new mechanism and use internal memory for their own logic instead of calling mem APIs.
mzal
pushed a commit
that referenced
this issue
Sep 18, 2020
Add a mechanism for registration of memory read/write handlers for particular addresses within IO ports range and for IE register. Refactor joypad, gpu and ints modules to use the new mechanism and use internal memory for their own logic instead of calling mem APIs.
mzal
pushed a commit
that referenced
this issue
Sep 19, 2020
Add a mechanism for registration of memory read/write handlers for particular addresses within IO ports range and for IE register. Refactor joypad, gpu and ints modules to use the new mechanism and use internal memory for their own logic instead of calling mem APIs.
mzal
pushed a commit
that referenced
this issue
Sep 21, 2020
Add a mechanism for registration of memory read/write handlers for particular addresses within IO ports range and for IE register. Refactor joypad, gpu and ints modules to use the new mechanism and use internal memory for their own logic instead of calling mem APIs. Dynamically calculate joypad register value on read. Change bgp -> obp in sprite-related gpu functions.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After further consideration, I think it is cleaner to let the particular modules handle IO ports registers related to them.
Previously, I thought about creating whole memory blocks to be handled by outside modules, but after further examination it appears that in many cases the IO ports addresses are not consecutive and assigning a handler function on per-address basis seems to make more sense.
The text was updated successfully, but these errors were encountered: