From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: Neal Frager <neal.frager@amd.com>
Cc: ibai.erkiaga-elorza@amd.com, michal.simek@amd.com,
thomas.petazzoni@bootlin.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 1/1] boot/versal-firmware: use microblaze toolchain
Date: Fri, 22 Sep 2023 16:32:40 +0200 [thread overview]
Message-ID: <20230922163240.6e3c1dcd@booty> (raw)
In-Reply-To: <20230907105621.205396-1-neal.frager@amd.com>
Hi Neal,
On Thu, 7 Sep 2023 11:56:21 +0100
Neal Frager <neal.frager@amd.com> wrote:
> This patch moves the versal-firmware package from the package directory to the
> boot directory because it is actually boot firmware.
This should be a separate patch. Not only because it is an indipentent
change, but also because the diff is not very useful with the old and
new code spread apart as one set of deleted files and a set of new
files.
> In addition, this patch uses the microblaze bare-metal toolchain from the
> patch set below in order to now build the plm and psmfw applications.
>
> Microblaze bare-metal toolchain patch set:
> https://patchwork.ozlabs.org/project/buildroot/list/?series=371570
Of course that needs to be applied first. I don't see a problem with
this patch being around before that, however it probably won't attract
much attention at least until the bare-metal toolchain approach is
accepted (not necessarily the actual patches).
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-09-22 14:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 10:56 [Buildroot] [PATCH v1 1/1] boot/versal-firmware: use microblaze toolchain Neal Frager via buildroot
2023-09-22 14:32 ` Luca Ceresoli via buildroot [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=20230922163240.6e3c1dcd@booty \
--to=buildroot@buildroot.org \
--cc=ibai.erkiaga-elorza@amd.com \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=thomas.petazzoni@bootlin.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