[PATCH] b43: Fix rxheader channel parsing

This patch fixes the parsing of the RX data header channel field. The current code parses the header incorrectly and passes a wrong channel number and frequency for each frame to mac80211. The FIXMEs added by this patch don't matter for now as the code where they live won't get executed anyway.

Re: [PATCH] b43: Fix rxheader channel parsing

Michael Buesch wrote: This patch fixes the parsing of the RX data header channel field. The current code parses the header incorrectly and passes a wrong channel number and frequency for each frame to mac80211. The FIXMEs added by this patch don't matter for now as the code where they live

Re: [PATCH] b43: Fix rxheader channel parsing

On Wednesday 02 January 2008 19:52:08 Larry Finger wrote: Michael Buesch wrote: This patch fixes the parsing of the RX data header channel field. The current code parses the header incorrectly and passes a wrong channel number and frequency for each frame to mac80211. The FIXMEs added

Re: [PATCH] b43: Fix rxheader channel parsing

Michael Buesch wrote: Shouldn't you just drop this case? No B PHY devices will ever use b43 and the default branch will issue the WARN_ON anyway. I guess you misread the patch. I did indeed. Sorry. Larry ___ Bcm43xx-dev mailing list

Re: [PATCH] b43: Fix rxheader channel parsing

On Wednesday 02 January 2008 20:37:41 Ehud Gavron wrote: Happy New Year, Michael! :) Yeah, thanks. :) Happy New Year to everyone on the list. Let's work on making The Linux Wireless Year (tm) out of it. -- Greetings Michael. ___ Bcm43xx-dev

Device busy error

While using the b43legacy driver with my 4306 card, wpa_supplicant and iwconfig both report that the device is busy when trying to switch from monitor mode to managed mode after having used kismet or airodump-ng. So far the only resolution to the issue has been to rmmod and then modprobe the

Re: Device busy error

On Wednesday 02 January 2008 21:18:29 David Ellingsworth wrote: While using the b43legacy driver with my 4306 card, wpa_supplicant and iwconfig both report that the device is busy when trying to switch from monitor mode to managed mode after having used kismet or airodump-ng. So far the

Re: Device busy error

You have a bogus Reply-To: [EMAIL PROTECTED] inside of your mailheaders, which confuses mailclients. See the attached bounce. -- Greetings Michael. This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients.