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: Thu, 6 Sep 2012 17:34:53 +0530 [thread overview]
Message-ID: <50489165.1080902@posedge.com> (raw)
In-Reply-To: <1346925298.5469.4.camel@jlt4.sipsolutions.net>
On 09/06/2012 03:24 PM, Johannes Berg wrote:
> On Thu, 2012-09-06 at 09:14 +0530, Mahesh Palivela wrote:
>> On 09/05/2012 07:09 PM, Johannes Berg wrote:
>
> No, it doesn't. It *derives* these. Check "Table 22-22—Fields to specify
> VHT channels" for how it actually *specifies* them.
>
hostapd.conf specifies using numbers only. hostapd converts to freq
values, puts into NL attribs and cfg80211 directly gets freq values
rather than channel numbers.
we have to do these calculations either in app or cfg80211. user space
vs krnl space. I am ok either way.
>>
>> just a defensive check. I can remove it, if redundant
>
> I was thinking then it should have a WARN_ON_ONCE() maybe.
>
>
ok. will put WARN_ON_ONCE()
>>
>> This is to find the regulatory rule only. Not checking desired BW around
>> prim channel. center freq chan 42 of 36, 40, 44 and 48 for 80 MHz BW may
>> not be in list of freq values in reg rule.
>
> Hmm? Don't think I understand this. Why do you pass in the right
> bandwidth if it's not used?
>
ok. I will define new freq_reg_info_regd() to take center freq and
desired BW and return reg_rule. I think current freq_reg_info_regd() may
fail if we give chan 42.
>>> This seems better, but is missing the bandwidth check?
>>
>> bandwidths are checked in reg_chan_use_permitted. reg rule decides it right?
>
> I guess I don't really understand this.
>
what should I do for bandwidth check in reg_sec_chans_permitted() ?
> johannes
>
next prev parent reply other threads:[~2012-09-06 12:05 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 [this message]
2012-09-07 12:10 ` Johannes Berg
2012-09-10 9:59 ` Mahesh Palivela
2012-09-28 8:09 ` Mahesh Palivela
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=50489165.1080902@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).