On 1/29/2020 4:02 PM, Kalle Valo wrote:
Arend Van Spriel <arend.vanspriel@xxxxxxxxxxxx> writes:
There is also precedent for users acquiring firmware themselves via the
b43 and b43legacy drivers, where users have to use a script to extract
the firmware from other drivers.
I wish I had a better answer to this, but I don't work for Broadcom or
anyone associated with it and am just trying to get the Mac I was given
for $DAYJOB to work with Linux. Perhaps since you do you'd be willing
to ask them to release the firmware.
The alternative is that the chip doesn't work at all (and can't be added
via the new_id sysfs entry because of the rambase setting) and users
have to compile a custom patched kernel to make their wireless card work
at all. I'd really prefer to avoid that if possible, since it's
a strictly worse experience in every way.
How about putting this device under some Kconfig flag. If distro
kernel start probing the device and fail, most users will probably
turn to their distro for help. Having a Kconfig with a good
description could avoid that. It would mean an extra step of building
the driver though.
I don't understand the issue you are trying to solve. If the firmware
image is missing there's a clear error message in the log and the kernel
continues to operate normally, right? That way users have a clear
understanding why their wireless is not working, and hopefully push
Broadcom to release the firmware with a suitable license :)
Hi Kalle,
Actually as there is precedent of firmwareless drivers in distros I am
fine with the change as is.
Regards,
Arend
