From: Michel Lanners <mlan@cpu.lu>
To: grant@borg.umn.edu
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Grabbing an Interrupt for a Brain-dead PCI Device
Date: Tue, 7 Mar 2000 23:00:27 +0100 (CET) [thread overview]
Message-ID: <200003072200.XAA00434@piglet.grunz.lu> (raw)
In-Reply-To: <Pine.SGI.4.21.0003071435240.45384-100000@brule.borg.umn.edu>
Hi there,
On 7 Mar, this message from Grant Erickson echoed through cyberspace:
> The device has an interrupt at INTA#. Unfortunately, the device being dumb
> as it is, doesn't utilize the interrupt pin register to advertise that it
> does in fact have an interrupt there. So, I assume that once again, the
> PROM doesn't give it one.
Of course not... how should it know? But....
> Is there a way, in Linux, for me to programmatically and manually assign
> an interrupt to this device as might have been done in the PROM? I'm
> guessing I have to twiddle some registers in the North Bridge, correct?
As far as I know, yes, it depends on the host bridge. However, I don't
think there's any bridge configuration involved here, as the interrupt
pin routing would rather be done in hardware.
If this is in a PowerMac (at least those previous to UMA), then there
is a fixed IRQ per physical slot. All 4 PCI interrupt lines are OR'ed
together per slot.
However, there are other IRQ routing schemes as well... the above being
the easiest one, because the IRQ value can be hardcoded based on the
slot, which you can determine by software.
Plus, there are ways to determine an unknown IRQ by letting the device
generate an interrupt, and seing what IRQ it comes in on. You might
find more info in 'Linux Device Drivers' by Alessandro Rubini.
Michel
-------------------------------------------------------------------------
Michel Lanners | " Read Philosophy. Study Art.
23, Rue Paul Henkes | Ask Questions. Make Mistakes.
L-1710 Luxembourg |
email mlan@cpu.lu |
http://www.cpu.lu/~mlan | Learn Always. "
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-03-07 22:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-05 21:30 HELP: Power Mac G3 PCI Strangeness in 2.2 and 2.3 Grant Erickson
2000-03-06 11:04 ` Geert Uytterhoeven
2000-03-07 20:40 ` Grabbing an Interrupt for a Brain-dead PCI Device Grant Erickson
2000-03-07 21:00 ` Geert Uytterhoeven
2000-03-07 22:00 ` Michel Lanners [this message]
2000-03-08 8:31 ` Geert Uytterhoeven
2000-03-08 14:15 ` Matt Porter
2000-03-08 18:47 ` Grant Erickson
2000-03-08 19:12 ` Geert Uytterhoeven
2000-03-09 6:58 ` Michel Lanners
2000-03-09 12:52 ` Gabriel Paubert
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=200003072200.XAA00434@piglet.grunz.lu \
--to=mlan@cpu.lu \
--cc=grant@borg.umn.edu \
--cc=linuxppc-dev@lists.linuxppc.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).