#
# 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 user who has just bought a PC, removed Windows,
-# installed Linux and is now recompiling the kernel for the first
-# time. Tell them what to do if they're unsure. Technical information
-# should go in a README in the Documentation directory. Mention all
-# the relevant READMEs and HOWTOs in the help text.
+# hypothetical ignorant but intelligent user who has just bought a PC,
+# removed Windows, installed Linux and is now recompiling the kernel
+# for the first time. Tell them what to do if they're
+# unsure. Technical information should go in a README in the
+# Documentation directory. Mention all the relevant READMEs and HOWTOs
+# in the help text.
#
# All this was shamelessly stolen from several different sources. Many
# thanks to all the contributors. Feel free to use these help texts
# in your own kernel configuration tools. The texts are copyrighted
-# (c) 1995,1996 by Axel Boldt and governed by the GNU Public License.
+# (c) 1995-1997 by Axel Boldt and others and governed by the GNU
+# Public License.
Prompt for development and/or incomplete code/drivers
CONFIG_EXPERIMENTAL
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.
+ 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, Documentation/BUG-HUNTING, and
+ Documentation/oops-tracing.txt in the kernel source).
Unless you intend to help test and develop a feature or driver that
- falls into this category, or you have a situation that requires using
- these features you should probably say N here, which will cause this
- configure script to present you with fewer choices. If you say Y here,
- you will be offered the choice of using features or drivers that are
- currently considered to be in the alpha-test phase.
+ falls into this category, or you have a situation that requires
+ using these features you should probably say N here, which will
+ cause this configure script to present you with fewer choices. If
+ you say Y here, you will be offered the choice of using features or
+ drivers that are currently considered to be in the alpha-test phase.
Kernel math emulation
CONFIG_MATH_EMULATION
a math coprocessor built in, 486SX and 386 do not, unless you added
a 487DX or 387, respectively. (The messages during boot time can
give you some hints here ["man dmesg"]) Everyone needs either a
- coprocessor or this emulation. If you enable this emulation even
+ coprocessor or this emulation. If you say Y here even
though you have a coprocessor, the coprocessor will be used
nevertheless. (This behavior can be changed with the kernel command
line option "no387", which comes handy if your coprocessor is
- broken. See the documentation of your boot loader (lilo or loadlin)
- about how to pass options to the kernel at boot time. The lilo
- procedure is also explained in the SCSI-HOWTO, available via ftp
- (user: anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO.) This
- means that it is a good idea to say Y here if you intend to use this
- kernel on different machines. More information about the internals
- of Linux math coprocessor emulation can be found in
- arch/i386/math-emu/README. If you are not sure, say Y; apart from
- resulting in a 45kB bigger kernel, it won't hurt.
+ broken. Try "man bootparam" or see the documentation of your boot
+ loader (lilo or loadlin) about how to pass options to the kernel at
+ boot time. The lilo procedure is also explained in the SCSI-HOWTO,
+ available via ftp (user: anonymous) in
+ sunsite.unc.edu:/pub/Linux/docs/HOWTO.) This means that it is a good
+ idea to say Y here if you intend to use this kernel on different
+ machines. More information about the internals of Linux math
+ coprocessor emulation can be found in arch/i386/math-emu/README. If
+ you are not sure, say Y; apart from resulting in a 45kB bigger
+ kernel, it won't hurt.
Normal floppy disk support
CONFIG_BLK_DEV_FD
If you want to use your floppy disk drive(s) under Linux, say
Y. Information about this driver, especially important for IBM
- Thinkpad users, is contained in drivers/block/README.fd. 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
+ Thinkpad users, is contained in drivers/block/README.fd. This 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.
RAM disk support
CONFIG_BLK_DEV_RAM
- Enabling this option will allow you to use a portion of your RAM
- memory as a block device, so that you can make filesystems on it,
- read and write to it and do all the other things that normal block
- devices (such as harddrives) can do. It is usually used to load and
+ Saying Y here will allow you to use a portion of your RAM memory as
+ a block device, so that you can make filesystems on it, read and
+ write to it and do all the other things that you can do with normal
+ block devices (such as harddrives). It is usually used to load and
store a copy of a minimal root file system off of a floppy into RAM
during the initial install of Linux. Note that the kernel command
line option "ramdisk=XX" is now obsolete. For details, read
Documentation/ramdisk.txt. If you want to compile this as a module (
= code which can be inserted in and removed from the running kernel
- whenever you want), say M and read Documentation/modules.txt. Most
- normal users won't need the RAM disk functionality, and can thus say
- N here.
+ whenever you want), say M and read Documentation/modules.txt. The
+ module will be called rd.o. Most normal users won't need the RAM
+ disk functionality, and can thus say N here.
Initial RAM disk (initrd) support
CONFIG_BLK_DEV_INITRD
The initial RAM disk is a RAM disk that is loaded by the boot loader
- (LOADLIN or LILO) and that is mounted as root before the normal boot
+ (loadlin or lilo) and that is mounted as root before the normal boot
procedure. It is typically used to load modules needed to mount the
"real" root file system, etc. See Documentation/initrd.txt for
details.
Loop device support
CONFIG_BLK_DEV_LOOP
- Enabling this option will allow you to mount a file as a file
- system. This is useful if you want to check an ISO9660 file system
- before burning the CD, or want to use floppy images without first
- writing them to floppy. This option also allows one to mount a
- filesystem with encryption. To use these features, you need a
- recent version of mount (available via ftp (user: anonymous) from
+ Saying Y here will allow you to mount a file as a file system. This
+ is useful if you want to check an ISO9660 file system before burning
+ the CD, or want to use floppy images without first writing them to
+ floppy. This option also allows one to mount a filesystem with
+ encryption. To use these features, you need a recent version of
+ mount (available via ftp (user: anonymous) from
ftp.win.tue.nl/pub/linux/util/). Note that this loop device has
nothing to do with the loopback device used for network connections
from the machine to itself. Most users will answer N here.
Old harddisk (MFM/RLL/IDE) driver
CONFIG_BLK_DEV_HD_ONLY
There are two drivers for MFM/RLL/IDE disks. Most people use the
- newer enhanced driver, but the old one is still around for two
+ newer enhanced driver, but this old one is still around for two
reasons. Some older systems have strange timing problems and seem
to work only with the old driver (which itself does not work with
some newer systems). The other reason is that the old driver is
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 installs the old
- harddisk driver to control the primary IDE/disk interface in the
+ the new enhanced driver by itself. This option however installs the
+ old harddisk driver to control the primary IDE/disk interface in the
system, leaving the new enhanced IDE driver 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
old harddisk driver instead, say Y. 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. If unsure, say Y.
+ Documentation/modules.txt. The module will be called ide-disk.o. If
+ unsure, say Y.
Include IDE/ATAPI CDROM support
CONFIG_BLK_DEV_IDECD
SCSI protocol. Most new CDROM drives use ATAPI, including the
NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
double(2X), quad(4X), and six(6X) speed drives. At boot time, the
- CDROM drive will be identified along with other IDE devices, as "hdb"
- or "hdc", or something similar.
- If this is your only CDROM drive, you can say N to all other CDROM
- options, but be sure to say Y to the ISO9660 filesystem. Read the
- CDROM-HOWTO, available via ftp (user: anonymous) in
+ CDROM drive will be identified along with other IDE devices, as
+ "hdb" or "hdc", or something similar. If this is your only CDROM
+ drive, you can say N to all other CDROM options, but be sure to say
+ Y to "ISO9660 cdrom filesystem support". Read the CDROM-HOWTO,
+ available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/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
- sunsite.unc.edu:/pub/Linux/system/Linux-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.
+ sunsite.unc.edu:/pub/Linux/system/Linux-boot/lilo. If you want to
+ compile the driver as a module ( = code which can be inserted in and
+ removed from the running kernel whenever you want), say M here and
+ read Documentation/modules.txt. The module will be called ide-cd.o.
Include IDE/ATAPI TAPE support
CONFIG_BLK_DEV_IDETAPE
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.
+ read Documentation/modules.txt. The module will be called ide-tape.o.
Include IDE/ATAPI FLOPPY support
CONFIG_BLK_DEV_IDEFLOPPY
something similar. If you want to compile the driver as a module ( =
code which can be inserted in and removed from the running kernel
whenever you want), say M here and read Documentation/modules.txt.
-
+ The module will be called ide-floppy.o.
+
SCSI emulation support
CONFIG_BLK_DEV_IDESCSI
This will provide SCSI host adapter emulation for IDE ATAPI devices,
Intel 82371 PIIX (Triton I/II) DMA support
CONFIG_BLK_DEV_TRITON
- This will improve performance if you have an Intel PCI Triton I/II
- IDE interface chipset (i82371FB or i82371SB). For details, read the
- comments at the beginning of drivers/block/triton.c and
- Documentation/ide.txt. If unsure, say N.
+ If your PCI system uses an IDE harddrive (as opposed to SCSI, say)
+ and includes the Intel Triton I/II IDE interface chipset (i82371FB
+ or i82371SB), you will want to enable this option to allow use of
+ bus-mastering DMA data transfers. Read the comments at the beginning
+ of drivers/block/triton.c. You can get the latest version of the
+ hdparm utility via ftp (user: anonymous) from
+ sunsite.unc.edu/pub/Linux/kernel/patches/diskdrives/; it is used to
+ tune your harddisk. It is safe to say Y to this question.
Other IDE chipset support
CONFIG_IDE_CHIPSETS
include a driver for these, say Y. 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. It's pretty unlikely that you have one of
- these: say N.
+ Documentation/modules.txt. The module will be called xd.o. It's
+ pretty unlikely that you have one of these: say N.
SyQuest EZ parallel port disk support
CONFIG_BLK_DEV_EZ
- If you have a parallel port version of SyQuest's EZ135 or EZ230 removable
- media devices you can use this driver. Answer Y to build the driver into
- the kernel, or M if you would like to build it as a loadable module.
- Read the file linux/Documentation/ez.txt. If you have several different
- devices that will share a common parallel port you should build them all
- as modules.
+ If you have a parallel port version of SyQuest's EZ135 or EZ230
+ removable media devices you can use this driver. Answer Y to build
+ the driver into the kernel, or M if you would like to build it as a
+ loadable module. The module will be called ez.o. Read the file
+ linux/Documentation/ez.txt. If you have several different devices
+ that will share a common parallel port you should build them all as
+ modules.
Multiple devices driver support
CONFIG_BLK_DEV_MD
Linear (append) mode
CONFIG_MD_LINEAR
- If you enable this, then your multiple devices driver will be able
- to use the so-called linear mode, i.e. it will combine the harddisk
+ 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 harddisk
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. If unsure, say Y.
+ read Documentation/modules.txt. The module will be called
+ linear.o. If unsure, say Y.
RAID-0 (striping) mode
CONFIG_MD_STRIPED
- If you enable this, then your multiple devices driver will be able
- to use the so-called raid0 mode, i.e. it will combine the harddisk
+ If you say Y here, then your multiple devices driver will be able to
+ use the so-called raid0 mode, i.e. it will combine the harddisk
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. 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. If unsure, say Y.
+ here and read Documentation/modules.txt. The module will be called
+ raid0.o. If unsure, say Y.
Support for Deskstation RPC44
CONFIG_DESKSTATION_RPC44
you want to configure your Linux box as a firewall for a local
network, say Y here. If your local network is TCP/IP based, you will
then also have to say Y to "IP: firewalling", below.
- You also need to say Y here and enable "IP firewalling" below in
+ You also need to say Y here and say Y to "IP firewalling" below in
order to be able to use IP masquerading (i.e. local computers can
chat with an outside host, but that outside host is made to think
that it is talking to the firewall box -- makes the local network
which is command line driven, and ARC, which uses menus and arrow
keys. The usual way to load Linux on an Alpha machine is to use MILO
(a bootloader that lets you pass command line parameters to the
- kernel just like LILO does) which can be loaded either from ARC or
- can be installed directly as a permanent firmware replacement from
- floppy (which requires changing a certain jumper on the
- motherboard). If you want to do either of these, say N here. If MILO
- doesn't work on your system (true for Jensen motherboards), you can
- bypass it altogether and boot Linux directly from an SRM console;
- say Y here in order to do that. Note that you won't be able to boot
- from an IDE disk using SRM. If unsure, say N. Details about the
- Linux/Alpha booting process are contained in the Linux/Alpha FAQ,
- accessible on the WWW from http://www.azstarnet.com/~axplinux/ (To
- browse the WWW, you need to have access to a machine on the Internet
- that has one of the programs lynx, netscape or Mosaic).
+ kernel just like lilo does for the 386 architecture) which can be
+ loaded either from ARC or can be installed directly as a permanent
+ firmware replacement from floppy (which requires changing a certain
+ jumper on the motherboard). If you want to do either of these, say N
+ here. If MILO doesn't work on your system (true for Jensen
+ motherboards), you can bypass it altogether and boot Linux directly
+ from an SRM console; say Y here in order to do that. Note that you
+ won't be able to boot from an IDE disk using SRM. If unsure, say
+ N. Details about the Linux/Alpha booting process are contained in
+ the Linux/Alpha FAQ, accessible on the WWW from
+ http://www.azstarnet.com/~axplinux/ (To browse the WWW, you need to
+ have access to a machine on the Internet that has one of the
+ programs lynx, netscape or Mosaic).
Echo console messages on /dev/ttyS1
CONFIG_SERIAL_ECHO
- If you enable this option, all kernel messages that would usually go
+ If you say Y here, all kernel messages that would usually go
to the console will also be sent to the device /dev/ttyS1 which
corresponds to a serial port; this could be useful if you attached
a terminal or printer to that port.
CONFIG_TGA_CONSOLE
Many Alpha systems (e.g the Multia) are shipped with a graphics card
that implements the TGA interface (much like the VGA standard, but
- older TGA adaptors are *not* VGA compatible). On such systems, this
- option needs to be enabled so that the TGA driver rather than the
- standard VGA driver is used. Note that, at this time, there is no X
- server for these systems. If unsure, try N.
+ older TGA adaptors are *not* VGA compatible). On such systems, you
+ should say Y here so that the TGA driver rather than the standard
+ VGA driver is used. Note that, at this time, there is no X server
+ for these systems. If unsure, try N.
PCI bios support
CONFIG_PCI
Documentation/mca.txt before attempting to build an MCA bus kernel.
Note that this is still experimental code.
-Intel 82371 PIIX (Triton I/II) DMA support
-CONFIG_BLK_DEV_TRITON
- If your PCI system uses an IDE harddrive (as opposed to SCSI, say)
- and includes the Intel 430FX PCI Triton chipset, you will want to
- enable this option to allow use of bus-mastering DMA data transfers.
- Read the comments at the beginning of drivers/block/triton.c. You
- can get the latest version of the hdparm utility via ftp (user:
- anonymous) from
- sunsite.unc.edu/pub/Linux/kernel/patches/diskdrives/; it is used to
- tune your harddisk. It is safe to say Y to this question.
-
System V IPC
CONFIG_SYSVIPC
Inter Process Communication is a suite of library functions and system
calls which let processes (= running programs) synchronize and
exchange information. It is generally considered to be a good thing,
- and some programs won't run unless you enable this. In particular,
+ 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 via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/HOWTO), you'll need to say Y here. You
sunsite.unc.edu:/pub/Linux/docs/man/info.tar.gz (extract with "tar
xzvf filename"). These docs are in the info format which is used to
document GNU software and can be read from within emacs ("Ctrl-h i")
- or with the program info ("man info"). Enabling this option enlarges
+ or with the program info ("man info"). Saying Y here enlarges
your kernel by about 7kB. Just say Y.
Kernel support for ELF binaries
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. Saying M or N here is dangerous
- because some crucial programs on your system might be in ELF format.
+ and read Documentation/modules.txt. The module will be called
+ binfmt_elf.o. Saying M or N here is dangerous because some crucial
+ programs on your system might be in ELF format.
Kernel support for A.OUT binaries
CONFIG_BINFMT_AOUT
wish to ensure that absolutely none of your programs will use this
older executable format. If you don't know what to answer at this
point then answer Y. If someone told you "You need a kernel with
- QMAGIC support" then you'll have to say Y here. You may answer M
- to compile a.out support as a module and later load the module when
- you want to use a program or library in a.out format. Saying M or N
- here is dangerous though, because some crucial programs on your
- system might still be in A.OUT format.
+ QMAGIC support" then you'll have to say Y here. You may answer M to
+ compile a.out support as a module and later load the module when you
+ want to use a program or library in a.out format. The module will be
+ called binfmt_aout.o. Saying M or N here is dangerous though,
+ because some crucial programs on your system might still be in A.OUT
+ format.
Kernel support for JAVA binaries
CONFIG_BINFMT_JAVA
- JAVA is an object oriented programming language developed by SUN;
- JAVA programs are compiled into "JAVA bytecode" binaries which can
- then be interpreted by run time systems on many different operating
- systems. These JAVA binaries are becoming a universal executable
- format. Saying Y here allows you to execute a JAVA bytecode binary
- just like any other Linux program: by typing in its name. As more
- and more Java programs become available, the use for this will
- gradually increase. You can even execute HTML files containing JAVA
- applets (= JAVA binaries) if those files start with the string
- "<!--applet-->". If you want to use this, read
- Documentation/java.txt and the Java on Linux HOWTO, available via
- ftp (user: anonymous) at sunsite.unc.edu:/pub/Linux/docs/HOWTO. You
- will then need to install the run time system contained in the Java
- Developers Kit (JDK) as described in the HOWTO. If you disable this
- option it will reduce your kernel by about 4kB. This is not much and
- by itself does not warrant removing support. However its removal is
- a good idea if you do not have the JDK installed. If you don't know
- what to answer at this point then answer Y. You may answer M for
- module support and later load the module when you install the JDK or
- find an interesting Java program that you can't live without.
+ JAVA(tm) is an object oriented programming language developed by
+ SUN; JAVA programs are compiled into "JAVA bytecode" binaries which
+ can then be interpreted by run time systems on many different
+ operating systems. These JAVA binaries are becoming a universal
+ executable format. If you want to execute JAVA binaries, read the
+ Java on Linux HOWTO, available via ftp (user: anonymous) at
+ sunsite.unc.edu:/pub/Linux/docs/HOWTO. You will then need to install
+ the run time system contained in the Java Developers Kit (JDK) as
+ described in the HOWTO. This is completely independent of the Linux
+ kernel and you do NOT need to say Y here for this to work.
+ Saying Y here allows you to execute a JAVA bytecode binary just like
+ any other Linux program: by simply typing in its name. (You also
+ need to have the JDK installed for this to work). As more and more
+ Java programs become available, the use for this will gradually
+ increase. You can even execute HTML files containing JAVA applets (=
+ JAVA binaries) if those files start with the string
+ "<!--applet-->". If you want to use this, say Y here and read
+ Documentation/java.txt. If you disable this option it will reduce
+ your kernel by about 4kB. This is not much and by itself does not
+ warrant removing support. However its removal is a good idea if you
+ do not have the JDK installed. You may answer M for module support
+ and later load the module when you install the JDK or find an
+ interesting Java program that you can't live without. The module
+ will be called binfmt_java.o. If you don't know what to answer at
+ this point then answer Y.
Processor type
CONFIG_M386
- This is the processor type of your CPU. It is used for optimizing
- purposes. In order to compile a kernel that can run on all CPU types
- (albeit not optimally fast), you can specify "386" here. If you
- specify "486" or "Pentium" or "PPro", then the kernel will run on
- 486 and Pentium (=586) and Pentium Pro (=686) CPUs. In rare cases,
- it can make sense to specify "Pentium" even if running a 486: the
- kernel will be smaller but slower. On the other hand, if you use a
- compiler before gcc 2.7 (say "gcc -v" to find out), then you have to
- say "386" or "486" here even if running on a Pentium or PPro
- machine. If you don't know what to do, say "386".
+ This is the processor type of your CPU. This information is used for
+ optimizing purposes. In order to compile a kernel that can run on
+ all Intel CPU types (albeit not optimally fast), you can specify
+ "386" here. If you specify one of "486" or "Pentium" or "PPro",
+ then the kernel will run on all of these CPUs: 486 and Pentium
+ (=586) and Pentium Pro (=686). In rare cases, it can make sense to
+ specify "Pentium" even if running on a 486: the kernel will be
+ smaller but slower. If you don't know what to do, say "386".
Video mode selection support
CONFIG_VIDEO_SELECT
- This enables support for text mode selection on kernel startup. If you
- want to take advantage of some high-resolution text mode your card's
- BIOS offers, but the traditional Linux utilities like SVGATextMode
- don't, you can enable this and set the mode using the "vga=" option
- from your boot loader (LILO or LOADLIN) or set "vga=ask" which brings
- up a video mode menu on kernel startup. Read Documentation/svga.txt
- for more information. If unsure, say N.
+ This enables support for text mode selection on kernel startup. If
+ you want to take advantage of some high-resolution text mode your
+ card's BIOS offers, but the traditional Linux utilities like
+ SVGATextMode don't, you can say Y here and set the mode using the
+ "vga=" option from your boot loader (lilo or loadlin) or set
+ "vga=ask" which brings up a video mode menu on kernel startup. Try
+ "man bootparam" or see the documentation of your boot loader about
+ how to pass options to the kernel. The lilo procedure is also
+ explained in the SCSI-HOWTO, available via ftp (user: anonymous) in
+ sunsite.unc.edu:/pub/Linux/docs/HOWTO. Read Documentation/svga.txt
+ for more information about the Video mode selection support. If
+ unsure, say N.
Compile the kernel into the ELF object format
CONFIG_ELF_KERNEL
Set version information on all symbols for modules
CONFIG_MODVERSIONS
Usually, modules have to be recompiled whenever you switch to a new
- kernel. Enabling this option 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 modules package (check the file Documentation/Changes for
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. By enabling
- this option, the kernel's internal ARP cache will never grow to more
- than 256 entries (the oldest entries are expired in a LIFO manner)
- and communication will be attempted with an external ARP daemon,
- arpd. This code is still experimental. If you do enable arpd
- support, you should obtain a copy of arpd from
+ connections are made to many machines on the network. By saying Y
+ here, the kernel's internal ARP cache will never grow to more than
+ 256 entries (the oldest entries are expired in a LIFO manner) and
+ communication will be attempted with an external ARP daemon, arpd.
+ This code is still experimental. If you do say Y here, you
+ should obtain a copy of arpd from
http://www.loran.com/~layes/arpd/index.html. If unsure, say N.
TCP/IP networking
local network from the internet. The Firewall-HOWTO tells you how to
do this. If your setup is more complex, say you are connected to
three networks and you want to act as a firewall between two of them
- and route traffic for the others, you need to say Y here and enable
- IP firewalling below. If you intend to use IP masquerading (i.e. IP
+ and route traffic for the others, you need to say Y here and Y to
+ "IP firewalling" below. If you intend to use IP masquerading (i.e. IP
traffic from one of the local computers and destined for an outside
host is changed by your box so that it appears to come from you),
you'll have to say Y here and also to IP firewalling and IP
ipfwadm tool (available via ftp (user: anonymous) from
ftp.xos.nl/pub/linux/ipfwadm/) to allow selective blocking of
internet traffic based on type, origin and destination. You need to
- enable IP firewalling in order to be able to use IP masquerading
+ say Y to "IP firewalling" in order to be able to use IP masquerading
(i.e. local computers can chat with an outside host, but that
outside host is made to think that it is talking to the firewall box
-- makes the local network completely invisible and avoids the need
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). Enabling
- this option will produce two modules ( = code which can be inserted
- in and removed from the running kernel whenever you want), one
- encapsulator and one decapsulator. You can read details in
- drivers/net/README.tunnel. Most people can say N.
+ 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),
+ one encapsulator and one decapsulator. The module will be called
+ ipip.o. You can read details in drivers/net/README.tunnel. Most
+ people can say N.
IP: firewall packet logging
CONFIG_IP_FIREWALL_VERBOSE
that the IP packets were too large and cut them in pieces) will be
reassembled (defragmented) before being processed, even if they are
about to be forwarded. This option is highly recommended if you
- have enabled the masquerading support (CONFIG_IP_MASQUERADE),
- because that facility requires that second and further fragments can
- be related to TCP or UDP port numbers, which are only stored in the
- first fragment. When using IP firewall support
- (CONFIG_IP_FIREWALL), you might also want to enable this option, to
+ have said Y to "IP: masquerading" because that facility requires
+ that second and further fragments can be related to TCP or UDP port
+ numbers, which are only stored in the first fragment. When using
+ "IP: firewalling" support , you might also want to say Y here, to
have a more reliable firewall (otherwise second and further
- fragments will always be accepted by the firewall). When using
- transparent proxying (CONFIG_IP_TRANSPARENT_PROXY), this option is
- implicit, although it is safe to say Y here. Do not say Y to this
- option except when running either a firewall that is the sole link
- to your network or a transparent proxy. Never ever say Y to this for
- a normal router or host.
+ fragments will always be accepted by the firewall). When using "IP:
+ transparent proxying", this option is implicit, although it is safe
+ to say Y here. Do not say Y to this option except when running
+ either a firewall that is the sole link to your network or a
+ transparent proxy. Never ever say Y to this for a normal router or
+ host.
IP: aliasing support
CONFIG_IP_ALIAS
CONFIG_INET_PCTCP
If you have been having difficulties telneting 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 enabling this
- option. Everyone else says N. People having problems with NCSA telnet
+ 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 linux/Documentation/networking/ncsa-telnet.
Reverse ARP
http://web.syr.edu/~jmwobus/comfaqs/dhcp.faq.html for details. If
you want to compile RARP 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. If you don't
- understand a word of the above, say N and rest in peace.
+ say M here and read Documentation/modules.txt. The module will be
+ called rarp.o. If you don't understand a word of the above, say N
+ and rest in peace.
Assume subnets are local
CONFIG_INET_SNARL
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. For details, see
- http://playground.sun.com/pub/ipng/html/ipng-main.html and the file
- net/ipv6/README in the kernel source. The IPv6 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. It's
- safe to say N for now.
+ interoperability with the current version of IP. For general
+ information about IPv6, see
+ http://playground.sun.com/pub/ipng/html/ipng-main.html; for specific
+ information about IPv6 under Linux read the HOWTO at
+ http://www.terra.net/ipv6/ and the file net/ipv6/README in the
+ kernel source. The IPv6 support is also available as a module ( =
+ code which can be inserted in and removed from the running kernel
+ whenever you want). The module will be called ipv6.o. If you want to
+ compile it as a module, say M here and read
+ Documentation/modules.txt. It's safe to say N for now.
The IPX protocol
CONFIG_IPX
IPX-HOWTO in sunsite.unc.edu:/pub/Linux/docs/howto. The IPX driver
would enlarge your kernel by about 5 kB. 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.
- Unless you want to integrate your Linux box with a local Novell
- network, say N.
+ 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.
Full internal IPX network
CONFIG_IPX_INTERN
+ Every IPX network has an address that identifies it. Sometimes it is
+ useful to give an IPX "network" address to your Linux box as well
+ (for example if your box is acting as a fileserver for different IPX
+ networks: it will then be accessible form everywhere using the same
+ address). The way this is done is to create a virtual internal
+ "network" inside your box and to assign an IPX address to this
+ network. Say Y here if you want to do this; read the IPX-HOWTO at
+ sunsite.unc.edu:/pub/Linux/docs/howto for details.
The full internal IPX network enables you to allocate sockets on
different virtual nodes of the internal network. This is done by
- evaluating the field sipx_node of the socket address given to the bind
- call. So applications should always initialize the node field to 0
- when binding a socket on the primary network. In this case the socket
- is assigned the default node that has been given to the kernel when
- the internal network was created.
- By enabling the full internal IPX network the cross-forwarding of
- packets targeted at 'special' sockets to sockets listening on the
- primary network is disabled. This might break existing applications,
- especially RIP/SAP daemons. A RIP/SAP daemon that works well with the
- full internal net can be found on ftp.gwdg.de:/pub/linux/misc/ncpfs.
- If you don't know what you are doing, say N.
+ evaluating the field sipx_node of the socket address given to the
+ bind call. So applications should always initialize the node field
+ to 0 when binding a socket on the primary network. In this case the
+ socket is assigned the default node that has been given to the
+ kernel when the internal network was created. By enabling the full
+ internal IPX network the cross-forwarding of packets targeted at
+ 'special' sockets to sockets listening on the primary network is
+ disabled. This might break existing applications, especially RIP/SAP
+ daemons. A RIP/SAP daemon that works well with the full internal net
+ can be found on ftp.gwdg.de:/pub/linux/misc/ncpfs. If you don't
+ know what you are doing, say N.
IPX Type 20 Routing
CONFIG_IPX_PPROP_ROUTING
CONFIG_ATALK
Appletalk is the way Apple computers speak to each other on a
network. EtherTalk is the name used for appletalk over ethernet and
- Localtalk is appletalk over the apple serial links. 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
+ Localtalk is appletalk over the apple serial links. 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://artoo.hitchcock.org/~flowerpt/projects/linux-netatalk/ on the
WWW for details (to browse the WWW, you need to have access to a
machine on the Internet that has one of the programs lynx, netscape
sunsite.unc.edu:/pub/Linux/docs/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). If you want to compile it as a module, say M here and read
- Documentation/modules.txt. I hear that the GNU boycott of Apple is
- over, so even politically correct people are allowed to say Y here.
- At the time the kernel is released the localtalk drivers are not
- yet ready to ship. The kernel however supports localtalk and when
- such drivers become available all you will need to do is download
- and install the localtalk driver.
+ want). The module will be called appletalk.o. If you want to compile
+ it as a module, say M here and read Documentation/modules.txt. I
+ hear that the GNU boycott of Apple is over, so even politically
+ correct people are allowed to say Y here. At the time the kernel is
+ released the localtalk drivers are not yet ready to ship. The kernel
+ however supports localtalk and when such drivers become available
+ all you will need to do is download and install the localtalk
+ driver.
Amateur Radio AX.25 Level 2
CONFIG_AX25
have to say Y to one of those drivers. Information about where to
get supporting software for Linux amateur radio as well as
information about how to configure an AX.25 port is contained in the
- HAM-HOWTO, available via ftp (user: anonymous) in
+ AX25-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/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
browse the WWW, you need to have access to a machine on the Internet
that has one of the programs lynx, netscape or Mosaic). 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.
+ 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.
Amateur Radio NET/ROM
CONFIG_NETROM
NET/ROM is a network layer protocol on top of AX.25 useful for
routing. A comprehensive listing of all the software for Linux
amateur radio users as well as information about how to configure an
- AX.25 port is contained in the HAM-HOWTO, available via ftp (user:
+ AX.25 port is contained in the AX25-HOWTO, available via ftp (user:
anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO. You also might
want to check out the file Documentation/networking/ax25.txt. More
information about digital amateur radio in general is on the WWW at
http://www.tapr.org/tapr/html/pkthome.html (To browse the WWW, you
need to have access to a machine on the Internet that has one of the
- programs lynx, netscape or Mosaic).
- 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
+ programs lynx, netscape or Mosaic). 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.
AX.25 over Ethernet
particular, essentially an alternative to NET/ROM. A comprehensive
listing of all the software for Linux amateur radio users as well as
information about how to configure an AX.25 port is contained in the
- HAM-HOWTO, available via ftp (user: anonymous) in
+ AX25-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/HOWTO. You also might want to check
out the file Documentation/networking/ax25.txt. More information
about digital amateur radio in general is on the WWW at
need to have access to a machine on the Internet that has one of the
programs lynx, netscape or Mosaic). 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.
+ 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.
+
+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 entry point
+ to the X.25 network can carry several logical point-to-point
+ connections (called "virtual circuits") to other computers connected
+ to the X.25 network. Governments, banks, and other organizations
+ tend to use it to connect to each other or to form Wide Area
+ Networks. Many 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). You can read more about X.25 at
+ http://www.sangoma.com/x25.html 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. 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 X.25 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). 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 x25.o. If unsure, say N.
+
+LAPB Data Link Driver (EXPERIMENTAL)
+CONFIG_LAPB
+ Link Access Procedure, Balanced (LAPB) is the data link layer part
+ of the X.25 protocol. It offers a reliable connection service to
+ exchange data frames with one other host, and it is used to
+ transport higher level protocols (mostly X.25 Packet Layer, but
+ others are possible as well). 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.
+ 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.
+802.2 LLC (VERY EXPERIMENTAL)
+CONFIG_LLC
+ This is a Logical Link Layer protocol used for X.25 connections over
+ ethernet, using ordinary ethernet cards.
+
Bridging (EXPERIMENTAL)
CONFIG_BRIDGE
If you say Y here, then your Linux box will be able to act as an
of the kernel or modules and user processes; the user processes are
able to read from and write to character special files in the /dev
directory having major mode 36. So far, the kernel uses it to
- publish some network related information if you enable "Routing
+ publish some network related information if you say Y to "Routing
messages", below. It is also used by the firewall code if you say Y
to "Kernel/User network link driver" further down. You also need to
say Y here if you want to use arpd, a daemon that helps keep the
Routing messages
CONFIG_RTNETLINK
- If you enable this and create a character special file /dev/route
+ If you say Y here and create a character special file /dev/route
with major number 36 and minor number 0 using mknod ("man mknod"),
you can read some network related routing information from that
file. Everything you write to that file will be discarded.
SCSI-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/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 and
- Documentation/scsi.txt.
+ 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.
SCSI disk support
CONFIG_BLK_DEV_SD
sunsite.unc.edu:/pub/Linux/docs/HOWTO. This is NOT for SCSI
CDROMs. 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 and Documentation/scsi.txt.
+ 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.
SCSI tape support
CONFIG_CHR_DEV_ST
sunsite.unc.edu:/pub/Linux/docs/HOWTO and drivers/scsi/README.st in
the kernel source. This is NOT for SCSI CDROMs. 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 and
- Documentation/scsi.txt .
+ 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 .
SCSI CDROM 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 from
- sunsite.unc.edu:/pub/Linux/docs/HOWTO. Also make sure to enable the
- ISO9660 filesystem later. 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 and
- Documentation/scsi.txt .
+ sunsite.unc.edu:/pub/Linux/docs/HOWTO. Also make sure to say Y to
+ "ISO9660 cdrom filesystem 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 .
Enable vendor-specific extensions (for SCSI CDROM)
CONFIG_BLK_DEV_SR_VENDOR
sunsite.unc.edu:/pub/Linux/docs/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 and Documentation/scsi.txt.
+ Documentation/modules.txt and Documentation/scsi.txt. The module
+ will be called sg.o. If unsure, say N.
Probe all LUNs on each SCSI device
CONFIG_SCSI_MULTI_LUN
Verbose SCSI error reporting (kernel size +=12K)
CONFIG_SCSI_CONSTANTS
The error messages regarding your SCSI hardware will be easier to
- understand if you enable this; it will enlarge your kernel by about
+ understand if you say Y here; it will enlarge your kernel by about
12KB. If in doubt, say Y.
AdvanSys SCSI support
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.
+ here and read Documentation/modules.txt. The module will be called
+ advansys.o.
Adaptec AHA152X/2825 support
CONFIG_SCSI_AHA152X
sunsite.unc.edu:/pub/Linux/docs/HOWTO. You might also want to read
the comments at the top of drivers/scsi/aha152x.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.
+ 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.
Adaptec AHA1542 support
CONFIG_SCSI_AHA1542
3.4 of the SCSI-HOWTO, available via ftp (user: anonymous) at
sunsite.unc.edu:/pub/Linux/docs/HOWTO. Note that Trantor was
recently 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. 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.
+ 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.
+ 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.
Adaptec AHA1740 support
CONFIG_SCSI_AHA1740
the box, you may have to change some settings in
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). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ whenever you want). The module will be called aha17400.o. If you
+ want to compile it as a module, say M here and read
+ Documentation/modules.txt.
Adaptec AHA274X/284X/294X support
CONFIG_SCSI_AIC7XXX
doesn't work out of the box, you may have to change some settings in
drivers/scsi/aic7xxx.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.
+ whenever you want), say M here and read
+ Documentation/modules.txt. The module will be called aic7xxx.o.
BusLogic SCSI support
CONFIG_SCSI_BUSLOGIC
correctly without modification, please contact the author. You can
build this driver also 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.
+ single instance may be loaded. The module will be called
+ BusLogic.o. If you want to compile it as a module, say M here and
+ read Documentation/modules.txt.
DTC3180/3280 SCSI support
CONFIG_SCSI_DTC3280
sunsite.unc.edu:/pub/Linux/docs/HOWTO and the 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). If you want to compile it as a module,
- say M here and read Documentation/modules.txt.
+ 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.
EATA-DMA (DPT, NEC, AT&T, SNI, AST, Olivetti, Alphatronix) support
CONFIG_SCSI_EATA_DMA
Adaptors like the SmartCache III/IV, SmartRAID controller families
and the DPT PM2011B and PM2012B controllers. Note that there is
also another driver for the same hardware: "EATA ISA/EISA/PCI
- support". You should enable only one of them. Please read the
+ support". You should only say Y to one of them. Please read the
SCSI-HOWTO, available via ftp (user: anonymous) at
sunsite.unc.edu:/pub/Linux/docs/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.
+ 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.
EATA-PIO (old DPT PM2001, PM2012A) support
CONFIG_SCSI_EATA_PIO
sunsite.unc.edu:/pub/Linux/docs/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.
+ 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 via ftp (user: anonymous) at
- sunsite.unc.edu:/pub/Linux/docs/HOWTO. Note that there is also another
- driver for the same hardware: "UltraStor SCSI support", below.
- You should enable 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). If you
- want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ 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 via ftp (user: anonymous) at
+ sunsite.unc.edu:/pub/Linux/docs/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
+ 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.
+
+enable linked commands
+CONFIG_SCSI_U14_34F_LINKED_COMMANDS
+ This is a feature of SCSI-2 which improves performance: the host
+ adaptor can send a whole list of commands to a device in one
+ batch. Some SCSI devices might not implement this properly, so the
+ save answer is N.
+
+maximum number of queued commands
+CONFIG_SCSI_U14_34F_MAX_TAGS
+ This specifies how many SCSI commands can be maximally queued for a
+ given SCSI device. Go with the default unless you know what you're
+ doing. Minimum is 2 and maximum is 8.
Future Domain 16xx SCSI support
CONFIG_SCSI_FUTURE_DOMAIN
This is support for Future Domain's 16-bit SCSI host adaptors
- (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and other
- adaptors based on the Future Domain chipsets (Quantum ISA-200S,
- ISA-250MG; Adaptec AHA-2920; and at least one IBM board). It is
- explained in section 3.7 of the SCSI-HOWTO, available via ftp (user:
- anonymous) at sunsite.unc.edu:/pub/Linux/docs/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.
+ (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
+ other adaptors based on the Future Domain chipsets (Quantum
+ ISA-200S, ISA-250MG; Adaptec AHA-2920; and at least one IBM board).
+ It is explained in section 3.7 of the SCSI-HOWTO, available via ftp
+ (user: anonymous) at sunsite.unc.edu:/pub/Linux/docs/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 fdomain.o. If you want to compile it as a
+ module, say M here and read Documentation/modules.txt.
Generic NCR5380/53c400 SCSI support
CONFIG_SCSI_GENERIC_NCR5380
the box, you may have to change some settings in
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). If you want to compile it as a module,
- say M here and read Documentation/modules.txt.
+ 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.
Enable NCR53c400 extensions
CONFIG_SCSI_GENERIC_NCR53C400
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. If you want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ details.
NCR5380/53c400 mapping method (use Port for T130B)
CONFIG_SCSI_G_NCR5380_PORT
box, you may have to change some settings in
drivers/scsi/53c7,8xx.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.
+ 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.
always negotiate synchronous transfers
CONFIG_SCSI_NCR53C7xx_sync
allow DISCONNECT
CONFIG_SCSI_NCR53C7xx_DISCONNECT
This enables the disconnect/reconnect feature of the NCR SCSI
- controller. When this is enabled, a slow SCSI device will not lock
+ controller. When you say Y here, a slow SCSI device will not lock
the SCSI bus while processing a request, allowing simultaneous use
of e.g. a SCSI hard disk and SCSI tape or CD-ROM drive, and
providing much better performance when using slow and fast SCSI
IBMMCA SCSI support
CONFIG_SCSI_IBMMCA
If your computer sports an MCA bus system architecture (IBM PS/2)
- with an SCSI harddrive, say Y here.
+ with an SCSI harddrive, say Y here. 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
+ ibmmca.o. If you want to compile it as a module, say M here and read
+ Documentation/modules.txt.
Always IN2000 SCSI support
CONFIG_SCSI_IN2000
- This is support for an ISA bus SCSI host adaptor. 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. 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.
+ This is support for an ISA bus SCSI host adaptor. 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. 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.
PAS16 SCSI support
CONFIG_SCSI_PAS16
3.10 of the SCSI-HOWTO, available via ftp (user: anonymous) at
sunsite.unc.edu:/pub/Linux/docs/HOWTO. If it doesn't work out of the
box, you may have to change some settings in 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.
+
Qlogic FAS SCSI support
CONFIG_SCSI_QLOGIC_FAS
This driver works only with the ISA, VLB, and PCMCIA versions of the
the SCSI-HOWTO, available via ftp (user: anonymous) at
sunsite.unc.edu:/pub/Linux/docs/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.
+ 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.
Qlogic ISP SCSI support (EXPERIMENTAL)
CONFIG_SCSI_QLOGIC_ISP
available via ftp (user: anonymous) at
sunsite.unc.edu:/pub/Linux/docs/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.
+ 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.
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
- via ftp (user: anonymous) at
+ 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 via ftp (user: anonymous) at
sunsite.unc.edu:/pub/Linux/docs/HOWTO. If it doesn't work out of the
box, you may have to change some settings in 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). If you want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ 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.
Trantor T128/T128F/T228 SCSI support
CONFIG_SCSI_T128
3.11 of the SCSI-HOWTO, available via ftp (user: anonymous) at
sunsite.unc.edu:/pub/Linux/docs/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 recently purchased by
- Adaptec, and some former Trantor products are being sold under the
- Adaptec name.
+ 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.
UltraStor SCSI support
CONFIG_SCSI_ULTRASTOR
box, you may have to change some settings in
drivers/scsi/ultrastor.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.
+ whenever you want), say M here and read
+ Documentation/modules.txt. The module will be called ultrastor.o.
Note that there is also another driver for the same hardware:
"UltraStor 14F/34F support", above.
This driver supports the Western Digital 7000 SCSI host adaptor.
Some information is in the source: 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). If you
- want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ 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.
EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support
CONFIG_SCSI_EATA
This driver supports all the EATA/DMA-compliant SCSI host adapters
- and does not need any BIOS32 service.
- DPT ISA and all EISA i/o addresses are probed looking for the "EATA"
- signature. If "PCI bios support" is enabled, the addresses of all
- the PCI SCSI controllers reported by BIOS32 are probed as well.
- Note that there is also another driver for the same hardware:
- "EATA-DMA support". You should enable only one of them.
- You want to read the start of drivers/scsi/eata.c and the
- SCSI-HOWTO, available via ftp (user: anonymous) at
- sunsite.unc.edu:/pub/Linux/docs/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.
+ and does not need any BIOS32 service. DPT ISA and all EISA i/o
+ addresses are probed looking for the "EATA" signature. If you said Y
+ to "PCI bios support", the addresses of all the PCI SCSI controllers
+ reported by BIOS32 are probed as well. Note that there is also
+ another driver for the same hardware available: "EATA-DMA
+ support". You should say Y to only one of them. You want to read
+ the start of drivers/scsi/eata.c and the SCSI-HOWTO, available via
+ ftp (user: anonymous) at sunsite.unc.edu:/pub/Linux/docs/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.o.
+
+enable tagged command queuing
+CONFIG_SCSI_EATA_TAGGED_QUEUE
+ This is a feature of SCSI-2 which improves performance: the host
+ adaptor can send several SCSI commands to a device's queue even if
+ previous commands haven't finished yet. Some SCSI devices don't
+ implement this properly, so the save answer is N.
+
+enable linked commands
+CONFIG_SCSI_EATA_LINKED_COMMANDS
+ This is a feature of SCSI-2 which improves performance: the host
+ adaptor can send a whole list of commands to a device in one
+ batch. Some SCSI devices might not implement this properly, so the
+ save answer is N.
+
+maximum number of queued commands
+CONFIG_SCSI_EATA_MAX_TAGS
+ This specifies how many SCSI commands can be maximally queued for a
+ given SCSI device. Go with the default unless you know what you're
+ doing. Minimum is 2 and maximum is 16. This number will only have an
+ effect if you said Y to "enable tagged command queuing", above.
NCR53c406a SCSI support
CONFIG_SCSI_NCR53C406A
anonymous) at sunsite.unc.edu:/pub/Linux/docs/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.
+ and read Documentation/modules.txt. The module will be called
+ NCR53c406.o.
AM53/79C974 PCI SCSI support
CONFIG_SCSI_AM53C974
sunsite.unc.edu:/pub/Linux/docs/HOWTO, is for you. 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 read Documentation/modules.txt. The module will be called
+ AM53C974.o.
IOMEGA Parallel Port ZIP drive SCSI support
CONFIG_SCSI_PPA
drive, a parallel printer or PLIP on the same parallel port, you
should compile the drivers as modules and only insert them as
needed. To compile this driver as a module, say M here and read
- Documentation/modules.txt. Note that you can say N here if you have
- the SCSI version of the ZIP drive: it will be supported
- automatically if you enabled the generic "SCSI disk support", above.
+ Documentation/modules.txt. The module will be called ppa.o. Note
+ that you can say N here if you have the SCSI version of the ZIP
+ drive: it will be supported automatically if you said Y to the
+ generic "SCSI disk support", above.
Network device support?
CONFIG_NETDEVICES
this device is consigned into oblivion) with a configurable IP
address. It is most commonly used in order to make your currently
inactive SLIP address seem like a real address for local
- programs. If you use SLIP or PPP, you might want to enable it. Read
+ programs. If you use SLIP or PPP, you might want to say Y here. Read
about it in the Network Administrator's Guide, available via ftp
(user: anonymous) from sunsite.unc.edu:/pub/Linux/docs/LDP. Since
this thing comes often handy, the default is Y. It won't enlarge
your kernel either. What a deal. 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. If you want to use more than one dummy
- device at a time, you need to compile it as a module. Instead of
- 'dummy', it will they will then be called 'dummy0', 'dummy1' etc.
+ 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 it as a module. Instead of 'dummy', it will they will then
+ be called 'dummy0', 'dummy1' etc.
SLIP (serial line) support
CONFIG_SLIP
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.
+ Documentation/networking/net-modules.txt. The module will be called
+ slip.o.
CSLIP compressed headers
CONFIG_SLIP_COMPRESSED
CONFIG_NET_RADIO
Radio based interfaces for Linux. This includes amateur radio
(AX.25), support for wireless ethernet and other systems. 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 radio interfaces. Some user-level drivers for scarab
- devices which don't require special kernel support are available via
- ftp (user: anonymous) from shadow.cabi.net. If unsure, say N.
+ 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 radio interfaces. Some user-level drivers for scarab devices
+ which don't require special kernel support are available via ftp
+ (user: anonymous) from shadow.cabi.net.
+ If unsure, say N.
+
+AX.25 network interfaces
+CONFIG_NET_HAM
+ Say Y here if you want support for a device that connects your Linux
+ box to your amateur radio (HAM). AX.25 is the protocol used for
+ digital traffic over amateur radio connections. You might want to
+ read the HAM-HOWTO and the AX25-HOWTO, both available via ftp (user:
+ anonymous) from sunsite.unc.edu:/pub/Linux/docs/HOWTO. Note that the
+ answer to this question won't directly affect the kernel: saying N
+ will just cause this configure script to skip all the questions
+ about amateur radio interfaces.
PPP (point-to-point) support
CONFIG_PPP
anonymous) from sunsite.unc.edu:/pub/Linux/system/Network/serial/).
To use PPP, you need an additional program called pppd as described
in Documentation/networking/ppp.txt and in the PPP-HOWTO, available
- from sunsite.unc.edu:/pub/Linux/docs/HOWTO. 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
- the Term-HOWTO). The PPP option enlarges your kernel by about
- 16kB. 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 said Y to "Version information on all symbols" above,
- then you cannot compile the PPP driver into the kernel; you can only
- compile it as a module. If you want to compile it as a module, say M
- here and read Documentation/modules.txt as well as
+ from sunsite.unc.edu:/pub/Linux/docs/HOWTO. If you upgrade from an
+ older kernel, you might need to upgrade pppd as well. Note that you
+ don't need "PPP support" 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 the Term-HOWTO). The PPP option enlarges your kernel
+ by about 16kB. 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 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.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. Note that, no matter what
you do, the BSD compression code (used to compress the IP packets
sent over the serial line; has to be supported at the other end as
except that it makes the kernel a bit 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.
+ Documentation/modules.txt. The module will be called strip.o.
WIC (Radio IP bridge)
CONFIG_WIC
to say N. 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 wic.o.
+
+CONFIG_LAPBETHER
+LAPB over Ethernet driver
+ This is a driver for a pseudo device (usually 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
+ need to say Y or M to the driver for your ethernet card as well as
+ 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.
Z8530 SCC driver for AX.25
CONFIG_SCC
These cards are used to connect your Linux box to an amateur radio
in order to communicate with other computers. If you want to use
- this, read Documentation/networking/z8530drv.txt and the AX.25-HOWTO,
- available via ftp (user: anonymous) at
+ this, read Documentation/networking/z8530drv.txt and the
+ AX.25-HOWTO, available via ftp (user: anonymous) at
sunsite.unc.edu:/pub/Linux/docs/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.
+ Documentation/modules.txt. The module will be called scc.o.
BAYCOM ser12 and par96 driver for AX.25
CONFIG_BAYCOM
This is an experimental driver for Baycom style simple amateur radio
modems that connect to either a serial interface or a parallel
interface. The driver supports the ser12 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 drivers/net/README.baycom.
- 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. This is recommended.
+ 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 drivers/net/README.baycom. 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.o.
Soundcard modem driver for AX.25
CONFIG_SOUNDMODEM
- This experimental driver allows a standard SoundBlaster or
+ This experimental driver allows a standard SoundBlaster or
WindowsSoundSystem compatible soundcard to be used as a packet radio
- modem. To configure the driver, use the sethdlc, smdiag and smmixer
- utilities available in the standard ax25 utilities package. For
- informations on how to key the transmitter, see
+ modem, to send digital traffic over amateur radio. 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
- drivers/net/README.soundmodem. If you want to compile this as a
- module ( = code which can be inserted in and removed from the
+ drivers/net/README.soundmodem. 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.
+ Documentation/modules.txt. This is recommended. The module will be
+ called soundmodem.o.
Soundcard modem support for SoundBlaster and compatible cards
CONFIG_SOUNDMODEM_SBC
- This option enables the soundmodem driver to use SoundBlaster
- and compatible cards. Dual mode cards (i.e. WSS cards with a
- SoundBlaster emulation) should be used in WSS mode because
- this results in usually better performance.
+ This option enables the soundmodem driver to use SoundBlaster and
+ compatible cards. If you have a dual mode card (i.e. a WSS cards
+ with a SoundBlaster emulation) you should say N here and Y to
+ "Soundcard modem support for WSS and Crystal cards", below, because
+ this usually results in better performance.
Soundcard modem support for WSS and Crystal cards
CONFIG_SOUNDMODEM_WSS
This option enables the soundmodem driver to use WindowsSoundSystem
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 it to save performance.
+ 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
+ it to save performance.
Soundcard modem support for 1200 baud AFSK modulation
CONFIG_SOUNDMODEM_AFSK1200
compatible to popular modems using TCM3105 or AM7911. The demodulator
requires about 12% of the CPU power of a Pentium 75 CPU per channel.
-Soundcard modem support for 1200 baud AFSK modulation
+Soundmodem 1200 baud AFSK using floating point
CONFIG_SOUNDMODEM_AFSK1200_FP
This option enables floating point calculations to be used for the
AFSK1200 baud modem. The Intel Pentium is a perverted chip because
- integer multiplications are, altough easier to implement in silicon,
- an order of a magnitude slower than floating point calculations.
+ integer multiplications are, although easier to implement in silicon,
+ an order of magnitude slower than floating point calculations.
Enabling this option uses a highly optimized assembler routine for
- correlations, modelled after the one published by Phil Karn, KA9Q.
- This reduces the computing power needed on Intel Pentium chips to about
- 50%. On the other hand, Pentium clones with faster integer multiply and
- slower floating point multiply will probably take longer with this
- option turned on. As a rule of thumb, enable it for Intel Pentium and
- Pentium Pro processors, and disable it for anything else.
+ correlations, modeled after the one published by Phil Karn, KA9Q.
+ This reduces the computing power needed on Intel Pentium chips to
+ about 50%. On the other hand, Pentium clones with faster integer
+ multiply and slower floating point multiply will probably take
+ longer with this option turned on. As a rule of thumb, enable it for
+ Intel Pentium and Pentium Pro processors, and disable it for
+ anything else.
I (sailer@ife.ee.ethz.ch) am very interested in figures. If you are
- willing to give me a feedback, please compile the driver once with this
- option enabled and once with it disabled, and send me the cycle counter
- numbers obtained with both compilations, and your exact chip. The cycle
- counter numbers can be optained by a recent sethdlc utility.
+ willing to give me a feedback, please compile the driver once with
+ this option enabled and once with it disabled, and send me the cycle
+ counter numbers obtained with both compilations, and your exact
+ chip. The cycle counter numbers can be obtained with a recent
+ sethdlc utility.
Soundcard modem support for 9600 baud FSK G3RUH modulation
CONFIG_SOUNDMODEM_FSK9600
This option enables the soundmodem driver 9600 baud FSK modem,
compatible to the G3RUH standard. The demodulator requires about 4%
- of the CPU power of a Pentium 75 CPU per channel.
+ of the CPU power of a Pentium 75 CPU per channel. You can say Y to
+ both 1200 baud AFSK and 9600 baud FSK if you want (but obviously you
+ can only use one protocol at a time, depending on what the other end
+ can understand).
Serial port KISS driver for AX.25
CONFIG_MKISS
case, you also have to say Y to "Amateur Radio AX.25 Level 2"
support. 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.
+ whenever you want), say M here and read
+ Documentation/modules.txt. The module will be called mkiss.o.
PLIP (parallel port) support
CONFIG_PLIP
your kernel by about 8kB. 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. If you want to use
- both a parallel printer and PLIP, there are two cases: 1) If the
- printer and the PLIP cable are to use the same parallel port
- (presumably because you have just one), it is best to compile both
- drivers as modules and load and unload them as needed. 2) To use
- different parallel ports for the printer and the PLIP cable, you can
- say Y to the printer driver, specify the base address of the
- parallel port(s) to use for the printer(s) with the "lp" kernel
- command line option. (See the documentation of your boot loader
- (lilo or loadlin) about how to pass options to the kernel at boot
- time. The lilo procedure is also explained in the SCSI-HOWTO,
- available via ftp (user: anonymous) in
- sunsite.unc.edu:/pub/Linux/docs/HOWTO.) The standard base addresses
- as well as the syntax of the "lp" command line option can be found
- in drivers/char/lp.c. You can then say Y to this PLIP driver or,
- preferably, M in which case Documentation/networking/net-modules.txt
- tells you how to specify the port and IRQ to be used by PLIP at
- module load time.
- It's safe to say N here.
+ well as Documentation/networking/net-modules.txt. The module will be
+ called plip.o. If you want to use both a parallel printer and PLIP,
+ there are two cases: 1) If the printer and the PLIP cable are to use
+ the same parallel port (presumably because you have just one), it is
+ best to compile both drivers as modules and load and unload them as
+ needed. 2) In order to use different parallel ports for the printer
+ and the PLIP cable, you can say Y to the printer driver and specify
+ the base address of the parallel port(s) to use for the printer(s)
+ 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 lilo procedure
+ is also explained in the SCSI-HOWTO, available via ftp (user:
+ anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO.) The standard
+ base addresses as well as the syntax of the "lp" command line option
+ can be found in drivers/char/lp.c. You can then say Y to this PLIP
+ driver or, preferably, M in which case
+ Documentation/networking/net-modules.txt tells you how to specify
+ the port and IRQ to be used by PLIP at module load time. It's safe
+ to say N here.
EQL (serial line load balancing) support
CONFIG_EQUALIZER
EQL Linux driver or with a Livingston Portmaster 2e. Say Y if you
want this and read drivers/net/README.eql. 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.
+ 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.
Frame Relay (DLCI) support
CONFIG_DLCI
the net-tools package as explained in
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). If you want to compile
- it as a module, say M here and read Documentation/modules.txt.
+ 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.
Max open DLCI
CONFIG_DLCI_COUNT
Sangoma S502A FRAD 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. 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.
+ 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. 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.
Sun LANCE Ethernet support
CONFIG_SUN_LANCE
the Ethernet-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/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
+ 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. If you plan to use more
than one network card under linux, read the
Multiple-Ethernet-mini-HOWTO, available from
the Ethernet-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/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. If you plan to use
- more than one network card under linux, read the
+ 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. 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.
- Important: There have been many reports that, with some motherboards
- mixing an SMC Ultra and an Adaptec AHA1542 SCSI card causes corruption
- problems with many operating systems.
+ sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. Important: There have
+ been many reports that, with some motherboards mixing an SMC Ultra
+ and an Adaptec AHA1542 SCSI card causes corruption problems with
+ many operating systems.
SMC 9194 Support
CONFIG_SMC9194
the Ethernet-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/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. If you plan to use
- more than one network card under linux, read the
+ 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. 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.
CONFIG_LANCE
If you have a network (ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available via ftp (user: anonymous) in
- sunsite.unc.edu:/pub/Linux/docs/HOWTO. 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.
+ sunsite.unc.edu:/pub/Linux/docs/HOWTO. Some LinkSys cards are of
+ this type. 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.
3COM cards
CONFIG_NET_VENDOR_3COM
If you have a network (ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/HOWTO. Also, consider buying a new
- card, since the 3c501 is slow and obsolete. This driver is also
+ card, since the 3c501 is slow, broken, and obsolete: you will 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). 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
+ 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. 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 - and don't use 3c501s.
3c503 support
the Ethernet-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/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
+ 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. If you plan to use more
than one network card under linux, read the
Multiple-Ethernet-mini-HOWTO, available from
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. If you plan to use more
- than one network card under linux, read the
- Multiple-Ethernet-mini-HOWTO, available from
+ Documentation/networking/net-modules.txt. The module will be called
+ 3c505.o. 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.
3c507 support
the Ethernet-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/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
+ 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. 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.
-3c523 support CONFIG_ELMC
+3c523 support
+CONFIG_ELMC
If you have a network (ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/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
+ 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. If you plan to use more
than one network card under linux, read the
Multiple-Ethernet-mini-HOWTO, available from
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. If you plan to use more
- than one network card under linux, read the
- Multiple-Ethernet-mini-HOWTO, available from
+ Documentation/networking/net-modules.txt. The module will be called
+ 3c509.o. 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. 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 media type.
the Ethernet-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/HOWTO. More specific information is
in Documentation/networking/vortex.txt and in the comments at the
- beginning of drivers/net/3c59x.c. If you want to compile this
- as a module ( = code which can be inserted in and removed from the
+ beginning of 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. If you plan to use more
- than one network card under linux, read the
- Multiple-Ethernet-mini-HOWTO, available from
+ Documentation/networking/net-modules.txt. The module will be called
+ 3c59x.o. 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
Other ISA cards
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 Documentation/networking/arcnet.txt.
You might also want to have a look at the Ethernet-HOWTO, available
via ftp (user: anonymous) in sunsite.unc.edu:/pub/Linux/docs/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). If you want to compile it
- as a module, say M here and read Documentation/modules.txt as well as
+ 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. If you plan to use more
than one network card under linux, read the
Multiple-Ethernet-mini-HOWTO, available from
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 enable this option 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
+ 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.
Enable arc0s (ARCnet RFC1051 packet format)
This allows you to use RFC1051 with your ARCnet card via the virtual
arc0s device. You only need arc0s if you want to talk to ARCnet
software complying with the "old" standard, specifically, the DOS
- arcnet.com packet driver, Amigas running AmiTCP, and some variants of
- NetBSD. You do not need to enable this option to communicate with
+ arcnet.com packet driver, Amigas running AmiTCP, and some variants
+ of NetBSD. 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
the Ethernet-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/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
+ 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. If you plan to use more
than one network card under linux, read the
Multiple-Ethernet-mini-HOWTO, available from
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. If you plan to use
- more than one network card under linux, read the
- Multiple-Ethernet-mini-HOWTO, available from
+ well as Documentation/networking/net-modules.txt. The module will be
+ called depca.o. 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.
EtherWorks 3 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 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
+ Documentation/networking/net-modules.txt. The module will be called
+ ewrk3.o. 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.
SEEQ8005 support
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
+ Documentation/networking/net-modules.txt. The module will be called
+ at1700.o. 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.
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 via ftp (user: anonymous)
- in sunsite.unc.edu:/pub/Linux/docs/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
+ say Y and read the Ethernet-HOWTO, available via ftp (user:
+ anonymous) in sunsite.unc.edu:/pub/Linux/docs/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 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. If you plan to use more
than one network card under linux, read the
Multiple-Ethernet-mini-HOWTO, available from
the Ethernet-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/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
+ 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. If you plan to use more
than one network card under linux, read the
Multiple-Ethernet-mini-HOWTO, available from
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. If you plan to use more
- than one network card under linux, read the
- Multiple-Ethernet-mini-HOWTO, available from
+ Documentation/networking/net-modules.txt. The module will be called
+ eexpress.o. 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.
NI5210 support
CONFIG_NI52
If you have a network (ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available via ftp (user: anonymous) in
- sunsite.unc.edu:/pub/Linux/docs/HOWTO. If you plan to use more than
+ sunsite.unc.edu:/pub/Linux/docs/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. 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 Ethernet-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/HOWTO. 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
+ Documentation/networking/net-modules.txt. The module will be called
+ ni65.o. 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.
Ottawa PI and PI/2 support
CONFIG_PI
This is a driver for the Ottawa Amateur Radio Club PI and PI2 cards,
- which are commonly used to send internet traffic over amateur radio.
+ which are commonly used to send internet traffic over amateur radio.
More information about these cards is on the WWW at
http://hydra.carleton.ca/info/pi2.html (To browse the WWW, you need
to have access to a machine on the Internet that has one of the
the protocol used for digital traffic over radio links. 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.
+ read Documentation/modules.txt. The module will be called pi2.o.
Gracilis PackeTwin support
CONFIG_PT
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.
+ Documentation/networking/net-modules.txt. The module will be called
+ pt.o.
WaveLAN support
CONFIG_WAVELAN
more specific information is contained in
drivers/net/README.wavelan. 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
+ 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. If you plan to use more
than one network card under linux, read the
Multiple-Ethernet-mini-HOWTO, available from
the Ethernet-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/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
+ 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. If you plan to use more
than one network card under linux, read the
Multiple-Ethernet-mini-HOWTO, available from
the Ethernet-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/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
+ 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. If you plan to use more
than one network card under linux, read the
Multiple-Ethernet-mini-HOWTO, available from
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. If you plan to use more
- than one network card under linux, read the
- Multiple-Ethernet-mini-HOWTO, available from
+ Documentation/networking/net-modules.txt. The module will be called
+ hp100.o. 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.
NE2000/NE1000 support
CONFIG_NE2000
If you have a network (ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available via ftp (user: anonymous) in
- sunsite.unc.edu:/pub/Linux/docs/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
+ sunsite.unc.edu:/pub/Linux/docs/HOWTO. Many ethernet cards without a
+ specific driver are compatible with NE2000. 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. If you plan to use more
than one network card under linux, read the
Multiple-Ethernet-mini-HOWTO, available from
the Ethernet-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/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
+ 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. If you plan to use more
than one network card under linux, read the
Multiple-Ethernet-mini-HOWTO, available from
the Ethernet-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/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
+ 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. If you plan to use more
than one network card under linux, read the
Multiple-Ethernet-mini-HOWTO, available from
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. If you plan to use more
- than one network card under linux, read the
- Multiple-Ethernet-mini-HOWTO, available from
+ Documentation/networking/net-modules.txt. The module will be called
+ apricot.o. 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.
DE425, DE434, DE435 support
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 you have a network card of this type, say Y and read
- the Ethernet-HOWTO, available via ftp (user: anonymous) in
+ models. If you have a network card of this type, say Y and read the
+ Ethernet-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/HOWTO. More specific information is
contained in drivers/net/README.de4x5. 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
+ 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. If you plan to use more
than one network card under linux, read the
Multiple-Ethernet-mini-HOWTO, available from
CONFIG_DEC_ELCP
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. (If your card is NOT SMC
- EtherPower 10/100 PCI (smc9332dst), you can also try the driver from
- "DE425, DE434, DE435 support", above.) However, most people with a
- network card of this type will say Y here. Do read the
- Ethernet-HOWTO, available via ftp (user: anonymous) in
- sunsite.unc.edu:/pub/Linux/docs/HOWTO. More specific information is
- contained in 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). 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.
+ 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 from "DE425, DE434, DE435
+ support", above.) However, most people with a network card of this
+ type will say Y here. Do read the Ethernet-HOWTO, available via ftp
+ (user: anonymous) in sunsite.unc.edu:/pub/Linux/docs/HOWTO. More
+ specific information is contained in
+ 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.
Digi Intl. RightSwitch 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 Ethernet-HOWTO, available via ftp (user: anonymous) in
+ models. If you have a network card of this type, say Y and read the
+ Ethernet-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/HOWTO. More specific information is
contained in drivers/net/README.dgrs. 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
+ 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. If you plan to use more
than one network card under linux, read the
Multiple-Ethernet-mini-HOWTO, available from
the Ethernet-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/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
+ 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. 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 if you want to use this. 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. If you intend to use this
- pocket adaptor as well as a parallel printer, you should compile
- both drivers as modules. 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.
+ here and read Documentation/modules.txt. The module will be called
+ de600.o. If you intend to use this pocket adaptor as well as a
+ parallel printer, you should compile both drivers as modules. 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.
D-Link DE620 pocket adaptor support
CONFIG_DE620
sunsite.unc.edu:/pub/Linux/docs/HOWTO if you want to use this. 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. If you intend to use this
- pocket adaptor as well as a parallel printer, you should compile
- both drivers as modules. 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.
+ here and read Documentation/modules.txt. The module will be called
+ de620.o. If you intend to use this pocket adaptor as well as a
+ parallel printer, you should compile both drivers as modules. 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.
Token Ring driver support
CONFIG_TR
almost definitely fail if more than one 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). If you want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ 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.
Traffic Shaper (EXPERIMENTAL)
CONFIG_SHAPER
- The traffic shaper is a virtual network device that allows you to limit
- the rate of data flow over another device. See
- Documentation/networking/shaper.txt for more information.
+ The traffic shaper is a virtual network device that allows you to
+ limit the rate of outgoing data flow over another network
+ device. See Documentation/networking/shaper.txt for more
+ information. To set up and configure shaper devices, you need the
+ shapecfg program, available via ftp (user: anonymous) from
+ 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.
FDDI driver support
CONFIG_FDDI
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 linux/drivers/cdrom/cdu31a.c. See the documentation
- of your boot loader (lilo or loadlin) about how to pass options to
- the kernel. The lilo procedure is also explained in the SCSI-HOWTO.
+ parameters into linux/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. The lilo procedure is also
+ explained in the SCSI-HOWTO. If you say Y here, you should also say
+ Y to "ISO9660 cdrom filesystem support" below, because that's the
+ filesystem used on CDROMs. 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.
Standard Mitsumi [no XA/Multisession] CDROM 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).
- 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.
- Note that this driver does not support XA or MultiSession CDs (PhotoCDs).
- There is a new driver (next question) which can do this. If you want
- that one, say N here.
- If the driver doesn't work out of the box, you might want to have
- a look at linux/include/linux/mcd.h.
+ 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).
+ 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.
+ Note that this driver does not support XA or MultiSession CDs
+ (PhotoCDs). There is a new driver (next question) which can do
+ this. If you want that one, say N here.
+ If the driver doesn't work out of the box, you might want to have a
+ look at linux/include/linux/mcd.h. If you say Y here, you should
+ also say Y to "ISO9660 cdrom filesystem support" below, because
+ that's the filesystem used on CDROMs. Please also read the file
+ Documentation/cdrom/mcd. 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.
Mitsumi [XA/MultiSession] support
CONFIG_MCDX
FX-001 or FX-001D CDROM 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. Check out Documentation/cdrom/mcdx.
+ interface card.
+ If you say Y here, you should also say Y to "ISO9660 cdrom
+ filesystem support" below, because that's the filesystem used on
+ CDROMs. Please also read the file Documentation/cdrom/mcdx. 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.
Matsushita/Panasonic/Creative, Longshine, TEAC CDROM support
CONFIG_SBPCD
card can support up to four CDROM drives; if you say Y here, you
will be asked how many controllers you have. If compiled as a
module, only one interface card (but with up to four drives) is
- usable.
+ usable.
+ If you say Y here, you should also say Y to "ISO9660 cdrom
+ filesystem support" below, because that's the filesystem used on
+ CDROMs. Please also read the file Documentation/cdrom/sbpcd. 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.
Matsushita/Panasonic, ... second CDROM controller support
CONFIG_SBPCD2
Say Y here only if you have two CDROM controller boards 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
- linux/include/linux/sbpcd.h before compiling the new kernel.
+ linux/include/linux/sbpcd.h before compiling the new kernel. Read
+ the file Documentation/cdrom/sbpcd.
Aztech/Orchid/Okano/Wearnes/TXC/CyDROM CDROM support
CONFIG_AZTCD
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 interface, such as Aztech
- CDA269-031SE.
+ CDA269-031SE. If you say Y here, you should also say Y to "ISO9660
+ cdrom filesystem support" below, because that's the filesystem used
+ on CDROMs. Please also read the file Documentation/cdrom/aztcd. 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.
Sony CDU535 CDROM support
CONFIG_CDU535
- This is the driver for the older Sony CDU-535 and CDU-531 CDROM drives.
+ This is the driver for the older Sony CDU-535 and CDU-531 CDROM
+ drives. If you say Y here, you should also say Y to "ISO9660 cdrom
+ filesystem support" below, because that's the filesystem used on
+ CDROMs. Please also read the file Documentation/cdrom/sonycd535.
+ 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.
Goldstar R420 CDROM support
CONFIG_GSCD
- If this is your CDROM drive, say Y here.
- As described in linux/Documentation/cdrom/gscd, you might have to
- change a setting in the file include/linux/gscd.h before compiling
- the kernel.
+ If this is your CDROM drive, say Y here. As described in
+ linux/Documentation/cdrom/gscd, you might have to change a setting
+ in the file include/linux/gscd.h before compiling the kernel. Please
+ read the file Documentation/cdrom/gscd. If you say Y here, you
+ should also say Y to "ISO9660 cdrom filesystem support" below,
+ because that's the filesystem used on CDROMs. 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.
MicroSolutions backpack CDROM support
CONFIG_BPCD
MicroSolutions backpack CDROM is an external drive that connects to
- the parallel port. The bpcd driver supports model 164550 (and perhaps
- other models). Say Y if you have one of these, and read the
- file linux/Documentation/cdrom/bpcd. If you have several different
- devices that will share a common parallel port, say M and build them
- as modules.
+ the parallel port. This driver supports model 164550 (and perhaps
+ other models). Say Y if you have one of these, and read the file
+ Documentation/cdrom/bpcd. If you say Y here, you should also say Y
+ to "ISO9660 cdrom filesystem support" below, because that's the
+ filesystem used on CDROMs. If you have several different devices
+ that will share a common parallel port, say M and build them as
+ modules. This module will be called bpcd.o.
Philips/LMS CM206 CDROM support
CONFIG_CM206
If you have a Philips/LMS CDROM drive cm206 in combination with a
- cm260 host adapter card, say Y here.
+ cm260 host adapter card, say Y here. Please also read the file
+ Documentation/cdrom/cm206. If you say Y here, you should also say Y
+ to "ISO9660 cdrom filesystem support" below, because that's the
+ filesystem used on CDROMs. 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.
Optics Storage DOLPHIN 8000AT CDROM support
CONFIG_OPTCD
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.
+ one. Please read the file Documentation/cdrom/optcd.
+ If you say Y here, you should also say Y to "ISO9660 cdrom
+ filesystem support" below, because that's the filesystem used on
+ CDROMs. 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.
Sanyo CDR-H94A CDROM support
CONFIG_SJCD
- If this is your CDROM drive, say Y here. Command line option
- (or 'append=' option in /etc/lilo.conf) is:
- sjcd=<port>
- Here 'port' is the base i/o address used by the drive. It defaults
- to port=0x340.
+ If this is your CDROM drive, say Y here and read the file
+ Documentation/cdrom/sjcd. You should then also say Y to "ISO9660
+ cdrom filesystem support" below, because that's the filesystem used
+ on CDROMs. 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.
Soft configurable cdrom interface card support
CONFIG_CDI_INIT
If you want to include boot-time initialization of any cdrom
- interface card that is software configurable, say Y here.
- Currently only the ISP16/MAD16/Mozart cards are supported.
+ interface card that is software configurable, say Y here. Currently
+ only the ISP16/MAD16/Mozart soundcards with built-in cdrom
+ interfaces are supported. 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.
ISP16/MAD16/Mozart soft configurable cdrom interface support
CONFIG_ISP16_CDI
- If you want any of these cdrom interface cards based on the
- OPTi 82C928 or 82C929 chips get detected and possibly configured
- at boot time, please say Y. Boot time command line options (or
- 'append=' options in /etc/lilo.conf) are:
- isp16=<port>,<irq>,<dma>,<drive_type>
- Here 'port','irq' and 'dma' are the base i/o address, irq number and
- dma line assumed to be used by the attached cdrom
- drive. 'drive_type' is the type of cdrom drive or its emulation
- mode. Valid values for drive_type include: Sanyo, Panasonic (same as
- Sanyo), Sony and Mitsumi. Default values are: port=0x340, irq=0,
- dma=0, drive_type=Sanyo.
- The command line
- isp16=noisp16
- will skip detection and configuration after all.
- N.B. options are case sensitive.
- Read Documentation/cdrom/isp16 for details.
+ These are soundcards with with built-in cdrom interfaces using the
+ OPTi 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. 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.
Quota support
CONFIG_QUOTA
leaner. You don't want to use it on your harddisk because of certain
built-in restrictions. This option will enlarge your kernel by about
25 kB. Everyone should say Y or M so that they are able to read this
- common floppy format. 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. Note that the filesystem of your root
- partition cannot be compiled as a module.
+ common floppy format. 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 filesystem of your root partition cannot be compiled as a
+ module.
Second extended fs support
CONFIG_EXT2_FS
transition to a *real* Linux partition later. Another (rare) case
which doesn't require ext2fs is a diskless Linux box which mounts
all files over the network using NFS (in this case it's sufficient
- to enable NFS filesystem support below; if you are planning to do
- this, have a look at the netboot package in
- /pub/Linux/system/Linux-boot/, available via ftp (user: anonymous)
- from sunsite.unc.edu, extract with "tar xzvf filename"). There is a
- short ext2fs-FAQ, available via ftp (user: anonymous) in
+ to say Y to "NFS filesystem support" below). There is a short
+ ext2fs-FAQ, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/faqs. This option will enlarge your
- kernel by about 41 kB. Default is Y.
+ kernel by about 41 kB. If you want to compile this filesystem 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 filesystem of your root partition cannot be
+ compiled as a module, and so this could be dangerous. Most everyone
+ wants to say Y here.
fat fs support
CONFIG_FAT_FS
If you want to use one of the FAT-based filesystems (the MS-DOS,
- VFAT (Windows'95) and UMSDOS filesystems), then you must include
- FAT support. This is not a filesystem in itself, but it provides
- the foundation for the other filesystems. This option will enlarge
- your kernel about 24 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. 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 filesystem of your root partition cannot be a module.
+ VFAT (Windows'95) and UMSDOS (used to run Linux on top of an
+ ordinary DOS partition) filesystems), then you must include FAT
+ support. This is not a filesystem in itself, but it provides the
+ foundation for the other filesystems. This option will enlarge your
+ kernel by about 24 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 filesystems into the kernel - they will have to
+ be modules as well. The filesystem of your root partition cannot be
+ a module, so don't say M here if you intend to use UMSDOS as your
+ root filesystem.
msdos fs support
CONFIG_MSDOS_FS
work if you said Y to "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. Note that the filesystem of your
- root partition cannot be a module.
+ and read Documentation/modules.txt. The module will be called
+ msdos.o.
vfat fs support
CONFIG_VFAT_FS
partitions. It does not support Windows'95 compressed filesystems.
You cannot use the VFAT filesystem for your root partition; use
UMSDOS instead. This option enlarges your kernel by about 10 kB and
- it only works if you enabled the "fat fs support" above. Please read
+ it only works if you said Y to the "fat fs support" above. Please read
the file Documentation/filesystems/vfat.txt for details.
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.
+ you want), say M here and read Documentation/modules.txt. The module
+ will be called vfat.o.
umsdos: Unix like fs on top of std MSDOS fs
CONFIG_UMSDOS_FS
is to write files with long unix filenames to MSDOS floppies; it
also allows unix style softlinks 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. This
+ make use of umsdos; read Documentation/filesystems/umsdos.txt. This
option enlarges your kernel by about 25 kB and it only works if you
- enabled both "fat fs support" and "msdos fs support" above. 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. Note that the filesystem of your root
- partition cannot be a module.
+ said Y to both "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 filesystem of your root partition cannot be
+ a module, so this could be dangerous. If unsure, say N.
/proc filesystem support
CONFIG_PROC_FS
example, "cat /proc/interrupts" gives information about what the
different IRQs are used for at the moment (there is a small number
of Interrupt ReQuest lines in your computer that are used by the
- periphery to gain the CPU's attention - often a source of trouble if
- two devices are mistakenly configured to use the same IRQ). Several
- programs depend on this, so everyone should say Y here.
+ attached devices to gain the CPU's attention - often a source of
+ trouble if two devices are mistakenly configured to use the same
+ IRQ). Several programs depend on this, so everyone should say Y
+ here.
NFS filesystem support
CONFIG_NFS_FS
If you are connected to some other (usually local) Unix computer
- (using SLIP, PLIP, PPP or ethernet) and want to mount files
- residing on that computer (the NFS server) using the Network
- File Sharing protocol, say Y. "Mounting files" means that the client
- can access the files with usual UNIX commands as if they were
- sitting on the client's harddisk. For this to work, the server must
- run the programs nfsd and mountd (but does not need to have NFS
- filesystem support enabled). NFS is explained in the Network
- Administrator's Guide, available via ftp (user: anonymous) in
+ (using SLIP, PLIP, PPP or ethernet) and want to mount files residing
+ on that computer (the NFS server) using the Network File Sharing
+ protocol, say Y. "Mounting files" means that the client can access
+ the files with usual UNIX commands as if they were sitting on the
+ client's harddisk. For this to work, the server must run the
+ programs nfsd and mountd (but does not need to have NFS filesystem
+ support enabled). NFS is explained in the Network Administrator's
+ Guide, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/LDP, and on its man page: "man
nfs". There is also a NFS-FAQ in
sunsite.unc.edu:/pub/Linux/docs/faqs which presumes that you know
to TCP/IP networking also. This option would enlarge your kernel by
about 27 kB. This filesystem 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. If you configure a diskless
- machine which will mount its root filesystem over nfs, you cannot
- compile this driver as a module. If you don't know what all this is
- about, say N.
+ 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. If you configure a diskless machine which
+ will mount its root filesystem over nfs (in order to do that, check
+ out the netboot package, available via ftp (user: anonymous) from
+ sunsite.unc.edu in /pub/Linux/system/Linux-boot/, extract with "tar
+ xzvf filename", and say Y to "Root file system on NFS" below), then
+ you cannot compile this driver as a module. If you don't know what
+ all this is about, say N.
Root file system on NFS
CONFIG_ROOT_NFS
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.
+ Documentation/modules.txt. The module will be called isofs.o.
OS/2 HPFS filesystem support (read only)
CONFIG_HPFS_FS
able to read them. Read Documentation/filesystems/hpfs.txt. This
filesystem 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. If unsure, say N.
+ 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.
System V and Coherent filesystem support
CONFIG_SYSV_FS
SCO, Xenix and Coherent are commercial Unix systems for intel
- machines. Enabling this option would allow you to read and write to
- and from their floppies and harddisk partitions. If you have a
- floppy or harddisk partition like that, it is probable that they
- contain binaries from those other Unix systems; in order to run
- these binaries, you will want to install iBCS2 (iBCS2 [Intel Binary
+ machines. Saying Y here would allow you to read and write to and
+ from their floppies and harddisk partitions. If you have a floppy or
+ harddisk partition like that, it is probable that they contain
+ binaries from those other Unix systems; in order to run these
+ binaries, you will want to install iBCS2 (iBCS2 [Intel Binary
Compatibility Standard] is a kernel module which lets you run SCO,
Xenix, Wyse, Unix Ware, Dell Unix and System V programs under Linux
and is often needed to run commercial software, most prominently
kernel by about 34 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. If you haven't heard about all of this
- before, it's safe to say N.
+ 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.
BSD UFS filesystem support (read only)
CONFIG_UFS_FS
BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD
and NeXTstep) use a filesystem called UFS. Some System V Unixes can
- create and mount partitions and diskettes using this filesystem
- as well. Enabling this option allows you to mount these partitions
- and diskettes read-only. If you only intend to mount files from
- some other Unix over the network using NFS, you don't need the
- UFS filesystem support (but you need nfs filesystem support
+ create and mount partitions and diskettes using this filesystem as
+ well. Saying Y here allows you to mount these partitions and
+ diskettes read-only. If you only intend to mount files from some
+ other Unix over the network using NFS, you don't need the UFS
+ filesystem support (but you need nfs filesystem 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"). When accessing NeXTstep
- files, you may need to convert them from the NeXT character set
- to the Latin1 character set; use GNU recode for this purpose.
- Say Y to build UFS support into your kernel. 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. If you haven't heard about all of this
- before, it's safe to say N.
+ directories between unixes (and even other operating systems) is
+ given by the tar program ("man tar"). When accessing NeXTstep files,
+ you may need to convert them from the NeXT character set to the
+ Latin1 character set; use GNU recode for this purpose. Say Y to
+ build UFS support into your kernel. 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 ufs.o. If you
+ haven't heard about all of this before, it's safe to say N.
BSD disklabel (FreeBSD partition tables) support
CONFIG_BSD_DISKLABEL
FreeBSD uses its own partition scheme on your PC. It requires only
one entry in the primary partition table of your disk and manages it
similarly to DOS extended partitions, putting in its first sector a
- new partition table in disklabel format. Enabling this option allows
- you to read these disklabels and further mount FreeBSD partitions on
- your Linux box if you also have configured BSD ufs filesystem
- support. If you don't know what all this is about, say N.
+ new partition table in disklabel format. Saying Y here allows you to
+ read these disklabels and further mount FreeBSD partitions on your
+ Linux box if you also have configured BSD ufs filesystem support. If
+ you don't know what all this is about, say N.
SMD disklabel (Sun partition tables) support
CONFIG_SMD_DISKLABEL
Like most systems, SunOS uses its own partition table format,
- incompatible with all others. Enabling this option allows you to read
- these partition tables and further mount SunOS disks on your Linux
- box if you also have configured BSD ufs filesystem support. This is
- mainly used to carry data from a Sparc under SunOS to your Linux box
- via a removable medium like magneto-optical or ZIP drives. If you
- don't know what all this is about, say N.
+ incompatible with all others. Saying Y here allows you to read these
+ partition tables and further mount SunOS disks on your Linux box if
+ you also have configured BSD ufs filesystem support. This is mainly
+ used to carry data from a Sparc under SunOS to your Linux box via a
+ removable medium like magneto-optical or ZIP drives. If you don't
+ know what all this is about, say N.
SMB filesystem support (to mount WfW shares etc..)
CONFIG_SMB_FS
SMB (Server Message Buffer) is the protocol Windows for Workgroups
- (WfW), Windows NT and Lan Manager use to talk to each other over an
- ethernet. Enabling this allows you to mount their filesystems (often
- called "shares") and access them just like any other unix
- directory. For details, read Documentation/filesystems/smbfs.txt.
- 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 enable this filesystem
- support; you can use the program samba (available via ftp (user:
- anonymous) in sunsite.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://eats.com/linux_mac_win.html (to browse the WWW, you need to
- have access to a machine on the Internet that has one of the
- programs lynx, netscape or Mosaic). 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. Most people say N, however.
+ (WfW), Windows 95, Windows NT and Lan Manager use to share files and
+ printers over local networks. Saying Y here allows you to mount
+ their filesystems (often called "shares" in this context) and access
+ them just like any other unix directory. For details, read
+ Documentation/filesystems/smbfs.txt. 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
+ sunsite.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://eats.com/linux_mac_win.html (to browse the WWW,
+ you need to have access to a machine on the Internet that has one of
+ the programs lynx, netscape or Mosaic). 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.
SMB Win95 bug work-around
CONFIG_SMB_WIN95
NCP filesystem support (to mount NetWare volumes)
CONFIG_NCP_FS
NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
- used by Novel NetWare clients to talk to file servers. It is to IPX
- what nfs is to tcp/ip, if that helps. Enabling this option allows
- you to mount NetWare file server volumes and to access them just
- like any other Unix directory. For details, please read the file
+ 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 on sunsite.unc.edu:/pub/Linux/docs/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.
+ read Documentation/modules.txt. The module will be called
+ ncpfs.o. Say N unless you are connected to a Novell network.
-Amiga FFS filesystem support (EXPERIMENTAL)
+Amiga FFS filesystem support
CONFIG_AFFS_FS
- The Fast File System (FFS) is the common filesystem used on harddisks
- by Amiga (tm) Systems since AmigaOS Version 1.3 (34.20). It's also
- possible to mount diskfiles used by the Un*X Amiga Emulator by Bernd
- Schmidt (http://www-users.informatik.rwth-aachen.de/~crux/uae.html)
- If you want to do the latter, you will also need the loop device
- support. Say Y if you want to be able to read and write files from
- and to an Amiga FFS partition of your harddrive. 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. This filesystem 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.
- If unsure, say N.
+ The Fast File System (FFS) is the common filesystem used on
+ harddisks by Amiga(tm) Systems since AmigaOS Version 1.3
+ (34.20). With this driver you can also mount diskfiles used by the
+ Un*X Amiga Emulator by Bernd Schmidt
+ (http://www-users.informatik.rwth-aachen.de/~crux/uae.html). If you
+ want to do the latter, you will also need to say Y to "Loop device
+ support", above. Say Y if you want to be able to read and write
+ files from and to an Amiga FFS partition on your harddrive. 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. This filesystem 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.
-ROMFS filesystem support (EXPERIMENTAL)
+ROM filesystem support
CONFIG_ROMFS_FS
- This is a special file system intended for installation disks or
- otherwise prebuilt medias. It has very low overhead and low memory
- requirements. However, it's read-only (one particular reason of the
- smallness), so you need extra programs to prepare disks in this
- format. If you are not sure, just say N, you don't need it.
+ This is a very small read-only filesystem mainly intended for
+ initial ram disks of installation disk, but it could be used for
+ other read-only media as well. Read
+ Documentation/filesystems/romfs.txt for details. This filesystem 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 compile it as a module, say M here
+ and read Documentation/modules.txt. If you don't know whether you
+ need it, then you don't need it: say N.
Standard/generic serial support
CONFIG_SERIAL
setting up dedicated ethernet WWW/ftp servers, or users that have
one of the various bus mice instead of a serial mouse. (Note that
the Cyclades and Stallion multi serial port drivers do not need this
- driver built in for them to work. They are completely independent of
- each other.) If you want to compile this driver as a module, say M
- here and read Documentation/modules.txt. [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 kerneld
- automatically unloads the driver. This limitation may be lifted in
- the future.] Most people will say Y or M here, so that they can use
- serial mice, modems and similar devices connecting to the standard
- serial ports.
+ 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. [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 kerneld automatically unloads the
+ driver. This limitation may be lifted in the future.] BTW: If you
+ have a mouseman serial mouse which is not recognized by the X window
+ system, try running gpm first. Most people will say Y or M here, so
+ that they can use serial mice, modems and similar devices connecting
+ to the standard serial ports.
Digiboard PC/Xx Support
CONFIG_DIGI
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 BBS. If you have a card like that, say Y here and
- read the file Documentation/digiboard.txt.
+ read the 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.
SDL RISCom/8 card support
CONFIG_RISCOM8
This is a driver for the SDL Communications RISCom/8 multiport card,
- 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 BBS. If you have a card like that, say Y here and
- read the file Documentation/riscom8.txt. Also it's possible to say
- M here and compile this driver as kernel loadable module.
+ 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 BBS. If you have a card like that, say Y here
+ and read the 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.
Cyclades async mux support
CONFIG_CYCLADES
your linux box, for instance in order to become a BBS. 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. If you haven't heard about it, it's
- safe to say N. (As of 1.3.9x kernels, this driver's minor numbers
- start at 0 instead of 32.)
+ read Documentation/modules.txt. The module will be called
+ cyclades.o. If you haven't heard about it, it's safe to say N. (As
+ of 1.3.9x kernels, this driver's minor numbers start at 0 instead of
+ 32.)
Stallion multiport serial support
CONFIG_STALDRV
heard about all this, it's safe to say N.
Stallion EasyIO or EC8/32 support
-CONFIG_STALLION n
+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
drivers/char/README.stallion. 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.
+ Documentation/modules.txt. The module will be called stallion.o.
Stallion EC8/64, ONboard, Brumby support
CONFIG_ISTALLION
serial multiport card, say Y here. Make sure to read
drivers/char/README.stallion. 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.
+ whenever you want), say M here and read
+ Documentation/modules.txt. The module will be called istallion.o.
Hayes ESP serial port support
CONFIG_ESPSERIAL
to transfer data to and from the host. Make sure to read
drivers/char/README.esp. 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.
+ whenever you want), say M here and read
+ Documentation/modules.txt. The module will be called esp.o.
+ If unsure, say N.
Hayes ESP serial port DMA channel
CONFIG_ESPSERIAL_DMA_CHANNEL
- This is the DMA channel to be used to transfer data to and from the host.
- One DMA channel is shared between all the ESP ports. Valid values are
- 1 and 3.
+ This is the DMA channel to be used to transfer data to and from the
+ host. One DMA channel is shared between all the ESP ports. Valid
+ values are 1 and 3.
Hayes ESP serial port trigger level
CONFIG_ESPSERIAL_TRIGGER_LEVEL
- This is the trigger level (in bytes) of the transmit FIFO and the receive
- FIFO. Larger values may result in fewer interrupts; however, a value too
- high could result in data loss. Valid values are 1 through 1015.
+ This is the trigger level (in bytes) of the transmit FIFO and the
+ receive FIFO. Larger values may result in fewer interrupts;
+ however, a value too high could result in data loss. Valid values
+ are 1 through 1015.
Parallel printer support
CONFIG_PRINTER
sunsite.unc.edu:/pub/Linux/docs/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. If you want to use both a parallel
- printer and PLIP, there are two cases: 1) If the printer and the
- PLIP cable are to use the same parallel port (presumably because you
- have just one), it is best to compile both drivers as modules and
- load and unload them as needed. 2) To use different parallel ports
- for the printer and the PLIP cable, you can say Y to this printer
- driver, specify the base address of the parallel port(s) to use for
- the printer(s) with the "lp" kernel command line option. (See the
- documentation of your boot loader (lilo or loadlin) about how to
- pass options to the kernel at boot time. The lilo procedure is also
- explained in the SCSI-HOWTO, available via ftp (user: anonymous) in
+ Documentation/modules.txt. The module will be called plip.o. If you
+ want to use both a parallel printer and PLIP, there are two cases:
+ 1) If the printer and the PLIP cable are to use the same parallel
+ port (presumably because you have just one), it is best to compile
+ both drivers as modules and load and unload them as needed. 2) To
+ use different parallel ports for the printer and the PLIP cable, you
+ can say Y to this printer driver, specify the base address of the
+ parallel port(s) to use for the printer(s) 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 lilo procedure is also explained in the
+ SCSI-HOWTO, available via ftp (user: anonymous) in
sunsite.unc.edu:/pub/Linux/docs/HOWTO.) The standard base addresses
as well as the syntax of the "lp" command line option can be found
in drivers/char/lp.c. You can then say Y to the PLIP driver or,
sunsite.unc.edu:/pub/Linux/docs/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. If you are unsure, say N and read the
- HOWTO nevertheless: it will tell you what you have.
+ 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
sunsite.unc.edu:/pub/Linux/system/Misc, solves this problem. If you
want to compile this mouse 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. If you are unsure,
- say N and read the HOWTO nevertheless: it will tell you what you
- have.
+ say M here and read Documentation/modules.txt. The module will be
+ called psaux.o. If you are unsure, say N and read the HOWTO
+ nevertheless: it will tell you what you have.
C&T 82C710 mouse port support (as on TI Travelmate)
CONFIG_82C710_MOUSE
(user: anonymous) in sunsite.unc.edu:/pub/Linux/docs/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. 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 about 'Microsoft busmouse' and
- actually mean PS/2 busmouse - so count the pins on the connector.
+ and read Documentation/modules.txt. The module will be called
+ msbusmouse.o. 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 about 'Microsoft busmouse' and actually mean
+ PS/2 busmouse - so count the pins on the connector.
ATIXL busmouse support
CONFIG_ATIXL_BUSMOUSE
anonymous) in sunsite.unc.edu:/pub/Linux/docs/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. If you are unsure, say N and read
- the HOWTO nevertheless: it will tell you what you have.
+ read 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.
Support for user miscellaneous modules
CONFIG_UMISC
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.
+ and read Documentation/modules.txt. The module will be called
+ tpqic02.o.
Do you want runtime configuration for QIC-02
CONFIG_QIC02_DYNCONF
If you have a tape drive that is connected to your floppy
controller, say Y here. Some tape drives (like the Iomega Ditto
3200) come with a high speed controller of its own. These drives
- (and their companion controller) is also supported. If you have a
- special controller (such as the CMS FC-10, FC-20, Iomega Mach-II, or
- Ditto Dash), you must configure it by editing the file
+ (and their companion controller) are also supported by this driver,
+ so say Y if you have one. If you have a special controller (such as
+ the CMS FC-10, FC-20, Iomega Mach-II, or Ditto Dash), you must say Y
+ here and configure it by editing the file
drivers/char/ftape/Makefile. If you want to use such a tape drive on
a PCI-bus based system, please read the file
drivers/char/ftape/README.PCI. This 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.
+ Documentation/modules.txt. The module will be called ftape.o.
Zilog serial support
CONFIG_SUN_ZS
also don't have compliant BIOSes, and this driver will cause those
machines to panic during the boot phase (typically, these machines
are using a data segment of 0040, which is reserved for the Linux
- kernel). If you get random kernel OOPSes that don't seem to be
- related to anything and you have a motherboard with APM support, try
- disabling/enabling this option. Generally, if you don't have a
- battery in your machine, there isn't much point in using this
- driver.
+ kernel). Generally, if you don't have a battery in your machine,
+ there isn't 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. Some other
+ things to try when experiencing seemingly random, "weird" problems:
+ 1) passing the "no-hlt" option to the kernel
+ 2) passing the "no-387" option to the kernel
+ 3) passing the "mem=4M" option to the kernel (thereby disabling
+ all but the first 4M of RAM)
+ 4) Reading the sig11 FAQ at http://www.bitwizard.nl/sig11/
+ 5) disabling the cache from your BIOS settings
+ 6) installing a better fan
+ 7) exchanging RAM chips
+ 8) exchanging the motherboard.
+
Ignore USER SUSPEND
CONFIG_APM_IGNORE_USER_SUSPEND
Watchdog Timer Support
CONFIG_WATCHDOG
- If you enable this option and create a character special file
- /dev/watchdog with major number 10 and minor number 130 using mknod
- ("man mknod"), you will get a watchdog, i.e.: subsequently opening
- the file and failing to write to it for longer than 1 minute will
- result in rebooting the machine. This could be useful for a
- networked machine that needs to come back online as fast as possible
- after a lock-up. There's a watchdog 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. If
- unsure, 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). If you want to compile it as a module, say M
- here and read Documentation/modules.txt.
+ 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
+ number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
+ subsequently opening the file and failing to write to it for longer
+ than 1 minute will result in rebooting the machine. This could be
+ useful for a networked machine that needs to come back online as
+ fast as possible after a lock-up. There's both a watchdog
+ 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.
+ The watchdog is usually used together with the watchdog daemon which
+ is available via ftp (user: anonymous) from
+ 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.
+ If unsure, say N.
Disable watchdog shutdown on close
CONFIG_WATCHDOG_NOWAYOUT
- The default watchdog behaviour is to stop the timer if the process
- managing it closes the file /dev/watchdog. It's always remotely
- possible that this process might get killed. If you enable this
- option, the watchdog cannot be stopped once it has been started.
+ The default watchdog behaviour (which you get if you say N here) is
+ to stop the timer if the process managing it closes the file
+ /dev/watchdog. It's always remotely possible that this process might
+ get killed. If you say Y here, the watchdog cannot be stopped once
+ it has been started.
WDT Watchdog timer
CONFIG_WDT
source at the top of drivers/char/wdt.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.
+ Documentation/modules.txt. The module will be called wdt.o.
WDT501 features
CONFIG_WDT_501
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.
+ it as a module, say M here and read Documentation/modules.txt. The
+ module will be called softdog.o.
Berkshire Products PC Watchdog
CONFIG_PCWATCHDOG
This card simply watches your kernel to make sure it doesn't freeze,
and if it does, it resets your computer after a certain amount of
time. This driver is like the WDT501 driver but for different
- hardware. The PC watchdog cards can be ordered from
- http://www.berkprod.com. Some example rc.local files are available
- from ftp.bitgate.com. 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. Most people will say N.
-
-Support for Revision A cards
-CONFIG_PCWD_REV_A
- This gives you support for revision A or B of the Berkshire PC Watchdog
- Card. The way to tell if you have an A or B style card is to check the
- manual on page 22. If it doesn't say "Port 3" at the top, you have a
- revision A or B card. Also, if your card doesn't have an audible beep,
- chances are you have a revision A or B card.
-
-Support for Revision C cards
-CONFIG_PCWD_REV_C
- This card gives you an audible beep. It also has support for disabling
- the card, enabling it, getting firmware versions, and a few other options.
-
-Show card state on reset
-CONFIG_PCWD_SHOW_PREVSTAT
- Enabling this option will display the previous reset state of your card.
- It will also give a little more verbose data about the card, or your
- system's previous status before reset.
+ hardware. Please read Documentation/pcwd-watchdog.txt. The PC
+ watchdog cards can be ordered from http://www.berkprod.com. Some
+ example rc.local files are available from ftp.bitgate.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. Most people will say N.
Enhanced Real Time Clock Support
CONFIG_RTC
- If you enable this option and create a character special file
- /dev/rtc with major number 10 and minor number 135 using mknod ("man
- mknod"), you will get access to the real time clock built into your
+ If you say Y here and create a character special file /dev/rtc with
+ major number 10 and minor number 135 using mknod ("man mknod"), you
+ will get access to the real time clock built into your
computer. Every PC has such a clock built in. It can be used to
generate signals from as low as 1Hz up to 8192Hz, and can also be
used as a 24 hour alarm. It reports status information via the file
/proc/rtc and its behaviour is set by various ioctls on
/dev/rtc. People running SMP (= multiprocessor) versions of Linux
- should enable this option to read and set the RTC clock in a SMP
- compatible fashion. If you think you have a use for such a device
- (such as periodic data sampling), then say Y here, and go read the
- file Documentation/rtc.txt for details.
+ should say Y here to read and set the RTC clock in a SMP compatible
+ fashion. If you think you have a use for such a device (such as
+ periodic data sampling), then say Y here, and go read the file
+ Documentation/rtc.txt for details.
Sound card support
CONFIG_SOUND
that are at
sunsite.unc.edu:/pub/Linux/kernel/patches/console/pcsndrv-X.X.tar.gz,
to be extracted with "tar xzvf filename".
- This driver is also available as a module ( = code which can be inserted
- in and removed from the running kernel whenever you want) on the
- Motorola 680x0 architecture. If you are compiling a kernel for
- Linux/m68k and want to compile this driver as a module, say M here
- and read Documentation/modules.txt.
ProAudioSpectrum 16 support
CONFIG_PAS
Gravis Ultrasound support
CONFIG_GUS
- Enable this option for any type of Gravis Ultrasound card, including
+ Say Y here for any type of Gravis Ultrasound card, including
the GUS or GUS MAX.
MPU-401 support (NOT for SB16)
CONFIG_MPU401
Be careful with this question. The MPU401 interface is supported by
all soundcards. However, some natively supported cards have their
- own driver for MPU401. Enabling the MPU401 option with these cards
+ 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
16 bit sampling option of GUS (_NOT_ GUS MAX)
CONFIG_GUS16
Answer Y if you have installed the 16 bit sampling daughtercard on
- your GUS. Answer N if you have a GUS MAX, since enabling this
- option disables GUS MAX support.
+ your GUS. Answer N if you have a GUS MAX, since saying Y here
+ disables GUS MAX support.
GUS MAX support
CONFIG_GUSMAX
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 enabling this option will cause a
+ have their own MSS support and saying Y to this option will cause a
conflict.
Ensoniq Soundscape support
Support for Crystal CS4232 based (PnP) cards
CONFIG_CS4232
- Enable this if you have a card based on the Crystal CS4232 chip set.
+ Say Y here if you have a card based on the Crystal CS4232 chip set.
Support for Turtle Beach Wave Front (Maui, Tropez) synthesizers
CONFIG_MAUI
- Enable this option if you have a Turtle Beach Wave Front, Maui, or
+ Say Y here if you have a Turtle Beach Wave Front, Maui, or
Tropez sound card.
Support for Crystal CS4232 based (PnP) cards
SB32/AWE support
CONFIG_AWE32_SYNTH
-Enable this option if you have a SB32 or SB AWE soundcard. See
-linux/drivers/sound/lowlevel/README.awe for more info.
+ Say Y here if you have a SB32 or SB AWE soundcard. See
+ linux/drivers/sound/lowlevel/README.awe for more info.
+
+Additional low level drivers
+CONFIG_LOWLEVEL_SOUND
+ If you need additional low level sound drivers which are not part
+ of USS/Lite (UNIX Sound System), say Y. The only such driver at
+ present is the ACI driver for the miroSOUND PCM12 and PCM20.
+
+ACI mixer (miroPCM12)
+CONFIG_ACI_MIXER
+ Audio Command Interface (ACI) driver. ACI is a protocol used to
+ communicate with the microcontroller on some sound cards produced
+ by miro, e.g. the miroSOUND PCM12 and PCM20. The main function
+ of the ACI is to control the mixer and to get a product
+ identification. This Voxware ACI driver currently only supports
+ the ACI functions on the miroSOUND PCM12 card. On the PCM20, ACI
+ also controls the radio tuner on this card, however this is not
+ yet supported in this software.
Kernel profiling support
CONFIG_PROFILE
This is for kernel hackers who want to know how much time the kernel
spends in the various procedures. The information is stored in
- /proc/profile (enable the /proc filesystem!) and in order to read
- it, you need the readprofile package from sunsite.unc.edu. Its
+ /proc/profile (say Y to "/proc filesystem support"!) and in order to
+ read it, you need the readprofile package from sunsite.unc.edu. Its
manpage gives information regarding the format of profiling data. To
become a kernel hacker, you can start with the Kernel Hacker's Guide
at http://www.redhat.com:8080/HyperNews/get/khg.html. Mere mortals
CONFIG_PROFILE_SHIFT
This is used to adjust the granularity with which the addresses of
executed instructions get recorded in /proc/profile. But since you
- enabled "Kernel profiling support", you must be a kernel hacker and
+ said Y to "Kernel profiling support", you must be a kernel hacker and
hence you know what this is about :-)
ISDN subsystem
CONFIG_ISDN
- ISDN ("Integrated Services Digital Networks", called RNIS in
- France) is a special type of fully digital telephone line; 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 modem/telephone connections. It only works if your computer
- is equipped with an ISDN card and both you and your service provider
- purchased an ISDN line from your phone company. For details, read
- http://alumni.caltech.edu/~dank/isdn/ on the WWW. (To browse the
- WWW, you need to have access to a machine on the Internet that has
- one of the programs lynx, netscape or Mosaic.) 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, channel-bundling,
+ 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
+ modem/telephone connections, and that you can have voice
+ 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. (To
+ browse the WWW, you need to have access to a machine on the Internet
+ that has one of the programs lynx, netscape or Mosaic.) 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, 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 and 1TR6 are
- supported. See Documentation/isdn/README for more information.
+ supported. See Documentation/isdn/README for more information. If
+ you want to compile the ISDN 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.
Support synchronous PPP
CONFIG_ISDN_PPP
- This enables synchronous PPP via ISDN. This protocol is used by
- Cisco or Sun for example. So you want 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
+ Over digital connections such as ISDN, there is no need to
+ synchronize sender and recipient's clocks with start and stop bits
+ as is done over telephone lines. Instead, one can use "synchronous
+ PPP". Saying Y here will include this protocol. This 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.
Support audio via ISDN
CONFIG_ISDN_AUDIO
- With this option enabled, the modem-emulator supports a subset
- of the EIA Class 8 Voice commands. Using a getty with voice-support
+ If you say Y here, the modem-emulator will support a subset of the
+ EIA Class 8 Voice commands. Using a getty with voice-support
(mgetty+sendfax by gert@greenie.muc.de with an extension, available
- with the ISDN utility package for example), you will be able
- to use your Linux box as an ISDN-answering machine. Of course, this
- must be supported by the lowlevel driver also. Currently, the Teles
- driver is the only voice-supporting one. See
+ with the ISDN utility package for example), you will be able to use
+ your Linux box as an ISDN-answering machine. Of course, this must be
+ supported by the lowlevel driver also. Currently, the Teles driver
+ is the only voice-supporting one. See
Documentation/isdn/README.audio for more information.
ICN 2B and 4B support
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.
+ 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.
Teles, NICCY1016PC, Creatix support
CONFIG_ISDN_DRV_TELES
support a 16.0-type using EDSS1-protocol. See
Documentation/isdn/README on how to configure it using 16.3, a
different D-channel protocol, or non-standard irq/port/shmem
- settings.
+ settings. 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 teles.o.
PCBIT-D support
CONFIG_ISDN_DRV_PCBIT
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.
+ 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.
Support for AP1000 multicomputer
CONFIG_AP1000
This enables support for a sparc based parallel multi-computer
- called an AP1000+. For details on our efforts to port Linux to this
+ called AP1000+. For details on our efforts to port Linux to this
machine see http://cap.anu.edu.au/cap/projects/linux or mail to
hackers@cafe.anu.edu.au
68020 support
CONFIG_M68020
- If you anticipate running this kernel on a computer with a MC68020 processor,
- say Y. Otherwise, say N. Note that the 68020 requires a 68851 MMU
- (= memory management unit) to run Linux/m68k.
+ If you anticipate running this kernel on a computer with a MC68020
+ processor, say Y. Otherwise, say N. Note that the 68020 requires a
+ 68851 MMU (= memory management unit) to run Linux/m68k.
68030 support
CONFIG_M68030
- If you anticipate running this kernel on a computer with a MC68030 processor,
- say Y. Otherwise, say N. Note that a MC68EC030 will not work, as it does
- not include an MMU (= memory management unit).
+ If you anticipate running this kernel on a computer with a MC68030
+ processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
+ work, as it does not include an MMU (= memory management unit).
68040 support
CONFIG_M68040
- If you anticipate running this kernel on a computer with a MC68LC040 or
- MC68040 processor, say Y. Otherwise, say N. Note that an MC68EC040 will
- not work, as it does not include an MMU (= memory management unit).
+ If you anticipate running this kernel on a computer with a MC68LC040
+ or MC68040 processor, say Y. Otherwise, say N. Note that an
+ MC68EC040 will not work, as it does not include an MMU (= memory
+ management unit).
Use -m68040 flag for 68040 specific optimizations
CONFIG_OPTIMIZE_040
If you will only be running this kernel on a 68040-series processor,
- this will make the kernel run somewhat faster. However, it will no longer
- run on a 68020 or 68030, no matter whether you included 68020 and 68030
- support or not. Say N unless the only processor you are compiling support
- for is the 68040 (or 68LC040).
+ this will make the kernel run somewhat faster. However, it will no
+ longer run on a 68020 or 68030, no matter whether you included 68020
+ and 68030 support or not. Say N unless the only processor you are
+ compiling support for is the 68040 (or 68LC040).
68060 support
CONFIG_M68060
Use -m68060 flag for 68060 specific optimizations
CONFIG_OPTIMIZE_060
If you will only be running this kernel on a 68060-series processor,
- this will make the kernel run somewhat faster. However, it will no longer
- run on a 68020, 68030 or 68040, no matter whether you included support
- for those processors or not. Say N unless the only processor you are
- compiling support for is the 68060.
+ this will make the kernel run somewhat faster. However, it will no
+ longer run on a 68020, 68030 or 68040, no matter whether you
+ included support for those processors or not. Say N unless the only
+ processor you are compiling support for is the 68060.
Advanced processor options
CONFIG_ADVANCED_CPU
Amiga ECS chipset support
CONFIG_AMIFB_ECS
- This enables support for the Enhanced Chip Set, found in later A500's,
- later A2000's, the A600, the A3000, the A3000T and CDTV. If you intend to
- run Linux on any of these systems, say Y; otherwise say N.
+ This enables support for the Enhanced Chip Set, found in later
+ A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
+ you intend to run Linux on any of these systems, say Y; otherwise
+ say N.
Amiga AGA chipset support
CONFIG_AMIFB_AGA
Amiga GSP (TMS340x0) support
CONFIG_AMIGA_GSP
- Include support for Amiga graphics cards that use the Texas Instruments
- TMS340x0 GSP (= graphics signal processor) chips. Say Y if you want
- to use a DMI Resolver or Commodore A2410 (Lowell) graphics card on
- an Amiga; otherwise, say N.
+ Include support for Amiga graphics cards that use the Texas
+ Instruments TMS340x0 GSP (= graphics signal processor) chips. Say Y
+ if you want to use a DMI Resolver or Commodore A2410 (Lowell)
+ graphics card on an Amiga; otherwise, say N.
DMI Resolver support
CONFIG_GSP_RESOLVER
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 ( = 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
+ 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 ( =
+ 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.
Atari ACSI support
CONFIG_ATARI_ACSI
- This enables support for the Atari ACSI interface. This driver is
- also available as a module ( = code which can be inserted in and
- removed from the running kernel whenever you want). The driver
+ This enables support for the Atari ACSI interface. The driver
supports hard disks and CD-ROMs, which have 512-byte sectors, or can
be switched to that mode. Due to the ACSI command format, only disks
up to 1 GB are supported. Special support for certain ACSI to SCSI
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). The module will
+ be called acsi.o.
Probe all LUNs on each ACSI device
CONFIG_ACSI_MULTI_LUN
If you have an Atari SLM laser printer, say Y to include support for
it in the kernel. 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).
- Be warned: the driver needs much ST-RAM and can cause problems due
- to that fact!
+ running kernel whenever you want). The module will be called
+ acsi_slm.o. Be warned: the driver needs much ST-RAM and can cause
+ problems due to that fact!
A3000 WD33C93A support
CONFIG_A3000_SCSI
- If you have an Amiga 3000 and have SCSI devices connected to the built-in
- SCSI controller, 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). If you
- want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ If you have an Amiga 3000 and have SCSI devices connected to the
+ built-in SCSI controller, 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 wd33c93.o. If you want to compile it as a module, say M here
+ and read Documentation/modules.txt.
A2091 WD33C93A support
CONFIG_A2091_SCSI
- If you have a Commodore A2091 SCSI controller, 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). If you
- want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ If you have a Commodore A2091 SCSI controller, 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 wd33c93.o. If you want to compile it as
+ a module, say M here and read Documentation/modules.txt.
GVP Series II WD33C93A support
CONFIG_GVP11_SCSI
- If you have a Great Valley Products Series II SCSI controller, say Y.
- Also say Y if you have a later model of GVP SCSI controller (such as
- the GVP A4008 or a Combo board). Otherwise, say N.
+ If you have a Great Valley Products Series II SCSI controller, say
+ Y. Also say Y if you have a later model of GVP SCSI controller
+ (such as the GVP A4008 or a Combo board). Otherwise, say N.
This driver does NOT work for the T-Rex series of accelerators from
TekMagic and GVP-M.
- 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.
+ 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.
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, say Y. Otherwise,
- say N.
+ If you have an Amiga with an original (MkI) Phase5 Cyberstorm
+ accelerator board and the optional Cyberstorm SCSI controller, say
+ Y. Otherwise, say N.
Cyberstorm II SCSI support
CONFIG_CYBERSTORMII_SCSI
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, say N.
+ If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
+ and want to use the onboard SCSI controller, say Y. Otherwise, say
+ N.
Blizzard 1230IV/1260 SCSI support
CONFIG_BLZ1230_SCSI
- If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard 1260
- accelerator, and the optional SCSI module, say Y. Otherwise, say N.
+ If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
+ 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
+ say N.
Atari native SCSI support
CONFIG_ATARI_SCSI
Falcon, ...) say Y to get it supported. Of course also, if you have
an 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). 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 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
This option increases the delay after a SCSI arbitration to
- accomodate some flakey Toshiba CD-ROM drives. Say Y if you intend to
+ accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
use a Toshiba CD-ROM drive; otherwise, the option is not needed and
would impact performance a bit, so say N.
Ariadne support
CONFIG_ARIADNE
- If you have a VillageTronics Ariadne Ethernet 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). If you
- want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ If you have a VillageTronics Ariadne Ethernet 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 ariadne.o. If you want to compile it as
+ a module, say M here and read Documentation/modules.txt.
A2065 support
CONFIG_A2065
- If you have a Commodore A2065 Ethernet 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). If you
- want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ If you have a Commodore A2065 Ethernet 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 a2065.o. If you want to compile it as a
+ module, say M here and read Documentation/modules.txt.
Hydra support
CONFIG_HYDRA
If you have a Hydra Ethernet 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). If you
- want to compile it as a module, say M here and read
- Documentation/modules.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 is called hydra.o. If you want to compile it as a
+ module, say M here and read Documentation/modules.txt.
Atari Lance support
CONFIG_ATARILANCE
Multiface Card III parallel support
CONFIG_MULTIFACE_III_LP
If you have a Multiface III card for your Amiga, and want to use its
- parallel port in Linux, 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). If you
- want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ parallel port in Linux, 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 lp_m68k.o. If you want to compile it as a module, say M here
+ and read Documentation/modules.txt.
Amiga mouse support
CONFIG_AMIGAMOUSE
- 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). If you
- want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ 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.
Amiga Copper Console
CONFIG_COPCON
- This configures the console to use the Amiga's graphics coprocessor for
- scrolling, instead of using the CPU. This option markedly improves
- response times in the high color modes (5 bitplanes and up). If you
- would like to use this, say Y; otherwise, say N.
+ This configures the console to use the Amiga's graphics coprocessor
+ for scrolling, instead of using the CPU. This option markedly
+ improves response times in the high color modes (5 bitplanes and
+ up). If you would like to use this, say Y; otherwise, say N.
Atari mouse support
CONFIG_ATARIMOUSE
- 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). If you
- want to compile it as a module, say M here and read
- Documentation/modules.txt.
+ 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.
Atari MFP serial support
CONFIG_ATARI_MFPSER
Linux, say Y. The driver equally supports all kinds of MFP serial
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
+ 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.
Note for Falcon users: You also have an MFP port, it's just not
Atari MIDI serial support
CONFIG_ATARI_MIDI
If you want to use your Atari's MIDI port 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). If you
- want to compile it as a module, say M here and read
+ 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.
Amiga builtin serial support
CONFIG_AMIGA_BUILTIN_SERIAL
- If you want to use your Amiga's built-in serial port 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). If you
- want to compile it as a module, say M here and read
+ If you want to use your Amiga's built-in serial port 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). If you want to compile it as a module, say M here and read
Documentation/modules.txt.
GVP IO-Extender support
Multiface Card III serial support
CONFIG_MULTIFACE_III_TTY
- If you want to use a Multiface III card's serial port in Linux, say Y.
+ If you want to use a Multiface III card's serial port 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). If you
want to compile it as a module, say M here and read
Amiga or Atari DMA sound support
CONFIG_DMASOUND
- If you want to use the internal audio of your Atari or Amiga in Linux,
- answer Y to this question. This will provide a Sun-like /dev/audio,
- compatible with the Linux/i386 sound system. 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). If you
- want to compile it as a module, say M here and read
+ If you want to use the internal audio of your Atari or Amiga in
+ Linux, answer Y to this question. This will provide a Sun-like
+ /dev/audio, compatible with the Linux/i386 sound system. 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). If you want to compile it as a module, say M here and read
Documentation/modules.txt.
MSDOS partition support
Say Y if you need this feature; users who are only using their
system-native partitioning scheme can say N here.
-Sparc ESP SCSI support
-CONFIG_SCSI_SUNESP
- This is the driver for the Sun ESP SCSI host adapter. The ESP
- chipset is present in most SPARC-based computers.
-
-Sparc /dev/openprom compatibility driver
-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. 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.
-
# need an empty line after last entry, for sed script in Configure.
#
# LocalWords: TR Sony CDU caddyless cdu Mitsumi MCD cd mcd XA MultiSession CDA
# LocalWords: Matsushita Panasonic SBPCD Soundblaster Longshine sbpcd Aztech
# LocalWords: Okano Wearnes AZTCD CDD SE aztcd sonycd Goldstar GSCD Philips fs
-# LocalWords: LMS OPTCD Sanyo SJCD minix faqs msdos harddrive mtools
+# LocalWords: LMS OPTCD Sanyo SJCD minix faqs xiafs XIA msdos harddrive mtools
# LocalWords: std softlinks umssync NetworkFileSharing nfsd mountd CDs HPFS TI
# LocalWords: hpfs SYSV SCO intel iBCS Wyse WordPerfect tsx mit unixes sysv NR
# LocalWords: SMB WfW Cyclades async mux Logitech busmouse MouseSystem aka AST
# LocalWords: smmixer ptt circ soundmodem MKISS FDDI DEFEA DEFPA DEFXX redhat
# LocalWords: HyperNews khg mconv sed lina wuftpd MicroChannel netlink irc cum
# LocalWords: raudio realaudio PPROP NETBIOS GUI IBMMCA ELMC Racal Interlan fi
-# LocalWords: eth shapecfg src esp PCWD PREVSTAT
+# LocalWords: eth shapecfg src esp PCWD PREVSTAT bootparam sig bitwizard SBC
+# LocalWords: downloads AFSK TCM FP Karn KA FSK RUH LinkSys cron mouseman LLC
+# LocalWords: SyQuest SyQuest's CCITT MicroSolutions BPCD bpcd ESPSERIAL PROM
+# LocalWords: SUNESP openprom OPENPROMIO quango themall al TT MC MMU LC RMW AA
+# LocalWords: INSNS Ataris AutoConfig ZORRO OCS AMIFB Agnus Denise ECS CDTV GB
+# LocalWords: AGA Cybervision CYBER GSP TMS DMI Zorro ACSI ROMs SLM BioNet GVP
+# LocalWords: PAMsNet TekMagic Cyberstorm MkI CYBERSTORMII MkII BLZ onboard cx
+# LocalWords: VillageTronics ATARILANCE RieblCard PAMCard VME MFP sangoma LAPB
+# LocalWords: Rhotron BioData's Multiface AMIGAMOUSE COPCON Amiga's bitplanes
+# LocalWords: ATARIMOUSE MFPSER SCC's MegaSTE ESCC Atari's GVPIOEXT DMASOUND
+# LocalWords: fdutils cisco univercd rpcg htm iface lapb LAPBETHER tpqic qic
+# LocalWords: SYNTH xd en binfmt aout ipip terra ipx fileserver sd sr sg wic
+# LocalWords: ibmmca lapbether mkiss dlci sdla fmv eepro eexpress ni hp ne es
+# LocalWords: ibmtr isofs ROMFS romfs pcxx cyclades istallion psaux msbusmouse
+# LocalWords: atixlmouse sbin softdog pcwd USS Lite ACI miroSOUND PCM miroPCM
+# LocalWords: microcontroller miro Voxware downloading teles acsi slm gvp
+# LocalWords: atari ariadne amigamouse atarimouse builtin
projects / history.git / commitdiff