| commit | 8db13a0e1e87ae2741ca1677caa90e9592c4cc43 | |
| author | Benjamin Herrenschmidt <benh@kernel.crashing.org> | |
| Thu, 31 Jul 2008 05:24:13 +0000 (31 15:24 +1000) | ||
| committer | Paul Mackerras <paulus@samba.org> | |
| Mon, 11 Aug 2008 00:09:56 +0000 (11 10:09 +1000) | ||
| tree | eefe3cd37ea1dc33d0878ecb9cb2f5f4dfc04105 | treesnapshot (tar.gz zip) |
| parent | b79998fc2e1144919b6b02acbd407a5db1f80ac0 | commitdiff |
powerpc/pci: Don't keep ISA memory hole resources in the tree
When we have an ISA memory hole (ie, a PCI window that allows us to
generate PCI memory cycles at low PCI address) mixed with other
resources using a different CPU <=> PCI mapping, we must not keep
the ISA hole in the bridge resource list.
If we do, things might start trying to allocate device resources
in there and will get the PCI addresses wrong.
This fixes it by arranging to remove the ISA memory hole resource in
this case. This fixes various cases of PCMCIA breakage on PowerBooks
using the MPC106 "grackle" bridge.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: Paul Mackerras <paulus@samba.org>
When we have an ISA memory hole (ie, a PCI window that allows us to
generate PCI memory cycles at low PCI address) mixed with other
resources using a different CPU <=> PCI mapping, we must not keep
the ISA hole in the bridge resource list.
If we do, things might start trying to allocate device resources
in there and will get the PCI addresses wrong.
This fixes it by arranging to remove the ISA memory hole resource in
this case. This fixes various cases of PCMCIA breakage on PowerBooks
using the MPC106 "grackle" bridge.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: Paul Mackerras <paulus@samba.org>
| arch/powerpc/kernel/pci-common.c | diffblobblamehistory |