From: Stefano Brivio <stefano.brivio@polimi.it>
To: Andreas Schwab <schwab@suse.de>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Larry Finger <larry.finger@lwfinger.net>,
linux-wireless@vger.kernel.org, bcm43xx-dev@lists.berlios.de,
mb@bu3sch.de
Subject: Re: [PATCH v3] remove bcm43xx
Date: Tue, 20 Nov 2007 01:15:49 +0100 [thread overview]
Message-ID: <20071120011549.6b04bb4d@morte> (raw)
In-Reply-To: <jed4u5esbo.fsf@sykes.suse.de>
On Tue, 20 Nov 2007 00:19:55 +0100
Andreas Schwab <schwab@suse.de> wrote:
> Stefano Brivio <stefano.brivio@polimi.it> writes:
>
> > This is strange. Because it has been developed mainly on PPC. Plus, if
> > you could better define "does not work"
>
> See <http://marc.info/?l=linux-wireless&m=119356497407301&w=2>.
It looks like we don't get a valid txstatus even if the txstatus indicator
register told us we could read it. The only difference I can see between
bcm43xx and b43 here is that in bcm43xx we allowed the whole register to be
non-zero, while in b43 we check a bit only (as per v4 specs). Would you
mind to try this:
--- drivers/net/wireless/b43/main.c.orig 2007-11-20 01:12:12.186524483 +0100
+++ drivers/net/wireless/b43/main.c 2007-11-20 01:12:34.922702865 +0100
@@ -947,7 +947,7 @@
while (1) {
v0 = b43_read32(dev, B43_MMIO_XMITSTAT_0);
- if (!(v0 & 0x00000001))
+ if (!v0)
break;
v1 = b43_read32(dev, B43_MMIO_XMITSTAT_1);
(probably it's not the solution, I just want to see what happens then).
BTW, what firmware are you using? Michael, any clue?
--
Ciao
Stefano
next prev parent reply other threads:[~2007-11-20 0:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 19:21 [PATCH v3] remove bcm43xx Stefano Brivio
2007-11-19 22:00 ` Rafael J. Wysocki
2007-11-19 22:19 ` Stefano Brivio
2007-11-19 22:36 ` Andreas Schwab
2007-11-19 23:02 ` Rafael J. Wysocki
2007-11-19 23:13 ` Stefano Brivio
2007-11-19 23:19 ` Andreas Schwab
2007-11-20 0:15 ` Stefano Brivio [this message]
2007-11-20 9:58 ` Andreas Schwab
2007-11-20 15:09 ` Larry Finger
2007-11-20 15:18 ` Michael Buesch
2007-11-20 13:17 ` Johannes Berg
2007-11-20 14:07 ` Michael Buesch
2007-11-20 14:11 ` Andreas Schwab
2007-11-20 14:20 ` Michael Buesch
2007-11-20 14:24 ` Andreas Schwab
2007-11-20 14:47 ` Andreas Schwab
2007-11-21 0:25 ` Asheesh Laroia
2007-11-19 22:57 ` Rafael J. Wysocki
2007-11-20 2:33 ` Larry Finger
2007-11-20 13:18 ` Johannes Berg
2007-11-20 14:09 ` Michael Buesch
2007-11-20 23:26 ` Rafael J. Wysocki
2007-11-21 13:45 ` Michael Buesch
2007-11-21 13:59 ` schedule bcm43xx removal for 2.6.26 -- " John W. Linville
2007-11-21 14:16 ` [PATCH] bcm43xx: mark as obsolete and schedule for removal John W. Linville
2007-11-21 15:26 ` [PATCH v2] " John W. Linville
2007-11-21 15:46 ` Stefano Brivio
2007-11-21 15:00 ` schedule bcm43xx removal for 2.6.26 -- Re: [PATCH v3] remove bcm43xx Larry Finger
2007-11-21 15:39 ` Johannes Berg
2007-11-21 18:20 ` Michael Buesch
2007-11-21 20:26 ` [PATCH] softmac: mark as obsolete and schedule for removal John W. Linville
2007-11-21 19:35 ` schedule bcm43xx removal for 2.6.26 -- Re: [PATCH v3] remove bcm43xx Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071120011549.6b04bb4d@morte \
--to=stefano.brivio@polimi.it \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=rjw@sisk.pl \
--cc=schwab@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.