On Tuesday, 27 August 2019 12:04:27 CEST Anilkumar Kolli wrote:
> Could you plz try removing below patch?
> https://source.codeaurora.org/quic/qsdk/oss/system/feeds/wlan-open/tree/mac80211/patches/072-ath11k-print-stats-on-crash.patch?h=win_ap.1.0
It is not applied. At least I can't find any ath11
On Tuesday, 27 August 2019 11:04:23 CEST Anilkumar Kolli wrote:
[...]
> > Yes, but it shouldn't kill the complete system.
> >
> This will not kill the whole system, This will crash target and we have
> mechanism to recover the system.
>
> Hope u have generated the crash with below patch,
> https
On Tuesday, 27 August 2019 09:33:39 CEST Anilkumar Kolli wrote:
[...]
> > [ 4312.884650] The reading for sensor 4 is 0x002041f7
> > [ 4312.891499] The reading for sensor 5 is 0x002051f4
> > [ 4312.896415] Couldn't get reading for sensor 6
> > [ 4312.901189] Couldn't get reading for
On Tuesday, 20 August 2019 17:47:36 CEST Kalle Valo wrote:
> +static ssize_t ath11k_read_simulate_fw_crash(struct file *file,
> +char __user *user_buf,
> +size_t count, loff_t *ppos)
> +{
> + const char bu
On Tuesday, 20 August 2019 17:47:57 CEST Kalle Valo wrote:
> +static void ath11k_peer_assoc_h_rates(struct ath11k *ar,
> + struct ieee80211_vif *vif,
> + struct ieee80211_sta *sta,
> + struct
Hi,
On Tuesday, 13 August 2019 12:55:49 CEST Jouni Malinen wrote:
[...]
> > [1] https://patchwork.ozlabs.org/patch/1131273/
> > [2] https://patchwork.ozlabs.org/patch/1116968/
> > [3] https://lore.kernel.org/r/2152977.f3ncjnVLFo@bentobox
>
> And with the exact same snapshot of hostap.git.
>
> Wit
From: Sven Eckelmann
Some features of 802.11ax without central organizing (AP) STA can also be
used in mesh mode. hwsim can be used to assist initial development of these
features without having access to HW.
Signed-off-by: Sven Eckelmann
---
v6:
* rebased on top of 690c4509e980
On Friday, 26 July 2019 15:32:50 CEST Johannes Berg wrote:
[...]
> Ok, dunno. But I don't really want to break everything in the hwsim
> tests, even if the kernel patch may be correct ... so I guess I'll wait
> until you resubmit after some fixes go into wpa_s?
Ok, will try to do this. Seems like
On Friday, 26 July 2019 15:26:32 CEST Johannes Berg wrote:
> On Wed, 2019-07-24 at 18:33 +0200, Sven Eckelmann wrote:
> > From: Sven Eckelmann
> >
> > Some features of 802.11ax without central organizing (AP) STA can also be
> > used in mesh mode. hwsim can be used to
On Wednesday, 24 July 2019 18:33:55 CEST Sven Eckelmann wrote:
> Hi,
>
> Some features of 802.11ax without central organizing (AP) STA can also be
> used in mesh mode. The main goal is to get HE mesh working with ath11k.
> For persons without ath11k compatible hw, hwsim can be
From: Sven Eckelmann
The firmware WLAN.HK.2.1.0.1-00629-QCAHKSWPL_SILICONZ-1 often stops sending
data on 5GHz when SU support is advertised. A simple throughput benchmark
will end up at only a couple hundred kilobytes per second (when finishing
at all).
Disabling SU related flags works around
From: Sven Eckelmann
The capabilities for the HE mesh are generated from the capabilities
reported by the fw. But the firmware only reports the overall capabilities
and not the one which are specific for mesh. Some of them (TWT, MU UL/DL,
TB PPDU, ...) require an infrastructure setup with a main
From: Sven Eckelmann
Some features of 802.11ax without central organizing (AP) STA can also be
used in mesh mode. hwsim can be used to assist initial development of these
features without having access to HW.
Signed-off-by: Sven Eckelmann
Forwarded: https://patchwork.kernel.org/patch/11029301
From: Sven Eckelmann
Implement the basics required for supporting high efficiency with mesh:
include HE information elements in beacons, probe responses, and peering
action frames, and check for compatible HE configurations when peering.
Signed-off-by: Sven Eckelmann
Forwarded: https
he_support workaround in ath11k because now all phy_modes are
HE phy modes
* v3
- force ath11k PHY mode for meshpoint vif to HE mode to avoid hang of
firmware when HE (or VHT on 2.4GHz) device tries to connect
* v2:
- add of ath11k patch
* v1:
- initial RFC
Sven Eckelmann (4
On Friday, 12 July 2019 11:42:51 CEST Johannes Berg wrote:
> On Fri, 2019-07-12 at 11:36 +0200, Sven Eckelmann wrote:
> >
> > There is already a workaround for that in the hostap testcases:
> >
> > if all_cap_one:
> > # It looks like tshark pa
On Friday, 12 July 2019 09:58:50 CEST Johannes Berg wrote:
> On Wed, 2019-07-03 at 11:23 +0200, Sven Eckelmann wrote:
> >
> > ~/tmp/wireshark/build/run/tshark -r
> > /tmp/hwsim-test-logs/latest/wpas_mesh_max_peering.hwsim0.pcapng -T fields
> > -e wlan
From: Sven Eckelmann
The capabilities for the HE mesh are generated from the capabilities
reported by the fw. But the firmware only reports the overall capabilities
and not the one which are specific for mesh. Some of them (TWT, MU UL/DL,
TB PPDU, ...) require an infrastructure setup with a main
patch
* v1:
- initial RFC
Sven Eckelmann (3):
mac80211: implement HE support for mesh
mac80211_hwsim: Register support for HE meshpoint
ath11k: register HE mesh capabilities
drivers/net/wireless/ath/ath11k/mac.c | 56 +
drivers/net/wireless/mac80211_hwsim.c | 283
From: Sven Eckelmann
Some features of 802.11ax without central organizing (AP) STA can also be
used in mesh mode. hwsim can be used to assist initial development of these
features without having access to HW.
Signed-off-by: Sven Eckelmann
---
drivers/net/wireless/mac80211_hwsim.c | 283
From: Sven Eckelmann
Implement the basics required for supporting high efficiency with mesh:
include HE information elements in beacons, probe responses, and peering
action frames, and check for compatible HE configurations when peering.
Signed-off-by: Sven Eckelmann
---
net/mac80211
Hi,
Thanks for clarifying your statement regarding ie_len. I think I should have
been able to guess what you meant but for some reason my brain wasn't able to
understand the phrase at that time.
On Friday, 14 June 2019 16:10:46 CEST Johannes Berg wrote:
> Two comments:
>
> 1) It seems to me th
On Friday, 14 June 2019 16:11:15 CEST Johannes Berg wrote:
> > + ie_len = 2 + 1 +
> > +sizeof(he_cap->he_cap_elem) + n +
> > +ieee80211_he_ppe_size(he_cap->ppe_thres[0],
> > + he_cap->he_cap_elem.phy_cap_info);
> > +
> > +
From: Sven Eckelmann
Some features of 802.11ax without central organizing (AP) STA can also be
used in mesh mode. hwsim can be used to assist initial development of these
features without having access to HW.
Signed-off-by: Sven Eckelmann
---
drivers/net/wireless/mac80211_hwsim.c | 283
mode for meshpoint vif to HE mode to avoid hang of
firmware when HE (or VHT on 2.4GHz) device tries to connect
* v2:
- add of ath11k patch
* v1:
- initial RFC
Kind regards,
Sven
Sven Eckelmann (3):
mac80211_hwsim: Register support for HE meshpoint
mac80211: implement HE
From: Sven Eckelmann
The capabilities for the HE mesh are generated from the capabilities
reported by the fw. But the firmware only reports the overall capabilities
and not the one which are specific for mesh. Some of them (TWT, MU UL/DL,
TB PPDU, ...) require an infrastructure setup with a main
From: Sven Eckelmann
Implement the basics required for supporting high efficiency with mesh:
include HE information elements in beacons, probe responses, and peering
action frames, and check for compatible HE configurations when peering.
Signed-off-by: Sven Eckelmann
---
include/net/cfg80211
On Tuesday, 11 June 2019 21:52:20 CEST Sven Eckelmann wrote:
[...]
> if (!test_sta_flag(sta, WLAN_STA_RATE_CONTROL))
> rate_control_rate_init(sta);
>
>/* inform drivers about changes */
> rate_control_rate_update(local, sband, sta, changed);
>
&g
On Tuesday, 11 June 2019 20:02:47 CEST Sven Eckelmann wrote:
[...]
> ---
> This doesn't work currently as expected. No HE rates are used between
> the two HE mesh peers:
[...]
There seems to be also an ordering problem. ath11k_peer_assoc_h_he is only
From: Sven Eckelmann
The capabilities for the HE mesh are generated from the capabilities
reported by the fw. But the firmware only reports the overall capabilities
and not the one which are specific for mesh. Some of them (TWT, MU UL/DL,
TB PPDU, ...) require an infrastructure setup with a main
From: Sven Eckelmann
Implement the basics required for supporting high efficiency with mesh:
include HE information elements in beacons, probe responses, and peering
action frames, and check for compatible HE configurations when peering.
Signed-off-by: Sven Eckelmann
---
include/net/cfg80211
From: Sven Eckelmann
Some features of 802.11ax without central organizing (AP) STA can also be
used in mesh mode. hwsim can be used to assist initial development of these
features without having access to HW.
Signed-off-by: Sven Eckelmann
---
drivers/net/wireless/mac80211_hwsim.c | 283
d) to enable HE for mesh.
hwsim can be used in the meantime as basis for initial development of these
features without having access to HW.
Kind regards,
Sven
Sven Eckelmann (3):
mac80211_hwsim: Register support for HE meshpoint
mac80211: implement HE support for mesh
ath11k: register HE
On Tuesday, 11 June 2019 08:38:52 CEST Lorenzo Bianconi wrote:
> + switch (n_chains) {
> + case 4:
> + target_power += 6;
> + break;
> + case 3:
> + target_power += 4;
> +
On Tuesday, 28 May 2019 08:58:28 CEST John Crispin wrote:
> Print the HE MAC/PHY capabilities and MCS/NSS sets.
>
> Signed-off-by: Shashidhar Lakkavalli
> Signed-off-by: John Crispin
> ---
> Changes in V2
> * add a missing ',' in the iftypes name list
The patch was already added with the bugfix
From: Sven Eckelmann
Implement the basics required for supporting high efficiency with mesh:
include HE information elements in beacons, probe responses, and peering
action frames, and check for compatible HE configurations when peering.
Signed-off-by: Sven Eckelmann
---
include/net/cfg80211
From: Sven Eckelmann
Some features of 802.11ax without central organizing (AP) STA can also be
used in mesh mode. hwsim can be used to assist initial development of these
features without having access to HW.
Signed-off-by: Sven Eckelmann
---
drivers/net/wireless/mac80211_hwsim.c | 283
On Monday, 20 May 2019 12:54:16 CEST John Crispin wrote:
> + char *iftypes[NUM_NL80211_IFTYPES] = {
> + "Unspec", "Adhoc", "Station", "AP", "AP/VLAN", "WDS",
> "Monitor"
> + "Mesh", "P2P/Client", "P2P/Go", "P2P/Device", "OCB", "NAN",
> + };
Noticed during t
On Wednesday, 20 March 2019 14:49:57 CET Tom Psyborg wrote:
> On 20/03/2019, Sven Eckelmann wrote:
>
> > This also means that a device with multiple tx chains is even limited
> > further:
> >
> > * 1 chain: 31 dBm per chain
> > * 2 chains: 28 dBm per ch
limit of 63. Since the antenna gain can be quite large and 8 bit
variables are often used in ath9k for txpower, a large, divisible by two
number like 254 is a good choice for this new limit.
Signed-off-by: Sven Eckelmann
---
drivers/net/wireless/ath/ath9k/eeprom.c| 2 +-
drivers/net/wireless
On Monday, 25 February 2019 21:00:38 CET Sven Eckelmann wrote:
[...]
> Tested-by: Sven Eckelmann
>
> Was tested on QCA988X with 10.2.4-1.0-00041
I just wanted to test it with 802.11s setup on IPQ4019 with 10.4-3.5.3-00057
and QCA9888 with 10.4-3.5.3-00053 (ath10k-firmware) and 10.4-
On Friday, 6 April 2018 17:17:55 CET Kalle Valo wrote:
> From: Sebastian Gottschall
>
> Adds LED and GPIO Control support for 988x, 9887, 9888, 99x0, 9984 based
> chipsets with on chipset connected led's using WMI Firmware API. The LED
> device will get available named as "ath10k-phyX" at sysfs
ested on QCA9984 with firmware 10.4-3.6.1-00827
>
> Fixes: cd93b83ad92 ("ath10k: support for multicast rate control")
> Co-developed-by: Zhi Chen
> Signed-off-by: Zhi Chen
> Signed-off-by: Pradeep Kumar Chitrapu
Tested-by: Sven Eckelmann
Was tested on QCA988X wit
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
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)
>
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
h 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..7f
On Dienstag, 4. September 2018 14:07:54 CEST Sven Eckelmann wrote:
> 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.ke
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
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.
[...]
> https
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
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
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 ath10k_rates_rev2
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 rat
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 that this messages comes so
preamble = WMI_RATE_PREAMBLE_OFDM;
+ }
* 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 th
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 onl
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;
> +
> + ret
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;
> + u3
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 valu
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 inser
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 inser
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 inser
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 inser
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 inser
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 inser
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 inser
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 inser
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
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
---
drivers/net/wireless/ath/regd_common.h | 10 +-
1 file changed, 5 insertions(+), 5 deletions
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 inser
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 inser
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 inser
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
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
---
drivers/net/wireless/ath/regd_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
t CTL mappings for this regdomain code are:
* 2.4GHz: ETSI
* 5GHz: FCC
Signed-off-by: Sven Eckelmann
---
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_common.h
index f1735ac
t CTL mappings for this regdomain code are:
* 2.4GHz: MKK
* 5GHz: ETSI
Signed-off-by: Sven Eckelmann
---
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_common.h
index 07c966a
t CTL mappings for this regdomain code are:
* 2.4GHz: FCC
* 5GHz: FCC
Signed-off-by: Sven Eckelmann
---
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_common.h
index 5cbd762
EPROM contents
The current CTL mappings for this country are:
* 2.4GHz: FCC
* 5GHz: FCC
Signed-off-by: Sven Eckelmann
---
drivers/net/wireless/ath/regd.h| 1 +
drivers/net/wireless/ath/regd_common.h | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/net/wireless/ath/regd.h b/dr
t CTL mappings for this regdomain code are:
* 2.4GHz: ETSI
* 5GHz: ETSI
Signed-off-by: Sven Eckelmann
---
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_common.h
index 44e3831
t CTL mappings for this regdomain code are:
* 2.4GHz: ETSI
* 5GHz: ETSI
Signed-off-by: Sven Eckelmann
---
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_common.h
index 14332b8
t CTL mappings for this regdomain code are:
* 2.4GHz: ETSI
* 5GHz: ETSI
Signed-off-by: Sven Eckelmann
---
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_common.h
index 88913c6
EPROM contents
The current CTL mappings for this country are:
* 2.4GHz: ETSI
* 5GHz: FCC
Signed-off-by: Sven Eckelmann
---
drivers/net/wireless/ath/regd.h| 1 +
drivers/net/wireless/ath/regd_common.h | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/net/wireless/ath/reg
1 - 100 of 220 matches
Mail list logo
