tracking of PCI address space
grundler at parisc-linux.org
Thu Apr 9 16:55:53 EST 2009
On Wed, Apr 08, 2009 at 03:53:55PM -0500, Kumar Gala wrote:
> I was wondering if we have anything that tracks regions associated with
> the "inbound" side of a pci_bus.
> What I mean is on embedded PPC we have window/mapping registers for both
> inbound (accessing memory on the SoC) and outbound (access PCI device
> MMIO, IO etc). The combination of the inbound & outbound convey what
> exists in the PCI address space vs CPU physical address space (and how to
> map from one to the other).
Most PCI Host bus controllers will negatively decode the outbound ranges
for inbound traffic.
PARISC and IA64 have extra registers to play some games with that. But
routing between PCI bus controllers to make them look like a single PCI
segment was the main intent of that. I've not found any other uses
to subvert that.
> Today in the PPC land we only attach
> outbound windows to the pci_bus. So technically the inbound side
> information (like what subset of physical memory is visible on the PCI
> bus) seems to be lost.
What did you need inbound "routing map" for?
More information about the Linuxppc-dev