linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mark Hatle <mhatle@mvista.com>
To: "Kevin P. Dankwardt" <k@kcomputing.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Fast boot times
Date: Mon, 07 Jun 2004 22:38:31 -0500	[thread overview]
Message-ID: <40C534B7.1090902@mvista.com> (raw)
In-Reply-To: <KCEOLLHGFJIAFNAMGACHIEGADMAA.k@kcomputing.com>


There are some simple things you need to do for this.  The first is
abondon the idea that EVERYTHING needs to be done in 50msec!  What you
really want is a base set of functionality that exists in the 50msec
range, then you bring up the rest of the functionality either as
required or in parallel with other system tasks.

What you want to do is have a minimal driver set built into the kernel.
  Also, get your firmware optimized as much as possible.  A lot of the
time, the firmware can eat a large chunk of time.

Basically you will boot the kernel with minimal drivers (perhaps just a
single filesystem driver).  Once the kernel hits userspace, load the
driver modules in an appropriate order.  If that is still not fast
enough, you will have to modify the drivers to allow for parallel system
initialization.

So my point in all of the above is figure out the exact minimum
requirements you have.  Work on getting that up "first".  Then expand to
your full compliment of drivers and userspace applications.

--Mark

Kevin P. Dankwardt wrote:
> I am participating in a project that has a challenging boot time
> requirement. We need a Linux boot solution where we have booted in the
> 50msec range, talking on a protocol stack, from a COLD Start (power being
> applied to the board.) The loading of the drivers and the stack
> initialization has to occur within 50msec.
>
> Does anyone have any leads/ideas for being able to meet this deadline?
>
> Thanks,
> Kevin Dankwardt
>
>
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-06-08  3:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-04 12:11 PPC tool chain - uClibc MuthuGanesh M
2004-06-04 16:15 ` Wolfgang Denk
2004-06-08  1:57   ` Fast boot times Kevin P. Dankwardt
2004-06-08  3:38     ` Mark Hatle [this message]
2004-06-08  8:35     ` Marius Groeger
2004-06-08  8:49       ` Stefan Nickl
2004-06-08 13:48     ` Kenneth Johansson
2004-06-07  5:42 ` PPC tool chain - uClibc sanjeev ramachandran

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=40C534B7.1090902@mvista.com \
    --to=mhatle@mvista.com \
    --cc=k@kcomputing.com \
    --cc=linuxppc-embedded@lists.linuxppc.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).