Larry,
Radxa confirmed that they do not program the eFUSE on these boards.
We do not get a sensible MAC from the chip, so I derive a one from the
CPU's unique serial number.
It's a hack, but it works well and is standard's compliant.
The RockPI-S a *very* inexpensive board, so I can understand Radxa
wanting to minimize the time spent configuring each one.
https://shop.allnetchina.cn/products/rock-pi-s
The vendor driver seems to deal with this by applying typical gain
parameters when the eFUSE is invalid.
With that driver, this board's WiFi performs beautifully, despite the
unprogrammed eFUSE.
Would you accept a patch to add this logic to RTW88?
- brent
Larry Finger wrote:
On 2/15/24 17:55, Brent Roman wrote:
Originally sent to linux-wireless on Feb 1, 2024:
The Radxa RockPi-S has a built-in RTL8723DS interfaced to a Rockchip
RK3308 A35 ARM64 processor on one of its SDIO busses.
I maintain Armbian's support this board.
The built-in WiFi works perfectly with RTL's 8723ds.ko driver.
Recently, the rtw88 driver got support for SDIO.
https://lwn.net/Articles/925940/
However, when we attempt to enable the rtw88_8723ds module, WiFi does
not work.
Specifically, the WiFi scan returns only the strongest AP while
indicating that AP has a very weak signal.
No connections can be made.
Unloading the rtw88_8723ds modules to replace it with 8723ds
immediately restores WiFi function without the need to reboot the
system.
Has anyone tested the SDIO variant of this driver?
If so, on which board(s)?
I'd very much like to get this working.
Any tips for debugging, or just getting relevant info from the
driver, would be appreciated
Brent,
Yes, there are SDIO cards working with the RTW88 driver.
Is the EFUSE properly encoded on the RockPI-S? If not, then the
parameters of the chip with respect to gains are not set correctly.
You should be able to see that condition in the dmesg output. Also, is
the driver getting a realistic MAC address? That also comes from the
EFUSE.
Larry
--
Brent Roman MBARI
Software Engineer Tel: (831) 775-1808
mailto:brent@xxxxxxxxx http://www.mbari.org/~brent
