This article is the second in a series of whitepapers on using the new Linux 2.6 kernel by William von Hagen of TimeSys. von Hagen’s whitepapers place special emphasis on the primary issues in migrating existing drivers, applications, and embedded Linux deployments to a Linux distribution based on the 2.6 kernel.
Migrating device drivers to Linux kernel 2.6
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
Also, you may want to read LWN’s long, in-depth article series about porting drivers to 2.6: http://lwn.net/Articles/driver-porting/
I wish damn RealTek would open all the code for their 8180 wireless chipset. Dmesg tells me that the kernel panic is happening in their “private part”, ala Nvidia style
I agree, I come here for OS news not slashdot.
From OSNews’ FAQ:
8. OSNews is not just about operating systems. We are reporting on other technology news, on development issues and articles, hardware, and if are short on news, we might kick in some sci-fi movie news or other stuff we might find cool. This is normal. We do OSNews for fun/hobby, so it has to be fun for us too. Comments like “this article is not OS news” will end you up get flamed.
I just can’t understand why people prefer to spend time whinning about an article instead of just clicking the good old “Back” button on the browser and go on.
i agree, i’ve asked and they may be considerring. i also asked that if they were not happy releasing the spec & source etc. can they at least keep up with the kernel & gcc releases + use the standard iwconfig command set. iwpriv is an arse in that you cannot use the gui’s etc that distros normally use – then you get locked into the non-standard way each distro has in doing things. please email them too and _politely_ ask yourself, don’t abuse them – just ask as one day it might work.