From: Jeremy Fitzhardinge <jeremy@goop.org>
To: linuxppc-dev@lists.linuxppc.org
Cc: cort@cs.nmt.edu
Subject: Interrupt routing in prep_pci.c
Date: Wed, 10 Feb 1999 20:32:09 -0800 (PST) [thread overview]
Message-ID: <XFMail.990210203209.jeremy@goop.org> (raw)
Hi Cort/all,
I'm trying to work out what kernel/prep_pci.c is doing with interrupt routing.
I'm looking at the stuff in the standard 2.2 kernel, so perhaps there's a better
place for me to look.
Firstly, in route_pci_interrupts it does an inb(0x800) to get something to
determine the interrupt architecture of the board. What is this value, and
where does it come from?
Rather than having hard-coded tables, can't the interrupt routing be determined
from either firmware or the interrupt controller itself? The comment at the
top of the file is that this will go away soon. What are you planning to
replace it?
Background: I'm porting LinuxPPC to a Yellowknife-like board running Open
Firmware. It works well except that the drivers can't find their interrupts.
Thanks,
J
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next reply other threads:[~1999-02-11 4:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-11 4:32 Jeremy Fitzhardinge [this message]
1999-02-11 9:07 ` Interrupt routing in prep_pci.c Gabriel Paubert
1999-02-14 5:42 ` Troy Benjegerdes
1999-02-15 3:06 ` Jeremy Fitzhardinge
1999-02-15 9:25 ` Gabriel Paubert
1999-02-15 9:23 ` Gabriel Paubert
1999-02-21 16:56 ` Johnnie Peters
1999-02-21 18:28 ` Cort Dougan
1999-02-22 8:45 ` VALETTE Eric
1999-02-22 18:25 ` Cort Dougan
1999-02-22 18:06 ` VALETTE Eric
1999-02-22 19:26 ` Cort Dougan
1999-02-23 8:40 ` VALETTE Eric
1999-02-23 14:53 ` Johnnie Peters
1999-02-23 15:55 ` VALETTE Eric
1999-02-26 7:18 ` Cort Dougan
1999-02-26 8:53 ` VALETTE Eric
1999-02-26 18:54 ` Cort Dougan
1999-02-26 7:09 ` bootloader problems and linux/ppc developers tree Cort Dougan
1999-02-26 9:02 ` VALETTE Eric
1999-02-26 11:05 ` Gabriel Paubert
1999-02-23 20:39 ` Interrupt routing in prep_pci.c Matt Porter
1999-02-26 7:21 ` Cort Dougan
1999-03-02 16:56 ` Matt Porter
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=XFMail.990210203209.jeremy@goop.org \
--to=jeremy@goop.org \
--cc=cort@cs.nmt.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).