Is it possible to focus on a small amount of fully functinonal machines compatible with Haiku?

[daniel0366]

Would anyone be interested in, or already own this x86 SBC?

Radxa X4

[lelldorin]

@dcatt

That’s great and all but it ultimately needs to be discoverable on the project website. Maybe such a reference already exists and I have failed to discover it. Would be great if the project itself hosted such a list.

I wouldn’t mind having our hardware database listed on the haiku site. Or is it already available on community sites? I couldn’t find it right now.

[lelldorin]

@donn

But when you want to get a laptop and be sure it will work? If there’s a solid answer for that, I think it would be a good thing for the front Haiku page. That isn’t going to be out of date a month after it’s posted. If there isn’t that solid of an answer, then that’s what I’m talking about – maybe there’s a way to get something like that going.

I’m wondering how this should be implemented. Conversely, this would mean that all developers working on the system (drivers, libraries, etc.) would have to use the same machine for this to even make sense. However, Haiku is an open source project, and no one makes money from it, and the developers do everything in their “free time.” Besides, this also involves costs.

[lelldorin]

@ubu

Maybe we could have a list of recommended machines, sorted by year of built/introduction.

Maybe in wiki form, maybe crosslinked with besly hardware

I think it would definitely be useful to make the existence of our database visible and to keep it prominent in the forum so that people can see that we have it and that we’re taking user experiences into account.

Suggestion:

• Permanent entry for the besly hardware database on the website’s main page
• Always make the “Hardware Complete Systems” entry visible as a favorite in the forum so that this entry is continually seen and thus kept up-to-date.
• Maybe we can create an area on our database page where the hardware that is fully compatible is displayed (@lorglas)?

But it must also be considered that even if you say that notebook xy runs with such and such names, this can also have changes in the hardware, because there are also differences in the use of hardware components within a name series

[michel]

@lelldorin

I’m wondering how this should be implemented. Conversely, this would mean that all developers working on the system (drivers, libraries, etc.) would have to use the same machine for this to even make sense

Not really. ONE developer would have to have that machine to test and certify that it works. Then, nothing gets committed to the repo until Joe has tested it.