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.
This will fix the resume hang.
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
---
John, this is a bugfix for 2.6.26.
Index:
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.
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
---
John, this is a bugfix for 2.6.26.
Index: wireless-testing/drivers/net/wireless/b43legacy/main.c
This fixes a possible MMIO access while the device is still down
from a suspend cycle. MMIO accesses with the device powered down
may cause crashes on certain devices.
Signed-off-by: Michael Buesch [EMAIL PROTECTED]
---
John, please queue for 2.6.26
Index:
On Fri, Jun 13, 2008 at 5:51 PM, Michael Buesch [EMAIL PROTECTED] wrote:
On Friday 13 June 2008 17:33:05 Pavel Roskin wrote:
...
applied, thanks.
BTW /* OK, done. Got the 4 samples. If we took less than 131 mS of
time should be /* OK, done. Got the 4 samples. If we took less than
131ms of
On Sat, Jun 14, 2008 at 3:53 PM, Michael Buesch [EMAIL PROTECTED] wrote:
This firmware does _only_ work on wireless core revisions 5, 6, 7, 8 or 10.
There are reports of it working on rev.9 cores. Is that possible?
(Resend of previous mail to the list.)
--
Vista: [V]iruses, [I]ntruders,
On Sunday 15 June 2008 20:20:27 Stefanik Gábor wrote:
On Sat, Jun 14, 2008 at 3:53 PM, Michael Buesch [EMAIL PROTECTED] wrote:
This firmware does _only_ work on wireless core revisions 5, 6, 7, 8 or 10.
There are reports of it working on rev.9 cores. Is that possible?
(Resend of previous
This same card works on an x86 and on this wl500gp (bcm4704) w/ asus
code. If I flash the same image on a bcm5352 (whr-hp-g54), the driver
loads, the firmware loads and I get scan results.
Both the x86 and the wl500gp used the same ssb code and b43 code and
firmware. I'm using yesterday's
