On Tue, Nov 9, 2021 at 8:42 AM Aleksei Bavshin
wrote:
> A module can load a firmware binary with the `request_firmware` API at
> any moment of it's lifetime. Usually, this happens when the module is
> initialized or discovers a new supported device, but I don't believe
> that is a strictly enforc
no information about the mapping of device ids -> fw
files available. I.e., let's say, `iwlwifi` in 5.15.0 declares 47 unique
firmware files and 77 supported PCI ids. But each of those PCI ids would
require only a small subset of these 47 firmware binaries. Thus, the
`iwl.*-firmware` pac
have:
$ rpm-qa|grepfirmware |wc-l
27
I seriously doubt I need all of them. I definitely do not need them on server, where I never add any new HW. But how do
I know which one is in use and which not?
2. How the firmware packages actually work? Do I need them to be present every time? Or when m
