4 ms·
IIRC the Oberon-powered drone was running on ARM, so there are ARM codegens for at least some versions of Oberon. Edit: https://people.inf.ethz.ch/wirth/Oberon
by 082349872349872 6y ago
IIRC the Oberon-powered drone was running on ARM, so there are ARM codegens for at least some versions of Oberon.
Edit: https://people.inf.ethz.ch/wirth/Oberon/Oberon.ARM.Compiler.pdf https://people.inf.ethz.ch/wirth/Oberon/Oberon.ARM.Compiler....
(not that this is meant to detract from TFA, just to point out the possibility for someone to take another step.)
- johndoe0815 6y agoThanks for the link! Adapting the Project Oberon compiler code generation isn't that difficult, but the devil is in the details :). My student Rikke described some of the challenges porting Project Oberon to RISC-V in her project report (https://github.com/solbjorg/oberon-riscv/blob/master/report.pdf https://github.com/solbjorg/oberon-riscv/blob/master/report....). I assume that the most time-consuming task to get Project Oberon to run on ARM/Raspberry Pi would be to write device drivers for more complex devices, e.g. USB and Ethernet. These could be written in Oberon (which would be a considerable effort) or possibly be abstracted by using a bare-metal hypervisor that supports VirtIO device abstractions, e.g. Vmware ESXI. This way, one would only have to implement VirtIO drivers in Oberon, which is considerably less complex. Connecting a PS/2 keyboard and mouse instead of USB might also be an alternative, since drivers for PS/2 are far less complex: http://www.deater.net/weave/vmwprod/hardware/pi-ps2/ http://www.deater.net/weave/vmwprod/hardware/pi-ps2/