From mboxrd@z Thu Jan  1 00:00:00 1970
From: Adrian Chadd <adrian@freebsd.org>
Date: Thu, 22 Jan 2015 11:54:22 -0800
Subject: [ath9k-devel] AR9103(AR9132) Antenna diversity
In-Reply-To: <54C09EC9.1070906@ruhr-uni-bochum.de>
References: <54BFB74F.9060100@ruhr-uni-bochum.de>
	<CAJ-Vmo=ExP84qDt4dVDTagD5X2ZHLp7fGO0DXFvvK7xNs30few@mail.gmail.com>
	<54C09EC9.1070906@ruhr-uni-bochum.de>
Message-ID: <CAJ-VmonKBQx2edXYhSywdn9XAkx3SrQzprkK=e9TPWpQxr1A6g@mail.gmail.com>
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

It's already doing MIMO diversity. If you have a chainmask that has 2
or more antennas enabled it already is doing it.

I think that variable is slow antenna diversity, not MIMO diversity.

It's configured with a chainmask of 0x7, so yes, I think it's fine.


-adrian


On 21 January 2015 at 22:55, Heiko Lechner
<Heiko.Lechner@ruhr-uni-bochum.de> wrote:
> Hi!
>
> Hmm, when I cat
> "/sys/kernel/debug/ieee80211/phy*/ath9k/antenna_diversity" it says
> "Antenna Diversity Combining is disabled"
>
> And here is the output from iw list (all three antennas are available
> and configured -> 0x7):
>
> ***
> Wiphy phy0
>         max # scan SSIDs: 4
>         max scan IEs length: 2257 bytes
>         Fragmentation threshold: 784
>         RTS threshold: 534
>         Retry short limit: 7
>         Retry long limit: 4
>         Coverage class: 1 (up to 450m)
>         Device supports AP-side u-APSD.
>         Device supports T-DLS.
>         Available Antennas: TX 0x7 RX 0x7
>         Configured Antennas: TX 0x7 RX 0x7
>         Supported interface modes:
>                  * IBSS
>                  * managed
>                  * AP
>                  * AP/VLAN
>                  * WDS
>                  * monitor
>                  * mesh point
>                  * P2P-client
>                  * P2P-GO
>         Band 1:
>                 Capabilities: 0x104e
>                         HT20/HT40
>                         SM Power Save disabled
>                         RX HT40 SGI
>                         No RX STBC
>                         Max AMSDU length: 3839 bytes
>                         DSSS/CCK HT40
>                 Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>                 Minimum RX AMPDU time spacing: 8 usec (0x06)
>                 HT TX/RX MCS rate indexes supported: 0-15
>                 Frequencies:
>                         * 2412 MHz [1] (20.0 dBm)
>                         * 2417 MHz [2] (20.0 dBm)
>                         * 2422 MHz [3] (20.0 dBm)
>                         * 2427 MHz [4] (20.0 dBm)
>                         * 2432 MHz [5] (20.0 dBm)
>                         * 2437 MHz [6] (20.0 dBm)
>                         * 2442 MHz [7] (20.0 dBm)
>                         * 2447 MHz [8] (20.0 dBm)
>                         * 2452 MHz [9] (20.0 dBm)
>                         * 2457 MHz [10] (20.0 dBm)
>                         * 2462 MHz [11] (20.0 dBm)
>                         * 2467 MHz [12] (20.0 dBm)
>                         * 2472 MHz [13] (20.0 dBm)
>                         * 2484 MHz [14] (disabled)
>         valid interface combinations:
>                  * #{ managed } <= 2048, #{ AP, mesh point } <= 8, #{
> P2P-client, P2P-GO } <= 1, #{ IBSS } <= 1,
>                    total <= 2048, #channels <= 1, STA/AP BI must match
>                  * #{ WDS } <= 2048,
>                    total <= 2048, #channels <= 1, STA/AP BI must match
>                  * #{ IBSS, AP, mesh point } <= 1,
>                    total <= 1, #channels <= 1, STA/AP BI must match,
> radar detect widths: { 20 MHz (no HT), 20 MHz }
>
>         HT Capability overrides:
>                  * MCS: ff ff ff ff ff ff ff ff ff ff
>                  * maximum A-MSDU length
>                  * supported channel width
>                  * short GI for 40 MHz
>                  * max A-MPDU length exponent
>                  * min MPDU start spacing
> ***
>
> Is that alright?
>
> TIA,
> Heiko.
>
>
> Am 21.01.2015 um 23:45 schrieb Adrian Chadd:
>> Hi,
>>
>> It's a MIMO chip, so it already is doing antenna diversity by MIMO combining.
>>
>>
>> -a
>>
>>
>> On 21 January 2015 at 06:27, Heiko Lechner
>> <Heiko.Lechner@ruhr-uni-bochum.de> wrote:
>>> Hi there!
>>>
>>> I have a question about ath9k and AR9103(AR9132):
>>> is antenna diversity available for that chipset?
>>>
>>> TIA,
>>> Heiko
>>> _______________________________________________
>>> ath9k-devel mailing list
>>> ath9k-devel at lists.ath9k.org
>>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel