From mboxrd@z Thu Jan  1 00:00:00 1970
From: Pavel Roskin <proski@gnu.org>
Date: Thu, 01 Apr 2010 22:35:26 -0400
Subject: [ath9k-devel] No 80211n possible with AR9220?
In-Reply-To: <4BB218EB.2000301@googlemail.com>
References: <4BB218EB.2000301@googlemail.com>
Message-ID: <1270175726.11685.12.camel@mj>
List-Id: <ath9k-devel.lists.ath9k.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: ath9k-devel@lists.ath9k.org

On Tue, 2010-03-30 at 17:29 +0200, Dennis Borgmann wrote:

> # iw dev wlan1 link
> Connected to 00:0e:8e:24:52:2f (on wlan1)
>     SSID: testsalat
>     freq: 2462
>     RX: 40496 bytes (404 packets)
>     TX: 3046 bytes (38 packets)
>     signal: -48 dBm
>     tx bitrate: 1.0 MBit/s

I tried AR9220 on the AP side and AR9280 on the station side.
Everything worked fine with 802.11n.  That's what I get on the client:

# iw dev wlan1 link
Connected to 00:26:5a:c2:4c:3d (on wlan1)
        SSID: mike2
        freq: 2462
        RX: 111244 bytes (629 packets)
        TX: 20186 bytes (176 packets)
        signal: -23 dBm
        tx bitrate: 117.0 MBit/s MCS 14

I'm using the current linux-wireless on both sides, so that may be the
reason.  I tried channels 6 and 11.  I tried no encryption and WPA2 with
CCMP.

I saw the bitrate fall to 1 Mbps if there is no traffic, but it would
immediately return to a high value once I start pinging the AP.

-- 
Regards,
Pavel Roskin