git and 4311

Hi all , i have a 4311 (laptop hp nx7400)
10:00.0 0280: 14e4:4311 (rev 01)
        Subsystem: 103c:1364
        Flags: bus master, fast devsel, latency 0, IRQ 11
        Memory at f4000000 (32-bit, non-prefetchable) [size=16K]
        Capabilities: [40] Power Management version 2
        Capabilities: [58] Message Signalled Interrupts: Mask- 64bit-
Queue=0/0 Enable-
        Capabilities: [d0] Express Legacy Endpoint IRQ 0

10:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN
Mini-PCI Card (rev 01)

i checked the netdev git tree (it say 2.6.19-rc6)
im (newbie in git too ) but
i do not have notice for my card, in dmesg do not show anything related
to this, any idea to continue?

tnks all!

Re: git and 4311

Fernando Toledo wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi all , i have a 4311 (laptop hp nx7400)
> 10:00.0 0280: 14e4:4311 (rev 01)
>         Subsystem: 103c:1364
>         Flags: bus master, fast devsel, latency 0, IRQ 11
>         Memory at f4000000 (32-bit, non-prefetchable) [size=16K]
>         Capabilities: [40] Power Management version 2
>         Capabilities: [58] Message Signalled Interrupts: Mask- 64bit-
> Queue=0/0 Enable-
>         Capabilities: [d0] Express Legacy Endpoint IRQ 0
> 
> 
> 10:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN
> Mini-PCI Card (rev 01)
> 
> i checked the netdev git tree (it say 2.6.19-rc6)
> im (newbie in git too ) but
> i do not have notice for my card, in dmesg do not show anything related
> to this, any idea to continue?
> 
> tnks all!

The 4311 is a PCI-E card. The mainline kernels 2.6.18 and 2.6.19 do not support this hardware. For 
it, you need to get the patch "ftp://lwfinger.dynalias.org/patches/patch_2.6.18.1_for_PCI-E". 
Despite the name, it should apply to 2.6.18 or 2.6.19.

Larry

Patch for > 1 GB RAM (12/01 version)

Will and Andrew,

Attached is the next round of the > 1 GB RAM patch. The main change is to use pci_alloc_coherent 
rather than dma_alloc_consistent to get the proper memory. That was the only difference between our 
code and the b44 driver, which is supposed to work.

Good luck and again my thanks for letting me crash your machines vicariously.

Larry

