Package: src:linux Followup-For: Bug #1029843 X-Debbugs-Cc: p...@akeo.ie, k...@debian.org, didi.deb...@cknow.org, debian-b...@lists.debian.org, 1029...@bugs.debian.org, 1035...@bugs.debian.org, 989...@bugs.debian.org, debian-arm@lists.debian.org Control: retitle -1 brcmfmac: requested firmware filename inconsistent with linux-firmware.git on non-devicetree systems
Thanks, Pete. I added a note[1] on the rpi4-uefi.dev GitHub repository, and from one of your fellow contributors' responses, it seems that in fact the filename-with-spaces format _is_ referenced from linux-firmware.git, in a 'WHENCE' file that is used to create symlinks (I hadn't been aware of that previously). As a result: I feel that maybe this bugreport is not valid. I suppose that some of the confusion stemmed from the fact that a single binary of a kernel module in combination with a single physical hardware device probed different firmware filenames at runtime depending on the context (ACPI vs Devicetree, in this case). (it's code, so yep, I get that it's technically _possible_ for that to happen, and perhaps it's useful to workaround limitations of existing standards, but it's not clear to me whether that's necessary here) > Note that, in case you think there may be something that we can improve > in the SMBIOS data reported by the UEFI firmware (which is currently > generated from the source code at [1], with the full output from a > Raspberry Pi 4, from UEFI Shell's smbiosview command at [2]) we can look > into updating the UEFI firmware to alter the data we output. Thank you - I'll take a look at those to learn more. [1] - https://github.com/pftf/RPi4/issues/76#issuecomment-1533295773
