From: Ralph Blach <rcblach@raleigh.ibm.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: 405gp pci mapping registers
Date: Mon, 24 Jul 2000 12:48:33 -0400 [thread overview]
Message-ID: <397C7361.3E97D93D@raleigh.ibm.com> (raw)
The IBM405gp has 3 sets of PMM registers. These allow extreme
flexibility in mapping
the where and how the PCI memory is configured into processor memory.
Each set of registers consist of 4 32 bit registers.
register offset 0 is the local address register
4 is the mask/attribute register
8 is the PCI low address register
c is the PCI high address register.
Heres how is works.
The local address in the local address register are translated to the
address PCI address
specified in the PCI high/low address registers.
The mask register specifies the size of the area to be translated with
the least significant bit being an enable bit.
So if the local address register is specified at 0x80000000 and the PCI
low address registers 0x80000000, and the mask register is 0xffff0001,
then the bridge will translate
all address from the PLB bus 0x80000000 to pci address 0x80000000 with a
size of 64k.
This is interesting because since the 405gp has three sets of these
register leading to split mappings. A good example if this is when a
video card is placed into on of the pci slots along with a card that
needs a memory BAR are placed in a IBM walnut board.
The open bios will map the memory bar to 405 memory 0x80000000 to PCI
memory 0x80000000, and the video card will get the mapping 405 memory
0xa0000000 to pci memory 0x0.
This leads to a slit address map.
My question is this. How should we manage this kind of address
flexability?
Chip
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-07-24 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-24 16:48 Ralph Blach [this message]
2000-07-24 17:32 ` 405gp pci mapping registers Dan Malek
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=397C7361.3E97D93D@raleigh.ibm.com \
--to=rcblach@raleigh.ibm.com \
--cc=linuxppc-embedded@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).