summaryrefslogtreecommitdiffstats
path: root/crypto/Makefile
diff options
context:
space:
mode:
authorAhmad Fatoum <a.fatoum@pengutronix.de>2022-08-18 07:04:45 +0200
committerSascha Hauer <s.hauer@pengutronix.de>2022-08-22 10:52:19 +0200
commit4794b2ccced53efaf2dc8d0fc1c70e71431d4daa (patch)
tree0ad644cd658ea43fbcaa9d0d04347555b2adda14 /crypto/Makefile
parent4b5b65fe21be09d5eb42ab822c72638a110b7c60 (diff)
downloadbarebox-4794b2ccced53efaf2dc8d0fc1c70e71431d4daa.tar.gz
barebox-4794b2ccced53efaf2dc8d0fc1c70e71431d4daa.tar.xz
pbl: export pbl_barebox_verify
There's no downside to always build the digest verification code in PBL and export pbl_barebox_verify to access it. This allows board code to use the function for verifying other firmware blobs and CONFIG_PBL_VERIFY_PIGGY=y will remain to enable the verification at barebox proper extraction time. Code not using it will have the function sections garbage collected by the linker, so no functional change. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220818050447.2072932-2-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'crypto/Makefile')
-rw-r--r--crypto/Makefile3
1 files changed, 1 insertions, 2 deletions
diff --git a/crypto/Makefile b/crypto/Makefile
index 762d7e543b..22035d4f69 100644
--- a/crypto/Makefile
+++ b/crypto/Makefile
@@ -10,8 +10,7 @@ obj-$(CONFIG_DIGEST_MD5_GENERIC) += md5.o
obj-$(CONFIG_DIGEST_SHA1_GENERIC) += sha1.o
obj-$(CONFIG_DIGEST_SHA224_GENERIC) += sha2.o
obj-$(CONFIG_DIGEST_SHA256_GENERIC) += sha2.o
-pbl-$(CONFIG_PBL_VERIFY_PIGGY) += sha2.o
-pbl-$(CONFIG_PBL_VERIFY_PIGGY) += digest.o
+pbl-y += sha2.o digest.o
obj-$(CONFIG_DIGEST_SHA384_GENERIC) += sha4.o
obj-$(CONFIG_DIGEST_SHA512_GENERIC) += sha4.o
obj-y += memneq.o