From: Larry Finger <larry.finger@lwfinger.net>
To: Michael Buesch <mb@bu3sch.de>
Cc: linux-wireless@vger.kernel.org, Bcm43xx-dev@lists.berlios.de
Subject: Re: bcm43xx-mac80211: a fix for the shared interrupt problem
Date: Sat, 28 Jul 2007 15:53:21 -0500 [thread overview]
Message-ID: <46ABACC1.1020107@lwfinger.net> (raw)
In-Reply-To: <200707281848.02554.mb@bu3sch.de>
Michael Buesch wrote:
>
> That's not the right bugfix.
> If the interface is not STAT_STARTED, it should _not_ generate IRQs.
> The bug is elsewhere in the init routines.
> Please find out which IRQ bits are generated for these spurious IRQs.
>
I trapped those entries where the interface was not STAT_STARTED and got 2 such interrupts, each
with the IRQ bits set to 0x00000001 (READY). They occur between the "30-bit DMA initialized" and the
"Wireless interface started" messages.
Larry
next prev parent reply other threads:[~2007-07-28 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-28 3:36 bcm43xx-mac80211: a fix for the shared interrupt problem Larry Finger
2007-07-28 16:48 ` Michael Buesch
2007-07-28 20:53 ` Larry Finger [this message]
2007-07-28 23:03 ` Michael Buesch
2007-07-28 23:58 ` Larry Finger
2007-07-29 8:54 ` Michael Buesch
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=46ABACC1.1020107@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).