From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Frager, Neal" <neal.frager@amd.com>
Cc: "Simek, Michal" <michal.simek@amd.com>,
"Erkiaga Elorza, Ibai" <ibai.erkiaga-elorza@amd.com>,
"luca.ceresoli@bootlin.com" <luca.ceresoli@bootlin.com>,
Neal Frager via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v1 1/2] package/zynqmp-firmware: new package
Date: Mon, 27 Mar 2023 09:42:22 +0200 [thread overview]
Message-ID: <20230327094222.3b11e289@windsurf> (raw)
In-Reply-To: <B1C2F9E6-C87B-4B1A-A6F9-9A312663D946@amd.com>
On Mon, 27 Mar 2023 05:45:45 +0000
"Frager, Neal" <neal.frager@amd.com> wrote:
> I would not say this is the conclusion of our discussion, but rather
> a next step. Once we have a microblaze compiler package, we can
> update the zynqmp-firmware package to use the included compiler by
> default or allow users to select an external one, in case they prefer
> to use the Xilinx distributed compiler.
Hm, OK. I don't know if we want to have both options of using a
compiler provided by Buildroot, or a compiler installed separately. No
strong feeling about this.
> These CFLAGS are needed for the k26 SOMs, so we will need to include
> them for the kv260 and kr260 defconfigs. I agree with you that
> custom flags are not so nice, and hopefully Xilinx will find a better
> solution for this in future versions.
>
> For now, I think we have to live with it.
Another solution would be to simply have a ZYNQMP_FIRMWARE option that
allows to pass custom CFLAGS, and let each defconfig handle this. Here
as well, no strong feeling about this.
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-27 7:42 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
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 [this message]
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=20230327094222.3b11e289@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 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.