Virgil Dupras b7cda6ed14 shell: improve reliability Make ASCII_BS (sent when driven through kbd) make the same thing as ASCII_DEL. Also, don't crash on filling the buffer.		2019-06-30 13:25:14 -04:00
..
acia.asm
blockdev_cmds.asm
blockdev.asm
core.asm
err.h
fs_cmds.asm
fs.asm
kbd.asm	kbd: make letters lowercase	2019-06-30 13:24:35 -04:00
mmap.asm
parse.asm
pgm.asm
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: improve reliability	2019-06-30 13:25:14 -04:00
stdio.asm
user.h.example

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"