Linked by Thom Holwerda on Tue 10th Feb 2009 18:31 UTC
BeOS & Derivatives Back when it was becoming clear that the time of the BeOS had come and gone, enthusiasts immediately set up the OpenBeOS project, an attempt to recreate the Be operating system from scratch, using a MIT-like license. The project faced difficult odds, and numerous times progress seemed quite slow. Still, persistence pays off, and the first alpha release is drawing ever closer. We decided to take a look at where Haiku currently stands.
Thread beginning with comment 348366
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Netbooks
by NexusCrawler on Thu 12th Feb 2009 07:55 UTC in reply to "RE: Netbooks"
Member since:

Unfortunately, while the netbooks share "80%" of the same hardware, they also are all "20%" different. And there is a *lot* of models, with new models every month. In particular you want things like ACPI to work flawlessly, which is the kind of part to be typically in these 20% (depends on the motherboard and on the device buttons, and so on, I guess).

The other thing to change from one netbook to the other is the wireless card, which is the key to the "net"-book concept... And there is a lot of work to be done here in Haiku, no wireless stack at all for now. And I understood that the wireless stack wasn't a priority for the Alpha release, so...

To sum up it would be quite difficult to support all of them, especially the newest ones that no Haiku developper already own.

Besides, linux drivers cannot be "borrowed" to be used in Haiku. mmu_man explains in details (among other things) why they cannot (easily) port Linux drivers to Haiku in this very interesting post about the need for "open hardware":

Basically, Haiku is not Linux so you cannot simply "reuse" the drivers; additionnaly, Linux drivers tends to be a big mess for several reasons, meaning that it's hard to port them successfully to another OS.

So what's sure is that hardware is still a big issue, as for any "alternative" OS. Which is sad because yes netbooks would be an interesting target for Haiku because of their limited ressources and because of their eagerness for quick boot and responsiveness.

But who knows... ? For now, my EeePC 701 boots quickly Haiku and has sound and Ethernet. Basically it's wireless and ACPI that lacks. Which are both a big deal of work to implement, but let's be patient.

Reply Parent Score: 2

RE[3]: Netbooks
by phoudoin on Fri 13th Feb 2009 16:23 in reply to "RE[2]: Netbooks"
phoudoin Member since:

Basic (read Intel CA implementation) ACPI is there but isn't enabled by default yet.

Wireless support will comes, and the very few (wmb2200, iw2100, rt25xx, hfa384x aka Prism 2 & 3 ...) that are/were available for BeOS R5 should works fine under Haiku, at the cost of having to edit by hand a config file, which is not very beos/haiku/user friendl, we all confess that.

Today there is far less windows-only hardware than 10 years ago, thanks to Linux and BSD communities big efforts to bring hardware makers to more openess. Atheros opened its HAL. Intel opened pretty much all its hardware devices, even their GMA. AMD/ATI do it now too, Realtek were since long already, and so on. Except for very niche hardware markets and, what a surprise, nVidia, the list of device supported by alternative OSes is increasing. And more and more auxiliary chips are made by asian makers, whose business model is less based on closed documentation, most propably because they've grown by... looking to what and how others makers were doing stuffs.

The end result is it's less difficult to have access to some hardware documentation that before. And Haiku already benefits from it, which make its hardware support future less darker than it was in BeOS times...

Still, using an alternative operating system will never give you the everything is supported of the #1 OS.
That's why they call choice freedom. But no choice comes without alternatives solutions...

Reply Parent Score: 1