linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Mahesh Palivela <maheshp@posedge.com>,
	<linux-wireless@vger.kernel.org>
Subject: Re: VHT support, take 2
Date: Fri, 16 Nov 2012 16:10:46 -0800	[thread overview]
Message-ID: <20121117001046.GP3354@lenteja.do-not-panic.com> (raw)
In-Reply-To: <50A65443.2000101@broadcom.com>

On Fri, Nov 16, 2012 at 03:57:07PM +0100, Arend van Spriel wrote:
> On 11/16/2012 02:28 PM, Johannes Berg wrote:
> >On Thu, 2012-11-15 at 17:39 +0530, Mahesh Palivela wrote:
> >
> >>vht regulatory code already posted long back. After went through several
> >>back n forth emails from Luis Rodriguez, accepted the patch.
> >>But not commited anywhere.
> >>Now I have to change that to match to new structs like chan_def etc from
> >>the vht channel work patches you posted 5 days back.
> >>
> >>Also helper funcs to replace chan->flags bit checking to dynamically
> >>check channel through regulatory
> >
> >Yeah, actually I'm not sure it's that easy. We'll also need per
> >bandwidth TX power restrictions, raise the 40 MHz bandwidth restriction
> >to 160 MHz (or get rid of it entirely), etc. That seems to require a new
> >regulatory database format?
> 
> Luis discussed the regulatory framework during the wireless summit
> in Barcelona last week. My (possibly limited) recollection was that
> the current regulatory code can accommodate VHT limits as well. I
> assume that also includes the regulatory database format.

The only thing mentioned which I had not considered is the per bandwidth
TX power restrictions. Where did these come from ?

  Luis

  reply	other threads:[~2012-11-17  0:08 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-09 20:17 VHT support, take 2 Johannes Berg
2012-11-09 20:17 ` [RFC v2 1/8] cfg80211: remove remain-on-channel channel type Johannes Berg
2012-11-09 20:17 ` [RFC v2 2/8] nl80211: add documentation for " Johannes Berg
2012-11-15 11:00   ` Mahesh Palivela
2012-11-15 12:09     ` Johannes Berg
2012-11-09 20:17 ` [RFC v2 3/8] cfg80211: pass a channel definition struct Johannes Berg
2012-11-09 20:17 ` [RFC v2 4/8] nl80211/cfg80211: support VHT channel configuration Johannes Berg
2012-11-12 10:55   ` Johannes Berg
2012-11-16 12:21   ` Mahesh Palivela
2012-11-16 12:37     ` Johannes Berg
2012-11-19  4:18       ` Mahesh Palivela
2012-11-19  8:33         ` Johannes Berg
2012-11-19 12:18   ` Mahesh Palivela
2012-11-19 14:11     ` Johannes Berg
2012-11-20  6:03       ` Mahesh Palivela
2012-11-20  7:27         ` Johannes Berg
2012-11-20  8:27   ` Mahesh Palivela
2012-11-20  8:41     ` Johannes Berg
2012-11-20  9:39       ` Johannes Berg
2012-11-20 11:59         ` Mahesh Palivela
2012-11-20 12:21           ` Johannes Berg
2012-11-20 12:56             ` Mahesh Palivela
2012-11-09 20:17 ` [RFC v2 5/8] mac80211: convert to channel definition struct Johannes Berg
2012-11-09 20:17 ` [RFC v2 6/8] nl80211/cfg80211: add VHT MCS support Johannes Berg
2012-11-09 20:17 ` [RFC v2 7/8] mac80211: support drivers reporting VHT RX Johannes Berg
2012-11-09 20:17 ` [RFC v2 8/8] mac80211: support VHT rates in TX info Johannes Berg
2012-11-09 20:21 ` VHT support, take 2 Johannes Berg
2012-11-15 12:09   ` Mahesh Palivela
2012-11-16 13:28     ` Johannes Berg
2012-11-16 14:57       ` Arend van Spriel
2012-11-17  0:10         ` Luis R. Rodriguez [this message]
2012-11-17  8:48           ` Johannes Berg
2012-11-17 23:34             ` Luis R. Rodriguez
2012-11-18 11:03               ` Johannes Berg
2012-11-18 11:05                 ` 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=20121117001046.GP3354@lenteja.do-not-panic.com \
    --to=rodrigue@qca.qualcomm.com \
    --cc=arend@broadcom.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --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).