From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] Add ubi volume image support, fix ubifs
Date: Wed, 11 Feb 2009 00:42:34 +0100 [thread overview]
Message-ID: <gmt3da$4r1$1@ger.gmane.org> (raw)
In-Reply-To: <20090210225940.GI11815@smtp.west.cox.net>
On 10-02-09 23:59, Tom Rini wrote:
> On Tue, Feb 10, 2009 at 11:43:07PM +0100, Koen Kooi wrote:
>> Op 10 feb 2009, om 21:48 heeft Tom Rini het volgende geschreven:
>>
>>> Hey all. I'd like to commit the following patch.
>> Looks ok, one minor featurerequest:
>>
>>
>>> +IMAGE_CMD_ubi = "echo \[ubifs\]> ubinize.cfg ; echo mode=ubi>>
>>> ubinize.cfg ; echo image=${DEPLOY_DIR_IMAGE}/$
>>> {IMAGE_NAME}.rootfs.ubifs>> ubinize.cfg ; echo vol_id=0>>
>>> ubinize.cfg ; echo vol_type=dynamic>> ubinize.cfg ; echo
>>> vol_name=rootfs>> ubinize.cfg ; echo vol_flags=autoresize>>
>>> ubinize.cfg;mkfs.ubifs -r ${IMAGE_ROOTFS} -o ${DEPLOY_DIR_IMAGE}/$
>>> {IMAGE_NAME}.rootfs.ubifs ${MKUBIFS_ARGS}&& ubinize -o $
>>> {DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.ubi ${UBINIZE_ARGS}
>>> ubinize.cfg"
>> echo vol_name=${MACHINE}-rootfs would be nice :)
>
> Really? iirc from the mounting commandline stuff that means you have to
> pass in machine-rootfs rather than just rootfs, ie
> root=ubi0:machine-rootfs not root=ubi0:rootfs
You'll have to update your bootloaders anyway, so cutting down on
'flashed wrong machine' errors is a big win :)
regards,
Koen
next prev parent reply other threads:[~2009-02-10 23:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 20:48 [RFC] Add ubi volume image support, fix ubifs Tom Rini
2009-02-10 22:43 ` Koen Kooi
2009-02-10 22:59 ` Tom Rini
2009-02-10 23:42 ` Koen Kooi [this message]
2009-02-11 0:27 ` Tom Rini
2009-02-11 8:09 ` Koen Kooi
2009-02-11 16:18 ` John Willis
2009-02-12 22:45 ` Koen Kooi
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='gmt3da$4r1$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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