On Mon, Nov 29, 2010 at 1:49 PM, Adrian Chadd <[email protected]> wrote:
> So it turns out that the SR-71A card TX power rates are quoted based
> on the sum of all three chain TX'ing, rather than per-chain TX power.
>
> Given that legacy frames are transmitted through all chains anyway
> (there's no special handling in the TX path that limits the TX
> chainmask to 1 for non-11n frames), is there any reason why all the
> radio chains aren't enabled for legacy mode?
Experienced people had said that one chain is sufficient for legacy
rates(except for PAPRD frames where all 3 chain is needed).The
chainmask of 1 is updated through the following thing in main.c and I
remember this goes into the tx descriptors,but for 11n mode the
default chainmask is used.
*
* 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_OFFCHANNEL) || 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);
}
>
>
> Adrian
> _______________________________________________
> ath9k-devel mailing list
> [email protected]
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
_______________________________________________
ath9k-devel mailing list
[email protected]
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
