public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* request_firmware() and in-kernel modules
@ 2007-10-19 17:35 Timur Tabi
  2007-10-21  4:07 ` Greg KH
  0 siblings, 1 reply; 3+ messages in thread
From: Timur Tabi @ 2007-10-19 17:35 UTC (permalink / raw)
  To: linux-kernel

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?


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: request_firmware() and in-kernel modules
  2007-10-19 17:35 request_firmware() and in-kernel modules Timur Tabi
@ 2007-10-21  4:07 ` Greg KH
  2007-10-22 22:01   ` Timur Tabi
  0 siblings, 1 reply; 3+ messages in thread
From: Greg KH @ 2007-10-21  4:07 UTC (permalink / raw)
  To: Timur Tabi; +Cc: linux-kernel

On Fri, Oct 19, 2007 at 12:35:38PM -0500, Timur Tabi wrote:
> If my driver is compiled in-kernel (and I have module support turned off), 
> can I still use request_firmware()?

Yes.

> 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?

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: request_firmware() and in-kernel modules
  2007-10-21  4:07 ` Greg KH
@ 2007-10-22 22:01   ` Timur Tabi
  0 siblings, 0 replies; 3+ messages in thread
From: Timur Tabi @ 2007-10-22 22:01 UTC (permalink / raw)
  To: Greg KH; +Cc: linux-kernel

Greg KH wrote:

> 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?


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2007-10-22 22:01 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-10-19 17:35 request_firmware() and in-kernel modules Timur Tabi
2007-10-21  4:07 ` Greg KH
2007-10-22 22:01   ` Timur Tabi

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox