[RFC] ath10k: search DT for qcom,ath10k-calibration-variant

From: Sven Eckelmann Board Data File (BDF) is loaded upon driver boot-up procedure. The right board data file is identified on QCA4019 using bus, bmi-chip-id and bmi-board-id. The problem, however, can occur when the (default) board data file cannot fulfill with the vendor requirements and it

Re: [RFC] ath10k: search DT for qcom,ath10k-calibration-variant

On Donnerstag, 9. März 2017 16:36:15 CET Sven Eckelmann wrote: > .../bindings/net/wireless/qcom,ath10k.txt | 3 +++ > drivers/net/wireless/ath/ath10k/core.c | 31 > +- > 2 files changed, 33 insertions(+), 1 deletion(-) Nice, not only us

[RFC v2] 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 Cc: Waldemar Rymarkiewicz Signed-off-by: Sven Eckelmann --- Cc: Christian Lamparter Cc: John Crispin Cc: Si

[PATCH 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 --- Since RFC: - initialize variant pointer to have it initialized to NULL when

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

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 --- Since RFC: - Spli

[PATCH] mac80211: Allow multiple listeners for management frames.

-off-by: Sven Eckelmann --- It is currently unknown why Benjamin never forwarded it. I am doing this now to have a chance that this private patch doesn't have to be rebased anymore by OpenMesh. --- net/wireless/mlme.c | 30 -- 1 file changed, 28 insertions(

Re: [PATCH] mac80211: Allow multiple listeners for management frames.

On Dienstag, 14. März 2017 14:51:01 CET Johannes Berg wrote: [...] > I'm not sure I mentioned it to him, or even remembered it when we were > discussing it, but I don't think this patch is a good idea, at least > for action frames. [...] > If you restrict it to non-action I can live with it, but I

Re: [PATCH] mac80211: Allow multiple listeners for management frames.

On Dienstag, 14. März 2017 15:13:12 CET Johannes Berg wrote: > > The idea was to grab probe requests from userspace with a program > > running next to hostapd. > > I guess there are some efficiency problems with that right now, but a > monitor mode interface should work just as well. Perhaps we ca

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

On Freitag, 10. März 2017 19:20:54 CET 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 needs

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

On Montag, 20. März 2017 10:07:33 CET Rob Herring wrote: > On Fri, Mar 10, 2017 at 09:06:14AM +0100, Sven Eckelmann wrote: > > The bus + bmi-chip-id + bmi-board-id is not enough to identify the correct > > board data file on QCA4019 based devices. Multiple different boards sha

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

On Montag, 20. März 2017 09:42:05 CET Adrian Chadd wrote: > Vendors using ath10k will like this. I mean, I'm using ath10k, and I > really like this moving forward. This will make life so much easier in > the long run. > > Everyone else isn't using board-2.bin; they're just copying > calibration/bo

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

On Dienstag, 21. März 2017 08:00:34 CET Rob Herring wrote: [...] > > It would then up with something like this as compatibility string: > > > > * qcom,ipq4019-wifi-asus-rt-ac58u > > * qcom,ipq4019-wifi-fritzbox-4040 > > * qcom,ipq4019-wifi-netgear-whatever > > * qcom,ipq4019-wifi-openmesh-i-hav

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

On Dienstag, 21. März 2017 21:56:54 CET Rob Herring wrote: [...] > Is this always the case? There's never some variation beyond the > reference design that a BDF difference can't handle? I have no knowledge about anything which isn't handled directly by the BDF variants. But maybe Kalle can correc

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

Hi, I had following "simple" setup with LEDE with a single ath9k phy and multiple vif: * encrypted AP * encrypted 802.11s meshpoint * encrypted IBSS Everything was started in the order by hostapd/wpa_supplicant (but immediately after each other). The problem which I've experienced was that

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 ieee80211_offchannel_return(

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: [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, failed pkts/bytes, retry > pkt

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

10.4") Signed-off-by: Sven Eckelmann --- 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 index 84b6067ff6e7..6c0a821fe79d 10

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 c

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

[9.707224] [] ? kthread_park+0x60/0x60 [9.714363] [] ? ret_from_fork+0x25/0x30 [ 9.721589] ---[ end trace 6814c79dfe2a14da ]--- Tested-by: Sven Eckelmann Kind regards, Sven signature.asc Description: This is a digitally signed message part.

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

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/wla

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

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_common.h | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/net/wireless/ath/regd_common.h b/drivers/net/wireless/ath/regd_common.h

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

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

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

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

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

EPROM contents The current CTL mappings for this country are: * 2.4GHz: ETSI * 5GHz: ETSI 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

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

EPROM contents The current CTL mappings for this country are: * 2.4GHz: ETSI * 5GHz: ETSI 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

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

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_common.h | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/net/wireless/ath/regd_common.h b/drivers/net/wireless/ath/regd_common.h

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

EPROM contents The current CTL mappings for this country are: * 2.4GHz: MKK * 5GHz: MKK 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

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

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

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

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

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

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

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

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

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

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_common.h | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/net/wireless/ath/regd_common.h b/drivers/net/wireless/ath/regd_common.h

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

EPROM contents The current CTL mappings for this country are: * 2.4GHz: ETSI * 5GHz: ETSI 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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[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 --- drivers/net/wireless/ath/regd_common.h | 10 +- 1 file changed, 5 insertions(+), 5 deletions

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 valu

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; > + u3

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; > + > + ret

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 onl

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

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

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 that this messages comes so

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 rat

Re: Debugging RTL8192CU firmware loading on 3.12 powerpc

On Freitag, 2. September 2016 13:13:20 CEST Arend Van Spriel wrote: [...] > > Do you have any recommendations where the firmware loading problems could > > come from, and where we could start to debug? Any pointers would be > > appreciated. > Hi Simon, > > Could it be an endian issue? Yes, it cou

Re: Debugging RTL8192CU firmware loading on 3.12 powerpc

On Freitag, 2. September 2016 12:53:28 CEST Larry Finger wrote: [...] > The patch I included in my previous E-mail, and attached here, does get the > firmware loaded correctly. There is still a problem that prevents > authentication. I'm still looking for that issue. Thanks for the fast update. I

Re: Debugging RTL8192CU firmware loading on 3.12 powerpc

On Dienstag, 6. September 2016 09:40:41 CEST Sven Eckelmann wrote: > On Freitag, 2. September 2016 12:53:28 CEST Larry Finger wrote: > [...] > > > The patch I included in my previous E-mail, and attached here, does get > > the firmware loaded correctly. There is still a

Re: [OpenWrt-Devel] ath10k mesh + ap + encryption?

On Montag, 19. September 2016 08:43:56 CEST Simon Wunderlich wrote: [...] > > We're testing encrypted AP + Mesh quite successfully right now with > > this firmware: https://github.com/kvalo/ath10k-firmware/commit/307cb46b > > 06661ebd3186723b5002de769c7add83, of course that is for a QCA4019 chip. >

[RFC 1/2] ath9k: work around AR_CFG 0xdeadbeef chip hang

. No way is known to reproduce the problem easily. Signed-off-by: Simon Wunderlich [sven.eckelm...@open-mesh.com: port to recent ath9k, add commit message] Signed-off-by: Sven Eckelmann --- This was discussed 4 years ago on the OpenWrt mailing list. The most relevant post is https

[RFC 2/2] ath9k: Reset chip on potential deaf state

ned-off-by: Simon Wunderlich [sven.eckelm...@open-mesh.com: port to recent ath9k, add commit message] Signed-off-by: Sven Eckelmann --- This problem was discovered in mesh setups. It was noticed that some nodes were not able to see their neighbors (mostly after running for a while) - even when those ne

Re: [RFC 1/2] ath9k: work around AR_CFG 0xdeadbeef chip hang

On Mittwoch, 16. November 2016 16:16:42 CET Valo, Kalle wrote: > Sven Eckelmann writes: > > > From: Simon Wunderlich > > > > QCA 802.11n chips (especially AR9330/AR9340) sometimes end up in a state in > > which a read of AR_CFG always returns 0xdeadbeef. This shoul

[RFC v2 2/2] ath9k: Reset chip on potential deaf state

ned-off-by: Simon Wunderlich [sven.eckelm...@open-mesh.com: port to recent ath9k, add commit message] Signed-off-by: Sven Eckelmann --- v2: - reduce amount of possible goto-raptor attacks by one (thanks Kalle Valo) This problem was discovered in mesh setups. It was noticed that some nodes were not able

[RFC v2 1/2] ath9k: work around AR_CFG 0xdeadbeef chip hang

. No way is known to reproduce the problem easily. Signed-off-by: Simon Wunderlich [sven.eckelm...@open-mesh.com: port to recent ath9k, add commit message] Signed-off-by: Sven Eckelmann --- v2: - reduce amount of possible goto-raptor attacks by one (thanks Kalle Valo) This was discussed 4 years

Re: [ath9k-devel] [RFC v2 2/2] ath9k: Reset chip on potential deaf state

On Montag, 21. November 2016 10:07:43 CET Ferry Huberts wrote: [...] > > v2: > > - reduce amount of possible goto-raptor attacks by one (thanks Kalle Valo) > > > > This problem was discovered in mesh setups. It was noticed that some nodes > > > What kind of setup? > Using 802.11s? Unencrypted I

Re: wifi driver crashes openwrt device

On Monday 16 May 2016 14:46:07 Kalle Valo wrote: [...] > Didn't openwrt have a some sort ramoops facility to collect the last > kernel logs before a crash? I don't recall the name right now but I'm > pretty sure I used it with one of our APs few years back. That might > help (or not). He can just

[PATCH 1/2] ath10k: add QCA9887 chipset support

Add the hardware name, revision, firmware names and update the pci_id table. QA9887 HW1.0 is supposed to be similar to QCA988X HW2.0 . Details about he firmware interface are currently unknown. Signed-off-by: Sven Eckelmann --- drivers/net/wireless/ath/ath10k/core.c | 20

[PATCH 0/2] ath10k: Add support for QCA9887

Hi, the QCA9887 chip is similar to the QCA988x chips. But it requires a special firmware and uses a different calibration data source. Unfortunately, no working firmware currently exists. But it is possible to create a semi working one by binary patching the current version. # download new fw

[PATCH 2/2] ath10k: Add board data download from target

The QCA9887 stores its calibration data (board.bin) inside the EEPROM of the target. This has to be downloaded manually to allow the device to initialize correctly. Signed-off-by: Sven Eckelmann --- drivers/net/wireless/ath/ath10k/core.c | 41 +- drivers/net/wireless/ath/ath10k/core.h

Re: [PATCH v1] ath10k: Fix 10.4 extended peer stats update

On Wednesday 11 May 2016 11:54:30 Mohammed Shafi Shajakhan wrote: > #else > -static inline void ath10k_sta_update_rx_duration(struct ath10k *ar, > - struct list_head *peer) > +static inline > +void ath10k_sta_update_rx_duration(struct ath10k *ar, > +

Re: [PATCH 0/2] ath10k: Add support for QCA9887

On Thursday 26 May 2016 17:32:30 Valo, Kalle wrote: > Sven Eckelmann writes: > > > the QCA9887 chip is similar to the QCA988x chips. But it requires a special > > firmware and uses a different calibration data source. Unfortunately, no > > working firmware currently exist

Re: [PATCH 0/2] ath10k: Add support for QCA9887

On Friday 27 May 2016 12:44:52 Valo, Kalle wrote: [...] > > But maybe I should add that the results with the original AP147 firmware > > also > > wasn't better. > > That doesn't sound good. Maybe a calibration issue? Maybe but I don't have a different card to compare it to. [...] > I pushed a n

Re: [PATCH 2/2] ath10k: Add board data download from target

On Saturday 04 June 2016 13:26:39 you wrote: [...] > Looking at this again I noticed that we issue this warning even if > EEPROM is not supported, which I think is wrong. I fixed this in the > pending branch, the diff is below. > > I also renamed target_board_data to cal_eeprom because, at least t

Re: [PATCH 0/2] ath10k: Add support for QCA9887

On Tuesday 07 June 2016 20:20:02 Mohammed Shafi Shajakhan wrote: [...] > [shafi] it would be helpful if you can share your basic test results (if its > possible to share). Have you tried to bring up the card in 5ghz (or) 2ghz. > Or both of them were tried ? * 5GHz-only (I have no 2.4GHz capable ca

[PATCH] ath9k: Fix programming of minCCA power threshold

: Fix regulatory compliance") Signed-off-by: Sven Eckelmann Cc: Simon Wunderlich Cc: Sujith Manoharan --- drivers/net/wireless/ath/ath9k/ar9003_eeprom.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/wireless/ath/ath9k/ar9003_eeprom.c b/drivers/net/wireless

  1   2   3   >