All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
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 09:44:25 -0400	[thread overview]
Message-ID: <20070720134425.GC7428@tuxdriver.com> (raw)
In-Reply-To: <1184906596.9511.42.camel@dv>

On Fri, Jul 20, 2007 at 12:43:16AM -0400, Pavel Roskin wrote:
> On Thu, 2007-07-19 at 20:38 -0500, Larry Finger wrote:

> > 4. Once bcm43xx-mac80211 gets merged to mainline, then Michael's driver should become bcm43xx and my 
> > driver gets its PCI IDs stripped to the 802.11b-only devices and once again becomes bcm4301. This 
> > name change for Michael's driver would cause some disruption for current users as their firmware 
> > would have the wrong name/version. That might be too much of a problem.
> 
> Actually, the common practice is that the new driver that doesn't
> supplant the old driver immediately and for the whole range of hardware
> gets a new name.  Think CONFIG_IDE vs CONFIG_ATA and eepro100 vs e100.
 
Yes, this preserves stability for happy bcm43xx users.  Still taking
suggestions for the new name for bcm43xx-mac80211... :-)

> Also, we could introduce a kernel option to enable support for new
> devices in your driver.
 
Yes, this is probably worthwhile for those wishing to avoid PCI ID
conflicts between the drivers.  I have also been speculating that
perhaps we need an option for a secondary PCI ID table, so that a
driver could support a large range of PCI IDs but then gracefully
bow-out if another driver had a certain ID in its primary table.
Does that make any sense?  It would seem to be applicable to a number
of drivers in the kernel.

> 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, we should probably start using a default value for fwpostfix.
As dwmw2 suggested, it would also be nice to fall back to an empty
fwpostfix if the firmware is not found w/ the default extension.

John
-- 
John W. Linville
linville@tuxdriver.com

  parent reply	other threads:[~2007-07-20 14:03 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
2007-07-20 13:44         ` John W. Linville [this message]
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=20070720134425.GC7428@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --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 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.