From: "Michael Büsch" <m@bues.ch>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org,
brcm80211-dev-list@broadcom.com
Subject: [RFC] b43-fwcutter: Add support for generating a fw for brcmsmac
Date: Sun, 23 Sep 2012 21:39:34 +0200 [thread overview]
Message-ID: <20120923213934.4da339ae@milhouse> (raw)
In-Reply-To: <1348425562-30730-1-git-send-email-hauke@hauke-m.de>
On Sun, 23 Sep 2012 20:39:22 +0200
Hauke Mehrtens <hauke@hauke-m.de> wrote:
> The normal firmware for brcmsmac is available in the linux-firmware git
> repository, but this firmware does not work on a bcm4716 devices with a
> ieee80211 core rev 16. When using a firmware extracted from the
> proprietary Broadcom driver the device works with brcmsmac.
>
> I tested a firmware version 666.2 extracted from the proprietary driver
> with brcmsmac on a BCM4716 and a BCM43224 and haven't seen any
> problems. The interface between the firmware and the driver changed
> some times, brcmsmac only support firmware version 598 and newer.
>
> For some entries in the firmware used by brcmsmac, fwcutter has to be
> more extended, so we are adding dummy entires for them in
> brcmsmac_add_dummy_entries(). Currently these entries are not used by
> brcmsmac, but it is checked if they are in the archive.
>
> I would still appreciate if Broadcom could release a firmware with
> support for the ieee80211 core found in the bcm4716.
>
> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
I'm OK with it. Some other comments?
--
Greetings, Michael.
PGP encryption is encouraged / 908D8B0E
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20120923/388c2afb/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: "Michael Büsch" <m@bues.ch>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org,
brcm80211-dev-list@broadcom.com
Subject: Re: [RFC] b43-fwcutter: Add support for generating a fw for brcmsmac
Date: Sun, 23 Sep 2012 21:39:34 +0200 [thread overview]
Message-ID: <20120923213934.4da339ae@milhouse> (raw)
In-Reply-To: <1348425562-30730-1-git-send-email-hauke@hauke-m.de>
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
On Sun, 23 Sep 2012 20:39:22 +0200
Hauke Mehrtens <hauke@hauke-m.de> wrote:
> The normal firmware for brcmsmac is available in the linux-firmware git
> repository, but this firmware does not work on a bcm4716 devices with a
> ieee80211 core rev 16. When using a firmware extracted from the
> proprietary Broadcom driver the device works with brcmsmac.
>
> I tested a firmware version 666.2 extracted from the proprietary driver
> with brcmsmac on a BCM4716 and a BCM43224 and haven't seen any
> problems. The interface between the firmware and the driver changed
> some times, brcmsmac only support firmware version 598 and newer.
>
> For some entries in the firmware used by brcmsmac, fwcutter has to be
> more extended, so we are adding dummy entires for them in
> brcmsmac_add_dummy_entries(). Currently these entries are not used by
> brcmsmac, but it is checked if they are in the archive.
>
> I would still appreciate if Broadcom could release a firmware with
> support for the ieee80211 core found in the bcm4716.
>
> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
I'm OK with it. Some other comments?
--
Greetings, Michael.
PGP encryption is encouraged / 908D8B0E
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-09-23 19:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-23 18:39 [RFC] b43-fwcutter: Add support for generating a fw for brcmsmac Hauke Mehrtens
2012-09-23 19:39 ` Michael Büsch [this message]
2012-09-23 19:39 ` Michael Büsch
2012-09-24 21:09 ` Michael Büsch
2012-09-24 21:09 ` Michael Büsch
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=20120923213934.4da339ae@milhouse \
--to=m@bues.ch \
--cc=b43-dev@lists.infradead.org \
--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 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.