From: Sid Boyce <sboyce@blueyonder.co.uk>
To: linux-omap@vger.kernel.org
Subject: Re: rt2x00 support not available for beagleboard
Date: Fri, 08 Jan 2010 04:18:29 +0000 [thread overview]
Message-ID: <4B46B215.10302@blueyonder.co.uk> (raw)
In-Reply-To: <4B4662DC.9000500@blueyonder.co.uk>
On 07/01/10 22:40, Sid Boyce wrote:
> That's the same on all recent kernels.
> # grep RT2X00 arch/arm/configs/omap3_beagle_defconfig
> #
> # grep RT2X00 arch/arm/configs/*
> arch/arm/configs/eseries_pxa_defconfig:# CONFIG_RT2X00 is not set
> arch/arm/configs/igep0020_defconfig:CONFIG_RT2X00=m
> arch/arm/configs/igep0020_defconfig:CONFIG_RT2X00_LIB_USB=m
> arch/arm/configs/igep0020_defconfig:CONFIG_RT2X00_LIB=m
> arch/arm/configs/igep0020_defconfig:CONFIG_RT2X00_LIB_HT=y
> arch/arm/configs/igep0020_defconfig:CONFIG_RT2X00_LIB_FIRMWARE=y
> arch/arm/configs/igep0020_defconfig:CONFIG_RT2X00_LIB_CRYPTO=y
> arch/arm/configs/igep0020_defconfig:# CONFIG_RT2X00_DEBUG is not set
> arch/arm/configs/kirkwood_defconfig:# CONFIG_RT2X00 is not set
> arch/arm/configs/mini2440_defconfig:# CONFIG_RT2X00 is not set
> arch/arm/configs/omap3_defconfig:# CONFIG_RT2X00 is not set
> arch/arm/configs/omap3_touchbook_defconfig:# CONFIG_RT2X00 is not set
> arch/arm/configs/overo_defconfig:# CONFIG_RT2X00 is not set
> arch/arm/configs/rx51_defconfig:# CONFIG_RT2X00 is not set
> arch/arm/configs/zeus_defconfig:CONFIG_RT2X00=m
> arch/arm/configs/zeus_defconfig:CONFIG_RT2X00_LIB_USB=m
> arch/arm/configs/zeus_defconfig:CONFIG_RT2X00_LIB=m
> arch/arm/configs/zeus_defconfig:CONFIG_RT2X00_LIB_FIRMWARE=y
> arch/arm/configs/zeus_defconfig:CONFIG_RT2X00_LIB_CRYPTO=y
> arch/arm/configs/zeus_defconfig:CONFIG_RT2X00_LIB_LEDS=y
> arch/arm/configs/zeus_defconfig:# CONFIG_RT2X00_DEBUG is not set
> Regards
> Sid.
OK, it seems I need to use omap3_defconfig.
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:[~2010-01-08 4:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 22:40 rt2x00 support not available for beagleboard Sid Boyce
2010-01-08 4:18 ` 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=4B46B215.10302@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