From: David Woodhouse <dwmw2@infradead.org>
To: Pavel Roskin <proski@gnu.org>
Cc: Larry Finger <larry.finger@lwfinger.net>,
wireless <linux-wireless@vger.kernel.org>,
Michael Buesch <mb@bu3sch.de>,
Stefano Brivio <stefano.brivio@polimi.it>,
Broadcom Linux <bcm43xx-dev@lists.berlios.de>
Subject: Re: bcm4301: A mac80211 driver using V3 firmware
Date: Fri, 20 Jul 2007 13:12:04 +0100 [thread overview]
Message-ID: <1184933524.14697.119.camel@pmac.infradead.org> (raw)
In-Reply-To: <1184906596.9511.42.camel@dv>
On Fri, 2007-07-20 at 00:43 -0400, Pavel Roskin wrote:
>
> That's a very good goal.
>
> I would also consider the option to use different names for v3 and v4
> firmware. I have a file /etc/modprobe.d/bcm43xx that reads
>
> options bcm43xx fwpostfix=.3
> options bcm43xx_mac80211 fwpostfix=.4
>
> but we cannot expect every distro (let alone every user) to take care
> of the naming conflict. Users don't expect the need to rename
> firmware, and we shouldn't create a problem for them.
Yes. Please use a suitable postfix for v3 and v4 firmware so that they
can coexist. You can always make each driver fall back to the old
filename if it doesn't find the firmware with the postfix.
We can make the fwcutter write out files with appropriate names too.
--
dwmw2
next prev parent reply other threads:[~2007-07-20 12:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 14:34 bcm4301: A mac80211 driver using V3 firmware Larry Finger
2007-07-19 21:58 ` John W. Linville
2007-07-19 22:26 ` Johannes Berg
2007-07-19 23:27 ` Stefano Brivio
2007-07-20 1:38 ` Larry Finger
2007-07-20 3:09 ` Stefano Brivio
2007-07-20 4:43 ` Pavel Roskin
2007-07-20 12:12 ` David Woodhouse [this message]
2007-07-20 13:44 ` John W. Linville
2007-07-20 16:05 ` Pavel Roskin
2007-07-20 16:33 ` Ehud Gavron
2007-07-20 17:57 ` Pavel Roskin
2007-07-20 18:05 ` John W. Linville
2007-07-20 20:41 ` Larry Finger
2007-07-21 12:50 ` Michael Buesch
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=1184933524.14697.119.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=proski@gnu.org \
--cc=stefano.brivio@polimi.it \
/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).