ath9k-devel.lists.ath9k.org archive mirror
 help / color / mirror / Atom feed
From: <bogus@does.not.exist.com>
To: ath9k-devel@lists.ath9k.org
Subject: No subject
Date: Sun, 19 Dec 2010 23:59:03 -0000	[thread overview]
Message-ID: <mailman.2.1297934885.6166.ath9k-devel@lists.ath9k.org> (raw)

<br>
* If your RX chainmask has &gt;1 radio enabled, you&#39;ll always be doing<=
br>
receive-side &quot;diversity&quot; (which is really &quot;combining&quot; (=
MRC) if I<br>
understand the technology correctly on multi-radio atheros 11n cards);<br>
* If your TX chainmask has &gt;1 radio enabled and the TX descriptor has<br=
>
the relevant chainmask bits set, you should be transmitting on both<br>
antennas regardless of the rate. I honestly haven&#39;t verified it (I&#39;=
ve<br>
only verified that behaviour for transmitting legacy rates out of the<br>
11n chips);<br>
<br>
* For rates &lt; MCS8 (and legacy rates) there&#39;s further TX-side tricke=
ry<br>
that can be going on which I&#39;m not too up-to-date on. For example,<br>
some (all?) of the 11n chips allow you to optionally transmit MCS0-7<br>
using STBC. But iirc, STBC is only enabled for 1-stream TX.<br>
<br>
In short, if you&#39;ve got all the radios enabled =C2=A0for RX and ath9k i=
s<br>
enabling both/all radio chains when TX&#39;ing, I think the answer is<br>
&quot;yes&quot; for you. :)<br>
<br>
Adrian<br>
<br>
On 16 February 2011 22:47, Baldomero Coll &lt;<a href=3D"mailto:baldo.ath9k=
@gmail.com">baldo.ath9k at gmail.com</a>&gt; wrote:<br>
&gt; I&#39;m not sure, but I&#39;ve read somewhere that by default the two =
antennas are<br>
&gt; used.<br>
&gt; It is true that I&#39;m not interested in selecting the number of ante=
nnas, what<br>
&gt; I really want is that the MIMO capability is exploited if I&#39;m usin=
g 802.11n<br>
&gt; HT IBSS operation mode.<br>
&gt; Can someone confirm that by default the two antennas (spatial diversit=
y) are<br>
&gt; being used when we create the HT IBSS network?<br>
&gt;<br>
&gt; 2011/2/16 Mohammed Shafi &lt;<a href=3D"mailto:shafi.ath9k@gmail.com">=
shafi.ath9k at gmail.com</a>&gt;<br>
&gt;&gt;<br>
&gt;&gt; On Tue, Feb 15, 2011 at 2:35 PM, Baldomero Coll &lt;<a href=3D"mai=
lto:baldo.ath9k@gmail.com">baldo.ath9k at gmail.com</a>&gt;<br>
&gt;&gt; wrote:<br>
&gt;&gt; &gt; Hello,<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; Can you please tell me how do you select one o two antennas?<=
br>
&gt;&gt;<br>
&gt;&gt; I don&#39;t know why you should do that. I guess changing the tx/r=
x<br>
&gt;&gt; chainmask will do after it was read from eeprom.<br>
&gt;&gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; I&#39;m using a similar setting than you:<br>
&gt;&gt; &gt; Linux kernel: 2.6.32-28-generic-pae.<br>
&gt;&gt; &gt; Driver: compat-wireless-2011-01-17 and iw-0.9.21 with the pat=
ch<br>
&gt;&gt; &gt; suggested by<br>
&gt;&gt; &gt; Alex.<br>
&gt;&gt; &gt; Radio card: Ubiquiti SR71x<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; Thanks in advance,<br>
&gt;&gt; &gt; Baldomero<br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt; &gt;&gt; Hi all,<br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt; &gt;&gt; I would like to confirm my findings. My test platform con=
figurations<br>
&gt;&gt; &gt;&gt; are<br>
&gt;&gt; &gt;&gt; follow.<br>
&gt;&gt; &gt;&gt; Board: pcengine alix3d2<br>
&gt;&gt; &gt;&gt; Linux kernel: 2.6.35 from linux-wireless git<br>
&gt;&gt; &gt;&gt; Driver: compat-wireless-2011-01-17 and iw-0.9.21 with the=
 patch<br>
