From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Matthieu CASTET <matthieu.castet@parrot.com>
Cc: Marco Stornelli <marco.stornelli@gmail.com>,
Constantine Shulyupin <const@makelinux.com>,
"linux-embedded@vger.kernel.org" <linux-embedded@vger.kernel.org>
Subject: Re: Super Fast Boot of Embedded Linux: 300 ms from boot loader to shell
Date: Thu, 14 Apr 2011 20:52:04 +0200 [thread overview]
Message-ID: <20110414185204.GJ3811@pengutronix.de> (raw)
In-Reply-To: <4DA6A5A7.2060701@parrot.com>
On Thu, Apr 14, 2011 at 09:43:35AM +0200, Matthieu CASTET wrote:
> Not to say such case are not interesting : loading a linux kernel with
> only a serial driver, a ramdisk and a shell as init doesn't reflect
> reality.
>
> In real product what you want if fast user interaction (sound,
> mounting big filesystem with user data, lcd display, ...)
Well, it depends on the application. In the automotive box I've shown
the barebox based boot optimizations for in my ELC-E talk, the task is
to get CAN communication running in < 200 ms. For that kind of
application it's useful to be in userspace as fast as possible, just in
order to have one socket-can application running, and everything else
comes later.
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2011-04-14 18:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 14:02 Super Fast Boot of Embedded Linux: 300 ms from boot loader to shell Constantine Shulyupin
2011-04-11 16:53 ` Marco Stornelli
2011-04-13 14:53 ` Constantine Shulyupin
2011-04-13 17:27 ` Marco Stornelli
2011-04-14 7:43 ` Matthieu CASTET
2011-04-14 18:52 ` Robert Schwebel [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=20110414185204.GJ3811@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=const@makelinux.com \
--cc=linux-embedded@vger.kernel.org \
--cc=marco.stornelli@gmail.com \
--cc=matthieu.castet@parrot.com \
/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).