firmware versions?

2007-08-09 Thread Johannes Berg
Hi, We were just discussing the negative effects of having too many different firmwares (like the problem Andy ran into); if you're using the version 4 driver and have a different firmware than * 343.126 (this is the currently recommended one) * 351.1092 (I'm using that) could you reply with

bcm4301 - bcm43xx-legacy

2007-08-09 Thread Michael Buesch
It turns out that it's better to extend the device support in bcm4301 due to more difficulties in reverse engineering the newer bcm drivers. Newer drivers don't contain support for wireless core ref 5 anymore. So I suggest we support 5 devices with the legacy driver using v3 firmware. And

Re: bcm4301 - bcm43xx-legacy

2007-08-09 Thread Pavel Roskin
On Thu, 2007-08-09 at 15:41 +0200, Michael Buesch wrote: So, that said, I want to rename all the drivers. My plan was to rename bcm43xx-mac80211 to b43, so you could probably rename bcm4301 to b43-legacy or something shorter like b43-leg or maybe even b43-old. I think if bcm43xx will be

Re: firmware versions?

2007-08-09 Thread Larry Finger
Johannes Berg wrote: Hi, We were just discussing the negative effects of having too many different firmwares (like the problem Andy ran into); if you're using the version 4 driver and have a different firmware than * 343.126 (this is the currently recommended one) * 351.1092 (I'm using

Re: Port of bcm43xx from softmac to mac80211 is available for testing

2007-08-09 Thread Richard Jonsson
On Wednesday 08 August 2007 22:49:17 you wrote: Richard Jonsson wrote: On Monday 06 August 2007 03:21:11 you wrote: Richard Jonsson wrote: Isn't Desired TX power supposed to adapt so that higher bitrates are possible, with Bit Rate going lower if that is not enough to keep a good

Re: bcm4301 - bcm43xx-legacy

2007-08-09 Thread Larry Finger
Michael Buesch wrote: It turns out that it's better to extend the device support in bcm4301 due to more difficulties in reverse engineering the newer bcm drivers. Newer drivers don't contain support for wireless core ref 5 anymore. So I suggest we support 5 devices with the legacy driver

Re: bcm4301 - bcm43xx-legacy

2007-08-09 Thread Pavel Roskin
On Thu, 2007-08-09 at 16:07 +0200, Michael Buesch wrote: On Thursday 09 August 2007 16:00:47 Pavel Roskin wrote: On Thu, 2007-08-09 at 15:41 +0200, Michael Buesch wrote: So, that said, I want to rename all the drivers. My plan was to rename bcm43xx-mac80211 to b43, so you could

Re: bcm4301 - bcm43xx-legacy

2007-08-09 Thread Michael Buesch
On Thursday 09 August 2007 16:21:09 Pavel Roskin wrote: On Thu, 2007-08-09 at 16:07 +0200, Michael Buesch wrote: On Thursday 09 August 2007 16:00:47 Pavel Roskin wrote: On Thu, 2007-08-09 at 15:41 +0200, Michael Buesch wrote: So, that said, I want to rename all the drivers. My

Re: bcm4301 - bcm43xx-legacy

2007-08-09 Thread Michael Buesch
On Thursday 09 August 2007 16:46:40 Larry Finger wrote: Michael Buesch wrote: Newer drivers don't contain support for wireless core ref 5 anymore. So I suggest we support 5 devices with the legacy driver using v3 firmware. And anything above with v4 firmware with upstream

Re: bcm4301 - bcm43xx-legacy

2007-08-09 Thread Michael Buesch
On Thursday 09 August 2007 16:09:53 Larry Finger wrote: Michael Buesch wrote: It turns out that it's better to extend the device support in bcm4301 due to more difficulties in reverse engineering the newer bcm drivers. Newer drivers don't contain support for wireless core ref 5

Re: bcm4301 - bcm43xx-legacy

2007-08-09 Thread Larry Finger
Michael Buesch wrote: Newer drivers don't contain support for wireless core ref 5 anymore. So I suggest we support 5 devices with the legacy driver using v3 firmware. And anything above with v4 firmware with upstream bcm43xx-mac80211. That's actually a nice cutoff point, as rev 5 is when

Re: bcm4301 - bcm43xx-legacy

2007-08-09 Thread Johannes Berg
On Thu, 2007-08-09 at 16:52 +0200, Michael Buesch wrote: There will be a problem with the PCI IDs, though. We can't see from the PCI ID if that's a v4 or v5 device. So we have to make _one_ common ssb-pci wrapper and let us probe from ssb, so that either b43 or b43legacy is loaded. I'll take

Re: bcm4301 - bcm43xx-legacy

2007-08-09 Thread Larry Finger
Johannes Berg wrote: On Thu, 2007-08-09 at 16:52 +0200, Michael Buesch wrote: There will be a problem with the PCI IDs, though. We can't see from the PCI ID if that's a v4 or v5 device. So we have to make _one_ common ssb-pci wrapper and let us probe from ssb, so that either b43 or

Re: bcm4301 - bcm43xx-legacy

2007-08-09 Thread Michael Buesch
On Thursday 09 August 2007, Larry Finger wrote: Johannes Berg wrote: On Thu, 2007-08-09 at 16:52 +0200, Michael Buesch wrote: There will be a problem with the PCI IDs, though. We can't see from the PCI ID if that's a v4 or v5 device. So we have to make _one_ common ssb-pci wrapper and

RE: firmware versions?

2007-08-09 Thread David Ellingsworth
Subject: firmware versions? From: [EMAIL PROTECTED] To: bcm43xx-dev@lists.berlios.de Date: Thu, 9 Aug 2007 15:42:52 +0200 Hi, We were just discussing the negative effects of having too many different firmwares (like the problem Andy ran into); if you're using the version 4 driver and

Re: bcm4301 - bcm43xx-legacy

2007-08-09 Thread John W. Linville
On Thu, Aug 09, 2007 at 08:33:52PM +0200, Martin Langer wrote: I wouldn't call it b43. Please add some letters here. BCM is still developing their bcm43xx platform. So it's possible that we will find another point in the future where we have to split b43 again. b43 is more a common name

Re: firmware versions?

2007-08-09 Thread Larry Finger
David Ellingsworth wrote: Subject: firmware versions? From: [EMAIL PROTECTED] To: bcm43xx-dev@lists.berlios.de Date: Thu, 9 Aug 2007 15:42:52 +0200 Hi, We were just discussing the negative effects of having too many different firmwares (like the problem Andy ran into); if you're using

RE: firmware versions?

2007-08-09 Thread David Ellingsworth
Date: Thu, 9 Aug 2007 15:01:34 -0500 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: [EMAIL PROTECTED]; bcm43xx-dev@lists.berlios.de Subject: Re: firmware versions? David Ellingsworth wrote: Subject: firmware versions? From: [EMAIL PROTECTED] To: bcm43xx-dev@lists.berlios.de

Re: firmware versions?

2007-08-09 Thread Larry Finger
David Ellingsworth wrote: bcm43xx-phy0: Broadcom 4306 WLAN found bcm43xx-phy0 debug: Found PHY: Analog 1, Type 2, Revision 1 bcm43xx-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2 bcm43xx-phy0 debug: Radio turned off bcm43xx-phy0 debug: Adding Interface type 2