diff options
| author | Hauke Mehrtens <hauke@hauke-m.de> | 2022-07-18 23:06:00 +0200 |
|---|---|---|
| committer | Hauke Mehrtens <hauke@hauke-m.de> | 2022-07-20 18:12:52 +0200 |
| commit | a1068f77c90244c38ff54e94a43837b4c65cbf72 (patch) | |
| tree | b762d1eb07e44994f0a37fc962a4f1480cd8d917 | |
| parent | dbe19b1041b15097af139c0d80dc6b3d07466107 (diff) | |
| download | upstream-a1068f77c90244c38ff54e94a43837b4c65cbf72.tar.gz upstream-a1068f77c90244c38ff54e94a43837b4c65cbf72.tar.bz2 upstream-a1068f77c90244c38ff54e94a43837b4c65cbf72.zip | |
wolfssl: Do not activate HW acceleration on armvirt by default
The armvirt target is also used to run OpenWrt in lxc on other targets
like a Raspberry Pi. If we set WOLFSSL_HAS_CPU_CRYPTO by default the
wolfssl binray is only working when the CPU supports the hardware crypto
extension.
Some targets like the Raspberry Pi do not support the ARM CPU crypto
extension, compile wolfssl without it by default. It is still possible
to activate it in custom builds.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
(cherry picked from commit d1b5d17d03c844ad578bb53b90ea17377bdc5eee)
| -rw-r--r-- | package/libs/wolfssl/Config.in | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/package/libs/wolfssl/Config.in b/package/libs/wolfssl/Config.in index 56e968f6ed..9a7a06d04f 100644 --- a/package/libs/wolfssl/Config.in +++ b/package/libs/wolfssl/Config.in @@ -69,7 +69,7 @@ config WOLFSSL_ASM_CAPABLE choice prompt "Hardware Acceleration" - default WOLFSSL_HAS_CPU_CRYPTO if WOLFSSL_ASM_CAPABLE + default WOLFSSL_HAS_CPU_CRYPTO if WOLFSSL_ASM_CAPABLE && !TARGET_armvirt default WOLFSSL_HAS_NO_HW config WOLFSSL_HAS_NO_HW |