patch-2.4.15 linux/Documentation/Configure.help
Next file: linux/Documentation/DocBook/via-audio.tmpl
Previous file: linux/CREDITS
Back to the patch index
Back to the overall index
- Lines: 24222
- Date:
Thu Nov 22 10:52:44 2001
- Orig file:
v2.4.14/linux/Documentation/Configure.help
- Orig date:
Mon Nov 5 15:55:25 2001
diff -u --recursive --new-file v2.4.14/linux/Documentation/Configure.help linux/Documentation/Configure.help
@@ -1,62 +1,71 @@
-# Maintained by Axel Boldt (axel@uni-paderborn.de)
+# Maintained by:
+# Eric S. Raymond <mailto:esr@thyrsus.com>
+# Steven Cole <mailto:elenstev@mesatop.com>
+#
+# Merged version 2.49: Current with 2.4.15-pre1 and 2.4.13-ac8.
#
# This version of the Linux kernel configuration help texts
# corresponds to the kernel versions 2.4.x.
#
# Translations of this file available on the WWW:
#
-# - Japanese, maintained by the JF Project (JF@linux.or.jp), at
-# http://www.linux.or.jp/JF/JFdocs/Configure.help/
-# - Russian, by kaf@linux.nevod.perm.su, at
-# http://nevod.perm.su/service/linux/doc/kernel/Configure.help
-# - French, by Pierre Tane (tanep@bigfoot.com), at
-# http://www.traduc.org/kernelfr
-# - Spanish, by Carlos Perelló Marín (fperllo@ehome.encis.es), at
-# http://visar.csustan.edu/~carlos/
-# XXX: Site has moved, new location has no Configure.help trans.
-# - Italian, by Alessandro Rubini (rubini@linux.it), at
-# ftp://ftp-pavia1.linux.it/pub/linux/Configure.help
-# XXX: ftp-pavia1.linux.it: Non-existent host/domain
-# - Polish, by Cezar Cichocki (cezar@cs.net.pl), at
-# http://www.cs.net.pl/~cezar/Kernel
-# - German, by SuSE, at http://www.suse.de/~ke/kernel . This patch
+# - Japanese, maintained by the JF Project <mailto:JF@linux.or.jp>, at
+# <http://www.linux.or.jp/JF/JFdocs/Configure.help/>
+# - Russian, by <mailto:kaf@linux.nevod.perm.su>, at
+# <http://nevod.perm.su/service/linux/doc/kernel/Configure.help>
+# - French, by Pierre Tane <mailto:tanep@bigfoot.com>, at
+# <http://www.traduc.org/kernelfr>
+# - Polish, by Dominik Mierzejewski <mailto:dmierzej@elka.pw.edu.pl>, at
+# <http://home.elka.pw.edu.pl/~dmierzej/linux/kernel/>
+# - German, by SuSE, at <http://www.suse.de/~ke/kernel>. This patch
# also includes infrastructure to support different languages.
#
# To access a document on the WWW, you need to have a direct Internet
# connection and a browser program such as netscape or lynx. If you
# only have email access, you can still use FTP and WWW servers: send
-# an email to mail-server@rtfm.mit.edu with the text
-# send usenet/news.answers/internet-services/access-via-email
+# an email to <mailto:mail-server@rtfm.mit.edu> with the text
+# send usenet/news.answers/internet-services/access-via-email
# in the body of the message.
#
# Information about what a kernel is, what it does, how to patch and
# compile it and much more is contained in the Kernel-HOWTO, available
-# at http://www.linuxdoc.org/docs.html#howto . Before you start
+# at <http://www.linuxdoc.org/docs.html#howto>. Before you start
# compiling, make sure that you have the necessary versions of all
# programs and libraries required to compile and run this kernel; they
-# are listed in the file Documentation/Changes. Make sure to read the
+# are listed in the <file:Documentation/Changes>. Make sure to read the
# toplevel kernel README file as well.
#
-# Format of this file: description<nl>variable<nl>help text<nl><nl>. If
-# the question being documented is of type "choice", we list only the
-# first occurring config variable. The help texts may contain empty
-# lines, but every non-empty line must be indented two positions.
-# Order of the help texts does not matter, however, no variable should
-# be documented twice: if it is, only the first occurrence will be
-# used by Configure. We try to keep the help texts of related variables
-# close together. Lines starting with `#' are ignored. To be nice to
-# menuconfig, limit your line length to 70 characters. Use emacs'
+# Format of this file: description<nl>variable<nl>help text<nl><nl>.
+# The help texts may contain empty lines, but every non-empty line must
+# be indented two positions. Order of the help texts does not matter,
+# however, no variable should be documented twice: if it is, only the
+# first occurrence will be used. We try to keep the help texts of related
+# variables close together. Lines starting with `#' are ignored. To be
+# nice to menuconfig, limit your line length to 70 characters. Use emacs'
# kfill.el to edit and ispell.el to spell check this file or you lose.
#
+# Comments of the form "# Choice:" followed by a menu name are used
+# internally by the maintainers' consistency-checking tools.
+#
# If you add a help text to this file, please try to be as gentle as
# possible. Don't use unexplained acronyms and generally write for the
# hypothetical ignorant but intelligent user who has just bought a PC,
# removed Windows, installed Linux and is now recompiling the kernel
-# for the first time. Tell them what to do if they're unsure. Technical
+# for the first time. Tell them what to do if they're unsure. Technical
# information should go in a README in the Documentation directory.
+#
# Mention all the relevant READMEs and HOWTOs in the help text.
+# Make them file URLs relative to the top level of the source tree so
+# that help browsers can turn them into hotlinks. All URLs ahould be
+# surrounded by <>.
+#
# Repetitions are fine since the help texts are not meant to be read
-# in sequence.
+# in sequence. It is good style to include URLs pointing to more
+# detailed technical information, pictures of the hardware, etc.
+#
+# The most important thing to include in a help entry is *motivation*.
+# Explain why someone configuring a kernel might want to select your
+# option.
#
# All this was shamelessly stolen from several different sources. Many
# thanks to all the contributors. Feel free to use these help texts in
@@ -66,21 +75,22 @@
Prompt for development and/or incomplete code/drivers
CONFIG_EXPERIMENTAL
- Some of the various things that Linux supports (such as network
- drivers, file systems, network protocols, etc.) can be in a state
- of development where the functionality, stability, or the level of
+ Some of the various things that Linux supports (such as network
+ drivers, file systems, network protocols, etc.) can be in a state
+ of development where the functionality, stability, or the level of
testing is not yet high enough for general use. This is usually
- known as the "alpha-test" phase amongst developers. If a feature is
- currently in alpha-test, then the developers usually discourage
+ known as the "alpha-test" phase among developers. If a feature is
+ currently in alpha-test, then the developers usually discourage
uninformed widespread use of this feature by the general public to
avoid "Why doesn't this work?" type mail messages. However, active
testing and use of these systems is welcomed. Just be aware that it
may not meet the normal level of reliability or it may fail to work
in some special cases. Detailed bug reports from people familiar
with the kernel internals are usually welcomed by the developers
- (before submitting bug reports, please read the documents README,
- MAINTAINERS, REPORTING-BUGS, Documentation/BUG-HUNTING, and
- Documentation/oops-tracing.txt in the kernel source).
+ (before submitting bug reports, please read the documents
+ <file:README>, <file:MAINTAINERS>, <file:REPORTING-BUGS>,
+ <file:Documentation/BUG-HUNTING>, and
+ <file:Documentation/oops-tracing.txt> in the kernel source).
This option will also make obsoleted drivers available. These are
drivers that have been replaced by something else, and/or are
@@ -89,11 +99,18 @@
Unless you intend to help test and develop a feature or driver that
falls into this category, or you have a situation that requires
using these features, you should probably say N here, which will
- cause this configure script to present you with fewer choices. If
+ cause the configurator to present you with fewer choices. If
you say Y here, you will be offered the choice of using features or
drivers that are currently considered to be in the alpha-test phase.
-Symmetric Multi Processing
+Prompt for drivers for obsolete features and hardware
+CONFIG_OBSOLETE
+ Obsolete drivers have usually been replaced by more recent software
+ that can talk to the same hardware. Obsolete hardware is things
+ like MGA monitors that you are very unlikely to see on today's
+ systems.
+
+Symmetric Multi-Processing support
CONFIG_SMP
This enables support for systems with more than one CPU. If you have
a system with only one CPU, like most personal computers, say N. If
@@ -114,12 +131,106 @@
Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
Management" code will be disabled if you say Y here.
- See also the files Documentation/smp.tex, Documentation/smp.txt,
- Documentation/i386/IO-APIC.txt, Documentation/nmi_watchdog.txt and the
- SMP-FAQ on the WWW at http://www.irisa.fr/prive/mentre/smp-faq/ .
-
+ See also the <file:Documentation/smp.tex>,
+ <file:Documentation/smp.txt>, <file:Documentation/i386/IO-APIC.txt>,
+ <file:Documentation/nmi_watchdog.txt> and the SMP-FAQ on the WWW at
+ <http://www.irisa.fr/prive/mentre/smp-faq/>.
+
If you don't know what to do here, say N.
+Intel or compatible 80x86 processor
+CONFIG_X86
+ This is Linux's home port. Linux was originally native to the Intel
+ 386, and runs on all the later x86 processors including the Intel
+ 486, 586, Pentiums, and various instruction-set-compatible chips by
+ AMD, Cyrix, and others.
+
+Alpha processor
+CONFIG_ALPHA
+ The Alpha is a 64-bit general-purpose processor designed and
+ marketed by the Digital Equipment Corporation of blessed memory, now
+ Compaq. Alpha Linux dates from 1995-1996 and was the first non-x86
+ port. The Alpha Linux project has a home page at
+ <http://www.alphalinux.org/>.
+
+32-bit Sun Sparc
+CONFIG_SPARC32
+ SPARC is a family of RISC microprocessors designed and marketed by
+ Sun Microsystems, incorporated. They are very widely found in Sun
+ workstations and clones. This port covers the original 32-bit SPARC;
+ it is old and stable and usually considered one of the "big three"
+ along with the Intel and Alpha ports. The UltraLinux project
+ maintains both the SPARC32 and SPARC64 ports; its web page is
+ available at <http://www.ultralinux.org/>.
+
+64-bit Sun Sparc
+CONFIG_SPARC64
+ SPARC is a family of RISC microprocessors designed and marketed by
+ Sun Microsystems, incorporated. This port covers the newer 64-bit
+ UltraSPARC. The UltraLinux project maintains both the SPARC32 and
+ SPARC64 ports; its web page is available at
+ <http://www.ultralinux.org/>.
+
+Power PC processor
+CONFIG_PPC
+ The PowerPC is a very capable 32-bit RISC processor from Motorola,
+ the successor to their 68000 and 88000 series. It powers recent
+ Macintoshes and also a widely-used series of single-board computers
+ from Motorola. The Linux PowerPC port has a home page at
+ <http://penguinppc.org/>.
+
+Motorola 68K processors
+CONFIG_M68K
+ The Motorola 68K microprocessors are now obsolete, having been
+ superseded by the PowerPC line also from Motorola. But they powered
+ the first wave of workstation hardware in the 1980s, including Sun
+ workstations; they were also the basis of the original Amiga and
+ later Atari personal computers. A lot of this hardware is still
+ around. The m68k project has a home page at
+ <http://www.linux-m68k.org/>.
+
+ARM processors
+CONFIG_ARM
+ The ARM series is a line of low-power-consumption RISC chip designs
+ licensed by ARM ltd and targeted at embedded applications and
+ handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
+ manufactured, but legacy ARM-based PC hardware remains popular in
+ Europe. There is an ARM Linux project with a web page at
+ <http://www.arm.linux.org.uk/>.
+
+SuperH processors
+CONFIG_SUPERH
+ The SuperH is a RISC processor targeted for use in embedded systems
+ and consumer electronics; it was also used in the Sega Dreamcast
+ gaming console. The SuperH port has a home page at
+ <http://www.sh-linux.org/>.
+
+IA64 processors, including Intel Itanium
+CONFIG_IA64
+ The Itanium is Intel's 64-bit successor to the 32-bit X86 line. As
+ of early 2001 it is not yet in widespread production use. The Linux
+ IA-64 project has a home page at <http://www.linuxia64.org/>.
+
+HP PA-RISC processor
+CONFIG_PARISC
+ The PA-RISC microprocessor is a RISC chip designed by
+ Hewlett-Packard and used in their line of workstations. The PA-RISC
+ Linux project has a home page at <www.parisc-linux.org>.
+
+IBM System/390
+CONFIG_S390
+ Linux now runs on the venerable System/390 mainframe from IBM, in a
+ guest partition under VM. In fact, over 40,000 simultaneous Linux
+ images have been run on a single mainframe! The S390 Linux project
+ has a home page at <http://linux.s390.org/>.
+
+Axis Communications ETRAX 100LX embedded network CPU
+CONFIG_CRIS
+ Linux has been ported to run on the Axis Communications ETRAX 100LX
+ CPU and the single-board computers built around it, targeted for
+ network and embedded applications. For more information see the
+ Axis Communication site, <http://developer.axis.com/>.
+
Multiquad support for NUMA systems
CONFIG_MULTIQUAD
This option is used for getting Linux to run on a (IBM/Sequent) NUMA
@@ -127,7 +238,7 @@
and uses Clustered Logical APIC addressing mode instead of Flat Logical.
You will need a new lynxer.elf file to flash your firmware with - send
email to Martin.Bligh@us.ibm.com
-
+
IO-APIC Support on Uniprocessors
CONFIG_X86_UP_IOAPIC
An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
@@ -160,7 +271,7 @@
a math coprocessor built in, 486SX and 386 do not, unless you added
a 487DX or 387, respectively. (The messages during boot time can
give you some hints here ["man dmesg"].) Everyone needs either a
- coprocessor or this emulation.
+ coprocessor or this emulation.
If you don't have a math coprocessor, you need to say Y here; if you
say Y here even though you have a coprocessor, the coprocessor will
@@ -172,7 +283,7 @@
intend to use this kernel on different machines.
More information about the internals of the Linux math coprocessor
- emulation can be found in arch/i386/math-emu/README.
+ emulation can be found in <file:arch/i386/math-emu/README>.
If you are not sure, say Y; apart from resulting in a 66 KB bigger
kernel, it won't hurt.
@@ -211,12 +322,13 @@
functions. You may choose to use both, but the Timer LED function
will overrule the CPU usage LED.
-Kernel FP software completion (EXPERIMENTAL)
+Kernel FP software completion
CONFIG_MATHEMU
This option is required for IEEE compliant floating point arithmetic
on the Alpha. The only time you would ever not say Y is to say M in
order to debug the code. Say Y unless you know what you are doing.
+# Choice: himem
High Memory support
CONFIG_NOHIGHMEM
Linux can use up to 64 Gigabytes of physical memory on x86 systems.
@@ -248,23 +360,45 @@
auto detected or can be forced by using a kernel command line option
such as "mem=256M". (Try "man bootparam" or see the documentation of
your boot loader (lilo or loadlin) about how to pass options to the
- kernel at boot time.)
+ kernel at boot time.)
If unsure, say "off".
+4GB
+CONFIG_HIGHMEM4G
+ Select this if you have a 32-bit processor and between 1 and 4
+ gigabytes of physical RAM.
+
+64GB
+CONFIG_HIGHMEM64G
+ Select this if you have a 32-bit processor and more than 4
+ gigabytes of physical RAM.
+
Normal PC floppy disk support
CONFIG_BLK_DEV_FD
If you want to use the floppy disk drive(s) of your PC under Linux,
say Y. Information about this driver, especially important for IBM
- Thinkpad users, is contained in Documentation/floppy.txt. That file
- also contains the location of the Floppy driver FAQ as well as
- location of the fdutils package used to configure additional
+ Thinkpad users, is contained in <file:Documentation/floppy.txt>.
+ That file also contains the location of the Floppy driver FAQ as
+ well as location of the fdutils package used to configure additional
parameters of the driver at run time.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called floppy.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
+
+iSeries Virtual I/O Disk Support
+CONFIG_VIODASD
+ If you are running on an iSeries system and you want to use
+ virtual disks created and managed by OS/400, say Y.
+
+iSeries Virtual I/O Disk IDE Emulation
+CONFIG_VIODASD_IDE
+ This causes the iSeries virtual disks to look like IDE disks.
+ If you have programs or utilities that only support certain
+ kinds of disks, this option will cause iSeries virtual disks
+ to pretend to be IDE disks, which may satisfy the program.
Support for PowerMac floppy
CONFIG_MAC_FLOPPY
@@ -278,15 +412,15 @@
write to it and do all the other things that you can do with normal
block devices (such as hard drives). It is usually used to load and
store a copy of a minimal root file system off of a floppy into RAM
- during the initial install of Linux.
+ during the initial install of Linux.
Note that the kernel command line option "ramdisk=XX" is now
- obsolete. For details, read Documentation/ramdisk.txt.
+ obsolete. For details, read <file:Documentation/ramdisk.txt>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M and read Documentation/modules.txt. The module will be called
- rd.o.
+ say M and read <file:Documentation/modules.txt>. The module will be
+ called rd.o.
Most normal users won't need the RAM disk functionality, and can
thus say N here.
@@ -301,15 +435,15 @@
The initial RAM disk is a RAM disk that is loaded by the boot loader
(loadlin or lilo) and that is mounted as root before the normal boot
procedure. It is typically used to load modules needed to mount the
- "real" root file system, etc. See Documentation/initrd.txt for
- details.
+ "real" root file system, etc. See <file:Documentation/initrd.txt>
+ for details.
-Loop device support
+Loopback device support
CONFIG_BLK_DEV_LOOP
Saying Y here will allow you to use a regular file as a block
device; you can then create a file system on that block device and
mount it just as you would mount other block devices such as hard
- drive partitions, CDROM drives or floppy drives. The loop devices
+ drive partitions, CD-ROM drives or floppy drives. The loop devices
are block special device files with major number 7 and typically
called /dev/loop0, /dev/loop1 etc.
@@ -318,7 +452,7 @@
writing them to floppy. Furthermore, some Linux distributions avoid
the need for a dedicated Linux partition by keeping their complete
root file system inside a DOS FAT file using this loop device
- driver.
+ driver.
The loop device driver can also be used to "hide" a file system in a
disk partition, floppy, or regular file, either using encryption
@@ -326,58 +460,58 @@
bits of, say, a sound file). This is also safe if the file resides
on a remote file server. If you want to do this, you will first have
to acquire and install a kernel patch from
- ftp://ftp.kerneli.org/pub/kerneli/ , and then you need to
+ <ftp://ftp.kerneli.org/pub/kerneli/>, and then you need to
say Y to this option.
Note that alternative ways to use encrypted file systems are
provided by the cfs package, which can be gotten from
- ftp://ftp.kerneli.org/pub/kerneli/net-source/ , and the newer tcfs
- package, available at http://tcfs.dia.unisa.it/ . You do not need to
- say Y here if you want to use one of these. However, using cfs
+ <ftp://ftp.kerneli.org/pub/kerneli/net-source/>, and the newer tcfs
+ package, available at <http://tcfs.dia.unisa.it/>. You do not need
+ to say Y here if you want to use one of these. However, using cfs
requires saying Y to "NFS file system support" below while using
tcfs requires applying a kernel patch. An alternative steganography
solution is provided by StegFS, also available from
- ftp://ftp.kerneli.org/pub/kerneli/net-source/ .
+ <ftp://ftp.kerneli.org/pub/kerneli/net-source/>.
To use the loop device, you need the losetup utility and a recent
version of the mount program, both contained in the util-linux
package. The location and current version number of util-linux is
- contained in the file Documentation/Changes.
+ contained in the file <file:Documentation/Changes>.
Note that this loop device has nothing to do with the loopback
device used for network connections from the machine to itself.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called loop.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called loop.o.
Most users will answer N here.
-Network Block Device support
+Network block device support
CONFIG_BLK_DEV_NBD
Saying Y here will allow your computer to be a client for network
block devices, i.e. it will be able to use block devices exported by
servers (mount file systems on them etc.). Communication between
client and server works over TCP/IP networking, but to the client
program this is hidden: it looks like a regular local file access to
- a block device special file such as /dev/nd0.
+ a block device special file such as /dev/nd0.
Network block devices also allows you to run a block-device in
userland (making server and client physically the same computer,
communicating using the loopback network device).
-
- Read Documentation/nbd.txt for more information, especially about
- where to find the server code, which runs in user space and does not
- need special kernel support.
+
+ Read <file:Documentation/nbd.txt> for more information, especially
+ about where to find the server code, which runs in user space and
+ does not need special kernel support.
Note that this has nothing to do with the network file systems NFS
or Coda; you can say N here even if you intend to use NFS or Coda.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called nbd.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called nbd.o.
If unsure, say N.
@@ -385,16 +519,16 @@
CONFIG_IDE
If you say Y here, your kernel will be able to manage low cost mass
storage units such as ATA/(E)IDE and ATAPI units. The most common
- cases are IDE hard drives and ATAPI CDROM drives.
+ cases are IDE hard drives and ATAPI CD-ROM drives.
If your system is pure SCSI and doesn't use these interfaces, you
can say N here.
-
+
Integrated Disk Electronics (IDE aka ATA-1) is a connecting standard
for mass storage units such as hard disks. It was designed by
Western Digital and Compaq Computer in 1984. It was then named
ST506. Quite a number of disks use the IDE interface.
-
+
AT Attachment (ATA) is the superset of the IDE specifications.
ST506 was also called ATA-1.
@@ -407,22 +541,22 @@
ATA/IDE standards by means of fast DMA controllers.
ATA Packet Interface (ATAPI) is a protocol used by EIDE tape and
- CDROM drives, similar in many respects to the SCSI protocol.
-
+ CD-ROM drives, similar in many respects to the SCSI protocol.
+
SMART IDE (Self Monitoring, Analysis and Reporting Technology) was
designed in order to prevent data corruption and disk crash by
detecting pre hardware failure conditions (heat, access time, and
- the like...). Disks built since June 1995 may follow this
- standard. The kernel itself don't manage this; however there are
- quite a number of user programs such as smart that can query the
- status of SMART parameters disk.
+ the like...). Disks built since June 1995 may follow this standard.
+ The kernel itself don't manage this; however there are quite a
+ number of user programs such as smart that can query the status of
+ SMART parameters disk.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called ide.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called ide.o.
- For further information, please read Documentation/ide.txt.
+ For further information, please read <file:Documentation/ide.txt>.
If unsure, say Y.
@@ -436,21 +570,21 @@
Useful information about large (>540 MB) IDE disks, multiple
interfaces, what to do if ATA/IDE devices are not automatically
detected, sound card ATA/IDE ports, module support, and other
- topics, is contained in Documentation/ide.txt. For detailed
+ topics, is contained in <file:Documentation/ide.txt>. For detailed
information about hard drives, consult the Disk-HOWTO and the
Multi-Disk-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
To fine-tune ATA/IDE drive/interface parameters for improved
performance, look for the hdparm package at
- http://www.ibiblio.org/pub/Linux/system/hardware .
+ <http://www.ibiblio.org/pub/Linux/system/hardware>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt and
- Documentation/ide.txt. The module will be called ide-mod.o. Do not
- compile this driver as a module if your root file system (the one
- containing the directory /) is located on an IDE device.
+ say M here and read <file:Documentation/modules.txt> and
+ <file:Documentation/ide.txt>. The module will be called ide-mod.o.
+ Do not compile this driver as a module if your root file system (the
+ one containing the directory /) is located on an IDE device.
If you have one or more IDE drives, say Y or M here. If your system
has no IDE drives, or if memory requirements are really tight, you
@@ -467,42 +601,42 @@
since it lacks the enhanced functionality of the new one. This makes
it a good choice for systems with very tight memory restrictions, or
for systems with only older MFM/RLL/ESDI drives. Choosing the old
- driver can save 13 KB or so of kernel memory.
+ driver can save 13 KB or so of kernel memory.
If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
instead of this one. For more detailed information, read the
Disk-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
Use old disk-only driver on primary interface
CONFIG_BLK_DEV_HD_IDE
- There are two drivers for MFM/RLL/IDE disks. Most people use just
- the new enhanced driver by itself. This option however installs the
+ There are two drivers for MFM/RLL/IDE disks. Most people use just
+ the new enhanced driver by itself. This option however installs the
old hard disk driver to control the primary IDE/disk interface in
the system, leaving the new enhanced IDE driver to take care of only
- the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from
- having an IDE/ATAPI CDROM or tape drive connected to the primary IDE
- interface. Choosing this option may be useful for older systems
+ the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from
+ having an IDE/ATAPI CD-ROM or tape drive connected to the primary
+ IDE interface. Choosing this option may be useful for older systems
which have MFM/RLL/ESDI controller+drives at the primary port
address (0x1f0), along with IDE drives at the secondary/3rd/4th port
- addresses.
+ addresses.
Normally, just say N here; you will then use the new driver for all
4 interfaces.
Include IDE/ATA-2 DISK support
CONFIG_BLK_DEV_IDEDISK
- This will include enhanced support for MFM/RLL/IDE hard disks. If
+ This will include enhanced support for MFM/RLL/IDE hard disks. If
you have a MFM/RLL/IDE disk, and there is no special reason to use
- the old hard disk driver instead, say Y. If you have an SCSI-only
+ the old hard disk driver instead, say Y. If you have an SCSI-only
system, you can say N here.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called ide-disk.o. Do not compile this driver as a module if your
- root file system (the one containing the directory /) is located on
- the IDE disk. If unsure, say Y.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called ide-disk.o. Do not compile this driver as a module
+ if your root file system (the one containing the directory /) is
+ located on the IDE disk. If unsure, say Y.
Use multi-mode by default
CONFIG_IDEDISK_MULTI_MODE
@@ -513,38 +647,43 @@
If in doubt, say N.
-Include IDE/ATAPI CDROM support
+PCMCIA IDE support
+CONFIG_BLK_DEV_IDECS
+ Support for outboard IDE disks, tape drives, and CD-ROM drives
+ connected through a PCMCIA card.
+
+Include IDE/ATAPI CD-ROM support
CONFIG_BLK_DEV_IDECD
- If you have a CDROM drive using the ATAPI protocol, say Y. ATAPI is
- a newer protocol used by IDE CDROM and TAPE drives, similar to the
- SCSI protocol. Most new CDROM drives use ATAPI, including the
+ If you have a CD-ROM drive using the ATAPI protocol, say Y. ATAPI is
+ a newer protocol used by IDE CD-ROM and TAPE drives, similar to the
+ SCSI protocol. Most new CD-ROM drives use ATAPI, including the
NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
double(2X) or better speed drives.
- If you say Y here, the CDROM drive will be identified at boot time
+ If you say Y here, the CD-ROM drive will be identified at boot time
along with other IDE devices, as "hdb" or "hdc", or something
similar (check the boot messages with dmesg). If this is your only
- CDROM drive, you can say N to all other CDROM options, but be sure
- to say Y or M to "ISO 9660 CDROM file system support".
+ CD-ROM drive, you can say N to all other CD-ROM options, but be sure
+ to say Y or M to "ISO 9660 CD-ROM file system support".
- Read the CDROM-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto and the file
- Documentation/cdrom/ide-cd. Note that older versions of lilo (the
- Linux boot loader) cannot properly deal with IDE/ATAPI CDROMs, so
- install lilo-16 or higher, available from
- ftp://metalab.unc.edu/pub/Linux/system/boot/lilo .
+ Read the CD-ROM-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto> and
+ <file:Documentation/cdrom/ide-cd>. Note that older versions of lilo
+ (the Linux boot loader) cannot properly deal with IDE/ATAPI CD-ROMs,
+ so install lilo-16 or higher, available from
+ <ftp://metalab.unc.edu/pub/Linux/system/boot/lilo>.
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called ide-cd.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called ide-cd.o.
Include IDE/ATAPI TAPE support
CONFIG_BLK_DEV_IDETAPE
If you have an IDE tape drive using the ATAPI protocol, say Y.
- ATAPI is a newer protocol used by IDE tape and CDROM drives, similar
- to the SCSI protocol. If you have an SCSI tape drive however, you
- can say N here.
+ ATAPI is a newer protocol used by IDE tape and CD-ROM drives,
+ similar to the SCSI protocol. If you have an SCSI tape drive
+ however, you can say N here.
You should also say Y if you have an OnStream DI-30 tape drive; this
will not work with the SCSI protocol, until there is support for the
@@ -553,27 +692,27 @@
If you say Y here, the tape drive will be identified at boot time
along with other IDE devices, as "hdb" or "hdc", or something
similar, and will be mapped to a character device such as "ht0"
- (check the boot messages with dmesg). Be sure to consult the
- drivers/ide/ide-tape.c and Documentation/ide.txt files for usage
- information.
+ (check the boot messages with dmesg). Be sure to consult the
+ <file:drivers/ide/ide-tape.c> and <file:Documentation/ide.txt> files
+ for usage information.
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called ide-tape.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called ide-tape.o.
Include IDE/ATAPI FLOPPY support
CONFIG_BLK_DEV_IDEFLOPPY
If you have an IDE floppy drive which uses the ATAPI protocol,
- answer Y. ATAPI is a newer protocol used by IDE CDROM/tape/floppy
- drives, similar to the SCSI protocol.
+ answer Y. ATAPI is a newer protocol used by IDE CD-ROM/tape/floppy
+ drives, similar to the SCSI protocol.
The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by
this driver. For information about jumper settings and the question
of when a ZIP drive uses a partition table, see
- http://www.win.tue.nl/~aeb/linux/zip/zip-1.html .
+ <http://www.win.tue.nl/~aeb/linux/zip/zip-1.html>.
(ATAPI PD-CD/CDR drives are not supported by this driver; support
- for PD-CD/CDR drives is available if you answer Y to
+ for PD-CD/CDR drives is available if you answer Y to
"SCSI emulation support", below).
If you say Y here, the FLOPPY drive will be identified along with
@@ -582,8 +721,8 @@
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called ide-floppy.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called ide-floppy.o.
SCSI emulation support
CONFIG_BLK_DEV_IDESCSI
@@ -625,7 +764,7 @@
conditions. Say Y here to include code which tries to automatically
detect and correct the problems under Linux. This option also
enables access to the secondary IDE ports in some CMD640 based
- systems.
+ systems.
This driver will work automatically in PCI based systems (most new
systems have PCI slots). But if your system uses VESA local bus
@@ -636,15 +775,15 @@
The CMD640 chip is also used on add-in cards by Acculogic, and on
the "CSA-6400E PCI to IDE controller" that some people have. For
- details, read Documentation/ide.txt.
+ details, read <file:Documentation/ide.txt>.
CMD640 enhanced support
CONFIG_BLK_DEV_CMD640_ENHANCED
This option includes support for setting/autotuning PIO modes and
- prefetch on CMD640 IDE interfaces. For details, read
- Documentation/ide.txt. If you have a CMD640 IDE interface and your
- BIOS does not already do this for you, then say Y here. Otherwise
- say N.
+ prefetch on CMD640 IDE interfaces. For details, read
+ <file:Documentation/ide.txt>. If you have a CMD640 IDE interface
+ and your BIOS does not already do this for you, then say Y here.
+ Otherwise say N.
RZ1000 chipset bugfix/support
CONFIG_BLK_DEV_RZ1000
@@ -654,14 +793,14 @@
severe data corruption under many conditions. Say Y here to include
code which automatically detects and corrects the problem under
Linux. This may slow disk throughput by a few percent, but at least
- things will operate 100% reliably.
+ things will operate 100% reliably.
Generic PCI IDE chipset support
CONFIG_BLK_DEV_IDEPCI
Say Y here for PCI systems which use IDE drive(s).
This option helps the IDE driver to automatically detect and
configure all PCI-based IDE interfaces in your system.
-
+
Support for sharing PCI IDE interrupts
CONFIG_IDEPCI_SHARE_IRQ
Some ATA/IDE chipsets have hardware support which allows for
@@ -681,14 +820,14 @@
for these drives, but you can change that by saying Y to the
following question "Use DMA by default when available". You can get
the latest version of the hdparm utility from
- ftp://metalab.unc.edu/pub/Linux/system/hardware/ .
+ <ftp://metalab.unc.edu/pub/Linux/system/hardware/>.
- Read the comments at the beginning of drivers/ide/ide-dma.c and
- the file Documentation/ide.txt for more information.
+ Read the comments at the beginning of <file:drivers/ide/ide-dma.c>
+ and the file <file:Documentation/ide.txt> for more information.
It is safe to say Y to this question.
-Good-Bad DMA Model-Firmware (EXPERIMENTAL)
+Good-Bad DMA Model-Firmware (WIP)
CONFIG_IDEDMA_NEW_DRIVE_LISTINGS
If you say Y here, the model and firmware revision of your drive
will be compared against a blacklist of buggy drives that claim to
@@ -701,6 +840,16 @@
If in doubt, say N.
+Attempt to HACK around Chipsets that TIMEOUT (WIP)
+CONFIG_BLK_DEV_IDEDMA_TIMEOUT
+ If you say Y here, this is a NASTY UGLY HACK!
+
+ We have to issue an abort and requeue the request DMA engine got
+ turned off by a goofy ASIC, and we have to clean up the mess, and
+ here is as good as any. Do it globally for all chipsets.
+
+ If in doubt, say N.
+
Boot off-board chipsets first support
CONFIG_BLK_DEV_OFFBOARD
Normally, IDE controllers built into the motherboard (on-board
@@ -722,7 +871,7 @@
If in doubt, say N.
-Use DMA by default when available
+Use PCI DMA by default when available
CONFIG_IDEDMA_PCI_AUTO
Prior to kernel version 2.1.112, Linux used to automatically use
DMA for IDE drives and chipsets which support it. Due to concerns
@@ -738,29 +887,45 @@
IGNORE word93 Validation BITS
CONFIG_IDEDMA_IVB
- Since various rules were applied and created ... et al. as it relates
- the detection of valid cable signals. This is a result of unclear terms
- in ATA-4 and ATA-5 standards.
+ There are unclear terms is ATA-4 and ATA-5 standards how certain
+ hardware (an 80c ribbon) should be detected. Different interpretations
+ of the standards have been released in hardware. This causes problems:
+ for example, a host with Ultra Mode 4 (or higher) will not run
+ in that mode with an 80c ribbon.
+
+ If you are experiencing compatibility or performance problems, you
+ MAY try to answering Y here. However, it does not necessarily solve
+ any of your problems, it could even cause more of them.
It is normally safe to answer Y; however, the default is N.
-Various ATA, Work(s) In Progress (EXPERIMENTAL)
+ATA Work(s) In Progress (EXPERIMENTAL)‹
CONFIG_IDEDMA_PCI_WIP
If you enable this you will be able to use and test highly
- developmental projects. If you say N, this configure script will
+ developmental projects. If you say N, the configurator will
simply skip those options.
It is SAFEST to say N to this question.
+Asyncronious DMA support (EXPERIMENTAL)
+CONFIG_BLK_DEV_ADMA
+ Please read the comments at the top of
+ <file:drivers/ide/ide-adma.c>.
+
+Pacific Digital A-DMA support (EXPERIMENTAL)
+CONFIG_BLK_DEV_PDC_ADMA
+ Please read the comments at the top of <file:drivers/ide/pdcadma.c>.
+
3ware Hardware ATA-RAID support
CONFIG_BLK_DEV_3W_XXXX_RAID
3ware is the only hardware ATA-Raid product in Linux to date.
This card is 2,4, or 8 channel master mode support only.
SCSI support required!!!
- http://www.3ware.com/
+ <http://www.3ware.com/>
- Please read the comments at the top of drivers/scsi/3w-xxxx.c
+ Please read the comments at the top of
+ <file:drivers/scsi/3w-xxxx.c>.
AEC62XX chipset support
CONFIG_BLK_DEV_AEC62XX
@@ -774,13 +939,13 @@
The ATP860 is an UltraDMA 66 chipset base.
The ATP860M(acintosh) version is an UltraDMA 66 chipset base.
- Please read the comments at the top of drivers/ide/aec62xx.c
- If you say Y here, then say Y to "Use DMA by default when available" as
- well.
+ Please read the comments at the top of <file:drivers/ide/aec62xx.c>.
+ If you say Y here, then say Y to "Use DMA by default when available"
+ as well.
AEC62XX Tuning support
CONFIG_AEC62XX_TUNING
- Please read the comments at the top of drivers/ide/aec62xx.c
+ Please read the comments at the top of <file:drivers/ide/aec62xx.c>.
If unsure, say N.
ALI M15x3 chipset support
@@ -790,8 +955,8 @@
normal dual channel support.
If you say Y here, you also need to say Y to "Use DMA by default
- when available", above.
- Please read the comments at the top of drivers/ide/alim15x3.c
+ when available", above. Please read the comments at the top of
+ <file:drivers/ide/alim15x3.c>.
If unsure, say N.
@@ -806,20 +971,21 @@
Using this option can allow WDC drives to run at ATA-4/5 transfer
rates with only an ATA-2 support structure.
- SAY NO!
+ SAY N!
-AMD7409 chipset support
-CONFIG_BLK_DEV_AMD7409
- This driver ensures (U)DMA support for the AMD756 Viper chipset.
+AMD Viper support
+CONFIG_BLK_DEV_AMD74XX
+ This driver ensures (U)DMA support for the AMD756/760 Viper
+ chipsets.
If you say Y here, you also need to say Y to "Use DMA by default
when available", above.
- Please read the comments at the top of drivers/ide/amd7409.c
+ Please read the comments at the top of <file:drivers/ide/amd74xx.c>.
If unsure, say N.
-AMD Viper ATA-66 Override support (WIP)
-CONFIG_AMD7409_OVERRIDE
+AMD Viper ATA-66 Override (WIP)
+CONFIG_AMD74XX_OVERRIDE
This option auto-forces the ata66 flag.
This effect can be also invoked by calling "idex=ata66"
If unsure, say N.
@@ -858,8 +1024,8 @@
HPT34X AUTODMA support (WIP)
CONFIG_HPT34X_AUTODMA
This is a dangerous thing to attempt currently! Please read the
- comments at the top of drivers/ide/hpt34x.c If you say Y here,
- then say Y to "Use DMA by default when available" as well.
+ comments at the top of <file:drivers/ide/hpt34x.c>. If you say Y
+ here, then say Y to "Use DMA by default when available" as well.
If unsure, say N.
@@ -868,9 +1034,9 @@
HPT366 is an Ultra DMA chipset for ATA-66.
HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
HPT370 is an Ultra DMA chipset for ATA-100.
-
+
This driver adds up to 4 more EIDE devices sharing a single
- interrupt.
+ interrupt.
The HPT366 chipset in its current form is bootable. One solution
for this problem are special LILO commands for redirecting the
@@ -884,21 +1050,22 @@
ide-probe at boot. It is reported to support DVD II drives, by the
manufacturer.
-NS87415 support (EXPERIMENTAL)
+NS87415 chipset support (EXPERIMENTAL)
CONFIG_BLK_DEV_NS87415
This driver adds detection and support for the NS87415 chip
(used in SPARC64, among others).
- Please read the comments at the top of drivers/ide/ns87415.c.
+ Please read the comments at the top of <file:drivers/ide/ns87415.c>.
-OPTi 82C621 enhanced support (EXPERIMENTAL)
+OPTi 82C621 chipset enhanced support (EXPERIMENTAL)
CONFIG_BLK_DEV_OPTI621
This is a driver for the OPTi 82C621 EIDE controller.
- Please read the comments at the top of drivers/ide/opti621.c.
+ Please read the comments at the top of <file:drivers/ide/opti621.c>.
-ServerWorks OSB4 chipset support (EXPERIMENTAL)
-CONFIG_BLK_DEV_OSB4
- This driver adds PIO/DMA support for the Serverworks OSB4 chipset
+ServerWorks OSB4/CSB5 chipset support
+CONFIG_BLK_DEV_SVWKS
+ This driver adds PIO/(U)DMA support for the ServerWorks OSB4/CSB5
+ chipsets.
Intel PIIXn chipsets support
CONFIG_BLK_DEV_PIIX
@@ -907,7 +1074,7 @@
PIO 0-4 mode settings, this allows dynamic tuning of the chipset
via the standard end-user tool 'hdparm'.
- Please read the comments at the top of drivers/ide/piix.c.
+ Please read the comments at the top of <file:drivers/ide/piix.c>.
If you say Y here, you should also say Y to "PIIXn Tuning support",
below.
@@ -926,29 +1093,30 @@
If unsure, say N.
-PROMISE PDC20246/PDC20262/PDC20267 support
+PROMISE PDC20246/PDC20262/PDC20265/PDC20267/PDC20268 support
CONFIG_BLK_DEV_PDC202XX
Promise Ultra33 or PDC20246
Promise Ultra66 or PDC20262
- Promise Ultra100 or PDC20265/PDC20267
+ Promise Ultra100 or PDC20265/PDC20267/PDC20268
This driver adds up to 4 more EIDE devices sharing a single
interrupt. This add-on card is a bootable PCI UDMA controller. Since
multiple cards can be installed and there are BIOS ROM problems that
happen if the BIOS revisions of all installed cards (three-max) do
not match, the driver attempts to do dynamic tuning of the chipset
- at boot-time for max-speed. Ultra33 BIOS 1.25 or newer is required
+ at boot-time for max-speed. Ultra33 BIOS 1.25 or newer is required
for more than one card. This card may require that you say Y to
- "Special UDMA Feature (EXPERIMENTAL)".
+ "Special UDMA Feature".
If you say Y here, you need to say Y to "Use DMA by default when
available" as well.
- Please read the comments at the top of drivers/ide/pdc202xx.c
+ Please read the comments at the top of
+ <file:drivers/ide/pdc202xx.c>.
If unsure, say N.
-Special UDMA Feature (EXPERIMENTAL)
+Special UDMA Feature
CONFIG_PDC202XX_BURST
For PDC20246, PDC20262, PDC20265 and PDC20267 Ultra DMA chipsets.
Designed originally for PDC20246/Ultra33 that has BIOS setup
@@ -956,10 +1124,15 @@
Unknown for PDC20265/PDC20267 Ultra DMA 100.
- Please read the comments at the top of drivers/ide/pdc202xx.c
+ Please read the comments at the top of
+ <file:drivers/ide/pdc202xx.c>.
If unsure, say N.
+Special FastTrak Feature
+CONFIG_PDC202XX_FORCE
+ For FastTrak enable overriding BIOS.
+
SiS5513 chipset support
CONFIG_BLK_DEV_SIS5513
This driver ensures (U)DMA support for SIS5513 chipset based
@@ -969,20 +1142,21 @@
If you say Y here, you need to say Y to "Use DMA by default when
available" as well.
- Please read the comments at the top of drivers/ide/sis5513.c
+ Please read the comments at the top of <file:drivers/ide/sis5513.c>.
SLC90E66 chipset support
CONFIG_BLK_DEV_SLC90E66
This driver ensures (U)DMA support for Victroy66 SouthBridges for
SMsC with Intel NorthBridges. This is an Ultra66 based chipset.
The nice thing about it is that you can mix Ultra/DMA/PIO devices
- and it will handle timing cycles. Since this is an improved look-a-like
- to the PIIX4 it should be a nice addition.
+ and it will handle timing cycles. Since this is an improved
+ look-a-like to the PIIX4 it should be a nice addition.
If you say Y here, you need to say Y to "Use DMA by default when
available" as well.
- Please read the comments at the top of drivers/ide/slc90e66.c
+ Please read the comments at the top of
+ <file:drivers/ide/slc90e66.c>.
Winbond SL82c105 support
CONFIG_BLK_DEV_SL82C105
@@ -990,35 +1164,34 @@
special configuration for this chip. This is common on various CHRP
motherboards, but could be used elsewhere. If in doubt, say Y.
-Tekram TRM290 chipset support (EXPERIMENTAL)
+Tekram TRM290 chipset support
CONFIG_BLK_DEV_TRM290
This driver adds support for bus master DMA transfers
using the Tekram TRM290 PCI IDE chip. Volunteers are
needed for further tweaking and development.
- Please read the comments at the top of drivers/ide/trm290.c.
+ Please read the comments at the top of <file:drivers/ide/trm290.c>.
VIA82CXXX chipset support
CONFIG_BLK_DEV_VIA82CXXX
This allows you to configure your chipset for a better use while
- running (U)DMA: it will allow you to enable efficiently the second
- channel dma usage, as it may not be set by BIOS. It allows you to
- pass a kernel command line at boot time in order to set fifo
- config. If no command line is provided, it will try to set fifo
- configuration at its best. It will allow you to get information from
- /proc/ide/via provided you enabled "proc" support.
+ running PIO/(U)DMA, it will allow you to enable efficiently the
+ second channel dma usage, as it may not be set by BIOS. It will try
+ to set fifo configuration at its best. It will allow you to get
+ information from /proc/ide/via provided you enabled "/proc file
+ system" support.
- Please read the comments at the top of drivers/ide/via82cxxx.c
+ Please read the comments at the top of
+ <file:drivers/ide/via82cxxx.c>.
If you say Y here, then say Y to "Use DMA by default when available"
as well.
If unsure, say N.
-VIA82CXXX Tuning support (WIP)
-CONFIG_VIA82CXXX_TUNING
- Please read the comments at the top of drivers/ide/via82cxxx.c
-
- If unsure, say N.
+RapIDE interface support
+CONFIG_BLK_DEV_IDE_RAPIDE
+ Say Y here if you want to support the Yellowstone RapIDE controller
+ manufactured for use with Acorn computers.
Other IDE chipset support
CONFIG_IDE_CHIPSETS
@@ -1030,9 +1203,9 @@
setting of higher speed I/O rates to improve system performance with
these chipsets. Most of these also require special kernel boot
parameters to actually turn on the support at runtime; you can find
- a list of these in the file Documentation/ide.txt.
-
- People with SCSI-only systems can say N here.
+ a list of these in the file <file:Documentation/ide.txt>.
+
+ People with SCSI-only systems can say N here.
Generic 4 drives/port support
CONFIG_BLK_DEV_4DRIVES
@@ -1045,53 +1218,64 @@
ALI M14xx support
CONFIG_BLK_DEV_ALI14XX
This driver is enabled at runtime using the "ide0=ali14xx" kernel
- boot parameter. It enables support for the secondary IDE interface
+ boot parameter. It enables support for the secondary IDE interface
of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
- I/O speeds to be set as well. See the files Documentation/ide.txt
- and drivers/ide/ali14xx.c for more info.
+ I/O speeds to be set as well. See the files
+ <file:Documentation/ide.txt> and <file:drivers/ide/ali14xx.c> for
+ more info.
DTC-2278 support
CONFIG_BLK_DEV_DTC2278
This driver is enabled at runtime using the "ide0=dtc2278" kernel
boot parameter. It enables support for the secondary IDE interface
of the DTC-2278 card, and permits faster I/O speeds to be set as
- well. See the Documentation/ide.txt and drivers/ide/dtc2278.c
- files for more info.
+ well. See the <file:Documentation/ide.txt> and
+ <file:drivers/ide/dtc2278.c> files for more info.
Holtek HT6560B support
CONFIG_BLK_DEV_HT6560B
This driver is enabled at runtime using the "ide0=ht6560b" kernel
boot parameter. It enables support for the secondary IDE interface
of the Holtek card, and permits faster I/O speeds to be set as well.
- See the Documentation/ide.txt and drivers/ide/ht6560b.c files for
- more info.
+ See the <file:Documentation/ide.txt> and
+ <file:drivers/ide/ht6560b.c> files for more info.
PROMISE DC4030 support (EXPERIMENTAL)
CONFIG_BLK_DEV_PDC4030
This driver provides support for the secondary IDE interface and
- cache of Promise IDE chipsets, e.g. DC4030 and DC5030. This driver
+ cache of Promise IDE chipsets, e.g. DC4030 and DC5030. This driver
is known to incur timeouts/retries during heavy I/O to drives
- attached to the secondary interface. CDROM and TAPE devices are not
- supported yet. This driver is enabled at runtime using the
- "ide0=dc4030" kernel boot parameter. See the Documentation/ide.txt
- and drivers/ide/pdc4030.c files for more info.
+ attached to the secondary interface. CD-ROM and TAPE devices are
+ not supported yet. This driver is enabled at runtime using the
+ "ide0=dc4030" kernel boot parameter. See the
+ <file:Documentation/ide.txt> and <file:drivers/ide/pdc4030.c> files
+ for more info.
+# This is for Linus's tree.
QDI QD6580 support
CONFIG_BLK_DEV_QD6580
This driver is enabled at runtime using the "ide0=qd6580" kernel
- boot parameter. It permits faster I/O speeds to be set. See the
- files Documentation/ide.txt and drivers/ide/qd6580.c for more
- info.
+ boot parameter. It permits faster I/O speeds to be set. See the
+ <file:Documentation/ide.txt> and <file:drivers/ide/qd6580.c> for
+ more info.
+
+# This is for Alan's tree. Note the name difference.
+QDI QD65XX support
+CONFIG_BLK_DEV_QD65XX
+ This driver is enabled at runtime using the "ide0=qd65xx" kernel
+ boot parameter. It permits faster I/O speeds to be set. See the
+ <file:Documentation/ide.txt> and <file:drivers/ide/qd65xx.c> for
+ more info.
UMC 8672 support
CONFIG_BLK_DEV_UMC8672
This driver is enabled at runtime using the "ide0=umc8672" kernel
boot parameter. It enables support for the secondary IDE interface
of the UMC-8672, and permits faster I/O speeds to be set as well.
- See the files Documentation/ide.txt and drivers/ide/umc8672.c for
- more info.
+ See the files <file:Documentation/ide.txt> and
+ <file:drivers/ide/umc8672.c> for more info.
-Amiga builtin Gayle IDE interface support
+Amiga Gayle IDE interface support
CONFIG_BLK_DEV_GAYLE
This is the IDE driver for the builtin IDE interface on some Amiga
models. It supports both the `A1200 style' (used in A600 and A1200)
@@ -1107,11 +1291,11 @@
disks, CD-ROM drives, etc.) that are connected to the builtin IDE
interface.
-Amiga Buddha/Catweasel IDE interface support (EXPERIMENTAL)
+Amiga Buddha/Catweasel/X-Surf IDE interface support (EXPERIMENTAL)
CONFIG_BLK_DEV_BUDDHA
- This is the IDE driver for the IDE interfaces on the Buddha and
- Catweasel expansion boards. It supports up to two interfaces on the
- Buddha and three on the Catweasel.
+ This is the IDE driver for the IDE interfaces on the Buddha,
+ Catweasel and X-Surf expansion boards. It supports up to two interfaces
+ on the Buddha, three on the Catweasel and two on the X-Surf.
Say Y if you have a Buddha or Catweasel expansion board and want to
use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
@@ -1131,10 +1315,16 @@
Say Y if you have an IDE doubler. The driver is enabled at kernel
runtime using the "ide=doubler" kernel boot parameter.
-Support for PowerMac IDE devices (must also enable IDE)
+WarpEngine SCSI support
+CONFIG_WARPENGINE_SCSI
+ Support for MacroSystem Development's WarpEngine Amiga SCSI-2
+ controller. Info at
+ <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>.
+
+Builtin PowerMac IDE support
CONFIG_BLK_DEV_IDE_PMAC
- This driver provides support for the built-in IDE controller on most
- of the recent Apple Power Macintoshes and PowerBooks.
+ This driver provides support for the built-in IDE controller on
+ most of the recent Apple Power Macintoshes and PowerBooks.
If unsure, say Y.
PowerMac IDE DMA support
@@ -1164,29 +1354,6 @@
devices (hard disks, CD-ROM drives, etc.) that are connected to the
builtin IDE interface.
-MPC8xx IDE support
-CONFIG_BLK_DEV_MPC8xx_IDE
- This option provides support for IDE on Motorola MPC8xx Systems.
- Please see 'Type of MPC8xx IDE interface' for details.
-
- If unsure, say N.
-
-Type of MPC8xx IDE interface
-CONFIG_IDE_8xx_PCCARD
- Select how the IDE devices are connected to the MPC8xx system:
-
- 8xx_PCCARD uses the 8xx internal PCMCIA interface in combination
- with a PC Card (e.g. ARGOSY portable Hard Disk Adapter),
- ATA PC Card HDDs or ATA PC Flash Cards (example: TQM8xxL
- systems)
-
- 8xx_DIRECT is used for directly connected IDE devices using the 8xx
- internal PCMCIA interface (example: IVMS8 systems)
-
- EXT_DIRECT is used for IDE devices directly connected to the 8xx
- bus using some glue logic, but _not_ the 8xx internal
- PCMCIA interface (example: IDIF860 systems)
-
ICS IDE interface support
CONFIG_BLK_DEV_IDE_ICSIDE
On Acorn systems, say Y here if you wish to use the ICS IDE
@@ -1212,12 +1379,12 @@
XT hard disk support
CONFIG_BLK_DEV_XD
Very old 8 bit hard disk controllers used in the IBM XT computer
- will be supported if you say Y here.
+ will be supported if you say Y here.
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called xd.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called xd.o.
It's pretty unlikely that you have one of these: say N.
@@ -1225,23 +1392,23 @@
CONFIG_BLK_DEV_PS2
Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
hard disk.
-
+
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called ps2esdi.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called ps2esdi.o.
Mylex DAC960/DAC1100 PCI RAID Controller support
CONFIG_BLK_DEV_DAC960
This driver adds support for the Mylex DAC960, AcceleRAID, and
- eXtremeRAID PCI RAID controllers. See the file
- Documentation/README.DAC960 for further information about this
- driver.
+ eXtremeRAID PCI RAID controllers. See the file
+ <file:Documentation/README.DAC960> for further information about
+ this driver.
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called DAC960.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called DAC960.o.
Parallel port IDE device support
CONFIG_PARIDE
@@ -1249,7 +1416,7 @@
your computer's parallel port. Most of them are actually IDE devices
using a parallel port IDE adapter. This option enables the PARIDE
subsystem which contains drivers for many of these external drives.
- Read Documentation/paride.txt for more information.
+ Read <file:Documentation/paride.txt> for more information.
If you have said Y to the "Parallel-port support" configuration
option, you may share a single port between your printer and other
@@ -1270,13 +1437,13 @@
Parallel port IDE disks
CONFIG_PARIDE_PD
- This option enables the high-level driver for IDE-type disk devices
- connected through a parallel port. If you chose to build PARIDE
- support into your kernel, you may answer Y here to build in the
- parallel port IDE driver, otherwise you should answer M to build
- it as a loadable module. The module will be called pd.o. You
- must also have at least one parallel port protocol driver in your
- system. Among the devices supported by this driver are the SyQuest
+ This option enables the high-level driver for IDE-type disk devices
+ connected through a parallel port. If you chose to build PARIDE
+ support into your kernel, you may answer Y here to build in the
+ parallel port IDE driver, otherwise you should answer M to build
+ it as a loadable module. The module will be called pd.o. You
+ must also have at least one parallel port protocol driver in your
+ system. Among the devices supported by this driver are the SyQuest
EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack
hard drives from MicroSolutions.
@@ -1291,8 +1458,8 @@
system. Among the devices supported by this driver are the
MicroSolutions backpack CD-ROM drives and the Freecom Power CD. If
you have such a CD-ROM drive, you should also say Y or M to "ISO
- 9660 CDROM file system support" below, because that's the file
- system used on CDROMs.
+ 9660 CD-ROM file system support" below, because that's the file
+ system used on CD-ROMs.
Parallel port ATAPI disks
CONFIG_PARIDE_PF
@@ -1322,7 +1489,7 @@
This option enables a special high-level driver for generic ATAPI
devices connected through a parallel port. The driver allows user
programs, such as cdrecord, to send ATAPI commands directly to a
- device.
+ device.
If you chose to build PARIDE support into your kernel, you may
answer Y here to build in the parallel port generic ATAPI driver,
@@ -1333,10 +1500,10 @@
your system.
This driver implements an API loosely related to the generic SCSI
- driver. See include/linux/pg.h for details.
+ driver. See <file:include/linux/pg.h>. for details.
You can obtain the most recent version of cdrecord from
- ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/ . Versions 1.6.1a3 and
+ <ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/>. Versions 1.6.1a3 and
later fully support this driver.
ATEN EH-100 protocol
@@ -1352,39 +1519,40 @@
Micro Solutions BACKPACK Series 5 protocol
CONFIG_PARIDE_BPCK
- This option enables support for the Micro Solutions BACKPACK parallel
- port Series 5 IDE protocol. (Most BACKPACK drives made before 1999 were
- Series 5) Series 5 drives will NOT always have the Series noted on the
- bottom of the drive. Series 6 drivers will.
+ This option enables support for the Micro Solutions BACKPACK
+ parallel port Series 5 IDE protocol. (Most BACKPACK drives made
+ before 1999 were Series 5) Series 5 drives will NOT always have the
+ Series noted on the bottom of the drive. Series 6 drivers will.
In other words, if your BACKPACK drive dosen't say "Series 6" on the
bottom, enable this option.
- If you chose to build PARIDE support into your kernel, you may answer Y
- here to build in the protocol driver, otherwise you should answer M to
- build it as a loadable module. The module will be called bpck.o. You
- must also have a high-level driver for the type of device that you want
- to support.
+ If you chose to build PARIDE support into your kernel, you may
+ answer Y here to build in the protocol driver, otherwise you should
+ answer M to build it as a loadable module. The module will be
+ called bpck.o. You must also have a high-level driver for the type
+ of device that you want to support.
Micro Solutions BACKPACK Series 6 protocol
CONFIG_PARIDE_BPCK6
- This option enables support for the Micro Solutions BACKPACK parallel
- port Series 6 IDE protocol. (Most BACKPACK drives made after 1999 were
- Series 6) Series 6 drives will have the Series noted on the bottom of
- the drive. Series 5 drivers don't always have it noted.
+ This option enables support for the Micro Solutions BACKPACK
+ parallel port Series 6 IDE protocol. (Most BACKPACK drives made
+ after 1999 were Series 6) Series 6 drives will have the Series noted
+ on the bottom of the drive. Series 5 drivers don't always have it
+ noted.
- In other words, if your BACKPACK drive says "Series 6" on the bottom,
- enable this option.
+ In other words, if your BACKPACK drive says "Series 6" on the
+ bottom, enable this option.
- If you chose to build PARIDE support into your kernel, you may answer Y
- here to build in the protocol driver, otherwise you should answer M to
- build it as a loadable module. The module will be called bpck6.o. You
- must also have a high-level driver for the type of device that you want
- to support.
+ If you chose to build PARIDE support into your kernel, you may
+ answer Y here to build in the protocol driver, otherwise you should
+ answer M to build it as a loadable module. The module will be
+ called bpck6.o. You must also have a high-level driver for the type
+ of device that you want to support.
DataStor Commuter protocol
CONFIG_PARIDE_COMM
- This option enables support for the Commuter parallel port IDE
+ This option enables support for the Commuter parallel port IDE
protocol from DataStor. If you chose to build PARIDE support
into your kernel, you may answer Y here to build in the protocol
driver, otherwise you should answer M to build it as a loadable
@@ -1393,7 +1561,7 @@
DataStor EP-2000 protocol
CONFIG_PARIDE_DSTR
- This option enables support for the EP-2000 parallel port IDE
+ This option enables support for the EP-2000 parallel port IDE
protocol from DataStor. If you chose to build PARIDE support
into your kernel, you may answer Y here to build in the protocol
driver, otherwise you should answer M to build it as a loadable
@@ -1412,7 +1580,7 @@
have a high-level driver for the type of device that you want to
support.
-Shuttle EPAT c7/c8 extension
+Shuttle EPAT c7/c8 extension
CONFIG_PARIDE_EPATC8
This option enables support for the newer Shuttle EP1284 (aka c7 and
c8) chip. You need this if you are using any recent Imation SuperDisk
@@ -1453,12 +1621,12 @@
Freecom IQ ASIC-2 protocol
CONFIG_PARIDE_FRIQ
This option enables support for version 2 of the Freecom IQ parallel
- port IDE adapter. This adapter is used by the Maxell Superdisk
+ port IDE adapter. This adapter is used by the Maxell Superdisk
drive. If you chose to build PARIDE support into your kernel, you
may answer Y here to build in the protocol driver, otherwise you
should answer M to build it as a loadable module. The module will be
called friq.o. You must also have a high-level driver for the type
- of device that you want to support.
+ of device that you want to support.
FreeCom power protocol
CONFIG_PARIDE_FRPW
@@ -1493,12 +1661,12 @@
OnSpec 90c20 protocol
CONFIG_PARIDE_ON20
- This option enables support for the (obsolete) 90c20 parallel port
+ This option enables support for the (obsolete) 90c20 parallel port
IDE protocol from OnSpec (often marketed under the ValuStore brand
- name). If you chose to build PARIDE support into your kernel, you
- may answer Y here to build in the protocol driver, otherwise you
- should answer M to build it as a loadable module. The module will
- be called on20.o. You must also have a high-level driver for the
+ name). If you chose to build PARIDE support into your kernel, you
+ may answer Y here to build in the protocol driver, otherwise you
+ should answer M to build it as a loadable module. The module will
+ be called on20.o. You must also have a high-level driver for the
type of device that you want to support.
OnSpec 90c26 protocol
@@ -1522,13 +1690,19 @@
to new capacity needs. Logical volumes are accessed as block
devices named /dev/VolumeGroupName/LogicalVolumeName.
- For details see Documentation/LVM-HOWTO. You will need supporting
- user space software; location is in Documentation/Changes.
+ For details see <file:Documentation/LVM-HOWTO>. You will need
+ supporting user space software; location is in
+ <file:Documentation/Changes>.
If you want to compile this support as a module ( = code which can
be inserted in and removed from the running kernel whenever you
- want), say M here and read Documentation/modules.txt. The module
- will be called lvm-mod.o.
+ want), say M here and read <file:Documentation/modules.txt>. The
+ module will be called lvm-mod.o.
+
+Multiple devices driver support (RAID and LVM)
+CONFIG_MD
+ Support multiple physical spindles through a single logical device.
+ Required for RAID and logical volume management (LVM).
Multiple devices driver support
CONFIG_BLK_DEV_MD
@@ -1543,7 +1717,7 @@
More information about Software RAID on Linux is contained in the
Software-RAID mini-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . There you will also
+ <http://www.linuxdoc.org/docs.html#howto>. There you will also
learn where to get the supporting user space utilities raidtools.
If unsure, say N.
@@ -1552,12 +1726,12 @@
CONFIG_MD_LINEAR
If you say Y here, then your multiple devices driver will be able to
use the so-called linear mode, i.e. it will combine the hard disk
- partitions by simply appending one to the other.
+ partitions by simply appending one to the other.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called linear.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called linear.o.
If unsure, say Y.
@@ -1567,40 +1741,40 @@
use the so-called raid0 mode, i.e. it will combine the hard disk
partitions into one logical device in such a fashion as to fill them
up evenly, one chunk here and one chunk there. This will increase
- the throughput rate if the partitions reside on distinct disks.
+ the throughput rate if the partitions reside on distinct disks.
Information about Software RAID on Linux is contained in the
Software-RAID mini-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . There you will also
+ <http://www.linuxdoc.org/docs.html#howto>. There you will also
learn where to get the supporting user space utilities raidtools.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called raid0.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called raid0.o.
If unsure, say Y.
RAID-1 (mirroring) mode
CONFIG_MD_RAID1
A RAID-1 set consists of several disk drives which are exact copies
- of each other. In the event of a mirror failure, the RAID driver
+ of each other. In the event of a mirror failure, the RAID driver
will continue to use the operational mirrors in the set, providing
an error free MD (multiple device) to the higher levels of the
- kernel. In a set with N drives, the available space is the capacity
+ kernel. In a set with N drives, the available space is the capacity
of a single drive, and the set protects against a failure of (N - 1)
- drives.
+ drives.
Information about Software RAID on Linux is contained in the
Software-RAID mini-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . There you will also
+ <http://www.linuxdoc.org/docs.html#howto>. There you will also
learn where to get the supporting user space utilities raidtools.
If you want to use such a RAID-1 set, say Y. This code is also
available as a module called raid1.o ( = code which can be inserted
- in and removed from the running kernel whenever you want). If you
+ in and removed from the running kernel whenever you want). If you
want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ <file:Documentation/modules.txt>.
If unsure, say Y.
@@ -1616,41 +1790,92 @@
Information about Software RAID on Linux is contained in the
Software-RAID mini-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . There you will also
+ <http://www.linuxdoc.org/docs.html#howto>. There you will also
learn where to get the supporting user space utilities raidtools.
If you want to use such a RAID-4/RAID-5 set, say Y. This code is
also available as a module called raid5.o ( = code which can be
inserted in and removed from the running kernel whenever you want).
If you want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ <file:Documentation/modules.txt>.
If unsure, say Y.
+Multipath I/O support
+CONFIG_MD_MULTIPATH
+ Multipath-IO is the ability of certain devices to address the same
+ physical disk over multiple 'IO paths'. The code ensures that such
+ paths can be defined and handled at runtime, and ensures that a
+ transparent failover to the backup path(s) happens if a IO errors
+ arrives on the primary path.
+
+ If unsure, say N.
+
+# AC tree only
+Support for IDE Raid controllers
+CONFIG_BLK_DEV_ATARAID
+ Say Y or M if you have an IDE Raid controller and want linux
+ to use its softwareraid feature. You must also select an
+ appropriate for your board low-level driver below.
+
+ Note, that Linux does not use the Raid implemetation in BIOS, and
+ the main purpose for this feature is to retain compatibility and
+ data integrity with other OS-es, using the same disk array. Linux
+ has its own Raid drivers, which you should use if you need better
+ performance.
+
+# AC tree only
+Support Promise software RAID (Fasttrak(tm))
+CONFIG_BLK_DEV_ATARAID_PDC
+ Say Y or M if you have a Promise Fasttrak (tm) Raid controller
+ and want linux to use the softwareraid feature of this card.
+ This driver uses /dev/ataraid/dXpY (X and Y numbers) as device
+ names.
+
+ If you choose to compile this as a module, the module will be called
+ pdcraid.o.
+
+# AC tree only
+Highpoint 370 software RAID
+CONFIG_BLK_DEV_ATARAID_HPT
+ Say Y or M if you have a Highpoint HPT 370 Raid controller
+ and want linux to use the softwareraid feature of this card.
+ This driver uses /dev/ataraid/dXpY (X and Y numbers) as device
+ names.
+
+ If you choose to compile this as a module, the module will be called
+ hptraid.o.
+
Support for Acer PICA 1 chipset
CONFIG_ACER_PICA_61
This is a machine with a R4400 133/150 MHz CPU. To compile a Linux
kernel that runs on these, say Y here. For details about Linux on
the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
- http://oss.sgi.com/mips .
+ <http://oss.sgi.com/mips>.
Support for Algorithmics P4032 (EXPERIMENTAL)
CONFIG_ALGOR_P4032
- This is an evaluation board of the British company Algorithmics. The
- board uses the R4300 and a R5230 CPUs. For more information about
- this board see http://www.algor.co.uk .
+ This is an evaluation board of the British company Algorithmics.
+ The board uses the R4300 and a R5230 CPUs. For more information
+ about this board see <http://www.algor.co.uk>.
Support for BAGET MIPS series
CONFIG_BAGET_MIPS
- This enables support for the Baget, a Russian embedded system. For
- more details about the Baget see the Linux/MIPS FAQ on
- http://oss.sgi.com/mips .
+ This enables support for the Baget, a Russian embedded system. For
+ more details about the Baget see the Linux/MIPS FAQ on
+ <http://oss.sgi.com/mips>.
+
+Baget AMD LANCE support
+CONFIG_BAGETLANCE
+ Say Y to enable kernel support for AMD Lance Ethernet cards on the
+ MIPS-32-based Baget embedded system. This chipset is better known
+ via the NE2100 cards.
Support for DECstations
CONFIG_DECSTATION
This enables support for DEC's MIPS based workstations. For details
- see the Linux/MIPS FAQ on http://oss.sgi.com/mips and the
- DECstation porting pages on http://decstation.unix-ag.org .
+ see the Linux/MIPS FAQ on <http://oss.sgi.com/mips> and the
+ DECstation porting pages on <http://decstation.unix-ag.org>.
If you have one of the following DECstation Models you definitely
want to choose R4xx0 for the CPU Type:
@@ -1662,6 +1887,25 @@
otherwise choose R3000.
+Support for Cobalt Micro Server
+CONFIG_COBALT_MICRO_SERVER
+ Support for MIPS-based Cobalt boxes (they have been bought by Sun
+ and are now the "Server Appliance Business Unit") including the 2700
+ series -- versions 1 of the Qube and Raq. To compile a Linux kernel
+ for this hardware, say Y here.
+
+Support for Cobalt 2800
+CONFIG_COBALT_28
+ Support for the second generation of MIPS-based Cobalt boxes (they
+ have been bought by Sun and are now the "Server Appliance Business
+ Unit") including the 2800 series -- versions 2 of the Qube and Raq.
+ To compile a Linux kernel for this hardware, say Y here.
+
+Support for the Momentum Computer Ocelot SBC
+CONFIG_MOMENCO_OCELOT
+ The Ocelot is a MIPS-based Single Board Computer (SBC) made by
+ Momentum Computer <http://www.momenco.com>.
+
Support for NEC DDB Vrc-5074
CONFIG_DDB5074
This enables support for the VR5000-based NEC DDB Vrc-5074
@@ -1673,10 +1917,18 @@
evaluation board.
Features : kernel debugging, serial terminal, NFS root fs, on-board
- ether port (with a patch to tulip driver), IDE controller, PS2 keyboard
- PS2 mouse, etc.
+ ether port (Need an additional patch at <http://linux.junsun.net>),
+ USB, AC97, PCI, PCI VGA card & framebuffer console, IDE controller,
+ PS2 keyboard, PS2 mouse, etc.
+
+Support for NEC DDB Vrc-5477
+CONFIG_DDB5477
+ This enables support for the R5432-based NEC DDB Vrc-5477
+ evaluation board.
- TODO : USB, Compact-PCI interface.
+ Features : kernel debugging, serial terminal, NFS root fs, on-board
+ ether port (Need an additional patch at <http://linux.junsun.net>),
+ USB, AC97, PCI, etc.
Support for MIPS Atlas board
CONFIG_MIPS_ATLAS
@@ -1688,19 +1940,39 @@
This enables support for the VR5000-based MIPS Malta evaluation
board.
+Support for Galileo Evaluation board or CoSine Orion
+CONFIG_ORION
+ Say Y if configuring for the Galileo evaluation board
+ or CoSine Orion. More information is available at
+ <http://tochna.technion.ac.il/project/linux/html/linux.html>.
+
+ Otherwise, say N.
+
Support for Mips Magnum 4000
CONFIG_MIPS_MAGNUM_4000
This is a machine with a R4000 100 MHz CPU. To compile a Linux
kernel that runs on these, say Y here. For details about Linux on
the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
- http://oss.sgi.com/mips.
+ <http://oss.sgi.com/mips>.
+
+Enable Qtronix 990P Keyboard Support
+CONFIG_QTRONIX_KEYBOARD
+ Images of Qtronix keyboards are at
+ <http://www.qtronix.com/keyboard.html>.
Support for Olivetti M700
CONFIG_OLIVETTI_M700
This is a machine with a R4000 100 MHz CPU. To compile a Linux
kernel that runs on these, say Y here. For details about Linux on
the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
- http://oss.sgi.com/mips.
+ <http://oss.sgi.com/mips>.
+
+Support for SNI RM200 PCI
+CONFIG_SNI_RM200_PCI
+ The SNI RM200 PCI was a MIPS-based platform manufactured by Siemens
+ Nixdorf Informationssysteme (SNI), parent company of Pyramid
+ Technology and now in turn merged with Fujitsu. Say Y here to
+ support this machine type.
Support for SGI IP22
CONFIG_SGI_IP22
@@ -1709,6 +1981,7 @@
that runs on these, say Y here.
Support for SGI IP27
+CONFIG_SGI_IP27
This are the SGI Origin 200, Origin 2000 and Onyx 2 Graphics
workstations. To compile a Linux kernel that runs on these, say Y
here.
@@ -1731,11 +2004,49 @@
4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
systems.
+MIPS GT96100 support
+CONFIG_MIPS_GT96100
+ Say Y here to support the Galileo Technology GT96100 communications
+ controller card. There is a web page at <http://www.galileot.com/>.
+
+MIPS GT96100 Ethernet support
+CONFIG_MIPS_GT96100ETH
+ Say Y here to support the Ethernet subsystem on your GT96100 card.
+
+Zalon SCSI support
+CONFIG_SCSI_ZALON
+ The Zalon is an interface chip that sits between the PA-RISC
+ processor and the NCR 53c720 SCSI controller on K-series PA-RISC
+ boards (these are used, among other places, on some HP 780
+ workstations). Say Y here to make sure it gets initialized
+ correctly before the Linux kernel tries to talk to the controller.
+
Kernel floating-point instruction emulation
CONFIG_MIPS_FPU_EMULATOR
- This option enables the MIPS software floatingpoint support. Due to the
- way floatingpoint works you should always enable this option unless
- you exactly know what you're doing.
+ This option enables the MIPS software floatingpoint support. Due to
+ the way floating point works you should always enable this option
+ unless you exactly know what you're doing.
+
+SGI PROM Console Support
+CONFIG_SGI_PROM_CONSOLE
+ Say Y here to set up the boot console on serial port 0.
+
+DZ11 Serial Support
+CONFIG_DZ
+ DZ11-family serial controllers for VAXstations, including the
+ DC7085, M7814, and M7819.
+
+
+TURBOchannel support
+CONFIG_TC
+ TurboChannel is a DEC (now Compaq) bus for Alpha and MIPS processors.
+ Documentation on writing device drivers for TurboChannel is available at:
+ <http://www.cs.arizona.edu/computer.help/policy/DIGITAL_unix/AA-PS3HD-TET1_html/TITLE.html>.
+
+Z85C30 Serial Support
+CONFIG_ZS
+ Documentation on the Zilog 85C350 serial communications controller
+ is downloadable at <http://www.zilog.com/pdfs/serial/z85c30.pdf>.
PCMCIA SCSI adapter support
CONFIG_SCSI_PCMCIA
@@ -1744,9 +2055,30 @@
size devices often used with laptops.
Note that the answer to this question won't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all
the questions PCMCIA SCSI host adapters.
+Adaptec APA1480 CardBus support
+CONFIG_PCMCIA_APA1480
+ Say Y here if you intend to attach this type of CardBus SCSI host
+ adapter to your computer.
+
+ This driver is also available as a module called apa1480_cb.o ( =
+ code which can be inserted in and removed from the running kernel
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
+
+NinjaSCSI-3 / NinjaSCSI-32Bi (16bit) PCMCIA support
+CONFIG_PCMCIA_NINJA_SCSI
+ If you intend to attach this type of PCMCIA SCSI host adapter to
+ your computer, say Y here and read
+ <file:Documentation/README.nsp_cs>.
+
+ This driver is also available as a module called nsp_cs.o ( =
+ code which can be inserted in and removed from the running kernel
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
+
Adaptec AHA152X PCMCIA support
CONFIG_PCMCIA_AHA152X
Say Y here if you intend to attach this type of PCMCIA SCSI host
@@ -1755,7 +2087,7 @@
This driver is also available as a module called aha152x_cs.o ( =
code which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
Qlogic PCMCIA support
CONFIG_PCMCIA_QLOGIC
@@ -1764,8 +2096,8 @@
This driver is also available as a module called qlogic_cs.o ( =
code which can be inserted in and removed from the running kernel
- whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
Future Domain PCMCIA support
CONFIG_PCMCIA_FDOMAIN
@@ -1774,27 +2106,96 @@
This driver is also available as a module called fdomain_cs.o ( =
code which can be inserted in and removed from the running kernel
- whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
-
-Adaptec APA1480 CardBus support
-CONFIG_PCMCIA_APA1480
- Say Y here if you intend to attach this type of CardBus SCSI host
- adapter to your computer.
-
- This driver is also available as a module called apa1480_cb.o ( =
- code which can be inserted in and removed from the running kernel
- whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
+# Choice: mipstype
CPU type
CONFIG_CPU_R3000
Please make sure to pick the right CPU type. Linux/MIPS is not
designed to be generic, i.e. Kernels compiled for R3000 CPUs will
- *not* work on R4000 Machines and vice versa.
- However, since most the supported Machines have an R4000 (or
- similar) CPU, R4xx0 might be a safe bet.
- If the resulting Kernel does not work try to recompile with R3000.
+ *not* work on R4000 machines and vice versa. However, since most
+ of the supported machines have an R4000 (or similar) CPU, R4x00
+ might be a safe bet. If the resulting kernel does not work,
+ try to recompile with R3000.
+
+ R3000 MIPS Technologies R3000-series processors,
+ including the 3041, 3051, and 3081.
+
+ R6000 MIPS Technologies R6000-series processors,
+ including the 64474, 64475, 64574 and 64575.
+
+ R4300 MIPS Technologies R4300-series processors.
+
+ R4x00 MIPS Technologies R4000-series processors other than 4300,
+ including the 4640, 4650, and 4700.
+
+ R5000 MIPS Technologies R5000-series processors other than the
+ Nevada.
+
+ R52xx MIPS Technologies R52xx-series ("Nevada") processors.
+
+ R10000 MIPS Technologies R10000-series processors.
+
+R6000
+CONFIG_CPU_R6000
+ MIPS Technologies R6000-series processors, including the 64474,
+ 64475, 64574 and 64575.
+
+R4300
+CONFIG_CPU_R4300
+ MIPS Technologies R4300-series processors.
+
+R4x00
+CONFIG_CPU_R4X00
+ MIPS Technologies R4000-series processors other than 4300, including
+ the 4640, 4650, and 4700.
+
+R5000
+CONFIG_CPU_R5000
+ MIPS Technologies R5000-series processors other than the Nevada.
+
+R52x0
+CONFIG_CPU_NEVADA
+ MIPS Technologies R52x0-series ("Nevada") processors.
+
+R8000
+CONFIG_CPU_R8000
+ MIPS Technologies R8000-series processors.
+
+R10000
+CONFIG_CPU_R10000
+ MIPS Technologies R10000-series processors.
+
+Discontiguous Memory Support
+CONFIG_DISCONTIGMEM
+ Say Y to upport efficient handling of discontiguous physical memory,
+ for architectures which are either NUMA (Non-Uniform Memory Access)
+ or have huge holes in the physical address space for other reasons.
+ See <file:Documentation/vm/numa> for more.
+
+Mapped kernel support
+CONFIG_MAPPED_KERNEL
+ Change the way a Linux kernel is loaded unto memory on a MIPS64
+ machine. This is required in order to support text replication and
+ NUMA. If you need to undersatand it, read the source code.
+
+Kernel text replication support
+CONFIG_REPLICATE_KTEXT
+ Say Y here to enable replicating the kernel text across multiple
+ nodes in a NUMA cluster. This trades memory for speed.
+
+Exception handler replication support
+CONFIG_REPLICATE_EXHANDLERS
+ Say Y here to enable replicating the kernel exception handlers
+ across multiple nodes in a NUMA cluster. This trades memory for
+ speed.
+
+NUMA support?
+CONFIG_NUMA
+ Say Y to compile the kernel to support NUMA (Non-Uniform Memory
+ Access). This option is for configuring high-end multiprocessor
+ server machines. If in doubt, say N.
CPU type
CONFIG_CPU_VR41XX
@@ -1805,14 +2206,18 @@
CPU feature configuration
CONFIG_CPU_ADVANCED
- Saying yes here allows you to select support for various features your
- CPU may or may not have. Most people should say N here.
+ Saying yes here allows you to select support for various features
+ your CPU may or may not have. Most people should say N here.
-ll and sc instructions
+ll/sc Instructions available
CONFIG_CPU_HAS_LLSC
- Say Y here if your CPU has the ll and sc instructions. Say Y here for
- better performance, N if you don't know. You must say Y here for
- multiprocessor machines.
+ MIPS R4000 series and later provide the Load Linked (ll)
+ and Store Conditional (sc) instructions. More information is
+ available at <http://www.go-ecs.com/mips/miptek1.htm>.
+
+ Say Y here if your CPU has the ll and sc instructions. Say Y here
+ for better performance, N if you don't know. You must say Y here
+ for multiprocessor machines.
lld and scd instructions
CONFIG_CPU_HAS_LLDSCD
@@ -1820,7 +2225,7 @@
equivalents of ll and sc. Say Y here for better performance, N if
you don't know. You must say Y here for multiprocessor machines.
-Support for writebuffer flushing
+Writeback Buffer available
CONFIG_CPU_HAS_WB
Say N here for slightly better performance. You must say Y here for
machines which require flushing of write buffers in software. Saying
@@ -1840,6 +2245,12 @@
byte order. These modes require different kernels. Say Y if your
machine is little endian, N if it's a big endian machine.
+Use power LED as a heartbeat
+CONFIG_HEARTBEAT
+ Use the power-on LED on your machine as a load meter. The exact
+ behavior is platform-dependent, but normally the flash frequency is
+ a hyperbolic function of the 5-minute load average.
+
Networking support
CONFIG_NET
Unless you really know what you are doing, you should say Y here.
@@ -1849,27 +2260,28 @@
should consider updating your networking tools too because changes
in the kernel and the tools often go hand in hand. The tools are
contained in the package net-tools, the location and version number
- of which are given in Documentation/Changes.
+ of which are given in <file:Documentation/Changes>.
For a general introduction to Linux networking, it is highly
recommended to read the NET-3-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
Socket filtering
CONFIG_FILTER
The Linux Socket Filter is derived from the Berkeley Packet Filter.
If you say Y here, user-space programs can attach a filter to any
socket and thereby tell the kernel that it should allow or disallow
- certain types of data to get through the socket. Linux Socket
- Filtering works on all socket types except TCP for now. See the text
- file Documentation/networking/filter.txt for more information.
+ certain types of data to get through the socket. Linux Socket
+ Filtering works on all socket types except TCP for now. See the
+ text file <file:Documentation/networking/filter.txt> for more
+ information.
You need to say Y here if you want to use PPP packet filtering
(see the CONFIG_PPP_FILTER option below).
If unsure, say N.
-Network packet filtering
+Network packet filtering (replaces ipchains)
CONFIG_NETFILTER
Netfilter is a framework for filtering and mangling network packets
that pass through your Linux box.
@@ -1912,21 +2324,21 @@
Various modules exist for netfilter which replace the previous
masquerading (ipmasqadm), packet filtering (ipchains), transparent
proxying, and portforwarding mechanisms. Please see
- Documentation/Changes under "iptables" for the location of these
- packages.
-
+ <file:Documentation/Changes> under "iptables" for the location of
+ these packages.
+
Make sure to say N to "Fast switching" below if you intend to say Y
here, as Fast switching currently bypasses netfilter.
-
+
Chances are that you should say Y here if you compile a kernel which
will run as a router and N for regular hosts. If unsure, say N.
-
+
Network packet filtering debugging
CONFIG_NETFILTER_DEBUG
You can say Y here if you want to get additional messages useful in
- debugging the netfilter code.
+ debugging the netfilter code.
-IP: connection tracking (required for masq/NAT)
+Connection tracking (required for masq/NAT)
CONFIG_IP_NF_CONNTRACK
Connection tracking keeps a record of what packets have passed
through your machine, in order to figure out how they are related
@@ -1938,7 +2350,7 @@
below).
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
IRC Send/Chat support
CONFIG_IP_NF_IRC
@@ -1961,17 +2373,17 @@
of Network Address Translation on them.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `Y'.
+ <file:Documentation/modules.txt>. If unsure, say `Y'.
-IP: user space queueing via NETLINK (EXPERIMENTAL)
+User space queueing via NETLINK
CONFIG_IP_NF_QUEUE
Netfilter has the ability to queue packets to user space: the
netlink device can be used to access them using this driver.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
-IP: ip tables support (required for filtering/masq/NAT)
+IP tables support (required for filtering/masq/NAT)
CONFIG_IP_NF_IPTABLES
iptables is a general, extensible packet identification framework.
The packet filtering and full NAT (masquerading, port forwarding,
@@ -1979,41 +2391,7 @@
either of those.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
-CONFIG_IP6_NF_MATCH_LIMIT
- limit matching allows you to control the rate at which a rule can be
- matched: mainly useful in combination with the LOG target ("LOG
- target support", below) and to avoid some Denial of Service attacks.
-
- If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
-
-MAC address match support
-CONFIG_IP6_NF_MATCH_MAC
- mac matching allows you to match packets based on the source
- ethernet address of the packet.
-
- If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
-
-Multiple port match support
-CONFIG_IP6_NF_MATCH_MULTIPORT
- Multiport matching allows you to match TCP or UDP packets based on
- a series of source or destination ports: normally a rule can only
- match a single range of ports.
-
- If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
-
-Owner match support (EXPERIMENTAL)
-CONFIG_IP6_NF_MATCH_OWNER
- Packet owner matching allows you to match locally-generated packets
- based on who created them: the user, group, process or session.
-
- If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
-
-
+ <file:Documentation/modules.txt>. If unsure, say `N'.
limit match support
CONFIG_IP_NF_MATCH_LIMIT
@@ -2022,24 +2400,24 @@
target support", below) and to avoid some Denial of Service attacks.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
MAC address match support
CONFIG_IP_NF_MATCH_MAC
- mac matching allows you to match packets based on the source
- ethernet address of the packet.
+ MAC matching allows you to match packets based on the source
+ Ethernet address of the packet.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
-netfilter mark match support
+Netfilter MARK match support
CONFIG_IP_NF_MATCH_MARK
Netfilter mark matching allows you to match packets based on the
`nfmark' value in the packet. This can be set by the MARK target
(see below).
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
Multiple port match support
CONFIG_IP_NF_MATCH_MULTIPORT
@@ -2048,7 +2426,7 @@
match a single range of ports.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
TTL match support
CONFIG_IP_NF_MATCH_TTL
@@ -2064,7 +2442,7 @@
specific value or range of values.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
TOS match support
CONFIG_IP_NF_MATCH_TOS
@@ -2072,7 +2450,7 @@
Service fields of the IP packet.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
Connection state match support
CONFIG_IP_NF_MATCH_STATE
@@ -2081,23 +2459,23 @@
is a powerful tool for packet classification.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
-Unclean match support (EXPERIMENTAL)
+Unclean match support
CONFIG_IP_NF_MATCH_UNCLEAN
Unclean packet matching matches any strange or invalid packets, by
looking at a series of fields in the IP, TCP, UDP and ICMP headers.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
-Owner match support (EXPERIMENTAL)
+Owner match support
CONFIG_IP_NF_MATCH_OWNER
Packet owner matching allows you to match locally-generated packets
based on who created them: the user, group, process or session.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
Packet filtering
CONFIG_IP_NF_FILTER
@@ -2106,7 +2484,7 @@
local output. See the man page for iptables(8).
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
REJECT target support
CONFIG_IP_NF_TARGET_REJECT
@@ -2115,24 +2493,24 @@
than silently being dropped.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
-MIRROR target support (EXPERIMENTAL)
+MIRROR target support
CONFIG_IP_NF_TARGET_MIRROR
The MIRROR target allows a filtering rule to specify that an
incoming packet should be bounced back to the sender.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
-Full NAT
+Full NAT (Network Address Translation)
CONFIG_IP_NF_NAT
The Full NAT option allows masquerading, port forwarding and other
forms of full Network Address Port Translation. It is controlled by
the `nat' table in iptables: see the man page for iptables(8).
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
MASQUERADE target support
CONFIG_IP_NF_TARGET_MASQUERADE
@@ -2143,21 +2521,21 @@
address will be different on next dialup).
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
Basic SNMP-ALG support
CONFIG_IP_NF_NAT_SNMP_BASIC
- This module implements an Application Layer Gateway (ALG) for
- SNMP payloads. In conjunction with NAT, it allows a network
- management system to access multiple private networks with
- conflicting addresses. It works by modifying IP addresses
+ This module implements an Application Layer Gateway (ALG) for
+ SNMP payloads. In conjunction with NAT, it allows a network
+ management system to access multiple private networks with
+ conflicting addresses. It works by modifying IP addresses
inside SNMP payloads to match IP-layer NAT mapping.
-
+
This is the "basic" form of SNMP-ALG, as described in RFC 2962
-
+
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
REDIRECT target support
CONFIG_IP_NF_TARGET_REDIRECT
@@ -2167,7 +2545,7 @@
useful for transparent proxies.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
Packet mangling
CONFIG_IP_NF_MANGLE
@@ -2176,7 +2554,7 @@
which can effect how the packet is routed.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
TOS target support
CONFIG_IP_NF_TARGET_TOS
@@ -2185,19 +2563,19 @@
packet prior to routing.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
MARK target support
CONFIG_IP_NF_TARGET_MARK
This option adds a `MARK' target, which allows you to create rules
in the `mangle' table which alter the netfilter mark (nfmark) field
- associated with the packet packet prior to routing. This can change
- the routing method (see `IP: use netfilter MARK value as routing
+ associated with the packet prior to routing. This can change
+ the routing method (see `Use netfilter MARK value as routing
key') and can also be used by other subsystems to change their
behavior.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
TCPMSS target support
CONFIG_IP_NF_TARGET_TCPMSS
@@ -2222,16 +2600,16 @@
-j TCPMSS --clamp-mss-to-pmtu
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
-tcpmss match support
+TCPMSS match support
CONFIG_IP_NF_MATCH_TCPMSS
This option adds a `tcpmss' match, which allows you to examine the
MSS value of TCP SYN packets, which control the maximum packet size
for that connection.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
LOG target support
CONFIG_IP_NF_TARGET_LOG
@@ -2239,7 +2617,7 @@
any iptables table which records the packet header to the syslog.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
ipchains (2.2-style) support
CONFIG_IP_NF_COMPAT_IPCHAINS
@@ -2250,7 +2628,7 @@
the ipchains tool exactly as in 2.2 kernels.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
ipfwadm (2.0-style) support
CONFIG_IP_NF_COMPAT_IPFWADM
@@ -2261,51 +2639,24 @@
the ipfwadm tool exactly as in 2.0 kernels.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
-
-IP6 tables support (required for filtering/masq/NAT)
-CONFIG_IP6_NF_IPTABLES
- ip6tables is a general, extensible packet identification framework.
- Currently only the packet filtering and packet mangling subsystem
- for IPv6 use this, but connection tracking is going to follow.
- Say 'Y' or 'M' here if you want to use either of those.
-
- If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
-
-IPv6 limit match support
-CONFIG_IP6_NF_MATCH_LIMIT
- limit matching allows you to control the rate at which a rule can be
- matched: mainly useful in combination with the LOG target ("LOG
- target support", below) and to avoid some Denial of Service attacks.
-
- If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
MAC address match support
CONFIG_IP6_NF_MATCH_MAC
mac matching allows you to match packets based on the source
- ethernet address of the packet.
+ Ethernet address of the packet.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
-netfilter mark match support
+Netfilter MARK match support
CONFIG_IP6_NF_MATCH_MARK
Netfilter mark matching allows you to match packets based on the
`nfmark' value in the packet. This can be set by the MARK target
(see below).
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
-
-LOG target support
-CONFIG_IP6_NF_TARGET_LOG
- This option adds a `LOG' target, which allows you to create rules in
- any ip6tables table which records the packet header to the syslog.
-
- If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
Packet filtering
CONFIG_IP6_NF_FILTER
@@ -2314,7 +2665,7 @@
local output. See the man page for iptables(8).
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
Packet mangling
CONFIG_IP6_NF_MANGLE
@@ -2323,38 +2674,38 @@
which can effect how the packet is routed.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
MARK target support
CONFIG_IP6_NF_TARGET_MARK
This option adds a `MARK' target, which allows you to create rules
in the `mangle' table which alter the netfilter mark (nfmark) field
associated with the packet packet prior to routing. This can change
- the routing method (see `IP: use netfilter MARK value as routing
+ the routing method (see `Use netfilter MARK value as routing
key') and can also be used by other subsystems to change their
behavior.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
TCP Explicit Congestion Notification support
CONFIG_INET_ECN
Explicit Congestion Notification (ECN) allows routers to notify
clients about network congestion, resulting in fewer dropped packets
- and increased network performance. This option adds ECN support to the
- Linux kernel, as well as a sysctl (/proc/sys/net/ipv4/tcp_ecn) which
- allows ECN support to be disabled at runtime.
+ and increased network performance. This option adds ECN support to
+ the Linux kernel, as well as a sysctl (/proc/sys/net/ipv4/tcp_ecn)
+ which allows ECN support to be disabled at runtime.
Note that, on the Internet, there are many broken firewalls which
refuse connections from ECN-enabled machines, and it may be a while
- before these firewalls are fixed. Until then, to access a site behind
- such a firewall (some of which are major sites, at the time of this
- writing) you will have to disable this option, either by saying N now
- or by using the sysctl.
+ before these firewalls are fixed. Until then, to access a site
+ behind such a firewall (some of which are major sites, at the time
+ of this writing) you will have to disable this option, either by
+ saying N now or by using the sysctl.
If in doubt, say N.
-IP6 tables support (required for filtering/masq/NAT)
+IPv6 tables support (required for filtering/masq/NAT)
CONFIG_IP6_NF_IPTABLES
ip6tables is a general, extensible packet identification framework.
Currently only the packet filtering and packet mangling subsystem
@@ -2362,7 +2713,7 @@
Say 'Y' or 'M' here if you want to use either of those.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
IPv6 limit match support
CONFIG_IP6_NF_MATCH_LIMIT
@@ -2371,54 +2722,7 @@
target support", below) and to avoid some Denial of Service attacks.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
-
-MAC address match support
-CONFIG_IP6_NF_MATCH_MAC
- mac matching allows you to match packets based on the source
- ethernet address of the packet.
-
- If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
-
-netfilter mark match support
-CONFIG_IP6_NF_MATCH_MARK
- Netfilter mark matching allows you to match packets based on the
- `nfmark' value in the packet. This can be set by the MARK target
- (see below).
-
- If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
-
-Packet filtering
-CONFIG_IP6_NF_FILTER
- Packet filtering defines a table `filter', which has a series of
- rules for simple packet filtering at local input, forwarding and
- local output. See the man page for iptables(8).
-
- If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
-
-Packet mangling
-CONFIG_IP6_NF_MANGLE
- This option adds a `mangle' table to iptables: see the man page for
- iptables(8). This table is used for various packet alterations
- which can effect how the packet is routed.
-
- If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
-
-MARK target support
-CONFIG_IP6_NF_TARGET_MARK
- This option adds a `MARK' target, which allows you to create rules
- in the `mangle' table which alter the netfilter mark (nfmark) field
- associated with the packet packet prior to routing. This can change
- the routing method (see `IP: use netfilter MARK value as routing
- key') and can also be used by other subsystems to change their
- behavior.
-
- If you want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say `N'.
+ <file:Documentation/modules.txt>. If unsure, say `N'.
SYN flood protection
CONFIG_SYN_COOKIES
@@ -2434,8 +2738,7 @@
continue to connect, even when your machine is under attack. There
is no need for the legitimate users to change their TCP/IP software;
SYN cookies work transparently to them. For technical information
- about SYN cookies, check out
- ftp://koobera.math.uic.edu/syncookies.html .
+ about SYN cookies, check out <http://cr.yp.to/syncookies.html>.
If you are SYN flooded, the source address reported by the kernel is
likely to have been forged by the attacker; it is only reported as
@@ -2450,12 +2753,21 @@
you can enable them by saying Y to "/proc file system support" and
"Sysctl support" below and executing the command
- echo 1 >/proc/sys/net/ipv4/tcp_syncookies
+ echo 1 >/proc/sys/net/ipv4/tcp_syncookies
at boot time after the /proc file system has been mounted.
-
- If unsure, say Y.
+ If unsure, say N.
+
+HCI EMU (virtual device) driver
+CONFIG_BLUEZ_HCIEMU
+ Bluetooth Virtual HCI device driver.
+ This driver is required if you want to use HCI Emulation software.
+
+ Say Y here to compile support for Virtual HCI devices into the
+ kernel or say M to compile it as module (hci_usb.o).
+
+# Choice: alphatype
Alpha system type
CONFIG_ALPHA_GENERIC
This is the system type of your hardware. A "generic" kernel will
@@ -2464,7 +2776,7 @@
To find out what type of Alpha system you have, you may want to
check out the Linux/Alpha FAQ, accessible on the WWW from
- http://www.alphalinux.org . In summary:
+ <http://www.alphalinux.org>. In summary:
Alcor/Alpha-XLT AS 600
Alpha-XL XL-233, XL-266
@@ -2476,7 +2788,7 @@
EB64+ EB64+ 21064 evaluation board
EB66 EB66 21066 evaluation board
EB66+ EB66+ 21066 evaluation board
- Jensen DECpc 150, DEC 2000 model 300,
+ Jensen DECpc 150, DEC 2000 model 300,
DEC 2000 model 500
LX164 AlphaPC164-LX
Miata Personal Workstation 433a, 433au, 500a,
@@ -2496,21 +2808,160 @@
If you don't know what to do, choose "generic".
-EV5 CPU daughtercard
+# Most of the information on these variants is from
+# <http://www.alphalinux.org/docs/alpha-howto.html>
+Alcor/Alpha-XLT
+CONFIG_ALPHA_ALCOR
+ For systems using the Digital ALCOR chipset: 5 chips (4, 64-bit data
+ slices (Data Switch, DSW) - 208-pin PQFP and 1 control (Control, I/O
+ Address, CIA) - a 383 pin plastic PGA). It provides a DRAM
+ controller (256-bit memory bus) and a PCI interface. It also does
+ all the work required to support an external Bcache and to maintain
+ memory coherence when a PCI device DMAs into (or out of) memory.
+
+Alpha-XL
+CONFIG_ALPHA_XL
+ XL-233 and XL-266-based Alpha systems.
+
+AlphaBook1
+CONFIG_ALPHA_BOOK1
+ Dec AlphaBook1/Burns Alpha-based laptops.
+
+Avanti
+CONFIG_ALPHA_AVANTI
+ Avanti AS 200, AS 205, AS 250, AS 255, AS 300, and AS 400-based
+ Alphas. Info at
+ <http://www.unix-ag.org/Linux-Alpha/Architectures/Avanti.html>.
+
+Cabriolet
+CONFIG_ALPHA_CABRIOLET
+ Cabriolet AlphaPC64, AlphaPCI64 systems. Derived from EB64+ but now
+ baby-AT with Flash boot ROM, no on-board SCSI or Ethernet. 3 ISA
+ slots, 4 PCI slots (one pair are on a shared slot), uses plug-in
+ Bcache SIMMs. Requires power supply with 3.3V output.
+
+DP264
+CONFIG_ALPHA_DP264
+ Various 21264 systems with the tsunami core logic chipset.
+ API Networks: 264DP, UP2000(+), CS20;
+ Compaq: DS10(E,L), XP900, XP1000, DS20(E), ES40.
+
+EB164
+CONFIG_ALPHA_EB164
+ EB164 21164 evaluation board from DEC. Uses 21164 and ALCOR. Has
+ ISA and PCI expansion (3 ISA slots, 2 64-bit PCI slots (one is
+ shared with an ISA slot) and 2 32-bit PCI slots. Uses plus-in
+ Bcache SIMMs. I/O sub-system provides SuperI/O (2S, 1P, FD), KBD,
+ MOUSE (PS2 style), RTC/NVRAM. Boot ROM is Flash. PC-AT-sized
+ motherboard. Requires power supply with 3.3V output.
+
+EB64+
+CONFIG_ALPHA_EB64P
+ Uses 21064 or 21064A and APECs. Has ISA and PCI expansion (3 ISA,
+ 2 PCI, one pair are on a shared slot). Supports 36-bit DRAM SIMs.
+ ISA bus generated by Intel SaturnI/O PCI-ISA bridge. On-board SCSI
+ (NCR 810 on PCI) Ethernet (Digital 21040), KBD, MOUSE (PS2 style),
+ SuperI/O (2S, 1P, FD), RTC/NVRAM. Boot ROM is EPROM. PC-AT size.
+ Runs from standard PC power supply.
+
+EB66
+CONFIG_ALPHA_EB66
+ A Digital DS group board. Uses 21066 or 21066A. I/O sub-system is
+ identical to EB64+. Baby PC-AT size. Runs from standard PC power
+ supply. The EB66 schematic was published as a marketing poster
+ advertising the 21066 as "the first microprocessor in the world with
+ embedded PCI".
+
+EB66+
+CONFIG_ALPHA_EB66P
+ Later variant of the EB66 board.
+
+Eiger
+CONFIG_ALPHA_EIGER
+ Apparently an obscure OEM single-board computer based on the
+ Typhoon/Tsunami chipset family. Information on it is scanty.
+
+Jensen
+CONFIG_ALPHA_JENSEN
+ DEC PC 150 AXP (aka Jensen): This is a very old Digital system - one
+ of the first-generation Alpha systems. A number of these systems
+ seem to be available on the second- hand market. The Jensen is a
+ floor-standing tower system which originally used a 150MHz 21064 It
+ used programmable logic to interface a 486 EISA I/O bridge to the
+ CPU.
+
+LX164
+CONFIG_ALPHA_LX164
+ A technical overview of this board is available at
+ <http://www.unix-ag.org/Linux-Alpha/Architectures/LX164.html>.
+
+Miata
+CONFIG_ALPHA_MIATA
+ The Digital PersonalWorkStation (PWS 433a, 433au, 500a, 500au, 600a,
+ or 600au). There is an Installation HOWTO for this hardware at
+ <http://members.brabant.chello.nl/~s.vandereijk/miata.html>.
+
+Mikasa
+CONFIG_ALPHA_MIKASA
+ AlphaServer 1000-based Alpha systems.
+
+Nautilus
+CONFIG_ALPHA_NAUTILUS
+ Alpha systems based on the AMD 751 & ALI 1543C chipsets.
+
+Noname
+CONFIG_ALPHA_NONAME
+ The AXPpci33 (aka NoName), is based on the EB66 (includes the Multia
+ UDB). This design was produced by Digital's Technical OEM (TOEM)
+ group. It uses the 21066 processor running at 166MHz or 233MHz. It
+ is a baby-AT size, and runs from a standard PC power supply. It has
+ 5 ISA slots and 3 PCI slots (one pair are a shared slot). There are
+ 2 versions, with either PS/2 or large DIN connectors for the
+ keyboard.
+
+Noritake
+CONFIG_ALPHA_NORITAKE
+ AlphaServer 1000A, AlphaServer 600A, and AlphaServer 800-based
+ systems.
+
+Rawhide
+CONFIG_ALPHA_RAWHIDE
+ AlphaServer 1200, AlphaServer 4000 and AlphaServer 4100 machines.
+ See HOWTO at
+ <http://www.alphalinux.org/docs/rawhide/4100_install.shtml>.
+
+Ruffian
+CONFIG_ALPHA_RUFFIAN
+ Samsung APC164UX. There is a page on known problems and workarounds
+ at <http://www.alphalinux.org/faq/FAQ-11.html>.
+
+Sable
+CONFIG_ALPHA_SABLE
+ Digital AlphaServer 2000 and 2100-based systems.
+
+Takara
+CONFIG_ALPHA_TAKARA
+ Alpha 11164-based OEM single-board computer.
+
+Wildfire
+CONFIG_ALPHA_WILDFIRE
+ AlphaServer GS 40/80/160/320 SMP based on the EV67 core.
+
+EV5 CPU daughtercard (model 5/xxx)
CONFIG_ALPHA_PRIMO
Say Y if you have an AS 1000 5/xxx or an AS 1000A 5/xxx.
-EV5 CPU(s)
+EV5 CPU(s) (model 5/xxx)
CONFIG_ALPHA_GAMMA
Say Y if you have an AS 2000 5/xxx or an AS 2100 5/xxx.
-Using SRM as bootloader
+Use SRM as bootloader
CONFIG_ALPHA_SRM
There are two different types of booting firmware on Alphas: SRM,
which is command line driven, and ARC, which uses menus and arrow
keys. Details about the Linux/Alpha booting process are contained in
the Linux/Alpha FAQ, accessible on the WWW from
- http://www.alphalinux.org .
+ <http://www.alphalinux.org>.
The usual way to load Linux on an Alpha machine is to use MILO
(a bootloader that lets you pass command line parameters to the
@@ -2521,7 +2972,7 @@
here. If MILO doesn't work on your system (true for Jensen
motherboards), you can bypass it altogether and boot Linux directly
from an SRM console; say Y here in order to do that. Note that you
- won't be able to boot from an IDE disk using SRM.
+ won't be able to boot from an IDE disk using SRM.
If unsure, say N.
@@ -2530,20 +2981,20 @@
The 2.4 kernel changed the kernel start address from 0x310000
to 0x810000 to make room for the Wildfire's larger SRM console.
- If you're using aboot 0.7 or later, the bootloader will examine
- the ELF headers to determine where to transfer control. Unfortunately,
- most older bootloaders -- APB or MILO -- hardcoded the kernel
- start address rather than examining the ELF headers, and the result
- is a hard lockup.
+ If you're using aboot 0.7 or later, the bootloader will examine the
+ ELF headers to determine where to transfer control. Unfortunately,
+ most older bootloaders -- APB or MILO -- hardcoded the kernel start
+ address rather than examining the ELF headers, and the result is a
+ hard lockup.
- Say Y if you have a broken bootloader. Say N if you do not, or
- if you wish to run on Wildfire.
+ Say Y if you have a broken bootloader. Say N if you do not, or if
+ you wish to run on Wildfire.
Large VMALLOC support
CONFIG_ALPHA_LARGE_VMALLOC
- Process creation and other aspects of virtual memory management
- can be streamlined if we restrict the kernel to one PGD for all
- vmalloc allocations. This equates to about 8GB.
+ Process creation and other aspects of virtual memory management can
+ be streamlined if we restrict the kernel to one PGD for all vmalloc
+ allocations. This equates to about 8GB.
Under normal circumstances, this is so far and above what is needed
as to be laughable. However, there are certain applications (such
@@ -2559,11 +3010,11 @@
This includes intelligent serial boards such as Cyclades,
Digiboards, etc. These are usually used for systems that need many
serial ports because they serve many terminals or dial-in
- connections.
+ connections.
Note that the answer to this question won't directly affect the
- kernel: saying N will just cause this configure script to skip all
- the questions about non-standard serial boards.
+ kernel: saying N will just cause the configurator to skip all
+ the questions about non-standard serial boards.
Most people can say N here.
@@ -2572,10 +3023,10 @@
If you wish to use any non-standard features of the standard "dumb"
driver, say Y here. This includes HUB6 support, shared serial
interrupts, special multiport support, support for more than the
- four COM 1/2/3/4 boards, etc.
+ four COM 1/2/3/4 boards, etc.
Note that the answer to this question won't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all
the questions about serial driver options. If unsure, say N.
Support more than 4 serial ports
@@ -2583,22 +3034,30 @@
Say Y here if you have dumb serial boards other than the four
standard COM 1/2/3/4 ports. This may happen if you have an AST
FourPort, Accent Async, Boca (read the Boca mini-HOWTO, available
- from http://www.linuxdoc.org/docs.html#howto ), or other custom
+ from <http://www.linuxdoc.org/docs.html#howto>), or other custom
serial port hardware which acts similar to standard serial port
hardware. If you only use the standard COM 1/2/3/4 ports, you can
say N here to save some memory. You can also say Y if you have an
"intelligent" multiport card such as Cyclades, Digiboards, etc.
+Support for serial ports defined by ACPI tables
+CONFIG_SERIAL_ACPI
+ Legacy free machines may not have serial ports at the legacy COM1,
+ COM2 etc addresses. Serial ports on such machines are described by
+ the ACPI tables SPCR (Serial Port Console Redirection) table and
+ DBGP (Debug Port) table. Say Y here if you want to include support
+ for these serial ports.
+
Support for sharing serial interrupts
CONFIG_SERIAL_SHARE_IRQ
Some serial boards have hardware support which allows multiple dumb
serial ports on the same board to share a single IRQ. To enable
support for this in the serial driver, say Y here.
-Auto detect IRQ on standard ports (unsafe)
+Auto-detect IRQ on standard ports (unsafe)
CONFIG_SERIAL_DETECT_IRQ
Say Y here if you want the kernel to try to guess which IRQ
- to use for your serial port.
+ to use for your serial port.
This is considered unsafe; it is far better to configure the IRQ in
a boot script using the setserial command.
@@ -2612,16 +3071,12 @@
servicing. Say Y here to enable the serial driver to take advantage
of those special I/O ports.
-SGI PROM Console Support
-CONFIG_ARC_CONSOLE
- Say Y here if you want to use the PROMs for console I/O.
-
SGI Zilog85C30 serial support
CONFIG_SGI_SERIAL
If you want to use your SGI's built-in serial ports under Linux,
answer Y.
-SGI Newport Graphics support (EXPERIMENTAL)
+SGI Newport Graphics support
CONFIG_SGI_NEWPORT_GFX
If you have an SGI machine and you want to compile the graphics
drivers, say Y here. This will include the code for the
@@ -2651,14 +3106,14 @@
CONFIG_PCMCIA_SERIAL_CS
Say Y here to enable support for 16-bit PCMCIA serial devices,
including serial port cards, modems, and the modem functions of
- multi-function ethernet/modem cards. (PCMCIA- or PC-cards are
+ multi-function Ethernet/modem cards. (PCMCIA- or PC-cards are
credit-card size devices often used with laptops.)
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called serial_cs.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt. If unsure,
- say N.
+ The module will be called serial_cs.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
+ If unsure, say N.
ACP Modem (Mwave) support
CONFIG_MWAVE
@@ -2685,17 +3140,14 @@
The module will be called mwave.o. If you want to compile it as
a module, say M here and read Documentation/modules.txt.
-/dev/agpgart (AGP Support) (EXPERIMENTAL)
+/dev/agpgart (AGP Support)
CONFIG_AGP
AGP (Accelerated Graphics Port) is a bus system mainly used to
- connect graphics cards to the rest of the system.
+ connect graphics cards to the rest of the system.
If you have an AGP system and you say Y here, it will be possible to
use the AGP features of your 3D rendering video card. This code acts
- as a sort of "AGP driver" for the motherboard's chipset. The glx
- module will then be able to program the GART (graphics aperture
- relocation table) registers with appropriate values to transfer
- commands to the card.
+ as a sort of "AGP driver" for the motherboard's chipset.
If you need more texture memory than you can get with the AGP GART
(theoretically up to 256 MB, but in practice usually 64 or 128 MB
@@ -2706,47 +3158,42 @@
write-combining with MTRR support on the AGP bus. Without it, OpenGL
direct rendering will be a lot slower but still faster than PIO.
- For the moment, you should probably say N, unless you want to test
- the GLX component for XFree86 3.3.6, which can be downloaded from
- http://utah-glx.sourceforge.net/ , or need to use the 810 Xserver in
- XFree 3.3.6.
-
- This driver is available as a module. If you want to compile it as a
- module, say M here and read Documentation/modules.txt. The module
- will be called agpgart.o.
+ You should say Y here if you use XFree86 3.3.6 or 4.x and want to
+ use GLX or DRI. If unsure, say N.
+
+ This driver is available as a module. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>. The
+ module will be called agpgart.o.
-Intel 440LX/BX/GX/815/830M/840/850 support
+Intel 440LX/BX/GX/815/820/830/840/845/850/860 support
CONFIG_AGP_INTEL
This option gives you AGP support for the GLX component of the
- XFree86 4.x on Intel 440LX/BX/GX, 815, 830M, 840 and 850 chipsets.
+ XFree86 4.x on Intel 440LX/BX/GX, 815, 820, 830, 840, 845, 850 and 860 chipsets.
- For the moment, you should probably say N, unless you want to test
- the GLX component for XFree86 3.3.6, which can be downloaded from
- http://utah-glx.sourceforge.net/ .
+ You should say Y here if you use XFree86 3.3.6 or 4.x and want to
+ use GLX or DRI. If unsure, say N.
-Intel I810/I810 DC100/I810e support
+Intel I810/I815 DC100/I810e support
CONFIG_AGP_I810
- This option gives you AGP support for the Xserver on the Intel 810,
- 830M and 815 chipset boards for their on-board integrated graphics.
- This is required to do any useful video modes with these boards.
+ This option gives you AGP support for the Xserver on the Intel 810
+ 815 and 830m chipset boards for their on-board integrated graphics. This
+ is required to do any useful video modes with these boards.
VIA chipset support
CONFIG_AGP_VIA
This option gives you AGP support for the GLX component of the
XFree86 4.x on VIA MPV3/Apollo Pro chipsets.
- For the moment, you should probably say N, unless you want to test
- the GLX component for XFree86 3.3.6, which can be downloaded from
- http://utah-glx.sourceforge.net/ .
+ You should say Y here if you use XFree86 3.3.6 or 4.x and want to
+ use GLX or DRI. If unsure, say N.
AMD Irongate, 761, and 762 support
CONFIG_AGP_AMD
This option gives you AGP support for the GLX component of the
XFree86 4.x on AMD Irongate, 761, and 762 chipsets.
- For the moment, you should probably say N, unless you want to test
- the GLX component for XFree86 3.3.6, which can be downloaded from
- http://utah-glx.sourceforge.net/ .
+ You should say Y here if you use XFree86 3.3.6 or 4.x and want to
+ use GLX or DRI. If unsure, say N.
Generic SiS support
CONFIG_AGP_SIS
@@ -2756,33 +3203,47 @@
Note that 5591/5592 AGP chipsets are NOT supported.
- For the moment, you should probably say N, unless you want to test
- the GLX component for XFree86 3.3.6, which can be downloaded from
- http://utah-glx.sourceforge.net/ .
+ You should say Y here if you use XFree86 3.3.6 or 4.x and want to
+ use GLX or DRI. If unsure, say N.
-ALI M1541 support
+Serverworks LE/HE support
+CONFIG_AGP_SWORKS
+ Say Y here to support the Serverworks AGP card. See
+ <http://www.serverworks.com/> for product descriptions and images.
+
+ALI chipset support
CONFIG_AGP_ALI
This option gives you AGP support for the GLX component of the
- XFree86 4.x on the ALi M1541 chipset.
+ XFree86 4.x on the following ALi chipsets. The supported chipsets
+ include M1541, M1621, M1631, M1632, M1641,M1647,and M1651.
+ For the ALi-chipset question, ALi suggests you refer to
+ <http://www.ali.com.tw/eng/support/index.shtml>.
- This chipset can do AGP 1x and 2x, but note that there is an
+ The M1541 chipset can do AGP 1x and 2x, but note that there is an
acknowledged incompatibility with Matrox G200 cards. Due to
timing issues, this chipset cannot do AGP 2x with the G200.
This is a hardware limitation. AGP 1x seems to be fine, though.
- For the moment, you should probably say N, unless you want to test
- the GLX component for XFree86 3.3.6, which can be downloaded from
- http://utah-glx.sourceforge.net/ .
+ You should say Y here if you use XFree86 3.3.6 or 4.x and want to
+ use GLX or DRI. If unsure, say N.
-PCI support
+Support for ISA-bus hardware
+CONFIG_ISA
+ Find out whether you have ISA slots on your motherboard. ISA is the
+ name of a bus system, i.e. the way the CPU talks to the other stuff
+ inside your box. Other bus systems are PCI, EISA, MicroChannel
+ (MCA) or VESA. ISA is an older system, now being displaced by PCI;
+ newer boards don't support it. If you have ISA, say Y, otherwise N.
+
+Support for PCI bus hardware
CONFIG_PCI
Find out whether you have a PCI motherboard. PCI is the name of a
bus system, i.e. the way the CPU talks to the other stuff inside
- your box. Other bus systems are ISA, EISA, Microchannel (MCA) or
- VESA. If you have PCI, say Y, otherwise N.
+ your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
+ VESA. If you have PCI, say Y, otherwise N.
The PCI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto , contains valuable
+ <http://www.linuxdoc.org/docs.html#howto>, contains valuable
information about which PCI hardware does work under Linux and which
doesn't.
@@ -2790,11 +3251,11 @@
CONFIG_PCI_INTEGRATOR
Find out whether you have a PCI motherboard. PCI is the name of a
bus system, i.e. the way the CPU talks to the other stuff inside
- your box. Other bus systems are ISA, EISA, Microchannel (MCA) or
- VESA. If you have PCI, say Y, otherwise N.
+ your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
+ VESA. If you have PCI, say Y, otherwise N.
The PCI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto , contains valuable
+ <http://www.linuxdoc.org/docs.html#howto>, contains valuable
information about which PCI hardware does work under Linux and which
doesn't.
@@ -2802,14 +3263,15 @@
CONFIG_PCI_QSPAN
Find out whether you have a PCI motherboard. PCI is the name of a
bus system, i.e. the way the CPU talks to the other stuff inside
- your box. Other bus systems are ISA, EISA, Microchannel (MCA) or
- VESA. If you have PCI, say Y, otherwise N.
+ your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
+ VESA. If you have PCI, say Y, otherwise N.
The PCI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto , contains valuable
+ <http://www.linuxdoc.org/docs.html#howto>, contains valuable
information about which PCI hardware does work under Linux and which
doesn't.
+# Choice: pci_access
PCI access mode
CONFIG_PCI_GOBIOS
On PCI systems, the BIOS can be used to detect the PCI devices and
@@ -2838,22 +3300,56 @@
When in doubt, say Y.
+PCI Hotplug support
+CONFIG_HOTPLUG_PCI
+ Say Y here if you have a motherboard with a PCI Hotplug controller.
+ This allows you to add and remove PCI cards while the machine is
+ powered up and running. The file system pcihpfs must be mounted
+ in order to interact with any PCI Hotplug controllers.
+
+ This code is also available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ The module will be called pci_hotplug.o. If you want to compile it
+ as a module, say M here and read <file:Documentation/modules.txt>.
+
+ When in doubt, say N.
+
+PCI Compaq Hotplug controller
+CONFIG_HOTPLUG_PCI_COMPAQ
+ Say Y here if you have a motherboard with a Compaq PCI Hotplug
+ controller.
+
+ This code is also available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ The module will be called cpqphp.o. If you want to compile it
+ as a module, say M here and read <file:Documentation/modules.txt>.
+
+ When in doubt, say N.
+
+PCI Compaq Hotplug controller NVRAM support
+CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM
+ Say Y here if you have a Compaq server that has a PCI Hotplug
+ controller. This will allow the PCI Hotplug driver to store the PCI
+ system configuration options in NVRAM.
+
+ When in doubt, say N.
+
MCA support
CONFIG_MCA
MicroChannel Architecture is found in some IBM PS/2 machines and
- laptops. It is a bus system similar to PCI or ISA. See
- Documentation/mca.txt (and especially the web page given there)
- before attempting to build an MCA bus kernel.
+ laptops. It is a bus system similar to PCI or ISA. See
+ <file:Documentation/mca.txt> (and especially the web page given
+ there) before attempting to build an MCA bus kernel.
-EISA support
+Support for EISA-bus hardware
CONFIG_EISA
The Extended Industry Standard Architecture (EISA) bus was
developed as an open alternative to the IBM MicroChannel bus.
The EISA bus provided some of the features of the IBM MicroChannel
bus while maintaining backward compatibility with cards made for
- the older ISA bus. The EISA bus saw limited use between 1988 and 1995
- when it was made obsolete by the PCI bus.
+ the older ISA bus. The EISA bus saw limited use between 1988 and
+ 1995 when it was made obsolete by the PCI bus.
Say Y here if you are building a kernel for an EISA-based machine.
@@ -2866,7 +3362,7 @@
Say Y here to create a kernel to run on the SGI 320 or 540.
A kernel compiled for the Visual Workstation will not run on other
PC boards and vice versa.
- See Documentation/sgi-visws.txt for more.
+ See <file:Documentation/sgi-visws.txt> for more.
SGI Visual Workstation framebuffer support
CONFIG_FB_SGIVW
@@ -2891,8 +3387,8 @@
This support is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. You will get modules called i2o_core.o
- and i2o_config.o.
+ <file:Documentation/modules.txt>. You will get modules called
+ i2o_core.o and i2o_config.o.
If unsure, say N.
@@ -2904,7 +3400,7 @@
This support is also available as a module called i2o_pci.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
I2O Block OSM
CONFIG_I2O_BLOCK
@@ -2914,7 +3410,7 @@
This support is also available as a module called i2o_block.o ( =
code which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
I2O LAN OSM
CONFIG_I2O_LAN
@@ -2925,7 +3421,7 @@
This support is also available as a module called i2o_lan.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
I2O SCSI OSM
CONFIG_I2O_SCSI
@@ -2936,7 +3432,7 @@
This support is also available as a module called i2o_scsi.o ( =
code which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
I2O /proc support
CONFIG_I2O_PROC
@@ -2947,7 +3443,7 @@
This support is also available as a module called i2o_proc.o ( =
code which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
Plug and Play support
CONFIG_PNP
@@ -2959,24 +3455,41 @@
Say Y here if you would like Linux to configure your Plug and Play
devices. You should then also say Y to "ISA Plug and Play support",
- below. Alternatively, you can say N here and configure your PnP
+ below. Alternatively, you can say N here and configure your PnP
devices using the user space utilities contained in the isapnptools
package.
-
+
This support is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
If you want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ <file:Documentation/modules.txt>.
ISA Plug and Play support
CONFIG_ISAPNP
Say Y here if you would like support for ISA Plug and Play devices.
- Some information is in Documentation/isapnp.txt.
-
+ Some information is in <file:Documentation/isapnp.txt>.
+
This support is also available as a module called isapnp.o ( =
code which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
+
+ If unsure, say Y.
+
+PNPBIOS support
+CONFIG_PNPBIOS
+ Linux uses the PNPBIOS as defined in "Plug and Play BIOS
+ Specification Version 1.0A May 5, 1994" to autodetect built-in
+ mainboard resources (e.g. parallel port resources).
+
+ Other features (e.g. change resources, ESCD, event notification,
+ Docking station information, ISAPNP services) are not used.
+
+ Note: ACPI is expected to supersede PNPBIOS some day, currently it
+ co-exists nicely.
+
+ See latest pcmcia-cs (stand-alone package) for a nice "lspnp" tools,
+ or have a look at /proc/bus/pnp.
If unsure, say Y.
@@ -2992,50 +3505,55 @@
example, used on modern desktops as well as laptops, is USB.
Enable HOTPLUG and KMOD, and build a modular kernel. Get agent
- software (at http://linux-hotplug.sourceforge.net) and install it.
+ software (at <http://linux-hotplug.sourceforge.net>) and install it.
Then your kernel will automatically call out to a user mode "policy
agent" (/sbin/hotplug) to load modules and set up software needed
to use devices as you hotplug them.
-PCMCIA/Cardbus support
+PCMCIA/CardBus support
CONFIG_PCMCIA
Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
- computer. These are credit-card size devices such as network cards,
- modems or hard drives often used with laptops computers. There are
+ computer. These are credit-card size devices such as network cards,
+ modems or hard drives often used with laptops computers. There are
actually two varieties of these cards: the older 16 bit PCMCIA cards
- and the newer 32 bit CardBus cards. If you want to use CardBus
+ and the newer 32 bit CardBus cards. If you want to use CardBus
cards, you need to say Y here and also to "CardBus support" below.
- To use your PC-cards, you will need supporting software from David
- Hinds' pcmcia-cs package (see the file Documentation/Changes for
- location). Please also read the PCMCIA-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto
+ To use your PC-cards, you will need supporting software from David
+ Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
+ for location). Please also read the PCMCIA-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
When compiled this way, there will be modules called pcmcia_core.o
and ds.o. If you want to compile it as a module, say M here and
- read Documentation/modules.txt.
+ read <file:Documentation/modules.txt>.
-CardBus support
+CardBus card and (Yenta) bridge support
CONFIG_CARDBUS
- CardBus is a bus mastering architecture for PC-cards, which allows
- for 32 bit PC-cards (the original PCMCIA standard specifies only
+ CardBus is a bus mastering architecture for PC-cards, which allows
+ for 32 bit PC-cards (the original PCMCIA standard specifies only
a 16 bit wide bus). Many newer PC-cards are actually CardBus cards.
- To use your PC-cards, you will need supporting software from David
- Hinds' pcmcia-cs package (see the file Documentation/Changes for
- location).
+ This option enables support for CardBus PC Cards, as well as support
+ for CardBus host bridges. Virtually all modern PCMCIA bridges are
+ CardBus compatible. A "bridge" is the hardware inside your computer
+ that PCMCIA cards are plugged into.
+
+ To use your PC-cards, you will need supporting software from David
+ Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
+ for location).
If unsure, say Y.
-i82365/Yenta compatible bridge support
+i82365 compatible host bridge support
CONFIG_I82365
- Say Y here to include support for PCMCIA and CardBus host bridges
- that are register compatible with the Intel i82365 and/or the Yenta
- specification: this includes virtually all modern PCMCIA bridges.
- "Bridge" is the name used for the hardware inside your computer that
- PCMCIA cards are plugged into. If unsure, say Y.
+ Say Y here to include support for ISA-bus PCMCIA host bridges that
+ are register compatible with the Intel i82365. These are found on
+ older laptops and ISA-bus card readers for desktop systems. A
+ "bridge" is the hardware inside your computer that PCMCIA cards are
+ plugged into. If unsure, say N.
Databook TCIC host bridge support
CONFIG_TCIC
@@ -3052,60 +3570,67 @@
and some programs won't run unless you say Y here. In particular, if
you want to run the DOS emulator dosemu under Linux (read the
DOSEMU-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto ), you'll need to say Y
+ <http://www.linuxdoc.org/docs.html#howto>), you'll need to say Y
here.
-
+
You can find documentation about IPC with "info ipc" and also in
section 6.4 of the Linux Programmer's Guide, available from
- http://www.linuxdoc.org/docs.html#guide .
+ <http://www.linuxdoc.org/docs.html#guide>.
BSD Process Accounting
CONFIG_BSD_PROCESS_ACCT
If you say Y here, a user level program will be able to instruct the
kernel (via a special system call) to write process accounting
information to a file: whenever a process exits, information about
- that process will be appended to the file by the kernel. The
+ that process will be appended to the file by the kernel. The
information includes things such as creation time, owning user,
command name, memory usage, controlling terminal etc. (the complete
- list is in the struct acct in include/linux/acct.h). It is up to the
- user level program to do useful things with this information. This
- is generally a good idea, so say Y.
-
+ list is in the struct acct in <file:include/linux/acct.h>). It is
+ up to the user level program to do useful things with this
+ information. This is generally a good idea, so say Y.
+
Sysctl support
CONFIG_SYSCTL
The sysctl interface provides a means of dynamically changing
certain kernel parameters and variables on the fly without requiring
- a recompile of the kernel or reboot of the system. The primary
+ a recompile of the kernel or reboot of the system. The primary
interface consists of a system call, but if you say Y to "/proc
file system support", a tree of modifiable sysctl entries will be
generated beneath the /proc/sys directory. They are explained in the
- files in Documentation/sysctl/. Note that enabling this option will
- enlarge the kernel by at least 8 KB.
+ files in <file:Documentation/sysctl/>. Note that enabling this
+ option will enlarge the kernel by at least 8 KB.
As it is generally a good thing, you should say Y here unless
building a kernel for install/rescue disks or your system is very
limited in memory.
+# Choice: kcore
Kernel core (/proc/kcore) format
CONFIG_KCORE_ELF
- If you enabled support for /proc file system then the file
- /proc/kcore will contain the kernel core image. This can be used
+ If you enabled support for /proc file system then the file
+ /proc/kcore will contain the kernel core image. This can be used
in gdb:
$ cd /usr/src/linux ; gdb vmlinux /proc/kcore
- You have two choices here: ELF and A.OUT. Selecting ELF will make
+ You have two choices here: ELF and A.OUT. Selecting ELF will make
/proc/kcore appear in ELF core format as defined by the Executable
and Linking Format specification. Selecting A.OUT will choose the
old "a.out" format which may be necessary for some old versions
of binutils or on some architectures.
- This is especially useful if you have compiled the kernel with the
- "-g" option to preserve debugging information. It is mainly used
- for examining kernel data structures on the live kernel so if you
- don't understand what this means or are not a kernel hacker, just
+ This is especially useful if you have compiled the kernel with the
+ "-g" option to preserve debugging information. It is mainly used
+ for examining kernel data structures on the live kernel so if you
+ don't understand what this means or are not a kernel hacker, just
leave it at its default value ELF.
+# Choice: kcore
+Select a.out format for /proc/kcore
+CONFIG_KCORE_AOUT
+ Not necessary unless you're using a very out-of-date binutils
+ version. You probably want KCORE_ELF.
+
Kernel support for ELF binaries
CONFIG_BINFMT_ELF
ELF (Executable and Linkable Format) is a format for libraries and
@@ -3120,21 +3645,21 @@
want to say Y here.
Information about ELF is contained in the ELF HOWTO available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
If you find that after upgrading from Linux kernel 1.2 and saying Y
here, you still can't run any ELF binaries (they just crash), then
you'll have to install the newest ELF runtime libraries, including
- ld.so (check the file Documentation/Changes for location and latest
- version).
+ ld.so (check the file <file:Documentation/Changes> for location and
+ latest version).
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called binfmt_elf.o. Saying M or N here is dangerous because some
- crucial programs on your system might be in ELF format.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called binfmt_elf.o. Saying M or N here is dangerous because
+ some crucial programs on your system might be in ELF format.
-Kernel support for A.OUT binaries
+Kernel support for a.out binaries
CONFIG_BINFMT_AOUT
A.out (Assembler.OUTput) is a set of formats for libraries and
executables used in the earliest versions of UNIX. Linux used the
@@ -3162,12 +3687,17 @@
this to work, you need to have the emulator /usr/bin/em86 in place.
You can get the same functionality by saying N here and saying Y to
- "Kernel support for MISC binaries".
+ "Kernel support for MISC binaries".
You may answer M to compile the emulation support as a module and
later load the module when you want to use a Linux/Intel binary. The
module will be called binfmt_em86.o. If unsure, say Y.
+Kernel support for SOM binaries
+CONFIG_BINFMT_SOM
+ SOM is a binary executable format inherited from HP/UX. Say Y here
+ to be able to load and execute SOM binaries directly.
+
Kernel support for MISC binaries
CONFIG_BINFMT_MISC
If you say Y here, it will be possible to plug wrapper-driven binary
@@ -3175,15 +3705,15 @@
programs that need an interpreter to run like Java, Python or
Emacs-Lisp. It's also useful if you often run DOS executables under
the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto ). Once you have
+ <http://www.linuxdoc.org/docs.html#howto>). Once you have
registered such a binary class with the kernel, you can start one of
those programs simply by typing in its name at a shell prompt; Linux
will automatically feed it to the correct interpreter.
You can do other nice things, too. Read the file
- Documentation/binfmt_misc.txt to learn how to use this feature, and
- Documentation/java.txt for information about how to include Java
- support.
+ <file:Documentation/binfmt_misc.txt> to learn how to use this
+ feature, and <file:Documentation/java.txt> for information about how
+ to include Java support.
You must say Y to "/proc file system support" (CONFIG_PROC_FS) to
use this part of the kernel.
@@ -3192,16 +3722,33 @@
you have use for it; the module is called binfmt_misc.o. If you
don't know what to answer at this point, say Y.
-Solaris binary emulation (EXPERIMENTAL)
+Kernel support for JAVA binaries
+CONFIG_BINFMT_JAVA
+ If you say Y here, the kernel will load and execute Java J-code
+ binaries directly. Note: this option is obsolete and scheduled for
+ removal, use CONFIG_BINFMT_MISC instead.
+
+Solaris binary emulation
CONFIG_SOLARIS_EMUL
This is experimental code which will enable you to run (many)
- Solaris binaries on your SPARC Linux machine.
+ Solaris binaries on your SPARC Linux machine.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called solaris.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
+
+SUN SME environment monitoring
+CONFIG_ENVCTRL
+ Kernel support for temperature and fan monitoring on Sun SME
+ machines.
+ This code is also available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ The module will be called envctrl.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
+
+# Choice: x86
Processor family
CONFIG_M386
This is the processor type of your CPU. This information is used for
@@ -3215,17 +3762,17 @@
Here are the settings recommended for greatest speed:
- "386" for the AMD/Cyrix/Intel 386DX/DXL/SL/SLC/SX, Cyrix/TI
- 486DLC/DLC2, UMC 486SX-S and NexGen Nx586. Only "386" kernels will
- run on a 386 class machine.
+ 486DLC/DLC2, UMC 486SX-S and NexGen Nx586. Only "386" kernels
+ will run on a 386 class machine.
- "486" for the AMD/Cyrix/IBM/Intel 486DX/DX2/DX4 or
SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5D or U5S.
- - "586" for generic Pentium CPUs, possibly lacking the TSC
+ - "586" for generic Pentium CPUs, possibly lacking the TSC
(time stamp counter) register.
- "Pentium-Classic" for the Intel Pentium.
- "Pentium-MMX" for the Intel Pentium MMX.
- "Pentium-Pro" for the Intel Pentium Pro/Celeron/Pentium II.
- "Pentium-III" for the Intel Pentium III
- and Celerons based on the coppermine core.
+ and Celerons based on the Coppermine core.
- "Pentium-4" for the Intel Pentium 4.
- "K6" for the AMD K6, K6-II and K6-III (aka K6-3D).
- "Athlon" for the AMD K7 family (Athlon/Duron/Thunderbird).
@@ -3237,18 +3784,54 @@
If you don't know what to do, choose "386".
+486
+CONFIG_M486
+ Select this for a x486 processor, ether Intel or one of the
+ compatible processors from AMD, Cyrix, IBM, or Intel. Includes DX,
+ DX2, and DX4 variants; also SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5D or
+ U5S.
+
+586/K5/5x86/6x86/6x86MX
+CONFIG_M586
+ Select this for an x586 or x686 processor such as the AMD K5, the
+ Intel 5x86 or 6x86, or the Intel 6x86MX. This choice does not
+ assume the RDTSC instruction.
+
+Pentium Classic
+CONFIG_M586TSC
+ Select this for a Pentium Classic processor with the RDTSC (Read
+ Time Stamp Counter) instruction for benchmarking.
+
+32-bit PDC
+CONFIG_PDC_NARROW
+ Saying Y here will allow developers with a C180, C200, C240, C360,
+ J200, J210, and/or a J2240 to test 64-bit kernels by providing a
+ wrapper for the 32-bit PDC calls. Since the machines which require
+ this option do not support over 4G of RAM, this option is targeted
+ for developers of these machines wishing to test changes on both
+ 32-bit and 64-bit configurations.
+
+ If unsure, say N.
+
VGA text console
CONFIG_VGA_CONSOLE
Saying Y here will allow you to use Linux in text mode through a
display that complies with the generic VGA standard. Virtually
- everyone wants that.
+ everyone wants that.
The program SVGATextMode can be used to utilize SVGA video cards to
their full potential in text mode. Download it from
- ftp://metalab.unc.edu/pub/Linux/utils/console .
+ <ftp://metalab.unc.edu/pub/Linux/utils/console>.
Say Y.
+Distribute interrupts on all CPUs by default
+CONFIG_IRQ_ALL_CPUS
+ This option gives the kernel permission to distribute IRQs across
+ multiple CPUs. Saying N here will route all IRQs to the first
+ CPU. Generally SMP PowerMacs can answer Y. SMP IBM CHRP boxes or
+ Power3 boxes should say N for now.
+
Video mode selection support
CONFIG_VIDEO_SELECT
This enables support for text mode selection on kernel startup. If
@@ -3260,16 +3843,16 @@
"man bootparam" or see the documentation of your boot loader about
how to pass options to the kernel.)
- Read the file Documentation/svga.txt for more information about the
- Video mode selection support. If unsure, say N.
+ Read the file <file:Documentation/svga.txt> for more information
+ about the Video mode selection support. If unsure, say N.
-Support for frame buffer devices (EXPERIMENTAL)
+Support for frame buffer devices
CONFIG_FB
The frame buffer device provides an abstraction for the graphics
hardware. It represents the frame buffer of some video hardware and
allows application software to access the graphics hardware through
a well-defined interface, so the software doesn't need to know
- anything about the low-level (hardware register) stuff.
+ anything about the low-level (hardware register) stuff.
Frame buffer devices work identically across the different
architectures supported by Linux and make the implementation of
@@ -3277,14 +3860,14 @@
server exists which uses the frame buffer device exclusively.
On several non-X86 architectures, the frame buffer device is the
only way to use the graphics hardware.
-
+
The device is accessed through special device nodes, usually located
in the /dev directory, i.e. /dev/fb*.
You need an utility program called fbset to make full use of frame
- buffer devices. Please read Documentation/fb/framebuffer.txt and the
- Framebuffer-HOWTO at
- http://www.tahallah.demon.co.uk/programming/prog.html for more
+ buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
+ and the Framebuffer-HOWTO at
+ <http://www.tahallah.demon.co.uk/programming/prog.html> for more
information.
Say Y here and to the driver for your graphics board below if you
@@ -3302,6 +3885,27 @@
hardware found in Acorn RISC PCs and other ARM-based machines. If
unsure, say N.
+Permedia2 support
+CONFIG_FB_PM2
+ This is the frame buffer device driver for the Permedia2 AGP frame
+ buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
+ product page at
+ <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
+
+Enable FIFO disconnect feature
+CONFIG_FB_PM2_FIFO_DISCONNECT
+ Support the Permedia2 FIFOI disconnect feature (see CONFIG_FB_PM2).
+
+Generic Permedia2 PCI board support
+CONFIG_FB_PM2_PCI
+ Say Y to enable support for Permedia2 AGP frame buffer card from
+ 3Dlabs (aka `Graphic Blaster Exxtreme') on the PCI bus.
+
+Phase5 CVisionPPC/BVisionPPC support
+CONFIG_FB_PM2_CVPPC
+ Say Y to enable support for the Amiga Phase 5 CVisionPPC BVisionPPC
+ framebuffer cards. Phase 5 is no longer with us, alas.
+
Amiga native chipset support
CONFIG_FB_AMIGA
This is the frame buffer device driver for the builtin graphics
@@ -3310,7 +3914,7 @@
The driver is also available as a module ( = code which can be
inserted and removed from the running kernel whenever you want). The
module will be called amifb.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
Amiga OCS chipset support
CONFIG_FB_AMIGA_OCS
@@ -3348,7 +3952,7 @@
Say Y if you have a NetWinder or a graphics card containing this
device, otherwise say N.
-Amiga CyberVision3D support (EXPERIMENTAL)
+Amiga CyberVision3D support
CONFIG_FB_VIRGE
This enables support for the Cybervision 64/3D graphics card from
Phase5. Please note that its use is not all that intuitive (i.e. if
@@ -3357,13 +3961,13 @@
kernel. Please note that this driver DOES NOT support the older
Cybervision 64 card, as they use incompatible video chips.
-Amiga RetinaZ3 support (EXPERIMENTAL)
+Amiga RetinaZ3 support
CONFIG_FB_RETINAZ3
This enables support for the Retina Z3 graphics card. Say N unless
you have a Retina Z3 or plan to get one before you next recompile
the kernel.
-Cirrus Logic generic driver (EXPERIMENTAL)
+Cirrus Logic generic driver
CONFIG_FB_CLGEN
This enables support for Cirrus Logic GD542x/543x based boards on
Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
@@ -3371,21 +3975,17 @@
If you have a PCI-based system, this enables support for these
chips: GD-543x, GD-544x, GD-5480.
- Please read the file Documentation/fb/clgenfb.txt.
+ Please read the file <file:Documentation/fb/clgenfb.txt>.
Say N unless you have such a graphics board or plan to get one
before you next recompile the kernel.
-Permedia2 support (EXPERIMENTAL)
-CONFIG_FB_PM2
- Say Y here if this is your graphics board.
-
Apollo support
CONFIG_APOLLO
Say Y here if you want to run Linux on an MC680x0-based Apollo
Domain workstation such as the DN3500.
-Apollo 3c505 support
+Apollo 3c505 "EtherLink Plus" support
CONFIG_APOLLO_ELPLUS
Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
If you don't have one made for Apollos, you can use one from a PC,
@@ -3397,16 +3997,21 @@
This is the frame buffer device driver for the builtin graphics
chipset found in Ataris.
-Open Firmware frame buffer device support
+Amiga FrameMaster II/Rainbow II support
+CONFIG_FB_FM2
+ This is the frame buffer device driver for the Amiga FrameMaster
+ card from BSC (exhibited 1992 but not shipped as a CBM product).
+
+Open Firmware frame buffer device support
CONFIG_FB_OF
Say Y if you want support with Open Firmware for your graphics
board.
-S3 Trio frame buffer device support
+S3 Trio frame buffer device support
CONFIG_FB_S3TRIO
- If you have a S3 Trio say Y. Say N for S3 Virge.
+ If you have a S3 Trio say Y. Say N for S3 Virge.
-3Dfx Banshee/Voodoo3 display support (EXPERIMENTAL)
+3Dfx Banshee/Voodoo3 display support
CONFIG_FB_3DFX
This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
chips. Say Y if you have such a graphics board.
@@ -3414,9 +4019,9 @@
The driver is also available as a module ( = code which can be
inserted and removed from the running kernel whenever you want). The
module will be called tdfxfb.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
-nVidia Riva support (EXPERIMENTAL)
+nVidia Riva support
CONFIG_FB_RIVA
This driver supports graphics boards with the nVidia Riva/Geforce
chips.
@@ -3425,9 +4030,9 @@
The driver is also available as a module ( = code which can be
inserted and removed from the running kernel whenever you want). The
module will be called rivafb.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
-ATI Mach64 display support (EXPERIMENTAL)
+ATI Mach64 display support
CONFIG_FB_ATY
This driver supports graphics boards with the ATI Mach64 chips.
Say Y if you have such a graphics board.
@@ -3435,30 +4040,54 @@
The driver is also available as a module ( = code which can be
inserted and removed from the running kernel whenever you want). The
module will be called atyfb.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
-
-ATI Mach64 GX display support (EXPERIMENTAL)
-CONFIG_FB_ATY_GX
- This options adds support for the first generation ATI Mach64
- graphics chips, i.e. the Mach64 GX and CX. Note that this support is
- limited.
-
-ATI Mach64 CT/VT/GT/LT display support (EXPERIMENTAL)
-CONFIG_FB_ATY_CT
- This option adss support for ATI Mach64 graphics chips starting
- with the Mach64 CT family. This includes the Mach64 VT (limited
- support), GT (3D RAGE family), and LT.
+ module, say M here and read <file:Documentation/modules.txt>.
-ATI Rage128 display support (EXPERIMENTAL)
+ATI Rage128 display support
CONFIG_FB_ATY128
This driver supports graphics boards with the ATI Rage128 chips.
Say Y if you have such a graphics board and read
- Documentation/fb/aty128fb.txt.
+ <file:Documentation/fb/aty128fb.txt>.
The driver is also available as a module ( = code which can be
inserted and removed from the running kernel whenever you want). The
module will be called aty128fb.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
+
+# AC tree only
+Maxine (Personal DECstation) onboard framebuffer support
+CONFIG_FB_MAXINE
+ Say Y here to directly support the on-board framebuffer in the
+ Maxine (5000/20, /25, /33) version of the DECstation. There is a
+ page dedicated to Linux on DECstations at <http://decstation.unix-ag.org/>.
+
+# AC tree only
+PMAG-BA TURBOchannel framebuffer support
+CONFIG_FB_PMAG_BA
+ Say Y here to directly support the on-board PMAG-BA framebuffer in
+ the 5000/1xx versions of the DECstation. There is a page dedicated
+ to Linux on DECstations at <http://decstation.unix-ag.org/>.
+
+# AC tree only
+PMAGB-B TURBOchannel framebuffer support
+CONFIG_FB_PMAGB_B
+ Say Y here to directly support the on-board PMAGB-B framebuffer in
+ the 5000/1xx versions of the DECstation. There is a page dedicated
+ to Linux on DECstations at <http://decstation.unix-ag.org/>.
+
+FutureTV PCI card
+CONFIG_ARCH_FTVPCI
+ Say Y here if you intend to run this kernel on a FutureTV (nee Nexus
+ Electronics) StrongARM PCI card.
+
+P720T
+CONFIG_ARCH_P720T
+ Say Y here if you intend to run this kernel on the ARM Prospector
+ 720T.
+
+Link-Up Systems LCD support
+CONFIG_FB_L7200
+ This driver supports the L7200 Color LCD.
+ Say Y if you want graphics support.
PowerMac "control" frame buffer device support
CONFIG_FB_CONTROL
@@ -3490,13 +4119,13 @@
This is the frame buffer device driver for generic VESA 2.0
compliant graphic cards. The older VESA 1.2 cards are not supported.
You will get a boot time penguin logo at no additional cost. Please
- read Documentation/fb/vesafb.txt. If unsure, say Y.
+ read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
VGA 16-color planar support
CONFIG_FBCON_VGA_PLANES
This low level frame buffer console driver enable the kernel to use
the 16-color planar modes of the old VGA cards where the bits of
- each pixel are separated into 4 planes.
+ each pixel are separated into 4 planes.
Only answer Y here if you have a (very old) VGA card that isn't VESA
2 compatible.
@@ -3509,7 +4138,29 @@
This code is also available as a module. If you want to compile it
as a module ( = code which can be inserted in and removed from the
running kernel whenever you want), say M here and read
- Documentation/modules.txt. The module will be called vga16fb.o.
+ <file:Documentation/modules.txt>. The module will be called
+ vga16fb.o.
+
+Generic STI frame buffer device support
+CONFIG_FB_STI
+ STI refers to the HP "Standard Text Interface" which is a set of
+ BIOS routines contained in a ROM chip in HP PA-RISC based machines.
+ Enabling this option will implement the linux framebuffer device and
+ an fbcon color text console using calls to the STI BIOS routines.
+ The HP framebuffer device is usually planar, uses a strange memory
+ layout, and changing the plane mask to create colored pixels
+ requires a call to the STI routines, so do not expect /dev/fb to
+ actually be useful. However, it is the best we have as far as
+ graphics on the HP chipsets due to lack of hardware level
+ documentation for the various on-board HP chipsets used in these
+ systems. It is sufficient for basic text console functions,
+ including fonts.
+
+ You should probably enable this option, unless you are having
+ trouble getting video when booting the kernel (make sure it isn't
+ just that you are running the console on the serial port, though).
+ Really old HP boxes may not have STI, and must use the PDC BIOS
+ console or the IODC BIOS.
Select other compiled-in fonts
CONFIG_FBCON_FONTS
@@ -3517,7 +4168,7 @@
your frame buffer console usually use.
Note that the answer to this question won't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all
the questions about foreign fonts.
If unsure, say N (the default choices are safe).
@@ -3549,14 +4200,29 @@
VGA 8x8 font
CONFIG_FONT_8x8
This is the "high resolution" font for the VGA frame buffer (the one
- provided by the text console 80x50 (and higher) modes).
+ provided by the text console 80x50 (and higher) modes).
Note that this is a poor quality font. The VGA 8x16 font is quite a
- lot more readable.
+ lot more readable.
Given the resolution provided by the frame buffer device, answer N
here is safe.
+Mac console 6x11 font (not supported by all drivers)
+CONFIG_FONT_6x11
+ Small console font with Macintosh-style high-half glyphs. Some Mac
+ framebuffer drivers don't support this one at all.
+
+Pearl (old m68k) console 8x8 font
+CONFIG_FONT_PEARL_8x8
+ Small console font with PC-style control-character and high-half
+ glyphs.
+
+Acorn console 8x8 font
+CONFIG_FONT_ACORN_8x8
+ Small console font with PC-style control characters and high-half
+ glyphs.
+
Backward compatibility mode for Xpmac
CONFIG_FB_COMPAT_XPMAC
If you use the Xpmac X server (common with mklinux), you'll need to
@@ -3564,35 +4230,61 @@
includes a server that supports the frame buffer device directly
(XF68_FBDev).
-HGA monochrome support (EXPERIMENTAL)
+Hercules (HGA) mono graphics support
CONFIG_FB_HGA
Say Y here if you have a Hercules mono graphics card.
This driver is also available as a module ( = code which can be
inserted and removed from the running kernel whenever you want).
The module will be called hgafb.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
+ a module, say M here and read <file:Documentation/modules.txt>.
As this card technology is 15 years old, most people will answer N
here.
+Epson 1355 framebuffer support
+CONFIG_FB_E1355
+ Build in support for the SED1355 Epson Research Embedded RAMDAC
+ LCD/CRT Controller (since redesignated as the S1D13505) as a
+ framebuffer. Product specs at
+ <http://www.erd.epson.com/vdc/html/products.htm>.
+
+Dreamcast Frame Buffer support
+CONFIG_FB_DC
+ Say Y here to enable support for the framebuffer on the Sega
+ Dreamcast. This driver is also available as a module, dcfb.o.
+
+Register Base Address
+CONFIG_E1355_REG_BASE
+ Epson SED1355/S1D13505 LCD/CRT controller register base address.
+ See the manuals at
+ <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for
+ discussion.
+
+Framebuffer Base Address
+CONFIG_E1355_FB_BASE
+ Epson SED1355/S1D13505 LCD/CRT controller memory base address. See
+ the manuals at
+ <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for
+ discussion.
+
NEC PowerVR 2 display support
CONFIG_FB_PVR2
- Say Y here if you have a PowerVR 2 card in your box. If you plan to
- run linux on your Dreamcast, you will have to say Y here. This driver
- may or may not work on other PowerVR 2 cards, but is totally untested.
- Use at your own risk. If unsure, say N.
+ Say Y here if you have a PowerVR 2 card in your box. If you plan to
+ run linux on your Dreamcast, you will have to say Y here.
+ This driver may or may not work on other PowerVR 2 cards, but is
+ totally untested. Use at your own risk. If unsure, say N.
This driver is also available as a module ( = code which can be
inserted and removed from the running kernel whenever you want).
- The module will be called pvr2fb.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
+ The module will be called pvr2fb.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
You can pass several parameters to the driver at boot time or at
- module load time. The parameters look like "video=pvr2:XXX", where
+ module load time. The parameters look like "video=pvr2:XXX", where
the meaning of XXX can be found at the end of the main source file
- (drivers/video/pvr2fb.c). Please see the file
- Documentation/fb/pvr2fb.txt.
+ (<file:drivers/video/pvr2fb.c>). Please see the file
+ <file:Documentation/fb/pvr2fb.txt>.
Debug pvr2fb
CONFIG_FB_PVR2_DEBUG
@@ -3600,26 +4292,26 @@
messages. Most people will want to say N here. If unsure, you will
also want to say N.
-Matrox unified accelerated driver (EXPERIMENTAL)
+Matrox unified accelerated driver
CONFIG_FB_MATROX
Say Y here if you have a Matrox Millennium, Matrox Millennium II,
Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
- Matrox G400 or G450 card in your box. At this time, support for the G100
- is untested and support for G450 is highly experimental.
+ Matrox G400 or G450 card in your box. At this time, support for the
+ G100 is untested and support for G450 is highly experimental.
This driver is also available as a module ( = code which can be
inserted and removed from the running kernel whenever you want).
The module will be called matroxfb.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
+ a module, say M here and read <file:Documentation/modules.txt>.
You can pass several parameters to the driver at boot time or at
module load time. The parameters look like "video=matrox:XXX", where
the meaning of XXX can be found at the end of the main source file
- (drivers/video/matroxfb.c). Please see the file
- Documentation/fb/matroxfb.txt.
+ (<file:drivers/video/matroxfb.c>). Please see
+ <file:Documentation/fb/matroxfb.txt>.
-Matrox Millennium support
+Matrox Millennium I/II support
CONFIG_FB_MATROX_MILLENIUM
Say Y here if you have a Matrox Millennium or Matrox Millennium II
video card. If you select "Advanced lowlevel driver options" below,
@@ -3638,9 +4330,9 @@
Matrox G100/G200/G400/G450 support
CONFIG_FB_MATROX_G100
Say Y here if you have a Matrox G100, G200, G400 or G450 based
- video card. If you select "Advanced lowlevel driver options", you
- should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
- pixel and 32 bpp packed pixel. You can also use font widths
+ video card. If you select "Advanced lowlevel driver options", you
+ should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
+ pixel and 32 bpp packed pixel. You can also use font widths
different from 8.
If you need support for G400 secondary head, you must first say Y to
@@ -3654,14 +4346,14 @@
DDC (I2C) bus present on all Matroxes, an I2C bus which
interconnects Matrox optional devices, like MGA-TVO on G200 and
G400, and the secondary head DDC bus, present on G400 only.
-
- You can say Y or M here if you want to experiment with monitor
+
+ You can say Y or M here if you want to experiment with monitor
detection code. You must say Y or M here if you want to use either
second head of G400 or MGA-TVO on G200 or G400.
-
+
If you compile it as module, it will create a module named
i2c-matroxfb.o.
-
+
Matrox G400 second head support
CONFIG_FB_MATROX_MAVEN
WARNING !!! This support does not work with G450 !!!
@@ -3672,26 +4364,24 @@
secondary head output is blanked while you are in X. With XFree
3.9.17 preview you can use both heads if you use SVGA over fbdev or
the fbdev driver on first head and the fbdev driver on second head.
-
+
If you compile it as module, two modules are created,
matroxfb_crtc2.o and matroxfb_maven.o. Matroxfb_maven is needed for
both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
also load i2c-matroxfb to get it to run.
-
+
The driver starts in monitor mode and you must use the matroxset
- tool (available at ftp://platan.vc.cvut.cz/pub/linux/matrox-latest)
- to switch it to PAL or NTSC or to swap primary and secondary head
- outputs. Secondary head driver also always start in 640x480
- resolution, you must use fbset to change it.
-
+ tool (available at
+ <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest>) to switch it to
+ PAL or NTSC or to swap primary and secondary head outputs.
+ Secondary head driver also always start in 640x480 resolution, you
+ must use fbset to change it.
+
Also do not forget that second head supports only 16 and 32 bpp
packed pixels, so it is a good idea to compile them into the kernel
- too. You can use only some font widths, as the driver uses generic
+ too. You can use only some font widths, as the driver uses generic
painting procedures (the secondary head does not use acceleration
engine).
-
- There is no need for enabling 'Matrox multihead support' if you have
- only one Matrox card in the box.
Matrox G450 second head support
CONFIG_FB_MATROX_G450
@@ -3703,10 +4393,10 @@
want two independent display devices.
The driver starts in monitor mode and currently does not support
- output in TV modes. You must use the matroxset tool (available
- at ftp://platan.vc.cvut.cz/pub/linux/matrox-latest) to swap primary
- and secondary head outputs. Secondary head driver always start in
- 640x480 resolution and you must use fbset to change it.
+ output in TV modes. You must use the matroxset tool (available
+ at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest>) to swap
+ primary and secondary head outputs. Secondary head driver always
+ start in 640x480 resolution and you must use fbset to change it.
Also do not forget that second head supports only 16 and 32 bpp
packed pixels, so it is a good idea to compile them into the kernel
@@ -3714,9 +4404,6 @@
painting procedures (the secondary head does not use acceleration
engine).
- There is no need for enabling 'Matrox multihead support' if you have
- only one Matrox card in the box.
-
Matrox unified driver multihead support
CONFIG_FB_MATROX_MULTIHEAD
Say Y here if you have more than one (supported) Matrox device in
@@ -3732,6 +4419,24 @@
for the different Matrox devices. This method is slightly faster but
uses 40 KB of kernel memory per Matrox card.
+ There is no need for enabling 'Matrox multihead support' if you have
+ only one Matrox card in the box.
+
+3Dfx Voodoo Graphics / Voodoo2 frame buffer support
+CONFIG_FB_VOODOO1
+ Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
+ Voodoo2 (cvg) based graphics card.
+
+ This driver is also available as a module ( = code which can be
+ inserted and removed from the running kernel whenever you want).
+ The module will be called sstfb.o. If you want to compile it as
+ a module, say M here and read Documentation/modules.txt.
+
+ WARNING: Do not use any application that uses the 3D engine
+ (namely glide) while using this driver.
+ Please read the file Documentation/fb/README-sstfb.txt for supported
+ options and other important info support.
+
MDA text console (dual-headed)
CONFIG_MDA_CONSOLE
Say Y here if you have an old MDA or monochrome Hercules graphics
@@ -3739,15 +4444,15 @@
will then be able to use two monitors with your Linux system. Do not
say Y here if your MDA card is the primary card in your system; the
normal VGA driver will handle it.
-
+
This driver is also available as a module ( = code which can be
inserted and removed from the running kernel whenever you want).
The module will be called mdacon.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
-
+ a module, say M here and read <file:Documentation/modules.txt>.
+
If unsure, say N.
-SBUS and UPA frame buffers
+SBUS and UPA framebuffers
CONFIG_FB_SBUS
Say Y if you want support for SBUS or UPA based frame buffer device.
@@ -3769,11 +4474,59 @@
CONFIG_FB_CGTHREE
This is the frame buffer device driver for the CGthree frame buffer.
+CGfourteen (SX) support
+CONFIG_FB_CGFOURTEEN
+ This is the frame buffer device driver for the CGfourteen frame
+ buffer on Desktop SPARCsystems with the SX graphics option.
+
+P9100 (Sparcbook 3 only) support
+CONFIG_FB_P9100
+ This is the frame buffer device driver for the P9100 card
+ supported on Sparcbook 3 machines.
+
+Leo (ZX) support
+CONFIG_FB_LEO
+ This is the frame buffer device driver for the SBUS-based Sun ZX
+ (leo) frame buffer cards.
+
+IGA 168x display support
+CONFIG_FB_IGA
+ This is the framebuffer device for the INTERGRAPHICS 1680 and
+ successor frame buffer cards.
+
TCX (SS4/SS5 only) support
CONFIG_FB_TCX
This is the frame buffer device driver for the TCX 24/8bit frame
buffer.
+HD64461 Frame Buffer support
+CONFIG_FB_HIT
+ This is the frame buffer device driver for the Hitachi HD64461 LCD
+ frame buffer card.
+
+SIS 630/540 display support
+CONFIG_FB_SIS
+ This is the frame buffer device driver for the SiS 630 and 640 Super
+ Socket 7 UMA cards. Specs available at <http://www.sis.com.tw/>.
+
+# AC tree only
+SIS 630/540/730 support
+CONFIG_FB_SIS_300
+ This is the frame buffer device driver for the SiS 630 and related
+ Super Socket 7 UMA cards. Specs available at
+ <http://www.sis.com.tw/>.
+
+# AC tree only
+SIS 315H/315 support
+CONFIG_FB_SIS_315
+ This is the frame buffer device driver for the SiS 315 graphics
+ card. Specs available at <http://www.sis.com.tw/>.
+
+IMS Twin Turbo display support
+CONFIG_FB_IMSTT
+ The IMS Twin Turbo is a PCI-based frame buffer card bundled with
+ many Macintosh and compatible computers.
+
Virtual Frame Buffer support (ONLY FOR TESTING!)
CONFIG_FB_VIRTUAL
This is a `virtual' frame buffer device. It operates on a chunk of
@@ -3788,13 +4541,48 @@
This driver is also available as a module ( = code which can be
inserted and removed from the running kernel whenever you want). The
module will be called vfb.o. If you want to compile it as a module,
- say M here and read Documentation/modules.txt.
-
+ say M here and read <file:Documentation/modules.txt>.
+
If unsure, say N.
+Mach64 CT/VT/GT/LT (incl. 3D RAGE) support
+CONFIG_FB_ATY_CT
+ Say Y here to support use of ATI's 64-bit Rage boards (or other
+ boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
+ framebuffer device. The ATI product support page for these boards
+ is at <http://support.ati.com/products/pc/mach64/>.
+
+Sony Vaio Picturebook laptop LCD panel support
+CONFIG_FB_ATY_CT_VAIO_LCD
+ Say Y here if you want to use the full width of the Sony Vaio
+ Picturebook laptops LCD panels (you will get a 128x30 console).
+
+ Note that you need to activate this mode using the 'vga=0x301'
+ option from your boot loader (lilo or loadlin). See the
+ documentation of your boot loader about how to pass options to the
+ kernel.
+
+Mach64 GX support
+CONFIG_FB_ATY_GX
+ Say Y here to support use of the ATI Mach64 Graphics Expression
+ board (or other boards based on the Mach64 GX chipset) as a
+ framebuffer device. The ATI product support page for these boards
+ is at
+ <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
+
+# AC tree only
+ATI Radeon display support
+CONFIG_FB_RADEON
+ Choose this option if you want to use an ATI Radeon graphics card as
+ a framebuffer device. There are both PCI and AGP versions. You
+ don't need to choose this to run the Radeon in plain VGA mode.
+ There is a product page at
+ <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
+
+SA-1100 LCD support
CONFIG_FB_SA1100
This is a framebuffer device for the SA-1100 LCD Controller.
- See http://www.linux-fbdev.org/ for information on framebuffer
+ See <http://www.linux-fbdev.org/> for information on framebuffer
devices.
If you plan to use the LCD display with your SA-1100 system, say
@@ -3819,8 +4607,8 @@
Low level frame buffer console drivers can be modules ( = code which
can be inserted and removed from the running kernel whenever you
want). The modules will be called fbcon-*.o. If you want to compile
- (some of) them as modules, read Documentation/modules.txt.
-
+ (some of) them as modules, read <file:Documentation/modules.txt>.
+
If unsure, say N.
Monochrome support
@@ -3890,10 +4678,10 @@
This is the low level frame buffer console driver for 1/2/4/8/16/32
bits per pixel packed pixels on Mac. It supports variable font
widths for low resolution screens.
-
-HGA monochrome support (EXPERIMENTAL)
+
+HGA monochrome support
CONFIG_FBCON_HGA
- This is the low level frame buffer console driver for Hercules mono
+ This is the low level frame buffer console driver for Hercules mono
graphics cards.
VGA characters/attributes support
@@ -3909,21 +4697,21 @@
drive, PLIP link (Parallel Line Internet Protocol is mainly used to
create a mini network by connecting the parallel ports of two local
machines) etc., then you need to say Y here; please read
- Documentation/parport.txt and drivers/parport/BUGS-parport.
+ <file:Documentation/parport.txt> and drivers/parport/BUGS-parport.
For extensive information about drivers for many devices attaching
- to the parallel port see http://www.torque.net/linux-pp.html on the
- WWW.
+ to the parallel port see <http://www.torque.net/linux-pp.html> on
+ the WWW.
It is possible to share a single parallel port among several devices
and it is safe to compile all the corresponding drivers into the
- kernel. If you want to compile parallel port support as a module ( =
- code which can be inserted in and removed from the running kernel
- whenever you want), say M here and read Documentation/modules.txt.
- The module will be called parport.o. If you have more than one
- parallel port and want to specify which port and IRQ to be used by
- this driver at module load time, take a look at
- Documentation/parport.txt.
+ kernel. If you want to compile parallel port support as a module
+ ( = code which can be inserted in and removed from the running
+ kernel whenever you want), say M here and read
+ <file:Documentation/modules.txt>. The module will be called
+ parport.o. If you have more than one parallel port and want to
+ specify which port and IRQ to be used by this driver at module load
+ time, take a look at <file:Documentation/parport.txt>.
If unsure, say Y.
@@ -3931,20 +4719,21 @@
CONFIG_PARPORT_PC
You should say Y here if you have a PC-style parallel port. All IBM
PC compatible computers and some Alphas have PC-style parallel
- ports.
+ ports.
- This code is also available as a module. If you want to compile it
+ This code is also available as a module. If you want to compile it
as a module ( = code which can be inserted in and removed from the
running kernel whenever you want), say M here and read
- Documentation/modules.txt. The module will be called parport_pc.o.
-
+ <file:Documentation/modules.txt>. The module will be called
+ parport_pc.o.
+
If unsure, say Y.
Parallel+serial PCI card support
CONFIG_PARPORT_SERIAL
- This adds support for multi-IO PCI cards that have parallel and serial
- ports. You should say Y or M here. If you say M, the module will be
- called parport_serial.o.
+ This adds support for multi-IO PCI cards that have parallel and
+ serial ports. You should say Y or M here. If you say M, the module
+ will be called parport_serial.o.
Use FIFO/DMA if available
CONFIG_PARPORT_PC_FIFO
@@ -3952,12 +4741,12 @@
printing. Say Y here if you want to take advantage of that.
As well as actually having a FIFO, or DMA capability, the kernel
- will need to know which IRQ the parallel port has. By default,
+ will need to know which IRQ the parallel port has. By default,
parallel port interrupts will not be used, and so neither will the
- FIFO. See Documentation/parport.txt to find out how to specify
- which IRQ/DMA to use.
+ FIFO. See <file:Documentation/parport.txt> to find out how to
+ specify which IRQ/DMA to use.
-SuperIO chipset support (EXPERIMENTAL)
+SuperIO chipset support
CONFIG_PARPORT_PC_SUPERIO
Saying Y here enables some probes for Super-IO chipsets in order to
find out things like base addresses, IRQ lines and DMA channels. It
@@ -3974,12 +4763,6 @@
other non-standard types of parallel ports. This causes a
performance loss, so most people say N.
-Sun Ultra/AX-style hardware
-CONFIG_PARPORT_AX
- Say Y here if you need support for the parallel port hardware on Sun
- Ultra/AX machines. This code is also available as a module (say M),
- called parport_ax.o. If in doubt, saying N is the safe plan.
-
Amiga built-in parallel port support
CONFIG_PARPORT_AMIGA
Say Y here if you need support for the parallel port hardware on
@@ -3992,51 +4775,51 @@
Atari machines. This code is also available as a module (say M),
called parport_atari.o. If in doubt, saying N is the safe plan.
-Multiface 3 parallel port card support
+Multiface III parallel port support
CONFIG_PARPORT_MFC3
Say Y here if you need parallel port support for the MFC3 card.
This code is also available as a module (say M), called
parport_mfc3.o. If in doubt, saying N is the safe plan.
-Support IEEE1284 status readback
+Support IEEE 1284 status readback
CONFIG_PRINTER_READBACK
If you have a device on your parallel port that support this
protocol, this option will allow the device to report its status. It
is safe to say Y.
-IEEE1284 transfer modes
+IEEE 1284 transfer modes
CONFIG_PARPORT_1284
If you have a printer that supports status readback or device ID, or
want to use a device that uses enhanced parallel port transfer modes
such as EPP and ECP, say Y here to enable advanced IEEE 1284
transfer modes. Also say Y if you want device ID information to
appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
-
+
Enable loadable module support
CONFIG_MODULES
Kernel modules are small pieces of compiled code which can be
inserted in or removed from the running kernel, using the programs
insmod and rmmod. This is described in the file
- Documentation/modules.txt, including the fact that you have to say
- "make modules" in order to compile the modules that you chose during
- kernel configuration. Modules can be device drivers, file systems,
- binary executable formats, and so on. If you think that you may want
- to make use of modules with this kernel in the future, then say Y
- here. If unsure, say Y.
+ <file:Documentation/modules.txt>, including the fact that you have
+ to say "make modules" in order to compile the modules that you chose
+ during kernel configuration. Modules can be device drivers, file
+ systems, binary executable formats, and so on. If you think that you
+ may want to make use of modules with this kernel in the future, then
+ say Y here. If unsure, say Y.
Set version information on all symbols for modules
CONFIG_MODVERSIONS
Usually, modules have to be recompiled whenever you switch to a new
- kernel. Saying Y here makes it possible, and safe, to use the
+ kernel. Saying Y here makes it possible, and safe, to use the
same modules even after compiling a new kernel; this requires the
program modprobe. All the software needed for module support is in
- the modutils package (check the file Documentation/Changes for
- location and latest version). NOTE: if you say Y here but don't
+ the modutils package (check the file <file:Documentation/Changes>
+ for location and latest version). NOTE: if you say Y here but don't
have the program genksyms (which is also contained in the above
mentioned modutils package), then the building of your kernel will
- fail. If you are going to use modules that are generated from
- non-kernel sources, you would benefit from this option. Otherwise
- it's not that important. So, N ought to be a safe bet.
+ fail. If you are going to use modules that are generated from
+ non-kernel sources, you would benefit from this option. Otherwise
+ it's not that important. So, N ought to be a safe bet.
Kernel module loader support
CONFIG_KMOD
@@ -4048,11 +4831,11 @@
kernel needs a module, it runs modprobe with the appropriate
arguments, thereby loading the module if it is available. (This is a
replacement for kerneld.) Say Y here and read about configuring it
- in Documentation/kmod.txt.
+ in <file:Documentation/kmod.txt>.
-ARP daemon support (EXPERIMENTAL)
+ARP daemon support
CONFIG_ARPD
- Normally, the kernel maintains an internal cache which maps IP
+ Normally, the kernel maintains an internal cache which maps IP
addresses to hardware addresses on the local network, so that
Ethernet/Token Ring/ etc. frames are sent to the proper address on
the physical networking layer. For small networks having a few
@@ -4060,7 +4843,7 @@
resolution (ARP) cache inside the kernel works well. However,
maintaining an internal ARP cache does not work well for very large
switched networks, and will use a lot of kernel memory if TCP/IP
- connections are made to many machines on the network.
+ connections are made to many machines on the network.
If you say Y here, the kernel's internal ARP cache will never grow
to more than 256 entries (the oldest entries are expired in a LIFO
@@ -4084,35 +4867,35 @@
For an excellent introduction to Linux networking, please read the
NET-3-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
This option is also necessary if you want to use the full power of
term (term is a program which gives you almost full Internet
connectivity if you have a regular dial up shell account on some
Internet connected Unix computer; for more information, read
- http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html ).
-
+ <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>).
+
If you say Y here and also to "/proc file system support" and
"Sysctl support" below, you can change various aspects of the
behavior of the TCP/IP code by writing to the (virtual) files in
/proc/sys/net/ipv4/*; the options are explained in the file
- Documentation/networking/ip-sysctl.txt.
+ <file:Documentation/networking/ip-sysctl.txt>.
Short answer: say Y.
-IP: multicasting
+IP multicasting
CONFIG_IP_MULTICAST
This is code for addressing several networked computers at once,
enlarging your kernel by about 2 KB. You need multicasting if you
intend to participate in the MBONE, a high bandwidth network on top
of the Internet which carries audio and video broadcasts. More
information about the MBONE is on the WWW at
- http://www-itg.lbl.gov/mbone/ . Information about the multicast
+ <http://www-itg.lbl.gov/mbone/>. Information about the multicast
capabilities of the various network cards is contained in
- Documentation/networking/multicast.txt. For most people, it's safe
- to say N.
+ <file:Documentation/networking/multicast.txt>. For most people, it's
+ safe to say N.
-IP: advanced router
+Advanced router
CONFIG_IP_ADVANCED_ROUTER
If you intend to run your Linux box mostly as a router, i.e. as a
computer that forwards and redistributes network packets, say Y; you
@@ -4120,7 +4903,7 @@
control about the routing process.
The answer to this question won't directly affect the kernel:
- answering N will just cause this configure script to skip all the
+ answering N will just cause the configurator to skip all the
questions about advanced routing.
Note that your box can only act as a router if you enable IP
@@ -4130,7 +4913,7 @@
echo "1" > /proc/sys/net/ipv4/ip_forward
- at boot time after the /proc file system has been mounted.
+ at boot time after the /proc file system has been mounted.
If you turn on IP forwarding, you will also get the rp_filter, which
automatically rejects incoming packets if the routing table entry
@@ -4148,26 +4931,27 @@
If unsure, say N here.
-IP: policy routing
+Policy routing
CONFIG_IP_MULTIPLE_TABLES
Normally, a router decides what to do with a received packet based
solely on the packet's final destination address. If you say Y here,
the Linux router will also be able to take the packet's source
- address into account. Furthermore, if you also say Y to "IP: use TOS
+ address into account. Furthermore, if you also say Y to "Use TOS
value as routing key" below, the TOS (Type-Of-Service) field of the
packet can be used for routing decisions as well. In addition, if
- you say Y here and to "IP: fast network address translation" below,
+ you say Y here and to "Fast network address translation" below,
the router will also be able to modify source and destination
addresses of forwarded packets.
If you are interested in this, please see the preliminary
- documentation at http://www.compendium.com.ar/policy-routing.txt and
- ftp://post.tepkom.ru/pub/vol2/Linux/docs/advanced-routing.tex . You
- will need supporting software from ftp://ftp.inr.ac.ru/ip-routing/
-
+ documentation at <http://www.compendium.com.ar/policy-routing.txt>
+ and <ftp://post.tepkom.ru/pub/vol2/Linux/docs/advanced-routing.tex>.
+ You will need supporting software from
+ <ftp://ftp.inr.ac.ru/ip-routing/>.
+
If unsure, say N.
-
-IP: equal cost multipath
+
+Equal cost multipath
CONFIG_IP_ROUTE_MULTIPATH
Normally, the routing tables specify a single action to be taken in
a deterministic manner for a given packet. If you say Y here
@@ -4177,20 +4961,20 @@
equal "cost" and chooses one of them in a non-deterministic fashion
if a matching packet arrives.
-IP: use TOS value as routing key
+Use TOS value as routing key
CONFIG_IP_ROUTE_TOS
The header of every IP packet carries a TOS (Type Of Service) value
- with which the packet requests a certain treatment, e.g. low latency
- (for interactive traffic), high throughput, or high reliability. If
- you say Y here, you will be able to specify different routes for
- packets with different TOS values.
+ with which the packet requests a certain treatment, e.g. low
+ latency (for interactive traffic), high throughput, or high
+ reliability. If you say Y here, you will be able to specify
+ different routes for packets with different TOS values.
-IP: use netfilter MARK value as routing key
+Use netfilter MARK value as routing key
CONFIG_IP_ROUTE_FWMARK
If you say Y here, you will be able to specify different routes for
packets with different mark values (see iptables(8), MARK target).
-IP: verbose route monitoring
+Verbose route monitoring
CONFIG_IP_ROUTE_VERBOSE
If you say Y here, which is recommended, then the kernel will print
verbose messages regarding the routing, for example warnings about
@@ -4199,20 +4983,20 @@
handled by the klogd daemon which is responsible for kernel messages
("man klogd").
-IP: large routing tables
+Large routing tables
CONFIG_IP_ROUTE_LARGE_TABLES
If you have routing zones that grow to more than about 64 entries,
you may want to say Y here to speed up the routing process.
-IP: fast network address translation
+Fast network address translation
CONFIG_IP_ROUTE_NAT
If you say Y here, your router will be able to modify source and
destination addresses of packets that pass through it, in a manner
- you specify. General information about Network Address Translation
+ you specify. General information about Network Address Translation
can be gotten from the document
- http://www.csn.tu-chemnitz.de/~mha/linux-ip-nat/diplom/nat.html
+ <http://www.csn.tu-chemnitz.de/~mha/linux-ip-nat/diplom/nat.html>.
-IP: kernel level autoconfiguration
+Kernel level IP autoconfiguration
CONFIG_IP_PNP
This enables automatic configuration of IP addresses of devices and
of the routing table during kernel boot, based on either information
@@ -4233,7 +5017,22 @@
does BOOTP itself, providing all necessary information on the kernel
command line, you can say N here. If unsure, say Y. Note that if you
want to use BOOTP, a BOOTP server must be operating on your network.
- Read Documentation/nfsroot.txt for details.
+ Read <file:Documentation/nfsroot.txt> for details.
+
+DHCP support
+CONFIG_IP_PNP_DHCP
+ If you want your Linux box to mount its whole root file system (the
+ one containing the directory /) from some other computer over the
+ net via NFS and you want the IP address of your computer to be
+ discovered automatically at boot time using the DHCP protocol (a
+ special protocol designed for doing this job), say Y here. In case
+ the boot ROM of your network card was designed for booting Linux and
+ does DHCP itself, providing all necessary information on the kernel
+ command line, you can say N here.
+
+ If unsure, say Y. Note that if you want to use DHCP, a DHCP server
+ must be operating on your network. Read
+ <file:Documentation/nfsroot.txt> for details.
RARP support
CONFIG_IP_PNP_RARP
@@ -4243,10 +5042,10 @@
discovered automatically at boot time using the RARP protocol (an
older protocol which is being obsoleted by BOOTP and DHCP), say Y
here. Note that if you want to use RARP, a RARP server must be
- operating on your network. Read Documentation/nfsroot.txt for
+ operating on your network. Read <file:Documentation/nfsroot.txt> for
details.
-IP: tunneling
+IP tunneling
CONFIG_NET_IPIP
Tunneling means encapsulating data of one protocol type within
another protocol and sending it over a channel that understands the
@@ -4256,13 +5055,13 @@
appear on a different network than it physically is, or to use
mobile-IP facilities (allowing laptops to seamlessly move between
networks without changing their IP addresses; check out
- http://anchor.cs.binghamton.edu/~mobileip/LJ/index.html ).
+ <http://anchor.cs.binghamton.edu/~mobileip/LJ/index.html>).
Saying Y to this option will produce two modules ( = code which can
be inserted in and removed from the running kernel whenever you
want). Most people won't need this and can say N.
-IP: GRE tunnels over IP
+GRE tunnels over IP
CONFIG_NET_IPGRE
Tunneling means encapsulating data of one protocol type within
another protocol and sending it over a channel that understands the
@@ -4270,18 +5069,18 @@
GRE (Generic Routing Encapsulation) and at this time allows
encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
This driver is useful if the other endpoint is a Cisco router: Cisco
- likes GRE much better than the other Linux tunneling driver ("IP:
+ likes GRE much better than the other Linux tunneling driver ("IP
tunneling" above). In addition, GRE allows multicast redistribution
through the tunnel.
-IP: broadcast GRE over IP
+Broadcast GRE over IP
CONFIG_NET_IPGRE_BROADCAST
One application of GRE/IP is to construct a broadcast WAN (Wide Area
Network), which looks like a normal Ethernet LAN (Local Area
Network), but can be distributed all over the Internet. If you want
- to do that, say Y here and to "IP: multicast routing" below.
+ to do that, say Y here and to "IP multicast routing" below.
-IP: multicast routing
+IP multicast routing
CONFIG_IP_MROUTE
This is used if you want your machine to act as a router for IP
packets that have several destination addresses. It is needed on the
@@ -4289,118 +5088,69 @@
audio and video broadcasts. In order to do that, you would most
likely run the program mrouted. Information about the multicast
capabilities of the various network cards is contained in
- Documentation/networking/multicast.txt. If you haven't heard about
- it, you don't need it.
+ <file:Documentation/networking/multicast.txt>. If you haven't heard
+ about it, you don't need it.
-IP: PIM-SM version 1 support
+PIM-SM version 1 support
CONFIG_IP_PIMSM_V1
Kernel side support for Sparse Mode PIM (Protocol Independent
Multicast) version 1. This multicast routing protocol is used widely
because Cisco supports it. You need special software to use it
- (pimd-v1). Please see http://netweb.usc.edu/pim/ for more
+ (pimd-v1). Please see <http://netweb.usc.edu/pim/> for more
information about PIM.
Say Y if you want to use PIM-SM v1. Note that you can say N here if
you just want to use Dense Mode PIM.
-IP: PIM-SM version 2 support
+PIM-SM version 2 support
CONFIG_IP_PIMSM_V2
Kernel side support for Sparse Mode PIM version 2. In order to use
this, you need an experimental routing daemon supporting it (pimd or
gated-5). This routing protocol is not used widely, so say N unless
you want to play with it.
-PC/TCP compatibility mode
-CONFIG_INET_PCTCP
- If you have been having difficulties telnetting to your Linux
- machine from a DOS system that uses (broken) PC/TCP networking
- software (all versions up to OnNet 2.0) over your local Ethernet try
- saying Y here. Everyone else says N.
-
- People having problems with NCSA telnet should see the file
- Documentation/networking/ncsa-telnet.
-
-Path MTU Discovery (normally enabled)
-CONFIG_PATH_MTU_DISCOVERY
- MTU (maximal transfer unit) is the size of the chunks we send out
- over the net. "Path MTU Discovery" means that, instead of always
- sending very small chunks, we start out sending big ones and if we
- then discover that some host along the way likes its chunks smaller,
- we adjust to a smaller size. This is good, so most people say Y
- here.
-
- However, some DOS software (versions of DOS NCSA telnet and Trumpet
- Winsock in PPP mode) is broken and won't be able to connect to your
- Linux machine correctly in all cases (especially through a terminal
- server) unless you say N here. See
- Documentation/networking/ncsa-telnet for the location of fixed NCSA
- telnet clients. If in doubt, say Y.
-
-Disable NAGLE algorithm (normally enabled)
-CONFIG_TCP_NAGLE_OFF
- The NAGLE algorithm works by requiring an acknowledgment before
- sending small IP frames (packets). This keeps tiny telnet and
- rlogin packets from congesting Wide Area Networks. Most people
- strongly recommend to say N here, thereby leaving NAGLE
- enabled. Those programs that would benefit from disabling this
- facility can do it on a per connection basis themselves.
-
-IP: Allow large windows (not recommended if <16 MB of memory)
-CONFIG_SKB_LARGE
- On high speed, long distance networks the performance limit on
- networking becomes the amount of data the sending machine can buffer
- until the other end confirms its reception. (At 45 Mbit/second there
- are a lot of bits between New York and London ...). If you say Y
- here, bigger buffers can be used which allows larger amounts of data
- to be "in flight" at any given time. It also means a user process
- can require a lot more memory for network buffers and thus this
- option is best used only on machines with 16 MB of memory or higher.
- Unless you are using long links with end to end speeds of over 2
- Mbit a second or satellite links this option will make no difference
- to performance.
-
Unix domain sockets
CONFIG_UNIX
If you say Y here, you will include support for Unix domain sockets;
sockets are the standard Unix mechanism for establishing and
- accessing network connections. Many commonly used programs such as
+ accessing network connections. Many commonly used programs such as
the X Window system and syslog use these sockets even if your
- machine is not connected to any network. Unless you are working on
+ machine is not connected to any network. Unless you are working on
an embedded system or something similar, you therefore definitely
want to say Y here.
However, the socket support is also available as a module ( = code
which can be inserted in and removed from the running kernel
- whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt. The module will be called
- unix.o. If you try building this as a module and you have said Y to
- "Kernel module loader support" above, be sure to add 'alias net-pf-1
- unix' to your /etc/modules.conf file. Note that several important
- services won't work correctly if you say M here and then neglect to
- load the module.
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>. The module will be
+ called unix.o. If you try building this as a module and you have
+ said Y to "Kernel module loader support" above, be sure to add
+ 'alias net-pf-1 unix' to your /etc/modules.conf file. Note that
+ several important services won't work correctly if you say M here
+ and then neglect to load the module.
Say Y unless you know what you are doing.
-The IPv6 protocol (EXPERIMENTAL)
+The IPv6 protocol
CONFIG_IPV6
This is experimental support for the next version of the Internet
Protocol: IP version 6 (also called IPng "IP next generation").
Features of this new protocol include: expanded address space,
authentication and privacy, and seamless interoperability with the
current version of IP (IP version 4). For general information about
- IPv6, see http://playground.sun.com/pub/ipng/html/ipng-main.html ;
+ IPv6, see <http://playground.sun.com/pub/ipng/html/ipng-main.html>;
for specific information about IPv6 under Linux read the HOWTO at
- http://www.bieringer.de/linux/IPv6/ and the file net/ipv6/README in
- the kernel source.
+ <http://www.bieringer.de/linux/IPv6/> and the file net/ipv6/README
+ in the kernel source.
If you want to use IPv6, please upgrade to the newest net-tools as
- given in Documentation/Changes. You will still be able to do regular
- IPv4 networking as well.
+ given in <file:Documentation/Changes>. You will still be able to do
+ regular IPv4 networking as well.
This protocol support is also available as a module ( = code which
can be inserted in and removed from the running kernel whenever you
want). The module will be called ipv6.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt.
+ as a module, say M here and read <file:Documentation/modules.txt>.
It is safe to say N here for now.
@@ -4410,8 +5160,8 @@
through the old netlink interface. However, a better option is to
say Y to "Kernel/User network link driver" and to "Routing
messages" instead.
-
-Kernel httpd acceleration (EXPERIMENTAL)
+
+Kernel httpd acceleration
CONFIG_KHTTPD
The kernel httpd acceleration daemon (kHTTPd) is a (limited) web
server built into the kernel. It is limited since it can only serve
@@ -4430,17 +5180,17 @@
The kHTTPd is experimental. Be careful when using it on a production
machine. Also note that kHTTPd doesn't support virtual servers yet.
-IPX networking
+The IPX protocol
CONFIG_IPX
This is support for the Novell networking protocol, IPX, commonly
- used for local networks of Windows machines. You need it if you want
- to access Novell NetWare file or print servers using the Linux
+ used for local networks of Windows machines. You need it if you
+ want to access Novell NetWare file or print servers using the Linux
Novell client ncpfs (available from
- ftp://metalab.unc.edu/pub/Linux/system/filesystems/ ) or from within
- the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto ). In order to do the
- former, you'll also have to say Y to "NCP file system support",
- below.
+ <ftp://metalab.unc.edu/pub/Linux/system/filesystems/>) or from
+ within the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO,
+ available from <http://www.linuxdoc.org/docs.html#howto>). In order
+ to do the former, you'll also have to say Y to "NCP file system
+ support", below.
IPX is similar in scope to IP, while SPX, which runs on top of IPX,
is similar to TCP. There is also experimental support for SPX in
@@ -4448,22 +5198,22 @@
To turn your Linux box into a fully featured NetWare file server and
IPX router, say Y here and fetch either lwared from
- ftp://metalab.unc.edu/pub/Linux/system/network/daemons/ or mars_nwe
- from ftp://ftp.gwdg.de/pub/linux/misc/ncpfs . For more information,
- read the IPX-HOWTO available from
- http://www.linuxdoc.org/docs.html#howto .
+ <ftp://metalab.unc.edu/pub/Linux/system/network/daemons/> or
+ mars_nwe from <ftp://ftp.gwdg.de/pub/linux/misc/ncpfs>. For more
+ information, read the IPX-HOWTO available from
+ <http://www.linuxdoc.org/docs.html#howto>.
General information about how to connect Linux, Windows machines and
- Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
+ Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
The IPX driver would enlarge your kernel by about 16 KB. This driver
is also available as a module ( = code which can be inserted in and
- removed from the running kernel whenever you want). The module will
- be called ipx.o. If you want to compile it as a module, say M here
- and read Documentation/modules.txt. Unless you want to integrate
- your Linux box with a local Novell network, say N.
+ removed from the running kernel whenever you want). The module will
+ be called ipx.o. If you want to compile it as a module, say M here
+ and read <file:Documentation/modules.txt>. Unless you want to
+ integrate your Linux box with a local Novell network, say N.
-IPX: Full internal IPX network
+Full internal IPX network
CONFIG_IPX_INTERN
Every IPX network has an address that identifies it. Sometimes it is
useful to give an IPX "network" address to your Linux box as well
@@ -4472,7 +5222,7 @@
same address). The way this is done is to create a virtual internal
"network" inside your box and to assign an IPX address to this
network. Say Y here if you want to do this; read the IPX-HOWTO at
- http://www.linuxdoc.org/docs.html#howto for details.
+ <http://www.linuxdoc.org/docs.html#howto> for details.
The full internal IPX network enables you to allocate sockets on
different virtual nodes of the internal network. This is done by
@@ -4485,12 +5235,17 @@
'special' sockets to sockets listening on the primary network is
disabled. This might break existing applications, especially RIP/SAP
daemons. A RIP/SAP daemon that works well with the full internal net
- can be found on ftp://ftp.gwdg.de/pub/linux/misc/ncpfs .
+ can be found on <ftp://ftp.gwdg.de/pub/linux/misc/ncpfs>.
If you don't know what you are doing, say N.
-IPX: SPX networking (EXPERIMENTAL)
+#(We're told this will come back someday)
+
+SPX networking
CONFIG_SPX
+ * Orphaned entry retained 20 April 2001 by Petr Vandrovec *
+ * If you read this note from the configurator, please contact *
+ * the Configure.help maintainers. *
The Sequenced Packet eXchange protocol is a transport layer protocol
built on top of IPX. It is used in Novell NetWare systems for
client-server applications and is similar to TCP (which runs on top
@@ -4502,26 +5257,26 @@
space programs lwared or mars_nwe for the server side).
Say Y here if you have use for SPX; read the IPX-HOWTO at
- http://www.linuxdoc.org/docs.html#howto for details.
+ <http://www.linuxdoc.org/docs.html#howto> for details.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called af_spx.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
-DECnet networking (EXPERIMENTAL)
+DECnet networking
CONFIG_DECNET
The DECnet networking protocol was used in many products made by
- Digital (now Compaq). It provides reliable stream and sequenced
+ Digital (now Compaq). It provides reliable stream and sequenced
packet communications over which run a variety of services similar
to those which run over TCP/IP.
To find some tools to use with the kernel layer support, please
- look at Patrick Caulfield's web site:
- http://linux.dreamtime.org/decnet/
+ look at Patrick Caulfield's web site:
+ <http://linux.dreamtime.org/decnet/>.
- More detailed documentation is available in the
- Documentation/networking/decnet.txt file.
+ More detailed documentation is available in
+ <file:Documentation/networking/decnet.txt>.
Be sure to say Y to "/proc file system support" and "Sysctl support"
below when using DECnet, since you will need sysctl support to aid
@@ -4533,27 +5288,27 @@
DECnet SIOCFIGCONF support
CONFIG_DECNET_SIOCGIFCONF
- This option should only be turned on if you are really sure that
- you know what you are doing. It can break other applications which
- use this system call and the proper way to get the information
- provided by this call is to use rtnetlink.
-
- If unsure, say N.
+ This option should only be turned on if you are really sure that
+ you know what you are doing. It can break other applications which
+ use this system call and the proper way to get the information
+ provided by this call is to use rtnetlink.
+
+ If unsure, say N.
-DECnet Router Support (EXPERIMENTAL)
+DECnet router support
CONFIG_DECNET_ROUTER
- Add support for turning your DECnet Endnode into a level 1 or 2
- router. This is an unfinished option for developers only. If you do
- say Y here, then make sure that you also say Y to "Kernel/User
- network link driver", "Routing messages" and "Network packet
- filtering". The first two are required to allow configuration via
- rtnetlink (currently you need Alexey Kuznetsov's iproute2 package
- from ftp://ftp.inr.ac.ru). The "Network packet filtering" option
- will be required for the forthcoming routing daemon to work.
+ Add support for turning your DECnet Endnode into a level 1 or 2
+ router. This is an unfinished option for developers only. If you
+ do say Y here, then make sure that you also say Y to "Kernel/User
+ network link driver", "Routing messages" and "Network packet
+ filtering". The first two are required to allow configuration via
+ rtnetlink (currently you need Alexey Kuznetsov's iproute2 package
+ from <ftp://ftp.inr.ac.ru>). The "Network packet filtering" option
+ will be required for the forthcoming routing daemon to work.
- See Documentation/networking/decnet.txt for more information.
+ See <file:Documentation/networking/decnet.txt> for more information.
-DECnet: use FWMARK value as routing key
+Use FWMARK value as DECnet routing key
CONFIG_DECNET_ROUTE_FWMARK
If you say Y here, you will be able to specify different routes for
packets with different FWMARK ("firewalling mark") values
@@ -4568,28 +5323,29 @@
AppleTalk protocol support
CONFIG_ATALK
AppleTalk is the way Apple computers speak to each other on a
- network. If your Linux box is connected to such a network and you
- want to join the conversation, say Y. You will need to use the
+ network. If your Linux box is connected to such a network and you
+ want to join the conversation, say Y. You will need to use the
netatalk package so that your Linux box can act as a print and file
- server for Macs as well as access AppleTalk printers. Check out
- http://www.zettabyte.net/netatalk/ on the WWW for details. EtherTalk
- is the name used for AppleTalk over Ethernet and the cheaper and
- slower LocalTalk is AppleTalk over a proprietary Apple network using
- serial links. EtherTalk and LocalTalk are fully supported by Linux.
+ server for Macs as well as access AppleTalk printers. Check out
+ <http://www.zettabyte.net/netatalk/> on the WWW for details.
+ EtherTalk is the name used for AppleTalk over Ethernet and the
+ cheaper and slower LocalTalk is AppleTalk over a proprietary Apple
+ network using serial links. EtherTalk and LocalTalk are fully
+ supported by Linux.
General information about how to connect Linux, Windows machines and
- Macs is on the WWW at http://www.eats.com/linux_mac_win.html . The
+ Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>. The
NET-3-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto , contains valuable
+ <http://www.linuxdoc.org/docs.html#howto>, contains valuable
information as well.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module is called appletalk.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt. You almost
- certainly want to compile it as a module so you can restart your
- AppleTalk stack without rebooting your machine. I hear that the
- GNU boycott of Apple is over, so even politically correct people
+ The module is called appletalk.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>. You
+ almost certainly want to compile it as a module so you can restart
+ your AppleTalk stack without rebooting your machine. I hear that
+ the GNU boycott of Apple is over, so even politically correct people
are allowed to say Y here.
AppleTalk-IP driver support
@@ -4600,7 +5356,7 @@
box is stuck on an AppleTalk only network) or decapsulate (e.g. if
you want your Linux box to act as an Internet gateway for a zoo of
AppleTalk connected Macs). Please see the file
- Documentation/networking/ipddp.txt for more information.
+ <file:Documentation/networking/ipddp.txt> for more information.
If you say Y here, the AppleTalk-IP support will be compiled into
the kernel. In this case, you can either use encapsulation or
@@ -4609,11 +5365,11 @@
If you say M here, the AppleTalk-IP support will be compiled as a
module ( = code which can be inserted in and removed from the
- running kernel whenever you want, read Documentation/modules.txt).
- The module is called ipddp.o. In this case, you will be able to use
- both encapsulation and decapsulation simultaneously, by loading two
- copies of the module and specifying different values for the module
- option ipddp_mode.
+ running kernel whenever you want, read
+ <file:Documentation/modules.txt>). The module is called ipddp.o.
+ In this case, you will be able to use both encapsulation and
+ decapsulation simultaneously, by loading two copies of the module
+ and specifying different values for the module option ipddp_mode.
IP to AppleTalk-IP Encapsulation support
CONFIG_IPDDP_ENCAP
@@ -4621,20 +5377,20 @@
IP packets inside AppleTalk frames; this is useful if your Linux box
is stuck on an AppleTalk network (which hopefully contains a
decapsulator somewhere). Please see
- Documentation/networking/ipddp.txt for more information. If you said
- Y to "AppleTalk-IP driver support" above and you say Y here, then
- you cannot say Y to "AppleTalk-IP to IP Decapsulation support",
- below.
+ <file:Documentation/networking/ipddp.txt> for more information. If
+ you said Y to "AppleTalk-IP driver support" above and you say Y
+ here, then you cannot say Y to "AppleTalk-IP to IP Decapsulation
+ support", below.
AppleTalk-IP to IP Decapsulation support
CONFIG_IPDDP_DECAP
If you say Y here, the AppleTalk-IP code will be able to decapsulate
AppleTalk-IP frames to IP packets; this is useful if you want your
Linux box to act as an Internet gateway for an AppleTalk network.
- Please see Documentation/networking/ipddp.txt for more information.
- If you said Y to "AppleTalk-IP driver support" above and you say Y
- here, then you cannot say Y to "IP to AppleTalk-IP Encapsulation
- support", above.
+ Please see <file:Documentation/networking/ipddp.txt> for more
+ information. If you said Y to "AppleTalk-IP driver support" above
+ and you say Y here, then you cannot say Y to "IP to AppleTalk-IP
+ Encapsulation support", above.
Apple/Farallon LocalTalk PC card support
CONFIG_LTPC
@@ -4643,7 +5399,7 @@
If you are in doubt, this card is the one with the 65C02 chip on it.
You also need version 1.3.3 or later of the netatalk package.
This driver is experimental, which means that it may not work.
- See the file Documentation/networking/ltpc.txt.
+ See the file <file:Documentation/networking/ltpc.txt>.
COPS LocalTalk PC card support
CONFIG_COPS
@@ -4652,7 +5408,7 @@
package. This driver is experimental, which means that it may not
work. This driver will only work if you choose "AppleTalk DDP"
networking support, above.
- Please read the file Documentation/networking/cops.txt.
+ Please read the file <file:Documentation/networking/cops.txt>.
Dayna firmware support
CONFIG_COPS_DAYNA
@@ -4668,15 +5424,15 @@
Amateur Radio support
CONFIG_HAMRADIO
If you want to connect your Linux box to an amateur radio, answer Y
- here. You want to read http://www.tapr.org/tapr/html/pkthome.html
+ here. You want to read <http://www.tapr.org/tapr/html/pkthome.html>
and the HAM-HOWTO and the AX25-HOWTO, both available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
Note that the answer to this question won't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all
the questions about amateur radio.
-Amateur Radio AX.25 Level 2
+Amateur Radio AX.25 Level 2 protocol
CONFIG_AX25
This is the protocol used for computer communication over amateur
radio. It is either used by itself for point-to-point links, or to
@@ -4694,15 +5450,16 @@
Information about where to get supporting software for Linux amateur
radio as well as information about how to configure an AX.25 port is
contained in the AX25-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . You might also want to
- check out the file Documentation/networking/ax25.txt in the kernel
- source. More information about digital amateur radio in general is
- on the WWW at http://www.tapr.org/tapr/html/pkthome.html .
+ <http://www.linuxdoc.org/docs.html#howto>. You might also want to
+ check out the file <file:Documentation/networking/ax25.txt> in the
+ kernel source. More information about digital amateur radio in
+ general is on the WWW at
+ <http://www.tapr.org/tapr/html/pkthome.html>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called ax25.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
AX.25 DAMA Slave support
CONFIG_AX25_DAMA_SLAVE
@@ -4722,7 +5479,7 @@
slaves. If you say Y here, your Linux box will act as a DAMA server.
If unsure, say N.
-Amateur Radio NET/ROM
+Amateur Radio NET/ROM support
CONFIG_NETROM
NET/ROM is a network layer protocol on top of AX.25 useful for
routing.
@@ -4730,15 +5487,15 @@
A comprehensive listing of all the software for Linux amateur radio
users as well as information about how to configure an AX.25 port is
contained in the AX25-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . You also might want to
- check out the file Documentation/networking/ax25.txt. More
+ <http://www.linuxdoc.org/docs.html#howto>. You also might want to
+ check out the file <file:Documentation/networking/ax25.txt>. More
information about digital amateur radio in general is on the WWW at
- http://www.tapr.org/tapr/html/pkthome.html .
+ <http://www.tapr.org/tapr/html/pkthome.html>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called netrom.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
Amateur Radio X.25 PLP (Rose)
CONFIG_ROSE
@@ -4749,15 +5506,15 @@
A comprehensive listing of all the software for Linux amateur radio
users as well as information about how to configure an AX.25 port is
contained in the AX25-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . You also might want to
- check out the file Documentation/networking/ax25.txt. More
+ <http://www.linuxdoc.org/docs.html#howto>. You also might want to
+ check out the file <file:Documentation/networking/ax25.txt>. More
information about digital amateur radio in general is on the WWW at
- http://www.tapr.org/tapr/html/pkthome.html .
+ <http://www.tapr.org/tapr/html/pkthome.html>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called rose.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
Serial port KISS driver for AX.25
CONFIG_MKISS
@@ -4773,8 +5530,8 @@
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called mkiss.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called mkiss.o.
Serial port 6PACK driver for AX.25
CONFIG_6PACK
@@ -4787,12 +5544,12 @@
Note that this driver is still experimental and might cause
problems. For details about the features and the usage of the
- driver, read Documentation/networking/6pack.txt.
+ driver, read <file:Documentation/networking/6pack.txt>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called 6pack.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called 6pack.o.
BPQ Ethernet driver
CONFIG_BPQETHER
@@ -4813,7 +5570,7 @@
Currently, this driver supports Ottawa PI/PI2, Paccomm/Gracilis
PackeTwin, and S5SCC/DMA boards. They are detected automatically.
If you have one of these cards, say Y here and read the AX25-HOWTO,
- available from http://www.linuxdoc.org/docs.html#howto .
+ available from <http://www.linuxdoc.org/docs.html#howto>.
This driver can operate multiple boards simultaneously. If you
compile it as a module (by saying M instead of Y), it will be called
@@ -4829,7 +5586,7 @@
certain parameters, such as channel access timing, clock mode, and
DMA channel. This is accomplished with a small utility program,
dmascc_cfg, available at
- http://www.nt.tuwien.ac.at/~kkudielk/Linux/ . Please be sure to get
+ <http://www.nt.tuwien.ac.at/~kkudielk/Linux/>. Please be sure to get
at least version 1.27 of dmascc_cfg, as older versions will not
work with the current driver.
@@ -4837,27 +5594,28 @@
CONFIG_SCC
These cards are used to connect your Linux box to an amateur radio
in order to communicate with other computers. If you want to use
- this, read Documentation/networking/z8530drv.txt and the AX25-HOWTO,
- available from http://www.linuxdoc.org/docs.html#howto . Also
- make sure to say Y to "Amateur Radio AX.25 Level 2" support.
+ this, read <file:Documentation/networking/z8530drv.txt> and the
+ AX25-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>. Also make sure to say Y
+ to "Amateur Radio AX.25 Level 2" support.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called scc.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called scc.o.
+
+Support for TRX that feedback the tx signal to rx
+CONFIG_SCC_TRXECHO
+ Some transmitters feed the transmitted signal back to the receive
+ line. Say Y here to foil this by explicitly disabling the receiver
+ during data transmission. If in doubt, say Y.
-additional delay for PA0HZP OptoSCC compatible boards
+Additional delay for PA0HZP OptoSCC compatible boards
CONFIG_SCC_DELAY
Say Y here if you experience problems with the SCC driver not
- working properly; please read Documentation/networking/z8530drv.txt
- for details. If unsure, say N.
-
-#support for TRX that feedback the tx signal to rx
-#CONFIG_SCC_TRXECHO
-###
-### Don't know what's going on here.
-###
-#
+ working properly; please read
+ <file:Documentation/networking/z8530drv.txt> for details. If unsure,
+ say N.
YAM driver for AX.25
CONFIG_YAM
@@ -4867,7 +5625,7 @@
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt.
+ say M here and read <file:Documentation/modules.txt>.
BAYCOM picpar and par96 driver for AX.25
CONFIG_BAYCOM_PAR
@@ -4875,13 +5633,13 @@
connect to a parallel interface. The driver supports the picpar and
par96 designs. To configure the driver, use the sethdlc utility
available in the standard ax25 utilities package. For information on
- the modems, see http://www.baycom.de and the file
- Documentation/networking/baycom.txt.
+ the modems, see <http://www.baycom.de> and the file
+ <file:Documentation/networking/baycom.txt>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called baycom_par.o.
+ say M here and read <file:Documentation/modules.txt>. This is
+ recommended. The module will be called baycom_par.o.
BAYCOM EPP driver for AX.25
CONFIG_BAYCOM_EPP
@@ -4889,48 +5647,49 @@
connect to a parallel interface. The driver supports the EPP
designs. To configure the driver, use the sethdlc utility available
in the standard ax25 utilities package. For information on the
- modems, see http://www.baycom.de and the file
- Documentation/networking/baycom.txt.
+ modems, see <http://www.baycom.de> and the file
+ <file:Documentation/networking/baycom.txt>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called baycom_par.o.
+ say M here and read <file:Documentation/modules.txt>. This is
+ recommended. The module will be called baycom_par.o.
-BAYCOM ser12 full duplex driver for AX.25
+BAYCOM ser12 full-duplex driver for AX.25
CONFIG_BAYCOM_SER_FDX
This is one of two drivers for Baycom style simple amateur radio
modems that connect to a serial interface. The driver supports the
- ser12 design in full duplex mode. In addition, it allows the
+ ser12 design in full-duplex mode. In addition, it allows the
baudrate to be set between 300 and 4800 baud (however not all modems
support all baudrates). This is the preferred driver. The next
- driver, "BAYCOM ser12 half duplex driver for AX.25" is the old
+ driver, "BAYCOM ser12 half-duplex driver for AX.25" is the old
driver and still provided in case this driver does not work with
your serial interface chip. To configure the driver, use the sethdlc
utility available in the standard ax25 utilities package. For
- information on the modems, see http://www.baycom.de and
- Documentation/networking/baycom.txt.
+ information on the modems, see <http://www.baycom.de> and
+ <file:Documentation/networking/baycom.txt>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called baycom_ser_fdx.o.
+ say M here and read <file:Documentation/modules.txt>. This is
+ recommended. The module will be called baycom_ser_fdx.o.
-BAYCOM ser12 half duplex driver for AX.25
+BAYCOM ser12 half-duplex driver for AX.25
CONFIG_BAYCOM_SER_HDX
This is one of two drivers for Baycom style simple amateur radio
modems that connect to a serial interface. The driver supports the
- ser12 design in full duplex mode. This is the old driver. It is
+ ser12 design in full-duplex mode. This is the old driver. It is
still provided in case your serial interface chip does not work with
- the full duplex driver. This driver is depreciated. To configure the
- driver, use the sethdlc utility available in the standard ax25
+ the full-duplex driver. This driver is depreciated. To configure
+ the driver, use the sethdlc utility available in the standard ax25
utilities package. For information on the modems, see
- http://www.baycom.de and Documentation/networking/baycom.txt.
+ <http://www.baycom.de> and
+ <file:Documentation/networking/baycom.txt>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called baycom_ser_hdx.o.
+ say M here and read <file:Documentation/modules.txt>. This is
+ recommended. The module will be called baycom_ser_hdx.o.
Sound card modem driver for AX.25
CONFIG_SOUNDMODEM
@@ -4942,13 +5701,13 @@
To configure the driver, use the sethdlc, smdiag and smmixer
utilities available in the standard ax25 utilities package. For
information on how to key the transmitter, see
- http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html and
- Documentation/networking/soundmodem.txt.
+ <http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html> and
+ <file:Documentation/networking/soundmodem.txt>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called soundmodem.o.
+ say M here and read <file:Documentation/modules.txt>. This is
+ recommended. The module will be called soundmodem.o.
Sound card modem support for Sound Blaster and compatible cards
CONFIG_SOUNDMODEM_SBC
@@ -4957,7 +5716,7 @@
with a Sound Blaster emulation) you should say N here and Y to
"Sound card modem support for WSS and Crystal cards", below, because
this usually results in better performance. This option also
- supports SB16/32/64 in full duplex mode.
+ supports SB16/32/64 in full-duplex mode.
Sound card modem support for WSS and Crystal cards
CONFIG_SOUNDMODEM_WSS
@@ -4965,8 +5724,8 @@
compatible cards. These cards feature a codec chip from either
Analog Devices (such as AD1848, AD1845, AD1812) or Crystal
Semiconductors (such as CS4248, CS423x). This option also supports
- the WSS full duplex operation which currently works with Crystal
- CS423x chips. If you don't need full duplex operation, do not enable
+ the WSS full-duplex operation which currently works with Crystal
+ CS423x chips. If you don't need full-duplex operation, do not enable
it to save performance.
Sound card modem support for 1200 baud AFSK modulation
@@ -5026,7 +5785,7 @@
can only use one protocol at a time, depending on what the other end
can understand).
-CCITT X.25 Packet Layer (EXPERIMENTAL)
+CCITT X.25 Packet Layer
CONFIG_X25
X.25 is a set of standardized network protocols, similar in scope to
frame relay; the one physical line from your box to the X.25 network
@@ -5037,13 +5796,13 @@
countries have public X.25 networks. X.25 consists of two
protocols: the higher level Packet Layer Protocol (PLP) (say Y here
if you want that) and the lower level data link layer protocol LAPB
- (say Y to "LAPB Data Link Driver" below if you want that).
+ (say Y to "LAPB Data Link Driver" below if you want that).
- You can read more about X.25 at http://www.sangoma.com/x25.htm and
- http://www.cisco.com/univercd/data/doc/software/11_0/rpcg/cx25.htm .
+ You can read more about X.25 at <http://www.sangoma.com/x25.htm> and
+ <http://www.cisco.com/univercd/data/doc/software/11_0/rpcg/cx25.htm>.
Information about X.25 for Linux is contained in the files
- Documentation/networking/x25.txt and
- Documentation/networking/x25-iface.txt.
+ <file:Documentation/networking/x25.txt> and
+ <file:Documentation/networking/x25-iface.txt>.
One connects to an X.25 network either with a dedicated network card
using the X.21 protocol (not yet supported by Linux) or one can do
@@ -5051,14 +5810,14 @@
to "X.25 async driver" below) or over Ethernet using an ordinary
Ethernet card and either the 802.2 LLC protocol (say Y to "802.2
LLC" below) or LAPB over Ethernet (say Y to "LAPB Data Link Driver"
- and "LAPB over Ethernet driver" below).
+ and "LAPB over Ethernet driver" below).
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called x25.o. If unsure, say N.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called x25.o. If unsure, say N.
-LAPB Data Link Driver (EXPERIMENTAL)
+LAPB Data Link Driver
CONFIG_LAPB
Link Access Procedure, Balanced (LAPB) is the data link layer (i.e.
the lower) part of the X.25 protocol. It offers a reliable
@@ -5069,41 +5828,42 @@
currently supports LAPB only over Ethernet connections. If you want
to use LAPB connections over Ethernet, say Y here and to "LAPB over
Ethernet driver" below. Read
- Documentation/networking/lapb-module.txt for technical details.
+ <file:Documentation/networking/lapb-module.txt> for technical
+ details.
If you want to compile this driver as a module though ( = code which
can be inserted in and removed from the running kernel whenever you
- want), say M here and read Documentation/modules.txt. The module
- will be called lapb.o. If unsure, say N.
+ want), say M here and read <file:Documentation/modules.txt>. The
+ module will be called lapb.o. If unsure, say N.
-802.2 LLC (EXPERIMENTAL)
+802.2 LLC
CONFIG_LLC
This is a Logical Link Layer protocol used for X.25 connections over
- Ethernet, using ordinary Ethernet cards.
+ Ethernet, using ordinary Ethernet cards.
-
-Frame Diverter (EXPERIMENTAL)
+Frame Diverter
CONFIG_NET_DIVERT
The Frame Diverter allows you to divert packets from the
- network, that are not aimed at the interface receiving it (in
- promisc. mode). Typically, a Linux box setup as an ethernet bridge
- with the Frames Diverter on, can do some *really* transparent www
+ network, that are not aimed at the interface receiving it (in
+ promisc. mode). Typically, a Linux box setup as an Ethernet bridge
+ with the Frames Diverter on, can do some *really* transparent www
caching using a Squid proxy for example.
This is very useful when you don't want to change your router's
config (or if you simply don't have access to it).
- The other possible usages of diverting Ethernet Frames are numberous:
+ The other possible usages of diverting Ethernet Frames are
+ numberous:
- reroute smtp traffic to another interface
- traffic-shape certain network streams
- transparently proxy smtp connections
- etc...
For more informations, please refer to:
- http://www.freshmeat.net/projects/etherdivert
- http://perso.wanadoo.fr/magpie/EtherDivert.html
+ <http://www.freshmeat.net/projects/etherdivert>
+ <http://perso.wanadoo.fr/magpie/EtherDivert.html>
- If unsure, say N
+ If unsure, say N.
802.1d Ethernet Bridging
CONFIG_BRIDGE
@@ -5113,21 +5873,22 @@
Several such bridges can work together to create even larger
networks of Ethernets using the IEEE 802.1 spanning tree algorithm.
As this is a standard, Linux bridges will cooperate properly with
- other third party bridge products.
+ other third party bridge products.
+
+ In order to use the Ethernet bridge, you'll need the bridge
+ configuration tools; see <file:Documentation/networking/bridge.txt>
+ for location. Please read the Bridge mini-HOWTO for more
+ information.
- In order to use the ethernet bridge, you'll need the bridge
- configuration tools; see Documentation/networking/bridge.txt for
- location. Please read the Bridge mini-HOWTO for more information.
-
Note that if your box acts as a bridge, it probably contains several
Ethernet devices, but the kernel is not able to recognize more than
one at boot time without help; for details read the Ethernet-HOWTO,
- available from in http://www.linuxdoc.org/docs.html#howto .
+ available from in <http://www.linuxdoc.org/docs.html#howto>.
If you want to compile this code as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called bridge.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called bridge.o.
If unsure, say N.
@@ -5135,15 +5896,15 @@
CONFIG_PACKET
The Packet protocol is used by applications which communicate
directly with network devices without an intermediate network
- protocol implemented in the kernel, e.g. tcpdump. If you want them
- to work, choose Y.
+ protocol implemented in the kernel, e.g. tcpdump. If you want them
+ to work, choose Y.
This driver is also available as a module called af_packet.o ( =
code which can be inserted in and removed from the running kernel
- whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt; if you use modprobe or
- kmod, you may also want to add "alias net-pf-17 af_packet" to
- /etc/modules.conf.
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>; if you use modprobe
+ or kmod, you may also want to add "alias net-pf-17 af_packet" to
+ /etc/modules.conf.
If unsure, say Y.
@@ -5157,17 +5918,17 @@
Kernel/User network link driver
CONFIG_NETLINK
This driver allows for two-way communication between the kernel and
- user processes. It does so by creating a new socket family, PF_NETLINK.
- Over this socket, the kernel can send and receive datagrams carrying
- information. It is documented on many systems in netlink(7), a HOWTO is
- provided as well, for example on
- http://snafu.freedom.org/linux2.2/docs/netlink-HOWTO.html
+ user processes. It does so by creating a new socket family,
+ PF_NETLINK. Over this socket, the kernel can send and receive
+ datagrams carrying information. It is documented on many systems in
+ netlink(7), a HOWTO is provided as well, for example on
+ <http://snafu.freedom.org/linux2.2/docs/netlink-HOWTO.html>.
So far, the kernel uses this feature to publish some network related
information if you say Y to "Routing messages", below. You also need
to say Y here if you want to use arpd, a daemon that helps keep the
internal ARP cache (a mapping between IP addresses and hardware
- addresses on the local network) small. The ethertap device, which
+ addresses on the local network) small. The ethertap device, which
lets user space programs read and write raw Ethernet frames, also
needs the network link driver.
@@ -5177,7 +5938,7 @@
CONFIG_RTNETLINK
If you say Y here, user space programs can receive some network
related routing information over the netlink. 'rtmon', supplied
- with the iproute2 package (ftp://ftp.inr.ac.ru), can read and
+ with the iproute2 package (<ftp://ftp.inr.ac.ru>), can read and
interpret this data. Information sent to the kernel over this link
is ignored.
@@ -5192,17 +5953,17 @@
Asynchronous Transfer Mode (ATM)
CONFIG_ATM
ATM is a high-speed networking technology for Local Area Networks
- and Wide Area Networks. It uses a fixed packet size and is
+ and Wide Area Networks. It uses a fixed packet size and is
connection oriented, allowing for the negotiation of minimum
bandwidth requirements.
-
+
In order to participate in an ATM network, your Linux box needs an
ATM networking card. If you have that, say Y here and to the driver
of your ATM card below.
Note that you need a set of user-space programs to actually make use
- of ATM. See the file Documentation/networking/atm.txt for further
- details.
+ of ATM. See the file <file:Documentation/networking/atm.txt> for
+ further details.
Classical IP over ATM
CONFIG_ATM_CLIP
@@ -5247,9 +6008,9 @@
The driver works with MMF (-MF or ...F) and UTP-5 (-U5 or ...D)
adapters.
- This driver is also available as a module. If you want to compile
- it as a module, say M here and read Documentation/modules.txt. The
- module will be called eni.o.
+ This driver is also available as a module. If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>. The module will be called eni.o.
Enable extended debugging
CONFIG_ATM_ENI_DEBUG
@@ -5296,7 +6057,7 @@
Burst four words at once in the send direction. You may want to try
this if you have disabled 8W bursts. Enabling 4W if 8W is also set
may or may not improve throughput.
-
+
Enable 2W TX bursts (optional)
CONFIG_ATM_ENI_BURST_TX_2W
Burst two words at once in the send direction. You may want to try
@@ -5331,9 +6092,9 @@
Driver for the ZeitNet ZN1221 (MMF) and ZN1225 (UTP-5) 155 Mbps ATM
adapters.
- This driver is also available as a module. If you want to compile
- it as a module, say M here and read Documentation/modules.txt. The
- module will be called zatm.o.
+ This driver is also available as a module. If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>. The module will be called zatm.o.
Enable extended debugging
CONFIG_ATM_ZATM_DEBUG
@@ -5345,12 +6106,13 @@
Fujitsu FireStream (FS50/FS155)
CONFIG_ATM_FIRESTREAM
- Driver for the Fujitsu FireStream 155 (MB86697) and
+ Driver for the Fujitsu FireStream 155 (MB86697) and
FireStream 50 (MB86695) ATM PCI chips.
- This driver is also available as a module. If you want to compile
- it as a module, say M here and read Documentation/modules.txt. The
- module will be called firestream.o.
+ This driver is also available as a module. If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>. The module will be called
+ firestream.o.
Enable usec resolution timestamps
CONFIG_ATM_ZATM_EXACT_TS
@@ -5368,21 +6130,22 @@
25 and for 155 Mbps, including IDT cards and the Fore ForeRunnerLE
series. Say Y if you have one of those.
- This driver is also available as a module. If you want to compile
- it as a module, say M here and read Documentation/modules.txt. The
- module will be called nicstar.o.
+ This driver is also available as a module. If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>. The module will be called
+ nicstar.o.
-ForeRunner LE155 PHYsical layer
+Use suni PHY driver (155Mbps)
CONFIG_ATM_NICSTAR_USE_SUNI
Support for the S-UNI and compatible PHYsical layer chips. These are
found in most 155Mbps NICStAR based ATM cards, namely in the
- ForeRunner LE155 cards. This driver provides detection of cable
+ ForeRunner LE155 cards. This driver provides detection of cable~
removal and reinsertion and provides some statistics. This driver
doesn't have removal capability when compiled as a module, so if you
need that capability don't include S-UNI support (it's not needed to
make the card work).
-ForeRunner LE25 PHYsical layer
+Use IDT77015 PHY driver (25Mbps)
CONFIG_ATM_NICSTAR_USE_IDT77105
Support for the PHYsical layer chip in ForeRunner LE25 cards. In
addition to cable removal/reinsertion detection, this driver allows
@@ -5390,6 +6153,31 @@
This driver is required for proper handling of temporary carrier
loss, so if you have a 25Mbps NICStAR based ATM card you must say Y.
+IDT 77252 (NICStAR II)
+CONFIG_ATM_IDT77252
+ Driver for the IDT 77252 ATM PCI chips.
+
+ This driver is also available as a module. If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>. The module will be called idt77252.o
+
+Enable debugging messages
+CONFIG_ATM_IDT77252_DEBUG
+ Somewhat useful debugging messages are available. The choice of
+ messages is controlled by a bitmap. This may be specified as a
+ module argument. See the file <file:drivers/atm/idt77252.h> for
+ the meanings of the bits in the mask.
+
+ When active, these messages can have a significant impact on the
+ speed of the driver, and the size of your syslog files! When
+ inactive, they will have only a modest impact on performance.
+
+Receive ALL cells in raw queue
+CONFIG_ATM_IDT77252_RCV_ALL
+ Enable receiving of all cells on the ATM link, that do not match
+ an open connection in the raw cell queue of the driver. Useful
+ for debugging or special applications only, so the safe answer is N.
+
Madge Ambassador (Collage PCI 155 Server)
CONFIG_ATM_AMBASSADOR
This is a driver for ATMizer based ATM card produced by Madge
@@ -5399,11 +6187,12 @@
Enable debugging messages
CONFIG_ATM_AMBASSADOR_DEBUG
Somewhat useful debugging messages are available. The choice of
- messages is controlled by a bitmap. This may be specified as a
+ messages is controlled by a bitmap. This may be specified as a
module argument (kernel command line argument as well?), changed
dynamically using an ioctl (not yet) or changed by sending the
- string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
- drivers/atm/ambassador.h for the meanings of the bits in the mask.
+ string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
+ <file:drivers/atm/ambassador.h> for the meanings of the bits in the
+ mask.
When active, these messages can have a significant impact on the
speed of the driver, and the size of your syslog files! When
@@ -5418,28 +6207,29 @@
Enable debugging messages
CONFIG_ATM_HORIZON_DEBUG
Somewhat useful debugging messages are available. The choice of
- messages is controlled by a bitmap. This may be specified as a
+ messages is controlled by a bitmap. This may be specified as a
module argument (kernel command line argument as well?), changed
dynamically using an ioctl (not yet) or changed by sending the
- string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
- drivers/atm/horizon.h for the meanings of the bits in the mask.
+ string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
+ <file:drivers/atm/horizon.h> for the meanings of the bits in the
+ mask.
When active, these messages can have a significant impact on the
speed of the driver, and the size of your syslog files! When
inactive, they will have only a modest impact on performance.
-Interphase ATM PCI x575/x525/x531
+Interphase ATM PCI x575/x525/x531
CONFIG_ATM_IA
This is a driver for the Interphase (i)ChipSAR adapter cards
- which include a variety of variants in term of the size of the
- control memory (128K-1KVC, 512K-4KVC), the size of the packet
- memory (128K, 512K, 1M), and the PHY type (Single/Multi mode OC3,
+ which include a variety of variants in term of the size of the
+ control memory (128K-1KVC, 512K-4KVC), the size of the packet
+ memory (128K, 512K, 1M), and the PHY type (Single/Multi mode OC3,
UTP155, UTP25, DS3 and E3). Go to:
www.iphase.com/products/ClassSheet.cfm?ClassID=ATM
- for more info about the cards. Say Y (or M to compile as a module
+ for more info about the cards. Say Y (or M to compile as a module
named iphase.o) here if you have one of these cards.
- See the file Documentation/networking/iphase.txt for further
+ See the file <file:Documentation/networking/iphase.txt> for further
details.
Enable debugging messages
@@ -5447,9 +6237,11 @@
Somewhat useful debugging messages are available. The choice of
messages is controlled by a bitmap. This may be specified as a
module argument (kernel command line argument as well?), changed
- dynamically using an ioctl (Get the debug utility, iadbg, from
- ftp.iphase.com/pub/atm/pci). See the file drivers/atm/iphase.h
- for the meanings of the bits in the mask.
+ dynamically using an ioctl (Get the debug utility, iadbg, from
+ <ftp://ftp.iphase.com/pub/atm/pci>).
+
+ See the file <file:drivers/atm/iphase.h> for the meanings of the
+ bits in the mask.
When active, these messages can have a significant impact on the
speed of the driver, and the size of your syslog files! When
@@ -5458,36 +6250,37 @@
Linux telephony support
CONFIG_PHONE
Say Y here if you have a telephony card, which for example allows
- you to use a regular phone for voice-over-IP applications.
+ you to use a regular phone for voice-over-IP applications.
- Note: this has nothing to do with modems. You do not need to say Y
+ Note: this has nothing to do with modems. You do not need to say Y
here in order to be able to use a modem under Linux.
- This support is also available as a module. If you want to compile
- it as a module, say M here and read Documentation/modules.txt. The
- module will be called phonedev.o.
+ This support is also available as a module. If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>. The module will be called
+ phonedev.o.
Compaq Smart Array support
CONFIG_BLK_CPQ_CISS_DA
- This is the driver for Compaq Smart Array 5xxx controllers.
- Everyone using these boards should say Y here.
- See Documentation/cciss.txt for the current list of
- boards supported by this driver, and for further information
- on the use of this driver.
+ This is the driver for Compaq Smart Array 5xxx controllers.
+ Everyone using these boards should say Y here.
+ See <file:Documentation/cciss.txt> for the current list of
+ boards supported by this driver, and for further information
+ on the use of this driver.
QuickNet Internet LineJack/PhoneJack support
CONFIG_PHONE_IXJ
Say M if you have a telephony card manufactured by Quicknet
Technologies, Inc. These include the Internet PhoneJACK and
Internet LineJACK Telephony Cards. You will get a module called
- ixj.o.
+ ixj.o.
For the ISA versions of these products, you can configure the
cards using the isapnp tools (pnpdump/isapnp) or you can use the
- isapnp support. Please read Documentation/telephony/ixj.txt.
+ isapnp support. Please read <file:Documentation/telephony/ixj.txt>.
For more information on these cards, see Quicknet's web site at:
- http://www.quicknet.net/ .
+ <http://www.quicknet.net/>.
If you do not have any Quicknet telephony cards, you can safely
say N here.
@@ -5498,66 +6291,66 @@
cards. It simultaneously supports PCA-200E and SBA-200E models
on PCI and SBUS hosts. Say Y (or M to compile as a module
named fore_200e.o) here if you have one of these ATM adapters.
-
+
Note that the driver will actually be compiled only if you
additionally enable the support for PCA-200E and/or SBA-200E
cards.
- See the file Documentation/networking/fore200e.txt for further
- details.
-
+ See the file <file:Documentation/networking/fore200e.txt> for
+ further details.
+
Enable PCA-200E card support on PCI-based hosts
CONFIG_ATM_FORE200E_PCA
Say Y here if you want your PCA-200E cards to be probed.
-
+
Use default PCA-200E firmware
CONFIG_ATM_FORE200E_PCA_DEFAULT_FW
Use the default PCA-200E firmware data shipped with the driver.
-
+
Normal users do not have to deal with the firmware stuff, so
they should say Y here.
-
+
Pathname of user-supplied binary firmware
CONFIG_ATM_FORE200E_PCA_FW
This defines the pathname of an alternative PCA-200E binary
firmware image supplied by the user. This pathname may be
absolute or relative to the drivers/atm directory.
-
+
The driver comes with an adequate firmware image, so normal users do
not have to supply an alternative one. They just say Y to "Use
default PCA-200E firmware" instead.
-
+
Enable SBA-200E card support on SBUS-based hosts
CONFIG_ATM_FORE200E_SBA
Say Y here if you want your SBA-200E cards to be probed.
-
+
Use default SBA-200E firmware
CONFIG_ATM_FORE200E_SBA_DEFAULT_FW
Use the default SBA-200E firmware data shipped with the driver.
-
+
Normal users do not have to deal with the firmware stuff, so
they should say Y here.
-
+
Pathname of user-supplied binary firmware
CONFIG_ATM_FORE200E_SBA_FW
This defines the pathname of an alternative SBA-200E binary
firmware image supplied by the user. This pathname may be
absolute or relative to the drivers/atm directory.
-
+
The driver comes with an adequate firmware image, so normal users do
not have to supply an alternative one. They just say Y to "Use
default SBA-200E firmware", above.
-
+
Maximum number of tx retries
CONFIG_ATM_FORE200E_TX_RETRY
Specifies the number of times the driver attempts to transmit
a message before giving up, if the transmit queue of the ATM card
is transiently saturated.
-
+
Saturation of the transmit queue may occur only under extreme
conditions, e.g. when a fast host continuously submits very small
frames (<64 bytes) or raw AAL0 cells (48 bytes) to the ATM adapter.
-
+
Note that under common conditions, it is unlikely that you encounter
a saturation of the transmit queue, so the retry mechanism never
comes into play.
@@ -5567,54 +6360,168 @@
Specifies the level of debugging messages issued by the driver.
The verbosity of the driver increases with the value of this
parameter.
-
+
When active, these messages can have a significant impact on
the performances of the driver, and the size of your syslog files!
Keep the debugging level to 0 during normal operations.
-SCSI support?
+Fusion MPT device support
+CONFIG_FUSION
+ LSI Logic Fusion(TM) Message Passing Technology (MPT) device support
+ provides high performance SCSI host initiator, and LAN [1] interface
+ services to a host system. The Fusion architecture is capable of
+ duplexing these protocols on high-speed Fibre Channel
+ (up to 2 GHz x 2 ports = 4 GHz) and parallel SCSI (up to Ultra-320)
+ physical medium.
+
+ [1] LAN is not supported on parallel SCSI medium.
+
+ These drivers require a Fusion MPT compatible PCI adapter installed
+ in the host system. MPT adapters contain specialized I/O processors
+ to handle I/O workload, and more importantly to offload this work
+ from the host CPU(s).
+
+ If you have Fusion MPT hardware and want to use it, you can say
+ Y or M here to add MPT (base + ScsiHost) drivers.
+ <Y> = build lib (fusion.o), and link [static] into the kernel [2]
+ proper
+ <M> = compiled as [dynamic] modules [3] named: (mptbase.o,
+ mptscsih.o)
+
+ [2] In order enable capability to boot the linux kernel
+ natively from a Fusion MPT target device, you MUST
+ answer Y here! (currently requires CONFIG_BLK_DEV_SD)
+ [3] This support is also available as a module ( = code
+ which can be inserted in and removed from the running
+ kernel whenever you want). If you want to compile as
+ modules, say M here and read
+ <file:Documentation/modules.txt>.
+
+ If unsure, say N.
+
+ If you say Y or M here you will get a choice of these
+ additional protocol and support module options: Module Name:
+ <M> Enhanced SCSI error reporting (isense.o)
+ <M> Fusion MPT misc device (ioctl) driver (mptctl.o)
+ <M> Fusion MPT LAN driver (mptlan.o)
+
+ ---
+ Fusion MPT is trademark of LSI Logic Corporation, and its
+ architecture is based on LSI Logic's Message Passing Interface (MPI)
+ specification.
+
+Fusion MPT enhanced SCSI error reporting [optional] module
+CONFIG_FUSION_ISENSE
+ The isense module (roughly stands for Interpret SENSE data) is
+ completely optional. It simply provides extra English readable
+ strings in SCSI Error Report(s) that might be generated from the
+ Fusion MPT SCSI Host driver, for example when a target device
+ returns a SCSI check condition on a I/O. Without this module
+ loaded you might see:
+
+ SCSI Error Report =-=-= (ioc0,scsi5:0)
+ SCSI_Status=02h (CHECK_CONDITION)
+ Original_CDB[]: 2A 00 00 00 00 41 00 00 02 00
+ SenseData[12h]: 70 00 02 00 00 00 00 0A 00 00 00 00 04 02 02 00 00 00
+ SenseKey=2h (NOT READY); FRU=02h
+ ASC/ASCQ=29h/00h
+
+ Where otherwise, if this module had been loaded, you would see:
+
+ SCSI Error Report =-=-= (ioc0,scsi5:0)
+ SCSI_Status=02h (CHECK_CONDITION)
+ Original_CDB[]: 2A 00 00 00 00 41 00 00 02 00 - "WRITE(10)"
+ SenseData[12h]: 70 00 02 00 00 00 00 0A 00 00 00 00 04 02 02 00 00 00
+ SenseKey=2h (NOT READY); FRU=02h
+ ASC/ASCQ=29h/00h "LOGICAL UNIT NOT READY, INITIALIZING CMD. REQUIRED"
+
+ Say M for "Enhanced SCSI error reporting" to compile this optional module,
+ creating a driver named: isense.o.
+
+ NOTE: Support for building this feature into the kernel is not
+ available, due to kernel size considerations.
+
+Fusion MPT misc device (ioctl) driver [optional] module
+CONFIG_FUSION_CTL
+ The Fusion MPT misc device driver provides specialized control
+ of MPT adapters via system ioctl calls. Use of ioctl calls to
+ the MPT driver requires that you create and use a misc device
+ node ala:
+ mknod /dev/mptctl c 10 240
+
+ One use of this ioctl interface is to perform an upgrade (reflash)
+ of the MPT adapter firmware. Refer to readme file(s) distributed
+ with the Fusion MPT linux driver for additional details.
+
+ If enabled by saying M to this, a driver named: mptctl.o
+ will be compiled.
+
+ If unsure whether you really want or need this, say N.
+
+Fusion MPT LAN driver [optional]
+CONFIG_FUSION_LAN
+ This module supports LAN IP traffic over Fibre Channel port(s)
+ on Fusion MPT compatible hardware (LSIFC9xx chips).
+ The physical interface used is defined in RFC 2625.
+ Please refer to that document for details.
+
+ Installing this driver requires the knowledge to configure and
+ activate a new network interface, "fc0", using standard Linux tools.
+
+ If enabled by saying M to this, a driver named: mptlan.o
+ will be compiled.
+
+ If unsure whether you really want or need this, say N.
+
+ NOTES: This feature is NOT available nor supported for linux-2.2.x
+ kernels. You must be building a linux-2.3.x or linux-2.4.x kernel
+ in order to configure this option.
+ Support for building this feature into the linux kernel is not
+ yet available.
+
+SCSI support
CONFIG_SCSI
- If you want to use a SCSI hard disk, SCSI tape drive, SCSI CDROM or
+ If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
any other SCSI device under Linux, say Y and make sure that you know
the name of your SCSI host adapter (the card inside your computer
that "speaks" the SCSI protocol, also called SCSI controller),
- because you will be asked for it.
+ because you will be asked for it.
You also need to say Y here if you want support for the parallel
port version of the 100 MB IOMEGA ZIP drive.
Please read the SCSI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . The
+ <http://www.linuxdoc.org/docs.html#howto>. The
SCSI-Programming-HOWTO contains information about how to add or
remove an SCSI device from a running Linux machine without
rebooting.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called scsi_mod.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt and
- Documentation/scsi.txt. However, do not compile this as a module if
- your root file system (the one containing the directory /) is
- located on a SCSI device.
+ The module will be called scsi_mod.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt> and
+ <file:Documentation/scsi.txt>. However, do not compile this as a
+ module if your root file system (the one containing the directory /)
+ is located on a SCSI device.
SCSI disk support
CONFIG_BLK_DEV_SD
If you want to use a SCSI hard disk or the SCSI or parallel port
version of the IOMEGA ZIP drive under Linux, say Y and read the
SCSI-HOWTO, the Disk-HOWTO and the Multi-Disk-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . This is NOT for SCSI
- CDROMs.
+ <http://www.linuxdoc.org/docs.html#howto>. This is NOT for SCSI
+ CD-ROMs.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called sd_mod.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt and
- Documentation/scsi.txt. Do not compile this driver as a module if
- your root file system (the one containing the directory /) is
- located on a SCSI disk. In this case, do not compile the driver for
- your SCSI host adapter (below) as a module either.
+ The module will be called sd_mod.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> and
+ <file:Documentation/scsi.txt>. Do not compile this driver as a
+ module if your root file system (the one containing the directory /)
+ is located on a SCSI disk. In this case, do not compile the driver
+ for your SCSI host adapter (below) as a module either.
-Extra SCSI Disks
+Maximum number of SCSI disks that can be loaded as modules
CONFIG_SD_EXTRA_DEVS
This controls the amount of additional space allocated in tables for
drivers that are loaded as modules after the kernel is booted. In
@@ -5628,63 +6535,76 @@
If you don't understand what's going on, go with the default.
+Maximum number of SCSI tapes that can be loaded as modules
+CONFIG_ST_EXTRA_DEVS
+ This controls the amount of additional space allocated in tables for
+ drivers that are loaded as modules after the kernel is booted. In
+ the event that the SCSI core itself was loaded as a module, this
+ value is the number of additional tapes that can be loaded after the
+ first host driver is loaded.
+
+ Admittedly this isn't pretty, but there are tons of race conditions
+ involved with resizing the internal arrays on the fly. Someday this
+ flag will go away, and everything will work automatically.
+
+ If you don't understand what's going on, go with the default.
+
SCSI tape support
CONFIG_CHR_DEV_ST
If you want to use a SCSI tape drive under Linux, say Y and read the
SCSI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto , and
- drivers/scsi/README.st in the kernel source. This is NOT for SCSI
- CDROMs.
+ <http://www.linuxdoc.org/docs.html#howto>, and
+ <file:drivers/scsi/README.st> in the kernel source. This is NOT for
+ SCSI CD-ROMs.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called st.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt and
- Documentation/scsi.txt .
+ module, say M here and read <file:Documentation/modules.txt> and
+ <file:Documentation/scsi.txt>.
OnStream SC-x0 SCSI tape support
CONFIG_CHR_DEV_OSST
- The OnStream SC-x0 SCSI tape drives can not be driven by the
- standard st driver, but instead need this special osst driver and
- use the /dev/osstX char device nodes (major 206).
- Via usb-storage and ide-scsi, you may be able to drive the USB-x0
- and DI-x0 drives as well. Note that there is also a second generation
- of OnStream tape drives (ADR-x0) that supports the standard SCSI-2
- commands for tapes (QIC-157) and can be driven by the standard
- driver st.
+ The OnStream SC-x0 SCSI tape drives can not be driven by the
+ standard st driver, but instead need this special osst driver and
+ use the /dev/osstX char device nodes (major 206). Via usb-storage
+ and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives
+ as well. Note that there is also a second generation of OnStream
+ tape drives (ADR-x0) that supports the standard SCSI-2 commands for
+ tapes (QIC-157) and can be driven by the standard driver st.
For more information, you may have a look at the SCSI-HOWTO
- ftp://metalab.unc.edu/pub/Linux/docs/HOWTO and
- drivers/scsi/README.osst in the kernel source.
- More info on the OnStream driver may be found on
- http://linux1.onstream.nl/test/
+ <ftp://metalab.unc.edu/pub/Linux/docs/HOWTO> and
+ <file:drivers/scsi/README.osst> in the kernel source.
+ More info on the OnStream driver may be found on
+ <http://linux1.onstream.nl/test/>
Please also have a look at the standard st docu, as most of it
applies to osst as well.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called osst.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt and
- Documentation/scsi.txt .
+ module, say M here and read <file:Documentation/modules.txt> and
+ <file:Documentation/scsi.txt>.
-SCSI CDROM support
+SCSI CD-ROM support
CONFIG_BLK_DEV_SR
- If you want to use a SCSI CDROM under Linux, say Y and read the
- SCSI-HOWTO and the CDROM-HOWTO at
- http://www.linuxdoc.org/docs.html#howto . Also make sure to say Y
- or M to "ISO 9660 CDROM file system support" later.
+ If you want to use a SCSI CD-ROM under Linux, say Y and read the
+ SCSI-HOWTO and the CD-ROM-HOWTO at
+ <http://www.linuxdoc.org/docs.html#howto>. Also make sure to say Y
+ or M to "ISO 9660 CD-ROM file system support" later.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called sr_mod.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt and
- Documentation/scsi.txt .
+ module, say M here and read <file:Documentation/modules.txt> and
+ <file:Documentation/scsi.txt>.
-Extra SCSI CDROMs
+Maximum number of CD-ROM devices that can be loaded as modules
CONFIG_SR_EXTRA_DEVS
This controls the amount of additional space allocated in tables for
drivers that are loaded as modules after the kernel is booted. In
the event that the SCSI core itself was loaded as a module, this
- value is the number of additional CDROMs that can be loaded after
+ value is the number of additional CD-ROMs that can be loaded after
the first host driver is loaded.
Admittedly this isn't pretty, but there are tons of race conditions
@@ -5693,7 +6613,7 @@
If you don't understand what's going on, go with the default.
-Enable vendor-specific extensions (for SCSI CDROM)
+Enable vendor-specific extensions (for SCSI CD-ROM)
CONFIG_BLK_DEV_SR_VENDOR
This enables the usage of vendor specific SCSI commands. This is
required to support multisession CDs with old NEC/TOSHIBA cdrom
@@ -5704,27 +6624,27 @@
CONFIG_CHR_DEV_SG
If you want to use SCSI scanners, synthesizers or CD-writers or just
about anything having "SCSI" in its name other than hard disks,
- CDROMs or tapes, say Y here. These won't be supported by the kernel
+ CD-ROMs or tapes, say Y here. These won't be supported by the kernel
directly, so you need some additional software which knows how to
talk to these devices using the SCSI protocol:
- For scanners, look at SANE (http://www.mostang.com/sane). For CD
+ For scanners, look at SANE (<http://www.mostang.com/sane>). For CD
writer software look at cdrecord
- (http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html)
+ (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
and for burning a "disk at once": cdrdao
- (http://www.ping.de/sites/daneb/cdrdao.html). Cdparanoia is a high
- quality digital reader of audio CDs (http://www.xiph.org/paranoia).
+ (<http://www.ping.de/sites/daneb/cdrdao.html>). Cdparanoia is a high
+ quality digital reader of audio CDs (<http://www.xiph.org/paranoia>).
For other devices, it's possible that you'll have to write the
driver software yourself. Please read the file
- Documentation/scsi-generic.txt for more information.
+ <file:Documentation/scsi-generic.txt> for more information.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt and
- Documentation/scsi.txt. The module will be called sg.o. If unsure,
+ say M here and read <file:Documentation/modules.txt> and
+ <file:Documentation/scsi.txt>. The module will be called sg.o. If unsure,
say N.
-Debug new queueing code for SCSI
+Enable extra checks in SCSI queueing code
CONFIG_SCSI_DEBUG_QUEUES
This option turns on a lot of additional consistency checking for
the new queueing code. This will adversely affect performance, but
@@ -5732,14 +6652,14 @@
This will typically cause the kernel to panic if an error is
detected, but it would have probably crashed if the panic weren't
there. Comments/questions/problems to linux-scsi mailing list
- please. See http://www.andante.org/scsi_queue.html for more
+ please. See <http://www.andante.org/scsi_queue.html> for more
up-to-date information.
Probe all LUNs on each SCSI device
CONFIG_SCSI_MULTI_LUN
If you have a SCSI device that supports more than one LUN (Logical
Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
- can say Y here to force the SCSI driver to probe for multiple LUNs.
+ can say Y here to force the SCSI driver to probe for multiple LUNs.
A SCSI device with multiple LUNs acts logically like multiple SCSI
devices. The vast majority of SCSI devices have only one LUN, and
so most people can say N here and should in fact do so, because it
@@ -5754,7 +6674,7 @@
SCSI logging facility
CONFIG_SCSI_LOGGING
This turns on a logging facility that can be used to debug a number
- of SCSI related problems.
+ of SCSI related problems.
If you say Y here, no logging output will appear by default, but you
can enable logging by saying Y to "/proc file system support" and
@@ -5765,25 +6685,37 @@
at boot time after the /proc file system has been mounted.
There are a number of things that can be used for 'token' (you can
- find them in the source: drivers/scsi/scsi.c), and this allows you
- to select the types of information you want, and the level allows
- you to select the level of verbosity.
+ find them in the source: <file:drivers/scsi/scsi.c>), and this
+ allows you to select the types of information you want, and the
+ level allows you to select the level of verbosity.
If you say N here, it may be harder to track down some types of SCSI
problems. If you say Y here your kernel will be somewhat larger, but
there should be no noticeable performance impact as long as you have
logging turned off.
+SGI WD93C93 SCSI Driver
+CONFIG_SCSI_SGIWD93
+ Say Y here to support the on-board WD93C93 SCSI controller found (a)
+ on the Indigo2 and other MIPS-based SGI machines, and (b) on ARCS
+ ARM-based machines.
+
+DEC NCR53C94 SCSI Driver
+CONFIG_SCSI_DECNCR
+ Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
+ based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
+
AdvanSys SCSI support
CONFIG_SCSI_ADVANSYS
This is a driver for all SCSI host adapters manufactured by
AdvanSys. It is documented in the kernel source in
- drivers/scsi/advansys.c.
+ <file:drivers/scsi/advansys.c>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. The module will be called advansys.o.
+ <file:Documentation/modules.txt>. The module will be called
+ advansys.o.
Adaptec AHA152X/2825 support
CONFIG_SCSI_AHA152X
@@ -5792,49 +6724,61 @@
must be manually specified in this case.
It is explained in section 3.3 of the SCSI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . You might also want to
- read the file drivers/scsi/README.aha152x.
+ <http://www.linuxdoc.org/docs.html#howto>. You might also want to
+ read the file <file:drivers/scsi/README.aha152x>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called aha152x.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
Adaptec AHA1542 support
CONFIG_SCSI_AHA1542
- This is support for a SCSI host adapter. It is explained in section
+ This is support for a SCSI host adapter. It is explained in section
3.4 of the SCSI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . Note that Trantor was
+ <http://www.linuxdoc.org/docs.html#howto>. Note that Trantor was
purchased by Adaptec, and some former Trantor products are being
- sold under the Adaptec name. If it doesn't work out of the box, you
- may have to change some settings in drivers/scsi/aha1542.h.
-
+ sold under the Adaptec name. If it doesn't work out of the box, you
+ may have to change some settings in <file:drivers/scsi/aha1542.h>.
+
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called aha1542.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called aha1542.o.
Adaptec AHA1740 support
CONFIG_SCSI_AHA1740
- This is support for a SCSI host adapter. It is explained in section
+ This is support for a SCSI host adapter. It is explained in section
3.5 of the SCSI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
+ <http://www.linuxdoc.org/docs.html#howto>. If it doesn't work out
of the box, you may have to change some settings in
- drivers/scsi/aha1740.h.
+ <file:drivers/scsi/aha1740.h>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called aha1740.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ The module will be called aha1740.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
-Adaptec AIC7xxx chipset SCSI controller support
+Adaptec AIC7xxx support
CONFIG_SCSI_AIC7XXX
- This driver supports all of Adaptec's PCI based SCSI controllers (not
- the hardware RAID controllers though) as well as the aic7770 based
- EISA and VLB SCSI controllers (the 274x and 284x series). This is
- an Adaptec sponsored driver written by Justin Gibbs. It is intended
- to replace the previous aic7xxx driver maintained by Doug Ledford since
- Doug is no longer maintaining that driver.
+ This driver supports all of Adaptec's PCI based SCSI controllers
+ (not the hardware RAID controllers though) as well as the aic7770
+ based EISA and VLB SCSI controllers (the 274x and 284x series).
+ This is an Adaptec sponsored driver written by Justin Gibbs. It is
+ intended to replace the previous aic7xxx driver maintained by Doug
+ Ledford since Doug is no longer maintaining that driver.
+
+Adaptec I2O RAID controllers
+CONFIG_SCSI_DPT_I2O
+ This driver supports all of Adaptec's I2O based RAID controllers as
+ well as the DPT SmartRaid V cards. This is an Adaptec maintained
+ driver by Deanna Bonds. See <file:drivers/scsi/README.dpti>.
+
+ This driver is also available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ If you want to compile it as a module, say M here and read
+ <file:Documentation/modules.txt>. The module will be called
+ dpt_i2o.o.
Default number of TCQ commands per device
CONFIG_AIC7XXX_CMDS_PER_DEVICE
@@ -5852,21 +6796,31 @@
Default: 253
-Initial Bus Reset Settle Delay
+Delay in seconds after SCSI bus reset
CONFIG_AIC7XXX_RESET_DELAY_MS
The number of milliseconds to delay after an initial bus reset.
The bus settle delay following all error recovery actions is
dictated by the SCSI layer and is not affected by this value.
- Default: 5000 (5 seconds)
+ Default: 15000 (15 seconds)
-Old Adaptec AIC7xxx chipset SCSI controller support
+Build Adapter Firmware with Kernel Build
+CONFIG_AIC7XXX_BUILD_FIRMWARE
+ This option should only be enabled if you are modifying the firmware
+ source to the aic7xxx driver and wish to have the generated firmware
+ include files updated during a normal kernel build. The assembler
+ for the firmware requires lex and yacc or their equivalents, as well
+ as the db v1 library. You may have to install additional packages
+ or modify the assembler make file or the files it includes if your
+ build environment is different than that of the author.
+
+Old Adaptec AIC7xxx support
CONFIG_SCSI_AIC7XXX_OLD
- WARNING This driver is an older aic7xxx driver and is no longer under
- active development. Adaptec, Inc. is writing a new driver to take the
- place of this one, and it is recommended that whenever possible, people
- should use the new Adaptec written driver instead of this one. This
- driver will eventually be phased out entirely.
+ WARNING This driver is an older aic7xxx driver and is no longer
+ under active development. Adaptec, Inc. is writing a new driver to
+ take the place of this one, and it is recommended that whenever
+ possible, people should use the new Adaptec written driver instead
+ of this one. This driver will eventually be phased out entirely.
This is support for the various aic7xxx based Adaptec SCSI
controllers. These include the 274x EISA cards; 284x VLB cards;
@@ -5889,47 +6843,47 @@
Information on the configuration options for this controller can be
found by checking the help file for each of the available
- configuration options. You should read drivers/scsi/aic7xxx_old/README.aic7xxx
- at a minimum before contacting the maintainer with any questions.
- The SCSI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto , can also be of great
- help.
+ configuration options. You should read
+ <file:drivers/scsi/aic7xxx_old/README.aic7xxx> at a minimum before
+ contacting the maintainer with any questions. The SCSI-HOWTO,
+ available from <http://www.linuxdoc.org/docs.html#howto>, can also
+ be of great help.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called aic7xxx_old.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called aic7xxx_old.o.
-Enable or Disable Tagged Command Queueing by default
+Enable tagged command queueing (TCQ) by default
CONFIG_AIC7XXX_OLD_TCQ_ON_BY_DEFAULT
This option causes the aic7xxx driver to attempt to use Tagged
- Command Queueing (TCQ) on all devices that claim to support it.
+ Command Queueing (TCQ) on all devices that claim to support it.
TCQ is a feature of SCSI-2 which improves performance: the host
adapter can send several SCSI commands to a device's queue even if
- previous commands haven't finished yet. Because the device is
+ previous commands haven't finished yet. Because the device is
intelligent, it can optimize its operations (like head positioning)
- based on its own request queue. Not all devices implement this
- correctly.
+ based on its own request queue. Not all devices implement this
+ correctly.
If you say Y here, you can still turn off TCQ on troublesome devices
- with the use of the tag_info boot parameter. See the file
- drivers/scsi/README.aic7xxx for more information on that and other
- aic7xxx setup commands. If this option is turned off, you may still
- enable TCQ on known good devices by use of the tag_info boot
+ with the use of the tag_info boot parameter. See the file
+ <file:drivers/scsi/README.aic7xxx> for more information on that and
+ other aic7xxx setup commands. If this option is turned off, you may
+ still enable TCQ on known good devices by use of the tag_info boot
parameter.
If you are unsure about your devices then it is safest to say N
here.
-
+
However, TCQ can increase performance on some hard drives by as much
as 50% or more, so it is recommended that if you say N here, you
- should at least read the README.aic7xxx file so you will know how to
- enable this option manually should your drives prove to be safe in
- regards to TCQ.
+ should at least read the <file:drivers/scsi/README.aic7xxx> file so
+ you will know how to enable this option manually should your drives
+ prove to be safe in regards to TCQ.
Conversely, certain drives are known to lock up or cause bus resets
- when TCQ is enabled on them. If you have a Western Digital
+ when TCQ is enabled on them. If you have a Western Digital
Enterprise SCSI drive for instance, then don't even bother to enable
TCQ on it as the drive will become unreliable, and it will actually
reduce performance.
@@ -5947,7 +6901,7 @@
eventually have their command depth reduced, but is a waste of
memory if all of your devices end up reducing this number down to a
more reasonable figure.
-
+
NOTE: Certain very broken drives are known to lock up when given
more commands than they like to deal with. Quantum Fireball drives
are the most common in this category. For the Quantum Fireball
@@ -5964,14 +6918,14 @@
small amount of overhead to each and every SCSI command the aic7xxx
driver handles, so if you aren't really interested in this
information, it is best to leave it disabled. This will only work if
- you also say Y to "/proc file system support", below.
+ you also say Y to "/proc file system support", below.
If unsure, say N.
-IBM ServeRAID Support
+IBM ServeRAID support
CONFIG_SCSI_IPS
This is support for the IBM ServeRAID hardware RAID controllers.
- See http://www.developer.ibm.com/welcome/netfinity/serveraid.html
+ See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
for more information. If this driver does not work correctly
without modification please contact the author by email at
ipslinux@us.ibm.com.
@@ -5979,14 +6933,14 @@
You can build this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
but only a single instance may be loaded. If you want to compile it
- as a module, say M here and read Documentation/modules.txt. The
- module will be called ips.o.
+ as a module, say M here and read <file:Documentation/modules.txt>.
+ The module will be called ips.o.
BusLogic SCSI support
CONFIG_SCSI_BUSLOGIC
This is support for BusLogic MultiMaster and FlashPoint SCSI Host
Adapters. Consult the SCSI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto , and the files
+ <http://www.linuxdoc.org/docs.html#howto>, and the files
README.BusLogic and README.FlashPoint in drivers/scsi for more
information. If this driver does not work correctly without
modification, please contact the author, Leonard N. Zubkoff, by
@@ -5995,8 +6949,8 @@
You can also build this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
but only a single instance may be loaded. If you want to compile it
- as a module, say M here and read Documentation/modules.txt. The
- module will be called BusLogic.o.
+ as a module, say M here and read <file:Documentation/modules.txt>.
+ The module will be called BusLogic.o.
Omit BusLogic SCSI FlashPoint support
CONFIG_SCSI_OMIT_FLASHPOINT
@@ -6005,81 +6959,86 @@
substantial, so users of MultiMaster Host Adapters may wish to omit
it.
+Compaq Fibre Channel 64-bit/66Mhz HBA support
+CONFIG_SCSI_CPQFCTS
+ Say Y here to compile in support for the Compaq StorageWorks Fibre
+ Channel 64-bit/66Mhz Host Bus Adapter.
+
DMX3191D SCSI support
CONFIG_SCSI_DMX3191D
This is support for Domex DMX3191D SCSI Host Adapters.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called dmx3191d.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ The module will be called dmx3191d.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
DTC3180/3280 SCSI support
CONFIG_SCSI_DTC3280
- This is support for DTC 3180/3280 SCSI Host Adapters. Please read
+ This is support for DTC 3180/3280 SCSI Host Adapters. Please read
the SCSI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto , and the file
- drivers/scsi/README.dtc3x80.
+ <http://www.linuxdoc.org/docs.html#howto>, and the file
+ <file:drivers/scsi/README.dtc3x80>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called dtc.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ The module will be called dtc.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti, Alphatronix) support
CONFIG_SCSI_EATA_DMA
This is support for the EATA-DMA protocol compliant SCSI Host
Adapters like the SmartCache III/IV, SmartRAID controller families
- and the DPT PM2011B and PM2012B controllers.
+ and the DPT PM2011B and PM2012B controllers.
- Note that this driver is obsolete; if you have one of the above SCSI
- Host Adapters, you should normally say N here and Y to "EATA
- ISA/EISA/PCI support", below. Please read the SCSI-HOWTO, available
- from http://www.linuxdoc.org/docs.html#howto .
+ Note that this driver is obsolete; if you have one of the above
+ SCSI Host Adapters, you should normally say N here and Y to "EATA
+ ISA/EISA/PCI support", below. Please read the SCSI-HOWTO, available
+ from <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called eata_dma.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ The module will be called eata_dma.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
EATA-PIO (old DPT PM2001, PM2012A) support
CONFIG_SCSI_EATA_PIO
This driver supports all EATA-PIO protocol compliant SCSI Host
- Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
+ Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
host adapters could also use this driver but are discouraged from
doing so, since this driver only supports hard disks and lacks
- numerous features. You might want to have a look at the SCSI-HOWTO,
- available from http://www.linuxdoc.org/docs.html#howto .
+ numerous features. You might want to have a look at the SCSI-HOWTO,
+ available from <http://www.linuxdoc.org/docs.html#howto>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called eata_pio.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called eata_pio.o.
UltraStor 14F/34F support
CONFIG_SCSI_U14_34F
This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
- The source at drivers/scsi/u14-34f.c contains some information about
- this hardware. If the driver doesn't work out of the box, you may
- have to change some settings in drivers/scsi/u14-34f.c. Read the
- SCSI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . Note that there is also
+ The source at <file:drivers/scsi/u14-34f.c> contains some
+ information about this hardware. If the driver doesn't work out of
+ the box, you may have to change some settings in
+ <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>. Note that there is also
another driver for the same hardware: "UltraStor SCSI support",
- below. You should say Y to both only if you want 24F support as
+ below. You should say Y to both only if you want 24F support as
well.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called u14-34f.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ The module will be called u14-34f.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
enable elevator sorting
CONFIG_SCSI_U14_34F_LINKED_COMMANDS
- This option enables elevator sorting for all probed SCSI disks and
- CDROMs. It definitely reduces the average seek distance when doing
+ This option enables elevator sorting for all probed SCSI disks and
+ CD-ROMs. It definitely reduces the average seek distance when doing
random seeks, but this does not necessarily result in a noticeable
performance improvement: your mileage may vary...
-
+
The safe answer is N.
maximum number of queued commands
@@ -6098,7 +7057,7 @@
other adapters based on the Future Domain chipsets (Quantum
ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
It is explained in section 3.7 of the SCSI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
@@ -6108,7 +7067,7 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called fdomain.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
Future Domain MCS-600/700 SCSI support
CONFIG_SCSI_FD_MCS
@@ -6121,71 +7080,90 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called fd_mcs.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
Generic NCR5380/53c400 SCSI support
CONFIG_SCSI_GENERIC_NCR5380
This is the generic NCR family of SCSI controllers, not to be
- confused with the NCR 53c7 or 8xx controllers. It is explained in
+ confused with the NCR 53c7 or 8xx controllers. It is explained in
section 3.8 of the SCSI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
+ <http://www.linuxdoc.org/docs.html#howto>. If it doesn't work out
of the box, you may have to change some settings in
- drivers/scsi/g_NCR5380.h.
+ <file:drivers/scsi/g_NCR5380.h>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called g_NCR5380.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
+ The module will be called g_NCR5380.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
Enable NCR53c400 extensions
CONFIG_SCSI_GENERIC_NCR53C400
- This enables certain optimizations for the NCR53c400 SCSI cards. You
- might as well try it out. Note that this driver will only probe for
- the Trantor T130B in its default configuration; you might have to
- pass a command line option to the kernel at boot time if it doesn't
- detect your card. See the file drivers/scsi/README.g_NCR5380 for
- details.
+ This enables certain optimizations for the NCR53c400 SCSI cards.
+ You might as well try it out. Note that this driver will only probe
+ for the Trantor T130B in its default configuration; you might have
+ to pass a command line option to the kernel at boot time if it does
+ not detect your card. See the file
+ <file:drivers/scsi/README.g_NCR5380> for details.
+# Choice: ncr5380
NCR5380/53c400 mapping method (use Port for T130B)
CONFIG_SCSI_G_NCR5380_PORT
The NCR5380 and NCR53c400 SCSI controllers come in two varieties:
port or memory mapped. You should know what you have. The most
common card, Trantor T130B, uses port mapped mode.
+NCR Dual 700 MCA SCSI support
+CONFIG_SCSI_NCR_D700
+ This is a driver for the MicroChannel Dual 700 card produced by
+ NCR and commonly used in 345x/35xx/4100 class machines. It always
+ tries to negotiate sync and uses tag command queueing.
+
+ Unless you have an NCR manufactured machine, the chances are that
+ you do not have this SCSI card, so say N.
+
+HP LASI SCSI support for 53c700
+CONFIG_SCSI_LASI700
+ This is a driver for the lasi baseboard in some parisc machines
+ which is based on the 53c700 chip. Will also support LASI subsystems
+ based on the 710 chip using 700 emulation mode.
+
+ Unless you know you have a 53c700 or 53c710 based lasi, say N here
+
NCR53c7,8xx SCSI support
CONFIG_SCSI_NCR53C7xx
This is a driver for the 53c7 and 8xx NCR family of SCSI
- controllers, not to be confused with the NCR 5380 controllers. It is
- explained in section 3.8 of the SCSI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
+ controllers, not to be confused with the NCR 5380 controllers. It
+ is explained in section 3.8 of the SCSI-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>. If it doesn't work out
of the box, you may have to change some settings in
- drivers/scsi/53c7,8xx.h. Please read drivers/scsi/README.ncr53c7xx
- for the available boot time command line options.
+ <file:drivers/scsi/53c7,8xx.h>. Please read
+ <file:drivers/scsi/README.ncr53c7xx> for the available boot time
+ command line options.
Note: there is another driver for the 53c8xx family of controllers
- ("NCR53C8XX SCSI support" below). If you want to use them both, you
+ ("NCR53C8XX SCSI support" below). If you want to use them both, you
need to say M to both and build them as modules, but only one may be
active at a time. If you have a 53c8xx board, it's better to use the
other driver.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called 53c7,8xx.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ The module will be called 53c7,8xx.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
-always negotiate synchronous transfers
+Always negotiate synchronous transfers
CONFIG_SCSI_NCR53C7xx_sync
In general, this is good; however, it is a bit dangerous since there
are some broken SCSI devices out there. Take your chances. Safe bet
is N.
-allow FAST-SCSI [10MHz]
+Allow FAST-SCSI [10MHz]
CONFIG_SCSI_NCR53C7xx_FAST
This will enable 10MHz FAST-SCSI transfers with your host
adapter. Some systems have problems with that speed, so it's safest
to say N here.
-allow DISCONNECT
+Allow DISCONNECT
CONFIG_SCSI_NCR53C7xx_DISCONNECT
This enables the disconnect/reconnect feature of the NCR SCSI
controller. When you say Y here, a slow SCSI device will not lock
@@ -6197,10 +7175,67 @@
to hang, which might cause a system crash. The safe answer
therefore is to say N.
+SYM53C8XX Version 2 SCSI support
+CONFIG_SCSI_SYM53C8XX_2
+ This driver supports the whole NCR53C8XX/SYM53C8XX family of
+ PCI-SCSI controllers. It also supports the subset of LSI53C10XX
+ Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
+ language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
+ controllers.
+
+ If your system has problems using this new major version of the
+ SYM53C8XX driver, you may switch back to driver version 1.
+
+ Please read drivers/scsi/sym53c8xx_2/Documentation.txt for more
+ information.
+
+PCI DMA addressing mode
+CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
+ This option only applies to PCI-SCSI chip that are PCI DAC capable
+ (875A, 895A, 896, 1010-33, 1010-66, 1000).
+
+ When set to 0, only PCI 32 bit DMA addressing (SAC) will be performed.
+ When set to 1, 40 bit DMA addressing (with upper 24 bits of address
+ set to zero) is supported. The addressable range is here 1 TB.
+ When set to 2, full 64 bits of address for DMA are supported, but only
+ 16 segments of 4 GB can be addressed. The addressable range is so
+ limited to 64 GB.
+
+ The safest value is 0 (32 bit DMA addressing) that is guessed to still
+ fit most of real machines.
+
+ The preferred value 1 (40 bit DMA addressing) should make happy
+ properly engineered PCI DAC capable host bridges. You may configure
+ this option for Intel platforms with more than 4 GB of memory.
+
+ The still experimental value 2 (64 bit DMA addressing with 16 x 4GB
+ segments limitation) can be used on systems that require PCI address
+ bits past bit 39 to be set for the addressing of memory using PCI
+ DAC cycles.
+
+use normal IO
+CONFIG_SCSI_SYM53C8XX_IOMAPPED
+ If you say Y here, the driver will preferently use normal IO rather than
+ memory mapped IO.
+
+maximum number of queued commands
+CONFIG_SCSI_SYM53C8XX_MAX_TAGS
+ This option allows you to specify the maximum number of commands
+ that can be queued to any device, when tagged command queuing is
+ possible. The driver supports up to 256 queued commands per device.
+ This value is used as a compiled-in hard limit.
+
+default tagged command queue depth
+CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS
+ This is the default value of the command queue depth the driver will
+ announce to the generic SCSI layer for devices that support tagged
+ command queueing. This value can be changed from the boot command line.
+ This is a soft limit that cannot exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
+
NCR53C8XX SCSI support
CONFIG_SCSI_NCR53C8XX
This is the BSD ncr driver adapted to Linux for the NCR53C8XX family
- of PCI-SCSI controllers. This driver supports parity checking,
+ of PCI-SCSI controllers. This driver supports parity checking,
tagged command queuing and fast synchronous data transfers up to 80
MB/s with wide FAST-40 LVD devices and controllers.
@@ -6208,21 +7243,22 @@
option "SYM53C8XX SCSI support", below.
Note: there is yet another driver for the 53c8xx family of
- controllers ("NCR53c7,8xx SCSI support" above). If you want to use
+ controllers ("NCR53c7,8xx SCSI support" above). If you want to use
them both, you need to say M to both and build them as modules, but
- only one may be active at a time. If you have a 53c8xx board, you
+ only one may be active at a time. If you have a 53c8xx board, you
probably do not want to use the "NCR53c7,8xx SCSI support".
- Please read drivers/scsi/README.ncr53c8xx for more information.
+ Please read <file:drivers/scsi/README.ncr53c8xx> for more
+ information.
-SYM53C8XX SCSI support
+SYM53C8XX Version 1 SCSI support
CONFIG_SCSI_SYM53C8XX
This driver supports all the features of recent 53C8XX chips (used
in PCI SCSI controllers), notably the hardware phase mismatch
feature of the SYM53C896.
Older versions of the 53C8XX chips are not supported by this
- driver. If your system uses either a 810 rev. < 16, a 815, or a 825
+ driver. If your system uses either a 810 rev. < 16, a 815, or a 825
rev. < 16 PCI SCSI processor, you must use the generic NCR53C8XX
driver ("NCR53C8XX SCSI support" above) or configure both the
NCR53C8XX and this SYM53C8XX drivers either as module or linked to
@@ -6231,32 +7267,33 @@
When both drivers are linked into the kernel, the SYM53C8XX driver
is called first at initialization and you can use the 'excl=ioaddr'
driver boot option to exclude attachment of adapters by the
- SYM53C8XX driver. For example, entering
+ SYM53C8XX driver. For example, entering
'sym53c8xx=excl:0xb400,excl=0xc000' at the lilo prompt prevents
adapters at io address 0xb400 and 0xc000 from being attached by the
SYM53C8XX driver, thus allowing the NCR53C8XX driver to attach them.
The 'excl' option is also supported by the NCR53C8XX driver.
-
- Please read drivers/scsi/README.ncr53c8xx for more information.
-synchronous data transfers frequency
+ Please read <file:drivers/scsi/README.ncr53c8xx> for more
+ information.
+
+Synchronous transfer frequency in MHz
CONFIG_SCSI_NCR53C8XX_SYNC
The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
- rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers are
- respectively the maximum data transfer rates in mega-transfers per
- second for each class. For example, a FAST-20 Wide 16 device is able
- to transfer data at 20 million 16 bit packets per second for a total
- rate of 40 MB/s.
+ rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
+ are respectively the maximum data transfer rates in mega-transfers
+ per second for each class. For example, a FAST-20 Wide 16 device is
+ able to transfer data at 20 million 16 bit packets per second for a
+ total rate of 40 MB/s.
You may specify 0 if you want to only use asynchronous data
transfers. This is the safest and slowest option. Otherwise, specify
a value between 5 and 80, depending on the capability of your SCSI
- controller. The higher the number, the faster the data transfer.
+ controller. The higher the number, the faster the data transfer.
Note that 80 should normally be ok since the driver decreases the
value automatically according to the controller's capabilities.
Your answer to this question is ignored for controllers with NVRAM,
- since the driver will get this information from the user set-up. It
+ since the driver will get this information from the user set-up. It
also can be overridden using a boot setup option, as follows
(example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
for FAST-20 synchronous data transfer (20 mega-transfers per
@@ -6270,18 +7307,18 @@
There is no safe option other than using good cabling, right
terminations and SCSI conformant devices.
-use normal IO
+Use normal IO
CONFIG_SCSI_NCR53C8XX_IOMAPPED
If you say Y here, the driver will use normal IO, as opposed to
memory mapped IO. Memory mapped IO has less latency than normal IO
and works for most Intel-based hardware. Under Linux/Alpha only
normal IO is currently supported by the driver and so, this option
- has no effect on those systems.
+ has no effect on those systems.
The normal answer therefore is N; try Y only if you encounter SCSI
related problems.
-not allow targets to disconnect
+Not allow targets to disconnect
CONFIG_SCSI_NCR53C8XX_NO_DISCONNECT
This option is only provided for safety if you suspect some SCSI
device of yours to not support properly the target-disconnect
@@ -6289,7 +7326,7 @@
not allow targets to disconnect is not reasonable if there is more
than 1 device on a SCSI bus. The normal answer therefore is N.
-default tagged command queue depth
+Default tagged command queue depth
CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS
"Tagged command queuing" is a feature of SCSI-2 which improves
performance: the host adapter can send several SCSI commands to a
@@ -6300,33 +7337,33 @@
feature, enter 0 or 1 here (it doesn't matter which).
The default value is 8 and should be supported by most hard disks.
- This value can be overridden from the boot command line using the
+ This value can be overridden from the boot command line using the
'tags' option as follows (example):
'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
4, set queue depth to 16 for target 2 and target 3 on controller 0
and set queue depth to 10 for target 0 / lun 2 on controller 1.
- The normal answer therefore is to go with the default 8 and to use
- a boot command line option for devices that need to use a different
+ The normal answer therefore is to go with the default 8 and to use
+ a boot command line option for devices that need to use a different
command queue depth.
There is no safe option other than using good SCSI devices.
-maximum number of queued commands
+Maximum number of queued commands
CONFIG_SCSI_NCR53C8XX_MAX_TAGS
This option allows you to specify the maximum number of commands
that can be queued to any device, when tagged command queuing is
possible. The default value is 32. Minimum is 2, maximum is 64.
- Modern hard disks are able to support 64 tags and even more, but
+ Modern hard disks are able to support 64 tags and even more, but
do not seem to be faster when more than 32 tags are being used.
-
+
So, the normal answer here is to go with the default value 32 unless
you are using very large hard disks with large cache (>= 1 MB) that
are able to take advantage of more than 32 tagged commands.
There is no safe option and the default answer is recommended.
-assume boards are SYMBIOS compatible (EXPERIMENTAL)
+Assume boards are SYMBIOS compatible
CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT
This option allows you to enable some features depending on GPIO
wiring. These General Purpose Input/Output pins can be used for
@@ -6335,7 +7372,7 @@
controller LED and GPIO3 bit as a flag indicating
singled-ended/differential interface. The Tekram DC-390U/F boards
uses a different GPIO wiring.
-
+
Your answer to this question is ignored if all your controllers have
NVRAM, since the driver is able to detect the board type from the
NVRAM format.
@@ -6344,16 +7381,16 @@
use BIOS and drivers from SYMBIOS, you would want to say Y here,
otherwise N. N is the safe answer.
-enable profiling statistics gathering
+Enable traffic profiling
CONFIG_SCSI_NCR53C8XX_PROFILE
This option allows you to enable profiling information gathering.
- These statistics are not very accurate due to the low frequency
- of the kernel clock (100 Hz on i386) and have performance impact
+ These statistics are not very accurate due to the low frequency
+ of the kernel clock (100 Hz on i386) and have performance impact
on systems that use very fast devices.
The normal answer therefore is N.
-include support for the NCR PQS/PDS SCSI card
+Include support for the NCR PQS/PDS SCSI card
CONFIG_SCSI_NCR53C8XX_PQS_PDS
Say Y here if you have a special SCSI adapter produced by NCR
corporation called a PCI Quad SCSI or PCI Dual SCSI. You do not need
@@ -6366,23 +7403,24 @@
IBMMCA SCSI support
CONFIG_SCSI_IBMMCA
This is support for the IBM SCSI adapter found in many of the PS/2
- series computers. These machines have an MCA bus, so you need to
- answer Y to "MCA support" as well and read Documentation/mca.txt.
+ series computers. These machines have an MCA bus, so you need to
+ answer Y to "MCA support" as well and read
+ <file:Documentation/mca.txt>.
If the adapter isn't found during boot (a common problem for models
56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
option, where <pun> is the id of the SCSI subsystem (usually 7, but
- if that doesn't work check your reference diskette). Owners of model
- 95 with a LED-matrix-display can in addition activate some activity
- info like under OS/2, but more informative, by setting
- 'ibmmcascsi=display' as an additional kernel parameter. Try "man
+ if that doesn't work check your reference diskette). Owners of
+ model 95 with a LED-matrix-display can in addition activate some
+ activity info like under OS/2, but more informative, by setting
+ 'ibmmcascsi=display' as an additional kernel parameter. Try "man
bootparam" or see the documentation of your boot loader about how to
pass options to the kernel.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called ibmmca.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called ibmmca.o.
Standard SCSI-order
CONFIG_IBMMCA_SCSI_ORDER_STANDARD
@@ -6399,7 +7437,7 @@
highest priority. This must therefore be the disk with the highest
SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
original definition of the SCSI-standard as also industrial- and
- process-control-machines, like VME-CPUs running under realtime-OSs
+ process-control-machines, like VME-CPUs running under realtime-OSes
(e.g. LynxOS, OS9) do.
If you like to run Linux on your MCA-machine with the same
@@ -6428,96 +7466,96 @@
you know that one of your older devices needs it; N is the safe
answer.
-NCR 53C9x MCA support
+NCR MCA 53C9x SCSI support
CONFIG_SCSI_MCA_53C9X
- Some Microchannel machines, notably the NCR 35xx line, use a SCSI
+ Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
controller based on the NCR 53C94. This driver will allow use of
- the controller on the 3550, and very possibly others.
+ the controller on the 3550, and very possibly others.
If you want to compile this as a module (= code which can be
inserted and removed from the running kernel whenever you want), say
- M here and read Documentation/modules.txt. The module will be called
- mca_53c9x.o.
-
+ M here and read <file:Documentation/modules.txt>. The module will
+ be called mca_53c9x.o.
+
Always IN2000 SCSI support
CONFIG_SCSI_IN2000
- This is support for an ISA bus SCSI host adapter. You'll find more
- information in drivers/scsi/in2000.readme. If it doesn't work out of
- the box, you may have to change the jumpers for IRQ or address
- selection.
+ This is support for an ISA bus SCSI host adapter. You'll find more
+ information in <file:drivers/scsi/README.in2000>. If it doesn't work
+ out of the box, you may have to change the jumpers for IRQ or
+ address selection.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called in2000.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called in2000.o.
Initio 91XXU(W) SCSI support
CONFIG_SCSI_INITIO
- This is support for the Initio 91XXU(W) SCSI host adapter. Please
+ This is support for the Initio 91XXU(W) SCSI host adapter. Please
read the SCSI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called initio.o
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called initio.o.
PAS16 SCSI support
CONFIG_SCSI_PAS16
- This is support for a SCSI host adapter. It is explained in section
+ This is support for a SCSI host adapter. It is explained in section
3.10 of the SCSI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
+ <http://www.linuxdoc.org/docs.html#howto>. If it doesn't work out
of the box, you may have to change some settings in
- drivers/scsi/pas16.h.
-
+ <file:drivers/scsi/pas16.h>.
+
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called pas16.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ The module will be called pas16.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
Initio INI-A100U2W SCSI support
CONFIG_SCSI_INIA100
- This is support for the Initio INI-A100U2W SCSI host adapter. Please
- read the SCSI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ This is support for the Initio INI-A100U2W SCSI host adapter.
+ Please read the SCSI-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
- If you want to compile this as a module ( = code which can be
+ If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called a100u2w.o
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called a100u2w.o.
PCI2000 support
CONFIG_SCSI_PCI2000
This is support for the PCI2000I EIDE interface card which acts as a
- SCSI host adapter. Please read the SCSI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ SCSI host adapter. Please read the SCSI-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module called pci2000.o ( = code
which can be inserted in and removed from the running kernel
- whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
PCI2220i support
CONFIG_SCSI_PCI2220I
This is support for the PCI2220i EIDE interface card which acts as a
- SCSI host adapter. Please read the SCSI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ SCSI host adapter. Please read the SCSI-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module called pci2220i.o ( = code
which can be inserted in and removed from the running kernel
- whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
PSI240i support
CONFIG_SCSI_PSI240I
This is support for the PSI240i EIDE interface card which acts as a
- SCSI host adapter. Please read the SCSI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ SCSI host adapter. Please read the SCSI-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module called psi240i.o ( = code
which can be inserted in and removed from the running kernel
- whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
Qlogic FAS SCSI support
CONFIG_SCSI_QLOGIC_FAS
@@ -6530,31 +7568,32 @@
SCSI support"), below.
Information about this driver is contained in
- drivers/scsi/README.qlogicfas. You should also read the SCSI-HOWTO,
- available from http://www.linuxdoc.org/docs.html#howto .
+ <file:drivers/scsi/README.qlogicfas>. You should also read the
+ SCSI-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called qlogicfas.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
+ a module, say M here and read <file:Documentation/modules.txt>.
-Qlogic ISP SCSI support (EXPERIMENTAL)
+Qlogic ISP SCSI support
CONFIG_SCSI_QLOGIC_ISP
This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
- IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
- card is supported by the "AM53/79C974 PCI SCSI" driver).
+ IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
+ card is supported by the "AM53/79C974 PCI SCSI" driver.)
If you say Y here, make sure to choose "BIOS" at the question "PCI
access mode".
- Please read the file drivers/scsi/README.qlogicisp. You should also
- read the SCSI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ Please read the file <file:drivers/scsi/README.qlogicisp>. You
+ should also read the SCSI-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called qlogicisp.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
+ The module will be called qlogicisp.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
Qlogic ISP FC SCSI support
CONFIG_SCSI_QLOGIC_FC
@@ -6562,8 +7601,8 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called qlogicfc.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
+ The module will be called qlogicfc.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
Qlogic QLA 1280 SCSI support
CONFIG_SCSI_QLOGIC_1280
@@ -6572,61 +7611,63 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called qla1280.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
+ a module, say M here and read <file:Documentation/modules.txt>.
Seagate ST-02 and Future Domain TMC-8xx SCSI support
CONFIG_SCSI_SEAGATE
These are 8-bit SCSI controllers; the ST-01 is also supported by
- this driver. It is explained in section 3.9 of the SCSI-HOWTO,
- available from http://www.linuxdoc.org/docs.html#howto . If it
+ this driver. It is explained in section 3.9 of the SCSI-HOWTO,
+ available from <http://www.linuxdoc.org/docs.html#howto>. If it
doesn't work out of the box, you may have to change some settings in
- drivers/scsi/seagate.h.
+ <file:drivers/scsi/seagate.h>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called seagate.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ The module will be called seagate.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
Trantor T128/T128F/T228 SCSI support
CONFIG_SCSI_T128
This is support for a SCSI host adapter. It is explained in section
3.11 of the SCSI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
+ <http://www.linuxdoc.org/docs.html#howto>. If it doesn't work out
of the box, you may have to change some settings in
- drivers/scsi/t128.h. Note that Trantor was purchased by Adaptec, and
- some former Trantor products are being sold under the Adaptec name.
+ <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
+ Adaptec, and some former Trantor products are being sold under the
+ Adaptec name.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called t128.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ The module will be called t128.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
UltraStor SCSI support
CONFIG_SCSI_ULTRASTOR
This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
- adapter family. This driver is explained in section 3.12 of the
+ adapter family. This driver is explained in section 3.12 of the
SCSI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
+ <http://www.linuxdoc.org/docs.html#howto>. If it doesn't work out
of the box, you may have to change some settings in
- drivers/scsi/ultrastor.h.
-
+ <file:drivers/scsi/ultrastor.h>.
+
Note that there is also another driver for the same hardware:
"UltraStor 14F/34F support", above.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called ultrastor.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called ultrastor.o.
7000FASST SCSI support
CONFIG_SCSI_7000FASST
This driver supports the Western Digital 7000 SCSI host adapter
- family. Some information is in the source: drivers/scsi/wd7000.c.
+ family. Some information is in the source:
+ <file:drivers/scsi/wd7000.c>.
This driver is also available as a module ( = code which can be
- inserted in and removed from the running kernel whenever you
- want). The module will be called wd7000.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt.
+ inserted in and removed from the running kernel whenever you want).
+ The module will be called wd7000.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
ACARD SCSI support
CONFIG_SCSI_ACARD
@@ -6635,40 +7676,41 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called atp870u.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support
CONFIG_SCSI_EATA
- This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
- ISA and all EISA i/o addresses are probed looking for the "EATA"
- signature. If you chose "BIOS" at the question "PCI access mode",
+ This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
+ ISA and all EISA I/O addresses are probed looking for the "EATA"
+ signature. If you chose "BIOS" at the question "PCI access mode",
the addresses of all the PCI SCSI controllers reported by the PCI
subsystem are probed as well.
- You want to read the start of drivers/scsi/eata.c and the
+ You want to read the start of <file:drivers/scsi/eata.c> and the
SCSI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
Note that there is also another driver for the same hardware
- available: "EATA-DMA support". You should say Y to only one of them.
+ available: "EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti,
+ Alphatronix) support". You should say Y to only one of them.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called eata.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called eata.o.
-enable tagged command queuing
+enable tagged command queueing
CONFIG_SCSI_EATA_TAGGED_QUEUE
This is a feature of SCSI-2 which improves performance: the host
adapter can send several SCSI commands to a device's queue even if
previous commands haven't finished yet. Most EATA adapters negotiate
this feature automatically with the device, even if your answer is
N. The safe answer is N.
-
+
enable elevator sorting
CONFIG_SCSI_EATA_LINKED_COMMANDS
- This option enables elevator sorting for all probed SCSI disks and
- CDROMs. It definitely reduces the average seek distance when doing
+ This option enables elevator sorting for all probed SCSI disks and
+ CD-ROMs. It definitely reduces the average seek distance when doing
random seeks, but this does not necessarily result in a noticeable
performance improvement: your mileage may vary...
The safe answer is N.
@@ -6684,21 +7726,21 @@
NCR53c406a SCSI support
CONFIG_SCSI_NCR53C406A
- This is support for the NCR53c406a SCSI host adapter. For user
- configurable parameters, check out drivers/scsi/NCR53c406.c in the
- kernel source. Also read the SCSI-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ This is support for the NCR53c406a SCSI host adapter. For user
+ configurable parameters, check out <file:drivers/scsi/NCR53c406.c>
+ in the kernel source. Also read the SCSI-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called NCR53c406.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called NCR53c406.o.
-Symbios Logic sym53c416 support
+Symbios 53c416 SCSI support
CONFIG_SCSI_SYM53C416
This is support for the sym53c416 SCSI host adapter, the SCSI
adapter that comes with some HP scanners. This driver requires that
- the sym53c416 is configured first using some sort of pnp
+ the sym53c416 is configured first using some sort of PnP
configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
are using isapnp then you need to compile this driver as a module
and then load it using insmod after isapnp has run. The parameters
@@ -6710,8 +7752,8 @@
There is support for up to four adapters. If you want to compile
this driver as a module ( = code which can be inserted in and
removed from the running kernel whenever you want), say M here and
- read Documentation/modules.txt. The module will be called
- sym53c416.o.
+ read <file:Documentation/modules.txt>. The module will be called
+ sym53c416.o.
Simple 53c710 SCSI support (Compaq, NCR machines)
CONFIG_SCSI_SIM710
@@ -6720,46 +7762,46 @@
More complex drivers for this chip are available ("NCR53c7,8xx SCSI
support", above), but they require that the scsi chip be able to do
DMA block moves between memory and on-chip registers, which can
- cause problems under certain conditions. This driver is designed to
+ cause problems under certain conditions. This driver is designed to
avoid these problems and is intended to work with any Intel machines
using 53c710 chips, including various Compaq and NCR machines.
Please read the comments at the top of the file
- drivers/scsi/sim710.c for more information.
+ <file:drivers/scsi/sim710.c> for more information.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called sim710.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called sim710.o.
-Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support
+Tekram DC390(T) and Am53/79C974 SCSI support
CONFIG_SCSI_DC390T
This driver supports PCI SCSI host adapters based on the Am53C974A
chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
PCscsi/PCnet (Am53/79C974) solutions.
- Documentation can be found in drivers/scsi/README.tmscsim.
-
+ Documentation can be found in <file:drivers/scsi/README.tmscsim>.
+
Note that this driver does NOT support Tekram DC390W/U/F, which are
based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
Also note that there is another generic Am53C974 driver,
- "AM53/79C974 PCI SCSI support" below. You can pick either one.
+ "AM53/79C974 PCI SCSI support" below. You can pick either one.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called tmscsim.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called tmscsim.o.
Omit support for other Am53/79C974 based SCSI adapters
CONFIG_SCSI_DC390T_NOGENSUPP
If you say N here, the DC390(T) SCSI driver relies on the DC390
EEPROM to get initial values for its settings, such as speed,
- termination, etc. If it can't find this EEPROM, it will use defaults
- or the user supplied boot/module parameters. For details on driver
- configuration see drivers/scsi/README.tmscsim.
+ termination, etc. If it can't find this EEPROM, it will use
+ defaults or the user supplied boot/module parameters. For details
+ on driver configuration see <file:drivers/scsi/README.tmscsim>.
If you say Y here and if no EEPROM is found, the driver gives up and
- thus only supports Tekram DC390(T) adapters. This can be useful if
+ thus only supports Tekram DC390(T) adapters. This can be useful if
you have a DC390(T) and another Am53C974 based adapter, which, for
some reason, you want to drive with the other AM53C974 driver.
@@ -6767,40 +7809,42 @@
AM53/79C974 PCI SCSI support
CONFIG_SCSI_AM53C974
- This is support for the AM53/79C974 SCSI host adapters. Please read
- drivers/scsi/README.AM53C974 for details. Also, the SCSI-HOWTO,
- available from http://www.linuxdoc.org/docs.html#howto , is for
- you.
+ This is support for the AM53/79C974 SCSI host adapters. Please read
+ <file:drivers/scsi/README.AM53C974> for details. Also, the
+ SCSI-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>, is for you.
Note that there is another driver for AM53C974 based adapters:
- "Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support", above. You
+ "Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support", above. You
can pick either one.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called AM53C974.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called AM53C974.o.
AMI MegaRAID support
CONFIG_SCSI_MEGARAID
This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490
- and 467 SCSI host adapters.
+ and 467 SCSI host adapters.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called megaraid.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called megaraid.o.
-GDT SCSI Disk Array Controller support
+Intel/ICP (former GDT SCSI Disk Array) RAID Controller Support
CONFIG_SCSI_GDTH
- This is a driver for all SCSI Disk Array Controllers (EISA/ISA/PCI)
- manufactured by ICP vortex. It is documented in the kernel source in
- drivers/scsi/gdth.c and drivers/scsi/gdth.h.
+ Formerly called GDT SCSI Disk Array Controller Support.
+
+ This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
+ manufactured by Intel/ICP vortex (an Intel Company). It is documented
+ in the kernel source in drivers/scsi/gdth.c and drivers/scsi/gdth.h.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
If you want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ <file:Documentation/modules.txt>.
IOMEGA parallel port (ppa - older drives)
CONFIG_SCSI_PPA
@@ -6817,17 +7861,17 @@
newer drives)", below.
For more information about this driver and how to use it you should
- read the file drivers/scsi/README.ppa. You should also read the
- SCSI-HOWTO, which is available from
- http://www.linuxdoc.org/docs.html#howto . If you use this driver,
+ read the file <file:drivers/scsi/README.ppa>. You should also read
+ the SCSI-HOWTO, which is available from
+ <http://www.linuxdoc.org/docs.html#howto>. If you use this driver,
you will still be able to use the parallel port for other tasks,
such as a printer; it is safe to compile both drivers into the
kernel.
This driver is also available as a module which can be inserted in
- and removed from the running kernel whenever you want. To compile
+ and removed from the running kernel whenever you want. To compile
this driver as a module, say M here and read
- Documentation/modules.txt. The module will be called ppa.o.
+ <file:Documentation/modules.txt>. The module will be called ppa.o.
IOMEGA parallel port (imm - newer drives)
CONFIG_SCSI_IMM
@@ -6844,17 +7888,17 @@
here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
For more information about this driver and how to use it you should
- read the file drivers/scsi/README.ppa. You should also read the
- SCSI-HOWTO, which is available from
- http://www.linuxdoc.org/docs.html#howto . If you use this driver,
+ read the file <file:drivers/scsi/README.ppa>. You should also read
+ the SCSI-HOWTO, which is available from
+ <http://www.linuxdoc.org/docs.html#howto>. If you use this driver,
you will still be able to use the parallel port for other tasks,
such as a printer; it is safe to compile both drivers into the
kernel.
This driver is also available as a module which can be inserted in
- and removed from the running kernel whenever you want. To compile
+ and removed from the running kernel whenever you want. To compile
this driver as a module, say M here and read
- Documentation/modules.txt. The module will be called imm.o.
+ <file:Documentation/modules.txt>. The module will be called imm.o.
Force the Iomega ZIP drivers to use EPP-16
CONFIG_SCSI_IZIP_EPP16
@@ -6866,7 +7910,7 @@
so we have to control the state of the chipset's FIFO queue every
now and then to avoid data loss. This will be done if you say Y
here.
-
+
Generally, saying Y is the safe option and slows things down a bit.
Assume slow parallel port control register
@@ -6881,67 +7925,7 @@
Generally, saying N is fine.
-Parallel port SCSI device support
-CONFIG_PPSCSI
- There are many external CD-ROM and disk devices that connect through
- your computer's parallel port. Lots of them are actually SCSI
- devices using a parallel port SCSI adapter. This option enables the
- ppSCSI subsystem which contains drivers for many of these external
- drives. You may also want to look at CONFIG_PARIDE (Parallel port
- IDE device support).
-
- If you built ppSCSI support into your kernel, you may still build
- the individual protocol modules and high-level drivers as loadable
- modules. If you build this support as a module, it will be called
- ppscsi.o.
-
- To use the ppSCSI support, you must say Y or M here and also to at
- least one protocol driver (e.g. "Shuttle EPST adapter", "Iomega VPI0
- adapter", "Shining ScarSCI adapter" etc.).
-
-Adaptec APA-348 adapter
-CONFIG_PPSCSI_T348
- This option enables support for the APA-348 adapter from Adaptec
- (also known as Trantor T348). If you build this as a module it will
- be called t348.o.
-
-Adaptec APA-358 adapter
-CONFIG_PPSCSI_T358
- This option enables support for the APA-358 adapter from Adaptec
- (also known as Trantor T358). If you build this as a module it will
- be called t358.o.
-
-Iomega VPI0 adapter
-CONFIG_PPSCSI_VPI0
- This option enables support for the Iomega VPI0 adapter found in the
- original ZIP-100 drives and the Jaz Traveller. If you build this as
- a module it will be called vpi0.o.
-
-OnSpec 90c26 adapter
-CONFIG_PPSCSI_ONSCSI
- This option enables support for the OnSpec 90c26 in its SCSI adapter
- mode. If you build this as a module it will be called onscsi.o.
-
-Shining SparSCI adapter
-CONFIG_PPSCSI_SPARCSI
- This option enables support for the WBS-11A parallel port SCSI
- adapter. This adapter has been marketed by LinkSys as the
- "ParaSCSI+" and by Shining Technologies as the "SparCSI". If you
- build this as a module it will be called sparcsi.o.
-
-Shuttle EPSA-2 adapter
-CONFIG_PPSCSI_EPSA2
- This option enables support for the Shuttle Technologies EPSA2
- parallel port SCSI adapter. EPAS2 is a predecessor to the EPST. If
- you build this as a module it will be called epsa2.o.
-
-Shuttle EPST adapter
-CONFIG_PPSCSI_EPST
- This option enables support for the Shuttle Technologies EPST
- parallel port SCSI adapter. If you build this as a module is will
- be called epst.o.
-
-SCSI Debug host simulator. (EXPERIMENTAL)
+SCSI debugging host simulator
CONFIG_SCSI_DEBUG
This is a host adapter simulator that can be programmed to simulate
a large number of conditions that could occur on a real bus. The
@@ -6950,7 +7934,7 @@
important data. This is primarily of use to people trying to debug
the middle and upper layers of the SCSI subsystem. If unsure, say N.
-Fibre Channel support and FC4 SCSI support
+Fibre Channel and FC4 SCSI support
CONFIG_FC4
Fibre Channel is a high speed serial protocol mainly used to
connect large storage devices to the computer; it is compatible with
@@ -6966,7 +7950,7 @@
If unsure, say N.
-Sun SOC
+Sun SOC/Sbus
CONFIG_FC4_SOC
Serial Optical Channel is an interface card with one or two Fibre
Optic ports, each of which can be connected to a disk array. Note
@@ -6976,7 +7960,7 @@
This support is also available as a module called soc.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
Sun SOC+ (aka SOCAL)
CONFIG_FC4_SOCAL
@@ -6989,16 +7973,16 @@
This support is also available as a module called socal.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
SparcSTORAGE Array 100 and 200 series
CONFIG_SCSI_PLUTO
- If you never bought a disk array made by Sun, go with N.
+ If you never bought a disk array made by Sun, go with N.
This support is also available as a module called pluto.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
Sun Enterprise Network Array (A5000 and EX500)
CONFIG_SCSI_FCAL
@@ -7010,14 +7994,14 @@
This support is also available as a module called fcal.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt. If unsure, say N.
+ here and read <file:Documentation/modules.txt>. If unsure, say N.
-AcornSCSI support
+Acorn SCSI card (aka30) support
CONFIG_SCSI_ACORNSCSI_3
This enables support for the Acorn SCSI card (aka30). If you have an
Acorn system with one of these, say Y. If unsure, say N.
-Acorn SCSI tagged queue support
+Support SCSI 2 Tagged queueing
CONFIG_SCSI_ACORNSCSI_TAGGED_QUEUE
Say Y here to enable tagged queuing support on the Acorn SCSI card.
@@ -7026,7 +8010,7 @@
previous commands haven't finished yet. Some SCSI devices don't
implement this properly, so the safe answer is N.
-Acorn SCSI Synchronous transfers support
+Support SCSI 2 Synchronous Transfers
CONFIG_SCSI_ACORNSCSI_SYNC
Say Y here to enable synchronous transfer negotiation with all
targets on the Acorn SCSI card.
@@ -7034,6 +8018,16 @@
In general, this improves performance; however some SCSI devices
don't implement it properly, so the safe answer is N.
+ARXE SCSI support
+CONFIG_SCSI_ARXESCSI
+ Around 1991, Arxe Systems Limited released a high density floppy
+ disc interface for the Acorn Archimedes range, to allow the use of
+ HD discs from the then new A5000 on earlier models. This interface
+ was either sold on its own or with an integral SCSI controller.
+ Technical details on this NCR53c94-based device are available at
+ <http://www.cryton.demon.co.uk/acornbits/scsi_arxe.html>
+ Say Y here to compile in support for the SCSI controller.
+
Oak SCSI support
CONFIG_SCSI_OAK1
This enables support for the Oak SCSI card. If you have an Acorn
@@ -7044,7 +8038,7 @@
This enables support for the Cumana SCSI I card. If you have an
Acorn system with one of these, say Y. If unsure, say N.
-Cumana SCSI II support (EXPERIMENTAL)
+Cumana SCSI II support
CONFIG_SCSI_CUMANA_2
This enables support for the Cumana SCSI II card. If you have an
Acorn system with one of these, say Y. If unsure, say N.
@@ -7055,17 +8049,17 @@
in the Econet socket. If you have an Acorn system with one of these,
say Y. If unsure, say N.
-EESOX SCSI support (EXPERIMENTAL)
+EESOX SCSI support
CONFIG_SCSI_EESOXSCSI
This enables support for the EESOX SCSI card. If you have an Acorn
system with one of these, say Y, otherwise say N.
-Powertec SCSI support (EXPERIMENTAL)
+PowerTec SCSI support
CONFIG_SCSI_POWERTECSCSI
This enables support for the Powertec SCSI card on Acorn systems. If
you have one of these, say Y. If unsure, say N.
-IEEE 1394 (aka FireWire) support
+IEEE 1394 (FireWire) support
CONFIG_IEEE1394
IEEE 1394 describes a high performance serial bus, which is also
known as FireWire(tm) or i.Link(tm) and is used for connecting all
@@ -7078,10 +8072,10 @@
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called ieee1394.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called ieee1394.o.
-TI PCILynx IEEE 1394 support
+Texas Instruments PCILynx support
CONFIG_IEEE1394_PCILYNX
Say Y here if you have an IEEE-1394 controller with the Texas
Instruments PCILynx chip. Note: this driver is written for revision
@@ -7089,8 +8083,8 @@
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called pcilynx.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called pcilynx.o.
Use local RAM on PCILynx board
CONFIG_IEEE1394_PCILYNX_LOCALRAM
@@ -7100,7 +8094,7 @@
computer's motherboard. Local RAM may speed up command processing
because no PCI transfers are necessary during use of the Packet
Control Lists.
-
+
Note that there are no known PCILynx systems providing local RAM
except for the evaluation boards by Texas Instruments and that the
PCILynx does not reliably report missing RAM. This means that it is
@@ -7114,32 +8108,43 @@
This option enables driver code to access the RAM, ROM and AUX ports
of the PCILynx through character devices in /dev. If you don't know
what this is about then you won't need it.
-
+
If unsure, say N.
+#Adaptec AIC-5800 IEEE 1394 support
+#CONFIG_IEEE1394_AIC5800
+# Say Y here if you have a IEEE 1394 controller using the Adaptec
+# AIC-5800 chip. All Adaptec host adapters (89xx series) use this
+# chip, as well as miro's DV boards.
+#
+# If you want to compile this as a module ( = code which can be
+# inserted in and removed from the running kernel whenever you want),
+# say M here and read <file:Documentation/modules.txt>. The module
+# will be called aic5800.o.
+#
OHCI-1394 support
CONFIG_IEEE1394_OHCI1394
Enable this driver if you have an IEEE 1394 controller based on the
OHCI-1394 specification. The current driver is only tested with OHCI
chipsets made by Texas Instruments and NEC. Most third-party vendors
- use one of these chipsets. It should work with any OHCI-1394 compliant
- card, however.
+ use one of these chipsets. It should work with any OHCI-1394
+ compliant card, however.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called ohci1394.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called ohci1394.o.
OHCI-1394 Video support
CONFIG_IEEE1394_VIDEO1394
- This option enables video device usage for OHCI-1394 cards. Enable this
- option only if you have an IEEE 1394 video device connected to an
- OHCI-1394 card.
+ This option enables video device usage for OHCI-1394 cards. Enable
+ this option only if you have an IEEE 1394 video device connected to
+ an OHCI-1394 card.
SBP-2 support (Harddisks etc.)
CONFIG_IEEE1394_SBP2
- This option enables you to use SBP-2 devices connected to your IEEE 1394
- bus. SBP-2 devices include harddrives and DVD devices.
+ This option enables you to use SBP-2 devices connected to your IEEE
+ 1394 bus. SBP-2 devices include harddrives and DVD devices.
Raw IEEE 1394 I/O support
CONFIG_IEEE1394_RAWIO
@@ -7150,8 +8155,8 @@
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called raw1394.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called raw1394.o.
Excessive debugging output
CONFIG_IEEE1394_VERBOSEDEBUG
@@ -7164,18 +8169,18 @@
Say Y if you really want or need the debugging output, everyone else
says N.
-Network device support?
+Network device support
CONFIG_NETDEVICES
You can say N here if you don't intend to connect your Linux box to
any other computer at all or if all your connections will be over a
telephone line with a modem either via UUCP (UUCP is a protocol to
forward mail and news between unix hosts over telephone lines; read
the UUCP-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto ) or dialing up a shell
+ <http://www.linuxdoc.org/docs.html#howto>) or dialing up a shell
account or a BBS, even using term (term is a program which gives you
almost full Internet connectivity if you have a regular dial up
shell account on some Internet connected Unix computer. Read
- http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html ).
+ <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>).
You'll have to say Y if your computer contains a network card that
you want to use under Linux (make sure you know its name because you
@@ -7191,7 +8196,7 @@
Make sure to read the NET-3-HOWTO. Eventually, you will have to read
Olaf Kirch's excellent and free book "Network Administrator's
- Guide", to be found in http://www.linuxdoc.org/docs.html#guide . If
+ Guide", to be found in <http://www.linuxdoc.org/docs.html#guide>. If
unsure, say Y.
Dummy net driver support
@@ -7204,14 +8209,15 @@
thing often comes in handy, the default is Y. It won't enlarge your
kernel either. What a deal. Read about it in the Network
Administrator's Guide, available from
- http://www.linuxdoc.org/docs.html#guide .
+ <http://www.linuxdoc.org/docs.html#guide>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called dummy.o. If you want to use more than one dummy device at a
- time, you need to compile this driver as a module. Instead of
- 'dummy', the devices will then be called 'dummy0', 'dummy1' etc.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called dummy.o. If you want to use more than one dummy
+ device at a time, you need to compile this driver as a module.
+ Instead of 'dummy', the devices will then be called 'dummy0',
+ 'dummy1' etc.
Bonding driver support
CONFIG_BONDING
@@ -7219,7 +8225,7 @@
Channels together. This is called 'Etherchannel' by Cisco,
'Trunking' by Sun, and 'Bonding' in Linux.
- If you have two ethernet connections to some other computer, you can
+ If you have two Ethernet connections to some other computer, you can
make them behave like one double speed connection using this driver.
Naturally, this has to be supported at the other end as well, either
with a similar Bonding Linux driver, a Cisco 5500 switch or a
@@ -7230,8 +8236,8 @@
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called bonding.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called bonding.o.
SLIP (serial line) support
CONFIG_SLIP
@@ -7247,23 +8253,23 @@
Normally, your access provider has to support SLIP in order for you
to be able to use it, but there is now a SLIP emulator called SLiRP
around (available via FTP (user: anonymous) from
- ftp://metalab.unc.edu/pub/Linux/system/network/serial/ ) which
+ <ftp://metalab.unc.edu/pub/Linux/system/network/serial/>) which
allows you to use SLIP over a regular dial up shell connection. If
you plan to use SLiRP, make sure to say Y to CSLIP, below. The
NET-3-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto , explains how to
+ <http://www.linuxdoc.org/docs.html#howto>, explains how to
configure SLIP. Note that you don't need this option if you just
want to run term (term is a program which gives you almost full
Internet connectivity if you have a regular dial up shell account on
some Internet connected Unix computer. Read
- http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html ). SLIP
+ <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
support will enlarge your kernel by about 4 KB. If unsure, say N.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
- slip.o.
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called slip.o.
CSLIP compressed headers
CONFIG_SLIP_COMPRESSED
@@ -7272,10 +8278,10 @@
on both ends. Ask your access provider if you are not sure and
answer Y, just in case. You will still be able to use plain SLIP. If
you plan to use SLiRP, the SLIP emulator (available from
- ftp://metalab.unc.edu/pub/Linux/system/network/serial/ ) which
+ <ftp://metalab.unc.edu/pub/Linux/system/network/serial/>) which
allows you to use SLIP over a regular dial up shell connection, you
definitely want to say Y here. The NET-3-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto , explains how to configure
+ <http://www.linuxdoc.org/docs.html#howto>, explains how to configure
CSLIP. This won't enlarge your kernel.
Keepalive and linefill
@@ -7296,24 +8302,24 @@
PPP (point-to-point protocol) support
CONFIG_PPP
- PPP (Point to Point Protocol) is a newer and better SLIP. It serves
+ PPP (Point to Point Protocol) is a newer and better SLIP. It serves
the same purpose: sending Internet traffic over telephone (and other
- serial) lines. Ask your access provider if they support it, because
- otherwise you can't use it; most internet access providers these
+ serial) lines. Ask your access provider if they support it, because
+ otherwise you can't use it; most Internet access providers these
days support PPP rather than SLIP.
To use PPP, you need an additional program called pppd as described
- in Documentation/networking/ppp.txt and in the PPP-HOWTO, available
- at http://www.linuxdoc.org/docs.html#howto . If you upgrade
- from an older kernel, you might need to upgrade pppd as well. The
- PPP option enlarges your kernel by about 16 KB.
+ in the PPP-HOWTO, available at
+ <http://www.linuxdoc.org/docs.html#howto>. Make sure that you have
+ the version of pppd recommended in <file:Documentation/Changes>.
+ The PPP option enlarges your kernel by about 16 KB.
There are actually two versions of PPP: the traditional PPP for
asynchronous lines, such as regular analog phone lines, and
synchronous PPP which can be used over digital ISDN lines for
- example. If you want to use PPP over phone lines or other
+ example. If you want to use PPP over phone lines or other
asynchronous serial lines, you need to say Y (or M) here and also to
- the next option, "PPP support for async serial ports". For PPP over
+ the next option, "PPP support for async serial ports". For PPP over
synchronous lines, you should say Y (or M) here and to "Support
synchronous PPP", below.
@@ -7321,12 +8327,12 @@
inserted in and removed from the running kernel whenever you want).
If you said Y to "Version information on all symbols" above, then
you cannot compile the PPP driver into the kernel; you can then only
- compile it as a module. The module will be called ppp_generic.o. If
- you want to compile it as a module, say M here and read
- Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ compile it as a module. The module will be called ppp_generic.o.
+ If you want to compile it as a module, say M here and read
+ <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>.
-PPP multilink support (EXPERIMENTAL)
+PPP multilink support
CONFIG_PPP_MULTILINK
PPP multilink is a protocol (defined in RFC 1990) which allows you
to combine several (logical or physical) lines into one logical PPP
@@ -7337,7 +8343,7 @@
If unsure, say N.
-PPP filtering (EXPERIMENTAL)
+PPP filtering
CONFIG_PPP_FILTER
Say Y here if you want to be able to filter the packets passing over
PPP interfaces. This allows you to control which packets count as
@@ -7357,7 +8363,7 @@
This code is also available as a module (code which can be inserted
into and removed from the running kernel). If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ it as a module, say M here and read <file:Documentation/modules.txt>.
If unsure, say Y.
@@ -7369,20 +8375,22 @@
This code is also available as a module (code which can be inserted
into and removed from the running kernel). If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>.
PPP Deflate compression
CONFIG_PPP_DEFLATE
Support for the Deflate compression method for PPP, which uses the
Deflate algorithm (the same algorithm that gzip uses) to compress
- each PPP packet before it is sent over the wire. The machine at the
+ each PPP packet before it is sent over the wire. The machine at the
other end of the PPP link (usually your ISP) has to support the
- Deflate compression method as well for this to be useful. Even if
+ Deflate compression method as well for this to be useful. Even if
they don't support it, it is safe to say Y here.
This code is also available as a module (code which can be inserted
into and removed from the running kernel). If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>.
PPP BSD-Compress compression
CONFIG_PPP_BSDCOMP
@@ -7401,14 +8409,14 @@
module; it is called bsd_comp.o and will show up in the directory
modules once you have said "make modules". If unsure, say N.
-PPP over Ethernet (EXPERIMENTAL)
+PPP over Ethernet
CONFIG_PPPOE
Support for PPP over Ethernet.
This driver requires a specially patched pppd daemon. The patch to
pppd, along with binaries of a patched pppd package can be found at:
- http://www.shoshin.uwaterloo.ca/~mostrows
-
+ <http://www.shoshin.uwaterloo.ca/~mostrows>.
+
Wireless LAN (non-hamradio)
CONFIG_NET_RADIO
Support for wireless LANs and everything having to do with radio,
@@ -7425,18 +8433,18 @@
driver (or Linux). If you wish to use Wireless Extensions with
wireless PCMCIA (PC-) cards, you need to say Y here; you can fetch
the tools from
- http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html .
+ <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>.
Some user-level drivers for scarab devices which don't require
special kernel support are available from
- ftp://shadow.cabi.net/pub/Linux .
+ <ftp://shadow.cabi.net/pub/Linux>.
STRIP (Metricom Starmode radio IP)
CONFIG_STRIP
Say Y if you have a Metricom radio and intend to use Starmode Radio
IP. STRIP is a radio protocol developed for the MosquitoNet project
- (on the WWW at http://mosquitonet.stanford.edu/ ) to send Internet
- traffic using Metricom radios. Metricom radios are small, battery
+ (on the WWW at <http://mosquitonet.stanford.edu/>) to send Internet
+ traffic using Metricom radios. Metricom radios are small, battery
powered, 100kbit/sec packet radio transceivers, about the size and
weight of a cellular telephone. (You may also have heard them called
"Metricom modems" but we avoid the term "modem" because it misleads
@@ -7447,50 +8455,51 @@
it is obviously most useful for people with laptop computers. If you
think you might get a Metricom radio in the future, there is no harm
in saying Y to STRIP now, except that it makes the kernel a bit
- bigger.
+ bigger.
You can also compile this as a module ( = code which can be inserted
in and removed from the running kernel whenever you want), say M
- here and read Documentation/modules.txt. The module will be called
- strip.o.
+ here and read <file:Documentation/modules.txt>. The module will be
+ called strip.o.
AT&T WaveLAN & DEC RoamAbout DS support
CONFIG_WAVELAN
The Lucent WaveLAN (formerly NCR and AT&T; or DEC RoamAbout DS) is
a Radio LAN (wireless Ethernet-like Local Area Network) using the
radio frequencies 900 MHz and 2.4 GHz.
-
- This driver support the ISA version of the WaveLAN card. A separate
+
+ This driver support the ISA version of the WaveLAN card. A separate
driver for the PCMCIA (PC-card) hardware is available in David
- Hinds' pcmcia-cs package (see the file Documentation/Changes for
- location).
+ Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
+ for location).
If you want to use an ISA WaveLAN card under Linux, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . Some more specific
- information is contained in Documentation/networking/wavelan.txt and
- in the source code drivers/net/wavelan.p.h.
+ <http://www.linuxdoc.org/docs.html#howto>. Some more specific
+ information is contained in
+ <file:Documentation/networking/wavelan.txt> and in the source code
+ <file:drivers/net/wavelan.p.h>.
You will also need the wireless tools package available from
- http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html .
+ <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>.
Please read the man pages contained therein.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called wavelan.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called wavelan.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
Aironet Arlan 655 & IC2200 DS support
CONFIG_ARLAN
Aironet makes Arlan, a class of wireless LAN adapters. These use the
www.Telxon.com chip, which is also used on several similar cards.
This driver is tested on the 655 and IC2200 series cards. Look at
- http://www.ylenurme.ee/~elmer/655/ for the latest information.
-
+ <http://www.ylenurme.ee/~elmer/655/> for the latest information.
+
The driver is built as two modules, arlan and arlan-proc. The latter
is the /proc interface and is not needed most of time.
-
+
On some computers the card ends up in non-valid state after some
time. Use a ping-reset script to clear it.
@@ -7499,27 +8508,27 @@
www.aironet.com (recently bought by Cisco) makes these 802.11 DS
adapters. Driver by Elmer Joandi (elmer@ylenurme.ee).
- Say Y here if you have such an adapter, and then say Y below to
- the option that applies to your particular type of card (PCI, ISA,
+ Say Y here if you have such an adapter, and then say Y below to
+ the option that applies to your particular type of card (PCI, ISA,
or PCMCIA).
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called aironet4500_core.o. If you want to
- compile it as a module, say M here and read
- Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called aironet4500_core.o. If you want to
+ compile it as a module, say M here and read
+ <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>.
- quick config parameters:
+ quick config parameters:
SSID=tsunami - "The Password"
adhoc=1 there are no Access Points around
- master=1 Adhoc master (the one who creates network
+ master=1 Adhoc master (the one who creates network
sync)
- slave=1 Adhoc slave (btw, it is still forming own net
+ slave=1 Adhoc slave (btw, it is still forming own net
sometimes, and has problems with firmware...
change IbssJoinNetTimeout from /proc...)
channel=1..? meaningful in adhoc mode
-
+
If you have problems with screwing up card, both_bap_lock=1 is a
conservative value (performance hit 15%).
@@ -7527,107 +8536,107 @@
Aironet 4500/4800 ISA/PCI/PNP/365 support
CONFIG_AIRONET4500_NONCS
- If you have an ISA, PCI or PCMCIA Aironet 4500/4800 wireless LAN
- card, say Y here, and then also to the options below that apply
+ If you have an ISA, PCI or PCMCIA Aironet 4500/4800 wireless LAN
+ card, say Y here, and then also to the options below that apply
to you.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called aironet4500_card.o. If you want to
- compile it as a module, say M here and read
- Documentation/modules.txt
+ The module will be called aironet4500_card.o. If you want to
+ compile it as a module, say M here and read
+ <file:Documentation/modules.txt>.
Aironet 4500/4800 PNP support
CONFIG_AIRONET4500_PNP
- If you have an ISA Aironet 4500/4800 card which you want to use in
- PNP (Plug and Play) mode, say Y here. This is the recommended mode
- for ISA cards. Remember however to enable the PNP jumper on the
+ If you have an ISA Aironet 4500/4800 card which you want to use in
+ PnP (Plug and Play) mode, say Y here. This is the recommended mode
+ for ISA cards. Remember however to enable the PnP jumper on the
board if you say Y here.
Aironet 4500/4800 PCI support
CONFIG_AIRONET4500_PCI
If you have an PCI Aironet 4500/4800 card, say Y here.
-Aironet 4500/4800 ISA broken support (EXPERIMENTAL)
+Aironet 4500/4800 ISA broken support
CONFIG_AIRONET4500_ISA
If you have an ISA Aironet 4500/4800 card which you want to run in
- non-PNP mode, say Y here. This is not recommended and does not work
+ non-PnP mode, say Y here. This is not recommended and does not work
correctly at this point. Say N.
-Aironet 4500/4800 I365 broken support (EXPERIMENTAL)
+Aironet 4500/4800 I365 broken support
CONFIG_AIRONET4500_I365
- If you have a PCMCIA Aironet 4500/4800 card which you want to use
- without the standard PCMCIA cardservices provided by the pcmcia-cs
+ If you have a PCMCIA Aironet 4500/4800 card which you want to use
+ without the standard PCMCIA cardservices provided by the pcmcia-cs
package, say Y here. This is not recommended, so say N.
Aironet 4500/4800 PCMCIA support
CONFIG_AIRONET4500_CS
- Say Y here if you have a PCMCIA Aironet 4500/4800 card which you
+ Say Y here if you have a PCMCIA Aironet 4500/4800 card which you
want to use with the standard PCMCIA cardservices provided by the
pcmcia-cs package.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called aironet4500_cs.o. If you want to
- compile it as a module, say M here and read
- Documentation/modules.txt.
-
+ The module will be called aironet4500_cs.o. If you want to
+ compile it as a module, say M here and read
+ <file:Documentation/modules.txt>.
+
Aironet 4500/4800 PROC interface
CONFIG_AIRONET4500_PROC
- If you say Y here (and to the "/proc file system" below), you will
- be able to configure your Aironet card via the
+ If you say Y here (and to the "/proc file system" below), you will
+ be able to configure your Aironet card via the
/proc/sys/aironet4500 interface.
- Additional info: look in drivers/net/aironet4500_rids.c.
+ Additional info: look in <file:drivers/net/aironet4500_rid.c>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called aironet4500_proc.o. If you want to
- compile it as a module, say M here and read
- Documentation/modules.txt.
+ The module will be called aironet4500_proc.o. If you want to
+ compile it as a module, say M here and read
+ <file:Documentation/modules.txt>.
NOTE: the proc interface uses a lot of memory, so it is recommended
- to compile it as a module and remove the module after
+ to compile it as a module and remove the module after
configuration.
LAPB over Ethernet driver
CONFIG_LAPBETHER
This is a driver for a pseudo device (typically called /dev/lapb0)
which allows you to open an LAPB point-to-point connection to some
- other computer on your Ethernet network. In order to do this, you
+ other computer on your Ethernet network. In order to do this, you
need to say Y or M to the driver for your Ethernet card as well as
- to "LAPB Data Link Driver".
+ to "LAPB Data Link Driver".
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called lapbether.o. If unsure, say N.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called lapbether.o. If unsure, say N.
X.25 async driver
CONFIG_X25_ASY
This is a driver for sending and receiving X.25 frames over regular
asynchronous serial lines such as telephone lines equipped with
- ordinary modems. Experts should note that this driver doesn't
+ ordinary modems. Experts should note that this driver doesn't
currently comply with the asynchronous HDLS framing protocols in
- CCITT recommendation X.25.
+ CCITT recommendation X.25.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called x25_asy.o. If unsure, say N.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called x25_asy.o. If unsure, say N.
PCMCIA network device support
CONFIG_NET_PCMCIA
Say Y if you would like to include support for any PCMCIA or CardBus
network adapters, then say Y to the driver for your particular card
- below. PCMCIA- or PC-cards are credit-card size devices often used
+ below. PCMCIA- or PC-cards are credit-card size devices often used
with laptops computers; CardBus is the newer and faster version of
- PCMCIA.
+ PCMCIA.
To use your PC-cards, you will need supporting software from David
- Hinds' pcmcia-cs package (see the file Documentation/Changes for
- location). You also want to check out the PCMCIA-HOWTO, available
- from http://www.linuxdoc.org/docs.html#howto .
+ Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
+ for location). You also want to check out the PCMCIA-HOWTO,
+ available from <http://www.linuxdoc.org/docs.html#howto>.
If unsure, say N.
@@ -7638,9 +8647,9 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called 3c589_cs.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt. If unsure,
- say N.
+ The module will be called 3c589_cs.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>. If
+ unsure, say N.
3Com 3c574 PCMCIA support
CONFIG_PCMCIA_3C574
@@ -7649,9 +8658,9 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called 3c574_cs.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt. If unsure,
- say N.
+ The module will be called 3c574_cs.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>. If
+ unsure, say N.
Fujitsu FMV-J18x PCMCIA support
CONFIG_PCMCIA_FMVJ18X
@@ -7660,9 +8669,9 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called fmvj18x_cs.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt. If unsure,
- say N.
+ The module will be called fmvj18x_cs.o. If you want to compile it
+ as a module, say M here and read <file:Documentation/modules.txt>.
+ If unsure, say N.
NE2000 compatible PCMCIA support
CONFIG_PCMCIA_PCNET
@@ -7671,9 +8680,9 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called pcnet_cs.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt. If unsure,
- say N.
+ The module will be called pcnet_cs.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>. If
+ unsure, say N.
New Media PCMCIA support
CONFIG_PCMCIA_NMCLAN
@@ -7682,9 +8691,9 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called nmclan_cs.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt. If unsure,
- say N.
+ The module will be called nmclan_cs.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>. If
+ unsure, say N.
SMC 91Cxx PCMCIA support
CONFIG_PCMCIA_SMC91C92
@@ -7693,20 +8702,20 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called smc91c92_cs.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt. If
- unsure, say N.
+ The module will be called smc91c92_cs.o. If you want to compile it
+ as a module, say M here and read <file:Documentation/modules.txt>.
+ If unsure, say N.
Xircom 16-bit PCMCIA support
CONFIG_PCMCIA_XIRC2PS
- Say Y here if you intend to attach a Xircom 16-bit PCMCIA
- (PC-card) Ethernet or Fast Ethernet card to your computer.
+ Say Y here if you intend to attach a Xircom 16-bit PCMCIA (PC-card)
+ Ethernet or Fast Ethernet card to your computer.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called xirc2ps_cs.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt. If unsure,
- say N.
+ The module will be called xirc2ps_cs.o. If you want to compile it
+ as a module, say M here and read <file:Documentation/modules.txt>.
+ If unsure, say N.
COM20020 ARCnet PCMCIA support
CONFIG_ARCNET_COM20020_CS
@@ -7715,20 +8724,20 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called com20020_cs.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt. If
- unsure, say N.
+ The module will be called com20020_cs.o. If you want to compile it
+ as a module, say M here and read <file:Documentation/modules.txt>.
+ If unsure, say N.
IBM PCMCIA Token Ring adapter support
CONFIG_PCMCIA_IBMTR
Say Y here if you intend to attach this type of Token Ring PCMCIA
card to your computer. You then also need to say Y to "Token Ring
- driver support".
+ driver support".
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called ibmtr_cs.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt.
+ The module will be called ibmtr_cs.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
Xircom Tulip-like CardBus support
CONFIG_PCMCIA_XIRTULIP
@@ -7739,20 +8748,20 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called xircom_tulip_cb.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt. If
- unsure, say N.
+ The module will be called xircom_tulip_cb.o. If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>. If unsure, say N.
-Pcmcia Wireless LAN
+PCMCIA Wireless LAN
CONFIG_NET_PCMCIA_RADIO
Say Y here if you would like to use a PCMCIA (PC-card) device to
connect to a wireless local area network. Then say Y to the driver
for your particular card below.
To use your PC-cards, you will need supporting software from David
- Hinds' pcmcia-cs package (see the file Documentation/Changes for
- location). You also want to check out the PCMCIA-HOWTO, available
- from http://www.linuxdoc.org/docs.html#howto .
+ Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
+ for location). You also want to check out the PCMCIA-HOWTO,
+ available from <http://www.linuxdoc.org/docs.html#howto>.
Hermes chipset 802.11b support (Orinoco/Prism2/Symbol cards)
CONFIG_HERMES
@@ -7772,7 +8781,7 @@
You will also very likely also need the Wireless Tools in order to
configure your card and that /etc/pcmcia/wireless.opts works :
- http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html
+ <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>
Apple Airport support (built-in)
CONFIG_APPLE_AIRPORT
@@ -7796,24 +8805,24 @@
CONFIG_PCMCIA_HERMES
A driver for "Hermes" chipset based PCMCIA wireless adaptors, such
as the Lucent WavelanIEEE/Orinoco cards and their OEM (Cabletron/
- EnteraSys RoamAbout 802.11, ELSA Airlancer, Melco Buffalo and others).
- It should also be usable on various Prism II based cards such as the
- Linksys, D-Link and Farallon Skyline. It should also work on Symbol
- cards such as the 3Com AirConnect and Ericsson WLAN.
+ EnteraSys RoamAbout 802.11, ELSA Airlancer, Melco Buffalo and
+ others). It should also be usable on various Prism II based cards
+ such as the Linksys, D-Link and Farallon Skyline. It should also
+ work on Symbol cards such as the 3Com AirConnect and Ericsson WLAN.
To use your PC-cards, you will need supporting software from David
- Hinds' pcmcia-cs package (see the file Documentation/Changes for
- location). You also want to check out the PCMCIA-HOWTO, available
- from http://www.linuxdoc.org/docs.html#howto .
+ Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
+ for location). You also want to check out the PCMCIA-HOWTO,
+ available from <http://www.linuxdoc.org/docs.html#howto>.
You will also very likely also need the Wireless Tools in order to
- configure your card and that /etc/pcmcia/wireless.opts works :
- http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html
+ configure your card and that /etc/pcmcia/wireless.opts works:
+ <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>.
Cisco/Aironet 34X/35X/4500/4800 ISA and PCI cards
CONFIG_AIRO
- This is the standard Linux driver to support Cisco/Aironet ISA
- and PCI 802.11 wireless cards.
+ This is the standard Linux driver to support Cisco/Aironet ISA and
+ PCI 802.11 wireless cards.
It supports the new 802.11b cards from Cisco (Cisco 34X, Cisco 35X
- with or without encryption) as well as card before the Cisco
aquisition (Aironet 4500, Aironet 4800, Aironet 4800B).
@@ -7827,7 +8836,7 @@
Cisco/Aironet 34X/35X/4500/4800 PCMCIA cards
CONFIG_AIRO_CS
This is the standard Linux driver to support Cisco/Aironet PCMCIA
- 802.11 wireless cards. This driver is the same as the Aironet
+ 802.11 wireless cards. This driver is the same as the Aironet
driver part of the Linux Pcmcia package.
It supports the new 802.11b cards from Cisco (Cisco 34X, Cisco 35X
- with or without encryption) as well as card before the Cisco
@@ -7840,22 +8849,28 @@
Cisco Linux utilities can be used to configure the card.
To use your PC-cards, you will need supporting software from David
- Hinds' pcmcia-cs package (see the file Documentation/Changes for
- location). You also want to check out the PCMCIA-HOWTO, available
- from http://www.linuxdoc.org/docs.html#howto .
+ Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
+ for location). You also want to check out the PCMCIA-HOWTO,
+ available from <http://www.linuxdoc.org/docs.html#howto>.
Aviator/Raytheon 2.4MHz wireless support
CONFIG_PCMCIA_RAYCS
Say Y here if you intend to attach an Aviator/Raytheon PCMCIA
(PC-card) wireless Ethernet networking card to your computer.
- Please read the file Documentation/networking/ray_cs.txt for
+ Please read the file <file:Documentation/networking/ray_cs.txt> for
details.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called ray_cs.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt. If unsure,
- say N.
+ The module will be called ray_cs.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>. If
+ unsure, say N.
+
+Apple Airport support (built-in)
+CONFIG_APPLE_AIRPORT
+ Say Y here to support the Airport 802.11b wireless Ethernet hardware
+ built into the Macintosh iBook and other recent PowerPC-based
+ Macintosh machines.
Xircom Netwave AirSurfer wireless support
CONFIG_PCMCIA_NETWAVE
@@ -7864,9 +8879,9 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called netwave_cs.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt. If unsure,
- say N.
+ The module will be called netwave_cs.o. If you want to compile it
+ as a module, say M here and read <file:Documentation/modules.txt>.
+ If unsure, say N.
AT&T/Lucent Wavelan wireless support
CONFIG_PCMCIA_WAVELAN
@@ -7876,44 +8891,45 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called wavelan_cs.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt. If unsure,
- say N.
+ The module will be called wavelan_cs.o. If you want to compile it
+ as a module, say M here and read <file:Documentation/modules.txt>.
+ If unsure, say N.
PLIP (parallel port) support
CONFIG_PLIP
PLIP (Parallel Line Internet Protocol) is used to create a
reasonably fast mini network consisting of two (or, rarely, more)
- local machines. A PLIP link from a Linux box is a popular means to
- install a Linux distribution on a machine which doesn't have a CDROM
- drive (a minimal system has to be transferred with floppies first).
- The kernels on both machines need to have this PLIP option enabled
- for this to work.
-
- The PLIP driver has two modes, mode 0 and mode 1. The parallel ports
- (the connectors at the computers with 25 holes) are connected with
- "null printer" or "Turbo Laplink" cables which can transmit 4 bits
- at a time (mode 0) or with special PLIP cables, to be used on
+ local machines. A PLIP link from a Linux box is a popular means to
+ install a Linux distribution on a machine which doesn't have a
+ CD-ROM drive (a minimal system has to be transferred with floppies
+ first). The kernels on both machines need to have this PLIP option
+ enabled for this to work.
+
+ The PLIP driver has two modes, mode 0 and mode 1. The parallel
+ ports (the connectors at the computers with 25 holes) are connected
+ with "null printer" or "Turbo Laplink" cables which can transmit 4
+ bits at a time (mode 0) or with special PLIP cables, to be used on
bidirectional parallel ports only, which can transmit 8 bits at a
time (mode 1); you can find the wiring of these cables in
- Documentation/networking/PLIP.txt. The cables can be up to 15m long.
- Mode 0 works also if one of the machines runs DOS/Windows and has
- some PLIP software installed, e.g. the Crynwr PLIP packet driver
- (http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html ) and
- winsock or NCSA's telnet.
+ <file:Documentation/networking/PLIP.txt>. The cables can be up to
+ 15m long. Mode 0 works also if one of the machines runs DOS/Windows
+ and has some PLIP software installed, e.g. the Crynwr PLIP packet
+ driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
+ and winsock or NCSA's telnet.
If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
as the NET-3-HOWTO, both available from
- http://www.linuxdoc.org/docs.html#howto . Note that the PLIP
+ <http://www.linuxdoc.org/docs.html#howto>. Note that the PLIP
protocol has been changed and this PLIP driver won't work together
- with the PLIP support in Linux versions 1.0.x. This option enlarges
+ with the PLIP support in Linux versions 1.0.x. This option enlarges
your kernel by about 8 KB.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
- plip.o. If unsure, say Y or M, in case you buy a laptop later.
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called plip.o. If unsure, say Y or M, in case you buy a laptop
+ later.
EQL (serial line load balancing) support
CONFIG_EQUALIZER
@@ -7921,39 +8937,41 @@
usually requires two modems and two telephone lines) and you use
SLIP (the protocol for sending Internet traffic over telephone
lines) or PPP (a better SLIP) on them, you can make them behave like
- one double speed connection using this driver. Naturally, this has
+ one double speed connection using this driver. Naturally, this has
to be supported at the other end as well, either with a similar EQL
- Linux driver or with a Livingston Portmaster 2e.
+ Linux driver or with a Livingston Portmaster 2e.
- Say Y if you want this and read Documentation/networking/eql.txt.
- You may also want to read section 6.2 of the NET-3-HOWTO, available
- from http://www.linuxdoc.org/docs.html#howto .
+ Say Y if you want this and read
+ <file:Documentation/networking/eql.txt>. You may also want to read
+ section 6.2 of the NET-3-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called eql.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt. If unsure,
- say N.
+ The module will be called eql.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>. If
+ unsure, say N.
-Universal TUN/TAP device driver.
+Universal TUN/TAP device driver support
CONFIG_TUN
- TUN/TAP provides packet reception and transmission for user space programs.
- It can be viewed as a simple Point-to-Point or Ethernet device, which
- instead of receiving packets from a physical media, receives them from
- user space program and instead of sending packets via physical media
- writes them to the user space program.
+ TUN/TAP provides packet reception and transmission for user space
+ programs. It can be viewed as a simple Point-to-Point or Ethernet
+ device, which instead of receiving packets from a physical media,
+ receives them from user space program and instead of sending packets
+ via physical media writes them to the user space program.
+
+ When a program opens /dev/net/tun, driver creates and registers
+ corresponding net device tunX or tapX. After a program closed above
+ devices, driver will automatically delete tunXX or tapXX device and
+ all routes corresponding to it.
- When a program opens /dev/net/tun, driver creates and registers
- corresponding net device tunX or tapX. After a program closed above
- devices, driver will automatically delete tunXX or tapXX device and all
- routes corresponding to it.
-
- Please read Documentation/networking/tuntap.txt for more information.
+ Please read <file:Documentation/networking/tuntap.txt> for more
+ information.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called tun.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ The module will be called tun.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
If you don't know what to use this for, you don't need it.
@@ -7963,7 +8981,7 @@
driver", above) and create a character special file /dev/tap0 with
major number 36 and minor number 16 using mknod ("man mknod"), you
will be able to have a user space program read and write raw
- Ethernet frames from/to that special file. tap0 can be configured
+ Ethernet frames from/to that special file. tap0 can be configured
with ifconfig and route like any other Ethernet device but it is not
connected to any physical LAN; everything written by the user to
/dev/tap0 is treated by the kernel as if it had come in from a LAN
@@ -7971,19 +8989,19 @@
device tap0 can instead be read by the user from /dev/tap0: the user
mode program replaces the LAN that would be attached to an ordinary
Ethernet device. Please read the file
- Documentation/networking/ethertap.txt for more information.
+ <file:Documentation/networking/ethertap.txt> for more information.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called ethertap.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
If you don't know what to use this for, you don't need it.
Sealevel Systems 4021 support
CONFIG_SEALEVEL_4021
This is a driver for the Sealevel Systems ACB 56 serial I/O adapter.
-
+
This driver can only be compiled as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
If you want to do that, say M here. The module will be called
@@ -7997,6 +9015,21 @@
of the Cisco HDLC/PPP driver (syncppp.c).
The SyncLink WAN driver (in character devices) must also be enabled.
+FarSync T-Series support
+CONFIG_FARSYNC
+ This driver supports the FarSync T-Series X.21 (and V.35/V.24) cards
+ from FarSite Communications Ltd.
+ Synchronous communication is supported on all ports at speeds up to
+ 8Mb/s (128K on V.24) using synchronous PPP or Cisco HDLC.
+
+ If you want to compile this driver as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want)
+ say M here and read <file:Documentation/modules.txt>.
+ The module will be called farsync.o and if you want the module to be
+ automatically loaded when the interface is referenced then you
+ should add "alias syncX farsync" to /etc/modules.conf for each
+ interface, where X is 0, 1, 2, ...
+
Frame Relay (DLCI) support
CONFIG_DLCI
This is support for the frame relay protocol; frame relay is a fast
@@ -8006,15 +9039,15 @@
network, usually at the phone company) can carry several logical
point-to-point connections to other computers connected to the frame
relay network. For a general explanation of the protocol, check out
- http://www.frforum.com/ on the WWW. To use frame relay, you need
+ <http://www.frforum.com/> on the WWW. To use frame relay, you need
supporting hardware (called FRAD) and certain programs from the
net-tools package as explained in
- Documentation/networking/framerelay.txt.
+ <file:Documentation/networking/framerelay.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called dlci.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
Max open DLCI
CONFIG_DLCI_COUNT
@@ -8029,19 +9062,19 @@
handled by each of your hardware frame relay access devices. Go with
the default.
-Sangoma S502A FRAD support
+SDLA (Sangoma S502/S508) support
CONFIG_SDLA
Say Y here if you need a driver for the Sangoma S502A, S502E, and
S508 Frame Relay Access Devices. These are multi-protocol cards, but
only frame relay is supported by the driver at this time. Please
- read Documentation/framerelay.txt.
+ read <file:Documentation/framerelay.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called sdla.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
-Acorn Econet/AUN protocols (EXPERIMENTAL)
+Acorn Econet/AUN protocols
CONFIG_ECONET
Econet is a fairly old and slow networking protocol mainly used by
Acorn computers to access file and print servers. It uses native
@@ -8057,7 +9090,7 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called econet.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
AUN over UDP
CONFIG_ECONET_AUNUDP
@@ -8070,7 +9103,7 @@
Say Y here if you have a native Econet network card installed in
your computer.
-WAN Router
+WAN router
CONFIG_WAN_ROUTER
Wide Area Networks (WANs), such as X.25, frame relay and leased
lines, are used to interconnect Local Area Networks (LANs) over vast
@@ -8082,16 +9115,17 @@
As an alternative, WAN routing can be built into the Linux kernel.
With relatively inexpensive WAN interface cards available on the
market, a perfectly usable router can be built for less than half
- the price of an external router. If you have one of those cards and
+ the price of an external router. If you have one of those cards and
wish to use your Linux box as a WAN router, say Y here and also to
- the WAN driver for your card, below. You will then need the
- wan-tools package which is available from ftp://ftp.sangoma.com .
- Read Documentation/networking/wan-router.txt for more information.
+ the WAN driver for your card, below. You will then need the
+ wan-tools package which is available from <ftp://ftp.sangoma.com>.
+ Read <file:Documentation/networking/wan-router.txt> for more
+ information.
The WAN routing support is also available as a module called
wanrouter.o ( = code which can be inserted in and removed from the
- running kernel whenever you want). If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ running kernel whenever you want). If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
If unsure, say N.
@@ -8103,13 +9137,13 @@
IMPORTANT NOTE: This option is NOT COMPATIBLE with "Network packet
filtering" (CONFIG_NETFILTER). Say N here if you say Y there.
- However, it will work with all options in the "IP: advanced router"
- section (except for "IP: use TOS value as routing key" and
- "IP: use FWMARK value as routing key").
+ However, it will work with all options in the "Advanced router"
+ section (except for "Use TOS value as routing key" and
+ "Use FWMARK value as routing key").
At the moment, few devices support fast switching (tulip is one of
them, a modified 8390 driver can be found at
- ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz ).
+ <ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz>).
If unsure, say N.
@@ -8119,7 +9153,7 @@
during periods of extremal congestion. At the moment only a couple
of device drivers support it (really only one -- tulip, a modified
8390 driver can be found at
- ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz ).
+ <ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz>).
Really, this option is applicable to any machine attached to a fast
enough network, and even a 10 Mb NIC is able to kill a not very slow
@@ -8146,68 +9180,75 @@
This code is considered to be experimental.
To administer these schedulers, you'll need the user-level utilities
- from the package iproute2+tc at ftp://ftp.inr.ac.ru/ip-routing/ .
+ from the package iproute2+tc at <ftp://ftp.inr.ac.ru/ip-routing/>.
That package also contains some documentation; for more, check out
- http://snafu.freedom.org/linux2.2/iproute-notes.html .
+ <http://snafu.freedom.org/linux2.2/iproute-notes.html>.
This Quality of Service (QoS) support will enable you to use
Differentiated Services (diffserv) and Resource Reservation Protocol
(RSVP) on your Linux router if you also say Y to "QoS support",
"Packet classifier API" and to some classifiers below. Documentation
- and software is at http://icawww1.epfl.ch/linux-diffserv/ .
+ and software is at <http://icawww1.epfl.ch/linux-diffserv/>.
If you say Y here and to "/proc file system" below, you will be able
to read status information about packet schedulers from the file
/proc/net/psched.
-
+
The available schedulers are listed in the following questions; you
can say Y to as many as you like. If unsure, say N now.
CBQ packet scheduler
CONFIG_NET_SCH_CBQ
Say Y here if you want to use the Class-Based Queueing (CBQ) packet
- scheduling algorithm for some of your network devices. This
+ scheduling algorithm for some of your network devices. This
algorithm classifies the waiting packets into a tree-like hierarchy
of classes; the leaves of this tree are in turn scheduled by
separate algorithms (called "disciplines" in this context).
- See the top of net/sched/sch_cbq.c for references about the CBQ
- algorithm.
-
+ See the top of <file:net/sched/sch_cbq.c> for references about the
+ CBQ algorithm.
+
CBQ is a commonly used scheduler, so if you're unsure, you should
say Y here. Then say Y to all the queueing algorithms below that you
- want to use as CBQ disciplines. Then say Y to "Packet classifier
+ want to use as CBQ disciplines. Then say Y to "Packet classifier
API" and say Y to all the classifiers you want to use; a classifier
is a routine that allows you to sort your outgoing traffic into
classes based on a certain criterion.
This code is also available as a module called sch_cbq.o ( = code
which can be inserted in and removed from the running kernel
- whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
CSZ packet scheduler
CONFIG_NET_SCH_CSZ
Say Y here if you want to use the Clark-Shenker-Zhang (CSZ) packet
- scheduling algorithm for some of your network devices. At the
+ scheduling algorithm for some of your network devices. At the
moment, this is the only algorithm that can guarantee service for
- real-time applications (see the top of net/sched/sch_csz.c for
- details and references about the algorithm).
-
+ real-time applications (see the top of <file:net/sched/sch_csz.c>
+ for details and references about the algorithm).
+
Note: this scheduler is currently broken.
This code is also available as a module called sch_csz.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
-#ATM pseudo-scheduler
-#CONFIG_NET_SCH_ATM
-#
-# ???
-#
-
-The simplest PRIO pseudo scheduler
+ATM pseudo-scheduler
+CONFIG_NET_SCH_ATM
+ Say Y here if you want to use the ATM pseudo-scheduler. This
+ provides a framework for invoking classifiers (aka "filters"), which
+ in turn select classes of this queuing discipline. Each class maps
+ the flow(s) it is handling to a given virtual circuit (see the top of
+ <file:net/sched/sch_atm.c>).
+
+ This code is also available as a module called sch_atm.o ( = code
+ which can be inserted in and removed from the running kernel
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
+
+The simplest PRIO pseudo-scheduler
CONFIG_NET_SCH_PRIO
Say Y here if you want to use an n-band priority queue packet
"scheduler" for some of your network devices or as a leaf discipline
@@ -8216,32 +9257,56 @@
This code is also available as a module called sch_prio.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
+
+Diffserv field marker
+CONFIG_NET_SCH_DSMARK
+ Say Y if you want to schedule packets avccording to the
+ Differentiated Services architecture proposed in RFC 2475.
+ Technical information on this method, with pointers to associated
+ RFCs, is available at <http://www.gta.ufrj.br/diffserv/>.
+
+ This code is also available as a module called sch_dsmark.o ( = code
+ which can be inserted in and removed from the running kernel
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
+
+GRED queue
+CONFIG_NET_SCH_GRED
+ Say Y here if you want to use the Generic Random Early Detection
+ (RED) packet scheduling algorithm for some of your network devices
+ (see the top of <file:net/sched/sch_red.c> for details and
+ references about the algorithm).
+
+ This code is also available as a module called sch_gred.o ( = code
+ which can be inserted in and removed from the running kernel
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
RED queue
CONFIG_NET_SCH_RED
Say Y here if you want to use the Random Early Detection (RED)
packet scheduling algorithm for some of your network devices (see
- the top of net/sched/sch_red.c for details and references about the
- algorithm).
+ the top of <file:net/sched/sch_red.c> for details and references
+ about the algorithm).
This code is also available as a module called sch_red.o ( = code
which can be inserted in and removed from the running kernel
- whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
SFQ queue
CONFIG_NET_SCH_SFQ
Say Y here if you want to use the Stochastic Fairness Queueing (SFQ)
packet scheduling algorithm for some of your network devices or as a
leaf discipline for the CBQ scheduling algorithm (see the top of
- net/sched/sch_sfq.c for details and references about the SFQ
- algorithm).
+ <file:net/sched/sch_sfq.c> for details and references about the SFQ
+ algorithm).
This code is also available as a module called sch_sfq.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
TEQL queue
CONFIG_NET_SCH_TEQL
@@ -8249,30 +9314,36 @@
scheduling algorithm for some of your network devices or as a leaf
discipline for the CBQ scheduling algorithm. This queueing
discipline allows the combination of several physical devices into
- one virtual device. (see the top of net/sched/sch_teql.c for
+ one virtual device. (see the top of <file:net/sched/sch_teql.c> for
details).
This code is also available as a module called sch_teql.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
TBF queue
CONFIG_NET_SCH_TBF
Say Y here if you want to use the Simple Token Bucket Filter (TBF)
packet scheduling algorithm for some of your network devices or as a
leaf discipline for the CBQ scheduling algorithm (see the top of
- net/sched/sch_tbf.c for a description of the TBF algorithm).
+ <file:net/sched/sch_tbf.c> for a description of the TBF algorithm).
This code is also available as a module called sch_tbf.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
+
+Ingress Qdisc
+CONFIG_NET_SCH_INGRESS
+ If you say Y here, you will be able to police incoming bandwidth
+ and drop packets when this bandwidth exceeds your desired rate.
+ If unsure, say Y.
-### Add these
-#+tristate ' GRED queue' CONFIG_NET_SCH_GRED
-#+tristate ' Diffserv field marker' CONFIG_NET_SCH_DSMARK
-#+tristate ' Ingress Qdisc' CONFIG_NET_SCH_INGRESS
+ This code is also available as a module called cls_ingress.o
+ ( = code which can be inserted in and removed from the running
+ kernel whenever you want). If you want to compile it as a module,
+ say M here and read <file:Documentation/modules.txt>.
QoS support
CONFIG_NET_QOS
@@ -8284,10 +9355,10 @@
Differentiated Services (diffserv) and Resource Reservation Protocol
(RSVP) on your Linux router if you also say Y to "Packet classifier
API" and to some classifiers below. Documentation and software is at
- http://icawww1.epfl.ch/linux-diffserv/ .
+ <http://icawww1.epfl.ch/linux-diffserv/>.
Note that the answer to this question won't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all
the questions about QoS support.
Rate estimator
@@ -8307,10 +9378,24 @@
This will enable you to use Differentiated Services (diffserv) and
Resource Reservation Protocol (RSVP) on your Linux router.
Documentation and software is at
- http://icawww1.epfl.ch/linux-diffserv/ .
+ <http://icawww1.epfl.ch/linux-diffserv/>.
-### Add
-#tristate ' TC index classifier' CONFIG_NET_CLS_TCINDEX
+Traffic policing (needed for in/egress)
+CONFIG_NET_CLS_POLICE
+ Say Y to support traffic policing (bandwidth limits). Needed for
+ ingress and egress rate limiting.
+
+TC index classifier
+CONFIG_NET_CLS_TCINDEX
+ If you say Y here, you will be able to classify outgoing packets
+ according to the tc_index field of the skb. You will want this
+ feature if you want to implement Differentiated Services using
+ sch_dsmark. If unsure, say Y.
+
+ This code is also available as a module called cls_tcindex.o
+ ( = code which can be inserted in and removed from the running
+ kernel whenever you want). If you want to compile it as a module,
+ say M here and read <file:Documentation/modules.txt>.
Routing tables based classifier
CONFIG_NET_CLS_ROUTE4
@@ -8319,8 +9404,8 @@
This code is also available as a module called cls_route.o ( = code
which can be inserted in and removed from the running kernel
- whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
Firewall based classifier
CONFIG_NET_CLS_FW
@@ -8329,8 +9414,8 @@
This code is also available as a module called cls_fw.o ( = code
which can be inserted in and removed from the running kernel
- whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
U32 classifier
CONFIG_NET_CLS_U32
@@ -8339,8 +9424,8 @@
This code is also available as a module called cls_u32.o ( = code
which can be inserted in and removed from the running kernel
- whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
Special RSVP classifier
CONFIG_NET_CLS_RSVP
@@ -8353,8 +9438,8 @@
This code is also available as a module called cls_rsvp.o ( = code
which can be inserted in and removed from the running kernel
- whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
Special RSVP classifier for IPv6
CONFIG_NET_CLS_RSVP6
@@ -8368,15 +9453,8 @@
This code is also available as a module called cls_rsvp6.o ( = code
which can be inserted in and removed from the running kernel
- whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt
-
-#
-# Traffic policing (needed for in/egress)
-# CONFIG_NET_CLS_POLICE
-###
-### Some expert please fill these in
-###
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
Network code profiler
CONFIG_NET_PROFILE
@@ -8405,10 +9483,10 @@
CONFIG_HOSTESS_SV11
This is a network card for low speed synchronous serial links, at
up to 256Kbps. It supports both PPP and Cisco HDLC.
-
+
At this point, the driver can only be compiled as a module.
-COSA/SRP sync serial boards support
+COSA/SRP sync serial board support
CONFIG_COSA
This is a driver for COSA and SRP synchronous serial boards. These
boards allow to connect synchronous serial devices (for example
@@ -8419,59 +9497,60 @@
To actually use the COSA or SRP board, you will need user-space
utilities for downloading the firmware to the cards and to set them
- up. Look at the http://www.fi.muni.cz/~kas/cosa/ for more
+ up. Look at the <http://www.fi.muni.cz/~kas/cosa/> for more
information about the cards (including the pointer to the user-space
utilities). You can also read the comment at the top of the
- drivers/net/cosa.c for details about the cards and the driver
+ <file:drivers/net/cosa.c> for details about the cards and the driver
itself.
The driver will be compiled as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called cosa.o. For general information about
- modules read Documentation/modules.txt.
+ modules read <file:Documentation/modules.txt>.
-Etinc PCISYNC serial boards support
+Etinc PCISYNC serial board support
CONFIG_DSCC4
This is a driver for Etinc PCISYNC boards based on the Infineon
(ex. Siemens) DSCC4 chipset. It is supposed to work with the four
- ports card. Take a look at http://www.cogenit.fr/dscc4
+ ports card. Take a look at <http://www.cogenit.fr/dscc4>
for further informations about the driver and his configuration.
The driver will be compiled as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called dscc4.o. For general information about
- modules read Documentation/modules.txt.
+ modules read <file:Documentation/modules.txt>.
-Lan Media sync serial boards support
+LanMedia Corp. serial boards (SSI/V.35, T1/E1, HSSI, T3)
CONFIG_LANMEDIA
- This is a driver for the following Lan Media family of serial boards.
-
+ This is a driver for the following Lan Media family of serial
+ boards.
+
LMC 1000 board allows you to connect synchronous serial devices (for
example base-band modems, or any other device with the X.21, V.24,
V.35 or V.36 interface) to your Linux box.
-
+
LMC 1200 with on board DSU board allows you to connect your Linux
box dirrectly to a T1 or E1 circuit.
-
- LMC 5200 board provides a HSSI interface capable of runnig up to
+
+ LMC 5200 board provides a HSSI interface capable of running up to
52 mbits per second.
-
+
LMC 5245 board connects directly to a T3 circuit saving the
additional external hardware.
-
+
To change setting such as syncPPP vs cisco HDLC or clock source you
- will need lmcctl. It it available at ftp.lanmedia.com.
-
+ will need lmcctl. It is available at <ftp://ftp.lanmedia.com>.
+
This code is also available as a module called lmc.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
Fibre Channel driver support
CONFIG_NET_FC
Fibre Channel is a high speed serial protocol mainly used to connect
large storage devices to the computer; it is compatible with and
- intended to replace SCSI.
+ intended to replace SCSI.
If you intend to use Fibre Channel, you need to have a Fibre channel
adaptor card in your computer; say Y here and to the driver for your
@@ -8485,9 +9564,9 @@
The driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called iph5526.o. For general information about
- modules read Documentation/modules.txt.
-
-Red Creek Hardware VPN (EXPERIMENTAL)
+ modules read <file:Documentation/modules.txt>.
+
+Red Creek Hardware VPN
CONFIG_RCPCI
This is a driver for hardware which provides a Virtual Private
Network (VPN). Say Y if you have it.
@@ -8495,19 +9574,28 @@
This code is also available as a module called rcpci.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
-
-SBNI12-xx support
+ here and read <file:Documentation/modules.txt>.
+
+Granch SBNI12 Leased Line adapter driver
CONFIG_SBNI
This is a driver for ISA SBNI12-xx cards which are low cost
alternatives to leased line modems. Say Y if you want to insert
the driver into the kernel or say M to compile it as a module (the
- module will be called sbni.o).
-
- You can find more information and last versions of drivers and
- utilities at http://www.granch.ru . If you have any question you
+ module will be called sbni.o).
+
+ You can find more information and last versions of drivers and
+ utilities at <http://www.granch.ru>. If you have any question you
can send email to sbni@granch.ru.
-
+
+ Say N if unsure.
+
+SBNI Adapters Multiline feature
+CONFIG_SBNI_MULTILINE
+ Schedule traffic for some parallel lines, via SBNI12 adapters.
+ If you have two computers connected with two parallel lines it's
+ possible to increase transfer rate nearly twice. You should have
+ a program named 'sbniconfig' to configure adapters.
+
Say N if unsure.
WAN router drivers
@@ -8519,27 +9607,26 @@
Router".
You will need the wan-tools package which is available from
- ftp://ftp.sangoma.com . Read Documentation/networking/wan-router.txt
- for more information.
+ <ftp://ftp.sangoma.com>. Read
+ <file:Documentation/networking/wan-router.txt> for more information.
Note that the answer to this question won't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all
the questions about WAN router drivers. If unsure, say N.
Sangoma WANPIPE(tm) multiprotocol cards
CONFIG_VENDOR_SANGOMA
+ WANPIPE from Sangoma Technologies Inc. (<http://www.sangoma.com>)
+ is a family of intelligent multiprotocol WAN adapters with data
+ transfer rates up to 4Mbps. They are also known as Synchronous
+ Data Link Adapters (SDLA) and are designated as S514-PCI or
+ S508-ISA. These cards support
+
+ - X.25, Frame Relay, PPP, Cisco HDLC protocols.
+
+ - API support for protocols like HDLC (LAPB),
+ HDLC Streaming, X.25, Frame Relay and BiSync.
- WANPIPE from Sangoma Technologies Inc. (http://www.sangoma.com)
- is a family of intelligent multiprotocol WAN adapters with data
- transfer rates up to 4Mbps. They are also known as Synchronous
- Data Link Adapters (SDLA) and are designated as S514-PCI or S508-ISA.
- These cards support
-
- - X.25, Frame Relay, PPP, Cisco HDLC protocols.
-
- - API support for protocols like HDLC (LAPB),
- HDLC Streaming, X.25, Frame Relay and BiSync.
-
- Ethernet Bridging over Frame Relay protocol.
- MULTILINK PPP
@@ -8547,32 +9634,32 @@
- Async PPP (Modem Dialup)
If you have one or more of these cards, say M to this option; you
- may then also want to read the file
- Documentation/networking/wanpipe.txt. The next questions will ask
- you about the protocols you want the driver to support.
+ may then also want to read the file
+ <file:Documentation/networking/wanpipe.txt>. The next questions
+ will ask you about the protocols you want the driver to support.
The driver will be compiled as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called wanpipe.o. For general information about
- modules read Documentation/modules.txt.
+ The module will be called wanpipe.o. For general information about
+ modules read <file:Documentation/modules.txt>.
WANPIPE X.25 support
CONFIG_WANPIPE_X25
Say Y to this option if you are planning to connect a WANPIPE card
to an X.25 network. Note, this feature also includes the X.25 API
support used to develope custom applications over the X.25 protocol.
- If you say N, the X.25 support will not be included in the driver.
+ If you say N, the X.25 support will not be included in the driver.
The X.25 option is supported on S514-PCI and S508-ISA cards.
WANPIPE Frame Relay support
CONFIG_WANPIPE_FR
Say Y to this option if you are planning to connect a WANPIPE card
- to a frame relay network, or use frame relay API to develope
- custom applications over the Frame Relay protocol.
+ to a frame relay network, or use frame relay API to develope
+ custom applications over the Frame Relay protocol.
This feature also contains the Ethernet Bridging over Frame Relay,
- where a WANPIPE frame relay link can be directly connected to the Linux
- kernel bridge. If you say N, the frame relay support will
- not be included in the driver. The Frame Relay option is
+ where a WANPIPE frame relay link can be directly connected to the
+ Linux kernel bridge. If you say N, the frame relay support will
+ not be included in the driver. The Frame Relay option is
supported on S514-PCI and S508-ISA cards.
WANPIPE PPP support
@@ -8582,70 +9669,71 @@
the PPP support will not be included in the driver. The PPP option
is supported on S514-PCI/S508-ISA cards.
-WANPIPE MultiPort PPP support
+WANPIPE Multi-Port PPP support
CONFIG_WANPIPE_MULTPPP
Say Y to this option if you are planning to connect a WANPIPE card
- to a leased line using Point-to-Point protocol (PPP). Note, the
- MultiPort PPP uses the Linux Kernel SyncPPP protocol over the Sangoma
- HDLC Streaming adapter. In this case each Sangoma adapter port
- can support an independent PPP connection. For example, a single
- Quad-Port PCI adapter can support up to four independent
- PPP links. If you say N,the PPP support will not be included
- in the driver. The PPP option is supported on S514-PCI/S508-ISA cards.
-
+ to a leased line using Point-to-Point protocol (PPP). Note, the
+ MultiPort PPP uses the Linux Kernel SyncPPP protocol over the
+ Sangoma HDLC Streaming adapter. In this case each Sangoma adapter
+ port can support an independent PPP connection. For example, a
+ single Quad-Port PCI adapter can support up to four independent
+ PPP links. If you say N,the PPP support will not be included in the
+ driver. The PPP option is supported on S514-PCI/S508-ISA cards.
+
WANPIPE Cisco HDLC support
CONFIG_WANPIPE_CHDLC
Say Y to this option if you are planning to connect a WANPIPE card
to a leased line using the Cisco HDLC protocol. This now supports
- Dual Port Cisco HDLC on the S514-PCI/S508-ISA cards.
- This support also allows user to build applications using the
- HDLC streaming API.
-
+ Dual Port Cisco HDLC on the S514-PCI/S508-ISA cards.
+ This support also allows user to build applications using the
+ HDLC streaming API.
+
CHDLC Streaming driver also supports MULTILINK PPP
support that can bind multiple WANPIPE T1 cards into
a single logical channel.
-
- If you say N, the Cisco HDLC support and
- HDLC streaming API and MULTILINK PPP will not be
+
+ If you say N, the Cisco HDLC support and
+ HDLC streaming API and MULTILINK PPP will not be
included in the driver.
-MultiGate/COMX support
+MultiGate (COMX) synchronous serial board support
CONFIG_COMX
Say Y if you want to use any board from the MultiGate (COMX) family.
These boards are synchronous serial adapters for the PC,
manufactured by ITConsult-Pro Co, Hungary.
- Read linux/Documentation/networking/comx.txt for help on configuring
- and using COMX interfaces. Further info on these cards can be found
- at http://www.itc.hu or <info@itc.hu>.
+ Read <file:Documentation/networking/comx.txt> for help on
+ configuring and using COMX interfaces. Further info on these cards
+ can be found at <http://www.itc.hu> or <info@itc.hu>.
You must say Y to "/proc file system support" (CONFIG_PROC_FS) to
use this driver.
If you want to compile this as a module, say M and read
- Documentation/modules.txt. The module will be called comx.o.
+ <file:Documentation/modules.txt>. The module will be called comx.o.
-COMX/CMX/HiCOMX board support
+Support for COMX/CMX/HiCOMX boards
CONFIG_COMX_HW_COMX
Hardware driver for the 'CMX', 'COMX' and 'HiCOMX' boards from the
- MultiGate family. Say Y if you have one of these.
+ MultiGate family. Say Y if you have one of these.
You will need additional firmware to use these cards, which are
- downloadable from ftp://ftp.itc.hu/.
+ downloadable from <ftp://ftp.itc.hu/>.
If you want to compile this as a module, say M and read
- Documentation/modules.txt. The module will be called comx-hw-comx.o.
+ <file:Documentation/modules.txt>. The module will be called
+ comx-hw-comx.o.
-LoCOMX board support
+Support for LoCOMX board
CONFIG_COMX_HW_LOCOMX
Hardware driver for the 'LoCOMX' board from the MultiGate family.
Say Y if you have a board like this.
If you want to compile this as a module, say M and read
- Documentation/modules.txt. The module will be called
+ <file:Documentation/modules.txt>. The module will be called
comx-hw-locomx.o.
-MixCOM board support
+Support for MixCOM board
CONFIG_COMX_HW_MIXCOM
Hardware driver for the 'MixCOM' board from the MultiGate family.
Say Y if you have a board like this.
@@ -8655,63 +9743,63 @@
configuration. The ISDN interface of this card is Teles 16.3
compatible, you should enable it in the ISDN configuration menu. The
driver for the flash ROM of this card is available separately on
- ftp://ftp.itc.hu/.
+ <ftp://ftp.itc.hu/>.
If you want to compile this as a module, say M and read
- Documentation/modules.txt. The module will be called
+ <file:Documentation/modules.txt>. The module will be called
comx-hw-mixcom.o.
-i810 TCO support
+i810 TCO timer/watchdog support
CONFIG_I810_TCO
Hardware driver for the TCO timer built into the Intel i810 and i815
- chipset family. The TCO (Total Cost of Ownership) timer is a watchdog
- timer that will reboot the machine after it's second expiration. The
- expiration time can be configured by commandline argument
- "i810_margin=<n>" where <n> is the counter initial value. It is
- decremented every 0.6 secs, the default is 50 which gives a timeout
- of 30 seconds and one minute until reset.
+ chipset family. The TCO (Total Cost of Ownership) timer is a
+ watchdog timer that will reboot the machine after its second
+ expiration. The expiration time can be configured by commandline
+ argument "i810_margin=<n>" where <n> is the counter initial value.
+ It is decremented every 0.6 secs, the default is 50 which gives a
+ timeout of 30 seconds and one minute until reset.
On some motherboards the driver may fail to reset the chipset's
- NO_REBOOT flag which prevents the watchdog from rebooting the machine.
- If this is the case you will get a kernel message like
+ NO_REBOOT flag which prevents the watchdog from rebooting the
+ machine. If this is the case you will get a kernel message like
"i810tco init: failed to reset NO_REBOOT flag".
If you want to compile this as a module, say M and read
- Documentation/modules.txt. The module will be called
+ <file:Documentation/modules.txt>. The module will be called
i810-tco.o.
-MultiGate Cisco-HDLC and synchronous PPP protocol support
+Support for HDLC and syncPPP protocols on MultiGate boards
CONFIG_COMX_PROTO_PPP
Cisco-HDLC and synchronous PPP protocol driver for all MultiGate
boards. Say Y if you want to use either protocol on your MultiGate
boards.
If you want to compile this as a module, say M and read
- Documentation/modules.txt. The module will be called
+ <file:Documentation/modules.txt>. The module will be called
comx-proto-ppp.o.
-MultiGate LAPB protocol support
+Support for LAPB protocol on MultiGate boards
CONFIG_COMX_PROTO_LAPB
- LAPB protocol driver for all MultiGate boards. Say Y if you
+ LAPB protocol driver for all MultiGate boards. Say Y if you
want to use this protocol on your MultiGate boards.
If you want to compile this as a module, say M and read
- Documentation/modules.txt. The module will be called
+ <file:Documentation/modules.txt>. The module will be called
comx-proto-lapb.o.
-MultiGate Frame Relay protocol support
+Support for Frame Relay on MultiGate boards
CONFIG_COMX_PROTO_FR
- Frame Relay protocol driver for all MultiGate boards. Say Y if you
+ Frame Relay protocol driver for all MultiGate boards. Say Y if you
want to use this protocol on your MultiGate boards.
If you want to compile this as a module, say M and read
- Documentation/modules.txt. The module will be called
+ <file:Documentation/modules.txt>. The module will be called
comx-proto-fr.o.
-Cyclom 2X(tm) multiprotocol cards (EXPERIMENTAL)
+Cyclom 2X(tm) multiprotocol cards
CONFIG_CYCLADES_SYNC
- Cyclom 2X from Cyclades Corporation (http://www.cyclades.com and
- http://www.cyclades.com.br) is an intelligent multiprotocol WAN
+ Cyclom 2X from Cyclades Corporation (<http://www.cyclades.com> and
+ <http://www.cyclades.com.br)> is an intelligent multiprotocol WAN
adapter with data transfer rates up to 512 Kbps. These cards support
the X.25 and SNA related protocols. If you have one or more of these
cards, say Y to this option. The next questions will ask you about
@@ -8719,10 +9807,11 @@
supported).
While no documentation is available at this time please grab the
- wanconfig tarball in http://www.conectiva.com.br/~acme/cycsyn-devel
- (with minor changes to make it compile with the current wanrouter
- include files; efforts are being made to use the original package
- available at ftp://ftp.sangoma.com ).
+ wanconfig tarball in
+ <http://www.conectiva.com.br/~acme/cycsyn-devel> (with minor changes
+ to make it compile with the current wanrouter include files; efforts
+ are being made to use the original package available at
+ <ftp://ftp.sangoma.com>).
Feel free to contact me or the cycsyn-devel mailing list at
acme@conectiva.com.br and cycsyn-devel@bazar.conectiva.com.br for
@@ -8732,12 +9821,12 @@
The driver will be compiled as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called cyclomx.o. For general information about
- modules read Documentation/modules.txt.
+ modules read <file:Documentation/modules.txt>.
Cyclom 2X X.25 support
CONFIG_CYCLOMX_X25
Say Y to this option if you are planning to connect a Cyclom 2X card
- to an X.25 network.
+ to an X.25 network.
If you say N, the X.25 support will not be included in the driver
(saves about 11 KB of kernel memory).
@@ -8747,41 +9836,69 @@
Say Y to this option if your Linux box contains a WAN card supported
by this driver and you are planning to connect the box to a WAN
( = Wide Area Network). You will need supporting software from
- http://hq.pm.waw.pl/hdlc/.
+ <http://hq.pm.waw.pl/hdlc/>.
Generic HDLC driver currently supports raw HDLC, Cisco HDLC, Frame
Relay, synchronous Point-to-Point Protocol (PPP) and X.25.
If unsure, say N here.
-Synchronous Point-to-Point Protocol (PPP)
+Raw HDLC support
+CONFIG_HDLC_RAW
+ Say Y to this option if you want generic HDLC driver to support
+ raw HDLC over WAN (Wide Area Network) connections.
+
+ If unsure, say N here.
+
+Cisco HDLC support
+CONFIG_HDLC_CISCO
+ Say Y to this option if you want generic HDLC driver to support
+ Cisco HDLC over WAN (Wide Area Network) connections.
+
+ If unsure, say N here.
+
+Frame-Relay HDLC support
+CONFIG_HDLC_FR
+ Say Y to this option if you want generic HDLC driver to support
+ Frame-Relay protocol over WAN (Wide Area Network) connections.
+
+ If unsure, say N here.
+
+Frame-Relay bridging support
+CONFIG_HDLC_FR_BRIDGE
+ Say Y to this option if you want generic HDLC driver to support
+ bridging LAN frames over Frame-Relay links.
+
+ If unsure, say N here.
+
+Synchronous Point-to-Point Protocol (PPP) support
CONFIG_HDLC_PPP
Say Y to this option if you want generic HDLC driver to support
PPP over WAN (Wide Area Network) connections.
If unsure, say N here.
-CCITT X.25 protocol
+CCITT X.25 over HDLC support
CONFIG_HDLC_X25
Say Y to this option if you want generic HDLC driver to support
X.25 protocol over WAN (Wide Area Network) connections.
If unsure, say N here.
-SDL RISCom/N2 driver
+SDL RISCom/N2 support
CONFIG_N2
This driver is for RISCom/N2 single or dual channel ISA cards
- made by SDL Communications Inc. If you have such a card,
- say Y here and see http://hq.pm.waw.pl/pub/hdlc/
+ made by SDL Communications Inc. If you have such a card,
+ say Y here and see <http://hq.pm.waw.pl/pub/hdlc/>.
Note that N2csu and N2dds cards are not supported by this driver.
If unsure, say N here.
-Moxa C101 driver
+Moxa C101 support
CONFIG_C101
This driver is for C101 SuperSync ISA cards made by Moxa
Technologies Co., Ltd. If you have such a card,
- say Y here and see http://hq.pm.waw.pl/pub/hdlc/
+ say Y here and see <http://hq.pm.waw.pl/pub/hdlc/>
If unsure, say N here.
@@ -8803,21 +9920,21 @@
If your Linux machine will be connected to an Ethernet and you have
an Ethernet network interface card (NIC) installed in your computer,
say Y here and read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . You will then also have
+ <http://www.linuxdoc.org/docs.html#howto>. You will then also have
to say Y to the driver for your particular NIC.
Note that the answer to this question won't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all
the questions about Ethernet network cards. If unsure, say N.
Western Digital/SMC cards
CONFIG_NET_VENDOR_SMC
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all
the questions about Western Digital cards. If you say Y, you will be
asked for your specific card in the following questions.
@@ -8825,32 +9942,32 @@
CONFIG_WD80x3
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called wd.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called wd.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
SMC Ultra MCA support
CONFIG_ULTRAMCA
If you have a network (Ethernet) card of this type and are running
an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
- available from http://www.linuxdoc.org/docs.html#howto .
+ available from <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called smc-mca.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called smc-mca.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
SMC Ultra support
CONFIG_ULTRA
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
-
+ <http://www.linuxdoc.org/docs.html#howto>.
+
Important: There have been many reports that, with some motherboards
mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
such as some BusLogic models) causes corruption problems with many
@@ -8860,44 +9977,44 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called smc-ultra.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called smc-ultra.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt> as
+ well as <file:Documentation/networking/net-modules.txt>.
SMC Ultra32 EISA support
CONFIG_ULTRA32
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called smc-ultra32.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt as well
- as Documentation/networking/net-modules.txt.
+ The module will be called smc-ultra32.o. If you want to compile it
+ as a module, say M here and read <file:Documentation/modules.txt> as
+ well as <file:Documentation/networking/net-modules.txt>.
-SMC 9194 Support
+SMC 9194 support
CONFIG_SMC9194
This is support for the SMC9xxx based Ethernet cards. Choose this
option if you have a DELL laptop with the docking station, or
- another SMC9192/9194 based chipset. Say Y if you want it compiled
+ another SMC9192/9194 based chipset. Say Y if you want it compiled
into the kernel, and read the file
- Documentation/networking/smc9.txt and the Ethernet-HOWTO, available
- from http://www.linuxdoc.org/docs.html#howto .
+ <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
+ available from <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
- inserted in and removed from the running kernel whenever you
- want). The module will be called smc9194.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt as
- well as Documentation/networking/net-modules.txt.
+ inserted in and removed from the running kernel whenever you want).
+ The module will be called smc9194.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
-PCI NE2000 support
+PCI NE2000 and clones support
CONFIG_NE2K_PCI
This driver is for NE2000 compatible PCI cards. It will not work
with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
support" below). If you have a PCI NE2000 network (Ethernet) card,
say Y and read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver also works for the following NE2000 clone cards:
RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
@@ -8906,64 +10023,64 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called ne2k-pci.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called ne2k-pci.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt> as
+ well as <file:Documentation/networking/net-modules.txt>.
Racal-Interlan (Micom) NI cards
CONFIG_NET_VENDOR_RACAL
If you have a network (Ethernet) card belonging to this class, such
as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
- available from http://www.linuxdoc.org/docs.html#howto .
+ available from <http://www.linuxdoc.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all
the questions about NI cards. If you say Y, you will be asked for
your specific card in the following questions.
-NI5010 support (EXPERIMENTAL)
+NI5010 support
CONFIG_NI5010
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . Note that this is still
+ <http://www.linuxdoc.org/docs.html#howto>. Note that this is still
experimental code.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called ni5010.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called ni5010.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
NI5210 support
CONFIG_NI52
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called ni52.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called ni52.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
NI6510 support
CONFIG_NI65
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called ni65.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called ni65.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
RealTek RTL-8139C+ 10/100 PCI Fast Ethernet Adapter support
CONFIG_8139CP
This is a driver for the Fast Ethernet PCI network cards based on
the RTL8139C+ chips. If you have one of those, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
@@ -8974,21 +10091,23 @@
CONFIG_8139TOO
This is a driver for the Fast Ethernet PCI network cards based on
the RTL8139 chips. If you have one of those, say Y and read
- Documentation/networking/8139too.txt as well as the Ethernet-HOWTO,
- available from http://www.linuxdoc.org/docs.html#howto .
+ <file:Documentation/networking/8139too.txt> as well as the
+ Ethernet-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called 8139too.o.
+ say M here and read <file:Documentation/modules.txt>. This is
+ recommended. The module will be called 8139too.o.
Use PIO instead of MMIO
CONFIG_8139TOO_PIO
This instructs the driver to use programmed I/O ports (PIO) instead
- of PCI shared memory (MMIO). This can possibly solve some problems in
- case your mainboard has memory consistency issues. If unsure, say N.
+ of PCI shared memory (MMIO). This can possibly solve some problems
+ in case your mainboard has memory consistency issues. If unsure,
+ say N.
-Support for automatic channel equalization (EXPERIMENTAL)
+Support for automatic channel equalization
CONFIG_8139TOO_TUNE_TWISTER
This implements a function which might come in handy in case you are
using low quality on long cabling. It tries to match the transceiver
@@ -8998,40 +10117,40 @@
Support for older RTL-8129/8130 boards
CONFIG_8139TOO_8129
This enables support for the older and uncommon RTL-8129 and
- RTL-8130 chips, which support MII via an external transceiver, instead
- of an internal one. Disabling this option will save some memory
- by making the code size smaller. If unsure, say Y.
+ RTL-8130 chips, which support MII via an external transceiver,
+ instead of an internal one. Disabling this option will save some
+ memory by making the code size smaller. If unsure, say Y.
-SiS 900 PCI Fast Ethernet Adapter support
+SiS 900/7016 PCI Fast Ethernet Adapter support
CONFIG_SIS900
This is a driver for the Fast Ethernet PCI network cards based on
the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
- SiS 630 and SiS 540 chipsets. If you have one of those, say Y and
+ SiS 630 and SiS 540 chipsets. If you have one of those, say Y and
read the Ethernet-HOWTO, available at
- http://www.linuxdoc.org/docs.html#howto . Please read
- Documentation/networking/sis900.txt and comments at the beginning of
- drivers/net/sis900.c for more information.
+ <http://www.linuxdoc.org/docs.html#howto>. Please read
+ <file:Documentation/networking/sis900.txt> and comments at the
+ beginning of <file:drivers/net/sis900.c> for more information.
This driver also supports AMD 79C901 HomePNA so that you can use
your phone line as a network cable.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called sis900.o.
+ say M here and read <file:Documentation/modules.txt>. This is
+ recommended. The module will be called sis900.o.
Packet Engines Yellowfin Gigabit-NIC / Symbios 53c885 support
CONFIG_YELLOWFIN
Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
used by the Beowulf Linux cluster project. See
- http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html for more
+ <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
information about this driver in particular and Beowulf in general.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called yellowfin.o.
+ say M here and read <file:Documentation/modules.txt>. This is
+ recommended. The module will be called yellowfin.o.
General Instruments Surfboard 1000
CONFIG_NET_SB1000
@@ -9044,29 +10163,29 @@
At present this driver only compiles as a module, so say M here if
you have this card. The module will be called sb1000.o. Then read
- Documentation/networking/README.sb1000 for information on how to use
- this module, as it needs special ppp scripts for establishing a
- connection. Further documentation and the necessary scripts can be
+ <file:Documentation/networking/README.sb1000> for information on how
+ to use this module, as it needs special ppp scripts for establishing
+ a connection. Further documentation and the necessary scripts can be
found at:
- http://www.jacksonville.net/~fventuri/
- http://home.adelphia.net/~siglercm/sb1000.html
- http://linuxpower.cx/~cable/
+ <http://www.jacksonville.net/~fventuri/>
+ <http://home.adelphia.net/~siglercm/sb1000.html>
+ <http://linuxpower.cx/~cable/>
If you don't have this card, of course say N.
-Adaptec Starfire support (EXPERIMENTAL)
+Adaptec Starfire support
CONFIG_ADAPTEC_STARFIRE
Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
adapter. The DuraLAN chip is used on the 64 bit PCI boards from
Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
driver.
-
+
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called starfire.o.
-
+ say M here and read <file:Documentation/modules.txt>. This is
+ recommended. The module will be called starfire.o.
+
Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support
CONFIG_ACENIC
Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
@@ -9078,16 +10197,16 @@
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called acenic.o.
+ say M here and read <file:Documentation/modules.txt>. This is
+ recommended. The module will be called acenic.o.
-Omit support for older Tigon I based AceNICs
+Omit support for old Tigon I based AceNICs
CONFIG_ACENIC_OMIT_TIGON_I
Say Y here if you only have Tigon II based AceNICs and want to leave
out support for the older Tigon I based cards which are no longer
being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
- version)). This will reduce the size of the driver object by
- app. 100KB. If you are not sure whether your card is a Tigon I or a
+ version)). This will reduce the size of the driver object by
+ app. 100KB. If you are not sure whether your card is a Tigon I or a
Tigon II, say N here.
The safe and default value for this is N.
@@ -9107,148 +10226,170 @@
The driver also supports the following adapters from Allied Telesyn:
- AT2970...
- The dual link adapters support a link-failover feature.
- Read Documentation/networking/sk98lin.txt for information about
+ The dual link adapters support a link-failover feature. Read
+ <file:Documentation/networking/sk98lin.txt> for information about
optional driver parameters.
Questions concerning this driver may be addressed to:
linux@syskonnect.de
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called sk98lin.o.
+ say M here and read <file:Documentation/modules.txt>. This is
+ recommended. The module will be called sk98lin.o.
+
+Sun GEM support
+CONFIG_SUNGEM
+ Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
+ <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
MyriCOM Gigabit Ethernet support
CONFIG_MYRI_SBUS
- This driver supports MyriCOM Sbus gigabit ethernet cards.
+ This driver supports MyriCOM Sbus gigabit Ethernet cards.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called myri_sbus.o.
+ say M here and read <file:Documentation/modules.txt>. This is
+ recommended. The module will be called myri_sbus.o.
D-Link 2000-based Gigabit Ethernet support
CONFIG_DL2K
This driver supports D-Link 2000-based gigabit ethernet cards, which
includes
- D-Link DGE-550T Gigabit Ethernet Adapter.
- D-Link DL2000-based Gigabit Ethernet Adapter.
+ D-Link DGE-550T Gigabit Ethernet Adapter.
+ D-Link DL2000-based Gigabit Ethernet Adapter.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called dl2k.o.
+ say M here and read <file:Documentation/modules.txt>. This is
+ recommended. The module will be called dl2k.o.
AMD LANCE and PCnet (AT1500 and NE2100) support
CONFIG_LANCE
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . Some LinkSys cards are
+ <http://www.linuxdoc.org/docs.html#howto>. Some LinkSys cards are
of this type.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called lance.o.
+ say M here and read <file:Documentation/modules.txt>. This is
+ recommended. The module will be called lance.o.
SGI IOC3 Ethernet
CONFIG_SGI_IOC3_ETH
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
+
+National Semiconductor DP83902AV support
+CONFIG_STNIC
+ Support for cards based on the National Semiconductor DP83902AV
+ ST-NIC Serial Network Interface Controller for Twisted Pair. This
+ is a 10Mbit/sec Ethernet controller. Product overview and specs at
+ <http://www.national.com/pf/DP/DP83902A.html>.
+
+CompactFlash Connection Area
+CONFIG_CF_AREA5
+ If your board has "Directly Connected" CompactFlash, You should
+ select the area where your CF is connected to.
+
+ - "Area5" if CompactFlash is connected to Area 5 (0x14000000)
+ - "Area6" if it is connected to Area 6 (0x18000000)
+
+ "Area6" will work for most boards. For ADX, select "Area5".
3COM cards
CONFIG_NET_VENDOR_3COM
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all
the questions about 3COM cards. If you say Y, you will be asked for
your specific card in the following questions.
-3c501 support
+3c501 "EtherLink" support
CONFIG_EL1
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . Also, consider buying a
+ <http://www.linuxdoc.org/docs.html#howto>. Also, consider buying a
new card, since the 3c501 is slow, broken, and obsolete: you will
- have problems. Some people suggest to ping ("man ping") a nearby
+ have problems. Some people suggest to ping ("man ping") a nearby
machine every minute ("man cron") when using this card.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called 3c501.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called 3c501.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
-3c503 support
+3c503 "EtherLink II" support
CONFIG_EL2
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called 3c503.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called 3c503.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
-3c505 support
+3c505 "EtherLink Plus" support
CONFIG_ELPLUS
Information about this network (Ethernet) card can be found in
- Documentation/networking/3c505.txt. If you have a card of this type,
- say Y and read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <file:Documentation/networking/3c505.txt>. If you have a card of
+ this type, say Y and read the Ethernet-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
- 3c505.o.
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called 3c505.o.
-3c507 support (EXPERIMENTAL)
+3c507 (EtherLink 16) support
CONFIG_EL16
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called 3c507.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called 3c507.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
-3c523 support
+3c523 "EtherlinkMC" support
CONFIG_ELMC
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called 3c523.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called 3c523.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
-3c527 support
+3c527 "EtherLink/MC 32" support
CONFIG_ELMC_II
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called 3c527.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called 3c527.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
-3c509/3c579 support
+3c509/3c529 (MCA)/3c579 "EtherLink III" support
CONFIG_EL3
If you have a network (Ethernet) card belonging to the 3Com
EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
- from http://www.linuxdoc.org/docs.html#howto .
+ from <http://www.linuxdoc.org/docs.html#howto>.
If your card is not working you may need to use the DOS
setup disk to disable Plug & Play mode, and to select the default
@@ -9256,23 +10397,23 @@
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
- 3c509.o.
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called 3c509.o.
3c515 ISA Fast EtherLink
CONFIG_3C515
If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
network card, say Y and read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
- 3c515.o.
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called 3c515.o.
-3c59x/3c90x/3c575_Cardbus series "Vortex/Boomerang/Cyclone" support
+3c590/3c900 series (592/595/597) "Vortex/Boomerang/Cyclone" support
CONFIG_VORTEX
This option enables driver support for a large number of 10mbps and
10/100mbps EISA, PCI and PCMCIA 3Com network cards:
@@ -9283,15 +10424,16 @@
"Tornado" (3c905) PCI
"Hurricane" (3c555/3cSOHO) PCI
- If you have such a card, say Y and read the Ethernet-HOWTO, available
- from http://www.linuxdoc.org/docs.html#howto . More specific
- information is in Documentation/networking/vortex.txt and in the
- comments at the beginning of drivers/net/3c59x.c.
+ If you have such a card, say Y and read the Ethernet-HOWTO,
+ available from <http://www.linuxdoc.org/docs.html#howto>. More
+ specific information is in
+ <file:Documentation/networking/vortex.txt> and in the comments at
+ the beginning of <file:drivers/net/3c59x.c>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>.
Other ISA cards
CONFIG_NET_ISA
@@ -9299,19 +10441,20 @@
bus system (that's the way the cards talks to the other components
of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
Make sure you know the name of your card. Read the Ethernet-HOWTO,
- available from http://www.linuxdoc.org/docs.html#howto .
+ available from <http://www.linuxdoc.org/docs.html#howto>.
If unsure, say Y.
Note that the answer to this question doesn't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all
the remaining ISA network card questions. If you say Y, you will be
asked for your specific card in the following questions.
Generic ARCnet support
CONFIG_ARCNET
If you have a network card of this type, say Y and check out the
- (arguably) beautiful poetry in Documentation/networking/arcnet.txt.
+ (arguably) beautiful poetry in
+ <file:Documentation/networking/arcnet.txt>.
You need both this driver, and the driver for the particular ARCnet
chipset of your card. If you don't know, then it's probably a
@@ -9319,26 +10462,14 @@
support" below.
You might also want to have a look at the Ethernet-HOWTO, available
- from http://www.linuxdoc.org/docs.html#howto (even though ARCnet
+ from <http://www.linuxdoc.org/docs.html#howto>(even though ARCnet
is not really Ethernet).
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called arcnet.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
-
-Enable arc0e (ARCnet "ether-encap" packet format)
-CONFIG_ARCNET_ETH
- This allows you to use "Ethernet encapsulation" with your ARCnet
- card via the virtual arc0e device. You only need arc0e if you want
- to talk to nonstandard ARCnet software, specifically,
- DOS/Windows-style "NDIS" drivers. You do not need to say Y here to
- communicate with industry-standard RFC1201 implementations, like the
- arcether.com packet driver or most DOS/Windows ODI drivers. RFC1201
- is included automatically as the arc0 device. Please read the
- ARCnet documentation in Documentation/networking/arcnet.txt for more
- information about using arc0e and arc0s.
+ The module will be called arcnet.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
Enable old ARCNet packet format (RFC 1051)
CONFIG_ARCNET_1051
@@ -9350,33 +10481,48 @@
industry-standard RFC1201 implementations, like the arcether.com
packet driver or most DOS/Windows ODI drivers. RFC1201 is included
automatically as the arc0 device. Please read the ARCnet
- documentation in Documentation/networking/arcnet.txt for more
+ documentation in <file:Documentation/networking/arcnet.txt> for more
information about using arc0e and arc0s.
+Enable standard ARCNet packet format (RFC 1201)
+CONFIG_ARCNET_1201
+ This allows you to use RFC1201 with your ARCnet card via the virtual
+ arc0 device. You need to say Y here to communicate with
+ industry-standard RFC1201 implementations, like the arcether.com
+ packet driver or most DOS/Windows ODI drivers. Please read the
+ ARCnet documentation in <file:Documentation/networking/arcnet.txt>
+ for more information about using arc0.
+
+Enable raw mode packet interface
+CONFIG_ARCNET_RAW
+ ARCnet "raw mode" packet encapsulation, no soft headers. Unlikely
+ to work unless talking to a copy of the same Linux arcnet driver,
+ but perhaps marginally faster in that case.
+
ARCnet COM90xx (normal) chipset driver
CONFIG_ARCNET_COM90xx
This is the chipset driver for the standard COM90xx cards. If you
have always used the old ARCnet driver without knowing what type of
- card you had, this is probably the one for you.
+ card you had, this is probably the one for you.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called com90xx.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called com90xx.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
ARCnet COM90xx (IO mapped) chipset driver
CONFIG_ARCNET_COM90xxIO
This is the chipset driver for the COM90xx cards, using them in
IO-mapped mode instead of memory-mapped mode. This is slower than
the normal driver. Only use it if your card doesn't support shared
- memory.
+ memory.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called com90io.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called com90io.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
ARCnet COM90xx (RIM I) chipset driver
CONFIG_ARCNET_RIM_I
@@ -9387,197 +10533,198 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you
- want). The module will be called arc-rimi.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt as
- well as Documentation/networking/net-modules.txt.
+ want). The module will be called arc-rimi.o. If you want to compile
+ it as a module, say M here and read <file:Documentation/modules.txt>
+ as well as <file:Documentation/networking/net-modules.txt>.
ARCnet COM20020 chipset driver
CONFIG_ARCNET_COM20020
This is the driver for the new COM20020 chipset. It supports such
things as promiscuous mode, so packet sniffing is possible, and
- extra diagnostic information.
+ extra diagnostic information.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called com20020.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called com20020.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt> as
+ well as <file:Documentation/networking/net-modules.txt>.
Cabletron E21xx support
CONFIG_E2100
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called e2100.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called e2100.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
-CS89x0 support
+CS89x0 support (Daynaport CS and LC cards)
CONFIG_CS89x0
Support for CS89x0 chipset based Ethernet cards. If you have a
network (Ethernet) card of this type, say Y and read the
Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto as well as
- Documentation/networking/cs89x0.txt.
+ <http://www.linuxdoc.org/docs.html#howto> as well as
+ <file:Documentation/networking/cs89x0.txt>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
- cs89x.o.
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called cs89x.o.
-DEPCA support
+DEPCA, DE10x, DE200, DE201, DE202, DE422 support
CONFIG_DEPCA
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto as well as
- drivers/net/depca.c.
+ <http://www.linuxdoc.org/docs.html#howto> as well as
+ <file:drivers/net/depca.c>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called
depca.o.
-EtherWorks 3 support
+EtherWORKS 3 (DE203, DE204, DE205) support
CONFIG_EWRK3
This driver supports the DE203, DE204 and DE205 network (Ethernet)
cards. If this is for you, say Y and read
- Documentation/networking/ewrk3.txt in the kernel source as well as
- the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <file:Documentation/networking/ewrk3.txt> in the kernel source as
+ well as the Ethernet-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
- ewrk3.o.
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called ewrk3.o.
SEEQ8005 support
CONFIG_SEEQ8005
- This is a driver for the SEEQ 8005 network (Ethernet) card. If this
+ This is a driver for the SEEQ 8005 network (Ethernet) card. If this
is for you, read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
- ewrk3.o.
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called ewrk3.o.
AT1700/1720 support
CONFIG_AT1700
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
If you want to compile it as a module, say M here and read
- Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
- at1700.o.
+ <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called at1700.o.
FMV-181/182/183/184 support
CONFIG_FMV18X
If you have a Fujitsu FMV-181/182/183/184 network (Ethernet) card,
say Y and read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
If you use an FMV-183 or FMV-184 and it is not working, you may need
to disable Plug & Play mode of the card.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called fmv18x.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called fmv18x.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
-EtherExpress PRO support
+EtherExpressPro support/EtherExpress 10 (i82595) support
CONFIG_EEXPRESS_PRO
If you have a network (Ethernet) card of this type, say Y. This
- driver supports intel i82595{FX,TX} based boards. Note however
+ driver supports intel i82595{FX,TX} based boards. Note however
that the EtherExpress PRO/100 Ethernet card has its own separate
- driver. Please read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ driver. Please read the Ethernet-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called eepro.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called eepro.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
-EtherExpress support
+EtherExpress 16 support
CONFIG_EEXPRESS
If you have an EtherExpress16 network (Ethernet) card, say Y and
read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . Note that the Intel
+ <http://www.linuxdoc.org/docs.html#howto>. Note that the Intel
EtherExpress16 card used to be regarded as a very poor choice
because the driver was very unreliable. We now have a new driver
that should do better.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
- eexpress.o.
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called eexpress.o.
Packet Engines Hamachi GNIC-II support
CONFIG_HAMACHI
If you have a Gigabit Ethernet card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
- hamachi.o.
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called hamachi.o.
HP PCLAN+ (27247B and 27252A) support
CONFIG_HPLAN_PLUS
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called hp-plus.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called hp-plus.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
HP PCLAN (27245 and other 27xxx series) support
CONFIG_HPLAN
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called hp.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called hp.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
HP 10/100VG PCLAN (ISA, EISA, PCI) support
CONFIG_HP100
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
- hp100.o.
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called hp100.o.
NE2000/NE1000 support
CONFIG_NE2000
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . Many Ethernet cards
+ <http://www.linuxdoc.org/docs.html#howto>. Many Ethernet cards
without a specific driver are compatible with NE2000.
If you have a PCI NE2000 card however, say N here and Y to "PCI
@@ -9588,74 +10735,76 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called ne.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called ne.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
-National Semiconductor DP83810 series PCI Ethernet support
+National Semiconductor DP8381x series PCI Ethernet support
CONFIG_NATSEMI
This driver is for the National Semiconductor DP83810 series,
- including the 83815 chip.
- More specific information and updates are available from
- http://www.scyld.com/network/natsemi.html
+ which is used in cards from PureData, NetGear, Linksys
+ and others, including the 83815 chip.
+ More specific information and updates are available from
+ <http://www.scyld.com/network/natsemi.html>.
SK_G16 support
CONFIG_SK_G16
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
NE/2 (ne2000 MCA version) support
CONFIG_NE2_MCA
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called ne2.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called ne2.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
SKnet MCA support
CONFIG_SKMC
- These are Micro Channel ethernet adapters. You need to say Y to "MCA
- support" in order to use this driver. Supported cards are the SKnet
- Junior MC2 and the SKnet MC2(+). The driver automatically
+ These are Micro Channel Ethernet adapters. You need to say Y to "MCA
+ support" in order to use this driver. Supported cards are the SKnet
+ Junior MC2 and the SKnet MC2(+). The driver automatically
distinguishes between the two cards. Note that using multiple boards
- of different type hasn't been tested with this driver. Say Y if you
- have one of these ethernet adapters.
+ of different type hasn't been tested with this driver. Say Y if you
+ have one of these Ethernet adapters.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module is called sk_mca.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module is called sk_mca.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
IBM LAN Adapter/A support
CONFIG_IBMLANA
- This is a Micro Channel ethernet adapter. You need to set CONFIG_MCA
- to use this driver. It is both available as an in-kernel driver and
- as a module ( = code which can be inserted in and removed from the
- running kernel whenever you want). If you want to compile it as a module,
- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. If you plan to use more than
- one network card under linux, read the Multiple-Ethernet-mini-HOWTO,
- available from sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. The only
- currently supported card is the IBM LAN Adapter/A for Ethernet. It will
- both support 16K and 32K memory windows, however a 32K window gives
- a better security against packet losses. Usage of multiple boards with
- this driver should be possible, but has not been tested up to now due
- to lack of hardware.
+ This is a Micro Channel Ethernet adapter. You need to set
+ CONFIG_MCA to use this driver. It is both available as an in-kernel
+ driver and as a module ( = code which can be inserted in and removed
+ from the running kernel whenever you want). If you want to compile
+ it as a module, say M here and read <file:Documentation/modules.txt>
+ as well as <file:Documentation/networking/net-modules.txt>.
+ If you plan to use more than one network card under linux, read the
+ Multiple-Ethernet-mini-HOWTO, available from
+ <ftp://sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini>. The only
+ currently supported card is the IBM LAN Adapter/A for Ethernet. It
+ will both support 16K and 32K memory windows, however a 32K window
+ gives a better security against packet losses. Usage of multiple
+ boards with this driver should be possible, but has not been tested
+ up to now due to lack of hardware.
EISA, VLB, PCI and on board controllers
CONFIG_NET_PCI
This is another class of network cards which attach directly to the
bus. If you have one of those, say Y and read the Ethernet-HOWTO,
- available from http://www.linuxdoc.org/docs.html#howto .
+ available from <http://www.linuxdoc.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all
the questions about this class of network cards. If you say Y, you
will be asked for your specific card in the following questions. If
you are unsure, say Y.
@@ -9664,98 +10813,100 @@
CONFIG_PCNET32
If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
answer Y here and read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called pcnet32.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called pcnet32.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
Ansel Communications EISA 3200 support
CONFIG_AC3200
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called ac3200.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called ac3200.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
-Mylex EISA LNE390A/LNE390B support (EXPERIMENTAL)
+Mylex EISA LNE390A/LNE390B support
CONFIG_LNE390
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called lne390.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called lne390.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
Novell/Eagle/Microdyne NE3210 EISA support
CONFIG_NE3210
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . Note that this driver
+ <http://www.linuxdoc.org/docs.html#howto>. Note that this driver
will NOT WORK for NE3200 cards as they are completely different.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called ne3210.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called ne3210.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
Apricot Xen-II on board Ethernet
CONFIG_APRICOT
If you have a network (Ethernet) controller of this type, say Y and
read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt. The module will be called
- apricot.o.
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. The module will be
+ called apricot.o.
Generic DECchip & DIGITAL EtherWORKS PCI/EISA
CONFIG_DE4X5
This is support for the DIGITAL series of PCI/EISA Ethernet cards.
- These include the DE425, DE434, DE435, DE450 and DE500 models. If
+ These include the DE425, DE434, DE435, DE450 and DE500 models. If
you have a network card of this type, say Y and read the
Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . More specific
- information is contained in Documentation/networking/de4x5.txt.
+ <http://www.linuxdoc.org/docs.html#howto>. More specific
+ information is contained in
+ <file:Documentation/networking/de4x5.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called de4x5.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called de4x5.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
DECchip Tulip (dc21x4x) PCI support
CONFIG_TULIP
This driver is developed for the SMC EtherPower series Ethernet
- cards and also works with cards based on the DECchip
- 21040/21041/21140 (Tulip series) chips. Some LinkSys PCI cards are
- of this type. (If your card is NOT SMC EtherPower 10/100 PCI
+ cards and also works with cards based on the DECchip
+ 21040/21041/21140 (Tulip series) chips. Some LinkSys PCI cards are
+ of this type. (If your card is NOT SMC EtherPower 10/100 PCI
(smc9332dst), you can also try the driver for "Generic DECchip"
- cards, above. However, most people with a network card of this type
+ cards, above. However, most people with a network card of this type
will say Y here.) Do read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . More specific
- information is contained in Documentation/networking/tulip.txt.
+ <http://www.linuxdoc.org/docs.html#howto>. More specific
+ information is contained in
+ <file:Documentation/networking/tulip.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called tulip.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called tulip.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
-New Tulip bus configuration (EXPERIMENTAL)
-CONFIG_TULIP_MWI
+New Tulip bus configuration
+CONFIG_TULIP_MWI
This configures your Tulip card specifically for the card and
system cache line size type you are using.
@@ -9763,34 +10914,34 @@
If unsure, say N.
-Digi Intl. RightSwitch support
+Digi Intl. RightSwitch SE-X support
CONFIG_DGRS
This is support for the Digi International RightSwitch series of
PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
- models. If you have a network card of this type, say Y and read the
+ models. If you have a network card of this type, say Y and read the
Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . More specific
- information is contained in Documentation/networking/dgrs.txt.
+ <http://www.linuxdoc.org/docs.html#howto>. More specific
+ information is contained in <file:Documentation/networking/dgrs.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called dgrs.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called dgrs.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
-EtherExpress PRO/100 support
+EtherExpress Pro/100 support
CONFIG_EEPRO100
If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
card, say Y and read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called eepro100.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called eepro100.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt> as
+ well as <file:Documentation/networking/net-modules.txt>.
-Enable Power Management (EXPERIMENTAL)
+Enable Power Management
CONFIG_EEPRO100_PM
Many Intel EtherExpress PRO/100 PCI network cards are capable
of providing power management capabilities. To make use of these
@@ -9802,34 +10953,40 @@
It is recommended to say N here.
-ICL EtherTeam 16i/32 support (EXPERIMENTAL)
+Myson MTD-8xx PCI Ethernet support
+CONFIG_FEALNX
+ Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
+ cards. Specifications and data at
+ <http:www.myson.com.hk/mtd/datasheet>.
+
+ICL EtherTeam 16i/32 support
CONFIG_ETH16I
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called eth16i.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called eth16i.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
-TI ThunderLAN support (EXPERIMENTAL)
+TI ThunderLAN support
CONFIG_TLAN
If you have a PCI Ethernet network card based on the ThunderLAN chip
which is supported by this driver, say Y and read the
Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
Devices currently supported by this driver are Compaq Netelligent,
- Compaq NetFlex and Olicom cards. Please read the file
- Documentation/networking/tlan.txt for more details.
+ Compaq NetFlex and Olicom cards. Please read the file
+ <file:Documentation/networking/tlan.txt> for more details.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called tlan.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called tlan.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
Please email feedback to torben.mathiasen@compaq.com.
@@ -9840,131 +10997,164 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called via-rhine.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called via-rhine.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt> as
+ well as <file:Documentation/networking/net-modules.txt>.
-PCI DM9102(A)/DM9132/DM9801 support
+Davicom DM910x/DM980x support
CONFIG_DM9102
This driver is for DM9102(A)/DM9132/DM9801 compatible PCI cards from
- Davicom ( http://www.davicom.com.tw ). If you have such a network
- (Ethernet) card, say Y. Some information is contained in the file
- Documentation/networking/dmfe.txt.
-
+ Davicom (<http://www.davicom.com.tw>). If you have such a network
+ (Ethernet) card, say Y. Some information is contained in the file
+ <file:Documentation/networking/dmfe.txt>.
+
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called dmfe.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called dmfe.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
-Racal-Interlan EISA ES3210 support (EXPERIMENTAL)
+Racal-Interlan EISA ES3210 support
CONFIG_ES3210
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called es3210.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt as well as
- Documentation/networking/net-modules.txt.
+ The module will be called es3210.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/networking/net-modules.txt>.
SMC EtherPower II
CONFIG_EPIC100
This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
which is based on the SMC83c17x (EPIC/100).
More specific information and updates are available from
- http://www.scyld.com/network/epic100.html
+ <http://www.scyld.com/network/epic100.html>.
-SGI Seeq ethernet controller support
+DEC LANCE Ethernet controller support
+CONFIG_DECLANCE
+ This driver is for the series of Ethernet controllers produced by
+ DEC (now Compaq) based on the AMD Lance chipset, including the
+ DEPCA series. (This chipset is better known via the NE2100 cards.)
+
+SGI Seeq Ethernet controller support
CONFIG_SGISEEQ
Say Y here if you have an Seeq based Ethernet network card. This is
used in many Silicon Graphics machines.
-Sundance "Alta" PCI Ethernet support
+Sundance Alta PCI Ethernet support
CONFIG_SUNDANCE
This driver is for the Sundance "Alta" chip.
More specific information and updates are available from
- http://www.scyld.com/network/sundance.html
+ <http://www.scyld.com/network/sundance.html>.
+
+Sun3/Sun3x on-board LANCE support
+CONFIG_SUN3LANCE
+ Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
+ featured an AMD Lance 10Mbit Ethernet controller on board; say Y
+ here to compile in the Linux driver for this and enable Ethernet.
+ General Linux information on the Sun 3 and 3x series (now
+ discontinued) is at
+ <http://www.angelfire.com/ca2/tech68k/sun3.html>.
+
+ If you're not building a kernel for a Sun 3, say N.
+
+Sun3 on-board Intel 82586 support
+CONFIG_SUN3_82586
+ This driver enables support for the on-board Intel 82586 based
+ Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
+ that this driver does not support 82586-based adapters on additional
+ VME boards.
Winbond W89c840 PCI Ethernet support
CONFIG_WINBOND_840
This driver is for the Winbond W89c840 chip. It also works with
the TX9882 chip on the Compex RL100-ATX board.
More specific information and updates are available from
- http://www.scyld.com/network/drivers.html
+ <http://www.scyld.com/network/drivers.html>.
-Zenith Z-Note support (EXPERIMENTAL)
+Zenith Z-Note support
CONFIG_ZNET
The Zenith Z-Note notebook computer has a built-in network
(Ethernet) card, and this is the Linux driver for it. Note that the
IBM Thinkpad 300 is compatible with the Z-Note and is also supported
by this driver. Read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
+
+Philips SAA9730 Ethernet support
+CONFIG_LAN_SAA9730
+ The SAA9730 is a combined multimedia and peripheral controller used
+ in thin clients, Internet access terminals, and diskless
+ workstations.
+ See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
Pocket and portable adapters
CONFIG_NET_POCKET
Cute little network (Ethernet) devices which attach to the parallel
port ("pocket adapters"), commonly used with laptops. If you have
one of those, say Y and read the Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
If you want to plug a network (or some other) card into the PCMCIA
(or PC-card) slot of your laptop instead (PCMCIA is the standard for
credit card size extension cards used by all modern laptops), you
need the pcmcia-cs package (location contained in the file
- Documentation/Changes) and you can say N here.
+ <file:Documentation/Changes>) and you can say N here.
Laptop users should read the Linux Laptop home page at
- http://www.cs.utexas.edu/users/kharker/linux-laptop/ .
+ <http://www.cs.utexas.edu/users/kharker/linux-laptop/>.
Note that the answer to this question doesn't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all
the questions about this class of network devices. If you say Y, you
will be asked for your specific device in the following questions.
AT-LAN-TEC/RealTek pocket adapter support
CONFIG_ATP
This is a network (Ethernet) device which attaches to your parallel
- port. Read drivers/net/atp.c as well as the Ethernet-HOWTO,
- available from http://www.linuxdoc.org/docs.html#howto , if you
- want to use this. If you intend to use this driver, you should have
+ port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
+ available from <http://www.linuxdoc.org/docs.html#howto>, if you
+ want to use this. If you intend to use this driver, you should have
said N to the "Parallel printer support", because the two drivers
don't like each other.
If you want to compile this driver as a module however ( = code
which can be inserted in and removed from the running kernel
- whenever you want), say M here and read Documentation/modules.txt.
- The module will be called atp.o.
+ whenever you want), say M here and read
+ <file:Documentation/modules.txt>. The module will be called atp.o.
D-Link DE600 pocket adapter support
CONFIG_DE600
This is a network (Ethernet) device which attaches to your parallel
- port. Read Documentation/networking/DLINK.txt as well as the
+ port. Read <file:Documentation/networking/DLINK.txt> as well as the
Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto , if you want to use
+ <http://www.linuxdoc.org/docs.html#howto>, if you want to use
this. It is possible to have several devices share a single parallel
port and it is safe to compile the corresponding drivers into the
kernel.
If you want to compile this driver as a module however ( = code
which can be inserted in and removed from the running kernel
- whenever you want), say M here and read Documentation/modules.txt.
+ whenever you want), say M here and read
+ <file:Documentation/modules.txt>.
The module will be called de600.o.
D-Link DE620 pocket adapter support
CONFIG_DE620
This is a network (Ethernet) device which attaches to your parallel
- port. Read Documentation/networking/DLINK.txt as well as the
+ port. Read <file:Documentation/networking/DLINK.txt> as well as the
Ethernet-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto , if you want to use
+ <http://www.linuxdoc.org/docs.html#howto>, if you want to use
this. It is possible to have several devices share a single parallel
port and it is safe to compile the corresponding drivers into the
kernel.
If you want to compile this driver as a module however ( = code
which can be inserted in and removed from the running kernel
- whenever you want), say M here and read Documentation/modules.txt.
+ whenever you want), say M here and read
+ <file:Documentation/modules.txt>.
The module will be called de620.o.
Token Ring driver support
@@ -9975,41 +11165,41 @@
connected to such a Token Ring network and want to use your Token
Ring card under Linux, say Y here and to the driver for your
particular card below and read the Token-Ring mini-HOWTO, available
- from http://www.linuxdoc.org/docs.html#howto . Most people can
+ from <http://www.linuxdoc.org/docs.html#howto>. Most people can
say N here.
IBM Tropic chipset based adapter support
CONFIG_IBMTR
This is support for all IBM Token Ring cards that don't use DMA. If
you have such a beast, say Y and read the Token-Ring mini-HOWTO,
- available from http://www.linuxdoc.org/docs.html#howto .
+ available from <http://www.linuxdoc.org/docs.html#howto>.
Warning: this driver will almost definitely fail if more than one
- active Token Ring card is present.
+ active Token Ring card is present.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called ibmtr.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
IBM Olympic chipset PCI adapter support
CONFIG_IBMOL
- This is support for all non-Lanstreamer IBM PCI Token Ring Cards.
+ This is support for all non-Lanstreamer IBM PCI Token Ring Cards.
Specifically this is all IBM PCI, PCI Wake On Lan, PCI II, PCI II
Wake On Lan, and PCI 100/16/4 adapters.
If you have such an adapter, say Y and read the Token-Ring
mini-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called olympic.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt.
+ as a module, say M here and read <file:Documentation/modules.txt>.
- Also read the file Documentation/networking/olympic.txt or check the
+ Also read <file:Documentation/networking/olympic.txt> or check the
Linux Token Ring Project site for the latest information at
- http://www.linuxtr.net .
+ <http://www.linuxtr.net>.
IBM Lanstreamer chipset PCI adapter support
CONFIG_IBMLS
@@ -10017,12 +11207,12 @@
If you have such an adapter, say Y and read the Token-Ring
mini-HOWTO available via FTP (user:anonymous) from
- ftp://metalab.unc/edu/pub/Linux/docs/HOWTO.
+ <ftp://metalab.unc/edu/pub/Linux/docs/HOWTO>.
This driver is also available as a modules ( = code which can be
inserted in and removed from the running kernel whenever you want).
The modules will be called lanstreamer.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt.
+ as a module, say M here and read <file:Documentation/modules.txt>.
Generic TMS380 Token Ring ISA/PCI/MCA/EISA adapter support
CONFIG_TMS380TR
@@ -10037,15 +11227,15 @@
If you have such an adapter and would like to use it, say Y and
read the Token-Ring mini-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
- Also read the file Documentation/networking/tms380tr.txt or
- check http://www.auk.cx/tms380tr/ .
+ Also read the file <file:Documentation/networking/tms380tr.txt> or
+ check <http://www.auk.cx/tms380tr/>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called tms380tr.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt.
+ as a module, say M here and read <file:Documentation/modules.txt>.
Generic TMS380 PCI support
CONFIG_TMSPCI
@@ -10060,19 +11250,31 @@
This driver is available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called tmspci.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt.
+ as a module, say M here and read <file:Documentation/modules.txt>.
+
+Generic TMS380 ISA support
+CONFIG_TMSISA
+ This tms380 module supports generic TMS380-based ISA cards.
+
+ These cards are known to work:
+ - SysKonnect TR4/16 ISA (SK-4190)
+
+ This driver is available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ The module will be called tmsisa.o. If you want to compile it
+ as a module, say M here and read <file:Documentation/modules.txt>.
Madge Smart 16/4 PCI Mk2 support
CONFIG_ABYSS
- This tms380 module supports the Madge Smart 16/4 PCI Mk2
+ This tms380 module supports the Madge Smart 16/4 PCI Mk2
cards (51-02).
This driver is available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called abyss.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt.
+ as a module, say M here and read <file:Documentation/modules.txt>.
-Madge Smart 16/4 Ringode MicroChannel
+Madge Smart 16/4 Ringnode MicroChannel
CONFIG_MADGEMC
This tms380 module supports the Madge Smart 16/4 MC16 and MC32
MicroChannel adapters.
@@ -10080,9 +11282,9 @@
This driver is available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called madgemc.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt.
+ as a module, say M here and read <file:Documentation/modules.txt>.
-SMC ISA TokenRing adapter support
+SMC ISA/MCA Token Ring adapter support
CONFIG_SMCTR
This is support for the ISA and MCA SMC Token Ring cards,
specifically SMC TokenCard Elite (8115T) and SMC TokenCard Elite/A
@@ -10090,13 +11292,13 @@
If you have such an adapter and would like to use it, say Y or M and
read the Token-Ring mini-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto and the file
- Documentation/networking/smctr.txt.
+ <http://www.linuxdoc.org/docs.html#howto> and the file
+ <file:Documentation/networking/smctr.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called smctr.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt.
+ as a module, say M here and read <file:Documentation/modules.txt>.
Sun Happy Meal 10/100baseT support
CONFIG_HAPPYMEAL
@@ -10108,60 +11310,62 @@
This support is also available as a module called sunhme.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
Sun Lance support
CONFIG_SUNLANCE
This driver supports the "le" interface present on all 32-bit Sparc
- systems, on some older Ultra systems and as an Sbus option.
+ systems, on some older Ultra systems and as an Sbus option. These
+ cards are based on the AMD Lance chipset, which is better known
+ via the NE2100 cards.
This support is also available as a module called sunlance.o ( =
code which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
-Sun BigMAC 10/100baseT support (EXPERIMENTAL)
+Sun BigMAC 10/100baseT support
CONFIG_SUNBMAC
This driver supports the "be" interface available as an Sbus option.
- This is Sun's older 100baseT ethernet device.
+ This is Sun's older 100baseT Ethernet device.
This support is also available as a module called sunbmac.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
Sun QuadEthernet support
CONFIG_SUNQE
- This driver supports the "qe" 10baseT ethernet device, available as
+ This driver supports the "qe" 10baseT Ethernet device, available as
an Sbus option. Note that this is not the same as Quad FastEthernet
"qfe" which is supported by the Happy Meal driver instead.
This support is also available as a module called sunqe.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
-Traffic Shaper (EXPERIMENTAL)
+Traffic Shaper
CONFIG_SHAPER
The traffic shaper is a virtual network device that allows you to
limit the rate of outgoing data flow over some other network device.
The traffic that you want to slow down can then be routed through
- these virtual devices. See Documentation/networking/shaper.txt for
- more information.
+ these virtual devices. See
+ <file:Documentation/networking/shaper.txt> for more information.
An alternative to this traffic shaper is the experimental
Class-Based Queueing (CBQ) scheduling support which you get if you
say Y to "QoS and/or fair queueing" above.
To set up and configure shaper devices, you need the shapecfg
- program, available from ftp://shadow.cabi.net/pub/Linux in the
+ program, available from <ftp://shadow.cabi.net/pub/Linux> in the
shaper package.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called shaper.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt. If unsure,
- say N.
+ The module will be called shaper.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>. If
+ unsure, say N.
FDDI driver support
CONFIG_FDDI
@@ -10196,8 +11400,8 @@
- Netelligent 100 FDDI DAS UTP
- Netelligent 100 FDDI SAS UTP
- Netelligent 100 FDDI SAS Fibre MIC
-
- Read Documentation/networking/skfp.txt for information about
+
+ Read <file:Documentation/networking/skfp.txt> for information about
the driver.
Questions concerning this driver can be addressed to:
@@ -10205,10 +11409,10 @@
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. This is recommended.
- The module will be called skfp.o.
+ say M here and read <file:Documentation/modules.txt>. This is
+ recommended. The module will be called skfp.o.
-HIgh Performance Parallel Interface support (EXPERIMENTAL)
+HIgh Performance Parallel Interface (HIPPI) support
CONFIG_HIPPI
HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
@@ -10218,16 +11422,16 @@
and have a HIPPI network card in your computer that you want to use
under Linux, say Y here (you must also remember to enable the driver
for your HIPPI card below). Most people will say N here.
-
+
Essential RoadRunner HIPPI PCI adapter support
CONFIG_ROADRUNNER
Say Y here if this is your PCI HIPPI network card.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called rrunner.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt. If unsure,
- say N.
+ The module will be called rrunner.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>. If
+ unsure, say N.
Use large TX/RX rings
CONFIG_ROADRUNNER_LARGE_RINGS
@@ -10237,80 +11441,92 @@
kernel code or by user space programs. Say Y here only if you have
the memory.
-Acorn Ether1 card
+Acorn Ether1 support
CONFIG_ARM_ETHER1
If you have an Acorn system with one of these (AKA25) network cards,
you should say Y to this option if you wish to use it with Linux.
-Acorn/ANT Ether3 card
+Acorn/ANT Ether3 support
CONFIG_ARM_ETHER3
If you have an Acorn system with one of these network cards, you
should say Y to this option if you wish to use it with Linux.
-I Cubed EtherH card
+I-Cubed EtherH support
CONFIG_ARM_ETHERH
If you have an Acorn system with one of these network cards, you
should say Y to this option if you wish to use it with Linux.
-EBSA-110 Ethernet interface
+EBSA-110 Ethernet interface (AM79C961A)
CONFIG_ARM_AM79C961A
If you wish to compile a kernel for the EBSA-110, then you should
always answer Y to this.
-Support CDROM drives that are not SCSI or IDE/ATAPI
+Support Thumb instructions
+CONFIG_ARM_THUMB
+ Say Y if you want to have kernel support for ARM Thumb instructions,
+ fault handlers, and system calls.
+
+ The Thumb instruction set is a compressed form of the standard ARM
+ instruction set resulting in smaller binaries at the expense of
+ slightly less efficient code.
+
+ If you don't know what this all is, saying Y is a safe choice.
+
+Support CD-ROM drives that are not SCSI or IDE/ATAPI
CONFIG_CD_NO_IDESCSI
- If you have a CDROM drive that is neither SCSI nor IDE/ATAPI, say Y
- here, otherwise N. Read the CDROM-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ If you have a CD-ROM drive that is neither SCSI nor IDE/ATAPI, say Y
+ here, otherwise N. Read the CD-ROM-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
- kernel: saying N will just cause this configure script to skip all
- the questions about these CDROM drives. If you are unsure what you
+ kernel: saying N will just cause the configurator to skip all
+ the questions about these CD-ROM drives. If you are unsure what you
have, say Y and find out whether you have one of the following
- drives.
+ drives.
- For each of these drivers, a file Documentation/cdrom/<driver_name>
+ For each of these drivers, a file Documentation/cdrom/{driver_name}
exists. Especially in cases where you do not know exactly which kind
of drive you have you should read there. Most of these drivers use a
- file drivers/cdrom/<driver_name>.h where you can define your
- interface parameters and switch some internal goodies.
+ file drivers/cdrom/{driver_name}.h where you can define your
+ interface parameters and switch some internal goodies.
- All these CDROM drivers are also usable as a module ( = code which
+ All these CD-ROM drivers are also usable as a module ( = code which
can be inserted in and removed from the running kernel whenever you
want). If you want to compile them as module, say M instead of Y and
- read Documentation/modules.txt.
+ read <file:Documentation/modules.txt>.
- If you want to use any of these CDROM drivers, you also have to
- answer Y or M to "ISO 9660 CDROM file system support" below (this
+ If you want to use any of these CD-ROM drivers, you also have to
+ answer Y or M to "ISO 9660 CD-ROM file system support" below (this
answer will get "defaulted" for you if you enable any of the Linux
- CDROM drivers).
+ CD-ROM drivers).
-Sony CDU31A/CDU33A CDROM support
+Sony CDU31A/CDU33A CD-ROM support
CONFIG_CDU31A
- These CDROM drives have a spring-pop-out caddyless drawer, and a
- rectangular green LED centered beneath it. NOTE: these CDROM drives
- will not be auto detected by the kernel at boot time; you have to
- provide the interface address as an option to the kernel at boot
- time as described in Documentation/cdrom/cdu31a or fill in your
- parameters into drivers/cdrom/cdu31a.c. Try "man bootparam" or
- see the documentation of your boot loader (lilo or loadlin) about
- how to pass options to the kernel.
+ These CD-ROM drives have a spring-pop-out caddyless drawer, and a
+ rectangular green LED centered beneath it. NOTE: these CD-ROM
+ drives will not be auto detected by the kernel at boot time; you
+ have to provide the interface address as an option to the kernel at
+ boot time as described in <file:Documentation/cdrom/cdu31a> or fill
+ in your parameters into <file:drivers/cdrom/cdu31a.c>. Try "man
+ bootparam" or see the documentation of your boot loader (lilo or
+ loadlin) about how to pass options to the kernel.
- If you say Y here, you should also say Y or M to "ISO 9660 CDROM
+ If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
file system support" below, because that's the file system used on
- CDROMs.
+ CD-ROMs.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called cdu31a.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ The module will be called cdu31a.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
-Standard Mitsumi [no XA/Multisession] CDROM support
+Standard Mitsumi [no XA/Multisession] CD-ROM support
CONFIG_MCD
This is the older of the two drivers for the older Mitsumi models
LU-005, FX-001 and FX-001D. This is not the right driver for the
FX-001DE and the triple or quad speed models (all these are
- IDE/ATAPI models). Please also the file Documentation/cdrom/mcd.
+ IDE/ATAPI models). Please also the file
+ <file:Documentation/cdrom/mcd>.
With the old LU-005 model, the whole drive chassis slides out for cd
insertion. The FX-xxx models use a motorized tray type mechanism.
@@ -10318,184 +11534,201 @@
(PhotoCDs). There is a new driver (next question) which can do
this. If you want that one, say N here.
- If you say Y here, you should also say Y or M to "ISO 9660 CDROM
+ If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
file system support" below, because that's the file system used on
- CDROMs.
+ CD-ROMs.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called mcd.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
IRQ channel for Mitsumi CD-ROM
CONFIG_MCD_IRQ
This allows you to specify the default value of the IRQ used by the
driver. This setting can be overridden by passing the "mcd="
parameter to the kernel at boot time (or at module load time if you
- said M to "Standard Mitsumi CDROM support").
+ said M to "Standard Mitsumi CD-ROM support").
I/O base address for Mitsumi CD-ROM
CONFIG_MCD_BASE
This allows you to specify the default value of the I/O base address
used by the driver. This setting can be overridden by passing the
"mcd=" parameter to the kernel at boot time (or at module load time
- if you said M to "Standard Mitsumi CDROM support").
+ if you said M to "Standard Mitsumi CD-ROM support").
-Mitsumi [XA/MultiSession] support
+Mitsumi [XA/MultiSession] CD-ROM support
CONFIG_MCDX
Use this driver if you want to be able to read XA or MultiSession
CDs (PhotoCDs) as well as ordinary CDs with your Mitsumi LU-005,
- FX-001 or FX-001D CDROM drive. In addition, this driver uses much
+ FX-001 or FX-001D CD-ROM drive. In addition, this driver uses much
less kernel memory than the old one, if that is a concern. This
driver is able to support more than one drive, but each drive needs
a separate interface card. Please read the file
- Documentation/cdrom/mcdx.
+ <file:Documentation/cdrom/mcdx>.
- If you say Y here, you should also say Y or M to "ISO 9660 CDROM
+ If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
file system support" below, because that's the file system used on
- CDROMs.
+ CD-ROMs.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called mcdx.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
-Matsushita/Panasonic/Creative, Longshine, TEAC CDROM support
+Matsushita/Panasonic/Creative, Longshine, TEAC CD-ROM support
CONFIG_SBPCD
This driver supports most of the drives which use the Panasonic or
- Sound Blaster interface. Please read the file
- Documentation/cdrom/sbpcd.
+ Sound Blaster interface. Please read the file
+ <file:Documentation/cdrom/sbpcd>.
The Matsushita CR-521, CR-522, CR-523, CR-562, CR-563 drives
(sometimes labeled "Creative"), the Creative Labs CD200, the
- Longshine LCS-7260, the "IBM External ISA CDROM" (in fact a CR-56x
- model), the TEAC CD-55A fall under this category. Some other
+ Longshine LCS-7260, the "IBM External ISA CD-ROM" (in fact a CR-56x
+ model), the TEAC CD-55A fall under this category. Some other
"electrically compatible" drives (Vertos, Genoa, some Funai models)
are currently not supported; for the Sanyo H94A drive currently a
- separate driver (asked later) is responsible. Most drives have a
+ separate driver (asked later) is responsible. Most drives have a
uniquely shaped faceplate, with a caddyless motorized drawer, but
- without external brand markings. The older CR-52x drives have a
- caddy and manual loading/eject, but still no external markings. The
+ without external brand markings. The older CR-52x drives have a
+ caddy and manual loading/eject, but still no external markings. The
driver is able to do an extended auto-probing for interface
addresses and drive types; this can help to find facts in cases you
are not sure, but can consume some time during the boot process if
- none of the supported drives gets found. Once your drive got found,
- you should enter the reported parameters into drivers/cdrom/sbpcd.h
- and set "DISTRIBUTION 0" there.
-
- This driver can support up to four CDROM controller cards, and each
- card can support up to four CDROM drives; if you say Y here, you
- will be asked how many controller cards you have. If compiled as a
+ none of the supported drives gets found. Once your drive got found,
+ you should enter the reported parameters into
+ <file:drivers/cdrom/sbpcd.h> and set "DISTRIBUTION 0" there.
+
+ This driver can support up to four CD-ROM controller cards, and each
+ card can support up to four CD-ROM drives; if you say Y here, you
+ will be asked how many controller cards you have. If compiled as a
module, only one controller card (but with up to four drives) is
usable.
- If you say Y here, you should also say Y or M to "ISO 9660 CDROM
+ If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
file system support" below, because that's the file system used on
- CDROMs.
+ CD-ROMs.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called sbpcd.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ The module will be called sbpcd.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
-Matsushita/Panasonic, ... second CDROM controller support
+Matsushita/Panasonic, ... second CD-ROM controller support
CONFIG_SBPCD2
- Say Y here only if you have two CDROM controller cards of this type
- (usually only if you have more than four drives). You should enter
+ Say Y here only if you have two CD-ROM controller cards of this type
+ (usually only if you have more than four drives). You should enter
the parameters for the second, third and fourth interface card into
- include/linux/sbpcd.h before compiling the new kernel. Read
- the file Documentation/cdrom/sbpcd.
+ <file:include/linux/sbpcd.h> before compiling the new kernel. Read
+ the file <file:Documentation/cdrom/sbpcd>.
+
+Matsushita/Panasonic, ... third CD-ROM controller support
+CONFIG_SBPCD3
+ Say Y here only if you have three CD-ROM controller cards of this
+ type (usually only if you have more than six drives). You should
+ enter the parameters for the second, third and fourth interface card
+ into <file:include/linux/sbpcd.h> before compiling the new kernel.
+ Read the file <file:Documentation/cdrom/sbpcd>.
+
+Matsushita/Panasonic, ... fourth CD-ROM controller support
+CONFIG_SBPCD4
+ Say Y here only if you have four CD-ROM controller cards of this
+ type (usually only if you have more than eight drives). You should
+ enter the parameters for the second, third and fourth interface card
+ into <file:include/linux/sbpcd.h> before compiling the new kernel.
+ Read the file <file:Documentation/cdrom/sbpcd>.
-Aztech/Orchid/Okano/Wearnes/TXC/CyDROM CDROM support
+Aztech/Orchid/Okano/Wearnes/TXC/CyDROM CD-ROM support
CONFIG_AZTCD
This is your driver if you have an Aztech CDA268-01A, Orchid
- CD-3110, Okano or Wearnes CDD110, Conrad TXC, or CyCDROM CR520 or
- CR540 CDROM drive. This driver -- just like all these CDROM drivers
- -- is NOT for CDROM drives with IDE/ATAPI interfaces, such as Aztech
- CDA269-031SE. Please read the file Documentation/cdrom/aztcd.
+ CD-3110, Okano or Wearnes CDD110, Conrad TXC, or CyCD-ROM CR520 or
+ CR540 CD-ROM drive. This driver -- just like all these CD-ROM
+ drivers -- is NOT for CD-ROM drives with IDE/ATAPI interfaces, such
+ as Aztech CDA269-031SE. Please read the file
+ <file:Documentation/cdrom/aztcd>.
- If you say Y here, you should also say Y or M to "ISO 9660 CDROM
+ If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
file system support" below, because that's the file system used on
- CDROMs.
+ CD-ROMs.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called aztcd.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ The module will be called aztcd.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
-Sony CDU535 CDROM support
+Sony CDU535 CD-ROM support
CONFIG_CDU535
- This is the driver for the older Sony CDU-535 and CDU-531 CDROM
- drives. Please read the file Documentation/cdrom/sonycd535.
+ This is the driver for the older Sony CDU-535 and CDU-531 CD-ROM
+ drives. Please read the file <file:Documentation/cdrom/sonycd535>.
- If you say Y here, you should also say Y or M to "ISO 9660 CDROM
+ If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
file system support" below, because that's the file system used on
- CDROMs.
+ CD-ROMs.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called sonycd535.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
+ a module, say M here and read <file:Documentation/modules.txt>.
-Goldstar R420 CDROM support
+Goldstar R420 CD-ROM support
CONFIG_GSCD
- If this is your CDROM drive, say Y here. As described in the file
- Documentation/cdrom/gscd, you might have to change a setting
- in the file drivers/cdrom/gscd.h before compiling the
- kernel. Please read the file Documentation/cdrom/gscd.
+ If this is your CD-ROM drive, say Y here. As described in the file
+ <file:Documentation/cdrom/gscd>, you might have to change a setting
+ in the file <file:drivers/cdrom/gscd.h> before compiling the
+ kernel. Please read the file <file:Documentation/cdrom/gscd>.
- If you say Y here, you should also say Y or M to "ISO 9660 CDROM
+ If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
file system support" below, because that's the file system used on
- CDROMs.
+ CD-ROMs.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called gscd.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ The module will be called gscd.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
-Philips/LMS CM206 CDROM support
+Philips/LMS CM206 CD-ROM support
CONFIG_CM206
- If you have a Philips/LMS CDROM drive cm206 in combination with a
+ If you have a Philips/LMS CD-ROM drive cm206 in combination with a
cm260 host adapter card, say Y here. Please also read the file
- Documentation/cdrom/cm206.
+ <file:Documentation/cdrom/cm206>.
- If you say Y here, you should also say Y or M to "ISO 9660 CDROM
+ If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
file system support" below, because that's the file system used on
- CDROMs.
+ CD-ROMs.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called cm206.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
-Optics Storage DOLPHIN 8000AT CDROM support
+Optics Storage DOLPHIN 8000AT CD-ROM support
CONFIG_OPTCD
This is the driver for the 'DOLPHIN' drive with a 34-pin Sony
compatible interface. It also works with the Lasermate CR328A. If
you have one of those, say Y. This driver does not work for the
- Optics Storage 8001 drive; use the IDE-ATAPI CDROM driver for that
- one. Please read the file Documentation/cdrom/optcd.
+ Optics Storage 8001 drive; use the IDE-ATAPI CD-ROM driver for that
+ one. Please read the file <file:Documentation/cdrom/optcd>.
- If you say Y here, you should also say Y or M to "ISO 9660 CDROM
+ If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
file system support" below, because that's the file system used on
- CDROMs.
+ CD-ROMs.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called optcd.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
-Sanyo CDR-H94A CDROM support
+Sanyo CDR-H94A CD-ROM support
CONFIG_SJCD
- If this is your CDROM drive, say Y here and read the file
- Documentation/cdrom/sjcd. You should then also say Y or M to
- "ISO 9660 CDROM file system support" below, because that's the
- file system used on CDROMs.
+ If this is your CD-ROM drive, say Y here and read the file
+ <file:Documentation/cdrom/sjcd>. You should then also say Y or M to
+ "ISO 9660 CD-ROM file system support" below, because that's the
+ file system used on CD-ROMs.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called sjcd.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
ISP16/MAD16/Mozart soft configurable cdrom interface support
CONFIG_ISP16_CDI
@@ -10503,12 +11736,17 @@
82C928 or 82C929 chips. Say Y here to have them detected and
possibly configured at boot time. In addition, You'll have to say Y
to a driver for the particular cdrom drive you have attached to the
- card. Read Documentation/cdrom/isp16 for details.
+ card. Read <file:Documentation/cdrom/isp16> for details.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called isp16.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
+
+iSeries Virtual I/O CD Support
+CONFIG_VIOCD
+ If you are running Linux on an IBM iSeries system and you want to
+ read a CD drive owned by OS/400, say Y here.
Quota support
CONFIG_QUOTA
@@ -10516,13 +11754,13 @@
usage (also called disk quotas). Currently, it works only for the
ext2 file system. You need additional software in order to use quota
support; for details, read the Quota mini-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . Probably the quota
+ <http://www.linuxdoc.org/docs.html#howto>. Probably the quota
support is only useful for multi user systems. If unsure, say N.
Memory Technology Device (MTD) support
CONFIG_MTD
Memory Technology Devices are flash, RAM and similar chips, often
- used for solid state filesystems on embedded devices. This option
+ used for solid state file systems on embedded devices. This option
will provide the generic support for MTD drivers to register
themselves with the kernel and for potential users of MTD devices
to enumerate the devices which are present and obtain a handle on
@@ -10548,18 +11786,17 @@
RedBoot partition table parsing
CONFIG_MTD_REDBOOT_PARTS
RedBoot is a ROM monitor and bootloader which deals with multiple
- 'images' in flash devices by putting a table in the last erase
- block of the device, similar to a partition table, which gives
- the offsets, lengths and names of all the images stored in the
- flash.
+ 'images' in flash devices by putting a table in the last erase block
+ of the device, similar to a partition table, which gives the
+ offsets, lengths and names of all the images stored in the flash.
If you need code which can detect and parse this table, and register
MTD 'partitions' corresponding to each image in the table, enable
- this option.
+ this option.
You will still need the parsing functions to be called by the driver
- for your particular device. It won't happen automatically. The
- SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
+ for your particular device. It won't happen automatically. The
+ SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
example.
Compaq bootldr partition table parsing
@@ -10567,11 +11804,11 @@
The Compaq bootldr deals with multiple 'images' in flash devices
by putting a table in one of the first erase blocks of the device,
similar to a partition table, which gives the offsets, lengths and
- names of all the images stored in the flash.
+ names of all the images stored in the flash.
If you need code which can detect and parse this table, and register
MTD 'partitions' corresponding to each image in the table, enable
- this option.
+ this option.
You will still need the parsing functions to be called by the driver
for your particular device. It won't happen automatically. The
@@ -10582,21 +11819,20 @@
CONFIG_MTD_AFS_PARTS
The ARM Firmware Suite allows the user to divide flash devices into
multiple 'images'. Each such image has a header containing its name
- and offset/size etc.
+ and offset/size etc.
- If you need code which can detect and parse these tables, and register
- MTD 'partitions' corresponding to each image detected, enable
- this option.
+ If you need code which can detect and parse these tables, and
+ register MTD 'partitions' corresponding to each image detected,
+ enable this option.
You will still need the parsing functions to be called by the driver
- for your particular device. It won't happen automatically. The
+ for your particular device. It won't happen automatically. The
'armflash' map driver (CONFIG_MTD_ARMFLASH) does this, for example.
-MTD debugging verbosity
+MTD debugging verbosity (0 = quiet, 3 = noisy)
CONFIG_MTD_DEBUG_VERBOSE
Determines the verbosity level of the MTD debugging messages.
-
Direct chardevice access to MTD devices
CONFIG_MTD_CHAR
This provides a character device for each MTD device present in
@@ -10608,8 +11844,8 @@
CONFIG_MTD_BLOCK
Although most flash chips have an erase size too large to be useful
as block devices, it is possible to use MTD devices which are based
- on RAM chips in this manner. This block device is a user of MTD devices
- performing that function.
+ on RAM chips in this manner. This block device is a user of MTD
+ devices performing that function.
At the moment, it is also required for the Journalling Flash File
System(s) to obtain a handle on the MTD device when it's mounted
@@ -10618,7 +11854,7 @@
Later, it may be extended to perform read/erase/modify/write cycles
on flash chips to emulate a smaller block size. Needless to say,
- this is very unsafe, but could be useful for filesystems which are
+ this is very unsafe, but could be useful for file systems which are
almost never written to.
You do not need this option for use with the DiskOnChip devices. For
@@ -10626,9 +11862,9 @@
Readonly block device access to MTD devices
CONFIG_MTD_BLOCK_RO
- This allows you to mount read-only filesystems (such as cramfs) from
- an MTD device, without the overhead (and danger) of the caching
- driver.
+ This allows you to mount read-only file systems (such as cramfs)
+ from an MTD device, without the overhead (and danger) of the caching
+ driver.
You do not need this option for use with the DiskOnChip devices. For
those, enable NFTL support (CONFIG_NFTL) instead.
@@ -10637,8 +11873,8 @@
CONFIG_FTL
This provides support for the original Flash Translation Layer which
is part of the PCMCIA specification. It uses a kind of pseudo-
- filesystem on a flash device to emulate a block device with 512-byte
- sectors, on top of which you put a 'normal' filesystem.
+ file system on a flash device to emulate a block device with
+ 512-byte sectors, on top of which you put a 'normal' file system.
You may find that the algorithms used in this code are patented
unless you live in the Free World where software patents aren't
@@ -10651,8 +11887,8 @@
CONFIG_NFTL
This provides support for the NAND Flash Translation Layer which is
used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
- filesystem on a flash device to emulate a block device with 512-byte
- sectors, on top of which you put a 'normal' filesystem.
+ file system on a flash device to emulate a block device with
+ 512-byte sectors, on top of which you put a 'normal' file system.
You may find that the algorithms used in this code are patented
unless you live in the Free World where software patents aren't
@@ -10663,9 +11899,10 @@
Write support for NFTL (EXPERIMENTAL)
CONFIG_NFTL_RW
- If you're lucky, this will actually work. Don't whinge if it doesn't.
- Send mail to the MTD mailing list <linux-mtd@lists.infradead.org> if
- you want to help to make it more reliable.
+ If you're lucky, this will actually work. Don't whinge if it
+ doesn't. Send mail to the MTD mailing list
+ <linux-mtd@lists.infradead.org> if you want to help to make it more
+ reliable.
Common Flash Interface (CFI) support
CONFIG_MTD_CFI
@@ -10673,7 +11910,7 @@
AMD and other flash manufactures that provides a universal method
for probing the capabilities of flash devices. If you wish to
support any device that is CFI-compliant, you need to enable this
- option. Visit (http://www.amd.com/products/nvd/overview/cfi.html)
+ option. Visit <http://www.amd.com/products/nvd/overview/cfi.html>
for more information on CFI.
CFI Advanced configuration options
@@ -10724,6 +11961,7 @@
If your flash chips are interleaved in fours - i.e. you have four
flash chips addressed by each bus cycle, then say 'Y'.
+# Choice: mtd_swap_data
Flash cmd/query data swapping
CONFIG_MTD_CFI_NOSWAP
This option defines the way in which the CPU attempts to arrange
@@ -10732,7 +11970,7 @@
enabled, means that the CPU will not do any swapping; the chips
are expected to be wired to the CPU in 'host-endian' form.
Specific arrangements are possible with the BIG_ENDIAN_BYTE and
- LITTLE_ENDIAN_BYTE, if the bytes are reversed.
+ LITTLE_ENDIAN_BYTE, if the bytes are reversed.
If you have a LART, on which the data (and address) lines were
connected in a fashion which ensured that the nets were as short
@@ -10741,14 +11979,14 @@
Yes, there really exists something sicker than PDP-endian :)
-CFI support for Intel/Sharp Extended Commands
+CFI support for Intel/Sharp Extended Command Set chips
CONFIG_MTD_CFI_INTELEXT
The Common Flash Interface defines a number of different command
sets which a CFI-compliant chip may claim to implement. This code
provides support for one of those command sets, used on Intel
StrataFlash and other parts.
-CFI support for AMD/Fujitsu Standard Commands
+CFI support for AMD/Fujitsu Standard Command Set chips
CONFIG_MTD_CFI_AMDSTD
The Common Flash Interface defines a number of different command
sets which a CFI-compliant chip may claim to implement. This code
@@ -10785,26 +12023,36 @@
This option enables basic support for ROM chips accessed through
a bus mapping driver.
+JEDEC device support
CONFIG_MTD_JEDEC
- Enable older older JEDEC flash interface devices for self programming
- flash. It is commonly used in older AMD chips. It is only called
- JEDEC because the JEDEC association (http://www.jedec.org/)
- distributes the identification codes for the chips. WARNING!!!! This
- code does not compile and is incomplete as are the specific JEDEC
- devices drivers.
+ Enable older older JEDEC flash interface devices for self
+ programming flash. It is commonly used in older AMD chips. It is
+ only called JEDEC because the JEDEC association
+ <http://www.jedec.org/> distributes the identification codes for the
+ chips. WARNING!!!! This code does not compile and is incomplete as
+ are the specific JEDEC devices drivers.
CFI Flash device mapped on StrongARM SA11x0
CONFIG_MTD_SA1100
- This enables access to the flash chips on most platforms based on the
- SA1100 and SA1110, including the Assabet and the Compaq iPAQ. If you
- have such a board, say 'Y'.
+ This enables access to the flash chips on most platforms based on
+ the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
+ If you have such a board, say 'Y'.
+Support for Compaq bootldr partition tables on SA11x0
CONFIG_MTD_SA1100_REDBOOT_PARTITIONS
Enabling this option will cause the kernel to look for a RedBoot
FIS (Flash Image System) table in the last erase block of the flash
chips detected. If you are using RedBoot on your SA11x0-based board
and want Linux to present 'partitions' matching the images which
- RedBoot has listed, say 'Y'.
+ RedBoot has listed, say 'Y'.
+
+Support for Compaq bootldr partition tables on SA11x0
+CONFIG_MTD_SA1100_BOOTLDR_PARTITIONS
+ Enabling this option will cause the kernel to look for a Compaq
+ bootldr partition table on the flash chips detected. If you are
+ using the Compaq bootldr on your SA11x0-based board and want Linux
+ to present 'partitions' matching the images which the bootldr has
+ listed, say 'Y'.
Flash chip mapping in physical memory
CONFIG_MTD_PHYSMAP
@@ -10830,6 +12078,7 @@
map which should hopefully be in the documentation for your
board.
+Buswidth of flash in bytes
CONFIG_MTD_PHYSMAP_BUSWIDTH
This is the total width of the data bus of the flash devices
in octets. For example, if you have a data bus width of 32
@@ -10847,7 +12096,7 @@
CONFIG_MTD_NORA
If you had to ask, you don't have one. Say 'N'.
-Flash chip mapping on PNC2000
+Flash chip mapping on Photron PNC-2000
CONFIG_MTD_PNC2000
PNC-2000 is the name of Network Camera product from PHOTRON
Ltd. in Japan. It uses CFI-compliant flash.
@@ -10858,7 +12107,7 @@
a strange sparse mapping. This 'mapping' driver supports that
arrangement, allowing the CFI probe and command set driver code
to communicate with the chips on the RPXLite board. More at
- (http://www.embeddedplanet.com/rpx_lite_specification_sheet.htm).
+ <http://www.embeddedplanet.com/rpx_lite_specification_sheet.htm>.
Flash chip mapping on AMD SC520 CDP board
CONFIG_MTD_SC520CDP
@@ -10866,47 +12115,67 @@
Dual-in-line JEDEC chip. This 'mapping' driver supports that
arrangement, implementing three MTD devices.
-Flash chip mapping on Arcom Control Systems' SBC-MediaGX
-CONFIG_MTD_SBC_MEDIAGX
+Flash chip mapping on Arcom Control Systems SBC-MediaGX
+CONFIG_MTD_SBC_GXX
This provides a driver for the on-board flash of Arcom Control
- Systems' SBC-MediaGX development board. By default the flash
- is split into 3 partitions which are accessed as separate MTD
- devices. This board utilizes Intel StrataFlash. More info at
- (http://www.arcomcontrols.com/products/icp/pc104/processors/).
+ Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
+ By default the flash is split into 3 partitions which are accessed
+ as separate MTD devices. This board utilizes Intel StrataFlash.
+ More info at
+ <http://www.arcomcontrols.com/products/icp/pc104/processors/>.
+
+CFI Flash device mapped on D-Box2
+CONFIG_MTD_DBOX2
+ This enables access routines for the flash chips on the Nokia/Sagem
+ D-Box 2 board. If you have one of these boards and would like to use
+ the flash chips on it, say 'Y'.
+
+CFI Flash device mapped on the XScale IQ80310 board
+CONFIG_MTD_IQ80310
+ This enables access routines for the flash chips on the Intel XScale
+ IQ80310 evaluation board. If you have one of these boards and would
+ like to use the flash chips on it, say 'Y'.
+
+CFI Flash device mapped on AMD NetSc520
+CONFIG_MTD_NETSC520
+ This enables access routines for the flash chips on the AMD NetSc520
+ demonstration board. If you have one of these boards and would like
+ to use the flash chips on it, say 'Y'.
-Flash chip mapping on Arcom Control Systems' ELAN-104NC
+Flash chip mapping on Arcom Control Systems ELAN-104NC
CONFIG_MTD_ELAN_104NC
This provides a driver for the on-board flash of the Arcom Control
System's ELAN-104NC development board. By default the flash
is split into 3 partitions which are accessed as separate MTD
devices. This board utilizes Intel StrataFlash. More info at
- (http://www.arcomcontrols.com/products/icp/pc104/processors/).
+ <http://www.arcomcontrols.com/products/icp/pc104/processors/>.
Flash chip mapping on Compaq iPAQ/Bitsy
CONFIG_MTD_BITSY
This provides a driver for the on-board flash found in Compaq's
iPAQ Palm PC and their research prototype the Itsy. iPAQ info at
- (http://www5.compaq.com/products/handhelds/pocketpc/) and the
- Itsy (http://www.research.digital.com/wrl/projects/Itsy/index.html).
+ <http://www5.compaq.com/products/handhelds/pocketpc/> and the
+ Itsy <http://www.research.digital.com/wrl/projects/Itsy/index.html>.
Flash chip mapping on Compaq iPAQ/Bitsy
CONFIG_MTD_DC21285
This provides a driver for the flash accessed using Intel's
21285 bridge used with Intel's StrongARM processors. More info at
- (http://developer.intel.com/design/bridge/quicklist/dsc-21285.htm).
+ <http://developer.intel.com/design/bridge/quicklist/dsc-21285.htm>.
Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board
CONFIG_MTD_CSTM_MIPS_IXX
- This provides a mapping driver for the Integrated Tecnology
- Express, Inc (ITE) QED-4N-S01B eval board and the Globespan IVR Reference
- Board. It provides the necessary addressing, length, buswidth, vpp code
- and addition setup of the flash device for these boards. In addition,
- this mapping driver can be used for other boards via setting of the
- CONFIG_MTD_CSTM_MIPS_IXX_START/LEN/BUSWIDTH parameters. This mapping
- will provide one mtd device using one partition. The start address can
- be offset from the beginning of flash and the len can be less than the
- total flash device size to allow a window into the flash. Both CFI and
- JEDEC probes are called.
+ This provides a mapping driver for the Integrated Tecnology Express,
+ Inc (ITE) QED-4N-S01B eval board and the Globespan IVR Reference
+ Board. It provides the necessary addressing, length, buswidth, vpp
+ code and addition setup of the flash device for these boards. In
+ addition, this mapping driver can be used for other boards via
+ setting of the CONFIG_MTD_CSTM_MIPS_IXX_START/LEN/BUSWIDTH
+ parameters. This mapping will provide one mtd device using one
+ partition. The start address can be offset from the beginning of
+ flash and the len can be less than the total flash device size to
+ allow a window into the flash. Both CFI and JEDEC probes are
+ called.
Physical start location of flash mapping
CONFIG_MTD_CSTM_MIPS_IXX_START
@@ -10920,7 +12189,7 @@
This is the total length that the MTD driver will use for the
flash chips on your particular board. Refer to the memory
map which should hopefully be in the documentation for your
- board.
+ board.
Physical bus width of flash mapping
CONFIG_MTD_CSTM_MIPS_IXX_BUSWIDTH
@@ -10934,26 +12203,26 @@
to get on with their job of driving the flash chips without
having to know about the paging. If you have one of these boards,
you probably want to enable this mapping driver. More info is at
- (http://www.itc.hu/).
+ <http://www.itc.hu/>.
Flash chip mapping on Octagon 5066 SBC
CONFIG_MTD_OCTAGON
This provides a 'mapping' driver which supports the way in which
the flash chips are connected in the Octagon-5066 Single Board
Computer. More information on the board is available at
- (http://www.octagonsystems.com/Products/5066/5066.html).
+ <http://www.octagonsystems.com/Products/5066/5066.html>.
Flash chip mapping on Tempustech VMAX SBC301
CONFIG_MTD_VMAX
This provides a 'mapping' driver which supports the way in which
the flash chips are connected in the Tempustech VMAX SBC301 Single
Board Computer. More information on the board is available at
- (http://www.tempustech.com/tt301.htm).
+ <http://www.tempustech.com/tt301.htm>.
Support for NAND flash devices
CONFIG_MTD_NAND
This enables support for accessing all type of NAND flash
- devices.
+ devices.
Support for software ECC algorithm
CONFIG_MTD_NAND_ECC
@@ -10983,96 +12252,102 @@
M-Systems Disk-On-Chip 2000 and Millennium support
CONFIG_MTD_DOC2000
This provides an MTD device driver for the M-Systems DiskOnChip
- 2000 and Millennium devices. Originally designed for the DiskOnChip
- 2000, it also now includes support for the DiskOnChip Millennium.
+ 2000 and Millennium devices. Originally designed for the DiskOnChip
+ 2000, it also now includes support for the DiskOnChip Millennium.
If you have problems with this driver and the DiskOnChip Millennium,
you may wish to try the alternative Millennium driver below. To use
the alternative driver, you will need to undefine DOC_SINGLE_DRIVER
- in the drivers/mtd/devices/docprobe.c source code.
+ in the <file:drivers/mtd/devices/docprobe.c> source code.
If you use this device, you probably also want to enable the NFTL
- 'NAND Flash Translation Layer' option below, which is used to emulate
- a block device by using a kind of filesystem on the flash chips.
+ 'NAND Flash Translation Layer' option below, which is used to
+ emulate a block device by using a kind of file system on the flash
+ chips.
Alternative Disk-On-Chip Millennium support
CONFIG_MTD_DOC2001
This provides an alternative MTD device driver for the M-Systems
- DiskOnChip Millennium devices. Use this if you have problems with
- the combined DiskOnChip 2000 and Millennium driver above. To get
+ DiskOnChip Millennium devices. Use this if you have problems with
+ the combined DiskOnChip 2000 and Millennium driver above. To get
the DiskOnChip probe code to load and use this driver instead of
the other one, you will need to undefine DOC_SINGLE_DRIVER near
- the beginning of drivers/mtd/devices/docprobe.c
+ the beginning of <file:drivers/mtd/devices/docprobe.c>.
If you use this device, you probably also want to enable the NFTL
- 'NAND Flash Translation Layer' option below, which is used to emulate
- a block device by using a kind of filesystem on the flash chips.
+ 'NAND Flash Translation Layer' option below, which is used to
+ emulate a block device by using a kind of file system on the flash
+ chips.
Probe for DiskOnChip devices
CONFIG_MTD_DOCPROBE
- This isn't a real config option, it's derived.
+ This isn't a real config option, it's derived.
Advanced detection options for DiskOnChip
CONFIG_MTD_DOCPROBE_ADVANCED
This option allows you to specify nonstandard address at which to
- probe for a DiskOnChip, or to change the detection options. You're
- unlikely to need any of this unless you're using LinuxBIOS. Say 'N'.
+ probe for a DiskOnChip, or to change the detection options. You
+ are unlikely to need any of this unless you are using LinuxBIOS.
+ Say 'N'.
-Probe for 0x55 0xAA BIOS Extension Signature.
+Probe for 0x55 0xAA BIOS Extension Signature
CONFIG_MTD_DOCPROBE_55AA
- Check for the 0x55 0xAA signature of a DiskOnChip, and do not continue
- with probing if it is absent. The signature will always be present for
- a DiskOnChip 2000 or a normal DiskOnChip Millennium. Only if you have
- overwritten the first block of a DiskOnChip Millennium will it be
- absent. Enable this option if you are using LinuxBIOS or if you need
- to recover a DiskOnChip Millennium on which you have managed to wipe
- the first block.
+ Check for the 0x55 0xAA signature of a DiskOnChip, and do not
+ continue with probing if it is absent. The signature will always be
+ present for a DiskOnChip 2000 or a normal DiskOnChip Millennium.
+ Only if you have overwritten the first block of a DiskOnChip
+ Millennium will it be absent. Enable this option if you are using
+ LinuxBIOS or if you need to recover a DiskOnChip Millennium on which
+ you have managed to wipe the first block.
Physical address of DiskOnChip
CONFIG_MTD_DOCPROBE_ADDRESS
- By default, the probe for DiskOnChip devices will look for a DiskOnChip
- at every multiple of 0x2000 between 0xC8000 and 0xEE000. This option
- allows you to specify a single address at which to probe for the device,
- which is useful if you have other devices in that range which get upset
- when they're probed.
+ By default, the probe for DiskOnChip devices will look for a
+ DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
+ This option allows you to specify a single address at which to probe
+ for the device, which is useful if you have other devices in that
+ range which get upset when they are probed.
- (Note that on PowerPC, the normal probe will only check at 0xE4000000.)
+ (Note that on PowerPC, the normal probe will only check at
+ 0xE4000000.)
- Normally, you should leave this set to zero, to allow the probe at the
- normal addresses.
+ Normally, you should leave this set to zero, to allow the probe at
+ the normal addresses.
Probe high addresses
CONFIG_MTD_DOCPROBE_HIGH
- By default, the probe for DiskOnChip devices will look for a DiskOnChip
- at every multiple of 0x2000 between 0xC8000 and 0xEE000. This option
- changes to make it probe between 0xFFFC8000 and 0xFFFEE000. Unless
- you're using LinuxBIOS, this is unlikely to be useful to you. Say 'N'.
+ By default, the probe for DiskOnChip devices will look for a
+ DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
+ This option changes to make it probe between 0xFFFC8000 and
+ 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
+ useful to you. Say 'N'.
Ramix PMC551 PCI Mezzanine ram card support
CONFIG_MTD_PMC551
This provides a MTD device driver for the Ramix PMC551 RAM PCI card
- from Ramix Inc. (http://www.ramix.com/products/memory/pmc551.html).
+ from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>.
These devices come in memory configurations from 32M - 1G. If you
have one, you probably want to enable this.
- If this driver is compiled as a module you get the ability to select the
- size of the aperture window pointing into the devices memory. What this
- means is that if you have a 1G card, normally the kernel will use a 1G
- memory map as it's view of the device. As a module, you can select a
- 1M window into the memory and the driver will "slide" the window around
- the PMC551's memory. This was particularly useful on the 2.2 kernels
- on PPC architectures as there was limited kernel space to deal with.
+ If this driver is compiled as a module you get the ability to select
+ the size of the aperture window pointing into the devices memory.
+ What this means is that if you have a 1G card, normally the kernel
+ will use a 1G memory map as its view of the device. As a module,
+ you can select a 1M window into the memory and the driver will
+ "slide" the window around the PMC551's memory. This was
+ particularly useful on the 2.2 kernels on PPC architectures as there
+ was limited kernel space to deal with.
PMC551 256M DRAM Bugfix
CONFIG_MTD_PMC551_BUGFIX
- Some of Ramix's PMC551 boards with 256M configurations have invalid column
- and row mux values. This option will fix them, but will break other memory
- configurations. If unsure say N.
+ Some of Ramix's PMC551 boards with 256M configurations have invalid
+ column and row mux values. This option will fix them, but will
+ break other memory configurations. If unsure say N.
PMC551 Debugging
CONFIG_MTD_PMC551_DEBUG
- This option makes the PMC551 more verbose during it's operation and is only
- really usefull if you are developing on this driver or suspect a possible
- hardware or driver bug. If unsure say N.
+ This option makes the PMC551 more verbose during its operation and
+ is only really useful if you are developing on this driver or
+ suspect a possible hardware or driver bug. If unsure say N.
Use extra onboard system memory as MTD device
CONFIG_MTD_SLRAM
@@ -11083,24 +12358,24 @@
Debugging RAM test driver
CONFIG_MTD_MTDRAM
This enables a test MTD device driver which uses vmalloc() to
- provide storage. You probably want to say 'N' unless you're
+ provide storage. You probably want to say 'N' unless you're
testing stuff.
-MTDRAM erase block size in KiB
+MTDRAM erase block size in KB
CONFIG_MTDRAM_ERASE_SIZE
This allows you to configure the size of the erase blocks in the
- device emulated by the MTDRAM driver. If the MTDRAM driver is built
+ device emulated by the MTDRAM driver. If the MTDRAM driver is built
as a module, it is also possible to specify this as a parameter when
loading the module.
-MTDRAM device size in KiB
+MTDRAM device size in KB
CONFIG_MTDRAM_TOTAL_SIZE
This allows you to configure the total size of the MTD device
- emulated by the MTDRAM driver. If the MTDRAM driver is built
+ emulated by the MTDRAM driver. If the MTDRAM driver is built
as a module, it is also possible to specify this as a parameter when
loading the module.
-SRAM absolute position
+SRAM Hexadecimal Absolute position or 0
CONFIG_MTDRAM_ABS_POS
If you have system RAM accessible by the CPU but not used by Linux
in normal operation, you can give the physical address at which the
@@ -11110,34 +12385,40 @@
Flash chip mapping on the Flaga Digital Module
CONFIG_MTD_CFI_FLAGADM
- Mapping for the Flaga digital module. If you don´t have one, ignore this
- setting.
+ Mapping for the Flaga digital module. If you don´t have one, ignore
+ this setting.
+
+Momenco Ocelot boot flash device
+CONFIG_MTD_OCELOT
+ This enables access routines for the boot flash device and for the
+ NVRAM on the Momenco Ocelot board. If you have one of these boards
+ and would like access to either of these, say 'Y'.
-Support for USB
+USB (Universal Serial Bus) support
CONFIG_USB
Universal Serial Bus (USB) is a specification for a serial bus
subsystem which offers higher speeds and more features than the
- traditional PC serial port. The bus supplies power to peripherals
- and allows for hot swapping. Up to 127 USB peripherals can be
- connected to a single USB port in a tree structure. The USB port is
+ traditional PC serial port. The bus supplies power to peripherals
+ and allows for hot swapping. Up to 127 USB peripherals can be
+ connected to a single USB port in a tree structure. The USB port is
the root of the tree, the peripherals are the leaves and the inner
- nodes are special USB devices called hubs. Many newer PC's have USB
+ nodes are special USB devices called hubs. Many newer PC's have USB
ports and newer peripherals such as scanners, keyboards, mice,
modems, and printers support the USB protocol and can be connected
to the PC via those ports.
Say Y here if your computer has a USB port and you want to use USB
- devices. You then need to say Y to at least one of "UHCI support" or
- "OHCI support" below (the type of interface that the USB hardware in
- your computer provides to the operating system) and then choose from
- among the drivers for USB peripherals. You may want to check out the
- information provided in Documentation/usb/ and especially the links
- given in Documentation/usb/usb-help.txt.
+ devices. You then need to say Y to at least one of "UHCI support"
+ or "OHCI support" below (the type of interface that the USB hardware
+ in your computer provides to the operating system) and then choose
+ from among the drivers for USB peripherals. You may want to check
+ out the information provided in <file:Documentation/usb/> and
+ especially the links given in <file:Documentation/usb/usb-help.txt>.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called usbcore.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ The module will be called usbcore.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
USB verbose debug messages
CONFIG_USB_DEBUG
@@ -11160,14 +12441,14 @@
USB long timeout
CONFIG_USB_LONG_TIMEOUT
This option makes the standard time out a bit longer. Basically,
- some devices are just slow to respond, so this makes usb more
+ some devices are just slow to respond, so this makes usb more
patient. There should be no harm in selecting this, but it is
needed for some MGE Ellipse UPSes.
If you have an MGE Ellipse UPS, or you see timeouts in HID
transactions, say Y; otherwise say N.
-UHCI (intel PIIX4, VIA, ...) support
+UHCI (Intel PIIX4, VIA, ...) support
CONFIG_USB_UHCI
The Universal Host Controller Interface is a standard by Intel for
accessing the USB hardware in the PC (which is also called the USB
@@ -11179,15 +12460,15 @@
133).
Currently there exist two drivers for UHCI host controllers: this
- one and the so-called JE driver, which you can get from
+ one and the so-called JE driver, which you can get from
"UHCI alternate (JE) support", below. You need only one.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called usb-uhci.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
-UHCI (intel PIIX4, VIA, ...) alternate (JE) support?
+UHCI (Intel PIIX4, VIA, ...) alternate (JE) support
CONFIG_USB_UHCI_ALT
The Universal Host Controller Interface is a standard by Intel for
accessing the USB hardware in the PC (which is also called the USB
@@ -11205,11 +12486,7 @@
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called uhci.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
-
-UHCI unlink optimizations (EXPERIMENTAL)
-CONFIG_USB_UHCI_ALT_UNLINK_OPTIMIZE
- This option currently does nothing. You may say Y or N.
+ module, say M here and read <file:Documentation/modules.txt>.
OHCI (Compaq, iMacs, OPTi, SiS, ALi, ...) support
CONFIG_USB_OHCI
@@ -11221,12 +12498,12 @@
-- like SiS (aktual 610, 610 and so on) or ALi (ALi IV, ALi V,
Aladdin Pro..) -- conform to this standard.
- You may want to read the file Documentation/usb/ohci.txt.
+ You may want to read <file:Documentation/usb/ohci.txt>.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called usb-ohci.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt.
+ as a module, say M here and read <file:Documentation/modules.txt>.
USB Human Interface Device (full HID) support
CONFIG_USB_HID
@@ -11234,22 +12511,20 @@
mice, joysticks, graphic tablets, or any other HID based devices
to your computer via USB. You can't use this driver and the
HIDBP (Boot Protocol) keyboard and mouse drivers at the same time.
- More information is available: Documentation/input/input.txt.
+ More information is available: <file:Documentation/input/input.txt>.
If unsure, say Y.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called hid.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
/dev/usb/hiddev raw HID device support
CONFIG_USB_HIDDEV
Say Y here if you want to support HID devices (from the USB
specification standpoint) that aren't strictly user interface
devices, like monitor controls and Uninterruptable Power Supplies.
- It is also used for "consumer keys" on multimedia keyboards and
- USB speakers.
This module supports these devices separately using a separate
event interface on /dev/usb/hiddevX (char 180:96 to 180:111).
@@ -11266,7 +12541,7 @@
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called usbkbd.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
If unsure, say N.
@@ -11279,41 +12554,41 @@
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called usbmouse.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
+ a module, say M here and read <file:Documentation/modules.txt>.
If unsure, say N.
Wacom Intuos/Graphire tablet support
CONFIG_USB_WACOM
Say Y here if you want to use the USB version of the Wacom Intuos
- or Graphire tablet. Make sure to say Y to "Mouse support"
+ or Graphire tablet. Make sure to say Y to "Mouse support"
(CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
(CONFIG_INPUT_EVDEV) as well.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called wacom.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ The module will be called wacom.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
-Logitech WingMan Force joystick support
-CONFIG_USB_WMFORCE
- Say Y here if you want to use the Logitech WingMan Force with Linux
- on the USB port. No force-feedback support yet, but other than that
- it should work like a normal joystick.
+Aiptek 8000U tablet support
+CONFIG_USB_AIPTEK
+ Say Y here if you want to use the USB version of the Aiptek 8000U
+ tablet. Make sure to say Y to "Event interface support"
+ (CONFIG_INPUT_EVDEV) as well.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called wmforce.o. If you want to compile it as a
+ The module will be called aiptek.o. If you want to compile it as a
module, say M here and read Documentation/modules.txt.
Use input layer for ADB devices
CONFIG_INPUT_ADBHID
Say Y here if you want to have ADB (Apple Desktop Bus) HID devices
- such as keyboards, mice, joysticks, or graphic tablets handled by the
- input layer. If you say Y here, make sure to say Y to the
+ such as keyboards, mice, joysticks, or graphic tablets handled by
+ the input layer. If you say Y here, make sure to say Y to the
corresponding drivers "Keyboard support" (CONFIG_INPUT_KEYBDEV),
- "Mouse Support" (CONFIG_INPUT_MOUSEDEV) and "Event interface support"
- (CONFIG_INPUT_EVDEV) as well.
+ "Mouse Support" (CONFIG_INPUT_MOUSEDEV) and "Event interface
+ support" (CONFIG_INPUT_EVDEV) as well.
If you say N here, you still have the option of using the old ADB
keyboard and mouse drivers.
@@ -11333,12 +12608,13 @@
Keyboard support
CONFIG_INPUT_KEYBDEV
Say Y here if you want your USB HID keyboard (or an ADB keyboard
- handled by the input layer) to be able to serve as a system keyboard.
+ handled by the input layer) to be able to serve as a system
+ keyboard.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called keybdev.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ The module will be called keybdev.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
Mouse support
CONFIG_INPUT_MOUSEDEV
@@ -11347,13 +12623,13 @@
/dev/input/mouseX and 13:63 - /dev/input/mice as an emulated ImPS/2
mouse. That way, all user space programs will be able to use your
mouse.
-
+
If unsure, say Y.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called mousedev.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
+ a module, say M here and read <file:Documentation/modules.txt>.
Horizontal screen resolution
CONFIG_INPUT_MOUSEDEV_SCREEN_X
@@ -11372,71 +12648,81 @@
Joystick support
CONFIG_INPUT_JOYDEV
Say Y here if you want your USB HID joystick or gamepad to be
- accessible as char device 13:0+ - /dev/input/jsX device.
+ accessible as char device 13:0+ - /dev/input/jsX device.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called joydev.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
Event interface support
CONFIG_INPUT_EVDEV
- Say Y here if you want your USB or ADB HID device events be accessible
- under char device 13:64+ - /dev/input/eventX in a generic way.
- This is the future ...
+ Say Y here if you want your USB or ADB HID device events be
+ accessible under char device 13:64+ - /dev/input/eventX in a generic
+ way. This is the future ...
USB Scanner support
CONFIG_USB_SCANNER
Say Y here if you want to connect a USB scanner to your computer's
- USB port. Please read Documentation/usb/scanner.txt and
- Documentation/usb/scanner-hp-sane.txt for more information.
+ USB port. Please read <file:Documentation/usb/scanner.txt> and
+ <file:Documentation/usb/scanner-hp-sane.txt> for more information.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called scanner.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
+ a module, say M here and read <file:Documentation/modules.txt>.
+
+HP 5300C scanner support
+CONFIG_USB_HP5300
+ Say Y here if you want to connect a HP5300C scanner to your
+ computer's USB port.
+
+ This code is also available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ The module will be called hp5300.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
USB Audio support
CONFIG_USB_AUDIO
- Say Y here if you want to connect UAB audio equipment such as
+ Say Y here if you want to connect USB audio equipment such as
speakers to your computer's USB port.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called audio.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
USB Modem (CDC ACM) support
CONFIG_USB_ACM
This driver supports USB modems and ISDN adapters which support the
Communication Device Class Abstract Control Model interface.
- Please read Documentation/usb/acm.txt for details.
+ Please read <file:Documentation/usb/acm.txt> for details.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called acm.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
-USB Serial converter support
+USB serial converter support
CONFIG_USB_SERIAL
Say Y here if you have a USB device that provides normal serial
ports, or acts like a serial device, and you want to connect it to
your USB bus.
- Please read Documentation/usb/usb-serial.txt for more information
- on the specifics of the different devices that are supported, and
- on how to use them.
-
+ Please read <file:Documentation/usb/usb-serial.txt> for more
+ information on the specifics of the different devices that are
+ supported, and on how to use them.
+
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called usbserial.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt.
+ The module will be called usbserial.o. If you want to compile it
+ as a module, say M here and read <file:Documentation/modules.txt>.
USB Generic Serial Driver
CONFIG_USB_SERIAL_GENERIC
- Say Y here if you want to use the generic USB serial driver. Please
- read Documentation/usb/usb-serial.txt for more information on using
- this driver. It is recommended that the "USB Serial converter
+ Say Y here if you want to use the generic USB serial driver. Please
+ read <file:Documentation/usb/usb-serial.txt> for more information on
+ using this driver. It is recommended that the "USB Serial converter
support" be compiled as a module for this driver to be used
properly.
@@ -11447,20 +12733,31 @@
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called whiteheat.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ The module will be called whiteheat.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
USB Handspring Visor Driver
CONFIG_USB_SERIAL_VISOR
- Say Y here if you want to connect to your HandSpring Visor, Palm m500
- or m505 through its USB docking station.
- See http://usbvisor.sourceforge.net for more information on using this
+ Say Y here if you want to connect to your HandSpring Visor, Palm
+ m500 or m505 through its USB docking station. See
+ <http://usbvisor.sourceforge.net> for more information on using this
driver.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called visor.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
+
+USB IR Dongle Serial Driver
+CONFIG_USB_SERIAL_IR
+ Say Y here if you want to enable simple serial support for USB IrDA
+ devices. This is useful if you do not want to use the full IrDA
+ stack.
+
+ This code is also available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ The module will be called ir-usb.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
USB Belkin and Paracom Single Port Serial Driver
CONFIG_USB_SERIAL_BELKIN
@@ -11471,20 +12768,21 @@
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called belkin_sa.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
+ a module, say M here and read <file:Documentation/modules.txt>.
USB FTDI Single Port Serial Driver
CONFIG_USB_SERIAL_FTDI_SIO
Say Y here if you want to use a FTDI SIO single port USB to serial
converter device. The implementation I have is called the USC-1000.
+ This driver has also be tested with the 245 and 232 devices.
- See http://reality.sgi.com/bryder_wellington/ftdi_sio for more
+ See http://ftdi-usb-sio.sourceforge.net for more
information on this driver and the device.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called ftdi_sio.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ The module will be called ftdi_sio.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
USB Keyspan PDA Single Port Serial Driver
CONFIG_USB_SERIAL_KEYSPAN_PDA
@@ -11494,8 +12792,8 @@
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called keyspan_pda.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt.
+ The module will be called keyspan_pda.o. If you want to compile it
+ as a module, say M here and read <file:Documentation/modules.txt>.
USB Xircom / Entregra Single Port Serial Driver
CONFIG_USB_SERIAL_XIRCOM
@@ -11513,14 +12811,14 @@
Say Y here if you want to use Keyspan USB to serial converter
devices. This driver makes use of Keyspan's official firmware
and was developed with their support. You must also include
- firmware to support your particular device(s).
+ firmware to support your particular device(s).
+
+ See <http://misc.nu/hugh/keyspan.html> for more information.
- See http://misc.nu/hugh/keyspan.html for more information.
-
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called keyspan.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
USB Keyspan USA-28 Firmware
CONFIG_USB_SERIAL_KEYSPAN_USA28
@@ -11566,8 +12864,8 @@
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called omninet.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ The module will be called omninet.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
USB Digi International AccelePort USB Serial Driver
CONFIG_USB_SERIAL_DIGI_ACCELEPORT
@@ -11581,33 +12879,34 @@
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called digi_acceleport.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ The module will be called digi_acceleport.o. If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>.
USB Empeg empeg-car Mark I/II Driver
CONFIG_USB_SERIAL_EMPEG
Say Y here if you want to connect to your Empeg empeg-car Mark I/II
mp3 player via USB. The driver uses a single ttyUSB{0,1,2,...}
- device node. See Documentation/usb/usb-serial.txt for more
+ device node. See <file:Documentation/usb/usb-serial.txt> for more
tidbits of information.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called empeg.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
USB MCT Single Port Serial Driver
CONFIG_USB_SERIAL_MCT_U232
Say Y here if you want to use a USB Serial single port adapter from
Magic Control Technology Corp. (U232 is one of the model numbers).
-
+
This driver also works with Sitecom U232-P25 and D-Link DU-H3SP USB
BAY devices.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called mct_u232.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
+ a module, say M here and read <file:Documentation/modules.txt>.
USB Prolific 2303 Single Port Serial Driver
CONFIG_USB_SERIAL_PL2303
@@ -11617,19 +12916,19 @@
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called pl2303.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
+ a module, say M here and read <file:Documentation/modules.txt>.
USB REINER SCT cyberJack pinpad/e-com chipcard reader
CONFIG_USB_SERIAL_CYBERJACK
Say Y here if you want to use a cyberJack pinpad/e-com USB chipcard
reader. This is an interface to ISO 7816 compatible contactbased
chipcards, e.g. GSM SIMs.
-
+
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called cyberjack.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
-
+ a module, say M here and read <file:Documentation/modules.txt>.
+
If unsure, say N.
USB Edgeport Serial Driver
@@ -11655,8 +12954,8 @@
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called io_edgeport.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt.
+ The module will be called io_edgeport.o. If you want to compile it
+ as a module, say M here and read <file:Documentation/modules.txt>.
USB Serial Converter verbose debug
CONFIG_USB_SERIAL_DEBUG
@@ -11671,57 +12970,85 @@
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called printer.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
USB IBM (Xirlink) C-It Camera support
CONFIG_USB_IBMCAM
Say Y here if you want to connect a IBM "C-It" camera, also known as
- "Xirlink PC Camera" to your computer's USB port. For more
- information, read Documentation/usb/ibmcam.txt.
+ "Xirlink PC Camera" to your computer's USB port. For more
+ information, read <file:Documentation/usb/ibmcam.txt>.
This driver uses the Video For Linux API. You must enable
(Y or M in config) Video For Linux (under Character Devices)
to use this driver. Information on this API and pointers to
"v4l" programs may be found on the WWW at
- http://roadrunner.swansea.uk.linux.org/v4l.shtml .
+ <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called ibmcam.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt. This camera
- has several configuration options which can be specified when you
- load the module. Read Documentation/usb/ibmcam.txt to learn more.
+ The module will be called ibmcam.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>. This
+ camera has several configuration options which can be specified when
+ you load the module. Read <file:Documentation/usb/ibmcam.txt> to
+ learn more.
USB OV511 Camera support
CONFIG_USB_OV511
Say Y here if you want to connect this type of camera to your
- computer's USB port. See Documentation/usb/ov511.txt for more
+ computer's USB port. See <file:Documentation/usb/ov511.txt> for more
information and for a list of supported cameras.
-
+
This driver uses the Video For Linux API. You must say Y or M to
"Video For Linux" (under Character Devices) to use this driver.
Information on this API and pointers to "v4l" programs may be found
- on the WWW at http://roadrunner.swansea.uk.linux.org/v4l.shtml .
+ on the WWW at <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called ov511.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
+
+USB Communication Class Ethernet driver
+CONFIG_USB_CDCETHER
+ This driver supports devices conforming to the Communication Device
+ Class Ethernet Control Model. This is used in some cable modems.
+ For more details on the specification, get the Communication Device
+ Class specification from <http://www.usb.org>.
+
+ This driver should work with the following devices:
+ * Ericsson PipeRider (all variants)
+ * Motorola (DM100 and SB4100)
+ * Broadcom Cable Modem (reference design)
+ * Toshiba PCX1100U and possibly other cable modems
+
+ The device creates a network device (ethX, where X depends on what
+ other networking devices you have in use), as for a normal PCI
+ or ISA based ethernet network card.
+
+ This code is also available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ The module will be called CDCEther.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
+
+NetChip 1080-based USB Host-to-Host Link
+CONFIG_USB_NET1080
+ The NetChip 1080 is a USB 1.1 host controller. NetChip has a web
+ site with technical information at <http://www.netchip.com/>.
Philips webcam support
CONFIG_USB_PWC
Say Y or M here if you want to use one of these Philips USB webcams:
- PCA645, PCA646, PCVC675, PCVC680, PCVC690, PCVC730, PCVC740, or
- the Askey VC010. The PCA635, PCVC665 and PCVC720 are not
- supported by this driver and never will be.
-
- This driver has an optional plugin, which is distributed as a
- binary module only. It contains code that allow you to use
- higher resolutions and framerates but may not be distributed
- as source. But even without this plugin you can these cams
- for most applications.
+ PCA645, PCA646, PCVC675, PCVC680, PCVC690, PCVC730, PCVC740, or
+ the Askey VC010. The PCA635, PCVC665 and PCVC720 are not supported
+ by this driver and never will be.
+
+ This driver has an optional plugin, which is distributed as a binary
+ module only. It contains code that allow you to use higher
+ resolutions and framerates but may not be distributed as source.
+ But even without this plugin you can these cams for most
+ applications.
- See Documentation/usb/philips.txt for more information and
+ See <file:Documentation/usb/philips.txt> for more information and
installation instructions.
The built-in microphone is enabled by selecting USB Audio support.
@@ -11729,29 +13056,12 @@
This driver uses the Video For Linux API. You must say Y or M to
"Video For Linux" (under Character Devices) to use this driver.
Information on this API and pointers to "v4l" programs may be found
- on the WWW at http://roadrunner.swansea.uk.linux.org/v4l.shtml .
+ on the WWW at <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called pwc.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
-
-
-USB SE401 Camera support
-CONFIG_USB_SE401
- Say Y here if you want to connect this type of camera to your
- computer's USB port. See Documentation/usb/se401.txt for more
- information and for a list of supported cameras.
-
- This driver uses the Video For Linux API. You must say Y or M to
- "Video For Linux" (under Multimedia Devices) to use this driver.
- Information on this API and pointers to "v4l" programs may be found
- on the WWW at http://roadrunner.swansea.uk.linux.org/v4l.shtml .
-
- This code is also available as a module ( = code which can be
- inserted in and removed from the running kernel whenever you want).
- The module will be called se401.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ The module will be called pwc.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
Pegasus/Pegasus II based USB-Ethernet device support
CONFIG_USB_PEGASUS
@@ -11765,8 +13075,9 @@
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called pegasus.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
+USB KLSI KL5USB101-based Ethernet device support '
CONFIG_USB_KAWETH
Say Y here if you want to use one of the following 10Mbps only
USB Ethernet adapters based on the KLSI KL5KUSB101B chipset:
@@ -11783,7 +13094,7 @@
Kingston Technology USB Ethernet Adapter
Linksys USB10T
Mobility USB-Ethernet Adapter
- NetGear EA-101
+ NetGear EA-101
Peracom Enet and Enet2
Portsmith Express Ethernet Adapter
Shark Pocket Adapter
@@ -11815,62 +13126,39 @@
CATC NetMate II
smartBridges smartNIC
+ This driver makes the adapter appear as a normal Ethernet interface,
+ typically on eth0, if it is the only ethernet device, or perhaps on
+ eth1, if you have a PCI or ISA ethernet card installed.
+
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called catc.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
-USB Communication Class Ethernet driver
-CONFIG_USB_CDCETHER
- This driver supports devices conforming to the Communication Device
- Class Ethernet Control Model. This is used in some cable modems.
- For more details on the specification, get the Communication Device
- Class specification from <http://www.usb.org>.
-
- This driver should work with the following devices:
- * Ericsson PipeRider (all variants)
- * Motorola (DM100 and SB4100)
- * Broadcom Cable Modem (reference design)
- * Toshiba PCX1100U and possibly other cable modems
-
- The device creates a network device (ethX, where X depends on what
- other networking devices you have in use), as for a normal PCI
- or ISA based ethernet network card.
-
- This code is also available as a module ( = code which can be
- inserted in and removed from the running kernel whenever you want).
- The module will be called CDCEther.o. If you want to compile it as
- a module, say M here and read <file:Documentation/modules.txt>.
-
-NetChip 1080-based USB Host-to-Host Link
-CONFIG_USB_NET1080
- The NetChip 1080 is a USB 1.1 host controller. NetChip has a web
- site with technical information at http://www.netchip.com/ .
-
USB Kodak DC-2xx Camera support
CONFIG_USB_DC2XX
- Say Y here if you want to connect this type of still camera to
- your computer's USB port. See Documentation/usb/dc2xx.txt for more
- information; some non-Kodak cameras may also work with this
- driver, given application support (such as www.gPhoto.org).
+ Say Y here if you want to connect this type of still camera to your
+ computer's USB port. See <file:Documentation/usb/dc2xx.txt> for
+ more information; some non-Kodak cameras may also work with this
+ driver, given application support (such as <http://www.gPhoto.org>).
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called dc2xx.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
-USB Mustek MDC800 Digital Camera Support
+USB Mustek MDC800 Digital Camera support
CONFIG_USB_MDC800
Say Y here if you want to connect this type of still camera to
your computer's USB port. This driver can be used with gphoto 0.4.3
- and higher (look at http://www.gphoto.org ).
+ and higher (look at <http://www.gphoto.org>).
To use it create a device node with "mknod /dev/mustek c 180 32" and
configure it in your software.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called mdc800.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
USB Mass Storage support
CONFIG_USB_STORAGE
@@ -11880,7 +13168,7 @@
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called usb-storage.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt.
+ as a module, say M here and read <file:Documentation/modules.txt>.
USB Mass Storage verbose debug
CONFIG_USB_STORAGE_DEBUG
@@ -11907,7 +13195,7 @@
Technologies USS-720 chip. These cables are plugged into your USB
port and provide USB compatibility to peripherals designed with
parallel port interfaces.
-
+
The chip has two modes: automatic mode and manual mode. In automatic
mode, it looks to the computer like a standard USB printer. Only
printers may be connected to the USS-720 in this mode. The generic
@@ -11927,29 +13215,33 @@
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called uss720.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
-
+ module, say M here and read <file:Documentation/modules.txt>.
+
USB device file system
CONFIG_USB_DEVICEFS
- If you say Y here (and to "/proc file system support" below), you
- will get a file /proc/bus/usb/devices which lists the devices
- currently connected to your USB busses, a file /proc/bus/usb/drivers
- which lists the USB kernel client drivers currently loaded, and for
- every connected device a file named "/proc/bus/usb/xxx/yyy", where
- xxx is the bus number and yyy the device number; the latter files
- can be used by user space programs to talk directly to the device.
- These files are "virtual", meaning they are generated on the fly
- and not stored on the hard drive.
-
- For the format of the /proc/bus/usb/ files, please read
- Documentation/usb/proc_usb_info.txt.
+ If you say Y here (and to "/proc file system support" in the "File
+ systems section, above), you will get a file /proc/bus/usb/devices
+ which lists the devices currently connected to your USB bus or
+ busses, a file /proc/bus/usb/drivers which lists the USB kernel
+ client drivers currently loaded, and for every connected device a
+ file named "/proc/bus/usb/xxx/yyy", where xxx is the bus number and
+ yyy the device number; the latter files can be used by user space
+ programs to talk directly to the device. These files are "virtual",
+ meaning they are generated on the fly and not stored on the hard
+ drive.
+
+ You may need to mount the usbdevfs file system to see the files, use
+ mount -t usbdevfs none /proc/bus/usb
+
+ For the format of the various /proc/bus/usb/ files, please read
+ <file:Documentation/usb/proc_usb_info.txt>.
Please note that this code is completely unrelated to devfs, the
"/dev file system support".
Most users want to say Y here.
-USB Bandwidth allocation
+Enforce USB bandwidth allocation
CONFIG_USB_BANDWIDTH
If you say Y here, the USB subsystem enforces USB bandwidth
allocation and will prevent some device opens from succeeding
@@ -11963,23 +13255,25 @@
DABUSB driver
CONFIG_USB_DABUSB
A Digital Audio Broadcasting (DAB) Receiver for USB and Linux
- brought to you by the DAB-Team (http://dab.in.tum.de). This driver
- can be taken as an example for URB-based bulk, control, and
+ brought to you by the DAB-Team (<http://dab.in.tum.de>). This
+ driver can be taken as an example for URB-based bulk, control, and
isochronous transactions. URB's are explained in
- Documentation/usb/URB.txt.
+ <file:Documentation/usb/URB.txt>.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called dabusb.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ The module will be called dabusb.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
Host-to-Host USB networking
CONFIG_USB_USBNET
This driver supports network links over USB with USB "Network"
or "data transfer" cables, often used to network laptops to PCs.
- Such cables have chips from suppliers such as NetChip and Prolific.
- Intelligent USB devices could also use this approach to provide
- Internet access, using standard USB cabling.
+ Such cables have chips from suppliers such as Belkin/eTEK, GeneSys
+ (GeneLink), NetChip and Prolific. Intelligent USB devices could also
+ use this approach to provide Internet access, using standard USB
+ cabling. You can find these chips also on some motherboards with
+ USB PC2PC support.
These links will have names like "usb0", "usb1", etc. They act
like two-node Ethernets, so you can use 802.1d Ethernet Bridging
@@ -11990,16 +13284,32 @@
The module will be called usbnet.o. If you want to compile it as a
module, say M here and read <file:Documentation/modules.txt>.
+Freecom USB/ATAPI Bridge support
+CONFIG_USB_STORAGE_FREECOM
+ Support for the Freecom USB to IDE/ATAPI adaptor.
+ Freecom has a web page at <http://www.freecom.de/>.
+
+Microtech CompactFlash/SmartMedia reader
+CONFIG_USB_STORAGE_DPCM
+ Say Y here to support the Microtech ZiO! CompactFlash/SmartMedia
+ reader, details at <http://www.microtechint.com/zio/index.html>.
+ This driver treats the flash card as a removable storage device.
+
+Sandisk SDDR-09 SmartMedia reader support
+CONFIG_USB_STORAGE_SDDR09
+ Say Y here to include additional code to support the Sandisk SDDR-09
+ SmartMedia reader in the USB Mass Storage driver.
+
USB Diamond Rio500 support
CONFIG_USB_RIO500
Say Y here if you want to connect a USB Rio500 mp3 player to your
- computer's USB port. Please read Documentation/usb/rio.txt
+ computer's USB port. Please read <file:Documentation/usb/rio.txt>
for more information.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called rio500.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
+ a module, say M here and read <file:Documentation/modules.txt>.
D-Link DSB-R100 FM radio support
CONFIG_USB_DSBR
@@ -12012,18 +13322,256 @@
(Y or M in config) Video For Linux (under Character Devices)
to use this driver. Information on this API and pointers to
"v4l" programs may be found on the WWW at
- http://roadrunner.swansea.uk.linux.org/v4l.shtml .
+ <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called dsbr100.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
+
+Always do synchronous disk IO for UBD
+CONFIG_BLK_DEV_UBD_SYNC
+ The User-Mode Linux port includes a driver called UBD which will let
+ you access arbitrary files on the host computer as block devices.
+ Writes to such a block device are not immediately written to the
+ host's disk; this may cause problems if, for example, the User-Mode
+ Linux 'Virtual Machine' uses a journalling file system and the host
+ computer crashes.
+
+ Synchronous operation (i.e. always writing data to the host's disk
+ immediately) is configurable on a per-UBD basis by using a special
+ kernel command line option. Alternatively, you can say Y here to
+ turn on synchronous operation by default for all block.
+
+ If you're running a journalling file system (like reiserfs, for
+ example) in your virtual machine, you will want to say Y here. If
+ you care for the safety of the data in your virtual machine, Y is a
+ wise choice too. In all other cases (for example, if you're just
+ playing around with User-Mode Linux) you can choose N.
+
+Enable ptrace proxy
+CONFIG_PT_PROXY
+ This option enables a debugging interface which allows gdb to debug
+ the kernel without needing to actually attach to kernel threads.
+ If you want to do kernel debugging, say Y here; otherwise say N.
+
+Management console
+CONFIG_MCONSOLE
+ The user mode linux management console is a low-level interface to
+ the kernel, somewhat like the i386 SysRq interface. Since there is
+ a full-blown operating system running under every user mode linux
+ instance, there is much greater flexibility possible than with the
+ SysRq mechanism.
+
+ If you answer 'Y' to this option, to use this feature, you need the
+ mconsole client (called uml_mconsole) which is present in CVS in
+ 2.4.5-9um and later (path /tools/mconsole), and is also in the
+ distribution RPM package in 2.4.6 and later.
+
+ It is safe to say 'Y' here.
+
+Enable kernel debugging symbols
+CONFIG_DEBUGSYM
+ When this is enabled, the User-Mode Linux binary will include
+ debugging symbols. This enlarges the binary by a few megabytes,
+ but aids in tracking down kernel problems in UML. It is required
+ if you intend to do any kernel development.
+
+ If you're truly short on disk space or don't expect to report any
+ bugs back to the UML developers, say N, otherwise say Y.
+
+Enable gcov support
+CONFIG_GCOV
+ This option allows developers to retrieve coverage data from a UML
+ session.
+
+ See <http://user-mode-linux.sourceforge.net/gcov.html> for more
+ details.
+
+ If you're involved in UML kernel development and want to use gcov,
+ say Y. If you're unsure, say N.
+
+Enable gprof support
+CONFIG_GPROF
+ This allows profiling of a User-Mode Linux kernel with the gprof
+ utility.
+
+ See <http://user-mode-linux.sourceforge.net/gprof.html> for more
+ details.
+
+ If you're involved in UML kernel development and want to use gprof,
+ say Y. If you're unsure, say N.
+
+Host filesystem
+CONFIG_HOSTFS
+ While the User-Mode Linux port uses its own root file system for
+ booting and normal file access, this module lets the UML user
+ access files stored on the host. It does not require any
+ network connection between the Host and UML. An example use of
+ this might be:
+
+ mount none /tmp/fromhost -t hostfs -o /tmp/umlshare
+
+ where /tmp/fromhost is an empty directory inside UML and
+ /tmp/umlshare is a directory on the host with files the UML user
+ wishes to access.
+
+ For more information, see
+ <http://user-mode-linux.sourceforge.net/hostfs.html>.
+
+ If you'd like to be able to work with files stored on the host,
+ say Y or M here; otherwise say N.
+
+Example IO Memory driver
+CONFIG_MMAPPER
+ The User-Mode Linux port can provide support for IO Memory
+ emulation with this option. This allows a host file to be
+ specified as an I/O region on the kernel command line. That file
+ will be mapped into UML's kernel address space where a driver can
+ locate it and do whatever it wants with the memory, including
+ providing an interface to it for UML processes to use.
+
+ For more information, see
+ <http://user-mode-linux.sourceforge.net/iomem.html>.
+
+ If you'd like to be able to provide a simulated IO port space for
+ User-Mode Linux processes, say Y. If unsure, say N.
+
+Virtual Serial Line
+CONFIG_SSL
+ The User-Mode Linux environment allows you to create virtual serial
+ lines on the UML that are usually made to show up on the host as
+ ttys or ptys.
+
+ See <http://user-mode-linux.sourceforge.net/input.html> for more
+ information and command line examples of how to use this facility.
+
+ Unless you have a specific reason for disabling this, say Y.
+
+Virtual network device
+CONFIG_UML_NET
+ While the User-Mode port cannot directly talk to any physical
+ hardware devices, this choice and the following transport options
+ provide one or more virtual network devices through which the UML
+ kernels can talk to each other, the host, and with the host's help,
+ machines on the outside world.
+
+ For more information, including explations of the networking and
+ sample configurations, see
+ <http://user-mode-linux.sourceforge.net/networking.html>.
+
+ If you'd like to be able to enable networking in the User-Mode
+ linux environment, say Y; otherwise say N. Note that you must
+ enable at least one of the following transport options to actually
+ make use of UML networking.
+
+Daemon transport
+CONFIG_UML_NET_DAEMON
+ This User-Mode Linux network transport allows one or more running
+ UMLs on a single host to communicate with each other, but not to
+ the host.
+
+ To use this form of networking, you'll need to run the UML
+ networking daemon on the host.
+
+ For more information, see
+ <http://user-mode-linux.sourceforge.net/networking.html> That site
+ has examples of the UML command line to use to enable Daemon
+ networking.
+
+ If you'd like to set up a network with other UMLs on a single host,
+ say Y. If you need a network between UMLs on multiple physical
+ hosts, choose the Multicast Transport. To set up a network with
+ the host and/or other IP machines, say Y to the Ethertap or Slip
+ transports. You'll need at least one of them, but may choose
+ more than one without conflict. If you don't need UML networking,
+ say N.
+
+Ethertap transport
+CONFIG_UML_NET_ETHERTAP
+ The Ethertap User-Mode Linux network transport allows a single
+ running UML to exchange packets with its host over one of the
+ host's Ethertap devices, such as /dev/tap0. Additional running
+ UMLs can use additional Ethertap devices, one per running UML.
+ While the UML believes its on a (multi-device, broadcast) virtual
+ Ethernet network, it's in fact communicating over a point-to-point
+ link with the host.
+
+ To use this, your host kernel must have support for Ethertap
+ devices. Also, if your host kernel is 2.4.x, it must have
+ CONFIG_NETLINK_DEV configured as Y or M.
+
+ For more information, see
+ <http://user-mode-linux.sourceforge.net/networking.html> That site
+ has examples of the UML command line to use to enable Ethertap
+ networking.
+
+ If you'd like to set up an IP network with the host and/or the
+ outside world, say Y to this, the Daemon Transport and/or the
+ Slip Transport. You'll need at least one of them, but may choose
+ more than one without conflict. If you don't need UML networking,
+ say N.
+
+TUN/TAP transport
+CONFIG_UML_NET_TUNTAP
+ The UML TUN/TAP network transport allows a UML instance to exchange
+ packets with the host over a TUN/TAP device. This option will only
+ work with a 2.4 host, unless you've applied the TUN/TAP patch to
+ your 2.2 host kernel.
+
+ To use this transport, your host kernel must have support for TUN/TAP
+ devices, either built-in or as a module.
+
+Multicast transport
+CONFIG_UML_NET_MCAST
+ This Multicast User-Mode Linux network transport allows multiple
+ UMLs (even ones running on different host machines!) to talk to
+ each other over a virtual ethernet network. However, it requires
+ at least one UML with one of the other transports to act as a
+ bridge if any of them need to be able to talk to their hosts or any
+ other IP machines.
+
+ To use this, your host kernel(s) must support IP Multicasting.
+
+ For more information, see
+ <http://user-mode-linux.sourceforge.net/networking.html> That site
+ has examples of the UML command line to use to enable Multicast
+ networking, and notes about the security of this approach.
+
+ If you need UMLs on multiple physical hosts to communicate as if
+ they shared an Ethernet network, say Y. If you need to communicate
+ with other IP machines, make sure you select one of the other
+ transports (possibly in addition to Multicast; they're not
+ exclusive). If you don't need to network UMLs say N to each of
+ the transports.
+
+SLIP transport
+CONFIG_UML_NET_SLIP
+ The Slip User-Mode Linux network transport allows a running UML to
+ network with its host over a point-to-point link. Unlike Ethertap,
+ which can carry any Ethernet frame (and hence even non-IP packets),
+ the Slip transport can only carry IP packets.
+
+ To use this, your host must support Slip devices.
+
+ For more information, see
+ <http://user-mode-linux.sourceforge.net/networking.html>. That site
+ has examples of the UML command line to use to enable Slip
+ networking, and details of a few quirks with it.
+
+ The Ethertap Transport is preferred over Slip because of its
+ limitation. If you prefer Slip, however, say Y here. Otherwise
+ choose the Multicast transport (to network multiple UMLs on
+ multiple hosts), Ethertap (to network with the host and the
+ outside world), and/or the Daemon transport (to network multiple
+ UMLs on a single host). You may choose more than one without
+ conflict. If you don't need UML networking, say N.
Microtek USB scanner support
CONFIG_USB_MICROTEK
Say Y here if you want support for the Microtek X6USB and
possibly the Phantom 336CX, Phantom C6 and ScanMaker V6U(S)L.
- Support for anything but the X6 is experimetal.
+ Support for anything but the X6 is experimental.
Please report failures and successes.
The scanner will appear as a scsi generic device to the rest
of the system. Scsi support is required for this driver to compile
@@ -12040,14 +13588,14 @@
CONFIG_USB_BLUETOOTH
Say Y here if you want to connect a USB Bluetooth device to your
computer's USB port. You will need the Bluetooth stack (available
- at http://developer.axis.com/software/index.shtml) to fully use
+ at <http://developer.axis.com/software/index.shtml)> to fully use
the device.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called bluetooth.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
-
+ The module will be called bluetooth.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
+
Minix fs support
CONFIG_MINIX_FS
Minix is a simple operating system used in many classes about OS's.
@@ -12056,58 +13604,75 @@
but has been superseded by the second extended file system ext2fs.
You don't want to use the minix file system on your hard disk
because of certain built-in restrictions, but it is sometimes found
- on older Linux floppy disks. This option will enlarge your kernel by
- about 28 KB. If unsure, say N.
+ on older Linux floppy disks. This option will enlarge your kernel
+ by about 28 KB. If unsure, say N.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called minix.o. Note that the file system of your root partition
- (the one containing the directory /) cannot be compiled as a module.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called minix.o. Note that the file system of your root
+ partition (the one containing the directory /) cannot be compiled as
+ a module.
Reiserfs support
CONFIG_REISERFS_FS
-
Stores not just filenames but the files themselves in a balanced
tree. Uses journaling.
- Balanced trees are more efficient than traditional
- filesystem architectural foundations.
+ Balanced trees are more efficient than traditional file system
+ architectural foundations.
- In general, ReiserFS is as fast as ext2, but is very efficient
- with large directories and small files. Additional patches are
- needed for NFS and quotas, please see www.reiserfs.org for
- links.
+ In general, ReiserFS is as fast as ext2, but is very efficient with
+ large directories and small files. Additional patches are needed
+ for NFS and quotas, please see <http://www.reiserfs.org> for links.
It is more easily extended to have features currently found in
- database and keyword search systems than block allocation based
- filesystems are. The next version will be so extended, and will
- support plugins consistent with our motto ``It takes more than a
- license to make source code open.''
+ database and keyword search systems than block allocation based file
+ systems are. The next version will be so extended, and will support
+ plugins consistent with our motto ``It takes more than a license to
+ make source code open.''
- Read www.reiserfs.org to learn more about reiserfs.
+ Read <http://www.reiserfs.org> to learn more about reiserfs.
Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com.
If you like it, you can pay us to add new features to it that you
need, buy a support contract, or pay us to port it to another OS.
-Enable Reiserfs consistency checks
+Enable extra Reiserfs consistency checks
CONFIG_REISERFS_CHECK
- If you set this to yes, then ReiserFS will perform every check it
- can possibly imagine of its internal consistency throughout its
+ If you set this to Y, then ReiserFS will perform every check it can
+ possibly imagine of its internal consistency throughout its
operation. It will also go substantially slower. More than once we
have forgotten that this was on, and then gone despondent over the
latest benchmarks.:-) Use of this option allows our team to go all
out in checking for consistency when debugging without fear of its
effect on end users. If you are on the verge of sending in a bug
- report, say yes and you might get a useful error message. Almost
- everyone should say no.
+ report, say Y and you might get a useful error message. Almost
+ everyone should say N.
+
+Publish some reiserfs-specific info under /proc/fs/reiserfs
+CONFIG_REISERFS_PROC_INFO
+ Create under /proc/fs/reiserfs hierarchy of files, displaying
+ various ReiserFS statistics and internal data on the expense of
+ making your kernel or module slightly larger (+8 KB). This also
+ increases amount of kernel memory required for each mount. Almost
+ everyone but ReiserFS developers and people fine-tuning reiserfs or
+ tracing problems should say N.
+
+Publish some reiserfs-specific info under /proc/fs/reiserfs
+CONFIG_REISERFS_PROC_INFO
+ Create under /proc/fs/reiserfs hierarchy of files, displaying
+ various ReiserFS statistics and internal data on the expense of
+ making your kernel or module slightly larger (+8K). This also increases
+ amount of kernel memory required for each mount. Almost everyone
+ but ReiserFS developers and people fine-tuning reiserfs or tracing
+ problems should say NO.
Second extended fs support
CONFIG_EXT2_FS
This is the de facto standard Linux file system (method to organize
- files on a storage device) for hard disks.
+ files on a storage device) for hard disks.
You want to say Y here, unless you intend to use Linux exclusively
from inside a DOS partition using the UMSDOS file system. The
@@ -12125,70 +13690,151 @@
by about 44 KB.
The Ext2fs-Undeletion mini-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto , gives information about
+ <http://www.linuxdoc.org/docs.html#howto>, gives information about
how to retrieve deleted files on ext2fs file systems.
To change the behavior of ext2 file systems, you can use the tune2fs
utility ("man tune2fs"). To modify attributes of files and
directories on ext2 file systems, use chattr ("man chattr").
-
+
Ext2fs partitions can be read from within DOS using the ext2tool
command line tool package (available via FTP (user: anonymous) from
- ftp://metalab.unc.edu/pub/Linux/system/filesystems/ext2 ) and from
+ <ftp://metalab.unc.edu/pub/Linux/system/filesystems/ext2>) and from
within Windows NT using the ext2nt command line tool package from
- ftp://metalab.unc.edu/pub/Linux/utils/dos . Explore2fs is a
+ <ftp://metalab.unc.edu/pub/Linux/utils/dos>. Explore2fs is a
graphical explorer for ext2fs partitions which runs on Windows 95
and Windows NT and includes experimental write support; it is
available from
- http://jnewbigin-pc.it.swin.edu.au/Linux/Explore2fs.htm .
+ <http://jnewbigin-pc.it.swin.edu.au/Linux/Explore2fs.htm>.
+
+ If you want to compile this file system as a module ( = code which
+ can be inserted in and removed from the running kernel whenever you
+ want), say M here and read <file:Documentation/modules.txt>. The
+ module will be called ext2.o. Be aware however that the file system
+ of your root partition (the one containing the directory /) cannot
+ be compiled as a module, and so this could be dangerous. Most
+ everyone wants to say Y here.
+
+Ext3 journaling file system support (EXPERIMENTAL)
+CONFIG_EXT3_FS
+ This is the journaling version of the Second extended file system
+ (often called ext3), the de facto standard Linux file system
+ (method to organize files on a storage device) for hard disks.
+
+ The journaling code included in this driver means you do not have
+ to run e2fsck (file system checker) on your file systems after a
+ crash. The journal keeps track of any changes that were being made
+ at the time the system crashed, and can ensure that your file system
+ is consistent without the need for a lengthy check.
+
+ Other than adding the journal to the file system, the on-disk format
+ of ext3 is identical to ext2. It is possible to freely switch
+ between using the ext3 driver and the ext2 driver, as long as the
+ file system has been cleanly unmounted, or e2fsck is run on the file
+ system.
+
+ To add a journal on an existing ext2 file system or change the
+ behavior of ext3 file systems, you can use the tune2fs utility ("man
+ tune2fs"). To modify attributes of files and directories on ext3
+ file systems, use chattr ("man chattr"). You need to be using
+ e2fsprogs version 1.20 or later in order to create ext3 journals
+ (available at <http://sourceforge.net/projects/e2fsprogs/>).
If you want to compile this file system as a module ( = code which
can be inserted in and removed from the running kernel whenever you
- want), say M here and read Documentation/modules.txt. The module
- will be called ext2.o. Be aware however that the file system of your
- root partition (the one containing the directory /) cannot be
- compiled as a module, and so this could be dangerous. Most everyone
- wants to say Y here.
+ want), say M here and read <file:Documentation/modules.txt>. The
+ module will be called ext3.o. Be aware however that the file system
+ of your root partition (the one containing the directory /) cannot
+ be compiled as a module, and so this may be dangerous.
-BFS file system support (EXPERIMENTAL)
+Journal Block Device support (JBD for ext3) (EXPERIMENTAL)
+CONFIG_JBD
+ This is a generic journaling layer for block devices. It is
+ currently used by the ext3 file system, but it could also be used to
+ add journal support to other file systems or block devices such as
+ RAID or LVM.
+
+ If you are using the ext3 file system, you need to say Y here. If
+ you are not using ext3 then you will probably want to say N.
+
+ If you want to compile this device as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want),
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called jbd.o. If you are compiling ext3 into the kernel,
+ you cannot compile this code as a module.
+
+JBD (ext3) debugging support
+CONFIG_JBD_DEBUG
+ If you are using the ext3 journaled file system (or potentially any
+ other file system/device using JBD), this option allows you to
+ enable debugging output while the system is running, in order to
+ help track down any problems you are having. By default the
+ debugging output will be turned off.
+
+ If you select Y here, then you will be able to turn on debugging
+ with "echo N > /proc/sys/fs/jbd-debug", where N is a number between
+ 1 and 5, the higher the number, the more debugging output is
+ generated. To turn debugging off again, do
+ "echo 0 > /proc/sys/fs/jbd-debug".
+
+Buffer Head tracing (DEBUG)
+CONFIG_BUFFER_DEBUG
+ If you are a kernel developer working with file systems or in the
+ block device layer, this buffer head tracing may help you to track
+ down bugs in your code. This enables some debugging macros
+ (BUFFER_TRACE, etc.) which allow you to track the state of a buffer
+ through various layers of code. The debugging code is used
+ primarily by ext3 and JBD code.
+
+ Because this option adds considerably to the size of each buffer,
+ most people will want to say N here.
+
+BFS file system support
CONFIG_BFS_FS
Boot File System (BFS) is a file system used under SCO UnixWare to
allow the bootloader access to the kernel image and other important
- files during the boot process. It is usually mounted under /stand
+ files during the boot process. It is usually mounted under /stand
and corresponds to the slice marked as "STAND" in the UnixWare
- partition. You should say Y if you want to read or write
- the files on your /stand slice from within Linux. You then also
- need to say Y to "UnixWare slices support", below. More information
- about the BFS file system is contained in the file
- Documentation/filesystems/bfs.txt.
+ partition. You should say Y if you want to read or write the files
+ on your /stand slice from within Linux. You then also need to say Y
+ to "UnixWare slices support", below. More information about the BFS
+ file system is contained in the file
+ <file:Documentation/filesystems/bfs.txt>.
If you don't know what this is about, say N.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called bfs.o. Note that the file system of your root partition (the
- one containing the directory /) cannot be compiled as a module.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called bfs.o. Note that the file system of your root
+ partition (the one containing the directory /) cannot be compiled as
+ a module.
Compressed ROM file system support
CONFIG_CRAMFS
Saying Y here includes support for CramFs (Compressed ROM File
- System). Cramfs is designed to be a simple, small, and compressed
- file system for ROM based embedded systems. CramFs is read-only,
+ System). CramFs is designed to be a simple, small, and compressed
+ file system for ROM based embedded systems. CramFs is read-only,
limited to 256MB file systems (with 16MB files), and doesn't support
16/32 bits uid/gid, hard links and timestamps.
-
- See Documentation/filesystems/cramfs.txt and fs/cramfs/README
- for further information.
+
+ See <file:Documentation/filesystems/cramfs.txt> and
+ <file:fs/cramfs/README> for further information.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called cramfs.o. Note that the root file system (the one containing
- the directory /) cannot be compiled as a module.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called cramfs.o. Note that the root file system (the one
+ containing the directory /) cannot be compiled as a module.
If unsure, say N.
-
+
+CMS file system support
+CONFIG_CMS_FS
+ Read only support for CMS minidisk file systems found on IBM
+ mainframe systems. Only the basic format is supported so far. If
+ you don't know what CMS is you probably don't want to know any more.
+
Virtual memory file system support
CONFIG_TMPFS
Tmpfs is a file system which keeps all files in virtual memory.
@@ -12200,8 +13846,8 @@
Everything is "virtual" in the sense that no files will be created
on your hard drive; if you reboot, everything in tmpfs will be
lost.
-
- You should mount the filesystem somewhere to be able to use
+
+ You should mount the file system somewhere to be able to use
POSIX shared memory. Adding the following line to /etc/fstab should
take care of things:
@@ -12211,10 +13857,10 @@
if necessary (/dev/shm is automagically created if you use devfs).
You can set limits for the number of blocks and inodes used by the
- filesystem with the mount options "size", "nr_blocks" and
+ file system with the mount options "size", "nr_blocks" and
"nr_inodes". These parameters accept a suffix k, m or g for kilo,
mega and giga and can be changed on remount.
-
+
The initial permissions of the root directory can be set with the
mount option "mode".
@@ -12223,40 +13869,40 @@
Ramfs is a file system which keeps all files in RAM. It allows
read and write access.
- It is more of an programming example than a useable filesystem. If
+ It is more of an programming example than a useable file system. If
you need a file system which lives in RAM with limit checking use
tmpfs.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called ramfs.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called ramfs.o.
-ISO 9660 CDROM file system support
+ISO 9660 CD-ROM file system support
CONFIG_ISO9660_FS
- This is the standard file system used on CDROMs. It was previously
+ This is the standard file system used on CD-ROMs. It was previously
known as "High Sierra File System" and is called "hsfs" on other
- Unix systems. The so-called Rock-Ridge extensions which allow for
+ Unix systems. The so-called Rock-Ridge extensions which allow for
long Unix filenames and symbolic links are also supported by this
- driver. If you have a CDROM drive and want to do more with it than
+ driver. If you have a CD-ROM drive and want to do more with it than
just listen to audio CDs and watch its LEDs, say Y (and read
- Documentation/filesystems/isofs.txt and the CDROM-HOWTO, available
- from http://www.linuxdoc.org/docs.html#howto ), thereby enlarging
- your kernel by about 27 KB; otherwise say N.
+ <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
+ available from <http://www.linuxdoc.org/docs.html#howto>), thereby
+ enlarging your kernel by about 27 KB; otherwise say N.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called isofs.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called isofs.o.
-Microsoft Joliet CDROM extensions
+Microsoft Joliet CD-ROM extensions
CONFIG_JOLIET
- Joliet is a Microsoft extension for the ISO 9660 CDROM file system
+ Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
which allows for long filenames in unicode format (unicode is the
new 16 bit character code, successor to ASCII, which encodes the
characters of almost all languages of the world; see
- http://www.unicode.org for more information). Say Y here if you want
- to be able to read Joliet CDROMs under Linux.
+ <http://www.unicode.org> for more information). Say Y here if you
+ want to be able to read Joliet CD-ROMs under Linux.
Transparent decompression extension
CONFIG_ZISOFS
@@ -12267,21 +13913,21 @@
necessary to create such a filesystem. Say Y here if you want to be
able to read such compressed CD-ROMs.
-UDF File System support (read only)
+UDF file system support (read-only)
CONFIG_UDF_FS
- This is the new file system used on some CDROMs and DVDs. Say Y if
+ This is the new file system used on some CD-ROMs and DVDs. Say Y if
you intend to mount DVD discs or CDRW's written in packet mode, or
if written to by other UDF utilities, such as DirectCD. This UDF
file system support is read-only. If you want to write to UDF
file systems on some media, you need to say Y to "UDF read-write
support" below in addition. Please read
- Documentation/filesystems/udf.txt.
+ <file:Documentation/filesystems/udf.txt>.
This file system support is also available as a module ( = code
which can be inserted in and removed from the running kernel
whenever you want). The module is called udf.o. If you want to
compile it as a module, say M here and read
- Documentation/modules.txt.
+ <file:Documentation/modules.txt>.
If unsure, say N.
@@ -12315,23 +13961,23 @@
Linux box, say Y here, mount the floppy under Linux with an MSDOS
file system and use GNU tar's M option. GNU tar is a program
available for Unix and DOS ("man tar" or "info tar").
-
+
It is now also becoming possible to read and write compressed FAT
- file systems; read Documentation/filesystems/fat_cvf.txt for
+ file systems; read <file:Documentation/filesystems/fat_cvf.txt> for
details.
-
+
The FAT support will enlarge your kernel by about 37 KB. If unsure,
say Y.
If you want to compile this as a module however ( = code which can
be inserted in and removed from the running kernel whenever you
- want), say M here and read Documentation/modules.txt. The module
- will be called fat.o. Note that if you compile the FAT support as a
- module, you cannot compile any of the FAT-based file systems into
- the kernel -- they will have to be modules as well. The file system
- of your root partition (the one containing the directory /) cannot
- be a module, so don't say M here if you intend to use UMSDOS as your
- root file system.
+ want), say M here and read <file:Documentation/modules.txt>. The
+ module will be called fat.o. Note that if you compile the FAT
+ support as a module, you cannot compile any of the FAT-based file
+ systems into the kernel -- they will have to be modules as well.
+ The file system of your root partition (the one containing the
+ directory /) cannot be a module, so don't say M here if you intend
+ to use UMSDOS as your root file system.
MSDOS fs support
CONFIG_MSDOS_FS
@@ -12339,8 +13985,8 @@
they are compressed; to access compressed MSDOS partitions under
Linux, you can either use the DOS emulator DOSEMU, described in the
DOSEMU-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto , or try dmsdosfs in
- ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs . If you
+ <http://www.linuxdoc.org/docs.html#howto>, or try dmsdosfs in
+ <ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs>. If you
intend to use dosemu with a non-compressed MSDOS partition, say Y
here) and MSDOS floppies. This means that file access becomes
transparent, i.e. the MSDOS files look and behave just like all
@@ -12359,32 +14005,33 @@
answer Y. This will only work if you said Y to "DOS FAT fs support"
as well. If you want to compile this as a module however ( = code
which can be inserted in and removed from the running kernel
- whenever you want), say M here and read Documentation/modules.txt.
+ whenever you want), say M here and read
+ <file:Documentation/modules.txt>.
The module will be called msdos.o.
VFAT (Windows-95) fs support
CONFIG_VFAT_FS
This option provides support for normal Windows file systems with
- long filenames. That includes non-compressed FAT-based file systems
+ long filenames. That includes non-compressed FAT-based file systems
used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
programs from the mtools package.
You cannot use the VFAT file system for your Linux root partition
(the one containing the directory /); use UMSDOS instead if you
want to run Linux from within a DOS partition (i.e. say Y to
- "UMSDOS: Unix like fs on top of std MSDOS fs", below).
+ "Unix like fs on top of std MSDOS fs", below).
The VFAT support enlarges your kernel by about 10 KB and it only
- works if you said Y to the "DOS FAT fs support" above. Please read
- the file Documentation/filesystems/vfat.txt for details. If unsure,
- say Y.
+ works if you said Y to the "DOS FAT fs support" above. Please read
+ the file <file:Documentation/filesystems/vfat.txt> for details. If
+ unsure, say Y.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called vfat.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called vfat.o.
-UMSDOS: Unix-like file system on top of standard MSDOS fs
+Unix-like file system on top of standard MSDOS fs
CONFIG_UMSDOS_FS
Say Y here if you want to run Linux from within an existing DOS
partition of your hard drive. The advantage of this is that you can
@@ -12392,34 +14039,25 @@
backing everything up and restoring afterwards) and hence you're
able to quickly try out Linux or show it to your friends; the
disadvantage is that Linux becomes susceptible to DOS viruses and
- that UMSDOS is somewhat slower than ext2fs. Another use of UMSDOS
+ that UMSDOS is somewhat slower than ext2fs. Another use of UMSDOS
is to write files with long unix filenames to MSDOS floppies; it
also allows Unix-style soft-links and owner/permissions of files on
- MSDOS floppies. You will need a program called umssync in order to
- make use of UMSDOS; read Documentation/filesystems/umsdos.txt.
+ MSDOS floppies. You will need a program called umssync in order to
+ make use of UMSDOS; read
+ <file:Documentation/filesystems/umsdos.txt>.
To get utilities for initializing/checking UMSDOS file system, or
latest patches and/or information, visit the UMSDOS home page at
- http://www.voyager.hr/~mnalis/umsdos/ .
+ <http://www.voyager.hr/~mnalis/umsdos/>.
This option enlarges your kernel by about 28 KB and it only works if
you said Y to both "DOS FAT fs support" and "MSDOS fs support"
- above. If you want to compile this as a module ( = code which can be
- inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called umsdos.o. Note that the file system of your root partition
- (the one containing the directory /) cannot be a module, so saying M
- could be dangerous. If unsure, say N.
-
-PReP residual data support
-CONFIG_PREP_RESIDUAL
- Some PReP systems have residual data passed to the kernel by the
- firmware. This allows detection of memory size, devices present and
- other useful pieces of information. Sometimes this information is not
- present or incorrect.
-
- Unless you expect to boot on a PReP system, there is not need to select
- yes.
+ above. If you want to compile this as a module ( = code which can
+ be inserted in and removed from the running kernel whenever you
+ want), say M here and read <file:Documentation/modules.txt>. The
+ module will be called umsdos.o. Note that the file system of your
+ root partition (the one containing the directory /) cannot be a
+ module, so saying M could be dangerous. If unsure, say N.
/proc file system support
CONFIG_PROC_FS
@@ -12427,7 +14065,7 @@
of the system. "Virtual" means that it doesn't take up any space on
your hard disk: the files are created on the fly by the kernel when
you try to access them. Also, you cannot read the files with older
- version of the program less: you need to use more or cat.
+ version of the program less: you need to use more or cat.
It's totally cool; for example, "cat /proc/interrupts" gives
information about what the different IRQs are used for at the moment
@@ -12443,13 +14081,23 @@
/proc" or the equivalent line in /etc/fstab does the job.
The /proc file system is explained in the file
- Documentation/filesystems/proc.txt and on the proc(5) manpage ("man
- 5 proc").
+ <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage
+ ("man 5 proc").
This option will enlarge your kernel by about 67 KB. Several
programs depend on this, so everyone should say Y here.
-/dev file system support (EXPERIMENTAL)
+Support for PReP Residual Data
+CONFIG_PREP_RESIDUAL
+ Some PReP systems have residual data passed to the kernel by the
+ firmware. This allows detection of memory size, devices present and
+ other useful pieces of information. Sometimes this information is
+ not present or incorrect.
+
+ Unless you expect to boot on a PReP system, there is not need to
+ select Y.
+
+/dev file system support
CONFIG_DEVFS_FS
This is support for devfs, a virtual file system (like /proc) which
provides the file system interface to device drivers, normally found
@@ -12460,12 +14108,12 @@
/dev directory using the mknod command (or MAKEDEV script) anymore.
This is work in progress. If you want to use this, you *must* read
- the material in Documentation/filesystems/devfs/, especially the
- file README there.
+ the material in <file:Documentation/filesystems/devfs/>, especially
+ the file README there.
If unsure, say N.
-Enable automatic mounting at boot
+Automatically mount devfs at boot time
CONFIG_DEVFS_MOUNT
This option appears if you have CONFIG_DEVFS_FS enabled. Setting
this to 'Y' will make the kernel automatically mount devfs onto /dev
@@ -12478,8 +14126,9 @@
CONFIG_DEVFS_DEBUG
If you say Y here, then the /dev file system code will generate
debugging messages. See the file
- Documentation/filesystems/devfs/boot-options for more details.
-
+ <file:Documentation/filesystems/devfs/boot-options> for more
+ details.
+
If unsure, say N.
NFS file system support
@@ -12493,35 +14142,35 @@
programs nfsd and mountd (but does not need to have NFS file system
support enabled in its kernel). NFS is explained in the Network
Administrator's Guide, available from
- http://www.linuxdoc.org/docs.html#guide , on its man page: "man
+ <http://www.linuxdoc.org/docs.html#guide>, on its man page: "man
nfs", and in the NFS-HOWTO.
-
+
A superior but less widely used alternative to NFS is provided by
the Coda file system; see "Coda file system support" below.
If you say Y here, you should have said Y to TCP/IP networking also.
- This option would enlarge your kernel by about 27 KB.
+ This option would enlarge your kernel by about 27 KB.
This file system is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module is called nfs.o. If you want to compile it as a module,
- say M here and read Documentation/modules.txt.
+ say M here and read <file:Documentation/modules.txt>.
If you are configuring a diskless machine which will mount its root
- file system over NFS at boot time, say Y here and to "IP: kernel
- level autoconfiguration" above and to "Root file system on NFS"
+ file system over NFS at boot time, say Y here and to "Kernel
+ level IP autoconfiguration" above and to "Root file system on NFS"
below. You cannot compile this driver as a module in this case.
There are two packages designed for booting diskless machines over
the net: netboot and etherboot, both available via FTP from
- ftp://metalab.unc.edu/pub/Linux/system/boot/ethernet/ .
+ <ftp://metalab.unc.edu/pub/Linux/system/boot/Ethernet/>.
If you don't know what all this is about, say N.
-Provide NFSv3 client support (EXPERIMENTAL)
+Provide NFSv3 client support
CONFIG_NFS_V3
Say Y here if you want your NFS client to be able to speak the newer
- version 3 of the NFS protocol.
-
+ version 3 of the NFS protocol.
+
If unsure, say N.
Root file system on NFS
@@ -12529,12 +14178,12 @@
If you want your Linux box to mount its whole root file system (the
one containing the directory /) from some other computer over the
net via NFS (presumably because your box doesn't have a hard disk),
- say Y. Read Documentation/nfsroot.txt for details. It is likely that
- in this case, you also want to say Y to "IP: kernel level
+ say Y. Read <file:Documentation/nfsroot.txt> for details. It is
+ likely that in this case, you also want to say Y to "Kernel level IP
autoconfiguration" so that your box can discover its network address
at boot time.
-
- Most people say N here.
+
+ Most people say N here.
NFS server support
CONFIG_NFSD
@@ -12547,20 +14196,21 @@
faster.
In either case, you will need support software; the respective
- locations are given in the file Documentation/Changes in the NFS
- section.
+ locations are given in the file <file:Documentation/Changes> in the
+ NFS section.
If you say Y here, you will get support for version 2 of the NFS
protocol (NFSv2). If you also want NFSv3, say Y to the next question
as well.
Please read the NFS-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
The NFS server is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module is called nfsd.o. If you want to compile it as a module,
- say M here and read Documentation/modules.txt. If unsure, say N.
+ The module is called nfsd.o. If you want to compile it as a module,
+ say M here and read <file:Documentation/modules.txt>. If unsure,
+ say N.
Provide NFSv3 server support
CONFIG_NFSD_V3
@@ -12572,7 +14222,8 @@
If you are a developer and want to work on fixing problems with
NFS server over TCP support, say Y here. If unsure, say N.
- Some problems can be found by looking for FIXME in net/sunrpc/svcsock.c
+ Some problems can be found by looking for FIXME in
+ <file:net/sunrpc/svcsock.c>.
OS/2 HPFS file system support
CONFIG_HPFS_FS
@@ -12582,29 +14233,13 @@
write files to an OS/2 HPFS partition on your hard drive. OS/2
floppies however are in regular MSDOS format, so you don't need this
option in order to be able to read them. Read
- Documentation/filesystems/hpfs.txt.
+ <file:Documentation/filesystems/hpfs.txt>.
This file system is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module is called hpfs.o. If you want to compile it as a module,
- say M here and read Documentation/modules.txt. If unsure, say N.
-
-FreeVxFS file system support (VERITAS VxFS(TM) compatible)
-CONFIG_VXFS_FS
- FreeVxFS is a filesystem driver that support the VERITAS VxFS(TM)
- filesystem format. VERITAS VxFS(TM) is the standard filesystem
- of SCO UnixWare (and possibly others) and optionally available
- for Sunsoft Solaris, HP-UX and many other operating systems.
- Currently only readonly access is supported.
-
- NOTE: the filesystem type as used by mount(1), mount(2) and fstab(5)
- is 'vxfs' as it describes the filesystem format, not the
- actual driver.
-
- This file system is also available as a module ( = code which can be
- inserted in and removed from the running kernel whenever you want).
- The module is called freevxfs.o. If you want to compile it as a module,
- say M here and read Documentation/modules.txt. If unsure, say N.
+ The module is called hpfs.o. If you want to compile it as a module,
+ say M here and read <file:Documentation/modules.txt>. If unsure,
+ say N.
NTFS file system support (read-only)
CONFIG_NTFS_FS
@@ -12637,94 +14272,98 @@
If unsure, say N.
-System V, Version 7, Xenix and Coherent filesystem support
+System V/Xenix/V7/Coherent file system support
CONFIG_SYSV_FS
SCO, Xenix and Coherent are commercial Unix systems for Intel
machines, and Version 7 was used on the DEC PDP-11. Saying Y
here would allow you to read from their floppies and hard disk
- partitions. If you also want to write to these media, say Y to
- "SYSV file system write support" below.
+ partitions.
If you have floppies or hard disk partitions like that, it is likely
that they contain binaries from those other Unix systems; in order
to run these binaries, you will want to install linux-abi which is a
- a set of kernel modules that lets you run SCO, Xenix, Wyse, UnixWare,
- Dell Unix and System V programs under Linux. It's available via FTP
- (user: ftp) from ftp://ftp.openlinux.org/pub/people/hch/linux-abi).
+ a set of kernel modules that lets you run SCO, Xenix, Wyse,
+ UnixWare, Dell Unix and System V programs under Linux. It is
+ available via FTP (user: ftp) from
+ <ftp://ftp.openlinux.org/pub/people/hch/linux-abi>).
NOTE: that will work only for binaries from Intel-based systems;
PDP ones will have to wait until somebody ports Linux to -11 ;-)
If you only intend to mount files from some other Unix over the
network using NFS, you don't need the System V file system support
- (but you need NFS file system support obviously).
+ (but you need NFS file system support obviously).
Note that this option is generally not needed for floppies, since a
good portable way to transport files and directories between unixes
(and even other operating systems) is given by the tar program ("man
- tar" or preferably "info tar"). Note also that this option has
+ tar" or preferably "info tar"). Note also that this option has
nothing whatsoever to do with the option "System V IPC". Read about
- the System V file system in Documentation/filesystems/sysv-fs.txt.
+ the System V file system in
+ <file:Documentation/filesystems/sysv-fs.txt>.
Saying Y here will enlarge your kernel by about 27 KB.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called sysv.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called sysv.o.
If you haven't heard about all of this before, it's safe to say N.
Amiga FFS file system support
CONFIG_AFFS_FS
The Fast File System (FFS) is the common file system used on hard
- disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
+ disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
if you want to be able to read and write files from and to an Amiga
- FFS partition on your hard drive. Amiga floppies however cannot be
+ FFS partition on your hard drive. Amiga floppies however cannot be
read with this driver due to an incompatibility of the floppy
controller used in an Amiga and the standard floppy controller in
- PCs and workstations. Read Documentation/filesystems/affs.txt and
- fs/affs/Changes.
+ PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
+ and <file:fs/affs/Changes>.
With this driver you can also mount disk files used by Bernd
- Schmidt's Un*X Amiga Emulator (http://www.freiburg.linux.de/~uae/ ).
+ Schmidt's Un*X Amiga Emulator
+ (<http://www.freiburg.linux.de/~uae/>).
If you want to do this, you will also need to say Y or M to "Loop
device support", above.
This file system is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module is called affs.o. If you want to compile it as a module,
- say M here and read Documentation/modules.txt. If unsure, say N.
+ The module is called affs.o. If you want to compile it as a module,
+ say M here and read <file:Documentation/modules.txt>. If unsure,
+ say N.
-Apple Macintosh file system support (EXPERIMENTAL)
+Apple Macintosh file system support
CONFIG_HFS_FS
If you say Y here, you will be able to mount Macintosh-formatted
floppy disks and hard drive partitions with full read-write access.
- Please read fs/hfs/HFS.txt to learn about the available mount
- options.
+ Please read <file:fs/hfs/HFS.txt> to learn about the available mount
+ options.
This file system support is also available as a module ( = code
which can be inserted in and removed from the running kernel
- whenever you want). The module is called hfs.o. If you want to
+ whenever you want). The module is called hfs.o. If you want to
compile it as a module, say M here and read
- Documentation/modules.txt.
+ <file:Documentation/modules.txt>.
ROM file system support
CONFIG_ROMFS_FS
This is a very small read-only file system mainly intended for
initial ram disks of installation disks, but it could be used for
- other read-only media as well. Read
- Documentation/filesystems/romfs.txt for details.
+ other read-only media as well. Read
+ <file:Documentation/filesystems/romfs.txt> for details.
This file system support is also available as a module ( = code
which can be inserted in and removed from the running kernel
- whenever you want). The module is called romfs.o. If you want to
+ whenever you want). The module is called romfs.o. If you want to
compile it as a module, say M here and read
- Documentation/modules.txt. Note that the file system of your root
- partition (the one containing the directory /) cannot be a module.
+ <file:Documentation/modules.txt>. Note that the file system of your
+ root partition (the one containing the directory /) cannot be a
+ module.
If you don't know whether you need it, then you don't need it:
answer N.
-QNX4 file system support (read only) (EXPERIMENTAL)
+QNX4 file system support (read only)
CONFIG_QNX4FS_FS
This is the file system used by the operating system QNX 4. Say Y if
you intend to mount QNX hard disks or floppies. Unless you say Y to
@@ -12735,7 +14374,7 @@
which can be inserted in and removed from the running kernel
whenever you want). The module is called qnx4.o. If you want to
compile it as a module, say M here and read
- Documentation/modules.txt.
+ <file:Documentation/modules.txt>.
If you don't know whether you need it, then you don't need it:
answer N.
@@ -12752,8 +14391,8 @@
automounter (amd), which is a pure user space daemon.
To use the automounter you need the user-space tools from the autofs
- package; you can find the location in Documentation/Changes. You
- also want to answer Y to "NFS file system support", below.
+ package; you can find the location in <file:Documentation/Changes>.
+ You also want to answer Y to "NFS file system support", below.
If you want to use the newer version of the automounter with more
features, say N here and say Y to "Kernel automounter v4 support",
@@ -12761,13 +14400,13 @@
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called autofs.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called autofs.o.
If you are not a part of a fairly large, distributed network, you
probably do not need an automounter, and can say N here.
-Kernel automounter v4 support
+Kernel automounter version 4 support (also supports v3)
CONFIG_AUTOFS4_FS
The automounter is a tool to automatically mount remote file systems
on demand. This implementation is partially kernel-based to reduce
@@ -12775,46 +14414,70 @@
automounter (amd), which is a pure user space daemon.
To use the automounter you need the user-space tools from
- ftp://ftp.kernel.org/pub/linux/daemons/autofs/testing-v4 ; you also
+ <ftp://ftp.kernel.org/pub/linux/daemons/autofs/testing-v4>; you also
want to answer Y to "NFS file system support", below.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called autofs4.o. You will need to add "alias autofs autofs4" to
- your modules configuration file.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called autofs4.o. You will need to add "alias autofs
+ autofs4" to your modules configuration file.
If you are not a part of a fairly large, distributed network or
don't have a laptop which needs to dynamically reconfigure to the
local network, you probably do not need an automounter, and can say
N here.
-EFS file system support (read-only) (EXPERIMENTAL)
+EFS file system support (read-only)
CONFIG_EFS_FS
- EFS is an older file system used for non-ISO9660 CDROMs and hard
+ EFS is an older file system used for non-ISO9660 CD-ROMs and hard
disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
uses the XFS file system for hard disk partitions however).
This implementation only offers read-only access. If you don't know
what all this is about, it's safe to say N. For more information
- about EFS see its home page at http://aeschi.ch.eu.org/efs/ .
+ about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
If you want to compile the EFS file system support as a module ( =
code which can be inserted in and removed from the running kernel
- whenever you want), say M here and read Documentation/modules.txt.
- The module will be called efs.o.
+ whenever you want), say M here and read
+ <file:Documentation/modules.txt>. The module will be called efs.o.
-Support for the Journalling Flash Filesystem
+Journalling Flash File System (JFFS) support
CONFIG_JFFS_FS
JFFS is the Journaling Flash File System developed by Axis
Communications in Sweden, aimed at providing a crash/powerdown-safe
- filesystem for disk-less embedded devices. Further information is
- available at (http://developer.axis.com/software/jffs/).
+ file system for disk-less embedded devices. Further information is
+ available at (<http://developer.axis.com/software/jffs/>).
-JFFS debugging verbosity
+JFFS debugging verbosity (0 = quiet, 3 = noisy)
CONFIG_JFFS_FS_VERBOSE
Determines the verbosity level of the JFFS debugging messages.
+Journalling Flash File System v2 (JFFS2) support
+CONFIG_JFFS2_FS
+ JFFS2 is the second generation of the Journalling Flash File System
+ for use on diskless embedded devices. It provides improved wear
+ levelling, compression and support for hard links. You cannot use
+ this on normal block devices, only on 'MTD' devices.
+
+ Further information should be made available soon at
+ <http://sources.redhat.com/jffs2/>.
+
+JFFS2 debugging verbosity (0 = quiet, 2 = noisy)
+CONFIG_JFFS2_FS_DEBUG
+ This controls the amount of debugging messages produced by the JFFS2
+ code. Set it to zero for use in production systems. For evaluation,
+ testing and debugging, it's advisable to set it to one. This will
+ enable a few assertions and will print debugging messages at the
+ KERN_DEBUG loglevel, where they won't normally be visible. Level 2
+ is unlikely to be useful - it enables extra debugging in certain
+ areas which at one point needed debugging, but when the bugs were
+ located and fixed, the detailed messages were relegated to level 2.
+
+ If reporting bugs, please try to have available a full dump of the
+ messages at debug level 1 while the misbehaviour was occurring.
+
UFS file system support (read-only)
CONFIG_UFS_FS
BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
@@ -12823,11 +14486,11 @@
this file system as well. Saying Y here will allow you to read from
these partitions; if you also want to write to them, say Y to the
experimental "UFS file system write support", below. Please read the
- file Documentation/filesystems/ufs.txt for more information.
+ file <file:Documentation/filesystems/ufs.txt> for more information.
If you only intend to mount files from some other Unix over the
network using NFS, you don't need the UFS file system support (but
- you need NFS file system support obviously).
+ you need NFS file system support obviously).
Note that this option is generally not needed for floppies, since a
good portable way to transport files and directories between unixes
@@ -12836,12 +14499,12 @@
When accessing NeXTstep files, you may need to convert them from the
NeXT character set to the Latin1 character set; use the program
- recode ("info recode") for this purpose.
+ recode ("info recode") for this purpose.
If you want to compile the UFS file system support as a module ( =
code which can be inserted in and removed from the running kernel
- whenever you want), say M here and read Documentation/modules.txt.
- The module will be called ufs.o.
+ whenever you want), say M here and read
+ <file:Documentation/modules.txt>. The module will be called ufs.o.
If you haven't heard about all of this before, it's safe to say N.
@@ -12857,11 +14520,38 @@
architecture than your Linux system.
Note that the answer to this question won't directly affect the
- kernel: saying N will just cause this configure script to skip all
- the questions about foreign partitioning schemes.
+ kernel: saying N will just cause the configurator to skip all
+ the questions about foreign partitioning schemes.
If unsure, say N.
+Acorn partition support
+CONFIG_ACORN_PARTITION
+ Support hard disks partitioned under Acorn operating systems.
+
+Native filecore partition support
+CONFIG_ACORN_PARTITION_ADFS
+ The Acorn Disc Filing System is the standard file system of the
+ RiscOS operating system which runs on Acorn's ARM-based Risc PC
+ systems and the Acorn Archimedes range of machines. If you say
+ `Y' here, Linux will support disk partitions created under ADFS.
+
+PowerTec partition support
+CONFIG_ACORN_PARTITION_POWERTEC
+ Support reading partition tables created on Acorn machines using
+ the PowerTec SCSI drive.
+
+RISCiX partition support
+CONFIG_ACORN_PARTITION_RISCIX
+ Once upon a time, there was a native Unix port for the Acorn series
+ of machines called RISCiX. If you say 'Y' here, Linux will be able
+ to read disks partitioned under RISCiX.
+
+ICS partition support
+CONFIG_ACORN_PARTITION_ICS
+ Say Y here if you would like to use hard disks under Linux which
+ were partitioned using the ICS interface on Acorn machines.
+
Alpha OSF partition support
CONFIG_OSF_PARTITION
Say Y here if you would like to use hard disks under Linux which
@@ -12884,10 +14574,11 @@
mirrored, striped or RAID volumes, all without the need for
rebooting.
- Normal partitions are now called Basic Disks under Windows 2000 and XP.
+ Normal partitions are now called Basic Disks under Windows 2000 and
+ XP.
Technical documentation to accompany this driver is available from:
- <http://linux-ntfs.sf.net/ldm>
+ <http://linux-ntfs.sf.net/ldm>.
If unsure, say N.
@@ -12904,6 +14595,16 @@
Say Y here if you would like to use hard disks under Linux which
were partitioned on an x86 PC (not necessarily by DOS).
+Amiga partition table support
+CONFIG_AMIGA_PARTITION
+ Say Y here if you would like to use hard disks under Linux which
+ were partitioned under AmigaOS.
+
+Atari partition table support
+CONFIG_ATARI_PARTITION
+ Say Y here if you would like to use hard disks under Linux which
+ were partitioned under the Atari OS.
+
BSD disklabel (FreeBSD partition tables) support
CONFIG_BSD_DISKLABEL
FreeBSD uses its own hard disk partition scheme on your PC. It
@@ -12921,7 +14622,7 @@
Say Y here if you want to mount and use Minix 2.0.0/2.0.2
subpartitions.
-Sun partition tables support
+Sun partition table support
CONFIG_SUN_PARTITION
Like most systems, SunOS uses its own hard disk partition table
format, incompatible with all others. Saying Y here allows you to
@@ -12947,13 +14648,19 @@
Say Y here if you would like to be able to read the hard disk
partition table format used by SGI machines.
-Ultrix partition support
+Ultrix partition table support
CONFIG_ULTRIX_PARTITION
Say Y here if you would like to be able to read the hard disk
partition table format used by DEC (now Compaq) Ultrix machines.
Otherwise, say N.
-ADFS file system support (EXPERIMENTAL)
+IBM disk label and partition support
+CONFIG_IBM_PARTITION
+ Say Y here if you would like to be able to read the hard disk
+ partition table format used by IBM DASD disks operating under CMS.
+ Otherwise, say N.
+
+ADFS file system support
CONFIG_ADFS_FS
The Acorn Disc Filing System is the standard file system of the
RiscOS operating system which runs on Acorn's ARM-based Risc PC
@@ -12964,12 +14671,12 @@
The ADFS partition should be the first partition (i.e.,
/dev/[hs]d?1) on each of your drives. Please read the file
- Documentation/filesystems/adfs.txt for further details.
+ <file:Documentation/filesystems/adfs.txt> for further details.
This code is also available as a module called adfs.o ( = code which
can be inserted in and removed from the running kernel whenever you
want). If you want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ <file:Documentation/modules.txt>.
If unsure, say N.
@@ -12989,17 +14696,55 @@
to acquire a pseudo terminal, a process opens /dev/ptmx; the number
of the pseudo terminal is then made available to the process and the
pseudo terminal slave can be accessed as /dev/pts/<number>. What was
- traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
+ traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
The GNU C library glibc 2.1 contains the requisite support for this
mode of operation; you also need client programs that use the Unix98
- API. Please read Documentation/Changes for more information about
- the Unix98 pty devices.
+ API. Please read <file:Documentation/Changes> for more information
+ about the Unix98 pty devices.
Note that the experimental "/dev file system support"
(CONFIG_DEVFS_FS) is a more general facility.
-UnixWare slices support (EXPERIMENTAL)
+# This is for Linus's tree
+FreeVxFS file system support (VERITAS VxFS(TM) compatible)
+CONFIG_VXFS_FS
+ FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
+ file system format. VERITAS VxFS(TM) is the standard file system
+ of SCO UnixWare (and possibly others) and optionally available
+ for Sunsoft Solaris, HP-UX and many other operating systems.
+ Currently only readonly access is supported.
+
+ NOTE: the file system type as used by mount(1), mount(2) and
+ fstab(5) is 'vxfs' as it describes the file system format, not
+ the actual driver.
+
+ This file system is also available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ The module is called freevxfs.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>. If
+ unsure, say N.
+
+# This is for Alan's tree. Note the name difference.
+FreeVxFS file system support (VERITAS VxFS(TM) compatible)
+CONFIG_FREEVXFS_FS
+ FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
+ file system format. VERITAS VxFS(TM) is the standard file system
+ of SCO UnixWare (and possibly others) and optionally available
+ for Sunsoft Solaris, HP-UX and many other operating systems.
+ Currently only readonly access is supported.
+
+ NOTE: the file system type as used by mount(1), mount(2) and
+ fstab(5) is 'vxfs' as it describes the filesystem format, not
+ the actual driver.
+
+ This file system is also available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ The module is called freevxfs.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>. If
+ unsure, say N.
+
+UnixWare slices support
CONFIG_UNIXWARE_DISKLABEL
Like some systems, UnixWare uses its own slice table inside a
partition (VTOC - Virtual Table of Contents). Its format is
@@ -13013,7 +14758,7 @@
removable IDE drives. Note, however, that a good portable way to
transport files and directories between unixes (and even other
operating systems) is given by the tar program ("man tar" or
- preferably "info tar").
+ preferably "info tar").
If you don't know what all this is about, say N.
@@ -13021,29 +14766,29 @@
CONFIG_SMB_FS
SMB (Server Message Block) is the protocol Windows for Workgroups
(WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
- files and printers over local networks. Saying Y here allows you to
+ files and printers over local networks. Saying Y here allows you to
mount their file systems (often called "shares" in this context) and
- access them just like any other Unix directory. Currently, this
+ access them just like any other Unix directory. Currently, this
works only if the Windows machines use TCP/IP as the underlying
- transport protocol, and not NetBEUI. For details, read
- Documentation/filesystems/smbfs.txt and the SMB-HOWTO, available
- from http://www.linuxdoc.org/docs.html#howto .
+ transport protocol, and not NetBEUI. For details, read
+ <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
+ available from <http://www.linuxdoc.org/docs.html#howto>.
Note: if you just want your box to act as an SMB *server* and make
files and printing services available to Windows clients (which need
to have a TCP/IP stack), you don't need to say Y here; you can use
the program samba (available via FTP (user: anonymous) in
- ftp://metalab.unc.edu/pub/Linux/system/network/samba ) for that.
+ <ftp://metalab.unc.edu/pub/Linux/system/network/samba>) for that.
General information about how to connect Linux, Windows machines and
- Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
+ Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
If you want to compile the SMB support as a module ( = code which
can be inserted in and removed from the running kernel whenever you
- want), say M here and read Documentation/modules.txt. The module
- will be called smbfs.o. Most people say N, however.
+ want), say M here and read <file:Documentation/modules.txt>. The
+ module will be called smbfs.o. Most people say N, however.
-use nls by default
+Use a default NLS
CONFIG_SMB_NLS_DEFAULT
Enabling this will make smbfs use nls translations by default. You
need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
@@ -13055,7 +14800,7 @@
smbmount from samba 2.2.0 or later supports this.
-nls support setting
+Default Remote NLS Option
CONFIG_SMB_NLS_REMOTE
This setting allows you to specify a default value for which
codepage the server uses. If this field is left blank no
@@ -13072,72 +14817,85 @@
Coda is an advanced network file system, similar to NFS in that it
enables you to mount file systems of a remote server and access them
with regular Unix commands as if they were sitting on your hard
- disk. Coda has several advantages over NFS: support for disconnected
- operation (e.g. for laptops), read/write server replication,
- security model for authentication and encryption, persistent client
- caches and write back caching.
+ disk. Coda has several advantages over NFS: support for
+ disconnected operation (e.g. for laptops), read/write server
+ replication, security model for authentication and encryption,
+ persistent client caches and write back caching.
If you say Y here, your Linux box will be able to act as a Coda
- *client*. You will need user level code as well, both for the client
- and server. Servers are currently user level, i.e. they need no
- kernel support. Please read Documentation/filesystems/coda.txt and
- check out the Coda home page http://www.coda.cs.cmu.edu .
+ *client*. You will need user level code as well, both for the
+ client and server. Servers are currently user level, i.e. they need
+ no kernel support. Please read
+ <file:Documentation/filesystems/coda.txt> and check out the Coda
+ home page <http://www.coda.cs.cmu.edu>.
If you want to compile the coda client support as a module ( = code
which can be inserted in and removed from the running kernel
- whenever you want), say M here and read Documentation/modules.txt.
- The module will be called coda.o.
+ whenever you want), say M here and read
+ <file:Documentation/modules.txt>. The module will be called coda.o.
+
+InterMezzo file system support (experimental, replicating fs)
+CONFIG_INTERMEZZO_FS
+ InterMezzo is a networked file system with disconnected operation
+ and kernel level write back caching. It is most often used for
+ replicating potentially large trees or keeping laptop/desktop copies
+ in sync.
+
+ If you say Y or M your kernel or module will provide InterMezzo
+ support. You will also need a file server daemon, which you can get
+ from <http://www.inter-mezzo.org>.
NCP file system support (to mount NetWare volumes)
CONFIG_NCP_FS
NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
- used by Novell NetWare clients to talk to file servers. It is to IPX
- what NFS is to TCP/IP, if that helps. Saying Y here allows you to
- mount NetWare file server volumes and to access them just like any
- other Unix directory. For details, please read the file
- Documentation/filesystems/ncpfs.txt in the kernel source and the
- IPX-HOWTO from http://www.linuxdoc.org/docs.html#howto .
+ used by Novell NetWare clients to talk to file servers. It is to
+ IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
+ to mount NetWare file server volumes and to access them just like
+ any other Unix directory. For details, please read the file
+ <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
+ the IPX-HOWTO from <http://www.linuxdoc.org/docs.html#howto>.
You do not have to say Y here if you want your Linux box to act as a
file *server* for Novell NetWare clients.
General information about how to connect Linux, Windows machines and
- Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
+ Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called ncpfs.o. Say N unless you are connected to a Novell network.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called ncpfs.o. Say N unless you are connected to a Novell
+ network.
Packet signatures
CONFIG_NCPFS_PACKET_SIGNING
NCP allows packets to be signed for stronger security. If you want
- security, say Y. Normal users can leave it off. To be able to use
+ security, say Y. Normal users can leave it off. To be able to use
packet signing you must use ncpfs > 2.0.12.
Proprietary file locking
CONFIG_NCPFS_IOCTL_LOCKING
- Allows locking of records on remote volumes. Say N unless you have
+ Allows locking of records on remote volumes. Say N unless you have
special applications which are able to utilize this locking scheme.
Clear remove/delete inhibit when needed
CONFIG_NCPFS_STRONG
- Allows manipulation of files flagged as Delete or Rename Inhibit. To
- use this feature you must mount volumes with the ncpmount parameter
- "-s" (ncpfs-2.0.12 and newer). Say Y unless you are not mounting
- volumes with -f 444.
+ Allows manipulation of files flagged as Delete or Rename Inhibit.
+ To use this feature you must mount volumes with the ncpmount
+ parameter "-s" (ncpfs-2.0.12 and newer). Say Y unless you are not
+ mounting volumes with -f 444.
-Use NFS namespace when available
+Use NFS namespace if available
CONFIG_NCPFS_NFS_NS
- Allows you to utilize NFS namespace on NetWare servers. It brings
- you case sensitive filenames. Say Y. You can disable it at
+ Allows you to utilize NFS namespace on NetWare servers. It brings
+ you case sensitive filenames. Say Y. You can disable it at
mount-time with the `-N nfs' parameter of ncpmount.
-Use OS2/LONG namespace when available
+Use LONG (OS/2) namespace if available
CONFIG_NCPFS_OS2_NS
Allows you to utilize OS2/LONG namespace on NetWare servers.
Filenames in this namespace are limited to 255 characters, they are
- case insensitive, and case in names is preserved. Say Y. You can
+ case insensitive, and case in names is preserved. Say Y. You can
disable it at mount time with the -N os2 parameter of ncpmount.
Lowercase DOS filenames on LONG namespace volume
@@ -13146,7 +14904,7 @@
the OS2/LONG namespace and created under DOS or on a volume using
DOS namespace will be converted to lowercase characters.
Saying N here will give you these filenames in uppercase.
-
+
This is only a cosmetic option since the OS2/LONG namespace is case
insensitive. The only major reason for this option is backward
compatibility when moving from DOS to OS2/LONG namespace support.
@@ -13158,25 +14916,7 @@
effects by saying Y to "Allow using of Native Language Support"
below.
-Allow mounting of volume subdirectories
-CONFIG_NCPFS_MOUNT_SUBDIR
- Allows you to mount not only whole servers or whole volumes, but
- also subdirectories from a volume. It can be used to reexport data
- and so on. There is no reason to say N, so Y is recommended unless
- you count every byte.
-
- To utilize this feature you must use ncpfs-2.0.12 or newer.
-
-NDS authentication support
-CONFIG_NCPFS_NDS_DOMAINS
- This allows storing NDS private keys in kernel space where they
- can be used to authenticate another server as interserver NDS
- accesses need it. You must use ncpfs-2.0.12.1 or newer to utilize
- this feature. Say Y if you are using NDS connections to NetWare
- servers. Do not say Y if security is primary for you because root
- can read your session key (from /proc/kcore).
-
-Allow using of Native Language Support
+Use Native Language Support
CONFIG_NCPFS_NLS
Allows you to use codepages and I/O charsets for file name
translation between the server file system and input/output. This
@@ -13194,21 +14934,24 @@
To use the new attributes, it is recommended to use the flags
'-f 600 -d 755' on the ncpmount command line.
-nls default codepage
+Default NLS Option
CONFIG_NLS_DEFAULT
- The default NLS used when mounting file system. Currently, the valid
- values are:
+ The default NLS used when mounting file system. Note, that this is
+ the NLS used by your console, not the NLS used by a specific file
+ system (if different) to store data (filenames) on a disk.
+ Currently, the valid values are:
big5, cp437, cp737, cp775, cp850, cp852, cp855, cp857, cp860, cp861,
cp862, cp863, cp864, cp865, cp866, cp869, cp874, cp932, cp936,
- cp949, cp950, euc-jp, euc-kr, gb2312, iso8859-1, iso8859-2, iso8859-3,
- iso8859-4, iso8859-5, iso8859-6, iso8859-7, iso8859-8, iso8859-9,
- iso8859-14, iso8859-15, koi8-r, sjis
- If you specify a wrong value, it will use the built-in NLS; compatible
- with iso8859-1.
+ cp949, cp950, cp1251, cp1255, euc-jp, euc-kr, gb2312, iso8859-1,
+ iso8859-2, iso8859-3, iso8859-4, iso8859-5, iso8859-6, iso8859-7,
+ iso8859-8, iso8859-9, iso8859-13, iso8859-14, iso8859-15,
+ koi8-r, koi8-ru, koi8-u, sjis, tis-620, utf8.
+ If you specify a wrong value, it will use the built-in NLS;
+ compatible with iso8859-1.
If unsure, specify it as "iso8859-1".
-nls codepage 437
+Codepage 437 (United States, Canada)
CONFIG_NLS_CODEPAGE_437
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored
@@ -13219,7 +14962,7 @@
say Y here if you want to include the DOS codepage that is used in
the United States and parts of Canada. This is recommended.
-nls codepage 737
+Codepage 737 (Greek)
CONFIG_NLS_CODEPAGE_737
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored
@@ -13230,7 +14973,7 @@
say Y here if you want to include the DOS codepage that is used for
Greek. If unsure, say N.
-nls codepage 775
+Codepage 775 (Baltic Rim)
CONFIG_NLS_CODEPAGE_775
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored
@@ -13239,9 +14982,10 @@
DOS/Windows partitions correctly. This does apply to the filenames
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage that is used
- for the Baltic Rim Languages. If unsure, say N.
+ for the Baltic Rim Languages (Latvian and Lithuanian). If unsure,
+ say N.
-nls codepage 850
+Codepage 850 (Europe)
CONFIG_NLS_CODEPAGE_850
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
@@ -13252,11 +14996,11 @@
say Y here if you want to include the DOS codepage that is used for
much of Europe -- United Kingdom, Germany, Spain, Italy, and [add
more countries here]. It has some characters useful to many European
- languages that are not part of the US codepage 437.
+ languages that are not part of the US codepage 437.
If unsure, say Y.
-nls codepage 852
+Codepage 852 (Central/Eastern Europe)
CONFIG_NLS_CODEPAGE_852
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
@@ -13270,7 +15014,7 @@
Finnish, Hungarian, Irish, German, Polish, Romanian, Serbian (Latin
transcription), Slovak, Slovenian, and Sorbian.
-nls codepage 855
+Codepage 855 (Cyrillic)
CONFIG_NLS_CODEPAGE_855
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
@@ -13280,7 +15024,7 @@
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for Cyrillic.
-nls codepage 857
+Codepage 857 (Turkish)
CONFIG_NLS_CODEPAGE_857
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
@@ -13290,7 +15034,7 @@
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for Turkish.
-nls codepage 860
+Codepage 860 (Portuguese)
CONFIG_NLS_CODEPAGE_860
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
@@ -13300,7 +15044,7 @@
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for Portuguese.
-nls codepage 861
+Codepage 861 (Icelandic)
CONFIG_NLS_CODEPAGE_861
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
@@ -13310,7 +15054,7 @@
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for Icelandic.
-nls codepage 862
+Codepage 862 (Hebrew)
CONFIG_NLS_CODEPAGE_862
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
@@ -13320,7 +15064,7 @@
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for Hebrew.
-nls codepage 863
+Codepage 863 (Canadian French)
CONFIG_NLS_CODEPAGE_863
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
@@ -13331,7 +15075,7 @@
say Y here if you want to include the DOS codepage for Canadian
French.
-nls codepage 864
+Codepage 864 (Arabic)
CONFIG_NLS_CODEPAGE_864
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
@@ -13341,7 +15085,7 @@
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for Arabic.
-nls codepage 865
+Codepage 865 (Norwegian, Danish)
CONFIG_NLS_CODEPAGE_865
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
@@ -13352,7 +15096,7 @@
say Y here if you want to include the DOS codepage for the Nordic
European countries.
-nls codepage 866
+Codepage 866 (Cyrillic/Russian)
CONFIG_NLS_CODEPAGE_866
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
@@ -13363,7 +15107,7 @@
say Y here if you want to include the DOS codepage for
Cyrillic/Russian.
-nls codepage 869
+Codepage 869 (Greek)
CONFIG_NLS_CODEPAGE_869
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
@@ -13373,7 +15117,7 @@
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for Greek.
-nls codepage 874
+Thai charset (CP874, TIS-620)
CONFIG_NLS_CODEPAGE_874
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
@@ -13383,7 +15127,18 @@
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for Thai.
-nls codepage 932
+Windows CP1251 (Bulgarian, Belarusian)
+CONFIG_NLS_CODEPAGE_1251
+ The Microsoft FAT file system family can deal with filenames in
+ native language character sets. These character sets are stored in
+ so-called DOS codepages. You need to include the appropriate
+ codepage if you want to be able to read/write these filenames on
+ DOS/Windows partitions correctly. This does apply to the filenames
+ only, not to the file contents. You can include several codepages;
+ say Y here if you want to include the DOS codepage for Russian and
+ Bulgarian and Belarusian.
+
+Japanese charsets (Shift-JIS, EUC-JP)
CONFIG_NLS_CODEPAGE_932
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
@@ -13393,9 +15148,9 @@
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for Shift-JIS
or EUC-JP. To use EUC-JP, you can use 'euc-jp' as mount option or
- NLS Default value during kernel configuration , instead of 'cp932'
+ NLS Default value during kernel configuration, instead of 'cp932'.
-nls codepage 936
+Simplified Chinese charset (CP936, GB2312)
CONFIG_NLS_CODEPAGE_936
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
@@ -13406,7 +15161,7 @@
say Y here if you want to include the DOS codepage for Simplified
Chinese(GBK).
-nls codepage 949
+Korean charset (CP949, EUC-KR)
CONFIG_NLS_CODEPAGE_949
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
@@ -13416,7 +15171,7 @@
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage for UHC.
-nls codepage 950
+Traditional Chinese charset (Big5)
CONFIG_NLS_CODEPAGE_950
The Microsoft FAT file system family can deal with filenames in
native language character sets. These character sets are stored in
@@ -13427,10 +15182,10 @@
say Y here if you want to include the DOS codepage for Traditional
Chinese(Big5).
-nls iso8859-1
+NLS ISO 8859-1 (Latin 1; Western European Languages)
CONFIG_NLS_ISO8859_1
If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for the Latin 1 character
set, which covers most West European languages such as Albanian,
@@ -13438,101 +15193,110 @@
Galician, Irish, Icelandic, Italian, Norwegian, Portuguese, Spanish,
and Swedish. It is also the default for the US. If unsure, say Y.
-nls iso8859-2
+NLS ISO 8859-2 (Latin 2; Slavic/Central European Languages)
CONFIG_NLS_ISO8859_2
If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for the Latin 2 character
set, which works for most Latin-written Slavic and Central European
languages: Czech, German, Hungarian, Polish, Rumanian, Croatian,
Slovak, Slovene.
-nls iso8859-3
+NLS ISO 8859-3 (Latin 3; Esperanto, Galician, Maltese, Turkish)
CONFIG_NLS_ISO8859_3
If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for the Latin 3 character
set, which is popular with authors of Esperanto, Galician, Maltese,
and Turkish.
-nls iso8859-4
+NLS ISO 8859-4 (Latin 4; old Baltic charset)
CONFIG_NLS_ISO8859_4
If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for the Latin 4 character
set which introduces letters for Estonian, Latvian, and
- Lithuanian. It is an incomplete predecessor of Latin 6.
+ Lithuanian. It is an incomplete predecessor of Latin 7.
-nls iso8859-5
+NLS ISO 8859-5 (Cyrillic)
CONFIG_NLS_ISO8859_5
If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for ISO8859-5, a Cyrillic
- character set with which you can type Bulgarian, Byelorussian,
+ character set with which you can type Bulgarian, Belarusian,
Macedonian, Russian, Serbian, and Ukrainian. Note that the charset
KOI8-R is preferred in Russia.
-nls iso8859-6
+NLS ISO 8859-6 (Arabic)
CONFIG_NLS_ISO8859_6
If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for ISO8859-6, the Arabic
character set.
-nls iso8859-7
+NLS ISO 8859-7 (Modern Greek)
CONFIG_NLS_ISO8859_7
If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for ISO8859-7, the Modern
Greek character set.
-nls iso8859-8
+Hebrew charsets (ISO-8859-8, CP1255)
CONFIG_NLS_ISO8859_8
If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for ISO8859-8, the Hebrew
character set.
-nls iso8859-9
+NLS ISO 8859-9 (Latin 5; Turkish)
CONFIG_NLS_ISO8859_9
If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for the Latin 5 character
set, and it replaces the rarely needed Icelandic letters in Latin 1
with the Turkish ones. Useful in Turkey.
-nls iso8859-10
+NLS ISO 8859-10 (Latin 6; Nordic)
CONFIG_NLS_ISO8859_10
If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for the Latin 6 character
set, which adds the last Inuit (Greenlandic) and Sami (Lappish)
letters that were missing in Latin 4 to cover the entire Nordic
area.
+NLS ISO 8859-13 (Latin 7; Baltic)
+CONFIG_NLS_ISO8859_13
+ If you want to display filenames with native language characters
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
+ correctly on the screen, you need to include the appropriate
+ input/output character sets. Say Y here for the Latin 7 character
+ set, which supports modern Baltic languages including Latvian
+ and Lithuanian.
+
NLS ISO 8859-14 (Latin 8; Celtic)
CONFIG_NLS_ISO8859_14
If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for the Latin 8 character
set, which adds the last accented vowels for Welsh (aka Cymraeg)
- (and Manx Gaelic) hat were missing in Latin 1.
- http://linux.speech.cymru.org/ has further information.
+ (and Manx Gaelic) that were missing in Latin 1.
+ <http://linux.speech.cymru.org/> has further information.
-nls iso8859-15
+NLS ISO 8859-15 (Latin 9; Western European languages with Euro)
CONFIG_NLS_ISO8859_15
If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for the Latin 9 character
set, which covers most West European languages such as Albanian,
@@ -13541,17 +15305,33 @@
Portuguese, Spanish, and Swedish. Latin 9 is an update to
Latin 1 (ISO 8859-1) that removes a handful of rarely used
characters and instead adds support for Estonian, corrects the
- support for French and Finnish, and adds the new Euro character. If
- unsure, say Y.
+ support for French and Finnish, and adds the new Euro character.
+ If unsure, say Y.
-nls koi8-r
+NLS KOI8-R (Russian)
CONFIG_NLS_KOI8_R
If you want to display filenames with native language characters
- from the Microsoft FAT file system family or from JOLIET CDROMs
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for the preferred Russian
character set.
+NLS KOI8-U/RU (Ukrainian, Belarusian)
+CONFIG_NLS_KOI8_U
+ If you want to display filenames with native language characters
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
+ correctly on the screen, you need to include the appropriate
+ input/output character sets. Say Y here for the preferred Ukrainian
+ (koi8-u) and Belarusian (koi8-ru) character sets.
+
+NLS UTF8
+CONFIG_NLS_UTF8
+ If you want to display filenames with native language characters
+ from the Microsoft FAT file system family or from JOLIET CD-ROMs
+ correctly on the screen, you need to include the appropriate
+ input/output character sets. Say Y here for the UTF-8 encoding of
+ the Unicode/ISO9646 universal character set.
+
Virtual terminal
CONFIG_VT
If you say Y here, you will get support for terminal devices with
@@ -13599,38 +15379,236 @@
If unsure, say Y.
-Support for PowerMac keyboard
-CONFIG_MAC_KEYBOARD
+STI console
+CONFIG_STI_CONSOLE
+ The STI console is the builtin display/keyboard on HP-PARISC
+ machines. Say Y here to build support for it into your kernel.
+ The alternative is to use your primary serial port as a console.
+
+Use MDIO for PHY configuration
+CONFIG_USE_MDIO
+ On some boards the hardware configuration of the ethernet PHY can be
+ used without any software interaction over the MDIO interface, so
+ all MII code can be omitted. Say N here if unsure or if you don't
+ need link status reports.
+
+860T FEC Ethernet
+CONFIG_FEC_ENET
+ Enable Ethernet support via the Fast Ethernet Controller (FCC) on
+ the Motorola MPC8260.
+
+Ethernet on FCC1
+CONFIG_FCC1_ENET
+ Use MPC8260 fast Ethernet controller 1 to drive Ethernet (default).
+
+Ethernet on FCC2
+CONFIG_FCC2_ENET
+ Use MPC8260 fast Ethernet controller 2 to drive Ethernet.
+
+Ethernet on FCC3
+CONFIG_FCC3_ENET
+ Use MPC8260 fast Ethernet controller 3 to drive Ethernet.
+
+CPM SCC Ethernet
+CONFIG_SCC_ENET
+ Enable Ethernet support via the Motorola MPC8xx serial
+ commmunications controller.
+
+Ethernet on SCC1
+CONFIG_SCC1_ENET
+ Use MPC8xx serial communications controller 1 to drive Ethernet
+ (default).
+
+Ethernet on SCC2
+CONFIG_SCC2_ENET
+ Use MPC8xx serial communications controller 2 to drive Ethernet.
+
+Ethernet on SCC3
+CONFIG_SCC3_ENET
+ Use MPC8xx serial communications controller 3 to drive Ethernet.
+
+Use Big CPM Ethernet Buffers
+CONFIG_ENET_BIG_BUFFERS
+ Allocate large buffers for MPC8xx Etherenet. Increases throughput
+ and decreases the likelihood of dropped packets, but costs memory.
+
+Apple Desktop Bus (ADB) support
+CONFIG_ADB
+ Apple Desktop Bus (ADB) support is for support of devices which
+ are connected to an ADB port. ADB devices tend to have 4 pins.
+ If you have an Apple Macintosh prior to the iMac, or a
+ "Blue and White G3", you probably want to say Y here. Otherwise
+ say N.
+
+Support for CUDA based PowerMacs
+CONFIG_ADB_CUDA
+ This provides support for CUDA based Power Macintosh systems. This
+ includes most OldWorld PowerMacs, the first generation iMacs, the
+ Blue&White G3 and the Yikes G4 (PCI Graphics). All later models
+ should use CONFIG_ADB_PMU instead.
+
+ If unsure say Y.
+
+Support for PMU-based PowerMacs
+CONFIG_ADB_PMU
+ On the PowerBook 3400 and 2400, the PMU is a 6805 microprocessor
+ core whose primary function is to control battery charging and
+ system power. The PMU also controls the ADB (Apple Desktop Bus)
+ which connects to the keyboard and mouse, as well as the
+ non-volatile RAM and the RTC (real time clock) chip. Say Y to
+ enable support for this device; you should do so if your machine
+ is one of these PowerBooks.
+
+Include MacIO ADB driver
+CONFIG_ADB_MACIO
+ Say Y here to include direct support for the ADB controller in the
+ Hydra chip used on PowerPC Macintoshes of the CHRP type. (The Hydra
+ also includes a MESH II SCSI controller, DBDMA controller, VIA chip,
+ OpenPIC controller and two RS422/Geoports.)
+
+Support for ADB keyboard (old driver)
+CONFIG_ADB_KEYBOARD
This option allows you to use an ADB keyboard attached to your
machine. Note that this disables any other (ie. PS/2) keyboard
support, even if your machine is physically capable of using both at
the same time.
-
+
If you use an ADB keyboard (4 pin connector), say Y here.
If you use a PS/2 keyboard (6 pin connector), say N here.
-Standard/generic serial support
+HIL keyboard support
+CONFIG_HIL
+ The "Human Interface Loop" is a older, 8-channel USB-like controller
+ used in Hewlette Packard PA-RISC based machines. There are a few
+ cases where it is seen on PC/MAC architectures as well, usually also
+ manufactured by HP. This driver is based off MACH and BSD drivers,
+ and implements support for a keyboard attached to the HIL port.
+ Full support for the USB-like functions and non-keyboard channels of
+ the HIL is not provided for in this driver. There are vestiges of
+ mouse support in the driver, but it is probably not working. The
+ necessary hardware documentation to fully support the HIL controller
+ and interface it to the linux-input API is lacking.
+
+ Enable this option if you intend to use a HIL keyboard.
+
+Include IOP (IIfx/Quadra 9x0) ADB driver
+CONFIG_ADB_IOP
+ The I/O Processor (IOP) is an Apple custom IC designed to provide
+ intelligent support for I/O controllers. It is described at
+ <http://www.angelfire.com/ca2/dev68k/iopdesc.html;> to enable direct
+ support for it, say 'Y' here.
+
+Mac II style Apple Desktop Bus support
+CONFIG_ADB_MACII
+ Say Y here if want your kernel to support Macintosh systems that use
+ the Mac II style ADB. This includes the II, IIx, IIcx, SE/30, IIci,
+ Quadra 610, Quadra 650, Quadra 700, Quadra 800, Centris 610 and
+ Centris 650.
+
+Mac IIsi style Apple Desktop Bus support
+CONFIG_ADB_MACIISI
+ Say Y here if want your kernel to support Macintosh systems that use
+ the Mac IIsi style ADB. This includes the IIsi, IIvi, IIvx, Classic
+ II, LC, LC II, LC III, Performa 460, and the Performa 600.
+
+Apple 68K PowerBook Power Management and Desktop Bus support
+CONFIG_ADB_PMU68K
+ Say Y here if want your kernel to support the m68k based Powerbooks.
+ This includes the PowerBook 140, PowerBook 145, PowerBook 150,
+ PowerBook 160, PowerBook 165, PowerBook 165c, PowerBook 170,
+ PowerBook 180, PowerBook, 180c, PowerBook 190cs, PowerBook 520,
+ PowerBook Duo 210, PowerBook Duo 230, PowerBook Duo 250,
+ PowerBook Duo 270c, PowerBook Duo 280 and PowerBook Duo 280c.
+
+Macintosh IIfx/Quadra 900/Quadra 950 floppy support
+CONFIG_BLK_DEV_SWIM_IOP
+ Say Y here to support the SWIM (Super Woz Integrated Machine) IOP
+ floppy controller on the Macintosh IIfx and Quadra 900/950.
+
+Macintosh NS8390 based Ethernet support
+CONFIG_MAC8390
+ If you want to include a driver to support Nubus or LC-PDS
+ Ethernet cards using an NS8390 chipset or its equivalent, say Y
+ and read the Ethernet-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
+
+Macintosh CS89x0 based Ethernet support
+CONFIG_MAC89x0
+ Support for CS89x0 chipset based Ethernet cards. If you have a
+ Nubus or LC-PDS network (Ethernet) card of this type, say Y and
+ read the Ethernet-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
+
+ If you want to compile this as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want),
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. This module will
+ be called mac89x0.o.
+
+Macintosh onboard AMD 79C940 MACE based Ethernet support
+CONFIG_MACMACE
+ Support for the onboard AMD 79C940 MACE Ethernet controller used in
+ the 660AV and 840AV Macintosh. If you have one of these Macintoshes
+ say Y and read the Ethernet-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
+
+Macintosh SONIC based Ethernet support (onboard, NuBus, LC, CS)
+CONFIG_MACSONIC
+ Support for NatSemi SONIC based Ethernet devices. This includes
+ the onboard Ethernet in many Quadras as well as some LC-PDS,
+ a few Nubus and all known Comm Slot Ethernet cards. If you have
+ one of these say Y and read the Ethernet-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
+
+ If you want to compile this as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want),
+ say M here and read <file:Documentation/modules.txt> as well as
+ <file:Documentation/networking/net-modules.txt>. This module will
+ be called macsonic.o.
+
+Macintosh NCR5380 SCSI support
+CONFIG_MAC_SCSI
+ This is the NCR 5380 SCSI controller included on most of the 68030
+ based Macintoshes. If you have one of these say Y and read the
+ SCSI-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
+
+Macintosh NCR53c9[46] SCSI support
+CONFIG_SCSI_MAC_ESP
+ This is the NCR 53c9x SCSI controller found on most of the 68040
+ based Macintoshes. If you have one of these say Y and read the
+ SCSI-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
+
+ This driver is also available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ The module will be called mac_esp.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
+
+Standard/generic (8250/16550 and compatible UARTs) serial support
CONFIG_SERIAL
This selects whether you want to include the driver for the standard
- serial ports. The standard answer is Y. People who might say N here
- are those that are setting up dedicated Ethernet WWW/FTP servers, or
- users that have one of the various bus mice instead of a serial
- mouse and don't intend to use their machine's standard serial port
- for anything. (Note that the Cyclades and Stallion multi serial port
- drivers do not need this driver built in for them to work.)
+ serial ports. The standard answer is Y. People who might say N
+ here are those that are setting up dedicated Ethernet WWW/FTP
+ servers, or users that have one of the various bus mice instead of a
+ serial mouse and don't intend to use their machine's standard serial
+ port for anything. (Note that the Cyclades and Stallion multi
+ serial port drivers do not need this driver built in for them to
+ work.)
If you want to compile this driver as a module, say M here and read
- Documentation/modules.txt. The module will be called serial.o.
+ <file:Documentation/modules.txt>. The module will be called
+ serial.o.
[WARNING: Do not compile this driver as a module if you are using
non-standard serial ports, since the configuration information will
- be lost when the driver is unloaded. This limitation may be lifted
+ be lost when the driver is unloaded. This limitation may be lifted
in the future.]
BTW1: If you have a mouseman serial mouse which is not recognized by
- the X window system, try running gpm first.
-
+ the X window system, try running gpm first.
+
BTW2: If you intend to use a software modem (also called Winmodem)
- under Linux, forget it. These modems are crippled and require
+ under Linux, forget it. These modems are crippled and require
proprietary drivers which are only available under Windows.
Most people will say Y or M here, so that they can use serial mice,
@@ -13671,7 +15649,8 @@
become a dial-in server.
If you want to compile this driver as a module, say M here and read
- Documentation/modules.txt. The module will be called rocket.o.
+ <file:Documentation/modules.txt>. The module will be called
+ rocket.o.
Digiboard Intelligent async support
CONFIG_DIGIEPCA
@@ -13681,14 +15660,14 @@
box, for instance in order to become a dial-in server. This driver
supports the original PC (ISA) boards as well as PCI, and EISA. If
you have a card like this, say Y here and read the file
- Documentation/digiepca.txt.
+ <file:Documentation/digiepca.txt>.
NOTE: There is another, separate driver for the Digiboard PC boards:
"Digiboard PC/Xx Support" below. You should (and can) only select
- one of the two drivers.
+ one of the two drivers.
If you want to compile this driver as a module, say M here and read
- Documentation/modules.txt. The module will be called epca.o.
+ <file:Documentation/modules.txt>. The module will be called epca.o.
Digiboard PC/Xx Support
CONFIG_DIGI
@@ -13696,10 +15675,10 @@
that give you many serial ports. You would need something like this
to connect more than two modems to your Linux box, for instance in
order to become a dial-in server. If you have a card like that, say
- Y here and read the file Documentation/digiboard.txt.
+ Y here and read the file <file:Documentation/digiboard.txt>.
If you want to compile this driver as a module, say M here and read
- Documentation/modules.txt. The module will be called pcxx.o.
+ <file:Documentation/modules.txt>. The module will be called pcxx.o.
SDL RISCom/8 card support
CONFIG_RISCOM8
@@ -13707,7 +15686,7 @@
which gives you many serial ports. You would need something like
this to connect more than two modems to your Linux box, for instance
in order to become a dial-in server. If you have a card like that,
- say Y here and read the file Documentation/riscom8.txt.
+ say Y here and read the file <file:Documentation/riscom8.txt>.
Also it's possible to say M here and compile this driver as kernel
loadable module; the module will be called riscom8.o.
@@ -13715,37 +15694,50 @@
Computone IntelliPort Plus serial support
CONFIG_COMPUTONE
This driver supports the entire family of Intelliport II/Plus
- controllers with the exception of the MicroChannel controllers and
+ controllers with the exception of the MicroChannel controllers and
products previous to the Intelliport II. These are multiport cards,
- which give you many serial ports. You would need something like
- this to connect more than two modems to your Linux box, for
- instance in order to become a dial-in server. If you have a
- card like that, say Y here and read Documentation/computone.txt.
+ which give you many serial ports. You would need something like this
+ to connect more than two modems to your Linux box, for instance in
+ order to become a dial-in server. If you have a card like that, say
+ Y here and read <file:Documentation/computone.txt>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. You will get two
- modules called ip2.o and ip2main.o.
+ say M here and read <file:Documentation/modules.txt>. You will get
+ two modules called ip2.o and ip2main.o.
Specialix IO8+ card support
CONFIG_SPECIALIX
This is a driver for the Specialix IO8+ multiport card (both the
- ISA and the PCI version) which gives you many serial ports. You
- would need something like this to connect more than two modems to
+ ISA and the PCI version) which gives you many serial ports. You
+ would need something like this to connect more than two modems to
your Linux box, for instance in order to become a dial-in server.
If you have a card like that, say Y here and read the file
- Documentation/specialix.txt. Also it's possible to say M here and
- compile this driver as kernel loadable module which will be called
- specialix.o.
+ <file:Documentation/specialix.txt>. Also it's possible to say M here
+ and compile this driver as kernel loadable module which will be
+ called specialix.o.
Specialix DTR/RTS pin is RTS
CONFIG_SPECIALIX_RTSCTS
- The Specialix card can only support either RTS or DTR. If you say N
- here, the driver will use the pin as "DTR" when the tty is in
- software handshake mode. If you say Y here or hardware handshake is
- on, it will always be RTS. Read the file Documentation/specialix.txt
- for more information.
+ The Specialix IO8+ card can only support either RTS or DTR. If you
+ say N here, the driver will use the pin as "DTR" when the tty is in
+ software handshake mode. If you say Y here or hardware handshake is
+ on, it will always be RTS. Read the file
+ <file:Documentation/specialix.txt> for more information.
+
+Specialix RIO system support
+CONFIG_RIO
+ This is a driver for the Specialix RIO, a smart serial card which
+ drives an outboard box that can support up to 128 ports. Product
+ information is at <http://www.sphinxcst.co.uk/perle/multi.htm>.
+ There are both ISA and PCI versions.
+
+Support really old RIO/PCI cards
+CONFIG_RIO_OLDPCI
+ Older RIO PCI cards need some initialization-time configuration to
+ determine the IRQ and some control addresses. If you have a RIO and
+ this doesn't seem to work, try setting this to Y.
Cyclades async mux support
CONFIG_CYCLADES
@@ -13753,19 +15745,19 @@
would need something like this to connect more than two modems to
your Linux box, for instance in order to become a dial-in server.
For information about the Cyclades-Z card, read
- drivers/char/README.cycladesZ.
+ <file:drivers/char/README.cycladesZ>.
As of 1.3.9x kernels, this driver's minor numbers start at 0 instead
of 32.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called cyclades.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called cyclades.o.
If you haven't heard about it, it's safe to say N.
-Cyclades-Z interrupt mode operation (EXPERIMENTAL)
+Cyclades-Z interrupt mode operation
CONFIG_CYZ_INTR
The Cyclades-Z family of multiport cards allows 2 (two) driver op
modes: polling and interrupt. In polling mode, the driver will check
@@ -13775,47 +15767,47 @@
status of the Cyclades-Z ports. The default op mode is polling. If
unsure, say N.
-Stallion multiport serial support
+Stallion multiport serial support
CONFIG_STALDRV
- Stallion cards give you many serial ports. You would need something
+ Stallion cards give you many serial ports. You would need something
like this to connect more than two modems to your Linux box, for
- instance in order to become a dial-in server. If you say Y here, you
- will be asked for your specific card model in the next questions.
- Make sure to read drivers/char/README.stallion in this case. If you
- have never heard about all this, it's safe to say N.
+ instance in order to become a dial-in server. If you say Y here,
+ you will be asked for your specific card model in the next
+ questions. Make sure to read <file:Documentation/stallion.txt> in
+ this case. If you have never heard about all this, it's safe to
+ say N.
-Stallion EasyIO or EC8/32 support
+Stallion EasyIO or EC8/32 support
CONFIG_STALLION
If you have an EasyIO or EasyConnection 8/32 multiport Stallion
- card, then this is for you; say Y. Make sure to read
- Documentation/stallion.txt.
+ card, then this is for you; say Y. Make sure to read
+ <file:Documentation/stallion.txt>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called stallion.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called stallion.o.
Stallion EC8/64, ONboard, Brumby support
CONFIG_ISTALLION
If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
serial multiport card, say Y here. Make sure to read
- Documentation/stallion.txt.
+ <file:Documentation/stallion.txt>.
To compile it as a module ( = code which can be inserted in and
removed from the running kernel whenever you want), say M here and
- read Documentation/modules.txt. The module will be called
+ read <file:Documentation/modules.txt>. The module will be called
istallion.o.
Microgate SyncLink adapter support
CONFIG_SYNCLINK
- Provides support for the SyncLink ISA and PCI
- multiprotocol serial adapters. These adapters
- support asynchronous and HDLC bit synchronous
- communication up to 10Mbps (PCI adapter).
+ Provides support for the SyncLink ISA and PCI multiprotocol serial
+ adapters. These adapters support asynchronous and HDLC bit
+ synchronous communication up to 10Mbps (PCI adapter).
This driver can only be built as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called synclink.o. If you want to do that, say M
+ The module will be called synclink.o. If you want to do that, say M
here.
Synchronous HDLC line discipline support
@@ -13831,7 +15823,7 @@
Specialix SX (and SI) card support
CONFIG_SX
This is a driver for the SX and SI multiport serial cards.
- Please read the file Documentation/sx.txt for details.
+ Please read the file <file:Documentation/sx.txt> for details.
This driver can only be built as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -13839,14 +15831,14 @@
Hayes ESP serial port support
CONFIG_ESPSERIAL
- This is a driver which supports Hayes ESP serial ports. Both single
- port cards and multiport cards are supported. Make sure to read
- Documentation/hayes-esp.txt.
+ This is a driver which supports Hayes ESP serial ports. Both single
+ port cards and multiport cards are supported. Make sure to read
+ <file:Documentation/hayes-esp.txt>.
To compile this driver as a module ( = code which can be inserted in
and removed from the running kernel whenever you want), say M here
- and read Documentation/modules.txt. The module will be called esp.o.
- If unsure, say N.
+ and read <file:Documentation/modules.txt>. The module will be
+ called esp.o. If unsure, say N.
Moxa Intellio support
CONFIG_MOXA_INTELLIO
@@ -13866,13 +15858,14 @@
The module will be called mxser.o. If you want to do that, say M
here.
-Multi-Tech multiport card support (EXPERIMENTAL)
+Multi-Tech multiport card support
CONFIG_ISI
This is a driver for the Multi-Tech cards which provide several
- serial ports. The driver is experimental and can currently only be
+ serial ports. The driver is experimental and can currently only be
built as a module ( = code which can be inserted in and removed from
- the running kernel whenever you want). Please read
- Documentation/modules.txt. The module will be called isicom.o
+ the running kernel whenever you want). Please read
+ <file:Documentation/modules.txt>. The module will be called
+ isicom.o.
Unix98 PTY support
CONFIG_UNIX98_PTYS
@@ -13882,7 +15875,7 @@
read data from and write data to the slave, thereby emulating a
terminal. Typical programs for the master side are telnet servers
and xterms.
-
+
Linux has traditionally used the BSD-like names /dev/ptyxx for
masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
has a number of problems. The GNU C library glibc 2.1 and later,
@@ -13898,8 +15891,8 @@
If you want to say Y here, you need to have the C library glibc 2.1
or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
- Read the instructions in Documentation/Changes pertaining to pseudo
- terminals. It's safe to say N.
+ Read the instructions in <file:Documentation/Changes> pertaining to
+ pseudo terminals. It's safe to say N.
Maximum number of Unix98 PTYs in use (0-2048)
CONFIG_UNIX98_PTY_COUNT
@@ -13916,23 +15909,23 @@
CONFIG_PRINTER
If you intend to attach a printer to the parallel port of your Linux
box (as opposed to using a serial printer; if the connector at the
- printer has 9 or 25 holes ["female"], then it's serial), say Y. Also
- read the Printing-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ printer has 9 or 25 holes ["female"], then it's serial), say Y.
+ Also read the Printing-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
It is possible to share one parallel port among several devices
(e.g. printer and ZIP drive) and it is safe to compile the
- corresponding drivers into the kernel. If you want to compile this
+ corresponding drivers into the kernel. If you want to compile this
driver as a module however ( = code which can be inserted in and
removed from the running kernel whenever you want), say M here and
- read Documentation/modules.txt and Documentation/parport.txt. The
- module will be called lp.o.
+ read <file:Documentation/modules.txt> and
+ <file:Documentation/parport.txt>. The module will be called lp.o.
If you have several parallel ports, you can specify which ports to
- use with the "lp" kernel command line option. (Try "man bootparam"
+ use with the "lp" kernel command line option. (Try "man bootparam"
or see the documentation of your boot loader (lilo or loadlin) about
- how to pass options to the kernel at boot time.) The syntax of the
- "lp" command line option can be found in drivers/char/lp.c.
+ how to pass options to the kernel at boot time.) The syntax of the
+ "lp" command line option can be found in <file:drivers/char/lp.c>.
If you have more than 8 printers, you need to increase the LP_NO
macro in lp.c and the PARPORT_MAX macro in parport.h.
@@ -13949,7 +15942,7 @@
By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
can make the kernel continue when this happens,
but it'll lose the kernel messages.
-
+
If unsure, say N.
Support for user-space parallel port device drivers
@@ -13963,74 +15956,206 @@
It is safe to say N to this -- it is not needed for normal printing
or parallel port CD-ROM/disk support.
- This support is also available as a module. If you want to compile
- it as a module, say M here and read Documentation/modules.txt. The
- module will be called ppdev.o.
+ This support is also available as a module. If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>. The module will be called
+ ppdev.o.
If unsure, say N.
+Cobalt Networks support
+CONFIG_COBALT
+ Support for Cobalt Networks x86-based servers.
+
+Gen III (3000 series) system support
+CONFIG_COBALT_GEN_III
+ This option enables support for the 3000 series of Cobalt Networks
+ systems. This includes the RaQ 3, RaQ 4, and Qube 3 product lines.
+
+ This platform uses an AMD K6-2 processor, an ALI M1541/1533 chipset,
+ an optional NCR 53c875 SCSI controller, and two Intel 82559ER or
+ National Semiconductor DP83815 NICs.
+
+ Getting this option wrong will likely result in a kernel that does
+ not boot. Selecting support for more than 1 system series will add
+ bloat to your kernel, but will not cause anything bad to happen.
+
+ If you have a Cobalt Networks System, but aren't sure what kind,
+ say Y here.
+
+Gen V (5000 series) system support
+CONFIG_COBALT_GEN_V
+ This option enables support for the 5000 series of Cobalt Networks
+ systems. This includes the RaQ XTR product line.
+
+ This platform uses Intel Pentium III Coppermine FCPGA CPUs, the
+ ServerWorks LE chipset (with registered ECC DIMMs only!), two
+ HighPoint HPT370 IDE controllers, and two National Semiconductor
+ DP83815 NICs.
+
+ Getting this option wrong will likely result in a kernel that does
+ not boot. Selecting support for more than 1 system series will add
+ bloat to your kernel, but will not cause anything bad to happen.
+
+ If you have a Cobalt Networks System, but aren't sure what kind,
+ say Y here.
+
+Create legacy /proc files
+CONFIG_COBALT_OLDPROC
+ This option forces some Cobalt Networks drivers to support legacy
+ files in /proc. Older versions of these drivers exported files
+ directly in /proc, as opposed to the newer /proc/cobalt. If you say
+ N to this option, the old filenames will no longer be exported.
+ Regardless of your selection here, files in /proc/cobalt will be
+ exported. Of course, you have to include support for /proc fs, too.
+
+ It is safe to say Y here.
+
+Front panel LCD support
+CONFIG_COBALT_LCD
+ This enables support for the Cobalt Networks front panel. This is
+ for the LCD panel and buttons. The primary method for connection is
+ via the parallel port (IO base 0x370), but newer systems use an
+ I2C bus.
+
+ If you have a Cobalt Networks system, you should say Y here.
+
+Software controlled LED support
+CONFIG_COBALT_LED
+ This enables support for the software-controlled LEDs on Cobalt
+ Networks systems. This includes the fault light and front panel
+ LEDs on the RaQ XTR, the lightbar on the Qube 3, and others.
+
+ If you have a Cobalt Networks system, you should say Y here.
+
+Silicon serial number support
+CONFIG_COBALT_SERNUM
+ This enables support for the on-board serial number on Cobalt
+ Networks systems. This is a universally-unique 64-bit serial
+ number. Some systems use a Dallas DS2401 chip, others have an I2C
+ based EEPROM.
+
+ If you select Y here, the files /proc/cobalt/hostid and
+ /proc/cobalt/serialnumber will be created. The hostid file contains
+ a 32 bit integer generated from the serial number, in binary form.
+ The serialnumber file contains the hexadecimal representation of the
+ serial number, in ASCII.
+
+ If you have a Cobalt Networks system, you should say Y here.
+
+Chipset watchdog timer support
+CONFIG_COBALT_WDT
+ This enables support for the watchdog timer built into Cobalt
+ chipsets. The timer wakes up periodically, to make find out if
+ system has hung, or disabled interrupts too long. The result of
+ detecting a hang is a hard reboot.
+
+ If you have a Cobalt Networks system, you should say Y here.
+
+Thermal sensor support
+CONFIG_COBALT_THERMAL
+ This enables support for the thermal sensor(s) built into Cobalt
+ Networks systems. This driver exports /proc/cobalt/thermal_sensors.
+
+ If you have a Cobalt Networks system, you should say Y here.
+
+Fan tachometer support
+CONFIG_COBALT_FANS
+ This enables support for the fan tachometers built into some Cobalt
+ Networks systems. This driver exports /proc/cobalt/faninfo. Some
+ Cobalt software depends on this feature, and enabling it does not
+ cause any risks.
+
+ If you have a Cobalt Networks system, you should say Y here, unless
+ you are absolutely sure.
+
+Disk drive ruler support
+CONFIG_COBALT_RULER
+ This enables support for the cobalt hard drive ruler, found on some
+ Cobalt systems, including the RaQ XTR. This is the device that
+ enables swapping of drives. It is not needed for basic disk
+ operation. Enabling this on a system with no ruler will have no
+ adverse effects.
+
+ If you have a Cobalt Networks system, you should say Y here,
+ unless you are absolutely sure.
+
I2C support
CONFIG_I2C
I2C (pronounce: I-square-C) is a slow serial bus protocol used in
- many micro controller applications and developed by Philips. SMBus,
- or System Management Bus is a subset of the I2C protocol. More
- information is contained in the directory Documentation/i2c/,
+ many micro controller applications and developed by Philips. SMBus,
+ or System Management Bus is a subset of the I2C protocol. More
+ information is contained in the directory <file:Documentation/i2c/>,
especially in the file called "summary" there.
Both I2C and SMBus are supported here. You will need this for
- hardware sensors support, and also for Video for Linux support.
+ hardware sensors support, and also for Video For Linux support.
Specifically, if you want to use a BT848 based frame grabber/overlay
boards under Linux, say Y here and also to "I2C bit-banging
interfaces", below.
If you want I2C support, you should say Y here and also to the
- specific driver for your bus adapter(s) below. If you say Y to
+ specific driver for your bus adapter(s) below. If you say Y to
"/proc file system" below, you will then get a /proc interface which
- is documented in Documentation/i2c/proc-interface.
+ is documented in <file:Documentation/i2c/proc-interface>.
- This I2C support is also available as a module. If you want to
+ This I2C support is also available as a module. If you want to
compile it as a module, say M here and read
- Documentation/modules.txt. The module will be called i2c-core.o.
+ <file:Documentation/modules.txt>.
+ The module will be called i2c-core.o.
+
+UltraSPARC-III bootbus i2c controller driver
+CONFIG_BBC_I2C
+ The BBC devices on the UltraSPARC III have two I2C controllers. The
+ first I2C controller connects mainly to configuration PROMs (NVRAM,
+ CPU configuration, DIMM types, etc.). The second I2C controller
+ connects to environmental control devices such as fans and
+ temperature sensors. The second controller also connects to the
+ smartcard reader, if present. Say Y to enable support for these.
I2C bit-banging interfaces
CONFIG_I2C_ALGOBIT
This allows you to use a range of I2C adapters called bit-banging
- adapters. Say Y if you own an I2C adapter belonging to this class
+ adapters. Say Y if you own an I2C adapter belonging to this class
and then say Y to the specific driver for you adapter below.
- This support is also available as a module. If you want to compile
- it as a module, say M here and read Documentation/modules.txt. The
- module will be called i2c-algo-bit.o.
+ This support is also available as a module. If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>.
+ The module will be called i2c-algo-bit.o.
Philips style parallel port adapter
CONFIG_I2C_PHILIPSPAR
- This supports parallel-port I2C adapters made by Philips. Say Y if
+ This supports parallel-port I2C adapters made by Philips. Say Y if
you own such an adapter.
- This driver is also available as a module. If you want to compile
- it as a module, say M here and read Documentation/modules.txt. The
- module will be called i2c-philips-par.o.
+ This driver is also available as a module. If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>.
+ The module will be called i2c-philips-par.o.
Note that if you want support for different parallel port devices,
life will be much easier if you compile them all as modules.
ELV adapter
CONFIG_I2C_ELV
- This supports parallel-port I2C adapters called ELV. Say Y if you
+ This supports parallel-port I2C adapters called ELV. Say Y if you
own such an adapter.
- This driver is also available as a module. If you want to compile
- it as a module, say M here and read Documentation/modules.txt. The
- module will be called i2c-elv.o.
+ This driver is also available as a module. If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>.
+ The module will be called i2c-elv.o.
Velleman K9000 adapter
CONFIG_I2C_VELLEMAN
- This supports the Velleman K9000 parallel-port I2C adapter. Say Y if
- you own such an adapter.
+ This supports the Velleman K9000 parallel-port I2C adapter. Say Y
+ if you own such an adapter.
- This driver is also available as a module. If you want to compile
- it as a module, say M here and read Documentation/modules.txt. The
- module will be called i2c-velleman.o.
+ This driver is also available as a module. If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>.
+ The module will be called i2c-velleman.o.
I2C PCF 8584 interfaces
CONFIG_I2C_ALGOPCF
@@ -14038,29 +16163,41 @@
Say Y if you own an I2C adapter belonging to this class and then say
Y to the specific driver for you adapter below.
- This support is also available as a module. If you want to compile
- it as a module, say M here and read Documentation/modules.txt. The
- module will be called i2c-algo-pcf.o.
+ This support is also available as a module. If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>.
+ The module will be called i2c-algo-pcf.o.
Elektor ISA card
CONFIG_I2C_ELEKTOR
- This supports the PCF8584 ISA bus I2C adapter. Say Y if you own such
- an adapter.
+ This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
+ such an adapter.
- This driver is also available as a module. If you want to compile
- it as a module, say M here and read Documentation/modules.txt. The
- module will be called i2c-elektor.o.
+ This driver is also available as a module. If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>.
+ The module will be called i2c-elektor.o.
I2C device interface
CONFIG_I2C_CHARDEV
Say Y here to use i2c-* device files, usually found in the /dev
- directory on your system. They make it possible to have user-space
- programs use the I2C bus. Information on how to do this is contained
- in the file Documentation/i2c/dev-interface.
+ directory on your system. They make it possible to have user-space
+ programs use the I2C bus. Information on how to do this is
+ contained in the file <file:Documentation/i2c/dev-interface>.
+
+ This code is also available as a module. If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>.
+ The module will be called i2c-dev.o.
+
+I2C /proc support
+CONFIG_I2C_PROC
+ This provides support for i2c device entries in the /proc filesystem.
+ The entries will be found in /proc/sys/dev/sensors.
This code is also available as a module. If you want to compile
- it as a module, say M here and read Documentation/modules.txt. The
- module will be called i2c-dev.o.
+ it as a module, say M here and read <file:Documentation/modules.txt>.
+ The module will be called i2c-proc.o.
Bus Mouse Support
CONFIG_BUSMOUSE
@@ -14069,11 +16206,11 @@
Microsoft mouse (made by Logitech) that plugs into a COM port
(rectangular with 9 or 25 pins). These people say N here. If you
have something else, read the Busmouse-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto , and say Y here.
+ <http://www.linuxdoc.org/docs.html#howto>, and say Y here.
If you have a laptop, you either have to check the documentation or
experiment a bit to find out whether the trackball is a serial mouse
- or not; it's best to say Y here for you.
+ or not; it's best to say Y here for you.
This is the generic bus mouse driver code. If you have a bus mouse,
you will have to say Y here and also to the specific driver for your
@@ -14082,7 +16219,7 @@
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called busmouse.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
Mouse Support (not serial and bus mice)
CONFIG_MOUSE
@@ -14092,30 +16229,30 @@
MouseSystem or Microsoft mouse (made by Logitech) that plugs into a
COM port (rectangular with 9 or 25 pins). These people say N here.
If you have something else, read the Busmouse-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . This HOWTO contains
+ <http://www.linuxdoc.org/docs.html#howto>. This HOWTO contains
information about all non-serial mice, not just bus mice.
If you have a laptop, you either have to check the documentation or
experiment a bit to find out whether the trackball is a serial mouse
- or not; it's best to say Y here for you.
+ or not; it's best to say Y here for you.
Note that the answer to this question won't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all
the questions about non-serial mice. If unsure, say Y.
Logitech busmouse support
CONFIG_LOGIBUSMOUSE
- Logitech mouse connected to a proprietary interface card. It's
+ Logitech mouse connected to a proprietary interface card. It's
generally a round connector with 9 pins. Note that the newer mice
made by Logitech don't use the Logitech protocol anymore; for those,
- you don't need this option. You want to read the Busmouse-HOWTO ,
- available from http://www.linuxdoc.org/docs.html#howto .
+ you don't need this option. You want to read the Busmouse-HOWTO,
+ available from <http://www.linuxdoc.org/docs.html#howto>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called busmouse.o. If you are unsure, say N and read the HOWTO
- nevertheless: it will tell you what you have.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called busmouse.o. If you are unsure, say N and read the
+ HOWTO nevertheless: it will tell you what you have.
PS/2 mouse (aka "auxiliary device") support
CONFIG_PSMOUSE
@@ -14129,12 +16266,12 @@
Although PS/2 mice are not technically bus mice, they are explained
in detail in the Busmouse-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
When using a PS/2 mouse, you can get problems if you want to use the
mouse both on the Linux console and under X. Using the "-R" option
of the Linux mouse managing program gpm (available from
- ftp://metalab.unc.edu/pub/Linux/system/mouse ) solves this
+ <ftp://metalab.unc.edu/pub/Linux/system/mouse>) solves this
problem, or you can get the "mconv2" utility from the same location.
C&T 82C710 mouse port support (as on TI Travelmate)
@@ -14142,25 +16279,25 @@
This is a certain kind of PS/2 mouse used on the TI Travelmate. If
you are unsure, try first to say N here and come back if the mouse
doesn't work. Read the Busmouse-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
PC110 digitizer pad support
CONFIG_PC110_PAD
- This drives the digitizer pad on the IBM PC110 palmtop. It can turn
+ This drives the digitizer pad on the IBM PC110 palmtop. It can turn
the digitizer pad into a PS/2 mouse emulation with tap gestures or
into an absolute pad.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called pc110pad.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called pc110pad.o.
Microsoft busmouse support
CONFIG_MS_BUSMOUSE
These animals (also called Inport mice) are connected to an
expansion board using a round connector with 9 pins. If this is what
you have, say Y and read the Busmouse-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
If you are unsure, say N and read the HOWTO nevertheless: it will
tell you what you have. Also be aware that several vendors talk
@@ -14169,41 +16306,33 @@
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called msbusmouse.o.
-
-Apple Desktop Bus support
-CONFIG_ADB
- Apple Desktop Bus (ADB) support is for support of devices which
- are connected to an ADB port. ADB devices tend to have 4 pins.
- If you have an Apple Macintosh prior to the iMac, or a
- "Blue and White G3", you probably want to say Y here. Otherwise
- say N.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called msbusmouse.o.
Apple Desktop Bus mouse support
CONFIG_ADBMOUSE
Say Y here if you have this type of bus mouse (4 pin connector) as
- is common on Macintoshes. You may want to read the Busmouse-HOWTO,
- available from http://www.linuxdoc.org/docs.html#howto .
+ is common on Macintoshes. You may want to read the Busmouse-HOWTO,
+ available from <http://www.linuxdoc.org/docs.html#howto>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called adbmouse.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called adbmouse.o.
ATIXL busmouse support
CONFIG_ATIXL_BUSMOUSE
This is a rare type of busmouse that is connected to the back of an
- ATI video card. Say Y if you have one of those. Note however that
+ ATI video card. Say Y if you have one of those. Note however that
most mice by ATI are actually Microsoft busmice; you should say Y to
- "Microsoft busmouse support" above if you have one of those. Read
+ "Microsoft busmouse support" above if you have one of those. Read
the Busmouse-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.linuxdoc.org/docs.html#howto>.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called atixlmouse.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called atixlmouse.o.
If you are unsure, say N and read the HOWTO nevertheless: it will
tell you what you have.
@@ -14213,29 +16342,34 @@
If you have a non-SCSI tape drive like that, say Y. Or, if you want
to compile this driver as a module ( = code which can be inserted in
and removed from the running kernel whenever you want), say M here
- and read Documentation/modules.txt. The module will be called
+ and read <file:Documentation/modules.txt>. The module will be called
tpqic02.o.
+iSeries Virtual Tape Support
+CONFIG_VIOTAPE
+ If you are running Linux on an iSeries system and you want Linux
+ to read and/or write a tape drive owned by OS/400, say Y here.
+
Do you want runtime configuration for QIC-02
CONFIG_QIC02_DYNCONF
You can either configure this driver once and for all by editing a
- header file (include/linux/tpqic02.h), in which case you should
- say N, or you can fetch a program via anonymous FTP which is able
- to configure this driver during runtime. The program to do this is
- called 'qic02conf' and it is part of the tpqic02-support-X.Y.tar.gz
- support package.
+ header file (<file:include/linux/tpqic02.h>), in which case you
+ should say N, or you can fetch a program via anonymous FTP which is
+ able to configure this driver during runtime. The program to do
+ this is called 'qic02conf' and it is part of the
+ tpqic02-support-X.Y.tar.gz support package.
If you want to use the qic02conf program, say Y.
Floppy tape drive (QIC-80/40/3010/3020/TR-1/TR-2/TR-3) support
CONFIG_FTAPE
If you have a tape drive that is connected to your floppy
- controller, say Y here.
+ controller, say Y here.
Some tape drives (like the Seagate "Tape Store 3200" or the Iomega
"Ditto 3200" or the Exabyte "Eagle TR-3") come with a "high speed"
controller of their own. These drives (and their companion
- controllers) are also supported if you say Y here.
+ controllers) are also supported if you say Y here.
If you have a special controller (such as the CMS FC-10, FC-20,
Mountain Mach-II, or any controller that is based on the Intel 82078
@@ -14243,56 +16377,57 @@
Iomega's "Ditto Dash") you must configure it by selecting the
appropriate entries from the "Floppy tape controllers" sub-menu
below and possibly modify the default values for the IRQ and DMA
- channel and the IO base in ftape's configuration menu.
+ channel and the IO base in ftape's configuration menu.
If you want to use your floppy tape drive on a PCI-bus based system,
- please read the file drivers/char/ftape/README.PCI.
+ please read the file <file:drivers/char/ftape/README.PCI>.
The ftape kernel driver is also available as a runtime loadable
module ( = code which can be inserted in and removed from the
running kernel whenever you want). If you want to compile it as a
- module, say M here and read Documentation/modules.txt. The module
- will be called ftape.o.
+ module, say M here and read <file:Documentation/modules.txt>. The
+ module will be called ftape.o.
Note that the Ftape-HOWTO is out of date (sorry) and documents the
older version 2.08 of this software but still contains useful
- information. There is a web page with more recent documentation at
- http://www.math1.rwth-aachen.de/~heine/ftape/ . This page
+ information. There is a web page with more recent documentation at
+ <http://www.math1.rwth-aachen.de/~heine/ftape/>. This page
always contains the latest release of the ftape driver and useful
information (backup software, ftape related patches and
- documentation, FAQ). Note that the file system interface has changed
- quite a bit compared to previous versions of ftape. Please read
- Documentation/ftape.txt.
+ documentation, FAQ). Note that the file system interface has
+ changed quite a bit compared to previous versions of ftape. Please
+ read <file:Documentation/ftape.txt>.
-The file system interface for ftape
+VFS interface for ftape
CONFIG_ZFTAPE
Normally, you want to say Y or M. DON'T say N here or you
WON'T BE ABLE TO USE YOUR FLOPPY TAPE DRIVE.
The ftape module itself no longer contains the routines necessary
to interface with the kernel VFS layer (i.e. to actually write data
- to and read data from the tape drive). Instead the file system
+ to and read data from the tape drive). Instead the file system
interface (i.e. the hardware independent part of the driver) has
been moved to a separate module.
If you say M zftape will be compiled as a runtime loadable
module ( = code which can be inserted in and removed from the
- running kernel whenever you want). In this case you should read
- Documentation/modules.txt. The module will be called zftape.o.
+ running kernel whenever you want). In this case you should read
+ <file:Documentation/modules.txt>. The module will be called
+ zftape.o.
Regardless of whether you say Y or M here, an additional runtime
loadable module called `zft-compressor.o' which contains code to
support user transparent on-the-fly compression based on Ross
- William's lzrw3 algorithm will be produced. If you have enabled the
+ William's lzrw3 algorithm will be produced. If you have enabled the
kernel module loader (i.e. have said Y to "Kernel module loader
support", above) then `zft-compressor.o' will be loaded
automatically by zftape when needed.
- Despite its name, zftape does NOT use compression by default. The
- file Documentation/ftape.txt contains a short description of the
- most important changes in the file system interface compared to
- previous versions of ftape. The ftape home page
- http://www-math.math.rwth-aachen.de/~LBFM/claus/ftape/ contains
+ Despite its name, zftape does NOT use compression by default. The
+ file <file:Documentation/ftape.txt> contains a short description of
+ the most important changes in the file system interface compared to
+ previous versions of ftape. The ftape home page
+ <http://www-math.math.rwth-aachen.de/~LBFM/claus/ftape/> contains
further information.
IMPORTANT NOTE: zftape can read archives created by previous
@@ -14331,7 +16466,7 @@
wastes 32 KB of memory. Please note that this memory cannot be
swapped out.
-Procfs entry for ftape
+Enable procfs status report (+2kb)
CONFIG_FT_PROC_FS
Optional. Saying Y will result in creation of a directory
`/proc/ftape' under the /proc file system. The files can be viewed
@@ -14348,6 +16483,7 @@
interface. Accessing `/proc/ftape' while the module is unloaded will
result in a kernel Oops. This cannot be fixed from inside ftape.
+# Choice: ftdebug
Controlling the amount of debugging output of ftape
CONFIG_FT_NORMAL_DEBUG
This option controls the amount of debugging output the ftape driver
@@ -14369,9 +16505,22 @@
printed to the console but only makes it possible to produce
"Excessive" debugging output.
- Please read Documentation/ftape.txt for a short description
+ Please read <file:Documentation/ftape.txt> for a short description
how to control the amount of debugging output.
+Excessive
+CONFIG_FT_FULL_DEBUG
+ Extremely verbose output for driver debugging purposes.
+
+Reduced
+CONFIG_FT_NO_TRACE
+ Reduced tape driver debugging output.
+
+None
+CONFIG_FT_NO_TRACE_AT_ALL
+ Suppress all debugging output from the tape drive.
+
+# Choice: ftcontroller
The floppy drive controller for ftape
CONFIG_FT_STD_FDC
Only change this setting if you have a special controller. If you
@@ -14407,13 +16556,13 @@
have said Y to "Floppy tape drive") or module load time (i.e. if you
have said M to "Floppy tape drive").
- Please read also the file Documentation/ftape.txt which
+ Please read also the file <file:Documentation/ftape.txt> which
contains a short description of the parameters that can be set at
boot or load time. If you want to use your floppy tape drive on a
PCI-bus based system, please read the file
- drivers/char/ftape/README.PCI.
+ <file:drivers/char/ftape/README.PCI>.
-IO base of the floppy disk controller used with Ftape
+IO base for the floppy disk controller used with Ftape
CONFIG_FT_FDC_BASE
You don't need to specify a value if the following default
settings for the base IO address are correct:
@@ -14435,9 +16584,9 @@
"Floppy tape drive") or module load time (i.e. if you have said M to
"Floppy tape drive").
- Please read also the file Documentation/ftape.txt which contains a
- short description of the parameters that can be set at boot or load
- time.
+ Please read also the file <file:Documentation/ftape.txt> which
+ contains a short description of the parameters that can be set at
+ boot or load time.
IRQ channel for the floppy disk controller used with Ftape
CONFIG_FT_FDC_IRQ
@@ -14461,9 +16610,9 @@
"Floppy tape drive") or module load time (i.e. if you said M to
"Floppy tape drive").
- Please read also the file Documentation/ftape.txt which contains a
- short description of the parameters that can be set at boot or load
- time.
+ Please read also the file <file:Documentation/ftape.txt> which
+ contains a short description of the parameters that can be set at
+ boot or load time.
DMA channel for the floppy disk controller used with Ftape
CONFIG_FT_FDC_DMA
@@ -14487,9 +16636,9 @@
"Floppy tape drive") or module load time (i.e. if you said M to
"Floppy tape drive").
- Please read also the file Documentation/ftape.txt which contains a
- short description of the parameters that can be set at boot or load
- time.
+ Please read also the file <file:Documentation/ftape.txt> which
+ contains a short description of the parameters that can be set at
+ boot or load time.
FDC FIFO Threshold before requesting DMA service
CONFIG_FT_FDC_THR
@@ -14521,10 +16670,16 @@
introduced in XFree86 4.0. If you say Y here, you need to select
the module that's right for your graphics card from the list below.
These modules provide support for synchronization, security, and
- DMA transfers. Please see http://dri.sourceforge.net for more
+ DMA transfers. Please see <http://dri.sourceforge.net> for more
details. You should also select and configure AGP
(/dev/agpgart) support.
+Build drivers for new (XFree 4.1) DRM
+CONFIG_DRM_NEW
+ If you set this option, the new DRM version needed by XFree86 4.1
+ will be used. Otherwise, the old DRM version will be used,
+ appropriate for XFree86 4.0.
+
3dfx Banshee/Voodoo3+
CONFIG_DRM_TDFX
Choose this option if you have a 3dfx Banshee or Voodoo3 (or later),
@@ -14541,19 +16696,69 @@
is selected, the module will be called r128.o. AGP support for
this card is strongly suggested (unless you have a PCI version).
+ATI Radeon
+CONFIG_DRM_RADEON
+ Choose this option if you have an ATI Radeon graphics card. There
+ are both PCI and AGP versions. You don't need to choose this to
+ run the Radeon in plain VGA mode. There is a product page at
+ <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
+ If M is selected, the module will be called radeon.o.
+
Intel I810
CONFIG_DRM_I810
Choose this option if you have an Intel I810 graphics card. If M is
selected, the module will be called i810.o. AGP support is required
for this driver to work.
-Matrox g200/g400
+Matrox G200/G400/G450
CONFIG_DRM_MGA
- Choose this option if you have a Matrox g200 or g400 graphics card. If M
- is selected, the module will be called mga.o. AGP support is required
+ Choose this option if you have a Matrox G200, G400 or G450 graphics
+ card. If M is selected, the module will be called mga.o. AGP
+ support is required for this driver to work.
+
+3dfx Banshee/Voodoo3+
+CONFIG_DRM40_TDFX
+ Choose this option if you have a 3dfx Banshee or Voodoo3 (or later),
+ graphics card. If M is selected, the module will be called tdfx.o.
+
+3dlabs GMX 2000
+CONFIG_DRM40_GAMMA
+ Choose this option if you have a 3dlabs GMX 2000 graphics card.
+ If M is selected, the module will be called gamma.o.
+
+ATI Rage 128
+CONFIG_DRM40_R128
+ Choose this option if you have an ATI Rage 128 graphics card. If M
+ is selected, the module will be called r128.o. AGP support for
+ this card is strongly suggested (unless you have a PCI version).
+
+ATI Radeon
+CONFIG_DRM40_RADEON
+ Choose this option if you have an ATI Radeon graphics card. There
+ are both PCI and AGP versions. You don't need to choose this to
+ run the Radeon in plain VGA mode. There is a product page at
+ <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
+ If M is selected, the module will be called radeon.o.
+
+Intel I810
+CONFIG_DRM40_I810
+ Choose this option if you have an Intel I810 graphics card. If M is
+ selected, the module will be called i810.o. AGP support is required
for this driver to work.
-MTRR control and configuration
+Matrox G200/G400/G450
+CONFIG_DRM40_MGA
+ Choose this option if you have a Matrox G200, G400 or G450 graphics
+ card. If M is selected, the module will be called mga.o. AGP
+ support is required for this driver to work.
+
+Creator/Creator3D/Elite3D
+CONFIG_DRM_FFB
+ Choose this option if you have one of Sun's Creator3D-based graphics
+ and frame buffer cards. Product page at
+ <http://www.sun.com/desktop/products/Graphics/creator3d.html>.
+
+MTRR (Memory Type Range Register) support
CONFIG_MTRR
On Intel P6 family processors (Pentium Pro, Pentium II and later)
the Memory Type Range Registers (MTRRs) may be used to control
@@ -14563,10 +16768,10 @@
before bursting over the PCI/AGP bus. This can increase performance
of image write operations 2.5 times or more. Saying Y here creates a
/proc/mtrr file which may be used to manipulate your processor's
- MTRRs. Typically the X server should use this.
+ MTRRs. Typically the X server should use this.
- This code has a reasonably generic interface so that similar
- control registers on other processors can be easily supported
+ This code has a reasonably generic interface so that similar
+ control registers on other processors can be easily supported
as well:
The Cyrix 6x86, 6x86MX and M II processors have Address Range
@@ -14584,9 +16789,9 @@
You can safely say Y even if your machine doesn't have MTRRs, you'll
just add about 9 KB to your kernel.
- See Documentation/mtrr.txt for more information.
+ See <file:Documentation/mtrr.txt> for more information.
-Main CPU frequency, only for DEC alpha machine
+CPU clock frequency of your DEC Alpha
CONFIG_FT_ALPHA_CLOCK
On some DEC Alpha machines the CPU clock frequency cannot be
determined automatically, so you need to specify it here ONLY if
@@ -14595,11 +16800,11 @@
Double Talk PC internal speech card support
CONFIG_DTLK
This driver is for the DoubleTalk PC, a speech synthesizer
- manufactured by RC Systems (http://www.rcsys.com/ ). It is also
+ manufactured by RC Systems (<http://www.rcsys.com/>). It is also
called the `internal DoubleTalk'. If you want to compile this as a
module ( = code which can be inserted in and removed from the
running kernel whenever you want), say M here and read
- Documentation/modules.txt. The module will be called dtlk.o.
+ <file:Documentation/modules.txt>. The module will be called dtlk.o.
Siemens R3964 serial protocol support
CONFIG_R3964
@@ -14609,7 +16814,7 @@
To compile this driver as a module ( = code which can be inserted in
and removed from the running kernel whenever you want), say M here
- and read Documentation/modules.txt. The module will be called
+ and read <file:Documentation/modules.txt>. The module will be called
n_r3964.o.
If unsure, say N.
@@ -14619,28 +16824,28 @@
This driver provides the kernel-side support for the intelligent
fieldbus cards made by Applicom International. More information
about these cards can be found on the WWW at the address
- http://www.applicom-int.com/ , or by email from David Woodhouse
+ <http://www.applicom-int.com/>, or by email from David Woodhouse
<dwmw2@infradead.org>.
To compile this driver as a module ( = code which can be inserted in
and removed from the running kernel whenever you want), say M here
- and read Documentation/modules.txt. The module will be called
+ and read <file:Documentation/modules.txt>. The module will be called
applicom.o.
If unsure, say N.
Sony Vaio Programmable I/O Control Device support
CONFIG_SONYPI
- This driver enables access to the Sony Programmable I/O Control Device
- which can be found in many (all ?) Sony Vaio laptops.
+ This driver enables access to the Sony Programmable I/O Control
+ Device which can be found in many (all ?) Sony Vaio laptops.
- If you have one of those laptops, read Documentation/sonypi.txt,
- and say Y or M here.
+ If you have one of those laptops, read
+ <file:Documentation/sonypi.txt>, and say Y or M here.
If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read <file:Documentation/modules.txt>. The module will be
- called sonypi.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called sonypi.o.
Intel Random Number Generator support
CONFIG_INTEL_RNG
@@ -14653,7 +16858,7 @@
To compile this driver as a module ( = code which can be inserted in
and removed from the running kernel whenever you want), say M here
- and read Documentation/modules.txt. The module will be called
+ and read <file:Documentation/modules.txt>. The module will be called
i810_rng.o.
If unsure, say N.
@@ -14662,50 +16867,76 @@
CONFIG_PM
"Power Management" means that parts of your computer are shut
off or put into a power conserving "sleep" mode if they are not
- being used. There are two competing standards for doing this: APM
- and ACPI. If you want to use either one, say Y here and then also to
- the requisite support below.
+ being used. There are two competing standards for doing this: APM
+ and ACPI. If you want to use either one, say Y here and then also
+ to the requisite support below.
Power Management is most important for battery powered laptop
computers; if you have a laptop, check out the Linux Laptop home
page on the WWW at
- http://www.cs.utexas.edu/users/kharker/linux-laptop/ and the Battery
- Powered Linux mini-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ <http://www.cs.utexas.edu/users/kharker/linux-laptop/> and the
+ Battery Powered Linux mini-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
Note that, even if you say N here, Linux on the x86 architecture
will issue the hlt instruction if nothing is to be done, thereby
sending the processor to sleep and saving power.
+USB SE401 Camera support
+CONFIG_USB_SE401
+ Say Y here if you want to connect this type of camera to your
+ computer's USB port. See <file:Documentation/usb/se401.txt> for more
+ information and for a list of supported cameras.
+
+ This driver uses the Video For Linux API. You must say Y or M to
+ "Video For Linux" (under Multimedia Devices) to use this driver.
+ Information on this API and pointers to "v4l" programs may be found
+ on the WWW at <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
+
+ This code is also available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ The module will be called se401.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
+
ACPI support
CONFIG_ACPI
- ACPI/OSPM support for Linux is currently under development. As such,
- this support is preliminary and EXPERIMENTAL. Configuring ACPI support
- enables kernel interfaces that allow higher level software (OSPM) to
- manipulate ACPI defined hardware and software interfaces, including
- the evaluation of ACPI control methods. If unsure, choose N here.
- Note, this option will enlarge your kernel by about 120K.
+ ACPI/OSPM support for Linux is currently under development. As such,
+ this support is preliminary and EXPERIMENTAL. Configuring ACPI
+ support enables kernel interfaces that allow higher level software
+ (OSPM) to manipulate ACPI defined hardware and software interfaces,
+ including the evaluation of ACPI control methods. If unsure, choose
+ N here. Note, this option will enlarge your kernel by about 120K.
This support requires an ACPI compliant platform (hardware/firmware).
If both ACPI and Advanced Power Management (APM) support are
configured, whichever is loaded first shall be used.
- This code DOES NOT currently provide a complete OSPM implementation --
- it has not yet reached APM's level of functionality. When fully
+ This code DOES NOT currently provide a complete OSPM implementation
+ -- it has not yet reached APM's level of functionality. When fully
implemented, Linux ACPI/OSPM will provide a more robust functional
- replacement for legacy configuration and power management interfaces,
- including the Plug-and-Play BIOS specification (PNP BIOS), the Multi-
- Processor Specification (MPS), and the Advanced Power Management
- specification (APM).
+ replacement for legacy configuration and power management
+ interfaces, including the Plug-and-Play BIOS specification (PnP
+ BIOS), the Multi-Processor Specification (MPS), and the Advanced
+ Power Management specification (APM).
Linux support for ACPI/OSPM is based on Intel Corporation's ACPI
Component Architecture (ACPI CA). The latest ACPI CA source code,
documentation, debug builds, and implementation status information
can be downloaded from:
- http://developer.intel.com/technology/iapc/acpi/downloads.htm
-
+ <http://developer.intel.com/technology/iapc/acpi/downloads.htm>.
+
The ACPI mailing list may also be of interest:
- http://phobos.fs.tum.de/acpi/index.html
+ <http://phobos.fs.tum.de/acpi/index.html>.
+
+Enable ACPI 2.0 with errata 1.3
+CONFIG_ACPI20
+ Enable support for the 2.0 version of the ACPI interpreter. See the
+ help for ACPI for caveats and discussion.
+
+ACPI kernel configuration manager
+CONFIG_ACPI_KERNEL_CONFIG
+ If you say `Y' here, Linux's ACPI support will use the
+ hardware-level system descriptions found on IA64 machines.
ACPI Debug Statements
CONFIG_ACPI_DEBUG
@@ -14716,37 +16947,39 @@
ACPI Bus Manager
CONFIG_ACPI_BUSMGR
The ACPI Bus Manager enumerates devices in the ACPI namespace, and
- handles PnP messages. All ACPI devices use its services, so using them
- requires saying Y here.
+ handles PnP messages. All ACPI devices use its services, so using
+ them requires saying Y here.
ACPI System Driver
CONFIG_ACPI_SYS
- This driver will enable your system to shut down using ACPI, and dump
- your ACPI DSDT table using /proc/acpi/dsdt.
+ This driver will enable your system to shut down using ACPI, and
+ dump your ACPI DSDT table using /proc/acpi/dsdt.
ACPI Processor Driver
CONFIG_ACPI_CPU
- This driver installs ACPI as the idle handler for Linux, and uses ACPI
- C2 and C3 processor states to save power, on systems that support it.
+ This driver installs ACPI as the idle handler for Linux, and uses
+ ACPI C2 and C3 processor states to save power, on systems that
+ support it.
ACPI Button
CONFIG_ACPI_BUTTON
- This driver registers for events based on buttons, such as the power,
- sleep, and lid switch. In the future, a daemon will read
+ This driver registers for events based on buttons, such as the
+ power, sleep, and lid switch. In the future, a daemon will read
/proc/acpi/event and perform user-defined actions such as shutting
- down the system. Until then, you can cat it, and see output when
+ down the system. Until then, you can cat it, and see output when
a button is pressed.
ACPI AC Adapter
CONFIG_ACPI_AC
This driver adds support for the AC Adapter object, which indicates
- whether a system is on AC, or not. Typically, only laptops have this
- object, since desktops are always on AC.
+ whether a system is on AC, or not. Typically, only laptops have
+ this object, since desktops are always on AC.
ACPI Embedded Controller
CONFIG_ACPI_EC
- This driver is required on some systems for the proper operation of the
- battery and thermal drivers. If you are compiling for a laptop, say Y.
+ This driver is required on some systems for the proper operation of
+ the battery and thermal drivers. If you are compiling for a laptop,
+ say Y.
ACPI Control Method Battery
CONFIG_ACPI_CMBATT
@@ -14774,13 +17007,13 @@
machines with more than one CPU.
In order to use APM, you will need supporting software. For location
- and more information, read Documentation/pm.txt and the Battery
- Powered Linux mini-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto .
+ and more information, read <file:Documentation/pm.txt> and the
+ Battery Powered Linux mini-HOWTO, available from
+ <http://www.linuxdoc.org/docs.html#howto>.
This driver does not spin down disk drives (see the hdparm(8)
manpage ("man 8 hdparm") for that), and it doesn't turn off
- VESA-compliant "green" monitors.
+ VESA-compliant "green" monitors.
This driver does not support the TI 4000M TravelMate and the ACER
486/DX4/75 because they don't have compliant BIOSes. Many "green"
@@ -14791,30 +17024,30 @@
much point in using this driver and you should say N. If you get
random kernel OOPSes or reboots that don't seem to be related to
anything, try disabling/enabling this option (or disabling/enabling
- APM in your BIOS).
+ APM in your BIOS).
Some other things you should try when experiencing seemingly random,
"weird" problems:
1) make sure that you have enough swap space and that it is
- enabled.
- 2) pass the "no-hlt" option to the kernel
+ enabled.
+ 2) pass the "no-hlt" option to the kernel
3) switch on floating point emulation in the kernel and pass
the "no387" option to the kernel
4) pass the "floppy=nodma" option to the kernel
- 5) pass the "mem=4M" option to the kernel (thereby disabling
+ 5) pass the "mem=4M" option to the kernel (thereby disabling
all but the first 4 MB of RAM)
6) make sure that the CPU is not over clocked.
- 7) read the sig11 FAQ at http://www.bitwizard.nl/sig11/
+ 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
8) disable the cache from your BIOS settings
9) install a fan for the video card or exchange video RAM
10) install a better fan for the CPU
- 11) exchange RAM chips
+ 11) exchange RAM chips
12) exchange the motherboard.
To compile this driver as a module ( = code which can be inserted in
and removed from the running kernel whenever you want), say M here
- and read Documentation/modules.txt. The module will be called
+ and read <file:Documentation/modules.txt>. The module will be called
apm.o.
Ignore USER SUSPEND
@@ -14839,7 +17072,7 @@
T400CDT. This is off by default since most machines do fine without
this feature.
-Do CPU IDLE calls
+Make CPU Idle calls when idle
CONFIG_APM_CPU_IDLE
Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
On some machines, this can activate improved power savings, such as
@@ -14887,7 +17120,7 @@
a work-around for a number of buggy BIOSes. Switch this option on if
your computer crashes instead of powering off properly.
-Watchdog Timer Support
+Watchdog Timer Support
CONFIG_WATCHDOG
If you say Y here (and to one of the following options) and create a
character special file /dev/watchdog with major number 10 and minor
@@ -14899,12 +17132,12 @@
implementation entirely in software (which can sometimes fail to
reboot the machine) and a driver for hardware watchdog boards, which
are more robust and can also keep track of the temperature inside
- your computer. For details, read Documentation/watchdog.txt in the
- kernel source.
+ your computer. For details, read <file:Documentation/watchdog.txt>
+ in the kernel source.
- The watchdog is usually used together with the watchdog daemon
+ The watchdog is usually used together with the watchdog daemon
which is available via FTP (user: anonymous) from
- ftp://tsx-11.mit.edu/pub/linux/sources/sbin/ . This daemon can also
+ <ftp://tsx-11.mit.edu/pub/linux/sources/sbin/>. This daemon can also
monitor NFS connections and can reboot the machine when the process
table is full.
@@ -14929,22 +17162,22 @@
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called wdt.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called wdt.o.
WDT PCI Watchdog timer
CONFIG_WDTPCI
- If you have a PCI WDT500/501 watchdog board, say Y here,
- otherwise N. It is not possible to probe for this board, which means
- that you have to inform the kernel about the IO port and IRQ using
- the "wdt=" kernel option (try "man bootparam" or see the
- documentation of your boot loader (lilo or loadlin) about how to
- pass options to the kernel at boot time).
+ If you have a PCI WDT500/501 watchdog board, say Y here, otherwise
+ N. It is not possible to probe for this board, which means that you
+ have to inform the kernel about the IO port and IRQ using the "wdt="
+ kernel option (try "man bootparam" or see the documentation of your
+ boot loader (lilo or loadlin) about how to pass options to the
+ kernel at boot time).
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called wdt_pci.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called wdt_pci.o.
WDT501 features
CONFIG_WDT_501
@@ -14964,12 +17197,13 @@
CONFIG_SOFT_WATCHDOG
A software monitoring watchdog. This will fail to reboot your system
from some situations that the hardware watchdog will recover
- from. Equally it's a lot cheaper to install.
+ from. Equally it's a lot cheaper to install.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. The module will be called softdog.o.
+ <file:Documentation/modules.txt>. The module will be called
+ softdog.o.
Berkshire Products PC Watchdog
CONFIG_PCWATCHDOG
@@ -14977,55 +17211,90 @@
This card simply watches your kernel to make sure it doesn't freeze,
and if it does, it reboots your computer after a certain amount of
time. This driver is like the WDT501 driver but for different
- hardware. Please read Documentation/pcwd-watchdog.txt. The PC
- watchdog cards can be ordered from http://www.berkprod.com .
+ hardware. Please read <file:Documentation/pcwd-watchdog.txt>. The PC
+ watchdog cards can be ordered from <http://www.berkprod.com>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module is called pcwd.o. If you want to compile it as a module,
- say M here and read Documentation/modules.txt.
+ say M here and read <file:Documentation/modules.txt>.
Most people will say N.
Acquire SBC Watchdog Timer
CONFIG_ACQUIRE_WDT
This is the driver for the hardware watchdog on the PSC-6x86 Single
- Board Computer produced by Acquire Inc (and others). This watchdog
+ Board Computer produced by Acquire Inc (and others). This watchdog
simply watches your kernel to make sure it doesn't freeze, and if
it does, it reboots your computer after a certain amount of time.
This driver is like the WDT501 driver but for different hardware.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module is called pscwdt.o. If you want to compile it as a
+ The module is called pscwdt.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>. Most
+ people will say N.
+
+Advantech SBC Watchdog Timer
+CONFIG_ADVANTECH_WDT
+ If you are configuring a Linux kernel for the Advantech single-board
+ computer, say `Y' here to support its built-in watchdog timer
+ feature. See the help for CONFIG_WATCHDOG for discussion.
+
+W83877F Watchdog Timer
+CONFIG_W83877F_WDT
+ This is the driver for the hardware watchdog on the W83877F chipset
+ as used in EMACS PC-104 motherboards (and likely others). This
+ watchdog simply watches your kernel to make sure it doesn't freeze,
+ and if it does, it reboots your computer after a certain amount of
+ time.
+
+ This driver is also available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ The module is called mixcomwd.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>. Most
+ people will say N.
+
+IB700 SBC Watchdog Timer
+CONFIG_IB700_WDT
+ This is the driver for the hardware watchdog on the IB700 Single
+ Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
+ simply watches your kernel to make sure it doesn't freeze, and if
+ it does, it reboots your computer after a certain amount of time.
+
+ This driver is like the WDT501 driver but for slightly different hardware.
+
+ This driver is also available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ The module is called ib700wdt.o. If you want to compile it as a
module, say M here and read Documentation/modules.txt. Most people
will say N.
Mixcom Watchdog
-CONFIG_MIXCOMWD
- This is a driver for the Mixcom hardware watchdog cards. This
+CONFIG_MIXCOMWD
+ This is a driver for the Mixcom hardware watchdog cards. This
watchdog simply watches your kernel to make sure it doesn't freeze,
and if it does, it reboots your computer after a certain amount of
time.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module is called mixcomwd.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt. Most people
- will say N.
+ The module is called mixcomwd.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>. Most
+ people will say N.
ZF MachZ Watchdog
CONFIG_MACHZ_WDT
- If you are using a ZF Micro MachZ processor, say Y here, otherwise N.
- This is the driver for the watchdog timer builtin on that processor
- using ZF-Logic interface. This watchdog simply watches your kernel to
- make sure it doesn't freeze, and if it does, it reboots your computer
- after a certain amount of time.
+ If you are using a ZF Micro MachZ processor, say Y here, otherwise
+ N. This is the driver for the watchdog timer builtin on that
+ processor using ZF-Logic interface. This watchdog simply watches
+ your kernel to make sure it doesn't freeze, and if it does, it
+ reboots your computer after a certain amount of time.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module is called machzwd.o. If you want to compile it as a module,
- say M here and read Documentation/modules.txt.
+ The module is called machzwd.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
SuperH 3/4 Watchdog
CONFIG_SH_WDT
@@ -15040,13 +17309,14 @@
Toshiba Laptop support
CONFIG_TOSHIBA
- This adds a driver to safely access the System Management Mode
- of the CPU on Toshiba portables. The System Management Mode
+ This adds a driver to safely access the System Management Mode of
+ the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
+ not work on models with a Pheonix BIOS. The System Management Mode
is used to set the BIOS and power saving options on Toshiba portables.
For information on utilities to make use of this driver see the
Toshiba Linux utilities web site at:
- http://www.buzzard.org.uk/toshiba/
+ <http://www.buzzard.org.uk/toshiba/>.
Say Y if you intend to run this kernel on a Toshiba portable.
Say N otherwise.
@@ -15065,7 +17335,7 @@
For information on utilities to make use of this driver see the
I8K Linux utilities web site at:
- http://www.debian.org/~dz/i8k/
+ <http://www.debian.org/~dz/i8k/>
Say Y if you intend to run this kernel on a Dell Inspiron 8000.
Say N otherwise.
@@ -15075,18 +17345,19 @@
If you say Y here and also to "/dev file system support" in the
'File systems' section, you will be able to update the microcode on
Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
- Pentium III, Pentium 4, Xeon etc. You will obviously need the actual
- microcode binary data itself which is not shipped with the Linux kernel.
+ Pentium III, Pentium 4, Xeon etc. You will obviously need the
+ actual microcode binary data itself which is not shipped with the
+ Linux kernel.
For latest news and information on obtaining all the required
ingredients for this driver, check:
- http://www.urbanmyth.org/microcode/
+ <http://www.urbanmyth.org/microcode/>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called microcode.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt. If you use
- modprobe or kmod you may also want to add the line
+ The module will be called microcode.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>. If
+ you use modprobe or kmod you may also want to add the line
'alias char-major-10-184 microcode' to your /etc/modules.conf file.
/dev/cpu/*/msr - Model-specific register support
@@ -15120,7 +17391,7 @@
CONFIG_RTC
If you say Y here and create a character special file /dev/rtc with
major number 10 and minor number 135 using mknod ("man mknod"), you
- will get access to the real time clock (or hardware clock) built
+ will get access to the real time clock (or hardware clock) built
into your computer.
Every PC has such a clock built in. It can be used to generate
@@ -15134,23 +17405,19 @@
and set the RTC in an SMP compatible fashion.
If you think you have a use for such a device (such as periodic data
- sampling), then say Y here, and read Documentation/rtc.txt for
- details.
+ sampling), then say Y here, and read <file:Documentation/rtc.txt>
+ for details.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module is called rtc.o. If you want to compile it as a module,
- say M here and read Documentation/modules.txt.
-
-### Add
-#EFI Real Time Clock Services
-#CONFIG_EFI_RTC
+ say M here and read <file:Documentation/modules.txt>.
Tadpole ANA H8 Support
CONFIG_H8
The Hitachi H8/337 is a microcontroller used to deal with the power
and thermal environment. If you say Y here, you will be able to
- communicate with it via a character special device.
+ communicate with it via a character special device.
If unsure, say N.
@@ -15160,7 +17427,7 @@
with major number 10 and minor number 144 using mknod ("man mknod"),
you get read and write access to the 50 bytes of non-volatile memory
in the real time clock (RTC), which is contained in every PC and
- most Ataris.
+ most Ataris.
This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
on Ataris. /dev/nvram may be used to view settings there, or to
@@ -15177,8 +17444,9 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called nvram.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
+# Linus tree only
Joystick support
CONFIG_JOYSTICK
If you have a joystick, 6dof controller, gamepad, steering wheel,
@@ -15186,232 +17454,299 @@
enable generic support for these controllers. You will also need to
say Y or M to at least one of the hardware specific drivers. This
will make the controllers available as /dev/input/jsX devices.
- Please read the file Documentation/joystick.txt which contains more
- information and the location of the joystick package that you'll
- need.
+ Please read the file <file:Documentation/joystick.txt> which
+ contains more information and the location of the joystick package
+ that you'll need.
+
+# AC tree only
+Game port support
+CONFIG_INPUT_GAMEPORT
+ Gameport support is for the standard 15-pin PC gameport. If you
+ have a joystick, gamepad, gameport card, a soundcard with a gameport
+ or anything else that uses the gameport, say Y or M here and also to
+ at least one of the hardware specific drivers.
+ Please read the file <file:Documentation/joystick.txt> which
+ contains more information and the location of the joystick package
+ that you'll need if you use the gameport with a joystick.
+
+ This driver is also available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ The module will be called gameport.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
-ns558 gameports
+Classic ISA/PnP gameports
CONFIG_INPUT_NS558
- Say Y here if you have an ISA, ISAPnP or PCI standard gameport.
+ Say Y here if you have an ISA or PnP gameport.
For more information on how to use the driver please read
- Documentation/joystick.txt
+ <file:Documentation/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called ns558.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ The module will be called ns558.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
PDPI Lightning 4 gamecard
CONFIG_INPUT_LIGHTNING
Say Y here if you have a PDPI Lightning 4 gamecard. For more
information on how to use the driver please read
- Documentation/joystick.txt
+ <file:Documentation/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called lightning.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ The module will be called lightning.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
+
+Crystal SoundFusion gameports
+CONFIG_INPUT_CS461X
+ Say Y here if you have a Cirrus CS461x aka "Crystal SoundFusion"
+ PCI audio accelerator. A product page for the CS4614 is at
+ <http://www.cirrus.com/design/products/overview/index.cfm?ProductID=40>.
+
+ This driver is also available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ The module will be called cs461x.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
Aureal Vortex and Trident 4DWave gameports
CONFIG_INPUT_PCIGAME
Say Y here if you have a Trident 4DWave DX/NX or Aureal Vortex 1/2
card. For more information on how to use the driver please read
- Documentation/joystick.txt
+ <file:Documentation/joystick.txt>.
+
+ This driver is also available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ The module will be called pcigame.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
+
+SoundBlaster Live! gameports
+CONFIG_INPUT_EMU10K1
+ Say Y here if you have a SoundBlaster Live! card and want to use
+ its gameport. For more information on how to use the driver
+ please read <file:Documentation/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called pcigame.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ The module will be called emu10k1-gp.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
Classic PC analog joysticks and gamepads
CONFIG_INPUT_ANALOG
Say Y here if you have a controller that connects to the PC
- gameport. This supports many different types, including joysticks
+ gameport. This supports many different types, including joysticks
with throttle control, with rudders, or with extensions like
additional hats and buttons compatible with CH Flightstick Pro,
ThrustMaster FCS, 6 and 8 button gamepads, or Saitek Cyborg
- joysticks. For more information on how to use the driver please read
- Documentation/joystick.txt
+ joysticks. For more information on how to use the driver please
+ read <file:Documentation/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called analog.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ The module will be called analog.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
-Assasin 3D and MadCatz Panther devices
+Assassin 3D and MadCatz Panther devices
CONFIG_INPUT_A3D
Say Y here if you have an FPGaming or MadCatz controller using the
- A3D protocol over the PC gameport. For more information on how to
- use the driver please read Documentation/joystick.txt
+ A3D protocol over the PC gameport. For more information on how to
+ use the driver please read <file:Documentation/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called a3d.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ The module will be called a3d.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
Logitech ADI digital joysticks and gamepads
CONFIG_INPUT_ADI
Say Y here if you have a Logitech controller using the ADI
protocol over the PC gameport. For more information on how to use
- the driver please read Documentation/joystick.txt
+ the driver please read <file:Documentation/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called adi.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ The module will be called adi.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
Creative Labs Blaster Cobra gamepad
CONFIG_INPUT_COBRA
Say Y here if you have a Creative Labs Blaster Cobra gamepad.
For more information on how to use the driver please read
- Documentation/joystick.txt
+ <file:Documentation/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called cobra.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ The module will be called cobra.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
Genius Flight2000 Digital joysticks and gamepads
CONFIG_INPUT_GF2K
- Say Y here if you have a Genius Flight2000 or MaxFighter
- digitally communicating joystick or gamepad. For more information
- on how to use the driver please read Documentation/joystick.txt
+ Say Y here if you have a Genius Flight2000 or MaxFighter digitally
+ communicating joystick or gamepad. For more information on how to
+ use the driver please read <file:Documentation/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called gf2k.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ The module will be called gf2k.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
Gravis GrIP joysticks and gamepads
CONFIG_INPUT_GRIP
Say Y here if you have a Gravis controller using the GrIP protocol
- over the PC gameport. For more information on how to use the driver
- please read Documentation/joystick.txt
+ over the PC gameport. For more information on how to use the driver
+ please read <file:Documentation/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called grip.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ The module will be called grip.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
InterAct digital joysticks and gamepads
CONFIG_INPUT_INTERACT
Say Y hereif you have an InterAct gameport or joystick
- communicating digitally over the gameport. For more information on
- how to use the driver please read Documentation/joystick.txt
+ communicating digitally over the gameport. For more information on
+ how to use the driver please read <file:Documentation/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called interact.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ The module will be called interact.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
ThrustMaster DirectConnect joysticks and gamepads
CONFIG_INPUT_TMDC
Say Y here if you have a ThrustMaster controller using the
- DirectConnect (BSP) protocol over the PC gameport. For more
+ DirectConnect (BSP) protocol over the PC gameport. For more
information on how to use the driver please read
- Documentation/joystick.txt
+ <file:Documentation/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called tmdc.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ The module will be called tmdc.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
Microsoft SideWinder digital joysticks and gamepads
CONFIG_INPUT_SIDEWINDER
Say Y here if you have a Microsoft controller using the Digital
- Overdrive protocol over PC gameport. For more information on how to
- use the driver please read Documentation/joystick.txt
+ Overdrive protocol over PC gameport. For more information on how to
+ use the driver please read <file:Documentation/joystick.txt>.
+
+ This driver is also available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ The module will be called sidewinder.o. If you want to compile it
+ as a module, say M here and read <file:Documentation/modules.txt>.
+
+Serial port device support
+CONFIG_INPUT_SERIO
+ Say Y here and to the Serial port input line discipline option if
+ you plan to use a joystick that communicates over the serial (COM)
+ port. For more information on how to use the driver please read
+ <file:Documentation/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called sidewinder.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ The module will be called sidewinder.o. If you want to compile it
+ as a module, say M here and read <file:Documentation/modules.txt>.
Serial port input line discipline
CONFIG_INPUT_SERPORT
- Say Y hereif you plan to use a joystick that communicates over the
- serial (COM) port. For more information on how to use the driver
- please read Documentation/joystick.txt
+ Say Y here if you plan to use a joystick that communicates over the
+ serial (COM) port. For more information on how to use the driver
+ please read <file:Documentation/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called serport.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ The module will be called serport.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
Logitech WingMan Warrior joystick
CONFIG_INPUT_WARRIOR
- Say Y here if you have a Logitech WingMan Warrior joystick
- connected to your computer's serial port. For more information on
- how to use the driver please read Documentation/joystick.txt
+ Say Y here if you have a Logitech WingMan Warrior joystick connected
+ to your computer's serial port. For more information on how to use
+ the driver please read <file:Documentation/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called warrior.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ The module will be called warrior.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
LogiCad3d Magellan/SpaceMouse 6dof controller
CONFIG_INPUT_MAGELLAN
Say Y here if you have a Magellan or Space Mouse 6DOF controller
connected to your computer's serial port. For more information on
- how to use the driver please read Documentation/joystick.txt
+ how to use the driver please read <file:Documentation/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called magellan.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ The module will be called magellan.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
SpaceTec SpaceOrb/Avenger 6dof controller
CONFIG_INPUT_SPACEORB
Say Y here if you have a SpaceOrb 360 or SpaceBall Avenger 6DOF
controller connected to your computer's serial port. For more
information on how to use the driver please read
- Documentation/joystick.txt
+ <file:Documentation/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called spaceorb.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
-
+ The module will be called spaceorb.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
+
SpaceTec SpaceBall 4000 FLX 6dof controller
CONFIG_INPUT_SPACEBALL
Say Y here if you have a SpaceTec SpaceBall 4000 FLX controller
- connected to your computer's serial port. For more information on
- how to use the driver please read Documentation/joystick.txt
+ connected to your computer's serial port. For more information on
+ how to use the driver please read <file:Documentation/joystick.txt>.
+
+ This driver is also available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ The module will be called spaceball.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
+
+Gravis Stinger gamepad
+CONFIG_INPUT_STINGER
+ Say Y here if you have a Gravis Stinger connected to one of your
+ serial ports. For more information on how to use the driver please
+ read <file:Documentation/joystick.txt>.
+
+ This driver is also available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ The module will be called stinger.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
I-Force joysticks/wheels
CONFIG_INPUT_IFORCE_232
Say Y here if you have an I-Force joystick or steering wheel
- connected to your serial (COM) port. For more information on
- how to use the driver please read Documentation/joystick.txt
+ connected to your serial (COM) port. For more information on how
+ to use the driver please read <file:Documentation/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called iforce.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ The module will be called iforce.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
I-Force joysticks/wheels
CONFIG_INPUT_IFORCE_USB
Say Y here if you have an I-Force joystick or steering wheel
- connected to your USB port. For more information on how to use the
- driver please read Documentation/joystick.txt
+ connected to your USB port. For more information on how to use the
+ driver please read <file:Documentation/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called iforce.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
-
+ The module will be called iforce.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
+
Multisystem, Sega Genesis, Saturn joysticks and gamepads
CONFIG_INPUT_DB9
Say Y here if you have a Sega Master System gamepad, Sega Genesis
gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga,
- Commodore, Amstrad CPC joystick connected to your parallel port.
- For more information on how to use the driver please read
- Documentation/joystick.txt and Documentation/joystick-parport.txt.
+ Commodore, Amstrad CPC joystick connected to your parallel port.
+ For more information on how to use the driver please read
+ <file:Documentation/joystick.txt> and
+ <file:Documentation/joystick-parport.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called db9.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ The module will be called db9.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
Multisystem, NES, SNES, N64, PSX joysticks and gamepads
CONFIG_INPUT_GAMECON
@@ -15420,47 +17755,48 @@
Sony PlayStation gamepad or a Multisystem -- Atari, Amiga,
Commodore, Amstrad CPC joystick connected to your parallel port.
For more information on how to use the driver please read
- Documentation/joystick.txt and Documentation/joystick-parport.txt
+ <file:Documentation/joystick.txt> and
+ <file:Documentation/joystick-parport.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called gamecon.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ The module will be called gamecon.o. If you want to compile it as a
+ module, say M here and read <file:Documentation/modules.txt>.
Multisystem joysticks via TurboGraFX device
CONFIG_INPUT_TURBOGRAFX
- Say Y here if you have the TurboGraFX interface by Steffen
- Schwenke, and want to use it with Multiststem -- Atari, Amiga,
- Commodore, Amstrad CPC joystick. For more information on how to use
- the driver please read Documentation/joystick.txt and
- Documentation/joystick-parport.txt
+ Say Y here if you have the TurboGraFX interface by Steffen Schwenke,
+ and want to use it with Multisystem -- Atari, Amiga, Commodore,
+ Amstrad CPC joystick. For more information on how to use the driver
+ please read <file:Documentation/joystick.txt> and
+ <file:Documentation/joystick-parport.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called turbografx.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ The module will be called turbografx.o. If you want to compile it
+ as a module, say M here and read <file:Documentation/modules.txt>.
Amiga joysticks
CONFIG_INPUT_AMIJOY
Say Y here if you have an Amiga with a digital joystick connected
- to it. For more information on how to use the driver please read
- Documentation/joystick.txt
+ to it. For more information on how to use the driver please read
+ <file:Documentation/joystick.txt>.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module will be called joy-amiga.o. If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ The module will be called joy-amiga.o. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
-Atomwide Serial Support
+Atomwide serial port support
CONFIG_ATOMWIDE_SERIAL
If you have an Atomwide Serial card for an Acorn system, say Y to
- this option. The driver can handle 1, 2, or 3 port cards.
- If unsure, say N
+ this option. The driver can handle 1, 2, or 3 port cards.
+ If unsure, say N.
-The Serial Port Dual Serial Port
+Dual serial port support
CONFIG_DUALSP_SERIAL
If you have the Serial Port's dual serial card for an Acorn system,
- say Y to this option. If unsure, say N
+ say Y to this option. If unsure, say N.
NetWinder Button
CONFIG_NWBUTTON
@@ -15481,7 +17817,8 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. The module will be called nwbutton.o.
+ <file:Documentation/modules.txt>. The module will be called
+ nwbutton.o.
Most people will answer Y to this question and "Reboot Using Button"
below to be able to initiate a system shutdown from the button.
@@ -15499,37 +17836,37 @@
Sound card support
CONFIG_SOUND
If you have a sound card in your computer, i.e. if it can say more
- than an occasional beep, say Y. Be sure to have all the information
+ than an occasional beep, say Y. Be sure to have all the information
about your sound card and its configuration down (I/O port,
- interrupt and DMA channel), because you will be asked for it.
+ interrupt and DMA channel), because you will be asked for it.
You want to read the Sound-HOWTO, available from
- http://www.linuxdoc.org/docs.html#howto . General information
- about the modular sound system is contained in the files
- Documentation/sound/Introduction. The file
- Documentation/sound/README.OSS contains some slightly outdated but
- still useful information as well.
+ <http://www.linuxdoc.org/docs.html#howto>. General information about
+ the modular sound system is contained in the files
+ <file:Documentation/sound/Introduction>. The file
+ <file:Documentation/sound/README.OSS> contains some slightly
+ outdated but still useful information as well.
If you have a PnP sound card and you want to configure it at boot
time using the ISA PnP tools (read
- http://www.roestock.demon.co.uk/isapnptools/ ), then you need to
+ <http://www.roestock.demon.co.uk/isapnptools/>), then you need to
compile the sound card support as a module ( = code which can be
inserted in and removed from the running kernel whenever you want)
- and load that module after the PnP configuration is finished. To do
- this, say M here and read Documentation/modules.txt as well as
- Documentation/sound/README.modules; the module will be called
- soundcore.o.
+ and load that module after the PnP configuration is finished. To do
+ this, say M here and read <file:Documentation/modules.txt> as well
+ as <file:Documentation/sound/README.modules>; the module will be
+ called soundcore.o.
I'm told that even without a sound card, you can make your computer
say more than an occasional beep, by programming the PC speaker.
Kernel patches and supporting utilities to do that are in the pcsp
- package, available at ftp://ftp.infradead.org/pub/pcsp/ .
+ package, available at <ftp://ftp.infradead.org/pub/pcsp/>.
OSS sound modules
CONFIG_SOUND_OSS
- OSS is the Open Sound System suite of sound card drivers. They make
- sound programming easier since they provide a common API. Say Y or M
- here (the module will be called sound.o) if you haven't found a
+ OSS is the Open Sound System suite of sound card drivers. They make
+ sound programming easier since they provide a common API. Say Y or
+ M here (the module will be called sound.o) if you haven't found a
driver for your sound card above, then pick your driver from the
list below.
@@ -15546,7 +17883,7 @@
then you can get the persistent DMA buffer functionality by passing
the command-line argument "dmabuf=1" to the sound.o module.
- Say Y unless you have 16MB or less RAM or a PCI sound card.
+ Say Y unless you have 16MB or more RAM or a PCI sound card.
Support for Aztech Sound Galaxy (non-PnP) cards
CONFIG_SOUND_SGALAXY
@@ -15558,9 +17895,9 @@
"sgalaxy=<io>,<irq>,<dma>,<dma2>,<sgbase>" to the kernel command
line.
-Support for AD1816(A) based cards (EXPERIMENTAL)
+Support for AD1816(A) based cards
CONFIG_SOUND_AD1816
- Say M here if you have a sound card based on the Analog Devices
+ Say M here if you have a sound card based on the Analog Devices
AD1816(A) chip.
If you compile the driver into the kernel, you have to add
@@ -15569,8 +17906,8 @@
Yamaha OPL3-SA1 audio controller
CONFIG_SOUND_OPL3SA1
Say Y or M if you have a Yamaha OPL3-SA1 sound chip, which is
- usually built into motherboards. Read Documentation/sound/OPL3-SA
- for details.
+ usually built into motherboards. Read
+ <file:Documentation/sound/OPL3-SA> for details.
If you compile the driver into the kernel, you have to add
"opl3sa=<io>,<irq>,<dma>,<dma2>,<mpuio>,<mpuirq>" to the kernel
@@ -15581,7 +17918,7 @@
Answer Y only if you have a Pro Audio Spectrum 16, ProAudio Studio
16 or Logitech SoundMan 16 sound card. Answer N if you have some
other card made by Media Vision or Logitech since those are not
- PAS16 compatible. Please read Documentation/sound/PAS16.
+ PAS16 compatible. Please read <file:Documentation/sound/PAS16>.
It is not necessary to add Sound Blaster support separately; it
is included in PAS support.
@@ -15589,6 +17926,11 @@
"pas2=<io>,<irq>,<dma>,<dma2>,<sbio>,<sbirq>,<sbdma>,<sbdma2>
to the kernel command line.
+Enable PAS16 joystick port
+CONFIG_PAS_JOYSTICK
+ Say Y here to enable the Pro Audio Spectrum 16's auxiliary joystick
+ port.
+
100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support
CONFIG_SOUND_SB
Answer Y if you have an original Sound Blaster card made by Creative
@@ -15596,48 +17938,43 @@
SM Games). For an unknown card you may answer Y if the card claims
to be Sound Blaster-compatible.
- Please read the file Documentation/sound/Soundblaster.
+ Please read the file <file:Documentation/sound/Soundblaster>.
You should also say Y here for cards based on the Avance Logic
- ALS-007 and ALS-1X0 chips (read Documentation/sound/ALS) and for cards
- based on ESS chips (read Documentation/sound/ESS1868 and
- Documentation/sound/ESS). If you have an SB AWE 32 or SB AWE 64, say
- Y here and also to "AWE32 synth" below and read
- Documentation/sound/INSTALL.awe. If you have an IBM Mwave card, say
- Y here and read Documentation/sound/mwave.
+ ALS-007 and ALS-1X0 chips (read <file:Documentation/sound/ALS>) and
+ for cards based on ESS chips (read
+ <file:Documentation/sound/ESS1868> and
+ <file:Documentation/sound/ESS>). If you have an SB AWE 32 or SB AWE
+ 64, say Y here and also to "AWE32 synth" below and read
+ <file:Documentation/sound/INSTALL.awe>. If you have an IBM Mwave
+ card, say Y here and read <file:Documentation/sound/mwave>.
If you compile the driver into the kernel and don't want to use
isapnp, you have to add "sb=<io>,<irq>,<dma>,<dma2>" to the kernel
command line.
-
+
You can say M here to compile this driver as a module; the module is
called sb.o.
-#Loopback MIDI device support
-#CONFIG_SOUND_VMIDI
-###
-### somebody please fill this in.
-###
-#
Gravis Ultrasound support
CONFIG_SOUND_GUS
- Say Y here for any type of Gravis Ultrasound card, including
- the GUS or GUS MAX. See also Documentation/sound/ultrasound for
- more information on configuring this card with modules.
+ Say Y here for any type of Gravis Ultrasound card, including the GUS
+ or GUS MAX. See also <file:Documentation/sound/ultrasound> for more
+ information on configuring this card with modules.
If you compile the driver into the kernel, you have to add
"gus=<io>,<irq>,<dma>,<dma2>" to the kernel command line.
MPU-401 support (NOT for SB16)
CONFIG_SOUND_MPU401
- Be careful with this question. The MPU401 interface is supported by
- all sound cards. However, some natively supported cards have their
- own driver for MPU401. Enabling this MPU401 option with these cards
- will cause a conflict. Also, enabling MPU401 on a system that
- doesn't really have a MPU401 could cause some trouble. If your card
+ Be careful with this question. The MPU401 interface is supported by
+ all sound cards. However, some natively supported cards have their
+ own driver for MPU401. Enabling this MPU401 option with these cards
+ will cause a conflict. Also, enabling MPU401 on a system that
+ doesn't really have a MPU401 could cause some trouble. If your card
was in the list of supported cards, look at the card specific
- instructions in the drivers/sound/Readme.cards file. It's safe to
- answer Y if you have a true MPU401 MIDI interface card.
+ instructions in the <file:Documentation/sound/README.OSS> file. It
+ is safe to answer Y if you have a true MPU401 MIDI interface card.
If you compile the driver into the kernel, you have to add
"mpu401=<io>,<irq>" to the kernel command line.
@@ -15657,7 +17994,7 @@
ADSP-16 or some other card based on the PSS chipset (AD1848 codec +
ADSP-2115 DSP chip + Echo ESC614 ASIC CHIP). For more information on
how to compile it into the kernel or as a module see the file
- Documentation/sound/PSS.
+ <file:Documentation/sound/PSS>.
If you compile the driver into the kernel, you have to add
"pss=<io>,<mssio>,<mssirq>,<mssdma>,<mpuio>,<mpuirq>" to the kernel
@@ -15672,7 +18009,7 @@
If you said M to "PSS support" above, you may enable or disable this
PSS mixer with the module parameter pss_mixer. For more information
- see the file Documentation/sound/PSS.
+ see the file <file:Documentation/sound/PSS>.
Have DSPxxx.LD firmware file
CONFIG_PSS_HAVE_BOOT
@@ -15687,10 +18024,10 @@
Microsoft Sound System support
CONFIG_SOUND_MSS
- Again think carefully before answering Y to this question. It's safe
- to answer Y if you have the original Windows Sound System card made
- by Microsoft or Aztech SG 16 Pro (or NX16 Pro). Also you may say Y
- in case your card is NOT among these:
+ Again think carefully before answering Y to this question. It's
+ safe to answer Y if you have the original Windows Sound System card
+ made by Microsoft or Aztech SG 16 Pro (or NX16 Pro). Also you may
+ say Y in case your card is NOT among these:
ATI Stereo F/X, AdLib, Audio Excell DSP16, Cardinal DSP16,
Ensoniq SoundScape (and compatibles made by Reveal and Spea),
@@ -15707,9 +18044,9 @@
synthesizers (OPL2, OPL3 and OPL4), 6850 UART MIDI Interface.
For cards having native support in VoxWare, consult the card
- specific instructions in drivers/sound/Readme.cards. Some drivers
- have their own MSS support and saying Y to this option will cause a
- conflict.
+ specific instructions in <file:Documentation/sound/README.OSS>.
+ Some drivers have their own MSS support and saying Y to this option
+ will cause a conflict.
If you compile the driver into the kernel, you have to add
"ad1848=<io>,<irq>,<dma>,<dma2>[,<type>]" to the kernel command
@@ -15717,11 +18054,12 @@
SGI Visual Workstation on-board audio
CONFIG_SOUND_VWSND
- Say Y or M if you have an SGI Visual Workstation and you want to
- be able to use its on-board audio. Read Documentation/sound/vwsnd
- for more info on this driver's capabilities.
+ Say Y or M if you have an SGI Visual Workstation and you want to be
+ able to use its on-board audio. Read
+ <file:Documentation/sound/vwsnd> for more info on this driver's
+ capabilities.
-Ensoniq Soundscape support
+Ensoniq SoundScape support
CONFIG_SOUND_SSCAPE
Answer Y if you have a sound card based on the Ensoniq SoundScape
chipset. Such cards are being manufactured at least by Ensoniq, Spea
@@ -15751,27 +18089,28 @@
Support for OPTi MAD16 and/or Mozart based cards
CONFIG_SOUND_MAD16
Answer Y if your card has a Mozart (OAK OTI-601) or MAD16 (OPTi
- 82C928 or 82C929 or 82C931) audio interface chip. These chips are
+ 82C928 or 82C929 or 82C931) audio interface chip. These chips are
quite common so it's possible that many no-name cards have one of
them. In addition the MAD16 chip is used in some cards made by known
manufacturers such as Turtle Beach (Tropez), Reveal (some models)
and Diamond (latest ones). Note however that the Tropez sound cards
have their own driver; if you have one of those, say N here and Y or
- M to "Full support for Turtle Beach WaveFront", below.
+ M to "Full support for Turtle Beach WaveFront", below.
If you compile the driver into the kernel, you have to add
"mad16=<io>,<irq>,<dma>,<dma2>,<mpuio>,<mpuirq>" to the
kernel command line.
- See also Documentation/sound/Opti and Documentation/sound/MAD16 for
- more information on setting these cards up as modules.
+ See also <file:Documentation/sound/Opti> and
+ <file:Documentation/sound/MAD16> for more information on setting
+ these cards up as modules.
-Full support for Turtle Beach WaveFront synth/sound cards
+Full support for Turtle Beach WaveFront (Tropez Plus, Tropez, Maui) synth/sound cards
CONFIG_SOUND_WAVEFRONT
Answer Y or M if you have a Tropez Plus, Tropez or Maui sound card
- and read the files Documentation/sound/Wavefront and
- Documentation/sound/Tropez+.
-
+ and read the files <file:Documentation/sound/Wavefront> and
+ <file:Documentation/sound/Tropez+>.
+
Support MIDI in older MAD16 based cards (requires SB)
CONFIG_MAD16_OLDCARD
Answer Y (or M) if you have an older card based on the C928 or
@@ -15787,15 +18126,15 @@
"cs4232=<io>,<irq>,<dma>,<dma2>,<mpuio>,<mpuirq>" to the kernel
command line.
- See Documentation/sound/CS4232 for more information on configuring
- this card.
+ See <file:Documentation/sound/CS4232> for more information on
+ configuring this card.
Support for Yamaha OPL3-SA2 and SA3 based PnP cards
CONFIG_SOUND_OPL3SA2
- Say Y or M if you have a card based on one of these Yamaha
- sound chipsets or the "SAx", which is actually a SA3. Read
- Documentation/sound/OPL3-SA2 for more information on configuring
- these cards.
+ Say Y or M if you have a card based on one of these Yamaha sound
+ chipsets or the "SAx", which is actually a SA3. Read
+ <file:Documentation/sound/OPL3-SA2> for more information on
+ configuring these cards.
If you compile the driver into the kernel and do not also
configure in the optional ISA PnP support, you will have to add
@@ -15824,52 +18163,118 @@
Support for Turtle Beach MultiSound Classic, Tahiti, Monterey
CONFIG_SOUND_MSNDCLAS
Say M here if you have a Turtle Beach MultiSound Classic, Tahiti or
- Monterey (not for the Pinnacle or Fiji).
+ Monterey (not for the Pinnacle or Fiji).
- See Documentation/sound/MultiSound for important information about
- this driver.
+ See <file:Documentation/sound/MultiSound> for important information
+ about this driver. Note that it has been discontinued, but the
+ Voyetra Turtle Beach knowledge base entry for it is still available
+ at <http://www.voyetra-turtle-beach.com/site/kb_ftp/790.asp>.
+
+MSND Classic I/O
+CONFIG_MSNDCLAS_IO
+ I/O port address for the MultiSound Classic and related cards.
+
+MSND Classic IRQ
+CONFIG_MSNDCLAS_IRQ
+ Interrupt Request line for the MultiSound Classic and related cards.
+
+MSND Classic memory address
+CONFIG_MSNDCLAS_MEM
+ Memory-mapped I/O base address for the MultiSound Classic and
+ related cards.
Full pathname of MSNDINIT.BIN firmware file
CONFIG_MSNDCLAS_INIT_FILE
The MultiSound cards have two firmware files which are required for
operation, and are not currently included. These files can be
- obtained from Turtle Beach. See Documentation/sound/MultiSound for
- information on how to obtain this.
+ obtained from Turtle Beach. See
+ <file:Documentation/sound/MultiSound> for information on how to
+ obtain this.
Full pathname of MSNDPERM.BIN firmware file
CONFIG_MSNDCLAS_PERM_FILE
The MultiSound cards have two firmware files which are required for
operation, and are not currently included. These files can be
- obtained from Turtle Beach. See Documentation/sound/MultiSound for
- information on how to obtain this.
+ obtained from Turtle Beach. See
+ <file:Documentation/sound/MultiSound> for information on how to
+ obtain this.
Support for Turtle Beach MultiSound Pinnacle, Fiji
CONFIG_SOUND_MSNDPIN
Say M here if you have a Turtle Beach MultiSound Pinnacle or Fiji.
- See Documentation/sound/MultiSound for important information about
- this driver.
+ See <file:Documentation/sound/MultiSound> for important information
+ about this driver. Note that it has been discontinued, but the
+ Voyetra Turtle Beach knowledge base entry for it is still available
+ at <http://www.voyetra-turtle-beach.com/site/kb_ftp/600.asp>.
+
+MSND Pinnacle IDE I/O 0
+CONFIG_MSNDPIN_IDE_IO0
+ CD-ROM drive 0 memory-mapped I/O base address for the MultiSound
+ Pinnacle and Fiji sound cards.
+
+MSND Pinnacle IDE I/O 1
+CONFIG_MSNDPIN_IDE_IO1
+ CD-ROM drive 1 memory-mapped I/O base address for the MultiSound
+ Pinnacle and Fiji sound cards.
+
+MSND Pinnacle IDE IRQ
+CONFIG_MSNDPIN_IDE_IRQ
+ Interrupt request number for the IDE CD-ROM interface on the
+ MultiSound Pinnacle and Fiji sound cards.
+
+MSND Pinnacle I/O
+CONFIG_MSNDPIN_IO
+ Memory-mapped I/O base address for the primary synthesizer on
+ MultiSound Pinnacle and Fiji sound cards.
+
+MSND Pinnacle MPU I/O
+CONFIG_MSNDPIN_MPU_IO
+ Memory-mapped I/O base address for the Kurzweil daughterboard
+ synthesizer on MultiSound Pinnacle and Fiji sound cards.
+
+MSND Pinnacle MPU IRQ
+CONFIG_MSNDPIN_MPU_IRQ
+ Iinterrupt request number for the Kurzweil daughterboard
+ synthesizer on MultiSound Pinnacle and Fiji sound cards.
+
+MSND Pinnacle IRQ
+CONFIG_MSNDPIN_IRQ
+ Interrupt request line for the primary synthesizer on MultiSound
+ Pinnacle and Fiji sound cards.
+
+MSND Pinnacle joystick I/O
+CONFIG_MSNDPIN_JOYSTICK_IO
+ Memory-mapped I/O base address for the joystick port on MultiSound
+ Pinnacle and Fiji sound cards.
+
+MSND Pinnacle memory
+CONFIG_MSNDPIN_MEM
+ Memory-mapped I/O base address for the primary synthesizer on
+ MultiSound Pinnacle and Fiji sound cards.
Full pathname of PNDSPINI.BIN firmware file
CONFIG_MSNDPIN_INIT_FILE
- The MultiSound cards have two firmware files which are required for
- operation, and are not currently included. These files can be
- obtained from Turtle Beach. See Documentation/sound/MultiSound for
- information on how to obtain this.
+ The MultiSound cards have two firmware files which are required
+ for operation, and are not currently included. These files can be
+ obtained from Turtle Beach. See
+ <file:Documentation/sound/MultiSound> for information on how to
+ obtain this.
Full pathname of PNDSPERM.BIN firmware file
CONFIG_MSNDPIN_PERM_FILE
The MultiSound cards have two firmware files which are required for
operation, and are not currently included. These files can be
- obtained from Turtle Beach. See Documentation/sound/MultiSound for
- information on how to obtain this.
+ obtained from Turtle Beach. See
+ <file:Documentation/sound/MultiSound> for information on how to
+ obtain this.
-MSND Pinnacle have S/PDIF I/O
+MSND Pinnacle has S/PDIF I/O
CONFIG_MSNDPIN_DIGITAL
If you have the S/PDIF daughter board for the Pinnacle or Fiji,
answer Y here; otherwise, say N. If you have this, you will be able
to play and record from the S/PDIF port (digital signal). See
- Documentation/sound/MultiSound for information on how to make use of
- this capability.
+ <file:Documentation/sound/MultiSound> for information on how to make
+ use of this capability.
MSND Pinnacle non-PnP Mode
CONFIG_MSNDPIN_NONPNP
@@ -15896,15 +18301,14 @@
and Pinnacle). Larger values reduce the chance of data overruns at
the expense of overall latency. If unsure, use the default.
-FM synthesizer (YM3812/OPL-3) support
+Yamaha FM synthesizer (YM3812/OPL-3) support
CONFIG_SOUND_YM3812
Answer Y if your card has a FM chip made by Yamaha (OPL2/OPL3/OPL4).
Answering Y is usually a safe and recommended choice, however some
cards may have software (TSR) FM emulation. Enabling FM support with
these cards may cause trouble (I don't currently know of any such
- cards, however).
- Please read the file Documentation/sound/OPL3 if your card has an
- OPL3 chip.
+ cards, however). Please read the file
+ <file:Documentation/sound/OPL3> if your card has an OPL3 chip.
If you compile the driver into the kernel, you have to add
"opl3=<io>" to the kernel command line.
@@ -15914,27 +18318,27 @@
ACI mixer (miroSOUND PCM1-pro/PCM12/PCM20 radio)
CONFIG_SOUND_ACI_MIXER
ACI (Audio Command Interface) is a protocol used to communicate with
- the microcontroller on some sound cards produced by miro and Cardinal
- Technologies. The main function of the ACI is to control the mixer
- and to get a product identification.
+ the microcontroller on some sound cards produced by miro and
+ Cardinal Technologies. The main function of the ACI is to control
+ the mixer and to get a product identification.
- This Voxware ACI driver currently supports the ACI functions on the
+ This VoxWare ACI driver currently supports the ACI functions on the
miroSOUND PCM1-pro, PCM12 and PCM20 radio. On the PCM20 radio, ACI
also controls the radio tuner. This is supported in the video4linux
- miropcm20 driver (say M or Y here and go back to "Multimedia devices"
- -> "Radio Adapters").
+ miropcm20 driver (say M or Y here and go back to "Multimedia
+ devices" -> "Radio Adapters").
This driver is also available as a module and will be called aci.o.
SB32/AWE support
CONFIG_SOUND_AWE32_SYNTH
Say Y here if you have a Sound Blaster SB32, AWE32-PnP, SB AWE64 or
- similar sound card. See Documentation/sound/README.awe,
- Documentation/sound/AWE32 and the Soundblaster-AWE mini-HOWTO,
- available from http://www.linuxdoc.org/docs.html#howto for more
- info.
+ similar sound card. See <file:Documentation/sound/README.awe>,
+ <file:Documentation/sound/AWE32> and the Soundblaster-AWE
+ mini-HOWTO, available from <http://www.linuxdoc.org/docs.html#howto>
+ for more info.
-Gallant's Audio Excel DSP 16 support (SC-6000 and SC-6600)
+Gallant Audio Cards (SC-6000 and SC-6600 based)
CONFIG_SOUND_AEDSP16
Answer Y if you have a Gallant's Audio Excel DSP 16 card. This
driver supports Audio Excel DSP 16 but not the III nor PnP versions
@@ -15948,10 +18352,10 @@
accordingly. You should say Y to one and only one of these two
questions.
- Read the drivers/sound/lowlevel/README.aedsp16 file and the head of
- drivers/sound/lowlevel/aedsp16.c as well as
- Documentation/sound/AudioExcelDSP16 to get more information about
- this driver and its configuration.
+ Read the <file:Documentation/sound/README.OSS> file and the head of
+ <file:drivers/sound/lowlevel/aedsp16.c> as well as
+ <file:Documentation/sound/AudioExcelDSP16> to get more information
+ about this driver and its configuration.
Audio Excel DSP 16 (SBPro emulation)
CONFIG_AEDSP16_SBPRO
@@ -15981,17 +18385,22 @@
Say Y here in order to use the joystick interface of the Audio Excel
DSP 16 card.
-SC-6600 CDROM Interface
-CONFIG_SC6600_CDROM
- This is used to activate the CDROM interface of the Audio Excel
+SC-6600 CD-ROM Interface
+CONFIG_SC6600_CDROM (4=None, 3=IDE, 1=Panasonic, 0=Sony)
+ This is used to activate the CD-ROM interface of the Audio Excel
DSP 16 card. Enter: 0 for Sony, 1 for Panasonic, 2 for IDE, 4 for no
- CDROM present.
+ CD-ROM present.
+
+SC-6600 CD-ROM Interface I/O Address
+CONFIG_SC6600_CDROMBASE
+ Base I/O port address for the CD-ROM interface of the Audio Excel
+ DSP 16 card.
Audio Excel DSP 16 (MPU401 emulation)
CONFIG_AEDSP16_MPU401
Answer Y if you want your audio card to emulate the MPU-401 midi
interface. You should then also say Y to "MPU-401 support".
-
+
Note that the I/O base for MPU-401 support of aedsp16 is the same
you have selected for "MPU-401 support". If you are using this
driver as a module you have to specify the MPU I/O base address with
@@ -16000,46 +18409,70 @@
C-Media PCI (CMI8338/8378)
CONFIG_SOUND_CMPCI
Say Y or M if you have a PCI sound card using the CMI8338
- or the CMI8378 chip.set.
+ or the CMI8378 chipset. Data on these chips are available at
+ <http://www.cmedia.com.tw/>.
+
+Support CMI8738 based audio cards
+CONFIG_SOUND_CMPCI_CM8738
+ Say Y or M if you have a PCI sound card using the CMI8338
+ or the CMI8378 chipset. Data on this chip is available at
+ <http://www.cmedia.com.tw/doc8738.htm>.
+
+Enable joystick
+CONFIG_SOUND_CMPCI_JOYSTICK
+ Say here in order to enable the joystick port on a sound crd using
+ the CMI8338 or the CMI8738 chipset. Data on these chips are
+ available at <http://www.cmedia.com.tw/>.
+
+Number of speakers (2, 4, 5, 6)
+CONFIG_SOUND_CMPCI_SPEAKERS
+ Specify the number of speaker channels you want the card to drive,
+ as an integer.
+
+Enable S/PDIF loop for CMI8738
+CONFIG_SOUND_CMPCI_SPDIFLOOP
+ Enable loopback from SPDIF in to SPDIF out. For discussion, see
+ "The 8738 Audio SPDIF In/Out Technical Data" on the technical
+ support page at <http://www.cmedia.com.tw/>.
-Creative EMU10K1 based PCI sound cards
+Creative SBLive! (EMU10K1) based PCI sound cards
CONFIG_SOUND_EMU10K1
Say Y or M if you have a PCI sound card using the EMU10K1 chipset,
- such as the various Creative SBLive!, SB PCI512 or Emu-APS.
+ such as the Creative SBLive!, SB PCI512 or Emu-APS.
For more information on this driver and the degree of support for the
different card models please check <http://opensource.creative.com>.
It is now possible to load dsp microcode patches into the EMU10K1
- chip. These patches are used to implement real time sound processing
- effects which include for example: signal routing, bass/treble
- control, AC3 passthrough, ...
+ chip. These patches are used to implement real time sound
+ processing effects which include for example: signal routing,
+ bass/treble control, AC3 passthrough, ...
Userspace tools to create new patches and load/unload them can be
found at <http://opensource.creative.com/dist.html>.
-
+
Creative EMU10K1 MIDI
CONFIG_MIDI_EMU10K1
- Say Y if you want to be able to use the OSS /dev/sequencer interface.
- This code is still experimental.
+ Say Y if you want to be able to use the OSS /dev/sequencer
+ interface. This code is still experimental.
Crystal SoundFusion (CS4280/461x)
CONFIG_SOUND_FUSION
- This module drives the Crystal SoundFusion devices (CS4280/46xx series)
- when wired as native sound drivers with AC97 codecs. If this driver
- does not work try the CS4232 driver.
+ This module drives the Crystal SoundFusion devices (CS4280/46xx
+ series) when wired as native sound drivers with AC97 codecs. If
+ this driver does not work try the CS4232 driver.
-Ensoniq ES1370 based PCI sound cards
+Ensoniq AudioPCI (ES1370) based PCI sound cards
CONFIG_SOUND_ES1370
Say Y or M if you have a PCI sound card utilizing the Ensoniq
ES1370 chipset, such as Ensoniq's AudioPCI (non-97). To find
out if your sound card uses an ES1370 without removing your
- computer's cover, use lspci -n and look for the PCI ID
+ computer's cover, use lspci -n and look for the PCI ID
1274:5000. Since Ensoniq was bought by Creative Labs,
Sound Blaster 64/PCI models are either ES1370 or ES1371 based.
This driver differs slightly from OSS/Free, so PLEASE READ
- Documentation/sound/es1370.
+ <file:Documentation/sound/es1370>.
-Ensoniq ES1371 based PCI sound cards
+Ensoniq AudioPCI 97 (ES1371) based sound cards
CONFIG_SOUND_ES1371
Say Y or M if you have a PCI sound card utilizing the Ensoniq
ES1371 chipset, such as Ensoniq's AudioPCI97. To find out if
@@ -16047,25 +18480,26 @@
cover, use lspci -n and look for the PCI ID 1274:1371. Since
Ensoniq was bought by Creative Labs, Sound Blaster 64/PCI
models are either ES1370 or ES1371 based. This driver differs
- slightly from OSS/Free, so PLEASE READ Documentation/sound/es1371.
+ slightly from OSS/Free, so PLEASE READ
+ <file:Documentation/sound/es1371>.
ESS Solo1 based PCI sound cards (eg. SC1938)
CONFIG_SOUND_ESSSOLO1
Say Y or M if you have a PCI sound card utilizing the ESS Technology
Solo1 chip. To find out if your sound card uses a
Solo1 chip without removing your computer's cover, use
- lspci -n and look for the PCI ID 125D:1969. This driver
+ lspci -n and look for the PCI ID 125D:1969. This driver
differs slightly from OSS/Free, so PLEASE READ
- Documentation/sound/solo1.
+ <file:Documentation/sound/solo1>.
S3 SonicVibes based PCI sound cards
CONFIG_SOUND_SONICVIBES
Say Y or M if you have a PCI sound card utilizing the S3
SonicVibes chipset. To find out if your sound card uses a
SonicVibes chip without removing your computer's cover, use
- lspci -n and look for the PCI ID 5333:CA00. This driver
+ lspci -n and look for the PCI ID 5333:CA00. This driver
differs slightly from OSS/Free, so PLEASE READ
- Documentation/sound/sonicvibes.
+ <file:Documentation/sound/sonicvibes>.
Trident 4DWave DX/NX, SiS 7018 or ALi 5451 PCI Audio Core
CONFIG_SOUND_TRIDENT
@@ -16082,26 +18516,29 @@
10B9:5451 stands for ALi5451.
This driver supports S/PDIF in/out (record/playback) for ALi 5451
- embedded in ALi M1535+ and M1535D+. Note that they aren't all
+ embedded in ALi M1535+ and M1535D+. Note that they aren't all
enabled by default; you can enable them by saying Y to "/proc file
- system support" and "Sysctl support", and after the /proc file
+ system support" and "Sysctl support", and after the /proc file
system has been mounted, executing the command
command what is enabled
-
+
echo 0>/proc/ALi5451 pcm out is also set to S/PDIF out. (Default).
-
+
echo 1>/proc/ALi5451 use S/PDIF out to output pcm data.
-
- echo 2>/proc/ALi5451 use S/PDIF out to output non-pcm data.(AC3...).
- echo 3>/proc/ALi5451 record from Ac97 in(MIC, Line in...). (Default).
-
- echo 4>/proc/ALi5451 no matter Ac97 settings, record from S/PDIF in.
-
-
+ echo 2>/proc/ALi5451 use S/PDIF out to output non-pcm data.
+ (AC3...).
+
+ echo 3>/proc/ALi5451 record from Ac97 in(MIC, Line in...).
+ (Default).
+
+ echo 4>/proc/ALi5451 no matter Ac97 settings, record from S/PDIF
+ in.
+
+
This driver differs slightly from OSS/Free, so PLEASE READ the
- comments at the top of driver/sound/trident.c
+ comments at the top of <file:drivers/sound/trident.c>.
Rockwell WaveArtist
CONFIG_SOUND_WAVEARTIST
@@ -16119,10 +18556,10 @@
VIA 82C686 MIDI
CONFIG_MIDI_VIA82CXXX
- Answer Y to use the MIDI interface of the Via686. You may need to
- enable this in the BIOS before it will work. This is for connection
- to external MIDI hardware, and is not required for software playback
- of MIDI files.
+ Answer Y to use the MIDI interface of the Via686. You may need to
+ enable this in the BIOS before it will work. This is for connection
+ to external MIDI hardware, and is not required for software playback
+ of MIDI files.
NeoMagic 256AV/256ZX sound chipsets
CONFIG_SOUND_NM256
@@ -16132,13 +18569,76 @@
laptops. It includes support for an AC97-compatible mixer and an
apparently proprietary sound engine.
- See Documentation/sound/NM256 for further information.
+ See <file:Documentation/sound/NM256> for further information.
-ESS Maestro sound chipsets
+ESS Maestro, Maestro2, Maestro2E driver
CONFIG_SOUND_MAESTRO
Say Y or M if you have a sound system driven by ESS's Maestro line
of PCI sound chips. These include the Maestro 1, Maestro 2, and
- Maestro 2E. See Documentation/sound/Maestro for more details.
+ Maestro 2E. See <file:Documentation/sound/Maestro> for more
+ details.
+
+ESS Maestro3/Allegro driver
+CONFIG_SOUND_MAESTRO3
+ Say Y or M if you have a sound system driven by ESS's Maestro 3
+ PCI sound chip.
+
+Adlib Cards
+CONFIG_SOUND_ADLIB
+ Includes ASB 64 4D. Information on programming AdLib cards is
+ available at <http://www.itsnet.com/home/ldragon/Specs/adlib.html>.
+
+Crystal Sound CS4281
+CONFIG_SOUND_CS4281
+ Picture and feature list at
+ <http://www.pcbroker.com/crystal4281.html>.
+
+16 bit sampling option of GUS (_NOT_ GUS MAX)
+CONFIG_SOUND_GUS16
+ Support for Gravis Ulstrasound (GUS) cards (other than the GUS),
+ sampling at 16-bit width.
+
+GUS MAX support
+CONFIG_SOUND_GUSMAX
+ Support for Gravis Ulstrasound MAX.
+
+Intel ICH audio support
+CONFIG_SOUND_ICH
+ Support for integral audio in Intel's I/O Controller Hub (ICH)
+ chipset, as used on the 810/820/840 motherboards.
+
+Verbose initialization
+CONFIG_SOUND_TRACEINIT
+ Verbose soundcard initialization -- affects the format of autoprobe
+ and initialization messages at boot time.
+
+TV card (bt848) mixer support
+CONFIG_SOUND_TVMIXER
+ Support for audio mixer facilities on the BT848 TV frame-grabber
+ card.
+
+VIDC 16-bit sound
+CONFIG_SOUND_VIDC
+ 16-bit support for the VIDC onboard sound hardware found on Acorn
+ machines.
+
+Loopback MIDI device support
+CONFIG_SOUND_VMIDI
+ Support for MIDI loopback on port 1 or 2.
+
+Yamaha YMF7xx PCI audio (native mode)
+CONFIG_SOUND_YMFPCI
+ Support for Yamaha cards including the YMF711, YMF715, YMF718,
+ YMF719, YMF724, Waveforce 192XG, and Waveforce 192 Digital.
+
+Yamaha PCI legacy ports support
+CONFIG_SOUND_YMFPCI_LEGACY
+ Support for YMF7xx PCI cards emulating an MP401.
+
+RME Hammerfall (RME96XX) support
+CONFIG_SOUND_RME96XX
+ Say Y or M if you have a Hammerfall, Hammerfall light or Hammerfall
+ DSP card from RME.
Are you using a crosscompiler
CONFIG_CROSSCOMPILE
@@ -16157,6 +18657,73 @@
only useful for people working on the floating point exception
handler. If you don't, say N.
+Galileo EV64120 Evaluation board
+CONFIG_MIPS_EV64120
+ This is an evaluation board based on the Galileo GT-64120
+ single-chip system controller that contains a MIPS R5000 compatible
+ core running at 75/100MHz. Their website is located at
+ <http://www.galileot.com/>. Say Y here if you wish to build a
+ kernel for this platform.
+
+Galileo EV96100 Evaluation board
+CONFIG_MIPS_EV96100
+ This is an evaluation board based on the Galielo GT-96100 LAN/WAN
+ communications controllers containing a MIPS R5000 compatible core
+ running at 83MHz. Their website is <http://www.galileot.com/>. Say Y
+ here if you wish to build a kernel for this platform.
+
+Support for ITE 8172G board
+CONFIG_MIPS_ITE8172
+ Ths is an evaluation board made by ITE (http://www.ite.com.tw/)
+ with ATX form factor that utilizes a MIPS R5000 to work with its
+ ITE8172G companion internet appliance chip. The MIPS core can be
+ either a NEC Vr5432 or QED RM5231. Say Y here if you wish to build
+ a kernel for this platform.
+
+Support for Globespan IVR board
+CONFIG_MIPS_IVR
+ This is an evaluation board built by Globespan to showcase thir
+ iVR (Internet Video Recorder) design. It utilizes a QED RM5231
+ R5000 MIPS core. More information can be found out their website
+ located at <http://www.globespan.net/products/product4.html>P. Say Y
+ here if you wish to build a kernel for this platform.
+
+Support for Alchemy Semi PB1000 board
+CONFIG_MIPS_PB1000
+ This is an evaluation board built by Alchemy Semiconducttor to
+ showcase their Au1000 Internet Edge Processor. It is SOC design
+ containing a MIPS32 core running at 266/400/500MHz with many
+ integrated peripherals. Further information can be found at their
+ website, <http://www.alchemysemi.com/>. Say Y here if you wish to
+ build a kernel for this platform.
+
+Support for Philips Nino
+CONFIG_NINO
+ Say Y here to select a kernel for the Philips Nino Palm PC. The
+ website at <http://www.realitydiluted.com/projects/nino/index.html>
+ will have more information.
+
+Model-500/510
+CONFIG_NINO_16MB
+ Say Y here to build a kernel specifically for Nino 500/501 color
+ Palm PCs from Philips (INCOMPLETE).
+
+Model-200/210/312/320/325/350/390
+CONFIG_NINO_8MB
+ Say Y here to build a kernel specifically for Nino Palm PCs with
+ 8MB of memory. These include models 200/210/312/320/325/350/390.
+
+Model-300/301/302/319
+CONFIG_NINO_4MB
+ Say Y here to build a kernel specifically for Nino Palm PCs with
+ 4MB of memory. These include models 300/301/302/319.
+
+Low-level debugging
+CONFIG_LL_DEBUG
+ Enable low-level debugging assertion macros in the kernel code.
+ Currently used only by the time services code in the MIPS port.
+ Don't turn this on unless you know what you are doing.
+
Remote GDB kernel debugging
CONFIG_REMOTE_DEBUG
If you say Y here, it will be possible to remotely debug the MIPS
@@ -16182,34 +18749,34 @@
by pressing various keys while holding SysRq (Alt+PrintScreen). It
also works on a serial console (on PC hardware at least), if you
send a BREAK and then within 5 seconds a command keypress. The
- keys are documented in Documentation/sysrq.txt. Don't say Y unless
- you really know what this hack does.
+ keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
+ unless you really know what this hack does.
-ISDN subsystem
+ISDN support
CONFIG_ISDN
ISDN ("Integrated Services Digital Networks", called RNIS in France)
is a special type of fully digital telephone service; it's mostly
used to connect to your Internet service provider (with SLIP or
- PPP). The main advantage is that the speed is higher than ordinary
+ PPP). The main advantage is that the speed is higher than ordinary
modem/telephone connections, and that you can have voice
- conversations while downloading stuff. It only works if your
+ conversations while downloading stuff. It only works if your
computer is equipped with an ISDN card and both you and your service
- provider purchased an ISDN line from the phone company. For details,
- read http://alumni.caltech.edu/~dank/isdn/ on the WWW.
+ provider purchased an ISDN line from the phone company. For
+ details, read <http://alumni.caltech.edu/~dank/isdn/> on the WWW.
This driver allows you to use an ISDN-card for networking
- connections and as dialin/out device. The isdn-tty's have a built in
- AT-compatible modem emulator. Network devices support autodial,
+ connections and as dialin/out device. The isdn-tty's have a built
+ in AT-compatible modem emulator. Network devices support autodial,
channel-bundling, callback and caller-authentication without having
- a daemon running. A reduced T.70 protocol is supported with tty's
- suitable for German BTX. On D-Channel, the protocols EDSS1
- (Euro-ISDN) and 1TR6 (German style) are supported. See
- Documentation/isdn/README for more information.
+ a daemon running. A reduced T.70 protocol is supported with tty's
+ suitable for German BTX. On D-Channel, the protocols EDSS1
+ (Euro-ISDN) and 1TR6 (German style) are supported. See
+ <file:Documentation/isdn/README> for more information.
If you want to compile the ISDN code as a module ( = code which can
be inserted in and removed from the running kernel whenever you
- want), say M here and read Documentation/modules.txt. The module
- will be called isdn.o. If unsure, say N.
+ want), say M here and read <file:Documentation/modules.txt>. The
+ module will be called isdn.o. If unsure, say N.
Support synchronous PPP
CONFIG_ISDN_PPP
@@ -16220,20 +18787,21 @@
protocol is used by Cisco and Sun for example. So you want to say Y
here if the other end of your ISDN connection supports it. You will
need a special version of pppd (called ipppd) for using this
- feature. See Documentation/isdn/README.syncppp and
- Documentation/isdn/syncPPP.FAQ for more information.
+ feature. See <file:Documentation/isdn/README.syncppp> and
+ <file:Documentation/isdn/syncPPP.FAQ> for more information.
Support generic MP (RFC 1717)
CONFIG_ISDN_MPP
With synchronous PPP enabled, it is possible to increase throughput
by bundling several ISDN-connections, using this protocol. See
- Documentation/isdn/README.syncppp for more information.
+ <file:Documentation/isdn/README.syncppp> for more information.
Use VJ-compression with synchronous PPP
CONFIG_ISDN_PPP_VJ
This enables Van Jacobson header compression for synchronous PPP.
Say Y if the other end of the connection supports it.
+Support BSD compression
CONFIG_ISDN_PPP_BSDCOMP
Support for the BSD-Compress compression method for PPP, which uses
the LZW compression method to compress each PPP packet before it is
@@ -16251,19 +18819,19 @@
your Linux box as an ISDN-answering machine. Of course, this must be
supported by the lowlevel driver also. Currently, the HiSax driver
is the only voice-supporting driver. See
- Documentation/isdn/README.audio for more information.
+ <file:Documentation/isdn/README.audio> for more information.
X.25 PLP on top of ISDN
CONFIG_ISDN_X25
- This feature provides the X.25 protocol over ISDN connections.
- See Documentation/isdn/README.x25 for more information
+ This feature provides the X.25 protocol over ISDN connections.
+ See <file:Documentation/isdn/README.x25> for more information
if you are thinking about using this.
ISDN diversion services support
CONFIG_ISDN_DIVERSION
This option allows you to use some supplementary diversion
services in conjunction with the HiSax driver on an EURO/DSS1
- line.
+ line.
Supported options are CD (call deflection), CFU (Call forward
unconditional), CFB (Call forward when busy) and CFNR (call forward
@@ -16274,22 +18842,23 @@
countries. The keypad protocol is still not implemented. CD should
work in all countries if the service has been subscribed to.
- Please read the file Documentation/isdn/README.diversion.
+ Please read the file <file:Documentation/isdn/README.diversion>.
ICN 2B and 4B support
CONFIG_ISDN_DRV_ICN
This enables support for two kinds of ISDN-cards made by a German
- company called ICN. 2B is the standard version for a single ISDN
- line with two B-channels, 4B supports two ISDN lines. For running
+ company called ICN. 2B is the standard version for a single ISDN
+ line with two B-channels, 4B supports two ISDN lines. For running
this card, additional firmware is necessary, which has to be
downloaded into the card using a utility which is distributed
- separately. See Documentation/isdn/README and README.icn for more
- information.
+ separately. See <file:Documentation/isdn/README> and
+ <file:Documentation/isdn/README.icn> for more
+ information.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called icn.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called icn.o.
isdnloop support
CONFIG_ISDN_DRV_LOOP
@@ -16304,19 +18873,19 @@
This is a driver supporting the Siemens chipset on various
ISDN-cards (like AVM A1, Elsa ISDN cards, Teles S0-16.0, Teles
S0-16.3, Teles S0-8, Teles/Creatix PnP, ITK micro ix1 and many
- compatibles).
+ compatibles).
HiSax is just the name of this driver, not the name of any hardware.
-
+
If you have a card with such a chipset, you should say Y here and
also to the configuration option of the driver for your particular
card, below.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called hisax.o. See Documentation/isdn/README.HiSax for more
- information on using this driver.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called hisax.o. See <file:Documentation/isdn/README.HiSax>
+ for more information on using this driver.
HiSax Support for EURO/DSS1
CONFIG_HISAX_EURO
@@ -16324,9 +18893,9 @@
telephone service company provides.
The call control protocol E-DSS1 is used in most European countries.
- If unsure, say yes.
+ If unsure, say Y.
-Support for german charge info
+Support for German chargeinfo
CONFIG_DE_AOC
If you want that the HiSax hardware driver sends messages to the
upper level of the isdn code on each AOCD (Advice Of Charge, During
@@ -16361,230 +18930,265 @@
HiSax Support for US NI1
CONFIG_HISAX_NI1
- Enable this if you like to use ISDN in US on a NI1 basic rate interface.
+ Enable this if you like to use ISDN in US on a NI1 basic rate
+ interface.
Teles 16.0/8.0
CONFIG_HISAX_16_0
This enables HiSax support for the Teles ISDN-cards S0-16.0, S0-8
- and many compatibles.
+ and many compatibles.
- See Documentation/isdn/README.HiSax on how to configure it using the
- different cards, a different D-channel protocol, or non-standard
- IRQ/port/shmem settings.
+ See <file:Documentation/isdn/README.HiSax> on how to configure it
+ using the different cards, a different D-channel protocol, or
+ non-standard IRQ/port/shmem settings.
Teles 16.3 or PNP or PCMCIA
CONFIG_HISAX_16_3
This enables HiSax support for the Teles ISDN-cards S0-16.3 the
Teles/Creatix PnP and the Teles PCMCIA.
-
- See Documentation/isdn/README.HiSax on how to configure it using the
- different cards, a different D-channel protocol, or non-standard
- IRQ/port settings.
+
+ See <file:Documentation/isdn/README.HiSax> on how to configure it
+ using the different cards, a different D-channel protocol, or
+ non-standard IRQ/port settings.
Teles PCI
CONFIG_HISAX_TELESPCI
This enables HiSax support for the Teles PCI.
- See Documentation/isdn/README.HiSax on how to configure it.
-
+ See <file:Documentation/isdn/README.HiSax> on how to configure it.
+
Teles S0Box
CONFIG_HISAX_S0BOX
This enables HiSax support for the Teles/Creatix parallel port
- S0BOX. See Documentation/isdn/README.HiSax on how to configure it.
+ S0BOX. See <file:Documentation/isdn/README.HiSax> on how to
+ configure it.
AVM A1 (Fritz)
CONFIG_HISAX_AVM_A1
This enables HiSax support for the AVM A1 (aka "Fritz").
-
- See Documentation/isdn/README.HiSax on how to configure it using the
- different cards, a different D-channel protocol, or non-standard
- IRQ/port settings.
-AVM PnP/PCI (Fritz!PNP/PCI)
+ See <file:Documentation/isdn/README.HiSax> on how to configure it
+ using the different cards, a different D-channel protocol, or
+ non-standard IRQ/port settings.
+
+AVM PnP/PCI (Fritz!PnP/PCI)
CONFIG_HISAX_FRITZPCI
This enables HiSax support for the AVM "Fritz!PnP" and "Fritz!PCI".
- See Documentation/isdn/README.HiSax on how to configure it.
+ See <file:Documentation/isdn/README.HiSax> on how to configure it.
AVM A1 PCMCIA (Fritz)
CONFIG_HISAX_AVM_A1_PCMCIA
This enables HiSax support for the AVM A1 "Fritz!PCMCIA").
- See Documentation/isdn/README.HiSax on how to configure it.
+ See <file:Documentation/isdn/README.HiSax> on how to configure it.
Elsa cards
CONFIG_HISAX_ELSA
This enables HiSax support for the Elsa Mircolink ISA cards, for the
Elsa Quickstep series cards and Elsa PCMCIA.
- See Documentation/isdn/README.HiSax on how to configure it using the
- different cards, a different D-channel protocol, or non-standard
- IRQ/port settings.
+ See <file:Documentation/isdn/README.HiSax> on how to configure it
+ using the different cards, a different D-channel protocol, or
+ non-standard IRQ/port settings.
ITK ix1-micro Revision 2
CONFIG_HISAX_IX1MICROR2
This enables HiSax support for the ITK ix1-micro Revision 2 card.
- See Documentation/isdn/README.HiSax on how to configure it using the
- different cards, a different D-channel protocol, or non-standard
- IRQ/port settings.
+ See <file:Documentation/isdn/README.HiSax> on how to configure it
+ using the different cards, a different D-channel protocol, or
+ non-standard IRQ/port settings.
Eicon.Diehl Diva cards
CONFIG_HISAX_DIEHLDIVA
This enables HiSax support for the Eicon.Diehl Diva none PRO
versions passive ISDN cards.
- See Documentation/isdn/README.HiSax on how to configure it using the
- different cards, a different D-channel protocol, or non-standard
- IRQ/port settings.
+ See <file:Documentation/isdn/README.HiSax> on how to configure it
+ using the different cards, a different D-channel protocol, or
+ non-standard IRQ/port settings.
ASUSCOM ISA cards
CONFIG_HISAX_ASUSCOM
This enables HiSax support for the AsusCom and their OEM versions
passive ISDN ISA cards.
- See Documentation/isdn/README.HiSax on how to configure it using the
- different cards, a different D-channel protocol, or non-standard
- IRQ/port settings.
+ See <file:Documentation/isdn/README.HiSax> on how to configure it
+ using the different cards, a different D-channel protocol, or
+ non-standard IRQ/port settings.
TELEINT cards
CONFIG_HISAX_TELEINT
This enables HiSax support for the TELEINT SA1 semiactiv ISDN card.
- See Documentation/isdn/README.HiSax on how to configure it using the
- different cards, a different D-channel protocol, or non-standard
- IRQ/port settings.
+ See <file:Documentation/isdn/README.HiSax> on how to configure it
+ using the different cards, a different D-channel protocol, or
+ non-standard IRQ/port settings.
HFC-S based cards
CONFIG_HISAX_HFCS
This enables HiSax support for the HFC-S 2BDS0 based cards, like
teles 16.3c.
-
- See Documentation/isdn/README.HiSax on how to configure it using the
- different cards, a different D-channel protocol, or non-standard
- IRQ/port settings.
+
+ See <file:Documentation/isdn/README.HiSax> on how to configure it
+ using the different cards, a different D-channel protocol, or
+ non-standard IRQ/port settings.
Sedlbauer cards
CONFIG_HISAX_SEDLBAUER
This enables HiSax support for the Sedlbauer passive ISDN cards.
- See Documentation/isdn/README.HiSax on how to configure it using the
- different cards, a different D-channel protocol, or non-standard
- IRQ/port settings.
+ See <file:Documentation/isdn/README.HiSax> on how to configure it
+ using the different cards, a different D-channel protocol, or
+ non-standard IRQ/port settings.
USR Sportster internal TA
CONFIG_HISAX_SPORTSTER
This enables HiSax support for the USR Sportster internal TA card.
- See Documentation/isdn/README.HiSax on how to configure it using a
- different D-channel protocol, or non-standard IRQ/port settings.
+ See <file:Documentation/isdn/README.HiSax> on how to configure it
+ using a different D-channel protocol, or non-standard IRQ/port
+ settings.
MIC card
CONFIG_HISAX_MIC
- This enables HiSax support for the ITH MIC card.
+ This enables HiSax support for the ITH MIC card.
- See Documentation/isdn/README.HiSax on how to configure it using a
- different D-channel protocol, or non-standard IRQ/port settings.
+ See <file:Documentation/isdn/README.HiSax> on how to configure it
+ using a different D-channel protocol, or non-standard IRQ/port
+ settings.
NETjet card
CONFIG_HISAX_NETJET
This enables HiSax support for the NetJet from Traverse
Technologies.
- See Documentation/isdn/README.HiSax on how to configure it using a
- different D-channel protocol, or non-standard IRQ/port settings.
+ See <file:Documentation/isdn/README.HiSax> on how to configure it
+ using a different D-channel protocol, or non-standard IRQ/port
+ settings.
NETspider U card
CONFIG_HISAX_NETJET_U
- This enables HiSax support for the Netspider U interface ISDN card from
- Traverse Technologies.
- See Documentation/isdn/README.HiSax on how to configure it using a
- different D-channel protocol, or non-standard IRQ/port settings.
+ This enables HiSax support for the Netspider U interface ISDN card
+ from Traverse Technologies.
+ See <file:Documentation/isdn/README.HiSax> on how to configure it
+ using a different D-channel protocol, or non-standard IRQ/port
+ settings.
Niccy PnP/PCI card
CONFIG_HISAX_NICCY
- This enables HiSax support for the Dr. Neuhaus Niccy PnP or PCI.
+ This enables HiSax support for the Dr. Neuhaus Niccy PnP or PCI.
- See Documentation/isdn/README.HiSax on how to configure it using a
- different D-channel protocol, or non-standard IRQ/port settings.
+ See <file:Documentation/isdn/README.HiSax> on how to configure it
+ using a different D-channel protocol, or non-standard IRQ/port
+ settings.
Siemens I-Surf card
CONFIG_HISAX_ISURF
This enables HiSax support for the Siemens I-Talk/I-Surf card with
ISAR chip.
- See Documentation/isdn/README.HiSax on how to configure it using a
- different D-channel protocol, or non-standard IRQ/port settings.
+ See <file:Documentation/isdn/README.HiSax> on how to configure it
+ using a different D-channel protocol, or non-standard IRQ/port
+ settings.
HST Saphir card
CONFIG_HISAX_HSTSAPHIR
This enables HiSax support for the HST Saphir card.
-
- See Documentation/isdn/README.HiSax on how to configure it using a
- different D-channel protocol, or non-standard IRQ/port settings.
+
+ See <file:Documentation/isdn/README.HiSax> on how to configure it
+ using a different D-channel protocol, or non-standard IRQ/port
+ settings.
Telekom A4T card
CONFIG_HISAX_BKM_A4T
This enables HiSax support for the Telekom A4T card.
-
- See Documentation/isdn/README.HiSax on how to configure it using a
- different D-channel protocol, or non-standard IRQ/port settings.
+
+ See <file:Documentation/isdn/README.HiSax> on how to configure it
+ using a different D-channel protocol, or non-standard IRQ/port
+ settings.
Scitel Quadro card
CONFIG_HISAX_SCT_QUADRO
This enables HiSax support for the Scitel Quadro card.
-
- See Documentation/isdn/README.HiSax on how to configure it using a
- different D-channel protocol, or non-standard IRQ/port settings.
+
+ See <file:Documentation/isdn/README.HiSax> on how to configure it
+ using a different D-channel protocol, or non-standard IRQ/port
+ settings.
Gazel cards
CONFIG_HISAX_GAZEL
This enables HiSax support for the Gazel cards.
- See Documentation/isdn/README.HiSax on how to configure it using a
- different D-channel protocol, or non-standard IRQ/port settings.
+ See <file:Documentation/isdn/README.HiSax> on how to configure it
+ using a different D-channel protocol, or non-standard IRQ/port
+ settings.
HFC PCI-Bus cards
CONFIG_HISAX_HFC_PCI
This enables HiSax support for the HFC-S PCI 2BDS0 based cards.
-
- For more informations see under Documentation/isdn/README.hfc-pci.
+
+ For more informations see under
+ <file:Documentation/isdn/README.hfc-pci>.
Winbond W6692 based cards
CONFIG_HISAX_W6692
This enables HiSax support for Winbond W6692 based PCI ISDN cards.
-
- See Documentation/isdn/README.HiSax on how to configure it using a
- different D-channel protocol, or non-standard IRQ/port settings.
-HFC-S+, HFC-SP, HFC-PCMCIA cards (EXPERIMENTAL)
+ See <file:Documentation/isdn/README.HiSax> on how to configure it
+ using a different D-channel protocol, or non-standard IRQ/port
+ settings.
+
+HFC-S+, HFC-SP, HFC-PCMCIA cards
CONFIG_HISAX_HFC_SX
This enables HiSax support for the HFC-S+, HFC-SP and HFC-PCMCIA
cards. This code is not finished yet.
-Am7930 (EXPERIMENTAL)
+Am7930
CONFIG_HISAX_AMD7930
This enables HiSax support for the AMD7930 chips on some SPARCs.
This code is not finished yet.
+HiSax debugging
+CONFIG_HISAX_DEBUG
+ This enables debugging code in the new-style HiSax drivers, i.e.
+ the ST5481 USB driver currently.
+ If in doubt, say yes.
+
+ELSA PCMCIA MicroLink cards
+CONFIG_HISAX_ELSA_CS
+ This enables the PCMCIA client driver for the Elsa PCMCIA MicroLink
+ card.
+
+Sedlbauer PCMCIA cards
+CONFIG_HISAX_SEDLBAUER_CS
+ This enables the PCMCIA client driver for the Sedlbauer Speed Star
+ and Speed Star II cards.
+
+ST5481 USB ISDN adapter
+CONFIG_HISAX_ST5481
+ This enables the driver for ST5481 based USB ISDN adapters,
+ e.g. the BeWan Gazel 128 USB
+
PCBIT-D support
CONFIG_ISDN_DRV_PCBIT
- This enables support for the PCBIT ISDN-card. This card is
- manufactured in Portugal by Octal. For running this card, additional
- firmware is necessary, which has to be downloaded into the card
- using a utility which is distributed separately. See
- Documentation/isdn/README and Documentation/isdn/README.pcbit for
- more information.
+ This enables support for the PCBIT ISDN-card. This card is
+ manufactured in Portugal by Octal. For running this card,
+ additional firmware is necessary, which has to be downloaded into
+ the card using a utility which is distributed separately. See
+ <file:Documentation/isdn/README> and
+ <file:Documentation/isdn/README.pcbit> for more information.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called pcbit.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called pcbit.o.
-Spellcaster support (EXPERIMENTAL)
+Spellcaster support
CONFIG_ISDN_DRV_SC
- This enables support for the Spellcaster BRI ISDN boards. This
+ This enables support for the Spellcaster BRI ISDN boards. This
driver currently builds only in a modularized version ( = code which
can be inserted in and removed from the running kernel whenever you
- want, details in Documentation/modules.txt); the module will be
- called sc.o. See Documentation/isdn/README.sc and
- http://www.spellcast.com for more information.
+ want, details in <file:Documentation/modules.txt>); the module will
+ be called sc.o. See <file:Documentation/isdn/README.sc> and
+ <http://www.spellcast.com> for more information.
Eicon active card support
CONFIG_ISDN_DRV_EICON
@@ -16592,23 +19196,29 @@
this card, additional firmware is necessary, which has to be loaded
into the card using the eiconctrl utility which is part of the
latest isdn4k-utils package. Please read the file
- Documentation/isdn/README.eicon for more information.
-
-Eicon Diva Server card support
+ <file:Documentation/isdn/README.eicon> for more information.
+
+Legacy Eicon driver
+CONFIG_ISDN_DRV_EICON_OLD
+ Say Y here to use your Eicon active ISDN card with ISDN4Linux
+ isdn module.
+
+Eicon PCI DIVA Server BRI/PRI/4BRI support
CONFIG_ISDN_DRV_EICON_PCI
- Say Y here if you have an Eicon Diva Server (BRI/PRI/4BRI) ISDN card.
- Please read Documentation/isdn/README.eicon for more information.
-
-Eicon old-type card support
+ Say Y here if you have an Eicon Diva Server (BRI/PRI/4BRI) ISDN
+ card. Please read <file:Documentation/isdn/README.eicon> for more
+ information.
+
+Eicon old-type (S,SX,SCOM,Quadro,S2M) card support
CONFIG_ISDN_DRV_EICON_ISA
Say Y here if you have an old-type Eicon active ISDN card. In order
to use this card, additional firmware is necessary, which has to be
loaded into the card using the eiconctrl utility which is part of
the latest isdn4k-utils package. Please read the file
- Documentation/isdn/README.eicon for more information.
+ <file:Documentation/isdn/README.eicon> for more information.
Eicon driver type standalone
-CONFIG_ISDN_DRV_EICON_STANDALONE
+CONFIG_ISDN_DRV_EICON_DIVAS
Enable this option if you want the eicon driver as standalone
version with no interface to the ISDN4Linux isdn module. If you
say Y here, the eicon module only supports the Diva Server PCI
@@ -16621,20 +19231,49 @@
Fax Class 1 and 2 commands. Using a getty with fax-support
(mgetty+sendfax, hylafax), you will be able to use your Linux box as
an ISDN-fax-machine. This must be supported by the lowlevel driver
- also. See Documentation/isdn/README.fax for more information.
+ also. See <file:Documentation/isdn/README.fax> for more information.
CAPI2.0 support
CONFIG_ISDN_CAPI
This provides the CAPI (Common ISDN Application Programming
Interface, a standard making it easy for programs to access ISDN
- hardware, see http://www.capi.org/ . This is needed for AVM's set of
- active ISDN controllers like B1, T1, M1.
+ hardware, see <http://www.capi.org/>. This is needed for AVM's set
+ of active ISDN controllers like B1, T1, M1.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The modules will be called capi.o and kernelcapi.o. If you want to
compile it as a module, say M here and read
- Documentation/modules.txt.
+ <file:Documentation/modules.txt>.
+
+CAPI2.0 /dev/capi20 support
+CONFIG_ISDN_CAPI_CAPI20
+ This option will provide the CAPI 2.0 interface to userspace
+ applications via /dev/capi20. Applications should use the
+ standardized libcapi20 to access this functionality. You should say
+ Y/M here.
+
+CAPI2.0 Middleware support
+CONFIG_ISDN_CAPI_MIDDLEWARE
+ This option will enhance the capabilities of the /dev/capi20
+ interface. It will provide a means of moving a data connection,
+ established via the usual /dev/capi20 interface to a special tty
+ device. If you want to use pppd with pppdcapiplugin to dial up to
+ your ISP, say Y here.
+
+CAPI2.0 filesystem support
+CONFIG_ISDN_CAPI_CAPIFS
+ This option provides a special file system, similar to /dev/pts with
+ device nodes for the special ttys established by using the
+ middleware extension above. If you want to use pppd with
+ pppdcapiplugin to dial up to your ISP, say Y here.
+
+CAPI2.0 capidrv interface support
+CONFIG_ISDN_CAPI_CAPIDRV
+ This option provides the glue code to hook up CAPI driven cards to
+ the legacy isdn4linux link layer. If you have a card which is
+ supported by a CAPI driver, but still want to use old features like
+ ippp interfaces or ttyI emulation, say Y/M here.
AVM B1 ISA support
CONFIG_ISDN_DRV_AVMB1_B1ISA
@@ -16657,6 +19296,11 @@
CONFIG_ISDN_DRV_AVMB1_B1PCMCIA
Enable support for the PCMCIA version of the AVM B1 card.
+AVM B1/M1/M2 PCMCIA cs module
+CONFIG_ISDN_DRV_AVMB1_AVM_CS
+ Enable the PCMCIA client driver for the AVM B1/M1/M2
+ PCMCIA cards.
+
AVM T1/T1-B PCI support
CONFIG_ISDN_DRV_AVMB1_T1PCI
Enable support for the AVM T1 T1B card.
@@ -16673,40 +19317,40 @@
disconnecting. This will increase the size of the kernel by 7 KB. If
unsure, say Y.
-IBM Active 2000 support (EXPERIMENTAL)
+IBM Active 2000 support
CONFIG_ISDN_DRV_ACT2000
Say Y here if you have an IBM Active 2000 ISDN card. In order to use
this card, additional firmware is necessary, which has to be loaded
into the card using a utility which is part of the latest
isdn4k-utils package. Please read the file
- Documentation/isdn/README.act2000 for more information.
+ <file:Documentation/isdn/README.act2000> for more information.
Auvertech TurboPAM support
CONFIG_ISDN_DRV_TPAM
This enables support for the Auvertech TurboPAM ISDN-card.
For running this card, additional firmware is necessary, which has
to be downloaded into the card using a utility which is distributed
- separately from the Auvertech's web site: http://www.auvertech.fr.
+ separately from the Auvertech's web site: <http://www.auvertech.fr>.
Please redirect all support questions to support@auvertech.fr.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called tpam.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called tpam.o.
Hypercope HYSDN cards (Champ, Ergo, Metro) support (module)
CONFIG_HYSDN
Say Y here if you have one of Hypercope's active PCI ISDN cards
Champ, Ergo and Metro. You will then get a module called hysdn.o.
- Please read the file Documentation/isdn/README.hysdn for more
+ Please read the file <file:Documentation/isdn/README.hysdn> for more
information.
HYSDN CAPI 2.0 support
CONFIG_HYSDN_CAPI
- Say Y here if you like to use Hypercope's CAPI 2.0 interface
+ Say Y here if you like to use Hypercope's CAPI 2.0 interface.
-Support for Sun4 architecture
+Support for SUN4 machines (disables SUN4[CDM] support)
CONFIG_SUN4
Say Y here if, and only if, your machine is a Sun4. Note that
a kernel compiled with this option will run only on Sun4.
@@ -16720,7 +19364,7 @@
This support is also available as a module called esp.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
PTI Qlogic, ISP Driver
CONFIG_SCSI_QLOGICPTI
@@ -16732,17 +19376,22 @@
This support is also available as a module called qlogicpti.o ( =
code which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
-SPARC /dev/openprom compatibility driver (EXPERIMENTAL)
+Sun PROM console
+CONFIG_PROM_CONSOLE
+ Say Y to build a console driver for Sun machines that uses the
+ terminal emulation built into their console PROMS.
+
+/dev/openprom device support
CONFIG_SUN_OPENPROMIO
This driver provides user programs with an interface to the SPARC
PROM device tree. The driver implements a SunOS-compatible
- interface and a NetBSD-compatible interface.
+ interface and a NetBSD-compatible interface.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M and read Documentation/modules.txt. If unsure, say Y.
+ say M and read <file:Documentation/modules.txt>. If unsure, say Y.
Openprom tree appears in /proc/openprom
CONFIG_SUN_OPENPROMFS
@@ -16752,8 +19401,9 @@
If you want to compile the /proc/openprom support as a module ( =
code which can be inserted in and removed from the running kernel
- whenever you want), say M here and read Documentation/modules.txt.
- The module will be called openpromfs.o. If unsure, say M.
+ whenever you want), say M here and read
+ <file:Documentation/modules.txt>.
+ The module will be called openpromfs.o. If unsure, say M.
Kernel support for Linux/Sparc 32bit binary compatibility
CONFIG_SPARC32_COMPAT
@@ -16773,11 +19423,11 @@
SunOS binary emulation
CONFIG_SUNOS_EMUL
- This allows you to run most SunOS binaries. If you want to do this,
+ This allows you to run most SunOS binaries. If you want to do this,
say Y here and place appropriate files in /usr/gnemul/sunos. See
- http://www.ultralinux.org/faq.html for more information. If you want
- to run SunOS binaries on an Ultra you must also say Y to "Kernel
- support for 32-bit a.out binaries" above.
+ <http://www.ultralinux.org/faq.html> for more information. If you
+ want to run SunOS binaries on an Ultra you must also say Y to
+ "Kernel support for 32-bit a.out binaries" above.
Mostek real time clock support
CONFIG_SUN_MOSTEK_RTC
@@ -16802,17 +19452,37 @@
This driver supports the serial ports on newer (PCI) Ultra systems.
Say Y if you want to be able to use your serial ports.
-Aurora Multiboard 1600se (EXPERIMENTAL)
+Videopix Frame Grabber
+CONFIG_SUN_VIDEOPIX
+ Say Y here to support the Videopix Frame Grabber from Sun
+ Microsystems, commonly found on SPARCstations. This card, which is
+ based on the Phillips SAA9051, can handle NTSC and PAL/SECAM and
+ SVIDEO signals.
+
+Sun bidirectional parallel port support
+CONFIG_SUN_BPP
+ Say Y here to support Sun's obsolete variant of IEEE1284
+ bidirectional parallel port protocol as /dev/bppX. Can be built on
+ x86 machines.
+
+Aurora Multiboard 1600se
CONFIG_SUN_AURORA
The Aurora Multiboard is a multi-port high-speed serial controller.
If you have one of these, say Y.
-Audio support (EXPERIMENTAL)
+Tadpole TS102 Microcontroller support
+CONFIG_TADPOLE_TS102_UCTRL
+ Say Y here to directly support the TS102 Microcontroller interface
+ on the Tadpole Sparcbook 3. This device handles power-management
+ events, and can also notice the attachment/detachment of external
+ monitors and mice.
+
+Audio support
CONFIG_SPARCAUDIO
This driver provides support for the build-in sound devices on most
Sun machines. If you want to be able to use this, select this option
and one or more of the lowlevel drivers below. See
- http://www.dementia.org/~shadow/sparcaudio.html for more
+ <http://www.dementia.org/~shadow/sparcaudio.html> for more
information.
AMD7930 Lowlevel Driver
@@ -16830,18 +19500,83 @@
This driver supports the DBRI audio interface found on the SS10,
SS20, Sparcbook 3, and Voyager systems.
-Dummy lowlevel Driver
+Dummy Lowlevel Driver
CONFIG_SPARCAUDIO_DUMMY
This is a pseudo-driver used for debugging and testing the
sparcaudio subsystem. Say N unless you want to work on this
subsystem.
-Sparc hardware (EXPERIMENTAL)
+Sparc hardware
CONFIG_PARPORT_SUNBPP
This driver provides support for the bidirectional parallel port
found on many Sun machines. Note that many of the newer Ultras
actually have pc style hardware instead.
+/proc/hardware support
+CONFIG_PROC_HARDWARE
+ Say Y here to support the /proc/hardware file, which gives you
+ access to information about the machine you're running on,
+ including the model, CPU, MMU, clock speed, BogoMIPS rating,
+ and memory size.
+
+Bluetooth subsystem support
+CONFIG_BLUEZ
+ Bluetooth is low-cost, low-power, short-range wireless technology.
+ It was designed as a replacement for cables and other short-range
+ technologies like IrDA. Bluetooth operates in personal area range
+ that typically extends up to 10 meters. More information about
+ Bluetooth can be found at <http://www.bluetooth.com>.
+
+ Linux Bluetooth subsystem consist of several layers:
+ HCI Core (device and connection manager, scheduler)
+ HCI Device drivers (interface to the hardware)
+ L2CAP Module (L2CAP protocol)
+
+ Say Y here to enable Linux Bluetooth support and to build HCI Core
+ layer.
+
+ To use Linux Bluetooth subsystem, you will need several user-space
+ utilities like hciconfig and hcid. These utilities and updates to
+ Bluetooth kernel modules are provided in the BlueZ package.
+ For more information, see <http://bluez.sf.net>.
+
+ If you want to compile HCI Core as module (hci.o) say M here.
+
+L2CAP protocol support
+CONFIG_BLUEZ_L2CAP
+ L2CAP (Logical Link Control and Adaptation Protocol) provides
+ connection oriented and connection-less data transport. L2CAP
+ support is required for most Bluetooth applications.
+
+ Say Y here to compile L2CAP support into the kernel or say M to
+ compile it as module (l2cap.o).
+
+HCI UART driver
+CONFIG_BLUEZ_HCIUART
+ Bluetooth HCI UART driver.
+ This driver is required if you want to use Bluetooth devices with
+ serial port interface.
+
+ Say Y here to compile support for Bluetooth UART devices into the
+ kernel or say M to compile it as module (hci_uart.o).
+
+HCI USB driver
+CONFIG_BLUEZ_HCIUSB
+ Bluetooth HCI USB driver.
+ This driver is required if you want to use Bluetooth devices with
+ USB interface.
+
+ Say Y here to compile support for Bluetooth USB devices into the
+ kernel or say M to compile it as module (hci_usb.o).
+
+HCI VHCI virtual HCI device driver
+CONFIG_BLUEZ_HCIVHCI
+ Bluetooth Virtual HCI device driver.
+ This driver is required if you want to use HCI Emulation software.
+
+ Say Y here to compile support for virtual HCI devices into the
+ kernel or say M to compile it as module (hci_vhci.o).
+
# The following options are for Linux when running on the Hitachi
# SuperH family of RISC microprocessors.
@@ -16959,20 +19694,45 @@
#
# m68k-specific kernel options
-# Documented by Chris Lawrence <quango@themall.net> et al.
+# Documented by Chris Lawrence <mailto:quango@themall.net> et al.
#
Amiga support
CONFIG_AMIGA
This option enables support for the Amiga series of computers. If
you plan to use this kernel on an Amiga, say Y here and browse the
- material available in Documentation/m68k; otherwise say N.
+ material available in <file:Documentation/m68k>; otherwise say N.
+
+Commodore A2232 serial support
+CONFIG_A2232
+ This option supports the 2232 7-port serial card shipped with the
+ Amiga 2000 and other Zorro-bus machines, dating from 1989. At
+ a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
+ each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
+ ports were connected with 8 pin DIN connectors on the card bracket,
+ for which 8 pin to DB25 adapters were supplied. The card also had
+ jumpers internally to toggle various pinning configurations.
+
+ This driver can be built as a module; but then "generic_serial.o"
+ will also be built as a module. This has to be loaded before
+ "ser_a2232.o". If you want to do this, answer M here and read
+ "<file:Documentation/modules.txt>".
+
+A4000T SCSI support
+CONFIG_A4000T_SCSI
+ Support for the NCR53C710 SCSI controller on the Amiga 4000T.
+
+A4091 SCSI support
+CONFIG_A4091_SCSI
+ Support for the NCR53C710 chip on the Amiga 4091 Z3 SCSI2 controller
+ (1993). Very obscure -- the 4091 was part of an Amiga 4000 upgrade
+ plan at the time the Amiga business was sold to DKB.
Atari support
CONFIG_ATARI
This option enables support for the 68000-based Atari series of
computers (including the TT, Falcon and Medusa). If you plan to use
this kernel on an Atari, say Y here and browse the material
- available in Documentation/m68k; otherwise say N.
+ available in <file:Documentation/m68k>; otherwise say N.
Hades support
CONFIG_HADES
@@ -16984,7 +19744,7 @@
This option enables support for the Apple Macintosh series of
computers (yes, there is experimental support now, at least for part
of the series).
-
+
Say N unless you're willing to code the remaining necessary support.
;)
@@ -16995,14 +19755,51 @@
If you plan to try to use the kernel on such a machine say Y here.
Everybody else says N.
+Q40/Q60 support
+CONFIG_Q40
+ The Q40 is a Motorola 68040-based successor to the Sinclair QL
+ manufactured in Germany. There is an official Q40 home page at
+ <http://www.q40.de/>. This option enables support for the Q40 and
+ Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
+ emulation.
+
+Sun 3 support
+CONFIG_SUN3
+ This option enables support for the Sun 3 series of workstations.
+ Currently, only the Sun 3/80 is supported within the Sun 3x family.
+ You will also want to enable 68030 support. General Linux
+ information on the Sun 3x series (now discontinued) is at
+ <http://www.angelfire.com/ca2/tech68k/sun3.html>.
+
+ If you don't want to compile a kernel for a Sun 3, say N.
+
Sun 3X support
CONFIG_SUN3X
This option enables support for the Sun 3x series of workstations.
Be warned that this support is very experimental. You will also want
to say Y to 68020 support and N to the other processors below.
+ General Linux information on the Sun 3x series (now discontinued)
+ is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
If you don't want to compile a kernel for a Sun 3x, say N.
+Sun3x builtin serial support
+CONFIG_SUN3X_ZS
+ ZS refers to a type of asynchronous serial port built in to the Sun3
+ and Sun3x workstations; if you have a Sun 3, you probably have
+ these. Say 'Y' to support ZS ports directly. This option must be
+ enabled in order to support the
+ keyboard and mouse ports.
+
+Sun keyboard support
+CONFIG_SUN_KEYBOARD
+ Say Y here to support the keyboard found on Sun 3 and 3x
+ workstations. It can also be used support Sun Type-5 keyboards
+ through an adaptor. See
+ <http://www.suse.cz/development/input/adapters.html> and
+ <http://sourceforge.net/projects/linuxconsole/> for details on the
+ latter.
+
68020 support
CONFIG_M68020
If you anticipate running this kernel on a computer with a MC68020
@@ -17028,7 +19825,7 @@
If you anticipate running this kernel on a computer with a MC68060
processor, say Y. Otherwise, say N.
-Math emulation support (EXPERIMENTAL)
+Math emulation support
CONFIG_M68KFPU_EMU
At some point in the future, this will cause floating-point math
instructions to be emulated by the kernel on machines that lack a
@@ -17060,19 +19857,25 @@
This gives you access to some advanced options for the CPU. The
defaults should be fine for most users, but these options may make
it possible for you to improve performance somewhat if you know what
- you are doing.
+ you are doing.
Note that the answer to this question won't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all
the questions about these options.
Most users should say N to this question.
+Use one physical chunk of memory only
+CONFIG_SINGLE_MEMORY_CHUNK
+ Ignore all but the first contiguous chunk of physical memory for VM
+ purposes. This will save a few bytes kernel size and may speed up
+ some operations. Say N if not sure.
+
Use read-modify-write instructions
CONFIG_RMW_INSNS
This allows to use certain instructions that work with indivisible
read-modify-write bus cycles. While this is faster than the
- workaround of disabling interrupts, it can conflict with DMA
+ workaround of disabling interrupts, it can conflict with DMA
( = direct memory access) on many Amiga systems, and it is also said
to destabilize other machines. It is very likely that this will
cause serious problems on any Amiga or Atari Medusa if set. The only
@@ -17081,7 +19884,7 @@
really know what you are doing, say N. Try Y only if you're quite
adventurous.
-Zorro support
+Amiga Zorro (AutoConfig) bus support
CONFIG_ZORRO
This enables support for the Zorro bus in the Amiga. If you have
expansion cards in your Amiga that conform to the Amiga
@@ -17103,23 +19906,34 @@
When in doubt, say Y.
-Amiga 1200/600 PCMCIA support (EXPERIMENTAL)
+Amiga 1200/600 PCMCIA support
CONFIG_AMIGA_PCMCIA
Include support in the kernel for pcmcia on Amiga 1200 and Amiga
600. If you intend to use pcmcia cards say Y; otherwise say N.
+Hisoft Whippet PCMCIA serial support
+CONFIG_WHIPPET_SERIAL
+ HiSoft has a web page at <http://www.hisoft.co.uk/>, but there
+ is no listing for the Whippet in their Amiga section.
+
Amiga Zorro II ramdisk support
CONFIG_AMIGA_Z2RAM
This enables support for using Chip RAM and Zorro II RAM as a
ramdisk or as a swap partition. Say Y if you want to include this
- driver in the kernel. This driver is also available as a module
+ driver in the kernel. This driver is also available as a module
( = code which can be inserted in and removed from the running
kernel whenever you want). The module is called z2ram.o. If you want
to compile it as a module, say M here and read
- Documentation/modules.txt.
+ <file:Documentation/modules.txt>.
-Atari ST-RAM swap support
+Support for ST-RAM as swap space
CONFIG_STRAM_SWAP
+ Some Atari 68k macines (including the 520STF and 1020STE) divide
+ their addressible memory into ST and TT sections. The TT section
+ (up to 512MB) is the main memory; the ST section (up to 4MB) is
+ accessible to the built-in graphics board, runs slower, and is
+ present mainly for backward compatibility with older machines.
+
This enables support for using (parts of) ST-RAM as swap space,
instead of as normal system memory. This can first enhance system
performance if you have lots of alternate RAM (compared to the size
@@ -17130,6 +19944,12 @@
sound). The probability that such allocations at module load time
fail is drastically reduced.
+ST-RAM statistics in /proc
+CONFIG_STRAM_PROC
+ Say Y here to report ST-RAM usage statistics in /proc/stram. See
+ the help for CONFIG_STRAM_SWAP for discussion of ST-RAM and its
+ uses.
+
Atari ACSI support
CONFIG_ATARI_ACSI
This enables support for the Atari ACSI interface. The driver
@@ -17140,7 +19960,7 @@
driver is also the basis for certain other drivers for devices
attached to the ACSI bus: Atari SLM laser printer, BioNet-100
Ethernet, and PAMsNet Ethernet. If you want to use one of these
- devices, you need ACSI support, too.
+ devices, you need ACSI support, too.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -17171,7 +19991,7 @@
also available as a module ( = code which can be inserted in and
removed from the running kernel whenever you want). The module is
called wd33c93.o. If you want to compile it as a module, say M here
- and read Documentation/modules.txt.
+ and read <file:Documentation/modules.txt>.
A2091 WD33C93A support
CONFIG_A2091_SCSI
@@ -17179,7 +19999,7 @@
say N. This driver is also available as a module ( = code which can
be inserted in and removed from the running kernel whenever you
want). The module is called wd33c93.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
+ a module, say M here and read <file:Documentation/modules.txt>.
GVP Series II WD33C93A support
CONFIG_GVP11_SCSI
@@ -17192,21 +20012,21 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you
want). The module will be called gvp11.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt.
+ as a module, say M here and read <file:Documentation/modules.txt>.
-Cyberstorm SCSI support
+CyberStorm SCSI support
CONFIG_CYBERSTORM_SCSI
If you have an Amiga with an original (MkI) Phase5 Cyberstorm
accelerator board and the optional Cyberstorm SCSI controller,
answer Y. Otherwise, say N.
-Cyberstorm II SCSI support
+CyberStorm II SCSI support
CONFIG_CYBERSTORMII_SCSI
If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
and the optional Cyberstorm SCSI controller, say Y. Otherwise,
answer N.
-Blizzard 2060 SCSI support (EXPERIMENTAL)
+Blizzard 2060 SCSI support
CONFIG_BLZ2060_SCSI
If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
and want to use the onboard SCSI controller, say Y. Otherwise,
@@ -17228,18 +20048,25 @@
If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
one in the near future, say Y to this question. Otherwise, say N.
+BSC Oktagon SCSI support
+CONFIG_OKTAGON_SCSI
+ If you have the BSC Oktagon SCSI disk controller for the Amiga, say
+ Y to this question. If you're in doubt about whether you have one,
+ see the picture at
+ <http://amiga.multigraph.com/photos/oktagon.html>.
+
Atari native SCSI support
CONFIG_ATARI_SCSI
If you have an Atari with built-in NCR5380 SCSI controller (TT,
Falcon, ...) say Y to get it supported. Of course also, if you have
- a compatible SCSI controller (e.g. for Medusa). This driver is also
+ a compatible SCSI controller (e.g. for Medusa). This driver is also
available as a module ( = code which can be inserted in and removed
- from the running kernel whenever you want). The module is called
- atari_scsi.o. If you want to compile it as a module, say M here and
- read Documentation/modules.txt. This driver supports both styles of
- NCR integration into the system: the TT style (separate DMA), and
- the Falcon style (via ST-DMA, replacing ACSI). It does NOT support
- other schemes, like in the Hades (without DMA).
+ from the running kernel whenever you want). The module is called
+ atari_scsi.o. If you want to compile it as a module, say M here and
+ read <file:Documentation/modules.txt>. This driver supports both
+ styles of NCR integration into the system: the TT style (separate
+ DMA), and the Falcon style (via ST-DMA, replacing ACSI). It does
+ NOT support other schemes, like in the Hades (without DMA).
Long delays for Toshiba CD-ROMs
CONFIG_ATARI_SCSI_TOSHIBA_DELAY
@@ -17248,6 +20075,12 @@
use a Toshiba CD-ROM drive; otherwise, the option is not needed and
would impact performance a bit, so say N.
+Reset SCSI-devices at boottime
+CONFIG_ATARI_SCSI_RESET_BOOT
+ Reset the devices on your Atari whenever it boots. This makes the
+ boot process fractionally longer but may assist recovery from errors
+ that leave the devices with SCSI operations partway completed.
+
Hades SCSI DMA emulator
CONFIG_TT_DMA_EMUL
This option enables code which emulates the TT SCSI DMA chip on the
@@ -17262,7 +20095,7 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you
want). The module is called ariadne.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
+ a module, say M here and read <file:Documentation/modules.txt>.
Ariadne II and X-Surf support
CONFIG_ARIADNE2
@@ -17273,7 +20106,7 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called ariadne2.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
+ a module, say M here and read <file:Documentation/modules.txt>.
A2065 support
CONFIG_A2065
@@ -17283,7 +20116,7 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you
want). The module is called a2065.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
Hydra support
CONFIG_HYDRA
@@ -17292,17 +20125,30 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you
want). The module is called hydra.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
-Pcmcia NE2000 compatible support
+Sun3 NCR5380 SCSI
+CONFIG_SUN3_SCSI
+ This option will enable support for the OBIO (onboard io) NCR5380
+ SCSI controller found in the Sun 3/50 and 3/60. Note that this
+ driver does not provide support for VME SCSI boards.
+ General Linux information on the Sun 3 series (now discontinued)
+ is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
+
+Sun3x ESP SCSI driver
+CONFIG_SUN3X_ESP
+ The ESP was an on-board SCSI controller used on Sun 3/80
+ machines. Say Y here to compile in support for it.
+
+PCMCIA NE2000 and compatibles support
CONFIG_APNE
- If you have a pcmcia ne2000 compatible adapter, say Y. Otherwise,
+ If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
say N.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you
want). The module is called apne.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
Atari Lance support
CONFIG_ATARILANCE
@@ -17324,32 +20170,32 @@
Amiga mouse support
CONFIG_AMIGAMOUSE
- If you want to be able to use an Amiga mouse in Linux, say Y.
+ If you want to be able to use an Amiga mouse in Linux, say Y.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module is called amigamouse.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
Atari mouse support
CONFIG_ATARIMOUSE
- If you want to be able to use an Atari mouse in Linux, say Y.
+ If you want to be able to use an Atari mouse in Linux, say Y.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module is called atarimouse.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
Atari MFP serial support
CONFIG_ATARI_MFPSER
If you like to use the MFP serial ports ("Modem1", "Serial1") under
Linux, say Y. The driver equally supports all kinds of MFP serial
- ports and automatically detects whether Serial1 is available.
+ ports and automatically detects whether Serial1 is available.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
If you want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ <file:Documentation/modules.txt>.
Note for Falcon users: You also have an MFP port, it's just not
wired to the outside... But you could use the port under Linux.
@@ -17365,7 +20211,7 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
If you want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ <file:Documentation/modules.txt>.
Atari SCC serial DMA support
CONFIG_ATARI_SCC_DMA
@@ -17382,9 +20228,9 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you
want). If you want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ <file:Documentation/modules.txt>.
-Atari DSP56k Digital Signal Processor support (EXPERIMENTAL)
+Atari DSP56k Digital Signal Processor support
CONFIG_ATARI_DSP56K
If you want to be able to use the DSP56001 in Falcons, say Y. This
driver is still experimental, and if you don't know what it is, or
@@ -17393,7 +20239,12 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
If you want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ <file:Documentation/modules.txt>.
+
+Support for early boot text console
+CONFIG_BOOTX_TEXT
+ Say Y here to see progress messages from the boot firmware in text
+ mode. Requires either BootX or Open Firmware.
Amiga builtin serial support
CONFIG_AMIGA_BUILTIN_SERIAL
@@ -17403,13 +20254,23 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you
want). If you want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ <file:Documentation/modules.txt>.
GVP IO-Extender support
CONFIG_GVPIOEXT
If you want to use a GVP IO-Extender serial card in Linux, say Y.
Otherwise, say N.
+GVP IO-Extender parallel printer support
+CONFIG_GVPIOEXT_LP
+ Say Y to enable driving a printer from the parallel port on your
+ GVP IO-Extender card, N otherwise.
+
+GVP IO-Extender PLIP support
+CONFIG_GVPIOEXT_PLIP
+ Say Y to enable doing IP over the parallel port on your GVP
+ IO-Extender card, N otherwise.
+
Multiface Card III serial support
CONFIG_MULTIFACE_III_TTY
If you want to use a Multiface III card's serial port in Linux,
@@ -17418,7 +20279,15 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
If you want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ <file:Documentation/modules.txt>.
+
+Amiga/Atari/PowerMac DMA sound support
+CONFIG_DMASOUND
+ Support built-in audio chips accessible by DMA on various machines
+ that have them. Note that this symbol does not affect the kernel
+ directly; rather, it controls whether configuration questions
+ enabling DMA sound drivers for various specific machine
+ architectures will be used.
Atari DMA sound support
CONFIG_DMASOUND_ATARI
@@ -17429,7 +20298,7 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you
want). If you want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ <file:Documentation/modules.txt>.
PowerMac DMA sound support
CONFIG_DMASOUND_AWACS
@@ -17440,7 +20309,7 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you
want). If you want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ <file:Documentation/modules.txt>.
Amiga DMA sound support
CONFIG_DMASOUND_PAULA
@@ -17451,7 +20320,7 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you
want). If you want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ <file:Documentation/modules.txt>.
Q40 sound support
CONFIG_DMASOUND_Q40
@@ -17462,7 +20331,7 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you
want). If you want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ <file:Documentation/modules.txt>.
HP DCA serial support
CONFIG_HPDCA
@@ -17480,39 +20349,122 @@
HP300 machines. If you are using such a system you almost certainly
want this.
+# Choice: ppctype
Processor Type
CONFIG_6xx
- There are four types of PowerPC chips supported. The more common
- types (601, 603, 604, 740, 750, 7400), the Motorola embedded versions
- (821, 823, 850, 855, 860, 8260), the IBM embedded versions (403 and
- 405) and the high end 64 bit Power processors (Power 3, Power 4).
- Unless you are building a kernel for one of the embedded processor
- systems, or a 64 bit IBM RS/6000, choose 6xx. Note that the kernel
- runs in 32-bit mode even on 64-bit chips. Also note that because
- the 82xx family has a 603e core, specific support for that chipset
- is asked later on.
+ There are four types of PowerPC chips supported. The more common
+ types (601, 603, 604, 740, 750, 7400), the Motorola embedded
+ versions (821, 823, 850, 855, 860, 8260), the IBM embedded versions
+ (403 and 405) and the high end 64 bit Power processors (Power 3,
+ Power 4). Unless you are building a kernel for one of the embedded
+ processor systems, or a 64 bit IBM RS/6000, choose 6xx. Note that
+ the kernel runs in 32-bit mode even on 64-bit chips. Also note that
+ because the 82xx family has a 603e core, specific support for that
+ chipset is asked later on.
Motorola MPC8260 CPM support
CONFIG_8260
The MPC8260 CPM (Communications Processor Module) is a typical
- embedded CPU made by Motorola. Selecting this option means that you
- wish to build a kernel for a machine with specifically an 8260 for
- a CPU.
+ embedded CPU made by Motorola. Selecting this option means that
+ you wish to build a kernel for a machine with specifically an 8260
+ for a CPU.
If in doubt, say N.
+# Choice: Machine type
+Oak
+CONFIG_OAK
+ Select Oak if you have an IBM 403GCX "Oak" Evaluation Board.
+
+ Select Walnut if you have an IBM 405GP "Walnut" Evaluation Board.
+
+ More information on these boards is available at:
+ <http://www.chips.ibm.com/products/powerpc/tools/evk_pn.html#GCX>.
+
+Walnut
+CONFIG_WALNUT
+ Select Walnut if you have an IBM 405GP "Walnut" Evaluation Board.
+
Workarounds for PPC601 bugs
CONFIG_PPC601_SYNC_FIX
Some versions of the PPC601 (the first PowerPC chip) have bugs which
- mean that extra synchronization instructions are required near certain
- instructions, typically those that make major changes to the CPU state.
- These extra instructions reduce performance slightly. If you say N
- here, these extra instructions will not be included, resulting in a
- kernel which will run faster but may not run at all on some systems
- with the PPC601 chip.
+ mean that extra synchronization instructions are required near
+ certain instructions, typically those that make major changes to the
+ CPU state. These extra instructions reduce performance slightly.
+ If you say N here, these extra instructions will not be included,
+ resulting in a kernel which will run faster but may not run at all
+ on some systems with the PPC601 chip.
+
+ If in doubt, say Y here.
+
+8xx Cache (Copy-Back or Writethrough)
+CONFIG_8xx_COPYBACK
+ Saying Y here will cause the cache on an MPC8xx processor to be used
+ in Copy-Back mode. If you say N here, it is used in Writethrough
+ mode.
+
+ If in doubt, say Y here.
+
+MPC860 (Pre Rev. C) CPU6 Silicon Errata
+CONFIG_8xx_CPU6
+ MPC860 CPUs, prior to Rev C have some bugs in the silicon, which
+ require workarounds for Linux (and most other OSes to work). If you
+ get a BUG() very early in boot, this might fix the problem. For
+ more details read the document entitled "MPC860 Family Device Errata
+ Reference" on Motorola's website. This option also incurs a
+ performance hit.
+
+ If in doubt, say N here.
+
+MPC8xx IDE support
+CONFIG_BLK_DEV_MPC8xx_IDE
+ This option provides support for IDE on Motorola MPC8xx Systems.
+ Please see 'Type of MPC8xx IDE interface' for details.
+
+ If unsure, say N.
+
+Type of MPC8xx IDE interface
+CONFIG_IDE_8xx_PCCARD
+ Select how the IDE devices are connected to the MPC8xx system:
+
+ 8xx_PCCARD uses the 8xx internal PCMCIA interface in combination
+ with a PC Card (e.g. ARGOSY portable Hard Disk Adapter),
+ ATA PC Card HDDs or ATA PC Flash Cards (example: TQM8xxL
+ systems)
+
+ 8xx_DIRECT is used for directly connected IDE devices using the 8xx
+ internal PCMCIA interface (example: IVMS8 systems)
+
+ EXT_DIRECT is used for IDE devices directly connected to the 8xx
+ bus using some glue logic, but _not_ the 8xx internal
+ PCMCIA interface (example: IDIF860 systems)
+
+Use SMC2 for UART
+CONFIG_SMC2_UART
+ If you would like to use SMC2 as a serial port, say Y here.
If in doubt, say Y here.
+Use SMC2 for Console
+CONFIG_CONS_SMC2
+ If you are going to have a serial console on your device and are
+ using SMC2 for your serial port, say Y here, else say N.
+
+Use the alternate SMC2 I/O
+CONFIG_ALTSMC2
+ If you have an MPC823 or MPC850 and would like to use the alternate
+ SMC2 for I/O, say Y here.
+
+ If in doubt, say N here.
+
+Enable SCC2 and SCC3 for UART
+CONFIG_USE_SCC_IO
+ If your MPC8xx board has other SCC ports that you would like to use
+ for for a serial port, say Y here.
+
+ If in doubt, say N here.
+
+# Choice: ppc6xxtype
Machine Type
CONFIG_ALL_PPC
Linux currently supports several different kinds of PowerPC-based
@@ -17522,7 +20474,28 @@
and some IBM RS/6000 systems), CHRP (Common Hardware Reference
Platform), and several embedded PowerPC systems containing 4xx, 6xx,
7xx, 8xx, 74xx, and 82xx processors. Currently, the default option
- is to build a kernel which works on the first three.
+ is to build a kernel which works on the first three.
+
+ Select PowerMac/PReP/MTX/CHRP if configuring for any of the above.
+
+ Select Gemini if configuring for a Synergy Microsystems' Gemini
+ series Single Board Computer. More information is available at:
+ <http://www.synergymicro.com/PressRel/97_10_15.html>.
+
+ Select APUS if configuring for a PowerUP Amiga. More information is
+ available at: <http://linux-apus.sourceforge.net>.
+
+Synergy-Gemini
+CONFIG_GEMINI
+ Select Gemini if configuring for a Synergy Microsystems' Gemini
+ series Single Board Computer. More information is available at:
+ <http://www.synergymicro.com/PressRel/97_10_15.html>.
+
+Amiga-Apus
+CONFIG_APUS
+ Select APUS if configuring for a PowerUP Amiga.
+ More information is available at:
+ <http://linux-apus.sourceforge.net>.
Embedded 8xx Board Type
CONFIG_RPXLITE
@@ -17646,7 +20619,7 @@
altivec registers, and turning on the 'altivec enable' bit so user
processes can execute altivec instructions.
- This option is only usefully if you have a processor that supports
+ This option is only usefully if you have a processor that supports
altivec (G4, otherwise known as 74xx series), but does not have
any affect on a non-altivec cpu (it does, however add code to the
kernel).
@@ -17657,7 +20630,7 @@
CONFIG_TAU
G3 and G4 processors have an on-chip temperature sensor called the
'Thermal Assist Unit (TAU)', which, in theory, can measure the on-die
- temperature within 2-4 degrees celcius. This option shows the current
+ temperature within 2-4 degrees Celsius. This option shows the current
on-die temperature in /proc/cpuinfo if the cpu supports it.
Unfortunately, on some chip revisions, this sensor is very inaccurate
@@ -17681,26 +20654,10 @@
Average high and low temp
CONFIG_TAU_AVERAGE
The TAU hardware can compare the temperature to an upper and lower bound.
- The default behavior is to show both the upper and lower bound in
+ The default behavior is to show both the upper and lower bound in
/proc/cpuinfo. If the range is large, the temperature is either changing
- a lot, or the TAU hardware is broken (likely on some G4's). If the range
- is small (around 4 degrees), the temperature is relatively stable.
-
-Support for CUDA based PowerMacs
-CONFIG_ADB_CUDA
- This provides support for CUDA based Power Macintosh systems. This
- includes most OldWorld PowerMacs, the first generation iMacs, the
- Blue&White G3 and the Yikes G4 (PCI Graphics). All later models
- should use CONFIG_ADB_PMU instead.
-
- If unsure say Y.
-
-Support for PMU based PowerMacs
-CONFIG_ADB_PMU
- This provides support for PMU based Power Macintosh systems. This
- includes all PowerBooks and all AGP-based machines.
-
- If unsure say Y.
+ a lot, or the TAU hardware is broken (likely on some G4's). If the range
+ is small (around 4 degrees), the temperature is relatively stable.
Power management support for PowerBooks
CONFIG_PMAC_PBOOK
@@ -17710,7 +20667,7 @@
must get the power management daemon, pmud, to make it work and you
must have the /dev/pmu device (see the pmud README).
- Get pmud from ftp://linuxcare.com.au/pub/ppclinux/pmud/
+ Get pmud from <ftp://ftp.samba.org/pub/ppclinux/pmud/>.
If you have a PowerBook, you should say Y.
@@ -17718,33 +20675,218 @@
have it autoloaded. The act of removing the module shuts down the
sound hardware for more power savings.
+Backlight control for LCD screens
+CONFIG_PMAC_BACKLIGHT
+ Say Y here to build in code to manage the LCD backlight on a
+ Macintosh PowerBook. With this code, the backlight will be turned
+ on and off appropriately on power-management and lid-open/lid-closed
+ events; also, the PowerBook button device will be enabled so you can
+ change the screen brightness.
+
+# Choice: ppc8xxtype
+RPX-Lite
+CONFIG_RPXLITE
+ Single-board computers based around the PowerPC MPC8xx chips and
+ intended for embedded applications. The following types are
+ supported:
+
+ RPX-Lite -- PC104 form-factor SBC based on the MPC823
+ RPX-Classic -- Credit-card-size SBC based on the MPC 860
+ BSE-IP -- Bright Star Engineering BSE-IP SBC
+ TQM823L -- TQM823L SBC from TQ Components
+ TQM850L -- TQM850L SBC from TQ Components
+ TQM855L -- TQM855L SBC from TQ Components
+ TQM860L -- TQM860L SBC from TQ Components
+ FPS850L -- FingerPrint Sensor from TQ Components
+ TQM860 -- TQM860 SBC from IKENDI AG
+ SPD823TS -- Speech Design TeleServer from Speech Design
+ IVMS8 -- Integrated VoiceMail SBC from Speech Design
+ SM850 -- Service Module 850 from Dependable Computer Systems
+ MBX -- MBX821 and MBX860 SBCs
+ Wincept -- Wincept SBCs for thin-client machines
+
+RPX-Classic
+CONFIG_RPXCLASSIC
+ The RPX-Classic is a single-board computer based on the Motorola
+ MPC860. It features 16MB of DRAM and a variable amount of flash,
+ I2C EEPROM, thermal monitoring, a PCMCIA slot, a DIP switch and two
+ LEDs. Variants with Ethernet ports exist. Say Y here to support it
+ directly.
+
+BSE-IP
+CONFIG_BSEIP
+ Say Y here to support the Bright Star Engineering ipEngine SBC.
+ This is a credit-card-sized device featuring a MPC823 processor,
+ 26MB DRAM, 4MB flash, Ethernet, a 16K-gate FPGA, USB, an LCD/video
+ controller, and two RS232 ports.
+
+TQM823L
+CONFIG_TQM823L
+ Say Y here to support the TQM823L, one of an MPC8xx-based family of
+ mini SBCs (half credit-card size) from TQ Components first released
+ in late 1999. Technical references are at
+ <http://www.denx.de/PDF/TQM8xxLHWM201.pdf>, and
+ <http://www.denx.de/PDF/STK8xxLHWM201.pdf>, and an image at
+ <http://www.denx.de/embedded-ppc-en.html>.
+
+TQM850L
+CONFIG_TQM850L
+ Say Y here to support the TQM850L, one of an MPC8xx-based family of
+ mini SBCs (half credit-card size) from TQ Components first released
+ in late 1999. Technical references are at
+ <http://www.denx.de/PDF/TQM8xxLHWM201.pdf>, and
+ <http://www.denx.de/PDF/STK8xxLHWM201.pdf>, and an image at
+ <http://www.denx.de/embedded-ppc-en.html>.
+
+TQM855L
+CONFIG_TQM855L
+ Say Y here to support the TQM855L, one of an MPC8xx-based family of
+ mini SBCs (half credit-card size) from TQ Components first released
+ in late 1999. Technical references are at
+ <http://www.denx.de/PDF/TQM8xxLHWM201.pdf>, and
+ <http://www.denx.de/PDF/STK8xxLHWM201.pdf>, and an image at
+ <http://www.denx.de/embedded-ppc-en.html>.
+
+TQM860L
+CONFIG_TQM860L
+ Say Y here to support the TQM860L, one of an MPC8xx-based family of
+ mini SBCs (half credit-card size) from TQ Components first released
+ in late 1999. Technical references are at
+ <http://www.denx.de/PDF/TQM8xxLHWM201.pdf>, and
+ <http://www.denx.de/PDF/STK8xxLHWM201.pdf>, and an image at
+ <http://www.denx.de/embedded-ppc-en.html>.
+
+FPS850
+CONFIG_FPS850
+ Say Y here to support the FingerPrint Sensor from AKENDI IG, based
+ on the TQ Components TQM850L module, released November 1999 and
+ discontinued a year later.
+
+TQM860
+CONFIG_TQM860
+ Say Y here to support the TQM860, one of an MPC8xx-based family of
+ SBCs (credit-card size) from TQ Components first released in
+ mid-1999 and discontinued mid-2000.
+
+SM850
+CONFIG_SM850
+ Say Y here to support the Service Module 850 from Dependable
+ Computer Systems, an SBC based on the TQM850L module by TQ
+ Components. This board is no longer in production. The
+ manufacturer's website is at <http://www.decomsys.com/>.
+
+SPD823TS
+CONFIG_SPD823TS
+ Say Y here to support the Speech Design 823 Tele-Server from Speech
+ Design, released in 2000. The manufacturer's website is at
+ <http://www.speech-design.de/>.
+
+IVMS8
+CONFIG_IVMS8
+ Say Y here to support the Integrated Voice-Mail Small 8-channel SBC
+ from Speech Design, released March 2001. The manufacturer's website
+ is at <http://www.speech-design.de/>.
+
+# IVML24 is not yet active
+IVML24
+CONFIG_IVML24
+ Say Y here to support the Integrated Voice-Mail Large 24-channel SBC
+ from Speech Design, released March 2001. The manufacturer's website
+ is at <http://www.speech-design.de/>.
+
+MBX
+CONFIG_MBX
+ MBX is a line of Motorola single-board computer based around the
+ MPC821 and MPC860 processors, and intended for embedded-controller
+ applications. Say Y here to support these boards directly.
+
+WinCept
+CONFIG_WINCEPT
+ The Wincept 100/110 is a Motorola single-board computer based on the
+ MPC821 PowerPC, introduced in 1998 and designed to be used in
+ thin-client machines. Say Y to support it directly.
+
+# More systems that will be supported soon, according to
+# Wolfgang Denk <wd@denx.de>:
+#
+# TQM8260:
+# MPC8260 based module
+#
+# Manufacturer: TQ Components, www.tq-group.de
+# Date of Release: June 2001
+# End of Life: not yet :-)
+# URL: <http://www.denx.de/PDF/TQM82xx_SPEC_Rev003.pdf>
+#
+# IP860:
+# VMEBus IP (Industry Pack) carrier board with MPC860
+#
+# Manufacturer: MicroSys GmbH, <http://www.microsys.de/>
+# Date of Release: ?
+# End of life: -
+# URL: <http://www.microsys.de/html/ip860.html>
+#
+# CU824:
+# VMEBus Board with PCI extension with MPC8240 CPU
+#
+# Manufacturer: MicroSys GmbH, <http://www.microsys.de/>
+# Date of Release: early 2001 (?)
+# End of life: -
+# URL: <http://www.microsys.de/html/cu824.html
+#
+# PM826:
+# Modular system with MPC8260 CPU
+#
+# Manufacturer: MicroSys GmbH, <http://www.microsys.de/>
+# Date of Release: mid 2001
+# End of life: -
+# URL: <http://www.microsys.de/html/pm826.html>
+#
+# PCU_E:
+# PCU = Peripheral Controller Unit; E = extended (?)
+#
+# Mfr: Siemens AG, ICN (Information and Communication Networks)
+# <http://www.siemens.de/page/1,3771,224315-1-999_2_226207-0,00.html>
+# Date of Release: April 2001
+# End of life: -
+# URL: n. a.o
+
+Support for EST8260
+CONFIG_EST8260
+ The EST8260 is a single-board computer manufactured by Wind River
+ Systems, Inc. (formerly Embedded Support Tools Corp.) and based on
+ the MPC8260. Wind River Systems has a website at
+ <http://www.windriver.com/>, but the EST8260 cannot be found on it
+ and has probably been discontinued or rebadged.
+
ADB raw keycode support
CONFIG_MAC_ADBKEYCODES
This provides support for sending raw ADB keycodes to console
devices. This is the default up to 2.4.0, but in future this may be
- phased out in favor of generic Linux keycodes. If you say Y here, you
- can dynamically switch via the
+ phased out in favor of generic Linux keycodes. If you say Y here,
+ you can dynamically switch via the
/proc/sys/dev/mac_hid/keyboard_sends_linux_keycodes
- sysctl and with the "keyboard_sends_linux_keycodes=" kernel argument.
-
+ sysctl and with the "keyboard_sends_linux_keycodes=" kernel
+ argument.
+
If unsure, say Y here.
Mouse button 2+3 emulation support
CONFIG_MAC_EMUMOUSEBTN
This provides generic support for emulating the 2nd and 3rd mouse
- button with keypresses. If you say Y here, the emulation is still
- disabled by default. The emulation is controlled by these sysctl entries:
+ button with keypresses. If you say Y here, the emulation is still
+ disabled by default. The emulation is controlled by these sysctl
+ entries:
/proc/sys/dev/mac_hid/mouse_button_emulation
/proc/sys/dev/mac_hid/mouse_button2_keycode
/proc/sys/dev/mac_hid/mouse_button3_keycode
-Enhanced Real Time Clock Support
+Enhanced Real Time Clock Support (/dev/rtc)
CONFIG_PPC_RTC
If you say Y here and create a character special file /dev/rtc with
major number 10 and minor number 135 using mknod ("man mknod"), you
- will get access to the real time clock (or hardware clock) built
+ will get access to the real time clock (or hardware clock) built
into your computer.
-
+
If unsure, say Y here.
Support for Open Firmware device tree in /proc
@@ -17753,27 +20895,27 @@
an image of the device tree that the kernel copies from Open
Firmware. If unsure, say Y here.
-RTAS proc interface
+RTAS (RunTime Abstraction Services) in /proc
CONFIG_PPC_RTAS
When you use this option, you will be able to use RTAS from
- userspace.
-
+ userspace.
+
RTAS stands for RunTime Abstraction Services and should
provide a portable way to access and set system information. This is
- commonly used on RS/6000 (pSeries) computers.
-
- You can access RTAS via the special proc filesystem entry rtas.
+ commonly used on RS/6000 (pSeries) computers.
+
+ You can access RTAS via the special proc file system entry rtas.
Don't confuse this rtas entry with the one in /proc/device-tree/rtas
which is readonly.
-
+
If you don't know if you can use RTAS look into
/proc/device-tree/rtas. If there are some entries, it is very likely
that you will be able to use RTAS.
You can do cool things with rtas. To print out information about
- various sensors in the system, just do a
+ various sensors in the system, just do a
- $ cat /proc/rtas/sensors
+ $ cat /proc/rtas/sensors
or if you power off your machine at night but want it running when
you enter your office at 7:45 am, do a
@@ -17782,7 +20924,7 @@
and shutdown.
- If unsure, say Y
+ If unsure, say Y.
MESH (Power Mac internal SCSI) support
CONFIG_SCSI_MESH
@@ -17792,9 +20934,9 @@
adaptor. This driver is also available as a module called mesh.o
( = code which can be inserted in and removed from the running
kernel whenever you want). If you want to compile it as a module,
- say M here and read Documentation/modules.txt.
+ say M here and read <file:Documentation/modules.txt>.
-Maximum synchronous transfer rate
+Maximum synchronous transfer rate (MB/s) (0 = async)
CONFIG_SCSI_MESH_SYNC_RATE
On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
drives a bus which is entirely internal to the machine (such as the
@@ -17810,12 +20952,12 @@
On Power Macintoshes (and clones) with two SCSI buses, the external
SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
machines which only have one SCSI bus, such as the 7200, also use
- the 53C94. Say Y to include support for the 53C94.
+ the 53C94. Say Y to include support for the 53C94.
This driver is also available as a module called mac53c94.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
MACE (Power Mac Ethernet) support
CONFIG_MACE
@@ -17826,7 +20968,7 @@
This driver is also available as a module called mace.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
Use AAUI port instead of TP by default
CONFIG_MACE_AAUI_PORT
@@ -17835,53 +20977,52 @@
instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
Y here if you have such a machine. If unsure, say N.
The driver will default to AAUI on ANS anyway, and if you use it as
- a module, you can provide the port_aaui=0|1 to force the driver
- setting.
+ a module, you can provide the port_aaui=0|1 to force the driver.
-BMAC (G3 ethernet) support
+BMAC (G3 Ethernet) support
CONFIG_BMAC
Say Y for support of BMAC Ethernet interfaces. These are used on G3
- computers.
+ computers.
This driver is also available as a module called bmac.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
-GMAC (G4/iBook ethernet) support
+GMAC (G4/iBook Ethernet) support
CONFIG_GMAC
Say Y for support of GMAC Ethernet interfaces. These are used on G4
- and iBook computers.
+ and iBook computers.
This driver is also available as a module called gmac.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
-National DP83902AV (Oak ethernet) support
+National DP83902AV (Oak Ethernet) support
CONFIG_OAKNET
Say Y if your machine has this type of Ethernet network card.
This driver is also available as a module called oaknet.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
Video For Linux
CONFIG_VIDEO_DEV
Support for audio/video capture and overlay devices and FM radio
cards. The exact capabilities of each device vary. User tools for
this are available from
- ftp://ftp.uk.linux.org/pub/linux/video4linux .
+ <ftp://ftp.uk.linux.org/pub/linux/video4linux>.
If you are interested in writing a driver for such an audio/video
device or user software interacting with such a driver, please read
- the file Documentation/video4linux/API.html.
+ the file <file:Documentation/video4linux/API.html>.
This driver is also available as a module called videodev.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
Video For Linux /proc file system information
CONFIG_VIDEO_PROC_FS
@@ -17897,122 +21038,121 @@
in the port address below.
Note that newer AIMSlab RadioTrack cards have a different chipset
- and are not supported by this driver. For these cards, use the
+ and are not supported by this driver. For these cards, use the
RadioTrack II driver below.
If you have a GemTeks combined (PnP) sound- and radio card you must
- use this driver as a module and setup the card with isapnptools. You
- must also pass the module a suitable io parameter, 0x248 has been
- reported to be used by these cards.
+ use this driver as a module and setup the card with isapnptools.
+ You must also pass the module a suitable io parameter, 0x248 has
+ been reported to be used by these cards.
In order to control your radio card, you will need to use programs
- that are compatible with the Video for Linux API. Information on
+ that are compatible with the Video For Linux API. Information on
this API and pointers to "v4l" programs may be found on the WWW at
- http://roadrunner.swansea.uk.linux.org/v4l.shtml . More information
- is contained in the file Documentation/video4linux/radiotrack.txt.
+ <http://roadrunner.swansea.uk.linux.org/v4l.shtml>. More
+ information is contained in the file
+ <file:Documentation/video4linux/radiotrack.txt>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called radio-aimslab.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called radio-aimslab.o.
-RadioTrack i/o port
+RadioTrack I/O port
CONFIG_RADIO_RTRACK_PORT
- Enter either 0x30f or 0x20f here. The card default is 0x30f, if you
+ Enter either 0x30f or 0x20f here. The card default is 0x30f, if you
haven't changed the jumper setting on the card.
AIMSlab RadioTrack II support
CONFIG_RADIO_RTRACK2
- Choose Y here if you have this FM radio card, and then fill in the
+ Choose Y here if you have this FM radio card, and then fill in the
port address below.
In order to control your radio card, you will need to use programs
- that are compatible with the Video for Linux API. Information on
+ that are compatible with the Video For Linux API. Information on
this API and pointers to "v4l" programs may be found on the WWW at
- http://roadrunner.swansea.uk.linux.org/v4l.shtml .
+ <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called radio-rtrack2.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called radio-rtrack2.o.
-RadioTrack II i/o port
+RadioTrack II I/O port
CONFIG_RADIO_RTRACK2_PORT
- Enter either 0x30c or 0x20c here. The card default is 0x30c, if you
+ Enter either 0x30c or 0x20c here. The card default is 0x30c, if you
haven't changed the jumper setting on the card.
Aztech/Packard Bell Radio
CONFIG_RADIO_AZTECH
Choose Y here if you have one of these FM radio cards, and then fill
in the port address below.
-
+
In order to control your radio card, you will need to use programs
- that are compatible with the Video for Linux API. Information on
+ that are compatible with the Video For Linux API. Information on
this API and pointers to "v4l" programs may be found on the WWW at
- http://roadrunner.swansea.uk.linux.org/v4l.shtml .
+ <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called radio-aztech.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called radio-aztech.o.
-Aztech/Packard Bell radio card i/o port
+Aztech/Packard Bell radio card I/O port
CONFIG_RADIO_AZTECH_PORT
- Enter either 0x350 or 0x358 here. The card default is 0x350, if you
- haven't changed the setting of jumper JP3 on the card. Removing the
+ Enter either 0x350 or 0x358 here. The card default is 0x350, if you
+ haven't changed the setting of jumper JP3 on the card. Removing the
jumper sets the card to 0x358.
ADS Cadet AM/FM Radio Tuner Card
CONFIG_RADIO_CADET
Choose Y here if you have one of these AM/FM radio cards, and then
fill in the port address below.
-
+
In order to control your radio card, you will need to use programs
- that are compatible with the Video for Linux API. Information on
+ that are compatible with the Video For Linux API. Information on
this API and pointers to "v4l" programs may be found on the WWW at
- http://roadrunner.swansea.uk.linux.org/v4l.shtml .
+ <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
Further documentation on this driver can be found on the WWW at
- http://linux.blackhawke.net/cadet.html .
+ <http://linux.blackhawke.net/cadet.html>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called radio-cadet.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called radio-cadet.o.
SF16FMI Radio
CONFIG_RADIO_SF16FMI
- Choose Y here if you have one of these FM radio cards, and then fill
- in the port address below.
+ Choose Y here if you have one of these FM radio cards. If you
+ compile the driver into the kernel and your card is not PnP one, you
+ have to add "sf16fm=<io>" to the kernel command line (I/O address is
+ 0x284 or 0x384).
In order to control your radio card, you will need to use programs
- that are compatible with the Video for Linux API. Information on
+ that are compatible with the Video For Linux API. Information on
this API and pointers to "v4l" programs may be found on the WWW at
- http://roadrunner.swansea.uk.linux.org/v4l.shtml .
+ <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called radio-sf16fmi.o
-
-SF16FMI I/O port (0x284 or 0x384)
-CONFIG_RADIO_SF16FMI_PORT
- Enter the I/O port of your SF16FMI radio card.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called radio-sf16fmi.o.
-Typhoon Radio
+Typhoon Radio (a.k.a. EcoRadio)
CONFIG_RADIO_TYPHOON
Choose Y here if you have one of these FM radio cards, and then fill
in the port address and the frequency used for muting below.
In order to control your radio card, you will need to use programs
- that are compatible with the Video for Linux API. Information on
+ that are compatible with the Video For Linux API. Information on
this API and pointers to "v4l" programs may be found on the WWW at
- http://roadrunner.swansea.uk.linux.org/v4l.shtml .
+ <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called radio-typhoon.o
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called radio-typhoon.o.
Support for /proc/radio-typhoon
CONFIG_RADIO_TYPHOON_PROC_FS
@@ -18041,88 +21181,132 @@
in the port address below.
In order to control your radio card, you will need to use programs
- that are compatible with the Video for Linux API. Information on
+ that are compatible with the Video For Linux API. Information on
this API and pointers to "v4l" programs may be found on the WWW at
- http://roadrunner.swansea.uk.linux.org/v4l.shtml .
+ <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called radio-zoltrix.o
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called radio-zoltrix.o.
ZOLTRIX I/O port (0x20c or 0x30c)
CONFIG_RADIO_ZOLTRIX_PORT
Enter the I/O port of your Zoltrix radio card.
-IIC on parallel port
+I2C on parallel port
CONFIG_I2C_PARPORT
I2C is a simple serial bus system used in many micro controller
- applications. Saying Y here will allow you to use your parallel port
- as an I2C interface.
+ applications. Saying Y here will allow you to use your parallel
+ port as an I2C interface.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called i2c-parport.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called i2c-parport.o.
miroSOUND PCM20 radio
CONFIG_RADIO_MIROPCM20
- Choose Y here if you have this sound card. You also need to say Y
+ Choose Y here if you have this FM radio card. You also need to say Y
to "ACI mixer (miroSOUND PCM1-pro/PCM12/PCM20 radio)" (in "Sound")
for this to work.
In order to control your radio card, you will need to use programs
- that are compatible with the Video for Linux API. Information on
+ that are compatible with the Video For Linux API. Information on
this API and pointers to "v4l" programs may be found on the WWW at
- http://roadrunner.swansea.uk.linux.org/v4l.shtml .
+ <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called miropcm20.o
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called miropcm20.o.
miroSOUND PCM20 radio RDS user interface (EXPERIMENTAL)
CONFIG_RADIO_MIROPCM20_RDS
- Choose Y here if you want to see RDS/RBDS information like RadioText,
- Programme Service name, Clock Time and date, Programme TYpe and
- Traffic Announcement/Programme identification. You also need to say
- Y to "miroSOUND PCM20 radio" and devfs!
+ Choose Y here if you want to see RDS/RBDS information like
+ RadioText, Programme Service name, Clock Time and date, Programme
+ TYpe and Traffic Announcement/Programme identification. You also
+ need to say Y to "miroSOUND PCM20 radio" and devfs!
It's not possible to read the raw RDS packets from the device, so
- the driver cant provide an V4L interface for this. But the
- availability of RDS is reported over V4L by the basic driver already.
- Here RDS can be read from files in /dev/v4l/rds.
+ the driver cant provide an V4L interface for this. But the
+ availability of RDS is reported over V4L by the basic driver
+ already. Here RDS can be read from files in /dev/v4l/rds.
As module the driver will be called miropcm20-rds.o.
-GemTek Radio Card
+Maestro on board radio
+CONFIG_RADIO_MAESTRO
+ Say Y here to directly support the on-board radio tuner on the
+ Maestro 2 or 2E sound card.
+
+ In order to control your radio card, you will need to use programs
+ that are compatible with the Video For Linux API. Information on
+ this API and pointers to "v4l" programs may be found on the WWW at
+ <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
+
+ If you want to compile this driver as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want),
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called radio-maestro.o.
+
+Guillemot MAXI Radio FM 2000 Radio Card
+CONFIG_RADIO_MAXIRADIO
+ Choose Y here if you have this radio card. This card may also be
+ found as Gemtek PCI FM.
+
+ In order to control your radio card, you will need to use programs
+ that are compatible with the Video For Linux API. Information on
+ this API and pointers to "v4l" programs may be found on the WWW at
+ <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
+
+ If you want to compile this driver as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want),
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called radio-maxiradio.o.
+
+GemTek Radio Card support
CONFIG_RADIO_GEMTEK
- Choose Y here if you have this FM radio card, and then fill in the
+ Choose Y here if you have this FM radio card, and then fill in the
port address below.
In order to control your radio card, you will need to use programs
- that are compatible with the Video for Linux API. Information on
+ that are compatible with the Video For Linux API. Information on
this API and pointers to "v4l" programs may be found on the WWW at
- http://roadrunner.swansea.uk.linux.org/v4l.shtml .
+ <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called radio-gemtek.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called radio-gemtek.o.
-GemTek i/o port
+GemTek I/O port
CONFIG_RADIO_GEMTEK_PORT
Enter either 0x20c, 0x30c, 0x24c or 0x34c here. The card default is
0x34c, if you haven't changed the jumper setting on the card. On
- Sound Vision 16 Gold PnP with FM Radio (ESS1869+FM Gemtek), the i/o
+ Sound Vision 16 Gold PnP with FM Radio (ESS1869+FM Gemtek), the I/O
port is 0x28c.
+Gemtek PCI Radio
+CONFIG_RADIO_GEMTEK_PCI
+ Choose Y here if you have this PCI FM radio card.
+
+ In order to control your radio card, you will need to use programs
+ that are compatible with the Video for Linux API. Information on
+ this API and pointers to "v4l" programs may be found on the WWW at
+ <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
+
+ If you want to compile this driver as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want),
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called radio-gemtek-pci.o.
+
PlanB Video-In for PowerMacs
CONFIG_VIDEO_PLANB
PlanB is the V4L driver for the PowerMac 7x00/8x00 series video
input hardware. If you want to experiment with this, say Y.
Otherwise, or if you don't understand a word, say N.
- See http://www.cpu.lu/~mlan/planb.html for more info.
+ See <http://www.cpu.lu/~mlan/planb.html> for more info.
Saying M will compile this driver as a module (planb.o).
@@ -18131,34 +21315,27 @@
Choose Y here if you have this FM radio card, and then fill in the
port address below. (TODO)
- Note: This driver is in its early stages. Right now volume and
+ Note: This driver is in its early stages. Right now volume and
frequency control and muting works at least for me, but
- unfortunately i have not found anybody who wants to use this card
- with Linux. So if it is this what YOU are trying to do right now,
- PLEASE DROP ME A NOTE!! Rolf Offermanns (rolf@offermanns.de)
-
+ unfortunately I have not found anybody who wants to use this card
+ with Linux. So if it is this what YOU are trying to do right now,
+ PLEASE DROP ME A NOTE!! Rolf Offermanns (rolf@offermanns.de)
+
In order to control your radio card, you will need to use programs
- that are compatible with the Video for Linux API. Information on
+ that are compatible with the Video For Linux API. Information on
this API and pointers to "v4l" programs may be found on the WWW at
- http://roadrunner.swansea.uk.linux.org/v4l.shtml .
+ <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
- say M here and read Documentation/modules.txt. The module will be
- called radio-terratec.o.
+ say M here and read <file:Documentation/modules.txt>. The module
+ will be called radio-terratec.o.
-Terratec i/o port (normally 0x590)
+Terratec I/O port (normally 0x590)
CONFIG_RADIO_TERRATEC_PORT
- Fill in the i/o port of your TerraTec FM radio card. If unsure, go
+ Fill in the I/O port of your TerraTec FM radio card. If unsure, go
with the default.
-### Add these
-# Zoran ZR36057/36060 support
-# CONFIG_VIDEO_ZORAN
-
-# Include support for Iomega Buz
-# CONFIG_VIDEO_BUZ
-
Trust FM radio card
CONFIG_RADIO_TRUST
This is a driver for the Trust FM radio cards. Say Y if you have
@@ -18167,38 +21344,76 @@
This driver is also available as a module called radio-trust.o ( =
code which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
-Trust i/o port (usually 0x350 or 0x358)
+Trust I/O port (usually 0x350 or 0x358)
CONFIG_RADIO_TRUST_PORT
- Enter the i/o port of your Trust FM radio card. If unsure, try the
+ Enter the I/O port of your Trust FM radio card. If unsure, try the
values "0x350" or "0x358".
BT848 Video For Linux
CONFIG_VIDEO_BT848
Support for BT848 based frame grabber/overlay boards. This includes
the Miro, Hauppauge and STB boards. Please read the material in
- Documentation/video4linux/bttv for more information.
+ <file:Documentation/video4linux/bttv> for more information.
If you say Y or M here, you need to say Y or M to "I2C support" and
"I2C bit-banging interfaces" in the character device section.
-
+
This driver is available as a module called bttv.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
+
+BT878 Audio DMA
+CONFIG_SOUND_BT878
+ Audio DMA support for bt878 based grabber boards. As you might have
+ already noticed, bt878 is listed with two functions in /proc/pci.
+ Function 0 does the video stuff (bt848 compatible), function 1 does
+ the same for audio data. This is a driver for the audio part of
+ the chip. If you say 'Y' here you get a oss-compatible dsp device
+ where you can record from. If you want just watch TV you probably
+ don't need this driver as most TV cards handle sound with a short
+ cable from the TV card to your sound card's line-in.
+
+ This driver is available as a module called btaudio.o ( = code
+ which can be inserted in and removed from the running kernel
+ whenever you want). If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>.
+
+SGI Vino Video For Linux
+CONFIG_VIDEO_VINO
+ Say Y here to build in support for the Vino video input system found
+ on SGI Indy machines.
+
+Stradis 4:2:2 MPEG-2 video driver
+CONFIG_VIDEO_STRADIS
+ Say Y here to enable support for the Stradis 4:2:2 MPEG-2 video
+ driver for PCI. There is a product page at
+ <http://www.stradis.com/decoder.html>.
+
+Zoran ZR36057/36060 Video For Linux
+CONFIG_VIDEO_ZORAN
+ Say Y here to include support for video cards based on the Zoran
+ ZR36057/36060 encoder/decoder chip (including the Iomega Buz and the
+ Miro DC10 and DC30 video capture cards).
+
+Include support for Iomega Buz
+CONFIG_VIDEO_BUZ
+ Say Y here to include support for the Iomega Buz video card. There
+ is a Buz/Linux homepage at <http://www.lysator.liu.se/~gz/buz/>.
-ZR36120/36125 Video for Linux
+Zoran ZR36120/36125 Video For Linux
CONFIG_VIDEO_ZR36120
Support for ZR36120/ZR36125 based frame grabber/overlay boards.
This includes the Victor II, WaveWatcher, Video Wonder, Maxi-TV,
and Buster boards. Please read the material in
- Documentation/video4linux/zr36120.txt for more information.
+ <file:Documentation/video4linux/zr36120.txt> for more information.
This driver is also available as a module called zr36120.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
SAA5249 Teletext processor
CONFIG_VIDEO_SAA5249
@@ -18208,26 +21423,37 @@
This driver is also available as a module called saa5249.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
-Quickcam BW Video For Linux
+QuickCam BW Video For Linux
CONFIG_VIDEO_BWQCAM
Say Y have if you the black and white version of the QuickCam
- camera. See the next option for the color version.
+ camera. See the next option for the color version.
This driver is also available as a module called bw-qcam.o ( = code
which can be inserted in and removed from the running kernel
whenever you want). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ here and read <file:Documentation/modules.txt>.
-Colour QuickCam Video For Linux
+QuickCam Colour Video For Linux
CONFIG_VIDEO_CQCAM
This is the video4linux driver for the colour version of the
- Connectix Quickcam. If you have one of these cameras, say Y here,
- otherwise say N. This driver does not work with the original
- monochrome Quickcam, Quickcam VC or QuickClip. It is also available
- as a module (c-qcam.o). Read Documentation/video4linux/CQcam.txt for
- more information.
+ Connectix QuickCam. If you have one of these cameras, say Y here,
+ otherwise say N. This driver does not work with the original
+ monochrome QuickCam, QuickCam VC or QuickClip. It is also available
+ as a module (c-qcam.o).
+ Read <file:Documentation/video4linux/CQcam.txt> for more information.
+
+Winbond W9966CF Webcam Video For Linux
+CONFIG_VIDEO_W9966
+ Video4linux driver for Winbond's w9966 based Webcams.
+ Currently tested with the LifeView FlyCam Supra.
+ If you have one of these cameras, say Y here
+ otherwise say N.
+ This driver is also available as a module (w9966.o).
+
+ Check out <file:Documentation/video4linux/w9966.txt> and
+ <file:Documentation/video4linux/w9966.c> for more information.
CPiA Video For Linux
CONFIG_VIDEO_CPIA
@@ -18236,10 +21462,10 @@
Blaster Webcam II. If you have one of these cameras, say Y here
and select parallel port and/or USB lowlevel support below,
otherwise say N. This will not work with the Creative Webcam III.
-
- Please read Documentation/video4linux/README.cpia for more
+
+ Please read <file:Documentation/video4linux/README.cpia> for more
information.
-
+
This driver is also available as a module (cpia.o).
CPiA Parallel Port Lowlevel Support
@@ -18260,11 +21486,13 @@
Mediavision Pro Movie Studio Video For Linux
CONFIG_VIDEO_PMS
- Say Y if you have such a thing. This driver is also available as a
+ Say Y if you have such a thing. This driver is also available as a
module called pms.o ( = code which can be inserted in and removed
- from the running kernel whenever you want). If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ from the running kernel whenever you want). If you want to compile
+ it as a module, say M here and read
+ <file:Documentation/modules.txt>.
+Sony Vaio Picturebook Motion Eye Video for Linux
CONFIG_VIDEO_MEYE
This is the video4linux driver for the Motion Eye camera found
in the Vaio Picturebook laptops. Please read the material in
@@ -18285,20 +21513,20 @@
s390-compiler released by IBM (based on gcc-2.95.1) before.
Merge some code into the kernel to make the image IPLable
-CONFIG_IPLABLE
+CONFIG_IPL
If you want to use the produced kernel to IPL directly from a
device, you have to merge a bootsector specific to the device
into the first bytes of the kernel. You will have to select the
- IPL device on another question, that pops up, when you select
- CONFIG_IPLABE.
+ IPL device.
-IPL from a /390 tape unit
+# Choice: s390_ipl
+IPL from a S/390 tape unit
CONFIG_IPL_TAPE
Select this option if you want to IPL the image from a Tape.
IPL from a virtual card reader emulated by VM/ESA
CONFIG_IPL_RDR_VM
- Select this option if you are running under VM/ESA and want
+ Select this option if you are running under VM/ESA and want
to IPL the image from the emulated card reader.
IPL from a real card reader
@@ -18307,7 +21535,7 @@
card reader. Maybe you still got one and want to try. We didn't
test.
-IBMs S/390 Harddisks (DASDs)
+Support for DASD hard disks
CONFIG_DASD
Enable this option if you want to access DASDs directly utilizing
S/390s channel subsystem commands. This is necessary for running
@@ -18340,6 +21568,163 @@
CONFIG_DASD_FBA
FBA devices are currently unsupported.
+Merge some code into the kernel to make the image IPLable
+CONFIG_IPLABLE
+ If you want to use the produced kernel to IPL directly from a
+ device, you have to merge a bootsector specific to the device
+ into the first bytes of the kernel. You will have to select the
+ IPL device on another question, that pops up, when you select
+ CONFIG_IPLABE.
+
+Support for 3215 line mode terminal
+CONFIG_3215
+ Include support for IBM 3215 line-mode terminals. Can't be used
+ if 3270 console support is chosen.
+
+Support for console on 3215 line mode terminal
+CONFIG_3215_CONSOLE
+ Include support for using an IBM 3215 line-mode terminal as the
+ Linux system console. Can't be used if 3270 console support is
+ chosen.
+
+Support for 3270 line mode terminal
+CONFIG_3270
+ Include support for IBM 3270 line-mode terminals.
+
+Support for console on 3270 line mode terminal
+CONFIG_3270_CONSOLE
+ Include support for using an IBM 3270 line-mode terminal as the
+ Linux system console. Excludes using 3215s. Available only if 3270
+ support is compiled in statically.
+
+Support for HWC line mode terminal
+CONFIG_HWC
+ Include support for IBM HWC line-mode terminals.
+
+Console on HWC line mode terminal
+CONFIG_HWC_CONSOLE
+ Include support for using an IBM HWC line-mode terminal as the Linux
+ system console.
+
+S/390 tape device support
+CONFIG_S390_TAPE
+ Select this option if you want to access channel-attached tape
+ devices on IBM S/390 or zSeries.
+ If you select this option you will also want to select at
+ least one of the tape interface options and one of the tape
+ hardware options in order to access a tape device.
+ This option is also available as a module. The module will be
+ called tape390.o and include all selected interfaces and
+ hardware drivers.
+
+Support for tape character devices
+CONFIG_S390_TAPE_CHAR
+ Select this option if you want to access your channel-attached
+ tape devices using the character device interface.
+ This interface is similar to other Linux tape devices like
+ SCSI-Tapes (st) and the floppy tape device (ftape).
+ If unsure, say "Y".
+
+Support for tape block devices
+CONFIG_S390_TAPE_BLOCK
+ Select this option if you want to access your channel-attached tape
+ devices using the block device interface. This interface is similar
+ to CD-ROM devices on other platforms. The tapes can only be
+ accessed read-only when using this interface. Have a look at
+ Documentation/s390/TAPE for further information about creating
+ volumes for and using this interface. It is safe to say "Y" here.
+
+Support for 3490 tape hardware
+CONFIG_S390_TAPE_3490
+ Select this option if you want to access IBM 3480 magnetic
+ tape subsystems and 100% compatibles.
+ It is safe to say "Y" here.
+
+Support for 3480 tape hardware
+CONFIG_S390_TAPE_3480
+ Select this option if you want to access IBM 3490 magnetic
+ tape subsystems and 100% compatibles.
+
+CTC device support
+CONFIG_CTC
+ Select this option if you want to use channel-to-channel networking
+ on IBM S/390 or zSeries. This device driver supports real CTC
+ coupling using ESCON. It also supports virtual CTCs when running
+ under VM. It will use the channel device configuration if this is
+ available. This option is also available as a module which will be
+ called ctc.o. If you do not know what it is, it's safe to say "Y".
+
+Support for DIAG access to CMS reserved Disks
+CONFIG_DASD_DIAG
+ Select this option if you want to use CMS reserved Disks under VM
+ with the Diagnose250 command. If you are not running under VM or
+ unsure what it is, say "N".
+
+XPRAM disk support
+CONFIG_BLK_DEV_XPRAM
+ Select this option if you want to use your expanded storage on S/390
+ or zSeries as a disk. This is useful as a _fast_ swap device if you
+ want to access more than 2G of memory when running in 31 bit mode.
+ This option is also available as a module which will be called
+ xpram.o. If unsure, say "N".
+
+Fast IRQ handling
+CONFIG_FAST_IRQ
+ Select this option in order to get the interrupts processed faster
+ on your S/390 or zSeries machine. If selected, after an interrupt
+ is processed, the channel subsystem will be asked for other pending
+ interrupts which will also be processed before leaving the interrupt
+ context. This speeds up the I/O a lot. Say "Y".
+
+IUCV device support (VM only)
+CONFIG_IUCV
+ Select this option if you want to use inter-user communication
+ vehicle networking under VM or VIF. This option is also available
+ as a module which will be called iucv.o. If unsure, say "Y".
+
+Kernel support for 31 bit ELF binaries
+CONFIG_S390_SUPPORT
+ Select this option if you want to enable your system kernel to
+ handle system-calls from ELF binaries for 31 bit ESA. This option
+ (and some other stuff like libraries and such) is needed for
+ executing 31 bit applications. It is safe to say "Y".
+
+Channel Device Configuration
+CONFIG_CHANDEV
+ The channel device layer is a layer to provide a consistent
+ interface for configuration & default machine check (devices
+ appearing & disappearing) handling on Linux for s/390 & z/Series
+ channel devices.
+
+ s/390 & z/Series channel devices include among others
+
+ lcs (the most common ethernet/token ring/fddi standard on
+ zSeries)
+ ctc/escon hi speed like serial link standard on zSeries
+ claw used to talk to cisco routers.
+ qeth gigabit ethernet.
+
+ These devices use two channels one read & one write for
+ configuration & communication (& a third channel, the data
+ channel the case of gigabit ethernet). The motivation
+ behind developing this layer was that there was a lot of
+ duplicate code among the channel device drivers for
+ configuration.
+
+ Also the lcs & ctc drivers tended to fight over
+ 3088/08's & 3088/1F's which could be either 2216/3172
+ channel attached lcs compatible devices or escon/ctc pipes
+ had to be configured separately as they couldn't autodetect,
+ this is now simplified by doing the configuration in a single
+ place (the channel device layer).
+
+ This layer isn't invasive & it is quite okay to use channel
+ drivers which don't use the channel device layer in
+ conjunction with drivers which do.
+
+ For more info see the chandev manpage usually distributed in
+ <file:Documentation/s390/chandev.8> in the Linux source tree.
+
SAB3036 tuner support
CONFIG_TUNER_3036
Say Y here to include support for Philips SAB3036 compatible tuners.
@@ -18347,15 +21732,24 @@
Compaq SMART2 support
CONFIG_BLK_CPQ_DA
- This is the driver for Compaq Smart Array controllers.
- Everyone using these boards should say Y here.
- See the file Documentation/cpqarray.txt for the current list of
- boards supported by this driver, and for further information
- on the use of this driver.
+ This is the driver for Compaq Smart Array controllers. Everyone
+ using these boards should say Y here. See the file
+ <file:Documentation/cpqarray.txt> for the current list of boards
+ supported by this driver, and for further information on the use of
+ this driver.
+
+Show crashed user process info
+CONFIG_PROCESS_DEBUG
+ Say Y to print all process fault locations to the console. This is
+ a debugging option; you probably do not want to set it unless you
+ are an S390 port maintainer.
#
# ARM options
#
+# CML2 transition note: CML1 asks ARCH_ARCA5K, then has ARCH_A5K and ARCH_ARK
+# as subquestions. CML2 asks the subquestions in the armtype menu and makes
+# ARCH_ARCA5K a derived symbol.
ARM System type
CONFIG_ARCH_ARCA5K
This selects what ARM system you wish to build the kernel for. It
@@ -18363,110 +21757,224 @@
to set this option to, please consult any information supplied with
your system.
+# Choice: armtype
+A5000
+CONFIG_ARCH_A5K
+ Say Y here to to support the Acorn A5000. Linux can support the
+ internal IDE disk and CD-ROM interface, serial and parallel port,
+ and the floppy drive. Note that on some A5000s the floppy is
+ plugged into the wrong socket on the motherboard.
+
+Archimedes
+CONFIG_ARCH_ARC
+ The Acorn Archimedes was an personal computer based on an 8K ARM2
+ processor, released in 1987. It supported 512K of RAM and 2 800K
+ floppy disks. Picture and more detailed specifications at
+ <http://www.computingmuseum.com/museum/archi.htm>.
+
+EBSA-110
+CONFIG_ARCH_EBSA110
+ This is an evaluation board for the StrongARM processor available
+ from Digital. It has limited hardware on-board, including an onboard
+ Ethernet interface, two PCMCIA sockets, two serial ports and a
+ parallel port.
+
+RiscPC
+CONFIG_ARCH_RPC
+ On the Acorn Risc-PC, Linux can support the internal IDE disk and
+ CD-ROM interface, serial and parallel port, and the floppy drive.
+
2MB physical memory
CONFIG_PAGESIZE_16
Say Y here if your Archimedes or A5000 system has only 2MB of
memory, otherwise say N. The resulting kernel will not run on a
machine with 4MB of memory.
-Include support for the CATS
+CATS
CONFIG_ARCH_CATS
Say Y here if you intend to run this kernel on the CATS.
Saying N will reduce the size of the Footbridge kernel.
-Include support for the EBSA285
+EBSA285 (addin mode)
+CONFIG_ARCH_EBSA285_ADDIN
+ Say Y here if you intend to run this kernel on the EBSA285 card
+ in addin mode.
+
+ Saying N will reduce the size of the Footbridge kernel.
+
+EBSA285 (host mode)
CONFIG_ARCH_EBSA285_HOST
Say Y here if you intend to run this kernel on the EBSA285 card
in host ("central function") mode.
Saying N will reduce the size of the Footbridge kernel.
-Include support for the LinkUp Systems L7200 SDB
+LinkUp Systems L7200 SDB
CONFIG_ARCH_L7200
Say Y here if you intend to run this kernel on a LinkUp Systems
L7200 Software Development Board which uses an ARM720T processor.
Information on this board can be obtained at:
- http://www.linkupsys.com/
+ <http://www.linkupsys.com/>
If you have any questions or comments about the Linux kernel port
- to this board, send e-mail to sjhill@cotw.com
+ to this board, send e-mail to sjhill@cotw.com.
-Include support for the NetWinder
+NetWinder
CONFIG_ARCH_NETWINDER
Say Y here if you intend to run this kernel on the Rebel.COM
NetWinder. Information about this machine can be found at:
- http://www.netwinder.org/
+ <http://www.netwinder.org/>
Saying N will reduce the size of the Footbridge kernel.
-Include support for the Compaq Personal Server
+P720T
+CONFIG_ARCH_P720T
+ Say Y here if you intend to run this kernel on the ARM Prospector
+ 720T.
+
+Compaq Personal Server
CONFIG_ARCH_PERSONAL_SERVER
Say Y here if you intend to run this kernel on the Compaq
Personal Server.
-
+
Saying N will reduce the size of the Footbridge kernel.
- The Compaq Personal Server is not available for purchase.
+ The Compaq Personal Server is not available for purchase.
There are no product plans beyond the current research
prototypes at this time. Information is available at:
-
- http://crl.research.compaq.com/projects/personalserver
-
+
+ <http://crl.research.compaq.com/projects/personalserver>
+
If you have any questions or comments about the Compaq Personal
- Server, send e-mail to skiff@crl.dec.com
+ Server, send e-mail to skiff@crl.dec.com.
-Include support for Assabet
+Assabet
CONFIG_SA1100_ASSABET
Say Y here if you are using the Intel(R) StrongARM(R) SA-1110
Microprocessor Development Board (also known as the Assabet).
-Include support for Neponset
+Neponset
CONFIG_ASSABET_NEPONSET
Say Y here if you are using the Intel(R) StrongARM(R) SA-1110
Microprocessor Development Board (Assabet) with the SA-1111
Development Board (Nepon).
-Include support for the Compaq iPAQ H3600 (Bitsy)
-CONFIG_SA1100_BITSY
- Say Y here if you intend to run this kernel on the Compaq iPAQ
+Compaq iPAQ H3600
+CONFIG_SA1100_H3600
+ Say Y here if you intend to run this kernel on the Compaq iPAQ
H3600 handheld computer. Information about this machine and the
Linux port to this machine can be found at:
- http://www.handhelds.org/Compaq/index.html#iPAQ_H3600
- http://www.compaq.com/products/handhelds/pocketpc/
+ <http://www.handhelds.org/Compaq/index.html#iPAQ_H3600>
+ <http://www.compaq.com/products/handhelds/pocketpc/>
-Include support for Brutus
+Brutus
CONFIG_SA1100_BRUTUS
Say Y here if you are using the Intel(R) StrongARM(R) SA-1100
Microprocessor Development Board (also known as the Brutus).
-Include support for LART
+LART
CONFIG_SA1100_LART
Say Y here if you are using the Linux Advanced Radio Terminal
- (also known as the LART). See http://www.lart.tudelft.nl/ for
+ (also known as the LART). See <http://www.lart.tudelft.nl/> for
information on the LART.
-Include support for GraphicsClient
+GraphicsClient
CONFIG_SA1100_GRAPHICSCLIENT
Say Y here if you are using an Applied Data Systems Intel(R)
StrongARM(R) SA-1100 based Graphics Client SBC. See
- http://www.flatpanels.com/ for information on this system.
+ <http://www.flatpanels.com/> for information on this system.
+
+CerfBoard
+CONFIG_SA1100_CERF
+ The Intrinsyc CerfBoard is based on the StrongARM 1110.
+ More information is available at:
+ <http://www.intrinsyc.com/products/referenceplatforms/cerfboard.html>.
+
+ Say Y if configuring for an Intrinsyc CerfBoard.
+ Say N otherwise.
+
+nanoEngine
+CONFIG_SA1100_NANOENGINE
+ The nanoEngine is a StrongARM 1110-based single board computer
+ from Bright Star Engineering. More information is available at:
+ <http://www.brightstareng.com/arm/nanoeng.htm>.
+
+ Say Y if configuring for a nanoEngine.
+ Say N otherwise.
+
+Pangolin
+CONFIG_SA1100_PANGOLIN
+ Pangolin is a StrongARM 1110-based evaluation platform produced
+ by Dialogue Technology. It has EISA slots for ease of configuration
+ with SDRAM/Flash memory card, USB/Serial/Audio card, Compact Flash
+ card, and TFT-LCD card.
+
+ Say Y if configuring for a Pangolin.
+ Say N otherwise.
-Include support for Victor
+Victor
CONFIG_SA1100_VICTOR
Say Y here if you are using a Visu Aide Intel(R) StrongARM(R)
SA-1100 based Victor Digital Talking Book Reader. See
- http://www.visuaide.com/pagevictor.en.html for information on
+ <http://www.visuaide.com/pagevictor.en.html> for information on
this system.
-Load kernel using Angel Debug Monitor
-CONFIG_ANGELBOOT
- Say Y if you plan to load the kernel using Angel, ARM Ltd's target
- debug stub. If you are not using Angel, you must say N. It is
- important to get this setting correct.
+Support ARM610 processor
+CONFIG_CPU_ARM610
+ The ARM610 is the successor to the ARM3 processor
+ and was produced by VLSI Technology Inc.
+
+ Say Y if you want support for the ARM610 processor.
+ Otherwise, say N.
+
+Support ARM710 processor
+CONFIG_CPU_ARM710
+ A 32-bit RISC microprocessor based on the ARM7 processor core
+ designed by Advanced RISC Machines Ltd. The ARM710 is the
+ successor to the ARM610 processor. It was released in
+ July 1994 by VLSI Technology Inc.
+
+ Say Y if you want support for the ARM710 processor.
+ Otherwise, say N.
+
+Support ARM720T processor
+CONFIG_CPU_ARM720T
+ A 32-bit RISC processor with 8kByte Cache, Write Buffer and
+ MMU built around an ARM7TDMI core.
+
+ Say Y if you want support for the ARM720T processor.
+ Otherwise, say N.
+
+Support ARM920T processor
+CONFIG_CPU_ARM920T
+ The ARM920T is licensed to be produced by numerous vendors,
+ and is used in the Maverick EP9312. More information at
+ <http://linuxdevices.com/products/PD2382866068.html>.
+
+ Say Y if you want support for the ARM920T processor.
+ Otherwise, say N.
+
+Support ARM1020 processor
+CONFIG_CPU_ARM1020
+ The ARM1020 is the cached version of the ARM10 processor,
+ with an addition of a floating-point unit.
+
+ Say Y if you want support for the ARM1020 processor.
+ Otherwise, say N.
+
+Support StrongARM SA-110 processor
+CONFIG_CPU_SA110
+ The Intel StrongARM(R) SA-110 is a 32-bit microprocessor and
+ is available at five speeds ranging from 100 MHz to 233 MHz.
+ More information is available at
+ <http://developer.intel.com/design/strong/sa110.htm>.
+
+ Say Y if you want support for the SA-110 processor.
+ Otherwise, say N.
Math emulation
CONFIG_FPE_NWFPE
@@ -18483,24 +21991,26 @@
You may say N here if you are going to load the Acorn FPEmulator
early in the bootup.
+FastFPE math emulation
CONFIG_FPE_FASTFPE
Say Y here to include the FAST floating point emulator in the kernel.
This is an experimental much faster emulator which has only 32 bit
- precision for the mantissa. It does not support any exceptions. This
- makes it very simple, it is approximately 4-8 times faster than NWFPE.
-
- It should be sufficient for most programs. It is definitely not
- suitable if you do scientific calculations that need double precision
- for iteration formulas that sum up lots of very small numbers. If you
- do not feel you need a faster FP emulation you should better choose
+ precision for the mantissa. It does not support any exceptions.
+ This makes it very simple, it is approximately 4-8 times faster than
NWFPE.
+ It should be sufficient for most programs. It is definitely not
+ suitable if you do scientific calculations that need double
+ precision for iteration formulas that sum up lots of very small
+ numbers. If you do not feel you need a faster FP emulation you
+ should better choose NWFPE.
+
It is also possible to say M to build the emulator as a module
- (fastfpe.o). But keep in mind that you should only load the FP emulator
- early in the bootup. You should never change from NWFPE to FASTFPE or
- vice versa in an active system!
+ (fastfpe.o). But keep in mind that you should only load the FP
+ emulator early in the bootup. You should never change from NWFPE to
+ FASTFPE or vice versa in an active system!
-DS1620 Thermometer support
+DS1620 thermometer support
CONFIG_DS1620
Say Y here to include support for the thermal management hardware
found in the NetWinder. This driver allows the user to control the
@@ -18531,7 +22041,7 @@
information that is reported is severely limited. Most people
should say N here.
-User fault debugging
+Verbose user fault messages
CONFIG_DEBUG_USER
When a user program crashes due to an exception, the kernel can
print a brief message explaining what the problem was. This is
@@ -18555,22 +22065,18 @@
Kernel low-level debugging messages via footbridge serial port
CONFIG_DEBUG_DC21285_PORT
- Say Y here if you want the low-level print routines to direct their
- output to the serial port in the DC21285 (Footbridge).
+ Say Y here if you want the debug print routines to direct their
+ output to the serial port in the DC21285 (Footbridge). Saying N
+ will cause the debug messages to appear on the first 16550
+ serial port.
+
+Kernel low-level debugging messages via UART2
+CONFIG_DEBUG_CLPS711X_UART2
+ Say Y here if you want the debug print routines to direct their
+ output to the second serial port on these devices. Saying N will
+ cause the debug messages to appear on the first serial port.
-Split initialisation functions into discardable section
-CONFIG_TEXT_SECTIONS
- If you say Y here, kernel code that is only used during
- initialisation is collected into a special area of the kernel so
- that it can be discarded and the memory reclaimed when
- initialisation is complete. In addition, if the kernel you wish to
- build is able to run on multiple architectures, it allows the unused
- code to be discarded. Some versions of binutils, however, have a bug
- that causes the kernel to crash during startup when this option is
- enabled. Say Y unless you experience problems that you suspect may
- be caused by this.
-
-Disable pgtable cache (EXPERIMENTAL)
+Disable pgtable cache
CONFIG_NO_PGT_CACHE
Normally the kernel maintains a `quicklist' of preallocated
pagetable structures in order to increase performance. On machines
@@ -18580,7 +22086,7 @@
RISC OS personality
CONFIG_ARTHUR
Say Y here to include the kernel code necessary if you want to run
- Acorn RISC OS/Arthur binaries under Linux. This code is still very
+ Acorn RISC OS/Arthur binaries under Linux. This code is still very
experimental; if this sounds frightening, say N and sleep in peace.
You can also say M here to compile this support as a module (which
will be called arthur.o).
@@ -18591,9 +22097,9 @@
for the boot loader to pass arguments to the kernel. For these
architectures, you should supply some command-line options at build
time by entering them here. As a minimum, you should specify the
- memory size and the root device (e.g., mem=64M root=/dev/nfs)
+ memory size and the root device (e.g., mem=64M root=/dev/nfs).
-Hardware alignment trap (EXPERIMENTAL)
+Kernel-mode alignment trap handler
CONFIG_ALIGNMENT_TRAP
ARM processors can not fetch/store information which is not
naturally aligned on the bus, i.e., a 4 byte fetch must start at an
@@ -18603,57 +22109,82 @@
correct operation of some network protocols. With an IP-only
configuration it is safe to say N, otherwise say Y.
-21285 serial port support
+DC21285 serial port support
CONFIG_SERIAL_21285
If you have a machine based on a 21285 (Footbridge) StrongARM(R)/
PCI bridge you can enable its onboard serial port by enabling this
option. The device has major ID 4, minor 64.
-Console on 21285 serial port
+Console on DC21285 serial port
CONFIG_SERIAL_21285_CONSOLE
If you have enabled the serial port on the 21285 footbridge you can
make it the console by answering Y to this option.
SA1100 serial port support
CONFIG_SERIAL_SA1100
+ * Orphaned entry retained 20 April 2001 by Russell King *
+ * If you read this note from the configurator, please contact *
+ * the Configure.help maintainers. *
If you have a machine based on a SA1100/SA1110 StrongARM CPU you can
enable its onboard serial port by enabling this option.
- Please read Documentation/arm/SA1100/serial_UART for further info.
+ Please read <file:Documentation/arm/SA1100/serial_UART> for further
+ info.
Console on SA1100 serial port
CONFIG_SERIAL_SA1100_CONSOLE
+ * Orphaned entry retained 20 April 2001 by Russell King *
+ * If you read this note from the configurator, please contact *
+ * the Configure.help maintainers. *
If you have enabled the serial port on the SA1100/SA1110 StrongARM
CPU you can make it the console by answering Y to this option.
L7200 serial port support
CONFIG_SERIAL_L7200
+ * Orphaned entry retained 20 April 2001 by Russell King *
+ * If you read this note from the configurator, please contact *
+ * the Configure.help maintainers. *
If you have a LinkUp Systems L7200 board you can enable its two
onboard serial ports by enabling this option. The device numbers
are major ID 4 with minor 64 and 65 respectively.
Console on L7200 serial port
CONFIG_SERIAL_L7200_CONSOLE
+ * Orphaned entry retained 20 April 2001 by Russell King *
+ * If you read this note from the configurator, please contact *
+ * the Configure.help maintainers. *
If you have enabled the serial ports on the L7200 development board
you can make the first serial port the console by answering Y to
this option.
L7200 SDB keyboard support
CONFIG_KEYBOARD_L7200
+ * Orphaned entry retained 20 April 2001 by Russell King *
+ * If you read this note from the configurator, please contact *
+ * the Configure.help maintainers. *
Enable this option if you would like to be able to use a keyboard
on a LinkUp Systems L7200 board.
L7200 SDB Fujitsu keyboard support
CONFIG_KEYBOARD_L7200_NORM
+ * Orphaned entry retained 20 April 2001 by Russell King *
+ * If you read this note from the configurator, please contact *
+ * the Configure.help maintainers. *
Select the Fujitsu keyboard if you want a normal QWERTY style
keyboard on the LinkUp SDB.
L7200 SDB Prototype keyboard support
CONFIG_KEYBOARD_L7200_DEMO
+ * Orphaned entry retained 20 April 2001 by Russell King *
+ * If you read this note from the configurator, please contact *
+ * the Configure.help maintainers. *
Select the prototype keyboard if you want to play with the
LCD/keyboard combination on the LinkUp SDB.
Footbridge Mode
CONFIG_HOST_FOOTBRIDGE
+ * Orphaned entry retained 20 April 2001 by Russell King *
+ * If you read this note from the configurator, please contact *
+ * the Configure.help maintainers. *
The 21285 Footbridge chip can operate in either `host mode' or
`add-in' mode. Say Y if your 21285 is in host mode, and therefore
is the configuration master, otherwise say N. This must not be
@@ -18691,7 +22222,7 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called nwflash.o. If you want to compile it as a
- module, say M here and read Documentation/modules.txt.
+ module, say M here and read <file:Documentation/modules.txt>.
If you're not sure, say N.
@@ -18704,22 +22235,22 @@
This driver is also available as a module and will be called
srm_env.o if you build it as a module.
-
+
Footbridge internal watchdog
CONFIG_21285_WATCHDOG
- The Intel Footbridge chip contains a builtin watchdog circuit. Say Y
+ The Intel Footbridge chip contains a builtin watchdog circuit. Say Y
here if you wish to use this. Alternatively say M to compile the
driver as a module, which will be called wdt285.o.
- This driver does not work on all machines. In particular, early CATS
- boards have hardware problems that will cause the machine to simply
+ This driver does not work on all machines. In particular, early CATS
+ boards have hardware problems that will cause the machine to simply
lock up if the watchdog fires.
"If in doubt, leave it out" - say N.
-NetWinder WB977 watchdog
+NetWinder WB83C977 watchdog
CONFIG_977_WATCHDOG
- Say Y here to include support for the WB977 watchdog included in
+ Say Y here to include support for the WB977 watchdog included in
NetWinder machines. Alternatively say M to compile the driver as
a module, which will be called wdt977.o.
@@ -18732,27 +22263,41 @@
infrared communication and is supported by most laptops and PDA's.
To use Linux support for the IrDA (tm) protocols, you will also need
- some user-space utilities like irattach. For more information, see the file
- Documentation/networking/irda.txt. You also want to read the
- IR-HOWTO, available at http://www.linuxdoc.org/docs.html#howto .
+ some user-space utilities like irattach. For more information, see
+ the file <file:Documentation/networking/irda.txt>. You also want to
+ read the IR-HOWTO, available at
+ <http://www.linuxdoc.org/docs.html#howto>.
+
+ If you want to exchange bits of data (vCal, vCard) with a PDA, you
+ will need to install some OBEX application, such as OpenObex :
+ <http://sourceforge.net/projects/openobex/>
- This support is also available as a module called irda.o. If you
+ This support is also available as a module called irda.o. If you
want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ <file:Documentation/modules.txt>.
+
+Ultra (connectionless) protocol
+CONFIG_IRDA_ULTRA
+ Say Y here to support the connectionless Ultra IRDA protocol.
+ Ultra allows to exchange data over IrDA with really simple devices
+ (watch, beacon) without the overhead of the IrDA protocol (no handshaking,
+ no management frames, simple fixed header).
+ Ultra is available as a special socket : socket(AF_IRDA, SOCK_DGRAM, 1);
IrDA protocol options
CONFIG_IRDA_OPTIONS
- Say Y here if you want to configure any of the following IrDA options.
+ Say Y here if you want to configure any of the following IrDA
+ options.
-IrDA Cache last LSAP
+IrDA cache last LSAP
CONFIG_IRDA_CACHE_LAST_LSAP
- Say Y here if you want IrLMP to cache the last LSAP used. This makes
- sense since most frames will be sent/received on the same
- connection. Enabling this option will save a hash-lookup per frame.
+ Say Y here if you want IrLMP to cache the last LSAP used. This
+ makes sense since most frames will be sent/received on the same
+ connection. Enabling this option will save a hash-lookup per frame.
If unsure, say Y.
-IrDA Fast RR's
+IrDA Fast RRs
CONFIG_IRDA_FAST_RR
Say Y here is you want IrLAP to send fast RR (Receive Ready) frames
when acting as a primary station. This will make IrLAP send out a RR
@@ -18768,129 +22313,165 @@
If unsure, say N.
-IrDA Debug
+IrDA debugging information
CONFIG_IRDA_DEBUG
Say Y here if you want the IrDA subsystem to write debug information
to your syslog. You can change the debug level in
- /proc/sys/net/irda/debug
+ /proc/sys/net/irda/debug .
If unsure, say Y (since it makes it easier to find the bugs).
-IrLAP Compression support
+IrLAP compression support
CONFIG_IRDA_COMPRESSION
Compression is _not_ part of the IrDA(tm) protocol specification,
but it's working great! Linux is the first to try out compression
support at the IrLAP layer. This means that you will only benefit
from compression if you are running a Linux <-> Linux configuration.
-
+
If you say Y here, you also need to say Y or M to a compression
protocol below.
-IrLAP Deflate Compression Protocol (EXPERIMENTAL)
+IrLAP Deflate compression
CONFIG_IRDA_DEFLATE
Say Y here if you want to build support for the Deflate compression
protocol. The deflate compression (GZIP) is exactly
- the same as the one used by the PPP protocol.
+ the same as the one used by the PPP protocol.
If you want to compile this compression support as a module, say M
- here and read Documentation/modules.txt. The module will be called
- irda_deflate.o.
+ here and read <file:Documentation/modules.txt>. The module will be
+ called irda_deflate.o.
-IrLAN Protocol
+IrLAN protocol
CONFIG_IRLAN
- Say Y here if you want to build support for the IrLAN protocol. If
+ Say Y here if you want to build support for the IrLAN protocol. If
you want to compile it as a module (irlan.o), say M here and read
- Documentation/modules.txt. IrLAN emulates an Ethernet and makes it
- possible to put up a wireless LAN using infrared beams.
+ <file:Documentation/modules.txt>. IrLAN emulates an Ethernet and
+ makes it possible to put up a wireless LAN using infrared beams.
- The IrLAN protocol can be used to talk with infrared access points
- like the HP NetbeamIR, or the ESI JetEye NET. You can also connect
- to another Linux machine running the IrLAN protocol for ad-hoc
+ The IrLAN protocol can be used to talk with infrared access points
+ like the HP NetbeamIR, or the ESI JetEye NET. You can also connect
+ to another Linux machine running the IrLAN protocol for ad-hoc
networking!
-IrNET Protocol
+IrNET protocol
CONFIG_IRNET
- Say Y here if you want to build support for the IrNET protocol. If
+ Say Y here if you want to build support for the IrNET protocol. If
you want to compile it as a module (irnet.o), say M here and read
- Documentation/modules.txt. IrNET is a PPP driver, so you will also
- need a working PPP subsystem (driver, daemon and config)...
+ <file:Documentation/modules.txt>. IrNET is a PPP driver, so you
+ will also need a working PPP subsystem (driver, daemon and
+ config)...
- IrNET is an alternate way to tranfer TCP/IP traffic over IrDA. It
- uses synchronous PPP over a set of point to point IrDA sockets. You
+ IrNET is an alternate way to tranfer TCP/IP traffic over IrDA. It
+ uses synchronous PPP over a set of point to point IrDA sockets. You
can use it between Linux machine or with W2k.
-IrCOMM Protocol
+IrCOMM protocol
CONFIG_IRCOMM
- Say Y here if you want to build support for the IrCOMM protocol. If
+ Say Y here if you want to build support for the IrCOMM protocol. If
you want to compile it as a module (you will get ircomm.o and
- ircomm-tty.o), say M here and read Documentation/modules.txt. IrCOMM
- implements serial port emulation, and makes it possible to use all
- existing applications that understands TTY's with an infrared link.
- Thus you should be able to use application like PPP, minicom and
- others. Enabling this option will create two modules called ircomm
- and ircomm_tty.
+ ircomm-tty.o), say M here and read <file:Documentation/modules.txt>.
+ IrCOMM implements serial port emulation, and makes it possible to
+ use all existing applications that understands TTY's with an
+ infrared link. Thus you should be able to use application like PPP,
+ minicom and others. Enabling this option will create two modules
+ called ircomm and ircomm_tty.
IrTTY IrDA Device Driver
CONFIG_IRTTY_SIR
Say Y here if you want to build support for the IrTTY line
- discipline. If you want to compile it as a module (irtty.o), say M
- here and read Documentation/modules.txt. IrTTY makes it possible to
- use Linux's own serial driver for all IrDA ports that are 16550
- compatible. Most IrDA chips are 16550 compatible so you should
- probably say Y to this option. Using IrTTY will however limit the
- speed of the connection to 115200 bps (IrDA SIR mode)
+ discipline. If you want to compile it as a module (irtty.o), say M
+ here and read <file:Documentation/modules.txt>. IrTTY makes it
+ possible to use Linux's own serial driver for all IrDA ports that
+ are 16550 compatible. Most IrDA chips are 16550 compatible so you
+ should probably say Y to this option. Using IrTTY will however
+ limit the speed of the connection to 115200 bps (IrDA SIR mode).
If unsure, say Y.
-IrPORT IrDA Device Driver
+IrPORT IrDA serial driver
CONFIG_IRPORT_SIR
Say Y here if you want to build support for the IrPORT IrDA device
driver. If you want to compile it as a module (irport.o), say M here
- and read Documentation/modules.txt. IrPORT can be used instead of
- IrTTY and sometimes this can be better. One example is if your IrDA
- port does not have echo-canceling, which will work OK with IrPORT
- since this driver is working in half-duplex mode only. You don't
- need to use irattach with IrPORT, but you just insert it the same
- way as FIR drivers (insmod irport io=0x3e8 irq=11). Notice that
- IrPORT is a SIR device driver which means that speed is limited to
- 115200 bps.
+ and read <file:Documentation/modules.txt>. IrPORT can be used
+ instead of IrTTY and sometimes this can be better. One example is
+ if your IrDA port does not have echo-canceling, which will work OK
+ with IrPORT since this driver is working in half-duplex mode only.
+ You don't need to use irattach with IrPORT, but you just insert it
+ the same way as FIR drivers (insmod irport io=0x3e8 irq=11). Notice
+ that IrPORT is a SIR device driver which means that speed is limited
+ to 115200 bps.
If unsure, say Y.
+USB IrDA FIR dongle Device Driver
+CONFIG_USB_IRDA
+ Say Y here if you want to build support for the USB IrDA FIR Dongle
+ device driver. If you want to compile it as a module (irda-usb.o),
+ say M here and read <file:Documentation/modules.txt>. IrDA-USB
+ support the various IrDA USB dongles available and most of their
+ pecularities. Those dongles plug in the USB port of your computer,
+ are plug and play, and support SIR and FIR (4Mbps) speeds. On the
+ other hand, those dongles tend to be less efficient than a FIR
+ chipset.
+
+ Please note that the driver is still experimental. And of course,
+ you will need both USB and IrDA support in your kernel...
+
Winbond W83977AF IrDA Device Driver
CONFIG_WINBOND_FIR
Say Y here if you want to build IrDA support for the Winbond
- W83977AF super-io chipset. This driver should be used for the IrDA
- chipset in the Corel NetWinder. The driver supports SIR, MIR and FIR
- (4Mbps) speeds.
+ W83977AF super-io chipset. This driver should be used for the IrDA
+ chipset in the Corel NetWinder. The driver supports SIR, MIR and
+ FIR (4Mbps) speeds.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. The module will be called w83977af_ir.o.
+ <file:Documentation/modules.txt>. The module will be called
+ w83977af_ir.o.
-NSC PC87108 IrDA Device Driver
+NSC PC87108/PC87338 IrDA Device Driver
CONFIG_NSC_FIR
Say Y here if you want to build support for the NSC PC87108 and
- PC87338 IrDA chipsets. This driver supports SIR,
- MIR and FIR (4Mbps) speeds.
+ PC87338 IrDA chipsets. This driver supports SIR,
+ MIR and FIR (4Mbps) speeds.
If you want to compile it as a module, say M here and read
- Documentation/modules.txt. The module will be called nsc-ircc.o.
+ <file:Documentation/modules.txt>. The module will be called
+ nsc-ircc.o.
-Toshiba Type-O IR Port Device Driver
+National Semiconductor DP83820 series driver
+CONFIG_NS83820
+ This is a driver for the National Semiconductor DP83820 series
+ of gigabit ethernet MACs. Cards using this chipset include
+ the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
+ SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
+ zero copy.
+
+Toshiba Type-O IR Port device driver
CONFIG_TOSHIBA_FIR
Say Y here if you want to build support for the Toshiba Type-O IR
- chipset. This chipset is used by the Toshiba Libretto 100CT, and
- many more laptops. If you want to compile it as a module, say M here
- and read Documentation/modules.txt. The module will be called
- toshoboe.o.
+ chipset. This chipset is used by the Toshiba Libretto 100CT, and
+ many more laptops. If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>. The module will be
+ called toshoboe.o.
-SMC IrCC (Experimental)
+SMC IrCC
CONFIG_SMC_IRCC_FIR
Say Y here if you want to build support for the SMC Infrared
- Communications Controller. It is used in the Fujitsu Lifebook 635t
- and Sony PCG-505TX. If you want to compile it as a module, say M
- here and read Documentation/modules.txt. The module will be called
- smc-ircc.o.
+ Communications Controller. It is used in the Fujitsu Lifebook 635t
+ and Sony PCG-505TX. If you want to compile it as a module, say M
+ here and read <file:Documentation/modules.txt>. The module will be
+ called smc-ircc.o.
+
+ALi M5123 FIR Controller Driver
+CONFIG_ALI_FIR
+ Say Y here if you want to build support for the ALi M5123 FIR
+ Controller. The ALi M5123 FIR Controller is embedded in ALi M1543C,
+ M1535, M1535D, M1535+, M1535D Sourth Bridge. This driver supports
+ SIR, MIR and FIR (4Mbps) speeds.
+
+ If you want to compile it as a module, say M here and read
+ <file:Documentation/modules.txt>. The module will be called
+ ali-ircc.o.
VLSI 82C147 PCI-IrDA Controller Driver
CONFIG_VLSI_FIR
@@ -18909,69 +22490,76 @@
or M to the driver for your particular dongle below.
Note that the answer to this question won't directly affect the
- kernel: saying N will just cause this configure script to skip all
+ kernel: saying N will just cause the configurator to skip all
the questions about serial dongles.
-ESI JetEye PC Dongle
+ESI JetEye PC dongle
CONFIG_ESI_DONGLE
Say Y here if you want to build support for the Extended Systems
- JetEye PC dongle. If you want to compile it as a module, say M here
- and read Documentation/modules.txt. The ESI dongle attaches to the
- normal 9-pin serial port connector, and can currently only be used
- by IrTTY. To activate support for ESI dongles you will have to
+ JetEye PC dongle. If you want to compile it as a module, say M here
+ and read <file:Documentation/modules.txt>. The ESI dongle attaches
+ to the normal 9-pin serial port connector, and can currently only be
+ used by IrTTY. To activate support for ESI dongles you will have to
start irattach like this: "irattach -d esi".
ACTiSYS IR-220L and IR220L+ dongle
CONFIG_ACTISYS_DONGLE
- Say Y here if you want to build support for the ACTiSYS
- IR-220L and IR220L+ dongles. If you want to compile it as a module,
- say M here and read Documentation/modules.txt. The ACTiSYS dongles
+ Say Y here if you want to build support for the ACTiSYS IR-220L and
+ IR220L+ dongles. If you want to compile it as a module, say M here
+ and read <file:Documentation/modules.txt>. The ACTiSYS dongles
attaches to the normal 9-pin serial port connector, and can
- currently only be used by IrTTY. To activate support for ACTiSYS
- dongles you will have to start irattach like this:
+ currently only be used by IrTTY. To activate support for ACTiSYS
+ dongles you will have to start irattach like this:
"irattach -d actisys" or "irattach -d actisys+".
Tekram IrMate 210B dongle
CONFIG_TEKRAM_DONGLE
- Say Y here if you want to build support for the Tekram IrMate 210B
- dongle. If you want to compile it as a module, say M here
- and read Documentation/modules.txt. The Tekram dongle attaches to
- the normal 9-pin serial port connector, and can currently only be
- used by IrTTY. To activate support for Tekram dongles you will have
- to start irattach like this: "irattach -d tekram".
+ Say Y here if you want to build support for the Tekram IrMate 210B
+ dongle. If you want to compile it as a module, say M here and read
+ <file:Documentation/modules.txt>. The Tekram dongle attaches to the
+ normal 9-pin serial port connector, and can currently only be used
+ by IrTTY. To activate support for Tekram dongles you will have to
+ start irattach like this: "irattach -d tekram".
Greenwich GIrBIL dongle
CONFIG_GIRBIL_DONGLE
Say Y here if you want to build support for the Greenwich GIrBIL
- dongle. If you want to compile it as a module, say M here and read
- Documentation/modules.txt. The Greenwich dongle attaches to the
- normal 9-pin serial port connector, and can currently only be used
- by IrTTY. To activate support for Greenwich dongles you will have to
- insert "irattach -d girbil" in the /etc/irda/drivers script.
+ dongle. If you want to compile it as a module, say M here and read
+ <file:Documentation/modules.txt>. The Greenwich dongle attaches to
+ the normal 9-pin serial port connector, and can currently only be
+ used by IrTTY. To activate support for Greenwich dongles you will
+ have to insert "irattach -d girbil" in the /etc/irda/drivers script.
-Parallax Litelink dongle
+Parallax LiteLink dongle
CONFIG_LITELINK_DONGLE
Say Y here if you want to build support for the Parallax Litelink
- dongle. If you want to compile it as a module, say M here and read
- Documentation/modules.txt. The Parallax dongle attaches to the
- normal 9-pin serial port connector, and can currently only be used
- by IrTTY. To activate support for Parallax dongles you will have to
- start irattach like this "irattach -d litelink".
+ dongle. If you want to compile it as a module, say M here and read
+ <file:Documentation/modules.txt>. The Parallax dongle attaches to
+ the normal 9-pin serial port connector, and can currently only be
+ used by IrTTY. To activate support for Parallax dongles you will
+ have to start irattach like this "irattach -d litelink".
Old Belkin dongle
CONFIG_OLD_BELKIN_DONGLE
Say Y here if you want to build support for the Adaptec Airport 1000
- and 2000 dongles. If you want to compile it as a module, say M here
- and read Documentation/modules.txt. The module will be called
- old_belkin.o. Some information is contained in the comments at the
- top of drivers/net/irda/old_belkin.c.
+ and 2000 dongles. If you want to compile it as a module, say M here
+ and read <file:Documentation/modules.txt>. The module will be
+ called old_belkin.o. Some information is contained in the comments
+ at the top of <file:drivers/net/irda/old_belkin.c>.
VME (Motorola and BVM) support
CONFIG_VME
Say Y here if you want to build a kernel for a 680x0 based VME
- board. Boards currently supported include Motorola boards MVME162,
- MVME166, MVME167, MVME172, and MVME177. BVME4000 and BVME6000
- boards from BVM Ltd are also supported.
+ board. Boards currently supported include Motorola boards MVME147,
+ MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
+ BVME6000 boards from BVM Ltd are also supported.
+
+MVME147 support
+CONFIG_MVME147
+ Say Y to include support for early Motorola VME boards. This will
+ build a kernel which can run on MVME147 single-board computers. If
+ you select this option you will have to select the appropriate
+ drivers for SCSI, Ethernet and serial ports later on.
MVME162, 166 and 167 support
CONFIG_MVME16x
@@ -19001,6 +22589,16 @@
is hardwired on. The 53c710 SCSI driver is known to suffer from
this problem.
+WD33C93 SCSI driver for MVME147
+CONFIG_MVME147_SCSI
+ Support for the on-board SCSI controller on the Motorola MVME147
+ single-board computer.
+
+SCC support for MVME147 serial ports
+CONFIG_MVME147_SCC
+ This is the driver for the serial ports on the Motorola MVME147
+ boards. Everyone using one of these boards should say Y here.
+
NCR53C710 SCSI driver for MVME16x
CONFIG_MVME16x_SCSI
The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
@@ -19013,19 +22611,26 @@
SCSI controller chip. Almost everyone using one of these boards
will want to say Y to this question.
+MVME147 (Lance) Ethernet support
+CONFIG_MVME147_NET
+ Support for the on-board Ethernet interface on the Motorola MVME147
+ single-board computer. Say Y here to include the
+ driver for this chip in your kernel. If you want to compile it as
+ a module, say M here and read <file:Documentation/modules.txt>.
+
MVME16x Ethernet support
CONFIG_MVME16x_NET
This is the driver for the Ethernet interface on the Motorola
MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
driver for this chip in your kernel. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
+ a module, say M here and read <file:Documentation/modules.txt>.
BVME6000 Ethernet support
CONFIG_BVME6000_NET
This is the driver for the Ethernet interface on BVME4000 and
BVME6000 VME boards. Say Y here to include the driver for this chip
in your kernel. If you want to compile it as a module, say M here
- and read Documentation/modules.txt.
+ and read <file:Documentation/modules.txt>.
CD2401 support for MVME166/7 serial ports
CONFIG_SERIAL167
@@ -19052,11 +22657,707 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called display7seg.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt.
+ as a module, say M here and read <file:Documentation/modules.txt>.
If you do not have a CompactPCI model CP1400 or CP1500, or
another UltraSPARC-IIi-cEngine boardset with a 7-segment display,
- you should say N to this option.
+ you should say N to this option.
+
+# Choice: cristype
+Etrax-100-LX-v1
+CONFIG_ETRAX100LX
+ Support version 1 of the Etrax 100LX.
+
+Etrax-100-LX-v2
+CONFIG_ETRAX100LX_V2
+ Support version 2 of the Etrax 100LX.
+
+Etrax-100-LX-for-xsim-simulator
+CONFIG_SVINTO_SIM
+ Support the xsim ETRAX Simulator.
+
+DRAM size (dec, in MB)
+CONFIG_ETRAX_DRAM_SIZE
+ Size of DRAM (decimal in MB) typically 2, 8 or 16.
+
+ETRAX Flash Memory configuration
+CONFIG_ETRAX_FLASH_BUSWIDTH
+ Width in bytes of the Flash bus (1, 2 or 4). Is usually 2.
+
+LED configuration on PA
+CONFIG_ETRAX_PA_LEDS
+ The Etrax network driver is responsible for flashing LED's when
+ packets arrive and are sent. It uses macros defined in
+ <file:include/asm-cris/io.h>, and those macros are defined after what
+ YOU choose in this option. The actual bits used are configured
+ separately. Select this if the LEDs are on port PA. Some products
+ put the leds on PB or a memory-mapped latch (CSP0) instead.
+
+LED configuration on PB
+CONFIG_ETRAX_PB_LEDS
+ The Etrax network driver is responsible for flashing LED's when
+ packets arrive and are sent. It uses macros defined in
+ <file:include/asm-cris/io.h>, and those macros are defined after what
+ YOU choose in this option. The actual bits used are configured
+ separately. Select this if the LEDs are on port PB. Some products
+ put the leds on PA or a memory-mapped latch (CSP0) instead.
+
+LED configuration on CSP0
+CONFIG_ETRAX_CSP0_LEDS
+ The Etrax network driver is responsible for flashing LED's when
+ packets arrive and are sent. It uses macros defined in
+ <file:include/asm-cris/io.h>, and those macros are defined after what
+ YOU choose in this option. The actual bits used are configured
+ separately. Select this if the LEDs are on a memory-mapped latch
+ using chip select CSP0, this is mapped at 0x90000000.
+ Some products put the leds on PA or PB instead.
+
+No LED at all
+CONFIG_ETRAX_NO_LEDS
+ Select this option if you don't have any LED at all.
+
+First green LED bit
+CONFIG_ETRAX_LED1G
+ Bit to use for the first green LED.
+ Most Axis products use bit 2 here.
+
+First red LED bit
+CONFIG_ETRAX_LED1R
+ Bit to use for the first red LED.
+ Most Axis products use bit 3 here.
+ For products with only one controllable LED,
+ set this to same as CONFIG_ETRAX_LED1G (normally 2).
+
+Second green LED bit
+CONFIG_ETRAX_LED2G
+ Bit to use for the second green LED. The "Active" LED.
+ Most Axis products use bit 4 here.
+ For products with only one controllable LED,
+ set this to same as CONFIG_ETRAX_LED1G (normally 2).
+
+Second red LED bit
+CONFIG_ETRAX_LED2R
+ Bit to use for the second red LED.
+ Most Axis products use bit 5 here.
+ For products with only one controllable LED,
+ set this to same as CONFIG_ETRAX_LED1G (normally 2).
+
+Third green LED bit
+CONFIG_ETRAX_LED3G
+ Bit to use for the third green LED. The "Drive" LED.
+ For products with only one or two controllable LEDs,
+ set this to same as CONFIG_ETRAX_LED1G (normally 2).
+
+Third red LED bit
+CONFIG_ETRAX_LED3R
+ Bit to use for the third red LED.
+ For products with only one or two controllable LEDs,
+ set this to same as CONFIG_ETRAX_LED1G (normally 2).
+
+Fourth green LED bit
+CONFIG_ETRAX_LED4G
+ Bit to use for the fourth green LED.
+ For products with only one or two controllable LEDs,
+ set this to same as CONFIG_ETRAX_LED1G (normally 2).
+
+Fourth red LED bit
+CONFIG_ETRAX_LED4R
+ Bit to use for the fourth red LED.
+ For products with only one or two controllable LEDs,
+ set this to same as CONFIG_ETRAX_LED1G (normally 2).
+
+Fifth green LED bit
+CONFIG_ETRAX_LED5G
+ Bit to use for the fifth green LED.
+ For products with only one or two controllable LEDs,
+ set this to same as CONFIG_ETRAX_LED1G (normally 2).
+
+Fifth red LED bit
+CONFIG_ETRAX_LED5R
+ Bit to use for the fifth red LED.
+ For products with only one or two controllable LEDs,
+ set this to same as CONFIG_ETRAX_LED1G (normally 2).
+
+Sixth green LED bit
+CONFIG_ETRAX_LED6G
+ Bit to use for the sixth green LED. The "Drive" LED.
+ For products with only one or two controllable LEDs,
+ set this to same as CONFIG_ETRAX_LED1G (normally 2).
+
+Sixth red LED bit
+CONFIG_ETRAX_LED6R
+ Bit to use for the sixth red LED.
+ For products with only one or two controllable LEDs,
+ set this to same as CONFIG_ETRAX_LED1G (normally 2).
+
+Seventh green LED bit
+CONFIG_ETRAX_LED7G
+ Bit to use for the seventh green LED.
+ For products with only one or two controllable LEDs,
+ set this to same as CONFIG_ETRAX_LED1G (normally 2).
+
+Seventh red LED bit
+CONFIG_ETRAX_LED7R
+ Bit to use for the seventh red LED.
+ For products with only one or two controllable LEDs,
+ set this to same as CONFIG_ETRAX_LED1G (normally 2).
+
+Eighth yellow LED bit
+CONFIG_ETRAX_LED8Y
+ Bit to use for the eighth yellow LED. The "Drive" LED.
+ For products with only one or two controllable LEDs,
+ set this to same as CONFIG_ETRAX_LED1G (normally 2).
+
+Ninth yellow LED bit
+CONFIG_ETRAX_LED9Y
+ Bit to use for the ninth yellow LED.
+ For products with only one or two controllable LEDs,
+ set this to same as CONFIG_ETRAX_LED1G (normally 2).
+
+Tenth yellow LED bit
+CONFIG_ETRAX_LED10Y
+ Bit to use for the tenth yellow LED.
+ For products with only one or two controllable LEDs,
+ set this to same as CONFIG_ETRAX_LED1G (normally 2).
+
+Eleventh yellow LED bit
+CONFIG_ETRAX_LED11Y
+ Bit to use for the eleventh yellow LED.
+ For products with only one or two controllable LEDs,
+ set this to same as CONFIG_ETRAX_LED1G (normally 2).
+
+Twelfth red LED bit
+CONFIG_ETRAX_LED12R
+ Bit to use for the twelfth red LED.
+ For products with only one or two controllable LEDs,
+ set this to same as CONFIG_ETRAX_LED1G (normally 2).
+
+Flash LED off during activity
+CONFIG_ETRAX_LED_OFF_DURING_ACTIVITY
+ This option allows you to decide whether the network LED (and
+ Bluetooth LED in case you use Bluetooth) will be on or off when
+ the network is connected, and whether it should flash off or on
+ when there is activity. If you say y to this option the network
+ LED will be lit when there is a connection, and will flash off
+ when there is activity.
+
+PA button configuration
+CONFIG_ETRAX_PA_BUTTON_BITMASK
+ This is a bitmask with information about what bits on PA that
+ are used for buttons.
+ Most products has a so called TEST button on PA1, if that's true
+ use 02 here.
+ Use 00 if there are no buttons on PA.
+ If the bitmask is <> 00 a button driver will be included in the gpio
+ driver. Etrax general I/O support must be enabled.
+
+PA changeable direction bits
+CONFIG_ETRAX_PA_CHANGEABLE_DIR
+ This is a bitmask with information of what bits in PA that a user
+ can change direction on using ioctl's.
+ Bit set = changeable.
+ You probably want 00 here.
+
+PA changeable data bits
+CONFIG_ETRAX_PA_CHANGEABLE_BITS
+ This is a bitmask with information of what bits in PA that a user
+ can change change the value on using ioctl's.
+ Bit set = changeable.
+ You probably want 00 here.
+
+PA changeable direction bits
+CONFIG_ETRAX_PB_CHANGEABLE_DIR
+ This is a bitmask with information of what bits in PB that a user
+ can change direction on using ioctl's.
+ Bit set = changeable.
+ You probably want 00 here.
+
+PB changeable data bits
+CONFIG_ETRAX_PB_CHANGEABLE_BITS
+ This is a bitmask with information of what bits in PB that a user
+ can change the value on using ioctl's.
+ Bit set = changeable.
+ You probably want 00 here.
+
+Kernel debugger (kgdb)
+CONFIG_ETRAX_KGDB
+ The CRIS version of gdb can be used to remotely debug a running
+ Linux kernel via the serial debug port. Provided you have gdb-cris
+ installed, run gdb-cris vmlinux, then type
+
+ (gdb) set remotebaud 115200 <- kgdb uses 115200 as default
+ (gdb) target remote /dev/ttyS0 <- maybe you use another port
+
+ This should connect you to your booted kernel (or boot it now if you
+ didn't before). The kernel halts when it boots, waiting for gdb if
+ this option is turned on!
+
+Etrax bus waitstates
+CONFIG_ETRAX_DEF_R_WAITSTATES
+ Waitstates for SRAM, Flash and peripherials (not DRAM). 95f8 is a
+ good choice for most Axis products...
+
+Etrax bus configuration
+CONFIG_ETRAX_DEF_R_BUS_CONFIG
+ Assorted bits controlling write mode, DMA burst length etc. 104 is
+ a good choice for most Axis products...
+
+Etrax SDRAM configuration
+CONFIG_ETRAX_SDRAM
+ Enable this if you use SDRAM chips and configure
+ R_SDRAM_CONFIG and R_SDRAM_TIMING as well.
+
+DRAM size (dec, in MB)
+CONFIG_ETRAX_DEF_R_DRAM_CONFIG
+ The R_DRAM_CONFIG register specifies everything on how the DRAM
+ chips in the system are connected to the Etrax CPU. This is
+ different depending on the manufacturer, chip type and number of
+ chips. So this value often needs to be different for each Axis
+ product.
+
+Etrax DRAM timing
+CONFIG_ETRAX_DEF_R_DRAM_TIMING
+ Different DRAM chips have different speeds. Current Axis products
+ use 50ns DRAM chips which can use the timing: 5611.
+
+Etrax SDRAM configuration
+CONFIG_ETRAX_DEF_R_SDRAM_CONFIG
+ The R_SDRAM_CONFIG register specifies everything on how the SDRAM
+ chips in the system are connected to the Etrax CPU. This is
+ different depending on the manufacturer, chip type and number of
+ chips. So this value often needs to be different for each Axis
+ product.
+
+Etrax SDRAM timing
+CONFIG_ETRAX_DEF_R_SDRAM_TIMING
+ Different SDRAM chips have different timing.
+
+Etrax General port A direction
+CONFIG_ETRAX_DEF_R_PORT_PA_DIR
+ Configures the direction of general port A bits. 1 is out, 0 is in.
+ This is often totally different depending on the product used.
+ There are some guidelines though - if you know that only LED's are
+ connected to port PA, then they are usually connected to bits 2-4
+ and you can therefore use 1c. On other boards which don't have the
+ LED's at the general ports, these bits are used for all kinds of
+ stuff. If you don't know what to use, it is always safe to put all
+ as inputs, although floating inputs isn't good.
+
+Etrax General port A data
+CONFIG_ETRAX_DEF_R_PORT_PA_DATA
+ Configures the initial data for the general port A bits. Most
+ products should use 00 here.
+
+Etrax General port B config
+CONFIG_ETRAX_DEF_R_PORT_PB_CONFIG
+ Configures the type of the general port B bits. 1 is chip select,
+ 0 is port. Most products should use 00 here.
+
+Etrax General port B direction
+CONFIG_ETRAX_DEF_R_PORT_PB_DIR
+ Configures the direction of general port B bits. 1 is out, 0 is in.
+ This is often totally different depending on the product used. Bits
+ 0 and 1 on port PB are usually used for I2C communication, but the
+ kernel I2C driver sets the appropriate directions itself so you
+ don't need to take that into consideration when setting this option.
+ If you don't know what to use, it is always safe to put all as
+ inputs.
+
+Etrax General port B data
+CONFIG_ETRAX_DEF_R_PORT_PB_DATA
+ Configures the initial data for the general port A bits. Most
+ products should use FF here.
+
+Etrax General port device
+CONFIG_ETRAX_GPIO
+ Enables the Etrax general port device (major 120, minors 0 and 1).
+ You can use this driver to access the general port bits. It supports
+ these ioctl's:
+ #include <linux/etraxgpio.h>
+ fd = open("/dev/gpioa", O_RDWR); // or /dev/gpiob
+ ioctl(fd, _IO(ETRAXGPIO_IOCTYPE, IO_SETBITS), bits_to_set);
+ ioctl(fd, _IO(ETRAXGPIO_IOCTYPE, IO_CLRBITS), bits_to_clear);
+ val = ioctl(fd, _IO(ETRAXGPIO_IOCTYPE, IO_READBITS), NULL);
+ Remember that you need to setup the port directions appropriately in
+ the General configuration.
+
+Etrax parallel data support
+CONFIG_ETRAX_PARDATA
+ Adds support for writing data to the parallel port par0 of the ETRAX
+ 100. If you create a character special file with major number 126,
+ you can write to the data bits of par0.
+ Note: you need to disable Etrax100 parallel port support.
+
+Etrax parallel LCD (HD44780) Driver
+CONFIG_ETRAX_LCD_HD44780
+ Adds support for a HD44780 controlled LCD connected to the parallel
+ port par0 of the Etrax.
+
+Etrax Serial port ser0 support
+CONFIG_ETRAX_SERIAL
+ Enables the ETRAX 100 serial driver for ser0 (ttyS0)
+ You probably want this enabled.
+
+/proc/serial entry
+CONFIG_ETRAX_SERIAL_PROC_ENTRY
+ Enables /proc/serial entry where errors and statistics can be
+ viewed. CONFIG_PROC_FS must also be set for this to work.
+
+Etrax Serial port fast flush of DMA using fast timer API
+CONFIG_ETRAX_SERIAL_FAST_TIMER
+ Select this to have the serial DMAs flushed at a higher rate than
+ normally, possible by using the fast timer API, the timeout is
+ approx. 4 character times.
+ If unsure, say N.
+
+Etrax Serial port fast flush of DMA
+CONFIG_ETRAX_SERIAL_FLUSH_DMA_FAST
+ Select this to have the serial DMAs flushed at a higher rate than
+ normally possible through a fast timer interrupt (currently at
+ 15360 Hz).
+ If unsure, say N.
+
+Etrax Serial port receive flush timeout
+CONFIG_ETRAX_SERIAL_RX_TIMEOUT_TICKS
+ Number of timer ticks between flush of receive fifo (1 tick = 10ms).
+ Try 0-3 for low latency applications. Approx 5 for high load
+ applications (e.g. PPP). Maybe this should be more adaptive some
+ day...
+
+Etrax Serial port ser0 DTR, RI, DSR and CD support on PB
+CONFIG_ETRAX_SER0_DTR_RI_DSR_CD_ON_PB
+ Enables the status and control signals DTR, RI, DSR and CD on PB for
+ ser0.
+
+Serial port 1 enabled
+CONFIG_ETRAX_SERIAL_PORT1
+ Enables the ETRAX 100 serial driver for ser1 (ttyS1).
+
+Etrax Serial port ser1 DTR, RI, DSR and CD support on PB
+CONFIG_ETRAX_SER1_DTR_RI_DSR_CD_ON_PB
+ Enables the status and control signals DTR, RI, DSR and CD on PB for
+ ser1.
+
+Serial port 2 enabled
+CONFIG_ETRAX_SERIAL_PORT2
+ Enables the ETRAX 100 serial driver for ser2 (ttyS2).
+
+Etrax Serial port ser2 DTR, RI, DSR and CD support on PA
+CONFIG_ETRAX_SER2_DTR_RI_DSR_CD_ON_PA
+ Enables the status and control signals DTR, RI, DSR and CD on PA for
+ ser2.
+
+Serial port 3 enabled
+CONFIG_ETRAX_SERIAL_PORT3
+ Enables the ETRAX 100 serial driver for ser3 (ttyS3).
+
+Etrax100 RS-485 support
+CONFIG_ETRAX_RS485
+ Enables support for RS-485 serial communication. For a primer on
+ RS-485, see <http://www.hw.cz/english/docs/rs485/rs485.html>.
+
+Etrax100 RS-485 mode on PA
+CONFIG_ETRAX_RS485_ON_PA
+ Control Driver Output Enable on RS485 tranceiver using a pin on PA
+ port:
+ Axis 2400/2401 uses PA 3.
+
+Etrax100 RS-485 mode on PA bit
+CONFIG_ETRAX_RS485_ON_PA_BIT
+ Control Driver Output Enable on RS485 tranceiver using a this bit
+ on PA port.
+
+Ser0 DTR on PB bit
+CONFIG_ETRAX_SER0_DTR_ON_PB_BIT
+ Specify the pin of the PB port to carry the DTR signal for serial
+ port 0.
+
+Ser0 RI on PB bit
+CONFIG_ETRAX_SER0_RI_ON_PB_BIT
+ Specify the pin of the PB port to carry the RI signal for serial
+ port 0.
+
+Ser0 DSR on PB bit
+CONFIG_ETRAX_SER0_DSR_ON_PB_BIT
+ Specify the pin of the PB port to carry the DSR signal for serial
+ port 0.
+
+Ser0 CD on PB bit
+CONFIG_ETRAX_SER0_CD_ON_PB_BIT
+ Specify the pin of the PB port to carry the CD signal for serial
+ port 0.
+
+Ser1 DTR on PB bit
+CONFIG_ETRAX_SER1_DTR_ON_PB_BIT
+ Specify the pin of the PB port to carry the DTR signal for serial
+ port 1.
+
+Ser1 RI on PB bit
+CONFIG_ETRAX_SER1_RI_ON_PB_BIT
+ Specify the pin of the PB port to carry the RI signal for serial
+ port 1.
+
+Ser1 DSR on PB bit
+CONFIG_ETRAX_SER1_DSR_ON_PB_BIT
+ Specify the pin of the PB port to carry the DSR signal for serial
+ port 1.
+
+Ser1 CD on PB bit
+CONFIG_ETRAX_SER1_CD_ON_PB_BIT
+ Specify the pin of the PB port to carry the CD signal for serial
+ port 1.
+
+Ser2 DTR on PA bit
+CONFIG_ETRAX_SER2_DTR_ON_PA_BIT
+ Specify the pin of the PA port to carry the DTR signal for serial
+ port 2.
+
+Ser2 RI on PA bit
+CONFIG_ETRAX_SER2_RI_ON_PA_BIT
+ Specify the pin of the PA port to carry the RI signal for serial
+ port 2.
+
+Ser2 DSR on PA bit
+CONFIG_ETRAX_SER2_DSR_ON_PA_BIT
+ Specify the pin of the PA port to carry the DTR signal for serial
+ port 2.
+
+Ser2 CD on PA bit
+CONFIG_ETRAX_SER2_CD_ON_PA_BIT
+ Specify the pin of the PA port to carry the CD signal for serial
+ port 2.
+
+Etrax100 RS-485 disable receiver
+CONFIG_ETRAX_RS485_DISABLE_RECEIVER
+ It's necessary to disable the serial receiver to avoid serial
+ loopback. Not all products are able to do this in software only.
+ Axis 2400/2401 must disable receiver.
+
+Etrax100 I2C Support
+CONFIG_ETRAX_I2C
+ Enables an I2C driver on PB0 and PB1 on ETRAX100.
+ EXAMPLE usage:
+ i2c_arg = I2C_WRITEARG(STA013_WRITE_ADDR, reg, val);
+ ioctl(fd, _IO(ETRAXI2C_IOCTYPE, I2C_WRITEREG), i2c_arg);
+ i2c_arg = I2C_READARG(STA013_READ_ADDR, reg);
+ val = ioctl(fd, _IO(ETRAXI2C_IOCTYPE, I2C_READREG), i2c_arg);
+
+Etrax100 I2C configuration
+CONFIG_ETRAX_I2C_USES_PB_NOT_PB_I2C
+ Select whether to use the special I2C mode in the PB I/O register or
+ not. This option needs to be selected in order to use some drivers
+ that access the I2C I/O pins directly instead of going through the
+ I2C driver, like the DS1302 realtime-clock driver. If you are
+ uncertain, choose Y here.
+
+Etrax100 I2C EEPROM (NVRAM) support
+CONFIG_ETRAX_I2C_EEPROM
+ Enables I2C EEPROM (non-volatile RAM) on PB0 and PB1 using the I2C
+ driver. Select size option: Probed, 2k, 8k, 16k.
+ (Probing works for 2k and 8k but not that well for 16k)
+
+Etrax100 I2C EEPROM (NVRAM) size/16kB
+CONFIG_ETRAX_I2C_EEPROM_16KB
+ Use a 16kB EEPROM.
+
+Etrax100 I2C EEPROM (NVRAM) size/2kB
+CONFIG_ETRAX_I2C_EEPROM_2KB
+ Use a 2kB EEPROM.
+
+Etrax100 I2C EEPROM (NVRAM) size/8kB
+CONFIG_ETRAX_I2C_EEPROM_8KB
+ Use a 8kB EEPROM.
+
+Etrax100 I2C EEPROM (NVRAM) size/probe
+CONFIG_ETRAX_I2C_EEPROM_PROBE
+ Specifies size or auto probe of the EEPROM size.
+ Options: Probed, 2k, 8k, 16k.
+ (Probing works for 2k and 8k but not that well for 16k)
+
+Etrax DS1302 Real-Time Clock driver
+CONFIG_ETRAX_DS1302
+ Enables the driver for the DS1302 Real-Time Clock battery-backed
+ chip on some products. The kernel reads the time when booting, and
+ the date can be set using ioctl(fd, RTC_SET_TIME, &rt) with rt a
+ rtc_time struct (see <file:include/asm-cris/rtc.h>) on the /dev/rtc
+ device, major 121. You can check the time with cat /proc/rtc, but
+ normal time reading should be done using libc function time and
+ friends.
+
+Etrax DS1302 RST on the Generic Port
+CONFIG_ETRAX_DS1302_RST_ON_GENERIC_PORT
+ If your product has the RST signal line for the DS1302 RTC on the
+ Generic Port then say Y here, otherwise leave it as N in which
+ case the RST signal line is assumed to be connected to Port PB
+ (just like the SCL and SDA lines).
+
+Etrax DS1302 RST bit number
+CONFIG_ETRAX_DS1302_RSTBIT
+ This is the bit number for the RST signal line of the DS1302 RTC on
+ the selected port. If you have selected the generic port then it
+ should be bit 27, otherwise your best bet is bit 5.
+
+Etrax DS1302 SCL bit number
+CONFIG_ETRAX_DS1302_SCLBIT
+ This is the bit number for the SCL signal line of the DS1302 RTC on
+ Port PB. This is probably best left at 3.
+
+Etrax DS1302 SDA bit number
+CONFIG_ETRAX_DS1302_SDABIT
+ This is the bit number for the SDA signal line of the DS1302 RTC on
+ Port PB. This is probably best left at 2.
+
+Etrax 100 IDE Reset
+CONFIG_ETRAX_IDE_CSP0_8_RESET
+ Configures the pin used to reset the IDE bus.
+
+Etrax 100 IDE Reset
+CONFIG_ETRAX_IDE_CSPE1_16_RESET
+ Configures the pin used to reset the IDE bus.
+
+Etrax 100 ATA/IDE support
+CONFIG_ETRAX_IDE_DELAY
+ Sets the time to wait for disks to regain consciousness after reset.
+
+Etrax 100 IDE Reset
+CONFIG_ETRAX_IDE_G27_RESET
+ Configures the pin used to reset the IDE bus.
+
+IDE reset on PB Bit 7
+CONFIG_ETRAX_IDE_PB7_RESET
+ Configures the pin used to reset the IDE bus.
+
+USB 1.1 host
+CONFIG_ETRAX_USB_HOST
+ This option enables the host functionality of the ETRAX 100LX
+ built-in USB controller. In host mode the controller is designed
+ for CTRL and BULK traffic only, INTR traffic may work as well
+ however (depending on the requirements of timeliness).
+
+USB 1.1 host port 1 enabled
+CONFIG_ETRAX_USB_HOST_PORT1
+ This option enables port 1 of the ETRAX 100LX USB root hub (RH).
+
+USB 1.1 host port 2 enabled
+CONFIG_ETRAX_USB_HOST_PORT2
+ This option enables port 2 of the ETRAX 100LX USB root hub (RH).
+
+ETRAX 100LX 10/100Mbit Ethernet controller
+CONFIG_ETRAX_ETHERNET
+ This option enables the ETRAX 100LX built-in 10/100Mbit Ethernet
+ controller.
+
+ETRAX 100LX Synchronous serial ports
+CONFIG_ETRAX_SYNCHRONOUS_SERIAL
+ This option enables support for the ETRAX 100LX built-in
+ synchronous serial ports. These ports are used for continuous
+ streamed data like audio. The default setting is compatible
+ with the STA 013 MP3 decoder, but can easily be tuned to fit
+ any other audio encoder/decoder and SPI.
+
+ETRAX 100LX Synchronous serial port 0 enabled
+CONFIG_ETRAX_SYNCHRONOUS_SERIAL_PORT0
+ Enables the ETRAX 100LX synchronous serial port 0 (syncser0).
+
+ETRAX 100LX Synchronous serial port 0 uses DMA
+CONFIG_ETRAX_SYNCHRONOUS_SERIAL0_DMA
+ Makes synchronous serial port 0 use DMA.
+
+ETRAX 100LX Synchronous serial port 1 enabled
+CONFIG_ETRAX_SYNCHRONOUS_SERIAL_PORT1
+ Enables the ETRAX 100LX synchronous serial port 1 (syncser1).
+
+ETRAX 100LX Synchronous serial port 1 uses DMA
+CONFIG_ETRAX_SYNCHRONOUS_SERIAL1_DMA
+ Makes synchronous serial port 1 use DMA.
+
+Delay for drives to regain consciousness
+CONFIG_IDE_DELAY
+ Number of seconds to wait for IDE drives to spin up after an IDE
+ reset.
+
+ARTPEC-1 support
+CONFIG_JULIETTE
+ The ARTPEC-1 is a video-compression chip used in the AXIS 2100
+ network camera, which is built around an ETRAX-100 board. With this
+ option selected, the ETRAX kernel configures a DMA channel at boot
+ time to talk to the chip.
+
+Axis flash-map support
+CONFIG_ETRAX_AXISFLASHMAP
+ This option enables MTD mapping of flash devices. Needed to use
+ flash memories. If unsure, say Y.
+
+Byte-offset of partition table sector
+CONFIG_ETRAX_PTABLE_SECTOR
+ Byte-offset of the partition table in the first flash chip.
+ The default value is 64kB and should not be changed unless
+ you know exactly what you are doing. The only valid reason
+ for changing this is when the flash block size is bigger
+ than 64kB (e.g. when using two parallel 16 bit flashes).
+
+Enable Etrax100 watchdog
+CONFIG_ETRAX_WATCHDOG
+ Enable the built-in watchdog timer support on Etrax100 embedded
+ network computers.
+
+# Choice: crisdebug
+Serial-0
+CONFIG_ETRAX_DEBUG_PORT0
+ Choose a serial port for the ETRAX debug console. Default to
+ port 0.
+
+Etrax debug port on ser1
+CONFIG_ETRAX_DEBUG_PORT1
+ Use serial port 1 for the console.
+
+Etrax debug port on ser2
+CONFIG_ETRAX_DEBUG_PORT2
+ Use serial port 2 for the console.
+
+Etrax debug port on ser3
+CONFIG_ETRAX_DEBUG_PORT3
+ Use serial port 3 for the console.
+
+No Etrax debug port
+CONFIG_ETRAX_DEBUG_PORT_NULL
+ Disable serial-port debugging.
+
+Parallel port support
+CONFIG_ETRAX_PARPORT
+ Say Y here to enable the ETRAX on-board parallel ports.
+
+Parallel port 0 enabled
+CONFIG_ETRAX_PARALLEL_PORT0
+ Say Y here to enable parallel port 0.
+
+Parallel port 1 enabled
+CONFIG_ETRAX_PARALLEL_PORT1
+ Say Y here to enable parallel port 1.
+
+# Choice: crisrescue
+Select a product rescue port
+CONFIG_ETRAX_RESCUE_SER0
+ Select one of the four serial ports as a rescue port. The default
+ is port 0.
+
+Serial-1
+CONFIG_ETRAX_RESCUE_SER1
+ Use serial port 1 as the rescue port.
+
+Serial-2
+CONFIG_ETRAX_RESCUE_SER2
+ Use serial port 2 as the rescue port.
+
+Serial-3
+CONFIG_ETRAX_RESCUE_SER3
+ Use serial port 3 as the rescue port.
+
+RIO Hardware Watchdog support
+CONFIG_WATCHDOG_RIO
+ Say Y here to support the hardware watchdog capability on Sun RIO
+ machines. The watchdog timeout period is normally one minute but
+ can be changed with a boot-time parameter.
CP1XXX Hardware Watchdog support
CONFIG_WATCHDOG_CP1XXX
@@ -19066,12 +23367,22 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called cpwatchdog.o. If you want to compile it
- as a module, say M here and read Documentation/modules.txt.
+ as a module, say M here and read <file:Documentation/modules.txt>.
If you do not have a CompactPCI model CP1400 or CP1500, or
another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
- you should say N to this option.
+ you should say N to this option.
+
+# Choice: ia64type
+Itanium
+CONFIG_ITANIUM
+ Select your IA64 processor type. The default is Intel Itanium.
+
+McKinley
+CONFIG_MCKINLEY
+ Select this to configure for a McKinley processor.
+# Choice: ia64system
IA-64 system type
CONFIG_IA64_GENERIC
This selects the system type of your hardware. A "generic" kernel
@@ -19079,19 +23390,21 @@
a kernel for your specific system, it will be faster and smaller.
To find out what type of IA-64 system you have, you may want to
- check the IA-64 Linux web site at http://www.linux-ia64.org/.
+ check the IA-64 Linux web site at <http://www.linux-ia64.org/>.
As of the time of this writing, most hardware is DIG compliant,
so the "DIG-compliant" option is usually the right choice.
- HP-simulator For the HP simulator (http://software.hp.com/ia64linux/).
+ HP-simulator For the HP simulator
+ (<http://software.hp.com/ia64linux/>).
SN1-simulator For the SGI SN1 simulator.
- DIG-compliant For DIG ("Developer's Interface Guide") compliant system.
+ DIG-compliant For DIG ("Developer's Interface Guide") compliant
+ system.
If you don't know what to do, choose "generic".
+# Choice: pagesize
Kernel page size
CONFIG_IA64_PAGE_SIZE_4KB
-
This lets you select the page size of the kernel. For best IA-64
performance, a page size of 8KB or 16KB is recommended. For best
IA-32 compatibility, a page size of 4KB should be selected (the vast
@@ -19109,8 +23422,8 @@
Enable Itanium A-step specific code
CONFIG_ITANIUM_ASTEP_SPECIFIC
Select this option to build a kernel for an Itanium prototype system
- with an A-step CPU. You have an A-step CPU if the "revision" field in
- /proc/cpuinfo is 0.
+ with an A-step CPU. You have an A-step CPU if the "revision" field
+ in /proc/cpuinfo is 0.
Enable Itanium B-step specific code
CONFIG_ITANIUM_BSTEP_SPECIFIC
@@ -19120,9 +23433,33 @@
Enable Itanium B0-step specific code
CONFIG_ITANIUM_B0_SPECIFIC
- Select this option to bild a kernel for an Itanium prototype system
- with a B0-step CPU. You have a B0-step CPU if the "revision" field in
- /proc/cpuinfo is 1.
+ Select this option to build a kernel for an Itanium prototype system
+ with a B0-step CPU. You have a B0-step CPU if the "revision" field
+ in /proc/cpuinfo is 1.
+
+Enable Itanium C-step specific code
+CONFIG_ITANIUM_CSTEP_SPECIFIC
+ Select this option to build a kernel for an Itanium prototype system
+ with a C-step CPU. You have a C-step CPU if the "revision" field in
+ /proc/cpuinfo is in the range of 5 to 8.
+
+Enable Itanium B1-step specific code
+CONFIG_ITANIUM_B1_SPECIFIC
+ Select this option to build a kernel for an Itanium prototype system
+ with a B1-step CPU. You have a B1-step CPU if the "revision" field
+ in /proc/cpuinfo is 2.
+
+Enable Itanium B2-step specific code
+CONFIG_ITANIUM_B2_SPECIFIC
+ Select this option to build a kernel for an Itanium prototype system
+ with a B2-step CPU. You have a B2-step CPU if the "revision" field
+ in /proc/cpuinfo is 3.
+
+Enable Itanium C0-step specific code
+CONFIG_ITANIUM_C0_SPECIFIC
+ Select this option to build a kernel for an Itanium prototype system
+ with a C0-step CPU. You have a C0-step CPU if the "revision" field
+ in /proc/cpuinfo is 5.
Force interrupt redirection
CONFIG_IA64_HAVE_IRQREDIR
@@ -19130,38 +23467,56 @@
redirect interrupts to different CPUs. Select N here if you're
unsure.
-Enable use of global TLB purge instruction (ptc.g)
-CONFIG_ITANIUM_PTCG
- Say Y here if you want the kernel to use the IA-64 "ptc.g"
- instruction to flush the TLB on all CPUs. Select N here if
- you're unsure.
-
-Enable SoftSDV hacks
-CONFIG_IA64_SOFTSDV_HACKS
- Say Y here to enable hacks to make the kernel work on the Intel
- SoftSDV simulator. Select N here if you're unsure.
-
-Enable AzusA hacks
-CONFIG_IA64_AZUSA_HACKS
- Say Y here to enable hacks to make the kernel work on the NEC
- AzusA platform. Select N here if you're unsure.
-
-Force socket buffers below 4GB?
-CONFIG_SKB_BELOW_4GB
- Most of today's network interface cards (NICs) support DMA to
- the low 32 bits of the address space only. On machines with
- more then 4GB of memory, this can cause the system to slow
- down if there is no I/O TLB hardware. Turning this option on
- avoids the slow-down by forcing socket buffers to be allocated
- from memory below 4GB. The downside is that your system could
- run out of memory below 4GB before all memory has been used up.
- If you're unsure how to answer this question, answer Y.
-
Enable IA-64 Machine Check Abort
CONFIG_IA64_MCA
Say Y here to enable machine check support for IA-64. If you're
unsure, answer Y.
+Disable IA-64 Virtual Hash Page Table
+CONFIG_DISABLE_VHPT
+ The Virtual Hash Page Table (VHPT) enhances virtual address
+ translation performance. Normally you want the VHPT active but you
+ can select this option to disable the VHPT for debugging. If you're
+ unsure, answer N.
+
+Enable McKinley A-step specific code
+CONFIG_MCKINLEY_ASTEP_SPECIFIC
+ Select this option to build a kernel for an IA64 McKinley system
+ with any A-stepping CPU.
+
+Enable McKinley A0/A1-step specific code
+CONFIG_MCKINLEY_A0_SPECIFIC
+ Select this option to build a kernel for an IA64 McKinley system
+ with an A0 or A1 stepping CPU.
+
+Turn on compare-and-exchange bug checking (slow!)
+CONFIG_IA64_DEBUG_CMPXCHG
+ Selecting this option turns on bug checking for the IA64
+ compare-and-exchange instructions. This is slow! Itaniums
+ from step B3 or later don't have this problem. If you're unsure,
+ select N.
+
+IA64 IRQ bug checking
+CONFIG_IA64_DEBUG_IRQ
+ Selecting this option turns on bug checking for the IA64 irq_save
+ and restore instructions. It's useful for tracking down spinlock
+ problems, but slow! If you're unsure, select N.
+
+Early printk support (requires VGA!)
+CONFIG_IA64_EARLY_PRINTK
+ Selecting this option uses the VGA screen for printk() output before
+ the consoles are initialised. It is useful for debugging problems
+ early in the boot process, but only if you have a VGA screen
+ attached. If you're unsure, select N.
+
+Print possible IA64 hazards to console
+CONFIG_IA64_PRINT_HAZARDS
+ Selecting this option prints more information for Illegal Dependency
+ Faults, that is, for Read after Write, Write after Write or Write
+ after Read violations. This option is ignored if you are compiling
+ for an Itanium A step processor (CONFIG_ITANIUM_ASTEP_SPECIFIC). If
+ you're unsure, select Y.
+
Performance monitor support
CONFIG_PERFMON
Selects whether support for the IA-64 performance monitor hardware
@@ -19179,12 +23534,416 @@
To use this option, you have to check that the "/proc file system
support" (CONFIG_PROC_FS) is enabled, too.
+Kernel support for IA-32 emulation
+CONFIG_IA32_SUPPORT
+ IA64 processors can run IA32 (that is, x86) binaries by emulating
+ the IA32 instruction set. Say Y here to build in kernel support for
+ this. If in doubt, say Y.
+
+/proc/efi/vars support
+CONFIG_IA64_EFIVARS
+ If you say Y here, you are able to get EFI (Extensible Firmware
+ Interface) variable information in /proc/efi/vars. You may read,
+ write, create, and destroy EFI variables through this interface.
+
+ To use this option, you have to check that the "/proc file system
+ support" (CONFIG_PROC_FS) is enabled, too.
+
+Directly Connected Compact Flash support
+CONFIG_CF_ENABLER
+ Compact Flash is a small, removable mass storage device introduced
+ in 1994 originally as a PCMCIA device. If you say `Y' here, you
+ compile in support for Compact Flash devices directly connected to
+ a SuperH processor. A Compact Flash FAQ is available at
+ <http://www.compactflash.org/faqs/faq.htm>.
+
+ If your board has "Directly Connected" CompactFlash at area 5 or 6,
+ you may want to enable this option. Then, you can use CF as
+ primary IDE drive (only tested for SanDisk).
+
+ If in doubt, select 'N'.
+
+Kernel debugging
+CONFIG_DEBUG_KERNEL
+ Say Y here if you are developing drivers or trying to debug and
+ identify kernel problems.
+
+Debug memory allocations
+CONFIG_DEBUG_SLAB
+ Say Y here to have the kernel do limited verification on memory
+ allocation as well as poisoning memory on free to catch use of freed
+ memory.
+
+Memory mapped I/O debug support
+CONFIG_DEBUG_IOVIRT
+ Say Y here to get warned whenever an attempt is made to do I/O on
+ obviously invalid addresses such as those generated when ioremap()
+ calls are forgotten. Memory mapped I/O will go through an extra
+ check to catch access to unmapped ISA addresses, an access method
+ that can still be used by old drivers that are being ported from
+ 2.0/2.2.
+
+Spinlock debugging
+CONFIG_DEBUG_SPINLOCK
+ Say Y here and build SMP to catch missing spinlock initialization
+ and certain other kinds of spinlock errors commonly made. This is
+ best used in conjunction with the NMI watchdog so that spinlock
+ deadlocks are also debuggable.
+
+Verbose BUG() reporting (adds 70K)
+CONFIG_DEBUG_BUGVERBOSE
+ Say Y here to make BUG() panics output the file name and line number
+ of the BUG call as well as the EIP and oops trace. This aids
+ debugging but costs about 70-100K of memory.
+
+Include kgdb kernel debugger
+CONFIG_KGDB
+ Include in-kernel hooks for kgdb, the Linux kernel source level
+ debugger. This project has a web page at
+ <http://kgdb.sourceforge.net/>.
+
+Include xmon kernel debugger
+CONFIG_XMON
+ Include in-kernel hooks for the xmon kernel monitor/debugger
+ supported by the PPC port.
+
+Include kgdb kernel debugger
+CONFIG_KWDB
+ Include in-kernel hooks for kdb, the source level debugger for the
+ PA-RISC port.
+
+IODC console
+CONFIG_IODC_CONSOLE
+ IODC is HP's pre-PCI standard for device identification (a la PCI
+ vendor, device IDs), detection, configuration, initialization and so
+ on. It also can provide firmware function to do the actual IO,
+ which are slow, not really defined for runtime usage and generally
+ not desirable.
+
+ See <http://www.linuxhq.com/kernel/v2.4/doc/parisc/IODC.txt.html>
+ for the gory details.
+
+ Say Y here to enable use of the IODC firmware functions for console
+ I/O. This is only useful on older PA-RISC workstations. If in
+ doubt, say Y.
+
+U2/Uturn I/O MMU
+CONFIG_IOMMU_CCIO
+ Say Y here to enable DMA management routines for the first
+ generation of PA-RISC cache-coherent machines. Programs the
+ U2/Uturn chip in "Virtual Mode" and use the I/O MMU.
+
+LBA/Elroy PCI support
+CONFIG_PCI_LBA
+ Say Y here to give the PA-RISC kernel access to PCI configuration
+ and IO-port space on PA-RISC workstations equipped with a Lower Bus
+ Adapter (LBA). This includes A, B, C, J, L, and N-class machines
+ with 4-digit model numbers, also the A300.
+
+LASI I/O support
+CONFIG_GSC_LASI
+ Say Y here to directly support the LASI controller chip found on
+ PA-RISC workstations. Linux-oriented documentation for this chip
+ can be found at <http://www.parisc-linux.org/documentation/>.
+
+LASI/ASP builtin parallel-port
+CONFIG_PARPORT_GSC
+ Say Y here to build in low-level parallel-support for PC-style
+ hardware integrated in the LASI-Controller (on the GSC Bus) for
+ HP-PARISC workstations.
+
+Fujitsu Vendor Specific
+CONFIG_BLK_DEV_IDEDISK_FUJITSU
+ Enable vendor-specific code for Fujitsu IDE disks. Unless you are
+ the IDE maintainer, you probably do not want to mess with this.
+
+IBM Vendor Specific
+CONFIG_BLK_DEV_IDEDISK_IBM
+ Enable vendor-specific code for IBM IDE disks. Unless you are the
+ IDE maintainer, you probably do not want to mess with this.
+
+Maxtor Vendor Specific
+CONFIG_BLK_DEV_IDEDISK_MAXTOR
+ Enable vendor-specific code for Maxtor IDE disks. Unless you are
+ the IDE maintainer, you probably do not want to mess with this.
+
+Quantum Vendor Specific
+CONFIG_BLK_DEV_IDEDISK_QUANTUM
+ Enable vendor-specific code for Quantum IDE disks. Unless you are
+ the IDE maintainer, you probably do not want to mess with this.
+
+Seagate Vendor Specific
+CONFIG_BLK_DEV_IDEDISK_SEAGATE
+ Enable vendor-specific code for Seagate IDE disks. Unless you are
+ the IDE maintainer, you probably do not want to mess with this.
+
+Western Digital Vendor Specific
+CONFIG_BLK_DEV_IDEDISK_WD
+ Enable vendor-specific code for Western Digital IDE disks. Unless
+ you are the IDE maintainer, you probably do not want to mess with
+ this.
+
+TiVo Commerial Application Specific
+CONFIG_BLK_DEV_TIVO
+ Enable vendor-specific code for TiVo IDE disks. Unless you are the
+ IDE maintainer, you probably do not want to mess with this.
+
+# Choice: superhsys
+Generic
+CONFIG_SH_GENERIC
+ Select Generic if configuring for a generic SuperH system.
+ The "generic" option compiles in *all* the possible hardware
+ support and relies on the sh_mv= kernel commandline option to choose
+ at runtime which routines to use. "MV" stands for "machine vector";
+ each of the machines below is described by a machine vector.
+
+ Select SolutionEngine if configuring for a Hitachi SH7709
+ or SH7750 evalutation board.
+
+ Select Overdrive if configuring for a ST407750 Overdrive board.
+ More information at
+ <http://linuxsh.sourceforge.net/docs/7750overdrive.php3>.
+
+ Select HP620 if configuring for a HP Jornada HP620.
+ More information (hardware only) at
+ <http://www.hp.com/jornada>.
+
+ Select HP680 if configuring for a HP Jornada HP680.
+ More information (hardware only) at
+ <http://www.hp.com/jornada/products/680>.
+
+ Select HP690 if configuring for a HP Jornada HP690.
+ More information (hardware only) at
+ <http://www.hp.com/jornada/products/680>.
+
+ Select CqREEK if configuring for a CqREEK SH7708 or SH7750.
+ More information at
+ <http://sources.redhat.com/ecos/hardware.html#SuperH>.
+
+ Select DMIDA if configuring for a DataMyte 4000 Industrial
+ Digital Assistant. More information at <http://www.dmida.com>.
+
+ Select EC3104 if configuring for a system with an Eclipse
+ International EC3104 chip, e.g. the Harris AD2000.
+
+ Select Dreamcast if configuring for a SEGA Dreamcast.
+ More information at
+ <http://www.m17n.org/linux-sh/dreamcast>. There is a
+ Dreamcast project is at <http://linuxdc.sourceforge.net/>.
+
+ Select BareCPU if you know what this means, and it applies
+ to your system.
+
+SolutionEngine
+CONFIG_SH_SOLUTION_ENGINE
+ Select SolutionEngine if configuring for a Hitachi SH7709
+ or SH7750 evalutation board.
+
+7751 SolutionEngine
+CONFIG_SH_7751_SOLUTION_ENGINE
+ Select 7751 SolutionEngine if configuring for a Hitachi SH7751
+ evalutation board.
+
+Overdrive
+CONFIG_SH_OVERDRIVE
+ Select Overdrive if configuring for a ST407750 Overdrive board.
+ More information at
+ <http://linuxsh.sourceforge.net/docs/7750overdrive.php3>.
+
+HP620
+CONFIG_SH_HP620
+ Select HP620 if configuring for a HP jornada HP620.
+ More information (hardware only) at
+ <http://www.hp.com/jornada>.
+
+HP680
+CONFIG_SH_HP680
+ Select HP680 if configuring for a HP Jornada HP680.
+ More information (hardware only) at
+ <http://www.hp.com/jornada/products/680>.
+
+HP690
+CONFIG_SH_HP690
+ Select HP690 if configuring for a HP Jornada HP690.
+ More information (hardware only)
+ at <http://www.hp.com/jornada/products/680>.
+
+CqREEK
+CONFIG_SH_CQREEK
+ Select CqREEK if configuring for a CqREEK SH7708 or SH7750.
+ More information at
+ <http://sources.redhat.com/ecos/hardware.html#SuperH>.
+
+DMIDA
+CONFIG_SH_DMIDA
+ Select DMIDA if configuring for a DataMyte 4000 Industrial
+ Digital Assistant. More information at <http://www.dmida.com>.
+
+EC3104
+CONFIG_SH_EC3104
+ Select EC3104 if configuring for a system with an Eclipse
+ International EC3104 chip, e.g. the Harris AD2000.
+
+Dreamcast
+CONFIG_SH_DREAMCAST
+ Select Dreamcast if configuring for a SEGA Dreamcast.
+ More information at
+ <http://www.m17n.org/linux-sh/dreamcast>. There is a
+ Dreamcast project is at <http://linuxdc.sourceforge.net/>.
+
+BareCPU
+CONFIG_SH_UNKNOWN
+ "Bare CPU" aka "unknown" means an SH-based system which is not one
+ of the specific ones mentioned above, which means you need to enter
+ all sorts of stuff like CONFIG_MEMORY_START because the config
+ system doesn't already know what it is. You get a machine vector
+ without any platform-specific code in it, so things like the RTC may
+ not work.
+
+ This option is for the early stages of porting to a new machine.
+
+# Choice: superhtype
+SH7707
+CONFIG_CPU_SUBTYPE_SH7707
+ Select the type of SuperH processor you have.
+
+ Select SH7707 if you have a 60 Mhz SH-3 HD6417707 CPU.
+
+ Select SH7708 if you have a 60 Mhz SH-3 HD6417708S or
+ if you have a 100 Mhz SH-3 HD6417708R CPU.
+
+ Select SH7709 if you have a 80 Mhz SH-3 HD6417709 CPU.
+
+ Select SH7750 if you have a 200 Mhz SH-4 HD6417750 CPU.
+
+SH7708
+CONFIG_CPU_SUBTYPE_SH7708
+ Select SH7708 if you have a 60 Mhz SH-3 HD6417708S or
+ if you have a 100 Mhz SH-3 HD6417708R CPU.
+
+SH7709
+CONFIG_CPU_SUBTYPE_SH7709
+ Select SH7709 if you have a 80 Mhz SH-3 HD6417709 CPU.
+
+SH7750
+CONFIG_CPU_SUBTYPE_SH7750
+ Select SH7750 if you have a 200 Mhz SH-4 HD6417750 CPU.
+
+Physical memory start address
+CONFIG_MEMORY_START
+ The physical memory start address will be automatically
+ set to 08000000, unless you selected one of the following
+ processor types: SolutionEngine, Overdrive, HP620, HP680, HP690,
+ in which case the start address will be set to 0c000000.
+
+ Tweak this only when porting to a new machine which is not already
+ known by the config system. Changing it from the known correct
+ value on any of the known systems will only lead to disaster.
+
+Hitachi HD64461 companion chip support
+CONFIG_HD64461
+ The Hitachi HD64461 provides an interface for
+ the SH7709 CPU, supporting a LCD controller,
+ CRT color controller, IrDA up to 4 Mbps, and a
+ PCMCIA controller supporting 2 slots.
+
+ More information is available at
+ <http://semiconductor.hitachi.com/windowsce/superh/sld013.htm>.
+
+ Say Y if you want support for the HD64461.
+ Otherwise, say N.
+
+HD64461 PCMCIA enabler
+CONFIG_HD64461_ENABLER
+ Say Y here if you want to enable PCMCIA support
+ via the HD64461 companion chip.
+ Otherwise, say N.
+
+HD64461 virtualized IRQ number
+CONFIG_HD64461_IRQ
+ The default setting of the HD64461 IRQ is 36.
+
+ Do not change this unless you know what you are doing.
+
+Hitachi HD64465 companion chip support
+CONFIG_HD64465
+ The Hitachi HD64465 provides an interface for
+ the SH7750 CPU, supporting a LCD controller,
+ CRT color controller, IrDA, USB, PCMCIA,
+ keyboard controller, and a printer interface.
+
+ More information is available at
+ <http://global.hitachi.com/New/cnews/E/1998/981019B.html>.
+
+ Say Y if you want support for the HD64465.
+ Otherwise, say N.
+
+HD64465 virtualized IRQ number
+CONFIG_HD64465_IRQ
+ The default setting of the HD64465 IRQ is 5.
+
+ Do not change this unless you know what you are doing.
+
+HD64465 start address
+CONFIG_HD64465_IOBASE
+ The default setting of the HD64465 IO base address is 0xb0000000.
+
+ Do not change this unless you know what you are doing.
+
+Early printk support
+CONFIG_SH_EARLY_PRINTK
+ Say Y here to redirect kernel messages to the serial port
+ used by the SH-IPL bootloader, starting very early in the boot
+ process and ending when the kernel's serial console is initialised.
+ This option is only useful porting the kernel to a new machine,
+ when the kernel may crash or hang before the serial console is
+ initialised.
+
+SuperH SCI (serial) support
+CONFIG_SH_SCI
+ Selecting this option will allow the Linux kernel to transfer data
+ over SCI (Serial Communication Interface) and/or SCIF (Serial
+ Communication Interface with FIFO) which are built into the Hitachi
+ SuperH processor. The option provides 1 to 3 (depending
+ on the CPU model) standard Linux tty devices, /dev/ttySC[012]; one
+ of these is normally used as the system console.
+
+ If in doubt, press "y".
+
+Use LinuxSH standard BIOS
+CONFIG_SH_STANDARD_BIOS
+ Say Y here if your target has the gdb-sh-stub
+ package from www.m17n.org (or any conforming standard LinuxSH BIOS)
+ in FLASH or EPROM. The kernel will use standard BIOS calls during
+ boot for various housekeeping tasks (including calls to read and
+ write characters to a system console, get a MAC address from an
+ on-board Ethernet interface, and shut down the hardware). Note this
+ does not work with machines with an existing operating system in
+ mask ROM and no flash (WindowsCE machines fall in this category).
+ If unsure, say N.
+
+GDB Stub kernel debug
+CONFIG_DEBUG_KERNEL_WITH_GDB_STUB
+ If you say Y here, it will be possible to remotely debug the SuperH
+ kernel using gdb, if you have the gdb-sh-stub package from
+ www.m17n.org (or any conforming standard LinuxSH BIOS) in FLASH or
+ EPROM. This enlarges your kernel image disk size by several
+ megabytes but allows you to load, run and debug the kernel image
+ remotely using gdb. This is only useful for kernel hackers. If
+ unsure, say N.
+
+Console output to GDB
+CONFIG_GDB_CONSOLE
+ If you are using GDB for remote debugging over a serial port and
+ would like kernel messages to be formatted into GDB $O packets so
+ that GDB prints them as program output, say 'Y'.
+
#
# A couple of things I keep forgetting:
-# capitalize: AppleTalk, Ethernet, DOS, DMA, FAT, FTP, Internet,
-# Intel, IRQ, ISDN, Linux, MSDOS, NetWare, NetWinder,
+# capitalize: AppleTalk, Ethernet, DOS, DMA, FAT, FTP, Internet,
+# Intel, IRQ, ISDN, Linux, MSDOS, NetWare, NetWinder,
# NFS, PCI, SCSI, SPARC
-# two words: file system, hard drive, hard disk, home page,
+# two words: file system, hard drive, hard disk, home page,
# user space, web site
# other: it's safe to save; daemon; use --, not - or ---;
# use KB for 1024 bytes, not kB or K.
@@ -19195,13 +23954,13 @@
# LocalWords: CONFIG coprocessor DX Pentium SX lilo loadlin HOWTO ftp metalab
# LocalWords: unc edu docs emu README kB BLK DEV FD Thinkpad fd MFM RLL IDE gz
# LocalWords: cdrom diskless netboot nfs xzvf ATAPI MB ide pavia rubini pl pd
-# LocalWords: HD CDROMs IDECD NEC MITSUMI filesystem XT XD PCI BIOS cezar ATEN
+# LocalWords: HD CD-ROMs IDECD NEC MITSUMI filesystem XT XD PCI BIOS cezar ATEN
# LocalWords: ISA EISA Microchannel VESA BIOSes IPC SYSVIPC ipc Ctrl dmesg hlt
# LocalWords: BINFMT Linkable http ac uk jo html GCC SPARC AVANTI CABRIOLET EB
# LocalWords: netscape gcc LD CC toplevel MODVERSIONS insmod rmmod modprobe IP
-# LocalWords: genksyms INET loopback gatewaying ethernet PPP ARP Arp MEMSIZE
+# LocalWords: genksyms INET loopback gatewaying Ethernet PPP ARP Arp MEMSIZE
# LocalWords: howto multicasting MULTICAST MBONE firewalling ipfw ACCT resp ip
-# LocalWords: proc acct IPIP encapsulator decapsulator klogd PCTCP RARP EXT PS
+# LocalWords: proc acct IPIP encapsulator decapsulator klogd RARP EXT PS
# LocalWords: telnetting subnetted NAGLE rlogin NOSR ttyS TGA techinfo mbone nl
# LocalWords: Mb SKB IPX Novell dosemu DDP ATALK vmalloc visar ehome
# LocalWords: SD CHR scsi thingy SG CD LUNs LUN jukebox Adaptec BusLogic EATA
@@ -19255,11 +24014,11 @@
# LocalWords: FC DC dc PPA IOMEGA's ppa RNFS FMV Fujitsu ARPD arpd loran layes
# LocalWords: FRAD indiana framerelay DLCI DCLIs Sangoma SDLA mrouted sync sec
# LocalWords: Starmode Metricom MosquitoNet mosquitonet kbit nfsroot Digiboard
-# LocalWords: DIGI Xe Xeve digiboard UMISC touchscreens mtu ethernets HBAs MEX
+# LocalWords: DIGI Xe Xeve digiboard UMISC touchscreens mtu Ethernets HBAs MEX
# LocalWords: Shifflett netcom js jshiffle WIC DECchip ELCP EtherPower dst RTC
# LocalWords: rtc SMP lp Digi Intl RightSwitch DGRS dgrs AFFS Amiga UFS SDL AP
# LocalWords: Solaris RISCom riscom syncPPP PCBIT pcbit sparc anu au artoo MFB
-# LocalWords: hitchcock Crynwr cnam pktdrvr NCSA's CyDROM CyCDROM FreeBSD NeXT
+# LocalWords: hitchcock Crynwr cnam pktdrvr NCSA's CyDROM CyCD-ROM FreeBSD NeXT
# LocalWords: NeXTstep disklabel disklabels SMD FFS tm AmigaOS diskfiles Un IQ
# LocalWords: Bernd informatik rwth aachen uae affs multihosting bytecode java
# LocalWords: applets applet JDK ncsa cabi SNI Alphatronix readme LANs scarab
@@ -19275,7 +24034,7 @@
# LocalWords: mgetty sendfax gert greenie muc lowlevel Lasermate LanManager io
# LocalWords: OOPSes trackball binghamton mobileip ncr IOMAPPED settags ns ser
# LocalWords: setsync NEGO MPARITY autotuning prefetch PIIX cdwrite utils rc
-# LocalWords: PCWATCHDOG berkprod bitgate boldt ucsb jf kyoto jp euc Tetsuyasu
+# LocalWords: PCWATCHDOG berkprod bitgate boldt ucsb jf kyoto jp euc Tetsuyasu
# LocalWords: YAMADA tetsu cauchy nslab ntt nevod perm su doc kaf kheops wsc
# LocalWords: traduc Bourgin dbourgin menuconfig kfill READMEs HOWTOs Virge WA
# LocalWords: IDEDISK IDEFLOPPY EIDE firewalls QMAGIC ZMAGIC LocalWords opti
@@ -19338,7 +24097,7 @@
# LocalWords: prio Micom xIO dwmw rimi OMIRR omirr omirrd unicode ntfs cmu NIC
# LocalWords: Braam braam Schmidt's freiburg nls codepages codepage Romanian
# LocalWords: Slovak Slovenian Sorbian Nordic iso Catalan Faeroese Galician SZ
-# LocalWords: Valencian Slovene Esperanto Estonian Latvian Byelorussian KOI mt
+# LocalWords: Valencian Slovene Esperanto Estonian Latvian Belarusian KOI mt
# LocalWords: charset Inuit Greenlandic Sami Lappish koi Alexey Kuznetsov's sa
# LocalWords: Specialix specialix DTR RTS RTSCTS cycladesZ Exabyte ftape's inr
# LocalWords: Iomega's LBFM claus ZFTAPE VFS zftape zft William's lzrw DFLT kb
@@ -19404,7 +24163,7 @@
# LocalWords: uit dagb irda LSAP IrLMP RR's IrLAP IR alloc skb's kfree skb's
# LocalWords: GZIP IrLAN NetbeamIR ESI JetEye IrOBEX IrCOMM TTY's minicom dti
# LocalWords: ircomm ircomm pluto thiguchi IrTTY Linux's bps NetWinder MIR NSC
-# LocalWords: ACTiSYS Dongle dongle dongles esi actisys IrMate tekram BVM MVME
+# LocalWords: ACTiSYS dongle dongles esi actisys IrMate tekram BVM MVME
# LocalWords: BVME BVME WRITETHROUGH copyback writethrough fwmark syncookie tu
# LocalWords: alphalinux GOBIOS csn chemnitz nat ACARD AMI MegaRAID megaraid
# LocalWords: QNXFS ISI isicom xterms Apollos VPN RCPCI rcpci sgi visws pcmcia
@@ -19416,7 +24175,7 @@
# LocalWords: SKMC USB UHCI OHCI intel compaq usb ohci HCD Virt Compaq's hcd
# LocalWords: VROOTHUB KBD ARRs MCRs NWBUTTON nwbutton NUM WaveArtist APNE cpu
# LocalWords: apne blackhawke PlanB lu mlan planb NWFPE FPA nwfpe unbootable
-# LocalWords: FPEmulator ds vmlinux initialisation discardable pgtable PGT mdw
+# LocalWords: FPEmulator ds vmlinux initialization discardable pgtable PGT mdw
# LocalWords: quicklist pagetable arthur StrongARM podule podules Autodetect
# LocalWords: dodgy IrPORT irport Litelink litelink SuSE rtfm internet hda CY
# LocalWords: multmode DriveReady SeekComplete DriveStatusError miscompile AEC
@@ -19445,7 +24204,7 @@
# LocalWords: VWSND eg ESSSOLO CFU CFNR scribed eiconctrl eicon hylafax KFPU
# LocalWords: EXTRAPREC fpu mainboards KHTTPD kHTTPd khttpd Xcelerator SBNI tw
# LocalWords: LOGIBUSMOUSE Granch granch sbni Raylink NOHIGHMEM Athlon SIM sim
-# LocalWords: hpl Tourrilhes DuraLAN starfile Davicom davicom dmfe auk tms tr
+# LocalWords: hpl Tourrilhes DuraLAN starfire Davicom davicom dmfe auk tms tr
# LocalWords: TokenExpress Belkin Peracom eTek DVDs infradead Cxxx Adlib AV ZX
# LocalWords: NeoMagic CPi CPt Celeron decapsulation Undeletion BFS bfs nVidia
# LocalWords: OnStream Irongate Riva phonedev QuickNet LineJack PhoneJack IXJ
@@ -19465,7 +24224,7 @@
# LocalWords: DEVS FireWire PCILynx pcilynx LOCALRAM miro's DV RAWIO GRED Mk
# LocalWords: Diffserv DSMARK Ingress Qdisc TCINDEX TMSPCI tmspci Ringode JE
# LocalWords: MADGEMC madgemc TokenRing SMCTR TokenCard smctr Wacom Graphire
-# LocalWords: WMFORCE mousedev ConnectTech HandSpring Xirlink IBMCAM ibmcam SN
+# LocalWords: mousedev ConnectTech HandSpring Xirlink IBMCAM ibmcam SN
# LocalWords: DEVICEFS yyy Cymraeg Dwave SIMM JSFLASH JavaStation's multilink
# LocalWords: nsc ircc DDB Vrc CMN TB PROMs Vino rivafb DDC Matroxes MGA TVO
# LocalWords: MAVEN fbdev crtc maven matroxset NTSC PCA SBA AAL SKFP DAS SAS
@@ -19495,3 +24254,11 @@
# LocalWords: DMX Domex dmx wellington ftdi sio Accton Billington Corega FEter
# LocalWords: MELCO LUA PNA Linksys SNC chkdsk AWACS Webcam RAMFS Ramfs ramfs
# LocalWords: ramfiles MAKEDEV pty WDTPCI APA apa
+#
+# The following sets edit modes for GNU EMACS
+# Local Variables:
+# case-fold-search:nil
+# fill-prefix:" "
+# adaptive-fill:nil
+# fill-column:70
+# End:
FUNET's LINUX-ADM group, linux-adm@nic.funet.fi
TCL-scripts by Sam Shen (who was at: slshen@lbl.gov)