collapseos/apps/shell/gluem.asm

; This repesents a minimal shell, that is, the smallest shell our configuration
; options allow. For a full-featured shell, see "glue.asm"
.inc "user.h"
.inc "err.h"
.inc "ascii.h"
jp	init

.inc "core.asm"
.inc "lib/util.asm"
.inc "lib/parse.asm"
.inc "lib/args.asm"
.inc "lib/fmt.asm"
.equ	SHELL_RAMSTART	USER_RAMSTART
.equ	SHELL_EXTRA_CMD_COUNT	0
.inc "shell/main.asm"

init:
	call	shellInit
	jp	shellLoop

USER_RAMSTART:
Make the shell a userspace app That's my mega-commit you've all been waiting for. The code for the shell share more routines with userspace apps than with kernel units, because, well, its behavior is that of a userspace app, not a device driver. This created a weird situation with libraries and jump tables. Some routine belonging to the `kernel/` directory felt weird there. And then comes `apps/basic`, which will likely share even more code with the shell. I was seeing myself creating huge jump tables to reuse code from the shell. It didn't feel right. Moreover, we'll probably want basic-like apps to optionnally replace the shell. So here I am with this huge change in the project structure. I didn't test all recipes on hardware yet, I will do later. I might have broken some... But now, the structure feels better and the line between what belongs to `kernel` and what belongs to `apps` feels clearer. 2019-11-16 07:37:49 +11:00			`; This repesents a minimal shell, that is, the smallest shell our configuration`
			`; options allow. For a full-featured shell, see "glue.asm"`
			`.inc "user.h"`
			`.inc "err.h"`
			`.inc "ascii.h"`
			`jp init`

			`.inc "core.asm"`
			`.inc "lib/util.asm"`
			`.inc "lib/parse.asm"`
			`.inc "lib/args.asm"`
basic: add puth command 2019-12-10 06:15:43 +11:00			`.inc "lib/fmt.asm"`
Make the shell a userspace app That's my mega-commit you've all been waiting for. The code for the shell share more routines with userspace apps than with kernel units, because, well, its behavior is that of a userspace app, not a device driver. This created a weird situation with libraries and jump tables. Some routine belonging to the `kernel/` directory felt weird there. And then comes `apps/basic`, which will likely share even more code with the shell. I was seeing myself creating huge jump tables to reuse code from the shell. It didn't feel right. Moreover, we'll probably want basic-like apps to optionnally replace the shell. So here I am with this huge change in the project structure. I didn't test all recipes on hardware yet, I will do later. I might have broken some... But now, the structure feels better and the line between what belongs to `kernel` and what belongs to `apps` feels clearer. 2019-11-16 07:37:49 +11:00			`.equ SHELL_RAMSTART USER_RAMSTART`
			`.equ SHELL_EXTRA_CMD_COUNT 0`
			`.inc "shell/main.asm"`

			`init:`
			`call shellInit`
			`jp shellLoop`

			`USER_RAMSTART:`