History

Virgil Dupras cbc6fb5931 zasm: clean up jump table requirements There was a little bit of cruft.		2019-11-11 20:21:13 -05:00
..
at28w	Rename blockdev's API routines to GetB/PutB	2019-10-30 16:59:35 -04:00
ed	Rename blockdev's API routines to GetB/PutB	2019-10-30 16:59:35 -04:00
lib	Decimal parse optimisations (#45 )	2019-10-24 07:58:32 -04:00
memt	zasm: rename #inc to .inc	2019-10-06 14:32:23 -04:00
sdct	Rename blockdev's API routines to GetB/PutB	2019-10-30 16:59:35 -04:00
zasm	zasm: clean up jump table requirements	2019-11-11 20:21:13 -05:00
README.md	Make userspace parse args the same way the shell does	2019-06-02 14:05:20 -04:00

README.md

User applications

This folder contains code designed to be "userspace" application. Unlike the kernel, which always stay in memory. Those apps here will more likely be loaded in RAM from storage, ran, then discarded so that another userspace program can be run.

That doesn't mean that you can't include that code in your kernel though, but you will typically not want to do that.

Userspace convention

We execute a userspace application by calling the address it's loaded into. This means: a userspace application is expected to return.

Whatever calls the userspace app (usually, it will be the shell), should set HL to a pointer to unparsed arguments in string form, null terminated.

The userspace application is expected to set A on return. 0 means success, non-zero means error.