Linux wireless drivers development
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: brcm80211-dev-list@broadcom.com, linux-wireless@vger.kernel.org
Subject: Re: How to get BRCM to work?
Date: Mon, 4 Nov 2013 16:07:28 +0300	[thread overview]
Message-ID: <20131104130728.GA20521@mwanda> (raw)
In-Reply-To: <52778D30.6030605@hauke-m.de>

On Mon, Nov 04, 2013 at 01:04:00PM +0100, Hauke Mehrtens wrote:
> On 11/04/2013 12:51 PM, Dan Carpenter wrote:
> > I've been trying to remember the trick to get BRCM to work and I can't
> > remember at all.  I'm using BCM4313.  I've enabled everything with BCMA
> > or BRCM in the config name.
> > 
> > The module loads and the device shows up if I type "ifconfig wlan0" but
> > network manager doesn't see it and wicd doesn't see it.  (These are old
> > versions of nm and wicd).
> > 
> > This used to work under 3.8 but I didn't save my .config...  :(
> 
> Are these old versions of nm and wicd only supporting the deprecated
> WEXT interface? If this is the case you have to set
> CONFIG_CFG80211_WEXT=y in your config.
> 

I have that enabled.

> You also need a firmware for this device /lib/firmware/brcm/bcm43xx-0.fw
> and /lib/firmware/brcm/bcm43xx_hdr-0.fw are needed.

I have the firmware.

> 
> When the device gets detected by brcmsmac, it is probably not a problem
> in the Broadcom driver.
> 
> > I've done a google search and it seems like the broadcom driver is still
> > a complete mess and you need to black list modules and hack everything
> > yourself on a per system basis?  Is that right?  Why can't we fix this
> > so it works?
> 
> When you want to use the property closed source Broadcom driver then you
> have to blacklist the in kernel drivers. When you want to use the in
> kernel drivers, BCM4313 should get detected and the modules should get
> loaded like it is done for every other PCIe device.

I don't have the closed source driver.

I'll do some more testing and get back on this.

regards,
dan carpenter


  reply	other threads:[~2013-11-04 13:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04 11:51 How to get BRCM to work? Dan Carpenter
2013-11-04 12:00 ` Dan Carpenter
2013-11-04 12:04 ` Hauke Mehrtens
2013-11-04 13:07   ` Dan Carpenter [this message]
2013-11-04 15:05     ` Arend van Spriel
2013-11-05 22:25       ` Dan Carpenter
2013-11-06  9:44         ` Arend van Spriel
2013-11-06 12:39           ` Hauke Mehrtens
2013-11-06 13:29             ` Arend van Spriel

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=20131104130728.GA20521@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=brcm80211-dev-list@broadcom.com \
    --cc=hauke@hauke-m.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