[PATCH v2 2/2] wireless-regdb: Sync DE with ETSI EN 301 893 V2.1.1 (2017-05)

that the limits for the 5GHz bands are out of date: * 5150 - 5250 MHz only usage is allowed to use up to 23 dBm (200 mW) even without TPC Signed-off-by: Sven Eckelmann --- db.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/db.txt b/db.txt index 7f978e1..8f356f7 100644 --- a/db.txt

Re: [PATCH 2/2] wireless-regdb: Sync DE with ETSI EN 301 893 V2.1.1 (2017-05)

On Montag, 17. September 2018 09:42:12 CEST Sven Eckelmann wrote: [...] > diff --git a/db.txt b/db.txt > index 7f978e1..f406ac0 100644 > --- a/db.txt > +++ b/db.txt > @@ -379,7 +379,7 @@ country CZ: DFS-ETSI > country DE: DFS-ETSI > (2400 - 2483.5 @ 40), (100 mW) >

[PATCH 2/2] wireless-regdb: Sync DE with ETSI EN 301 893 V2.1.1 (2017-05)

that the limits for the 5GHz bands are out of date: * 5150 - 5250 MHz only usage is allowed to use up to 23 dBm (200 mW) even without TPC Signed-off-by: Sven Eckelmann --- db.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/db.txt b/db.txt index 7f978e1..f406ac0 100644 --- a/db.txt

[PATCH 1/2] wireless-regdb: Sync FR with ETSI EN 301 893 V2.1.1 (2017-05)

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 --- db.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/db.txt b/db.txt index bc64628..7f978e1

Re: [PATCH v2 9/9] mac80211: Don't wake up from PS for offchannel TX

On Dienstag, 4. September 2018 14:40:55 CEST Luca Coelho wrote: > ) > Sender: linux-wireless-ow...@vger.kernel.org > Precedence: bulk > List-ID: > X-Mailing-List: linux-wireless@vger.kernel.org Looks like the SMTP headers are broken in all your patches. Here the interesting part (as received by

Re: mac80211: AQM and block_tx

On Dienstag, 10. Juli 2018 18:09:37 CEST Manikanta Pubbisetty wrote: [...] > I am working on a patch which takes care of stopping the iTXQs after > detecting a radar(covering other scenarios where stopping iTXQs is > important) > and there by making sure packets are not transmitted. [...] >

Re: mac80211: AQM and block_tx

On Donnerstag, 5. Juli 2018 10:47:11 CEST Sven Eckelmann wrote: > Hi Toke, > > we are currently testing DFS with ath10k and noticed that AQM seems to ignore > cfg80211_csa_settings->block_tx. Problem is now that the channel switch is > started on a detected radar > &g

mac80211: AQM and block_tx

Hi Toke, we are currently testing DFS with ath10k and noticed that AQM seems to ignore cfg80211_csa_settings->block_tx. Problem is now that the channel switch is started on a detected radar echo 1 >/sys/kernel/debug/ieee80211/phy1/ath10k/dfs_simulate_radar NL80211_ATTR_CH_SWITCH_BLOCK_TX is

Re: [PATCH v2] ath10k: support for multicast rate control

On Montag, 7. Mai 2018 18:34:51 CEST Pradeep Kumar Chitrapu wrote: > Issues wmi command to firmwre when multicast rate change is received > with the new BSS_CHANGED_MCAST_RATE flag. > Also fixes the incorrect fixed_rate setting for CCK rates which got > introduced with addition of

Re: [PATCH] ath10k:add support for multicast rate control

On Montag, 16. April 2018 22:10:50 CEST prade...@codeaurora.org wrote: [...] > > I see two major problems here without checking the actual > > implementation > > details: > > > > * hw_value is incorrect for a couple of devices. Some devices use a > > different > > mapping when they receive

Re: [PATCH 2/2] ath9k: fix tx99 bus error

On Dienstag, 20. Juni 2017 09:13:40 CEST miaoq...@codeaurora.org wrote: > From: Miaoqing Pan > > The hard coded register 0x9864 and 0x9924 are invalid > for ar9300 chips. [...] > - REG_SET_BIT(ah, 0x9864, 0x7f000); > - REG_SET_BIT(ah, 0x9924, 0x7f00fe); Sorry

Re: [PATCH] ath10k:add support for multicast rate control

FDM; + } * bcast + mcast (+ mgmt) have to be set separately I have attached my POC patch (which I was using for packet loss based mesh metrics) and to work around (using debugfs) the silly mgmt vs. mcast/bcast settings of the QCA fw for APs. Many of the information came from Ben Greears

