Bug 8925
Summary: | poor connection with broadcom 4306rev02, native 43xx driver | ||
---|---|---|---|
Product: | Drivers | Reporter: | Bodo Graumann (delilahblue) |
Component: | network-wireless | Assignee: | Larry Finger (Larry.Finger) |
Status: | CLOSED CODE_FIX | ||
Severity: | normal | CC: | Larry.Finger |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | kernel 2.6.21+ | Subsystem: | |
Regression: | --- | Bisected commit-id: |
Description
Bodo Graumann
2007-08-23 02:03:04 UTC
This results from a typo in the specifications. When translated into code, it broke this particular model. It has now been reverted with the following commit: commit 829ef1f574a979f681959fd17f9bd698e878cda4 Author: John W. Linville <linville@tuxdriver.com> Date: Mon Aug 6 14:41:59 2007 -0400 Revert "[PATCH] bcm43xx: Fix deviation from specifications in set_baseband_attenuation" This reverts commit 77548f58070894cf5970a110981e511ffe793369. David Woodhouse wrote: >This broke my shinybook. I seem to get absolutely _no_ outgoing packets, >although I can receive OK. Larry Finger wrote: >Please revert this patch. Signed-off-by: John W. Linville <linville@tuxdriver.com> The complete failure of driver bcm43xx for this particular device should be fixed by the above reversion in 2.6.23-rc3. The temporary driver that was called bcm4301 has been abandoned. That effort has resulted in a driver named b43legacy that is in the wireless-dev git tree. On my system, that driver handles the BCM4306/2 device. Performance is not as good as other chips, but it is being worked on. I will certainly investigate all the changes since 2.6.20 to see which might be causing a regression in performance. If you have troubles with b43legacy, please report it on the Broadcom Linux mailing list at bcm43xx-dev@lists.berlios.de. Fixed in 2.6.23-rc3... |