From: Henning Schild <henning.schild@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v2] linux-custom: Fix decompressed kernel name for arm64
Date: Thu, 2 Sep 2021 17:05:43 +0200 [thread overview]
Message-ID: <20210902170543.38a9e62a@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20210125143128.88428-1-amikan@ilbers.de>
Turns out this is wrong. debian itself would use vmlinuz for arm64 and
in fact also does that i.e in "linux-update-symlinks" which takes its
"stem" from
https://salsa.debian.org/kernel-team/linux-base/-/blob/master/lib/DebianLinux.pm#L79
And on the other side of the story ... debians kernel build sets the
arm64 stem
https://salsa.debian.org/kernel-team/linux/-/blob/master/debian/config/arm64/defines#L14
I will send patches.
Henning
Am Mon, 25 Jan 2021 17:31:28 +0300
schrieb Anton Mikanovich <amikan@ilbers.de>:
> We are performing gunzip from vmlinuz on arm64, so output should have
> correct naming.
>
> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
> ---
> Changes since v1:
> - Add RECIPE-API-CHANGELOG entry.
> ---
> RECIPE-API-CHANGELOG.md | 5 +++++
> meta/conf/bitbake.conf | 1 +
> meta/recipes-kernel/linux/files/debian/isar/install.tmpl | 6 +++---
> 3 files changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md
> index cc45f3f..bd8a204 100644
> --- a/RECIPE-API-CHANGELOG.md
> +++ b/RECIPE-API-CHANGELOG.md
> @@ -282,3 +282,8 @@ like /boot/efi to avoid such issues.
> ### Deprecate BUILD_DEPENDS in u-boot-custom.inc
>
> Use DEBIAN_BUILD_DEPENDS instead, to align with deb_debianize.
> +
> +### Change kernel image name for arm64
> +
> +Kernel image name for arm64 platforms is vmlinux now. Image format
> was +not changed (uncompressed executable) but now it is named
> correctly. diff --git a/meta/conf/bitbake.conf
> b/meta/conf/bitbake.conf index acce55d..9859456 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -61,6 +61,7 @@ CACHE = "${TMPDIR}/cache"
> KERNEL_FILE ?= "vmlinuz"
> KERNEL_FILE_mipsel ?= "vmlinux"
> KERNEL_FILE_riscv64 ?= "vmlinux"
> +KERNEL_FILE_arm64 ?= "vmlinux"
>
> OVERRIDES =
> "${DISTRO_ARCH}:${COMPAT_OVERRIDE}:${MACHINE}:${DISTRO}:forcevariable"
> FILESOVERRIDES = "${DISTRO_ARCH}:${MACHINE}" diff --git
> a/meta/recipes-kernel/linux/files/debian/isar/install.tmpl
> b/meta/recipes-kernel/linux/files/debian/isar/install.tmpl index
> 8eca4c7..69fb88d 100644 ---
> a/meta/recipes-kernel/linux/files/debian/isar/install.tmpl +++
> b/meta/recipes-kernel/linux/files/debian/isar/install.tmpl @@ -26,9
> +26,9 @@ do_install() { fi krel="$(${MAKE} O=${O} -s
> --no-print-directory kernelrelease)" case "${ARCH}" in
> - mips|powerpc|riscv) kimage_path="boot/vmlinux-${krel}" ;;
> - um) kimage_path="usr/bin/vmlinux-${krel}" ;;
> - *) kimage_path="boot/vmlinuz-${krel}" ;;
> + mips|powerpc|riscv|arm64) kimage_path="boot/vmlinux-${krel}"
> ;;
> + um)
> kimage_path="usr/bin/vmlinux-${krel}" ;;
> + *) kimage_path="boot/vmlinuz-${krel}"
> ;; esac
>
> print_settings
next prev parent reply other threads:[~2021-09-03 15:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 14:31 Anton Mikanovich
2021-02-10 9:19 ` Anton Mikanovich
2021-09-02 15:05 ` Henning Schild [this message]
2021-10-06 5:09 ` Srinuvasan A
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=20210902170543.38a9e62a@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=amikan@ilbers.de \
--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