CONFIG_FW_LOADER
Currently the help for this states:
CONFIG_FW_LOADER:
This option is provided for the case where no in-kernel-tree modules require userspace firmware loading support, but a module built outside the kernel tree does.
Is it just me or is this somewhat misleading? Don't all modules that load firmware from userspace require this?
Hi Adrian,
Quoted 11 lines
Currently the help for this states:
CONFIG_FW_LOADER:
This option is provided for the case where no in-kernel-tree modules require userspace firmware loading support, but a module built outside the kernel tree does.Is it just me or is this somewhat misleading? Don't all modules that load firmware from userspace require this?
all drivers that do use 'select FW_LOADER' and so they trigger building this module anyway. The config option is purely if you have a driver that is built outside the tree and wanna use request_firmware().
Regards
Marcel
Quoted 11 lines · Marcel Holtmann
Hi Adrian,
Quoted 9 lines
Currently the help for this states:
CONFIG_FW_LOADER:
This option is provided for the case where no in-kernel-tree modules require userspace firmware loading support, but a module built outside the kernel tree does.
Quoted 7 lines
Quoted 2 lines
Is it just me or is this somewhat misleading? Don't all modules that load firmware from userspace require this?
all drivers that do use 'select
FW_LOADER' and so they trigger building this module anyway. The config option is purely if you have a driver that is built outside the tree and wanna userequest_firmware().
OK. Guess the issue is that my module doesn't select this. I'll patch that.