Haikuware News

This time/round I'm on top of things! Please send/comment any nomination (with reason), you have for our June Thank You Award.

Have you seen recent work done by a Haiku developer that you feel deserves recognition?? Let us know...

Well, my favourite way to check Haiku's latest commits is now down indefinitely. CIA.vc has been retired by the owner. It was a great service and provided FOSS projects, like Haiku, years of wonderful, stable, and free service. Cheers to the owner, developers and all those involved for providing us with that great tool all these years. The owner, by the way, has unselfishly offered the database and code up to a group or committee that's willing to continue or fork the project (with sensible restrictions).

So what now...? No more cute little CIA.vc bot notifying #Haiku IRC users of source changes to Haiku anymore!

*Update, it's back online!

We recently noticed Michael Lotz (mmlr) has been quite busy committing to Haiku lately. We thought an interview would be timely, and thank Michael for helping explain what he's been up to in such great detail! The interview:

#1 - We've noticed a flurry of commits from you recently regarding ACPI and IRQ tables/routing. Could you please explain if this will help close ticket #5, and help Haiku realize proposition #4 from Haiku's 'must have R1 features' poll? Also, perhaps translate into plain English what it is you've done? :)

What I've done is finish implementing IO-APIC support that I started implementing back in 2008. Back then I only implemented programming of the actual IO-APIC controller, but not the required mapping between PCIinterrupt pins and the IO-APIC inputs. While the IO-APIC basically worked since then, it wasn't usable at all because the essential information, i.e. what pins are physically connected to what inputs was simply missing.

A two week poll has decided that the $2002.09 gathered from an incompletely finished bounty (Wifi Encryption), and an expired bounty (TV Card Support) should be forwarded to Haiku Inc. to be put towards a work contract that will further Haiku's development (it was also interesting to note there was strong support to see Gobe Productive v3.0 on Haiku).