Thanks Maarten, now kernel compiles again. One of your patches had a typo (COFIG instead of CONFIG), corrected it and recreated it for the latest trunk revision.
Index: package/kernel/modules/crypto.mk =================================================================== --- package/kernel/modules/crypto.mk (revision 27463) +++ package/kernel/modules/crypto.mk (working copy) @@ -41,7 +41,9 @@ define KernelPackage/crypto-hash TITLE:=CryptoAPI hash support - KCONFIG:=CONFIG_CRYPTO_HASH + KCONFIG:= \ + CONFIG_CRYPTO_HASH \ + CONFIG_CRYPTO_HASH2 FILES:=$(LINUX_DIR)/crypto/crypto_hash.ko AUTOLOAD:=$(call AutoLoad,02,crypto_hash) $(call AddDepends/crypto) @@ -447,7 +449,7 @@ define KernelPackage/crypto-mv-cesa TITLE:=Marvell crypto engine - DEPENDS:=+kmod-crypto-manager +kmod-crypto-aes @TARGET_kirkwood||TARGET_orion + DEPENDS:=+kmod-crypto-manager +kmod-crypto-aes +kmod-crypto-sha1 +kmod-crypto-hmac @TARGET_kirkwood||TARGET_orion KCONFIG:=CONFIG_CRYPTO_DEV_MV_CESA FILES:=$(LINUX_DIR)/drivers/crypto/mv_cesa.ko AUTOLOAD:=$(call AutoLoad,09,mv_cesa) But now I run into another issue with ltq-tapi: ... Set the kernel architecture to arm configure: error: The lib_ifxos include directory is not valid! make[3]: *** [/home/maddes/openwrt/trunk/build_dir/linux-orion_generic/drv_tapi-3.13.0/.configured_] Error 1 make[3]: Leaving directory `/home/maddes/openwrt/trunk/package/ltq-tapi' ... Maddes On 04.07.2011 21:52, Maarten Bezemer wrote: > I noticed the same yesterday, but did not get to it to submit the > patches. > > In order to automatically select the kmod-crypto-sha1 and > kmod-crypto-hmac packages the fix-crypto-mv-cesa.patch needs to be > applied > > For some reasons the linux source expects CONFIG_CRYPTO_HASH2 instead > (?) of CONFIG_CRYPTO_HASH. See attached fix-crypto-hash.patch > > Maybe for the crypto-hash patch the CONFIG_CRYPTO_HASH part needs to be > removed? I am not a real Linux kernel developer so I do not know. Having > both at least does not give errors. > > With both patches applied the Orion target builds again without problems > when kmod-mv-cesa is selected > > Greetings, > Maarten > > On Mon, 2011-07-04 at 20:24 +0200, Matthias Buecher / Germany wrote: >> Hi everybody, >> >> I just got back to OpenWrt development after 6 months and recognized >> that the Orion platform doesn't build anymore. >> According to ticket #9209 [1] this happened ~3 months ago. >> Can anybody please help, so I can continue developing some packages for >> my platform. >> >> Thanks in advance >> Maddes >> >> [1] https://dev.openwrt.org/ticket/9209 >> _______________________________________________ >> openwrt-devel mailing list >> openwrt-devel@lists.openwrt.org >> https://lists.openwrt.org/mailman/listinfo/openwrt-devel > > > > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel Matthias "Maddes" Bücher -- http://www.maddes.net/ Home: Earth / Germany / Ruhr-Area
Index: package/kernel/modules/crypto.mk =================================================================== --- package/kernel/modules/crypto.mk (revision 27463) +++ package/kernel/modules/crypto.mk (working copy) @@ -41,7 +41,9 @@ define KernelPackage/crypto-hash TITLE:=CryptoAPI hash support - KCONFIG:=CONFIG_CRYPTO_HASH + KCONFIG:= \ + CONFIG_CRYPTO_HASH \ + CONFIG_CRYPTO_HASH2 FILES:=$(LINUX_DIR)/crypto/crypto_hash.ko AUTOLOAD:=$(call AutoLoad,02,crypto_hash) $(call AddDepends/crypto) @@ -447,7 +449,7 @@ define KernelPackage/crypto-mv-cesa TITLE:=Marvell crypto engine - DEPENDS:=+kmod-crypto-manager +kmod-crypto-aes @TARGET_kirkwood||TARGET_orion + DEPENDS:=+kmod-crypto-manager +kmod-crypto-aes +kmod-crypto-sha1 +kmod-crypto-hmac @TARGET_kirkwood||TARGET_orion KCONFIG:=CONFIG_CRYPTO_DEV_MV_CESA FILES:=$(LINUX_DIR)/drivers/crypto/mv_cesa.ko AUTOLOAD:=$(call AutoLoad,09,mv_cesa)
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
