From: Greg Malysa <malysagreg@gmail.com>
To: u-boot@lists.denx.de
Cc: adsp-linux@analog.com, Greg Malysa <malysagreg@gmail.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>
Subject: [PATCH 03/10] docker: add ADI build-related tools to docker image
Date: Mon, 2 Jun 2025 15:44:41 -0400 [thread overview]
Message-ID: <20250602194507.15159-4-malysagreg@gmail.com> (raw)
In-Reply-To: <20250602194507.15159-1-malysagreg@gmail.com>
ADI processors require packaging with the ldr utility for bootrom
compatibility. Normally this is available as part of our yocto-derived
toolchain but it is not a part of any other premade toolchain, so it is
otherwise unavailable in the docker image for CI. This patch adds a
source build from the ADI maintained github repository. The same ldr
tool is used for arm and arm64 for all of our boards with names adjusted
to match the expected $(CROSS_COMPILE) for these boards.
Signed-off-by: Greg Malysa <malysagreg@gmail.com>
---
tools/docker/Dockerfile | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/tools/docker/Dockerfile b/tools/docker/Dockerfile
index ceb7a25ad4d..1c4a169e079 100644
--- a/tools/docker/Dockerfile
+++ b/tools/docker/Dockerfile
@@ -308,6 +308,14 @@ RUN wget -O - https://coreboot.org/releases/coreboot-24.08.tar.xz | tar -C /tmp
sudo cp build/coreboot.rom build/cbfstool /opt/coreboot/ && \
rm -rf /tmp/coreboot-24.08
+# Build ldr tool for ADI boards and install to match expected abi name
+RUN git clone https://github.com/analogdevicesinc/lnxdsp-arm-poky-linux-gnueabi-ldr.git /tmp/lnxdsp-arm-poky-linux-gnueabi-ldr && \
+ cd /tmp/lnxdsp-arm-poky-linux-gnueabi-ldr/src/ldr && \
+ ./configure && \
+ make -j $(nproc) && \
+ cp ldr /usr/bin/arm-linux-gnueabi-ldr && \
+ cp ldr /usr/bin/aarch64-linux-ldr
+
# Create our user/group
RUN echo uboot ALL=NOPASSWD: ALL > /etc/sudoers.d/uboot
RUN useradd -m -U uboot
--
2.45.2
next prev parent reply other threads:[~2025-06-02 19:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 19:44 [PATCH 00/10] sc5xx: Add complete board support for all ADI SC5xx boards Greg Malysa
2025-06-02 19:44 ` [PATCH 01/10] mach-sc5xx: Introduce Kconfig symbols for image addresses Greg Malysa
2025-06-02 19:44 ` [PATCH 02/10] mach-sc5xx: Add binman support Greg Malysa
2025-06-02 19:44 ` Greg Malysa [this message]
2025-06-02 20:11 ` [PATCH 03/10] docker: add ADI build-related tools to docker image Heinrich Schuchardt
[not found] ` <CABdDSeV0D2n223hu+2pAp0x_UksGU=15m09pwY7edgpP5kZ9_w@mail.gmail.com>
2025-06-03 7:06 ` Greg Malysa
2025-06-02 19:44 ` [PATCH 04/10] board: adi: Add SOMCRR infrastructure Greg Malysa
2025-06-02 19:44 ` [PATCH 05/10] board: adi: Add support for SC573-ezkit Greg Malysa
2025-06-02 19:44 ` [PATCH 06/10] board: adi: Add support for SC589 boards Greg Malysa
2025-06-02 19:44 ` [PATCH 07/10] board: adi: Add support for SC584 Greg Malysa
2025-06-02 19:44 ` [PATCH 08/10] board: adi: Add support for SC598 Greg Malysa
2025-06-02 19:44 ` [PATCH 09/10] board: adi: Add support for SC594 Greg Malysa
2025-06-02 19:44 ` [PATCH 10/10] MAINTAINERS: Update ADI entries for new boards Greg Malysa
2025-06-05 17:12 ` Tom Rini
2025-07-09 19:14 ` Greg Malysa
2025-07-11 15:48 ` Tom Rini
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=20250602194507.15159-4-malysagreg@gmail.com \
--to=malysagreg@gmail.com \
--cc=adsp-linux@analog.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).