Re: [Bug 9414] Not work light of button-led with module b43 in chipset broadcom 4318

2007-11-19 Thread Fernando Toledo 
El Mar 20 Nov 2007, Larry Finger escribió:
> [EMAIL PROTECTED] wrote:
> > http://bugzilla.kernel.org/show_bug.cgi?id=9414
> >
> >
> > [EMAIL PROTECTED] changed:
> >
> >What|Removed |Added
> > -
> >--- CC||[EMAIL PROTECTED]
>
> Michael,
>
> Just like this guy, the light on my wireless switch does not work, and has
> not since the rfkill logic was changed. I have been too busy to complain;
> however, the issue needs to ba addressed.
>
> How does one supply the necessary information so that the light will be
> changed as the switch is moved?
>
> Larry
>
> ___
> Bcm43xx-dev mailing list
> Bcm43xx-dev@lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

i can confirm this bug too.
i have a 4311 chipset

10:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI 
(rev 01)

i dont see the led on and the radio button dont show the old message "Radio 
button switched on/off" in the dmesg.



-- 
Dock Sud BBS
http://www.docksud.com.ar
telnet://bbs.docksud.com.ar


signature.asc
Description: This is a digitally signed message part.
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Re: [Bug 9414] Not work light of button-led with module b43 in chipset broadcom 4318

2007-11-19 Thread Larry Finger 
[EMAIL PROTECTED] wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=9414
> 
> 
> [EMAIL PROTECTED] changed:
> 
>What|Removed |Added
> 
>  CC||[EMAIL PROTECTED]

Michael,

Just like this guy, the light on my wireless switch does not work, and has not 
since the rfkill
logic was changed. I have been too busy to complain; however, the issue needs 
to ba addressed.

How does one supply the necessary information so that the light will be changed 
as the switch is moved?

Larry

___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Re: [PATCH v3] remove bcm43xx

2007-11-19 Thread Larry Finger 
Rafael J. Wysocki wrote:
> 
> Many people use the old driver and you are forcing them to switch in a rather
> unfriendly fashion.
> 
> Moreover, the switch generally involves a configuration change (on my system
> eth1 became wlan0) and is not _that_ seamless.

That change is in udev and has nothing to do with the bcm43xx - b43 change. The 
renaming will happen
even though one stays with bcm43xx.

Larry
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Re: [PATCH v3] remove bcm43xx

2007-11-19 Thread Stefano Brivio 
On Tue, 20 Nov 2007 00:19:55 +0100
Andreas Schwab <[EMAIL PROTECTED]> wrote:

> Stefano Brivio <[EMAIL PROTECTED]> writes:
> 
> > This is strange. Because it has been developed mainly on PPC. Plus, if
> > you could better define "does not work"
> 
> See .

It looks like we don't get a valid txstatus even if the txstatus indicator
register told us we could read it. The only difference I can see between
bcm43xx and b43 here is that in bcm43xx we allowed the whole register to be
non-zero, while in b43 we check a bit only (as per v4 specs). Would you
mind to try this:

--- drivers/net/wireless/b43/main.c.orig2007-11-20 01:12:12.186524483 
+0100
+++ drivers/net/wireless/b43/main.c 2007-11-20 01:12:34.922702865 +0100
@@ -947,7 +947,7 @@

