brcmsmac: firmware
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 16 lines · John Talbut
Quoted 13 lines · Arend van Spriel
Quoted 3 lines · John Talbut
As a matter of curiosity, why is the code currently in the firmware not included in the kernel driver?
Well. the kernel driver is what is running on the host. In your case on the Atom processor. The firmware contains of initialization data for the device and code that is using an instruction set that is dedicated to the broadcom device so there is no way to move that into the driver other than as a binary blob, but that is not acceptable in open-source Linux drivers. So people in the community invented the user-space firmware loading stuff.
Quoted 1 line
Gr. AvS
Quoted 8 lines
Hi Arend
Hmm. As I understand it, if the source code for the initialization data for the device and code that is using an instruction set that is dedicated to the broadcom device was released then the code could be compiled into the kernel.
Do you have any sense of why Broadcom does not do this?
Well. Your understanding is different from mine. Here is mine: the linux kernel aims for a separation between kernel code and firmware (mainly to resolve licensing issues, I think) and all drivers with embedded firmware have/are converted to using the request_firmware API. This is described in [1].
Gr. AvS
[1]
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/firmware/README.AddingFirmware