BarinkOS/source/kernel/drivers
Nigel b07b4f0d38 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 23:38:32 +01:00
..
acpi Moving certain aspects into their own static library 2023-02-19 23:38:32 +01:00
ata Moving certain aspects into their own static library 2023-02-19 23:38:32 +01:00
atapi Merged FAT16 into Dev 2023-02-03 21:47:05 +01:00
cmos src folder -> source folder; makes merging with dev a bit easier. 2022-09-10 20:06:49 +02:00
ide Cleanup of PCI API 2023-02-17 14:42:42 +01:00
io Merged FAT16 into Dev 2023-02-03 21:47:05 +01:00
pci Cleanup of PCI API 2023-02-17 14:42:42 +01:00
pic Merged FAT16 into Dev 2023-02-03 21:47:05 +01:00
pit Merged FAT16 into Dev 2023-02-03 21:47:05 +01:00
ps-2 Starting to move towards proper HAL and ring3 2023-02-11 12:22:45 +01:00
serial KERNEL: Implementing VMM & cleaning up 2022-09-01 20:16:16 +02:00
vga KERNEL: Implementing VMM & cleaning up 2022-09-01 20:16:16 +02:00