Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Luca Ceresoli via buildroot <buildroot@buildroot.org>,
	Neal Frager <neal.frager@amd.com>
Cc: michal.simek@amd.com, Luca Ceresoli <luca.ceresoli@bootlin.com>,
	ibai.erkiaga-elorza@amd.com
Subject: Re: [Buildroot] [PATCH v2 1/2] package/zynqmp-firmware: new package
Date: Wed, 23 Aug 2023 00:01:16 +0200	[thread overview]
Message-ID: <20230823000116.5f8ec3c5@windsurf> (raw)
In-Reply-To: <20230407171648.6fca3a4d@booty>

On Fri, 7 Apr 2023 17:16:48 +0200
Luca Ceresoli via buildroot <buildroot@buildroot.org> wrote:

> 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!

I agree with Luca, but I would relax a bit the requirement and say I
would be fine with a pre-built external toolchain to be packaged, like
package/arm-gnu-toolchain/ does for a pre-built ARM32 bare-metal
toolchain.

I looked a bit for such a pre-built Microblaze toolchain, but all what
Xilinx provides is hidden inside multi-GB archives with zillions of
things, and these archives are themselves accessible with a proper
login on the Xilinx site.

So either Xilinx puts online a bare-metal toolchain that we can package
like package/arm-gnu-toolchain/, or we look at adding support for
building a bare-metal toolchain in Buildroot.

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-08-22 22:01 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 ` [Buildroot] [PATCH v2 1/2] package/zynqmp-firmware: new package Luca Ceresoli via buildroot
2023-08-22 22:01   ` Thomas Petazzoni 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=20230823000116.5f8ec3c5@windsurf \
    --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