Adding new Marvell cryptoengine as some device might use the new one and not the old one.
Signed-off-by: Michal Hrusecky <michal.hruse...@nic.cz> --- package/kernel/linux/modules/crypto.mk | 20 +++++++++++++++++--- 1 file changed, 17 insertions(+), 3 deletions(-) diff --git a/package/kernel/linux/modules/crypto.mk b/package/kernel/linux/modules/crypto.mk index 0acc730..0f37a55 100644 --- a/package/kernel/linux/modules/crypto.mk +++ b/package/kernel/linux/modules/crypto.mk @@ -711,14 +711,28 @@ endef $(eval $(call KernelPackage,crypto-xts)) - define KernelPackage/crypto-mv-cesa - TITLE:=Marvell crypto engine + TITLE:=Old Marvell crypto engine DEPENDS:=+kmod-crypto-manager @TARGET_kirkwood||TARGET_orion||TARGET_mvebu - KCONFIG:=CONFIG_CRYPTO_DEV_MV_CESA + KCONFIG:= \ + CONFIG_CRYPTO_DEV_MV_CESA \ + CONFIG_CRYPTO_HW=y FILES:=$(LINUX_DIR)/drivers/crypto/mv_cesa.ko AUTOLOAD:=$(call AutoLoad,09,mv_cesa) $(call AddDepends/crypto) endef $(eval $(call KernelPackage,crypto-mv-cesa)) + +define KernelPackage/crypto-marvell-cesa + TITLE:=New Marvell crypto engine + DEPENDS:=+kmod-crypto-manager @TARGET_kirkwood||TARGET_orion||TARGET_mvebu + KCONFIG:= \ + CONFIG_CRYPTO_DEV_MARVELL_CESA \ + CONFIG_CRYPTO_HW=y + FILES:=$(LINUX_DIR)/drivers/crypto/marvell/marvell-cesa.ko + AUTOLOAD:=$(call AutoLoad,09,marvell-cesa) + $(call AddDepends/crypto) +endef + +$(eval $(call KernelPackage,crypto-marvell-cesa)) -- 2.8.2 _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
