Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: tf+lists.yocto@r-finger.com
Cc: Tomas Frydrych <tomas@sleepfive.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] image_types: fix default location of kernel when generating elf images
Date: Wed, 01 May 2013 13:29:56 -0700	[thread overview]
Message-ID: <51817B44.30702@linux.intel.com> (raw)
In-Reply-To: <1367439862-4658-1-git-send-email-tf+lists.yocto@r-finger.com>



On 05/01/2013 01:24 PM, tf+lists.yocto@r-finger.com wrote:
> From: Tomas Frydrych <tomas@sleepfive.com>
> 
> The kernel is now located in DEPLOY_DIR_IMAGE rather than sysroot.
> 
> Signed-off-by: Tomas Frydrych <tomas@sleepfive.com>
> ---
>  meta/classes/image_types.bbclass |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/classes/image_types.bbclass b/meta/classes/image_types.bbclass
> index 98d31f5..0e1ad3a 100644
> --- a/meta/classes/image_types.bbclass
> +++ b/meta/classes/image_types.bbclass
> @@ -185,7 +185,7 @@ IMAGE_CMD_cpio () {
>  	cd ${IMAGE_ROOTFS} && (find . | cpio -o -H newc >${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.cpio)
>  }
>  
> -ELF_KERNEL ?= "${STAGING_DIR_HOST}/kernel/${KERNEL_IMAGETYPE}"
> +ELF_KERNEL ?= "${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${MACHINE}.bin"


Looks correct, how did this fail before? What was the symptom?


>  ELF_APPEND ?= "ramdisk_size=32768 root=/dev/ram0 rw console="
>  
>  IMAGE_CMD_elf () {
> 

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel



  reply	other threads:[~2013-05-01 20:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-01 20:24 [PATCH] image_types: fix default location of kernel when generating elf images tf+lists.yocto
2013-05-01 20:29 ` Darren Hart [this message]
2013-05-01 20:51   ` Tomas Frydrych
2013-05-03 11:50     ` Richard Purdie
2013-05-03 12:09       ` Tomas Frydrych
2013-05-03 11:39 ` [Patch v2] " tf+lists.yocto
2013-05-03 12:18 ` [Patch v3] " Tomas Frydrych

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=51817B44.30702@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=tf+lists.yocto@r-finger.com \
    --cc=tomas@sleepfive.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox