public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Javier Pello <javier.pello@urjc.es>
To: david@lang.hm
Cc: linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: [PATCH] request_firmware: skip timeout if userspace was not  notified
Date: Sat, 04 Aug 2007 23:20:49 +0200	[thread overview]
Message-ID: <46B4EDB1.1070808@urjc.es> (raw)
In-Reply-To: <Pine.LNX.4.64.0708041007430.6905@asgard.lang.hm>

On Sat, 4 Aug 2007, David Lang wrote:
> what I've been told is that with the drive built-in instead of
> modular you can create a filesystem that has only the firmware
> on it, nothing else, and have the kernel find and load it (no
> userspace software involved)

I'm afraid my understanding of the kernel is not very deep, so
I don't know of this method you're describing.

Anyway, if there's no userspace involved then nothing should
change. The patch I sent only affects the behaviour of the kernel
when it actually tries to send a firmware request to userspace
(and it determines that the request was not received). If the
kernel loads a firmware image without userspace support, it must
do so in a codepath different from request_firmware, whose point
is precisely to send a firmware request and wait for it, and
request_firmware is the only function that effectively changes
with my patch.

Javier



  reply	other threads:[~2007-08-04 21:20 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-03 19:07 [PATCH] request_firmware: skip timeout if userspace was not notified Javier Pello
2007-08-04  5:21 ` david
2007-08-04  8:50   ` Javier Pello
2007-08-04 17:09     ` david
2007-08-04 21:20       ` Javier Pello [this message]
2007-08-06 12:24 ` Cornelia Huck
2007-08-06 20:23   ` Javier Pello
     [not found]     ` <20070807125844.4d756b04@gondo lin.boeblingen.de.ibm.com>
2007-08-07 10:58     ` Cornelia Huck
2007-08-07 11:46       ` Kay Sievers
2007-08-07 12:10         ` Cornelia Huck
2007-08-07 12:31           ` Kay Sievers
2007-08-07 12:48             ` Cornelia Huck
2007-08-07 12:47           ` Javier Pello
2007-08-07 12:57             ` Kay Sievers
2007-08-07 13:15               ` Cornelia Huck
2007-08-07 13:59               ` Javier Pello
2007-08-07 14:08                 ` Kay Sievers
2007-08-07 14:38                   ` Cornelia Huck
2007-08-09  9:13                   ` Javier Pello
2007-08-09  9:21                     ` Kay Sievers
2007-08-09  9:26                     ` Cornelia Huck
2007-08-07 14:26                 ` Cornelia Huck
2007-08-09  9:36                   ` Javier Pello
2007-08-09 11:58                     ` Kay Sievers
2007-08-10 21:24                       ` Javier Pello
2007-08-11 13:26                         ` Kay Sievers
2007-08-07 20:05 ` Andrew Morton

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=46B4EDB1.1070808@urjc.es \
    --to=javier.pello@urjc.es \
    --cc=david@lang.hm \
    --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