while (1) {
v0 = b43_read32(dev, B43_MMIO_XMITSTAT_0);
-   if (!(v0 & 0x0001))
+   if (!v0)
break;
v1 = b43_read32(dev, B43_MMIO_XMITSTAT_1);

(probably it's not the solution, I just want to see what happens then).
BTW, what firmware are you using? Michael, any clue?


-- 
Ciao
Stefano
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Re: [PATCH v3] remove bcm43xx

2007-11-19 Thread Andreas Schwab 
Stefano Brivio <[EMAIL PROTECTED]> writes:

> This is strange. Because it has been developed mainly on PPC. Plus, if you
> could better define "does not work"

See .

Andreas.

-- 
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Re: [PATCH v3] remove bcm43xx

2007-11-19 Thread Stefano Brivio 
On Mon, 19 Nov 2007 23:36:44 +0100
Andreas Schwab <[EMAIL PROTECTED]> wrote:

> Stefano Brivio <[EMAIL PROTECTED]> writes:
> 
> > On Mon, 19 Nov 2007 23:00:11 +0100
> > "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
> >
> >> Well, are you 100% sure that everyone interested knows that this
> >> drivers is going out in 2.6.25 and no one will object?
> >
> > The maintainers know. Having both drivers in 2.6.24 should help find
> > out if there's anything which should be ironed out with b43/b43legacy,
> > but right now they are already working a lot better than bcm43xx, and
> > they are more stable. So I couldn't find a reason why we shouldn't
> > remove bcm43xx in 2.6.25.
> 
> b43 still does not work at all on ppc.

This is strange. Because it has been developed mainly on PPC. Plus, if you
could better define "does not work" as per
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html, it would be great.


-- 
Ciao
Stefano
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Re: [PATCH v3] remove bcm43xx

2007-11-19 Thread Rafael J. Wysocki 
On Monday, 19 of November 2007, Andreas Schwab wrote:
> Stefano Brivio <[EMAIL PROTECTED]> writes:
> 
> > On Mon, 19 Nov 2007 23:00:11 +0100
> > "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
> >
> >> Well, are you 100% sure that everyone interested knows that this drivers
> >> is going out in 2.6.25 and no one will object?
> >
> > The maintainers know. Having both drivers in 2.6.24 should help find out if
> > there's anything which should be ironed out with b43/b43legacy, but right
> > now they are already working a lot better than bcm43xx, and they are more
> > stable. So I couldn't find a reason why we shouldn't remove bcm43xx in
> > 2.6.25.
> 
> b43 still does not work at all on ppc.

Well, in that case for ppc users the removal of bcm43xx will be a regression.

Greetings,
Rafael
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Re: [PATCH v3] remove bcm43xx

2007-11-19 Thread Rafael J. Wysocki 
On Monday, 19 of November 2007, Stefano Brivio wrote:
> On Mon, 19 Nov 2007 23:00:11 +0100
> "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
> 
> > Well, are you 100% sure that everyone interested knows that this drivers
> > is going out in 2.6.25 and no one will object?
> 
> The maintainers know.

I mean the users.

> Having both drivers in 2.6.24 should help find out if 
> there's anything which should be ironed out with b43/b43legacy, but right
> now they are already working a lot better than bcm43xx, and they are more
> stable. So I couldn't find a reason why we shouldn't remove bcm43xx in
> 2.6.25.

Many people use the old driver and you are forcing them to switch in a rather
unfriendly fashion.

Moreover, the switch generally involves a configuration change (on my system
eth1 became wlan0) and is not _that_ seamless.

IMvHO, the schedule of the removal of this driver should be discussed on LKML.

Greetings,
Rafael
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Re: [PATCH v3] remove bcm43xx

2007-11-19 Thread Andreas Schwab 
Stefano Brivio <[EMAIL PROTECTED]> writes:

> On Mon, 19 Nov 2007 23:00:11 +0100
> "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
>
>> Well, are you 100% sure that everyone interested knows that this drivers
>> is going out in 2.6.25 and no one will object?
>
> The maintainers know. Having both drivers in 2.6.24 should help find out if
> there's anything which should be ironed out with b43/b43legacy, but right
> now they are already working a lot better than bcm43xx, and they are more
> stable. So I couldn't find a reason why we shouldn't remove bcm43xx in
> 2.6.25.

b43 still does not work at all on ppc.

Andreas.

-- 
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Re: [PATCH v3] remove bcm43xx

2007-11-19 Thread Stefano Brivio 
On Mon, 19 Nov 2007 23:00:11 +0100
"Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:

> Well, are you 100% sure that everyone interested knows that this drivers
> is going out in 2.6.25 and no one will object?

The maintainers know. Having both drivers in 2.6.24 should help find out if
there's anything which should be ironed out with b43/b43legacy, but right
now they are already working a lot better than bcm43xx, and they are more
stable. So I couldn't find a reason why we shouldn't remove bcm43xx in
2.6.25.


-- 
Ciao
Stefano
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Re: [PATCH v3] remove bcm43xx

2007-11-19 Thread Rafael J. Wysocki 
On Monday, 19 of November 2007, Stefano Brivio wrote:
> Remove bcm43xx.
> 
> 
> Signed-off-by: Stefano Brivio <[EMAIL PROTECTED]>
> 
> ---
> 
> John,
> I hope this is the last try, v2 was line wrapped. :) This is for 2.6.25.

Well, are you 100% sure that everyone interested knows that this drivers is
going out in 2.6.25 and no one will object?

Rafael
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

[PATCH v3] b43/b43legacy: fix left-over URLs and ifdefs

2007-11-19 Thread Stefano Brivio 
Fix some left-over URLs and ifdefs in b43 and b43legacy drivers.


Signed-off-by: Stefano Brivio <[EMAIL PROTECTED]>

---

John,
I hope this is the last try, v2 was line wrapped. :) This is for 2.6.24.

