Linux MIPS Architecture development
 help / color / mirror / Atom feed
* How does PCI device get its interrupt vector?
@ 2000-07-19 21:41 Jun Sun
  2000-07-20  1:12 ` Jun Sun
  0 siblings, 1 reply; 2+ messages in thread
From: Jun Sun @ 2000-07-19 21:41 UTC (permalink / raw)
  To: linux, linux-mips; +Cc: Geert.Uytterhoeven


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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2000-07-20  1:13 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-07-19 21:41 How does PCI device get its interrupt vector? Jun Sun
2000-07-20  1:12 ` Jun Sun

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox