diff --git a/handbook/authors.sgml b/handbook/authors.sgml index 0e8468fc73..07210c90d2 100644 --- a/handbook/authors.sgml +++ b/handbook/authors.sgml @@ -1,26 +1,27 @@ - + <asami@FreeBSD.org>"> <davidg@Root.COM>"> <dufault@hda.com>"> <gclarkii@FreeBSD.org>"> <gena@NetVision.net.il>"> <ghelmer@alpha.dsu.edu>"> <gpalmer@FreeBSD.org>"> <jfieber@FreeBSD.org>"> <jkh@FreeBSD.org>"> <joerg_wunsch@uriah.heep.sax.de>"> <john@starfire.MN.ORG>"> <mark@grondar.za>"> <martin@innovus.com>"> <md@bsc.no>"> <nik@blueberry.co.uk>"> <phk@FreeBSD.org>"> <paul@FreeBSD.org>"> +<rgrimes@FreeBSD.org>"> <wilko@yedi.iaf.nl>"> diff --git a/handbook/hw.sgml b/handbook/hw.sgml index 64bfcc5e25..48c2dbb81f 100644 --- a/handbook/hw.sgml +++ b/handbook/hw.sgml @@ -1,70 +1,123 @@ - + + + PC Hardware compatibility

Issues of hardware compatibility are among the most troublesome in the computer industry today and FreeBSD is by no means immune to trouble. In this respect, FreeBSD's advantage of being able to run on inexpensive commidity PC hardware is also its liability when it comes to support for the amazing variety of components on the market. While it would be impossible to provide a exhaustive listing of hardware that FreeBSD supports, this section serves as a catalog of the device drivers included with FreeBSD and the hardware each drivers supports. Where possible and appropriate, notes about specific products are included. As FreeBSD is a volunteer project without a funded testing department, we depend on you, the user, for much of the information contained in this catalog. If you have direct experience of hardware that does or does not work with FreeBSD, please let us know by sending email to doc@freebsd.org. Questions about supported hardware should be directed to questions@freebsd.org (see for more information). When submitting information or asking a question, please remember to specify exactly what version of FreeBSD you are using and include as many details of your hardware as possible. -* Core/Processing +Core/Processing -* Motherboards +Motherboards, busses, and chipsets * ISA * EISA * VLB - * PCI + PCI + +

Contributed by &a.rgrimes;.25 April 1995.

+ +

Of the Intel PCI chip sets the following is a list + of brokenness from worst to best and a short + description of brokenness.

+ +

+ + Mercury: Cache coherency problems, + especially if there are ISA bus masters behind + the ISA to PCI bridge chip. Hardware flaw, only + known work around is to turn the cache + off. + + Saturn-I (ie, 82424ZX at rev 0, 1 or + 2): write back cache coherency + problems. Hardware flaw, only known work around + is to set the external cache to write-through + mode. Upgrade to Saturn-II. + + Saturn-II (ie, 82424ZX at rev 3 or + 4): Works fine, but many MB + manufactures leave out the external dirty bit + SRAM needed for write back operation. Work + arounds are either run it in write through mode, + or get the dirty bit SRAM installed. (I have + these for the ASUS PCI/I-486SP3G rev 1.6 and + later boards). + + Neptune: Can not run more than 2 bus + master devices. Admitted Intel design flaw. + Workarounds include don't run more than 2 bus + masters, special hardware design to replace the + PCI bus arbiter (appears on Intel Altair board + and several other Intel server group MB's). And + of course Intel's official answer, move to the + Triton chip set, we ``fixed it there''. + + Triton: No known cache coherency or bus + master problems, chip set does not implement + parity checking. Workaround for parity issue. + Wait for Triton-II. + + Triton-II: Unknown, not yet shipping. + + +

+ * CPUs/FPUs * Memory * BIOS * Input/Output Devices * Video cards * Sound cards * Serial ports (including multiport cards) * Parallel ports * Modems * Network cards * Keyboards * Mice * Other * Storage Devices * Disk/tape controllers * SCSI * IDE * Floppy * Hard drives * Tape drives * CD-ROM drives * Other * Other * PCMCIA