As has been the case recently, the Activity Report is hereby combined with my Contract Report.
This report covers hrev55992 to hrev56087.
Just like the last few months, the usual Activity Report is hereby combined with my Contract Report.
This report covers hrev55917 to hrev55991.
Just like last month, the usual Activity Report is hereby combined with my Contract Report.
This report covers hrev55836 to hrev55916.
For a bit of a change this month, the usual Activity Report is hereby combined with my Contract Report. (Thanks to PulkoMandy for all his hard work writing the activity reports most other months, and for all the work he put into this one before turning it over to me for its completion. Now I get to write about myself in the third person!)
This report covers hrev55769 to hrev55835.
For the first time, most of the work I did as part of this contract was not in the month’s activity report aside from a passing reference, as nearly all of it took place outside the main Haiku source tree. So, here I detail it; and thanks once again to the generous donations of readers like you (thank you!).
Happy new year!
Note: this report covers changes only to the Haiku main git repository. There are many other things going on for Haiku outside that git repository. In recent big news, we have an X11 compatibility layer, and a running experimental Wine port. However, I cannot cover everything in these reports. Help welcome if you want to contribute to our website with news announcements for such items.
That being said, let’s see what’s going on in Haiku itself!
PulkoMandy has already written the activity report for this month, so now I am once again left to detail the work I have been doing thanks to the generous donations of readers like you (thank you!).
Hello there, it’s time for the monthly activity report!
This report covers hrev55609-hrev55687.
New architectures Kallisti5 fixed some minor problems with the PowerPC port to keep it building and simplify it a bit. Kallisti5 and waddlesplash also continued cleaning up the RISC-V sources and fixing various minor issues there.
David Karoly is making progress on the 32bit ARM port, using EFI as a boot method. The previous attempts for an ARM port used the linux style booting, where the firmware bootloader (usually uboot) only does the minimal hardware initialization, and then hands over complete control to the operating system.
Thanks in large part to the hard work by X512 and everyone developing on Haiku, our nightly RISCV64 images are now functional.
RISC-V marks Haiku’s first functional non-Intel/x86 port!
What is RISC-V? RISC-V is a modern, fully open CPU instruction set which can be implemented, customized, extended, and sold without royalties. Designs exist for a 32-bit, 64-bit, and even a 128-bit processor design.
You can emulate RISC-V in qemu, design your own CPU and synthesize it for an FPGA, or you can purchase a commercially built and designed computer with a RISC-V processor.
