mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] Kbuild: include arch/ Makefile before other directories
Date: Tue, 13 Jun 2023 11:16:59 +0200	[thread overview]
Message-ID: <20230613091659.GS18491@pengutronix.de> (raw)
In-Reply-To: <20230605063719.1431079-1-a.fatoum@pengutronix.de>

On Mon, Jun 05, 2023 at 08:37:19AM +0200, Ahmad Fatoum wrote:
> Unless overridden by SORT*, LD will place sections matched by wildcards
> in the order they were seen in the link. So far, this meant that
> arch/ initcalls and device trees compiled into barebox proper, were
> always last.
> 
> For platforms with PBL or with only one device tree in barebox proper,
> this didn't matter much, but when enabling the of_manipulation selftest,
> a second device tree would be built into barebox on kvx, openrisc and
> some MIPS.
> 
> Because all directories appear before arch/, this had the effect that
> on kvx, openrisc and some MIPS, __dtb_start would end up pointing at the
> test's device tree instead of the board device tree breaking the build.
> 
> Switching the affected platforms to use PBL would be one fix for the
> issue, but there's a simple one: let's do what Linux does in its
> top-level Kbuild file and have arch/ not be the last in sequence.
> 
> This may fause fallout for code that depended on specific ordering of
> initcalls or other linker-defined lists, which would need to be fixed.

I am afraid this causes regressions that take a long time to realize and
to sort out.

We could do something along the following lines to pick the correct dtb.
This is only meant as an example, it likely needs some sugar to work
correctly in all cases.

Sascha

----------------------------------8<------------------------------

diff --git a/arch/mips/boot/Makefile b/arch/mips/boot/Makefile
index d1e27b5e6b..e114cc5d8a 100644
--- a/arch/mips/boot/Makefile
+++ b/arch/mips/boot/Makefile
@@ -3,6 +3,7 @@
 obj-y += start.o
 obj-y += main_entry.o
 
+CFLAGS_dtb.o += -DBUILTIN_DTB_SYMBOL=__dtb_$(patsubst "%",%,$(subst -,_,$(CONFIG_BUILTIN_DTB_NAME)))_start
 obj-$(CONFIG_OFDEVICE) += dtb.o
 
 pbl-y += main_entry-pbl.o
diff --git a/arch/mips/boot/dtb.c b/arch/mips/boot/dtb.c
index ece1494e5f..3afcd20a0e 100644
--- a/arch/mips/boot/dtb.c
+++ b/arch/mips/boot/dtb.c
@@ -34,7 +34,7 @@ int of_add_memory_bank(struct device_node *node, bool dump, int r,
 	return ret;
 }
 
-extern char __dtb_start[];
+extern char BUILTIN_DTB_SYMBOL[];
 
 static int of_mips_init(void)
 {
@@ -42,7 +42,7 @@ static int of_mips_init(void)
 
 	fdt = glob_fdt;
 	if (!fdt)
-		fdt = __dtb_start;
+		fdt = BUILTIN_DTB_SYMBOL;
 
 	return barebox_register_fdt(fdt);
 }
-- 
2.39.2

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  parent reply	other threads:[~2023-06-13  9:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-05  6:37 Ahmad Fatoum
2023-06-13  8:04 ` Ahmad Fatoum
2023-06-13  9:16 ` Sascha Hauer [this message]
2023-06-13 10:18   ` Ahmad Fatoum

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=20230613091659.GS18491@pengutronix.de \
    --to=sha@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /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