linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@open-mesh.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: OpenWrt Development List <openwrt-devel@lists.openwrt.org>,
	Simon Wunderlich <simon@open-mesh.com>,
	"ath9k-devel@venema.h4ckr.net" <ath9k-devel@venema.h4ckr.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [OpenWrt-Devel] [ath9k-devel] ath9k: Deaf QCA9558 when setting rxchainmask
Date: Mon, 11 Nov 2013 10:36:52 +0100	[thread overview]
Message-ID: <2985619.kldLYNDlSX@bentobox> (raw)
In-Reply-To: <CAJ-VmombLQqJsN50nndqCioFEOy=9cp_-34onQnWnpMoX6360w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]

On Friday 08 November 2013 18:33:19 Adrian Chadd wrote:
> Hm, is the 0x5 chainmask triggering the ALT_CHAIN logic?

You are talking about ar9003_phy.c -> ar9003_hw_set_chain_masks? No, the 
device is 3x3 and ah->caps.tx_chainmask & ah->caps.rx_chainmask are 7 and not 
5. The AR_PHY_ANALOG_SWAP := AR_PHY_SWAP_ALT_CHAIN is only done when one of 
them would be 5. But I am not really sure what this register setting is really 
doing. Maybe you can explain it when you think it could be related. Thanks

> What are you trying to do? Control the receive antenna config, or the
> transmit antenna config?

I have a device which is using a QCA9558 3x3 and a AR93XX 3x3 device. Both are 
working fine with the proprietary atheros driver and a 2x2 device as client 
(Intel and Atheros). The used driver is a a binary blob of 9.5.3.15 
(Atheros/multi-bss). But the download rate (AP -> Client) is relative low when 
using ath9k and the QCA9558 for tx. It is quite good when using the AR93XX.

The bad TX seems to be related to the low ewma prop for MCS14/15 in an 1-4.5m 
test (HT20). One idea was to test the different antennas to check whether 
there is some kind of antenna (selection) related problem. Unfortunatelly, 
this test only caused the problem mentioned in this thread.

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2013-11-11  9:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06 15:04 ath9k: Deaf QCA9558 when setting rxchainmask Sven Eckelmann
2013-11-09  0:32 ` [ath9k-devel] " Julius Schulz-Zander
2013-11-09  2:33   ` [OpenWrt-Devel] " Adrian Chadd
2013-11-11  8:33     ` [ath9k-devel] [OpenWrt-Devel] ath9k: Deaf " Alex Hacker
2013-11-11  9:36     ` Sven Eckelmann [this message]
2013-11-11 13:58       ` [OpenWrt-Devel] [ath9k-devel] ath9k: Deaf QCA9558 " Sujith Manoharan
2013-11-12  7:12         ` [ath9k-devel] [OpenWrt-Devel] " Alex Hacker
2013-11-14  8:39           ` Sujith Manoharan
2013-11-18 13:00         ` Matthias May
2013-11-18 13:12           ` Sujith Manoharan
2013-11-18 13:36             ` Matthias May
2013-11-18 15:05               ` Sujith Manoharan
2013-11-18 14:52           ` Sujith Manoharan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2985619.kldLYNDlSX@bentobox \
    --to=sven@open-mesh.com \
    --cc=adrian@freebsd.org \
    --cc=ath9k-devel@venema.h4ckr.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=openwrt-devel@lists.openwrt.org \
    --cc=simon@open-mesh.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).