summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorkettenis <kettenis@openbsd.org>2008-07-23 17:39:35 +0000
committerkettenis <kettenis@openbsd.org>2008-07-23 17:39:35 +0000
commitf5d09e55be872cd4c3545c46fcfcac212b72f01b (patch)
treea8bcd41fe8cb1e8252a6f5ea4e11640cb5fcc744
parentfix stack abuse in the `time' commmand, using alloc()'d memory instead. (diff)
downloadwireguard-openbsd-f5d09e55be872cd4c3545c46fcfcac212b72f01b.tar.xz
wireguard-openbsd-f5d09e55be872cd4c3545c46fcfcac212b72f01b.zip
So it turns outthe HP engineers changed the PA-RISC 2.0 architecture
after it was published. In particular, they changed the maximum cache aliasing boundary from 1MB to 16MB. It turns that on the PA-8700 the aliasing boundary is actually 4MB (reported as such by the firmware at least). There are some comments in the Linux code that suggest that HP never actually built PA-RISC CPUs with an 8MB or 16MB aliasing boundary. So raise the aliasing boundary to 4MB. This fixes the weird ps(1) problem where it didn't print its own arguments correctly.
-rw-r--r--sys/arch/hppa/include/cpu.h8
1 files changed, 4 insertions, 4 deletions
diff --git a/sys/arch/hppa/include/cpu.h b/sys/arch/hppa/include/cpu.h
index d80bae1d2ed..243855f1096 100644
--- a/sys/arch/hppa/include/cpu.h
+++ b/sys/arch/hppa/include/cpu.h
@@ -1,4 +1,4 @@
-/* $OpenBSD: cpu.h,v 1.54 2008/07/18 23:43:31 art Exp $ */
+/* $OpenBSD: cpu.h,v 1.55 2008/07/23 17:39:35 kettenis Exp $ */
/*
* Copyright (c) 2000-2004 Michael Shalayeff
@@ -124,9 +124,9 @@ extern register_t kpsw;
* Exported definitions unique to hp700/PA-RISC cpu support.
*/
-#define HPPA_PGALIAS 0x00100000
-#define HPPA_PGAMASK 0xfff00000
-#define HPPA_PGAOFF 0x000fffff
+#define HPPA_PGALIAS 0x00400000
+#define HPPA_PGAMASK 0xffc00000
+#define HPPA_PGAOFF 0x003fffff
#define HPPA_IOBEGIN 0xf0000000
#define HPPA_IOLEN 0x10000000