From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] initramfs doesn't get linked into kernel
Date: Sat, 27 Apr 2013 03:17:58 +0200 [thread overview]
Message-ID: <20130427031758.363b222f@skate> (raw)
In-Reply-To: <klf34k$81s$1@ger.gmane.org>
Dear Adam Nielsen,
On Sat, 27 Apr 2013 09:37:59 +1000, Adam Nielsen wrote:
> I'm trying to figure out how to get the initramfs image linked in to my kernel
> zImage. I have selected BR2_TARGET_ROOTFS_INITRAMFS (the only option I can
> find in the menuconfig containing 'initramfs') but nothing gets linked in to
> my kernel.
>
> I am using a custom kernel config, and I tried putting the filename of the
> buildroot-generated .cpio image in as CONFIG_INITRAMFS_SOURCE which linked in
> successfully, but then it won't boot as it appears you are supposed to put an
> initramfs configuration filename here instead.
>
> Is it correct that I have to manually put something into
> CONFIG_INITRAMFS_SOURCE? If so, what should I place here to use the rootfs
> generated by buildroot?
If you let Buildroot build your kernel, it does that automatically (see
the code in linux/linux.mk). If you build your kernel outside of
Buildroot, you have to set CONFIG_INITRAMFS_SOURCE correctly.
If you build your kernel outside of Buildroot, pointing
CONFIG_INITRAMFS_SOURCE to the .cpio image works just fine. I'm doing
that all the time here. Here's what I have in my kernel configuration:
CONFIG_INITRAMFS_SOURCE="../marvell-rootfs/images/rootfs.cpio"
Could you attach your Buildroot .config, and your kernel configuration
file (output/build/linux-x.y.z/.config if you build your kernel with
Buildroot) ?
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-04-27 1:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 23:37 [Buildroot] initramfs doesn't get linked into kernel Adam Nielsen
2013-04-27 1:17 ` Thomas Petazzoni [this message]
2013-04-27 9:53 ` Adam Nielsen
2013-04-27 17:34 ` Thomas Petazzoni
2013-04-27 22:50 ` Adam Nielsen
2013-05-04 0:29 ` Adam Nielsen
2013-05-04 8:25 ` Thomas Petazzoni
2013-05-04 11:35 ` Adam Nielsen
2013-05-04 17:36 ` Thomas Petazzoni
2013-05-05 1:47 ` Adam Nielsen
2013-05-05 2:11 ` Adam Nielsen
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=20130427031758.363b222f@skate \
--to=thomas.petazzoni@free-electrons.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