Linked by Thom Holwerda on Thu 1st Feb 2007 14:41 UTC, submitted by Oliver
Thread beginning with comment 208270
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
More News »
Sponsored Links



Member since:
2005-07-06
This looks similiar to the sort of thing we do on Syllable. Providing an API that is "close enough" to Linux has worked very well for us, at least. We can port things like ethernet and USB drivers very quickly, with the minimum amount of changes and maintain similiar levels of hardware compatability as the original driver.
Tracking the ever-changing Linux API hasn't been too bad. It helps if you're only dealing with a limited number of driver classes, because that obviously limits the size of the APIs you need to concern yourself with. The fundemental APIs (E.g. Stuff like kmalloc()) are very stable, so there are generally no problems there.