From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2-RESEND 3/6] zynqmp-pmufw-binaries: new package
Date: Mon, 9 Apr 2018 23:13:27 +0200 [thread overview]
Message-ID: <20180409231327.28e2b2e4@windsurf> (raw)
In-Reply-To: <1523032461-3295-4-git-send-email-luca@lucaceresoli.net>
Hello,
On Fri, 6 Apr 2018 18:34:18 +0200, Luca Ceresoli wrote:
> diff --git a/boot/zynqmp-pmufw-binaries/Config.in b/boot/zynqmp-pmufw-binaries/Config.in
> new file mode 100644
> index 000000000000..e39561cbf91e
> --- /dev/null
> +++ b/boot/zynqmp-pmufw-binaries/Config.in
> @@ -0,0 +1,19 @@
> +config BR2_TARGET_ZYNQMP_PMUFW_BINARIES
> + bool "Zynqmp PMU firmware"
> + depends on BR2_aarch64
> + help
> + This package provides precompiled firmwares for the Platform
> + Management Unit (PMU) of the Xilinx ZynqMP family of SoCs.
> +
> + https://github.com/lucaceresoli/zynqmp-pmufw-binaries
> +
> +if BR2_TARGET_ZYNQMP_PMUFW_BINARIES
> +
> +config BR2_TARGET_ZYNQMP_PMUFW_BINARIES_IMAGE
> + string "PMU firmware image file"
> + help
> + Enter the path to the PMU firmware file for your board and
> + configuration, relative to the repository top directory.
> + Example: "zcu106-default/pmufw.bin".
So this hints at the fact that this firmware is board specific. Is that
correct ? If so, shouldn't we plan on making the Git repo and its
version configurable ?
I mean, what are the chances that for some random ZynqMP board, your
Github repo will contain the appropriate firmware file ?
Generally speaking, it's a bit annoying that we can't build this from
source. I understand it needs a Microblaze toolchain, so it's very
difficult to integrate in Buildroot :-/
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-04-09 21:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 16:34 [Buildroot] [PATCH v2-RESEND 0/6] Add Xilinx ZynqMP and ZCU106 board support Luca Ceresoli
2018-04-06 16:34 ` [Buildroot] [PATCH v2-RESEND 1/6] arm-trusted-firmware: simplify release dir path Luca Ceresoli
2018-04-06 16:34 ` [Buildroot] [PATCH v2-RESEND 2/6] arm-trusted-firmware: generate atf-uboot.ub for ZynqMP booting Luca Ceresoli
2018-04-09 21:08 ` Thomas Petazzoni
2018-04-11 21:12 ` Luca Ceresoli
2018-04-06 16:34 ` [Buildroot] [PATCH v2-RESEND 3/6] zynqmp-pmufw-binaries: new package Luca Ceresoli
2018-04-09 21:13 ` Thomas Petazzoni [this message]
2018-04-11 21:03 ` Luca Ceresoli
2018-04-12 9:09 ` Thomas Petazzoni
2018-05-03 16:26 ` Luca Ceresoli
2018-04-06 16:34 ` [Buildroot] [PATCH v2-RESEND 4/6] uboot: zynqmp: generate SPL image with PMUFW binary Luca Ceresoli
2018-04-09 21:26 ` Thomas Petazzoni
2018-04-06 16:34 ` [Buildroot] [PATCH v2-RESEND 5/6] uboot: zynqmp: allow to use custom psu_init files Luca Ceresoli
2018-04-06 16:34 ` [Buildroot] [PATCH v2-RESEND 6/6] configs: add Xilinx ZCU106 board (ZynqMP SoC) Luca Ceresoli
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=20180409231327.28e2b2e4@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.