Linked by Thom Holwerda on Mon 20th Mar 2006 23:07 UTC, submitted by Tako Lansbergen
BeOS & Derivatives Studio33 has released part II [part I] in its series of articles looking at the current state of Haiku. "In the previous part I talked about the achievements of the Haiku Team since the project was first started, this time I will go deeper into the work that has been done lately and which parts need serious attention in the coming months." Screenshots o'plenty, boys and girls.
Thread beginning with comment 106222
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Re: Kernel, etc
by Maciek on Tue 21st Mar 2006 01:53 UTC in reply to "Re: Kernel, etc"
Member since:

Agreed, but a "wrapper" sub-system for Linux ethernet and PCI drivers (or other drivers, for that matter) would be a nice short-term solution. In fact, this has already been implemented for some 3COM cards -- check the lib directory:

Reply Parent Score: 2

RE[2]: Re: Kernel, etc
by Nathan O. on Tue 21st Mar 2006 02:22 in reply to "RE: Re: Kernel, etc"
Nathan O. Member since:

Isn't this how Syllable's drivers work?

Reply Parent Score: 1

RE[3]: Re: Kernel, etc
by Vanders on Tue 21st Mar 2006 08:01 in reply to "RE[2]: Re: Kernel, etc"
Vanders Member since:

Sort of. For network drivers and (currently) soundcard drivers, we generally port from Linux. For that small subset of devices the kernel APIs are close enough that it isn't too much work; you generally only need to tweak the way ethernet frames are pushed up and down the stack and re-write the PCI and logical device management. We do have a linux_compat.h system header for drivers, which is a small set of macros and typedefs to make life a little easier.

All of this ignores the fact that the Haiku/NewOS kernel isn't GPL though, which would make it tricky to use GPLd drivers as Syllable does.

Reply Parent Score: 3