From: Mahesh Palivela <maheshp@posedge.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
Stanislaw Gruszka <sgruszka@redhat.com>
Subject: Re: [RFC v2] cfg80211: VHT regulatory
Date: Fri, 28 Sep 2012 13:39:26 +0530 [thread overview]
Message-ID: <50655B36.5060500@posedge.com> (raw)
In-Reply-To: <1347019809.4256.21.camel@jlt4.sipsolutions.net>
On 09/07/2012 05:40 PM, Johannes Berg wrote:
>
> We don't have to do any calculation in kernel though as far as I can
> tell? Maybe we do need the channel, but I think in terms of
> *specifying*, in particular in the nl80211 and cfg80211 APIs, we should
> stick to the standard if we're going to change it now.
>
struct ieee80211_channel_config {
enum ieee80211_chan_width chan_width;
u16 center_freq1;
u16 center_freq2;
u16 prim_chan_freq;
};
If we stick to standard, all u16 become u8, as their values range is
from 1-200. But these numbers have to be converted to freqKHz in
reg_chan_use_permitted() to find fits in reg rule or not?
Is that ok?
If so I have to use below formulas to get freqKHz.
Channel center frequency [MHz]
= Channel starting frequency + 5 x dot11CurrentChannelCenterFrequencyIndex
Primary 20 MHz channel center frequency [MHz]
= Channel starting frequency + 5 dot11CurrentPrimaryChannel
Thanks,
Mahesh
next prev parent reply other threads:[~2012-09-28 8:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 7:11 [RFC v2] cfg80211: VHT regulatory Mahesh Palivela
2012-09-05 13:39 ` Johannes Berg
2012-09-06 3:44 ` Mahesh Palivela
2012-09-06 9:54 ` Johannes Berg
2012-09-06 12:04 ` Mahesh Palivela
2012-09-07 12:10 ` Johannes Berg
2012-09-10 9:59 ` Mahesh Palivela
2012-09-28 8:09 ` Mahesh Palivela [this message]
2012-09-28 10:39 ` Johannes Berg
2012-09-28 10:42 ` Johannes Berg
2012-09-28 17:34 ` Mahesh Palivela
2012-10-10 9:11 ` Johannes Berg
2012-10-15 3:47 ` Mahesh Palivela
2012-10-19 13:11 ` 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=50655B36.5060500@posedge.com \
--to=maheshp@posedge.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sgruszka@redhat.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).