linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	wireless-regdb@lists.infradead.org,
	linux-wireless@vger.kernel.org, robertbasic.com@gmail.com
Subject: Re: [PATCH v2] wireless-regdb: add regulatory rule for ETSI members on 60gHz band
Date: Wed, 6 Feb 2013 13:39:41 -0500	[thread overview]
Message-ID: <20130206183940.GG2148@tuxdriver.com> (raw)
In-Reply-To: <2028055.RB8DPWJWyd@lx-vladimir>

On Mon, Dec 10, 2012 at 05:48:24PM +0200, Vladimir Kondratiev wrote:

<snip>

> and, patch:
> 
> From 69554755daf74ba32ebe0d028de57ed45003e0ab Mon Sep 17 00:00:00 2001
> From: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
> Date: Mon, 10 Dec 2012 17:43:53 +0200
> Subject: [PATCH v2] wireless-regdb: add regulatory rule for ETSI members on
>  60GHz band
> 
> 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
> 
> 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:
> 
> The EU member states:
> Austria, Belgium, Bulgaria, Cyprus, Czech Republic, Denmark,
> Estonia, Finland, France, Germany, Greece, Hungary, Ireland,
> Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands,
> Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden,
> United Kingdom
> 
> plus:
> Andorra, Iceland, Norway, Switzerland, Croatia,
> Bosnia and Herzegovina, Serbia, Macedonia,
> Ukraine, Turkey, Georgia
> 
> Final country codes list:

<snip>

> RS

<snip>

> @@ -575,6 +639,12 @@ country RO: DFS-ETSI
>  	(5170 - 5250 @ 40), (N/A, 20)
>  	(5250 - 5330 @ 40), (N/A, 20), DFS
>  	(5490 - 5710 @ 40), (N/A, 27), DFS
> +        # 60 gHz band channels 1-4, ref: Etsi En 302 567
> +        (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR
> +
> +country RS:
> +        # 60 gHz band channels 1-4, ref: Etsi En 302 567
> +        (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR
>  
>  country RU:
>  	(2402 - 2482 @ 40), (N/A, 20)

Is this really the correct rule for RS (Serbia)?  Only 60 GHz is allowed there?

The bug reporter here seems to disagree...

https://bugzilla.redhat.com/show_bug.cgi?id=908267

What should the rules really be for Serbia?

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2013-02-06 18:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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
2012-12-10 15:48             ` [PATCH v2] " Vladimir Kondratiev
2013-02-06 18:39               ` John W. Linville [this message]
2013-02-07  9:27                 ` Vladimir Kondratiev
2012-12-23  9:36 ` [PATCH] wireless-regdb: add regulatory rule for US " Vladimir Kondratiev

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=20130206183940.GG2148@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=qca_vkondrat@qca.qualcomm.com \
    --cc=robertbasic.com@gmail.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;
as well as URLs for NNTP newsgroup(s).