Linux Cross Reference
Linux/Documentation/Configure.help

   # Maintained by Axel Boldt (axel@uni-paderborn.de)
   #
   # This version of the Linux kernel configuration help texts
   # corresponds to the kernel versions 2.3.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/
  #   - Italian, by Alessandro Rubini (rubini@linux.it), at
  #     ftp://ftp-pavia1.linux.it/pub/linux/Configure.help
  #   - 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
  #     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 
  # 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
  # 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
  # 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'
  # kfill.el to edit and ispell.el to spell check this file or you lose.
  #
  # 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 
  # information should go in a README in the Documentation directory.
  # Mention all the relevant READMEs and HOWTOs in the help text.
  # Repetitions are fine since the help texts are not meant to be read
  # in sequence.
  #
  # All this was shamelessly stolen from several different sources. Many
  # thanks to all the contributors. Feel free to use these help texts in
  # your own kernel configuration tools. The texts are copyrighted (c)
  # 1995-2000 by Axel Boldt and many others and are governed by the GNU
  # General Public License.
  
  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 
    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 
    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). 
  
    This option will also make obsoleted drivers available. These are
    drivers that have been replaced by something else, and/or are
    scheduled to be removed in a future kernel release.
  
    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
    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
  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
    you have a system with more than one CPU, say Y.
  
   If you say N here, the kernel will run on single and multiprocessor
   machines, but will use only one CPU of a multiprocessor machine. If
   you say Y here, the kernel will run on many, but not all,
   singleprocessor machines. On a singleprocessor machine, the kernel
   will run faster if you say N here.
 
   Note that if you say Y here and choose architecture "586" or
   "Pentium" under "Processor family", the kernel will not work on 486
   architectures. Similarly, multiprocessor kernels for the "PPro"
   architecture may not work on all Pentium based boards.
 
   People using multiprocessor machines who say Y here should also say
   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/ .
   
   If you don't know what to do here, say N.
   
 APIC and IO-APIC Support on Uniprocessors
 CONFIG_X86_UP_IOAPIC
   APIC (Advanced Programmable Interrupt Controller) is a scheme for
   delivering hardware interrupt requests to the CPU. It is commonly
   used on systems with several CPU's. If you have a single-CPU system
   which uses APIC, you can say Y here to use it. If you say Y here
   even though your machine doesn't have APIC, then the kernel will
   still run with no slowdown at all.
 
   If you have system with several CPU's, you do not need to say Y
   here: APIC will be used automatically.
 
 Kernel math emulation
 CONFIG_MATH_EMULATION
   Linux can emulate a math coprocessor (used for floating point
   operations) if you don't have one. 486DX and Pentium processors have
   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. 
 
   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
   be used nevertheless. (This behavior can be changed with the kernel
   command line option "no387", which comes handy if your coprocessor
   is broken. 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.) This means that it is a good idea to say Y here if you
   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.
 
   If you are not sure, say Y; apart from resulting in a 66 KB bigger
   kernel, it won't hurt.
 
 Timer and CPU usage LEDs
 CONFIG_LEDS
   If you say Y here, the LEDs on your machine will be used
   to provide useful information about your current system status.
 
   If you are compiling a kernel for a NetWinder or EBSA-285, you will
   be able to select which LEDs are active using the options below. If
   you are compiling a kernel for the EBSA-110 or the LART however, the
   red LED will simply flash regularly to indicate that the system is
   still functional. It is safe to say Y here if you have a CATS
   system, but the driver will do nothing.
 
 Timer LED
 CONFIG_LEDS_TIMER
   If you say Y here, one of the system LEDs (the green one on the
   NetWinder, the amber one on the EBSA285, or the red one on the LART)
   will flash regularly to indicate that the system is still
   operational. This is mainly useful to kernel hackers who are
   debugging unstable kernels.
 
   The LART uses the same LED for both Timer LED and CPU usage LED
   functions. You may choose to use both, but the Timer LED function
   will overrule the CPU usage LED.
 
 CPU usage LED
 CONFIG_LEDS_CPU
   If you say Y here, the red LED will be used to give a good real
   time indication of CPU usage, by lighting whenever the idle task
   is not currently executing.
 
   The LART uses the same LED for both Timer LED and CPU usage LED
   functions. You may choose to use both, but the Timer LED function
   will overrule the CPU usage LED.
 
 Kernel FP software completion (EXPERIMENTAL)
 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.
 
 High Memory support
 CONFIG_NOHIGHMEM
   Linux can use up to 64 Gigabytes of physical memory on x86 systems.
   However, the address space of 32-bit x86 processors is only 4
   Gigabytes large. That means that, if you have a large amount of
   physical memory, not all of it can be "permanently mapped" by the
   kernel. The physical memory that's not permanently mapped is called
   "high memory".
 
   If you are compiling a kernel which will never run on a machine with
   more than 1 Gigabyte total physical RAM, answer "off" here (default
   choice and suitable for most users). This will result in a "3GB/1GB"
   split: 3GB are mapped so that each process sees a 3GB virtual memory
   space and the remaining part of the 4GB virtual memory space is used
   by the kernel to permanently map as much physical memory as
   possible.
 
   If the machine has between 1 and 4 Gigabytes physical RAM, then
   answer "4GB" here.
 
   If more than 4 Gigabytes is used then answer "64GB" here. This
   selection turns Intel PAE (Physical Address Extension) mode on.
   PAE implements 3-level paging on IA32 processors. PAE is fully
   supported by Linux, PAE mode is implemented on all recent Intel
   processors (Pentium Pro and better). NOTE: If you say "64GB" here,
   then the kernel will not boot on CPUs that don't support PAE!
 
   The actual amount of total physical memory will either be
   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.) 
 
   If unsure, say "off".
 
 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
   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.
 
 Support for PowerMac floppy
 CONFIG_MAC_FLOPPY
   If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
   floppy controller, say Y here. Most commonly found in PowerMacs.
 
 RAM disk support
 CONFIG_BLK_DEV_RAM
   Saying Y here will allow you to use a portion of your RAM memory as
   a block device, so that you can make file systems on it, read and
   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. 
 
   Note that the kernel command line option "ramdisk=XX" is now
   obsolete. For details, read 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. 
 
   Most normal users won't need the RAM disk functionality, and can
   thus say N here.
 
 Initial RAM disk (initrd) support
 CONFIG_BLK_DEV_INITRD
   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.
 
 Loop 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
   are block special device files with major number 7 and typically
   called /dev/loop0, /dev/loop1 etc.
 
   This is useful if you want to check an ISO 9660 file system before
   burning the CD, or if you want to use floppy images without first
   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. 
 
   The loop device driver can also be used to "hide" a file system in a
   disk partition, floppy, or regular file, either using encryption
   (scrambling the data) or steganography (hiding the data in the low
   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
   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
   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/ .
 
   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.
 
   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.
 
   Most users will answer N here.
 
 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. 
 
   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.
 
   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.
 
   If unsure, say N.
 
 ATA/IDE/MFM/RLL support
 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.
 
   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.
 
   Fast-IDE is ATA-2 (also named Fast ATA), Enhanced IDE (EIDE) is
   ATA-3. It provides support for larger disks (up to 8.4GB by means of
   the LBA standard), more disks (4 instead of 2) and for other mass
   storage units such as tapes and cdrom. UDMA/33 (aka UltraDMA/33) is
   ATA-4 and provides faster (and more CPU friendly) transfer modes
   than previous PIO (Programmed processor Input/Output) from previous
   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.
   
   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.
 
   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.
 
   For further information, please read Documentation/ide.txt.
 
   If unsure, say Y.
 
 Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
 CONFIG_BLK_DEV_IDE
   If you say Y here, you will use the full-featured IDE driver to
   control up to ten ATA/IDE interfaces, each being able to serve a
   "master" and a "slave" device, for a total of up to twenty ATA/IDE
   disk/cdrom/tape/floppy drives.
 
   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
   information about hard drives, consult the Disk-HOWTO and the
   Multi-Disk-HOWTO, available from
   http://www.linuxdoc.org/docs.html#howto .
 
   To fine-tune ATA/IDE drive/interface parameters for improved
   performance, look for the hdparm package at
   ftp://metalab.unc.edu/pub/Linux/kernel/patches/diskdrives/ .
 
   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.
 
   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
   could say N here, and select the "Old hard disk driver" below
   instead to save about 13 KB of memory in the kernel.
 
 Old hard disk (MFM/RLL/IDE) driver
 CONFIG_BLK_DEV_HD_ONLY
   There are two drivers for MFM/RLL/IDE hard disks. Most people use
   the newer enhanced driver, but this old one is still around for two
   reasons. Some older systems have strange timing problems and seem to
   work only with the old driver (which itself does not work with some
   newer systems). The other reason is that the old driver is smaller,
   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. 
 
   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 .
 
 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
   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
   which have MFM/RLL/ESDI controller+drives at the primary port
   address (0x1f0), along with IDE drives at the secondary/3rd/4th port
   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
   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
   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.
 
 Use multi-mode by default
 CONFIG_IDEDISK_MULTI_MODE
   If you get this error, try to say Y here:
 
   hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
   hda: set_multmode: error=0x04 { DriveStatusError }
 
   If in doubt, say N.
 
 Include IDE/ATAPI CDROM 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
   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
   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".
 
   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 .
 
   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.
 
 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.
 
   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
   SC-30 and SC-50 versions.
 
   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.
 
   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.
 
 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. 
 
   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 .
   (ATAPI PD-CD/CDR drives are not supported by this driver; support
   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
   other IDE devices, as "hdb" or "hdc", or something similar (check
   the boot messages with dmesg).
 
   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.
 
 SCSI emulation support
 CONFIG_BLK_DEV_IDESCSI
   This will provide SCSI host adapter emulation for IDE ATAPI devices,
   and will allow you to use a SCSI device driver instead of a native
   ATAPI driver.
 
   This is useful if you have an ATAPI device for which no native
   driver has been written (for example, an ATAPI PD-CD or CDR drive);
   you can then use this emulation together with an appropriate SCSI
   device driver. In order to do this, say Y here and to "SCSI support"
   and "SCSI generic support", below. You must then provide the kernel
   command line "hdx=scsi" (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) for devices if you want the
   native EIDE sub-drivers to skip over the native support, so that
   this SCSI emulation can be used instead. This is required for use of
   CD-RW's.
 
   Note that this option does NOT allow you to attach SCSI devices to a
   box that doesn't have a SCSI host adapter installed.
 
   If both this SCSI emulation and native ATAPI support are compiled
   into the kernel, the native support will be used.
 
 ISA-PNP EIDE support
 CONFIG_BLK_DEV_ISAPNP
   If you have an ISA EIDE card that is PnP (Plug and Play) and
   requires setup first before scanning for devices, say Y here.
 
   If unsure, say N.
 
 CMD640 chipset bugfix/support
 CONFIG_BLK_DEV_CMD640
   The CMD-Technologies CMD640 IDE chip is used on many common 486 and
   Pentium motherboards, usually in combination with a "Neptune" or
   "SiS" chipset. Unfortunately, it has a number of rather nasty
   design flaws that can cause severe data corruption under many common
   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. 
 
   This driver will work automatically in PCI based systems (most new
   systems have PCI slots). But if your system uses VESA local bus
   (VLB) instead of PCI, you must also supply a kernel boot parameter
   to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man
   bootparam" or see the documentation of your boot loader about how to
   pass options to the kernel.)
 
   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. 
 
 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.
 
 RZ1000 chipset bugfix/support
 CONFIG_BLK_DEV_RZ1000
   The PC-Technologies RZ1000 IDE chip is used on many common 486 and
   Pentium motherboards, usually along with the "Neptune" chipset.
   Unfortunately, it has a rather nasty design flaw that can cause
   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. 
 
 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
   sharing a single IRQ with other cards. To enable support for
   this in the ATA/IDE driver, say Y here.
 
   It is safe to say Y to this question, in most cases.
   If unsure, say N.
 
 Generic PCI bus-master DMA support
 CONFIG_BLK_DEV_IDEDMA_PCI
   If your PCI system uses IDE drive(s) (as opposed to SCSI, say) and
   is capable of bus-master DMA operation (most Pentium PCI systems),
   you will want to say Y here to reduce CPU overhead. You can then use
   the "hdparm" utility to enable DMA for drives for which it was not
   enabled automatically. By default, DMA is not enabled automatically
   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/ .
 
   Read the comments at the beginning of drivers/ide/ide-dma.c and
   the file Documentation/ide.txt for more information.
 
   It is safe to say Y to this question.
 
 Good-Bad DMA Model-Firmware (EXPERIMENTAL)
 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
   be (U)DMA capable but aren't. This is a blanket on/off test with no
   speed limit options.
 
   Straight GNU GCC 2.7.3/2.8.X compilers are known to be safe;
   whereas, many versions of EGCS have a problem and miscompile if you
   say Y here.
 
   If in doubt, say N.
 
 Boot off-board chipsets first support
 CONFIG_BLK_DEV_OFFBOARD
   Normally, IDE controllers built into the motherboard (on-board
   controllers) are assigned to ide0 and ide1 while those on add-in PCI
   cards (off-board controllers) are relegated to ide2 and ide3.
   Answering Y here will allow you to reverse the situation, with
   off-board controllers on ide0/1 and on-board controllers on ide2/3.
   This can improve the usability of some boot managers such as lilo
   when booting from a drive on an off-board controller.
 
   If you say Y here, and you actually want to reverse the device scan
   order as explained above, you also need to issue the kernel command
   line option "ide=reverse". (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.)
 
   Note that, if you do this, the order of the hd* devices will be
   rearranged which may require modification of fstab and other files.
 
   If in doubt, say N.
 
 Use 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
   about a couple of cases where buggy hardware may have caused damage,
   the default is now to NOT use DMA automatically. To revert to the
   previous behaviour, say Y to this question.
 
   If you suspect your hardware is at all flakey, say N here.
   Do NOT email the IDE kernel people regarding this issue!
 
   It is normally safe to answer Y to this question unless your
   motherboard uses a VIA VP2 chipset, in which case you should say N.
 
 IGNORE word93 Validation BITS
 CONFIG_IDEDMA_IVB
   Since various rules were applied and created ... et al. as it relates
   the detection of vaild 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)
 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
   simply skip those options.
 
   It is SAFEST to say N to this question.
 
 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/
 
   Please read the comments at the top of drivers/scsi/3w-xxxx.c  
 
 AEC62XX chipset support
 CONFIG_BLK_DEV_AEC62XX
   This driver adds up to 4 more EIDE devices sharing a single
   interrupt. This add-on card is a bootable PCI UDMA controller. In
   order to get this card to initialize correctly in some cases, you
   should say Y here, and preferably also to "Use DMA by default when
   available".
 
   The ATP850U/UF is an UltraDMA 33 chipset base.
   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.
 
 AEC62XX Tuning support
 CONFIG_AEC62XX_TUNING
   Please read the comments at the top of drivers/ide/aec62xx.c  
   If unsure, say N.
 
 ALI M15x3 chipset support
 CONFIG_BLK_DEV_ALI15X3
   This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C
   onboard chipsets.  It also tests for Simplex mode and enables
   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
 
   If unsure, say N.
 
 ALI M15x3 WDC support (DANGEROUS)
 CONFIG_WDC_ALI15X3
   This allows for UltraDMA support for WDC drives that ignore CRC
   checking. You are a fool for enabling this option, but there have
   been requests. DO NOT COMPLAIN IF YOUR DRIVE HAS FS CORRUPTION, IF
   YOU ENABLE THIS! No one will listen, just laugh for ignoring this
   SERIOUS WARNING.
 
   Using this option can allow WDC drives to run at ATA-4/5 transfer
   rates with only an ATA-2 support structure.
 
   SAY NO!
 
 AMD7409 chipset support
 CONFIG_BLK_DEV_AMD7409
   This driver ensures (U)DMA support for the AMD756 Viper chipset.
 
   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
 
   If unsure, say N.
 
 AMD Viper ATA-66 Override support (WIP)
 CONFIG_AMD7409_OVERRIDE
   This option auto-forces the ata66 flag.
   This effect can be also invoked by calling "idex=ata66"
   If unsure, say N.
 
 CMD64X chipset support
 CONFIG_BLK_DEV_CMD64X
   Say Y here if you have an IDE controller which uses any of these
   chipsets: CMD643, CMD646, or CMD648.
 
 CY82C693 chipset support
 CONFIG_BLK_DEV_CY82C693
   This driver adds detection and support for the CY82C693 chipset
   used on Digital's PC-Alpha 164SX boards.
 
   If you say Y here, you need to say Y to "Use DMA by default
   when available" as well.
 
 Cyrix CS5530 MediaGX chipset support
 CONFIG_BLK_DEV_CS5530
   Include support for UDMA on the Cyrix MediaGX 5530 chipset. This
   will automatically be detected and configured if found.
 
   It is safe to say Y to this question.
 
   People with SCSI-only systems should say N here. If unsure, say Y.
 
 HPT34X chipset support
 CONFIG_BLK_DEV_HPT34X
   This driver adds up to 4 more EIDE devices sharing a single
   interrupt. The HPT343 chipset in its current form is a non-bootable
   controller; the HPT345/HPT363 chipset is a bootable (needs BIOS FIX)
   PCI UDMA controllers. This driver requires dynamic tuning of the
   chipset during the ide-probe at boot time. It is reported to support
   DVD II drives, by the manufacturer.
 
 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.
 
   If unsure, say N.
 
 HPT366 chipset support
 CONFIG_BLK_DEV_HPT366
   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. 
 
   The HPT366 chipset in its current form is bootable. One solution
   for this problem are special LILO commands for redirecting the
   reference to device 0x80. The other solution is to say Y to "Boot
   off-board chipsets first support" (CONFIG_BLK_DEV_OFFBOARD) unless
   your mother board has the chipset natively mounted. Regardless one
   should use the fore mentioned option and call at LILO or include
   "ide=reverse" in LILO's append-line.
 
   This driver requires dynamic tuning of the chipset during the
   ide-probe at boot. It is reported to support DVD II drives, by the
   manufacturer.
 
 NS87415 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.
 
 OPTi 82C621 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.
 
 ServerWorks OSB4 chipset support (EXPERIMENTAL)
 CONFIG_BLK_DEV_OSB4
   This driver adds PIO/DMA support for the Serverworks OSB4 chipset
 
 Intel PIIXn chipsets support
 CONFIG_BLK_DEV_PIIX
   This driver adds PIO mode setting and tuning for all PIIX IDE
   controllers by Intel.  Since the BIOS can sometimes improperly tune
   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.
 
   If you say Y here, you should also say Y to "PIIXn Tuning support",
   below.
 
   If unsure, say N.
 
 PIIXn Tuning support
 CONFIG_PIIX_TUNING
   This driver extension adds DMA mode setting and tuning for all PIIX
   IDE controllers by Intel. Since the BIOS can sometimes improperly
   set up the device/adapter combination and speed limits, it has
   become a necessity to back/forward speed devices as needed.
 
   Case 430HX/440FX PIIX3 need speed limits to reduce UDMA to DMA mode
   2 if the BIOS can not perform this task at initialization.
 
   If unsure, say N.
 
 PROMISE PDC20246/PDC20262/PDC20267 support
 CONFIG_BLK_DEV_PDC202XX
   Promise Ultra33 or PDC20246
   Promise Ultra66 or PDC20262
   Promise Ultra100 or PDC20265/PDC20267
 
   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
   for more than one card. This card may require that you say Y to
   "Special UDMA Feature (EXPERIMENTAL)".
 
   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
 
   If unsure, say N.
 
 Special UDMA Feature (EXPERIMENTAL)
 CONFIG_PDC202XX_BURST
   For PDC20246, PDC20262, PDC20265 and PDC20267 Ultra DMA chipsets.
   Designed originally for PDC20246/Ultra33 that has BIOS setup
   failures when using 3 or more cards.
 
   Unknown for PDC20265/PDC20267 Ultra DMA 100.
 
   Please read the comments at the top of drivers/ide/pdc202xx.c
 
   If unsure, say N.
 
 SiS5513 chipset support
 CONFIG_BLK_DEV_SIS5513
   This driver ensures (U)DMA support for SIS5513 chipset based
   mainboards. SiS620/530 UDMA mode 4, SiS5600/5597 UDMA mode 2, all
   other DMA mode 2 limited chipsets are unsupported to date.
 
   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
 
 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.
 
   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
 
 Winbond SL82c105 support
 CONFIG_BLK_DEV_SL82C105
   If you have a Winbond SL82c105 IDE controller, say Y here to enable
   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)
 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.
 
 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.
 
   Please read the comments at the top of 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.
 
 Other IDE chipset support
 CONFIG_IDE_CHIPSETS
   Say Y here if you want to include enhanced support for various IDE
   interface chipsets used on motherboards and add-on cards. You can
   then pick your particular IDE chip from among the following options.
   This enhanced support may be necessary for Linux to be able to
   access the 3rd/4th drives in some systems. It may also enable
   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. 
 
 Generic 4 drives/port support
 CONFIG_BLK_DEV_4DRIVES
   Certain older chipsets, including the Tekram 690CD, use a single set
   of I/O ports at 0x1f0 to control up to four drives, instead of the
   customary two drives per port. Support for this can be enabled at
   runtime using the "ide0=four" kernel boot parameter if you say Y
   here.
 
 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
   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.
 
 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.
 
 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.
 
 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
   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.
 
 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.
 
 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.
 
 Amiga builtin 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)
   and `A4000 style' (used in A4000 and A4000T) of the Gayle IDE
   interface. Say Y if you have such an Amiga model and want to use IDE
   devices (hard disks, CD-ROM drives, etc.) that are connected to the
   builtin IDE interface.
 
 Falcon IDE interface support
 CONFIG_BLK_DEV_FALCON_IDE
   This is the IDE driver for the builtin IDE interface on the Atari
   Falcon. Say Y if you have a Falcon and want to use IDE devices (hard
   disks, CD-ROM drives, etc.) that are connected to the builtin IDE
   interface.
 
 Amiga Buddha/Catweasel 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.
 
   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
   to one of its IDE interfaces.
 
 Amiga IDE Doubler support (EXPERIMENTAL)
 CONFIG_BLK_DEV_IDEDOUBLER
   This driver provides support for the so-called `IDE doublers' (made
   by various manufacturers, e.g. Eyetech) that can be connected to the
   builtin IDE interface of some Amiga models. Using such an IDE
   doubler, you can connect up to four instead of two IDE devices on
   the Amiga's builtin IDE interface.
 
   Note that the normal Amiga Gayle IDE driver may not work correctly
   if you have an IDE doubler and don't enable this driver!
 
   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)
 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.
   If unsure, say Y.
 
 PowerMac IDE DMA support
 CONFIG_BLK_DEV_IDEDMA_PMAC
   This option allows the driver for the built-in IDE controller on
   Power Macintoshes and PowerBooks to use DMA (direct memory access)
   to transfer data to and from memory.  Saying Y is safe and improves
   performance.
 
 Use DMA by default
 CONFIG_BLK_DEV_IDEDMA_PMAC_AUTO
   This option allows the driver for the built-in IDE controller on
   Power Macintoshes and PowerBooks to use DMA automatically, without
   it having to be explicitly enabled.  This option is provided because
   of concerns about a couple of cases where using DMA on buggy PC
   hardware may have caused damage.  Saying Y should be safe on all
   Apple machines.
 
 Macintosh Quadra/Powerbook IDE interface support
 CONFIG_BLK_DEV_MAC_IDE
   This is the IDE driver for the builtin IDE interface on some m68k
   Macintosh models. It supports both the `Quadra style' (used in
   Quadra/ Centris 630 and Performa 588 models) and `Powerbook style'
   (used in the Powerbook 150 and 190 models) IDE interface.
 
   Say Y if you have such an Macintosh model and want to use IDE
   devices (hard disks, CD-ROM drives, etc.) that are connected to the
   builtin IDE interface.
 
 ICS IDE interface support
 CONFIG_BLK_DEV_IDE_ICSIDE
   On Acorn systems, say Y here if you wish to use the ICS IDE
   interface card.  This is not required for ICS partition support.
   If you are unsure, say N to this.
 
 ICS DMA support
 CONFIG_BLK_DEV_IDEDMA_ICS
   Say Y here if you want to add DMA (Direct Memory Access) support to
   the ICS IDE driver.
 
 Use ICS DMA by default
 CONFIG_IDEDMA_ICS_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
   about a couple of cases where buggy hardware may have caused damage,
   the default is now to NOT use DMA automatically. To revert to the
   previous behaviour, say Y to this question.
 
   If you suspect your hardware is at all flakey, say N here.
   Do NOT email the IDE kernel people regarding this issue!
 
 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. 
 
   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. 
 
   It's pretty unlikely that you have one of these: say N.
 
 PS/2 ESDI hard disk support
 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.
 
 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.
 
   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. 
 
 Parallel port IDE device support
 CONFIG_PARIDE
   There are many external CD-ROM and disk devices that connect through
   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.
 
   If you have said Y to the "Parallel-port support" configuration
   option, you may share a single port between your printer and other
   parallel port devices. Answer Y to build PARIDE support into your
   kernel, or M if you would like to build it as a loadable module. If
   your parallel port support is in a loadable module, you must build
   PARIDE as a module. If you built PARIDE support into your kernel,
   you may still build the individual protocol modules and high-level
   drivers as loadable modules. If you build this support as a module,
   it will be called paride.o.
 
   To use the PARIDE support, you must say Y or M here and also to at
   least one high-level driver (e.g. "Parallel port IDE disks",
   "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
   to at least one protocol driver (e.g. "ATEN EH-100 protocol",
   "MicroSolutions backpack protocol", "DataStor Commuter protocol"
   etc.).
 
 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 
   EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack
   hard drives from MicroSolutions.
 
 Parallel port ATAPI CD-ROMs
 CONFIG_PARIDE_PCD
   This option enables the high-level driver for ATAPI CD-ROM 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 ATAPI CD-ROM driver, otherwise you should answer M to
   build it as a loadable module. The module will be called pcd.o. You
   must also have at least one parallel port protocol driver in your
   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.
 
 Parallel port ATAPI disks
 CONFIG_PARIDE_PF
   This option enables the high-level driver for ATAPI 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 ATAPI disk driver, otherwise you should answer M
   to build it as a loadable module. The module will be called pf.o.
   You must also have at least one parallel port protocol driver in
   your system. Among the devices supported by this driver are the
   MicroSolutions backpack PD/CD drive and the Imation Superdisk
   LS-120 drive.
 
 Parallel port ATAPI tapes
 CONFIG_PARIDE_PT
   This option enables the high-level driver for ATAPI tape 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 ATAPI disk driver, otherwise you should answer M
   to build it as a loadable module. The module will be called pt.o.
   You must also have at least one parallel port protocol driver in
   your system. Among the devices supported by this driver is the
   parallel port version of the HP 5GB drive.
 
 Parallel port generic ATAPI devices
 CONFIG_PARIDE_PG
   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. 
 
   If you chose to build PARIDE support into your kernel, you may
   answer Y here to build in the parallel port generic ATAPI driver,
   otherwise you should answer M to build it as a loadable module. The
   module will be called pg.o.
 
   You must also have at least one parallel port protocol driver in
   your system.
 
   This driver implements an API loosely related to the generic SCSI
   driver. See 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
   later fully support this driver.
 
 ATEN EH-100 protocol
 CONFIG_PARIDE_ATEN
   This option enables support for the ATEN EH-100 parallel port IDE
   protocol. This protocol is used in some inexpensive low performance
   parallel port kits made in Hong Kong. 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 aten.o. You must also
   have a high-level driver for the type of device that you want to
   support.
 
 MicroSolutions backpack protocol
 CONFIG_PARIDE_BPCK
   This option enables support for the MicroSolutions backpack parallel
   port IDE protocol. 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.
 
 DataStor Commuter protocol
 CONFIG_PARIDE_COMM
   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
   module. The module will be called comm.o. You must also have
   a high-level driver for the type of device that you want to support.
 
 DataStor EP-2000 protocol
 CONFIG_PARIDE_DSTR
   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
   module. The module will be called dstr.o. You must also have
   a high-level driver for the type of device that you want to support.
 
 Shuttle EPAT/EPEZ protocol
 CONFIG_PARIDE_EPAT
   This option enables support for the EPAT parallel port IDE protocol.
   EPAT is a parallel port IDE adapter manufactured by Shuttle
   Technology and widely used in devices from major vendors such as
   Hewlett-Packard, SyQuest, Imation and Avatar. 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 epat.o. You must also
   have a high-level driver for the type of device that you want to
   support.
 
 Shuttle EPIA protocol
 CONFIG_PARIDE_EPIA
   This option enables support for the (obsolete) EPIA parallel port
   IDE protocol from Shuttle Technology. This adapter can still be
   found in some no-name kits. 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 epia.o. You must also have a
   high-level driver for the type of device that you want to support.
 
 FIT TD-2000 protocol
 CONFIG_PARIDE_FIT2
   This option enables support for the TD-2000 parallel port IDE
   protocol from Fidelity International Technology. This is a simple
   (low speed) adapter that is used in some portable hard drives. 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 ktti.o.
   You must also have a high-level driver for the type of device that
   you want to support.
 
 FIT TD-3000 protocol
 CONFIG_PARIDE_FIT3
   This option enables support for the TD-3000 parallel port IDE
   protocol from Fidelity International Technology. This protocol is
   used in newer models of their portable disk, CD-ROM and PD/CD
   devices. 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 fit3.o. You must also have a high-level driver for the type
   of device that you want to support.
 
 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 
   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. 
 
 FreeCom power protocol
 CONFIG_PARIDE_FRPW
   This option enables support for the Freecom power parallel port IDE
   protocol. 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 frpw.o. You must also have a high-level driver for the type
   of device that you want to support.
 
 KingByte KBIC-951A/971A protocols
 CONFIG_PARIDE_KBIC
   This option enables support for the KBIC-951A and KBIC-971A parallel
   port IDE protocols from KingByte Information Corp. KingByte's
   adapters appear in many no-name portable disk and CD-ROM products,
   especially in Europe. 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 kbic.o. You must also have a high-level driver
   for the type of device that you want to support.
 
 KT PHd protocol
 CONFIG_PARIDE_KTTI
   This option enables support for the "PHd" parallel port IDE protocol
   from KT Technology. This is a simple (low speed) adapter that is
   used in some 2.5" portable hard drives. 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 ktti.o. You must also
   have a high-level driver for the type of device that you want to
   support.
 
 OnSpec 90c20 protocol
 CONFIG_PARIDE_ON20
   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 
   type of device that you want to support.
 
 OnSpec 90c26 protocol
 CONFIG_PARIDE_ON26
   This option enables support for the 90c26 parallel port IDE protocol
   from OnSpec Electronics (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 on26.o. You must also have a high-level driver for the type
   of device that you want to support.
 
 Logical Volume Manager (LVM) support
 CONFIG_BLK_DEV_LVM
   This driver lets you combine several hard disks, hard disk
   partitions, multiple devices or even loop devices (for evaluation
   purposes) into a volume group.  Imagine a volume group as a kind of
   virtual disk. Logical volumes, which can be thought of as virtual
   partitions, can be created in the volume group.  You can resize
   volume groups and logical volumes after creation time, corresponding
   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.
 
   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.
 
 Logical Volume Manager /proc file system information
 CONFIG_LVM_PROC_FS
   If you say Y here, you are able to access overall Logical Volume
   Manager, Volume Group, Logical and Physical Volume information in
   /proc/lvm.
 
   To use this option, you have to check, that the "/proc file system
   support" (CONFIG_PROC_FS) is enabled too.
 
 Multiple devices driver support
 CONFIG_BLK_DEV_MD
   This driver lets you combine several hard disk partitions into one
   logical block device. This can be used to simply append one
   partition to another one or to combine several redundant hard disks
   into a RAID1/4/5 device so as to provide protection against hard
   disk failures. This is called "Software RAID" since the combining of
   the partitions is done by the kernel. "Hardware RAID" means that the
   combining is done by a dedicated controller; if you have such a
   controller, you do not need to say Y here.
 
   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
   learn where to get the supporting user space utilities raidtools.
 
   If unsure, say N.
 
 Linear (append) mode
 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. 
 
   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.
 
   If unsure, say Y.
 
 RAID-0 (striping) mode
 CONFIG_MD_RAID0
   If you say Y here, then your multiple devices driver will be able to
   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. 
 
   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
   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.
 
   If unsure, say Y.
 
 RAID-1/RAID-5 code (DANGEROUS)
 CONFIG_RAID15_DANGEROUS
   This new RAID1/RAID5 code has been freshly merged, and has not seen
   enough testing yet. While there are no known bugs in it, it might
   destroy your filesystems, eat your data and start World War III.
   You have been warned.
 
   If unsure, say N.
 
 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
   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
   of a single drive, and the set protects against a failure of (N - 1)
   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
   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
   want to compile it as a module, say M here and read
   Documentation/modules.txt.
 
   If unsure, say Y.
 
 RAID-4/RAID-5 mode
 CONFIG_MD_RAID5
   A RAID-5 set of N drives with a capacity of C MB per drive provides
   the capacity of C * (N - 1) MB, and protects against a failure
   of a single drive. For a given sector (row) number, (N - 1) drives
   contain data sectors, and one drive contains the parity protection.
   For a RAID-4 set, the parity blocks are present on a single drive,
   while a RAID-5 set distributes the parity across the drives in one
   of the available parity distribution methods.
 
   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
   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.
 
   If unsure, say Y.
 
 RAID Boot support
 CONFIG_MD_BOOT
   To boot with an initial raid volume (any type) you can select
   autodetect, or answer Y here and appropriate options to the kernel
   at boot time.
   For lilo and loadlin options see the file Documentation/md.txt.
 
 RAID AutoDetect support
 CONFIG_AUTODETECT_RAID
   An alternative to "Raid Boot support" is autodetect support.
   With this selected, any partitons of type 0xFD will be considered for
   inclusion in a RAID array.  Information in the RAID-superblock on
   the partition will determine how it is included.
 
 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 .
 
 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 .
 
 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 .
 
 Support for Cobalt Microserver
 CONFIG_COBALT_MICRO_SERVER
   This enables support for the Cobalt Microserver.  For more information
   see the Linux/MIPS FAQ on http://oss.sgi.com/mips .
 
 Support for 2800
 CONFIG_COBALT_28
   This adds support for the Cobalt Microserver 2800.  A kernel with this
   option selected will only work on the 2800.
 
 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 .
 
   If you have one of the following DECstation Models you definitely
   want to choose R4xx0 for the CPU Type:
 
         DECstation 5000/50
         DECstation 5000/150
         DECstation 5000/260
         DECsystem 5900/260
 
   otherwise choose R3000.
 
 Support for NEC DDB Vrc-5074
 CONFIG_DDB5074
   This enables support for the VR5000-based NEC DDB Vrc-5074
   evaluation board.
 
 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.
 
 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.
 
 Support for SGI IP22
 CONFIG_SGI_IP22
   This are the SGI Indy, Challenge S and Indigo2, as well as certain
   OEM variants like the Tandem CMN B006S. To compile a Linux kernel
   that runs on these, say Y here.
 
 Support for 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.
 
 IP27 N-Mode
 CONFIG_SGI_SN0_N_MODE
   The nodes of Origin 200, Origin 2000 and Onyx 2 systems can be
   configured in either N-Modes which allows for more nodes or M-Mode
   which allows for more more memory.  Your system is most probably
   running in M-Mode, so you should say N here.
 
 MIPS JAZZ onboard SONIC Ethernet support
 CONFIG_MIPS_JAZZ_SONIC
   This is the driver for the onboard card of of MIPS Magnum 4000,
   Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
 
 MIPS JAZZ FAS216 SCSI support
 CONFIG_JAZZ_ESP
   This is the driver for the onboard SCSI host adapter of MIPS Magnum
   4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
   systems.
 
 PCMCIA SCSI adapter support
 CONFIG_SCSI_PCMCIA
   Say Y here if you intend to attach a PCMCIA or CardBus card to your
   computer which acts as a SCSI host adapter. These are credit card
   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
   the questions PCMCIA SCSI host adapters.
 
 Adaptec AHA152X PCMCIA support
 CONFIG_PCMCIA_AHA152X
   Say Y here if you intend to attach this type of PCMCIA SCSI host
   adapter to your computer.
 
   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.
 
 Qlogic PCMCIA support
 CONFIG_PCMCIA_QLOGIC
   Say Y here if you intend to attach this type of PCMCIA SCSI host
   adapter to your computer.
 
   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.
 
 Future Domain PCMCIA support
 CONFIG_PCMCIA_FDOMAIN
   Say Y here if you intend to attach this type of PCMCIA SCSI host
   adapter to your computer.
 
   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.
 
 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.
 
 Support for large 64-bit configurations
 CONFIG_MIPS_INSANE_LARGE
   MIPS R10000 does support a 44 bit / 16TB address space as opposed to
   previous 64-bit processors which only supported 40 bit / 1TB. If you
   need processes of more than 1TB virtual address space, say Y here.
   This will result in additional memory usage, so it is not
   recommended for normal users.
 
 Generate little endian code
 CONFIG_CPU_LITTLE_ENDIAN
   Some MIPS machines can be configured for either little or big endian
   byte order. These modes require different kernels. Say Y if your
   machine is little endian, N if it's a big endian machine.
 
 Networking support
 CONFIG_NET
   Unless you really know what you are doing, you should say Y here.
   The reason is that some programs need kernel networking support even
   when running on a stand-alone machine that isn't connected to any
   other computer. If you are upgrading from an older kernel, you
   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.
 
   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 .
 
 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.
   If unsure, say N.
 
 Network packet filtering
 CONFIG_NETFILTER
   Netfilter is a framework for filtering and mangling network packets
   that pass through your Linux box.
 
   The most common use of packet filtering is to run your Linux box as
   a firewall protecting a local network from the Internet. The type of
   firewall provided by this kernel support is called a "packet
   filter", which means that it can reject individual network packets
   based on type, source, destination etc. The other kind of firewall,
   a "proxy-based" one, is more secure but more intrusive and more
   bothersome to set up; it inspects the network traffic much more
   closely, modifies it and has knowledge about the higher level
   protocols, which a packet filter lacks. Moreover, proxy-based
   firewalls often require changes to the programs running on the local
   clients. Proxy-based firewalls don't need support by the kernel, but
   they are often combined with a packet filter, which only works if
   you say Y here.
 
   You should also say Y here if you intend to use your Linux box as
   the gateway to the Internet for a local network of machines without
   globally valid IP addresses. This is called "masquerading": if one
   of the computers on your local network wants to send something to
   the outside, your box can "masquerade" as that computer, i.e. it
   forwards the traffic to the intended outside destination, but
   modifies the packets to make it look like they came from the
   firewall box itself. It works both ways: if the outside host
   replies, the Linux box will silently forward the traffic to the
   correct local computer. This way, the computers on your local net
   are completely invisible to the outside world, even though they can
   reach the outside and can receive replies. It is even possible to
   run globally visible servers from within a masqueraded local network
   using a mechanism called portforwarding. Masquerading is also often
   called NAT (Network Address Translation).
 
   Another use of Netfilter is in transparent proxying: if a machine on
   the local network tries to connect to an outside host, your Linux
   box can transparently forward the traffic to a local server,
   typically a caching proxy server.
 
   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.
  
   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. 
 
 IP: 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
   into connections.
 
   This is required to do Masquerading or other kinds of Network
   Address Translation (except for Fast NAT).  It can also be used to
   enhance packet filtering (see `Connection state match support'
   below).
 
   If you want to compile it as a module, say M here and read
   Documentation/modules.txt.  If unsure, say `N'.
 
 FTP protocol support
 CONFIG_IP_NF_FTP
   Tracking FTP connections is problematic: special helpers are
   required for tracking them, and doing masquerading and other forms
   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'.
 
 IP: user space queueing via NETLINK (EXPERIMENTAL)
 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'.
 
 IP: 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,
   etc) subsystems now use this: 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'.
 
 limit match support
 CONFIG_IP_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_IP_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_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'.
 
 Multiple port match support
 CONFIG_IP_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'.
 
 TOS match support
 CONFIG_IP_NF_MATCH_TOS
   TOS matching allows you to match packets based on the Type Of
   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'.
 
 Connection state match support
 CONFIG_IP_NF_MATCH_STATE
   Connection state matching allows you to match packets based on their
   relationship to a tracked connection (ie. previous packets).  This
   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'.
 
 Unclean match support (EXPERIMENTAL)
 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'.
 
 Owner match support (EXPERIMENTAL)
 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'.
 
 Packet filtering
 CONFIG_IP_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'.
 
 REJECT target support
 CONFIG_IP_NF_TARGET_REJECT
   The REJECT target allows a filtering rule to specify that an ICMP
   error should be issued in response to an incoming packet, rather
   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'.
 
 MIRROR target support (EXPERIMENTAL)
 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'.
 
 Full NAT
 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'.
 
 MASQUERADE target support
 CONFIG_IP_NF_TARGET_MASQUERADE
   Masquerading is a special case of NAT: all outgoing connections are
   changed to seem to come from a particular interface's address, and
   if the interface goes down, those connections are lost.  This is
   only useful for dialup accounts with dynamic IP address (ie. your IP
   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'.
 
 REDIRECT target support
 CONFIG_IP_NF_TARGET_REDIRECT
   REDIRECT is a special case of NAT: all incoming connections are
   mapped onto the incoming interface's address, causing the packets to
   come to the local machine instead of passing through.  This is
   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'.
 
 Packet mangling
 CONFIG_IP_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'.
 
 TOS target support
 CONFIG_IP_NF_TARGET_TOS
   This option adds a `TOS' target, which allows you to create rules in
   the `mangle' table which alter the Type Of Service field of an IP
   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'.
 
 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
   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'.
 
 LOG target support
 CONFIG_IP_NF_TARGET_LOG
   This option adds a `LOG' target, which allows you to create rules in
   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'.
 
 ipchains (2.2-style) support
 CONFIG_IP_NF_COMPAT_IPCHAINS
   This option places ipchains (with masquerading and redirection
   support) back into the kernel, using the new netfilter
   infrastructure.  It is not recommended for new installations (see
   `Packet filtering').  With this enabled, you should be able to use
   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'.
 
 ipfwadm (2.0-style) support
 CONFIG_IP_NF_COMPAT_IPFWADM
   This option places ipfwadm (with masquerading and redirection
   support) back into the kernel, using the new netfilter
   infrastructure.  It is not recommended for new installations (see
   `Packet filtering').  With this enabled, you should be able to use
   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'.
 
 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.
 
   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.
 
   If in doubt, say N.
 
 SYN flood protection
 CONFIG_SYN_COOKIES
   Normal TCP/IP networking is open to an attack known as "SYN
   flooding". This denial-of-service attack prevents legitimate remote
   users from being able to connect to your computer during an ongoing
   attack and requires very little work from the attacker, who can
   operate from anywhere on the Internet.
 
   SYN cookies provide protection against this type of attack. If you
   say Y here, the TCP/IP stack will use a cryptographic challenge
   protocol known as "SYN cookies" to enable legitimate users to
   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 .
 
   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
   an aid in tracing the packets to their actual source and should not
   be taken as absolute truth.
 
   SYN cookies may prevent correct error reporting on clients when the
   server is really overloaded. If this happens frequently better turn
   them off.
 
   If you say Y here, note that SYN cookies aren't enabled by default;
   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 
 
   at boot time after the /proc file system has been mounted.
   
   If unsure, say Y.
 
 Alpha system type
 CONFIG_ALPHA_GENERIC
   This is the system type of your hardware.  A "generic" kernel will
   run on any supported Alpha system. However, if you configure a
   kernel for your specific system, it will be faster and smaller.
 
   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:
 
   Alcor/Alpha-XLT     AS 600
   Alpha-XL            XL-233, XL-266
   AlphaBook1          Alpha laptop
   Avanti              AS 200, AS 205, AS 250, AS 255, AS 300, AS 400
   Cabriolet           AlphaPC64, AlphaPCI64
   DP264               DP264
   EB164               EB164 21164 evaluation board
   EB64+               EB64+ 21064 evaluation board
   EB66                EB66 21066 evaluation board
   EB66+               EB66+ 21066 evaluation board
   Jensen              DECpc 150, DEC 2000 model 300, 
                       DEC 2000 model 500
   LX164               AlphaPC164-LX
   Miata               Personal Workstation 433a, 433au, 500a,
                       500au, 600a, or 600au
   Mikasa              AS 1000
   Noname              AXPpci33, UDB (Multia)
   Noritake            AS 1000A, AS 600A, AS 800
   PC164               AlphaPC164
   Rawhide             AS 1200, AS 4000, AS 4100
   Ruffian             RPX164-2, AlphaPC164-UX, AlphaPC164-BX
   SX164               AlphaPC164-SX
   Sable               AS 2000, AS 2100
   Takara              Takara
   Titan               Privateer
   Wildfire            AlphaServer GS 40/80/160/320
 
   If you don't know what to do, choose "generic".
 
 EV5 CPU daughtercard
 CONFIG_ALPHA_PRIMO
   Say Y if you have an AS 1000 5/xxx or an AS 1000A 5/xxx.
 
 EV5 CPU(s)
 CONFIG_ALPHA_GAMMA
   Say Y if you have an AS 2000 5/xxx or an AS 2100 5/xxx.
 
 Using 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 .
 
   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
   kernel just like lilo does for the x86 architecture) which can be
   loaded either from ARC or can be installed directly as a permanent
   firmware replacement from floppy (which requires changing a certain
   jumper on the motherboard). If you want to do either of these, say N
   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. 
 
   If unsure, say N.
 
 Legacy kernel start address
 CONFIG_ALPHA_LEGACY_START_ADDRESS
   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.
 
   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.
 
   Under normal circumstances, this is so far and above what is needed
   as to be laughable.  However, there are certain applications (such
   as benchmark-grade in-kernel web serving) that can make use of as
   much vmalloc space as is available.
 
   Say N unless you know you need gobs and gobs of vmalloc space.
 
 Non-standard serial port support
 CONFIG_SERIAL_NONSTANDARD
   Say Y here if you have any non-standard serial boards -- boards
   which aren't supported using the standard "dumb" serial driver.
   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. 
 
   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. 
 
   Most people can say N here.
 
 Extended dumb serial driver options
 CONFIG_SERIAL_EXTENDED
   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. 
 
   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 serial driver options. If unsure, say N.
 
 Support more than 4 serial ports
 CONFIG_SERIAL_MANY_PORTS
   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
   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 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)
 CONFIG_SERIAL_DETECT_IRQ
   Say Y here if you want the kernel to try to guess which IRQ
   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.
 
   If unsure, say N.
 
 Support special multiport boards
 CONFIG_SERIAL_MULTIPORT
   Some multiport serial ports have special ports which are used to
   signal when there are any serial ports on the board which need
   servicing. Say Y here to enable the serial driver to take advantage
   of those special I/O ports.
 
 SGI PROM Console Support
 CONFIG_SGI_PROM_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)
 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
   /dev/graphics and /dev/gfx drivers into the kernel for supporting
   virtualized access to your graphics hardware.
 
 SGI Newport Console support
 CONFIG_SGI_NEWPORT_CONSOLE
   Say Y here if you want the console on the Newport aka XL graphics
   card of your Indy.  Most people say Y here.
 
 SGI DS1286 RTC support
 CONFIG_SGI_DS1286
   If you say Y here and create a character special file /dev/rtc with
   major number 10 and minor number 135 using mknod ("man mknod"), you
   will get access to the real time clock built into your computer.
   Every SGI has such a clock built in. It reports status information
   via the file /proc/rtc and its behaviour is set by various ioctls on
   /dev/rtc.
 
 Support the Bell Technologies HUB6 card
 CONFIG_HUB6
   Say Y here to enable support in the dumb serial driver to support
   the HUB6 card.
 
 PCMCIA serial device support
 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
   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.
 
 CardBus serial device support
 CONFIG_PCMCIA_SERIAL_CB
   Say Y here to enable support for CardBus serial devices, including
   serial port cards, modems, and the modem functions of multi-function
   ethernet/modem devices. (CardBus cards are the newer and better 
   version of PCMCIA- or PC-cards: 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_cb.o. If you want to compile it as
   a module, say M here and read Documentation/modules.txt. If unsure,
   say N.
 
 /dev/agpgart (AGP Support) (EXPERIMENTAL)
 CONFIG_AGP
   AGP (Accelerated Graphics Port) is a bus system mainly used to
   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.
 
   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
   due to kernel allocation issues), you could use PCI accesses
   and have up to a couple gigs of texture space.
 
   Note that this is the only means to have XFree4/GLX use
   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.
 
 Intel 440LX/BX/GX/815/840/850 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, 840 and 850 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/ .
 
 Intel I810/I810 DC100/I810e support
 CONFIG_AGP_I810
   This option gives you AGP support for the Xserver on the Intel 810
   and 815 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/ .
 
 AMD Irongate support
 CONFIG_AGP_AMD
   This option gives you AGP support for the GLX component of the
   XFree86 4.x on AMD Irongate chipset.
 
   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/ .
 
 Generic SiS support
 CONFIG_AGP_SIS
   This option gives you AGP support for the GLX component of the "soon
   to be released" XFree86 4.x on Silicon Integrated Systems [SiS]
   chipsets.
 
   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/ .
 
 ALI M1541 support
 CONFIG_AGP_ALI
   This option gives you AGP support for the GLX component of the
   XFree86 4.x on the ALi M1541 chipset.
 
   This 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/ .
 
 PCI support
 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. 
 
   The PCI-HOWTO, available from
   http://www.linuxdoc.org/docs.html#howto , contains valuable
   information about which PCI hardware does work under Linux and which
   doesn't.
 
 PCI support
 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. 
 
   The PCI-HOWTO, available from
   http://www.linuxdoc.org/docs.html#howto , contains valuable
   information about which PCI hardware does work under Linux and which
   doesn't.
 
 QSpan PCI
 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. 
 
   The PCI-HOWTO, available from
   http://www.linuxdoc.org/docs.html#howto , contains valuable
   information about which PCI hardware does work under Linux and which
   doesn't.
 
 PCI access mode
 CONFIG_PCI_GOBIOS
   On PCI systems, the BIOS can be used to detect the PCI devices and
   determine their configuration. However, some old PCI motherboards
   have BIOS bugs and may crash if this is done. Also, some embedded
   PCI-based systems don't have any BIOS at all. Linux can also try to
   detect the PCI hardware directly without using the BIOS.
 
   With this option, you can specify how Linux should detect the PCI
   devices. If you choose "BIOS", the BIOS will be used, if you choose
   "Direct", the BIOS won't be used, and if you choose "Any", the
   kernel will try the direct access method and falls back to the BIOS
   if that doesn't work. If unsure, go with the default, which is
   "Any".
 
 PCI device name database
 CONFIG_PCI_NAMES
   By default, the kernel contains a database of all known PCI device
   names to make the information in /proc/pci, /proc/ioports and
   similar files comprehensible to the user. This database increases
   size of the kernel image by about 80KB, but it gets freed after the
   system boots up, so it doesn't take up kernel memory. Anyway, if you
   are building an installation floppy or kernel for an embedded system
   where kernel image size really matters, you can disable this feature
   and you'll get device ID numbers instead of names.
 
   When in doubt, say Y.
 
 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.
 
 EISA support
 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.
 
   Say Y here if you are building a kernel for an EISA-based machine.
 
   Otherwise, say N.
 
 SGI Visual Workstation support
 CONFIG_VISWS
   The SGI Visual Workstation series is an IA32-based workstation
   based on SGI systems chips with some legacy PC hardware attached.
   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.
 
 SGI Visual Workstation framebuffer support
 CONFIG_FB_SGIVW
   SGI Visual Workstation support for framebuffer graphics.
 
 I2O support
 CONFIG_I2O
   The Intelligent Input/Output (I2O) architecture allows hardware
   drivers to be split into two parts: an operating system specific
   module called the OSM and an hardware specific module called the
   HDM. The OSM can talk to a whole range of HDM's, and ideally the
   HDM's are not OS dependent. This allows for the same HDM driver to
   be used under different operating systems if the relevant OSM is in
   place. In order for this to work, you need to have an I2O interface
   adapter card in your computer. This card contains a special I/O
   processor (IOP), thus allowing high speeds since the CPU does not
   have to deal with I/O.
 
   If you say Y here, you will get a choice of interface adapter
   drivers and OSM's with the following questions.
 
   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 i20_config.o. 
 
   If unsure, say N.
 
 I2O PCI support
 CONFIG_I2O_PCI
   Say Y for support of PCI bus I2O interface adapters. Currently this
   is the only variety supported, so you should say Y.
 
   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.
 
 I2O Block OSM
 CONFIG_I2O_BLOCK
   Include support for the I2O Block OSM. The Block OSM presents disk
   and other structured block devices to the operating system.
 
   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.
 
 I2O LAN OSM
 CONFIG_I2O_LAN
   Include support for the LAN OSM. You will also need to include
   support for token ring or FDDI if you wish to use token ring or FDDI
   I2O cards with this driver.
 
   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.
 
 I2O SCSI OSM
 CONFIG_I2O_SCSI
   Allows direct SCSI access to SCSI devices on a SCSI or FibreChannel
   I2O controller. You can use both the SCSI and Block OSM together if
   you wish.
 
   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.
 
 I2O /proc support
 CONFIG_I2O_PROC
   If you say Y here and to "/proc file system support", you will be
   able to read I2O related information from the virtual directory
   /proc/i2o.
 
   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.
 
 Plug and Play support
 CONFIG_PNP
   Plug and Play (PnP) is a standard for peripherals which allows those
   peripherals to be configured by software, e.g. assign IRQ's or other
   parameters. No jumpers on the cards are needed, instead the values
   are provided to the cards from the BIOS, from the operating system,
   or using a user-space utility.
 
   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 
   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.
 
 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.
  
   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.
 
   If unsure, say Y.
 
 Support for hot-pluggable devices
 CONFIG_HOTPLUG
   Say Y here if you want to plug devices into your computer while
   the system is running, and be able to use them quickly.  In many
   cases, the devices can likewise be unplugged at any time too.
 
   One well known example of this is PCMCIA- or PC-cards, credit-card
   size devices such as network cards, modems or hard drives which are
   plugged into slots found on all modern laptop computers.
 
   Another example, used on modern desktops as well as laptops, is USB.
   Enable HOTPLUG with USB and KMOD, and your kernel will automatically
   call out to a user mode "policy agent" to load modules and set up
   software needed to use USB devices you plug in.  Get agent software
   (at http://www.linux-usb.org/policy.html) and install it.
 
 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
   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
   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
 
   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.
 
 CardBus 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 
   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).
 
   If unsure, say Y.
 
 i82365/Yenta compatible 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.
 
 Databook TCIC host bridge support
 CONFIG_TCIC
   Say Y here to include support for the Databook TCIC family of PCMCIA
   host bridges. These are only found on a handful of old systems.
   "Bridge" is the name used for the hardware inside your computer that
   PCMCIA cards are plugged into. If unsure, say N.
 
 System V IPC
 CONFIG_SYSVIPC
   Inter Process Communication is a suite of library functions and
   system calls which let processes (running programs) synchronize and
   exchange information. It is generally considered to be a good thing,
   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
   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 .
 
   Shared memory is now implemented using a new (minimal) virtual file
   system. To mount it automatically at system startup just add the
   following line to your /etc/fstab:
 
   none  /dev/shm        shm     defaults        0 0
 
   Saying Y here enlarges your kernel by about 18 KB. Just say Y.
 
 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
   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.
   
 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
   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.
 
   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.
 
 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 
   in gdb:
 
   $ cd /usr/src/linux ; gdb vmlinux /proc/kcore
 
   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 
   leave it at its default value ELF.
 
 Kernel support for ELF binaries
 CONFIG_BINFMT_ELF
   ELF (Executable and Linkable Format) is a format for libraries and
   executables used across different architectures and operating
   systems. Saying Y here will enable your kernel to run ELF binaries
   and enlarge it by about 13 KB. ELF support under Linux has now all
   but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC)
   because it is portable (this does *not* mean that you will be able
   to run executables from different architectures or operating systems
   however) and makes building run-time libraries very easy. Many new
   executables are distributed solely in ELF format. You definitely
   want to say Y here.
 
   Information about ELF is contained in the ELF HOWTO available from
   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).
 
   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.
 
 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
   a.out formats QMAGIC and ZMAGIC until they were replaced with the
   ELF format.
 
   As more and more programs are converted to ELF, the use for a.out
   will gradually diminish. If you disable this option it will reduce
   your kernel by one page. This is not much and by itself does not
   warrant removing support. However its removal is a good idea if you
   wish to ensure that absolutely none of your programs will use this
   older executable format. If you don't know what to answer at this
   point then answer Y. If someone told you "You need a kernel with
   QMAGIC support" then you'll have to say Y here. You may answer M to
   compile a.out support as a module and later load the module when you
   want to use a program or library in a.out format. The module will be
   called binfmt_aout.o. Saying M or N here is dangerous though,
   because some crucial programs on your system might still be in A.OUT
   format.
 
 Kernel support for Linux/Intel ELF binaries
 CONFIG_BINFMT_EM86
   Say Y here if you want to be able to execute Linux/Intel ELF
   binaries just like native Alpha binaries on your Alpha machine. For
   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". 
 
   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 MISC binaries
 CONFIG_BINFMT_MISC
   If you say Y here, it will be possible to plug wrapper-driven binary
   formats into the kernel. You will like this especially when you use
   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
   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.
 
   You must say Y to "/proc file system support" (CONFIG_PROC_FS) to
   use this part of the kernel.
 
   You may say M here for module support and later load the module when
   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)
 CONFIG_SOLARIS_EMUL
   This is experimental code which will enable you to run (many)
   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.
 
 Processor family
 CONFIG_M386
   This is the processor type of your CPU. This information is used for
   optimizing purposes. In order to compile a kernel that can run on
   all x86 CPU types (albeit not optimally fast), you can specify
   "386" here.
 
   The kernel will not necessarily run on earlier architectures than
   the one you have chosen, e.g. a Pentium optimized kernel will run on
   a PPro, but not necessarily on a i486.
 
   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.
    - "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 
      (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.
    - "Pentium-4" for the Intel Pentium 4
    - "K6" for the AMD K6, K6-II and K6-III (aka K6-3D).
    - "Athlon" for the AMD Athlon (K7).
    - "Crusoe" for the Transmeta Crusoe series.
    - "Winchip-C6" for original IDT Winchip.
    - "Winchip-2" for IDT Winchip 2.
    - "Winchip-2A" for IDT Winchips with 3dNow! capabilities.
 
   If you don't know what to do, choose "386".
 
 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. 
 
   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 .
 
   Say Y.
 
 Video mode selection support
 CONFIG_VIDEO_SELECT
   This enables support for text mode selection on kernel startup. If
   you want to take advantage of some high-resolution text mode your
   card's BIOS offers, but the traditional Linux utilities like
   SVGATextMode don't, you can say Y here and set the mode using the
   "vga=" option from your boot loader (lilo or loadlin) or set
   "vga=ask" which brings up a video mode menu on kernel startup. (Try
   "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.
 
 Support for frame buffer devices (EXPERIMENTAL)
 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. 
 
   Frame buffer devices work identically across the different
   architectures supported by Linux and make the implementation of
   application programs easier and more portable; at this point, an X
   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
   information.
 
   Say Y here and to the driver for your graphics board below if you
   are compiling a kernel for a non-x86 architecture.
 
   If you are compiling for the x86 architecture, you can say Y if you
   want to play with it, but it is not essential. Please note that
   running graphical applications that directly touch the hardware
   (e.g. an accelerated X server) and that are not frame buffer
   device-aware may cause unexpected results. If unsure, say N.
 
 Acorn VIDC support
 CONFIG_FB_ACORN
   This is the frame buffer device driver for the Acorn VIDC graphics
   hardware found in Acorn RISC PCs and other ARM-based machines.  If
   unsure, say N.
 
 Amiga native chipset support
 CONFIG_FB_AMIGA
   This is the frame buffer device driver for the builtin graphics
   chipset found in Amigas.
 
   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.
 
 Amiga OCS chipset support
 CONFIG_FB_AMIGA_OCS
   This enables support for the original Agnus and Denise video chips,
   found in the Amiga 1000 and most A500's and A2000's. If you intend
   to run Linux on any of these systems, say Y; otherwise say N.
 
 Amiga ECS chipset support
 CONFIG_FB_AMIGA_ECS
   This enables support for the Enhanced Chip Set, found in later
   A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
   you intend to run Linux on any of these systems, say Y; otherwise
   say N.
 
 Amiga AGA chipset support
 CONFIG_FB_AMIGA_AGA
   This enables support for the Advanced Graphics Architecture (also
   known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
   and CD32. If you intend to run Linux on any of these systems, say Y;
   otherwise say N.
 
 Amiga CyberVision support
 CONFIG_FB_CYBER
   This enables support for the Cybervision 64 graphics card from
   Phase5. Please note that its use is not all that intuitive (i.e. if
   you have any questions, be sure to ask!). Say N unless you have a
   Cybervision 64 or plan to get one before you next recompile the
   kernel. Please note that this driver DOES NOT support the
   Cybervision 64 3D card, as they use incompatible video chips.
 
 CyberPro 20x0 support
 CONFIG_FB_CYBER2000
   This enables support for the Integraphics CyberPro 20x0 and 5000
   VGA chips used in the Rebel.com Netwinder and other machines.
   Say Y if you have a NetWinder or a graphics card containing this
   device, otherwise say N.
 
 Amiga CyberVision3D support (EXPERIMENTAL)
 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
   you have any questions, be sure to ask!). Say N unless you have a
   Cybervision 64/3D or plan to get one before you next recompile the
   kernel. Please note that this driver DOES NOT support the older
   Cybervision 64 card, as they use incompatible video chips.
 
 Amiga RetinaZ3 support (EXPERIMENTAL)
 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)
 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.
 
   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.
 
   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
 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,
   except that your Apollo won't be able to boot from it (because the
   code in the ROM will be for a PC).
 
 Atari native chipset support
 CONFIG_FB_ATARI
   This is the frame buffer device driver for the builtin graphics
   chipset found in Ataris.
 
 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 
 CONFIG_FB_S3TRIO
   If you have a S3 Trio say Y. Say N for S3 Virge. 
 
 3Dfx Banshee/Voodoo3 display support (EXPERIMENTAL)
 CONFIG_FB_3DFX
   This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
   chips. Say Y if you have such a graphics board.
 
   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.
 
 nVidia Riva support (EXPERIMENTAL)
 CONFIG_FB_RIVA
   This driver supports graphics boards with the nVidia Riva (aka TNTx)
   chips.
   Say Y if you have such a graphics board.
 
   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.
 
 ATI Mach64 display support (EXPERIMENTAL)
 CONFIG_FB_ATY
   This driver supports graphics boards with the ATI Mach64 chips.
   Say Y if you have such a graphics board.
 
   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 Rage128 display support (EXPERIMENTAL)
 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. 
 
   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.
 
 PowerMac "control" frame buffer device support
 CONFIG_FB_CONTROL
   This driver supports a frame buffer for the graphics adapter in the
   Power Macintosh 7300 and others.
 
 PowerMac "platinum" frame buffer device support
 CONFIG_FB_PLATINUM
   This driver supports a frame buffer for the "platinum" graphics
   adapter in some Power Macintoshes.
 
 PowerMac "valkyrie" frame buffer device support
 CONFIG_FB_VALKYRIE
   This driver supports a frame buffer for the "valkyrie" graphics
   adapter in some Power Macintoshes.
 
 Chips 65550 display support
 CONFIG_FB_CT65550
   This is the frame buffer device driver for the Chips & Technologies
   65550 graphics chip in PowerBooks.
 
 TGA frame buffer support
 CONFIG_FB_TGA
   This is the frame buffer device driver for generic TGA graphic
   cards. Say Y if you have one of those.
 
 VESA VGA graphics console
 CONFIG_FB_VESA
   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.
 
 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. 
 
   Only answer Y here if you have a (very old) VGA card that isn't VESA
   2 compatible.
 
 VGA 16-color graphics console
 CONFIG_FB_VGA16
   This is the frame buffer device driver for VGA 16 color graphic
   cards. Say Y if you have such a card.
 
   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.
 
 Select other compiled-in fonts
 CONFIG_FBCON_FONTS
   Say Y here if you would like to use fonts other than the default
   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
   the questions about foreign fonts.
 
   If unsure, say N (the default choices are safe).
 
 VGA 8x16 font
 CONFIG_FONT_8x16
   This is the "high resolution" font for the VGA frame buffer (the one
   provided by the VGA text console 80x25 mode.
 
   If unsure, say Y.
 
 Support only 8 pixels wide fonts
 CONFIG_FBCON_FONTWIDTH8_ONLY
   Answer Y here will make the kernel provide only the 8x8 fonts (these
   are the less readable).
 
   If unsure, say N.
 
 Sparc console 8x16 font
 CONFIG_FONT_SUN8x16
   This is the high resolution console font for Sun machines. Say Y.
 
 Sparc console 12x22 font (not supported by all drivers)
 CONFIG_FONT_SUN12x22
   This is the high resolution console font for Sun machines with very
   big letters (like the letters used in the SPARC PROM). If the
   standard font is unreadable for you, say Y, otherwise say N.
 
 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). 
 
   Note that this is a poor quality font. The VGA 8x16 font is quite a
   lot more readable. 
 
   Given the resolution provided by the frame buffer device, answer N
   here is safe.
 
 Backward compatibility mode for Xpmac
 CONFIG_FB_COMPAT_XPMAC
   If you use the Xpmac X server (common with mklinux), you'll need to
   say Y here to use X. You should consider changing to XFree86 which
   includes a server that supports the frame buffer device directly
   (XF68_FBDev).
 
 HGA monochrome support (EXPERIMENTAL)
 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.
 
   As this card technology is 15 years old, most people will answer N
   here.
 
 Matrox unified accelerated driver (EXPERIMENTAL)
 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.
 
   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.
 
   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. 
 
 Matrox Millennium 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,
   you should check 4 bpp packed pixel, 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.
 
 Matrox Mystique support
 CONFIG_FB_MATROX_MYSTIQUE
   Say Y here if you have a Matrox Mystique or Matrox Mystique 220
   video card. If you select "Advanced lowlevel driver options" below,
   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.
 
 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 
   different from 8.
 
   If you need support for G400 secondary head, you must first say Y to
   "I2C support" and "I2C bit-banging support" in the character devices
   section, and then to "Matrox I2C support" and "G400 second head
   support" here in the framebuffer section.
 
 Matrox I2C support
 CONFIG_FB_MATROX_I2C
   This drivers creates I2C buses which are needed for accessing the
   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 
   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 !!!
 
   Say Y or M here if you want to use a secondary head (meaning two
   monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
   head is not compatible with accelerated XFree 3.3.x SVGA servers -
   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.
   
   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
   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
   Say Y or M here if you want to use a secondary head (meaning two
   monitors in parallel) on G450.
 
   If you compile it as module, two modules are created,
   matroxfb_crtc2.o and matroxfb_g450.o. Both modules are needed if you
   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.
 
   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
   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
   your computer and you want to use all of them for different monitors
   ("multihead"). If you have only one device, you should say N because
   the driver compiled with Y is larger and a bit slower, especially on
   ia32 (ix86).
 
   If you said M to "Matrox unified accelerated driver" and N here, you
   will still be able to use several Matrox devices simultaneously:
   insert several instances of the module matroxfb.o into the kernel
   with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
   for the different Matrox devices. This method is slightly faster but
   uses 40 KB of kernel memory per Matrox card.
 
 MDA text console (dual-headed)
 CONFIG_MDA_CONSOLE
   Say Y here if you have an old MDA or monochrome Hercules graphics
   adapter in your system acting as a second head ( = video card). You
   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.
   
   If unsure, say N.
 
 SBUS and UPA frame buffers
 CONFIG_FB_SBUS
   Say Y if you want support for SBUS or UPA based frame buffer device.
 
 Creator/Creator3D support
 CONFIG_FB_CREATOR
   This is the frame buffer device driver for the Creator and Creator3D
   graphics boards.
 
 CGsix (GX,TurboGX) support
 CONFIG_FB_CGSIX
   This is the frame buffer device driver for the CGsix (GX, TurboGX)
   frame buffer.
 
 BWtwo support
 CONFIG_FB_BWTWO
   This is the frame buffer device driver for the BWtwo frame buffer.
 
 CGthree support
 CONFIG_FB_CGTHREE
   This is the frame buffer device driver for the CGthree frame buffer.
 
 TCX (SS4/SS5 only) support
 CONFIG_FB_TCX
   This is the frame buffer device driver for the TCX 24/8bit frame
   buffer.
 
 Virtual Frame Buffer support (ONLY FOR TESTING!)
 CONFIG_FB_VIRTUAL
   This is a `virtual' frame buffer device. It operates on a chunk of
   unswapable kernel memory instead of on the memory of a graphics
   board. This means you cannot see any output sent to this frame
   buffer device, while it does consume precious memory. The main use
   of this frame buffer device is testing and debugging the frame
   buffer subsystem. Do NOT enable it for normal systems! To protect
   the innocent, it has to be enabled explicitly at boot time using the
   kernel option `video=vfb:'.
 
   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.
  
   If unsure, say N.
 
 CONFIG_FB_SA1100
   This is a framebuffer device for the SA-1100 LCD Controller.
   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
   Y here.
 
 Advanced low level driver options
 CONFIG_FBCON_ADVANCED
   The frame buffer console uses character drawing routines that are
   tailored to the specific organization of pixels in the memory of
   your graphics hardware. These are called the low level frame buffer
   console drivers. Note that they are used for text console output
   only; they are NOT needed for graphical applications.
 
   If you say N here, the needed low level drivers are automatically
   enabled, depending on what frame buffer devices you selected above.
   This is recommended for most users.
 
   If you say Y here, you have more fine-grained control over which low
   level drivers are enabled. You can e.g. leave out low level drivers
   for color depths you do not intend to use for text consoles.
 
   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.
   
   If unsure, say N.
 
 Monochrome support
 CONFIG_FBCON_MFB
   This is the low level frame buffer console driver for monochrome
   (2 colors) packed pixels.
 
 2 bpp packed pixels support
 CONFIG_FBCON_CFB2
   This is the low level frame buffer console driver for 2 bits per
   pixel (4 colors) packed pixels.
 
 4 bpp packed pixels support
 CONFIG_FBCON_CFB4
   This is the low level frame buffer console driver for 4 bits per
   pixel (16 colors) packed pixels.
 
 8 bpp packed pixels support
 CONFIG_FBCON_CFB8
   This is the low level frame buffer console driver for 8 bits per
   pixel (256 colors) packed pixels.
 
 16 bpp packed pixels support
 CONFIG_FBCON_CFB16
   This is the low level frame buffer console driver for 15 or 16 bits
   per pixel (32K or 64K colors, also known as `hicolor') packed
   pixels.
 
 24 bpp packed pixels support
 CONFIG_FBCON_CFB24
   This is the low level frame buffer console driver for 24 bits per
   pixel (16M colors, also known as `truecolor') packed pixels. It is
   NOT for `sparse' 32 bits per pixel mode.
 
 32 bpp packed pixels support
 CONFIG_FBCON_CFB32
   This is the low level frame buffer console driver for 32 bits per
   pixel (16M colors, also known as `truecolor') sparse packed pixels.
 
 Amiga bitplanes support
 CONFIG_FBCON_AFB
   This is the low level frame buffer console driver for 1 to 8
   bitplanes (2 to 256 colors) on Amiga.
 
 Amiga interleaved bitplanes support
 CONFIG_FBCON_ILBM
   This is the low level frame buffer console driver for 1 to 8
   interleaved bitplanes (2 to 256 colors) on Amiga.
 
 Atari interleaved bitplanes (2 planes) support
 CONFIG_FBCON_IPLAN2P2
   This is the low level frame buffer console driver for 2 interleaved
   bitplanes (4 colors) on Atari.
 
 Atari interleaved bitplanes (4 planes) support
 CONFIG_FBCON_IPLAN2P4
   This is the low level frame buffer console driver for 4 interleaved
   bitplanes (16 colors) on Atari.
 
 Atari interleaved bitplanes (8 planes) support
 CONFIG_FBCON_IPLAN2P8
   This is the low level frame buffer console driver for 8 interleaved
   bitplanes (256 colors) on Atari.
 
 Mac variable bpp packed pixels support
 CONFIG_FBCON_MAC
   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)
 CONFIG_FBCON_HGA
   This is the low level frame buffer console driver for Hercules mono 
   graphics cards.
 
 VGA characters/attributes support
 CONFIG_FBCON_VGA
   This is the low level frame buffer console driver for VGA text mode;
   it is used by frame buffer device drivers that support VGA text
   mode.
 
 Parallel-port support
 CONFIG_PARPORT
   If you want to use devices connected to your machine's parallel port
   (the connector at the computer with 25 holes), e.g. printer, ZIP
   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.
 
   For extensive information about drivers for many devices attaching
   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.
 
   If unsure, say Y.
 
 PC-style hardware
 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. 
 
   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.
   
   If unsure, say Y.
 
 Use FIFO/DMA if available
 CONFIG_PARPORT_PC_FIFO
   Many parallel port chipsets provide hardware that can speed up
   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,
   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.
 
 SuperIO chipset support (EXPERIMENTAL)
 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
   is safe to say N.
 
 Support for PCMCIA management for PC-style ports
 CONFIG_PARPORT_PC_PCMCIA
   Say Y here if you need PCMCIA support for your PC-style parallel
   ports. If unsure, say N.
 
 Support foreign hardware
 CONFIG_PARPORT_OTHER
   Say Y here if you want to be able to load driver modules to support
   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
   Amiga machines. This code is also available as a module (say M),
   called parport_amiga.o. If in doubt, saying N is the safe plan.
 
 Atari built-in parallel port support
 CONFIG_PARPORT_ATARI
   Say Y here if you need support for the parallel port hardware on
   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
 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
 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
 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.
 
 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
   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
   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.
 
 Kernel module loader support
 CONFIG_KMOD
   Normally when you have selected some drivers and/or file systems to
   be created as loadable modules, you also have the responsibility to
   load the corresponding modules (using the programs insmod or
   modprobe) before you can use them. If you say Y here however, the
   kernel will be able to load modules for itself: when a part of the
   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.
 
 ARP daemon support (EXPERIMENTAL)
 CONFIG_ARPD
   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
   hundred directly connected hosts or less, keeping this address
   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. 
 
   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
   manner) and communication will be attempted with the user space ARP
   daemon arpd. Arpd then answers the address resolution request either
   from its own cache or by asking the net.
 
   This code is experimental and also obsolete. If you want to use it,
   you need to find a version of the daemon arpd on the net somewhere,
   and you should also say Y to "Kernel/User network link driver",
   below. If unsure, say N.
 
 TCP/IP networking
 CONFIG_INET
   These are the protocols used on the Internet and on most local
   Ethernets. It is highly recommended to say Y here (this will enlarge
   your kernel by about 144 KB), since some programs (e.g. the X window
   system) use TCP/IP even if your machine is not connected to any
   other computer. You will get the so-called loopback device which
   allows you to ping yourself (great fun, that!).
 
   For an excellent introduction to Linux networking, please read the
   NET-3-HOWTO, available from
   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 ).
   
   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.
 
   Short answer: say Y.
 
 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
   capabilities of the various network cards is contained in
   Documentation/networking/multicast.txt. For most people, it's safe
   to say N.
 
 IP: 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
   will then be presented with several options that allow more precise
   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
   questions about advanced routing.
 
   Note that your box can only act as a router if you enable IP
   forwarding in your kernel; you can do that by saying Y to "/proc
   file system support" and "Sysctl support" below and executing the
   line
 
     echo "1" > /proc/sys/net/ipv4/ip_forward
 
   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
   for their source address doesn't match the network interface they're
   arriving on. This has security advantages because it prevents the
   so-called IP spoofing, however it can pose problems if you use
   asymmetric routing (packets from you to a host take a different path
   than packets from that host to you) or if you operate a non-routing
   host which has several IP addresses on different interfaces. To turn
   rp_filter off use:
 
         echo 0 > /proc/sys/net/ipv4/conf/<device>/rp_filter
   or
         echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter
 
   If unsure, say N here.
 
 IP: 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
   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,
   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/
   
   If unsure, say N.
   
 IP: 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
   however, it becomes possible to attach several actions to a packet
   pattern, in effect specifying several alternative paths to travel
   for those packets. The router considers all these paths to be of
   equal "cost" and chooses one of them in a non-deterministic fashion
   if a matching packet arrives.
 
 IP: 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.
 
 IP: 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
 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
   received packets which look strange and could be evidence of an
   attack or a misconfigured system somewhere. The information is
   handled by the klogd daemon which is responsible for kernel messages
   ("man klogd").
 
 IP: 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
 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
   can be gotten from the document
   http://www.csn.tu-chemnitz.de/~mha/linux-ip-nat/diplom/nat.html
 
 IP: kernel level 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
   supplied on the kernel command line or by BOOTP or RARP protocols.
   You need to say Y only for diskless machines requiring network
   access to boot (in which case you want to say Y to "Root file system
   on NFS" as well), because all other machines configure the network
   in their startup scripts.
 
 BOOTP support
 CONFIG_IP_PNP_BOOTP
   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 BOOTP 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 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.
 
 RARP support
 CONFIG_IP_PNP_RARP
   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 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
   details.
 
 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
   encapsulating protocol. This particular tunneling driver implements
   encapsulation of IP within IP, which sounds kind of pointless, but
   can be useful if you want to make your (or some other) machine
   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 ). 
 
   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
 CONFIG_NET_IPGRE
   Tunneling means encapsulating data of one protocol type within
   another protocol and sending it over a channel that understands the
   encapsulating protocol. This particular tunneling driver implements
   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:
   tunneling" above). In addition, GRE allows multicast redistribution
   through the tunnel.
 
 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.
 
 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
   MBONE, a high bandwidth network on top of the Internet which carries
   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.
 
 IP: 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
   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
 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
   the X Window system and syslog use these sockets even if your
   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.
 
   Say Y unless you know what you are doing.
 
 The IPv6 protocol (EXPERIMENTAL)
 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 ;
   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.
 
   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.
 
   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.
 
   It is safe to say N here for now.
 
 IPv6: enable EUI-64 token format
 CONFIG_IPV6_EUI64
   6bone, the network of computers using the IPv6 protocol, is moving
   to a new aggregatable address format and a new link local address
   assignment (EUI-64). Say Y if your site has upgraded already, or
   has started to upgrade.
 
 IPv6: disable provider based addresses
 CONFIG_IPV6_NO_PB
   Linux tries to operate correctly when your site has moved to EUI-64
   only partially. Unfortunately, the two address formats (old:
   "provider based" and new: "aggregatable") are incompatible. Say Y if
   your site finished the upgrade to EUI-64, and/or you encountered
   some problems caused by the presence of two link-local addresses on
   an interface.
 
 IPv6: routing messages via old netlink
 CONFIG_IPV6_NETLINK
   You can say Y here to receive routing messages from the IPv6 code
   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)
 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
   files from the file system and cannot deal with executable content
   such as CGI scripts. Serving files is sped up if you use kHTTPd.
   If kHTTPd is not able to fulfill a request, it can transparently
   pass it through to a user space web server such as apache.
 
   Saying "M" here builds the kHTTPd module; this is NOT enough to have
   a working kHTTPd. For safety reasons, the module has to be activated
   by doing a "echo 1 > /proc/sys/net/khttpd/start" after inserting the
   module.
 
   Before using this, read the README in net/khttpd !
 
   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
 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
   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.
 
   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
   Linux (see "SPX networking", below).
 
   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 .
 
   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 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.
 
 IPX: 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
   (for example if your box is acting as a file server for different
   IPX networks: it will then be accessible from everywhere using the
   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.
 
   The full internal IPX network enables you to allocate sockets on
   different virtual nodes of the internal network. This is done by
   evaluating the field sipx_node of the socket address given to the
   bind call. So applications should always initialize the node field
   to 0 when binding a socket on the primary network. In this case the
   socket is assigned the default node that has been given to the
   kernel when the internal network was created. By enabling the full
   internal IPX network the cross-forwarding of packets targeted at
   '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 . 
 
   If you don't know what you are doing, say N.
 
 IPX: SPX networking (EXPERIMENTAL)
 CONFIG_SPX
   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
   of IP).
 
   Note that Novell NetWare file sharing does not use SPX; it uses a
   protocol called NCP, for which separate Linux support is available
   ("NCP file system support" below for the client side, and the user
   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.
 
   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.
 
 DECnet networking (EXPERIMENTAL)
 CONFIG_DECNET
   The DECnet networking protocol was used in many products made by
   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/
 
   More detailed documentation is available in the
   Documentation/networking/decnet.txt file.
 
   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
   in configuration at run time.
 
   The DECnet code 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 decnet.o.
 
 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.
 
 DECnet Router Support (EXPERIMENTAL)
 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.
 
    See Documentation/networking/decnet.txt for more information.
 
 DECnet: use FWMARK value as 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
   (see ipchains(8), "-m" argument).
 
 Appletalk interfaces support
 CONFIG_APPLETALK
   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.
 
 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
   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://threepio.hitchcock.org/cgi-bin/faq/netatalk/faq.pl 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
   NET-3-HOWTO, available from
   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. 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
 CONFIG_IPDDP
   This allows IP networking for users who only have AppleTalk
   networking available. This feature is experimental. With this
   driver, you can encapsulate IP inside AppleTalk (e.g. if your Linux
   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.
 
   If you say Y here, the AppleTalk-IP support will be compiled into
   the kernel. In this case, you can either use encapsulation or
   decapsulation, but not both. With the following two questions, you
   decide which one you want.
 
   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. 
 
 IP to AppleTalk-IP Encapsulation support
 CONFIG_IPDDP_ENCAP
   If you say Y here, the AppleTalk-IP code will be able to encapsulate
   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.
 
 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.
 
 Apple/Farallon LocalTalk PC card support
 CONFIG_LTPC
   This allows you to use the AppleTalk PC card to connect to LocalTalk
   networks. The card is also known as the Farallon PhoneNet PC card.
   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.
 
 COPS LocalTalk PC card support
 CONFIG_COPS
   This allows you to use COPS AppleTalk cards to connect to LocalTalk
   networks. You also need version 1.3.3 or later of the netatalk
   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. 
 
 Dayna firmware support
 CONFIG_COPS_DAYNA
   Support COPS compatible cards with Dayna style firmware (Dayna
   DL2000/ Daynatalk/PC (half length), COPS LT-95, Farallon PhoneNET PC
   III, Farallon PhoneNET PC II).
 
 Tangent firmware support
 CONFIG_COPS_TANGENT
   Support COPS compatible cards with Tangent style firmware (Tangent
   ATB_II, Novell NL-1000, Daystar Digital LT-200.
 
 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
   and the HAM-HOWTO and the AX25-HOWTO, both available from
   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
   the questions about amateur radio.
 
 Amateur Radio AX.25 Level 2
 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
   carry other protocols such as tcp/ip. To use it, you need a device
   that connects your Linux box to your amateur radio. You can either
   use a low speed TNC (a Terminal Node Controller acts as a kind of
   modem connecting your computer's serial port to your radio's
   microphone input and speaker output) supporting the KISS protocol or
   one of the various SCC cards that are supported by the generic Z8530
   or the DMA SCC driver. Another option are the Baycom modem serial
   and parallel port hacks or the sound card modem (supported by their
   own drivers). If you say Y here, you also have to say Y to one of
   those drivers.
 
   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 .
 
   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.
 
 AX.25 DAMA Slave support
 CONFIG_AX25_DAMA_SLAVE
   DAMA is a mechanism to prevent collisions when doing AX.25
   networking. A DAMA server (called "master") accepts incoming traffic
   from clients (called "slaves") and redistributes it to other slaves.
   If you say Y here, your Linux box will act as a DAMA slave; this is
   transparent in that you don't have to do any special DAMA
   configuration. (Linux cannot yet act as a DAMA server.) If unsure,
   say N.
 
 AX.25 DAMA Master support
 CONFIG_AX25_DAMA_MASTER
   DAMA is a mechanism to prevent collisions when doing AX.25
   networking. A DAMA server (called "master") accepts incoming traffic
   from clients (called "slaves") and redistributes it to other
   slaves. If you say Y here, your Linux box will act as a DAMA server.
   If unsure, say N.
 
 Amateur Radio NET/ROM
 CONFIG_NETROM
   NET/ROM is a network layer protocol on top of AX.25 useful for
   routing.
 
   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
   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 netrom.o. If you want to compile it as a
   module, say M here and read Documentation/modules.txt.
 
 Amateur Radio X.25 PLP (Rose)
 CONFIG_ROSE
   The Packet Layer Protocol (PLP) is a way to route packets over X.25
   connections in general and amateur radio AX.25 connections in
   particular, essentially an alternative to NET/ROM.
 
   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
   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 rose.o. If you want to compile it as a
   module, say M here and read Documentation/modules.txt.
 
 Serial port KISS driver for AX.25
 CONFIG_MKISS
   KISS is a protocol used for the exchange of data between a computer
   and a Terminal Node Controller (a small embedded system commonly
   used for networking over AX.25 amateur radio connections; it
   connects the computer's serial port with the radio's microphone
   input and speaker output).
 
   Although KISS is less advanced than the 6pack protocol, it has
   the advantage that it is already supported by most modern TNCs
   without the need for a firmware upgrade.
 
   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.
 
 Serial port 6PACK driver for AX.25
 CONFIG_6PACK
   6pack is a transmission protocol for the data exchange between your
   PC and your TNC (the Terminal Node Controller acts as a kind of
   modem connecting your computer's serial port to your radio's
   microphone input and speaker output). This protocol can be used as
   an alternative to KISS for networking over AX.25 amateur radio
   connections, but it has some extended functionality.
 
   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.
 
   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.
 
 BPQ Ethernet driver
 CONFIG_BPQETHER
   AX.25 is the protocol used for computer communication over amateur
   radio. If you say Y here, you will be able to send and receive AX.25
   traffic over Ethernet (also called "BPQ AX.25"), which could be
   useful if some other computer on your local network has a direct
   amateur radio connection.
 
 High-speed (DMA) SCC driver for AX.25
 CONFIG_DMASCC
   This is a driver for high-speed SCC boards, i.e. those supporting
   DMA on one port. You usually use those boards to connect your
   computer to an amateur radio modem (such as the WA4DSY 56kbps
   modem), in order to send and receive AX.25 packet radio network
   traffic.
 
   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 .
 
   This driver can operate multiple boards simultaneously. If you
   compile it as a module (by saying M instead of Y), it will be called
   dmascc.o. If you don't pass any parameter to the driver, all
   possible I/O addresses are probed. This could irritate other devices
   that are currently not in use. You may specify the list of addresses
   to be probed by "dmascc=addr1,addr2,..." (when compiled into the
   kernel image) or "io=addr1,addr2,..." (when loaded as a module). The
   network interfaces will be called dmascc0 and dmascc1 for the board
   detected first, dmascc2 and dmascc3 for the second one, and so on.
 
   Before you configure each interface with ifconfig, you MUST set
   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
   at least version 1.27 of dmascc_cfg, as older versions will not
   work with the current driver.
 
 Z8530 SCC driver for AX.25
 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.
 
   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.
 
 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.
 ###
 #
 
 YAM driver for AX.25
 CONFIG_YAM
   The YAM is a modem for packet radio which connects to the serial
   port and includes some of the functions of a Terminal Node
   Controller. If you have one of those, say Y here.
 
   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.
 
 BAYCOM picpar and par96 driver for AX.25
 CONFIG_BAYCOM_PAR
   This is a driver for Baycom style simple amateur radio modems that
   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.
 
   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.
 
 BAYCOM EPP driver for AX.25
 CONFIG_BAYCOM_EPP
   This is a driver for Baycom style simple