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: Tue, 22 Mar 2011 11:13:55 +0100	[thread overview]
Message-ID: <AANLkTi=JV5PiqG4Q6xO2Q7+ThvtOZDvZ0APqBJ9iK_dh@mail.gmail.com> (raw)

>
>
> Message: 4
> Date: Mon, 7 Mar 2011 15:49:02 -0600
> From: Xianghua Xiao <xiaoxianghua@gmail.com>
> Subject: Re: [ath9k-devel] Progress on Ath9k HT support on Adhoc mode
> To: simon_alex at web.de
> Cc: ath9k-devel at lists.ath9k.org
> Message-ID:
>        <AANLkTi=DTzrGDa60wPBsAgqXDZ--wiJC9qKK3KTf8Dk6@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Will there be a new version of IBSS/HT patch in the near future?
> Thanks,
>

Can anyone  tell me which 802.11n features are used when the HT IBSS network
is configured with 20 MHz band with?
As far as I know, the frame aggregation (AMSDU, AMPDU) is not working yet
(either in HT40, or in HT20 mode). Obviously, HT20 does not use 40MHz
channel. When I configure my HT20 IBSS network using the Alex and Benoit's
path, I don't experience 802.11n performance, the throughput is even lower
than that achieved with legacy IBSS network. Should the MCS0-15 data rates
also be working in addition to the MIMO technology?

thanks,
Baldo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20110322/de7e8d9f/attachment.htm 

             reply	other threads:[~2011-03-22 10:13 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-22 10:13 Baldomero Coll [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-03-10  8:41 [ath9k-devel] Progress on Ath9k HT support on Adhoc mode 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-15  9:05 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
2011-02-17 16:11         ` Adrian Chadd
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=JV5PiqG4Q6xO2Q7+ThvtOZDvZ0APqBJ9iK_dh@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.