The latest code didn't work for me either for the b43legacy.  I had to 
reload the old drivers to see any SSIDs.  Wish I knew how to turn on 
debugging so I could provide more info.

Kurt
------------------------------

Message: 3
Date: Sun, 06 Apr 2008 17:42:57 -0500
From: Larry Finger <[EMAIL PROTECTED]>
Subject: Additional problem with b43legacy
To: Stefano Brivio <[EMAIL PROTECTED]>, Michael Buesch
        <[EMAIL PROTECTED]>
Cc: Broadcom Linux <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Stefano and Michael,

In order to test Stefano's recent patches for the BCM4303 using
b43legacy, I dug out my Linksys WMP11-V27, which has a BCM4301 chip.
Implementing it is a pain as it kills my sound card - thus it must be
removed before I turn that computer back to my spouse (it runs Windows).

The ssb details for the card are as follows:

ssb: Core 0 found: IEEE 802.11 (cc 0x812, rev 0x02, vendor 0x4243)
ssb: Core 1 found: PCMCIA (cc 0x80D, rev 0x00, vendor 0x4243)
ssb: Core 2 found: Fast Ethernet (cc 0x806, rev 0x02, vendor 0x4243)
ssb: Core 3 found: V90 (cc 0x807, rev 0x01, vendor 0x4243)
ssb: Core 4 found: PCI (cc 0x804, rev 0x03, vendor 0x4243)
ssb: SPROM revision 1 detected.
ssb: Sonics Silicon Backplane found on PCI device 0000:00:0b.0

The b43legacy and mac80211 messages that follow are:

b43legacy-phy0: Broadcom 4301 WLAN found
b43legacy-phy0 debug: Found PHY: Analog 0, Type 1, Revision 4
b43legacy-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2053, Revision 2
b43legacy-phy0 debug: Radio initialized
phy0: Selected rate control algorithm 'pid'
Broadcom 43xx-legacy driver loaded [ Features: PID, Firmware-ID: FW10 ]
b43legacy-phy0: Loading firmware version 0x127, patch level 14
(2005-04-18 02:36:27)
b43legacy-phy0 debug: Chip initialized
b43legacy-phy0 debug: 30-bit DMA initialized
b43legacy-phy0 debug: Wireless interface started
b43legacy-phy0 debug: Adding Interface type 2

The card works perfectly when running bcm43xx from the 2.6.22 kernel
used by openSUSE 10.3, but fails to transmit when running b43legacy.
The clue that there is a "TX problem" is seen when the module is unloaded:

b43legacy-phy0 debug: DMA-30 0x0220 (TX) max used slots: 128/128

To try to debug this, I added the following two printouts, and turned
on debugging in mac80211.

Index: wireless-testing/drivers/net/wireless/b43legacy/dma.c
===================================================================
--- wireless-testing.orig/drivers/net/wireless/b43legacy/dma.c
+++ wireless-testing/drivers/net/wireless/b43legacy/dma.c
@@ -94,6 +94,7 @@ static void op32_poke_tx(struct b43legac
   {
          b43legacy_dma_write(ring, B43legacy_DMA32_TXINDEX,
                              (u32)(slot * sizeof(struct
b43legacy_dmadesc32)));
+       printk(KERN_INFO "b43legacy: 30/32-bit DMA poked\n");
   }

   static void op32_tx_suspend(struct b43legacy_dmaring *ring)

Index: wireless-testing/drivers/net/wireless/b43legacy/main.c
===================================================================
--- wireless-testing.orig/drivers/net/wireless/b43legacy/main.c
+++ wireless-testing/drivers/net/wireless/b43legacy/main.c
@@ -743,6 +743,7 @@ static void handle_irq_transmit_status(s
          u16 tmp;
          struct b43legacy_txstatus stat;

+       printk(KERN_INFO "b43legacy: entered
handle_irq_transmit_status\n");
          while (1) {
                  v0 = b43legacy_read32(dev, B43legacy_MMIO_XMITSTAT_0);
                  if (!(v0 & 0x00000001))

My intention was to be certain that the DMA operation had been
"poked", and to see if an interrupt resulted. I see the poke, but not
the interrupt, as follows:

phy0: TX to low-level driver (len=32) FC=0x0040 DUR=0x0000
A1=ff:ff:ff:ff:ff:ff A2=00:06:25:1c:99:a0 A3=ff:ff:ff:ff:ff:ff
b43legacy: 30/32-bit DMA poked

Do you have any suggestions on what might be wrong? Where should I
place printk's to find out where the DMA process is failing? Besides
the transmit problem, I never see any AP's with an "iwlist scan"
command, so it is likely that receiving is also not functioning.

Larry


_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to