aboutsummaryrefslogtreecommitdiff
path: root/docs/boot.md
diff options
context:
space:
mode:
authorKimplul <kimi.h.kuparinen@gmail.com>2023-06-04 17:43:32 +0300
committerKimplul <kimi.h.kuparinen@gmail.com>2023-06-04 17:43:32 +0300
commitc7df9ae5f60ef1d36a20dbfbb8b4b0f4cd1a601a (patch)
treec7d4d044c5657cb57649d828d6a52b847b33ea83 /docs/boot.md
parent3dbd8c34176312b0bd3aba2309d284ac83181411 (diff)
downloadkmi-c7df9ae5f60ef1d36a20dbfbb8b4b0f4cd1a601a.tar.gz
kmi-c7df9ae5f60ef1d36a20dbfbb8b4b0f4cd1a601a.zip
add some docs about visionfive2
Diffstat (limited to 'docs/boot.md')
-rw-r--r--docs/boot.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/boot.md b/docs/boot.md
index 2131d93..f79f475 100644
--- a/docs/boot.md
+++ b/docs/boot.md
@@ -1,11 +1,11 @@
I need to figure out how to write MarkDown files, but the general procedure of a
boot is that we
-1) Assume we start of in real memory mode, i.e. no MMU active.
+1. Assume we start of in real memory mode, i.e. no MMU active.
-2) arch/whatever/init/init.c kickstarts us into virtual memory with a direct
-mapping, with offset VM_DMAP aliasing to physical address 0.
+2. arch/whatever/init/init.c kickstarts us into virtual memory with a direct
+mapping, with offset `VM_DMAP` aliasing to physical address 0.
-3) The kernel proper is moved to its correct location in this direct mapping.
+3. The kernel proper is moved to its correct location in this direct mapping.
-4) The kernel proper is jumped to, after which the kernel does whatever.
+4. The kernel proper is jumped to, after which the kernel does whatever.