summaryrefslogtreecommitdiffstats
path: root/drivers/net
diff options
context:
space:
mode:
authorDavid S. Miller <davem@sunset.davemloft.net>2006-10-17 19:04:44 -0700
committerDavid S. Miller <davem@sunset.davemloft.net>2006-10-17 19:28:50 -0700
commit5aee87c43e3a71a4aa4e72b0dc2180e4952c0848 (patch)
tree7d53d2ffd49fba8815d1986bb8f07d8b0959c605 /drivers/net
parent7341df16a1f228be833e918cb42534a34381a37e (diff)
downloadop-kernel-dev-5aee87c43e3a71a4aa4e72b0dc2180e4952c0848.zip
op-kernel-dev-5aee87c43e3a71a4aa4e72b0dc2180e4952c0848.tar.gz
[SPARC64]: Fix PCI memory space root resource on Hummingbird.
For Hummingbird PCI controllers, we should create the root PCI memory space resource as the full 4GB area, and then allocate the IOMMU DMA translation window out of there. The old code just assumed that the IOMMU DMA translation base to the top of the 4GB area was unusable. This is not true on many systems such as SB100 and SB150, where the IOMMU DMA translation window sits at 0xc0000000->0xdfffffff. So what would happen is that any device mapped by the firmware at the top section 0xe0000000->0xffffffff would get remapped by Linux somewhere else leading to all kinds of problems and boot failures. While we're here, report more cases of OBP resource assignment conflicts. The only truly valid ones are ROM resource conflicts. Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud