Poky Project Discussions
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Minimal images: kernel config
Date: Fri, 18 Feb 2011 09:52:59 -0800	[thread overview]
Message-ID: <4D5EB1FB.9030704@linux.intel.com> (raw)

I've been getting more and more questions regarding flash footprint, 
memory footprint, and boot time. All of these fall under the "minimal 
image" heading in my head.

Currently, poky-image-minimal is a simple subset of poky-image-sato. It 
uses busybox, but is still dynamically linked and uses the same 
somewhat-generic kernel build. By somewhat-generic I mean we have named 
features that often cover more drivers than are stricly necessary for a 
given board (usb-net comes to mind). I'd like to see minimal become a 
truly minimal image from both the userspace and kernel side point of view.

Here's my take on this. From userspace this means uclibc and a staticly 
linked busybox. From the kernel this means a static build (no modules) 
with nothing more than is required for the board's built-in peripherals 
to function, with the possible exception of something like usb-storage. 
I'd like to see a < 10M flash size and a <8M memory footprint.

Thoughts on this direction?

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


             reply	other threads:[~2011-02-18 17:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-18 17:52 Darren Hart [this message]
2011-02-18 18:25 ` Minimal images: kernel config Richard Purdie
2011-02-18 18:52   ` Mark Hatle
2011-02-18 19:08     ` Darren Hart
2011-02-18 20:33     ` Tom Rini
2011-02-18 19:15 ` Bruce Ashfield
2011-04-27  5:38   ` Kang Kai
2011-04-28 19:23     ` Bruce Ashfield

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=4D5EB1FB.9030704@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=poky@yoctoproject.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