linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Francis Moreau" <francis.moro@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"gregkh@suse.de" <gregkh@suse.de>
Subject: Re: About the patch: "staging: brcm80211: only enable brcmsmac if bcma is not set"
Date: Wed, 11 Jan 2012 13:24:11 +0100	[thread overview]
Message-ID: <4F0D7F6B.5000601@broadcom.com> (raw)
In-Reply-To: <CAC9WiBhVWvvN-yqoYvBoD1uUi0P5e2cBu68Mva99wVxr7W0ibg@mail.gmail.com>

On 01/11/2012 12:40 PM, Francis Moreau wrote:
> Hi,
> 
> This has finally been merged and is part of the 3.2 release.
> 
> So now distros don't ship the brcmsmac driver anymore which is
> basically the only driver which can handle my card.

I am not sure why you come to that conclusion, but I don't know the
criteria that distros use. In hindsight maybe this patch was not needed
because you could use module blacklist instead.

> did you really intend to do that ?
> 
> Thanks

For kernel v3.3 the brcmsmac driver will be using bcma. I had a look and
it turns out b43 is claiming the same bcma cores that brcmsmac claims.
So there you probably need to blacklist b43.

Gr. AvS


  reply	other threads:[~2012-01-11 12:24 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
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 [this message]
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=4F0D7F6B.5000601@broadcom.com \
    --to=arend@broadcom.com \
    --cc=francis.moro@gmail.com \
    --cc=gregkh@suse.de \
    --cc=linux-wireless@vger.kernel.org \
    /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).