From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: "Frager, Neal" <neal.frager@amd.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>,
"Chaplin, Kris" <Kris.Chaplin@amd.com>,
"wesley@sonifex.co.uk" <wesley@sonifex.co.uk>,
"giulio.benetti@benettiengineering.com"
<giulio.benetti@benettiengineering.com>,
"Simek, Michal" <michal.simek@amd.com>,
"yann.morin.1998@free.fr" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH v1 1/2] configs/zynqmp_zcu102_defconfig: fix pmufw sw reset
Date: Tue, 18 Oct 2022 09:04:42 +0200 [thread overview]
Message-ID: <20221018090442.2cb7fda8@booty> (raw)
In-Reply-To: <CH2PR12MB5004B9D704E2468C787578ACF0299@CH2PR12MB5004.namprd12.prod.outlook.com>
Hi Neal, Michal,
On Mon, 17 Oct 2022 14:15:16 +0000
"Frager, Neal" <neal.frager@amd.com> wrote:
> Hi Luca,
>
> > Why are these binaries board-specific? I thought this used to be only
> > needed for the "community workflow" before U-Boot SPL was able to load
> > a pmufw cfg object.
>
> Good question! I had a feeling you would ask this.
;-)
> In the case of the zcu102, zcu104 and zcu106, the pmufw binary is not board specific. The same pmufw binary will work on all 3 boards and even custom hardware, if a developer wants to use it unchanged.
OK, I see. (@Michal) I compared the zcu102 and zcu106 binaries and they
are different, thus I wondered.
> But since the pmu reset gpios are customisable among other things, the kria kv260 actually uses a different pmufw configuration. And developers may wish to modify the pmufw for their target as well.
>
> Since the Xilinx firmware repository is created using the petalinux prebuilt images for each target hardware, we chose to have a pmufw.elf in each board directory to match what comes from the petalinux builds.
Sure, knowing the process clarifies the reason for having different
places for firmwares that are equivalent.
> That said, since the Xilinx repository has a pmufw.elf in each individual board directory, I thought it would be cleaner for buildroot to use the pmufw.elf for each specific target. Even if the zcu102 and zcu106 pmufw.elf binaries are really interchangeable.
Sure it is.
Thank you both for the clarifications!
Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
--
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:[~2022-10-18 7:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 7:10 [Buildroot] [PATCH v1 1/2] configs/zynqmp_zcu102_defconfig: fix pmufw sw reset Neal Frager via buildroot
2022-10-17 7:10 ` [Buildroot] [PATCH v1 2/2] configs/zynqmp_zcu106_defconfig: " Neal Frager via buildroot
2022-10-18 7:05 ` Luca Ceresoli via buildroot
2022-10-18 19:42 ` Peter Korsgaard
2022-11-02 22:57 ` Peter Korsgaard
2022-10-17 13:58 ` [Buildroot] [PATCH v1 1/2] configs/zynqmp_zcu102_defconfig: " Luca Ceresoli via buildroot
2022-10-17 14:15 ` Frager, Neal via buildroot
2022-10-18 7:04 ` Luca Ceresoli via buildroot [this message]
2022-10-18 19:41 ` Peter Korsgaard
2022-11-02 22:57 ` Peter Korsgaard
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=20221018090442.2cb7fda8@booty \
--to=buildroot@buildroot.org \
--cc=Kris.Chaplin@amd.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=wesley@sonifex.co.uk \
--cc=yann.morin.1998@free.fr \
/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