From: Christian Stewart via buildroot <buildroot@buildroot.org>
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: Wed, 12 Feb 2025 13:24:32 -0800 [thread overview]
Message-ID: <m234giua9b.fsf@aperture.us> (raw)
In-Reply-To: <96b69abb843dc7292777c64f6787f134@free.fr> (Julien Olivain's message of "Mon, 10 Feb 2025 20:33:55 +0100")
Hi Julien, Dario,
Julien Olivain <ju.o@free.fr> writes:
> I don't think this is the right fix for this issue.
>
> U-Boot Makefile is using the "SCP" variable here:
> https://source.denx.de/u-boot/u-boot/-/blob/v2025.01/Makefile#L1411
>
> According the the "binman" documentation:
> https://source.denx.de/u-boot/u-boot/-/blob/v2025.01/tools/binman/entries.rst#L1727
>
> This SCP is the "System Control Processor firmware blob".
>
> Buildroot exports a SCP variable here:
> https://gitlab.com/buildroot.org/buildroot/-/blob/2024.11.1/package/pkg-download.mk#L18
>
> The value is set here:
> https://gitlab.com/buildroot.org/buildroot/-/blob/2024.11.1/Config.in#L134
>
> BR2_SCP corresponds to the SSH Secure File Copy command:
> https://man.openbsd.org/scp
>
> which has nothing to do with the System Control Processor firmware
> binman is expecting. So this is an unfortunate name clash.
>
> There is few defconfigs using BR2_TARGET_UBOOT_CUSTOM_MAKEOPTS to
> workaround this. See for example:
> https://gitlab.com/buildroot.org/buildroot/-/blob/2024.11.1/configs/orangepi_zero_plus2_defconfig#L45
This worked to fix the issue for me on bananapi m3:
# https://lore.kernel.org/buildroot/96b69abb843dc7292777c64f6787f134@free.fr/
# https://gitlab.com/buildroot.org/buildroot/-/blob/2024.11.1/configs/orangepi_zero_plus2_defconfig#L45
# https://github.com/skiffos/SkiffOS/issues/325
BR2_TARGET_UBOOT_CUSTOM_MAKEOPTS="SCP=/dev/null"
Thanks,
Christian Stewart
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-02-12 21:24 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
2025-02-12 21:23 ` Christian Stewart via buildroot
2025-02-12 21:24 ` Christian Stewart via buildroot [this message]
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=m234giua9b.fsf@aperture.us \
--to=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=dario.binacchi@amarulasolutions.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