From: jingai <jingai@floatingpenguins.com>
To: Benjamin Herrenschmidt <bh40@calva.net>
Cc: debian-powerpc@lists.debian.org
Subject: Re: Re: Status of PCI-PCI bridge on UMAX S900
Date: Wed, 27 Dec 2000 18:12:14 -0500 [thread overview]
Message-ID: <200012272312.RAA03294@lists.linuxppc.org> (raw)
In-Reply-To: <19341121033813.21271@192.168.1.2>
> >Hello, I am just curious if anyone is working on getting the PCI-PCI
> >bridge code working for the UMAX S900
>
> [...snip...]
>
> I had no time to fix that yet. email me in a couple of weeks, I'll have
> finished moving and my boxes will be back up.
Ok, np.
> Note that it's not similar to the 9500, the 9500 has 2 host bridges while
> you have only one with a PCI<->PCI bridge, the interrupt problem appear
> to be specific to this configuration on an oldworld machine.
Ahh, ok, I was under the impression that the 9500 also had p2p bridge,
didn't know it actually had two host controllers...
> If you want to give it a look by yourself, the code that gets the
> interrupt numbers is in arch/ppc/prom.c. Look at the bits that use the
> "AAPL,interrupt" property and modify it slightly so that when it can't
> find it, it looks for the parent.
Ok, here is where you can call me stupid :) I just did have a long look
over the code, but bear in mind, this is the first time I've really looked
at any of the PPC-specific code (or much of any of it for that matter).
Here is what I tried, which didn't work, so maybe you could give me
a few more hints:
(this is repeated for every instance)
ip = (int *) get_property(np, "AAPL,interrupts", &l);
if (ip == 0)
ip = (int *) get_property(np, "interrupts", &l);
++ if (ip == 0)
++ ip = (int *) get_property(np, "interrupt-parent", &l);
I also tried:
++ if (ip == 0)
++ ip = (int *) get_property(npi->parent, "AAPL,interrupts", &l);
Forgive me for my ignorance, but as I said, this is my first time even
looking at it :)
TIA for any help,
jonathan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-12-27 23:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <j-jvNB.A.O4F.4jrR6@murphy>
2000-12-27 10:06 ` Status of PCI-PCI bridge on UMAX S900 Benjamin Herrenschmidt
2000-12-27 23:12 ` jingai [this message]
2000-12-28 4:05 ` jingai
2000-12-28 14:13 ` Chas Williams
2000-12-29 0:16 jingai
-- strict thread matches above, loose matches on Subject: below --
2001-01-04 19:19 Tibor Pausz
2001-01-04 20:41 ` Benjamin Herrenschmidt
2001-01-04 22:48 ` jingai
2001-01-04 22:53 David Edelsohn
2001-01-05 12:58 ` jingai
2001-01-05 14:24 ` Benjamin Herrenschmidt
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=200012272312.RAA03294@lists.linuxppc.org \
--to=jingai@floatingpenguins.com \
--cc=bh40@calva.net \
--cc=debian-powerpc@lists.debian.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).