All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: qca_vkondrat@qca.qualcomm.com, linux-wireless@vger.kernel.org,
	wireless-regdb@lists.infradead.org
Subject: Re: [PATCH] wireless-regdb: add regulatory rule for ETSI members on 60GHz band
Date: Tue, 14 Oct 2014 14:28:58 +0200	[thread overview]
Message-ID: <543D170A.6060709@gmail.com> (raw)

Hi,

related to 623d8438b724afb7c4818cb9b129a552ef2b518b at wireless-regdb.

On 12/10/2012, Vladimir Kondratiev wrote:

> Purpose is to serve for 802.11ad specification that introduces operation
> on the 60GHz band, using bandwidth 2160MHz.
> 
> For the 60GHz band, regulation defined in the "Etsi En 302 567"
> http://docsfiles.com/pdf_final_draft_etsi_en_302_567.html
> 
> It defines for the frequency range 57 GHz to 66 GHz,
> Max. power level (EIRP) for
> indoor only: 40 dBm, and indoor/outdoor: 25 dBm
> Also, there is spectral power density limit
> 13 dBm/MHz for indoor and -2 dBm/MHz indoor/outdoor

I don't know where you did get this information.
ETSI EN 302 567 V1.2.1 (2012-01) http://www.etsi.org/deliver/etsi_en/302500_302599/302567/01.02.01_60/en_302567v010201p.pdf
doesn't handle in different way indoor/outdoor.

And also 57000 - 66000 is allowed.

So that:
"(57240 - 65880 @ 2160), (40), NO-OUTDOOR" should(must) be replaced by:
"(57000 - 66000 @ 2160), (40)"

> Only indoor part specified, as kernel can't use multiple
> rules per frequency at the moment. Also, standard do not set bandwidth limitation;
> for purpose of 802.11ad this patch specifies bandwidth 2160 MHz,
> in this case gross EIRP limit applies. Frequency limits also set accordingly
> to the 802.11ad channel allocation.
> 
> This patch apply this to the full ETSI member countries:
> [...]
>
> diff --git a/db.txt b/db.txt
> index c00602c..848c985 100644
> --- a/db.txt
> +++ b/db.txt
> @@ -12,6 +12,10 @@ country 00:
>          (5735 - 5835 @ 40), (3, 20), PASSIVE-SCAN, NO-IBSS
>  
>  
> +country AD:
> +        # 60 gHz band channels 1-4, ref: Etsi En 302 567
> +        (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR
> [...]

             reply	other threads:[~2014-10-14 12:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-14 12:28 Xose Vazquez Perez [this message]
2014-10-19  6:49 ` [PATCH] wireless-regdb: add regulatory rule for ETSI members on 60GHz band Vladimir Kondratiev
2014-10-19  6:49   ` [wireless-regdb] " Vladimir Kondratiev
2014-10-27 17:26   ` John W. Linville
2014-10-27 17:26     ` [wireless-regdb] " John W. Linville
2014-10-28  8:19     ` Vladimir Kondratiev
2014-10-28  8:19       ` [wireless-regdb] " Vladimir Kondratiev
2014-10-28 11:06       ` Xose Vazquez Perez
2014-10-28 11:06         ` [wireless-regdb] " Xose Vazquez Perez
  -- strict thread matches above, loose matches on Subject: below --
2012-12-09 14:16 [PATCH] wireless-regdb: add regulatory rule for US on 60gHz band Vladimir Kondratiev
2012-12-10  9:45 ` [PATCH] wireless-regdb: add regulatory rule for ETSI members " Vladimir Kondratiev
2012-12-10 10:21   ` Johannes Berg
2012-12-10 11:09     ` Vladimir Kondratiev
2012-12-10 11:31       ` Johannes Berg
2012-12-10 12:15         ` Vladimir Kondratiev
2012-12-10 12:33           ` 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=543D170A.6060709@gmail.com \
    --to=xose.vazquez@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=qca_vkondrat@qca.qualcomm.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.