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 17:02:45 +0200 |
| commit | d1b5d17d03c844ad578bb53b90ea17377bdc5eee (patch) | |
| tree | b68926a098d22e426ea9f493deca825ee3ba31fc /package/libs | |
| parent | 5451b03b7ceb2315445c683fe174e28bbdd49c2f (diff) | |
| download | upstream-d1b5d17d03c844ad578bb53b90ea17377bdc5eee.tar.gz upstream-d1b5d17d03c844ad578bb53b90ea17377bdc5eee.tar.bz2 upstream-d1b5d17d03c844ad578bb53b90ea17377bdc5eee.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>
Diffstat (limited to 'package/libs')
| -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 0af5b4a778..332a151550 100644 --- a/package/libs/wolfssl/Config.in +++ b/package/libs/wolfssl/Config.in @@ -72,7 +72,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 |