All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baldomero Coll <baldo.ath9k@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Progress on Ath9k HT support on Adhoc mode
Date: Thu, 17 Feb 2011 10:27:55 +0100	[thread overview]
Message-ID: <AANLkTi=saEzfkKcCWbBjKiN6KPOPZDo1YKUAoixQCgar@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinZXSt6zt9LRBRdSdtZGYgHLiooOYD=eb-P7wFK@mail.gmail.com>

Thank you for your illustrative answer adrian.
I've sent an email today to the mailing list showing my performance in HT
IBSS mode.

What happens now is that my ad-hoc link don't support HT in both directions.
One of the stations seems to stay in legacy IBSS mode, although sometimes it
upgrades to HT mode.

I suppose it is due to the link adaptation mechanism (Minstrel HT?), but I
would also investigate if the station that stay in legacy IBSS mode is the
one who creates the HT network, the one who joins the HT network, or if it
don't really depend on that.

2011/2/16 Adrian Chadd <adrian@freebsd.org>

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

  reply	other threads:[~2011-02-17  9:27 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15  9:05 [ath9k-devel] Progress on Ath9k HT support on Adhoc mode Baldomero Coll
2011-02-15  9:10 ` Sagar Bijwe
2011-02-16  0:10   ` Peizhao Hu
2011-02-16 12:16 ` Mohammed Shafi
2011-02-16 14:47   ` Baldomero Coll
2011-02-16 16:46     ` Brian Prodoehl
2011-02-17  9:05       ` Baldomero Coll
2011-02-16 17:03     ` Adrian Chadd
2011-02-17  9:27       ` Baldomero Coll [this message]
2011-02-17 16:11         ` Adrian Chadd
  -- strict thread matches above, loose matches on Subject: below --
2011-03-22 10:13 Baldomero Coll
2011-03-10  8:41 Baldomero Coll
2011-02-18 18:49 Baldomero Coll
2011-03-07 21:49 ` Xianghua Xiao
2011-03-08  5:25 ` Mohammed Shafi
2011-02-10 12:04 Baldomero Coll
2011-02-10 14:11 ` Mohammed Shafi
2011-02-10 16:45   ` Baldomero Coll
2011-02-11 10:24     ` Mohammed Shafi
2011-02-08 16:00 le thanh son
2010-12-03  5:30 Peizhao Hu
2010-12-03  6:51 ` Mohammed Shafi
2010-12-09 12:36 ` Alexander Simon
2010-12-09 18:55   ` Luis R. Rodriguez
2010-12-22  8:25   ` Robert Chan
2010-12-29  6:10     ` Robert Chan
2010-12-29 20:20       ` Brian Prodoehl
2010-12-29  6:10     ` Robert Chan
2010-12-29  6:32       ` Mohammed Shafi
2010-12-29  6:52         ` Jouni Malinen
2010-12-29  7:00           ` Mohammed Shafi
2010-12-29  7:21           ` Robert Chan
2010-12-29  8:30             ` Jouni Malinen
2011-01-19 13:42     ` Alexander Simon
2011-02-04  3:04       ` Peizhao Hu
2011-02-04  5:27         ` Mohammed Shafi
2011-02-08  3:38           ` Peizhao Hu
2011-02-10 14:07             ` Mohammed Shafi
2011-01-28  8:58 ` bcoll

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='AANLkTi=saEzfkKcCWbBjKiN6KPOPZDo1YKUAoixQCgar@mail.gmail.com' \
    --to=baldo.ath9k@gmail.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 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.