Morning;
On the MX64 / MX64W Page it states the Wireless chip is not supported - the wireless chip is the same used in the MR32 that is supported...
MR32 showing support for WLAN BCM43520: https://openwrt.org/toh/meraki/mr32
MX64 saying no support for the same WLAN Chip: https://openwrt.org/inbox/toh/meraki/meraki_mx64?s[]=mx64w
BCM43520KMLG is the chip in question ... if it's supported on the MR32 why can't it be supported on the MX64W?
What lleachii has linked gives you the necessary information, but...
What does "support" actually mean to you?
BCM43520 is a 2x2 802.11ac/ wifi 5 WLAN chipset, specified for 866 MBit/s (yes, under ideal circumstances you may only get ½-⅔ of that in practice, but still). With OpenWrt/ b43 it will top out around 15-20 MBit/s<fullstop>. Considering that, do you still care about the finer details (and the additional limitations and hurdles)?
If wireless 'works' (with 15 MBit/s) or not at all is just materially insignificant for a wifi4/ wifi5/ wifi6/ wifi7 AP.
EDIT: Just for reference, last month I have replaced the stock Broadcom BCM43228 802.11a/b/g/n WLAN card in a HP T520 thin client running general purpose linux (v6.14.x, b43) with a cheap Realtek RTL8822CE 802.11ac mini-PCIe one (rtw88), differences:
It means I have multiple MR65W devices sitting around doing nothing and I would prefer to reuse them instead of spending money even if I need to setup a build box and build custom firmware...
If you're fine with the 20mb speed cap, you can use Openwrt and add support for the device.
You could also request the sources from the vendor, but those would most likely miss the BLOBs required to get the radios up and running.
This is where you loose me: " add support for the device." - how? Could you give me a map and a compass or point me in the right direction?
By BLOBs do you mean the firmware? - I already found the Broadcom Firmware Cutter - downloaded the BCM4352 windows driver and have extracted the the firmware...
Those BLOBs will probably only work with the old Broadcom kernel used in the stock firmware.
You'll need to request the sources from Meraki.
if you read the git commit for the mr32:
WARNING:
Only the 1x1:1 abgn Air Marshal WIPS wifi is currently supported by b43:
b43-phy2: Found PHY: Analog 9, Type 4 (N), Revision 16
b43-phy2: Found Radio: Manuf 0x17F, ID 0x2057, Revision 9, Version 1
b43-phy2: Loading firmware version 784.2 (2012-08-15 21:35:19)
and only as 802.11ABG!
while WIFI1 and WIFI2 (both BCM4352) are not:
b43-phy0: Broadcom 4352 WLAN found (core revision 42)
b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 12, Type 11 (AC), Revision 1)
The MR32 has no support for the BCM43520, only the WIFI3: Broadcom BCM43428 abgn (1x1:1 - id: 43428)
So maybe we can get some comunity lil bit hacky driver for broadcom wireless chips? Yep i don't care if it's not si opensource since it's working like it should be.
When you discover you're riding a dead horse, the best strategy is to dismount.
When You have money (dd-wrt team ) then you can make this horse a unbeatable champion. I like the idea of opensource but when i need performance then simply i don't care.
And I want a pink pony…
If you haven't been living under a rock, you'd know that there haven't been mainline Broadcom drivers (past 802.11g with b43[*]) within the last 20+ years and chances are that there won't be any in the upcoming 20+ years either. So if you want use use OpenWrt, which I just assume for those posting in this forum, Broadcom is not the wireless hardware to go with (and for wifi6+ there aren't any Broadcom wireless drivers at all).
If you want full hardware performance, you're currently getting it with filogic/ mt76 - ipq50xx/ ipq60xx/ ipq807x is behind, but usable (and ipq95xx/ ipq53xx is looking a tad more promising); Broadcom is not -and hasn't been- for the last two decades.
--
[*] yes, I know they have thrown brcmsmac/ brcmfmac over the wall, to choke further b43 development, but those have their own problems and are mostly abandoned.