More if_ath churn coming your way!

[Adrian Chadd]

On 21 January 2011 01:26, Dmitry Kolosov <onyx at z-up.ru> wrote:

> ath1: <Atheros 9280> mem 0xff9b0000-0xff9bffff irq 23 at device 2.0 on pci5
> ath1 at pci0:5:2:0:        class=0x028000 card=0x3a781186 chip=0x0029168c
> rev=0x01 hdr=0x00
>    vendor     = 'Atheros Communications Inc.'
>    class      = network

I need to know the output in dmesg of the chipset MAC/PHY revisions.

> as AP (it's brand new PCI D-Link RangeBooster N™ 650 DWA-547 802.11n) and

> ath0: <Atheros 9285> mem 0xd7100000-0xd710ffff irq 17 at device 0.0 on pci6
> ath0 at pci0:6:0:0:        class=0x028000 card=0x30a117aa chip=0x002b168c
> rev=0x01 hdr=0x00
>    vendor     = 'Atheros Communications Inc.'
>    device     = 'Atheros AR9285 Wireless LAN 802.11 a/b/g/n Controller
> (AR928x)'
>    class      = network
>
> as a client (it's lenovo y550p laptop).

> All i can have now it's a OFDM/54Mbps mode 11g. Is it possible to have
> something faster? Also, atheros extensions, such as fast frames and turbo
> modes, not working ever. Any help is welcome.

Eventually, yes. As I said before, I have a local tree with
functioning, basic 11n HT/20 support. The driver needs further
attention before we can enable HT modes and have the chipsets have
even a remote hope of being stable and useful enough.

There's also quite a bit missing from my "basic 11n HT/20 support"
which doesn't even remotely work - eg legacy protection modes, making
sure HT/40 channel protection works, broken A-MPDU support (which
shouldn't be broken, that's another problem to fix) and rate control
module stuff. It was just enough for me to verify that actual TX/RX of
MCS rates worked (and it did, well enough.)

If someone can help me source an AR9285 NIC then I can also work on
that. Right now however, I'm just going to concentrate on the AR9160
and AR9220/AR9280 (same chipset, one being PCI and the other being
PCIe.)

As for turbo mode (and half/XR modes) and FF support - in ath9k, those
are all "deprecated". If you have access to older chips (so
AR5212/AR5213 and earlier) and would like to help debug this then
please pipe up.



Adrian