BCM4359 is not supported in the mainline kernel using brcmfmac; there is driver support for the PCIe version of the chip but not SDIO and it’s not as simple as adding the chip IDs to the SDIO code. It’s possible to patch the out-of-tree Broadcom “dhd” driver into the kernel tree but some people have reported it to behave badly. I’ve approached the linux-wireless mailing list for help and was given a patch to get some debug output, but since Linux 5.2 i’ve not been able to patch the device IDs into the kernel without triggering a complete boot failure, and I haven’t had the free time to go back to 5.1 to make the tests. That’s probably not the answer(s) you wanted to hear, but that’s current status.
NB: The Google device that’s bankrolling most of the current G12 mainline support also has the same chip and when Google enquired … Broadcom ignored them too - so it’s not a case of Khadas not having the weight to get a solution (although I question why people keep spec’ing chips with zero/shitty driver support… but that’s another debate).
yes ! i think its big mistake to use brcm chips - ))) why people again and again try to use this crap ??? i hope khadas for next time chose another normal chip with good support from opensource
I can’t really comment on dhd as I don’t use it (our distro refuses to add it). If you can help with running the test (with the extra commit to add debug info) and share the output that would be appreciated. It’s the first step towards getting one of the Broadcom maintainers to take an interest in getting BCM4359 supported upstream.
Please share your experience and also logs if you can get it.
I will pass it on to Rockchip and Ampak, maybe they can help to solve the remaining problems.
For testing devices that frequently don’t have working WiFi from the comfort of my sofa (without using a 15m Ethernet cable) I acquired a used Apple Airport Express from eBay ($15). it’s configured in bridge mode so that any device I plug in via Ethernet has reliable WiFi with no dependencies on drivers, kernel versions, etc. … just a suggestion.
Apple Airport Express - need power from adapter (or its same by usb cable connected to same device )? + and price about 50USD and up, i think any usb wifi dongle with true supported chip its easy and price only 5 USD
PS: i have use orange-pi devices its just 10USD for same bridge usage , but he provide usb-ethernet <=BRIDGE=> wifi , and use only one usb cable and same no need special drivers )
.
It appears VIM3 is shipping without working WiFi on many Linux distributions, even though its datasheet advertises Wifi AC as a feature.
.
There is nothing wrong with wanting / needing it to work for a specific use case, is there?
.
If there is an issue with my suggestion to use a patch that appears to have worked in making wifi useable on another board using the same chip, please let me know. It it is not applicable, I’d be interested in understanding why
.
It uses mains power (240v) and the last one I bought (used) was $13 inc. postage. If you want to support cheap Realtek USB devices with shit out-of-tree drivers, be my guest. I don’t