From: "Hommel, Thomas (GE Indust, GE Fanuc)" <Thomas.Hommel@gefanuc.com>
To: <linuxppc-dev@ozlabs.org>
Subject: Set up device tree for PCI bus
Date: Fri, 12 Oct 2007 12:48:03 +0200 [thread overview]
Message-ID: <62DDBB9E5E23CC4A929EE46F9427CEAF3682BB@BUDMLVEM04.e2k.ad.ge.com> (raw)
Hi all,
I'm wondering how to set up a proper device tree for a PCI bus. The bus
has a tree-like structure with several bridges and can be extended
dynamically (by adding PMC/XMC modules).
The structure looks like this:
----------------------
| MPC8641 |
| |
| BDF 0:0:0 |
----------------------
|
|Bus #1
|PCIe 8x
|
-----------------------------------------------
| PCIe switch | |
| ------------- |
| | BDF 1:0:0 | | =20
| ------------- |
| |Bus #2 |
| ----------------------------- |
| | | | |
| ----------- ------------ ----------- |
| |BDF 2:1:0| |BDF 2:2:0 | |BDF 2:3:0| |
| ----------- ------------ ----------- |
| |Bus #3 |Bus #5 |Bus #6 |
| |PCIe 4x |PCIe 2x |PCIe 2x |
-----------------------------------------------
| | |
----------- ------------ ----------- =20
|Bridge | |Expansion | |SATA | =20
|BDF 3:0:0| |Slot | |BDF 6:0:0| =20
----------- ------------ ----------- =20
|
|Bus #4
|PCI-X
----------------------
| |
------------ ------------=20
|VME Bridge| |PMC Slot | =20
|BDF 4:e:0 | |BDF 4:c:0 | =20
------------ ------------ =20
A problem is that the modules in the Expansion/PMC slot can contain more
bridges and therefore the bus numbering isn't fixed. For example, if the
PMC adds one more bus, #5 becomes #6 and #6 becomes #7.
Can I assign fixed resources for all the bridge parts of the system?
Thanks
Thomas
next reply other threads:[~2007-10-12 11:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 10:48 Hommel, Thomas (GE Indust, GE Fanuc) [this message]
2007-10-12 11:27 ` Set up device tree for PCI bus 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=62DDBB9E5E23CC4A929EE46F9427CEAF3682BB@BUDMLVEM04.e2k.ad.ge.com \
--to=thomas.hommel@gefanuc.com \
--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