From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Neal Frager via buildroot <buildroot@buildroot.org>
Cc: michal.simek@amd.com, ibai.erkiaga-elorza@amd.com,
luca.ceresoli@bootlin.com, Neal Frager <neal.frager@amd.com>
Subject: Re: [Buildroot] [PATCH v1 2/2] boot/uboot.mk: new BR2_TARGET_UBOOT_NEEDS_ZYNQMP_FIRMWARE
Date: Sun, 26 Mar 2023 22:09:08 +0200 [thread overview]
Message-ID: <20230326220908.623ba0b5@windsurf> (raw)
In-Reply-To: <20230326140949.11262-2-neal.frager@amd.com>
On Sun, 26 Mar 2023 15:09:49 +0100
Neal Frager via buildroot <buildroot@buildroot.org> wrote:
> The new BR2_TARGET_UBOOT_NEEDS_ZYNQMP_FIRMWARE option will enable u-boot to
> use the zynqmp-firmware package for building a pmufw.elf that gets included in
> the generated boot.bin.
>
> Signed-off-by: Neal Frager <neal.frager@amd.com>
> ---
> boot/uboot/Config.in | 11 +++++++++++
> boot/uboot/uboot.mk | 5 +++++
> 2 files changed, 16 insertions(+)
>
> diff --git a/boot/uboot/Config.in b/boot/uboot/Config.in
> index f5c20f5168..116df71ea3 100644
> --- a/boot/uboot/Config.in
> +++ b/boot/uboot/Config.in
> @@ -476,6 +476,17 @@ config BR2_TARGET_UBOOT_ZYNQMP
>
> if BR2_TARGET_UBOOT_ZYNQMP
>
> +config BR2_TARGET_UBOOT_NEEDS_ZYNQMP_FIRMWARE
> + bool "U-Boot needs zynqmp-firmware"
I think this naming is confusing. If I understand correctly, U-Boot now
offers two possibilities:
(1) Using a prebuild PMU firmware (this is what is currently possible
in Buildroot)
(2) Building the PMU firmware from source (which is what your patch is
adding)
I believe the proposed option naming/organization doesn't make this
very clear. I don't have a super clear idea of what it should look
like. Perhaps we should have a choice...endchoice that makes it 100%
clear that the user can chose between using a pre-built vs. building
one from source?
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:[~2023-03-26 20:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 14:09 [Buildroot] [PATCH v1 1/2] package/zynqmp-firmware: new package Neal Frager via buildroot
2023-03-26 14:09 ` [Buildroot] [PATCH v1 2/2] boot/uboot.mk: new BR2_TARGET_UBOOT_NEEDS_ZYNQMP_FIRMWARE Neal Frager via buildroot
2023-03-26 20:09 ` Thomas Petazzoni via buildroot [this message]
2023-03-27 11:08 ` Frager, Neal via buildroot
2023-03-26 20:05 ` [Buildroot] [PATCH v1 1/2] package/zynqmp-firmware: new package Thomas Petazzoni via buildroot
2023-03-27 5:45 ` Frager, Neal via buildroot
2023-03-27 7:42 ` Thomas Petazzoni via buildroot
2023-03-27 9:00 ` Frager, Neal via buildroot
2023-03-27 13:11 ` Luca Ceresoli via buildroot
2023-03-27 13:22 ` Frager, Neal via buildroot
2023-03-27 12:21 ` Frager, Neal via buildroot
[not found] ` <MN0PR12MB60041E824606160DF5277406A08B9@MN0PR12MB6004.namprd12.prod.outlook.com>
2023-03-27 12:47 ` Frager, Neal via buildroot
2023-03-27 12:57 ` Thomas Petazzoni via buildroot
2023-03-27 13:03 ` 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=20230326220908.623ba0b5@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