From: Mahesh Palivela <maheshp@posedge.com>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linville@tuxdriver.com" <linville@tuxdriver.com>
Subject: Re: [RFC] cfg80211: VHT regulatory
Date: Wed, 5 Sep 2012 10:24:09 +0530 [thread overview]
Message-ID: <5046DAF1.103@posedge.com> (raw)
In-Reply-To: <CAGRGNgXkjKKoykWYAev=JpS+owTopCj0j9tLbvwDC+NDM0vzVw@mail.gmail.com>
On 09/05/2012 10:19 AM, Julian Calaby wrote:
> Hi Mahesh,
>
>>>
>>>
>>> Hmm? Shouldn't you add 10 MHz to the lower end, if anything?
>>>
>>
>> Nope. For example 80 MHz BW, take channel 36, 40, 44 and 48. Center freq
>> value is chan 42. so left end will be chan 34 and right end will be chan 50.
>> so I am subtracting 10MHz on both ends to get chan 36 and 48
>
> Surely if you subtract 10MHz from chan 34, you'd end up with chan 32, right?
Very bad. I am wrong. It should be + 10 MHz. Thanks for quick response
Julian.
>
> Thanks,
>
prev parent reply other threads:[~2012-09-05 4:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 3:25 [RFC] cfg80211: VHT regulatory Mahesh Palivela
2012-09-04 8:25 ` Johannes Berg
2012-09-05 4:45 ` Mahesh Palivela
2012-09-05 4:49 ` Julian Calaby
2012-09-05 4:54 ` Mahesh Palivela [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=5046DAF1.103@posedge.com \
--to=maheshp@posedge.com \
--cc=johannes@sipsolutions.net \
--cc=julian.calaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).