From: Simon Wunderlich <simon@open-mesh.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] QCA9558 problems for MCS 14/15
Date: Fri, 22 Nov 2013 16:57:04 +0100 [thread overview]
Message-ID: <201311221657.04880.simon@open-mesh.com> (raw)
Hello ath9k-devs,
we have an issue with a new QCA9558 SoC based board (Rev 0, a 3x3 2.4G board).
We were doing performance tests with various 2-stream 802.11n clients, but
appearently the high MCS rates 14 and 15 can not be used reliably with ath9k -
rc_stats show that transmission fail most of the time, and the connected
clients don't receive them as well. The original firmware with an Atheros 9.5
driver (9.5.3.15) does not show that behaviour and works fine. Therefore we
assume that there is something missing/wrong in ath9k. Iperf tests in HT20
showed 60 Mbit/s with ath9k and 80 Mbit/s with the original firmware (distance
1-3 meter).
We have been in contact with Sujith who kindly helped us and checked for
updates, thanks to his work some patches made it to the mailing list. However
the problem is not yet solved on our AP, and while we are still working on it,
I'd like to get your opinions as well.
What we did so far: We have tested Intel and Atheros clients (2-stream) which
work fine with other Access Points. We have tested various driver versions
(OpenWRT trunk, OpenWRT with manually backported drivers from latest wireless-
testing, including Sujiths latest patches). We have also tried different
hardware samples. We experience the described problem in all of these
combinations, ath9k/minstrel tops out at MCS12/13 maximum (manual setting
MCS15 fails as well).
Any ideas and suggestions (also how to debug the problem further) would be
very much appreciated.
Thank you,
Simon
next reply other threads:[~2013-11-22 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 15:57 Simon Wunderlich [this message]
2013-11-23 9:37 ` [ath9k-devel] QCA9558 problems for MCS 14/15 Thomas Hühn
2013-11-25 15:10 ` Sven Eckelmann
2013-11-29 17:59 ` Simon Wunderlich
2013-11-30 0:51 ` Adrian Chadd
2013-11-30 16:22 ` Simon Wunderlich
2013-11-30 19:27 ` Adrian Chadd
2013-12-02 11:45 ` Simon Wunderlich
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=201311221657.04880.simon@open-mesh.com \
--to=simon@open-mesh.com \
--cc=ath9k-devel@lists.ath9k.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.