linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Kernel Firmware Loading
Date: Mon, 31 Oct 2005 14:35:25 +0000	[thread overview]
Message-ID: <20051031143525.GA780@vrfy.org> (raw)
In-Reply-To: <4365DBD9.2040407@ukonline.co.uk>

On Mon, Oct 31, 2005 at 02:27:35PM +0100, Duncan Sands wrote:
> On Monday 31 October 2005 14:10, Kay Sievers wrote:
> > On Mon, Oct 31, 2005 at 11:59:05AM +0100, Duncan Sands wrote:
> > > It would be nice if the driver was more helpful here,
> > > by trying to load the firmware more than once.  It's
> > > a bit tricky though.  For example, you could say: "if
> > > the firmware wasn't found, then try to load it when
> > > someone opens a connection".  Unfortunately, while this
> > > is possible with the speedtch modem, this isn't possible
> > > with the connexant access runner: you can't correctly create
> > > an ATM device unless the firmware was already loaded into
> > > the modem, which means it's impossible to even try to
> > > open a connection before the firmware is loaded.  Another
> > > possibility is to try to load the firmware every couple
> > > of seconds.  I could certainly do that, but it's not very
> > > elegant.
> > > 
> > > In any case, I too am interested in hearing what the hotplug
> > > people have to say.
> > 
> > I like to see the stupid timeout in the request_firmware to completely
> > go away. It doesn't make any sense. The drivers should use the async
> > version of request_firmware() anyway and the so called syncronous version
> > should be removed.
> 
> that's fine with me, even though the loading in the speedtouch driver is
> fundamentally synchronous (no useful work can be done until the firmware
> is loaded): it is easy to build what I want on top of the async version.
> 
> > If the kernel sends the request out and it gets lost during early boot,
> > you can just fulfill it any time later by looking at the outstanding
> > requests in sysfs.
> 
> But isn't the problem different: the request did not get lost: it reached
> the script (or whatever), the script couldn't find the firmware file and
> cancelled the load?  This has nothing to do with timeouts and events
> getting lost...

Well, just check with the firmware script and never cancel a request
if you are in initramfs.

Kay


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2005-10-31 14:35 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31  8:54 Kernel Firmware Loading Andrew Benton
2005-10-31  9:37 ` Alexander E. Patrakov
2005-10-31 10:04 ` Andrew Benton
2005-10-31 10:59 ` Duncan Sands
2005-10-31 10:59 ` Alexander E. Patrakov
2005-10-31 11:08 ` Marco d'Itri
2005-10-31 11:18 ` Duncan Sands
2005-10-31 11:50 ` Marco d'Itri
2005-10-31 13:10 ` Kay Sievers
2005-10-31 13:27 ` Duncan Sands
2005-10-31 14:35 ` Kay Sievers [this message]
2005-10-31 14:41 ` Duncan Sands
2005-10-31 14:54 ` Kay Sievers
2005-10-31 16:29 ` linas
2005-10-31 16:33 ` Marco d'Itri
2005-10-31 21:15 ` Andrew Benton
2005-11-01  9:48 ` Duncan Sands
2005-11-01 11:15 ` Andrew Benton
2005-11-01 15:56 ` Alexander E. Patrakov
2005-11-01 16:59 ` linas
2005-11-01 21:19 ` Andrew Benton
2005-11-02  2:09 ` Alexander E. Patrakov
2005-11-02  6:20 ` Alexander E. Patrakov
2005-11-02  6:28 ` Alexander E. Patrakov
2005-11-02 23:22 ` Andrew Benton
2005-11-03  8:08 ` Duncan Sands
2005-11-04 14:46 ` Alexander E. Patrakov
2005-11-04 14:52 ` Duncan Sands
2005-11-04 15:14 ` Alexander E. Patrakov
2005-11-07 15:48 ` Patrick Mansfield
2005-11-08  8:16 ` Alexander E. Patrakov
2005-11-08 17:54 ` Greg KH
2005-11-08 18:37 ` Patrick Mansfield

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=20051031143525.GA780@vrfy.org \
    --to=kay.sievers@vrfy.org \
    --cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).