collapseos/kernel
2019-06-29 14:26:03 -04:00
..
acia.asm acia: protect DE during aciaInt 2019-06-16 19:29:58 -04:00
blockdev_cmds.asm blockdev: fix bug recently introduced in load cmd 2019-06-17 09:54:30 -04:00
blockdev.asm Update comments 2019-06-17 13:42:53 -04:00
core.asm shell: add support for backspace 2019-06-14 22:14:09 -04:00
err.h
fs_cmds.asm fs: fix broken fopn on id > 0 2019-06-05 15:40:56 -04:00
fs.asm zasm: fix include EOF detection 2019-06-15 15:50:27 -04:00
kbd.asm recipes/rc2014/ps2: drive a shell with ps/2 kbd! 2019-06-29 14:26:03 -04:00
mmap.asm
parse.asm parse: fix option word default value 2019-06-14 21:10:18 -04:00
pgm.asm pgm: adapt to recent blkdev change 2019-06-05 14:45:38 -04:00
README.md Update docs w.r.t. its relationship with scas 2019-06-19 13:34:06 -04:00
sdc.asm sdc: make sdcReadBlk return error on max retries 2019-06-19 13:22:07 -04:00
shell.asm shell: make arg in peek/poke mandatory 2019-06-17 08:18:28 -04:00
stdio.asm
user.h.example

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"