collapseos/kernel
Virgil Dupras 63473cc2e3 blockdev: make selection structure opaque
I'm about to change that structure and I don't want fs to be messed up
by this. I'm proceeding step by step...
2019-06-04 09:56:36 -04:00
..
acia.asm Move /parts/z80 to /kernel 2019-05-19 11:19:41 -04:00
blockdev_cmds.asm blockdev: make selection structure opaque 2019-06-04 09:56:36 -04:00
blockdev.asm blockdev: make selection structure opaque 2019-06-04 09:56:36 -04:00
core.asm fs: check for file size bounds in GetC 2019-05-31 11:12:29 -04:00
err.h Make userspace parse args the same way the shell does 2019-06-02 14:05:20 -04:00
fs_cmds.asm fs: standardize file handle routine argument to IX 2019-05-31 14:28:06 -04:00
fs.asm blockdev: make selection structure opaque 2019-06-04 09:56:36 -04:00
mmap.asm mmap: make zasm-friendly 2019-06-03 11:14:29 -04:00
parse.asm Make parseArgs not expect a leading space 2019-06-02 14:46:07 -04:00
pgm.asm pgm: have its own file handle 2019-06-03 09:25:17 -04:00
README.md Move /parts/z80 to /kernel 2019-05-19 11:19:41 -04:00
sdc.asm sdc: add sdcPutC 2019-06-01 19:53:42 -04:00
shell.asm Make parseArgs not expect a leading space 2019-06-02 14:46:07 -04:00
stdio.asm shell/stdio: decouple from blkdev (again) 2019-06-02 11:06:38 -04:00
user.h.example zasm emul: bring back kernel/user distinction 2019-05-19 12:57:59 -04:00

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.

As of now, the z80 assembler code is written to be assembled with scas, but this is going to change in the future as a new hosted assembler is written.

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 coould look like:

MOD1_RAMSTART .equ RAMSTART
#include "mod1.asm"
MOD2_RAMSTART .equ MOD1_RAMEND
#include "mod2.asm"

Code style

The asm code used in these parts is heavily dependent on what scas offers. I try to be as "low-tech" as possible because the implementation of the assembler to be implemented for the z80 will likely be more limited. For example, we don't use macros.