collapseos/recipes/rc2014/ps2/glue.asm

.equ	RAMSTART	0x8000
.equ	RAMEND		0xffff
.equ	ACIA_CTL	0x80	; Control and status. RS off.
.equ	ACIA_IO		0x81	; Transmit. RS on.
.equ	KBD_PORT	0x08

jp	init

.inc "err.h"
.inc "ascii.h"
.inc "core.asm"
.inc "str.asm"
.equ	ACIA_RAMSTART	RAMSTART
.inc "acia.asm"

.equ	KBD_RAMSTART	ACIA_RAMEND
.inc "kbd.asm"

.equ	STDIO_RAMSTART	KBD_RAMEND
.equ	STDIO_GETC	kbdGetC
.equ	STDIO_PUTC	aciaPutC
.inc "stdio.asm"

; *** Shell ***
.inc "lib/util.asm"
.inc "lib/parse.asm"
.inc "lib/args.asm"
.inc "lib/stdio.asm"
.equ	SHELL_RAMSTART	STDIO_RAMEND
.equ	SHELL_EXTRA_CMD_COUNT 0
.inc "shell/main.asm"

init:
	di
	; setup stack
	ld	hl, RAMEND
	ld	sp, hl

	call	aciaInit
	call	kbdInit
	call	shellInit
	jp	shellLoop

KBD_FETCHKC:
	in	a, (KBD_PORT)
	ret
recipes/rc2014/ps2: drive a shell with ps/2 kbd! 2019-06-29 14:25:18 -04:00			`.equ RAMSTART 0x8000`
			`.equ RAMEND 0xffff`
			`.equ ACIA_CTL 0x80 ; Control and status. RS off.`
			`.equ ACIA_IO 0x81 ; Transmit. RS on.`
			`.equ KBD_PORT 0x08`

			`jp init`

zasm: rename #inc to .inc scas, it's not needed any more. 2019-10-06 14:32:23 -04:00			`.inc "err.h"`
Move ASCII consts to ascii.h And made them shorter in name. The new ascii.h file allow reuse in userspace code. 2019-11-13 20:38:06 -05:00			`.inc "ascii.h"`
zasm: rename #inc to .inc scas, it's not needed any more. 2019-10-06 14:32:23 -04:00			`.inc "core.asm"`
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 09:55:31 -05:00			`.inc "str.asm"`
recipes/rc2014/ps2: drive a shell with ps/2 kbd! 2019-06-29 14:25:18 -04:00			`.equ ACIA_RAMSTART RAMSTART`
zasm: rename #inc to .inc scas, it's not needed any more. 2019-10-06 14:32:23 -04:00			`.inc "acia.asm"`
recipes/rc2014/ps2: drive a shell with ps/2 kbd! 2019-06-29 14:25:18 -04:00
			`.equ KBD_RAMSTART ACIA_RAMEND`
zasm: rename #inc to .inc scas, it's not needed any more. 2019-10-06 14:32:23 -04:00			`.inc "kbd.asm"`
recipes/rc2014/ps2: drive a shell with ps/2 kbd! 2019-06-29 14:25:18 -04:00
			`.equ STDIO_RAMSTART KBD_RAMEND`
stdio: remove a layer of indirection in GetC/PutC We use zasm's ability to use labels in .equ directive. We didn't do it before because for a while, we were in between scas and zasm (scas was used in automated tests) so we needed to use the lowest common denominator: zasm doesn't have macros and scas can't use labels in .equ directives. This forced us to add this layer of indirection. But now that we are completely cut from scas' dependency, we can use this nice zasm's ability. 2019-11-04 09:55:12 -05:00			`.equ STDIO_GETC kbdGetC`
			`.equ STDIO_PUTC aciaPutC`
zasm: rename #inc to .inc scas, it's not needed any more. 2019-10-06 14:32:23 -04:00			`.inc "stdio.asm"`
recipes/rc2014/ps2: drive a shell with ps/2 kbd! 2019-06-29 14:25:18 -04:00
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-15 15:37:49 -05:00			`; * Shell *`
			`.inc "lib/util.asm"`
			`.inc "lib/parse.asm"`
			`.inc "lib/args.asm"`
			`.inc "lib/stdio.asm"`
recipes/rc2014/ps2: drive a shell with ps/2 kbd! 2019-06-29 14:25:18 -04:00			`.equ SHELL_RAMSTART STDIO_RAMEND`
			`.equ SHELL_EXTRA_CMD_COUNT 0`
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-15 15:37:49 -05:00			`.inc "shell/main.asm"`
recipes/rc2014/ps2: drive a shell with ps/2 kbd! 2019-06-29 14:25:18 -04:00
			`init:`
			`di`
			`; setup stack`
			`ld hl, RAMEND`
			`ld sp, hl`

			`call aciaInit`
recipes/rc2014/ps2: works rather well now! 2019-06-30 14:16:00 -04:00			`call kbdInit`
recipes/rc2014/ps2: drive a shell with ps/2 kbd! 2019-06-29 14:25:18 -04:00			`call shellInit`
			`jp shellLoop`
recipes/sms/kbd: PS/2 keyboard adapter for the SMS! 2019-07-19 15:45:13 -04:00
			`KBD_FETCHKC:`
			`in a, (KBD_PORT)`
			`ret`