Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: Robert Yang <liezhi.yang@windriver.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/4] image_types.bbclass: fix ubi ubifs and multiubi
Date: Fri, 8 Apr 2016 11:09:23 +0200	[thread overview]
Message-ID: <57077543.1010708@denx.de> (raw)
In-Reply-To: <088e89118818dccb4f19c73795d7ae2a724e6473.1460099653.git.liezhi.yang@windriver.com>

Hi Robert,

On 08/04/2016 09:15, Robert Yang wrote:
> Fixed when do_image_ubi:
> | DEBUG: Executing shell function do_image_ubifs
> | Error: min. I/O unit was not specified (use -h for help)
> | WARNING: exit code 255 from a shell command.
> 
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> ---
>  meta/classes/image_types.bbclass | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/meta/classes/image_types.bbclass b/meta/classes/image_types.bbclass
> index 3f97ddd..caa4dbb 100644
> --- a/meta/classes/image_types.bbclass
> +++ b/meta/classes/image_types.bbclass
> @@ -120,6 +120,9 @@ IMAGE_CMD_elf () {
>  }
>  IMAGE_TYPEDEP_elf = "cpio.gz"
>  
> +MKUBIFS_ARGS ?= "-m 1KiB -e 128KiB -c $ROOTFS_SIZE"
> +UBINIZE_ARGS ?= "-m 1KiB -p 128KiB"
> +

These are machine specific and are generally set in the machine
configuration file. Default values you set here could be wrong in most
cases, depending on the NAND chip.

Is it not better to get the error ? Then I know that I forget to set the
two variables and I can easy fix it. If no error is raised, we get a
ubifs that never run on the machine and as rootfs is not mounted - and
finding the reason is much more difficult.

Best regards,
Stefano

-- 
=====================================================================
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================


  reply	other threads:[~2016-04-08  9:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-08  7:15 [PATCH 0/4] image_types.bbclass: fix btrfs, ubifs and elf Robert Yang
2016-04-08  7:15 ` [PATCH 1/4] image_types.bbclass: set nodesize for btrfs Robert Yang
2016-04-08  7:15 ` [PATCH 2/4] image_types.bbclass: fix ubi ubifs and multiubi Robert Yang
2016-04-08  9:09   ` Stefano Babic [this message]
2016-04-08  9:54     ` Anders Darander
2016-04-08 10:08       ` Robert Yang
2016-04-08  7:15 ` [PATCH 3/4] image_types.bbclass: fix elf Robert Yang
2016-04-08  7:15 ` [PATCH 4/4] image-vm.bbclass/image_types.bbclass: IMAGE_NAME -> IMAGE_LINK_NAME Robert Yang
2016-04-08 10:11 ` [PATCH 0/4] image_types.bbclass: fix btrfs, ubifs and elf Robert Yang

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=57077543.1010708@denx.de \
    --to=sbabic@denx.de \
    --cc=liezhi.yang@windriver.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