linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Mahesh Palivela <maheshp@posedge.com>
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: Wed, 10 Oct 2012 11:11:48 +0200	[thread overview]
Message-ID: <1349860308.4683.47.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <5065DFAD.2070305@posedge.com>

On Fri, 2012-09-28 at 23:04 +0530, Mahesh Palivela wrote:

> >> I prefer MHz for center freqs, but offset for the primary channel, and
> >> this is exactly like table 22-22 in the 802.11ac draft, so only the "u16
> >> primary_channel_freq" becomes "u8 primary_channel_offset", not all of
> >> them change, no?
> >
> > Ohh, wait, it's called frequency in table 22-22 but actually says the
> > valid range is 1-200 ... wtf? Ok you're right, then it uses the equation
> > 22-99, but ... hmm that's a bit stupid since it needs the (non-constant)
> > "Channel starting frequency".
> >
> > Ok so maybe that wasn't such a good idea. How about we just change
> > prim_chan_freq to prim_chan_offset and leave the other two unchanged?
> 
> 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.

johannes


  reply	other threads:[~2012-10-10  9:11 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 [this message]
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=1349860308.4683.47.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=maheshp@posedge.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).