From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH] linux-custom: Fix decompressed kernel name for arm64
Date: Mon, 25 Jan 2021 14:11:48 +0100 [thread overview]
Message-ID: <5bf5becc-0742-bc00-335e-d606dbb3077a@siemens.com> (raw)
In-Reply-To: <10725c2e-109e-cb42-fcf6-c9141ef2599d@ilbers.de>
On 25.01.21 13:51, Anton Mikanovich wrote:
> 25.01.2021 15:32, Jan Kiszka wrote:
>> On 22.01.21 18:13, Anton Mikanovich wrote:
>>> We are performing gunzip from vmlinuz on arm64, so output should have
>>> correct naming.
>>>
>> What's the practical impact of this change? How did you notice it? Can
>> anything break that expected the old incorrect name?
>>
>> Jan
>
> I've noticed that when building custom kernel for imx8 (which is arm64)
> on one of the private projects. Naming decompressed image as compressed
> one cause bootloader configuring issues and general misunderstanding.
> Moreover, the same logic is already fixed for riscv, so arm64 also
> should work in the same way.
> All additional logic assuming incorrect name should be fixed of course.
>
We have tons of arm64 systems out there, that's why I'm asking
cautiously. If you can't specify the impact, whether if it requires a
RECIPE-API-CHANGELOG entry e.g., I guess we need to test it...
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2021-01-25 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 17:13 Anton Mikanovich
2021-01-25 12:32 ` Jan Kiszka
2021-01-25 12:51 ` Anton Mikanovich
2021-01-25 13:11 ` Jan Kiszka [this message]
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=5bf5becc-0742-bc00-335e-d606dbb3077a@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