summaryrefslogtreecommitdiffstats
path: root/sys/ia64/include/md_var.h
diff options
context:
space:
mode:
authormarcel <marcel@FreeBSD.org>2004-02-22 02:10:48 +0000
committermarcel <marcel@FreeBSD.org>2004-02-22 02:10:48 +0000
commit2a9068ac03f4d66f08009d4aa0bb2ec199ae8030 (patch)
treeab398a173ed6ac6fd5954e9f4e98044f95caf7b2 /sys/ia64/include/md_var.h
parent9576df9a828ddb44a5aa60c1a938a251ab4506d9 (diff)
downloadFreeBSD-src-2a9068ac03f4d66f08009d4aa0bb2ec199ae8030.zip
FreeBSD-src-2a9068ac03f4d66f08009d4aa0bb2ec199ae8030.tar.gz
Do not pre-map the I/O port space. On the Intel Tiger 4 this conflicts
with a memory mapped I/O range that's immediately before it and is not 256MB aligned. As a result, when an address is accessed in the memory mapped range and a direct mapping is added for it, it overlaps with the pre-mapped I/O port space and causes a machine check. Based on a patch from: arun@
Diffstat (limited to 'sys/ia64/include/md_var.h')
-rw-r--r--sys/ia64/include/md_var.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/sys/ia64/include/md_var.h b/sys/ia64/include/md_var.h
index a9a3dfd..4946709 100644
--- a/sys/ia64/include/md_var.h
+++ b/sys/ia64/include/md_var.h
@@ -63,7 +63,6 @@ void ia64_probe_sapics(void);
int interrupt(uint64_t, struct trapframe *);
void map_gateway_page(void);
void map_pal_code(void);
-void map_port_space(void);
void os_boot_rendez(void);
void os_mca(void);
void spillfd(void *src, void *dst);
OpenPOWER on IntegriCloud