On Sun, 2007-08-05 at 12:18 +0200, Michael Buesch wrote:
Well, it's not that easy. Current code just doesn't make any sense.
I do not understand how hardware power control works exactly, so I
can't write some detailed message or something.
That's probably a chicken and egg problem ;)
OK, the
From: Larry Finger [EMAIL PROTECTED]
Since commit 85a83d26697dd2203ac4e5f33022951f2c3e6e33, bcm43xx-mac80211:
Rewrite and simplify handling of the initialization status, some PCI
adapters have problems due to interrupts happening before the device status
reaches BCM43xx_STARTED. This patch delays
From: Larry Finger [EMAIL PROTECTED]
In the sprom for bcm43xx devices, any unprogrammed values are set to all ones.
In the case of antenna gains, the specs indicate that a gain of 2 dBm should
be set if no value is stored. This patch implements that provision.
Signed-off-by: Larry Finger [EMAIL
From: Larry Finger [EMAIL PROTECTED]
Fixed-by: Michael Buesch [EMAIL PROTECTED]
In bcm43xx-mac80211, the mechanism for decreasing the transmit rate cannot
be triggered. This may be shown by walking away from the AP with a laptop.
At some distance, communications will be lost and never recovered
This will always work.
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
Index: wireless-dev/drivers/net/wireless/bcm43xx-mac80211/bcm43xx_dma.c
===
--- wireless-dev.orig/drivers/net/wireless/bcm43xx-mac80211/bcm43xx_dma.c
On Monday 06 August 2007, Pavel Roskin wrote:
On Sun, 2007-08-05 at 12:18 +0200, Michael Buesch wrote:
Well, it's not that easy. Current code just doesn't make any sense.
I do not understand how hardware power control works exactly, so I
can't write some detailed message or something.
On Mon, 2007-08-06 at 08:42 -0400, Joseph Jezak wrote:
The problem is that the reverse engineering team (myself and
Johannes) don't understand the code in the original driver well
enough. The power control code is certainly the most confusing and
incomplete part of our specs. While I'd
Pavel Roskin wrote:
On Sun, 2007-08-05 at 12:18 +0200, Michael Buesch wrote:
Well, it's not that easy. Current code just doesn't make any sense.
I do not understand how hardware power control works exactly, so I
can't write some detailed message or something.
That's probably a chicken and
On Monday 06 August 2007, John W. Linville wrote:
On Sat, Aug 04, 2007 at 06:47:29PM +0200, Michael Buesch wrote:
On Saturday 04 August 2007, Larry Finger wrote:
Pavel Roskin wrote:
On Fri, 2007-08-03 at 20:46 -0500, Larry Finger wrote:
The size of LO array message is not fatal.
Michael Buesch wrote:
Well, without a stacktrace you don't know who caused the error.
We can remove that. But I still don't know what we gain from
removing useful debug messages. If you don't care about bcm43xx bugs, simply
disable bcm43xx debugging.
Michael, I agree with you in general,
On Monday 06 August 2007, Larry Finger wrote:
Michael Buesch wrote:
Well, without a stacktrace you don't know who caused the error.
We can remove that. But I still don't know what we gain from
removing useful debug messages. If you don't care about bcm43xx bugs, simply
disable bcm43xx
On Fri, Aug 03, 2007 at 01:02:12AM -0700, Michael Wu wrote:
This doesn't seem quite right. I think ieee80211_rx_h_data is a safer place
for this check (inside the IEEE80211_FCTL_FROMDS case), and allows various
statistics to be updated. ieee80211_rx_h_sta_process is another function that
On 8/6/07, Pavel Roskin [EMAIL PROTECTED] wrote:
On Sun, 2007-08-05 at 12:18 +0200, Michael Buesch wrote:
Well, it's not that easy. Current code just doesn't make any sense.
I do not understand how hardware power control works exactly, so I
can't write some detailed message or something.
For testing purposes, this patch adds a file named power_level to the
debugfs for bcm43xx-mac80211. If this file is read, it returns the current
setting for the Desired power level. Writing a number between 5 and 18
will set that value as the new value for the desired power setting.
On Monday 06 August 2007 22:22:14 Larry Finger wrote:
Index: wireless-dev/drivers/net/wireless/bcm43xx-mac80211/bcm43xx_main.c
===
--- wireless-dev.orig/drivers/net/wireless/bcm43xx-mac80211/bcm43xx_main.c
+++
Michael Buesch wrote:
On Monday 06 August 2007 22:22:14 Larry Finger wrote:
Index: wireless-dev/drivers/net/wireless/bcm43xx-mac80211/bcm43xx_main.c
===
--- wireless-dev.orig/drivers/net/wireless/bcm43xx-mac80211/bcm43xx_main.c
On Sunday 05 August 2007 23:11:33 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
connection?
It should, but this feature is not yet implemented. I have some
On Monday 06 August 2007 22:36:49 Larry Finger wrote:
Michael Buesch wrote:
On Monday 06 August 2007 22:22:14 Larry Finger wrote:
Index: wireless-dev/drivers/net/wireless/bcm43xx-mac80211/bcm43xx_main.c
===
---
For testing purposes, this patch adds a file named power_level to the
debugfs for bcm43xx-mac80211. If this file is read, it returns the current
setting for the Desired power level. Writing a number between 5 and 18
will set that value as the new value for the desired power setting.
Michael Buesch wrote:
No, why do you poke with this at all.
This completely breaks power adjustment from mac80211.
Simply don't touch bcm43xx_dev_config :)
The problem is that mac80211 never seems to do any power adjustment. The funny
0x1b value for power
level that I wondered about
On Monday 06 August 2007 23:29:04 Larry Finger wrote:
Michael,
I sent the wrong message under this subject before.
This hack disabled hardware power control. With this installed and the
desired power set to 10 dBm using the previous patch, I get much, much
better performance from
---
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
I am currently doing a patch for this.
That's it
http://bu3sch.de/patches/wireless-dev/20070806-1186437386/patches
22 matches
Mail list logo
