From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] kernel size
Date: Mon, 3 Nov 2008 11:15:06 +0100 [thread overview]
Message-ID: <20081103111506.1005c517@surf> (raw)
In-Reply-To: <000001c93d37$d5a696d0$80f3c470$@be>
Le Sun, 2 Nov 2008 23:10:37 +0100,
"steve caster" <steve@c2root.be> a ?crit :
> I am trying to build a kernel with buildroot and are using a separate
> .config file which I made myself. The kernel is working, yet is about
> 90MB is size. This is unbelievable as I nearly don't have any
> modules. What could make is so big?
By chance, aren't you using an initramfs, included in the kernel, which
contains your root filesystem ? That could easily explain the large
size of your kernel image.
This is something that is done automatically by Buildroot if you
enabled BR2_TARGET_ROOTFS_INITRAMFS.
Sincerly,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2008-11-03 10:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-02 22:10 [Buildroot] kernel size steve caster
2008-11-03 8:41 ` Peter Korsgaard
2008-11-03 15:05 ` steve at c2root.be
2008-11-03 10:15 ` Thomas Petazzoni [this message]
2008-11-03 10:26 ` Ivan Kuten
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=20081103111506.1005c517@surf \
--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