patch-2.1.128 linux/Documentation/Configure.help
Next file: linux/Documentation/mca.txt
Previous file: linux/CREDITS
Back to the patch index
Back to the overall index
- Lines: 5933
- Date:
Sun Nov 8 10:45:13 1998
- Orig file:
v2.1.127/linux/Documentation/Configure.help
- Orig date:
Sun Nov 8 14:02:40 1998
diff -u --recursive --new-file v2.1.127/linux/Documentation/Configure.help linux/Documentation/Configure.help
@@ -78,7 +78,7 @@
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).
+ 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
@@ -92,7 +92,7 @@
Linux can emulate a math coprocessor (used for floating point
operations) if you don't have one. 486DX and Pentium processors have
a math coprocessor built in, 486SX and 386 do not, unless you added
- a 487DX or 387, respectively. (The messages during boot time can
+ 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.
@@ -110,7 +110,7 @@
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
+ If you are not sure, say Y; apart from resulting in a 45 KB bigger
kernel, it won't hurt.
Normal PC floppy disk support
@@ -127,16 +127,22 @@
The module will be called floppy.o. If you want to compile it as a
module, say M here and read Documentation/modules.txt.
+Support for PowerMac floppy
+CONFIG_MAC_FLOPPY
+ If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
+ floppy controller, say Y here. Most commonly found in PowerMacs.
+
RAM disk support
CONFIG_BLK_DEV_RAM
Saying Y here will allow you to use a portion of your RAM memory as
a block device, so that you can make filesystems on it, read and
write to it and do all the other things that you can do with normal
- block devices (such as hard drives). It is usually used to load and
+ block devices (such as hard drives). It is usually used to load and
store a copy of a minimal root file system off of a floppy into RAM
- during the initial install of Linux. Note that the kernel command
- line option "ramdisk=XX" is now obsolete. For details, read
- Documentation/ramdisk.txt.
+ 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),
@@ -158,8 +164,8 @@
CONFIG_BLK_DEV_LOOP
Saying Y here will allow you to use a regular file as a block
device; you can then create a file system on that block device and
- mount it just as you would mount other block devices such as hard drive
- partitions, CDROM drives or floppy drives.
+ mount it just as you would mount other block devices such as hard
+ drive partitions, CDROM drives or floppy drives.
This is useful if you want to check an ISO 9660 file system before
burning the CD, or if you want to use floppy images without first
@@ -171,8 +177,9 @@
bits of, say, a sound file). This is also safe if the file resides
on a remote file server. If you want to do this, you will first have
to acquire and install a kernel patch from
- ftp://ftp.replay.com/pub/crypto/linux/all, and then you need to say
- Y to this option.
+ ftp://ftp.replay.com/pub/crypto/linux/all or
+ ftp://verden.pvv.org/pub/linux/kerneli/v2.1/, and then you need to
+ say Y to this option.
Note that alternative ways to use encrypted filesystems are provided
by the cfs package, which can be gotten via FTP (user: anonymous)
@@ -200,18 +207,22 @@
Network Block Device support
CONFIG_BLK_DEV_NBD
Saying Y here will allow your computer to be a client for network
- block devices -- it will be able to use block devices exported by
+ block devices, i.e. it will be able to use block devices exported by
servers (mount filesystems on them etc.). Communication between
client and server works over TCP/IP networking, but to the client
program this is hidden: it looks like a regular local file access to
- a special file such as /dev/nd0. It also allows you to run a
- block-device in userland (making server and client physically the
- same computer, communicating using the loopback network device).
+ a block device special file such as /dev/nd0.
+
+ Network block devices also allows you to run a block-device in
+ userland (making server and client physically the same computer,
+ communicating using the loopback network device).
+
Read Documentation/nbd.txt for more information, especially about
- where to find the server code.
+ where to find the server code, which runs in user space and does not
+ need special kernel support.
- Note that this has nothing to do with the network file system NFS;
- you can say N here even if you intend to use NFS.
+ Note that this has nothing to do with the network file systems NFS
+ or Coda; you can say N here even if you intend to use NFS or Coda.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
@@ -225,22 +236,25 @@
If you say Y here, you will use the full-featured IDE driver to
control up to four IDE interfaces, each being able to serve a
"master" and a "slave" device, for a total of up to eight IDE
- disk/cdrom/tape/floppy drives. People with SCSI-only systems
- should say 'N' here.
+ disk/cdrom/tape/floppy drives. People with SCSI-only systems
+ can say N here.
- Useful information about large (>540MB) IDE disks, sound card IDE
- ports, module support, and other topics, is contained in
- Documentation/ide.txt. For detailed information about hard drives,
- consult the Disk-HOWTO, available via FTP (user: anonymous) from
- ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. To fine-tune IDE
- drive/interface parameters for improved performance, look for the
- hdparm package at
- sunsite.unc.edu:/pub/Linux/kernel/patches/diskdrives/
+ Useful information about large (>540 MB) IDE disks, multiple
+ interfaces, what to do if IDE devices are not automatically
+ detected, sound card IDE ports, module support, and other topics, is
+ contained in Documentation/ide.txt. For detailed information about
+ hard drives, consult the Disk-HOWTO and the Multi-Disk-HOWTO,
+ available via FTP (user: anonymous) from
+ ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+
+ To fine-tune IDE drive/interface parameters for improved
+ performance, look for the hdparm package at
+ ftp://sunsite.unc.edu:/pub/Linux/kernel/patches/diskdrives/
If you have one or more IDE drives, say Y here. If your system has
no IDE drives, or if memory requirements are really tight, you could
say N here, and select the "Old hard disk driver" instead to save
- about 13kB of memory in the kernel.
+ about 13 KB of memory in the kernel.
Old hard disk (MFM/RLL/IDE) driver
CONFIG_BLK_DEV_HD_ONLY
@@ -252,12 +266,14 @@
since it lacks the enhanced functionality of the new one. This makes
it a good choice for systems with very tight memory restrictions, or
for systems with only older MFM/RLL/ESDI drives. Choosing the old
- driver can save 13kB or so of kernel memory. If you are unsure, then
- just choose the Enhanced IDE/MFM/RLL driver instead of this one. For
- more detailed information, read the Disk-HOWTO, available via FTP
- (user: anonymous) from ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+ driver can save 13 KB or so of kernel memory.
+
+ If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
+ instead of this one. For more detailed information, read the
+ Disk-HOWTO, available via FTP (user: anonymous) from
+ ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
- People with SCSI-only systems can say 'N' here.
+ People with SCSI-only systems can say N here.
Use old disk-only driver on primary interface
CONFIG_BLK_DEV_HD_IDE
@@ -270,16 +286,20 @@
interface. Choosing this option may be useful for older systems
which have MFM/RLL/ESDI controller+drives at the primary port
address (0x1f0), along with IDE drives at the secondary/3rd/4th port
- addresses. Normally, just say N here; you will then use the new
- driver for all 4 interfaces.
+ addresses.
+
+ Normally, just say N here; you will then use the new driver for all
+ 4 interfaces.
- People with SCSI-only systems can say 'N' here.
+ People with SCSI-only systems don't need this and can say N here as
+ well.
Include IDE/ATA-2 DISK support
CONFIG_BLK_DEV_IDEDISK
- This will include enhanced support for MFM/RLL/IDE hard disks. If you
- have a MFM/RLL/IDE disk, and there is no special reason to use the
- old hard disk driver instead, say Y. If all your disks are SCSI, say 'N'.
+ This will include enhanced support for MFM/RLL/IDE hard disks. If
+ you have a MFM/RLL/IDE disk, and there is no special reason to use
+ the old hard disk driver instead, say Y. If you have an SCSI-only
+ system, you can say N here.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
@@ -318,7 +338,8 @@
CONFIG_BLK_DEV_IDETAPE
If you have an IDE tape drive using the ATAPI protocol, say Y.
ATAPI is a newer protocol used by IDE tape and CDROM drives, similar
- to the SCSI protocol (but say 'N' if your tape is a SCSI device).
+ to the SCSI protocol. If you have an SCSI tape drive however, you
+ can say N here.
If you say Y here, the tape drive will be identified at boot time
along with other IDE devices, as "hdb" or "hdc", or something
@@ -334,12 +355,12 @@
Include IDE/ATAPI FLOPPY support
CONFIG_BLK_DEV_IDEFLOPPY
- If you have an IDE floppy drive which uses the ATAPI protocol, say
- Y. ATAPI is a newer protocol used by IDE CDROM/tape/floppy drives,
- similar to the SCSI protocol. IDE floppy drives include the LS-120
- and the ATAPI ZIP (ATAPI PD-CD/CDR drives are not supported by this
- driver; support for PD-CD/CDR drives is available if you say Y to
- "SCSI emulation support", below).
+ If you have an IDE floppy drive which uses the ATAPI protocol,
+ answer Y. ATAPI is a newer protocol used by IDE CDROM/tape/floppy
+ drives, similar to the SCSI protocol. IDE floppy drives include the
+ LS-120 and the ATAPI ZIP (ATAPI PD-CD/CDR drives are not supported
+ by this driver; support for PD-CD/CDR drives is available if you
+ answer Y to "SCSI emulation support", below).
If you say Y here, the FLOPPY drive will be identified along with
other IDE devices, as "hdb" or "hdc", or something similar (check
@@ -368,18 +389,18 @@
If both this SCSI emulation and native ATAPI support are compiled
into the kernel, the native support will be used.
- People with SCSI-only systems should say 'N' here. If unsure, say N.
+ People with SCSI-only systems can say N here. If unsure, say N.
CMD640 chipset bugfix/support
CONFIG_BLK_DEV_CMD640
The CMD-Technologies CMD640 IDE chip is used on many common 486 and
Pentium motherboards, usually in combination with a "Neptune" or
- "SiS" chipset. Unfortunately, it has a number of rather nasty
+ "SiS" chipset. Unfortunately, it has a number of rather nasty
design flaws that can cause severe data corruption under many common
- conditions. Say Y here to include code which tries to automatically
- detect and correct the problems under Linux. This option also
+ conditions. Say Y here to include code which tries to automatically
+ detect and correct the problems under Linux. This option also
enables access to the secondary IDE ports in some CMD640 based
- systems.
+ systems.
This driver will work automatically in PCI based systems (most new
systems have PCI slots). But if your system uses VESA local bus
@@ -394,36 +415,35 @@
the "CSA-6400E PCI to IDE controller" that some people have. For
details, read Documentation/ide.txt.
- People with SCSI-only systems should say 'N' here. If unsure, say Y.
+ People with SCSI-only systems should say N here. If unsure, say Y.
CMD640 enhanced support
CONFIG_BLK_DEV_CMD640_ENHANCED
This option includes support for setting/autotuning PIO modes and
- prefetch on CMD640 IDE interfaces. For details, read
+ prefetch on CMD640 IDE interfaces. For details, read
Documentation/ide.txt. If you have a CMD640 IDE interface and your
- BIOS does not already do this for you, then say Y here. Otherwise
+ BIOS does not already do this for you, then say Y here. Otherwise
say N.
RZ1000 chipset bugfix/support
CONFIG_BLK_DEV_RZ1000
- The PC-Technologies RZ1000 chip is used on many common 486 and
+ The PC-Technologies RZ1000 IDE chip is used on many common 486 and
Pentium motherboards, usually along with the "Neptune" chipset.
Unfortunately, it has a rather nasty design flaw that can cause
- severe data corruption under many conditions. Say Y here to include
+ severe data corruption under many conditions. Say Y here to include
code which automatically detects and corrects the problem under
- Linux. This may slow disk throughput by a few percent, but at least
+ Linux. This may slow disk throughput by a few percent, but at least
things will operate 100% reliably.
- People with SCSI-only systems can say 'N' here. If unsure, say Y.
+ People with SCSI-only systems should say N here. If unsure, say Y.
Generic PCI IDE chipset support
CONFIG_BLK_DEV_IDEPCI
Enable this for PCI systems which use IDE drive(s).
This option helps the IDE driver to automatically detect and
configure all PCI-based IDE interfaces in your system.
-
- People with SCSI-only systems should say 'N' here. It is safe to
- say 'Y' to this question.
+
+ People with SCSI-only systems should say N here; if unsure say Y.
Generic PCI bus-master DMA support
CONFIG_BLK_DEV_IDEDMA
@@ -442,26 +462,33 @@
It is safe to say Y to this question.
+Winbond SL82c105 support
+CONFIG_BLK_DEV_SL82C105
+ If you have a Winbond SL82c105 IDE controller, say Y here to enable
+ special configuration for this chip. This is common on various CHRP
+ motherboards, but could be used elsewhere. If in doubt, say Y.
+
Boot off-board chipsets first support
CONFIG_BLK_DEV_OFFBOARD
Normally, IDE controllers built into the motherboard (on-board
- controllers) are assigned to ide0 and ide1 while those on add-in
- PCI cards (off-board controllers) are relegated to ide2 and ide3.
- Saying Y to here will reverse the situation, with off-board
- controllers on ide0/1 and on-board controllers on ide2/3. This
- can improve the usability of some boot managers such as LILO
- when booting from a drive on an off-board controller.
- Note that this will rearrange the order of the hd* devices and
- may require modification of fstab and other files.
+ controllers) are assigned to ide0 and ide1 while those on add-in PCI
+ cards (off-board controllers) are relegated to ide2 and ide3.
+ Answering Y here will reverse the situation, with off-board
+ controllers on ide0/1 and on-board controllers on ide2/3. This can
+ improve the usability of some boot managers such as LILO when
+ booting from a drive on an off-board controller.
+
+ Note that, if you say Y here, the order of the hd* devices will be
+ rearranged which may require modification of fstab and other files.
If in doubt, say N.
Use DMA by default when available
CONFIG_IDEDMA_AUTO
Prior to kernel version 2.1.112, Linux used to automatically use
- DMA for IDE drives and chipsets which support it. Due to concerns
+ DMA for IDE drives and chipsets which support it. Due to concerns
about a couple of cases where buggy hardware may have caused damage,
- the default is now to NOT use DMA automatically. To revert to the
+ the default is now to NOT use DMA automatically. To revert to the
previous behaviour, say Y to this question.
If you suspect your hardware is at all flakey, say N here.
@@ -472,46 +499,48 @@
Other IDE chipset support
CONFIG_IDE_CHIPSETS
Say Y here if you want to include enhanced support for various IDE
- interface chipsets used on motherboards and add-on cards. This
- enhanced support may be necessary for Linux to be able to access the
- 3rd/4th drives in some systems. It may also enable setting of
- higher speed I/O rates to improve system performance with these
- chipsets. Most of these also require special kernel boot parameters
- to actually turn on the support at runtime.
-
- People with SCSI-only systems should say 'N' here.
+ interface chipsets used on motherboards and add-on cards. You can
+ then pick your particular IDE chip from among the following options.
+ This enhanced support may be necessary for Linux to be able to
+ access the 3rd/4th drives in some systems. It may also enable
+ setting of higher speed I/O rates to improve system performance with
+ these chipsets. Most of these also require special kernel boot
+ parameters to actually turn on the support at runtime; you can find
+ a list of these in the file Documentation/ide.txt.
+
+ People with SCSI-only systems can say N here.
Generic 4 drives/port support
CONFIG_BLK_DEV_4DRIVES
- Certain older chipsets, including the Tekram 690CD, use a
- single set of I/O ports at 0x1f0 to control up to four drives,
- instead of the customary two drives per port. Support for this
- can be enabled at runtime using the "ide0=four" kernel boot
- parameter if you say Y here.
+ Certain older chipsets, including the Tekram 690CD, use a single set
+ of I/O ports at 0x1f0 to control up to four drives, instead of the
+ customary two drives per port. Support for this can be enabled at
+ runtime using the "ide0=four" kernel boot parameter if you say Y
+ here.
DTC-2278 support
CONFIG_BLK_DEV_DTC2278
This driver is enabled at runtime using the "ide0=dtc2278" kernel
- boot parameter. It enables support for the secondary IDE interface
+ boot parameter. It enables support for the secondary IDE interface
of the DTC-2278 card, and permits faster I/O speeds to be set as
- well. See the Documentation/ide.txt and dtc2278.c files for more
+ well. See the Documentation/ide.txt and dtc2278.c files for more
info.
Holtek HT6560B support
CONFIG_BLK_DEV_HT6560B
This driver is enabled at runtime using the "ide0=ht6560b" kernel
- boot parameter. It enables support for the secondary IDE interface
+ boot parameter. It enables support for the secondary IDE interface
of the Holtek card, and permits faster I/O speeds to be set as well.
See the Documentation/ide.txt and ht6560b.c files for more info.
PROMISE DC4030 support (EXPERIMENTAL)
CONFIG_BLK_DEV_PDC4030
This driver provides support for the secondary IDE interface and
- cache of Promise IDE chipsets, e.g. DC4030 and DC5030. This driver
+ cache of Promise IDE chipsets, e.g. DC4030 and DC5030. This driver
is known to incur timeouts/retries during heavy I/O to drives
- attached to the secondary interface. CDROM and TAPE devices are not
- supported yet. This driver is enabled at runtime using the
- "ide0=dc4030" kernel boot parameter. See the Documentation/ide.txt
+ attached to the secondary interface. CDROM and TAPE devices are not
+ supported yet. This driver is enabled at runtime using the
+ "ide0=dc4030" kernel boot parameter. See the Documentation/ide.txt
and drivers/block/pdc4030.c files for more info.
PS/2 ESDI hard disk support
@@ -522,7 +551,7 @@
Tekram TRM290 chipset support (EXPERIMENTAL)
CONFIG_BLK_DEV_TRM290
This driver adds support for bus master DMA transfers
- using the Tekram TRM290 PCI IDE chip. Volunteers are
+ using the Tekram TRM290 PCI IDE chip. Volunteers are
needed for further tweaking and development.
Please read the comments at the top of drivers/block/trm290.c.
@@ -541,41 +570,47 @@
VIA82C586 chipset support (EXPERIMENTAL)
CONFIG_BLK_DEV_VIA82C586
This adds initial timing settings for VIA (U)DMA onboard ide
- controllers that are ATA3 compliant. May work with ATA4 systems,
- but not tested to date.
+ controllers that are ATA3 compliant. May work with ATA4 systems, but
+ not tested to date.
+
+ If you say Y here, you also need to say Y to "Use DMA by default
+ when available", above.
- This requires CONFIG_IDEDMA_AUTO to be enabled.
Please read the comments at the top of drivers/block/via82C586.c
If unsure, say N.
+CMD646 chipset support (EXPERIMENTAL)
+CONFIG_BLK_DEV_CMD646
+ Say Y here if you have an IDE controller like this.
+
HPT343 chipset support (EXPERIMENTAL)
CONFIG_BLK_DEV_HPT343
- This driver adds up to 4 more eide devices sharing a single interrupt.
- The HPT343 chipset in it's current form is a non-bootable PCI
- UDMA controller. This driver requires dynamic tuning of the
- chipset during the ide-probe at boot. It is reported to support
- DVD II drives, by the manufacturer.
+ This driver adds up to 4 more EIDE devices sharing a single
+ interrupt. The HPT343 chipset in its current form is a non-bootable
+ PCI UDMA controller. This driver requires dynamic tuning of the
+ chipset during the ide-probe at boot. It is reported to support DVD
+ II drives, by the manufacturer.
Please read the comments at the top of drivers/block/hpt343.c
QDI QD6580 support
CONFIG_BLK_DEV_QD6580
This driver is enabled at runtime using the "ide0=qd6580" kernel
- boot parameter. It permits faster I/O speeds to be set. See the
+ boot parameter. It permits faster I/O speeds to be set. See the
files Documentation/ide.txt and qd6580.c for more info.
UMC 8672 support
CONFIG_BLK_DEV_UMC8672
This driver is enabled at runtime using the "ide0=umc8672" kernel
- boot parameter. It enables support for the secondary IDE interface
+ boot parameter. It enables support for the secondary IDE interface
of the UMC-8672, and permits faster I/O speeds to be set as well.
See the files Documentation/ide.txt and umc8672.c for more info.
ALI M14xx support
CONFIG_BLK_DEV_ALI14XX
This driver is enabled at runtime using the "ide0=ali14xx" kernel
- boot parameter. It enables support for the secondary IDE interface
+ boot parameter. It enables support for the secondary IDE interface
of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
I/O speeds to be set as well. See the files Documentation/ide.txt
and ali14xx.c for more info.
@@ -620,12 +655,12 @@
Parallel port IDE disks
CONFIG_PARIDE_PD
This option enables the high-level driver for IDE-type disk devices
- connected through a parallel port. If you chose to build PARIDE
+ connected through a parallel port. If you chose to build PARIDE
support into your kernel, you may answer Y here to build in the
parallel port IDE driver, otherwise you should answer M to build
- it as a loadable module. The module will be called pd.o. You
+ it as a loadable module. The module will be called pd.o. You
must also have at least one parallel port protocol driver in your
- system. Among the devices supported by this driver are the SyQuest
+ system. Among the devices supported by this driver are the SyQuest
EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack
hard drives from MicroSolutions.
@@ -639,31 +674,31 @@
must also have at least one parallel port protocol driver in your
system. Among the devices supported by this driver are the
MicroSolutions backpack CD-ROM drives and the Freecom Power CD. If
- you have such a CD-ROM drive, you should also say Y or M to "ISO 9660
- CDROM filesystem support" below, because that's the filesystem used
- on CDROMs.
+ you have such a CD-ROM drive, you should also say Y or M to "ISO
+ 9660 CDROM filesystem support" below, because that's the filesystem
+ used on CDROMs.
Parallel port ATAPI disks
CONFIG_PARIDE_PF
This option enables the high-level driver for ATAPI disk devices
- connected through a parallel port. If you chose to build PARIDE
+ connected through a parallel port. If you chose to build PARIDE
support into your kernel, you may answer Y here to build in the
parallel port ATAPI disk driver, otherwise you should answer M
- to build it as a loadable module. The module will be called pf.o.
+ to build it as a loadable module. The module will be called pf.o.
You must also have at least one parallel port protocol driver in
- your system. Among the devices supported by this driver are the
+ your system. Among the devices supported by this driver are the
MicroSolutions backpack PD/CD drive and the Imation Superdisk
LS-120 drive.
Parallel port ATAPI tapes
CONFIG_PARIDE_PT
This option enables the high-level driver for ATAPI tape devices
- connected through a parallel port. If you chose to build PARIDE
+ connected through a parallel port. If you chose to build PARIDE
support into your kernel, you may answer Y here to build in the
parallel port ATAPI disk driver, otherwise you should answer M
- to build it as a loadable module. The module will be called pt.o.
+ to build it as a loadable module. The module will be called pt.o.
You must also have at least one parallel port protocol driver in
- your system. Among the devices supported by this driver is the
+ your system. Among the devices supported by this driver is the
parallel port version of the HP 5GB drive.
Parallel port generic ATAPI devices
@@ -671,54 +706,59 @@
This option enables a special high-level driver for generic ATAPI
devices connected through a parallel port. The driver allows user
programs, such as cdrecord, to send ATAPI commands directly to a
- device. If you chose to build PARIDE support into your kernel, you
- may answer Y here to build in the parallel port generic ATAPI driver,
- otherwise you should answer M to build it as a loadable module.
- The module will be called pg.o. You must also have at least one
- parallel port protocol driver in your system. This driver
- implements an API loosely related to the generic SCSI driver.
- See /usr/include/linux/pg.h for details.
+ device.
+
+ If you chose to build PARIDE support into your kernel, you may
+ answer Y here to build in the parallel port generic ATAPI driver,
+ otherwise you should answer M to build it as a loadable module. The
+ module will be called pg.o.
+
+ You must also have at least one parallel port protocol driver in
+ your system.
+
+ This driver implements an API loosely related to the generic SCSI
+ driver. See /usr/include/linux/pg.h for details.
You can obtain the most recent version of cdrecord from
- ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/ . Versions 1.6.1a3 and
- later fully support the pg driver.
+ ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/ . Versions 1.6.1a3 and
+ later fully support this driver.
ATEN EH-100 protocol
CONFIG_PARIDE_ATEN
This option enables support for the ATEN EH-100 parallel port IDE
- protocol. This protocol is used in some inexpensive low performance
- parallel port kits made in Hong Kong. If you chose to build PARIDE
- support into your kernel, you may answer Y here to build in the
- protocol driver, otherwise you should answer M to build it as a
- loadable module. The module will be called aten.o. You must also
- have a high-level driver for the type of device that you want to
+ protocol. This protocol is used in some inexpensive low performance
+ parallel port kits made in Hong Kong. If you chose to build PARIDE
+ support into your kernel, you may answer Y here to build in the
+ protocol driver, otherwise you should answer M to build it as a
+ loadable module. The module will be called aten.o. You must also
+ have a high-level driver for the type of device that you want to
support.
MicroSolutions backpack protocol
CONFIG_PARIDE_BPCK
- This option enables support for the MicroSolutions backpack
- parallel port IDE protocol. If you chose to build PARIDE support
- into your kernel, you may answer Y here to build in the protocol
- driver, otherwise you should answer M to build it as a loadable
- module. The module will be called bpck.o. You must also have
- a high-level driver for the type of device that you want to support.
+ This option enables support for the MicroSolutions backpack parallel
+ port IDE protocol. If you chose to build PARIDE support into your
+ kernel, you may answer Y here to build in the protocol driver,
+ otherwise you should answer M to build it as a loadable module. The
+ module will be called bpck.o. You must also have a high-level driver
+ for the type of device that you want to support.
DataStor Commuter protocol
CONFIG_PARIDE_COMM
This option enables support for the Commuter parallel port IDE
- protocol from DataStor. If you chose to build PARIDE support
+ protocol from DataStor. If you chose to build PARIDE support
into your kernel, you may answer Y here to build in the protocol
driver, otherwise you should answer M to build it as a loadable
- module. The module will be called comm.o. You must also have
+ module. The module will be called comm.o. You must also have
a high-level driver for the type of device that you want to support.
DataStor EP-2000 protocol
CONFIG_PARIDE_DSTR
This option enables support for the EP-2000 parallel port IDE
- protocol from DataStor. If you chose to build PARIDE support
+ protocol from DataStor. If you chose to build PARIDE support
into your kernel, you may answer Y here to build in the protocol
driver, otherwise you should answer M to build it as a loadable
- module. The module will be called dstr.o. You must also have
+ module. The module will be called dstr.o. You must also have
a high-level driver for the type of device that you want to support.
Shuttle EPAT/EPEZ protocol
@@ -767,11 +807,11 @@
FreeCom power protocol
CONFIG_PARIDE_FRPW
- This option enables support for the Freecom power parallel port IDE
- protocol. If you chose to build PARIDE support into your kernel, you
- may answer Y here to build in the protocol driver, otherwise you
- should answer M to build it as a loadable module. The module will be
- called frpw.o. You must also have a high-level driver for the type
+ This option enables support for the Freecom power parallel port IDE
+ protocol. If you chose to build PARIDE support into your kernel, you
+ may answer Y here to build in the protocol driver, otherwise you
+ should answer M to build it as a loadable module. The module will be
+ called frpw.o. You must also have a high-level driver for the type
of device that you want to support.
KingByte KBIC-951A/971A protocols
@@ -788,11 +828,11 @@
KT PHd protocol
CONFIG_PARIDE_KTTI
This option enables support for the "PHd" parallel port IDE protocol
- from KT Technology. This is a simple (low speed) adapter that is
- used in some 2.5" portable hard drives. If you chose to build PARIDE
- support into your kernel, you may answer Y here to build in the
- protocol driver, otherwise you should answer M to build it as a
- loadable module. The module will be called ktti.o. You must also
+ from KT Technology. This is a simple (low speed) adapter that is
+ used in some 2.5" portable hard drives. If you chose to build PARIDE
+ support into your kernel, you may answer Y here to build in the
+ protocol driver, otherwise you should answer M to build it as a
+ loadable module. The module will be called ktti.o. You must also
have a high-level driver for the type of device that you want to
support.
@@ -800,43 +840,52 @@
CONFIG_PARIDE_ON20
This option enables support for the (obsolete) 90c20 parallel port
IDE protocol from OnSpec (often marketed under the ValuStore brand
- name). If you chose to build PARIDE support into your kernel, you
+ name). If you chose to build PARIDE support into your kernel, you
may answer Y here to build in the protocol driver, otherwise you
- should answer M to build it as a loadable module. The module will
- be called on20.o. You must also have a high-level driver for the
+ should answer M to build it as a loadable module. The module will
+ be called on20.o. You must also have a high-level driver for the
type of device that you want to support.
OnSpec 90c26 protocol
CONFIG_PARIDE_ON26
- This option enables support for the 90c26 parallel port IDE protocol
+ This option enables support for the 90c26 parallel port IDE protocol
from OnSpec Electronics (often marketed under the ValuStore brand
- name). If you chose to build PARIDE support into your kernel, you
- may answer Y here to build in the protocol driver, otherwise you
- should answer M to build it as a loadable module. The module will
- be called on26.o. You must also have a high-level driver for the
- type of device that you want to support.
+ name). If you chose to build PARIDE support into your kernel, you
+ may answer Y here to build in the protocol driver, otherwise you
+ should answer M to build it as a loadable module. The module will be
+ called on26.o. You must also have a high-level driver for the type
+ of device that you want to support.
Multiple devices driver support
CONFIG_BLK_DEV_MD
This driver lets you combine several hard disk partitions into one
- logical block device. This can be used to combine several redundant
+ logical block device. This can be used to simply append one
+ partition to another one or to combine several redundant
hard disks to a RAID1/4/5 device so as to provide protection against
- hard disk failures. More information and the necessary tools are
- available over FTP (user: anonymous) from
- ftp://sweet-smoke.ufr-info-p7.ibp.fr/pub/Linux in the md package and
- the md-FAQ. Please read drivers/block/README.md and the relevant
- section of the Disk-HOWTO, available via FTP (user: anonymous) from
- ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. If unsure, say N.
+ hard disk failures. This is called "Software RAID" since the
+ combining of the partitions is done by the kernel. "Hardware RAID"
+ means that the combining is done by a dedicated controller; if you
+ have such a controller, you do not need to say Y here.
+
+ More information about Software RAID on Linux is contained in the
+ Software-RAID mini-HOWTO, available via FTP (user: anonymous) from
+ ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/mini. There you will also
+ learn where to get the supporting user space utilities raidtools.
+
+ If unsure, say N.
Linear (append) mode
CONFIG_MD_LINEAR
If you say Y here, then your multiple devices driver will be able to
use the so-called linear mode, i.e. it will combine the hard disk
- partitions by simply appending one to the other. If you want to
- compile this as a module ( = code which can be inserted in and
- removed from the running kernel whenever you want), say M here and
- read Documentation/modules.txt. The module will be called
- linear.o. If unsure, say Y.
+ partitions by simply appending one to the other.
+
+ If you want to compile this as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want),
+ say M here and read Documentation/modules.txt. The module will be
+ called linear.o.
+
+ If unsure, say Y.
RAID-0 (striping) mode
CONFIG_MD_STRIPED
@@ -844,31 +893,19 @@
use the so-called raid0 mode, i.e. it will combine the hard disk
partitions into one logical device in such a fashion as to fill them
up evenly, one chunk here and one chunk there. This will increase
- the throughput rate if the partitions reside on distinct disks. If
- you want to compile this as a module ( = code which can be inserted
- in and removed from the running kernel whenever you want), say M
- here and read Documentation/modules.txt. The module will be called
- raid0.o. If unsure, say Y.
+ the throughput rate if the partitions reside on distinct disks.
-Are you using a crosscompiler
-CONFIG_CROSSCOMPILE
- Set this if you are using another architecture to compile the
- kernel for your MIPS machine.
+ Information about Software RAID on Linux is contained in the
+ Software-RAID mini-HOWTO, available via FTP (user: anonymous) from
+ ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/mini. There you will also
+ learn where to get the supporting user space utilities raidtools.
-Support for Acer PICA 1 chipset
-CONFIG_ACER_PICA_61
- This is a machine with a R4400 133/150 MHz CPU. To compile a Linux
- kernel that runs on these, say Y here. For details about Linux on
- the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
- http://lena.fnet.fr/ (To browse the WWW, you need to have access to
- a machine on the Internet that has a program like lynx or
- netscape).
+ If you want to compile this as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want),
+ say M here and read Documentation/modules.txt. The module will be
+ called raid0.o.
-Support for Algorithmics P4032
-CONFIG_ALGOR_P4032
- This is an evaluation board of the British company Algorithmics. The
- board uses the R4300 and a R5230 CPUs. For more information about
- this board see www.algor.co.uk.
+ If unsure, say Y.
RAID-1 (mirroring) mode
CONFIG_MD_MIRRORING
@@ -878,23 +915,20 @@
an error free MD (multiple device) to the higher levels of the
kernel. In a set with N drives, the available space is the capacity
of a single drive, and the set protects against a failure of (N - 1)
- drives.
+ drives.
- Raidtools, a set of user-space tools which create and maintain
- RAID1/4/5 sets, is available at:
- ftp://ftp.kernel.org/pub/linux/daemons/raid
- http://luthien.nuclecu.unam.mx/~miguel/raid
+ Information about Software RAID on Linux is contained in the
+ Software-RAID mini-HOWTO, available via FTP (user: anonymous) from
+ ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/mini. There you will also
+ learn where to get the supporting user space utilities raidtools.
If you want to use such a RAID-1 set, say Y. This code is also
available as a module called raid1.o ( = code which can be inserted
in and removed from the running kernel whenever you want). If you
want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say Y.
+ Documentation/modules.txt.
-Boot support (linear, striped)
-CONFIG_MD_BOOT
- To boot with an initial linear or striped md device you have to say
- Y here. For lilo and loadlin options see Documentation/md.txt.
+ If unsure, say Y.
RAID-4/RAID-5 mode
CONFIG_MD_RAID5
@@ -906,16 +940,47 @@
while a RAID-5 set distributes the parity across the drives in one
of the available parity distribution methods.
- Raidtools, a set of user-space tools which create and maintain
- RAID1/4/5 sets, is available at:
- ftp://ftp.kernel.org/pub/linux/daemons/raid
- http://luthien.nuclecu.unam.mx/~miguel/raid
+ Information about Software RAID on Linux is contained in the
+ Software-RAID mini-HOWTO, available via FTP (user: anonymous) from
+ ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/mini. There you will also
+ learn where to get the supporting user space utilities raidtools.
- If you want to use such a RAID-5 set, say Y. This code is also
- available as a module called raid5.o ( = code which can be inserted
- in and removed from the running kernel whenever you want). If you
- want to compile it as a module, say M here and read
- Documentation/modules.txt. If unsure, say Y.
+ If you want to use such a RAID-4/RAID-5 set, say Y. This code is
+ also available as a module called raid5.o ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ If you want to compile it as a module, say M here and read
+ Documentation/modules.txt.
+
+ If unsure, say Y.
+
+Boot support (linear, striped)
+CONFIG_MD_BOOT
+ To boot with an initial linear or striped md device you have to
+ answer Y here. For lilo and loadlin options see the file
+ Documentation/md.txt.
+
+Support for Deskstation RPC44
+CONFIG_DESKSTATION_RPC44
+ This is a machine with a R4400 100 MHz CPU. To compile a Linux
+ kernel that runs on these, say Y here. For details about Linux
+ on the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
+ http://lena.fnet.fr/ (To browse the WWW, you need to
+ have access to a machine on the Internet that has a program like
+ lynx or netscape).
+
+Support for Acer PICA 1 chipset
+CONFIG_ACER_PICA_61
+ This is a machine with a R4400 133/150 MHz CPU. To compile a Linux
+ kernel that runs on these, say Y here. For details about Linux on
+ the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
+ http://lena.fnet.fr/ (To browse the WWW, you need to have access to
+ a machine on the Internet that has a program like lynx or netscape).
+
+Support for Algorithmics P4032
+CONFIG_ALGOR_P4032
+ This is an evaluation board of the British company Algorithmics. The
+ board uses the R4300 and a R5230 CPUs. For more information about
+ this board see http://www.algor.co.uk.
Support for Mips Magnum 4000
CONFIG_MIPS_MAGNUM_4000
@@ -935,27 +1000,27 @@
CPU type
CONFIG_CPU_R3000
- Give the type of your machine's MIPS CPU. For this question,
- it suffices to give a unique prefix of the option you want to
- choose. In case of doubt select the R3000 CPU. This kernel will
- run on other MIPS machines but with slightly reduced performance.
+ Give the type of your machine's MIPS CPU. For this question, it
+ suffices to give a unique prefix of the option you want to choose.
+ In case of doubt select the R3000 CPU. The kernel will then run on
+ other MIPS machines but with slightly reduced performance.
Compile the kernel into the ECOFF object format
CONFIG_ECOFF_KERNEL
- Some machines require a kernel in the ECOFF format. You will have to
- Choose this option for example if you want to a Mips Magnum 3000 or a
- DECstation over network.
+ Some machines require a kernel in the ECOFF format. You will have to
+ say Y here for example if you want to use a Mips Magnum 3000 or a
+ DECstation.
Generate little endian code
CONFIG_CPU_LITTLE_ENDIAN
Some MIPS machines can be configured for either little or big endian
- byte order. Both modes require different kernels. Say yes if your
- machine is little endian, no if it's a big endian machine.
+ byte order. These modes require different kernels. Say Y if your
+ machine is little endian, N if it's a big endian machine.
Kernel support for IRIX binaries
CONFIG_BINFMT_IRIX
- This option enables the kernel support for IRIX binaries. Running
- IRIX binaries additionally requires IRIX libraries.
+ If you say Y here, the kernel will support running of IRIX binaries.
+ You will need IRIX libraries for this to work.
Networking support
CONFIG_NET
@@ -1036,10 +1101,11 @@
SYN flood protection
CONFIG_SYN_COOKIES
- Normal TCP/IP networking is open to an attack known as "SYN flooding".
- This denial-of-service attack prevents legitimate remote users from
- being able to connect to your computer and requires very little work
- from the attacker, who can operate from anywhere on the Internet.
+ Normal TCP/IP networking is open to an attack known as "SYN
+ flooding". This denial-of-service attack prevents legitimate remote
+ users from being able to connect to your computer during an ongoing
+ attack and requires very little work from the attacker, who can
+ operate from anywhere on the Internet.
SYN cookies provide protection against this type of attack. If you
say Y here, the TCP/IP stack will use a cryptographic challenge
@@ -1055,6 +1121,10 @@
an aid in tracing the packets to their actual source and should not
be taken as absolute truth.
+ SYN cookies may prevent correct error reporting on clients when the
+ server is really overloaded. If this happens frequently better turn
+ them off.
+
If you say Y here, note that SYN cookies aren't enabled by default;
you can enable them by saying Y to "/proc filesystem support" and
"Sysctl support" below and executing the command
@@ -1081,7 +1151,7 @@
question, it suffices to give a unique prefix of the option you want
to choose. The choices:
** Avanti: This is for Mustang (AS200), M3 (AS250), Avanti (AS400)
- AlphaStations. These usually come with a TGA graphics adapter,
+ AlphaStations. These usually come with a TGA graphics adapter,
so you'll want to say Y to "TGA Console support", below, if you
have one of these.
** Alpha-XL: A.k.a. "Windows NT Dream Machine" :-) These usually
@@ -1134,20 +1204,24 @@
This includes intelligent serial boards such as Cyclades,
Digiboards, etc. These are usually used for systems that need many
serial ports because they serve many terminals or dial-in
- connections. Note that the answer to this question won't directly
- affect the kernel: saying N will just cause this configure script to
- skip all the questions about non-standard serial boards. Most people
- can say N here.
+ connections.
+
+ Note that the answer to this question won't directly affect the
+ kernel: saying N will just cause this configure script to skip all
+ the questions about non-standard serial boards.
+
+ Most people can say N here.
Extended dumb serial driver options
CONFIG_SERIAL_EXTENDED
If you wish to use any non-standard features of the standard "dumb"
- driver, say Y here. This includes HUB6 support, shared serial
+ driver, say Y here. This includes HUB6 support, shared serial
interrupts, special multiport support, support for more than the
- four COM 1/2/3/4 boards, etc. Note that the answer to this question
- won't directly affect the kernel: saying N will just cause this
- configure script to skip all the questions about serial driver
- options. If unsure, say N.
+ four COM 1/2/3/4 boards, etc.
+
+ Note that the answer to this question won't directly affect the
+ kernel: saying N will just cause this configure script to skip all
+ the questions about serial driver options. If unsure, say N.
Support more than 4 serial ports
CONFIG_SERIAL_MANY_PORTS
@@ -1164,7 +1238,7 @@
Support for sharing serial interrupts
CONFIG_SERIAL_SHARE_IRQ
Some serial boards have hardware support which allows multiple dumb
- serial ports on the same board to share a single IRQ. To enable
+ serial ports on the same board to share a single IRQ. To enable
support for this in the serial driver, say Y here.
Auto detect IRQ on standard ports (unsafe)
@@ -1181,26 +1255,20 @@
CONFIG_SERIAL_MULTIPORT
Some multiport serial ports have special ports which are used to
signal when there are any serial ports on the board which need
- servicing. Say Y here to enable the serial driver to take advantage
+ servicing. Say Y here to enable the serial driver to take advantage
of those special I/O ports.
SGI Zilog85C30 serial support
CONFIG_SGI_SERIAL
- If you want to use your SGI's built-in serial ports under Linux, say Y.
+ If you want to use your SGI's built-in serial ports under Linux,
+ answer Y.
SGI graphics support
CONFIG_SGI_GRAPHICS
- If you have an SGI machine and you want to compile the graphic drivers
- select this option. This will include the code for the /dev/graphics
- and /dev/gfx drivers into the kernel for supporting the virtualized
- access to your graphics hardware.
-
-Remote GDB kernel debugging
-CONFIG_REMOTE_DEBUG
- This enables remote debugging support for the MIPS kernel. Enabling
- this option enlarges you kernel image disk size by several megabytes
- and requires a machine with more than 16mb, better 32mb RAM to avoid
- excessive linking time.
+ If you have an SGI machine and you want to compile the graphics
+ drivers, say Y here. This will include the code for the
+ /dev/graphics and /dev/gfx drivers into the kernel for supporting
+ virtualized access to your graphics hardware.
Support the Bell Technologies HUB6 card
CONFIG_HUB6
@@ -1238,10 +1306,10 @@
CONFIG_PCI_DIRECT
If you don't want to use the PCI BIOS (e.g., because you run some
embedded system with no BIOS at all) or Linux says it cannot use
- your PCI BIOS, you can enable direct PCI hardware here. It might fail
- if your machine is based on some unusual chipset, but it usually
- works. If both PCI BIOS and direct PCI access are enabled, the use
- of BIOS is preferred. If unsure, say Y.
+ your PCI BIOS, you can enable direct PCI hardware here. It might
+ fail if your machine is based on some unusual chipset, but it
+ usually works. If both PCI BIOS and direct PCI access are enabled,
+ the use of BIOS is preferred. If unsure, say Y.
PCI quirks
CONFIG_PCI_QUIRKS
@@ -1253,9 +1321,9 @@
PCI bridge optimization (experimental)
CONFIG_PCI_OPTIMIZE
This can improve access times for some hardware devices if you have
- a really broken BIOS and your computer uses a PCI bus system. Set to
- Y if you think it might help, but try turning it off if you
- experience any problems with the PCI bus. N is the safe answer.
+ a really broken BIOS and your computer uses a PCI bus system. Say Y
+ if you think it might help, but try turning it off if you experience
+ any problems with the PCI bus. N is the safe answer.
Backward-compatible /proc/pci
CONFIG_PCI_OLD_PROC
@@ -1275,15 +1343,15 @@
MCA support
CONFIG_MCA
MicroChannel Architecture is found in some IBM PS/2 machines and
- laptops. It is a bus system similar to PCI or ISA. See
+ laptops. It is a bus system similar to PCI or ISA. See
Documentation/mca.txt (and especially the web page given there)
- before attempting to build an MCA bus kernel. Note that this is
+ before attempting to build an MCA bus kernel. Note that this is
still experimental code.
System V IPC
CONFIG_SYSVIPC
Inter Process Communication is a suite of library functions and
- system calls which let processes (= running programs) synchronize
+ system calls which let processes (running programs) synchronize
and exchange information. It is generally considered to be a good
thing, and some programs won't run unless you say Y here. In
particular, if you want to run the DOS emulator dosemu under Linux
@@ -1296,7 +1364,7 @@
(user: anonymous) from
ftp://sunsite.unc.edu/pub/Linux/docs/LDP/programmers-guide.
- Saying Y here enlarges your kernel by about 7kB. Just say Y.
+ Saying Y here enlarges your kernel by about 7 KB. Just say Y.
BSD Process Accounting
CONFIG_BSD_PROCESS_ACCT
@@ -1319,31 +1387,33 @@
enabled, a tree of modifiable sysctl entries will be generated
beneath the /proc/sys directory. They are explained in the files in
Documentation/sysctl/. Note that enabling this option will enlarge
- the kernel by at least 8kB. As it is generally a good thing, you
- should say Y here unless building a kernel for install/rescue disks
- or your system is very limited in memory.
+ the kernel by at least 8 KB.
+
+ As it is generally a good thing, you should say Y here unless
+ building a kernel for install/rescue disks or your system is very
+ limited in memory.
Kernel support for ELF binaries
CONFIG_BINFMT_ELF
ELF (Executable and Linkable Format) is a format for libraries and
executables used across different architectures and operating
- systems. Saying Y here will enable your kernel to run ELF binaries and
- enlarge it by about 2kB. ELF support under Linux has now all but
- replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC)
+ systems. Saying Y here will enable your kernel to run ELF binaries
+ and enlarge it by about 2 KB. ELF support under Linux has now all
+ but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC)
because it is portable (this does *not* mean that you will be able
- to run executables from different architectures or operating
- systems!) and makes building run-time libraries very easy. Many new
+ to run executables from different architectures or operating systems
+ however) and makes building run-time libraries very easy. Many new
executables are distributed solely in ELF format. You definitely
- want to say Y here.
+ want to say Y here.
- Information about ELF is on the WWW at
- http://www.sjc.ox.ac.uk/users/barlow/elf-howto.html (to browse the
- WWW, you need to have access to a machine on the Internet that has a
- program like lynx or netscape). If you find that after upgrading
- from Linux kernel 1.2 and saying Y here, you still can't run any ELF
- binaries (they just crash), then you'll have to install the newest
- ELF runtime libraries, including ld.so (check the file
- Documentation/Changes for location and latest version).
+ Information about ELF is contained in the ELF HOWTO available via
+ FTP (user: anonymous) at ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+
+ If you find that after upgrading from Linux kernel 1.2 and saying Y
+ here, you still can't run any ELF binaries (they just crash), then
+ you'll have to install the newest ELF runtime libraries, including
+ ld.so (check the file Documentation/Changes for location and latest
+ version).
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
@@ -1389,14 +1459,14 @@
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
+ 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
+ increase. You can even execute HTML files containing JAVA applets
+ (little embedded JAVA binaries) if those files start with the string
"<!--applet-->". If you want to use this, say Y here and read
- Documentation/java.txt.
+ Documentation/java.txt.
- If you disable this option it will reduce your kernel by about 4kB.
+ If you disable this option it will reduce your kernel by about 4 KB.
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
@@ -1417,7 +1487,7 @@
this to work, you need to have the emulator /usr/bin/em86 in place.
You may answer M to compile the emulation support as a module and
later load the module when you want to use a Linux/Intel binary. The
- module will be called binfmt_em86.o. If unsure, say Y.
+ module will be called binfmt_em86.o. If unsure, say Y.
Kernel support for MISC binaries
CONFIG_BINFMT_MISC
@@ -1450,7 +1520,7 @@
Solaris binary emulation
CONFIG_SOLARIS_EMUL
This is experimental code which will enable you to run (many)
- Solaris binaries on your SPARC Linux machine.
+ Solaris binaries on your SPARC Linux machine.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -1462,11 +1532,23 @@
This is the processor type of your CPU. This information is used for
optimizing purposes. In order to compile a kernel that can run on
all x86 CPU types (albeit not optimally fast), you can specify
- "386" here. 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.
+ "386" here. If you specify one of "486" or "Pentium" or "PPro",
+ then the kernel will run on all x86 architectures except on 386.
+
+ Here are the settings recommended for greatest speed:
+ - "386" for the AMD/Cyrix/Intel 386DX/DXL/SL/SLC/SX and
+ Cyrix/TI 486DLC/DLC2. Only "386" kernels will run on a 386 class
+ machine.
+ - "486" for the AMD/Cyrix/IBM/Intel DX4 or 486DX/DX2/SL/SX/SX2,
+ AMD/Cyrix 5x86, NexGen Nx586 and UMC U5D or U5S
+ - "Pentium" for the AMD K5, K6 and K6-3D, Cyrix MediaGX,
+ Cyrix/IBM/National Semiconductor 6x86 and GXm, IDT Centaur
+ WinChip C6, and Intel Pentium/Pentium MMX
+ - "PPro" for the Cyrix/IBM/National Semiconductor 6x86MX, MII and
+ Intel Pentium II/Pentium Pro
+
+ 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 have a single processor machine, make sure that the line
"SMP=1" at the top of the toplevel kernel Makefile is commented out;
@@ -1479,12 +1561,12 @@
like lynx or netscape). People using multiprocessor machines should
also say Y to "Enhanced Real Time Clock Support", below.
- If you want to compile a kernel that should work on both single
- processor and multi processor machines, it is possible to set SMP=1.
- The "Advanced Power Management" code (see configuration option
- below) will not work in that scenario, though. In addition, the
- kernel will be slower on single processor machines, and other
- problems may appear, so this is not recommended.
+ If you want to compile a kernel that works on both single processor
+ and multi processor machines, it is possible to set SMP=1. The
+ "Advanced Power Management" code (see configuration option below)
+ will not work in that scenario, though. In addition, the kernel will
+ be slower on single processor machines, and other problems may
+ appear, so this is not recommended.
If you don't know what to do, choose "386".
@@ -1492,7 +1574,13 @@
CONFIG_VGA_CONSOLE
Saying Y here will allow you to use Linux in text mode through a
display that complies with the generic VGA standard. Virtually
- everyone wants that. Say Y.
+ everyone wants that.
+
+ The program SVGATextMode can be used to utilize SVGA video cards to
+ their full potential in text mode. Download it via FTP (user:
+ anonymous) from ftp://sunsite.unc.edu/pub/Linux/utils/console.
+
+ Say Y.
Video mode selection support
CONFIG_VIDEO_SELECT
@@ -1528,13 +1616,15 @@
in the /dev directory, i.e. /dev/fb*.
You need an utility program called fbset to make full use of frame
- buffer devices. Please read the file
- Documentation/fb/framebuffer.txt for more information.
+ buffer devices. Please read Documentation/fb/framebuffer.txt and the
+ Framebuffer-HOWTO at
+ http://www.tahallah.demon.co.uk/programming/prog.html for more
+ information.
- If you want to play with it, say Y here and also to the driver for
- your graphics board, below. If unsure, say N, unless you are
- compiling a kernel for a non-X86 architecture, in which case you
- should say Y.
+ Say Y here and to the driver for your graphics board below if you
+ are compiling a kernel for a non-x86 architecture. If you are
+ compiling for the x86 architecture, you can say Y if you want to
+ play with it, but it is not essential.
Acorn VIDC support
CONFIG_FB_ACORN
@@ -1554,13 +1644,13 @@
Amiga OCS chipset support
CONFIG_FB_AMIGA_OCS
This enables support for the original Agnus and Denise video chips,
- found in the Amiga 1000 and most A500's and A2000's. If you intend
+ found in the Amiga 1000 and most A500's and A2000's. If you intend
to run Linux on any of these systems, say Y; otherwise say N.
Amiga ECS chipset support
CONFIG_FB_AMIGA_ECS
This enables support for the Enhanced Chip Set, found in later
- A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
+ 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.
@@ -1568,7 +1658,7 @@
CONFIG_FB_AMIGA_AGA
This enables support for the Advanced Graphics Architecture (also
known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
- and CD32. If you intend to run Linux on any of these systems, say Y;
+ and CD32. If you intend to run Linux on any of these systems, say Y;
otherwise say N.
Amiga CyberVision support
@@ -1609,7 +1699,8 @@
Open Firmware frame buffer device support
CONFIG_FB_OF
- Say Y if you want support with Open Firmware for your graphics board.
+ Say Y if you want support with Open Firmware for your graphics
+ board.
S3 Trio frame buffer device support
CONFIG_FB_S3TRIO
@@ -1626,13 +1717,13 @@
PowerMac "platinum" frame buffer device support
CONFIG_FB_PLATINUM
- This driver supports a frame buffer for the "platinum" graphics adapter
- in some Power Macintoshes.
+ This driver supports a frame buffer for the "platinum" graphics
+ adapter in some Power Macintoshes.
PowerMac "valkyrie" frame buffer device support
CONFIG_FB_VALKYRIE
- This driver supports a frame buffer for the "valkyrie" graphics adapter
- in some Power Macintoshes.
+ This driver supports a frame buffer for the "valkyrie" graphics
+ adapter in some Power Macintoshes.
Chips 65550 display support
CONFIG_FB_CT65550
@@ -1651,29 +1742,39 @@
TGA frame buffer support
CONFIG_FB_TGA
- This is the frame buffer device driver for generic TGA graphic cards.
- Say Y if you have one of those.
+ This is the frame buffer device driver for generic TGA graphic
+ cards. Say Y if you have one of those.
VESA VGA graphics console
CONFIG_FB_VESA
- This is the frame buffer device driver for generic VESA graphic cards.
- Please read Documentation/fb/vesafb.txt.
+ This is the frame buffer device driver for generic VESA 2.0
+ compliant graphic cards. The older VESA 1.2 cards are not supported.
+ You will get a boot time penguin logo at no additional cost. Please
+ read Documentation/fb/vesafb.txt and the . If unsure, say Y.
+
+Backward compatibility mode for Xpmac
+CONFIG_FB_COMPAT_XPMAC
+ If you use the Xpmac X server (common with mklinux), you'll need
+ to enable this to use X. You should consider changing to XFree86
+ which includes a server that supports the frame buffer device
+ directly (XF68_FBDev).
MDA text console (dual-headed)
CONFIG_MDA_CONSOLE
Say Y here if you have an old MDA or monochrome Hercules graphics
- adapter in your system acting as a second head ( = video card). Do
- not enable this driver if your MDA card is the primary card in your
- system; the normal VGA driver will handle it.
+ adapter in your system acting as a second head ( = video card). You
+ will then be able to use two monitors with your Linux system. Do not
+ say Y here if your MDA card is the primary card in your system; the
+ normal VGA driver will handle it.
This driver is also available as a module ( = code which can be
inserted and removed from the running kernel whenever you want).
- The module will be called mdacon.o. If you want to compile it as
+ The module will be called mdacon.o. If you want to compile it as
a module, say M here and read Documentation/modules.txt.
If unsure, say N.
-SBUS and UPA framebuffers
+SBUS and UPA frame buffers
CONFIG_FB_SBUS
Say Y if you want support for SBUS or UPA based frame buffer device.
@@ -1697,7 +1798,8 @@
TCX (SS4/SS5 only) support
CONFIG_FB_TCX
- This is the frame buffer device driver for the TCX 24/8bit frame buffer.
+ This is the frame buffer device driver for the TCX 24/8bit frame
+ buffer.
Virtual Frame Buffer support (ONLY FOR TESTING!)
CONFIG_FB_VIRTUAL
@@ -1711,19 +1813,19 @@
kernel option `video=vfb:'.
This driver is also available as a module ( = code which can be
- inserted and removed from the running kernel whenever you want).
- The module will be called vfb.o. If you want to compile it as
- a module, say M here and read Documentation/modules.txt.
+ inserted and removed from the running kernel whenever you want). The
+ module will be called vfb.o. If you want to compile it as a module,
+ say M here and read Documentation/modules.txt.
If unsure, say N.
Advanced low level driver options
CONFIG_FBCON_ADVANCED
The frame buffer console uses character drawing routines that are
- tailored to the specific organization of pixels in the memory of your
- graphics hardware. These are called the low level frame buffer console
- drivers. Note that they are used for text console output only; they are
- NOT needed for graphical applications.
+ tailored to the specific organization of pixels in the memory of
+ your graphics hardware. These are called the low level frame buffer
+ console drivers. Note that they are used for text console output
+ only; they are NOT needed for graphical applications.
If you say N here, the needed low level drivers are automatically
enabled, depending on what frame buffer devices you selected above.
@@ -1734,9 +1836,9 @@
for color depths you do not intend to use for text consoles.
Low level frame buffer console drivers can be modules ( = code which
- can be inserted and removed from the running kernel whenever you want).
- The modules will be called fbcon-*.o. If you want to compile (some of)
- them as modules, read Documentation/modules.txt.
+ can be inserted and removed from the running kernel whenever you
+ want). The modules will be called fbcon-*.o. If you want to compile
+ (some of) them as modules, read Documentation/modules.txt.
If unsure, say N.
@@ -1747,23 +1849,24 @@
2 bpp packed pixels support
CONFIG_FBCON_CFB2
- This is the low level frame buffer console driver for 2 bits per pixel
- (4 colors) packed pixels.
+ This is the low level frame buffer console driver for 2 bits per
+ pixel (4 colors) packed pixels.
4 bpp packed pixels support
CONFIG_FBCON_CFB4
- This is the low level frame buffer console driver for 4 bits per pixel
- (16 colors) packed pixels.
+ This is the low level frame buffer console driver for 4 bits per
+ pixel (16 colors) packed pixels.
8 bpp packed pixels support
CONFIG_FBCON_CFB8
- This is the low level frame buffer console driver for 8 bits per pixel
- (256 colors) packed pixels.
+ This is the low level frame buffer console driver for 8 bits per
+ pixel (256 colors) packed pixels.
16 bpp packed pixels support
CONFIG_FBCON_CFB16
This is the low level frame buffer console driver for 15 or 16 bits
- per pixel (32K or 64K colors, also known as `hicolor') packed pixels.
+ per pixel (32K or 64K colors, also known as `hicolor') packed
+ pixels.
24 bpp packed pixels support
CONFIG_FBCON_CFB24
@@ -1773,13 +1876,13 @@
32 bpp packed pixels support
CONFIG_FBCON_CFB32
- This is the low level frame buffer console driver for 32 bits per pixel
- (16M colors, also known as `truecolor') sparse packed pixels.
+ This is the low level frame buffer console driver for 32 bits per
+ pixel (16M colors, also known as `truecolor') sparse packed pixels.
Amiga bitplanes support
CONFIG_FBCON_AFB
- This is the low level frame buffer console driver for 1 to 8 bitplanes
- (2 to 256 colors) on Amiga.
+ This is the low level frame buffer console driver for 1 to 8
+ bitplanes (2 to 256 colors) on Amiga.
Amiga interleaved bitplanes support
CONFIG_FBCON_ILBM
@@ -1804,8 +1907,8 @@
Mac variable bpp packed pixels support
CONFIG_FBCON_MAC
This is the low level frame buffer console driver for 1/2/4/8/16/32
- bits per pixel packed pixels on Mac. It supports variable font widths
- for low resolution screens.
+ bits per pixel packed pixels on Mac. It supports variable font
+ widths for low resolution screens.
VGA characters/attributes support
CONFIG_FBCON_VGA
@@ -1823,13 +1926,13 @@
For extensive information about drivers for many devices attaching
to the parallel port see http://www.torque.net/linux-pp.html on the
- WWW (To browse the WWW, you need to have access to a machine on the
+ WWW (to browse the WWW, you need to have access to a machine on the
Internet that has a program like lynx or netscape).
It is possible to share a single parallel port among several devices
and it is safe to compile all the corresponding drivers into the
- kernel. If you want to compile parallel port support as a module
- ( = code which can be inserted in and removed from the running kernel
+ kernel. If you want to compile parallel port support as a module ( =
+ code which can be inserted in and removed from the running kernel
whenever you want), say M here and read Documentation/modules.txt.
The module will be called parport.o. If you have more than one
parallel port and want to specify which port and IRQ to be used by
@@ -1857,22 +1960,8 @@
Sun Ultra/AX-style hardware
CONFIG_PARPORT_AX
Say Y here if you need support for the parallel port hardware on Sun
- Ultra/AX machines. This code is also available as a module (say M),
- called parport_ax.o. If in doubt, saying N is the safe plan.
-
-Generate little endian code
-CONFIG_CPU_LITTLE_ENDIAN
- If your compiler is mipsel-linux-gcc or mipsel-linuxelf-gcc (as
- opposed to mips-linux-gcc or mips-linuxelf-gcc), say Y here,
- otherwise N. Most MIPS machines use little-endian code, but it might
- be necessary to run older Mips systems, such as the Sony News and
- MIPS RC3xxx, in big endian mode.
-
-Build fp execption handler module
-CONFIG_MIPS_FPE_MODULE
- Build the floating point exception handler module. This option is only
- useful for people working on the floating point exception handler. If
- you don't, say n.
+ Ultra/AX machines. This code is also available as a module (say M),
+ called parport_ax.o. If in doubt, saying N is the safe plan.
Plug and Play support
CONFIG_PNP
@@ -1882,8 +1971,8 @@
Auto-probe for parallel devices
CONFIG_PNP_PARPORT
Some IEEE-1284 conforming parallel-port devices can identify
- themselves when requested. Say Y to enable this feature, or M to
- compile it as a module (parport_ieee1284.o). If in doubt, say N.
+ themselves when requested. Say Y to enable this feature, or M to
+ compile it as a module (parport_ieee1284.o). If in doubt, say N.
Enable loadable module support
CONFIG_MODULES
@@ -1904,10 +1993,10 @@
same modules even after compiling a new kernel; this requires the
program modprobe. All the software needed for module support is in
the modutils package (check the file Documentation/Changes for
- location and latest version). NOTE: if you say Y here but don't
+ location and latest version). NOTE: if you say Y here but don't
have the program genksyms (which is also contained in the above
mentioned modutils package), then the building of your kernel will
- fail. If you are going to use modules that are generated from
+ fail. If you are going to use modules that are generated from
non-kernel sources, you would benefit from this option. Otherwise
it's not that important. So, N ought to be a safe bet.
@@ -1919,20 +2008,21 @@
modprobe) before you can use them. If you say Y here however, the
kernel will be able to load modules for itself: when a part of the
kernel needs a module, it runs modprobe with the appropriate
- arguments. (This is a replacement for kerneld.) Say Y here and read
- about configuring it in Documentation/kmod.txt.
+ arguments, thereby loading the module if it is available. (This is a
+ replacement for kerneld.) Say Y here and read about configuring it
+ in Documentation/kmod.txt.
ARP daemon support (EXPERIMENTAL)
CONFIG_ARPD
Normally, the kernel maintains an internal cache which maps IP
addresses to hardware addresses on the local network, so that
Ethernet/Token Ring/ etc. frames are sent to the proper address on
- the physical networking layer. For small networks having a few
+ the physical networking layer. For small networks having a few
hundred directly connected hosts or less, keeping this address
- resolution (ARP) cache inside the kernel works well. However,
+ resolution (ARP) cache inside the kernel works well. However,
maintaining an internal ARP cache does not work well for very large
switched networks, and will use a lot of kernel memory if TCP/IP
- connections are made to many machines on the network.
+ connections are made to many machines on the network.
If you say Y here, the kernel's internal ARP cache will never grow
to more than 256 entries (the oldest entries are expired in a LIFO
@@ -1940,10 +2030,10 @@
daemon arpd. Arpd then answers the address resolution request either
from its own cache or by asking the net.
- 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, and you should also say
- Y to "Kernel/User network link driver", below. If unsure, say N.
+ This code is experimental. If you do say Y here, you should obtain a
+ copy of arpd from http://www.loran.com/~layes/arpd/index.html, and
+ you should also say Y to "Kernel/User network link driver", below.
+ If unsure, say N.
TCP/IP networking
CONFIG_INET
@@ -1952,11 +2042,12 @@
kernel by about 35 kB), since some programs (e.g. the X window
system) use TCP/IP even if your machine is not connected to any
other computer. You will get the so-called loopback device which
- allows you to ping yourself (great fun, that!). This option is also
- necessary if you want to use the full power of term (term is a
- program which gives you almost full Internet connectivity if you
- have a regular dial up shell account on some Internet connected Unix
- computer. Read http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html).
+ allows you to ping yourself (great fun, that!). This option is
+ also necessary if you want to use the full power of term (term
+ is a program which gives you almost full Internet connectivity
+ if you have a regular dial up shell account on some Internet
+ connected Unix computer; for more information, read
+ http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html).
If you say Y here and also to "/proc filesystem support" and "Sysctl
support" below, you can change various aspects of the behavior of
@@ -1987,17 +2078,32 @@
will then be presented with several options that allow more precise
control about the routing process.
- The answer to this question won't directly affect the kernel: saying
- N will just cause this configure script to skip all the questions
- about advanced routing.
+ The answer to this question won't directly affect the kernel:
+ answering N will just cause this configure script to skip all the
+ questions about advanced routing.
Note that your box can only act as a router if you enable IP
forwarding in your kernel; you can do that by saying Y to "/proc
- filesystem support" and "Sysctl support" below and executing the line
+ filesystem support" and "Sysctl support" below and executing the
+ line
echo "1" > /proc/sys/net/ipv4/ip_forward
- at boot time after the /proc filesystem has been mounted.
+ at boot time after the /proc filesystem has been mounted.
+
+ If you turn on IP forwarding, you will also get the rp_filter, which
+ automatically rejects incoming packets if the routing table entry
+ for their source address doesn't match the network interface they're
+ arriving on. This has security advantages because it prevents the
+ so-called IP spoofing, however it can pose problems if you use
+ asymmetric routing (packets from you to a host take a different path
+ than packets from that host to you) or if you operate a non-routing
+ host which has several IP addresses on different interfaces. To turn
+ rp_filter off use:
+
+ echo 0 > /proc/sys/net/ipv4/conf/<device>/rp_filter
+ or
+ echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter
If unsure, say N here.
@@ -2005,8 +2111,10 @@
CONFIG_IP_MULTIPLE_TABLES
Normally, a router decides what to do with a received packet based
solely on the packet's final destination address. If you say Y here,
- routing can also take into account the originating address and the
- network device from which the packet reached us.
+ the Linux router will also be able to take the packet's source
+ address into account. Furthermore, if you also say Y to "IP: use TOS
+ value as routing key" below, the TOS (Type-Of-Service) field of the
+ packet can be used for routing decisions as well.
IP: equal cost multipath
CONFIG_IP_ROUTE_MULTIPATH
@@ -2022,10 +2130,9 @@
CONFIG_IP_ROUTE_TOS
The header of every IP packet carries a TOS (Type of Service) value
with which the packet requests a certain treatment, e.g. low latency
- (for interactive traffic), high throughput, or high reliability.
- Normally, these values are ignored, but if you say Y here, you will
- be able to specify different routes for packets with different TOS
- values.
+ (for interactive traffic), high throughput, or high reliability. If
+ you say Y here, you will be able to specify different routes for
+ packets with different TOS values.
IP: verbose route monitoring
CONFIG_IP_ROUTE_VERBOSE
@@ -2044,7 +2151,8 @@
IP: fast network address translation
CONFIG_IP_ROUTE_NAT
If you say Y here, your router will be able to modify source and
- destination addresses of packets that pass through it.
+ destination addresses of packets that pass through it, in a manner
+ you specify.
IP: optimize as router not host
CONFIG_IP_ROUTER
@@ -2057,11 +2165,13 @@
Note that your box can only act as a router if you enable IP
forwarding in your kernel; you can do that by saying Y to "/proc
- filesystem support" and "Sysctl support" below and executing the line
+ filesystem support" and "Sysctl support" below and executing the
+ line
echo "1" > /proc/sys/net/ipv4/ip_forward
- at boot time after the /proc filesystem has been mounted.
+ at boot time after the /proc filesystem has been mounted. You can do
+ that even if you say N here.
If unsure, say N here.
@@ -2095,7 +2205,7 @@
echo "1" > /proc/sys/net/ipv4/ip_forward
- at boot time after the /proc filesystem has been mounted.
+ at boot time after the /proc filesystem has been mounted.
You need to say Y to "IP firewalling" in order to be able to use IP
masquerading (masquerading means that local computers can chat with
@@ -2131,10 +2241,10 @@
This enables automatic configuration of IP addresses of devices and
of the routing table during kernel boot, based on either information
supplied at the kernel command line or by BOOTP or RARP protocols.
- You need to say Y only for diskless machines requiring network access
- to boot (in which case you want to say Y to "Root file system on
- NFS" as well), because all other machines configure the network in
- their startup scripts.
+ You need to say Y only for diskless machines requiring network
+ access to boot (in which case you want to say Y to "Root file system
+ on NFS" as well), because all other machines configure the network
+ in their startup scripts.
BOOTP support
CONFIG_IP_PNP_BOOTP
@@ -2144,7 +2254,7 @@
the BOOTP protocol (a special protocol designed for doing this job),
say Y here. In case the boot ROM of your network card was designed
for booting Linux and does BOOTP itself, providing all necessary
- information on the kernel command line, you can say N here. If
+ information on the kernel command line, you can say N here. If
unsure, say Y. Note that if you want to use BOOTP, a BOOTP server
must be operating on your network. Read Documentation/nfsroot.txt
for details.
@@ -2201,7 +2311,7 @@
This enables your Linux firewall to transparently redirect any
network traffic originating from the local network and destined
for a remote host to a local server, called a "transparent proxy
- server". This makes the local computers think they are talking to
+ server". This makes the local computers think they are talking to
the remote end, while in fact they are connected to the local
proxy. Redirection is activated by defining special input firewall
rules (using the ipchains utility) and/or by doing an appropriate
@@ -2233,7 +2343,7 @@
echo "1" > /proc/sys/net/ipv4/ip_forward
- from a boot time script after the /proc filesystem has been mounted.
+ from a boot time script after the /proc filesystem has been mounted.
Details on how to set things up are contained in the IP Masquerade
mini-HOWTO, available via FTP (user: anonymous) from
@@ -2244,33 +2354,55 @@
If you say Y here, you should also say Y to "IP: always defragment",
below.
- If you say Y here, then the modules ip_masq_ftp.o (for ftp transfers
- through the firewall), ip_masq_irc.o (for irc chats through the
- firewall), and ip_masq_raudio.o (for RealAudio downloads through the
- firewall) will automatically be compiled. Modules are pieces of code
- which can be inserted in and removed from the running kernel
- whenever you want; read Documentation/modules.txt for details.
+ If you say Y here, then the modules ip_masq_ftp.o (for ftp file
+ transfers), ip_masq_irc.o (for irc chats), ip_masq_quake.o (you
+ guessed it), ip_masq_vdolive.o (for VDOLive video connections),
+ ip_masq_cuseeme.o (for CU-SeeMe broadcasts) and ip_masq_raudio.o
+ (for RealAudio downloads) will automatically be compiled. They are
+ needed to make masquerading for these protocols work. Modules are
+ pieces of code which can be inserted in and removed from the running
+ kernel whenever you want; read Documentation/modules.txt for
+ details.
IP: ICMP masquerading
CONFIG_IP_MASQUERADE_ICMP
- The basic masquerade code described for "IP: masquerading" above only
- handles TCP or UDP packets (and ICMP errors for existing
- connections). This option adds additional support for masquerading
+ The basic masquerade code described for "IP: masquerading" above
+ only handles TCP or UDP packets (and ICMP errors for existing
+ connections). This option adds additional support for masquerading
ICMP packets, such as ping or the probes used by the Windows 95
tracert program.
If you want this, say Y.
+IP: masquerading special modules support
+CONFIG_IP_MASQUERADE_MOD
+ This provides support for special modules that can modify the
+ rewriting rules used when masquerading. Please not that this feature
+ adds a little overhead in the input packet processing chain.
+
+ Examples of such modules are ipautofw (allowing the masquerading of
+ protocols which don't have their own protocol helpers) and port
+ forwarding (making an incoming port of a local computer visible
+ through the masquerading host).
+
+ You will need the user space program "ipmasqadm" to use these
+ additional modules; you can download it from
+ http://juanjox.home.ml.org/
+
+ All this additional code is still under development and so is
+ currently marked EXPERIMENTAL.
+
+ If you want to try, for example, PORT FORWARDING, say Y.
+
IP: ipautofw masquerade support (Experimental)
CONFIG_IP_MASQUERADE_IPAUTOFW
- ipautofw is a program by Richard Lynch allowing additional support
- for masquerading protocols which do not (as yet) have their own
- protocol helpers. Information and source for ipautofw is available
- via FTP (user: anonymous) from
+ ipautofw is a program which allows the masquerading of protocols
+ which do not (as yet) have their own protocol helpers. Information
+ and source for ipautofw is available via FTP (user: anonymous) from
ftp://ftp.netis.com/pub/members/rlynch/
- For 2.1 kernels, you will need "ipmasqadm" tool from
- http://juanjox.home.ml.org
+ You will also need the ipmasqadm tool available from
+ http://juanjox.home.ml.org .
The ipautofw code is still under development and so is currently
marked EXPERIMENTAL. If you want to try it, say Y.
@@ -2280,44 +2412,27 @@
The module will be called ip_masq_autofw.o. If you want to compile
it as a module, say M here and read Documentation/modules.txt.
-IP: masquerading special modules support
-CONFIG_IP_MASQUERADE_MOD
- This provides support for special modules that can modify rewriting
- rules to achieve, for example, input port forwarding.
- Beware that this feature adds a little overhead in the input packet
- processing chain.
-
- You will need user space program "ipmasqadm" to use these
- additional modules, you can download it from
- http://juanjox.home.ml.org/
-
- All this additional code is still under development and so is currently
- marked EXPERIMENTAL.
-
- If you want to try, for example, PORT FORWARDING, say Y.
-
IP: ipportfw masquerade support
CONFIG_IP_MASQUERADE_IPPORTFW
- Port Forwarding is an addition to IP Masquerading written by Steven
- Clarke to allow some forwarding of packets from outside to inside a
- firewall on given ports. This could be useful if, for example, you
- want to run a web server behind the firewall or masquerading host
- and this web server should be visible to the outside world. An
- external client connects to port 80 of the firewall, the firewall
- forwards requests to this port to the web server, the web server
- handles the request and the results are sent through the firewall to
- the original client. The client thinks that the firewall machine
- itself is running the web server.
+ Port Forwarding is an addition to IP Masquerading which allows some
+ forwarding of packets from outside to inside a firewall on given
+ ports. This could be useful if, for example, you want to run a web
+ server behind the firewall or masquerading host and this web server
+ should be visible to the outside world. An external client connects
+ to port 80 of the firewall, the firewall forwards requests to this
+ port to the web server, the web server handles the request and the
+ results are sent through the firewall to the original client. The
+ client thinks that the firewall machine itself is running the web
+ server.
Information about it is available from
http://www.monmouth.demon.co.uk/ipsubs/portforwarding.html (to
browse the WWW, you need to have access to a machine on the Internet
- that has a program like lynx or netscape). You will need the user
- space program "ipmasqadm" which can be downloaded from
- http://juanjox.home.ml.org/
+ that has a program like lynx or netscape). For general info, please
+ see ftp://ftp.compsoc.net/users/steve/ipportfw/linux21/
- For general info, please see
- ftp://ftp.compsoc.net/users/steve/ipportfw/linux21/
+ You will need the user space program "ipmasqadm" which can be
+ downloaded from http://juanjox.home.ml.org/
The portfw code is still under development and so is currently
marked EXPERIMENTAL. If you want to try it, say Y.
@@ -2329,9 +2444,9 @@
IP: ipmarkfw masquerade support
CONFIG_IP_MASQUERADE_IPMARKFW
- This provides functionally equivalent to port forwarding, the difference
- is that Mark Forwarding uses "firewalling mark" to select which packets
- must forward (see ipchains(8), "-m" argument).
+ This provides functionality equivalent to port forwarding, the
+ difference is that Mark Forwarding uses "firewalling mark" to select
+ which packets must forward (see ipchains(8), "-m" argument).
The markfw code is still under development and so is currently
marked EXPERIMENTAL. If you want to try it, say Y.
@@ -2343,37 +2458,41 @@
IP: always defragment
CONFIG_IP_ALWAYS_DEFRAG
- This option means that all incoming fragments (= parts of IP packets
+ If you say Y here, then all incoming fragments (parts of IP packets
that arose when some host between origin and destination decided
- that the IP packets were too large and cut them into pieces) will be
+ that the packets were too large and cut them into pieces) will be
reassembled (defragmented) before being processed, even if they are
- about to be forwarded.
+ about to be forwarded.
This option is highly recommended if you 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 "IP: transparent proxying", this option is
- implicit, although it is safe to say Y here. Only say Y here if
- running either a firewall that is the sole link to your network or a
- transparent proxy; never ever say Y here for a normal router or
- host.
+ 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 must be dealt with by the firewall, which can be tricky).
+
+ When using "IP: transparent proxying", this option is implicit,
+ although it is safe to say Y here.
+
+ Only say Y here if running either a firewall that is the sole link
+ to your network or a transparent proxy; never ever say Y here for a
+ normal router or host.
IP: aliasing support
CONFIG_IP_ALIAS
Sometimes it is useful to give several IP addresses to a single
- physical network interface (= serial port or Ethernet card). The
- most common case is that you want to serve different WWW or ftp
- documents to the outside according to which of your host names was
- used to connect to you. This is called "multihosting" or "virtual
- domains" or "virtual hosting services" and is explained in detail on
- the WWW at http://www.thesphere.com/~dlp/TwoServers/ (to browse the
- WWW, you need to have access to a machine on the Internet that has a
- program like lynx or netscape) and also in the
- Virtual-Hosting-HOWTO, available via FTP (user: anonymous) from
- ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+ physical network interface (serial port or Ethernet card). The most
+ common case is that you want to serve different WWW or ftp documents
+ to the outside according to which of your host names was used to
+ connect to you. This is called "multihosting" or "virtual domains"
+ or "virtual hosting services" and is explained in detail on the WWW
+ at http://www.thesphere.com/~dlp/TwoServers/ (to browse the WWW, you
+ need to have access to a machine on the Internet that has a program
+ like lynx or netscape) and also in the Virtual-Hosting-HOWTO,
+ available via FTP (user: anonymous) from
+ ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
Another scenario would be
that there are two logical networks living on your local Ethernet
@@ -2400,27 +2519,31 @@
CONFIG_IP_PIMSM_V1
Kernel side support for Sparse Mode PIM (Protocol Independent
Multicast) version 1. This multicast routing protocol is used widely
- because Cisco supports it. You need special software to use it
+ because Cisco supports it. You need special software to use it
(pimd-v1). Please see http://netweb.usc.edu/pim/ for more
information about PIM (to browse the WWW, you need to have access to
a machine on the Internet that has a program like lynx or
- netscape). Say Y if you want to use PIM-SM v1. Note that you can say
- N here if you just want to use Dense Mode PIM.
+ netscape).
+
+ Say Y if you want to use PIM-SM v1. Note that you can say N here if
+ you just want to use Dense Mode PIM.
IP: PIM-SM version 2 support
CONFIG_IP_PIMSM_V2
Kernel side support for Sparse Mode PIM version 2. In order to use
this, you need an experimental routing daemon supporting it (pimd or
- gated-5). This routing protocol is not used widely, so say N unless
+ gated-5). This routing protocol is not used widely, so say N unless
you want to play with it.
PC/TCP compatibility mode
CONFIG_INET_PCTCP
- If you have been having difficulties telnetting to your Linux machine
- from a DOS system that uses (broken) PC/TCP networking software (all
- versions up to OnNet 2.0) over your local Ethernet try saying Y
- here. Everyone else says N. People having problems with NCSA telnet
- should see the file linux/Documentation/networking/ncsa-telnet.
+ If you have been having difficulties telnetting to your Linux
+ machine from a DOS system that uses (broken) PC/TCP networking
+ software (all versions up to OnNet 2.0) over your local Ethernet try
+ saying Y here. Everyone else says N.
+
+ People having problems with NCSA telnet should see the file
+ linux/Documentation/networking/ncsa-telnet.
Reverse ARP server
CONFIG_INET_RARP
@@ -2431,9 +2554,9 @@
addresses. Diskless Sun 3 machines use this procedure at boot time,
and diskless Linux boxes can be configured to do it as well.
- If you want your Linux box to be able to *answer* such requests, say
- Y here; you'll then have to run the program rarp ("man rarp") on
- your box.
+ If you want your Linux box to be able to *answer* such requests,
+ answer Y here; you'll then have to run the program rarp ("man rarp")
+ on your box.
If you actually want to use a diskless Sun 3 machine as an X
terminal to Linux, say Y here and fetch Linux-Xkernel from
@@ -2459,8 +2582,9 @@
Say Y if you are on a subnetted network with all machines connected
by Ethernet segments only, as this option optimizes network access
for this special case. If there are other connections, e.g. SLIP
- links, between machines of your IP network, say N. If in doubt, say
- N. The PATH mtu discovery facility will cover most cases anyway.
+ links, between machines of your IP network, say N. If in doubt,
+ answer N. The PATH mtu discovery facility will cover most cases
+ anyway.
Path MTU Discovery (normally enabled)
CONFIG_PATH_MTU_DISCOVERY
@@ -2468,8 +2592,8 @@
over the net. "Path MTU Discovery" means that, instead of always
sending very small chunks, we start out sending big ones and if we
then discover that some host along the way likes its chunks smaller,
- we adjust to a smaller size. This is good, so most people say
- Y here.
+ we adjust to a smaller size. This is good, so most people say Y
+ here.
However, some DOS software (versions of DOS NCSA telnet and Trumpet
Winsock in PPP mode) is broken and won't be able to connect to your
@@ -2481,37 +2605,39 @@
Disable NAGLE algorithm (normally enabled)
CONFIG_TCP_NAGLE_OFF
The NAGLE algorithm works by requiring an acknowledgment before
- sending small IP frames (= packets). This keeps tiny telnet and
- rlogin packets from congesting Wide Area Networks. Most people
+ sending small IP frames (packets). This keeps tiny telnet and
+ rlogin packets from congesting Wide Area Networks. Most people
strongly recommend to say N here, thereby leaving NAGLE
enabled. Those programs that would benefit from disabling this
facility can do it on a per connection basis themselves.
IP: Drop source routed frames
CONFIG_IP_NOSR
- Usually, the originator of an IP frame (= packet) specifies only the
+ Usually, the originator of an IP frame (packet) specifies only the
destination, and the hosts along the way do the routing, i.e. they
decide how to forward the frame. However, there is a feature of the
IP protocol that allows to specify the full route for a given frame
already at its origin. A frame with such a fully specified route is
called "source routed". The question now is whether we should honour
- these route requests when such frames arrive, or if we should
- drop all those frames instead. Honouring them can introduce security
- problems (and is rarely a useful feature), and hence it is recommended
- that you say Y here unless you really know what you're doing.
+ these route requests when such frames arrive, or if we should drop
+ all those frames instead. Honouring them can introduce security
+ problems (and is rarely a useful feature), and hence it is
+ recommended that you say Y here unless you really know what you're
+ doing.
-IP: Allow large windows (not recommended if <16Mb of memory)
+IP: Allow large windows (not recommended if <16 MB of memory)
CONFIG_SKB_LARGE
On high speed, long distance networks the performance limit on
- networking becomes the amount of data a machine can buffer until the
- other end confirms its reception. (At 45Mbit/second there are a lot
- of bits between New York and London ...). This option allows larger
- amounts of data to be "in flight" at a given time. It also means a
- user process can require a lot more memory for network buffers and
- thus this option is best used only on machines with 16Mb of memory
- or higher. Unless you are using long links with end to end speeds of
- over 2Mbit a second or satellite links this option will make no
- difference to performance.
+ networking becomes the amount of data the sending machine can buffer
+ until the other end confirms its reception. (At 45 Mbit/second there
+ are a lot of bits between New York and London ...). If you say Y
+ here, bigger buffers can be used which allows larger amounts of data
+ to be "in flight" at any given time. It also means a user process
+ can require a lot more memory for network buffers and thus this
+ option is best used only on machines with 16 MB of memory or higher.
+ Unless you are using long links with end to end speeds of over 2
+ Mbit a second or satellite links this option will make no difference
+ to performance.
Unix domain sockets
CONFIG_UNIX
@@ -2549,6 +2675,11 @@
given in Documentation/Changes. You will still be able to do regular
IPv4 networking as well.
+ This protocol support is also available as a module ( = code which
+ can be inserted in and removed from the running kernel whenever you
+ want). The module will be called ipv6.o. If you want to compile it
+ as a module, say M here and read Documentation/modules.txt.
+
It is safe to say N here for now.
IPv6: enable EUI-64 token format
@@ -2612,12 +2743,12 @@
CONFIG_IPX_INTERN
Every IPX network has an address that identifies it. Sometimes it is
useful to give an IPX "network" address to your Linux box as well
- (for example if your box is acting as a file server for different IPX
- networks: it will then be accessible from everywhere using the same
- address). The way this is done is to create a virtual internal
+ (for example if your box is acting as a file server for different
+ IPX networks: it will then be accessible from everywhere using the
+ same address). The way this is done is to create a virtual internal
"network" inside your box and to assign an IPX address to this
network. Say Y here if you want to do this; read the IPX-HOWTO at
- ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO for details.
+ ftp://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
@@ -2625,13 +2756,14 @@
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
+ kernel when the internal network was created. By enabling the full
internal IPX network the cross-forwarding of packets targeted at
'special' sockets to sockets listening on the primary network is
disabled. This might break existing applications, especially RIP/SAP
daemons. A RIP/SAP daemon that works well with the full internal net
- can be found on ftp://ftp.gwdg.de/pub/linux/misc/ncpfs. If you don't
- know what you are doing, say N.
+ can be found on ftp://ftp.gwdg.de/pub/linux/misc/ncpfs.
+
+ If you don't know what you are doing, say N.
IPX: SPX networking (EXPERIMENTAL)
CONFIG_SPX
@@ -2683,7 +2815,7 @@
AppleTalk-IP driver support
CONFIG_IPDDP
This allows IP networking for users who only have AppleTalk
- networking available. This feature is experimental. With this
+ networking available. This feature is experimental. With this
driver, you can either encapsulate IP inside AppleTalk (e.g. if your
Linux box is stuck on an AppleTalk only network) or decapsulate
(e.g. if you want your Linux box to act as an Internet gateway for a
@@ -2718,7 +2850,7 @@
Apple/Farallon LocalTalk PC card support
CONFIG_LTPC
This allows you to use the AppleTalk PC card to connect to LocalTalk
- networks. The card is also known as the Farallon PhoneNet PC card.
+ networks. The card is also known as the Farallon PhoneNet PC card.
If you are in doubt, this card is the one with the 65C02 chip on it.
You also need version 1.3.3 or later of the netatalk package.
This driver is experimental, which means that it may not work.
@@ -2728,8 +2860,8 @@
CONFIG_COPS
This allows you to use COPS AppleTalk cards to connect to LocalTalk
networks. You also need version 1.3.3 or later of the netatalk
- package. This driver is experimental, which means that it may not
- work. This driver will only work if you choose "AppleTalk DDP"
+ package. This driver is experimental, which means that it may not
+ work. This driver will only work if you choose "AppleTalk DDP"
networking support, above.
Please read the file Documentation/networking/cops.txt.
@@ -2746,15 +2878,16 @@
Amateur Radio support
CONFIG_HAMRADIO
- If you want to connect your Linux computer to an amateur radio, say
- Y here. You want to read http://www.tapr.org/tapr/html/pkthome.html
+ If you want to connect your Linux box to an amateur radio, answer Y
+ here. You want to read http://www.tapr.org/tapr/html/pkthome.html
(to browse the WWW, you need to have access to a machine on the
Internet that has a program like lynx or netscape) and the HAM-HOWTO
and the AX25-HOWTO, both available via FTP (user: anonymous) from
- ftp://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.
+ ftp://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.
Amateur Radio AX.25 Level 2
CONFIG_AX25
@@ -2815,7 +2948,7 @@
ftp://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
+ 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 a program
like lynx or netscape).
@@ -2836,7 +2969,7 @@
ftp://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
+ 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 a program
like lynx or netscape).
@@ -2849,7 +2982,10 @@
CONFIG_MKISS
KISS is a protocol used for the exchange of data between a computer
and a Terminal Node Controller (a small embedded system commonly
- used for networking over AX25 amateur radio connections).
+ used for networking over AX.25 amateur radio connections; it
+ connects the computer's serial port with the radio's microphone
+ input and speaker output).
+
Although KISS is less advanced than the 6pack protocol, it has
the advantage that it is already supported by most modern TNCs
without the need for a firmware upgrade.
@@ -2900,15 +3036,15 @@
the AX25-HOWTO, available via FTP (user: anonymous) in
ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/.
- This driver can operate multiple boards simultaneously. If you compile
- it as a module (by saying M instead of Y), it will be called dmascc.o.
- If you don't pass any parameter to the driver, all possible I/O
- addresses are probed. This could irritate other devices that are
- currently not in use. You may specify the list of addresses to be
- probed by "dmascc=addr1,addr2,..." (when compiled into the kernel
- image) or "io=addr1,addr2,..." (when loaded as a module). The network
- interfaces will be called dmascc0 and dmascc1 for the board detected
- first, dmascc2 and dmascc3 for the second one, and so on.
+ This driver can operate multiple boards simultaneously. If you
+ compile it as a module (by saying M instead of Y), it will be called
+ dmascc.o. If you don't pass any parameter to the driver, all
+ possible I/O addresses are probed. This could irritate other devices
+ that are currently not in use. You may specify the list of addresses
+ to be probed by "dmascc=addr1,addr2,..." (when compiled into the
+ kernel image) or "io=addr1,addr2,..." (when loaded as a module). The
+ network interfaces will be called dmascc0 and dmascc1 for the board
+ detected first, dmascc2 and dmascc3 for the second one, and so on.
Before you configure each interface with ifconfig, you MUST set
certain parameters, such as channel access timing, clock mode, and
@@ -2984,7 +3120,7 @@
driver, "BAYCOM ser12 half duplex driver for AX.25" is the old
driver and still provided in case this driver does not work with
your serial interface chip. To configure the driver, use the sethdlc
- utility available in the standard ax25 utilities package. For
+ utility available in the standard ax25 utilities package. For
information on the modems, see http://www.baycom.de (to browse the
WWW, you need to have access to a machine on the Internet that has a
program like lynx or netscape) and
@@ -2999,9 +3135,9 @@
CONFIG_BAYCOM_SER_HDX
This is one of two drivers for Baycom style simple amateur radio
modems that connect to a serial interface. The driver supports the
- ser12 design in full duplex mode. This is the old driver. It is
+ ser12 design in full duplex mode. This is the old driver. It is
still provided in case your serial interface chip does not work with
- the full duplex driver. This driver is depreciated. To configure
+ the full duplex driver. This driver is depreciated. To configure
the driver, use the sethdlc utility available in the standard ax25
utilities package. For information on the modems, see
http://www.baycom.de (to browse the WWW, you need to have access to
@@ -3016,9 +3152,9 @@
Sound card modem driver for AX.25
CONFIG_SOUNDMODEM
This experimental driver allows a standard Sound Blaster or
- WindowsSoundSystem compatible sound card to be used as a packet radio
- modem (NOT as a telephone modem!), to send digital traffic over
- amateur radio.
+ WindowsSoundSystem compatible sound card to be used as a packet
+ radio modem (NOT as a telephone 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
@@ -3039,8 +3175,8 @@
compatible cards. If you have a dual mode card (i.e. a WSS cards
with a Sound Blaster emulation) you should say N here and Y to
"Sound card modem support for WSS and Crystal cards", below, because
- this usually results in better performance. This option also supports
- SB16/32/64 in full duplex mode.
+ this usually results in better performance. This option also
+ supports SB16/32/64 in full duplex mode.
Sound card modem support for WSS and Crystal cards
CONFIG_SOUNDMODEM_WSS
@@ -3054,15 +3190,16 @@
Sound card modem support for 1200 baud AFSK modulation
CONFIG_SOUNDMODEM_AFSK1200
- This option enables the soundmodem driver 1200 baud AFSK modem,
- compatible to popular modems using TCM3105 or AM7911. The demodulator
- requires about 12% of the CPU power of a Pentium 75 CPU per channel.
+ This option enables the soundmodem driver 1200 baud AFSK modem,
+ compatible to popular modems using TCM3105 or AM7911. The
+ demodulator requires about 12% of the CPU power of a Pentium 75 CPU
+ per channel.
Sound card modem support for 2400 baud AFSK modulation (7.3728MHz crystal)
CONFIG_SOUNDMODEM_AFSK2400_7
This option enables the soundmodem driver 2400 baud AFSK modem,
compatible to TCM3105 modems (over-)clocked with a 7.3728MHz
- crystal. Note that the availability of this driver does _not_ imply
+ crystal. Note that the availability of this driver does _not_ imply
that I recommend building such links. It is only here since users
especially in eastern Europe have asked me to do so. In fact this
modulation scheme has many disadvantages, mainly its incompatibility
@@ -3097,7 +3234,7 @@
This option enables the soundmodem driver 4800 baud HAPN-1
compatible modem. This modulation seems to be widely used 'down
under' and in the Netherlands. Here, nobody uses it, so I could not
- test if it works. It is compatible to itself, however :-)
+ test if it works. It is compatible to itself, however :-)
Sound card modem support for 9600 baud FSK G3RUH modulation
CONFIG_SOUNDMODEM_FSK9600
@@ -3116,7 +3253,7 @@
(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 (WANs). Many
- countries have public X.25 networks. X.25 consists of two
+ 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).
@@ -3144,16 +3281,16 @@
LAPB Data Link Driver (EXPERIMENTAL)
CONFIG_LAPB
- Link Access Procedure, Balanced (LAPB) is the data link layer
- (i.e. the lower) part of the X.25 protocol. It offers a reliable
+ Link Access Procedure, Balanced (LAPB) is the data link layer (i.e.
+ the lower) 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, the higher part of X.25, but others are possible as
- well). Usually, LAPB is used with specialized X.21 network cards, but
- Linux currently supports LAPB only over Ethernet connections. If you
- want to use LAPB connections over Ethernet, say Y here and to "LAPB
- over Ethernet driver" below. Read
- Documentation/networking/lapb-module.txt for technical details.
+ Layer, the higher part of X.25, but others are possible as well).
+ Usually, LAPB is used with specialized X.21 network cards, but Linux
+ currently supports LAPB only over Ethernet connections. If you want
+ to use LAPB connections over Ethernet, say Y here and to "LAPB over
+ Ethernet driver" below. Read
+ Documentation/networking/lapb-module.txt for technical details.
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
@@ -3225,16 +3362,6 @@
This is a backward compatibility option, choose Y for now.
This option will be removed soon.
-HIgh Performance Parallel Interface support (EXPERIMENTAL)
-CONFIG_HIPPI
- HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
- 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
- can run over copper (25m) or fiber (300m on multi-mode or 10km on
- single-mode). If you are connected to a HIPPI network, and want
- to enable HIPPI support in the kernel, say Y here (you must also
- remember to enable the driver for your HIPPI card below). Most
- people will say N here.
-
SCSI support?
CONFIG_SCSI
If you want to use a SCSI hard disk, SCSI tape drive, SCSI CDROM or
@@ -3244,10 +3371,13 @@
because you will be asked for it.
You also need to say Y here if you want support for the parallel
- port version of the 100MB IOMEGA ZIP drive.
+ port version of the 100 MB IOMEGA ZIP drive.
Please read the SCSI-HOWTO, available via FTP (user: anonymous) in
- ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+ ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. The
+ SCSI-Programming-HOWTO contains information about how to add or
+ remove an SCSI device from a running Linux machine without
+ rebooting.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -3261,9 +3391,9 @@
CONFIG_BLK_DEV_SD
If you want to use a SCSI hard disk or the SCSI or parallel port
version of the IOMEGA ZIP drive under Linux, say Y and read the
- SCSI-HOWTO and the Disk-HOWTO, both available via FTP (user:
- anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. This is
- NOT for SCSI CDROMs.
+ SCSI-HOWTO, the Disk-HOWTO and the Multi-Disk-HOWTO, available via
+ FTP (user: anonymous) in ftp://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).
@@ -3292,8 +3422,8 @@
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 say Y or M
- to "ISO 9660 CDROM filesystem support" later.
+ ftp://sunsite.unc.edu:/pub/Linux/docs/HOWTO. Also make sure to say Y
+ or M to "ISO 9660 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).
@@ -3316,11 +3446,11 @@
directly, so you need some additional software which knows how to
talk to these devices using the SCSI protocol. For CD-writers, you
would need the program cdwrite, available via FTP (user: anonymous)
- from ftp://sunsite.unc.edu/pub/Linux/utils/disk-management; for other
- devices, it's possible that you'll have to write the driver software
- yourself, so have a look at the SCSI-HOWTO and at the
+ from ftp://sunsite.unc.edu/pub/Linux/utils/disk-management; for
+ other devices, it's possible that you'll have to write the driver
+ software yourself, so have a look at the SCSI-HOWTO and at the
SCSI-Programming-HOWTO, both available via FTP (user: anonymous) in
- sunsite.unc.edu:/pub/Linux/docs/HOWTO.
+ ftp://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),
@@ -3334,7 +3464,7 @@
Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
can say Y here to force the SCSI driver to probe for multiple LUNs.
A SCSI device with multiple LUNs acts logically like multiple SCSI
- devices. The vast majority of SCSI devices have only one LUN, and
+ devices. The vast majority of SCSI devices have only one LUN, and
so most people can say N here and should in fact do so, because it
is safer.
@@ -3342,24 +3472,30 @@
CONFIG_SCSI_CONSTANTS
The error messages regarding your SCSI hardware will be easier to
understand if you say Y here; it will enlarge your kernel by about
- 12KB. If in doubt, say Y.
+ 12 KB. If in doubt, say Y.
SCSI logging facility
CONFIG_SCSI_LOGGING
This turns on a logging facility that can be used to debug a number
- of problems. Normally no logging output will appear, but you can
- enable logging with a shell command like:
+ of SCSI related problems.
+
+ If you say Y here, no logging output will appear by default, but you
+ can enable logging by saying Y to "/proc filesystem support" and
+ "Sysctl support" below and executing the command
echo "scsi log token [level]" > /proc/scsi/scsi
+ at boot time after the /proc filesystem has been mounted.
+
There are a number of things that can be used for 'token' (you can
find them in the source: drivers/scsi/scsi.c), and this allows you
to select the types of information you want, and the level allows
- you to select the level of verbosity. If you say N here, it may be
- harder to track down some types of SCSI problems. If you say Y here
- your kernel will be somewhat larger, but there should be no
- noticeable performance impact as long as you have logging turned
- off.
+ you to select the level of verbosity.
+
+ If you say N here, it may be harder to track down some types of SCSI
+ problems. If you say Y here your kernel will be somewhat larger, but
+ there should be no noticeable performance impact as long as you have
+ logging turned off.
AdvanSys SCSI support
CONFIG_SCSI_ADVANSYS
@@ -3389,7 +3525,7 @@
CONFIG_SCSI_AHA1542
This is support for a SCSI host adapter. It is explained in section
3.4 of the SCSI-HOWTO, available via FTP (user: anonymous) at
- ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Note that Trantor was
+ ftp://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.
@@ -3422,10 +3558,10 @@
found by checking the help file for each of the available
configuration options. You also want to read
drivers/scsi/README.aic7xxx and the SCSI-HOWTO, available via FTP
- (user: anonymous) at ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Note
- that the AHA2920 SCSI host adapter is *not* supported by this
+ (user: anonymous) at ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+ Note that the AHA2920 SCSI host adapter is *not* supported by this
driver; choose "Future Domain 16xx SCSI support" instead if you have
- one of those.
+ one of those.
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),
@@ -3452,9 +3588,9 @@
Maximum number of commands per LUN
CONFIG_AIC7XXX_CMDS_PER_LUN
Specify the maximum number of commands you would like to allocate
- per LUN (a LUN is a Logical Unit Number -- some physical SCSI devices,
- e.g. CD jukeboxes, act logically as several separate units, each of
- which gets its own number).
+ per LUN (a LUN is a Logical Unit Number -- some physical SCSI
+ devices, e.g. CD jukeboxes, act logically as several separate units,
+ each of which gets its own number).
Reasonable figures are in the range of 14 to 32 commands per device,
but depending on hardware could be increased or decreased from that
@@ -3476,7 +3612,9 @@
small amount of overhead to each and every SCSI command the aic7xxx
driver handles, so if you aren't really interested in this
information, it is best to leave it disabled. This will only work if
- you also say Y to "/proc filesystem support", below. If unsure, say N.
+ you also say Y to "/proc filesystem support", below.
+
+ If unsure, say N.
Delay in seconds after SCSI bus reset
CONFIG_AIC7XXX_RESET_DELAY
@@ -3496,12 +3634,12 @@
BusLogic SCSI support
CONFIG_SCSI_BUSLOGIC
This is support for BusLogic MultiMaster and FlashPoint SCSI Host
- Adapters. Consult the SCSI-HOWTO, available via anonymous FTP from
+ Adapters. Consult the SCSI-HOWTO, available via anonymous FTP from
ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO, and the files
README.BusLogic and README.FlashPoint in drivers/scsi for more
- information. If this driver does not work correctly without
+ information. If this driver does not work correctly without
modification, please contact the author, Leonard N. Zubkoff, by
- email to lnz@dandelion.com.
+ email to lnz@dandelion.com.
You can also build this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
@@ -3512,18 +3650,18 @@
Omit BusLogic SCSI FlashPoint support
CONFIG_SCSI_OMIT_FLASHPOINT
This option allows you to omit the FlashPoint support from the
- BusLogic SCSI driver. The FlashPoint SCCB Manager code is
+ BusLogic SCSI driver. The FlashPoint SCCB Manager code is
substantial, so users of MultiMaster Host Adapters may wish to omit
it.
DTC3180/3280 SCSI support
CONFIG_SCSI_DTC3280
- This is support for DTC 3180/3280 SCSI Host Adapters. Please read
+ This is support for DTC 3180/3280 SCSI Host Adapters. Please read
the SCSI-HOWTO, available via FTP (user: anonymous) at
ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO and the file
- drivers/scsi/README.dtc3x80.
+ drivers/scsi/README.dtc3x80.
- This driver is also available as a module (= code which can be
+ This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called dtc.o. If you want to compile it as a
module, say M here and read Documentation/modules.txt.
@@ -3532,13 +3670,13 @@
CONFIG_SCSI_EATA_DMA
This is support for the EATA-DMA protocol compliant SCSI Host
Adapters like the SmartCache III/IV, SmartRAID controller families
- and the DPT PM2011B and PM2012B controllers. Note that there is
+ 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 only say Y to one of them. Please read the
SCSI-HOWTO, available via FTP (user: anonymous) at
- ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+ ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
- This driver is also available as a module (= code which can be
+ This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called eata_dma.o. If you want to compile it as a
module, say M here and read Documentation/modules.txt.
@@ -3549,9 +3687,9 @@
Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
host adapters could also use this driver but are discouraged from
doing so, since this driver only supports hard disks and lacks
- numerous features. You might want to have a look at the SCSI-HOWTO,
+ numerous features. You might want to have a look at the SCSI-HOWTO,
available via FTP (user: anonymous) at
- ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+ ftp://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),
@@ -3563,11 +3701,11 @@
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
+ have to change some settings in drivers/scsi/u14-34f.c. Read the
SCSI-HOWTO, available via FTP (user: anonymous) at
ftp://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
+ 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
@@ -3595,7 +3733,7 @@
other adapters 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 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+ (user: anonymous) at ftp://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).
@@ -3660,13 +3798,13 @@
allow DISCONNECT
CONFIG_SCSI_NCR53C7xx_DISCONNECT
This enables the disconnect/reconnect feature of the NCR SCSI
- controller. When you say Y here, a slow SCSI device will not lock
+ 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
devices at the same time. Some devices, however, do not operate
properly with this option enabled, and will cause your SCSI system
- to hang, which might cause a system crash. The safe answer
+ to hang, which might cause a system crash. The safe answer
therefore is to say N.
NCR53C8XX SCSI support
@@ -3676,7 +3814,7 @@
tagged command queuing and fast synchronous data transfers up to 80
MB/s with wide FAST-40 LVD devices and controllers.
- The NCR53C860 and NCR53C875 support FAST-20 transfers. The NCR53C895
+ The NCR53C860 and NCR53C875 support FAST-20 transfers. The NCR53C895
supports FAST-40 transfers with Ultra2 LVD devices.
Please read drivers/scsi/README.ncr53c8xx for more information.
@@ -3729,7 +3867,7 @@
device of yours to not support properly the target-disconnect
feature. In that case, you would say Y here. In general however, to
not allow targets to disconnect is not reasonable if there is more
- than 1 device on a SCSI bus. The normal answer therefore is N.
+ than 1 device on a SCSI bus. The normal answer therefore is N.
default tagged command queue depth
CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS
@@ -3740,12 +3878,12 @@
this feature, enter 0 or 1 here (it doesn't matter which).
The default value is 8 and should be supported by most hard disks.
- This option has no effect for adapters with NVRAM, since the driver
- will get this information from the user set-up. It also can be
+ This option has no effect for adapters with NVRAM, since the driver
+ will get this information from the user set-up. It also can be
overridden using a boot setup option, as follows (example):
- 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to 4,
- set queue depth to 16 for target 2 and target 3 on controller 0 and
- set queue depth to 10 for target 0 / lun 2 on controller 1.
+ 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
+ 4, set queue depth to 16 for target 2 and target 3 on controller 0
+ and set queue depth to 10 for target 0 / lun 2 on controller 1.
The normal answer therefore is to go with the default 8 and to use
a boot command line option for devices that need to use a different
@@ -3757,14 +3895,15 @@
CONFIG_SCSI_NCR53C8XX_MAX_TAGS
This option allows you to specify the maximum number of commands
that can be queued to any device, when tagged command queuing is
- possible. The default value is 32. Minimum is 2, maximum is 64.
- For value less than 32, this option only saves a little memory
- (8*7*(32-MAXTAGS) bytes), so using less than 32 isn't worth it.
- For value greater than 32, latency on reselection will be increased
- by 1 or 2 micro-seconds. So, the normal answer here is to go with the
- default value 32 unless you are using very large hard disks with
- large cache (>= 1MB) that are able to take advantage of more than
- 32 tagged commands.
+ possible. The default value is 32. Minimum is 2, maximum is 64. For
+ value less than 32, this option only saves a little memory
+ (8*7*(32-MAXTAGS) bytes), so using less than 32 isn't worth it. For
+ value greater than 32, latency on reselection will be increased by 1
+ or 2 micro-seconds.
+
+ So, the normal answer here is to go with the default value 32 unless
+ you are using very large hard disks with large cache (>= 1 MB) that
+ are able to take advantage of more than 32 tagged commands.
There is no safe option and the default answer is recommended.
@@ -3798,8 +3937,8 @@
IBMMCA SCSI support
CONFIG_SCSI_IBMMCA
This is support for the IBM SCSI adapter found in many of the PS/2
- series computers. These machines have an MCA bus, so you need to say
- Y to "MCA support" as well and read Documentation/mca.txt.
+ series computers. These machines have an MCA bus, so you need to
+ answer Y to "MCA support" as well and read Documentation/mca.txt.
If the adapter isn't found during boot (a common problem for models
56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
@@ -3840,14 +3979,14 @@
assignment of hard disks as seen from e.g. DOS or OS/2 on your
machine, which is in addition conformant to the SCSI-standard, you
must say Y here. This is also necessary for MCA-Linux users who want
- to keep downward- compatibility to older releases of the
+ to keep downward compatibility to older releases of the
IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
June 1997).
If you like to have the lowest SCSI-id assigned as drive C:, as
modern SCSI-BIOSes do, which does not conform to the standard, but
is widespread and common in the PC-world of today, you must say N
- here. If unsure, say Y.
+ here. If unsure, say Y.
Reset SCSI-devices at boot time
CONFIG_IBMMCA_SCSI_DEV_RESET
@@ -3926,8 +4065,8 @@
Qlogic FastSCSI! cards as well as any other card based on the FASXX
chip (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards); it
does NOT support the PCI version. The PCI versions are supported by
- the Qlogic ISP driver though. Information about this driver is
- contained in drivers/scsi/README.qlogicfas. You should also read
+ the Qlogic ISP driver though. Information about this driver is
+ contained in drivers/scsi/README.qlogicfas. You should also read
the SCSI-HOWTO, available via FTP (user: anonymous) at
ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
@@ -3940,12 +4079,13 @@
CONFIG_SCSI_QLOGIC_ISP
This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
- card is supported by the "AM53/79C974 PCI SCSI" driver). If you say
- Y here, make sure to say Y to "PCI BIOS support" as well. More
- information is contained in the file
- drivers/scsi/README.qlogicisp. You should also read the SCSI-HOWTO,
- available via FTP (user: anonymous) at
- ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+ card is supported by the "AM53/79C974 PCI SCSI" driver).
+
+ If you say Y here, make sure to say Y to "PCI BIOS support" as well.
+
+ Please read the file drivers/scsi/README.qlogicisp. You should also
+ read the SCSI-HOWTO, available via FTP (user: anonymous) at
+ ftp://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).
@@ -4000,7 +4140,7 @@
7000FASST SCSI support
CONFIG_SCSI_7000FASST
This driver supports the Western Digital 7000 SCSI host adapter
- family. Some information is in the source: drivers/scsi/wd7000.c.
+ family. Some information is in the source: 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
@@ -4010,12 +4150,12 @@
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
+ 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. You want to read
- the start of drivers/scsi/eata.c and the SCSI-HOWTO, available via
- FTP (user: anonymous) at ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+ reported by BIOS32 are probed as well. You want to read the start of
+ drivers/scsi/eata.c and the SCSI-HOWTO, available via FTP (user:
+ anonymous) at ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
Note that there is also another driver for the same hardware
available: "EATA-DMA support". You should say Y to only one of them.
@@ -4051,7 +4191,7 @@
This is support for the NCR53c406a SCSI host adapter. For user
configurable parameters, check out drivers/scsi/NCR53c406.c in the
kernel source. Also read the SCSI-HOWTO, available via FTP (user:
- anonymous) at ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+ anonymous) at ftp://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),
@@ -4060,31 +4200,32 @@
Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support
CONFIG_SCSI_DC390T
- This driver supports PCI SCSI host adapters based on the Am53C974A
- chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
+ This driver supports PCI SCSI host adapters based on the Am53C974A
+ chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
PCscsi/PCnet (Am53/79C974) solutions.
+
Documentation can be found in linux/drivers/scsi/README.tmscsim.
- Note that this driver does NOT support Tekram DC390W/U/F, which are
- based on NCR/Symbios chips. Use the NCR53C8XX driver for those.
- Also note, that there is another generic Am53C974 driver.
+ Note that this driver does NOT support Tekram DC390W/U/F, which are
+ based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
+ Also note that there is another generic Am53C974 driver.
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
+ inserted in and removed from the running kernel whenever you want),
+ say M here and read Documentation/modules.txt. The module will be
called tmscsim.o.
-Skip support for other Am53/79C974 based SCSI adapters
+Omit support for other Am53/79C974 based SCSI adapters
CONFIG_SCSI_DC390T_NOGENSUPP
- Normally, the DC390(T) SCSI driver relies on the DC390 EEPROM to get
- initial values for its settings, such as speed, termination, etc.
- If it can't find this EEPROM, it will use defaults or the user
- supplied boot/module parameters. For details on driver configuration
- see linux/drivers/scsi/README.tmscsim.
-
- With this option set, if no EEPROM is found, the driver gives up and
- thus only supports Tekram DC390(T) adapters. This can be useful if
- you have a DC390(T) and another Am53C974 based adapter, which, for
+ If you say N here, the DC390(T) SCSI driver relies on the DC390
+ EEPROM to get initial values for its settings, such as speed,
+ termination, etc. If it can't find this EEPROM, it will use defaults
+ or the user supplied boot/module parameters. For details on driver
+ configuration see linux/drivers/scsi/README.tmscsim.
+
+ If you say Y here and if no EEPROM is found, the driver gives up and
+ thus only supports Tekram DC390(T) adapters. This can be useful if
+ you have a DC390(T) and another Am53C974 based adapter, which, for
some reason, you want to drive with the other AM53C974 driver.
If unsure, say N.
@@ -4096,8 +4237,8 @@
available via FTP (user: anonymous) at
ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO, is for you.
- Note that there is another driver for AM53C974 based adapters: The
- Tekram DC390(T) driver.
+ Note that there is another driver for AM53C974 based adapters:
+ "Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support", above.
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),
@@ -4118,7 +4259,7 @@
IOMEGA Parallel Port ZIP drive SCSI support
CONFIG_SCSI_PPA
This driver supports the parallel port version of IOMEGA's ZIP drive
- (a 100Mb removable media device). For more information about this
+ (a 100 MB removable media device). For more information about this
driver and how to use it you should read the file
drivers/scsi/README.ppa. You should also read the SCSI-HOWTO, which
is available via FTP (user: anonymous) from
@@ -4141,17 +4282,13 @@
EPP (Enhanced Parallel Port) is a standard for parallel ports which
allows them to act as expansion buses that can handle up to 64
peripheral devices. Some parallel port chipsets are slower than
- their motherboard, and so we have to control the state of the FIFO
- every now and then to avoid data loss. The permitted values for
- this option are 0 (don't check FIFO), 1 (check FIFO every 4 bytes),
- 2 (check FIFO every other byte) and 3 (check FIFO every time). If
- your EPP chipset is from the SMC series, you are likely to have to
- set this value greater than 0.
-
-SGI wd93 Scsi Driver
-CONFIG_SCSI_SGIWD93
- This is the SCSI driver for WD33C93 / WD33C95 SCSI chips used in many
- SGI machines.
+ their motherboard, and so we have to control the state of the
+ chipset's FIFO queue every now and then to avoid data loss. This
+ will be done if you say Y here.
+
+ If your EPP chipset is from the SMC series, you are likely to have
+ to say Y here. Generally, saying Y is the safe option and slows
+ things down a bit.
SCSI Debug host simulator.
CONFIG_SCSI_DEBUG
@@ -4175,18 +4312,18 @@
Sun SOC
CONFIG_FC4_SOC
- Serial Optical Channel is an interface card with one or two Fibre Optic
- ports, each of which can be connected to a disk array. Only the SBus
- incarnation of the adapter is supported at the moment.
+ Serial Optical Channel is an interface card with one or two Fibre
+ Optic ports, each of which can be connected to a disk array. Only
+ the SBus incarnation of the adapter is supported at the moment.
SparcSTORAGE Array 100 and 200 series
CONFIG_SCSI_PLUTO
- If you never bought a disk array made by Sun, go with N.
+ If you never bought a disk array made by Sun, go with N.
AcornSCSI support
CONFIG_SCSI_ACORNSCSI_3
- This enables support for the Acorn SCSI card (aka30). If you have an
- Acorn system with one of these, say Y. If unsure, say N.
+ This enables support for the Acorn SCSI card (aka30). If you have an
+ Acorn system with one of these, say Y. If unsure, say N.
Acorn SCSI tagged queue support
CONFIG_SCSI_ACORNSCSI_TAGGED_QUEUE
@@ -4199,42 +4336,42 @@
Acorn SCSI Synchronous transfers support
CONFIG_SCSI_ACORNSCSI_SYNC
- Say Y here to enable synchronous transfer negotiation with all targets
- on the Acorn SCSI card.
+ Say Y here to enable synchronous transfer negotiation with all
+ targets on the Acorn SCSI card.
In general, this improves performance; however some SCSI devices
don't implement it properly, so the safe answer is N.
Oak SCSI support
CONFIG_SCSI_OAK1
- This enables support for the Oak SCSI card. If you have an Acorn system
- with one of these, say Y. If unsure, say N.
+ This enables support for the Oak SCSI card. If you have an Acorn
+ system with one of these, say Y. If unsure, say N.
Cumana SCSI I support
CONFIG_SCSI_CUMANA_1
- This enables support for the Cumana SCSI I card. If you have an Acorn
- system with one of these, say Y. If unsure, say N.
+ This enables support for the Cumana SCSI I card. If you have an
+ Acorn system with one of these, say Y. If unsure, say N.
Cumana SCSI II support
CONFIG_SCSI_CUMANA_2
- This enables support for the Cumana SCSI II card. If you have an Acorn
- system with one of these, say Y. If unsure, say N.
+ This enables support for the Cumana SCSI II card. If you have an
+ Acorn system with one of these, say Y. If unsure, say N.
EcoSCSI support
CONFIG_SCSI_ECOSCSI
- This enables support for the EcoSCSI card -- a small card that sits in
- the Econet socket. If you have an Acorn system with one of these,
- say Y. If unsure, say N.
+ This enables support for the EcoSCSI card -- a small card that sits
+ in the Econet socket. If you have an Acorn system with one of these,
+ say Y. If unsure, say N.
EESOX SCSI support
CONFIG_SCSI_EESOXSCSI
- This enables support for the EESOX SCSI card. If you have an Acorn
+ This enables support for the EESOX SCSI card. If you have an Acorn
system with one of these, say Y, otherwise say N.
Powertec SCSI support
CONFIG_SCSI_POWERTECSCSI
- This enables support for the Powertec SCSI card on Acorn systems. If
- you have one of these, say Y. If unsure, say N.
+ This enables support for the Powertec SCSI card on Acorn systems. If
+ you have one of these, say Y. If unsure, say N.
Network device support?
CONFIG_NETDEVICES
@@ -4255,8 +4392,8 @@
you want to use under Linux (make sure you know its name because you
will be asked for it and read the Ethernet-HOWTO (especially if you
plan to use more than one network card under Linux), available from
- sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini) or if you want to use
- SLIP (Serial Line Internet Protocol is the protocol used to send
+ ftp://sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini) or if you want to
+ use SLIP (Serial Line Internet Protocol is the protocol used to send
Internet traffic over telephone lines or null modem cables) or CSLIP
(compressed SLIP) or PPP (Point to Point Protocol, a better and
newer replacement for SLIP) or PLIP (Parallel Line Internet Protocol
@@ -4266,7 +4403,7 @@
Make sure to read the NET-2-HOWTO. Eventually, you will have to read
Olaf Kirch's excellent and free book "Network Administrator's
- Guide", to be found in sunsite.unc.edu:/pub/Linux/docs/LDP. If
+ Guide", to be found in ftp://sunsite.unc.edu:/pub/Linux/docs/LDP. If
unsure, say Y.
Dummy net driver support
@@ -4293,10 +4430,11 @@
Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
connect to your Internet service provider or to connect to some
other local Unix box or if you want to configure your Linux box as a
- Slip/CSlip server for other people to dial in. SLIP (Serial Line
- Internet Protocol) is a protocol used to send Internet traffic
- over telephone lines or serial cables (also known as
- null modems); nowadays, the PPP is a more common protocol than SLIP.
+ Slip/CSlip server for other people to dial in. SLIP (Serial Line
+ Internet Protocol) is a protocol used to send Internet traffic over
+ serial connections such as telephone lines or null modem cables;
+ nowadays, the protocol PPP is more commonly used for this same
+ purpose.
Normally, your access provider has to support SLIP in order for you
to be able to use it, but there is now a SLIP emulator called SLiRP
@@ -4313,7 +4451,7 @@
http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html (to browse
the WWW, you need to have access to a machine on the Internet that
has a program like lynx or netscape)). SLIP support will enlarge
- your kernel by about 4kB. If unsure, say N.
+ your kernel by about 4 KB. If unsure, say N.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
@@ -4325,9 +4463,9 @@
CONFIG_SLIP_COMPRESSED
This protocol is faster than SLIP because it uses compression on the
TCP/IP headers (not on the data itself), but it has to be supported
- on both ends. Ask your access provider if you are not sure and say
- Y, just in case. You will still be able to use plain SLIP. If you
- plan to use SLiRP, the SLIP emulator (available via FTP (user:
+ on both ends. Ask your access provider if you are not sure and
+ answer Y, just in case. You will still be able to use plain SLIP. If
+ you plan to use SLiRP, the SLIP emulator (available via FTP (user:
anonymous) from
ftp://sunsite.unc.edu/pub/Linux/system/network/serial/) which allows
you to use SLIP over a regular dial up shell connection, you
@@ -4371,9 +4509,9 @@
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. If you upgrade from an
- older kernel, you might need to upgrade pppd as well. The PPP option
- enlarges your kernel by about 16kB.
+ from ftp://sunsite.unc.edu:/pub/Linux/docs/HOWTO. If you upgrade
+ from an older kernel, you might need to upgrade pppd as well. The
+ PPP option enlarges your kernel by about 16 KB.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -4404,13 +4542,13 @@
STRIP (Metricom Starmode radio IP)
CONFIG_STRIP
Say Y if you have a Metricom radio and intend to use Starmode Radio
- IP. STRIP is a radio protocol developed for the MosquitoNet project
+ IP. STRIP is a radio protocol developed for the MosquitoNet project
(On the WWW at http://mosquitonet.stanford.edu/; to browse the WWW,
you need to have access to a machine on the Internet that has a
program like lynx or netscape) to send Internet traffic using
- Metricom radios. Metricom radios are small, battery powered,
+ Metricom radios. Metricom radios are small, battery powered,
100kbit/sec packet radio transceivers, about the size and weight of
- a cellular telephone. (You may also have heard them called
+ a cellular telephone. (You may also have heard them called
"Metricom modems" but we avoid the term "modem" because it misleads
many people into thinking that you can plug a Metricom modem into a
phone line and use it as a modem.)
@@ -4458,7 +4596,7 @@
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".
+ 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),
@@ -4495,8 +4633,8 @@
CONFIG_HFMODEM_WSS
This option enables the hfmodem driver to use WindowsSoundSystem
compatible cards. These cards feature a codec chip from either
- Analog Devices (such as AD1848, AD1845) or Crystal
- Semiconductors (such as CS4248, CS423x).
+ Analog Devices (such as AD1848, AD1845) or Crystal Semiconductors
+ (such as CS4248, CS423x).
PLIP (parallel port) support
CONFIG_PLIP
@@ -4504,9 +4642,9 @@
reasonably fast mini network consisting of two (or, rarely, more)
local machines. A PLIP link from a Linux box is a popular means to
install a Linux distribution on a machine which doesn't have a CDROM
- drive (a minimal system has to be transferred with floppies
- first). The kernels on both machines need to have this PLIP option
- enabled for this to work.
+ drive (a minimal system has to be transferred with floppies first).
+ The kernels on both machines need to have this PLIP option enabled
+ for this to work.
The PLIP driver has two modes, mode 0 and mode 1. The parallel ports
(the connectors at the computers with 25 holes) are connected with
@@ -4527,9 +4665,9 @@
NET-2-HOWTO in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Note that
the PLIP protocol was changed and this PLIP driver won't work
together with the PLIP support in Linux versions 1.0.x. This option
- enlarges your kernel by about 8kB.
+ enlarges your kernel by about 8 KB.
- If you want to compile this as a module (= code which can be
+ If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read Documentation/modules.txt as well as
Documentation/networking/net-modules.txt. The module will be called
@@ -4539,8 +4677,8 @@
CONFIG_EQUALIZER
If you have two serial connections to some other computer (this
usually requires two modems and two telephone lines) and you use
- SLIP (= the protocol for sending Internet traffic over telephone
- lines) or PPP (= a better SLIP) on them, you can make them behave
+ SLIP (the protocol for sending Internet traffic over telephone
+ lines) or PPP (a better SLIP) on them, you can make them behave
like one double speed connection using this driver. Naturally, this
has to be supported at the other end as well, either with a similar
EQL Linux driver or with a Livingston Portmaster 2e. Say Y if you
@@ -4565,8 +4703,8 @@
to the device tap0; everything the kernel wants to send out over the
device tap0 can instead be read by the user from /dev/tap0: the user
mode program replaces the LAN that would be attached to an ordinary
- Ethernet device. Please read the file
- Documentation/networking/ethertap.txt for more information.
+ Ethernet device. Please read the file
+ Documentation/networking/ethertap.txt for more information.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -4639,7 +4777,7 @@
AUN over UDP
CONFIG_ECONET_AUNUDP
- Say Y here if you want to send Econet/AUN traffic over a a UDP
+ Say Y here if you want to send Econet/AUN traffic over a UDP
connection (UDP is a packet based protocol that runs on top of the
Internet protocol IP) using an ordinary Ethernet network card.
@@ -4669,7 +4807,7 @@
WAN routing support is always built as a module ( = code which can
be inserted in and removed from the running kernel whenever you
- want). The module is called wanrouter.o. For general information
+ want). The module is called wanrouter.o. For general information
about modules read Documentation/modules.txt.
Fast switching (read help!)
@@ -4695,7 +4833,7 @@
8390 can be found at
ftp://ftp.inr.ac.ru/ip-routing/fastroute-8390.tar.gz). Really, this
option is applicable to any machine attached to a fast enough
- network, and even a 10Mb NIC is able to kill a not very slow box,
+ network, and even a 10 Mb NIC is able to kill a not very slow box,
such as a 120MHz Pentium.
However, do not say Y here if you did not experience any serious
@@ -4712,20 +4850,20 @@
When the kernel has several packets to send out over the network
devices, it has to make a decision which one to send first. This is
especially important if some of the network devices are real time
- devices that need a certain minimum data flow rate. There are
+ devices that need a certain minimum data flow rate. There are
several different algorithms for how to do this "fairly"; they are
- called packet schedulers. You can attach different schedulers to
- different network devices. If you want to stick to the default
+ called packet schedulers. If you want to stick to the default
scheduling algorithm, say N here. If you want to experiment with a
- couple of different algorithms, say Y. Currently, this is only
+ couple of different algorithms, say Y. You can then attach different
+ schedulers to different network devices. Currently, this is only
recommended for experts.
To administer these schedulers, you'll need the user-level utilities
from the package iproute2+tc at ftp://ftp.inr.ac.ru/ip-routing/
If you say Y here and to "/proc filesystem" below, you will be able
- to read status information about priority schedulers from
- the file /proc/net/psched.
+ to read status information about priority schedulers from the file
+ /proc/net/psched.
The available schedulers are listed in the following questions; you
can say Y to as many as you like. If unsure, say N now.
@@ -4873,24 +5011,25 @@
performance will be written to /proc/net/profile. If you don't know
what it is about, you don't need it: say N.
-#Comtrol Hostess SV-11 support
-#CONFIG_HOSTESS_SV11
-###
-### I don't know what this is.
-###
+Comtrol Hostess SV-11 support
+CONFIG_HOSTESS_SV11
+ This is a network card for high speed synchronous serial links. It
+ is commonly used to connect to Cisco equipment over HSSI links. At
+ this point, the driver can only be compiled as a module.
WAN Drivers
CONFIG_WAN_DRIVERS
Say Y to this option if your Linux box contains a WAN card and you
- are planning to use the box as a WAN ( = Wide Area Network) router
+ are planning to use the box as a WAN ( = Wide Area Network) router
( = device used to interconnect local area networks over wide area
- communication links, such as leased lines and public data networks,
- e.g. X.25 and frame relay) and you will be offered a list of drivers
+ communication links, such as leased lines or public data networks,
+ e.g. X.25 or frame relay) and you will be offered a list of drivers
for WAN cards currently available. For more information, read
- Documentation/networking/wan-router.txt. 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 WAN
- card drivers. If unsure, say N.
+ Documentation/networking/wan-router.txt.
+
+ 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 WAN card drivers. If unsure, say N.
Sangoma WANPIPE(tm) multiprotocol cards
CONFIG_VENDOR_SANGOMA
@@ -4898,12 +5037,12 @@
browse the WWW, you need to have access to a machine on the Internet
that has a program like lynx or netscape) is a family of intelligent
multiprotocol WAN adapters with data transfer rates up to T1 (1.544
- Mbps). They are also known as Synchronous Data Link Adapters (SDLA)
+ Mbps). They are also known as Synchronous Data Link Adapters (SDLA)
and designated S502E(A), S503 or S508. These cards support the X.25,
Frame Relay, and PPP protocols. If you have one or more of these
- cards, say Y to this option and read
- Documentation/networking/wanpipe.txt. The next questions will ask
- you about the protocols you want the driver to support.
+ cards, say Y to this option; you may then also want to read the file
+ Documentation/networking/wanpipe.txt. The next questions will ask
+ you about the protocols you want the driver to support.
The driver will be compiled as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -4912,8 +5051,8 @@
Maximum number of cards
CONFIG_WANPIPE_CARDS
- Enter number of WANPIPE adapters installed in your machine. The
- driver can support up to 8 cards. You may enter more than you
+ Enter number of WANPIPE adapters installed in your machine. The
+ driver can support up to 8 cards. You may enter more than you
actually have if you plan to add more cards in the future without
re-compiling the driver, but remember that in this case you'll waste
some kernel memory (about 1K per card).
@@ -4923,15 +5062,15 @@
Say Y to this option if you are planning to connect a WANPIPE card
to an X.25 network. You should then also have said Y to "CCITT X.25
Packet Layer" and "LAPB Data Link Driver", above. If you say N, the
- X.25 support will not be included in the driver (saves about 16K of
- kernel memory).
+ X.25 support will not be included in the driver (saves about 16 KB
+ of kernel memory).
WANPIPE Frame Relay support
CONFIG_WANPIPE_FR
Say Y to this option if you are planning to connect a WANPIPE card
to a frame relay network. You should then also have said Y to "Frame
Relay (DLCI) support", above. If you say N, the frame relay
- support will not be included in the driver (saves about 16K of
+ support will not be included in the driver (saves about 16 KB of
kernel memory).
WANPIPE PPP support
@@ -4940,7 +5079,7 @@
to a leased line using Point-to-Point protocol (PPP). You should
then also have said Y to "PPP (point-to-point) support", above. If
you say N, the PPP support will not be included in the driver (saves
- about 16K of kernel memory).
+ about 16 KB of kernel memory).
Ethernet (10 or 100Mbit)
CONFIG_NET_ETHERNET
@@ -4980,8 +5119,8 @@
Sun Intel Ethernet support
CONFIG_SUN_INTEL
- This is support for the Intel Ethernet cards on some Sun workstations
- (all those with a network interface 'ie0' under SunOS).
+ This is support for the Intel Ethernet cards on some Sun
+ workstations (all those with a network interface 'ie0' under SunOS).
Western Digital/SMC cards
CONFIG_NET_VENDOR_SMC
@@ -5042,7 +5181,7 @@
CONFIG_ULTRA32
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available via FTP (user: anonymous) in
- ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+ ftp://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).
@@ -5069,8 +5208,9 @@
PCI NE2000 support
CONFIG_NE2K_PCI
This driver is for NE2000 compatible PCI cards. It will not work
- with ISA NE2000 cards. If you have a PCI NE2000 network (Ethernet)
- card, say Y and read the Ethernet-HOWTO, available via FTP (user:
+ with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
+ support" below). If you have a PCI NE2000 network (Ethernet) card,
+ say Y and read the Ethernet-HOWTO, available via FTP (user:
anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
This driver is also available as a module ( = code which can be
@@ -5257,8 +5397,8 @@
CONFIG_VORTEX
If you have a 3Com "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597)
or "Boomerang" series (EtherLink XL 3c900 or 3c905) network
- (Ethernet) card, say Y and read the Ethernet-HOWTO, available via FTP
- (user: anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+ (Ethernet) card, say Y and read the Ethernet-HOWTO, available via
+ FTP (user: anonymous) in ftp://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.
@@ -5287,9 +5427,9 @@
(arguably) beautiful poetry in Documentation/networking/arcnet.txt.
You need both this driver, and the driver for the particular ARCnet
- chipset of your card. If you don't know, then it's probably a
- COM90xx type card, so say Y (or M) to "ARCnet COM90xx chipset support"
- below.
+ chipset of your card. If you don't know, then it's probably a
+ COM90xx type card, so say Y (or M) to "ARCnet COM90xx chipset
+ support" below.
You might also want to have a look at the Ethernet-HOWTO, available
via FTP (user: anonymous) in
@@ -5305,25 +5445,25 @@
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
+ 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
+ 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
+ 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)
CONFIG_ARCNET_1051
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
+ 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 say Y here to communicate with
+ 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
+ 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.
@@ -5343,7 +5483,7 @@
CONFIG_ARCNET_COM90xxIO
This is the chipset driver for the COM90xx cards, using them in
IO-mapped mode instead of memory-mapped mode. This is slower than
- the normal driver. Only use it if your card doesn't support shared
+ the normal driver. Only use it if your card doesn't support shared
memory.
This driver is also available as a module ( = code which can be
@@ -5533,7 +5673,13 @@
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available via FTP (user: anonymous) in
ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Many Ethernet cards
- without a specific driver are compatible with NE2000.
+ without a specific driver are compatible with NE2000.
+
+ If you have a PCI NE2000 card however, say N here and Y to "PCI
+ NE2000 support", above. If you have a NE2000 card and are running on
+ an MCA system (a bus system used on some IBM PS/2 computers and
+ laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
+ below.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -5547,6 +5693,18 @@
the Ethernet-HOWTO, available via FTP (user: anonymous) in
ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
+NE/2 (ne2000 MCA version) support
+CONFIG_NE2_MCA
+ If you have a network (Ethernet) card of this type, say Y and read
+ the Ethernet-HOWTO, available via FTP (user: anonymous) in
+ ftp://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 ne2.o. If you want to compile it as a
+ module, say M here and read Documentation/modules.txt as well as
+ Documentation/networking/net-modules.txt.
+
EISA, VLB, PCI and on board controllers
CONFIG_NET_EISA
This is another class of network cards which attach directly to the
@@ -5562,8 +5720,8 @@
AMD PCnet32 (VLB and PCI) support
CONFIG_PCNET32
- If you have a PCnet32 or PCnetPCI based network (Ethernet) card, say
- Y here and read the Ethernet-HOWTO, available via FTP (user:
+ If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
+ answer Y here and read the Ethernet-HOWTO, available via FTP (user:
anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
This driver is also available as a module ( = code which can be
@@ -5584,18 +5742,6 @@
module, say M here and read Documentation/modules.txt as well as
Documentation/networking/net-modules.txt.
-Racal-Interlan EISA ES3210 support
-CONFIG_ES3210
- If you have a network (Ethernet) card of this type, say Y and read
- the Ethernet-HOWTO, available via FTP (user: anonymous) in
- ftp://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 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.
-
Mylex EISA LNE390A/LNE390B support
CONFIG_LNE390
If you have a network (Ethernet) card of this type, say Y and read
@@ -5725,6 +5871,29 @@
Please email feedback to james.banks@caldera.com.
+VIA Rhine support
+CONFIG_VIA_RHINE
+ If you have a VIA "rhine" based network card (Rhine-I (3043) or
+ Rhine-2 (VT86c100A)), 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 via-rhine.o. If you want to compile it as
+ a module, say M here and read Documentation/modules.txt as well as
+ Documentation/networking/net-modules.txt.
+
+Racal-Interlan EISA ES3210 support
+CONFIG_ES3210
+ If you have a network (Ethernet) card of this type, say Y and read
+ the Ethernet-HOWTO, available via FTP (user: anonymous) in
+ ftp://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 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.
+
SMC EtherPower II (EXPERIMENTAL)
CONFIG_EPIC100
If you have an SMC EtherPower II 9432 PCI Ethernet network card
@@ -5738,11 +5907,10 @@
module, say M here and read Documentation/modules.txt as well as
Documentation/networking/net-modules.txt.
-VIA Rhine support
-CONFIG_VIA_RHINE
- If you have a VIA "rhine" based network card (Rhine-I (3043) or
- Rhine-2 (VT86c100A)), say Y here. To build this driver as a module
- say M.
+SGI Seeq ethernet controller support
+CONFIG_SGISEEQ
+ Say Y here if you have an Seeq based Ethernet network card. This is
+ used in many Silicon Graphics machines.
Zenith Z-Note support
CONFIG_ZNET
@@ -5859,9 +6027,9 @@
The traffic shaper is a virtual network device that allows you to
limit the rate of outgoing data flow over some other network
device. See Documentation/networking/shaper.txt for more
- information. To set up and configure shaper devices, you need the
+ information. To set up and configure shaper devices, you need the
shapecfg program, available via FTP (user: anonymous) from
- ftp://shadow.cabi.net/pub/Linux in the shaper package.
+ ftp://shadow.cabi.net/pub/Linux in the shaper package.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -5883,9 +6051,44 @@
This is support for the DIGITAL series of EISA (DEFEA) and PCI
(DEFPA) controllers which can connect you to a local FDDI network.
-SGI Seeq ethernet controller support
- This is a driver for the Seeq based Ethernet adapters used in many
- Silicon Graphics machines.
+HIgh Performance Parallel Interface support (EXPERIMENTAL)
+CONFIG_HIPPI
+ HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
+ 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
+ can run over copper (25m) or fiber (300m on multi-mode or 10km on
+ single-mode). HIPPI networks are commonly used for clusters and to
+ connect to super computers. If you are connected to a HIPPI network
+ and have a HIPPI network card in your computer that you want to use
+ under Linux, say Y here (you must also remember to enable the driver
+ for your HIPPI card below). Most people will say N here.
+
+CERN HIPPI PCI adapter support
+CONFIG_CERN_HIPPI
+ Say Y here if this is your PCI HIPPI network card.
+
+ This driver is also available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ The module will be called cern_hippi.o. If you want to compile it as
+ a module, say M here and read Documentation/modules.txt. If unsure,
+ say N.
+
+Essential RoadRunner HIPPI PCI adapter support
+CONFIG_ROADRUNNER
+ Say Y here if this is your PCI HIPPI network card.
+
+ This driver is also available as a module ( = code which can be
+ inserted in and removed from the running kernel whenever you want).
+ The module will be called rrunner.o. If you want to compile it as
+ a module, say M here and read Documentation/modules.txt. If unsure,
+ say N.
+
+Use large TX/RX rings
+CONFIG_ROADRUNNER_LARGE_RINGS
+ If you say Y here, the RoadRunner driver will preallocate up to 2 MB
+ of additional memory to allow for fastest operation, both for
+ transmitting and receiving. This memory cannot be used by any other
+ kernel code or by user space programs. Say Y here only if you have
+ the memory.
Acorn Ether1 card
CONFIG_ARM_ETHER1
@@ -5925,20 +6128,20 @@
file drivers/cdrom/<driver_name>.h where you can define your
interface parameters and switch some internal goodies.
- All these CDROM drivers are also usable as a module (= code which
+ All these CDROM drivers are also usable as a module ( = code which
can be inserted in and removed from the running kernel whenever you
want). If you want to compile them as module, say M instead of Y and
read Documentation/modules.txt.
- If you want to use any of these CDROM drivers, you also have to say
- Y or M to "ISO 9660 CDROM filesystem support" below (this answer will
- get "defaulted" for you if you enable any of the Linux CDROM
- drivers).
+ If you want to use any of these CDROM drivers, you also have to
+ answer Y or M to "ISO 9660 CDROM filesystem support" below (this
+ answer will get "defaulted" for you if you enable any of the Linux
+ CDROM drivers).
Sony CDU31A/CDU33A CDROM support
CONFIG_CDU31A
These CDROM drives have a spring-pop-out caddyless drawer, and a
- rectangular green LED centered beneath it. NOTE: these CDROM drives
+ rectangular green LED centered beneath it. NOTE: these CDROM drives
will not be auto detected by the kernel at boot time; you have to
provide the interface address as an option to the kernel at boot
time as described in Documentation/cdrom/cdu31a or fill in your
@@ -5964,13 +6167,13 @@
IDE/ATAPI models). Please also the file Documentation/cdrom/mcd.
With the old LU-005 model, the whole drive chassis slides out for cd
- insertion. The FX-xxx models use a motorized tray type mechanism.
+ 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
+ (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 drivers/cdrom/mcd.h.
+ look at drivers/cdrom/mcd.h.
If you say Y here, you should also say Y or M to "ISO 9660 CDROM
filesystem support" below, because that's the filesystem used on
@@ -5985,10 +6188,11 @@
CONFIG_MCDX
Use this driver if you want to be able to read XA or MultiSession
CDs (PhotoCDs) as well as ordinary CDs with your Mitsumi LU-005,
- FX-001 or FX-001D CDROM drive. In addition, this driver uses much less
- kernel memory than the old one, if that is a concern. This driver is
- able to support more than one drive, but each drive needs a separate
- interface card. Please read the file Documentation/cdrom/mcdx.
+ 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. Please read the file
+ Documentation/cdrom/mcdx.
If you say Y here, you should also say Y or M to "ISO 9660 CDROM
filesystem support" below, because that's the filesystem used on
@@ -6049,7 +6253,7 @@
CONFIG_AZTCD
This is your driver if you have an Aztech CDA268-01A, Orchid
CD-3110, Okano or Wearnes CDD110, Conrad TXC, or CyCDROM CR520 or
- CR540 CDROM drive. This driver -- just like all these CDROM drivers
+ CR540 CDROM drive. This driver -- just like all these CDROM drivers
-- is NOT for CDROM drives with IDE/ATAPI interfaces, such as Aztech
CDA269-031SE. Please read the file Documentation/cdrom/aztcd.
@@ -6078,7 +6282,7 @@
Goldstar R420 CDROM support
CONFIG_GSCD
- If this is your CDROM drive, say Y here. As described in
+ If this is your CDROM drive, say Y here. As described in the file
linux/Documentation/cdrom/gscd, you might have to change a setting
in the file linux/drivers/cdrom/gscd.h before compiling the
kernel. Please read the file Documentation/cdrom/gscd.
@@ -6095,7 +6299,7 @@
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. Please also read the file
+ 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 or M to "ISO 9660 CDROM
@@ -6139,9 +6343,9 @@
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
+ interface card that is software configurable, say Y here. Currently
only the ISP16/MAD16/Mozart sound cards with built-in cdrom
- interfaces are supported.
+ 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
@@ -6149,11 +6353,11 @@
ISP16/MAD16/Mozart soft configurable cdrom interface support
CONFIG_ISP16_CDI
- These are sound cards with with built-in cdrom interfaces using the
- OPTi 82C928 or 82C929 chips. Say Y here to have them detected and
+ These are sound cards 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.
+ 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).
@@ -6172,15 +6376,15 @@
Minix fs support
CONFIG_MINIX_FS
- Minix is a simple operating system used in many classes about
- OS's. The minix filesystem (= method to organize files on a hard disk
+ Minix is a simple operating system used in many classes about OS's.
+ The minix filesystem (method to organize files on a hard disk
partition or a floppy disk) was the original filesystem for Linux,
- has been superseded by the second extended filesystem ext2fs but is
- still used for root/boot and other floppies or ram disks since it is
- leaner. You don't want to use it on your hard disk 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.
+ has since been superseded by the second extended filesystem ext2fs
+ but is still being used for root/boot and other floppies or ram
+ disks since it is leaner. You don't want to use it on your hard disk
+ 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 filesystem.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
@@ -6190,7 +6394,7 @@
Second extended fs support
CONFIG_EXT2_FS
- This is the de facto standard Linux filesystem (= method to organize
+ This is the de facto standard Linux filesystem (method to organize
files on a storage device) for hard disks.
You want to say Y here, unless you intend to use Linux exclusively
@@ -6218,10 +6422,13 @@
directories on ext2 filesystems, use chattr ("man chattr").
Ext2fs partitions can be read from within DOS using the ext2tool
- package (available via FTP (user: anonymous) from
+ command line tool package (available via FTP (user: anonymous) from
ftp://sunsite.unc.edu/pub/Linux/system/filesystems/ext2) and from
- within Windows 95 and Windows NT using the ex2fs explorer available
- from http://jnewbigin-pc.it.swin.edu.au/Linux/Explore2fs.htm.
+ within Windows NT using the ext2nt command line tool package from
+ ftp://sunsite.unc.edu/pub/Linux/utils/dos. Explore2fs is a graphical
+ explorer for ext2fs partitions which runs on Windows 95 and Windows
+ NT and includes experimental write support; it is available from
+ http://jnewbigin-pc.it.swin.edu.au/Linux/Explore2fs.htm.
If you want to compile this filesystem as a module ( = code which
can be inserted in and removed from the running kernel whenever you
@@ -6294,33 +6501,33 @@
Another way to read and write MSDOS floppies from within Linux (but
not transparently) is with the mtools ("man mtools") program suite,
- which doesn't require the msdos filesystem support.
+ which doesn't require the msdos filesystem support.
If you want to use umsdos, the Unix-like filesystem on top of DOS,
which allows you to run Linux from within a DOS partition without
repartitioning, you'll have to say Y or M here. If you have Windows
95 or Windows NT installed on your MSDOS partitions, you should use
the VFAT filesystem instead, or you will not be able to see the long
- filenames generated by Windows 95 / Windows NT.
+ filenames generated by Windows 95 / Windows NT.
- This option will enlarge your kernel by about 7 kB. If unsure, say
- Y. This will only 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. The module will be
- called msdos.o.
+ This option will enlarge your kernel by about 7 kB. If unsure,
+ answer Y. This will only 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. The module
+ will be called msdos.o.
vfat fs support
CONFIG_VFAT_FS
This allows you to mount MSDOS partitions of your hard drive. It
- will let you use filenames in a way compatible with the long
+ will let you use filenames in a way compatible with the long
filenames used by Windows 95 and Windows NT fat-based (not NTFS)
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 said Y to the "fat fs support" above. Please read
- the file Documentation/filesystems/vfat.txt for details.
- If unsure, say N.
+ 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),
@@ -6335,7 +6542,7 @@
backing everything up and restoring afterwards) and hence you're
able to quickly try out Linux or show it to your friends; the
disadvantage is that Linux becomes susceptible to DOS viruses and
- that UMSDOS is somewhat slower than ext2fs. Another use of umsdos
+ that UMSDOS is somewhat slower than ext2fs. Another use of umsdos
is to write files with long unix filenames to MSDOS floppies; it
also allows Unix-style softlinks and owner/permissions of files on
MSDOS floppies. You will need a program called umssync in order to
@@ -6385,7 +6592,7 @@
ftp://sunsite.unc.edu/pub/Linux/docs/LDP, on its man page: "man
nfs", and in the NFS-HOWTO.
- An superior but less widely used alternative to NFS is provided by
+ A superior but less widely used alternative to NFS is provided by
the Coda filesystem; see "Coda filesystem support" below.
If you say Y here, you should have said Y to TCP/IP networking also.
@@ -6429,7 +6636,7 @@
You will need the support software from the linux-nfs package
available at ftp://ftp.mathematik.th-darmstadt.de/pub/linux/okir/.
Please read the NFS-HOWTO, available via FTP (user: anonymous) from
- sunsite.unc.edu:/pub/Linux/docs/HOWTO.
+ ftp://sunsite.unc.edu:/pub/Linux/docs/HOWTO.
The NFS server is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -6439,8 +6646,8 @@
Emulate Sun NFS daemon
CONFIG_NFSD_SUN
If you would like for the server to allow clients to access
- directories that are mountpoints on the local filesystem (this is
- how nfsd behaves on Sun systems), say yes here. If unsure, say N.
+ directories that are mount points on the local filesystem (this is
+ how nfsd behaves on Sun systems), say yes here. If unsure, say N.
OS/2 HPFS filesystem support (read only)
CONFIG_HPFS_FS
@@ -6472,7 +6679,7 @@
NTFS read-write support (experimental)
CONFIG_NTFS_RW
If you say Y here, you will (hopefully) be able to write to NTFS
- file systems as well as read from them. The read-write support
+ file systems as well as read from them. The read-write support
in NTFS is far from being complete and is not well tested. If you
enable this, back up your NTFS volume first since it may get
damaged.
@@ -6482,34 +6689,36 @@
System V and Coherent filesystem support
CONFIG_SYSV_FS
SCO, Xenix and Coherent are commercial Unix systems for Intel
- machines. Saying Y here would allow you to read and write to and
- from their floppies and hard disk partitions.
+ machines. Saying Y here would allow you to read to and write from
+ their floppies and hard disk partitions.
- If you have a floppy or hard disk partition like that, it is likely
+ If you have floppies or hard disk partitions like that, it is likely
that they contain binaries from those other Unix systems; in order
- to run these binaries, you will want to install iBCS2 (iBCS2 [Intel
- Binary Compatibility Standard] is a kernel module which lets you run
- SCO, Xenix, Wyse, UnixWare, Dell Unix and System V programs under
- Linux and is often needed to run commercial software that's only
- available for those systems. It's available via FTP (user:
- anonymous) from ftp://tsx-11.mit.edu/pub/linux/BETA).
+ to run these binaries, you will want to install iBCS2 (Intel Binary
+ Compatibility Standard is a kernel module which lets you run SCO,
+ Xenix, Wyse, UnixWare, Dell Unix and System V programs under Linux
+ and is often needed to run commercial software that's only available
+ for those systems. It's available via FTP (user: anonymous) from
+ ftp://tsx-11.mit.edu/pub/linux/BETA).
If you only intend to mount files from some other Unix over the
network using NFS, you don't need the System V 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" or
- preferably "info tar"). Note also that this option has nothing
- whatsoever to do with the option "System V IPC". Read about the
- System V filesystem in Documentation/filesystems/sysv-fs.txt. This
- option will enlarge your kernel by about 34 kB.
+ (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" or preferably "info tar"). Note also that this option has
+ nothing whatsoever to do with the option "System V IPC". Read about
+ the System V filesystem in Documentation/filesystems/sysv-fs.txt.
+ Saying Y here will enlarge your 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. The module will be
- called sysv.o. If you haven't heard about all of this before, it's
- safe to say N.
+ called sysv.o.
+
+ If you haven't heard about all of this before, it's safe to say N.
Amiga FFS filesystem support
CONFIG_AFFS_FS
@@ -6558,8 +6767,8 @@
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.
+ If you don't know whether you need it, then you don't need it:
+ answer N.
QNX filesystem support (EXPERIMENTAL)
CONFIG_QNX4FS_FS
@@ -6576,13 +6785,13 @@
Kernel automounter support
CONFIG_AUTOFS_FS
The automounter is a tool to automatically mount remote filesystems
- on demand. This implementation is partially kernel-based to reduce
+ on demand. This implementation is partially kernel-based to reduce
overhead in the already-mounted case; this is unlike the BSD
automounter (amd), which is a pure user space daemon.
To use the automounter you need the user-space tools from
- ftp://ftp.kernel.org/pub/linux/daemons/autofs; you also want to say
- Y to "NFS filesystem support", above.
+ ftp://ftp.kernel.org/pub/linux/daemons/autofs; you also want to
+ answer Y to "NFS filesystem 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),
@@ -6597,8 +6806,8 @@
BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
OpenBSD and NeXTstep) use a filesystem called UFS. Some System V
Unixes can create and mount hard disk partitions and diskettes using
- this filesystem as well. Saying Y here allows you to mount these
- partitions and diskettes.
+ this filesystem as well. Saying Y here will allow you to read from
+ and write to these partitions and diskettes.
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
@@ -6699,12 +6908,12 @@
SMB filesystem support (to mount WfW shares etc..)
CONFIG_SMB_FS
SMB (Server Message Block) is the protocol Windows for Workgroups
- (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. Currently, this works only
- if the Windows machines use TCP/IP as the underlying transport
- protocol, and not NetBEUI. For details, read
+ (WfW), Windows 95, Windows NT and OS/2 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. Currently, this
+ works only if the Windows machines use TCP/IP as the underlying
+ transport protocol, and not NetBEUI. For details, read
Documentation/filesystems/smbfs.txt and the SMB-HOWTO, available via
FTP (user: anonymous) from
ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
@@ -6738,18 +6947,17 @@
enables you to mount filesystems of a remote server and access them
with regular Unix commands as if they were sitting on your hard
disk. Coda has several advantages over NFS: support for disconnected
- operation for laptops, read/write server replication, security model
- for authentication and encryption, persistent client caches and
- write back caching.
+ operation (e.g. for laptops), read/write server replication,
+ security model for authentication and encryption, persistent client
+ caches and write back caching.
If you say Y here, your Linux box will be able to act as a Coda
*client*. You will need user level code as well, both for the client
and server. Servers are currently user level, i.e. need no kernel
- support. For technical information, read
- Documentation/filesystems/coda.txt. For further information see
- http://www.coda.cs.cmu.edu (to browse the WWW, you need to have
- access to a machine on the Internet that has a program like lynx or
- netscape) or contact Peter Braam <braam@cs.cmu.edu>.
+ support. Please read Documentation/filesystems/coda.txt and check
+ out the Coda home page http://www.coda.cs.cmu.edu (to browse the
+ WWW, you need to have access to a machine on the Internet that has a
+ program like lynx or netscape).
If you want to compile the coda client support as a module ( = code
which can be inserted in and removed from the running kernel
@@ -6764,7 +6972,7 @@
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.
+ IPX-HOWTO on ftp://sunsite.unc.edu:/pub/Linux/docs/howto.
You do not have to say Y here if you want your Linux box to act as a
file *server* for Novell NetWare clients.
@@ -6887,16 +7095,17 @@
nls codepage 850
CONFIG_NLS_CODEPAGE_850
The Microsoft fat filesystem family can deal with filenames in
- native language character sets. These character sets are stored
- in so-called DOS codepages. You need to include the appropriate
+ native language character sets. These character sets are stored in
+ so-called DOS codepages. You need to include the appropriate
codepage if you want to be able to read/write these filenames on
DOS/Windows partitions correctly. This does apply to the filenames
only, not to the file contents. You can include several codepages;
say Y here if you want to include the DOS codepage that is used for
- much of Europe -- United Kingdom, Germany, Spain, Italy, and [add more
- countries here]. It has some characters useful to many European
- languages that are not part of the US codepage 437. If unsure, say
- Y.
+ much of Europe -- United Kingdom, Germany, Spain, Italy, and [add
+ more countries here]. It has some characters useful to many European
+ languages that are not part of the US codepage 437.
+
+ If unsure, say Y.
nls codepage 852
CONFIG_NLS_CODEPAGE_852
@@ -6907,7 +7116,7 @@
DOS/Windows partitions correctly. This does apply to the filenames
only, not to the file contents. You can include several codepages;
say Y here if you want to include the Latin 2 codepage used by DOS
- for much of Central and Eastern Europe. It has all the required
+ for much of Central and Eastern Europe. It has all the required
characters for these languages: Albanian, Croatian, Czech, English,
Finnish, Hungarian, Irish, German, Polish, Romanian, Serbian (Latin
transcription), Slovak, Slovenian, and Sorbian.
@@ -7075,7 +7284,7 @@
correctly on the screen, you need to include the appropriate
input/output character sets. Say Y here for ISO8859-5, a Cyrillic
character set with which you can type Bulgarian, Byelorussian,
- Macedonian, Russian, Serbian, and Ukrainian. Note that the charset
+ Macedonian, Russian, Serbian, and Ukrainian. Note that the charset
KOI8-R is preferred in Russia.
nls iso8859-6
@@ -7131,30 +7340,67 @@
Virtual terminal
CONFIG_VT
- If you say Y here, you will get support for a terminal device with
+ If you say Y here, you will get support for terminal devices with
display and keyboard devices. These are called "virtual" because you
- can run several virtual terminals on one physical terminal; however,
- you need at least one virtual terminal device in order to make use
- of a physical terminal. Only people using embedded systems want to
- say N here; most everybody else says Y. If unsure, say Y, or else
- you won't be able to do much with your new shiny Linux system :-)
+ can run several virtual terminals (also called virtual consoles) on
+ one physical terminal. This is rather useful, for example one
+ virtual terminal can collect system messages and warnings, another
+ one can be used for a text-mode user session, and a third could run
+ an X session, all in parallel. Switching between virtual terminals
+ is done with certain key combinations, usually Alt-<function key>.
+
+ The setterm command ("man setterm") can be used to change the
+ properties (such as colors) of a virtual terminal.
+
+ You need at least one virtual terminal device in order to make use
+ of your keyboard and monitor. Therefore, only people configuring an
+ embedded system would want to say N here in order to save some
+ memory; the only way to log into such a system is then via a serial
+ or network connection.
+
+ If unsure, say Y, or else you won't be able to do much with your new
+ shiny Linux system :-)
Support for console on virtual terminal
CONFIG_VT_CONSOLE
- If you say Y here, by default all kernel messages will be sent to
- the device /dev/tty0 which corresponds to the virtual terminal that
- is visible on your display. You should say Y here unless you only
- want to have the kernel messages output to a serial port (in which
- case you probably want to say Y to "Console on serial port", below).
+ The system console is the device which receives all kernel messages
+ and warnings and which allows logins in single user mode. If you
+ answer Y here, a virtual terminal (the device used to interact with
+ a physical terminal) can be used as system console. This is the most
+ common mode of operations, so you should say Y here unless you want
+ the kernel messages be output only to a serial port (in which case
+ you should say Y to "Console on serial port", below).
+
+ If you do say Y here, by default the currently visible virtual
+ terminal (/dev/tty0) will be used as system console. You can change
+ that with a kernel command line option such as "console=tty3" which
+ would use the third virtual terminal as system console. (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
+ ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.)
+
+ If unsure, say Y.
Software generated cursor
CONFIG_SOFTCURSOR
If you say Y here, you'll be able to do lots of nice things with the
cursors of your virtual consoles -- for example turn them into
non-blinking block cursors which are more visible on laptop screens,
- or change their color depending on the virtual console you're on.
+ or change their colors depending on the virtual console they're on.
See Documentation/VGA-softcursor.txt for more information.
+Support for PowerMac keyboard
+CONFIG_MAC_KEYBOARD
+ This option allows you to use an ADB keyboard attached to your
+ machine. Note that this disables any other (ie. PS/2) keyboard
+ support, even if your machine is physically capable of using both at
+ the same time.
+
+ If you use an ADB keyboard (4 pin connector), say Y here.
+ If you use a PS/2 keyboard (6 pin connector), say N here.
+
Standard/generic serial support
CONFIG_SERIAL
This selects whether you want to include the driver for the standard
@@ -7169,38 +7415,54 @@
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 if you unload the driver. This limitation may be lifted in
- the future.]
+ be lost when the driver is unloaded. This limitation may be lifted
+ in the future.]
BTW1: If you have a mouseman serial mouse which is not recognized by
the X window system, try running gpm first.
BTW2: If you intend to connect a so-called Winmodem to your
- machine's serial port, forget it. These modems require proprietary
- drivers which are only available under Windows.
+ machine's serial port, forget it. These modems are crippled and
+ require proprietary drivers which are only available under Windows.
Most people will say Y or M here, so that they can use serial mice,
modems and similar devices connecting to the standard serial ports.
Support for console on serial port
CONFIG_SERIAL_CONSOLE
- If you say Y here, it is possible to use a serial port as the
- console. By default still the currently visible virtual console will
- be used as the system console but you can alter that using a kernel
- command line option such as "console=ttyS1". (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 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.) If you
- don't have a VGA card installed and you say Y here, the kernel will
- automatically use /dev/ttyS0 as system console.
+ If you say Y here, it will be possible to use a serial port as the
+ system console (the system console is the device which receives all
+ kernel messages and warnings and which allows logins in single user
+ mode). This could be useful if some terminal or printer is connected
+ to that serial port.
+
+ Even if you say Y here, the currently visible virtual console
+ (/dev/tty0) will still be used as the system console by default, but
+ you can alter that using a kernel command line option such as
+ "console=ttyS1". (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
+ ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.)
+
+ If you don't have a VGA card installed and you say Y here, the
+ kernel will automatically use the first serial line, /dev/ttyS0, as
+ system console.
+
+ If unsure, say N.
+
+Support for PowerMac serial ports
+CONFIG_MAC_SERIAL
+ If you have Macintosh style serial ports (8 pin mini-DIN), say Y
+ here. If you also have regular serial ports and enable the driver
+ for them, you can't currently use the serial console feature.
Comtrol Rocketport support
CONFIG_ROCKETPORT
This is a driver for the Comtrol Rocketport cards which provide
- multiple 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.
+ multiple serial ports. You would need something like this to connect
+ more than two modems to your Linux box, for instance in order to
+ become a dial-in server.
If you want to compile this driver as a module, say M here and read
Documentation/modules.txt. The module will be called rocket.o.
@@ -7208,12 +7470,12 @@
Digiboard Intelligent async support
CONFIG_DIGIEPCA
This is a driver for Digi International's Xx, Xeve, and Xem series
- of cards which provide multiple serial ports. You would need
+ of cards which provide multiple 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. This driver supports the
- original PC (ISA) boards as well as PCI, and EISA. If you have a
- card like this, say Y here and read the file
- Documentation/digiepca.txt.
+ box, for instance in order to become a dial-in server. This driver
+ supports the original PC (ISA) boards as well as PCI, and EISA. If
+ you have a card like this, say Y here and read the file
+ Documentation/digiepca.txt.
NOTE: There is another, separate driver for the Digiboard PC boards:
"Digiboard PC/Xx Support" below. You should (and can) only select
@@ -7227,8 +7489,8 @@
This is a driver for the Digiboard PC/Xe, PC/Xi, and PC/Xeve cards
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.
+ order to become a dial-in server. If you have a card like that, say
+ Y here and 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.
@@ -7238,8 +7500,8 @@
This is a driver for the SDL Communications RISCom/8 multiport card,
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.
+ in order to become a dial-in server. If you have a card like that,
+ say Y here and read the file Documentation/riscom8.txt.
Also it's possible to say M here and compile this driver as kernel
loadable module; the module will be called riscom8.o.
@@ -7249,7 +7511,7 @@
This is a driver for the Specialix IO8+ multiport card (both the
ISA and the PCI version) which gives you many serial ports. You
would need something like this to connect more than two modems to
- your Linux box, for instance in order to become a BBS.
+ your Linux box, for instance in order to become a dial-in server.
If you have a card like that, say Y here and read the file
Documentation/specialix.txt. Also it's possible to say M here and
@@ -7258,19 +7520,19 @@
Specialix DTR/RTS pin is RTS
CONFIG_SPECIALIX_RTSCTS
- The Specialix card can only support either RTS or DTR. If you say
- N here, the driver will use the pin as "DTR" when the tty is in
- software handshake mode. If you say Y here or hardware handshake
- is on, it will always be RTS. Read the file
- Documentation/specialix.txt for more information.
+ The Specialix card can only support either RTS or DTR. If you say N
+ here, the driver will use the pin as "DTR" when the tty is in
+ software handshake mode. If you say Y here or hardware handshake is
+ on, it will always be RTS. Read the file Documentation/specialix.txt
+ for more information.
Cyclades async mux support
CONFIG_CYCLADES
This is a driver for a card that 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. For
- information about the Cyclades-Z card, read
- drivers/char/README.cycladesZ.
+ your Linux box, for instance in order to become a dial-in server.
+ For information about the Cyclades-Z card, read
+ drivers/char/README.cycladesZ.
As of 1.3.9x kernels, this driver's minor numbers start at 0 instead
of 32.
@@ -7286,10 +7548,10 @@
CONFIG_STALDRV
Stallion cards give you many serial ports. You would need something
like this to connect more than two modems to your Linux box, for
- instance in order to become a BBS. If you say Y here, you will be
- asked for your specific card model in the next questions. Make sure
- to read drivers/char/README.stallion in this case. If you have never
- heard about all this, it's safe to say N.
+ instance in order to become a dial-in server. If you say Y here, you
+ will be asked for your specific card model in the next questions.
+ Make sure to read drivers/char/README.stallion in this case. If you
+ have never heard about all this, it's safe to say N.
Stallion EasyIO or EC8/32 support
CONFIG_STALLION
@@ -7315,8 +7577,8 @@
Hayes ESP serial port support
CONFIG_ESPSERIAL
- This is a driver which supports Hayes ESP serial ports. Both single
- port cards and multiport cards are supported. Make sure to read
+ This is a driver which supports Hayes ESP serial ports. Both single
+ port cards and multiport cards are supported. Make sure to read
Documentation/hayes-esp.txt.
To compile this driver as a module ( = code which can be inserted in
@@ -7346,8 +7608,9 @@
filesystem; therefore, if you say Y here you should say Y to
"/dev/pts filesystem for Unix98 PTYs" as well.
- Say Y here if you are uncertain, unless you are very short on
- memory.
+ You should say Y here only if your C library is glibc 2.1 or later
+ (equal to libc-6.1, check with "ls -l /lib/libc.so.*"). Read the
+ instructions in Documentation/Changes.
Maximum number of Unix98 PTYs in use (0-2048)
CONFIG_UNIX98_PTY_COUNT
@@ -7358,7 +7621,7 @@
connection and every xterm uses up one PTY.
When not in use, each additional set of 256 PTYs occupy
- approximately 8K of kernel memory on 32-bit architectures.
+ approximately 8 KB of kernel memory on 32-bit architectures.
Parallel printer support
CONFIG_PRINTER
@@ -7392,7 +7655,7 @@
CONFIG_PRINTER_READBACK
If your printer conforms to IEEE 1284, it may be able to provide a
status indication when you read from it (for example, with `cat
- /dev/lp1'). To use this feature, say Y here.
+ /dev/lp1'). To use this feature, say Y here.
Mouse Support (not serial mice)
CONFIG_MOUSE
@@ -7436,20 +7699,16 @@
AST and IBM all use this as their mouse port on currently shipping
machines. The trackballs of some laptops are PS/2 mice also. In
particular, the C&T 82C710 mouse on TI Travelmates is a PS/2 mouse.
+
Although PS/2 mice are not technically bus mice, they are explained
in detail in the Busmouse-HOWTO, available via FTP (user: anonymous)
- in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. When using a PS/2
- mouse, you can get problems if you want to use the mouse both on the
- Linux console and under X. Using the "-R" option of the Linux mouse
- managing program gpm (available from
- sunsite.unc.edu:/pub/Linux/system/Daemons) solves this problem, or
- you can get the "mconv" utility also from sunsite.
+ in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
- 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. 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.
+ When using a PS/2 mouse, you can get problems if you want to use the
+ mouse both on the Linux console and under X. Using the "-R" option
+ of the Linux mouse managing program gpm (available from
+ ftp://sunsite.unc.edu:/pub/Linux/system/Daemons) solves this
+ problem, or you can get the "mconv" utility also from sunsite.
C&T 82C710 mouse port support (as on TI Travelmate)
CONFIG_82C710_MOUSE
@@ -7464,7 +7723,7 @@
http://toy.cabi.net; to browse the WWW, you need to have access to a
machine on the Internet that has a program like lynx or
netscape). It can turn the digitizer pad into a PS/2 mouse emulation
- with tap gestures or into an absolute pad.
+ with tap gestures or into an absolute pad.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
@@ -7503,13 +7762,10 @@
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
- This option forces generic miscellaneous minor device support in the
- kernel, and allows later loading of user miscellaneous character
- device modules, such as drivers for optic pens and touchscreens.
- Unless you need such specific modules, or are willing to write/test
- one, just say N.
+Support for PowerMac ADB mouse
+CONFIG_ADBMOUSE
+ If you have an ADB mouse (4 pin connector) as is common on
+ Macintoshes, say Y here.
QIC-02 tape support
CONFIG_QIC02_TAPE
@@ -7525,7 +7781,7 @@
header file (include/linux/tpqic02.h), in which case you should
say N, or you can fetch a program via anonymous FTP which is able
to configure this driver during runtime. The program to do this is
- called 'qic02conf' and it is part of the 'tpqic02-support-X.Y.tar.gz'
+ called 'qic02conf' and it is part of the tpqic02-support-X.Y.tar.gz
support package.
If you want to use the qic02conf program, say Y.
@@ -7607,7 +7863,7 @@
Default block size for zftape
CONFIG_ZFT_DFLT_BLK_SZ
- If unsure leave this at its default value, i.e. 10240. Note that
+ If unsure leave this at its default value, i.e. 10240. Note that
you specify only the default block size here. The block size can be
changed at run time using the MTSETBLK tape operation with the
MTIOCTOP ioctl (i.e. with "mt -f /dev/qft0 setblk #BLKSZ" from the
@@ -7618,7 +7874,7 @@
in multiples of a fixed block size. The block size defaults to
10240 which is what GNU tar uses. The values for the block size
should be either 1 or multiples of 1024 up to a maximum value of
- 63488 (i.e. 62k). If you specify `1' then zftape's builtin
+ 63488 (i.e. 62 K). If you specify `1' then zftape's builtin
compression will be disabled.
Reasonable values are `10240' (GNU tar's default block size),
@@ -7628,12 +7884,12 @@
Number of DMA buffers
CONFIG_FT_NR_BUFFERS
- Please leave this at `3' unless you REALLY know what you are
- doing. It is not necessary to change this value. Values below 3 make
- the proper use of ftape impossible, values greater than 3 are a waste
- of memory. You can change the amount of DMA memory used by ftape at
+ Please leave this at `3' unless you REALLY know what you are doing.
+ It is not necessary to change this value. Values below 3 make the
+ proper use of ftape impossible, values greater than 3 are a waste of
+ memory. You can change the amount of DMA memory used by ftape at
runtime with "mt -f /dev/qft0 setdrvbuffer #NUMBUFFERS". Each buffer
- wastes 32kb of memory. Please note that this memory cannot be
+ wastes 32 KB of memory. Please note that this memory cannot be
swapped out.
Procfs entry for ftape
@@ -7646,9 +7902,9 @@
cartridge, the kernel driver, your tape drive, the floppy disk
controller and the error history for the most recent use of the
kernel driver. Saying Y will enlarge the size of the ftape driver
- by approximately 2k.
+ by approximately 2 KB.
- WARNING: When compiling ftape as a module (i.e. saying `M' to
+ WARNING: When compiling ftape as a module (i.e. saying M to
"Floppy tape drive") it is dangerous to use ftape's proc file system
interface. Accessing `/proc/ftape' while the module is unloaded will
result in a kernel Oops. This cannot be fixed from inside ftape.
@@ -7762,9 +8018,9 @@
Note that this menu lets you specify only the default setting for
the IRQ channel. The hardware configuration can be changed at boot
- time (when ftape is compiled into the kernel, i.e. if you specified
- Y to "Floppy tape drive") or module load time (i.e. if you have said M
- to "Floppy tape drive").
+ time (when ftape is compiled into the kernel, i.e. if you said Y to
+ "Floppy tape drive") or module load time (i.e. if you said M to
+ "Floppy tape drive").
Please read also the file Documentation/ftape.txt which contains a
short description of the parameters that can be set at boot or load
@@ -7788,9 +8044,9 @@
Note that this menu lets you specify only the default setting for
the DMA channel. The hardware configuration can be changed at boot
- time (when ftape is compiled into the kernel, i.e. if you specified
- Y to "Floppy tape drive") or module load time (i.e. if you have said M
- to "Floppy tape drive").
+ time (when ftape is compiled into the kernel, i.e. if you said Y to
+ "Floppy tape drive") or module load time (i.e. if you said M to
+ "Floppy tape drive").
Please read also the file Documentation/ftape.txt which contains a
short description of the parameters that can be set at boot or load
@@ -7828,11 +8084,11 @@
PCI or AGP bus. Enabling write-combining allows bus write transfers
to be combined into a larger transfer before bursting over the
PCI/AGP bus. This can increase performance of image write operations
- 2.5 times or more.
- This option creates a /proc/mtrr file which may be used to manipulate
- your MTRRs. Typically the X server should use this. This should have
- a reasonably generic interface so that similar control registers on
- other processors can be easily supported.
+ 2.5 times or more. This option creates a /proc/mtrr file which may
+ be used to manipulate your MTRRs. Typically the X server should use
+ this. This should have a reasonably generic interface so that
+ similar control registers on other processors can be easily
+ supported.
Saying Y here also fixes a problem with buggy SMP BIOSes which only
set the MTRRs for the boot CPU and not the secondary CPUs. This can
@@ -7841,7 +8097,8 @@
In general you should compile this into the kernel, rather than as a
loadable module, because the BIOS fix needs to be done early in the
boot sequence. If you compile this as a module, the BIOS fix will be
- delayed until when you load the module. You do this at your own risk.
+ delayed until when you load the module. You do this at your own
+ risk.
See Documentation/mtrr.txt for more information.
@@ -7853,8 +8110,8 @@
Zilog serial support
CONFIG_SUN_ZS
- This driver does not exist at this point, so you might as well say
- N.
+ This driver does not exist at this point, so you might as well
+ say N.
Advanced Power Management
CONFIG_APM
@@ -7892,41 +8149,45 @@
anything, try disabling/enabling this option (or disabling/enabling
APM in your BIOS).
- Some other things to try when experiencing seemingly random, "weird"
- problems:
- 1) passing the "no-hlt" option to the kernel
- 2) switching on floating point emulation in the kernel and passing
+ Some other things you should try when experiencing seemingly random,
+ "weird" problems:
+
+ 1) make sure that you have enough swap space and that it is
+ enabled.
+ 2) pass the "no-hlt" option to the kernel
+ 3) switch on floating point emulation in the kernel and pass
the "no387" option to the kernel
- 3) passing the "floppy=nodma" option to the kernel
- 4) passing the "mem=4M" option to the kernel (thereby disabling
- all but the first 4M of RAM)
- 5) making sure that the CPU is not over clocked.
- 6) reading the sig11 FAQ at http://www.bitwizard.nl/sig11/
- 7) disabling the cache from your BIOS settings
- 8) installing a better fan
- 9) exchanging RAM chips
- 10) exchanging the motherboard.
+ 4) pass the "floppy=nodma" option to the kernel
+ 5) pass the "mem=4M" option to the kernel (thereby disabling
+ all but the first 4 MB of RAM)
+ 6) make sure that the CPU is not over clocked.
+ 7) read the sig11 FAQ at http://www.bitwizard.nl/sig11/
+ 8) disable the cache from your BIOS settings
+ 9) install a fan for the video card or exchange video RAM
+ 10) install a better fan for the CPU
+ 11) exchange RAM chips
+ 12) exchange the motherboard.
Ignore USER SUSPEND
CONFIG_APM_IGNORE_USER_SUSPEND
- This option will ignore USER SUSPEND requests. On machines with a
- compliant APM BIOS, you want to say N. However, on the NEC Versa M
+ This option will ignore USER SUSPEND requests. On machines with a
+ compliant APM BIOS, you want to say N. However, on the NEC Versa M
series notebooks, it is necessary to say Y because of a BIOS bug.
Enable APM at boot time
CONFIG_APM_DO_ENABLE
- Enable APM features at boot time. From page 36 of the APM BIOS
+ Enable APM features at boot time. From page 36 of the APM BIOS
specification: "When disabled, the APM BIOS does not automatically
power manage devices, enter the Standby State, enter the Suspend
State, or take power saving steps in response to CPU Idle calls."
This driver will make CPU Idle calls when Linux is idle (unless this
- feature is turned off -- see "Do CPU IDLE calls", below). This
+ feature is turned off -- see "Do CPU IDLE calls", below). This
should always save battery power, but more complicated APM features
- will be dependent on your BIOS implementation. You may need to turn
+ will be dependent on your BIOS implementation. You may need to turn
this option off if your computer hangs at boot time when using APM
- support, or if it beeps continuously instead of suspending. Turn
+ support, or if it beeps continuously instead of suspending. Turn
this off if you have a NEC UltraLite Versa 33/C or a Toshiba
- T400CDT. This is off by default since most machines do fine without
+ T400CDT. This is off by default since most machines do fine without
this feature.
Do CPU IDLE calls
@@ -7941,12 +8202,12 @@
Enable console blanking using APM
CONFIG_APM_DISPLAY_BLANK
- Enable console blanking using the APM. Some laptops can use this to
+ Enable console blanking using the APM. Some laptops can use this to
turn off the LCD backlight when the screen blanker of the Linux
- virtual console blanks the screen. Note that this is only used by
+ virtual console blanks the screen. Note that this is only used by
the virtual console screen blanker, and won't turn off the backlight
when using the X Window system. This also doesn't have anything to
- do with your VESA-compliant power-saving monitor. Further, this
+ do with your VESA-compliant power-saving monitor. Further, this
option doesn't work for all laptops -- it might not turn off your
backlight at all, or it might print a lot of errors to the console,
especially if you are using gpm.
@@ -7954,13 +8215,14 @@
Power off on shutdown
CONFIG_APM_POWER_OFF
Enable the ability to power off the computer after the Linux kernel
- is halted. You will need software (e.g., a suitable version of the
+ is halted. You will need software (e.g., a suitable version of the
halt(8) command ("man 8 halt")) to cause the computer to power down.
Recent versions of the sysvinit package available from
ftp://sunsite.unc.edu/pub/Linux/system/daemons/init/ (user:
anonymous) contain support for this ("halt -p" shuts down Linux and
- powers off the computer). As with the other APM options, this
- option may not work reliably with some APM BIOS implementations.
+ powers off the computer, if executed from runlevel 0). As with the
+ other APM options, this option may not work reliably with some APM
+ BIOS implementations.
Ignore multiple suspend/standby events
CONFIG_APM_IGNORE_MULTIPLE_SUSPEND
@@ -7985,8 +8247,8 @@
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
+ The watchdog is usually used together with the watchdog daemon
+ which is available via FTP (user: anonymous) from
ftp://tsx-11.mit.edu/pub/linux/sources/sbin/. This daemon can also
monitor NFS connections and can reboot the machine when the process
table is full.
@@ -8043,7 +8305,7 @@
This is the driver for the Berkshire Products PC Watchdog card.
This card simply watches your kernel to make sure it doesn't freeze,
and if it does, it reboots your computer after a certain amount of
- time. This driver is like the WDT501 driver but for different
+ time. This driver is like the WDT501 driver but for different
hardware. Please read Documentation/pcwd-watchdog.txt. The PC
watchdog cards can be ordered from http://www.berkprod.com. Some
example rc.local files are available from ftp://ftp.bitgate.com.
@@ -8051,8 +8313,9 @@
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module 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.
+ say M here and read Documentation/modules.txt.
+
+ Most people will say N.
Acquire SBC Watchdog Timer
CONFIG_ACQUIRE_WDT
@@ -8062,54 +8325,55 @@
it does, it reboots your computer after a certain amount of time.
This driver is like the WDT501 driver but for different hardware.
- This driver is also available as a module ( = code which can be
+ This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
- The module is called pscwdt.o. If you want to compile it as a module,
- say M here and read Documentation/modules.txt. Most people will say N.
+ The module is called pscwdt.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 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.
+ 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 say Y
+ People running SMP (multiprocessor) versions of Linux should say Y
here to read and set the RTC clock in a SMP compatible
fashion. (They should also read Documentation/smp and
Documentation/IO-APIC.txt and the SMP-FAQ on the WWW at
http://www.irisa.fr/prive/mentre/smp-faq/ (to browse the WWW, you
need to have access to a machine on the Internet that has a program
- like lynx or netscape)).
+ like lynx or netscape).)
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.
+ sampling), then say Y here, and read Documentation/rtc.txt for
+ details.
Tadpole ANA H8 Support
CONFIG_H8
The Hitachi H8/337 is a microcontroller used to deal with the power
and thermal environment. If you say Y here, you will be able to
- communicate with it via via a character special device. If unsure,
- say N.
+ communicate with it via a character special device.
+
+ If unsure, say N.
/dev/nvram support
CONFIG_NVRAM
If you say Y here and create a character special file /dev/nvram
with major number 10 and minor number 144 using mknod ("man mknod"),
- you get access to the 50 bytes of non-volatile memory in the real
- time clock (RTC), which is contained in every PC and most
- Ataris. This memory is conventionally called "CMOS RAM" on PCs and
- "NVRAM" on Ataris. /dev/nvram may be used to view settings there, or
- to change them (with some utility). It could also be used to
- frequently save a few bits of very important data that may not be
- lost over power-off and for which writing to disk is too
- insecure. On Atari machines, /dev/nvram is always configured and
- does not need to be selected.
+ you get read and write access to the 50 bytes of non-volatile memory
+ in the real time clock (RTC), which is contained in every PC and
+ most Ataris. This memory is conventionally called "CMOS RAM" on PCs
+ and "NVRAM" on Ataris. /dev/nvram may be used to view settings
+ there, or to change them (with some utility). It could also be used
+ to frequently save a few bits of very important data that may not be
+ lost over power-off and for which writing to disk is too insecure.
+ On Atari machines, /dev/nvram is always configured and does not need
+ to be selected.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -8121,7 +8385,7 @@
If you have a joystick, you can say Y here to enable generic
joystick support. You will also need to say Y or M to at least one
of the hardware specific joystick drivers. This will make the
- joysticks available under /dev/jsX devices. Please read the file
+ joysticks available as /dev/jsX devices. Please read the file
Documentation/joystick.txt which contains more information and the
location of the joystick package that you'll need.
@@ -8172,31 +8436,32 @@
ThrustMaster DirectConnect (BSP) joysticks
CONFIG_JOY_THRUSTMASTER
- Say Y here if you have a ThrustMaster Millenium 3D Inceptor, ThrustMaster
- 3D Rage Pad, or ThrustMaster WCS III. For more information on how to use the
- driver please read Documentation/joystick.txt
+ Say Y here if you have a ThrustMaster Millenium 3D Inceptor,
+ ThrustMaster 3D Rage Pad, or ThrustMaster WCS III. For more
+ information on how to use the driver please read
+ Documentation/joystick.txt
NES, SNES, PSX, Multisystem gamepads
CONFIG_JOY_CONSOLE
Say Y here if you have a Nintendo Entertainment System gamepad,
Super Nintendo Entertainment System gamepad, Sony PlayStation
- gamepad or a Multisystem - Atari, Amiga, Commodore, Amstrad CPC
+ gamepad or a Multisystem -- Atari, Amiga, Commodore, Amstrad CPC
joystick. For more information on how to use the driver please read
Documentation/joystick.txt
Sega, Multisystem gamepads
CONFIG_JOY_DB9
Say Y here if you have a Sega Master System gamepad, Sega Genesis
- gamepad, Sega Saturn gamepad, or a Multisystem - Atari, Amiga,
+ gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga,
Commodore, Amstrad CPC joystick. For more information on how to use
the driver please read Documentation/joystick.txt
TurboGraFX Multisystem joystick interface
CONFIG_JOY_TURBOGRAFX
- Say Y here if you have the TurboGraFX interface by Steffen Schwenke, and
- want to use it with Multiststem - Atari, Amiga, Commodore, Amstrad CPC
- joystick. For more information on how to use the driver please read
- Documentation/joystick-parport.txt
+ Say Y here if you have the TurboGraFX interface by Steffen Schwenke,
+ and want to use it with Multiststem -- Atari, Amiga, Commodore,
+ Amstrad CPC joystick. For more information on how to use the driver
+ please read Documentation/joystick-parport.txt
Amiga joysticks
CONFIG_JOY_AMIGA
@@ -8207,13 +8472,13 @@
Atomwide Serial Support
CONFIG_ATOMWIDE_SERIAL
If you have an Atomwide Serial card for an Acorn system, say Y to
- this option. The driver can handle 1, 2, or 3 port cards.
+ this option. The driver can handle 1, 2, or 3 port cards.
If unsure, say N
The Serial Port Dual Serial Port
CONFIG_DUALSP_SERIAL
If you have the Serial Port's dual serial card for an Acorn system,
- say Y to this option. If unsure, say N
+ say Y to this option. If unsure, say N
Sound card support
CONFIG_SOUND
@@ -8240,9 +8505,8 @@
I'm told that even without a sound card, you can make your computer
say more than an occasional beep, by programming the PC speaker.
- Kernel patches and programs to do that are in the pcsndrv package on
- ftp://sunsite.unc.edu/pub/Linux/kernel/patches/console/ and in the
- pcsp patch at http://www.imladris.demon.co.uk/pcsp/
+ Kernel patches and supporting utilities to do that are in the pcsp
+ package, available at http://www.imladris.demon.co.uk/pcsp/.
OSS sound modules
CONFIG_SOUND_OSS
@@ -8267,7 +8531,7 @@
ProAudioSpectrum 16 support
CONFIG_SOUND_PAS
Answer Y only if you have a Pro Audio Spectrum 16, ProAudio Studio
- 16 or Logitech SoundMan 16 sound card. Don't answer Y if you have
+ 16 or Logitech SoundMan 16 sound card. Don't answer Y if you have
some other card made by Media Vision or Logitech since they are not
PAS16 compatible.
@@ -8277,7 +8541,7 @@
Creative Labs or a 100% hardware compatible clone (like the
Thunderboard or SM Games). If your card was in the list of supported
cards look at the card specific instructions in the
- drivers/sound/Readme.cards file before answering this question. For
+ drivers/sound/Readme.cards file before answering this question. For
an unknown card you may answer Y if the card claims to be
Sound Blaster-compatible.
@@ -8330,12 +8594,17 @@
instructions in the drivers/sound/Readme.cards file. It's safe to
answer Y if you have a true MPU401 MIDI interface card.
-6850 UART Midi support
+6850 UART support
CONFIG_SOUND_UART6850
This option enables support for MIDI interfaces based on the 6850
- UART chip. This interface is rarely found on sound cards. It's safe
+ UART chip. This interface is rarely found on sound cards. It's safe
to answer N to this question.
+VIDC Sound
+CONFIG_VIDC_SOUND
+ Say Y here for ARM systems with the VIDC video controller and 16-bit
+ Linear sound DACs. If unsure, say N.
+
PSS (AD1848, ADSP-2115, ESC614) support
CONFIG_SOUND_PSS
Answer Y or M if you have an Orchid SW32, Cardinal DSP16, Beethoven
@@ -8357,8 +8626,8 @@
Have DSPxxx.LD firmware file
CONFIG_PSS_HAVE_BOOT
- If you have the DSPxxx.LD file or SYNTH.LD file for you card, answer
- Y to include this file. Without this file the synth device (OPL) may
+ If you have the DSPxxx.LD file or SYNTH.LD file for you card, say Y
+ to include this file. Without this file the synth device (OPL) may
not work.
Full pathname of DSPxxx.LD firmware file
@@ -8369,7 +8638,7 @@
16 bit sampling option of GUS (_NOT_ GUS MAX)
CONFIG_SOUND_GUS16
Answer Y if you have installed the 16 bit sampling daughtercard on
- your GUS. Answer N if you have a GUS MAX, since saying Y here
+ your GUS. Answer N if you have a GUS MAX, since saying Y here
disables GUS MAX support.
GUS MAX support
@@ -8378,10 +8647,10 @@
Microsoft Sound System support
CONFIG_SOUND_MSS
- Again think carefully before answering Y to this question. It's
- safe to answer Y if you have the original Windows Sound System card
- made by Microsoft or Aztech SG 16 Pro (or NX16 Pro). Also you may
- answer Y in case your card is NOT among these:
+ Again think carefully before answering Y to this question. It's safe
+ to answer Y if you have the original Windows Sound System card made
+ by Microsoft or Aztech SG 16 Pro (or NX16 Pro). Also you may say Y
+ in case your card is NOT among these:
ATI Stereo F/X, AdLib, Audio Excell DSP16, Cardinal DSP16,
Ensoniq SoundScape (and compatibles made by Reveal and Spea),
@@ -8448,27 +8717,33 @@
Support MIDI in older MAD16 based cards (requires SB)
CONFIG_MAD16_OLDCARD
- Answer Y (or M) if you have an older card based on the C928
- or Mozart chipset and you want to have MIDI support. If you
- enable this option you also need to enable support for Sound Blaster.
+ Answer Y (or M) if you have an older card based on the C928 or
+ Mozart chipset and you want to have MIDI support. If you enable this
+ option you also need to enable support for Sound Blaster.
Support for Crystal CS4232 based (PnP) cards
CONFIG_SOUND_CS4232
Say Y here if you have a card based on the Crystal CS4232 chip set,
- which uses its own Plug and Play protocol. See
- Documentation/sound/CS4232 for more information on configuring this
- card.
+ which uses its own Plug and Play protocol.
+
+ See Documentation/sound/CS4232 for more information on configuring
+ this card.
+
+Support for Yamaha OPL3-SA[2,3,x] based (PnP) cards
+CONFIG_SOUND_OPL3SA2
+ Say Y or M here if you have such a sound card.
Support for Turtle Beach Wave Front (Maui, Tropez) synthesizers
CONFIG_SOUND_MAUI
- Say Y here if you have a Turtle Beach Wave Front, Maui, or
- Tropez sound card.
+ Say Y here if you have a Turtle Beach Wave Front, Maui, or Tropez
+ sound card.
Have OSWF.MOT firmware file
CONFIG_MAUI_HAVE_BOOT
- Turtle Beach Maui and Tropez sound cards have a microcontroller which
- needs to be initialized prior to use. OSWF.MOT is a file distributed
- with the card's DOS/Windows drivers. Answer Y if you have this file.
+ Turtle Beach Maui and Tropez sound cards have a microcontroller
+ which needs to be initialized prior to use. OSWF.MOT is a file
+ distributed with the card's DOS/Windows drivers. Answer Y if you
+ have this file.
Full pathname of OSWF.MOT firmware file
CONFIG_MAUI_BOOT_FILE
@@ -8477,22 +8752,23 @@
Support for Turtle Beach MultiSound Classic, Tahiti, Monterey
CONFIG_SOUND_MSNDCLAS
Say M here if you have a Turtle Beach MultiSound Classic, Tahiti or
- Monterey (not for the Pinnacle or Fiji). See
- Documentation/sound/MultiSound for important information about this
- driver.
+ Monterey (not for the Pinnacle or Fiji).
+
+ See Documentation/sound/MultiSound for important information about
+ this driver.
Full pathname of MSNDINIT.BIN firmware file
CONFIG_MSNDCLAS_INIT_FILE
The MultiSound cards have two firmware files which are required for
- operation, and are not currently included. These files can be
- obtained from Turtle Beach. See Documentation/sound/MultiSound for
+ operation, and are not currently included. These files can be
+ obtained from Turtle Beach. See Documentation/sound/MultiSound for
information on how to obtain this.
Full pathname of MSNDPERM.BIN firmware file
CONFIG_MSNDCLAS_PERM_FILE
The MultiSound cards have two firmware files which are required for
- operation, and are not currently included. These files can be
- obtained from Turtle Beach. See Documentation/sound/MultiSound for
+ operation, and are not currently included. These files can be
+ obtained from Turtle Beach. See Documentation/sound/MultiSound for
information on how to obtain this.
Support for Turtle Beach MultiSound Pinnacle, Fiji
@@ -8504,61 +8780,61 @@
Full pathname of PNDSPINI.BIN firmware file
CONFIG_MSNDPIN_INIT_FILE
The MultiSound cards have two firmware files which are required for
- operation, and are not currently included. These files can be
- obtained from Turtle Beach. See Documentation/sound/MultiSound for
+ operation, and are not currently included. These files can be
+ obtained from Turtle Beach. See Documentation/sound/MultiSound for
information on how to obtain this.
Full pathname of PNDSPERM.BIN firmware file
CONFIG_MSNDPIN_PERM_FILE
The MultiSound cards have two firmware files which are required for
- operation, and are not currently included. These files can be
- obtained from Turtle Beach. See Documentation/sound/MultiSound for
+ operation, and are not currently included. These files can be
+ obtained from Turtle Beach. See Documentation/sound/MultiSound for
information on how to obtain this.
MSND Pinnacle have S/PDIF I/O
CONFIG_MSNDPIN_DIGITAL
- If you have the S/PDIF daughterboard for the Pinnacle or Fiji, say Y
- here; otherwise, say N. If you have this, you will be able to play
- and record from the S/PDIF port (digital signal). See
+ If you have the S/PDIF daughter board for the Pinnacle or Fiji,
+ answer Y here; otherwise, say N. If you have this, you will be able
+ to play and record from the S/PDIF port (digital signal). See
Documentation/sound/MultiSound for information on how to make use of
this capability.
MSND Pinnacle non-PnP Mode
CONFIG_MSNDPIN_NONPNP
The Pinnacle and Fiji card resources can be configured either with
- PnP, or through a configuration port. For the Pinnacle,
- configuration in non-PnP mode allows use of the IDE and joystick
- peripherals on the card as well, since they do not show up when the
- card is in PnP mode. Specifying zero for any resource of a device
- will disable the device. If you are running the card in PnP mode,
- you must say N here and use isapnptools to configure the card's
- resources.
+ PnP, or through a configuration port. Say Y here if your card is NOT
+ in PnP mode. For the Pinnacle, configuration in non-PnP mode allows
+ use of the IDE and joystick peripherals on the card as well; these
+ do not show up when the card is in PnP mode. Specifying zero for any
+ resource of a device will disable the device. If you are running the
+ card in PnP mode, you must say N here and use isapnptools to
+ configure the card's resources.
MSND Pinnacle config port
CONFIG_MSNDPIN_CFG
- This is the port which the Pinnacle and Fiji uses to configure
- the card's resources when not in PnP mode. If your card is in
- PnP mode, then be sure to say N to the previous option,
- CONFIG_MSNDPIN_NONPNP.
+ This is the port which the Pinnacle and Fiji uses to configure the
+ card's resources when not in PnP mode. If your card is in PnP mode,
+ then be sure to say N to the previous option, "MSND Pinnacle Non-PnP
+ Mode".
MSND buffer size (kB)
CONFIG_MSND_FIFOSIZE
Configures the size of each audio buffer, in kilobytes, for
recording and playing in the MultiSound drivers (both the Classic
- and Pinnacle). Larger values reduce the chance of data overruns at
+ and Pinnacle). Larger values reduce the chance of data overruns at
the expense of overall latency. If unsure, use the default.
/dev/dsp and /dev/audio support
CONFIG_SOUND_AUDIO
- Answering N disables /dev/dsp and /dev/audio, the A/D and D/A
- converter devices. Answer N only if you know you will not need
- the option. They are usually required. Answer Y.
+ If you say Y here, you will get the /dev/dsp and /dev/audio devices;
+ these are the analog-digital and digital-analog converter devices
+ and are very useful, so say Y.
MIDI interface support
CONFIG_SOUND_MIDI
Answering N disables /dev/midixx devices and access to any MIDI
ports using /dev/sequencer and /dev/music. This option also affects
- any MPU401 and/or General MIDI compatible devices. Answer Y.
+ any MPU401 and/or General MIDI compatible devices. Answer Y.
FM synthesizer (YM3812/OPL-3) support
CONFIG_SOUND_YM3812
@@ -8578,14 +8854,14 @@
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.
+ 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.
SB32/AWE support
CONFIG_AWE32_SYNTH
@@ -8623,7 +8899,7 @@
Audio Excel DSP 16 (MSS emulation)
CONFIG_AEDSP16_MSS
Answer Y if you want your audio card to emulate Microsoft Sound
- System. You should then say Y to "Microsoft Sound System support"
+ System. You should then say Y to "Microsoft Sound System support"
and say N to "Audio Excel DSP 16 (SBPro emulation)".
Audio Excel DSP 16 (SBPro emulation)
@@ -8644,6 +8920,10 @@
This driver differs slightly from OSS/Free, so PLEASE READ
Documentation/sound/es1370.
+Joystick support at boot time
+CONFIG_SOUND_ES1370_JOYPORT_BOOT
+ Say Y here to use the joystick port of your sound card.
+
Ensoniq ES1371 based PCI sound cards
CONFIG_SOUND_ES1371
Say Y or M if you have a PCI sound card utilizing the Ensoniq
@@ -8663,6 +8943,25 @@
differs slightly from OSS/Free, so PLEASE READ
Documentation/sound/sonicvibes.
+Are you using a crosscompiler
+CONFIG_CROSSCOMPILE
+ Say Y here if you are compiling the kernel on a different
+ architecture than the one it is intended to run on.
+
+Build fp exception handler module
+CONFIG_MIPS_FPE_MODULE
+ Build the floating point exception handler module. This option is
+ only useful for people working on the floating point exception
+ handler. If you don't, say N.
+
+Remote GDB kernel debugging
+CONFIG_REMOTE_DEBUG
+ If you say Y here, it will be possible to remotely debug the MIPS
+ kernel using gdb. This enlarges your kernel image disk size by
+ several megabytes and requires a machine with more than 16 MB,
+ better 32 MB RAM to avoid excessive linking time. This is only
+ useful for kernel hackers. If unsure, say N.
+
Magic System Request Key support
CONFIG_MAGIC_SYSRQ
If you say Y here, you will have some control over the system even
@@ -8682,10 +8981,10 @@
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 a program like lynx or netscape.)
+ 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 a program like lynx or netscape.)
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
@@ -8748,7 +9047,7 @@
line with two B-channels, 4B supports two ISDN lines. For running
this card, additional firmware is necessary, which has to be
downloaded into the card using a utility which is distributed
- separately. See Documentation/isdn/README and README.icn for more
+ separately. See Documentation/isdn/README and README.icn for more
information.
If you want to compile this as a module ( = code which can be
@@ -8785,104 +9084,116 @@
HiSax Support for Teles 16.0/8.0
CONFIG_HISAX_16_0
- This enables HiSax support for the Teles ISDN-cards S0-16.0,
- S0-8 and many compatibles.
- See Documentation/isdn/README.HiSax on how to configure it
- using the different cards, a different D-channel protocol, or
- non-standard IRQ/port/shmem settings.
+ This enables HiSax support for the Teles ISDN-cards S0-16.0, S0-8
+ and many compatibles.
+
+ See Documentation/isdn/README.HiSax on how to configure it using the
+ different cards, a different D-channel protocol, or non-standard
+ IRQ/port/shmem settings.
HiSax Support for Teles 16.3 or PNP or PCMCIA
CONFIG_HISAX_16_3
- This enables HiSax support for the Teles ISDN-cards S0-16.3
- the Teles/Creatix PnP and the Teles PCMCIA.
- See Documentation/isdn/README.HiSax on how to configure it
- using the different cards, a different D-channel protocol, or
- non-standard IRQ/port settings.
+ This enables HiSax support for the Teles ISDN-cards S0-16.3 the
+ Teles/Creatix PnP and the Teles PCMCIA.
+
+ See Documentation/isdn/README.HiSax on how to configure it using the
+ different cards, a different D-channel protocol, or non-standard
+ IRQ/port settings.
HiSax Support for Teles 16.3c
CONFIG_HISAX_TELES3C
This enables HiSax support for the Teles ISDN-cards 16.3c.
- See Documentation/isdn/README.HiSax on how to configure it
- using the different cards, a different D-channel protocol, or
- non-standard IRQ/port settings.
+
+ See Documentation/isdn/README.HiSax on how to configure it using the
+ different cards, a different D-channel protocol, or non-standard
+ IRQ/port settings.
HiSax Support for AVM A1 (Fritz)
CONFIG_HISAX_AVM_A1
This enables HiSax support for the AVM A1 (aka "Fritz").
- See Documentation/isdn/README.HiSax on how to configure it
- using the different cards, a different D-channel protocol, or
- non-standard IRQ/port settings.
+
+ See Documentation/isdn/README.HiSax on how to configure it using the
+ different cards, a different D-channel protocol, or non-standard
+ IRQ/port settings.
HiSax Support for Elsa ISA cards
CONFIG_HISAX_ELSA
- This enables HiSax support for the Elsa Mircolink ISA cards,
- for the Elsa Quickstep series cards and Elsa PCMCIA.
- See Documentation/isdn/README.HiSax on how to configure it
- using the different cards, a different D-channel protocol, or
- non-standard IRQ/port settings.
+ This enables HiSax support for the Elsa Mircolink ISA cards, for the
+ Elsa Quickstep series cards and Elsa PCMCIA.
+
+ See Documentation/isdn/README.HiSax on how to configure it using the
+ different cards, a different D-channel protocol, or non-standard
+ IRQ/port settings.
HiSax Support for ITK ix1-micro Revision 2
CONFIG_HISAX_IX1MICROR2
This enables HiSax support for the ITK ix1-micro Revision 2 card.
- See Documentation/isdn/README.HiSax on how to configure it
- using the different cards, a different D-channel protocol, or
- non-standard IRQ/port settings.
+
+ See Documentation/isdn/README.HiSax on how to configure it using the
+ different cards, a different D-channel protocol, or non-standard
+ IRQ/port settings.
HiSax Support for Eicon.Diehl Diva cards
CONFIG_HISAX_DIEHLDIVA
- This enables HiSax support for the Eicon.Diehl Diva none PRO versions
- passive ISDN cards.
+ This enables HiSax support for the Eicon.Diehl Diva none PRO
+ versions passive ISDN cards.
- See Documentation/isdn/README.HiSax on how to configure it
- using the different cards, a different D-channel protocol, or
- non-standard IRQ/port settings.
+ See Documentation/isdn/README.HiSax on how to configure it using the
+ different cards, a different D-channel protocol, or non-standard
+ IRQ/port settings.
HiSax Support for ASUSCOM cards
CONFIG_HISAX_ASUSCOM
This enables HiSax support for the AsusCom and their OEM versions
passive ISDN cards.
- See Documentation/isdn/README.HiSax on how to configure it
- using the different cards, a different D-channel protocol, or
- non-standard IRQ/port settings.
+ See Documentation/isdn/README.HiSax on how to configure it using the
+ different cards, a different D-channel protocol, or non-standard
+ IRQ/port settings.
HiSax Support for TELEINT cards
CONFIG_HISAX_TELEINT
This enables HiSax support for the TELEINT SA1 semiactiv ISDN card.
- See Documentation/isdn/README.HiSax on how to configure it
- using the different cards, a different D-channel protocol, or
- non-standard IRQ/port settings.
+
+ See Documentation/isdn/README.HiSax on how to configure it using the
+ different cards, a different D-channel protocol, or non-standard
+ IRQ/port settings.
HiSax Support for Sedlbauer speed card/win-star
CONFIG_HISAX_SEDLBAUER
This enables HiSax support for the Sedlbauer passive ISDN cards.
- See Documentation/isdn/README.HiSax on how to configure it
- using the different cards, a different D-channel protocol, or
- non-standard IRQ/port settings.
+
+ See Documentation/isdn/README.HiSax on how to configure it using the
+ different cards, a different D-channel protocol, or non-standard
+ IRQ/port settings.
HiSax Support for USR Sportster internal TA
CONFIG_HISAX_SPORTSTER
This enables HiSax support for the USR Sportster internal TA card.
+
See Documentation/isdn/README.HiSax on how to configure it using a
different D-channel protocol, or non-standard IRQ/port settings.
HiSax Support for MIC card
CONFIG_HISAX_MIC
- This enables HiSax support for the ITH MIC card. See
- Documentation/isdn/README.HiSax on how to configure it using a
+ This enables HiSax support for the ITH MIC card.
+
+ See Documentation/isdn/README.HiSax on how to configure it using a
different D-channel protocol, or non-standard IRQ/port settings.
HiSax Support for NETjet card
CONFIG_HISAX_NETJET
This enables HiSax support for the NetJet from Traverse
- Technologies. See Documentation/isdn/README.HiSax on how to
- configure it using a different D-channel protocol, or non-standard
- IRQ/port settings.
+ Technologies.
+
+ See Documentation/isdn/README.HiSax on how to configure it using a
+ different D-channel protocol, or non-standard IRQ/port settings.
HiSax Support for Niccy PnP/PCI card
CONFIG_HISAX_NICCY
- This enables HiSax support for the Dr. Neuhaus Niccy PnP or PCI. See
- Documentation/isdn/README.HiSax on how to configure it using a
+ This enables HiSax support for the Dr. Neuhaus Niccy PnP or PCI.
+
+ See Documentation/isdn/README.HiSax on how to configure it using a
different D-channel protocol, or non-standard IRQ/port settings.
HiSax Support for Am7930 (EXPERIMENTAL)
@@ -8903,10 +9214,10 @@
CONFIG_DE_AOC
If you want that the HiSax hardware driver sends messages to the
upper level of the isdn code on each AOCD (Advice Of Charge, During
- the call -- transmission of the fee information during a call) and on
- each AOCE (Advice Of Charge, at the End of the call -- transmission
- of fee information at the end of the call), say Y here. This works
- only in Germany.
+ the call -- transmission of the fee information during a call) and
+ on each AOCE (Advice Of Charge, at the End of the call --
+ transmission of fee information at the end of the call), say Y here.
+ This works only in Germany.
Support for Australian Microlink service (not for std. EURO)
CONFIG_HISAX_ML
@@ -8935,7 +9246,7 @@
This enables support for the PCBIT ISDN-card. This card is
manufactured in Portugal by Octal. For running this card, additional
firmware is necessary, which has to be downloaded into the card
- using a utility which is distributed separately. See
+ using a utility which is distributed separately. See
Documentation/isdn/README and Documentation/isdn/README.pcbit for
more information.
@@ -8950,7 +9261,7 @@
driver currently builds only in a modularized version ( = code which
can be inserted in and removed from the running kernel whenever you
want, details in Documentation/modules.txt); the module will be
- called sc.o. See Documentation/isdn/README.sc and
+ called sc.o. See Documentation/isdn/README.sc and
http://www.spellcast.com for more information (to browse the WWW,
you need to have access to a machine on the Internet that has a
program like lynx or netscape).
@@ -8965,7 +9276,7 @@
interface for this card is provided. In order to use this card,
additional firmware is necessary, which has to be downloaded into
the card using a utility which is distributed separately. Please
- read the file Documentation/isdn/README.avmb1.
+ read the file Documentation/isdn/README.avmb1.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -8975,7 +9286,7 @@
Verbose reason code reporting (kernel size +=7K)
CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON
If you say Y here, the AVM B1 driver will give verbose reasons for
- disconnecting. This will increase the size of the kernel by 7K. If
+ disconnecting. This will increase the size of the kernel by 7 KB. If
unsure, say Y.
IBM Active 2000 support (EXPERIMENTAL)
@@ -9030,21 +9341,21 @@
#
Amiga support
CONFIG_AMIGA
- This option enables support for the Amiga series of computers. If
+ This option enables support for the Amiga series of computers. If
you plan to use this kernel on an Amiga, say Y here and browse the
material available in Documentation/m68k; otherwise say N.
Atari support
CONFIG_ATARI
This option enables support for the 68000-based Atari series of
- computers (including the TT, Falcon and Medusa). If you plan to use
+ computers (including the TT, Falcon and Medusa). If you plan to use
this kernel on an Atari, say Y here and browse the material
available in Documentation/m68k; otherwise say N.
Hades support
CONFIG_HADES
- This option enables support for the Hades Atari clone. If you plan to
- use this kernel on a Hades, say Y here; otherwise say N.
+ This option enables support for the Hades Atari clone. If you plan
+ to use this kernel on a Hades, say Y here; otherwise say N.
Macintosh support
CONFIG_MAC
@@ -9060,49 +9371,49 @@
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.
+ 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).
+ 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).
+ 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
+ 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
+ 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
If you anticipate running this kernel on a computer with a MC68060
- processor, say Y. Otherwise, say N.
+ processor, say Y. Otherwise, say N.
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
+ 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
+ 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
- This gives you access to some advanced options for the CPU. The
+ This gives you access to some advanced options for the CPU. The
defaults should be fine for most users, but these options may make
it possible for you to improve performance somewhat if you know what
- you are doing. Most users should say N to this question.
+ you are doing. Most users should say N to this question.
Use read-modify-write instructions
CONFIG_RMW_INSNS
@@ -9122,7 +9433,7 @@
This enables support for automatic identification of Amiga expansion
cards that obey the AutoConfig(tm) specification.
Say Y if you want your expansion cards to be identified on bootup;
- it will enlarge your kernel by about 10KB. The identification
+ it will enlarge your kernel by about 10 KB. The identification
information is also available through /proc/zorro (say Y to
"/proc filesystem support"!).
@@ -9132,13 +9443,13 @@
Amiga OCS chipset support
CONFIG_AMIFB_OCS
This enables support for the original Agnus and Denise video chips,
- found in the Amiga 1000 and most A500's and A2000's. If you intend
+ found in the Amiga 1000 and most A500's and A2000's. If you intend
to run Linux on any of these systems, say Y; otherwise say N.
Amiga ECS chipset support
CONFIG_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
+ 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.
@@ -9146,31 +9457,31 @@
CONFIG_AMIFB_AGA
This enables support for the Advanced Graphics Architecture (also
known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
- and CD32. If you intend to run Linux on any of these systems, say Y;
+ and CD32. If you intend to run Linux on any of these systems, say Y;
otherwise say N.
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
+ 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
- Include support in the kernel for the DMI Resolver graphics card. If
+ Include support in the kernel for the DMI Resolver graphics card. If
you have one, say Y; otherwise, say N.
A2410 support
CONFIG_GSP_A2410
Include support in the kernel for the Commodore/University of Lowell
- A2410 graphics card. If you have one, say Y; otherwise, say N.
+ A2410 graphics card. If you have one, say Y; otherwise, say N.
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
+ 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
@@ -9219,13 +9530,13 @@
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). The module will be called
- acsi_slm.o. Be warned: the driver needs much ST-RAM and can cause
+ 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
+ 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
@@ -9233,19 +9544,19 @@
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
+ 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.
- This driver does NOT work for the T-Rex series of accelerators from
- TekMagic and GVP-M.
+ If you have a Great Valley Products Series II SCSI controller,
+ answer Y. Also say Y if you have a later model of GVP SCSI
+ controller (such as the GVP A4008 or a Combo board). Otherwise,
+ answer 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
@@ -9255,36 +9566,36 @@
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.
+ accelerator board and the optional Cyberstorm SCSI controller,
+ answer Y. Otherwise, say N.
Cyberstorm II SCSI support
CONFIG_CYBERSTORMII_SCSI
If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
- and the optional Cyberstorm SCSI controller, say Y. Otherwise, say
- N.
+ and the optional Cyberstorm SCSI controller, say Y. Otherwise,
+ answer N.
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.
+ and want to use the onboard SCSI controller, say Y. Otherwise,
+ answer 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,
+ 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
say N.
Blizzard PowerUP 603e+ SCSI support
CONFIG_BLZ603EPLUS_SCSI
If you have an Amiga 1200 with a Phase5 Blizzard PowerUP 603e+
- accelerator, say Y. Otherwise, say N.
+ accelerator, say Y. Otherwise, say N.
Fastlane SCSI support
CONFIG_FASTLANE_SCSI
If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
- one in the near future, say Y to this question. Otherwise, say N.
+ one in the near future, say Y to this question. Otherwise, say N.
Atari native SCSI support
CONFIG_ATARI_SCSI
@@ -9294,7 +9605,7 @@
available as a module ( = code which can be inserted in and removed
from the running kernel whenever you want). The module is called
atari_scsi.o. If you want to compile it as a module, say M here and
- read Documentation/modules.txt. This driver supports both styles of
+ 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).
@@ -9316,7 +9627,7 @@
Ariadne support
CONFIG_ARIADNE
- If you have a Village Tronic Ariadne Ethernet adapter, say Y.
+ 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
@@ -9326,7 +9637,7 @@
Ariadne II support
CONFIG_ARIADNE2
- If you have a Village Tronic Ariadne II Ethernet adapter, say Y.
+ If you have a VillageTronics Ariadne II Ethernet adapter, say Y.
Otherwise, say N.
This driver is also available as a module ( = code which can be
@@ -9336,7 +9647,7 @@
A2065 support
CONFIG_A2065
- If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
+ 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
@@ -9346,7 +9657,7 @@
Hydra support
CONFIG_HYDRA
- If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
+ 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
@@ -9374,7 +9685,7 @@
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.
+ 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).
@@ -9383,7 +9694,7 @@
Amiga mouse support
CONFIG_AMIGAMOUSE
- If you want to be able to use an Amiga mouse in Linux, say Y.
+ If you want to be able to use an Amiga mouse in Linux, say Y.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -9393,13 +9704,13 @@
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
+ 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.
+ 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.
+ 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).
@@ -9426,7 +9737,7 @@
LAN) and like to use them under Linux, say Y. All built-in SCC's are
supported (TT, MegaSTE, Falcon), and also the ST-ESCC. If you have
two connectors for channel A (Serial2 and LAN), they are visible as
- two separate devices.
+ two separate devices.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -9435,9 +9746,9 @@
Atari SCC serial DMA support
CONFIG_ATARI_SCC_DMA
- This enables DMA support for receiving data on channel A of the
- SCC. If you have a TT you may say Y here and read
- drivers/char/atari_SCC.README. All other users should say N here,
+ This enables DMA support for receiving data on channel A of the SCC.
+ If you have a TT you may say Y here and read
+ drivers/char/atari_SCC.README. All other users should say N here,
because only the TT has SCC-DMA, even if your machine keeps claiming
so at boot time.
@@ -9452,19 +9763,19 @@
Atari DSP56k Digital Signal Processor support
CONFIG_ATARI_DSP56K
- If you want to be able to use the DSP56001 in Falcons, say Y.
- This driver is still experimental, and if you don't know what it is,
- or if you don't have this processor, just say N.
+ If you want to be able to use the DSP56001 in Falcons, say Y. This
+ driver is still experimental, and if you don't know what it is, or
+ if you don't have this processor, just 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
+ 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.
+ If you want to use your Amiga's built-in serial port in Linux,
+ answer Y.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you
@@ -9478,8 +9789,8 @@
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,
+ answer Y.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
@@ -9489,8 +9800,8 @@
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,
+ 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
@@ -9501,41 +9812,40 @@
MSDOS partition support
CONFIG_MSDOS_PARTITION
This option enables support for using hard disks that were
- partitioned on an MS-DOS system. This may be useful if you are
+ partitioned on an MS-DOS system. This may be useful if you are
sharing a hard disk between i386 and m68k Linux boxes, for example.
Say Y if you need this feature; users who are only using their
system-native partitioning scheme can say N here.
Processor Type
CONFIG_6xx
- There are two types of PowerPC chips supported. The more common
+ There are two types of PowerPC chips supported. The more common
types (601,603,604,740,750) and the embedded versions (821 and 860).
- Unless you are building a kernel for one of the embedded boards using
- the 821 or 860 choose 6xx.
+ Unless you are building a kernel for one of the embedded boards
+ using the 821 or 860 choose 6xx.
Machine Type
CONFIG_PMAC
Linux currently supports several different kinds of PowerPC-based
- machines: Apple Power Macintoshes and clones (such as the
- Motorola Starmax series), PReP (PowerPC Reference Platform) machines
- such as the Motorola PowerStack, Amiga Power-Up systems (APUS), CHRP
- and the embedded MBX boards from Motorola. Currently, a single
- kernel binary only supports one type or the other. However, there is
- very early work on support for CHRP, PReP and PowerMac's from a
- single binary.
+ machines: Apple Power Macintoshes and clones (such as the Motorola
+ Starmax series), PReP (PowerPC Reference Platform) machines such as
+ the Motorola PowerStack, Amiga Power-Up systems (APUS), CHRP and the
+ embedded MBX boards from Motorola. Currently, a single kernel binary
+ only supports one type or the other. However, there is very early
+ work on support for CHRP, PReP and PowerMac's from a single binary.
Support for Open Firmware device tree in /proc
CONFIG_PROC_DEVICETREE
This option adds a device-tree directory under /proc which contains
an image of the device tree that the kernel copies from Open
- Firmware. If unsure, say Y here.
+ Firmware. If unsure, say Y here.
MESH (Power Mac internal SCSI) support
CONFIG_SCSI_MESH
Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
- other Power Macintoshes do). Say Y to include support for this SCSI
- adaptor. This driver is also available as a module called mesh.o
+ other Power Macintoshes do). Say Y to include support for this SCSI
+ adaptor. This driver is also available as a module called mesh.o
( = code which can be inserted in and removed from the running
kernel whenever you want). If you want to compile it as a module,
say M here and read Documentation/modules.txt.
@@ -9545,18 +9855,18 @@
On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
drives a bus which is entirely internal to the machine (such as the
7500, 7600, 8500, etc.), the MESH is capable of synchronous
- operation at up to 10MB/s. On machines where the SCSI bus
+ operation at up to 10 MB/s. On machines where the SCSI bus
controlled by the MESH can have external devices connected, it is
- usually rated at 5MB/s. 5 is a safe value here unless you know the
- MESH SCSI bus is internal only; in that case you can say 10. Say 0
+ usually rated at 5 MB/s. 5 is a safe value here unless you know the
+ MESH SCSI bus is internal only; in that case you can say 10. Say 0
to disable synchronous operation.
53C94 (Power Mac external SCSI) support
CONFIG_SCSI_MAC53C94
On Power Macintoshes (and clones) with two SCSI buses, the external
- SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
+ SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
machines which only have one SCSI bus, such as the 7200, also use
- the 53C94. Say Y to include support for the 53C94.
+ the 53C94. Say Y to include support for the 53C94.
This driver is also available as a module called mac53c94.o ( = code
which can be inserted in and removed from the running kernel
@@ -9567,7 +9877,7 @@
CONFIG_MACE
Power Macintoshes and clones with Ethernet built-in on the
motherboard will usually use a MACE (Medium Access Control for
- Ethernet) interface. Say Y to include support for the MACE chip.
+ Ethernet) interface. Say Y to include support for the MACE chip.
BMAC (G3 ethernet) support
CONFIG_BMAC
@@ -9600,7 +9910,7 @@
RadioTrack II driver below.
In order to control your radio card, you will need to use programs
- that are compatible with the Video for Linux API. Information on
+ that are compatible with the Video for Linux API. Information on
this API and pointers to "v4l" programs may be found on the WWW at
http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
you need to have access to a machine on the Internet that has a
@@ -9614,7 +9924,7 @@
RadioTrack i/o port
CONFIG_RADIO_RTRACK_PORT
- Enter either 0x30f or 0x20f here. The card default is 0x30f, if you
+ Enter either 0x30f or 0x20f here. The card default is 0x30f, if you
haven't changed the jumper setting on the card.
AIMSlab RadioTrack II support
@@ -9623,7 +9933,7 @@
port address below.
In order to control your radio card, you will need to use programs
- that are compatible with the Video for Linux API. Information on
+ that are compatible with the Video for Linux API. Information on
this API and pointers to "v4l" programs may be found on the WWW at
http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
you need to have access to a machine on the Internet that has a
@@ -9636,7 +9946,7 @@
RadioTrack II i/o port
CONFIG_RADIO_RTRACK2_PORT
- Enter either 0x30c or 0x20c here. The card default is 0x30c, if you
+ Enter either 0x30c or 0x20c here. The card default is 0x30c, if you
haven't changed the jumper setting on the card.
Aztech/Packard Bell Radio
@@ -9645,7 +9955,7 @@
in the port address below.
In order to control your radio card, you will need to use programs
- that are compatible with the Video for Linux API. Information on
+ that are compatible with the Video for Linux API. Information on
this API and pointers to "v4l" programs may be found on the WWW at
http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
you need to have access to a machine on the Internet that has a
@@ -9658,8 +9968,8 @@
Aztech/Packard Bell radio card i/o port
CONFIG_RADIO_AZTECH_PORT
- Enter either 0x350 or 0x358 here. The card default is 0x350, if you
- haven't changed the setting of jumper JP3 on the card. Removing the
+ Enter either 0x350 or 0x358 here. The card default is 0x350, if you
+ haven't changed the setting of jumper JP3 on the card. Removing the
jumper sets the card to 0x358.
SF16FMI Radio
@@ -9668,7 +9978,7 @@
in the port address below.
In order to control your radio card, you will need to use programs
- that are compatible with the Video for Linux API. Information on
+ that are compatible with the Video for Linux API. Information on
this API and pointers to "v4l" programs may be found on the WWW at
http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
you need to have access to a machine on the Internet that has a
@@ -9689,7 +9999,7 @@
in the port address below.
In order to control your radio card, you will need to use programs
- that are compatible with the Video for Linux API. Information on
+ that are compatible with the Video for Linux API. Information on
this API and pointers to "v4l" programs may be found on the WWW at
http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
you need to have access to a machine on the Internet that has a
@@ -9710,7 +10020,7 @@
in the port address below.
In order to control your radio card, you will need to use programs
- that are compatible with the Video for Linux API. Information on
+ that are compatible with the Video for Linux API. Information on
this API and pointers to "v4l" programs may be found on the WWW at
http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
you need to have access to a machine on the Internet that has a
@@ -9769,17 +10079,17 @@
CPU Optimization
CONFIG_CPU_ARM2
- This selects the processor type of your CPU. This is only used to
+ This selects the processor type of your CPU. This is only used to
determine C compiler optimization options, and can affect the
- compatibility of the kernel on other processors. If you specify
- ARM6, the kernel should work on all 32-bit processors. If you
+ compatibility of the kernel on other processors. If you specify
+ ARM6, the kernel should work on all 32-bit processors. If you
specify ARM2, ARM250 or ARM3, it should work on all 26-bit
- processors. If you're not sure, set it to "None".
+ processors. If you're not sure, set it to "None".
ARM System type
CONFIG_ARCH_ARC
- This selects what ARM system you wish to build the kernel for. It
- also selects to some extent the CPU type. If you are unsure what
+ This selects what ARM system you wish to build the kernel for. It
+ also selects to some extent the CPU type. If you are unsure what
to set this option to, please consult any information supplied with
your system.
@@ -9795,51 +10105,6 @@
it will give useful debugging/error results. If you don't debug the
kernel, you can say N.
-VIDC Sound
-CONFIG_VIDC_SOUND
- Say 'Y' here for ARM systems with the VIDC video controller and 16-bit
- Linear sound DACs. If unsure, say N.
-
-Backward compatibility mode for Xpmac
-CONFIG_FB_COMPAT_XPMAC
- If you use the Xpmac X server (common with mklinux), you'll need
- to enable this to use X. You should consider changing to XFree86
- which includes a server that supports the frame buffer device
- directly (XF68_FBDev).
-
-Support for PowerMac keyboard
-CONFIG_MAC_KEYBOARD
- This option allows you to use an ADB keyboard attached to your
- machine. Note that this disables any other (ie. PS/2) keyboard
- support, even if your machine is physically capable of using both
- at the same time.
-
- If you use an ADB keyboard (4 pin connector), say Y here.
- If you use a PS/2 keyboard (6 pin connector), say N here.
-
-Support for PowerMac floppy
-CONFIG_MAC_FLOPPY
- If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
- floppy controller, say Y here. Most commonly found in PowerMacs.
-
-Support for PowerMac serial ports
-CONFIG_MAC_SERIAL
- If you have Macintosh style serial ports (8 pin mini-DIN), this
- is the driver for them. If you also have regular serial ports
- and enable the driver for them, you can't currently use the
- serial console feature.
-
-Support for PowerMac ADB mouse
-CONFIG_ADBMOUSE
- If you have an ADB mouse (4 pin connector) as is common on
- Macintoshes, say Y here.
-
-Winbond SL82c105 support
-CONFIG_BLK_DEV_SL82C105
- If you have a Winbond SL82c105 IDE controller, say Y here to
- enable special configuration for this chip. This is common
- on various CHRP motherboards, but could be used elsewhere.
- If in doubt, say Y.
#
# A couple of things I keep forgetting:
# capitalize: AppleTalk, Ethernet, DMA, FTP, Internet, Intel, IRQ,
@@ -9891,13 +10156,13 @@
# LocalWords: RTNETLINK mknod xos MTU lwared Macs mac netatalk macs cs Wolff
# LocalWords: dartmouth flowerpt MultiMaster FlashPoint tudelft etherexpress
# LocalWords: ICL EtherTeam ETH IDESCSI TXC SmartRAID SmartCache httpd sjc dlp
-# LocalWords: thesphere TwoServers BOOTP DHCP ncpfs BPQETHER BPQ chipsets MG
+# LocalWords: thesphere TwoServers BOOTP DHCP ncpfs BPQETHER BPQ MG HIPPI cern
# LocalWords: bsd comp SPARCstation le SunOS ie Gracilis PackeTwin PT pt LU FX
# LocalWords: FX TEAC CR LCS mS ramdisk IDETAPE cmd fperllo encis tcfs unisa
# LocalWords: Vertos Genoa Funai hsfs NCP NetWare tgz APM apm ioctls UltraLite
# LocalWords: TravelMate CDT LCD backlight VC RPC Mips AXP barlow cdrecord pg
# LocalWords: PMAX MILO Alphas Multia Tseng linuxelf endian mipsel mips drv HT
-# LocalWords: KERNELD kerneld callouts AdvanSys advansys Admin WDT DataStor EP
+# LocalWords: kerneld callouts AdvanSys advansys Admin WDT DataStor EP verden
# LocalWords: wdt hdb hdc bugfix SiS vlb Acculogic CSA DTC dtc Holtek ht QDI
# LocalWords: QD qd UMC umc ALI ali lena fnet fr azstarnet axplinux cdr fb MDA
# LocalWords: Avanti XL AlphaStations Jensen DECpc AXPpci UDB Cabriolet MCA RC
@@ -9948,7 +10213,7 @@
# 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: Village Tronic ATARILANCE RieblCard PAMCard VME MFP sangoma LAPB
+# 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
@@ -9971,7 +10236,7 @@
# LocalWords: zorro CAPI AVMB capi avmb VP SYN syncookies EM em pc Ethertalk
# LocalWords: Dayna DL Daynatalk LT PhoneNET ATB Daystar queueing CMDS SCBs ls
# LocalWords: SCB STATS Thinnet ThunderLAN TLAN Netelligent NetFlex tlan james
-# LocalWords: caldera Preload dcache Preloading slowdowns schoebel uni NBD nbd
+# LocalWords: caldera Preload Preloading slowdowns schoebel uni NBD nbd prog
# LocalWords: stuttgart rdist TRANS hostnames mango jukeboxes ESS userland PD
# LocalWords: hardlinked NAMETRANS env mtab fstab umount nologin runlevel gid
# LocalWords: transname filespace adm Nodename hostname uname Kernelname bootp
@@ -10033,6 +10298,19 @@
# LocalWords: CyberVision Cirrus PowerBooks Topcat SBUS CGsix TurboGX BWtwo SS
# LocalWords: CGthree TCX unswapable vfb fbcon hicolor truecolor AFB ILBM SOC
# LocalWords: IPLAN gracilis Fibre SBus SparcSTORAGE SV jnewbigin swin QNX qnx
-# LocalWords: PTY PTYS ptyxx ttyxx PTYs ssh sb Avance ALS pss
-# LocalWords: synth WaveFront MSND NONPNP AudioExcelDSP STRAM APUS CHRP MBX
-# LocalWords: PowerMac's BMAC radiotrack rtrack miropcm
+# LocalWords: PTY PTYS ptyxx ttyxx PTYs ssh sb Avance ALS pss pvv kerneli hd
+# LocalWords: synth WaveFront MSND NONPNP AudioExcelDSP STRAM APUS CHRP MBX Nx
+# LocalWords: PowerMac's BMAC radiotrack rtrack miropcm OFFBOARD HPT UDMA DVD
+# LocalWords: hpt fokus gmd Cyrix DXL SLC DLC NexGen MediaGX GXm IDT WinChip
+# LocalWords: MMX MII valkyrie mdacon vdolive VDOLive cuseeme CU hippi rrunner
+# LocalWords: SeeMe ipmasqadm juanjox ipmarkfw markfw TNCs Microdyne rhine lib
+# LocalWords: libc jsX gamepad gameport CHF FCS FPGaming MadCatz ASSASIN GrIP
+# LocalWords: Assasin gamepads GamePad PDPI gamecards gamecard WingMan BSP WCS
+# LocalWords: ThunderPad CyberMan SideWinder ThrustMaster DirectConnect NES XF
+# LocalWords: Millenium SNES PSX Multisystem Nintendo PlayStation Amstrad CPC
+# LocalWords: Sega TurboGraFX Steffen Schwenke Multiststem PDIF FIFOSIZE EPLUS
+# LocalWords: PowerUP RoadRunner tahallah dos functionkey setterm imladris Woz
+# LocalWords: PowerMacs Winbond Algorithmics ALGOR algor ECOFF IRIX SGI SGI's
+# LocalWords: gfx virtualized Xpmac mklinux XFree FBDev Woodhouse mvhi Seeq fp
+# LocalWords: SGISEEQ HIgh ADB ADBMOUSE crosscompiler CROSSCOMPILE FPE GDB gdb
+# LocalWords: JOYPORT rp spoofing DawiControl NOGENSUPP EEPROM HSSI
FUNET's LINUX-ADM group, linux-adm@nic.funet.fi
TCL-scripts by Sam Shen, slshen@lbl.gov