From: Tom Zanussi <tom.zanussi@intel.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Poky Project <poky@yoctoproject.org>
Subject: Re: "core" explosion?
Date: Mon, 25 Apr 2011 09:41:17 -0500 [thread overview]
Message-ID: <1303742477.11649.7.camel@elmorro> (raw)
In-Reply-To: <4DB565BE.7010606@mlbassoc.com>
On Mon, 2011-04-25 at 05:14 -0700, Gary Thomas wrote:
> I've been building from a Poky tree, keeping up to date with
> the master branch for quite some time. Recently, I used this
> tree to build to do some testing on my [emenlow-like] Atom.
>
> Using the external meta-intel, I've built for atom-pc since it's
> supported by core (but sadly doesn't work on my Atom PC!) and
> emenlow (which does work). I've noticed quite a change in the
> size of images over the past month:
>
> ls -l /work/tmp/*.hddimg
> -rw-r--r-- 1 gthomas gthomas 521244672 Apr 22 15:00 /work/tmp/core-image-sato-live-atom-pc.hddimg
> -rw-r--r-- 1 gthomas gthomas 2056809472 Apr 22 22:28 /work/tmp/core-image-sato-live-emenlow.hddimg
> -rw-r--r-- 1 gthomas gthomas 508077056 Mar 21 12:37 /work/tmp/poky-image-sato-live-atom-pc.hddimg
> -rw-r--r-- 1 gthomas gthomas 1032937472 Mar 22 05:40 /work/tmp/poky-image-sato-live-emenlow.hddimg
>
> Notice that with the new "core" images, the size is bigger, but
> why is the emenlow image _doubled_ whereas the atom-pc version only
> grew by around 4%?
Previous to the below commit, the IMAGE_ROOTFS_SIZE overrides were being
ignored and the rootfs size defaulted to the actual image size + 20%.
Now IMAGE_ROOTFS_SIZE is driving the image sizes as expected.
commit adac5a690fd5b4239bb59ec54e3e5174dbcf29e9
Author: Richard Purdie <richard.purdie@linuxfoundation.org>
Date: Thu Mar 24 12:29:19 2011 +0000
image.bbclass: Move ROOTFS_SIZE into runimagecmd() function
prev parent reply other threads:[~2011-04-25 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 12:14 "core" explosion? Gary Thomas
2011-04-25 14:41 ` Tom Zanussi [this message]
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=1303742477.11649.7.camel@elmorro \
--to=tom.zanussi@intel.com \
--cc=gary@mlbassoc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.