Here’s the update for week 14 of work on the Haiku ARM port. I was travelling for a good part of week 13 and thus couldn’t get much work done during the time.
TL;DR - The problems of kernel overwriting the loader code and the exceptions when setting up framebuffer have been temporarily solved. The framebuffer related code has been disabled for now and the entire memory map moved to a higher address(when FDT support is implemented, a lot of these problems probably won’t arise). Currently, a fault is raised when the kernel attempts to obtain the same lock twice, which drops to KDL.
Here’s a quick update for week #12.
TL;DR - The decompression process fails because the archive is present in a location that isn’t mapped by the MMU and subsequently allocated for the zlib output stream. No solutions have been discussed yet. It shouldn’t be long till the kernel is running hopefully :).
Here’s the update for week #11.
TL;DR - Haiku faults when trying to find the floppyboot archive present in stage2 loader. There seems to be a difference in few offsets/sizes, which causes different bytes to be read every time the loader tries to detect the archive.
Here’s the update for week #10. Sorry about the delay in posting there - I had some issues logging into the website over past few days.
TL;DR - MMU is enabled and now working!
The bootstrap-mmc target is now finally available! What this means is that you can follow all instructions in 
Here is an update on the port.
Just like week 6, this is another short update.
I’ve been working on creating a bootstrap-mmc target for the build system. The current issues I’m facing are
- Downloading MLO and u-boot fails and thus build fails since jam doesn’t know how to create those targets otherwise. I managed to fix this but apparently, the fix breaks the current build system so I need to modify the fix such that it doesn’t break the build system.
- Copying the bootstrap image as the second partition of the MMC image. I planned to use dd since it works fine and probably works fine on Linux and BSDs but dd requires a size to be specified, which is slightly tricky to compute in jam. The obvious solution of using cat doesn’t seem to work - the resultant size of MMC is much higher than expected.
I hope to add the bootstrap-mmc target for jam within this week which would make it much easier for anyone to build the image.