Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Neal Frager <neal.frager@amd.com>
Cc: luca.ceresoli@bootlin.com, buildroot@buildroot.org,
	kris.chaplin@amd.com, wesley@sonifex.co.uk,
	giulio.benetti@benettiengineering.com, michal.simek@amd.com,
	yann.morin.1998@free.fr
Subject: Re: [Buildroot] [PATCH v4 1/1] boot/uboot/uboot.mk: add pmufw.elf support
Date: Wed, 02 Nov 2022 07:53:27 +0100	[thread overview]
Message-ID: <877d0dvod4.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20221013064931.60174-1-neal.frager@amd.com> (Neal Frager's message of "Thu, 13 Oct 2022 00:49:31 -0600")

>>>>> "Neal" == Neal Frager <neal.frager@amd.com> writes:

 > This patch adds support for zynqmp pmufw.elf files.
 > It will allow buildroot to use pmufw.elf binaries directly
 > from the Xilinx git repository built by petalinux in
 > addition to still supporting pmufw.bin binaries built
 > by the zynqmp-pmufw-builder.

 > https://github.com/Xilinx/ubuntu-firmware/tree/v2022.1_22.04_1/xlnx-firmware

 > Signed-off-by: Neal Frager <neal.frager@amd.com>
 > ---
 > V1-> V2:
 >   - corrected objcopy instruction for converting elf to bin
 > V2-> V3:
 >   - removed unnecessary spaces
 >   - simplified if statement to check for a pmufw.elf file
 > V3-> V4:
 >   - added spaces around = sign of UBOOT_ZYNQMP_PMUFW_BASENAME definition

Committed to 2022.08.x and 2022.02.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2022-11-02  6:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-13  6:49 [Buildroot] [PATCH v4 1/1] boot/uboot/uboot.mk: add pmufw.elf support Neal Frager via buildroot
2022-10-13 13:18 ` Luca Ceresoli via buildroot
2022-10-13 13:54   ` Frager, Neal via buildroot
2022-10-15 16:41 ` Peter Korsgaard
2022-11-02  6:53 ` Peter Korsgaard [this message]

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=877d0dvod4.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=kris.chaplin@amd.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