From: Niklas Cassel via buildroot <buildroot@buildroot.org>
To: Sergey Matyukevich <geomatsi@gmail.com>
Cc: Julien Olivain <ju.o@free.fr>,
"buildroot@buildroot.org" <buildroot@buildroot.org>,
Dario Binacchi <dario.binacchi@amarulasolutions.com>,
"linux-amarula@amarulasolutions.com"
<linux-amarula@amarulasolutions.com>,
"Yann E . MORIN" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH 1/1] boot/uboot: fix binman failure
Date: Thu, 13 Feb 2025 13:21:56 +0000 [thread overview]
Message-ID: <Z63x80LJFWR9ShPV@ryzen> (raw)
In-Reply-To: <Z62yW6nlzZw2OlpB@curiosity>
Hello Sergey,
On Thu, Feb 13, 2025 at 11:50:35AM +0300, Sergey Matyukevich wrote:
> 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"
I think that Dario is working on a patch:
https://lore.kernel.org/buildroot/87frkjyma6.fsf@dell.be.48ers.dk/T/#m7f5f85f0cdb2468c78512d34ade8703595921047
However, Peter had some comments, so maybe Dario will send a v2?
Kind regards,
Niklas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-02-13 13:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 23:12 [Buildroot] [PATCH 1/1] boot/uboot: fix binman failure Dario Binacchi
2025-02-08 15:21 ` Sergey Matyukevich
2025-02-10 11:53 ` Niklas Cassel via buildroot
2025-02-10 19:33 ` Julien Olivain
2025-02-10 21:16 ` Julien Olivain
2025-02-13 8:50 ` Sergey Matyukevich
2025-02-13 13:21 ` Niklas Cassel via buildroot [this message]
2025-02-12 21:23 ` Christian Stewart via buildroot
2025-02-12 21:24 ` Christian Stewart via buildroot
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=Z63x80LJFWR9ShPV@ryzen \
--to=buildroot@buildroot.org \
--cc=Niklas.Cassel@wdc.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=geomatsi@gmail.com \
--cc=ju.o@free.fr \
--cc=linux-amarula@amarulasolutions.com \
--cc=yann.morin.1998@free.fr \
/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