linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: <jingai@floatingpenguins.com>
Cc: David Edelsohn <dje@watson.ibm.com>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Re: Status of PCI-PCI bridge on UMAX S900
Date: Fri, 5 Jan 2001 15:24:33 +0100	[thread overview]
Message-ID: <19341130075617.28501@mailhost.mipsys.com> (raw)
In-Reply-To: <200101051258.GAA21989@lists.linuxppc.org>


>
>My guess would be probably, to be thorough.  But I'm no kernel
>expert, so anyone else have any comments?
>
>Although (again just guessing), I don't think many (if any) systems
>will have more than one PCI controller, or more than one bridge
>chip for that matter...

The best solution is probably to cleanup the current parsing mecanism in
prom.c to clearly separate the 3 cases:

 - Real OF with interrupt tree (CHRP, newworld mac booting via OF). This
one is already more or less separate.

 - OldWorld macs (booted either via OF or BootX/miBoot)

 - Newworld macs booted via BootX/miBoot


Only the second case should iterate the AAPL,interrupts parents, and in
this case, all parents should be iterated up to the top of the tree in
case of cascaded bridges. For now, your patch may be enough, I'll look
into cleaning all that up myself. The only "tricky" case is NewWorld macs
booted via BootX/miBoot. Those machine should use the OF interrupt tree.
Unfortunately, MacOS screws it up (we no longer have access to the
phandle's, and so can't follow the interrupt-parent links). So we rely on
other types of infos left by MacOS, but those seem to occasionally be
different on older newworld macs and core99 machines.


Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-01-05 14:24 UTC|newest]

Thread overview: 15+ 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
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 [this message]
2001-01-04 22:26     ` Chas Williams
2001-01-05 19:51       ` Tibor Pausz
     [not found] <j-jvNB.A.O4F.4jrR6@murphy>
2000-12-27 10:06 ` Benjamin Herrenschmidt
2000-12-27 23:12   ` jingai
2000-12-28  4:05   ` 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=19341130075617.28501@mailhost.mipsys.com \
    --to=bh40@calva.net \
    --cc=dje@watson.ibm.com \
    --cc=jingai@floatingpenguins.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).