Mark
c3f23032f0
Memory map is now a part of boot protocol structure. The change was caused by UEFI placing this boot structure (as part of yboot's data section) very high in physical memory, above kernel's mapped 4GiB range, so kernel had no way of accessing it. It's not the best solution, but will work for sure.
Yggdrasil x86-64 kernel
(I still need refactoring, huh.)
Yggdrasil is the name for my kernel development project which tries to follow the Unix principles (yet another POSIX OS?) and is loosely inspired by stuff like Linux, BSD and other *nixes I've laid my hands on so far.
Building
See Building Guide
What works
- Preemptive multitasking (kernel/user)
- VFS implementation with non-resident ("mapper") filesystem support
- ext2 driver supporting both read/write (pending rewrite though), directories and symlinks
- VT100 basic control sequences for color/cursor control in tty.
- tar-based initrd with programs and other files for userspace
- Over 50 system calls for POSIX-like interface: fork()/execve()/read()/write()/...
What works: devices
- RTL8139 Network Controller - both Tx/Rx
- AHCI SATA controllers (Read/Write)
Credits
- Linux for default8x16 font