linux-toradex.git/drivers/net/wireless/b43legacy, branch v2.6.25.12

b43legacy: Fix possible NULL pointer dereference in DMA code

2008-07-24T16:14:04+00:00

commit 2f9ec47d0954f9d2e5a00209c2689cbc477a8c89 upstream

This fixes a possible NULL pointer dereference in an error path of the
DMA allocation error checking code. This is also necessary for a future
DMA API change that is on its way into the mainline kernel that adds
an additional dev parameter to dma_mapping_error().

Signed-off-by: Michael Buesch 
Signed-off-by: John W. Linville 
Signed-off-by: Greg Kroah-Hartman

b43legacy: Do not return TX_BUSY from op_tx

2008-07-24T16:14:01+00:00

Never return TX_BUSY from op_tx. It doesn't make sense to return
TX_BUSY, if we can not transmit the packet.
Drop the packet and return TX_OK.

Upstream commit is
eb803e419ca6be06ece2e42027bb4ebd8ec09f91

Signed-off-by: Michael Buesch 
Signed-off-by: Greg Kroah-Hartman

b43legacy: fix DMA mapping leakage

2008-04-15T19:04:36+00:00

This fixes a DMA mapping leakage in the case where we reject a DMA buffer
because of its address.
The patch by Michael Buesch has been ported to b43legacy.

Signed-off-by: Stefano Brivio 
Cc: Christian Casteyde 
Signed-off-by: John W. Linville

b43legacy: Fix usage of struct device used for DMAing

2008-04-15T19:04:35+00:00

This fixes b43legacy for the SSB DMA API change.

Signed-off-by: Michael Buesch 
Cc: Stefano Brivio 
Signed-off-by: John W. Linville

b43legacy: fix initvals loading on bcm4303

2008-04-15T19:04:34+00:00

This allows for the correct initial values to be uploaded to bcm4303
devices. It should be correct, but I can't reliably test this as I suspect
there's something going wrong with an hardware rfkill switch on my laptop.
Please test.

Signed-off-by: Stefano Brivio 
Signed-off-by: John W. Linville

b43legacy: Fix module init message

2008-03-04T23:36:39+00:00

This fixes the module init message to tell that the legacy
driver loaded. This makes it less confusing, in case both drivers are loaded.

Signed-off-by: Michael Buesch 
Signed-off-by: John W. Linville

Use a separate config option for the b43 pci to ssb bridge.

2008-02-28T14:13:10+00:00

The bridge code was unnecessary enabled by the b44
driver, but it prevents the bcm43xx driver from
being loaded, as the bridge claims the same pci ids.

Now we enable the birdge only if the b43{legacy}
drivers are selected.

Signed-off-by: Alexey Zaytsev 
Acked-by: Larry Finger 
Signed-off-by: John W. Linville

b43legacy: Add driver load messages

2008-02-15T18:44:19+00:00

This adds printk messages with basic information about the driver being loaded.
This information includes a summary of the compiled-in features, which
simplifies bug-reporting and debugging a lot.
Also a firmware ID is printed. This is a unique identifier blob for a specific
version of the firmware. This ID is attached to a specific version of the firmware
blob in b43-fwcutter (see fwcutter git).
This helps users to select the right firmware for their device.
This also makes it possible to use automated scripts to fetch and extract the right
firmware for the driver. (The script will grep the .ko for the "Firmware-ID: xxx" string.)
While the driver might still support other versions of the firmware for backward
compatibility, this will always print out the officially supported version, which
people _should_ use.

Signed-off-by: Stefano Brivio 
Signed-off-by: John W. Linville

b43legacy: fix firmware load message level

2008-02-15T18:44:19+00:00

The firmware version information should always get printed. Not only on a
debug build.

The patch by Michael Buesch has been ported to b43legacy.

Signed-off-by: Stefano Brivio 
Signed-off-by: John W. Linville

b43legacy: add firmware information to modinfo

2008-02-15T18:44:19+00:00

This adds the firmware ID to modinfo.

The patch by Michael Buesch has been ported to b43legacy.

Signed-off-by: Stefano Brivio 
Signed-off-by: John W. Linville