All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Seth Forshee <seth.forshee@canonical.com>,
	wireless-regdb@lists.infradead.org
Cc: cory novak <cory.novak@gmail.com>
Subject: Re: [wireless-regdb] [RFC] wireless-regdb: Update 5 GHz rules for Canada
Date: Tue, 07 Feb 2017 08:52:30 +0100	[thread overview]
Message-ID: <1486453950.2643.1.camel@sipsolutions.net> (raw)
In-Reply-To: <1486414234-63497-1-git-send-email-seth.forshee@canonical.com>

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.

johannes

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


  reply	other threads:[~2017-02-07  7:52 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 [this message]
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
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=1486453950.2643.1.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=cory.novak@gmail.com \
    --cc=seth.forshee@canonical.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 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.