From: Jouni Malinen <j@w1.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Paul Stewart <pstew@chromium.org>,
linux-wireless@vger.kernel.org,
Rajkumar Manoharan <rmanohar@qca.qualcomm.com>,
Arik Nemtsov <anamtsov@gmail.com>,
Eliad Peller <eliad@wizery.com>
Subject: Re: [RFCv2] mac80211: Don't let regulatory make us deaf
Date: Mon, 27 Feb 2012 13:32:12 +0200 [thread overview]
Message-ID: <20120227113212.GA4576@w1.fi> (raw)
In-Reply-To: <1330338898.3483.10.camel@jlt3.sipsolutions.net>
On Mon, Feb 27, 2012 at 11:34:58AM +0100, Johannes Berg wrote:
> Come to think of it, we could also simply configure the channel to be
> the right HT channel during auth, and then still associate as a non-HT
> station later. I realise this isn't the best configuration, but given
> that this is a corner case (TKIP used on an HT AP!) I think we can live
> with that.
In general, it should be fine to enable HT/HT40 configuration for
receive and just make sure we never transmit using parameters not
allowed by regulatory or something like HT+TKIP rules. However, there
could be some hardware/firmware designs that would refuse HT+TKIP at
lower layer, so skipping the channel (re-)configuration could
potentially cause some problems. I'm not aware of any specific example
of this, though, so I can only speculate that such a thing could exist.
> More importantly though, I think having to worry about reconfiguring the
> channel will also be a big hassle in upcoming multi-channel code.
Agreed.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2012-02-27 11:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 5:25 [RFC] mac80211: Don't let regulatory make us deaf Paul Stewart
2012-02-21 5:25 ` [RFCv2] " Paul Stewart
2012-02-21 18:01 ` Mahesh
2012-02-23 13:39 ` Johannes Berg
2012-02-23 14:53 ` Sam Leffler
2012-02-23 14:59 ` Johannes Berg
2012-02-23 15:14 ` Paul Stewart
2012-02-24 1:53 ` Luis R. Rodriguez
2012-02-24 4:15 ` Paul Stewart
2012-02-21 5:25 ` [PATCH] " Paul Stewart
2012-02-24 4:25 ` [RFCv2] " Sam Leffler
2012-02-26 11:15 ` Johannes Berg
2012-02-26 11:25 ` Johannes Berg
2012-02-27 10:34 ` Johannes Berg
2012-02-27 11:32 ` Jouni Malinen [this message]
2012-02-27 11:38 ` Johannes Berg
2012-02-27 13:46 ` Jouni Malinen
2012-03-07 5:46 ` Paul Stewart
2012-03-07 7:36 ` Johannes Berg
2012-03-07 18:40 ` John W. Linville
2012-03-07 18:52 ` Johannes Berg
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=20120227113212.GA4576@w1.fi \
--to=j@w1.fi \
--cc=anamtsov@gmail.com \
--cc=eliad@wizery.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=pstew@chromium.org \
--cc=rmanohar@qca.qualcomm.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).