Atheros Releases Free Linux Driver For Its 802.11n Devices
mcgrof writes "Atheros has released a shiny new Atheros driver for all their 11n devices aimed for inclusion in the Linux kernel. This new driver has no proprietary HAL and is licensed under the ISC license, so the BSD community should be able to benefit as well. Note: no firmware required!"
for my AR5212
Geology - it's not rocket science; it's rock science
No more weighing the lesser of two evils, I can cross off all the laptops with Broadcom chips and narrow the playing field.
I wasted untold hours with the b43 driver and routinely get bitten when I upgrade kernels and madwifi falls apart and I can't load the new source because it fell apart. Wireless hardware that just works will be a relief.
That's why I bought the Dell Inspiron 1420n. I KNEW that everything would work under Linux.
When I finally upgrade my home's network, you can bet I'll be going with Atheros.
ath9k - Atheros unveils free Linux driver for its 802.11n devices Â
We are pleased to announce Atheros has released ath9k to the community. This driver is aimed at inclusion to the Linux kernel and supports all Atheros IEEE 802.11n devices. This represents a major shift in terms of support from Atheros with respect to Linux. The ath9k driver comes shortly after Atheros hired two key Linux wireless developers -- Luis Rodriguez and Jouni Malinen.
We have been informed Atheros does plan to add access point support to ath9k and to work with the community to enhance and complete access point support in the Linux kernel. It is understood there is plenty of work required on the wireless stack to complete full access point support. Jouni Malinen will help drive this process within the community while Luis helps enhance regulatory compliance in the Linux kernel.
We are eager to work with Atheros with ath9k and applaud their efforts for properly supporting Linux.
The ath9k driver includes supports for the following chipsets:
* AR5418+AR5133
* AR5416+AR5133
* AR5416+AR2133
* AR9160
* AR9280
* AR9281
http://www.ubnt.com/products/sr71a.php
And it's been in the kernel for at least one major release. ath5k is the name
I have a few of these devices and they work pretty well with the driver. They don't do access point mode yet, but that will come soon.
The driver itself is open source but depends on the proprietary Hardware Abstraction Layer (HAL) that is available in binary form only.
Breakfast served all day!
After struggling with Zydas ZD1211, various Broadcrap cards and two TI ACX cards, I tried using atheros. After that, I ordered 10 minipci cards to use in my various devices (NAS, Laptop, routers etc.). And by the look of things, I'm never going back ;)
I just get Intel laptops with Centrino...works perfectly.
"You can either have software quality or you can have pointer arithmetic, but you cannot have both at the same time."
Yes but, due to the physical differences (MIMO, etc) the software->hardware interface is likely significantly different.
The specifications for 802.11n are mostly compatible with a/b/g, but what you are saying is, to use a car analogy, putting a truck transmission into a coup. Sure, they do the same thing, but they are still completely different 'under the hood'.
Another example: a CD and DVD do the same thing, a DVD is backwards compatible, and a DVD does more. But a DVD is not a CD, and you cannot interface with the DVD the same way as you do a CD. (this is usually abstracted away from you, by the chips in the actual drive, but it is still true)
For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
From the MadWifi homepage:
The driver itself is open source but depends on the proprietary Hardware Abstraction Layer (HAL) that is available in binary form only.
That's for the madwifi driver.
...yes, they're all written by the madwifi group...
We're talking about the ath9k driver.
There's also ath5k, that does not uses HAL.
"I was gratified to be able to answer promptly, and I did. I said I didn't know." -- Mark Twain
Ya, except if you go READ those drivers, you will find they violate GPL in several places (notably copying/stealing 2.6 kernel code, ripping off the copyright notice and then plastering (C) Broadcom all over it). Shrug.