On Friday 20 July 2007 22:41, Larry Finger wrote:
John W. Linville wrote:
ACK...fwiw, I like the b43 name suggestion. I wonder if that is
too prone to confusion w/ b44? Probably no worse than ixgb vs
cxgb3 or e100 vs e1000 I suppose.
Today's discussion was very useful for me - I
3. If the port of softmac to mac80211 is merged before
Michael's driver, it will be known as bcm43xx with
bcm43xx-mac80211 remaining in wireless-dev.
Renaming a driver always creates madness. For example, even now
people and projects (e.g. Kismet) refer to madwifi-ng, but
there is no
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
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
On Fri, 2007-07-20 at 09:44 -0400, John W. Linville wrote:
On Fri, Jul 20, 2007 at 12:43:16AM -0400, Pavel Roskin wrote:
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
Not a developer, just a tester, and not a very good one... but I am a
_USER_ so here's my take.
The USERs don't want to know what card they have or what driver they
need or PCI IDs. That's all stuff that makes them say Linux Bad,
*s good. (Yeah I know, there's the whole driver moreass
Hello, Ehud!
On Fri, 2007-07-20 at 09:33 -0700, Ehud Gavron wrote:
The USERs don't want to know what card they have or what driver they
need or PCI IDs. That's all stuff that makes them say Linux Bad,
*s good. (Yeah I know, there's the whole driver moreass there and
PCI VENs too) but
On Fri, Jul 20, 2007 at 01:57:48PM -0400, Pavel Roskin wrote:
On Fri, 2007-07-20 at 09:33 -0700, Ehud Gavron wrote:
The driver should have a name that reflects its use and capabilities.
Not necessarily. End users should be shielded from such details by
distributions. Do you know the
On Thu, 2007-07-19 at 17:58 -0400, John W. Linville wrote:
Regarding hardware support, I have begun to lean towards having
the v3 driver continue to support all the hardware it does now.
I agree, until we can sort out the issues with that.
What exactly do we gain from using the v4 firmware?
On Thu, Jul 12, 2007 at 09:34:55AM -0500, Larry Finger wrote:
My plan is to clean up the code, check it with my BCM4306 and BCM4318
devices, and then make it available as a patch against the mainline source
for more general testing. At the same time, I will publish the results of
my
On Thu, 19 Jul 2007 17:58:01 -0400
John W. Linville [EMAIL PROTECTED] wrote:
Are you proposing to add a third driver and deprecate the softmac
driver? Or can we treat this as a port of the existing driver
to mac80211? I think that might be better for users and distros,
and might let us get
Stefano Brivio wrote:
On Thu, 19 Jul 2007 17:58:01 -0400
John W. Linville [EMAIL PROTECTED] wrote:
Are you proposing to add a third driver and deprecate the softmac
driver? Or can we treat this as a port of the existing driver
to mac80211? I think that might be better for users and
On Thu, 19 Jul 2007 20:38:17 -0500
Larry Finger [EMAIL PROTECTED] 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
Hello, Larry!
First of all, many thanks for porting the v3 driver to mac80211!
On Thu, 2007-07-19 at 20:38 -0500, Larry Finger wrote:
1. For more general testing, I'll distribute my driver as a patch to
be applied to wireless-dev as
it needs ssb, which is not yet in mainline. If we are
John and Michael,
I have good news regarding the driver mentioned in the subject. It is now
working on my BCM4311 with
performance that is nearly as good as for the softmac driver.
My approach has been to take the PHY and radio parts of the softmac driver and
use them with as much
of the
15 matches
Mail list logo
