izaya/collapseos
1
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity
ae028e3a86
collapseos/tools/emul/zasm/glue.asm

120 lines
1.7 KiB
NASM
Raw Normal View History

Move apps/zasm/emul to tools/emul
2019-05-09 14:09:40 -04:00
; Glue code for the emulated environment
zasm: use blkdev IDs as input and output This will soon allow use to seek and tell on input, which is necessary for a second pass which is necessary for forward symbol references. This require making `blkSel` a bit more flexible. Rather than having one global selected blkdev, each app can select its own, in its own memory space.
2019-05-10 18:20:43 -04:00
.equ RAMSTART 0x4000
zasm now bootstraps itself without scas!
2019-05-19 15:03:34 -04:00
.equ USER_CODE 0x4800
Move apps/zasm/emul to tools/emul
2019-05-09 14:09:40 -04:00
.equ STDIO_PORT 0x00
zasm: change ioRewind to ioSeek Will need it soon.
2019-05-15 13:41:56 -04:00
.equ STDIN_SEEK 0x01
zasm emul: hook fsdev in glue code
2019-05-16 13:23:23 -04:00
.equ FS_DATA_PORT 0x02
.equ FS_SEEK_PORT 0x03
zasm emul: add dumpSymbolTable debug routine Very helpful...
2019-05-17 13:22:45 -04:00
.equ STDERR_PORT 0x04
Move apps/zasm/emul to tools/emul
2019-05-09 14:09:40 -04:00
zasm emul: bring back kernel/user distinction It was a bad idea to remove it. Now that I'm introducing the concept of a per-app glue file, it becomes much easier to build emulated zasm as a userspace app.
2019-05-19 12:57:59 -04:00
jp init ; 3 bytes
; *** JUMP TABLE ***
fs: check for file size bounds in GetC
2019-05-31 11:12:29 -04:00
jp strncmp
jp addDE
jp addHL
jp upcase
jp unsetZ
jp intoDE
jp intoHL
jp writeHLinDE
jp findchar
jp parseHex
jp parseHexPair
jp blkSel
jp fsFindFN
jp fsOpen
jp fsGetC
jp fsSeek
jp fsTell
jp cpHLDE
Make userspace parse args the same way the shell does
2019-06-02 14:05:20 -04:00
jp parseArgs
blockdev: make implementors "random access" This huge refactoring remove the Seek and Tell routine from blockdev implementation requirements and change GetC and PutC's API so that they take an address to read and write (through HL/DE) at each call. The "PTR" approach in blockdev implementation was very redundant from device to device and it made more sense to generalize. It's possible that future device aren't "random access", but we'll be able to add more device types later. Another important change in this commit is that the "blockdev handle" is now opaque. Previously, consumers of the API would happily call routines directly from one of the 4 offsets. We can't do that any more. This makes the API more solid for future improvements. This change forced me to change a lot of things in fs, but overall, things are now simpler. No more `FS_PTR`: the "device handle" now holds the active pointer. Lots, lots of changes, but it also feels a lot cleaner and solid.
2019-06-04 11:53:02 -04:00
jp _blkGetC
jp _blkPutC
jp _blkSeek
jp _blkTell
Move apps/zasm/emul to tools/emul
2019-05-09 14:09:40 -04:00
zasm emul: hook fsdev in glue code
2019-05-16 13:23:23 -04:00
#include "core.asm"
Make userspace parse args the same way the shell does
2019-06-02 14:05:20 -04:00
#include "err.h"
Add the concept of unit tests Will be much much easier to tests new core routines without having to re-create their context first. Also, extract parse.asm from core.asm
2019-05-17 09:33:20 -04:00
#include "parse.asm"
zasm emul: hook fsdev in glue code
2019-05-16 13:23:23 -04:00
.equ BLOCKDEV_RAMSTART RAMSTART
.equ BLOCKDEV_COUNT 3
#include "blockdev.asm"
; List of devices
blockdev: make implementors "random access" This huge refactoring remove the Seek and Tell routine from blockdev implementation requirements and change GetC and PutC's API so that they take an address to read and write (through HL/DE) at each call. The "PTR" approach in blockdev implementation was very redundant from device to device and it made more sense to generalize. It's possible that future device aren't "random access", but we'll be able to add more device types later. Another important change in this commit is that the "blockdev handle" is now opaque. Previously, consumers of the API would happily call routines directly from one of the 4 offsets. We can't do that any more. This makes the API more solid for future improvements. This change forced me to change a lot of things in fs, but overall, things are now simpler. No more `FS_PTR`: the "device handle" now holds the active pointer. Lots, lots of changes, but it also feels a lot cleaner and solid.
2019-06-04 11:53:02 -04:00
.dw emulGetC, unsetZ
.dw unsetZ, emulPutC
.dw fsdevGetC, fsdevPutC
zasm emul: hook fsdev in glue code
2019-05-16 13:23:23 -04:00
.equ FS_RAMSTART BLOCKDEV_RAMEND
.equ FS_HANDLE_COUNT 0
#include "fs.asm"
Move apps/zasm/emul to tools/emul
2019-05-09 14:09:40 -04:00
init:
di
zasm emul: get rid of the kernel/user distinction Made things complicated for nothing.
2019-05-19 09:14:40 -04:00
ld hl, 0xffff
Move apps/zasm/emul to tools/emul
2019-05-09 14:09:40 -04:00
ld sp, hl
zasm emul: hook fsdev in glue code
2019-05-16 13:23:23 -04:00
ld a, 2 ; select fsdev
blockdev: make selection structure opaque I'm about to change that structure and I don't want fs to be messed up by this. I'm proceeding step by step...
2019-06-04 09:56:36 -04:00
ld de, BLOCKDEV_SEL
zasm emul: hook fsdev in glue code
2019-05-16 13:23:23 -04:00
call blkSel
call fsOn
Make userspace parse args the same way the shell does
2019-06-02 14:05:20 -04:00
ld hl, .zasmArgs
zasm emul: bring back kernel/user distinction It was a bad idea to remove it. Now that I'm introducing the concept of a per-app glue file, it becomes much easier to build emulated zasm as a userspace app.
2019-05-19 12:57:59 -04:00
call USER_CODE
Move apps/zasm/emul to tools/emul
2019-05-09 14:09:40 -04:00
; signal the emulator we're done
halt
Make userspace parse args the same way the shell does
2019-06-02 14:05:20 -04:00
.zasmArgs:
Make parseArgs not expect a leading space
2019-06-02 14:46:07 -04:00
.db "0 1", 0
Make userspace parse args the same way the shell does
2019-06-02 14:05:20 -04:00
zasm emul: add dumpSymbolTable debug routine Very helpful...
2019-05-17 13:22:45 -04:00
; *** I/O ***
zasm: Read from and write to streams instead of memory
2019-05-09 15:36:03 -04:00
emulGetC:
blockdev: make implementors "random access" This huge refactoring remove the Seek and Tell routine from blockdev implementation requirements and change GetC and PutC's API so that they take an address to read and write (through HL/DE) at each call. The "PTR" approach in blockdev implementation was very redundant from device to device and it made more sense to generalize. It's possible that future device aren't "random access", but we'll be able to add more device types later. Another important change in this commit is that the "blockdev handle" is now opaque. Previously, consumers of the API would happily call routines directly from one of the 4 offsets. We can't do that any more. This makes the API more solid for future improvements. This change forced me to change a lot of things in fs, but overall, things are now simpler. No more `FS_PTR`: the "device handle" now holds the active pointer. Lots, lots of changes, but it also feels a lot cleaner and solid.
2019-06-04 11:53:02 -04:00
; the STDIN_SEEK port works by poking it twice. First poke is for high
; byte, second poke is for low one.
ld a, h
out (STDIN_SEEK), a
ld a, l
out (STDIN_SEEK), a
zasm: Read from and write to streams instead of memory
2019-05-09 15:36:03 -04:00
in a, (STDIO_PORT)
or a ; cp 0
jr z, .eof
cp a ; ensure z
ret
.eof:
call unsetZ
ret
emulPutC:
out (STDIO_PORT), a
ret
blockdev: make implementors "random access" This huge refactoring remove the Seek and Tell routine from blockdev implementation requirements and change GetC and PutC's API so that they take an address to read and write (through HL/DE) at each call. The "PTR" approach in blockdev implementation was very redundant from device to device and it made more sense to generalize. It's possible that future device aren't "random access", but we'll be able to add more device types later. Another important change in this commit is that the "blockdev handle" is now opaque. Previously, consumers of the API would happily call routines directly from one of the 4 offsets. We can't do that any more. This makes the API more solid for future improvements. This change forced me to change a lot of things in fs, but overall, things are now simpler. No more `FS_PTR`: the "device handle" now holds the active pointer. Lots, lots of changes, but it also feels a lot cleaner and solid.
2019-06-04 11:53:02 -04:00
fsdevGetC:
ld a, e
out (FS_SEEK_PORT), a
zasm: change ioRewind to ioSeek Will need it soon.
2019-05-15 13:41:56 -04:00
ld a, h
blockdev: make implementors "random access" This huge refactoring remove the Seek and Tell routine from blockdev implementation requirements and change GetC and PutC's API so that they take an address to read and write (through HL/DE) at each call. The "PTR" approach in blockdev implementation was very redundant from device to device and it made more sense to generalize. It's possible that future device aren't "random access", but we'll be able to add more device types later. Another important change in this commit is that the "blockdev handle" is now opaque. Previously, consumers of the API would happily call routines directly from one of the 4 offsets. We can't do that any more. This makes the API more solid for future improvements. This change forced me to change a lot of things in fs, but overall, things are now simpler. No more `FS_PTR`: the "device handle" now holds the active pointer. Lots, lots of changes, but it also feels a lot cleaner and solid.
2019-06-04 11:53:02 -04:00
out (FS_SEEK_PORT), a
zasm: change ioRewind to ioSeek Will need it soon.
2019-05-15 13:41:56 -04:00
ld a, l
blockdev: make implementors "random access" This huge refactoring remove the Seek and Tell routine from blockdev implementation requirements and change GetC and PutC's API so that they take an address to read and write (through HL/DE) at each call. The "PTR" approach in blockdev implementation was very redundant from device to device and it made more sense to generalize. It's possible that future device aren't "random access", but we'll be able to add more device types later. Another important change in this commit is that the "blockdev handle" is now opaque. Previously, consumers of the API would happily call routines directly from one of the 4 offsets. We can't do that any more. This makes the API more solid for future improvements. This change forced me to change a lot of things in fs, but overall, things are now simpler. No more `FS_PTR`: the "device handle" now holds the active pointer. Lots, lots of changes, but it also feels a lot cleaner and solid.
2019-06-04 11:53:02 -04:00
out (FS_SEEK_PORT), a
in a, (FS_SEEK_PORT)
or a
ret nz
zasm emul: hook fsdev in glue code
2019-05-16 13:23:23 -04:00
in a, (FS_DATA_PORT)
cp a ; ensure Z
ret
fsdevPutC:
push af
Make blockdev pointers 32 bits This allows us to break through the 64K limit for includes CFS in zasm, a limit we were dangerously close to breaking. In fact, this commit makes us go over that limit. Right in time!
2019-05-28 15:56:39 -04:00
ld a, e
out (FS_SEEK_PORT), a
zasm emul: hook fsdev in glue code
2019-05-16 13:23:23 -04:00
ld a, h
out (FS_SEEK_PORT), a
zasm: iiiiiiiincluuuuuuudes!!1!
2019-05-16 21:15:00 -04:00
ld a, l
out (FS_SEEK_PORT), a
zasm emul: hook fsdev in glue code
2019-05-16 13:23:23 -04:00
in a, (FS_SEEK_PORT)
blockdev: make implementors "random access" This huge refactoring remove the Seek and Tell routine from blockdev implementation requirements and change GetC and PutC's API so that they take an address to read and write (through HL/DE) at each call. The "PTR" approach in blockdev implementation was very redundant from device to device and it made more sense to generalize. It's possible that future device aren't "random access", but we'll be able to add more device types later. Another important change in this commit is that the "blockdev handle" is now opaque. Previously, consumers of the API would happily call routines directly from one of the 4 offsets. We can't do that any more. This makes the API more solid for future improvements. This change forced me to change a lot of things in fs, but overall, things are now simpler. No more `FS_PTR`: the "device handle" now holds the active pointer. Lots, lots of changes, but it also feels a lot cleaner and solid.
2019-06-04 11:53:02 -04:00
or a
jr nz, .error
zasm emul: hook fsdev in glue code
2019-05-16 13:23:23 -04:00
pop af
blockdev: make implementors "random access" This huge refactoring remove the Seek and Tell routine from blockdev implementation requirements and change GetC and PutC's API so that they take an address to read and write (through HL/DE) at each call. The "PTR" approach in blockdev implementation was very redundant from device to device and it made more sense to generalize. It's possible that future device aren't "random access", but we'll be able to add more device types later. Another important change in this commit is that the "blockdev handle" is now opaque. Previously, consumers of the API would happily call routines directly from one of the 4 offsets. We can't do that any more. This makes the API more solid for future improvements. This change forced me to change a lot of things in fs, but overall, things are now simpler. No more `FS_PTR`: the "device handle" now holds the active pointer. Lots, lots of changes, but it also feels a lot cleaner and solid.
2019-06-04 11:53:02 -04:00
out (FS_DATA_PORT), a
zasm emul: hook fsdev in glue code
2019-05-16 13:23:23 -04:00
ret
blockdev: make implementors "random access" This huge refactoring remove the Seek and Tell routine from blockdev implementation requirements and change GetC and PutC's API so that they take an address to read and write (through HL/DE) at each call. The "PTR" approach in blockdev implementation was very redundant from device to device and it made more sense to generalize. It's possible that future device aren't "random access", but we'll be able to add more device types later. Another important change in this commit is that the "blockdev handle" is now opaque. Previously, consumers of the API would happily call routines directly from one of the 4 offsets. We can't do that any more. This makes the API more solid for future improvements. This change forced me to change a lot of things in fs, but overall, things are now simpler. No more `FS_PTR`: the "device handle" now holds the active pointer. Lots, lots of changes, but it also feels a lot cleaner and solid.
2019-06-04 11:53:02 -04:00
.error:
pop af
jp unsetZ ; returns
zasm emul: hook fsdev in glue code
2019-05-16 13:23:23 -04:00
Reference in New Issue Copy Permalink