From: Alexander Simon <alexander.simon@saxnet.de>
To: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 4/4] mac80211: Add IEEE802.11n for IBSS
Date: Thu, 28 Apr 2011 12:13:55 +0000 (UTC) [thread overview]
Message-ID: <loom.20110428T135917-421@post.gmane.org> (raw)
In-Reply-To: 1302607159.3639.8.camel@jlt3.sipsolutions.net
> Also what if the IBSS is created with HT40+ and then joins, can it join
> HT40-? Is the channel type "advisory" like the frequency? Can it join
> HT20 IBSS as well?
HT type can`t be advisory, as there may be stations without n.
Our card is set to HT40+/- if set by iw.
Some other station is added into our internal station list by its HT beacons.
E.g. if we have configured HT40- and there is someone with HT40+, minstrel_ht
should use HT20 only. But i admit it seems cleaner to AND both caps.
next prev parent reply other threads:[~2011-04-28 12:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 10:42 [PATCH 1/4] cfg80211: Add channel type for IBSS Alexander Simon
2011-04-12 11:04 ` [PATCH 2/4] nl80211: Add NL80211_ATTR_WIPHY_CHANNEL_TYPE " Alexander Simon
2011-04-12 11:08 ` Johannes Berg
2011-04-12 11:06 ` [PATCH 3/4] mac80211: Add function to build HT caps Alexander Simon
2011-04-12 11:16 ` Johannes Berg
2011-04-12 11:22 ` Alexander Simon
2011-04-12 11:07 ` [PATCH 4/4] mac80211: Add IEEE802.11n for IBSS Alexander Simon
2011-04-12 11:19 ` Johannes Berg
2011-04-28 12:13 ` Alexander Simon [this message]
2011-04-28 12:56 ` Johannes Berg
2011-04-29 6:54 ` Alexander Simon
2011-04-29 7:21 ` Johannes Berg
2011-04-29 8:37 ` Alexander Simon
2011-04-29 12:36 ` Alexander Simon
2011-04-29 12:39 ` Johannes Berg
2011-04-29 12:50 ` Alexander Simon
2011-04-26 19:11 ` [PATCH 1/4] cfg80211: Add channel type " John W. Linville
2011-04-28 12:15 ` Alexander Simon
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=loom.20110428T135917-421@post.gmane.org \
--to=alexander.simon@saxnet.de \
--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).