collapseos/kernel
Virgil Dupras 7cf3ed38da Extract str.asm from core.asm and make core included by userspace
Most of register fiddling routines (which is now the only thing contained
in care.asm) are used by almost all userspace apps, often in inner loops.

That makes the penalty of using jump tables for those a bit too high.
Moreover, it burdens jump tables needlessly.

Because this unit is very small (now that string routines are out), it makes
sense to always include it in binaries.
2019-11-14 10:14:15 -05:00
..
fnt recipes/ti84: use a 3x5 font instead of a 5x7 one 2019-11-11 13:26:24 -05:00
sms Move ASCII consts to ascii.h 2019-11-13 20:38:06 -05:00
ti Move ASCII consts to ascii.h 2019-11-13 20:38:06 -05:00
acia.asm acia: make GetC blocking 2019-11-04 14:44:43 -05:00
ascii.h Move ASCII consts to ascii.h 2019-11-13 20:38:06 -05:00
blockdev_cmds.asm Rename blockdev's API routines to GetB/PutB 2019-10-30 16:59:35 -04:00
blockdev.asm Rename blockdev's API routines to GetB/PutB 2019-10-30 16:59:35 -04:00
core.asm Extract str.asm from core.asm and make core included by userspace 2019-11-14 10:14:15 -05:00
err.h Rename blockdev's API routines to GetB/PutB 2019-10-30 16:59:35 -04:00
fs_cmds.asm fs: fix broken fopn on id > 0 2019-06-05 15:40:56 -04:00
fs.asm Rename blockdev's API routines to GetB/PutB 2019-10-30 16:59:35 -04:00
kbd.asm kbd: add keypad codes to keycode table 2019-07-25 14:22:17 -04:00
mmap.asm Rename blockdev's API routines to GetB/PutB 2019-10-30 16:59:35 -04:00
parse.asm Decimal parse optimisations (#45) 2019-10-24 07:58:32 -04:00
pgm.asm Rename blockdev's API routines to GetB/PutB 2019-10-30 16:59:35 -04:00
README.md ed: add 'd' cmd 2019-07-14 10:32:28 -04:00
sdc.asm Rename blockdev's API routines to GetB/PutB 2019-10-30 16:59:35 -04:00
shell.asm Move ASCII consts to ascii.h 2019-11-13 20:38:06 -05:00
stdio.asm Move ASCII consts to ascii.h 2019-11-13 20:38:06 -05:00
str.asm Extract str.asm from core.asm and make core included by userspace 2019-11-14 10:14:15 -05: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.

This code is designed to be assembled by Collapse OS' own [zasm][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"

Stack management

Keeping the stack "balanced" is a big challenge when writing assembler code. Those push and pop need to correspond, otherwise we end up with completely broken code.

The usual "push/pop" at the beginning and end of a routine is rather easy to manage, nothing special about them.

The problem is for the "inner" push and pop, which are often necessary in routines handling more data at once. In those cases, we walk on eggshells.

A naive approach could be to indent the code between those push/pop, but indent level would quickly become too big to fit in 80 chars.

I've tried ASCII art in some places, where comments next to push/pop have "|" indicating the scope of the push/pop. It's nice, but it makes code complicated to edit, especially when dense comments are involved. The pipes have to go through them.

Of course, one could add descriptions next to each push/pop describing what is being pushed, and I do it in some places, but it doesn't help much in easily tracking down stack levels.

So, what I've started doing is to accompany each "non-routine" (at the beginning and end of a routine) push/pop with "--> lvl X" and "<-- lvl X" comments. Example:

push    af  ; --> lvl 1
inc     a
push    af  ; --> lvl 2
inc     a
pop     af  ; <-- lvl 2
pop     af  ; <-- lvl 1

I think that this should do the trick, so I'll do this consistently from now on. [zasm]: ../apps/zasm/README.md