From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: "Frager, Neal" <neal.frager@amd.com>
Cc: "Simek, Michal" <michal.simek@amd.com>,
"'giulio.benetti@benettiengineering.com'"
<giulio.benetti@benettiengineering.com>,
"'buildroot@buildroot.org'" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v1 2/2] configs/zynqmp_zcu106_defconfig: transition to tarballs
Date: Thu, 18 Aug 2022 18:13:06 +0200 [thread overview]
Message-ID: <20220818181306.64b0039e@booty> (raw)
In-Reply-To: <CH2PR12MB50047F205184CA0DFD7C688DF06A9@CH2PR12MB5004.namprd12.prod.outlook.com>
Hi Neal,
On Wed, 17 Aug 2022 17:23:41 +0000
"Frager, Neal" <neal.frager@amd.com> wrote:
> Hi Luca,
>
> > Hi Luca,
> >
> > > Hi Neal,
> >
> > On 13/05/22 06:21, Neal Frager wrote:
> > > Hi Peter, Luca,
> > >
> > >
> > >
> > >> Le 12 mai 2022 à 21:33, Peter Korsgaard <peter@korsgaard.com> a écrit :
> > >>
> > >> CAUTION: This message has originated from an External Source. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email.
> > >>
> > >>
> > >>>>>>> "Neal" == Neal Frager <nealf@xilinx.com> writes:
> > >>
> > >> Hi,
> > >>
> > >>>>> I had to also pass the -m* flags in EXTRA_COMPILER_FLAGS to get
> > >>>>> it to link, presumably the petalinux toolchain has incompatible
> > >>>>> defaults. Luca, any specific reasons to not pass CFLAGS there?
> > >>>>
> > >>>> I'm afraid I have no real answer. :( When I initially wrote the
> > >>>> script I did it to have the same logic as petalinux. Later I
> > >>>> didn't watch for its changes. I would love to be helpful but I
> > >>>> have no access to a zynqmp board now.
> > >>
> > >>> Would it be possible for you to just implement the changes that
> > >>> Peter has proposed? Peter appears to have already identified a solution.
> > >>
> > >>> Both Peter and I have zcu106 boards, so we can both test and
> > >>> verify the update works.
> > >>
> > >> Sorry, that is not true. I haven't found the magic incarnation to
> > >> get a working pmufw build with the toolchain built by crosstool-ng.
> > >> My diff was just to show what I had to change to adjust
> > >> zynqmp-pmufw-builder to use a petalinux toolchain.
> > >>
> > >
> > > Is there a reason why we cannot change the zynqmp-pmufw-builder to download the same toolchain that petalinux uses as the crosstool-ng toolchain?
> >
> > > Can you point to where the petalinux toolchain comes from?
> >
> > > If petalinux uses a publicly available prebuilt toolchain, possibly with sources available, then this could be considered.
> >
> > > However I suspect it does use a toolchain that is shipped by Vitis. If it is the case, then it's not an option here.
> >
> > > The est option would be to fix the ct-ng toolchain of course, but
> > > I'm afraid I cannot be very helpful on this, especially without an
> > > hardware to test. :(
> >
> > > Vitis and PetaLinux 2022.1 use GCC compiler 11.2.0 with the following patch set:
> > > https://github.com/Xilinx/meta-xilinx/tree/xlnx-rel-v2022.1/meta-mic
> > > roblaze/recipes-devtools/gcc/gcc-11
> >
> > I wanted to follow up on this. Have you had a chance to apply these patches to the compiler used by the zynqmp-pmufw-builder?
> >
> > It would be great if we could update the zynqmp-pmufw-builder to generate good pmufw images for zynqmp and kria soms in time for the 2022.2 update.
>
> > Apologies, I had zero spare time to try this. :(
>
> I hope it is ok, but while the zynqmp-pmufw-builder compiler is still creating pmufw images that cannot correctly soft reboot,
> I have created a temporary solution using pmufw images built with petalinux.
>
> https://github.com/nealfrager/zynqmp_pmufw
>
> I just submitted a patch today that migrates the zynqmp defconfigs to use these pmufw images instead of the ones
> generated by the zynqmp-pmufw-builder tool.
>
> https://patchwork.ozlabs.org/project/buildroot/patch/20220817115249.9894-1-neal.frager@xilinx.com/
>
> Once we get the zynqmp-pmufw-builder tool working properly again, I would be happy to switch buildroot back to using it.
>
> Are you ok with this solution?
Given I'm the one who is keeping this idle, I surely cannot blame you!
FYI: I definitely would like to address this issue and hope to find
some time to do that. That said, any patches would be welcome too.
Thanks for your effort.
--
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-08-18 16:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 15:24 [Buildroot] [PATCH v1 1/2] configs/zynqmp_zcu102_defconfig: transition to tarballs Neal Frager via buildroot
2022-05-03 15:24 ` [Buildroot] [PATCH v1 2/2] configs/zynqmp_zcu106_defconfig: " Neal Frager via buildroot
2022-05-04 6:49 ` Peter Korsgaard
[not found] ` <edddb58b-dee7-21aa-05b8-3a94c3e2c4d1@xilinx.com>
2022-05-04 7:18 ` Peter Korsgaard
[not found] ` <86b8666c-4427-32c6-c015-f9b67e963195@xilinx.com>
2022-05-04 7:39 ` Peter Korsgaard
2022-05-04 8:53 ` Neal Frager
2022-05-04 9:12 ` Luca Ceresoli
2022-05-04 9:24 ` Neal Frager
2022-05-04 9:34 ` Neal Frager
[not found] ` <a430617e-f535-75c5-a848-2384c774368d@xilinx.com>
2022-05-04 9:53 ` Luca Ceresoli
[not found] ` <5dd71ac6-35a1-1d34-0964-66390cbb94ba@xilinx.com>
2022-05-04 12:45 ` Neal Frager
[not found] ` <87d7438b-6b9d-a837-c6b9-0e2f6086b8c7@xilinx.com>
2022-05-04 13:09 ` Neal Frager
2022-05-11 9:10 ` Peter Korsgaard
[not found] ` <08d36a3f-8c9b-173d-f965-fa2aef9a8c77@xilinx.com>
2022-05-11 10:08 ` Peter Korsgaard
2022-05-11 11:06 ` Neal Frager
2022-05-11 13:41 ` Neal Frager
2022-05-11 15:54 ` Peter Korsgaard
2022-05-12 14:38 ` Luca Ceresoli
2022-05-12 16:09 ` Neal Frager
2022-05-12 19:32 ` Peter Korsgaard
2022-05-13 4:21 ` Neal Frager
2022-05-13 7:17 ` Luca Ceresoli
2022-05-13 8:40 ` Neal Frager
2022-05-13 9:06 ` Neal Frager
2022-05-13 10:48 ` Neal Frager
2022-05-17 7:42 ` Luca Ceresoli
2022-05-17 7:50 ` Neal Frager
2022-05-17 7:58 ` Peter Korsgaard
2022-08-01 13:59 ` Frager, Neal via buildroot
2022-08-02 15:01 ` Luca Ceresoli via buildroot
2022-08-02 15:06 ` Frager, Neal via buildroot
2022-08-17 17:23 ` Frager, Neal via buildroot
2022-08-18 16:13 ` Luca Ceresoli via buildroot [this message]
2022-05-28 8:37 ` Peter Korsgaard
2022-05-04 6:46 ` [Buildroot] [PATCH v1 1/2] configs/zynqmp_zcu102_defconfig: " Peter Korsgaard
2022-05-28 8:37 ` 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=20220818181306.64b0039e@booty \
--to=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.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