Mirror of CollapseOS
Nelze vybrat více než 25 témat Téma musí začínat písmenem nebo číslem, může obsahovat pomlčky („-“) a může být dlouhé až 35 znaků.
Virgil Dupras e44ebb08b2 recipes/rc2014/ps2: drive a shell with ps/2 kbd! před 5 roky
..
README.md Update docs w.r.t. its relationship with scas před 5 roky
acia.asm acia: protect DE during aciaInt před 5 roky
blockdev.asm Update comments před 5 roky
blockdev_cmds.asm blockdev: fix bug recently introduced in load cmd před 5 roky
core.asm shell: add support for backspace před 5 roky
err.h blockdev: make implementors "random access" před 5 roky
fs.asm zasm: fix include EOF detection před 5 roky
fs_cmds.asm fs: fix broken fopn on id > 0 před 5 roky
kbd.asm recipes/rc2014/ps2: drive a shell with ps/2 kbd! před 5 roky
mmap.asm blockdev: make implementors "random access" před 5 roky
parse.asm parse: fix option word default value před 5 roky
pgm.asm pgm: adapt to recent blkdev change před 5 roky
sdc.asm sdc: make sdcReadBlk return error on max retries před 5 roky
shell.asm shell: make arg in peek/poke mandatory před 5 roky
stdio.asm shell/stdio: decouple from blkdev (again) před 5 roky
user.h.example zasm emul: bring back kernel/user distinction před 5 roky

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"