From: Sid Boyce <sboyce@blueyonder.co.uk>
To: linux-omap@vger.kernel.org
Subject: Re: linux-omap-2.6 does not allow configuring rt2xx
Date: Wed, 11 Nov 2009 17:19:37 +0000 [thread overview]
Message-ID: <4AFAF229.1050907@blueyonder.co.uk> (raw)
In-Reply-To: <4AFA5F05.7060201@compulab.co.il>
On 11/11/09 06:51, Mike Rapoport wrote:
>
>
> Sid Boyce wrote:
>> Spotted over the last few days.
>> "make ARCH=arm CROSS_COMPILE=/opt/arm-2009q1/bin/arm-none-linux/gnueabi-
>> omap3_beagle_defconfig", then xconfig/menuconfig/config, the option
>> never shows up.
>
> Have you tried enabling cfg80211 and mac80211 in "Networking support -> Wireless"?
>
>> Regards
>> Sid.
>
Thanks, that did it. I thought I had tried those earlier.
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
prev parent reply other threads:[~2009-11-11 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 21:35 linux-omap-2.6 does not allow configuring rt2xx Sid Boyce
2009-11-11 6:51 ` Mike Rapoport
2009-11-11 17:19 ` Sid Boyce [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=4AFAF229.1050907@blueyonder.co.uk \
--to=sboyce@blueyonder.co.uk \
--cc=linux-omap@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