mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jon Masters <jonathan@jonmasters.org>
To: George Kumar <grgkumar4@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is there a way to set the order of initialization of different systems ?
Date: Fri, 30 Jan 2009 04:41:26 -0500	[thread overview]
Message-ID: <1233308486.3937.113.camel@perihelion.bos.jonmasters.org> (raw)
In-Reply-To: <5f695cd0901300103o31cb92f4o9feb8c598465617c@mail.gmail.com>

On Fri, 2009-01-30 at 01:03 -0800, George Kumar wrote:

> I would like to explore if there is a way so that I can set the order
> of initialization of different kernel sub systems. The main reason I
> would like to do this is because I have a network driver built
> statically in the kernel which wants to download firmware from the
> disk, but the IDE subsystem and root FS is not mounted yet so it
> basically hangs for a minute waiting to dowload firmware and then
> proceeds with the boot sequence. If I could ensure that IDE subsys is
> initialized and root FS is mounted before networking is initialized,
> this problem probably will not occur.

This is why we have initrds and similar. What you want is already done
quite successfully by a number of implementations in which the driver
will load, and cause a uevent to be emitted as it seeks firmware that
will be supplied to it. There's absolutely no reason for your driver to
be reading the firmware files directly from disk when we have
infrastructure like request_firmware around.

LWN wrote this article back in 2003: http://lwn.net/Articles/32997/

Jon.



      reply	other threads:[~2009-01-30  9:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30  9:03 George Kumar
2009-01-30  9:41 ` Jon Masters [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=1233308486.3937.113.camel@perihelion.bos.jonmasters.org \
    --to=jonathan@jonmasters.org \
    --cc=grgkumar4@gmail.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

all inboxes | Powered by JetHome®