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.
Virgil Dupras 9eb80d5eac sms/pad: new module to manage Megadrive controller in SMS преди 5 години
..
sms sms/pad: new module to manage Megadrive controller in SMS преди 5 години
README.md Update docs w.r.t. its relationship with scas преди 5 години
acia.asm acia: protect DE during aciaInt преди 5 години
blockdev.asm Update comments преди 5 години
blockdev_cmds.asm blockdev: fix bug recently introduced in load cmd преди 5 години
core.asm shell: add support for backspace преди 5 години
err.h blockdev: make implementors "random access" преди 5 години
fs.asm zasm: fix include EOF detection преди 5 години
fs_cmds.asm fs: fix broken fopn on id > 0 преди 5 години
kbd.asm kbd: make letters lowercase преди 5 години
mmap.asm blockdev: make implementors "random access" преди 5 години
parse.asm parse: fix option word default value преди 5 години
pgm.asm pgm: adapt to recent blkdev change преди 5 години
sdc.asm sdc: make sdcReadBlk return error on max retries преди 5 години
shell.asm shell: improve reliability преди 5 години
stdio.asm shell/stdio: decouple from blkdev (again) преди 5 години
user.h.example zasm emul: bring back kernel/user distinction преди 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"