Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Sender: Larry Finger <larry.finger@gmail.com>
Message-ID: <e0086aed-6aad-1b1c-65d0-1bb5e2ae3698@lwfinger.net>
Date:   Mon, 22 May 2023 08:03:29 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.11.0
Subject: Re: [PATCH 0/7] wifi: rtw89: 8851b: add to enable 8851BE
To:     Ping-Ke Shih <pkshih@realtek.com>, kvalo@kernel.org
Cc:     timlee@realtek.com, linux-wireless@vger.kernel.org
References: <20230519031500.21087-1-pkshih@realtek.com>
Content-Language: en-US
From:   Larry Finger <Larry.Finger@lwfinger.net>
In-Reply-To: <20230519031500.21087-1-pkshih@realtek.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 5/18/23 22:14, Ping-Ke Shih wrote:
> With preparation before, this patchset can enable 8851BE eventually.
> Thanks for the review, Kalle.
> 
> The first four patches are to add remaining chip_ops and chip_info.
> Patch 5/7 is to extend debugfs entry of read_reg to have ability to read
> wider length of registers. Patch 6/7 is to enable a firmware feature, and
> other features like hardware scan aren't verified completely, so I defer
> to enable them later because current version can still work fine.
> 
> The last patch 7/7 is to modify Kconfig and Makefile to enable 8851BE.
> 
> Chin-Yen Lee (1):
>    wifi: rtw89: add tx_wake notify for 8851B
> 
> Ping-Ke Shih (6):
>    wifi: rtw89: 8851b: add TX power related functions
>    wifi: rtw89: 8851b: fill BB related capabilities to chip_info
>    wifi: rtw89: 8851b: add MAC configurations to chip_info
>    wifi: rtw89: 8851b: add RF configurations
>    wifi: rtw89: enlarge supported length of read_reg debugfs entry
>    wifi: rtw89: 8851b: add 8851be to Makefile and Kconfig

I received samples of the RTW8851BE and the preliminary version of these patches 
one week ago. I tested with that code for 4 days, and then switched to this 
version when it was posted here. During the nearly 7 days of testing, I found no 
major issues. The connection was stable with a local LibreSpeed server and 
Speedtest.net both showing 400-500 Mbps up and down. The connection was to an 
ax1500 AP using the 5G band.

Tested-by: Larry Finger <Larry.Finger@lwfinger.net>

Larry