Porting Linux drivers

Am I the only one who is fucking done with atheros 802.11 chipsets? OpenBSD, NetBSD, FreeBSD, Minix3 and Solaris 11 don't have support for those chipsets. And they're the only chipsets I can find around here. (Also no cash for another one).
How hard is to port a Linux driver to any of those platforms? I'm ready to write code.

hail satan

Libertas 88w8335 - JEW

Just install Linux.

>>4
I'm posting from Linux. But I usualy work with others operating systems too.

>>4
You think Linux supports anything?THINK AGAIN.
Linux doesn't support shit. ndiswrapper a shit.  ndiswapper is a broken piece of shit that doesn't work. Linus is devil. nvidia is pig

https://en.wikipedia.org/wiki/NDISwrapper
http://sourceforge.net/apps/mediawiki/ndiswrapper/index.php?title=Main_Page
http://sourceforge.net/projects/ndiswrapper/

And strange you say that, what specific device you have, lspci(8) and dmesg(8)?:
[i386,pc98,amd64,sparc64] The ath(4) driver supports all Atheros Cardbus and PCI cards, except those that are based on the AR5005VL chipset.
http://www.freebsd.org/cgi/man.cgi?query=ath&sektion=4&manpath=FreeBSD+9.1-RELEASE
http://atheros.com/support/

>>6
but linux supports atheros chips

>>8
Indeed, so those FreeBSD. Which is why we know >>1 is trolling.

s/those/does/

>>6
death to windows and mac os x

It's an atheros AR9170 USB device.

FreeBSD doesn't support it, but OpenBSD's otus driver does.

Should be very easy. All you're doing is changing the interface, and those are all *nix-style OSs. In fact I'll dare to say that if you're new to driver development it'll probably take you longer to get used to the build process than to write the code.

A network driver basically has 5 entry points:

* Init - load and configure the HW
* Dnit - shut down the HW
* Send - OS calls into driver to send packet
* Recv - driver calls into OS when packet received
* Misc - other nonessential stuff


I've ported FreeBSD and Linux network drivers to OS X. The bulk of the hard work (poking the HW in the right way) is done for you already, you just have to hook it up to the OS.

>>1
As a atheros 802.11 chip, I'm offended by that.

>>11
Solaris 4 evar!

>>16
More like Slowlaris amirite.

>>17
Maybe 10 years ago, but with ZFS and QFS if you need clustering, I wouldn't use anything else as a file server these days (except for maybe VMS).

>>14
Any books you'd recommend to get into driver development?

>>19
http://docs.oracle.com/cd/E19683-01/806-5222/index.html

>>22
nice dabz

>>21
fuck off fagshit