aboutsummaryrefslogtreecommitdiff
path: root/docs/boot.md
diff options
context:
space:
mode:
authorKimplul <kimi.h.kuparinen@gmail.com>2022-05-29 01:07:48 +0300
committerKimplul <kimi.h.kuparinen@gmail.com>2022-05-29 01:07:48 +0300
commit0f4a751e60a6c8ac40592ff44c74f1c9e4846d9a (patch)
tree96fb1e8479261a128f065ee493ee3a97a3b91949 /docs/boot.md
parent013a27aec9370221e8afae188a8ed08ed2d406b0 (diff)
downloadkmi-0f4a751e60a6c8ac40592ff44c74f1c9e4846d9a.tar.gz
kmi-0f4a751e60a6c8ac40592ff44c74f1c9e4846d9a.zip
continue documentation efforts.
Diffstat (limited to 'docs/boot.md')
-rw-r--r--docs/boot.md11
1 files changed, 11 insertions, 0 deletions
diff --git a/docs/boot.md b/docs/boot.md
new file mode 100644
index 0000000..2131d93
--- /dev/null
+++ b/docs/boot.md
@@ -0,0 +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.
+
+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.
+
+4) The kernel proper is jumped to, after which the kernel does whatever.