linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Sven Eckelmann <sven.eckelmann@openmesh.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
	"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Subject: Re: ath: Incorrect regDomainPairs/allCountries settings
Date: Wed, 1 Nov 2017 10:58:22 +0000	[thread overview]
Message-ID: <87k1zaxo36.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1693831.JqVThioVz9@bentobox> (Sven Eckelmann's message of "Tue, 08 Aug 2017 11:45:38 +0200")

Sven Eckelmann <sven.eckelmann@openmesh.com> writes:

> I just had two inquiries from Vietnam and Singapore regarding the used CT=
L=20
> limits by Atheros based chips. I've checked through the code and noticed =
that=20
> regd_common.h assigns SG to APL6_WORLD and VN to NULL1_WORLD.
>
>  * SG: APL6_WORLD
>    - 2.4GHz: CTL_ETSI
>    -   5GHz: CTL_ETSI
>  * VN: NULL1_WORLD
>    - 2.4GHz: CTL_ETSI
>    -   5GHz: NO_CTL
>
> But I personally would have expected that both countries would be assigne=
d to=20
> FCC3_WORLD.
>
>  * FCC3_WORLD
>    - 2.4GHz: CTL_ETSI
>    -   5GHz: CTL_FCC
>
> Maybe someone from QCA can check with their internal driver.

I asked around and got this answer:

"Correct, internal code base assigns SG and VN to FCC3_WORLD regdomain,
CTL limits are assigned accordingly as he mentioned."

--=20
Kalle Valo=

      reply	other threads:[~2017-11-01 10:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-08  9:45 ath: Incorrect regDomainPairs/allCountries settings Sven Eckelmann
2017-11-01 10:58 ` Kalle Valo [this message]

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=87k1zaxo36.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@do-not-panic.com \
    --cc=sven.eckelmann@openmesh.com \
    /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).