linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: linux-embedded@vger.kernel.org
Subject: selecting initramfs support without initrd?
Date: Tue, 24 Jun 2008 18:11:01 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0806241805390.5000@localhost.localdomain> (raw)


  i'm not sure if this is the proper forum for this, but while
perusing the early boot code, i noticed that selecting the config
variable BLK_DEV_INITRD gives you support for both initramfs, and an
initrd image.

  however, with embedded systems, isn't it more common to use
initramfs and not need initrd at all (depending on the functionality
of the bootloader)?  and if that's true, might there not be some
benefit in splitting those two features (initramfs versus initrd) so
you could select initramfs all by itself, and not compile in any
initrd support whatsoever?

  based on a quick inspection of the source under init/, it would seem
that you could whack out sizable chunks of code if you had no need for
initrd, but i could be wrong.

rday
--

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
    Have classroom, will lecture.

http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================

             reply	other threads:[~2008-06-24 22:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24 22:11 Robert P. J. Day [this message]
2008-06-26  9:40 ` selecting initramfs support without initrd? Leon Woestenberg
2008-07-01  4:46 ` Rob Landley

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=alpine.LFD.1.10.0806241805390.5000@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=linux-embedded@vger.kernel.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).