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. The Linux kernel is designed to work this way, but in our case, we actually rely a bit more
on the firmware, to run our stage 2 bootloader which provides an user friendly boot menu.
Hello there, it’s time for the monthly activity report!
This report covers hrev55452-hrev55608.
Kernel
Waddlesplash made the kernel always build with gcc8, even on 32bit systems. It was built with gcc2
until now, but it was not possible to use BeOS drivers anymore since the introduction of SMAP and
other features, which led to slight changes in the driver ABI. No one complained, so there is no
reason to preserve BeOS driver compatibility further. This should result in performance improvements
for 32bit installations, as the new compiler is much better at optimizing code. And it will allow
kernel developers to use more modern C++ features.
I’ve been wanting to publicly comment on Lenovo’s statement on Linux support for a while, as there’s much to say about it, and my failing attempt at finding a suitable replacement for my venerable T510 gave me an excuse to document my love-hate relationship with Lenovo all at once.
This is of course my own personal views and ideas, and does not reflect the Haiku project’s position on the topic, nor that of Haiku, Inc. But I feel they deserve to be brought here due to history and the direct and indirect effect it might have had on the project, including previous failed attempts at commercial applications using it.
While Lenovo is still above many other manufacturers on some aspects, and on others domains, well, nobody does any better anyway, they purport to perpetuating the IBM legacy, so I think (sic) they should be held up to the standard they claim to follow. Yet the discussion about repair and documentation pertains to almost every vendor.
Hello there, it’s time for the monthly activity report!
This report covers hrev55343-hrev55451.
app_server
PulkoMandy reworked the way the screen is taken out of DPMS power saving mode when app_server
first starts. This should have no consequences on most hardware since the screen will normally
already be up during the boot screen, but the way it was implemented led to some confusion in
existing drivers, as we tried to turn the screen on before the driver had a chance to set a video
mode on its own. So this code is moved a little later in the setup sequence.
Hi there, let’s do another activity report! You may have noticed that there were a lot of news
since the previous one, but here’s a recap in case you missed it: a new beta release, the
celebration of the 20th birthday of the Haiku project, the end of Google Summer of Code (final
evaluations are being filled in as I write this), and also news from the promotion team which was
re-launched a few months ago and is working on various things (read their own report for more details).
Hey everyone! Since the GSoC period is nearing its end therefore here’s the final report on my GSoC project Coding Style Checker Bot.
Project Description:
Haiku has its own coding guidelines which describe how the code should be formatted. There is a tool (haiku-format tool) for reformatting or checking if code follows these guidelines, but it has to be compiled on the developer machine and then run manually. My project was to create a Coding Style Checker bot that runs haiku-review tool on files submitted as a patchset in our code review system and posts the report in the patchset comments.
GSoC’s coming to an end, so it’s time for a final update: An overview of
what I’ve been working on this summer.
Project
My project was to “modernize” and write a libpurple add-on for
Caya, a multi-protocol chat program.
Ultimately, I hard-forked Caya into
Chat-O-Matic at the request of a
previous maintainer― with the name being suggested by win8linux. :-)
“Modernization” here means three things: Allowing multiple accounts in use
at once, re-orienting the program to support multi-user chats, and giving
add-ons some more flexibility.
