summaryrefslogtreecommitdiffstats
path: root/arch
diff options
context:
space:
mode:
authorGrant Grundler <grundler@parisc-linux.org>2006-01-10 20:47:57 -0500
committerKyle McMartin <kyle@duet.int.mcmartin.ca>2006-01-10 21:52:11 -0500
commit5cdb8205e917c09fd1348e4b22e26492e8c45b36 (patch)
tree0ad6ed7bba30e60dacd827ae6a8c512dfa5bc141 /arch
parent6ca45a24ccb847251f71aec8906746d33e99f33e (diff)
downloadop-kernel-dev-5cdb8205e917c09fd1348e4b22e26492e8c45b36.zip
op-kernel-dev-5cdb8205e917c09fd1348e4b22e26492e8c45b36.tar.gz
[PARISC] Fix BLK_BOUNCE_HIGH on parisc by initializing max_low_pfn
max_low_pfn was not being set in arch/parisc/mm/init.c, causing severe problems whenever anything tried to use BLK_BOUNCE_HIGH. Set it to max_pfn like other similar architectures do. Signed-off-by: Grant Grundler <grundler@parisc-linux.org> Signed-off-by: Kyle McMartin <kyle@parisc-linux.org>
Diffstat (limited to 'arch')
-rw-r--r--arch/parisc/mm/init.c7
1 files changed, 7 insertions, 0 deletions
diff --git a/arch/parisc/mm/init.c b/arch/parisc/mm/init.c
index f2e7f13..720287d 100644
--- a/arch/parisc/mm/init.c
+++ b/arch/parisc/mm/init.c
@@ -300,6 +300,13 @@ static void __init setup_bootmem(void)
max_pfn = start_pfn + npages;
}
+ /* IOMMU is always used to access "high mem" on those boxes
+ * that can support enough mem that a PCI device couldn't
+ * directly DMA to any physical addresses.
+ * ISA DMA support will need to revisit this.
+ */
+ max_low_pfn = max_pfn;
+
if ((bootmap_pfn - bootmap_start_pfn) != bootmap_pages) {
printk(KERN_WARNING "WARNING! bootmap sizing is messed up!\n");
BUG();
OpenPOWER on IntegriCloud