Re: Wii: bwi driver fails to attach for device id 0x044b on NetBSD 11.0-BETA

[deltaresero <deltaresero%zoho.com@localhost>]

Hello Jared,

I checked out the master/trunk branch but was unable to build kernel from the src repository https://github.com/NetBSD/src.git as the build system failed during the host tool compilation phase.

I thought cross compiling it on Linux might have been just as simple as running:
$ ./build.sh -m evbppc -U tools kernel=WII
but I kept getting repeated "incompatible pointer type" errors in the texinfo tool's makeinfo/cmds.c file.

Given the local build failure, I tested your changes using the daily binary snapshot:
https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/20251019171412Z/evbppc/binary/gzimg/wii.img.gz

This appears to fix the issue as the system successfully recognizes and initializes the Wi-Fi chip.

On first boot with the new kernel, the system correctly logged that it needed the firmware: bwi0: firmware_open failed on v3/ucode5.fw. I then followed the standard procedure for injecting firmware onto the SD card. On a second machine, I downloaded the v3.tbz file, moved it over to the FAT32 partition of the SD card, logged into NetBSD and ran:
# cp /boot/v3.tbz .
# mkdir -p /libdata/firmware/bwi
# tar -C /libdata/firmware/bwi -jxvf v3.tbz
# reboot

On the subsequent boot, bwi0 initialized successfully, with the following related messages:
bwi0: firmware rev0x0127, patch level 0x000e
bwi0: base tssi measure failed

The warning regarding "base tssi measure failed" did not appear to prevent normal operation. After the driver successfully attached, I was able to configure and activate the interface.
# wpa_passphrase myssid mypassword >>/etc/wpa_supplicant.conf
# echo 'wpa_supplicant=YES' >>/etc/rc.conf
# service wpa_supplicant start

ifconfig -a now lists the bwi0 interface with an assigned address, and I was able to successfully ping external hosts. 
Thank you so much for fixing this!

Best regards,
DeltaResero



---- On Sat, 18 Oct 2025 22:17:09 -0300 Jared McNeill <jmcneill%invisible.ca@localhost> wrote ---

 > I checked in a patch that should help. Can you give it a shot? 
 >  
 > revision 1.44 
 > date: 2025-10-18 22:15:45 -0300;  author: jmcneill;  state: Exp;  lines: +10 -3;  commitid: vHCZXTlZiGEnk7fG; 
 > bwi: Retry SDIO common regwin probe a few times before giving up. 
 >  
 > It seems that on some systems, we need to read the SDIO common regwin ID 
 > register more than once to properly identify it. Try a couple of times 
 > before giving up. 
 >  
 > This makes bwi(4) attach on my red Wii. 
 >  
 >  
 > On Fri, 10 Oct 2025, Jared McNeill wrote: 
 >  
 > > Actually, don't waste your time with that patch, on second thought it won't 
 > > work. I'll do some more digging. 
 > > 
 > > 
 > > On Fri, 10 Oct 2025, Jared McNeill wrote: 
 > > 
 > >> Hi! 
 > >> 
 > >> That's interesting, I haven't been able to reproduce this myself with any 
 > >> of the NA units that I have, but after seeing your message I went back and 
 > >> looked at Jun Ebihara's dmesg from 
 > >> https://mail-index.netbsd.org/port-powerpc/2025/06/16/msg003701.html and 
 > >> the same error is there. 
 > >> 
 > >> Maybe a different wifi chip in some revisions of the device? 
 > >> 
 > >> For a quick test, can you build a kernel with the following hack to see if 
 > >> it helps? 
 > >> 
 > >> --- sys/dev/sdmmc/if_bwi_sdio.c 19 Jan 2025 00:29:29 -0000      1.1 
 > >> +++ sys/dev/sdmmc/if_bwi_sdio.c 10 Oct 2025 16:19:01 -0000 
 > >> @@ -178,7 +178,7 @@ bwi_sdio_attach(device_t parent, device_ 
 > >>        sc->sc_reg_write_4 = bwi_sdio_reg_write_4; 
 > >>        sc->sc_reg_read_4 = bwi_sdio_reg_read_4; 
 > >>        sc->sc_pci_revid = 0;   /* XXX can this come from CIS? */ 
 > >> -       sc->sc_pci_did = cis->product; 
 > >> +       sc->sc_pci_did = 0x4318; 
 > >>        sc->sc_pci_subvid = cis->manufacturer; 
 > >>        sc->sc_pci_subdid = cis->product; 
 > >> 
 > >> 
 > >> On Sun, 5 Oct 2025, deltaresero wrote: 
 > >> 
 > >>> Hello, 
 > >>> 
 > >>> I'm running NetBSD 11.0-BETA (WII) on a Nintendo Wii (build from Oct 5, 
 > >>> 2025). 
 > >>> 
 > >>> uname -a: 
 > >>> NetBSD wii 11.0_BETA NetBSD 11.0_BETA (WII) #0 Fri Oct 3 16:09:55 UTC 2025 
 > >>> mk repro%mkrepro.NetBSD.org@localhost:/usr/src/sys/arch/evbppc/compile/WII evbppc 
 > >>> 
 > >>> dmesg | grep -i bwi -n 
 > >>> 74:[     1.209984] bwi0 at sdmmc1 function 1: broadcom Wireless 
 > >>> 75:[     1.209984] bwi0: autoconfiguration error: no BBP id for device id 
 > >>> 0x044b 
 > >>> 
 > >>> I followed Jared McNeill’s instructions for adding Wii WLAN support to 
 > >>> -current (see: 
 > >>> https://mail-index.netbsd.org/port-powerpc/2025/01/19/msg003669.html) and 
 > >>> installed the v3 firmware per bwi(4). The driver detects the device but 
 > >>> reports “no BBP id for device id 0x044b” and, as expected, I only see the 
 > >>> loopback adapter lo0. I suspect this may be a hardware revision not 
 > >>> present in the driver's table. If that’s the case, is it possible to add 
 > >>> support for this device? 
 > >>> 
 > >>> Thanks, 
 > >>> DeltaResero 
 > >>> 
 > >