ia64/xen-unstable

changeset 505:08e3ab6bded3

bitkeeper revision 1.274 (3f05a93anjjeliV5S9lcht7Daq_Rhw)

Allow client operating systems controlled access to the
partition table. Essentially, this allows you to specify a
partition number when granting access to a range of blocks,
and xenolinux will then map the range to the given partition.
author sos22@labyrinth.cl.cam.ac.uk
date Fri Jul 04 16:20:10 2003 +0000 (2003-07-04)
parents aeb88ca14b2d
children 073c9b6cb4f9
files .rootkeys xen/drivers/block/xen_block.c xen/drivers/block/xen_physdisk.c xen/include/xeno/physdisk.h xenolinux-2.4.21-sparse/Documentation/Configure.help xenolinux-2.4.21-sparse/fs/partitions/Config.in xenolinux-2.4.21-sparse/fs/partitions/Makefile xenolinux-2.4.21-sparse/fs/partitions/check.c xenolinux-2.4.21-sparse/fs/partitions/xeno.c xenolinux-2.4.21-sparse/fs/partitions/xeno.h
line diff
     1.1 --- a/.rootkeys	Fri Jul 04 12:41:17 2003 +0000
     1.2 +++ b/.rootkeys	Fri Jul 04 16:20:10 2003 +0000
     1.3 @@ -493,6 +493,7 @@ 3eb3c87fPL2T_zBb0bHlbZY-ACEKRw xen/tools
     1.4  3eb3c87fmKYTC5GCh_rydFakZp9ayw xen/tools/figlet/README
     1.5  3eb3c87fdQKQ5OBGbM-KjZfi9Us4ng xen/tools/figlet/figlet.c
     1.6  3eb3c87fS7DNbg0i6yhFs28UIqAK5g xen/tools/figlet/xen.flf
     1.7 +3f05a939TA3SLPY7ZiScMotLjg9owQ xenolinux-2.4.21-sparse/Documentation/Configure.help
     1.8  3e5a4e6589G-U42lFKs43plskXoFxQ xenolinux-2.4.21-sparse/Makefile
     1.9  3e5a4e65IEPjnWPZ5w3TxS5scV8Ewg xenolinux-2.4.21-sparse/arch/xeno/Makefile
    1.10  3e5a4e65n-KhsEAs-A4ULiStBp-r6w xenolinux-2.4.21-sparse/arch/xeno/boot/Makefile
    1.11 @@ -547,6 +548,11 @@ 3ea53c6em6uzVHSiGqrbbAVofyRY_g xenolinux
    1.12  3e5a4e66mrtlmV75L1tjKDg8RaM5gA xenolinux-2.4.21-sparse/drivers/block/ll_rw_blk.c
    1.13  3e5a4e66rw65CxyolW9PKz4GG42RcA xenolinux-2.4.21-sparse/drivers/char/tty_io.c
    1.14  3e5a4e669uzIE54VwucPYtGwXLAbzA xenolinux-2.4.21-sparse/fs/exec.c
    1.15 +3f05a939l8s0eQb_fpMvYiI06cTGlA xenolinux-2.4.21-sparse/fs/partitions/Config.in
    1.16 +3f05a939W65febbeWrBtuQgsQDK2Bg xenolinux-2.4.21-sparse/fs/partitions/Makefile
    1.17 +3f05a939phguW4R5PelNQZ8o_EcYZA xenolinux-2.4.21-sparse/fs/partitions/check.c
    1.18 +3f05a939ZSKN7gX2sfTLzPcYJvPkcQ xenolinux-2.4.21-sparse/fs/partitions/xeno.c
    1.19 +3f05a939_I9vPADPgyVBwUDUxtoeOQ xenolinux-2.4.21-sparse/fs/partitions/xeno.h
    1.20  3e5a4e66wbeCpsJgVf_U8Jde-CNcsA xenolinux-2.4.21-sparse/include/asm-xeno/bugs.h
    1.21  3e5a4e66HdSkvIV6SJ1evG_xmTmXHA xenolinux-2.4.21-sparse/include/asm-xeno/desc.h
    1.22  3e5a4e66SYp_UpAVcF8Lc1wa3Qtgzw xenolinux-2.4.21-sparse/include/asm-xeno/fixmap.h
     2.1 --- a/xen/drivers/block/xen_block.c	Fri Jul 04 12:41:17 2003 +0000
     2.2 +++ b/xen/drivers/block/xen_block.c	Fri Jul 04 16:20:10 2003 +0000
     2.3 @@ -432,12 +432,6 @@ static void dispatch_probe_physdev(struc
     2.4      physdisk_probebuf_t *buf;
     2.5      int result;
     2.6  
     2.7 -    if ( p->domain != 0 )
     2.8 -    {
     2.9 -        result = 1;
    2.10 -        goto out;
    2.11 -    }
    2.12 -
    2.13      buffer = blk_ring->ring[index].req.buffer_and_sects[0] & ~0x1FF;
    2.14  
    2.15      spin_lock_irqsave(&p->page_lock, flags);
    2.16 @@ -451,7 +445,7 @@ static void dispatch_probe_physdev(struc
    2.17      spin_unlock_irqrestore(&p->page_lock, flags);
    2.18  
    2.19      buf = phys_to_virt(buffer);
    2.20 -    result = xen_physdisk_probe(buf);
    2.21 +    result = xen_physdisk_probe(p, buf);
    2.22  
    2.23      unlock_buffer(p, buffer, sizeof(*buf), 1);
    2.24  
     3.1 --- a/xen/drivers/block/xen_physdisk.c	Fri Jul 04 12:41:17 2003 +0000
     3.2 +++ b/xen/drivers/block/xen_physdisk.c	Fri Jul 04 16:20:10 2003 +0000
     3.3 @@ -10,7 +10,7 @@
     3.4  
     3.5  #define MAX(a,b) ((a) > (b) ? (a) : (b))
     3.6  
     3.7 -#if 1
     3.8 +#if 0
     3.9  #define DPRINTK printk
    3.10  #else
    3.11  #define DPRINTK(...)
    3.12 @@ -40,6 +40,8 @@ static struct physdisk_ace *find_ace(con
    3.13    struct list_head *cur_ace_head;
    3.14    struct physdisk_ace *cur_ace;
    3.15  
    3.16 +  dev &= ~0x1f; /* ignore the partition part */
    3.17 +
    3.18    list_for_each(cur_ace_head, &p->physdisk_aces) {
    3.19      cur_ace = list_entry(cur_ace_head, struct physdisk_ace,
    3.20  			 list);
    3.21 @@ -48,7 +50,7 @@ static struct physdisk_ace *find_ace(con
    3.22  	    sect);
    3.23      if (sect >= cur_ace->start_sect &&
    3.24  	sect < cur_ace->start_sect + cur_ace->n_sectors &&
    3.25 -	dev == cur_ace->device &&
    3.26 +	dev == (cur_ace->device & ~0x1f) && /* ignore partition part */
    3.27  	((operation == READ && (cur_ace->mode & PHYSDISK_MODE_R)) ||
    3.28  	 (operation == WRITE && (cur_ace->mode & PHYSDISK_MODE_W)))) {
    3.29        DPRINTK("Yes.\n");
    3.30 @@ -206,7 +208,8 @@ int xen_physdisk_grant(xp_disk_t *xpd_in
    3.31    return res;
    3.32  }
    3.33  
    3.34 -int xen_physdisk_probe(physdisk_probebuf_t *buf_in)
    3.35 +int xen_physdisk_probe(struct task_struct *requesting_domain,
    3.36 +		       physdisk_probebuf_t *buf_in)
    3.37  {
    3.38    struct task_struct *p;
    3.39    physdisk_probebuf_t *buf = map_domain_mem(virt_to_phys(buf_in));
    3.40 @@ -220,6 +223,12 @@ int xen_physdisk_probe(physdisk_probebuf
    3.41      res = 1;
    3.42      goto out;
    3.43    }
    3.44 +  if (requesting_domain->domain != 0 &&
    3.45 +      requesting_domain->domain != buf->domain) {
    3.46 +    res = 1;
    3.47 +    goto out;
    3.48 +  }
    3.49 +
    3.50    spin_lock(&p->physdev_lock);
    3.51    xen_physdisk_probe_access(buf, p);
    3.52    spin_unlock(&p->physdev_lock);
     4.1 --- a/xen/include/xeno/physdisk.h	Fri Jul 04 12:41:17 2003 +0000
     4.2 +++ b/xen/include/xeno/physdisk.h	Fri Jul 04 16:20:10 2003 +0000
     4.3 @@ -6,7 +6,8 @@ struct task_struct;
     4.4  void destroy_physdisk_aces(struct task_struct *p);
     4.5  
     4.6  int xen_physdisk_grant(xp_disk_t *);
     4.7 -int xen_physdisk_probe(physdisk_probebuf_t *);
     4.8 +int xen_physdisk_probe(struct task_struct *requesting_task,
     4.9 +		       physdisk_probebuf_t *);
    4.10  int xen_physdisk_access_okay(phys_seg_t *pseg, struct task_struct *p,
    4.11  			     int operation);
    4.12  
     5.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     5.2 +++ b/xenolinux-2.4.21-sparse/Documentation/Configure.help	Fri Jul 04 16:20:10 2003 +0000
     5.3 @@ -0,0 +1,26986 @@
     5.4 +# Maintained by:
     5.5 +#	Eric S. Raymond <mailto:esr@thyrsus.com>
     5.6 +#	Steven Cole <mailto:elenstev@mesatop.com>
     5.7 +#
     5.8 +# Version 3.01: current with 2.4.19+
     5.9 +#
    5.10 +# Translations of this file available on the WWW:
    5.11 +#
    5.12 +#   - Japanese, maintained by the JF Project <mailto:JF@linux.or.jp>, at
    5.13 +#     <http://www.linux.or.jp/JF/JFdocs/Configure.help/>
    5.14 +#   - Russian, by <mailto:kaf@linux.nevod.perm.su>, at
    5.15 +#     <http://nevod.perm.su/service/linux/doc/kernel/Configure.help>
    5.16 +#   - French, by Pierre Tane <mailto:tanep@bigfoot.com>, at
    5.17 +#     <http://www.traduc.org/kernelfr/>
    5.18 +#   - Polish, by Dominik Mierzejewski <mailto:dmierzej@elka.pw.edu.pl>, at
    5.19 +#     <http://home.elka.pw.edu.pl/~dmierzej/linux/kernel/>
    5.20 +#   - German, by SuSE, at <http://www.suse.de/~ke/kernel/>. This patch
    5.21 +#     also includes infrastructure to support different languages.
    5.22 +#   - Catalan, by Antoni Bella <mailto:bella5@teleline.es>, at
    5.23 +#     <http://www.terra.es/personal7/bella5/traduccions.htm>
    5.24 +#
    5.25 +# To access a document on the WWW, you need to have a direct Internet
    5.26 +# connection and a browser program such as netscape or lynx. If you
    5.27 +# only have email access, you can still use FTP and WWW servers: send
    5.28 +# an email to <mailto:mail-server@rtfm.mit.edu> with the text
    5.29 +#   send usenet/news.answers/internet-services/access-via-email
    5.30 +# in the body of the message.
    5.31 +#
    5.32 +# Information about what a kernel is, what it does, how to patch and
    5.33 +# compile it and much more is contained in the Kernel-HOWTO, available
    5.34 +# at <http://www.tldp.org/docs.html#howto>. Before you start
    5.35 +# compiling, make sure that you have the necessary versions of all
    5.36 +# programs and libraries required to compile and run this kernel; they
    5.37 +# are listed in the <file:Documentation/Changes>. Make sure to read the
    5.38 +# toplevel kernel README file as well.
    5.39 +#
    5.40 +# Format of this file: description<nl>variable<nl>help text<nl><nl>.
    5.41 +# The help texts may contain empty lines, but every non-empty line must
    5.42 +# be indented two positions.  Order of the help texts does not matter,
    5.43 +# however, no variable should be documented twice: if it is, only the
    5.44 +# first occurrence will be used. We try to keep the help texts of related
    5.45 +# variables close together. Lines starting with `#' are ignored. To be
    5.46 +# nice to menuconfig, limit your line length to 70 characters. Use emacs'
    5.47 +# kfill.el to edit and ispell.el to spell check this file or you lose.
    5.48 +#
    5.49 +# Comments of the form "# Choice:" followed by a menu name are used
    5.50 +# internally by the maintainers' consistency-checking tools.
    5.51 +#
    5.52 +# If you add a help text to this file, please try to be as gentle as
    5.53 +# possible. Don't use unexplained acronyms and generally write for the
    5.54 +# hypothetical ignorant but intelligent user who has just bought a PC,
    5.55 +# removed Windows, installed Linux and is now recompiling the kernel
    5.56 +# for the first time. Tell them what to do if they're unsure. Technical
    5.57 +# information should go in a README in the Documentation directory.
    5.58 +#
    5.59 +# Mention all the relevant READMEs and HOWTOs in the help text.
    5.60 +# Make them file URLs relative to the top level of the source tree so
    5.61 +# that help browsers can turn them into hotlinks.  All URLs should be
    5.62 +# surrounded by <>.
    5.63 +#
    5.64 +# Repetitions are fine since the help texts are not meant to be read
    5.65 +# in sequence.  It is good style to include URLs pointing to more
    5.66 +# detailed technical information, pictures of the hardware, etc.
    5.67 +#
    5.68 +# The most important thing to include in a help entry is *motivation*.
    5.69 +# Explain why someone configuring a kernel might want to select your
    5.70 +# option.
    5.71 +#
    5.72 +# All this was shamelessly stolen from numerous different sources. Many
    5.73 +# thanks to all the contributors. Feel free to use these help texts in
    5.74 +# your own kernel configuration tools. The texts are copyrighted (c)
    5.75 +# 1995-2000 by Axel Boldt and many others and are governed by the GNU
    5.76 +# General Public License.
    5.77 +
    5.78 +Prompt for development and/or incomplete code/drivers
    5.79 +CONFIG_EXPERIMENTAL
    5.80 +  Some of the various things that Linux supports (such as network
    5.81 +  drivers, file systems, network protocols, etc.) can be in a state
    5.82 +  of development where the functionality, stability, or the level of
    5.83 +  testing is not yet high enough for general use. This is usually
    5.84 +  known as the "alpha-test" phase among developers. If a feature is
    5.85 +  currently in alpha-test, then the developers usually discourage
    5.86 +  uninformed widespread use of this feature by the general public to
    5.87 +  avoid "Why doesn't this work?" type mail messages. However, active
    5.88 +  testing and use of these systems is welcomed. Just be aware that it
    5.89 +  may not meet the normal level of reliability or it may fail to work
    5.90 +  in some special cases. Detailed bug reports from people familiar
    5.91 +  with the kernel internals are usually welcomed by the developers
    5.92 +  (before submitting bug reports, please read the documents
    5.93 +  <file:README>, <file:MAINTAINERS>, <file:REPORTING-BUGS>,
    5.94 +  <file:Documentation/BUG-HUNTING>, and
    5.95 +  <file:Documentation/oops-tracing.txt> in the kernel source).
    5.96 +
    5.97 +  This option will also make obsoleted drivers available. These are
    5.98 +  drivers that have been replaced by something else, and/or are
    5.99 +  scheduled to be removed in a future kernel release.
   5.100 +
   5.101 +  Unless you intend to help test and develop a feature or driver that
   5.102 +  falls into this category, or you have a situation that requires
   5.103 +  using these features, you should probably say N here, which will
   5.104 +  cause the configurator to present you with fewer choices. If
   5.105 +  you say Y here, you will be offered the choice of using features or
   5.106 +  drivers that are currently considered to be in the alpha-test phase.
   5.107 +
   5.108 +Prompt for drivers for obsolete features and hardware
   5.109 +CONFIG_OBSOLETE
   5.110 +  Obsolete drivers have usually been replaced by more recent software
   5.111 +  that can talk to the same hardware.  Obsolete hardware is things
   5.112 +  like MGA monitors that you are very unlikely to see on today's
   5.113 +  systems.
   5.114 +
   5.115 +Symmetric Multi-Processing support
   5.116 +CONFIG_SMP
   5.117 +  This enables support for systems with more than one CPU. If you have
   5.118 +  a system with only one CPU, like most personal computers, say N. If
   5.119 +  you have a system with more than one CPU, say Y.
   5.120 +
   5.121 +  If you say N here, the kernel will run on single and multiprocessor
   5.122 +  machines, but will use only one CPU of a multiprocessor machine. If
   5.123 +  you say Y here, the kernel will run on many, but not all,
   5.124 +  single machines. On a singleprocessor machine, the kernel
   5.125 +  will run faster if you say N here.
   5.126 +
   5.127 +  Note that if you say Y here and choose architecture "586" or
   5.128 +  "Pentium" under "Processor family", the kernel will not work on 486
   5.129 +  architectures. Similarly, multiprocessor kernels for the "PPro"
   5.130 +  architecture may not work on all Pentium based boards.
   5.131 +
   5.132 +  People using multiprocessor machines who say Y here should also say
   5.133 +  Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
   5.134 +  Management" code will be disabled if you say Y here.
   5.135 +
   5.136 +  See also the <file:Documentation/smp.tex>,
   5.137 +  <file:Documentation/smp.txt>, <file:Documentation/i386/IO-APIC.txt>,
   5.138 +  <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
   5.139 +  <http://www.tldp.org/docs.html#howto>.
   5.140 +
   5.141 +  If you don't know what to do here, say N.
   5.142 +
   5.143 +Intel or compatible 80x86 processor
   5.144 +CONFIG_X86
   5.145 +  This is Linux's home port.  Linux was originally native to the Intel
   5.146 +  386, and runs on all the later x86 processors including the Intel
   5.147 +  486, 586, Pentiums, and various instruction-set-compatible chips by
   5.148 +  AMD, Cyrix, and others.
   5.149 +
   5.150 +Alpha processor
   5.151 +CONFIG_ALPHA
   5.152 +  The Alpha is a 64-bit general-purpose processor designed and
   5.153 +  marketed by the Digital Equipment Corporation of blessed memory, now
   5.154 +  Compaq.  Alpha Linux dates from 1995-1996 and was the first non-x86
   5.155 +  port. The Alpha Linux project has a home page at
   5.156 +  <http://www.alphalinux.org/>.
   5.157 +
   5.158 +32-bit Sun Sparc
   5.159 +CONFIG_SPARC32
   5.160 +  SPARC is a family of RISC microprocessors designed and marketed by
   5.161 +  Sun Microsystems, incorporated.  They are very widely found in Sun
   5.162 +  workstations and clones. This port covers the original 32-bit SPARC;
   5.163 +  it is old and stable and usually considered one of the "big three"
   5.164 +  along with the Intel and Alpha ports.  The UltraLinux project
   5.165 +  maintains both the SPARC32 and SPARC64 ports; its web page is
   5.166 +  available at <http://www.ultralinux.org/>.
   5.167 +
   5.168 +64-bit Sun Sparc
   5.169 +CONFIG_SPARC64
   5.170 +  SPARC is a family of RISC microprocessors designed and marketed by
   5.171 +  Sun Microsystems, incorporated.  This port covers the newer 64-bit
   5.172 +  UltraSPARC.  The UltraLinux project maintains both the SPARC32 and
   5.173 +  SPARC64 ports; its web page is available at
   5.174 +  <http://www.ultralinux.org/>.
   5.175 +
   5.176 +Power PC processor
   5.177 +CONFIG_PPC
   5.178 +  The PowerPC is a very capable 32-bit RISC processor from Motorola,
   5.179 +  the successor to their 68000 and 88000 series.  It powers recent
   5.180 +  Macintoshes and also a widely-used series of single-board computers
   5.181 +  from Motorola.  The Linux PowerPC port has a home page at
   5.182 +  <http://penguinppc.org/>.
   5.183 +
   5.184 +Motorola 68K processors
   5.185 +CONFIG_M68K
   5.186 +  The Motorola 68K microprocessors are now obsolete, having been
   5.187 +  superseded by the PowerPC line also from Motorola.  But they powered
   5.188 +  the first wave of workstation hardware in the 1980s, including Sun
   5.189 +  workstations; they were also the basis of the original Amiga and
   5.190 +  later Atari personal computers.  A lot of this hardware is still
   5.191 +  around.  The m68k project has a home page at
   5.192 +  <http://www.linux-m68k.org/>.
   5.193 +
   5.194 +ARM processors
   5.195 +CONFIG_ARM
   5.196 +  The ARM series is a line of low-power-consumption RISC chip designs
   5.197 +  licensed by ARM ltd and targeted at embedded applications and
   5.198 +  handhelds such as the Compaq IPAQ.  ARM-based PCs are no longer
   5.199 +  manufactured, but  legacy ARM-based PC hardware remains popular in
   5.200 +  Europe.  There is an ARM Linux project with a web page at
   5.201 +  <http://www.arm.linux.org.uk/>.
   5.202 +
   5.203 +SuperH processors
   5.204 +CONFIG_SUPERH
   5.205 +  The SuperH is a RISC processor targeted for use in embedded systems
   5.206 +  and consumer electronics; it was also used in the Sega Dreamcast
   5.207 +  gaming console.  The SuperH port has a home page at
   5.208 +  <http://www.sh-linux.org/>.
   5.209 +
   5.210 +IA64 processors, including Intel Itanium
   5.211 +CONFIG_IA64
   5.212 +  The Itanium is Intel's 64-bit successor to the 32-bit X86 line.  As
   5.213 +  of early 2001 it is not yet in widespread production use.  The Linux
   5.214 +  IA-64 project has a home page at <http://www.linuxia64.org/>.
   5.215 +
   5.216 +HP PA-RISC processor
   5.217 +CONFIG_PARISC
   5.218 +  The PA-RISC microprocessor is a RISC chip designed by
   5.219 +  Hewlett-Packard and used in their line of workstations.  The PA-RISC
   5.220 +  Linux project has a home page at <www.parisc-linux.org>.
   5.221 +
   5.222 +IBM System/390
   5.223 +CONFIG_S390
   5.224 +  Linux now runs on the venerable System/390 mainframe from IBM, in a
   5.225 +  guest partition under VM.  In fact, over 40,000 simultaneous Linux
   5.226 +  images have been run on a single mainframe!  The S390 Linux project
   5.227 +  has a home page at <http://linux.s390.org/>.
   5.228 +
   5.229 +Axis Communications ETRAX 100LX embedded network CPU
   5.230 +CONFIG_CRIS
   5.231 +  Linux has been ported to run on the Axis Communications ETRAX 100LX
   5.232 +  CPU and the single-board computers built around it, targeted for
   5.233 +  network and embedded applications.  For more information see the
   5.234 +  Axis Communication site, <http://developer.axis.com/>.
   5.235 +
   5.236 +Unsynced TSC support
   5.237 +CONFIG_X86_TSC_DISABLE
   5.238 +  This option is used for getting Linux to run on a NUMA multi-node 
   5.239 +  boxes, laptops and other systems suffering from unsynced TSCs or 
   5.240 +  TSC drift, which can cause gettimeofday to return non-monotonic values. 
   5.241 +  Choosing this option will disable the CONFIG_X86_TSC optimization,
   5.242 +  and allows you to then specify "notsc" as a boot option regardless of 
   5.243 +  which processor you have compiled for. 
   5.244 +  
   5.245 +  NOTE: If your system hangs when init should run, you are probably
   5.246 +  using a i686 compiled glibc which reads the TSC without checking for 
   5.247 +  availability. Boot without "notsc" and install a i386 compiled glibc 
   5.248 +  to solve the problem.
   5.249 +
   5.250 +  If unsure, say N.
   5.251 +
   5.252 +Multiquad support for NUMAQ systems
   5.253 +CONFIG_X86_NUMAQ
   5.254 +  This option is used for getting Linux to run on a (IBM/Sequent) NUMA 
   5.255 +  multiquad box. This changes the way that processors are bootstrapped,
   5.256 +  and uses Clustered Logical APIC addressing mode instead of Flat Logical.
   5.257 +  You will need a new lynxer.elf file to flash your firmware with - send
   5.258 +  email to Martin.Bligh@us.ibm.com
   5.259 +
   5.260 +Support for IBM Summit (EXA) systems
   5.261 +CONFIG_X86_SUMMIT
   5.262 +  This option is needed for IBM systems that use the Summit/EXA chipset.
   5.263 +  (EXA: Extendable Xseries Architecture)In particular, it is needed for 
   5.264 +  the x440 (even for the 4-CPU model).
   5.265 +
   5.266 +  If you don't have this computer, you may safely say N.
   5.267 +
   5.268 +IO-APIC support on uniprocessors
   5.269 +CONFIG_X86_UP_IOAPIC
   5.270 +  An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
   5.271 +  SMP-capable replacement for PC-style interrupt controllers. Most
   5.272 +  SMP systems and a small number of uniprocessor systems have one.
   5.273 +  If you have a single-CPU system with an IO-APIC, you can say Y here
   5.274 +  to use it. If you say Y here even though your machine doesn't have
   5.275 +  an IO-APIC, then the kernel will still run with no slowdown at all.
   5.276 +
   5.277 +  If you have a system with several CPUs, you do not need to say Y
   5.278 +  here: the IO-APIC will be used automatically.
   5.279 +
   5.280 +Local APIC Support on Uniprocessors
   5.281 +CONFIG_X86_UP_APIC
   5.282 +  A local APIC (Advanced Programmable Interrupt Controller) is an
   5.283 +  integrated interrupt controller in the CPU. If you have a single-CPU
   5.284 +  system which has a processor with a local APIC, you can say Y here to
   5.285 +  enable and use it. If you say Y here even though your machine doesn't
   5.286 +  have a local APIC, then the kernel will still run with no slowdown at
   5.287 +  all. The local APIC supports CPU-generated self-interrupts (timer,
   5.288 +  performance counters), and the NMI watchdog which detects hard lockups.
   5.289 +
   5.290 +  If you have a system with several CPUs, you do not need to say Y
   5.291 +  here: the local APIC will be used automatically.
   5.292 +
   5.293 +Kernel math emulation
   5.294 +CONFIG_MATH_EMULATION
   5.295 +  Linux can emulate a math coprocessor (used for floating point
   5.296 +  operations) if you don't have one. 486DX and Pentium processors have
   5.297 +  a math coprocessor built in, 486SX and 386 do not, unless you added
   5.298 +  a 487DX or 387, respectively. (The messages during boot time can
   5.299 +  give you some hints here ["man dmesg"].) Everyone needs either a
   5.300 +  coprocessor or this emulation.
   5.301 +
   5.302 +  If you don't have a math coprocessor, you need to say Y here; if you
   5.303 +  say Y here even though you have a coprocessor, the coprocessor will
   5.304 +  be used nevertheless. (This behaviour can be changed with the kernel
   5.305 +  command line option "no387", which comes handy if your coprocessor
   5.306 +  is broken. Try "man bootparam" or see the documentation of your boot
   5.307 +  loader (lilo or loadlin) about how to pass options to the kernel at
   5.308 +  boot time.) This means that it is a good idea to say Y here if you
   5.309 +  intend to use this kernel on different machines.
   5.310 +
   5.311 +  More information about the internals of the Linux math coprocessor
   5.312 +  emulation can be found in <file:arch/i386/math-emu/README>.
   5.313 +
   5.314 +  If you are not sure, say Y; apart from resulting in a 66 KB bigger
   5.315 +  kernel, it won't hurt.
   5.316 +
   5.317 +Timer and CPU usage LEDs
   5.318 +CONFIG_LEDS
   5.319 +  If you say Y here, the LEDs on your machine will be used
   5.320 +  to provide useful information about your current system status.
   5.321 +
   5.322 +  If you are compiling a kernel for a NetWinder or EBSA-285, you will
   5.323 +  be able to select which LEDs are active using the options below. If
   5.324 +  you are compiling a kernel for the EBSA-110 or the LART however, the
   5.325 +  red LED will simply flash regularly to indicate that the system is
   5.326 +  still functional. It is safe to say Y here if you have a CATS
   5.327 +  system, but the driver will do nothing.
   5.328 +
   5.329 +Timer LED
   5.330 +CONFIG_LEDS_TIMER
   5.331 +  If you say Y here, one of the system LEDs (the green one on the
   5.332 +  NetWinder, the amber one on the EBSA285, or the red one on the LART)
   5.333 +  will flash regularly to indicate that the system is still
   5.334 +  operational. This is mainly useful to kernel hackers who are
   5.335 +  debugging unstable kernels.
   5.336 +
   5.337 +  The LART uses the same LED for both Timer LED and CPU usage LED
   5.338 +  functions. You may choose to use both, but the Timer LED function
   5.339 +  will overrule the CPU usage LED.
   5.340 +
   5.341 +CPU usage LED
   5.342 +CONFIG_LEDS_CPU
   5.343 +  If you say Y here, the red LED will be used to give a good real
   5.344 +  time indication of CPU usage, by lighting whenever the idle task
   5.345 +  is not currently executing.
   5.346 +
   5.347 +  The LART uses the same LED for both Timer LED and CPU usage LED
   5.348 +  functions. You may choose to use both, but the Timer LED function
   5.349 +  will overrule the CPU usage LED.
   5.350 +
   5.351 +Kernel FP software completion
   5.352 +CONFIG_MATHEMU
   5.353 +  This option is required for IEEE compliant floating point arithmetic
   5.354 +  on the Alpha. The only time you would ever not say Y is to say M in
   5.355 +  order to debug the code. Say Y unless you know what you are doing.
   5.356 +
   5.357 +# Choice: himem
   5.358 +High Memory support
   5.359 +CONFIG_NOHIGHMEM
   5.360 +  Linux can use up to 64 Gigabytes of physical memory on x86 systems.
   5.361 +  However, the address space of 32-bit x86 processors is only 4
   5.362 +  Gigabytes large. That means that, if you have a large amount of
   5.363 +  physical memory, not all of it can be "permanently mapped" by the
   5.364 +  kernel. The physical memory that's not permanently mapped is called
   5.365 +  "high memory".
   5.366 +
   5.367 +  If you are compiling a kernel which will never run on a machine with
   5.368 +  more than 960 megabytes of total physical RAM, answer "off" here (default
   5.369 +  choice and suitable for most users). This will result in a "3GB/1GB"
   5.370 +  split: 3GB are mapped so that each process sees a 3GB virtual memory
   5.371 +  space and the remaining part of the 4GB virtual memory space is used
   5.372 +  by the kernel to permanently map as much physical memory as
   5.373 +  possible.
   5.374 +
   5.375 +  If the machine has between 1 and 4 Gigabytes physical RAM, then
   5.376 +  answer "4GB" here.
   5.377 +
   5.378 +  If more than 4 Gigabytes is used then answer "64GB" here. This
   5.379 +  selection turns Intel PAE (Physical Address Extension) mode on.
   5.380 +  PAE implements 3-level paging on IA32 processors. PAE is fully
   5.381 +  supported by Linux, PAE mode is implemented on all recent Intel
   5.382 +  processors (Pentium Pro and better). NOTE: If you say "64GB" here,
   5.383 +  then the kernel will not boot on CPUs that don't support PAE!
   5.384 +
   5.385 +  The actual amount of total physical memory will either be auto
   5.386 +  detected or can be forced by using a kernel command line option such
   5.387 +  as "mem=256M". (Try "man bootparam" or see the documentation of your
   5.388 +  boot loader (grub, lilo or loadlin) about how to pass options to the
   5.389 +  kernel at boot time.)
   5.390 +
   5.391 +  If unsure, say "off".
   5.392 +
   5.393 +4GB
   5.394 +CONFIG_HIGHMEM4G
   5.395 +  Select this if you have a 32-bit processor and between 1 and 4
   5.396 +  gigabytes of physical RAM.
   5.397 +
   5.398 +64GB
   5.399 +CONFIG_HIGHMEM64G
   5.400 +  Select this if you have a 32-bit processor and more than 4
   5.401 +  gigabytes of physical RAM.
   5.402 +
   5.403 +HIGHMEM I/O support
   5.404 +CONFIG_HIGHIO
   5.405 +  If you want to be able to do I/O to high memory pages, say Y.
   5.406 +  Otherwise low memory pages are used as bounce buffers causing a
   5.407 +  degrade in performance.
   5.408 +
   5.409 +Normal floppy disk support
   5.410 +CONFIG_BLK_DEV_FD
   5.411 +  If you want to use the floppy disk drive(s) of your PC under Linux,
   5.412 +  say Y. Information about this driver, especially important for IBM
   5.413 +  Thinkpad users, is contained in <file:Documentation/floppy.txt>.
   5.414 +  That file also contains the location of the Floppy driver FAQ as
   5.415 +  well as location of the fdutils package used to configure additional
   5.416 +  parameters of the driver at run time.
   5.417 +
   5.418 +  This driver is also available as a module ( = code which can be
   5.419 +  inserted in and removed from the running kernel whenever you want).
   5.420 +  The module will be called floppy.o. If you want to compile it as a
   5.421 +  module, say M here and read <file:Documentation/modules.txt>.
   5.422 +
   5.423 +iSeries Virtual I/O Disk Support
   5.424 +CONFIG_VIODASD
   5.425 +  If you are running on an iSeries system and you want to use
   5.426 +  virtual disks created and managed by OS/400, say Y.
   5.427 +
   5.428 +iSeries Virtual I/O Disk IDE Emulation
   5.429 +CONFIG_VIODASD_IDE
   5.430 +  This causes the iSeries virtual disks to look like IDE disks.
   5.431 +  If you have programs or utilities that only support certain
   5.432 +  kinds of disks, this option will cause iSeries virtual disks
   5.433 +  to pretend to be IDE disks, which may satisfy the program.
   5.434 +
   5.435 +Support for PowerMac floppy
   5.436 +CONFIG_MAC_FLOPPY
   5.437 +  If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
   5.438 +  floppy controller, say Y here. Most commonly found in PowerMacs.
   5.439 +
   5.440 +RAM disk support
   5.441 +CONFIG_BLK_DEV_RAM
   5.442 +  Saying Y here will allow you to use a portion of your RAM memory as
   5.443 +  a block device, so that you can make file systems on it, read and
   5.444 +  write to it and do all the other things that you can do with normal
   5.445 +  block devices (such as hard drives). It is usually used to load and
   5.446 +  store a copy of a minimal root file system off of a floppy into RAM
   5.447 +  during the initial install of Linux.
   5.448 +
   5.449 +  Note that the kernel command line option "ramdisk=XX" is now
   5.450 +  obsolete. For details, read <file:Documentation/ramdisk.txt>.
   5.451 +
   5.452 +  If you want to compile this as a module ( = code which can be
   5.453 +  inserted in and removed from the running kernel whenever you want),
   5.454 +  say M and read <file:Documentation/modules.txt>. The module will be
   5.455 +  called rd.o.
   5.456 +
   5.457 +  Most normal users won't need the RAM disk functionality, and can
   5.458 +  thus say N here.
   5.459 +
   5.460 +Default RAM disk size
   5.461 +CONFIG_BLK_DEV_RAM_SIZE
   5.462 +  The default value is 4096. Only change this if you know what are
   5.463 +  you doing. If you are using IBM S/390, then set this to 8192.
   5.464 +
   5.465 +Initial RAM disk (initrd) support
   5.466 +CONFIG_BLK_DEV_INITRD
   5.467 +  The initial RAM disk is a RAM disk that is loaded by the boot loader
   5.468 +  (loadlin or lilo) and that is mounted as root before the normal boot
   5.469 +  procedure. It is typically used to load modules needed to mount the
   5.470 +  "real" root file system, etc. See <file:Documentation/initrd.txt>
   5.471 +  for details.
   5.472 +
   5.473 +Loopback device support
   5.474 +CONFIG_BLK_DEV_LOOP
   5.475 +  Saying Y here will allow you to use a regular file as a block
   5.476 +  device; you can then create a file system on that block device and
   5.477 +  mount it just as you would mount other block devices such as hard
   5.478 +  drive partitions, CD-ROM drives or floppy drives. The loop devices
   5.479 +  are block special device files with major number 7 and typically
   5.480 +  called /dev/loop0, /dev/loop1 etc.
   5.481 +
   5.482 +  This is useful if you want to check an ISO 9660 file system before
   5.483 +  burning the CD, or if you want to use floppy images without first
   5.484 +  writing them to floppy. Furthermore, some Linux distributions avoid
   5.485 +  the need for a dedicated Linux partition by keeping their complete
   5.486 +  root file system inside a DOS FAT file using this loop device
   5.487 +  driver.
   5.488 +
   5.489 +  The loop device driver can also be used to "hide" a file system in a
   5.490 +  disk partition, floppy, or regular file, either using encryption
   5.491 +  (scrambling the data) or steganography (hiding the data in the low
   5.492 +  bits of, say, a sound file). This is also safe if the file resides
   5.493 +  on a remote file server. If you want to do this, you will first have
   5.494 +  to acquire and install a kernel patch from
   5.495 +  <ftp://ftp.kerneli.org/pub/kerneli/>, and then you need to
   5.496 +  say Y to this option.
   5.497 +
   5.498 +  Note that alternative ways to use encrypted file systems are
   5.499 +  provided by the cfs package, which can be gotten from
   5.500 +  <ftp://ftp.kerneli.org/pub/kerneli/net-source/>, and the newer tcfs
   5.501 +  package, available at <http://tcfs.dia.unisa.it/>. You do not need
   5.502 +  to say Y here if you want to use one of these. However, using cfs
   5.503 +  requires saying Y to "NFS file system support" below while using
   5.504 +  tcfs requires applying a kernel patch. An alternative steganography
   5.505 +  solution is provided by StegFS, also available from
   5.506 +  <ftp://ftp.kerneli.org/pub/kerneli/net-source/>.
   5.507 +
   5.508 +  To use the loop device, you need the losetup utility and a recent
   5.509 +  version of the mount program, both contained in the util-linux
   5.510 +  package. The location and current version number of util-linux is
   5.511 +  contained in the file <file:Documentation/Changes>.
   5.512 +
   5.513 +  Note that this loop device has nothing to do with the loopback
   5.514 +  device used for network connections from the machine to itself.
   5.515 +
   5.516 +  If you want to compile this driver as a module ( = code which can be
   5.517 +  inserted in and removed from the running kernel whenever you want),
   5.518 +  say M here and read <file:Documentation/modules.txt>. The module
   5.519 +  will be called loop.o.
   5.520 +
   5.521 +  Most users will answer N here.
   5.522 +
   5.523 +Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL)
   5.524 +CONFIG_BLK_DEV_UMEM
   5.525 +  Saying Y here will include support for the MM5415 family of
   5.526 +  battery backed (Non-volatile) RAM cards.
   5.527 +  <http://www.umem.com/>
   5.528 +
   5.529 +  The cards appear as block devices that can be partitioned into
   5.530 +  as many as 15 partitions.
   5.531 +
   5.532 +  If you want to compile this driver as a module ( = code which can be
   5.533 +  inserted in and removed from the running kernel whenever you want),
   5.534 +  say M here and read Documentation/modules.txt. The module will be
   5.535 +  called umem.o.
   5.536 +
   5.537 +  The umem driver has been allocated block major number 116.
   5.538 +  See Documentation/devices.txt for recommended device naming.
   5.539 +
   5.540 +Network block device support
   5.541 +CONFIG_BLK_DEV_NBD
   5.542 +  Saying Y here will allow your computer to be a client for network
   5.543 +  block devices, i.e. it will be able to use block devices exported by
   5.544 +  servers (mount file systems on them etc.). Communication between
   5.545 +  client and server works over TCP/IP networking, but to the client
   5.546 +  program this is hidden: it looks like a regular local file access to
   5.547 +  a block device special file such as /dev/nd0.
   5.548 +
   5.549 +  Network block devices also allows you to run a block-device in
   5.550 +  userland (making server and client physically the same computer,
   5.551 +  communicating using the loopback network device).
   5.552 +
   5.553 +  Read <file:Documentation/nbd.txt> for more information, especially
   5.554 +  about where to find the server code, which runs in user space and
   5.555 +  does not need special kernel support.
   5.556 +
   5.557 +  Note that this has nothing to do with the network file systems NFS
   5.558 +  or Coda; you can say N here even if you intend to use NFS or Coda.
   5.559 +
   5.560 +  If you want to compile this driver as a module ( = code which can be
   5.561 +  inserted in and removed from the running kernel whenever you want),
   5.562 +  say M here and read <file:Documentation/modules.txt>. The module
   5.563 +  will be called nbd.o.
   5.564 +
   5.565 +  If unsure, say N.
   5.566 +
   5.567 +Per partition statistics in /proc/partitions
   5.568 +CONFIG_BLK_STATS
   5.569 +  If you say yes here, your kernel will keep statistical information
   5.570 +  for every partition. The information includes things as numbers of
   5.571 +  read and write accesses, the number of merged requests etc.
   5.572 +
   5.573 +  This is required for the full functionality of sar(8) and interesting
   5.574 +  if you want to do performance tuning, by tweaking the elevator, e.g.
   5.575 +
   5.576 +  If unsure, say N.
   5.577 +
   5.578 +ATA/IDE/MFM/RLL support
   5.579 +CONFIG_IDE
   5.580 +  If you say Y here, your kernel will be able to manage low cost mass
   5.581 +  storage units such as ATA/(E)IDE and ATAPI units. The most common
   5.582 +  cases are IDE hard drives and ATAPI CD-ROM drives.
   5.583 +
   5.584 +  If your system is pure SCSI and doesn't use these interfaces, you
   5.585 +  can say N here.
   5.586 +
   5.587 +  Integrated Disk Electronics (IDE aka ATA-1) is a connecting standard
   5.588 +  for mass storage units such as hard disks. It was designed by
   5.589 +  Western Digital and Compaq Computer in 1984. It was then named
   5.590 +  ST506. Quite a number of disks use the IDE interface.
   5.591 +
   5.592 +  AT Attachment (ATA) is the superset of the IDE specifications.
   5.593 +  ST506 was also called ATA-1.
   5.594 +
   5.595 +  Fast-IDE is ATA-2 (also named Fast ATA), Enhanced IDE (EIDE) is
   5.596 +  ATA-3. It provides support for larger disks (up to 8.4GB by means of
   5.597 +  the LBA standard), more disks (4 instead of 2) and for other mass
   5.598 +  storage units such as tapes and cdrom. UDMA/33 (aka UltraDMA/33) is
   5.599 +  ATA-4 and provides faster (and more CPU friendly) transfer modes
   5.600 +  than previous PIO (Programmed processor Input/Output) from previous
   5.601 +  ATA/IDE standards by means of fast DMA controllers.
   5.602 +
   5.603 +  ATA Packet Interface (ATAPI) is a protocol used by EIDE tape and
   5.604 +  CD-ROM drives, similar in many respects to the SCSI protocol.
   5.605 +
   5.606 +  SMART IDE (Self Monitoring, Analysis and Reporting Technology) was
   5.607 +  designed in order to prevent data corruption and disk crash by
   5.608 +  detecting pre hardware failure conditions (heat, access time, and
   5.609 +  the like...). Disks built since June 1995 may follow this standard.
   5.610 +  The kernel itself don't manage this; however there are quite a
   5.611 +  number of user programs such as smart that can query the status of
   5.612 +  SMART parameters disk.
   5.613 +
   5.614 +  If you want to compile this driver as a module ( = code which can be
   5.615 +  inserted in and removed from the running kernel whenever you want),
   5.616 +  say M here and read <file:Documentation/modules.txt>. The module
   5.617 +  will be called ide.o.
   5.618 +
   5.619 +  For further information, please read <file:Documentation/ide.txt>.
   5.620 +
   5.621 +  If unsure, say Y.
   5.622 +
   5.623 +Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
   5.624 +CONFIG_BLK_DEV_IDE
   5.625 +  If you say Y here, you will use the full-featured IDE driver to
   5.626 +  control up to ten ATA/IDE interfaces, each being able to serve a
   5.627 +  "master" and a "slave" device, for a total of up to twenty ATA/IDE
   5.628 +  disk/cdrom/tape/floppy drives.
   5.629 +
   5.630 +  Useful information about large (>540 MB) IDE disks, multiple
   5.631 +  interfaces, what to do if ATA/IDE devices are not automatically
   5.632 +  detected, sound card ATA/IDE ports, module support, and other
   5.633 +  topics, is contained in <file:Documentation/ide.txt>. For detailed
   5.634 +  information about hard drives, consult the Disk-HOWTO and the
   5.635 +  Multi-Disk-HOWTO, available from
   5.636 +  <http://www.tldp.org/docs.html#howto>.
   5.637 +
   5.638 +  To fine-tune ATA/IDE drive/interface parameters for improved
   5.639 +  performance, look for the hdparm package at
   5.640 +  <ftp://ibiblio.org/pub/Linux/system/hardware/>.
   5.641 +
   5.642 +  If you want to compile this driver as a module ( = code which can be
   5.643 +  inserted in and removed from the running kernel whenever you want),
   5.644 +  say M here and read <file:Documentation/modules.txt> and
   5.645 +  <file:Documentation/ide.txt>. The module will be called ide-mod.o.
   5.646 +  Do not compile this driver as a module if your root file system (the
   5.647 +  one containing the directory /) is located on an IDE device.
   5.648 +
   5.649 +  If you have one or more IDE drives, say Y or M here. If your system
   5.650 +  has no IDE drives, or if memory requirements are really tight, you
   5.651 +  could say N here, and select the "Old hard disk driver" below
   5.652 +  instead to save about 13 KB of memory in the kernel.
   5.653 +
   5.654 +Old hard disk (MFM/RLL/IDE) driver
   5.655 +CONFIG_BLK_DEV_HD_ONLY
   5.656 +  There are two drivers for MFM/RLL/IDE hard disks. Most people use
   5.657 +  the newer enhanced driver, but this old one is still around for two
   5.658 +  reasons. Some older systems have strange timing problems and seem to
   5.659 +  work only with the old driver (which itself does not work with some
   5.660 +  newer systems). The other reason is that the old driver is smaller,
   5.661 +  since it lacks the enhanced functionality of the new one. This makes
   5.662 +  it a good choice for systems with very tight memory restrictions, or
   5.663 +  for systems with only older MFM/RLL/ESDI drives. Choosing the old
   5.664 +  driver can save 13 KB or so of kernel memory.
   5.665 +
   5.666 +  If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
   5.667 +  instead of this one. For more detailed information, read the
   5.668 +  Disk-HOWTO, available from
   5.669 +  <http://www.tldp.org/docs.html#howto>.
   5.670 +
   5.671 +Use old disk-only driver on primary interface
   5.672 +CONFIG_BLK_DEV_HD_IDE
   5.673 +  There are two drivers for MFM/RLL/IDE disks.  Most people use just
   5.674 +  the new enhanced driver by itself.  This option however installs the
   5.675 +  old hard disk driver to control the primary IDE/disk interface in
   5.676 +  the system, leaving the new enhanced IDE driver to take care of only
   5.677 +  the 2nd/3rd/4th IDE interfaces.  Doing this will prevent you from
   5.678 +  having an IDE/ATAPI CD-ROM or tape drive connected to the primary
   5.679 +  IDE interface.  Choosing this option may be useful for older systems
   5.680 +  which have MFM/RLL/ESDI controller+drives at the primary port
   5.681 +  address (0x1f0), along with IDE drives at the secondary/3rd/4th port
   5.682 +  addresses.
   5.683 +
   5.684 +  Normally, just say N here; you will then use the new driver for all
   5.685 +  4 interfaces.
   5.686 +
   5.687 +Include IDE/ATA-2 DISK support
   5.688 +CONFIG_BLK_DEV_IDEDISK
   5.689 +  This will include enhanced support for MFM/RLL/IDE hard disks.  If
   5.690 +  you have a MFM/RLL/IDE disk, and there is no special reason to use
   5.691 +  the old hard disk driver instead, say Y.  If you have an SCSI-only
   5.692 +  system, you can say N here.
   5.693 +
   5.694 +  If you want to compile this driver as a module ( = code which can be
   5.695 +  inserted in and removed from the running kernel whenever you want),
   5.696 +  say M here and read <file:Documentation/modules.txt>.  The module
   5.697 +  will be called ide-disk.o.  Do not compile this driver as a module
   5.698 +  if your root file system (the one containing the directory /) is
   5.699 +  located on the IDE disk. If unsure, say Y.
   5.700 +
   5.701 +Use multi-mode by default
   5.702 +CONFIG_IDEDISK_MULTI_MODE
   5.703 +  If you get this error, try to say Y here:
   5.704 +
   5.705 +  hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
   5.706 +  hda: set_multmode: error=0x04 { DriveStatusError }
   5.707 +
   5.708 +  If in doubt, say N.
   5.709 +
   5.710 +PCMCIA IDE support
   5.711 +CONFIG_BLK_DEV_IDECS
   5.712 +  Support for outboard IDE disks, tape drives, and CD-ROM drives
   5.713 +  connected through a  PCMCIA card.
   5.714 +
   5.715 +  This driver is also available as a module ( = code which can be
   5.716 +  inserted in and removed from the running kernel whenever you want).
   5.717 +  If you want to compile it as a module, say M here and read
   5.718 +  <file:Documentation/modules.txt>. The module will be called
   5.719 +  ide-cs.o
   5.720 +
   5.721 +Include IDE/ATAPI CD-ROM support
   5.722 +CONFIG_BLK_DEV_IDECD
   5.723 +  If you have a CD-ROM drive using the ATAPI protocol, say Y. ATAPI is
   5.724 +  a newer protocol used by IDE CD-ROM and TAPE drives, similar to the
   5.725 +  SCSI protocol. Most new CD-ROM drives use ATAPI, including the
   5.726 +  NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
   5.727 +  double(2X) or better speed drives.
   5.728 +
   5.729 +  If you say Y here, the CD-ROM drive will be identified at boot time
   5.730 +  along with other IDE devices, as "hdb" or "hdc", or something
   5.731 +  similar (check the boot messages with dmesg). If this is your only
   5.732 +  CD-ROM drive, you can say N to all other CD-ROM options, but be sure
   5.733 +  to say Y or M to "ISO 9660 CD-ROM file system support".
   5.734 +
   5.735 +  Note that older versions of LILO (LInux LOader) cannot properly deal
   5.736 +  with IDE/ATAPI CD-ROMs, so install LILO 16 or higher, available from
   5.737 +  <ftp://brun.dyndns.org/pub/linux/lilo/>.
   5.738 +
   5.739 +  If you want to compile the driver as a module ( = code which can be
   5.740 +  inserted in and removed from the running kernel whenever you want),
   5.741 +  say M here and read <file:Documentation/modules.txt>.  The module
   5.742 +  will be called ide-cd.o.
   5.743 +
   5.744 +Include IDE/ATAPI TAPE support
   5.745 +CONFIG_BLK_DEV_IDETAPE
   5.746 +  If you have an IDE tape drive using the ATAPI protocol, say Y.
   5.747 +  ATAPI is a newer protocol used by IDE tape and CD-ROM drives,
   5.748 +  similar to the SCSI protocol.  If you have an SCSI tape drive
   5.749 +  however, you can say N here.
   5.750 +
   5.751 +  You should also say Y if you have an OnStream DI-30 tape drive; this
   5.752 +  will not work with the SCSI protocol, until there is support for the
   5.753 +  SC-30 and SC-50 versions.
   5.754 +
   5.755 +  If you say Y here, the tape drive will be identified at boot time
   5.756 +  along with other IDE devices, as "hdb" or "hdc", or something
   5.757 +  similar, and will be mapped to a character device such as "ht0"
   5.758 +  (check the boot messages with dmesg).  Be sure to consult the
   5.759 +  <file:drivers/ide/ide-tape.c> and <file:Documentation/ide.txt> files
   5.760 +  for usage information.
   5.761 +
   5.762 +  If you want to compile the driver as a module ( = code which can be
   5.763 +  inserted in and removed from the running kernel whenever you want),
   5.764 +  say M here and read <file:Documentation/modules.txt>.  The module
   5.765 +  will be called ide-tape.o.
   5.766 +
   5.767 +Include IDE/ATAPI FLOPPY support
   5.768 +CONFIG_BLK_DEV_IDEFLOPPY
   5.769 +  If you have an IDE floppy drive which uses the ATAPI protocol,
   5.770 +  answer Y.  ATAPI is a newer protocol used by IDE CD-ROM/tape/floppy
   5.771 +  drives, similar to the SCSI protocol.
   5.772 +
   5.773 +  The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by
   5.774 +  this driver. For information about jumper settings and the question
   5.775 +  of when a ZIP drive uses a partition table, see
   5.776 +  <http://www.win.tue.nl/~aeb/linux/zip/zip-1.html>.
   5.777 +  (ATAPI PD-CD/CDR drives are not supported by this driver; support
   5.778 +  for PD-CD/CDR drives is available if you answer Y to
   5.779 +  "SCSI emulation support", below).
   5.780 +
   5.781 +  If you say Y here, the FLOPPY drive will be identified along with
   5.782 +  other IDE devices, as "hdb" or "hdc", or something similar (check
   5.783 +  the boot messages with dmesg).
   5.784 +
   5.785 +  If you want to compile the driver as a module ( = code which can be
   5.786 +  inserted in and removed from the running kernel whenever you want),
   5.787 +  say M here and read <file:Documentation/modules.txt>.  The module
   5.788 +  will be called ide-floppy.o.
   5.789 +
   5.790 +AWARD Bios Work-Around
   5.791 +CONFIG_IDEDISK_STROKE
   5.792 +  Should you have a system w/ an AWARD Bios and your drives are larger
   5.793 +  than 32GB and it will not boot, one is required to perform a few OEM
   5.794 +  operations first.  The option is called "STROKE" because it allows
   5.795 +  one to "soft clip" the drive to work around a barrier limit.  For
   5.796 +  Maxtor drives it is called "jumpon.exe".  Please search Maxtor's
   5.797 +  web-site for "JUMPON.EXE".  IBM has a similar tool at:
   5.798 +  <http://www.storage.ibm.com/hdd/support/download.htm>.
   5.799 +
   5.800 +  If you are unsure, say N here.
   5.801 +
   5.802 +Raw Access to Media
   5.803 +CONFIG_IDE_TASK_IOCTL
   5.804 +  This is a direct raw access to the media.  It is a complex but
   5.805 +  elegant solution to test and validate the domain of the hardware and
   5.806 +  perform below the driver data recover if needed.  This is the most
   5.807 +  basic form of media-forensics.
   5.808 +
   5.809 +  If you are unsure, say N here.
   5.810 +
   5.811 +Use Taskfile I/O
   5.812 +CONFIG_IDE_TASKFILE_IO
   5.813 +  This is the "Jewel" of the patch.  It will go away and become the new
   5.814 +  driver core.  Since all the chipsets/host side hardware deal w/ their
   5.815 +  exceptions in "their local code" currently, adoption of a
   5.816 +  standardized data-transport is the only logical solution.
   5.817 +  Additionally we packetize the requests and gain rapid performance and
   5.818 +  a reduction in system latency.  Additionally by using a memory struct
   5.819 +  for the commands we can redirect to a MMIO host hardware in the next
   5.820 +  generation of controllers, specifically second generation Ultra133
   5.821 +  and Serial ATA.
   5.822 +
   5.823 +  Since this is a major transition, it was deemed necessary to make the
   5.824 +  driver paths buildable in separate models.  Therefore if using this
   5.825 +  option fails for your arch then we need to address the needs for that
   5.826 +  arch.
   5.827 +
   5.828 +  If you want to test this functionality, say Y here.
   5.829 +
   5.830 +Force DMA
   5.831 +CONFIG_BLK_DEV_IDEDMA_FORCED
   5.832 +  This is an old piece of lost code from Linux 2.0 Kernels.
   5.833 +
   5.834 +  Generally say N here.
   5.835 +
   5.836 +DMA Only on Disks
   5.837 +CONFIG_IDEDMA_ONLYDISK
   5.838 +  This is used if you know your ATAPI Devices are going to fail DMA
   5.839 +  Transfers.
   5.840 +
   5.841 +  Generally say N here.
   5.842 +
   5.843 +SCSI emulation support
   5.844 +CONFIG_BLK_DEV_IDESCSI
   5.845 +  This will provide SCSI host adapter emulation for IDE ATAPI devices,
   5.846 +  and will allow you to use a SCSI device driver instead of a native
   5.847 +  ATAPI driver.
   5.848 +
   5.849 +  This is useful if you have an ATAPI device for which no native
   5.850 +  driver has been written (for example, an ATAPI PD-CD or CDR drive);
   5.851 +  you can then use this emulation together with an appropriate SCSI
   5.852 +  device driver. In order to do this, say Y here and to "SCSI support"
   5.853 +  and "SCSI generic support", below. You must then provide the kernel
   5.854 +  command line "hdx=scsi" (try "man bootparam" or see the
   5.855 +  documentation of your boot loader (lilo or loadlin) about how to
   5.856 +  pass options to the kernel at boot time) for devices if you want the
   5.857 +  native EIDE sub-drivers to skip over the native support, so that
   5.858 +  this SCSI emulation can be used instead. This is required for use of
   5.859 +  CD-RW's.
   5.860 +
   5.861 +  Note that this option does NOT allow you to attach SCSI devices to a
   5.862 +  box that doesn't have a SCSI host adapter installed.
   5.863 +
   5.864 +  If both this SCSI emulation and native ATAPI support are compiled
   5.865 +  into the kernel, the native support will be used.
   5.866 +
   5.867 +  This driver is also available as a module ( = code which can be
   5.868 +  inserted in and removed from the running kernel whenever you want).
   5.869 +  If you want to compile it as a module, say M here and read
   5.870 +  <file:Documentation/modules.txt>. The module will be called
   5.871 +  ide-scsi.o
   5.872 +
   5.873 +Use the NOOP Elevator (WARNING)
   5.874 +CONFIG_BLK_DEV_ELEVATOR_NOOP
   5.875 +  If you are using a raid class top-level driver above the ATA/IDE core,
   5.876 +  one may find a performance boost by preventing a merging and re-sorting
   5.877 +  of the new requests.
   5.878 +
   5.879 +  If unsure, say N.
   5.880 +
   5.881 +ISA-PNP EIDE support
   5.882 +CONFIG_BLK_DEV_ISAPNP
   5.883 +  If you have an ISA EIDE card that is PnP (Plug and Play) and
   5.884 +  requires setup first before scanning for devices, say Y here.
   5.885 +
   5.886 +  If unsure, say N.
   5.887 +
   5.888 +CMD640 chipset bugfix/support
   5.889 +CONFIG_BLK_DEV_CMD640
   5.890 +  The CMD-Technologies CMD640 IDE chip is used on many common 486 and
   5.891 +  Pentium motherboards, usually in combination with a "Neptune" or
   5.892 +  "SiS" chipset. Unfortunately, it has a number of rather nasty
   5.893 +  design flaws that can cause severe data corruption under many common
   5.894 +  conditions. Say Y here to include code which tries to automatically
   5.895 +  detect and correct the problems under Linux. This option also
   5.896 +  enables access to the secondary IDE ports in some CMD640 based
   5.897 +  systems.
   5.898 +
   5.899 +  This driver will work automatically in PCI based systems (most new
   5.900 +  systems have PCI slots). But if your system uses VESA local bus
   5.901 +  (VLB) instead of PCI, you must also supply a kernel boot parameter
   5.902 +  to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man
   5.903 +  bootparam" or see the documentation of your boot loader about how to
   5.904 +  pass options to the kernel.)
   5.905 +
   5.906 +  The CMD640 chip is also used on add-in cards by Acculogic, and on
   5.907 +  the "CSA-6400E PCI to IDE controller" that some people have. For
   5.908 +  details, read <file:Documentation/ide.txt>.
   5.909 +
   5.910 +CMD640 enhanced support
   5.911 +CONFIG_BLK_DEV_CMD640_ENHANCED
   5.912 +  This option includes support for setting/autotuning PIO modes and
   5.913 +  prefetch on CMD640 IDE interfaces.  For details, read
   5.914 +  <file:Documentation/ide.txt>. If you have a CMD640 IDE interface
   5.915 +  and your BIOS does not already do this for you, then say Y here.
   5.916 +  Otherwise say N.
   5.917 +
   5.918 +RZ1000 chipset bugfix/support
   5.919 +CONFIG_BLK_DEV_RZ1000
   5.920 +  The PC-Technologies RZ1000 IDE chip is used on many common 486 and
   5.921 +  Pentium motherboards, usually along with the "Neptune" chipset.
   5.922 +  Unfortunately, it has a rather nasty design flaw that can cause
   5.923 +  severe data corruption under many conditions. Say Y here to include
   5.924 +  code which automatically detects and corrects the problem under
   5.925 +  Linux. This may slow disk throughput by a few percent, but at least
   5.926 +  things will operate 100% reliably.
   5.927 +
   5.928 +Generic PCI IDE chipset support
   5.929 +CONFIG_BLK_DEV_IDEPCI
   5.930 +  Say Y here for PCI systems which use IDE drive(s).
   5.931 +  This option helps the IDE driver to automatically detect and
   5.932 +  configure all PCI-based IDE interfaces in your system.
   5.933 +
   5.934 +Support for sharing PCI IDE interrupts
   5.935 +CONFIG_IDEPCI_SHARE_IRQ
   5.936 +  Some ATA/IDE chipsets have hardware support which allows for
   5.937 +  sharing a single IRQ with other cards. To enable support for
   5.938 +  this in the ATA/IDE driver, say Y here.
   5.939 +
   5.940 +  It is safe to say Y to this question, in most cases.
   5.941 +  If unsure, say N.
   5.942 +
   5.943 +Generic PCI bus-master DMA support
   5.944 +CONFIG_BLK_DEV_IDEDMA_PCI
   5.945 +  If your PCI system uses IDE drive(s) (as opposed to SCSI, say) and
   5.946 +  is capable of bus-master DMA operation (most Pentium PCI systems),
   5.947 +  you will want to say Y here to reduce CPU overhead. You can then use
   5.948 +  the "hdparm" utility to enable DMA for drives for which it was not
   5.949 +  enabled automatically. By default, DMA is not enabled automatically
   5.950 +  for these drives, but you can change that by saying Y to the
   5.951 +  following question "Use DMA by default when available". You can get
   5.952 +  the latest version of the hdparm utility from
   5.953 +  <ftp://ibiblio.org/pub/Linux/system/hardware/>.
   5.954 +
   5.955 +  Read the comments at the beginning of <file:drivers/ide/ide-dma.c>
   5.956 +  and the file <file:Documentation/ide.txt> for more information.
   5.957 +
   5.958 +  It is safe to say Y to this question.
   5.959 +
   5.960 +Good-Bad DMA Model-Firmware (WIP)
   5.961 +CONFIG_IDEDMA_NEW_DRIVE_LISTINGS
   5.962 +  If you say Y here, the model and firmware revision of your drive
   5.963 +  will be compared against a blacklist of buggy drives that claim to
   5.964 +  be (U)DMA capable but aren't. This is a blanket on/off test with no
   5.965 +  speed limit options.
   5.966 +
   5.967 +  Straight GNU GCC 2.7.3/2.8.X compilers are known to be safe;
   5.968 +  whereas, many versions of EGCS have a problem and miscompile if you
   5.969 +  say Y here.
   5.970 +
   5.971 +  If in doubt, say N.
   5.972 +
   5.973 +Attempt to HACK around Chipsets that TIMEOUT (WIP)
   5.974 +CONFIG_BLK_DEV_IDEDMA_TIMEOUT
   5.975 +  If you say Y here, this is a NASTY UGLY HACK!
   5.976 +
   5.977 +  We have to issue an abort and requeue the request DMA engine got
   5.978 +  turned off by a goofy ASIC, and we have to clean up the mess, and
   5.979 +  here is as good as any.  Do it globally for all chipsets.
   5.980 +
   5.981 +  If in doubt, say N.
   5.982 +
   5.983 +Boot off-board chipsets first support
   5.984 +CONFIG_BLK_DEV_OFFBOARD
   5.985 +  Normally, IDE controllers built into the motherboard (on-board
   5.986 +  controllers) are assigned to ide0 and ide1 while those on add-in PCI
   5.987 +  cards (off-board controllers) are relegated to ide2 and ide3.
   5.988 +  Answering Y here will allow you to reverse the situation, with
   5.989 +  off-board controllers on ide0/1 and on-board controllers on ide2/3.
   5.990 +  This can improve the usability of some boot managers such as lilo
   5.991 +  when booting from a drive on an off-board controller.
   5.992 +
   5.993 +  If you say Y here, and you actually want to reverse the device scan
   5.994 +  order as explained above, you also need to issue the kernel command
   5.995 +  line option "ide=reverse". (Try "man bootparam" or see the
   5.996 +  documentation of your boot loader (lilo or loadlin) about how to
   5.997 +  pass options to the kernel at boot time.)
   5.998 +
   5.999 +  Note that, if you do this, the order of the hd* devices will be
  5.1000 +  rearranged which may require modification of fstab and other files.
  5.1001 +
  5.1002 +  If in doubt, say N.
  5.1003 +
  5.1004 +Use PCI DMA by default when available
  5.1005 +CONFIG_IDEDMA_PCI_AUTO
  5.1006 +  Prior to kernel version 2.1.112, Linux used to automatically use
  5.1007 +  DMA for IDE drives and chipsets which support it. Due to concerns
  5.1008 +  about a couple of cases where buggy hardware may have caused damage,
  5.1009 +  the default is now to NOT use DMA automatically. To revert to the
  5.1010 +  previous behaviour, say Y to this question.
  5.1011 +
  5.1012 +  If you suspect your hardware is at all flakey, say N here.
  5.1013 +  Do NOT email the IDE kernel people regarding this issue!
  5.1014 +
  5.1015 +  It is normally safe to answer Y to this question unless your
  5.1016 +  motherboard uses a VIA VP2 chipset, in which case you should say N.
  5.1017 +
  5.1018 +IGNORE word93 Validation BITS
  5.1019 +CONFIG_IDEDMA_IVB
  5.1020 +  There are unclear terms in ATA-4 and ATA-5 standards how certain
  5.1021 +  hardware (an 80c ribbon) should be detected. Different interpretations
  5.1022 +  of the standards have been released in hardware. This causes problems:
  5.1023 +  for example, a host with Ultra Mode 4 (or higher) will not run
  5.1024 +  in that mode with an 80c ribbon.
  5.1025 +
  5.1026 +  If you are experiencing compatibility or performance problems, you
  5.1027 +  MAY try to answering Y here. However, it does not necessarily solve
  5.1028 +  any of your problems, it could even cause more of them.
  5.1029 +
  5.1030 +  It is normally safe to answer Y; however, the default is N.
  5.1031 +
  5.1032 +ATA Work(s) In Progress (EXPERIMENTAL)
  5.1033 +CONFIG_IDEDMA_PCI_WIP
  5.1034 +  If you enable this you will be able to use and test highly
  5.1035 +  developmental projects. If you say N, the configurator will
  5.1036 +  simply skip those options.
  5.1037 +
  5.1038 +  It is SAFEST to say N to this question.
  5.1039 +
  5.1040 +Asynchronous DMA support (EXPERIMENTAL)
  5.1041 +CONFIG_BLK_DEV_ADMA
  5.1042 +  Please read the comments at the top of
  5.1043 +  <file:drivers/ide/ide-adma.c>.
  5.1044 +
  5.1045 +Pacific Digital A-DMA support (EXPERIMENTAL)
  5.1046 +CONFIG_BLK_DEV_PDC_ADMA
  5.1047 +  Please read the comments at the top of <file:drivers/ide/setup-pci.c>.
  5.1048 +
  5.1049 +3ware Hardware ATA-RAID support
  5.1050 +CONFIG_BLK_DEV_3W_XXXX_RAID
  5.1051 +  3ware is the only hardware ATA-Raid product in Linux to date.
  5.1052 +  This card is 2,4, or 8 channel master mode support only.
  5.1053 +  SCSI support required!!!
  5.1054 +
  5.1055 +  <http://www.3ware.com/>
  5.1056 +
  5.1057 +  Please read the comments at the top of
  5.1058 +  <file:drivers/scsi/3w-xxxx.c>.
  5.1059 +
  5.1060 +  If you want to compile the driver as a module ( = code which can be
  5.1061 +  inserted in and removed from the running kernel whenever you want),
  5.1062 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.1063 +  will be called 3w-xxxx.o.
  5.1064 +
  5.1065 +AEC62XX chipset support
  5.1066 +CONFIG_BLK_DEV_AEC62XX
  5.1067 +  This driver adds up to 4 more EIDE devices sharing a single
  5.1068 +  interrupt. This add-on card is a bootable PCI UDMA controller. In
  5.1069 +  order to get this card to initialize correctly in some cases, you
  5.1070 +  should say Y here, and preferably also to "Use DMA by default when
  5.1071 +  available".
  5.1072 +
  5.1073 +  The ATP850U/UF is an UltraDMA 33 chipset base.
  5.1074 +  The ATP860 is an UltraDMA 66 chipset base.
  5.1075 +  The ATP860M(acintosh) version is an UltraDMA 66 chipset base.
  5.1076 +
  5.1077 +  Please read the comments at the top of <file:drivers/ide/pci/aec62xx.c>.
  5.1078 +  If you say Y here, then say Y to "Use DMA by default when available"
  5.1079 +  as well.
  5.1080 +
  5.1081 +AEC62XX Tuning support
  5.1082 +CONFIG_AEC62XX_TUNING
  5.1083 +  Please read the comments at the top of <file:drivers/ide/pci/aec62xx.c>.
  5.1084 +  If unsure, say N.
  5.1085 +
  5.1086 +ALI M15x3 chipset support
  5.1087 +CONFIG_BLK_DEV_ALI15X3
  5.1088 +  This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C
  5.1089 +  onboard chipsets.  It also tests for Simplex mode and enables
  5.1090 +  normal dual channel support.
  5.1091 +
  5.1092 +  If you say Y here, you also need to say Y to "Use DMA by default
  5.1093 +  when available", above.  Please read the comments at the top of
  5.1094 +  <file:drivers/ide/pci/alim15x3.c>.
  5.1095 +
  5.1096 +  If unsure, say N.
  5.1097 +
  5.1098 +ALI M15x3 WDC support (DANGEROUS)
  5.1099 +CONFIG_WDC_ALI15X3
  5.1100 +  This allows for UltraDMA support for WDC drives that ignore CRC
  5.1101 +  checking. You are a fool for enabling this option, but there have
  5.1102 +  been requests. DO NOT COMPLAIN IF YOUR DRIVE HAS FS CORRUPTION, IF
  5.1103 +  YOU ENABLE THIS! No one will listen, just laugh for ignoring this
  5.1104 +  SERIOUS WARNING.
  5.1105 +
  5.1106 +  Using this option can allow WDC drives to run at ATA-4/5 transfer
  5.1107 +  rates with only an ATA-2 support structure.
  5.1108 +
  5.1109 +  SAY N!
  5.1110 +
  5.1111 +AMD and nVidia IDE support
  5.1112 +CONFIG_BLK_DEV_AMD74XX
  5.1113 +  This driver adds explicit support for AMD-7xx and AMD-8111 chips
  5.1114 +  and also for the nVidia nForce chip.  This allows the kernel to
  5.1115 +  change PIO, DMA and UDMA speeds and to configure the chip to
  5.1116 +  optimum performance.
  5.1117 +
  5.1118 +  If you say Y here, you also need to say Y to "Use DMA by default
  5.1119 +  when available", above.
  5.1120 +  Please read the comments at the top of <file:drivers/ide/pci/amd74xx.c>.
  5.1121 +
  5.1122 +  If unsure, say N.
  5.1123 +
  5.1124 +AMD Viper ATA-66 Override support (WIP)
  5.1125 +CONFIG_AMD74XX_OVERRIDE
  5.1126 +  This option auto-forces the ata66 flag.
  5.1127 +  This effect can be also invoked by calling "idex=ata66"
  5.1128 +  If unsure, say N.
  5.1129 +
  5.1130 +CMD64X/CMD680 chipset support
  5.1131 +CONFIG_BLK_DEV_CMD64X
  5.1132 +  Say Y here if you have an IDE controller which uses any of these
  5.1133 +  chipsets: CMD643, CMD646 and CMD648.
  5.1134 +
  5.1135 +CY82C693 chipset support
  5.1136 +CONFIG_BLK_DEV_CY82C693
  5.1137 +  This driver adds detection and support for the CY82C693 chipset
  5.1138 +  used on Digital's PC-Alpha 164SX boards.
  5.1139 +
  5.1140 +  If you say Y here, you need to say Y to "Use DMA by default
  5.1141 +  when available" as well.
  5.1142 +
  5.1143 +Cyrix CS5530 MediaGX chipset support
  5.1144 +CONFIG_BLK_DEV_CS5530
  5.1145 +  Include support for UDMA on the Cyrix MediaGX 5530 chipset. This
  5.1146 +  will automatically be detected and configured if found.
  5.1147 +
  5.1148 +  It is safe to say Y to this question.
  5.1149 +
  5.1150 +  People with SCSI-only systems should say N here. If unsure, say Y.
  5.1151 +
  5.1152 +HPT34X chipset support
  5.1153 +CONFIG_BLK_DEV_HPT34X
  5.1154 +  This driver adds up to 4 more EIDE devices sharing a single
  5.1155 +  interrupt. The HPT343 chipset in its current form is a non-bootable
  5.1156 +  controller; the HPT345/HPT363 chipset is a bootable (needs BIOS FIX)
  5.1157 +  PCI UDMA controllers. This driver requires dynamic tuning of the
  5.1158 +  chipset during the ide-probe at boot time. It is reported to support
  5.1159 +  DVD II drives, by the manufacturer.
  5.1160 +
  5.1161 +HPT34X AUTODMA support (WIP)
  5.1162 +CONFIG_HPT34X_AUTODMA
  5.1163 +  This is a dangerous thing to attempt currently! Please read the
  5.1164 +  comments at the top of <file:drivers/ide/pci/hpt34x.c>.  If you say Y
  5.1165 +  here, then say Y to "Use DMA by default when available" as well.
  5.1166 +
  5.1167 +  If unsure, say N.
  5.1168 +
  5.1169 +HPT36X/37X chipset support
  5.1170 +CONFIG_BLK_DEV_HPT366
  5.1171 +  HPT366 is an Ultra DMA chipset for ATA-66.
  5.1172 +  HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
  5.1173 +  HPT370 is an Ultra DMA chipset for ATA-100.
  5.1174 +  HPT372 is an Ultra DMA chipset for ATA-133.
  5.1175 +  HPT374 is an Ultra DMA chipset for ATA-133.
  5.1176 +
  5.1177 +  This driver adds up to 4 more EIDE devices sharing a single
  5.1178 +  interrupt.
  5.1179 +
  5.1180 +  The HPT366 chipset in its current form is bootable. One solution
  5.1181 +  for this problem are special LILO commands for redirecting the
  5.1182 +  reference to device 0x80. The other solution is to say Y to "Boot
  5.1183 +  off-board chipsets first support" (CONFIG_BLK_DEV_OFFBOARD) unless
  5.1184 +  your mother board has the chipset natively mounted. Regardless one
  5.1185 +  should use the fore mentioned option and call at LILO or include
  5.1186 +  "ide=reverse" in LILO's append-line.
  5.1187 +
  5.1188 +  This driver requires dynamic tuning of the chipset during the
  5.1189 +  ide-probe at boot. It is reported to support DVD II drives, by the
  5.1190 +  manufacturer.
  5.1191 +
  5.1192 +NS87415 chipset support (EXPERIMENTAL)
  5.1193 +CONFIG_BLK_DEV_NS87415
  5.1194 +  This driver adds detection and support for the NS87415 chip
  5.1195 +  (used in SPARC64, among others).
  5.1196 +
  5.1197 +  Please read the comments at the top of <file:drivers/ide/pci/ns87415.c>.
  5.1198 +
  5.1199 +OPTi 82C621 chipset enhanced support (EXPERIMENTAL)
  5.1200 +CONFIG_BLK_DEV_OPTI621
  5.1201 +  This is a driver for the OPTi 82C621 EIDE controller.
  5.1202 +  Please read the comments at the top of <file:drivers/ide/pci/opti621.c>.
  5.1203 +
  5.1204 +ServerWorks OSB4/CSB5 chipset support
  5.1205 +CONFIG_BLK_DEV_SVWKS
  5.1206 +  This driver adds PIO/(U)DMA support for the ServerWorks OSB4/CSB5
  5.1207 +  chipsets.
  5.1208 +
  5.1209 +Intel PIIXn chipsets support
  5.1210 +CONFIG_BLK_DEV_PIIX
  5.1211 +  This driver adds PIO mode setting and tuning for all PIIX IDE
  5.1212 +  controllers by Intel.  Since the BIOS can sometimes improperly tune
  5.1213 +  PIO 0-4 mode settings, this allows dynamic tuning of the chipset
  5.1214 +  via the standard end-user tool 'hdparm'.
  5.1215 +
  5.1216 +  Please read the comments at the top of <file:drivers/ide/pci/piix.c>.
  5.1217 +
  5.1218 +  If you say Y here, you should also say Y to "PIIXn Tuning support",
  5.1219 +  below.
  5.1220 +
  5.1221 +  If unsure, say N.
  5.1222 +
  5.1223 +PIIXn Tuning support
  5.1224 +CONFIG_PIIX_TUNING
  5.1225 +  This driver extension adds DMA mode setting and tuning for all PIIX
  5.1226 +  IDE controllers by Intel. Since the BIOS can sometimes improperly
  5.1227 +  set up the device/adapter combination and speed limits, it has
  5.1228 +  become a necessity to back/forward speed devices as needed.
  5.1229 +
  5.1230 +  Case 430HX/440FX PIIX3 need speed limits to reduce UDMA to DMA mode
  5.1231 +  2 if the BIOS can not perform this task at initialization.
  5.1232 +
  5.1233 +  If unsure, say N.
  5.1234 +
  5.1235 +PROMISE PDC20246/PDC20262/PDC20265/PDC20267/PDC20268 support
  5.1236 +CONFIG_BLK_DEV_PDC202XX_OLD
  5.1237 +  Promise Ultra33 or PDC20246
  5.1238 +  Promise Ultra66 or PDC20262
  5.1239 +  Promise Ultra100 or PDC20265/PDC20267/PDC20268
  5.1240 +
  5.1241 +  This driver adds up to 4 more EIDE devices sharing a single
  5.1242 +  interrupt. This add-on card is a bootable PCI UDMA controller. Since
  5.1243 +  multiple cards can be installed and there are BIOS ROM problems that
  5.1244 +  happen if the BIOS revisions of all installed cards (three-max) do
  5.1245 +  not match, the driver attempts to do dynamic tuning of the chipset
  5.1246 +  at boot-time for max-speed.  Ultra33 BIOS 1.25 or newer is required
  5.1247 +  for more than one card. This card may require that you say Y to
  5.1248 +  "Special UDMA Feature".
  5.1249 +
  5.1250 +  If you say Y here, you need to say Y to "Use DMA by default when
  5.1251 +  available" as well.
  5.1252 +
  5.1253 +  Please read the comments at the top of
  5.1254 +  <file:drivers/ide/pci/pdc202xx_old.c>.
  5.1255 +
  5.1256 +  If unsure, say N.
  5.1257 +
  5.1258 +Special UDMA Feature
  5.1259 +CONFIG_PDC202XX_BURST
  5.1260 +  This option causes the pdc202xx driver to enable UDMA modes on the
  5.1261 +  PDC202xx even when the PDC202xx BIOS has not done so.
  5.1262 +
  5.1263 +  It was originally designed for the PDC20246/Ultra33, whose BIOS will
  5.1264 +  only setup UDMA on the first two PDC20246 cards.  It has also been
  5.1265 +  used successfully on a PDC20265/Ultra100, allowing use of UDMA modes
  5.1266 +  when the PDC20265 BIOS has been disabled (for faster boot up).
  5.1267 +
  5.1268 +  Please read the comments at the top of
  5.1269 +  <file:drivers/ide/pci/pdc202xx_old.c>.
  5.1270 +
  5.1271 +  If unsure, say N.
  5.1272 +
  5.1273 +Special FastTrak Feature
  5.1274 +CONFIG_PDC202XX_FORCE
  5.1275 +  For FastTrak enable overriding BIOS.
  5.1276 +
  5.1277 +SiS5513 chipset support
  5.1278 +CONFIG_BLK_DEV_SIS5513
  5.1279 +  This driver ensures (U)DMA support for SIS5513 chipset family based
  5.1280 +  mainboards.
  5.1281 +
  5.1282 +  The following chipsets are supported:
  5.1283 +  ATA16:  SiS5511, SiS5513
  5.1284 +  ATA33:  SiS5591, SiS5597, SiS5598, SiS5600
  5.1285 +  ATA66:  SiS530, SiS540, SiS620, SiS630, SiS640
  5.1286 +  ATA100: SiS635, SiS645, SiS650, SiS730, SiS735, SiS740,
  5.1287 +          SiS745, SiS750
  5.1288 +
  5.1289 +  If you say Y here, you need to say Y to "Use DMA by default when
  5.1290 +  available" as well.
  5.1291 +
  5.1292 +  Please read the comments at the top of <file:drivers/ide/pci/sis5513.c>.
  5.1293 +
  5.1294 +Silicon Image chipset support
  5.1295 +CONFIG_BLK_DEV_SIIMAGE
  5.1296 +  This driver provides (U)DMA support for the SII3112 SATA controllers and
  5.1297 +  for the CMD/SI680 UDMA/DMA ATA controller.
  5.1298 +
  5.1299 +SLC90E66 chipset support
  5.1300 +CONFIG_BLK_DEV_SLC90E66
  5.1301 +  This driver ensures (U)DMA support for Victroy66 SouthBridges for
  5.1302 +  SMsC with Intel NorthBridges.  This is an Ultra66 based chipset.
  5.1303 +  The nice thing about it is that you can mix Ultra/DMA/PIO devices
  5.1304 +  and it will handle timing cycles.  Since this is an improved
  5.1305 +  look-a-like to the PIIX4 it should be a nice addition.
  5.1306 +
  5.1307 +  If you say Y here, you need to say Y to "Use DMA by default when
  5.1308 +  available" as well.
  5.1309 +
  5.1310 +  Please read the comments at the top of
  5.1311 +  <file:drivers/ide/pci/slc90e66.c>.
  5.1312 +
  5.1313 +Winbond SL82c105 support
  5.1314 +CONFIG_BLK_DEV_SL82C105
  5.1315 +  If you have a Winbond SL82c105 IDE controller, say Y here to enable
  5.1316 +  special configuration for this chip. This is common on various CHRP
  5.1317 +  motherboards, but could be used elsewhere. If in doubt, say Y.
  5.1318 +
  5.1319 +Tekram TRM290 chipset support
  5.1320 +CONFIG_BLK_DEV_TRM290
  5.1321 +  This driver adds support for bus master DMA transfers
  5.1322 +  using the Tekram TRM290 PCI IDE chip. Volunteers are
  5.1323 +  needed for further tweaking and development.
  5.1324 +  Please read the comments at the top of <file:drivers/ide/pci/trm290.c>.
  5.1325 +
  5.1326 +VIA82CXXX chipset support
  5.1327 +CONFIG_BLK_DEV_VIA82CXXX
  5.1328 +  This allows you to configure your chipset for a better use while
  5.1329 +  running PIO/(U)DMA, it will allow you to enable efficiently the
  5.1330 +  second channel dma usage, as it may not be set by BIOS.  It will try
  5.1331 +  to set fifo configuration at its best.  It will allow you to get
  5.1332 +  information from /proc/ide/via provided you enabled "/proc file
  5.1333 +  system" support.
  5.1334 +
  5.1335 +  Please read the comments at the top of
  5.1336 +  <file:drivers/ide/pci/via82cxxx.c>.
  5.1337 +
  5.1338 +  If you say Y here, then say Y to "Use DMA by default when available"
  5.1339 +  as well.
  5.1340 +
  5.1341 +  If unsure, say N.
  5.1342 +
  5.1343 +RapIDE interface support
  5.1344 +CONFIG_BLK_DEV_IDE_RAPIDE
  5.1345 +  Say Y here if you want to support the Yellowstone RapIDE controller
  5.1346 +  manufactured for use with Acorn computers.
  5.1347 +
  5.1348 +Other IDE chipset support
  5.1349 +CONFIG_IDE_CHIPSETS
  5.1350 +  Say Y here if you want to include enhanced support for various IDE
  5.1351 +  interface chipsets used on motherboards and add-on cards. You can
  5.1352 +  then pick your particular IDE chip from among the following options.
  5.1353 +  This enhanced support may be necessary for Linux to be able to
  5.1354 +  access the 3rd/4th drives in some systems. It may also enable
  5.1355 +  setting of higher speed I/O rates to improve system performance with
  5.1356 +  these chipsets. Most of these also require special kernel boot
  5.1357 +  parameters to actually turn on the support at runtime; you can find
  5.1358 +  a list of these in the file <file:Documentation/ide.txt>.
  5.1359 +
  5.1360 +  People with SCSI-only systems can say N here.
  5.1361 +
  5.1362 +Generic 4 drives/port support
  5.1363 +CONFIG_BLK_DEV_4DRIVES
  5.1364 +  Certain older chipsets, including the Tekram 690CD, use a single set
  5.1365 +  of I/O ports at 0x1f0 to control up to four drives, instead of the
  5.1366 +  customary two drives per port. Support for this can be enabled at
  5.1367 +  runtime using the "ide0=four" kernel boot parameter if you say Y
  5.1368 +  here.
  5.1369 +
  5.1370 +ALI M14xx support
  5.1371 +CONFIG_BLK_DEV_ALI14XX
  5.1372 +  This driver is enabled at runtime using the "ide0=ali14xx" kernel
  5.1373 +  boot parameter.  It enables support for the secondary IDE interface
  5.1374 +  of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
  5.1375 +  I/O speeds to be set as well.  See the files
  5.1376 +  <file:Documentation/ide.txt> and <file:drivers/ide/legacy/ali14xx.c> for
  5.1377 +  more info.
  5.1378 +
  5.1379 +DTC-2278 support
  5.1380 +CONFIG_BLK_DEV_DTC2278
  5.1381 +  This driver is enabled at runtime using the "ide0=dtc2278" kernel
  5.1382 +  boot parameter. It enables support for the secondary IDE interface
  5.1383 +  of the DTC-2278 card, and permits faster I/O speeds to be set as
  5.1384 +  well. See the <file:Documentation/ide.txt> and
  5.1385 +  <file:drivers/ide/legacy/dtc2278.c> files for more info.
  5.1386 +
  5.1387 +Holtek HT6560B support
  5.1388 +CONFIG_BLK_DEV_HT6560B
  5.1389 +  This driver is enabled at runtime using the "ide0=ht6560b" kernel
  5.1390 +  boot parameter. It enables support for the secondary IDE interface
  5.1391 +  of the Holtek card, and permits faster I/O speeds to be set as well.
  5.1392 +  See the <file:Documentation/ide.txt> and
  5.1393 +  <file:drivers/ide/legacy/ht6560b.c> files for more info.
  5.1394 +
  5.1395 +PROMISE DC4030 support (EXPERIMENTAL)
  5.1396 +CONFIG_BLK_DEV_PDC4030
  5.1397 +  This driver provides support for the secondary IDE interface and
  5.1398 +  cache of Promise IDE chipsets, e.g. DC4030 and DC5030.  This driver
  5.1399 +  is known to incur timeouts/retries during heavy I/O to drives
  5.1400 +  attached to the secondary interface.  CD-ROM and TAPE devices are
  5.1401 +  not supported yet.  This driver is enabled at runtime using the
  5.1402 +  "ide0=dc4030" kernel boot parameter.  See the
  5.1403 +  <file:Documentation/ide.txt> and <file:drivers/ide/legacy/pdc4030.c> files
  5.1404 +  for more info.
  5.1405 +
  5.1406 +QDI QD65XX support
  5.1407 +CONFIG_BLK_DEV_QD65XX
  5.1408 +  This driver is enabled at runtime using the "ide0=qd65xx" kernel
  5.1409 +  boot parameter.  It permits faster I/O speeds to be set.  See the
  5.1410 +  <file:Documentation/ide.txt> and <file:drivers/ide/legacy/qd65xx.c> for
  5.1411 +  more info.
  5.1412 +
  5.1413 +UMC 8672 support
  5.1414 +CONFIG_BLK_DEV_UMC8672
  5.1415 +  This driver is enabled at runtime using the "ide0=umc8672" kernel
  5.1416 +  boot parameter. It enables support for the secondary IDE interface
  5.1417 +  of the UMC-8672, and permits faster I/O speeds to be set as well.
  5.1418 +  See the files <file:Documentation/ide.txt> and
  5.1419 +  <file:drivers/ide/legacy/umc8672.c> for more info.
  5.1420 +
  5.1421 +Amiga Gayle IDE interface support
  5.1422 +CONFIG_BLK_DEV_GAYLE
  5.1423 +  This is the IDE driver for the builtin IDE interface on some Amiga
  5.1424 +  models. It supports both the `A1200 style' (used in A600 and A1200)
  5.1425 +  and `A4000 style' (used in A4000 and A4000T) of the Gayle IDE
  5.1426 +  interface. Say Y if you have such an Amiga model and want to use IDE
  5.1427 +  devices (hard disks, CD-ROM drives, etc.) that are connected to the
  5.1428 +  builtin IDE interface.
  5.1429 +
  5.1430 +Falcon IDE interface support
  5.1431 +CONFIG_BLK_DEV_FALCON_IDE
  5.1432 +  This is the IDE driver for the builtin IDE interface on the Atari
  5.1433 +  Falcon. Say Y if you have a Falcon and want to use IDE devices (hard
  5.1434 +  disks, CD-ROM drives, etc.) that are connected to the builtin IDE
  5.1435 +  interface.
  5.1436 +
  5.1437 +Amiga Buddha/Catweasel/X-Surf IDE interface support (EXPERIMENTAL)
  5.1438 +CONFIG_BLK_DEV_BUDDHA
  5.1439 +  This is the IDE driver for the IDE interfaces on the Buddha, 
  5.1440 +  Catweasel and X-Surf expansion boards.  It supports up to two interfaces 
  5.1441 +  on the Buddha, three on the Catweasel and two on the X-Surf.
  5.1442 +
  5.1443 +  Say Y if you have a Buddha or Catweasel expansion board and want to
  5.1444 +  use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
  5.1445 +  to one of its IDE interfaces.
  5.1446 +
  5.1447 +Amiga IDE Doubler support (EXPERIMENTAL)
  5.1448 +CONFIG_BLK_DEV_IDEDOUBLER
  5.1449 +  This driver provides support for the so-called `IDE doublers' (made
  5.1450 +  by various manufacturers, e.g. Eyetech) that can be connected to the
  5.1451 +  builtin IDE interface of some Amiga models. Using such an IDE
  5.1452 +  doubler, you can connect up to four instead of two IDE devices on
  5.1453 +  the Amiga's builtin IDE interface.
  5.1454 +
  5.1455 +  Note that the normal Amiga Gayle IDE driver may not work correctly
  5.1456 +  if you have an IDE doubler and don't enable this driver!
  5.1457 +
  5.1458 +  Say Y if you have an IDE doubler.  The driver is enabled at kernel
  5.1459 +  runtime using the "ide=doubler" kernel boot parameter.
  5.1460 +
  5.1461 +WarpEngine SCSI support
  5.1462 +CONFIG_WARPENGINE_SCSI
  5.1463 +  Support for MacroSystem Development's WarpEngine Amiga SCSI-2
  5.1464 +  controller. Info at
  5.1465 +  <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>.
  5.1466 +
  5.1467 +Builtin PowerMac IDE support
  5.1468 +CONFIG_BLK_DEV_IDE_PMAC
  5.1469 +  This driver provides support for the built-in IDE controller on
  5.1470 +  most of the recent Apple Power Macintoshes and PowerBooks.
  5.1471 +  If unsure, say Y.
  5.1472 +
  5.1473 +PowerMac IDE DMA support
  5.1474 +CONFIG_BLK_DEV_IDEDMA_PMAC
  5.1475 +  This option allows the driver for the built-in IDE controller on
  5.1476 +  Power Macintoshes and PowerBooks to use DMA (direct memory access)
  5.1477 +  to transfer data to and from memory.  Saying Y is safe and improves
  5.1478 +  performance.
  5.1479 +
  5.1480 +Use DMA by default
  5.1481 +CONFIG_BLK_DEV_IDEDMA_PMAC_AUTO
  5.1482 +  This option allows the driver for the built-in IDE controller on
  5.1483 +  Power Macintoshes and PowerBooks to use DMA automatically, without
  5.1484 +  it having to be explicitly enabled.  This option is provided because
  5.1485 +  of concerns about a couple of cases where using DMA on buggy PC
  5.1486 +  hardware may have caused damage.  Saying Y should be safe on all
  5.1487 +  Apple machines.
  5.1488 +
  5.1489 +Macintosh Quadra/Powerbook IDE interface support
  5.1490 +CONFIG_BLK_DEV_MAC_IDE
  5.1491 +  This is the IDE driver for the builtin IDE interface on some m68k
  5.1492 +  Macintosh models. It supports both the `Quadra style' (used in
  5.1493 +  Quadra/ Centris 630 and Performa 588 models) and `Powerbook style'
  5.1494 +  (used in the Powerbook 150 and 190 models) IDE interface.
  5.1495 +
  5.1496 +  Say Y if you have such an Macintosh model and want to use IDE
  5.1497 +  devices (hard disks, CD-ROM drives, etc.) that are connected to the
  5.1498 +  builtin IDE interface.
  5.1499 +
  5.1500 +ICS IDE interface support
  5.1501 +CONFIG_BLK_DEV_IDE_ICSIDE
  5.1502 +  On Acorn systems, say Y here if you wish to use the ICS IDE
  5.1503 +  interface card.  This is not required for ICS partition support.
  5.1504 +  If you are unsure, say N to this.
  5.1505 +
  5.1506 +ICS DMA support
  5.1507 +CONFIG_BLK_DEV_IDEDMA_ICS
  5.1508 +  Say Y here if you want to add DMA (Direct Memory Access) support to
  5.1509 +  the ICS IDE driver.
  5.1510 +
  5.1511 +Use ICS DMA by default
  5.1512 +CONFIG_IDEDMA_ICS_AUTO
  5.1513 +  Prior to kernel version 2.1.112, Linux used to automatically use
  5.1514 +  DMA for IDE drives and chipsets which support it. Due to concerns
  5.1515 +  about a couple of cases where buggy hardware may have caused damage,
  5.1516 +  the default is now to NOT use DMA automatically. To revert to the
  5.1517 +  previous behaviour, say Y to this question.
  5.1518 +
  5.1519 +  If you suspect your hardware is at all flakey, say N here.
  5.1520 +  Do NOT email the IDE kernel people regarding this issue!
  5.1521 +
  5.1522 +XT hard disk support
  5.1523 +CONFIG_BLK_DEV_XD
  5.1524 +  Very old 8 bit hard disk controllers used in the IBM XT computer
  5.1525 +  will be supported if you say Y here.
  5.1526 +
  5.1527 +  If you want to compile the driver as a module ( = code which can be
  5.1528 +  inserted in and removed from the running kernel whenever you want),
  5.1529 +  say M here and read <file:Documentation/modules.txt>. The module
  5.1530 +  will be called xd.o.
  5.1531 +
  5.1532 +  It's pretty unlikely that you have one of these: say N.
  5.1533 +
  5.1534 +PS/2 ESDI hard disk support
  5.1535 +CONFIG_BLK_DEV_PS2
  5.1536 +  Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
  5.1537 +  hard disk.
  5.1538 +
  5.1539 +  If you want to compile the driver as a module ( = code which can be
  5.1540 +  inserted in and removed from the running kernel whenever you want),
  5.1541 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.1542 +  will be called ps2esdi.o.
  5.1543 +
  5.1544 +Mylex DAC960/DAC1100 PCI RAID Controller support
  5.1545 +CONFIG_BLK_DEV_DAC960
  5.1546 +  This driver adds support for the Mylex DAC960, AcceleRAID, and
  5.1547 +  eXtremeRAID PCI RAID controllers.  See the file
  5.1548 +  <file:Documentation/README.DAC960> for further information about
  5.1549 +  this driver.
  5.1550 +
  5.1551 +  If you want to compile the driver as a module ( = code which can be
  5.1552 +  inserted in and removed from the running kernel whenever you want),
  5.1553 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.1554 +  will be called DAC960.o.
  5.1555 +
  5.1556 +Parallel port IDE device support
  5.1557 +CONFIG_PARIDE
  5.1558 +  There are many external CD-ROM and disk devices that connect through
  5.1559 +  your computer's parallel port. Most of them are actually IDE devices
  5.1560 +  using a parallel port IDE adapter. This option enables the PARIDE
  5.1561 +  subsystem which contains drivers for many of these external drives.
  5.1562 +  Read <file:Documentation/paride.txt> for more information.
  5.1563 +
  5.1564 +  If you have said Y to the "Parallel-port support" configuration
  5.1565 +  option, you may share a single port between your printer and other
  5.1566 +  parallel port devices. Answer Y to build PARIDE support into your
  5.1567 +  kernel, or M if you would like to build it as a loadable module. If
  5.1568 +  your parallel port support is in a loadable module, you must build
  5.1569 +  PARIDE as a module. If you built PARIDE support into your kernel,
  5.1570 +  you may still build the individual protocol modules and high-level
  5.1571 +  drivers as loadable modules. If you build this support as a module,
  5.1572 +  it will be called paride.o.
  5.1573 +
  5.1574 +  To use the PARIDE support, you must say Y or M here and also to at
  5.1575 +  least one high-level driver (e.g. "Parallel port IDE disks",
  5.1576 +  "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
  5.1577 +  to at least one protocol driver (e.g. "ATEN EH-100 protocol",
  5.1578 +  "MicroSolutions backpack protocol", "DataStor Commuter protocol"
  5.1579 +  etc.).
  5.1580 +
  5.1581 +Parallel port IDE disks
  5.1582 +CONFIG_PARIDE_PD
  5.1583 +  This option enables the high-level driver for IDE-type disk devices
  5.1584 +  connected through a parallel port. If you chose to build PARIDE
  5.1585 +  support into your kernel, you may answer Y here to build in the
  5.1586 +  parallel port IDE driver, otherwise you should answer M to build
  5.1587 +  it as a loadable module. The module will be called pd.o. You
  5.1588 +  must also have at least one parallel port protocol driver in your
  5.1589 +  system. Among the devices supported by this driver are the SyQuest
  5.1590 +  EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack
  5.1591 +  hard drives from MicroSolutions.
  5.1592 +
  5.1593 +Parallel port ATAPI CD-ROMs
  5.1594 +CONFIG_PARIDE_PCD
  5.1595 +  This option enables the high-level driver for ATAPI CD-ROM devices
  5.1596 +  connected through a parallel port. If you chose to build PARIDE
  5.1597 +  support into your kernel, you may answer Y here to build in the
  5.1598 +  parallel port ATAPI CD-ROM driver, otherwise you should answer M to
  5.1599 +  build it as a loadable module. The module will be called pcd.o. You
  5.1600 +  must also have at least one parallel port protocol driver in your
  5.1601 +  system. Among the devices supported by this driver are the
  5.1602 +  MicroSolutions backpack CD-ROM drives and the Freecom Power CD. If
  5.1603 +  you have such a CD-ROM drive, you should also say Y or M to "ISO
  5.1604 +  9660 CD-ROM file system support" below, because that's the file
  5.1605 +  system used on CD-ROMs.
  5.1606 +
  5.1607 +Parallel port ATAPI disks
  5.1608 +CONFIG_PARIDE_PF
  5.1609 +  This option enables the high-level driver for ATAPI disk devices
  5.1610 +  connected through a parallel port. If you chose to build PARIDE
  5.1611 +  support into your kernel, you may answer Y here to build in the
  5.1612 +  parallel port ATAPI disk driver, otherwise you should answer M
  5.1613 +  to build it as a loadable module. The module will be called pf.o.
  5.1614 +  You must also have at least one parallel port protocol driver in
  5.1615 +  your system. Among the devices supported by this driver are the
  5.1616 +  MicroSolutions backpack PD/CD drive and the Imation Superdisk
  5.1617 +  LS-120 drive.
  5.1618 +
  5.1619 +Parallel port ATAPI tapes
  5.1620 +CONFIG_PARIDE_PT
  5.1621 +  This option enables the high-level driver for ATAPI tape devices
  5.1622 +  connected through a parallel port. If you chose to build PARIDE
  5.1623 +  support into your kernel, you may answer Y here to build in the
  5.1624 +  parallel port ATAPI disk driver, otherwise you should answer M
  5.1625 +  to build it as a loadable module. The module will be called pt.o.
  5.1626 +  You must also have at least one parallel port protocol driver in
  5.1627 +  your system. Among the devices supported by this driver is the
  5.1628 +  parallel port version of the HP 5GB drive.
  5.1629 +
  5.1630 +Parallel port generic ATAPI devices
  5.1631 +CONFIG_PARIDE_PG
  5.1632 +  This option enables a special high-level driver for generic ATAPI
  5.1633 +  devices connected through a parallel port. The driver allows user
  5.1634 +  programs, such as cdrtools, to send ATAPI commands directly to a
  5.1635 +  device.
  5.1636 +
  5.1637 +  If you chose to build PARIDE support into your kernel, you may
  5.1638 +  answer Y here to build in the parallel port generic ATAPI driver,
  5.1639 +  otherwise you should answer M to build it as a loadable module. The
  5.1640 +  module will be called pg.o.
  5.1641 +
  5.1642 +  You must also have at least one parallel port protocol driver in
  5.1643 +  your system.
  5.1644 +
  5.1645 +  This driver implements an API loosely related to the generic SCSI
  5.1646 +  driver. See <file:include/linux/pg.h>. for details.
  5.1647 +
  5.1648 +  You can obtain the most recent version of cdrtools from
  5.1649 +  <ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/>. Versions 1.6.1a3 and
  5.1650 +  later fully support this driver.
  5.1651 +
  5.1652 +ATEN EH-100 protocol
  5.1653 +CONFIG_PARIDE_ATEN
  5.1654 +  This option enables support for the ATEN EH-100 parallel port IDE
  5.1655 +  protocol. This protocol is used in some inexpensive low performance
  5.1656 +  parallel port kits made in Hong Kong. If you chose to build PARIDE
  5.1657 +  support into your kernel, you may answer Y here to build in the
  5.1658 +  protocol driver, otherwise you should answer M to build it as a
  5.1659 +  loadable module. The module will be called aten.o. You must also
  5.1660 +  have a high-level driver for the type of device that you want to
  5.1661 +  support.
  5.1662 +
  5.1663 +Micro Solutions BACKPACK Series 5 protocol
  5.1664 +CONFIG_PARIDE_BPCK
  5.1665 +  This option enables support for the Micro Solutions BACKPACK
  5.1666 +  parallel port Series 5 IDE protocol.  (Most BACKPACK drives made
  5.1667 +  before 1999 were Series 5) Series 5 drives will NOT always have the
  5.1668 +  Series noted on the bottom of the drive. Series 6 drivers will.
  5.1669 +
  5.1670 +  In other words, if your BACKPACK drive dosen't say "Series 6" on the
  5.1671 +  bottom, enable this option.
  5.1672 +
  5.1673 +  If you chose to build PARIDE support into your kernel, you may
  5.1674 +  answer Y here to build in the protocol driver, otherwise you should
  5.1675 +  answer M to build it as a loadable module.  The module will be
  5.1676 +  called bpck.o.  You must also have a high-level driver for the type
  5.1677 +  of device that you want to support.
  5.1678 +
  5.1679 +Micro Solutions BACKPACK Series 6 protocol
  5.1680 +CONFIG_PARIDE_BPCK6
  5.1681 +  This option enables support for the Micro Solutions BACKPACK
  5.1682 +  parallel port Series 6 IDE protocol.  (Most BACKPACK drives made
  5.1683 +  after 1999 were Series 6) Series 6 drives will have the Series noted
  5.1684 +  on the bottom of the drive.  Series 5 drivers don't always have it
  5.1685 +  noted.
  5.1686 +
  5.1687 +  In other words, if your BACKPACK drive says "Series 6" on the
  5.1688 +  bottom, enable this option.
  5.1689 +
  5.1690 +  If you chose to build PARIDE support into your kernel, you may
  5.1691 +  answer Y here to build in the protocol driver, otherwise you should
  5.1692 +  answer M to build it as a loadable module.  The module will be
  5.1693 +  called bpck6.o.  You must also have a high-level driver for the type
  5.1694 +  of device that you want to support.
  5.1695 +
  5.1696 +DataStor Commuter protocol
  5.1697 +CONFIG_PARIDE_COMM
  5.1698 +  This option enables support for the Commuter parallel port IDE
  5.1699 +  protocol from DataStor. If you chose to build PARIDE support
  5.1700 +  into your kernel, you may answer Y here to build in the protocol
  5.1701 +  driver, otherwise you should answer M to build it as a loadable
  5.1702 +  module. The module will be called comm.o. You must also have
  5.1703 +  a high-level driver for the type of device that you want to support.
  5.1704 +
  5.1705 +DataStor EP-2000 protocol
  5.1706 +CONFIG_PARIDE_DSTR
  5.1707 +  This option enables support for the EP-2000 parallel port IDE
  5.1708 +  protocol from DataStor. If you chose to build PARIDE support
  5.1709 +  into your kernel, you may answer Y here to build in the protocol
  5.1710 +  driver, otherwise you should answer M to build it as a loadable
  5.1711 +  module. The module will be called dstr.o. You must also have
  5.1712 +  a high-level driver for the type of device that you want to support.
  5.1713 +
  5.1714 +Shuttle EPAT/EPEZ protocol
  5.1715 +CONFIG_PARIDE_EPAT
  5.1716 +  This option enables support for the EPAT parallel port IDE protocol.
  5.1717 +  EPAT is a parallel port IDE adapter manufactured by Shuttle
  5.1718 +  Technology and widely used in devices from major vendors such as
  5.1719 +  Hewlett-Packard, SyQuest, Imation and Avatar. If you chose to build
  5.1720 +  PARIDE support into your kernel, you may answer Y here to build in
  5.1721 +  the protocol driver, otherwise you should answer M to build it as a
  5.1722 +  loadable module. The module will be called epat.o. You must also
  5.1723 +  have a high-level driver for the type of device that you want to
  5.1724 +  support.
  5.1725 +
  5.1726 +Shuttle EPAT c7/c8 extension
  5.1727 +CONFIG_PARIDE_EPATC8
  5.1728 +  This option enables support for the newer Shuttle EP1284 (aka c7 and
  5.1729 +  c8) chip. You need this if you are using any recent Imation SuperDisk
  5.1730 +  (LS-120) drive.
  5.1731 +
  5.1732 +Shuttle EPIA protocol
  5.1733 +CONFIG_PARIDE_EPIA
  5.1734 +  This option enables support for the (obsolete) EPIA parallel port
  5.1735 +  IDE protocol from Shuttle Technology. This adapter can still be
  5.1736 +  found in some no-name kits. If you chose to build PARIDE support
  5.1737 +  into your kernel, you may answer Y here to build in the protocol
  5.1738 +  driver, otherwise you should answer M to build it as a loadable
  5.1739 +  module. The module will be called epia.o. You must also have a
  5.1740 +  high-level driver for the type of device that you want to support.
  5.1741 +
  5.1742 +FIT TD-2000 protocol
  5.1743 +CONFIG_PARIDE_FIT2
  5.1744 +  This option enables support for the TD-2000 parallel port IDE
  5.1745 +  protocol from Fidelity International Technology. This is a simple
  5.1746 +  (low speed) adapter that is used in some portable hard drives. If
  5.1747 +  you chose to build PARIDE support into your kernel, you may answer Y
  5.1748 +  here to build in the protocol driver, otherwise you should answer M
  5.1749 +  to build it as a loadable module. The module will be called fit2.o.
  5.1750 +  You must also have a high-level driver for the type of device that
  5.1751 +  you want to support.
  5.1752 +
  5.1753 +FIT TD-3000 protocol
  5.1754 +CONFIG_PARIDE_FIT3
  5.1755 +  This option enables support for the TD-3000 parallel port IDE
  5.1756 +  protocol from Fidelity International Technology. This protocol is
  5.1757 +  used in newer models of their portable disk, CD-ROM and PD/CD
  5.1758 +  devices. If you chose to build PARIDE support into your kernel, you
  5.1759 +  may answer Y here to build in the protocol driver, otherwise you
  5.1760 +  should answer M to build it as a loadable module. The module will be
  5.1761 +  called fit3.o. You must also have a high-level driver for the type
  5.1762 +  of device that you want to support.
  5.1763 +
  5.1764 +Freecom IQ ASIC-2 protocol
  5.1765 +CONFIG_PARIDE_FRIQ
  5.1766 +  This option enables support for version 2 of the Freecom IQ parallel
  5.1767 +  port IDE adapter.  This adapter is used by the Maxell Superdisk
  5.1768 +  drive.  If you chose to build PARIDE support into your kernel, you
  5.1769 +  may answer Y here to build in the protocol driver, otherwise you
  5.1770 +  should answer M to build it as a loadable module. The module will be
  5.1771 +  called friq.o. You must also have a high-level driver for the type
  5.1772 +  of device that you want to support.
  5.1773 +
  5.1774 +FreeCom power protocol
  5.1775 +CONFIG_PARIDE_FRPW
  5.1776 +  This option enables support for the Freecom power parallel port IDE
  5.1777 +  protocol. If you chose to build PARIDE support into your kernel, you
  5.1778 +  may answer Y here to build in the protocol driver, otherwise you
  5.1779 +  should answer M to build it as a loadable module. The module will be
  5.1780 +  called frpw.o. You must also have a high-level driver for the type
  5.1781 +  of device that you want to support.
  5.1782 +
  5.1783 +KingByte KBIC-951A/971A protocols
  5.1784 +CONFIG_PARIDE_KBIC
  5.1785 +  This option enables support for the KBIC-951A and KBIC-971A parallel
  5.1786 +  port IDE protocols from KingByte Information Corp. KingByte's
  5.1787 +  adapters appear in many no-name portable disk and CD-ROM products,
  5.1788 +  especially in Europe. If you chose to build PARIDE support into your
  5.1789 +  kernel, you may answer Y here to build in the protocol driver,
  5.1790 +  otherwise you should answer M to build it as a loadable module. The
  5.1791 +  module will be called kbic.o. You must also have a high-level driver
  5.1792 +  for the type of device that you want to support.
  5.1793 +
  5.1794 +KT PHd protocol
  5.1795 +CONFIG_PARIDE_KTTI
  5.1796 +  This option enables support for the "PHd" parallel port IDE protocol
  5.1797 +  from KT Technology. This is a simple (low speed) adapter that is
  5.1798 +  used in some 2.5" portable hard drives. If you chose to build PARIDE
  5.1799 +  support into your kernel, you may answer Y here to build in the
  5.1800 +  protocol driver, otherwise you should answer M to build it as a
  5.1801 +  loadable module. The module will be called ktti.o. You must also
  5.1802 +  have a high-level driver for the type of device that you want to
  5.1803 +  support.
  5.1804 +
  5.1805 +OnSpec 90c20 protocol
  5.1806 +CONFIG_PARIDE_ON20
  5.1807 +  This option enables support for the (obsolete) 90c20 parallel port
  5.1808 +  IDE protocol from OnSpec (often marketed under the ValuStore brand
  5.1809 +  name). If you chose to build PARIDE support into your kernel, you
  5.1810 +  may answer Y here to build in the protocol driver, otherwise you
  5.1811 +  should answer M to build it as a loadable module. The module will
  5.1812 +  be called on20.o. You must also have a high-level driver for the
  5.1813 +  type of device that you want to support.
  5.1814 +
  5.1815 +OnSpec 90c26 protocol
  5.1816 +CONFIG_PARIDE_ON26
  5.1817 +  This option enables support for the 90c26 parallel port IDE protocol
  5.1818 +  from OnSpec Electronics (often marketed under the ValuStore brand
  5.1819 +  name). If you chose to build PARIDE support into your kernel, you
  5.1820 +  may answer Y here to build in the protocol driver, otherwise you
  5.1821 +  should answer M to build it as a loadable module. The module will be
  5.1822 +  called on26.o. You must also have a high-level driver for the type
  5.1823 +  of device that you want to support.
  5.1824 +
  5.1825 +Logical Volume Manager (LVM) support
  5.1826 +CONFIG_BLK_DEV_LVM
  5.1827 +  This driver lets you combine several hard disks, hard disk
  5.1828 +  partitions, multiple devices or even loop devices (for evaluation
  5.1829 +  purposes) into a volume group.  Imagine a volume group as a kind of
  5.1830 +  virtual disk. Logical volumes, which can be thought of as virtual
  5.1831 +  partitions, can be created in the volume group.  You can resize
  5.1832 +  volume groups and logical volumes after creation time, corresponding
  5.1833 +  to new capacity needs.  Logical volumes are accessed as block
  5.1834 +  devices named /dev/VolumeGroupName/LogicalVolumeName.
  5.1835 +
  5.1836 +  For details see <file:Documentation/LVM-HOWTO>.  You will need
  5.1837 +  supporting user space software; location is in
  5.1838 +  <file:Documentation/Changes>.
  5.1839 +
  5.1840 +  If you want to compile this support as a module ( = code which can
  5.1841 +  be inserted in and removed from the running kernel whenever you
  5.1842 +  want), say M here and read <file:Documentation/modules.txt>.  The
  5.1843 +  module will be called lvm-mod.o.
  5.1844 +
  5.1845 +Multiple devices driver support (RAID and LVM)
  5.1846 +CONFIG_MD
  5.1847 +  Support multiple physical spindles through a single logical device.
  5.1848 +  Required for RAID and logical volume management (LVM).
  5.1849 +
  5.1850 +Multiple devices driver support
  5.1851 +CONFIG_BLK_DEV_MD
  5.1852 +  This driver lets you combine several hard disk partitions into one
  5.1853 +  logical block device. This can be used to simply append one
  5.1854 +  partition to another one or to combine several redundant hard disks
  5.1855 +  into a RAID1/4/5 device so as to provide protection against hard
  5.1856 +  disk failures. This is called "Software RAID" since the combining of
  5.1857 +  the partitions is done by the kernel. "Hardware RAID" means that the
  5.1858 +  combining is done by a dedicated controller; if you have such a
  5.1859 +  controller, you do not need to say Y here.
  5.1860 +
  5.1861 +  More information about Software RAID on Linux is contained in the
  5.1862 +  Software RAID mini-HOWTO, available from
  5.1863 +  <http://www.tldp.org/docs.html#howto>. There you will also learn
  5.1864 +  where to get the supporting user space utilities raidtools.
  5.1865 +
  5.1866 +  This driver is also available as a module ( = code which can be
  5.1867 +  inserted in and removed from the running kernel whenever you want).
  5.1868 +  If you want to compile it as a module, say M here and read
  5.1869 +  <file:Documentation/modules.txt>. The module will be called
  5.1870 +  md.o
  5.1871 +
  5.1872 +  If unsure, say N.
  5.1873 +
  5.1874 +Linear (append) mode
  5.1875 +CONFIG_MD_LINEAR
  5.1876 +  If you say Y here, then your multiple devices driver will be able to
  5.1877 +  use the so-called linear mode, i.e. it will combine the hard disk
  5.1878 +  partitions by simply appending one to the other.
  5.1879 +
  5.1880 +  If you want to compile this as a module ( = code which can be
  5.1881 +  inserted in and removed from the running kernel whenever you want),
  5.1882 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.1883 +  will be called linear.o.
  5.1884 +
  5.1885 +  If unsure, say Y.
  5.1886 +
  5.1887 +RAID-0 (striping) mode
  5.1888 +CONFIG_MD_RAID0
  5.1889 +  If you say Y here, then your multiple devices driver will be able to
  5.1890 +  use the so-called raid0 mode, i.e. it will combine the hard disk
  5.1891 +  partitions into one logical device in such a fashion as to fill them
  5.1892 +  up evenly, one chunk here and one chunk there. This will increase
  5.1893 +  the throughput rate if the partitions reside on distinct disks.
  5.1894 +
  5.1895 +  Information about Software RAID on Linux is contained in the
  5.1896 +  Software-RAID mini-HOWTO, available from
  5.1897 +  <http://www.tldp.org/docs.html#howto>. There you will also
  5.1898 +  learn where to get the supporting user space utilities raidtools.
  5.1899 +
  5.1900 +  If you want to compile this as a module ( = code which can be
  5.1901 +  inserted in and removed from the running kernel whenever you want),
  5.1902 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.1903 +  will be called raid0.o.
  5.1904 +
  5.1905 +  If unsure, say Y.
  5.1906 +
  5.1907 +RAID-1 (mirroring) mode
  5.1908 +CONFIG_MD_RAID1
  5.1909 +  A RAID-1 set consists of several disk drives which are exact copies
  5.1910 +  of each other.  In the event of a mirror failure, the RAID driver
  5.1911 +  will continue to use the operational mirrors in the set, providing
  5.1912 +  an error free MD (multiple device) to the higher levels of the
  5.1913 +  kernel.  In a set with N drives, the available space is the capacity
  5.1914 +  of a single drive, and the set protects against a failure of (N - 1)
  5.1915 +  drives.
  5.1916 +
  5.1917 +  Information about Software RAID on Linux is contained in the
  5.1918 +  Software-RAID mini-HOWTO, available from
  5.1919 +  <http://www.tldp.org/docs.html#howto>.  There you will also
  5.1920 +  learn where to get the supporting user space utilities raidtools.
  5.1921 +
  5.1922 +  If you want to use such a RAID-1 set, say Y. This code is also
  5.1923 +  available as a module called raid1.o ( = code which can be inserted
  5.1924 +  in and removed from the running kernel whenever you want).  If you
  5.1925 +  want to compile it as a module, say M here and read
  5.1926 +  <file:Documentation/modules.txt>.
  5.1927 +
  5.1928 +  If unsure, say Y.
  5.1929 +
  5.1930 +RAID-4/RAID-5 mode
  5.1931 +CONFIG_MD_RAID5
  5.1932 +  A RAID-5 set of N drives with a capacity of C MB per drive provides
  5.1933 +  the capacity of C * (N - 1) MB, and protects against a failure
  5.1934 +  of a single drive. For a given sector (row) number, (N - 1) drives
  5.1935 +  contain data sectors, and one drive contains the parity protection.
  5.1936 +  For a RAID-4 set, the parity blocks are present on a single drive,
  5.1937 +  while a RAID-5 set distributes the parity across the drives in one
  5.1938 +  of the available parity distribution methods.
  5.1939 +
  5.1940 +  Information about Software RAID on Linux is contained in the
  5.1941 +  Software-RAID mini-HOWTO, available from
  5.1942 +  <http://www.tldp.org/docs.html#howto>. There you will also
  5.1943 +  learn where to get the supporting user space utilities raidtools.
  5.1944 +
  5.1945 +  If you want to use such a RAID-4/RAID-5 set, say Y. This code is
  5.1946 +  also available as a module called raid5.o ( = code which can be
  5.1947 +  inserted in and removed from the running kernel whenever you want).
  5.1948 +  If you want to compile it as a module, say M here and read
  5.1949 +  <file:Documentation/modules.txt>.
  5.1950 +
  5.1951 +  If unsure, say Y.
  5.1952 +
  5.1953 +Multipath I/O support
  5.1954 +CONFIG_MD_MULTIPATH
  5.1955 +  Multipath-IO is the ability of certain devices to address the same
  5.1956 +  physical disk over multiple 'IO paths'. The code ensures that such
  5.1957 +  paths can be defined and handled at runtime, and ensures that a
  5.1958 +  transparent failover to the backup path(s) happens if a IO errors
  5.1959 +  arrives on the primary path.
  5.1960 +
  5.1961 +  This driver is also available as a module ( = code which can be
  5.1962 +  inserted in and removed from the running kernel whenever you want).
  5.1963 +  If you want to compile it as a module, say M here and read
  5.1964 +  <file:Documentation/modules.txt>. The module will be called
  5.1965 +  multipath.o
  5.1966 +
  5.1967 +  If unsure, say N.
  5.1968 +
  5.1969 +Support for IDE Raid controllers
  5.1970 +CONFIG_BLK_DEV_ATARAID
  5.1971 +  Say Y or M if you have an IDE Raid controller and want linux
  5.1972 +  to use its softwareraid feature.  You must also select an
  5.1973 +  appropriate for your board low-level driver below.
  5.1974 +
  5.1975 +  Note, that Linux does not use the Raid implementation in BIOS, and
  5.1976 +  the main purpose for this feature is to retain compatibility and
  5.1977 +  data integrity with other OS-es, using the same disk array. Linux
  5.1978 +  has its own Raid drivers, which you should use if you need better
  5.1979 +  performance.
  5.1980 +
  5.1981 +  This driver is also available as a module ( = code which can be
  5.1982 +  inserted in and removed from the running kernel whenever you want).
  5.1983 +  If you want to compile it as a module, say M here and read
  5.1984 +  <file:Documentation/modules.txt>. The module will be called
  5.1985 +  ataraid.o
  5.1986 +
  5.1987 +Support Promise software RAID (Fasttrak(tm))
  5.1988 +CONFIG_BLK_DEV_ATARAID_PDC
  5.1989 +  Say Y or M if you have a Promise Fasttrak (tm) Raid controller
  5.1990 +  and want linux to use the softwareraid feature of this card.
  5.1991 +  This driver uses /dev/ataraid/dXpY (X and Y numbers) as device
  5.1992 +  names.
  5.1993 +
  5.1994 +  If you choose to compile this as a module, the module will be called
  5.1995 +  pdcraid.o.
  5.1996 +
  5.1997 +Highpoint 370 software RAID
  5.1998 +CONFIG_BLK_DEV_ATARAID_HPT
  5.1999 +  Say Y or M if you have a Highpoint HPT 370 Raid controller
  5.2000 +  and want linux to use the softwareraid feature of this card.
  5.2001 +  This driver uses /dev/ataraid/dXpY (X and Y numbers) as device
  5.2002 +  names.
  5.2003 +
  5.2004 +  If you choose to compile this as a module, the module will be called
  5.2005 +  hptraid.o.
  5.2006 +
  5.2007 +Support for Acer PICA 1 chipset
  5.2008 +CONFIG_ACER_PICA_61
  5.2009 +  This is a machine with a R4400 133/150 MHz CPU. To compile a Linux
  5.2010 +  kernel that runs on these, say Y here. For details about Linux on
  5.2011 +  the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
  5.2012 +  <http://oss.sgi.com/mips/>.
  5.2013 +
  5.2014 +Support for Algorithmics P4032 (EXPERIMENTAL)
  5.2015 +CONFIG_ALGOR_P4032
  5.2016 +  This is an evaluation board of the British company Algorithmics.
  5.2017 +  The board uses the R4300 and a R5230 CPUs.  For more information
  5.2018 +  about this board see <http://www.algor.co.uk/>.
  5.2019 +
  5.2020 +Support for BAGET MIPS series
  5.2021 +CONFIG_BAGET_MIPS
  5.2022 +  This enables support for the Baget, a Russian embedded system.  For
  5.2023 +  more details about the Baget see the Linux/MIPS FAQ on
  5.2024 +  <http://oss.sgi.com/mips/>.
  5.2025 +
  5.2026 +Baget AMD LANCE support
  5.2027 +CONFIG_BAGETLANCE
  5.2028 +  Say Y to enable kernel support for AMD Lance Ethernet cards on the
  5.2029 +  MIPS-32-based Baget embedded system.  This chipset is better known
  5.2030 +  via the NE2100 cards.
  5.2031 +
  5.2032 +Support for DECstations
  5.2033 +CONFIG_DECSTATION
  5.2034 +  This enables support for DEC's MIPS based workstations.  For details
  5.2035 +  see the Linux/MIPS FAQ on <http://oss.sgi.com/mips/> and the
  5.2036 +  DECstation porting pages on <http://decstation.unix-ag.org/>.
  5.2037 +
  5.2038 +  If you have one of the following DECstation Models you definitely
  5.2039 +  want to choose R4xx0 for the CPU Type:
  5.2040 +
  5.2041 +	DECstation 5000/50
  5.2042 +	DECstation 5000/150
  5.2043 +	DECstation 5000/260
  5.2044 +	DECsystem 5900/260
  5.2045 +
  5.2046 +  otherwise choose R3000.
  5.2047 +
  5.2048 +Support for Cobalt Micro Server
  5.2049 +CONFIG_COBALT_MICRO_SERVER
  5.2050 +  Support for MIPS-based Cobalt boxes (they have been bought by Sun
  5.2051 +  and are now the "Server Appliance Business Unit") including the 2700
  5.2052 +  series -- versions 1 of the Qube and Raq.  To compile a Linux kernel
  5.2053 +  for this hardware, say Y here.
  5.2054 +
  5.2055 +Support for Cobalt 2800
  5.2056 +CONFIG_COBALT_28
  5.2057 +  Support for the second generation of MIPS-based Cobalt boxes (they
  5.2058 +  have been bought by Sun and are now the "Server Appliance Business
  5.2059 +  Unit") including the 2800 series -- versions 2 of the Qube and Raq.
  5.2060 +  To compile a Linux kernel for this hardware, say Y here.
  5.2061 +
  5.2062 +Support for the Momentum Computer Ocelot SBC
  5.2063 +CONFIG_MOMENCO_OCELOT
  5.2064 +  The Ocelot is a MIPS-based Single Board Computer (SBC) made by
  5.2065 +  Momentum Computer <http://www.momenco.com/>.
  5.2066 +
  5.2067 +Support for NEC DDB Vrc-5074
  5.2068 +CONFIG_DDB5074
  5.2069 +  This enables support for the VR5000-based NEC DDB Vrc-5074
  5.2070 +  evaluation board.
  5.2071 +
  5.2072 +Support for NEC DDB Vrc-5476
  5.2073 +CONFIG_DDB5476
  5.2074 +  This enables support for the R5432-based NEC DDB Vrc-5476
  5.2075 +  evaluation board.
  5.2076 +
  5.2077 +  Features : kernel debugging, serial terminal, NFS root fs, on-board
  5.2078 +  ether port (Need an additional patch at <http://linux.junsun.net/>),
  5.2079 +  USB, AC97, PCI, PCI VGA card & framebuffer console, IDE controller,
  5.2080 +  PS2 keyboard, PS2 mouse, etc.
  5.2081 +
  5.2082 +Support for NEC DDB Vrc-5477
  5.2083 +CONFIG_DDB5477
  5.2084 +  This enables support for the R5432-based NEC DDB Vrc-5477
  5.2085 +  evaluation board.
  5.2086 +
  5.2087 +  Features : kernel debugging, serial terminal, NFS root fs, on-board
  5.2088 +  ether port (Need an additional patch at <http://linux.junsun.net/>),
  5.2089 +  USB, AC97, PCI, etc.
  5.2090 +
  5.2091 +Support for MIPS Atlas board
  5.2092 +CONFIG_MIPS_ATLAS
  5.2093 +  This enables support for the QED R5231-based MIPS Atlas evaluation
  5.2094 +  board.
  5.2095 +
  5.2096 +Support for MIPS Malta board
  5.2097 +CONFIG_MIPS_MALTA
  5.2098 +  This enables support for the VR5000-based MIPS Malta evaluation
  5.2099 +  board.
  5.2100 +
  5.2101 +Support for Galileo Evaluation board or CoSine Orion
  5.2102 +CONFIG_ORION
  5.2103 +  Say Y if configuring for the Galileo evaluation board
  5.2104 +  or CoSine Orion.  More information is available at
  5.2105 +  <http://tochna.technion.ac.il/project/linux/html/linux.html>.
  5.2106 +
  5.2107 +  Otherwise, say N.
  5.2108 +
  5.2109 +Support for Mips Magnum 4000
  5.2110 +CONFIG_MIPS_MAGNUM_4000
  5.2111 +  This is a machine with a R4000 100 MHz CPU. To compile a Linux
  5.2112 +  kernel that runs on these, say Y here. For details about Linux on
  5.2113 +  the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
  5.2114 +  <http://oss.sgi.com/mips/>.
  5.2115 +
  5.2116 +Enable Qtronix 990P Keyboard Support
  5.2117 +CONFIG_QTRONIX_KEYBOARD
  5.2118 +  Images of Qtronix keyboards are at
  5.2119 +  <http://www.qtronix.com/keyboard.html>.
  5.2120 +
  5.2121 +Support for Olivetti M700
  5.2122 +CONFIG_OLIVETTI_M700
  5.2123 +  This is a machine with a R4000 100 MHz CPU. To compile a Linux
  5.2124 +  kernel that runs on these, say Y here. For details about Linux on
  5.2125 +  the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
  5.2126 +  <http://oss.sgi.com/mips/>.
  5.2127 +
  5.2128 +Support for SNI RM200 PCI
  5.2129 +CONFIG_SNI_RM200_PCI
  5.2130 +  The SNI RM200 PCI was a MIPS-based platform manufactured by Siemens
  5.2131 +  Nixdorf Informationssysteme (SNI), parent company of Pyramid
  5.2132 +  Technology and now in turn merged with Fujitsu.  Say Y here to
  5.2133 +  support this machine type.
  5.2134 +
  5.2135 +Support for SGI-IP22 (Indy/Indigo2)
  5.2136 +CONFIG_SGI_IP22
  5.2137 +  This are the SGI Indy, Challenge S and Indigo2, as well as certain
  5.2138 +  OEM variants like the Tandem CMN B006S. To compile a Linux kernel
  5.2139 +  that runs on these, say Y here.
  5.2140 +
  5.2141 +Support for SGI IP27 (Origin200/2000)
  5.2142 +CONFIG_SGI_IP27
  5.2143 +  This are the SGI Origin 200, Origin 2000 and Onyx 2 Graphics
  5.2144 +  workstations.  To compile a Linux kernel that runs on these, say Y
  5.2145 +  here.
  5.2146 +
  5.2147 +IP27 N-Mode
  5.2148 +CONFIG_SGI_SN0_N_MODE
  5.2149 +  The nodes of Origin 200, Origin 2000 and Onyx 2 systems can be
  5.2150 +  configured in either N-Modes which allows for more nodes or M-Mode
  5.2151 +  which allows for more memory.  Your system is most probably
  5.2152 +  running in M-Mode, so you should say N here.
  5.2153 +
  5.2154 +Lasi Ethernet
  5.2155 +CONFIG_LASI_82596
  5.2156 +  Say Y here to support the on-board Intel 82596 ethernet controller
  5.2157 +  built into Hewlett-Packard PA-RISC machines.
  5.2158 +
  5.2159 +MIPS JAZZ onboard SONIC Ethernet support
  5.2160 +CONFIG_MIPS_JAZZ_SONIC
  5.2161 +  This is the driver for the onboard card of MIPS Magnum 4000,
  5.2162 +  Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
  5.2163 +
  5.2164 +MIPS JAZZ FAS216 SCSI support
  5.2165 +CONFIG_JAZZ_ESP
  5.2166 +  This is the driver for the onboard SCSI host adapter of MIPS Magnum
  5.2167 +  4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
  5.2168 +  systems.
  5.2169 +
  5.2170 +MIPS GT96100 support
  5.2171 +CONFIG_MIPS_GT96100
  5.2172 +  Say Y here to support the Galileo Technology GT96100 communications
  5.2173 +  controller card.  There is a web page at <http://www.galileot.com/>.
  5.2174 +
  5.2175 +MIPS GT96100 Ethernet support
  5.2176 +CONFIG_MIPS_GT96100ETH
  5.2177 +  Say Y here to support the Ethernet subsystem on your GT96100 card.
  5.2178 +
  5.2179 +Zalon SCSI support
  5.2180 +CONFIG_SCSI_ZALON
  5.2181 +  The Zalon is an interface chip that sits between the PA-RISC
  5.2182 +  processor and the NCR 53c720 SCSI controller on K-series PA-RISC
  5.2183 +  boards (these are used, among other places, on some HP 780
  5.2184 +  workstations).  Say Y here to make sure it gets initialized
  5.2185 +  correctly before the Linux kernel tries to talk to the controller.
  5.2186 +
  5.2187 +Kernel floating-point instruction emulation
  5.2188 +CONFIG_MIPS_FPU_EMULATOR
  5.2189 +  This option enables the MIPS software floating support.  Due to
  5.2190 +  the way floating point works you should always enable this option
  5.2191 +  unless you exactly know what you're doing.
  5.2192 +
  5.2193 +SGI PROM Console Support
  5.2194 +CONFIG_SGI_PROM_CONSOLE
  5.2195 +  Say Y here to set up the boot console on serial port 0.
  5.2196 +
  5.2197 +DZ11 Serial Support
  5.2198 +CONFIG_DZ
  5.2199 +  DZ11-family serial controllers for VAXstations, including the
  5.2200 +  DC7085, M7814, and M7819.
  5.2201 +
  5.2202 +TURBOchannel support
  5.2203 +CONFIG_TC
  5.2204 +  TurboChannel is a DEC (now Compaq) bus for Alpha and MIPS processors.
  5.2205 +  Documentation on writing device drivers for TurboChannel is available at:
  5.2206 +  <http://www.cs.arizona.edu/computer.help/policy/DIGITAL_unix/AA-PS3HD-TET1_html/TITLE.html>.
  5.2207 +
  5.2208 +# Choice: galileo_clock
  5.2209 +75
  5.2210 +CONFIG_SYSCLK_75
  5.2211 +  Configure the kernel for clock speed of your Galileo board.  
  5.2212 +  The choices are 75MHz, 83.3MHz, and 100MHz.
  5.2213 +
  5.2214 +83.3
  5.2215 +CONFIG_SYSCLK_83
  5.2216 +  Configure the Galileo kernel for a clock speed of 83.3 MHz.
  5.2217 +
  5.2218 +100
  5.2219 +CONFIG_SYSCLK_100
  5.2220 +  Configure the Galileo kernel for a clock speed of 100 MHz.
  5.2221 +
  5.2222 +Z85C30 Serial Support
  5.2223 +CONFIG_ZS
  5.2224 +  Documentation on the Zilog 85C350 serial communications controller
  5.2225 +  is downloadable at <http://www.zilog.com/pdfs/serial/z85c30.pdf>.
  5.2226 +
  5.2227 +PCMCIA SCSI adapter support
  5.2228 +CONFIG_SCSI_PCMCIA
  5.2229 +  Say Y here if you intend to attach a PCMCIA or CardBus card to your
  5.2230 +  computer which acts as a SCSI host adapter. These are credit card
  5.2231 +  size devices often used with laptops.
  5.2232 +
  5.2233 +  Note that the answer to this question won't directly affect the
  5.2234 +  kernel: saying N will just cause the configurator to skip all
  5.2235 +  the questions PCMCIA SCSI host adapters.
  5.2236 +
  5.2237 +Adaptec APA1480 CardBus support
  5.2238 +CONFIG_PCMCIA_APA1480
  5.2239 +  Say Y here if you intend to attach this type of CardBus SCSI host
  5.2240 +  adapter to your computer.
  5.2241 +
  5.2242 +  This driver is also available as a module called apa1480_cb.o ( =
  5.2243 +  code which can be inserted in and removed from the running kernel
  5.2244 +  whenever you want). If you want to compile it as a module, say M
  5.2245 +  here and read <file:Documentation/modules.txt>.
  5.2246 +
  5.2247 +NinjaSCSI-3 / NinjaSCSI-32Bi (16bit) PCMCIA support
  5.2248 +CONFIG_PCMCIA_NINJA_SCSI
  5.2249 +  If you intend to attach this type of PCMCIA SCSI host adapter to
  5.2250 +  your computer, say Y here and read
  5.2251 +  <file:Documentation/README.nsp_cs.eng>.
  5.2252 +
  5.2253 +  This driver is also available as a module called nsp_cs.o ( =
  5.2254 +  code which can be inserted in and removed from the running kernel
  5.2255 +  whenever you want). If you want to compile it as a module, say M
  5.2256 +  here and read <file:Documentation/modules.txt>.
  5.2257 +
  5.2258 +Adaptec AHA152X PCMCIA support
  5.2259 +CONFIG_PCMCIA_AHA152X
  5.2260 +  Say Y here if you intend to attach this type of PCMCIA SCSI host
  5.2261 +  adapter to your computer.
  5.2262 +
  5.2263 +  This driver is also available as a module called aha152x_cs.o ( =
  5.2264 +  code which can be inserted in and removed from the running kernel
  5.2265 +  whenever you want). If you want to compile it as a module, say M
  5.2266 +  here and read <file:Documentation/modules.txt>.
  5.2267 +
  5.2268 +Qlogic PCMCIA support
  5.2269 +CONFIG_PCMCIA_QLOGIC
  5.2270 +  Say Y here if you intend to attach this type of PCMCIA SCSI host
  5.2271 +  adapter to your computer.
  5.2272 +
  5.2273 +  This driver is also available as a module called qlogic_cs.o ( =
  5.2274 +  code which can be inserted in and removed from the running kernel
  5.2275 +  whenever you want).  If you want to compile it as a module, say M
  5.2276 +  here and read <file:Documentation/modules.txt>.
  5.2277 +
  5.2278 +Future Domain PCMCIA support
  5.2279 +CONFIG_PCMCIA_FDOMAIN
  5.2280 +  Say Y here if you intend to attach this type of PCMCIA SCSI host
  5.2281 +  adapter to your computer.
  5.2282 +
  5.2283 +  This driver is also available as a module called fdomain_cs.o ( =
  5.2284 +  code which can be inserted in and removed from the running kernel
  5.2285 +  whenever you want).  If you want to compile it as a module, say M
  5.2286 +  here and read <file:Documentation/modules.txt>.
  5.2287 +
  5.2288 +# Choice: mipstype
  5.2289 +CPU type
  5.2290 +CONFIG_CPU_R3000
  5.2291 +  Please make sure to pick the right CPU type. Linux/MIPS is not
  5.2292 +  designed to be generic, i.e. Kernels compiled for R3000 CPUs will
  5.2293 +  *not* work on R4000 machines and vice versa.  However, since most
  5.2294 +  of the supported machines have an R4000 (or similar) CPU, R4x00
  5.2295 +  might be a safe bet.  If the resulting kernel does not work,
  5.2296 +  try to recompile with R3000.
  5.2297 +
  5.2298 +  R3000    MIPS Technologies R3000-series processors,
  5.2299 +           including the 3041, 3051, and 3081.
  5.2300 +
  5.2301 +  R6000    MIPS Technologies R6000-series processors,
  5.2302 +           including the 64474, 64475, 64574 and 64575.
  5.2303 +
  5.2304 +  R4300    MIPS Technologies R4300-series processors.
  5.2305 +
  5.2306 +  R4x00    MIPS Technologies R4000-series processors other than 4300,
  5.2307 +           including the 4640, 4650, and 4700.
  5.2308 +
  5.2309 +  R5000    MIPS Technologies R5000-series processors other than the
  5.2310 +           Nevada.
  5.2311 +
  5.2312 +  R52xx    MIPS Technologies R52xx-series ("Nevada") processors.
  5.2313 +
  5.2314 +  R10000   MIPS Technologies R10000-series processors.
  5.2315 +
  5.2316 +R6000
  5.2317 +CONFIG_CPU_R6000
  5.2318 +  MIPS Technologies R6000-series processors, including the 64474,
  5.2319 +  64475, 64574 and 64575.
  5.2320 +
  5.2321 +R4300
  5.2322 +CONFIG_CPU_R4300
  5.2323 +  MIPS Technologies R4300-series processors.
  5.2324 +
  5.2325 +R4x00
  5.2326 +CONFIG_CPU_R4X00
  5.2327 +  MIPS Technologies R4000-series processors other than 4300, including
  5.2328 +  the 4640, 4650, and 4700.
  5.2329 +
  5.2330 +R5000
  5.2331 +CONFIG_CPU_R5000
  5.2332 +  MIPS Technologies R5000-series processors other than the Nevada.
  5.2333 +
  5.2334 +R52x0
  5.2335 +CONFIG_CPU_NEVADA
  5.2336 +  MIPS Technologies R52x0-series ("Nevada") processors.
  5.2337 +
  5.2338 +R8000
  5.2339 +CONFIG_CPU_R8000
  5.2340 +  MIPS Technologies R8000-series processors.
  5.2341 +
  5.2342 +R10000
  5.2343 +CONFIG_CPU_R10000
  5.2344 +  MIPS Technologies R10000-series processors.
  5.2345 +
  5.2346 +Discontiguous Memory Support
  5.2347 +CONFIG_DISCONTIGMEM
  5.2348 +  Say Y to support efficient handling of discontiguous physical memory,
  5.2349 +  for architectures which are either NUMA (Non-Uniform Memory Access)
  5.2350 +  or have huge holes in the physical address space for other reasons.
  5.2351 +  See <file:Documentation/vm/numa> for more.
  5.2352 +
  5.2353 +Mapped kernel support
  5.2354 +CONFIG_MAPPED_KERNEL
  5.2355 +  Change the way a Linux kernel is loaded unto memory on a MIPS64
  5.2356 +  machine.  This is required in order to support text replication and
  5.2357 +  NUMA.  If you need to understand it, read the source code.
  5.2358 +
  5.2359 +Kernel text replication support
  5.2360 +CONFIG_REPLICATE_KTEXT
  5.2361 +  Say Y here to enable replicating the kernel text across multiple
  5.2362 +  nodes in a NUMA cluster.  This trades memory for speed.
  5.2363 +
  5.2364 +Exception handler replication support
  5.2365 +CONFIG_REPLICATE_EXHANDLERS
  5.2366 +  Say Y here to enable replicating the kernel exception handlers
  5.2367 +  across multiple nodes in a NUMA cluster. This trades memory for
  5.2368 +  speed.
  5.2369 +
  5.2370 +NUMA support?
  5.2371 +CONFIG_NUMA
  5.2372 +  Say Y to compile the kernel to support NUMA (Non-Uniform Memory
  5.2373 +  Access).  This option is for configuring high-end multiprocessor
  5.2374 +  server machines.  If in doubt, say N.
  5.2375 +
  5.2376 +R41xx
  5.2377 +CONFIG_CPU_VR41XX
  5.2378 +  The options selects support for the NEC VR41xx series of processors.
  5.2379 +  Only choose this option if you have one of these processors as a
  5.2380 +  kernel built with this option will not run on any other type of
  5.2381 +  processor or vice versa.
  5.2382 +
  5.2383 +CPU feature configuration
  5.2384 +CONFIG_CPU_ADVANCED
  5.2385 +  Saying yes here allows you to select support for various features
  5.2386 +  your CPU may or may not have.  Most people should say N here.
  5.2387 +
  5.2388 +ll and sc instructions available
  5.2389 +CONFIG_CPU_HAS_LLSC
  5.2390 +  MIPS R4000 series and later provide the Load Linked (ll)
  5.2391 +  and Store Conditional (sc) instructions. More information is
  5.2392 +  available at <http://www.go-ecs.com/mips/miptek1.htm>.
  5.2393 +
  5.2394 +  Say Y here if your CPU has the ll and sc instructions.  Say Y here
  5.2395 +  for better performance, N if you don't know.  You must say Y here
  5.2396 +  for multiprocessor machines.
  5.2397 +
  5.2398 +lld and scd instructions available
  5.2399 +CONFIG_CPU_HAS_LLDSCD
  5.2400 +  Say Y here if your CPU has the lld and scd instructions, the 64-bit
  5.2401 +  equivalents of ll and sc.  Say Y here for better performance, N if
  5.2402 +  you don't know.  You must say Y here for multiprocessor machines.
  5.2403 +
  5.2404 +Writeback Buffer available
  5.2405 +CONFIG_CPU_HAS_WB
  5.2406 +  Say N here for slightly better performance.  You must say Y here for
  5.2407 +  machines which require flushing of write buffers in software.  Saying
  5.2408 +  Y is the safe option; N may result in kernel malfunction and crashes.
  5.2409 +
  5.2410 +Support for large 64-bit configurations
  5.2411 +CONFIG_MIPS_INSANE_LARGE
  5.2412 +  MIPS R10000 does support a 44 bit / 16TB address space as opposed to
  5.2413 +  previous 64-bit processors which only supported 40 bit / 1TB. If you
  5.2414 +  need processes of more than 1TB virtual address space, say Y here.
  5.2415 +  This will result in additional memory usage, so it is not
  5.2416 +  recommended for normal users.
  5.2417 +
  5.2418 +Generate little endian code
  5.2419 +CONFIG_CPU_LITTLE_ENDIAN
  5.2420 +  Some MIPS machines can be configured for either little or big endian
  5.2421 +  byte order. These modes require different kernels. Say Y if your
  5.2422 +  machine is little endian, N if it's a big endian machine.
  5.2423 +
  5.2424 +Use power LED as a heartbeat
  5.2425 +CONFIG_HEARTBEAT
  5.2426 +  Use the power-on LED on your machine as a load meter.  The exact
  5.2427 +  behaviour is platform-dependent, but normally the flash frequency is
  5.2428 +  a hyperbolic function of the 5-minute load average.
  5.2429 +
  5.2430 +Networking support
  5.2431 +CONFIG_NET
  5.2432 +  Unless you really know what you are doing, you should say Y here.
  5.2433 +  The reason is that some programs need kernel networking support even
  5.2434 +  when running on a stand-alone machine that isn't connected to any
  5.2435 +  other computer. If you are upgrading from an older kernel, you
  5.2436 +  should consider updating your networking tools too because changes
  5.2437 +  in the kernel and the tools often go hand in hand. The tools are
  5.2438 +  contained in the package net-tools, the location and version number
  5.2439 +  of which are given in <file:Documentation/Changes>.
  5.2440 +
  5.2441 +  For a general introduction to Linux networking, it is highly
  5.2442 +  recommended to read the NET-HOWTO, available from
  5.2443 +  <http://www.tldp.org/docs.html#howto>.
  5.2444 +
  5.2445 +Socket filtering
  5.2446 +CONFIG_FILTER
  5.2447 +  The Linux Socket Filter is derived from the Berkeley Packet Filter.
  5.2448 +  If you say Y here, user-space programs can attach a filter to any
  5.2449 +  socket and thereby tell the kernel that it should allow or disallow
  5.2450 +  certain types of data to get through the socket.  Linux Socket
  5.2451 +  Filtering works on all socket types except TCP for now.  See the
  5.2452 +  text file <file:Documentation/networking/filter.txt> for more
  5.2453 +  information.
  5.2454 +
  5.2455 +  You need to say Y here if you want to use PPP packet filtering
  5.2456 +  (see the CONFIG_PPP_FILTER option below).
  5.2457 +
  5.2458 +  If unsure, say N.
  5.2459 +
  5.2460 +Network packet filtering (replaces ipchains)
  5.2461 +CONFIG_NETFILTER
  5.2462 +  Netfilter is a framework for filtering and mangling network packets
  5.2463 +  that pass through your Linux box.
  5.2464 +
  5.2465 +  The most common use of packet filtering is to run your Linux box as
  5.2466 +  a firewall protecting a local network from the Internet. The type of
  5.2467 +  firewall provided by this kernel support is called a "packet
  5.2468 +  filter", which means that it can reject individual network packets
  5.2469 +  based on type, source, destination etc. The other kind of firewall,
  5.2470 +  a "proxy-based" one, is more secure but more intrusive and more
  5.2471 +  bothersome to set up; it inspects the network traffic much more
  5.2472 +  closely, modifies it and has knowledge about the higher level
  5.2473 +  protocols, which a packet filter lacks. Moreover, proxy-based
  5.2474 +  firewalls often require changes to the programs running on the local
  5.2475 +  clients. Proxy-based firewalls don't need support by the kernel, but
  5.2476 +  they are often combined with a packet filter, which only works if
  5.2477 +  you say Y here.
  5.2478 +
  5.2479 +  You should also say Y here if you intend to use your Linux box as
  5.2480 +  the gateway to the Internet for a local network of machines without
  5.2481 +  globally valid IP addresses. This is called "masquerading": if one
  5.2482 +  of the computers on your local network wants to send something to
  5.2483 +  the outside, your box can "masquerade" as that computer, i.e. it
  5.2484 +  forwards the traffic to the intended outside destination, but
  5.2485 +  modifies the packets to make it look like they came from the
  5.2486 +  firewall box itself. It works both ways: if the outside host
  5.2487 +  replies, the Linux box will silently forward the traffic to the
  5.2488 +  correct local computer. This way, the computers on your local net
  5.2489 +  are completely invisible to the outside world, even though they can
  5.2490 +  reach the outside and can receive replies. It is even possible to
  5.2491 +  run globally visible servers from within a masqueraded local network
  5.2492 +  using a mechanism called portforwarding. Masquerading is also often
  5.2493 +  called NAT (Network Address Translation).
  5.2494 +
  5.2495 +  Another use of Netfilter is in transparent proxying: if a machine on
  5.2496 +  the local network tries to connect to an outside host, your Linux
  5.2497 +  box can transparently forward the traffic to a local server,
  5.2498 +  typically a caching proxy server.
  5.2499 +
  5.2500 +  Various modules exist for netfilter which replace the previous
  5.2501 +  masquerading (ipmasqadm), packet filtering (ipchains), transparent
  5.2502 +  proxying, and portforwarding mechanisms. Please see
  5.2503 +  <file:Documentation/Changes> under "iptables" for the location of
  5.2504 +  these packages.
  5.2505 +
  5.2506 +  Make sure to say N to "Fast switching" below if you intend to say Y
  5.2507 +  here, as Fast switching currently bypasses netfilter.
  5.2508 +
  5.2509 +  Chances are that you should say Y here if you compile a kernel which
  5.2510 +  will run as a router and N for regular hosts. If unsure, say N.
  5.2511 +
  5.2512 +Network packet filtering debugging
  5.2513 +CONFIG_NETFILTER_DEBUG
  5.2514 +  You can say Y here if you want to get additional messages useful in
  5.2515 +  debugging the netfilter code.
  5.2516 +
  5.2517 +Connection tracking (required for masq/NAT)
  5.2518 +CONFIG_IP_NF_CONNTRACK
  5.2519 +  Connection tracking keeps a record of what packets have passed
  5.2520 +  through your machine, in order to figure out how they are related
  5.2521 +  into connections.
  5.2522 +
  5.2523 +  This is required to do Masquerading or other kinds of Network
  5.2524 +  Address Translation (except for Fast NAT).  It can also be used to
  5.2525 +  enhance packet filtering (see `Connection state match support'
  5.2526 +  below).
  5.2527 +
  5.2528 +  If you want to compile it as a module, say M here and read
  5.2529 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2530 +
  5.2531 +Amanda protocol support
  5.2532 +CONFIG_IP_NF_AMANDA
  5.2533 +  If you are running the Amanda backup package (http://www.amanda.org/)
  5.2534 +  on this machine or machines that will be MASQUERADED through this
  5.2535 +  machine, then you may want to enable this feature.  This allows the
  5.2536 +  connection tracking and natting code to allow the sub-channels that
  5.2537 +  Amanda requires for communication of the backup data, messages and
  5.2538 +  index.
  5.2539 +
  5.2540 +  If you want to compile it as a module, say M here and read
  5.2541 +  Documentation/modules.txt.  If unsure, say `N'.
  5.2542 +
  5.2543 +
  5.2544 +IRC Send/Chat protocol support
  5.2545 +CONFIG_IP_NF_IRC
  5.2546 +  There is a commonly-used extension to IRC called
  5.2547 +  Direct Client-to-Client Protocol (DCC).  This enables users to send
  5.2548 +  files to each other, and also chat to each other without the need
  5.2549 +  of a server.  DCC Sending is used anywhere you send files over IRC,
  5.2550 +  and DCC Chat is most commonly used by Eggdrop bots.  If you are
  5.2551 +  using NAT, this extension will enable you to send files and initiate
  5.2552 +  chats.  Note that you do NOT need this extension to get files or
  5.2553 +  have others initiate chats, or everything else in IRC.
  5.2554 +
  5.2555 +  If you want to compile it as a module, say 'M' here and read
  5.2556 +  Documentation/modules.txt.  If unsure, say 'N'.
  5.2557 +
  5.2558 +TFTP protocol support
  5.2559 +CONFIG_IP_NF_TFTP
  5.2560 +  TFTP connection tracking helper, this is required depending
  5.2561 +  on how restrictive your ruleset is.
  5.2562 +  If you are using a tftp client behind -j SNAT or -j MASQUERADING
  5.2563 +  you will need this.
  5.2564 +
  5.2565 +  If you want to compile it as a module, say M here and read
  5.2566 +  Documentation/modules.txt.  If unsure, say `Y'.
  5.2567 +
  5.2568 +FTP protocol support
  5.2569 +CONFIG_IP_NF_FTP
  5.2570 +  Tracking FTP connections is problematic: special helpers are
  5.2571 +  required for tracking them, and doing masquerading and other forms
  5.2572 +  of Network Address Translation on them.
  5.2573 +
  5.2574 +  If you want to compile it as a module, say M here and read
  5.2575 +  <file:Documentation/modules.txt>.  If unsure, say `Y'.
  5.2576 +
  5.2577 +User space queueing via NETLINK
  5.2578 +CONFIG_IP_NF_QUEUE
  5.2579 +  Netfilter has the ability to queue packets to user space: the
  5.2580 +  netlink device can be used to access them using this driver.
  5.2581 +
  5.2582 +  If you want to compile it as a module, say M here and read
  5.2583 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2584 +
  5.2585 +IP tables support (required for filtering/masq/NAT)
  5.2586 +CONFIG_IP_NF_IPTABLES
  5.2587 +  iptables is a general, extensible packet identification framework.
  5.2588 +  The packet filtering and full NAT (masquerading, port forwarding,
  5.2589 +  etc) subsystems now use this: say `Y' or `M' here if you want to use
  5.2590 +  either of those.
  5.2591 +
  5.2592 +  If you want to compile it as a module, say M here and read
  5.2593 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2594 +
  5.2595 +limit match support
  5.2596 +CONFIG_IP_NF_MATCH_LIMIT
  5.2597 +  limit matching allows you to control the rate at which a rule can be
  5.2598 +  matched: mainly useful in combination with the LOG target ("LOG
  5.2599 +  target support", below) and to avoid some Denial of Service attacks.
  5.2600 +
  5.2601 +  If you want to compile it as a module, say M here and read
  5.2602 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2603 +
  5.2604 +skb->pkt_type packet match support
  5.2605 +CONFIG_IP_NF_MATCH_PKTTYPE
  5.2606 +  This patch allows you to match packet in accrodance
  5.2607 +  to its "class", eg. BROADCAST, MULTICAST, ...
  5.2608 +  
  5.2609 +  Typical usage:
  5.2610 +  iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
  5.2611 +  
  5.2612 +  If you want to compile it as a module, say M here and read
  5.2613 +  Documentation/modules.txt.  If unsure, say `N'.
  5.2614 +
  5.2615 +MAC address match support
  5.2616 +CONFIG_IP_NF_MATCH_MAC
  5.2617 +  MAC matching allows you to match packets based on the source
  5.2618 +  Ethernet address of the packet.
  5.2619 +
  5.2620 +  If you want to compile it as a module, say M here and read
  5.2621 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2622 +
  5.2623 +Netfilter MARK match support
  5.2624 +CONFIG_IP_NF_MATCH_MARK
  5.2625 +  Netfilter mark matching allows you to match packets based on the
  5.2626 +  `nfmark' value in the packet.  This can be set by the MARK target
  5.2627 +  (see below).
  5.2628 +
  5.2629 +  If you want to compile it as a module, say M here and read
  5.2630 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2631 +
  5.2632 +Multiple port match support
  5.2633 +CONFIG_IP_NF_MATCH_MULTIPORT
  5.2634 +  Multiport matching allows you to match TCP or UDP packets based on
  5.2635 +  a series of source or destination ports: normally a rule can only
  5.2636 +  match a single range of ports.
  5.2637 +
  5.2638 +  If you want to compile it as a module, say M here and read
  5.2639 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2640 +
  5.2641 +TTL match support
  5.2642 +CONFIG_IP_NF_MATCH_TTL
  5.2643 +  This adds CONFIG_IP_NF_MATCH_TTL option, which enabled the user
  5.2644 +  to match packets by their TTL value.
  5.2645 +
  5.2646 +  If you want to compile it as a module, say M here and read
  5.2647 +  Documentation/modules.txt.  If unsure, say `N'.
  5.2648 +
  5.2649 +LENGTH match support
  5.2650 +CONFIG_IP_NF_MATCH_LENGTH
  5.2651 +  This option allows you to match the length of a packet against a
  5.2652 +  specific value or range of values.
  5.2653 +
  5.2654 +  If you want to compile it as a module, say M here and read
  5.2655 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2656 +
  5.2657 +AH/ESP match support
  5.2658 +CONFIG_IP_NF_MATCH_AH_ESP
  5.2659 +  These two match extensions (`ah' and `esp') allow you to match a
  5.2660 +  range of SPIs inside AH or ESP headers of IPSec packets.
  5.2661 +
  5.2662 +  If you want to compile it as a module, say M here and read
  5.2663 +  Documentation/modules.txt.  If unsure, say `N'.
  5.2664 +
  5.2665 +DSCP match support
  5.2666 +CONFIG_IP_NF_MATCH_DSCP
  5.2667 +  This option adds a `DSCP' match, which allows you to match against
  5.2668 +  the IPv4 header DSCP field (DSCP codepoint).
  5.2669 +
  5.2670 +  The DSCP codepoint can have any value between 0x0 and 0x4f.
  5.2671 +
  5.2672 +  If you want to compile it as a module, say M here and read
  5.2673 +  Documentation/modules.txt.  If unsure, say `N'.
  5.2674 +
  5.2675 + 
  5.2676 +
  5.2677 +ECN match support
  5.2678 +CONFIG_IP_NF_MATCH_ECN
  5.2679 +  This option adds a `ECN' match, which allows you to match against
  5.2680 +  the IPv4 and TCP header ECN fields.
  5.2681 +
  5.2682 +  If you want to compile it as a module, say M here and read
  5.2683 +  Documentation/modules.txt.  If unsure, say `N'.
  5.2684 +
  5.2685 + 
  5.2686 +
  5.2687 +TOS match support
  5.2688 +CONFIG_IP_NF_MATCH_TOS
  5.2689 +  TOS matching allows you to match packets based on the Type Of
  5.2690 +  Service fields of the IP packet.
  5.2691 +
  5.2692 +  If you want to compile it as a module, say M here and read
  5.2693 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2694 +
  5.2695 +conntrack match support
  5.2696 +CONFIG_IP_NF_MATCH_CONNTRACK
  5.2697 +  This is a general conntrack match module, a superset of the state match.
  5.2698 +
  5.2699 +  It allows matching on additional conntrack information, which is
  5.2700 +  useful in complex configurations, such as NAT gateways with multiple
  5.2701 +  internet links or tunnels.
  5.2702 +
  5.2703 +  If you want to compile it as a module, say M here and read
  5.2704 +  Documentation/modules.txt.  If unsure, say `N'.
  5.2705 +
  5.2706 +
  5.2707 +Connection state match support
  5.2708 +CONFIG_IP_NF_MATCH_STATE
  5.2709 +  Connection state matching allows you to match packets based on their
  5.2710 +  relationship to a tracked connection (ie. previous packets).  This
  5.2711 +  is a powerful tool for packet classification.
  5.2712 +
  5.2713 +  If you want to compile it as a module, say M here and read
  5.2714 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2715 +
  5.2716 +Unclean match support
  5.2717 +CONFIG_IP_NF_MATCH_UNCLEAN
  5.2718 +  Unclean packet matching matches any strange or invalid packets, by
  5.2719 +  looking at a series of fields in the IP, TCP, UDP and ICMP headers.
  5.2720 +
  5.2721 +  If you want to compile it as a module, say M here and read
  5.2722 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2723 +
  5.2724 +Owner match support
  5.2725 +CONFIG_IP_NF_MATCH_OWNER
  5.2726 +  Packet owner matching allows you to match locally-generated packets
  5.2727 +  based on who created them: the user, group, process or session.
  5.2728 +
  5.2729 +  If you want to compile it as a module, say M here and read
  5.2730 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2731 +
  5.2732 +Packet filtering
  5.2733 +CONFIG_IP_NF_FILTER
  5.2734 +  Packet filtering defines a table `filter', which has a series of
  5.2735 +  rules for simple packet filtering at local input, forwarding and
  5.2736 +  local output.  See the man page for iptables(8).
  5.2737 +
  5.2738 +  If you want to compile it as a module, say M here and read
  5.2739 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2740 +
  5.2741 +REJECT target support
  5.2742 +CONFIG_IP_NF_TARGET_REJECT
  5.2743 +  The REJECT target allows a filtering rule to specify that an ICMP
  5.2744 +  error should be issued in response to an incoming packet, rather
  5.2745 +  than silently being dropped.
  5.2746 +
  5.2747 +  If you want to compile it as a module, say M here and read
  5.2748 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2749 +
  5.2750 +MIRROR target support
  5.2751 +CONFIG_IP_NF_TARGET_MIRROR
  5.2752 +  The MIRROR target allows a filtering rule to specify that an
  5.2753 +  incoming packet should be bounced back to the sender.
  5.2754 +
  5.2755 +  If you want to compile it as a module, say M here and read
  5.2756 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2757 +
  5.2758 +Local NAT support
  5.2759 +CONFIG_IP_NF_NAT_LOCAL
  5.2760 +  This option enables support for NAT of locally originated connections. 
  5.2761 +  Enable this if you need to use destination NAT on connections
  5.2762 +  originating from local processes on the nat box itself.
  5.2763 +
  5.2764 +  Please note that you will need a recent version (>= 1.2.6a)
  5.2765 +  of the iptables userspace program in order to use this feature.
  5.2766 +  See <http://www.iptables.org/> for download instructions.
  5.2767 +
  5.2768 +  If unsure, say 'N'.
  5.2769 +
  5.2770 +
  5.2771 +Full NAT (Network Address Translation)
  5.2772 +CONFIG_IP_NF_NAT
  5.2773 +  The Full NAT option allows masquerading, port forwarding and other
  5.2774 +  forms of full Network Address Port Translation.  It is controlled by
  5.2775 +  the `nat' table in iptables: see the man page for iptables(8).
  5.2776 +
  5.2777 +  If you want to compile it as a module, say M here and read
  5.2778 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2779 +
  5.2780 +MASQUERADE target support
  5.2781 +CONFIG_IP_NF_TARGET_MASQUERADE
  5.2782 +  Masquerading is a special case of NAT: all outgoing connections are
  5.2783 +  changed to seem to come from a particular interface's address, and
  5.2784 +  if the interface goes down, those connections are lost.  This is
  5.2785 +  only useful for dialup accounts with dynamic IP address (ie. your IP
  5.2786 +  address will be different on next dialup).
  5.2787 +
  5.2788 +  If you want to compile it as a module, say M here and read
  5.2789 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2790 +
  5.2791 +Basic SNMP-ALG support
  5.2792 +CONFIG_IP_NF_NAT_SNMP_BASIC
  5.2793 +
  5.2794 +  This module implements an Application Layer Gateway (ALG) for
  5.2795 +  SNMP payloads.  In conjunction with NAT, it allows a network
  5.2796 +  management system to access multiple private networks with
  5.2797 +  conflicting addresses.  It works by modifying IP addresses
  5.2798 +  inside SNMP payloads to match IP-layer NAT mapping.
  5.2799 +
  5.2800 +  This is the "basic" form of SNMP-ALG, as described in RFC 2962
  5.2801 +
  5.2802 +  If you want to compile it as a module, say M here and read
  5.2803 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2804 +
  5.2805 +REDIRECT target support
  5.2806 +CONFIG_IP_NF_TARGET_REDIRECT
  5.2807 +  REDIRECT is a special case of NAT: all incoming connections are
  5.2808 +  mapped onto the incoming interface's address, causing the packets to
  5.2809 +  come to the local machine instead of passing through.  This is
  5.2810 +  useful for transparent proxies.
  5.2811 +
  5.2812 +  If you want to compile it as a module, say M here and read
  5.2813 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2814 +
  5.2815 +Packet mangling
  5.2816 +CONFIG_IP_NF_MANGLE
  5.2817 +  This option adds a `mangle' table to iptables: see the man page for
  5.2818 +  iptables(8).  This table is used for various packet alterations
  5.2819 +  which can effect how the packet is routed.
  5.2820 +
  5.2821 +  If you want to compile it as a module, say M here and read
  5.2822 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2823 +
  5.2824 +DSCP target support
  5.2825 +CONFIG_IP_NF_TARGET_DSCP
  5.2826 +  This option adds a `DSCP' target, which allows you to create rules in
  5.2827 +  the iptables mangle table. The selected packet has the DSCP field set
  5.2828 +  to the hex value provided on the command line; unlike the TOS target
  5.2829 +  which will only set the legal values within ip.h.
  5.2830 +
  5.2831 +  The DSCP field can be set to any value between 0x0 and 0x4f. It does
  5.2832 +  take into account that bits 6 and 7 are used by ECN.
  5.2833 +
  5.2834 +  If you want to compile it as a module, say M here and read
  5.2835 +  Documentation/modules.txt.  If unsure, say `N'.
  5.2836 +
  5.2837 + 
  5.2838 +
  5.2839 +ECN target support
  5.2840 +CONFIG_IP_NF_TARGET_ECN
  5.2841 +  This option adds a `ECN' target, which can be used in the iptables mangle
  5.2842 +  table.  
  5.2843 +
  5.2844 +  You can use this target to remove the ECN bits from the IPv4 header of
  5.2845 +  an IP packet.  This is particularly useful, if you need to work around
  5.2846 +  existing ECN blackholes on the internet, but don't want to disable
  5.2847 +  ECN support in general.
  5.2848 +
  5.2849 +  If you want to compile it as a module, say M here and read
  5.2850 +  Documentation/modules.txt.  If unsure, say `N'.
  5.2851 +
  5.2852 + 
  5.2853 +
  5.2854 +TOS target support
  5.2855 +CONFIG_IP_NF_TARGET_TOS
  5.2856 +  This option adds a `TOS' target, which allows you to create rules in
  5.2857 +  the `mangle' table which alter the Type Of Service field of an IP
  5.2858 +  packet prior to routing.
  5.2859 +
  5.2860 +  If you want to compile it as a module, say M here and read
  5.2861 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2862 +
  5.2863 +MARK target support
  5.2864 +CONFIG_IP_NF_TARGET_MARK
  5.2865 +  This option adds a `MARK' target, which allows you to create rules
  5.2866 +  in the `mangle' table which alter the netfilter mark (nfmark) field
  5.2867 +  associated with the packet prior to routing. This can change
  5.2868 +  the routing method (see `Use netfilter MARK value as routing
  5.2869 +  key') and can also be used by other subsystems to change their
  5.2870 +  behaviour.
  5.2871 +
  5.2872 +  If you want to compile it as a module, say M here and read
  5.2873 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2874 +
  5.2875 +TCPMSS target support
  5.2876 +CONFIG_IP_NF_TARGET_TCPMSS
  5.2877 +  This option adds a `TCPMSS' target, which allows you to alter the
  5.2878 +  MSS value of TCP SYN packets, to control the maximum size for that
  5.2879 +  connection (usually limiting it to your outgoing interface's MTU
  5.2880 +  minus 40).
  5.2881 +
  5.2882 +  This is used to overcome criminally braindead ISPs or servers which
  5.2883 +  block ICMP Fragmentation Needed packets.  The symptoms of this
  5.2884 +  problem are that everything works fine from your Linux
  5.2885 +  firewall/router, but machines behind it can never exchange large
  5.2886 +  packets:
  5.2887 +	1) Web browsers connect, then hang with no data received.
  5.2888 +	2) Small mail works fine, but large emails hang.
  5.2889 +	3) ssh works fine, but scp hangs after initial handshaking.
  5.2890 +
  5.2891 +  Workaround: activate this option and add a rule to your firewall
  5.2892 +  configuration like:
  5.2893 +
  5.2894 +        iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
  5.2895 +		 -j TCPMSS --clamp-mss-to-pmtu
  5.2896 +
  5.2897 +  If you want to compile it as a module, say M here and read
  5.2898 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2899 +
  5.2900 +Helper match support
  5.2901 +CONFIG_IP_NF_MATCH_HELPER
  5.2902 +  Helper matching allows you to match packets in dynamic connections
  5.2903 +  tracked by a conntrack-helper, ie. ip_conntrack_ftp
  5.2904 +
  5.2905 +  If you want to compile it as a module, say M here and read
  5.2906 +  Documentation/modules.txt.  If unsure, say `Y'.
  5.2907 +
  5.2908 +TCPMSS match support
  5.2909 +CONFIG_IP_NF_MATCH_TCPMSS
  5.2910 +  This option adds a `tcpmss' match, which allows you to examine the
  5.2911 +  MSS value of TCP SYN packets, which control the maximum packet size
  5.2912 +  for that connection.
  5.2913 +
  5.2914 +  If you want to compile it as a module, say M here and read
  5.2915 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2916 +
  5.2917 +ULOG target support
  5.2918 +CONFIG_IP_NF_TARGET_ULOG
  5.2919 +  This option adds a `ULOG' target, which allows you to create rules in
  5.2920 +  any iptables table. The packet is passed to a userspace logging
  5.2921 +  daemon using netlink multicast sockets; unlike the LOG target
  5.2922 +  which can only be viewed through syslog.
  5.2923 +
  5.2924 +  The appropriate userspace logging daemon (ulogd) may be obtained from
  5.2925 +  <http://www.gnumonks.org/projects/ulogd>
  5.2926 +
  5.2927 +  If you want to compile it as a module, say M here and read
  5.2928 +  Documentation/modules.txt.  If unsure, say `N'.
  5.2929 +
  5.2930 +LOG target support
  5.2931 +CONFIG_IP_NF_TARGET_LOG
  5.2932 +  This option adds a `LOG' target, which allows you to create rules in
  5.2933 +  any iptables table which records the packet header to the syslog.
  5.2934 +
  5.2935 +  If you want to compile it as a module, say M here and read
  5.2936 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2937 +
  5.2938 +ipchains (2.2-style) support
  5.2939 +CONFIG_IP_NF_COMPAT_IPCHAINS
  5.2940 +  This option places ipchains (with masquerading and redirection
  5.2941 +  support) back into the kernel, using the new netfilter
  5.2942 +  infrastructure.  It is not recommended for new installations (see
  5.2943 +  `Packet filtering').  With this enabled, you should be able to use
  5.2944 +  the ipchains tool exactly as in 2.2 kernels.
  5.2945 +
  5.2946 +  If you want to compile it as a module, say M here and read
  5.2947 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2948 +
  5.2949 +ipfwadm (2.0-style) support
  5.2950 +CONFIG_IP_NF_COMPAT_IPFWADM
  5.2951 +  This option places ipfwadm (with masquerading and redirection
  5.2952 +  support) back into the kernel, using the new netfilter
  5.2953 +  infrastructure.  It is not recommended for new installations (see
  5.2954 +  `Packet filtering').  With this enabled, you should be able to use
  5.2955 +  the ipfwadm tool exactly as in 2.0 kernels.
  5.2956 +
  5.2957 +  If you want to compile it as a module, say M here and read
  5.2958 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2959 +
  5.2960 +EUI64 address check (EXPERIMENTAL)
  5.2961 +CONFIG_IP6_NF_MATCH_EUI64
  5.2962 +  This module performs checking on the IPv6 source address
  5.2963 +  Compares the last 64 bits with the EUI64 (delivered
  5.2964 +  from the MAC address) address
  5.2965 +
  5.2966 +  If you want to compile it as a module, say M here and read
  5.2967 +  Documentation/modules.txt.  If unsure, say `N'.
  5.2968 +
  5.2969 +MAC address match support
  5.2970 +CONFIG_IP6_NF_MATCH_MAC
  5.2971 +  mac matching allows you to match packets based on the source
  5.2972 +  Ethernet address of the packet.
  5.2973 +
  5.2974 +  If you want to compile it as a module, say M here and read
  5.2975 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2976 +
  5.2977 +length match support
  5.2978 +CONFIG_IP6_NF_MATCH_LENGTH
  5.2979 +  This option allows you to match the length of a packet against a
  5.2980 +  specific value or range of values.
  5.2981 +
  5.2982 +  If you want to compile it as a module, say M here and read
  5.2983 +  Documentation/modules.txt.  If unsure, say `N'.
  5.2984 +
  5.2985 +Netfilter MARK match support
  5.2986 +CONFIG_IP6_NF_MATCH_MARK
  5.2987 +  Netfilter mark matching allows you to match packets based on the
  5.2988 +  `nfmark' value in the packet.  This can be set by the MARK target
  5.2989 +  (see below).
  5.2990 +
  5.2991 +  If you want to compile it as a module, say M here and read
  5.2992 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.2993 +
  5.2994 +Multiple port match support
  5.2995 +CONFIG_IP6_NF_MATCH_MULTIPORT
  5.2996 +  Multiport matching allows you to match TCP or UDP packets based on
  5.2997 +  a series of source or destination ports: normally a rule can only
  5.2998 +  match a single range of ports.
  5.2999 +
  5.3000 +  If you want to compile it as a module, say M here and read
  5.3001 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.3002 +
  5.3003 +IPV6 queue handler (EXPERIMENTAL)
  5.3004 +CONFIG_IP6_NF_QUEUE
  5.3005 +
  5.3006 +  This option adds a queue handler to the kernel for IPv6
  5.3007 +  packets which lets us to receive the filtered packets
  5.3008 +  with QUEUE target using libiptc as we can do with
  5.3009 +  the IPv4 now.
  5.3010 +
  5.3011 +  (C) Fernando Anton 2001
  5.3012 +  IPv64 Project - Work based in IPv64 draft by Arturo Azcorra.
  5.3013 +  Universidad Carlos III de Madrid
  5.3014 +  Universidad Politecnica de Alcala de Henares
  5.3015 +  email: fanton@it.uc3m.es
  5.3016 +
  5.3017 +  If you want to compile it as a module, say M here and read
  5.3018 +  Documentation/modules.txt. If unsure, say `N'.
  5.3019 +
  5.3020 +Owner match support
  5.3021 +CONFIG_IP6_NF_MATCH_OWNER
  5.3022 +  Packet owner matching allows you to match locally-generated packets
  5.3023 +  based on who created them: the user, group, process or session.
  5.3024 +
  5.3025 +  If you want to compile it as a module, say M here and read
  5.3026 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.3027 +
  5.3028 +Packet filtering
  5.3029 +CONFIG_IP6_NF_FILTER
  5.3030 +  Packet filtering defines a table `filter', which has a series of
  5.3031 +  rules for simple packet filtering at local input, forwarding and
  5.3032 +  local output.  See the man page for iptables(8).
  5.3033 +
  5.3034 +  If you want to compile it as a module, say M here and read
  5.3035 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.3036 +
  5.3037 +Packet mangling
  5.3038 +CONFIG_IP6_NF_MANGLE
  5.3039 +  This option adds a `mangle' table to iptables: see the man page for
  5.3040 +  iptables(8).  This table is used for various packet alterations
  5.3041 +  which can effect how the packet is routed.
  5.3042 +
  5.3043 +  If you want to compile it as a module, say M here and read
  5.3044 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.3045 +
  5.3046 +MARK target support
  5.3047 +CONFIG_IP6_NF_TARGET_MARK
  5.3048 +  This option adds a `MARK' target, which allows you to create rules
  5.3049 +  in the `mangle' table which alter the netfilter mark (nfmark) field
  5.3050 +  associated with the packet packet prior to routing. This can change
  5.3051 +  the routing method (see `Use netfilter MARK value as routing
  5.3052 +  key') and can also be used by other subsystems to change their
  5.3053 +  behaviour.
  5.3054 +
  5.3055 +  If you want to compile it as a module, say M here and read
  5.3056 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.3057 +
  5.3058 +TCP Explicit Congestion Notification support
  5.3059 +CONFIG_INET_ECN
  5.3060 +  Explicit Congestion Notification (ECN) allows routers to notify
  5.3061 +  clients about network congestion, resulting in fewer dropped packets
  5.3062 +  and increased network performance.  This option adds ECN support to
  5.3063 +  the Linux kernel, as well as a sysctl (/proc/sys/net/ipv4/tcp_ecn)
  5.3064 +  which allows ECN support to be disabled at runtime.
  5.3065 +
  5.3066 +  Note that, on the Internet, there are many broken firewalls which
  5.3067 +  refuse connections from ECN-enabled machines, and it may be a while
  5.3068 +  before these firewalls are fixed.  Until then, to access a site
  5.3069 +  behind such a firewall (some of which are major sites, at the time
  5.3070 +  of this writing) you will have to disable this option, either by
  5.3071 +  saying N now or by using the sysctl.
  5.3072 +
  5.3073 +  If in doubt, say N.
  5.3074 +
  5.3075 +IPv6 tables support (required for filtering/masq/NAT)
  5.3076 +CONFIG_IP6_NF_IPTABLES
  5.3077 +  ip6tables is a general, extensible packet identification framework.
  5.3078 +  Currently only the packet filtering and packet mangling subsystem
  5.3079 +  for IPv6 use this, but connection tracking is going to follow.
  5.3080 +  Say 'Y' or 'M' here if you want to use either of those.
  5.3081 +
  5.3082 +  If you want to compile it as a module, say M here and read
  5.3083 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.3084 +
  5.3085 +IPv6 limit match support
  5.3086 +CONFIG_IP6_NF_MATCH_LIMIT
  5.3087 +  limit matching allows you to control the rate at which a rule can be
  5.3088 +  matched: mainly useful in combination with the LOG target ("LOG
  5.3089 +  target support", below) and to avoid some Denial of Service attacks.
  5.3090 +
  5.3091 +  If you want to compile it as a module, say M here and read
  5.3092 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.3093 +
  5.3094 +LOG target support
  5.3095 +CONFIG_IP6_NF_TARGET_LOG
  5.3096 +  This option adds a `LOG' target, which allows you to create rules in
  5.3097 +  any iptables table which records the packet header to the syslog.
  5.3098 +
  5.3099 +  If you want to compile it as a module, say M here and read
  5.3100 +  <file:Documentation/modules.txt>.  If unsure, say `N'.
  5.3101 +
  5.3102 +SYN flood protection
  5.3103 +CONFIG_SYN_COOKIES
  5.3104 +  Normal TCP/IP networking is open to an attack known as "SYN
  5.3105 +  flooding". This denial-of-service attack prevents legitimate remote
  5.3106 +  users from being able to connect to your computer during an ongoing
  5.3107 +  attack and requires very little work from the attacker, who can
  5.3108 +  operate from anywhere on the Internet.
  5.3109 +
  5.3110 +  SYN cookies provide protection against this type of attack. If you
  5.3111 +  say Y here, the TCP/IP stack will use a cryptographic challenge
  5.3112 +  protocol known as "SYN cookies" to enable legitimate users to
  5.3113 +  continue to connect, even when your machine is under attack. There
  5.3114 +  is no need for the legitimate users to change their TCP/IP software;
  5.3115 +  SYN cookies work transparently to them. For technical information
  5.3116 +  about SYN cookies, check out <http://cr.yp.to/syncookies.html>.
  5.3117 +
  5.3118 +  If you are SYN flooded, the source address reported by the kernel is
  5.3119 +  likely to have been forged by the attacker; it is only reported as
  5.3120 +  an aid in tracing the packets to their actual source and should not
  5.3121 +  be taken as absolute truth.
  5.3122 +
  5.3123 +  SYN cookies may prevent correct error reporting on clients when the
  5.3124 +  server is really overloaded. If this happens frequently better turn
  5.3125 +  them off.
  5.3126 +
  5.3127 +  If you say Y here, note that SYN cookies aren't enabled by default;
  5.3128 +  you can enable them by saying Y to "/proc file system support" and
  5.3129 +  "Sysctl support" below and executing the command
  5.3130 +
  5.3131 +    echo 1 >/proc/sys/net/ipv4/tcp_syncookies
  5.3132 +
  5.3133 +  at boot time after the /proc file system has been mounted.
  5.3134 +
  5.3135 +  If unsure, say N.
  5.3136 +
  5.3137 +# Choice: alphatype
  5.3138 +Alpha system type
  5.3139 +CONFIG_ALPHA_GENERIC
  5.3140 +  This is the system type of your hardware.  A "generic" kernel will
  5.3141 +  run on any supported Alpha system. However, if you configure a
  5.3142 +  kernel for your specific system, it will be faster and smaller.
  5.3143 +
  5.3144 +  To find out what type of Alpha system you have, you may want to
  5.3145 +  check out the Linux/Alpha FAQ, accessible on the WWW from
  5.3146 +  <http://www.alphalinux.org/>. In summary:
  5.3147 +
  5.3148 +  Alcor/Alpha-XLT     AS 600
  5.3149 +  Alpha-XL            XL-233, XL-266
  5.3150 +  AlphaBook1          Alpha laptop
  5.3151 +  Avanti              AS 200, AS 205, AS 250, AS 255, AS 300, AS 400
  5.3152 +  Cabriolet           AlphaPC64, AlphaPCI64
  5.3153 +  DP264               DP264
  5.3154 +  EB164               EB164 21164 evaluation board
  5.3155 +  EB64+               EB64+ 21064 evaluation board
  5.3156 +  EB66                EB66 21066 evaluation board
  5.3157 +  EB66+               EB66+ 21066 evaluation board
  5.3158 +  Jensen              DECpc 150, DEC 2000 model 300,
  5.3159 +                      DEC 2000 model 500
  5.3160 +  LX164               AlphaPC164-LX
  5.3161 +  Miata               Personal Workstation 433a, 433au, 500a,
  5.3162 +                      500au, 600a, or 600au
  5.3163 +  Mikasa              AS 1000
  5.3164 +  Noname              AXPpci33, UDB (Multia)
  5.3165 +  Noritake            AS 1000A, AS 600A, AS 800
  5.3166 +  PC164               AlphaPC164
  5.3167 +  Rawhide             AS 1200, AS 4000, AS 4100
  5.3168 +  Ruffian             RPX164-2, AlphaPC164-UX, AlphaPC164-BX
  5.3169 +  SX164               AlphaPC164-SX
  5.3170 +  Sable               AS 2000, AS 2100
  5.3171 +  Shark		      DS 20L
  5.3172 +  Takara              Takara
  5.3173 +  Titan               Privateer
  5.3174 +  Wildfire            AlphaServer GS 40/80/160/320
  5.3175 +
  5.3176 +  If you don't know what to do, choose "generic".
  5.3177 +
  5.3178 +# Most of the information on these variants is from
  5.3179 +# <http://www.alphalinux.org/docs/alpha-howto.html>
  5.3180 +Alcor/Alpha-XLT
  5.3181 +CONFIG_ALPHA_ALCOR
  5.3182 +  For systems using the Digital ALCOR chipset: 5 chips (4, 64-bit data
  5.3183 +  slices (Data Switch, DSW) - 208-pin PQFP and 1 control (Control, I/O
  5.3184 +  Address, CIA) - a 383 pin plastic PGA).  It provides a DRAM
  5.3185 +  controller (256-bit memory bus) and a PCI interface.  It also does
  5.3186 +  all the work required to support an external Bcache and to maintain
  5.3187 +  memory coherence when a PCI device DMAs into (or out of) memory.
  5.3188 +
  5.3189 +Alpha-XL
  5.3190 +CONFIG_ALPHA_XL
  5.3191 +  XL-233 and XL-266-based Alpha systems.
  5.3192 +
  5.3193 +AlphaBook1
  5.3194 +CONFIG_ALPHA_BOOK1
  5.3195 +  Dec AlphaBook1/Burns Alpha-based laptops.
  5.3196 +
  5.3197 +Avanti
  5.3198 +CONFIG_ALPHA_AVANTI
  5.3199 +  Avanti AS 200, AS 205, AS 250, AS 255, AS 300, and AS 400-based
  5.3200 +  Alphas. Info at
  5.3201 +  <http://www.unix-ag.org/Linux-Alpha/Architectures/Avanti.html>.
  5.3202 +
  5.3203 +Cabriolet
  5.3204 +CONFIG_ALPHA_CABRIOLET
  5.3205 +  Cabriolet AlphaPC64, AlphaPCI64 systems.  Derived from EB64+ but now
  5.3206 +  baby-AT with Flash boot ROM, no on-board SCSI or Ethernet. 3 ISA
  5.3207 +  slots, 4 PCI slots (one pair are on a shared slot), uses plug-in
  5.3208 +  Bcache SIMMs.  Requires power supply with 3.3V output.
  5.3209 +
  5.3210 +DP264
  5.3211 +CONFIG_ALPHA_DP264
  5.3212 +  Various 21264 systems with the tsunami core logic chipset.
  5.3213 +  API Networks: 264DP, UP2000(+), CS20;
  5.3214 +  Compaq: DS10(E,L), XP900, XP1000, DS20(E), ES40.
  5.3215 +
  5.3216 +EB164
  5.3217 +CONFIG_ALPHA_EB164
  5.3218 +  EB164 21164 evaluation board from DEC.  Uses 21164 and ALCOR.  Has
  5.3219 +  ISA and PCI expansion (3 ISA slots, 2 64-bit PCI slots (one is
  5.3220 +  shared with an ISA slot) and 2 32-bit PCI slots.  Uses plus-in
  5.3221 +  Bcache SIMMs. I/O sub-system provides SuperI/O (2S, 1P, FD), KBD,
  5.3222 +  MOUSE (PS2 style), RTC/NVRAM.  Boot ROM is Flash.  PC-AT-sized
  5.3223 +  motherboard.  Requires power supply with 3.3V output.
  5.3224 +
  5.3225 +EB64+
  5.3226 +CONFIG_ALPHA_EB64P
  5.3227 +  Uses 21064 or 21064A and APECs.  Has ISA and PCI expansion (3 ISA,
  5.3228 +  2 PCI, one pair are on a shared slot). Supports 36-bit DRAM SIMs.
  5.3229 +  ISA bus generated by Intel SaturnI/O PCI-ISA bridge. On-board SCSI
  5.3230 +  (NCR 810 on PCI) Ethernet (Digital 21040), KBD, MOUSE (PS2 style),
  5.3231 +  SuperI/O (2S, 1P, FD), RTC/NVRAM. Boot ROM is EPROM.  PC-AT size.
  5.3232 +  Runs from standard PC power supply.
  5.3233 +
  5.3234 +EB66
  5.3235 +CONFIG_ALPHA_EB66
  5.3236 +  A Digital DS group board.  Uses 21066 or 21066A.  I/O sub-system is
  5.3237 +  identical to EB64+.  Baby PC-AT size.  Runs from standard PC power
  5.3238 +  supply.  The EB66 schematic was published as a marketing poster
  5.3239 +  advertising the 21066 as "the first microprocessor in the world with
  5.3240 +  embedded PCI".
  5.3241 +
  5.3242 +EB66+
  5.3243 +CONFIG_ALPHA_EB66P
  5.3244 +  Later variant of the EB66 board.
  5.3245 +
  5.3246 +Eiger
  5.3247 +CONFIG_ALPHA_EIGER
  5.3248 +  Apparently an obscure OEM single-board computer based on the
  5.3249 +  Typhoon/Tsunami chipset family. Information on it is scanty.
  5.3250 +
  5.3251 +Jensen
  5.3252 +CONFIG_ALPHA_JENSEN
  5.3253 +  DEC PC 150 AXP (aka Jensen): This is a very old Digital system - one
  5.3254 +  of the first-generation Alpha systems. A number of these systems
  5.3255 +  seem to be available on the second- hand market. The Jensen is a
  5.3256 +  floor-standing tower system which originally used a 150MHz 21064 It
  5.3257 +  used programmable logic to interface a 486 EISA I/O bridge to the
  5.3258 +  CPU.
  5.3259 +
  5.3260 +LX164
  5.3261 +CONFIG_ALPHA_LX164
  5.3262 +  A technical overview of this board is available at
  5.3263 +  <http://www.unix-ag.org/Linux-Alpha/Architectures/LX164.html>.
  5.3264 +
  5.3265 +Miata
  5.3266 +CONFIG_ALPHA_MIATA
  5.3267 +  The Digital PersonalWorkStation (PWS 433a, 433au, 500a, 500au, 600a,
  5.3268 +  or 600au).  There is an Installation HOWTO for this hardware at
  5.3269 +  <http://members.brabant.chello.nl/~s.vandereijk/miata.html>.
  5.3270 +
  5.3271 +Mikasa
  5.3272 +CONFIG_ALPHA_MIKASA
  5.3273 +  AlphaServer 1000-based Alpha systems.
  5.3274 +
  5.3275 +Nautilus
  5.3276 +CONFIG_ALPHA_NAUTILUS
  5.3277 +  Alpha systems based on the AMD 751 & ALI 1543C chipsets.
  5.3278 +
  5.3279 +Noname
  5.3280 +CONFIG_ALPHA_NONAME
  5.3281 +  The AXPpci33 (aka NoName), is based on the EB66 (includes the Multia
  5.3282 +  UDB).  This design was produced by Digital's Technical OEM (TOEM)
  5.3283 +  group. It uses the 21066 processor running at 166MHz or 233MHz. It
  5.3284 +  is a baby-AT size, and runs from a standard PC power supply. It has
  5.3285 +  5 ISA slots and 3 PCI slots (one pair are a shared slot). There are
  5.3286 +  2 versions, with either PS/2 or large DIN connectors for the
  5.3287 +  keyboard.
  5.3288 +
  5.3289 +Noritake
  5.3290 +CONFIG_ALPHA_NORITAKE
  5.3291 +  AlphaServer 1000A, AlphaServer 600A, and AlphaServer 800-based
  5.3292 +  systems.
  5.3293 +
  5.3294 +Rawhide
  5.3295 +CONFIG_ALPHA_RAWHIDE
  5.3296 +  AlphaServer 1200, AlphaServer 4000 and AlphaServer 4100 machines.
  5.3297 +  See HOWTO at
  5.3298 +  <http://www.alphalinux.org/docs/rawhide/4100_install.shtml>.
  5.3299 +
  5.3300 +Ruffian
  5.3301 +CONFIG_ALPHA_RUFFIAN
  5.3302 +  Samsung APC164UX.  There is a page on known problems and workarounds
  5.3303 +  at <http://www.alphalinux.org/faq/FAQ-11.html>.
  5.3304 +
  5.3305 +Sable
  5.3306 +CONFIG_ALPHA_SABLE
  5.3307 +  Digital AlphaServer 2000 and 2100-based systems.
  5.3308 +
  5.3309 +Takara
  5.3310 +CONFIG_ALPHA_TAKARA
  5.3311 +  Alpha 11164-based OEM single-board computer.
  5.3312 +
  5.3313 +Wildfire
  5.3314 +CONFIG_ALPHA_WILDFIRE
  5.3315 +  AlphaServer GS 40/80/160/320 SMP based on the EV67 core.
  5.3316 +
  5.3317 +EV5 CPU daughtercard (model 5/xxx)
  5.3318 +CONFIG_ALPHA_PRIMO
  5.3319 +  Say Y if you have an AS 1000 5/xxx or an AS 1000A 5/xxx.
  5.3320 +
  5.3321 +EV5 CPU(s) (model 5/xxx)
  5.3322 +CONFIG_ALPHA_GAMMA
  5.3323 +  Say Y if you have an AS 2000 5/xxx or an AS 2100 5/xxx.
  5.3324 +
  5.3325 +EV67 (or later) CPU (speed > 600MHz)?
  5.3326 +CONFIG_ALPHA_EV67
  5.3327 +  Is this a machine based on the EV67 core?  If in doubt, select N here
  5.3328 +  and the machine will be treated as an EV6.
  5.3329 +
  5.3330 +Use SRM as bootloader
  5.3331 +CONFIG_ALPHA_SRM
  5.3332 +  There are two different types of booting firmware on Alphas: SRM,
  5.3333 +  which is command line driven, and ARC, which uses menus and arrow
  5.3334 +  keys. Details about the Linux/Alpha booting process are contained in
  5.3335 +  the Linux/Alpha FAQ, accessible on the WWW from
  5.3336 +  <http://www.alphalinux.org/>.
  5.3337 +
  5.3338 +  The usual way to load Linux on an Alpha machine is to use MILO
  5.3339 +  (a bootloader that lets you pass command line parameters to the
  5.3340 +  kernel just like lilo does for the x86 architecture) which can be
  5.3341 +  loaded either from ARC or can be installed directly as a permanent
  5.3342 +  firmware replacement from floppy (which requires changing a certain
  5.3343 +  jumper on the motherboard). If you want to do either of these, say N
  5.3344 +  here. If MILO doesn't work on your system (true for Jensen
  5.3345 +  motherboards), you can bypass it altogether and boot Linux directly
  5.3346 +  from an SRM console; say Y here in order to do that. Note that you
  5.3347 +  won't be able to boot from an IDE disk using SRM.
  5.3348 +
  5.3349 +  If unsure, say N.
  5.3350 +
  5.3351 +Legacy kernel start address
  5.3352 +CONFIG_ALPHA_LEGACY_START_ADDRESS
  5.3353 +  The 2.4 kernel changed the kernel start address from 0x310000
  5.3354 +  to 0x810000 to make room for the Wildfire's larger SRM console.
  5.3355 +
  5.3356 +  If you're using aboot 0.7 or later, the bootloader will examine the
  5.3357 +  ELF headers to determine where to transfer control. Unfortunately,
  5.3358 +  most older bootloaders -- APB or MILO -- hardcoded the kernel start
  5.3359 +  address rather than examining the ELF headers, and the result is a
  5.3360 +  hard lockup.
  5.3361 +
  5.3362 +  Say Y if you have a broken bootloader.  Say N if you do not, or if
  5.3363 +  you wish to run on Wildfire.
  5.3364 +
  5.3365 +Large VMALLOC support
  5.3366 +CONFIG_ALPHA_LARGE_VMALLOC
  5.3367 +  Process creation and other aspects of virtual memory management can
  5.3368 +  be streamlined if we restrict the kernel to one PGD for all vmalloc
  5.3369 +  allocations.  This equates to about 8GB.
  5.3370 +
  5.3371 +  Under normal circumstances, this is so far and above what is needed
  5.3372 +  as to be laughable.  However, there are certain applications (such
  5.3373 +  as benchmark-grade in-kernel web serving) that can make use of as
  5.3374 +  much vmalloc space as is available.
  5.3375 +
  5.3376 +  Say N unless you know you need gobs and gobs of vmalloc space.
  5.3377 +
  5.3378 +Non-standard serial port support
  5.3379 +CONFIG_SERIAL_NONSTANDARD
  5.3380 +  Say Y here if you have any non-standard serial boards -- boards
  5.3381 +  which aren't supported using the standard "dumb" serial driver.
  5.3382 +  This includes intelligent serial boards such as Cyclades,
  5.3383 +  Digiboards, etc. These are usually used for systems that need many
  5.3384 +  serial ports because they serve many terminals or dial-in
  5.3385 +  connections.
  5.3386 +
  5.3387 +  Note that the answer to this question won't directly affect the
  5.3388 +  kernel: saying N will just cause the configurator to skip all
  5.3389 +  the questions about non-standard serial boards.
  5.3390 +
  5.3391 +  Most people can say N here.
  5.3392 +
  5.3393 +Extended dumb serial driver options
  5.3394 +CONFIG_SERIAL_EXTENDED
  5.3395 +  If you wish to use any non-standard features of the standard "dumb"
  5.3396 +  driver, say Y here. This includes HUB6 support, shared serial
  5.3397 +  interrupts, special multiport support, support for more than the
  5.3398 +  four COM 1/2/3/4 boards, etc.
  5.3399 +
  5.3400 +  Note that the answer to this question won't directly affect the
  5.3401 +  kernel: saying N will just cause the configurator to skip all
  5.3402 +  the questions about serial driver options. If unsure, say N.
  5.3403 +
  5.3404 +Support more than 4 serial ports
  5.3405 +CONFIG_SERIAL_MANY_PORTS
  5.3406 +  Say Y here if you have dumb serial boards other than the four
  5.3407 +  standard COM 1/2/3/4 ports. This may happen if you have an AST
  5.3408 +  FourPort, Accent Async, Boca (read the Boca mini-HOWTO, available
  5.3409 +  from <http://www.tldp.org/docs.html#howto>), or other custom
  5.3410 +  serial port hardware which acts similar to standard serial port
  5.3411 +  hardware. If you only use the standard COM 1/2/3/4 ports, you can
  5.3412 +  say N here to save some memory. You can also say Y if you have an
  5.3413 +  "intelligent" multiport card such as Cyclades, Digiboards, etc.
  5.3414 +
  5.3415 +Support for sharing serial interrupts
  5.3416 +CONFIG_SERIAL_SHARE_IRQ
  5.3417 +  Some serial boards have hardware support which allows multiple dumb
  5.3418 +  serial ports on the same board to share a single IRQ. To enable
  5.3419 +  support for this in the serial driver, say Y here.
  5.3420 +
  5.3421 +Auto-detect IRQ on standard ports (unsafe)
  5.3422 +CONFIG_SERIAL_DETECT_IRQ
  5.3423 +  Say Y here if you want the kernel to try to guess which IRQ
  5.3424 +  to use for your serial port.
  5.3425 +
  5.3426 +  This is considered unsafe; it is far better to configure the IRQ in
  5.3427 +  a boot script using the setserial command.
  5.3428 +
  5.3429 +  If unsure, say N.
  5.3430 +
  5.3431 +Support special multiport boards
  5.3432 +CONFIG_SERIAL_MULTIPORT
  5.3433 +  Some multiport serial ports have special ports which are used to
  5.3434 +  signal when there are any serial ports on the board which need
  5.3435 +  servicing. Say Y here to enable the serial driver to take advantage
  5.3436 +  of those special I/O ports.
  5.3437 +
  5.3438 +SGI Zilog85C30 serial support
  5.3439 +CONFIG_SGI_SERIAL
  5.3440 +  If you want to use your SGI's built-in serial ports under Linux,
  5.3441 +  answer Y.
  5.3442 +
  5.3443 +SGI Newport Graphics support
  5.3444 +CONFIG_SGI_NEWPORT_GFX
  5.3445 +  If you have an SGI machine and you want to compile the graphics
  5.3446 +  drivers, say Y here. This will include the code for the
  5.3447 +  /dev/graphics and /dev/gfx drivers into the kernel for supporting
  5.3448 +  virtualized access to your graphics hardware.
  5.3449 +
  5.3450 +SGI Newport Console support
  5.3451 +CONFIG_SGI_NEWPORT_CONSOLE
  5.3452 +  Say Y here if you want the console on the Newport aka XL graphics
  5.3453 +  card of your Indy.  Most people say Y here.
  5.3454 +
  5.3455 +SGI DS1286 RTC support
  5.3456 +CONFIG_SGI_DS1286
  5.3457 +  If you say Y here and create a character special file /dev/rtc with
  5.3458 +  major number 10 and minor number 135 using mknod ("man mknod"), you
  5.3459 +  will get access to the real time clock built into your computer.
  5.3460 +  Every SGI has such a clock built in. It reports status information
  5.3461 +  via the file /proc/rtc and its behaviour is set by various ioctls on
  5.3462 +  /dev/rtc.
  5.3463 +
  5.3464 +Indy/I2 Hardware Watchdog
  5.3465 +CONFIG_INDYDOG
  5.3466 +  Hardwaredriver for the Indy's/I2's watchdog. This is a
  5.3467 +  watchdog timer that will reboot the machine after a 60 second 
  5.3468 +  timer expired and no process has written to /dev/watchdog during
  5.3469 +  that time.
  5.3470 +
  5.3471 +Support the Bell Technologies HUB6 card
  5.3472 +CONFIG_HUB6
  5.3473 +  Say Y here to enable support in the dumb serial driver to support
  5.3474 +  the HUB6 card.
  5.3475 +
  5.3476 +PCMCIA serial device support
  5.3477 +CONFIG_PCMCIA_SERIAL_CS
  5.3478 +  Say Y here to enable support for 16-bit PCMCIA serial devices,
  5.3479 +  including serial port cards, modems, and the modem functions of
  5.3480 +  multi-function Ethernet/modem cards. (PCMCIA- or PC-cards are
  5.3481 +  credit-card size devices often used with laptops.)
  5.3482 +
  5.3483 +  This driver is also available as a module ( = code which can be
  5.3484 +  inserted in and removed from the running kernel whenever you want).
  5.3485 +  The module will be called serial_cs.o.  If you want to compile it as
  5.3486 +  a module, say M here and read <file:Documentation/modules.txt>.
  5.3487 +  If unsure, say N.
  5.3488 +
  5.3489 +CONFIG_SYNCLINK_CS
  5.3490 +  Enable support for the SyncLink PC Card serial adapter, running
  5.3491 +  asynchronous and HDLC communications up to 512Kbps. The port is
  5.3492 +  selectable for RS-232, V.35, RS-449, RS-530, and X.21
  5.3493 +
  5.3494 +  This driver may be built as a module ( = code which can be
  5.3495 +  inserted in and removed from the running kernel whenever you want).
  5.3496 +  The module will be called synclinkmp.o.  If you want to do that, say M
  5.3497 +  here.
  5.3498 +
  5.3499 +ACP Modem (Mwave) support
  5.3500 +CONFIG_MWAVE
  5.3501 +  The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
  5.3502 +  kernel driver and a user level application. Together these components
  5.3503 +  support direct attachment to public switched telephone networks (PSTNs)
  5.3504 +  and support selected world wide countries.
  5.3505 +
  5.3506 +  This version of the ACP Modem driver supports the IBM Thinkpad 600E,
  5.3507 +  600, and 770 that include on board ACP modem hardware.
  5.3508 +
  5.3509 +  The modem also supports the standard communications port interface
  5.3510 +  (ttySx) and is compatible with the Hayes AT Command Set.
  5.3511 +
  5.3512 +  The user level application needed to use this driver can be found at
  5.3513 +  the IBM Linux Technology Center (LTC) web site:
  5.3514 +  <http://www.ibm.com/linux/ltc/>.
  5.3515 +
  5.3516 +  If you own one of the above IBM Thinkpads which has the Mwave chipset
  5.3517 +  in it, say Y.
  5.3518 +
  5.3519 +  This driver is also available as a module ( = code which can be
  5.3520 +  inserted in and removed from the running kernel whenever you want).
  5.3521 +  The module will be called mwave.o. If you want to compile it as
  5.3522 +  a module, say M here and read Documentation/modules.txt.
  5.3523 +
  5.3524 +/dev/agpgart (AGP Support)
  5.3525 +CONFIG_AGP
  5.3526 +  AGP (Accelerated Graphics Port) is a bus system mainly used to
  5.3527 +  connect graphics cards to the rest of the system.
  5.3528 +
  5.3529 +  If you have an AGP system and you say Y here, it will be possible to
  5.3530 +  use the AGP features of your 3D rendering video card. This code acts
  5.3531 +  as a sort of "AGP driver" for the motherboard's chipset.
  5.3532 +
  5.3533 +  If you need more texture memory than you can get with the AGP GART
  5.3534 +  (theoretically up to 256 MB, but in practice usually 64 or 128 MB
  5.3535 +  due to kernel allocation issues), you could use PCI accesses
  5.3536 +  and have up to a couple gigs of texture space.
  5.3537 +
  5.3538 +  Note that this is the only means to have XFree4/GLX use
  5.3539 +  write-combining with MTRR support on the AGP bus. Without it, OpenGL
  5.3540 +  direct rendering will be a lot slower but still faster than PIO.
  5.3541 +
  5.3542 +  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  5.3543 +  use GLX or DRI.  If unsure, say N.
  5.3544 +
  5.3545 +  This driver is available as a module.  If you want to compile it as
  5.3546 +  a module, say M here and read <file:Documentation/modules.txt>.  The
  5.3547 +  module will be called agpgart.o.
  5.3548 +
  5.3549 +Intel 440LX/BX/GX/815/820/830/840/845/850/860 support
  5.3550 +CONFIG_AGP_INTEL
  5.3551 +  This option gives you AGP support for the GLX component of the
  5.3552 +  XFree86 4.x on Intel 440LX/BX/GX, 815, 820, 830, 840, 845, 850 and 860 chipsets.
  5.3553 +
  5.3554 +  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  5.3555 +  use GLX or DRI.  If unsure, say N.
  5.3556 +
  5.3557 +Intel 460GX support
  5.3558 +CONFIG_AGP_I460
  5.3559 +  This option gives you AGP support for the Intel 460GX chipset.  This
  5.3560 +  chipset, the first to support Intel Itanium processors, is new and
  5.3561 +  this option is correspondingly a little experimental.
  5.3562 +
  5.3563 +  If you don't have a 460GX based machine (such as BigSur) with an AGP 
  5.3564 +  slot then this option isn't going to do you much good.  If you're
  5.3565 +  dying to do Direct Rendering on IA-64, this is what you're looking for.
  5.3566 +
  5.3567 +Intel I810/I815 DC100/I810e support
  5.3568 +CONFIG_AGP_I810
  5.3569 +  This option gives you AGP support for the Xserver on the Intel 810
  5.3570 +  815 and 830m chipset boards for their on-board integrated graphics. This
  5.3571 +  is required to do any useful video modes with these boards.
  5.3572 +
  5.3573 +VIA chipset support
  5.3574 +CONFIG_AGP_VIA
  5.3575 +  This option gives you AGP support for the GLX component of the
  5.3576 +  XFree86 4.x on VIA MPV3/Apollo Pro chipsets.
  5.3577 +
  5.3578 +  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  5.3579 +  use GLX or DRI.  If unsure, say N.
  5.3580 +
  5.3581 +AMD Irongate, 761, and 762 support
  5.3582 +CONFIG_AGP_AMD
  5.3583 +  This option gives you AGP support for the GLX component of the
  5.3584 +  XFree86 4.x on AMD Irongate, 761, and 762 chipsets.
  5.3585 +
  5.3586 +  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  5.3587 +  use GLX or DRI.  If unsure, say N.
  5.3588 +
  5.3589 +CONFIG_AGP_AMD_8151
  5.3590 +  This option gives you AGP support for the GLX component of
  5.3591 +  XFree86 on AMD K8 with an AGP 8151 chipset.
  5.3592 +
  5.3593 +  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  5.3594 +  use GLX or DRI.  If unsure, say N.
  5.3595 +
  5.3596 +Generic SiS support
  5.3597 +CONFIG_AGP_SIS
  5.3598 +  This option gives you AGP support for the GLX component of the "soon
  5.3599 +  to be released" XFree86 4.x on Silicon Integrated Systems [SiS]
  5.3600 +  chipsets.
  5.3601 +
  5.3602 +  Note that 5591/5592 AGP chipsets are NOT supported.
  5.3603 +
  5.3604 +  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  5.3605 +  use GLX or DRI.  If unsure, say N.
  5.3606 +
  5.3607 +Serverworks LE/HE support
  5.3608 +CONFIG_AGP_SWORKS
  5.3609 +  Say Y here to support the Serverworks AGP card.  See 
  5.3610 +  <http://www.serverworks.com/> for product descriptions and images.
  5.3611 +
  5.3612 +ALI chipset support
  5.3613 +CONFIG_AGP_ALI
  5.3614 +  This option gives you AGP support for the GLX component of the
  5.3615 +  XFree86 4.x on the following ALi chipsets.  The supported chipsets
  5.3616 +  include M1541, M1621, M1631, M1632, M1641,M1647,and M1651.
  5.3617 +  For the ALi-chipset question, ALi suggests you refer to
  5.3618 +  <http://www.ali.com.tw/eng/support/index.shtml>.
  5.3619 +
  5.3620 +  The M1541 chipset can do AGP 1x and 2x, but note that there is an
  5.3621 +  acknowledged incompatibility with Matrox G200 cards. Due to
  5.3622 +  timing issues, this chipset cannot do AGP 2x with the G200.
  5.3623 +  This is a hardware limitation. AGP 1x seems to be fine, though.
  5.3624 +
  5.3625 +  You should say Y here if you use XFree86 3.3.6 or 4.x and want to
  5.3626 +  use GLX or DRI.  If unsure, say N.
  5.3627 +
  5.3628 +CONFIG_AGP_HP_ZX1
  5.3629 +  This option gives you AGP GART support for the HP ZX1 chipset
  5.3630 +  for IA64 processors.
  5.3631 +
  5.3632 +Support for ISA-bus hardware
  5.3633 +CONFIG_ISA
  5.3634 +  Find out whether you have ISA slots on your motherboard.  ISA is the
  5.3635 +  name of a bus system, i.e. the way the CPU talks to the other stuff
  5.3636 +  inside your box.  Other bus systems are PCI, EISA, MicroChannel
  5.3637 +  (MCA) or VESA.  ISA is an older system, now being displaced by PCI;
  5.3638 +  newer boards don't support it.  If you have ISA, say Y, otherwise N.
  5.3639 +
  5.3640 +Support for PCI bus hardware
  5.3641 +CONFIG_PCI
  5.3642 +  Find out whether you have a PCI motherboard. PCI is the name of a
  5.3643 +  bus system, i.e. the way the CPU talks to the other stuff inside
  5.3644 +  your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
  5.3645 +  VESA. If you have PCI, say Y, otherwise N.
  5.3646 +
  5.3647 +  The PCI-HOWTO, available from
  5.3648 +  <http://www.tldp.org/docs.html#howto>, contains valuable
  5.3649 +  information about which PCI hardware does work under Linux and which
  5.3650 +  doesn't.
  5.3651 +
  5.3652 +PCI support
  5.3653 +CONFIG_PCI_INTEGRATOR
  5.3654 +  Find out whether you have a PCI motherboard. PCI is the name of a
  5.3655 +  bus system, i.e. the way the CPU talks to the other stuff inside
  5.3656 +  your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
  5.3657 +  VESA. If you have PCI, say Y, otherwise N.
  5.3658 +
  5.3659 +  The PCI-HOWTO, available from
  5.3660 +  <http://www.tldp.org/docs.html#howto>, contains valuable
  5.3661 +  information about which PCI hardware does work under Linux and which
  5.3662 +  doesn't.
  5.3663 +
  5.3664 +QSpan PCI
  5.3665 +CONFIG_PCI_QSPAN
  5.3666 +  Find out whether you have a PCI motherboard. PCI is the name of a
  5.3667 +  bus system, i.e. the way the CPU talks to the other stuff inside
  5.3668 +  your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
  5.3669 +  VESA. If you have PCI, say Y, otherwise N.
  5.3670 +
  5.3671 +  The PCI-HOWTO, available from
  5.3672 +  <http://www.tldp.org/docs.html#howto>, contains valuable
  5.3673 +  information about which PCI hardware does work under Linux and which
  5.3674 +  doesn't.
  5.3675 +
  5.3676 +# Choice: pci_access
  5.3677 +PCI access mode
  5.3678 +CONFIG_PCI_GOBIOS
  5.3679 +  On PCI systems, the BIOS can be used to detect the PCI devices and
  5.3680 +  determine their configuration. However, some old PCI motherboards
  5.3681 +  have BIOS bugs and may crash if this is done. Also, some embedded
  5.3682 +  PCI-based systems don't have any BIOS at all. Linux can also try to
  5.3683 +  detect the PCI hardware directly without using the BIOS.
  5.3684 +
  5.3685 +  With this option, you can specify how Linux should detect the PCI
  5.3686 +  devices. If you choose "BIOS", the BIOS will be used, if you choose
  5.3687 +  "Direct", the BIOS won't be used, and if you choose "Any", the
  5.3688 +  kernel will try the direct access method and falls back to the BIOS
  5.3689 +  if that doesn't work. If unsure, go with the default, which is
  5.3690 +  "Any".
  5.3691 +
  5.3692 +PCI device name database
  5.3693 +CONFIG_PCI_NAMES
  5.3694 +  By default, the kernel contains a database of all known PCI device
  5.3695 +  names to make the information in /proc/pci, /proc/ioports and
  5.3696 +  similar files comprehensible to the user. This database increases
  5.3697 +  size of the kernel image by about 80KB, but it gets freed after the
  5.3698 +  system boots up, so it doesn't take up kernel memory. Anyway, if you
  5.3699 +  are building an installation floppy or kernel for an embedded system
  5.3700 +  where kernel image size really matters, you can disable this feature
  5.3701 +  and you'll get device ID numbers instead of names.
  5.3702 +
  5.3703 +  When in doubt, say Y.
  5.3704 +
  5.3705 +Generic PCI hotplug support
  5.3706 +CONFIG_HOTPLUG_PCI
  5.3707 +  Say Y here if you have a motherboard with a PCI Hotplug controller.
  5.3708 +  This allows you to add and remove PCI cards while the machine is
  5.3709 +  powered up and running.  The file system pcihpfs must be mounted
  5.3710 +  in order to interact with any PCI Hotplug controllers.
  5.3711 +
  5.3712 +  This code is also available as a module ( = code which can be
  5.3713 +  inserted in and removed from the running kernel whenever you want).
  5.3714 +  The module will be called pci_hotplug.o. If you want to compile it
  5.3715 +  as a module, say M here and read <file:Documentation/modules.txt>.
  5.3716 +
  5.3717 +  When in doubt, say N.
  5.3718 +
  5.3719 +Compaq PCI Hotplug driver
  5.3720 +CONFIG_HOTPLUG_PCI_COMPAQ
  5.3721 +  Say Y here if you have a motherboard with a Compaq PCI Hotplug
  5.3722 +  controller.
  5.3723 +
  5.3724 +  This code is also available as a module ( = code which can be
  5.3725 +  inserted in and removed from the running kernel whenever you want).
  5.3726 +  The module will be called cpqphp.o. If you want to compile it
  5.3727 +  as a module, say M here and read <file:Documentation/modules.txt>.
  5.3728 +
  5.3729 +  When in doubt, say N.
  5.3730 +
  5.3731 +PCI Compaq Hotplug controller NVRAM support
  5.3732 +CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM
  5.3733 +  Say Y here if you have a Compaq server that has a PCI Hotplug
  5.3734 +  controller.  This will allow the PCI Hotplug driver to store the PCI
  5.3735 +  system configuration options in NVRAM.
  5.3736 +
  5.3737 +  When in doubt, say N.
  5.3738 +
  5.3739 +ACPI PCI Hotplug driver
  5.3740 +CONFIG_HOTPLUG_PCI_ACPI
  5.3741 +  Say Y here if you have a system that supports PCI Hotplug using
  5.3742 +  ACPI.
  5.3743 +
  5.3744 +  This code is also available as a module ( = code which can be
  5.3745 +  inserted in and removed from the running kernel whenever you want).
  5.3746 +  The module will be called acpiphp.o. If you want to compile it
  5.3747 +  as a module, say M here and read <file:Documentation/modules.txt>.
  5.3748 +
  5.3749 +MCA support
  5.3750 +CONFIG_MCA
  5.3751 +  MicroChannel Architecture is found in some IBM PS/2 machines and
  5.3752 +  laptops.  It is a bus system similar to PCI or ISA. See
  5.3753 +  <file:Documentation/mca.txt> (and especially the web page given
  5.3754 +  there) before attempting to build an MCA bus kernel.
  5.3755 +
  5.3756 +Support for EISA-bus hardware
  5.3757 +CONFIG_EISA
  5.3758 +  The Extended Industry Standard Architecture (EISA) bus was
  5.3759 +  developed as an open alternative to the IBM MicroChannel bus.
  5.3760 +
  5.3761 +  The EISA bus provided some of the features of the IBM MicroChannel
  5.3762 +  bus while maintaining backward compatibility with cards made for
  5.3763 +  the older ISA bus.  The EISA bus saw limited use between 1988 and
  5.3764 +  1995 when it was made obsolete by the PCI bus.
  5.3765 +
  5.3766 +  Say Y here if you are building a kernel for an EISA-based machine.
  5.3767 +
  5.3768 +  Otherwise, say N.
  5.3769 +
  5.3770 +SGI Visual Workstation support
  5.3771 +CONFIG_VISWS
  5.3772 +  The SGI Visual Workstation series is an IA32-based workstation
  5.3773 +  based on SGI systems chips with some legacy PC hardware attached.
  5.3774 +  Say Y here to create a kernel to run on the SGI 320 or 540.
  5.3775 +  A kernel compiled for the Visual Workstation will not run on other
  5.3776 +  PC boards and vice versa.
  5.3777 +  See <file:Documentation/sgi-visws.txt> for more.
  5.3778 +
  5.3779 +SGI Visual Workstation framebuffer support
  5.3780 +CONFIG_FB_SGIVW
  5.3781 +  SGI Visual Workstation support for framebuffer graphics.
  5.3782 +
  5.3783 +I2O support
  5.3784 +CONFIG_I2O
  5.3785 +  The Intelligent Input/Output (I2O) architecture allows hardware
  5.3786 +  drivers to be split into two parts: an operating system specific
  5.3787 +  module called the OSM and an hardware specific module called the
  5.3788 +  HDM. The OSM can talk to a whole range of HDM's, and ideally the
  5.3789 +  HDM's are not OS dependent. This allows for the same HDM driver to
  5.3790 +  be used under different operating systems if the relevant OSM is in
  5.3791 +  place. In order for this to work, you need to have an I2O interface
  5.3792 +  adapter card in your computer. This card contains a special I/O
  5.3793 +  processor (IOP), thus allowing high speeds since the CPU does not
  5.3794 +  have to deal with I/O.
  5.3795 +
  5.3796 +  If you say Y here, you will get a choice of interface adapter
  5.3797 +  drivers and OSM's with the following questions.
  5.3798 +
  5.3799 +  This support is also available as a module ( = code which can be
  5.3800 +  inserted in and removed from the running kernel whenever you want).
  5.3801 +  If you want to compile it as a module, say M here and read
  5.3802 +  <file:Documentation/modules.txt>.  You will get modules called
  5.3803 +  i2o_core.o and i2o_config.o.
  5.3804 +
  5.3805 +  If unsure, say N.
  5.3806 +
  5.3807 +I2O PCI support
  5.3808 +CONFIG_I2O_PCI
  5.3809 +  Say Y for support of PCI bus I2O interface adapters. Currently this
  5.3810 +  is the only variety supported, so you should say Y.
  5.3811 +
  5.3812 +  This support is also available as a module called i2o_pci.o ( = code
  5.3813 +  which can be inserted in and removed from the running kernel
  5.3814 +  whenever you want). If you want to compile it as a module, say M
  5.3815 +  here and read <file:Documentation/modules.txt>.
  5.3816 +
  5.3817 +I2O Block OSM
  5.3818 +CONFIG_I2O_BLOCK
  5.3819 +  Include support for the I2O Block OSM. The Block OSM presents disk
  5.3820 +  and other structured block devices to the operating system.
  5.3821 +
  5.3822 +  This support is also available as a module called i2o_block.o ( =
  5.3823 +  code which can be inserted in and removed from the running kernel
  5.3824 +  whenever you want). If you want to compile it as a module, say M
  5.3825 +  here and read <file:Documentation/modules.txt>.
  5.3826 +
  5.3827 +I2O LAN OSM
  5.3828 +CONFIG_I2O_LAN
  5.3829 +  Include support for the LAN OSM. You will also need to include
  5.3830 +  support for token ring or FDDI if you wish to use token ring or FDDI
  5.3831 +  I2O cards with this driver.
  5.3832 +
  5.3833 +  This support is also available as a module called i2o_lan.o ( = code
  5.3834 +  which can be inserted in and removed from the running kernel
  5.3835 +  whenever you want). If you want to compile it as a module, say M
  5.3836 +  here and read <file:Documentation/modules.txt>.
  5.3837 +
  5.3838 +I2O SCSI OSM
  5.3839 +CONFIG_I2O_SCSI
  5.3840 +  Allows direct SCSI access to SCSI devices on a SCSI or FibreChannel
  5.3841 +  I2O controller. You can use both the SCSI and Block OSM together if
  5.3842 +  you wish.
  5.3843 +
  5.3844 +  This support is also available as a module called i2o_scsi.o ( =
  5.3845 +  code which can be inserted in and removed from the running kernel
  5.3846 +  whenever you want). If you want to compile it as a module, say M
  5.3847 +  here and read <file:Documentation/modules.txt>.
  5.3848 +
  5.3849 +I2O /proc support
  5.3850 +CONFIG_I2O_PROC
  5.3851 +  If you say Y here and to "/proc file system support", you will be
  5.3852 +  able to read I2O related information from the virtual directory
  5.3853 +  /proc/i2o.
  5.3854 +
  5.3855 +  This support is also available as a module called i2o_proc.o ( =
  5.3856 +  code which can be inserted in and removed from the running kernel
  5.3857 +  whenever you want). If you want to compile it as a module, say M
  5.3858 +  here and read <file:Documentation/modules.txt>.
  5.3859 +
  5.3860 +Plug and Play support
  5.3861 +CONFIG_PNP
  5.3862 +  Plug and Play (PnP) is a standard for peripherals which allows those
  5.3863 +  peripherals to be configured by software, e.g. assign IRQ's or other
  5.3864 +  parameters. No jumpers on the cards are needed, instead the values
  5.3865 +  are provided to the cards from the BIOS, from the operating system,
  5.3866 +  or using a user-space utility.
  5.3867 +
  5.3868 +  Say Y here if you would like Linux to configure your Plug and Play
  5.3869 +  devices. You should then also say Y to "ISA Plug and Play support",
  5.3870 +  below. Alternatively, you can say N here and configure your PnP
  5.3871 +  devices using the user space utilities contained in the isapnptools
  5.3872 +  package.
  5.3873 +
  5.3874 +  This support is also available as a module ( = code which can be
  5.3875 +  inserted in and removed from the running kernel whenever you want).
  5.3876 +  If you want to compile it as a module, say M here and read
  5.3877 +  <file:Documentation/modules.txt>.
  5.3878 +
  5.3879 +ISA Plug and Play support
  5.3880 +CONFIG_ISAPNP
  5.3881 +  Say Y here if you would like support for ISA Plug and Play devices.
  5.3882 +  Some information is in <file:Documentation/isapnp.txt>.
  5.3883 +
  5.3884 +  This support is also available as a module called isapnp.o ( =
  5.3885 +  code which can be inserted in and removed from the running kernel
  5.3886 +  whenever you want). If you want to compile it as a module, say M
  5.3887 +  here and read <file:Documentation/modules.txt>.
  5.3888 +
  5.3889 +  If unsure, say Y.
  5.3890 +
  5.3891 +PNPBIOS support
  5.3892 +CONFIG_PNPBIOS
  5.3893 +  Linux uses the PNPBIOS as defined in "Plug and Play BIOS
  5.3894 +  Specification Version 1.0A May 5, 1994" to autodetect built-in
  5.3895 +  mainboard resources (e.g. parallel port resources).
  5.3896 +
  5.3897 +  Other features (e.g. change resources, ESCD, event notification,
  5.3898 +  Docking station information, ISAPNP services) are not used.
  5.3899 +
  5.3900 +  Note: ACPI is expected to supersede PNPBIOS some day, currently it
  5.3901 +  co-exists nicely.
  5.3902 +
  5.3903 +  See latest pcmcia-cs (stand-alone package) for a nice "lspnp" tools,
  5.3904 +  or have a look at /proc/bus/pnp.
  5.3905 +
  5.3906 +  If unsure, say Y.
  5.3907 +
  5.3908 +Support for hot-pluggable devices
  5.3909 +CONFIG_HOTPLUG
  5.3910 +  Say Y here if you want to plug devices into your computer while
  5.3911 +  the system is running, and be able to use them quickly.  In many
  5.3912 +  cases, the devices can likewise be unplugged at any time too.
  5.3913 +
  5.3914 +  One well known example of this is PCMCIA- or PC-cards, credit-card
  5.3915 +  size devices such as network cards, modems or hard drives which are
  5.3916 +  plugged into slots found on all modern laptop computers.  Another
  5.3917 +  example, used on modern desktops as well as laptops, is USB.
  5.3918 +
  5.3919 +  Enable HOTPLUG and KMOD, and build a modular kernel.  Get agent
  5.3920 +  software (at <http://linux-hotplug.sourceforge.net/>) and install it.
  5.3921 +  Then your kernel will automatically call out to a user mode "policy
  5.3922 +  agent" (/sbin/hotplug) to load modules and set up software needed
  5.3923 +  to use devices as you hotplug them.
  5.3924 +
  5.3925 +PCMCIA/CardBus support
  5.3926 +CONFIG_PCMCIA
  5.3927 +  Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
  5.3928 +  computer.  These are credit-card size devices such as network cards,
  5.3929 +  modems or hard drives often used with laptops computers.  There are
  5.3930 +  actually two varieties of these cards: the older 16 bit PCMCIA cards
  5.3931 +  and the newer 32 bit CardBus cards.  If you want to use CardBus
  5.3932 +  cards, you need to say Y here and also to "CardBus support" below.
  5.3933 +
  5.3934 +  To use your PC-cards, you will need supporting software from David
  5.3935 +  Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
  5.3936 +  for location).  Please also read the PCMCIA-HOWTO, available from
  5.3937 +  <http://www.tldp.org/docs.html#howto>.
  5.3938 +
  5.3939 +  This driver is also available as a module ( = code which can be
  5.3940 +  inserted in and removed from the running kernel whenever you want).
  5.3941 +  When compiled this way, there will be modules called pcmcia_core.o
  5.3942 +  and ds.o.  If you want to compile it as a module, say M here and
  5.3943 +  read <file:Documentation/modules.txt>.
  5.3944 +
  5.3945 +CardBus card and (Yenta) bridge support
  5.3946 +CONFIG_CARDBUS
  5.3947 +  CardBus is a bus mastering architecture for PC-cards, which allows
  5.3948 +  for 32 bit PC-cards (the original PCMCIA standard specifies only
  5.3949 +  a 16 bit wide bus). Many newer PC-cards are actually CardBus cards.
  5.3950 +
  5.3951 +  This option enables support for CardBus PC Cards, as well as support
  5.3952 +  for CardBus host bridges.  Virtually all modern PCMCIA bridges are
  5.3953 +  CardBus compatible.  A "bridge" is the hardware inside your computer
  5.3954 +  that PCMCIA cards are plugged into.
  5.3955 +
  5.3956 +  To use your PC-cards, you will need supporting software from David
  5.3957 +  Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
  5.3958 +  for location).
  5.3959 +
  5.3960 +  If unsure, say Y.
  5.3961 +
  5.3962 +i82092 compatible bridge support
  5.3963 +CONFIG_I82092
  5.3964 +  This provides support for the Intel I82092AA PCI-to-PCMCIA bridge device,
  5.3965 +  found in some older laptops and more commonly in evaluation boards for the
  5.3966 +  chip.
  5.3967 +
  5.3968 +i82365 compatible host bridge support
  5.3969 +CONFIG_I82365
  5.3970 +  Say Y here to include support for ISA-bus PCMCIA host bridges that
  5.3971 +  are register compatible with the Intel i82365.  These are found on
  5.3972 +  older laptops and ISA-bus card readers for desktop systems.  A
  5.3973 +  "bridge" is the hardware inside your computer that PCMCIA cards are
  5.3974 +  plugged into. If unsure, say N.
  5.3975 +
  5.3976 +Databook TCIC host bridge support
  5.3977 +CONFIG_TCIC
  5.3978 +  Say Y here to include support for the Databook TCIC family of PCMCIA
  5.3979 +  host bridges. These are only found on a handful of old systems.
  5.3980 +  "Bridge" is the name used for the hardware inside your computer that
  5.3981 +  PCMCIA cards are plugged into. If unsure, say N.
  5.3982 +
  5.3983 +System V IPC
  5.3984 +CONFIG_SYSVIPC
  5.3985 +  Inter Process Communication is a suite of library functions and
  5.3986 +  system calls which let processes (running programs) synchronize and
  5.3987 +  exchange information. It is generally considered to be a good thing,
  5.3988 +  and some programs won't run unless you say Y here. In particular, if
  5.3989 +  you want to run the DOS emulator dosemu under Linux (read the
  5.3990 +  DOSEMU-HOWTO, available from
  5.3991 +  <http://www.tldp.org/docs.html#howto>), you'll need to say Y
  5.3992 +  here.
  5.3993 +
  5.3994 +  You can find documentation about IPC with "info ipc" and also in
  5.3995 +  section 6.4 of the Linux Programmer's Guide, available from
  5.3996 +  <http://www.tldp.org/docs.html#guide>.
  5.3997 +
  5.3998 +BSD Process Accounting
  5.3999 +CONFIG_BSD_PROCESS_ACCT
  5.4000 +  If you say Y here, a user level program will be able to instruct the
  5.4001 +  kernel (via a special system call) to write process accounting
  5.4002 +  information to a file: whenever a process exits, information about
  5.4003 +  that process will be appended to the file by the kernel.  The
  5.4004 +  information includes things such as creation time, owning user,
  5.4005 +  command name, memory usage, controlling terminal etc. (the complete
  5.4006 +  list is in the struct acct in <file:include/linux/acct.h>).  It is
  5.4007 +  up to the user level program to do useful things with this
  5.4008 +  information.  This is generally a good idea, so say Y.
  5.4009 +
  5.4010 +Sysctl support
  5.4011 +CONFIG_SYSCTL
  5.4012 +  The sysctl interface provides a means of dynamically changing
  5.4013 +  certain kernel parameters and variables on the fly without requiring
  5.4014 +  a recompile of the kernel or reboot of the system.  The primary
  5.4015 +  interface consists of a system call, but if you say Y to "/proc
  5.4016 +  file system support", a tree of modifiable sysctl entries will be
  5.4017 +  generated beneath the /proc/sys directory. They are explained in the
  5.4018 +  files in <file:Documentation/sysctl/>.  Note that enabling this
  5.4019 +  option will enlarge the kernel by at least 8 KB.
  5.4020 +
  5.4021 +  As it is generally a good thing, you should say Y here unless
  5.4022 +  building a kernel for install/rescue disks or your system is very
  5.4023 +  limited in memory.
  5.4024 +
  5.4025 +# Choice: kcore
  5.4026 +Kernel core (/proc/kcore) format
  5.4027 +CONFIG_KCORE_ELF
  5.4028 +  If you enabled support for /proc file system then the file
  5.4029 +  /proc/kcore will contain the kernel core image. This can be used
  5.4030 +  in gdb:
  5.4031 +
  5.4032 +  $ cd /usr/src/linux ; gdb vmlinux /proc/kcore
  5.4033 +
  5.4034 +  You have two choices here: ELF and A.OUT. Selecting ELF will make
  5.4035 +  /proc/kcore appear in ELF core format as defined by the Executable
  5.4036 +  and Linking Format specification. Selecting A.OUT will choose the
  5.4037 +  old "a.out" format which may be necessary for some old versions
  5.4038 +  of binutils or on some architectures.
  5.4039 +
  5.4040 +  This is especially useful if you have compiled the kernel with the
  5.4041 +  "-g" option to preserve debugging information. It is mainly used
  5.4042 +  for examining kernel data structures on the live kernel so if you
  5.4043 +  don't understand what this means or are not a kernel hacker, just
  5.4044 +  leave it at its default value ELF.
  5.4045 +
  5.4046 +Select a.out format for /proc/kcore
  5.4047 +CONFIG_KCORE_AOUT
  5.4048 +  Not necessary unless you're using a very out-of-date binutils
  5.4049 +  version.  You probably want KCORE_ELF.
  5.4050 +
  5.4051 +Kernel support for ELF binaries
  5.4052 +CONFIG_BINFMT_ELF
  5.4053 +  ELF (Executable and Linkable Format) is a format for libraries and
  5.4054 +  executables used across different architectures and operating
  5.4055 +  systems. Saying Y here will enable your kernel to run ELF binaries
  5.4056 +  and enlarge it by about 13 KB. ELF support under Linux has now all
  5.4057 +  but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC)
  5.4058 +  because it is portable (this does *not* mean that you will be able
  5.4059 +  to run executables from different architectures or operating systems
  5.4060 +  however) and makes building run-time libraries very easy. Many new
  5.4061 +  executables are distributed solely in ELF format. You definitely
  5.4062 +  want to say Y here.
  5.4063 +
  5.4064 +  Information about ELF is contained in the ELF HOWTO available from
  5.4065 +  <http://www.tldp.org/docs.html#howto>.
  5.4066 +
  5.4067 +  If you find that after upgrading from Linux kernel 1.2 and saying Y
  5.4068 +  here, you still can't run any ELF binaries (they just crash), then
  5.4069 +  you'll have to install the newest ELF runtime libraries, including
  5.4070 +  ld.so (check the file <file:Documentation/Changes> for location and
  5.4071 +  latest version).
  5.4072 +
  5.4073 +  If you want to compile this as a module ( = code which can be
  5.4074 +  inserted in and removed from the running kernel whenever you want),
  5.4075 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.4076 +  will be called binfmt_elf.o. Saying M or N here is dangerous because
  5.4077 +  some crucial programs on your system might be in ELF format.
  5.4078 +
  5.4079 +Kernel support for a.out binaries
  5.4080 +CONFIG_BINFMT_AOUT
  5.4081 +  A.out (Assembler.OUTput) is a set of formats for libraries and
  5.4082 +  executables used in the earliest versions of UNIX. Linux used the
  5.4083 +  a.out formats QMAGIC and ZMAGIC until they were replaced with the
  5.4084 +  ELF format.
  5.4085 +
  5.4086 +  As more and more programs are converted to ELF, the use for a.out
  5.4087 +  will gradually diminish. If you disable this option it will reduce
  5.4088 +  your kernel by one page. This is not much and by itself does not
  5.4089 +  warrant removing support. However its removal is a good idea if you
  5.4090 +  wish to ensure that absolutely none of your programs will use this
  5.4091 +  older executable format. If you don't know what to answer at this
  5.4092 +  point then answer Y. If someone told you "You need a kernel with
  5.4093 +  QMAGIC support" then you'll have to say Y here. You may answer M to
  5.4094 +  compile a.out support as a module and later load the module when you
  5.4095 +  want to use a program or library in a.out format. The module will be
  5.4096 +  called binfmt_aout.o. Saying M or N here is dangerous though,
  5.4097 +  because some crucial programs on your system might still be in A.OUT
  5.4098 +  format.
  5.4099 +
  5.4100 +OSF/1 v4 readv/writev compatibility
  5.4101 +CONFIG_OSF4_COMPAT
  5.4102 +  Say Y if you are using OSF/1 binaries (like Netscape and Acrobat)
  5.4103 +  with v4 shared libraries freely available from Compaq. If you're
  5.4104 +  going to use shared libraries from Tru64 version 5.0 or later, say N.
  5.4105 +
  5.4106 +Kernel support for Linux/Intel ELF binaries
  5.4107 +CONFIG_BINFMT_EM86
  5.4108 +  Say Y here if you want to be able to execute Linux/Intel ELF
  5.4109 +  binaries just like native Alpha binaries on your Alpha machine. For
  5.4110 +  this to work, you need to have the emulator /usr/bin/em86 in place.
  5.4111 +
  5.4112 +  You can get the same functionality by saying N here and saying Y to
  5.4113 +  "Kernel support for MISC binaries".
  5.4114 +
  5.4115 +  You may answer M to compile the emulation support as a module and
  5.4116 +  later load the module when you want to use a Linux/Intel binary. The
  5.4117 +  module will be called binfmt_em86.o. If unsure, say Y.
  5.4118 +
  5.4119 +Kernel support for SOM binaries
  5.4120 +CONFIG_BINFMT_SOM
  5.4121 +  SOM is a binary executable format inherited from HP/UX.  Say Y here
  5.4122 +  to be able to load and execute SOM binaries directly.
  5.4123 +
  5.4124 +Kernel support for MISC binaries
  5.4125 +CONFIG_BINFMT_MISC
  5.4126 +  If you say Y here, it will be possible to plug wrapper-driven binary
  5.4127 +  formats into the kernel. You will like this especially when you use
  5.4128 +  programs that need an interpreter to run like Java, Python or
  5.4129 +  Emacs-Lisp. It's also useful if you often run DOS executables under
  5.4130 +  the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
  5.4131 +  <http://www.tldp.org/docs.html#howto>). Once you have
  5.4132 +  registered such a binary class with the kernel, you can start one of
  5.4133 +  those programs simply by typing in its name at a shell prompt; Linux
  5.4134 +  will automatically feed it to the correct interpreter.
  5.4135 +
  5.4136 +  You can do other nice things, too. Read the file
  5.4137 +  <file:Documentation/binfmt_misc.txt> to learn how to use this
  5.4138 +  feature, and <file:Documentation/java.txt> for information about how
  5.4139 +  to include Java support.
  5.4140 +
  5.4141 +  You must say Y to "/proc file system support" (CONFIG_PROC_FS) to
  5.4142 +  use this part of the kernel.
  5.4143 +
  5.4144 +  You may say M here for module support and later load the module when
  5.4145 +  you have use for it; the module is called binfmt_misc.o. If you
  5.4146 +  don't know what to answer at this point, say Y.
  5.4147 +
  5.4148 +Kernel support for JAVA binaries
  5.4149 +CONFIG_BINFMT_JAVA
  5.4150 +  If you say Y here, the kernel will load and execute Java J-code
  5.4151 +  binaries directly.  Note: this option is obsolete and scheduled for
  5.4152 +  removal, use CONFIG_BINFMT_MISC instead.
  5.4153 +
  5.4154 +Solaris binary emulation
  5.4155 +CONFIG_SOLARIS_EMUL
  5.4156 +  This is experimental code which will enable you to run (many)
  5.4157 +  Solaris binaries on your SPARC Linux machine.
  5.4158 +
  5.4159 +  This code is also available as a module ( = code which can be
  5.4160 +  inserted in and removed from the running kernel whenever you want).
  5.4161 +  The module will be called solaris.o. If you want to compile it as a
  5.4162 +  module, say M here and read <file:Documentation/modules.txt>.
  5.4163 +
  5.4164 +SUN SME environment monitoring
  5.4165 +CONFIG_ENVCTRL
  5.4166 +  Kernel support for temperature and fan monitoring on Sun SME
  5.4167 +  machines.
  5.4168 +
  5.4169 +  This code is also available as a module ( = code which can be
  5.4170 +  inserted in and removed from the running kernel whenever you want).
  5.4171 +  The module will be called envctrl.o. If you want to compile it as a
  5.4172 +  module, say M here and read <file:Documentation/modules.txt>.
  5.4173 +
  5.4174 +# Choice: x86type
  5.4175 +Processor family
  5.4176 +CONFIG_M386
  5.4177 +  This is the processor type of your CPU. This information is used for
  5.4178 +  optimizing purposes. In order to compile a kernel that can run on
  5.4179 +  all x86 CPU types (albeit not optimally fast), you can specify
  5.4180 +  "386" here.
  5.4181 +
  5.4182 +  The kernel will not necessarily run on earlier architectures than
  5.4183 +  the one you have chosen, e.g. a Pentium optimized kernel will run on
  5.4184 +  a PPro, but not necessarily on a i486.
  5.4185 +
  5.4186 +  Here are the settings recommended for greatest speed:
  5.4187 +   - "386" for the AMD/Cyrix/Intel 386DX/DXL/SL/SLC/SX, Cyrix/TI
  5.4188 +     486DLC/DLC2, UMC 486SX-S and NexGen Nx586.  Only "386" kernels
  5.4189 +     will run on a 386 class machine.
  5.4190 +   - "486" for the AMD/Cyrix/IBM/Intel 486DX/DX2/DX4 or
  5.4191 +     SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5D or U5S.
  5.4192 +   - "586" for generic Pentium CPUs, possibly lacking the TSC
  5.4193 +     (time stamp counter) register.
  5.4194 +   - "Pentium-Classic" for the Intel Pentium.
  5.4195 +   - "Pentium-MMX" for the Intel Pentium MMX.
  5.4196 +   - "Pentium-Pro" for the Intel Pentium Pro/Celeron/Pentium II.
  5.4197 +   - "Pentium-III" for the Intel Pentium III
  5.4198 +     and Celerons based on the Coppermine core.
  5.4199 +   - "Pentium-4" for the Intel Pentium 4.
  5.4200 +   - "K6" for the AMD K6, K6-II and K6-III (aka K6-3D).
  5.4201 +   - "Athlon" for the AMD K7 family (Athlon/Duron/Thunderbird).
  5.4202 +   - "Elan" for the AMD Elan family (Elan SC400/SC410).
  5.4203 +   - "Crusoe" for the Transmeta Crusoe series.
  5.4204 +   - "Winchip-C6" for original IDT Winchip.
  5.4205 +   - "Winchip-2" for IDT Winchip 2.
  5.4206 +   - "Winchip-2A" for IDT Winchips with 3dNow! capabilities.
  5.4207 +   - "CyrixIII" for VIA Cyrix III or VIA C3.
  5.4208 +   - "VIA C3-2 for VIA C3-2 "Nehemiah" (model 9 and above).
  5.4209 +
  5.4210 +  If you don't know what to do, choose "386".
  5.4211 +
  5.4212 +486
  5.4213 +CONFIG_M486
  5.4214 +  Select this for a x486 processor, ether Intel or one of the
  5.4215 +  compatible processors from AMD, Cyrix, IBM, or Intel.  Includes DX,
  5.4216 +  DX2, and DX4 variants; also SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5D or
  5.4217 +  U5S.
  5.4218 +
  5.4219 +586/K5/5x86/6x86/6x86MX
  5.4220 +CONFIG_M586
  5.4221 +  Select this for an x586 or x686 processor such as the AMD K5, the
  5.4222 +  Intel 5x86 or 6x86, or the Intel 6x86MX.  This choice does not
  5.4223 +  assume the RDTSC instruction.
  5.4224 +
  5.4225 +Pentium Classic
  5.4226 +CONFIG_M586TSC
  5.4227 +  Select this for a Pentium Classic processor with the RDTSC (Read
  5.4228 +  Time Stamp Counter) instruction for benchmarking.
  5.4229 +
  5.4230 +VIA C3-2 (Nehemiah)
  5.4231 +CONFIG_MVIAC3_2
  5.4232 +  Select this for a VIA C3 "Nehemiah". Selecting this enables usage of SSE
  5.4233 +  and tells gcc to treat the CPU as a 686.
  5.4234 +
  5.4235 +  Note, this kernel will not boot on older (pre model 9) C3s.
  5.4236 +
  5.4237 +32-bit PDC
  5.4238 +CONFIG_PDC_NARROW
  5.4239 +  Saying Y here will allow developers with a C180, C200, C240, C360,
  5.4240 +  J200, J210, and/or a J2240 to test 64-bit kernels by providing a
  5.4241 +  wrapper for the 32-bit PDC calls.  Since the machines which require
  5.4242 +  this option do not support over 4G of RAM, this option is targeted
  5.4243 +  for developers of these machines wishing to test changes on both
  5.4244 +  32-bit and 64-bit configurations.
  5.4245 +
  5.4246 +  If unsure, say N.
  5.4247 +
  5.4248 +VGA text console
  5.4249 +CONFIG_VGA_CONSOLE
  5.4250 +  Saying Y here will allow you to use Linux in text mode through a
  5.4251 +  display that complies with the generic VGA standard. Virtually
  5.4252 +  everyone wants that.
  5.4253 +
  5.4254 +  The program SVGATextMode can be used to utilize SVGA video cards to
  5.4255 +  their full potential in text mode. Download it from
  5.4256 +  <ftp://ibiblio.org/pub/Linux/utils/console/>.
  5.4257 +
  5.4258 +  Say Y.
  5.4259 +
  5.4260 +Distribute interrupts on all CPUs by default
  5.4261 +CONFIG_IRQ_ALL_CPUS
  5.4262 +  This option gives the kernel permission to distribute IRQs across
  5.4263 +  multiple CPUs.  Saying N here will route all IRQs to the first
  5.4264 +  CPU. Generally SMP PowerMacs can answer Y. SMP IBM CHRP boxes or
  5.4265 +  Power3 boxes should say N for now.
  5.4266 +
  5.4267 +Video mode selection support
  5.4268 +CONFIG_VIDEO_SELECT
  5.4269 +  This enables support for text mode selection on kernel startup. If
  5.4270 +  you want to take advantage of some high-resolution text mode your
  5.4271 +  card's BIOS offers, but the traditional Linux utilities like
  5.4272 +  SVGATextMode don't, you can say Y here and set the mode using the
  5.4273 +  "vga=" option from your boot loader (lilo or loadlin) or set
  5.4274 +  "vga=ask" which brings up a video mode menu on kernel startup. (Try
  5.4275 +  "man bootparam" or see the documentation of your boot loader about
  5.4276 +  how to pass options to the kernel.)
  5.4277 +
  5.4278 +  Read the file <file:Documentation/svga.txt> for more information
  5.4279 +  about the Video mode selection support. If unsure, say N.
  5.4280 +
  5.4281 +Support for frame buffer devices
  5.4282 +CONFIG_FB
  5.4283 +  The frame buffer device provides an abstraction for the graphics
  5.4284 +  hardware. It represents the frame buffer of some video hardware and
  5.4285 +  allows application software to access the graphics hardware through
  5.4286 +  a well-defined interface, so the software doesn't need to know
  5.4287 +  anything about the low-level (hardware register) stuff.
  5.4288 +
  5.4289 +  Frame buffer devices work identically across the different
  5.4290 +  architectures supported by Linux and make the implementation of
  5.4291 +  application programs easier and more portable; at this point, an X
  5.4292 +  server exists which uses the frame buffer device exclusively.
  5.4293 +  On several non-X86 architectures, the frame buffer device is the
  5.4294 +  only way to use the graphics hardware.
  5.4295 +
  5.4296 +  The device is accessed through special device nodes, usually located
  5.4297 +  in the /dev directory, i.e. /dev/fb*.
  5.4298 +
  5.4299 +  You need an utility program called fbset to make full use of frame
  5.4300 +  buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
  5.4301 +  and the Framebuffer-HOWTO at
  5.4302 +  <http://www.tahallah.demon.co.uk/programming/prog.html> for more
  5.4303 +  information.
  5.4304 +
  5.4305 +  Say Y here and to the driver for your graphics board below if you
  5.4306 +  are compiling a kernel for a non-x86 architecture.
  5.4307 +
  5.4308 +  If you are compiling for the x86 architecture, you can say Y if you
  5.4309 +  want to play with it, but it is not essential. Please note that
  5.4310 +  running graphical applications that directly touch the hardware
  5.4311 +  (e.g. an accelerated X server) and that are not frame buffer
  5.4312 +  device-aware may cause unexpected results. If unsure, say N.
  5.4313 +
  5.4314 +Acorn VIDC support
  5.4315 +CONFIG_FB_ACORN
  5.4316 +  This is the frame buffer device driver for the Acorn VIDC graphics
  5.4317 +  hardware found in Acorn RISC PCs and other ARM-based machines.  If
  5.4318 +  unsure, say N.
  5.4319 +
  5.4320 +Permedia2 support
  5.4321 +CONFIG_FB_PM2
  5.4322 +  This is the frame buffer device driver for the Permedia2 AGP frame
  5.4323 +  buffer card from ASK, aka `Graphic Blaster Exxtreme'.  There is a
  5.4324 +  product page at
  5.4325 +  <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
  5.4326 +
  5.4327 +Enable FIFO disconnect feature
  5.4328 +CONFIG_FB_PM2_FIFO_DISCONNECT
  5.4329 +  Support the Permedia2 FIFOI disconnect feature (see CONFIG_FB_PM2).
  5.4330 +
  5.4331 +Generic Permedia2 PCI board support
  5.4332 +CONFIG_FB_PM2_PCI
  5.4333 +  Say Y to enable support for Permedia2 AGP frame buffer card from
  5.4334 +  3Dlabs (aka `Graphic Blaster Exxtreme') on the PCI bus.
  5.4335 +
  5.4336 +Phase5 CVisionPPC/BVisionPPC support
  5.4337 +CONFIG_FB_PM2_CVPPC
  5.4338 +  Say Y to enable support for the Amiga Phase 5 CVisionPPC BVisionPPC
  5.4339 +  framebuffer cards.  Phase 5 is no longer with us, alas.
  5.4340 +
  5.4341 +Amiga native chipset support
  5.4342 +CONFIG_FB_AMIGA
  5.4343 +  This is the frame buffer device driver for the builtin graphics
  5.4344 +  chipset found in Amigas.
  5.4345 +
  5.4346 +  The driver is also available as a module ( = code which can be
  5.4347 +  inserted and removed from the running kernel whenever you want). The
  5.4348 +  module will be called amifb.o. If you want to compile it as a
  5.4349 +  module, say M here and read <file:Documentation/modules.txt>.
  5.4350 +
  5.4351 +Amiga OCS chipset support
  5.4352 +CONFIG_FB_AMIGA_OCS
  5.4353 +  This enables support for the original Agnus and Denise video chips,
  5.4354 +  found in the Amiga 1000 and most A500's and A2000's. If you intend
  5.4355 +  to run Linux on any of these systems, say Y; otherwise say N.
  5.4356 +
  5.4357 +Amiga ECS chipset support
  5.4358 +CONFIG_FB_AMIGA_ECS
  5.4359 +  This enables support for the Enhanced Chip Set, found in later
  5.4360 +  A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
  5.4361 +  you intend to run Linux on any of these systems, say Y; otherwise
  5.4362 +  say N.
  5.4363 +
  5.4364 +Amiga AGA chipset support
  5.4365 +CONFIG_FB_AMIGA_AGA
  5.4366 +  This enables support for the Advanced Graphics Architecture (also
  5.4367 +  known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
  5.4368 +  and CD32. If you intend to run Linux on any of these systems, say Y;
  5.4369 +  otherwise say N.
  5.4370 +
  5.4371 +Amiga CyberVision support
  5.4372 +CONFIG_FB_CYBER
  5.4373 +  This enables support for the Cybervision 64 graphics card from
  5.4374 +  Phase5. Please note that its use is not all that intuitive (i.e. if
  5.4375 +  you have any questions, be sure to ask!). Say N unless you have a
  5.4376 +  Cybervision 64 or plan to get one before you next recompile the
  5.4377 +  kernel. Please note that this driver DOES NOT support the
  5.4378 +  Cybervision 64 3D card, as they use incompatible video chips.
  5.4379 +
  5.4380 +CyberPro 20x0 support
  5.4381 +CONFIG_FB_CYBER2000
  5.4382 +  This enables support for the Integraphics CyberPro 20x0 and 5000
  5.4383 +  VGA chips used in the Rebel.com Netwinder and other machines.
  5.4384 +  Say Y if you have a NetWinder or a graphics card containing this
  5.4385 +  device, otherwise say N.
  5.4386 +
  5.4387 +Amiga CyberVision3D support
  5.4388 +CONFIG_FB_VIRGE
  5.4389 +  This enables support for the Cybervision 64/3D graphics card from
  5.4390 +  Phase5. Please note that its use is not all that intuitive (i.e. if
  5.4391 +  you have any questions, be sure to ask!). Say N unless you have a
  5.4392 +  Cybervision 64/3D or plan to get one before you next recompile the
  5.4393 +  kernel. Please note that this driver DOES NOT support the older
  5.4394 +  Cybervision 64 card, as they use incompatible video chips.
  5.4395 +
  5.4396 +Amiga RetinaZ3 support
  5.4397 +CONFIG_FB_RETINAZ3
  5.4398 +  This enables support for the Retina Z3 graphics card. Say N unless
  5.4399 +  you have a Retina Z3 or plan to get one before you next recompile
  5.4400 +  the kernel.
  5.4401 +
  5.4402 +Cirrus Logic generic driver
  5.4403 +CONFIG_FB_CLGEN
  5.4404 +  This enables support for Cirrus Logic GD542x/543x based boards on
  5.4405 +  Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
  5.4406 +
  5.4407 +  If you have a PCI-based system, this enables support for these
  5.4408 +  chips: GD-543x, GD-544x, GD-5480.
  5.4409 +
  5.4410 +  Please read the file <file:Documentation/fb/clgenfb.txt>.
  5.4411 +
  5.4412 +  Say N unless you have such a graphics board or plan to get one
  5.4413 +  before you next recompile the kernel.
  5.4414 +
  5.4415 +Apollo support
  5.4416 +CONFIG_APOLLO
  5.4417 +  Say Y here if you want to run Linux on an MC680x0-based Apollo
  5.4418 +  Domain workstation such as the DN3500.
  5.4419 +
  5.4420 +Apollo 3c505 "EtherLink Plus" support
  5.4421 +CONFIG_APOLLO_ELPLUS
  5.4422 +  Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
  5.4423 +  If you don't have one made for Apollos, you can use one from a PC,
  5.4424 +  except that your Apollo won't be able to boot from it (because the
  5.4425 +  code in the ROM will be for a PC).
  5.4426 +
  5.4427 +Atari native chipset support
  5.4428 +CONFIG_FB_ATARI
  5.4429 +  This is the frame buffer device driver for the builtin graphics
  5.4430 +  chipset found in Ataris.
  5.4431 +
  5.4432 +Amiga FrameMaster II/Rainbow II support
  5.4433 +CONFIG_FB_FM2
  5.4434 +  This is the frame buffer device driver for the Amiga FrameMaster
  5.4435 +  card from BSC (exhibited 1992 but not shipped as a CBM product).
  5.4436 +
  5.4437 +Open Firmware frame buffer device support
  5.4438 +CONFIG_FB_OF
  5.4439 +  Say Y if you want support with Open Firmware for your graphics
  5.4440 +  board.
  5.4441 +
  5.4442 +S3 Trio frame buffer device support
  5.4443 +CONFIG_FB_S3TRIO
  5.4444 +  If you have a S3 Trio say Y. Say N for S3 Virge.
  5.4445 +
  5.4446 +3Dfx Banshee/Voodoo3 display support
  5.4447 +CONFIG_FB_3DFX
  5.4448 +  This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
  5.4449 +  chips. Say Y if you have such a graphics board.
  5.4450 +
  5.4451 +  The driver is also available as a module ( = code which can be
  5.4452 +  inserted and removed from the running kernel whenever you want). The
  5.4453 +  module will be called tdfxfb.o. If you want to compile it as a
  5.4454 +  module, say M here and read <file:Documentation/modules.txt>.
  5.4455 +
  5.4456 +nVidia Riva support
  5.4457 +CONFIG_FB_RIVA
  5.4458 +  This driver supports graphics boards with the nVidia Riva/Geforce
  5.4459 +  chips.
  5.4460 +  Say Y if you have such a graphics board.
  5.4461 +
  5.4462 +  The driver is also available as a module ( = code which can be
  5.4463 +  inserted and removed from the running kernel whenever you want). The
  5.4464 +  module will be called rivafb.o. If you want to compile it as a
  5.4465 +  module, say M here and read <file:Documentation/modules.txt>.
  5.4466 +
  5.4467 +Trident Blade/Image support
  5.4468 +CONFIG_FB_TRIDENT
  5.4469 +  This driver is supposed to support graphics boards with the
  5.4470 +  Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
  5.4471 +  but also on some motherboards.Read <file:Documentation/fb/tridentfb.txt>
  5.4472 +
  5.4473 +  Say Y if you have such a graphics board.
  5.4474 +
  5.4475 +  The driver is also available as a module ( = code which can be
  5.4476 +  inserted and removed from the running kernel whenever you want). The
  5.4477 +  module will be called tridentfb.o. If you want to compile it as a
  5.4478 +  module, say M here and read <file:Documentation/modules.txt>.
  5.4479 +
  5.4480 +ATI Mach64 display support
  5.4481 +CONFIG_FB_ATY
  5.4482 +  This driver supports graphics boards with the ATI Mach64 chips.
  5.4483 +  Say Y if you have such a graphics board.
  5.4484 +
  5.4485 +  The driver is also available as a module ( = code which can be
  5.4486 +  inserted and removed from the running kernel whenever you want). The
  5.4487 +  module will be called atyfb.o. If you want to compile it as a
  5.4488 +  module, say M here and read <file:Documentation/modules.txt>.
  5.4489 +
  5.4490 +ATI Rage128 display support
  5.4491 +CONFIG_FB_ATY128
  5.4492 +  This driver supports graphics boards with the ATI Rage128 chips.
  5.4493 +  Say Y if you have such a graphics board and read
  5.4494 +  <file:Documentation/fb/aty128fb.txt>.
  5.4495 +
  5.4496 +  The driver is also available as a module ( = code which can be
  5.4497 +  inserted and removed from the running kernel whenever you want). The
  5.4498 +  module will be called aty128fb.o. If you want to compile it as a
  5.4499 +  module, say M here and read <file:Documentation/modules.txt>.
  5.4500 +
  5.4501 +Maxine (Personal DECstation) onboard framebuffer support
  5.4502 +CONFIG_FB_MAXINE
  5.4503 +  Say Y here to directly support the on-board framebuffer in the
  5.4504 +  Maxine (5000/20, /25, /33) version of the DECstation.  There is a
  5.4505 +  page dedicated to Linux on DECstations at <http://decstation.unix-ag.org/>.
  5.4506 +
  5.4507 +PMAG-BA TURBOchannel framebuffer support
  5.4508 +CONFIG_FB_PMAG_BA
  5.4509 +  Say Y here to directly support the on-board PMAG-BA framebuffer in
  5.4510 +  the 5000/1xx versions of the DECstation.  There is a page dedicated
  5.4511 +  to Linux on DECstations at <http://decstation.unix-ag.org/>.
  5.4512 +
  5.4513 +PMAGB-B TURBOchannel framebuffer support
  5.4514 +CONFIG_FB_PMAGB_B
  5.4515 +  Say Y here to directly support the on-board PMAGB-B framebuffer in
  5.4516 +  the 5000/1xx versions of the DECstation.  There is a page dedicated
  5.4517 +  to Linux on DECstations at <http://decstation.unix-ag.org/>.
  5.4518 +
  5.4519 +FutureTV PCI card
  5.4520 +CONFIG_ARCH_FTVPCI
  5.4521 +  Say Y here if you intend to run this kernel on a FutureTV (nee Nexus
  5.4522 +  Electronics) StrongARM PCI card.
  5.4523 +
  5.4524 +ANAKIN Vehicle Telematics Platform
  5.4525 +CONFIG_ARCH_ANAKIN
  5.4526 +  The Anakin is a StrongArm based SA110 - 2 DIN Vehicle Telematics Platform.
  5.4527 +  64MB SDRAM - 4 Mb Flash - Compact Flash Interface - 1 MB VRAM
  5.4528 +
  5.4529 +  On board peripherals:
  5.4530 +        * Front display: 400x234 16 bit TFT touchscreen
  5.4531 +        * External independent second screen interface
  5.4532 +        * CAN controller SJA1000
  5.4533 +        * USB host controller
  5.4534 +        * 6 channel video codec with hardware overlay
  5.4535 +        * Smartcard reader
  5.4536 +        * IrDa
  5.4537 +
  5.4538 +  Modules interfaced over the Multi Media Extension slots:
  5.4539 +        * A communication card
  5.4540 +                Wavecom GPRS modem
  5.4541 +                uBlock GPS
  5.4542 +                Bosch DAB module
  5.4543 +        * An audio card ( 4 * 40W, AC97 Codec, I2S)
  5.4544 +
  5.4545 +Altera Excalibur XA10 Dev Board
  5.4546 +ARCH_CAMELOT
  5.4547 +  This enables support for Altera's Excalibur XA10 development board.
  5.4548 +  If you would like to build your kernel to run on one of these boards
  5.4549 +  then you must say 'Y' here. Otherwise say 'N'
  5.4550 +
  5.4551 +Link-Up Systems LCD support
  5.4552 +CONFIG_FB_L7200
  5.4553 +  This driver supports the L7200 Color LCD.
  5.4554 +  Say Y if you want graphics support.
  5.4555 +
  5.4556 +NeoMagic display support (EXPERIMENTAL)
  5.4557 +CONFIG_FB_NEOMAGIC
  5.4558 +  This driver supports notebooks with NeoMagic PCI chips.
  5.4559 +  Say Y if you have such a graphics card. 
  5.4560 +
  5.4561 +  The driver is also available as a module ( = code which can be
  5.4562 +  inserted and removed from the running kernel whenever you want). The
  5.4563 +  module will be called neofb.o. If you want to compile it as a
  5.4564 +  module, say M here and read Documentation/modules.txt.
  5.4565 +
  5.4566 +PowerMac "control" frame buffer device support
  5.4567 +CONFIG_FB_CONTROL
  5.4568 +  This driver supports a frame buffer for the graphics adapter in the
  5.4569 +  Power Macintosh 7300 and others.
  5.4570 +
  5.4571 +PowerMac "platinum" frame buffer device support
  5.4572 +CONFIG_FB_PLATINUM
  5.4573 +  This driver supports a frame buffer for the "platinum" graphics
  5.4574 +  adapter in some Power Macintoshes.
  5.4575 +
  5.4576 +PowerMac "valkyrie" frame buffer device support
  5.4577 +CONFIG_FB_VALKYRIE
  5.4578 +  This driver supports a frame buffer for the "valkyrie" graphics
  5.4579 +  adapter in some Power Macintoshes.
  5.4580 +
  5.4581 +Chips 65550 display support
  5.4582 +CONFIG_FB_CT65550
  5.4583 +  This is the frame buffer device driver for the Chips & Technologies
  5.4584 +  65550 graphics chip in PowerBooks.
  5.4585 +
  5.4586 +TGA frame buffer support
  5.4587 +CONFIG_FB_TGA
  5.4588 +  This is the frame buffer device driver for generic TGA graphic
  5.4589 +  cards. Say Y if you have one of those.
  5.4590 +
  5.4591 +VESA VGA graphics console
  5.4592 +CONFIG_FB_VESA
  5.4593 +  This is the frame buffer device driver for generic VESA 2.0
  5.4594 +  compliant graphic cards. The older VESA 1.2 cards are not supported.
  5.4595 +  You will get a boot time penguin logo at no additional cost. Please
  5.4596 +  read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
  5.4597 +
  5.4598 +VGA 16-color planar support
  5.4599 +CONFIG_FBCON_VGA_PLANES
  5.4600 +  This low level frame buffer console driver enable the kernel to use
  5.4601 +  the 16-color planar modes of the old VGA cards where the bits of
  5.4602 +  each pixel are separated into 4 planes.
  5.4603 +
  5.4604 +  Only answer Y here if you have a (very old) VGA card that isn't VESA
  5.4605 +  2 compatible.
  5.4606 +
  5.4607 +VGA 16-color graphics console
  5.4608 +CONFIG_FB_VGA16
  5.4609 +  This is the frame buffer device driver for VGA 16 color graphic
  5.4610 +  cards. Say Y if you have such a card.
  5.4611 +
  5.4612 +  This code is also available as a module. If you want to compile it
  5.4613 +  as a module ( = code which can be inserted in and removed from the
  5.4614 +  running kernel whenever you want), say M here and read
  5.4615 +  <file:Documentation/modules.txt>.  The module will be called
  5.4616 +  vga16fb.o.
  5.4617 +
  5.4618 +Generic STI frame buffer device support
  5.4619 +CONFIG_FB_STI
  5.4620 +  STI refers to the HP "Standard Text Interface" which is a set of
  5.4621 +  BIOS routines contained in a ROM chip in HP PA-RISC based machines.
  5.4622 +  Enabling this option will implement the linux framebuffer device and
  5.4623 +  an fbcon color text console using calls to the STI BIOS routines.
  5.4624 +  The HP framebuffer device is sometimes planar, using a strange memory
  5.4625 +  layout, and changing the plane mask to create colored pixels
  5.4626 +  can require a call to the STI routines, so /dev/fb may not actually 
  5.4627 +  be useful.  However, on some systems packed pixel formats are supported.  
  5.4628 +  It is sufficient for basic text console functions, including fonts.
  5.4629 +
  5.4630 +  You should probably enable this option, unless you are having
  5.4631 +  trouble getting video when booting the kernel (make sure it isn't
  5.4632 +  just that you are running the console on the serial port, though).
  5.4633 +  Really old HP boxes may not have STI, and must use the PDC BIOS
  5.4634 +  console or the IODC BIOS.
  5.4635 +
  5.4636 +Select other compiled-in fonts
  5.4637 +CONFIG_FBCON_FONTS
  5.4638 +  Say Y here if you would like to use fonts other than the default
  5.4639 +  your frame buffer console usually use.
  5.4640 +
  5.4641 +  Note that the answer to this question won't directly affect the
  5.4642 +  kernel: saying N will just cause the configurator to skip all
  5.4643 +  the questions about foreign fonts.
  5.4644 +
  5.4645 +  If unsure, say N (the default choices are safe).
  5.4646 +
  5.4647 +VGA 8x16 font
  5.4648 +CONFIG_FONT_8x16
  5.4649 +  This is the "high resolution" font for the VGA frame buffer (the one
  5.4650 +  provided by the VGA text console 80x25 mode.
  5.4651 +
  5.4652 +  If unsure, say Y.
  5.4653 +
  5.4654 +Support only 8 pixels wide fonts
  5.4655 +CONFIG_FBCON_FONTWIDTH8_ONLY
  5.4656 +  Answer Y here will make the kernel provide only the 8x8 fonts (these
  5.4657 +  are the less readable).
  5.4658 +
  5.4659 +  If unsure, say N.
  5.4660 +
  5.4661 +Sparc console 8x16 font
  5.4662 +CONFIG_FONT_SUN8x16
  5.4663 +  This is the high resolution console font for Sun machines. Say Y.
  5.4664 +
  5.4665 +Sparc console 12x22 font (not supported by all drivers)
  5.4666 +CONFIG_FONT_SUN12x22
  5.4667 +  This is the high resolution console font for Sun machines with very
  5.4668 +  big letters (like the letters used in the SPARC PROM). If the
  5.4669 +  standard font is unreadable for you, say Y, otherwise say N.
  5.4670 +
  5.4671 +VGA 8x8 font
  5.4672 +CONFIG_FONT_8x8
  5.4673 +  This is the "high resolution" font for the VGA frame buffer (the one
  5.4674 +  provided by the text console 80x50 (and higher) modes).
  5.4675 +
  5.4676 +  Note that this is a poor quality font. The VGA 8x16 font is quite a
  5.4677 +  lot more readable.
  5.4678 +
  5.4679 +  Given the resolution provided by the frame buffer device, answer N
  5.4680 +  here is safe.
  5.4681 +
  5.4682 +Mac console 6x11 font (not supported by all drivers)
  5.4683 +CONFIG_FONT_6x11
  5.4684 +  Small console font with Macintosh-style high-half glyphs.  Some Mac
  5.4685 +  framebuffer drivers don't support this one at all.
  5.4686 +
  5.4687 +Pearl (old m68k) console 8x8 font
  5.4688 +CONFIG_FONT_PEARL_8x8
  5.4689 +  Small console font with PC-style control-character and high-half
  5.4690 +  glyphs.
  5.4691 +
  5.4692 +Acorn console 8x8 font
  5.4693 +CONFIG_FONT_ACORN_8x8
  5.4694 +  Small console font with PC-style control characters and high-half
  5.4695 +  glyphs.
  5.4696 +
  5.4697 +Backward compatibility mode for Xpmac
  5.4698 +CONFIG_FB_COMPAT_XPMAC
  5.4699 +  If you use the Xpmac X server (common with mklinux), you'll need to
  5.4700 +  say Y here to use X. You should consider changing to XFree86 which
  5.4701 +  includes a server that supports the frame buffer device directly
  5.4702 +  (XF68_FBDev).
  5.4703 +
  5.4704 +Hercules (HGA) mono graphics support
  5.4705 +CONFIG_FB_HGA
  5.4706 +  Say Y here if you have a Hercules mono graphics card.
  5.4707 +
  5.4708 +  This driver is also available as a module ( = code which can be
  5.4709 +  inserted and removed from the running kernel whenever you want).
  5.4710 +  The module will be called hgafb.o. If you want to compile it as
  5.4711 +  a module, say M here and read <file:Documentation/modules.txt>.
  5.4712 +
  5.4713 +  As this card technology is 15 years old, most people will answer N
  5.4714 +  here.
  5.4715 +
  5.4716 +Epson 1355 framebuffer support
  5.4717 +CONFIG_FB_E1355
  5.4718 +  Build in support for the SED1355 Epson Research Embedded RAMDAC
  5.4719 +  LCD/CRT Controller (since redesignated as the S1D13505) as a
  5.4720 +  framebuffer.  Product specs at
  5.4721 +  <http://www.erd.epson.com/vdc/html/products.htm>.
  5.4722 +
  5.4723 +Dreamcast Frame Buffer support
  5.4724 +CONFIG_FB_DC
  5.4725 +  Say Y here to enable support for the framebuffer on the Sega
  5.4726 +  Dreamcast.  This driver is also available as a module, dcfb.o.
  5.4727 +
  5.4728 +Register Base Address
  5.4729 +CONFIG_E1355_REG_BASE
  5.4730 +  Epson SED1355/S1D13505 LCD/CRT controller register base address.
  5.4731 +  See the manuals at
  5.4732 +  <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for
  5.4733 +  discussion.
  5.4734 +
  5.4735 +Framebuffer Base Address
  5.4736 +CONFIG_E1355_FB_BASE
  5.4737 +  Epson SED1355/S1D13505 LCD/CRT controller memory base address.  See
  5.4738 +  the manuals at
  5.4739 +  <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for
  5.4740 +  discussion.
  5.4741 +
  5.4742 +NEC PowerVR 2 display support
  5.4743 +CONFIG_FB_PVR2
  5.4744 +  Say Y here if you have a PowerVR 2 card in your box.  If you plan to
  5.4745 +  run linux on your Dreamcast, you will have to say Y here.
  5.4746 +  This driver may or may not work on other PowerVR 2 cards, but is
  5.4747 +  totally untested.  Use at your own risk.  If unsure, say N.
  5.4748 +
  5.4749 +  This driver is also available as a module ( = code which can be
  5.4750 +  inserted and removed from the running kernel whenever you want).
  5.4751 +  The module will be called pvr2fb.o.  If you want to compile it as
  5.4752 +  a module, say M here and read <file:Documentation/modules.txt>.
  5.4753 +
  5.4754 +  You can pass several parameters to the driver at boot time or at
  5.4755 +  module load time.  The parameters look like "video=pvr2:XXX", where
  5.4756 +  the meaning of XXX can be found at the end of the main source file
  5.4757 +  (<file:drivers/video/pvr2fb.c>). Please see the file
  5.4758 +  <file:Documentation/fb/pvr2fb.txt>.
  5.4759 +
  5.4760 +Debug pvr2fb
  5.4761 +CONFIG_FB_PVR2_DEBUG
  5.4762 +  Say Y here if you wish for the pvr2fb driver to print out debugging
  5.4763 +  messages. Most people will want to say N here. If unsure, you will
  5.4764 +  also want to say N.
  5.4765 +
  5.4766 +Matrox unified accelerated driver
  5.4767 +CONFIG_FB_MATROX
  5.4768 +  Say Y here if you have a Matrox Millennium, Millennium II, Mystique,
  5.4769 +  Mystique 220, Productiva G100, Mystique G200, Millennium G200,
  5.4770 +  Matrox G400, G450 or G550 card in your box. At this time, support for 
  5.4771 +  the G-series digital output is almost non-existant.
  5.4772 +
  5.4773 +  This driver is also available as a module ( = code which can be
  5.4774 +  inserted and removed from the running kernel whenever you want).
  5.4775 +  The module will be called matroxfb.o. If you want to compile it as
  5.4776 +  a module, say M here and read <file:Documentation/modules.txt>.
  5.4777 +
  5.4778 +  You can pass several parameters to the driver at boot time or at
  5.4779 +  module load time. The parameters look like "video=matrox:XXX", and
  5.4780 +  are described in <file:Documentation/fb/matroxfb.txt>.
  5.4781 +
  5.4782 +Matrox Millennium I/II support
  5.4783 +CONFIG_FB_MATROX_MILLENIUM
  5.4784 +  Say Y here if you have a Matrox Millennium or Matrox Millennium II
  5.4785 +  video card. If you select "Advanced lowlevel driver options" below,
  5.4786 +  you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
  5.4787 +  packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
  5.4788 +  also use font widths different from 8.
  5.4789 +
  5.4790 +Matrox Mystique support
  5.4791 +CONFIG_FB_MATROX_MYSTIQUE
  5.4792 +  Say Y here if you have a Matrox Mystique or Matrox Mystique 220
  5.4793 +  video card. If you select "Advanced lowlevel driver options" below,
  5.4794 +  you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
  5.4795 +  packed pixel and 32 bpp packed pixel. You can also use font widths
  5.4796 +  different from 8.
  5.4797 +
  5.4798 +Matrox G100/G200/G400/G450/G550 support
  5.4799 +CONFIG_FB_MATROX_G100
  5.4800 +  Say Y here if you have a Matrox G100, G200, G400, G450, or G550
  5.4801 +  based video card. If you select "Advanced lowlevel driver options",
  5.4802 +  you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
  5.4803 +  packed pixel and 32 bpp packed pixel. You can also use font widths
  5.4804 +  different from 8.
  5.4805 +
  5.4806 +  If you need support for G400 secondary head, you must first say Y to
  5.4807 +  "I2C support" and "I2C bit-banging support" in the character devices
  5.4808 +  section, and then to "Matrox I2C support" and "G400 second head
  5.4809 +  support" here in the framebuffer section.
  5.4810 +  
  5.4811 +  If you have G550, you must also compile support for G450/G550 secondary
  5.4812 +  head into kernel, otherwise picture will be shown only on the output you
  5.4813 +  are probably not using...
  5.4814 +
  5.4815 +  If you need support for G450 or G550 secondary head, say Y to
  5.4816 +  "Matrox G450/G550 second head support" below.
  5.4817 +
  5.4818 +Matrox I2C support
  5.4819 +CONFIG_FB_MATROX_I2C
  5.4820 +  This drivers creates I2C buses which are needed for accessing the
  5.4821 +  DDC (I2C) bus present on all Matroxes, an I2C bus which
  5.4822 +  interconnects Matrox optional devices, like MGA-TVO on G200 and
  5.4823 +  G400, and the secondary head DDC bus, present on G400 only.
  5.4824 +
  5.4825 +  You can say Y or M here if you want to experiment with monitor
  5.4826 +  detection code. You must say Y or M here if you want to use either
  5.4827 +  second head of G400 or MGA-TVO on G200 or G400.
  5.4828 +
  5.4829 +  If you compile it as module, it will create a module named
  5.4830 +  i2c-matroxfb.o.
  5.4831 +
  5.4832 +Matrox G400 second head support
  5.4833 +CONFIG_FB_MATROX_MAVEN
  5.4834 +  WARNING !!! This support does not work with G450 !!!
  5.4835 +
  5.4836 +  Say Y or M here if you want to use a secondary head (meaning two
  5.4837 +  monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
  5.4838 +  head is not compatible with accelerated XFree 3.3.x SVGA servers -
  5.4839 +  secondary head output is blanked while you are in X. With XFree
  5.4840 +  3.9.17 preview you can use both heads if you use SVGA over fbdev or
  5.4841 +  the fbdev driver on first head and the fbdev driver on second head.
  5.4842 +
  5.4843 +  If you compile it as module, two modules are created,
  5.4844 +  matroxfb_crtc2.o and matroxfb_maven.o. Matroxfb_maven is needed for
  5.4845 +  both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
  5.4846 +  also load i2c-matroxfb to get it to run.
  5.4847 +
  5.4848 +  The driver starts in monitor mode and you must use the matroxset
  5.4849 +  tool (available at
  5.4850 +  <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
  5.4851 +  PAL or NTSC or to swap primary and secondary head outputs.
  5.4852 +  Secondary head driver also always start in 640x480 resolution, you
  5.4853 +  must use fbset to change it.
  5.4854 +
  5.4855 +  Also do not forget that second head supports only 16 and 32 bpp
  5.4856 +  packed pixels, so it is a good idea to compile them into the kernel
  5.4857 +  too.  You can use only some font widths, as the driver uses generic
  5.4858 +  painting procedures (the secondary head does not use acceleration
  5.4859 +  engine).
  5.4860 +
  5.4861 +Matrox G450 second head support
  5.4862 +CONFIG_FB_MATROX_G450
  5.4863 +  Say Y or M here if you want to use a secondary head (meaning two
  5.4864 +  monitors in parallel) on G450, or if you are using analog output
  5.4865 +  of G550.
  5.4866 +
  5.4867 +  If you compile it as module, two modules are created,
  5.4868 +  matroxfb_crtc2.o and matroxfb_g450.o. Both modules are needed if you
  5.4869 +  want two independent display devices.
  5.4870 +
  5.4871 +  The driver starts in monitor mode and currently does not support
  5.4872 +  output in TV modes.  You must use the matroxset tool (available
  5.4873 +  at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to swap
  5.4874 +  primary and secondary head outputs.  Secondary head driver always
  5.4875 +  start in 640x480 resolution and you must use fbset to change it.
  5.4876 +
  5.4877 +  Note on most G550 cards the analog output is the secondary head,
  5.4878 +  so you will need to say Y here to use it.
  5.4879 +
  5.4880 +  Also do not forget that second head supports only 16 and 32 bpp
  5.4881 +  packed pixels, so it is a good idea to compile them into the kernel
  5.4882 +  too. You can use only some font widths, as the driver uses generic
  5.4883 +  painting procedures (the secondary head does not use acceleration
  5.4884 +  engine).
  5.4885 +
  5.4886 +Matrox unified driver multihead support
  5.4887 +CONFIG_FB_MATROX_MULTIHEAD
  5.4888 +  Say Y here if you have more than one (supported) Matrox device in
  5.4889 +  your computer and you want to use all of them for different monitors
  5.4890 +  ("multihead"). If you have only one device, you should say N because
  5.4891 +  the driver compiled with Y is larger and a bit slower, especially on
  5.4892 +  ia32 (ix86).
  5.4893 +
  5.4894 +  If you said M to "Matrox unified accelerated driver" and N here, you
  5.4895 +  will still be able to use several Matrox devices simultaneously:
  5.4896 +  insert several instances of the module matroxfb.o into the kernel
  5.4897 +  with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
  5.4898 +  for the different Matrox devices. This method is slightly faster but
  5.4899 +  uses 40 KB of kernel memory per Matrox card.
  5.4900 +
  5.4901 +  There is no need for enabling 'Matrox multihead support' if you have
  5.4902 +  only one Matrox card in the box.
  5.4903 +
  5.4904 +3Dfx Voodoo Graphics / Voodoo2 frame buffer support
  5.4905 +CONFIG_FB_VOODOO1
  5.4906 +  Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or 
  5.4907 +  Voodoo2 (cvg) based graphics card.
  5.4908 +
  5.4909 +  This driver is also available as a module ( = code which can be 
  5.4910 +  inserted and removed from the running kernel whenever you want).
  5.4911 +  The module will be called sstfb.o. If you want to compile it as
  5.4912 +  a module, say M here and read Documentation/modules.txt.
  5.4913 +
  5.4914 +  WARNING: Do not use any application that uses the 3D engine
  5.4915 +  (namely glide) while using this driver.
  5.4916 +  Please read the file Documentation/fb/README-sstfb.txt for supported
  5.4917 +  options and other important info  support.
  5.4918 +
  5.4919 +MDA text console (dual-headed)
  5.4920 +CONFIG_MDA_CONSOLE
  5.4921 +  Say Y here if you have an old MDA or monochrome Hercules graphics
  5.4922 +  adapter in your system acting as a second head ( = video card). You
  5.4923 +  will then be able to use two monitors with your Linux system. Do not
  5.4924 +  say Y here if your MDA card is the primary card in your system; the
  5.4925 +  normal VGA driver will handle it.
  5.4926 +
  5.4927 +  This driver is also available as a module ( = code which can be
  5.4928 +  inserted and removed from the running kernel whenever you want).
  5.4929 +  The module will be called mdacon.o. If you want to compile it as
  5.4930 +  a module, say M here and read <file:Documentation/modules.txt>.
  5.4931 +
  5.4932 +  If unsure, say N.
  5.4933 +
  5.4934 +SBUS and UPA framebuffers
  5.4935 +CONFIG_FB_SBUS
  5.4936 +  Say Y if you want support for SBUS or UPA based frame buffer device.
  5.4937 +
  5.4938 +Creator/Creator3D support
  5.4939 +CONFIG_FB_CREATOR
  5.4940 +  This is the frame buffer device driver for the Creator and Creator3D
  5.4941 +  graphics boards.
  5.4942 +
  5.4943 +CGsix (GX,TurboGX) support
  5.4944 +CONFIG_FB_CGSIX
  5.4945 +  This is the frame buffer device driver for the CGsix (GX, TurboGX)
  5.4946 +  frame buffer.
  5.4947 +
  5.4948 +BWtwo support
  5.4949 +CONFIG_FB_BWTWO
  5.4950 +  This is the frame buffer device driver for the BWtwo frame buffer.
  5.4951 +
  5.4952 +CGthree support
  5.4953 +CONFIG_FB_CGTHREE
  5.4954 +  This is the frame buffer device driver for the CGthree frame buffer.
  5.4955 +
  5.4956 +CGfourteen (SX) support
  5.4957 +CONFIG_FB_CGFOURTEEN
  5.4958 +  This is the frame buffer device driver for the CGfourteen frame
  5.4959 +  buffer on Desktop SPARCsystems with the SX graphics option.
  5.4960 +
  5.4961 +P9100 (Sparcbook 3 only) support
  5.4962 +CONFIG_FB_P9100
  5.4963 +  This is the frame buffer device driver for the P9100 card
  5.4964 +  supported on Sparcbook 3 machines.
  5.4965 +
  5.4966 +Leo (ZX) support
  5.4967 +CONFIG_FB_LEO
  5.4968 +  This is the frame buffer device driver for the SBUS-based Sun ZX
  5.4969 +  (leo) frame buffer cards.
  5.4970 +
  5.4971 +IGA 168x display support
  5.4972 +CONFIG_FB_IGA
  5.4973 +  This is the framebuffer device for the INTERGRAPHICS 1680 and
  5.4974 +  successor frame buffer cards.
  5.4975 +
  5.4976 +TCX (SS4/SS5 only) support
  5.4977 +CONFIG_FB_TCX
  5.4978 +  This is the frame buffer device driver for the TCX 24/8bit frame
  5.4979 +  buffer.
  5.4980 +
  5.4981 +HD64461 Frame Buffer support
  5.4982 +CONFIG_FB_HIT
  5.4983 +  This is the frame buffer device driver for the Hitachi HD64461 LCD
  5.4984 +  frame buffer card.
  5.4985 +
  5.4986 +SIS acceleration
  5.4987 +CONFIG_FB_SIS
  5.4988 +  This is the frame buffer device driver for the SiS 630 and 640 Super
  5.4989 +  Socket 7 UMA cards.  Specs available at <http://www.sis.com.tw/>.
  5.4990 +
  5.4991 +SIS 630/540/730 support
  5.4992 +CONFIG_FB_SIS_300
  5.4993 +  This is the frame buffer device driver for the SiS 630 and related
  5.4994 +  Super Socket 7 UMA cards.  Specs available at
  5.4995 +  <http://www.sis.com.tw/>.
  5.4996 +
  5.4997 +SIS 315H/315 support
  5.4998 +CONFIG_FB_SIS_315
  5.4999 +  This is the frame buffer device driver for the SiS 315 graphics
  5.5000 +  card.  Specs available at <http://www.sis.com.tw/>.
  5.5001 +
  5.5002 +IMS Twin Turbo display support
  5.5003 +CONFIG_FB_IMSTT
  5.5004 +  The IMS Twin Turbo is a PCI-based frame buffer card bundled with
  5.5005 +  many Macintosh and compatible computers.
  5.5006 +
  5.5007 +CONFIG_FB_TX3912
  5.5008 +  The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core;
  5.5009 +  see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
  5.5010 +
  5.5011 +  Say Y here to enable kernel support for the on-board framebuffer.
  5.5012 +
  5.5013 +Virtual Frame Buffer support (ONLY FOR TESTING!)
  5.5014 +CONFIG_FB_VIRTUAL
  5.5015 +  This is a `virtual' frame buffer device. It operates on a chunk of
  5.5016 +  unswappable kernel memory instead of on the memory of a graphics
  5.5017 +  board. This means you cannot see any output sent to this frame
  5.5018 +  buffer device, while it does consume precious memory. The main use
  5.5019 +  of this frame buffer device is testing and debugging the frame
  5.5020 +  buffer subsystem. Do NOT enable it for normal systems! To protect
  5.5021 +  the innocent, it has to be enabled explicitly at boot time using the
  5.5022 +  kernel option `video=vfb:'.
  5.5023 +
  5.5024 +  This driver is also available as a module ( = code which can be
  5.5025 +  inserted and removed from the running kernel whenever you want). The
  5.5026 +  module will be called vfb.o. If you want to compile it as a module,
  5.5027 +  say M here and read <file:Documentation/modules.txt>.
  5.5028 +
  5.5029 +  If unsure, say N.
  5.5030 +
  5.5031 +Mach64 CT/VT/GT/LT (incl. 3D RAGE) support
  5.5032 +CONFIG_FB_ATY_CT
  5.5033 +  Say Y here to support use of ATI's 64-bit Rage boards (or other
  5.5034 +  boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
  5.5035 +  framebuffer device.  The ATI product support page for these boards
  5.5036 +  is at <http://support.ati.com/products/pc/mach64/>.
  5.5037 +
  5.5038 +Sony Vaio Picturebook laptop LCD panel support
  5.5039 +CONFIG_FB_ATY_CT_VAIO_LCD
  5.5040 +  Say Y here if you want to use the full width of the Sony Vaio 
  5.5041 +  Picturebook laptops LCD panels (you will get a 128x30 console).
  5.5042 +
  5.5043 +  Note that you need to activate this mode using the 'vga=0x301'
  5.5044 +  option from your boot loader (lilo or loadlin).  See the
  5.5045 +  documentation of your boot loader about how to pass options to the
  5.5046 +  kernel.
  5.5047 +  
  5.5048 +Mach64 GX support
  5.5049 +CONFIG_FB_ATY_GX
  5.5050 +  Say Y here to support use of the ATI Mach64 Graphics Expression
  5.5051 +  board (or other boards based on the Mach64 GX chipset) as a
  5.5052 +  framebuffer device.  The ATI product support page for these boards
  5.5053 +  is at
  5.5054 +  <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
  5.5055 +
  5.5056 +ATI Radeon display support
  5.5057 +CONFIG_FB_RADEON
  5.5058 +  Choose this option if you want to use an ATI Radeon graphics card as
  5.5059 +  a framebuffer device.  There are both PCI and AGP versions.  You
  5.5060 +  don't need to choose this to run the Radeon in plain VGA mode.
  5.5061 +  There is a product page at
  5.5062 +  <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
  5.5063 +
  5.5064 +SA-1100 LCD support
  5.5065 +CONFIG_FB_SA1100
  5.5066 +  This is a framebuffer device for the SA-1100 LCD Controller.
  5.5067 +  See <http://www.linux-fbdev.org/> for information on framebuffer
  5.5068 +  devices.
  5.5069 +
  5.5070 +  If you plan to use the LCD display with your SA-1100 system, say
  5.5071 +  Y here.
  5.5072 +
  5.5073 +Advanced low level driver options
  5.5074 +CONFIG_FBCON_ADVANCED
  5.5075 +  The frame buffer console uses character drawing routines that are
  5.5076 +  tailored to the specific organization of pixels in the memory of
  5.5077 +  your graphics hardware. These are called the low level frame buffer
  5.5078 +  console drivers. Note that they are used for text console output
  5.5079 +  only; they are NOT needed for graphical applications.
  5.5080 +
  5.5081 +  If you say N here, the needed low level drivers are automatically
  5.5082 +  enabled, depending on what frame buffer devices you selected above.
  5.5083 +  This is recommended for most users.
  5.5084 +
  5.5085 +  If you say Y here, you have more fine-grained control over which low
  5.5086 +  level drivers are enabled. You can e.g. leave out low level drivers
  5.5087 +  for color depths you do not intend to use for text consoles.
  5.5088 +
  5.5089 +  Low level frame buffer console drivers can be modules ( = code which
  5.5090 +  can be inserted and removed from the running kernel whenever you
  5.5091 +  want). The modules will be called fbcon-*.o. If you want to compile
  5.5092 +  (some of) them as modules, read <file:Documentation/modules.txt>.
  5.5093 +
  5.5094 +  If unsure, say N.
  5.5095 +
  5.5096 +Monochrome support
  5.5097 +CONFIG_FBCON_MFB
  5.5098 +  This is the low level frame buffer console driver for monochrome
  5.5099 +  (2 colors) packed pixels.
  5.5100 +
  5.5101 +2 bpp packed pixels support
  5.5102 +CONFIG_FBCON_CFB2
  5.5103 +  This is the low level frame buffer console driver for 2 bits per
  5.5104 +  pixel (4 colors) packed pixels.
  5.5105 +
  5.5106 +4 bpp packed pixels support
  5.5107 +CONFIG_FBCON_CFB4
  5.5108 +  This is the low level frame buffer console driver for 4 bits per
  5.5109 +  pixel (16 colors) packed pixels.
  5.5110 +
  5.5111 +8 bpp packed pixels support
  5.5112 +CONFIG_FBCON_CFB8
  5.5113 +  This is the low level frame buffer console driver for 8 bits per
  5.5114 +  pixel (256 colors) packed pixels.
  5.5115 +
  5.5116 +16 bpp packed pixels support
  5.5117 +CONFIG_FBCON_CFB16
  5.5118 +  This is the low level frame buffer console driver for 15 or 16 bits
  5.5119 +  per pixel (32K or 64K colors, also known as `hicolor') packed
  5.5120 +  pixels.
  5.5121 +
  5.5122 +24 bpp packed pixels support
  5.5123 +CONFIG_FBCON_CFB24
  5.5124 +  This is the low level frame buffer console driver for 24 bits per
  5.5125 +  pixel (16M colors, also known as `truecolor') packed pixels. It is
  5.5126 +  NOT for `sparse' 32 bits per pixel mode.
  5.5127 +
  5.5128 +32 bpp packed pixels support
  5.5129 +CONFIG_FBCON_CFB32
  5.5130 +  This is the low level frame buffer console driver for 32 bits per
  5.5131 +  pixel (16M colors, also known as `truecolor') sparse packed pixels.
  5.5132 +
  5.5133 +Amiga bitplanes support
  5.5134 +CONFIG_FBCON_AFB
  5.5135 +  This is the low level frame buffer console driver for 1 to 8
  5.5136 +  bitplanes (2 to 256 colors) on Amiga.
  5.5137 +
  5.5138 +Amiga interleaved bitplanes support
  5.5139 +CONFIG_FBCON_ILBM
  5.5140 +  This is the low level frame buffer console driver for 1 to 8
  5.5141 +  interleaved bitplanes (2 to 256 colors) on Amiga.
  5.5142 +
  5.5143 +Atari interleaved bitplanes (2 planes) support
  5.5144 +CONFIG_FBCON_IPLAN2P2
  5.5145 +  This is the low level frame buffer console driver for 2 interleaved
  5.5146 +  bitplanes (4 colors) on Atari.
  5.5147 +
  5.5148 +Atari interleaved bitplanes (4 planes) support
  5.5149 +CONFIG_FBCON_IPLAN2P4
  5.5150 +  This is the low level frame buffer console driver for 4 interleaved
  5.5151 +  bitplanes (16 colors) on Atari.
  5.5152 +
  5.5153 +Atari interleaved bitplanes (8 planes) support
  5.5154 +CONFIG_FBCON_IPLAN2P8
  5.5155 +  This is the low level frame buffer console driver for 8 interleaved
  5.5156 +  bitplanes (256 colors) on Atari.
  5.5157 +
  5.5158 +Mac variable bpp packed pixels support
  5.5159 +CONFIG_FBCON_MAC
  5.5160 +  This is the low level frame buffer console driver for 1/2/4/8/16/32
  5.5161 +  bits per pixel packed pixels on Mac. It supports variable font
  5.5162 +  widths for low resolution screens.
  5.5163 +
  5.5164 +Permedia3 support (EXPERIMENTAL)
  5.5165 +CONFIG_FB_PM3
  5.5166 +  This is the frame buffer device driver for the 3DLabs Permedia3
  5.5167 +  chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
  5.5168 +  similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
  5.5169 +  and maybe other boards.
  5.5170 +
  5.5171 +HGA monochrome support
  5.5172 +CONFIG_FBCON_HGA
  5.5173 +  This is the low level frame buffer console driver for Hercules mono
  5.5174 +  graphics cards.
  5.5175 +
  5.5176 +VGA characters/attributes support
  5.5177 +CONFIG_FBCON_VGA
  5.5178 +  This is the low level frame buffer console driver for VGA text mode;
  5.5179 +  it is used by frame buffer device drivers that support VGA text
  5.5180 +  mode.
  5.5181 +
  5.5182 +Parallel-port support
  5.5183 +CONFIG_PARPORT
  5.5184 +  If you want to use devices connected to your machine's parallel port
  5.5185 +  (the connector at the computer with 25 holes), e.g. printer, ZIP
  5.5186 +  drive, PLIP link (Parallel Line Internet Protocol is mainly used to
  5.5187 +  create a mini network by connecting the parallel ports of two local
  5.5188 +  machines) etc., then you need to say Y here; please read
  5.5189 +  <file:Documentation/parport.txt> and
  5.5190 +  <file:drivers/parport/BUGS-parport>.
  5.5191 +
  5.5192 +  For extensive information about drivers for many devices attaching
  5.5193 +  to the parallel port see <http://www.torque.net/linux-pp.html> on
  5.5194 +  the WWW.
  5.5195 +
  5.5196 +  It is possible to share a single parallel port among several devices
  5.5197 +  and it is safe to compile all the corresponding drivers into the
  5.5198 +  kernel.  If you want to compile parallel port support as a module
  5.5199 +  ( = code which can be inserted in and removed from the running
  5.5200 +  kernel whenever you want), say M here and read
  5.5201 +  <file:Documentation/modules.txt>.  The module will be called
  5.5202 +  parport.o.  If you have more than one parallel port and want to
  5.5203 +  specify which port and IRQ to be used by this driver at module load
  5.5204 +  time, take a look at <file:Documentation/parport.txt>.
  5.5205 +
  5.5206 +  If unsure, say Y.
  5.5207 +
  5.5208 +PC-style hardware
  5.5209 +CONFIG_PARPORT_PC
  5.5210 +  You should say Y here if you have a PC-style parallel port. All IBM
  5.5211 +  PC compatible computers and some Alphas have PC-style parallel
  5.5212 +  ports.
  5.5213 +
  5.5214 +  This code is also available as a module.  If you want to compile it
  5.5215 +  as a module ( = code which can be inserted in and removed from the
  5.5216 +  running kernel whenever you want), say M here and read
  5.5217 +  <file:Documentation/modules.txt>.  The module will be called
  5.5218 +  parport_pc.o.
  5.5219 +
  5.5220 +  If unsure, say Y.
  5.5221 +
  5.5222 +Parallel+serial PCI multi-IO card support
  5.5223 +CONFIG_PARPORT_SERIAL
  5.5224 +  This adds support for multi-IO PCI cards that have parallel and
  5.5225 +  serial ports.  You should say Y or M here.  If you say M, the module
  5.5226 +  will be called parport_serial.o.
  5.5227 +
  5.5228 +Use FIFO/DMA if available
  5.5229 +CONFIG_PARPORT_PC_FIFO
  5.5230 +  Many parallel port chipsets provide hardware that can speed up
  5.5231 +  printing. Say Y here if you want to take advantage of that.
  5.5232 +
  5.5233 +  As well as actually having a FIFO, or DMA capability, the kernel
  5.5234 +  will need to know which IRQ the parallel port has.  By default,
  5.5235 +  parallel port interrupts will not be used, and so neither will the
  5.5236 +  FIFO.  See <file:Documentation/parport.txt> to find out how to
  5.5237 +  specify which IRQ/DMA to use.
  5.5238 +
  5.5239 +SuperIO chipset support
  5.5240 +CONFIG_PARPORT_PC_SUPERIO
  5.5241 +  Saying Y here enables some probes for Super-IO chipsets in order to
  5.5242 +  find out things like base addresses, IRQ lines and DMA channels.  It
  5.5243 +  is safe to say N.
  5.5244 +
  5.5245 +Support for PCMCIA management for PC-style ports
  5.5246 +CONFIG_PARPORT_PC_PCMCIA
  5.5247 +  Say Y here if you need PCMCIA support for your PC-style parallel
  5.5248 +  ports. If unsure, say N.
  5.5249 +
  5.5250 +  This driver is also available as a module ( = code which can be
  5.5251 +  inserted in and removed from the running kernel whenever you want).
  5.5252 +  If you want to compile it as a module, say M here and read
  5.5253 +  <file:Documentation/modules.txt>. The module will be called
  5.5254 +  parport_cs.o
  5.5255 +
  5.5256 +Support foreign hardware
  5.5257 +CONFIG_PARPORT_OTHER
  5.5258 +  Say Y here if you want to be able to load driver modules to support
  5.5259 +  other non-standard types of parallel ports. This causes a
  5.5260 +  performance loss, so most people say N.
  5.5261 +
  5.5262 +Amiga built-in parallel port support
  5.5263 +CONFIG_PARPORT_AMIGA
  5.5264 +  Say Y here if you need support for the parallel port hardware on
  5.5265 +  Amiga machines. This code is also available as a module (say M),
  5.5266 +  called parport_amiga.o. If in doubt, saying N is the safe plan.
  5.5267 +
  5.5268 +Atari built-in parallel port support
  5.5269 +CONFIG_PARPORT_ATARI
  5.5270 +  Say Y here if you need support for the parallel port hardware on
  5.5271 +  Atari machines. This code is also available as a module (say M),
  5.5272 +  called parport_atari.o. If in doubt, saying N is the safe plan.
  5.5273 +
  5.5274 +Multiface III parallel port support
  5.5275 +CONFIG_PARPORT_MFC3
  5.5276 +  Say Y here if you need parallel port support for the MFC3 card.
  5.5277 +  This code is also available as a module (say M), called
  5.5278 +  parport_mfc3.o. If in doubt, saying N is the safe plan.
  5.5279 +
  5.5280 +Support IEEE 1284 status readback
  5.5281 +CONFIG_PRINTER_READBACK
  5.5282 +  If you have a device on your parallel port that support this
  5.5283 +  protocol, this option will allow the device to report its status. It
  5.5284 +  is safe to say Y.
  5.5285 +
  5.5286 +IEEE 1284 transfer modes
  5.5287 +CONFIG_PARPORT_1284
  5.5288 +  If you have a printer that supports status readback or device ID, or
  5.5289 +  want to use a device that uses enhanced parallel port transfer modes
  5.5290 +  such as EPP and ECP, say Y here to enable advanced IEEE 1284
  5.5291 +  transfer modes. Also say Y if you want device ID information to
  5.5292 +  appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
  5.5293 +
  5.5294 +Enable loadable module support
  5.5295 +CONFIG_MODULES
  5.5296 +  Kernel modules are small pieces of compiled code which can be
  5.5297 +  inserted in or removed from the running kernel, using the programs
  5.5298 +  insmod and rmmod. This is described in the file
  5.5299 +  <file:Documentation/modules.txt>, including the fact that you have
  5.5300 +  to say "make modules" in order to compile the modules that you chose
  5.5301 +  during kernel configuration.  Modules can be device drivers, file
  5.5302 +  systems, binary executable formats, and so on. If you think that you
  5.5303 +  may want to make use of modules with this kernel in the future, then
  5.5304 +  say Y here.  If unsure, say Y.
  5.5305 +
  5.5306 +Set version information on all symbols for modules
  5.5307 +CONFIG_MODVERSIONS
  5.5308 +  Usually, modules have to be recompiled whenever you switch to a new
  5.5309 +  kernel.  Saying Y here makes it possible, and safe, to use the
  5.5310 +  same modules even after compiling a new kernel; this requires the
  5.5311 +  program modprobe. All the software needed for module support is in
  5.5312 +  the modutils package (check the file <file:Documentation/Changes>
  5.5313 +  for location and latest version).  NOTE: if you say Y here but don't
  5.5314 +  have the program genksyms (which is also contained in the above
  5.5315 +  mentioned modutils package), then the building of your kernel will
  5.5316 +  fail.  If you are going to use modules that are generated from
  5.5317 +  non-kernel sources, you would benefit from this option.  Otherwise
  5.5318 +  it's not that important.  So, N ought to be a safe bet.
  5.5319 +
  5.5320 +Kernel module loader support
  5.5321 +CONFIG_KMOD
  5.5322 +  Normally when you have selected some drivers and/or file systems to
  5.5323 +  be created as loadable modules, you also have the responsibility to
  5.5324 +  load the corresponding modules (using the programs insmod or
  5.5325 +  modprobe) before you can use them. If you say Y here however, the
  5.5326 +  kernel will be able to load modules for itself: when a part of the
  5.5327 +  kernel needs a module, it runs modprobe with the appropriate
  5.5328 +  arguments, thereby loading the module if it is available. (This is a
  5.5329 +  replacement for kerneld.) Say Y here and read about configuring it
  5.5330 +  in <file:Documentation/kmod.txt>.
  5.5331 +
  5.5332 +ARP daemon support
  5.5333 +CONFIG_ARPD
  5.5334 +  Normally, the kernel maintains an internal cache which maps IP
  5.5335 +  addresses to hardware addresses on the local network, so that
  5.5336 +  Ethernet/Token Ring/ etc. frames are sent to the proper address on
  5.5337 +  the physical networking layer. For small networks having a few
  5.5338 +  hundred directly connected hosts or less, keeping this address
  5.5339 +  resolution (ARP) cache inside the kernel works well. However,
  5.5340 +  maintaining an internal ARP cache does not work well for very large
  5.5341 +  switched networks, and will use a lot of kernel memory if TCP/IP
  5.5342 +  connections are made to many machines on the network.
  5.5343 +
  5.5344 +  If you say Y here, the kernel's internal ARP cache will never grow
  5.5345 +  to more than 256 entries (the oldest entries are expired in a LIFO
  5.5346 +  manner) and communication will be attempted with the user space ARP
  5.5347 +  daemon arpd. Arpd then answers the address resolution request either
  5.5348 +  from its own cache or by asking the net.
  5.5349 +
  5.5350 +  This code is experimental and also obsolete. If you want to use it,
  5.5351 +  you need to find a version of the daemon arpd on the net somewhere,
  5.5352 +  and you should also say Y to "Kernel/User network link driver",
  5.5353 +  below. If unsure, say N.
  5.5354 +
  5.5355 +TCP/IP networking
  5.5356 +CONFIG_INET
  5.5357 +  These are the protocols used on the Internet and on most local
  5.5358 +  Ethernets. It is highly recommended to say Y here (this will enlarge
  5.5359 +  your kernel by about 144 KB), since some programs (e.g. the X window
  5.5360 +  system) use TCP/IP even if your machine is not connected to any
  5.5361 +  other computer. You will get the so-called loopback device which
  5.5362 +  allows you to ping yourself (great fun, that!).
  5.5363 +
  5.5364 +  For an excellent introduction to Linux networking, please read the
  5.5365 +  NET-3-HOWTO, available from
  5.5366 +  <http://www.tldp.org/docs.html#howto>.
  5.5367 +
  5.5368 +  This option is also necessary if you want to use the full power of
  5.5369 +  term (term is a program which gives you almost full Internet
  5.5370 +  connectivity if you have a regular dial up shell account on some
  5.5371 +  Internet connected Unix computer; for more information, read
  5.5372 +  <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>).
  5.5373 +
  5.5374 +  If you say Y here and also to "/proc file system support" and
  5.5375 +  "Sysctl support" below, you can change various aspects of the
  5.5376 +  behaviour of the TCP/IP code by writing to the (virtual) files in
  5.5377 +  /proc/sys/net/ipv4/*; the options are explained in the file
  5.5378 +  <file:Documentation/networking/ip-sysctl.txt>.
  5.5379 +
  5.5380 +  Short answer: say Y.
  5.5381 +
  5.5382 +IP multicasting
  5.5383 +CONFIG_IP_MULTICAST
  5.5384 +  This is code for addressing several networked computers at once,
  5.5385 +  enlarging your kernel by about 2 KB. You need multicasting if you
  5.5386 +  intend to participate in the MBONE, a high bandwidth network on top
  5.5387 +  of the Internet which carries audio and video broadcasts. More
  5.5388 +  information about the MBONE is on the WWW at
  5.5389 +  <http://www-itg.lbl.gov/mbone/>. Information about the multicast
  5.5390 +  capabilities of the various network cards is contained in
  5.5391 +  <file:Documentation/networking/multicast.txt>. For most people, it's
  5.5392 +  safe to say N.
  5.5393 +
  5.5394 +Advanced router
  5.5395 +CONFIG_IP_ADVANCED_ROUTER
  5.5396 +  If you intend to run your Linux box mostly as a router, i.e. as a
  5.5397 +  computer that forwards and redistributes network packets, say Y; you
  5.5398 +  will then be presented with several options that allow more precise
  5.5399 +  control about the routing process.
  5.5400 +
  5.5401 +  The answer to this question won't directly affect the kernel:
  5.5402 +  answering N will just cause the configurator to skip all the
  5.5403 +  questions about advanced routing.
  5.5404 +
  5.5405 +  Note that your box can only act as a router if you enable IP
  5.5406 +  forwarding in your kernel; you can do that by saying Y to "/proc
  5.5407 +  file system support" and "Sysctl support" below and executing the
  5.5408 +  line
  5.5409 +
  5.5410 +    echo "1" > /proc/sys/net/ipv4/ip_forward
  5.5411 +
  5.5412 +  at boot time after the /proc file system has been mounted.
  5.5413 +
  5.5414 +  If you turn on IP forwarding, you will also get the rp_filter, which
  5.5415 +  automatically rejects incoming packets if the routing table entry
  5.5416 +  for their source address doesn't match the network interface they're
  5.5417 +  arriving on. This has security advantages because it prevents the
  5.5418 +  so-called IP spoofing, however it can pose problems if you use
  5.5419 +  asymmetric routing (packets from you to a host take a different path
  5.5420 +  than packets from that host to you) or if you operate a non-routing
  5.5421 +  host which has several IP addresses on different interfaces. To turn
  5.5422 +  rp_filter off use:
  5.5423 +
  5.5424 +        echo 0 > /proc/sys/net/ipv4/conf/<device>/rp_filter
  5.5425 +  or
  5.5426 +        echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter
  5.5427 +
  5.5428 +  If unsure, say N here.
  5.5429 +
  5.5430 +Policy routing
  5.5431 +CONFIG_IP_MULTIPLE_TABLES
  5.5432 +  Normally, a router decides what to do with a received packet based
  5.5433 +  solely on the packet's final destination address. If you say Y here,
  5.5434 +  the Linux router will also be able to take the packet's source
  5.5435 +  address into account. Furthermore, if you also say Y to "Use TOS
  5.5436 +  value as routing key" below, the TOS (Type-Of-Service) field of the
  5.5437 +  packet can be used for routing decisions as well. In addition, if
  5.5438 +  you say Y here and to "Fast network address translation" below,
  5.5439 +  the router will also be able to modify source and destination
  5.5440 +  addresses of forwarded packets.
  5.5441 +
  5.5442 +  If you are interested in this, please see the preliminary
  5.5443 +  documentation at <http://www.compendium.com.ar/policy-routing.txt>
  5.5444 +  and <ftp://post.tepkom.ru/pub/vol2/Linux/docs/advanced-routing.tex>.
  5.5445 +  You will need supporting software from
  5.5446 +  <ftp://ftp.inr.ac.ru/ip-routing/>.
  5.5447 +
  5.5448 +  If unsure, say N.
  5.5449 +
  5.5450 +Equal cost multipath
  5.5451 +CONFIG_IP_ROUTE_MULTIPATH
  5.5452 +  Normally, the routing tables specify a single action to be taken in
  5.5453 +  a deterministic manner for a given packet. If you say Y here
  5.5454 +  however, it becomes possible to attach several actions to a packet
  5.5455 +  pattern, in effect specifying several alternative paths to travel
  5.5456 +  for those packets. The router considers all these paths to be of
  5.5457 +  equal "cost" and chooses one of them in a non-deterministic fashion
  5.5458 +  if a matching packet arrives.
  5.5459 +
  5.5460 +Use TOS value as routing key
  5.5461 +CONFIG_IP_ROUTE_TOS
  5.5462 +  The header of every IP packet carries a TOS (Type Of Service) value
  5.5463 +  with which the packet requests a certain treatment, e.g. low
  5.5464 +  latency (for interactive traffic), high throughput, or high
  5.5465 +  reliability.  If you say Y here, you will be able to specify
  5.5466 +  different routes for packets with different TOS values.
  5.5467 +
  5.5468 +Use netfilter MARK value as routing key
  5.5469 +CONFIG_IP_ROUTE_FWMARK
  5.5470 +  If you say Y here, you will be able to specify different routes for
  5.5471 +  packets with different mark values (see iptables(8), MARK target).
  5.5472 +
  5.5473 +Verbose route monitoring
  5.5474 +CONFIG_IP_ROUTE_VERBOSE
  5.5475 +  If you say Y here, which is recommended, then the kernel will print
  5.5476 +  verbose messages regarding the routing, for example warnings about
  5.5477 +  received packets which look strange and could be evidence of an
  5.5478 +  attack or a misconfigured system somewhere. The information is
  5.5479 +  handled by the klogd daemon which is responsible for kernel messages
  5.5480 +  ("man klogd").
  5.5481 +
  5.5482 +Large routing tables
  5.5483 +CONFIG_IP_ROUTE_LARGE_TABLES
  5.5484 +  If you have routing zones that grow to more than about 64 entries,
  5.5485 +  you may want to say Y here to speed up the routing process.
  5.5486 +
  5.5487 +Fast network address translation
  5.5488 +CONFIG_IP_ROUTE_NAT
  5.5489 +  If you say Y here, your router will be able to modify source and
  5.5490 +  destination addresses of packets that pass through it, in a manner
  5.5491 +  you specify.  General information about Network Address Translation
  5.5492 +  can be gotten from the document
  5.5493 +  <http://www.csn.tu-chemnitz.de/~mha/linux-ip-nat/diplom/nat.html>.
  5.5494 +
  5.5495 +Kernel level IP autoconfiguration
  5.5496 +CONFIG_IP_PNP
  5.5497 +  This enables automatic configuration of IP addresses of devices and
  5.5498 +  of the routing table during kernel boot, based on either information
  5.5499 +  supplied on the kernel command line or by BOOTP or RARP protocols.
  5.5500 +  You need to say Y only for diskless machines requiring network
  5.5501 +  access to boot (in which case you want to say Y to "Root file system
  5.5502 +  on NFS" as well), because all other machines configure the network
  5.5503 +  in their startup scripts.
  5.5504 +
  5.5505 +BOOTP support
  5.5506 +CONFIG_IP_PNP_BOOTP
  5.5507 +  If you want your Linux box to mount its whole root file system (the
  5.5508 +  one containing the directory /) from some other computer over the
  5.5509 +  net via NFS and you want the IP address of your computer to be
  5.5510 +  discovered automatically at boot time using the BOOTP protocol (a
  5.5511 +  special protocol designed for doing this job), say Y here. In case
  5.5512 +  the boot ROM of your network card was designed for booting Linux and
  5.5513 +  does BOOTP itself, providing all necessary information on the kernel
  5.5514 +  command line, you can say N here. If unsure, say Y. Note that if you
  5.5515 +  want to use BOOTP, a BOOTP server must be operating on your network.
  5.5516 +  Read <file:Documentation/nfsroot.txt> for details.
  5.5517 +
  5.5518 +DHCP support
  5.5519 +CONFIG_IP_PNP_DHCP
  5.5520 +  If you want your Linux box to mount its whole root file system (the
  5.5521 +  one containing the directory /) from some other computer over the
  5.5522 +  net via NFS and you want the IP address of your computer to be
  5.5523 +  discovered automatically at boot time using the DHCP protocol (a
  5.5524 +  special protocol designed for doing this job), say Y here. In case
  5.5525 +  the boot ROM of your network card was designed for booting Linux and
  5.5526 +  does DHCP itself, providing all necessary information on the kernel
  5.5527 +  command line, you can say N here.
  5.5528 +
  5.5529 +  If unsure, say Y. Note that if you want to use DHCP, a DHCP server
  5.5530 +  must be operating on your network.  Read
  5.5531 +  <file:Documentation/nfsroot.txt> for details.
  5.5532 +
  5.5533 +RARP support
  5.5534 +CONFIG_IP_PNP_RARP
  5.5535 +  If you want your Linux box to mount its whole root file system (the
  5.5536 +  one containing the directory /) from some other computer over the
  5.5537 +  net via NFS and you want the IP address of your computer to be
  5.5538 +  discovered automatically at boot time using the RARP protocol (an
  5.5539 +  older protocol which is being obsoleted by BOOTP and DHCP), say Y
  5.5540 +  here. Note that if you want to use RARP, a RARP server must be
  5.5541 +  operating on your network. Read <file:Documentation/nfsroot.txt> for
  5.5542 +  details.
  5.5543 +
  5.5544 +IP tunneling
  5.5545 +CONFIG_NET_IPIP
  5.5546 +  Tunneling means encapsulating data of one protocol type within
  5.5547 +  another protocol and sending it over a channel that understands the
  5.5548 +  encapsulating protocol. This particular tunneling driver implements
  5.5549 +  encapsulation of IP within IP, which sounds kind of pointless, but
  5.5550 +  can be useful if you want to make your (or some other) machine
  5.5551 +  appear on a different network than it physically is, or to use
  5.5552 +  mobile-IP facilities (allowing laptops to seamlessly move between
  5.5553 +  networks without changing their IP addresses; check out
  5.5554 +  <http://anchor.cs.binghamton.edu/~mobileip/LJ/index.html>).
  5.5555 +
  5.5556 +  Saying Y to this option will produce two modules ( = code which can
  5.5557 +  be inserted in and removed from the running kernel whenever you
  5.5558 +  want). Most people won't need this and can say N.
  5.5559 +
  5.5560 +  This driver is also available as a module ( = code which can be
  5.5561 +  inserted in and removed from the running kernel whenever you want).
  5.5562 +  If you want to compile it as a module, say M here and read
  5.5563 +  <file:Documentation/modules.txt>. The module will be called
  5.5564 +  ipip.o
  5.5565 +
  5.5566 +GRE tunnels over IP
  5.5567 +CONFIG_NET_IPGRE
  5.5568 +  Tunneling means encapsulating data of one protocol type within
  5.5569 +  another protocol and sending it over a channel that understands the
  5.5570 +  encapsulating protocol. This particular tunneling driver implements
  5.5571 +  GRE (Generic Routing Encapsulation) and at this time allows
  5.5572 +  encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
  5.5573 +  This driver is useful if the other endpoint is a Cisco router: Cisco
  5.5574 +  likes GRE much better than the other Linux tunneling driver ("IP
  5.5575 +  tunneling" above). In addition, GRE allows multicast redistribution
  5.5576 +  through the tunnel.
  5.5577 +
  5.5578 +  This driver is also available as a module ( = code which can be
  5.5579 +  inserted in and removed from the running kernel whenever you want).
  5.5580 +  If you want to compile it as a module, say M here and read
  5.5581 +  <file:Documentation/modules.txt>. The module will be called
  5.5582 +  ip_gre.o
  5.5583 +
  5.5584 +Broadcast GRE over IP
  5.5585 +CONFIG_NET_IPGRE_BROADCAST
  5.5586 +  One application of GRE/IP is to construct a broadcast WAN (Wide Area
  5.5587 +  Network), which looks like a normal Ethernet LAN (Local Area
  5.5588 +  Network), but can be distributed all over the Internet. If you want
  5.5589 +  to do that, say Y here and to "IP multicast routing" below.
  5.5590 +
  5.5591 +IP multicast routing
  5.5592 +CONFIG_IP_MROUTE
  5.5593 +  This is used if you want your machine to act as a router for IP
  5.5594 +  packets that have several destination addresses. It is needed on the
  5.5595 +  MBONE, a high bandwidth network on top of the Internet which carries
  5.5596 +  audio and video broadcasts. In order to do that, you would most
  5.5597 +  likely run the program mrouted. Information about the multicast
  5.5598 +  capabilities of the various network cards is contained in
  5.5599 +  <file:Documentation/networking/multicast.txt>. If you haven't heard
  5.5600 +  about it, you don't need it.
  5.5601 +
  5.5602 +PIM-SM version 1 support
  5.5603 +CONFIG_IP_PIMSM_V1
  5.5604 +  Kernel side support for Sparse Mode PIM (Protocol Independent
  5.5605 +  Multicast) version 1. This multicast routing protocol is used widely
  5.5606 +  because Cisco supports it. You need special software to use it
  5.5607 +  (pimd-v1). Please see <http://netweb.usc.edu/pim/> for more
  5.5608 +  information about PIM.
  5.5609 +
  5.5610 +  Say Y if you want to use PIM-SM v1. Note that you can say N here if
  5.5611 +  you just want to use Dense Mode PIM.
  5.5612 +
  5.5613 +PIM-SM version 2 support
  5.5614 +CONFIG_IP_PIMSM_V2
  5.5615 +  Kernel side support for Sparse Mode PIM version 2. In order to use
  5.5616 +  this, you need an experimental routing daemon supporting it (pimd or
  5.5617 +  gated-5). This routing protocol is not used widely, so say N unless
  5.5618 +  you want to play with it.
  5.5619 +
  5.5620 +Unix domain sockets
  5.5621 +CONFIG_UNIX
  5.5622 +  If you say Y here, you will include support for Unix domain sockets;
  5.5623 +  sockets are the standard Unix mechanism for establishing and
  5.5624 +  accessing network connections.  Many commonly used programs such as
  5.5625 +  the X Window system and syslog use these sockets even if your
  5.5626 +  machine is not connected to any network.  Unless you are working on
  5.5627 +  an embedded system or something similar, you therefore definitely
  5.5628 +  want to say Y here.
  5.5629 +
  5.5630 +  However, the socket support is also available as a module ( = code
  5.5631 +  which can be inserted in and removed from the running kernel
  5.5632 +  whenever you want).  If you want to compile it as a module, say M
  5.5633 +  here and read <file:Documentation/modules.txt>. The module will be
  5.5634 +  called unix.o.  If you try building this as a module and you have
  5.5635 +  said Y to "Kernel module loader support" above, be sure to add
  5.5636 +  'alias net-pf-1 unix' to your /etc/modules.conf file. Note that
  5.5637 +  several important services won't work correctly if you say M here
  5.5638 +  and then neglect to load the module.
  5.5639 +
  5.5640 +  Say Y unless you know what you are doing.
  5.5641 +
  5.5642 +The IPv6 protocol
  5.5643 +CONFIG_IPV6
  5.5644 +  This is experimental support for the next version of the Internet
  5.5645 +  Protocol: IP version 6 (also called IPng "IP next generation").
  5.5646 +  Features of this new protocol include: expanded address space,
  5.5647 +  authentication and privacy, and seamless interoperability with the
  5.5648 +  current version of IP (IP version 4). For general information about
  5.5649 +  IPv6, see <http://playground.sun.com/pub/ipng/html/ipng-main.html>;
  5.5650 +  for specific information about IPv6 under Linux read the HOWTO at
  5.5651 +  <http://www.bieringer.de/linux/IPv6/> and the file net/ipv6/README
  5.5652 +  in the kernel source.
  5.5653 +
  5.5654 +  If you want to use IPv6, please upgrade to the newest net-tools as
  5.5655 +  given in <file:Documentation/Changes>. You will still be able to do
  5.5656 +  regular IPv4 networking as well.
  5.5657 +
  5.5658 +  This protocol support is also available as a module ( = code which
  5.5659 +  can be inserted in and removed from the running kernel whenever you
  5.5660 +  want). The module will be called ipv6.o. If you want to compile it
  5.5661 +  as a module, say M here and read <file:Documentation/modules.txt>.
  5.5662 +
  5.5663 +  It is safe to say N here for now.
  5.5664 +
  5.5665 +Kernel httpd acceleration
  5.5666 +CONFIG_KHTTPD
  5.5667 +  The kernel httpd acceleration daemon (kHTTPd) is a (limited) web
  5.5668 +  server built into the kernel. It is limited since it can only serve
  5.5669 +  files from the file system and cannot deal with executable content
  5.5670 +  such as CGI scripts. Serving files is sped up if you use kHTTPd.
  5.5671 +  If kHTTPd is not able to fulfill a request, it can transparently
  5.5672 +  pass it through to a user space web server such as apache.
  5.5673 +
  5.5674 +  Saying "M" here builds the kHTTPd module; this is NOT enough to have
  5.5675 +  a working kHTTPd. For safety reasons, the module has to be activated
  5.5676 +  by doing a "echo 1 > /proc/sys/net/khttpd/start" after inserting the
  5.5677 +  module.
  5.5678 +
  5.5679 +  Before using this, read the README in net/khttpd !
  5.5680 +
  5.5681 +  The kHTTPd is experimental. Be careful when using it on a production
  5.5682 +  machine. Also note that kHTTPd doesn't support virtual servers yet.
  5.5683 +
  5.5684 +The IPX protocol
  5.5685 +CONFIG_IPX
  5.5686 +  This is support for the Novell networking protocol, IPX, commonly
  5.5687 +  used for local networks of Windows machines.  You need it if you
  5.5688 +  want to access Novell NetWare file or print servers using the Linux
  5.5689 +  Novell client ncpfs (available from
  5.5690 +  <ftp://platan.vc.cvut.cz/pub/linux/ncpfs/>) or from
  5.5691 +  within the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO,
  5.5692 +  available from <http://www.tldp.org/docs.html#howto>).  In order
  5.5693 +  to do the former, you'll also have to say Y to "NCP file system
  5.5694 +  support", below.
  5.5695 +
  5.5696 +  IPX is similar in scope to IP, while SPX, which runs on top of IPX,
  5.5697 +  is similar to TCP. There is also experimental support for SPX in
  5.5698 +  Linux (see "SPX networking", below).
  5.5699 +
  5.5700 +  To turn your Linux box into a fully featured NetWare file server and
  5.5701 +  IPX router, say Y here and fetch either lwared from
  5.5702 +  <ftp://ibiblio.org/pub/Linux/system/network/daemons/> or
  5.5703 +  mars_nwe from <ftp://www.compu-art.de/mars_nwe/>. For more
  5.5704 +  information, read the IPX-HOWTO available from
  5.5705 +  <http://www.tldp.org/docs.html#howto>.
  5.5706 +
  5.5707 +  General information about how to connect Linux, Windows machines and
  5.5708 +  Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
  5.5709 +
  5.5710 +  The IPX driver would enlarge your kernel by about 16 KB. This driver
  5.5711 +  is also available as a module ( = code which can be inserted in and
  5.5712 +  removed from the running kernel whenever you want).  The module will
  5.5713 +  be called ipx.o.  If you want to compile it as a module, say M here
  5.5714 +  and read <file:Documentation/modules.txt>.  Unless you want to
  5.5715 +  integrate your Linux box with a local Novell network, say N.
  5.5716 +
  5.5717 +Full internal IPX network
  5.5718 +CONFIG_IPX_INTERN
  5.5719 +  Every IPX network has an address that identifies it. Sometimes it is
  5.5720 +  useful to give an IPX "network" address to your Linux box as well
  5.5721 +  (for example if your box is acting as a file server for different
  5.5722 +  IPX networks: it will then be accessible from everywhere using the
  5.5723 +  same address). The way this is done is to create a virtual internal
  5.5724 +  "network" inside your box and to assign an IPX address to this
  5.5725 +  network. Say Y here if you want to do this; read the IPX-HOWTO at
  5.5726 +  <http://www.tldp.org/docs.html#howto> for details.
  5.5727 +
  5.5728 +  The full internal IPX network enables you to allocate sockets on
  5.5729 +  different virtual nodes of the internal network. This is done by
  5.5730 +  evaluating the field sipx_node of the socket address given to the
  5.5731 +  bind call. So applications should always initialize the node field
  5.5732 +  to 0 when binding a socket on the primary network. In this case the
  5.5733 +  socket is assigned the default node that has been given to the
  5.5734 +  kernel when the internal network was created. By enabling the full
  5.5735 +  internal IPX network the cross-forwarding of packets targeted at
  5.5736 +  'special' sockets to sockets listening on the primary network is
  5.5737 +  disabled. This might break existing applications, especially RIP/SAP
  5.5738 +  daemons. A RIP/SAP daemon that works well with the full internal net
  5.5739 +  can be found on <ftp://ftp.gwdg.de/pub/linux/misc/ncpfs/>.
  5.5740 +
  5.5741 +  If you don't know what you are doing, say N.
  5.5742 +
  5.5743 +#(We're told this will come back someday)
  5.5744 +
  5.5745 +SPX networking
  5.5746 +CONFIG_SPX
  5.5747 +  * Orphaned entry retained 20 April 2001 by Petr Vandrovec     *
  5.5748 +  * If you read this note from the configurator, please contact *
  5.5749 +  * the Configure.help maintainers.                             *
  5.5750 +  The Sequenced Packet eXchange protocol is a transport layer protocol
  5.5751 +  built on top of IPX. It is used in Novell NetWare systems for
  5.5752 +  client-server applications and is similar to TCP (which runs on top
  5.5753 +  of IP).
  5.5754 +
  5.5755 +  Note that Novell NetWare file sharing does not use SPX; it uses a
  5.5756 +  protocol called NCP, for which separate Linux support is available
  5.5757 +  ("NCP file system support" below for the client side, and the user
  5.5758 +  space programs lwared or mars_nwe for the server side).
  5.5759 +
  5.5760 +  Say Y here if you have use for SPX; read the IPX-HOWTO at
  5.5761 +  <http://www.tldp.org/docs.html#howto> for details.
  5.5762 +
  5.5763 +  This driver is also available as a module ( = code which can be
  5.5764 +  inserted in and removed from the running kernel whenever you want).
  5.5765 +  The module will be called af_spx.o. If you want to compile it as a
  5.5766 +  module, say M here and read <file:Documentation/modules.txt>.
  5.5767 +
  5.5768 +DECnet networking
  5.5769 +CONFIG_DECNET
  5.5770 +  The DECnet networking protocol was used in many products made by
  5.5771 +  Digital (now Compaq).  It provides reliable stream and sequenced
  5.5772 +  packet communications over which run a variety of services similar
  5.5773 +  to those which run over TCP/IP.
  5.5774 +
  5.5775 +  To find some tools to use with the kernel layer support, please
  5.5776 +  look at Patrick Caulfield's web site:
  5.5777 +  <http://linux.dreamtime.org/decnet/>.
  5.5778 +
  5.5779 +  More detailed documentation is available in
  5.5780 +  <file:Documentation/networking/decnet.txt>.
  5.5781 +
  5.5782 +  Be sure to say Y to "/proc file system support" and "Sysctl support"
  5.5783 +  below when using DECnet, since you will need sysctl support to aid
  5.5784 +  in configuration at run time.
  5.5785 +
  5.5786 +  The DECnet code is also available as a module ( = code which can be
  5.5787 +  inserted in and removed from the running kernel whenever you want).
  5.5788 +  The module is called decnet.o.
  5.5789 +
  5.5790 +DECnet SIOCFIGCONF support
  5.5791 +CONFIG_DECNET_SIOCGIFCONF
  5.5792 +  This option should only be turned on if you are really sure that
  5.5793 +  you know what you are doing. It can break other applications which
  5.5794 +  use this system call and the proper way to get the information
  5.5795 +  provided by this call is to use rtnetlink.
  5.5796 +
  5.5797 +  If unsure, say N.
  5.5798 +
  5.5799 +DECnet router support
  5.5800 +CONFIG_DECNET_ROUTER
  5.5801 +  Add support for turning your DECnet Endnode into a level 1 or 2
  5.5802 +  router.  This is an unfinished option for developers only.  If you
  5.5803 +  do say Y here, then make sure that you also say Y to "Kernel/User
  5.5804 +  network link driver", "Routing messages" and "Network packet
  5.5805 +  filtering".  The first two are required to allow configuration via
  5.5806 +  rtnetlink (currently you need Alexey Kuznetsov's iproute2 package
  5.5807 +  from <ftp://ftp.inr.ac.ru/>). The "Network packet filtering" option
  5.5808 +  will be required for the forthcoming routing daemon to work.
  5.5809 +
  5.5810 +  See <file:Documentation/networking/decnet.txt> for more information.
  5.5811 +
  5.5812 +Use FWMARK value as DECnet routing key
  5.5813 +CONFIG_DECNET_ROUTE_FWMARK
  5.5814 +  If you say Y here, you will be able to specify different routes for
  5.5815 +  packets with different FWMARK ("firewalling mark") values
  5.5816 +  (see ipchains(8), "-m" argument).
  5.5817 +
  5.5818 +AppleTalk interfaces support
  5.5819 +CONFIG_DEV_APPLETALK
  5.5820 +  AppleTalk is the protocol that Apple computers can use to communicate
  5.5821 +  on a network.  If your Linux box is connected to such a network, and wish
  5.5822 +  to do IP over it, or you have a LocalTalk card and wish to use it to
  5.5823 +  connect to the AppleTalk network, say Y.
  5.5824 +
  5.5825 +AppleTalk protocol support
  5.5826 +CONFIG_ATALK
  5.5827 +  AppleTalk is the protocol that Apple computers can use to communicate
  5.5828 +  on a network.  If your Linux box is connected to such a network and you
  5.5829 +  wish to connect to it, say Y.  You will need to use the netatalk package
  5.5830 +  so that your Linux box can act as a print and file server for Macs as
  5.5831 +  well as access AppleTalk printers.  Check out
  5.5832 +  <http://www.zettabyte.net/netatalk/> on the WWW for details.
  5.5833 +  EtherTalk is the name used for AppleTalk over Ethernet and the
  5.5834 +  cheaper and slower LocalTalk is AppleTalk over a proprietary Apple
  5.5835 +  network using serial links.  EtherTalk and LocalTalk are fully
  5.5836 +  supported by Linux.
  5.5837 +
  5.5838 +  General information about how to connect Linux, Windows machines and
  5.5839 +  Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.  The
  5.5840 +  NET-3-HOWTO, available from
  5.5841 +  <http://www.tldp.org/docs.html#howto>, contains valuable
  5.5842 +  information as well.
  5.5843 +
  5.5844 +  This driver is also available as a module ( = code which can be
  5.5845 +  inserted in and removed from the running kernel whenever you want).
  5.5846 +  The module is called appletalk.o.  If you want to compile it as a
  5.5847 +  module, say M here and read <file:Documentation/modules.txt>.  You
  5.5848 +  almost certainly want to compile it as a module so you can restart
  5.5849 +  your AppleTalk stack without rebooting your machine.  I hear that
  5.5850 +  the GNU boycott of Apple is over, so even politically correct people
  5.5851 +  are allowed to say Y here.
  5.5852 +
  5.5853 +AppleTalk-IP driver support
  5.5854 +CONFIG_IPDDP
  5.5855 +  This allows IP networking for users who only have AppleTalk
  5.5856 +  networking available. This feature is experimental. With this
  5.5857 +  driver, you can encapsulate IP inside AppleTalk (e.g. if your Linux
  5.5858 +  box is stuck on an AppleTalk only network) or decapsulate (e.g. if
  5.5859 +  you want your Linux box to act as an Internet gateway for a zoo of
  5.5860 +  AppleTalk connected Macs). Please see the file
  5.5861 +  <file:Documentation/networking/ipddp.txt> for more information.
  5.5862 +
  5.5863 +  If you say Y here, the AppleTalk-IP support will be compiled into
  5.5864 +  the kernel. In this case, you can either use encapsulation or
  5.5865 +  decapsulation, but not both. With the following two questions, you
  5.5866 +  decide which one you want.
  5.5867 +
  5.5868 +  If you say M here, the AppleTalk-IP support will be compiled as a
  5.5869 +  module ( = code which can be inserted in and removed from the
  5.5870 +  running kernel whenever you want, read
  5.5871 +  <file:Documentation/modules.txt>).  The module is called ipddp.o.
  5.5872 +  In this case, you will be able to use both encapsulation and
  5.5873 +  decapsulation simultaneously, by loading two copies of the module
  5.5874 +  and specifying different values for the module option ipddp_mode.
  5.5875 +
  5.5876 +IP to AppleTalk-IP Encapsulation support
  5.5877 +CONFIG_IPDDP_ENCAP
  5.5878 +  If you say Y here, the AppleTalk-IP code will be able to encapsulate
  5.5879 +  IP packets inside AppleTalk frames; this is useful if your Linux box
  5.5880 +  is stuck on an AppleTalk network (which hopefully contains a
  5.5881 +  decapsulator somewhere). Please see
  5.5882 +  <file:Documentation/networking/ipddp.txt> for more information. If
  5.5883 +  you said Y to "AppleTalk-IP driver support" above and you say Y
  5.5884 +  here, then you cannot say Y to "AppleTalk-IP to IP Decapsulation
  5.5885 +  support", below.
  5.5886 +
  5.5887 +AppleTalk-IP to IP Decapsulation support
  5.5888 +CONFIG_IPDDP_DECAP
  5.5889 +  If you say Y here, the AppleTalk-IP code will be able to decapsulate
  5.5890 +  AppleTalk-IP frames to IP packets; this is useful if you want your
  5.5891 +  Linux box to act as an Internet gateway for an AppleTalk network.
  5.5892 +  Please see <file:Documentation/networking/ipddp.txt> for more
  5.5893 +  information.  If you said Y to "AppleTalk-IP driver support" above
  5.5894 +  and you say Y here, then you cannot say Y to "IP to AppleTalk-IP
  5.5895 +  Encapsulation support", above.
  5.5896 +
  5.5897 +Apple/Farallon LocalTalk PC card support
  5.5898 +CONFIG_LTPC
  5.5899 +  This allows you to use the AppleTalk PC card to connect to LocalTalk
  5.5900 +  networks. The card is also known as the Farallon PhoneNet PC card.
  5.5901 +  If you are in doubt, this card is the one with the 65C02 chip on it.
  5.5902 +  You also need version 1.3.3 or later of the netatalk package.
  5.5903 +  This driver is experimental, which means that it may not work.
  5.5904 +  See the file <file:Documentation/networking/ltpc.txt>.
  5.5905 +
  5.5906 +  This driver is also available as a module ( = code which can be
  5.5907 +  inserted in and removed from the running kernel whenever you want).
  5.5908 +  If you want to compile it as a module, say M here and read
  5.5909 +  <file:Documentation/modules.txt>. The module will be called
  5.5910 +  ltpc.o
  5.5911 +
  5.5912 +COPS LocalTalk PC card support
  5.5913 +CONFIG_COPS
  5.5914 +  This allows you to use COPS AppleTalk cards to connect to LocalTalk
  5.5915 +  networks. You also need version 1.3.3 or later of the netatalk
  5.5916 +  package. This driver is experimental, which means that it may not
  5.5917 +  work. This driver will only work if you choose "AppleTalk DDP"
  5.5918 +  networking support, above.
  5.5919 +  Please read the file <file:Documentation/networking/cops.txt>.
  5.5920 +
  5.5921 +  This driver is also available as a module ( = code which can be
  5.5922 +  inserted in and removed from the running kernel whenever you want).
  5.5923 +  If you want to compile it as a module, say M here and read
  5.5924 +  <file:Documentation/modules.txt>. The module will be called
  5.5925 +  cops.o
  5.5926 +
  5.5927 +Dayna firmware support
  5.5928 +CONFIG_COPS_DAYNA
  5.5929 +  Support COPS compatible cards with Dayna style firmware (Dayna
  5.5930 +  DL2000/ Daynatalk/PC (half length), COPS LT-95, Farallon PhoneNET PC
  5.5931 +  III, Farallon PhoneNET PC II).
  5.5932 +
  5.5933 +Tangent firmware support
  5.5934 +CONFIG_COPS_TANGENT
  5.5935 +  Support COPS compatible cards with Tangent style firmware (Tangent
  5.5936 +  ATB_II, Novell NL-1000, Daystar Digital LT-200.
  5.5937 +
  5.5938 +Amateur Radio support
  5.5939 +CONFIG_HAMRADIO
  5.5940 +  If you want to connect your Linux box to an amateur radio, answer Y
  5.5941 +  here. You want to read <http://www.tapr.org/tapr/html/pkthome.html> and
  5.5942 +  the AX25-HOWTO, available from <http://www.tldp.org/docs.html#howto>.
  5.5943 +
  5.5944 +  Note that the answer to this question won't directly affect the
  5.5945 +  kernel: saying N will just cause the configurator to skip all
  5.5946 +  the questions about amateur radio.
  5.5947 +
  5.5948 +Amateur Radio AX.25 Level 2 protocol
  5.5949 +CONFIG_AX25
  5.5950 +  This is the protocol used for computer communication over amateur
  5.5951 +  radio. It is either used by itself for point-to-point links, or to
  5.5952 +  carry other protocols such as tcp/ip. To use it, you need a device
  5.5953 +  that connects your Linux box to your amateur radio. You can either
  5.5954 +  use a low speed TNC (a Terminal Node Controller acts as a kind of
  5.5955 +  modem connecting your computer's serial port to your radio's
  5.5956 +  microphone input and speaker output) supporting the KISS protocol or
  5.5957 +  one of the various SCC cards that are supported by the generic Z8530
  5.5958 +  or the DMA SCC driver. Another option are the Baycom modem serial
  5.5959 +  and parallel port hacks or the sound card modem (supported by their
  5.5960 +  own drivers). If you say Y here, you also have to say Y to one of
  5.5961 +  those drivers.
  5.5962 +
  5.5963 +  Information about where to get supporting software for Linux amateur
  5.5964 +  radio as well as information about how to configure an AX.25 port is
  5.5965 +  contained in the AX25-HOWTO, available from
  5.5966 +  <http://www.tldp.org/docs.html#howto>. You might also want to
  5.5967 +  check out the file <file:Documentation/networking/ax25.txt> in the
  5.5968 +  kernel source. More information about digital amateur radio in
  5.5969 +  general is on the WWW at
  5.5970 +  <http://www.tapr.org/tapr/html/pkthome.html>.
  5.5971 +
  5.5972 +  This driver is also available as a module ( = code which can be
  5.5973 +  inserted in and removed from the running kernel whenever you want).
  5.5974 +  The module will be called ax25.o. If you want to compile it as a
  5.5975 +  module, say M here and read <file:Documentation/modules.txt>.
  5.5976 +
  5.5977 +AX.25 DAMA Slave support
  5.5978 +CONFIG_AX25_DAMA_SLAVE
  5.5979 +  DAMA is a mechanism to prevent collisions when doing AX.25
  5.5980 +  networking. A DAMA server (called "master") accepts incoming traffic
  5.5981 +  from clients (called "slaves") and redistributes it to other slaves.
  5.5982 +  If you say Y here, your Linux box will act as a DAMA slave; this is
  5.5983 +  transparent in that you don't have to do any special DAMA
  5.5984 +  configuration. (Linux cannot yet act as a DAMA server.) If unsure,
  5.5985 +  say N.
  5.5986 +
  5.5987 +AX.25 DAMA Master support
  5.5988 +CONFIG_AX25_DAMA_MASTER
  5.5989 +  DAMA is a mechanism to prevent collisions when doing AX.25
  5.5990 +  networking. A DAMA server (called "master") accepts incoming traffic
  5.5991 +  from clients (called "slaves") and redistributes it to other
  5.5992 +  slaves. If you say Y here, your Linux box will act as a DAMA server.
  5.5993 +  If unsure, say N.
  5.5994 +
  5.5995 +Amateur Radio NET/ROM support
  5.5996 +CONFIG_NETROM
  5.5997 +  NET/ROM is a network layer protocol on top of AX.25 useful for
  5.5998 +  routing.
  5.5999 +
  5.6000 +  A comprehensive listing of all the software for Linux amateur radio
  5.6001 +  users as well as information about how to configure an AX.25 port is
  5.6002 +  contained in the AX25-HOWTO, available from
  5.6003 +  <http://www.tldp.org/docs.html#howto>. You also might want to
  5.6004 +  check out the file <file:Documentation/networking/ax25.txt>. More
  5.6005 +  information about digital amateur radio in general is on the WWW at
  5.6006 +  <http://www.tapr.org/tapr/html/pkthome.html>.
  5.6007 +
  5.6008 +  This driver is also available as a module ( = code which can be
  5.6009 +  inserted in and removed from the running kernel whenever you want).
  5.6010 +  The module will be called netrom.o. If you want to compile it as a
  5.6011 +  module, say M here and read <file:Documentation/modules.txt>.
  5.6012 +
  5.6013 +Amateur Radio X.25 PLP (Rose)
  5.6014 +CONFIG_ROSE
  5.6015 +  The Packet Layer Protocol (PLP) is a way to route packets over X.25
  5.6016 +  connections in general and amateur radio AX.25 connections in
  5.6017 +  particular, essentially an alternative to NET/ROM.
  5.6018 +
  5.6019 +  A comprehensive listing of all the software for Linux amateur radio
  5.6020 +  users as well as information about how to configure an AX.25 port is
  5.6021 +  contained in the AX25-HOWTO, available from
  5.6022 +  <http://www.tldp.org/docs.html#howto>.  You also might want to
  5.6023 +  check out the file <file:Documentation/networking/ax25.txt>. More
  5.6024 +  information about digital amateur radio in general is on the WWW at
  5.6025 +  <http://www.tapr.org/tapr/html/pkthome.html>.
  5.6026 +
  5.6027 +  This driver is also available as a module ( = code which can be
  5.6028 +  inserted in and removed from the running kernel whenever you want).
  5.6029 +  The module will be called rose.o. If you want to compile it as a
  5.6030 +  module, say M here and read <file:Documentation/modules.txt>.
  5.6031 +
  5.6032 +Serial port KISS driver for AX.25
  5.6033 +CONFIG_MKISS
  5.6034 +  KISS is a protocol used for the exchange of data between a computer
  5.6035 +  and a Terminal Node Controller (a small embedded system commonly
  5.6036 +  used for networking over AX.25 amateur radio connections; it
  5.6037 +  connects the computer's serial port with the radio's microphone
  5.6038 +  input and speaker output).
  5.6039 +
  5.6040 +  Although KISS is less advanced than the 6pack protocol, it has
  5.6041 +  the advantage that it is already supported by most modern TNCs
  5.6042 +  without the need for a firmware upgrade.
  5.6043 +
  5.6044 +  If you want to compile this driver as a module ( = code which can be
  5.6045 +  inserted in and removed from the running kernel whenever you want),
  5.6046 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.6047 +  will be called mkiss.o.
  5.6048 +
  5.6049 +Serial port 6PACK driver for AX.25
  5.6050 +CONFIG_6PACK
  5.6051 +  6pack is a transmission protocol for the data exchange between your
  5.6052 +  PC and your TNC (the Terminal Node Controller acts as a kind of
  5.6053 +  modem connecting your computer's serial port to your radio's
  5.6054 +  microphone input and speaker output). This protocol can be used as
  5.6055 +  an alternative to KISS for networking over AX.25 amateur radio
  5.6056 +  connections, but it has some extended functionality.
  5.6057 +
  5.6058 +  Note that this driver is still experimental and might cause
  5.6059 +  problems. For details about the features and the usage of the
  5.6060 +  driver, read <file:Documentation/networking/6pack.txt>.
  5.6061 +
  5.6062 +  If you want to compile this driver as a module ( = code which can be
  5.6063 +  inserted in and removed from the running kernel whenever you want),
  5.6064 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.6065 +  will be called 6pack.o.
  5.6066 +
  5.6067 +BPQ Ethernet driver
  5.6068 +CONFIG_BPQETHER
  5.6069 +  AX.25 is the protocol used for computer communication over amateur
  5.6070 +  radio. If you say Y here, you will be able to send and receive AX.25
  5.6071 +  traffic over Ethernet (also called "BPQ AX.25"), which could be
  5.6072 +  useful if some other computer on your local network has a direct
  5.6073 +  amateur radio connection.
  5.6074 +
  5.6075 +  If you want to compile the driver as a module ( = code which can be
  5.6076 +  inserted in and removed from the running kernel whenever you want),
  5.6077 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.6078 +  will be called bpqether.o.
  5.6079 +
  5.6080 +High-speed (DMA) SCC driver for AX.25
  5.6081 +CONFIG_DMASCC
  5.6082 +  This is a driver for high-speed SCC boards, i.e. those supporting
  5.6083 +  DMA on one port. You usually use those boards to connect your
  5.6084 +  computer to an amateur radio modem (such as the WA4DSY 56kbps
  5.6085 +  modem), in order to send and receive AX.25 packet radio network
  5.6086 +  traffic.
  5.6087 +
  5.6088 +  Currently, this driver supports Ottawa PI/PI2, Paccomm/Gracilis
  5.6089 +  PackeTwin, and S5SCC/DMA boards. They are detected automatically.
  5.6090 +  If you have one of these cards, say Y here and read the AX25-HOWTO,
  5.6091 +  available from <http://www.tldp.org/docs.html#howto>.
  5.6092 +
  5.6093 +  This driver can operate multiple boards simultaneously. If you
  5.6094 +  compile it as a module (by saying M instead of Y), it will be called
  5.6095 +  dmascc.o. If you don't pass any parameter to the driver, all
  5.6096 +  possible I/O addresses are probed. This could irritate other devices
  5.6097 +  that are currently not in use. You may specify the list of addresses
  5.6098 +  to be probed by "dmascc=addr1,addr2,..." (when compiled into the
  5.6099 +  kernel image) or "io=addr1,addr2,..." (when loaded as a module). The
  5.6100 +  network interfaces will be called dmascc0 and dmascc1 for the board
  5.6101 +  detected first, dmascc2 and dmascc3 for the second one, and so on.
  5.6102 +
  5.6103 +  Before you configure each interface with ifconfig, you MUST set
  5.6104 +  certain parameters, such as channel access timing, clock mode, and
  5.6105 +  DMA channel. This is accomplished with a small utility program,
  5.6106 +  dmascc_cfg, available at
  5.6107 +  <http://www.nt.tuwien.ac.at/~kkudielk/Linux/>. Please be sure to get
  5.6108 +  at least version 1.27 of dmascc_cfg, as older versions will not
  5.6109 +  work with the current driver.
  5.6110 +
  5.6111 +Z8530 SCC driver for AX.25
  5.6112 +CONFIG_SCC
  5.6113 +  These cards are used to connect your Linux box to an amateur radio
  5.6114 +  in order to communicate with other computers. If you want to use
  5.6115 +  this, read <file:Documentation/networking/z8530drv.txt> and the
  5.6116 +  AX25-HOWTO, available from
  5.6117 +  <http://www.tldp.org/docs.html#howto>. Also make sure to say Y
  5.6118 +  to "Amateur Radio AX.25 Level 2" support.
  5.6119 +
  5.6120 +  If you want to compile this as a module ( = code which can be
  5.6121 +  inserted in and removed from the running kernel whenever you want),
  5.6122 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.6123 +  will be called scc.o.
  5.6124 +
  5.6125 +Support for TRX that feedback the tx signal to rx
  5.6126 +CONFIG_SCC_TRXECHO
  5.6127 +  Some transmitters feed the transmitted signal back to the receive
  5.6128 +  line.  Say Y here to foil this by explicitly disabling the receiver
  5.6129 +  during data transmission.  If in doubt, say Y.
  5.6130 +
  5.6131 +Additional delay for PA0HZP OptoSCC compatible boards
  5.6132 +CONFIG_SCC_DELAY
  5.6133 +  Say Y here if you experience problems with the SCC driver not
  5.6134 +  working properly; please read
  5.6135 +  <file:Documentation/networking/z8530drv.txt> for details. If unsure,
  5.6136 +  say N.
  5.6137 +
  5.6138 +YAM driver for AX.25
  5.6139 +CONFIG_YAM
  5.6140 +  The YAM is a modem for packet radio which connects to the serial
  5.6141 +  port and includes some of the functions of a Terminal Node
  5.6142 +  Controller. If you have one of those, say Y here.
  5.6143 +
  5.6144 +  If you want to compile the driver as a module ( = code which can be
  5.6145 +  inserted in and removed from the running kernel whenever you want),
  5.6146 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.6147 +  will be called yam.o.
  5.6148 +
  5.6149 +BAYCOM picpar and par96 driver for AX.25
  5.6150 +CONFIG_BAYCOM_PAR
  5.6151 +  This is a driver for Baycom style simple amateur radio modems that
  5.6152 +  connect to a parallel interface. The driver supports the picpar and
  5.6153 +  par96 designs. To configure the driver, use the sethdlc utility
  5.6154 +  available in the standard ax25 utilities package. For information on
  5.6155 +  the modems, see <http://www.baycom.de/> and the file
  5.6156 +  <file:Documentation/networking/baycom.txt>.
  5.6157 +
  5.6158 +  If you want to compile this driver as a module ( = code which can be
  5.6159 +  inserted in and removed from the running kernel whenever you want),
  5.6160 +  say M here and read <file:Documentation/modules.txt>.  This is
  5.6161 +  recommended.  The module will be called baycom_par.o.
  5.6162 +
  5.6163 +BAYCOM EPP driver for AX.25
  5.6164 +CONFIG_BAYCOM_EPP
  5.6165 +  This is a driver for Baycom style simple amateur radio modems that
  5.6166 +  connect to a parallel interface. The driver supports the EPP
  5.6167 +  designs. To configure the driver, use the sethdlc utility available
  5.6168 +  in the standard ax25 utilities package. For information on the
  5.6169 +  modems, see <http://www.baycom.de/> and the file
  5.6170 +  <file:Documentation/networking/baycom.txt>.
  5.6171 +
  5.6172 +  If you want to compile this driver as a module ( = code which can be
  5.6173 +  inserted in and removed from the running kernel whenever you want),
  5.6174 +  say M here and read <file:Documentation/modules.txt>.  This is
  5.6175 +  recommended.  The module will be called baycom_par.o.
  5.6176 +
  5.6177 +BAYCOM ser12 full-duplex driver for AX.25
  5.6178 +CONFIG_BAYCOM_SER_FDX
  5.6179 +  This is one of two drivers for Baycom style simple amateur radio
  5.6180 +  modems that connect to a serial interface. The driver supports the
  5.6181 +  ser12 design in full-duplex mode. In addition, it allows the
  5.6182 +  baudrate to be set between 300 and 4800 baud (however not all modems
  5.6183 +  support all baudrates). This is the preferred driver. The next
  5.6184 +  driver, "BAYCOM ser12 half-duplex driver for AX.25" is the old
  5.6185 +  driver and still provided in case this driver does not work with
  5.6186 +  your serial interface chip. To configure the driver, use the sethdlc
  5.6187 +  utility available in the standard ax25 utilities package. For
  5.6188 +  information on the modems, see <http://www.baycom.de/> and
  5.6189 +  <file:Documentation/networking/baycom.txt>.
  5.6190 +
  5.6191 +  If you want to compile this driver as a module ( = code which can be
  5.6192 +  inserted in and removed from the running kernel whenever you want),
  5.6193 +  say M here and read <file:Documentation/modules.txt>.  This is
  5.6194 +  recommended.  The module will be called baycom_ser_fdx.o.
  5.6195 +
  5.6196 +BAYCOM ser12 half-duplex driver for AX.25
  5.6197 +CONFIG_BAYCOM_SER_HDX
  5.6198 +  This is one of two drivers for Baycom style simple amateur radio
  5.6199 +  modems that connect to a serial interface. The driver supports the
  5.6200 +  ser12 design in full-duplex mode. This is the old driver.  It is
  5.6201 +  still provided in case your serial interface chip does not work with
  5.6202 +  the full-duplex driver. This driver is depreciated.  To configure
  5.6203 +  the driver, use the sethdlc utility available in the standard ax25
  5.6204 +  utilities package. For information on the modems, see
  5.6205 +  <http://www.baycom.de/> and
  5.6206 +  <file:Documentation/networking/baycom.txt>.
  5.6207 +
  5.6208 +  If you want to compile this driver as a module ( = code which can be
  5.6209 +  inserted in and removed from the running kernel whenever you want),
  5.6210 +  say M here and read <file:Documentation/modules.txt>.  This is
  5.6211 +  recommended.  The module will be called baycom_ser_hdx.o.
  5.6212 +
  5.6213 +Sound card modem driver for AX.25
  5.6214 +CONFIG_SOUNDMODEM
  5.6215 +  This experimental driver allows a standard Sound Blaster or
  5.6216 +  WindowsSoundSystem compatible sound card to be used as a packet
  5.6217 +  radio modem (NOT as a telephone modem!), to send digital traffic
  5.6218 +  over amateur radio.
  5.6219 +
  5.6220 +  To configure the driver, use the sethdlc, smdiag and smmixer
  5.6221 +  utilities available in the standard ax25 utilities package. For
  5.6222 +  information on how to key the transmitter, see
  5.6223 +  <http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html> and
  5.6224 +  <file:Documentation/networking/soundmodem.txt>.
  5.6225 +
  5.6226 +  If you want to compile this driver as a module ( = code which can be
  5.6227 +  inserted in and removed from the running kernel whenever you want),
  5.6228 +  say M here and read <file:Documentation/modules.txt>.  This is
  5.6229 +  recommended.  The module will be called soundmodem.o.
  5.6230 +
  5.6231 +Sound card modem support for Sound Blaster and compatible cards
  5.6232 +CONFIG_SOUNDMODEM_SBC
  5.6233 +  This option enables the soundmodem driver to use Sound Blaster and
  5.6234 +  compatible cards. If you have a dual mode card (i.e. a WSS cards
  5.6235 +  with a Sound Blaster emulation) you should say N here and Y to
  5.6236 +  "Sound card modem support for WSS and Crystal cards", below, because
  5.6237 +  this usually results in better performance. This option also
  5.6238 +  supports SB16/32/64 in full-duplex mode.
  5.6239 +
  5.6240 +Sound card modem support for WSS and Crystal cards
  5.6241 +CONFIG_SOUNDMODEM_WSS
  5.6242 +  This option enables the soundmodem driver to use WindowsSoundSystem
  5.6243 +  compatible cards. These cards feature a codec chip from either
  5.6244 +  Analog Devices (such as AD1848, AD1845, AD1812) or Crystal
  5.6245 +  Semiconductors (such as CS4248, CS423x). This option also supports
  5.6246 +  the WSS full-duplex operation which currently works with Crystal
  5.6247 +  CS423x chips. If you don't need full-duplex operation, do not enable
  5.6248 +  it to save performance.
  5.6249 +
  5.6250 +Sound card modem support for 1200 baud AFSK modulation
  5.6251 +CONFIG_SOUNDMODEM_AFSK1200
  5.6252 +  This option enables the soundmodem driver 1200 baud AFSK modem,
  5.6253 +  compatible to popular modems using TCM3105 or AM7911. The
  5.6254 +  demodulator requires about 12% of the CPU power of a Pentium 75 CPU
  5.6255 +  per channel.
  5.6256 +
  5.6257 +Sound card modem support for 2400 baud AFSK modulation (7.3728MHz crystal)
  5.6258 +CONFIG_SOUNDMODEM_AFSK2400_7
  5.6259 +  This option enables the soundmodem driver 2400 baud AFSK modem,
  5.6260 +  compatible to TCM3105 modems (over-)clocked with a 7.3728MHz
  5.6261 +  crystal. Note that the availability of this driver does _not_ imply
  5.6262 +  that I recommend building such links. It is only here since users
  5.6263 +  especially in eastern Europe have asked me to do so. In fact this
  5.6264 +  modulation scheme has many disadvantages, mainly its incompatibility
  5.6265 +  with many transceiver designs and the fact that the TCM3105 (if
  5.6266 +  used) is operated widely outside its specifications.
  5.6267 +
  5.6268 +Sound card modem support for 2400 baud AFSK modulation (8MHz crystal)
  5.6269 +CONFIG_SOUNDMODEM_AFSK2400_8
  5.6270 +  This option enables the soundmodem driver 2400 baud AFSK modem,
  5.6271 +  compatible to TCM3105 modems (over-)clocked with an 8MHz crystal.
  5.6272 +  Note that the availability of this driver does _not_ imply that I
  5.6273 +  recommend building such links. It is only here since users
  5.6274 +  especially in eastern Europe have asked me to do so. In fact this
  5.6275 +  modulation scheme has many disadvantages, mainly its incompatibility
  5.6276 +  with many transceiver designs and the fact that the TCM3105 (if
  5.6277 +  used) is operated widely outside its specifications.
  5.6278 +
  5.6279 +Sound card modem support for 2666 baud AFSK modulation
  5.6280 +CONFIG_SOUNDMODEM_AFSK2666
  5.6281 +  This option enables the soundmodem driver 2666 baud AFSK modem.
  5.6282 +  This modem is experimental, and not compatible to anything
  5.6283 +  else I know of.
  5.6284 +
  5.6285 +Sound card modem support for 4800 baud 8PSK modulation
  5.6286 +CONFIG_SOUNDMODEM_PSK4800
  5.6287 +  This option enables the soundmodem driver 4800 baud 8PSK modem.
  5.6288 +  This modem is experimental, and not compatible to anything
  5.6289 +  else I know of.
  5.6290 +
  5.6291 +Sound card modem support for 4800 baud HAPN-1 modulation
  5.6292 +CONFIG_SOUNDMODEM_HAPN4800
  5.6293 +  This option enables the soundmodem driver 4800 baud HAPN-1
  5.6294 +  compatible modem. This modulation seems to be widely used 'down
  5.6295 +  under' and in the Netherlands. Here, nobody uses it, so I could not
  5.6296 +  test if it works. It is compatible to itself, however :-)
  5.6297 +
  5.6298 +Sound card modem support for 9600 baud FSK G3RUH modulation
  5.6299 +CONFIG_SOUNDMODEM_FSK9600
  5.6300 +  This option enables the soundmodem driver 9600 baud FSK modem,
  5.6301 +  compatible to the G3RUH standard. The demodulator requires about 4%
  5.6302 +  of the CPU power of a Pentium 75 CPU per channel. You can say Y to
  5.6303 +  both 1200 baud AFSK and 9600 baud FSK if you want (but obviously you
  5.6304 +  can only use one protocol at a time, depending on what the other end
  5.6305 +  can understand).
  5.6306 +
  5.6307 +CCITT X.25 Packet Layer
  5.6308 +CONFIG_X25
  5.6309 +  X.25 is a set of standardized network protocols, similar in scope to
  5.6310 +  frame relay; the one physical line from your box to the X.25 network
  5.6311 +  entry point can carry several logical point-to-point connections
  5.6312 +  (called "virtual circuits") to other computers connected to the X.25
  5.6313 +  network. Governments, banks, and other organizations tend to use it
  5.6314 +  to connect to each other or to form Wide Area Networks (WANs). Many
  5.6315 +  countries have public X.25 networks. X.25 consists of two
  5.6316 +  protocols: the higher level Packet Layer Protocol (PLP) (say Y here
  5.6317 +  if you want that) and the lower level data link layer protocol LAPB
  5.6318 +  (say Y to "LAPB Data Link Driver" below if you want that).
  5.6319 +
  5.6320 +  You can read more about X.25 at <http://www.sangoma.com/x25.htm> and
  5.6321 +  <http://www.cisco.com/univercd/data/doc/software/11_0/rpcg/cx25.htm>.
  5.6322 +  Information about X.25 for Linux is contained in the files
  5.6323 +  <file:Documentation/networking/x25.txt> and
  5.6324 +  <file:Documentation/networking/x25-iface.txt>.
  5.6325 +
  5.6326 +  One connects to an X.25 network either with a dedicated network card
  5.6327 +  using the X.21 protocol (not yet supported by Linux) or one can do
  5.6328 +  X.25 over a standard telephone line using an ordinary modem (say Y
  5.6329 +  to "X.25 async driver" below) or over Ethernet using an ordinary
  5.6330 +  Ethernet card and either the 802.2 LLC protocol (say Y to "802.2
  5.6331 +  LLC" below) or LAPB over Ethernet (say Y to "LAPB Data Link Driver"
  5.6332 +  and "LAPB over Ethernet driver" below).
  5.6333 +
  5.6334 +  If you want to compile this driver as a module ( = code which can be
  5.6335 +  inserted in and removed from the running kernel whenever you want),
  5.6336 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.6337 +  will be called x25.o. If unsure, say N.
  5.6338 +
  5.6339 +LAPB Data Link Driver
  5.6340 +CONFIG_LAPB
  5.6341 +  Link Access Procedure, Balanced (LAPB) is the data link layer (i.e.
  5.6342 +  the lower) part of the X.25 protocol. It offers a reliable
  5.6343 +  connection service to exchange data frames with one other host, and
  5.6344 +  it is used to transport higher level protocols (mostly X.25 Packet
  5.6345 +  Layer, the higher part of X.25, but others are possible as well).
  5.6346 +  Usually, LAPB is used with specialized X.21 network cards, but Linux
  5.6347 +  currently supports LAPB only over Ethernet connections. If you want
  5.6348 +  to use LAPB connections over Ethernet, say Y here and to "LAPB over
  5.6349 +  Ethernet driver" below. Read
  5.6350 +  <file:Documentation/networking/lapb-module.txt> for technical
  5.6351 +  details.
  5.6352 +
  5.6353 +  If you want to compile this driver as a module though ( = code which
  5.6354 +  can be inserted in and removed from the running kernel whenever you
  5.6355 +  want), say M here and read <file:Documentation/modules.txt>.  The
  5.6356 +  module will be called lapb.o.  If unsure, say N.
  5.6357 +
  5.6358 +802.2 LLC
  5.6359 +CONFIG_LLC
  5.6360 +  This is a Logical Link Layer protocol used for X.25 connections over
  5.6361 +  Ethernet, using ordinary Ethernet cards.
  5.6362 +
  5.6363 +Frame Diverter
  5.6364 +CONFIG_NET_DIVERT
  5.6365 +  The Frame Diverter allows you to divert packets from the
  5.6366 +  network, that are not aimed at the interface receiving it (in
  5.6367 +  promisc. mode). Typically, a Linux box setup as an Ethernet bridge
  5.6368 +  with the Frames Diverter on, can do some *really* transparent www
  5.6369 +  caching using a Squid proxy for example.
  5.6370 +
  5.6371 +  This is very useful when you don't want to change your router's
  5.6372 +  config (or if you simply don't have access to it).
  5.6373 +
  5.6374 +  The other possible usages of diverting Ethernet Frames are
  5.6375 +  numberous:
  5.6376 +   - reroute smtp traffic to another interface
  5.6377 +   - traffic-shape certain network streams
  5.6378 +   - transparently proxy smtp connections
  5.6379 +   - etc...
  5.6380 +
  5.6381 +  For more informations, please refer to:
  5.6382 +    <http://diverter.sourceforge.net/>
  5.6383 +    <http://perso.wanadoo.fr/magpie/EtherDivert.html>
  5.6384 +
  5.6385 +  If unsure, say N.
  5.6386 +
  5.6387 +802.1d Ethernet Bridging
  5.6388 +CONFIG_BRIDGE
  5.6389 +  If you say Y here, then your Linux box will be able to act as an
  5.6390 +  Ethernet bridge, which means that the different Ethernet segments it
  5.6391 +  is connected to will appear as one Ethernet to the participants.
  5.6392 +  Several such bridges can work together to create even larger
  5.6393 +  networks of Ethernets using the IEEE 802.1 spanning tree algorithm.
  5.6394 +  As this is a standard, Linux bridges will cooperate properly with
  5.6395 +  other third party bridge products.
  5.6396 +
  5.6397 +  In order to use the Ethernet bridge, you'll need the bridge
  5.6398 +  configuration tools; see <file:Documentation/networking/bridge.txt>
  5.6399 +  for location. Please read the Bridge mini-HOWTO for more
  5.6400 +  information.
  5.6401 +
  5.6402 +  Note that if your box acts as a bridge, it probably contains several
  5.6403 +  Ethernet devices, but the kernel is not able to recognize more than
  5.6404 +  one at boot time without help; for details read the Ethernet-HOWTO,
  5.6405 +  available from in <http://www.tldp.org/docs.html#howto>.
  5.6406 +
  5.6407 +  If you want to compile this code as a module ( = code which can be
  5.6408 +  inserted in and removed from the running kernel whenever you want),
  5.6409 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.6410 +  will be called bridge.o.
  5.6411 +
  5.6412 +  If unsure, say N.
  5.6413 +
  5.6414 +Packet socket
  5.6415 +CONFIG_PACKET
  5.6416 +  The Packet protocol is used by applications which communicate
  5.6417 +  directly with network devices without an intermediate network
  5.6418 +  protocol implemented in the kernel, e.g. tcpdump.  If you want them
  5.6419 +  to work, choose Y.
  5.6420 +
  5.6421 +  This driver is also available as a module called af_packet.o ( =
  5.6422 +  code which can be inserted in and removed from the running kernel
  5.6423 +  whenever you want).  If you want to compile it as a module, say M
  5.6424 +  here and read <file:Documentation/modules.txt>; if you use modprobe
  5.6425 +  or kmod, you may also want to add "alias net-pf-17 af_packet" to
  5.6426 +  /etc/modules.conf.
  5.6427 +
  5.6428 +  If unsure, say Y.
  5.6429 +
  5.6430 +Packet socket: mmapped IO
  5.6431 +CONFIG_PACKET_MMAP
  5.6432 +  If you say Y here, the Packet protocol driver will use an IO
  5.6433 +  mechanism that results in faster communication.
  5.6434 +
  5.6435 +  If unsure, say N.
  5.6436 +
  5.6437 +Netlink device emulation
  5.6438 +CONFIG_NETLINK_DEV
  5.6439 +  This option will be removed soon. Any programs that want to use
  5.6440 +  character special nodes like /dev/tap0 or /dev/route (all with major
  5.6441 +  number 36) need this option, and need to be rewritten soon to use
  5.6442 +  the real netlink socket.
  5.6443 +  This is a backward compatibility option, choose Y for now.
  5.6444 +
  5.6445 +  This driver is also available as a module ( = code which can be
  5.6446 +  inserted in and removed from the running kernel whenever you want).
  5.6447 +  If you want to compile it as a module, say M here and read
  5.6448 +  <file:Documentation/modules.txt>. The module will be called
  5.6449 +  netlink_dev.o
  5.6450 +
  5.6451 +Asynchronous Transfer Mode (ATM)
  5.6452 +CONFIG_ATM
  5.6453 +  ATM is a high-speed networking technology for Local Area Networks
  5.6454 +  and Wide Area Networks.  It uses a fixed packet size and is
  5.6455 +  connection oriented, allowing for the negotiation of minimum
  5.6456 +  bandwidth requirements.
  5.6457 +
  5.6458 +  In order to participate in an ATM network, your Linux box needs an
  5.6459 +  ATM networking card. If you have that, say Y here and to the driver
  5.6460 +  of your ATM card below.
  5.6461 +
  5.6462 +  Note that you need a set of user-space programs to actually make use
  5.6463 +  of ATM.  See the file <file:Documentation/networking/atm.txt> for
  5.6464 +  further details.
  5.6465 +
  5.6466 +Classical IP over ATM
  5.6467 +CONFIG_ATM_CLIP
  5.6468 +  Classical IP over ATM for PVCs and SVCs, supporting InARP and
  5.6469 +  ATMARP. If you want to communication with other IP hosts on your ATM
  5.6470 +  network, you will typically either say Y here or to "LAN Emulation
  5.6471 +  (LANE)" below.
  5.6472 +
  5.6473 +Do NOT send ICMP if no neighbour
  5.6474 +CONFIG_ATM_CLIP_NO_ICMP
  5.6475 +  Normally, an "ICMP host unreachable" message is sent if a neighbour
  5.6476 +  cannot be reached because there is no VC to it in the kernel's
  5.6477 +  ATMARP table. This may cause problems when ATMARP table entries are
  5.6478 +  briefly removed during revalidation. If you say Y here, packets to
  5.6479 +  such neighbours are silently discarded instead.
  5.6480 +
  5.6481 +RFC1483/2684 Bridged protocols
  5.6482 +CONFIG_ATM_BR2684
  5.6483 +  ATM PVCs can carry ethernet PDUs according to rfc2684 (formerly 1483)
  5.6484 +  This device will act like an ethernet from the kernels point of view,
  5.6485 +  with the traffic being carried by ATM PVCs (currently 1 PVC/device).
  5.6486 +  This is sometimes used over DSL lines.  If in doubt, say N.
  5.6487 +
  5.6488 +Per-VC IP filter kludge
  5.6489 +CONFIG_ATM_BR2684_IPFILTER
  5.6490 +  This is an experimental mechanism for users who need to terminating a
  5.6491 +  large number of IP-only vcc's.  Do not enable this unless you are sure
  5.6492 +  you know what you are doing.
  5.6493 +
  5.6494 +LAN Emulation (LANE) support
  5.6495 +CONFIG_ATM_LANE
  5.6496 +  LAN Emulation emulates services of existing LANs across an ATM
  5.6497 +  network. Besides operating as a normal ATM end station client, Linux
  5.6498 +  LANE client can also act as an proxy client bridging packets between
  5.6499 +  ELAN and Ethernet segments. You need LANE if you want to try MPOA.
  5.6500 +
  5.6501 +Multi-Protocol Over ATM (MPOA) support
  5.6502 +CONFIG_ATM_MPOA
  5.6503 +  Multi-Protocol Over ATM allows ATM edge devices such as routers,
  5.6504 +  bridges and ATM attached hosts establish direct ATM VCs across
  5.6505 +  subnetwork boundaries. These shortcut connections bypass routers
  5.6506 +  enhancing overall network performance.
  5.6507 +
  5.6508 +ATM over TCP
  5.6509 +CONFIG_ATM_TCP
  5.6510 +  ATM over TCP driver. Useful mainly for development and for
  5.6511 +  experiments. If unsure, say N.
  5.6512 +
  5.6513 +Efficient Networks ENI155P
  5.6514 +CONFIG_ATM_ENI
  5.6515 +  Driver for the Efficient Networks ENI155p series and SMC ATM
  5.6516 +  Power155 155 Mbps ATM adapters. Both, the versions with 512KB and
  5.6517 +  2MB on-board RAM (Efficient calls them "C" and "S", respectively),
  5.6518 +  and the FPGA and the ASIC Tonga versions of the board are supported.
  5.6519 +  The driver works with MMF (-MF or ...F) and UTP-5 (-U5 or ...D)
  5.6520 +  adapters.
  5.6521 +
  5.6522 +  This driver is also available as a module.  If you want to compile
  5.6523 +  it as a module, say M here and read
  5.6524 +  <file:Documentation/modules.txt>.  The module will be called eni.o.
  5.6525 +
  5.6526 +Enable extended debugging
  5.6527 +CONFIG_ATM_ENI_DEBUG
  5.6528 +  Extended debugging records various events and displays that list
  5.6529 +  when an inconsistency is detected. This mechanism is faster than
  5.6530 +  generally using printks, but still has some impact on performance.
  5.6531 +  Note that extended debugging may create certain race conditions
  5.6532 +  itself. Enable this ONLY if you suspect problems with the driver.
  5.6533 +
  5.6534 +Fine-tune burst settings
  5.6535 +CONFIG_ATM_ENI_TUNE_BURST
  5.6536 +  In order to obtain good throughput, the ENI NIC can transfer
  5.6537 +  multiple words of data per PCI bus access cycle. Such a multi-word
  5.6538 +  transfer is called a burst.
  5.6539 +
  5.6540 +  The default settings for the burst sizes are suitable for most PCI
  5.6541 +  chipsets. However, in some cases, large bursts may overrun buffers
  5.6542 +  in the PCI chipset and cause data corruption. In such cases, large
  5.6543 +  bursts must be disabled and only (slower) small bursts can be used.
  5.6544 +  The burst sizes can be set independently in the send (TX) and
  5.6545 +  receive (RX) direction.
  5.6546 +
  5.6547 +  Note that enabling many different burst sizes in the same direction
  5.6548 +  may increase the cost of setting up a transfer such that the
  5.6549 +  resulting throughput is lower than when using only the largest
  5.6550 +  available burst size.
  5.6551 +
  5.6552 +  Also, sometimes larger bursts lead to lower throughput, e.g. on an
  5.6553 +  Intel 440FX board, a drop from 135 Mbps to 103 Mbps was observed
  5.6554 +  when going from 8W to 16W bursts.
  5.6555 +
  5.6556 +Enable 16W TX bursts (discouraged)
  5.6557 +CONFIG_ATM_ENI_BURST_TX_16W
  5.6558 +  Burst sixteen words at once in the send direction. This may work
  5.6559 +  with recent PCI chipsets, but is known to fail with older chipsets.
  5.6560 +
  5.6561 +Enable 8W TX bursts (recommended)
  5.6562 +CONFIG_ATM_ENI_BURST_TX_8W
  5.6563 +  Burst eight words at once in the send direction. This is the default
  5.6564 +  setting.
  5.6565 +
  5.6566 +Enable 4W TX bursts (optional)
  5.6567 +CONFIG_ATM_ENI_BURST_TX_4W
  5.6568 +  Burst four words at once in the send direction. You may want to try
  5.6569 +  this if you have disabled 8W bursts. Enabling 4W if 8W is also set
  5.6570 +  may or may not improve throughput.
  5.6571 +
  5.6572 +Enable 2W TX bursts (optional)
  5.6573 +CONFIG_ATM_ENI_BURST_TX_2W
  5.6574 +  Burst two words at once in the send direction. You may want to try
  5.6575 +  this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or 8W
  5.6576 +  are also set may or may not improve throughput.
  5.6577 +
  5.6578 +Enable 16W RX bursts (discouraged)
  5.6579 +CONFIG_ATM_ENI_BURST_RX_16W
  5.6580 +  Burst sixteen words at once in the receive direction. This may work
  5.6581 +  with recent PCI chipsets, but is known to fail with older chipsets.
  5.6582 +
  5.6583 +Enable 8W RX bursts (discouraged)
  5.6584 +CONFIG_ATM_ENI_BURST_RX_8W
  5.6585 +  Burst eight words at once in the receive direction. This may work
  5.6586 +  with recent PCI chipsets, but is known to fail with older chipsets,
  5.6587 +  such as the Intel Neptune series.
  5.6588 +
  5.6589 +Enable 4W RX bursts (recommended)
  5.6590 +CONFIG_ATM_ENI_BURST_RX_4W
  5.6591 +  Burst four words at once in the receive direction. This is the
  5.6592 +  default setting. Enabling 4W if 8W is also set may or may not
  5.6593 +  improve throughput.
  5.6594 +
  5.6595 +Enable 2W RX bursts (optional)
  5.6596 +CONFIG_ATM_ENI_BURST_RX_2W
  5.6597 +  Burst two words at once in the receive direction. You may want to
  5.6598 +  try this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or
  5.6599 +  8W are also set may or may not improve throughput.
  5.6600 +
  5.6601 +ZeitNet ZN1221/ZN1225
  5.6602 +CONFIG_ATM_ZATM
  5.6603 +  Driver for the ZeitNet ZN1221 (MMF) and ZN1225 (UTP-5) 155 Mbps ATM
  5.6604 +  adapters.
  5.6605 +
  5.6606 +  This driver is also available as a module.  If you want to compile
  5.6607 +  it as a module, say M here and read
  5.6608 +  <file:Documentation/modules.txt>.  The module will be called zatm.o.
  5.6609 +
  5.6610 +Enable extended debugging
  5.6611 +CONFIG_ATM_ZATM_DEBUG
  5.6612 +  Extended debugging records various events and displays that list
  5.6613 +  when an inconsistency is detected. This mechanism is faster than
  5.6614 +  generally using printks, but still has some impact on performance.
  5.6615 +  Note that extended debugging may create certain race conditions
  5.6616 +  itself. Enable this ONLY if you suspect problems with the driver.
  5.6617 +
  5.6618 +Fujitsu FireStream (FS50/FS155)
  5.6619 +CONFIG_ATM_FIRESTREAM
  5.6620 +  Driver for the Fujitsu FireStream 155 (MB86697) and
  5.6621 +  FireStream 50 (MB86695) ATM PCI chips.
  5.6622 +
  5.6623 +  This driver is also available as a module.  If you want to compile
  5.6624 +  it as a module, say M here and read
  5.6625 +  <file:Documentation/modules.txt>.  The module will be called
  5.6626 +  firestream.o.
  5.6627 +
  5.6628 +Enable usec resolution timestamps
  5.6629 +CONFIG_ATM_ZATM_EXACT_TS
  5.6630 +  The uPD98401 SAR chip supports a high-resolution timer (approx. 30
  5.6631 +  MHz) that is used for very accurate reception timestamps. Because
  5.6632 +  that timer overflows after 140 seconds, and also to avoid timer
  5.6633 +  drift, time measurements need to be periodically synchronized with
  5.6634 +  the normal system time. Enabling this feature will add some general
  5.6635 +  overhead for timer synchronization and also per-packet overhead for
  5.6636 +  time conversion.
  5.6637 +
  5.6638 +IDT 77201/11 (NICStAR) (ForeRunnerLE)
  5.6639 +CONFIG_ATM_NICSTAR
  5.6640 +  The NICStAR chipset family is used in a large number of ATM NICs for
  5.6641 +  25 and for 155 Mbps, including IDT cards and the Fore ForeRunnerLE
  5.6642 +  series. Say Y if you have one of those.
  5.6643 +
  5.6644 +  This driver is also available as a module.  If you want to compile
  5.6645 +  it as a module, say M here and read
  5.6646 +  <file:Documentation/modules.txt>. The module will be called
  5.6647 +  nicstar.o.
  5.6648 +
  5.6649 +Use suni PHY driver (155Mbps)
  5.6650 +CONFIG_ATM_NICSTAR_USE_SUNI
  5.6651 +  Support for the S-UNI and compatible PHYsical layer chips. These are
  5.6652 +  found in most 155Mbps NICStAR based ATM cards, namely in the
  5.6653 +  ForeRunner LE155 cards. This driver provides detection of cable~
  5.6654 +  removal and reinsertion and provides some statistics. This driver
  5.6655 +  doesn't have removal capability when compiled as a module, so if you
  5.6656 +  need that capability don't include S-UNI support (it's not needed to
  5.6657 +  make the card work).
  5.6658 +
  5.6659 +Use IDT77015 PHY driver (25Mbps)
  5.6660 +CONFIG_ATM_NICSTAR_USE_IDT77105
  5.6661 +  Support for the PHYsical layer chip in ForeRunner LE25 cards. In
  5.6662 +  addition to cable removal/reinsertion detection, this driver allows
  5.6663 +  you to control the loopback mode of the chip via a dedicated IOCTL.
  5.6664 +  This driver is required for proper handling of temporary carrier
  5.6665 +  loss, so if you have a 25Mbps NICStAR based ATM card you must say Y.
  5.6666 +
  5.6667 +IDT 77252 (NICStAR II)
  5.6668 +CONFIG_ATM_IDT77252
  5.6669 +  Driver for the IDT 77252 ATM PCI chips.
  5.6670 +
  5.6671 +  This driver is also available as a module.  If you want to compile
  5.6672 +  it as a module, say M here and read
  5.6673 +  <file:Documentation/modules.txt>. The module will be called idt77252.o
  5.6674 +
  5.6675 +Enable debugging messages
  5.6676 +CONFIG_ATM_IDT77252_DEBUG
  5.6677 +  Somewhat useful debugging messages are available. The choice of
  5.6678 +  messages is controlled by a bitmap.  This may be specified as a
  5.6679 +  module argument.  See the file <file:drivers/atm/idt77252.h> for
  5.6680 +  the meanings of the bits in the mask.
  5.6681 +
  5.6682 +  When active, these messages can have a significant impact on the
  5.6683 +  speed of the driver, and the size of your syslog files! When
  5.6684 +  inactive, they will have only a modest impact on performance.
  5.6685 +
  5.6686 +Receive ALL cells in raw queue
  5.6687 +CONFIG_ATM_IDT77252_RCV_ALL
  5.6688 +  Enable receiving of all cells on the ATM link, that do not match
  5.6689 +  an open connection in the raw cell queue of the driver.  Useful
  5.6690 +  for debugging or special applications only, so the safe answer is N.
  5.6691 +
  5.6692 +Madge Ambassador (Collage PCI 155 Server)
  5.6693 +CONFIG_ATM_AMBASSADOR
  5.6694 +  This is a driver for ATMizer based ATM card produced by Madge
  5.6695 +  Networks Ltd. Say Y (or M to compile as a module named ambassador.o)
  5.6696 +  here if you have one of these cards.
  5.6697 +
  5.6698 +Enable debugging messages
  5.6699 +CONFIG_ATM_AMBASSADOR_DEBUG
  5.6700 +  Somewhat useful debugging messages are available. The choice of
  5.6701 +  messages is controlled by a bitmap.  This may be specified as a
  5.6702 +  module argument (kernel command line argument as well?), changed
  5.6703 +  dynamically using an ioctl (not yet) or changed by sending the
  5.6704 +  string "Dxxxx" to VCI 1023 (where x is a hex digit).  See the file
  5.6705 +  <file:drivers/atm/ambassador.h> for the meanings of the bits in the
  5.6706 +  mask.
  5.6707 +
  5.6708 +  When active, these messages can have a significant impact on the
  5.6709 +  speed of the driver, and the size of your syslog files! When
  5.6710 +  inactive, they will have only a modest impact on performance.
  5.6711 +
  5.6712 +Madge Horizon [Ultra] (Collage PCI 25 and Collage PCI 155 Client)
  5.6713 +CONFIG_ATM_HORIZON
  5.6714 +  This is a driver for the Horizon chipset ATM adapter cards once
  5.6715 +  produced by Madge Networks Ltd. Say Y (or M to compile as a module
  5.6716 +  named horizon.o) here if you have one of these cards.
  5.6717 +
  5.6718 +Enable debugging messages
  5.6719 +CONFIG_ATM_HORIZON_DEBUG
  5.6720 +  Somewhat useful debugging messages are available. The choice of
  5.6721 +  messages is controlled by a bitmap.  This may be specified as a
  5.6722 +  module argument (kernel command line argument as well?), changed
  5.6723 +  dynamically using an ioctl (not yet) or changed by sending the
  5.6724 +  string "Dxxxx" to VCI 1023 (where x is a hex digit).  See the file
  5.6725 +  <file:drivers/atm/horizon.h> for the meanings of the bits in the
  5.6726 +  mask.
  5.6727 +
  5.6728 +  When active, these messages can have a significant impact on the
  5.6729 +  speed of the driver, and the size of your syslog files! When
  5.6730 +  inactive, they will have only a modest impact on performance.
  5.6731 +
  5.6732 +Interphase ATM PCI x575/x525/x531
  5.6733 +CONFIG_ATM_IA
  5.6734 +  This is a driver for the Interphase (i)ChipSAR adapter cards
  5.6735 +  which include a variety of variants in term of the size of the
  5.6736 +  control memory (128K-1KVC, 512K-4KVC), the size of the packet
  5.6737 +  memory (128K, 512K, 1M), and the PHY type (Single/Multi mode OC3,
  5.6738 +  UTP155, UTP25, DS3 and E3). Go to:
  5.6739 +  	<http://www.iphase.com/products/ClassSheet.cfm?ClassID=ATM>
  5.6740 +  for more info about the cards. Say Y (or M to compile as a module
  5.6741 +  named iphase.o) here if you have one of these cards.
  5.6742 +
  5.6743 +  See the file <file:Documentation/networking/iphase.txt> for further
  5.6744 +  details.
  5.6745 +
  5.6746 +Enable debugging messages
  5.6747 +CONFIG_ATM_IA_DEBUG
  5.6748 +  Somewhat useful debugging messages are available. The choice of
  5.6749 +  messages is controlled by a bitmap. This may be specified as a
  5.6750 +  module argument (kernel command line argument as well?), changed
  5.6751 +  dynamically using an ioctl (Get the debug utility, iadbg, from
  5.6752 +  <ftp://ftp.iphase.com/pub/atm/pci/>).
  5.6753 +
  5.6754 +  See the file <file:drivers/atm/iphase.h> for the meanings of the
  5.6755 +  bits in the mask.
  5.6756 +
  5.6757 +  When active, these messages can have a significant impact on the
  5.6758 +  speed of the driver, and the size of your syslog files! When
  5.6759 +  inactive, they will have only a modest impact on performance.
  5.6760 +
  5.6761 +Efficient Networks Speedstream 3010
  5.6762 +CONFIG_ATM_LANAI
  5.6763 +  Supports ATM cards based on the Efficient Networks "Lanai"
  5.6764 +  chipset such as the Speedstream 3010 and the ENI-25p.  The
  5.6765 +  Speedstream 3060 is currently not supported since we don't
  5.6766 +  have the code to drive the on-board Alcatel DSL chipset (yet).
  5.6767 +
  5.6768 +Linux telephony support
  5.6769 +CONFIG_PHONE
  5.6770 +  Say Y here if you have a telephony card, which for example allows
  5.6771 +  you to use a regular phone for voice-over-IP applications.
  5.6772 +
  5.6773 +  Note: this has nothing to do with modems.  You do not need to say Y
  5.6774 +  here in order to be able to use a modem under Linux.
  5.6775 +
  5.6776 +  This support is also available as a module.  If you want to compile
  5.6777 +  it as a module, say M here and read
  5.6778 +  <file:Documentation/modules.txt>.  The module will be called
  5.6779 +  phonedev.o.
  5.6780 +
  5.6781 +Compaq Smart Array support
  5.6782 +CONFIG_BLK_CPQ_CISS_DA
  5.6783 +  This is the driver for Compaq Smart Array 5xxx controllers.
  5.6784 +  Everyone using these boards should say Y here.
  5.6785 +  See <file:Documentation/cciss.txt> for the current list of
  5.6786 +  boards supported by this driver, and for further information
  5.6787 +  on the use of this driver.
  5.6788 +
  5.6789 +  This driver is also available as a module ( = code which can be
  5.6790 +  inserted in and removed from the running kernel whenever you want).
  5.6791 +  If you want to compile it as a module, say M here and read
  5.6792 +  <file:Documentation/modules.txt>. The module will be called
  5.6793 +  cciss.o
  5.6794 +
  5.6795 +SCSI tape drive support for Smart Array 5xxx
  5.6796 +CONFIG_CISS_SCSI_TAPE
  5.6797 +  When enabled (Y), this option allows SCSI tape drives and SCSI medium
  5.6798 +  changers (tape robots) to be accessed via a Compaq 5xxx array
  5.6799 +  controller.  (See Documentation/cciss.txt for more details.)
  5.6800 +
  5.6801 +  "SCSI support" and "SCSI tape support" must also be enabled for this
  5.6802 +  option to work.
  5.6803 +
  5.6804 +  When this option is disabled (N), the SCSI portion of the driver
  5.6805 +  is not compiled.
  5.6806 +
  5.6807 +QuickNet Internet LineJack/PhoneJack support
  5.6808 +CONFIG_PHONE_IXJ
  5.6809 +  Say M if you have a telephony card manufactured by Quicknet
  5.6810 +  Technologies, Inc.  These include the Internet PhoneJACK and
  5.6811 +  Internet LineJACK Telephony Cards. You will get a module called
  5.6812 +  ixj.o.
  5.6813 +
  5.6814 +  For the ISA versions of these products, you can configure the
  5.6815 +  cards using the isapnp tools (pnpdump/isapnp) or you can use the
  5.6816 +  isapnp support.  Please read <file:Documentation/telephony/ixj.txt>.
  5.6817 +
  5.6818 +  For more information on these cards, see Quicknet's web site at:
  5.6819 +  <http://www.quicknet.net/>.
  5.6820 +
  5.6821 +  If you do not have any Quicknet telephony cards, you can safely
  5.6822 +  say N here.
  5.6823 +
  5.6824 +QuickNet Internet LineJack/PhoneJack PCMCIA support
  5.6825 +CONFIG_PHONE_IXJ_PCMCIA
  5.6826 +  Say Y here to configure in PCMCIA service support for the Quicknet
  5.6827 +  cards manufactured by Quicknet Technologies, Inc.  This builds an
  5.6828 +  additional support module for the PCMCIA version of the card.
  5.6829 +
  5.6830 +FORE Systems 200E-series
  5.6831 +CONFIG_ATM_FORE200E_MAYBE
  5.6832 +  This is a driver for the FORE Systems 200E-series ATM adapter
  5.6833 +  cards. It simultaneously supports PCA-200E and SBA-200E models
  5.6834 +  on PCI and SBUS hosts. Say Y (or M to compile as a module
  5.6835 +  named fore_200e.o) here if you have one of these ATM adapters.
  5.6836 +
  5.6837 +  Note that the driver will actually be compiled only if you
  5.6838 +  additionally enable the support for PCA-200E and/or SBA-200E
  5.6839 +  cards.
  5.6840 +
  5.6841 +  See the file <file:Documentation/networking/fore200e.txt> for
  5.6842 +  further details.
  5.6843 +
  5.6844 +Enable PCA-200E card support on PCI-based hosts
  5.6845 +CONFIG_ATM_FORE200E_PCA
  5.6846 +  Say Y here if you want your PCA-200E cards to be probed.
  5.6847 +
  5.6848 +Use default PCA-200E firmware
  5.6849 +CONFIG_ATM_FORE200E_PCA_DEFAULT_FW
  5.6850 +  Use the default PCA-200E firmware data shipped with the driver.
  5.6851 +
  5.6852 +  Normal users do not have to deal with the firmware stuff, so
  5.6853 +  they should say Y here.
  5.6854 +
  5.6855 +Pathname of user-supplied binary firmware
  5.6856 +CONFIG_ATM_FORE200E_PCA_FW
  5.6857 +  This defines the pathname of an alternative PCA-200E binary
  5.6858 +  firmware image supplied by the user. This pathname may be
  5.6859 +  absolute or relative to the drivers/atm directory.
  5.6860 +
  5.6861 +  The driver comes with an adequate firmware image, so normal users do
  5.6862 +  not have to supply an alternative one. They just say Y to "Use
  5.6863 +  default PCA-200E firmware" instead.
  5.6864 +
  5.6865 +Enable SBA-200E card support on SBUS-based hosts
  5.6866 +CONFIG_ATM_FORE200E_SBA
  5.6867 +  Say Y here if you want your SBA-200E cards to be probed.
  5.6868 +
  5.6869 +Use default SBA-200E firmware
  5.6870 +CONFIG_ATM_FORE200E_SBA_DEFAULT_FW
  5.6871 +  Use the default SBA-200E firmware data shipped with the driver.
  5.6872 +
  5.6873 +  Normal users do not have to deal with the firmware stuff, so
  5.6874 +  they should say Y here.
  5.6875 +
  5.6876 +Pathname of user-supplied binary firmware
  5.6877 +CONFIG_ATM_FORE200E_SBA_FW
  5.6878 +  This defines the pathname of an alternative SBA-200E binary
  5.6879 +  firmware image supplied by the user. This pathname may be
  5.6880 +  absolute or relative to the drivers/atm directory.
  5.6881 +
  5.6882 +  The driver comes with an adequate firmware image, so normal users do
  5.6883 +  not have to supply an alternative one. They just say Y to "Use
  5.6884 +  default SBA-200E firmware", above.
  5.6885 +
  5.6886 +Maximum number of tx retries
  5.6887 +CONFIG_ATM_FORE200E_TX_RETRY
  5.6888 +  Specifies the number of times the driver attempts to transmit
  5.6889 +  a message before giving up, if the transmit queue of the ATM card
  5.6890 +  is transiently saturated.
  5.6891 +
  5.6892 +  Saturation of the transmit queue may occur only under extreme
  5.6893 +  conditions, e.g. when a fast host continuously submits very small
  5.6894 +  frames (<64 bytes) or raw AAL0 cells (48 bytes) to the ATM adapter.
  5.6895 +
  5.6896 +  Note that under common conditions, it is unlikely that you encounter
  5.6897 +  a saturation of the transmit queue, so the retry mechanism never
  5.6898 +  comes into play.
  5.6899 +
  5.6900 +Debugging level (0-3)
  5.6901 +CONFIG_ATM_FORE200E_DEBUG
  5.6902 +  Specifies the level of debugging messages issued by the driver.
  5.6903 +  The verbosity of the driver increases with the value of this
  5.6904 +  parameter.
  5.6905 +
  5.6906 +  When active, these messages can have a significant impact on
  5.6907 +  the performances of the driver, and the size of your syslog files!
  5.6908 +  Keep the debugging level to 0 during normal operations.
  5.6909 +
  5.6910 +PPP over ATM
  5.6911 +CONFIG_PPPOATM
  5.6912 +  Support PPP (Point to Point Protocol) encapsulated in ATM frames.
  5.6913 +  This implementation does not yet comply with section 8 of RFC2364,
  5.6914 +  which can lead to bad results idf the ATM peer loses state and 
  5.6915 +  changes its encapsulation unilaterally.
  5.6916 +
  5.6917 +Fusion MPT device support
  5.6918 +CONFIG_FUSION
  5.6919 +  LSI Logic Fusion(TM) Message Passing Technology (MPT) device support
  5.6920 +  provides high performance SCSI host initiator, and LAN [1] interface
  5.6921 +  services to a host system.  The Fusion architecture is capable of
  5.6922 +  duplexing these protocols on high-speed Fibre Channel
  5.6923 +  (up to 2 GHz x 2 ports = 4 GHz) and parallel SCSI (up to Ultra-320)
  5.6924 +  physical medium.
  5.6925 +
  5.6926 +          [1] LAN is not supported on parallel SCSI medium.
  5.6927 +
  5.6928 +  These drivers require a Fusion MPT compatible PCI adapter installed
  5.6929 +  in the host system.  MPT adapters contain specialized I/O processors
  5.6930 +  to handle I/O workload, and more importantly to offload this work
  5.6931 +  from the host CPU(s).
  5.6932 +
  5.6933 +  If you have Fusion MPT hardware and want to use it, you can say
  5.6934 +  Y or M here to add MPT (base + ScsiHost) drivers.
  5.6935 +    <Y> = build lib (fusion.o), and link [static] into the kernel [2]
  5.6936 +          proper
  5.6937 +    <M> = compiled as [dynamic] modules [3] named: (mptbase.o,
  5.6938 +          mptscsih.o)
  5.6939 +
  5.6940 +          [2] In order enable capability to boot the linux kernel
  5.6941 +              natively from a Fusion MPT target device, you MUST
  5.6942 +               answer Y here! (currently requires CONFIG_BLK_DEV_SD)
  5.6943 +          [3] This support is also available as a module ( = code
  5.6944 +              which can be inserted in and removed from the running
  5.6945 +              kernel whenever you want).  If you want to compile as
  5.6946 +              modules, say M here and read
  5.6947 +              <file:Documentation/modules.txt>.
  5.6948 +
  5.6949 +  If unsure, say N.
  5.6950 +
  5.6951 +  If you say Y or M here you will get a choice of these
  5.6952 +  additional protocol and support module options:         Module Name:
  5.6953 +    <M>   Enhanced SCSI error reporting                     (isense.o)
  5.6954 +    <M>   Fusion MPT misc device (ioctl) driver             (mptctl.o)
  5.6955 +    <M>   Fusion MPT LAN driver                             (mptlan.o)
  5.6956 +
  5.6957 +  ---
  5.6958 +  Fusion MPT is trademark of LSI Logic Corporation, and its
  5.6959 +  architecture is based on LSI Logic's Message Passing Interface (MPI)
  5.6960 +  specification.
  5.6961 +
  5.6962 +Fusion MPT enhanced SCSI error reporting [optional] module
  5.6963 +CONFIG_FUSION_ISENSE
  5.6964 +  The isense module (roughly stands for Interpret SENSE data) is
  5.6965 +  completely optional.  It simply provides extra English readable
  5.6966 +  strings in SCSI Error Report(s) that might be generated from the
  5.6967 +  Fusion MPT SCSI Host driver, for example when a target device
  5.6968 +  returns a SCSI check condition on a I/O.  Without this module
  5.6969 +  loaded you might see:
  5.6970 +
  5.6971 +    SCSI Error Report =-=-= (ioc0,scsi5:0)
  5.6972 +      SCSI_Status=02h (CHECK_CONDITION)
  5.6973 +      Original_CDB[]: 2A 00 00 00 00 41 00 00 02 00
  5.6974 +      SenseData[12h]: 70 00 02 00 00 00 00 0A 00 00 00 00 04 02 02 00 00 00
  5.6975 +      SenseKey=2h (NOT READY); FRU=02h
  5.6976 +      ASC/ASCQ=29h/00h
  5.6977 +
  5.6978 +  Where otherwise, if this module had been loaded, you would see:
  5.6979 +
  5.6980 +    SCSI Error Report =-=-= (ioc0,scsi5:0)
  5.6981 +      SCSI_Status=02h (CHECK_CONDITION)
  5.6982 +      Original_CDB[]: 2A 00 00 00 00 41 00 00 02 00 - "WRITE(10)"
  5.6983 +      SenseData[12h]: 70 00 02 00 00 00 00 0A 00 00 00 00 04 02 02 00 00 00
  5.6984 +      SenseKey=2h (NOT READY); FRU=02h
  5.6985 +      ASC/ASCQ=29h/00h "LOGICAL UNIT NOT READY, INITIALIZING CMD. REQUIRED"
  5.6986 +
  5.6987 +  Say M for "Enhanced SCSI error reporting" to compile this optional module,
  5.6988 +  creating a driver named: isense.o.
  5.6989 +
  5.6990 +  NOTE: Support for building this feature into the kernel is not
  5.6991 +  available, due to kernel size considerations.
  5.6992 +
  5.6993 +Fusion MPT misc device (ioctl) driver [optional] module
  5.6994 +CONFIG_FUSION_CTL
  5.6995 +  The Fusion MPT misc device driver provides specialized control
  5.6996 +  of MPT adapters via system ioctl calls.  Use of ioctl calls to
  5.6997 +  the MPT driver requires that you create and use a misc device
  5.6998 +  node ala:
  5.6999 +    mknod /dev/mptctl c 10 240
  5.7000 +
  5.7001 +  One use of this ioctl interface is to perform an upgrade (reflash)
  5.7002 +  of the MPT adapter firmware.  Refer to readme file(s) distributed
  5.7003 +  with the Fusion MPT linux driver for additional details.
  5.7004 +
  5.7005 +  If enabled by saying M to this, a driver named: mptctl.o
  5.7006 +  will be compiled.
  5.7007 +
  5.7008 +  If unsure whether you really want or need this, say N.
  5.7009 +
  5.7010 +Fusion MPT LAN driver [optional]
  5.7011 +CONFIG_FUSION_LAN
  5.7012 +  This module supports LAN IP traffic over Fibre Channel port(s)
  5.7013 +  on Fusion MPT compatible hardware (LSIFC9xx chips).
  5.7014 +  The physical interface used is defined in RFC 2625.
  5.7015 +  Please refer to that document for details.
  5.7016 +
  5.7017 +  Installing this driver requires the knowledge to configure and
  5.7018 +  activate a new network interface, "fc0", using standard Linux tools.
  5.7019 +
  5.7020 +  If enabled by saying M to this, a driver named: mptlan.o
  5.7021 +  will be compiled.
  5.7022 +
  5.7023 +  If unsure whether you really want or need this, say N.
  5.7024 +
  5.7025 +  NOTES: This feature is NOT available nor supported for linux-2.2.x
  5.7026 +  kernels.  You must be building a linux-2.3.x or linux-2.4.x kernel
  5.7027 +  in order to configure this option.
  5.7028 +  Support for building this feature into the linux kernel is not
  5.7029 +  yet available.
  5.7030 +
  5.7031 +SCSI support
  5.7032 +CONFIG_SCSI
  5.7033 +  If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
  5.7034 +  any other SCSI device under Linux, say Y and make sure that you know
  5.7035 +  the name of your SCSI host adapter (the card inside your computer
  5.7036 +  that "speaks" the SCSI protocol, also called SCSI controller),
  5.7037 +  because you will be asked for it.
  5.7038 +
  5.7039 +  You also need to say Y here if you want support for the parallel
  5.7040 +  port version of the 100 MB IOMEGA ZIP drive.
  5.7041 +
  5.7042 +  This driver is also available as a module ( = code which can be
  5.7043 +  inserted in and removed from the running kernel whenever you want).
  5.7044 +  The module will be called scsi_mod.o.  If you want to compile it as
  5.7045 +  a module, say M here and read <file:Documentation/modules.txt> and
  5.7046 +  <file:Documentation/scsi.txt>.  However, do not compile this as a
  5.7047 +  module if your root file system (the one containing the directory /)
  5.7048 +  is located on a SCSI device.
  5.7049 +
  5.7050 +SCSI disk support
  5.7051 +CONFIG_BLK_DEV_SD
  5.7052 +  If you want to use a SCSI hard disk or the SCSI or parallel port
  5.7053 +  version of the IOMEGA ZIP drive under Linux, say Y and read the
  5.7054 +  SCSI-HOWTO, the Disk-HOWTO and the Multi-Disk-HOWTO, available from
  5.7055 +  <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
  5.7056 +  CD-ROMs.
  5.7057 +
  5.7058 +  This driver is also available as a module ( = code which can be
  5.7059 +  inserted in and removed from the running kernel whenever you want).
  5.7060 +  The module will be called sd_mod.o.  If you want to compile it as a
  5.7061 +  module, say M here and read <file:Documentation/modules.txt> and
  5.7062 +  <file:Documentation/scsi.txt>.  Do not compile this driver as a
  5.7063 +  module if your root file system (the one containing the directory /)
  5.7064 +  is located on a SCSI disk. In this case, do not compile the driver
  5.7065 +  for your SCSI host adapter (below) as a module either.
  5.7066 +
  5.7067 +Maximum number of SCSI disks that can be loaded as modules
  5.7068 +CONFIG_SD_EXTRA_DEVS
  5.7069 +  This controls the amount of additional space allocated in tables for
  5.7070 +  drivers that are loaded as modules after the kernel is booted.  In
  5.7071 +  the event that the SCSI core itself was loaded as a module, this
  5.7072 +  value is the number of additional disks that can be loaded after the
  5.7073 +  first host driver is loaded.
  5.7074 +
  5.7075 +  Admittedly this isn't pretty, but there are tons of race conditions
  5.7076 +  involved with resizing the internal arrays on the fly.  Someday this
  5.7077 +  flag will go away, and everything will work automatically.
  5.7078 +
  5.7079 +  If you don't understand what's going on, go with the default.
  5.7080 +
  5.7081 +Maximum number of SCSI tapes that can be loaded as modules
  5.7082 +CONFIG_ST_EXTRA_DEVS
  5.7083 +  This controls the amount of additional space allocated in tables for
  5.7084 +  drivers that are loaded as modules after the kernel is booted.  In
  5.7085 +  the event that the SCSI core itself was loaded as a module, this
  5.7086 +  value is the number of additional tapes that can be loaded after the
  5.7087 +  first host driver is loaded.
  5.7088 +
  5.7089 +  Admittedly this isn't pretty, but there are tons of race conditions
  5.7090 +  involved with resizing the internal arrays on the fly.  Someday this
  5.7091 +  flag will go away, and everything will work automatically.
  5.7092 +
  5.7093 +  If you don't understand what's going on, go with the default.
  5.7094 +
  5.7095 +SCSI tape support
  5.7096 +CONFIG_CHR_DEV_ST
  5.7097 +  If you want to use a SCSI tape drive under Linux, say Y and read the
  5.7098 +  SCSI-HOWTO, available from
  5.7099 +  <http://www.tldp.org/docs.html#howto>, and
  5.7100 +  <file:drivers/scsi/README.st> in the kernel source.  This is NOT for
  5.7101 +  SCSI CD-ROMs.
  5.7102 +
  5.7103 +  This driver is also available as a module ( = code which can be
  5.7104 +  inserted in and removed from the running kernel whenever you want).
  5.7105 +  The module will be called st.o. If you want to compile it as a
  5.7106 +  module, say M here and read <file:Documentation/modules.txt> and
  5.7107 +  <file:Documentation/scsi.txt>.
  5.7108 +
  5.7109 +OnStream SC-x0 SCSI tape support
  5.7110 +CONFIG_CHR_DEV_OSST
  5.7111 +  The OnStream SC-x0 SCSI tape drives can not be driven by the
  5.7112 +  standard st driver, but instead need this special osst driver and
  5.7113 +  use the  /dev/osstX char device nodes (major 206).  Via usb-storage
  5.7114 +  and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives
  5.7115 +  as well.  Note that there is also a second generation of OnStream
  5.7116 +  tape drives (ADR-x0) that supports the standard SCSI-2 commands for
  5.7117 +  tapes (QIC-157) and can be driven by the standard driver st.
  5.7118 +  For more information, you may have a look at the SCSI-HOWTO
  5.7119 +  <http://www.tldp.org/docs.html#howto>  and
  5.7120 +  <file:drivers/scsi/README.osst>  in the kernel source.
  5.7121 +  More info on the OnStream driver may be found on
  5.7122 +  <http://linux1.onstream.nl/test/>
  5.7123 +  Please also have a look at the standard st docu, as most of it
  5.7124 +  applies to osst as well.
  5.7125 +
  5.7126 +  This driver is also available as a module ( = code which can be
  5.7127 +  inserted in and removed from the running kernel whenever you want).
  5.7128 +  The module will be called osst.o. If you want to compile it as a
  5.7129 +  module, say M here and read <file:Documentation/modules.txt> and
  5.7130 +  <file:Documentation/scsi.txt>.
  5.7131 +
  5.7132 +SCSI CD-ROM support
  5.7133 +CONFIG_BLK_DEV_SR
  5.7134 +  If you want to use a SCSI CD-ROM under Linux, say Y and read the
  5.7135 +  SCSI-HOWTO and the CD-ROM-HOWTO at
  5.7136 +  <http://www.tldp.org/docs.html#howto>. Also make sure to say Y
  5.7137 +  or M to "ISO 9660 CD-ROM file system support" later.
  5.7138 +
  5.7139 +  This driver is also available as a module ( = code which can be
  5.7140 +  inserted in and removed from the running kernel whenever you want).
  5.7141 +  The module will be called sr_mod.o. If you want to compile it as a
  5.7142 +  module, say M here and read <file:Documentation/modules.txt> and
  5.7143 +  <file:Documentation/scsi.txt>.
  5.7144 +
  5.7145 +Maximum number of CD-ROM devices that can be loaded as modules
  5.7146 +CONFIG_SR_EXTRA_DEVS
  5.7147 +  This controls the amount of additional space allocated in tables for
  5.7148 +  drivers that are loaded as modules after the kernel is booted. In
  5.7149 +  the event that the SCSI core itself was loaded as a module, this
  5.7150 +  value is the number of additional CD-ROMs that can be loaded after
  5.7151 +  the first host driver is loaded.
  5.7152 +
  5.7153 +  Admittedly this isn't pretty, but there are tons of race conditions
  5.7154 +  involved with resizing the internal arrays on the fly.  Someday this
  5.7155 +  flag will go away, and everything will work automatically.
  5.7156 +
  5.7157 +  If you don't understand what's going on, go with the default.
  5.7158 +
  5.7159 +Enable vendor-specific extensions (for SCSI CD-ROM)
  5.7160 +CONFIG_BLK_DEV_SR_VENDOR
  5.7161 +  This enables the usage of vendor specific SCSI commands. This is
  5.7162 +  required to support multisession CDs with old NEC/TOSHIBA cdrom
  5.7163 +  drives (and HP Writers). If you have such a drive and get the first
  5.7164 +  session only, try saying Y here; everybody else says N.
  5.7165 +
  5.7166 +SCSI generic support
  5.7167 +CONFIG_CHR_DEV_SG
  5.7168 +  If you want to use SCSI scanners, synthesizers or CD-writers or just
  5.7169 +  about anything having "SCSI" in its name other than hard disks,
  5.7170 +  CD-ROMs or tapes, say Y here. These won't be supported by the kernel
  5.7171 +  directly, so you need some additional software which knows how to
  5.7172 +  talk to these devices using the SCSI protocol:
  5.7173 +
  5.7174 +  For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
  5.7175 +  writer software look at Cdrtools
  5.7176 +  (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
  5.7177 +  and for burning a "disk at once": CDRDAO
  5.7178 +  (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
  5.7179 +  quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
  5.7180 +  For other devices, it's possible that you'll have to write the
  5.7181 +  driver software yourself. Please read the file
  5.7182 +  <file:Documentation/scsi-generic.txt> for more information.
  5.7183 +
  5.7184 +  If you want to compile this as a module ( = code which can be
  5.7185 +  inserted in and removed from the running kernel whenever you want),
  5.7186 +  say M here and read <file:Documentation/modules.txt> and
  5.7187 +  <file:Documentation/scsi.txt>. The module will be called sg.o. If unsure,
  5.7188 +  say N.
  5.7189 +
  5.7190 +Probe all LUNs on each SCSI device
  5.7191 +CONFIG_SCSI_MULTI_LUN
  5.7192 +  If you have a SCSI device that supports more than one LUN (Logical
  5.7193 +  Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
  5.7194 +  can say Y here to force the SCSI driver to probe for multiple LUNs.
  5.7195 +  A SCSI device with multiple LUNs acts logically like multiple SCSI
  5.7196 +  devices. The vast majority of SCSI devices have only one LUN, and
  5.7197 +  so most people can say N here and should in fact do so, because it
  5.7198 +  is safer.
  5.7199 +
  5.7200 +Verbose SCSI error reporting (kernel size +=12K)
  5.7201 +CONFIG_SCSI_CONSTANTS
  5.7202 +  The error messages regarding your SCSI hardware will be easier to
  5.7203 +  understand if you say Y here; it will enlarge your kernel by about
  5.7204 +  12 KB. If in doubt, say Y.
  5.7205 +
  5.7206 +SCSI logging facility
  5.7207 +CONFIG_SCSI_LOGGING
  5.7208 +  This turns on a logging facility that can be used to debug a number
  5.7209 +  of SCSI related problems.
  5.7210 +
  5.7211 +  If you say Y here, no logging output will appear by default, but you
  5.7212 +  can enable logging by saying Y to "/proc file system support" and
  5.7213 +  "Sysctl support" below and executing the command
  5.7214 +
  5.7215 +     echo "scsi log token [level]" > /proc/scsi/scsi
  5.7216 +
  5.7217 +  at boot time after the /proc file system has been mounted.
  5.7218 +
  5.7219 +  There are a number of things that can be used for 'token' (you can
  5.7220 +  find them in the source: <file:drivers/scsi/scsi.c>), and this
  5.7221 +  allows you to select the types of information you want, and the
  5.7222 +  level allows you to select the level of verbosity.
  5.7223 +
  5.7224 +  If you say N here, it may be harder to track down some types of SCSI
  5.7225 +  problems. If you say Y here your kernel will be somewhat larger, but
  5.7226 +  there should be no noticeable performance impact as long as you have
  5.7227 +  logging turned off.
  5.7228 +
  5.7229 +SGI WD93C93 SCSI Driver
  5.7230 +CONFIG_SCSI_SGIWD93
  5.7231 +  Say Y here to support the on-board WD93C93 SCSI controller found (a)
  5.7232 +  on the Indigo2 and other MIPS-based SGI machines, and (b) on ARCS
  5.7233 +  ARM-based machines.
  5.7234 +
  5.7235 +DEC NCR53C94 SCSI Driver
  5.7236 +CONFIG_SCSI_DECNCR
  5.7237 +  Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
  5.7238 +  based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
  5.7239 +
  5.7240 +AdvanSys SCSI support
  5.7241 +CONFIG_SCSI_ADVANSYS
  5.7242 +  This is a driver for all SCSI host adapters manufactured by
  5.7243 +  AdvanSys. It is documented in the kernel source in
  5.7244 +  <file:drivers/scsi/advansys.c>.
  5.7245 +
  5.7246 +  This driver is also available as a module ( = code which can be
  5.7247 +  inserted in and removed from the running kernel whenever you want).
  5.7248 +  If you want to compile it as a module, say M here and read
  5.7249 +  <file:Documentation/modules.txt>.  The module will be called
  5.7250 +  advansys.o.
  5.7251 +
  5.7252 +Adaptec AHA152X/2825 support
  5.7253 +CONFIG_SCSI_AHA152X
  5.7254 +  This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
  5.7255 +  SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
  5.7256 +  must be manually specified in this case.
  5.7257 +
  5.7258 +  It is explained in section 3.3 of the SCSI-HOWTO, available from
  5.7259 +  <http://www.tldp.org/docs.html#howto>. You might also want to
  5.7260 +  read the file <file:drivers/scsi/README.aha152x>.
  5.7261 +
  5.7262 +  This driver is also available as a module ( = code which can be
  5.7263 +  inserted in and removed from the running kernel whenever you want).
  5.7264 +  The module will be called aha152x.o. If you want to compile it as a
  5.7265 +  module, say M here and read <file:Documentation/modules.txt>.
  5.7266 +
  5.7267 +Adaptec AHA1542 support
  5.7268 +CONFIG_SCSI_AHA1542
  5.7269 +  This is support for a SCSI host adapter.  It is explained in section
  5.7270 +  3.4 of the SCSI-HOWTO, available from
  5.7271 +  <http://www.tldp.org/docs.html#howto>.  Note that Trantor was
  5.7272 +  purchased by Adaptec, and some former Trantor products are being
  5.7273 +  sold under the Adaptec name.  If it doesn't work out of the box, you
  5.7274 +  may have to change some settings in <file:drivers/scsi/aha1542.h>.
  5.7275 +
  5.7276 +  If you want to compile this as a module ( = code which can be
  5.7277 +  inserted in and removed from the running kernel whenever you want),
  5.7278 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.7279 +  will be called aha1542.o.
  5.7280 +
  5.7281 +Adaptec AHA1740 support
  5.7282 +CONFIG_SCSI_AHA1740
  5.7283 +  This is support for a SCSI host adapter.  It is explained in section
  5.7284 +  3.5 of the SCSI-HOWTO, available from
  5.7285 +  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
  5.7286 +  of the box, you may have to change some settings in
  5.7287 +  <file:drivers/scsi/aha1740.h>.
  5.7288 +
  5.7289 +  This driver is also available as a module ( = code which can be
  5.7290 +  inserted in and removed from the running kernel whenever you want).
  5.7291 +  The module will be called aha1740.o.  If you want to compile it as a
  5.7292 +  module, say M here and read <file:Documentation/modules.txt>.
  5.7293 +
  5.7294 +Adaptec AIC7xxx support
  5.7295 +CONFIG_SCSI_AIC7XXX
  5.7296 +  This driver supports all of Adaptec's PCI based SCSI controllers
  5.7297 +  (not the hardware RAID controllers though) as well as the aic7770
  5.7298 +  based EISA and VLB SCSI controllers (the 274x and 284x series).
  5.7299 +  This is an Adaptec sponsored driver written by Justin Gibbs.  It is
  5.7300 +  intended to replace the previous aic7xxx driver maintained by Doug
  5.7301 +  Ledford since Doug is no longer maintaining that driver.
  5.7302 +
  5.7303 +  If you want to compile the driver as a module ( = code which can be
  5.7304 +  inserted in and removed from the running kernel whenever you want),
  5.7305 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.7306 +  will be called aic7xxx.o.
  5.7307 +
  5.7308 +Adaptec I2O RAID support
  5.7309 +CONFIG_SCSI_DPT_I2O
  5.7310 +  This driver supports all of Adaptec's I2O based RAID controllers as 
  5.7311 +  well as the DPT SmartRaid V cards.  This is an Adaptec maintained
  5.7312 +  driver by Deanna Bonds.  See <file:drivers/scsi/README.dpti>.
  5.7313 +
  5.7314 +  This driver is also available as a module ( = code which can be
  5.7315 +  inserted in and removed from the running kernel whenever you want).
  5.7316 +  If you want to compile it as a module, say M here and read
  5.7317 +  <file:Documentation/modules.txt>.  The module will be called
  5.7318 +  dpt_i2o.o.
  5.7319 +
  5.7320 +Default number of TCQ commands per device
  5.7321 +CONFIG_AIC7XXX_CMDS_PER_DEVICE
  5.7322 +  Specify the number of commands you would like to allocate per SCSI
  5.7323 +  device when Tagged Command Queueing (TCQ) is enabled on that device.
  5.7324 +
  5.7325 +  This is an upper bound value for the number of tagged transactions
  5.7326 +  to be used for any device.  The aic7xxx driver will automatically
  5.7327 +  vary this number based on device behaviour.  For devices with a
  5.7328 +  fixed maximum, the driver will eventually lock to this maximum
  5.7329 +  and display a console message indicating this value.
  5.7330 +
  5.7331 +  Note: Unless you experience some type of device failure, the default
  5.7332 +	value, no enforced limit, should work for you.
  5.7333 +
  5.7334 +  Default: 253
  5.7335 +
  5.7336 +Delay in seconds after SCSI bus reset
  5.7337 +CONFIG_AIC7XXX_RESET_DELAY_MS
  5.7338 +  The number of milliseconds to delay after an initial bus reset.
  5.7339 +  The bus settle delay following all error recovery actions is
  5.7340 +  dictated by the SCSI layer and is not affected by this value.
  5.7341 +
  5.7342 +  Default: 15000 (15 seconds)
  5.7343 +
  5.7344 +Build Adapter Firmware with Kernel Build
  5.7345 +CONFIG_AIC7XXX_BUILD_FIRMWARE
  5.7346 +  This option should only be enabled if you are modifying the firmware
  5.7347 +  source to the aic7xxx driver and wish to have the generated firmware
  5.7348 +  include files updated during a normal kernel build.  The assembler
  5.7349 +  for the firmware requires lex and yacc or their equivalents, as well
  5.7350 +  as the db v1 library.  You may have to install additional packages
  5.7351 +  or modify the assembler make file or the files it includes if your
  5.7352 +  build environment is different than that of the author.
  5.7353 +
  5.7354 +Old Adaptec AIC7xxx support
  5.7355 +CONFIG_SCSI_AIC7XXX_OLD
  5.7356 +  WARNING This driver is an older aic7xxx driver and is no longer
  5.7357 +  under active development.  Adaptec, Inc. is writing a new driver to
  5.7358 +  take the place of this one, and it is recommended that whenever
  5.7359 +  possible, people should use the new Adaptec written driver instead
  5.7360 +  of this one.  This driver will eventually be phased out entirely.
  5.7361 +
  5.7362 +  This is support for the various aic7xxx based Adaptec SCSI
  5.7363 +  controllers. These include the 274x EISA cards; 284x VLB cards;
  5.7364 +  2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
  5.7365 +  motherboard based SCSI controllers from Adaptec. It does not support
  5.7366 +  the AAA-13x RAID controllers from Adaptec, nor will it likely ever
  5.7367 +  support them. It does not support the 2920 cards from Adaptec that
  5.7368 +  use the Future Domain SCSI controller chip. For those cards, you
  5.7369 +  need the "Future Domain 16xx SCSI support" driver.
  5.7370 +
  5.7371 +  In general, if the controller is based on an Adaptec SCSI controller
  5.7372 +  chip from the aic777x series or the aic78xx series, this driver
  5.7373 +  should work. The only exception is the 7810 which is specifically
  5.7374 +  not supported (that's the RAID controller chip on the AAA-13x
  5.7375 +  cards).
  5.7376 +
  5.7377 +  Note that the AHA2920 SCSI host adapter is *not* supported by this
  5.7378 +  driver; choose "Future Domain 16xx SCSI support" instead if you have
  5.7379 +  one of those.
  5.7380 +
  5.7381 +  Information on the configuration options for this controller can be
  5.7382 +  found by checking the help file for each of the available
  5.7383 +  configuration options. You should read
  5.7384 +  <file:drivers/scsi/aic7xxx_old/README.aic7xxx> at a minimum before
  5.7385 +  contacting the maintainer with any questions.  The SCSI-HOWTO,
  5.7386 +  available from <http://www.tldp.org/docs.html#howto>, can also
  5.7387 +  be of great help.
  5.7388 +
  5.7389 +  If you want to compile this driver as a module ( = code which can be
  5.7390 +  inserted in and removed from the running kernel whenever you want),
  5.7391 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.7392 +  will be called aic7xxx_old.o.
  5.7393 +
  5.7394 +Enable tagged command queueing (TCQ) by default
  5.7395 +CONFIG_AIC7XXX_OLD_TCQ_ON_BY_DEFAULT
  5.7396 +  This option causes the aic7xxx driver to attempt to use Tagged
  5.7397 +  Command Queueing (TCQ) on all devices that claim to support it.
  5.7398 +
  5.7399 +  TCQ is a feature of SCSI-2 which improves performance: the host
  5.7400 +  adapter can send several SCSI commands to a device's queue even if
  5.7401 +  previous commands haven't finished yet.  Because the device is
  5.7402 +  intelligent, it can optimize its operations (like head positioning)
  5.7403 +  based on its own request queue.  Not all devices implement this
  5.7404 +  correctly.
  5.7405 +
  5.7406 +  If you say Y here, you can still turn off TCQ on troublesome devices
  5.7407 +  with the use of the tag_info boot parameter.  See the file
  5.7408 +  <file:drivers/scsi/README.aic7xxx> for more information on that and
  5.7409 +  other aic7xxx setup commands.  If this option is turned off, you may
  5.7410 +  still enable TCQ on known good devices by use of the tag_info boot
  5.7411 +  parameter.
  5.7412 +
  5.7413 +  If you are unsure about your devices then it is safest to say N
  5.7414 +  here.
  5.7415 +
  5.7416 +  However, TCQ can increase performance on some hard drives by as much
  5.7417 +  as 50% or more, so it is recommended that if you say N here, you
  5.7418 +  should at least read the <file:drivers/scsi/README.aic7xxx> file so
  5.7419 +  you will know how to enable this option manually should your drives
  5.7420 +  prove to be safe in regards to TCQ.
  5.7421 +
  5.7422 +  Conversely, certain drives are known to lock up or cause bus resets
  5.7423 +  when TCQ is enabled on them.  If you have a Western Digital
  5.7424 +  Enterprise SCSI drive for instance, then don't even bother to enable
  5.7425 +  TCQ on it as the drive will become unreliable, and it will actually
  5.7426 +  reduce performance.
  5.7427 +
  5.7428 +Default number of TCQ commands per device
  5.7429 +CONFIG_AIC7XXX_OLD_CMDS_PER_DEVICE
  5.7430 +  Specify the number of commands you would like to allocate per SCSI
  5.7431 +  device when Tagged Command Queueing (TCQ) is enabled on that device.
  5.7432 +
  5.7433 +  Reasonable figures are in the range of 8 to 24 commands per device,
  5.7434 +  but depending on hardware could be increased or decreased from that
  5.7435 +  figure. If the number is too high for any particular device, the
  5.7436 +  driver will automatically compensate usually after only 10 minutes
  5.7437 +  of uptime. It will not hinder performance if some of your devices
  5.7438 +  eventually have their command depth reduced, but is a waste of
  5.7439 +  memory if all of your devices end up reducing this number down to a
  5.7440 +  more reasonable figure.
  5.7441 +
  5.7442 +  NOTE: Certain very broken drives are known to lock up when given
  5.7443 +  more commands than they like to deal with. Quantum Fireball drives
  5.7444 +  are the most common in this category. For the Quantum Fireball
  5.7445 +  drives it is suggested to use no more than 8 commands per device.
  5.7446 +
  5.7447 +  Default: 8
  5.7448 +
  5.7449 +Collect statistics to report in /proc
  5.7450 +CONFIG_AIC7XXX_OLD_PROC_STATS
  5.7451 +  This option tells the driver to keep track of how many commands have
  5.7452 +  been sent to each particular device and report that information to
  5.7453 +  the user via the /proc/scsi/aic7xxx/n file, where n is the number of
  5.7454 +  the aic7xxx controller you want the information on. This adds a
  5.7455 +  small amount of overhead to each and every SCSI command the aic7xxx
  5.7456 +  driver handles, so if you aren't really interested in this
  5.7457 +  information, it is best to leave it disabled. This will only work if
  5.7458 +  you also say Y to "/proc file system support", below.
  5.7459 +
  5.7460 +  If unsure, say N.
  5.7461 +
  5.7462 +IBM ServeRAID support
  5.7463 +CONFIG_SCSI_IPS
  5.7464 +  This is support for the IBM ServeRAID hardware RAID controllers.
  5.7465 +  See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
  5.7466 +  for more information.  If this driver does not work correctly
  5.7467 +  without modification please contact the author by email at
  5.7468 +  ipslinux@us.ibm.com.
  5.7469 +
  5.7470 +  You can build this driver as a module ( = code which can be
  5.7471 +  inserted in and removed from the running kernel whenever you want),
  5.7472 +  but only a single instance may be loaded. If you want to compile it
  5.7473 +  as a module, say M here and read <file:Documentation/modules.txt>.
  5.7474 +  The module will be called ips.o.
  5.7475 +
  5.7476 +BusLogic SCSI support
  5.7477 +CONFIG_SCSI_BUSLOGIC
  5.7478 +  This is support for BusLogic MultiMaster and FlashPoint SCSI Host
  5.7479 +  Adapters. Consult the SCSI-HOWTO, available from
  5.7480 +  <http://www.tldp.org/docs.html#howto>, and the files
  5.7481 +  <file:drivers/scsi/README.BusLogic> and
  5.7482 +  <file:drivers/scsi/README.FlashPoint> for more information. If this
  5.7483 +  driver does not work correctly without modification, please contact
  5.7484 +  the author, Leonard N. Zubkoff, by email to lnz@dandelion.com.
  5.7485 +
  5.7486 +  You can also build this driver as a module ( = code which can be
  5.7487 +  inserted in and removed from the running kernel whenever you want),
  5.7488 +  but only a single instance may be loaded. If you want to compile it
  5.7489 +  as a module, say M here and read <file:Documentation/modules.txt>.
  5.7490 +  The module will be called BusLogic.o.
  5.7491 +
  5.7492 +Omit BusLogic SCSI FlashPoint support
  5.7493 +CONFIG_SCSI_OMIT_FLASHPOINT
  5.7494 +  This option allows you to omit the FlashPoint support from the
  5.7495 +  BusLogic SCSI driver. The FlashPoint SCCB Manager code is
  5.7496 +  substantial, so users of MultiMaster Host Adapters may wish to omit
  5.7497 +  it.
  5.7498 +
  5.7499 +Compaq Fibre Channel 64-bit/66Mhz HBA support
  5.7500 +CONFIG_SCSI_CPQFCTS
  5.7501 +  Say Y here to compile in support for the Compaq StorageWorks Fibre
  5.7502 +  Channel 64-bit/66Mhz Host Bus Adapter.
  5.7503 +
  5.7504 +  If you want to compile the driver as a module ( = code which can be
  5.7505 +  inserted in and removed from the running kernel whenever you want),
  5.7506 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.7507 +  will be called cpqfc.o.
  5.7508 +
  5.7509 +DMX3191D SCSI support
  5.7510 +CONFIG_SCSI_DMX3191D
  5.7511 +  This is support for Domex DMX3191D SCSI Host Adapters.
  5.7512 +
  5.7513 +  This driver is also available as a module ( = code which can be
  5.7514 +  inserted in and removed from the running kernel whenever you want).
  5.7515 +  The module will be called dmx3191d.o.  If you want to compile it as
  5.7516 +  a module, say M here and read <file:Documentation/modules.txt>.
  5.7517 +
  5.7518 +DTC3180/3280 SCSI support
  5.7519 +CONFIG_SCSI_DTC3280
  5.7520 +  This is support for DTC 3180/3280 SCSI Host Adapters.  Please read
  5.7521 +  the SCSI-HOWTO, available from
  5.7522 +  <http://www.tldp.org/docs.html#howto>, and the file
  5.7523 +  <file:drivers/scsi/README.dtc3x80>.
  5.7524 +
  5.7525 +  This driver is also available as a module ( = code which can be
  5.7526 +  inserted in and removed from the running kernel whenever you want).
  5.7527 +  The module will be called dtc.o.  If you want to compile it as a
  5.7528 +  module, say M here and read <file:Documentation/modules.txt>.
  5.7529 +
  5.7530 +EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti, Alphatronix) support
  5.7531 +CONFIG_SCSI_EATA_DMA
  5.7532 +  This is support for the EATA-DMA protocol compliant SCSI Host
  5.7533 +  Adapters like the SmartCache III/IV, SmartRAID controller families
  5.7534 +  and the DPT PM2011B and PM2012B controllers.
  5.7535 +
  5.7536 +  Note that this driver is obsolete; if you have one of the above
  5.7537 +  SCSI Host Adapters, you should normally say N here and Y to "EATA
  5.7538 +  ISA/EISA/PCI support", below.  Please read the SCSI-HOWTO, available
  5.7539 +  from <http://www.tldp.org/docs.html#howto>.
  5.7540 +
  5.7541 +  This driver is also available as a module ( = code which can be
  5.7542 +  inserted in and removed from the running kernel whenever you want).
  5.7543 +  The module will be called eata_dma.o.  If you want to compile it as
  5.7544 +  a module, say M here and read <file:Documentation/modules.txt>.
  5.7545 +
  5.7546 +EATA-PIO (old DPT PM2001, PM2012A) support
  5.7547 +CONFIG_SCSI_EATA_PIO
  5.7548 +  This driver supports all EATA-PIO protocol compliant SCSI Host
  5.7549 +  Adapters like the DPT PM2001 and the PM2012A.  EATA-DMA compliant
  5.7550 +  host adapters could also use this driver but are discouraged from
  5.7551 +  doing so, since this driver only supports hard disks and lacks
  5.7552 +  numerous features.  You might want to have a look at the SCSI-HOWTO,
  5.7553 +  available from <http://www.tldp.org/docs.html#howto>.
  5.7554 +
  5.7555 +  If you want to compile this as a module ( = code which can be
  5.7556 +  inserted in and removed from the running kernel whenever you want),
  5.7557 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.7558 +  will be called eata_pio.o.
  5.7559 +
  5.7560 +UltraStor 14F/34F support
  5.7561 +CONFIG_SCSI_U14_34F
  5.7562 +  This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
  5.7563 +  The source at <file:drivers/scsi/u14-34f.c> contains some
  5.7564 +  information about this hardware.  If the driver doesn't work out of
  5.7565 +  the box, you may have to change some settings in
  5.7566 +  <file: drivers/scsi/u14-34f.c>.  Read the SCSI-HOWTO, available from
  5.7567 +  <http://www.tldp.org/docs.html#howto>.  Note that there is also
  5.7568 +  another driver for the same hardware: "UltraStor SCSI support",
  5.7569 +  below.  You should say Y to both only if you want 24F support as
  5.7570 +  well.
  5.7571 +
  5.7572 +  This driver is also available as a module ( = code which can be
  5.7573 +  inserted in and removed from the running kernel whenever you want).
  5.7574 +  The module will be called u14-34f.o.  If you want to compile it as a
  5.7575 +  module, say M here and read <file:Documentation/modules.txt>.
  5.7576 +
  5.7577 +enable elevator sorting
  5.7578 +CONFIG_SCSI_U14_34F_LINKED_COMMANDS
  5.7579 +  This option enables elevator sorting for all probed SCSI disks and
  5.7580 +  CD-ROMs. It definitely reduces the average seek distance when doing
  5.7581 +  random seeks, but this does not necessarily result in a noticeable
  5.7582 +  performance improvement: your mileage may vary...
  5.7583 +
  5.7584 +  The safe answer is N.
  5.7585 +
  5.7586 +maximum number of queued commands
  5.7587 +CONFIG_SCSI_U14_34F_MAX_TAGS
  5.7588 +  This specifies how many SCSI commands can be maximally queued for
  5.7589 +  each probed SCSI device. You should reduce the default value of 8
  5.7590 +  only if you have disks with buggy or limited tagged command support.
  5.7591 +  Minimum is 2 and maximum is 14. This value is also the window size
  5.7592 +  used by the elevator sorting option above. The effective value used
  5.7593 +  by the driver for each probed SCSI device is reported at boot time.
  5.7594 +
  5.7595 +Future Domain 16xx SCSI/AHA-2920A support
  5.7596 +CONFIG_SCSI_FUTURE_DOMAIN
  5.7597 +  This is support for Future Domain's 16-bit SCSI host adapters
  5.7598 +  (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
  5.7599 +  other adapters based on the Future Domain chipsets (Quantum
  5.7600 +  ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
  5.7601 +  It is explained in section 3.7 of the SCSI-HOWTO, available from
  5.7602 +  <http://www.tldp.org/docs.html#howto>.
  5.7603 +
  5.7604 +  NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
  5.7605 +  and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
  5.7606 +  controller support"). This Future Domain driver works with the older
  5.7607 +  Adaptec AHA-2920A boards with a Future Domain chip on them.
  5.7608 +
  5.7609 +  This driver is also available as a module ( = code which can be
  5.7610 +  inserted in and removed from the running kernel whenever you want).
  5.7611 +  The module will be called fdomain.o. If you want to compile it as a
  5.7612 +  module, say M here and read <file:Documentation/modules.txt>.
  5.7613 +
  5.7614 +Future Domain MCS-600/700 SCSI support
  5.7615 +CONFIG_SCSI_FD_MCS
  5.7616 +  This is support for Future Domain MCS 600/700 MCA SCSI adapters.
  5.7617 +  Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
  5.7618 +  is identical to the MCS 700 and hence also supported by this driver.
  5.7619 +  This driver also supports the Reply SB16/SCSI card (the SCSI part).
  5.7620 +  It supports multiple adapters in the same system.
  5.7621 +
  5.7622 +  This driver is also available as a module ( = code which can be
  5.7623 +  inserted in and removed from the running kernel whenever you want).
  5.7624 +  The module will be called fd_mcs.o. If you want to compile it as a
  5.7625 +  module, say M here and read <file:Documentation/modules.txt>.
  5.7626 +
  5.7627 +Generic NCR5380/53c400 SCSI support
  5.7628 +CONFIG_SCSI_GENERIC_NCR5380
  5.7629 +  This is the generic NCR family of SCSI controllers, not to be
  5.7630 +  confused with the NCR 53c7 or 8xx controllers.  It is explained in
  5.7631 +  section 3.8 of the SCSI-HOWTO, available from
  5.7632 +  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
  5.7633 +  of the box, you may have to change some settings in
  5.7634 +  <file:drivers/scsi/g_NCR5380.h>.
  5.7635 +
  5.7636 +  This driver is also available as a module ( = code which can be
  5.7637 +  inserted in and removed from the running kernel whenever you want).
  5.7638 +  The module will be called g_NCR5380.o.  If you want to compile it as
  5.7639 +  a module, say M here and read <file:Documentation/modules.txt>.
  5.7640 +
  5.7641 +Enable NCR53c400 extensions
  5.7642 +CONFIG_SCSI_GENERIC_NCR53C400
  5.7643 +  This enables certain optimizations for the NCR53c400 SCSI cards.
  5.7644 +  You might as well try it out.  Note that this driver will only probe
  5.7645 +  for the Trantor T130B in its default configuration; you might have
  5.7646 +  to pass a command line option to the kernel at boot time if it does
  5.7647 +  not detect your card.  See the file
  5.7648 +  <file:drivers/scsi/README.g_NCR5380> for details.
  5.7649 +
  5.7650 +# Choice: ncr5380
  5.7651 +NCR5380/53c400 mapping method (use Port for T130B)
  5.7652 +CONFIG_SCSI_G_NCR5380_PORT
  5.7653 +  The NCR5380 and NCR53c400 SCSI controllers come in two varieties:
  5.7654 +  port or memory mapped. You should know what you have. The most
  5.7655 +  common card, Trantor T130B, uses port mapped mode.
  5.7656 +
  5.7657 +NCR Dual 700 MCA SCSI support
  5.7658 +CONFIG_SCSI_NCR_D700
  5.7659 +  This is a driver for the MicroChannel Dual 700 card produced by
  5.7660 +  NCR and commonly used in 345x/35xx/4100 class machines.  It always
  5.7661 +  tries to negotiate sync and uses tag command queueing.
  5.7662 +
  5.7663 +  Unless you have an NCR manufactured machine, the chances are that
  5.7664 +  you do not have this SCSI card, so say N.
  5.7665 +
  5.7666 +  If you want to compile the driver as a module ( = code which can be
  5.7667 +  inserted in and removed from the running kernel whenever you want),
  5.7668 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.7669 +  will be called NCR_D700.o.
  5.7670 +
  5.7671 +HP LASI SCSI support for 53c700/710
  5.7672 +CONFIG_SCSI_LASI700
  5.7673 +  This is a driver for the lasi baseboard in some parisc machines
  5.7674 +  which is based on the 53c700 chip.  Will also support LASI subsystems
  5.7675 +  based on the 710 chip using 700 emulation mode.
  5.7676 +
  5.7677 +  Unless you know you have a 53c700 or 53c710 based lasi, say N here
  5.7678 +
  5.7679 +NCR53c7,8xx SCSI support
  5.7680 +CONFIG_SCSI_NCR53C7xx
  5.7681 +  This is a driver for the 53c7 and 8xx NCR family of SCSI
  5.7682 +  controllers, not to be confused with the NCR 5380 controllers.  It
  5.7683 +  is explained in section 3.8 of the SCSI-HOWTO, available from
  5.7684 +  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
  5.7685 +  of the box, you may have to change some settings in
  5.7686 +  <file:drivers/scsi/53c7,8xx.h>.  Please read
  5.7687 +  <file:drivers/scsi/README.ncr53c7xx> for the available boot time
  5.7688 +  command line options.
  5.7689 +
  5.7690 +  Note: there is another driver for the 53c8xx family of controllers
  5.7691 +  ("NCR53C8XX SCSI support" below).  If you want to use them both, you
  5.7692 +  need to say M to both and build them as modules, but only one may be
  5.7693 +  active at a time. If you have a 53c8xx board, it's better to use the
  5.7694 +  other driver.
  5.7695 +
  5.7696 +  This driver is also available as a module ( = code which can be
  5.7697 +  inserted in and removed from the running kernel whenever you want).
  5.7698 +  The module will be called 53c7,8xx.o.  If you want to compile it as
  5.7699 +  a module, say M here and read <file:Documentation/modules.txt>.
  5.7700 +
  5.7701 +Always negotiate synchronous transfers
  5.7702 +CONFIG_SCSI_NCR53C7xx_sync
  5.7703 +  In general, this is good; however, it is a bit dangerous since there
  5.7704 +  are some broken SCSI devices out there. Take your chances. Safe bet
  5.7705 +  is N.
  5.7706 +
  5.7707 +Allow FAST-SCSI [10MHz]
  5.7708 +CONFIG_SCSI_NCR53C7xx_FAST
  5.7709 +  This will enable 10MHz FAST-SCSI transfers with your host
  5.7710 +  adapter. Some systems have problems with that speed, so it's safest
  5.7711 +  to say N here.
  5.7712 +
  5.7713 +Allow DISCONNECT
  5.7714 +CONFIG_SCSI_NCR53C7xx_DISCONNECT
  5.7715 +  This enables the disconnect/reconnect feature of the NCR SCSI
  5.7716 +  controller. When you say Y here, a slow SCSI device will not lock
  5.7717 +  the SCSI bus while processing a request, allowing simultaneous use
  5.7718 +  of e.g. a SCSI hard disk and SCSI tape or CD-ROM drive, and
  5.7719 +  providing much better performance when using slow and fast SCSI
  5.7720 +  devices at the same time. Some devices, however, do not operate
  5.7721 +  properly with this option enabled, and will cause your SCSI system
  5.7722 +  to hang, which might cause a system crash. The safe answer
  5.7723 +  therefore is to say N.
  5.7724 +
  5.7725 +SYM53C8XX Version 2 SCSI support
  5.7726 +CONFIG_SCSI_SYM53C8XX_2
  5.7727 +  This driver supports the whole NCR53C8XX/SYM53C8XX family of 
  5.7728 +  PCI-SCSI controllers. It also supports the subset of LSI53C10XX 
  5.7729 +  Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS 
  5.7730 +  language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI 
  5.7731 +  controllers.
  5.7732 +
  5.7733 +  If your system has problems using this new major version of the
  5.7734 +  SYM53C8XX driver, you may switch back to driver version 1.
  5.7735 +
  5.7736 +  Please read <file:drivers/scsi/sym53c8xx_2/Documentation.txt> for more
  5.7737 +  information.
  5.7738 +
  5.7739 +  If you want to compile the driver as a module ( = code which can be
  5.7740 +  inserted in and removed from the running kernel whenever you want),
  5.7741 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.7742 +  will be called sym53c8xx.o.
  5.7743 +
  5.7744 +PCI DMA addressing mode
  5.7745 +CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
  5.7746 +  This option only applies to PCI-SCSI chip that are PCI DAC capable 
  5.7747 +  (875A, 895A, 896, 1010-33, 1010-66, 1000).
  5.7748 +
  5.7749 +  When set to 0, only PCI 32 bit DMA addressing (SAC) will be performed.
  5.7750 +  When set to 1, 40 bit DMA addressing (with upper 24 bits of address 
  5.7751 +  set to zero) is supported. The addressable range is here 1 TB.
  5.7752 +  When set to 2, full 64 bits of address for DMA are supported, but only
  5.7753 +  16 segments of 4 GB can be addressed. The addressable range is so 
  5.7754 +  limited to 64 GB.
  5.7755 +
  5.7756 +  The safest value is 0 (32 bit DMA addressing) that is guessed to still 
  5.7757 +  fit most of real machines.
  5.7758 +
  5.7759 +  The preferred value 1 (40 bit DMA addressing) should make happy 
  5.7760 +  properly engineered PCI DAC capable host bridges. You may configure
  5.7761 +  this option for Intel platforms with more than 4 GB of memory.
  5.7762 +
  5.7763 +  The still experimental value 2 (64 bit DMA addressing with 16 x 4GB 
  5.7764 +  segments limitation) can be used on systems that require PCI address 
  5.7765 +  bits past bit 39 to be set for the addressing of memory using PCI 
  5.7766 +  DAC cycles.
  5.7767 +
  5.7768 +use normal IO
  5.7769 +CONFIG_SCSI_SYM53C8XX_IOMAPPED
  5.7770 +  If you say Y here, the driver will preferently use normal IO rather than 
  5.7771 +  memory mapped IO.
  5.7772 +
  5.7773 +maximum number of queued commands
  5.7774 +CONFIG_SCSI_SYM53C8XX_MAX_TAGS
  5.7775 +  This option allows you to specify the maximum number of commands
  5.7776 +  that can be queued to any device, when tagged command queuing is
  5.7777 +  possible. The driver supports up to 256 queued commands per device.
  5.7778 +  This value is used as a compiled-in hard limit.
  5.7779 +
  5.7780 +default tagged command queue depth
  5.7781 +CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS
  5.7782 +  This is the default value of the command queue depth the driver will 
  5.7783 +  announce to the generic SCSI layer for devices that support tagged 
  5.7784 +  command queueing. This value can be changed from the boot command line.
  5.7785 +  This is a soft limit that cannot exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
  5.7786 +
  5.7787 +NCR53C8XX SCSI support
  5.7788 +CONFIG_SCSI_NCR53C8XX
  5.7789 +  This is the BSD ncr driver adapted to Linux for the NCR53C8XX family
  5.7790 +  of PCI-SCSI controllers.  This driver supports parity checking,
  5.7791 +  tagged command queuing and fast synchronous data transfers up to 80
  5.7792 +  MB/s with wide FAST-40 LVD devices and controllers.
  5.7793 +
  5.7794 +  Recent versions of the 53C8XX chips are better supported by the
  5.7795 +  option "SYM53C8XX SCSI support", below.
  5.7796 +
  5.7797 +  Note: there is yet another driver for the 53c8xx family of
  5.7798 +  controllers ("NCR53c7,8xx SCSI support" above).  If you want to use
  5.7799 +  them both, you need to say M to both and build them as modules, but
  5.7800 +  only one may be active at a time.  If you have a 53c8xx board, you
  5.7801 +  probably do not want to use the "NCR53c7,8xx SCSI support".
  5.7802 +
  5.7803 +  Please read <file:drivers/scsi/README.ncr53c8xx> for more
  5.7804 +  information.
  5.7805 +
  5.7806 +  If you want to compile the driver as a module ( = code which can be
  5.7807 +  inserted in and removed from the running kernel whenever you want),
  5.7808 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.7809 +  will be called ncr53c8xx.o.
  5.7810 +
  5.7811 +SYM53C8XX Version 1 SCSI support
  5.7812 +CONFIG_SCSI_SYM53C8XX
  5.7813 +  This driver supports all the features of recent 53C8XX chips (used
  5.7814 +  in PCI SCSI controllers), notably the hardware phase mismatch
  5.7815 +  feature of the SYM53C896.
  5.7816 +
  5.7817 +  Older versions of the 53C8XX chips are not supported by this
  5.7818 +  driver.  If your system uses either a 810 rev. < 16, a 815, or a 825
  5.7819 +  rev. < 16 PCI SCSI processor, you must use the generic NCR53C8XX
  5.7820 +  driver ("NCR53C8XX SCSI support" above) or configure both the
  5.7821 +  NCR53C8XX and this SYM53C8XX drivers either as module or linked to
  5.7822 +  the kernel image.
  5.7823 +
  5.7824 +  When both drivers are linked into the kernel, the SYM53C8XX driver
  5.7825 +  is called first at initialization and you can use the 'excl=ioaddr'
  5.7826 +  driver boot option to exclude attachment of adapters by the
  5.7827 +  SYM53C8XX driver.  For example, entering
  5.7828 +  'sym53c8xx=excl:0xb400,excl=0xc000' at the lilo prompt prevents
  5.7829 +  adapters at io address 0xb400 and 0xc000 from being attached by the
  5.7830 +  SYM53C8XX driver, thus allowing the NCR53C8XX driver to attach them.
  5.7831 +  The 'excl' option is also supported by the NCR53C8XX driver.
  5.7832 +
  5.7833 +  Please read <file:drivers/scsi/README.ncr53c8xx> for more
  5.7834 +  information.
  5.7835 +
  5.7836 +  If you want to compile the driver as a module ( = code which can be
  5.7837 +  inserted in and removed from the running kernel whenever you want),
  5.7838 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.7839 +  will be called sym53c8xx.o.
  5.7840 +
  5.7841 +Synchronous transfer frequency in MHz
  5.7842 +CONFIG_SCSI_NCR53C8XX_SYNC
  5.7843 +  The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
  5.7844 +  rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80.  The numbers
  5.7845 +  are respectively the maximum data transfer rates in mega-transfers
  5.7846 +  per second for each class.  For example, a FAST-20 Wide 16 device is
  5.7847 +  able to transfer data at 20 million 16 bit packets per second for a
  5.7848 +  total rate of 40 MB/s.
  5.7849 +
  5.7850 +  You may specify 0 if you want to only use asynchronous data
  5.7851 +  transfers. This is the safest and slowest option. Otherwise, specify
  5.7852 +  a value between 5 and 80, depending on the capability of your SCSI
  5.7853 +  controller.  The higher the number, the faster the data transfer.
  5.7854 +  Note that 80 should normally be ok since the driver decreases the
  5.7855 +  value automatically according to the controller's capabilities.
  5.7856 +
  5.7857 +  Your answer to this question is ignored for controllers with NVRAM,
  5.7858 +  since the driver will get this information from the user set-up.  It
  5.7859 +  also can be overridden using a boot setup option, as follows
  5.7860 +  (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
  5.7861 +  for FAST-20 synchronous data transfer (20 mega-transfers per
  5.7862 +  second).
  5.7863 +
  5.7864 +  The normal answer therefore is not to go with the default but to
  5.7865 +  select the maximum value 80 allowing the driver to use the maximum
  5.7866 +  value supported by each controller. If this causes problems with
  5.7867 +  your SCSI devices, you should come back and decrease the value.
  5.7868 +
  5.7869 +  There is no safe option other than using good cabling, right
  5.7870 +  terminations and SCSI conformant devices.
  5.7871 +
  5.7872 +Use normal IO
  5.7873 +CONFIG_SCSI_NCR53C8XX_IOMAPPED
  5.7874 +  If you say Y here, the driver will use normal IO, as opposed to
  5.7875 +  memory mapped IO. Memory mapped IO has less latency than normal IO
  5.7876 +  and works for most Intel-based hardware. Under Linux/Alpha only
  5.7877 +  normal IO is currently supported by the driver and so, this option
  5.7878 +  has no effect on those systems.
  5.7879 +
  5.7880 +  The normal answer therefore is N; try Y only if you encounter SCSI
  5.7881 +  related problems.
  5.7882 +
  5.7883 +Not allow targets to disconnect
  5.7884 +CONFIG_SCSI_NCR53C8XX_NO_DISCONNECT
  5.7885 +  This option is only provided for safety if you suspect some SCSI
  5.7886 +  device of yours to not support properly the target-disconnect
  5.7887 +  feature. In that case, you would say Y here. In general however, to
  5.7888 +  not allow targets to disconnect is not reasonable if there is more
  5.7889 +  than 1 device on a SCSI bus. The normal answer therefore is N.
  5.7890 +
  5.7891 +Default tagged command queue depth
  5.7892 +CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS
  5.7893 +  "Tagged command queuing" is a feature of SCSI-2 which improves
  5.7894 +  performance: the host adapter can send several SCSI commands to a
  5.7895 +  device's queue even if previous commands haven't finished yet.
  5.7896 +  Because the device is intelligent, it can optimize its operations
  5.7897 +  (like head positioning) based on its own request queue. Some SCSI
  5.7898 +  devices don't implement this properly; if you want to disable this
  5.7899 +  feature, enter 0 or 1 here (it doesn't matter which).
  5.7900 +
  5.7901 +  The default value is 8 and should be supported by most hard disks.
  5.7902 +  This value can be overridden from the boot command line using the
  5.7903 +  'tags' option as follows (example):
  5.7904 +  'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
  5.7905 +  4, set queue depth to 16 for target 2 and target 3 on controller 0
  5.7906 +  and set queue depth to 10 for target 0 / lun 2 on controller 1.
  5.7907 +
  5.7908 +  The normal answer therefore is to go with the default 8 and to use
  5.7909 +  a boot command line option for devices that need to use a different
  5.7910 +  command queue depth.
  5.7911 +
  5.7912 +  There is no safe option other than using good SCSI devices.
  5.7913 +
  5.7914 +Maximum number of queued commands
  5.7915 +CONFIG_SCSI_NCR53C8XX_MAX_TAGS
  5.7916 +  This option allows you to specify the maximum number of commands
  5.7917 +  that can be queued to any device, when tagged command queuing is
  5.7918 +  possible. The default value is 32. Minimum is 2, maximum is 64.
  5.7919 +  Modern hard disks are able to support 64 tags and even more, but
  5.7920 +  do not seem to be faster when more than 32 tags are being used.
  5.7921 +
  5.7922 +  So, the normal answer here is to go with the default value 32 unless
  5.7923 +  you are using very large hard disks with large cache (>= 1 MB) that
  5.7924 +  are able to take advantage of more than 32 tagged commands.
  5.7925 +
  5.7926 +  There is no safe option and the default answer is recommended.
  5.7927 +
  5.7928 +Assume boards are SYMBIOS compatible
  5.7929 +CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT
  5.7930 +  This option allows you to enable some features depending on GPIO
  5.7931 +  wiring. These General Purpose Input/Output pins can be used for
  5.7932 +  vendor specific features or implementation of the standard SYMBIOS
  5.7933 +  features. Genuine SYMBIOS controllers use GPIO0 in output for
  5.7934 +  controller LED and GPIO3 bit as a flag indicating
  5.7935 +  singled-ended/differential interface. The Tekram DC-390U/F boards
  5.7936 +  uses a different GPIO wiring.
  5.7937 +
  5.7938 +  Your answer to this question is ignored if all your controllers have
  5.7939 +  NVRAM, since the driver is able to detect the board type from the
  5.7940 +  NVRAM format.
  5.7941 +
  5.7942 +  If all the controllers in your system are genuine SYMBIOS boards or
  5.7943 +  use BIOS and drivers from SYMBIOS, you would want to say Y here,
  5.7944 +  otherwise N. N is the safe answer.
  5.7945 +
  5.7946 +Enable traffic profiling
  5.7947 +CONFIG_SCSI_NCR53C8XX_PROFILE
  5.7948 +  This option allows you to enable profiling information gathering.
  5.7949 +  These statistics are not very accurate due to the low frequency
  5.7950 +  of the kernel clock (100 Hz on i386) and have performance impact
  5.7951 +  on systems that use very fast devices.
  5.7952 +
  5.7953 +  The normal answer therefore is N.
  5.7954 +
  5.7955 +Include support for the NCR PQS/PDS SCSI card
  5.7956 +CONFIG_SCSI_NCR53C8XX_PQS_PDS
  5.7957 +  Say Y here if you have a special SCSI adapter produced by NCR
  5.7958 +  corporation called a PCI Quad SCSI or PCI Dual SCSI. You do not need
  5.7959 +  this if you do not have one of these adapters. However, since this
  5.7960 +  device is detected as a specific PCI device, this option is quite
  5.7961 +  safe.
  5.7962 +
  5.7963 +  The common answer here is N, but answering Y is safe.
  5.7964 +
  5.7965 +Workbit NinjaSCSI-32Bi/UDE support
  5.7966 +CONFIG_SCSI_NSP32
  5.7967 +  This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
  5.7968 +  SCSI host adapter. Please read the SCSI-HOWTO, available from
  5.7969 +  <http://www.linuxdoc.org/docs.html#howto>.
  5.7970 +
  5.7971 +  If you want to compile this as a module ( = code which can be
  5.7972 +  inserted in and removed from the running kernel whenever you want),
  5.7973 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.7974 +  will be called nsp32.o.
  5.7975 +
  5.7976 +IBMMCA SCSI support
  5.7977 +CONFIG_SCSI_IBMMCA
  5.7978 +  This is support for the IBM SCSI adapter found in many of the PS/2
  5.7979 +  series computers.  These machines have an MCA bus, so you need to
  5.7980 +  answer Y to "MCA support" as well and read
  5.7981 +  <file:Documentation/mca.txt>.
  5.7982 +
  5.7983 +  If the adapter isn't found during boot (a common problem for models
  5.7984 +  56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
  5.7985 +  option, where <pun> is the id of the SCSI subsystem (usually 7, but
  5.7986 +  if that doesn't work check your reference diskette).  Owners of
  5.7987 +  model 95 with a LED-matrix-display can in addition activate some
  5.7988 +  activity info like under OS/2, but more informative, by setting
  5.7989 +  'ibmmcascsi=display' as an additional kernel parameter.  Try "man
  5.7990 +  bootparam" or see the documentation of your boot loader about how to
  5.7991 +  pass options to the kernel.
  5.7992 +
  5.7993 +  If you want to compile this driver as a module ( = code which can be
  5.7994 +  inserted in and removed from the running kernel whenever you want),
  5.7995 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.7996 +  will be called ibmmca.o.
  5.7997 +
  5.7998 +Standard SCSI-order
  5.7999 +CONFIG_IBMMCA_SCSI_ORDER_STANDARD
  5.8000 +  In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
  5.8001 +  are assigned to the drive letters, starting with the lowest SCSI-id
  5.8002 +  (physical number -- pun) to be drive C:, as seen from DOS and
  5.8003 +  similar operating systems. When looking into papers describing the
  5.8004 +  ANSI-SCSI-standard, this assignment of drives appears to be wrong.
  5.8005 +  The SCSI-standard follows a hardware-hierarchy which says that id 7
  5.8006 +  has the highest priority and id 0 the lowest. Therefore, the host
  5.8007 +  adapters are still today everywhere placed as SCSI-id 7 by default.
  5.8008 +  In the SCSI-standard, the drive letters express the priority of the
  5.8009 +  disk. C: should be the hard disk, or a partition on it, with the
  5.8010 +  highest priority. This must therefore be the disk with the highest
  5.8011 +  SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
  5.8012 +  original definition of the SCSI-standard as also industrial- and
  5.8013 +  process-control-machines, like VME-CPUs running under realtime-OSes
  5.8014 +  (e.g. LynxOS, OS9) do.
  5.8015 +
  5.8016 +  If you like to run Linux on your MCA-machine with the same
  5.8017 +  assignment of hard disks as seen from e.g. DOS or OS/2 on your
  5.8018 +  machine, which is in addition conformant to the SCSI-standard, you
  5.8019 +  must say Y here. This is also necessary for MCA-Linux users who want
  5.8020 +  to keep downward compatibility to older releases of the
  5.8021 +  IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
  5.8022 +  June 1997).
  5.8023 +
  5.8024 +  If you like to have the lowest SCSI-id assigned as drive C:, as
  5.8025 +  modern SCSI-BIOSes do, which does not conform to the standard, but
  5.8026 +  is widespread and common in the PC-world of today, you must say N
  5.8027 +  here. If unsure, say Y.
  5.8028 +
  5.8029 +Reset SCSI-devices at boot time
  5.8030 +CONFIG_IBMMCA_SCSI_DEV_RESET
  5.8031 +  By default, SCSI-devices are reset when the machine is powered on.
  5.8032 +  However, some devices exist, like special-control-devices,
  5.8033 +  SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
  5.8034 +  not reset when switched on. If you say Y here, each device connected
  5.8035 +  to your SCSI-bus will be issued a reset-command after it has been
  5.8036 +  probed, while the kernel is booting. This may cause problems with
  5.8037 +  more modern devices, like hard disks, which do not appreciate these
  5.8038 +  reset commands, and can cause your system to hang. So say Y only if
  5.8039 +  you know that one of your older devices needs it; N is the safe
  5.8040 +  answer.
  5.8041 +
  5.8042 +NCR MCA 53C9x SCSI support
  5.8043 +CONFIG_SCSI_MCA_53C9X
  5.8044 +  Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
  5.8045 +  controller based on the NCR 53C94.  This driver will allow use of
  5.8046 +  the controller on the 3550, and very possibly others.
  5.8047 +
  5.8048 +  If you want to compile this as a module (= code which can be
  5.8049 +  inserted and removed from the running kernel whenever you want), say
  5.8050 +  M here and read <file:Documentation/modules.txt>.  The module will
  5.8051 +  be called mca_53c9x.o.
  5.8052 +
  5.8053 +Always IN2000 SCSI support
  5.8054 +CONFIG_SCSI_IN2000
  5.8055 +  This is support for an ISA bus SCSI host adapter.  You'll find more
  5.8056 +  information in <file:drivers/scsi/README.in2000>. If it doesn't work
  5.8057 +  out of the box, you may have to change the jumpers for IRQ or
  5.8058 +  address selection.
  5.8059 +
  5.8060 +  If you want to compile this as a module ( = code which can be
  5.8061 +  inserted in and removed from the running kernel whenever you want),
  5.8062 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.8063 +  will be called in2000.o.
  5.8064 +
  5.8065 +Initio 91XXU(W) SCSI support
  5.8066 +CONFIG_SCSI_INITIO
  5.8067 +  This is support for the Initio 91XXU(W) SCSI host adapter.  Please
  5.8068 +  read the SCSI-HOWTO, available from
  5.8069 +  <http://www.tldp.org/docs.html#howto>.
  5.8070 +
  5.8071 +  If you want to compile this as a module ( = code which can be
  5.8072 +  inserted in and removed from the running kernel whenever you want),
  5.8073 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.8074 +  will be called initio.o.
  5.8075 +
  5.8076 +PAS16 SCSI support
  5.8077 +CONFIG_SCSI_PAS16
  5.8078 +  This is support for a SCSI host adapter.  It is explained in section
  5.8079 +  3.10 of the SCSI-HOWTO, available from
  5.8080 +  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
  5.8081 +  of the box, you may have to change some settings in
  5.8082 +  <file:drivers/scsi/pas16.h>.
  5.8083 +
  5.8084 +  This driver is also available as a module ( = code which can be
  5.8085 +  inserted in and removed from the running kernel whenever you want).
  5.8086 +  The module will be called pas16.o.  If you want to compile it as a
  5.8087 +  module, say M here and read <file:Documentation/modules.txt>.
  5.8088 +
  5.8089 +Initio INI-A100U2W SCSI support
  5.8090 +CONFIG_SCSI_INIA100
  5.8091 +  This is support for the Initio INI-A100U2W SCSI host adapter.
  5.8092 +  Please read the SCSI-HOWTO, available from
  5.8093 +  <http://www.tldp.org/docs.html#howto>.
  5.8094 +
  5.8095 +  If you want to compile this as a module ( = code which can be
  5.8096 +  inserted in and removed from the running kernel whenever you want),
  5.8097 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.8098 +  will be called a100u2w.o.
  5.8099 +
  5.8100 +PCI2000 support
  5.8101 +CONFIG_SCSI_PCI2000
  5.8102 +  This is support for the PCI2000I EIDE interface card which acts as a
  5.8103 +  SCSI host adapter.  Please read the SCSI-HOWTO, available from
  5.8104 +  <http://www.tldp.org/docs.html#howto>.
  5.8105 +
  5.8106 +  This driver is also available as a module called pci2000.o ( = code
  5.8107 +  which can be inserted in and removed from the running kernel
  5.8108 +  whenever you want).  If you want to compile it as a module, say M
  5.8109 +  here and read <file:Documentation/modules.txt>.
  5.8110 +
  5.8111 +PCI2220i support
  5.8112 +CONFIG_SCSI_PCI2220I
  5.8113 +  This is support for the PCI2220i EIDE interface card which acts as a
  5.8114 +  SCSI host adapter.  Please read the SCSI-HOWTO, available from
  5.8115 +  <http://www.tldp.org/docs.html#howto>.
  5.8116 +
  5.8117 +  This driver is also available as a module called pci2220i.o ( = code
  5.8118 +  which can be inserted in and removed from the running kernel
  5.8119 +  whenever you want).  If you want to compile it as a module, say M
  5.8120 +  here and read <file:Documentation/modules.txt>.
  5.8121 +
  5.8122 +PSI240i support
  5.8123 +CONFIG_SCSI_PSI240I
  5.8124 +  This is support for the PSI240i EIDE interface card which acts as a
  5.8125 +  SCSI host adapter.  Please read the SCSI-HOWTO, available from
  5.8126 +  <http://www.tldp.org/docs.html#howto>.
  5.8127 +
  5.8128 +  This driver is also available as a module called psi240i.o ( = code
  5.8129 +  which can be inserted in and removed from the running kernel
  5.8130 +  whenever you want).  If you want to compile it as a module, say M
  5.8131 +  here and read <file:Documentation/modules.txt>.
  5.8132 +
  5.8133 +Qlogic FAS SCSI support
  5.8134 +CONFIG_SCSI_QLOGIC_FAS
  5.8135 +  This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
  5.8136 +  FastSCSI! cards as well as any other card based on the FASXX chip
  5.8137 +  (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
  5.8138 +
  5.8139 +  This driver does NOT support the PCI versions of these cards. The
  5.8140 +  PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
  5.8141 +  SCSI support"), below.
  5.8142 +
  5.8143 +  Information about this driver is contained in
  5.8144 +  <file:drivers/scsi/README.qlogicfas>.  You should also read the
  5.8145 +  SCSI-HOWTO, available from
  5.8146 +  <http://www.tldp.org/docs.html#howto>.
  5.8147 +
  5.8148 +  This driver is also available as a module ( = code which can be
  5.8149 +  inserted in and removed from the running kernel whenever you want).
  5.8150 +  The module will be called qlogicfas.o. If you want to compile it as
  5.8151 +  a module, say M here and read <file:Documentation/modules.txt>.
  5.8152 +
  5.8153 +Qlogic ISP SCSI support
  5.8154 +CONFIG_SCSI_QLOGIC_ISP
  5.8155 +  This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
  5.8156 +  IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card.  (This latter
  5.8157 +  card is supported by the "AM53/79C974 PCI SCSI" driver.)
  5.8158 +
  5.8159 +  If you say Y here, make sure to choose "BIOS" at the question "PCI
  5.8160 +  access mode".
  5.8161 +
  5.8162 +  Please read the file <file:drivers/scsi/README.qlogicisp>.  You
  5.8163 +  should also read the SCSI-HOWTO, available from
  5.8164 +  <http://www.tldp.org/docs.html#howto>.
  5.8165 +
  5.8166 +  This driver is also available as a module ( = code which can be
  5.8167 +  inserted in and removed from the running kernel whenever you want).
  5.8168 +  The module will be called qlogicisp.o.  If you want to compile it as
  5.8169 +  a module, say M here and read <file:Documentation/modules.txt>.
  5.8170 +
  5.8171 +Qlogic ISP FC SCSI support
  5.8172 +CONFIG_SCSI_QLOGIC_FC
  5.8173 +  This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
  5.8174 +
  5.8175 +  This driver is also available as a module ( = code which can be
  5.8176 +  inserted in and removed from the running kernel whenever you want).
  5.8177 +  The module will be called qlogicfc.o.  If you want to compile it as
  5.8178 +  a module, say M here and read <file:Documentation/modules.txt>.
  5.8179 +
  5.8180 +Include loadable firmware in driver
  5.8181 +CONFIG_SCSI_QLOGIC_FC_FIRMWARE
  5.8182 +  Say Y to include ISP2100 Fabric Initiator/Target Firmware, with
  5.8183 +  expanded LUN addressing and FcTape (FCP-2) support, in the
  5.8184 +  Qlogic QLA 1280 driver. This is required on some platforms.
  5.8185 +
  5.8186 +Qlogic QLA 1280 SCSI support
  5.8187 +CONFIG_SCSI_QLOGIC_1280
  5.8188 +  Say Y if you have a QLogic ISP1x80/1x160 SCSI host adapter.
  5.8189 +
  5.8190 +  This driver is also available as a module ( = code which can be
  5.8191 +  inserted in and removed from the running kernel whenever you want).
  5.8192 +  The module will be called qla1280.o. If you want to compile it as
  5.8193 +  a module, say M here and read <file:Documentation/modules.txt>.
  5.8194 +
  5.8195 +Seagate ST-02 and Future Domain TMC-8xx SCSI support
  5.8196 +CONFIG_SCSI_SEAGATE
  5.8197 +  These are 8-bit SCSI controllers; the ST-01 is also supported by
  5.8198 +  this driver.  It is explained in section 3.9 of the SCSI-HOWTO,
  5.8199 +  available from <http://www.tldp.org/docs.html#howto>.  If it
  5.8200 +  doesn't work out of the box, you may have to change some settings in
  5.8201 +  <file:drivers/scsi/seagate.h>.
  5.8202 +
  5.8203 +  This driver is also available as a module ( = code which can be
  5.8204 +  inserted in and removed from the running kernel whenever you want).
  5.8205 +  The module will be called seagate.o.  If you want to compile it as a
  5.8206 +  module, say M here and read <file:Documentation/modules.txt>.
  5.8207 +
  5.8208 +Trantor T128/T128F/T228 SCSI support
  5.8209 +CONFIG_SCSI_T128
  5.8210 +  This is support for a SCSI host adapter. It is explained in section
  5.8211 +  3.11 of the SCSI-HOWTO, available from
  5.8212 +  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
  5.8213 +  of the box, you may have to change some settings in
  5.8214 +  <file:drivers/scsi/t128.h>.  Note that Trantor was purchased by
  5.8215 +  Adaptec, and some former Trantor products are being sold under the
  5.8216 +  Adaptec name.
  5.8217 +
  5.8218 +  This driver is also available as a module ( = code which can be
  5.8219 +  inserted in and removed from the running kernel whenever you want).
  5.8220 +  The module will be called t128.o.  If you want to compile it as a
  5.8221 +  module, say M here and read <file:Documentation/modules.txt>.
  5.8222 +
  5.8223 +UltraStor SCSI support
  5.8224 +CONFIG_SCSI_ULTRASTOR
  5.8225 +  This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
  5.8226 +  adapter family.  This driver is explained in section 3.12 of the
  5.8227 +  SCSI-HOWTO, available from
  5.8228 +  <http://www.tldp.org/docs.html#howto>.  If it doesn't work out
  5.8229 +  of the box, you may have to change some settings in
  5.8230 +  <file:drivers/scsi/ultrastor.h>.
  5.8231 +
  5.8232 +  Note that there is also another driver for the same hardware:
  5.8233 +  "UltraStor 14F/34F support", above.
  5.8234 +
  5.8235 +  If you want to compile this as a module ( = code which can be
  5.8236 +  inserted in and removed from the running kernel whenever you want),
  5.8237 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.8238 +  will be called ultrastor.o.
  5.8239 +
  5.8240 +7000FASST SCSI support
  5.8241 +CONFIG_SCSI_7000FASST
  5.8242 +  This driver supports the Western Digital 7000 SCSI host adapter
  5.8243 +  family.  Some information is in the source:
  5.8244 +  <file:drivers/scsi/wd7000.c>.
  5.8245 +
  5.8246 +  This driver is also available as a module ( = code which can be
  5.8247 +  inserted in and removed from the running kernel whenever you want).
  5.8248 +  The module will be called wd7000.o.  If you want to compile it as a
  5.8249 +  module, say M here and read <file:Documentation/modules.txt>.
  5.8250 +
  5.8251 +ACARD SCSI support
  5.8252 +CONFIG_SCSI_ACARD
  5.8253 +  This driver supports the ACARD 870U/W SCSI host adapter.
  5.8254 +
  5.8255 +  This driver is also available as a module ( = code which can be
  5.8256 +  inserted in and removed from the running kernel whenever you want).
  5.8257 +  The module will be called atp870u.o. If you want to compile it as a
  5.8258 +  module, say M here and read <file:Documentation/modules.txt>.
  5.8259 +
  5.8260 +EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support
  5.8261 +CONFIG_SCSI_EATA
  5.8262 +  This driver supports all EATA/DMA-compliant SCSI host adapters.  DPT
  5.8263 +  ISA and all EISA I/O addresses are probed looking for the "EATA"
  5.8264 +  signature.  If you chose "BIOS" at the question "PCI access mode",
  5.8265 +  the addresses of all the PCI SCSI controllers reported by the PCI
  5.8266 +  subsystem are probed as well.
  5.8267 +
  5.8268 +  You want to read the start of <file:drivers/scsi/eata.c> and the
  5.8269 +  SCSI-HOWTO, available from
  5.8270 +  <http://www.tldp.org/docs.html#howto>.
  5.8271 +
  5.8272 +  Note that there is also another driver for the same hardware
  5.8273 +  available: "EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti,
  5.8274 +  Alphatronix) support". You should say Y to only one of them.
  5.8275 +
  5.8276 +  If you want to compile this as a module ( = code which can be
  5.8277 +  inserted in and removed from the running kernel whenever you want),
  5.8278 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.8279 +  will be called eata.o.
  5.8280 +
  5.8281 +enable tagged command queueing
  5.8282 +CONFIG_SCSI_EATA_TAGGED_QUEUE
  5.8283 +  This is a feature of SCSI-2 which improves performance: the host
  5.8284 +  adapter can send several SCSI commands to a device's queue even if
  5.8285 +  previous commands haven't finished yet. Most EATA adapters negotiate
  5.8286 +  this feature automatically with the device, even if your answer is
  5.8287 +  N. The safe answer is N.
  5.8288 +
  5.8289 +enable elevator sorting
  5.8290 +CONFIG_SCSI_EATA_LINKED_COMMANDS
  5.8291 +  This option enables elevator sorting for all probed SCSI disks and
  5.8292 +  CD-ROMs. It definitely reduces the average seek distance when doing
  5.8293 +  random seeks, but this does not necessarily result in a noticeable
  5.8294 +  performance improvement: your mileage may vary...
  5.8295 +  The safe answer is N.
  5.8296 +
  5.8297 +maximum number of queued commands
  5.8298 +CONFIG_SCSI_EATA_MAX_TAGS
  5.8299 +  This specifies how many SCSI commands can be maximally queued for
  5.8300 +  each probed SCSI device. You should reduce the default value of 16
  5.8301 +  only if you have disks with buggy or limited tagged command support.
  5.8302 +  Minimum is 2 and maximum is 62. This value is also the window size
  5.8303 +  used by the elevator sorting option above. The effective value used
  5.8304 +  by the driver for each probed SCSI device is reported at boot time.
  5.8305 +
  5.8306 +NCR53c406a SCSI support
  5.8307 +CONFIG_SCSI_NCR53C406A
  5.8308 +  This is support for the NCR53c406a SCSI host adapter.  For user
  5.8309 +  configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
  5.8310 +  in the kernel source.  Also read the SCSI-HOWTO, available from
  5.8311 +  <http://www.tldp.org/docs.html#howto>.
  5.8312 +
  5.8313 +  If you want to compile this driver as a module ( = code which can be
  5.8314 +  inserted in and removed from the running kernel whenever you want),
  5.8315 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.8316 +  will be called NCR53c406.o.
  5.8317 +
  5.8318 +Symbios 53c416 SCSI support
  5.8319 +CONFIG_SCSI_SYM53C416
  5.8320 +  This is support for the sym53c416 SCSI host adapter, the SCSI
  5.8321 +  adapter that comes with some HP scanners. This driver requires that
  5.8322 +  the sym53c416 is configured first using some sort of PnP
  5.8323 +  configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
  5.8324 +  are using isapnp then you need to compile this driver as a module
  5.8325 +  and then load it using insmod after isapnp has run. The parameters
  5.8326 +  of the configured card(s) should be passed to the driver. The format
  5.8327 +  is:
  5.8328 +
  5.8329 +    insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
  5.8330 +
  5.8331 +  There is support for up to four adapters. If you want to compile
  5.8332 +  this driver as a module ( = code which can be inserted in and
  5.8333 +  removed from the running kernel whenever you want), say M here and
  5.8334 +  read <file:Documentation/modules.txt>. The module will be called
  5.8335 +  sym53c416.o.
  5.8336 +
  5.8337 +Simple 53c710 SCSI support (Compaq, NCR machines)
  5.8338 +CONFIG_SCSI_SIM710
  5.8339 +  This is a simple driver for NCR53c710 based SCSI host adapters.
  5.8340 +
  5.8341 +  More complex drivers for this chip are available ("NCR53c7,8xx SCSI
  5.8342 +  support", above), but they require that the scsi chip be able to do
  5.8343 +  DMA block moves between memory and on-chip registers, which can
  5.8344 +  cause problems under certain conditions.  This driver is designed to
  5.8345 +  avoid these problems and is intended to work with any Intel machines
  5.8346 +  using 53c710 chips, including various Compaq and NCR machines.
  5.8347 +
  5.8348 +  Please read the comments at the top of the file
  5.8349 +  <file:drivers/scsi/sim710.c> for more information.
  5.8350 +
  5.8351 +  If you want to compile this driver as a module ( = code which can be
  5.8352 +  inserted in and removed from the running kernel whenever you want),
  5.8353 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.8354 +  will be called sim710.o.
  5.8355 +
  5.8356 +Tekram DC390(T) and Am53/79C974 SCSI support
  5.8357 +CONFIG_SCSI_DC390T
  5.8358 +  This driver supports PCI SCSI host adapters based on the Am53C974A
  5.8359 +  chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
  5.8360 +  PCscsi/PCnet (Am53/79C974) solutions.
  5.8361 +
  5.8362 +  Documentation can be found in <file:drivers/scsi/README.tmscsim>.
  5.8363 +
  5.8364 +  Note that this driver does NOT support Tekram DC390W/U/F, which are
  5.8365 +  based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
  5.8366 +  Also note that there is another generic Am53C974 driver,
  5.8367 +  "AM53/79C974 PCI SCSI support" below.  You can pick either one.
  5.8368 +
  5.8369 +  If you want to compile this driver as a module ( = code which can be
  5.8370 +  inserted in and removed from the running kernel whenever you want),
  5.8371 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.8372 +  will be called tmscsim.o.
  5.8373 +
  5.8374 +Omit support for other Am53/79C974 based SCSI adapters
  5.8375 +CONFIG_SCSI_DC390T_NOGENSUPP
  5.8376 +  If you say N here, the DC390(T) SCSI driver relies on the DC390
  5.8377 +  EEPROM to get initial values for its settings, such as speed,
  5.8378 +  termination, etc.  If it can't find this EEPROM, it will use
  5.8379 +  defaults or the user supplied boot/module parameters.  For details
  5.8380 +  on driver configuration see <file:drivers/scsi/README.tmscsim>.
  5.8381 +
  5.8382 +  If you say Y here and if no EEPROM is found, the driver gives up and
  5.8383 +  thus only supports Tekram DC390(T) adapters.  This can be useful if
  5.8384 +  you have a DC390(T) and another Am53C974 based adapter, which, for
  5.8385 +  some reason, you want to drive with the other AM53C974 driver.
  5.8386 +
  5.8387 +  If unsure, say N.
  5.8388 +
  5.8389 +AM53/79C974 PCI SCSI support
  5.8390 +CONFIG_SCSI_AM53C974
  5.8391 +  This is support for the AM53/79C974 SCSI host adapters.  Please read
  5.8392 +  <file:drivers/scsi/README.AM53C974> for details.  Also, the
  5.8393 +  SCSI-HOWTO, available from
  5.8394 +  <http://www.tldp.org/docs.html#howto>, is for you.
  5.8395 +
  5.8396 +  Note that there is another driver for AM53C974 based adapters:
  5.8397 +  "Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support", above.  You
  5.8398 +  can pick either one.
  5.8399 +
  5.8400 +  If you want to compile this driver as a module ( = code which can be
  5.8401 +  inserted in and removed from the running kernel whenever you want),
  5.8402 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.8403 +  will be called AM53C974.o.
  5.8404 +
  5.8405 +AMI MegaRAID support
  5.8406 +CONFIG_SCSI_MEGARAID
  5.8407 +  This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490
  5.8408 +  and 467 SCSI host adapters.
  5.8409 +
  5.8410 +  If you want to compile this driver as a module ( = code which can be
  5.8411 +  inserted in and removed from the running kernel whenever you want),
  5.8412 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.8413 +  will be called megaraid.o.
  5.8414 +
  5.8415 +Intel/ICP (former GDT SCSI Disk Array) RAID Controller support
  5.8416 +CONFIG_SCSI_GDTH
  5.8417 +  Formerly called GDT SCSI Disk Array Controller Support.
  5.8418 + 
  5.8419 +  This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI) 
  5.8420 +  manufactured by Intel/ICP vortex (an Intel Company). It is documented
  5.8421 +  in the kernel source in <file:drivers/scsi/gdth.c> and
  5.8422 +  <file:drivers/scsi/gdth.h.>
  5.8423 +
  5.8424 +  If you want to compile the driver as a module ( = code which can be
  5.8425 +  inserted in and removed from the running kernel whenever you want),
  5.8426 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.8427 +  will be called gdth.o.
  5.8428 +
  5.8429 +IOMEGA parallel port (ppa - older drives)
  5.8430 +CONFIG_SCSI_PPA
  5.8431 +  This driver supports older versions of IOMEGA's parallel port ZIP
  5.8432 +  drive (a 100 MB removable media device).
  5.8433 +
  5.8434 +  Note that you can say N here if you have the SCSI version of the ZIP
  5.8435 +  drive: it will be supported automatically if you said Y to the
  5.8436 +  generic "SCSI disk support", above.
  5.8437 +
  5.8438 +  If you have the ZIP Plus drive or a more recent parallel port ZIP
  5.8439 +  drive (if the supplied cable with the drive is labeled "AutoDetect")
  5.8440 +  then you should say N here and Y to "IOMEGA parallel port (imm -
  5.8441 +  newer drives)", below.
  5.8442 +
  5.8443 +  For more information about this driver and how to use it you should
  5.8444 +  read the file <file:drivers/scsi/README.ppa>.  You should also read
  5.8445 +  the SCSI-HOWTO, which is available from
  5.8446 +  <http://www.tldp.org/docs.html#howto>.  If you use this driver,
  5.8447 +  you will still be able to use the parallel port for other tasks,
  5.8448 +  such as a printer; it is safe to compile both drivers into the
  5.8449 +  kernel.
  5.8450 +
  5.8451 +  This driver is also available as a module which can be inserted in
  5.8452 +  and removed from the running kernel whenever you want.  To compile
  5.8453 +  this driver as a module, say M here and read
  5.8454 +  <file:Documentation/modules.txt>.  The module will be called ppa.o.
  5.8455 +
  5.8456 +IOMEGA parallel port (imm - newer drives)
  5.8457 +CONFIG_SCSI_IMM
  5.8458 +  This driver supports newer versions of IOMEGA's parallel port ZIP
  5.8459 +  drive (a 100 MB removable media device).
  5.8460 +
  5.8461 +  Note that you can say N here if you have the SCSI version of the ZIP
  5.8462 +  drive: it will be supported automatically if you said Y to the
  5.8463 +  generic "SCSI disk support", above.
  5.8464 +
  5.8465 +  If you have the ZIP Plus drive or a more recent parallel port ZIP
  5.8466 +  drive (if the supplied cable with the drive is labeled "AutoDetect")
  5.8467 +  then you should say Y here; if you have an older ZIP drive, say N
  5.8468 +  here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
  5.8469 +
  5.8470 +  For more information about this driver and how to use it you should
  5.8471 +  read the file <file:drivers/scsi/README.ppa>.  You should also read
  5.8472 +  the SCSI-HOWTO, which is available from
  5.8473 +  <http://www.tldp.org/docs.html#howto>.  If you use this driver,
  5.8474 +  you will still be able to use the parallel port for other tasks,
  5.8475 +  such as a printer; it is safe to compile both drivers into the
  5.8476 +  kernel.
  5.8477 +
  5.8478 +  This driver is also available as a module which can be inserted in
  5.8479 +  and removed from the running kernel whenever you want.  To compile
  5.8480 +  this driver as a module, say M here and read
  5.8481 +  <file:Documentation/modules.txt>.  The module will be called imm.o.
  5.8482 +
  5.8483 +Force the Iomega ZIP drivers to use EPP-16
  5.8484 +CONFIG_SCSI_IZIP_EPP16
  5.8485 +  EPP (Enhanced Parallel Port) is a standard for parallel ports which
  5.8486 +  allows them to act as expansion buses that can handle up to 64
  5.8487 +  peripheral devices.
  5.8488 +
  5.8489 +  Some parallel port chipsets are slower than their motherboard, and
  5.8490 +  so we have to control the state of the chipset's FIFO queue every
  5.8491 +  now and then to avoid data loss. This will be done if you say Y
  5.8492 +  here.
  5.8493 +
  5.8494 +  Generally, saying Y is the safe option and slows things down a bit.
  5.8495 +
  5.8496 +Assume slow parallel port control register
  5.8497 +CONFIG_SCSI_IZIP_SLOW_CTR
  5.8498 +  Some parallel ports are known to have excessive delays between
  5.8499 +  changing the parallel port control register and good data being
  5.8500 +  available on the parallel port data/status register. This option
  5.8501 +  forces a small delay (1.0 usec to be exact) after changing the
  5.8502 +  control register to let things settle out. Enabling this option may
  5.8503 +  result in a big drop in performance but some very old parallel ports
  5.8504 +  (found in 386 vintage machines) will not work properly.
  5.8505 +
  5.8506 +  Generally, saying N is fine.
  5.8507 +
  5.8508 +SCSI debugging host simulator
  5.8509 +CONFIG_SCSI_DEBUG
  5.8510 +  This is a host adapter simulator that can be programmed to simulate
  5.8511 +  a large number of conditions that could occur on a real bus. The
  5.8512 +  advantage is that many hard to reproduce problems can be tested in a
  5.8513 +  controlled environment where there is reduced risk of losing
  5.8514 +  important data. This is primarily of use to people trying to debug
  5.8515 +  the middle and upper layers of the SCSI subsystem. If unsure, say N.
  5.8516 +
  5.8517 +  If you want to compile the driver as a module ( = code which can be
  5.8518 +  inserted in and removed from the running kernel whenever you want),
  5.8519 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.8520 +  will be called scsi_debug.o.
  5.8521 +
  5.8522 +Fibre Channel and FC4 SCSI support
  5.8523 +CONFIG_FC4
  5.8524 +  Fibre Channel is a high speed serial protocol mainly used to
  5.8525 +  connect large storage devices to the computer; it is compatible with
  5.8526 +  and intended to replace SCSI.
  5.8527 +
  5.8528 +  This is an experimental support for storage arrays connected to your
  5.8529 +  computer using optical fibre cables and the "X3.269-199X Fibre
  5.8530 +  Channel Protocol for SCSI" specification. If you want to use this,
  5.8531 +  you need to say Y here and to "SCSI support" as well as to the
  5.8532 +  drivers for the storage array itself and for the interface adapter
  5.8533 +  such as SOC or SOC+. This subsystem could even serve for IP
  5.8534 +  networking, with some code extensions.
  5.8535 +
  5.8536 +  If unsure, say N.
  5.8537 +
  5.8538 +Sun SOC/Sbus
  5.8539 +CONFIG_FC4_SOC
  5.8540 +  Serial Optical Channel is an interface card with one or two Fibre
  5.8541 +  Optic ports, each of which can be connected to a disk array. Note
  5.8542 +  that if you have older firmware in the card, you'll need the
  5.8543 +  microcode from the Solaris driver to make it work.
  5.8544 +
  5.8545 +  This support is also available as a module called soc.o ( = code
  5.8546 +  which can be inserted in and removed from the running kernel
  5.8547 +  whenever you want). If you want to compile it as a module, say M
  5.8548 +  here and read <file:Documentation/modules.txt>.
  5.8549 +
  5.8550 +Sun SOC+ (aka SOCAL)
  5.8551 +CONFIG_FC4_SOCAL
  5.8552 +  Serial Optical Channel Plus is an interface card with up to two
  5.8553 +  Fibre Optic ports. This card supports FC Arbitrated Loop (usually
  5.8554 +  A5000 or internal FC disks in E[3-6]000 machines through the
  5.8555 +  Interface Board). You'll probably need the microcode from the
  5.8556 +  Solaris driver to make it work.
  5.8557 +
  5.8558 +  This support is also available as a module called socal.o ( = code
  5.8559 +  which can be inserted in and removed from the running kernel
  5.8560 +  whenever you want). If you want to compile it as a module, say M
  5.8561 +  here and read <file:Documentation/modules.txt>.
  5.8562 +
  5.8563 +SparcSTORAGE Array 100 and 200 series
  5.8564 +CONFIG_SCSI_PLUTO
  5.8565 +  If you never bought a disk array made by Sun, go with N.
  5.8566 +
  5.8567 +  This support is also available as a module called pluto.o ( = code
  5.8568 +  which can be inserted in and removed from the running kernel
  5.8569 +  whenever you want). If you want to compile it as a module, say M
  5.8570 +  here and read <file:Documentation/modules.txt>.
  5.8571 +
  5.8572 +Sun Enterprise Network Array (A5000 and EX500)
  5.8573 +CONFIG_SCSI_FCAL
  5.8574 +  This driver drives FC-AL disks connected through a Fibre Channel
  5.8575 +  card using the drivers/fc4 layer (currently only SOCAL). The most
  5.8576 +  common is either A5000 array or internal disks in E[3-6]000
  5.8577 +  machines.
  5.8578 +
  5.8579 +  This support is also available as a module called fcal.o ( = code
  5.8580 +  which can be inserted in and removed from the running kernel
  5.8581 +  whenever you want). If you want to compile it as a module, say M
  5.8582 +  here and read <file:Documentation/modules.txt>. If unsure, say N.
  5.8583 +
  5.8584 +Acorn SCSI card (aka30) support
  5.8585 +CONFIG_SCSI_ACORNSCSI_3
  5.8586 +  This enables support for the Acorn SCSI card (aka30). If you have an
  5.8587 +  Acorn system with one of these, say Y. If unsure, say N.
  5.8588 +
  5.8589 +Support SCSI 2 Tagged queueing
  5.8590 +CONFIG_SCSI_ACORNSCSI_TAGGED_QUEUE
  5.8591 +  Say Y here to enable tagged queuing support on the Acorn SCSI card.
  5.8592 +
  5.8593 +  This is a feature of SCSI-2 which improves performance: the host
  5.8594 +  adapter can send several SCSI commands to a device's queue even if
  5.8595 +  previous commands haven't finished yet. Some SCSI devices don't
  5.8596 +  implement this properly, so the safe answer is N.
  5.8597 +
  5.8598 +Support SCSI 2 Synchronous Transfers
  5.8599 +CONFIG_SCSI_ACORNSCSI_SYNC
  5.8600 +  Say Y here to enable synchronous transfer negotiation with all
  5.8601 +  targets on the Acorn SCSI card.
  5.8602 +
  5.8603 +  In general, this improves performance; however some SCSI devices
  5.8604 +  don't implement it properly, so the safe answer is N.
  5.8605 +
  5.8606 +ARXE SCSI support
  5.8607 +CONFIG_SCSI_ARXESCSI
  5.8608 +  Around 1991, Arxe Systems Limited released a high density floppy
  5.8609 +  disc interface for the Acorn Archimedes range, to allow the use of
  5.8610 +  HD discs from the then new A5000 on earlier models. This interface
  5.8611 +  was either sold on its own or with an integral SCSI controller.
  5.8612 +  Technical details on this NCR53c94-based device are available at
  5.8613 +  <http://www.cryton.demon.co.uk/acornbits/scsi_arxe.html>
  5.8614 +  Say Y here to compile in support for the SCSI controller.
  5.8615 +
  5.8616 +Oak SCSI support
  5.8617 +CONFIG_SCSI_OAK1
  5.8618 +  This enables support for the Oak SCSI card. If you have an Acorn
  5.8619 +  system with one of these, say Y. If unsure, say N.
  5.8620 +
  5.8621 +Cumana SCSI I support
  5.8622 +CONFIG_SCSI_CUMANA_1
  5.8623 +  This enables support for the Cumana SCSI I card. If you have an
  5.8624 +  Acorn system with one of these, say Y. If unsure, say N.
  5.8625 +
  5.8626 +Cumana SCSI II support
  5.8627 +CONFIG_SCSI_CUMANA_2
  5.8628 +  This enables support for the Cumana SCSI II card. If you have an
  5.8629 +  Acorn system with one of these, say Y. If unsure, say N.
  5.8630 +
  5.8631 +EcoSCSI support
  5.8632 +CONFIG_SCSI_ECOSCSI
  5.8633 +  This enables support for the EcoSCSI card -- a small card that sits
  5.8634 +  in the Econet socket. If you have an Acorn system with one of these,
  5.8635 +  say Y. If unsure, say N.
  5.8636 +
  5.8637 +EESOX SCSI support
  5.8638 +CONFIG_SCSI_EESOXSCSI
  5.8639 +  This enables support for the EESOX SCSI card. If you have an Acorn
  5.8640 +  system with one of these, say Y, otherwise say N.
  5.8641 +
  5.8642 +PowerTec SCSI support
  5.8643 +CONFIG_SCSI_POWERTECSCSI
  5.8644 +  This enables support for the Powertec SCSI card on Acorn systems. If
  5.8645 +  you have one of these, say Y. If unsure, say N.
  5.8646 +
  5.8647 +IEEE 1394 (FireWire) support
  5.8648 +CONFIG_IEEE1394
  5.8649 +  IEEE 1394 describes a high performance serial bus, which is also
  5.8650 +  known as FireWire(tm) or i.Link(tm) and is used for connecting all
  5.8651 +  sorts of devices (most notably digital video cameras) to your
  5.8652 +  computer.
  5.8653 +
  5.8654 +  If you have FireWire hardware and want to use it, say Y here.  This
  5.8655 +  is the core support only, you will also need to select a driver for
  5.8656 +  your IEEE 1394 adapter.
  5.8657 +
  5.8658 +  If you want to compile this as a module ( = code which can be
  5.8659 +  inserted in and removed from the running kernel whenever you want),
  5.8660 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.8661 +  will be called ieee1394.o.
  5.8662 +
  5.8663 +Texas Instruments PCILynx support
  5.8664 +CONFIG_IEEE1394_PCILYNX
  5.8665 +  Say Y here if you have an IEEE-1394 controller with the Texas
  5.8666 +  Instruments PCILynx chip.  Note: this driver is written for revision
  5.8667 +  2 of this chip and may not work with revision 0.
  5.8668 +
  5.8669 +  If you want to compile this as a module ( = code which can be
  5.8670 +  inserted in and removed from the running kernel whenever you want),
  5.8671 +  say M here and read <file:Documentation/modules.txt>.  The module
  5.8672 +  will be called pcilynx.o.
  5.8673 +
  5.8674 +Use local RAM on PCILynx board
  5.8675 +CONFIG_IEEE1394_PCILYNX_LOCALRAM
  5.8676 +  This option makes the PCILynx driver use local RAM available on some
  5.8677 +  PCILynx setups for Packet Control Lists. Local RAM is random access
  5.8678 +  memory which resides on the PCILynx board as opposed to on your
  5.8679 +  computer's motherboard. Local RAM may speed up command processing
  5.8680