izaya/collapseos
1
0
Fork 0
mirror of https://github.com/hsoft/collapseos.git synced 2024-11-21 02:28:05 +11:00
Code Issues Releases Wiki Activity
888395d496
collapseos/recipes/sms/romasm/Makefile

21 lines
478 B
Makefile
Raw Normal View History

recipes/sms/romasm: first steps
2019-07-22 05:37:03 +10:00
ZASM = ../../../tools/zasm.sh
KERNEL = ../../../kernel
APPS = ../../../apps
recipes/sms/romasm: adjust ed/zasm offsets
2019-07-23 00:10:42 +10:00
.PHONY: all clean
all: os.sms
recipes/sms/romasm: first steps
2019-07-22 05:37:03 +10:00
Modify userspace .org and RAMSTART expectations Instead of expecting a `USER_CODE` symbol to be set, we expect `.org` to be set in all userspace glue code. This gives us more flexibility with regards to how we manage that. Moreover, instead of making `USER_RAMSTART` mandatory, we make it default to the end of the binary, which is adequate in a majority of cases. Will be useful for my upcoming mega-commit... :)
2019-11-16 02:33:13 +11:00
# -o value synced with offset in glue.asm
recipes/sms/romasm: first steps
2019-07-22 05:37:03 +10:00
ed.bin: $(APPS)/ed/glue.asm
Modify userspace .org and RAMSTART expectations Instead of expecting a `USER_CODE` symbol to be set, we expect `.org` to be set in all userspace glue code. This gives us more flexibility with regards to how we manage that. Moreover, instead of making `USER_RAMSTART` mandatory, we make it default to the end of the binary, which is adequate in a majority of cases. Will be useful for my upcoming mega-commit... :)
2019-11-16 02:33:13 +11:00
$(ZASM) -o 19 $(KERNEL) $(APPS) user.h < $< > $@
recipes/sms/romasm: first steps
2019-07-22 05:37:03 +10:00
Modify userspace .org and RAMSTART expectations Instead of expecting a `USER_CODE` symbol to be set, we expect `.org` to be set in all userspace glue code. This gives us more flexibility with regards to how we manage that. Moreover, instead of making `USER_RAMSTART` mandatory, we make it default to the end of the binary, which is adequate in a majority of cases. Will be useful for my upcoming mega-commit... :)
2019-11-16 02:33:13 +11:00
# -o value synced with offset in glue.asm
recipes/sms/romasm: first steps
2019-07-22 05:37:03 +10:00
zasm.bin: $(APPS)/zasm/glue.asm
Modify userspace .org and RAMSTART expectations Instead of expecting a `USER_CODE` symbol to be set, we expect `.org` to be set in all userspace glue code. This gives us more flexibility with regards to how we manage that. Moreover, instead of making `USER_RAMSTART` mandatory, we make it default to the end of the binary, which is adequate in a majority of cases. Will be useful for my upcoming mega-commit... :)
2019-11-16 02:33:13 +11:00
$(ZASM) -o 1d $(KERNEL) $(APPS) user.h < $< > $@
recipes/sms/romasm: first steps
2019-07-22 05:37:03 +10:00
os.sms: glue.asm ed.bin zasm.bin
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
$(ZASM) $(KERNEL) $(APPS) ed.bin zasm.bin < $< > $@
recipes/sms/romasm: first steps
2019-07-22 05:37:03 +10:00
recipes/sms/romasm: adjust ed/zasm offsets
2019-07-23 00:10:42 +10:00
clean:
rm -f os.sms ed.bin zasm.bin
Reference in New Issue Copy Permalink