izaya/collapseos
1
0
Fork 0
mirror of https://github.com/hsoft/collapseos.git synced 2024-12-27 21:58:05 +11:00
Code Issues Releases Wiki Activity
8f1d942e5f
collapseos/recipes/sms/glue.asm

49 lines
754 B
NASM
Raw Normal View History

recipes/sms: hitting a button now adds a char on the screen
2019-07-03 00:49:30 +10:00
; 8K of onboard RAM
.equ RAMSTART 0xc000
; Memory register at the end of RAM. Must not overwrite
.equ RAMEND 0xfdd0
jp init
recipes/sms: New section for Sega Master System
2019-07-02 01:05:25 +10:00
.fill 0x66-$
retn
zasm: rename #inc to .inc scas, it's not needed any more.
2019-10-07 05:32:23 +11: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-14 12:38:06 +11:00
.inc "ascii.h"
zasm: rename #inc to .inc scas, it's not needed any more.
2019-10-07 05:32:23 +11: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-15 01:55:31 +11:00
.inc "str.asm"
recipes/sms: plug shell in! Now this is getting eminently exciting!
2019-07-03 01:14:30 +10:00
recipes/sms: hitting a button now adds a char on the screen
2019-07-03 00:49:30 +10:00
.equ PAD_RAMSTART RAMSTART
zasm: rename #inc to .inc scas, it's not needed any more.
2019-10-07 05:32:23 +11:00
.inc "sms/pad.asm"
sms/pad: new module to manage Megadrive controller in SMS
2019-07-02 23:02:19 +10:00
recipes/sms: hitting a button now adds a char on the screen
2019-07-03 00:49:30 +10:00
.equ VDP_RAMSTART PAD_RAMEND
zasm: rename #inc to .inc scas, it's not needed any more.
2019-10-07 05:32:23 +11:00
.inc "sms/vdp.asm"
recipes/sms: hitting a button now adds a char on the screen
2019-07-03 00:49:30 +10:00
recipes/sms: plug shell in! Now this is getting eminently exciting!
2019-07-03 01:14:30 +10:00
.equ STDIO_RAMSTART VDP_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-05 01:55:12 +11:00
.equ STDIO_GETC padGetC
.equ STDIO_PUTC vdpPutC
zasm: rename #inc to .inc scas, it's not needed any more.
2019-10-07 05:32:23 +11:00
.inc "stdio.asm"
recipes/sms: plug shell in! Now this is getting eminently exciting!
2019-07-03 01:14:30 +10: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-16 07:37:49 +11:00
; *** Shell ***
.inc "lib/util.asm"
.inc "lib/parse.asm"
.inc "lib/args.asm"
.inc "lib/stdio.asm"
recipes/sms: plug shell in! Now this is getting eminently exciting!
2019-07-03 01:14:30 +10: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-16 07:37:49 +11:00
.inc "shell/main.asm"
recipes/sms: plug shell in! Now this is getting eminently exciting!
2019-07-03 01:14:30 +10:00
recipes/sms: hitting a button now adds a char on the screen
2019-07-03 00:49:30 +10:00
init:
sms/pad: new module to manage Megadrive controller in SMS
2019-07-02 23:02:19 +10:00
di
im 1
recipes/sms: hitting a button now adds a char on the screen
2019-07-03 00:49:30 +10:00
ld sp, RAMEND
recipes/sms: New section for Sega Master System
2019-07-02 01:05:25 +10:00
recipes/sms: plug shell in! Now this is getting eminently exciting!
2019-07-03 01:14:30 +10:00
call padInit
recipes/sms: hitting a button now adds a char on the screen
2019-07-03 00:49:30 +10:00
call vdpInit
recipes/sms: plug shell in! Now this is getting eminently exciting!
2019-07-03 01:14:30 +10:00
call shellInit
jp shellLoop
recipes/sms: New section for Sega Master System
2019-07-02 01:05:25 +10:00
.fill 0x7ff0-$
.db "TMR SEGA", 0x00, 0x00, 0xfb, 0x68, 0x00, 0x00, 0x00, 0x4c
Reference in New Issue Copy Permalink