From: Larry Finger <larry.finger@lwfinger.net>
To: Dan Williams <dcbw@redhat.com>
Cc: Michael Wu <flamingice@sourmilk.net>,
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 22:42:54 -0500 [thread overview]
Message-ID: <461DAABE.1060607@lwfinger.net> (raw)
In-Reply-To: <1176336070.1298.17.camel@localhost.localdomain>
Dan Williams wrote:
> 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.
This is aimed at Linville's wireless-dev and the -mm tree where both softmac and mac80211 versions
coexist.
At the moment, mac80211 is not in as good shape as softmac, and a date for its addition to mainline
has not been set.
Larry
next prev parent reply other threads:[~2007-04-12 3:41 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
2007-04-12 3:42 ` Larry Finger [this message]
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=461DAABE.1060607@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=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).