All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
To: "John W. Linville" <linville@tuxdriver.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: Thu, 7 Feb 2013 11:27:28 +0200	[thread overview]
Message-ID: <4125342.NcrOy0nJDp@lx-vladimir> (raw)
In-Reply-To: <20130206183940.GG2148@tuxdriver.com>

On Wednesday, February 06, 2013 01:39:41 PM John W. Linville wrote:
> On Mon, Dec 10, 2012 at 05:48:24PM +0200, Vladimir Kondratiev wrote:
> > 
> > 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
> > 
<snip>
> > +
> > +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?

Sure it is not! Problem is, entry for Serbia was not exist in original db.txt

I added 60G data as per regulatory document; but then missed data
for 2.4/5 bands leads to this problem...

By the way, same problem is for AD (Andorra)

Correct solution would be, as you mentioned below, to add data for Serbia.
I'm not sure what is correct rule set.
Most of ETSI countries (but not all!) have rule set like this:

country AT: DFS-ETSI
	(2402 - 2482 @ 40), (N/A, 20)
	(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

I am not sure we can apply this for Andorra and Serbia since I see exceptions -
some ETSI countries have different rules. See BG, CZ, DE, GE, NL, TR, UA.

> 
> 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
> 

WARNING: multiple messages have this Message-ID (diff)
From: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org,
	Johannes Berg <johannes@sipsolutions.net>,
	wireless-regdb@lists.infradead.org, robertbasic.com@gmail.com
Subject: Re: [wireless-regdb] [PATCH v2] wireless-regdb: add regulatory rule for ETSI members on 60gHz band
Date: Thu, 7 Feb 2013 11:27:28 +0200	[thread overview]
Message-ID: <4125342.NcrOy0nJDp@lx-vladimir> (raw)
In-Reply-To: <20130206183940.GG2148@tuxdriver.com>

On Wednesday, February 06, 2013 01:39:41 PM John W. Linville wrote:
> On Mon, Dec 10, 2012 at 05:48:24PM +0200, Vladimir Kondratiev wrote:
> > 
> > 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
> > 
<snip>
> > +
> > +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?

Sure it is not! Problem is, entry for Serbia was not exist in original db.txt

I added 60G data as per regulatory document; but then missed data
for 2.4/5 bands leads to this problem...

By the way, same problem is for AD (Andorra)

Correct solution would be, as you mentioned below, to add data for Serbia.
I'm not sure what is correct rule set.
Most of ETSI countries (but not all!) have rule set like this:

country AT: DFS-ETSI
	(2402 - 2482 @ 40), (N/A, 20)
	(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

I am not sure we can apply this for Andorra and Serbia since I see exceptions -
some ETSI countries have different rules. See BG, CZ, DE, GE, NL, TR, UA.

> 
> 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
> 

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


  reply	other threads:[~2013-02-07  9:27 UTC|newest]

Thread overview: 16+ 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 10:21     ` [wireless-regdb] " Johannes Berg
2012-12-10 11:09     ` Vladimir Kondratiev
2012-12-10 11:31       ` Johannes Berg
2012-12-10 11:31         ` [wireless-regdb] " Johannes Berg
2012-12-10 12:15         ` Vladimir Kondratiev
2012-12-10 12:33           ` Johannes Berg
2012-12-10 12:33             ` [wireless-regdb] " Johannes Berg
2012-12-10 15:48             ` [PATCH v2] " Vladimir Kondratiev
2013-02-06 18:39               ` John W. Linville
2013-02-06 18:39                 ` [wireless-regdb] " John W. Linville
2013-02-07  9:27                 ` Vladimir Kondratiev [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=4125342.NcrOy0nJDp@lx-vladimir \
    --to=qca_vkondrat@qca.qualcomm.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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 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.