From: Johannes Berg <johannes@sipsolutions.net>
To: Mahesh Palivela <maheshp@posedge.com>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] cfg80211: 80MHz (11ac) regulatory change
Date: Thu, 26 Jul 2012 19:42:44 +0200 [thread overview]
Message-ID: <1343324564.4477.5.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <5010E413.9010502@posedge.com>
On Thu, 2012-07-26 at 12:00 +0530, Mahesh Palivela wrote:
> >> 11ac Draft3.0 section 22.3.14 says VHT channel is specified by
> >> dot11CurrentChannelBandwidth, dot11CurrentChannelCenterFrequencyIndex0,
> >> dot11CurrentChannelCenterFrequencyIndex1 and dot11CurrentPrimaryChannel
> >>
> >> primary channel comes from HT Op IE.
> >> chanBW, chanCenterFreq0, chanCenterFreq1 comes from VHT Op IE.
> >> So multiple secondary channels doesn't seem to be a valid?
> >
> > Hmm. But that means we have to specify the channel completely
> > differently? I think we should stick to our scheme of center freq of a
> > 20 MHz channel + surrounding bandwidth,
>
> ok. Let's stick to old way of channel config. Basically freq value and
> channel type which kind of specifies channel widths. so how about for
> VHT channel types as below. Its similar to what you proposed.
>
> For 80 MHz:
>
> VHT80_3PLUS
> VHT80_MINUS_2PLUS
> VHT80_2MINUS_PLUS
> VHT80_3MINUS
>
> For 160 MHz:
>
> VHT160_7PLUS
> VHT160_MINUS_6PLUS
> VHT160_2MINUS_5PLUS
> VHT160_3MINUS_4PLUS
> VHT160_4MINUS_3PLUS
> VHT160_5MINUS_2PLUS
> VHT160_6MINUS_PLUS
> VHT160_7MINUS
Yeah, that would work. Lots of channel types ...
> > though it obviously won't work for 80+80. The question will be where
> > we deviate from our previous scheme. I tend to think that HT80+80
> > should deviate, I have a feeling it won't be implemented soon
> > (or ever?) anyway.
> >
>
> Yea, even I feel the channel config representation what we are proposing
> is not really extendable to discrete bands. That's my only worry...
? What do you mean?
> >> CHAN_NO_VHT80 is actually 2 bits. NO_VHT80MINUS & NO_VHT80PLUS.
> >> Is that ok?
> >>
> >> + IEEE80211_CHAN_NO_VHT80PLUS = 1<<6,
> >> + IEEE80211_CHAN_NO_VHT80MINUS = 1<<7,
> >>
> >> +#define IEEE80211_CHAN_NO_VHT80 \
> >> + (IEEE80211_CHAN_NO_VHT80PLUS | IEEE80211_CHAN_NO_VHT80MINUS)
> >
> > Right. But did you mean to check that all of them are set? What if one
> > of them is set but the other isn't?
> >
>
> If one of them is set, then we accept VHT80 for that channel.
Yes, but is that really correct?
johannes
next prev parent reply other threads:[~2012-07-26 17:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 9:17 [PATCH] cfg80211: 80MHz (11ac) regulatory change Mahesh Palivela
2012-07-23 13:06 ` Johannes Berg
2012-07-24 6:46 ` Mahesh Palivela
2012-07-24 8:56 ` Johannes Berg
2012-07-24 10:48 ` Mahesh Palivela
2012-07-24 11:17 ` Johannes Berg
2012-07-25 4:01 ` Mahesh Palivela
2012-07-25 9:50 ` Johannes Berg
2012-07-26 6:30 ` Mahesh Palivela
2012-07-26 17:42 ` Johannes Berg [this message]
2012-07-30 8:31 ` Mahesh Palivela
2012-07-24 7:12 ` Kalle Valo
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=1343324564.4477.5.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=maheshp@posedge.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).