From 24de320bb1d63beefd5bc89c97b4ad727d8e05e7 Mon Sep 17 00:00:00 2001 From: Andreas Baumann Date: Sun, 29 Oct 2017 11:47:05 +0100 Subject: some docu fixes --- doc/LINKS.TODO | 5 +++++ src/kernel/entry.c | 4 ++-- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/doc/LINKS.TODO b/doc/LINKS.TODO index d9b081b..5686ec6 100644 --- a/doc/LINKS.TODO +++ b/doc/LINKS.TODO @@ -19,6 +19,7 @@ http://www.henkessoft.de/OS_Dev/OS_Dev1.htm http://www.brokenthorn.com/Resources/OSDevIndex.html - fitting code following the brokenthorm tutorial: https://github.com/tuhdo/os-study +http://www.fysnet.net/ In C#: https://github.com/FlingOS/FlingOS @@ -125,3 +126,7 @@ http://www.hackersdelight.org/hdcodetxt/crc.c.txt ARP: https://tools.ietf.org/html/rfc826 http://wiki.osdev.org/Address_Resolution_Protocol + +Syscalls: +AX, BX software interrupt 0x80, classic Linux/DOS/Windows syscalls + diff --git a/src/kernel/entry.c b/src/kernel/entry.c index d0e75a7..e85460a 100644 --- a/src/kernel/entry.c +++ b/src/kernel/entry.c @@ -1,11 +1,11 @@ #include "kernel.h" // must be first entry in kernel.bin (0x8800) as stage 2 of -// the boot loader expects the entry point to b here! +// the boot loader expects the entry point to be here! // // compilers (at least gcc) mess with the order of functions when // compiling with optimization levels, so kernel_main ends up somewhere -// in the first compilation unit. I didn't find an elegand way (but for +// in the first compilation unit. I didn't find an elegant way (but for // an ld script with custom section and some compiler specific attributes // how to solve this issue). This solution here is sort of a nice // workaround working no matter what the compilers try to do (of course -- cgit v1.2.3-54-g00ecf