From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Througput 802.11g-like - configuration issue?
Date: Thu, 7 May 2009 14:28:18 -0700 [thread overview]
Message-ID: <20090507212818.GF13596@tesla> (raw)
In-Reply-To: <892822.32482.qm@web55303.mail.re4.yahoo.com>
On Thu, May 07, 2009 at 01:35:33PM -0700, austinxxh-ath9k at yahoo.com wrote:
> Luis,
>
> from http://linuxwireless.org/en/users/Drivers/ath9k it states IBSS mode is supported.
>
> Are you saying ath9k/11n will not support mesh/IBSS anytime in the future? I'm a bit confused by the message below.
Let me try to put this into a few sets of logical components, might
be easier to understand:
* ath9k supports Ad-hoc (since 2.6.27) and Mesh (since 2.6.31 IIRC)
* To use 802.11n completely you need to support MCS rates and aggregation
* There are two types of 802.11n aggregation: AMPDU, AMSDU
* mac80211 only supports AMPDU aggregation, there is some support for AMDSU
aggregation but for RX only and I am not sure if this was ever tested
* 802.11 standards do not yet define how to support aggregation with ad-hoc
or mesh
* mac80211 does not support aggregation for Ad-hoc or Mesh, it just won't
happen
* You can probably use MCS rates with ath9k in both ad-hoc and in mesh mode
but that's just by chance -- in the future we could decide just disable that.
For more details on 802.11n please see:
http://wireless.kernel.org/en/developers/Documentation/ieee80211/802.11n
Luis
>
> thanks!
> xiao
>
>
> --- On Mon, 4/27/09, Luis R. Rodriguez <lrodriguez@atheros.com> wrote:
> From: Luis R. Rodriguez <lrodriguez@atheros.com>
> Subject: Re: [ath9k-devel] Througput 802.11g-like - configuration issue?
> To: "Fabian Hugelshofer" <hugelshofer2006@gmx.ch>
> Cc: "Johannes Berg" <johannes@sipsolutions.net>, "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
> Date: Monday, April 27, 2009, 12:38 PM
>
>
> On Mon, Apr 20, 2009 at 08:34:08AM -0700, Fabian
> Hugelshofer wrote:
> > Hi all,
> >
> > I am using ath9k with OpenWRT. I have two router boards with identical
> > wireless cards. The wireless card get recognised as:
> > phy0: Atheros AR9160 MAC/BB Rev:1 AR5133 RF Rev:b0
> >
> > Both cards operate in ad-hoc mode on 2.4 or 5Ghz.
>
> To use 11n fully (MCS rates and aggregation) you will need hostapd
> to use AP mode and a STA capable of using 11n. Ad-hoc mode does not
> define how to implement 11n support and as such we don't support it
> with mac80211. Right now in mac80211 we do allow you to set your
> channel type to an HT mode if on adhoc or Mesh but perhaps we'll
> disable this as its not supposed really supported.
>
> Luis
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
next prev parent reply other threads:[~2009-05-07 21:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 15:34 [ath9k-devel] Througput 802.11g-like - configuration issue? Fabian Hugelshofer
2009-04-20 20:03 ` simone pascucci
2009-04-27 17:38 ` Luis R. Rodriguez
2009-05-07 20:35 ` austinxxh-ath9k at yahoo.com
2009-05-07 21:28 ` Luis R. Rodriguez [this message]
2009-09-14 15:31 ` Peter Tarjan
2009-09-14 16:05 ` Luis R. Rodriguez
2009-09-14 21:26 ` xxiao
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=20090507212818.GF13596@tesla \
--to=lrodriguez@atheros.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.