BarinkOS/kernel/supervisorterminal/superVisorTerminal.h

#pragma once 
#include "../terminal/kterm.h"
#include "../time.h"
#include "../drivers/pit/pit.h"
#include "../drivers/ps-2/keyboard.h"
#include "../memory/PhysicalMemoryManager.h"
#include <CoreLib/Memory.h>

extern "C" void startSuperVisorTerminal();
KERNEL: Implementing VMM & cleaning up Folders now are alll lower case Started working on the implementation of the Virtual memory manager. Implemented allocate and free page funtionality for as far as I can atm. Implemented the 2022-09-01 18:16:16 +00:00			`#pragma once`
			`#include "../terminal/kterm.h"`
			`#include "../time.h"`
			`#include "../drivers/pit/pit.h"`
			`#include "../drivers/ps-2/keyboard.h"`
			`#include "../memory/PhysicalMemoryManager.h"`
Moving certain aspects into their own static library Problem: As our kernel grows we need more complex datastructures and functions these would come from the standard C/C++ library with normal programs. The kernel is a freestanding programme and has no access to standard libraries. Solution: We build a mini version of the standard C/C++ library which will contain the datastructures and functions we want. This library can then be statically linked into our kernel binary. Making it a statically linked library also gives more structure to the project. Keeping these random functions and datastructures in the kernel just clutters the kernel source code with less relevant source code. 2023-02-19 22:38:32 +00:00			`#include <CoreLib/Memory.h>`
KERNEL: Implementing VMM & cleaning up Folders now are alll lower case Started working on the implementation of the Virtual memory manager. Implemented allocate and free page funtionality for as far as I can atm. Implemented the 2022-09-01 18:16:16 +00:00
Clean up jump into RING 3 2023-02-17 13:46:44 +00:00			`extern "C" void startSuperVisorTerminal();`