From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: "Frager, Neal" <neal.frager@amd.com>
Cc: Brandon Maier <brandon.maier@collins.com>,
"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] boot/uboot/uboot.mk: support binary pm_cfg_obj
Date: Tue, 13 Dec 2022 09:23:25 +0100 [thread overview]
Message-ID: <20221213092325.15176bbb@booty> (raw)
In-Reply-To: <CH2PR12MB500436FEFB9A1E70F891A504F0E29@CH2PR12MB5004.namprd12.prod.outlook.com>
Hi Neal,
On Mon, 12 Dec 2022 12:52:37 +0000
"Frager, Neal" <neal.frager@amd.com> wrote:
> Hi Luca,
>
> > BR2_TARGET_UBOOT_ZYNQMP_PM_CFG only works with C files, as it always
> > tries to process them through tools/zynqmp_pm_cfg_obj_convert.py.
> > Rework the logic so if the pm_cfg_obj isn't a C file, it is provided
> > directly to U-Boot.
>
> > Can you describe a use case where this would be useful? While I intuitively understand there _might_ be some, I cannot find any good example based on my experience.
>
> > Building the pm_cfg_obj from source code is very easily done by Buildroot, unlike building the PMUFW. Additionally one PMUFW binary can be used on multiple zynqmp hardware, while the cfg obj is very likely to change across different projects, and a somewhat readable text file is way more understandable than a binary blob.
>
> I believe Brandon should weigh in on this with his opinion as well. As I thought about it this morning, I just wanted to share my two cents for what they are worth.
>
> I agree with you that most users would want to build everything with buildroot, if they could. Right now, we support using pmufw binaries only because we do not have a solution for building the pmufw itself with buildroot.
> If users could build the pmufw itself with buildroot, I am sure most of them would.
>
> However, at the same time, does Brandon's patch really hurt anything? By allowing users to provide a pre-built pm_cfg_obj binary blob, it does not prevent users from still providing a c file.
> Basically, it allows for the capability of building the pm_cfg_obj.c file with Xilinx tools and just providing the binary blob for being included in the spl/boot.bin by buildroot without removing any capability.
>
> So from my view, this patch may not be critical, but it does not break anything either. I am ok with whatever you and Brandon decide about committing it.
I think any line of code that is not very useful (or not useful at all)
does hurt. People have to maintain it, code is less readable, etc.
--
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-12-13 8:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 19:40 [Buildroot] [PATCH 1/1] boot/uboot/uboot.mk: support binary pm_cfg_obj Brandon Maier via buildroot
2022-12-10 9:55 ` Frager, Neal via buildroot
2022-12-12 9:35 ` Luca Ceresoli via buildroot
2022-12-12 9:43 ` Frager, Neal via buildroot
2022-12-12 9:31 ` Luca Ceresoli via buildroot
2022-12-12 12:52 ` Frager, Neal via buildroot
2022-12-13 8:23 ` Luca Ceresoli via buildroot [this message]
2022-12-12 15:41 ` [Buildroot] [External] " Maier, Brandon L Collins via buildroot
2022-12-13 8:21 ` Luca Ceresoli via buildroot
2022-12-22 14:37 ` Frager, Neal via buildroot
2022-12-29 22:42 ` Luca Ceresoli 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=20221213092325.15176bbb@booty \
--to=buildroot@buildroot.org \
--cc=brandon.maier@collins.com \
--cc=luca.ceresoli@bootlin.com \
--cc=neal.frager@amd.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