linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Mykyta Iziumtsev <mykyta.iziumtsev@gmail.com>
Cc: wireless-regdb@lists.infradead.org,
	Arend van Spriel <arend@broadcom.com>,
	linux-wireless@vger.kernel.org,
	"Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>,
	Pavel Chernyshev <pchernyshev@gmail.com>,
	Andrew Bordunov <andrew.bordunov@gmail.com>
Subject: Re: [PATCH v2] wireless-regdb: Update regulations for Ukraine
Date: Thu, 6 Dec 2012 10:04:44 +0100	[thread overview]
Message-ID: <20121206090443.GD2502@redhat.com> (raw)
In-Reply-To: <CAHc5FiWpUBUDh=8tDaaLRh9fHXT-k3EBj+KdoOGoR=BhYhzrVQ@mail.gmail.com>

On Tue, Dec 04, 2012 at 11:27:55PM +0100, Mykyta Iziumtsev wrote:
> Add 5GHz band and mark 2.4GHz and 5GHz as NO-OUTDOOR according to
> "Рішення про затвердження Переліку радіоелектронних засобів
> та випромінювальних пристроїв, для експлуатації яких не потрібні
> дозволи на експлуатацію" from 27 May 2010.
> 
> Ref:
> * #914 / 06 Sep 2007: http://www.ucrf.gov.ua/uk/doc/nkrz/1196068874
> * #1174 / 23 Oct 2008: http://www.nkrz.gov.ua/uk/activities/ruling/1225269361
> (appendix 8)

Since regulatory maintainer does not understand Ukrainian,
there is little chance to get this patch applied.

IMHO this can be solved by:

* having official English translation of those document on gov.ua site
* provide patch by wlan chip vendor, confirmed by legal deparament of
  the vendor
* provide patch by some known Ukrainian kernel developer, someone
  who is know by regulatory maintainer and can be trust

Stanislaw

  reply	other threads:[~2012-12-06  9:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-04 22:27 [PATCH v2] wireless-regdb: Update regulations for Ukraine Mykyta Iziumtsev
2012-12-06  9:04 ` Stanislaw Gruszka [this message]
2012-12-08  9:13   ` Andrii Bordunov
2012-12-08  9:55   ` Arend van Spriel

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=20121206090443.GD2502@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=andrew.bordunov@gmail.com \
    --cc=arend@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mykyta.iziumtsev@gmail.com \
    --cc=pchernyshev@gmail.com \
    --cc=rodrigue@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 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).