diff -u --recursive --new-file v2.4.14/linux/CREDITS linux/CREDITS
--- v2.4.14/linux/CREDITS	Mon Nov  5 15:55:25 2001
+++ linux/CREDITS	Sun Nov 11 10:09:32 2001
@@ -1611,8 +1611,10 @@
 W: http://www.kroah.com/linux-usb/
 D: USB Serial Converter driver framework, USB Handspring Visor driver
 D: ConnectTech WHITEHeat USB driver, Generic USB Serial driver
-D: USB Bluetooth driver
+D: USB I/O Edgeport driver, USB Serial IrDA driver
+D: USB Bluetooth driver, USB Skeleton driver
 D: bits and pieces of USB core code.
+D: PCI Hotplug core, PCI Hotplug Compaq driver modifications
 
 N: Russell Kroll
 E: rkroll@exploits.org
diff -u --recursive --new-file v2.4.14/linux/Documentation/Configure.help linux/Documentation/Configure.help
--- v2.4.14/linux/Documentation/Configure.help	Mon Nov  5 15:55:25 2001
+++ linux/Documentation/Configure.help	Wed Nov 21 09:59:11 2001
@@ -1,62 +1,71 @@
-# Maintained by Axel Boldt (axel@uni-paderborn.de)
+# Maintained by:
+#	Eric S. Raymond <mailto:esr@thyrsus.com>
+#	Steven Cole <mailto:elenstev@mesatop.com>
+#
+# Merged version 2.49: Current with 2.4.15-pre1 and 2.4.13-ac8.
 #
 # This version of the Linux kernel configuration help texts
 # corresponds to the kernel versions 2.4.x.
 #
 # Translations of this file available on the WWW:
 #
-#   - Japanese, maintained by the JF Project (JF@linux.or.jp), at
-#     http://www.linux.or.jp/JF/JFdocs/Configure.help/
-#   - Russian, by kaf@linux.nevod.perm.su, at
-#     http://nevod.perm.su/service/linux/doc/kernel/Configure.help
-#   - French, by Pierre Tane (tanep@bigfoot.com), at
-#     http://www.traduc.org/kernelfr
-#   - Spanish, by Carlos Perelló Marín (fperllo@ehome.encis.es), at
-#     http://visar.csustan.edu/~carlos/
-#     XXX: Site has moved, new location has no Configure.help trans.
-#   - Italian, by Alessandro Rubini (rubini@linux.it), at
-#     ftp://ftp-pavia1.linux.it/pub/linux/Configure.help
-#     XXX: ftp-pavia1.linux.it: Non-existent host/domain
-#   - Polish, by Cezar Cichocki (cezar@cs.net.pl), at
-#     http://www.cs.net.pl/~cezar/Kernel
-#   - German, by SuSE, at http://www.suse.de/~ke/kernel . This patch
+#   - Japanese, maintained by the JF Project <mailto:JF@linux.or.jp>, at
+#     <http://www.linux.or.jp/JF/JFdocs/Configure.help/>
+#   - Russian, by <mailto:kaf@linux.nevod.perm.su>, at
+#     <http://nevod.perm.su/service/linux/doc/kernel/Configure.help>
+#   - French, by Pierre Tane <mailto:tanep@bigfoot.com>, at
+#     <http://www.traduc.org/kernelfr>
+#   - Polish, by Dominik Mierzejewski <mailto:dmierzej@elka.pw.edu.pl>, at
+#     <http://home.elka.pw.edu.pl/~dmierzej/linux/kernel/>
+#   - German, by SuSE, at <http://www.suse.de/~ke/kernel>. This patch
 #     also includes infrastructure to support different languages.
 #
 # To access a document on the WWW, you need to have a direct Internet
 # connection and a browser program such as netscape or lynx. If you
 # only have email access, you can still use FTP and WWW servers: send
-# an email to mail-server@rtfm.mit.edu with the text 
-#   send usenet/news.answers/internet-services/access-via-email 
+# an email to <mailto:mail-server@rtfm.mit.edu> with the text
+#   send usenet/news.answers/internet-services/access-via-email
 # in the body of the message.
 #
 # Information about what a kernel is, what it does, how to patch and
 # compile it and much more is contained in the Kernel-HOWTO, available
-# at http://www.linuxdoc.org/docs.html#howto . Before you start
+# at <http://www.linuxdoc.org/docs.html#howto>. Before you start
 # compiling, make sure that you have the necessary versions of all
 # programs and libraries required to compile and run this kernel; they
-# are listed in the file Documentation/Changes. Make sure to read the
+# are listed in the <file:Documentation/Changes>. Make sure to read the
 # toplevel kernel README file as well.
 #
-# Format of this file: description<nl>variable<nl>help text<nl><nl>. If
-# the question being documented is of type "choice", we list only the
-# first occurring config variable. The help texts may contain empty
-# lines, but every non-empty line must be indented two positions.
-# Order of the help texts does not matter, however, no variable should
-# be documented twice: if it is, only the first occurrence will be
-# used by Configure. We try to keep the help texts of related variables
-# close together. Lines starting with `#' are ignored. To be nice to
-# menuconfig, limit your line length to 70 characters. Use emacs'
+# Format of this file: description<nl>variable<nl>help text<nl><nl>.
+# The help texts may contain empty lines, but every non-empty line must
+# be indented two positions.  Order of the help texts does not matter,
+# however, no variable should be documented twice: if it is, only the
+# first occurrence will be used. We try to keep the help texts of related
+# variables close together. Lines starting with `#' are ignored. To be
+# nice to menuconfig, limit your line length to 70 characters. Use emacs'
 # kfill.el to edit and ispell.el to spell check this file or you lose.
 #
+# Comments of the form "# Choice:" followed by a menu name are used
+# internally by the maintainers' consistency-checking tools.
+#
 # If you add a help text to this file, please try to be as gentle as
 # possible. Don't use unexplained acronyms and generally write for the
 # hypothetical ignorant but intelligent user who has just bought a PC,
 # removed Windows, installed Linux and is now recompiling the kernel
-# for the first time. Tell them what to do if they're unsure. Technical 
+# for the first time. Tell them what to do if they're unsure. Technical
 # information should go in a README in the Documentation directory.
+#
 # Mention all the relevant READMEs and HOWTOs in the help text.
+# Make them file URLs relative to the top level of the source tree so
+# that help browsers can turn them into hotlinks.  All URLs ahould be
+# surrounded by <>.
+#
 # Repetitions are fine since the help texts are not meant to be read
-# in sequence.
+# in sequence.  It is good style to include URLs pointing to more
+# detailed technical information, pictures of the hardware, etc.
+#
+# The most important thing to include in a help entry is *motivation*.
+# Explain why someone configuring a kernel might want to select your
+# option.
 #
 # All this was shamelessly stolen from several different sources. Many
 # thanks to all the contributors. Feel free to use these help texts in
@@ -66,21 +75,22 @@
 
 Prompt for development and/or incomplete code/drivers
 CONFIG_EXPERIMENTAL
-  Some of the various things that Linux supports (such as network 
-  drivers, file systems, network protocols, etc.) can be in a state 
-  of development where the functionality, stability, or the level of 
+  Some of the various things that Linux supports (such as network
+  drivers, file systems, network protocols, etc.) can be in a state
+  of development where the functionality, stability, or the level of
   testing is not yet high enough for general use. This is usually
-  known as the "alpha-test" phase amongst developers. If a feature is
-  currently in alpha-test, then the developers usually discourage 
+  known as the "alpha-test" phase among developers. If a feature is
+  currently in alpha-test, then the developers usually discourage
   uninformed widespread use of this feature by the general public to
   avoid "Why doesn't this work?" type mail messages. However, active
   testing and use of these systems is welcomed. Just be aware that it
   may not meet the normal level of reliability or it may fail to work
   in some special cases. Detailed bug reports from people familiar
   with the kernel internals are usually welcomed by the developers
-  (before submitting bug reports, please read the documents README,
-  MAINTAINERS, REPORTING-BUGS, Documentation/BUG-HUNTING, and
-  Documentation/oops-tracing.txt in the kernel source). 
+  (before submitting bug reports, please read the documents
+  <file:README>, <file:MAINTAINERS>, <file:REPORTING-BUGS>,
+  <file:Documentation/BUG-HUNTING>, and
+  <file:Documentation/oops-tracing.txt> in the kernel source).
 
   This option will also make obsoleted drivers available. These are
   drivers that have been replaced by something else, and/or are
@@ -89,11 +99,18 @@
   Unless you intend to help test and develop a feature or driver that
   falls into this category, or you have a situation that requires
   using these features, you should probably say N here, which will
-  cause this configure script to present you with fewer choices. If
+  cause the configurator to present you with fewer choices. If
   you say Y here, you will be offered the choice of using features or
   drivers that are currently considered to be in the alpha-test phase.
 
-Symmetric Multi Processing
+Prompt for drivers for obsolete features and hardware
+CONFIG_OBSOLETE
+  Obsolete drivers have usually been replaced by more recent software
+  that can talk to the same hardware.  Obsolete hardware is things
+  like MGA monitors that you are very unlikely to see on today's
+  systems.
+
+Symmetric Multi-Processing support
 CONFIG_SMP
   This enables support for systems with more than one CPU. If you have
   a system with only one CPU, like most personal computers, say N. If
@@ -114,12 +131,106 @@
   Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
   Management" code will be disabled if you say Y here.
 
-  See also the files Documentation/smp.tex, Documentation/smp.txt,
-  Documentation/i386/IO-APIC.txt, Documentation/nmi_watchdog.txt and the 
-  SMP-FAQ on the WWW at http://www.irisa.fr/prive/mentre/smp-faq/ .
-  
+  See also the <file:Documentation/smp.tex>,
+  <file:Documentation/smp.txt>, <file:Documentation/i386/IO-APIC.txt>,
+  <file:Documentation/nmi_watchdog.txt> and the SMP-FAQ on the WWW at
+  <http://www.irisa.fr/prive/mentre/smp-faq/>.
+
   If you don't know what to do here, say N.
 
+Intel or compatible 80x86 processor
+CONFIG_X86
+  This is Linux's home port.  Linux was originally native to the Intel
+  386, and runs on all the later x86 processors including the Intel
+  486, 586, Pentiums, and various instruction-set-compatible chips by
+  AMD, Cyrix, and others.
+
+Alpha processor
+CONFIG_ALPHA
+  The Alpha is a 64-bit general-purpose processor designed and
+  marketed by the Digital Equipment Corporation of blessed memory, now
+  Compaq.  Alpha Linux dates from 1995-1996 and was the first non-x86
+  port. The Alpha Linux project has a home page at
+  <http://www.alphalinux.org/>.
+
+32-bit Sun Sparc
+CONFIG_SPARC32
+  SPARC is a family of RISC microprocessors designed and marketed by
+  Sun Microsystems, incorporated.  They are very widely found in Sun
+  workstations and clones. This port covers the original 32-bit SPARC;
+  it is old and stable and usually considered one of the "big three"
+  along with the Intel and Alpha ports.  The UltraLinux project
+  maintains both the SPARC32 and SPARC64 ports; its web page is
+  available at <http://www.ultralinux.org/>.
+
+64-bit Sun Sparc
+CONFIG_SPARC64
+  SPARC is a family of RISC microprocessors designed and marketed by
+  Sun Microsystems, incorporated.  This port covers the newer 64-bit
+  UltraSPARC.  The UltraLinux project maintains both the SPARC32 and
+  SPARC64 ports; its web page is available at
+  <http://www.ultralinux.org/>.
+
+Power PC processor
+CONFIG_PPC
+  The PowerPC is a very capable 32-bit RISC processor from Motorola,
+  the successor to their 68000 and 88000 series.  It powers recent
+  Macintoshes and also a widely-used series of single-board computers
+  from Motorola.  The Linux PowerPC port has a home page at
+  <http://penguinppc.org/>.
+
+Motorola 68K processors
+CONFIG_M68K
+  The Motorola 68K microprocessors are now obsolete, having been
+  superseded by the PowerPC line also from Motorola.  But they powered
+  the first wave of workstation hardware in the 1980s, including Sun
+  workstations; they were also the basis of the original Amiga and
+  later Atari personal computers.  A lot of this hardware is still
+  around.  The m68k project has a home page at
+  <http://www.linux-m68k.org/>.
+
+ARM processors
+CONFIG_ARM
+  The ARM series is a line of low-power-consumption RISC chip designs
+  licensed by ARM ltd and targeted at embedded applications and
+  handhelds such as the Compaq IPAQ.  ARM-based PCs are no longer
+  manufactured, but  legacy ARM-based PC hardware remains popular in
+  Europe.  There is an ARM Linux project with a web page at
+  <http://www.arm.linux.org.uk/>.
+
+SuperH processors
+CONFIG_SUPERH
+  The SuperH is a RISC processor targeted for use in embedded systems
+  and consumer electronics; it was also used in the Sega Dreamcast
+  gaming console.  The SuperH port has a home page at
+  <http://www.sh-linux.org/>.
+
+IA64 processors, including Intel Itanium
+CONFIG_IA64
+  The Itanium is Intel's 64-bit successor to the 32-bit X86 line.  As
+  of early 2001 it is not yet in widespread production use.  The Linux
+  IA-64 project has a home page at <http://www.linuxia64.org/>.
+
+HP PA-RISC processor
+CONFIG_PARISC
+  The PA-RISC microprocessor is a RISC chip designed by
+  Hewlett-Packard and used in their line of workstations.  The PA-RISC
+  Linux project has a home page at <www.parisc-linux.org>.
+
+IBM System/390
+CONFIG_S390
+  Linux now runs on the venerable System/390 mainframe from IBM, in a
+  guest partition under VM.  In fact, over 40,000 simultaneous Linux
+  images have been run on a single mainframe!  The S390 Linux project
+  has a home page at <http://linux.s390.org/>.
+
+Axis Communications ETRAX 100LX embedded network CPU
+CONFIG_CRIS
+  Linux has been ported to run on the Axis Communications ETRAX 100LX
+  CPU and the single-board computers built around it, targeted for
+  network and embedded applications.  For more information see the
+  Axis Communication site, <http://developer.axis.com/>.
+
 Multiquad support for NUMA systems
 CONFIG_MULTIQUAD
   This option is used for getting Linux to run on a (IBM/Sequent) NUMA 
@@ -127,7 +238,7 @@
   and uses Clustered Logical APIC addressing mode instead of Flat Logical.
   You will need a new lynxer.elf file to flash your firmware with - send
   email to Martin.Bligh@us.ibm.com
-  
+
 IO-APIC Support on Uniprocessors
 CONFIG_X86_UP_IOAPIC
   An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
@@ -160,7 +271,7 @@
   a math coprocessor built in, 486SX and 386 do not, unless you added
   a 487DX or 387, respectively. (The messages during boot time can
   give you some hints here ["man dmesg"].) Everyone needs either a
-  coprocessor or this emulation. 
+  coprocessor or this emulation.
 
   If you don't have a math coprocessor, you need to say Y here; if you
   say Y here even though you have a coprocessor, the coprocessor will
@@ -172,7 +283,7 @@
   intend to use this kernel on different machines.
 
   More information about the internals of the Linux math coprocessor
-  emulation can be found in arch/i386/math-emu/README.
+  emulation can be found in <file:arch/i386/math-emu/README>.
 
   If you are not sure, say Y; apart from resulting in a 66 KB bigger
   kernel, it won't hurt.
@@ -211,12 +322,13 @@
   functions. You may choose to use both, but the Timer LED function
   will overrule the CPU usage LED.
 
-Kernel FP software completion (EXPERIMENTAL)
+Kernel FP software completion
 CONFIG_MATHEMU
   This option is required for IEEE compliant floating point arithmetic
   on the Alpha. The only time you would ever not say Y is to say M in
   order to debug the code. Say Y unless you know what you are doing.
 
+# Choice: himem
 High Memory support
 CONFIG_NOHIGHMEM
   Linux can use up to 64 Gigabytes of physical memory on x86 systems.
@@ -248,23 +360,45 @@
   auto detected or can be forced by using a kernel command line option
   such as "mem=256M". (Try "man bootparam" or see the documentation of
   your boot loader (lilo or loadlin) about how to pass options to the
-  kernel at boot time.) 
+  kernel at boot time.)
 
   If unsure, say "off".
 
+4GB
+CONFIG_HIGHMEM4G
+  Select this if you have a 32-bit processor and between 1 and 4
+  gigabytes of physical RAM.
+
+64GB
+CONFIG_HIGHMEM64G
+  Select this if you have a 32-bit processor and more than 4
+  gigabytes of physical RAM.
+
 Normal PC floppy disk support
 CONFIG_BLK_DEV_FD
   If you want to use the floppy disk drive(s) of your PC under Linux,
   say Y. Information about this driver, especially important for IBM
-  Thinkpad users, is contained in Documentation/floppy.txt. That file
-  also contains the location of the Floppy driver FAQ as well as
-  location of the fdutils package used to configure additional
+  Thinkpad users, is contained in <file:Documentation/floppy.txt>.
+  That file also contains the location of the Floppy driver FAQ as
+  well as location of the fdutils package used to configure additional
   parameters of the driver at run time.
 
   This driver is also available as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want).
   The module will be called floppy.o. If you want to compile it as a
-  module, say M here and read Documentation/modules.txt.
+  module, say M here and read <file:Documentation/modules.txt>.
+
+iSeries Virtual I/O Disk Support
+CONFIG_VIODASD
+  If you are running on an iSeries system and you want to use
+  virtual disks created and managed by OS/400, say Y.
+
+iSeries Virtual I/O Disk IDE Emulation
+CONFIG_VIODASD_IDE
+  This causes the iSeries virtual disks to look like IDE disks.
+  If you have programs or utilities that only support certain
+  kinds of disks, this option will cause iSeries virtual disks
+  to pretend to be IDE disks, which may satisfy the program.
 
 Support for PowerMac floppy
 CONFIG_MAC_FLOPPY
@@ -278,15 +412,15 @@
   write to it and do all the other things that you can do with normal
   block devices (such as hard drives). It is usually used to load and
   store a copy of a minimal root file system off of a floppy into RAM
-  during the initial install of Linux. 
+  during the initial install of Linux.
 
   Note that the kernel command line option "ramdisk=XX" is now
-  obsolete. For details, read Documentation/ramdisk.txt.
+  obsolete. For details, read <file:Documentation/ramdisk.txt>.
 
   If you want to compile this as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M and read Documentation/modules.txt. The module will be called
-  rd.o. 
+  say M and read <file:Documentation/modules.txt>. The module will be
+  called rd.o.
 
   Most normal users won't need the RAM disk functionality, and can
   thus say N here.
@@ -301,15 +435,15 @@
   The initial RAM disk is a RAM disk that is loaded by the boot loader
   (loadlin or lilo) and that is mounted as root before the normal boot
   procedure. It is typically used to load modules needed to mount the
-  "real" root file system, etc. See Documentation/initrd.txt for
-  details.
+  "real" root file system, etc. See <file:Documentation/initrd.txt>
+  for details.
 
-Loop device support
+Loopback device support
 CONFIG_BLK_DEV_LOOP
   Saying Y here will allow you to use a regular file as a block
   device; you can then create a file system on that block device and
   mount it just as you would mount other block devices such as hard
-  drive partitions, CDROM drives or floppy drives. The loop devices
+  drive partitions, CD-ROM drives or floppy drives. The loop devices
   are block special device files with major number 7 and typically
   called /dev/loop0, /dev/loop1 etc.
 
@@ -318,7 +452,7 @@
   writing them to floppy. Furthermore, some Linux distributions avoid
   the need for a dedicated Linux partition by keeping their complete
   root file system inside a DOS FAT file using this loop device
-  driver. 
+  driver.
 
   The loop device driver can also be used to "hide" a file system in a
   disk partition, floppy, or regular file, either using encryption
@@ -326,58 +460,58 @@
   bits of, say, a sound file). This is also safe if the file resides
   on a remote file server. If you want to do this, you will first have
   to acquire and install a kernel patch from
-  ftp://ftp.kerneli.org/pub/kerneli/ , and then you need to
+  <ftp://ftp.kerneli.org/pub/kerneli/>, and then you need to
   say Y to this option.
 
   Note that alternative ways to use encrypted file systems are
   provided by the cfs package, which can be gotten from
-  ftp://ftp.kerneli.org/pub/kerneli/net-source/ , and the newer tcfs
-  package, available at http://tcfs.dia.unisa.it/ . You do not need to
-  say Y here if you want to use one of these. However, using cfs
+  <ftp://ftp.kerneli.org/pub/kerneli/net-source/>, and the newer tcfs
+  package, available at <http://tcfs.dia.unisa.it/>. You do not need
+  to say Y here if you want to use one of these. However, using cfs
   requires saying Y to "NFS file system support" below while using
   tcfs requires applying a kernel patch. An alternative steganography
   solution is provided by StegFS, also available from
-  ftp://ftp.kerneli.org/pub/kerneli/net-source/ .
+  <ftp://ftp.kerneli.org/pub/kerneli/net-source/>.
 
   To use the loop device, you need the losetup utility and a recent
   version of the mount program, both contained in the util-linux
   package. The location and current version number of util-linux is
-  contained in the file Documentation/Changes.
+  contained in the file <file:Documentation/Changes>.
 
   Note that this loop device has nothing to do with the loopback
   device used for network connections from the machine to itself.
 
   If you want to compile this driver as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt. The module will be
-  called loop.o.
+  say M here and read <file:Documentation/modules.txt>. The module
+  will be called loop.o.
 
   Most users will answer N here.
 
-Network Block Device support
+Network block device support
 CONFIG_BLK_DEV_NBD
   Saying Y here will allow your computer to be a client for network
   block devices, i.e. it will be able to use block devices exported by
   servers (mount file systems on them etc.). Communication between
   client and server works over TCP/IP networking, but to the client
   program this is hidden: it looks like a regular local file access to
-  a block device special file such as /dev/nd0. 
+  a block device special file such as /dev/nd0.
 
   Network block devices also allows you to run a block-device in
   userland (making server and client physically the same computer,
   communicating using the loopback network device).
-  
-  Read Documentation/nbd.txt for more information, especially about
-  where to find the server code, which runs in user space and does not
-  need special kernel support.
+
+  Read <file:Documentation/nbd.txt> for more information, especially
+  about where to find the server code, which runs in user space and
+  does not need special kernel support.
 
   Note that this has nothing to do with the network file systems NFS
   or Coda; you can say N here even if you intend to use NFS or Coda.
 
   If you want to compile this driver as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt. The module will be
-  called nbd.o.
+  say M here and read <file:Documentation/modules.txt>. The module
+  will be called nbd.o.
 
   If unsure, say N.
 
@@ -385,16 +519,16 @@
 CONFIG_IDE
   If you say Y here, your kernel will be able to manage low cost mass
   storage units such as ATA/(E)IDE and ATAPI units. The most common
-  cases are IDE hard drives and ATAPI CDROM drives.
+  cases are IDE hard drives and ATAPI CD-ROM drives.
 
   If your system is pure SCSI and doesn't use these interfaces, you
   can say N here.
- 
+
   Integrated Disk Electronics (IDE aka ATA-1) is a connecting standard
   for mass storage units such as hard disks. It was designed by
   Western Digital and Compaq Computer in 1984. It was then named
   ST506. Quite a number of disks use the IDE interface.
-	
+
   AT Attachment (ATA) is the superset of the IDE specifications.
   ST506 was also called ATA-1.
 
@@ -407,22 +541,22 @@
   ATA/IDE standards by means of fast DMA controllers.
 
   ATA Packet Interface (ATAPI) is a protocol used by EIDE tape and
-  CDROM drives, similar in many respects to the SCSI protocol.
-  
+  CD-ROM drives, similar in many respects to the SCSI protocol.
+
   SMART IDE (Self Monitoring, Analysis and Reporting Technology) was
   designed in order to prevent data corruption and disk crash by
   detecting pre hardware failure conditions (heat, access time, and
-  the like...). Disks built since June 1995 may follow this
-  standard. The kernel itself don't manage this; however there are
-  quite a number of user programs such as smart that can query the
-  status of SMART parameters disk.
+  the like...). Disks built since June 1995 may follow this standard.
+  The kernel itself don't manage this; however there are quite a
+  number of user programs such as smart that can query the status of
+  SMART parameters disk.
 
   If you want to compile this driver as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt. The module will be
-  called ide.o.
+  say M here and read <file:Documentation/modules.txt>. The module
+  will be called ide.o.
 
-  For further information, please read Documentation/ide.txt.
+  For further information, please read <file:Documentation/ide.txt>.
 
   If unsure, say Y.
 
@@ -436,21 +570,21 @@
   Useful information about large (>540 MB) IDE disks, multiple
   interfaces, what to do if ATA/IDE devices are not automatically
   detected, sound card ATA/IDE ports, module support, and other
-  topics, is contained in Documentation/ide.txt. For detailed
+  topics, is contained in <file:Documentation/ide.txt>. For detailed
   information about hard drives, consult the Disk-HOWTO and the
   Multi-Disk-HOWTO, available from
-  http://www.linuxdoc.org/docs.html#howto .
+  <http://www.linuxdoc.org/docs.html#howto>.
 
   To fine-tune ATA/IDE drive/interface parameters for improved
   performance, look for the hdparm package at
-  http://www.ibiblio.org/pub/Linux/system/hardware .
+  <http://www.ibiblio.org/pub/Linux/system/hardware>.
 
   If you want to compile this driver as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt and
-  Documentation/ide.txt. The module will be called ide-mod.o. Do not
-  compile this driver as a module if your root file system (the one
-  containing the directory /) is located on an IDE device.
+  say M here and read <file:Documentation/modules.txt> and
+  <file:Documentation/ide.txt>. The module will be called ide-mod.o.
+  Do not compile this driver as a module if your root file system (the
+  one containing the directory /) is located on an IDE device.
 
   If you have one or more IDE drives, say Y or M here. If your system
   has no IDE drives, or if memory requirements are really tight, you
@@ -467,42 +601,42 @@
   since it lacks the enhanced functionality of the new one. This makes
   it a good choice for systems with very tight memory restrictions, or
   for systems with only older MFM/RLL/ESDI drives. Choosing the old
-  driver can save 13 KB or so of kernel memory. 
+  driver can save 13 KB or so of kernel memory.
 
   If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
   instead of this one. For more detailed information, read the
   Disk-HOWTO, available from
-  http://www.linuxdoc.org/docs.html#howto .
+  <http://www.linuxdoc.org/docs.html#howto>.
 
 Use old disk-only driver on primary interface
 CONFIG_BLK_DEV_HD_IDE
-  There are two drivers for MFM/RLL/IDE disks. Most people use just
-  the new enhanced driver by itself. This option however installs the
+  There are two drivers for MFM/RLL/IDE disks.  Most people use just
+  the new enhanced driver by itself.  This option however installs the
   old hard disk driver to control the primary IDE/disk interface in
   the system, leaving the new enhanced IDE driver to take care of only
-  the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from
-  having an IDE/ATAPI CDROM or tape drive connected to the primary IDE
-  interface. Choosing this option may be useful for older systems
+  the 2nd/3rd/4th IDE interfaces.  Doing this will prevent you from
+  having an IDE/ATAPI CD-ROM or tape drive connected to the primary
+  IDE interface.  Choosing this option may be useful for older systems
   which have MFM/RLL/ESDI controller+drives at the primary port
   address (0x1f0), along with IDE drives at the secondary/3rd/4th port
-  addresses. 
+  addresses.
 
   Normally, just say N here; you will then use the new driver for all
   4 interfaces.
 
 Include IDE/ATA-2 DISK support
 CONFIG_BLK_DEV_IDEDISK
-  This will include enhanced support for MFM/RLL/IDE hard disks. If
+  This will include enhanced support for MFM/RLL/IDE hard disks.  If
   you have a MFM/RLL/IDE disk, and there is no special reason to use
-  the old hard disk driver instead, say Y. If you have an SCSI-only
+  the old hard disk driver instead, say Y.  If you have an SCSI-only
   system, you can say N here.
 
   If you want to compile this driver as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt. The module will be
-  called ide-disk.o. Do not compile this driver as a module if your
-  root file system (the one containing the directory /) is located on
-  the IDE disk. If unsure, say Y.
+  say M here and read <file:Documentation/modules.txt>.  The module
+  will be called ide-disk.o.  Do not compile this driver as a module
+  if your root file system (the one containing the directory /) is
+  located on the IDE disk. If unsure, say Y.
 
 Use multi-mode by default
 CONFIG_IDEDISK_MULTI_MODE
@@ -513,38 +647,43 @@
 
   If in doubt, say N.
 
-Include IDE/ATAPI CDROM support
+PCMCIA IDE support
+CONFIG_BLK_DEV_IDECS
+  Support for outboard IDE disks, tape drives, and CD-ROM drives
+  connected through a  PCMCIA card.
+
+Include IDE/ATAPI CD-ROM support
 CONFIG_BLK_DEV_IDECD
-  If you have a CDROM drive using the ATAPI protocol, say Y. ATAPI is
-  a newer protocol used by IDE CDROM and TAPE drives, similar to the
-  SCSI protocol. Most new CDROM drives use ATAPI, including the
+  If you have a CD-ROM drive using the ATAPI protocol, say Y. ATAPI is
+  a newer protocol used by IDE CD-ROM and TAPE drives, similar to the
+  SCSI protocol. Most new CD-ROM drives use ATAPI, including the
   NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
   double(2X) or better speed drives.
 
-  If you say Y here, the CDROM drive will be identified at boot time
+  If you say Y here, the CD-ROM drive will be identified at boot time
   along with other IDE devices, as "hdb" or "hdc", or something
   similar (check the boot messages with dmesg). If this is your only
-  CDROM drive, you can say N to all other CDROM options, but be sure
-  to say Y or M to "ISO 9660 CDROM file system support".
+  CD-ROM drive, you can say N to all other CD-ROM options, but be sure
+  to say Y or M to "ISO 9660 CD-ROM file system support".
 
-  Read the CDROM-HOWTO, available from
-  http://www.linuxdoc.org/docs.html#howto and the file
-  Documentation/cdrom/ide-cd. Note that older versions of lilo (the
-  Linux boot loader) cannot properly deal with IDE/ATAPI CDROMs, so
-  install lilo-16 or higher, available from
-  ftp://metalab.unc.edu/pub/Linux/system/boot/lilo .
+  Read the CD-ROM-HOWTO, available from
+  <http://www.linuxdoc.org/docs.html#howto> and
+  <file:Documentation/cdrom/ide-cd>. Note that older versions of lilo
+  (the Linux boot loader) cannot properly deal with IDE/ATAPI CD-ROMs,
+  so install lilo-16 or higher, available from
+  <ftp://metalab.unc.edu/pub/Linux/system/boot/lilo>.
 
   If you want to compile the driver as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt. The module will be
-  called ide-cd.o.
+  say M here and read <file:Documentation/modules.txt>.  The module
+  will be called ide-cd.o.
 
 Include IDE/ATAPI TAPE support
 CONFIG_BLK_DEV_IDETAPE
   If you have an IDE tape drive using the ATAPI protocol, say Y.
-  ATAPI is a newer protocol used by IDE tape and CDROM drives, similar
-  to the SCSI protocol. If you have an SCSI tape drive however, you
-  can say N here.
+  ATAPI is a newer protocol used by IDE tape and CD-ROM drives,
+  similar to the SCSI protocol.  If you have an SCSI tape drive
+  however, you can say N here.
 
   You should also say Y if you have an OnStream DI-30 tape drive; this
   will not work with the SCSI protocol, until there is support for the
@@ -553,27 +692,27 @@
   If you say Y here, the tape drive will be identified at boot time
   along with other IDE devices, as "hdb" or "hdc", or something
   similar, and will be mapped to a character device such as "ht0"
-  (check the boot messages with dmesg). Be sure to consult the
-  drivers/ide/ide-tape.c and Documentation/ide.txt files for usage
-  information.
+  (check the boot messages with dmesg).  Be sure to consult the
+  <file:drivers/ide/ide-tape.c> and <file:Documentation/ide.txt> files
+  for usage information.
 
   If you want to compile the driver as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt. The module will be
-  called ide-tape.o.
+  say M here and read <file:Documentation/modules.txt>.  The module
+  will be called ide-tape.o.
 
 Include IDE/ATAPI FLOPPY support
 CONFIG_BLK_DEV_IDEFLOPPY
   If you have an IDE floppy drive which uses the ATAPI protocol,
-  answer Y. ATAPI is a newer protocol used by IDE CDROM/tape/floppy
-  drives, similar to the SCSI protocol. 
+  answer Y.  ATAPI is a newer protocol used by IDE CD-ROM/tape/floppy
+  drives, similar to the SCSI protocol.
 
   The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by
   this driver. For information about jumper settings and the question
   of when a ZIP drive uses a partition table, see
-  http://www.win.tue.nl/~aeb/linux/zip/zip-1.html .
+  <http://www.win.tue.nl/~aeb/linux/zip/zip-1.html>.
   (ATAPI PD-CD/CDR drives are not supported by this driver; support
-  for PD-CD/CDR drives is available if you answer Y to 
+  for PD-CD/CDR drives is available if you answer Y to
   "SCSI emulation support", below).
 
   If you say Y here, the FLOPPY drive will be identified along with
