public inbox for b43-dev@lists.infradead.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: b43-dev@lists.infradead.org
Subject: Problem with BCM4312 802.11b/g [14e4:4315]
Date: Sat, 21 Aug 2010 13:04:02 -0500	[thread overview]
Message-ID: <4C701512.7020807@lwfinger.net> (raw)
In-Reply-To: <20100821194610.e91ce1fd.cyrille@cbiot.fr>

On 08/21/2010 12:46 PM, Cyrille wrote:
> 
> Thanx !
> 
>> You should put it in b43, not b43-open - b43-open is only for
>> OpenFWWF. (It is not actually "specific to BLAG" - all distros can use
>> it to house OpenFWWF.) And OpenFWWF doesn't support LP-PHY.
> 
> 
> but even with b43 i had same errors.
> 
> 
> I try this http://wireless.kernel.org/en/users/Drivers/b43#device_firmware_installation
> (Section : You are using the b43 driver with an LP-PHY card (e.g. BCM4312))
> but don't work.
> 
> 
> What method recommends you to install this driver?

If you want to use open software for everything, there is no way to operate the
BCM4312 802.11b/g card with a PCI ID of 14e4:4315. The open-source driver b43
needs the firmware extracted with fwcutter, and that firmware is not open
source. The Broadcom hybrid driver is the only other option; however, it is
worse as the driver code and the firmware are both closed source.

If you want to use the card, you will need to find a way to relax the
restriction on closed-source firmware or find another distro.

I do not like the idea of having to use closed-source firmware, but at least it
cannot cause your kernel to go crazy and destroy your file system the way a
closed-source driver could.

Larry

  reply	other threads:[~2010-08-21 18:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-21 17:31 Problem with BCM4312 802.11b/g [14e4:4315] Cyrille
2010-08-21 17:38 ` Gábor Stefanik
2010-08-21 17:46   ` Cyrille
2010-08-21 18:04     ` Larry Finger [this message]
2010-08-21 20:19       ` Gábor Stefanik

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=4C701512.7020807@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=b43-dev@lists.infradead.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