Re: [PATCH] wifi: brcmfmac: disable TX beamforming on BCM4364

From: Arend van Spriel

Date: Tue Nov 17 2026 - 14:46:57 EST


On 17/11/2026 18:50, Aditya Garg wrote:


On 17 Nov 2026, at 2:07 AM, Arend van Spriel <arend.vanspriel@xxxxxxxxxxxx> wrote:

On Wed, 4 Nov 2026 16:16:23 +0100, Andre Eikmeyer <dev@deq.rocks> wrote:
With "txbf" enabled, the BCM4364 firmware (9.30.514.0.32.5.94, as shipped
by Apple for the MacBookPro15,1) transmits a single beamformed spatial
stream (nrate VHT MCS9 NSS1 TXBF) towards a two stream AP. With "txbf"
cleared it picks two streams (VHT MCS9 NSS2) on its own. The firmware
enables "txbf" by default, so the driver has to clear it.

[...]

Tested-by: Yossef Osman <Yossef.Osman@xxxxxxxxx>
Tested-by: Aditya Garg <aditya.garg@xxxxxxxxx>
Signed-off-by: Andre Eikmeyer <dev@deq.rocks>

[...]

@@ -450,8 +451,12 @@ int brcmf_c_preinit_dcmds(struct brcmf_if *ifp)
goto done;
}

- /* Enable tx beamforming, errors can be ignored (not supported) */
- (void)brcmf_fil_iovar_int_set(ifp, "txbf", 1);
+ /* Enable tx beamforming, errors can be ignored (not supported).
+ * BCM4364 firmware enables it by default and then transmits a single
+ * beamformed stream instead of two, halving its uplink throughput.
+ */
+ (void)brcmf_fil_iovar_int_set(ifp, "txbf",
+ drvr->bus_if->chip != BRCM_CC_4364_CHIP_ID);
done:
return err;
}

The chip ID check has the same problem as in the ARP/ND offload patch [1]:
the issue is described as specific to the firmware shipped by Apple
(9.30.514.0.32.5.94), but the quirk applies to every BCM4364. Please
restrict it as suggested there.

Also, the comment says "Enable tx beamforming" while the code now
conditionally disables it. Please make the code self-explanatory, e.g. a
local variable or an explicit if (chip == BRCM_CC_4364_CHIP_ID) with the
txbf value spelled out, instead of passing a bool expression as the
iovar value.

Minor: typo "refression" in the commit message, and the subject lacks
the target tree (wireless-next) which wifibot flagged.

Since this is a throughput quirk (not a fix) I would also like to know
whether TX beamforming is functional at all on the BCM4364 or just
mis-selected by rate control, so the commit message can state the actual
root cause.

Unrelated but Airdrop conversation seems to have been stalled :(.

Indeed unrelated so let me respond to your earlier email that was more on the subject.

Regards,
Arend