---

Index: wireless-2.6/drivers/net/wireless/b43/main.c
===
--- wireless-2.6.orig/drivers/net/wireless/b43/main.c
+++ wireless-2.6/drivers/net/wireless/b43/main.c
@@ -1558,7 +1558,7 @@ static void b43_release_firmware(struct 
 static void b43_print_fw_helptext(struct b43_wl *wl)
 {
b43err(wl, "You must go to "
-  
"http://linuxwireless.org/en/users/Drivers/bcm43xx#devicefirmware "
+  "http://linuxwireless.org/en/users/Drivers/b43#devicefirmware "
   "and download the correct firmware (version 4).\n");
 }
 
Index: wireless-2.6/drivers/net/wireless/b43legacy/dma.c
===
--- wireless-2.6.orig/drivers/net/wireless/b43legacy/dma.c
+++ wireless-2.6/drivers/net/wireless/b43legacy/dma.c
@@ -996,7 +996,7 @@ int b43legacy_dma_init(struct b43legacy_
 
err = ssb_dma_set_mask(dev->dev, dmamask);
if (err) {
-#ifdef BCM43XX_PIO
+#ifdef CONFIG_B43LEGACY_PIO
b43legacywarn(dev->wl, "DMA for this device not supported. "
"Falling back to PIO\n");
dev->__using_pio = 1;
Index: wireless-2.6/drivers/net/wireless/b43legacy/main.c
===
--- wireless-2.6.orig/drivers/net/wireless/b43legacy/main.c
+++ wireless-2.6/drivers/net/wireless/b43legacy/main.c
@@ -1398,7 +1398,7 @@ static void b43legacy_release_firmware(s
 static void b43legacy_print_fw_helptext(struct b43legacy_wl *wl)
 {
b43legacyerr(wl, "You must go to http://linuxwireless.org/en/users/";
-"Drivers/bcm43xx#devicefirmware "
+"Drivers/b43#devicefirmware "
 "and download the correct firmware (version 3).\n");
 }
 
 
-- 
Ciao
Stefano
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

[PATCH v3] remove bcm43xx

2007-11-19 Thread Stefano Brivio 
Remove bcm43xx.


Signed-off-by: Stefano Brivio <[EMAIL PROTECTED]>

---

John,
I hope this is the last try, v2 was line wrapped. :) This is for 2.6.25.
Please also run:
git rm -r drivers/net/wireless/bcm43xx


---

Index: wireless-2.6/Documentation/networking/bcm43xx.txt
===
--- wireless-2.6.orig/Documentation/networking/bcm43xx.txt
+++ /dev/null
@@ -1,89 +0,0 @@
-
-   BCM43xx Linux Driver Project
-   
-
-Introduction
-
-
-Many of the wireless devices found in modern notebook computers are
-based on the wireless chips produced by Broadcom. These devices have
-been a problem for Linux users as there is no open-source driver
-available. In addition, Broadcom has not released specifications
-for the device, and driver availability has been limited to the
-binary-only form used in the GPL versions of AP hardware such as the
-Linksys WRT54G, and the Windows and OS X drivers.  Before this project
-began, the only way to use these devices were to use the Windows or
-OS X drivers with either the Linuxant or ndiswrapper modules. There
-is a strong penalty if this method is used as loading the binary-only
-module "taints" the kernel, and no kernel developer will help diagnose
-any kernel problems.
-
-Development

-
-This driver has been developed using
-a clean-room technique that is described at
-http://bcm-specs.sipsolutions.net/ReverseEngineeringProcess. For legal
-reasons, none of the clean-room crew works on the on the Linux driver,
-and none of the Linux developers sees anything but the specifications,
-which are the ultimate product of the reverse-engineering group.
-
-Software
-
-
-Since the release of the 2.6.17 kernel, the bcm43xx driver has been
-distributed with the kernel source, and is prebuilt in most, if not
-all, distributions.  There is, however, additional software that is
-required. The firmware used by the chip is the intellectual property
-of Broadcom and they have not given the bcm43xx team redistribution
-rights to this firmware.  Since we cannot legally redistribute
-the firmware we cannot include it with the driver. Furthermore, it
-cannot be placed in the downloadable archives of any distributing
-organization; therefore, the user is responsible for obtaining the
-firmware and placing it in the appropriate location so that the driver
-can find it when initializing.
-
-To help with this process, the bcm43xx developers provide a separate
-program named bcm43xx-fwcutter to "cut" the firmware out of a
-Windows or OS X driver and write the extracted files to the proper
-location. This program is usually provided with the distribution;
-however, it may be downloaded from
-
-http://developer.berlios.de/project/showfiles.php?group_id=4547
-
-The firmware is available in two versions. V3 firmware is used with
-the in-kernel bcm43xx driver that uses a software MAC layer called
-SoftMAC, and will have a microcode revision of 0x127 or smaller. The
-V4 firmware is used by an out-of-kernel driver employing a variation of
-the Devicescape MAC layer known as d80211. Once bcm43xx-d80211 reaches
-a satisfactory level of development, it will replace bcm43xx-softmac
-in the kernel as it is much more flexible and powerful.
-
-A source for the latest V3 firmware is
-
-http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o
-
-Once this file is downloaded, the command
-'bcm43xx-fwcutter -w  '
-will extract the microcode and write it to directory
-. The correct directory will depend on your distribution;
-however, most use '/lib/firmware'. Once this step is completed,
-the bcm3xx driver should load when the system is booted. To see
-any messages relating to the driver, issue the command 'dmesg |
-grep bcm43xx' from a terminal window. If there are any problems,
-please send that output to [EMAIL PROTECTED]
-
-Although the driver has been in-kernel since 2.6.17, the earliest
-version is quite limited in its capability. Patches that include
-all features of later versions are available for the stable kernel
-versions from 2.6.18. These will be needed if you use a BCM4318,
-or a PCI Express version (BCM4311 and BCM4312). In addition, if you
-have an early BCM4306 and more than 1 GB RAM, your kernel will need
-to be patched. These patches, which are being updated regularly,
-are available at ftp://lwfinger.dynalias.org/patches. Look for
-combined_2.6.YY.patch. Of course you will need kernel source downloaded
-from kernel.org, or the source from your distribution.
-
-If you build your own kernel, please enable CONFIG_BCM43XX_DEBUG
-and CONFIG_IEEE80211_SOFTMAC_DEBUG. The log information provided is
-essential for solving any problems.
Index: wireless-2.6/MAINTAINERS
===
--- wireless-2.6.orig/MAINTAINERS
+++ wireless-2.6/MAINTAINERS
@@ -821,15 +821,6 @@ L: [EMAIL PROTECTED]
 W: ht

[PATCH v2] b43/b43legacy: fix left-over URLs and ifdefs

2007-11-19 Thread Stefano Brivio 
Fix some left-over URLs and ifdefs in b43 and b43legacy drivers.


Signed-off-by: Stefano Brivio <[EMAIL PROTECTED]>

---

John,
this is for 2.6.24. Sorry for the noise, please just discard the previous
patch.

---

Index: wireless-2.6/drivers/net/wireless/b43/main.c
===
--- wireless-2.6.orig/drivers/net/wireless/b43/main.c
+++ wireless-2.6/drivers/net/wireless/b43/main.c
@@ -1558,7 +1558,7 @@ static void b43_release_firmware(struct 
 static void b43_print_fw_helptext(struct b43_wl *wl)
 {
b43err(wl, "You must go to "
-
"http://linuxwireless.org/en/users/Drivers/bcm43xx#devicefirmware "
+
"http://linuxwireless.org/en/users/Drivers/b43#devicefirmware " "and
download the correct firmware (version 4).\n"); }
 
Index: wireless-2.6/drivers/net/wireless/b43legacy/dma.c
===
--- wireless-2.6.orig/drivers/net/wireless/b43legacy/dma.c
+++ wireless-2.6/drivers/net/wireless/b43legacy/dma.c
@@ -996,7 +996,7 @@ int b43legacy_dma_init(struct b43legacy_
 
err = ssb_dma_set_mask(dev->dev, dmamask);
if (err) {
-#ifdef BCM43XX_PIO
+#ifdef CONFIG_B43LEGACY_PIO
b43legacywarn(dev->wl, "DMA for this device not supported.
" "Falling back to PIO\n");
dev->__using_pio = 1;
Index: wireless-2.6/drivers/net/wireless/b43legacy/main.c
===
--- wireless-2.6.orig/drivers/net/wireless/b43legacy/main.c
+++ wireless-2.6/drivers/net/wireless/b43legacy/main.c
@@ -1398,7 +1398,7 @@ static void b43legacy_release_firmware(s
 static void b43legacy_print_fw_helptext(struct b43legacy_wl *wl)
 {
b43legacyerr(wl, "You must go to
http://linuxwireless.org/en/users/";
-"Drivers/bcm43xx#devicefirmware "
+"Drivers/b43#devicefirmware "
 "and download the correct firmware (version 3).\n");
 }
 


-- 
Ciao
Stefano
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

[PATCH v2] remove bcm43xx

2007-11-19 Thread Stefano Brivio 
Remove bcm43xx.


Signed-off-by: Stefano Brivio <[EMAIL PROTECTED]>

---

John,
this is for 2.6.25. Please also run:
git rm -r drivers/wireless/bcm43xx


---

Index: wireless-2.6/Documentation/networking/bcm43xx.txt
===
--- wireless-2.6.orig/Documentation/networking/bcm43xx.txt
+++ /dev/null
@@ -1,89 +0,0 @@
-
-   BCM43xx Linux Driver Project
-   
-
-Introduction
-
-
-Many of the wireless devices found in modern notebook computers are
-based on the wireless chips produced by Broadcom. These devices have
-been a problem for Linux users as there is no open-source driver
-available. In addition, Broadcom has not released specifications
-for the device, and driver availability has been limited to the
-binary-only form used in the GPL versions of AP hardware such as the
-Linksys WRT54G, and the Windows and OS X drivers.  Before this project
-began, the only way to use these devices were to use the Windows or
-OS X drivers with either the Linuxant or ndiswrapper modules. There
-is a strong penalty if this method is used as loading the binary-only
-module "taints" the kernel, and no kernel developer will help diagnose
-any kernel problems.
-
-Development

-
-This driver has been developed using
-a clean-room technique that is described at
-http://bcm-specs.sipsolutions.net/ReverseEngineeringProcess. For legal
-reasons, none of the clean-room crew works on the on the Linux driver,
-and none of the Linux developers sees anything but the specifications,
-which are the ultimate product of the reverse-engineering group.
-
-Software
-
-
-Since the release of the 2.6.17 kernel, the bcm43xx driver has been
-distributed with the kernel source, and is prebuilt in most, if not
-all, distributions.  There is, however, additional software that is
-required. The firmware used by the chip is the intellectual property
-of Broadcom and they have not given the bcm43xx team redistribution
-rights to this firmware.  Since we cannot legally redistribute
-the firmware we cannot include it with the driver. Furthermore, it
-cannot be placed in the downloadable archives of any distributing
-organization; therefore, the user is responsible for obtaining the
-firmware and placing it in the appropriate location so that the driver
-can find it when initializing.
-
-To help with this process, the bcm43xx developers provide a separate
-program named bcm43xx-fwcutter to "cut" the firmware out of a
-Windows or OS X driver and write the extracted files to the proper
-location. This program is usually provided with the distribution;
-however, it may be downloaded from
-
-http://developer.berlios.de/project/showfiles.php?group_id=4547
-
-The firmware is available in two versions. V3 firmware is used with
-the in-kernel bcm43xx driver that uses a software MAC layer called
-SoftMAC, and will have a microcode revision of 0x127 or smaller. The
-V4 firmware is used by an out-of-kernel driver employing a variation of
-the Devicescape MAC layer known as d80211. Once bcm43xx-d80211 reaches
-a satisfactory level of development, it will replace bcm43xx-softmac
-in the kernel as it is much more flexible and powerful.
-
-A source for the latest V3 firmware is
-
-http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o
-
-Once this file is downloaded, the command
-'bcm43xx-fwcutter -w  '
-will extract the microcode and write it to directory
-. The correct directory will depend on your distribution;
-however, most use '/lib/firmware'. Once this step is completed,
-the bcm3xx driver should load when the system is booted. To see
-any messages relating to the driver, issue the command 'dmesg |
-grep bcm43xx' from a terminal window. If there are any problems,
-please send that output to [EMAIL PROTECTED]
-
-Although the driver has been in-kernel since 2.6.17, the earliest
-version is quite limited in its capability. Patches that include
-all features of later versions are available for the stable kernel
-versions from 2.6.18. These will be needed if you use a BCM4318,
-or a PCI Express version (BCM4311 and BCM4312). In addition, if you
-have an early BCM4306 and more than 1 GB RAM, your kernel will need
-to be patched. These patches, which are being updated regularly,
-are available at ftp://lwfinger.dynalias.org/patches. Look for
-combined_2.6.YY.patch. Of course you will need kernel source downloaded
-from kernel.org, or the source from your distribution.
-
-If you build your own kernel, please enable CONFIG_BCM43XX_DEBUG
-and CONFIG_IEEE80211_SOFTMAC_DEBUG. The log information provided is
-essential for solving any problems.
Index: wireless-2.6/MAINTAINERS
===
--- wireless-2.6.orig/MAINTAINERS
+++ wireless-2.6/MAINTAINERS
@@ -821,15 +821,6 @@ L: [EMAIL PROTECTED]
 W: http://linuxwireless.org/en/users/Drivers/b43
 S: Maint

Re: [PATCH] remove bcm43xx

2007-11-19 Thread Michael Buesch 
On Monday 19 November 2007 17:12:17 Stefano Brivio wrote:
> Remove bcm43xx. Fix some left-over URLs and ifdefs in b43 and b43legacy
> drivers.
> 

Stefano, please send the fixes for b43 and b43legacy as a seperate
patch, as they have to go into 2.6.24.


-- 
Greetings Michael.
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Re: [resend] [PATCH] remove bcm43xx

2007-11-19 Thread Stefano Brivio 
On Mon, 19 Nov 2007 17:27:50 +0100
Stefano Brivio <[EMAIL PROTECTED]> wrote:

> John,
> this is for 2.6.25 - in case you didn't get the full patch. Please also
> run: git rm -r drivers/wireless/bcm43xx

git rm -r drivers/net/wireless/bcm43xx, of course. :)


-- 
Ciao
Stefano
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

[resend] [PATCH] remove bcm43xx

2007-11-19 Thread Stefano Brivio 
Remove bcm43xx. Fix some left-over URLs and ifdefs in b43 and b43legacy
drivers.


Signed-off-by: Stefano Brivio <[EMAIL PROTECTED]>

---

John,
this is for 2.6.25 - in case you didn't get the full patch. Please also run:
git rm -r drivers/wireless/bcm43xx

---

Index: wireless-2.6/Documentation/networking/bcm43xx.txt
===
--- wireless-2.6.orig/Documentation/networking/bcm43xx.txt
+++ /dev/null
@@ -1,89 +0,0 @@
-
-   BCM43xx Linux Driver Project
-   
-
-Introduction
-
-
-Many of the wireless devices found in modern notebook computers are
-based on the wireless chips produced by Broadcom. These devices have
-been a problem for Linux users as there is no open-source driver
-available. In addition, Broadcom has not released specifications
-for the device, and driver availability has been limited to the
-binary-only form used in the GPL versions of AP hardware such as the
-Linksys WRT54G, and the Windows and OS X drivers.  Before this project
-began, the only way to use these devices were to use the Windows or
-OS X drivers with either the Linuxant or ndiswrapper modules. There
-is a strong penalty if this method is used as loading the binary-only
-module "taints" the kernel, and no kernel developer will help diagnose
-any kernel problems.
-
-Development

-
-This driver has been developed using
-a clean-room technique that is described at
-http://bcm-specs.sipsolutions.net/ReverseEngineeringProcess. For legal
-reasons, none of the clean-room crew works on the on the Linux driver,
-and none of the Linux developers sees anything but the specifications,
-which are the ultimate product of the reverse-engineering group.
-
-Software
-
-
-Since the release of the 2.6.17 kernel, the bcm43xx driver has been
-distributed with the kernel source, and is prebuilt in most, if not
-all, distributions.  There is, however, additional software that is
-required. The firmware used by the chip is the intellectual property
-of Broadcom and they have not given the bcm43xx team redistribution
-rights to this firmware.  Since we cannot legally redistribute
-the firmware we cannot include it with the driver. Furthermore, it
-cannot be placed in the downloadable archives of any distributing
-organization; therefore, the user is responsible for obtaining the
-firmware and placing it in the appropriate location so that the driver
-can find it when initializing.
-
-To help with this process, the bcm43xx developers provide a separate
-program named bcm43xx-fwcutter to "cut" the firmware out of a
-Windows or OS X driver and write the extracted files to the proper
-location. This program is usually provided with the distribution;
-however, it may be downloaded from
-
-http://developer.berlios.de/project/showfiles.php?group_id=4547
-
-The firmware is available in two versions. V3 firmware is used with
-the in-kernel bcm43xx driver that uses a software MAC layer called
-SoftMAC, and will have a microcode revision of 0x127 or smaller. The
-V4 firmware is used by an out-of-kernel driver employing a variation of
-the Devicescape MAC layer known as d80211. Once bcm43xx-d80211 reaches
-a satisfactory level of development, it will replace bcm43xx-softmac
-in the kernel as it is much more flexible and powerful.
-
-A source for the latest V3 firmware is
-
-http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o
-
-Once this file is downloaded, the command
-'bcm43xx-fwcutter -w  '
-will extract the microcode and write it to directory
-. The correct directory will depend on your distribution;
-however, most use '/lib/firmware'. Once this step is completed,
-the bcm3xx driver should load when the system is booted. To see
-any messages relating to the driver, issue the command 'dmesg |
-grep bcm43xx' from a terminal window. If there are any problems,
-please send that output to [EMAIL PROTECTED]
-
-Although the driver has been in-kernel since 2.6.17, the earliest
-version is quite limited in its capability. Patches that include
-all features of later versions are available for the stable kernel
-versions from 2.6.18. These will be needed if you use a BCM4318,
-or a PCI Express version (BCM4311 and BCM4312). In addition, if you
-have an early BCM4306 and more than 1 GB RAM, your kernel will need
-to be patched. These patches, which are being updated regularly,
-are available at ftp://lwfinger.dynalias.org/patches. Look for
-combined_2.6.YY.patch. Of course you will need kernel source downloaded
-from kernel.org, or the source from your distribution.
-
-If you build your own kernel, please enable CONFIG_BCM43XX_DEBUG
-and CONFIG_IEEE80211_SOFTMAC_DEBUG. The log information provided is
-essential for solving any problems.
Index: wireless-2.6/MAINTAINERS
===
--- wireless-2.6.orig/MAINTAINERS
+++ wireless-2.6/MAINTAINERS
@@ -8

Re: [Bugme-new] [Bug 9402] New: Not work chipset broadcom 4318

2007-11-19 Thread Larry Finger 
Andrew Morton wrote:
> On Sun, 18 Nov 2007 15:49:40 -0800 (PST) [EMAIL PROTECTED] wrote:
> 
>> http://bugzilla.kernel.org/show_bug.cgi?id=9402
> 
> Rafael, this is allegedly a post-2.6.23 regression.
> 

Raphael and Andrew,

This is most definitely not a regression. The OP has switched from the SoftMAC 
to the mac80211
driver. His original problem is that he did not do the requisite upgrade of the 
firmware. Now that
he has done so, his is also running into a problem with his udev renaming 
rules. In managed mode,
mac80211 creates two interfaces - one named wmaster0 with type 0x801 and a 
second named wlan0 with
type 0x001. On the OP's system, the renaming rules have wmaster0 => eth1 and 
wlan0 => wlan0-ren. The
proper renaming rule for udev should have a 'ATTR{TYPE}=="1"' clause, which is 
likely missing. Once
the names are wrong, so are the scripts in /etc/sysconfig/network.

Larry



___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev