From: "Bjørn Mork" <bjorn@mork.no>
To: "Luis R. Rodriguez" <mcgrof@frijolero.org>
Cc: wireless-regdb@lists.infradead.org,
"Robert Grønning" <slimg@iggu.org>,
linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
"Michael Green" <green@qca.qualcomm.com>,
"Tomas Winkler" <tomas.winkler@intel.com>
Subject: Re: [wireless-regdb] wireless-regdb: Update regulatory rules for Norway (NO)
Date: Wed, 08 Feb 2012 09:55:09 +0100 [thread overview]
Message-ID: <87mx8t7lhu.fsf@nemi.mork.no> (raw)
In-Reply-To: <CAB=NE6VVcQgum4mQ5eooS2yXo-NNXHvujsUwpbEwNdQQSreaBA@mail.gmail.com> (Luis R. Rodriguez's message of "Tue, 7 Feb 2012 12:37:59 -0800")
"Luis R. Rodriguez" <mcgrof@frijolero.org> writes:
> On Tue, Feb 7, 2012 at 11:54 AM, John W. Linville
> <linville@tuxdriver.com> wrote:
>> Well, sorry for the delay... I will take this silence as "no
>> objection". :-)
>
> Sorry, I did get a reply by Michael Green on 11/28/2011 but I never
> followed up with the list. Apologies as well with the delay, but here
> is our review.
>
> The European Union has some harmonized European radio conformance spec
> and QCA's interpretation and position is that that spec overrides
> deviations for end products for specific countries like the one being
> recommended for Norway. This also means that QCA does not deviate for
> EU countries on specs, even if countries have their own quirks, for
> any country in the EU.
>
> Supporting changes like these are a deviation from what QCA is used to
> using and testing and we unfortunately cannot verify any individual
> country specific changes like the one proposed for the EU. It is also
> our sentiment that we stand to gain more if we simply unify the EU
> requirements through the harmonized spec, it provides simplicity, its
> what we use and we can help in that regards. If wireless-regdb decides
> to take a different path we simply will not be able to verify and
> validate these changes. I'd be surprised if any other 802.11 vendor
> differs from this position.
I fully agree.
However, this should really be taken up with the regulatory bodies
deviating from the conformance spec. It cannot simply be fixed by
ignoring it in the regulatory database. That just implies that the
regulatory database deviates from the regulations, and that's no good...
But if you want to put this change on hold and work towards harmonizing
the regulations instead, then I'm fine with that solution.
Bjørn
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
next prev parent reply other threads:[~2012-02-08 8:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 14:13 [wireless-regdb] wireless-regdb: Update regulatory rules for Norway (NO) Bjørn Mork
2011-11-28 18:19 ` John W. Linville
2012-02-07 19:54 ` John W. Linville
2012-02-07 20:37 ` Luis R. Rodriguez
[not found] ` <201202072247.08793.david.goodenough@btconnect.com>
2012-02-07 23:05 ` Luis R. Rodriguez
2012-02-08 8:55 ` Bjørn Mork [this message]
2012-02-07 20:41 ` Bjørn Mork
2012-02-07 20:42 ` John W. Linville
-- strict thread matches above, loose matches on Subject: below --
2011-06-23 17:58 Robert Grønning
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=87mx8t7lhu.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=green@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@frijolero.org \
--cc=slimg@iggu.org \
--cc=tomas.winkler@intel.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