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]
Date:   Thu, 30 Jun 2022 13:29:37 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Meng Tang <tangmeng@...ontech.com>
Cc:     stable@...r.kernel.org, tony0620emma@...il.com,
        kvalo@...eaurora.org, davem@...emloft.net, kuba@...nel.org,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        Ping-Ke Shih <pkshih@...ltek.com>,
        masterzorag <masterzorag@...il.com>,
        Larry Finger <Larry.Finger@...inger.net>,
        Kalle Valo <kvalo@...nel.org>
Subject: Re: [PATCH 5.10 v2 3/3] commit e109e3617e5d ("rtw88: rtw8821c:
 enable rfe 6 devices")

On Tue, Jun 28, 2022 at 09:43:51PM +0800, Meng Tang wrote:
> These commits can fix the problem of wifi not loading properly. At
> least in my 5.10 kernel environment, the following error message is
> reported:
> 
> rtw_8821ce 0000:01:00.0: rfe 6 isn't supported
> rtw_8821ce 0000:01:00.0: failed to setup chip efuse info
> rtw_8821ce 0000:01:00.0: failed to setup chip information
> 
> so I think that 5.10 need to merge these commits.
> 
> The patch 1/3 and patch 2/3 need to be merged synchronously, otherwise it
> will cause OE and then kernel exception.

This is not in the original commit log at all.  Shouldn't this be in the
0/3 email instead?

And yes, this hardware is not supported in the 5.10 kernel tree, please
move to 5.15 or newer and it will be fine.

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