From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Frager, Neal" <neal.frager@amd.com>
Cc: "Simek, Michal" <michal.simek@amd.com>,
"Chaplin, Kris" <Kris.Chaplin@amd.com>,
"O'Neal, Terry" <terry.oneal@amd.com>,
"luca.ceresoli@bootlin.com" <luca.ceresoli@bootlin.com>,
Neal Frager via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v6 1/2] package/versal-firmware: new package
Date: Fri, 25 Nov 2022 12:33:44 +0100 [thread overview]
Message-ID: <20221125123344.045a4441@windsurf> (raw)
In-Reply-To: <9EE282D7-0646-421F-BF16-BD424E508ABE@amd.com>
Hello Neal,
On Fri, 25 Nov 2022 11:18:43 +0000
"Frager, Neal" <neal.frager@amd.com> wrote:
> Yes, it is the full source code, just like there is the full source
> code for the zynqmp pmufw. The problem is that all 3 of these
> applications are running on a microblaze.
>
> So to build them, we need to be able to work with two compilers. A
> microblaze compiler for all the firmware applications and an ARM
> compiler for the rest.
>
> Normally, it would be much better if we could build the pmufw for
> zynqmp and the plm and psmfw applications for versal. We have
> discussed this before, but do you have any new ideas for how we could
> configure buildroot to download and build two compilers for two
> different architectures?
Sure: we are already doing that for some ARM64 platforms that need to
build ARM32 firmware: this needs a different compiler.
It is for this reason that we have the package/arm-gnu-toolchain/
package, which downloads and installs a pre-compiled bare-metal ARM32
toolchain. Then this toolchain is for example used by
boot/arm-trusted-firmware/ in some situations:
ifeq ($(BR2_TARGET_ARM_TRUSTED_FIRMWARE_NEEDS_ARM32_TOOLCHAIN),y)
ARM_TRUSTED_FIRMWARE_DEPENDENCIES += host-arm-gnu-toolchain
endif
So if you have a Microblaze bare metal toolchain available somewhere,
we could create a package for it, and build the firmware from source.
Best regards,
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
next prev parent reply other threads:[~2022-11-25 11:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 10:21 [Buildroot] [PATCH v6 1/2] package/versal-firmware: new package Neal Frager via buildroot
2022-11-24 10:21 ` [Buildroot] [PATCH v6 2/2] configs/versal_vck190: new defconfig Neal Frager via buildroot
2022-11-24 21:15 ` [Buildroot] [PATCH v6 1/2] package/versal-firmware: new package Thomas Petazzoni via buildroot
2022-11-25 9:29 ` Frager, Neal via buildroot
2022-11-25 11:02 ` Thomas Petazzoni via buildroot
2022-11-25 11:18 ` Frager, Neal via buildroot
2022-11-25 11:33 ` Thomas Petazzoni via buildroot [this message]
2022-11-25 13:18 ` Frager, Neal via buildroot
2022-11-25 14:13 ` Thomas Petazzoni via buildroot
2022-11-25 14:14 ` Frager, Neal 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=20221125123344.045a4441@windsurf \
--to=buildroot@buildroot.org \
--cc=Kris.Chaplin@amd.com \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=terry.oneal@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.