From: Sven Eckelmann <hidden> Date: 2018-03-01 14:20:29
The mappings from ath was not synced with the QCA driver since 2009. Only
two minor fixes were integrated in 2011. Since then, a lot of regd changes
were integrated in the close source QCA driver which are now used but not
supported by the Open Source driver. This either prevents the use of the
OSS driver on such devices or the wrong conformance test limits (CTLs) may
be used.
To get the integrated we would first get access to the closed source QCA
driver and a special OSS-NDA with QCA. This doesn't seem to be possible at
the moment and thus other sources for the changes have to be found. One of
them is the qcacld-2.0 source repository [1] which contains the QCA
regdomain.h and regdomain_common.h which was relicensed by QCA as ISC. It
isn't the newest version from the QCA driver but at least received some
updates which are not present in ath's regd.
This repository [1] (commit 48f9ab5d5c161549be098997fa0e3602c1547213 to be
more precise) was now used to find differences and ad some missing
mappings.
The title of the mappings describe what exactly was changed. The "Add
regulatory mapping for" patches introduce new country codes/mappings and
thus don't change old mappings. The "Add regulatory mapping for" patches
are similar but for regulatory code mappings instead of country code
mappings.
More interesting might be the "Map XXXX to YYYY" patches because they
modify already existing mappings. The result are following changes to the
selected CTLs:
* CTRY_ALBANIA: 5GHz: NO_CTL -> ETSI
* CTRY_ALGERIA: 5GHz: NO_CTL -> ETSI
* CTRY_BANGLADESH: 5GHz: NO_CTL -> FCC
* CTRY_BRUNEI_DARUSSALAM: 5GHz: FCC -> ETSI
* CTRY_HONDURAS: 5GHz: NO_CTL -> FCC
* CTRY_INDONESIA: 5GHz: NO_CTL -> FCC
* CTRY_ISRAEL: 5GHz: NO_CTL -> ETSI
* CTRY_KOREA_NORTH: 2.4GHz: ETSI -> MKK
* CTRY_KOREA_ROC: 2.4GHz: ETSI -> MKK
* CTRY_KOREA_ROC3: 2.4GHz: ETSI -> MKK
* CTRY_LEBANON: 5GHz: NO_CTL -> FCC
* CTRY_MACEDONIA: 5GHz: NO_CTL -> ETSI
* CTRY_MALAYSIA: 5GHz: ETSI -> FCC
* CTRY_MEXICO: 2.4GHz: FCC-> ETSI
* CTRY_PAKISTAN: 5GHz: NO_CTL -> FCC
* CTRY_ROMANIA: 5GHz: NO_CTL -> ETSI
* CTRY_RUSSIA: 5GHz: NO_CTL -> ETSI
* CTRY_SAUDI_ARABIA: 5GHz: NO_CTL -> FCC
* CTRY_SINGAPORE: 5GHz: ETSI -> FCC
* CTRY_UKRAINE: 5GHz: NO_CTL -> ETSI
* CTRY_UAE: 5GHz: NO_CTL -> ETSI
* CTRY_VIET_NAM: 5GHz: NO_CTL -> ETSI
* CTRY_ZIMBABWE: 5GHz: NO_CTL -> ETSI
Btw. I have not removed CTRY_SERBIA_MONTENEGRO, CTRY_KOREA_ROC2 or
APL2_APLD because this might break devices which have these programmed in
the EEPROM. And I have not added APL11_FCCA, APL12_WORLD and CTRY_MALDIVES
because only the code was in the qcacld-2.0 source code but not the actual
mapping.
I am relative confident that QCA also has following extra countries:
* Afghanistan
* American Samoa
* Anguilla
* Bhutan
* Burkina Faso
* Cayman Islands
* Central Africa Republic
* Chad
* Christmas Islands
* Dominica
* Ethiopia
* French Guiana
* French Polynesia
* Ghana
* Guadeloupe
* Guyana
* Cote d'Ivoire
* Lesotho
* Malawi
* Maldives
* Marshall Islands
* Martinique
* Mauitania
* Mayotte
* Micronesia
* Moldova
* Mongolia
* Namibia
* Nigeria
* Northern Mariana Islands
* Palau
* Reunion
* St Barthelemy
* St Kitts Nevis
* St Lucia
* St Martin
* St Pierre Miquelon
* St Vincent Grenadiens
* Samoa
* Senegal
* Suriname
* Togo
* Turks Caicos
* Vanuatu
* Virgin Islands
* Wallis Futuna
+ a lot of extra regdomain codes (0x15, 0x16, 0x17, 0x18, 0x19, 0x3c, 0x4f,
0x51, 0x57, 0x59) and the corresponding mappings.
There might be even a lot more. But we will miss out on them unless QCA
somehow opensources their current:
* regdomain_common.h or at least:
- enum EnumRd
- ahCmnRegDomainPairs
- ahCmnAllCountries
- ahCmnRegDomains
* regdomain.h or at least:
- enum CountryCode
Kind regards,
Sven
[1] https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0
Sven Eckelmann (52):
ath: Add regulatory mapping for Bahamas
ath: Add regulatory mapping for Bermuda
ath: Add regulatory mapping for Japan (J56)
ath: Add regulatory mapping for Japan KDDI
ath: Add regulatory mapping for Kenya
ath: Add regulatory mapping for Mauritius
ath: Add regulatory mapping for Montenegro
ath: Add regulatory mapping for Nicaragua
ath: Add regulatory mapping for Paraguya
ath: Add regulatory mapping for Rwanda
ath: Add regulatory mapping for Serbia
ath: Add regulatory mapping for Tanzania
ath: Add regulatory mapping for Uganda
ath: Add regulatory mapping for United States for AP
ath: Add regulatory mapping for APL2_FCCA
ath: Add regulatory mapping for APL10_MKKC
ath: Add regulatory mapping for APL13_WORLD
ath: Add regulatory mapping for ETSI8_WORLD
ath: Add regulatory mapping for ETSI9_WORLD
ath: Add regulatory mapping for FCC3_ETSIC
ath: Switch APL9_WORLD to 2.4GHz MKK CTL
ath: Map Albania to ETSI1_WORLD
ath: Map Algeria to APL13_WORLD
ath: Map Australia to FCC3_WORLD
ath: Map Bangladesh to APL1_WORLD
ath: Map Brunei Darussalam to APL6_WORLD
ath: Map Bulgaria to ETSI1_WORLD
ath: Map Colombia to FCC1_FCCA
ath: Map Czech to ETSI1_WORLD
ath: Map Honduras to FCC3_WORLD
ath: Map Indonesia to APL2_WORLD
ath: Map Isreal to ETSI3_WORLD
ath: Map Japan to MKK5_MKKA2
ath: Map South Korea to APL10_MKKC
ath: Map Lebanon to APL1_WORLD
ath: Map Macedonia to ETSI1_WORLD
ath: Map Malasia to FCC1_WORLD
ath: Map Mexico to FCC1_WORLD
ath: Map New Zealand to FCC3_ETSIC
ath: Map Pakistan to APL1_WORLD
ath: Map Peru to APL1_WORLD
ath: Map Philippines to FCC3_WORLD
ath: Map Romania to ETSI1_WORLD
ath: Map Russia to ETSI8_WORLD
ath: Map Saudi Arabia to FCC2_WORLD
ath: Map Singapore to FCC3_WORLD
ath: Map Taiwan to APL7_FCCA
ath: Map Ukraine to ETSI9_WORLD
ath: Map U.A.E. to ETSI1_WORLD
ath: Map Venezuela to FCC1_WORLD
ath: Map Vietnam to ETSI3_WORLD
ath: Map Zimbabwe to ETSI1_WORLD
drivers/net/wireless/ath/regd.h | 10 ++++
drivers/net/wireless/ath/regd_common.h | 98 ++++++++++++++++++++++------------
2 files changed, 73 insertions(+), 35 deletions(-)
--
2.11.0
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:20:31
The country code is used by the ath to detect the ISO 3166-1 alpha-2 name
and to select the correct conformance test limits (CTL) for a country. If
the country isn't available and it is still programmed in the EEPROM then
it will cause an error and stop the initialization with:
Invalid EEPROM contents
The current CTL mappings for this country are:
* 2.4GHz: ETSI
* 5GHz: FCC
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd.h | 1 +
drivers/net/wireless/ath/regd_common.h | 1 +
2 files changed, 2 insertions(+)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:20:33
The country code is used by the ath to detect the ISO 3166-1 alpha-2 name
and to select the correct conformance test limits (CTL) for a country. If
the country isn't available and it is still programmed in the EEPROM then
it will cause an error and stop the initialization with:
Invalid EEPROM contents
The current CTL mappings for this country are:
* 2.4GHz: FCC
* 5GHz: FCC
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd.h | 1 +
drivers/net/wireless/ath/regd_common.h | 1 +
2 files changed, 2 insertions(+)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:20:36
The country code is used by the ath to detect the ISO 3166-1 alpha-2 name
and to select the correct conformance test limits (CTL) for a country. If
the country isn't available and it is still programmed in the EEPROM then
it will cause an error and stop the initialization with:
Invalid EEPROM contents
The current CTL mappings for this country are:
* 2.4GHz: FCC
* 5GHz: MKK
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 3 +++
1 file changed, 3 insertions(+)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:20:38
The country code is used by the ath to detect the ISO 3166-1 alpha-2 name
and to select the correct conformance test limits (CTL) for a country. If
the country isn't available and it is still programmed in the EEPROM then
it will cause an error and stop the initialization with:
Invalid EEPROM contents
The current CTL mappings for this country are:
* 2.4GHz: MKK
* 5GHz: MKK
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd.h | 1 +
drivers/net/wireless/ath/regd_common.h | 1 +
2 files changed, 2 insertions(+)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:20:41
The country code is used by the ath to detect the ISO 3166-1 alpha-2 name
and to select the correct conformance test limits (CTL) for a country. If
the country isn't available and it is still programmed in the EEPROM then
it will cause an error and stop the initialization with:
Invalid EEPROM contents
The current CTL mappings for this country are:
* 2.4GHz: ETSI
* 5GHz: FCC
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 1 +
1 file changed, 1 insertion(+)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:20:43
The country code is used by the ath to detect the ISO 3166-1 alpha-2 name
and to select the correct conformance test limits (CTL) for a country. If
the country isn't available and it is still programmed in the EEPROM then
it will cause an error and stop the initialization with:
Invalid EEPROM contents
The current CTL mappings for this country are:
* 2.4GHz: ETSI
* 5GHz: ETSI
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd.h | 1 +
drivers/net/wireless/ath/regd_common.h | 1 +
2 files changed, 2 insertions(+)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:20:46
The country code is used by the ath to detect the ISO 3166-1 alpha-2 name
and to select the correct conformance test limits (CTL) for a country. If
the country isn't available and it is still programmed in the EEPROM then
it will cause an error and stop the initialization with:
Invalid EEPROM contents
The current CTL mappings for this country are:
* 2.4GHz: ETSI
* 5GHz: ETSI
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd.h | 1 +
drivers/net/wireless/ath/regd_common.h | 1 +
2 files changed, 2 insertions(+)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:20:48
The country code is used by the ath to detect the ISO 3166-1 alpha-2 name
and to select the correct conformance test limits (CTL) for a country. If
the country isn't available and it is still programmed in the EEPROM then
it will cause an error and stop the initialization with:
Invalid EEPROM contents
The current CTL mappings for this country are:
* 2.4GHz: FCC
* 5GHz: FCC
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 1 +
1 file changed, 1 insertion(+)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:20:51
The country code is used by the ath to detect the ISO 3166-1 alpha-2 name
and to select the correct conformance test limits (CTL) for a country. If
the country isn't available and it is still programmed in the EEPROM then
it will cause an error and stop the initialization with:
Invalid EEPROM contents
The current CTL mappings for this country are:
* 2.4GHz: ETSI
* 5GHz: FCC
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 1 +
1 file changed, 1 insertion(+)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:20:53
The country code is used by the ath to detect the ISO 3166-1 alpha-2 name
and to select the correct conformance test limits (CTL) for a country. If
the country isn't available and it is still programmed in the EEPROM then
it will cause an error and stop the initialization with:
Invalid EEPROM contents
The current CTL mappings for this country are:
* 2.4GHz: ETSI
* 5GHz: FCC
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd.h | 1 +
drivers/net/wireless/ath/regd_common.h | 1 +
2 files changed, 2 insertions(+)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:20:56
The country code is used by the ath to detect the ISO 3166-1 alpha-2 name
and to select the correct conformance test limits (CTL) for a country. If
the country isn't available and it is still programmed in the EEPROM then
it will cause an error and stop the initialization with:
Invalid EEPROM contents
The current CTL mappings for this country are:
* 2.4GHz: ETSI
* 5GHz: ETSI
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd.h | 1 +
drivers/net/wireless/ath/regd_common.h | 1 +
2 files changed, 2 insertions(+)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:20:58
The country code is used by the ath to detect the ISO 3166-1 alpha-2 name
and to select the correct conformance test limits (CTL) for a country. If
the country isn't available and it is still programmed in the EEPROM then
it will cause an error and stop the initialization with:
Invalid EEPROM contents
The current CTL mappings for this country are:
* 2.4GHz: ETSI
* 5GHz: FCC
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd.h | 1 +
drivers/net/wireless/ath/regd_common.h | 1 +
2 files changed, 2 insertions(+)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:21:01
The country code is used by the ath to detect the ISO 3166-1 alpha-2 name
and to select the correct conformance test limits (CTL) for a country. If
the country isn't available and it is still programmed in the EEPROM then
it will cause an error and stop the initialization with:
Invalid EEPROM contents
The current CTL mappings for this country are:
* 2.4GHz: ETSI
* 5GHz: FCC
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd.h | 1 +
drivers/net/wireless/ath/regd_common.h | 1 +
2 files changed, 2 insertions(+)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:21:03
The country code is used by the ath to detect the ISO 3166-1 alpha-2 name
and to select the correct conformance test limits (CTL) for a country. If
the country isn't available and it is still programmed in the EEPROM then
it will cause an error and stop the initialization with:
Invalid EEPROM contents
The current CTL mappings for this country are:
* 2.4GHz: FCC
* 5GHz: FCC
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd.h | 1 +
drivers/net/wireless/ath/regd_common.h | 1 +
2 files changed, 2 insertions(+)
@@ -478,6 +478,7 @@ static struct country_code_to_enum_rd allCountries[] = {{CTRY_UAE,NULL1_WORLD,"AE"},{CTRY_UNITED_KINGDOM,ETSI1_WORLD,"GB"},{CTRY_UNITED_STATES,FCC3_FCCA,"US"},+{CTRY_UNITED_STATES2,FCC6_FCCA,"US"},/* This "PS" is for US public safety actually... to support this we*wouldneedtoassignnewspecialalpha2toCRDAdbaswiththeworld*regdomainanduseanotheralpha2*/
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:21:06
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't available and
it is still programmed in the EEPROM then it will cause an error and stop
the initialization with:
Invalid EEPROM contents
The current CTL mappings for this regdomain code are:
* 2.4GHz: FCC
* 5GHz: FCC
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 ++
1 file changed, 2 insertions(+)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:21:08
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't available and
it is still programmed in the EEPROM then it will cause an error and stop
the initialization with:
Invalid EEPROM contents
The current CTL mappings for this regdomain code are:
* 2.4GHz: MKK
* 5GHz: ETSI
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 ++
1 file changed, 2 insertions(+)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:21:11
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't available and
it is still programmed in the EEPROM then it will cause an error and stop
the initialization with:
Invalid EEPROM contents
The current CTL mappings for this regdomain code are:
* 2.4GHz: ETSI
* 5GHz: ETSI
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 ++
1 file changed, 2 insertions(+)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:21:13
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't available and
it is still programmed in the EEPROM then it will cause an error and stop
the initialization with:
Invalid EEPROM contents
The current CTL mappings for this regdomain code are:
* 2.4GHz: ETSI
* 5GHz: ETSI
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 ++
1 file changed, 2 insertions(+)
@@ -183,6 +184,7 @@ static struct reg_dmn_pair_mapping regDomainPairs[] = {{ETSI4_WORLD,CTL_ETSI,CTL_ETSI},{ETSI5_WORLD,CTL_ETSI,CTL_ETSI},{ETSI6_WORLD,CTL_ETSI,CTL_ETSI},+{ETSI8_WORLD,CTL_ETSI,CTL_ETSI},/* XXX: For ETSI3_ETSIA, Was NO_CTL meant for the 2 GHz band ? */{ETSI3_ETSIA,CTL_ETSI,CTL_ETSI},
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:21:16
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't available and
it is still programmed in the EEPROM then it will cause an error and stop
the initialization with:
Invalid EEPROM contents
The current CTL mappings for this regdomain code are:
* 2.4GHz: ETSI
* 5GHz: ETSI
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 ++
1 file changed, 2 insertions(+)
@@ -185,6 +186,7 @@ static struct reg_dmn_pair_mapping regDomainPairs[] = {{ETSI5_WORLD,CTL_ETSI,CTL_ETSI},{ETSI6_WORLD,CTL_ETSI,CTL_ETSI},{ETSI8_WORLD,CTL_ETSI,CTL_ETSI},+{ETSI9_WORLD,CTL_ETSI,CTL_ETSI},/* XXX: For ETSI3_ETSIA, Was NO_CTL meant for the 2 GHz band ? */{ETSI3_ETSIA,CTL_ETSI,CTL_ETSI},
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:21:18
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't available and
it is still programmed in the EEPROM then it will cause an error and stop
the initialization with:
Invalid EEPROM contents
The current CTL mappings for this regdomain code are:
* 2.4GHz: ETSI
* 5GHz: FCC
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 ++
1 file changed, 2 insertions(+)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:21:21
The regdomain code 0x5E was switched from ETSI conformance test limits
(CTL) on 2.4GHz to MKK. This only affects the different South Korea country
codes.
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:21:23
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
The CTL mappings for this regdomain code were now changed to:
* 2.4GHz: ETSI
* 5GHz: NO_CTL -> ETSI
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:21:26
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
The CTL mappings for this regdomain code were now changed to:
* 2.4GHz: ETSI
* 5GHz: NO_CTL -> ETSI
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:21:28
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
This change itself doesn't change the selected CTL of this country and is
only required to stay in sync with the QCA mappings.
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:21:30
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
The CTL mappings for this regdomain code were now changed to:
* 2.4GHz: ETSI
* 5GHz: NO_CTL -> FCC
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:21:33
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
The CTL mappings for this regdomain code were now changed to:
* 2.4GHz: ETSI
* 5GHz: FCC -> ETSI
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:21:36
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
This change itself doesn't change the selected CTL of this country and is
only required to stay in sync with the QCA mappings.
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:21:39
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
This change itself doesn't change the selected CTL of this country and is
only required to stay in sync with the QCA mappings.
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:21:41
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
This change itself doesn't change the selected CTL of this country and is
only required to stay in sync with the QCA mappings.
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:21:44
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
The CTL mappings for this regdomain code were now changed to:
* 2.4GHz: ETSI
* 5GHz: NO_CTL -> FCC
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:21:46
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
The CTL mappings for this regdomain code were now changed to:
* 2.4GHz: ETSI
* 5GHz: NO_CTL -> FCC
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:21:48
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
The CTL mappings for this regdomain code were now changed to:
* 2.4GHz: ETSI
* 5GHz: NO_CTL -> ETSI
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:21:51
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
This change itself doesn't change the selected CTL of this country and is
only required to stay in sync with the QCA mappings.
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:21:53
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
This change itself doesn't change the selected CTL of this country and is
only required to stay in sync with the QCA mappings.
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:21:56
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
The CTL mappings for this regdomain code were now changed to:
* 2.4GHz: ETSI
* 5GHz: NO_CTL -> FCC
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:21:58
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
The CTL mappings for this regdomain code were now changed to:
* 2.4GHz: ETSI
* 5GHz: NO_CTL -> ETSI
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:22:01
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
The CTL mappings for this regdomain code were now changed to:
* 2.4GHz: ETSI
* 5GHz: ETSI -> FCC
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:22:03
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
The CTL mappings for this regdomain code were now changed to:
* 2.4GHz: FCC-> ETSI
* 5GHz: FCC
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:22:06
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
This change itself doesn't change the selected CTL of this country and is
only required to stay in sync with the QCA mappings.
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:22:08
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
The CTL mappings for this regdomain code were now changed to:
* 2.4GHz: ETSI
* 5GHz: NO_CTL -> FCC
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:22:11
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
This change itself doesn't change the selected CTL of this country and is
only required to stay in sync with the QCA mappings.
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:22:13
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
This change itself doesn't change the selected CTL of this country and is
only required to stay in sync with the QCA mappings.
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:22:15
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
The CTL mappings for this regdomain code were now changed to:
* 2.4GHz: ETSI
* 5GHz: NO_CTL -> ETSI
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:22:18
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
The CTL mappings for this regdomain code were now changed to:
* 2.4GHz: ETSI
* 5GHz: NO_CTL -> ETSI
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:22:21
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
The CTL mappings for this regdomain code were now changed to:
* 2.4GHz: ETSI
* 5GHz: NO_CTL -> FCC
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:22:23
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
The CTL mappings for this regdomain code were now changed to:
* 2.4GHz: ETSI
* 5GHz: ETSI -> FCC
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:22:26
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
This change itself doesn't change the selected CTL of this country and is
only required to stay in sync with the QCA mappings.
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:22:28
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
The CTL mappings for this regdomain code were now changed to:
* 2.4GHz: ETSI
* 5GHz: NO_CTL -> ETSI
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:22:31
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
The CTL mappings for this regdomain code were now changed to:
* 2.4GHz: ETSI
* 5GHz: NO_CTL -> ETSI
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:22:33
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
This change itself doesn't change the selected CTL of this country and is
only required to stay in sync with the QCA mappings.
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:22:35
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
The CTL mappings for this regdomain code were now changed to:
* 2.4GHz: ETSI
* 5GHz: NO_CTL -> ETSI
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Sven Eckelmann <hidden> Date: 2018-03-01 14:22:39
The regdomain code is used to select the correct the correct conformance
test limits (CTL) for a country. If the regdomain code isn't correctly
mapped to the actual CTL entries in EEPROM then it could happen that the
device violates the regulations. But it can also happen that the device is
then not able to be used with its full txpower on all rates.
The CTL mappings for this regdomain code were now changed to:
* 2.4GHz: ETSI
* 5GHz: NO_CTL -> ETSI
Signed-off-by: Sven Eckelmann <redacted>
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Kalle Valo <hidden> Date: 2018-05-24 14:10:06
Sven Eckelmann [off-list ref] writes:
The mappings from ath was not synced with the QCA driver since 2009. Only
two minor fixes were integrated in 2011. Since then, a lot of regd changes
were integrated in the close source QCA driver which are now used but not
supported by the Open Source driver. This either prevents the use of the
OSS driver on such devices or the wrong conformance test limits (CTLs) may
be used.
To get the integrated we would first get access to the closed source QCA
driver and a special OSS-NDA with QCA. This doesn't seem to be possible at
the moment and thus other sources for the changes have to be found. One of
them is the qcacld-2.0 source repository [1] which contains the QCA
regdomain.h and regdomain_common.h which was relicensed by QCA as ISC. It
isn't the newest version from the QCA driver but at least received some
updates which are not present in ath's regd.
This repository [1] (commit 48f9ab5d5c161549be098997fa0e3602c1547213 to be
more precise) was now used to find differences and ad some missing
mappings.
The title of the mappings describe what exactly was changed. The "Add
regulatory mapping for" patches introduce new country codes/mappings and
thus don't change old mappings. The "Add regulatory mapping for" patches
are similar but for regulatory code mappings instead of country code
mappings.
More interesting might be the "Map XXXX to YYYY" patches because they
modify already existing mappings. The result are following changes to the
selected CTLs:
* CTRY_ALBANIA: 5GHz: NO_CTL -> ETSI
* CTRY_ALGERIA: 5GHz: NO_CTL -> ETSI
* CTRY_BANGLADESH: 5GHz: NO_CTL -> FCC
* CTRY_BRUNEI_DARUSSALAM: 5GHz: FCC -> ETSI
* CTRY_HONDURAS: 5GHz: NO_CTL -> FCC
* CTRY_INDONESIA: 5GHz: NO_CTL -> FCC
* CTRY_ISRAEL: 5GHz: NO_CTL -> ETSI
* CTRY_KOREA_NORTH: 2.4GHz: ETSI -> MKK
* CTRY_KOREA_ROC: 2.4GHz: ETSI -> MKK
* CTRY_KOREA_ROC3: 2.4GHz: ETSI -> MKK
* CTRY_LEBANON: 5GHz: NO_CTL -> FCC
* CTRY_MACEDONIA: 5GHz: NO_CTL -> ETSI
* CTRY_MALAYSIA: 5GHz: ETSI -> FCC
* CTRY_MEXICO: 2.4GHz: FCC-> ETSI
* CTRY_PAKISTAN: 5GHz: NO_CTL -> FCC
* CTRY_ROMANIA: 5GHz: NO_CTL -> ETSI
* CTRY_RUSSIA: 5GHz: NO_CTL -> ETSI
* CTRY_SAUDI_ARABIA: 5GHz: NO_CTL -> FCC
* CTRY_SINGAPORE: 5GHz: ETSI -> FCC
* CTRY_UKRAINE: 5GHz: NO_CTL -> ETSI
* CTRY_UAE: 5GHz: NO_CTL -> ETSI
* CTRY_VIET_NAM: 5GHz: NO_CTL -> ETSI
* CTRY_ZIMBABWE: 5GHz: NO_CTL -> ETSI
Btw. I have not removed CTRY_SERBIA_MONTENEGRO, CTRY_KOREA_ROC2 or
APL2_APLD because this might break devices which have these programmed in
the EEPROM. And I have not added APL11_FCCA, APL12_WORLD and CTRY_MALDIVES
because only the code was in the qcacld-2.0 source code but not the actual
mapping.
I am relative confident that QCA also has following extra countries:
* Afghanistan
* American Samoa
* Anguilla
* Bhutan
* Burkina Faso
* Cayman Islands
* Central Africa Republic
* Chad
* Christmas Islands
* Dominica
* Ethiopia
* French Guiana
* French Polynesia
* Ghana
* Guadeloupe
* Guyana
* Cote d'Ivoire
* Lesotho
* Malawi
* Maldives
* Marshall Islands
* Martinique
* Mauitania
* Mayotte
* Micronesia
* Moldova
* Mongolia
* Namibia
* Nigeria
* Northern Mariana Islands
* Palau
* Reunion
* St Barthelemy
* St Kitts Nevis
* St Lucia
* St Martin
* St Pierre Miquelon
* St Vincent Grenadiens
* Samoa
* Senegal
* Suriname
* Togo
* Turks Caicos
* Vanuatu
* Virgin Islands
* Wallis Futuna
+ a lot of extra regdomain codes (0x15, 0x16, 0x17, 0x18, 0x19, 0x3c, 0x4f,
0x51, 0x57, 0x59) and the corresponding mappings.
I asked about this and indeed qcacld-2.0 has few old mappings. I was
told these patches are not current so I dropped them for now:
[03/52] ath: Add regulatory mapping for Japan (J56) 2018-03-01
[04/52] ath: Add regulatory mapping for Japan KDDI 2018-03-01
[10/52] ath: Add regulatory mapping for Rwanda 2018-03-01
[14/52] ath: Add regulatory mapping for United States for AP 2018-03-01
[16/52] ath: Add regulatory mapping for APL10_MKKC 2018-03-01
[21/52] ath: Switch APL9_WORLD to 2.4GHz MKK CTL 2018-03-01
[31/52] ath: Map Indonesia to APL2_WORLD 2018-03-01
[33/52] ath: Map Japan to MKK5_MKKA2 2018-03-01
[34/52] ath: Map South Korea to APL10_MKKC 2018-03-01
[35/52] ath: Map Lebanon to APL1_WORLD 2018-03-01
[38/52] ath: Map Mexico to FCC1_WORLD 2018-03-01
[40/52] ath: Map Pakistan to APL1_WORLD 2018-03-01
[45/52] ath: Map Saudi Arabia to FCC2_WORLD 2018-03-01
[47/52] ath: Map Taiwan to APL7_FCCA 2018-03-01
[49/52] ath: Map U.A.E. to ETSI1_WORLD 2018-03-01
[50/52] ath: Map Venezuela to FCC1_WORLD 2018-03-01
[51/52] ath: Map Vietnam to ETSI3_WORLD 2018-03-01
Rest of the patches are now in the pending branch and I'm hoping to
apply them soon:
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/log/?h=pending
--
Kalle Valo
From: Kalle Valo <hidden> Date: 2018-05-24 18:43:38
Kalle Valo [off-list ref] writes:
Sven Eckelmann [off-list ref] writes:
quoted
The mappings from ath was not synced with the QCA driver since 2009. Only
two minor fixes were integrated in 2011. Since then, a lot of regd changes
were integrated in the close source QCA driver which are now used but not
supported by the Open Source driver. This either prevents the use of the
OSS driver on such devices or the wrong conformance test limits (CTLs) may
be used.
To get the integrated we would first get access to the closed source QCA
driver and a special OSS-NDA with QCA. This doesn't seem to be possible at
the moment and thus other sources for the changes have to be found. One of
them is the qcacld-2.0 source repository [1] which contains the QCA
regdomain.h and regdomain_common.h which was relicensed by QCA as ISC. It
isn't the newest version from the QCA driver but at least received some
updates which are not present in ath's regd.
This repository [1] (commit 48f9ab5d5c161549be098997fa0e3602c1547213 to be
more precise) was now used to find differences and ad some missing
mappings.
The title of the mappings describe what exactly was changed. The "Add
regulatory mapping for" patches introduce new country codes/mappings and
thus don't change old mappings. The "Add regulatory mapping for" patches
are similar but for regulatory code mappings instead of country code
mappings.
More interesting might be the "Map XXXX to YYYY" patches because they
modify already existing mappings. The result are following changes to the
selected CTLs:
* CTRY_ALBANIA: 5GHz: NO_CTL -> ETSI
* CTRY_ALGERIA: 5GHz: NO_CTL -> ETSI
* CTRY_BANGLADESH: 5GHz: NO_CTL -> FCC
* CTRY_BRUNEI_DARUSSALAM: 5GHz: FCC -> ETSI
* CTRY_HONDURAS: 5GHz: NO_CTL -> FCC
* CTRY_INDONESIA: 5GHz: NO_CTL -> FCC
* CTRY_ISRAEL: 5GHz: NO_CTL -> ETSI
* CTRY_KOREA_NORTH: 2.4GHz: ETSI -> MKK
* CTRY_KOREA_ROC: 2.4GHz: ETSI -> MKK
* CTRY_KOREA_ROC3: 2.4GHz: ETSI -> MKK
* CTRY_LEBANON: 5GHz: NO_CTL -> FCC
* CTRY_MACEDONIA: 5GHz: NO_CTL -> ETSI
* CTRY_MALAYSIA: 5GHz: ETSI -> FCC
* CTRY_MEXICO: 2.4GHz: FCC-> ETSI
* CTRY_PAKISTAN: 5GHz: NO_CTL -> FCC
* CTRY_ROMANIA: 5GHz: NO_CTL -> ETSI
* CTRY_RUSSIA: 5GHz: NO_CTL -> ETSI
* CTRY_SAUDI_ARABIA: 5GHz: NO_CTL -> FCC
* CTRY_SINGAPORE: 5GHz: ETSI -> FCC
* CTRY_UKRAINE: 5GHz: NO_CTL -> ETSI
* CTRY_UAE: 5GHz: NO_CTL -> ETSI
* CTRY_VIET_NAM: 5GHz: NO_CTL -> ETSI
* CTRY_ZIMBABWE: 5GHz: NO_CTL -> ETSI
Btw. I have not removed CTRY_SERBIA_MONTENEGRO, CTRY_KOREA_ROC2 or
APL2_APLD because this might break devices which have these programmed in
the EEPROM. And I have not added APL11_FCCA, APL12_WORLD and CTRY_MALDIVES
because only the code was in the qcacld-2.0 source code but not the actual
mapping.
I am relative confident that QCA also has following extra countries:
* Afghanistan
* American Samoa
* Anguilla
* Bhutan
* Burkina Faso
* Cayman Islands
* Central Africa Republic
* Chad
* Christmas Islands
* Dominica
* Ethiopia
* French Guiana
* French Polynesia
* Ghana
* Guadeloupe
* Guyana
* Cote d'Ivoire
* Lesotho
* Malawi
* Maldives
* Marshall Islands
* Martinique
* Mauitania
* Mayotte
* Micronesia
* Moldova
* Mongolia
* Namibia
* Nigeria
* Northern Mariana Islands
* Palau
* Reunion
* St Barthelemy
* St Kitts Nevis
* St Lucia
* St Martin
* St Pierre Miquelon
* St Vincent Grenadiens
* Samoa
* Senegal
* Suriname
* Togo
* Turks Caicos
* Vanuatu
* Virgin Islands
* Wallis Futuna
+ a lot of extra regdomain codes (0x15, 0x16, 0x17, 0x18, 0x19, 0x3c, 0x4f,
0x51, 0x57, 0x59) and the corresponding mappings.
I asked about this and indeed qcacld-2.0 has few old mappings. I was
told these patches are not current so I dropped them for now:
[03/52] ath: Add regulatory mapping for Japan (J56) 2018-03-01
[04/52] ath: Add regulatory mapping for Japan KDDI 2018-03-01
[10/52] ath: Add regulatory mapping for Rwanda 2018-03-01
[14/52] ath: Add regulatory mapping for United States for AP 2018-03-01
[16/52] ath: Add regulatory mapping for APL10_MKKC 2018-03-01
[21/52] ath: Switch APL9_WORLD to 2.4GHz MKK CTL 2018-03-01
[31/52] ath: Map Indonesia to APL2_WORLD 2018-03-01
[33/52] ath: Map Japan to MKK5_MKKA2 2018-03-01
[34/52] ath: Map South Korea to APL10_MKKC 2018-03-01
[35/52] ath: Map Lebanon to APL1_WORLD 2018-03-01
[38/52] ath: Map Mexico to FCC1_WORLD 2018-03-01
[40/52] ath: Map Pakistan to APL1_WORLD 2018-03-01
[45/52] ath: Map Saudi Arabia to FCC2_WORLD 2018-03-01
[47/52] ath: Map Taiwan to APL7_FCCA 2018-03-01
[49/52] ath: Map U.A.E. to ETSI1_WORLD 2018-03-01
[50/52] ath: Map Venezuela to FCC1_WORLD 2018-03-01
[51/52] ath: Map Vietnam to ETSI3_WORLD 2018-03-01
Rest of the patches are now in the pending branch and I'm hoping to
apply them soon:
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/log/?h=pending
Forgot to mention that there was a trivial conflict due to dropping some
of the patches:
Pushing patch "ath-map-russia-to-etsi8_world" ... done (conflict)
Error: 1 merge conflict(s)
CONFLICT (content): Merge conflict in
drivers/net/wireless/ath/regd_common.h
Now at patch "ath-map-russia-to-etsi8_world"
I fixed it like this:
diff --cc drivers/net/wireless/ath/regd_common.h
index 3afce206e049,dcb4fe28e76a..000000000000
From: Kalle Valo <hidden> Date: 2018-05-25 10:02:06
Sven Eckelmann [off-list ref] wrote:
The country code is used by the ath to detect the ISO 3166-1 alpha-2 name
and to select the correct conformance test limits (CTL) for a country. If
the country isn't available and it is still programmed in the EEPROM then
it will cause an error and stop the initialization with:
Invalid EEPROM contents
The current CTL mappings for this country are:
* 2.4GHz: ETSI
* 5GHz: FCC
Signed-off-by: Sven Eckelmann <redacted>
Signed-off-by: Kalle Valo <redacted>
35 patches applied to ath-next branch of ath.git, thanks.
699e2302c286 ath: Add regulatory mapping for Bahamas
9c790f2d234f ath: Add regulatory mapping for Bermuda
b840fa912308 ath: Add regulatory mapping for Kenya
a71c984bc4e5 ath: Add regulatory mapping for Mauritius
a0a6f2a916dc ath: Add regulatory mapping for Montenegro
a20f1338c5de ath: Add regulatory mapping for Nicaragua
67a956682472 ath: Add regulatory mapping for Paraguya
2a3169a54bb5 ath: Add regulatory mapping for Serbia
667ddac5745f ath: Add regulatory mapping for Tanzania
1ea3986ad2bc ath: Add regulatory mapping for Uganda
4f183687e3fa ath: Add regulatory mapping for APL2_FCCA
9ba8df0c52b3 ath: Add regulatory mapping for APL13_WORLD
45faf6e096da ath: Add regulatory mapping for ETSI8_WORLD
897fab6c5d90 ath: Add regulatory mapping for ETSI9_WORLD
01fb2994a98d ath: Add regulatory mapping for FCC3_ETSIC
fed8f5e83037 ath: Map Albania to ETSI1_WORLD
485daee92bde ath: Map Algeria to APL13_WORLD
8120cc0b215c ath: Map Australia to FCC3_WORLD
1507b32891c0 ath: Map Bangladesh to APL1_WORLD
37090d944705 ath: Map Brunei Darussalam to APL6_WORLD
fed60f81a2d0 ath: Map Bulgaria to ETSI1_WORLD
515e968624b2 ath: Map Colombia to FCC1_FCCA
0fa31a86998b ath: Map Czech to ETSI1_WORLD
143a9b9bd7ee ath: Map Honduras to FCC3_WORLD
62ba2b22d120 ath: Map Isreal to ETSI3_WORLD
64874ed2a73a ath: Map Macedonia to ETSI1_WORLD
823a64065adf ath: Map Malasia to FCC1_WORLD
9bfc2bb32e01 ath: Map New Zealand to FCC3_ETSIC
b5c11e474406 ath: Map Peru to APL1_WORLD
c454d4c25844 ath: Map Philippines to FCC3_WORLD
12f415566fb4 ath: Map Romania to ETSI1_WORLD
b7e015132d85 ath: Map Russia to ETSI8_WORLD
054e07788002 ath: Map Singapore to FCC3_WORLD
4e78075c4821 ath: Map Ukraine to ETSI9_WORLD
f1abff21acc5 ath: Map Zimbabwe to ETSI1_WORLD
--
https://patchwork.kernel.org/patch/10251529/https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches