From: "Henry Ptasinski" <henryp@broadcom.com>
To: dwmw2@infradead.org
Cc: linux-wireless@vger.kernel.org, devel@linuxdriverproject.org,
henryp@broadcom.com, brudley@broadcom.com, arend@broadcom.com,
rvossen@broadcom.com
Subject: [PATCH 0/3] linux-firmware: Updated firmware and new license for brcm firmware
Date: Tue, 5 Apr 2011 07:58:39 -0700 [thread overview]
Message-ID: <1302015522-20601-1-git-send-email-henryp@broadcom.com> (raw)
David,
Here's a short patch series for the linux-firmware repo, including a much
shorter license, some file renaming to get the firmware repo in synch with the
firmware names expected by the drivers, and a new version of firmware which
should resolve a lot of the stability issues people are seeing with the
brcmsmac driver. Please apply them to the linux-firmware repo.
Thanks,
---
Henry Ptasinski
henryp@broadcom.com
Henry Ptasinski (3):
linux-firmware: Simplified license file for brcm firmware
linux-firmware: Removed codeversion from brcm firmware filenames.
linux-firmware: updated firmware for BCM4313, BCM43224, and BCM43225
chips
LICENCE.broadcom_bcm43xx | 262 +++++---------------
WHENCE | 12 +-
...llmac-4-218-248-5.bin => bcm4329-fullmac-4.bin} | Bin 269595 -> 269595 bytes
...llmac-4-218-248-5.txt => bcm4329-fullmac-4.txt} | 0
brcm/{bcm43xx-0-610-809-0.fw => bcm43xx-0.fw} | Bin 97376 -> 97344 bytes
brcm/bcm43xx_hdr-0-610-809-0.fw | Bin 180 -> 0 bytes
brcm/bcm43xx_hdr-0.fw | Bin 0 -> 180 bytes
7 files changed, 67 insertions(+), 207 deletions(-)
rename brcm/{bcm4329-fullmac-4-218-248-5.bin => bcm4329-fullmac-4.bin} (100%)
rename brcm/{bcm4329-fullmac-4-218-248-5.txt => bcm4329-fullmac-4.txt} (100%)
rename brcm/{bcm43xx-0-610-809-0.fw => bcm43xx-0.fw} (74%)
delete mode 100644 brcm/bcm43xx_hdr-0-610-809-0.fw
create mode 100644 brcm/bcm43xx_hdr-0.fw
next reply other threads:[~2011-04-05 14:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 14:58 Henry Ptasinski [this message]
2011-04-05 14:58 ` [PATCH 2/3] linux-firmware: Removed codeversion from brcm firmware filenames Henry Ptasinski
2011-04-05 15:34 ` Larry Finger
2011-04-05 17:51 ` Henry Ptasinski
2011-04-05 19:00 ` Larry Finger
2011-04-05 19:29 ` Greg KH
2011-04-05 20:33 ` Larry Finger
2011-04-05 20:42 ` Greg KH
2011-04-05 14:58 ` [PATCH 3/3] linux-firmware: updated firmware for BCM4313, BCM43224, and BCM43225 chips Henry Ptasinski
2011-04-21 18:30 ` [PATCH 0/3] linux-firmware: brcm firmware fixes Henry Ptasinski
2011-04-21 18:30 ` [PATCH 1/3] linux-firmware: Simplified license file for brcm firmware Henry Ptasinski
2011-04-21 18:30 ` [PATCH 2/3] linux-firmware: Removed codeversion from brcm firmware filenames Henry Ptasinski
2011-04-21 18:30 ` [PATCH 3/3] linux-firmware: updated firmware for BCM4313, BCM43224, and BCM43225 chips Henry Ptasinski
2011-04-07 21:15 ` [PATCH 0/3] linux-firmware: Updated firmware and new license for brcm firmware Henry Ptasinski
2011-04-08 6:41 ` Johannes Berg
2011-04-08 14:49 ` Henry Ptasinski
2011-04-08 14:51 ` [PATCH 1/3] linux-firmware: Simplified license file " Henry Ptasinski
2011-04-08 14:51 ` [PATCH 2/3] linux-firmware: Removed codeversion from brcm firmware filenames Henry Ptasinski
2011-04-08 14:51 ` [PATCH 3/3] linux-firmware: updated firmware for BCM4313, BCM43224, and BCM43225 chips Henry Ptasinski
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=1302015522-20601-1-git-send-email-henryp@broadcom.com \
--to=henryp@broadcom.com \
--cc=arend@broadcom.com \
--cc=brudley@broadcom.com \
--cc=devel@linuxdriverproject.org \
--cc=dwmw2@infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rvossen@broadcom.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).