From: drwho@infidigm.net
To: "Hauke Mehrtens" <hauke@hauke-m.de>
Cc: backports@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: mac80211 menu option missing in backports using kernel with imx_v6_v7_defconfig
Date: Thu, 26 Jun 2014 16:57:22 -0400 [thread overview]
Message-ID: <4ac8f03450ae2022eef8615c04ce6221.squirrel@www.infidigm.net> (raw)
In-Reply-To: <53AC8517.5040806@hauke-m.de>
>> when I run the backports menuconfig mac80211 is hidden....
>> make menuconfig
>> CROSS_COMPILE=/home/xxx/gcc-linaro-arm-linux-gnueabi-2012.04-20120426_linux/bin/arm-linux-gnueabi-
>> ARCH=arm KLIB_BUILD=/home/xxx/imx_linux-3.10/ KLIB=~/home/xxx/rootfs/
>>
>> Searching for mac80211 in backport's menuconfig shows its dependences
>> are met
>> Symbol: MAC80211 [=n]
>> Type : tristate
>> Prompt: Generic IEEE 802.11 Networking Stack (mac80211)
>> Defined at net/mac80211/Kconfig:1
>> Depends on: m && <choice> && CFG80211 [=m] && CRYPTO [=y] &&
>> CRYPTO_ARC4 && CRYPTO_AES [=y] && CRYPTO_CCM && CRC32 [=y]
>> Selects: BACKPORT_AVERAGE [=n]
>>
>> If I point backports to an x86 kernel mac80211 magically appears
>> make menuconfig KLIB_BUILD=/home/xxx/x86_linux-3.10/
>> KLIB=/home/xxx/rootfs/
>>
>> Something in the imx_v6_v7_defconfig making backports unhappy?
>> backports
>> broken? Am I missing something for the cross compile?
>>
>> using backports-3.13.2-1
>>
>> Jon
>
> Have you set CONFIG_CRYPTO_CCM in your kernel config? This is needed for
> mac80211 in backports.
>
> Hauke
Enabling crypto_ccm and crypto_arc4 in the kernel fixed it. Thanks. I
guess I was looking for [=n] and didn't even see they were disabled.
Jon
prev parent reply other threads:[~2014-06-26 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 19:23 mac80211 menu option missing in backports using kernel with imx_v6_v7_defconfig drwho
2014-06-26 20:39 ` Hauke Mehrtens
2014-06-26 20:57 ` drwho [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ac8f03450ae2022eef8615c04ce6221.squirrel@www.infidigm.net \
--to=drwho@infidigm.net \
--cc=backports@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox