Wireless-regdb Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: Matthias May <matthias.may@neratec.com>,
	Johannes Berg <johannes@sipsolutions.net>
Cc: cory novak <cory.novak@gmail.com>, wireless-regdb@lists.infradead.org
Subject: Re: [wireless-regdb] [RFC] wireless-regdb: Update 5 GHz rules for Canada
Date: Wed, 1 Mar 2017 09:07:57 -0600	[thread overview]
Message-ID: <20170301150757.GL122517@ubuntu-hedt> (raw)
In-Reply-To: <a79eaf02-b384-4c5b-3116-c1386ef98850@neratec.com>

There were some replies to this, but I just noticed that the mailing
list somehow got dropped. Bringing the discussion back to the list.

On Mon, Feb 13, 2017 at 02:58:28PM +0100, Matthias May wrote:
> On 07/02/17 15:04, Seth Forshee wrote:
> > On Tue, Feb 07, 2017 at 08:52:30AM +0100, Johannes Berg wrote:
> >> On Mon, 2017-02-06 at 14:50 -0600, Seth Forshee wrote:
> >>> +	(5150 - 5250 @ 80), (23), AUTO-BW
> >>
> >> For 20 MHz this is right, since the document says:
> >>
> >>     The maximum e.i.r.p. shall not exceed 200 mW or 10 + 10 log10 B,
> >>     dBm, whichever power is less. B is the 99% emission bandwidth in
> >>     megahertz. The e.i.r.p. spectral density shall not exceed 10 dBm in
> >>     any 1.0 MHz band.
> >>
> >> However, for < 20 MHz, like 5 or 10, which we in theory do support, you
> >> can't use that much due to the spectral density requirement. It seems
> >> possible that that's where the 17 dBm came from, since 10 + 10 log10(5)
> >> is about 17.
> > 
> > Yes, thanks. I had forgotten to consider bandwidths less than 20 MHz.
> > 
> > Seth
> > 
> > _______________________________________________
> > wireless-regdb mailing list
> > wireless-regdb@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/wireless-regdb
> > 
> 
> According to  .../include/net/cfg80211.h
> 
> >static inline int
> >ieee80211_chandef_max_power(struct cfg80211_chan_def *chandef)
> >{
> >	switch (chandef->width) {
> >	case NL80211_CHAN_WIDTH_5:
> >		return min(chandef->chan->max_reg_power - 6,
> >			   chandef->chan->max_power);
> >	case NL80211_CHAN_WIDTH_10:
> >		return min(chandef->chan->max_reg_power - 3,
> >			   chandef->chan->max_power);
> >	default:
> >		break;
> >	}
> >	return chandef->chan->max_power;
> >}
> 
> This looks to me like it already handles the reduction of power
> according to bandwidth.

Johannes, just wanted to confirm that based on this you no longer have
any objection to the changes.

Thanks,
Seth

_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb


  reply	other threads:[~2017-03-01 15:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAPw1JcdLDkW9xEUfh-764kuC643DAJ+qWNf4RxmoyUXbpc-D5w@mail.gmail.com>
2017-02-06 19:12 ` [wireless-regdb] Fwd: possible mismatch Canadian regulatory info cory novak
2017-02-06 19:39   ` Seth Forshee
2017-02-06 19:44     ` cory novak
2017-02-06 20:50       ` [wireless-regdb] [RFC] wireless-regdb: Update 5 GHz rules for Canada Seth Forshee
2017-02-07  7:52         ` Johannes Berg
2017-02-07 14:04           ` Seth Forshee
2017-02-07 14:15             ` Johannes Berg
2017-02-13 13:58             ` Matthias May
2017-03-01 15:07               ` Seth Forshee [this message]
2017-03-01 15:35                 ` Johannes Berg
2017-03-01 15:49         ` Seth Forshee

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=20170301150757.GL122517@ubuntu-hedt \
    --to=seth.forshee@canonical.com \
    --cc=cory.novak@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=matthias.may@neratec.com \
    --cc=wireless-regdb@lists.infradead.org \
    /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