From: Zwane Mwaikambo <zwane@linux.realnet.co.sz>
To: <matt@eee.nott.ac.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: PCI interrupts
Date: Tue, 6 Nov 2001 10:57:28 +0200 (SAST) [thread overview]
Message-ID: <Pine.LNX.4.33.0111061041001.7663-100000@netfinity.realnet.co.sz> (raw)
Matthew Clark said...
>(b) if it shouldn't have a unique number do I have to share the
>interrupt (with the usb controller) or can I change it to
>another address (by writing to the config space?)?
>If I have to share it how do I do this- (my card will generate a
>lot of interrupt traffic)?.
Assuming i386
>From my limited knowledge about the IRQ handling subsystems, you would
call arch/i386/irq.c:request_irq() with the appropriate flags, ie
SA_SHIRQ and any others you may require. I *think* you might also be able
to do dev->irq = irq_num and then do your request_irq() but you might
require a bit of voodoo inbetween.
Regards,
Zwane Mwaikambo
next reply other threads:[~2001-11-06 8:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-06 8:57 Zwane Mwaikambo [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-05 23:43 PCI interrupts Matthew Clark
2001-11-05 23:57 ` Alan Cox
2001-11-06 14:37 ` Tommy Reynolds
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=Pine.LNX.4.33.0111061041001.7663-100000@netfinity.realnet.co.sz \
--to=zwane@linux.realnet.co.sz \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@eee.nott.ac.uk \
/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).