2019-04-17 03:36:57 +10:00
|
|
|
# User applications
|
|
|
|
|
|
2019-05-20 01:19:41 +10:00
|
|
|
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.
|
2019-06-03 04:05:20 +10:00
|
|
|
|
|
|
|
|
## 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.
|
2019-11-14 07:28:16 +11:00
|
|
|
|
|
|
|
|
A userspace application can expect the `SP` pointer to be properly set. If it
|
|
|
|
|
moves it, it should take care of returning it where it was before returning
|
|
|
|
|
because otherwise, it will break the kernel.
|
|
|
|
|
|
|
|
|
|
Apps in Collapse OS are design to be ROM-compatible, that is, they don't write
|
|
|
|
|
to addresses that are part of the code's address space.
|
