Virgil Dupras
2da4a3a87b
|
5 年之前 | |
|---|---|---|
| .. | ||
| sms | 5 年之前 | |
| README.md | 5 年之前 | |
| acia.asm | 5 年之前 | |
| blockdev.asm | 5 年之前 | |
| blockdev_cmds.asm | 5 年之前 | |
| core.asm | 5 年之前 | |
| err.h | 5 年之前 | |
| fs.asm | 5 年之前 | |
| fs_cmds.asm | 5 年之前 | |
| kbd.asm | 5 年之前 | |
| mmap.asm | 5 年之前 | |
| parse.asm | 5 年之前 | |
| pgm.asm | 5 年之前 | |
| sdc.asm | 5 年之前 | |
| shell.asm | 5 年之前 | |
| stdio.asm | 5 年之前 | |
| user.h.example | 5 年之前 | |
README.md
Kernel
Bits and pieces of code that you can assemble to build a kernel for your machine.
These parts are made to be glued together in a single glue.asm file you write
yourself.
This code is designed to be assembled by Collapse OS’ own zasm.
Defines
Each part can have its own constants, but some constant are made to be defined externally. We already have some of those external definitions in platform includes, but we can have more defines than this.
Each part has a “DEFINES” section listing the constant it expects to be defined. Make sure that you have these constants defined before you include the file.
Variable management
Each part can define variables. These variables are defined as addresses in
RAM. We know where RAM start from the RAMSTART constant in platform includes,
but because those parts are made to be glued together in no pre-defined order,
we need a system to align variables from different modules in RAM.
This is why each part that has variable expect a <PARTNAME>_RAMSTART
constant to be defined and, in turn, defines a <PARTNAME>_RAMEND constant to
carry to the following part.
Thus, code that glue parts together could look like:
MOD1_RAMSTART .equ RAMSTART
#include "mod1.asm"
MOD2_RAMSTART .equ MOD1_RAMEND
#include "mod2.asm"