From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Linuxppc-dev Development <linuxppc-dev@ozlabs.org>
Subject: Re: why does ppc64 require boards to call pci_devs_phb_init()?
Date: Fri, 01 May 2009 07:08:30 +1000 [thread overview]
Message-ID: <1241125710.29501.35.camel@pasglop> (raw)
In-Reply-To: <33403DE1-6AC2-49E9-9539-C520E4944D77@kernel.crashing.org>
On Thu, 2009-04-30 at 10:37 -0500, Kumar Gala wrote:
> looking at merging this in w/ppc32 and wondering why board code has to
> call pci_devs_phb_init() and not do it via pcibios_init()
As I said on IRC, not too sure at the moment, it could be due to some
ordering issues where pSeries needs the pci_dn's to be there before
pcibios_init(). We'll have to dig a bit on that one.
Cheers,
Ben.
prev parent reply other threads:[~2009-04-30 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 15:37 why does ppc64 require boards to call pci_devs_phb_init()? Kumar Gala
2009-04-30 18:04 ` Kumar Gala
2009-04-30 21:09 ` Benjamin Herrenschmidt
2009-04-30 21:08 ` Benjamin Herrenschmidt [this message]
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=1241125710.29501.35.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).