@@ -582,8 +721,8 @@
 
   If you want to compile the driver as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt. The module will be
-  called ide-floppy.o.
+  say M here and read <file:Documentation/modules.txt>.  The module
+  will be called ide-floppy.o.
 
 SCSI emulation support
 CONFIG_BLK_DEV_IDESCSI
@@ -625,7 +764,7 @@
   conditions. Say Y here to include code which tries to automatically
   detect and correct the problems under Linux. This option also
   enables access to the secondary IDE ports in some CMD640 based
-  systems. 
+  systems.
 
   This driver will work automatically in PCI based systems (most new
   systems have PCI slots). But if your system uses VESA local bus
@@ -636,15 +775,15 @@
 
   The CMD640 chip is also used on add-in cards by Acculogic, and on
   the "CSA-6400E PCI to IDE controller" that some people have. For
-  details, read Documentation/ide.txt. 
+  details, read <file:Documentation/ide.txt>.
 
 CMD640 enhanced support
 CONFIG_BLK_DEV_CMD640_ENHANCED
   This option includes support for setting/autotuning PIO modes and
-  prefetch on CMD640 IDE interfaces. For details, read
-  Documentation/ide.txt. If you have a CMD640 IDE interface and your
-  BIOS does not already do this for you, then say Y here. Otherwise
-  say N.
+  prefetch on CMD640 IDE interfaces.  For details, read
+  <file:Documentation/ide.txt>. If you have a CMD640 IDE interface
+  and your BIOS does not already do this for you, then say Y here.
+  Otherwise say N.
 
 RZ1000 chipset bugfix/support
 CONFIG_BLK_DEV_RZ1000
@@ -654,14 +793,14 @@
   severe data corruption under many conditions. Say Y here to include
   code which automatically detects and corrects the problem under
   Linux. This may slow disk throughput by a few percent, but at least
-  things will operate 100% reliably. 
+  things will operate 100% reliably.
 
 Generic PCI IDE chipset support
 CONFIG_BLK_DEV_IDEPCI
   Say Y here for PCI systems which use IDE drive(s).
   This option helps the IDE driver to automatically detect and
   configure all PCI-based IDE interfaces in your system.
-  
+
 Support for sharing PCI IDE interrupts
 CONFIG_IDEPCI_SHARE_IRQ
   Some ATA/IDE chipsets have hardware support which allows for
@@ -681,14 +820,14 @@
   for these drives, but you can change that by saying Y to the
   following question "Use DMA by default when available". You can get
   the latest version of the hdparm utility from
-  ftp://metalab.unc.edu/pub/Linux/system/hardware/ .
+  <ftp://metalab.unc.edu/pub/Linux/system/hardware/>.
 
-  Read the comments at the beginning of drivers/ide/ide-dma.c and
-  the file Documentation/ide.txt for more information.
+  Read the comments at the beginning of <file:drivers/ide/ide-dma.c>
+  and the file <file:Documentation/ide.txt> for more information.
 
   It is safe to say Y to this question.
 
-Good-Bad DMA Model-Firmware (EXPERIMENTAL)
+Good-Bad DMA Model-Firmware (WIP)
 CONFIG_IDEDMA_NEW_DRIVE_LISTINGS
   If you say Y here, the model and firmware revision of your drive
   will be compared against a blacklist of buggy drives that claim to
@@ -701,6 +840,16 @@
 
   If in doubt, say N.
 
