From: Seewer Philippe <philippe.seewer-omB+W0Dpw2o@public.gmane.org>
To: Scott James Remnant <scott-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
Cc: maximilian attems <max-U9r9yeDMy7A@public.gmane.org>,
initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kernel-team-nLRlyDuq1AZFpShjVBNYrg@public.gmane.org,
debian-kernel-0aAXYlwwYIJuHlm7Suoebg@public.gmane.org
Subject: Re: initramfs-tools stable release 0.93.3
Date: Fri, 7 Aug 2009 09:37:24 +0200 [thread overview]
Message-ID: <4A7BD9B4.1090109@bfh.ch> (raw)
In-Reply-To: <1248871471.23840.50.camel@quest>
Scott James Remnant wrote:
[snip]
>>> Slimming the initramfs right down to the essentials reduces the boot
>>> time by over a second! Paradoxically, this means that the driver can be
>>> loaded in the real system at roughly the same time point as it would be
>>> loaded in a bloated initramfs.
>> well afair the intel fast boot doesn't use initramfs in the fast path
>> at all
>>
> Our fast boot does use an initramfs.
This is a bit offtopic: Do you have any more info about intel fast boot?
I use an intel atom board at home which supposedly has intel fast boot,
but I haven't found any info on how to make use of that.
Thanks,
Philippe
>
> Scott
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-08-07 7:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 15:30 initramfs-tools stable release 0.93.3 maximilian attems
[not found] ` <20090610153017.GA19401-U9r9yeDMy7A@public.gmane.org>
2009-06-11 10:42 ` Scott James Remnant
2009-07-25 9:21 ` maximilian attems
[not found] ` <20090725092159.GJ11967-U9r9yeDMy7A@public.gmane.org>
2009-07-29 12:44 ` Scott James Remnant
2009-08-07 7:37 ` Seewer Philippe [this message]
[not found] ` <4A7BD9B4.1090109-omB+W0Dpw2o@public.gmane.org>
2009-08-07 14:00 ` Alan Jenkins
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=4A7BD9B4.1090109@bfh.ch \
--to=philippe.seewer-omb+w0dpw2o@public.gmane.org \
--cc=debian-kernel-0aAXYlwwYIJuHlm7Suoebg@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kernel-team-nLRlyDuq1AZFpShjVBNYrg@public.gmane.org \
--cc=max-U9r9yeDMy7A@public.gmane.org \
--cc=scott-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.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