This repository has been archived by the owner on Apr 7, 2022. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
2 additions
and
20 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,23 +1,5 @@ | ||
# RomainOS | ||
|
||
Here's a 64 bits OS, from scratch, using assembly and C++. | ||
Here's a 64 bits OS using assembly and C++, with a display of 25x80 pixels. | ||
|
||
### How and why is it working | ||
|
||
When booting, the BIOS will load the first 512 bytes from the disk (aka the boot sector), defined in <code>src/bootSector/bootloader.asm</code>. | ||
|
||
The bootloader, still in "real-mode" 16-bits, will then enter in "protected-mode" 32-bits using <code>src/secondSector/extendedProgram.asm</code>.<br> | ||
At this stage, the available memory is listed and well-structured,<br> | ||
there's no wrap-around at 1 MB (yeah this bug really haunted me, but the A20 line is finally enabled),<br> | ||
the interrupts are disabled, and there's a basic permission system applied, while still being limited at 4 GB. | ||
|
||
Then, we continue up to 64-bits mode, handling a VGA display of 25x80 pixels (!).<br> | ||
CPU infos are availables, 64 bits int are usable, GDT goes on 64 bits and the RAM finally has paging. | ||
|
||
Then, floating points operations inside the kernel are supported using SSE. | ||
|
||
Last assembly trick, the function <code>_start</code> from <code>src/kernel.cpp</code> is called, finally loading the "true" C++ kernel. | ||
|
||
In C++ now, keyboards interrupts are initialized, and the available memory regions fetched. | ||
|
||
And THEN, the kernel is ready ! | ||
Work in progress, but will probably only be continued after my other stuff (especially, a compiler). |