Description of problem:
A default Fedora 39 install on a RPi CM4 that uses brcmfmac-firmware v20231211 currently fails to correctly load the brcmfmac43455-sdio driver due to a missing/incorrect symlink for the CM4 platform. Below is a trivial symlink fix for this, but hopefully a helpful one.

Version-Release number of selected component (if applicable):
brcmfmac-firmware v20231211

How reproducible:
Trivially and consistently.

Steps to Reproduce:
1. Write (any) fedora aarch64 to an SD card, or the CM4 eMMC.
2. Boot.
3. Update to latest brcmfmac-firmware release (v20231211, at time of writing) via "sudo dnf up -y --refresh"
4. Note despite the correct firmware packages being installed, the output of "sudo lshw" indicates no driver is loaded for mmc@1:0001:1, where the wireless interface is located on the BCM2711.
5. Note the output of "dmesg | grep brcmfmac" (see below) further suggests the SDIO driver .txt could not be found.
6. Create a symlink named "brcm/brcmfmac43455-sdio.raspberrypi,4-compute-module.txt.xz" to "brcmfmac43455-sdio.raspberrypi,4-model-b.txt.xz"
7. Reload the brcmfmac kernel module via "sudo modprobe -r brcmfmac && sudo modprobe brcmfmac"
8. Note as evident from dmesg, lshw output, that the brcmfmac43455-sdio is now correctly loaded and the wlan0 interface is now available.

Actual results:

With brcmfmac-firmware v20231211,running "dmesg | grep brcmfmac" returns:
[   21.935652] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[   21.936705] usbcore: registered new interface driver brcmfmac
[   21.946819] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-compute-module.bin failed with error -2
[   22.043741] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.txt failed with error -2
[   23.044697] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50

Expected results:
"dmesg | grep brcmfmac" output, as below, noting the driver loads as expected, and the subsequent creation of a wlan0 network interface:

[10018.250485] usbcore: deregistering interface driver brcmfmac
[10018.526421] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[10018.526574] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-compute-module.bin failed with error -2
[10018.530345] usbcore: registered new interface driver brcmfmac
[10018.776624] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2)
[10018.777005] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Apr 15 2021 03:03:20 version 7.45.234 (4ca95bb CY) FWID 01-996384e2

Additional info:
I note there are symlinks for some platform targets provided in /lib/firmware/brcm including:

brcmfmac43455-sdio.raspberrypi,4-model-b.txt.xz
brcmfmac43455-sdio.Raspberry Pi Foundation-Raspberry Pi Compute Module 4.txt.xz

The second is a symlink to the first, but doesn't reflect what is dmesg actually shows the OS attempt to load. Loading this SDIO driver works as expected for (any) near-identical RPi 4B installs with the same driver, which was curious.

By simply copying the 4-model-b.txt.xz, or creating a further symlink to this, for the target noted in dmesg, as below, resolves this issue, and the device driver then loads as expected:

brcm/brcmfmac43455-sdio.raspberrypi,4-compute-module.txt.xz

On reloading the brcmfmac kernel module via "sudo modprobe -r brcmfmac && sudo modprobe brcmfmac" the output of "dmesg | grep brcmfmac" then returns as expected, and notes the driver now loads successfully.