All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mahesh Palivela <maheshp@posedge.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Stanislaw Gruszka <sgruszka@redhat.com>,
	Kalle Valo <kvalo@adurom.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>
Subject: Re: [PATCH] cfg80211: VHT (11ac) Regulatory change
Date: Fri, 24 Aug 2012 18:38:41 +0530	[thread overview]
Message-ID: <50377CD9.3090204@posedge.com> (raw)
In-Reply-To: <1345809927.6991.0.camel@jlt3.sipsolutions.net>

On 08/24/2012 05:35 PM, Johannes Berg wrote:
> On Fri, 2012-08-24 at 17:03 +0530, Mahesh Palivela wrote:
>
>> /**
>>    * enum ieee80211_chan_width - channel bandwidths
>>    *
>>    * @IEEE80211_CHAN_WIDTH_20MHZ: 20 MHz chan bandwidth
>>    * @IEEE80211_CHAN_WIDTH_40MHZ: 40 MHz chan bandwidth
>>    * @IEEE80211_CHAN_WIDTH_80MHZ: 80 MHz chan bandwidth
>>    * @IEEE80211_CHAN_WIDTH_160MHZ: 160 MHz chan bandwidth
>>    */
>
> We might need 20MHZ_NOHT or something?

Yes, I missed that.
20MHZ_NOHT in 5G band and legacy operation 2.4G band may be 5MHZ.

>
>>           enum ieee80211_chan_width chan_width2;
>>           u16 control_offset2;
>
> Those shouldn't be necessary, I think? The secondary 80 MHz channel
> can't have a control channel, it seems, and the width should be the same
> as well? Plus this is only allowed in 80+80 anyway.
>
> johannes
>
11ac d3.0 spec section 8.4.2.10 says

An operating class for an 80+80 MHz channel bandwidth is expressed by 
two consecutive Operating/Sub-
band Sequences, where the first Operating/Subband Sequence field 
contains an Operating Triplet for an
80 MHz Channel Spacing with an 80+ Behavior Limit and the second 
Operating/Subband Sequence field
contains an Operating Triplet for an 80 MHz Channel Spacing without an 
80+ Behavior Limit.

so country might allow primary chan to fall in other frequency segment?

- Mahesh

  reply	other threads:[~2012-08-24 13:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-14 15:55 [PATCH] cfg80211: VHT (11ac) Regulatory change Mahesh Palivela
2012-08-16 10:22 ` Stanislaw Gruszka
2012-08-16 13:17   ` Mahesh Palivela
2012-08-17 14:06     ` Stanislaw Gruszka
2012-08-17 17:56       ` Mahesh Palivela
2012-08-20 16:38         ` Johannes Berg
2012-08-21  7:50           ` Kalle Valo
2012-08-21  8:18             ` Stanislaw Gruszka
2012-08-21 13:35               ` Mahesh Palivela
2012-08-21 15:53                 ` Johannes Berg
2012-08-21 18:07                   ` Mahesh Palivela
2012-08-22  7:03                     ` Johannes Berg
2012-08-22  9:01                       ` Stanislaw Gruszka
2012-08-22  9:04                         ` Johannes Berg
2012-08-22 10:12                           ` Stanislaw Gruszka
2012-08-24 11:33                             ` Mahesh Palivela
2012-08-24 12:05                               ` Johannes Berg
2012-08-24 13:08                                 ` Mahesh Palivela [this message]
2012-08-26  8:39                                   ` Johannes Berg
2012-08-27  4:15                                     ` Mahesh Palivela
2012-08-27 12:05                                     ` Mahesh Palivela
2012-08-28 12:20                                       ` Mahesh Palivela
2012-08-29  4:07                                     ` Mahesh Palivela
2012-09-04  8:17                                       ` Johannes Berg
  -- strict thread matches above, loose matches on Subject: below --
2012-08-14  7:32 Mahesh Palivela
2012-08-14 12:05 ` Stanislaw Gruszka

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=50377CD9.3090204@posedge.com \
    --to=maheshp@posedge.com \
    --cc=johannes@sipsolutions.net \
    --cc=kvalo@adurom.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.