From: Denis Carikli <denis@eukrea.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/2] bitbake.conf: fix ubi images creation
Date: Fri, 2 Sep 2011 15:31:07 +0200 [thread overview]
Message-ID: <1314970267-20365-2-git-send-email-denis@eukrea.com> (raw)
In-Reply-To: <1314970267-20365-1-git-send-email-denis@eukrea.com>
Without that commit ubinize.cfg lack a volume name value,
and the related ubinize.cfg line looks like that:
vol_name=
which result in a broken ubi image,which after beeing flashed produce
the following error:
UBI error: vtbl_check: volume table check failed: record 0, error 11
wich result in a kernel panic because the rootfs can't be mounted.
Signed-off-by: Denis Carikli <denis@eukrea.com>
---
meta/conf/bitbake.conf | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index a68be07..14ee90c 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -382,6 +382,8 @@ IMAGE_BASENAME = "${PN}"
IMAGE_NAME = "${IMAGE_BASENAME}-${MACHINE}-${DATETIME}"
IMAGE_LINK_NAME = "${IMAGE_BASENAME}-${MACHINE}"
+UBI_VOLNAME ?= "${MACHINE}-rootfs"
+
# This option allows for a percentage overage of the actual image size rather than a
# fixed extra space, this is space needed for initial startup and basic operations.
IMAGE_OVERHEAD_FACTOR ?= 1.3
--
1.7.4.1
next prev parent reply other threads:[~2011-09-02 16:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 13:31 [PATCH 1/2] mtd-utils: update to version to 1.4.6 Denis Carikli
2011-09-02 13:31 ` Denis Carikli [this message]
2011-09-02 16:09 ` [RESEND] bitbake.conf: fix ubi images creation Denis Carikli
2011-09-05 7:05 ` Anders Darander
2011-09-05 7:09 ` Martin Jansa
2011-09-05 7:33 ` James Limbouris
2011-09-05 19:37 ` Richard Purdie
2011-09-02 13:38 ` [PATCH v2] mtd-utils: update to version to 1.4.6 Denis Carikli
2011-09-02 13:45 ` Denis Carikli
2011-09-02 14:07 ` [PATCH v3] " Denis Carikli
2011-09-06 7:12 ` [PATCH v4] " Denis Carikli
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=1314970267-20365-2-git-send-email-denis@eukrea.com \
--to=denis@eukrea.com \
--cc=openembedded-core@lists.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