aboutsummaryrefslogtreecommitdiff
path: root/TODO.txt
diff options
context:
space:
mode:
authorKimplul <kimi.h.kuparinen@gmail.com>2021-10-11 23:18:47 +0300
committerKimplul <kimi.h.kuparinen@gmail.com>2021-10-11 23:18:47 +0300
commit7237d673904d8568a2f9c290a0247c9d1a07c5d2 (patch)
tree7deabe2dc64ddf05016eb3e3a4f22a7e252b5c35 /TODO.txt
parentebd34a9ab3809167e16e4107c8e72d1d81faff9c (diff)
downloadkmi-7237d673904d8568a2f9c290a0247c9d1a07c5d2.tar.gz
kmi-7237d673904d8568a2f9c290a0247c9d1a07c5d2.zip
Start designing vmem framework
Diffstat (limited to 'TODO.txt')
-rw-r--r--TODO.txt9
1 files changed, 6 insertions, 3 deletions
diff --git a/TODO.txt b/TODO.txt
index 5176f0a..0d65372 100644
--- a/TODO.txt
+++ b/TODO.txt
@@ -7,9 +7,12 @@
+ Write the kernel lol
+ Test libfdt and see if it can be used to read memory geometry etc.
-+ Jump to vmem
++ Jump to vmem x
+ Mark fdt, reserved mem, kernel, init and initrd in vmem. Remember to remove
init from vmem when jumping to vmem
-+ Figure out best way to tell the init how large out kernel is
++ Figure out best way to tell the init how large out kernel is x~
+ Make code more robust, error checking etc
-+ Make all physical memory addresses use the same typedef
++ Make all physical memory addresses use the same typedef x
+
++ should I consider passing more pointers around rather than return structures?
++ should probably come up with some kind of general error handling scheme?