One of these (the XHCI one) I do intend to investigate. The one with a kernel crash is an assert, I’m pretty sure, and only happens on debug builds, so it isn’t an issue on beta builds (though of course it should be fixed.)
The I/O stalls are indeed annoying but I don’t know if anyone has really had a lot of success investigating it. It’s not especially high on my priority list, but we’ll see, I guess.
@waddlesplash or @tqh, regarding Haiku on ARM64, I have a PineBook that I’m not using that I’d be happy to donate to one of you to help with the porting effort, if you want. I think I have their funky audio to USB serial cable too.
Interestingly I have a PinePhone from the start of the year here too not being used… I have the USB connector, keyboard, mouse so might also be a good candidate.
Fantastic news, that Waddlesplash is able to work full time on Haiku.
I am just a user who finds Haiku a joy to use.
I really like the serenity os developers vlog (which I watch from Haiku) and their attitude, which is that developers work on whatever they find fun.
Currently, Waddlesplash is the only paid developer, but if it goes well then I’m sure Haiku Inc. will definitely consider another paid developer - of course, that’s dependent on how many donations we get as well
Correct. Haiku, Inc. has been saving donation funds for ~5-10 years now to be able to hire a full time developer at a somewhat reasonable salary. It’s why we really wanted to target someone who had a history of contributing to Haiku. We wanted someone who could “hit the ground running” since these donation initial funds were so hard-fought to save.
One idea is if waddlesplash works out well and we attract more donation funds, we’ll be in a better place to continue paying full time positions into the future.
I am not interested in a contract job that will only last a few months. I have a stable long term job that pays well and gives me a reasonable amount of free time to work on Haiku and other projects. At the moment I do not want to leave it.
I just read through the list of hard tasks and if virtualization and sleep mode worked I would switch in a heartbeat. 3D acceleration is nice, but other things are more important IMHO.
If only Haiku could attract the support of a large company or a billionaire.
Working on documentation and associated dev tooling to lower the entry effort? (btw I have setup an OpenGrok instance dedicated to Haiku main repositories: haiku, buildtools, haikuwebkit)
In parallel maybe communicate on this doc and tooling effort, and on the progress of Web+ and any other app using HaikuWebkit?
Have coding sprints dedicated to Web+?