From: "John W. Linville" <linville@tuxdriver.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Francis Moreau <francis.moro@gmail.com>,
Arend van Spriel <arend@broadcom.com>,
linux-wireless@vger.kernel.org, gregkh@suse.de
Subject: Re: About the patch: "staging: brcm80211: only enable brcmsmac if bcma is not set"
Date: Tue, 13 Sep 2011 13:44:44 -0400 [thread overview]
Message-ID: <20110913174444.GG11772@tuxdriver.com> (raw)
In-Reply-To: <CACna6rwQ60viPGssWzBzgtVGBq1xu+AOxb0fqfRq4NaJFcmP=w@mail.gmail.com>
On Mon, Sep 12, 2011 at 11:27:20PM +0200, Rafał Miłecki wrote:
> The problem is that brcmsmac duplicates code present in the bcma
> driver. It doesn't use bcma bus architecture.
>
> The real solution is to add bcma driver support in brcmsmac and ssb
> driver support in brcmfmac. Then you can always use bcma and:
> 1) If b43 will load and detect unsupported PHY, it will release the BCMA's core
> 2) brcmsmac will be loaded to let it support the core
We are going to have to find a way to get brcmsmac into the
wireless-next tree to make it feasible for the Broadcom guys to get
bcma support into that driver. Do you agree?
We could move it under the drivers/net/wireless tree. Or, maybe I
could negotiate with Greg to keep it under the drivers/staging tree
but to let me manage it under wireless-next. Or...? Do you have
any thoughts on this?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2011-09-13 17:45 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 8:46 About the patch: "staging: brcm80211: only enable brcmsmac if bcma is not set" Francis Moreau
2011-09-12 21:27 ` Rafał Miłecki
2011-09-13 7:03 ` Francis Moreau
2011-09-13 13:28 ` John W. Linville
2011-09-13 13:37 ` Francis Moreau
2011-09-13 13:44 ` John W. Linville
2011-09-13 20:25 ` Rafał Miłecki
2011-09-14 6:53 ` Francis Moreau
2011-09-14 9:27 ` Arend Van Spriel
2011-09-14 9:11 ` Arend Van Spriel
2011-09-14 9:15 ` Francis Moreau
2011-09-16 7:29 ` Rafał Miłecki
2011-09-13 17:44 ` John W. Linville [this message]
2011-09-13 18:44 ` Larry Finger
2011-09-13 19:10 ` John W. Linville
2011-09-13 20:23 ` Rafał Miłecki
2011-09-14 8:42 ` Greg KH
2011-09-16 10:43 ` Rafał Miłecki
2011-09-16 10:52 ` Arend Van Spriel
2011-09-16 10:55 ` Rafał Miłecki
2011-09-16 11:13 ` Arend van Spriel
2011-09-16 11:20 ` Rafał Miłecki
2011-09-16 11:25 ` Arend van Spriel
2011-09-16 11:34 ` Rafał Miłecki
2011-09-14 9:23 ` Arend Van Spriel
2011-09-14 20:18 ` Rafał Miłecki
2011-09-15 11:53 ` Arend van Spriel
2012-01-11 11:40 ` Francis Moreau
2012-01-11 12:24 ` Arend van Spriel
2012-01-11 13:13 ` Francis Moreau
2012-01-11 14:26 ` Arend van Spriel
2012-01-11 14:30 ` Francis Moreau
2012-01-11 15:41 ` Francis Moreau
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=20110913174444.GG11772@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=arend@broadcom.com \
--cc=francis.moro@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.com \
/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).