From: Larry Finger <Larry.Finger@lwfinger.net>
To: Jack Schneider <puck@dp-indexing.com>
Cc: Peter Stuge <stuge-linux-pcmcia@cdy.org>,
"linux-pcmcia@lists.infradead.org"
<linux-pcmcia@lists.infradead.org>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: Problem with exclusive interrupt in hostap_cs
Date: Tue, 21 Apr 2009 11:49:39 -0500 [thread overview]
Message-ID: <49EDF923.2020102@lwfinger.net> (raw)
In-Reply-To: <20090421103617.05737b01@dp-indexing.com>
Jack Schneider wrote:
>
> Hi, All
> Tried the orinoco_cs driver last nite and got an error, something like;
> device not supported..
>
> Thanks for trying..
I took a second look at the code and found that other drivers are using the
routine prism2_interrupt() with shared interrupts, thus the patch below should
be all that is needed.
I trust that you will be able to build the patched driver.
Larry
Index: wireless-testing/drivers/net/wireless/hostap/hostap_cs.c
===================================================================
--- wireless-testing.orig/drivers/net/wireless/hostap/hostap_cs.c
+++ wireless-testing/drivers/net/wireless/hostap/hostap_cs.c
@@ -666,7 +666,8 @@ static int prism2_config(struct pcmcia_d
* irq structure is initialized.
*/
if (link->conf.Attributes & CONF_ENABLE_IRQ) {
- link->irq.Attributes = IRQ_TYPE_EXCLUSIVE | IRQ_HANDLE_PRESENT;
+ link->irq.Attributes = IRQ_TYPE_DYNAMIC_SHARING |
+ IRQ_HANDLE_PRESENT;
link->irq.IRQInfo1 = IRQ_LEVEL_ID;
link->irq.Handler = prism2_interrupt;
link->irq.Instance = dev;
next prev parent reply other threads:[~2009-04-21 16:50 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 ` Problem with exclusive interrupt in hostap_cs Larry Finger
2009-04-20 22:57 ` Peter Stuge
[not found] ` <20090421103617.05737b01@dp-indexing.com>
2009-04-21 16:49 ` Larry Finger [this message]
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=49EDF923.2020102@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=puck@dp-indexing.com \
--cc=stuge-linux-pcmcia@cdy.org \
/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).