&gt;&gt; &gt;&gt; suggested by Alex.<br>
&gt;&gt; &gt;&gt; Radio card: Ubiqiti SR71a on channel 36 with HT40+<br>
&gt;&gt; &gt;&gt; Measurement tool and settings: Iperf, UDP, 100Mb offered =
load<br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt; &gt;&gt; Recored throughput: 50-54Mbps (one antenna); 78-80Mbps (t=
wo or three<br>
&gt;&gt; &gt;&gt; antennas).<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; _______________________________________________<br>
&gt;&gt; &gt; ath9k-devel mailing list<br>
&gt;&gt; &gt; <a href=3D"mailto:ath9k-devel@lists.ath9k.org">ath9k-devel at li=
sts.ath9k.org</a><br>
&gt;&gt; &gt; <a href=3D"https://lists.ath9k.org/mailman/listinfo/ath9k-dev=
el" target=3D"_blank">https://lists.ath9k.org/mailman/listinfo/ath9k-devel<=
/a><br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; ath9k-devel mailing list<br>
&gt; <a href=3D"mailto:ath9k-devel@lists.ath9k.org">ath9k-devel at lists.ath9k=
.org</a><br>
&gt; <a href=3D"https://lists.ath9k.org/mailman/listinfo/ath9k-devel" targe=
t=3D"_blank">https://lists.ath9k.org/mailman/listinfo/ath9k-devel</a><br>
&gt;<br>
&gt;<br>
</blockquote></div><br>

--002215048f672c1ad2049c7703f8--

             reply	other threads:[~2010-12-19 23:59 UTC|newest]

Thread overview: 96+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-19 23:59 bogus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-11-19 18:31 No subject bogus
2016-11-19 18:31 bogus
2016-11-19 18:31 bogus
2016-11-19 18:31 bogus
2016-06-13  6:24 bogus
2016-06-13  6:24 bogus
2016-02-09  7:29 bogus
2015-11-16 16:13 bogus
2015-10-12 17:26 bogus
2014-09-13 19:40 bogus
2014-09-13 19:40 bogus
2014-09-13 19:40 bogus
2014-09-13 19:40 bogus
2014-09-13 19:40 bogus
2013-09-15  9:49 bogus
2013-09-15  9:49 bogus
2013-09-15  9:49 bogus
2013-04-03 10:31 bogus
2013-04-03 10:31 bogus
2013-04-03 10:31 bogus
2013-04-03 10:31 bogus
2013-01-16 21:46 bogus
2013-01-16 21:46 bogus
2012-11-08  9:33 bogus
2012-05-25 15:26 bogus
2012-05-25 15:26 bogus
2012-04-05  7:54 bogus
2012-04-05  7:54 bogus
2012-02-27  5:00 bogus
2012-02-27  5:00 bogus
2012-02-27  5:00 bogus
2012-01-15  8:24 bogus
2011-11-12 14:39 bogus
2011-11-12 14:39 bogus
2011-08-05  3:08 bogus
2011-08-05  3:08 bogus
2011-08-05  3:08 bogus
2011-08-05  3:08 bogus
2011-08-05  3:08 bogus
2011-06-04 23:16 bogus
2011-06-04 23:16 bogus
2011-04-07  5:55 bogus
2011-04-07  5:55 bogus
2011-04-07  5:55 bogus
2011-04-07  5:55 bogus
2011-04-07  5:55 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-07-23 10:05 bogus
2010-03-25 17:02 bogus
2010-03-25 17:02 bogus
2009-02-27 19:01 bogus
2009-02-27 19:01 bogus
2009-02-27 19:01 bogus
2009-02-27 19:01 bogus
2009-02-27 19:01 bogus
2009-02-27 19:01 bogus
2009-02-27 19:01 bogus
2009-02-15  8:49 bogus
2009-01-04 17:33 bogus
2009-01-04 17:33 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-07-28  4:41 bogus

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=mailman.2.1297934885.6166.ath9k-devel@lists.ath9k.org \
    --to=bogus@does.not.exist.com \
    --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 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).