summaryrefslogtreecommitdiff
path: root/faq.en.in
diff options
context:
space:
mode:
authorThomas Schwinge <tschwinge@gnu.org>2008-07-26 15:07:29 +0200
committerThomas Schwinge <tschwinge@gnu.org>2008-07-26 15:07:29 +0200
commiteee1566c5165980e281437c025536491655520e6 (patch)
tree497649846e5e8d2ff93c7f4a11ecceb966180706 /faq.en.in
parent2fcf5a8b0d20aadd59fbee967d9d75ee4f34085b (diff)
Supported for hardware is described in [[microkernel/mach/gnumach/hardware_compatibility_list]].
Diffstat (limited to 'faq.en.in')
-rw-r--r--faq.en.in24
1 files changed, 0 insertions, 24 deletions
diff --git a/faq.en.in b/faq.en.in
index a694c94c..11e1c242 100644
--- a/faq.en.in
+++ b/faq.en.in
@@ -27,30 +27,6 @@ license is included in the file COPYRIGHT.
? Installation
-?? What kind of hardware is supported?
-
-{NHW} Currently, the GNU Hurd only runs on IA32 machines, however,
-porting to other architectures should not be difficult: the code has
-always been written with portability in mind.
-
-With respect to drivers, GNU Mach uses a subset of the drivers from the
-Linux 2.0.x kernel. A relatively complete hardware compatibility guide
-can be found at:
-
- http://www.nongnu.org/thug/gnumach_hardware.html
-
-If you run into trouble, it is most likely that:
-
-- You are using IRQ sharing; GNU Mach does not support this in the
- least.
-- A device driver is frobbing the hardware and accidentally activating
- the wrong device.
-
-In the former case, you should start removing devices or play with the
-BIOS. As for the latter, GNU Mach does not support loadable kernel
-modules. Therefore, you will have to compile a new kernel and only
-activate those device drivers that you actually need.
-
?? What partition type should I use for my GNU/Hurd partitions?
{MB} You should use an ext2 filesystem. Alternatively, you may use BSD