From: Benjamin Herrenschmidt <bh40@calva.net>
To: David Edelsohn <dje@watson.ibm.com>,
linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Status of PCI-PCI bridge on UMAX S900
Date: Thu, 4 Jan 2001 22:17:31 +0100 [thread overview]
Message-ID: <19341129144915.19004@mailhost.mipsys.com> (raw)
In-Reply-To: <200101042057.PAA38658@mal-ach.watson.ibm.com>
> "interrupts" property is well-defined in the OF spec for each
>device-tree node, but I do not think that prom.c currently has enough
>parsing ability to handle the complexity or makes too many assumption.
>And it does not need to fully parse that property, as Ben suggests.
I didn't say it wasn't well defined ;) I said it's usage by Apple is not.
prom.c has an interrupt tree parser that is used only on newworld macs
(they have a valid interrupt tree) and only when booting via Open
Firmware (booting via MacOS kills too much infos from the device tree to
be able to parse the interrupt tree any more).
I think it's also used on CHRP.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-04 21:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-29 0:16 Re: Status of PCI-PCI bridge on UMAX S900 jingai
2000-12-29 15:09 ` Chas Williams
2001-01-04 19:19 ` Tibor Pausz
2001-01-04 20:41 ` Benjamin Herrenschmidt
2001-01-04 20:57 ` David Edelsohn
2001-01-04 21:17 ` Benjamin Herrenschmidt [this message]
2001-01-04 21:19 ` 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
2001-01-04 22:26 ` Chas Williams
2001-01-05 19:51 ` Tibor Pausz
-- strict thread matches above, loose matches on Subject: below --
2000-12-28 4:05 jingai
2000-12-28 14:13 ` Chas Williams
[not found] <j-jvNB.A.O4F.4jrR6@murphy>
2000-12-27 10:06 ` Benjamin Herrenschmidt
2000-12-25 3:03 jingai
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=19341129144915.19004@mailhost.mipsys.com \
--to=bh40@calva.net \
--cc=dje@watson.ibm.com \
--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).