Re: [PATCH v2] ath10k: Implement get_expected_throughput callback

On Mittwoch, 28. März 2018 11:41:51 CEST ako...@codeaurora.org wrote: [...] > The rate average and throughput are relative. no? In the sense that rate has a tendency to affect the expected throughput - yes. But it is not like the expected throughput perfectly correlates with the rate and you

Re: [PATCH v2] ath10k: Implement get_expected_throughput callback

On Freitag, 23. März 2018 19:37:14 CEST Anilkumar Kolli wrote: > +static u32 ath10k_get_expected_throughput(struct ieee80211_hw *hw, > + struct ieee80211_sta *sta) > +{ > + struct ath10k_sta *arsta = (struct ath10k_sta *)sta->drv_priv; > + > +

Re: [PATCH] ath10k: Implement get_expected_throughput callback

On Freitag, 23. März 2018 13:07:00 CET Anilkumar Kolli wrote: [...] > +static u32 ath10k_get_expected_throughput(struct ieee80211_hw *hw, > + struct ieee80211_sta *sta) > +{ > + struct ath10k_sta *arsta = (struct ath10k_sta *)sta->drv_priv; > +

Re: [PATCH 2/2] ath10k: add debugfs support to configure fwtest parameters

On Montag, 5. März 2018 12:29:08 CET Anilkumar Kolli wrote: > @@ -496,6 +497,8 @@ struct ath10k_debug { > u32 reg_addr; > u32 nf_cal_period; > void *cal_data; > + u32 fw_test_param_id; > + u32 fw_test_param_value; > }; Why is it necessary to have these two

[PATCH 35/52] ath: Map Lebanon to APL1_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 +- 1 file changed, 1

[PATCH 36/52] ath: Map Macedonia to ETSI1_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 +- 1 file changed, 1

[PATCH 52/52] ath: Map Zimbabwe to ETSI1_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 +- 1 file changed, 1

[PATCH 48/52] ath: Map Ukraine to ETSI9_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 +- 1 file changed, 1

[PATCH 45/52] ath: Map Saudi Arabia to FCC2_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 +- 1 file changed, 1

[PATCH 49/52] ath: Map U.A.E. to ETSI1_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 +- 1 file changed, 1

[PATCH 51/52] ath: Map Vietnam to ETSI3_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 +- 1 file changed, 1

[PATCH 50/52] ath: Map Venezuela to FCC1_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2

[PATCH 46/52] ath: Map Singapore to FCC3_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 +- 1 file changed, 1 insert

[PATCH 39/52] ath: Map New Zealand to FCC3_ETSIC

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2

[PATCH 44/52] ath: Map Russia to ETSI8_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 +- 1 file changed, 1

[PATCH 47/52] ath: Map Taiwan to APL7_FCCA

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2

[PATCH 38/52] ath: Map Mexico to FCC1_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 +- 1 file changed, 1 insert

[PATCH 41/52] ath: Map Peru to APL1_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2

[PATCH 42/52] ath: Map Philippines to FCC3_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2

[PATCH 43/52] ath: Map Romania to ETSI1_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 +- 1 file changed, 1

[PATCH 40/52] ath: Map Pakistan to APL1_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 +- 1 file changed, 1

[PATCH 30/52] ath: Map Honduras to FCC3_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 +- 1 file changed, 1

[PATCH 29/52] ath: Map Czech to ETSI1_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2

[PATCH 37/52] ath: Map Malasia to FCC1_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 +- 1 file changed, 1 insert

[PATCH 33/52] ath: Map Japan to MKK5_MKKA2

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2

[PATCH 34/52] ath: Map South Korea to APL10_MKKC

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2

[PATCH 32/52] ath: Map Isreal to ETSI3_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 +- 1 file changed, 1

[PATCH 31/52] ath: Map Indonesia to APL2_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 +- 1 file changed, 1

[PATCH 21/52] ath: Switch APL9_WORLD to 2.4GHz MKK CTL

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 10 +- 1 file chan

[PATCH 27/52] ath: Map Bulgaria to ETSI1_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2

[PATCH 26/52] ath: Map Brunei Darussalam to APL6_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 +- 1 file changed, 1 insert

[PATCH 25/52] ath: Map Bangladesh to APL1_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 +- 1 file changed, 1

[PATCH 28/52] ath: Map Colombia to FCC1_FCCA

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2

[PATCH 24/52] ath: Map Australia to FCC3_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2

[PATCH 22/52] ath: Map Albania to ETSI1_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 +- 1 file changed, 1

[PATCH 23/52] ath: Map Algeria to APL13_WORLD

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 <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 +- 1 file changed, 1

[PATCH 20/52] ath: Add regulatory mapping for FCC3_ETSIC

mappings for this regdomain code are: * 2.4GHz: ETSI * 5GHz: FCC Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/net/wireless/ath/regd_common.h b/drivers/net/wireless/ath/regd_co

[PATCH 16/52] ath: Add regulatory mapping for APL10_MKKC

mappings for this regdomain code are: * 2.4GHz: MKK * 5GHz: ETSI Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/net/wireless/ath/regd_common.h b/drivers/net/wireless/ath/regd_co

[PATCH 15/52] ath: Add regulatory mapping for APL2_FCCA

mappings for this regdomain code are: * 2.4GHz: FCC * 5GHz: FCC Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/net/wireless/ath/regd_common.h b/drivers/net/wireless/ath/regd_co

[PATCH 14/52] ath: Add regulatory mapping for United States for AP

contents The current CTL mappings for this country are: * 2.4GHz: FCC * 5GHz: FCC Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd.h| 1 + drivers/net/wireless/ath/regd_common.h | 1 + 2 files changed, 2 insertions(+) diff --git a/drive

[PATCH 17/52] ath: Add regulatory mapping for APL13_WORLD

mappings for this regdomain code are: * 2.4GHz: ETSI * 5GHz: ETSI Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/net/wireless/ath/regd_common.h b/drivers/net/wireless/ath/regd_co

[PATCH 18/52] ath: Add regulatory mapping for ETSI8_WORLD

mappings for this regdomain code are: * 2.4GHz: ETSI * 5GHz: ETSI Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/net/wireless/ath/regd_common.h b/drivers/net/wireless/ath/regd_co

[PATCH 19/52] ath: Add regulatory mapping for ETSI9_WORLD

mappings for this regdomain code are: * 2.4GHz: ETSI * 5GHz: ETSI Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/net/wireless/ath/regd_common.h b/drivers/net/wireless/ath/regd_co

[PATCH 12/52] ath: Add regulatory mapping for Tanzania

contents The current CTL mappings for this country are: * 2.4GHz: ETSI * 5GHz: FCC Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd.h| 1 + drivers/net/wireless/ath/regd_common.h | 1 + 2 files changed, 2 insertions(+) diff --git a/drive

[PATCH 11/52] ath: Add regulatory mapping for Serbia

contents The current CTL mappings for this country are: * 2.4GHz: ETSI * 5GHz: ETSI Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd.h| 1 + drivers/net/wireless/ath/regd_common.h | 1 + 2 files changed, 2 insertions(+) diff --git a/d

[PATCH 13/52] ath: Add regulatory mapping for Uganda

contents The current CTL mappings for this country are: * 2.4GHz: ETSI * 5GHz: FCC Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd.h| 1 + drivers/net/wireless/ath/regd_common.h | 1 + 2 files changed, 2 insertions(+) diff --git a/drive

[PATCH 05/52] ath: Add regulatory mapping for Kenya

contents The current CTL mappings for this country are: * 2.4GHz: ETSI * 5GHz: FCC Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/net/wireless/ath/regd_common.h b/drive

[PATCH 03/52] ath: Add regulatory mapping for Japan (J56)

contents The current CTL mappings for this country are: * 2.4GHz: FCC * 5GHz: MKK Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/net/wireless/ath/regd_common.h b/drive

[PATCH 10/52] ath: Add regulatory mapping for Rwanda

contents The current CTL mappings for this country are: * 2.4GHz: ETSI * 5GHz: FCC Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd.h| 1 + drivers/net/wireless/ath/regd_common.h | 1 + 2 files changed, 2 insertions(+) diff --git a/drive

[PATCH 08/52] ath: Add regulatory mapping for Nicaragua

contents The current CTL mappings for this country are: * 2.4GHz: FCC * 5GHz: FCC Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/net/wireless/ath/regd_common.h b/drive

[PATCH 07/52] ath: Add regulatory mapping for Montenegro

contents The current CTL mappings for this country are: * 2.4GHz: ETSI * 5GHz: ETSI Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd.h| 1 + drivers/net/wireless/ath/regd_common.h | 1 + 2 files changed, 2 insertions(+) diff --git a/d

[PATCH 06/52] ath: Add regulatory mapping for Mauritius

contents The current CTL mappings for this country are: * 2.4GHz: ETSI * 5GHz: ETSI Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd.h| 1 + drivers/net/wireless/ath/regd_common.h | 1 + 2 files changed, 2 insertions(+) diff --git a/d

[PATCH 04/52] ath: Add regulatory mapping for Japan KDDI

contents The current CTL mappings for this country are: * 2.4GHz: MKK * 5GHz: MKK Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd.h| 1 + drivers/net/wireless/ath/regd_common.h | 1 + 2 files changed, 2 insertions(+) diff --git a/drive

[PATCH 09/52] ath: Add regulatory mapping for Paraguya

contents The current CTL mappings for this country are: * 2.4GHz: ETSI * 5GHz: FCC Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd_common.h | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/net/wireless/ath/regd_common.h b/drive

[PATCH 02/52] ath: Add regulatory mapping for Bermuda

contents The current CTL mappings for this country are: * 2.4GHz: FCC * 5GHz: FCC Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd.h| 1 + drivers/net/wireless/ath/regd_common.h | 1 + 2 files changed, 2 insertions(+) diff --git a/drive

[PATCH 01/52] ath: Add regulatory mapping for Bahamas

contents The current CTL mappings for this country are: * 2.4GHz: ETSI * 5GHz: FCC Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/regd.h| 1 + drivers/net/wireless/ath/regd_common.h | 1 + 2 files changed, 2 insertions(+) diff --git a/drive

[PATCH 00/52] ath: Synchronize regd mappings with qcacld-2.0 4.0.11.181

: * 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 Eckelm

Re: [PATCH v2 2/2] ath10k: fix CCK h/w rates for QCA99X0 and newer chipsets

On Donnerstag, 2. Juni 2016 12:53:55 CET Mohammed Shafi Shajakhan wrote: > From: Mohammed Shafi Shajakhan > > CCK hardware table mapping from QCA99X0 onwards got revised. > The CCK hardware rate values are in a proper order wrt. to > rate and preamble as below > >

Re: [PATCH 1/1] ath10k: add LED and GPIO controlling support for various chipsets

On Donnerstag, 15. Februar 2018 15:31:04 CET Sebastian Gottschall wrote: > Adds LED and GPIO Control support for 988x, 9887, 9888, 99x0, 9984 and > ipq4019 based chipsets with on chipset connected led's > using WMI Firmware API. > The LED device will get available named as "ath10k-phyX" at sysfs

Re: 802.11ac devices that use Minstrel_HT

On Dienstag, 13. Februar 2018 07:56:29 CET Ali Abedi wrote: > > So I would currently bet on hwsim (only useful when you only want to have > > some > > simulations) or mt76. Afaik mt76 was also the one which was used to test the > > VHT rate injection code for monitor interfaces and is therefore

Re: 802.11ac devices that use Minstrel_HT

On Montag, 12. Februar 2018 14:05:36 CET Ali Abedi wrote: > Hello, > > It seems that Minstrel_ht rate adaptation algorithm supports 802.11ac > VHT rates. > Can you refer me to some 802.11ac devices that use this rate adaptation > algorithm? > I need to modify the rate adaptation algorithm

Re: [1/2] mt76: fix possible NULL pointer dereferencing in mt76x2_ampdu_action()

On Mittwoch, 17. Januar 2018 16:50:23 CET Kalle Valo wrote: [...] > >> I didn't see Felix's ack, at least not on patchwork. > > > > I sent my ack (for both patches) as a reply to 0/2 > > Ah. patchwork is annoying as it doesn't show the cover letter at all so > I missed that. Newer version at

Re: [PATCH] ath10k: Add BMI parameters to fix calibration from DT/pre-cal

On Montag, 11. Dezember 2017 18:50:09 CET ako...@codeaurora.org wrote: [...] > >> > Just tried this on an QCA9984 which doesn't seem to have the > >> > calibration data in the PCI EEPROM. > >> > > >> > [ 71.728929] ath10k_pci :01:00.0: qca9984/qca9994 hw1.0 > >> > target 0x0100

Re: [PATCH] ath10k: Add BMI parameters to fix calibration from DT/pre-cal

On Freitag, 8. Dezember 2017 18:05:38 CET ako...@codeaurora.org wrote: > On 2017-12-08 17:42, Sven Eckelmann wrote: > > On Donnerstag, 25. Mai 2017 16:21:23 CET ako...@qti.qualcomm.com wrote: > >> From: Anilkumar Kolli <ako...@qti.qualcomm.com> > >> > &

Re: [PATCH] ath10k: Add BMI parameters to fix calibration from DT/pre-cal

On Donnerstag, 25. Mai 2017 16:21:23 CET ako...@qti.qualcomm.com wrote: > From: Anilkumar Kolli > > QCA99X0, QCA9888, QCA9984 supports calibration data in > either OTP or DT/pre-cal file. Current ath10k supports > Calibration data from OTP only. > > If caldata is loaded

[PATCH v2 1/2] dt: bindings: add new dt entry for ath10k calibration variant

in the correct calibration data when combined with the pre-calibration data from the device. An additional "variant" information has to be provided (via SMBIOS or DT) to select the correct board data for a design which was modified by an ODM. Signed-off-by: Sven Eckelmann <sven.eckelm...

[PATCH v2 2/2] ath10k: search DT for qcom,ath10k-calibration-variant

s would create the boarddata identifiers for the board-2.bin search * bus=ahb,bmi-chip-id=0,bmi-board-id=16,variant=RT-AC58U * bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=RT-AC58U Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/ath10k/core.c |

Re: ath10k: Fix reported HT MCS rates with NSS > 1

On Dienstag, 21. November 2017 11:43:36 CET ako...@codeaurora.org wrote: [...] > > I think we should add a special case to not print the warning if mcs == > > 15 until we figure out what it means. > > Fix identified in Firmware and will push ASAP. Is it known when this will be released and for

Re: [PATCHv3 1/2] ath10k: add per peer htt tx stats support for 10.4

On Dienstag, 21. November 2017 10:00:20 CET Sebastian Gottschall wrote: > maybe this one? > > i have this qca988x supporting tx/rx rate patch in my local tree. just > need to extract it again > > ath10k: report per-station tx/rate rates to mac80211 This one sounds like

Re: [PATCHv3 1/2] ath10k: add per peer htt tx stats support for 10.4

On Dienstag, 21. November 2017 09:00:54 CET Sebastian Gottschall wrote: [...] > >> Why is the support for 10.2.4 firmware not upstreamed? I mean the one > >> which is > >> using pktlog to transfer the PEER_STATS information. > > I'm not sure what you are asking. If you are asking the firmware

Re: [PATCHv3 1/2] ath10k: add per peer htt tx stats support for 10.4

On Dienstag, 15. November 2016 22:07:29 CET ako...@qti.qualcomm.com wrote: > From: Anilkumar Kolli > > Per peer tx stats are part of 'HTT_10_4_T2H_MSG_TYPE_PEER_STATS' > event, Firmware sends one HTT event for every four PPDUs. > HTT payload has success pkts/bytes,

Re: ath10k: Fix reported HT MCS rates with NSS > 1

On Montag, 6. November 2017 09:28:42 CET Sebastian Gottschall wrote: > Am 06.11.2017 um 09:23 schrieb Sven Eckelmann: > > On Sonntag, 5. November 2017 10:22:22 CET Sebastian Gottschall wrote: > >> the assumption made in this patch is obviously wrong (at least for more >

Re: ath10k: Fix reported HT MCS rates with NSS > 1

On Sonntag, 5. November 2017 10:22:22 CET Sebastian Gottschall wrote: > the assumption made in this patch is obviously wrong (at least for more > recent firmwares and 9984) > my log is flooded with messages like > [208802.803537] ath10k_pci 0001:03:00.0: Invalid VHT mcs 15 peer stats >

Re: [PATCH] wireless-regdb: Update regulatory rules for Singapore (SG)

On Mittwoch, 23. August 2017 15:52:40 CEST Seth Forshee wrote: [...] > > +# Source > > +# > > https://www.imda.gov.sg/~/media/imda/files/regulation%20licensing%20and%20consultations/ict%20standards/telecommunication%20standards/radio-comms/imdatssrd.pdf?la=en > > +# page 12-14 > > +# The EIRP for

Re: [PATCH 2/2] ath10k: search DT for qcom,ath10k-calibration-variant

On Freitag, 10. März 2017 19:20:54 CEST Christian Lamparter wrote: [...] > @Aeolus Yang / Kalle / QCA: Would it be possible to assign a variant string to > the Asus RT-AC58U? > > I've attached the necessary bmi-board-id=16 and bmi-board-id=17 board > files to this mail as well. So, all that

ath: Incorrect regDomainPairs/allCountries settings

Hi, I just had two inquiries from Vietnam and Singapore regarding the used CTL limits by Atheros based chips. I've checked through the code and noticed that regd_common.h assigns SG to APL6_WORLD and VN to NULL1_WORLD. * SG: APL6_WORLD - 2.4GHz: CTL_ETSI - 5GHz: CTL_ETSI * VN:

[PATCH] wireless-regdb: Update regulatory rules for Singapore (SG)

2.4GHz and the lower 5GHz band can now be use with up to 23dBm. But the DFS channels in general require TPC to be usable. Only 5150 - 5250 has an exception which allows the use of it without TPC when reducing the power to 20 dBm. Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.

Re: [PATCH v2 2/3] ath10k: Configure rxnss_override for 10.4 firmware.

On Freitag, 16. Juni 2017 08:50:13 CEST Kalle Valo wrote: > We have hw_params for stuff like this so I changed this and the > following patch to use that. Please review: Looks good. Thanks for adjusting the patches. Kind regards, Sven signature.asc Description: This is a digitally

[PATCH v2 2/3] ath10k: Configure rxnss_override for 10.4 firmware.

t have configured the rxnss_override. This could use some testing Signed-off-by: Ben Greear <gree...@candelatech.com> [sven.eckelm...@openmesh.com: rebase, cleanup, drop 160Mhz workaround cleanup] Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com> --- v2: - rebased patch

[PATCH v2 1/3] ath10k: Use complete VHT chan width for 160MHz workaround

doesn't make any sense. The correct mask for the VHT channel width should be used instead to make this check more readable. Signed-off-by: Ben Greear <gree...@candelatech.com> [sven.eckelm...@openmesh.com: separate 160Mhz workaround cleanup, add commit message] Signed-off-by: Sven

[PATCH v2 3/3] ath10k: Set rxnss_override for QCA9888

QCA9888 supports VHT80 with 2x2. But it only support 1x1 with VHT160 or VHT80+80. Inform userspace and the the QCA firmware about that limitation whenever VHT80+80 or VHT160 is configured. Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com> --- v2: - new patch drivers/net/wirele

Re: ath10k: Configure rxnss_override for 10.4 firmware.

On Mittwoch, 15. Februar 2017 01:26:58 CEST Kalle Valo wrote: > Ben Greear wrote: > > From: Ben Greear > > > > QCA9984 hardware can do 4x4 at 80Mhz, but only 2x2 at 160Mhz. [] > Does not apply: > > error: patch failed:

Re: [PATCH] [ath10k] go back to using dma_alloc_coherent() for firmware scratch memory.

2bb/0x700 [9.707224] [] ? kthread_park+0x60/0x60 [9.714363] [] ? ret_from_fork+0x25/0x30 [9.721589] ---[ end trace 6814c79dfe2a14da ]--- Tested-by: Sven Eckelmann <sven.eckelm...@openmesh.com> Kind regards, Sven signature.asc Description: This is a digitally signed message part.

Re: [PATCH] ath10k: Fix reported HT MCS rates with NSS > 1

On Donnerstag, 11. Mai 2017 11:39:46 CEST Arend Van Spriel wrote: [...] > So you leave VHT as is. Did you check with 11ac device? I am wondering > if it needs the same change. VHT MCS rates are reported by drivers with NSS + MCS rates 0-9 [1] as separated values. So I would say that the code is

[PATCH] ath10k: Fix reported HT MCS rates with NSS > 1

10.4") Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com> --- drivers/net/wireless/ath/ath10k/htt_rx.c | 14 ++ 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/drivers/net/wireless/ath/ath10k/htt_rx.c b/drivers/net/wireless/ath/ath10k/htt_rx.c in

Re: [PATCHv3 1/2] ath10k: add per peer htt tx stats support for 10.4

On Dienstag, 15. November 2016 22:07:29 CEST ako...@qti.qualcomm.com wrote: > From: Anilkumar Kolli > > Per peer tx stats are part of 'HTT_10_4_T2H_MSG_TYPE_PEER_STATS' > event, Firmware sends one HTT event for every four PPDUs. > HTT payload has success pkts/bytes,

Re: [REGRESSION] mac80211: IBSS vif queue stopped when started after 11s vif

On Mittwoch, 29. März 2017 13:53:06 CEST Johannes Berg wrote: [...] > > Not sure whether removing it in ieee80211_propagate_queue_wake will > > have other odd side effects with software queuing. Maybe Michal > > Kazior can tell us if it is safe to remove it. > > No, it's the other way around. >

Re: [REGRESSION] mac80211: IBSS vif queue stopped when started after 11s vif

On Mittwoch, 29. März 2017 09:49:21 CEST Johannes Berg wrote: > > But I could be completely wrong about it. It would therefore be > > interesting for me to know who would be responsible to start the > > queues when ieee80211_do_open rejected it for IBSS. > > Well, once

  1   2   >