From: Larry Finger <Larry.Finger@lwfinger.net>
To: Jeff Burdges <burdges@gnunet.org>
Cc: b43-dev@lists.infradead.org,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Is b43-fwcutter an option for a BCM4360?
Date: Mon, 15 Jun 2015 15:17:31 -0500 [thread overview]
Message-ID: <557F32DB.5030001@lwfinger.net> (raw)
In-Reply-To: <1434398914.2004.11.camel@gnunet.org>
On 06/15/2015 03:08 PM, Jeff Burdges wrote:
>
> I've a MacBook Air 6.2 with a Broadcom BCM4360 802.11ac adapter
> [14e4:43a0] (rev 03). It's apparently not supported according to :
>
> https://wireless.wiki.kernel.org/en/users/Drivers/b43
>
> I imagine there is no point in playing around with extracting the
> firmware from the drivers on Yosemite or Mavericks using b43-fwcutter,
> right?
>
> Thanks,
> Jeff
>
> p.s. I've already tried using the proprietary wl driver, but it crashes
> lots on WPA2 and maybe WPA networks. I mentioned the error messages
> here :
> https://unix.stackexchange.com/questions/209280/broadcom-wireless-driver-source-vs-dkms
If the wiki says that it is unsupported, then that is correct. That list is kept
up to date.
Firmware is not your problem. It is the basic drivers not supporting that new
hardware. Using b43-fwcutter will do no good.
I'm sure that you are aware that only Broadcom can debug the proprietary driver.
I have added the wireless mailing list to get additional exposure.
Larry
WARNING: multiple messages have this Message-ID (diff)
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Jeff Burdges <burdges@gnunet.org>
Cc: b43-dev@lists.infradead.org,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Is b43-fwcutter an option for a BCM4360?
Date: Mon, 15 Jun 2015 15:17:31 -0500 [thread overview]
Message-ID: <557F32DB.5030001@lwfinger.net> (raw)
In-Reply-To: <1434398914.2004.11.camel@gnunet.org>
On 06/15/2015 03:08 PM, Jeff Burdges wrote:
>
> I've a MacBook Air 6.2 with a Broadcom BCM4360 802.11ac adapter
> [14e4:43a0] (rev 03). It's apparently not supported according to :
>
> https://wireless.wiki.kernel.org/en/users/Drivers/b43
>
> I imagine there is no point in playing around with extracting the
> firmware from the drivers on Yosemite or Mavericks using b43-fwcutter,
> right?
>
> Thanks,
> Jeff
>
> p.s. I've already tried using the proprietary wl driver, but it crashes
> lots on WPA2 and maybe WPA networks. I mentioned the error messages
> here :
> https://unix.stackexchange.com/questions/209280/broadcom-wireless-driver-source-vs-dkms
If the wiki says that it is unsupported, then that is correct. That list is kept
up to date.
Firmware is not your problem. It is the basic drivers not supporting that new
hardware. Using b43-fwcutter will do no good.
I'm sure that you are aware that only Broadcom can debug the proprietary driver.
I have added the wireless mailing list to get additional exposure.
Larry
next prev parent reply other threads:[~2015-06-15 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 20:08 Is b43-fwcutter an option for a BCM4360? Jeff Burdges
2015-06-15 20:17 ` Larry Finger [this message]
2015-06-15 20:17 ` Larry Finger
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=557F32DB.5030001@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=burdges@gnunet.org \
--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 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.