izaya/collapseos
1
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity
b575d7f863
collapseos/recipes/rc2014/ps2/glue.asm

60 lines
1.0 KiB
NASM
Raw Normal View History

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
recipes/rc2014/ps2: Use BASIC shell
2019-12-06 20:00:29 -05:00
; *** BASIC ***
; RAM space used in different routines for short term processing.
tools: use BASIC's new while loop Also, increase STDIO_BUFSIZE to 0x40 so that those while loops work.
2019-12-12 12:04:56 -05:00
.equ SCRATCHPAD_SIZE STDIO_BUFSIZE
recipes/rc2014/ps2: Use BASIC shell
2019-12-06 20:00:29 -05:00
.equ SCRATCHPAD STDIO_RAMEND
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 "lib/util.asm"
recipes/rc2014/ps2: Use BASIC shell
2019-12-06 20:00:29 -05:00
.inc "lib/ari.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-15 15:37:49 -05:00
.inc "lib/parse.asm"
recipes/rc2014/ps2: Use BASIC shell
2019-12-06 20:00:29 -05:00
.inc "lib/fmt.asm"
.equ EXPR_PARSE parseLiteralOrVar
.inc "lib/expr.asm"
.inc "basic/util.asm"
.inc "basic/parse.asm"
.inc "basic/tok.asm"
.equ VAR_RAMSTART SCRATCHPAD+SCRATCHPAD_SIZE
.inc "basic/var.asm"
.equ BUF_RAMSTART VAR_RAMEND
.inc "basic/buf.asm"
.equ BAS_RAMSTART BUF_RAMEND
.inc "basic/main.asm"
recipes/rc2014/ps2: drive a shell with ps/2 kbd!
2019-06-29 14:25:18 -04:00
init:
di
recipes/rc2014/ps2: Use BASIC shell
2019-12-06 20:00:29 -05:00
ld sp, RAMEND
im 1
recipes/rc2014/ps2: drive a shell with ps/2 kbd!
2019-06-29 14:25:18 -04:00
call aciaInit
recipes/rc2014/ps2: works rather well now!
2019-06-30 14:16:00 -04:00
call kbdInit
recipes/rc2014/ps2: Use BASIC shell
2019-12-06 20:00:29 -05:00
call basInit
ei
jp basStart
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
Reference in New Issue Copy Permalink