On Mon, 2007-08-06 at 13:05 -0400, John W. Linville wrote:
--- a/net/mac80211/ieee80211.c
+++ b/net/mac80211/ieee80211.c
@@ -3030,9 +3030,10 @@ ieee80211_rx_h_data(struct ieee80211_txrx_data *rx)
memcpy(dst, hdr-addr1, ETH_ALEN);
memcpy(src, hdr-addr3, ETH_ALEN);
On Fri, Aug 17, 2007 at 02:52:56AM +0200, Johannes Berg wrote:
On Mon, 2007-08-06 at 13:05 -0400, John W. Linville wrote:
--- a/net/mac80211/ieee80211.c
+++ b/net/mac80211/ieee80211.c
@@ -3030,9 +3030,10 @@ ieee80211_rx_h_data(struct ieee80211_txrx_data *rx)
memcpy(dst,
Kay Sievers wrote:
On 8/17/07, Larry Finger [EMAIL PROTECTED] wrote:
A new driver for the Broadcom BCM43xx devices has been written that uses
mac80211, rather than
softmac. The newest versions of the Broadcom firmware does not support all
the BCM devices.
Accordingly, a separate driver is
On Thu, Aug 16, 2007 at 06:40:23PM -0500, Larry Finger wrote:
Has anyone used the new driver variation known as b43 from that branch of
wireless-dev and gotten
auto-loading at bootup of the b43 module on i386 or x86_64 platforms. It
still doesn't work here
even after upgrading to the
John W. Linville wrote:
On Thu, Aug 16, 2007 at 06:40:23PM -0500, Larry Finger wrote:
Has anyone used the new driver variation known as b43 from that branch of
wireless-dev and gotten
auto-loading at bootup of the b43 module on i386 or x86_64 platforms. It
still doesn't work here
even
Michael,
Now that I have solved the module loading problem on my openSUSE 10.2 systems,
I'm nearly ready to
push the b43legacy patch to John.
Is it your plan to stay with the current firmware naming scheme, or are you
going to change to what
Johannes proposed?
For the help text in b43's
On Friday 17 August 2007 01:40:23 Larry Finger wrote:
Has anyone used the new driver variation known as b43 from that branch of
wireless-dev and gotten auto-loading at bootup of the b43 module on i386 or
x86_64 platforms. It still doesn't work here even after upgrading to the
latest version of
On Friday 17 August 2007 18:12:05 Larry Finger wrote:
Michael,
Now that I have solved the module loading problem on my openSUSE 10.2
systems, I'm nearly ready to
push the b43legacy patch to John.
Is it your plan to stay with the current firmware naming scheme, or are you
going to
On Friday 17 August 2007 20:11:23 Larry Finger wrote:
The help text in Kconfig for b43 is updated to indicate the devices that it
does not support and to note that it can coexist with b43legacy.
Signed-off-by: Larry Finger [EMAIL PROTECTED]
Queued, thanks!
--
Greetings Michael.
The help text in Kconfig for b43 is updated to indicate the devices that it
does not support and to note that it can coexist with b43legacy.
Signed-off-by: Larry Finger [EMAIL PROTECTED]
---
Index: wireless-dev/drivers/net/wireless/b43/Kconfig
Synopsis:
With everything tree and b43, loses AP association but then
reassociates, usually on ARP request.
I realize there's a tcpdump in there and that doesn't really provide any
useful info... the key is the iwevent and generating traffic.
Duplicating:
1. Use a 4311
2. Load b43
From: Johannes Berg [EMAIL PROTECTED]
The auto-loading mechanism from ssb to b43 is case sensitive; however, the
present code is generating a lower-case a for the BCM4311, which has an
802.11 core with revision 10.
Signed-off-by: Johannes Berg [EMAIL PROTECTED]
Signed-off-by: Larry Finger [EMAIL
On Fri, 2007-08-17 at 17:37 -0500, Larry Finger wrote:
ret = add_uevent_var(envp, num_envp, i,
buffer, buffer_size, length,
- MODALIAS=ssb:v%.4xid%.4xrev%.2x,
+ MODALIAS=ssb:v%.4xid%.4xrev%.2X,
13 matches
Mail list logo
