From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: linville@tuxdriver.com, johannes@sipsolutions.net
Cc: linux-wireless@vger.kernel.org,
"Luis R. Rodriguez" <lrodriguez@atheros.com>
Subject: [PATCH 1/4] cfg80211: check allowed channel max bandwidth before setting HT40
Date: Mon, 9 Mar 2009 22:04:56 -0400 [thread overview]
Message-ID: <1236650699-30538-2-git-send-email-lrodriguez@atheros.com> (raw)
In-Reply-To: <1236650699-30538-1-git-send-email-lrodriguez@atheros.com>
Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
---
net/wireless/nl80211.c | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/net/wireless/nl80211.c b/net/wireless/nl80211.c
index 531bb67..08d4f55 100644
--- a/net/wireless/nl80211.c
+++ b/net/wireless/nl80211.c
@@ -398,6 +398,12 @@ static int nl80211_set_wiphy(struct sk_buff *skb, struct genl_info *info)
/* Primary channel not allowed */
if (!chan || chan->flags & IEEE80211_CHAN_DISABLED)
goto bad_res;
+ /* You need 40 MHz for an HT40 channel */
+ if (channel_type == NL80211_CHAN_HT40PLUS ||
+ channel_type == NL80211_CHAN_HT40MINUS) {
+ if (chan->max_bandwidth < 40)
+ goto bad_res;
+ }
if (channel_type == NL80211_CHAN_HT40MINUS)
sec_freq = freq - 20;
--
1.6.0.6
next prev parent reply other threads:[~2009-03-10 2:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 2:04 [PATCH 0/4] wireless: use channel bandwidth Luis R. Rodriguez
2009-03-10 2:04 ` Luis R. Rodriguez [this message]
2009-03-10 2:04 ` [PATCH 2/4] mac80211: move early error branch check on ieee80211_set_freq() Luis R. Rodriguez
2009-03-10 2:04 ` [PATCH 3/4] mac80211: disallow HT40 if max channel bandwidth is less than 40 MHz Luis R. Rodriguez
2009-03-10 7:15 ` Johannes Berg
2009-03-10 8:43 ` Luis R. Rodriguez
2009-03-10 8:46 ` Johannes Berg
2009-03-10 8:51 ` Luis R. Rodriguez
2009-03-10 2:04 ` [PATCH 4/4] cfg80211: send channel max bandwidth to userspace Luis R. Rodriguez
2009-03-10 7:16 ` [PATCH 0/4] wireless: use channel bandwidth Johannes Berg
2009-03-10 8:43 ` Luis R. Rodriguez
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=1236650699-30538-2-git-send-email-lrodriguez@atheros.com \
--to=lrodriguez@atheros.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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