collapseos/recipes/rc2014/ps2/Makefile

PROGNAME = ps2ctl
AVRDUDEMCU ?= t45
AVRDUDEARGS ?= -c usbtiny -P usb 
TARGETS = $(PROGNAME).hex os.bin
ZASM = ../../../tools/zasm.sh
KERNEL = ../../../kernel
APPS = ../../../apps

# Rules

.PHONY: send all clean

all: $(TARGETS)
	@echo Done!

send: $(PROGNAME).hex
	avrdude $(AVRDUDEARGS) -p $(AVRDUDEMCU) -U flash:w:$<

$(PROGNAME).hex: $(PROGNAME).asm
	avra -o $@ $<

os.bin: glue.asm
	$(ZASM) $(KERNEL) $(APPS) < $< > $@

clean:
	rm -f $(TARGETS) *.eep.hex *.obj os.bin
recipes/rc2014/pc2: new recipe (WIP) 2019-06-28 22:54:57 -04:00			`PROGNAME = ps2ctl`
			`AVRDUDEMCU ?= t45`
			`AVRDUDEARGS ?= -c usbtiny -P usb`
recipes/rc2014/ps2: drive a shell with ps/2 kbd! 2019-06-29 14:25:18 -04:00			`TARGETS = $(PROGNAME).hex os.bin`
			`ZASM = ../../../tools/zasm.sh`
			`KERNEL = ../../../kernel`
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			`APPS = ../../../apps`
recipes/rc2014/pc2: new recipe (WIP) 2019-06-28 22:54:57 -04:00
			`# Rules`

			`.PHONY: send all clean`

			`all: $(TARGETS)`
			`@echo Done!`

			`send: $(PROGNAME).hex`
			`avrdude $(AVRDUDEARGS) -p $(AVRDUDEMCU) -U flash:w:$<`

			`$(PROGNAME).hex: $(PROGNAME).asm`
			`avra -o $@ $<`

recipes/rc2014/ps2: drive a shell with ps/2 kbd! 2019-06-29 14:25:18 -04:00			`os.bin: glue.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			`$(ZASM) $(KERNEL) $(APPS) < $< > $@`
recipes/rc2014/pc2: new recipe (WIP) 2019-06-28 22:54:57 -04:00
recipes/rc2014/ps2: drive a shell with ps/2 kbd! 2019-06-29 14:25:18 -04:00			`clean:`
			`rm -f $(TARGETS) .eep.hex .obj os.bin`