From: Denys Dmytriyenko <denis@denix.org>
To: yin.thong.choong@intel.com
Cc: otc-pg-team@eclists.intel.com, paul.eggleton@intel.com,
saul.wold@intel.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] image_types.bbclass: Added default argument for ubi and ubifs image creation
Date: Wed, 14 Jun 2017 21:42:33 -0400 [thread overview]
Message-ID: <20170615014230.GF28053@denix.org> (raw)
In-Reply-To: <1497461477-151292-2-git-send-email-yin.thong.choong@intel.com>
On Wed, Jun 14, 2017 at 10:31:17AM -0700, yin.thong.choong@intel.com wrote:
> From: Choong YinThong <yin.thong.choong@intel.com>
>
> Added default argument for ubi and ubifs image creation.
> MKUBIFS_ARGS and UBINIZE_ARGS both argument still able to
> edit in local.conf
>
> [YOCTO #11589]
>
> Signed-off-by: Choong YinThong <yin.thong.choong@intel.com>
> ---
> meta/classes/image_types.bbclass | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/meta/classes/image_types.bbclass b/meta/classes/image_types.bbclass
> index 7749b00..815f1ea 100644
> --- a/meta/classes/image_types.bbclass
> +++ b/meta/classes/image_types.bbclass
> @@ -292,3 +292,12 @@ IMAGE_EXTENSION_live = "hddimg iso"
> # The IMAGE_TYPES_MASKED variable will be used to mask out from the IMAGE_FSTYPES,
> # images that will not be built at do_rootfs time: vmdk, vdi, qcow2, hdddirect, hddimg, iso, etc.
> IMAGE_TYPES_MASKED ?= ""
> +
> +# Default argument to create ubi and ubifs image with core-image-sato-sdk (http://www.linux-mtd.infradead.org/faq/ubifs.html)
> +# -m 2048: tells mkfs.ubifs that the minimum input/output unit size of the flash this UBIFS image is created for is 2048 bytes (NAND page in this case);
> +# -e 129024: logical eraseblock size of the UBI volume this image is created for;
> +# -c 8749: specifies maximum file-system size in logical eraseblocks; this means that it will be possible to use the resulting file-system on volumes up to this size (less or equivalent); so in this particular case, the resulting FS may be put on volumes up to about 251MiB (129024 multiplied by 2047); See this section for more details.
> +# -p 128KiB: tells ubinize that physical eraseblock size of the flash chip the UBI image is created for is 128KiB (128 * 1024 bytes);
> +# -s 512: tells ubinize that the flash supports sub-pages and sub-page size is 512 bytes; ubinize will take this into account and put the VID header to the same NAND page as the EC header.
> +MKUBIFS_ARGS = " -m 2048 -e 129024 -c 8749 "
> +UBINIZE_ARGS = " -p 128KiB -m 2048 -s 512 "
This will override machine-specific settings.
--
Denys
next prev parent reply other threads:[~2017-06-15 1:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 17:31 [PATCH] ubi and ubifs image compression failed yin.thong.choong
2017-06-14 17:31 ` [PATCH] image_types.bbclass: Added default argument for ubi and ubifs image creation yin.thong.choong
2017-06-15 1:42 ` Denys Dmytriyenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-14 23:04 [PATCH v2] ubi and ubifs image compression failed yin.thong.choong
2017-06-14 23:04 ` [PATCH] image_types.bbclass: Added default argument for ubi and ubifs image creation yin.thong.choong
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=20170615014230.GF28053@denix.org \
--to=denis@denix.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otc-pg-team@eclists.intel.com \
--cc=paul.eggleton@intel.com \
--cc=saul.wold@intel.com \
--cc=yin.thong.choong@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.