From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: ulf@emagii.com,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] image_types.bbclass: implement jffs2 summary images (sum.jffs2)
Date: Thu, 08 Dec 2011 22:56:10 +0000 [thread overview]
Message-ID: <1323384970.5309.92.camel@ted> (raw)
In-Reply-To: <4EE13D86.6020203@emagii.com>
On Thu, 2011-12-08 at 23:43 +0100, Ulf Samuelsson wrote:
> Not sure exactly what sumtools does,
> but as I understood it, it does things which
> the targets need to be doing at first startup otherwise.
>
> Does that not mean that the target rootfs will grow
> from 44 MB to 57 MB during that process?
>
> If it does, you never want to have the non-sumtool version.
> (I guess if you downloaded the file over a 20 bps channel to
> a nuclear submarine, you would disagree)
It doesn't. It will compute all this data into memory at each boot
increasing boot time but it won't write it back to the flash.
The sum images just mean the data can be directly loaded without
computation and reading a lot more of the flash.
Cheers,
Richard
next prev parent reply other threads:[~2011-12-08 23:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 23:23 [PATCH 0/2] rework jffs2 images creation, add jffs2 summary Andrea Adami
2011-12-06 23:23 ` [PATCH 1/2] image_types.bbclass: implement jffs2 summary images (sum.jffs2) Andrea Adami
2011-12-08 14:57 ` Tom Rini
2011-12-08 15:10 ` Martin Jansa
2011-12-08 21:30 ` Andrea Adami
2011-12-08 22:43 ` Ulf Samuelsson
2011-12-08 22:48 ` Andrea Adami
2011-12-08 22:56 ` Richard Purdie [this message]
2011-12-11 10:03 ` Martin Jansa
2011-12-11 22:20 ` Andrea Adami
2011-12-11 22:57 ` Martin Jansa
2011-12-06 23:23 ` [PATCH 2/2] image_types.bbclass: disable cleanmarkers for jffs2 images Andrea Adami
2011-12-08 14:59 ` Tom Rini
2011-12-08 18:22 ` [PATCH 0/2] rework jffs2 images creation, add jffs2 summary Saul Wold
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=1323384970.5309.92.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ulf@emagii.com \
/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