Re: [Buildroot] [PATCH 1/1] boot/uboot: fix binman failure

From: Sergey Matyukevich <geomatsi@gmail.com>
To: Julien Olivain <ju.o@free.fr>
Cc: Dario Binacchi <dario.binacchi@amarulasolutions.com>,
	buildroot@buildroot.org,
	"Yann E . MORIN" <yann.morin.1998@free.fr>,
	linux-amarula@amarulasolutions.com
Subject: Re: [Buildroot] [PATCH 1/1] boot/uboot: fix binman failure
Date: Thu, 13 Feb 2025 11:50:35 +0300	[thread overview]
Message-ID: <Z62yW6nlzZw2OlpB@curiosity> (raw)
In-Reply-To: <a023971c7c8bfa4826a9a8721500c7ff@free.fr>

Hi Julien and all,

On Mon, Feb 10, 2025 at 10:16:05PM +0100, Julien Olivain wrote:
> Hi Dario, All,
> 
> On 10/02/2025 20:33, Julien Olivain wrote:
> > Maybe we could introduce a new u-boot Kconfig option string such as:
> > BR2_TARGET_UBOOT_SCP_FIRMWARE and properly set the u-boot SCP
> > variable to this value (and set it to /dev/null if empty).
> 
> After quickly testing, it seems u-boot and binman can take
> an empty string without failing. So there is no need to
> set it to /dev/null if empty. So if a new Kconfig is added
> with an empty default value, just adding
> "SCP=$(BR2_TARGET_UBOOT_SCP_FIRMWARE)" in UBOOT_MAKE_OPTS
> should be fine.

Am I correct assuming that there will be no generic fix and
the recommended solution is to add the following line to all
the impacted configs:
- BR2_TARGET_UBOOT_CUSTOM_MAKEOPTS="SCP=/dev/null"

Regards,
Sergey
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot