gilbraltar
gilbraltar copied to clipboard
MirageOS on RPi4
Currently, our unikernel is available at `0x0` into our image and we specify to the firmware that we use the _old_ memory layout with `kernel_old=1`. However, from an @palainp's advise,...
a `mirage-gilbraltar`, as a `mirage-solo5` should exists and we should extend targets inside the `mirage/mirage` project. However, I think we must implement _yield_ before to be able to launch `lwt`.
The problem is the same as `ocaml-freestanding` when `ocaml-ci` wants to run `dune` and ... this project is just a spaguetti of `Makefile`...
So, any idea what the other cores should be doing while one is executing one MirageOS unikernel? One idea would be to have one unikernel per CPU - thus a...
GPIO is directly available from the kernel without a huge ceremony. We should add a support of it in Gilbraltar. It should not be complex.