Atheros Linux wireless drivers#

This page documents allAtheros Communications Linux wireless drivers.

Contribution map#

We have aGoogle Drive spreadsheetwith graphs you can view. Several formats are available:

If you’d like to contribute please contact one of the device driver maintainers.

Shared modules#

Atheros drivers tend to follow a lineage of hardware families and asthey progress pick things up from one family or another and sometimeskeep things the same. So hardware or EEPROM layouts can share certaincharacteristics and the same code can be reused through differenthardware families.

Shared module for Atheros 802.11 drivers:

  • ath - code that is common amongst all hardware families

IRC#

For support and development for all drivers we use the#linux-wireless IRC channel on irc.freenode.net.

PCI / PCI-E / AHB Drivers#

Technology

Upstream driver

802.11abg

ath5k

802.11abgn

ath9k

802.11ac

ath10k

802.11ad

wil6210

USB Drivers#

Technology

Legacy driver

Upstream driver

802.11b

None

zd1201

802.11bg

zd1211

zd1211rw

802.11abg

None

ar5523

802.11abgn

otus /ar9170

carl9170 (carl9170.fw GPLv2)

802.11abgn

None

ath9k_htc

Mobile (SDIO & CF)#

  • ar6k - Non-upstream GPL mobile driver, as used by OpenMoko

  • ath6kl - Reference driver from Atheros for AR600x with cfg80211 support

Licensing#

To help other FOSS Operating Systems, when possible, Atheros licensestheir device drivers source code under a permissive license. Atherospicked theISC Licensedue to historical reasons, mainly that of the ath5k developers alsochoosing it to help share code between Linux and OpenBSD. Atherosfollows this tradition to further assist not only OpenBSD but also otherFOSS Operating Systems. There are a few exceptions to using the ISClicense on Atheros drivers, when in doubt consult the header of the filefor the respective license of the file.

As far as firmware is concerned Atheros does try to open source firmwarewhen possible with the first release being that ofar9170.fw. When not possible (lack of resources mainly) we do try towork with the community to see if this can be done through sidecommunity work, and only if not possible at all do we release firmwareas binary with a friendly standard redistributable license.