Offending module: ieee80211_crypto_ccmp.c Error Message: ieee80211_crypto_ccmp.c:290: error: invalid use of undefined type 'struct page' ieee80211_crypto_ccmp.c:294: error: invalid use of undefined type 'struct page' Code reference: static void rijndael_encrypt(struct crypto_tfm *tfm, const void *src, void *dst) { { struct scatterlist sg_src; struct scatterlist sg_dst; -----> sg_src.page = virt_to_page(src); <---------------- ERROR sg_src.offset = offset_in_page(src); sg_src.length = AES_BLOCK_LEN; -----> sg_dst.page = virt_to_page(dst); <---------------- ERROR sg_dst.offset = offset_in_page(dst); sg_dst.length = AES_BLOCK_LEN; crypto_cipher_encrypt(tfm, &sg_dst, &sg_src, AES_BLOCK_LEN); } I believe this is not the only file with the problem (i assume dot1x would be similairly affected) Additional Problems: The Sandbox violation also exists in this version (there is a seperate bug for this) The header file "config.h" has been removed from /usr/src/linux/include/linux/config.h, but is required by madwifi-old. (should be fixed as this is a stub header file for <linux/autoconf.h>)
care to provide a patch for the problem? I dont think anyone else cares enough to write one.
Created attachment 109847 [details, diff] Patch to help madwifi-old compile with kernel 2.6.20
sorry, does not apply here. Can you please give an ebuild for applying it too?
Created attachment 110043 [details] Apply it manualy Hi, This is corrected version. Apply it manually by moving into the madwifi-old work-dir: cd /var/tmp/portage/net-wireless/madwifi-old-0.0.1417.20060128/work/madwifi-old-r1417-20060128/ madwifi-old-r1417-20060128 # patch -p0 < [path to where you saved ieee80211_crypto_ccmp.patch] The driver will then compile, however... it is unstable. I think it's best to move to madwifi-ng if possible. (I'll give it another try.. though it didn't work for me at first)
thanks, I committed this.
I get a failed patch error for patch 2.6.20 when trying to emerge madwifi-old. Is that related to this?
seems I got the wrong patch, should work now, thanks.
*** Bug 168407 has been marked as a duplicate of this bug. ***