Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [OT] Using CONFIG_INITRAMFS_SOURCE _and_ initrd=<path>?
Date: Mon, 29 Nov 2010 15:33:47 +0000 (UTC)	[thread overview]
Message-ID: <id0h4r$3v3$1@dough.gmane.org> (raw)

I've been experimenting with using both CONFIG_INITRAMFS_SOURCE at
kernel build time, and an initrd loaded by the boot loader.  According
to the mnaual for systemrescuecd:

   With the CONFIG_INITRAMFS_SOURCE option each kernel image contains
   its own kernel modules. And the initram.igz only contains the
   common boot scripts and programs which are used by all these
   kernels. When a kernel boots, both the embedded initramfs and the
   initram.igz are extracted into memory, then the kernel has all it
   needs to boot.

The interesting part is this:

   When a kernel boots,  _both_the_embedded_initramfs_and_the_
   initram.igz_ are extracted into memory

My experimentation seems to show otherwise, when
CONFIG_INITRAMFS_SOURCE is enabled in the kernel, the initrd loaded by
the bootloader into ram and passed to the kernel on the command-line
is ignored.

Can anybody confirm whether or not you're supposed to be able to use
both CONFIG_INITRAMFS_SOURCE _and_ an extra-kernel initrd?
   
-- 
Grant Edwards               grant.b.edwards        Yow! Did you move a lot of
                                  at               KOREAN STEAK KNIVES this
                              gmail.com            trip, Dingy?

                 reply	other threads:[~2010-11-29 15:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='id0h4r$3v3$1@dough.gmane.org' \
    --to=grant.b.edwards@gmail.com \
    --cc=buildroot@busybox.net \
    /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