From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v4 3/6] mac80211: check if HT40+/- is allowed before sending assoc
Date: Sat, 21 Mar 2009 09:02:22 +0100 [thread overview]
Message-ID: <1237622542.5100.163.camel@johannes.local> (raw)
In-Reply-To: <20090320142957.GA8120@tesla>
[-- Attachment #1: Type: text/plain, Size: 994 bytes --]
On Fri, 2009-03-20 at 07:29 -0700, Luis R. Rodriguez wrote:
> On Fri, Mar 20, 2009 at 03:48:56AM -0700, Johannes Berg wrote:
> > On Thu, 2009-03-19 at 02:41 -0400, Luis R. Rodriguez wrote:
> > > We weren't checking this at all.
> >
> > The question is whether we really want that. In other places, we trust
> > the AP, why not here as well?
>
> Its not about trust its also about if it will logistically make sense, for
> example you simply cannot use HT40- on channel 11 if yuo don't have
> a channel 7. The NO_HT40- would indicate this to us so we don't bother.
> The example I give is lousy as its not something that would occur usually
> but with 5 GHz and regulatory rules changing things could be a bit
> different.
Yeah, good point. That's why we need to disassoc from the AP if we
definitely cannot support it -- we cannot change the APs opinion of our
HT40 capabilities. Of course, when we start out not supporting it we can
tell it we don't do HT40.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2009-03-21 8:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 6:41 [PATCH v4 3/6] mac80211: check if HT40+/- is allowed before sending assoc Luis R. Rodriguez
2009-03-20 10:48 ` Johannes Berg
2009-03-20 14:29 ` Luis R. Rodriguez
2009-03-21 8:02 ` Johannes Berg [this message]
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=1237622542.5100.163.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=Luis.Rodriguez@Atheros.com \
--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 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.