aboutsummaryrefslogtreecommitdiffstats
path: root/package/libs/wolfssl/Config.in
diff options
context:
space:
mode:
authorEneas U de Queiroz <cotequeiroz@gmail.com>2022-04-19 12:02:09 -0300
committerChristian 'Ansuel' Marangi <ansuelsmth@gmail.com>2022-06-07 10:56:49 +0200
commit0a2edc2714dcda10be902c32525723ce2cbcb138 (patch)
tree414ae7aa914c0b042ff2fab2b8fd1cea37620726 /package/libs/wolfssl/Config.in
parent18fd12edb810f9dfbf8410bb81f639df052134cb (diff)
downloadupstream-0a2edc2714dcda10be902c32525723ce2cbcb138.tar.gz
upstream-0a2edc2714dcda10be902c32525723ce2cbcb138.tar.bz2
upstream-0a2edc2714dcda10be902c32525723ce2cbcb138.zip
wolfssl: enable CPU crypto instructions
This enables AES & SHA CPU instructions for compatible armv8, and x86_64 architectures. Add this to the hardware acceleration choice, since they can't be enabled at the same time. The package was marked non-shared, since the arm CPUs may or may not have crypto extensions enabled based on licensing; bcm27xx does not enable them. There is no run-time detection of this for arm. NOTE: Should this be backported to a release branch, it must be done shortly before a new minor release, because the change to nonshared will remove libwolfssl from the shared packages, but the nonshared are only built in a subsequent release! Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
Diffstat (limited to 'package/libs/wolfssl/Config.in')
-rw-r--r--package/libs/wolfssl/Config.in12
1 files changed, 12 insertions, 0 deletions
diff --git a/package/libs/wolfssl/Config.in b/package/libs/wolfssl/Config.in
index b32d5ab6cb..f495a90ff6 100644
--- a/package/libs/wolfssl/Config.in
+++ b/package/libs/wolfssl/Config.in
@@ -62,13 +62,25 @@ config WOLFSSL_ALT_NAMES
config WOLFSSL_HAS_DEVCRYPTO
bool
+config WOLFSSL_ASM_CAPABLE
+ bool
+ default x86_64 || (aarch64 && !TARGET_bcm27xx)
+
choice
prompt "Hardware Acceleration"
+ default WOLFSSL_HAS_CPU_CRYPTO if WOLFSSL_ASM_CAPABLE
default WOLFSSL_HAS_NO_HW
config WOLFSSL_HAS_NO_HW
bool "None"
+ config WOLFSSL_HAS_CPU_CRYPTO
+ bool "Use CPU crypto instructions"
+ depends on WOLFSSL_ASM_CAPABLE
+ help
+ This will use Intel AESNI insturctions or armv8 Crypto Extensions.
+ Either of them should easily outperform hardware crypto in WolfSSL.
+
config WOLFSSL_HAS_AFALG
bool "AF_ALG"