From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: linux-wireless@vger.kernel.org, stable@kernel.org
Cc: linux-kernel@vger.kernel.org, linville@tuxdriver.com,
"Luis R. Rodriguez" <lrodriguez@atheros.com>
Subject: [FYI] cfg80211: HT40 fix for APs with odd country IEs for 2.6.33.y
Date: Thu, 11 Mar 2010 20:00:32 -0500 [thread overview]
Message-ID: <1268355632-32348-1-git-send-email-lrodriguez@atheros.com> (raw)
Just a heads up to distribution maintainers, 2.6.33 has an
issue with disabling HT40 channels if you connect to an AP
that has an odd country IE. Specifically if your AP sends
out country IEs as follows:
[1-1]
[2-2]
[3-3]
[4-4]
[5-5]
[6-6]
[7-7]
[8-8]
[9-9]
[10-10]
[11-11]
instead of like this:
[1-11]
Then HT40 gets disabled. This issue was fixed on 2.6.34 and the fixes
were not propagated to 2.6.33.y as they are not "critical" fixes
per se, but if you do value this as "important" you may want to
fetch them and apply them to your 2.6.33.y kernel tree.
I've backported them and stashed them here:
http://kernel.org/pub/linux/kernel/people/mcgrof/patches/cfg80211/2010-03/reg-fixes-33/01-ht40-odd-country-ie/
John W. Linville (1):
wireless: fix build breakage when CONFIG_CFG80211_REG_DEBUG not set
Luis R. Rodriguez (7):
cfg80211: add a regulatory debug print
cfg80211: add debug print when we drop a bogus country IE
cfg80211: process the max power on a country IE
cfg80211: Fix country IE parsing for single channel triplets
cfg80211: fix 2 GHz subband calculation for country IEs
cfg80211: Ingore country IEs with a zero set of number of channels
cfg80211: make regulatory_hint_11d() band specific
net/wireless/reg.c | 317 +++++++++++++++++++++++++++++++++++++++++++++++-----
net/wireless/reg.h | 11 ++
net/wireless/sme.c | 1 +
3 files changed, 302 insertions(+), 27 deletions(-)
next reply other threads:[~2010-03-12 1:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 1:00 Luis R. Rodriguez [this message]
2010-03-12 1:07 ` 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=1268355632-32348-1-git-send-email-lrodriguez@atheros.com \
--to=lrodriguez@atheros.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=stable@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
all inboxes | Powered by JetHome®