From: Tom Rini <trini@konsulko.com>
To: Jonathan Humphreys <j-humphreys@ti.com>
Cc: Mattijs Korpershoek <mkorpershoek@baylibre.com>,
Kamlesh Gurudasani <kamlesh@ti.com>,
Manorit Chawdhry <m-chawdhry@ti.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Judith Mendez <jm@ti.com>,
Christian Gmeiner <christian.gmeiner@gmail.com>,
Devarsh Thakkar <devarsht@ti.com>, Simon Glass <sjg@chromium.org>,
Nikhil M Jain <n-jain1@ti.com>,
Neha Malcom Francis <n-francis@ti.com>, Andrew Davis <afd@ti.com>,
Maxime Ripard <mripard@kernel.org>,
Siddharth Vadapalli <s-vadapalli@ti.com>,
Roger Quadros <rogerq@kernel.org>, Bryan Brattlof <bb@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Robert Nelson <robertcnelson@gmail.com>,
Nishanth Menon <nm@ti.com>,
Sughosh Ganu <sughosh.ganu@linaro.org>,
Masahisa Kojima <kojima.masahisa@socionext.com>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
u-boot@lists.denx.de
Subject: Re: [PATCH v2 4/7] dts: beagleplay: binman: Include firmware capsules binman nodes
Date: Fri, 10 May 2024 11:32:00 -0600 [thread overview]
Message-ID: <20240510173200.GV2568172@bill-the-cat> (raw)
In-Reply-To: <20240419212819.170033-5-j-humphreys@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1677 bytes --]
On Fri, Apr 19, 2024 at 04:28:16PM -0500, Jonathan Humphreys wrote:
> Fill in the BeaglePlay's capsule GUID properties of the base binman capsule
> nodes.
>
> Signed-off-by: Jonathan Humphreys <j-humphreys@ti.com>
> ---
> arch/arm/dts/k3-am625-beagleplay-u-boot.dtsi | 27 ++++++++++++++++++++
> arch/arm/dts/k3-am625-r5-beagleplay.dts | 15 +++++++++++
> 2 files changed, 42 insertions(+)
This series introduces failure to build in CI, and it's a little tricky
to replicate locally, depending on your environment. You first need to
NOT have BINMAN_INDIRS set and instead be using fake binaries. Second,
it seems python version dependent perhaps? I don't see this on my host,
but by:
- Using the CI container
- Setting up a virtualenv inside of it
- pip install -r tools/buildman/requirements.txt
I get:
$ ./tools/buildman/buildman --keep-outputs --reproducible-builds -dvel --force-build -PEWM --output /tmp/am62x_beagleplay_r5 --board am62x_beagleplay_r5
Building current source for 1 boards (1 thread, 12 jobs per thread)
arm: + am62x_beagleplay_r5
+(am62x_beagleplay_r5) Image 'tiboot3-am62x-gp-evm.bin' is missing optional external blobs but is still functional: ti-fs-gp.bin
+(am62x_beagleplay_r5)
+(am62x_beagleplay_r5) /binman/tiboot3-am62x-gp-evm.bin/ti-fs-gp.bin (ti-sysfw/ti-fs-firmware-am62x-gp.bin):
+(am62x_beagleplay_r5) Missing blob
+(am62x_beagleplay_r5) binman: object of type 'NoneType' has no len()
+(am62x_beagleplay_r5) make[1]: *** [Makefile:1126: .binman_stamp] Error 1
+(am62x_beagleplay_r5) make: *** [Makefile:177: sub-make] Error 2
0 0 1 /1 am62x_beagleplay_r5
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-05-10 17:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 21:28 [PATCH v2 0/7] binman: ti: create binman nodes for EFI capsules Jonathan Humphreys
2024-04-19 21:28 ` [PATCH v2 1/7] dts: ti: binman: Add base K3 firmware capsule nodes Jonathan Humphreys
2024-04-19 21:28 ` [PATCH v2 2/7] dts: am64x: binman: Include firmware capsules binman nodes Jonathan Humphreys
2024-04-19 21:28 ` [PATCH v2 3/7] dts: j721e: " Jonathan Humphreys
2024-04-19 21:28 ` [PATCH v2 4/7] dts: beagleplay: " Jonathan Humphreys
2024-05-10 17:32 ` Tom Rini [this message]
2024-05-22 2:20 ` Jon Humphreys
2024-05-22 14:10 ` Tom Rini
2024-05-23 4:12 ` Jon Humphreys
2024-05-23 15:17 ` Tom Rini
2024-05-23 21:09 ` Jon Humphreys
2024-05-23 22:12 ` Tom Rini
2024-04-19 21:28 ` [PATCH v2 5/7] dts: am62px: " Jonathan Humphreys
2024-04-19 21:28 ` [PATCH v2 6/7] dts: am62x: " Jonathan Humphreys
2024-04-19 21:28 ` [PATCH v2 7/7] dts: beagleboneai64: " Jonathan Humphreys
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=20240510173200.GV2568172@bill-the-cat \
--to=trini@konsulko.com \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=christian.gmeiner@gmail.com \
--cc=devarsht@ti.com \
--cc=ilias.apalodimas@linaro.org \
--cc=j-humphreys@ti.com \
--cc=jm@ti.com \
--cc=kamlesh@ti.com \
--cc=kojima.masahisa@socionext.com \
--cc=m-chawdhry@ti.com \
--cc=marcel.ziswiler@toradex.com \
--cc=mkorpershoek@baylibre.com \
--cc=mripard@kernel.org \
--cc=n-francis@ti.com \
--cc=n-jain1@ti.com \
--cc=nm@ti.com \
--cc=robertcnelson@gmail.com \
--cc=rogerq@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=sjg@chromium.org \
--cc=sughosh.ganu@linaro.org \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
--cc=xypron.glpk@gmx.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).