From: Rasmus Villemoes <ravi@prevas.dk>
To: E Shattow <e@freeshell.de>
Cc: Tom Rini <trini@konsulko.com>, <u-boot@lists.denx.de>
Subject: Re: [PATCH v1] scripts/Makefile.lib: add CONFIG_SYS_CONFIG_NAME prefix to dtsi search
Date: Mon, 25 Aug 2025 09:50:40 +0200 [thread overview]
Message-ID: <87sehf4z73.fsf@prevas.dk> (raw)
In-Reply-To: <20250825040122.303437-1-e@freeshell.de> (E. Shattow's message of "Sun, 24 Aug 2025 21:01:14 -0700")
On Sun, Aug 24 2025, E Shattow <e@freeshell.de> wrote:
> Add ${CONFIG_SYS_CONFIG_NAME}-u-boot.dtsi into dtsi include search order:
> dtsi location, SYS_SOC, SYS_CPU, SYS_VENDOR, (SYS_CONFIG_NAME), no prefix
>
I tried that, with CONFIG_SYS_BOARD, but for my use case I wanted it to
have higher priority than something "just" matching SOC or CPU.
https://lore.kernel.org/u-boot/20230317102639.464263-1-rasmus.villemoes@prevas.dk/
Can you explain what board(s) you are going to use this for? Because
this having lower priority than SOC, CPU, VENDOR seems wrong, and if
there already is some soc-dtsi file for you board, this won't have any
effect for you.
The problem with my patch was that we build a lot of completely
unnecessary .dtb files, and the build of those unneeded dtb files break
if/when the .config we're building causes an unrelated .dtsi file to be
included (most often because it refers to nodes that do not exist). I've
suggested several times that we just nuke most of that dts/Makefile
because it's really not useful, it still contains typos, and nobody
notices because we nowadays have build logic to automatically build all
the .dtbs that are actually relevant to the .config we're building.
Rasmus
next prev parent reply other threads:[~2025-08-25 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 4:01 [PATCH v1] scripts/Makefile.lib: add CONFIG_SYS_CONFIG_NAME prefix to dtsi search E Shattow
2025-08-25 7:50 ` Rasmus Villemoes [this message]
2025-08-25 8:29 ` E Shattow
2025-08-26 21:25 ` E Shattow
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=87sehf4z73.fsf@prevas.dk \
--to=ravi@prevas.dk \
--cc=e@freeshell.de \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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.