From: "Henry Ptasinski" <henryp@broadcom.com>
To: "Greg KH" <greg@kroah.com>
Cc: "Nohee Ko" <noheek@broadcom.com>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"Brett Rudley" <brudley@broadcom.com>,
"grundler@google.com" <grundler@google.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"Henry Ptasinski" <henryp@broadcom.com>
Subject: Re: Subject: [PATCH v2] staging: brcm80211: brcmfmac: Removed codeversion from firmware filenames.
Date: Thu, 21 Oct 2010 11:37:53 -0700 [thread overview]
Message-ID: <20101021183753.GB25335@broadcom.com> (raw)
In-Reply-To: <20101021182648.GA6827@kroah.com>
The basename-apiversion-codeversion construction for firmware filenames is not
used by most other firmware files, adds complexity, and is not providing any
value. Rename the firmware files using just basename-apiversion.
Users of the brcmfmac driver will need to update the linux-firmware package
to get the renamed files, or manually rename their installed firmware files.
Signed-off-by: Henry Ptasinski <henryp@broadcom.com>
---
drivers/staging/brcm80211/brcmfmac/wl_cfg80211.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/brcm80211/brcmfmac/wl_cfg80211.c b/drivers/staging/brcm80211/brcmfmac/wl_cfg80211.c
index 621521b..7f00bc4 100644
--- a/drivers/staging/brcm80211/brcmfmac/wl_cfg80211.c
+++ b/drivers/staging/brcm80211/brcmfmac/wl_cfg80211.c
@@ -54,8 +54,8 @@ static struct wl_dev *wl_cfg80211_dev;
u32 wl_dbg_level = WL_DBG_ERR | WL_DBG_INFO;
-#define WL_4329_FW_FILE "brcm/bcm4329-fullmac-4-218-248-5.bin"
-#define WL_4329_NVRAM_FILE "brcm/bcm4329-fullmac-4-218-248-5.txt"
+#define WL_4329_FW_FILE "brcm/bcm4329-fullmac-4.bin"
+#define WL_4329_NVRAM_FILE "brcm/bcm4329-fullmac-4.txt"
/*
** cfg80211_ops api/callback list
--
1.7.1
prev parent reply other threads:[~2010-10-21 18:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4CBE23F4.4020104@broadcom.com>
[not found] ` <20101019233520.GA12510@kroah.com>
[not found] ` <FD96C117992C584DBC47231B1EB6F5568206D859DC@SJEXCHCCR02.corp.ad.broadcom.com>
[not found] ` <20101020004743.GB31965@kroah.com>
[not found] ` <20101020005546.GL10832@broadcom.com>
[not found] ` <20101020010320.GA370@kroah.com>
2010-10-20 2:18 ` [PATCH] staging:brcm80211:brcmfmac:change firmware/config file name Henry Ptasinski
2010-10-20 3:10 ` Greg KH
2010-10-20 11:49 ` Rafał Miłecki
2010-10-20 18:04 ` Henry Ptasinski (local)
2010-10-21 17:08 ` [PATCH] linux-firmware: brcm: Removed codeversion from firmware filenames Henry Ptasinski
2010-11-01 14:28 ` David Woodhouse
2010-12-08 20:50 ` [PATCH v2] " Henry Ptasinski
2010-12-08 22:07 ` Rafał Miłecki
2010-12-08 22:23 ` Greg KH
2010-12-08 23:35 ` Henry Ptasinski
2010-12-09 0:28 ` Rafał Miłecki
2010-12-09 1:30 ` Henry Ptasinski
2010-12-09 9:01 ` Rafał Miłecki
2010-10-21 17:10 ` Subject: [PATCH] staging: brcm80211: brcmfmac: " Henry Ptasinski
2010-10-21 18:26 ` Greg KH
2010-10-21 18:37 ` Henry Ptasinski [this message]
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=20101021183753.GB25335@broadcom.com \
--to=henryp@broadcom.com \
--cc=brudley@broadcom.com \
--cc=devel@linuxdriverproject.org \
--cc=dwmw2@infradead.org \
--cc=greg@kroah.com \
--cc=grundler@google.com \
--cc=linux-wireless@vger.kernel.org \
--cc=noheek@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.