linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kenneth Johansson <ken@switchboard.ericsson.se>
To: "Kevin P. Dankwardt" <k@kcomputing.com>
Cc: "linuxppc-embedded@lists.linuxppc.org"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Fast boot times
Date: Tue, 08 Jun 2004 15:48:17 +0200	[thread overview]
Message-ID: <1086702496.4640.8.camel@spawn.uab.ericsson.se> (raw)
In-Reply-To: <KCEOLLHGFJIAFNAMGACHIEGADMAA.k@kcomputing.com>


On Tue, 2004-06-08 at 03:57, 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?

You don't say much about the hardware but I would say it's a borderline
case even if you put a lot of work into it.

say you have a 8bit flash 120ns access time that gives
8.3 MB/sec thus you can only copy 400kB data in 50ms so you have barley
enough time getting the data into dram before your time is up.

It's not going to happen just checking a config option that's for sure.


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

  parent reply	other threads:[~2004-06-08 13:48 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
2004-06-08  8:35     ` Marius Groeger
2004-06-08  8:49       ` Stefan Nickl
2004-06-08 13:48     ` Kenneth Johansson [this message]
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=1086702496.4640.8.camel@spawn.uab.ericsson.se \
    --to=ken@switchboard.ericsson.se \
    --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).