From: "Kevin P. Dankwardt" <k@kcomputing.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Fast boot times
Date: Mon, 7 Jun 2004 20:57:25 -0500 [thread overview]
Message-ID: <KCEOLLHGFJIAFNAMGACHIEGADMAA.k@kcomputing.com> (raw)
In-Reply-To: <20040604161515.C28C6C109F@atlas.denx.de>
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/
next prev parent reply other threads:[~2004-06-08 1:57 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 ` Kevin P. Dankwardt [this message]
2004-06-08 3:38 ` Fast boot times Mark Hatle
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=KCEOLLHGFJIAFNAMGACHIEGADMAA.k@kcomputing.com \
--to=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).