izaya/collapseos
1
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity
cd514e6cd6
collapseos/blk/812

16 lines
538 B
Plaintext
Raw Normal View History

pcat: move all find code in _find word It isn't used by low level boot code anymore, so it can go there.
2020-06-21 11:57:12 -04:00
VARIABLE lblexec VARIABLE lblnext
pcat: use a far jump to boot into the OS Unless I misunderstood, this is supposed to set CS. This would make all SREG have the same value. This allows us to remove BIN( offset from os.bin. I've tried booting to offset 0, but it didn't seem to work. Let's settle for 0x8000. 512kb of system RAM is way more than we need anyways.
2020-06-13 20:06:51 -04:00
H@ ORG !
pcat: add PSP checks in all native words Also, fix (roll) which wasn't properly implemented.
2020-06-21 14:07:02 -04:00
JMPn, 0 A,, ( 00, main ) 0 A, ( unused ) 0 A,, ( 04, BOOT )
0 A,, ( 06, uflw ) 0 A,, ( 08, LATEST )
pcat: begin organizing native words properly This port is taking shape!
2020-06-18 15:28:30 -04:00
0 A, 0 A, 0 A,, ( unused )
0 A, 0 A,, ( unused ) JMPn, 0 A,, ( 11, pushRS )
pcat: begin porting forth I'm not sure yet where I'm going, but I'm not going to build the 8086 port from the ground up like I did with the z80, that is, making is sustain itself and eventually merge its forth code with core words. That would be too much work which would then be thrown out (all those words I'll initially have to implement in asm which are already implemented in Forth). What I *think* I can do is build a mirror version of z80 boot code and cross-compile it from the z80. This means it has to follow z80 stable ABI. Nope, I'm not sure where I'm going...
2020-06-13 21:37:54 -04:00
JMPn, 0 A,, ( 14, popRS )
pcat: begin organizing native words properly This port is taking shape!
2020-06-18 15:28:30 -04:00
0 A, 0 A,, ( unused )
JMPn, 0 A,, ( 1a, next ) 0 A, 0 A,, ( unused )
0 A, 0 A, 0 A, 0 A, ( unused )
0 A, 0 A, 0 A, 0 A, ( unused )
0 A, 0 A,, ( unused )
0 A, 0 A,, 0 A, 0 A, ( unused )
pcat: begin porting forth I'm not sure yet where I'm going, but I'm not going to build the 8086 port from the ground up like I did with the z80, that is, making is sustain itself and eventually merge its forth code with core words. That would be too much work which would then be thrown out (all those words I'll initially have to implement in asm which are already implemented in Forth). What I *think* I can do is build a mirror version of z80 boot code and cross-compile it from the z80. This means it has to follow z80 stable ABI. Nope, I'm not sure where I'm going...
2020-06-13 21:37:54 -04:00
0 A, 0 A,, ( unused )
pcat: begin organizing native words properly This port is taking shape!
2020-06-18 15:28:30 -04:00
JMPn, 0 A,, ( 33, execute ) 0 A, 0 A, 0 A, 0 A,, ( unused )
Reference in New Issue Copy Permalink