I've tested it with BCM4318 (ASUS WL500-gP). When I run hostapd - it seems
to hang the system (100% CPU load)
but also this patch seems to fix this bug:
https://lists.berlios.de/pipermail/bcm43xx-dev/2008-March/007021.html
___
Bcm43xx-dev mailing list
Another unrelated bug (sorry, testing often finds unrelated bugs) is
that scanning with specific ESSID was returning non-matching APs. I
mean iwlist wlan0 scan my_essid, which would still report many
different ESSIDs. It's inconvenient when the driver can sense 22 APs at
once :)
Heh. I'm
I had a case of total disassociation last night, and it is unusual. NM
was unable to reconnect (so we go to bash).
A scan revealed no APs but after a module reload they are back...
What further testing or other diagnostics can I run should this happen
again to rest?
Thanks
E
[EMAIL PROTECTED]
On Fri, 2008-04-04 at 21:43 +0200, Michael Buesch wrote:
This fixes the initialization of the PHY TX control words in
shared memory. These control words are used for management frames
like beacons.
This actually breaks beacons, if I don't use this it sends them,
otherwise it only gets PHY TX
On Friday 04 April 2008 21:43:07 Michael Buesch wrote:
This fixes the initialization of the PHY TX control words in
shared memory. These control words are used for management frames
like beacons.
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
---
John, this is for 2.6.26
Please
This fixes beacon updating in the bottomhalf.
In case the device is busy, we will defer to later in the IRQ handler.
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
---
John, this is for 2.6.26 in addition to the beacon patch I sent yesterday.
drivers/net/wireless/b43/main.c | 98
This fixes the initialization of the PHY TX control words in
shared memory. These control words are used for management frames
like beacons.
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
---
John, this is for 2.6.26.
This is a replacement patch for the one I sent yesterday.
Index:
We must use the b43_is_mode() call to check the current interface
operation mode.
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
---
John, this is for 2.6.26.
Index: wireless-testing/drivers/net/wireless/b43/main.c
===
---
KURT PETERS wrote:
Can I just Diff this into the current kernel?
Kurt
You should be more specific about what you mean by current kernel.
Do you mean Linus's tree? My patch is based on the current contents of
wireless-testing. It fails to apply against Linus's tree, but only the
final hunk
This patch is _not_ supposed to go upstream, yet.
I just like to have it in -mm to get more testing.
This patch is supposed to distribute the calibration bursts over time,
so that calibration only happens when it's actually needed.
So instead of disabling the MAC every 120 secs and recalibrating
The calculation of TX power has recently been improved in b43.
This patch implements those improvements in b43legacy.
With this patch, the estimated power out calculation becomes
quite stable. After the initial settling, the estimate varies by
0.25 dBm, or less.
This patch is meant to apply to
KURT PETERS wrote:
You mentioned I couldn't use Linus's repository, so Where can I get a
revised kernel with these changes already in place (I'm running 2.6.24.3
from kernel.org)?
kurt
I didn't say that you couldn't use Linus's repository - only that you need to
remove one hunk from the
Pavel Roskin a écrit :
You may want to use compat-wireless then:
http://linuxwireless.org/en/users/Download
It's a backport of the current wireless drivers for the older kernels.
The patch Michael asked us to test applies to it cleanly.
Thank you. I didn't know compat-wireless.
On Sun, 2008-04-06 at 01:27 +0200, [EMAIL PROTECTED] wrote:
Pavel Roskin a écrit :
You may want to use compat-wireless then:
http://linuxwireless.org/en/users/Download
It's a backport of the current wireless drivers for the older kernels.
The patch Michael asked us to test applies to
On Sat, 2008-04-05 at 11:09 +0200, Johannes Berg wrote:
Another unrelated bug (sorry, testing often finds unrelated bugs) is
that scanning with specific ESSID was returning non-matching APs. I
mean iwlist wlan0 scan my_essid, which would still report many
different ESSIDs. It's
On Fri, 2008-04-04 at 23:06 -0400, Pavel Roskin wrote:
I'll try to get 4318 tested over the weekend.
It's just as good as bcm4306.
b43-phy0: Broadcom 4318 WLAN found
b43-phy0 debug: Found PHY: Analog 3, Type 2, Revision 7
b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 8
It
16 matches
Mail list logo
