lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <dec60af0-d439-4e72-ba07-358996532e9c@quicinc.com>
Date: Tue, 9 Jul 2024 09:33:13 +0800
From: Baochen Qiang <quic_bqiang@...cinc.com>
To: Kalle Valo <kvalo@...nel.org>
CC: Paul Menzel <pmenzel@...gen.mpg.de>, James Prestwood <prestwoj@...il.com>,
        <linux-wireless@...r.kernel.org>, <ath10k@...ts.infradead.org>,
        LKML
	<linux-kernel@...r.kernel.org>,
        Chun Wu <chunwu@....qualcomm.com>
Subject: Re: invalid vht params rate 1920 100kbps nss 2 mcs 9



On 7/8/2024 6:33 PM, Kalle Valo wrote:
> Baochen Qiang <quic_bqiang@...cinc.com> writes:
> 
>>>>> 2.  invalid vht params rate 960 100kbps nss 1 mcs 9
>>>>> 3.  invalid vht params rate 1730 100kbps nss 2 mcs 9
>>>>> 4.  invalid vht params rate 1920 100kbps nss 2 mcs 9
>>>>
>>>> OK, these are due to mismatch between host and QCA6174 firmware, we
>>>> can update host to fix them.
>>
>> Kalle, the root cause to these three warnings are clear now and if you
>> agree I can submit patches to fix them. Or I can also wait until the
>> NSS 3 issue is clear.
> 
> I'm not sure why would we want to wait for the NSS 3 to be solved? Based
> on my (limited) understanding I think it would be good to submit patches
> for solved issues now.
Sure, will do today.

> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