From: Nicolas Lavocat <nicolas.lavocat-s/S/64wAxt+H1Tvi1vFFB9BPR1lH4CV8@public.gmane.org>
To: devicetree-discuss
<devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org>
Subject: mapping a PCI bus
Date: Mon, 09 Mar 2009 11:42:04 +0100 [thread overview]
Message-ID: <49B4F27C.7040007@fr.thalesgroup.com> (raw)
Hy everybody!
I’m working on a project:
On a proprietary board, (with a PowerPC 7448), a minimal Linux has been
embedded. My first aim consist in using a graphic chipset on the board,
that is to say make work the PCI bus. For the address mapping, I try to
write a dts, using the dts of the mpc7448hpc2 board as a model. My
problem is that I don’t understand how to fill the field “range” of the
PCI. The “width” used and the number of range is different from on board
to an other where PCI is used. I read the PCI specification, and don’t
find anything about it.
Here is an extract of my dts, where the field in question is indicated
thanks to commentaries:
pci@70000000 { compatible = "abac-pci";
device_type = "pci";
#size-cells = <2>;
#address-cells = <3>;
#interrupt-cells = <1>;
reg = <0x70000000 0x1000>;
bus-range = <0 0>;
/* how can I know how to chose the number of range and their width?*/
ranges = <0x2000000 0x0 0xe0000000 0xe0000000 0x0 0x1a000000
0x1000000 0x0 0x0 0xfa000000 0x0 0x10000>;
…
};
Then, I have a second question: why PCI’s addresses seem to be
implemented on 96 bits, whereas the addressing is done on 32 bits?
Thanks for Your attention !
Nicolas Lavocat
next reply other threads:[~2009-03-09 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 10:42 Nicolas Lavocat [this message]
[not found] ` <49B4F27C.7040007-s/S/64wAxt+H1Tvi1vFFB9BPR1lH4CV8@public.gmane.org>
2009-03-09 17:25 ` mapping a PCI bus Mitch Bradley
-- strict thread matches above, loose matches on Subject: below --
2009-03-12 10:35 Nicolas Lavocat
[not found] ` <49B8E583.3070108-s/S/64wAxt+H1Tvi1vFFB9BPR1lH4CV8@public.gmane.org>
2009-03-12 18:20 ` Mitch Bradley
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=49B4F27C.7040007@fr.thalesgroup.com \
--to=nicolas.lavocat-s/s/64waxt+h1tvi1vffb9bpr1lh4cv8@public.gmane.org \
--cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.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