From: Peter Korsgaard <peter@korsgaard.com>
To: Neal Frager <neal.frager@xilinx.com>
Cc: luca@lucaceresoli.net, giulio.benetti@benettiengineering.com,
michal.simek@xilinx.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v6 2/2] add configs/zynqmp_zcu102_defconfig
Date: Sat, 12 Feb 2022 14:43:20 +0100 [thread overview]
Message-ID: <87leygnqtj.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220211144402.1626443-2-neal.frager@xilinx.com> (Neal Frager's message of "Fri, 11 Feb 2022 07:44:02 -0700")
>>>>> "Neal" == Neal Frager <neal.frager@xilinx.com> writes:
> This patch:
> - adds support for Xilinx ZCU102 evaluation board
> - ZCU102 features can be found here:
> https://www.xilinx.com/products/boards-and-kits/zcu102.html
> Signed-off-by: Neal Frager <neal.frager@xilinx.com>
> Reviewed-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> Tested-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> [Giulio: only build tested]
> ---
V1-> V2:
> * fixed general build issues
> * added extlinux.conf for run-time boot issue
V2-> V3:
> * enabled support for host machines without OpenSSL required by U-Boot and Linux
> * moved readme.txt update to zynqmp_zcu102_defconfig patch 2/2
V3-> V4:
> * cleaned up commit log messages
> * added version history
V4-> V5:
> * switched to sha1 urls to make ATF, U-Boot and Linux builds reproducible
> * generated board specific pm_cfg_obj.c files with vitis 2021.2
V5-> V6:
> * fixed build issue with pm_cfg_obj.c files
> ---
> ---
> board/zynqmp/readme.txt | 23 +-
> board/zynqmp/zcu102/pm_cfg_obj.c | 563 +++++++++++++++++++++++++++++++
> configs/zynqmp_zcu102_defconfig | 39 +++
> 3 files changed, 618 insertions(+), 7 deletions(-)
> create mode 100644 board/zynqmp/zcu102/pm_cfg_obj.c
> create mode 100644 configs/zynqmp_zcu102_defconfig
You forgot to add an entry to the DEVELOPERS file for it, so I've done
that, changed the git hashes with the git describe output like I
explained for zcu106 and committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-02-12 13:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 14:44 [Buildroot] [PATCH v6 1/2] configs/zynqmp_zcu106: bump ATF/U-Boot/Linux to Xilinx 2022 Neal Frager
2022-02-11 14:44 ` [Buildroot] [PATCH v6 2/2] add configs/zynqmp_zcu102_defconfig Neal Frager
2022-02-12 13:43 ` Peter Korsgaard [this message]
2022-02-12 13:13 ` [Buildroot] [PATCH v6 1/2] configs/zynqmp_zcu106: bump ATF/U-Boot/Linux to Xilinx 2022 Luca Ceresoli
2022-02-12 13:18 ` Neal Frager
2022-02-12 13:45 ` Peter Korsgaard
2022-02-12 14:47 ` Neal Frager
2022-02-23 10:05 ` Peter Korsgaard
2022-02-23 12:55 ` Neal Frager
2022-02-12 13:42 ` Peter Korsgaard
2022-02-23 10:04 ` Peter Korsgaard
2022-02-23 11:02 ` Neal Frager
2022-02-23 11:11 ` Peter Korsgaard
2022-02-23 11:29 ` Neal Frager
2022-02-23 11:18 ` Peter Korsgaard
2022-02-23 11:27 ` Neal Frager
2022-02-23 11:07 ` Neal Frager
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=87leygnqtj.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=luca@lucaceresoli.net \
--cc=michal.simek@xilinx.com \
--cc=neal.frager@xilinx.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