06-08-2018, 02:56 AM
The Rock64 is not using an Intel CPU or the x86_64 architecture and does therefore not understand the Intel AES-NI instructions.
The rockchip rk3328 SoC is an aarch64 architecture, often also called arm64 or armv8.
Luckily the armv8 instruction set contains an equivalent offloading mechanism called "Cryptography extensions" (http://infocenter.arm.com/help/topic/com...DEBAF.html).
So whatever you are trying to accomplish, you will have to use the offloading mechanisms your hardware actually supports.
In ayufans latest kernel the relevant options seem to be enabled:
CONFIG_CRYPTO_HW=y
CONFIG_ARM64_CRYPTO=y
CONFIG_CRYPTO_SHA1_ARM64_CE=y
CONFIG_CRYPTO_SHA2_ARM64_CE=y
CONFIG_CRYPTO_GHASH_ARM64_CE=y
CONFIG_CRYPTO_AES_ARM64_CE=y
CONFIG_CRYPTO_AES_ARM64_CE_CCM=y
CONFIG_CRYPTO_AES_ARM64_CE_BLK=y
The rockchip rk3328 SoC is an aarch64 architecture, often also called arm64 or armv8.
Luckily the armv8 instruction set contains an equivalent offloading mechanism called "Cryptography extensions" (http://infocenter.arm.com/help/topic/com...DEBAF.html).
So whatever you are trying to accomplish, you will have to use the offloading mechanisms your hardware actually supports.
In ayufans latest kernel the relevant options seem to be enabled:
CONFIG_CRYPTO_HW=y
CONFIG_ARM64_CRYPTO=y
CONFIG_CRYPTO_SHA1_ARM64_CE=y
CONFIG_CRYPTO_SHA2_ARM64_CE=y
CONFIG_CRYPTO_GHASH_ARM64_CE=y
CONFIG_CRYPTO_AES_ARM64_CE=y
CONFIG_CRYPTO_AES_ARM64_CE_CCM=y
CONFIG_CRYPTO_AES_ARM64_CE_BLK=y
