From: Dan Williams <dcbw@redhat.com>
To: Michael Wu <flamingice@sourmilk.net>
Cc: Michael Buesch <mb@bu3sch.de>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] bcm43xx: Hide if bcm43xx-mac80211 is builtin
Date: Wed, 11 Apr 2007 20:01:10 -0400 [thread overview]
Message-ID: <1176336070.1298.17.camel@localhost.localdomain> (raw)
In-Reply-To: <200704111901.06403.flamingice@sourmilk.net>
On Wed, 2007-04-11 at 19:01 -0400, Michael Wu wrote:
> bcm43xx: Hide if bcm43xx-mac80211 is builtin
>
> From: Michael Wu <flamingice@sourmilk.net>
>
> This prevents users from compiling bcm43xx (softmac) and bcm43xx-mac80211
> into the kernel at the same time. In the case that it is attempted, make
> bcm43xx (softmac) not build.
What kernel version is this targetted at? Have the mac80211 bits
reached feature parity with the softmac bits? I'm still hearing quite a
few reports of mac80211 being flaky WRT WEXT implementation and
compatibility. I don't necessarily object, I just want to make sure
that when this patch hits released kernels, that the mac80211 port is in
the same or better shape than the softmac one.
Dan
> Signed-off-by: Michael Wu <flamingice@sourmilk.net>
> ---
>
> drivers/net/wireless/bcm43xx/Kconfig | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/net/wireless/bcm43xx/Kconfig b/drivers/net/wireless/bcm43xx/Kconfig
> index ce397e4..f69510d 100644
> --- a/drivers/net/wireless/bcm43xx/Kconfig
> +++ b/drivers/net/wireless/bcm43xx/Kconfig
> @@ -1,6 +1,7 @@
> config BCM43XX
> tristate "Broadcom BCM43xx wireless support"
> depends on PCI && IEEE80211 && IEEE80211_SOFTMAC && WLAN_80211 && EXPERIMENTAL
> + depends on BCM43XX_MAC80211 != 'y'
> select WIRELESS_EXT
> select FW_LOADER
> select HW_RANDOM
next prev parent reply other threads:[~2007-04-11 23:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 23:01 [PATCH] bcm43xx: Hide if bcm43xx-mac80211 is builtin Michael Wu
2007-04-12 0:01 ` Dan Williams [this message]
2007-04-12 3:42 ` Larry Finger
2007-04-12 1:20 ` John W. Linville
2007-04-12 1:55 ` Michael Wu
2007-04-12 23:56 ` John W. Linville
2007-04-12 2:23 ` Pavel Roskin
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=1176336070.1298.17.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=flamingice@sourmilk.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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;
as well as URLs for NNTP newsgroup(s).