From: Jun Sun <jsun@mvista.com>
To: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr
Cc: Geert.Uytterhoeven@sonycom.com
Subject: How does PCI device get its interrupt vector?
Date: Wed, 19 Jul 2000 14:41:40 -0700 [thread overview]
Message-ID: <39762094.9F59676D@mvista.com> (raw)
I am trying to get DDB5476 working and got puzzled by the interrupt
vector thing.
The on-board ether chip, a PCI device, apparently indicates it generates
interrupts and has an interrupt vector of 123. Later on, when
tulip_open tries to call request_irq(123, ...), it returns with an error
because the vector is greater than 32.
Here are my questions :
1. Who wrote 123 to the ether chip? That does not sound right to me at
first place.
2. Assuming the ether chip returns 0xFF (an invalid interrupt vector,
which I believe is the correct behavior), which part of Linux is
responsible to figure out the correct interrupt vector? Here we do have
the interrupt pin information and interrupt routing information. So we
should be able to tell what is the right interrupt vector number.
Any hints? Thanks.
Jun
next reply other threads:[~2000-07-19 21:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-19 21:41 Jun Sun [this message]
2000-07-20 1:12 ` How does PCI device get its interrupt vector? Jun Sun
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=39762094.9F59676D@mvista.com \
--to=jsun@mvista.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=linux-mips@fnet.fr \
--cc=linux@cthulhu.engr.sgi.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