From: David Monro <davidm@amberdata•demon.co.uk>
To: Gabriel Paubert <paubert@iram•es>
Cc: Linux/ppc Dev List <linuxppc-dev@lists•linuxppc.org>
Subject: Re: prep interrupt routing
Date: Mon, 17 Apr 2000 21:59:20 +0100 [thread overview]
Message-ID: <38FB7B28.9DFFDBE1@amberdata.demon.co.uk> (raw)
In-Reply-To: Pine.HPX.4.10.10004170952310.6016-100000@gra-ux1.iram.es
Gabriel Paubert wrote:
>
> On Fri, 14 Apr 2000, David Monro wrote:
>
[..]
> It looks like the output of my residual data dump code :-), and the first
> line shows a bug in my code (harmless, but then I had never found residual
> data which specifies that a device has no interrupt lines).
Yup; I found the commented out call to print_residual_device_info() in
prep_setup.c
>
> >
[..]
>
> Good...
>
> >
> > Of course putting all of the devices on irq 15 doesn't seem like a
> > particularly good idea. Does anybody know a) which chip is responsible
> > for the mapping and b) how to reprogram it?
>
[..]
The PCI-ISA bridge is the "IBM Fire Coral" chip - does anybody actually
have a part number for this chip so I can look it up on IBM's site?
>
> [root@vlab1 linux-test]# lspci -xxxsb.0
> 00:0b.0 ISA bridge: Symphony Labs W83C553 (rev 04)
> [snipped]
> 40: 24 04 00 00 ef ab 78 00 f1 00 00 00 00 33 04 00
> ^^^^^
> Or 0xabef in right byte order: meaning routing to IRQs 10/11/14/15,
> although I don't use these any more since the board has an OpenPIC (but
> PPCBUUG disagnostics would be very upset if I changed it).
>
> Regards,
> Gabriel.
Output from the above command:
prozac:~# lspci -xxxsb.0
00:0b.0 ISA bridge: IBM Fire Coral (rev 02)
00: 14 10 0a 00 07 00 00 04 02 00 01 06 00 00 00 00
10: 01 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 ff 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
I have no idea what any of this means :-) If I could find the IBM
datasheet I might have half a clue though.
Cheers,
David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-04-17 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-14 20:07 prep interrupt routing David Monro
2000-04-17 8:19 ` Gabriel Paubert
2000-04-17 20:59 ` David Monro [this message]
2000-04-18 18:20 ` 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=38FB7B28.9DFFDBE1@amberdata.demon.co.uk \
--to=davidm@amberdata$(echo .)demon.co.uk \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
--cc=paubert@iram$(echo .)es \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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