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 106279
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Re: Kernel, etc
by Vanders on Tue 21st Mar 2006 08:01 UTC in reply to "RE[2]: Re: Kernel, etc"
Vanders
Member since:
2005-07-06

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

RE[4]: Re: Kernel, etc
by Jack Burton on Tue 21st Mar 2006 08:14 in reply to "RE[3]: Re: Kernel, etc"
Jack Burton Member since:
2005-07-06

"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."

Sorry, this doesn't make sense. We already have some GPLd drivers in our tree.

Reply Parent Score: 3

RE[5]: Re: Kernel, etc
by Vanders on Tue 21st Mar 2006 10:02 in reply to "RE[4]: Re: Kernel, etc"
Vanders Member since:
2005-07-06

I didn't say it was impossible, just tricky. It's a gray area of the GPL, and if the Syllable kernel was not under the GPL it isn't an area I'd want to deal with myself, personally. There isn't even a clear-cut consensus on which way around linking between the kernel and a driver occurs: does the driver link against the kernel, or does the kernel link against the driver?

Provided you're happy with your answers to those questions then that's fine. Linux drivers are an amazingly useful resource, so it's great that you're making the most of them.

Reply Parent Score: 3