Re: QCA6174 showing terrible performance when connecting via WPA3-SAE

2024-05-06 Thread Eric Park
On 5/6/2024 6:04 PM, Kalle Valo wrote: (...) This is of course just a theory. I don't know how familiar you are with 802.11 protocols but that is something to investigate. Unfortunately I have very little time for ath10k nowadays. Not very familiar with 802.11 protocols, I'm just a user.

Re: [PATCH v3 1/3] dt-bindings: net: wireless: ath10k: add qcom,no-msa-ready-indicator prop

2024-05-06 Thread Kalle Valo
Marc Gonzalez writes: > On 30/04/2024 06:06, Kalle Valo wrote: > >> Bjorn Andersson wrote: >> >>> On Mon, Apr 29, 2024 at 04:04:51PM +0200, Marc Gonzalez wrote: >>> The ath10k driver waits for an "MSA_READY" indicator to complete initialization. If the indicator is not received,

Re: [PATCH v3 3/3] arm64: dts: qcom: msm8998: set qcom,no-msa-ready-indicator for wifi

2024-05-06 Thread Marc Gonzalez
On 29/04/2024 16:07, Marc Gonzalez wrote: > The ath10k driver waits for an "MSA_READY" indicator > to complete initialization. If the indicator is not > received, then the device remains unusable. > > cf. ath10k_qmi_driver_event_work() > > Several msm8998-based devices are affected by this

Re: QCA6174 showing terrible performance when connecting via WPA3-SAE

2024-05-06 Thread Kalle Valo
Eric Park writes: > I had the opportunity to test the connection with another router (Asus > RT-AX56U) today and it negotiated with WPA2-PSK, PMF default on, on 5 > GHz. I ran a speedtest and got 20 Mbps both up/down. > > I then ran the `nmcli connection modify wifi-sec.pmf 1` and > after