From: Johannes Berg <johannes@sipsolutions.net>
To: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
Cc: "John W . Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
"Luis R . Rodriguez" <rodrigue@qca.qualcomm.com>
Subject: Re: [PATCH v3] cfg80211: Fix regulatory check for 60GHz band frequencies
Date: Tue, 25 Sep 2012 09:42:50 +0200 [thread overview]
Message-ID: <1348558970.10041.20.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1348558107.10041.19.camel@jlt4.sipsolutions.net> (sfid-20120925_092757_197809_8B558E03)
On Tue, 2012-09-25 at 09:28 +0200, Johannes Berg wrote:
> On Sun, 2012-09-23 at 09:49 +0200, Vladimir Kondratiev wrote:
> > The current regulatory code on cfg80211 performs a check to
> > see if a regulatory rule belongs to an IEEE band so that if
> > a Country IE is received and no rules are specified for a
> > band (which is allowed by IEEE) those bands are left intact.
> > The current band check assumes a rule is bound to a band
> > if the rule's start or end frequency is less than 2 GHz
> > apart from the center of frequency being inspected.
> >
> > In order to support 60 GHz for 802.11ad we need to increase
> > this to account for the channel spacing of 2160 MHz whereby
> > a channel somewhere in the middle of a regulatory rule may
> > be more than 2 MHz apart from either the beginning or
>
> GHz?
Applied with that fix & a typo fix in the comments.
johannes
next prev parent reply other threads:[~2012-09-25 7:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-23 7:49 [PATCH v3] Fix for regulatory in 60g Vladimir Kondratiev
2012-09-23 7:49 ` [PATCH v3] cfg80211: Fix regulatory check for 60GHz band frequencies Vladimir Kondratiev
2012-09-24 16:49 ` Luis R. Rodriguez
2012-09-25 7:28 ` Johannes Berg
2012-09-25 7:42 ` Johannes Berg [this message]
2012-09-25 16: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=1348558970.10041.20.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=qca_vkondrat@qca.qualcomm.com \
--cc=rodrigue@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