From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 0/6] Use the regulatory bandwidth and export HT40 stuff
Date: Thu, 19 Mar 2009 20:40:47 +0100 [thread overview]
Message-ID: <1237491647.5100.114.camel@johannes.local> (raw)
In-Reply-To: <1237442080-27509-1-git-send-email-lrodriguez@atheros.com>
[-- Attachment #1: Type: text/plain, Size: 2191 bytes --]
John,
please back out this series, I'm not sure I agree with the concept and
I'm sure there are potential bugs that can make it segfault.
johannes
On Thu, 2009-03-19 at 01:54 -0400, Luis R. Rodriguez wrote:
> This took a little more consideration than I thought. This is a redesign
> of the bandwidth regulatory stuff, it also keeps in mind preferences in
> the future to use alternative bandwidths like 10 MHz and 5 MHz for things
> like 802.11p.
>
> Ultimately you'll now get proper interpretation of the regulatory
> bandwidth supported, we'll export the bandwidth allowed per channel,
> and we'll also export the channel HT40-/+ capabilities -- if they are
> allowed or not.
>
> This should also help considerably with testing regulatory settings.
> And for users planning to use HT40 it'll give you a direct guide which
> channels to pick on your AP.
>
> This second series completely abandons our old strategy to use the channel
> bandwidth to determine whether or not we support HT40, instead we use it for
> to determine the supported actual bandwidth _per_channel_, not per channel
> set (the pair of channels on an HT40 configuration).
>
> Luis R. Rodriguez (6):
> cfg80211: Process regulatory max bandwidth checks for HT40
> wireless: rename IEEE80211_CHAN_NO_FAT_* to HT40-/+
> mac80211: check if HT40+/- is allowed before sending assoc
> cfg80211: check allowed channel type upon userspace requests
> cfg80211: send channel max bandwidth to userspace
> cfg80211: send to userspace if HT40-/+ is allowed on each channel
>
> drivers/net/wireless/ath9k/regd.c | 10 +-
> drivers/net/wireless/iwlwifi/iwl-core.c | 4 +-
> drivers/net/wireless/iwlwifi/iwl-eeprom.c | 8 +-
> include/linux/nl80211.h | 18 +++
> include/net/wireless.h | 23 +++--
> net/mac80211/ht.c | 11 ++-
> net/mac80211/mlme.c | 4 +-
> net/wireless/nl80211.c | 27 ++++-
> net/wireless/reg.c | 194 ++++++++++++++++++++++------
> 9 files changed, 234 insertions(+), 65 deletions(-)
>
>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-03-19 19:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 5:54 [PATCH v2 0/6] Use the regulatory bandwidth and export HT40 stuff Luis R. Rodriguez
2009-03-19 5:54 ` [PATCH v2 1/6] cfg80211: Process regulatory max bandwidth checks for HT40 Luis R. Rodriguez
2009-03-19 5:54 ` [PATCH v2 2/6] wireless: rename IEEE80211_CHAN_NO_FAT_* to HT40-/+ Luis R. Rodriguez
2009-03-19 5:54 ` [PATCH v2 3/6] mac80211: check if HT40+/- is allowed before sending assoc Luis R. Rodriguez
2009-03-19 5:54 ` [PATCH v2 4/6] cfg80211: check allowed channel type upon userspace requests Luis R. Rodriguez
2009-03-20 10:45 ` Johannes Berg
2009-03-19 5:54 ` [PATCH v2 5/6] cfg80211: send channel max bandwidth to userspace Luis R. Rodriguez
2009-03-19 5:54 ` [PATCH v2 6/6] cfg80211: send to userspace if HT40-/+ is allowed on each channel Luis R. Rodriguez
2009-03-19 19:40 ` Johannes Berg [this message]
2009-03-19 20:28 ` [PATCH v2 0/6] Use the regulatory bandwidth and export HT40 stuff Luis R. Rodriguez
2009-03-19 21:40 ` Johannes Berg
2009-03-19 20:44 ` Luis R. Rodriguez
2009-03-19 21:46 ` Johannes Berg
2009-03-19 20:56 ` 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=1237491647.5100.114.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.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;
as well as URLs for NNTP newsgroup(s).