public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: request_firmware() and in-kernel modules
Date: Mon, 22 Oct 2007 17:01:44 -0500	[thread overview]
Message-ID: <471D1DC8.5090802@freescale.com> (raw)
In-Reply-To: <20071021040757.GC24869@kroah.com>

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?


      reply	other threads:[~2007-10-22 22:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=471D1DC8.5090802@freescale.com \
    --to=timur@freescale.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox