From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>, nm@ti.com
Cc: Wadim Egorov <w.egorov@phytec.de>,
ilias.apalodimas@linaro.org, marek.vasut+renesas@mailbox.org,
sughosh.ganu@arm.com, u-boot@lists.denx.de,
upstream@lists.phytec.de
Subject: Re: [PATCH] Makefile: binman: Search board directory before srctree
Date: Fri, 15 May 2026 10:02:56 -0600 [thread overview]
Message-ID: <20260515160256.GF1858239@bill-the-cat> (raw)
In-Reply-To: <CAFLszTid-e+NWrFxoorfrUT23_mztUZP8FRbmT9FJ55M8A+FXA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2202 bytes --]
On Fri, May 15, 2026 at 09:35:10AM -0600, Simon Glass wrote:
> Hi Tom,
>
> On Fri, 15 May 2026 at 08:54, Tom Rini <trini@konsulko.com> wrote:
> >
> > On Fri, May 15, 2026 at 07:43:27AM +0200, Wadim Egorov wrote:
> >
> > > A file like rm-cfg.yaml accidentally left in the source tree root
> > > shadows the board-specific copy. binman builds the wrong YAML, the
> > > resulting rm-cfg.bin may match a different SoC, and we end up with
> > > the following error:
> > >
> > > k3_system_controller sysctrler: k3_sysctrler_start:
> > > Boot Notification response failed. ret = -110
> > >
> > > Move the board directory ahead of the srctree root so that the
> > > most-specific match wins.
> > >
> > > Signed-off-by: Wadim Egorov <w.egorov@phytec.de>
> > > ---
> > > Makefile | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/Makefile b/Makefile
> > > index 552328f9f2c..1ec29dfe0be 100644
> > > --- a/Makefile
> > > +++ b/Makefile
> > > @@ -1682,7 +1682,7 @@ cmd_binman = $(srctree)/tools/binman/binman $(if $(BINMAN_DEBUG),-D) \
> > > build -u -d $(binman_dtb) -O . -m \
> > > --allow-missing --fake-ext-blobs \
> > > $(if $(BINMAN_ALLOW_MISSING),--ignore-missing) \
> > > - -I . -I $(srctree) -I $(srctree)/board/$(BOARDDIR) \
> > > + -I . -I $(srctree)/board/$(BOARDDIR) -I $(srctree) \
> > > $(foreach f,$(of_list_dirs),-I $(f)) -a of-list=$(of_list) \
> > > $(foreach f,$(BINMAN_INDIRS),-I $(f)) \
> > > -a atf-bl1-path=${BL1} \
> >
> > Why do we need to look in $(srctree) itself?
>
> See for example:
>
> arch/arm/dts/k3-j721e-binman.dtsi:308: private-key =
> "arch/arm/mach-k3/keys/custMpk.pem";
That's not great, I'm sorry I missed it at the time. I wonder how easy
replacing that key is with a non-dummy key. Hopefully it's done in a way
that doesn't encourage checking private keys in to repositories..
> Also, people sometimes put files in the source tree, e.g. BL31 images,
> in the hope that they will be found.
That's also a bad practice and what BINMAN_INDIRS is for.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-05-15 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 5:43 [PATCH] Makefile: binman: Search board directory before srctree Wadim Egorov
2026-05-15 14:01 ` Simon Glass
2026-05-15 14:54 ` Tom Rini
2026-05-15 15:35 ` Simon Glass
2026-05-15 16:02 ` Tom Rini [this message]
2026-05-15 18:13 ` Simon Glass
2026-05-15 18:24 ` Tom Rini
2026-05-15 18:32 ` Simon Glass
2026-05-15 18:44 ` Tom Rini
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=20260515160256.GF1858239@bill-the-cat \
--to=trini@konsulko.com \
--cc=ilias.apalodimas@linaro.org \
--cc=marek.vasut+renesas@mailbox.org \
--cc=nm@ti.com \
--cc=sjg@chromium.org \
--cc=sughosh.ganu@arm.com \
--cc=u-boot@lists.denx.de \
--cc=upstream@lists.phytec.de \
--cc=w.egorov@phytec.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 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.