izaya
/
collapseos
mirror of https://github.com/hsoft/collapseos.git
1
1
Fork 0
Code Issues 0 Releases 0 Wiki Activity
Mirror of CollapseOS
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
377 Commits
4 Branches
13MB
Tree: 3d474c9121
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '3d474c9121'
${ noResults }
collapseos/kernel
Virgil Dupras 921a109749 stdio: little tweaks 5 years ago
..
sms sms/pad: make B jump to the next selection "class" 5 years ago
README.md Update docs w.r.t. its relationship with scas 5 years ago
acia.asm acia: protect DE during aciaInt 5 years ago
blockdev.asm Update comments 5 years ago
blockdev_cmds.asm blockdev: fix bug recently introduced in load cmd 5 years ago
core.asm shell: add support for backspace 5 years ago
err.h blockdev: make implementors "random access" 5 years ago
fs.asm zasm: fix include EOF detection 5 years ago
fs_cmds.asm fs: fix broken fopn on id > 0 5 years ago
kbd.asm kbd: make letters lowercase 5 years ago
mmap.asm blockdev: make implementors "random access" 5 years ago
parse.asm parse: fix option word default value 5 years ago
pgm.asm pgm: adapt to recent blkdev change 5 years ago
sdc.asm sdc: make sdcReadBlk return error on max retries 5 years ago
shell.asm stdio: add stdioReadC 5 years ago
stdio.asm stdio: little tweaks 5 years ago
user.h.example zasm emul: bring back kernel/user distinction 5 years ago

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"