public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: Re: [PATCH] u-boot-script: Adjust to new kernel filename
Date: Thu, 8 Apr 2021 08:29:27 +0200	[thread overview]
Message-ID: <dc454619-fe16-a838-37f0-ead2e262d7f0@siemens.com> (raw)
In-Reply-To: <8b2b154f-e34f-a293-cbe8-d5433669acfb@siemens.com>

On 27.03.21 09:28, [ext] Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> Fixes: d6954739fe43 ("linux-custom: Fix decompressed kernel name for arm64")
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> 
> Seems we are lacking tests that do complete boot sequences, at least for 
> arm64 boards.
> 
>  meta/recipes-bsp/u-boot-script/files/update-u-boot-script | 6 +-----
>  1 file changed, 1 insertion(+), 5 deletions(-)
> 
> diff --git a/meta/recipes-bsp/u-boot-script/files/update-u-boot-script b/meta/recipes-bsp/u-boot-script/files/update-u-boot-script
> index 39989a89..40d31081 100755
> --- a/meta/recipes-bsp/u-boot-script/files/update-u-boot-script
> +++ b/meta/recipes-bsp/u-boot-script/files/update-u-boot-script
> @@ -18,11 +18,7 @@ BOOT_CMD=$(mktemp)
>  KERNEL_VERSION=$(linux-version list | linux-version sort --reverse | head -1)
>  
>  case $(uname -m) in
> -	aarch64)
> -		KERNEL_FILE="vmlinuz"
> -		BOOT="booti"
> -		;;
> -	mips|riscv64)
> +	aarch64|mips|riscv64)
>  		KERNEL_FILE="vmlinux"
>  		BOOT="booti"
>  		;;
> 

Ping. This is a critical regression fix affecting lots of targets.

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

  reply	other threads:[~2021-04-08  6:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-27  8:28 Jan Kiszka
2021-04-08  6:29 ` Jan Kiszka [this message]
2021-04-08  8:16   ` Anton Mikanovich

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=dc454619-fe16-a838-37f0-ead2e262d7f0@siemens.com \
    --to=jan.kiszka@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