From: "John W. Linville" <linville@tuxdriver.com>
To: Francis Moreau <francis.moro@gmail.com>
Cc: "Rafał Miłecki" <zajec5@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 09:44:06 -0400 [thread overview]
Message-ID: <20110913134406.GD11772@tuxdriver.com> (raw)
In-Reply-To: <CAC9WiBjOj9+HmprcdKhfj5Y=SpNoKQj=wZfBJzR7fpx9OA+1hQ@mail.gmail.com>
On Tue, Sep 13, 2011 at 03:37:12PM +0200, Francis Moreau wrote:
> On Tue, Sep 13, 2011 at 3:28 PM, John W. Linville
> <linville@tuxdriver.com> wrote:
> > On Tue, Sep 13, 2011 at 09:03:13AM +0200, Francis Moreau wrote:
> >> 2011/9/12 Rafał Miłecki <zajec5@gmail.com>:
> >
> >> > 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
> >> >
> >>
> >> Thanks for the description.
> >>
> >> But what should be done for the time being (3.1-rc5) ?
> >
> > Turn-off CONFIG_B43_BCMA.
> >
>
> Does the b43/bcma driver support some cards that the brcmsmac one doesn't ?
Not any BCMA-based ones.
--
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 13: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 [this message]
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
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=20110913134406.GD11772@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.