public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Cedric Hombourger <Cedric_Hombourger@mentor.com>
To: <isar-users@googlegroups.com>
Cc: Cedric Hombourger <Cedric_Hombourger@mentor.com>
Subject: [PATCH v2 1/9] image.bbclass: introduce KERNEL_FILE (defaults to vmlinuz)
Date: Tue, 11 Jun 2019 14:50:18 +0200	[thread overview]
Message-ID: <1560257426-225-2-git-send-email-Cedric_Hombourger@mentor.com> (raw)
In-Reply-To: <1560257426-225-1-git-send-email-Cedric_Hombourger@mentor.com>

Some Debian ports use a non-standard name for the symbolic link
to the Linux kernel: e.g. "vmlinux" for the mips port instead of
the usual "vmlinuz". The name of the symbolic link is needed for
Isar to copy the kernel image to tmp/deploy/images/<machine> (an
incorrect name causes the copy_boot_file task to fail).

Signed-off-by: Cedric Hombourger <Cedric_Hombourger@mentor.com>
---
 meta/classes/image.bbclass | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index 1950263..ec6bd39 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -13,7 +13,8 @@ IMAGE_INSTALL += "${@ ("linux-image-" + d.getVar("KERNEL_NAME", True)) if d.getV
 IMAGE_FULLNAME = "${PF}"
 
 # These variables are used by wic and start_vm
-KERNEL_IMAGE ?= "${PF}-vmlinuz"
+KERNEL_FILE  ?= "vmlinuz"
+KERNEL_IMAGE ?= "${PF}-${KERNEL_FILE}"
 INITRD_IMAGE ?= "${PF}-initrd.img"
 
 # Useful variables for imager implementations:
@@ -123,7 +124,7 @@ EOF
 
 do_copy_boot_files[dirs] = "${DEPLOY_DIR_IMAGE}"
 do_copy_boot_files() {
-    kernel="$(realpath -q '${IMAGE_ROOTFS}/vmlinuz')"
+    kernel="$(realpath -q '${IMAGE_ROOTFS}/${KERNEL_FILE}')"
     if [ -n "$kernel" ]; then
         cp -f "$kernel" '${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGE}'
     fi
-- 
2.11.0


  reply	other threads:[~2019-06-11 12:50 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11  5:38 [PATCH 0/7] Add mipsel architecture and QEMU machine Cedric Hombourger
2019-06-11  5:38 ` [PATCH 1/7] image.bbclass: introduce KERNEL_FILE (defaults to vmlinuz) Cedric Hombourger
2019-06-11  5:38 ` [PATCH 2/7] start_vm: append kernel arguments specified in QEMU_KARGS Cedric Hombourger
2019-06-11  5:38 ` [PATCH 3/7] recipes-devtools/*-apt: add support for the mipsel architecture Cedric Hombourger
2019-06-11  5:38 ` [PATCH 4/7] recipes-kernel/linux: " Cedric Hombourger
2019-06-11  5:38 ` [PATCH 5/7] start_vm: add mipsel to the list of supported architectures Cedric Hombourger
2019-06-11  5:38 ` [PATCH 6/7] meta-isar: add the qemumipsel machine Cedric Hombourger
2019-06-11  5:38 ` [PATCH 7/7] ci_build: add qemumipsel-stretch to build targets Cedric Hombourger
2019-06-11  8:42   ` Henning Schild
2019-06-11  8:44     ` Hombourger, Cedric
2019-06-11 11:07       ` Henning Schild
2019-06-11 12:50         ` [PATCH v2 0/9] Add mipsel architecture and QEMU machine Cedric Hombourger
2019-06-11 12:50           ` Cedric Hombourger [this message]
2019-06-11 12:50           ` [PATCH v2 2/9] start_vm: append kernel arguments specified in QEMU_KARGS Cedric Hombourger
2019-06-11 12:50           ` [PATCH v2 3/9] recipes-devtools/*-apt: add support for the mipsel architecture Cedric Hombourger
2019-06-11 12:50           ` [PATCH v2 4/9] recipes-kernel/linux: " Cedric Hombourger
2019-06-11 12:56             ` [PATCH v2 5/9] start_vm: add mipsel to the list of supported architectures Cedric Hombourger
2019-06-11 12:56               ` [PATCH v2 6/9] meta-isar: add the qemumipsel machine Cedric Hombourger
2019-06-11 12:56               ` [PATCH v2 7/9] ci_build: add qemumipsel-stretch to build targets Cedric Hombourger
2019-06-11 12:56               ` [PATCH v2 8/9] meta-isar: add qemumipsel-buster configuration Cedric Hombourger
2019-06-11 12:56               ` [PATCH v2 9/9] ci_build: add qemumipsel-buster configuration to build targets Cedric Hombourger
2019-06-11 12:59           ` [PATCH v2 0/9] Add mipsel architecture and QEMU machine chombourger
2019-06-12  9:30             ` Claudius Heine
2019-06-12  9:44               ` chombourger
2019-06-12 11:21                 ` Baurzhan Ismagulov
2019-06-12 11:27                 ` Claudius Heine
2019-06-12 17:23           ` Baurzhan Ismagulov
2019-06-12 17:43             ` chombourger
2019-06-11  7:36 ` [PATCH 0/7] " Claudius Heine

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=1560257426-225-2-git-send-email-Cedric_Hombourger@mentor.com \
    --to=cedric_hombourger@mentor.com \
    --cc=isar-users@googlegroups.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