+Attempt to HACK around Chipsets that TIMEOUT (WIP)
+CONFIG_BLK_DEV_IDEDMA_TIMEOUT
+  If you say Y here, this is a NASTY UGLY HACK!
+
+  We have to issue an abort and requeue the request DMA engine got
+  turned off by a goofy ASIC, and we have to clean up the mess, and
+  here is as good as any.  Do it globally for all chipsets.
+
+  If in doubt, say N.
+
 Boot off-board chipsets first support
 CONFIG_BLK_DEV_OFFBOARD
   Normally, IDE controllers built into the motherboard (on-board
@@ -722,7 +871,7 @@
 
   If in doubt, say N.
 
-Use DMA by default when available
+Use PCI DMA by default when available
 CONFIG_IDEDMA_PCI_AUTO
   Prior to kernel version 2.1.112, Linux used to automatically use
   DMA for IDE drives and chipsets which support it. Due to concerns
@@ -738,29 +887,39 @@
 
 IGNORE word93 Validation BITS
 CONFIG_IDEDMA_IVB
-  Since various rules were applied and created ... et al. as it relates
-  the detection of valid cable signals.  This is a result of unclear terms
-  in ATA-4 and ATA-5 standards.
+  Since various rules were applied and created ... et al. as it
+  relates the detection of valid cable signals.  This is a result of
+  unclear terms in ATA-4 and ATA-5 standards.
 
   It is normally safe to answer Y; however, the default is N.
 
-Various ATA, Work(s) In Progress (EXPERIMENTAL)
+ATA Work(s) In Progress (EXPERIMENTAL)‹
 CONFIG_IDEDMA_PCI_WIP
   If you enable this you will be able to use and test highly
-  developmental projects. If you say N, this configure script will
+  developmental projects. If you say N, the configurator will
   simply skip those options.
 
   It is SAFEST to say N to this question.
 
+Asyncronious DMA support (EXPERIMENTAL)
+CONFIG_BLK_DEV_ADMA
+  Please read the comments at the top of
+  <file:drivers/ide/ide-adma.c>.
+
+Pacific Digital A-DMA support (EXPERIMENTAL)
+CONFIG_BLK_DEV_PDC_ADMA
+  Please read the comments at the top of <file:drivers/ide/pdcadma.c>.
+
 3ware Hardware ATA-RAID support
 CONFIG_BLK_DEV_3W_XXXX_RAID
   3ware is the only hardware ATA-Raid product in Linux to date.
   This card is 2,4, or 8 channel master mode support only.
   SCSI support required!!!
 
-  http://www.3ware.com/
+  <http://www.3ware.com/>
 
-  Please read the comments at the top of drivers/scsi/3w-xxxx.c  
+  Please read the comments at the top of
+  <file:drivers/scsi/3w-xxxx.c>.
 
 AEC62XX chipset support
 CONFIG_BLK_DEV_AEC62XX
@@ -774,13 +933,13 @@
   The ATP860 is an UltraDMA 66 chipset base.
   The ATP860M(acintosh) version is an UltraDMA 66 chipset base.
 
-  Please read the comments at the top of drivers/ide/aec62xx.c
-  If you say Y here, then say Y to "Use DMA by default when available" as
-  well.
+  Please read the comments at the top of <file:drivers/ide/aec62xx.c>.
+  If you say Y here, then say Y to "Use DMA by default when available"
+  as well.
 
 AEC62XX Tuning support
 CONFIG_AEC62XX_TUNING
-  Please read the comments at the top of drivers/ide/aec62xx.c  
+  Please read the comments at the top of <file:drivers/ide/aec62xx.c>.
   If unsure, say N.
 
 ALI M15x3 chipset support
@@ -790,8 +949,8 @@
   normal dual channel support.
 
   If you say Y here, you also need to say Y to "Use DMA by default
-  when available", above.
-  Please read the comments at the top of drivers/ide/alim15x3.c
+  when available", above.  Please read the comments at the top of
+  <file:drivers/ide/alim15x3.c>.
 
   If unsure, say N.
 
@@ -806,20 +965,21 @@
   Using this option can allow WDC drives to run at ATA-4/5 transfer
   rates with only an ATA-2 support structure.
 
-  SAY NO!
+  SAY N!
 
-AMD7409 chipset support
-CONFIG_BLK_DEV_AMD7409
-  This driver ensures (U)DMA support for the AMD756 Viper chipset.
+AMD Viper support
+CONFIG_BLK_DEV_AMD74XX
+  This driver ensures (U)DMA support for the AMD756/760 Viper
+  chipsets.
 
   If you say Y here, you also need to say Y to "Use DMA by default
   when available", above.
-  Please read the comments at the top of drivers/ide/amd7409.c
+  Please read the comments at the top of <file:drivers/ide/amd74xx.c>.
 
   If unsure, say N.
 
-AMD Viper ATA-66 Override support (WIP)
-CONFIG_AMD7409_OVERRIDE
+AMD Viper ATA-66 Override (WIP)
+CONFIG_AMD74XX_OVERRIDE
   This option auto-forces the ata66 flag.
   This effect can be also invoked by calling "idex=ata66"
   If unsure, say N.
@@ -858,8 +1018,8 @@
 HPT34X AUTODMA support (WIP)
 CONFIG_HPT34X_AUTODMA
   This is a dangerous thing to attempt currently! Please read the
-  comments at the top of drivers/ide/hpt34x.c If you say Y here,
-  then say Y to "Use DMA by default when available" as well.
+  comments at the top of <file:drivers/ide/hpt34x.c>.  If you say Y
+  here, then say Y to "Use DMA by default when available" as well.
 
   If unsure, say N.
 
@@ -868,9 +1028,9 @@
   HPT366 is an Ultra DMA chipset for ATA-66.
   HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
   HPT370 is an Ultra DMA chipset for ATA-100.
- 
+
   This driver adds up to 4 more EIDE devices sharing a single
-  interrupt. 
+  interrupt.
 
   The HPT366 chipset in its current form is bootable. One solution
   for this problem are special LILO commands for redirecting the
@@ -884,21 +1044,22 @@
   ide-probe at boot. It is reported to support DVD II drives, by the
   manufacturer.
 
-NS87415 support (EXPERIMENTAL)
+NS87415 chipset support (EXPERIMENTAL)
 CONFIG_BLK_DEV_NS87415
   This driver adds detection and support for the NS87415 chip
   (used in SPARC64, among others).
 
-  Please read the comments at the top of drivers/ide/ns87415.c.
+  Please read the comments at the top of <file:drivers/ide/ns87415.c>.
 
-OPTi 82C621 enhanced support (EXPERIMENTAL)
+OPTi 82C621 chipset enhanced support (EXPERIMENTAL)
 CONFIG_BLK_DEV_OPTI621
   This is a driver for the OPTi 82C621 EIDE controller.
-  Please read the comments at the top of drivers/ide/opti621.c.
+  Please read the comments at the top of <file:drivers/ide/opti621.c>.
 
-ServerWorks OSB4 chipset support (EXPERIMENTAL)
-CONFIG_BLK_DEV_OSB4
-  This driver adds PIO/DMA support for the Serverworks OSB4 chipset
+ServerWorks OSB4/CSB5 chipset support
+CONFIG_BLK_DEV_SVWKS
+  This driver adds PIO/(U)DMA support for the ServerWorks OSB4/CSB5
+  chipsets.
 
 Intel PIIXn chipsets support
 CONFIG_BLK_DEV_PIIX
@@ -907,7 +1068,7 @@
   PIO 0-4 mode settings, this allows dynamic tuning of the chipset
   via the standard end-user tool 'hdparm'.
 
-  Please read the comments at the top of drivers/ide/piix.c.
+  Please read the comments at the top of <file:drivers/ide/piix.c>.
 
   If you say Y here, you should also say Y to "PIIXn Tuning support",
   below.
@@ -926,29 +1087,30 @@
 
   If unsure, say N.
 
-PROMISE PDC20246/PDC20262/PDC20267 support
+PROMISE PDC20246/PDC20262/PDC20265/PDC20267/PDC20268 support
 CONFIG_BLK_DEV_PDC202XX
   Promise Ultra33 or PDC20246
   Promise Ultra66 or PDC20262
-  Promise Ultra100 or PDC20265/PDC20267
+  Promise Ultra100 or PDC20265/PDC20267/PDC20268
 
   This driver adds up to 4 more EIDE devices sharing a single
   interrupt. This add-on card is a bootable PCI UDMA controller. Since
   multiple cards can be installed and there are BIOS ROM problems that
   happen if the BIOS revisions of all installed cards (three-max) do
   not match, the driver attempts to do dynamic tuning of the chipset
-  at boot-time for max-speed. Ultra33 BIOS 1.25 or newer is required
+  at boot-time for max-speed.  Ultra33 BIOS 1.25 or newer is required
   for more than one card. This card may require that you say Y to
-  "Special UDMA Feature (EXPERIMENTAL)".
+  "Special UDMA Feature".
 
   If you say Y here, you need to say Y to "Use DMA by default when
   available" as well.
 
-  Please read the comments at the top of drivers/ide/pdc202xx.c
+  Please read the comments at the top of
+  <file:drivers/ide/pdc202xx.c>.
 
   If unsure, say N.
 
-Special UDMA Feature (EXPERIMENTAL)
+Special UDMA Feature
 CONFIG_PDC202XX_BURST
   For PDC20246, PDC20262, PDC20265 and PDC20267 Ultra DMA chipsets.
   Designed originally for PDC20246/Ultra33 that has BIOS setup
@@ -956,10 +1118,15 @@
 
   Unknown for PDC20265/PDC20267 Ultra DMA 100.
 
-  Please read the comments at the top of drivers/ide/pdc202xx.c
+  Please read the comments at the top of
+  <file:drivers/ide/pdc202xx.c>.
 
   If unsure, say N.
 
+Special FastTrak Feature
+CONFIG_PDC202XX_FORCE
+  For FastTrak enable overriding BIOS.
+
 SiS5513 chipset support
 CONFIG_BLK_DEV_SIS5513
   This driver ensures (U)DMA support for SIS5513 chipset based
@@ -969,20 +1136,21 @@
   If you say Y here, you need to say Y to "Use DMA by default when
   available" as well.
 
-  Please read the comments at the top of drivers/ide/sis5513.c
+  Please read the comments at the top of <file:drivers/ide/sis5513.c>.
 
 SLC90E66 chipset support
 CONFIG_BLK_DEV_SLC90E66
   This driver ensures (U)DMA support for Victroy66 SouthBridges for
   SMsC with Intel NorthBridges.  This is an Ultra66 based chipset.
   The nice thing about it is that you can mix Ultra/DMA/PIO devices
-  and it will handle timing cycles.  Since this is an improved look-a-like
-  to the PIIX4 it should be a nice addition.
+  and it will handle timing cycles.  Since this is an improved
+  look-a-like to the PIIX4 it should be a nice addition.
 
   If you say Y here, you need to say Y to "Use DMA by default when
   available" as well.
 
-  Please read the comments at the top of drivers/ide/slc90e66.c
+  Please read the comments at the top of
+  <file:drivers/ide/slc90e66.c>.
 
 Winbond SL82c105 support
 CONFIG_BLK_DEV_SL82C105
@@ -990,35 +1158,34 @@
   special configuration for this chip. This is common on various CHRP
   motherboards, but could be used elsewhere. If in doubt, say Y.
 
-Tekram TRM290 chipset support (EXPERIMENTAL)
+Tekram TRM290 chipset support
 CONFIG_BLK_DEV_TRM290
   This driver adds support for bus master DMA transfers
   using the Tekram TRM290 PCI IDE chip. Volunteers are
   needed for further tweaking and development.
-  Please read the comments at the top of drivers/ide/trm290.c.
+  Please read the comments at the top of <file:drivers/ide/trm290.c>.
 
 VIA82CXXX chipset support
 CONFIG_BLK_DEV_VIA82CXXX
   This allows you to configure your chipset for a better use while
-  running (U)DMA: it will allow you to enable efficiently the second
-  channel dma usage, as it may not be set by BIOS. It allows you to
-  pass a kernel command line at boot time in order to set fifo
-  config. If no command line is provided, it will try to set fifo
-  configuration at its best. It will allow you to get information from
-  /proc/ide/via provided you enabled "proc" support.
+  running PIO/(U)DMA, it will allow you to enable efficiently the
+  second channel dma usage, as it may not be set by BIOS.  It will try
+  to set fifo configuration at its best.  It will allow you to get
+  information from /proc/ide/via provided you enabled "/proc file
+  system" support.
 
-  Please read the comments at the top of drivers/ide/via82cxxx.c
+  Please read the comments at the top of
+  <file:drivers/ide/via82cxxx.c>.
 
   If you say Y here, then say Y to "Use DMA by default when available"
   as well.
 
   If unsure, say N.
 
-VIA82CXXX Tuning support (WIP)
-CONFIG_VIA82CXXX_TUNING
-  Please read the comments at the top of drivers/ide/via82cxxx.c
-
-  If unsure, say N.
+RapIDE interface support
+CONFIG_BLK_DEV_IDE_RAPIDE
+  Say Y here if you want to support the Yellowstone RapIDE controller
+  manufactured for use with Acorn computers.
 
 Other IDE chipset support
 CONFIG_IDE_CHIPSETS
@@ -1030,9 +1197,9 @@
   setting of higher speed I/O rates to improve system performance with
   these chipsets. Most of these also require special kernel boot
   parameters to actually turn on the support at runtime; you can find
-  a list of these in the file Documentation/ide.txt.
-  
-  People with SCSI-only systems can say N here. 
+  a list of these in the file <file:Documentation/ide.txt>.
+
+  People with SCSI-only systems can say N here.
 
 Generic 4 drives/port support
 CONFIG_BLK_DEV_4DRIVES
@@ -1045,53 +1212,64 @@
 ALI M14xx support
 CONFIG_BLK_DEV_ALI14XX
   This driver is enabled at runtime using the "ide0=ali14xx" kernel
-  boot parameter. It enables support for the secondary IDE interface
+  boot parameter.  It enables support for the secondary IDE interface
   of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
-  I/O speeds to be set as well. See the files Documentation/ide.txt
-  and drivers/ide/ali14xx.c for more info.
+  I/O speeds to be set as well.  See the files
+  <file:Documentation/ide.txt> and <file:drivers/ide/ali14xx.c> for
+  more info.
 
 DTC-2278 support
 CONFIG_BLK_DEV_DTC2278
   This driver is enabled at runtime using the "ide0=dtc2278" kernel
   boot parameter. It enables support for the secondary IDE interface
   of the DTC-2278 card, and permits faster I/O speeds to be set as
-  well. See the Documentation/ide.txt and drivers/ide/dtc2278.c
-  files for more info.
+  well. See the <file:Documentation/ide.txt> and
+  <file:drivers/ide/dtc2278.c> files for more info.
 
 Holtek HT6560B support
 CONFIG_BLK_DEV_HT6560B
   This driver is enabled at runtime using the "ide0=ht6560b" kernel
   boot parameter. It enables support for the secondary IDE interface
   of the Holtek card, and permits faster I/O speeds to be set as well.
-  See the Documentation/ide.txt and drivers/ide/ht6560b.c files for
-  more info.
+  See the <file:Documentation/ide.txt> and
+  <file:drivers/ide/ht6560b.c> files for more info.
 
 PROMISE DC4030 support (EXPERIMENTAL)
 CONFIG_BLK_DEV_PDC4030
   This driver provides support for the secondary IDE interface and
-  cache of Promise IDE chipsets, e.g. DC4030 and DC5030. This driver
+  cache of Promise IDE chipsets, e.g. DC4030 and DC5030.  This driver
   is known to incur timeouts/retries during heavy I/O to drives
-  attached to the secondary interface. CDROM and TAPE devices are not
-  supported yet. This driver is enabled at runtime using the
-  "ide0=dc4030" kernel boot parameter. See the Documentation/ide.txt
-  and drivers/ide/pdc4030.c files for more info.
+  attached to the secondary interface.  CD-ROM and TAPE devices are
+  not supported yet.  This driver is enabled at runtime using the
+  "ide0=dc4030" kernel boot parameter.  See the
+  <file:Documentation/ide.txt> and <file:drivers/ide/pdc4030.c> files
+  for more info.
 
+# This is for Linus's tree.
 QDI QD6580 support
 CONFIG_BLK_DEV_QD6580
   This driver is enabled at runtime using the "ide0=qd6580" kernel
-  boot parameter. It permits faster I/O speeds to be set. See the
-  files Documentation/ide.txt and drivers/ide/qd6580.c for more
-  info.
+  boot parameter.  It permits faster I/O speeds to be set.  See the
+  <file:Documentation/ide.txt> and <file:drivers/ide/qd6580.c> for
+  more info.
+
+# This is for Alan's tree.  Note the name difference.
+QDI QD65XX support
+CONFIG_BLK_DEV_QD65XX
+  This driver is enabled at runtime using the "ide0=qd65xx" kernel
+  boot parameter.  It permits faster I/O speeds to be set.  See the
+  <file:Documentation/ide.txt> and <file:drivers/ide/qd65xx.c> for
+  more info.
 
 UMC 8672 support
 CONFIG_BLK_DEV_UMC8672
   This driver is enabled at runtime using the "ide0=umc8672" kernel
   boot parameter. It enables support for the secondary IDE interface
   of the UMC-8672, and permits faster I/O speeds to be set as well.
-  See the files Documentation/ide.txt and drivers/ide/umc8672.c for
-  more info.
+  See the files <file:Documentation/ide.txt> and
+  <file:drivers/ide/umc8672.c> for more info.
 
-Amiga builtin Gayle IDE interface support
+Amiga Gayle IDE interface support
 CONFIG_BLK_DEV_GAYLE
   This is the IDE driver for the builtin IDE interface on some Amiga
   models. It supports both the `A1200 style' (used in A600 and A1200)
@@ -1107,11 +1285,11 @@
   disks, CD-ROM drives, etc.) that are connected to the builtin IDE
   interface.
 
-Amiga Buddha/Catweasel IDE interface support (EXPERIMENTAL)
+Amiga Buddha/Catweasel/X-Surf IDE interface support (EXPERIMENTAL)
 CONFIG_BLK_DEV_BUDDHA
-  This is the IDE driver for the IDE interfaces on the Buddha and
-  Catweasel expansion boards.  It supports up to two interfaces on the
-  Buddha and three on the Catweasel.
+  This is the IDE driver for the IDE interfaces on the Buddha, 
+  Catweasel and X-Surf expansion boards.  It supports up to two interfaces 
+  on the Buddha, three on the Catweasel and two on the X-Surf.
 
   Say Y if you have a Buddha or Catweasel expansion board and want to
   use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
@@ -1131,10 +1309,16 @@
   Say Y if you have an IDE doubler.  The driver is enabled at kernel
   runtime using the "ide=doubler" kernel boot parameter.
 
-Support for PowerMac IDE devices (must also enable IDE)
+WarpEngine SCSI support
+CONFIG_WARPENGINE_SCSI
+  Support for MacroSystem Development's WarpEngine Amiga SCSI-2
+  controller. Info at
+  <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>.
+
+Builtin PowerMac IDE support
 CONFIG_BLK_DEV_IDE_PMAC
-  This driver provides support for the built-in IDE controller on most
-  of the recent Apple Power Macintoshes and PowerBooks.
+  This driver provides support for the built-in IDE controller on
+  most of the recent Apple Power Macintoshes and PowerBooks.
   If unsure, say Y.
 
 PowerMac IDE DMA support
@@ -1164,29 +1348,6 @@
   devices (hard disks, CD-ROM drives, etc.) that are connected to the
   builtin IDE interface.
 
-MPC8xx IDE support
-CONFIG_BLK_DEV_MPC8xx_IDE
-  This option provides support for IDE on Motorola MPC8xx Systems.
-  Please see 'Type of MPC8xx IDE interface' for details.
-
-  If unsure, say N.
-
-Type of MPC8xx IDE interface
-CONFIG_IDE_8xx_PCCARD
-  Select how the IDE devices are connected to the MPC8xx system:
-
-  8xx_PCCARD uses the 8xx internal PCMCIA interface in combination
-             with a PC Card (e.g. ARGOSY portable Hard Disk Adapter),
-             ATA PC Card HDDs or ATA PC Flash Cards (example: TQM8xxL
-             systems)
-
-  8xx_DIRECT is used for directly connected IDE devices using the 8xx
-             internal PCMCIA interface (example: IVMS8 systems)
-
-  EXT_DIRECT is used for IDE devices directly connected to the 8xx
-             bus using some glue logic, but _not_ the 8xx internal
-             PCMCIA interface (example: IDIF860 systems)
-
 ICS IDE interface support
 CONFIG_BLK_DEV_IDE_ICSIDE
   On Acorn systems, say Y here if you wish to use the ICS IDE
@@ -1212,12 +1373,12 @@
 XT hard disk support
 CONFIG_BLK_DEV_XD
   Very old 8 bit hard disk controllers used in the IBM XT computer
-  will be supported if you say Y here. 
+  will be supported if you say Y here.
 
   If you want to compile the driver as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt. The module will be
-  called xd.o. 
+  say M here and read <file:Documentation/modules.txt>. The module
+  will be called xd.o.
 
   It's pretty unlikely that you have one of these: say N.
 
@@ -1225,23 +1386,23 @@
 CONFIG_BLK_DEV_PS2
   Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
   hard disk.
-  
+
   If you want to compile the driver as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt. The module will be
-  called ps2esdi.o.
+  say M here and read <file:Documentation/modules.txt>.  The module
+  will be called ps2esdi.o.
 
 Mylex DAC960/DAC1100 PCI RAID Controller support
 CONFIG_BLK_DEV_DAC960
   This driver adds support for the Mylex DAC960, AcceleRAID, and
-  eXtremeRAID PCI RAID controllers. See the file
-  Documentation/README.DAC960 for further information about this
-  driver.
+  eXtremeRAID PCI RAID controllers.  See the file
+  <file:Documentation/README.DAC960> for further information about
+  this driver.
 
   If you want to compile the driver as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt.  The module will be
-  called DAC960.o. 
+  say M here and read <file:Documentation/modules.txt>.  The module
+  will be called DAC960.o.
 
 Parallel port IDE device support
 CONFIG_PARIDE
@@ -1249,7 +1410,7 @@
   your computer's parallel port. Most of them are actually IDE devices
   using a parallel port IDE adapter. This option enables the PARIDE
   subsystem which contains drivers for many of these external drives.
-  Read Documentation/paride.txt for more information.
+  Read <file:Documentation/paride.txt> for more information.
 
   If you have said Y to the "Parallel-port support" configuration
   option, you may share a single port between your printer and other
@@ -1270,13 +1431,13 @@
 
 Parallel port IDE disks
 CONFIG_PARIDE_PD
-  This option enables the high-level driver for IDE-type disk devices 
-  connected through a parallel port. If you chose to build PARIDE 
-  support into your kernel, you may answer Y here to build in the 
-  parallel port IDE driver, otherwise you should answer M to build 
-  it as a loadable module. The module will be called pd.o. You 
-  must also have at least one parallel port protocol driver in your 
-  system. Among the devices supported by this driver are the SyQuest 
+  This option enables the high-level driver for IDE-type disk devices
+  connected through a parallel port. If you chose to build PARIDE
+  support into your kernel, you may answer Y here to build in the
+  parallel port IDE driver, otherwise you should answer M to build
+  it as a loadable module. The module will be called pd.o. You
+  must also have at least one parallel port protocol driver in your
+  system. Among the devices supported by this driver are the SyQuest
   EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack
   hard drives from MicroSolutions.
 
@@ -1291,8 +1452,8 @@
   system. Among the devices supported by this driver are the
   MicroSolutions backpack CD-ROM drives and the Freecom Power CD. If
   you have such a CD-ROM drive, you should also say Y or M to "ISO
-  9660 CDROM file system support" below, because that's the file
-  system used on CDROMs.
+  9660 CD-ROM file system support" below, because that's the file
+  system used on CD-ROMs.
 
 Parallel port ATAPI disks
 CONFIG_PARIDE_PF
@@ -1322,7 +1483,7 @@
   This option enables a special high-level driver for generic ATAPI
   devices connected through a parallel port. The driver allows user
   programs, such as cdrecord, to send ATAPI commands directly to a
-  device. 
+  device.
 
   If you chose to build PARIDE support into your kernel, you may
   answer Y here to build in the parallel port generic ATAPI driver,
@@ -1333,10 +1494,10 @@
   your system.
 
   This driver implements an API loosely related to the generic SCSI
-  driver. See include/linux/pg.h for details.
+  driver. See <file:include/linux/pg.h>. for details.
 
   You can obtain the most recent version of cdrecord from
-  ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/ . Versions 1.6.1a3 and
+  <ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/>. Versions 1.6.1a3 and
   later fully support this driver.
 
 ATEN EH-100 protocol
@@ -1352,39 +1513,40 @@
 
 Micro Solutions BACKPACK Series 5 protocol
 CONFIG_PARIDE_BPCK
-  This option enables support for the Micro Solutions BACKPACK parallel
-  port Series 5 IDE protocol. (Most BACKPACK drives made before 1999 were 
-  Series 5) Series 5 drives will NOT always have the Series noted on the
-  bottom of the drive. Series 6 drivers will. 
+  This option enables support for the Micro Solutions BACKPACK
+  parallel port Series 5 IDE protocol.  (Most BACKPACK drives made
+  before 1999 were Series 5) Series 5 drives will NOT always have the
+  Series noted on the bottom of the drive. Series 6 drivers will.
 
   In other words, if your BACKPACK drive dosen't say "Series 6" on the
   bottom, enable this option.
 
-  If you chose to build PARIDE support into your kernel, you may answer Y
-  here to build in the protocol driver, otherwise you should answer M to
-  build it as a loadable module. The module will be called bpck.o. You
-  must also have a high-level driver for the type of device that you want
-  to support.
+  If you chose to build PARIDE support into your kernel, you may
+  answer Y here to build in the protocol driver, otherwise you should
+  answer M to build it as a loadable module.  The module will be
+  called bpck.o.  You must also have a high-level driver for the type
+  of device that you want to support.
 
 Micro Solutions BACKPACK Series 6 protocol
 CONFIG_PARIDE_BPCK6
-  This option enables support for the Micro Solutions BACKPACK parallel
-  port Series 6 IDE protocol. (Most BACKPACK drives made after 1999 were 
-  Series 6) Series 6 drives will have the Series noted on the bottom of
-  the drive. Series 5 drivers don't always have it noted. 
+  This option enables support for the Micro Solutions BACKPACK
+  parallel port Series 6 IDE protocol.  (Most BACKPACK drives made
+  after 1999 were Series 6) Series 6 drives will have the Series noted
+  on the bottom of the drive.  Series 5 drivers don't always have it
+  noted.
 
-  In other words, if your BACKPACK drive says "Series 6" on the bottom,
-  enable this option.
+  In other words, if your BACKPACK drive says "Series 6" on the
+  bottom, enable this option.
 
-  If you chose to build PARIDE support into your kernel, you may answer Y
-  here to build in the protocol driver, otherwise you should answer M to
-  build it as a loadable module. The module will be called bpck6.o. You
-  must also have a high-level driver for the type of device that you want
-  to support.
+  If you chose to build PARIDE support into your kernel, you may
+  answer Y here to build in the protocol driver, otherwise you should
+  answer M to build it as a loadable module.  The module will be
+  called bpck6.o.  You must also have a high-level driver for the type
+  of device that you want to support.
 
 DataStor Commuter protocol
 CONFIG_PARIDE_COMM
-  This option enables support for the Commuter parallel port IDE 
+  This option enables support for the Commuter parallel port IDE
   protocol from DataStor. If you chose to build PARIDE support
   into your kernel, you may answer Y here to build in the protocol
   driver, otherwise you should answer M to build it as a loadable
@@ -1393,7 +1555,7 @@
 
 DataStor EP-2000 protocol
 CONFIG_PARIDE_DSTR
-  This option enables support for the EP-2000 parallel port IDE 
+  This option enables support for the EP-2000 parallel port IDE
   protocol from DataStor. If you chose to build PARIDE support
   into your kernel, you may answer Y here to build in the protocol
   driver, otherwise you should answer M to build it as a loadable
@@ -1412,7 +1574,7 @@
   have a high-level driver for the type of device that you want to
   support.
 
-Shuttle EPAT c7/c8 extension 
+Shuttle EPAT c7/c8 extension
 CONFIG_PARIDE_EPATC8
   This option enables support for the newer Shuttle EP1284 (aka c7 and
   c8) chip. You need this if you are using any recent Imation SuperDisk
@@ -1453,12 +1615,12 @@
 Freecom IQ ASIC-2 protocol
 CONFIG_PARIDE_FRIQ
   This option enables support for version 2 of the Freecom IQ parallel
-  port IDE adapter.  This adapter is used by the Maxell Superdisk 
+  port IDE adapter.  This adapter is used by the Maxell Superdisk
   drive.  If you chose to build PARIDE support into your kernel, you
   may answer Y here to build in the protocol driver, otherwise you
   should answer M to build it as a loadable module. The module will be
   called friq.o. You must also have a high-level driver for the type
-  of device that you want to support. 
+  of device that you want to support.
 
 FreeCom power protocol
 CONFIG_PARIDE_FRPW
@@ -1493,12 +1655,12 @@
 
 OnSpec 90c20 protocol
 CONFIG_PARIDE_ON20
-  This option enables support for the (obsolete) 90c20 parallel port 
+  This option enables support for the (obsolete) 90c20 parallel port
   IDE protocol from OnSpec (often marketed under the ValuStore brand
-  name). If you chose to build PARIDE support into your kernel, you 
-  may answer Y here to build in the protocol driver, otherwise you 
-  should answer M to build it as a loadable module. The module will 
-  be called on20.o. You must also have a high-level driver for the 
+  name). If you chose to build PARIDE support into your kernel, you
+  may answer Y here to build in the protocol driver, otherwise you
+  should answer M to build it as a loadable module. The module will
+  be called on20.o. You must also have a high-level driver for the
   type of device that you want to support.
 
 OnSpec 90c26 protocol
@@ -1522,13 +1684,19 @@
   to new capacity needs.  Logical volumes are accessed as block
   devices named /dev/VolumeGroupName/LogicalVolumeName.
 
-  For details see Documentation/LVM-HOWTO. You will need supporting
-  user space software; location is in Documentation/Changes.
+  For details see <file:Documentation/LVM-HOWTO>.  You will need
+  supporting user space software; location is in
+  <file:Documentation/Changes>.
 
   If you want to compile this support as a module ( = code which can
   be inserted in and removed from the running kernel whenever you
-  want), say M here and read Documentation/modules.txt. The module
-  will be called lvm-mod.o.
+  want), say M here and read <file:Documentation/modules.txt>.  The
+  module will be called lvm-mod.o.
+
+Multiple devices driver support (RAID and LVM)
+CONFIG_MD
+  Support multiple physical spindles through a single logical device.
+  Required for RAID and logical volume management (LVM).
 
 Multiple devices driver support
 CONFIG_BLK_DEV_MD
@@ -1543,7 +1711,7 @@
 
   More information about Software RAID on Linux is contained in the
   Software-RAID mini-HOWTO, available from
-  http://www.linuxdoc.org/docs.html#howto . There you will also
+  <http://www.linuxdoc.org/docs.html#howto>. There you will also
   learn where to get the supporting user space utilities raidtools.
 
   If unsure, say N.
@@ -1552,12 +1720,12 @@
 CONFIG_MD_LINEAR
   If you say Y here, then your multiple devices driver will be able to
   use the so-called linear mode, i.e. it will combine the hard disk
-  partitions by simply appending one to the other. 
+  partitions by simply appending one to the other.
 
   If you want to compile this as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt. The module will be
-  called linear.o.
+  say M here and read <file:Documentation/modules.txt>.  The module
+  will be called linear.o.
 
   If unsure, say Y.
 
@@ -1567,40 +1735,40 @@
   use the so-called raid0 mode, i.e. it will combine the hard disk
   partitions into one logical device in such a fashion as to fill them
   up evenly, one chunk here and one chunk there. This will increase
-  the throughput rate if the partitions reside on distinct disks. 
+  the throughput rate if the partitions reside on distinct disks.
 
   Information about Software RAID on Linux is contained in the
   Software-RAID mini-HOWTO, available from
-  http://www.linuxdoc.org/docs.html#howto . There you will also
+  <http://www.linuxdoc.org/docs.html#howto>. There you will also
   learn where to get the supporting user space utilities raidtools.
 
   If you want to compile this as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt. The module will be
-  called raid0.o.
+  say M here and read <file:Documentation/modules.txt>.  The module
+  will be called raid0.o.
 
   If unsure, say Y.
 
 RAID-1 (mirroring) mode
 CONFIG_MD_RAID1
   A RAID-1 set consists of several disk drives which are exact copies
-  of each other. In the event of a mirror failure, the RAID driver
+  of each other.  In the event of a mirror failure, the RAID driver
   will continue to use the operational mirrors in the set, providing
   an error free MD (multiple device) to the higher levels of the
-  kernel. In a set with N drives, the available space is the capacity
+  kernel.  In a set with N drives, the available space is the capacity
   of a single drive, and the set protects against a failure of (N - 1)
-  drives. 
+  drives.
 
   Information about Software RAID on Linux is contained in the
   Software-RAID mini-HOWTO, available from
-  http://www.linuxdoc.org/docs.html#howto . There you will also
+  <http://www.linuxdoc.org/docs.html#howto>.  There you will also
   learn where to get the supporting user space utilities raidtools.
 
   If you want to use such a RAID-1 set, say Y. This code is also
   available as a module called raid1.o ( = code which can be inserted
-  in and removed from the running kernel whenever you want). If you
+  in and removed from the running kernel whenever you want).  If you
   want to compile it as a module, say M here and read
-  Documentation/modules.txt.
+  <file:Documentation/modules.txt>.
 
   If unsure, say Y.
 
@@ -1616,41 +1784,92 @@
 
   Information about Software RAID on Linux is contained in the
   Software-RAID mini-HOWTO, available from
-  http://www.linuxdoc.org/docs.html#howto . There you will also
+  <http://www.linuxdoc.org/docs.html#howto>. There you will also
   learn where to get the supporting user space utilities raidtools.
 
   If you want to use such a RAID-4/RAID-5 set, say Y. This code is
   also available as a module called raid5.o ( = code which can be
   inserted in and removed from the running kernel whenever you want).
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.
+  <file:Documentation/modules.txt>.
 
   If unsure, say Y.
 
+Multipath I/O support
+CONFIG_MD_MULTIPATH
+  Multipath-IO is the ability of certain devices to address the same
+  physical disk over multiple 'IO paths'. The code ensures that such
+  paths can be defined and handled at runtime, and ensures that a
+  transparent failover to the backup path(s) happens if a IO errors
+  arrives on the primary path.
+
+  If unsure, say N.
+
+# AC tree only
+Support for IDE Raid controllers
+CONFIG_BLK_DEV_ATARAID
+  Say Y or M if you have an IDE Raid controller and want linux
+  to use its softwareraid feature.  You must also select an
+  appropriate for your board low-level driver below.
+
+  Note, that Linux does not use the Raid implemetation in BIOS, and
+  the main purpose for this feature is to retain compatibility and
+  data integrity with other OS-es, using the same disk array. Linux
+  has its own Raid drivers, which you should use if you need better
+  performance.
+
+# AC tree only
+Support Promise software RAID (Fasttrak(tm))
+CONFIG_BLK_DEV_ATARAID_PDC
+  Say Y or M if you have a Promise Fasttrak (tm) Raid controller
+  and want linux to use the softwareraid feature of this card.
+  This driver uses /dev/ataraid/dXpY (X and Y numbers) as device
+  names.
+
+  If you choose to compile this as a module, the module will be called
+  pdcraid.o.
+
+# AC tree only
+Highpoint 370 software RAID
+CONFIG_BLK_DEV_ATARAID_HPT
+  Say Y or M if you have a Highpoint HPT 370 Raid controller
+  and want linux to use the softwareraid feature of this card.
+  This driver uses /dev/ataraid/dXpY (X and Y numbers) as device
+  names.
+
+  If you choose to compile this as a module, the module will be called
+  hptraid.o.
+
 Support for Acer PICA 1 chipset
 CONFIG_ACER_PICA_61
   This is a machine with a R4400 133/150 MHz CPU. To compile a Linux
   kernel that runs on these, say Y here. For details about Linux on
   the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
-  http://oss.sgi.com/mips .
+  <http://oss.sgi.com/mips>.
 
 Support for Algorithmics P4032 (EXPERIMENTAL)
 CONFIG_ALGOR_P4032
-  This is an evaluation board of the British company Algorithmics. The
-  board uses the R4300 and a R5230 CPUs. For more information about
-  this board see http://www.algor.co.uk .
+  This is an evaluation board of the British company Algorithmics.
+  The board uses the R4300 and a R5230 CPUs.  For more information
+  about this board see <http://www.algor.co.uk>.
 
 Support for BAGET MIPS series
 CONFIG_BAGET_MIPS
-  This enables support for the Baget, a Russian embedded system.  For 
-  more details about the Baget see the Linux/MIPS FAQ on 
-  http://oss.sgi.com/mips .
+  This enables support for the Baget, a Russian embedded system.  For
+  more details about the Baget see the Linux/MIPS FAQ on
+  <http://oss.sgi.com/mips>.
+
+Baget AMD LANCE support
+CONFIG_BAGETLANCE
+  Say Y to enable kernel support for AMD Lance Ethernet cards on the
+  MIPS-32-based Baget embedded system.  This chipset is better known
+  via the NE2100 cards.
 
 Support for DECstations
 CONFIG_DECSTATION
   This enables support for DEC's MIPS based workstations.  For details
-  see the Linux/MIPS FAQ on http://oss.sgi.com/mips and the 
-  DECstation porting pages on http://decstation.unix-ag.org .
+  see the Linux/MIPS FAQ on <http://oss.sgi.com/mips> and the
+  DECstation porting pages on <http://decstation.unix-ag.org>.
 
   If you have one of the following DECstation Models you definitely
   want to choose R4xx0 for the CPU Type:
@@ -1662,6 +1881,25 @@
 
   otherwise choose R3000.
 
+Support for Cobalt Micro Server
+CONFIG_COBALT_MICRO_SERVER
+  Support for MIPS-based Cobalt boxes (they have been bought by Sun
+  and are now the "Server Appliance Business Unit") including the 2700
+  series -- versions 1 of the Qube and Raq.  To compile a Linux kernel
+  for this hardware, say Y here.
+
+Support for Cobalt 2800
+CONFIG_COBALT_28
+  Support for the second generation of MIPS-based Cobalt boxes (they
+  have been bought by Sun and are now the "Server Appliance Business
+  Unit") including the 2800 series -- versions 2 of the Qube and Raq.
+  To compile a Linux kernel for this hardware, say Y here.
+
+Support for the Momentum Computer Ocelot SBC
+CONFIG_MOMENCO_OCELOT
+  The Ocelot is a MIPS-based Single Board Computer (SBC) made by
+  Momentum Computer <http://www.momenco.com>.
+
 Support for NEC DDB Vrc-5074
 CONFIG_DDB5074
   This enables support for the VR5000-based NEC DDB Vrc-5074
@@ -1673,10 +1911,18 @@
   evaluation board.
 
   Features : kernel debugging, serial terminal, NFS root fs, on-board
-  ether port (with a patch to tulip driver), IDE controller, PS2 keyboard
-  PS2 mouse, etc.
+  ether port (Need an additional patch at <http://linux.junsun.net>),
+  USB, AC97, PCI, PCI VGA card & framebuffer console, IDE controller,
+  PS2 keyboard, PS2 mouse, etc.
+
+Support for NEC DDB Vrc-5477
+CONFIG_DDB5477
+  This enables support for the R5432-based NEC DDB Vrc-5477
+  evaluation board.
 
-  TODO : USB, Compact-PCI interface.
+  Features : kernel debugging, serial terminal, NFS root fs, on-board
+  ether port (Need an additional patch at <http://linux.junsun.net>),
+  USB, AC97, PCI, etc.
 
 Support for MIPS Atlas board
 CONFIG_MIPS_ATLAS
@@ -1688,19 +1934,39 @@
   This enables support for the VR5000-based MIPS Malta evaluation
   board.
 
+Support for Galileo Evaluation board or CoSine Orion
+CONFIG_ORION
+  Say Y if configuring for the Galileo evaluation board
+  or CoSine Orion.  More information is available at
+  <http://tochna.technion.ac.il/project/linux/html/linux.html>.
+
+  Otherwise, say N.
+
 Support for Mips Magnum 4000
 CONFIG_MIPS_MAGNUM_4000
   This is a machine with a R4000 100 MHz CPU. To compile a Linux
   kernel that runs on these, say Y here. For details about Linux on
   the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
-  http://oss.sgi.com/mips.
+  <http://oss.sgi.com/mips>.
+
+Enable Qtronix 990P Keyboard Support
+CONFIG_QTRONIX_KEYBOARD
+  Images of Qtronix keyboards are at
+  <http://www.qtronix.com/keyboard.html>.
 
 Support for Olivetti M700
 CONFIG_OLIVETTI_M700
   This is a machine with a R4000 100 MHz CPU. To compile a Linux
   kernel that runs on these, say Y here. For details about Linux on
   the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
-  http://oss.sgi.com/mips.
+  <http://oss.sgi.com/mips>.
+
+Support for SNI RM200 PCI
+CONFIG_SNI_RM200_PCI
+  The SNI RM200 PCI was a MIPS-based platform manufactured by Siemens
+  Nixdorf Informationssysteme (SNI), parent company of Pyramid
+  Technology and now in turn merged with Fujitsu.  Say Y here to
+  support this machine type.
 
 Support for SGI IP22
 CONFIG_SGI_IP22
@@ -1709,6 +1975,7 @@
   that runs on these, say Y here.
 
 Support for SGI IP27
+CONFIG_SGI_IP27
   This are the SGI Origin 200, Origin 2000 and Onyx 2 Graphics
   workstations.  To compile a Linux kernel that runs on these, say Y
   here.
@@ -1731,11 +1998,49 @@
   4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
   systems.
 
+MIPS GT96100 support
+CONFIG_MIPS_GT96100
+  Say Y here to support the Galileo Technology GT96100 communications
+  controller card.  There is a web page at <http://www.galileot.com/>.
+
+MIPS GT96100 Ethernet support
+CONFIG_MIPS_GT96100ETH
+  Say Y here to support the Ethernet subsystem on your GT96100 card.
+
+Zalon SCSI support
+CONFIG_SCSI_ZALON
+  The Zalon is an interface chip that sits between the PA-RISC
+  processor and the NCR 53c720 SCSI controller on K-series PA-RISC
+  boards (these are used, among other places, on some HP 780
+  workstations).  Say Y here to make sure it gets initialized
+  correctly before the Linux kernel tries to talk to the controller.
+
 Kernel floating-point instruction emulation
 CONFIG_MIPS_FPU_EMULATOR
-  This option enables the MIPS software floatingpoint support.  Due to the
-  way floatingpoint works you should always enable this option unless
-  you exactly know what you're doing.
+  This option enables the MIPS software floatingpoint support.  Due to
+  the way floating point works you should always enable this option
+  unless you exactly know what you're doing.
+
+SGI PROM Console Support
+CONFIG_SGI_PROM_CONSOLE
+  Say Y here to set up the boot console on serial port 0.
+
+DZ11 Serial Support
+CONFIG_DZ
+  DZ11-family serial controllers for VAXstations, including the
+  DC7085, M7814, and M7819.
+
+
+TURBOchannel support
+CONFIG_TC
+  TurboChannel is a DEC (now Compaq) bus for Alpha and MIPS processors.
+  Documentation on writing device drivers for TurboChannel is available at:
+  <http://www.cs.arizona.edu/computer.help/policy/DIGITAL_unix/AA-PS3HD-TET1_html/TITLE.html>.
+
+Z85C30 Serial Support
+CONFIG_ZS
+  Documentation on the Zilog 85C350 serial communications controller
+  is downloadable at <http://www.zilog.com/pdfs/serial/z85c30.pdf>.
 
 PCMCIA SCSI adapter support
 CONFIG_SCSI_PCMCIA
@@ -1744,9 +2049,30 @@
   size devices often used with laptops.
 
   Note that the answer to this question won't directly affect the
-  kernel: saying N will just cause this configure script to skip all
+  kernel: saying N will just cause the configurator to skip all
   the questions PCMCIA SCSI host adapters.
 
+Adaptec APA1480 CardBus support
+CONFIG_PCMCIA_APA1480
+  Say Y here if you intend to attach this type of CardBus SCSI host
+  adapter to your computer.
+
+  This driver is also available as a module called apa1480_cb.o ( =
+  code which can be inserted in and removed from the running kernel
+  whenever you want). If you want to compile it as a module, say M
+  here and read <file:Documentation/modules.txt>.
+
+NinjaSCSI-3 / NinjaSCSI-32Bi (16bit) PCMCIA support
+CONFIG_PCMCIA_NINJA_SCSI
+  If you intend to attach this type of PCMCIA SCSI host adapter to
+  your computer, say Y here and read
+  <file:Documentation/README.nsp_cs>.
+
+  This driver is also available as a module called nsp_cs.o ( =
+  code which can be inserted in and removed from the running kernel
+  whenever you want). If you want to compile it as a module, say M
+  here and read <file:Documentation/modules.txt>.
+
 Adaptec AHA152X PCMCIA support
 CONFIG_PCMCIA_AHA152X
   Say Y here if you intend to attach this type of PCMCIA SCSI host
@@ -1755,7 +2081,7 @@
   This driver is also available as a module called aha152x_cs.o ( =
   code which can be inserted in and removed from the running kernel
   whenever you want). If you want to compile it as a module, say M
-  here and read Documentation/modules.txt.
+  here and read <file:Documentation/modules.txt>.
 
 Qlogic PCMCIA support
 CONFIG_PCMCIA_QLOGIC
@@ -1764,8 +2090,8 @@
 
   This driver is also available as a module called qlogic_cs.o ( =
   code which can be inserted in and removed from the running kernel
-  whenever you want). If you want to compile it as a module, say M
-  here and read Documentation/modules.txt.
+  whenever you want).  If you want to compile it as a module, say M
+  here and read <file:Documentation/modules.txt>.
 
 Future Domain PCMCIA support
 CONFIG_PCMCIA_FDOMAIN
@@ -1774,27 +2100,96 @@
 
   This driver is also available as a module called fdomain_cs.o ( =
   code which can be inserted in and removed from the running kernel
-  whenever you want). If you want to compile it as a module, say M
-  here and read Documentation/modules.txt.
-
-Adaptec APA1480 CardBus support
-CONFIG_PCMCIA_APA1480
-  Say Y here if you intend to attach this type of CardBus SCSI host
-  adapter to your computer.
-
-  This driver is also available as a module called apa1480_cb.o ( =
-  code which can be inserted in and removed from the running kernel
-  whenever you want). If you want to compile it as a module, say M
-  here and read Documentation/modules.txt.
+  whenever you want).  If you want to compile it as a module, say M
+  here and read <file:Documentation/modules.txt>.
 
+# Choice: mipstype
 CPU type
 CONFIG_CPU_R3000
   Please make sure to pick the right CPU type. Linux/MIPS is not
   designed to be generic, i.e. Kernels compiled for R3000 CPUs will
-  *not* work on R4000 Machines and vice versa.
-  However, since most the supported Machines have an R4000 (or 
-  similar) CPU, R4xx0 might be a safe bet.
-  If the resulting Kernel does not work try to recompile with R3000.
+  *not* work on R4000 machines and vice versa.  However, since most
+  of the supported machines have an R4000 (or similar) CPU, R4x00
+  might be a safe bet.  If the resulting kernel does not work,
+  try to recompile with R3000.
+
+  R3000    MIPS Technologies R3000-series processors,
+           including the 3041, 3051, and 3081.
+
+  R6000    MIPS Technologies R6000-series processors,
+           including the 64474, 64475, 64574 and 64575.
+
+  R4300    MIPS Technologies R4300-series processors.
+
+  R4x00    MIPS Technologies R4000-series processors other than 4300,
+           including the 4640, 4650, and 4700.
+
+  R5000    MIPS Technologies R5000-series processors other than the
+           Nevada.
+
+  R52xx    MIPS Technologies R52xx-series ("Nevada") processors.
+
+  R10000   MIPS Technologies R10000-series processors.
+
+R6000
+CONFIG_CPU_R6000
+  MIPS Technologies R6000-series processors, including the 64474,
+  64475, 64574 and 64575.
+
+R4300
+CONFIG_CPU_R4300
+  MIPS Technologies R4300-series processors.
+
+R4x00
+CONFIG_CPU_R4X00
+  MIPS Technologies R4000-series processors other than 4300, including
+  the 4640, 4650, and 4700.
+
+R5000
+CONFIG_CPU_R5000
+  MIPS Technologies R5000-series processors other than the Nevada.
+
+R52x0
+CONFIG_CPU_NEVADA
+  MIPS Technologies R52x0-series ("Nevada") processors.
+
+R8000
+CONFIG_CPU_R8000
+  MIPS Technologies R8000-series processors.
+
+R10000
+CONFIG_CPU_R10000
+  MIPS Technologies R10000-series processors.
+
+Discontiguous Memory Support
+CONFIG_DISCONTIGMEM
+  Say Y to upport efficient handling of discontiguous physical memory,
+  for architectures which are either NUMA (Non-Uniform Memory Access)
+  or have huge holes in the physical address space for other reasons.
+  See <file:Documentation/vm/numa> for more.
+
+Mapped kernel support
+CONFIG_MAPPED_KERNEL
+  Change the way a Linux kernel is loaded unto memory on a MIPS64
+  machine.  This is required in order to support text replication and
+  NUMA.  If you need to undersatand it, read the source code.
+
+Kernel text replication support
+CONFIG_REPLICATE_KTEXT
+  Say Y here to enable replicating the kernel text across multiple
+  nodes in a NUMA cluster.  This trades memory for speed.
+
+Exception handler replication support
+CONFIG_REPLICATE_EXHANDLERS
+  Say Y here to enable replicating the kernel exception handlers
+  across multiple nodes in a NUMA cluster. This trades memory for
+  speed.
+
+NUMA support?
+CONFIG_NUMA
+  Say Y to compile the kernel to support NUMA (Non-Uniform Memory
+  Access).  This option is for configuring high-end multiprocessor
+  server machines.  If in doubt, say N.
 
 CPU type
 CONFIG_CPU_VR41XX
@@ -1805,14 +2200,18 @@
 
 CPU feature configuration
 CONFIG_CPU_ADVANCED
-  Saying yes here allows you to select support for various features your
-  CPU may or may not have.  Most people should say N here.
+  Saying yes here allows you to select support for various features
+  your CPU may or may not have.  Most people should say N here.
 
-ll and sc instructions
+ll/sc Instructions available
 CONFIG_CPU_HAS_LLSC
-  Say Y here if your CPU has the ll and sc instructions.  Say Y here for
-  better performance, N if you don't know.  You must say Y here for
-  multiprocessor machines.
+  MIPS R4000 series and later provide the Load Linked (ll)
+  and Store Conditional (sc) instructions. More information is
+  available at <http://www.go-ecs.com/mips/miptek1.htm>.
+
+  Say Y here if your CPU has the ll and sc instructions.  Say Y here
+  for better performance, N if you don't know.  You must say Y here
+  for multiprocessor machines.
 
 lld and scd instructions
 CONFIG_CPU_HAS_LLDSCD
@@ -1820,7 +2219,7 @@
   equivalents of ll and sc.  Say Y here for better performance, N if
   you don't know.  You must say Y here for multiprocessor machines.
 
-Support for writebuffer flushing
+Writeback Buffer available
 CONFIG_CPU_HAS_WB
   Say N here for slightly better performance.  You must say Y here for
   machines which require flushing of write buffers in software.  Saying
@@ -1840,6 +2239,12 @@
   byte order. These modes require different kernels. Say Y if your
   machine is little endian, N if it's a big endian machine.
 
+Use power LED as a heartbeat
+CONFIG_HEARTBEAT
+  Use the power-on LED on your machine as a load meter.  The exact
+  behavior is platform-dependent, but normally the flash frequency is
+  a hyperbolic function of the 5-minute load average.
+
 Networking support
 CONFIG_NET
   Unless you really know what you are doing, you should say Y here.
@@ -1849,27 +2254,28 @@
   should consider updating your networking tools too because changes
   in the kernel and the tools often go hand in hand. The tools are
   contained in the package net-tools, the location and version number
-  of which are given in Documentation/Changes.
+  of which are given in <file:Documentation/Changes>.
 
   For a general introduction to Linux networking, it is highly
   recommended to read the NET-3-HOWTO, available from
-  http://www.linuxdoc.org/docs.html#howto .
+  <http://www.linuxdoc.org/docs.html#howto>.
 
 Socket filtering
 CONFIG_FILTER
   The Linux Socket Filter is derived from the Berkeley Packet Filter.
   If you say Y here, user-space programs can attach a filter to any
   socket and thereby tell the kernel that it should allow or disallow
-  certain types of data to get through the socket. Linux Socket
-  Filtering works on all socket types except TCP for now. See the text
-  file Documentation/networking/filter.txt for more information.
+  certain types of data to get through the socket.  Linux Socket
+  Filtering works on all socket types except TCP for now.  See the
+  text file <file:Documentation/networking/filter.txt> for more
+  information.
 
   You need to say Y here if you want to use PPP packet filtering
   (see the CONFIG_PPP_FILTER option below).
 
   If unsure, say N.
 
-Network packet filtering
+Network packet filtering (replaces ipchains)
 CONFIG_NETFILTER
   Netfilter is a framework for filtering and mangling network packets
   that pass through your Linux box.
@@ -1912,21 +2318,21 @@
   Various modules exist for netfilter which replace the previous
   masquerading (ipmasqadm), packet filtering (ipchains), transparent
   proxying, and portforwarding mechanisms. Please see
-  Documentation/Changes under "iptables" for the location of these
-  packages.
- 
+  <file:Documentation/Changes> under "iptables" for the location of
+  these packages.
+
   Make sure to say N to "Fast switching" below if you intend to say Y
   here, as Fast switching currently bypasses netfilter.
- 
+
   Chances are that you should say Y here if you compile a kernel which
   will run as a router and N for regular hosts. If unsure, say N.
- 
+
 Network packet filtering debugging
 CONFIG_NETFILTER_DEBUG
   You can say Y here if you want to get additional messages useful in
-  debugging the netfilter code. 
+  debugging the netfilter code.
 
-IP: connection tracking (required for masq/NAT)
+Connection tracking (required for masq/NAT)
 CONFIG_IP_NF_CONNTRACK
   Connection tracking keeps a record of what packets have passed
   through your machine, in order to figure out how they are related
@@ -1938,7 +2344,7 @@
   below).
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 IRC Send/Chat support
 CONFIG_IP_NF_IRC
@@ -1961,17 +2367,17 @@
   of Network Address Translation on them.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `Y'.
+  <file:Documentation/modules.txt>.  If unsure, say `Y'.
 
-IP: user space queueing via NETLINK (EXPERIMENTAL)
+User space queueing via NETLINK
 CONFIG_IP_NF_QUEUE
   Netfilter has the ability to queue packets to user space: the
   netlink device can be used to access them using this driver.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
-IP: ip tables support (required for filtering/masq/NAT)
+IP tables support (required for filtering/masq/NAT)
 CONFIG_IP_NF_IPTABLES
   iptables is a general, extensible packet identification framework.
   The packet filtering and full NAT (masquerading, port forwarding,
@@ -1979,41 +2385,7 @@
   either of those.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
-CONFIG_IP6_NF_MATCH_LIMIT
-  limit matching allows you to control the rate at which a rule can be
-  matched: mainly useful in combination with the LOG target ("LOG
-  target support", below) and to avoid some Denial of Service attacks.
-
-  If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
-
-MAC address match support
-CONFIG_IP6_NF_MATCH_MAC
-  mac matching allows you to match packets based on the source
-  ethernet address of the packet.
-
-  If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
-
-Multiple port match support
-CONFIG_IP6_NF_MATCH_MULTIPORT
-  Multiport matching allows you to match TCP or UDP packets based on
-  a series of source or destination ports: normally a rule can only
-  match a single range of ports.
-
-  If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
-
-Owner match support (EXPERIMENTAL)
-CONFIG_IP6_NF_MATCH_OWNER
-  Packet owner matching allows you to match locally-generated packets
-  based on who created them: the user, group, process or session.
-
-  If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
-
-
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 limit match support
 CONFIG_IP_NF_MATCH_LIMIT
@@ -2022,24 +2394,24 @@
   target support", below) and to avoid some Denial of Service attacks.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 MAC address match support
 CONFIG_IP_NF_MATCH_MAC
-  mac matching allows you to match packets based on the source
-  ethernet address of the packet.
+  MAC matching allows you to match packets based on the source
+  Ethernet address of the packet.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
-netfilter mark match support
+Netfilter MARK match support
 CONFIG_IP_NF_MATCH_MARK
   Netfilter mark matching allows you to match packets based on the
   `nfmark' value in the packet.  This can be set by the MARK target
   (see below).
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 Multiple port match support
 CONFIG_IP_NF_MATCH_MULTIPORT
@@ -2048,7 +2420,7 @@
   match a single range of ports.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 TTL match support
 CONFIG_IP_NF_MATCH_TTL
@@ -2064,7 +2436,7 @@
   specific value or range of values.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 TOS match support
 CONFIG_IP_NF_MATCH_TOS
@@ -2072,7 +2444,7 @@
   Service fields of the IP packet.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 Connection state match support
 CONFIG_IP_NF_MATCH_STATE
@@ -2081,23 +2453,23 @@
   is a powerful tool for packet classification.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
-Unclean match support (EXPERIMENTAL)
+Unclean match support
 CONFIG_IP_NF_MATCH_UNCLEAN
   Unclean packet matching matches any strange or invalid packets, by
   looking at a series of fields in the IP, TCP, UDP and ICMP headers.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
-Owner match support (EXPERIMENTAL)
+Owner match support
 CONFIG_IP_NF_MATCH_OWNER
   Packet owner matching allows you to match locally-generated packets
   based on who created them: the user, group, process or session.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 Packet filtering
 CONFIG_IP_NF_FILTER
@@ -2106,7 +2478,7 @@
   local output.  See the man page for iptables(8).
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 REJECT target support
 CONFIG_IP_NF_TARGET_REJECT
@@ -2115,24 +2487,24 @@
   than silently being dropped.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
-MIRROR target support (EXPERIMENTAL)
+MIRROR target support
 CONFIG_IP_NF_TARGET_MIRROR
   The MIRROR target allows a filtering rule to specify that an
   incoming packet should be bounced back to the sender.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
-Full NAT
+Full NAT (Network Address Translation)
 CONFIG_IP_NF_NAT
   The Full NAT option allows masquerading, port forwarding and other
   forms of full Network Address Port Translation.  It is controlled by
   the `nat' table in iptables: see the man page for iptables(8).
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 MASQUERADE target support
 CONFIG_IP_NF_TARGET_MASQUERADE
@@ -2143,21 +2515,21 @@
   address will be different on next dialup).
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 Basic SNMP-ALG support
 CONFIG_IP_NF_NAT_SNMP_BASIC
 
-  This module implements an Application Layer Gateway (ALG) for 
-  SNMP payloads.  In conjunction with NAT, it allows a network 
-  management system to access multiple private networks with 
-  conflicting addresses.  It works by modifying IP addresses 
+  This module implements an Application Layer Gateway (ALG) for
+  SNMP payloads.  In conjunction with NAT, it allows a network
+  management system to access multiple private networks with
+  conflicting addresses.  It works by modifying IP addresses
   inside SNMP payloads to match IP-layer NAT mapping.
-  
+
   This is the "basic" form of SNMP-ALG, as described in RFC 2962
-  
+
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 REDIRECT target support
 CONFIG_IP_NF_TARGET_REDIRECT
@@ -2167,7 +2539,7 @@
   useful for transparent proxies.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 Packet mangling
 CONFIG_IP_NF_MANGLE
@@ -2176,7 +2548,7 @@
   which can effect how the packet is routed.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 TOS target support
 CONFIG_IP_NF_TARGET_TOS
@@ -2185,19 +2557,19 @@
   packet prior to routing.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 MARK target support
 CONFIG_IP_NF_TARGET_MARK
   This option adds a `MARK' target, which allows you to create rules
   in the `mangle' table which alter the netfilter mark (nfmark) field
-  associated with the packet packet prior to routing. This can change
-  the routing method (see `IP: use netfilter MARK value as routing
+  associated with the packet prior to routing. This can change
+  the routing method (see `Use netfilter MARK value as routing
   key') and can also be used by other subsystems to change their
   behavior.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 TCPMSS target support
 CONFIG_IP_NF_TARGET_TCPMSS
@@ -2222,16 +2594,16 @@
 		 -j TCPMSS --clamp-mss-to-pmtu
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
-tcpmss match support
+TCPMSS match support
 CONFIG_IP_NF_MATCH_TCPMSS
   This option adds a `tcpmss' match, which allows you to examine the
   MSS value of TCP SYN packets, which control the maximum packet size
   for that connection.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 LOG target support
 CONFIG_IP_NF_TARGET_LOG
@@ -2239,7 +2611,7 @@
   any iptables table which records the packet header to the syslog.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 ipchains (2.2-style) support
 CONFIG_IP_NF_COMPAT_IPCHAINS
@@ -2250,7 +2622,7 @@
   the ipchains tool exactly as in 2.2 kernels.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 ipfwadm (2.0-style) support
 CONFIG_IP_NF_COMPAT_IPFWADM
@@ -2261,51 +2633,24 @@
   the ipfwadm tool exactly as in 2.0 kernels.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
-
-IP6 tables support (required for filtering/masq/NAT)
-CONFIG_IP6_NF_IPTABLES
-  ip6tables is a general, extensible packet identification framework.
-  Currently only the packet filtering and packet mangling subsystem
-  for IPv6 use this, but connection tracking is going to follow.
-  Say 'Y' or 'M' here if you want to use either of those.
-
-  If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
-
-IPv6 limit match support
-CONFIG_IP6_NF_MATCH_LIMIT
-  limit matching allows you to control the rate at which a rule can be
-  matched: mainly useful in combination with the LOG target ("LOG
-  target support", below) and to avoid some Denial of Service attacks.
-
-  If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 MAC address match support
 CONFIG_IP6_NF_MATCH_MAC
   mac matching allows you to match packets based on the source
-  ethernet address of the packet.
+  Ethernet address of the packet.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
-netfilter mark match support
+Netfilter MARK match support
 CONFIG_IP6_NF_MATCH_MARK
   Netfilter mark matching allows you to match packets based on the
   `nfmark' value in the packet.  This can be set by the MARK target
   (see below).
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
-
-LOG target support
-CONFIG_IP6_NF_TARGET_LOG
-  This option adds a `LOG' target, which allows you to create rules in
-  any ip6tables table which records the packet header to the syslog.
-
-  If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 Packet filtering
 CONFIG_IP6_NF_FILTER
@@ -2314,7 +2659,7 @@
   local output.  See the man page for iptables(8).
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 Packet mangling
 CONFIG_IP6_NF_MANGLE
@@ -2323,38 +2668,38 @@
   which can effect how the packet is routed.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 MARK target support
 CONFIG_IP6_NF_TARGET_MARK
   This option adds a `MARK' target, which allows you to create rules
   in the `mangle' table which alter the netfilter mark (nfmark) field
   associated with the packet packet prior to routing. This can change
-  the routing method (see `IP: use netfilter MARK value as routing
+  the routing method (see `Use netfilter MARK value as routing
   key') and can also be used by other subsystems to change their
   behavior.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 TCP Explicit Congestion Notification support
 CONFIG_INET_ECN
   Explicit Congestion Notification (ECN) allows routers to notify
   clients about network congestion, resulting in fewer dropped packets
-  and increased network performance. This option adds ECN support to the
-  Linux kernel, as well as a sysctl (/proc/sys/net/ipv4/tcp_ecn) which
-  allows ECN support to be disabled at runtime.
+  and increased network performance.  This option adds ECN support to
+  the Linux kernel, as well as a sysctl (/proc/sys/net/ipv4/tcp_ecn)
+  which allows ECN support to be disabled at runtime.
 
   Note that, on the Internet, there are many broken firewalls which
   refuse connections from ECN-enabled machines, and it may be a while
-  before these firewalls are fixed. Until then, to access a site behind
-  such a firewall (some of which are major sites, at the time of this
-  writing) you will have to disable this option, either by saying N now
-  or by using the sysctl.
+  before these firewalls are fixed.  Until then, to access a site
+  behind such a firewall (some of which are major sites, at the time
+  of this writing) you will have to disable this option, either by
+  saying N now or by using the sysctl.
 
   If in doubt, say N.
 
-IP6 tables support (required for filtering/masq/NAT)
+IPv6 tables support (required for filtering/masq/NAT)
 CONFIG_IP6_NF_IPTABLES
   ip6tables is a general, extensible packet identification framework.
   Currently only the packet filtering and packet mangling subsystem
@@ -2362,7 +2707,7 @@
   Say 'Y' or 'M' here if you want to use either of those.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 IPv6 limit match support
 CONFIG_IP6_NF_MATCH_LIMIT
@@ -2371,54 +2716,7 @@
   target support", below) and to avoid some Denial of Service attacks.
 
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
-
-MAC address match support
-CONFIG_IP6_NF_MATCH_MAC
-  mac matching allows you to match packets based on the source
-  ethernet address of the packet.
-
-  If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
-
-netfilter mark match support
-CONFIG_IP6_NF_MATCH_MARK
-  Netfilter mark matching allows you to match packets based on the
-  `nfmark' value in the packet.  This can be set by the MARK target
-  (see below).
-
-  If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
-
-Packet filtering
-CONFIG_IP6_NF_FILTER
-  Packet filtering defines a table `filter', which has a series of
-  rules for simple packet filtering at local input, forwarding and
-  local output.  See the man page for iptables(8).
-
-  If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
-
-Packet mangling
-CONFIG_IP6_NF_MANGLE
-  This option adds a `mangle' table to iptables: see the man page for
-  iptables(8).  This table is used for various packet alterations
-  which can effect how the packet is routed.
-
-  If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
-
-MARK target support
-CONFIG_IP6_NF_TARGET_MARK
-  This option adds a `MARK' target, which allows you to create rules
-  in the `mangle' table which alter the netfilter mark (nfmark) field
-  associated with the packet packet prior to routing. This can change
-  the routing method (see `IP: use netfilter MARK value as routing
-  key') and can also be used by other subsystems to change their
-  behavior.
-
-  If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.  If unsure, say `N'.
+  <file:Documentation/modules.txt>.  If unsure, say `N'.
 
 SYN flood protection
 CONFIG_SYN_COOKIES
@@ -2434,8 +2732,7 @@
   continue to connect, even when your machine is under attack. There
   is no need for the legitimate users to change their TCP/IP software;
   SYN cookies work transparently to them. For technical information
-  about SYN cookies, check out
-  ftp://koobera.math.uic.edu/syncookies.html .
+  about SYN cookies, check out <http://cr.yp.to/syncookies.html>.
 
   If you are SYN flooded, the source address reported by the kernel is
   likely to have been forged by the attacker; it is only reported as
@@ -2450,12 +2747,21 @@
   you can enable them by saying Y to "/proc file system support" and
   "Sysctl support" below and executing the command
 
-    echo 1 >/proc/sys/net/ipv4/tcp_syncookies 
+    echo 1 >/proc/sys/net/ipv4/tcp_syncookies
 
   at boot time after the /proc file system has been mounted.
-  
-  If unsure, say Y.
 
+  If unsure, say N.
+
+HCI EMU (virtual device) driver
+CONFIG_BLUEZ_HCIEMU
+  Bluetooth Virtual HCI device driver.
+  This driver is required if you want to use HCI Emulation software.
+
+  Say Y here to compile support for Virtual HCI devices into the
+  kernel or say M to compile it as module (hci_usb.o).
+
+# Choice: alphatype
 Alpha system type
 CONFIG_ALPHA_GENERIC
   This is the system type of your hardware.  A "generic" kernel will
@@ -2464,7 +2770,7 @@
 
   To find out what type of Alpha system you have, you may want to
   check out the Linux/Alpha FAQ, accessible on the WWW from
-  http://www.alphalinux.org . In summary:
+  <http://www.alphalinux.org>. In summary:
 
   Alcor/Alpha-XLT     AS 600
   Alpha-XL            XL-233, XL-266
@@ -2476,7 +2782,7 @@
   EB64+               EB64+ 21064 evaluation board
   EB66                EB66 21066 evaluation board
   EB66+               EB66+ 21066 evaluation board
-  Jensen              DECpc 150, DEC 2000 model 300, 
+  Jensen              DECpc 150, DEC 2000 model 300,
                       DEC 2000 model 500
   LX164               AlphaPC164-LX
   Miata               Personal Workstation 433a, 433au, 500a,
@@ -2496,21 +2802,160 @@
 
   If you don't know what to do, choose "generic".
 
-EV5 CPU daughtercard
+# Most of the information on these variants is from
+# <http://www.alphalinux.org/docs/alpha-howto.html>
+Alcor/Alpha-XLT
+CONFIG_ALPHA_ALCOR
+  For systems using the Digital ALCOR chipset: 5 chips (4, 64-bit data
+  slices (Data Switch, DSW) - 208-pin PQFP and 1 control (Control, I/O
+  Address, CIA) - a 383 pin plastic PGA).  It provides a DRAM
+  controller (256-bit memory bus) and a PCI interface.  It also does
+  all the work required to support an external Bcache and to maintain
+  memory coherence when a PCI device DMAs into (or out of) memory.
+
+Alpha-XL
+CONFIG_ALPHA_XL
+  XL-233 and XL-266-based Alpha systems.
+
+AlphaBook1
+CONFIG_ALPHA_BOOK1
+  Dec AlphaBook1/Burns Alpha-based laptops.
+
+Avanti
+CONFIG_ALPHA_AVANTI
+  Avanti AS 200, AS 205, AS 250, AS 255, AS 300, and AS 400-based
+  Alphas. Info at
+  <http://www.unix-ag.org/Linux-Alpha/Architectures/Avanti.html>.
+
+Cabriolet
+CONFIG_ALPHA_CABRIOLET
+  Cabriolet AlphaPC64, AlphaPCI64 systems.  Derived from EB64+ but now
+  baby-AT with Flash boot ROM, no on-board SCSI or Ethernet. 3 ISA
+  slots, 4 PCI slots (one pair are on a shared slot), uses plug-in
+  Bcache SIMMs.  Requires power supply with 3.3V output.
+
+DP264
+CONFIG_ALPHA_DP264
+  Various 21264 systems with the tsunami core logic chipset.
+  API Networks: 264DP, UP2000(+), CS20;
+  Compaq: DS10(E,L), XP900, XP1000, DS20(E), ES40.
+
+EB164
+CONFIG_ALPHA_EB164
+  EB164 21164 evaluation board from DEC.  Uses 21164 and ALCOR.  Has
+  ISA and PCI expansion (3 ISA slots, 2 64-bit PCI slots (one is
+  shared with an ISA slot) and 2 32-bit PCI slots.  Uses plus-in
+  Bcache SIMMs. I/O sub-system provides SuperI/O (2S, 1P, FD), KBD,
+  MOUSE (PS2 style), RTC/NVRAM.  Boot ROM is Flash.  PC-AT-sized
+  motherboard.  Requires power supply with 3.3V output.
+
+EB64+
+CONFIG_ALPHA_EB64P
+  Uses 21064 or 21064A and APECs.  Has ISA and PCI expansion (3 ISA,
+  2 PCI, one pair are on a shared slot). Supports 36-bit DRAM SIMs.
+  ISA bus generated by Intel SaturnI/O PCI-ISA bridge. On-board SCSI
+  (NCR 810 on PCI) Ethernet (Digital 21040), KBD, MOUSE (PS2 style),
+  SuperI/O (2S, 1P, FD), RTC/NVRAM. Boot ROM is EPROM.  PC-AT size.
+  Runs from standard PC power supply.
+
+EB66
+CONFIG_ALPHA_EB66
+  A Digital DS group board.  Uses 21066 or 21066A.  I/O sub-system is
+  identical to EB64+.  Baby PC-AT size.  Runs from standard PC power
+  supply.  The EB66 schematic was published as a marketing poster
+  advertising the 21066 as "the first microprocessor in the world with
+  embedded PCI".
+
+EB66+
+CONFIG_ALPHA_EB66P
+  Later variant of the EB66 board.
+
+Eiger
+CONFIG_ALPHA_EIGER
+  Apparently an obscure OEM single-board computer based on the
+  Typhoon/Tsunami chipset family. Information on it is scanty.
+
+Jensen
+CONFIG_ALPHA_JENSEN
+  DEC PC 150 AXP (aka Jensen): This is a very old Digital system - one
+  of the first-generation Alpha systems. A number of these systems
+  seem to be available on the second- hand market. The Jensen is a
+  floor-standing tower system which originally used a 150MHz 21064 It
+  used programmable logic to interface a 486 EISA I/O bridge to the
+  CPU.
+
+LX164
+CONFIG_ALPHA_LX164
+  A technical overview of this board is available at
+  <http://www.unix-ag.org/Linux-Alpha/Architectures/LX164.html>.
+
+Miata
+CONFIG_ALPHA_MIATA
+  The Digital PersonalWorkStation (PWS 433a, 433au, 500a, 500au, 600a,
+  or 600au).  There is an Installation HOWTO for this hardware at
+  <http://members.brabant.chello.nl/~s.vandereijk/miata.html>.
+
+Mikasa
+CONFIG_ALPHA_MIKASA
+  AlphaServer 1000-based Alpha systems.
+
+Nautilus
+CONFIG_ALPHA_NAUTILUS
+  Alpha systems based on the AMD 751 & ALI 1543C chipsets.
+
+Noname
+CONFIG_ALPHA_NONAME
+  The AXPpci33 (aka NoName), is based on the EB66 (includes the Multia
+  UDB).  This design was produced by Digital's Technical OEM (TOEM)
+  group. It uses the 21066 processor running at 166MHz or 233MHz. It
+  is a baby-AT size, and runs from a standard PC power supply. It has
+  5 ISA slots and 3 PCI slots (one pair are a shared slot). There are
+  2 versions, with either PS/2 or large DIN connectors for the
+  keyboard.
+
+Noritake
+CONFIG_ALPHA_NORITAKE
+  AlphaServer 1000A, AlphaServer 600A, and AlphaServer 800-based
+  systems.
+
+Rawhide
+CONFIG_ALPHA_RAWHIDE
+  AlphaServer 1200, AlphaServer 4000 and AlphaServer 4100 machines.
+  See HOWTO at
+  <http://www.alphalinux.org/docs/rawhide/4100_install.shtml>.
+
+Ruffian
+CONFIG_ALPHA_RUFFIAN
+  Samsung APC164UX.  There is a page on known problems and workarounds
+  at <http://www.alphalinux.org/faq/FAQ-11.html>.
+
+Sable
+CONFIG_ALPHA_SABLE
+  Digital AlphaServer 2000 and 2100-based systems.
+
+Takara
+CONFIG_ALPHA_TAKARA
+  Alpha 11164-based OEM single-board computer.
+
+Wildfire
+CONFIG_ALPHA_WILDFIRE
+  AlphaServer GS 40/80/160/320 SMP based on the EV67 core.
+
+EV5 CPU daughtercard (model 5/xxx)
 CONFIG_ALPHA_PRIMO
   Say Y if you have an AS 1000 5/xxx or an AS 1000A 5/xxx.
 
-EV5 CPU(s)
+EV5 CPU(s) (model 5/xxx)
 CONFIG_ALPHA_GAMMA
   Say Y if you have an AS 2000 5/xxx or an AS 2100 5/xxx.
 
-Using SRM as bootloader
+Use SRM as bootloader
 CONFIG_ALPHA_SRM
   There are two different types of booting firmware on Alphas: SRM,
   which is command line driven, and ARC, which uses menus and arrow
   keys. Details about the Linux/Alpha booting process are contained in
   the Linux/Alpha FAQ, accessible on the WWW from
-  http://www.alphalinux.org .
+  <http://www.alphalinux.org>.
 
   The usual way to load Linux on an Alpha machine is to use MILO
   (a bootloader that lets you pass command line parameters to the
@@ -2521,7 +2966,7 @@
   here. If MILO doesn't work on your system (true for Jensen
   motherboards), you can bypass it altogether and boot Linux directly
   from an SRM console; say Y here in order to do that. Note that you
-  won't be able to boot from an IDE disk using SRM. 
+  won't be able to boot from an IDE disk using SRM.
 
   If unsure, say N.
 
@@ -2530,20 +2975,20 @@
   The 2.4 kernel changed the kernel start address from 0x310000
   to 0x810000 to make room for the Wildfire's larger SRM console.
 
-  If you're using aboot 0.7 or later, the bootloader will examine
-  the ELF headers to determine where to transfer control.  Unfortunately,
-  most older bootloaders -- APB or MILO -- hardcoded the kernel
-  start address rather than examining the ELF headers, and the result
-  is a hard lockup.
+  If you're using aboot 0.7 or later, the bootloader will examine the
+  ELF headers to determine where to transfer control. Unfortunately,
+  most older bootloaders -- APB or MILO -- hardcoded the kernel start
+  address rather than examining the ELF headers, and the result is a
+  hard lockup.
 
-  Say Y if you have a broken bootloader.  Say N if you do not, or
-  if you wish to run on Wildfire.
+  Say Y if you have a broken bootloader.  Say N if you do not, or if
+  you wish to run on Wildfire.
 
 Large VMALLOC support
 CONFIG_ALPHA_LARGE_VMALLOC
-  Process creation and other aspects of virtual memory management
-  can be streamlined if we restrict the kernel to one PGD for all
-  vmalloc allocations.  This equates to about 8GB.
+  Process creation and other aspects of virtual memory management can
+  be streamlined if we restrict the kernel to one PGD for all vmalloc
+  allocations.  This equates to about 8GB.
 
   Under normal circumstances, this is so far and above what is needed
   as to be laughable.  However, there are certain applications (such
@@ -2559,11 +3004,11 @@
   This includes intelligent serial boards such as Cyclades,
   Digiboards, etc. These are usually used for systems that need many
   serial ports because they serve many terminals or dial-in
-  connections. 
+  connections.
 
   Note that the answer to this question won't directly affect the
-  kernel: saying N will just cause this configure script to skip all
-  the questions about non-standard serial boards. 
+  kernel: saying N will just cause the configurator to skip all
+  the questions about non-standard serial boards.
 
   Most people can say N here.
 
@@ -2572,10 +3017,10 @@
   If you wish to use any non-standard features of the standard "dumb"
   driver, say Y here. This includes HUB6 support, shared serial
   interrupts, special multiport support, support for more than the
-  four COM 1/2/3/4 boards, etc. 
+  four COM 1/2/3/4 boards, etc.
 
   Note that the answer to this question won't directly affect the
-  kernel: saying N will just cause this configure script to skip all
+  kernel: saying N will just cause the configurator to skip all
   the questions about serial driver options. If unsure, say N.
 
 Support more than 4 serial ports
@@ -2583,22 +3028,30 @@
   Say Y here if you have dumb serial boards other than the four
   standard COM 1/2/3/4 ports. This may happen if you have an AST
   FourPort, Accent Async, Boca (read the Boca mini-HOWTO, available
-  from http://www.linuxdoc.org/docs.html#howto ), or other custom
+  from <http://www.linuxdoc.org/docs.html#howto>), or other custom
   serial port hardware which acts similar to standard serial port
   hardware. If you only use the standard COM 1/2/3/4 ports, you can
   say N here to save some memory. You can also say Y if you have an
   "intelligent" multiport card such as Cyclades, Digiboards, etc.
 
+Support for serial ports defined by ACPI tables
+CONFIG_SERIAL_ACPI
+  Legacy free machines may not have serial ports at the legacy COM1, 
+  COM2 etc addresses. Serial ports on such machines are described by
+  the ACPI tables SPCR (Serial Port Console Redirection) table and 
+  DBGP (Debug Port) table. Say Y here if you want to include support
+  for these serial ports.
+
 Support for sharing serial interrupts
 CONFIG_SERIAL_SHARE_IRQ
   Some serial boards have hardware support which allows multiple dumb
   serial ports on the same board to share a single IRQ. To enable
   support for this in the serial driver, say Y here.
 
-Auto detect IRQ on standard ports (unsafe)
+Auto-detect IRQ on standard ports (unsafe)
 CONFIG_SERIAL_DETECT_IRQ
   Say Y here if you want the kernel to try to guess which IRQ
-  to use for your serial port. 
+  to use for your serial port.
 
   This is considered unsafe; it is far better to configure the IRQ in
   a boot script using the setserial command.
@@ -2612,16 +3065,12 @@
   servicing. Say Y here to enable the serial driver to take advantage
   of those special I/O ports.
 
-SGI PROM Console Support
-CONFIG_ARC_CONSOLE
-  Say Y here if you want to use the PROMs for console I/O.
-
 SGI Zilog85C30 serial support
 CONFIG_SGI_SERIAL
   If you want to use your SGI's built-in serial ports under Linux,
   answer Y.
 
-SGI Newport Graphics support (EXPERIMENTAL)
+SGI Newport Graphics support
 CONFIG_SGI_NEWPORT_GFX
   If you have an SGI machine and you want to compile the graphics
   drivers, say Y here. This will include the code for the
@@ -2651,14 +3100,14 @@
 CONFIG_PCMCIA_SERIAL_CS
   Say Y here to enable support for 16-bit PCMCIA serial devices,
   including serial port cards, modems, and the modem functions of
-  multi-function ethernet/modem cards. (PCMCIA- or PC-cards are
+  multi-function Ethernet/modem cards. (PCMCIA- or PC-cards are
   credit-card size devices often used with laptops.)
 
   This driver is also available as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want).
-  The module will be called serial_cs.o. If you want to compile it as
-  a module, say M here and read Documentation/modules.txt. If unsure,
-  say N.
+  The module will be called serial_cs.o.  If you want to compile it as
+  a module, say M here and read <file:Documentation/modules.txt>.
+  If unsure, say N.
 
 ACP Modem (Mwave) support
 CONFIG_MWAVE
@@ -2685,17 +3134,14 @@
   The module will be called mwave.o. If you want to compile it as
   a module, say M here and read Documentation/modules.txt.
 
-/dev/agpgart (AGP Support) (EXPERIMENTAL)
+/dev/agpgart (AGP Support)
 CONFIG_AGP
   AGP (Accelerated Graphics Port) is a bus system mainly used to
-  connect graphics cards to the rest of the system. 
+  connect graphics cards to the rest of the system.
 
   If you have an AGP system and you say Y here, it will be possible to
   use the AGP features of your 3D rendering video card. This code acts
-  as a sort of "AGP driver" for the motherboard's chipset. The glx
-  module will then be able to program the GART (graphics aperture
-  relocation table) registers with appropriate values to transfer
-  commands to the card.
+  as a sort of "AGP driver" for the motherboard's chipset.
 
   If you need more texture memory than you can get with the AGP GART
   (theoretically up to 256 MB, but in practice usually 64 or 128 MB
@@ -2706,47 +3152,42 @@
   write-combining with MTRR support on the AGP bus. Without it, OpenGL
   direct rendering will be a lot slower but still faster than PIO.
 
-  For the moment, you should probably say N, unless you want to test
-  the GLX component for XFree86 3.3.6, which can be downloaded from
-  http://utah-glx.sourceforge.net/ , or need to use the 810 Xserver in
-  XFree 3.3.6.
-
-  This driver is available as a module. If you want to compile it as a
-  module, say M here and read Documentation/modules.txt. The module
-  will be called agpgart.o.
+  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
+  use GLX or DRI.  If unsure, say N.
+
+  This driver is available as a module.  If you want to compile it as
+  a module, say M here and read <file:Documentation/modules.txt>.  The
+  module will be called agpgart.o.
 
-Intel 440LX/BX/GX/815/830M/840/850 support
+Intel 440LX/BX/GX/815/820/830/840/845/850/860 support
 CONFIG_AGP_INTEL
   This option gives you AGP support for the GLX component of the
-  XFree86 4.x on Intel 440LX/BX/GX, 815, 830M, 840 and 850 chipsets.
+  XFree86 4.x on Intel 440LX/BX/GX, 815, 820, 830, 840, 845, 850 and 860 chipsets.
 
-  For the moment, you should probably say N, unless you want to test
-  the GLX component for XFree86 3.3.6, which can be downloaded from
-  http://utah-glx.sourceforge.net/ .
+  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
+  use GLX or DRI.  If unsure, say N.
 
-Intel I810/I810 DC100/I810e support
+Intel I810/I815 DC100/I810e support
 CONFIG_AGP_I810
-  This option gives you AGP support for the Xserver on the Intel 810,
-  830M and 815 chipset boards for their on-board integrated graphics.
-  This is required to do any useful video modes with these boards.
+  This option gives you AGP support for the Xserver on the Intel 810
+  815 and 830m chipset boards for their on-board integrated graphics. This
+  is required to do any useful video modes with these boards.
 
 VIA chipset support
 CONFIG_AGP_VIA
   This option gives you AGP support for the GLX component of the
   XFree86 4.x on VIA MPV3/Apollo Pro chipsets.
 
-  For the moment, you should probably say N, unless you want to test
-  the GLX component for XFree86 3.3.6, which can be downloaded from
-  http://utah-glx.sourceforge.net/ .
+  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
+  use GLX or DRI.  If unsure, say N.
 
 AMD Irongate, 761, and 762 support
 CONFIG_AGP_AMD
   This option gives you AGP support for the GLX component of the
   XFree86 4.x on AMD Irongate, 761, and 762 chipsets.
 
-  For the moment, you should probably say N, unless you want to test
-  the GLX component for XFree86 3.3.6, which can be downloaded from
-  http://utah-glx.sourceforge.net/ .
+  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
+  use GLX or DRI.  If unsure, say N.
 
 Generic SiS support
 CONFIG_AGP_SIS
@@ -2756,33 +3197,47 @@
 
   Note that 5591/5592 AGP chipsets are NOT supported.
 
-  For the moment, you should probably say N, unless you want to test
-  the GLX component for XFree86 3.3.6, which can be downloaded from
-  http://utah-glx.sourceforge.net/ .
+  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
+  use GLX or DRI.  If unsure, say N.
 
-ALI M1541 support
+Serverworks LE/HE support
+CONFIG_AGP_SWORKS
+  Say Y here to support the Serverworks AGP card.  See 
+  <http://www.serverworks.com/> for product descriptions and images.
+
+ALI chipset support
 CONFIG_AGP_ALI
   This option gives you AGP support for the GLX component of the
-  XFree86 4.x on the ALi M1541 chipset.
+  XFree86 4.x on the following ALi chipsets.  The supported chipsets
+  include M1541, M1621, M1631, M1632, M1641,M1647,and M1651.
+  For the ALi-chipset question, ALi suggests you refer to
+  <http://www.ali.com.tw/eng/support/index.shtml>.
 
-  This chipset can do AGP 1x and 2x, but note that there is an
+  The M1541 chipset can do AGP 1x and 2x, but note that there is an
   acknowledged incompatibility with Matrox G200 cards. Due to
   timing issues, this chipset cannot do AGP 2x with the G200.
   This is a hardware limitation. AGP 1x seems to be fine, though.
 
-  For the moment, you should probably say N, unless you want to test
-  the GLX component for XFree86 3.3.6, which can be downloaded from
-  http://utah-glx.sourceforge.net/ .
+  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
+  use GLX or DRI.  If unsure, say N.
 
-PCI support
+Support for ISA-bus hardware
+CONFIG_ISA
+  Find out whether you have ISA slots on your motherboard.  ISA is the
+  name of a bus system, i.e. the way the CPU talks to the other stuff
+  inside your box.  Other bus systems are PCI, EISA, MicroChannel
+  (MCA) or VESA.  ISA is an older system, now being displaced by PCI;
+  newer boards don't support it.  If you have ISA, say Y, otherwise N.
+
+Support for PCI bus hardware
 CONFIG_PCI
   Find out whether you have a PCI motherboard. PCI is the name of a
   bus system, i.e. the way the CPU talks to the other stuff inside
-  your box. Other bus systems are ISA, EISA, Microchannel (MCA) or
-  VESA. If you have PCI, say Y, otherwise N. 
+  your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
+  VESA. If you have PCI, say Y, otherwise N.
 
   The PCI-HOWTO, available from
-  http://www.linuxdoc.org/docs.html#howto , contains valuable
+  <http://www.linuxdoc.org/docs.html#howto>, contains valuable
   information about which PCI hardware does work under Linux and which
   doesn't.
 
@@ -2790,11 +3245,11 @@
 CONFIG_PCI_INTEGRATOR
   Find out whether you have a PCI motherboard. PCI is the name of a
   bus system, i.e. the way the CPU talks to the other stuff inside
-  your box. Other bus systems are ISA, EISA, Microchannel (MCA) or
-  VESA. If you have PCI, say Y, otherwise N. 
+  your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
+  VESA. If you have PCI, say Y, otherwise N.
 
   The PCI-HOWTO, available from
-  http://www.linuxdoc.org/docs.html#howto , contains valuable
+  <http://www.linuxdoc.org/docs.html#howto>, contains valuable
   information about which PCI hardware does work under Linux and which
   doesn't.
 
@@ -2802,14 +3257,15 @@
 CONFIG_PCI_QSPAN
   Find out whether you have a PCI motherboard. PCI is the name of a
   bus system, i.e. the way the CPU talks to the other stuff inside
-  your box. Other bus systems are ISA, EISA, Microchannel (MCA) or
-  VESA. If you have PCI, say Y, otherwise N. 
+  your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
+  VESA. If you have PCI, say Y, otherwise N.
 
   The PCI-HOWTO, available from
-  http://www.linuxdoc.org/docs.html#howto , contains valuable
+  <http://www.linuxdoc.org/docs.html#howto>, contains valuable
   information about which PCI hardware does work under Linux and which
   doesn't.
 
+# Choice: pci_access
 PCI access mode
 CONFIG_PCI_GOBIOS
   On PCI systems, the BIOS can be used to detect the PCI devices and
@@ -2838,22 +3294,56 @@
 
   When in doubt, say Y.
 
+PCI Hotplug support
+CONFIG_HOTPLUG_PCI
+  Say Y here if you have a motherboard with a PCI Hotplug controller.
+  This allows you to add and remove PCI cards while the machine is
+  powered up and running.  The file system pcihpfs must be mounted
+  in order to interact with any PCI Hotplug controllers.
+
+  This code is also available as a module ( = code which can be
+  inserted in and removed from the running kernel whenever you want).
+  The module will be called pci_hotplug.o. If you want to compile it
+  as a module, say M here and read <file:Documentation/modules.txt>.
+
+  When in doubt, say N.
+
+PCI Compaq Hotplug controller
+CONFIG_HOTPLUG_PCI_COMPAQ
+  Say Y here if you have a motherboard with a Compaq PCI Hotplug
+  controller.
+
+  This code is also available as a module ( = code which can be
+  inserted in and removed from the running kernel whenever you want).
+  The module will be called cpqphp.o. If you want to compile it
+  as a module, say M here and read <file:Documentation/modules.txt>.
+
+  When in doubt, say N.
+
+PCI Compaq Hotplug controller NVRAM support
+CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM
+  Say Y here if you have a Compaq server that has a PCI Hotplug
+  controller.  This will allow the PCI Hotplug driver to store the PCI
+  system configuration options in NVRAM.
+
+  When in doubt, say N.
+
 MCA support
 CONFIG_MCA
   MicroChannel Architecture is found in some IBM PS/2 machines and
-  laptops. It is a bus system similar to PCI or ISA. See
-  Documentation/mca.txt (and especially the web page given there)
-  before attempting to build an MCA bus kernel.
+  laptops.  It is a bus system similar to PCI or ISA. See
+  <file:Documentation/mca.txt> (and especially the web page given
+  there) before attempting to build an MCA bus kernel.
 
-EISA support
+Support for EISA-bus hardware
 CONFIG_EISA
   The Extended Industry Standard Architecture (EISA) bus was
   developed as an open alternative to the IBM MicroChannel bus.
 
   The EISA bus provided some of the features of the IBM MicroChannel
   bus while maintaining backward compatibility with cards made for
-  the older ISA bus. The EISA bus saw limited use between 1988 and 1995
-  when it was made obsolete by the PCI bus.
+  the older ISA bus.  The EISA bus saw limited use between 1988 and
+  1995 when it was made obsolete by the PCI bus.
 
   Say Y here if you are building a kernel for an EISA-based machine.
 
@@ -2866,7 +3356,7 @@
   Say Y here to create a kernel to run on the SGI 320 or 540.
   A kernel compiled for the Visual Workstation will not run on other
   PC boards and vice versa.
-  See Documentation/sgi-visws.txt for more.
+  See <file:Documentation/sgi-visws.txt> for more.
 
 SGI Visual Workstation framebuffer support
 CONFIG_FB_SGIVW
@@ -2891,8 +3381,8 @@
   This support is also available as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want).
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt. You will get modules called i2o_core.o
-  and i2o_config.o. 
+  <file:Documentation/modules.txt>.  You will get modules called
+  i2o_core.o and i2o_config.o.
 
   If unsure, say N.
 
@@ -2904,7 +3394,7 @@
   This support is also available as a module called i2o_pci.o ( = code
   which can be inserted in and removed from the running kernel
   whenever you want). If you want to compile it as a module, say M
-  here and read Documentation/modules.txt.
+  here and read <file:Documentation/modules.txt>.
 
 I2O Block OSM
 CONFIG_I2O_BLOCK
@@ -2914,7 +3404,7 @@
   This support is also available as a module called i2o_block.o ( =
   code which can be inserted in and removed from the running kernel
   whenever you want). If you want to compile it as a module, say M
-  here and read Documentation/modules.txt.
+  here and read <file:Documentation/modules.txt>.
 
 I2O LAN OSM
 CONFIG_I2O_LAN
@@ -2925,7 +3415,7 @@
   This support is also available as a module called i2o_lan.o ( = code
   which can be inserted in and removed from the running kernel
   whenever you want). If you want to compile it as a module, say M
-  here and read Documentation/modules.txt.
+  here and read <file:Documentation/modules.txt>.
 
 I2O SCSI OSM
 CONFIG_I2O_SCSI
@@ -2936,7 +3426,7 @@
   This support is also available as a module called i2o_scsi.o ( =
   code which can be inserted in and removed from the running kernel
   whenever you want). If you want to compile it as a module, say M
-  here and read Documentation/modules.txt.
+  here and read <file:Documentation/modules.txt>.
 
 I2O /proc support
 CONFIG_I2O_PROC
@@ -2947,7 +3437,7 @@
   This support is also available as a module called i2o_proc.o ( =
   code which can be inserted in and removed from the running kernel
   whenever you want). If you want to compile it as a module, say M
-  here and read Documentation/modules.txt.
+  here and read <file:Documentation/modules.txt>.
 
 Plug and Play support
 CONFIG_PNP
@@ -2959,24 +3449,41 @@
 
   Say Y here if you would like Linux to configure your Plug and Play
   devices. You should then also say Y to "ISA Plug and Play support",
-  below. Alternatively, you can say N here and configure your PnP 
+  below. Alternatively, you can say N here and configure your PnP
   devices using the user space utilities contained in the isapnptools
   package.
-  
+
   This support is also available as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want).
   If you want to compile it as a module, say M here and read
-  Documentation/modules.txt.
+  <file:Documentation/modules.txt>.
 
 ISA Plug and Play support
 CONFIG_ISAPNP
   Say Y here if you would like support for ISA Plug and Play devices.
-  Some information is in Documentation/isapnp.txt.
- 
+  Some information is in <file:Documentation/isapnp.txt>.
+
   This support is also available as a module called isapnp.o ( =
   code which can be inserted in and removed from the running kernel
   whenever you want). If you want to compile it as a module, say M
-  here and read Documentation/modules.txt.
+  here and read <file:Documentation/modules.txt>.
+
+  If unsure, say Y.
+
+PNPBIOS support
+CONFIG_PNPBIOS
+  Linux uses the PNPBIOS as defined in "Plug and Play BIOS
+  Specification Version 1.0A May 5, 1994" to autodetect built-in
+  mainboard resources (e.g. parallel port resources).
+
+  Other features (e.g. change resources, ESCD, event notification,
+  Docking station information, ISAPNP services) are not used.
+
+  Note: ACPI is expected to supersede PNPBIOS some day, currently it
+  co-exists nicely.
+
+  See latest pcmcia-cs (stand-alone package) for a nice "lspnp" tools,
+  or have a look at /proc/bus/pnp.
 
   If unsure, say Y.
 
@@ -2992,50 +3499,55 @@
   example, used on modern desktops as well as laptops, is USB.
 
   Enable HOTPLUG and KMOD, and build a modular kernel.  Get agent
-  software (at http://linux-hotplug.sourceforge.net) and install it.
+  software (at <http://linux-hotplug.sourceforge.net>) and install it.
   Then your kernel will automatically call out to a user mode "policy
   agent" (/sbin/hotplug) to load modules and set up software needed
   to use devices as you hotplug them.
 
-PCMCIA/Cardbus support
+PCMCIA/CardBus support
 CONFIG_PCMCIA
   Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
-  computer. These are credit-card size devices such as network cards,
-  modems or hard drives often used with laptops computers. There are
+  computer.  These are credit-card size devices such as network cards,
+  modems or hard drives often used with laptops computers.  There are
   actually two varieties of these cards: the older 16 bit PCMCIA cards
-  and the newer 32 bit CardBus cards. If you want to use CardBus
+  and the newer 32 bit CardBus cards.  If you want to use CardBus
   cards, you need to say Y here and also to "CardBus support" below.
 
-  To use your PC-cards, you will need supporting software from David 
-  Hinds' pcmcia-cs package (see the file Documentation/Changes for 
-  location). Please also read the PCMCIA-HOWTO, available from
-  http://www.linuxdoc.org/docs.html#howto
+  To use your PC-cards, you will need supporting software from David
+  Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
+  for location).  Please also read the PCMCIA-HOWTO, available from
+  <http://www.linuxdoc.org/docs.html#howto>.
 
   This driver is also available as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want).
   When compiled this way, there will be modules called pcmcia_core.o
   and ds.o.  If you want to compile it as a module, say M here and
-  read Documentation/modules.txt.
+  read <file:Documentation/modules.txt>.
 
-CardBus support
+CardBus card and (Yenta) bridge support
 CONFIG_CARDBUS
-  CardBus is a bus mastering architecture for PC-cards, which allows 
-  for 32 bit PC-cards (the original PCMCIA standard specifies only 
+  CardBus is a bus mastering architecture for PC-cards, which allows
+  for 32 bit PC-cards (the original PCMCIA standard specifies only
   a 16 bit wide bus). Many newer PC-cards are actually CardBus cards.
 
-  To use your PC-cards, you will need supporting software from David 
-  Hinds' pcmcia-cs package (see the file Documentation/Changes for 
-  location).
+  This option enables support for CardBus PC Cards, as well as support
+  for CardBus host bridges.  Virtually all modern PCMCIA bridges are
+  CardBus compatible.  A "bridge" is the hardware inside your computer
+  that PCMCIA cards are plugged into.
+
+  To use your PC-cards, you will need supporting software from David
+  Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
+  for location).
 
   If unsure, say Y.
 
-i82365/Yenta compatible bridge support
+i82365 compatible host bridge support
 CONFIG_I82365
-  Say Y here to include support for PCMCIA and CardBus host bridges
-  that are register compatible with the Intel i82365 and/or the Yenta
-  specification: this includes virtually all modern PCMCIA bridges.
-  "Bridge" is the name used for the hardware inside your computer that
-  PCMCIA cards are plugged into. If unsure, say Y.
+  Say Y here to include support for ISA-bus PCMCIA host bridges that
+  are register compatible with the Intel i82365.  These are found on
+  older laptops and ISA-bus card readers for desktop systems.  A
+  "bridge" is the hardware inside your computer that PCMCIA cards are
+  plugged into. If unsure, say N.
 
 Databook TCIC host bridge support
 CONFIG_TCIC
@@ -3052,60 +3564,67 @@
   and some programs won't run unless you say Y here. In particular, if
   you want to run the DOS emulator dosemu under Linux (read the
   DOSEMU-HOWTO, available from
-  http://www.linuxdoc.org/docs.html#howto ), you'll need to say Y
+  <http://www.linuxdoc.org/docs.html#howto>), you'll need to say Y
   here.
-  
+
   You can find documentation about IPC with "info ipc" and also in
   section 6.4 of the Linux Programmer's Guide, available from
-  http://www.linuxdoc.org/docs.html#guide .
+  <http://www.linuxdoc.org/docs.html#guide>.
 
 BSD Process Accounting
 CONFIG_BSD_PROCESS_ACCT
   If you say Y here, a user level program will be able to instruct the
   kernel (via a special system call) to write process accounting
   information to a file: whenever a process exits, information about
-  that process will be appended to the file by the kernel. The
+  that process will be appended to the file by the kernel.  The
   information includes things such as creation time, owning user,
   command name, memory usage, controlling terminal etc. (the complete
-  list is in the struct acct in include/linux/acct.h). It is up to the
-  user level program to do useful things with this information. This
-  is generally a good idea, so say Y.
-  
+  list is in the struct acct in <file:include/linux/acct.h>).  It is
+  up to the user level program to do useful things with this
+  information.  This is generally a good idea, so say Y.
+
 Sysctl support
 CONFIG_SYSCTL
   The sysctl interface provides a means of dynamically changing
   certain kernel parameters and variables on the fly without requiring
-  a recompile of the kernel or reboot of the system. The primary
+  a recompile of the kernel or reboot of the system.  The primary
   interface consists of a system call, but if you say Y to "/proc
   file system support", a tree of modifiable sysctl entries will be
   generated beneath the /proc/sys directory. They are explained in the
-  files in Documentation/sysctl/. Note that enabling this option will
-  enlarge the kernel by at least 8 KB.
+  files in <file:Documentation/sysctl/>.  Note that enabling this
+  option will enlarge the kernel by at least 8 KB.
 
   As it is generally a good thing, you should say Y here unless
   building a kernel for install/rescue disks or your system is very
   limited in memory.
 
+# Choice: kcore
 Kernel core (/proc/kcore) format
 CONFIG_KCORE_ELF
-  If you enabled support for /proc file system then the file 
-  /proc/kcore will contain the kernel core image. This can be used 
+  If you enabled support for /proc file system then the file
+  /proc/kcore will contain the kernel core image. This can be used
   in gdb:
 
   $ cd /usr/src/linux ; gdb vmlinux /proc/kcore
 
-  You have two choices here: ELF and A.OUT. Selecting ELF will make 
+  You have two choices here: ELF and A.OUT. Selecting ELF will make
   /proc/kcore appear in ELF core format as defined by the Executable
   and Linking Format specification. Selecting A.OUT will choose the
   old "a.out" format which may be necessary for some old versions
   of binutils or on some architectures.
 
-  This is especially useful if you have compiled the kernel with the 
-  "-g" option to preserve debugging information. It is mainly used 
-  for examining kernel data structures on the live kernel so if you 
-  don't understand what this means or are not a kernel hacker, just 
+  This is especially useful if you have compiled the kernel with the
+  "-g" option to preserve debugging information. It is mainly used
+  for examining kernel data structures on the live kernel so if you
+  don't understand what this means or are not a kernel hacker, just
   leave it at its default value ELF.
 
+# Choice: kcore
+Select a.out format for /proc/kcore
+CONFIG_KCORE_AOUT
+  Not necessary unless you're using a very out-of-date binutils
+  version.  You probably want KCORE_ELF.
+
 Kernel support for ELF binaries
 CONFIG_BINFMT_ELF
   ELF (Executable and Linkable Format) is a format for libraries and
@@ -3120,21 +3639,21 @@
   want to say Y here.
 
   Information about ELF is contained in the ELF HOWTO available from
-  http://www.linuxdoc.org/docs.html#howto .
+  <http://www.linuxdoc.org/docs.html#howto>.
 
   If you find that after upgrading from Linux kernel 1.2 and saying Y
   here, you still can't run any ELF binaries (they just crash), then
   you'll have to install the newest ELF runtime libraries, including
-  ld.so (check the file Documentation/Changes for location and latest
-  version).
+  ld.so (check the file <file:Documentation/Changes> for location and
+  latest version).
 
   If you want to compile this as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt. The module will be
-  called binfmt_elf.o. Saying M or N here is dangerous because some
-  crucial programs on your system might be in ELF format.
+  say M here and read <file:Documentation/modules.txt>.  The module
+  will be called binfmt_elf.o. Saying M or N here is dangerous because
+  some crucial programs on your system might be in ELF format.
 
-Kernel support for A.OUT binaries
+Kernel support for a.out binaries
 CONFIG_BINFMT_AOUT
   A.out (Assembler.OUTput) is a set of formats for libraries and
   executables used in the earliest versions of UNIX. Linux used the
@@ -3162,12 +3681,17 @@
   this to work, you need to have the emulator /usr/bin/em86 in place.
 
   You can get the same functionality by saying N here and saying Y to
-  "Kernel support for MISC binaries". 
+  "Kernel support for MISC binaries".
 
   You may answer M to compile the emulation support as a module and
   later load the module when you want to use a Linux/Intel binary. The
   module will be called binfmt_em86.o. If unsure, say Y.
 
+Kernel support for SOM binaries
+CONFIG_BINFMT_SOM
+  SOM is a binary executable format inherited from HP/UX.  Say Y here
+  to be able to load and execute SOM binaries directly.
+
 Kernel support for MISC binaries
 CONFIG_BINFMT_MISC
   If you say Y here, it will be possible to plug wrapper-driven binary
@@ -3175,15 +3699,15 @@
   programs that need an interpreter to run like Java, Python or
   Emacs-Lisp. It's also useful if you often run DOS executables under
   the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
-  http://www.linuxdoc.org/docs.html#howto ). Once you have
+  <http://www.linuxdoc.org/docs.html#howto>). Once you have
   registered such a binary class with the kernel, you can start one of
   those programs simply by typing in its name at a shell prompt; Linux
   will automatically feed it to the correct interpreter.
 
   You can do other nice things, too. Read the file
-  Documentation/binfmt_misc.txt to learn how to use this feature, and
-  Documentation/java.txt for information about how to include Java
-  support.
+  <file:Documentation/binfmt_misc.txt> to learn how to use this
+  feature, and <file:Documentation/java.txt> for information about how
+  to include Java support.
 
   You must say Y to "/proc file system support" (CONFIG_PROC_FS) to
   use this part of the kernel.
@@ -3192,16 +3716,33 @@
   you have use for it; the module is called binfmt_misc.o. If you
   don't know what to answer at this point, say Y.
 
-Solaris binary emulation (EXPERIMENTAL)
+Kernel support for JAVA binaries
+CONFIG_BINFMT_JAVA
+  If you say Y here, the kernel will load and execute Java J-code
+  binaries directly.  Note: this option is obsolete and scheduled for
+  removal, use CONFIG_BINFMT_MISC instead.
+
+Solaris binary emulation
 CONFIG_SOLARIS_EMUL
   This is experimental code which will enable you to run (many)
-  Solaris binaries on your SPARC Linux machine. 
+  Solaris binaries on your SPARC Linux machine.
 
   This code is also available as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want).
   The module will be called solaris.o. If you want to compile it as a
-  module, say M here and read Documentation/modules.txt.
+  module, say M here and read <file:Documentation/modules.txt>.
+
+SUN SME environment monitoring
+CONFIG_ENVCTRL
+  Kernel support for temperature and fan monitoring on Sun SME
+  machines.
 
+  This code is also available as a module ( = code which can be
+  inserted in and removed from the running kernel whenever you want).
+  The module will be called envctrl.o. If you want to compile it as a
+  module, say M here and read <file:Documentation/modules.txt>.
+
+# Choice: x86
 Processor family
 CONFIG_M386
   This is the processor type of your CPU. This information is used for
@@ -3215,17 +3756,17 @@
 
   Here are the settings recommended for greatest speed:
    - "386" for the AMD/Cyrix/Intel 386DX/DXL/SL/SLC/SX, Cyrix/TI
-     486DLC/DLC2, UMC 486SX-S and NexGen Nx586. Only "386" kernels will
-     run on a 386 class machine.
+     486DLC/DLC2, UMC 486SX-S and NexGen Nx586.  Only "386" kernels
+     will run on a 386 class machine.
    - "486" for the AMD/Cyrix/IBM/Intel 486DX/DX2/DX4 or
      SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5D or U5S.
-   - "586" for generic Pentium CPUs, possibly lacking the TSC 
+   - "586" for generic Pentium CPUs, possibly lacking the TSC
      (time stamp counter) register.
    - "Pentium-Classic" for the Intel Pentium.
    - "Pentium-MMX" for the Intel Pentium MMX.
    - "Pentium-Pro" for the Intel Pentium Pro/Celeron/Pentium II.
    - "Pentium-III" for the Intel Pentium III
-     and Celerons based on the coppermine core.
+     and Celerons based on the Coppermine core.
    - "Pentium-4" for the Intel Pentium 4.
    - "K6" for the AMD K6, K6-II and K6-III (aka K6-3D).
    - "Athlon" for the AMD K7 family (Athlon/Duron/Thunderbird).
@@ -3237,18 +3778,54 @@
 
   If you don't know what to do, choose "386".
 
+486
+CONFIG_M486
+  Select this for a x486 processor, ether Intel or one of the
+  compatible processors from AMD, Cyrix, IBM, or Intel.  Includes DX,
+  DX2, and DX4 variants; also SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5D or
+  U5S.
+
+586/K5/5x86/6x86/6x86MX
+CONFIG_M586
+  Select this for an x586 or x686 processor such as the AMD K5, the
+  Intel 5x86 or 6x86, or the Intel 6x86MX.  This choice does not
+  assume the RDTSC instruction.
+
+Pentium Classic
+CONFIG_M586TSC
+  Select this for a Pentium Classic processor with the RDTSC (Read
+  Time Stamp Counter) instruction for benchmarking.
+
+32-bit PDC
+CONFIG_PDC_NARROW
+  Saying Y here will allow developers with a C180, C200, C240, C360,
+  J200, J210, and/or a J2240 to test 64-bit kernels by providing a
+  wrapper for the 32-bit PDC calls.  Since the machines which require
+  this option do not support over 4G of RAM, this option is targeted
+  for developers of these machines wishing to test changes on both
+  32-bit and 64-bit configurations.
+
+  If unsure, say N.
+
 VGA text console
 CONFIG_VGA_CONSOLE
   Saying Y here will allow you to use Linux in text mode through a
   display that complies with the generic VGA standard. Virtually
-  everyone wants that. 
+  everyone wants that.
 
   The program SVGATextMode can be used to utilize SVGA video cards to
   their full potential in text mode. Download it from
-  ftp://metalab.unc.edu/pub/Linux/utils/console .
+  <ftp://metalab.unc.edu/pub/Linux/utils/console>.
 
   Say Y.
 
+Distribute interrupts on all CPUs by default
+CONFIG_IRQ_ALL_CPUS
+  This option gives the kernel permission to distribute IRQs across
+  multiple CPUs.  Saying N here will route all IRQs to the first
+  CPU. Generally SMP PowerMacs can answer Y. SMP IBM CHRP boxes or
+  Power3 boxes should say N for now.
+
 Video mode selection support
 CONFIG_VIDEO_SELECT
   This enables support for text mode selection on kernel startup. If
@@ -3260,16 +3837,16 @@
   "man bootparam" or see the documentation of your boot loader about
   how to pass options to the kernel.)
 
-  Read the file Documentation/svga.txt for more information about the
-  Video mode selection support. If unsure, say N.
+  Read the file <file:Documentation/svga.txt> for more information
+  about the Video mode selection support. If unsure, say N.
 
-Support for frame buffer devices (EXPERIMENTAL)
+Support for frame buffer devices
 CONFIG_FB
   The frame buffer device provides an abstraction for the graphics
   hardware. It represents the frame buffer of some video hardware and
   allows application software to access the graphics hardware through
   a well-defined interface, so the software doesn't need to know
-  anything about the low-level (hardware register) stuff. 
+  anything about the low-level (hardware register) stuff.
 
   Frame buffer devices work identically across the different
   architectures supported by Linux and make the implementation of
@@ -3277,14 +3854,14 @@
   server exists which uses the frame buffer device exclusively.
   On several non-X86 architectures, the frame buffer device is the
   only way to use the graphics hardware.
- 
+
   The device is accessed through special device nodes, usually located
   in the /dev directory, i.e. /dev/fb*.
 
   You need an utility program called fbset to make full use of frame
-  buffer devices. Please read Documentation/fb/framebuffer.txt and the
-  Framebuffer-HOWTO at
-  http://www.tahallah.demon.co.uk/programming/prog.html for more
+  buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
+  and the Framebuffer-HOWTO at
+  <http://www.tahallah.demon.co.uk/programming/prog.html> for more
   information.
 
   Say Y here and to the driver for your graphics board below if you
@@ -3302,6 +3879,27 @@
   hardware found in Acorn RISC PCs and other ARM-based machines.  If
   unsure, say N.
 
+Permedia2 support
+CONFIG_FB_PM2
+  This is the frame buffer device driver for the Permedia2 AGP frame
+  buffer card from ASK, aka `Graphic Blaster Exxtreme'.  There is a
+  product page at
+  <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
+
+Enable FIFO disconnect feature
+CONFIG_FB_PM2_FIFO_DISCONNECT
+  Support the Permedia2 FIFOI disconnect feature (see CONFIG_FB_PM2).
+
+Generic Permedia2 PCI board support
+CONFIG_FB_PM2_PCI
+  Say Y to enable support for Permedia2 AGP frame buffer card from
+  3Dlabs (aka `Graphic Blaster Exxtreme') on the PCI bus.
+
+Phase5 CVisionPPC/BVisionPPC support
+CONFIG_FB_PM2_CVPPC
+  Say Y to enable support for the Amiga Phase 5 CVisionPPC BVisionPPC
+  framebuffer cards.  Phase 5 is no longer with us, alas.
+
 Amiga native chipset support
 CONFIG_FB_AMIGA
   This is the frame buffer device driver for the builtin graphics
@@ -3310,7 +3908,7 @@
   The driver is also available as a module ( = code which can be
   inserted and removed from the running kernel whenever you want). The
   module will be called amifb.o. If you want to compile it as a
-  module, say M here and read Documentation/modules.txt.
+  module, say M here and read <file:Documentation/modules.txt>.
 
 Amiga OCS chipset support
 CONFIG_FB_AMIGA_OCS
@@ -3348,7 +3946,7 @@
   Say Y if you have a NetWinder or a graphics card containing this
   device, otherwise say N.
 
-Amiga CyberVision3D support (EXPERIMENTAL)
+Amiga CyberVision3D support
 CONFIG_FB_VIRGE
   This enables support for the Cybervision 64/3D graphics card from
   Phase5. Please note that its use is not all that intuitive (i.e. if
@@ -3357,13 +3955,13 @@
   kernel. Please note that this driver DOES NOT support the older
   Cybervision 64 card, as they use incompatible video chips.
 
-Amiga RetinaZ3 support (EXPERIMENTAL)
+Amiga RetinaZ3 support
 CONFIG_FB_RETINAZ3
   This enables support for the Retina Z3 graphics card. Say N unless
   you have a Retina Z3 or plan to get one before you next recompile
   the kernel.
 
-Cirrus Logic generic driver (EXPERIMENTAL)
+Cirrus Logic generic driver
 CONFIG_FB_CLGEN
   This enables support for Cirrus Logic GD542x/543x based boards on
   Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
@@ -3371,21 +3969,17 @@
   If you have a PCI-based system, this enables support for these
   chips: GD-543x, GD-544x, GD-5480.
 
-  Please read the file Documentation/fb/clgenfb.txt.
+  Please read the file <file:Documentation/fb/clgenfb.txt>.
 
   Say N unless you have such a graphics board or plan to get one
   before you next recompile the kernel.
 
-Permedia2 support (EXPERIMENTAL)
-CONFIG_FB_PM2
-  Say Y here if this is your graphics board.
-
 Apollo support
 CONFIG_APOLLO
   Say Y here if you want to run Linux on an MC680x0-based Apollo
   Domain workstation such as the DN3500.
 
-Apollo 3c505 support
+Apollo 3c505 "EtherLink Plus" support
 CONFIG_APOLLO_ELPLUS
   Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
   If you don't have one made for Apollos, you can use one from a PC,
@@ -3397,16 +3991,21 @@
   This is the frame buffer device driver for the builtin graphics
   chipset found in Ataris.
 
-Open Firmware frame buffer device support 
+Amiga FrameMaster II/Rainbow II support
+CONFIG_FB_FM2
+  This is the frame buffer device driver for the Amiga FrameMaster
+  card from BSC (exhibited 1992 but not shipped as a CBM product).
+
+Open Firmware frame buffer device support
 CONFIG_FB_OF
   Say Y if you want support with Open Firmware for your graphics
   board.
 
-S3 Trio frame buffer device support 
+S3 Trio frame buffer device support
 CONFIG_FB_S3TRIO
-  If you have a S3 Trio say Y. Say N for S3 Virge. 
+  If you have a S3 Trio say Y. Say N for S3 Virge.
 
-3Dfx Banshee/Voodoo3 display support (EXPERIMENTAL)
+3Dfx Banshee/Voodoo3 display support
 CONFIG_FB_3DFX
   This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
   chips. Say Y if you have such a graphics board.
@@ -3414,9 +4013,9 @@
   The driver is also available as a module ( = code which can be
   inserted and removed from the running kernel whenever you want). The
   module will be called tdfxfb.o. If you want to compile it as a
-  module, say M here and read Documentation/modules.txt.
+  module, say M here and read <file:Documentation/modules.txt>.
 
-nVidia Riva support (EXPERIMENTAL)
+nVidia Riva support
 CONFIG_FB_RIVA
   This driver supports graphics boards with the nVidia Riva/Geforce
   chips.
@@ -3425,9 +4024,9 @@
   The driver is also available as a module ( = code which can be
   inserted and removed from the running kernel whenever you want). The
   module will be called rivafb.o. If you want to compile it as a
-  module, say M here and read Documentation/modules.txt.
+  module, say M here and read <file:Documentation/modules.txt>.
 
-ATI Mach64 display support (EXPERIMENTAL)
+ATI Mach64 display support
 CONFIG_FB_ATY
   This driver supports graphics boards with the ATI Mach64 chips.
   Say Y if you have such a graphics board.
@@ -3435,30 +4034,54 @@
   The driver is also available as a module ( = code which can be
   inserted and removed from the running kernel whenever you want). The
   module will be called atyfb.o. If you want to compile it as a
-  module, say M here and read Documentation/modules.txt.
-  
-ATI Mach64 GX display support (EXPERIMENTAL)
-CONFIG_FB_ATY_GX
-  This options adds support for the first generation ATI Mach64
-  graphics chips, i.e. the Mach64 GX and CX. Note that this support is
-  limited.
-
-ATI Mach64 CT/VT/GT/LT display support (EXPERIMENTAL)
-CONFIG_FB_ATY_CT
-  This option adss support for ATI Mach64 graphics chips starting
-  with the Mach64 CT family. This includes the Mach64 VT (limited
-  support), GT (3D RAGE family), and LT.
+  module, say M here and read <file:Documentation/modules.txt>.
 
-ATI Rage128 display support (EXPERIMENTAL)
+ATI Rage128 display support
 CONFIG_FB_ATY128
   This driver supports graphics boards with the ATI Rage128 chips.
   Say Y if you have such a graphics board and read
-  Documentation/fb/aty128fb.txt. 
+  <file:Documentation/fb/aty128fb.txt>.
 
   The driver is also available as a module ( = code which can be
   inserted and removed from the running kernel whenever you want). The
   module will be called aty128fb.o. If you want to compile it as a
-  module, say M here and read Documentation/modules.txt.
+  module, say M here and read <file:Documentation/modules.txt>.
+
+# AC tree only
+Maxine (Personal DECstation) onboard framebuffer support
+CONFIG_FB_MAXINE
+  Say Y here to directly support the on-board framebuffer in the
+  Maxine (5000/20, /25, /33) version of the DECstation.  There is a
+  page dedicated to Linux on DECstations at <http://decstation.unix-ag.org/>.
+
+# AC tree only
+PMAG-BA TURBOchannel framebuffer support
+CONFIG_FB_PMAG_BA
+  Say Y here to directly support the on-board PMAG-BA framebuffer in
+  the 5000/1xx versions of the DECstation.  There is a page dedicated
+  to Linux on DECstations at <http://decstation.unix-ag.org/>.
+
+# AC tree only
+PMAGB-B TURBOchannel framebuffer support
+CONFIG_FB_PMAGB_B
+  Say Y here to directly support the on-board PMAGB-B framebuffer in
+  the 5000/1xx versions of the DECstation.  There is a page dedicated
+  to Linux on DECstations at <http://decstation.unix-ag.org/>.
+
+FutureTV PCI card
+CONFIG_ARCH_FTVPCI
+  Say Y here if you intend to run this kernel on a FutureTV (nee Nexus
+  Electronics) StrongARM PCI card.
+
+P720T
+CONFIG_ARCH_P720T
+  Say Y here if you intend to run this kernel on the ARM Prospector
+  720T.
+
+Link-Up Systems LCD support
+CONFIG_FB_L7200
+  This driver supports the L7200 Color LCD.
+  Say Y if you want graphics support.
 
 PowerMac "control" frame buffer device support
 CONFIG_FB_CONTROL
@@ -3490,13 +4113,13 @@
   This is the frame buffer device driver for generic VESA 2.0
   compliant graphic cards. The older VESA 1.2 cards are not supported.
   You will get a boot time penguin logo at no additional cost. Please
-  read Documentation/fb/vesafb.txt. If unsure, say Y.
+  read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
 
 VGA 16-color planar support
 CONFIG_FBCON_VGA_PLANES
   This low level frame buffer console driver enable the kernel to use
   the 16-color planar modes of the old VGA cards where the bits of
-  each pixel are separated into 4 planes. 
+  each pixel are separated into 4 planes.
 
   Only answer Y here if you have a (very old) VGA card that isn't VESA
   2 compatible.
@@ -3509,7 +4132,29 @@
   This code is also available as a module. If you want to compile it
   as a module ( = code which can be inserted in and removed from the
   running kernel whenever you want), say M here and read
-  Documentation/modules.txt. The module will be called vga16fb.o.
+  <file:Documentation/modules.txt>.  The module will be called
+  vga16fb.o.
+
+Generic STI frame buffer device support
+CONFIG_FB_STI
+  STI refers to the HP "Standard Text Interface" which is a set of
+  BIOS routines contained in a ROM chip in HP PA-RISC based machines.
+  Enabling this option will implement the linux framebuffer device and
+  an fbcon color text console using calls to the STI BIOS routines.
+  The HP framebuffer device is usually planar, uses a strange memory
+  layout, and changing the plane mask to create colored pixels
+  requires a call to the STI routines, so do not expect /dev/fb to
+  actually be useful.  However, it is the best we have as far as
+  graphics on the HP chipsets due to lack of hardware level
+  documentation for the various on-board HP chipsets used in these
+  systems.  It is sufficient for basic text console functions,
+  including fonts.
+
+  You should probably enable this option, unless you are having
+  trouble getting video when booting the kernel (make sure it isn't
+  just that you are running the console on the serial port, though).
+  Really old HP boxes may not have STI, and must use the PDC BIOS
+  console or the IODC BIOS.
 
 Select other compiled-in fonts
 CONFIG_FBCON_FONTS
@@ -3517,7 +4162,7 @@
   your frame buffer console usually use.
 
   Note that the answer to this question won't directly affect the
-  kernel: saying N will just cause this configure script to skip all
+  kernel: saying N will just cause the configurator to skip all
   the questions about foreign fonts.
 
   If unsure, say N (the default choices are safe).
@@ -3549,14 +4194,29 @@
 VGA 8x8 font
 CONFIG_FONT_8x8
   This is the "high resolution" font for the VGA frame buffer (the one
-  provided by the text console 80x50 (and higher) modes). 
+  provided by the text console 80x50 (and higher) modes).
 
   Note that this is a poor quality font. The VGA 8x16 font is quite a
-  lot more readable. 
+  lot more readable.
 
   Given the resolution provided by the frame buffer device, answer N
   here is safe.
 
+Mac console 6x11 font (not supported by all drivers)
+CONFIG_FONT_6x11
+  Small console font with Macintosh-style high-half glyphs.  Some Mac
+  framebuffer drivers don't support this one at all.
+
+Pearl (old m68k) console 8x8 font
+CONFIG_FONT_PEARL_8x8
+  Small console font with PC-style control-character and high-half
+  glyphs.
+
+Acorn console 8x8 font
+CONFIG_FONT_ACORN_8x8
+  Small console font with PC-style control characters and high-half
+  glyphs.
+
 Backward compatibility mode for Xpmac
 CONFIG_FB_COMPAT_XPMAC
   If you use the Xpmac X server (common with mklinux), you'll need to
@@ -3564,35 +4224,61 @@
   includes a server that supports the frame buffer device directly
   (XF68_FBDev).
 
-HGA monochrome support (EXPERIMENTAL)
+Hercules (HGA) mono graphics support
 CONFIG_FB_HGA
   Say Y here if you have a Hercules mono graphics card.
 
   This driver is also available as a module ( = code which can be
   inserted and removed from the running kernel whenever you want).
   The module will be called hgafb.o. If you want to compile it as
-  a module, say M here and read Documentation/modules.txt.
+  a module, say M here and read <file:Documentation/modules.txt>.
 
   As this card technology is 15 years old, most people will answer N
   here.
 
+Epson 1355 framebuffer support
+CONFIG_FB_E1355
+  Build in support for the SED1355 Epson Research Embedded RAMDAC
+  LCD/CRT Controller (since redesignated as the S1D13505) as a
+  framebuffer.  Product specs at
+  <http://www.erd.epson.com/vdc/html/products.htm>.
+
+Dreamcast Frame Buffer support
+CONFIG_FB_DC
+  Say Y here to enable support for the framebuffer on the Sega
+  Dreamcast.  This driver is also available as a module, dcfb.o.
+
+Register Base Address
+CONFIG_E1355_REG_BASE
+  Epson SED1355/S1D13505 LCD/CRT controller register base address.
+  See the manuals at
+  <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for
+  discussion.
+
+Framebuffer Base Address
+CONFIG_E1355_FB_BASE
+  Epson SED1355/S1D13505 LCD/CRT controller memory base address.  See
+  the manuals at
+  <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for
+  discussion.
+
 NEC PowerVR 2 display support
 CONFIG_FB_PVR2
-  Say Y here if you have a PowerVR 2 card in your box. If you plan to
-  run linux on your Dreamcast, you will have to say Y here. This driver
-  may or may not work on other PowerVR 2 cards, but is totally untested.
-  Use at your own risk. If unsure, say N.
+  Say Y here if you have a PowerVR 2 card in your box.  If you plan to
+  run linux on your Dreamcast, you will have to say Y here.
+  This driver may or may not work on other PowerVR 2 cards, but is
+  totally untested.  Use at your own risk.  If unsure, say N.
 
   This driver is also available as a module ( = code which can be
   inserted and removed from the running kernel whenever you want).
-  The module will be called pvr2fb.o. If you want to compile it as
-  a module, say M here and read Documentation/modules.txt.
+  The module will be called pvr2fb.o.  If you want to compile it as
+  a module, say M here and read <file:Documentation/modules.txt>.
 
   You can pass several parameters to the driver at boot time or at
-  module load time. The parameters look like "video=pvr2:XXX", where
+  module load time.  The parameters look like "video=pvr2:XXX", where
   the meaning of XXX can be found at the end of the main source file
-  (drivers/video/pvr2fb.c). Please see the file
-  Documentation/fb/pvr2fb.txt.
+  (<file:drivers/video/pvr2fb.c>). Please see the file
+  <file:Documentation/fb/pvr2fb.txt>.
 
 Debug pvr2fb
 CONFIG_FB_PVR2_DEBUG
@@ -3600,26 +4286,26 @@
   messages. Most people will want to say N here. If unsure, you will
   also want to say N.
 
-Matrox unified accelerated driver (EXPERIMENTAL)
+Matrox unified accelerated driver
 CONFIG_FB_MATROX
   Say Y here if you have a Matrox Millennium, Matrox Millennium II,
   Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
   Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
-  Matrox G400 or G450 card in your box. At this time, support for the G100
-  is untested and support for G450 is highly experimental.
+  Matrox G400 or G450 card in your box. At this time, support for the
+  G100 is untested and support for G450 is highly experimental.
 
   This driver is also available as a module ( = code which can be
   inserted and removed from the running kernel whenever you want).
   The module will be called matroxfb.o. If you want to compile it as
-  a module, say M here and read Documentation/modules.txt.
+  a module, say M here and read <file:Documentation/modules.txt>.
 
   You can pass several parameters to the driver at boot time or at
   module load time. The parameters look like "video=matrox:XXX", where
   the meaning of XXX can be found at the end of the main source file
-  (drivers/video/matroxfb.c). Please see the file
-  Documentation/fb/matroxfb.txt. 
+  (<file:drivers/video/matroxfb.c>). Please see
+  <file:Documentation/fb/matroxfb.txt>.
 
-Matrox Millennium support
+Matrox Millennium I/II support
 CONFIG_FB_MATROX_MILLENIUM
   Say Y here if you have a Matrox Millennium or Matrox Millennium II
   video card. If you select "Advanced lowlevel driver options" below,
@@ -3638,9 +4324,9 @@
 Matrox G100/G200/G400/G450 support
 CONFIG_FB_MATROX_G100
   Say Y here if you have a Matrox G100, G200, G400 or G450 based
-  video card. If you select "Advanced lowlevel driver options", you 
-  should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed 
-  pixel and 32 bpp packed pixel. You can also use font widths 
+  video card. If you select "Advanced lowlevel driver options", you
+  should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
+  pixel and 32 bpp packed pixel. You can also use font widths
   different from 8.
 
   If you need support for G400 secondary head, you must first say Y to
@@ -3654,14 +4340,14 @@
   DDC (I2C) bus present on all Matroxes, an I2C bus which
   interconnects Matrox optional devices, like MGA-TVO on G200 and
   G400, and the secondary head DDC bus, present on G400 only.
-  
-  You can say Y or M here if you want to experiment with monitor 
+
+  You can say Y or M here if you want to experiment with monitor
   detection code. You must say Y or M here if you want to use either
   second head of G400 or MGA-TVO on G200 or G400.
-  
+
   If you compile it as module, it will create a module named
   i2c-matroxfb.o.
-  
+
 Matrox G400 second head support
 CONFIG_FB_MATROX_MAVEN
   WARNING !!! This support does not work with G450 !!!
@@ -3672,26 +4358,24 @@
   secondary head output is blanked while you are in X. With XFree
   3.9.17 preview you can use both heads if you use SVGA over fbdev or
   the fbdev driver on first head and the fbdev driver on second head.
-  
+
   If you compile it as module, two modules are created,
   matroxfb_crtc2.o and matroxfb_maven.o. Matroxfb_maven is needed for
   both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
   also load i2c-matroxfb to get it to run.
-  
+
   The driver starts in monitor mode and you must use the matroxset
-  tool (available at ftp://platan.vc.cvut.cz/pub/linux/matrox-latest)
-  to switch it to PAL or NTSC or to swap primary and secondary head
-  outputs. Secondary head driver also always start in 640x480
-  resolution, you must use fbset to change it.
-  
+  tool (available at
+  <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest>) to switch it to
+  PAL or NTSC or to swap primary and secondary head outputs.
+  Secondary head driver also always start in 640x480 resolution, you
+  must use fbset to change it.
+
   Also do not forget that second head supports only 16 and 32 bpp
   packed pixels, so it is a good idea to compile them into the kernel
-  too. You can use only some font widths, as the driver uses generic
+  too.  You can use only some font widths, as the driver uses generic
   painting procedures (the secondary head does not use acceleration
   engine).
-  
-  There is no need for enabling 'Matrox multihead support' if you have
-  only one Matrox card in the box.
 
 Matrox G450 second head support
 CONFIG_FB_MATROX_G450
@@ -3703,10 +4387,10 @@
   want two independent display devices.
 
   The driver starts in monitor mode and currently does not support
-  output in TV modes. You must use the matroxset tool (available
-  at ftp://platan.vc.cvut.cz/pub/linux/matrox-latest) to swap primary
-  and secondary head outputs. Secondary head driver always start in
-  640x480 resolution and you must use fbset to change it.
+  output in TV modes.  You must use the matroxset tool (available
+  at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest>) to swap
+  primary and secondary head outputs.  Secondary head driver always
+  start in 640x480 resolution and you must use fbset to change it.
 
   Also do not forget that second head supports only 16 and 32 bpp
   packed pixels, so it is a good idea to compile them into the kernel
@@ -3714,9 +4398,6 @@
   painting procedures (the secondary head does not use acceleration
   engine).
 
-  There is no need for enabling 'Matrox multihead support' if you have
-  only one Matrox card in the box.
-
 Matrox unified driver multihead support
 CONFIG_FB_MATROX_MULTIHEAD
   Say Y here if you have more than one (supported) Matrox device in
@@ -3732,6 +4413,24 @@
   for the different Matrox devices. This method is slightly faster but
   uses 40 KB of kernel memory per Matrox card.
 
+  There is no need for enabling 'Matrox multihead support' if you have
+  only one Matrox card in the box.
+
+3Dfx Voodoo Graphics / Voodoo2 frame buffer support
+CONFIG_FB_VOODOO1
+  Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or 
+  Voodoo2 (cvg) based graphics card.
+
+  This driver is also available as a module ( = code which can be 
+  inserted and removed from the running kernel whenever you want).
+  The module will be called sstfb.o. If you want to compile it as
+  a module, say M here and read Documentation/modules.txt.
+
+  WARNING: Do not use any application that uses the 3D engine
+  (namely glide) while using this driver.
+  Please read the file Documentation/fb/README-sstfb.txt for supported
+  options and other important info  support.
+
 MDA text console (dual-headed)
 CONFIG_MDA_CONSOLE
   Say Y here if you have an old MDA or monochrome Hercules graphics
@@ -3739,15 +4438,15 @@
   will then be able to use two monitors with your Linux system. Do not
   say Y here if your MDA card is the primary card in your system; the
   normal VGA driver will handle it.
-  
+
   This driver is also available as a module ( = code which can be
   inserted and removed from the running kernel whenever you want).
   The module will be called mdacon.o. If you want to compile it as
-  a module, say M here and read Documentation/modules.txt.
-  
+  a module, say M here and read <file:Documentation/modules.txt>.
+
   If unsure, say N.
 
-SBUS and UPA frame buffers
+SBUS and UPA framebuffers
 CONFIG_FB_SBUS
   Say Y if you want support for SBUS or UPA based frame buffer device.
 
@@ -3769,11 +4468,59 @@
 CONFIG_FB_CGTHREE
   This is the frame buffer device driver for the CGthree frame buffer.
 
+CGfourteen (SX) support
+CONFIG_FB_CGFOURTEEN
+  This is the frame buffer device driver for the CGfourteen frame
+  buffer on Desktop SPARCsystems with the SX graphics option.
+
+P9100 (Sparcbook 3 only) support
+CONFIG_FB_P9100
+  This is the frame buffer device driver for the P9100 card
+  supported on Sparcbook 3 machines.
+
+Leo (ZX) support
+CONFIG_FB_LEO
+  This is the frame buffer device driver for the SBUS-based Sun ZX
+  (leo) frame buffer cards.
+
+IGA 168x display support
+CONFIG_FB_IGA
+  This is the framebuffer device for the INTERGRAPHICS 1680 and
+  successor frame buffer cards.
+
 TCX (SS4/SS5 only) support
 CONFIG_FB_TCX
   This is the frame buffer device driver for the TCX 24/8bit frame
   buffer.
 
+HD64461 Frame Buffer support
+CONFIG_FB_HIT
+  This is the frame buffer device driver for the Hitachi HD64461 LCD
+  frame buffer card.
+
+SIS 630/540 display support
+CONFIG_FB_SIS
+  This is the frame buffer device driver for the SiS 630 and 640 Super
+  Socket 7 UMA cards.  Specs available at <http://www.sis.com.tw/>.
+
+# AC tree only
+SIS 630/540/730 support
+CONFIG_FB_SIS_300
+  This is the frame buffer device driver for the SiS 630 and related
+  Super Socket 7 UMA cards.  Specs available at
+  <http://www.sis.com.tw/>.
+
+# AC tree only
+SIS 315H/315 support
+CONFIG_FB_SIS_315
+  This is the frame buffer device driver for the SiS 315 graphics
+  card.  Specs available at <http://www.sis.com.tw/>.
+
+IMS Twin Turbo display support
+CONFIG_FB_IMSTT
+  The IMS Twin Turbo is a PCI-based frame buffer card bundled with
+  many Macintosh and compatible computers.
+
 Virtual Frame Buffer support (ONLY FOR TESTING!)
 CONFIG_FB_VIRTUAL
   This is a `virtual' frame buffer device. It operates on a chunk of
@@ -3788,13 +4535,48 @@
   This driver is also available as a module ( = code which can be
   inserted and removed from the running kernel whenever you want). The
   module will be called vfb.o. If you want to compile it as a module,
-  say M here and read Documentation/modules.txt.
- 
+  say M here and read <file:Documentation/modules.txt>.
+
   If unsure, say N.
 
+Mach64 CT/VT/GT/LT (incl. 3D RAGE) support
+CONFIG_FB_ATY_CT
+  Say Y here to support use of ATI's 64-bit Rage boards (or other
+  boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
+  framebuffer device.  The ATI product support page for these boards
+  is at <http://support.ati.com/products/pc/mach64/>.
+
+Sony Vaio Picturebook laptop LCD panel support
+CONFIG_FB_ATY_CT_VAIO_LCD
+  Say Y here if you want to use the full width of the Sony Vaio 
+  Picturebook laptops LCD panels (you will get a 128x30 console).
+
+  Note that you need to activate this mode using the 'vga=0x301'
+  option from your boot loader (lilo or loadlin).  See the
+  documentation of your boot loader about how to pass options to the
+  kernel.
+  
+Mach64 GX support
+CONFIG_FB_ATY_GX
+  Say Y here to support use of the ATI Mach64 Graphics Expression
+  board (or other boards based on the Mach64 GX chipset) as a
+  framebuffer device.  The ATI product support page for these boards
+  is at
+  <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
+
+# AC tree only
+ATI Radeon display support
+CONFIG_FB_RADEON
+  Choose this option if you want to use an ATI Radeon graphics card as
+  a framebuffer device.  There are both PCI and AGP versions.  You
+  don't need to choose this to run the Radeon in plain VGA mode.
+  There is a product page at
+  <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
+
+SA-1100 LCD support
 CONFIG_FB_SA1100
   This is a framebuffer device for the SA-1100 LCD Controller.
-  See http://www.linux-fbdev.org/ for information on framebuffer
+  See <http://www.linux-fbdev.org/> for information on framebuffer
   devices.
 
   If you plan to use the LCD display with your SA-1100 system, say
@@ -3819,8 +4601,8 @@
   Low level frame buffer console drivers can be modules ( = code which
   can be inserted and removed from the running kernel whenever you
   want). The modules will be called fbcon-*.o. If you want to compile
-  (some of) them as modules, read Documentation/modules.txt.
-  
+  (some of) them as modules, read <file:Documentation/modules.txt>.
+
   If unsure, say N.
 
 Monochrome support
@@ -3890,10 +4672,10 @@
   This is the low level frame buffer console driver for 1/2/4/8/16/32
   bits per pixel packed pixels on Mac. It supports variable font
   widths for low resolution screens.
-  
-HGA monochrome support (EXPERIMENTAL)
+
+HGA monochrome support
 CONFIG_FBCON_HGA
-  This is the low level frame buffer console driver for Hercules mono 
+  This is the low level frame buffer console driver for Hercules mono
   graphics cards.
 
 VGA characters/attributes support
@@ -3909,21 +4691,21 @@
   drive, PLIP link (Parallel Line Internet Protocol is mainly used to
   create a mini network by connecting the parallel ports of two local
   machines) etc., then you need to say Y here; please read
-  Documentation/parport.txt and drivers/parport/BUGS-parport.
+  <file:Documentation/parport.txt> and drivers/parport/BUGS-parport.
 
   For extensive information about drivers for many devices attaching
-  to the parallel port see http://www.torque.net/linux-pp.html on the
-  WWW.
+  to the parallel port see <http://www.torque.net/linux-pp.html> on
+  the WWW.
 
   It is possible to share a single parallel port among several devices
   and it is safe to compile all the corresponding drivers into the
-  kernel. If you want to compile parallel port support as a module ( =
-  code which can be inserted in and removed from the running kernel
-  whenever you want), say M here and read Documentation/modules.txt.
-  The module will be called parport.o. If you have more than one
-  parallel port and want to specify which port and IRQ to be used by
-  this driver at module load time, take a look at
-  Documentation/parport.txt.
+  kernel.  If you want to compile parallel port support as a module
+  ( = code which can be inserted in and removed from the running
+  kernel whenever you want), say M here and read
+  <file:Documentation/modules.txt>.  The module will be called
+  parport.o.  If you have more than one parallel port and want to
+  specify which port and IRQ to be used by this driver at module load
+  time, take a look at <file:Documentation/parport.txt>.
 
   If unsure, say Y.
 
@@ -3931,20 +4713,21 @@
 CONFIG_PARPORT_PC
   You should say Y here if you have a PC-style parallel port. All IBM
   PC compatible computers and some Alphas have PC-style parallel
-  ports. 
+  ports.
 
-  This code is also available as a module. If you want to compile it
+  This code is also available as a module.  If you want to compile it
   as a module ( = code which can be inserted in and removed from the
   running kernel whenever you want), say M here and read
-  Documentation/modules.txt. The module will be called parport_pc.o.
-  
+  <file:Documentation/modules.txt>.  The module will be called
+  parport_pc.o.
+
   If unsure, say Y.
 
 Parallel+serial PCI card support
 CONFIG_PARPORT_SERIAL
-  This adds support for multi-IO PCI cards that have parallel and serial
-  ports.  You should say Y or M here.  If you say M, the module will be
-  called parport_serial.o.
+  This adds support for multi-IO PCI cards that have parallel and
+  serial ports.  You should say Y or M here.  If you say M, the module
+  will be called parport_serial.o.
 
 Use FIFO/DMA if available
 CONFIG_PARPORT_PC_FIFO
@@ -3952,12 +4735,12 @@
   printing. Say Y here if you want to take advantage of that.
 
   As well as actually having a FIFO, or DMA capability, the kernel
-  will need to know which IRQ the parallel port has. By default,
+  will need to know which IRQ the parallel port has.  By default,
   parallel port interrupts will not be used, and so neither will the
-  FIFO. See Documentation/parport.txt to find out how to specify
-  which IRQ/DMA to use.
+  FIFO.  See <file:Documentation/parport.txt> to find out how to
+  specify which IRQ/DMA to use.
 
-SuperIO chipset support (EXPERIMENTAL)
+SuperIO chipset support
 CONFIG_PARPORT_PC_SUPERIO
   Saying Y here enables some probes for Super-IO chipsets in order to
   find out things like base addresses, IRQ lines and DMA channels.  It
@@ -3974,12 +4757,6 @@
   other non-standard types of parallel ports. This causes a
   performance loss, so most people say N.
 
-Sun Ultra/AX-style hardware 
-CONFIG_PARPORT_AX
-  Say Y here if you need support for the parallel port hardware on Sun
-  Ultra/AX machines. This code is also available as a module (say M),
-  called parport_ax.o. If in doubt, saying N is the safe plan.
-
 Amiga built-in parallel port support
 CONFIG_PARPORT_AMIGA
   Say Y here if you need support for the parallel port hardware on
@@ -3992,51 +4769,51 @@
   Atari machines. This code is also available as a module (say M),
   called parport_atari.o. If in doubt, saying N is the safe plan.
 
-Multiface 3 parallel port card support
+Multiface III parallel port support
 CONFIG_PARPORT_MFC3
   Say Y here if you need parallel port support for the MFC3 card.
   This code is also available as a module (say M), called
   parport_mfc3.o. If in doubt, saying N is the safe plan.
 
-Support IEEE1284 status readback
+Support IEEE 1284 status readback
 CONFIG_PRINTER_READBACK
   If you have a device on your parallel port that support this
   protocol, this option will allow the device to report its status. It
   is safe to say Y.
 
-IEEE1284 transfer modes
+IEEE 1284 transfer modes
 CONFIG_PARPORT_1284
   If you have a printer that supports status readback or device ID, or
   want to use a device that uses enhanced parallel port transfer modes
   such as EPP and ECP, say Y here to enable advanced IEEE 1284
   transfer modes. Also say Y if you want device ID information to
   appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
- 
+
 Enable loadable module support
 CONFIG_MODULES
   Kernel modules are small pieces of compiled code which can be
   inserted in or removed from the running kernel, using the programs
   insmod and rmmod. This is described in the file
-  Documentation/modules.txt, including the fact that you have to say
-  "make modules" in order to compile the modules that you chose during
-  kernel configuration. Modules can be device drivers, file systems,
-  binary executable formats, and so on. If you think that you may want
-  to make use of modules with this kernel in the future, then say Y
-  here. If unsure, say Y.
+  <file:Documentation/modules.txt>, including the fact that you have
+  to say "make modules" in order to compile the modules that you chose
+  during kernel configuration.  Modules can be device drivers, file
+  systems, binary executable formats, and so on. If you think that you
+  may want to make use of modules with this kernel in the future, then
+  say Y here.  If unsure, say Y.
 
 Set version information on all symbols for modules
 CONFIG_MODVERSIONS
   Usually, modules have to be recompiled whenever you switch to a new
-  kernel. Saying Y here makes it possible, and safe, to use the
+  kernel.  Saying Y here makes it possible, and safe, to use the
   same modules even after compiling a new kernel; this requires the
   program modprobe. All the software needed for module support is in
-  the modutils package (check the file Documentation/Changes for
-  location and latest version). NOTE: if you say Y here but don't
+  the modutils package (check the file <file:Documentation/Changes>
+  for location and latest version).  NOTE: if you say Y here but don't
   have the program genksyms (which is also contained in the above
   mentioned modutils package), then the building of your kernel will
-  fail. If you are going to use modules that are generated from
-  non-kernel sources, you would benefit from this option. Otherwise
-  it's not that important. So, N ought to be a safe bet.
+  fail.  If you are going to use modules that are generated from
+  non-kernel sources, you would benefit from this option.  Otherwise
+  it's not that important.  So, N ought to be a safe bet.
 
 Kernel module loader support
 CONFIG_KMOD
@@ -4048,11 +4825,11 @@
   kernel needs a module, it runs modprobe with the appropriate
   arguments, thereby loading the module if it is available. (This is a
   replacement for kerneld.) Say Y here and read about configuring it
-  in Documentation/kmod.txt.
+  in <file:Documentation/kmod.txt>.
 
-ARP daemon support (EXPERIMENTAL)
+ARP daemon support
 CONFIG_ARPD
-  Normally, the kernel maintains an internal cache which maps IP 
+  Normally, the kernel maintains an internal cache which maps IP
   addresses to hardware addresses on the local network, so that
   Ethernet/Token Ring/ etc. frames are sent to the proper address on
   the physical networking layer. For small networks having a few
@@ -4060,7 +4837,7 @@
   resolution (ARP) cache inside the kernel works well. However,
   maintaining an internal ARP cache does not work well for very large
   switched networks, and will use a lot of kernel memory if TCP/IP
-  connections are made to many machines on the network. 
+  connections are made to many machines on the network.
 
   If you say Y here, the kernel's internal ARP cache will never grow
   to more than 256 entries (the oldest entries are expired in a LIFO
@@ -4084,35 +4861,35 @@
 
   For an excellent introduction to Linux networking, please read the
   NET-3-HOWTO, available from
-  http://www.linuxdoc.org/docs.html#howto .
+  <http://www.linuxdoc.org/docs.html#howto>.
 
   This option is also necessary if you want to use the full power of
   term (term is a program which gives you almost full Internet
   connectivity if you have a regular dial up shell account on some
   Internet connected Unix computer; for more information, read
-  http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html ).
-  
+  <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>).
+
   If you say Y here and also to "/proc file system support" and
   "Sysctl support" below, you can change various aspects of the
   behavior of the TCP/IP code by writing to the (virtual) files in
   /proc/sys/net/ipv4/*; the options are explained in the file
-  Documentation/networking/ip-sysctl.txt.
+  <file:Documentation/networking/ip-sysctl.txt>.
 
   Short answer: say Y.
 
-IP: multicasting
+IP multicasting
 CONFIG_IP_MULTICAST
   This is code for addressing several networked computers at once,
   enlarging your kernel by about 2 KB. You need multicasting if you
   intend to participate in the MBONE, a high bandwidth network on top
   of the Internet which carries audio and video broadcasts. More
   information about the MBONE is on the WWW at
-  http://www-itg.lbl.gov/mbone/ . Information about the multicast
+  <http://www-itg.lbl.gov/mbone/>. Information about the multicast
   capabilities of the various network cards is contained in
-  Documentation/networking/multicast.txt. For most people, it's safe
-  to say N.
+  <file:Documentation/networking/multicast.txt>. For most people, it's
+  safe to say N.
 
-IP: advanced router
+Advanced router
 CONFIG_IP_ADVANCED_ROUTER
   If you intend to run your Linux box mostly as a router, i.e. as a
   computer that forwards and redistributes network packets, say Y; you
@@ -4120,7 +4897,7 @@
   control about the routing process.
 
   The answer to this question won't directly affect the kernel:
-  answering N will just cause this configure script to skip all the
+  answering N will just cause the configurator to skip all the
   questions about advanced routing.
 
   Note that your box can only act as a router if you enable IP
@@ -4130,7 +4907,7 @@
 
     echo "1" > /proc/sys/net/ipv4/ip_forward
 
-  at boot time after the /proc file system has been mounted. 
+  at boot time after the /proc file system has been mounted.
 
   If you turn on IP forwarding, you will also get the rp_filter, which
   automatically rejects incoming packets if the routing table entry
@@ -4148,26 +4925,27 @@
 
   If unsure, say N here.
 
-IP: policy routing
+Policy routing
 CONFIG_IP_MULTIPLE_TABLES
   Normally, a router decides what to do with a received packet based
   solely on the packet's final destination address. If you say Y here,
   the Linux router will also be able to take the packet's source
-  address into account. Furthermore, if you also say Y to "IP: use TOS
+  address into account. Furthermore, if you also say Y to "Use TOS
   value as routing key" below, the TOS (Type-Of-Service) field of the
   packet can be used for routing decisions as well. In addition, if
-  you say Y here and to "IP: fast network address translation" below,
+  you say Y here and to "Fast network address translation" below,
   the router will also be able to modify source and destination
   addresses of forwarded packets.
 
   If you are interested in this, please see the preliminary
-  documentation at http://www.compendium.com.ar/policy-routing.txt and
-  ftp://post.tepkom.ru/pub/vol2/Linux/docs/advanced-routing.tex . You
-  will need supporting software from ftp://ftp.inr.ac.ru/ip-routing/
-  
+  documentation at <http://www.compendium.com.ar/policy-routing.txt>
+  and <ftp://post.tepkom.ru/pub/vol2/Linux/docs/advanced-routing.tex>.
+  You will need supporting software from
+  <ftp://ftp.inr.ac.ru/ip-routing/>.
+
   If unsure, say N.
-  
-IP: equal cost multipath
+
+Equal cost multipath
 CONFIG_IP_ROUTE_MULTIPATH
   Normally, the routing tables specify a single action to be taken in
   a deterministic manner for a given packet. If you say Y here
@@ -4177,20 +4955,20 @@
   equal "cost" and chooses one of them in a non-deterministic fashion
   if a matching packet arrives.
 
-IP: use TOS value as routing key
+Use TOS value as routing key
 CONFIG_IP_ROUTE_TOS
   The header of every IP packet carries a TOS (Type Of Service) value
-  with which the packet requests a certain treatment, e.g. low latency
-  (for interactive traffic), high throughput, or high reliability. If
-  you say Y here, you will be able to specify different routes for
-  packets with different TOS values.
+  with which the packet requests a certain treatment, e.g. low
+  latency (for interactive traffic), high throughput, or high
+  reliability.  If you say Y here, you will be able to specify
+  different routes for packets with different TOS values.
 
-IP: use netfilter MARK value as routing key
+Use netfilter MARK value as routing key
 CONFIG_IP_ROUTE_FWMARK
   If you say Y here, you will be able to specify different routes for
   packets with different mark values (see iptables(8), MARK target).
 
-IP: verbose route monitoring
+Verbose route monitoring
 CONFIG_IP_ROUTE_VERBOSE
   If you say Y here, which is recommended, then the kernel will print
   verbose messages regarding the routing, for example warnings about
@@ -4199,20 +4977,20 @@
   handled by the klogd daemon which is responsible for kernel messages
   ("man klogd").
 
-IP: large routing tables
+Large routing tables
 CONFIG_IP_ROUTE_LARGE_TABLES
   If you have routing zones that grow to more than about 64 entries,
   you may want to say Y here to speed up the routing process.
 
-IP: fast network address translation
+Fast network address translation
 CONFIG_IP_ROUTE_NAT
   If you say Y here, your router will be able to modify source and
   destination addresses of packets that pass through it, in a manner
-  you specify. General information about Network Address Translation
+  you specify.  General information about Network Address Translation
   can be gotten from the document
-  http://www.csn.tu-chemnitz.de/~mha/linux-ip-nat/diplom/nat.html
+  <http://www.csn.tu-chemnitz.de/~mha/linux-ip-nat/diplom/nat.html>.
 
-IP: kernel level autoconfiguration
+Kernel level IP autoconfiguration
 CONFIG_IP_PNP
   This enables automatic configuration of IP addresses of devices and
   of the routing table during kernel boot, based on either information
@@ -4233,7 +5011,22 @@
   does BOOTP itself, providing all necessary information on the kernel
   command line, you can say N here. If unsure, say Y. Note that if you
   want to use BOOTP, a BOOTP server must be operating on your network.
-  Read Documentation/nfsroot.txt for details.
+  Read <file:Documentation/nfsroot.txt> for details.
+
+DHCP support
+CONFIG_IP_PNP_DHCP
+  If you want your Linux box to mount its whole root file system (the
+  one containing the directory /) from some other computer over the
+  net via NFS and you want the IP address of your computer to be
+  discovered automatically at boot time using the DHCP protocol (a
+  special protocol designed for doing this job), say Y here. In case
+  the boot ROM of your network card was designed for booting Linux and
+  does DHCP itself, providing all necessary information on the kernel
+  command line, you can say N here.
+
+  If unsure, say Y. Note that if you want to use DHCP, a DHCP server
+  must be operating on your network.  Read
+  <file:Documentation/nfsroot.txt> for details.
 
 RARP support
 CONFIG_IP_PNP_RARP
@@ -4243,10 +5036,10 @@
   discovered automatically at boot time using the RARP protocol (an
   older protocol which is being obsoleted by BOOTP and DHCP), say Y
   here. Note that if you want to use RARP, a RARP server must be
-  operating on your network. Read Documentation/nfsroot.txt for
+  operating on your network. Read <file:Documentation/nfsroot.txt> for
   details.
 
-IP: tunneling
+IP tunneling
 CONFIG_NET_IPIP
   Tunneling means encapsulating data of one protocol type within
   another protocol and sending it over a channel that understands the
@@ -4256,13 +5049,13 @@
   appear on a different network than it physically is, or to use
   mobile-IP facilities (allowing laptops to seamlessly move between
   networks without changing their IP addresses; check out
-  http://anchor.cs.binghamton.edu/~mobileip/LJ/index.html ). 
+  <http://anchor.cs.binghamton.edu/~mobileip/LJ/index.html>).
 
   Saying Y to this option will produce two modules ( = code which can
   be inserted in and removed from the running kernel whenever you
   want). Most people won't need this and can say N.
 
-IP: GRE tunnels over IP
+GRE tunnels over IP
 CONFIG_NET_IPGRE
   Tunneling means encapsulating data of one protocol type within
   another protocol and sending it over a channel that understands the
@@ -4270,18 +5063,18 @@
   GRE (Generic Routing Encapsulation) and at this time allows
   encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
   This driver is useful if the other endpoint is a Cisco router: Cisco
-  likes GRE much better than the other Linux tunneling driver ("IP:
+  likes GRE much better than the other Linux tunneling driver ("IP
   tunneling" above). In addition, GRE allows multicast redistribution
   through the tunnel.
 
-IP: broadcast GRE over IP
+Broadcast GRE over IP
 CONFIG_NET_IPGRE_BROADCAST
   One application of GRE/IP is to construct a broadcast WAN (Wide Area
   Network), which looks like a normal Ethernet LAN (Local Area
   Network), but can be distributed all over the Internet. If you want
-  to do that, say Y here and to "IP: multicast routing" below.
+  to do that, say Y here and to "IP multicast routing" below.
 
-IP: multicast routing
+IP multicast routing
 CONFIG_IP_MROUTE
   This is used if you want your machine to act as a router for IP
   packets that have several destination addresses. It is needed on the
@@ -4289,118 +5082,69 @@
   audio and video broadcasts. In order to do that, you would most
   likely run the program mrouted. Information about the multicast
   capabilities of the various network cards is contained in
-  Documentation/networking/multicast.txt. If you haven't heard about
-  it, you don't need it.
+  <file:Documentation/networking/multicast.txt>. If you haven't heard
+  about it, you don't need it.
 
-IP: PIM-SM version 1 support
+PIM-SM version 1 support
 CONFIG_IP_PIMSM_V1
   Kernel side support for Sparse Mode PIM (Protocol Independent
   Multicast) version 1. This multicast routing protocol is used widely
   because Cisco supports it. You need special software to use it
-  (pimd-v1). Please see http://netweb.usc.edu/pim/ for more
+  (pimd-v1). Please see <http://netweb.usc.edu/pim/> for more
   information about PIM.
 
   Say Y if you want to use PIM-SM v1. Note that you can say N here if
   you just want to use Dense Mode PIM.
 
-IP: PIM-SM version 2 support
+PIM-SM version 2 support
 CONFIG_IP_PIMSM_V2
   Kernel side support for Sparse Mode PIM version 2. In order to use
   this, you need an experimental routing daemon supporting it (pimd or
   gated-5). This routing protocol is not used widely, so say N unless
   you want to play with it.
 
-PC/TCP compatibility mode
-CONFIG_INET_PCTCP
-  If you have been having difficulties telnetting to your Linux
-  machine from a DOS system that uses (broken) PC/TCP networking
-  software (all versions up to OnNet 2.0) over your local Ethernet try
-  saying Y here. Everyone else says N. 
-
-  People having problems with NCSA telnet should see the file
-  Documentation/networking/ncsa-telnet.
-
-Path MTU Discovery (normally enabled)
-CONFIG_PATH_MTU_DISCOVERY
-  MTU (maximal transfer unit) is the size of the chunks we send out
-  over the net. "Path MTU Discovery" means that, instead of always
-  sending very small chunks, we start out sending big ones and if we
-  then discover that some host along the way likes its chunks smaller,
-  we adjust to a smaller size. This is good, so most people say Y
-  here.
-
-  However, some DOS software (versions of DOS NCSA telnet and Trumpet
-  Winsock in PPP mode) is broken and won't be able to connect to your
-  Linux machine correctly in all cases (especially through a terminal
-  server) unless you say N here. See
-  Documentation/networking/ncsa-telnet for the location of fixed NCSA
-  telnet clients. If in doubt, say Y.
-
-Disable NAGLE algorithm (normally enabled)
-CONFIG_TCP_NAGLE_OFF
-  The NAGLE algorithm works by requiring an acknowledgment before
-  sending small IP frames (packets). This keeps tiny telnet and
-  rlogin packets from congesting Wide Area Networks. Most people
-  strongly recommend to say N here, thereby leaving NAGLE
-  enabled. Those programs that would benefit from disabling this
-  facility can do it on a per connection basis themselves.
-
-IP: Allow large windows (not recommended if <16 MB of memory)
-CONFIG_SKB_LARGE
-  On high speed, long distance networks the performance limit on
-  networking becomes the amount of data the sending machine can buffer
-  until the other end confirms its reception. (At 45 Mbit/second there
-  are a lot of bits between New York and London ...). If you say Y
-  here, bigger buffers can be used which allows larger amounts of data
-  to be "in flight" at any given time. It also means a user process
-  can require a lot more memory for network buffers and thus this
-  option is best used only on machines with 16 MB of memory or higher.
-  Unless you are using long links with end to end speeds of over 2
-  Mbit a second or satellite links this option will make no difference
-  to performance.
-
 Unix domain sockets
 CONFIG_UNIX
   If you say Y here, you will include support for Unix domain sockets;
   sockets are the standard Unix mechanism for establishing and
-  accessing network connections. Many commonly used programs such as
+  accessing network connections.  Many commonly used programs such as
   the X Window system and syslog use these sockets even if your
-  machine is not connected to any network. Unless you are working on
+  machine is not connected to any network.  Unless you are working on
   an embedded system or something similar, you therefore definitely
   want to say Y here.
 
   However, the socket support is also available as a module ( = code
   which can be inserted in and removed from the running kernel
-  whenever you want). If you want to compile it as a module, say M
-  here and read Documentation/modules.txt. The module will be called
-  unix.o. If you try building this as a module and you have said Y to
-  "Kernel module loader support" above, be sure to add 'alias net-pf-1
-  unix' to your /etc/modules.conf file. Note that several important
-  services won't work correctly if you say M here and then neglect to
-  load the module.
+  whenever you want).  If you want to compile it as a module, say M
+  here and read <file:Documentation/modules.txt>. The module will be
+  called unix.o.  If you try building this as a module and you have
+  said Y to "Kernel module loader support" above, be sure to add
+  'alias net-pf-1 unix' to your /etc/modules.conf file. Note that
+  several important services won't work correctly if you say M here
+  and then neglect to load the module.
 
   Say Y unless you know what you are doing.
 
-The IPv6 protocol (EXPERIMENTAL)
+The IPv6 protocol
 CONFIG_IPV6
   This is experimental support for the next version of the Internet
   Protocol: IP version 6 (also called IPng "IP next generation").
   Features of this new protocol include: expanded address space,
   authentication and privacy, and seamless interoperability with the
   current version of IP (IP version 4). For general information about
-  IPv6, see http://playground.sun.com/pub/ipng/html/ipng-main.html ;
+  IPv6, see <http://playground.sun.com/pub/ipng/html/ipng-main.html>;
   for specific information about IPv6 under Linux read the HOWTO at
-  http://www.bieringer.de/linux/IPv6/ and the file net/ipv6/README in
-  the kernel source.
+  <http://www.bieringer.de/linux/IPv6/> and the file net/ipv6/README
+  in the kernel source.
 
   If you want to use IPv6, please upgrade to the newest net-tools as
-  given in Documentation/Changes. You will still be able to do regular
-  IPv4 networking as well.
+  given in <file:Documentation/Changes>. You will still be able to do
+  regular IPv4 networking as well.
 
   This protocol support is also available as a module ( = code which
   can be inserted in and removed from the running kernel whenever you
   want). The module will be called ipv6.o. If you want to compile it
-  as a module, say M here and read Documentation/modules.txt.
+  as a module, say M here and read <file:Documentation/modules.txt>.
 
   It is safe to say N here for now.
 
@@ -4410,8 +5154,8 @@
   through the old netlink interface. However, a better option is to
   say Y to "Kernel/User network link driver" and to "Routing
   messages" instead.
-  
-Kernel httpd acceleration (EXPERIMENTAL)
+
+Kernel httpd acceleration
 CONFIG_KHTTPD
   The kernel httpd acceleration daemon (kHTTPd) is a (limited) web
   server built into the kernel. It is limited since it can only serve
@@ -4430,17 +5174,17 @@
   The kHTTPd is experimental. Be careful when using it on a production
   machine. Also note that kHTTPd doesn't support virtual servers yet.
 
-IPX networking
+The IPX protocol
 CONFIG_IPX
   This is support for the Novell networking protocol, IPX, commonly
-  used for local networks of Windows machines. You need it if you want
-  to access Novell NetWare file or print servers using the Linux
+  used for local networks of Windows machines.  You need it if you
+  want to access Novell NetWare file or print servers using the Linux
   Novell client ncpfs (available from
-  ftp://metalab.unc.edu/pub/Linux/system/filesystems/ ) or from within
-  the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
-  http://www.linuxdoc.org/docs.html#howto ). In order to do the
-  former, you'll also have to say Y to "NCP file system support",
-  below.
+  <ftp://metalab.unc.edu/pub/Linux/system/filesystems/>) or from
+  within the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO,
+  available from <http://www.linuxdoc.org/docs.html#howto>).  In order
+  to do the former, you'll also have to say Y to "NCP file system
+  support", below.
 
   IPX is similar in scope to IP, while SPX, which runs on top of IPX,
   is similar to TCP. There is also experimental support for SPX in
@@ -4448,22 +5192,22 @@
 
   To turn your Linux box into a fully featured NetWare file server and
   IPX router, say Y here and fetch either lwared from
-  ftp://metalab.unc.edu/pub/Linux/system/network/daemons/ or mars_nwe
-  from ftp://ftp.gwdg.de/pub/linux/misc/ncpfs . For more information,
-  read the IPX-HOWTO available from
-  http://www.linuxdoc.org/docs.html#howto .
+  <ftp://metalab.unc.edu/pub/Linux/system/network/daemons/> or
+  mars_nwe from <ftp://ftp.gwdg.de/pub/linux/misc/ncpfs>. For more
+  information, read the IPX-HOWTO available from
+  <http://www.linuxdoc.org/docs.html#howto>.
 
   General information about how to connect Linux, Windows machines and
-  Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
+  Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
 
   The IPX driver would enlarge your kernel by about 16 KB. This driver
   is also available as a module ( = code which can be inserted in and
-  removed from the running kernel whenever you want). The module will
-  be called ipx.o. If you want to compile it as a module, say M here
-  and read Documentation/modules.txt. Unless you want to integrate
-  your Linux box with a local Novell network, say N.
+  removed from the running kernel whenever you want).  The module will
+  be called ipx.o.  If you want to compile it as a module, say M here
+  and read <file:Documentation/modules.txt>.  Unless you want to
+  integrate your Linux box with a local Novell network, say N.
 
-IPX: Full internal IPX network
+Full internal IPX network
 CONFIG_IPX_INTERN
   Every IPX network has an address that identifies it. Sometimes it is
   useful to give an IPX "network" address to your Linux box as well
@@ -4472,7 +5216,7 @@
   same address). The way this is done is to create a virtual internal
   "network" inside your box and to assign an IPX address to this
   network. Say Y here if you want to do this; read the IPX-HOWTO at
-  http://www.linuxdoc.org/docs.html#howto for details.
+  <http://www.linuxdoc.org/docs.html#howto> for details.
 
   The full internal IPX network enables you to allocate sockets on
   different virtual nodes of the internal network. This is done by
@@ -4485,12 +5229,17 @@
   'special' sockets to sockets listening on the primary network is
   disabled. This might break existing applications, especially RIP/SAP
   daemons. A RIP/SAP daemon that works well with the full internal net
-  can be found on ftp://ftp.gwdg.de/pub/linux/misc/ncpfs . 
+  can be found on <ftp://ftp.gwdg.de/pub/linux/misc/ncpfs>.
 
   If you don't know what you are doing, say N.
 
-IPX: SPX networking (EXPERIMENTAL)
+#(We're told this will come back someday)
+
+SPX networking
 CONFIG_SPX
+  * Orphaned entry retained 20 April 2001 by Petr Vandrovec     *
+  * If you read this note from the configurator, please contact *
+  * the Configure.help maintainers.                             *
   The Sequenced Packet eXchange protocol is a transport layer protocol
   built on top of IPX. It is used in Novell NetWare systems for
   client-server applications and is similar to TCP (which runs on top
@@ -4502,26 +5251,26 @@
   space programs lwared or mars_nwe for the server side).
 
   Say Y here if you have use for SPX; read the IPX-HOWTO at
-  http://www.linuxdoc.org/docs.html#howto for details.
+  <http://www.linuxdoc.org/docs.html#howto> for details.
 
   This driver is also available as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want).
   The module will be called af_spx.o. If you want to compile it as a
-  module, say M here and read Documentation/modules.txt.
+  module, say M here and read <file:Documentation/modules.txt>.
 
-DECnet networking (EXPERIMENTAL)
+DECnet networking
 CONFIG_DECNET
   The DECnet networking protocol was used in many products made by
-  Digital (now Compaq). It provides reliable stream and sequenced
+  Digital (now Compaq).  It provides reliable stream and sequenced
   packet communications over which run a variety of services similar
   to those which run over TCP/IP.
 
   To find some tools to use with the kernel layer support, please
-  look at Patrick Caulfield's web site: 
-  http://linux.dreamtime.org/decnet/
+  look at Patrick Caulfield's web site:
+  <http://linux.dreamtime.org/decnet/>.
 
-  More detailed documentation is available in the
-  Documentation/networking/decnet.txt file.
+  More detailed documentation is available in
+  <file:Documentation/networking/decnet.txt>.
 
   Be sure to say Y to "/proc file system support" and "Sysctl support"
   below when using DECnet, since you will need sysctl support to aid
@@ -4533,27 +5282,27 @@
 
 DECnet SIOCFIGCONF support
 CONFIG_DECNET_SIOCGIFCONF
-   This option should only be turned on if you are really sure that
-   you know what you are doing. It can break other applications which
-   use this system call and the proper way to get the information
-   provided by this call is to use rtnetlink.
-   
-   If unsure, say N.
+  This option should only be turned on if you are really sure that
+  you know what you are doing. It can break other applications which
+  use this system call and the proper way to get the information
+  provided by this call is to use rtnetlink.
+
+  If unsure, say N.
 
-DECnet Router Support (EXPERIMENTAL)
+DECnet router support
 CONFIG_DECNET_ROUTER
-   Add support for turning your DECnet Endnode into a level 1 or 2
-   router. This is an unfinished option for developers only. If you do
-   say Y here, then make sure that you also say Y to "Kernel/User
-   network link driver", "Routing messages" and "Network packet
-   filtering". The first two are required to allow configuration via
-   rtnetlink (currently you need Alexey Kuznetsov's iproute2 package
-   from ftp://ftp.inr.ac.ru). The "Network packet filtering" option
-   will be required for the forthcoming routing daemon to work.
+  Add support for turning your DECnet Endnode into a level 1 or 2
+  router.  This is an unfinished option for developers only.  If you
+  do say Y here, then make sure that you also say Y to "Kernel/User
+  network link driver", "Routing messages" and "Network packet
+  filtering".  The first two are required to allow configuration via
+  rtnetlink (currently you need Alexey Kuznetsov's iproute2 package
+  from <ftp://ftp.inr.ac.ru>). The "Network packet filtering" option
+  will be required for the forthcoming routing daemon to work.
 
-   See Documentation/networking/decnet.txt for more information.
+  See <file:Documentation/networking/decnet.txt> for more information.
 
-DECnet: use FWMARK value as routing key
+Use FWMARK value as DECnet routing key
 CONFIG_DECNET_ROUTE_FWMARK
   If you say Y here, you will be able to specify different routes for
   packets with different FWMARK ("firewalling mark") values
@@ -4568,28 +5317,29 @@
 AppleTalk protocol support
 CONFIG_ATALK
   AppleTalk is the way Apple computers speak to each other on a
-  network. If your Linux box is connected to such a network and you
-  want to join the conversation, say Y. You will need to use the
+  network.  If your Linux box is connected to such a network and you
+  want to join the conversation, say Y.  You will need to use the
   netatalk package so that your Linux box can act as a print and file
-  server for Macs as well as access AppleTalk printers. Check out
-  http://www.zettabyte.net/netatalk/ on the WWW for details. EtherTalk 
-  is the name used for AppleTalk over Ethernet and the cheaper and 
-  slower LocalTalk is AppleTalk over a proprietary Apple network using
-  serial links. EtherTalk and LocalTalk are fully supported by Linux.
+  server for Macs as well as access AppleTalk printers.  Check out
+  <http://www.zettabyte.net/netatalk/> on the WWW for details.
+  EtherTalk is the name used for AppleTalk over Ethernet and the
+  cheaper and slower LocalTalk is AppleTalk over a proprietary Apple
+  network using serial links.  EtherTalk and LocalTalk are fully
+  supported by Linux.
 
   General information about how to connect Linux, Windows machines and
-  Macs is on the WWW at http://www.eats.com/linux_mac_win.html . The
+  Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.  The
   NET-3-HOWTO, available from
-  http://www.linuxdoc.org/docs.html#howto , contains valuable
+  <http://www.linuxdoc.org/docs.html#howto>, contains valuable
   information as well.
 
   This driver is also available as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want).
-  The module is called appletalk.o. If you want to compile it as a
-  module, say M here and read Documentation/modules.txt.  You almost
-  certainly want to compile it as a module so you can restart your 
-  AppleTalk stack without rebooting your machine.  I hear that the 
-  GNU boycott of Apple is over, so even politically correct people
+  The module is called appletalk.o.  If you want to compile it as a
+  module, say M here and read <file:Documentation/modules.txt>.  You
+  almost certainly want to compile it as a module so you can restart
+  your AppleTalk stack without rebooting your machine.  I hear that
+  the GNU boycott of Apple is over, so even politically correct people
   are allowed to say Y here.
 
 AppleTalk-IP driver support
@@ -4600,7 +5350,7 @@
   box is stuck on an AppleTalk only network) or decapsulate (e.g. if
   you want your Linux box to act as an Internet gateway for a zoo of
   AppleTalk connected Macs). Please see the file
-  Documentation/networking/ipddp.txt for more information.
+  <file:Documentation/networking/ipddp.txt> for more information.
 
   If you say Y here, the AppleTalk-IP support will be compiled into
   the kernel. In this case, you can either use encapsulation or
@@ -4609,11 +5359,11 @@
 
   If you say M here, the AppleTalk-IP support will be compiled as a
   module ( = code which can be inserted in and removed from the
-  running kernel whenever you want, read Documentation/modules.txt).
-  The module is called ipddp.o. In this case, you will be able to use
-  both encapsulation and decapsulation simultaneously, by loading two
-  copies of the module and specifying different values for the module
-  option ipddp_mode. 
+  running kernel whenever you want, read
+  <file:Documentation/modules.txt>).  The module is called ipddp.o.
+  In this case, you will be able to use both encapsulation and
+  decapsulation simultaneously, by loading two copies of the module
+  and specifying different values for the module option ipddp_mode.
 
 IP to AppleTalk-IP Encapsulation support
 CONFIG_IPDDP_ENCAP
@@ -4621,20 +5371,20 @@
   IP packets inside AppleTalk frames; this is useful if your Linux box
   is stuck on an AppleTalk network (which hopefully contains a
   decapsulator somewhere). Please see
-  Documentation/networking/ipddp.txt for more information. If you said
-  Y to "AppleTalk-IP driver support" above and you say Y here, then
-  you cannot say Y to "AppleTalk-IP to IP Decapsulation support",
-  below.
+  <file:Documentation/networking/ipddp.txt> for more information. If
+  you said Y to "AppleTalk-IP driver support" above and you say Y
+  here, then you cannot say Y to "AppleTalk-IP to IP Decapsulation
+  support", below.
 
 AppleTalk-IP to IP Decapsulation support
 CONFIG_IPDDP_DECAP
   If you say Y here, the AppleTalk-IP code will be able to decapsulate
   AppleTalk-IP frames to IP packets; this is useful if you want your
   Linux box to act as an Internet gateway for an AppleTalk network.
-  Please see Documentation/networking/ipddp.txt for more information.
-  If you said Y to "AppleTalk-IP driver support" above and you say Y
-  here, then you cannot say Y to "IP to AppleTalk-IP Encapsulation
-  support", above.
+  Please see <file:Documentation/networking/ipddp.txt> for more
+  information.  If you said Y to "AppleTalk-IP driver support" above
+  and you say Y here, then you cannot say Y to "IP to AppleTalk-IP
+  Encapsulation support", above.
 
 Apple/Farallon LocalTalk PC card support
 CONFIG_LTPC
@@ -4643,7 +5393,7 @@
   If you are in doubt, this card is the one with the 65C02 chip on it.
   You also need version 1.3.3 or later of the netatalk package.
   This driver is experimental, which means that it may not work.
-  See the file Documentation/networking/ltpc.txt.
+  See the file <file:Documentation/networking/ltpc.txt>.
 
 COPS LocalTalk PC card support
 CONFIG_COPS
@@ -4652,7 +5402,7 @@
   package. This driver is experimental, which means that it may not
   work. This driver will only work if you choose "AppleTalk DDP"
   networking support, above.
-  Please read the file Documentation/networking/cops.txt. 
+  Please read the file <file:Documentation/networking/cops.txt>.
 
 Dayna firmware support
 CONFIG_COPS_DAYNA
@@ -4668,15 +5418,15 @@
 Amateur Radio support
 CONFIG_HAMRADIO
   If you want to connect your Linux box to an amateur radio, answer Y
-  here. You want to read http://www.tapr.org/tapr/html/pkthome.html
+  here. You want to read <http://www.tapr.org/tapr/html/pkthome.html>
   and the HAM-HOWTO and the AX25-HOWTO, both available from
-  http://www.linuxdoc.org/docs.html#howto .
+  <http://www.linuxdoc.org/docs.html#howto>.
 
   Note that the answer to this question won't directly affect the
-  kernel: saying N will just cause this configure script to skip all
+  kernel: saying N will just cause the configurator to skip all
   the questions about amateur radio.
 
-Amateur Radio AX.25 Level 2
+Amateur Radio AX.25 Level 2 protocol
 CONFIG_AX25
   This is the protocol used for computer communication over amateur
   radio. It is either used by itself for point-to-point links, or to
@@ -4694,15 +5444,16 @@
   Information about where to get supporting software for Linux amateur
   radio as well as information about how to configure an AX.25 port is
   contained in the AX25-HOWTO, available from
-  http://www.linuxdoc.org/docs.html#howto . You might also want to
-  check out the file Documentation/networking/ax25.txt in the kernel
-  source. More information about digital amateur radio in general is
-  on the WWW at http://www.tapr.org/tapr/html/pkthome.html .
+  <http://www.linuxdoc.org/docs.html#howto>. You might also want to
+  check out the file <file:Documentation/networking/ax25.txt> in the
+  kernel source. More information about digital amateur radio in
+  general is on the WWW at
+  <http://www.tapr.org/tapr/html/pkthome.html>.
 
   This driver is also available as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want).
   The module will be called ax25.o. If you want to compile it as a
-  module, say M here and read Documentation/modules.txt.
+  module, say M here and read <file:Documentation/modules.txt>.
 
 AX.25 DAMA Slave support
 CONFIG_AX25_DAMA_SLAVE
@@ -4722,7 +5473,7 @@
   slaves. If you say Y here, your Linux box will act as a DAMA server.
   If unsure, say N.
 
-Amateur Radio NET/ROM
+Amateur Radio NET/ROM support
 CONFIG_NETROM
   NET/ROM is a network layer protocol on top of AX.25 useful for
   routing.
@@ -4730,15 +5481,15 @@
   A comprehensive listing of all the software for Linux amateur radio
   users as well as information about how to configure an AX.25 port is
   contained in the AX25-HOWTO, available from
-  http://www.linuxdoc.org/docs.html#howto . You also might want to
-  check out the file Documentation/networking/ax25.txt. More
+  <http://www.linuxdoc.org/docs.html#howto>. You also might want to
+  check out the file <file:Documentation/networking/ax25.txt>. More
   information about digital amateur radio in general is on the WWW at
-  http://www.tapr.org/tapr/html/pkthome.html .
+  <http://www.tapr.org/tapr/html/pkthome.html>.
 
   This driver is also available as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want).
   The module will be called netrom.o. If you want to compile it as a
-  module, say M here and read Documentation/modules.txt.
+  module, say M here and read <file:Documentation/modules.txt>.
 
 Amateur Radio X.25 PLP (Rose)
 CONFIG_ROSE
@@ -4749,15 +5500,15 @@
   A comprehensive listing of all the software for Linux amateur radio
   users as well as information about how to configure an AX.25 port is
   contained in the AX25-HOWTO, available from
-  http://www.linuxdoc.org/docs.html#howto . You also might want to
-  check out the file Documentation/networking/ax25.txt. More
+  <http://www.linuxdoc.org/docs.html#howto>.  You also might want to
+  check out the file <file:Documentation/networking/ax25.txt>. More
   information about digital amateur radio in general is on the WWW at
-  http://www.tapr.org/tapr/html/pkthome.html .
+  <http://www.tapr.org/tapr/html/pkthome.html>.
 
   This driver is also available as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want).
   The module will be called rose.o. If you want to compile it as a
-  module, say M here and read Documentation/modules.txt.
+  module, say M here and read <file:Documentation/modules.txt>.
 
 Serial port KISS driver for AX.25
 CONFIG_MKISS
@@ -4773,8 +5524,8 @@
 
   If you want to compile this driver as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt. The module will be
-  called mkiss.o.
+  say M here and read <file:Documentation/modules.txt>.  The module
+  will be called mkiss.o.
 
 Serial port 6PACK driver for AX.25
 CONFIG_6PACK
@@ -4787,12 +5538,12 @@
 
   Note that this driver is still experimental and might cause
   problems. For details about the features and the usage of the
-  driver, read Documentation/networking/6pack.txt.
+  driver, read <file:Documentation/networking/6pack.txt>.
 
   If you want to compile this driver as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt. The module will be
-  called 6pack.o.
+  say M here and read <file:Documentation/modules.txt>.  The module
+  will be called 6pack.o.
 
 BPQ Ethernet driver
 CONFIG_BPQETHER
@@ -4813,7 +5564,7 @@
   Currently, this driver supports Ottawa PI/PI2, Paccomm/Gracilis
   PackeTwin, and S5SCC/DMA boards. They are detected automatically.
   If you have one of these cards, say Y here and read the AX25-HOWTO,
-  available from http://www.linuxdoc.org/docs.html#howto .
+  available from <http://www.linuxdoc.org/docs.html#howto>.
 
   This driver can operate multiple boards simultaneously. If you
   compile it as a module (by saying M instead of Y), it will be called
@@ -4829,7 +5580,7 @@
   certain parameters, such as channel access timing, clock mode, and
   DMA channel. This is accomplished with a small utility program,
   dmascc_cfg, available at
-  http://www.nt.tuwien.ac.at/~kkudielk/Linux/ . Please be sure to get
+  <http://www.nt.tuwien.ac.at/~kkudielk/Linux/>. Please be sure to get
   at least version 1.27 of dmascc_cfg, as older versions will not
   work with the current driver.
 
@@ -4837,27 +5588,28 @@
 CONFIG_SCC
   These cards are used to connect your Linux box to an amateur radio
   in order to communicate with other computers. If you want to use
-  this, read Documentation/networking/z8530drv.txt and the AX25-HOWTO,
-  available from http://www.linuxdoc.org/docs.html#howto . Also
-  make sure to say Y to "Amateur Radio AX.25 Level 2" support.
+  this, read <file:Documentation/networking/z8530drv.txt> and the
+  AX25-HOWTO, available from
+  <http://www.linuxdoc.org/docs.html#howto>. Also make sure to say Y
+  to "Amateur Radio AX.25 Level 2" support.
 
   If you want to compile this as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt. The module will be
-  called scc.o.
+  say M here and read <file:Documentation/modules.txt>.  The module
+  will be called scc.o.
+
+Support for TRX that feedback the tx signal to rx
+CONFIG_SCC_TRXECHO
+  Some transmitters feed the transmitted signal back to the receive
+  line.  Say Y here to foil this by explicitly disabling the receiver
+  during data transmission.  If in doubt, say Y.
 
-additional delay for PA0HZP OptoSCC compatible boards
+Additional delay for PA0HZP OptoSCC compatible boards
 CONFIG_SCC_DELAY
   Say Y here if you experience problems with the SCC driver not
-  working properly; please read Documentation/networking/z8530drv.txt
-  for details. If unsure, say N.
-
-#support for TRX that feedback the tx signal to rx
-#CONFIG_SCC_TRXECHO
-###
-### Don't know what's going on here.
-###
-#
+  working properly; please read
+  <file:Documentation/networking/z8530drv.txt> for details. If unsure,
+  say N.
 
 YAM driver for AX.25
 CONFIG_YAM
@@ -4867,7 +5619,7 @@
 
   If you want to compile this as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt.
+  say M here and read <file:Documentation/modules.txt>.
 
 BAYCOM picpar and par96 driver for AX.25
 CONFIG_BAYCOM_PAR
@@ -4875,13 +5627,13 @@
   connect to a parallel interface. The driver supports the picpar and
   par96 designs. To configure the driver, use the sethdlc utility
   available in the standard ax25 utilities package. For information on
-  the modems, see http://www.baycom.de and the file
-  Documentation/networking/baycom.txt.
+  the modems, see <http://www.baycom.de> and the file
+  <file:Documentation/networking/baycom.txt>.
 
   If you want to compile this driver as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt. This is recommended.
-  The module will be called baycom_par.o.
+  say M here and read <file:Documentation/modules.txt>.  This is
+  recommended.  The module will be called baycom_par.o.
 
 BAYCOM EPP driver for AX.25
 CONFIG_BAYCOM_EPP
@@ -4889,48 +5641,49 @@
   connect to a parallel interface. The driver supports the EPP
   designs. To configure the driver, use the sethdlc utility available
   in the standard ax25 utilities package. For information on the
-  modems, see http://www.baycom.de and the file
-  Documentation/networking/baycom.txt.
+  modems, see <http://www.baycom.de> and the file
+  <file:Documentation/networking/baycom.txt>.
 
   If you want to compile this driver as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt. This is recommended.
-  The module will be called baycom_par.o.
+  say M here and read <file:Documentation/modules.txt>.  This is
+  recommended.  The module will be called baycom_par.o.
 
-BAYCOM ser12 full duplex driver for AX.25
+BAYCOM ser12 full-duplex driver for AX.25
 CONFIG_BAYCOM_SER_FDX
   This is one of two drivers for Baycom style simple amateur radio
   modems that connect to a serial interface. The driver supports the
-  ser12 design in full duplex mode. In addition, it allows the
+  ser12 design in full-duplex mode. In addition, it allows the
   baudrate to be set between 300 and 4800 baud (however not all modems
   support all baudrates). This is the preferred driver. The next
-  driver, "BAYCOM ser12 half duplex driver for AX.25" is the old
+  driver, "BAYCOM ser12 half-duplex driver for AX.25" is the old
   driver and still provided in case this driver does not work with
   your serial interface chip. To configure the driver, use the sethdlc
   utility available in the standard ax25 utilities package. For
-  information on the modems, see http://www.baycom.de and
-  Documentation/networking/baycom.txt.
+  information on the modems, see <http://www.baycom.de> and
+  <file:Documentation/networking/baycom.txt>.
 
   If you want to compile this driver as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt. This is recommended.
-  The module will be called baycom_ser_fdx.o.
+  say M here and read <file:Documentation/modules.txt>.  This is
+  recommended.  The module will be called baycom_ser_fdx.o.
 
-BAYCOM ser12 half duplex driver for AX.25
+BAYCOM ser12 half-duplex driver for AX.25
 CONFIG_BAYCOM_SER_HDX
   This is one of two drivers for Baycom style simple amateur radio
   modems that connect to a serial interface. The driver supports the
-  ser12 design in full duplex mode. This is the old driver. It is
+  ser12 design in full-duplex mode. This is the old driver.  It is
   still provided in case your serial interface chip does not work with
-  the full duplex driver. This driver is depreciated. To configure the
-  driver, use the sethdlc utility available in the standard ax25
+  the full-duplex driver. This driver is depreciated.  To configure
+  the driver, use the sethdlc utility available in the standard ax25
   utilities package. For information on the modems, see
-  http://www.baycom.de and Documentation/networking/baycom.txt.
+  <http://www.baycom.de> and
+  <file:Documentation/networking/baycom.txt>.
 
   If you want to compile this driver as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt. This is recommended.
-  The module will be called baycom_ser_hdx.o.
+  say M here and read <file:Documentation/modules.txt>.  This is
+  recommended.  The module will be called baycom_ser_hdx.o.
 
 Sound card modem driver for AX.25
 CONFIG_SOUNDMODEM
@@ -4942,13 +5695,13 @@
   To configure the driver, use the sethdlc, smdiag and smmixer
   utilities available in the standard ax25 utilities package. For
   information on how to key the transmitter, see
-  http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html and
-  Documentation/networking/soundmodem.txt.
+  <http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html> and
+  <file:Documentation/networking/soundmodem.txt>.
 
   If you want to compile this driver as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt. This is recommended.
-  The module will be called soundmodem.o.
+  say M here and read <file:Documentation/modules.txt>.  This is
+  recommended.  The module will be called soundmodem.o.
 
 Sound card modem support for Sound Blaster and compatible cards
 CONFIG_SOUNDMODEM_SBC
@@ -4957,7 +5710,7 @@
   with a Sound Blaster emulation) you should say N here and Y to
   "Sound card modem support for WSS and Crystal cards", below, because
   this usually results in better performance. This option also
-  supports SB16/32/64 in full duplex mode.
+  supports SB16/32/64 in full-duplex mode.
 
 Sound card modem support for WSS and Crystal cards
 CONFIG_SOUNDMODEM_WSS
@@ -4965,8 +5718,8 @@
   compatible cards. These cards feature a codec chip from either
   Analog Devices (such as AD1848, AD1845, AD1812) or Crystal
   Semiconductors (such as CS4248, CS423x). This option also supports
-  the WSS full duplex operation which currently works with Crystal
-  CS423x chips. If you don't need full duplex operation, do not enable
+  the WSS full-duplex operation which currently works with Crystal
+  CS423x chips. If you don't need full-duplex operation, do not enable
   it to save performance.
 
 Sound card modem support for 1200 baud AFSK modulation
@@ -5026,7 +5779,7 @@
   can only use one protocol at a time, depending on what the other end
   can understand).
 
-CCITT X.25 Packet Layer (EXPERIMENTAL)
+CCITT X.25 Packet Layer
 CONFIG_X25
   X.25 is a set of standardized network protocols, similar in scope to
   frame relay; the one physical line from your box to the X.25 network
@@ -5037,13 +5790,13 @@
   countries have public X.25 networks. X.25 consists of two
   protocols: the higher level Packet Layer Protocol (PLP) (say Y here
   if you want that) and the lower level data link layer protocol LAPB
-  (say Y to "LAPB Data Link Driver" below if you want that). 
+  (say Y to "LAPB Data Link Driver" below if you want that).
 
-  You can read more about X.25 at http://www.sangoma.com/x25.htm and
-  http://www.cisco.com/univercd/data/doc/software/11_0/rpcg/cx25.htm .
+  You can read more about X.25 at <http://www.sangoma.com/x25.htm> and
+  <http://www.cisco.com/univercd/data/doc/software/11_0/rpcg/cx25.htm>.
   Information about X.25 for Linux is contained in the files
-  Documentation/networking/x25.txt and
-  Documentation/networking/x25-iface.txt.
+  <file:Documentation/networking/x25.txt> and
+  <file:Documentation/networking/x25-iface.txt>.
 
   One connects to an X.25 network either with a dedicated network card
   using the X.21 protocol (not yet supported by Linux) or one can do
@@ -5051,14 +5804,14 @@
   to "X.25 async driver" below) or over Ethernet using an ordinary
   Ethernet card and either the 802.2 LLC protocol (say Y to "802.2
   LLC" below) or LAPB over Ethernet (say Y to "LAPB Data Link Driver"
-  and "LAPB over Ethernet driver" below). 
+  and "LAPB over Ethernet driver" below).
 
   If you want to compile this driver as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt. The module will be
-  called x25.o. If unsure, say N.
+  say M here and read <file:Documentation/modules.txt>.  The module
+  will be called x25.o. If unsure, say N.
 
-LAPB Data Link Driver (EXPERIMENTAL) 
+LAPB Data Link Driver
 CONFIG_LAPB
   Link Access Procedure, Balanced (LAPB) is the data link layer (i.e.
   the lower) part of the X.25 protocol. It offers a reliable
@@ -5069,41 +5822,42 @@
   currently supports LAPB only over Ethernet connections. If you want
   to use LAPB connections over Ethernet, say Y here and to "LAPB over
   Ethernet driver" below. Read
-  Documentation/networking/lapb-module.txt for technical details.
+  <file:Documentation/networking/lapb-module.txt> for technical
+  details.
 
   If you want to compile this driver as a module though ( = code which
   can be inserted in and removed from the running kernel whenever you
-  want), say M here and read Documentation/modules.txt. The module
-  will be called lapb.o. If unsure, say N.
+  want), say M here and read <file:Documentation/modules.txt>.  The
+  module will be called lapb.o.  If unsure, say N.
 
-802.2 LLC (EXPERIMENTAL)
+802.2 LLC
 CONFIG_LLC
   This is a Logical Link Layer protocol used for X.25 connections over
-  Ethernet, using ordinary Ethernet cards. 
+  Ethernet, using ordinary Ethernet cards.
 
-
-Frame Diverter (EXPERIMENTAL)
+Frame Diverter
 CONFIG_NET_DIVERT
   The Frame Diverter allows you to divert packets from the
-  network, that are not aimed at the interface receiving it (in 
-  promisc. mode). Typically, a Linux box setup as an ethernet bridge
-  with the Frames Diverter on, can do some *really* transparent www 
+  network, that are not aimed at the interface receiving it (in
+  promisc. mode). Typically, a Linux box setup as an Ethernet bridge
+  with the Frames Diverter on, can do some *really* transparent www
   caching using a Squid proxy for example.
 
   This is very useful when you don't want to change your router's
   config (or if you simply don't have access to it).
 
-  The other possible usages of diverting Ethernet Frames are numberous:
+  The other possible usages of diverting Ethernet Frames are
+  numberous:
    - reroute smtp traffic to another interface
    - traffic-shape certain network streams
    - transparently proxy smtp connections
    - etc...
 
   For more informations, please refer to:
-    http://www.freshmeat.net/projects/etherdivert
-    http://perso.wanadoo.fr/magpie/EtherDivert.html
+    <http://www.freshmeat.net/projects/etherdivert>
+    <http://perso.wanadoo.fr/magpie/EtherDivert.html>
 
-  If unsure, say N
+  If unsure, say N.
 
 802.1d Ethernet Bridging
 CONFIG_BRIDGE
@@ -5113,21 +5867,22 @@
   Several such bridges can work together to create even larger
   networks of Ethernets using the IEEE 802.1 spanning tree algorithm.
   As this is a standard, Linux bridges will cooperate properly with
-  other third party bridge products. 
+  other third party bridge products.
+
+  In order to use the Ethernet bridge, you'll need the bridge
+  configuration tools; see <file:Documentation/networking/bridge.txt>
+  for location. Please read the Bridge mini-HOWTO for more
+  information.
 
-  In order to use the ethernet bridge, you'll need the bridge
-  configuration tools; see Documentation/networking/bridge.txt for
-  location. Please read the Bridge mini-HOWTO for more information.
-  
   Note that if your box acts as a bridge, it probably contains several
   Ethernet devices, but the kernel is not able to recognize more than
   one at boot time without help; for details read the Ethernet-HOWTO,
-  available from in http://www.linuxdoc.org/docs.html#howto .
+  available from in <http://www.linuxdoc.org/docs.html#howto>.
 
   If you want to compile this code as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt. The module will be
-  called bridge.o.
+  say M here and read <file:Documentation/modules.txt>.  The module
+  will be called bridge.o.
 
   If unsure, say N.
 
@@ -5135,15 +5890,15 @@
 CONFIG_PACKET
   The Packet protocol is used by applications which communicate
   directly with network devices without an intermediate network
-  protocol implemented in the kernel, e.g. tcpdump. If you want them
-  to work, choose Y. 
+  protocol implemented in the kernel, e.g. tcpdump.  If you want them
+  to work, choose Y.
 
   This driver is also available as a module called af_packet.o ( =
   code which can be inserted in and removed from the running kernel
-  whenever you want). If you want to compile it as a module, say M
-  here and read Documentation/modules.txt; if you use modprobe or
-  kmod, you may also want to add "alias net-pf-17 af_packet" to 
-  /etc/modules.conf. 
+  whenever you want).  If you want to compile it as a module, say M
+  here and read <file:Documentation/modules.txt>; if you use modprobe
+  or kmod, you may also want to add "alias net-pf-17 af_packet" to
+  /etc/modules.conf.
 
   If unsure, say Y.
 
@@ -5157,17 +5912,17 @@
 Kernel/User network link driver
 CONFIG_NETLINK
   This driver allows for two-way communication between the kernel and
-  user processes. It does so by creating a new socket family, PF_NETLINK.
-  Over this socket, the kernel can send and receive datagrams carrying
-  information. It is documented on many systems in netlink(7), a HOWTO is
-  provided as well, for example on
-  http://snafu.freedom.org/linux2.2/docs/netlink-HOWTO.html
+  user processes.  It does so by creating a new socket family,
+  PF_NETLINK.  Over this socket, the kernel can send and receive
+  datagrams carrying information.  It is documented on many systems in
+  netlink(7), a HOWTO is provided as well, for example on
+  <http://snafu.freedom.org/linux2.2/docs/netlink-HOWTO.html>.
 
   So far, the kernel uses this feature to publish some network related
   information if you say Y to "Routing messages", below. You also need
   to say Y here if you want to use arpd, a daemon that helps keep the
   internal ARP cache (a mapping between IP addresses and hardware
-  addresses on the local network) small. The ethertap device, which
+  addresses on the local network) small.  The ethertap device, which
   lets user space programs read and write raw Ethernet frames, also
   needs the network link driver.
 
@@ -5177,7 +5932,7 @@
 CONFIG_RTNETLINK
   If you say Y here, user space programs can receive some network
   related routing information over the netlink. 'rtmon', supplied
-  with the iproute2 package (ftp://ftp.inr.ac.ru), can read and
+  with the iproute2 package (<ftp://ftp.inr.ac.ru>), can read and
   interpret this data.  Information sent to the kernel over this link
   is ignored.
 
@@ -5192,17 +5947,17 @@
 Asynchronous Transfer Mode (ATM)
 CONFIG_ATM
   ATM is a high-speed networking technology for Local Area Networks
-  and Wide Area Networks. It uses a fixed packet size and is
+  and Wide Area Networks.  It uses a fixed packet size and is
   connection oriented, allowing for the negotiation of minimum
   bandwidth requirements.
-  
+
   In order to participate in an ATM network, your Linux box needs an
   ATM networking card. If you have that, say Y here and to the driver
   of your ATM card below.
 
   Note that you need a set of user-space programs to actually make use
-  of ATM. See the file Documentation/networking/atm.txt for further
-  details.
+  of ATM.  See the file <file:Documentation/networking/atm.txt> for
+  further details.
 
 Classical IP over ATM
 CONFIG_ATM_CLIP
@@ -5247,9 +6002,9 @@
   The driver works with MMF (-MF or ...F) and UTP-5 (-U5 or ...D)
   adapters.
 
-  This driver is also available as a module. If you want to compile
-  it as a module, say M here and read Documentation/modules.txt. The
-  module will be called eni.o.
+  This driver is also available as a module.  If you want to compile
+  it as a module, say M here and read
+  <file:Documentation/modules.txt>.  The module will be called eni.o.
 
 Enable extended debugging
 CONFIG_ATM_ENI_DEBUG
@@ -5296,7 +6051,7 @@
   Burst four words at once in the send direction. You may want to try
   this if you have disabled 8W bursts. Enabling 4W if 8W is also set
   may or may not improve throughput.
-  
+
 Enable 2W TX bursts (optional)
 CONFIG_ATM_ENI_BURST_TX_2W
   Burst two words at once in the send direction. You may want to try
@@ -5331,9 +6086,9 @@
   Driver for the ZeitNet ZN1221 (MMF) and ZN1225 (UTP-5) 155 Mbps ATM
   adapters.
 
-  This driver is also available as a module. If you want to compile
-  it as a module, say M here and read Documentation/modules.txt. The
-  module will be called zatm.o.
+  This driver is also available as a module.  If you want to compile
+  it as a module, say M here and read
+  <file:Documentation/modules.txt>.  The module will be called zatm.o.
 
 Enable extended debugging
 CONFIG_ATM_ZATM_DEBUG
@@ -5345,12 +6100,13 @@
 
 Fujitsu FireStream (FS50/FS155)
 CONFIG_ATM_FIRESTREAM
-  Driver for the Fujitsu FireStream 155 (MB86697) and 
+  Driver for the Fujitsu FireStream 155 (MB86697) and
   FireStream 50 (MB86695) ATM PCI chips.
 
-  This driver is also available as a module. If you want to compile
-  it as a module, say M here and read Documentation/modules.txt. The
-  module will be called firestream.o.
+  This driver is also available as a module.  If you want to compile
+  it as a module, say M here and read
+  <file:Documentation/modules.txt>.  The module will be called
+  firestream.o.
 
 Enable usec resolution timestamps
 CONFIG_ATM_ZATM_EXACT_TS
@@ -5368,21 +6124,22 @@
   25 and for 155 Mbps, including IDT cards and the Fore ForeRunnerLE
   series. Say Y if you have one of those.
 
-  This driver is also available as a module. If you want to compile
-  it as a module, say M here and read Documentation/modules.txt. The
-  module will be called nicstar.o.
+  This driver is also available as a module.  If you want to compile
+  it as a module, say M here and read
+  <file:Documentation/modules.txt>. The module will be called
+  nicstar.o.
 
-ForeRunner LE155 PHYsical layer
+Use suni PHY driver (155Mbps)
 CONFIG_ATM_NICSTAR_USE_SUNI
   Support for the S-UNI and compatible PHYsical layer chips. These are
   found in most 155Mbps NICStAR based ATM cards, namely in the
-  ForeRunner LE155 cards. This driver provides detection of cable
+  ForeRunner LE155 cards. This driver provides detection of cable~
   removal and reinsertion and provides some statistics. This driver
   doesn't have removal capability when compiled as a module, so if you
   need that capability don't include S-UNI support (it's not needed to
   make the card work).
 
-ForeRunner LE25 PHYsical layer
+Use IDT77015 PHY driver (25Mbps)
 CONFIG_ATM_NICSTAR_USE_IDT77105
   Support for the PHYsical layer chip in ForeRunner LE25 cards. In
   addition to cable removal/reinsertion detection, this driver allows
@@ -5390,6 +6147,31 @@
   This driver is required for proper handling of temporary carrier
   loss, so if you have a 25Mbps NICStAR based ATM card you must say Y.
 
+IDT 77252 (NICStAR II)
+CONFIG_ATM_IDT77252
+  Driver for the IDT 77252 ATM PCI chips.
+
+  This driver is also available as a module.  If you want to compile
+  it as a module, say M here and read
+  <file:Documentation/modules.txt>. The module will be called idt77252.o
+
+Enable debugging messages
+CONFIG_ATM_IDT77252_DEBUG
+  Somewhat useful debugging messages are available. The choice of
+  messages is controlled by a bitmap.  This may be specified as a
+  module argument.  See the file <file:drivers/atm/idt77252.h> for
+  the meanings of the bits in the mask.
+
+  When active, these messages can have a significant impact on the
+  speed of the driver, and the size of your syslog files! When
+  inactive, they will have only a modest impact on performance.
+
+Receive ALL cells in raw queue
+CONFIG_ATM_IDT77252_RCV_ALL
+  Enable receiving of all cells on the ATM link, that do not match
+  an open connection in the raw cell queue of the driver.  Useful
+  for debugging or special applications only, so the safe answer is N.
+
 Madge Ambassador (Collage PCI 155 Server)
 CONFIG_ATM_AMBASSADOR
   This is a driver for ATMizer based ATM card produced by Madge
@@ -5399,11 +6181,12 @@
 Enable debugging messages
 CONFIG_ATM_AMBASSADOR_DEBUG
   Somewhat useful debugging messages are available. The choice of
-  messages is controlled by a bitmap. This may be specified as a
+  messages is controlled by a bitmap.  This may be specified as a
   module argument (kernel command line argument as well?), changed
   dynamically using an ioctl (not yet) or changed by sending the
-  string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
-  drivers/atm/ambassador.h for the meanings of the bits in the mask.
+  string "Dxxxx" to VCI 1023 (where x is a hex digit).  See the file
+  <file:drivers/atm/ambassador.h> for the meanings of the bits in the
+  mask.
 
   When active, these messages can have a significant impact on the
   speed of the driver, and the size of your syslog files! When
@@ -5418,28 +6201,29 @@
 Enable debugging messages
 CONFIG_ATM_HORIZON_DEBUG
   Somewhat useful debugging messages are available. The choice of
-  messages is controlled by a bitmap. This may be specified as a
+  messages is controlled by a bitmap.  This may be specified as a
   module argument (kernel command line argument as well?), changed
   dynamically using an ioctl (not yet) or changed by sending the
-  string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
-  drivers/atm/horizon.h for the meanings of the bits in the mask.
+  string "Dxxxx" to VCI 1023 (where x is a hex digit).  See the file
+  <file:drivers/atm/horizon.h> for the meanings of the bits in the
+  mask.
 
   When active, these messages can have a significant impact on the
   speed of the driver, and the size of your syslog files! When
   inactive, they will have only a modest impact on performance.
 
-Interphase ATM PCI x575/x525/x531 
+Interphase ATM PCI x575/x525/x531
 CONFIG_ATM_IA
   This is a driver for the Interphase (i)ChipSAR adapter cards
-  which include a variety of variants in term of the size of the 
-  control memory (128K-1KVC, 512K-4KVC), the size of the packet 
-  memory (128K, 512K, 1M), and the PHY type (Single/Multi mode OC3, 
+  which include a variety of variants in term of the size of the
+  control memory (128K-1KVC, 512K-4KVC), the size of the packet
+  memory (128K, 512K, 1M), and the PHY type (Single/Multi mode OC3,
   UTP155, UTP25, DS3 and E3). Go to:
   	www.iphase.com/products/ClassSheet.cfm?ClassID=ATM
-  for more info about the cards. Say Y (or M to compile as a module 
+  for more info about the cards. Say Y (or M to compile as a module
   named iphase.o) here if you have one of these cards.
 
-  See the file Documentation/networking/iphase.txt for further
+  See the file <file:Documentation/networking/iphase.txt> for further
   details.
 
 Enable debugging messages
@@ -5447,9 +6231,11 @@
   Somewhat useful debugging messages are available. The choice of
   messages is controlled by a bitmap. This may be specified as a
   module argument (kernel command line argument as well?), changed
-  dynamically using an ioctl (Get the debug utility, iadbg, from 
-  ftp.iphase.com/pub/atm/pci). See the file drivers/atm/iphase.h 
-  for the meanings of the bits in the mask.
+  dynamically using an ioctl (Get the debug utility, iadbg, from
+  <ftp://ftp.iphase.com/pub/atm/pci>).
+
+  See the file <file:drivers/atm/iphase.h> for the meanings of the
+  bits in the mask.
 
   When active, these messages can have a significant impact on the
   speed of the driver, and the size of your syslog files! When
@@ -5458,36 +6244,37 @@
 Linux telephony support
 CONFIG_PHONE
   Say Y here if you have a telephony card, which for example allows
-  you to use a regular phone for voice-over-IP applications. 
+  you to use a regular phone for voice-over-IP applications.
 
-  Note: this has nothing to do with modems. You do not need to say Y
+  Note: this has nothing to do with modems.  You do not need to say Y
   here in order to be able to use a modem under Linux.
 
-  This support is also available as a module. If you want to compile
-  it as a module, say M here and read Documentation/modules.txt. The
-  module will be called phonedev.o.
+  This support is also available as a module.  If you want to compile
+  it as a module, say M here and read
+  <file:Documentation/modules.txt>.  The module will be called
+  phonedev.o.
 
 Compaq Smart Array support
 CONFIG_BLK_CPQ_CISS_DA
-   This is the driver for Compaq Smart Array 5xxx controllers.
-   Everyone using these boards should say Y here.
-   See Documentation/cciss.txt for the current list of
-   boards supported by this driver, and for further information
-   on the use of this driver.
+  This is the driver for Compaq Smart Array 5xxx controllers.
+  Everyone using these boards should say Y here.
+  See <file:Documentation/cciss.txt> for the current list of
+  boards supported by this driver, and for further information
+  on the use of this driver.
 
 QuickNet Internet LineJack/PhoneJack support
 CONFIG_PHONE_IXJ
   Say M if you have a telephony card manufactured by Quicknet
   Technologies, Inc.  These include the Internet PhoneJACK and
   Internet LineJACK Telephony Cards. You will get a module called
-  ixj.o. 
+  ixj.o.
 
   For the ISA versions of these products, you can configure the
   cards using the isapnp tools (pnpdump/isapnp) or you can use the
-  isapnp support.  Please read Documentation/telephony/ixj.txt.
+  isapnp support.  Please read <file:Documentation/telephony/ixj.txt>.
 
   For more information on these cards, see Quicknet's web site at:
-  http://www.quicknet.net/ .
+  <http://www.quicknet.net/>.
 
   If you do not have any Quicknet telephony cards, you can safely
   say N here.
@@ -5498,66 +6285,66 @@
   cards. It simultaneously supports PCA-200E and SBA-200E models
   on PCI and SBUS hosts. Say Y (or M to compile as a module
   named fore_200e.o) here if you have one of these ATM adapters.
- 
+
   Note that the driver will actually be compiled only if you
   additionally enable the support for PCA-200E and/or SBA-200E
   cards.
 
-  See the file Documentation/networking/fore200e.txt for further
-  details.
- 
+  See the file <file:Documentation/networking/fore200e.txt> for
+  further details.
+
 Enable PCA-200E card support on PCI-based hosts
 CONFIG_ATM_FORE200E_PCA
   Say Y here if you want your PCA-200E cards to be probed.
- 
+
 Use default PCA-200E firmware
 CONFIG_ATM_FORE200E_PCA_DEFAULT_FW
   Use the default PCA-200E firmware data shipped with the driver.
- 
+
   Normal users do not have to deal with the firmware stuff, so
   they should say Y here.
- 
+
 Pathname of user-supplied binary firmware
 CONFIG_ATM_FORE200E_PCA_FW
   This defines the pathname of an alternative PCA-200E binary
   firmware image supplied by the user. This pathname may be
   absolute or relative to the drivers/atm directory.
- 
+
   The driver comes with an adequate firmware image, so normal users do
   not have to supply an alternative one. They just say Y to "Use
   default PCA-200E firmware" instead.
- 
+
 Enable SBA-200E card support on SBUS-based hosts
 CONFIG_ATM_FORE200E_SBA
   Say Y here if you want your SBA-200E cards to be probed.
- 
+
 Use default SBA-200E firmware
 CONFIG_ATM_FORE200E_SBA_DEFAULT_FW
   Use the default SBA-200E firmware data shipped with the driver.
- 
+
   Normal users do not have to deal with the firmware stuff, so
   they should say Y here.
- 
+
 Pathname of user-supplied binary firmware
 CONFIG_ATM_FORE200E_SBA_FW
   This defines the pathname of an alternative SBA-200E binary
   firmware image supplied by the user. This pathname may be
   absolute or relative to the drivers/atm directory.
- 
+
   The driver comes with an adequate firmware image, so normal users do
   not have to supply an alternative one. They just say Y to "Use
   default SBA-200E firmware", above.
- 
+
 Maximum number of tx retries
 CONFIG_ATM_FORE200E_TX_RETRY
   Specifies the number of times the driver attempts to transmit
   a message before giving up, if the transmit queue of the ATM card
   is transiently saturated.
- 
+
   Saturation of the transmit queue may occur only under extreme
   conditions, e.g. when a fast host continuously submits very small
   frames (<64 bytes) or raw AAL0 cells (48 bytes) to the ATM adapter.
- 
+
   Note that under common conditions, it is unlikely that you encounter
   a saturation of the transmit queue, so the retry mechanism never
   comes into play.
@@ -5567,54 +6354,168 @@
   Specifies the level of debugging messages issued by the driver.
   The verbosity of the driver increases with the value of this
   parameter.
- 
+
   When active, these messages can have a significant impact on
   the performances of the driver, and the size of your syslog files!
   Keep the debugging level to 0 during normal operations.
 
-SCSI support?
+Fusion MPT device support
+CONFIG_FUSION
+  LSI Logic Fusion(TM) Message Passing Technology (MPT) device support
+  provides high performance SCSI host initiator, and LAN [1] interface
+  services to a host system.  The Fusion architecture is capable of
+  duplexing these protocols on high-speed Fibre Channel
+  (up to 2 GHz x 2 ports = 4 GHz) and parallel SCSI (up to Ultra-320)
+  physical medium.
+
+          [1] LAN is not supported on parallel SCSI medium.
+
+  These drivers require a Fusion MPT compatible PCI adapter installed
+  in the host system.  MPT adapters contain specialized I/O processors
+  to handle I/O workload, and more importantly to offload this work
+  from the host CPU(s).
+
+  If you have Fusion MPT hardware and want to use it, you can say
+  Y or M here to add MPT (base + ScsiHost) drivers.
+    <Y> = build lib (fusion.o), and link [static] into the kernel [2]
+          proper
+    <M> = compiled as [dynamic] modules [3] named: (mptbase.o,
+          mptscsih.o)
+
+          [2] In order enable capability to boot the linux kernel
+              natively from a Fusion MPT target device, you MUST
+               answer Y here! (currently requires CONFIG_BLK_DEV_SD)
+          [3] This support is also available as a module ( = code
+              which can be inserted in and removed from the running
+              kernel whenever you want).  If you want to compile as
+              modules, say M here and read
+              <file:Documentation/modules.txt>.
+
+  If unsure, say N.
+
+  If you say Y or M here you will get a choice of these
+  additional protocol and support module options:         Module Name:
+    <M>   Enhanced SCSI error reporting                     (isense.o)
+    <M>   Fusion MPT misc device (ioctl) driver             (mptctl.o)
+    <M>   Fusion MPT LAN driver                             (mptlan.o)
+
+  ---
+  Fusion MPT is trademark of LSI Logic Corporation, and its
+  architecture is based on LSI Logic's Message Passing Interface (MPI)
+  specification.
+
+Fusion MPT enhanced SCSI error reporting [optional] module
+CONFIG_FUSION_ISENSE
+  The isense module (roughly stands for Interpret SENSE data) is
+  completely optional.  It simply provides extra English readable
+  strings in SCSI Error Report(s) that might be generated from the
+  Fusion MPT SCSI Host driver, for example when a target device
+  returns a SCSI check condition on a I/O.  Without this module
+  loaded you might see:
+
+    SCSI Error Report =-=-= (ioc0,scsi5:0)
+      SCSI_Status=02h (CHECK_CONDITION)
+      Original_CDB[]: 2A 00 00 00 00 41 00 00 02 00
+      SenseData[12h]: 70 00 02 00 00 00 00 0A 00 00 00 00 04 02 02 00 00 00
+      SenseKey=2h (NOT READY); FRU=02h
+      ASC/ASCQ=29h/00h
+
+  Where otherwise, if this module had been loaded, you would see:
+
+    SCSI Error Report =-=-= (ioc0,scsi5:0)
+      SCSI_Status=02h (CHECK_CONDITION)
+      Original_CDB[]: 2A 00 00 00 00 41 00 00 02 00 - "WRITE(10)"
+      SenseData[12h]: 70 00 02 00 00 00 00 0A 00 00 00 00 04 02 02 00 00 00
+      SenseKey=2h (NOT READY); FRU=02h
+      ASC/ASCQ=29h/00h "LOGICAL UNIT NOT READY, INITIALIZING CMD. REQUIRED"
+
+  Say M for "Enhanced SCSI error reporting" to compile this optional module,
+  creating a driver named: isense.o.
+
+  NOTE: Support for building this feature into the kernel is not
+  available, due to kernel size considerations.
+
+Fusion MPT misc device (ioctl) driver [optional] module
+CONFIG_FUSION_CTL
+  The Fusion MPT misc device driver provides specialized control
+  of MPT adapters via system ioctl calls.  Use of ioctl calls to
+  the MPT driver requires that you create and use a misc device
+  node ala:
+    mknod /dev/mptctl c 10 240
+
+  One use of this ioctl interface is to perform an upgrade (reflash)
+  of the MPT adapter firmware.  Refer to readme file(s) distributed
+  with the Fusion MPT linux driver for additional details.
+
+  If enabled by saying M to this, a driver named: mptctl.o
+  will be compiled.
+
+  If unsure whether you really want or need this, say N.
+
+Fusion MPT LAN driver [optional]
+CONFIG_FUSION_LAN
+  This module supports LAN IP traffic over Fibre Channel port(s)
+  on Fusion MPT compatible hardware (LSIFC9xx chips).
+  The physical interface used is defined in RFC 2625.
+  Please refer to that document for details.
+
+  Installing this driver requires the knowledge to configure and
+  activate a new network interface, "fc0", using standard Linux tools.
+
+  If enabled by saying M to this, a driver named: mptlan.o
+  will be compiled.
+
+  If unsure whether you really want or need this, say N.
+
+  NOTES: This feature is NOT available nor supported for linux-2.2.x
+  kernels.  You must be building a linux-2.3.x or linux-2.4.x kernel
+  in order to configure this option.
+  Support for building this feature into the linux kernel is not
+  yet available.
+
+SCSI support
 CONFIG_SCSI
-  If you want to use a SCSI hard disk, SCSI tape drive, SCSI CDROM or
+  If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
   any other SCSI device under Linux, say Y and make sure that you know
   the name of your SCSI host adapter (the card inside your computer
   that "speaks" the SCSI protocol, also called SCSI controller),
-  because you will be asked for it. 
+  because you will be asked for it.
 
   You also need to say Y here if you want support for the parallel
   port version of the 100 MB IOMEGA ZIP drive.
 
   Please read the SCSI-HOWTO, available from
-  http://www.linuxdoc.org/docs.html#howto . The
+  <http://www.linuxdoc.org/docs.html#howto>. The
   SCSI-Programming-HOWTO contains information about how to add or
   remove an SCSI device from a running Linux machine without
   rebooting.
 
   This driver is also available as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want).
-  The module will be called scsi_mod.o. If you want to compile it as a
-  module, say M here and read Documentation/modules.txt and
-  Documentation/scsi.txt. However, do not compile this as a module if
-  your root file system (the one containing the directory /) is
-  located on a SCSI device.
+  The module will be called scsi_mod.o.  If you want to compile it as
+  a module, say M here and read <file:Documentation/modules.txt> and
+  <file:Documentation/scsi.txt>.  However, do not compile this as a
+  module if your root file system (the one containing the directory /)
+  is located on a SCSI device.
 
 SCSI disk support
 CONFIG_BLK_DEV_SD
   If you want to use a SCSI hard disk or the SCSI or parallel port
   version of the IOMEGA ZIP drive under Linux, say Y and read the
   SCSI-HOWTO, the Disk-HOWTO and the Multi-Disk-HOWTO, available from
-  http://www.linuxdoc.org/docs.html#howto . This is NOT for SCSI
-  CDROMs.
+  <http://www.linuxdoc.org/docs.html#howto>. This is NOT for SCSI
+  CD-ROMs.
 
   This driver is also available as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want).
-  The module will be called sd_mod.o. If you want to compile it as a
-  module, say M here and read Documentation/modules.txt and
-  Documentation/scsi.txt. Do not compile this driver as a module if
-  your root file system (the one containing the directory /) is
-  located on a SCSI disk. In this case, do not compile the driver for
-  your SCSI host adapter (below) as a module either.
+  The module will be called sd_mod.o.  If you want to compile it as a
+  module, say M here and read <file:Documentation/modules.txt> and
+  <file:Documentation/scsi.txt>.  Do not compile this driver as a
+  module if your root file system (the one containing the directory /)
+  is located on a SCSI disk. In this case, do not compile the driver
+  for your SCSI host adapter (below) as a module either.
 
-Extra SCSI Disks
+Maximum number of SCSI disks that can be loaded as modules
 CONFIG_SD_EXTRA_DEVS
   This controls the amount of additional space allocated in tables for
   drivers that are loaded as modules after the kernel is booted.  In
@@ -5628,63 +6529,76 @@
 
   If you don't understand what's going on, go with the default.
 
+Maximum number of SCSI tapes that can be loaded as modules
+CONFIG_ST_EXTRA_DEVS
+  This controls the amount of additional space allocated in tables for
+  drivers that are loaded as modules after the kernel is booted.  In
+  the event that the SCSI core itself was loaded as a module, this
+  value is the number of additional tapes that can be loaded after the
+  first host driver is loaded.
+
+  Admittedly this isn't pretty, but there are tons of race conditions
+  involved with resizing the internal arrays on the fly.  Someday this
+  flag will go away, and everything will work automatically.
+
+  If you don't understand what's going on, go with the default.
+
 SCSI tape support
 CONFIG_CHR_DEV_ST
   If you want to use a SCSI tape drive under Linux, say Y and read the
   SCSI-HOWTO, available from
-  http://www.linuxdoc.org/docs.html#howto , and
-  drivers/scsi/README.st in the kernel source. This is NOT for SCSI
-  CDROMs.
+  <http://www.linuxdoc.org/docs.html#howto>, and
+  <file:drivers/scsi/README.st> in the kernel source.  This is NOT for
+  SCSI CD-ROMs.
 
   This driver is also available as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want).
   The module will be called st.o. If you want to compile it as a
-  module, say M here and read Documentation/modules.txt and
-  Documentation/scsi.txt .
+  module, say M here and read <file:Documentation/modules.txt> and
+  <file:Documentation/scsi.txt>.
 
 OnStream SC-x0 SCSI tape support
 CONFIG_CHR_DEV_OSST
-  The OnStream SC-x0 SCSI tape drives can not be driven by the 
-  standard st driver, but instead need this special osst driver and 
-  use the  /dev/osstX char device nodes (major 206).
-  Via usb-storage and ide-scsi, you may be able to drive the USB-x0 
-  and DI-x0 drives as well. Note that there is also a second generation
-  of OnStream tape drives (ADR-x0) that supports the standard SCSI-2
-  commands for tapes (QIC-157) and can be driven by the standard
-  driver st.
+  The OnStream SC-x0 SCSI tape drives can not be driven by the
+  standard st driver, but instead need this special osst driver and
+  use the  /dev/osstX char device nodes (major 206).  Via usb-storage
+  and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives
+  as well.  Note that there is also a second generation of OnStream
+  tape drives (ADR-x0) that supports the standard SCSI-2 commands for
+  tapes (QIC-157) and can be driven by the standard driver st.
   For more information, you may have a look at the SCSI-HOWTO
-  ftp://metalab.unc.edu/pub/Linux/docs/HOWTO  and
-  drivers/scsi/README.osst  in the kernel source. 
-  More info on the OnStream driver may be found on 
-  http://linux1.onstream.nl/test/
+  <ftp://metalab.unc.edu/pub/Linux/docs/HOWTO>  and
+  <file:drivers/scsi/README.osst>  in the kernel source.
+  More info on the OnStream driver may be found on
+  <http://linux1.onstream.nl/test/>
   Please also have a look at the standard st docu, as most of it
   applies to osst as well.
 
   This driver is also available as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want).
   The module will be called osst.o. If you want to compile it as a
-  module, say M here and read Documentation/modules.txt and
-  Documentation/scsi.txt .
+  module, say M here and read <file:Documentation/modules.txt> and
+  <file:Documentation/scsi.txt>.
 
-SCSI CDROM support
+SCSI CD-ROM support
 CONFIG_BLK_DEV_SR
-  If you want to use a SCSI CDROM under Linux, say Y and read the
-  SCSI-HOWTO and the CDROM-HOWTO at
-  http://www.linuxdoc.org/docs.html#howto . Also make sure to say Y
-  or M to "ISO 9660 CDROM file system support" later.
+  If you want to use a SCSI CD-ROM under Linux, say Y and read the
+  SCSI-HOWTO and the CD-ROM-HOWTO at
+  <http://www.linuxdoc.org/docs.html#howto>. Also make sure to say Y
+  or M to "ISO 9660 CD-ROM file system support" later.
 
   This driver is also available as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want).
   The module will be called sr_mod.o. If you want to compile it as a
-  module, say M here and read Documentation/modules.txt and
-  Documentation/scsi.txt .
+  module, say M here and read <file:Documentation/modules.txt> and
+  <file:Documentation/scsi.txt>.
 
-Extra SCSI CDROMs
+Maximum number of CD-ROM devices that can be loaded as modules
 CONFIG_SR_EXTRA_DEVS
   This controls the amount of additional space allocated in tables for
   drivers that are loaded as modules after the kernel is booted. In
   the event that the SCSI core itself was loaded as a module, this
-  value is the number of additional CDROMs that can be loaded after
+  value is the number of additional CD-ROMs that can be loaded after
   the first host driver is loaded.
 
   Admittedly this isn't pretty, but there are tons of race conditions
@@ -5693,7 +6607,7 @@
 
   If you don't understand what's going on, go with the default.
 
-Enable vendor-specific extensions (for SCSI CDROM)
+Enable vendor-specific extensions (for SCSI CD-ROM)
 CONFIG_BLK_DEV_SR_VENDOR
   This enables the usage of vendor specific SCSI commands. This is
   required to support multisession CDs with old NEC/TOSHIBA cdrom
@@ -5704,27 +6618,27 @@
 CONFIG_CHR_DEV_SG
   If you want to use SCSI scanners, synthesizers or CD-writers or just
   about anything having "SCSI" in its name other than hard disks,
-  CDROMs or tapes, say Y here. These won't be supported by the kernel
+  CD-ROMs or tapes, say Y here. These won't be supported by the kernel
   directly, so you need some additional software which knows how to
   talk to these devices using the SCSI protocol:
 
-  For scanners, look at SANE (http://www.mostang.com/sane). For CD
+  For scanners, look at SANE (<http://www.mostang.com/sane>). For CD
   writer software look at cdrecord
-  (http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html)
+  (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
   and for burning a "disk at once": cdrdao
-  (http://www.ping.de/sites/daneb/cdrdao.html). Cdparanoia is a high
-  quality digital reader of audio CDs (http://www.xiph.org/paranoia).
+  (<http://www.ping.de/sites/daneb/cdrdao.html>). Cdparanoia is a high
+  quality digital reader of audio CDs (<http://www.xiph.org/paranoia>).
   For other devices, it's possible that you'll have to write the
   driver software yourself. Please read the file
-  Documentation/scsi-generic.txt for more information.
+  <file:Documentation/scsi-generic.txt> for more information.
 
   If you want to compile this as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
-  say M here and read Documentation/modules.txt and
-  Documentation/scsi.txt. The module will be called sg.o. If unsure,
+  say M here and read <file:Documentation/modules.txt> and
+  <file:Documentation/scsi.txt>. The module will be called sg.o. If unsure,
   say N.
 
-Debug new queueing code for SCSI
+Enable extra checks in SCSI queueing code
 CONFIG_SCSI_DEBUG_QUEUES
   This option turns on a lot of additional consistency checking for
   the new queueing code. This will adversely affect ology (MPT)this p@@
   If you wish to= code which.""0[85)ere s graphics boa