Skip to contentSkip to conversation

Adding sumtool to a JFFS2 build to speed up first boot

DISCUSSION Ulf Samuelsson 4 participants 6 messages Oct 29, 2011 – Dec 7, 2011

lore
Share & tools
lore
#0 lore raw

Trying to solve another problem I came up with changing IMAGE_CMD_jffs2 defined in conf/bitbake.conf by redefining it in conf/local.conf.

During that process I noticed the "sumtool" utility which works on the jffs2 image, doing some bookkeeping which then does not have to be done on the target.

I unserstand, this can speed up loading significantly. Any reason not using this in OE?

Signature · 2 lines
Best Regards
Ulf Samuelsson
#1 lore raw
Quoted 11 lines · Ulf Samuelsson

Trying to solve another problem I came up with changing IMAGE_CMD_jffs2 defined in conf/bitbake.conf by redefining it in conf/local.conf.

During that process I noticed the "sumtool" utility which works on the jffs2 image, doing some bookkeeping which then does not have to be done on the target.

I unserstand, this can speed up loading significantly. Any reason not using this in OE?

Last time I looked at this, the reason was that you had to re-jigger the IMAGE_CMD a bit and you also have to take care as not all of the options are the same between mkfs.jffs2 and sumtool. At least the first part might be easier with oe-core and the reworked image class. The latter part is just annoying.

Signature · 1 line
Tom
#2 lore raw
Quoted 20 lines · Tom Rini
Quoted 11 lines · Ulf Samuelsson

Trying to solve another problem I came up with changing IMAGE_CMD_jffs2 defined in conf/bitbake.conf by redefining it in conf/local.conf.

During that process I noticed the "sumtool" utility which works on the jffs2 image, doing some bookkeeping which then does not have to be done on the target.

I unserstand, this can speed up loading significantly. Any reason not using this in OE?

Last time I looked at this, the reason was that you had to re-jigger the IMAGE_CMD a bit and you also have to take care as not all of the options are the same between mkfs.jffs2 and sumtool. At least the first part might be easier with oe-core and the reworked image class. The latter part is just annoying.

Quoted 4 lines

--
Tom

FWIW we are defining our jffs2-summary in

http://cgit.openembedded.org/meta-handheld/tree/conf/machine/include/zaurus.inc

This works beautifully in oe-dev but not using oe-core for it sets IMAGE_CMD_jffs2 = and this can not be overriden
We would just need a weak assignment in image_types.bbclass or maybe a new image type like IMAGE_CMD_jffs2-summary and related commands.

Regards

Andrea

#3 lore raw
Quoted 25 lines · Andrea Adami
Quoted 23 lines · Tom Rini
Quoted 11 lines · Ulf Samuelsson

Trying to solve another problem I came up with changing IMAGE_CMD_jffs2 defined in conf/bitbake.conf by redefining it in conf/local.conf.

During that process I noticed the "sumtool" utility which works on the jffs2 image, doing some bookkeeping which then does not have to be done on the target.

I unserstand, this can speed up loading significantly. Any reason not using this in OE?

Last time I looked at this, the reason was that you had to re-jigger the IMAGE_CMD a bit and you also have to take care as not all of the options are the same between mkfs.jffs2 and sumtool.  At least the first part might be easier with oe-core and the reworked image class. The latter part is just annoying.

--
Tom

Quoted 7 lines
Quoted 1 line

FWIW we are defining our jffs2-summary in

http://cgit.openembedded.org/meta-handheld/tree/conf/machine/include/zaurus.inc

This works beautifully in oe-dev but not using oe-core for it sets IMAGE_CMD_jffs2 = and this can  not be overriden
We would just need a weak assignment in image_types.bbclass or maybe a new image type like IMAGE_CMD_jffs2-summary and related commands.

It's been a while since I peeked at this, but there's never a reason not to sumtool as at worst case the first kernel mount will decide it needs to do this work again anyhow if something was somehow wrong.

Signature · 1 line
Tom
#4 lore raw
In reply to Andrea Adami
Quoted 25 lines · Andrea Adami
Quoted 23 lines · Tom Rini
Quoted 11 lines · Ulf Samuelsson

Trying to solve another problem I came up with changing IMAGE_CMD_jffs2 defined in conf/bitbake.conf by redefining it in conf/local.conf.

During that process I noticed the "sumtool" utility which works on the jffs2 image, doing some bookkeeping which then does not have to be done on the target.

I unserstand, this can speed up loading significantly. Any reason not using this in OE?

Last time I looked at this, the reason was that you had to re-jigger the IMAGE_CMD a bit and you also have to take care as not all of the options are the same between mkfs.jffs2 and sumtool.  At least the first part might be easier with oe-core and the reworked image class. The latter part is just annoying.

--
Tom

Quoted 8 lines
Quoted 1 line

FWIW we are defining our jffs2-summary in

http://cgit.openembedded.org/meta-handheld/tree/conf/machine/include/zaurus.inc

This works beautifully in oe-dev but not using oe-core for it sets IMAGE_CMD_jffs2 = and this can  not be overriden
We would just need a weak assignment in image_types.bbclass or maybe a new image type like IMAGE_CMD_jffs2-summary and related commands.

I would say port patches to oe-core for it.

Quoted 8 lines

Regards

Andrea
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

#5 lore raw
Quoted 29 lines · Khem Raj
Quoted 28 lines · Andrea Adami
Quoted 20 lines · Tom Rini
Quoted 11 lines · Ulf Samuelsson

Trying to solve another problem I came up with changing IMAGE_CMD_jffs2 defined in conf/bitbake.conf by redefining it in conf/local.conf.

During that process I noticed the "sumtool" utility which works on the jffs2 image, doing some bookkeeping which then does not have to be done on the target.

I unserstand, this can speed up loading significantly. Any reason not using this in OE?

Last time I looked at this, the reason was that you had to re-jigger the IMAGE_CMD a bit and you also have to take care as not all of the options are the same between mkfs.jffs2 and sumtool.  At least the first part might be easier with oe-core and the reworked image class. The latter part is just annoying.

Quoted 4 lines

--
Tom

FWIW we are defining our jffs2-summary in

http://cgit.openembedded.org/meta-handheld/tree/conf/machine/include/zaurus.inc

Quoted 7 lines
Quoted 5 lines

This works beautifully in oe-dev but not using oe-core for it sets IMAGE_CMD_jffs2 = and this can  not be overriden
We would just need a weak assignment in image_types.bbclass or maybe a new image type like IMAGE_CMD_jffs2-summary and related commands.

I would say port patches to oe-core for it.

Done, patch sent to oe-core

Regards
Andrea

Quoted 10 lines
Quoted 5 lines

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel