[OpenWrt-Devel] AES module vs builtin

[Cristian Morales Vega]

target/linux/generic/config-* has "CONFIG_CRYPTO_AES=y".
But package/kernel/linux/modules/crypto.mk still defines a
kmod-crypto-aes package which just contains a file in /etc/modules.d/
trying to load a module which doesn't exist.

Not sure how the config files in target/linux/generic files are
created... Should kmod-crypto-aes be removed, or is
"CONFIG_CRYPTO_AES=y" what shouldn't be there?


Also, it's a bit worrisome that there was no build failure since the
kmod-crypto-aes package description defines
FILES:=$(LINUX_DIR)/crypto/aes_generic.ko
and the file doesn't exist.
There is an "OpenWRT build system expert" around? Otherwise I will try
to take a look.
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel