[PATCH] b43: Remove bogus integer truncation warnings
"warning: large integer implicitly truncated to unsigned type"
Signed-off-by: Michael Buesch
---
Virtual fists were already shaked, so I need to hurry up to fixup my crap. :P
Index: wireless-testing/drivers/net/wireless/b43/phy_g.c
===
--- wireless-testing.orig/drivers/net/wireless/b43/phy_g.c 2009-02-23
22:38:56.0 +0100
+++ wireless-testing/drivers/net/wireless/b43/phy_g.c 2009-02-23
22:41:28.0 +0100
@@ -968,13 +968,13 @@ b43_radio_interference_mitigation_enable
b43_phy_maskset(dev, 0x04A8, 0xFFF0, 0x0006);
b43_phy_maskset(dev, 0x04A2, 0xF0FF, 0x0800);
b43_phy_maskset(dev, 0x04A0, 0xF0FF, 0x0500);
b43_phy_maskset(dev, 0x04A2, 0xFFF0, 0x000B);
if (phy->rev >= 3) {
- b43_phy_mask(dev, 0x048A, ~0x8000);
+ b43_phy_mask(dev, 0x048A, (u16)~0x8000);
b43_phy_maskset(dev, 0x0415, 0x8000, 0x36D8);
b43_phy_maskset(dev, 0x0416, 0x8000, 0x36D8);
b43_phy_maskset(dev, 0x0417, 0xFE00, 0x016D);
} else {
b43_phy_set(dev, 0x048A, 0x1000);
b43_phy_maskset(dev, 0x048A, 0x9FFF, 0x2000);
Index: wireless-testing/drivers/net/wireless/b43/wa.c
===
--- wireless-testing.orig/drivers/net/wireless/b43/wa.c 2009-02-23
18:26:03.0 +0100
+++ wireless-testing/drivers/net/wireless/b43/wa.c 2009-02-23
22:43:00.0 +0100
@@ -379,13 +379,13 @@ static void b43_wa_altagc(struct b43_wld
b43_ofdmtab_write16(dev, B43_OFDMTAB_AGC1, 0, 254);
b43_ofdmtab_write16(dev, B43_OFDMTAB_AGC1, 1, 13);
b43_ofdmtab_write16(dev, B43_OFDMTAB_AGC1, 2, 19);
b43_ofdmtab_write16(dev, B43_OFDMTAB_AGC1, 3, 25);
}
- b43_phy_maskset(dev, B43_PHY_CCKSHIFTBITS_WA, ~0xFF00, 0x5700);
+ b43_phy_maskset(dev, B43_PHY_CCKSHIFTBITS_WA, (u16)~0xFF00, 0x5700);
b43_phy_maskset(dev, B43_PHY_OFDM(0x1A), ~0x007F, 0x000F);
b43_phy_maskset(dev, B43_PHY_OFDM(0x1A), ~0x3F80, 0x2B80);
b43_phy_maskset(dev, B43_PHY_ANTWRSETT, 0xF0FF, 0x0300);
b43_radio_set(dev, 0x7A, 0x0008);
b43_phy_maskset(dev, B43_PHY_N1P1GAIN, ~0x000F, 0x0008);
b43_phy_maskset(dev, B43_PHY_P1P2GAIN, ~0x0F00, 0x0600);
@@ -397,25 +397,25 @@ static void b43_wa_altagc(struct b43_wld
b43_phy_maskset(dev, B43_PHY_OFDM(0x88), ~0x00FF, 0x001C);
b43_phy_maskset(dev, B43_PHY_OFDM(0x88), ~0x3F00, 0x0200);
b43_phy_maskset(dev, B43_PHY_OFDM(0x96), ~0x00FF, 0x001C);
b43_phy_maskset(dev, B43_PHY_OFDM(0x89), ~0x00FF, 0x0020);
b43_phy_maskset(dev, B43_PHY_OFDM(0x89), ~0x3F00, 0x0200);
b43_phy_maskset(dev, B43_PHY_OFDM(0x82), ~0x00FF, 0x002E);
- b43_phy_maskset(dev, B43_PHY_OFDM(0x96), ~0xFF00, 0x1A00);
+ b43_phy_maskset(dev, B43_PHY_OFDM(0x96), (u16)~0xFF00, 0x1A00);
b43_phy_maskset(dev, B43_PHY_OFDM(0x81), ~0x00FF, 0x0028);
- b43_phy_maskset(dev, B43_PHY_OFDM(0x81), ~0xFF00, 0x2C00);
+ b43_phy_maskset(dev, B43_PHY_OFDM(0x81), (u16)~0xFF00, 0x2C00);
if (phy->rev == 1) {
b43_phy_write(dev, B43_PHY_PEAK_COUNT, 0x092B);
b43_phy_maskset(dev, B43_PHY_OFDM(0x1B), ~0x001E, 0x0002);
} else {
b43_phy_mask(dev, B43_PHY_OFDM(0x1B), ~0x001E);
b43_phy_write(dev, B43_PHY_OFDM(0x1F), 0x287A);
b43_phy_maskset(dev, B43_PHY_LPFGAINCTL, ~0x000F, 0x0004);
if (phy->rev >= 6) {
b43_phy_write(dev, B43_PHY_OFDM(0x22), 0x287A);
- b43_phy_maskset(dev, B43_PHY_LPFGAINCTL, ~0xF000,
0x3000);
+ b43_phy_maskset(dev, B43_PHY_LPFGAINCTL, (u16)~0xF000,
0x3000);
}
}
b43_phy_maskset(dev, B43_PHY_DIVSRCHIDX, 0x8080, 0x7874);
b43_phy_write(dev, B43_PHY_OFDM(0x8E), 0x1C00);
if (phy->rev == 1) {
b43_phy_maskset(dev, B43_PHY_DIVP1P2GAIN, ~0x0F00, 0x0600);
--
Greetings, Michael.
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
John Mountcastle wrote: > Can I just edit Michael's patch and apply it again just like I did the first > time: > > cd $(COMPAT_SRC_DIR) > patch -p1 < $(PATCH_FILE) > > Regards > > John Yes. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
Can I just edit Michael's patch and apply it again just like I did the first time: cd $(COMPAT_SRC_DIR) patch -p1 < $(PATCH_FILE) Regards John - Original Message From: Larry Finger To: John Mountcastle Cc: Michael Buesch ; bcm43xx-dev@lists.berlios.de Sent: Monday, February 23, 2009 1:54:54 PM Subject: Re: I need some help stabaizing b43 for a 4306 John Mountcastle wrote: > Yes, I'd say results are mixed. B43 now says it wants 20dBm and it's getting > 16.75 but iwconfig says rate is only 1Mb/s and I can't keep the link up long > enough to be usefull. > > If the SPROM was wrong all along, why does it work fine with bcm43xx? Many parts of the power control have undergone major changes. For most interfaces, these changes made them work better; however, yours may be different. If you want to try what happens with lower power, you can change the line in Michaels patch that looks like +max_pwr = INT_TO_Q52(20); You started with the equivalent of "INT_TO_Q52(15)" - what happens if the 20 is replaced by 12 or 10? Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
OK, it sounds like a pretty tough nut to crack. I'm not sure if I can get a new card as it's kinda built into this laptop, or, maybe I'm wrong. Do you think I might be able to crack this thing open and put in a replacement device? Anyway, thanks a lot for your help. I learned a little in the bargain so I won't call the adventure a total loss. Probably my best move is just to go back to openSUSE 10.3 with the bcm43xx driver. Or I might try blacklisting b43 and usng ndiswrapper. I've used it before with excellent results. Regards John - Original Message From: Michael Buesch To: Larry Finger Cc: John Mountcastle ; bcm43xx-dev@lists.berlios.de Sent: Monday, February 23, 2009 1:47:39 PM Subject: Re: I need some help stabaizing b43 for a 4306 On Monday 23 February 2009 18:36:12 Larry Finger wrote: > More food for thought: > > My BCM4306/2 in a Cardbus format has a maxpbg value that translates to 10 dBm. > It routinely transmits at 5-6 Mb/s in my normal setting. When I reprogrammed > the > SPROM to 20 dBm, it would start out at the above rate, then rapidly drop to 1 > Mb/s. It looked as if the radio was overheating. This has nothing to do with overheating, so let's reduce FUD a bit. ;) The attenuation is not linear. There's a certain threshold where it inverts. Let's explain it in simple numbers. Let's say the attenuation A is from 0-9. The actual power output O would looke something like this: A= 0 1 2 3 4 5 6 7 8 9 O= 0 1 2 3 4 4 3 2 1 0 This is true for broadcom cards and some atheros cards. So as we decrease attennuation, there's a point where output power is inverted. In this simple example we must not go below an A value of 5. The actual threshold is different for each device and you're pretty much likely hitting it. The control algorithm is unaware of this threshold and it will scale the attenuation down which results in lower power which will result in scaling down... So John, back to your problem. I think you're pretty much lost with it. Like thousands of other people (including me) are lost with crappy broadcom devices. I suggest you go and buy something sane instead. I cannot help you anymore with this. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
John Mountcastle wrote: > Yes, I'd say results are mixed. B43 now says it wants 20dBm and it's getting > 16.75 but iwconfig says rate is only 1Mb/s and I can't keep the link up long > enough to be usefull. > > If the SPROM was wrong all along, why does it work fine with bcm43xx? Many parts of the power control have undergone major changes. For most interfaces, these changes made them work better; however, yours may be different. If you want to try what happens with lower power, you can change the line in Michaels patch that looks like + max_pwr = INT_TO_Q52(20); You started with the equivalent of "INT_TO_Q52(15)" - what happens if the 20 is replaced by 12 or 10? Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
On Monday 23 February 2009 18:36:12 Larry Finger wrote: > More food for thought: > > My BCM4306/2 in a Cardbus format has a maxpbg value that translates to 10 dBm. > It routinely transmits at 5-6 Mb/s in my normal setting. When I reprogrammed > the > SPROM to 20 dBm, it would start out at the above rate, then rapidly drop to 1 > Mb/s. It looked as if the radio was overheating. This has nothing to do with overheating, so let's reduce FUD a bit. ;) The attenuation is not linear. There's a certain threshold where it inverts. Let's explain it in simple numbers. Let's say the attenuation A is from 0-9. The actual power output O would looke something like this: A= 0 1 2 3 4 5 6 7 8 9 O= 0 1 2 3 4 4 3 2 1 0 This is true for broadcom cards and some atheros cards. So as we decrease attennuation, there's a point where output power is inverted. In this simple example we must not go below an A value of 5. The actual threshold is different for each device and you're pretty much likely hitting it. The control algorithm is unaware of this threshold and it will scale the attenuation down which results in lower power which will result in scaling down... So John, back to your problem. I think you're pretty much lost with it. Like thousands of other people (including me) are lost with crappy broadcom devices. I suggest you go and buy something sane instead. I cannot help you anymore with this. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
Yes, I'd say results are mixed. B43 now says it wants 20dBm and it's getting 16.75 but iwconfig says rate is only 1Mb/s and I can't keep the link up long enough to be usefull. If the SPROM was wrong all along, why does it work fine with bcm43xx? Incidentally, when I rebooted and while the 4306 was still connected, NetworkManager said he saw 100%. b43-phy0 debug: [TX power] current = 16.75 dBm, desired = 20.0 dBm, max = 20.0 b43-phy0 debug: [TX power deltas] 3.25 dBm => bbatt-delta = 2, rfatt-delta = -2 b43-phy0 debug: Adjusting TX power b43-phy0 debug: Tuning TX-power to bbatt(2), rfatt(0), tx_control(0x30), tx_bias(0x00), tx_magn(0x00) sybill:~ # iwconfig wlan0 wlan0 IEEE 802.11bg ESSID:"MBR-6d2" Mode:Managed Frequency:2.417 GHz Access Point: 00:30:44:02:76:D2 Bit Rate=1 Mb/s Tx-Power=27 dBm Retry min limit:7 RTS thr:off Fragment thr=2352 B Encryption key:7761-7465-7266-616C-6C30-3030-30 Security mode:open Power Management:off Link Quality=85/70 Signal level:-45 dBm Noise level=-68 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 Regards John - Original Message From: Larry Finger To: John Mountcastle Cc: Michael Buesch ; bcm43xx-dev@lists.berlios.de Sent: Monday, February 23, 2009 12:36:12 PM Subject: Re: I need some help stabaizing b43 for a 4306 More food for thought: My BCM4306/2 in a Cardbus format has a maxpbg value that translates to 10 dBm. It routinely transmits at 5-6 Mb/s in my normal setting. When I reprogrammed the SPROM to 20 dBm, it would start out at the above rate, then rapidly drop to 1 Mb/s. It looked as if the radio was overheating. It is possible that the patch of today will make things worse, not better. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
More food for thought: My BCM4306/2 in a Cardbus format has a maxpbg value that translates to 10 dBm. It routinely transmits at 5-6 Mb/s in my normal setting. When I reprogrammed the SPROM to 20 dBm, it would start out at the above rate, then rapidly drop to 1 Mb/s. It looked as if the radio was overheating. It is possible that the patch of today will make things worse, not better. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
John Mountcastle wrote: > Here's a thought, every time I unload b43 and reload it, my indicated signal > strength (NetworkManager) is 85%. Shortly it drops off to 65%, then 51%. then > it usually fails. I ad to go find a wire because I couldn't keep the 4306 up, > long enough to reach yahoo. > > Michael, I applied you patch and compiled. I'll install and load the ne > drivers and let you know what TXmit power indicates. > > Larry, here's the SPROM you wanted. Your SPROM contains a maxpbg value of 0x3C, which translates to 15 dBm - exactly what the program is trying to maintain. I have data for a number of BCM4306 SPROM's due to my fixing of the Bluetooth coexistence problem for Ubuntu users. Every one of them that I looked at has that same value for maxpbg, which probably explains the poor performance. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
Here's a thought, every time I unload b43 and reload it, my indicated signal strength (NetworkManager) is 85%. Shortly it drops off to 65%, then 51%. then it usually fails. I ad to go find a wire because I couldn't keep the 4306 up, long enough to reach yahoo. Michael, I applied you patch and compiled. I'll install and load the ne drivers and let you know what TXmit power indicates. Larry, here's the SPROM you wanted. Password: sybill:~ # SPROM=$(find /sys -name ssb_sprom) sybill:~ # echo $SPROM /sys/devices/pci:00/:00:1e.0/:02:06.0/ssb_sprom sybill:~ # cat $SPROM 0140F4123C10204300800200021000189000944BA62C60369A1193FBA5FE3C003E000D000152 sybill:~ # - Original Message From: Larry Finger To: John Mountcastle Cc: Michael Buesch ; bcm43xx-dev@lists.berlios.de Sent: Monday, February 23, 2009 10:31:05 AM Subject: Re: I need some help stabaizing b43 for a 4306 John, I would like to see what is in your SPROM concerning the power settings. Please run the following commands: SPROM=$(find /sys -name ssb_sprom) echo $SPROM sudo cat $SPROM and post the output. Thanks, Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
John, I would like to see what is in your SPROM concerning the power settings. Please run the following commands: SPROM=$(find /sys -name ssb_sprom) echo $SPROM sudo cat $SPROM and post the output. Thanks, Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
On Monday 23 February 2009 13:52:04 mtcs...@yahoo.com wrote: > Good morning Michael. So, to be sure I've got it right; I want the second > patch and not the first. I need to apply it to this morning's compat sources, > not two days ago? right. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
Good morning Michael. So, to be sure I've got it right; I want the second patch and not the first. I need to apply it to this morning's compat sources, not two days ago? Cheers John Sent via BlackBerry by AT&T -Original Message- From: Michael Buesch Date: Mon, 23 Feb 2009 13:31:05 To: Subject: Re: I need some help stabaizing b43 for a 4306 On Monday 23 February 2009 13:25:36 Michael Buesch wrote: > On Monday 23 February 2009 12:15:54 Michael Buesch wrote: > > On Monday 23 February 2009 03:40:01 John Mountcastle wrote: > > > mtcs...@sybill:~/Desktop> sudo /usr/sbin/iwconfig wlan0 > > > wlan0 IEEE 802.11bg ESSID:"MBR-6d2" > > > Mode:Managed Frequency:2.417 GHz Access Point: > > > 00:30:44:02:76:D2 > > > Bit Rate=1 Mb/s Tx-Power=27 dBm > > > Retry min limit:7 RTS thr:off Fragment thr=2352 B > > > Encryption key:7761-7465-7266-616C-6C30-3030-30 Security > > > mode:open > > > Power Management:off > > > Link Quality=51/100 Signal level:-5 dBm Noise level=-17 dBm > > > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > > > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > > > > > Note that while b43-phy0 debug says desired output is 15.0dBm, iwconfig > > > says it's askigng for 27. > > > > Right, that's what I suspected. > > > > Can you try wireless-compat? It prints additional debugging info for this. > > compat is easy to install, usually. Just download it and do make; make > > install in the > > extracted source tree. You don't need to change your kernel for this. You > > can run it > > on a standard distribution kernel, usually. > > > > I made a patch which fixes up a possible PROM screwup: > http://bu3sch.de/patches/wireless-testing/20090223-1324/patches/018-b43-txpwr-sprom-fixes.patch > > You can apply that to compat-wireless: > cd compat-wireless-2009-02-XX > patch -p1 < 018-b43-txpwr-sprom-fixes.patch > Ok, seems this doesn't apply to compat-wireless. Use this one, which was diffed against today's compat-wireless: http://bu3sch.de/patches/misc/018-b43-txpwr-sprom-fixes.patch -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
On Monday 23 February 2009 13:25:36 Michael Buesch wrote: > On Monday 23 February 2009 12:15:54 Michael Buesch wrote: > > On Monday 23 February 2009 03:40:01 John Mountcastle wrote: > > > mtcs...@sybill:~/Desktop> sudo /usr/sbin/iwconfig wlan0 > > > wlan0 IEEE 802.11bg ESSID:"MBR-6d2" > > > Mode:Managed Frequency:2.417 GHz Access Point: > > > 00:30:44:02:76:D2 > > > Bit Rate=1 Mb/s Tx-Power=27 dBm > > > Retry min limit:7 RTS thr:off Fragment thr=2352 B > > > Encryption key:7761-7465-7266-616C-6C30-3030-30 Security > > > mode:open > > > Power Management:off > > > Link Quality=51/100 Signal level:-5 dBm Noise level=-17 dBm > > > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > > > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > > > > > Note that while b43-phy0 debug says desired output is 15.0dBm, iwconfig > > > says it's askigng for 27. > > > > Right, that's what I suspected. > > > > Can you try wireless-compat? It prints additional debugging info for this. > > compat is easy to install, usually. Just download it and do make; make > > install in the > > extracted source tree. You don't need to change your kernel for this. You > > can run it > > on a standard distribution kernel, usually. > > > > I made a patch which fixes up a possible PROM screwup: > http://bu3sch.de/patches/wireless-testing/20090223-1324/patches/018-b43-txpwr-sprom-fixes.patch > > You can apply that to compat-wireless: > cd compat-wireless-2009-02-XX > patch -p1 < 018-b43-txpwr-sprom-fixes.patch > Ok, seems this doesn't apply to compat-wireless. Use this one, which was diffed against today's compat-wireless: http://bu3sch.de/patches/misc/018-b43-txpwr-sprom-fixes.patch -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
On Monday 23 February 2009 12:15:54 Michael Buesch wrote: > On Monday 23 February 2009 03:40:01 John Mountcastle wrote: > > mtcs...@sybill:~/Desktop> sudo /usr/sbin/iwconfig wlan0 > > wlan0 IEEE 802.11bg ESSID:"MBR-6d2" > > Mode:Managed Frequency:2.417 GHz Access Point: > > 00:30:44:02:76:D2 > > Bit Rate=1 Mb/s Tx-Power=27 dBm > > Retry min limit:7 RTS thr:off Fragment thr=2352 B > > Encryption key:7761-7465-7266-616C-6C30-3030-30 Security > > mode:open > > Power Management:off > > Link Quality=51/100 Signal level:-5 dBm Noise level=-17 dBm > > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > > > Note that while b43-phy0 debug says desired output is 15.0dBm, iwconfig > > says it's askigng for 27. > > Right, that's what I suspected. > > Can you try wireless-compat? It prints additional debugging info for this. > compat is easy to install, usually. Just download it and do make; make > install in the > extracted source tree. You don't need to change your kernel for this. You can > run it > on a standard distribution kernel, usually. > I made a patch which fixes up a possible PROM screwup: http://bu3sch.de/patches/wireless-testing/20090223-1324/patches/018-b43-txpwr-sprom-fixes.patch You can apply that to compat-wireless: cd compat-wireless-2009-02-XX patch -p1 < 018-b43-txpwr-sprom-fixes.patch -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: More data on open-source firmware crash
On Monday 23 February 2009 07:30:13 Larry Finger wrote: > Francesco Gringoli wrote: > > > > do you mind testing this firmware? It's not the solution, but can help > > us understanding if we should follow this way. Download at > > http://www.ing.unibs.it/~gringoli/fwtest.tar.gz > > > > Before using this firmware please recompile b43 changing these two > > definitions in b43.h > > > > #define B43_MARKER_ID_REG 52 > > #define B43_MARKER_LINE_REG 53 > > > > I coded the firmware so that it will raise a B43_DEBUGIRQ_MARKER with id > > 10, line 100 if the condition I'm thinking to is true. You will see (I > > hope) in dmesg. > > I ran the test firmware until there was a failure. The B43_DEBUGIRQ_MARKER was > not present in the dmesg output. > > I also did as Michael suggested and preserved the depth of the tx_status > queue, > as well as the maximum depth observed. The latter value is 16; therefore, it > is > possible that the queue is being overrun. It is certainly full if the limit > really is 16. I still need to look at the detailed data from the last run, but > it is late here today. Note again that I expect the "tx status queue is full" check at the _start_ of the TX processing in firmware. Because if we started TX and later figure out the status queue is full, we can't really do anything about it. So we'd have to check that before even fetching the frame from the DMA. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
On Monday 23 February 2009 03:40:01 John Mountcastle wrote: > mtcs...@sybill:~/Desktop> sudo /usr/sbin/iwconfig wlan0 > wlan0 IEEE 802.11bg ESSID:"MBR-6d2" > Mode:Managed Frequency:2.417 GHz Access Point: 00:30:44:02:76:D2 > > Bit Rate=1 Mb/s Tx-Power=27 dBm > Retry min limit:7 RTS thr:off Fragment thr=2352 B > Encryption key:7761-7465-7266-616C-6C30-3030-30 Security mode:open > Power Management:off > Link Quality=51/100 Signal level:-5 dBm Noise level=-17 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > Note that while b43-phy0 debug says desired output is 15.0dBm, iwconfig says > it's askigng for 27. Right, that's what I suspected. Can you try wireless-compat? It prints additional debugging info for this. compat is easy to install, usually. Just download it and do make; make install in the extracted source tree. You don't need to change your kernel for this. You can run it on a standard distribution kernel, usually. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
