request_firmware() and in-kernel modules
If my driver is compiled in-kernel (and I have module support turned off), can I still use request_firmware()? If my driver is loaded before the file system drivers are loaded, how can a user process copy the firmware to the /sys/class/firwmare/.../data device?
Quoted 2 lines · Timur Tabi
If my driver is compiled in-kernel (and I have module support turned off), can I still use
request_firmware()?
Yes.
Quoted 3 lines
If my driver is loaded before the file system drivers are loaded, how can a user process copy the firmware to the
/sys/class/firwmare/.../datadevice?
I'd recommend using the non-blocking mode, that way, when userspace finally gets running, it can handle the firmware events properly, and your kernel code will have not timed out already.
thanks,
greg k-h
Quoted 3 lines · Greg KH
I'd recommend using the non-blocking mode, that way, when userspace finally gets running, it can handle the firmware events properly, and your kernel code will have not timed out already.
Thanks Greg, that did the trick.
What the value of FW_ACTION_NOHOTPLUG? If I specify that instead of FW_ACTION_HOTPLUG, I presume I don't get automatic loading of the firwmare via the hotplug subsystem, but request_firmware() still times out. Why would I ever not want to take advantage of hotplug?