Index: wireless-2.6/drivers/net/wireless/bcm43xx/bcm43xx_dma.c
===================================================================
--- wireless-2.6.orig/drivers/net/wireless/bcm43xx/bcm43xx_dma.c
+++ wireless-2.6/drivers/net/wireless/bcm43xx/bcm43xx_dma.c
 <at>  <at>  -147,13 +147,55  <at>  <at>  dma_addr_t map_descbuffer(struct bcm43xx
 	dma_addr_t dmaaddr;

 	if (tx) {
-		dmaaddr = dma_map_single(&ring->bcm->pci_dev->dev,
+		dmaaddr = pci_map_single(ring->bcm->pci_dev,
 					 buf, len,
-					 DMA_TO_DEVICE);
+					 PCI_DMA_TODEVICE);
+
+		/* Hardware bug work-around, the chip is unable to do PCI DMA
+		   to/from anything above 1GB  */
+		if (dma_mapping_error(dmaaddr) ||
+		    dmaaddr + len > ring->bcm->dma_mask) {
+			/* Sigh... */

431 and pcie patch results

hi , i patch my kernel 2.6.18.3 with the PCI_E patch to probe my 4311 card

ntbkragnarok:/usr/src# patch -p0
</home/ragnarok/download/nx7400/patch_2.6.18.1_for_PCI-E
patching file linux-2.6.18.orig/drivers/net/wireless/bcm43xx/bcm43xx_dma.h
patching file linux-2.6.18.orig/drivers/net/wireless/bcm43xx/bcm43xx_main.c
Hunk #10 succeeded at 3715 (offset 8 lines).
Hunk #11 succeeded at 4066 (offset 8 lines).
Hunk #12 succeeded at 4083 (offset 8 lines).
patching file linux-2.6.18.orig/drivers/net/wireless/bcm43xx/bcm43xx_dma.c
patching file linux-2.6.18.orig/drivers/net/wireless/bcm43xx/bcm43xx.h
patching file linux-2.6.18.orig/drivers/net/wireless/bcm43xx/bcm43xx_power.c

i have some advances but still do not connect

modprobe bcm4311 work and seems to detect the board

bcm43xx driver
PCI: Enabling device 0000:10:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:10:00.0[A] -> GSI 17 (level, low) -> IRQ 177
PCI: Setting latency timer of device 0000:10:00.0 to 64
bcm43xx: Chip ID 0x4311, rev 0x1
bcm43xx: Number of cores: 4
bcm43xx: Core 0: ID 0x800, rev 0x11, vendor 0x4243, enabled
bcm43xx: Core 1: ID 0x812, rev 0xa, vendor 0x4243, enabled
bcm43xx: Core 2: ID 0x817, rev 0x3, vendor 0x4243, disabled
bcm43xx: Core 3: ID 0x820, rev 0x1, vendor 0x4243, enabled
bcm43xx: PHY connected
bcm43xx: Detected PHY: Version: 4, Type 2, Revision 8

Re: 4311 and pcie patch results

[Freitag, 1. Dezember 2006 19:33] schrieb Fernando Toledo (wrote):

> here can be the problem, the channel do not change to 11 (2.462 GHz) and
> still in 14 ( Frequency=2.484 GHz)
>
> i do not see the AP's too
>
> my notebook is a hp nx7400 that have a button to activate/deactivate the
> wireless maybe this is the problem?
>
> any another steps to continue my tests?

Welcome to my problem...
loading and unloading ndiswrapper before loading bcm43xx makes a difference, 
but is not a solution. Can you check with another machine if it is sending 
something?

Gruß,
Jochen 
--

-- 
"In a world without fences and walls, who needs gates and windows?"

Das bessere Office kostenlos: http://de.openoffice.org/
Einfach der bessere Browser:  http://www.mozilla.com/firefox/all

_______________________________________________
Bcm43xx-dev mailing list
Bcm43xx-dev@...
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Re: 4311 and pcie patch results

Jochen Puchalla wrote:
> [Freitag, 1. Dezember 2006 19:33] schrieb Fernando Toledo (wrote):
> 
>> here can be the problem, the channel do not change to 11 (2.462 GHz) and
>> still in 14 ( Frequency=2.484 GHz)
>>
>> i do not see the AP's too
>>
>> my notebook is a hp nx7400 that have a button to activate/deactivate the
>> wireless maybe this is the problem?
>>
>> any another steps to continue my tests?
> 
> Welcome to my problem...
> loading and unloading ndiswrapper before loading bcm43xx makes a difference, 
> but is not a solution. Can you check with another machine if it is sending 
> something?

Jochen and Fernando,

Would you please run the command 'keypress' as root, press the button that turns the RF on/off and 
return the result. That will let us know if the button goes through the keyboard handler.

Thanks,

Larry

Re: 4311 and pcie patch results

Jochen Puchalla escribió:
> [Freitag, 1. Dezember 2006 19:33] schrieb Fernando Toledo (wrote):
> 
>> here can be the problem, the channel do not change to 11 (2.462 GHz) and
>> still in 14 ( Frequency=2.484 GHz)
>>
>> i do not see the AP's too
>>
>> my notebook is a hp nx7400 that have a button to activate/deactivate the
>> wireless maybe this is the problem?
>>
>> any another steps to continue my tests?
> 
> Welcome to my problem...
> loading and unloading ndiswrapper before loading bcm43xx makes a difference, 
> but is not a solution. Can you check with another machine if it is sending 
> something?
> 
> Gruß,
> Jochen 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Bcm43xx-dev mailing list
> Bcm43xx-dev@...
> https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Re: 4311 and pcie patch results

Fernando Toledo wrote:
> 
> hi! =(
> im not using ndiswrapper..
> i have a realtek pcmcia with kismet a cant see anything

The reason you don't see anything is that your radio is not turned on. At the moment, bcm43xx does 
not know what happens in the hardware when you push the RF KILL button on your keyboard. What Jochen 
does is load ndiswrapper and the Windows driver to turn on the radio, then unloads ndiswrapper and 
loads bcm43xx. In this process, the radio stays on.

He is running a test for me to see what differences there are in the radio registers between the two 
situations.

Larry

Re: Patch for > 1 GB RAM (12/01 version)

On 12/1/06, Larry Finger <Larry.Finger@...> wrote:
> Will and Andrew,
>
> Attached is the next round of the > 1 GB RAM patch. The main change is to use pci_alloc_coherent
> rather than dma_alloc_consistent to get the proper memory. That was the only difference between our
> code and the b44 driver, which is supposed to work.
>
> Good luck and again my thanks for letting me crash your machines vicariously.
>
> Larry

Well, it appears we're making slow but steady progress.  We're not
getting spammed with the 1-2-1-2-1-2 lines anymore, but we still do
wind up with an error.  No kernel panic, but the computer is still
rendered unusable.  (things like ifconfig hang, the keyboard doesn't
work, etc).

Here's the log:

bcm43xx driver
ACPI: PCI Interrupt 0000:00:0c.0[A] -> GSI 18 (level, low) -> IRQ 18
bcm43xx: Chip ID 0x4306, rev 0x3
bcm43xx: Number of cores: 5
bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243
bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243
bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243
bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243
bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243
bcm43xx: PHY connected
bcm43xx: Detected PHY: Version: 2, Type 2, Revision 2

Patch for > 1 GB RAM (12/01 version #2)

Will and Andrew,

The log from the 12/01 version looked encouraging; however, I wonder why allocating the RX buffer 
went well for a while, then crashed.

Attached is the next round of the > 1 GB RAM patch. I found one other place where the dma rather 
than pci layer was invoked, and I cleaned up the logic a bit. In addition, I put in a stack dump 
when level 2 fails so we know whence it came.

Good luck.

Larry

Index: wireless-2.6/drivers/net/wireless/bcm43xx/bcm43xx_dma.c
===================================================================
--- wireless-2.6.orig/drivers/net/wireless/bcm43xx/bcm43xx_dma.c
+++ wireless-2.6/drivers/net/wireless/bcm43xx/bcm43xx_dma.c
 <at>  <at>  -145,15 +145,40  <at>  <at>  dma_addr_t map_descbuffer(struct bcm43xx
 			  int tx)
 {
 	dma_addr_t dmaaddr;
+	int direction = PCI_DMA_FROMDEVICE;

-	if (tx) {
-		dmaaddr = dma_map_single(&ring->bcm->pci_dev->dev,
-					 buf, len,
-					 DMA_TO_DEVICE);
-	} else {