Oliver Schwartz wrote:
Hi,
On Monday 28 November 2005 12:28, Jérémy Bobbio wrote:
On Sunday 27 November 2005 22:53, Larry Finger wrote:
At the moment, I am unable to load the bcm430x module due to the
following messages:
bcm430x: module license 'unspecified' taints kernel.
bcm430x: Unknown
I am using svn rev 946 of bcm43xx with the 051222 patches for the dscape stack
with WPA-TKIP encryption.
When I start a default ping sequence to my AP/router, I get 16 messages transmitted/received, then
the ping process hangs. If I interrupt it with CTRL/C, it reports back that 16 were sent
Routines to set/get_wap have recently been added to softmac. The attached patch removes the unused
set/get code from the softmac version of bcm43xx_wx.c and adds the SIOCTL links to the new softmac
routines.
Larry
Index: bcm43xx_wx.c
While reviewing the softmac version of r0utine bcm43xx_wx_get_rangeparams, I found the following
code snippit:
switch (bcm-current_core-phy-type) {
case BCM43xx_PHYTYPE_A:
case BCM43xx_PHYTYPE_G:
range-num_bitrates += 4;
range-bitrate[i++]
Johannes Berg wrote:
On Tue, 2006-01-10 at 21:05 -0600, Larry Finger wrote:
To be able to do this, it was necessary to patch ieee80211softmac_wx.c and bcm43xx_wx.c using the
two attached patches.
Are these different to the patches you had posted earlier to me (or on
the bcm mailing list
Johannes Berg wrote:
On Wed, 2006-01-11 at 09:50 -0600, Larry Finger wrote:
Some of the pieces were in the old patches, but these are definitely new.
Good, thanks. As I said, I'll test it over the weekend.
johannes
I forgot to mention in my earlier message that I never got beyond
Yves-Alexis Perez wrote:
Hi people,
I have a kernel panic with latest softmac snapshot and lastest bcm43xx
revision. Before, I was using the mercurial repository, and with the
last revision it worked fine. Now i've switched to the git tree, but
don't want to check out the whole kernel, so I've
Yves-Alexis Perez wrote:
Larry Finger wrote:
Yves-Alexis Perez wrote:
Hi people,
I have a kernel panic with latest softmac snapshot and lastest bcm43xx
revision. Before, I was using the mercurial repository, and with the
last revision it worked fine. Now i've switched to the git tree
Johannes Berg wrote:
On Tue, 2006-01-10 at 21:05 -0600, Larry Finger wrote:
To be able to do this, it was necessary to patch ieee80211softmac_wx.c
I decided to go ahead and committed a slightly different version of this
to ieee80211 instead of softmac (the difference being adding some
Yves-Alexis Perez wrote:
Larry Finger wrote:
No other oops...
Even this one didn't get saved in the logfile when your computer
crashed. Certainly doesn't make it easy. As soon as I test the build fro
the snapshot, I'll be back in touch.
Hmh, ok. Now i've made some cleaning. I don't
Larry Finger wrote:
I have successfully connected my Linksys WPC54G to my AP using WPA-PSK
encryption using the bcm43xx/softmac software.
To be able to do this, it was necessary to patch ieee80211softmac_wx.c
and bcm43xx_wx.c using the two attached patches.
Johannes changed my patch to add
Attached is a patch for bcm43xx/softmac that enables /proc/net/wireless and SIOCGIWSTATS to obtain
the wireless statistics, which are also used by desktop tools such as the Wireless Network Applet in
KDE. In the present implementation, I added the iw_statistics struct to bcm43xx_private. If
Paul T.Threshold wrote:
thank you very much
now it works, i had to add a patch to wpa_supplicant, posted before on
the list :-)
The only patch to wpa_supplicant that I know about was to implement the dscape interface. That is
not needed for the softmac/bcm43xx combination. I'm using
Paul T.Threshold wrote:
yes it works without patches, great!!! the only thing i'm concerned
about is that up till now i've got to tell my airport base st. not to
be a closed network, whe i'm the only computer connected... not a
problem anyway :-)
I had to go on-line to find out what you
[EMAIL PROTECTED] wrote:
Hi,
I've been trying this for several days now with no success.
I'm building the softmac layers with the daily snapshot each time and also
the BCM43xx driver from the daily snapshot.
I get warnings when compiling but no errors.
I've got eth1 aliased to bcm43xx in my
[EMAIL PROTECTED] wrote:
Thanks Larry,
I cant' get Ndiswrapper to work under this kernel (it's a custom 2.6.15
kernel with the DSDT patches 'cos the DSDT is broken on this laptop).
I'm wondering after reading a few more posts if this is to do with the
stack size. Will need to check this.
Simon,
I'm not sure about all your output on the previous e-mail, but please try a
couple of other things.
What do you see from an iwconfig command? You may have to be root to run that
one.
What do you see from an 'iwlist s' command? Again that may require root.
Those commands should be run
Marc Morrisette wrote:
I successfully extracted the firmware from wl_apsta.o, this worked
better than the Windows driver (apparently newer). I'm not getting any
more weird errors now, I also updated baselayout to the latest ~x86
version. This makes it bring the interface up before attempting
Attached is a patch for bcm43xx/softmac that enables /proc/net/wireless and
SIOCGIWSTATS to obtain
the wireless statistics, which are also used by desktop tools such as the
Wireless Network Applet in
KDE. In the present implementation, I added the iw_statistics struct to
bcm43xx_private. If
Danny,
Attached is the patch to implement statistics with Michael's comments addressed. This patch has been
made against his git tree.
Larry
diff --git a/drivers/net/wireless/bcm43xx/bcm43xx.h
b/drivers/net/wireless/bcm43xx/bcm43xx.h
index 38e75ed..411c18f 100644
---
Michael Buesch wrote:
On Monday 06 February 2006 08:22, Mike Leahy wrote:
Thanks for the tip.
I eventually abandoned bcm43xx in favour of ndiswrapper. Maybe bcm43xx
driver works for some people...but never for me. I've been running
FC5T2 (and subsequent updates) - every kernel that gets
Scott Robinson wrote:
On Tue, Feb 07, 2006 at 12:50:08PM -0600, Larry Finger wrote:
[...]
As you are obviously in the FC test program, could you inquire where they
are downloading softmac and bcm43xx code?
[...]
That's a good braod question. There have been a lot of patches flying
back
Joseph Jezak wrote:
Michael Buesch wrote:
The original driver looped 3500 times here, is that enough Larry? I've
changed the specs to reflect this.
On my system, when 1000 fails, 1 still doesn't work as the IRQ_READY will never appear. With my
modification, it hasn't failed in nearly
Mike Leahy wrote:
Stefano,
I gave your suggestion a try...distance doesn't seem to have any impact.
Setting the txpower via iwconfig doesn't seem to have any obvious
effect either.
The set_xmitpower section is still a TODO. The interface accepts the input but
then throws it away.
Larry
Increasing the timeout loop count in bcm43xx_mac_suspend has cured most of the
'MAC suspend failed'
and all of the XMIT ERROR messages.
The one remaining situation where there is a failure in mac_suspend comes from periodic_work1. When
it happens, the system gets into an
Scott Robinson wrote:
On Tue, Feb 14, 2006 at 03:16:09AM +0100, Maik Beckmann wrote:
[...]
Maybe you should set the rate to 11M. At least that worked for me and if
I recall right there are some problems with the rates. Anyway, I'm not a
developer ;)
[...]
Does anyone know why, in
to set the maximum channel according to the guidelines. This patch is drawn against the 060215 snapshot.
Signed-Off-By: Larry Finger [EMAIL PROTECTED]
diff -ur a/drivers/net/wireless/bcm43xx/bcm43xx_main.h
b/drivers/net/wireless/bcm43xx/bcm43xx_main.h
--- a/drivers/net/wireless/bcm43xx
Michael Buesch wrote:
On Thursday 16 February 2006 04:09, Larry Finger wrote:
The current version of the bcm43xx-softmac driver scans 14 channels, even though channels greater
than 11 are not permitted in the US and Canada. Similarly only channels 1-13 are allowed in Europe.
AFAIK, channel 14
Cedric Blancher wrote:
Yes it is indeed. Just remember management traffic is still sent
unprotected.
Now you want to crack WPA PSK. To achieve this, you need to sniff one
authentication so you can attack it with your dictionnary or
bruteforcer. How do you get this authentication ? You inject
Hans Fugal wrote:
I know I asked this in that other email that was so long probably nobody
read to the end where the question was, so I apologize for repeating
myself.
Has anyone had success with wpa_supplicant and the softmac stack? Is
this expected to work? When I try to use it, it seems to
Gregory Gulik wrote:
I was surprised (pleasantly at first) to find there was a bcm43xx driver
included in the Fedora Core 5 Test 3 release. Anyway, I found the
firmware and I think I installed it correctly.
However, when the device gets started up it seems to think the radio is
turned off
Dan Williams wrote:
Completely untested, not entirely sure it compiles. For whatever
reason, softmac is sending custom events to userspace already, but it
should _really_ be sending the right WEXT events instead. Comments? If
this looks good, please apply it.
Signed-off-by: Dan Williams
Andrea Lusuardi - UoVoBW wrote:
sorry if i snip, but i'll answer only the part about which i can
say something: the part regarding authentication speed.
I too am using the softmac driver on debian on an ibook with rc5, and i
found that i need to lower the rate to get a stable/fast
Michael Buesch wrote:
On Sunday 04 June 2006 21:49, Mattias Nissler wrote:
On Sun, 2006-06-04 at 21:44 +0200, Michael Buesch wrote:
On Sunday 04 June 2006 21:30, Mattias Nissler wrote:
Well, mine is a mini-PCI. I'd replace mine by one of a newer rev and
donate the old one if somebody can tell
Michael Buesch wrote:
On Sunday 04 June 2006 21:49, Mattias Nissler wrote:
On Sun, 2006-06-04 at 21:44 +0200, Michael Buesch wrote:
On Sunday 04 June 2006 21:30, Mattias Nissler wrote:
Well, mine is a mini-PCI. I'd replace mine by one of a newer rev and
donate the old one if somebody can tell
Meyer, Richard wrote:
Yes, I enabled the debugging. My device is listed on the site, so I
would imagine it has been encountered before.
Not necessarily. The BCM430s has been, but not necessarily your combination of
rev levels.
I booted up my system and let it crash, the following is the
Larry Finger wrote:
Meyer, Richard wrote:
Yes, I enabled the debugging. My device is listed on the site, so I
would imagine it has been encountered before.
Not necessarily. The BCM430s has been, but not necessarily your
combination of rev levels.
I booted up my system and let it crash
regulatory information.
Signed-Off-By: Larry Finger [EMAIL PROTECTED]
diff --git a/drivers/net/wireless/bcm43xx/bcm43xx_main.h
b/drivers/net/wireless/bcm43xx/bcm43xx_main.h
index 30a202b..1164936 100644
--- a/drivers/net/wireless/bcm43xx/bcm43xx_main.h
+++ b/drivers/net/wireless/bcm43xx
Jeff Garzik wrote:
John W. Linville wrote:
+assert(bcm-mac_suspended = 0);
+if (bcm-mac_suspended == 0) {
+bcm43xx_power_saving_ctl_bits(bcm, -1, 1);
+bcm43xx_write32(bcm, BCM43xx_MMIO_STATUS_BITFIELD,
+bcm43xx_read32(bcm,
Florian,
Florian Fainelli wrote:
Hi Larry,
I posted recently that I had false reported signal values from 0 to -250 dBm
which are impossible for a Wi-Fi card, so I guess there must be something
wrong with the qdbm - mw and mw - qdbm calculations somewhere, probably
affecting the showed
Johannes Berg wrote:
On Tue, 2006-06-27 at 12:49 -0500, Larry Finger wrote:
If anyone has a better value, please let me
know. The noise value is still the one calculated from the clean-room formula. On my system, this is
roughly -65 dBm, which seems too high. I would appreciate getting any
In http://bcm-specs.sipsolutions.net/APHYSetup/noise_scale_table in the table for G PHY Rev = 2,
offset 13 has the value 0x1402, whereas bcm43xx_ilt.c has 0x1400 for the equivalent number. Is this
a typo in the driver or on the website?
Larry
___
Joe,
Joseph Jezak wrote:
Larry Finger wrote:
In http://bcm-specs.sipsolutions.net/APHYSetup/noise_scale_table in the
table for G PHY Rev = 2, offset 13 has the value 0x1402, whereas
bcm43xx_ilt.c has 0x1400 for the equivalent number. Is this a typo in
the driver or on the website?
Larry
I
I have been working on the bcm43xx_mac_suspend problem on my machine, which has led to many
sequences of 'ifdown', remove CardBus card, 'modprobe -r bcm43xx', and replug the card to get my
newly revised version of bcm43xx.ko loaded. I am running Linville's tree with only minor
modifications.
Michael,
In trying various things in mac_suspend, I accidentally messed up the test for IRQ ready so that the
code returned immediately. The bottom line was that nothing went wrong. There were no crashes and no
hangs. On that basis, I changed the code as shown in the following patch. This code
Matej Cepl wrote:
First of all -- I can read this list, so I really don't need to
get on Cc: -- if your email client (even if it is webmail)
doesn't support posting just to the list, use different one or
edit headers. Thanks.
Replying to All is common courtesy on these lists. We don't know
I remember an announcement on this list that the user interface for bcm43xx-d80211 changed, but I
have been unable to locate any documentation on the new UI. Will someone please point me to the
appropriate document(s)?
Thanks,
Larry
___
Bcm43xx-dev
I have gotten most things working to produce wireless statistics through
/proc/net/wireless for
bcm43xx-d80211; however, I have one problem that I have not yet been able to
solve. When I do a 'cat
/proc/net/wireless', the following is printed:
Inter-| sta-| Quality| Discarded
Paolo Arnaldo Dallari wrote:
Hi all.
I'm writing because I have some problems with my Airport Extreme card on
my ibook g4.
I've recompiled a 2.6.17 kernel with bcm43xx support.
No problem in compilation, no one when i bring up the module:
ieee80211_crypt: registered algorithm 'NULL'
I downloaded and built the latest version of bcm43xx-softmac from
Linville's wireless-2.6 tree. I am now getting lots of
bcm43xx: ASSERTION FAILED (bcm-mac_suspended = 0) at:
drivers/net/wireless/bcm43xx/bcm43xx_main.c:2147:bcm43xx_mac_enable()
messages in my log. I thought this problem was
Michael Buesch wrote:
We are talking about the mac_suspend in pwork patch, which got
commented to death by you and several others.
But there is no way around applying it.
There are only two choices. Either we apply that patch and make
further development (and bugfixing) of bcm43xx possible,
While running the latest version from Linville's wireless-dev tree, I
get the following in my logs:
bcm43xx_d80211: ASSERTION FAILED (bcm-interface.if_id == if_id) at:
drivers/net/wireless/d80211/bcm43xx/bcm43xx_main.c:4311:bcm43xx_config_interface()
HW CONFIG: channel=1 freq=2412 phymode=3
Michael Buesch wrote:
On Tuesday 01 August 2006 21:02, Larry Finger wrote:
While running the latest version from Linville's wireless-dev tree, I
get the following in my logs:
bcm43xx_d80211: ASSERTION FAILED (bcm-interface.if_id == if_id) at:
drivers/net/wireless/d80211/bcm43xx
I have more information on
bcm43xx_d80211: ASSERTION FAILED (bcm-interface.if_id == if_id) at:
drivers/net/wireless/d80211/bcm43xx/bcm43xx_main.c:4312:bcm43xx_config_interface()
At time of the assertion failure, bcm-interface.if_id = 6, if_id = 5
The stack dump at the time is
[c0103d4d]
Sometimes when I insert by BCM4306 card, the virtual interface wlan1
is deleted. Note: mot that it seems to matter, but the modules
bcm43xx-d80211, 80211, and rate-control have all just been reloaded.
The logged messages are:
bcm43xx_d80211: Chip ID 0x4306, rev 0x2
bcm43xx_d80211: Number of
Jiri Benc wrote:
Thanks for your bugreports.
Glad to help, particularly as I'm told that d80211 will be replacing
softmac in the kernel.
I have one other problem that I cannot document. When the wireless
interface is active, but never when I'm connected through the wire,
the machine will
Jiri Benc wrote:
Could you write details about your setup? Which bcm chip do you have
(I'll try to reproduce it with a similar chip if possible)? Do you have
SMP machine? Do you have SMP kernel? Do you have preemption enabled in
the kernel? Do you have ipv6 enabled? What type of encryption are
Jiri,
Since Linville's wireless-dev and your dscape were brought to
v2.6.18-rc3 in the past couple of days, my system has hung in bootup
if the bcm43xx card is installed. Usually, it stops just into run
level 5 while starting the network. Sometimes kdm comes up, but I am
unable to log in as
Jiri Benc wrote:
On Thu, 03 Aug 2006 07:33:49 -0500, Larry Finger wrote:
Preemption is enabled,
I suspect this is the problem. If I'm right, no debug info will help.
Try to disable preemption first and check if hangs still occur.
You are right. With preemption disabled, I have had no hangs
Jiri,
This patch, which is made against your tree today, implements wireless
statistics for bcm43xx-d80211 in the same manner as was previously
done for bcm43xx-softmac.
There are changes to two of the data structures:
1. In bcm43xx_stats, the completely bogus 'link_quality' is replaced
by
Ben Klein wrote:
I have just bought a Linksys WPC54G adapter based on research indicating
it was a Broadcom chipset that works with ndiswrapper. I have not tried
ndiswrapper yet, as I found out about bcm43xx in the 2.6.17 kernel after
confirming it is a Broadcom.
I'm sending this email
Michael,
Michael Buesch wrote:
Hi John,
Please apply this to wireless-dev.
--
This fixes various bugs in the init and shutdown code
that would lead to lockups and crashes.
This is best reproducable by receiving a timeout from
the netdev watchdog.
Is a similar bug likely to be the
a few bytes of memory
for the sake of speed by not requiring masking (and probably
shifting) of the bitfields.
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Signed-Off-By: Larry Finger [EMAIL PROTECTED]
Index: wireless-2.6/drivers/net/wireless/bcm43xx/bcm43xx_dma.h
Michael Buesch wrote:
On Wednesday 16 August 2006 17:52, Larry Finger wrote:
Johannes Berg wrote:
On Wed, 2006-08-16 at 10:36 -0500, Larry Finger wrote:
+ /* Boolean. Is this a TX ring? */
+ u8 tx
+ /* Boolean. 64bit DMA if true, 32bit DMA otherwise. */
+ u8 dma64;
does that compile
-by: Michael Buesch [EMAIL PROTECTED]
Signed-Off-By: Larry Finger [EMAIL PROTECTED]
Index: wireless-2.6/drivers/net/wireless/bcm43xx/bcm43xx_dma.h
===
--- wireless-2.6.orig/drivers/net/wireless/bcm43xx/bcm43xx_dma.h
2006-08-16 12:47
Michael Buesch wrote:
Hm, weird bug.
I can't reproduce this on i386 or PPC.
Could it be a bug in the lockdep code?
It could be. I'll send it on to LKML. Perhaps one of the experts
there can tell us. It doesn't seem to cause any trouble, but I get
one of these when bcm43xx starts.
Are you
Arjan van de Ven wrote:
On Wed, 2006-08-16 at 18:06 +0200, Michael Buesch wrote:
On Wednesday 16 August 2006 05:54, Larry Finger wrote:
I'm at a loss here. Can anyone explain how to interpret this dump? I
think I see a general protection fault, but what to do from there is a
mystery.
Hm
I am having severe performance problems with bcm43xx-softmac.
When I ping my AP (only a wireless round trip), The following
times are typical. Note the instance when it takes nearly
1/2 second! In addition, I have seen times of 10 seconds, or more.
larrylap:~ # ping -c 10 192.168.1.1
PING
Michael Buesch wrote:
Can you post a dump of /debug/bcm43xx/ethX/tx_status
directly after you produced such a long delay?
The last ping before I took this output took 333 ms.
Larry
larrylap:~ # cat /debug/bcm43xx/eth1/tx_status
Last 100 logged xmitstatus blobs (Latest first):
0x00:
Kevin Crocker (teq) wrote:
Hi,
Yes, I have one of these devices in my laptop.
Yes, I want to get it to work.
03:02.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
Wireless LAN Controller (rev 02)
03:02.0 0280: 14e4:4320 (rev 02)
ifconfig eth1
eth1 Link
[EMAIL PROTECTED] wrote:
On Fri, 2006-08-18 at 08:01 -0400, Kevin Crocker (teq) wrote:
eth1 IEEE 802.11b/g ESSID: off/any Nickname:Broadcom 4306
Mode: Managed Frequency=2.437 GHz Access Point: Invalid
Bit Rate=1 Mb/s
RTS thr: off Fragment thr:off
Michael Buesch wrote:
On Friday 18 August 2006 13:52, Michael Buesch wrote:
Hm, I don't see anything special.
There's only one packet retried once, but even that succeed after the retry.
I would say that's normal noise.
So, what's going on there? Did you try with another card and driver, but
Jochen Puchalla wrote:
Hello list,
I have a HP compaq nx6325 with this card:
:30:00.0 Network controller: Broadcom Corporation BCM4310 UART (rev 01)
Subsystem: Hewlett-Packard Company: Unknown device 1361
Flags: bus master, fast devsel, latency 0, IRQ 10
Jochen Puchalla wrote:
Hi Larry,
I managed to boot the system with the patch, but the card does not show up in
iwconfig, so I send you some output of dmesg, maybe you see something
important there.
PS: I also could not switch on the antenna after booting, module was loaded
automatically.
-d80211 behave the same.
Signed-Off-By: Larry Finger [EMAIL PROTECTED]
diff --git a/drivers/net/wireless/bcm43xx/bcm43xx_wx.c
b/drivers/net/wireless/bcm43xx/bcm43xx_wx.c
index 1d3a3aa..888077f 100644
--- a/drivers/net/wireless/bcm43xx/bcm43xx_wx.c
+++ b/drivers/net/wireless/bcm43xx/bcm43xx_wx.c
Michael Buesch wrote:
On Thursday 31 August 2006 02:57, Larry Finger wrote:
+#if WIRELESS_EXT 20
+#define IW_ESSID_FIX0
+#else
+#define IW_ESSID_FIX1
+#endif
Eh, was this useless #if in the original patch I signed-off, too?
Because I want to revert my sign-off
with the revised SSID length of
WE-21.
Signed-off-by: Larry Finger [EMAIL PROTECTED]
Index: wireless-2.6/net/ieee80211/softmac/ieee80211softmac_wx.c
===
--- wireless-2.6.orig/net/ieee80211/softmac/ieee80211softmac_wx.c
+++ wireless
Michael,
This patch includes the board revision in the chip_id printk for the ssb
version of bcm43xx-d80211
and is meant to be applied to wireless-dev. As we have seen, behavior of the
chips can be dependent
on the rev level, thus a need to have it in the log.
Signed-off-by: Larry Finger
the latest wireless-dev.
Michael Buesch wrote:
On Friday 01 September 2006 18:00, Larry Finger wrote:
It is not sent for inclusion into mainline and I am not sure how
to handle this. if we simply merge it into mainline, we will end
up with all sorts of horrible and hard to resolve rejects
The latest git pull from wireless-dev (g7844a579) is calling a sleeping
function with irq's
disabled. The kernel is a UP version with preemption disabled. The dump is as
follows:
kernel: bcm43xx_d80211: Virtual interface added (type: 0x0002, ID: 4, MAC:
00:06:25:40:6f:03)
kernel:
Michael Buesch wrote:
John, please apply the following patch to wireless-dev.
(And please apply all the other patches, too, as I'm still
waiting to pull ;) )
--
Don't disable IRQs in PHY init.
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
The patch fixes the problem on my
Emanuele Giaquinta wrote:
I can confirm the very same behaviour using a bcm4306 on linux-2.6.18-rc4
with the bcm43xx patches queued for 2.6.19 applied; when a hard reset
occurs ksoftirqd begins using 100% CPU indefinitely, and in one case the
controller restart failed:
NETDEV WATCHDOG:
in
bcm43xx-softmac were
changed, but was overlooked at that time. The value of bcm-stats.link_quality
computed here is
never used.
Signed-off-by: Larry Finger [EMAIL PROTECTED]
Index: wireless-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c
Michael Buesch wrote:
On Monday 04 September 2006 06:38, Larry Finger wrote:
John,
Please queue the following patch for wireless-2.6. It removes some code that
was made obsolete by
the wireless statistics changes of several weeks ago, but was not noticed
them.
Thanks,
Larry
in
bcm43xx-softmac were
changed, but was overlooked at that time. The value of bcm-stats.link_quality
computed here is
never used, so it is removed as well.
Signed-off-by: Larry Finger [EMAIL PROTECTED]
Index: wireless-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c
Martin Langer wrote:
This patch prints microcode revision, patchlevel, date and time to
KERN_INFO. Also, version 4.xx microcodes (rev0x128) will be rejected
by the driver, because they still do not work.
Signed-off-by: Martin Langer [EMAIL PROTECTED]
Are there any reactions to this
With bcm43xx-softmac I am receiving a lot of messages like this
kernel: TKIP: received packet without ExtIV flag from 00:12:17:2c:66:c4
in my logs. The MAC address is that of my neighbor's AP, which uses WEP
encryption, not WPA-PSK TKIP
like I use. I think I recall seeing a place in softmac
Peter Osterlund wrote:
Michael Buesch [EMAIL PROTECTED] writes:
On Monday 04 September 2006 05:09, Larry Finger wrote:
This sounds as if there may be a deadlock when a restart occurs. Do you
have the lock debugging
options set in your configuration? I used to get the NETDEV WATCHDOG
Michael Buesch wrote:
Thanks. This is
Acked-by: Michael Buesch [EMAIL PROTECTED]
Larry, please push upstream.
Martin, can you also rediff this against wireless-dev?
Michael - I will push wireless-2.6 upstream.
Martin - your original patch had some fuzz and trailing whitespace. A
-by: Martin Langer [EMAIL PROTECTED]
Acked by Michael Buesch
Signed-off-by: Larry Finger [EMAIL PROTECTED]
Index: wireless-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c
===
--- wireless-2.6.orig/drivers/net/wireless/bcm43xx
Peter Osterlund wrote:
Larry Finger [EMAIL PROTECTED] writes:
Peter - does the interface work for a while, or does this transmit
timeout happen immediately?
It works perfectly for a few hours, then it stops working. Stressing
the network doesn't seem to make a difference. The only
I thought this was well known, but it has come up twice today.
If you want to use bcm43xx_SoftMAC, do _NOT_ use the code from Linville's
wireless-dev tree. It is
outdated!!! From that tree, use only bcm43xx-d80211. The correct tree for
softmac is the
wireless-2.6 tree of Linville.
Michael Buesch wrote:
Simple: increasing badness limit makes the whole periodic work
non-preemptible. And we all know what happens if we call
schedule() in non-preemptible code (we hold the IRQ spinlock).
This assert() was added to prevent incorrect BADNESS_LIMIT tunings ;)
I wonder
Martin Langer wrote:
Larry, IIRC your hardware is a 0x812 rev 4. This core will load a
different microcode (bcm43xx_microcode4.fw) than all later core
revisions. (I guess the pci revision number isn't usefull here.)
Those old microcodes 2 and 4 seem to have a different instruction set in
Martin Langer wrote:
On Wed, Sep 06, 2006 at 04:51:08PM -0500, Larry Finger wrote:
Sure. But there are more rev numbers in your logfiles. And there has to
be the revision of your wlan core 0x812, too. Look for a line like
bcm43xx: Core 1: ID 0x812, rev 0x4, vendor 0x4243, disabled
Michael Buesch wrote:
On Thursday 07 September 2006 03:34, Larry Finger wrote:
+return -EPERM;
+
you want to take the spinlock lock here, too.
Obviously, I copied the wrong model. Is it correct that one should take both
locks if your code will
touch the hardware, but the mutex
incorporates the
locking revision comments of Michael Buesch.
Thanks,
Larry
This patch prints out the ucode debug status to sysfs. So, users can
watch the microcode status of their hardware.
Signed-off-by: Martin Langer [EMAIL PROTECTED]
Signed-off-by: Larry Finger [EMAIL PROTECTED
Hi all,
I think I have a fix for the bcm43xx bug that leads to NETDEV WATCHDOG tx
timeouts and would like it
to get as much testing as possible as this bug affects V2.6.18-rcX. If the
problem is truly
fixed, I hope to get the fix into mainline before release of the bug into the
stable series.
Michael Buesch wrote:
The real question is: Why does this patch help?
Let's explain it. We don't stop networking just for fun there.
While executing long preemptible periodic work, we must ensure
that the TX path into the driver is not entered. It's the same
reason why we disable IRQs in the
Bin Zhang wrote:
I'd like to test the patch (the only thing I cant do for helping as I
don't know code).
(once again, my ibook freeze after 5 hours uptimes, and I see
Sep 8 00:07:40 localhost kernel: bcm43xx: Controller restarted
in my syslog)
1 - 100 of 1483 matches
Mail list logo
