From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Question on tx-power and number of chains.
Date: Thu, 26 Feb 2015 08:47:25 +0100 [thread overview]
Message-ID: <1424936845.1885.3.camel@sipsolutions.net> (raw)
In-Reply-To: <54EE276A.6050006@candelatech.com>
On Wed, 2015-02-25 at 11:50 -0800, Ben Greear wrote:
> 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?
They're 1 stream at least, so only one chain is needed. I'm not entirely
sure you couldn't transmit them on multiple chains but I don't think
it'd make that much sense?
johannes
prev parent reply other threads:[~2015-02-26 7:47 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
2015-02-26 7:47 ` Johannes Berg [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=1424936845.1885.3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--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).