From: Felix Fietkau <nbd@openwrt.org>
To: Daniel Smith <viscous.liquid@gmail.com>
Cc: linux-wireless@vger.kernel.org,
Felix Fietkau <public-nbd-p3rKhJxN3npAfugRpC6u6w@lo.gmane.org>
Subject: Re: [PATCH v13 5/5] ath9k: implement .get_antenna and .set_antenna
Date: Thu, 06 Oct 2011 00:43:25 +0200 [thread overview]
Message-ID: <4E8CDD8D.7010607@openwrt.org> (raw)
In-Reply-To: <4E8C9D53.1080307@gmail.com>
On 2011-10-05 8:09 PM, Daniel Smith wrote:
> On 9/2/2011 7:40 PM, Felix Fietkau wrote:
>> On MIMO chips this can be used to enable/disable hardware chains, ensuring
>> that the MCS information is updated accordingly.
>> On non-MIMO chips with rx diversity (e.g. 9285), this configures the rx
>> input antenna.
>
> I have been working with this patch as I needed the ability to select
> the rx chain/antenna on an AR9820.. A problem I have ran into is that
> regardless of what I set the antenna chain to, the radiotap header
> always reports antenna 1. I know this originates from the rx status
> descriptor, but is this really what should be used to report the antenna
> when using chains to select the antenna?
Typically all receive chains are used simultaneously when receiving
packets, and the antenna field in the rx status is meaningless. I'm
currently working on a patch that makes per-chain rx signal strength
available in the status info and puts it in the station info available
via nl80211.
- Felix
prev parent reply other threads:[~2011-10-05 22:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 23:40 [PATCH v13 1/5] ath9k: eliminate common->{rx,tx}_chainmask Felix Fietkau
2011-09-02 23:40 ` [PATCH v13 2/5] ath9k: move a few functions around Felix Fietkau
2011-09-02 23:40 ` [PATCH v13 3/5] ath9k: always call ath_reset from workqueue context Felix Fietkau
2011-09-02 23:40 ` [PATCH v13 4/5] ath9k: merge reset related functions Felix Fietkau
2011-09-02 23:40 ` [PATCH v13 5/5] ath9k: implement .get_antenna and .set_antenna Felix Fietkau
2011-10-05 18:09 ` Daniel Smith
2011-10-05 22:43 ` Felix Fietkau [this message]
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=4E8CDD8D.7010607@openwrt.org \
--to=nbd@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=public-nbd-p3rKhJxN3npAfugRpC6u6w@lo.gmane.org \
--cc=viscous.liquid@gmail.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).