From: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>,
"John W . Linville" <linville@tuxdriver.com>,
<linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3] cfg80211: Fix regulatory check for 60GHz band frequencies
Date: Tue, 25 Sep 2012 09:56:30 -0700 [thread overview]
Message-ID: <20120925165630.GG3354@lenteja.do-not-panic.com> (raw)
In-Reply-To: <1348558107.10041.19.camel@jlt4.sipsolutions.net>
On Tue, Sep 25, 2012 at 09:28:27AM +0200, Johannes Berg wrote:
> On Sun, 2012-09-23 at 09:49 +0200, Vladimir Kondratiev wrote:
> > Without a fix for this even though channels 1-3 are allowed world
> > wide on the rule (57240 - 63720 @ 2160), channel 2 at 60480 MHz
> > will end up getting disabled given that it is 3240 MHz from
> > both the frequency rule start and end frequency. Fix this by
> > using 2 GHz separation assumption for the 2.4 and 5 GHz bands
> > but for 60 GHz use a 10 GHz separation before assuming a rule
> > is not part of the band.
>
> Luis, given that you think the regulatory code in the kernel is 802.11
> specific, why are we inferring these rules from the frequencies rather
> than using the 802.11 specific information about the band that it
> represents? :-D
Its a good point freq_reg_info() is at the crux of where we do are still
agnostic to 802.11. To make this 802.11 specific and easier to read I
suspect we can require passing the chan struct and then we'd use a switch
statement for the band.
Luis
prev parent reply other threads:[~2012-09-25 16:55 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
2012-09-25 16:56 ` Luis R. Rodriguez [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=20120925165630.GG3354@lenteja.do-not-panic.com \
--to=rodrigue@qca.qualcomm.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=qca_vkondrat@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