Broadcom FullMAC Wi-Fi WCC vendor plug-in
A Broadcom-supplied extension to the brcmfmac FullMAC Wi-Fi driver that handles vendor-specific firmware behaviour for Broadcom's mobility wireless chipsets, the kind integrated into Raspberry Pi 4 and Compute Module 4 boards and other embedded systems with onboard 802.11ac. It plugs into the multi-vendor framework added to brcmfmac in 2022.
recommendation
It should stay because this is the vendor-specific firmware path that brcmfmac uses to talk to Broadcom mobility Wi-Fi chips, including the ones still shipping in 2025 on Raspberry Pi 4 and Compute Module 4 (which Raspberry Pi has committed to producing through at least 2034). The code was added in late 2022 and received fresh work in 2024 for WPA3/SAE handling, so it is actively maintained.
repository signals
sources
- lore.kernel.org
The WCC support was added in 2022 as the vendor-specific firmware-API path for brcmfmac, with the patch text stating the WCC variant was selected for all devices at that time.
- lore.kernel.org
The WCC path received functional work in 2024 for SAE/WPA3 handling via the multi-vendor framework, indicating maintenance beyond initial bring-up.
- raspberrypi.com
Raspberry Pi Compute Module 4 remained an actively sold product in 2025+, with optional 2.4/5 GHz Wi-Fi and an official production horizon through at least January 2034.
- raspberrypi.com
Raspberry Pi 4 Model B is an official current product page for a Broadcom-based platform with integrated 802.11ac wireless, supporting the conclusion that Broadcom FullMAC Wi-Fi remains in new deployments.
codex reasoning notes (technical)
exec_command on local git history showed the directory was introduced in late 2022 and saw real functional updates in 2024, with no removal/deprecation-oriented history found in local log grep. exec_command on module.c confirmed it is a plugin for 'Broadcom mobility chipsets'. The two lore URLs were obtained from commit Link tags in local git log output; the Raspberry Pi URLs were obtained via web search. Replacement driver is null because this directory is a brcmfmac vendor plugin, not a superseded standalone driver. Deployment level is inferred as medium: still present in current embedded/SBC products, but not a broad PC-class market.