From: Seth Forshee <seth.forshee@canonical.com>
To: Sven Eckelmann <sven.eckelmann@openmesh.com>
Cc: linux-wireless@vger.kernel.org,
wireless-regdb@lists.infradead.org,
Simon Wunderlich <simon.wunderlich@openmesh.com>,
Shashidhar Lakkavalli <shashidhar.lakkavalli@openmesh.com>
Subject: Re: [PATCH 1/2] wireless-regdb: Sync FR with ETSI EN 301 893 V2.1.1 (2017-05)
Date: Fri, 28 Sep 2018 09:15:20 -0500 [thread overview]
Message-ID: <20180928141520.GS16752@ubuntu-xps13> (raw)
In-Reply-To: <20180917074212.6739-1-sven.eckelmann@openmesh.com>
On Mon, Sep 17, 2018 at 09:42:11AM +0200, Sven Eckelmann wrote:
> The documents
> https://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf
> and
> https://www.anfr.fr/fileadmin/mediatheque/documents/controle/20171127ANFR_-_ficheRLAN_5GHz.pdf
> show that the limits for the 5GHz bands are out of date:
>
> * frequencies don't match the official limits
> * 5150 - 5350 MHz is not for outdoor usage
> * 5150 - 5250 MHz only usage is allowed to use up to 23 dBm (200 mW) even
> without TPC
>
> Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com>
Applied both patches, thanks!
Seth
WARNING: multiple messages have this Message-ID (diff)
From: Seth Forshee <seth.forshee@canonical.com>
To: Sven Eckelmann <sven.eckelmann@openmesh.com>
Cc: wireless-regdb@lists.infradead.org,
linux-wireless@vger.kernel.org,
Simon Wunderlich <simon.wunderlich@openmesh.com>,
Shashidhar Lakkavalli <shashidhar.lakkavalli@openmesh.com>
Subject: Re: [wireless-regdb] [PATCH 1/2] wireless-regdb: Sync FR with ETSI EN 301 893 V2.1.1 (2017-05)
Date: Fri, 28 Sep 2018 09:15:20 -0500 [thread overview]
Message-ID: <20180928141520.GS16752@ubuntu-xps13> (raw)
In-Reply-To: <20180917074212.6739-1-sven.eckelmann@openmesh.com>
On Mon, Sep 17, 2018 at 09:42:11AM +0200, Sven Eckelmann wrote:
> The documents
> https://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf
> and
> https://www.anfr.fr/fileadmin/mediatheque/documents/controle/20171127ANFR_-_ficheRLAN_5GHz.pdf
> show that the limits for the 5GHz bands are out of date:
>
> * frequencies don't match the official limits
> * 5150 - 5350 MHz is not for outdoor usage
> * 5150 - 5250 MHz only usage is allowed to use up to 23 dBm (200 mW) even
> without TPC
>
> Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com>
Applied both patches, thanks!
Seth
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
next prev parent reply other threads:[~2018-09-28 14:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 7:42 [PATCH 1/2] wireless-regdb: Sync FR with ETSI EN 301 893 V2.1.1 (2017-05) Sven Eckelmann
2018-09-17 7:42 ` [wireless-regdb] " Sven Eckelmann
2018-09-17 7:42 ` [PATCH 2/2] wireless-regdb: Sync DE " Sven Eckelmann
2018-09-17 7:42 ` [wireless-regdb] " Sven Eckelmann
2018-09-17 7:44 ` Sven Eckelmann
2018-09-17 7:44 ` [wireless-regdb] " Sven Eckelmann
2018-09-17 7:45 ` [PATCH v2 " Sven Eckelmann
2018-09-17 7:45 ` [wireless-regdb] " Sven Eckelmann
2018-09-28 14:15 ` Seth Forshee [this message]
2018-09-28 14:15 ` [wireless-regdb] [PATCH 1/2] wireless-regdb: Sync FR " 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=20180928141520.GS16752@ubuntu-xps13 \
--to=seth.forshee@canonical.com \
--cc=linux-wireless@vger.kernel.org \
--cc=shashidhar.lakkavalli@openmesh.com \
--cc=simon.wunderlich@openmesh.com \
--cc=sven.eckelmann@openmesh.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.