linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>,
	"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Subject: Re: [RFC v2] cfg80211: VHT regulatory
Date: Mon, 15 Oct 2012 09:17:50 +0530	[thread overview]
Message-ID: <507B8766.9010501@posedge.com> (raw)
In-Reply-To: <1349860308.4683.47.camel@jlt4.sipsolutions.net>

On 10/10/2012 02:41 PM, Johannes Berg wrote:
>>
>> we need "channel starting frequency" anyways for calculating center
>> freq. so we can use same constant for computing primary chan freq as
>> well. why switch to prim_chan_offset?
>
> I think it'd be easier for drivers, since they typically seem to use
> that to specify the control channel. If we give the frequency, they'll
> have to calculate back to offset. The offset is also used in IEs etc.,
> so I think overall that would simplify things.

Offset means we specify one of -70, -50, -30, -10, +10, +30, +50, +70 
for 80/160 MHz BW from center freq.
For ex. 80 MHz BW of channel 36, 40, 44 and 48 center freq is 42. If 
control chan 36, then we specify offset -30. Is that what we want?

VHT IEs doesn't use offset anywhere. I am not sure why/where drivers use 
offset values.


  reply	other threads:[~2012-10-15  3:47 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
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 [this message]
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=507B8766.9010501@posedge.com \
    --to=maheshp@posedge.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@do-not-panic.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).