From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: Karsten Merker <merker@debian.org>
Cc: Atish Patra <atish.patra@wdc.com>,
linux-kernel@vger.kernel.org, Tom Rini <trini@konsulko.com>,
Alexander Graf <agraf@suse.de>, Anup Patel <anup@brainfault.org>,
Bin Meng <bmeng.cn@gmail.com>,
Boris Brezillon <boris.brezillon@bootlin.com>,
Joe Hershberger <joe.hershberger@ni.com>,
Lukas Auer <lukas.auer@aisec.fraunhofer.de>,
Marek Vasut <marek.vasut@gmail.com>,
Michal Simek <michal.simek@xilinx.com>,
Rick Chen <rick@andestech.com>, Simon Glass <sjg@chromium.org>,
u-boot@lists.denx.de
Subject: Re: [U-Boot] [v4 PATCH] RISCV: image: Add booti support
Date: Mon, 6 May 2019 23:10:57 +0200 [thread overview]
Message-ID: <d1c63af6-e1e0-4ec3-e97a-4c3e9ec11623@gmx.de> (raw)
In-Reply-To: <20190506203956.ty6gkmhm4dlylld4@excalibur.cnev.de>
On 5/6/19 10:39 PM, Karsten Merker wrote:
> On Mon, May 06, 2019 at 10:06:39PM +0200, Heinrich Schuchardt wrote:
>> On 5/6/19 8:11 PM, Atish Patra wrote:
>>> This patch adds booti support for RISC-V Linux kernel. The existing
>>> bootm method will also continue to work as it is.
> [...]
>>> + "boot arm64/riscv Linux Image image from memory", booti_help_text
>>
>> %s/Image image/image/
>>
>> "arm64/riscv" is distracting. If I am on RISC-V I cannot boot an ARM64
>> image here. Remove the reference to the architecture, please.
>
> Hello,
>
> I'm not sure about the last point - ISTR (please correct me if my
> memory betrays me here) that an arm64 U-Boot can in principle be
> used to boot either an arm64 or an armv7 kernel, but the commands
> are different in those cases (booti for an arm64 "Image" format
> kernel and bootz for an armv7 "zImage" format kernel), so having
> the information which kernel format is supported by the
> respective commands appears useful to me. If the arm64 kernel
> image format would have a distinctive name (like "zImage" on
> armv7 or "bzImage" on x86) that would be less problematic, but
> with the confusion potential of "boot a Linux Image" (as in the
> arm64/riscv-specific "Image" format) vs "boot a Linux image" (as
> in generally some form of kernel image), I think explicitly
> mentioning the supported architectures makes sense.
In this case you have to ensure that only the *supported* architectures
are mentioned. RISC-V is not supported on ARM64.
Best regards
Heinrich
next prev parent reply other threads:[~2019-05-06 21:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 18:11 [U-Boot] [v4 PATCH] RISCV: image: Add booti support Atish Patra
2019-05-06 20:06 ` Heinrich Schuchardt
2019-05-06 20:39 ` Karsten Merker
2019-05-06 21:10 ` Heinrich Schuchardt [this message]
2019-05-06 21:27 ` Tom Rini
2019-05-07 0:50 ` Atish Patra
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=d1c63af6-e1e0-4ec3-e97a-4c3e9ec11623@gmx.de \
--to=xypron.glpk@gmx.de \
--cc=agraf@suse.de \
--cc=anup@brainfault.org \
--cc=atish.patra@wdc.com \
--cc=bmeng.cn@gmail.com \
--cc=boris.brezillon@bootlin.com \
--cc=joe.hershberger@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.auer@aisec.fraunhofer.de \
--cc=marek.vasut@gmail.com \
--cc=merker@debian.org \
--cc=michal.simek@xilinx.com \
--cc=rick@andestech.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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;
as well as URLs for NNTP newsgroup(s).