linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: Chester <somethingsome2000@gmail.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: brcmsmac driver is ghost in 3.3
Date: Tue, 3 Apr 2012 20:15:45 +0200	[thread overview]
Message-ID: <4F7B3E51.5020403@broadcom.com> (raw)
In-Reply-To: <CAAE6i0gVsYnpa82FrKCNV5sszr38But4Og6D20cv4r8BF3Tv=Q@mail.gmail.com>

On 04/03/2012 07:05 AM, Chester wrote:
> And this is when I curse at all the google results that say "blacklist
> bcma" ... brcmsmac DEPENDS on bcma /facepalms and goes to sleep..

brcmsmac changed basically from a pci device driver to a bcma device 
driver. So before 3.3 it was good to blacklist bcma to avoid it from 
claiming the device away from brcmsmac.

For 3.3, brcmsmac relies on bcma indeed.

Gr. AvS


      reply	other threads:[~2012-04-03 18:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-03  4:50 brcmsmac driver is ghost in 3.3 Chester
2012-04-03  5:05 ` Chester
2012-04-03 18:15   ` Arend van Spriel [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=4F7B3E51.5020403@broadcom.com \
    --to=arend@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=somethingsome2000@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).