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 v2 1/2] package/zynqmp-firmware: new package
Date: Fri, 7 Apr 2023 17:16:48 +0200 [thread overview]
Message-ID: <20230407171648.6fca3a4d@booty> (raw)
In-Reply-To: <20230327170604.22854-1-neal.frager@amd.com>
Hi Neal,
On Mon, 27 Mar 2023 18:06:03 +0100
Neal Frager <neal.frager@amd.com> wrote:
> This patch adds a new package to buildroot for building the zynqmp pmufw
> with the requirement that the user must provide an external microblaze
> toolchain.
>
> The below example config options can be used to build the pmufw.elf v2022.2
> using the Xilinx toolchain.
>
> BR2_PACKAGE_ZYNQMP_FIRMWARE=y
> BR2_PACKAGE_ZYNQMP_FIRMWARE_VERSION="v2022.2"
> BR2_PACKAGE_ZYNQMP_FIRMWARE_EXTERNAL_TOOLCHAIN_PATH="/opt/Xilinx/Vitis/2022.2/gnu/microblaze/lin"
> BR2_PACKAGE_ZYNQMP_FIRMWARE_EXTERNAL_TOOLCHAIN_PREFIX="microblaze-xilinx-elf-"
>
> Signed-off-by: Neal Frager <neal.frager@amd.com>
These two patches look good, and I appreciate a lot your effort, however
I'm not sure it's a good idea to support both an external and a
generated toolchain. It makes things more complicated on the Buildroot
side and I'm not aware of any actual benefits.
Moreover if we take these patches now we would to some extent encourage
users to use an external Microblaze toolchain, possibly reducing usage
of the generated one for initial users. And I guess we would stick to
the external toolchain as a default for the future because it's what
was there initially.
So I would prefer waiting until we have a working
Buildroot-generated toolchain and initially support only that. Support
for an external toolchain can be added easily later, in case the
generated one were not suitable for good reasons.
Do you have any updates on your work to generate a minimal Microblaze
toolchain within Buildroot? Should you be facing any issues, remember
the Buildroot community can be very helpful!
Best regards,
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
next prev parent reply other threads:[~2023-04-07 15:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 17:06 [Buildroot] [PATCH v2 1/2] package/zynqmp-firmware: new package Neal Frager via buildroot
2023-03-27 17:06 ` [Buildroot] [PATCH v2 2/2] boot/uboot.mk: new zynqmp pmufw build option Neal Frager via buildroot
2023-08-22 22:02 ` Thomas Petazzoni via buildroot
2023-04-07 15:16 ` Luca Ceresoli via buildroot [this message]
2023-08-22 22:01 ` [Buildroot] [PATCH v2 1/2] package/zynqmp-firmware: new package Thomas Petazzoni via buildroot
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=20230407171648.6fca3a4d@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