From: Larry Finger <Larry.Finger@lwfinger.net>
To: Henry Ptasinski <henryp@broadcom.com>, dwmw2@infradead.org
Cc: linux-wireless@vger.kernel.org, devel@linuxdriverproject.org,
brudley@broadcom.com, arend@broadcom.com, rvossen@broadcom.com
Subject: Re: [PATCH 2/3] linux-firmware: Removed codeversion from brcm firmware filenames.
Date: Tue, 05 Apr 2011 10:34:17 -0500 [thread overview]
Message-ID: <4D9B3679.10509@lwfinger.net> (raw)
In-Reply-To: <1302015522-20601-3-git-send-email-henryp@broadcom.com>
On 04/05/2011 09:58 AM, Henry Ptasinski wrote:
> The basename-apiversion-codeversion construction for firmware filenames is not
> used by most other firmware files, adds complexity, and is not providing any
> value. Renamed the firmware files using just basename-apiversion and fixed
> WHENCE to have correct names and path to these files.
> ---
> 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 -> 97376 bytes
> ...bcm43xx_hdr-0-610-809-0.fw => bcm43xx_hdr-0.fw} | Bin 180 -> 180 bytes
> 5 files changed, 6 insertions(+), 6 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} (100%)
> rename brcm/{bcm43xx_hdr-0-610-809-0.fw => bcm43xx_hdr-0.fw} (100%)
>
> diff --git a/WHENCE b/WHENCE
> index 6632b85..c81a2b4 100644
> --- a/WHENCE
> +++ b/WHENCE
> @@ -1433,19 +1433,19 @@ Licence:
>
> --------------------------------------------------------------------------
>
> -Driver: brcm80211 - Broadcom 802.11n wireless LAN driver.
> +Driver: brcmsmac - Broadcom 802.11n softmac wireless LAN driver.
>
> -File: brcm/bcm43xx-0-610-809-0.fw
> -File: brcm/bcm43xx_hdr-0-610-809-0.fw
> +File: brcm/bcm43xx-0.fw
> +File: brcm/bcm43xx_hdr-0.fw
>
> Licence: Redistributable. See LICENCE.broadcom_bcm43xx for details.
>
> --------------------------------------------------------------------------
>
> -Driver: brcm80211 - Broadcom 802.11n wireless LAN driver.
> +Driver: brcmfmac - Broadcom 802.11n fullmac wireless LAN driver.
>
> -File: bcm4329-fullmac-4-218-248-5.bin
> -File: bcm4329-fullmac-4-218-248-5.txt
> +File: brcm/bcm4329-fullmac-4.bin
> +File: brcm/bcm4329-fullmac-4.txt
>
> Licence: Redistributable. See LICENCE.broadcom_bcm43xx for details.
>
> diff --git a/brcm/bcm4329-fullmac-4-218-248-5.txt b/brcm/bcm4329-fullmac-4.txt
> similarity index 100%
> rename from brcm/bcm4329-fullmac-4-218-248-5.txt
> rename to brcm/bcm4329-fullmac-4.txt
Given all the problems we in the b43 community have had with Broadcom firmware,
I certainly applaud every instance where the company makes firmware freely
available and redistributable.
I also endorse removing the version number from the firmware name; however, I
see a fundamental flaw in the present submission. Both brcmsmac and its
predecessor brcm80211 have been included in mainline and compat-wireless, have
been widely distributed, and have a number of users. This change will break the
system of every one of them - including mine. My proposed solution is to do the
rename as done in this patch, but also include links to the new name from every
name used in any distributed version. After approximately two years, the links
can be removed, but they are needed now.
The brcmsmac/brcm80211 driver already has a PR problem due to the instabilities
and the system lockups. Adding this kind of system breakage would do even more
damage to its reputation.
Larry
next prev parent reply other threads:[~2011-04-05 15:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 14:58 [PATCH 0/3] linux-firmware: Updated firmware and new license for brcm firmware Henry Ptasinski
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 [this message]
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=4D9B3679.10509@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=arend@broadcom.com \
--cc=brudley@broadcom.com \
--cc=devel@linuxdriverproject.org \
--cc=dwmw2@infradead.org \
--cc=henryp@broadcom.com \
--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 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.