[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8dffe5f57c6948e1bca5f7cb3e40a781@realtek.com>
Date: Mon, 23 Oct 2023 02:22:18 +0000
From: Ping-Ke Shih <pkshih@...ltek.com>
To: Chukun Pan <amadeus@....edu.cn>,
"kvalo@...nel.org" <kvalo@...nel.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>
Subject: RE: [PATCH 1/1] wifi: rtw88: 8822b: disable call trace when write RF mode table fail
> -----Original Message-----
> From: Chukun Pan <amadeus@....edu.cn>
> Sent: Sunday, October 22, 2023 5:09 PM
> To: kvalo@...nel.org
> Cc: Ping-Ke Shih <pkshih@...ltek.com>; linux-kernel@...r.kernel.org; linux-wireless@...r.kernel.org;
> Chukun Pan <amadeus@....edu.cn>
> Subject: RE: [PATCH 1/1] wifi: rtw88: 8822b: disable call trace when write RF mode table fail
>
> > _Why_ is that warning printed? Are your devices uncalibrated or are they
> > somehow else special?
>
> I don't know, but not only my rtl8822be wifi module will have this call trace
> every time when the driver probes. This can be considered a common problem.
> So I prefer to disable this call trace and use the driver warning instead.
>
Except to call trace, rtl8822be works well in your side? If so, you just
worry the verbose trace, right?
By the way, I tested two hardware version of rtl8822be, and they both are fine.
Ping-Ke
Powered by blists - more mailing lists