From 79f4ccc10510d9ba29bad6f233ef6e9d3a7939bc Mon Sep 17 00:00:00 2001 From: Wojtek Kosior Date: Mon, 20 Jan 2020 14:54:49 +0100 Subject: fix a typo --- docs/MMU-explained.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/MMU-explained.txt b/docs/MMU-explained.txt index a26c670..ae2fe83 100644 --- a/docs/MMU-explained.txt +++ b/docs/MMU-explained.txt @@ -75,7 +75,7 @@ As of 15.01.2020 page tables and small pages are not used in the project (althou ### Project specific info -Despite the overhelming amount of configuration options available, most can be left deafult and this is how it's done in this project. Those default settings usually make the MMU behave like it did in older ARM versions, when some options were not yet available and hence, the entire system was simpler. +Despite the overwhelming amount of configuration options available, most can be left deafult and this is how it's done in this project. Those default settings usually make the MMU behave like it did in older ARM versions, when some options were not yet available and hence, the entire system was simpler. Our project uses C bitfield structs for operating on SCTLR and TTBCR contents and translation table descriptors. With DACR - bit shifts are more appropriate and with TTBCR - our default configuration means we're writing '0' to that register. This is an elegant and readable approach, yet little-portable across compilers. Current struct definitions work properly with GCC. -- cgit v1.2.3