kmi - ACTIVE - Kernel with migrating threads as IPC

Age	Commit message (Collapse)	Author
2024-07-07	simplify assertions	Kimplul
	+ No real point having multiple different levels of assertions, just say you assert something and be done with it
2024-07-06	core bringup + various warnings	Kimplul
	+ dbg_fdt() is apparently broken, possibly due to UB or something, but it causes some issues with optimizations enabled. Remove it temporarily
2023-08-04	add initial smp bringup	Kimplul

2023-07-25	simplify fdt reg reading	Kimplul

2023-05-01	update license stuff	Kimplul

2023-04-30	rename to kmi	Kimplul

2022-06-12	add license texts	Kimplul

2022-05-29	modify formatting rules	Kimplul

2022-05-24	initial musings about exec	Kimplul

2022-05-23	start writing documentation	Kimplul

2022-05-22	add @file info to all files	Kimplul
	+ Next step, start documenting contents of each file.
2022-05-21	implement timers better	Kimplul

2022-04-10	add basic ubsan and fix issues reported by it	Kimplul

2022-04-10	add clang format and run it	Kimplul

2022-01-07	Use #if defined(...) when not guard clause	Kimplul

2021-12-29	Refactoring	Kimplul
	+ Mainly just moving stuff out or arch/riscv/ that should be handled in common/ + Prepared separate process stack/call stack for server callbacks, rest to be implemeted soon ish
2021-10-11	Moved some functions to common/	Kimplul

2021-09-20	Some slight robustness improvements and obo errors	Kimplul

2021-09-19	Added basic awareness of kernel size/bounds	Kimplul

2021-09-19	Added fdt debug capability	Kimplul
	+ For future reference, apos now requires initrd to be found in fdt.
2021-08-25	libfdt seems to work	Kimplul
	At least as far as reading memory info, cool. One issue I have is that .(ro)data is apparently accessed by absolute addresses, so I need to know at which address the kernel is going to be loaded. I would prefer completely position independent code, but if that's not possible then eh.