diff options
author | Wojtek Kosior <kwojtus@protonmail.com> | 2020-01-15 17:04:14 +0100 |
---|---|---|
committer | Wojtek Kosior <kwojtus@protonmail.com> | 2020-01-15 17:04:14 +0100 |
commit | ebc85a24c9c04232e775f5bc7cf4ea9af8e1caa7 (patch) | |
tree | 2f7ecc71fb906efb1bf08ae6f268b7a0508b94fa | |
parent | ca3bf744f826225bb041afc4779ee19493d5440e (diff) | |
download | rpi-MMU-example-ebc85a24c9c04232e775f5bc7cf4ea9af8e1caa7.tar.gz rpi-MMU-example-ebc85a24c9c04232e775f5bc7cf4ea9af8e1caa7.zip |
add TODO concerning smarter use of memory attributes
-rw-r--r-- | TODOs | 2 |
1 files changed, 2 insertions, 0 deletions
@@ -54,6 +54,8 @@ high priority TODOs are higher; low priority ones and completed ones are lower; * write some procedures for dumping registers and other stuff (for use in debugging); maybe print registers' contents on data/prefetch abort? +* Memory regions can be configured as one of several types, which affects how memory reads/writes are performed by the processor. Dig into that and use the best appropriate settings in paging.c (i.e. normal memory instead of strongly-ordered memory for RAM). + * partially DONE - one can always add more, but we have the most important stuff * Implement some basic utilities for us to use (memcpy, printf, etc...) * partailly DONE - svc works; once we implement processes we could also kill them on aborts * develop userspace process supervision (handling of interrupt caused by svc instruction, proper handling of other data abort, undefined instruction, etc.) |