From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2 v2] image_types: Add elf image type
Date: Fri, 29 Jun 2012 10:45:28 -0700 [thread overview]
Message-ID: <4FEDE9B8.8010605@linux.intel.com> (raw)
In-Reply-To: <1340984497-32423-1-git-send-email-ray.danks@se-eng.com>
On 06/29/2012 08:41 AM, Raymond Danks wrote:
> On x86, an ELF image file may be stored as a coreboot payload.
> The image file is constructed, using the mkelfimage utility,
> from a kernel and an initrd.
>
> Signed-off-by: Raymond Danks <ray.danks@se-eng.com>
> ---
> This was originally submitted to the openembedded project:
> http://patches.openembedded.org/patch/7689/
>
> v2:
> Include KERNEL_IMAGETYPE for location of ELF_KERNEL
>
> meta/classes/image_types.bbclass | 18 +++++++++++++++++-
> 1 files changed, 17 insertions(+), 1 deletions(-)
>
> diff --git a/meta/classes/image_types.bbclass b/meta/classes/image_types.bbclass
> index 55f122e..12419f4 100644
> --- a/meta/classes/image_types.bbclass
> +++ b/meta/classes/image_types.bbclass
> @@ -7,6 +7,12 @@ def get_imagecmds(d):
> ctypes = d.getVar('COMPRESSIONTYPES', True).split()
> cimages = {}
>
> + if "elf" in alltypes:
> + alltypes.remove("elf")
> + if "cpio.gz" not in alltypes:
> + alltypes.append("cpio.gz")
> + alltypes.append("elf")
> +
> # Filter out all the compressed images from types
> for type in alltypes:
> basetype = None
> @@ -173,6 +179,14 @@ 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}
This should be ${STAGING_KERNEL_DIR} I believe. I have a patch series
under review currently which would break the above as it is now in
/usr/src/kernel-headers
Note that you could also collect this from the DEPLOY_DIR_IMAGE, which
is probably more appropriate for assembling images
Thanks,
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-06-29 17:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 20:22 [PATCH 1/2] image_types: Add elf image type Raymond Danks
2012-06-22 20:22 ` [PATCH 2/2] mkelfimage: Add stable git build (initial recipe) Raymond Danks
2012-06-29 12:19 ` Richard Purdie
2012-06-29 15:32 ` Raymond Danks
2012-06-29 15:41 ` [PATCH 1/2 v2] image_types: Add elf image type Raymond Danks
2012-06-29 17:45 ` Darren Hart [this message]
2012-06-29 20:01 ` Raymond Danks
2012-06-29 15:41 ` [PATCH 2/2 v2] mkelfimage: Add stable git build (initial recipe) Raymond Danks
2012-06-29 17:47 ` Darren Hart
2012-06-29 20:03 ` Raymond Danks
2012-06-29 20:19 ` [PATCH 1/2 v3] image_types: Add elf image type Raymond Danks
2012-06-30 13:38 ` Darren Hart
2012-07-02 4:22 ` Saul Wold
2012-07-02 15:05 ` Raymond Danks
2012-07-02 16:51 ` Saul Wold
2012-07-02 19:00 ` Raymond Danks
2012-07-02 20:51 ` [PATCH 1/2 v4] " Raymond Danks
2012-07-05 17:35 ` Saul Wold
2012-06-29 20:30 ` [PATCH 2/2 v3] mkelfimage: Add stable git build (initial recipe) Raymond Danks
2012-07-08 21:34 ` [PATCH 2/2] " Saul Wold
2012-07-09 19:20 ` Raymond Danks
2012-06-25 16:58 ` [PATCH 1/2] image_types: Add elf image type Darren Hart
2012-06-27 20:34 ` Raymond Danks
2012-06-27 20:43 ` Raymond Danks
2012-06-27 21:32 ` Darren Hart
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=4FEDE9B8.8010605@linux.intel.com \
--to=dvhart@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