From: Pavel Roskin <proski@gnu.org>
To: "John W. Linville" <linville@tuxdriver.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:23:43 -0400 [thread overview]
Message-ID: <1176344623.21564.46.camel@dv> (raw)
In-Reply-To: <20070412012051.GC3473@tuxdriver.com>
On Wed, 2007-04-11 at 21:20 -0400, John W. Linville wrote:
> On Wed, Apr 11, 2007 at 07:01:06PM -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.
>
> Since the two drivers use different firmware and the (currently)
> softmac-based driver will evolve into bcm4301 with support for older
> hardware, I'd prefer to leave this one out.
It's possible to bind and unbind drivers, so having two drivers for the
same hardware is not a problem per se.
The problem is that such configuration won't compile as it stands now.
It can be fixed by massive renaming of the symbols in one of the
drivers, but I'm not sure we settled on a specific name. I suggested
bcm4301, which was well received, but it sound like it won't happen
until bcm43xx_mac80211 matures.
If "bcm4301" prefix is too confusing or "humiliating" for the
softmac-based driver, we could consider something more acceptable in the
short term, like bcm4k, broadcom, bcom, brcm (Broadcom's stock ticker),
bcm43sm (after softmac), bcmwifi, bcmw, bcw (just to amuse Theo) and so
on.
If the symbols are not renamed, we need some protection in Kconfig, or
we'll fail "make allyesconfig".
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2007-04-12 2:23 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
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 [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=1176344623.21564.46.camel@dv \
--to=proski@gnu.org \
--cc=flamingice@sourmilk.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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).