From: Larry Finger <Larry.Finger@lwfinger.net>
To: Jouni Malinen <j@w1.fi>
Cc: Jack Schneider <puck@dp-indexing.com>,
"linux-pcmcia@lists.infradead.org"
<linux-pcmcia@lists.infradead.org>,
wireless <linux-wireless@vger.kernel.org>
Subject: Problem with exclusive interrupt in hostap_cs
Date: Mon, 20 Apr 2009 14:19:26 -0500 [thread overview]
Message-ID: <49ECCABE.40805@lwfinger.net> (raw)
In-Reply-To: <20090420101340.142b6bc6@dp-indexing.com>
Jouni,
This was posted on the PCMCIA mailing list by Jack Schneider:
> Hi, folks Using Debian Lenny OS with 2.6.28.2-486 kernel.
> I have a very old DEC VP575 laptop which I want to use as back-up
> server. I need two net connections. When I use a single pccard,
> wired, all is well. If I insert my second card, WIFI-Intersil Prism2.5
> I get the following /var/log/messages error:
> pcmcia: request for exclusive IRQ couuld not be fulfilled.
> pcmcia: the driver needs updating to supported shared IRQ lines
The two drivers being loaded are hostap_cs and xirc2ps_cs. The latter one is
coded to handle shared interrupts, but hostap_cs is not.
I would have no problem changing the driver interrupt registration in the
link->irq structure, but I was not quite sure how change prism2_interrupt() to
detect the shared case when the interrupt status register is 0xFFFF.
Could you please take a look at this?
Thanks,
Larry
next parent reply other threads:[~2009-04-20 19:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090420101340.142b6bc6@dp-indexing.com>
2009-04-20 19:19 ` Larry Finger [this message]
2009-04-20 22:57 ` Problem with exclusive interrupt in hostap_cs Peter Stuge
[not found] ` <20090421103617.05737b01@dp-indexing.com>
2009-04-21 16:49 ` Larry Finger
2009-07-27 13:50 ` Wolfram Sang
2009-07-27 22:28 ` Larry Finger
2009-07-28 8:34 ` Wolfram Sang
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=49ECCABE.40805@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=j@w1.fi \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=puck@dp-indexing.com \
/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).