From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH master 2/6] scripts: remove openssl dependency in multi_v7_defconfig
Date: Mon, 12 Jun 2023 14:53:27 +0200 [thread overview]
Message-ID: <20230612125331.1085059-2-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20230612125331.1085059-1-a.fatoum@pengutronix.de>
The 32-bit rockchip support doesn't use the rkimage tool and instead
depends on mkimage to wrap the barebox binary. There's thus no need to
compile the rkimage utility for 32-bit barebox builds. This is a good
thing, because it removes the openssl dependency as the library is used
for sha256/sha512 calculation.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
scripts/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/Kconfig b/scripts/Kconfig
index dcd5f32d1df1..26c6a3c19806 100644
--- a/scripts/Kconfig
+++ b/scripts/Kconfig
@@ -51,8 +51,8 @@ config STM32_IMAGE
config RK_IMAGE
bool "Rockchip image tool" if COMPILE_HOST_TOOLS
- depends on ARCH_ROCKCHIP || COMPILE_HOST_TOOLS
- default y if ARCH_ROCKCHIP
+ depends on ARCH_ROCKCHIP_V8 || COMPILE_HOST_TOOLS
+ default y if ARCH_ROCKCHIP_V8
help
This enables building the image creation tool for Rockchip SoCs
--
2.39.2
next prev parent reply other threads:[~2023-06-12 12:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 12:53 [PATCH master 1/6] net: smc1111: add missing drive's of_device_id array sentinel Ahmad Fatoum
2023-06-12 12:53 ` Ahmad Fatoum [this message]
2023-06-12 12:53 ` [PATCH master 3/6] clocksource: armv7m_systick: fix MMIO address Ahmad Fatoum
2023-06-12 12:53 ` [PATCH master 4/6] of: select OF_OVERLAY where appropriate Ahmad Fatoum
2023-06-12 12:53 ` [PATCH master 5/6] memory_display: don't skip va_end in error case Ahmad Fatoum
2023-06-12 12:53 ` [PATCH master 6/6] regmap-mmio: fix use-after-free Ahmad Fatoum
2023-06-13 7:11 ` Sascha Hauer
2023-06-13 7:17 ` 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=20230612125331.1085059-2-a.fatoum@pengutronix.de \
--to=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