Re: Strange behavior on bcm4311
2. After it I've got to do couple times (sometimes just once) localhost linux # ifconfig wlan0 up SIOCSIFFLAGS: Protocol error localhost linux # ifconfig wlan0 up SIOCSIFFLAGS: Protocol error localhost linux # ifconfig wlan0 up SIOCSIFFLAGS: Protocol error localhost linux # ifconfig wlan0 up After it my card is coming up. And that's what I've got from dmesg (I thing that 3 first errors where after SIOCSIFFLAGS: Protocol error): I don't know why the Protocol error occurs. This is just an indication that the firmware wasn't uploaded and the device isn't ready. -Joe ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
bug report : dscape bcm43xx on linksys WRT54G
Hi,
I have a linksys WRT54G on which I install OpenWRT (the development
version, ie Kamikaze). This linux system comes with a 2.6.17 kernel
(not the linus kernel but one patched to support some of the WRT54G
hardware).
When building this system (with a cross compiler : WRT54G is mips),
we can choose to compile the bcm43xx module (the SoftMac one). The
sources for this module are not patched (ie they are the same as the
ones in 2.6.17 official linux kernel). However, I want to use my WRT54G
as an AP, so I need hostapd, so I need the dscape bcm43xx...
I try to follow the advices from
http://openfacts.berlios.de/index-en.phtml?title=Broadcom_43xx_Linux_Driver/Debian_Unstable_with_Devicescape_802.11_stack
With some more patches, I succeed in cross-compiling a dscape bcm43xx.
For those who are interested, I add a package/dscape-ieee80211 directory
whose contents can be see here:
http://dept-info.labri.fr/~danjean/dscape-ieee80211/
In two words, I use the rt2x00 dscape stack with the bcm43xx dscape
driver (and ssb.c) from the wireless-dev linux tree.
However, when loading the module, no core were detected. Looking at the
sources and comparing with the softmac bcm43xx (that detect my device),
I found that dscape bcm43xx does not change the mmio when switching the
core.
I added the following patch to my sources :
http://dept-info.labri.fr/~danjean/dscape-ieee80211/patches/200-ssb-bugfix.patch
Index: dscape-ieee80211/src/wireless-dev/ssb/ssb.c
===
--- dscape-ieee80211.orig/src/wireless-dev/ssb/ssb.c2006-11-13
02:00:02.0 +0100
+++ dscape-ieee80211/src/wireless-dev/ssb/ssb.c 2006-11-13 01:58:55.0
+0100
@@ -590,6 +590,7 @@
int err;
int attempts = 0;
u32 cur_core;
+ static int last_core = 1;
while (1) {
err = ssb_pci_write_config32(ssb, SSB_BAR0_WIN,
@@ -610,6 +611,10 @@
goto error;
udelay(10);
}
+ char* mmio=(char*)((coreidx-last_core)*SSB_CORE_SIZE +
(char*)ssb-mmio);
+ ssb-mmio=mmio;
+ last_core=coreidx;
+ printk(KERN_DEBUG PFX switched to core %i, mmio set to %p\n, coreidx,
ssb-mmio);
return 0;
error:
printk(KERN_ERR PFX Failed to switch to core %u\n, coreidx);
I know that this is a quirck and dirty patch, but it seems to work.
At least, when loading the bcm, I get this :
Nov 13 22:19:04 (none) user.warn kernel: PCI: Enabling device :00:01.0
( - 0002)
Nov 13 22:19:04 (none) user.debug kernel: PCI: Setting latency timer of device
:00:01.0 to 64
Nov 13 22:19:04 (none) user.debug kernel: ssb: switched to core 0, mmio set to
b800
Nov 13 22:19:04 (none) user.debug kernel: ssb: switched to core 0, mmio set to
b800
Nov 13 22:19:04 (none) user.debug kernel: ssb: Core 0 found: cc 0800, rev 09,
vendor 4243
Nov 13 22:19:04 (none) user.debug kernel: ssb: switched to core 1, mmio set to
b8001000
Nov 13 22:19:04 (none) user.debug kernel: ssb: Core 1 found: cc 0812, rev 07,
vendor 4243
Nov 13 22:19:04 (none) user.debug kernel: ssb: switched to core 2, mmio set to
b8002000
Nov 13 22:19:04 (none) user.debug kernel: ssb: Core 2 found: cc 0806, rev 07,
vendor 4243
Nov 13 22:19:04 (none) user.debug kernel: ssb: switched to core 3, mmio set to
b8003000
Nov 13 22:19:04 (none) user.debug kernel: ssb: Core 3 found: cc 0818, rev 01,
vendor 4243
Nov 13 22:19:04 (none) user.debug kernel: ssb: switched to core 4, mmio set to
b8004000
Nov 13 22:19:04 (none) user.debug kernel: ssb: Core 4 found: cc 0817, rev 01,
vendor 4243
Nov 13 22:19:04 (none) user.debug kernel: ssb: switched to core 5, mmio set to
b8005000
Nov 13 22:19:04 (none) user.debug kernel: ssb: Core 5 found: cc 0816, rev 01,
vendor 4243
Nov 13 22:19:04 (none) user.debug kernel: ssb: switched to core 6, mmio set to
b8006000
Nov 13 22:19:04 (none) user.debug kernel: ssb: Core 6 found: cc 080F, rev 01,
vendor 4243
Nov 13 22:19:04 (none) user.debug kernel: ssb: switched to core 7, mmio set to
b8007000
Nov 13 22:19:04 (none) user.debug kernel: ssb: Core 7 found: cc 0804, rev 0A,
vendor 4243
Nov 13 22:19:04 (none) user.info kernel: bcm43xx_d80211: Broadcom 4712 WLAN
found
Nov 13 22:19:04 (none) user.debug kernel: ssb: switched to core 7, mmio set to
b8007000
Nov 13 22:19:04 (none) user.debug kernel: ssb: switched to core 1, mmio set to
b8001000
Nov 13 22:19:04 (none) user.info kernel: bcm43xx_d80211: PHY connected
Nov 13 22:19:04 (none) user.info kernel: bcm43xx_d80211: Detected PHY: Version:
2, Type 2, Revision 2
Nov 13 22:19:04 (none) user.info kernel: bcm43xx_d80211: Detected Radio: ID:
2205017f (Manuf: 17f Ver: 2050 Rev: 2)
Nov 13 22:19:04 (none) user.info kernel: bcm43xx_d80211: Radio turned off
Nov 13 22:19:04 (none) user.info kernel: bcm43xx_d80211: Radio turned off
Nov 13 22:19:04 (none) user.debug kernel: ssb: switched to core 0, mmio set to
b800
Nov 13 22:19:04 (none) user.debug
Re: bug report : dscape bcm43xx on linksys WRT54G
On Monday 13 November 2006 23:45, Vincent Danjean wrote:
Index: dscape-ieee80211/src/wireless-dev/ssb/ssb.c
===
--- dscape-ieee80211.orig/src/wireless-dev/ssb/ssb.c 2006-11-13
02:00:02.0 +0100
+++ dscape-ieee80211/src/wireless-dev/ssb/ssb.c 2006-11-13
01:58:55.0 +0100
@@ -590,6 +590,7 @@
int err;
int attempts = 0;
u32 cur_core;
+ static int last_core = 1;
while (1) {
err = ssb_pci_write_config32(ssb, SSB_BAR0_WIN,
@@ -610,6 +611,10 @@
goto error;
udelay(10);
}
+ char* mmio=(char*)((coreidx-last_core)*SSB_CORE_SIZE +
(char*)ssb-mmio);
+ ssb-mmio=mmio;
+ last_core=coreidx;
+ printk(KERN_DEBUG PFX switched to core %i, mmio set to %p\n, coreidx,
ssb-mmio);
return 0;
error:
printk(KERN_ERR PFX Failed to switch to core %u\n, coreidx);
I am working on a port of bcm43xx to this machine.
The issue is really more complicated than this mmio hack.
If you want to have some hack that actually works on the wrt,
please lookup the mail archives.
--
Greetings Michael.
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
bcm4318
Well after doing a serious upgrade on my line I discovered just how bad off the bcm4318 truely is. I have a 3Mbp/s line and with bcm4318 I am lucky if I can utilize a 1/3rd of that. ( i.e =1.0Mbps ) Those who have this card might want to concider throwing it in the trash, it does not work with dscape and softmac development is dead if you read Micheal's post to the mail list. ALL development should only be done on wireless-dev tree :/ . So for now I will stick with my wired ethernet just so I get to use what I pay for. Just figured I would let you all know how bad off the bcm4318 truely is right now :/ If your interested in testing your line results see www.2wire.com and run their speed meter. Jory ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: bcm4318
Jory A. Pratt wrote: Well after doing a serious upgrade on my line I discovered just how bad off the bcm4318 truely is. I have a 3Mbp/s line and with bcm4318 I am lucky if I can utilize a 1/3rd of that. ( i.e =1.0Mbps ) Those who have this card might want to concider throwing it in the trash, it does not work with dscape and softmac development is dead if you read Micheal's post to the mail list. ALL development should only be done on wireless-dev tree :/ . So for now I will stick with my wired ethernet just so I get to use what I pay for. Just figured I would let you all know how bad off the bcm4318 truely is right now :/ If your interested in testing your line results see www.2wire.com and run their speed meter. Jory Honestly, what's the problem here? It's incredible that it works even a little bit. That's better than it was before bcm43xx existed. I don't see how you can claim that it's awful and that we're not working on trying to make it better. Larry has done a lot of work to keep the SoftMAC port working as best as possible and has backported many of Michael's devicescape fixes. Just because Michael isn't working on SoftMAC doesn't mean that it's useless. As for fixing bcm4318, have you reviewed the spec changes and compared them to the driver? Instead of complaining, be happy that it works at all and maybe help us out instead of sending useless emails to the list. -Joe ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: bcm4318
Jory A. Pratt wrote: Just figured I would let you all know how bad off the bcm4318 truely I didn't even know the 4318 was even supported. Must have skimmed over those emails (I have a 4311). I'd say 1M on a card that I didn't know would come up and work is pretty good. (Let's see, that's gotta be at least 50% faster than not working.) (Customers! I just can't stop laughing. ;) tom -- Tom Surace) ,~~v~~, [EMAIL PROTECTED]),`. .`, http://www.byteheaven.com ) - === + === --- A:tekhedd Y:tekhedd2003 )Hamster was here signature.asc Description: OpenPGP digital signature ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
