# WCN6750 WLAN board data (calibration, Qualcomm/Fairphone) - taken from the
# stock modem partition on-device instead of being shipped (fp6 repo
# journal/base/ 2026-10-14, journal/blobs/). The device tree asks ath11k for
# the Fairphone_Gen_6 entry; upstream linux-firmware's board-2.bin has none,
# the driver silently falls back to generic data, and the FP6 Plus does not
# associate on that (user report 2026-10-14; the FP6 happens to work either
# way). The container built here is upstream's file with every entry kept
# plus the device's own bdwlan.elf under the requested name; it lives in
# /lib/firmware/updates, which the loader searches first. Active slot first,
# the other slot as fallback; no hash pin - calibration data is OEM data and
# the WLAN firmware verifies what it is given.
ath11k-bdf modem_a,modem_b image/qca6750/bdwlan.elf bus=ahb,qmi-chip-id=1,qmi-board-id=255,variant=Fairphone_Gen_6 /usr/lib/firmware/ath11k/WCN6750/hw1.0/board-2.bin.zst /usr/lib/firmware/updates/ath11k/WCN6750/hw1.0/board-2.bin
# Fallback for a driver that probed before extraction (the service runs
# pre-coldplug, so this normally no-ops): re-probing ath11k restarts the
# WPSS remoteproc and the firmware reads the new container; the association
# comes back through NetworkManager.
rebind platform 17110040.wifi