From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Kernel and buildroot in 1MB
Date: Sat, 3 Mar 2012 15:29:36 +0000 [thread overview]
Message-ID: <201203031529.36487.arnout@mind.be> (raw)
In-Reply-To: <1330600410.23056.YahooMailNeo@web132105.mail.ird.yahoo.com>
On Thursday 01 March 2012 11:13:30 bifferos wrote:
> > That said, it's probably quite difficult these days to build a system
> > for which the kernel+root filesystem fits within 1 MB, as your e-mail
> > topic seems to suggest.
>
> I wouldn't say it's difficult. I'm using such a system right now to do
> something useful and, it's actually about 800K (kernel + initrd) system.
> I wrote up some notes here:
> https://sites.google.com/site/bifferboard/Home/boards-with-1mb-flash/buildroot
Impressive... But what a complex way of doing things! You can actually:
- configure buildroot to download the 3.3-rc1 kernel
- configure buildroot to use your custom kernel config
- run 'make linux-menuconfig' to tweak it if necessary
- run 'make linux-update-defconfig' to store it back to the original file
- configure buildroot to use the files.tgz tree as the skeleton of the
target filesystem
- if necessary, remove redundant files in a post-build script
- configure buildroot to pack the rootfs in the kernel as an initrd
- save the buildroot config with 'make savedefconfig' for easy distribution
Hey, it's so easy that I've created the necessary files for you! A patch
will follow this mail. After applying it, run 'make bifferboard_defconfig'
followed by 'make' and you should get a working system. It's still 972K,
because I didn't strip the busybox config too much. But it doesn't contain
a libc.so. It does still contain a non-working ldconfig and getconf,
though. I wonder BTW what either of them is doing on a system that doesn't
have HAVE_DEVFILES enabled...
If my patch gives you a working bifferboard, can you reply to it with an
Acked-by: statement (using your real name please)? Then we can include
it in buildroot.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-03-03 15:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 0:52 [Buildroot] Kernel and buildroot in 1MB bifferos
2012-03-01 7:50 ` Thomas Petazzoni
2012-03-01 11:13 ` bifferos
2012-03-03 15:29 ` Arnout Vandecappelle [this message]
2012-03-03 15:35 ` [Buildroot] [PATCH] bifferboard: new board Arnout Vandecappelle
2012-03-05 9:49 ` Thomas Petazzoni
2012-03-06 7:00 ` Arnout Vandecappelle
2012-03-11 10:58 ` [Buildroot] [PATCH v2] " Arnout Vandecappelle
2012-03-12 14:46 ` bifferos
2012-03-12 1:23 ` [Buildroot] [PATCH] " bifferos
2012-03-16 1:58 ` [Buildroot] Debugging /sbin/init startup issues bifferos
2012-03-17 4:03 ` Charles Krinke
2012-03-17 14:10 ` bifferos
2012-03-18 13:50 ` [Buildroot] [PATCH] bifferboard: new board Arnout Vandecappelle
2012-03-18 16:12 ` bifferos
2012-03-18 17:13 ` Arnout Vandecappelle
2012-03-18 19:51 ` Alexandre Pereira da Silva
2012-03-18 20:54 ` bifferos
2012-03-18 21:40 ` Arnout Vandecappelle
2012-03-19 12:36 ` bifferos
[not found] ` <4F525794.5010406@yahoo.co.uk>
2012-03-03 17:00 ` [Buildroot] Kernel and buildroot in 1MB Arnout Vandecappelle
2012-03-01 12:18 ` Peter Korsgaard
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=201203031529.36487.arnout@mind.be \
--to=arnout@mind.be \
--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