aboutsummaryrefslogtreecommitdiff
path: root/TODO.txt
diff options
context:
space:
mode:
authorKimplul <kimi.h.kuparinen@gmail.com>2021-12-21 13:24:33 +0200
committerKimplul <kimi.h.kuparinen@gmail.com>2021-12-21 13:24:33 +0200
commit0e1617f1e68c9900538296f1186c0e9768d6cb87 (patch)
tree706ea8942cc2ddf290bc72760e81bc8569d31995 /TODO.txt
parent41c405fdb18b139bbde475063230e14a59304ef6 (diff)
downloadkmi-0e1617f1e68c9900538296f1186c0e9768d6cb87.tar.gz
kmi-0e1617f1e68c9900538296f1186c0e9768d6cb87.zip
Started allowing higher order allocs
Diffstat (limited to 'TODO.txt')
-rw-r--r--TODO.txt12
1 files changed, 10 insertions, 2 deletions
diff --git a/TODO.txt b/TODO.txt
index 77cdf70..464539f 100644
--- a/TODO.txt
+++ b/TODO.txt
@@ -6,5 +6,13 @@
+ Make sure vmap is in 4K increments or whatever
+ Remove/converge convnum and debugging __atoi
+ Create actual init program
- + That will need some kind of linking info, say, `place .text etc above
- 0xffffffadsadsad` or whatever. Should be doable, let's see.
+
++ Add in (attempting) to map into specific region of memory, see phone for
+details dumbass
++ Primarily memory should be allocated to a process through mmap-like
+functionality, but brk/sbrk can probably still be emulated. If s/brk maps memory
+that's later attempted to mmap, it fails, and vice versa. Apparently should be
+acceptable by Unix standards.
++ Alignment can maybe still be used, though more in the sense of using larger
+pages? YES, CHECK common/vmem.c:map_fill_region! Should be implemented there as
+well