From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ishizaki Kou <kou.ishizaki@toshiba.co.jp>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH 1/4] celleb: fix supporting for multiple pci domains
Date: Wed, 09 May 2007 17:50:02 +1000 [thread overview]
Message-ID: <1178697002.14928.157.camel@localhost.localdomain> (raw)
In-Reply-To: <200705090734.l497YJqU004144@toshiba.co.jp>
On Wed, 2007-05-09 at 16:34 +0900, Ishizaki Kou wrote:
> Celleb has multiple PCI host bridges (phbs). Previous boot logic gives
> non-overlapped bus IDs between PCI host bridges so you can identify
> PHB by bus ID. But newer boot logic gives same bus ID between PHBs (it
> gives bus ID 0 as root bus.) So we have to set 'phb->buid' as
> non-zero.
Shouldn't you obtain it from the device-tree ?
Ben.
next prev parent reply other threads:[~2007-05-09 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 7:34 [PATCH 1/4] celleb: fix supporting for multiple pci domains Ishizaki Kou
2007-05-09 7:50 ` Benjamin Herrenschmidt [this message]
2007-05-10 7:14 ` Ishizaki Kou
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=1178697002.14928.157.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=kou.ishizaki@toshiba.co.jp \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).