From: Robert Meschke <r_meschke@yahoo.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Antenna Configuration
Date: Mon, 13 Sep 2010 18:30:57 +0200 [thread overview]
Message-ID: <4C8E51C1.4010803@yahoo.de> (raw)
Hi Adrian,
look at the main.c of ath9k.
/*
* Update tx/rx chainmask. For legacy association,
* hard code chainmask to 1x1, for 11n association, use
* the chainmask configuration, for bt coexistence, use
* the chainmask configuration even in legacy mode.
*/
void ath_update_chainmask(struct ath_softc *sc, int is_ht)
{
struct ath_hw *ah = sc->sc_ah;
struct ath_common *common = ath9k_hw_common(ah);
if ((sc->sc_flags & SC_OP_SCANNING) || is_ht ||
(ah->btcoex_hw.scheme != ATH_BTCOEX_CFG_NONE)) {
common->tx_chainmask = ah->caps.tx_chainmask;
common->rx_chainmask = ah->caps.rx_chainmask;
} else {
common->tx_chainmask = 1;
common->rx_chainmask = 1;
}
ath_print(common, ATH_DBG_CONFIG,
"tx chmask: %d, rx chmask: %d\n",
common->tx_chainmask,
common->rx_chainmask);
}
This function is called on every channel change. If there is no 11n mode
1x1 is used (when no bt coexistence is used) -> always chain0 is used.
So i think that antenna diversity is impossible in legacy mode!? with no
bt coexictence. I don't know the term bt coexistence (Bluetooth -
coexictence!?)
My patch only overides the capability field. I don't touch this
function. So I think my patch can only work well in 11n mode.
Btw. If you setup 2x2 on AR9160 you will use chain0 an chain1. I got
strange behaviour, when I tried to use for example chain 0 and chain2
Robert
next reply other threads:[~2010-09-13 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 16:30 Robert Meschke [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-09-13 15:56 [ath9k-devel] Antenna Configuration Robert Meschke
2010-09-13 16:10 ` Adrian Chadd
2010-09-15 9:50 ` Mike Pithouse
2010-09-13 10:32 Mike Pithouse
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=4C8E51C1.4010803@yahoo.de \
--to=r_meschke@yahoo.de \
--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.