Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] image_types.bbclass: redefine EXTRA_IMAGECMD_jffs2 to leverage siteinfo
Date: Wed, 09 May 2012 16:27:54 -0700	[thread overview]
Message-ID: <4FAAFD7A.7060702@linux.intel.com> (raw)
In-Reply-To: <1336365869-12720-1-git-send-email-b28495@freescale.com>

On 05/06/2012 09:44 PM, b28495@freescale.com wrote:
> From: Ting Liu<b28495@freescale.com>
>
> Signed-off-by: Ting Liu<b28495@freescale.com>
> ---
>   meta/classes/image_types.bbclass |    7 ++++++-
>   1 files changed, 6 insertions(+), 1 deletions(-)
>
> diff --git a/meta/classes/image_types.bbclass b/meta/classes/image_types.bbclass
> index b590ae1..55f122e 100644
> --- a/meta/classes/image_types.bbclass
> +++ b/meta/classes/image_types.bbclass
> @@ -188,7 +188,12 @@ IMAGE_CMD_ubi () {
>   IMAGE_CMD_ubifs = "mkfs.ubifs -r ${IMAGE_ROOTFS} -o ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.ubifs ${MKUBIFS_ARGS}"
>
>   EXTRA_IMAGECMD = ""
> -EXTRA_IMAGECMD_jffs2 ?= "--pad --little-endian --eraseblock=0x40000"
> +
> +inherit siteinfo
> +JFFS2_ENDIANNESS ?= "${@base_conditional('SITEINFO_ENDIANNESS', 'le', '--little-endian', '--big-endian', d)}"
> +JFFS2_ERASEBLOCK ?= "0x40000"
> +EXTRA_IMAGECMD_jffs2 ?= "--pad ${JFFS2_ENDIANNESS} --eraseblock=${JFFS2_ERASEBLOCK} --no-cleanmarkers"
> +
>   # Change these if you want default genext2fs behavior (i.e. create minimal inode number)
>   EXTRA_IMAGECMD_ext2 ?= "-i 8192"
>   EXTRA_IMAGECMD_ext3 ?= "-i 8192"

Merged into OE-Core

Thanks
	Sau!



      reply	other threads:[~2012-05-09 23:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07  4:44 [PATCH] image_types.bbclass: redefine EXTRA_IMAGECMD_jffs2 to leverage siteinfo b28495
2012-05-09 23:27 ` Saul Wold [this message]

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=4FAAFD7A.7060702@linux.intel.com \
    --to=sgw@linux.intel.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