diff options
| author | GNU Hurd wiki engine <web-hurd@gnu.org> | 2007-10-27 15:32:21 +0000 |
|---|---|---|
| committer | GNU Hurd wiki engine <web-hurd@gnu.org> | 2007-10-27 15:32:21 +0000 |
| commit | 1bbef523bf9e2d03e61281b2b9c1079f75440f34 (patch) | |
| tree | 8caede7d637ca43d6708d6803c3c9a030361f4ce | |
| parent | b25149e6f2670f7d914cec58ad49555d61429f86 (diff) | |
web commit by antrik: Reworked section on amd64 compatibility, to be more exact and informative
| -rw-r--r-- | microkernel/mach/gnumach/hardwarecompatibilitylist.mdwn | 13 |
1 files changed, 9 insertions, 4 deletions
diff --git a/microkernel/mach/gnumach/hardwarecompatibilitylist.mdwn b/microkernel/mach/gnumach/hardwarecompatibilitylist.mdwn index e0e7e4ea..9366d3ab 100644 --- a/microkernel/mach/gnumach/hardwarecompatibilitylist.mdwn +++ b/microkernel/mach/gnumach/hardwarecompatibilitylist.mdwn @@ -8,10 +8,15 @@ is included in the section entitled # CPU Architecture -GNU Mach current only supports the `x86` architecture. `amd64` should -- in -theory -- as well work fine in `32-bit` compatibility mode, however in practice -there are problems with the chipsets used for such processors, so that booting -on such a system won't succeed. +GNU Mach current only supports the `x86` (alias `ia32` or `i386`) architecture. + +`amd64`/`ix64` should work in `32-bit` compatibility mode. However, in practice +`amd64` systems seem to be troublesome more often than not. This is probably +related to the same (chipset-related) problems we often see with recent +machines; but it seems that amd64 ones use problematic chipsets particularily +often. So far we haven't heard of similar problems with Intel's eqivalent +`ix64` (or `EM64T` as it used to be called) -- but maybe that just means fewer +people tried running the Hurd on such machines :-) Support for running GNU Mach (and a complete GNU/Hurd system) in a [Xen](http://www.cl.cam.ac.uk/research/srg/netos/xen/) `domU` (again on `x86` |