From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Question on tx-power and number of chains.
Date: Wed, 25 Feb 2015 11:50:02 -0800 [thread overview]
Message-ID: <54EE276A.6050006@candelatech.com> (raw)
In-Reply-To: <1424891437.2050.29.camel@sipsolutions.net>
On 02/25/2015 11:10 AM, Johannes Berg wrote:
> On Wed, 2015-02-25 at 10:51 -0800, Ben Greear wrote:
>
>> Is there a table somewhere that explains how many chains are used by each
>> rate?
>
> mcsindex.com?
What about OFDM and CCK. Are those always 1 chain?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2015-02-25 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 18:51 Question on tx-power and number of chains Ben Greear
2015-02-25 19:10 ` Johannes Berg
2015-02-25 19:21 ` Arend van Spriel
2015-02-25 19:29 ` Johannes Berg
2015-02-25 19:50 ` Ben Greear [this message]
2015-02-26 7:47 ` Johannes Berg
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=54EE276A.6050006@candelatech.com \
--to=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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 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).