1 # Maintained by Axel Boldt (boldt@math.ucsb.edu)
3 # This version of the Linux kernel configuration help texts
4 # corresponds to the kernel versions 2.2.x.
6 # Translations of this file available on the WWW:
8 # - Japanese, by Tetsuyasu YAMADA (tetsu@cauchy.nslab.ntt.co.jp), at
9 # http://jf.gee.kyoto-u.ac.jp/JF/JF-ftp/euc/Configure.help.euc
10 # - Russian, by kaf@linux.nevod.perm.su, at
11 # http://nevod.perm.su/service/linux/doc/kernel/Configure.help
12 # - French, by David Bourgin (dbourgin@wsc.com), at
13 # http://www.linux-kheops.com/traduc/kernels/
14 # - Spanish, by Carlos Perelló Marín (fperllo@ehome.encis.es), at
15 # http://visar.csustan.edu/~carlos/
16 # - Italian, by Alessandro Rubini (rubini@linux.it), at
17 # ftp://ftp-pavia1.linux.it/pub/linux/Configure.help
18 # - Polish, by Cezar Cichocki (cezar@cs.net.pl), at
19 # http://www.cs.net.pl/~cezar/Kernel
20 # - German, by Jörg Strebel (jstrebel@suse.de) and Karl Eichwalder
21 # (ke@suse.de), at http://www.suse.de/~ke/kernel/Configure.de.help.gz
23 # Information about what a kernel is, what it does, how to patch and
24 # compile it and much more is contained in the Kernel-HOWTO, available
25 # via FTP (user: anonymous) from metalab.unc.edu in the directory
26 # /pub/Linux/docs/HOWTO. Before you start compiling, make sure that
27 # you have the necessary versions of all programs and libraries
28 # required to compile and run this kernel; they are listed in the file
29 # Documentation/Changes. Make sure to read the toplevel kernel README
32 # Format of this file: description<nl>variable<nl>help text<nl><nl>. If
33 # the question being documented is of type "choice", we list only the
34 # first occurring config variable. The help texts may contain empty
35 # lines, but every non-empty line must be indented two positions.
36 # Order of the help texts does not matter, however, no variable should
37 # be documented twice: if it is, only the first occurrence will be
38 # used by Configure. We try to keep the help texts of related variables
39 # close together. Lines starting with `#' are ignored. To be nice to
40 # menuconfig, limit your line length to 70 characters. Use emacs'
41 # kfill.el to edit and ispell.el to spell check this file or you lose.
43 # If you add a help text to this file, please try to be as gentle as
44 # possible. Don't use unexplained acronyms and generally write for the
45 # hypothetical ignorant but intelligent user who has just bought a PC,
46 # removed Windows, installed Linux and is now recompiling the kernel
47 # for the first time. Tell them what to do if they're unsure. Technical
48 # information should go in a README in the Documentation directory.
49 # Mention all the relevant READMEs and HOWTOs in the help text.
50 # Repetitions are fine since the help texts are not meant to be read
53 # All this was shamelessly stolen from several different sources. Many
54 # thanks to all the contributors. Feel free to use these help texts in
55 # your own kernel configuration tools. The texts are copyrighted (c)
56 # 1995-1999 by Axel Boldt and many others and are governed by the GNU
57 # General Public License.
59 Prompt for development and/or incomplete code/drivers
61 Some of the various things that Linux supports (such as network
62 drivers, filesystems, network protocols, etc.) can be in a state
63 of development where the functionality, stability, or the level of
64 testing is not yet high enough for general use. This is usually
65 known as the "alpha-test" phase amongst developers. If a feature is
66 currently in alpha-test, then the developers usually discourage
67 uninformed widespread use of this feature by the general public to
68 avoid "Why doesn't this work?" type mail messages. However, active
69 testing and use of these systems is welcomed. Just be aware that it
70 may not meet the normal level of reliability or it may fail to work
71 in some special cases. Detailed bug reports from people familiar
72 with the kernel internals are usually welcomed by the developers
73 (before submitting bug reports, please read the documents README,
74 MAINTAINERS, REPORTING_BUGS, Documentation/BUG-HUNTING, and
75 Documentation/oops-tracing.txt in the kernel source).
77 Unless you intend to help test and develop a feature or driver that
78 falls into this category, or you have a situation that requires
79 using these features you should probably say N here, which will
80 cause this configure script to present you with fewer choices. If
81 you say Y here, you will be offered the choice of using features or
82 drivers that are currently considered to be in the alpha-test phase.
84 Symmetric Multi Processing
86 This enables support for systems with more than one CPU. If you have
87 a system with only one CPU, like most personal computers, say N. If
88 you have a system with more than one CPU, say Y.
90 If you say N here, the kernel will run on single and multiprocessor
91 machines, but will use only one CPU of a multiprocessor machine. If
92 you say Y here, the kernel will run on many, but not all,
93 singleprocessor machines. On a singleprocessor machine, the kernel
94 will run faster if you say N here.
96 Note that if you say Y here and choose architecture "586" or
97 "Pentium" under "Processor family", the kernel will not work on 486
98 architectures. Similarly, multiprocessor kernels for the "PPro"
99 architecture may not work on all Pentium based boards.
101 People using multiprocessor machines who say Y here should also say
102 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
103 Management" code will be disabled if you say Y here.
105 See also: Documentation/SMP.txt, Documentation/smp.tex,
106 Documentation/smp.txt, and Documentation/IO-APIC.txt. Also see the
107 SMP-FAQ on the WWW at http://www.irisa.fr/prive/mentre/smp-faq/ (to
108 browse the WWW, you need to have access to a machine on the Internet
109 that has a program like lynx or netscape).
111 If you don't know what to do here, say N.
113 Kernel math emulation
114 CONFIG_MATH_EMULATION
115 Linux can emulate a math coprocessor (used for floating point
116 operations) if you don't have one. 486DX and Pentium processors have
117 a math coprocessor built in, 486SX and 386 do not, unless you added
118 a 487DX or 387, respectively. (The messages during boot time can
119 give you some hints here ["man dmesg"].) Everyone needs either a
120 coprocessor or this emulation.
122 If you don't have a math coprocessor, you need to say Y here; if you
123 say Y here even though you have a coprocessor, the coprocessor will
124 be used nevertheless. (This behavior can be changed with the kernel
125 command line option "no387", which comes handy if your coprocessor
126 is broken. Try "man bootparam" or see the documentation of your boot
127 loader (lilo or loadlin) about how to pass options to the kernel at
128 boot time. The lilo procedure is also explained in the SCSI-HOWTO,
129 available via FTP (user: anonymous) in
130 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.) This means that it is a
131 good idea to say Y here if you intend to use this kernel on
134 More information about the internals of the Linux math coprocessor
135 emulation can be found in arch/i386/math-emu/README.
137 If you are not sure, say Y; apart from resulting in a 45 KB bigger
138 kernel, it won't hurt.
140 Timer and CPU usage LEDs
142 If you define this option, the LEDs on your machine will be used
143 to provide useful information about your current system status.
145 If you are compiling a kernel for a NetWinder or EBSA-285, you
146 will be able to select which LEDs are active using the options
147 below. If you are compiling a kernel for the EBSA-110 however,
148 the red LED will simply flash regularly to indicate that the
149 system is still functional. It is still safe to say yes here if
150 you have a CATS system, but the driver will do nothing.
154 If you say yes here, one of the system LEDs (the green one on the
155 NetWinder or the amber one on the EBSA285) will flash regularly to
156 indicate that the system is still operational. This is mainly
157 useful to kernel hackers who are debugging unstable kernels.
161 If you say yes here, the red LED will be used to give a good real
162 time indication of CPU usage, by lighting whenever the idle task
163 is not currently executing.
165 Kernel FP software completion
167 This option is required for IEEE compliant floating point arithmetic
168 on the Alpha. The only time you would ever not say Y is to say M in
169 order to debug the code. Say Y unless you know what you are doing.
171 Normal PC floppy disk support
173 If you want to use the floppy disk drive(s) of your PC under Linux,
174 say Y. Information about this driver, especially important for IBM
175 Thinkpad users, is contained in drivers/block/README.fd. This file
176 also contains the location of the Floppy driver FAQ as well as
177 location of the fdutils package used to configure additional
178 parameters of the driver at run time.
180 This driver is also available as a module ( = code which can be
181 inserted in and removed from the running kernel whenever you want).
182 The module will be called floppy.o. If you want to compile it as a
183 module, say M here and read Documentation/modules.txt.
185 Support for PowerMac floppy
187 If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
188 floppy controller, say Y here. Most commonly found in PowerMacs.
192 Saying Y here will allow you to use a portion of your RAM memory as
193 a block device, so that you can make filesystems on it, read and
194 write to it and do all the other things that you can do with normal
195 block devices (such as hard drives). It is usually used to load and
196 store a copy of a minimal root file system off of a floppy into RAM
197 during the initial install of Linux.
199 Note that the kernel command line option "ramdisk=XX" is now
200 obsolete. For details, read Documentation/ramdisk.txt.
202 If you want to compile this as a module ( = code which can be
203 inserted in and removed from the running kernel whenever you want),
204 say M and read Documentation/modules.txt. The module will be called
207 Most normal users won't need the RAM disk functionality, and can
210 Initial RAM disk (initrd) support
211 CONFIG_BLK_DEV_INITRD
212 The initial RAM disk is a RAM disk that is loaded by the boot loader
213 (loadlin or lilo) and that is mounted as root before the normal boot
214 procedure. It is typically used to load modules needed to mount the
215 "real" root file system, etc. See Documentation/initrd.txt for
220 Saying Y here will allow you to use a regular file as a block
221 device; you can then create a file system on that block device and
222 mount it just as you would mount other block devices such as hard
223 drive partitions, CDROM drives or floppy drives.
225 This is useful if you want to check an ISO 9660 file system before
226 burning the CD, or if you want to use floppy images without first
227 writing them to floppy.
229 The loop device driver can also be used to "hide" a filesystem in a
230 disk partition, floppy, or regular file, either using encryption
231 (scrambling the data) or steganography (hiding the data in the low
232 bits of, say, a sound file). This is also safe if the file resides
233 on a remote file server. If you want to do this, you will first have
234 to acquire and install a kernel patch from
235 ftp://ftp.replay.com/pub/crypto/linux/all or
236 ftp://verden.pvv.org/pub/linux/kerneli/v2.1/, and then you need to
237 say Y to this option.
239 Note that alternative ways to use encrypted filesystems are provided
240 by the cfs package, which can be gotten via FTP (user: anonymous)
241 from ftp://ftp.replay.com/pub/crypto/disk/, and the newer tcfs
242 package, available at http://tcfs.dia.unisa.it/. You do not need to
243 say Y here if you want to use one of these. However, using cfs
244 requires saying Y to "NFS filesystem support" below while using tcfs
245 requires applying a kernel patch.
247 To use the loop device, you need the losetup utility and a recent
248 version of the mount program, both contained in the util-linux
249 package. The location and current version number of util-linux is
250 contained in the file Documentation/Changes.
252 Note that this loop device has nothing to do with the loopback
253 device used for network connections from the machine to itself.
255 If you want to compile this driver as a module ( = code which can be
256 inserted in and removed from the running kernel whenever you want),
257 say M here and read Documentation/modules.txt. The module will be
260 Most users will answer N here.
262 Network Block Device support
264 Saying Y here will allow your computer to be a client for network
265 block devices, i.e. it will be able to use block devices exported by
266 servers (mount filesystems on them etc.). Communication between
267 client and server works over TCP/IP networking, but to the client
268 program this is hidden: it looks like a regular local file access to
269 a block device special file such as /dev/nd0.
271 Network block devices also allows you to run a block-device in
272 userland (making server and client physically the same computer,
273 communicating using the loopback network device).
275 Read Documentation/nbd.txt for more information, especially about
276 where to find the server code, which runs in user space and does not
277 need special kernel support.
279 Note that this has nothing to do with the network file systems NFS
280 or Coda; you can say N here even if you intend to use NFS or Coda.
282 If you want to compile this driver as a module ( = code which can be
283 inserted in and removed from the running kernel whenever you want),
284 say M here and read Documentation/modules.txt. The module will be
289 Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
291 If you say Y here, you will use the full-featured IDE driver to
292 control up to eight IDE interfaces, each being able to serve a
293 "master" and a "slave" device, for a total of up to sixteen (16)
294 IDE disk/cdrom/tape/floppy drives. People with SCSI-only systems
297 Useful information about large (>540 MB) IDE disks, multiple
298 interfaces, what to do if IDE devices are not automatically
299 detected, sound card IDE ports, module support, and other topics, is
300 contained in Documentation/ide.txt. For detailed information about
301 hard drives, consult the Disk-HOWTO and the Multi-Disk-HOWTO,
302 available via FTP (user: anonymous) from
303 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
305 To fine-tune IDE drive/interface parameters for improved
306 performance, look for the hdparm package at
307 ftp://metalab.unc.edu/pub/Linux/kernel/patches/diskdrives/
309 If you want to compile this driver as a module ( = code which can be
310 inserted in and removed from the running kernel whenever you want),
311 say M here and read Documentation/modules.txt and
312 Documentation/ide.txt. The module will be called ide.o. Do not
313 compile this driver as a module if your root filesystem (the one
314 containing the directory /) is located on an IDE device.
316 If you have one or more IDE drives, say Y or M here. If your system
317 has no IDE drives, or if memory requirements are really tight, you
318 could say N here, and select the "Old hard disk driver" below
319 instead to save about 13 KB of memory in the kernel.
321 Old hard disk (MFM/RLL/IDE) driver
322 CONFIG_BLK_DEV_HD_ONLY
323 There are two drivers for MFM/RLL/IDE hard disks. Most people use
324 the newer enhanced driver, but this old one is still around for two
325 reasons. Some older systems have strange timing problems and seem to
326 work only with the old driver (which itself does not work with some
327 newer systems). The other reason is that the old driver is smaller,
328 since it lacks the enhanced functionality of the new one. This makes
329 it a good choice for systems with very tight memory restrictions, or
330 for systems with only older MFM/RLL/ESDI drives. Choosing the old
331 driver can save 13 KB or so of kernel memory.
333 If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
334 instead of this one. For more detailed information, read the
335 Disk-HOWTO, available via FTP (user: anonymous) from
336 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
338 People with SCSI-only systems can say N here.
340 Use old disk-only driver on primary interface
341 CONFIG_BLK_DEV_HD_IDE
342 There are two drivers for MFM/RLL/IDE disks. Most people use just
343 the new enhanced driver by itself. This option however installs the
344 old hard disk driver to control the primary IDE/disk interface in
345 the system, leaving the new enhanced IDE driver to take care of only
346 the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from
347 having an IDE/ATAPI CDROM or tape drive connected to the primary IDE
348 interface. Choosing this option may be useful for older systems
349 which have MFM/RLL/ESDI controller+drives at the primary port
350 address (0x1f0), along with IDE drives at the secondary/3rd/4th port
353 Normally, just say N here; you will then use the new driver for all
356 People with SCSI-only systems don't need this and can say N here as
359 Include IDE/ATA-2 DISK support
360 CONFIG_BLK_DEV_IDEDISK
361 This will include enhanced support for MFM/RLL/IDE hard disks. If
362 you have a MFM/RLL/IDE disk, and there is no special reason to use
363 the old hard disk driver instead, say Y. If you have an SCSI-only
364 system, you can say N here.
366 If you want to compile this driver as a module ( = code which can be
367 inserted in and removed from the running kernel whenever you want),
368 say M here and read Documentation/modules.txt. The module will be
369 called ide-disk.o. Do not compile this driver as a module if your
370 root filesystem (the one containing the directory /) is located on
371 the IDE disk. If unsure, say Y.
373 Use multi-mode by default
374 CONFIG_IDEDISK_MULTI_MODE
375 If you get this error, try to enable this option.
377 hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
378 hda: set_multmode: error=0x04 { DriveStatusError }
382 Include IDE/ATAPI CDROM support
384 If you have a CDROM drive using the ATAPI protocol, say Y. ATAPI is
385 a newer protocol used by IDE CDROM and TAPE drives, similar to the
386 SCSI protocol. Most new CDROM drives use ATAPI, including the
387 NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
388 double(2X) or better speed drives.
390 If you say Y here, the CDROM drive will be identified at boot time
391 along with other IDE devices, as "hdb" or "hdc", or something
392 similar (check the boot messages with dmesg). If this is your only
393 CDROM drive, you can say N to all other CDROM options, but be sure
394 to say Y or M to "ISO 9660 CDROM filesystem support".
396 Read the CDROM-HOWTO, available via FTP (user: anonymous) in
397 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO and the file
398 Documentation/cdrom/ide-cd. Note that older versions of lilo (the
399 Linux boot loader) cannot properly deal with IDE/ATAPI CDROMs, so
400 install lilo-16 or higher, available from
401 ftp://metalab.unc.edu/pub/Linux/system/Linux-boot/lilo.
403 If you want to compile the driver as a module ( = code which can be
404 inserted in and removed from the running kernel whenever you want),
405 say M here and read Documentation/modules.txt. The module will be
408 Include CD-Changer Reporting
410 If you have an IDE/ATAPI multi-slot cd-changer and you want
411 to report which slots have disk-present, say Y. If you say Y
412 and there is not a multi-slot cdrom present, this code is skipped.
414 This could be the bases of multi-disk access based on multi-mounts.
415 This is still pie-in-the-sky.
419 Include IDE/ATAPI TAPE support
420 CONFIG_BLK_DEV_IDETAPE
421 If you have an IDE tape drive using the ATAPI protocol, say Y.
422 ATAPI is a newer protocol used by IDE tape and CDROM drives, similar
423 to the SCSI protocol. If you have an SCSI tape drive however, you
426 If you say Y here, the tape drive will be identified at boot time
427 along with other IDE devices, as "hdb" or "hdc", or something
428 similar, and will be mapped to a character device such as "ht0"
429 (check the boot messages with dmesg). Be sure to consult the
430 drivers/block/ide-tape.c and Documentation/ide.txt files for usage
433 If you want to compile the driver as a module ( = code which can be
434 inserted in and removed from the running kernel whenever you want),
435 say M here and read Documentation/modules.txt. The module will be
438 Include IDE/ATAPI FLOPPY support
439 CONFIG_BLK_DEV_IDEFLOPPY
440 If you have an IDE floppy drive which uses the ATAPI protocol,
441 answer Y. ATAPI is a newer protocol used by IDE CDROM/tape/floppy
442 drives, similar to the SCSI protocol.
444 The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by
445 this driver. (ATAPI PD-CD/CDR drives are not supported by this
446 driver; support for PD-CD/CDR drives is available if you answer Y to
447 "SCSI emulation support", below).
449 If you say Y here, the FLOPPY drive will be identified along with
450 other IDE devices, as "hdb" or "hdc", or something similar (check
451 the boot messages with dmesg).
453 If you want to compile the driver as a module ( = code which can be
454 inserted in and removed from the running kernel whenever you want),
455 say M here and read Documentation/modules.txt. The module will be
458 SCSI emulation support
459 CONFIG_BLK_DEV_IDESCSI
460 This will provide SCSI host adapter emulation for IDE ATAPI devices,
461 and will allow you to use a SCSI device driver instead of a native
464 This is useful if you have an ATAPI device for which no native
465 driver has been written (for example, an ATAPI PD-CD or CDR drive);
466 you can then use this emulation together with an appropriate SCSI
467 device driver. In order to do this, say Y here and to "SCSI support"
468 and "SCSI generic support", below.
470 Note that this option does NOT allow you to attach SCSI devices to a
471 box that doesn't have a SCSI host adapter installed.
473 If both this SCSI emulation and native ATAPI support are compiled
474 into the kernel, the native support will be used.
476 People with SCSI-only systems can say N here. If unsure, say N.
478 CMD640 chipset bugfix/support
479 CONFIG_BLK_DEV_CMD640
480 The CMD-Technologies CMD640 IDE chip is used on many common 486 and
481 Pentium motherboards, usually in combination with a "Neptune" or
482 "SiS" chipset. Unfortunately, it has a number of rather nasty
483 design flaws that can cause severe data corruption under many common
484 conditions. Say Y here to include code which tries to automatically
485 detect and correct the problems under Linux. This option also
486 enables access to the secondary IDE ports in some CMD640 based
489 This driver will work automatically in PCI based systems (most new
490 systems have PCI slots). But if your system uses VESA local bus
491 (VLB) instead of PCI, you must also supply a kernel boot parameter
492 to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man
493 bootparam" or see the documentation of your boot loader about how to
494 pass options to the kernel. The lilo procedure is also explained in
495 the SCSI-HOWTO, available via FTP (user: anonymous) in
496 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.)
498 The CMD640 chip is also used on add-in cards by Acculogic, and on
499 the "CSA-6400E PCI to IDE controller" that some people have. For
500 details, read Documentation/ide.txt.
502 People with SCSI-only systems should say N here. If unsure, say Y.
504 CMD640 enhanced support
505 CONFIG_BLK_DEV_CMD640_ENHANCED
506 This option includes support for setting/autotuning PIO modes and
507 prefetch on CMD640 IDE interfaces. For details, read
508 Documentation/ide.txt. If you have a CMD640 IDE interface and your
509 BIOS does not already do this for you, then say Y here. Otherwise
512 RZ1000 chipset bugfix/support
513 CONFIG_BLK_DEV_RZ1000
514 The PC-Technologies RZ1000 IDE chip is used on many common 486 and
515 Pentium motherboards, usually along with the "Neptune" chipset.
516 Unfortunately, it has a rather nasty design flaw that can cause
517 severe data corruption under many conditions. Say Y here to include
518 code which automatically detects and corrects the problem under
519 Linux. This may slow disk throughput by a few percent, but at least
520 things will operate 100% reliably.
522 People with SCSI-only systems should say N here. If unsure, say Y.
524 Generic PCI IDE chipset support
525 CONFIG_BLK_DEV_IDEPCI
526 Say Y here for PCI systems which use IDE drive(s).
527 This option helps the IDE driver to automatically detect and
528 configure all PCI-based IDE interfaces in your system.
530 People with SCSI-only systems should say N here; if unsure say Y.
532 Generic PCI bus-master DMA support
533 CONFIG_BLK_DEV_IDEDMA_PCI
534 If your PCI system uses IDE drive(s) (as opposed to SCSI, say) and
535 is capable of bus-master DMA operation (most Pentium PCI systems),
536 you will want to say Y here to reduce CPU overhead. You can then use
537 the "hdparm" utility to enable DMA for drives for which it was not
538 enabled automatically. By default, DMA is not enabled automatically
539 for these drives, but you can change that by saying Y to the
540 following question "Use DMA by default when available". You can get
541 the latest version of the hdparm utility via anonymous FTP from
542 ftp://metalab.unc.edu/pub/Linux/system/hardware/.
544 Read the comments at the beginning of drivers/block/idedma.c and the
545 file Documentation/ide.txt for more information.
547 It is safe to say Y to this question.
549 Good-Bad DMA Model-Firmware (EXPERIMENTAL)
550 IDEDMA_NEW_DRIVE_LISTINGS
551 This test compares both the model and firmware revision for buggy drives
552 that claim to (U)DMA capable. This is a blanket on/off test with no speed
553 limit options. Straight GNU GCC 2.7.3/2.8.X compilers are known to be safe;
554 whereas, many versions of EGCS have a problem and miscompile.
558 Generic ATA-66 support (DANGEROUS)
559 CONFIG_IDEDMA_ULTRA_66
560 This allows for your Generic IDE control to attempt support for
561 using ATA-66 or UDMA-66 transfer modes 3/4. If you are not sure what you
562 are attempting, "DO NOT" even think about this option, unless your
563 mainboard's chipset is verified. Do not complain to anyone if you
564 do not know what you are doing and are just playing around.
565 This option has no known success cases to date.
567 Say N, or beware.........
569 Winbond SL82c105 support
570 CONFIG_BLK_DEV_SL82C105
571 If you have a Winbond SL82c105 IDE controller, say Y here to enable
572 special configuration for this chip. This is common on various CHRP
573 motherboards, but could be used elsewhere. If in doubt, say Y.
575 Boot off-board chipsets first support
576 CONFIG_BLK_DEV_OFFBOARD
577 Normally, IDE controllers built into the motherboard (on-board
578 controllers) are assigned to ide0 and ide1 while those on add-in PCI
579 cards (off-board controllers) are relegated to ide2 and ide3.
580 Answering Y here will reverse the situation, with off-board
581 controllers on ide0/1 and on-board controllers on ide2/3. This can
582 improve the usability of some boot managers such as LILO when
583 booting from a drive on an off-board controller.
585 Requires that all onboard ide controllers be disabled or calling
586 "pci=reverse" to invert the device scan order.
588 Note that, if you say Y here, the order of the hd* devices will be
589 rearranged which may require modification of fstab and other files.
593 Use DMA by default when available
594 CONFIG_IDEDMA_PCI_AUTO
595 Prior to kernel version 2.1.112, Linux used to automatically use
596 DMA for IDE drives and chipsets which support it. Due to concerns
597 about a couple of cases where buggy hardware may have caused damage,
598 the default is now to NOT use DMA automatically. To revert to the
599 previous behaviour, say Y to this question.
601 If you suspect your hardware is at all flakey, say N here.
602 Do NOT email the IDE kernel people regarding this issue!
604 It is normally safe to answer Y to this question unless your
605 motherboard uses a VIA VP2 chipset, in which case you should say N.
607 Other IDE chipset support
609 Say Y here if you want to include enhanced support for various IDE
610 interface chipsets used on motherboards and add-on cards. You can
611 then pick your particular IDE chip from among the following options.
612 This enhanced support may be necessary for Linux to be able to
613 access the 3rd/4th drives in some systems. It may also enable
614 setting of higher speed I/O rates to improve system performance with
615 these chipsets. Most of these also require special kernel boot
616 parameters to actually turn on the support at runtime; you can find
617 a list of these in the file Documentation/ide.txt.
619 People with SCSI-only systems can say N here.
621 Generic 4 drives/port support
622 CONFIG_BLK_DEV_4DRIVES
623 Certain older chipsets, including the Tekram 690CD, use a single set
624 of I/O ports at 0x1f0 to control up to four drives, instead of the
625 customary two drives per port. Support for this can be enabled at
626 runtime using the "ide0=four" kernel boot parameter if you say Y
630 CONFIG_BLK_DEV_DTC2278
631 This driver is enabled at runtime using the "ide0=dtc2278" kernel
632 boot parameter. It enables support for the secondary IDE interface
633 of the DTC-2278 card, and permits faster I/O speeds to be set as
634 well. See the Documentation/ide.txt and drivers/block/dtc2278.c
637 Holtek HT6560B support
638 CONFIG_BLK_DEV_HT6560B
639 This driver is enabled at runtime using the "ide0=ht6560b" kernel
640 boot parameter. It enables support for the secondary IDE interface
641 of the Holtek card, and permits faster I/O speeds to be set as well.
642 See the Documentation/ide.txt and drivers/block/ht6560b.c files for
645 PROMISE DC4030 support (EXPERIMENTAL)
646 CONFIG_BLK_DEV_PDC4030
647 This driver provides support for the secondary IDE interface and
648 cache of Promise IDE chipsets, e.g. DC4030 and DC5030. This driver
649 is known to incur timeouts/retries during heavy I/O to drives
650 attached to the secondary interface. CDROM and TAPE devices are not
651 supported yet. This driver is enabled at runtime using the
652 "ide0=dc4030" kernel boot parameter. See the Documentation/ide.txt
653 and drivers/block/pdc4030.c files for more info.
655 PS/2 ESDI hard disk support
657 Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
660 If you want to compile the driver as a module ( = code which can be
661 inserted in and removed from the running kernel whenever you want),
662 say M here and read Documentation/modules.txt. The module will be
665 Tekram TRM290 chipset support (EXPERIMENTAL)
666 CONFIG_BLK_DEV_TRM290
667 This driver adds support for bus master DMA transfers
668 using the Tekram TRM290 PCI IDE chip. Volunteers are
669 needed for further tweaking and development.
670 Please read the comments at the top of drivers/block/trm290.c.
672 OPTi 82C621 enhanced support (EXPERIMENTAL)
673 CONFIG_BLK_DEV_OPTI621
674 This is a driver for the OPTi 82C621 EIDE controller.
675 Please read the comments at the top of drivers/block/opti621.c.
677 NS87415 support (EXPERIMENTAL)
678 CONFIG_BLK_DEV_NS87415
679 This driver adds detection and support for the NS87415 chip
680 (used in SPARC64, among others).
682 Please read the comments at the top of drivers/block/ns87415.c.
684 CY82C693 chipset support (EXPERIMENTAL)
685 CONFIG_BLK_DEV_CY82C693
687 This driver adds detection and support for the CY82C693 chipset
688 used on Digital's PC-Alpha 164SX boards.
690 This requires CONFIG_IDEDMA_PCI_AUTO to be enabled.
692 Please read the comments at the top of drivers/block/cy82c693.c
694 VIA82C586 chipset support (EXPERIMENTAL)
695 CONFIG_BLK_DEV_VIA82C586
696 This allows you to to configure your chipset for a better use while
697 running (U)DMA: it will allow you to enable efficiently the second
698 channel dma usage, as it is may not be set by BIOS. It allows you to
699 run a kernel command line at boot time in order to set fifo config.
700 If no command line is provided, it will try to set fifo configuration
701 at its best. It will allow you to get a proc/ide/via display
702 (while running a "cat") provided you enabled "proc" support and
703 set DISPLAY_APOLLO_TIMINGS in via82c586.c
705 This requires CONFIG_IDEDMA_PCI_AUTO to be enabled.
709 CMD646 chipset support (EXPERIMENTAL)
710 CONFIG_BLK_DEV_CMD646
711 Say Y here if you have an IDE controller like this.
713 ALI M15x3 chipset support (EXPERIMENTAL)
714 CONFIG_BLK_DEV_ALI15X3
715 This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C
716 onboard chipsets. It also tests for Simplex mode and enables
717 normal dual channel support.
719 This requires CONFIG_IDEDMA_PCI_AUTO to be enabled.
721 Please read the comments at the top of drivers/block/alim15x3.c
725 PROMISE PDC20246/PDC20262 support
726 CONFIG_BLK_DEV_PDC202XX
727 Promise Ultra33 or PDC20246.
728 This driver adds up to 4 more eide devices sharing a single interrupt.
729 This add-on card is a bootable PCI UDMA controller.
730 Since multiple cards can be installed and there are BIOS ROM problems
731 that happen if the BIOS revisions of all installed cards (three-max)
732 do not match. Should you be unable to make new BIOS chips with a burner,
733 the driver attempts to dynamic tuning of the chipset at boot-time
734 for max-speed. Ultra33 BIOS 1.25 or new required for more than one card.
735 This card may require "PDC202XX Special UDMA Feature (EXPERIMENTAL)".
737 Promise Ultra66 or PDC20262.
738 This driver adds up to 4 more eide devices sharing a single interrupt.
739 This add-on card is a bootable PCI UDMA ATA-66 controller.
740 The driver attempts to dynamic tuning of the chipset at boot-time
741 for max-speed. Note tested limits are UDMA-2.
742 Ultra66 BIOS 1.11 or newer required.
744 This requires CONFIG_IDEDMA_PCI_AUTO to be enabled.
746 Please read the comments at the top of drivers/block/pdc202xx.c
750 Special UDMA Feature (EXPERIMENTAL)
751 PDC202XX_FORCE_BURST_BIT
752 For PDC20246 and PDC20262 Ultra DMA chipsets.
753 Designed originally for PDC20246/Ultra33 that has BIOS setup failures
754 when using 3 or more cards.
756 Please read the comments at the top of drivers/block/pdc202xx.c
760 Special Mode Feature (DANGEROUS)
761 PDC202XX_FORCE_MASTER_MODE
762 For PDC20246 and PDC20262 Ultra DMA chipsets.
763 This is reserved for possible Hardware RAID 0,1 for the FastTrak Series.
767 AEC6210 chipset support
768 CONFIG_BLK_DEV_AEC6210
769 This driver adds up to 4 more eide devices sharing a single interrupt.
770 This add-on card is a bootable PCI UDMA controller. In order to get this
771 card to initialize correctly in some cases, you should include this driver.
773 This prefers CONFIG_IDEDMA_PCI_AUTO to be enabled, regardless.
775 Please read the comments at the top of drivers/block/aec6210.c
777 Intel PIIXn chipsets support
779 This driver adds PIO mode setting and tuning for all PIIX IDE
780 controllers by Intel. Since the BIOS can sometimes improperly tune
781 PIO 0-4 mode settings, this allows dynamic tuning of the chipset
782 via the standard end-user tool 'hdparm'.
784 Please read the comments at the top of drivers/block/piix.c
788 PIIXn Tuning support (EXPERIMENTAL)
789 CONFIG_BLK_DEV_PIIX_TUNING
790 This driver extension adds DMA mode setting and tuning for all PIIX IDE
791 controllers by Intel. Since the BIOS can sometimes improperly setup
792 the device/adapter combination and speed limits, It has become a necessity
793 to back/forward speed devices as needed.
795 Case 430HX/440FX PIIX3 need speed limits to reduce UDMA to DMA mode 2
796 if the BIOS can to perform this task at INIT.
800 HPT34X chipset support
801 CONFIG_BLK_DEV_HPT34X
802 This driver adds up to 4 more EIDE devices sharing a single
803 interrupt. The HPT343 chipset in its current form is a non-bootable or
804 HPT345/HPT363 chipset is bootable (needs BIOS FIX) PCI UDMA controllers.
805 This driver requires dynamic tuning of the chipset during the ide-probe
806 at boot. It is reported to support DVD II drives, by the manufacturer.
808 Please read the comments at the top of drivers/block/hpt343.c
810 HPT34X DMA support (DANGEROUS)
811 CONFIG_BLK_DEV_HPT34X_DMA
812 This requires CONFIG_IDEDMA_PCI_AUTO to be enabled.
814 Please read the comments at the top of drivers/block/hpt343.c
817 CONFIG_BLK_DEV_QD6580
818 This driver is enabled at runtime using the "ide0=qd6580" kernel
819 boot parameter. It permits faster I/O speeds to be set. See the
820 files Documentation/ide.txt and drivers/block/qd6580.c for more
824 CONFIG_BLK_DEV_UMC8672
825 This driver is enabled at runtime using the "ide0=umc8672" kernel
826 boot parameter. It enables support for the secondary IDE interface
827 of the UMC-8672, and permits faster I/O speeds to be set as well.
828 See the files Documentation/ide.txt and drivers/block/umc8672.c for
832 CONFIG_BLK_DEV_ALI14XX
833 This driver is enabled at runtime using the "ide0=ali14xx" kernel
834 boot parameter. It enables support for the secondary IDE interface
835 of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
836 I/O speeds to be set as well. See the files Documentation/ide.txt
837 and drivers/block/ali14xx.c for more info.
839 Amiga builtin Gayle IDE interface support
841 This is the IDE driver for the builtin IDE interface on some Amiga
842 models. It supports both the `A1200 style' (used in A600 and A1200)
843 and `A4000 style' (used in A4000 and A4000T) of the Gayle IDE interface.
844 Say Y if you have such an Amiga model and want to use IDE devices
845 (hard disks, CD-ROM drives, etc.) that are connected to the builtin
848 Falcon IDE interface support
849 CONFIG_BLK_DEV_FALCON_IDE
850 This is the IDE driver for the builtin IDE interface on the Atari Falcon.
851 Say Y if you have a Falcon and want to use IDE devices (hard disks,
852 CD-ROM drives, etc.) that are connected to the builtin IDE interface.
854 Amiga Buddha/Catweasel IDE interface support (EXPERIMENTAL)
855 CONFIG_BLK_DEV_BUDDHA
856 This is the IDE driver for the IDE interfaces on the Buddha and
857 Catweasel expansion boards. It supports up to two interfaces on the
858 Buddha and three on the Catweasel.
859 Say Y if you have a Buddha or Catweasel expansion board and want to
860 use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
861 to one of its IDE interfaces.
863 Amiga IDE Doubler support (EXPERIMENTAL)
864 CONFIG_BLK_DEV_IDEDOUBLER
865 This driver provides support for the so called `IDE doublers' (made by
866 various manufacturers, e.g. Eyetech) that can be connected to the
867 builtin IDE interface of some Amiga models. Using such an IDE doubler,
868 you can connect up to four instead of two IDE devices on the Amiga's
869 builtin IDE interface.
870 Note that the normal Amiga Gayle IDE driver may not work correctly if
871 you have an IDE doubler and don't enable this driver!
872 Say Y if you have an IDE doubler. The driver is enabled at kernel
873 runtime using the "ide=doubler" kernel boot parameter.
875 Support for PowerMac IDE devices (must also enable IDE)
876 CONFIG_BLK_DEV_IDE_PMAC
877 No help for CONFIG_BLK_DEV_IDE_PMAC
879 PowerMac IDE DMA support
880 CONFIG_BLK_DEV_IDEDMA_PMAC
881 No help for CONFIG_BLK_DEV_IDEDMA_PMAC
884 CONFIG_IDEDMA_PMAC_AUTO
885 No help for CONFIG_IDEDMA_PMAC_AUTO
887 Macintosh Quadra/Powerbook IDE interface support
888 CONFIG_BLK_DEV_MAC_IDE
889 This is the IDE driver for the builtin IDE interface on the some m68k
890 Macintosh models. It supports both the `Quadra style' (used in Quadra/
891 Centris 630 and Performa 588 models) and `Powerbook style' (used in the
892 Powerbook 150 and 190 models) IDE interface.
893 Say Y if you have such an Macintosh model and want to use IDE devices
894 (hard disks, CD-ROM drives, etc.) that are connected to the builtin
897 ICS IDE interface support
898 CONFIG_BLK_DEV_IDE_ICSIDE
899 No help for CONFIG_BLK_DEV_IDE_ICSIDE
902 CONFIG_BLK_DEV_IDEDMA_ICS
903 No help for CONFIG_BLK_DEV_IDEDMA_ICS
905 Use ICS DMA by default
906 CONFIG_IDEDMA_ICS_AUTO
907 No help for CONFIG_IDEDMA_ICS_AUTO
909 RapIDE interface support
910 CONFIG_BLK_DEV_IDE_RAPIDE
911 No help for CONFIG_BLK_DEV_IDE_RAPIDE
915 Very old 8 bit hard disk controllers used in the IBM XT computer
916 will be supported if you say Y here.
918 If you want to compile the driver as a module ( = code which can be
919 inserted in and removed from the running kernel whenever you want),
920 say M here and read Documentation/modules.txt. The module will be
923 It's pretty unlikely that you have one of these: say N.
925 Parallel port IDE device support
927 There are many external CD-ROM and disk devices that connect through
928 your computer's parallel port. Most of them are actually IDE devices
929 using a parallel port IDE adapter. This option enables the PARIDE
930 subsystem which contains drivers for many of these external drives.
931 Read linux/Documentation/paride.txt for more information.
933 If you have said Y to the "Parallel-port support" configuration
934 option, you may share a single port between your printer and other
935 parallel port devices. Answer Y to build PARIDE support into your
936 kernel, or M if you would like to build it as a loadable module. If
937 your parallel port support is in a loadable module, you must build
938 PARIDE as a module. If you built PARIDE support into your kernel,
939 you may still build the individual protocol modules and high-level
940 drivers as loadable modules. If you build this support as a module,
941 it will be called paride.o.
943 To use the PARIDE support, you must say Y or M here and also to at
944 least one high-level driver (e.g. "Parallel port IDE disks",
945 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
946 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
947 "MicroSolutions backpack protocol", "DataStor Commuter protocol"
950 Parallel port IDE disks
952 This option enables the high-level driver for IDE-type disk devices
953 connected through a parallel port. If you chose to build PARIDE
954 support into your kernel, you may answer Y here to build in the
955 parallel port IDE driver, otherwise you should answer M to build
956 it as a loadable module. The module will be called pd.o. You
957 must also have at least one parallel port protocol driver in your
958 system. Among the devices supported by this driver are the SyQuest
959 EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack
960 hard drives from MicroSolutions.
962 Parallel port ATAPI CD-ROMs
964 This option enables the high-level driver for ATAPI CD-ROM devices
965 connected through a parallel port. If you chose to build PARIDE
966 support into your kernel, you may answer Y here to build in the
967 parallel port ATAPI CD-ROM driver, otherwise you should answer M to
968 build it as a loadable module. The module will be called pcd.o. You
969 must also have at least one parallel port protocol driver in your
970 system. Among the devices supported by this driver are the
971 MicroSolutions backpack CD-ROM drives and the Freecom Power CD. If
972 you have such a CD-ROM drive, you should also say Y or M to "ISO
973 9660 CDROM filesystem support" below, because that's the filesystem
976 Parallel port ATAPI disks
978 This option enables the high-level driver for ATAPI disk devices
979 connected through a parallel port. If you chose to build PARIDE
980 support into your kernel, you may answer Y here to build in the
981 parallel port ATAPI disk driver, otherwise you should answer M
982 to build it as a loadable module. The module will be called pf.o.
983 You must also have at least one parallel port protocol driver in
984 your system. Among the devices supported by this driver are the
985 MicroSolutions backpack PD/CD drive and the Imation Superdisk
988 Parallel port ATAPI tapes
990 This option enables the high-level driver for ATAPI tape devices
991 connected through a parallel port. If you chose to build PARIDE
992 support into your kernel, you may answer Y here to build in the
993 parallel port ATAPI disk driver, otherwise you should answer M
994 to build it as a loadable module. The module will be called pt.o.
995 You must also have at least one parallel port protocol driver in
996 your system. Among the devices supported by this driver is the
997 parallel port version of the HP 5GB drive.
999 Parallel port generic ATAPI devices
1001 This option enables a special high-level driver for generic ATAPI
1002 devices connected through a parallel port. The driver allows user
1003 programs, such as cdrecord, to send ATAPI commands directly to a
1006 If you chose to build PARIDE support into your kernel, you may
1007 answer Y here to build in the parallel port generic ATAPI driver,
1008 otherwise you should answer M to build it as a loadable module. The
1009 module will be called pg.o.
1011 You must also have at least one parallel port protocol driver in
1014 This driver implements an API loosely related to the generic SCSI
1015 driver. See /usr/include/linux/pg.h for details.
1017 You can obtain the most recent version of cdrecord from
1018 ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/ . Versions 1.6.1a3 and
1019 later fully support this driver.
1021 ATEN EH-100 protocol
1023 This option enables support for the ATEN EH-100 parallel port IDE
1024 protocol. This protocol is used in some inexpensive low performance
1025 parallel port kits made in Hong Kong. If you chose to build PARIDE
1026 support into your kernel, you may answer Y here to build in the
1027 protocol driver, otherwise you should answer M to build it as a
1028 loadable module. The module will be called aten.o. You must also
1029 have a high-level driver for the type of device that you want to
1032 MicroSolutions backpack protocol
1034 This option enables support for the MicroSolutions backpack parallel
1035 port IDE protocol. If you chose to build PARIDE support into your
1036 kernel, you may answer Y here to build in the protocol driver,
1037 otherwise you should answer M to build it as a loadable module. The
1038 module will be called bpck.o. You must also have a high-level driver
1039 for the type of device that you want to support.
1041 DataStor Commuter protocol
1043 This option enables support for the Commuter parallel port IDE
1044 protocol from DataStor. If you chose to build PARIDE support
1045 into your kernel, you may answer Y here to build in the protocol
1046 driver, otherwise you should answer M to build it as a loadable
1047 module. The module will be called comm.o. You must also have
1048 a high-level driver for the type of device that you want to support.
1050 DataStor EP-2000 protocol
1052 This option enables support for the EP-2000 parallel port IDE
1053 protocol from DataStor. If you chose to build PARIDE support
1054 into your kernel, you may answer Y here to build in the protocol
1055 driver, otherwise you should answer M to build it as a loadable
1056 module. The module will be called dstr.o. You must also have
1057 a high-level driver for the type of device that you want to support.
1059 Shuttle EPAT/EPEZ protocol
1061 This option enables support for the EPAT parallel port IDE protocol.
1062 EPAT is a parallel port IDE adapter manufactured by Shuttle
1063 Technology and widely used in devices from major vendors such as
1064 Hewlett-Packard, SyQuest, Imation and Avatar. If you chose to build
1065 PARIDE support into your kernel, you may answer Y here to build in
1066 the protocol driver, otherwise you should answer M to build it as a
1067 loadable module. The module will be called epat.o. You must also
1068 have a high-level driver for the type of device that you want to
1071 Shuttle EPIA protocol
1073 This option enables support for the (obsolete) EPIA parallel port
1074 IDE protocol from Shuttle Technology. This adapter can still be
1075 found in some no-name kits. If you chose to build PARIDE support
1076 into your kernel, you may answer Y here to build in the protocol
1077 driver, otherwise you should answer M to build it as a loadable
1078 module. The module will be called epia.o. You must also have a
1079 high-level driver for the type of device that you want to support.
1081 FIT TD-2000 protocol
1083 This option enables support for the TD-2000 parallel port IDE
1084 protocol from Fidelity International Technology. This is a simple
1085 (low speed) adapter that is used in some portable hard drives. If
1086 you chose to build PARIDE support into your kernel, you may answer Y
1087 here to build in the protocol driver, otherwise you should answer M
1088 to build it as a loadable module. The module will be called ktti.o.
1089 You must also have a high-level driver for the type of device that
1090 you want to support.
1092 FIT TD-3000 protocol
1094 This option enables support for the TD-3000 parallel port IDE
1095 protocol from Fidelity International Technology. This protocol is
1096 used in newer models of their portable disk, CD-ROM and PD/CD
1097 devices. If you chose to build PARIDE support into your kernel, you
1098 may answer Y here to build in the protocol driver, otherwise you
1099 should answer M to build it as a loadable module. The module will be
1100 called fit3.o. You must also have a high-level driver for the type
1101 of device that you want to support.
1103 Freecom IQ ASIC-2 protocol
1105 This option enables support for version 2 of the Freecom IQ parallel
1106 port IDE adapter. This adapter is used by the Maxell Superdisk
1107 drive. If you chose to build PARIDE support into your kernel, you
1108 may answer Y here to build in the protocol driver, otherwise you
1109 should answer M to build it as a loadable module. The module will be
1110 called friq.o. You must also have a high-level driver for the type
1111 of device that you want to support.
1113 FreeCom power protocol
1115 This option enables support for the Freecom power parallel port IDE
1116 protocol. If you chose to build PARIDE support into your kernel, you
1117 may answer Y here to build in the protocol driver, otherwise you
1118 should answer M to build it as a loadable module. The module will be
1119 called frpw.o. You must also have a high-level driver for the type
1120 of device that you want to support.
1122 KingByte KBIC-951A/971A protocols
1124 This option enables support for the KBIC-951A and KBIC-971A parallel
1125 port IDE protocols from KingByte Information Corp. KingByte's
1126 adapters appear in many no-name portable disk and CD-ROM products,
1127 especially in Europe. If you chose to build PARIDE support into your
1128 kernel, you may answer Y here to build in the protocol driver,
1129 otherwise you should answer M to build it as a loadable module. The
1130 module will be called kbic.o. You must also have a high-level driver
1131 for the type of device that you want to support.
1135 This option enables support for the "PHd" parallel port IDE protocol
1136 from KT Technology. This is a simple (low speed) adapter that is
1137 used in some 2.5" portable hard drives. If you chose to build PARIDE
1138 support into your kernel, you may answer Y here to build in the
1139 protocol driver, otherwise you should answer M to build it as a
1140 loadable module. The module will be called ktti.o. You must also
1141 have a high-level driver for the type of device that you want to
1144 OnSpec 90c20 protocol
1146 This option enables support for the (obsolete) 90c20 parallel port
1147 IDE protocol from OnSpec (often marketed under the ValuStore brand
1148 name). If you chose to build PARIDE support into your kernel, you
1149 may answer Y here to build in the protocol driver, otherwise you
1150 should answer M to build it as a loadable module. The module will
1151 be called on20.o. You must also have a high-level driver for the
1152 type of device that you want to support.
1154 OnSpec 90c26 protocol
1156 This option enables support for the 90c26 parallel port IDE protocol
1157 from OnSpec Electronics (often marketed under the ValuStore brand
1158 name). If you chose to build PARIDE support into your kernel, you
1159 may answer Y here to build in the protocol driver, otherwise you
1160 should answer M to build it as a loadable module. The module will be
1161 called on26.o. You must also have a high-level driver for the type
1162 of device that you want to support.
1164 Multiple devices driver support
1166 This driver lets you combine several hard disk partitions into one
1167 logical block device. This can be used to simply append one
1168 partition to another one or to combine several redundant
1169 hard disks to a RAID1/4/5 device so as to provide protection against
1170 hard disk failures. This is called "Software RAID" since the
1171 combining of the partitions is done by the kernel. "Hardware RAID"
1172 means that the combining is done by a dedicated controller; if you
1173 have such a controller, you do not need to say Y here.
1175 More information about Software RAID on Linux is contained in the
1176 Software-RAID mini-HOWTO, available via FTP (user: anonymous) from
1177 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini. There you will also
1178 learn where to get the supporting user space utilities raidtools.
1182 Linear (append) mode
1184 If you say Y here, then your multiple devices driver will be able to
1185 use the so-called linear mode, i.e. it will combine the hard disk
1186 partitions by simply appending one to the other.
1188 If you want to compile this as a module ( = code which can be
1189 inserted in and removed from the running kernel whenever you want),
1190 say M here and read Documentation/modules.txt. The module will be
1195 RAID-0 (striping) mode
1197 If you say Y here, then your multiple devices driver will be able to
1198 use the so-called raid0 mode, i.e. it will combine the hard disk
1199 partitions into one logical device in such a fashion as to fill them
1200 up evenly, one chunk here and one chunk there. This will increase
1201 the throughput rate if the partitions reside on distinct disks.
1203 Information about Software RAID on Linux is contained in the
1204 Software-RAID mini-HOWTO, available via FTP (user: anonymous) from
1205 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini. There you will also
1206 learn where to get the supporting user space utilities raidtools.
1208 If you want to compile this as a module ( = code which can be
1209 inserted in and removed from the running kernel whenever you want),
1210 say M here and read Documentation/modules.txt. The module will be
1215 RAID-1 (mirroring) mode
1217 A RAID-1 set consists of several disk drives which are exact copies
1218 of each other. In the event of a mirror failure, the RAID driver
1219 will continue to use the operational mirrors in the set, providing
1220 an error free MD (multiple device) to the higher levels of the
1221 kernel. In a set with N drives, the available space is the capacity
1222 of a single drive, and the set protects against a failure of (N - 1)
1225 Information about Software RAID on Linux is contained in the
1226 Software-RAID mini-HOWTO, available via FTP (user: anonymous) from
1227 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini. There you will also
1228 learn where to get the supporting user space utilities raidtools.
1230 If you want to use such a RAID-1 set, say Y. This code is also
1231 available as a module called raid1.o ( = code which can be inserted
1232 in and removed from the running kernel whenever you want). If you
1233 want to compile it as a module, say M here and read
1234 Documentation/modules.txt.
1240 A RAID-5 set of N drives with a capacity of C MB per drive provides
1241 the capacity of C * (N - 1) drives, and protects against a failure
1242 of a single drive. For a given sector (row) number, (N - 1) drives
1243 contain data sectors, and one drive contains the parity protection.
1244 For a RAID-4 set, the parity blocks are present on a single drive,
1245 while a RAID-5 set distributes the parity across the drives in one
1246 of the available parity distribution methods.
1248 Information about Software RAID on Linux is contained in the
1249 Software-RAID mini-HOWTO, available via FTP (user: anonymous) from
1250 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini. There you will also
1251 learn where to get the supporting user space utilities raidtools.
1253 If you want to use such a RAID-4/RAID-5 set, say Y. This code is
1254 also available as a module called raid5.o ( = code which can be
1255 inserted in and removed from the running kernel whenever you want).
1256 If you want to compile it as a module, say M here and read
1257 Documentation/modules.txt.
1261 Boot support (linear, striped)
1263 To boot with an initial linear or striped md device you have to
1264 answer Y here. For lilo and loadlin options see the file
1265 Documentation/md.txt.
1267 Support for Deskstation RPC44
1268 CONFIG_DESKSTATION_RPC44
1269 This is a machine with a R4400 100 MHz CPU. To compile a Linux
1270 kernel that runs on these, say Y here. For details about Linux
1271 on the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1272 http://lena.fnet.fr/ (To browse the WWW, you need to
1273 have access to a machine on the Internet that has a program like
1276 Support for Acer PICA 1 chipset
1278 This is a machine with a R4400 133/150 MHz CPU. To compile a Linux
1279 kernel that runs on these, say Y here. For details about Linux on
1280 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1281 http://lena.fnet.fr/ (To browse the WWW, you need to have access to
1282 a machine on the Internet that has a program like lynx or netscape).
1284 Support for Algorithmics P4032
1286 This is an evaluation board of the British company Algorithmics. The
1287 board uses the R4300 and a R5230 CPUs. For more information about
1288 this board see http://www.algor.co.uk.
1291 CONFIG_BLK_DEV_IDE_CARDS
1292 On Acorn systems, enable this if you wish to use an IDE interface
1293 expansion card. If you do not or are unsure, say N to this.
1296 CONFIG_BLK_DEV_IDE_ICS
1297 On Acorn systems, enable this if you wish to use the ICS IDE
1298 interface card. This is not required for ICS partition support.
1299 If you are unsure, say N to this.
1301 ADFS partition support
1303 This allows Linux on Acorn systems to determine its partitions in
1304 the 'non-ADFS' partition area of the hard disk - usually located
1305 after the ADFS partition. You are probably using this system, so
1306 you should enable it.
1308 Support for Mips Magnum 4000
1309 CONFIG_MIPS_MAGNUM_4000
1310 This is a machine with a R4000 100 MHz CPU. To compile a Linux
1311 kernel that runs on these, say Y here. For details about Linux on
1312 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1313 http://lena.fnet.fr/ (To browse the WWW, you need to have access to
1314 a machine on the Internet that has a program like lynx or netscape).
1316 Support for Olivetti M700
1317 CONFIG_OLIVETTI_M700
1318 This is a machine with a R4000 100 MHz CPU. To compile a Linux
1319 kernel that runs on these, say Y here. For details about Linux on
1320 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1321 http://lena.fnet.fr/ (To browse the WWW, you need to have access to
1322 a machine on the Internet that has a program like lynx or netscape).
1326 Give the type of your machine's MIPS CPU. For this question, it
1327 suffices to give a unique prefix of the option you want to choose.
1328 In case of doubt select the R3000 CPU. The kernel will then run on
1329 other MIPS machines but with slightly reduced performance.
1331 Compile the kernel into the ECOFF object format
1333 Some machines require a kernel in the ECOFF format. You will have to
1334 say Y here for example if you want to use a Mips Magnum 3000 or a
1337 Generate little endian code
1338 CONFIG_CPU_LITTLE_ENDIAN
1339 Some MIPS machines can be configured for either little or big endian
1340 byte order. These modes require different kernels. Say Y if your
1341 machine is little endian, N if it's a big endian machine.
1343 Kernel support for IRIX binaries
1345 If you say Y here, the kernel will support running of IRIX binaries.
1346 You will need IRIX libraries for this to work.
1350 Unless you really know what you are doing, you should say Y here.
1351 The reason is that some programs need kernel networking support even
1352 when running on a stand-alone machine that isn't connected to any
1353 other computer. If you are upgrading from an older kernel, you
1354 should consider updating your networking tools too because changes
1355 in the kernel and the tools often go hand in hand. The tools are
1356 contained in the package net-tools, the location and version number
1357 of which are given in Documentation/Changes.
1359 For a general introduction to Linux networking, it is highly
1360 recommended to read the NET-3-HOWTO, available via FTP (user:
1361 anonymous) from ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
1365 The Linux Socket Filter is derived from the Berkeley Packet Filter.
1366 If you say Y here, user-space programs can attach a filter to any
1367 socket and thereby tell the kernel that it should allow or disallow
1368 certain types of data to get through the socket. Linux Socket
1369 Filtering works on all socket types except TCP for now. See the text
1370 file linux/Documentation/networking/filter.txt for more information.
1375 A firewall is a computer which protects a local network from the
1376 rest of the world: all traffic to and from computers on the local
1377 net is inspected by the firewall first, and sometimes blocked or
1378 modified. The type of firewall you'll get if you say Y here is
1379 called a "packet filter": it can block network traffic based on
1380 type, origin and destination. By contrast, "proxy-based" firewalls
1381 are more secure but more intrusive and more bothersome to set up;
1382 they inspect the network traffic much more closely, modify it and
1383 have knowledge about the higher level protocols, which packet
1384 filters lack. They also often require changes in the programs
1385 running on the local clients. Proxy-based firewalls don't need
1386 support by the kernel, but they are often combined with packet
1387 filters, which only works if you say Y here.
1389 If you want to configure your Linux box as a packet filter firewall
1390 for a local network, say Y here. If your local network is TCP/IP
1391 based, you will then also have to say Y to "IP: firewalling", below.
1393 You also need to say Y here and to "IP firewalling" below in order
1394 to be able to use IP masquerading (i.e. local computers can chat
1395 with an outside host, but that outside host is made to think that it
1396 is talking to the firewall box -- makes the local network completely
1397 invisible to the outside world and avoids the need to allocate
1398 globally valid IP host addresses for the machines on the local net)
1399 and IP transparent proxying (makes the computers on the local
1400 network think they're talking to a remote computer, while in reality
1401 the traffic is redirected by your Linux firewall to a local proxy
1404 Make sure to say N to "Fast switching" below if you intend to say Y
1407 Chances are that you should say Y here for every machine which is
1408 run as a router and N for every regular host. If unsure, say N.
1410 SYN flood protection
1412 Normal TCP/IP networking is open to an attack known as "SYN
1413 flooding". This denial-of-service attack prevents legitimate remote
1414 users from being able to connect to your computer during an ongoing
1415 attack and requires very little work from the attacker, who can
1416 operate from anywhere on the Internet.
1418 SYN cookies provide protection against this type of attack. If you
1419 say Y here, the TCP/IP stack will use a cryptographic challenge
1420 protocol known as "SYN cookies" to enable legitimate users to
1421 continue to connect, even when your machine is under attack. There
1422 is no need for the legitimate users to change their TCP/IP software;
1423 SYN cookies work transparently to them. For technical information
1424 about SYN cookies, check out
1425 ftp://koobera.math.uic.edu/pub/docs/syncookies-archive.
1427 If you are SYN flooded, the source address reported by the kernel is
1428 likely to have been forged by the attacker; it is only reported as
1429 an aid in tracing the packets to their actual source and should not
1430 be taken as absolute truth.
1432 SYN cookies may prevent correct error reporting on clients when the
1433 server is really overloaded. If this happens frequently better turn
1436 If you say Y here, note that SYN cookies aren't enabled by default;
1437 you can enable them by saying Y to "/proc filesystem support" and
1438 "Sysctl support" below and executing the command
1440 echo 1 >/proc/sys/net/ipv4/tcp_syncookies
1442 at boot time after the proc filesystem has been mounted.
1446 Sun floppy controller support
1447 CONFIG_BLK_DEV_SUNFD
1448 This is support for floppy drives on Sun SPARC workstations. Say Y
1449 if you have a floppy drive, otherwise N. Easy.
1452 CONFIG_ALPHA_GENERIC
1453 This is the system type of your hardware. A "generic" kernel will
1454 run on any supported Alpha system. However, if you configure a
1455 kernel for your specific system, it will be faster and smaller.
1457 To find out what type of Alpha system you have, you may want to
1458 check out the Linux/Alpha FAQ, accessible on the WWW from
1459 http://www.alphalinux.org (To browse the WWW, you need to
1460 have access to a machine on the Internet that has a program like
1461 lynx or netscape). In summary:
1463 Alcor/Alpha-XLT AS 600
1464 Alpha-XL XL-233, XL-266
1465 AlphaBook1 Alpha laptop
1466 Avanti AS 200, AS 205, AS 250, AS 255, AS 300, AS 400
1467 Cabriolet AlphaPC64, AlphaPCI64
1469 EB164 EB164 21164 evaluation board
1470 EB64+ EB64+ 21064 evaluation board
1471 EB66 EB66 21066 evaluation board
1472 EB66+ EB66+ 21066 evaluation board
1473 Jensen DECpc 150, DEC 2000 model 300,
1476 Miata Personal Workstation 433a, 433au, 500a,
1477 500au, 600a, or 600au
1479 Noname AXPpci33, UDB (Multia)
1480 Noritake AS 1000A, AS 600A, AS 800
1482 Rawhide AS 1200, AS 4000, AS 4100
1483 Ruffian RPX164-2, AlphaPC164-UX, AlphaPC164-BX
1485 Sable AS 2000, AS 2100
1488 If you don't know what to do, choose "generic".
1490 EV5 CPU daughtercard
1492 Say Y if you have an AS 1000 5/xxx or an AS 1000A 5/xxx.
1496 Say Y if you have an AS 2000 5/xxx or an AS 2100 5/xxx.
1498 Using SRM as bootloader
1500 There are two different types of booting firmware on Alphas: SRM,
1501 which is command line driven, and ARC, which uses menus and arrow
1502 keys. Details about the Linux/Alpha booting process are contained in
1503 the Linux/Alpha FAQ, accessible on the WWW from
1504 http://www.alphalinux.org (To browse the WWW, you need to
1505 have access to a machine on the Internet that has a program like
1508 The usual way to load Linux on an Alpha machine is to use MILO
1509 (a bootloader that lets you pass command line parameters to the
1510 kernel just like lilo does for the x86 architecture) which can be
1511 loaded either from ARC or can be installed directly as a permanent
1512 firmware replacement from floppy (which requires changing a certain
1513 jumper on the motherboard). If you want to do either of these, say N
1514 here. If MILO doesn't work on your system (true for Jensen
1515 motherboards), you can bypass it altogether and boot Linux directly
1516 from an SRM console; say Y here in order to do that. Note that you
1517 won't be able to boot from an IDE disk using SRM.
1522 CONFIG_ALPHA_SRM_SETUP
1523 This option controls whether or not the PCI configuration set up by
1524 SRM is modified. If you say Y, the existing PCI configuration will
1527 Non-standard serial port support
1528 CONFIG_SERIAL_NONSTANDARD
1529 Say Y here if you have any non-standard serial boards -- boards
1530 which aren't supported using the standard "dumb" serial driver.
1531 This includes intelligent serial boards such as Cyclades,
1532 Digiboards, etc. These are usually used for systems that need many
1533 serial ports because they serve many terminals or dial-in
1536 Note that the answer to this question won't directly affect the
1537 kernel: saying N will just cause this configure script to skip all
1538 the questions about non-standard serial boards.
1540 Most people can say N here.
1542 Extended dumb serial driver options
1543 CONFIG_SERIAL_EXTENDED
1544 If you wish to use any non-standard features of the standard "dumb"
1545 driver, say Y here. This includes HUB6 support, shared serial
1546 interrupts, special multiport support, support for more than the
1547 four COM 1/2/3/4 boards, etc.
1549 Note that the answer to this question won't directly affect the
1550 kernel: saying N will just cause this configure script to skip all
1551 the questions about serial driver options. If unsure, say N.
1553 Support more than 4 serial ports
1554 CONFIG_SERIAL_MANY_PORTS
1555 Say Y here if you have dumb serial boards other than the four
1556 standard COM 1/2/3/4 ports. This may happen if you have an AST
1557 FourPort, Accent Async, Boca (read the Boca mini-HOWTO, available
1558 via FTP (user: anonymous) from
1559 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini), or other custom
1560 serial port hardware which acts similar to standard serial port
1561 hardware. If you only use the standard COM 1/2/3/4 ports, you can
1562 say N here to save some memory. You can also say Y if you have an
1563 "intelligent" multiport card such as Cyclades, Digiboards, etc.
1565 Support for sharing serial interrupts
1566 CONFIG_SERIAL_SHARE_IRQ
1567 Some serial boards have hardware support which allows multiple dumb
1568 serial ports on the same board to share a single IRQ. To enable
1569 support for this in the serial driver, say Y here.
1571 Auto detect IRQ on standard ports (unsafe)
1572 CONFIG_SERIAL_DETECT_IRQ
1573 Say Y here if you want the kernel to try to guess which IRQ
1574 to use for your serial port.
1576 This is considered unsafe; it is far better to configure the IRQ in
1577 a boot script using the setserial command.
1581 Support special multiport boards
1582 CONFIG_SERIAL_MULTIPORT
1583 Some multiport serial ports have special ports which are used to
1584 signal when there are any serial ports on the board which need
1585 servicing. Say Y here to enable the serial driver to take advantage
1586 of those special I/O ports.
1588 SGI Zilog85C30 serial support
1590 If you want to use your SGI's built-in serial ports under Linux,
1593 SGI Newport Graphics support
1594 CONFIG_SGI_NEWPORT_GFX
1595 If you have an SGI machine and you want to compile the graphics
1596 drivers, say Y here. This will include the code for the
1597 /dev/graphics and /dev/gfx drivers into the kernel for supporting
1598 virtualized access to your graphics hardware.
1600 Support the Bell Technologies HUB6 card
1602 Say Y here to enable support in the dumb serial driver to support
1607 Find out whether you have a PCI motherboard. PCI is the name of a
1608 bus system, i.e. the way the CPU talks to the other stuff inside
1609 your box. Other bus systems are ISA, EISA, Microchannel (MCA) or
1610 VESA. If you have PCI, say Y, otherwise N.
1612 The PCI-HOWTO, available via FTP (user: anonymous) in
1613 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO, contains valuable
1614 information about which PCI hardware does work under Linux and which
1619 On PCI systems, the BIOS can be used to detect the PCI devices and
1620 determine their configuration. However, some old PCI motherboards
1621 have BIOS bugs and may crash if this is done. Also, some embedded
1622 PCI-based systems don't have any BIOS at all. Linux can also try to
1623 detect the PCI hardware directly without using the BIOS.
1625 With this option, you can specify how Linux should detect the PCI
1626 devices. If you choose "BIOS", the BIOS will be used, if you choose
1627 "Direct", the BIOS won't be used, and if you choose "Any", the
1628 kernel will try the direct access method and falls back to the BIOS
1629 if that doesn't work. If unsure, go with the default.
1633 If you have a broken BIOS, it may fail to set up the PCI bus in a
1634 correct or optimal fashion. Saying Y here will correct that problem.
1635 If your BIOS is fine you can say N here for a very slightly smaller
1636 kernel. If unsure, say Y.
1638 PCI bridge optimization (experimental)
1640 This can improve access times for some hardware devices if you have
1641 a really broken BIOS and your computer uses a PCI bus system. Say Y
1642 if you think it might help, but try turning it off if you experience
1643 any problems with the PCI bus. N is the safe answer.
1645 Backward-compatible /proc/pci
1647 Older kernels supported a /proc/pci file containing brief textual
1648 descriptions of all PCI devices in the system. Several programs
1649 tried to parse this file, so it became almost impossible to add new
1650 fields without breaking compatibility. So a new /proc interface to
1651 PCI (/proc/bus/pci) has been implemented and the old one is
1652 supported for compatibility reasons only; you'll get the old one (in
1653 addition to the new one) if you say Y here and to "/proc filesystem
1654 support", below. If unsure, say Y. If you say N, you'll only get the
1655 new /proc/bus/pci interface.
1659 MicroChannel Architecture is found in some IBM PS/2 machines and
1660 laptops. It is a bus system similar to PCI or ISA. See
1661 Documentation/mca.txt (and especially the web page given there)
1662 before attempting to build an MCA bus kernel.
1664 SGI Visual Workstation support
1666 The SGI Visual Workstation series is an IA32-based workstation
1667 based on SGI systems chips with some legacy PC hardware attached.
1668 Say Y here to create a kernel to run on the SGI 320 or 540.
1669 A kernel compiled for the Visual Workstation will not run on other
1670 PC boards and vice versa.
1671 See Documentation/sgi-visws.txt for more.
1673 SGI Visual Workstation framebuffer support
1675 SGI Visual Workstation support for framebuffer graphics.
1679 The Intelligent Input/Output (I2O) architecture allows
1680 hardware drivers to be split into two parts: an operating system
1681 specific module called the OSM and an hardware specific module
1682 called the HDM. The OSM can talk to a whole range of HDM's, and
1683 ideally the HDM's are not OS dependent. This allows for the same
1684 driver to be used under different operating systems if the relevant
1685 OSM is in place. If you say Y here, you will get a choice of OSM's
1686 with the following questions.
1688 This support is also available as a module ( = code which can be
1689 inserted in and removed from the running kernel whenever you want).
1690 If you want to compile it as a module, say M here and read
1691 Documentation/modules.txt.
1697 Build in support for PCI bus I2O interface adapters. Currently this
1698 is the only variety supported.
1702 Include support for the I2O Block OSM. The Block OSM presents disk and
1703 other structured block devices to the operating system.
1707 Include support for the LAN OSM. You will also need to include support
1708 for token ring or fddi if you wish to use token ring or FDDI I2O cards
1713 Allow direct scsi access to scsi devices on a SCSI or FibreChannel I2O
1714 controller. You can use both the SCSI and Block OSM together if you wish.
1718 Inter Process Communication is a suite of library functions and
1719 system calls which let processes (running programs) synchronize
1720 and exchange information. It is generally considered to be a good
1721 thing, and some programs won't run unless you say Y here. In
1722 particular, if you want to run the DOS emulator dosemu under Linux
1723 (read the DOSEMU-HOWTO, available via FTP (user: anonymous) in
1724 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO), you'll need to say Y
1727 You can find documentation about IPC with "info ipc" and also in
1728 section 6.4 of the Linux Programmer's Guide, available via FTP
1729 (user: anonymous) from
1730 ftp://metalab.unc.edu/pub/Linux/docs/LDP/programmers-guide.
1732 Saying Y here enlarges your kernel by about 7 KB. Just say Y.
1734 BSD Process Accounting
1735 CONFIG_BSD_PROCESS_ACCT
1736 If you say Y here, a user level program will be able to instruct the
1737 kernel (via a special system call) to write process accounting
1738 information to a file: whenever a process exits, information about
1739 that process will be appended to the file by the kernel. The
1740 information includes things such as creation time, owning user,
1741 command name, memory usage, controlling terminal etc. (the complete
1742 list is in the struct acct in include/linux/acct.h). It is up to the
1743 user level program to do useful things with this information. This
1744 is generally a good idea, so say Y.
1748 The sysctl interface provides a means of dynamically changing
1749 certain kernel parameters and variables on the fly without requiring
1750 a recompile of the kernel or reboot of the system. The primary
1751 interface consists of a system call, but if the /proc filesystem is
1752 enabled, a tree of modifiable sysctl entries will be generated
1753 beneath the /proc/sys directory. They are explained in the files in
1754 Documentation/sysctl/. Note that enabling this option will enlarge
1755 the kernel by at least 8 KB.
1757 As it is generally a good thing, you should say Y here unless
1758 building a kernel for install/rescue disks or your system is very
1761 Kernel support for ELF binaries
1763 ELF (Executable and Linkable Format) is a format for libraries and
1764 executables used across different architectures and operating
1765 systems. Saying Y here will enable your kernel to run ELF binaries
1766 and enlarge it by about 2 KB. ELF support under Linux has now all
1767 but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC)
1768 because it is portable (this does *not* mean that you will be able
1769 to run executables from different architectures or operating systems
1770 however) and makes building run-time libraries very easy. Many new
1771 executables are distributed solely in ELF format. You definitely
1774 Information about ELF is contained in the ELF HOWTO available via
1775 FTP (user: anonymous) at ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
1777 If you find that after upgrading from Linux kernel 1.2 and saying Y
1778 here, you still can't run any ELF binaries (they just crash), then
1779 you'll have to install the newest ELF runtime libraries, including
1780 ld.so (check the file Documentation/Changes for location and latest
1783 If you want to compile this as a module ( = code which can be
1784 inserted in and removed from the running kernel whenever you want),
1785 say M here and read Documentation/modules.txt. The module will be
1786 called binfmt_elf.o. Saying M or N here is dangerous because some
1787 crucial programs on your system might be in ELF format.
1789 Kernel support for A.OUT binaries
1791 A.out (Assembler.OUTput) is a set of formats for libraries and
1792 executables used in the earliest versions of UNIX. Linux used the
1793 a.out formats QMAGIC and ZMAGIC until they were replaced with the
1796 As more and more programs are converted to ELF, the use for a.out
1797 will gradually diminish. If you disable this option it will reduce
1798 your kernel by one page. This is not much and by itself does not
1799 warrant removing support. However its removal is a good idea if you
1800 wish to ensure that absolutely none of your programs will use this
1801 older executable format. If you don't know what to answer at this
1802 point then answer Y. If someone told you "You need a kernel with
1803 QMAGIC support" then you'll have to say Y here. You may answer M to
1804 compile a.out support as a module and later load the module when you
1805 want to use a program or library in a.out format. The module will be
1806 called binfmt_aout.o. Saying M or N here is dangerous though,
1807 because some crucial programs on your system might still be in A.OUT
1810 Kernel support for Linux/Intel ELF binaries
1812 Say Y here if you want to be able to execute Linux/Intel ELF
1813 binaries just like native Alpha binaries on your Alpha machine. For
1814 this to work, you need to have the emulator /usr/bin/em86 in place.
1815 You may answer M to compile the emulation support as a module and
1816 later load the module when you want to use a Linux/Intel binary. The
1817 module will be called binfmt_em86.o. If unsure, say Y.
1819 Kernel support for MISC binaries
1821 If you say Y here, it will be possible to plug wrapper-driven binary
1822 formats into the kernel. You will like this especially when you use
1823 programs that need an interpreter to run like Java, Python or
1824 Emacs-Lisp. It's also useful if you often run DOS executables under
1825 the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available in
1826 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO). Once you have
1827 registered such a binary class with the kernel, you can start one of
1828 those programs simply by typing in its name at a shell prompt; Linux
1829 will automatically feed it to the correct interpreter.
1831 If you say Y here, you won't need "Kernel support for JAVA binaries"
1832 (CONFIG_BINFMT_JAVA) or "Kernel support for Linux/Intel ELF
1833 binaries" (CONFIG_BINFMT_EM86), as this is a more general solution.
1835 You can do other nice things, too. Read
1836 Documentation/binfmt_misc.txt to learn how to use this feature, and
1837 Documentation/java.txt for information about how to include Java
1840 You must say Y to "proc filesystem support" (CONFIG_PROC_FS) to
1841 use this part of the kernel.
1843 You may say M here for module support and later load the module when
1844 you have use for it; the module is called binfmt_misc.o. If you
1845 don't know what to answer at this point, say Y.
1847 Solaris binary emulation
1849 This is experimental code which will enable you to run (many)
1850 Solaris binaries on your SPARC Linux machine.
1852 This code is also available as a module ( = code which can be
1853 inserted in and removed from the running kernel whenever you want).
1854 The module will be called solaris.o. If you want to compile it as a
1855 module, say M here and read Documentation/modules.txt.
1859 This is the processor type of your CPU. This information is used for
1860 optimizing purposes. In order to compile a kernel that can run on
1861 all x86 CPU types (albeit not optimally fast), you can specify
1864 If you specify one of "486" or "586" or "Pentium" or "PPro", then
1865 the kernel will not necessarily run on earlier architectures (e.g. a
1866 Pentium optimized kernel will run on a PPro, but not necessarily on
1869 Here are the settings recommended for greatest speed:
1870 - "386" for the AMD/Cyrix/Intel 386DX/DXL/SL/SLC/SX, Cyrix/TI
1871 486DLC/DLC2 and UMC 486SX-S. Only "386" kernels will run on a 386
1873 - "486" for the AMD/Cyrix/IBM/Intel DX4 or 486DX/DX2/SL/SX/SX2,
1874 AMD/Cyrix 5x86, NexGen Nx586 and UMC U5D or U5S.
1875 - "586" for generic Pentium CPUs, possibly lacking the TSC
1876 (time stamp counter) register.
1877 - "Pentium" for the Intel Pentium/Pentium MMX, AMD K5, K6 and
1879 - "PPro" for the Cyrix/IBM/National Semiconductor 6x86MX, MII and
1880 Intel Pentium II/Pentium Pro.
1882 If you don't know what to do, choose "386".
1886 Saying Y here will allow you to use Linux in text mode through a
1887 display that complies with the generic VGA standard. Virtually
1888 everyone wants that.
1890 The program SVGATextMode can be used to utilize SVGA video cards to
1891 their full potential in text mode. Download it via FTP (user:
1892 anonymous) from ftp://metalab.unc.edu/pub/Linux/utils/console.
1896 Video mode selection support
1898 This enables support for text mode selection on kernel startup. If
1899 you want to take advantage of some high-resolution text mode your
1900 card's BIOS offers, but the traditional Linux utilities like
1901 SVGATextMode don't, you can say Y here and set the mode using the
1902 "vga=" option from your boot loader (lilo or loadlin) or set
1903 "vga=ask" which brings up a video mode menu on kernel startup. Try
1904 "man bootparam" or see the documentation of your boot loader about
1905 how to pass options to the kernel. The lilo procedure is also
1906 explained in the SCSI-HOWTO, available via FTP (user: anonymous) in
1907 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Read
1908 Documentation/svga.txt for more information about the Video mode
1909 selection support. If unsure, say N.
1911 Support for frame buffer devices (EXPERIMENTAL)
1913 The frame buffer device provides an abstraction for the graphics
1914 hardware. It represents the frame buffer of some video hardware and
1915 allows application software to access the graphics hardware through
1916 a well-defined interface, so the software doesn't need to know
1917 anything about the low-level (hardware register) stuff.
1919 Frame buffer devices work identically across the different
1920 architectures supported by Linux and make the implementation of
1921 application programs easier and more portable; at this point, an X
1922 server exists which uses the frame buffer device exclusively.
1923 On several non-X86 architectures, the frame buffer device is the
1924 only way to use the graphics hardware.
1926 The device is accessed through special device nodes, usually located
1927 in the /dev directory, i.e. /dev/fb*.
1929 You need an utility program called fbset to make full use of frame
1930 buffer devices. Please read Documentation/fb/framebuffer.txt and the
1931 Framebuffer-HOWTO at
1932 http://www.tahallah.demon.co.uk/programming/prog.html for more
1935 Say Y here and to the driver for your graphics board below if you
1936 are compiling a kernel for a non-x86 architecture.
1938 If you are compiling for the x86 architecture, you can say Y if you
1939 want to play with it, but it is not essential. Please note that
1940 running graphical applications that directly touch the hardware
1941 (e.g. an accelerated X server) and that are not frame buffer
1942 device-aware may cause unexpected results. If unsure, say N.
1946 This is the frame buffer device driver for the Acorn VIDC graphics
1949 Apollo frame buffer device
1951 This is the frame buffer device driver for the monochrome graphics
1952 hardware found in some Apollo workstations.
1954 Amiga native chipset support
1956 This is the frame buffer device driver for the builtin graphics
1957 chipset found in Amigas.
1959 Amiga OCS chipset support
1961 This enables support for the original Agnus and Denise video chips,
1962 found in the Amiga 1000 and most A500's and A2000's. If you intend
1963 to run Linux on any of these systems, say Y; otherwise say N.
1965 Amiga ECS chipset support
1967 This enables support for the Enhanced Chip Set, found in later
1968 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
1969 you intend to run Linux on any of these systems, say Y; otherwise
1972 Amiga AGA chipset support
1974 This enables support for the Advanced Graphics Architecture (also
1975 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
1976 and CD32. If you intend to run Linux on any of these systems, say Y;
1979 Amiga CyberVision support
1981 This enables support for the Cybervision 64 graphics card from
1982 Phase5. Please note that its use is not all that intuitive (i.e. if
1983 you have any questions, be sure to ask!). Say N unless you have a
1984 Cybervision 64 or plan to get one before you next recompile the
1985 kernel. Please note that this driver DOES NOT support the
1986 Cybervision 64 3D card, as they use incompatible video chips.
1988 Amiga CyberVision3D support (EXPERIMENTAL)
1990 This enables support for the Cybervision 64/3D graphics card from
1991 Phase5. Please note that its use is not all that intuitive (i.e. if
1992 you have any questions, be sure to ask!). Say N unless you have a
1993 Cybervision 64/3D or plan to get one before you next recompile the
1994 kernel. Please note that this driver DOES NOT support the older
1995 Cybervision 64 card, as they use incompatible video chips.
1997 Amiga RetinaZ3 support (EXPERIMENTAL)
1999 This enables support for the Retina Z3 graphics card. Say N unless
2000 you have a Retina Z3 or plan to get one before you next recompile
2003 Amiga CLgen driver (EXPERIMENTAL)
2005 This enables support for Cirrus Logic GD542x/543x based boards on
2006 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
2007 Say N unless you have such a graphics board or plan to get one
2008 before you next recompile the kernel.
2012 Say Y here if you want to run Linux on an MC680x0-based Apollo
2013 Domain workstation such as the DN3500.
2015 Apollo 3c505 support
2016 CONFIG_APOLLO_ELPLUS
2017 Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
2018 If you don't have one made for Apollos, you can use one from a PC,
2019 except that your Apollo won't be able to boot from it (because the
2020 code in the ROM will be for a PC).
2022 Atari native chipset support
2024 This is the frame buffer device driver for the builtin graphics
2025 chipset found in Ataris.
2027 Open Firmware frame buffer device support
2029 Say Y if you want support with Open Firmware for your graphics
2032 S3 Trio frame buffer device support
2034 If you have a S3 Trio say Y. Say N for S3 Virge.
2036 ATI Mach64 display support
2038 This driver supports graphics boards with the ATI Mach64 chips.
2040 PowerMac "control" frame buffer device support
2042 This driver supports a frame buffer for the graphics adapter in the
2043 Power Macintosh 7300 and others.
2045 PowerMac "platinum" frame buffer device support
2047 This driver supports a frame buffer for the "platinum" graphics
2048 adapter in some Power Macintoshes.
2050 PowerMac "valkyrie" frame buffer device support
2052 This driver supports a frame buffer for the "valkyrie" graphics
2053 adapter in some Power Macintoshes.
2055 Chips 65550 display support
2057 This is the frame buffer device driver for the Chips & Technologies
2058 65550 graphics chip in PowerBooks.
2060 Mac frame buffer device
2062 This is the frame buffer device driver for the graphics hardware in
2065 HP300 frame buffer device
2067 This is the frame buffer device driver for the Topcat graphics
2068 hardware found in HP300 workstations.
2070 TGA frame buffer support
2072 This is the frame buffer device driver for generic TGA graphic
2073 cards. Say Y if you have one of those.
2075 VESA VGA graphics console
2077 This is the frame buffer device driver for generic VESA 2.0
2078 compliant graphic cards. The older VESA 1.2 cards are not supported.
2079 You will get a boot time penguin logo at no additional cost. Please
2080 read Documentation/fb/vesafb.txt. If unsure, say Y.
2082 VGA 16-color graphics console
2084 This is the frame buffer device driver for VGA 16 color graphic
2085 cards. Say Y if you have such a card.
2087 Backward compatibility mode for Xpmac
2088 CONFIG_FB_COMPAT_XPMAC
2089 If you use the Xpmac X server (common with mklinux), you'll need to
2090 say Y here to use X. You should consider changing to XFree86 which
2091 includes a server that supports the frame buffer device directly
2094 Matrox unified accelerated driver
2096 Say Y here if you have Matrox Millennium, Matrox Millennium II,
2097 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
2098 Mystique G200, Matrox Millennium G200 or Matrox Marvel G200 video
2099 card in your box. At this time, support for the G100, Mystique G200
2100 and Marvel G200 is untested.
2102 This driver is also available as a module ( = code which can be
2103 inserted and removed from the running kernel whenever you want).
2104 The module will be called matroxfb.o. If you want to compile it as
2105 a module, say M here and read Documentation/modules.txt.
2107 You can pass several parameters to the driver at boot time or at
2108 module load time. The parameters look like "video=matrox:XXX", where
2109 the meaning of XXX can be found at the end of the main source file
2110 (drivers/video/matroxfb.c). Please see the file
2111 Documentation/fb/matroxfb.txt.
2113 Matrox Millennium support
2114 CONFIG_FB_MATROX_MILLENIUM
2115 Say Y here if you have a Matrox Millennium or Matrox Millennium II
2116 video card. If you select "Advanced lowlevel driver options" below,
2117 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
2118 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
2119 also use font widths different from 8.
2121 Matrox Mystique support
2122 CONFIG_FB_MATROX_MYSTIQUE
2123 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
2124 video card. If you select "Advanced lowlevel driver options" below,
2125 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
2126 packed pixel and 32 bpp packed pixel. You can also use font widths
2129 Matrox G100/G200 support
2130 CONFIG_FB_MATROX_G100
2131 Say Y here if you have a Matrox Productiva G100, Matrox Mystique
2132 G200, Matrox Marvel G200 or Matrox Millennium G200 video card. If
2133 you select "Advanced lowlevel driver options", you should check 8
2134 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed pixel and 32
2135 bpp packed pixel. You can also use font widths different from 8.
2137 Matrox unified driver multihead support
2138 CONFIG_FB_MATROX_MULTIHEAD
2139 Say Y here if you have more than one (supported) Matrox device in
2140 your computer and you want to use all of them. If you have only one
2141 device, you should say N because the driver compiled with Y is
2142 larger and a bit slower, especially on ia32 (ix86).
2144 If you said M to "Matrox unified accelerated driver" and N here, you
2145 will still be able to use several Matrox devices simultaneously.
2146 This is slightly faster but uses 40 KB of kernel memory per Matrox
2147 card. You do this by inserting several instances of the module
2148 matroxfb.o into the kernel with insmod, supplying the parameter
2149 "dev=N" where N is 0, 1, etc. for the different Matrox devices.
2151 MDA text console (dual-headed)
2153 Say Y here if you have an old MDA or monochrome Hercules graphics
2154 adapter in your system acting as a second head ( = video card). You
2155 will then be able to use two monitors with your Linux system. Do not
2156 say Y here if your MDA card is the primary card in your system; the
2157 normal VGA driver will handle it.
2159 This driver is also available as a module ( = code which can be
2160 inserted and removed from the running kernel whenever you want).
2161 The module will be called mdacon.o. If you want to compile it as
2162 a module, say M here and read Documentation/modules.txt.
2166 SBUS and UPA frame buffers
2168 Say Y if you want support for SBUS or UPA based frame buffer device.
2170 Creator/Creator3D support
2172 This is the frame buffer device driver for the Creator and Creator3D
2175 CGsix (GX,TurboGX) support
2177 This is the frame buffer device driver for the CGsix (GX, TurboGX)
2182 This is the frame buffer device driver for the BWtwo frame buffer.
2186 This is the frame buffer device driver for the CGthree frame buffer.
2188 TCX (SS4/SS5 only) support
2190 This is the frame buffer device driver for the TCX 24/8bit frame
2193 Virtual Frame Buffer support (ONLY FOR TESTING!)
2195 This is a `virtual' frame buffer device. It operates on a chunk of
2196 unswapable kernel memory instead of on the memory of a graphics
2197 board. This means you cannot see any output sent to this frame
2198 buffer device, while it does consume precious memory. The main use
2199 of this frame buffer device is testing and debugging the frame
2200 buffer subsystem. Do NOT enable it for normal systems! To protect
2201 the innocent, it has to be enabled explicitly at boot time using the
2202 kernel option `video=vfb:'.
2204 This driver is also available as a module ( = code which can be
2205 inserted and removed from the running kernel whenever you want). The
2206 module will be called vfb.o. If you want to compile it as a module,
2207 say M here and read Documentation/modules.txt.
2211 Advanced low level driver options
2212 CONFIG_FBCON_ADVANCED
2213 The frame buffer console uses character drawing routines that are
2214 tailored to the specific organization of pixels in the memory of
2215 your graphics hardware. These are called the low level frame buffer
2216 console drivers. Note that they are used for text console output
2217 only; they are NOT needed for graphical applications.
2219 If you say N here, the needed low level drivers are automatically
2220 enabled, depending on what frame buffer devices you selected above.
2221 This is recommended for most users.
2223 If you say Y here, you have more fine-grained control over which low
2224 level drivers are enabled. You can e.g. leave out low level drivers
2225 for color depths you do not intend to use for text consoles.
2227 Low level frame buffer console drivers can be modules ( = code which
2228 can be inserted and removed from the running kernel whenever you
2229 want). The modules will be called fbcon-*.o. If you want to compile
2230 (some of) them as modules, read Documentation/modules.txt.
2236 This is the low level frame buffer console driver for monochrome
2237 (2 colors) packed pixels.
2239 2 bpp packed pixels support
2241 This is the low level frame buffer console driver for 2 bits per
2242 pixel (4 colors) packed pixels.
2244 4 bpp packed pixels support
2246 This is the low level frame buffer console driver for 4 bits per
2247 pixel (16 colors) packed pixels.
2249 8 bpp packed pixels support
2251 This is the low level frame buffer console driver for 8 bits per
2252 pixel (256 colors) packed pixels.
2254 16 bpp packed pixels support
2256 This is the low level frame buffer console driver for 15 or 16 bits
2257 per pixel (32K or 64K colors, also known as `hicolor') packed
2260 24 bpp packed pixels support
2262 This is the low level frame buffer console driver for 24 bits per
2263 pixel (16M colors, also known as `truecolor') packed pixels. It is
2264 NOT for `sparse' 32 bits per pixel mode.
2266 32 bpp packed pixels support
2268 This is the low level frame buffer console driver for 32 bits per
2269 pixel (16M colors, also known as `truecolor') sparse packed pixels.
2271 Amiga bitplanes support
2273 This is the low level frame buffer console driver for 1 to 8
2274 bitplanes (2 to 256 colors) on Amiga.
2276 Amiga interleaved bitplanes support
2278 This is the low level frame buffer console driver for 1 to 8
2279 interleaved bitplanes (2 to 256 colors) on Amiga.
2281 Atari interleaved bitplanes (2 planes) support
2282 CONFIG_FBCON_IPLAN2P2
2283 This is the low level frame buffer console driver for 2 interleaved
2284 bitplanes (4 colors) on Atari.
2286 Atari interleaved bitplanes (4 planes) support
2287 CONFIG_FBCON_IPLAN2P4
2288 This is the low level frame buffer console driver for 4 interleaved
2289 bitplanes (16 colors) on Atari.
2291 Atari interleaved bitplanes (8 planes) support
2292 CONFIG_FBCON_IPLAN2P8
2293 This is the low level frame buffer console driver for 8 interleaved
2294 bitplanes (256 colors) on Atari.
2296 Mac variable bpp packed pixels support
2298 This is the low level frame buffer console driver for 1/2/4/8/16/32
2299 bits per pixel packed pixels on Mac. It supports variable font
2300 widths for low resolution screens.
2302 VGA characters/attributes support
2304 This is the low level frame buffer console driver for VGA text mode;
2305 it is used if you said Y to "VGA chipset support (text only)" above.
2307 Parallel-port support
2309 If you want to use devices connected to your machine's parallel port
2310 (the connector at the computer with 25 holes), e.g. printer, ZIP
2311 drive, PLIP link (Parallel Line Internet Protocol is mainly used to
2312 create a mini network by connecting the parallel ports of two local
2313 machines) etc., then you need to say Y here; please read
2314 Documentation/parport.txt and drivers/misc/BUGS-parport.
2316 For extensive information about drivers for many devices attaching
2317 to the parallel port see http://www.torque.net/linux-pp.html on the
2318 WWW (to browse the WWW, you need to have access to a machine on the
2319 Internet that has a program like lynx or netscape).
2321 It is possible to share a single parallel port among several devices
2322 and it is safe to compile all the corresponding drivers into the
2323 kernel. If you want to compile parallel port support as a module ( =
2324 code which can be inserted in and removed from the running kernel
2325 whenever you want), say M here and read Documentation/modules.txt.
2326 The module will be called parport.o. If you have more than one
2327 parallel port and want to specify which port and IRQ to be used by
2328 this driver at module load time, take a look at
2329 Documentation/networking/parport.txt.
2335 You should say Y here if you have a PC-style parallel port. All IBM
2336 PC compatible computers and some Alphas have PC-style parallel
2339 This code is also available as a module. If you want to compile it
2340 as a module ( = code which can be inserted in and removed from the
2341 running kernel whenever you want), say M here and read
2342 Documentation/modules.txt. The module will be called parport_pc.o.
2346 Use FIFO/DMA if available
2347 CONFIG_PARPORT_PC_FIFO
2348 Many parallel port chipsets provide hardware that can speed up
2349 printing. Say Y here if you want to take advantage of that.
2351 As well as actually having a FIFO, or DMA capability, the kernel
2352 will need to know which IRQ the parallel port has. By default,
2353 parallel port interrupts will not be used, and so neither will the
2354 FIFO. See Documentation/parport.txt to find out how to specify
2355 which IRQ/DMA to use.
2357 Support foreign hardware
2358 CONFIG_PARPORT_OTHER
2359 Say Y here if you want to be able to load driver modules to support
2360 other non-standard types of parallel ports. This causes a
2361 performance loss, so most people say N.
2363 Sun Ultra/AX-style hardware
2365 Say Y here if you need support for the parallel port hardware on Sun
2366 Ultra/AX machines. This code is also available as a module (say M),
2367 called parport_ax.o. If in doubt, saying N is the safe plan.
2369 IEEE1284 transfer modes
2371 If you have a printer that supports status readback or device ID, or
2372 want to use a device that uses enhanced parallel port transfer modes
2373 such as EPP and ECP, say Y here to enable advanced IEEE 1284
2374 transfer modes. Also say Y if you want device ID information to
2375 appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
2377 Enable loadable module support
2379 Kernel modules are small pieces of compiled code which can be
2380 inserted in or removed from the running kernel, using the programs
2381 insmod and rmmod. This is described in the file
2382 Documentation/modules.txt, including the fact that you have to say
2383 "make modules" in order to compile the modules that you chose during
2384 kernel configuration. Modules can be device drivers, file systems,
2385 binary executable formats, and so on. If you think that you may want
2386 to make use of modules with this kernel in the future, then say Y
2387 here. If unsure, say Y.
2389 Set version information on all symbols for modules
2391 Usually, modules have to be recompiled whenever you switch to a new
2392 kernel. Saying Y here makes it possible, and safe, to use the
2393 same modules even after compiling a new kernel; this requires the
2394 program modprobe. All the software needed for module support is in
2395 the modutils package (check the file Documentation/Changes for
2396 location and latest version). NOTE: if you say Y here but don't
2397 have the program genksyms (which is also contained in the above
2398 mentioned modutils package), then the building of your kernel will
2399 fail. If you are going to use modules that are generated from
2400 non-kernel sources, you would benefit from this option. Otherwise
2401 it's not that important. So, N ought to be a safe bet.
2403 Kernel module loader support
2405 Normally when you have selected some drivers and/or filesystems to
2406 be created as loadable modules, you also have the responsibility to
2407 load the corresponding modules (using the programs insmod or
2408 modprobe) before you can use them. If you say Y here however, the
2409 kernel will be able to load modules for itself: when a part of the
2410 kernel needs a module, it runs modprobe with the appropriate
2411 arguments, thereby loading the module if it is available. (This is a
2412 replacement for kerneld.) Say Y here and read about configuring it
2413 in Documentation/kmod.txt.
2415 ARP daemon support (EXPERIMENTAL)
2417 Normally, the kernel maintains an internal cache which maps IP
2418 addresses to hardware addresses on the local network, so that
2419 Ethernet/Token Ring/ etc. frames are sent to the proper address on
2420 the physical networking layer. For small networks having a few
2421 hundred directly connected hosts or less, keeping this address
2422 resolution (ARP) cache inside the kernel works well. However,
2423 maintaining an internal ARP cache does not work well for very large
2424 switched networks, and will use a lot of kernel memory if TCP/IP
2425 connections are made to many machines on the network.
2427 If you say Y here, the kernel's internal ARP cache will never grow
2428 to more than 256 entries (the oldest entries are expired in a LIFO
2429 manner) and communication will be attempted with the user space ARP
2430 daemon arpd. Arpd then answers the address resolution request either
2431 from its own cache or by asking the net.
2433 This code is experimental. If you do say Y here, you should obtain a
2434 copy of arpd from http://www.loran.com/~layes/arpd/index.html, and
2435 you should also say Y to "Kernel/User network link driver", below.
2440 These are the protocols used on the Internet and on most local
2441 Ethernets. It is highly recommended to say Y here (this will enlarge
2442 your kernel by about 35 KB), since some programs (e.g. the X window
2443 system) use TCP/IP even if your machine is not connected to any
2444 other computer. You will get the so-called loopback device which
2445 allows you to ping yourself (great fun, that!).
2447 For an excellent introduction to Linux networking, please read the
2448 NET-3-HOWTO, available via FTP (user: anonymous) from
2449 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
2451 This option is also necessary if you want to use the full power of
2452 term (term is a program which gives you almost full Internet
2453 connectivity if you have a regular dial up shell account on some
2454 Internet connected Unix computer; for more information, read
2455 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html).
2457 If you say Y here and also to "/proc filesystem support" and "Sysctl
2458 support" below, you can change various aspects of the behavior of
2459 the TCP/IP code by writing to the (virtual) files in
2460 /proc/sys/net/ipv4/*; the options are explained in the file
2461 Documentation/Networking/ip-sysctl.txt.
2463 Short answer: say Y.
2467 This is code for addressing several networked computers at once,
2468 enlarging your kernel by about 2 kB. You need multicasting if you
2469 intend to participate in the MBONE, a high bandwidth network on top
2470 of the Internet which carries audio and video broadcasts. More
2471 information about the MBONE is on the WWW at
2472 http://www.best.com/~prince/techinfo/mbone.html (to browse the WWW,
2473 you need to have access to a machine on the Internet that has a
2474 program like lynx or netscape). Information about the multicast
2475 capabilities of the various network cards is contained in
2476 Documentation/networking/multicast.txt. For most people, it's safe
2480 CONFIG_IP_ADVANCED_ROUTER
2481 If you intend to run your Linux box mostly as a router, i.e. as a
2482 computer that forwards and redistributes network packets, say Y; you
2483 will then be presented with several options that allow more precise
2484 control about the routing process.
2486 The answer to this question won't directly affect the kernel:
2487 answering N will just cause this configure script to skip all the
2488 questions about advanced routing.
2490 Note that your box can only act as a router if you enable IP
2491 forwarding in your kernel; you can do that by saying Y to "/proc
2492 filesystem support" and "Sysctl support" below and executing the
2495 echo "1" > /proc/sys/net/ipv4/ip_forward
2497 at boot time after the /proc filesystem has been mounted.
2499 If you turn on IP forwarding, you will also get the rp_filter, which
2500 automatically rejects incoming packets if the routing table entry
2501 for their source address doesn't match the network interface they're
2502 arriving on. This has security advantages because it prevents the
2503 so-called IP spoofing, however it can pose problems if you use
2504 asymmetric routing (packets from you to a host take a different path
2505 than packets from that host to you) or if you operate a non-routing
2506 host which has several IP addresses on different interfaces. To turn
2509 echo 0 > /proc/sys/net/ipv4/conf/<device>/rp_filter
2511 echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter
2513 If unsure, say N here.
2516 CONFIG_IP_MULTIPLE_TABLES
2517 Normally, a router decides what to do with a received packet based
2518 solely on the packet's final destination address. If you say Y here,
2519 the Linux router will also be able to take the packet's source
2520 address into account. Furthermore, if you also say Y to "IP: use TOS
2521 value as routing key" below, the TOS (Type-Of-Service) field of the
2522 packet can be used for routing decisions as well. In addition, if
2523 you say Y here and to "IP: fast network address translation" below,
2524 the router will also be able to modify source and destination
2525 addresses of forwarded packets.
2527 If you are interested in this, please see the preliminary
2528 documentation at http://www.compendium.com.ar/policy-routing.txt and
2529 ftp://post.tepkom.ru/pub/vol2/Linux/docs/advanced-routing.tex. You
2530 will need supporting software from ftp://ftp.inr.ac.ru/ip-routing/
2534 IP: equal cost multipath
2535 CONFIG_IP_ROUTE_MULTIPATH
2536 Normally, the routing tables specify a single action to be taken in
2537 a deterministic manner for a given packet. If you say Y here
2538 however, it becomes possible to attach several actions to a packet
2539 pattern, in effect specifying several alternative paths to travel
2540 for those packets. The router considers all these paths to be of
2541 equal "cost" and chooses one of them in a non-deterministic fashion
2542 if a matching packet arrives.
2544 IP: use TOS value as routing key
2546 The header of every IP packet carries a TOS (Type of Service) value
2547 with which the packet requests a certain treatment, e.g. low latency
2548 (for interactive traffic), high throughput, or high reliability. If
2549 you say Y here, you will be able to specify different routes for
2550 packets with different TOS values.
2552 IP: use FWMARK value as routing key
2553 CONFIG_IP_ROUTE_FWMARK
2554 If you say Y here, you will be able to specify different routes for
2555 packets with different FWMARK ("firewalling mark") values
2556 (see ipchains(8), "-m" argument).
2558 IP: verbose route monitoring
2559 CONFIG_IP_ROUTE_VERBOSE
2560 If you say Y here, which is recommended, then the kernel will print
2561 verbose messages regarding the routing, for example warnings about
2562 received packets which look strange and could be evidence of an
2563 attack or a misconfigured system somewhere. The information is
2564 handled by the klogd daemon which is responsible for kernel messages
2567 IP: large routing tables
2568 CONFIG_IP_ROUTE_LARGE_TABLES
2569 If you have routing zones that grow to more than about 64 entries,
2570 you may want to say Y here to speed up the routing process.
2572 IP: fast network address translation
2574 If you say Y here, your router will be able to modify source and
2575 destination addresses of packets that pass through it, in a manner
2576 you specify. General information about Network Address Translation
2577 can be gotten from the document
2578 http://www.csn.tu-chemnitz.de/~mha/linux-ip-nat/diplom/nat.html
2580 IP: optimize as router not host
2582 Some Linux network drivers use a technique called copy and checksum
2583 to optimize host performance. For a machine which acts as a router
2584 most of the time and is forwarding most packets to another host this
2585 is however a loss. If you say Y here, copy and checksum will be
2586 switched off. In the future, it may make other changes which
2587 optimize for router operation.
2589 Note that your box can only act as a router if you enable IP
2590 forwarding in your kernel; you can do that by saying Y to "/proc
2591 filesystem support" and "Sysctl support" below and executing the
2594 echo "1" > /proc/sys/net/ipv4/ip_forward
2596 at boot time after the /proc filesystem has been mounted. You can do
2597 that even if you say N here.
2599 If unsure, say N here.
2603 If you want to configure your Linux box as a packet filter firewall
2604 for a local TCP/IP based network, say Y here. You may want to read
2605 the FIREWALL-HOWTO, available via FTP (user: anonymous) in
2606 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
2608 Also, you will need the ipchains tool (available on the WWW at
2609 http://www.rustcorp.com/linux/ipchains/) to allow selective blocking
2610 of Internet traffic based on type, origin and destination.
2611 Note that the Linux firewall code has changed and the old program
2612 called ipfwadm won't work anymore. Please read the IPCHAINS-HOWTO.
2614 The type of firewall provided by ipchains and this kernel support is
2615 called a "packet filter". The other type of firewall, a
2616 "proxy-based" one, is more secure but more intrusive and more
2617 bothersome to set up; it inspects the network traffic much more
2618 closely, modifies it and has knowledge about the higher level
2619 protocols, which a packet filter lacks. Moreover, proxy-based
2620 firewalls often require changes to the programs running on the local
2621 clients. Proxy-based firewalls don't need support by the kernel, but
2622 they are often combined with a packet filter, which only works if
2625 The firewalling code will only work if IP forwarding is enabled in
2626 your kernel. You can do that by saying Y to "/proc filesystem
2627 support" and "Sysctl support" below and executing the line
2629 echo "1" > /proc/sys/net/ipv4/ip_forward
2631 at boot time after the /proc filesystem has been mounted.
2633 You need to say Y to "IP firewalling" in order to be able to use IP
2634 masquerading (masquerading means that local computers can chat with
2635 an outside host, but that outside host is made to think that it is
2636 talking to the firewall box -- makes the local network completely
2637 invisible to the outside world and avoids the need to allocate
2638 globally valid IP host addresses for the machines on the local net)
2639 and IP packet logging and accounting (keeping track of what is using
2640 all your network bandwidth) and IP transparent proxying (makes the
2641 computers on the local network think they're talking to a remote
2642 computer, while in reality the traffic is redirected by your Linux
2643 firewall to a local proxy server).
2645 If in doubt, say N here.
2647 IP: firewall packet netlink device
2648 CONFIG_IP_FIREWALL_NETLINK
2649 If you say Y here, you can use the ipchains tool to copy all or part
2650 of any packet you specify that hits your Linux firewall to optional
2651 user space monitoring software that can then look for attacks and
2652 take actions such as paging the administrator of the site.
2654 To use this, you need to create a character special file under /dev
2655 with major number 36 and minor number 3 using mknod ("man mknod"),
2656 and you need (to write) a program that reads from that device and
2657 takes appropriate action.
2659 IP: kernel level autoconfiguration
2661 This enables automatic configuration of IP addresses of devices and
2662 of the routing table during kernel boot, based on either information
2663 supplied at the kernel command line or by BOOTP or RARP protocols.
2664 You need to say Y only for diskless machines requiring network
2665 access to boot (in which case you want to say Y to "Root file system
2666 on NFS" as well), because all other machines configure the network
2667 in their startup scripts.
2671 If you want your Linux box to mount its whole root filesystem (the
2672 one containing the directory /) from some other computer over the
2673 net via NFS and you want the IP address of your computer to be
2674 discovered automatically at boot time using the BOOTP protocol (a
2675 special protocol designed for doing this job), say Y here. In case
2676 the boot ROM of your network card was designed for booting Linux and
2677 does BOOTP itself, providing all necessary information on the kernel
2678 command line, you can say N here. If unsure, say Y. Note that if you
2679 want to use BOOTP, a BOOTP server must be operating on your network.
2680 Read Documentation/nfsroot.txt for details.
2684 If you want your Linux box to mount its whole root filesystem (the
2685 one containing the directory /) from some other computer over the
2686 net via NFS and you want the IP address of your computer to be
2687 discovered automatically at boot time using the RARP protocol (an
2688 older protocol which is being obsoleted by BOOTP and DHCP), say Y
2689 here. Note that if you want to use RARP, a RARP server must be
2690 operating on your network. Read Documentation/nfsroot.txt for
2695 Tunneling means encapsulating data of one protocol type within
2696 another protocol and sending it over a channel that understands the
2697 encapsulating protocol. This particular tunneling driver implements
2698 encapsulation of IP within IP, which sounds kind of pointless, but
2699 can be useful if you want to make your (or some other) machine
2700 appear on a different network than it physically is, or to use
2701 mobile-IP facilities (allowing laptops to seamlessly move between
2702 networks without changing their IP addresses; check out
2703 http://anchor.cs.binghamton.edu/~mobileip/LJ/index.html).
2705 Saying Y to this option will produce two modules ( = code which can
2706 be inserted in and removed from the running kernel whenever you
2707 want). Most people won't need this and can say N.
2709 IP: GRE tunnels over IP
2711 Tunneling means encapsulating data of one protocol type within
2712 another protocol and sending it over a channel that understands the
2713 encapsulating protocol. This particular tunneling driver implements
2714 GRE (Generic Routing Encapsulation) and at this time allows
2715 encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
2716 This driver is useful if the other endpoint is a Cisco router: Cisco
2717 likes GRE much better than the other Linux tunneling driver ("IP:
2718 tunneling" above). In addition, GRE allows multicast redistribution
2721 IP: broadcast GRE over IP
2722 CONFIG_NET_IPGRE_BROADCAST
2723 One application of GRE/IP is to construct a broadcast WAN (Wide Area
2724 Network), which looks like a normal Ethernet LAN (Local Area
2725 Network), but can be distributed all over the Internet. If you want
2726 to do that, say Y here and to "IP: multicast routing" below.
2728 IP: transparent proxying
2729 CONFIG_IP_TRANSPARENT_PROXY
2730 This enables your Linux firewall to transparently redirect any
2731 network traffic originating from the local network and destined
2732 for a remote host to a local server, called a "transparent proxy
2733 server". This makes the local computers think they are talking to
2734 the remote end, while in fact they are connected to the local
2735 proxy. Redirection is activated by defining special input firewall
2736 rules (using the ipchains utility) and/or by doing an appropriate
2740 CONFIG_IP_MASQUERADE
2741 If one of the computers on your local network for which your Linux
2742 box acts as a firewall wants to send something to the outside, your
2743 box can "masquerade" as that computer, i.e. it forwards the traffic
2744 to the intended outside destination, but makes it look like it came
2745 from the firewall box itself. It works both ways: if the outside
2746 host replies, the Linux firewall will silently forward the traffic
2747 to the corresponding local computer. This way, the computers on your
2748 local net are completely invisible to the outside world, even though
2749 they can reach the outside and can receive replies. This makes it
2750 possible to have the computers on the local network participate on
2751 the Internet even if they don't have officially registered IP
2752 addresses. (This last problem can also be solved by connecting the
2753 Linux box to the Internet using SLiRP [SLiRP is a SLIP/PPP emulator
2754 that works if you have a regular dial up shell account on some UNIX
2755 computer; get it via FTP (user: anonymous) from
2756 ftp://metalab.unc.edu/pub/Linux/system/network/serial/ ].)
2758 The IP masquerading code will only work if IP forwarding is enabled
2759 in your kernel; you can do this by saying Y to "/proc
2760 filesystem support" and "Sysctl support" below and then executing a
2763 echo "1" > /proc/sys/net/ipv4/ip_forward
2765 from a boot time script after the /proc filesystem has been mounted.
2767 Details on how to set things up are contained in the IP Masquerade
2768 mini-HOWTO, available via FTP (user: anonymous) from
2769 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini; there's also some
2770 information on the WWW at
2771 http://www.tor.shaw.wave.ca/~ambrose/kernel21.html.
2773 If you say Y here, then the modules ip_masq_ftp.o (for ftp file
2774 transfers), ip_masq_irc.o (for irc chats), ip_masq_quake.o (you
2775 guessed it), ip_masq_vdolive.o (for VDOLive video connections),
2776 ip_masq_cuseeme.o (for CU-SeeMe broadcasts) and ip_masq_raudio.o
2777 (for RealAudio downloads) will automatically be compiled. They are
2778 needed to make masquerading for these protocols work. Modules are
2779 pieces of code which can be inserted in and removed from the running
2780 kernel whenever you want; read Documentation/modules.txt for
2783 IP: ICMP masquerading
2784 CONFIG_IP_MASQUERADE_ICMP
2785 The basic masquerade code described for "IP: masquerading" above
2786 only handles TCP or UDP packets (and ICMP errors for existing
2787 connections). This option adds additional support for masquerading
2788 ICMP packets, such as ping or the probes used by the Windows 95
2791 If you want this, say Y.
2793 IP: masquerading special modules support
2794 CONFIG_IP_MASQUERADE_MOD
2795 This provides support for special modules that can modify the
2796 rewriting rules used when masquerading. Please note that this
2797 feature adds a little overhead in the input packet processing chain.
2799 Examples of such modules are ipautofw (allowing the masquerading of
2800 protocols which don't have their own protocol helpers) and port
2801 forwarding (making an incoming port of a local computer visible
2802 through the masquerading host).
2804 You will need the user space program "ipmasqadm" to use these
2805 additional modules; you can download it from
2806 http://juanjox.linuxhq.com/
2808 All this additional code is still under development and so is
2809 currently marked EXPERIMENTAL.
2811 If you want to try, for example, PORT FORWARDING, say Y.
2813 IP: ipautofw masquerade support (Experimental)
2814 CONFIG_IP_MASQUERADE_IPAUTOFW
2815 ipautofw is a program which allows the masquerading of protocols
2816 which do not (as yet) have their own protocol helpers. Information
2817 and source for ipautofw is available via FTP (user: anonymous) from
2818 ftp://ftp.netis.com/pub/members/rlynch/
2820 You will also need the ipmasqadm tool available from
2821 http://juanjox.linuxhq.com/ .
2823 The ipautofw code is still under development and so is currently
2824 marked EXPERIMENTAL. If you want to try it, say Y.
2826 This code is also available as a module ( = code which can be
2827 inserted in and removed from the running kernel whenever you want).
2828 The module will be called ip_masq_autofw.o. If you want to compile
2829 it as a module, say M here and read Documentation/modules.txt.
2831 IP: ipportfw masquerade support
2832 CONFIG_IP_MASQUERADE_IPPORTFW
2833 Port Forwarding is an addition to IP Masquerading which allows some
2834 forwarding of packets from outside to inside a firewall on given
2835 ports. This could be useful if, for example, you want to run a web
2836 server behind the firewall or masquerading host and that web server
2837 should be accessible from the outside world. An external client
2838 sends a request to port 80 of the firewall, the firewall forwards
2839 this request to the web server, the web server handles the request
2840 and the results are sent through the firewall to the original
2841 client. The client thinks that the firewall machine itself is
2842 running the web server. This can also be used for load balancing if
2843 you have a farm of identical web servers behind the firewall.
2845 Information about this feature is available from
2846 http://www.monmouth.demon.co.uk/ipsubs/portforwarding.html (to
2847 browse the WWW, you need to have access to a machine on the Internet
2848 that has a program like lynx or netscape). For general info, please
2849 see ftp://ftp.compsoc.net/users/steve/ipportfw/linux21/
2851 You will need the user space program "ipmasqadm" which can be
2852 downloaded from http://juanjox.linuxhq.com/
2854 The portfw code is still under development and so is currently
2855 marked EXPERIMENTAL. If you want to try it, say Y.
2857 This code is also available as a module ( = code which can be
2858 inserted in and removed from the running kernel whenever you want).
2859 The module will be called ip_masq_portfw.o. If you want to compile
2860 it as a module, say M here and read Documentation/modules.txt.
2862 IP: ipmarkfw masquerade support
2863 CONFIG_IP_MASQUERADE_MFW
2864 Firewall Mark Forwarding provides functionality similar to port
2865 forwarding (see "IP: ipportfw masquerade support", above), the
2866 difference being that Firewall Mark Forwarding uses "firewalling
2867 mark" to select which packets must be forwarded (see ipchains(8),
2870 This code is still under development and so is currently marked
2871 EXPERIMENTAL. If you want to try it, say Y.
2873 This code is also available as a module ( = code which can be
2874 inserted in and removed from the running kernel whenever you want).
2875 The module will be called ip_masq_markfw.o. If you want to compile
2876 it as a module, say M here and read Documentation/modules.txt.
2878 IP: always defragment (required for masquerading)
2879 CONFIG_IP_ALWAYS_DEFRAG
2880 If you say Y here, then all incoming fragments (parts of IP packets
2881 that arose when some host between origin and destination decided
2882 that the packets were too large and cut them into pieces) will be
2883 reassembled (defragmented) before being processed, even if they are
2884 about to be forwarded.
2886 You must say Y here if you want to enable "IP: masquerading" or "IP:
2887 transparent proxying".
2889 When using "IP: firewalling" support, you might also want to say Y
2890 here, to have a more reliable firewall (otherwise second and further
2891 fragments must be dealt with by the firewall, which can be tricky).
2893 Only say Y here if running either a firewall that is the sole link
2894 to your network or a transparent proxy; never ever say Y here for a
2895 normal router or host.
2897 IP: aliasing support
2899 Sometimes it is useful to give several IP addresses to a single
2900 physical network interface (serial port or Ethernet card). The most
2901 common case is that you want to serve different WWW or ftp documents
2902 to the outside depending on which of your host names was used to
2903 connect to you. This is called "multihosting" or "virtual domains"
2904 or "virtual hosting services" and is explained in detail on the WWW
2905 at http://www.thesphere.com/~dlp/TwoServers/ (to browse the WWW, you
2906 need to have access to a machine on the Internet that has a program
2907 like lynx or netscape) and also in the Virtual-Services-HOWTO,
2908 available via FTP (user: anonymous) from
2909 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
2911 Another scenario would be that there are two logical networks living
2912 on your local Ethernet and you want to access them both with the
2913 same Ethernet card. This can also be done if you say Y here.
2915 The configuration of these alias addresses is done with a special
2916 name syntax explained in Documentation/networking/alias.txt and in
2917 the IP-Alias mini-HOWTO. If you want this, say Y. Most people don't
2920 IP: multicast routing
2922 This is used if you want your machine to act as a router for IP
2923 packets that have several destination addresses. It is needed on the
2924 MBONE, a high bandwidth network on top of the Internet which carries
2925 audio and video broadcasts. In order to do that, you would most
2926 likely run the program mrouted. Information about the multicast
2927 capabilities of the various network cards is contained in
2928 Documentation/networking/multicast.txt. If you haven't heard about
2929 it, you don't need it.
2931 IP: PIM-SM version 1 support
2933 Kernel side support for Sparse Mode PIM (Protocol Independent
2934 Multicast) version 1. This multicast routing protocol is used widely
2935 because Cisco supports it. You need special software to use it
2936 (pimd-v1). Please see http://netweb.usc.edu/pim/ for more
2937 information about PIM (to browse the WWW, you need to have access to
2938 a machine on the Internet that has a program like lynx or
2941 Say Y if you want to use PIM-SM v1. Note that you can say N here if
2942 you just want to use Dense Mode PIM.
2944 IP: PIM-SM version 2 support
2946 Kernel side support for Sparse Mode PIM version 2. In order to use
2947 this, you need an experimental routing daemon supporting it (pimd or
2948 gated-5). This routing protocol is not used widely, so say N unless
2949 you want to play with it.
2951 PC/TCP compatibility mode
2953 If you have been having difficulties telnetting to your Linux
2954 machine from a DOS system that uses (broken) PC/TCP networking
2955 software (all versions up to OnNet 2.0) over your local Ethernet try
2956 saying Y here. Everyone else says N.
2958 People having problems with NCSA telnet should see the file
2959 linux/Documentation/networking/ncsa-telnet.
2963 If there are (usually diskless or portable) machines on your local
2964 network that know their hardware Ethernet addresses but don't know
2965 their IP addresses upon startup, they can send out a Reverse Address
2966 Resolution Protocol (RARP) request to find out their own IP
2967 addresses. Diskless Sun 3 machines use this procedure at boot time,
2968 and diskless Linux boxes can be configured to do it as well.
2970 If you want your Linux box to be able to *answer* such requests,
2971 answer Y here; you'll then have to run the program rarp ("man rarp")
2974 If you actually want to use a diskless Sun 3 machine as an X
2975 terminal to Linux, say Y here and fetch Linux-Xkernel from
2976 ftp://metalab.unc.edu/pub/Linux/system/network/boot.net/.
2978 Superior solutions to the problem of booting and configuring
2979 machines over a net connection are given by the protocol BOOTP and
2980 its successor DHCP. See the DHCP FAQ
2981 http://web.syr.edu/~jmwobus/comfaqs/dhcp.faq.html for details (to
2982 browse the WWW, you need to have access to a machine on the Internet
2983 that has a program like lynx or netscape).
2985 If you want to compile RARP support as a module ( = code which can
2986 be inserted in and removed from the running kernel whenever you
2987 want), say M here and read Documentation/modules.txt. The module
2988 will be called rarp.o.
2990 If you don't understand a word of the above, say N and rest in
2993 Assume subnets are local
2995 Say Y if you are on a subnetted network with all machines connected
2996 by Ethernet segments only, as this option optimizes network access
2997 for this special case. If there are other connections, e.g. SLIP
2998 links, between machines of your IP network, say N. If in doubt,
2999 answer N. The PATH mtu discovery facility will cover most cases
3002 Path MTU Discovery (normally enabled)
3003 CONFIG_PATH_MTU_DISCOVERY
3004 MTU (maximal transfer unit) is the size of the chunks we send out
3005 over the net. "Path MTU Discovery" means that, instead of always
3006 sending very small chunks, we start out sending big ones and if we
3007 then discover that some host along the way likes its chunks smaller,
3008 we adjust to a smaller size. This is good, so most people say Y
3011 However, some DOS software (versions of DOS NCSA telnet and Trumpet
3012 Winsock in PPP mode) is broken and won't be able to connect to your
3013 Linux machine correctly in all cases (especially through a terminal
3014 server) unless you say N here. See
3015 Documentation/networking/ncsa-telnet for the location of fixed NCSA
3016 telnet clients. If in doubt, say Y.
3018 Disable NAGLE algorithm (normally enabled)
3019 CONFIG_TCP_NAGLE_OFF
3020 The NAGLE algorithm works by requiring an acknowledgment before
3021 sending small IP frames (packets). This keeps tiny telnet and
3022 rlogin packets from congesting Wide Area Networks. Most people
3023 strongly recommend to say N here, thereby leaving NAGLE
3024 enabled. Those programs that would benefit from disabling this
3025 facility can do it on a per connection basis themselves.
3027 IP: Allow large windows (not recommended if <16 MB of memory)
3029 On high speed, long distance networks the performance limit on
3030 networking becomes the amount of data the sending machine can buffer
3031 until the other end confirms its reception. (At 45 Mbit/second there
3032 are a lot of bits between New York and London ...). If you say Y
3033 here, bigger buffers can be used which allows larger amounts of data
3034 to be "in flight" at any given time. It also means a user process
3035 can require a lot more memory for network buffers and thus this
3036 option is best used only on machines with 16 MB of memory or higher.
3037 Unless you are using long links with end to end speeds of over 2
3038 Mbit a second or satellite links this option will make no difference
3043 If you say Y here, you will include support for Unix domain sockets;
3044 sockets are the standard Unix mechanism for establishing and
3045 accessing network connections. Many commonly used programs such as
3046 the X Window system and syslog use these sockets even if your
3047 machine is not connected to any network. Unless you are working on
3048 an embedded system or something similar, you therefore definitely
3051 However, the socket support is also available as a module ( = code
3052 which can be inserted in and removed from the running kernel
3053 whenever you want). If you want to compile it as a module, say M
3054 here and read Documentation/modules.txt. The module will be called
3055 unix.o. If you try building this as a module and you have said Y to
3056 "Kernel module loader support" above, be sure to add 'alias net-pf-1
3057 unix' to your /etc/conf.modules file. Note that several important
3058 services won't work correctly if you say M here and then neglect to
3061 Say Y unless you know what you are doing.
3065 This is experimental support for the next version of the Internet
3066 Protocol: IP version 6 (also called IPng "IP next generation").
3067 Features of this new protocol include: expanded address space,
3068 authentication and privacy, and seamless interoperability with the
3069 current version of IP (IP version 4). For general information about
3070 IPv6, see http://playground.sun.com/pub/ipng/html/ipng-main.html (to
3071 browse the WWW, you need to have access to a machine on the Internet
3072 that has a program like lynx or netscape); for specific information
3073 about IPv6 under Linux read the HOWTO at http://www.terra.net/ipv6/
3074 and the file net/ipv6/README in the kernel source.
3076 If you want to use IPv6, please upgrade to the newest net-tools as
3077 given in Documentation/Changes. You will still be able to do regular
3078 IPv4 networking as well.
3080 This protocol support is also available as a module ( = code which
3081 can be inserted in and removed from the running kernel whenever you
3082 want). The module will be called ipv6.o. If you want to compile it
3083 as a module, say M here and read Documentation/modules.txt.
3085 It is safe to say N here for now.
3087 IPv6: enable EUI-64 token format
3089 6bone, the network of computers using the IPv6 protocol, is moving
3090 to a new aggregatable address format and a new link local address
3091 assignment (EUI-64). Say Y if your site has upgraded already, or
3092 has started to upgrade.
3094 IPv6: disable provider based addresses
3096 Linux tries to operate correctly when your site has moved to EUI-64
3097 only partially. Unfortunately, the two address formats (old:
3098 "provider based" and new: "aggregatable") are incompatible. Say Y if
3099 your site finished the upgrade to EUI-64, and/or you encountered
3100 some problems caused by the presence of two link-local addresses on
3103 IPv6: routing messages via old netlink
3105 You can say Y here to receive routing messages from the IPv6 code
3106 through the old netlink interface. However, a better option is to
3107 say Y to "Kernel/User network link driver" and to "Routing
3112 This is support for the Novell networking protocol, IPX, commonly
3113 used for local networks of Windows machines. You need it if you want
3114 to access Novell NetWare file or print servers using the Linux
3115 Novell client ncpfs (available via FTP (user: anonymous) from
3116 ftp://metalab.unc.edu/pub/Linux/system/filesystems/) or from within
3117 the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available in
3118 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO). In order to do the
3119 former, you'll also have to say Y to "NCP filesystem support",
3122 IPX is similar in scope to IP, while SPX, which runs on top of IPX,
3123 is similar to TCP. There is also experimental support for SPX in
3124 Linux (see "SPX networking", below).
3126 To turn your Linux box into a fully featured NetWare file server and
3127 IPX router, say Y here and fetch either lwared from
3128 ftp://metalab.unc.edu/pub/Linux/system/network/daemons/ or mars_nwe
3129 from ftp://ftp.gwdg.de/pub/linux/misc/ncpfs. For more information,
3130 read the IPX-HOWTO in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
3132 General information about how to connect Linux, Windows machines and
3133 Macs is on the WWW at http://www.eats.com/linux_mac_win.html (to
3134 browse the WWW, you need to have access to a machine on the Internet
3135 that has a program like lynx or netscape).
3137 The IPX driver would enlarge your kernel by about 5 kB. This driver
3138 is also available as a module ( = code which can be inserted in and
3139 removed from the running kernel whenever you want). The module will
3140 be called ipx.o. If you want to compile it as a module, say M here
3141 and read Documentation/modules.txt. Unless you want to integrate
3142 your Linux box with a local Novell network, say N.
3144 IPX: Full internal IPX network
3146 Every IPX network has an address that identifies it. Sometimes it is
3147 useful to give an IPX "network" address to your Linux box as well
3148 (for example if your box is acting as a file server for different
3149 IPX networks: it will then be accessible from everywhere using the
3150 same address). The way this is done is to create a virtual internal
3151 "network" inside your box and to assign an IPX address to this
3152 network. Say Y here if you want to do this; read the IPX-HOWTO at
3153 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO for details.
3155 The full internal IPX network enables you to allocate sockets on
3156 different virtual nodes of the internal network. This is done by
3157 evaluating the field sipx_node of the socket address given to the
3158 bind call. So applications should always initialize the node field
3159 to 0 when binding a socket on the primary network. In this case the
3160 socket is assigned the default node that has been given to the
3161 kernel when the internal network was created. By enabling the full
3162 internal IPX network the cross-forwarding of packets targeted at
3163 'special' sockets to sockets listening on the primary network is
3164 disabled. This might break existing applications, especially RIP/SAP
3165 daemons. A RIP/SAP daemon that works well with the full internal net
3166 can be found on ftp://ftp.gwdg.de/pub/linux/misc/ncpfs.
3168 If you don't know what you are doing, say N.
3170 IPX: SPX networking (EXPERIMENTAL)
3172 The Sequenced Packet eXchange protocol is a transport layer protocol
3173 built on top of IPX. It is used in Novell NetWare systems for
3174 client-server applications and is similar to TCP (which runs on top
3177 Note that Novell NetWare file sharing does not use SPX; it uses a
3178 protocol called NCP, for which separate Linux support is available
3179 ("NCP filesystem support" below for the client side, and the user
3180 space programs lwared or mars_nwe for the server side).
3182 Say Y here if you have use for SPX; read the IPX-HOWTO at
3183 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO for details.
3185 This driver is also available as a module ( = code which can be
3186 inserted in and removed from the running kernel whenever you want).
3187 The module will be called af_spx.o. If you want to compile it as a
3188 module, say M here and read Documentation/modules.txt.
3192 The DECnet networking protocol was used in many products made by
3193 Digital (now Compaq). It provides reliable stream and sequenced
3194 packet communications over which run a variety of services similar
3195 to those which run over TCP/IP.
3197 To find some tools to use with the kernel layer support, please
3198 look at Patrick Caulfield's web site:
3199 http://linux.dreamtime.org/decnet/
3201 More detailed documentation is available in the
3202 Documentation/networking/decnet.txt file.
3204 Be sure to turn on the CONFIG_PROCFS and CONFIG_SYSCTL options
3205 when using DECnet, since you will need sysctl support to aid in
3206 configuration at run time.
3208 DECnet SIOCFIGCONF support
3209 CONFIG_DECNET_SIOCGIFCONF
3210 This option should only be turned on if you are really sure that
3211 you know what you are doing. It can break other applications which
3212 use this system call and the proper way to get the information
3213 provided by this call is to use rtnetlink.
3215 DECnet Router Support
3216 CONFIG_DECNET_ROUTER
3217 Add support for turning your DECnet Endnode into a level 1 or 2
3218 router. This is an unfinished option for developers only. If you
3219 do turn it on, then make sure you also have rtnetlink configured
3220 in, since thats the only current method of configuration.
3222 DECnet Raw Socket Support
3224 Add support for the SOCK_RAW type under DECnet. Used by userland
3225 routing programs to receive routing messages from the kernel and
3226 also as a general debugging aid to see whats going on "under the hood".
3230 AppleTalk is the way Apple computers speak to each other on a
3231 network. If your Linux box is connected to such a network and you
3232 want to join the conversation, say Y. You will need to use the
3233 netatalk package so that your Linux box can act as a print and file
3234 server for Macs as well as access AppleTalk printers. Check out
3235 http://threepio.hitchcock.org/cgi-bin/faq/netatalk/faq.pl on the WWW
3236 for details (to browse the WWW, you need to have access to a machine
3237 on the Internet that has a program like lynx or netscape). EtherTalk
3238 is the name used for AppleTalk over Ethernet and the cheaper and
3239 slower LocalTalk is AppleTalk over a proprietary Apple network using
3240 serial links. EtherTalk and LocalTalk are fully supported by Linux.
3242 General information about how to connect Linux, Windows machines and
3243 Macs is on the WWW at http://www.eats.com/linux_mac_win.html
3244 The NET-3-HOWTO, available via FTP (user: anonymous) in
3245 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO contains valuable
3246 information as well.
3248 This driver is also available as a module ( = code which can be
3249 inserted in and removed from the running kernel whenever you want).
3250 The module is called appletalk.o. If you want to compile it as a
3251 module, say M here and read Documentation/modules.txt. I hear that
3252 the GNU boycott of Apple is over, so even politically correct people
3253 are allowed to say Y here.
3255 AppleTalk-IP driver support
3257 This allows IP networking for users who only have AppleTalk
3258 networking available. This feature is experimental. With this
3259 driver, you can encapsulate IP inside AppleTalk (e.g. if your Linux
3260 box is stuck on an AppleTalk only network) or decapsulate (e.g. if
3261 you want your Linux box to act as an Internet gateway for a zoo of
3262 AppleTalk connected Macs). Please see the file
3263 Documentation/networking/ipddp.txt for more information.
3265 If you say Y here, the AppleTalk-IP support will be compiled into
3266 the kernel. In this case, you can either use encapsulation or
3267 decapsulation, but not both. With the following two questions, you
3268 decide which one you want.
3270 If you say M here, the AppleTalk-IP support will be compiled as a
3271 module ( = code which can be inserted in and removed from the
3272 running kernel whenever you want, read Documentation/modules.txt).
3273 The module is called ipddp.o. In this case, you will be able to use
3274 both encapsulation and decapsulation simultaneously, by loading two
3275 copies of the module and specifying different values for the module
3278 IP to AppleTalk-IP Encapsulation support
3280 If you say Y here, the AppleTalk-IP code will be able to encapsulate
3281 IP packets inside AppleTalk frames; this is useful if your Linux box
3282 is stuck on an AppleTalk network (which hopefully contains a
3283 decapsulator somewhere). Please see
3284 Documentation/networking/ipddp.txt for more information. If you said
3285 Y to "AppleTalk-IP driver support" above and you say Y here, then
3286 you cannot say Y to "AppleTalk-IP to IP Decapsulation support",
3289 AppleTalk-IP to IP Decapsulation support
3291 If you say Y here, the AppleTalk-IP code will be able to decapsulate
3292 AppleTalk-IP frames to IP packets; this is useful if you want your
3293 Linux box to act as an Internet gateway for an AppleTalk network.
3294 Please see Documentation/networking/ipddp.txt for more information.
3295 If you said Y to "AppleTalk-IP driver support" above and you say Y
3296 here, then you cannot say Y to "IP to AppleTalk-IP Encapsulation
3299 Apple/Farallon LocalTalk PC card support
3301 This allows you to use the AppleTalk PC card to connect to LocalTalk
3302 networks. The card is also known as the Farallon PhoneNet PC card.
3303 If you are in doubt, this card is the one with the 65C02 chip on it.
3304 You also need version 1.3.3 or later of the netatalk package.
3305 This driver is experimental, which means that it may not work.
3306 See the file Documentation/networking/ltpc.txt.
3308 COPS LocalTalk PC card support
3310 This allows you to use COPS AppleTalk cards to connect to LocalTalk
3311 networks. You also need version 1.3.3 or later of the netatalk
3312 package. This driver is experimental, which means that it may not
3313 work. This driver will only work if you choose "AppleTalk DDP"
3314 networking support, above.
3315 Please read the file Documentation/networking/cops.txt.
3317 Dayna firmware support
3319 Support COPS compatible cards with Dayna style firmware (Dayna
3320 DL2000/ Daynatalk/PC (half length), COPS LT-95, Farallon PhoneNET PC
3321 III, Farallon PhoneNET PC II).
3323 Tangent firmware support
3325 Support COPS compatible cards with Tangent style firmware (Tangent
3326 ATB_II, Novell NL-1000, Daystar Digital LT-200.
3328 Amateur Radio support
3330 If you want to connect your Linux box to an amateur radio, answer Y
3331 here. You want to read http://www.tapr.org/tapr/html/pkthome.html
3332 (to browse the WWW, you need to have access to a machine on the
3333 Internet that has a program like lynx or netscape) and the HAM-HOWTO
3334 and the AX25-HOWTO, both available via FTP (user: anonymous) from
3335 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
3337 Note that the answer to this question won't directly affect the
3338 kernel: saying N will just cause this configure script to skip all
3339 the questions about amateur radio.
3341 Amateur Radio AX.25 Level 2
3343 This is the protocol used for computer communication over amateur
3344 radio. It is either used by itself for point-to-point links, or to
3345 carry other protocols such as tcp/ip. To use it, you need a device
3346 that connects your Linux box to your amateur radio. You can either
3347 use a low speed TNC (a Terminal Node Controller acts as a kind of
3348 modem connecting your computer's serial port to your radio's
3349 microphone input and speaker output) supporting the KISS protocol or
3350 one of the various SCC cards that are supported by the generic Z8530
3351 or the DMA SCC driver. Another option are the Baycom modem serial
3352 and parallel port hacks or the sound card modem (supported by their
3353 own drivers). If you say Y here, you also have to say Y to one of
3356 Information about where to get supporting software for Linux amateur
3357 radio as well as information about how to configure an AX.25 port is
3358 contained in the AX25-HOWTO, available via FTP (user: anonymous) in
3359 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. You might also want to
3360 check out the file Documentation/networking/ax25.txt in the kernel
3361 source. More information about digital amateur radio in general is
3362 on the WWW at http://www.tapr.org/tapr/html/pkthome.html. (To browse
3363 the WWW, you need to have access to a machine on the Internet that
3364 has a program like lynx or netscape).
3366 This driver is also available as a module ( = code which can be
3367 inserted in and removed from the running kernel whenever you want).
3368 The module will be called ax25.o. If you want to compile it as a
3369 module, say M here and read Documentation/modules.txt.
3371 AX.25 DAMA Slave support
3372 CONFIG_AX25_DAMA_SLAVE
3373 DAMA is a mechanism to prevent collisions when doing AX.25
3374 networking. A DAMA server (called "master") accepts incoming traffic
3375 from clients (called "slaves") and redistributes it to other slaves.
3376 If you say Y here, your Linux box will act as a DAMA slave; this is
3377 transparent in that you don't have to do any special DAMA
3378 configuration. (Linux cannot yet act as a DAMA server.) If unsure,
3381 AX.25 DAMA Master support
3382 CONFIG_AX25_DAMA_MASTER
3383 DAMA is a mechanism to prevent collisions when doing AX.25
3384 networking. A DAMA server (called "master") accepts incoming traffic
3385 from clients (called "slaves") and redistributes it to other
3386 slaves. If you say Y here, your Linux box will act as a DAMA server.
3389 Amateur Radio NET/ROM
3391 NET/ROM is a network layer protocol on top of AX.25 useful for
3394 A comprehensive listing of all the software for Linux amateur radio
3395 users as well as information about how to configure an AX.25 port is
3396 contained in the AX25-HOWTO, available via FTP (user: anonymous) in
3397 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. You also might want to
3398 check out the file Documentation/networking/ax25.txt. More
3399 information about digital amateur radio in general is on the WWW at
3400 http://www.tapr.org/tapr/html/pkthome.html (to browse the WWW, you
3401 need to have access to a machine on the Internet that has a program
3402 like lynx or netscape).
3404 This driver is also available as a module ( = code which can be
3405 inserted in and removed from the running kernel whenever you want).
3406 The module will be called netrom.o. If you want to compile it as a
3407 module, say M here and read Documentation/modules.txt.
3409 Amateur Radio X.25 PLP (Rose)
3411 The Packet Layer Protocol (PLP) is a way to route packets over X.25
3412 connections in general and amateur radio AX.25 connections in
3413 particular, essentially an alternative to NET/ROM.
3415 A comprehensive listing of all the software for Linux amateur radio
3416 users as well as information about how to configure an AX.25 port is
3417 contained in the AX25-HOWTO, available via FTP (user: anonymous) in
3418 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. You also might want to
3419 check out the file Documentation/networking/ax25.txt. More
3420 information about digital amateur radio in general is on the WWW at
3421 http://www.tapr.org/tapr/html/pkthome.html (to browse the WWW, you
3422 need to have access to a machine on the Internet that has a program
3423 like lynx or netscape).
3425 This driver is also available as a module ( = code which can be
3426 inserted in and removed from the running kernel whenever you want).
3427 The module will be called rose.o. If you want to compile it as a
3428 module, say M here and read Documentation/modules.txt.
3430 Serial port KISS driver for AX.25
3432 KISS is a protocol used for the exchange of data between a computer
3433 and a Terminal Node Controller (a small embedded system commonly
3434 used for networking over AX.25 amateur radio connections; it
3435 connects the computer's serial port with the radio's microphone
3436 input and speaker output).
3438 Although KISS is less advanced than the 6pack protocol, it has
3439 the advantage that it is already supported by most modern TNCs
3440 without the need for a firmware upgrade.
3442 If you want to compile this driver as a module ( = code which can be
3443 inserted in and removed from the running kernel whenever you want),
3444 say M here and read Documentation/modules.txt. The module will be
3447 Serial port 6PACK driver for AX.25
3449 6pack is a transmission protocol for the data exchange between your
3450 PC and your TNC (the Terminal Node Controller acts as a kind of
3451 modem connecting your computer's serial port to your radio's
3452 microphone input and speaker output). This protocol can be used as
3453 an alternative to KISS for networking over AX.25 amateur radio
3454 connections, but it has some extended functionality.
3456 Note that this driver is still experimental and might cause
3457 problems. For details about the features and the usage of the
3458 driver, read Documentation/networking/6pack.txt.
3460 If you want to compile this driver as a module ( = code which can be
3461 inserted in and removed from the running kernel whenever you want),
3462 say M here and read Documentation/modules.txt. The module will be
3467 AX.25 is the protocol used for computer communication over amateur
3468 radio. If you say Y here, you will be able to send and receive AX.25
3469 traffic over Ethernet (also called "BPQ AX.25"), which could be
3470 useful if some other computer on your local network has a direct
3471 amateur radio connection.
3473 High-speed (DMA) SCC driver for AX.25
3475 This is a driver for high-speed SCC boards, i.e. those supporting
3476 DMA on one port. You usually use those boards to connect your
3477 computer to an amateur radio modem (such as the WA4DSY 56kbps
3478 modem), in order to send and receive AX.25 packet radio network
3481 Currently, this driver supports Ottawa PI/PI2
3482 (http://hydra.carleton.ca/info/pi2.html) and Gracilis PackeTwin
3483 (http://www.paccomm.com/gracilis.html) boards. They are detected
3484 automatically. If you have one of these cards, say Y here and read
3485 the AX25-HOWTO, available via FTP (user: anonymous) in
3486 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/.
3488 This driver can operate multiple boards simultaneously. If you
3489 compile it as a module (by saying M instead of Y), it will be called
3490 dmascc.o. If you don't pass any parameter to the driver, all
3491 possible I/O addresses are probed. This could irritate other devices
3492 that are currently not in use. You may specify the list of addresses
3493 to be probed by "dmascc=addr1,addr2,..." (when compiled into the
3494 kernel image) or "io=addr1,addr2,..." (when loaded as a module). The
3495 network interfaces will be called dmascc0 and dmascc1 for the board
3496 detected first, dmascc2 and dmascc3 for the second one, and so on.
3498 Before you configure each interface with ifconfig, you MUST set
3499 certain parameters, such as channel access timing, clock mode, and
3500 DMA channel. This is accomplished with a small utility program,
3501 dmascc_cfg, available at
3502 http://www.nt.tuwien.ac.at/~kkudielk/Linux/. (To browse the WWW, you
3503 need to have access to a machine on the Internet that has a program
3504 like lynx or netscape).
3506 Z8530 SCC driver for AX.25
3508 These cards are used to connect your Linux box to an amateur radio
3509 in order to communicate with other computers. If you want to use
3510 this, read Documentation/networking/z8530drv.txt and the
3511 AX25-HOWTO, available via FTP (user: anonymous) at
3512 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Also make sure to say Y
3513 to "Amateur Radio AX.25 Level 2" support.
3515 If you want to compile this as a module ( = code which can be
3516 inserted in and removed from the running kernel whenever you want),
3517 say M here and read Documentation/modules.txt. The module will be
3520 additional delay for PA0HZP OptoSCC compatible boards
3522 Say Y here if you experience problems with the SCC driver not
3523 working properly; please read Documentation/networking/z8530drv.txt
3524 for details. If unsure, say N.
3526 #support for TRX that feedback the tx signal to rx
3529 ### Don't know what's going on here.
3532 BAYCOM picpar and par96 driver for AX.25
3534 This is a driver for Baycom style simple amateur radio modems that
3535 connect to a parallel interface. The driver supports the picpar and
3536 par96 designs. To configure the driver, use the sethdlc utility
3537 available in the standard ax25 utilities package. For information on
3538 the modems, see http://www.baycom.de (to browse the WWW, you need to
3539 have access to a machine on the Internet that has a program like
3540 lynx or netscape) and Documentation/networking/baycom.txt.
3542 If you want to compile this driver as a module ( = code which can be
3543 inserted in and removed from the running kernel whenever you want),
3544 say M here and read Documentation/modules.txt. This is recommended.
3545 The module will be called baycom_par.o.
3547 BAYCOM EPP driver for AX.25
3549 This is a driver for Baycom style simple amateur radio modems that
3550 connect to a parallel interface. The driver supports the EPP
3551 designs. To configure the driver, use the sethdlc utility available
3552 in the standard ax25 utilities package. For information on the
3553 modems, see http://www.baycom.de (to browse the WWW, you need to
3554 have access to a machine on the Internet that has a program like
3555 lynx or netscape) and Documentation/networking/baycom.txt.
3557 If you want to compile this driver as a module ( = code which can be
3558 inserted in and removed from the running kernel whenever you want),
3559 say M here and read Documentation/modules.txt. This is recommended.
3560 The module will be called baycom_par.o.
3562 BAYCOM ser12 full duplex driver for AX.25
3563 CONFIG_BAYCOM_SER_FDX
3564 This is one of two drivers for Baycom style simple amateur radio
3565 modems that connect to a serial interface. The driver supports the
3566 ser12 design in full duplex mode. In addition, it allows the
3567 baudrate to be set between 300 and 4800 baud (however not all modems
3568 support all baudrates). This is the preferred driver. The next
3569 driver, "BAYCOM ser12 half duplex driver for AX.25" is the old
3570 driver and still provided in case this driver does not work with
3571 your serial interface chip. To configure the driver, use the sethdlc
3572 utility available in the standard ax25 utilities package. For
3573 information on the modems, see http://www.baycom.de (to browse the
3574 WWW, you need to have access to a machine on the Internet that has a
3575 program like lynx or netscape) and
3576 Documentation/networking/baycom.txt.
3578 If you want to compile this driver as a module ( = code which can be
3579 inserted in and removed from the running kernel whenever you want),
3580 say M here and read Documentation/modules.txt. This is recommended.
3581 The module will be called baycom_ser_fdx.o.
3583 BAYCOM ser12 half duplex driver for AX.25
3584 CONFIG_BAYCOM_SER_HDX
3585 This is one of two drivers for Baycom style simple amateur radio
3586 modems that connect to a serial interface. The driver supports the
3587 ser12 design in full duplex mode. This is the old driver. It is
3588 still provided in case your serial interface chip does not work with
3589 the full duplex driver. This driver is depreciated. To configure
3590 the driver, use the sethdlc utility available in the standard ax25
3591 utilities package. For information on the modems, see
3592 http://www.baycom.de (to browse the WWW, you need to have access to
3593 a machine on the Internet that has a program like lynx or netscape)
3594 and Documentation/networking/baycom.txt.
3596 If you want to compile this driver as a module ( = code which can be
3597 inserted in and removed from the running kernel whenever you want),
3598 say M here and read Documentation/modules.txt. This is recommended.
3599 The module will be called baycom_ser_hdx.o.
3601 Sound card modem driver for AX.25
3603 This experimental driver allows a standard Sound Blaster or
3604 WindowsSoundSystem compatible sound card to be used as a packet
3605 radio modem (NOT as a telephone modem!), to send digital traffic
3608 To configure the driver, use the sethdlc, smdiag and smmixer
3609 utilities available in the standard ax25 utilities package. For
3610 information on how to key the transmitter, see
3611 http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html (to browse
3612 the WWW, you need to have access to a machine on the Internet that
3613 has a program like lynx or netscape) and
3614 Documentation/networking/soundmodem.txt.
3616 If you want to compile this driver as a module ( = code which can be
3617 inserted in and removed from the running kernel whenever you want),
3618 say M here and read Documentation/modules.txt. This is recommended.
3619 The module will be called soundmodem.o.
3621 Sound card modem support for Sound Blaster and compatible cards
3622 CONFIG_SOUNDMODEM_SBC
3623 This option enables the soundmodem driver to use Sound Blaster and
3624 compatible cards. If you have a dual mode card (i.e. a WSS cards
3625 with a Sound Blaster emulation) you should say N here and Y to
3626 "Sound card modem support for WSS and Crystal cards", below, because
3627 this usually results in better performance. This option also
3628 supports SB16/32/64 in full duplex mode.
3630 Sound card modem support for WSS and Crystal cards
3631 CONFIG_SOUNDMODEM_WSS
3632 This option enables the soundmodem driver to use WindowsSoundSystem
3633 compatible cards. These cards feature a codec chip from either
3634 Analog Devices (such as AD1848, AD1845, AD1812) or Crystal
3635 Semiconductors (such as CS4248, CS423x). This option also supports
3636 the WSS full duplex operation which currently works with Crystal
3637 CS423x chips. If you don't need full duplex operation, do not enable
3638 it to save performance.
3640 Sound card modem support for 1200 baud AFSK modulation
3641 CONFIG_SOUNDMODEM_AFSK1200
3642 This option enables the soundmodem driver 1200 baud AFSK modem,
3643 compatible to popular modems using TCM3105 or AM7911. The
3644 demodulator requires about 12% of the CPU power of a Pentium 75 CPU
3647 Sound card modem support for 2400 baud AFSK modulation (7.3728MHz crystal)
3648 CONFIG_SOUNDMODEM_AFSK2400_7
3649 This option enables the soundmodem driver 2400 baud AFSK modem,
3650 compatible to TCM3105 modems (over-)clocked with a 7.3728MHz
3651 crystal. Note that the availability of this driver does _not_ imply
3652 that I recommend building such links. It is only here since users
3653 especially in eastern Europe have asked me to do so. In fact this
3654 modulation scheme has many disadvantages, mainly its incompatibility
3655 with many transceiver designs and the fact that the TCM3105 (if
3656 used) is operated widely outside its specifications.
3658 Sound card modem support for 2400 baud AFSK modulation (8MHz crystal)
3659 CONFIG_SOUNDMODEM_AFSK2400_8
3660 This option enables the soundmodem driver 2400 baud AFSK modem,
3661 compatible to TCM3105 modems (over-)clocked with an 8MHz crystal.
3662 Note that the availability of this driver does _not_ imply that I
3663 recommend building such links. It is only here since users
3664 especially in eastern Europe have asked me to do so. In fact this
3665 modulation scheme has many disadvantages, mainly its incompatibility
3666 with many transceiver designs and the fact that the TCM3105 (if
3667 used) is operated widely outside its specifications.
3669 Sound card modem support for 2666 baud AFSK modulation
3670 CONFIG_SOUNDMODEM_AFSK2666
3671 This option enables the soundmodem driver 2666 baud AFSK modem.
3672 This modem is experimental, and not compatible to anything
3675 Sound card modem support for 4800 baud 8PSK modulation
3676 CONFIG_SOUNDMODEM_PSK4800
3677 This option enables the soundmodem driver 4800 baud 8PSK modem.
3678 This modem is experimental, and not compatible to anything
3681 Sound card modem support for 4800 baud HAPN-1 modulation
3682 CONFIG_SOUNDMODEM_HAPN4800
3683 This option enables the soundmodem driver 4800 baud HAPN-1
3684 compatible modem. This modulation seems to be widely used 'down
3685 under' and in the Netherlands. Here, nobody uses it, so I could not
3686 test if it works. It is compatible to itself, however :-)
3688 Sound card modem support for 9600 baud FSK G3RUH modulation
3689 CONFIG_SOUNDMODEM_FSK9600
3690 This option enables the soundmodem driver 9600 baud FSK modem,
3691 compatible to the G3RUH standard. The demodulator requires about 4%
3692 of the CPU power of a Pentium 75 CPU per channel. You can say Y to
3693 both 1200 baud AFSK and 9600 baud FSK if you want (but obviously you
3694 can only use one protocol at a time, depending on what the other end
3697 CCITT X.25 Packet Layer
3699 X.25 is a set of standardized network protocols, similar in scope to
3700 frame relay; the one physical line from your box to the X.25 network
3701 entry point can carry several logical point-to-point connections
3702 (called "virtual circuits") to other computers connected to the X.25
3703 network. Governments, banks, and other organizations tend to use it
3704 to connect to each other or to form Wide Area Networks (WANs). Many
3705 countries have public X.25 networks. X.25 consists of two
3706 protocols: the higher level Packet Layer Protocol (PLP) (say Y here
3707 if you want that) and the lower level data link layer protocol LAPB
3708 (say Y to "LAPB Data Link Driver" below if you want that).
3710 You can read more about X.25 at http://www.sangoma.com/x25.html and
3711 http://www.cisco.com/univercd/data/doc/software/11_0/rpcg/cx25.htm
3712 (to browse the WWW, you need to have access to a machine on the
3713 Internet that has a program like lynx or netscape). Information
3714 about X.25 for Linux is contained in the files
3715 Documentation/networking/x25.txt and
3716 Documentation/networking/x25-iface.txt.
3718 One connects to an X.25 network either with a dedicated network card
3719 using the X.21 protocol (not yet supported by Linux) or one can do
3720 X.25 over a standard telephone line using an ordinary modem (say Y
3721 to "X.25 async driver" below) or over Ethernet using an ordinary
3722 Ethernet card and either the 802.2 LLC protocol (say Y to "802.2
3723 LLC" below) or LAPB over Ethernet (say Y to "LAPB Data Link Driver"
3724 and "LAPB over Ethernet driver" below).
3726 If you want to compile this driver as a module ( = code which can be
3727 inserted in and removed from the running kernel whenever you want),
3728 say M here and read Documentation/modules.txt. The module will be
3729 called x25.o. If unsure, say N.
3731 LAPB Data Link Driver (EXPERIMENTAL)
3733 Link Access Procedure, Balanced (LAPB) is the data link layer (i.e.
3734 the lower) part of the X.25 protocol. It offers a reliable
3735 connection service to exchange data frames with one other host, and
3736 it is used to transport higher level protocols (mostly X.25 Packet
3737 Layer, the higher part of X.25, but others are possible as well).
3738 Usually, LAPB is used with specialized X.21 network cards, but Linux
3739 currently supports LAPB only over Ethernet connections. If you want
3740 to use LAPB connections over Ethernet, say Y here and to "LAPB over
3741 Ethernet driver" below. Read
3742 Documentation/networking/lapb-module.txt for technical details.
3744 If you want to compile this driver as a module though ( = code which
3745 can be inserted in and removed from the running kernel whenever you
3746 want), say M here and read Documentation/modules.txt. The module
3747 will be called lapb.o. If unsure, say N.
3749 802.2 LLC (VERY EXPERIMENTAL)
3751 This is a Logical Link Layer protocol used for X.25 connections over
3752 Ethernet, using ordinary Ethernet cards.
3754 Bridging (EXPERIMENTAL)
3756 If you say Y here, then your Linux box will be able to act as an
3757 Ethernet bridge, which means that the different Ethernet segments it
3758 is connected to will appear as one Ethernet to the participants.
3759 Several such bridges can work together to create even larger
3760 networks of Ethernets using the IEEE802.1 spanning tree algorithm.
3761 As this is a standard, Linux bridges will interwork properly with
3762 other third party bridge products.
3764 In order to use this, you'll need the bridge configuration tools
3765 available via FTP (user: anonymous) from
3766 ftp://shadow.cabi.net/pub/Linux. Please read the Bridge mini-HOWTO
3767 for more information. Note that if your box acts as a bridge, it
3768 probably contains several Ethernet devices, but the kernel is not
3769 able to recognize more than one at boot time without help; for
3770 details read the Ethernet-HOWTO, available via FTP (user: anonymous)
3771 in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. The Bridging code is
3772 still in test. If unsure, say N.
3776 The Packet protocol is used by applications which communicate
3777 directly with network devices without an intermediate network
3778 protocol implemented in the kernel, e.g. tcpdump. If you want them
3779 to work, choose Y. This driver is also available as a module called
3780 af_packet.o ( = code which can be inserted in and removed from the
3781 running kernel whenever you want). If you want to compile it as a
3782 module, say M here and read Documentation/modules.txt. If unsure,
3785 Kernel/User network link driver
3787 This driver allows for two-way communication between certain parts
3788 of the kernel or modules and user processes; the user processes are
3789 able to read from and write to character special files in the /dev
3790 directory having major mode 36. So far, the kernel uses it to
3791 publish some network related information if you say Y to "Routing
3792 messages", below. It is also used by the firewall code to publish
3793 information about possible attacks if you say Y to "IP: firewall
3794 packet netlink device" further down. You also need to say Y here if
3795 you want to use arpd, a daemon that helps keep the internal ARP
3796 cache (a mapping between IP addresses and hardware addresses on the
3797 local network) small. The ethertap device, which lets user space
3798 programs read and write raw Ethernet frames, also needs the network
3799 link driver. If unsure, say Y.
3803 If you say Y here and create a character special file /dev/route
3804 with major number 36 and minor number 0 using mknod ("man mknod"),
3805 you (or some user space utility) can read some network related
3806 routing information from that file. Everything you write to that
3807 file will be discarded.
3809 Netlink device emulation
3811 This is a backward compatibility option, choose Y for now.
3812 This option will be removed soon.
3816 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CDROM or
3817 any other SCSI device under Linux, say Y and make sure that you know
3818 the name of your SCSI host adapter (the card inside your computer
3819 that "speaks" the SCSI protocol, also called SCSI controller),
3820 because you will be asked for it.
3822 You also need to say Y here if you want support for the parallel
3823 port version of the 100 MB IOMEGA ZIP drive.
3825 Please read the SCSI-HOWTO, available via FTP (user: anonymous) in
3826 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. The
3827 SCSI-Programming-HOWTO contains information about how to add or
3828 remove an SCSI device from a running Linux machine without
3831 This driver is also available as a module ( = code which can be
3832 inserted in and removed from the running kernel whenever you want).
3833 The module will be called scsi_mod.o. If you want to compile it as a
3834 module, say M here and read Documentation/modules.txt and
3835 Documentation/scsi.txt. However, do not compile this as a module if
3836 your root filesystem (the one containing the directory /) is located
3841 If you want to use a SCSI hard disk or the SCSI or parallel port
3842 version of the IOMEGA ZIP drive under Linux, say Y and read the
3843 SCSI-HOWTO, the Disk-HOWTO and the Multi-Disk-HOWTO, available via
3844 FTP (user: anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
3845 This is NOT for SCSI CDROMs.
3847 This driver is also available as a module ( = code which can be
3848 inserted in and removed from the running kernel whenever you want).
3849 The module will be called sd_mod.o. If you want to compile it as a
3850 module, say M here and read Documentation/modules.txt and
3851 Documentation/scsi.txt. Do not compile this driver as a module if
3852 your root filesystem (the one containing the directory /) is located
3853 on a SCSI disk. In this case, do not compile the driver for your
3854 SCSI host adapter (below) as a module either.
3858 If you want to use a SCSI tape drive under Linux, say Y and read the
3859 SCSI-HOWTO, available via FTP (user: anonymous) in
3860 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO and
3861 drivers/scsi/README.st in the kernel source. This is NOT for SCSI
3864 This driver is also available as a module ( = code which can be
3865 inserted in and removed from the running kernel whenever you want).
3866 The module will be called st.o. If you want to compile it as a
3867 module, say M here and read Documentation/modules.txt and
3868 Documentation/scsi.txt .
3872 If you want to use a SCSI CDROM under Linux, say Y and read the
3873 SCSI-HOWTO and the CDROM-HOWTO from
3874 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Also make sure to say Y
3875 or M to "ISO 9660 CDROM filesystem support" later.
3877 This driver is also available as a module ( = code which can be
3878 inserted in and removed from the running kernel whenever you want).
3879 The module will be called sr_mod.o. If you want to compile it as a
3880 module, say M here and read Documentation/modules.txt and
3881 Documentation/scsi.txt .
3883 Enable vendor-specific extensions (for SCSI CDROM)
3884 CONFIG_BLK_DEV_SR_VENDOR
3885 This enables the usage of vendor specific SCSI commands. This is
3886 required to support multisession CDs with old NEC/TOSHIBA cdrom
3887 drives (and HP Writers). If you have such a drive and get the first
3888 session only, try saying Y here; everybody else says N.
3890 SCSI generic support
3892 If you want to use SCSI scanners, synthesizers or CD-writers or just
3893 about anything having "SCSI" in its name other than hard disks,
3894 CDROMs or tapes, say Y here. These won't be supported by the kernel
3895 directly, so you need some additional software which knows how to
3896 talk to these devices using the SCSI protocol. For CD-writers, you
3897 would need the program cdwrite, available via FTP (user: anonymous)
3898 from ftp://metalab.unc.edu/pub/Linux/utils/disk-management; for
3899 other devices, it's possible that you'll have to write the driver
3900 software yourself, so have a look at the SCSI-HOWTO and at the
3901 SCSI-Programming-HOWTO, both available via FTP (user: anonymous) in
3902 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Please read the file
3903 Documentation/scsi-generic.txt for more information.
3905 If you want to compile this as a module ( = code which can be
3906 inserted in and removed from the running kernel whenever you want),
3907 say M here and read Documentation/modules.txt and
3908 Documentation/scsi.txt. The module will be called sg.o. If unsure,
3911 Probe all LUNs on each SCSI device
3912 CONFIG_SCSI_MULTI_LUN
3913 If you have a SCSI device that supports more than one LUN (Logical
3914 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
3915 can say Y here to force the SCSI driver to probe for multiple LUNs.
3916 A SCSI device with multiple LUNs acts logically like multiple SCSI
3917 devices. The vast majority of SCSI devices have only one LUN, and
3918 so most people can say N here and should in fact do so, because it
3921 Verbose SCSI error reporting (kernel size +=12K)
3922 CONFIG_SCSI_CONSTANTS
3923 The error messages regarding your SCSI hardware will be easier to
3924 understand if you say Y here; it will enlarge your kernel by about
3925 12 KB. If in doubt, say Y.
3927 SCSI logging facility
3929 This turns on a logging facility that can be used to debug a number
3930 of SCSI related problems.
3932 If you say Y here, no logging output will appear by default, but you
3933 can enable logging by saying Y to "/proc filesystem support" and
3934 "Sysctl support" below and executing the command
3936 echo "scsi log token [level]" > /proc/scsi/scsi
3938 at boot time after the /proc filesystem has been mounted.
3940 There are a number of things that can be used for 'token' (you can
3941 find them in the source: drivers/scsi/scsi.c), and this allows you
3942 to select the types of information you want, and the level allows
3943 you to select the level of verbosity.
3945 If you say N here, it may be harder to track down some types of SCSI
3946 problems. If you say Y here your kernel will be somewhat larger, but
3947 there should be no noticeable performance impact as long as you have
3950 AdvanSys SCSI support
3951 CONFIG_SCSI_ADVANSYS
3952 This is a driver for all SCSI host adapters manufactured by
3953 AdvanSys. It is documented in the kernel source in
3954 drivers/scsi/advansys.c.
3956 This driver is also available as a module ( = code which can be
3957 inserted in and removed from the running kernel whenever you want).
3958 If you want to compile it as a module, say M here and read
3959 Documentation/modules.txt. The module will be called advansys.o.
3961 Adaptec AHA152X/2825 support
3963 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
3964 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
3965 must be manually specified in this case.
3967 It is explained in section 3.3 of the SCSI-HOWTO, available via FTP
3968 (user: anonymous) at ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. You
3969 might also want to read the comments at the top of
3970 drivers/scsi/aha152x.c.
3972 This driver is also available as a module ( = code which can be
3973 inserted in and removed from the running kernel whenever you want).
3974 The module will be called aha152x.o. If you want to compile it as a
3975 module, say M here and read Documentation/modules.txt.
3977 Adaptec AHA1542 support
3979 This is support for a SCSI host adapter. It is explained in section
3980 3.4 of the SCSI-HOWTO, available via FTP (user: anonymous) at
3981 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Note that Trantor was
3982 recently purchased by Adaptec, and some former Trantor products are
3983 being sold under the Adaptec name. If it doesn't work out of the
3984 box, you may have to change some settings in drivers/scsi/aha1542.h.
3986 If you want to compile this as a module ( = code which can be
3987 inserted in and removed from the running kernel whenever you want),
3988 say M here and read Documentation/modules.txt. The module will be
3991 Adaptec AHA1740 support
3993 This is support for a SCSI host adapter. It is explained in section
3994 3.5 of the SCSI-HOWTO, available via FTP (user: anonymous) at
3995 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work out
3996 of the box, you may have to change some settings in
3997 drivers/scsi/aha1740.h.
3999 This driver is also available as a module ( = code which can be
4000 inserted in and removed from the running kernel whenever you want).
4001 The module will be called aha1740.o. If you want to compile it as a
4002 module, say M here and read Documentation/modules.txt.
4004 Adaptec AIC7xxx chipset SCSI controller support
4006 This is support for the various aic7xxx based Adaptec SCSI
4007 controllers. These include the 274x EISA cards; 284x VLB cards;
4008 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
4009 motherboard based SCSI controllers from Adaptec. It does not support
4010 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
4011 support them. It does not support the 2920 cards from Adaptec that
4012 use the Future Domain SCSI controller chip. For those cards, you
4013 need the "Future Domain 16xx SCSI support" driver.
4015 In general, if the controller is based on an Adaptec SCSI controller
4016 chip from the aic777x series or the aic78xx series, this driver
4017 should work. The only exception is the 7810 which is specifically
4018 not supported (that's the RAID controller chip on the AAA-13x
4021 Note that the AHA2920 SCSI host adapter is *not* supported by this
4022 driver; choose "Future Domain 16xx SCSI support" instead if you have
4025 Information on the configuration options for this controller can be
4026 found by checking the help file for each of the available
4027 configuration options. You should read drivers/scsi/README.aic7xxx
4028 at a minimum before contacting the maintainer with any questions.
4029 The SCSI-HOWTO, available via FTP (user: anonymous) at
4030 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO can also be of great
4033 If you want to compile this driver as a module ( = code which can be
4034 inserted in and removed from the running kernel whenever you want),
4035 say M here and read Documentation/modules.txt. The module will be
4038 Enable or Disable Tagged Command Queueing by default
4039 CONFIG_AIC7XXX_TCQ_ON_BY_DEFAULT
4040 This option causes the aic7xxx driver to attempt to use tagged command
4041 queueing on any devices that claim to support it. If this is set to yes,
4042 you can still turn off TCQ on troublesome devices with the use of the
4043 tag_info boot parameter. See /usr/src/linux/drivers/scsi/README.aic7xxx
4044 for more information on that and other aic7xxx setup commands. If this
4045 option is turned off, you may still enable TCQ on known good devices by
4046 use of the tag_info boot parameter.
4048 If you are unsure about your devices then it is safest to say N here.
4050 However, TCQ can increase performance on some hard drives by as much
4051 as 50% or more, so I would recommend that if you say N here, that you
4052 at least read the README.aic7xxx file so you will know how to enable
4053 this option manually should your drives prove to be safe in regards
4056 Conversely, certain drives are known to lock up or cause bus resets when
4057 TCQ is enabled on them. If you have a Western Digital Enterprise SCSI
4058 drive for instance, then don't even bother to enable TCQ on it as the
4059 drive will become unreliable, and it will actually reduce performance.
4061 Default number of TCQ commands per device
4062 CONFIG_AIC7XXX_CMDS_PER_DEVICE
4063 Specify the number of commands you would like to allocate per SCSI
4064 device when Tagged Command Queueing (TCQ) is enabled on that device.
4066 Reasonable figures are in the range of 8 to 24 commands per device,
4067 but depending on hardware could be increased or decreased from that
4068 figure. If the number is too high for any particular device, the
4069 driver will automatically compensate usually after only 10 minutes
4070 of uptime. It will not hinder performance if some of your devices
4071 eventually have their command depth reduced, but is a waste of memory
4072 if all of your devices end up reducing this number down to a more
4075 NOTE: Certain very broken drives are known to lock up when given more
4076 commands than they like to deal with. Quantum Fireball drives are the
4077 most common in this category. For the Quantum Fireball drives I would
4078 suggest no more than 8 commands per device.
4082 Collect statistics to report in /proc
4083 CONFIG_AIC7XXX_PROC_STATS
4084 This option tells the driver to keep track of how many commands have
4085 been sent to each particular device and report that information to
4086 the user via the /proc/scsi/aic7xxx/n file, where n is the number of
4087 the aic7xxx controller you want the information on. This adds a
4088 small amount of overhead to each and every SCSI command the aic7xxx
4089 driver handles, so if you aren't really interested in this
4090 information, it is best to leave it disabled. This will only work if
4091 you also say Y to "/proc filesystem support", below.
4095 Delay in seconds after SCSI bus reset
4096 CONFIG_AIC7XXX_RESET_DELAY
4097 This sets how long the driver will wait after resetting the SCSI bus
4098 before attempting to communicate with the devices on the SCSI bus
4099 again. This delay will be used during the reset phase at bootup time
4100 as well as after any reset that might occur during normal operation.
4101 Reasonable numbers range anywhere from 5 to 15 seconds depending on
4102 your devices. DAT tape drives are notorious for needing more time
4103 after a bus reset to be ready for the next command, but most hard
4104 drives and CD-ROM devices are ready in only a few seconds. This
4105 option has a maximum upper limit of 20 seconds to avoid bad
4106 interactions between the aic7xxx driver and the rest of the linux
4107 kernel. The default value has been reduced to 5 seconds. If this
4108 doesn't work with your hardware, try increasing this value.
4110 BusLogic SCSI support
4111 CONFIG_SCSI_BUSLOGIC
4112 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
4113 Adapters. Consult the SCSI-HOWTO, available via anonymous FTP from
4114 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO, and the files
4115 README.BusLogic and README.FlashPoint in drivers/scsi for more
4116 information. If this driver does not work correctly without
4117 modification, please contact the author, Leonard N. Zubkoff, by
4118 email to lnz@dandelion.com.
4120 You can also build this driver as a module ( = code which can be
4121 inserted in and removed from the running kernel whenever you want),
4122 but only a single instance may be loaded. If you want to compile it
4123 as a module, say M here and read Documentation/modules.txt. The
4124 module will be called BusLogic.o.
4126 Omit BusLogic SCSI FlashPoint support
4127 CONFIG_SCSI_OMIT_FLASHPOINT
4128 This option allows you to omit the FlashPoint support from the
4129 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
4130 substantial, so users of MultiMaster Host Adapters may wish to omit
4133 DTC3180/3280 SCSI support
4135 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
4136 the SCSI-HOWTO, available via FTP (user: anonymous) at
4137 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO and the file
4138 drivers/scsi/README.dtc3x80.
4140 This driver is also available as a module ( = code which can be
4141 inserted in and removed from the running kernel whenever you want).
4142 The module will be called dtc.o. If you want to compile it as a
4143 module, say M here and read Documentation/modules.txt.
4145 EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti, Alphatronix) support
4146 CONFIG_SCSI_EATA_DMA
4147 This is support for the EATA-DMA protocol compliant SCSI Host
4148 Adapters like the SmartCache III/IV, SmartRAID controller families
4149 and the DPT PM2011B and PM2012B controllers.
4151 Note that this driver is obsolete; if you have one of the above SCSI
4152 Host Adapters, you should normally say N here and Y to "EATA
4153 ISA/EISA/PCI support", below. Please read the SCSI-HOWTO, available
4154 via FTP (user: anonymous) at
4155 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4157 This driver is also available as a module ( = code which can be
4158 inserted in and removed from the running kernel whenever you want).
4159 The module will be called eata_dma.o. If you want to compile it as a
4160 module, say M here and read Documentation/modules.txt.
4162 EATA-PIO (old DPT PM2001, PM2012A) support
4163 CONFIG_SCSI_EATA_PIO
4164 This driver supports all EATA-PIO protocol compliant SCSI Host
4165 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
4166 host adapters could also use this driver but are discouraged from
4167 doing so, since this driver only supports hard disks and lacks
4168 numerous features. You might want to have a look at the SCSI-HOWTO,
4169 available via FTP (user: anonymous) at
4170 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4172 If you want to compile this as a module ( = code which can be
4173 inserted in and removed from the running kernel whenever you want),
4174 say M here and read Documentation/modules.txt. The module will be
4177 UltraStor 14F/34F support
4179 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
4180 The source at drivers/scsi/u14-34f.c contains some information about
4181 this hardware. If the driver doesn't work out of the box, you may
4182 have to change some settings in drivers/scsi/u14-34f.c. Read the
4183 SCSI-HOWTO, available via FTP (user: anonymous) at
4184 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Note that there is also
4185 another driver for the same hardware: "UltraStor SCSI support",
4186 below. You should say Y to both only if you want 24F support as
4189 This driver is also available as a module ( = code which can be
4190 inserted in and removed from the running kernel whenever you want).
4191 The module will be called u14-34f.o. If you want to compile it as a
4192 module, say M here and read Documentation/modules.txt.
4194 enable elevator sorting
4195 CONFIG_SCSI_U14_34F_LINKED_COMMANDS
4196 This option enables elevator sorting for all probed SCSI disks and
4197 CDROMs. It definitely reduces the average seek distance when doing
4198 random seeks, but this does not necessarily result in a noticeable
4199 performance improvement: your mileage may vary...
4201 The safe answer is N.
4203 maximum number of queued commands
4204 CONFIG_SCSI_U14_34F_MAX_TAGS
4205 This specifies how many SCSI commands can be maximally queued for
4206 each probed SCSI device. You should reduce the default value of 8
4207 only if you have disks with buggy or limited tagged command support.
4208 Minimum is 2 and maximum is 14. This value is also the window size
4209 used by the elevator sorting option above. The effective value used
4210 by the driver for each probed SCSI device is reported at boot time.
4212 Future Domain 16xx SCSI/AHA-2920A support
4213 CONFIG_SCSI_FUTURE_DOMAIN
4214 This is support for Future Domain's 16-bit SCSI host adapters
4215 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
4216 other adapters based on the Future Domain chipsets (Quantum
4217 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
4218 It is explained in section 3.7 of the SCSI-HOWTO, available via FTP
4219 (user: anonymous) at ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4221 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
4222 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
4223 controller support"). This Future Domain driver works with the older
4224 Adaptec AHA-2920A boards with a Future Domain chip on them.
4226 This driver is also available as a module ( = code which can be
4227 inserted in and removed from the running kernel whenever you want).
4228 The module will be called fdomain.o. If you want to compile it as a
4229 module, say M here and read Documentation/modules.txt.
4231 Future Domain MCS-600/700 SCSI support
4233 This is support for Future Domain MCS 600/700 MCA SCSI adapters. Some
4234 PS/2 computers are equipped with IBM Fast SCSI Adapter/A which is
4235 identical to the MCS 700 and hence also supported by this driver.
4236 This driver also supports the Reply SB16/SCSI card (the SCSI part).
4237 It supports multiple adapters in the same system.
4239 Generic NCR5380/53c400 SCSI support
4240 CONFIG_SCSI_GENERIC_NCR5380
4241 This is the generic NCR family of SCSI controllers, not to be
4242 confused with the NCR 53c7 or 8xx controllers. It is explained in
4243 section 3.8 of the SCSI-HOWTO, available via FTP (user: anonymous)
4244 at ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work
4245 out of the box, you may have to change some settings in
4246 drivers/scsi/g_NCR5380.h.
4248 This driver is also available as a module ( = code which can be
4249 inserted in and removed from the running kernel whenever you want).
4250 The module will be called g_NCR5380.o. If you want to compile it as
4251 a module, say M here and read Documentation/modules.txt.
4253 Enable NCR53c400 extensions
4254 CONFIG_SCSI_GENERIC_NCR53C400
4255 This enables certain optimizations for the NCR53c400 SCSI cards. You
4256 might as well try it out. Note that this driver will only probe for
4257 the Trantor T130B in its default configuration; you might have to
4258 pass a command line option to the kernel at boot time if it doesn't
4259 detect your card. See the file drivers/scsi/README.g_NCR5380 for
4262 NCR5380/53c400 mapping method (use Port for T130B)
4263 CONFIG_SCSI_G_NCR5380_PORT
4264 The NCR5380 and NCR53c400 SCSI controllers come in two varieties:
4265 port or memory mapped. You should know what you have. The most
4266 common card, Trantor T130B, uses port mapped mode.
4268 NCR53c7,8xx SCSI support
4269 CONFIG_SCSI_NCR53C7xx
4270 This is a driver for the 53c7 and 8xx NCR family of SCSI
4271 controllers, not to be confused with the NCR 5380 controllers. It is
4272 explained in section 3.8 of the SCSI-HOWTO, available via FTP (user:
4273 anonymous) at ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. If it
4274 doesn't work out of the box, you may have to change some settings in
4275 drivers/scsi/53c7,8xx.h. Please read drivers/scsi/README.ncr53c7xx
4276 for the available boot time command line options.
4278 Note: there is another driver for the 53c8xx family of controllers
4279 ("NCR53C8XX SCSI support" below). If you want to use them both, you
4280 need to say M to both and build them as modules, but only one may be
4281 active at a time. If you have a 53c8xx board, it's better to use the
4284 This driver is also available as a module ( = code which can be
4285 inserted in and removed from the running kernel whenever you want).
4286 The module will be called 53c7,8xx.o. If you want to compile it as a
4287 module, say M here and read Documentation/modules.txt.
4289 always negotiate synchronous transfers
4290 CONFIG_SCSI_NCR53C7xx_sync
4291 In general, this is good; however, it is a bit dangerous since there
4292 are some broken SCSI devices out there. Take your chances. Safe bet
4295 allow FAST-SCSI [10MHz]
4296 CONFIG_SCSI_NCR53C7xx_FAST
4297 This will enable 10MHz FAST-SCSI transfers with your host
4298 adapter. Some systems have problems with that speed, so it's safest
4302 CONFIG_SCSI_NCR53C7xx_DISCONNECT
4303 This enables the disconnect/reconnect feature of the NCR SCSI
4304 controller. When you say Y here, a slow SCSI device will not lock
4305 the SCSI bus while processing a request, allowing simultaneous use
4306 of e.g. a SCSI hard disk and SCSI tape or CD-ROM drive, and
4307 providing much better performance when using slow and fast SCSI
4308 devices at the same time. Some devices, however, do not operate
4309 properly with this option enabled, and will cause your SCSI system
4310 to hang, which might cause a system crash. The safe answer
4311 therefore is to say N.
4313 NCR53C8XX SCSI support
4314 CONFIG_SCSI_NCR53C8XX
4315 This is the BSD ncr driver adapted to Linux for the NCR53C8XX family
4316 of PCI-SCSI controllers. This driver supports parity checking,
4317 tagged command queuing and fast synchronous data transfers up to 80
4318 MB/s with wide FAST-40 LVD devices and controllers.
4320 Recent versions of the 53C8XX chips are better supported by the
4321 option "SYM53C8XX SCSI support", below.
4323 Note: there is yet another driver for the 53c8xx family of controllers
4324 ("NCR53c7,8xx SCSI support" above). If you want to use them both,
4325 you need to say M to both and build them as modules, but only one
4326 may be active at a time. If you have a 53c8xx board, you probably do
4327 not want to use the "NCR53c7,8xx SCSI support".
4329 Please read drivers/scsi/README.ncr53c8xx for more information.
4331 SYM53C8XX SCSI support
4332 CONFIG_SCSI_SYM53C8XX
4333 This driver supports all the features of recent 53C8XX chips (used
4334 in PCI SCSI controllers), notably the hardware phase mismatch
4335 feature of the SYM53C896.
4337 Older versions of the 53C8XX chips are not supported by this
4338 driver. If your system uses either a 810 rev. < 16, a 815, or a 825
4339 rev. < 16 PCI SCSI processor, you must use the generic NCR53C8XX
4340 driver ("NCR53C8XX SCSI support" above) or configure both the
4341 NCR53C8XX and this SYM53C8XX drivers either as module or linked to
4344 When both drivers are linked to the kernel, the SYM53C8XX driver is
4345 called first at initialization and you can use the 'excl=ioaddr'
4346 driver boot option to exclude attachment of adapters by the SYM53C8XX
4347 driver. For instance, entering 'sym53c8xx=excl:0xb400,excl=0xc000' at
4348 lilo prompt prevents adapters at io address 0xb400 and 0xc000 from
4349 being attached by the SYM53C8XX driver, thus allowing the NCR53C8XX
4350 driver to attach them. The 'excl' option is also supported by the
4353 Please read drivers/scsi/README.ncr53c8xx for more information.
4355 synchronous data transfers frequency
4356 CONFIG_SCSI_NCR53C8XX_SYNC
4357 The SCSI Parallel Interface-2 Standard defines 4 classes of transfer
4358 rates: FAST-5, FAST-10, FAST-20 and FAST-40. The numbers are
4359 respectively the maximum data transfer rates in mega-transfers per
4360 second for each class. For example, a FAST-20 Wide 16 device is able
4361 to transfer data at 20 million 16 bit packets per second for a total
4364 You may specify 0 if you want to only use asynchronous data
4365 transfers. This is the safest and slowest option. Otherwise, specify
4366 a value between 5 and 40, depending on the capability of your SCSI
4367 controller. The higher the number, the faster the data transfer.
4368 Note that 40 should normally be ok since the driver decreases the
4369 value automatically according to the controller's capabilities.
4371 Your answer to this question is ignored for controllers with NVRAM,
4372 since the driver will get this information from the user set-up. It
4373 also can be overridden using a boot setup option, as follows
4374 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
4375 for FAST-20 synchronous data transfer (20 mega-transfers per
4378 The normal answer therefore is not to go with the default but to
4379 select the maximum value 40 allowing the driver to use the maximum
4380 value supported by each controller. If this causes problems with
4381 your SCSI devices, you should come back and decrease the value.
4383 There is no safe option other than using good cabling, right
4384 terminations and SCSI conformant devices.
4387 CONFIG_SCSI_NCR53C8XX_IOMAPPED
4388 If you say Y here, the driver will use normal IO, as opposed to
4389 memory mapped IO. Memory mapped IO has less latency than normal IO
4390 and works for most Intel-based hardware. Under Linux/Alpha only
4391 normal IO is currently supported by the driver and so, this option
4392 has no effect on those systems.
4394 The normal answer therefore is N; try Y only if you encounter SCSI
4397 not allow targets to disconnect
4398 CONFIG_SCSI_NCR53C8XX_NO_DISCONNECT
4399 This option is only provided for safety if you suspect some SCSI
4400 device of yours to not support properly the target-disconnect
4401 feature. In that case, you would say Y here. In general however, to
4402 not allow targets to disconnect is not reasonable if there is more
4403 than 1 device on a SCSI bus. The normal answer therefore is N.
4405 default tagged command queue depth
4406 CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS
4407 "Tagged command queuing" is a feature of SCSI-2 which improves
4408 performance: the host adapter can send several SCSI commands to a
4409 device's queue even if previous commands haven't finished yet. Some
4410 SCSI devices don't implement this properly; if you want to disable
4411 this feature, enter 0 or 1 here (it doesn't matter which).
4413 The default value is 8 and should be supported by most hard disks.
4414 This value can be overridden from the boot command line using the
4415 'tags' option as follows (example):
4416 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
4417 4, set queue depth to 16 for target 2 and target 3 on controller 0
4418 and set queue depth to 10 for target 0 / lun 2 on controller 1.
4420 The normal answer therefore is to go with the default 8 and to use
4421 a boot command line option for devices that need to use a different
4422 command queue depth.
4424 There is no safe option other than using good SCSI devices.
4426 maximum number of queued commands
4427 CONFIG_SCSI_NCR53C8XX_MAX_TAGS
4428 This option allows you to specify the maximum number of commands
4429 that can be queued to any device, when tagged command queuing is
4430 possible. The default value is 32. Minimum is 2, maximum is 64.
4431 Modern hard disks are able to support 64 tags and even more, but
4432 do not seem to be faster when more than 32 tags are being used.
4434 So, the normal answer here is to go with the default value 32 unless
4435 you are using very large hard disks with large cache (>= 1 MB) that
4436 are able to take advantage of more than 32 tagged commands.
4438 There is no safe option and the default answer is recommended.
4440 assume boards are SYMBIOS compatible
4441 CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT
4442 This option allows you to enable some features depending on GPIO
4443 wiring. These General Purpose Input/Output pins can be used for
4444 vendor specific features or implementation of the standard SYMBIOS
4445 features. Genuine SYMBIOS controllers use GPIO0 in output for
4446 controller LED and GPIO3 bit as a flag indicating
4447 singled-ended/differential interface. The Tekram DC-390U/F boards
4448 uses a different GPIO wiring.
4450 Your answer to this question is ignored if all your controllers have
4451 NVRAM, since the driver is able to detect the board type from the
4454 If all the controllers in your system are genuine SYMBIOS boards or
4455 use BIOS and drivers from SYMBIOS, you would want to say Y here,
4456 otherwise N. N is the safe answer.
4458 enable profiling statistics gathering
4459 CONFIG_SCSI_NCR53C8XX_PROFILE
4460 This option allows you to enable profiling information gathering.
4461 These statistics are not very accurate due to the low frequency
4462 of the kernel clock (100 Hz on i386) and have performance impact
4463 on systems that use very fast devices.
4465 The normal answer therefore is N.
4467 include support for the NCR PQS/PDS SCSI card
4468 CONFIG_SCSI_NCR53C8XX_PQS_PDS
4469 Say Y here if you have a special SCSI adapter produced by NCR
4470 corporation called a PCI Quad SCSI or PCI Dual SCSI. You do not need
4471 this if you do not have one of these adapters. However, since this
4472 device is detected as a specific PCI device, this option is quite
4475 The common answer here is N, but answering Y is safe.
4479 This is support for the IBM SCSI adapter found in many of the PS/2
4480 series computers. These machines have an MCA bus, so you need to
4481 answer Y to "MCA support" as well and read Documentation/mca.txt.
4483 If the adapter isn't found during boot (a common problem for models
4484 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
4485 option, where <pun> is the id of the SCSI subsystem (usually 7, but
4486 if that doesn't work check your reference diskette). Owners of model
4487 95 with a LED-matrix-display can in addition activate some activity
4488 info like under OS/2, but more informative, by setting
4489 'ibmmcascsi=display' as an additional kernel parameter. Try "man
4490 bootparam" or see the documentation of your boot loader about how to
4491 pass options to the kernel. The lilo procedure is also explained in
4492 the SCSI-HOWTO, available via FTP (user: anonymous) in
4493 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4495 If you want to compile this driver as a module ( = code which can be
4496 inserted in and removed from the running kernel whenever you want),
4497 say M here and read Documentation/modules.txt. The module will be
4501 CONFIG_IBMMCA_SCSI_ORDER_STANDARD
4502 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
4503 are assigned to the drive letters, starting with the lowest SCSI-id
4504 (physical number -- pun) to be drive C:, as seen from DOS and
4505 similar operating systems. When looking into papers describing the
4506 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
4507 The SCSI-standard follows a hardware-hierarchy which says that id 7
4508 has the highest priority and id 0 the lowest. Therefore, the host
4509 adapters are still today everywhere placed as SCSI-id 7 by default.
4510 In the SCSI-standard, the drive letters express the priority of the
4511 disk. C: should be the hard disk, or a partition on it, with the
4512 highest priority. This must therefore be the disk with the highest
4513 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
4514 original definition of the SCSI-standard as also industrial- and
4515 process-control-machines, like VME-CPUs running under realtime-OSs
4516 (e.g. LynxOS, OS9) do.
4518 If you like to run Linux on your MCA-machine with the same
4519 assignment of hard disks as seen from e.g. DOS or OS/2 on your
4520 machine, which is in addition conformant to the SCSI-standard, you
4521 must say Y here. This is also necessary for MCA-Linux users who want
4522 to keep downward compatibility to older releases of the
4523 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
4526 If you like to have the lowest SCSI-id assigned as drive C:, as
4527 modern SCSI-BIOSes do, which does not conform to the standard, but
4528 is widespread and common in the PC-world of today, you must say N
4529 here. If unsure, say Y.
4531 Reset SCSI-devices at boot time
4532 CONFIG_IBMMCA_SCSI_DEV_RESET
4533 By default, SCSI-devices are reset when the machine is powered on.
4534 However, some devices exist, like special-control-devices,
4535 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
4536 not reset when switched on. If you say Y here, each device connected
4537 to your SCSI-bus will be issued a reset-command after it has been
4538 probed, while the kernel is booting. This may cause problems with
4539 more modern devices, like hard disks, which do not appreciate these
4540 reset commands, and can cause your system to hang. So say Y only if
4541 you know that one of your older devices needs it; N is the safe
4544 NCR 53C9x MCA support
4545 CONFIG_SCSI_MCA_53C9X
4546 Some Microchannel machines, notably the NCR 35xx line, use a SCSI
4547 controller based on the NCR 53C94. This driver will allow use of
4548 the controller on the 3550, and very possibly others.
4550 If you want to compile this as a module (= code which can be
4551 inserted and removed from the running kernel whenever you want), say
4552 M here and read Documentation/modules.txt. The module will be called
4555 Always IN2000 SCSI support
4557 This is support for an ISA bus SCSI host adapter. You'll find more
4558 information in drivers/scsi/in2000.readme. If it doesn't work out of
4559 the box, you may have to change the jumpers for IRQ or address
4562 If you want to compile this as a module ( = code which can be
4563 inserted in and removed from the running kernel whenever you want),
4564 say M here and read Documentation/modules.txt. The module will be
4567 Initio 91XXU(W) SCSI support
4569 This is support for the Initio 91XXU(W) SCSI host adapter.
4570 Please read the SCSI-HOWTO, available via FTP (user: anonymous) at
4571 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4573 If you want to compile this as a module ( = code which can be
4574 inserted in and removed from the running kernel whenever you want),
4575 say M here and read Documentation/modules.txt. The module will be
4580 This is support for a SCSI host adapter. It is explained in section
4581 3.10 of the SCSI-HOWTO, available via FTP (user: anonymous) at
4582 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work out
4583 of the box, you may have to change some settings in
4584 drivers/scsi/pas16.h.
4586 This driver is also available as a module ( = code which can be
4587 inserted in and removed from the running kernel whenever you want).
4588 The module will be called pas16.o. If you want to compile it as a
4589 module, say M here and read Documentation/modules.txt.
4591 Initio INI-A100U2W SCSI support
4593 This is support for the Initio INI-A100U2W SCSI host adapter.
4594 Please read the SCSI-HOWTO, available via FTP (user: anonymous) at
4595 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4597 If you want to compile this as a module ( = code which can be
4598 inserted in and removed from the running kernel whenever you want),
4599 say M here and read Documentation/modules.txt. The module will be
4604 This is support for the PCI2000I EIDE interface card which acts as a
4605 SCSI host adapter. Please read the SCSI-HOWTO, available via FTP
4606 (user: anonymous) at ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4608 This driver is also available as a module called pci2000.o ( = code
4609 which can be inserted in and removed from the running kernel
4610 whenever you want). If you want to compile it as a module, say M
4611 here and read Documentation/modules.txt.
4614 CONFIG_SCSI_PCI2220I
4615 This is support for the PCI2220i EIDE interface card which acts as a
4616 SCSI host adapter. Please read the SCSI-HOWTO, available via FTP
4617 (user: anonymous) at ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4619 This driver is also available as a module called pci2220i.o ( = code
4620 which can be inserted in and removed from the running kernel
4621 whenever you want). If you want to compile it as a module, say M
4622 here and read Documentation/modules.txt.
4626 This is support for the PSI240i EIDE interface card which acts as a
4627 SCSI host adapter. Please read the SCSI-HOWTO, available via FTP
4628 (user: anonymous) at ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4630 This driver is also available as a module called psi240i.o ( = code
4631 which can be inserted in and removed from the running kernel
4632 whenever you want). If you want to compile it as a module, say M
4633 here and read Documentation/modules.txt.
4635 Qlogic FAS SCSI support
4636 CONFIG_SCSI_QLOGIC_FAS
4637 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
4638 FastSCSI! cards as well as any other card based on the FASXX chip
4639 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
4641 This driver does NOT support the PCI versions of these cards. The
4642 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
4643 SCSI support"), below.
4645 Information about this driver is contained in
4646 drivers/scsi/README.qlogicfas. You should also read the SCSI-HOWTO,
4647 available via FTP (user: anonymous) at
4648 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4650 This driver is also available as a module ( = code which can be
4651 inserted in and removed from the running kernel whenever you want).
4652 The module will be called qlogicfas.o. If you want to compile it as
4653 a module, say M here and read Documentation/modules.txt.
4655 Qlogic ISP SCSI support (EXPERIMENTAL)
4656 CONFIG_SCSI_QLOGIC_ISP
4657 This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
4658 IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
4659 card is supported by the "AM53/79C974 PCI SCSI" driver).
4661 If you say Y here, make sure to choose "BIOS" at the question "PCI
4664 Please read the file drivers/scsi/README.qlogicisp. You should also
4665 read the SCSI-HOWTO, available via FTP (user: anonymous) at
4666 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4668 This driver is also available as a module ( = code which can be
4669 inserted in and removed from the running kernel whenever you want).
4670 The module will be called qlogicisp.o. If you want to compile it as
4671 a module, say M here and read Documentation/modules.txt.
4673 Qlogic ISP FC SCSI support
4674 CONFIG_SCSI_QLOGIC_FC
4675 This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
4677 This driver is also available as a module ( = code which can be
4678 inserted in and removed from the running kernel whenever you want).
4679 The module will be called qlogicfc.o. If you want to compile it as
4680 a module, say M here and read Documentation/modules.txt.
4682 Seagate ST-02 and Future Domain TMC-8xx SCSI support
4684 These are 8-bit SCSI controllers; the ST-01 is also supported by
4685 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
4686 available via FTP (user: anonymous) at
4687 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work out
4688 of the box, you may have to change some settings in
4689 drivers/scsi/seagate.h.
4691 This driver is also available as a module ( = code which can be
4692 inserted in and removed from the running kernel whenever you want).
4693 The module will be called seagate.o. If you want to compile it as a
4694 module, say M here and read Documentation/modules.txt.
4696 Trantor T128/T128F/T228 SCSI support
4698 This is support for a SCSI host adapter. It is explained in section
4699 3.11 of the SCSI-HOWTO, available via FTP (user: anonymous) at
4700 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work out
4701 of the box, you may have to change some settings in
4702 drivers/scsi/t128.h. Note that Trantor was purchased by Adaptec, and
4703 some former Trantor products are being sold under the Adaptec name.
4705 This driver is also available as a module ( = code which can be
4706 inserted in and removed from the running kernel whenever you want).
4707 The module will be called t128.o. If you want to compile it as a
4708 module, say M here and read Documentation/modules.txt.
4710 UltraStor SCSI support
4711 CONFIG_SCSI_ULTRASTOR
4712 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
4713 adapter family. This driver is explained in section 3.12 of the
4714 SCSI-HOWTO, available via FTP (user: anonymous) at
4715 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work out
4716 of the box, you may have to change some settings in
4717 drivers/scsi/ultrastor.h.
4719 Note that there is also another driver for the same hardware:
4720 "UltraStor 14F/34F support", above.
4722 If you want to compile this as a module ( = code which can be
4723 inserted in and removed from the running kernel whenever you want),
4724 say M here and read Documentation/modules.txt. The module will be
4727 7000FASST SCSI support
4728 CONFIG_SCSI_7000FASST
4729 This driver supports the Western Digital 7000 SCSI host adapter
4730 family. Some information is in the source: drivers/scsi/wd7000.c.
4732 This driver is also available as a module ( = code which can be
4733 inserted in and removed from the running kernel whenever you
4734 want). The module will be called wd7000.o. If you want to compile it
4735 as a module, say M here and read Documentation/modules.txt.
4739 This driver supports the ACARD 870U/W SCSI host adapter.
4741 This driver is also available as a module ( = code which can be
4742 inserted in and removed from the running kernel whenever you want).
4743 The module will be called atp870u.o. If you want to compile it as a
4744 module, say M here and read Documentation/modules.txt.
4746 EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support
4748 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
4749 ISA and all EISA i/o addresses are probed looking for the "EATA"
4750 signature. If you chose "BIOS" at the question "PCI access mode",
4751 the addresses of all the PCI SCSI controllers reported by the PCI
4752 subsystem are probed as well.
4754 You want to read the start of drivers/scsi/eata.c and the
4755 SCSI-HOWTO, available via FTP (user: anonymous) at
4756 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4758 Note that there is also another driver for the same hardware
4759 available: "EATA-DMA support". You should say Y to only one of them.
4761 If you want to compile this as a module ( = code which can be
4762 inserted in and removed from the running kernel whenever you want),
4763 say M here and read Documentation/modules.txt. The module will be
4766 enable tagged command queuing
4767 CONFIG_SCSI_EATA_TAGGED_QUEUE
4768 This is a feature of SCSI-2 which improves performance: the host
4769 adapter can send several SCSI commands to a device's queue even if
4770 previous commands haven't finished yet. Most EATA adapters negotiate
4771 this feature automatically with the device, even if your answer is
4772 N. The safe answer is N.
4774 enable elevator sorting
4775 CONFIG_SCSI_EATA_LINKED_COMMANDS
4776 This option enables elevator sorting for all probed SCSI disks and
4777 CDROMs. It definitely reduces the average seek distance when doing
4778 random seeks, but this does not necessarily result in a noticeable
4779 performance improvement: your mileage may vary...
4780 The safe answer is N.
4782 maximum number of queued commands
4783 CONFIG_SCSI_EATA_MAX_TAGS
4784 This specifies how many SCSI commands can be maximally queued for
4785 each probed SCSI device. You should reduce the default value of 16
4786 only if you have disks with buggy or limited tagged command support.
4787 Minimum is 2 and maximum is 62. This value is also the window size
4788 used by the elevator sorting option above. The effective value used
4789 by the driver for each probed SCSI device is reported at boot time.
4791 NCR53c406a SCSI support
4792 CONFIG_SCSI_NCR53C406A
4793 This is support for the NCR53c406a SCSI host adapter. For user
4794 configurable parameters, check out drivers/scsi/NCR53c406.c in the
4795 kernel source. Also read the SCSI-HOWTO, available via FTP (user:
4796 anonymous) at ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4798 If you want to compile this driver as a module ( = code which can be
4799 inserted in and removed from the running kernel whenever you want),
4800 say M here and read Documentation/modules.txt. The module will be
4803 Symbios Logic sym53c416 support
4804 CONFIG_SCSI_SYM53C416
4805 This is support for the sym53c416 SCSI host adapter, the SCSI
4806 adapter that comes with some HP scanners. This driver requires that
4807 the sym53c416 is configured first using some sort of pnp
4808 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
4809 are using isapnp then you need to compile this driver as a module
4810 and then load it using insmod after isapnp has run. The parameters
4811 of the configured card(s) should be passed to the driver. The format
4814 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
4816 There is support for up to four adapters. If you want to compile
4817 this driver as a module ( = code which can be inserted in and
4818 removed from the running kernel whenever you want), say M here and
4819 read Documentation/modules.txt. The module will be called
4822 Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support
4824 This driver supports PCI SCSI host adapters based on the Am53C974A
4825 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
4826 PCscsi/PCnet (Am53/79C974) solutions.
4828 Documentation can be found in linux/drivers/scsi/README.tmscsim.
4830 Note that this driver does NOT support Tekram DC390W/U/F, which are
4831 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
4832 Also note that there is another generic Am53C974 driver,
4833 "AM53/79C974 PCI SCSI support" below. You can pick either one.
4835 If you want to compile this driver as a module ( = code which can be
4836 inserted in and removed from the running kernel whenever you want),
4837 say M here and read Documentation/modules.txt. The module will be
4840 Omit support for other Am53/79C974 based SCSI adapters
4841 CONFIG_SCSI_DC390T_NOGENSUPP
4842 If you say N here, the DC390(T) SCSI driver relies on the DC390
4843 EEPROM to get initial values for its settings, such as speed,
4844 termination, etc. If it can't find this EEPROM, it will use defaults
4845 or the user supplied boot/module parameters. For details on driver
4846 configuration see linux/drivers/scsi/README.tmscsim.
4848 If you say Y here and if no EEPROM is found, the driver gives up and
4849 thus only supports Tekram DC390(T) adapters. This can be useful if
4850 you have a DC390(T) and another Am53C974 based adapter, which, for
4851 some reason, you want to drive with the other AM53C974 driver.
4855 AM53/79C974 PCI SCSI support
4856 CONFIG_SCSI_AM53C974
4857 This is support for the AM53/79C974 SCSI host adapters. Please read
4858 drivers/scsi/README.AM53C974 for details. Also, the SCSI-HOWTO,
4859 available via FTP (user: anonymous) at
4860 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO, is for you.
4862 Note that there is another driver for AM53C974 based adapters:
4863 "Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support", above. You
4864 can pick either one.
4866 If you want to compile this driver as a module ( = code which can be
4867 inserted in and removed from the running kernel whenever you want),
4868 say M here and read Documentation/modules.txt. The module will be
4871 AMI MegaRAID support
4872 CONFIG_SCSI_MEGARAID
4873 This driver supports the AMI MegaRAID 428 and 438 (and maybe 466)
4876 If you want to compile this driver as a module ( = code which can be
4877 inserted in and removed from the running kernel whenever you want),
4878 say M here and read Documentation/modules.txt. The module will be
4884 #Concurrent IO commands on MegaRAID
4885 #CONFIG_MEGARAID_MULTI_IO
4887 GDT SCSI Disk Array Controller support
4889 This is a driver for all SCSI Disk Array Controllers (EISA/ISA/PCI)
4890 manufactured by ICP vortex. It is documented in the kernel source in
4891 drivers/scsi/gdth.c and drivers/scsi/gdth.h.
4893 This driver is also available as a module ( = code which can be
4894 inserted in and removed from the running kernel whenever you want).
4895 If you want to compile it as a module, say M here and read
4896 Documentation/modules.txt.
4898 IOMEGA parallel port (ppa - older drives)
4900 This driver supports older versions of IOMEGA's parallel port ZIP
4901 drive (a 100 MB removable media device).
4903 Note that you can say N here if you have the SCSI version of the ZIP
4904 drive: it will be supported automatically if you said Y to the
4905 generic "SCSI disk support", above.
4907 If you have the ZIP Plus drive or a more recent parallel port ZIP
4908 drive (if the supplied cable with the drive is labeled "AutoDetect")
4909 then you should say N here and Y to "IOMEGA parallel port (imm -
4910 newer drives)", below.
4912 For more information about this driver and how to use it you should
4913 read the file drivers/scsi/README.ppa. You should also read the
4914 SCSI-HOWTO, which is available via FTP (user: anonymous) from
4915 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. If you use this driver,
4916 you will still be able to use the parallel port for other tasks,
4917 such as a printer; it is safe to compile both drivers into the
4920 This driver is also available as a module which can be inserted in
4921 and removed from the running kernel whenever you want. To compile
4922 this driver as a module, say M here and read
4923 Documentation/modules.txt. The module will be called ppa.o.
4925 IOMEGA parallel port (imm - newer drives)
4927 This driver supports newer versions of IOMEGA's parallel port ZIP
4928 drive (a 100 MB removable media device).
4930 Note that you can say N here if you have the SCSI version of the ZIP
4931 drive: it will be supported automatically if you said Y to the
4932 generic "SCSI disk support", above.
4934 If you have the ZIP Plus drive or a more recent parallel port ZIP
4935 drive (if the supplied cable with the drive is labeled "AutoDetect")
4936 then you should say Y here; if you have an older ZIP drive, say N
4937 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
4939 For more information about this driver and how to use it you should
4940 read the file drivers/scsi/README.ppa. You should also read the
4941 SCSI-HOWTO, which is available via FTP (user: anonymous) from
4942 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. If you use this driver,
4943 you will still be able to use the parallel port for other tasks,
4944 such as a printer; it is safe to compile both drivers into the
4947 This driver is also available as a module which can be inserted in
4948 and removed from the running kernel whenever you want. To compile
4949 this driver as a module, say M here and read
4950 Documentation/modules.txt. The module will be called imm.o.
4952 Force the Iomega ZIP drivers to use EPP-16
4953 CONFIG_SCSI_IZIP_EPP16
4954 EPP (Enhanced Parallel Port) is a standard for parallel ports which
4955 allows them to act as expansion buses that can handle up to 64
4958 Some parallel port chipsets are slower than their motherboard, and
4959 so we have to control the state of the chipset's FIFO queue every
4960 now and then to avoid data loss. This will be done if you say Y
4963 Generally, saying Y is the safe option and slows things down a bit.
4965 Assume slow parallel port control register
4966 CONFIG_SCSI_IZIP_SLOW_CTR
4967 Some parallel ports are known to have excessive delays between
4968 changing the parallel port control register and good data being
4969 available on the parallel port data/status register. This option
4970 forces a small delay (1.0 usec to be exact) after changing the
4971 control register to let things settle out. Enabling this option may
4972 result in a big drop in performance but some very old parallel ports
4973 (found in 386 vintage machines) will not work properly.
4975 Generally, saying N is fine.
4977 SCSI Debug host simulator.
4979 This is a host adapter simulator that can be programmed to simulate
4980 a large number of conditions that could occur on a real bus. The
4981 advantage is that many hard to reproduce problems can be tested in a
4982 controlled environment where there is reduced risk of losing
4983 important data. This is primarily of use to people trying to debug
4984 the middle and upper layers of the SCSI subsystem. If unsure, say N.
4986 Fibre Channel support
4988 This is an experimental support for storage arrays connected to
4989 the system using Fibre Optic and the "X3.269-199X Fibre Channel
4990 Protocol for SCSI" specification. You'll also need the generic SCSI
4991 support, as well as the drivers for the storage array itself and
4992 for the interface adapter such as SOC. This subsystem could even
4993 serve for IP networking, with some code extensions.
4999 Serial Optical Channel is an interface card with one or two Fibre
5000 Optic ports, each of which can be connected to a disk array. Only
5001 the SBus incarnation of the adapter is supported at the moment.
5003 SparcSTORAGE Array 100 and 200 series
5005 If you never bought a disk array made by Sun, go with N.
5008 CONFIG_SCSI_ACORNSCSI_3
5009 This enables support for the Acorn SCSI card (aka30). If you have an
5010 Acorn system with one of these, say Y. If unsure, say N.
5012 Acorn SCSI tagged queue support
5013 CONFIG_SCSI_ACORNSCSI_TAGGED_QUEUE
5014 Say Y here to enable tagged queuing support on the Acorn SCSI card.
5016 This is a feature of SCSI-2 which improves performance: the host
5017 adapter can send several SCSI commands to a device's queue even if
5018 previous commands haven't finished yet. Some SCSI devices don't
5019 implement this properly, so the safe answer is N.
5021 Acorn SCSI Synchronous transfers support
5022 CONFIG_SCSI_ACORNSCSI_SYNC
5023 Say Y here to enable synchronous transfer negotiation with all
5024 targets on the Acorn SCSI card.
5026 In general, this improves performance; however some SCSI devices
5027 don't implement it properly, so the safe answer is N.
5031 This enables support for the Oak SCSI card. If you have an Acorn
5032 system with one of these, say Y. If unsure, say N.
5034 Cumana SCSI I support
5035 CONFIG_SCSI_CUMANA_1
5036 This enables support for the Cumana SCSI I card. If you have an
5037 Acorn system with one of these, say Y. If unsure, say N.
5039 Cumana SCSI II support
5040 CONFIG_SCSI_CUMANA_2
5041 This enables support for the Cumana SCSI II card. If you have an
5042 Acorn system with one of these, say Y. If unsure, say N.
5046 This enables support for the EcoSCSI card -- a small card that sits
5047 in the Econet socket. If you have an Acorn system with one of these,
5048 say Y. If unsure, say N.
5051 CONFIG_SCSI_EESOXSCSI
5052 This enables support for the EESOX SCSI card. If you have an Acorn
5053 system with one of these, say Y, otherwise say N.
5055 Powertec SCSI support
5056 CONFIG_SCSI_POWERTECSCSI
5057 This enables support for the Powertec SCSI card on Acorn systems. If
5058 you have one of these, say Y. If unsure, say N.
5060 Network device support?
5062 You can say N here if you don't intend to connect your Linux box to
5063 any other computer at all or if all your connections will be over a
5064 telephone line with a modem either via UUCP (UUCP is a protocol to
5065 forward mail and news between unix hosts over telephone lines; read
5066 the UUCP-HOWTO, available via FTP (user: anonymous) in
5067 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO) or dialing up a shell
5068 account or a BBS, even using term (term is a program which gives you
5069 almost full Internet connectivity if you have a regular dial up
5070 shell account on some Internet connected Unix computer. Read
5071 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html (to browse
5072 the WWW, you need to have access to a machine on the Internet that
5073 has a program like lynx or netscape)).
5075 You'll have to say Y if your computer contains a network card that
5076 you want to use under Linux (make sure you know its name because you
5077 will be asked for it and read the Ethernet-HOWTO (especially if you
5078 plan to use more than one network card under Linux), available from
5079 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini) or if you want to
5080 use SLIP (Serial Line Internet Protocol is the protocol used to send
5081 Internet traffic over telephone lines or null modem cables) or CSLIP
5082 (compressed SLIP) or PPP (Point to Point Protocol, a better and
5083 newer replacement for SLIP) or PLIP (Parallel Line Internet Protocol
5084 is mainly used to create a mini network by connecting the parallel
5085 ports of two local machines) or AX.25/KISS (protocol for sending
5086 Internet traffic over amateur radio links).
5088 Make sure to read the NET-3-HOWTO. Eventually, you will have to read
5089 Olaf Kirch's excellent and free book "Network Administrator's
5090 Guide", to be found in ftp://metalab.unc.edu/pub/Linux/docs/LDP. If
5093 Dummy net driver support
5095 This is essentially a bit-bucket device (i.e. traffic you send to
5096 this device is consigned into oblivion) with a configurable IP
5097 address. It is most commonly used in order to make your currently
5098 inactive SLIP address seem like a real address for local programs.
5099 If you use SLIP or PPP, you might want to say Y here. Read about it
5100 in the Network Administrator's Guide, available via FTP (user:
5101 anonymous) from ftp://metalab.unc.edu/pub/Linux/docs/LDP. Since this
5102 thing often comes in handy, the default is Y. It won't enlarge your
5103 kernel either. What a deal.
5105 If you want to compile this as a module ( = code which can be
5106 inserted in and removed from the running kernel whenever you want),
5107 say M here and read Documentation/modules.txt. The module will be
5108 called dummy.o. If you want to use more than one dummy device at a
5109 time, you need to compile this driver as a module. Instead of
5110 'dummy', the devices will then be called 'dummy0', 'dummy1' etc.
5112 SLIP (serial line) support
5114 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
5115 connect to your Internet service provider or to connect to some
5116 other local Unix box or if you want to configure your Linux box as a
5117 Slip/CSlip server for other people to dial in. SLIP (Serial Line
5118 Internet Protocol) is a protocol used to send Internet traffic over
5119 serial connections such as telephone lines or null modem cables;
5120 nowadays, the protocol PPP is more commonly used for this same
5123 Normally, your access provider has to support SLIP in order for you
5124 to be able to use it, but there is now a SLIP emulator called SLiRP
5125 around (available via FTP (user: anonymous) from
5126 ftp://metalab.unc.edu/pub/Linux/system/network/serial/ ) which
5127 allows you to use SLIP over a regular dial up shell connection. If
5128 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
5129 NET-3-HOWTO, available via FTP (user: anonymous) in
5130 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO, explains how to
5131 configure SLIP. Note that you don't need this option if you just
5132 want to run term (term is a program which gives you almost full
5133 Internet connectivity if you have a regular dial up shell account on
5134 some Internet connected Unix computer. Read
5135 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html (to browse
5136 the WWW, you need to have access to a machine on the Internet that
5137 has a program like lynx or netscape)). SLIP support will enlarge
5138 your kernel by about 4 KB. If unsure, say N.
5140 If you want to compile this as a module ( = code which can be
5141 inserted in and removed from the running kernel whenever you want),
5142 say M here and read Documentation/modules.txt as well as
5143 Documentation/networking/net-modules.txt. The module will be called
5146 CSLIP compressed headers
5147 CONFIG_SLIP_COMPRESSED
5148 This protocol is faster than SLIP because it uses compression on the
5149 TCP/IP headers (not on the data itself), but it has to be supported
5150 on both ends. Ask your access provider if you are not sure and
5151 answer Y, just in case. You will still be able to use plain SLIP. If
5152 you plan to use SLiRP, the SLIP emulator (available via FTP (user:
5154 ftp://metalab.unc.edu/pub/Linux/system/network/serial/) which allows
5155 you to use SLIP over a regular dial up shell connection, you
5156 definitely want to say Y here. The NET-3-HOWTO, available via FTP
5157 (user: anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO,
5158 explains how to configure CSLIP. This won't enlarge your kernel.
5160 Keepalive and linefill
5162 Adds additional capabilities to the SLIP driver to support the
5163 RELCOM line fill and keepalive monitoring. Ideal on poor quality
5166 Six bit SLIP encapsulation
5167 CONFIG_SLIP_MODE_SLIP6
5168 Just occasionally you may need to run IP over hostile serial
5169 networks that don't pass all control characters or are only seven
5170 bit. Saying Y here adds an extra mode you can use with SLIP:
5171 "slip6". In this mode, SLIP will only send normal ASCII symbols over
5172 the serial device. Naturally, this has to be supported at the other
5173 end of the link as well. It's good enough, for example, to run IP
5174 over the async ports of a Camtec JNT Pad. If unsure, say N.
5176 PPP (point-to-point) support
5178 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
5179 the same purpose: sending Internet traffic over telephone (and other
5180 serial) lines. Ask your access provider if they support it, because
5181 otherwise you can't use it (not quite true any more: the free
5182 program SLiRP can emulate a PPP line if you just have a regular dial
5183 up shell account on some UNIX computer; get it via FTP (user:
5185 ftp://metalab.unc.edu/pub/Linux/system/network/serial/). Note that
5186 you don't need "PPP support" if you just want to run term (term is a
5187 program which gives you almost full Internet connectivity if you
5188 have a regular dial up shell account on some Internet connected UNIX
5190 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html (to browse
5191 the WWW, you need to have access to a machine on the Internet that
5192 has a program like lynx or netscape)).
5194 To use PPP, you need an additional program called pppd as described
5195 in Documentation/networking/ppp.txt and in the PPP-HOWTO, available
5196 from ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. If you upgrade
5197 from an older kernel, you might need to upgrade pppd as well. The
5198 PPP option enlarges your kernel by about 16 KB.
5200 This driver is also available as a module ( = code which can be
5201 inserted in and removed from the running kernel whenever you want).
5202 If you said Y to "Version information on all symbols" above, then
5203 you cannot compile the PPP driver into the kernel; you can then only
5204 compile it as a module. The module will be called ppp.o. If you want
5205 to compile it as a module, say M here and read
5206 Documentation/modules.txt as well as
5207 Documentation/networking/net-modules.txt. Note that, no matter what
5208 you do, the BSD compression code (used to compress the IP packets
5209 sent over the serial line; has to be supported at the other end as
5210 well) will always be compiled as a module; it is called bsd_comp.o
5211 and will show up in the directory modules once you have said "make
5212 modules". If unsure, say N.
5214 Wireless LAN (non-hamradio)
5216 Support for wireless LANs and everything having to do with radio,
5217 but not with amateur radio. Note that the answer to this question
5218 won't directly affect the kernel: saying N will just cause this
5219 configure script to skip all the questions about radio
5222 Some user-level drivers for scarab devices which don't require
5223 special kernel support are available via FTP (user: anonymous) from
5224 ftp://shadow.cabi.net/pub/Linux.
5226 STRIP (Metricom Starmode radio IP)
5228 Say Y if you have a Metricom radio and intend to use Starmode Radio
5229 IP. STRIP is a radio protocol developed for the MosquitoNet project
5230 (On the WWW at http://mosquitonet.stanford.edu/; to browse the WWW,
5231 you need to have access to a machine on the Internet that has a
5232 program like lynx or netscape) to send Internet traffic using
5233 Metricom radios. Metricom radios are small, battery powered,
5234 100kbit/sec packet radio transceivers, about the size and weight of
5235 a cellular telephone. (You may also have heard them called
5236 "Metricom modems" but we avoid the term "modem" because it misleads
5237 many people into thinking that you can plug a Metricom modem into a
5238 phone line and use it as a modem.)
5240 You can use STRIP on any Linux machine with a serial port, although
5241 it is obviously most useful for people with laptop computers. If you
5242 think you might get a Metricom radio in the future, there is no harm
5243 in saying Y to STRIP now, except that it makes the kernel a bit
5246 You can also compile this as a module ( = code which can be inserted
5247 in and removed from the running kernel whenever you want), say M
5248 here and read Documentation/modules.txt. The module will be called
5251 AT&T WaveLAN & DEC RoamAbout DS support
5253 The Lucent WaveLAN (formerly NCR and AT&T; or DEC RoamAbout DS) is
5254 a Radio LAN (wireless Ethernet-like Local Area Network) using the
5255 radio frequencies 900 MHz and 2.4 GHz.
5257 This driver support the ISA version of the WaveLAN card. A separate
5258 driver for the PCMCIA (PC-card) hardware is available in David
5259 Hinds' pcmcia-cs package (see the file Documentation/Changes for
5262 If you want to use an ISA WaveLAN card under Linux, say Y and read
5263 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5264 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Some more specific
5265 information is contained in Documentation/networking/wavelan.txt and
5266 in the source code drivers/net/wavelan.p.h.
5268 You will also need the wireless tools package available from
5269 ftp://ftp.inka.de/pub/comp/Linux/networking/NetTools/contrib/.
5270 Please read the man pages contained therein.
5272 This driver is also available as a module ( = code which can be
5273 inserted in and removed from the running kernel whenever you want).
5274 The module will be called wavelan.o. If you want to compile it as a
5275 module, say M here and read Documentation/modules.txt as well as
5276 Documentation/networking/net-modules.txt.
5278 Aironet Arlan 655 & IC2200 DS support
5280 Aironet makes Arlan. www.aironet.com. Uses www.Telxon.com chip, which is
5281 used on several similar cards. Driver is tested on 655 and IC2200 series.
5282 Look for http://www.ylenurme.ee/~elmer/655/ for latest information.
5283 Driver is build as two modules, arlan and arlan-proc. The later is /proc
5284 interface and not needed most of time.
5285 On some computers the card ends up in non-valid state after some time.
5286 Use a ping-reset script to clear it.
5289 LAPB over Ethernet driver
5291 This is a driver for a pseudo device (typically called /dev/lapb0)
5292 which allows you to open an LAPB point-to-point connection to some
5293 other computer on your Ethernet network. In order to do this, you
5294 need to say Y or M to the driver for your Ethernet card as well as
5295 to "LAPB Data Link Driver".
5297 If you want to compile this driver as a module ( = code which can be
5298 inserted in and removed from the running kernel whenever you want),
5299 say M here and read Documentation/modules.txt. The module will be
5300 called lapbether.o. If unsure, say N.
5304 This is a driver for sending and receiving X.25 frames over regular
5305 asynchronous serial lines such as telephone lines equipped with
5306 ordinary modems. Experts should note that this driver doesn't
5307 currently comply with the asynchronous HDLS framing protocols in
5308 CCITT recommendation X.25.
5310 If you want to compile this driver as a module ( = code which can be
5311 inserted in and removed from the running kernel whenever you want),
5312 say M here and read Documentation/modules.txt. The module will be
5313 called x25_asy.o. If unsure, say N.
5315 Shortwave radio modem driver
5317 This experimental driver is used by a package (to be released)
5318 that implements the shortwave radio protocols RTTY, Sitor (Amtor),
5319 Pactor 1 and GTOR using a standard PC sound card. If unsure,
5322 Shortwave radio modem driver support for Sound Blaster and compatible cards
5324 This option enables the hfmodem driver to use Sound Blaster and
5325 compatible cards. It requires a 16bit capable card, i.e.
5326 SB16 or better, or ESS1688 or newer.
5328 Shortwave radio modem driver support for WSS and Crystal cards
5330 This option enables the hfmodem driver to use WindowsSoundSystem
5331 compatible cards. These cards feature a codec chip from either
5332 Analog Devices (such as AD1848, AD1845) or Crystal Semiconductors
5333 (such as CS4248, CS423x).
5335 PLIP (parallel port) support
5337 PLIP (Parallel Line Internet Protocol) is used to create a
5338 reasonably fast mini network consisting of two (or, rarely, more)
5339 local machines. A PLIP link from a Linux box is a popular means to
5340 install a Linux distribution on a machine which doesn't have a CDROM
5341 drive (a minimal system has to be transferred with floppies first).
5342 The kernels on both machines need to have this PLIP option enabled
5345 The PLIP driver has two modes, mode 0 and mode 1. The parallel ports
5346 (the connectors at the computers with 25 holes) are connected with
5347 "null printer" or "Turbo Laplink" cables which can transmit 4 bits
5348 at a time (mode 0) or with special PLIP cables, to be used on
5349 bidirectional parallel ports only, which can transmit 8 bits at a
5350 time (mode 1); you can find the wiring of these cables in
5351 Documentation/networking/PLIP.txt. The cables can be up to 15m long.
5352 Mode 0 works also if one of the machines runs DOS/Windows and has
5353 some PLIP software installed, e.g. the Crynwr PLIP packet driver
5354 (http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html; to browse
5355 the WWW, you need to have access to a machine on the Internet that
5356 has a program like lynx or netscape) and winsock or NCSA's telnet.
5358 If you want to use PLIP, say Y and read the PLIP mini-HOWTO,
5359 available via FTP (user: anonymous) in
5360 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini as well as the
5361 NET-3-HOWTO in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Note that
5362 the PLIP protocol was changed and this PLIP driver won't work
5363 together with the PLIP support in Linux versions 1.0.x. This option
5364 enlarges your kernel by about 8 KB.
5366 If you want to compile this as a module ( = code which can be
5367 inserted in and removed from the running kernel whenever you want),
5368 say M here and read Documentation/modules.txt as well as
5369 Documentation/networking/net-modules.txt. The module will be called
5370 plip.o. If unsure, say Y or M, in case you buy a laptop later.
5372 EQL (serial line load balancing) support
5374 If you have two serial connections to some other computer (this
5375 usually requires two modems and two telephone lines) and you use
5376 SLIP (the protocol for sending Internet traffic over telephone
5377 lines) or PPP (a better SLIP) on them, you can make them behave like
5378 one double speed connection using this driver. Naturally, this has
5379 to be supported at the other end as well, either with a similar EQL
5380 Linux driver or with a Livingston Portmaster 2e.
5382 Say Y if you want this and read Documentation/networking/eql.txt.
5383 You may also want to read section 6.2 of the NET-3-HOWTO, available
5384 via FTP (user: anonymous) from
5385 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
5387 This driver is also available as a module ( = code which can be
5388 inserted in and removed from the running kernel whenever you want).
5389 The module will be called eql.o. If you want to compile it as a
5390 module, say M here and read Documentation/modules.txt. If unsure,
5393 Ethertap network tap
5395 If you say Y here (and have said Y to "Kernel/User network link
5396 driver", above) and create a character special file /dev/tap0 with
5397 major number 36 and minor number 16 using mknod ("man mknod"), you
5398 will be able to have a user space program read and write raw
5399 Ethernet frames from/to that special file. tap0 can be configured
5400 with ifconfig and route like any other Ethernet device but it is not
5401 connected to any physical LAN; everything written by the user to
5402 /dev/tap0 is treated by the kernel as if it had come in from a LAN
5403 to the device tap0; everything the kernel wants to send out over the
5404 device tap0 can instead be read by the user from /dev/tap0: the user
5405 mode program replaces the LAN that would be attached to an ordinary
5406 Ethernet device. Please read the file
5407 Documentation/networking/ethertap.txt for more information.
5409 This driver is also available as a module ( = code which can be
5410 inserted in and removed from the running kernel whenever you want).
5411 The module will be called ethertap.o. If you want to compile it as a
5412 module, say M here and read Documentation/modules.txt. If you don't
5413 know what to use this for, you don't need it.
5415 Sealevel Systems 4021 support
5416 CONFIG_SEALEVEL_4021
5417 This is a driver for the Sealevel Systems ACB 56 serial I/O adapter.
5419 This driver can only be compiled as a module ( = code which can be
5420 inserted in and removed from the running kernel whenever you want).
5421 If you want to do that, say M here. The module will be called
5424 Frame Relay (DLCI) support
5426 This is support for the frame relay protocol; frame relay is a fast
5427 low-cost way to connect to a remote Internet access provider or to
5428 form a private wide area network. The one physical line from your
5429 box to the local "switch" (i.e. the entry point to the frame relay
5430 network, usually at the phone company) can carry several logical
5431 point-to-point connections to other computers connected to the frame
5432 relay network. For a general explanation of the protocol, check out
5433 http://www.frforum.com/ on the WWW. (To browse the WWW, you need to
5434 have access to a machine on the Internet that has a program like
5435 lynx or netscape.) To use frame relay, you need supporting hardware
5436 (called FRAD) and certain programs from the net-tools package as
5437 explained in Documentation/networking/framerelay.txt.
5439 This driver is also available as a module ( = code which can be
5440 inserted in and removed from the running kernel whenever you want).
5441 The module will be called dlci.o. If you want to compile it as a
5442 module, say M here and read Documentation/modules.txt.
5446 This is the maximal number of logical point-to-point frame relay
5447 connections (the identifiers of which are called DCLIs) that
5448 the driver can handle. The default is probably fine.
5452 You can specify here how many logical point-to-point frame relay
5453 connections (the identifiers of which are called DCLIs) should be
5454 handled by each of your hardware frame relay access devices. Go with
5457 Sangoma S502A FRAD support
5459 Say Y here if you need a driver for the Sangoma S502A, S502E, and
5460 S508 Frame Relay Access Devices. These are multi-protocol cards, but
5461 only frame relay is supported by the driver at this time. Please
5462 read Documentation/framerelay.txt.
5464 This driver is also available as a module ( = code which can be
5465 inserted in and removed from the running kernel whenever you want).
5466 The module will be called sdla.o. If you want to compile it as a
5467 module, say M here and read Documentation/modules.txt.
5469 Acorn Econet/AUN protocols (EXPERIMENTAL)
5471 Econet is a fairly old and slow networking protocol mainly used by
5472 Acorn computers to access file and print servers. It uses native
5473 Econet network cards. AUN is an implementation of the higher level
5474 parts of Econet that runs over ordinary Ethernet connections, on
5475 top of the UDP packet protocol, which in turn runs on top of the
5476 Internet protocol IP.
5478 If you say Y here, you can choose with the next two options whether
5479 to send Econet/AUN traffic over a UDP Ethernet connection or over
5480 a native Econet network card.
5482 This driver is also available as a module ( = code which can be
5483 inserted in and removed from the running kernel whenever you want).
5484 The module will be called econet.o. If you want to compile it as a
5485 module, say M here and read Documentation/modules.txt.
5488 CONFIG_ECONET_AUNUDP
5489 Say Y here if you want to send Econet/AUN traffic over a UDP
5490 connection (UDP is a packet based protocol that runs on top of the
5491 Internet protocol IP) using an ordinary Ethernet network card.
5494 CONFIG_ECONET_NATIVE
5495 Say Y here if you have a native Econet network card installed in
5500 Wide Area Networks (WANs), such as X.25, frame relay and leased
5501 lines, are used to interconnect Local Area Networks (LANs) over vast
5502 distances with data transfer rates significantly higher than those
5503 achievable with commonly used asynchronous modem connections.
5504 Usually, a quite expensive external device called a `WAN router' is
5505 needed to connect to a WAN.
5507 As an alternative, WAN routing can be built into the Linux kernel.
5508 With relatively inexpensive WAN interface cards available on the
5509 market, a perfectly usable router can be built for less than half
5510 the price of an external router. If you have one of those cards and
5511 wish to use your Linux box as a WAN router, say Y here and also to
5512 the WAN driver for your card, below. You will then need the
5513 wan-tools package which is available via FTP (user: anonymous) from
5514 ftp://ftp.sangoma.com. Read Documentation/networking/wan-router.txt
5515 for more information.
5517 The WAN routing support is also available as a module called
5518 wanrouter.o ( = code which can be inserted in and removed from the
5519 running kernel whenever you want). If you want to compile it as a
5520 module, say M here and read Documentation/modules.txt.
5524 Fast switching (read help!)
5525 CONFIG_NET_FASTROUTE
5526 Saying Y here enables direct NIC-to-NIC (NIC = Network Interface
5527 Card) data transfers, which is fast.
5529 *** This option is NOT COMPATIBLE with several important ***
5530 *** networking options: especially CONFIG*FIREWALL. ***
5531 *** Say N here if you intend to use Linux as a firewall. ***
5533 However, it will work with all options in CONFIG_IP_ADVANCED_ROUTER
5534 section (except for CONFIG_IP_ROUTE_TOS and CONFIG_IP_ROUTE_FWMARK).
5535 At the moment, few devices support fast switching (tulip is one of
5536 them, modified 8390 can be found at
5537 ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz).
5541 Forwarding between high speed interfaces
5542 CONFIG_NET_HW_FLOWCONTROL
5543 This option enables NIC (Network Interface Card) hardware throttling
5544 during periods of extremal congestion. At the moment only a couple
5545 of device drivers support it (really only one -- tulip, modified
5546 8390 can be found at
5547 ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz).
5548 Really, this option is applicable to any machine attached to a fast enough
5549 network, and even a 10 Mb NIC is able to kill a not very slow box,
5550 such as a 120MHz Pentium.
5552 However, do not say Y here if you did not experience any serious
5555 CPU is too slow to handle full bandwidth
5557 If you suspect that your CPU is not fast enough to handle the
5558 full bandwidth of your network connection, try saying Y here. If
5561 QoS and/or fair queueing
5563 When the kernel has several packets to send out over the network
5564 devices, it has to make a decision which one to send first. This is
5565 especially important if some of the network devices are real time
5566 devices that need a certain minimum data flow rate. There are
5567 several different algorithms for how to do this "fairly"; they are
5568 called packet schedulers. If you want to stick to the default
5569 scheduling algorithm, say N here. If you want to experiment with a
5570 couple of different algorithms, say Y. You can then attach different
5571 schedulers to different network devices. Currently, this is only
5572 recommended for experts.
5574 To administer these schedulers, you'll need the user-level utilities
5575 from the package iproute2+tc at ftp://ftp.inr.ac.ru/ip-routing/
5577 If you say Y here and to "/proc filesystem" below, you will be able
5578 to read status information about priority schedulers from the file
5581 The available schedulers are listed in the following questions; you
5582 can say Y to as many as you like. If unsure, say N now.
5584 CBQ packet scheduler
5586 Say Y here if you want to use the Class-Based Queueing (CBQ) packet
5587 scheduling algorithm for some of your network devices. This
5588 algorithm classifies the waiting packets into a tree-like hierarchy
5589 of classes; the leaves of this tree are in turn scheduled by
5590 separate algorithms (called "disciplines" in this context) which you
5591 can choose below from among the various queueing algorithms. See the
5592 top of net/sched/sch_cbq.c for references about the CBQ algorithm.
5594 This code is also available as a module called sch_cbq.o ( = code
5595 which can be inserted in and removed from the running kernel
5596 whenever you want). If you want to compile it as a module, say M
5597 here and read Documentation/modules.txt.
5599 CSZ packet scheduler
5601 Say Y here if you want to use the Clark-Shenker-Zhang (CSZ) packet
5602 scheduling algorithm for some of your network devices. At the
5603 moment, this is the only algorithm that can guarantee service for
5604 real-time applications (see the top of net/sched/sch_csz.c for
5605 details and references about the algorithm).
5607 Note: this scheduler is currently broken.
5609 This code is also available as a module called sch_csz.o ( = code
5610 which can be inserted in and removed from the running kernel
5611 whenever you want). If you want to compile it as a module, say M
5612 here and read Documentation/modules.txt.
5614 The simplest PRIO pseudo scheduler
5616 Say Y here if you want to use an n-band priority queue packet
5617 "scheduler" for some of your network devices or as a leaf discipline
5618 for the CBQ scheduling algorithm.
5620 This code is also available as a module called sch_prio.o ( = code
5621 which can be inserted in and removed from the running kernel
5622 whenever you want). If you want to compile it as a module, say M
5623 here and read Documentation/modules.txt.
5627 Say Y here if you want to use the Random Early Detection (RED)
5628 packet scheduling algorithm for some of your network devices (see
5629 the top of net/sched/sch_red.c for details and references about the
5632 This code is also available as a module called sch_red.o ( = code
5633 which can be inserted in and removed from the running kernel
5634 whenever you want). If you want to compile it as a module, say M
5635 here and read Documentation/modules.txt.
5639 Say Y here if you want to use the Stochastic Fairness Queueing (SFQ)
5640 packet scheduling algorithm for some of your network devices or as a
5641 leaf discipline for the CBQ scheduling algorithm (see the top of
5642 net/sched/sch_sfq.c for details and references about the SFQ
5645 This code is also available as a module called sch_sfq.o ( = code
5646 which can be inserted in and removed from the running kernel
5647 whenever you want). If you want to compile it as a module, say M
5648 here and read Documentation/modules.txt.
5652 Say Y here if you want to use the True Link Equalizer (TLE) packet
5653 scheduling algorithm for some of your network devices or as a leaf
5654 discipline for the CBQ scheduling algorithm. This queueing
5655 discipline allows the combination of several physical devices into
5656 one virtual device. (see the top of net/sched/sch_teql.c for
5659 This code is also available as a module called sch_teql.o ( = code
5660 which can be inserted in and removed from the running kernel
5661 whenever you want). If you want to compile it as a module, say M
5662 here and read Documentation/modules.txt.
5666 Say Y here if you want to use the Simple Token Bucket Filter (TBF)
5667 packet scheduling algorithm for some of your network devices or as a
5668 leaf discipline for the CBQ scheduling algorithm (see the top of
5669 net/sched/sch_tbf.c for a description of the TBF algorithm).
5671 This code is also available as a module called sch_tbf.o ( = code
5672 which can be inserted in and removed from the running kernel
5673 whenever you want). If you want to compile it as a module, say M
5674 here and read Documentation/modules.txt.
5678 Say Y here if you want to include Quality Of Service scheduling
5679 features, which means that you will be able to request certain
5680 rate-of-flow limits for your net devices.
5682 Note that the answer to this question won't directly affect the
5683 kernel: saying N will just cause this configure script to skip all
5684 the questions about QoS support.
5687 CONFIG_NET_ESTIMATOR
5688 In order for Quality of Service scheduling to work, the current
5689 rate-of-flow for a network device has to be estimated; if you say Y
5690 here, the kernel will do just that.
5692 Packet classifier API
5694 The CBQ scheduling algorithm requires that network packets which are
5695 scheduled to be sent out over a network device be classified in some
5696 way. If you say Y here, you will get a choice of several different
5697 packet classifiers with the following questions.
5699 # Routing tables based classifier
5700 # CONFIG_NET_CLS_ROUTE
5702 # Firewall based classifier
5706 # CONFIG_NET_CLS_U32
5708 # Special RSVP classifier
5709 # CONFIG_NET_CLS_RSVP
5711 # Special RSVP classifier for IPv6
5712 # CONFIG_NET_CLS_RSVP6
5714 # Ingres traffic policing
5715 # CONFIG_NET_CLS_POLICE
5717 ### Some expert please fill these in
5720 Network code profiler
5722 If you say Y here and to "/proc filesystem support" below, some
5723 obscure and undocumented information about the network code's
5724 performance will be written to /proc/net/profile. If you don't know
5725 what it is about, you don't need it: say N.
5727 Comtrol Hostess SV-11 support
5729 This is a network card for low speed synchronous serial links, at
5730 up to 256Kbps. It supports both PPP and Cisco HDLC.
5732 At this point, the driver can only be compiled as a module.
5734 COSA/SRP sync serial boards support
5736 This is a driver for COSA and SRP synchronous serial boards. These
5737 boards allow to connect synchronous serial devices (for example
5738 base-band modems, or any other device with the X.21, V.24, V.35 or
5739 V.36 interface) to your Linux box. The cards can work as the
5740 character device, synchronous PPP network device, or the Cisco HDLC
5743 To actually use the COSA or SRP board, you will need user-space
5744 utilities for downloading the firmware to the cards and to set them
5745 up. Look at the http://www.fi.muni.cz/~kas/cosa/ for more
5746 information about the cards (including the pointer to the user-space
5747 utilities). You can also read the comment at the top of the
5748 drivers/net/cosa.c for details about the cards and the driver
5751 The driver will be compiled as a module ( = code which can be
5752 inserted in and removed from the running kernel whenever you want).
5753 The module will be called cosa.o. For general information about
5754 modules read Documentation/modules.txt.
5756 Red Creek Hardware VPN (EXPERIMENTAL)
5758 This is a driver for hardware which provides a Virtual Private
5759 Network (VPN). Say Y if you have it.
5761 This code is also available as a module called rcpci.o ( = code
5762 which can be inserted in and removed from the running kernel
5763 whenever you want). If you want to compile it as a module, say M
5764 here and read Documentation/modules.txt.
5768 Say Y to this option if your Linux box contains a WAN card and you
5769 are planning to use the box as a WAN ( = Wide Area Network) router
5770 ( = device used to interconnect local area networks over wide area
5771 communication links, such as leased lines or public data networks,
5772 e.g. X.25 or frame relay) and you will be offered a list of drivers
5773 for WAN cards currently available. For more information, read
5774 Documentation/networking/wan-router.txt.
5776 Note that the answer to this question won't directly affect the
5777 kernel: saying N will just cause this configure script to skip all
5778 the questions about WAN card drivers. If unsure, say N.
5780 Sangoma WANPIPE(tm) multiprotocol cards
5781 CONFIG_VENDOR_SANGOMA
5782 WANPIPE from Sangoma Technologies Inc. (http://www.sangoma.com; to
5783 browse the WWW, you need to have access to a machine on the Internet
5784 that has a program like lynx or netscape) is a family of intelligent
5785 multiprotocol WAN adapters with data transfer rates up to T1 (1.544
5786 Mbps). They are also known as Synchronous Data Link Adapters (SDLA)
5787 and designated S502E(A), S503 or S508. These cards support the X.25,
5788 Frame Relay, and PPP protocols. If you have one or more of these
5789 cards, say Y to this option; you may then also want to read the file
5790 Documentation/networking/wanpipe.txt. The next questions will ask
5791 you about the protocols you want the driver to support.
5793 The driver will be compiled as a module ( = code which can be
5794 inserted in and removed from the running kernel whenever you want).
5795 The module will be called wanpipe.o. For general information about
5796 modules read Documentation/modules.txt.
5798 Maximum number of cards
5799 CONFIG_WANPIPE_CARDS
5800 Enter number of WANPIPE adapters installed in your machine. The
5801 driver can support up to 8 cards. You may enter more than you
5802 actually have if you plan to add more cards in the future without
5803 re-compiling the driver, but remember that in this case you'll waste
5804 some kernel memory (about 1K per card).
5806 WANPIPE X.25 support
5808 Say Y to this option if you are planning to connect a WANPIPE card
5809 to an X.25 network. You should then also have said Y to "CCITT X.25
5810 Packet Layer" and "LAPB Data Link Driver", above. If you say N, the
5811 X.25 support will not be included in the driver (saves about 16 KB
5814 WANPIPE Frame Relay support
5816 Say Y to this option if you are planning to connect a WANPIPE card
5817 to a frame relay network. You should then also have said Y to "Frame
5818 Relay (DLCI) support", above. If you say N, the frame relay
5819 support will not be included in the driver (saves about 16 KB of
5824 Say Y to this option if you are planning to connect a WANPIPE card
5825 to a leased line using Point-to-Point protocol (PPP). You should
5826 then also have said Y to "PPP (point-to-point) support", above. If
5827 you say N, the PPP support will not be included in the driver (saves
5828 about 16 KB of kernel memory).
5830 Cyclom 2X(tm) multiprotocol cards
5831 CONFIG_CYCLADES_SYNC
5832 Cyclom 2X from Cyclades Corporation (http://www.cyclades.com and
5833 http://www.cyclades.com.br; to browse the WWW, you need to have
5834 access to a machine on the Internet that has a program like lynx or
5835 netscape) is an intelligent multiprotocol WAN adapter with data
5836 transfer rates up to 512 Kbps). These cards support the X.25 and SNA
5837 related protocols. If you have one or more of these cards, say Y to
5838 this option. The next questions will ask you about the protocols you
5839 want the driver to support (for now only X.25 is supported).
5841 While no documentation is available at this time please grab the
5842 wanconfig tarball in http://www.conectiva.com.br/~acme/cycsyn-devel
5843 (with minor changes to make it compile with the current wanrouter
5844 include files; efforts are being made to use the original package
5845 available at ftp://ftp.sangoma.com).
5847 Feel free to contact me or the cycsyn-devel mailing list at
5848 acme@conectiva.com.br and cycsyn-devel@bazar.conectiva.com.br for
5849 aditional details, I hope to have documentation available as soon
5852 The driver will be compiled as a module ( = code which can be
5853 inserted in and removed from the running kernel whenever you want).
5854 The module will be called cyclomx.o. For general information about
5855 modules read Documentation/modules.txt.
5857 Cyclom 2X X.25 support
5859 Say Y to this option if you are planning to connect a Cyclom 2X card
5861 If you say N, the X.25 support will not be included in the driver
5862 (saves about 11 KB of kernel memory).
5864 Ethernet (10 or 100Mbit)
5866 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
5867 type of Local Area Network (LAN) in universities and companies.
5869 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
5870 coaxial cable, linking computers in a chain), 10BASE-T or twisted
5871 pair (10 Mbps over twisted pair cable, linking computers to central
5872 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
5873 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
5874 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
5875 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
5876 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
5877 Ethernet (1 Gbps over optical fiber or short copper links).
5879 If your Linux machine will be connected to an Ethernet and you have
5880 an Ethernet network interface card (NIC) installed in your computer,
5881 say Y here and read the Ethernet-HOWTO, available via FTP (user:
5882 anonymous) from ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. You will
5883 then also have to say Y to the driver for your particular NIC.
5885 Note that the answer to this question won't directly affect the
5886 kernel: saying N will just cause this configure script to skip all
5887 the questions about Ethernet network cards. If unsure, say N.
5889 Sun LANCE Ethernet support
5891 This is support for lance Ethernet cards on Sun workstations such as
5892 the SPARCstation IPC (any SPARC with a network interface 'le0' under
5895 This driver is also available as a module ( = code which can be
5896 inserted in and removed from the running kernel whenever you want).
5897 The module will be called lance.o. If you want to compile it as a
5898 module, say M here and read Documentation/modules.txt.
5900 Sun Intel Ethernet support
5902 This is support for the Intel Ethernet cards on some Sun
5903 workstations (all those with a network interface 'ie0' under SunOS).
5905 Western Digital/SMC cards
5906 CONFIG_NET_VENDOR_SMC
5907 If you have a network (Ethernet) card belonging to this class, say Y
5908 and read the Ethernet-HOWTO, available via FTP (user: anonymous) in
5909 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
5911 Note that the answer to this question doesn't directly affect the
5912 kernel: saying N will just cause this configure script to skip all
5913 the questions about Western Digital cards. If you say Y, you will be
5914 asked for your specific card in the following questions.
5918 If you have a network (Ethernet) card of this type, say Y and read
5919 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5920 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
5922 This driver is also available as a module ( = code which can be
5923 inserted in and removed from the running kernel whenever you want).
5924 The module will be called wd.o. If you want to compile it as a
5925 module, say M here and read Documentation/modules.txt as well as
5926 Documentation/networking/net-modules.txt.
5928 SMC Ultra MCA support
5930 If you have a network (Ethernet) card of this type and are running
5931 an MCA based system (PS/2), say Y and read
5932 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5933 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
5935 This driver is also available as a module ( = code which can be
5936 inserted in and removed from the running kernel whenever you want).
5937 The module will be called smc-mca.o. If you want to compile it as a
5938 module, say M here and read Documentation/modules.txt as well as
5939 Documentation/networking/net-modules.txt.
5943 If you have a network (Ethernet) card of this type, say Y and read
5944 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5945 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
5947 Important: There have been many reports that, with some motherboards
5948 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
5949 such as some BusLogic models) causes corruption problems with many
5950 operating systems. The Linux smc-ultra driver has a work-around for
5951 this but keep it in mind if you have such a SCSI card and have
5954 This driver is also available as a module ( = code which can be
5955 inserted in and removed from the running kernel whenever you want).
5956 The module will be called smc-ultra.o. If you want to compile it as
5957 a module, say M here and read Documentation/modules.txt as well as
5958 Documentation/networking/net-modules.txt.
5960 SMC Ultra32 EISA support
5962 If you have a network (Ethernet) card of this type, say Y and read
5963 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5964 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
5966 This driver is also available as a module ( = code which can be
5967 inserted in and removed from the running kernel whenever you want).
5968 The module will be called smc-ultra32.o. If you want to compile it
5969 as a module, say M here and read Documentation/modules.txt as well
5970 as Documentation/networking/net-modules.txt.
5974 This is support for the SMC9xxx based Ethernet cards. Choose this
5975 option if you have a DELL laptop with the docking station, or
5976 another SMC9192/9194 based chipset. Say Y if you want it compiled
5977 into the kernel, and read the file
5978 Documentation/networking/smc9.txt and the Ethernet-HOWTO, available
5979 via FTP (user: anonymous) in
5980 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
5982 This driver is also available as a module ( = code which can be
5983 inserted in and removed from the running kernel whenever you
5984 want). The module will be called smc9194.o. If you want to compile
5985 it as a module, say M here and read Documentation/modules.txt as
5986 well as Documentation/networking/net-modules.txt.
5990 This driver is for NE2000 compatible PCI cards. It will not work
5991 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
5992 support" below). If you have a PCI NE2000 network (Ethernet) card,
5993 say Y and read the Ethernet-HOWTO, available via FTP (user:
5994 anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
5996 This driver is also available as a module ( = code which can be
5997 inserted in and removed from the running kernel whenever you want).
5998 The module will be called ne2k-pci.o. If you want to compile it as a
5999 module, say M here and read Documentation/modules.txt as well as
6000 Documentation/networking/net-modules.txt.
6002 Racal-Interlan (Micom) NI cards
6003 CONFIG_NET_VENDOR_RACAL
6004 If you have a network (Ethernet) card belonging to this class, such
6005 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
6006 available via FTP (user: anonymous) in
6007 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6009 Note that the answer to this question doesn't directly affect the
6010 kernel: saying N will just cause this configure script to skip all
6011 the questions about NI cards. If you say Y, you will be asked for
6012 your specific card in the following questions.
6016 If you have a network (Ethernet) card of this type, say Y and read
6017 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6018 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Note that this is still
6021 This driver is also available as a module ( = code which can be
6022 inserted in and removed from the running kernel whenever you want).
6023 The module will be called ni5010.o. If you want to compile it as a
6024 module, say M here and read Documentation/modules.txt as well as
6025 Documentation/networking/net-modules.txt.
6029 If you have a network (Ethernet) card of this type, say Y and read
6030 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6031 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6033 This driver is also available as a module ( = code which can be
6034 inserted in and removed from the running kernel whenever you want).
6035 The module will be called ni52.o. If you want to compile it as a
6036 module, say M here and read Documentation/modules.txt as well as
6037 Documentation/networking/net-modules.txt.
6041 If you have a network (Ethernet) card of this type, say Y and read
6042 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6043 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6045 This driver is also available as a module ( = code which can be
6046 inserted in and removed from the running kernel whenever you want).
6047 The module will be called ni65.o. If you want to compile it as a
6048 module, say M here and read Documentation/modules.txt as well as
6049 Documentation/networking/net-modules.txt.
6051 RealTek 8129/8139 (not 8019/8029!) support
6053 This is a driver for the Fast Ethernet PCI network cards based on
6054 the RTL8129 and RTL8139 chips. If you have one of those, say Y and
6055 read the Ethernet-HOWTO, available via FTP (user: anonymous) in
6056 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6058 If you want to compile this driver as a module ( = code which can be
6059 inserted in and removed from the running kernel whenever you want),
6060 say M here and read Documentation/modules.txt. This is recommended.
6061 The module will be called rtl8139.o.
6063 Packet Engines Yellowfin Gigabit-NIC support
6065 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
6066 adapter. This adapter is used by the Beowulf Linux cluster project.
6067 See http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html for
6068 more information about this driver in particular and Beowulf in
6069 general (to browse the WWW, you need to have access to a machine on
6070 the Internet that has a program like lynx or netscape).
6072 If you want to compile this driver as a module ( = code which can be
6073 inserted in and removed from the running kernel whenever you want),
6074 say M here and read Documentation/modules.txt. This is recommended.
6075 The module will be called yellowfin.o.
6077 Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support
6079 Say Y here if you have an Alteon AceNIC or 3Com 3C985 PCI Gigabit
6080 Ethernet adapter. The driver allows for using the Jumbo Frame
6081 option (9000 bytes/frame) however it requires that your switches
6082 can handle this as well. To enable Jumbo Frames, add `mtu 9000' to
6085 If you want to compile this driver as a module ( = code which can be
6086 inserted in and removed from the running kernel whenever you want),
6087 say M here and read Documentation/modules.txt. This is recommended.
6088 The module will be called acenic.o.
6090 AMD LANCE and PCnet (AT1500 and NE2100) support
6092 If you have a network (Ethernet) card of this type, say Y and read
6093 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6094 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Some LinkSys cards are
6097 If you want to compile this driver as a module ( = code which can be
6098 inserted in and removed from the running kernel whenever you want),
6099 say M here and read Documentation/modules.txt. This is recommended.
6100 The module will be called lance.o.
6103 CONFIG_NET_VENDOR_3COM
6104 If you have a network (Ethernet) card belonging to this class, say Y
6105 and read the Ethernet-HOWTO, available via FTP (user: anonymous) in
6106 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6108 Note that the answer to this question doesn't directly affect the
6109 kernel: saying N will just cause this configure script to skip all
6110 the questions about 3COM cards. If you say Y, you will be asked for
6111 your specific card in the following questions.
6115 If you have a network (Ethernet) card of this type, say Y and read
6116 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6117 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Also, consider buying a
6118 new card, since the 3c501 is slow, broken, and obsolete: you will
6119 have problems. Some people suggest to ping ("man ping") a nearby
6120 machine every minute ("man cron") when using this card.
6122 This driver is also available as a module ( = code which can be
6123 inserted in and removed from the running kernel whenever you want).
6124 The module will be called 3c501.o. If you want to compile it as a
6125 module, say M here and read Documentation/modules.txt as well as
6126 Documentation/networking/net-modules.txt.
6130 If you have a network (Ethernet) card of this type, say Y and read
6131 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6132 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6134 This driver is also available as a module ( = code which can be
6135 inserted in and removed from the running kernel whenever you want).
6136 The module will be called 3c503.o. If you want to compile it as a
6137 module, say M here and read Documentation/modules.txt as well as
6138 Documentation/networking/net-modules.txt.
6142 Information about this network (Ethernet) card can be found in
6143 Documentation/networking/3c505.txt. If you have a card of this type,
6144 say Y and read the Ethernet-HOWTO, available via FTP (user:
6145 anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6147 If you want to compile this as a module ( = code which can be
6148 inserted in and removed from the running kernel whenever you want),
6149 say M here and read Documentation/modules.txt as well as
6150 Documentation/networking/net-modules.txt. The module will be called
6155 If you have a network (Ethernet) card of this type, say Y and read
6156 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6157 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6159 This driver is also available as a module ( = code which can be
6160 inserted in and removed from the running kernel whenever you want).
6161 The module will be called 3c507.o. If you want to compile it as a
6162 module, say M here and read Documentation/modules.txt as well as
6163 Documentation/networking/net-modules.txt.
6167 If you have a network (Ethernet) card of this type, say Y and read
6168 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6169 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6171 This driver is also available as a module ( = code which can be
6172 inserted in and removed from the running kernel whenever you want).
6173 The module will be called 3c523.o. If you want to compile it as a
6174 module, say M here and read Documentation/modules.txt as well as
6175 Documentation/networking/net-modules.txt.
6179 If you have a network (Ethernet) card of this type, say Y and read
6180 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6181 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6183 This driver is also available as a module ( = code which can be
6184 inserted in and removed from the running kernel whenever you want).
6185 The module will be called 3c527.o. If you want to compile it as a
6186 module, say M here and read Documentation/modules.txt as well as
6187 Documentation/networking/net-modules.txt.
6191 If you have a network (Ethernet) card belonging to the 3Com
6192 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
6193 via FTP (user: anonymous) in
6194 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6196 If your card is not working you may need to use the DOS
6197 setup disk to disable Plug & Play mode, and to select the default
6200 If you want to compile this as a module ( = code which can be
6201 inserted in and removed from the running kernel whenever you want),
6202 say M here and read Documentation/modules.txt as well as
6203 Documentation/networking/net-modules.txt. The module will be called
6206 3c590 series (592/595/597) "Vortex" support
6208 If you have a 3Com "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597)
6209 or "Boomerang" series (EtherLink XL 3c900 or 3c905) network
6210 (Ethernet) card, say Y and read the Ethernet-HOWTO, available via
6211 FTP (user: anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6212 More specific information is in Documentation/networking/vortex.txt
6213 and in the comments at the beginning of drivers/net/3c59x.c.
6215 If you want to compile this as a module ( = code which can be
6216 inserted in and removed from the running kernel whenever you want),
6217 say M here and read Documentation/modules.txt as well as
6218 Documentation/networking/net-modules.txt.
6222 If your network (Ethernet) card hasn't been mentioned yet and its
6223 bus system (that's the way the cards talks to the other components
6224 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
6225 Make sure you know the name of your card. Read the Ethernet-HOWTO,
6226 available via FTP (user: anonymous) in
6227 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. If unsure, say Y.
6229 Note that the answer to this question doesn't directly affect the
6230 kernel: saying N will just cause this configure script to skip all
6231 the remaining ISA network card questions. If you say Y, you will be
6232 asked for your specific card in the following questions.
6234 Generic ARCnet support
6236 If you have a network card of this type, say Y and check out the
6237 (arguably) beautiful poetry in Documentation/networking/arcnet.txt.
6239 You need both this driver, and the driver for the particular ARCnet
6240 chipset of your card. If you don't know, then it's probably a
6241 COM90xx type card, so say Y (or M) to "ARCnet COM90xx chipset
6244 You might also want to have a look at the Ethernet-HOWTO, available
6245 via FTP (user: anonymous) in
6246 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO (even though ARCnet is
6247 not really Ethernet).
6249 This driver is also available as a module ( = code which can be
6250 inserted in and removed from the running kernel whenever you want).
6251 The module will be called arcnet.o. If you want to compile it as a
6252 module, say M here and read Documentation/modules.txt as well as
6253 Documentation/networking/net-modules.txt.
6255 Enable arc0e (ARCnet "ether-encap" packet format)
6257 This allows you to use "Ethernet encapsulation" with your ARCnet
6258 card via the virtual arc0e device. You only need arc0e if you want
6259 to talk to nonstandard ARCnet software, specifically,
6260 DOS/Windows-style "NDIS" drivers. You do not need to say Y here to
6261 communicate with industry-standard RFC1201 implementations, like the
6262 arcether.com packet driver or most DOS/Windows ODI drivers. RFC1201
6263 is included automatically as the arc0 device. Please read the
6264 ARCnet documentation in Documentation/networking/arcnet.txt for more
6265 information about using arc0e and arc0s.
6267 Enable arc0s (ARCnet RFC1051 packet format)
6269 This allows you to use RFC1051 with your ARCnet card via the virtual
6270 arc0s device. You only need arc0s if you want to talk to ARCnet
6271 software complying with the "old" standard, specifically, the DOS
6272 arcnet.com packet driver, Amigas running AmiTCP, and some variants
6273 of NetBSD. You do not need to say Y here to communicate with
6274 industry-standard RFC1201 implementations, like the arcether.com
6275 packet driver or most DOS/Windows ODI drivers. RFC1201 is included
6276 automatically as the arc0 device. Please read the ARCnet
6277 documentation in Documentation/networking/arcnet.txt for more
6278 information about using arc0e and arc0s.
6280 ARCnet COM90xx (normal) chipset driver
6281 CONFIG_ARCNET_COM90xx
6282 This is the chipset driver for the standard COM90xx cards. If you
6283 have always used the old ARCnet driver without knowing what type of
6284 card you had, this is probably the one for you.
6286 This driver is also available as a module ( = code which can be
6287 inserted in and removed from the running kernel whenever you want).
6288 The module will be called com90xx.o. If you want to compile it as a
6289 module, say M here and read Documentation/modules.txt as well as
6290 Documentation/networking/net-modules.txt.
6292 ARCnet COM90xx (IO mapped) chipset driver
6293 CONFIG_ARCNET_COM90xxIO
6294 This is the chipset driver for the COM90xx cards, using them in
6295 IO-mapped mode instead of memory-mapped mode. This is slower than
6296 the normal driver. Only use it if your card doesn't support shared
6299 This driver is also available as a module ( = code which can be
6300 inserted in and removed from the running kernel whenever you want).
6301 The module will be called com90io.o. If you want to compile it as a
6302 module, say M here and read Documentation/modules.txt as well as
6303 Documentation/networking/net-modules.txt.
6305 ARCnet COM90xx (RIM I) chipset driver
6307 This is yet another chipset driver for the COM90xx cards, but this
6308 time only using memory-mapped mode, and no IO ports at all. This
6309 driver is completely untested, so if you have one of these cards,
6310 please mail David.Woodhouse@mvhi.com, especially if it works!
6312 This driver is also available as a module ( = code which can be
6313 inserted in and removed from the running kernel whenever you
6314 want). The module will be called arc-rimi.o. If you want to compile
6315 it as a module, say M here and read Documentation/modules.txt as
6316 well as Documentation/networking/net-modules.txt.
6318 ARCnet COM20020 chipset driver
6319 CONFIG_ARCNET_COM20020
6320 This is the driver for the new COM20020 chipset. It supports such
6321 things as promiscuous mode, so packet sniffing is possible, and
6322 extra diagnostic information.
6324 This driver is also available as a module ( = code which can be
6325 inserted in and removed from the running kernel whenever you want).
6326 The module will be called com20020.o. If you want to compile it as a
6327 module, say M here and read Documentation/modules.txt as well as
6328 Documentation/networking/net-modules.txt.
6330 Cabletron E21xx support
6332 If you have a network (Ethernet) card of this type, say Y and read
6333 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6334 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6336 This driver is also available as a module ( = code which can be
6337 inserted in and removed from the running kernel whenever you want).
6338 The module will be called e2100.o. If you want to compile it as a
6339 module, say M here and read Documentation/modules.txt as well as
6340 Documentation/networking/net-modules.txt.
6344 Support for CS89x0 chipset based Ethernet cards. If you have a
6345 network (Ethernet) card of this type, say Y and read the
6346 Ethernet-HOWTO, available via FTP (user: anonymous) in
6347 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO as well as
6348 Documentation/networking/cs89x0.txt.
6350 If you want to compile this as a module ( = code which can be
6351 inserted in and removed from the running kernel whenever you want),
6352 say M here and read Documentation/modules.txt as well as
6353 Documentation/networking/net-modules.txt. The module will be called
6358 If you have a network (Ethernet) card of this type, say Y and read
6359 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6360 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO as well as
6361 drivers/net/depca.c.
6363 If you want to compile this as a module ( = code which can be
6364 inserted in and removed from the running kernel whenever you want),
6365 say M here and read Documentation/modules.txt as well as
6366 Documentation/networking/net-modules.txt. The module will be called
6369 EtherWorks 3 support
6371 This driver supports the DE203, DE204 and DE205 network (Ethernet)
6372 cards. If this is for you, say Y and read
6373 Documentation/networking/ewrk3.txt in the kernel source as well as
6374 the Ethernet-HOWTO, available via FTP (user: anonymous) from
6375 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6377 If you want to compile this as a module ( = code which can be
6378 inserted in and removed from the running kernel whenever you want),
6379 say M here and read Documentation/modules.txt as well as
6380 Documentation/networking/net-modules.txt. The module will be called
6385 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
6386 is for you, read the Ethernet-HOWTO, available via FTP (user:
6387 anonymous) from ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6391 If you have a network (Ethernet) card of this type, say Y and read
6392 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6393 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6395 This driver is also available as a module ( = code which can be
6396 inserted in and removed from the running kernel whenever you want).
6397 If you want to compile it as a module, say M here and read
6398 Documentation/modules.txt as well as
6399 Documentation/networking/net-modules.txt. The module will be called
6402 FMV-181/182/183/184 support
6404 If you have a Fujitsu FMV-181/182/183/184 network (Ethernet) card,
6405 say Y and read the Ethernet-HOWTO, available via FTP (user:
6406 anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6408 If you use an FMV-183 or FMV-184 and it is not working, you may need
6409 to disable Plug & Play mode of the card.
6411 This driver is also available as a module ( = code which can be
6412 inserted in and removed from the running kernel whenever you want).
6413 The module will be called fmv18x.o. If you want to compile it as a
6414 module, say M here and read Documentation/modules.txt as well as
6415 Documentation/networking/net-modules.txt.
6417 EtherExpress PRO support
6419 If you have a network (Ethernet) card of this type, say Y. Note
6420 however that the EtherExpress PRO/100 Ethernet card has its own
6421 separate driver. Please read the Ethernet-HOWTO, available via FTP
6422 (user: anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6424 This driver is also available as a module ( = code which can be
6425 inserted in and removed from the running kernel whenever you want).
6426 The module will be called eepro.o. If you want to compile it as a
6427 module, say M here and read Documentation/modules.txt as well as
6428 Documentation/networking/net-modules.txt.
6430 EtherExpress support
6432 If you have an EtherExpress16 network (Ethernet) card, say Y and
6433 read the Ethernet-HOWTO, available via FTP (user: anonymous) in
6434 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Note that the Intel
6435 EtherExpress16 card used to be regarded as a very poor choice
6436 because the driver was very unreliable. We now have a new driver
6437 that should do better.
6439 If you want to compile this driver as a module ( = code which can be
6440 inserted in and removed from the running kernel whenever you want),
6441 say M here and read Documentation/modules.txt as well as
6442 Documentation/networking/net-modules.txt. The module will be called
6445 HP PCLAN+ (27247B and 27252A) support
6447 If you have a network (Ethernet) card of this type, say Y and read
6448 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6449 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6451 This driver is also available as a module ( = code which can be
6452 inserted in and removed from the running kernel whenever you want).
6453 The module will be called hp-plus.o. If you want to compile it as a
6454 module, say M here and read Documentation/modules.txt as well as
6455 Documentation/networking/net-modules.txt.
6457 HP PCLAN (27245 and other 27xxx series) support
6459 If you have a network (Ethernet) card of this type, say Y and read
6460 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6461 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6463 This driver is also available as a module ( = code which can be
6464 inserted in and removed from the running kernel whenever you want).
6465 The module will be called hp.o. If you want to compile it as a
6466 module, say M here and read Documentation/modules.txt as well as
6467 Documentation/networking/net-modules.txt.
6469 HP 10/100VG PCLAN (ISA, EISA, PCI) support
6471 If you have a network (Ethernet) card of this type, say Y and read
6472 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6473 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6475 If you want to compile this as a module ( = code which can be
6476 inserted in and removed from the running kernel whenever you want),
6477 say M here and read Documentation/modules.txt as well as
6478 Documentation/networking/net-modules.txt. The module will be called
6481 NE2000/NE1000 support
6483 If you have a network (Ethernet) card of this type, say Y and read
6484 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6485 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Many Ethernet cards
6486 without a specific driver are compatible with NE2000.
6488 If you have a PCI NE2000 card however, say N here and Y to "PCI
6489 NE2000 support", above. If you have a NE2000 card and are running on
6490 an MCA system (a bus system used on some IBM PS/2 computers and
6491 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
6494 This driver is also available as a module ( = code which can be
6495 inserted in and removed from the running kernel whenever you want).
6496 The module will be called ne.o. If you want to compile it as a
6497 module, say M here and read Documentation/modules.txt as well as
6498 Documentation/networking/net-modules.txt.
6502 If you have a network (Ethernet) card of this type, say Y and read
6503 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6504 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6506 NE/2 (ne2000 MCA version) support
6508 If you have a network (Ethernet) card of this type, say Y and read
6509 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6510 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6512 This driver is also available as a module ( = code which can be
6513 inserted in and removed from the running kernel whenever you want).
6514 The module will be called ne2.o. If you want to compile it as a
6515 module, say M here and read Documentation/modules.txt as well as
6516 Documentation/networking/net-modules.txt.
6520 This are Micro Channel ethernet adapters. You need to set CONFIG_MCA
6521 to use this driver. It's both available as an in-kernel driver and
6522 as a module ( = code which can be inserted in and removed from the
6523 running kernel whenever you want). If you want to compile it as a module,
6524 say M here and read Documentation/modules.txt as well as
6525 Documentation/networking/net-modules.txt. If you plan to use more than
6526 one network card under linux, read the Multiple-Ethernet-mini-HOWTO,
6527 available from sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. Supported
6528 cards are the SKnet Junior MC2 and the SKnet MC2(+). Distinguishing
6529 both cards is done automatically. Note that using multiple boards
6530 of different type hasn't been tested with this driver.
6532 EISA, VLB, PCI and on board controllers
6534 This is another class of network cards which attach directly to the
6535 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
6536 available via FTP (user: anonymous) from
6537 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6539 Note that the answer to this question doesn't directly affect the
6540 kernel: saying N will just cause this configure script to skip all
6541 the questions about this class of network cards. If you say Y, you
6542 will be asked for your specific card in the following questions. If
6543 you are unsure, say Y.
6545 AMD PCnet32 (VLB and PCI) support
6547 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
6548 answer Y here and read the Ethernet-HOWTO, available via FTP (user:
6549 anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6551 This driver is also available as a module ( = code which can be
6552 inserted in and removed from the running kernel whenever you want).
6553 The module will be called pcnet32.o. If you want to compile it as a
6554 module, say M here and read Documentation/modules.txt as well as
6555 Documentation/networking/net-modules.txt.
6557 Ansel Communications EISA 3200 support
6559 If you have a network (Ethernet) card of this type, say Y and read
6560 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6561 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6563 This driver is also available as a module ( = code which can be
6564 inserted in and removed from the running kernel whenever you want).
6565 The module will be called ac3200.o. If you want to compile it as a
6566 module, say M here and read Documentation/modules.txt as well as
6567 Documentation/networking/net-modules.txt.
6569 Mylex EISA LNE390A/LNE390B support
6571 If you have a network (Ethernet) card of this type, say Y and read
6572 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6573 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6575 This driver is also available as a module ( = code which can be
6576 inserted in and removed from the running kernel whenever you want).
6577 The module will be called lne390.o. If you want to compile it as a
6578 module, say M here and read Documentation/modules.txt as well as
6579 Documentation/networking/net-modules.txt.
6581 Novell/Eagle/Microdyne NE3210 EISA support
6583 If you have a network (Ethernet) card of this type, say Y and read
6584 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6585 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Note that this driver
6586 will NOT WORK for NE3200 cards as they are completely different.
6588 This driver is also available as a module ( = code which can be
6589 inserted in and removed from the running kernel whenever you want).
6590 The module will be called ne3210.o. If you want to compile it as a
6591 module, say M here and read Documentation/modules.txt as well as
6592 Documentation/networking/net-modules.txt.
6594 Apricot Xen-II on board Ethernet
6596 If you have a network (Ethernet) controller of this type, say Y and
6597 read the Ethernet-HOWTO, available via FTP (user: anonymous) in
6598 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6600 If you want to compile this as a module ( = code which can be
6601 inserted in and removed from the running kernel whenever you want),
6602 say M here and read Documentation/modules.txt as well as
6603 Documentation/networking/net-modules.txt. The module will be called
6606 Generic DECchip & DIGITAL EtherWORKS PCI/EISA
6608 This is support for the DIGITAL series of PCI/EISA Ethernet cards.
6609 These include the DE425, DE434, DE435, DE450 and DE500 models. If
6610 you have a network card of this type, say Y and read the
6611 Ethernet-HOWTO, available via FTP (user: anonymous) in
6612 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. More specific
6613 information is contained in Documentation/networking/de4x5.txt.
6615 This driver is also available as a module ( = code which can be
6616 inserted in and removed from the running kernel whenever you want).
6617 The module will be called de4x5.o. If you want to compile it as a
6618 module, say M here and read Documentation/modules.txt as well as
6619 Documentation/networking/net-modules.txt.
6621 DECchip Tulip (dc21x4x) PCI support
6623 This driver is developed for the SMC EtherPower series Ethernet
6624 cards and also works with cards based on the DECchip
6625 21040/21041/21140 (Tulip series) chips. Some LinkSys PCI cards are
6626 of this type. (If your card is NOT SMC EtherPower 10/100 PCI
6627 (smc9332dst), you can also try the driver for "Generic DECchip"
6628 cards, above. However, most people with a network card of this type
6629 will say Y here.) Do read the Ethernet-HOWTO, available via FTP
6630 (user: anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6631 More specific information is contained in
6632 Documentation/networking/tulip.txt.
6634 This driver is also available as a module ( = code which can be
6635 inserted in and removed from the running kernel whenever you want).
6636 The module will be called tulip.o. If you want to compile it as a
6637 module, say M here and read Documentation/modules.txt as well as
6638 Documentation/networking/net-modules.txt.
6640 Digi Intl. RightSwitch support
6642 This is support for the Digi International RightSwitch series of
6643 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
6644 models. If you have a network card of this type, say Y and read the
6645 Ethernet-HOWTO, available via FTP (user: anonymous) in
6646 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. More specific
6647 information is contained in Documentation/networking/dgrs.txt.
6649 This driver is also available as a module ( = code which can be
6650 inserted in and removed from the running kernel whenever you want).
6651 The module will be called dgrs.o. If you want to compile it as a
6652 module, say M here and read Documentation/modules.txt as well as
6653 Documentation/networking/net-modules.txt.
6655 EtherExpress PRO/100 support
6656 CONFIG_EEXPRESS_PRO100
6657 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
6658 card, say Y and read the Ethernet-HOWTO, available via FTP (user:
6659 anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6661 This driver is also available as a module ( = code which can be
6662 inserted in and removed from the running kernel whenever you want).
6663 The module will be called eepro100.o. If you want to compile it as a
6664 module, say M here and read Documentation/modules.txt as well as
6665 Documentation/networking/net-modules.txt.
6667 ICL EtherTeam 16i/32 support
6669 If you have a network (Ethernet) card of this type, say Y and read
6670 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6671 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6673 This driver is also available as a module ( = code which can be
6674 inserted in and removed from the running kernel whenever you want).
6675 The module will be called eth16i.o. If you want to compile it as a
6676 module, say M here and read Documentation/modules.txt as well as
6677 Documentation/networking/net-modules.txt.
6679 TI ThunderLAN support (EXPERIMENTAL)
6681 If you have a PCI Ethernet network card based on the ThunderLAN chip
6682 which is supported by this driver, say Y and read the
6683 Ethernet-HOWTO, available via FTP (user: anonymous) in
6684 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6686 Devices currently supported by this driver are Compaq Netelligent,
6687 Compaq NetFlex and Olicom cards. Please read the file
6688 Documentation/networking/tlan.txt for more details.
6690 This driver is also available as a module ( = code which can be
6691 inserted in and removed from the running kernel whenever you want).
6692 The module will be called tlan.o. If you want to compile it as a
6693 module, say M here and read Documentation/modules.txt as well as
6694 Documentation/networking/net-modules.txt.
6696 Please email feedback to james.banks@caldera.com.
6700 If you have a VIA "rhine" based network card (Rhine-I (3043) or
6701 Rhine-2 (VT86c100A)), say Y here.
6703 This driver is also available as a module ( = code which can be
6704 inserted in and removed from the running kernel whenever you want).
6705 The module will be called via-rhine.o. If you want to compile it as
6706 a module, say M here and read Documentation/modules.txt as well as
6707 Documentation/networking/net-modules.txt.
6709 Racal-Interlan EISA ES3210 support
6711 If you have a network (Ethernet) card of this type, say Y and read
6712 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6713 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6715 This driver is also available as a module ( = code which can be
6716 inserted in and removed from the running kernel whenever you want).
6717 The module will be called es3210.o. If you want to compile it as a
6718 module, say M here and read Documentation/modules.txt as well as
6719 Documentation/networking/net-modules.txt.
6721 SMC EtherPower II (EXPERIMENTAL)
6723 If you have an SMC EtherPower II 9432 PCI Ethernet network card
6724 which is based on the SMC83c170, say Y and read the Ethernet-HOWTO,
6725 available via FTP (user: anonymous) in
6726 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6728 This driver is also available as a module ( = code which can be
6729 inserted in and removed from the running kernel whenever you want).
6730 The module will be called epic100.o. If you want to compile it as a
6731 module, say M here and read Documentation/modules.txt as well as
6732 Documentation/networking/net-modules.txt.
6734 SGI Seeq ethernet controller support
6736 Say Y here if you have an Seeq based Ethernet network card. This is
6737 used in many Silicon Graphics machines.
6739 Zenith Z-Note support
6741 The Zenith Z-Note notebook computer has a built-in network
6742 (Ethernet) card, and this is the Linux driver for it. Note that the
6743 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
6744 by this driver. Read the Ethernet-HOWTO, available via FTP (user:
6745 anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6747 Pocket and portable adapters
6749 Cute little network (Ethernet) devices which attach to the parallel
6750 port ("pocket adapters"), commonly used with laptops. If you have
6751 one of those, say Y and read the Ethernet-HOWTO, available via FTP
6752 (user: anonymous) from ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6754 If you want to plug a network (or some other) card into the PCMCIA
6755 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
6756 credit card size extension cards used by all modern laptops), you
6757 need the pcmcia-cs package (location contained in the file
6758 Documentation/Changes) and you can say N here.
6760 Laptop users should read the Linux Laptop home page at
6761 http://www.cs.utexas.edu/users/kharker/linux-laptop/ (to browse the
6762 WWW, you need to have access to a machine on the Internet that has a
6763 program like lynx or netscape).
6765 Note that the answer to this question doesn't directly affect the
6766 kernel: saying N will just cause this configure script to skip all
6767 the questions about this class of network devices. If you say Y, you
6768 will be asked for your specific device in the following questions.
6770 AT-LAN-TEC/RealTek pocket adapter support
6772 This is a network (Ethernet) device which attaches to your parallel
6773 port. Read drivers/net/atp.c as well as the Ethernet-HOWTO,
6774 available via FTP (user: anonymous) from
6775 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO if you want to use this.
6776 If you intend to use this driver, you should have said N to the
6777 Parallel Printer support, because the two drivers don't like each
6780 D-Link DE600 pocket adapter support
6782 This is a network (Ethernet) device which attaches to your parallel
6783 port. Read Documentation/networking/DLINK.txt as well as the
6784 Ethernet-HOWTO, available via FTP (user: anonymous) from
6785 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO if you want to use this.
6786 It is possible to have several devices share a single parallel port
6787 and it is safe to compile the corresponding drivers into the kernel.
6789 If you want to compile this driver as a module however ( = code
6790 which can be inserted in and removed from the running kernel
6791 whenever you want), say M here and read Documentation/modules.txt.
6792 The module will be called de600.o.
6794 D-Link DE620 pocket adapter support
6796 This is a network (Ethernet) device which attaches to your parallel
6797 port. Read Documentation/networking/DLINK.txt as well as the
6798 Ethernet-HOWTO, available via FTP (user: anonymous) from
6799 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO if you want to use this.
6800 It is possible to have several devices share a single parallel port
6801 and it is safe to compile the corresponding drivers into the kernel.
6803 If you want to compile this driver as a module however ( = code
6804 which can be inserted in and removed from the running kernel
6805 whenever you want), say M here and read Documentation/modules.txt.
6806 The module will be called de620.o.
6808 Token Ring driver support
6810 Token Ring is IBM's way of communication on a local network; the
6811 rest of the world uses Ethernet. To participate on a Token Ring
6812 network, you need a special Token ring network card. If you are
6813 connected to such a Token Ring network and want to use your Token
6814 Ring card under Linux, say Y here and to the driver for your
6815 particular card below and read the Token-Ring mini-HOWTO, available
6816 via FTP (user:anonymous) from
6817 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Most people can say N
6820 IBM Tropic chipset based adapter support
6822 This is support for all IBM Token Ring cards that don't use DMA. If
6823 you have such a beast, say Y and read the Token-Ring mini-HOWTO,
6824 available via FTP (user:anonymous) from
6825 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6827 Warning: this driver will almost definitely fail if more than one
6828 active Token Ring card is present.
6830 This driver is also available as a module ( = code which can be
6831 inserted in and removed from the running kernel whenever you want).
6832 The module will be called ibmtr.o. If you want to compile it as a
6833 module, say M here and read Documentation/modules.txt.
6835 IBM Olympic chipset PCI adapter support
6837 This is support for all non-Lanstreamer IBM PCI Token Ring Cards.
6838 Specifically this is all IBM PCI, PCI Wake On Lan, PCI II, PCI II
6839 Wake On Lan, and PCI 100/16/4 adapters.
6841 If you have such an adapter, say Y and read the Token-Ring mini-HOWTO,
6842 available via FTP (user:anonymous) from
6843 ftp://metalab.unc/edu/pub/Linux/docs/HOWTO.
6845 This driver is also available as a module ( = code which can be
6846 inserted in and removed from the running kernel whenever you want).
6847 The module will will be called olympic.o. If you want to compile it as a
6848 module, say M here and read Documentation/modules.txt.
6850 Also read the linux/Documentation/networking/olympic.txt or check the
6851 Linux Token Ring Project site for the latest information at
6852 http://www.linuxtr.net
6854 SysKonnect adapter support
6856 This is support for all SysKonnect Token Ring cards, specifically
6857 SysKonnect TR4/16(+) ISA (SK-4190), SysKonnect TR4/16(+) PCI
6858 (SK-4590), SysKonnect TR4/16 PCI (SK-4591) adapters.
6860 If you have such an adapter and would like to use it, say Y or M and
6861 read the Token-Ring mini-HOWTO, available via FTP (user: anonymous)
6862 from ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6864 Also read the file linux/Documentation/networking/sktr.txt or check
6865 the Linux-SNA WWW site for the latest information at
6866 http://samba.anu.edu.au/linux-sna/documents/drivers/SysKonnect/
6868 Traffic Shaper (EXPERIMENTAL)
6870 The traffic shaper is a virtual network device that allows you to
6871 limit the rate of outgoing data flow over some other network
6872 device. See Documentation/networking/shaper.txt for more
6873 information. To set up and configure shaper devices, you need the
6874 shapecfg program, available via FTP (user: anonymous) from
6875 ftp://shadow.cabi.net/pub/Linux in the shaper package.
6877 This driver is also available as a module ( = code which can be
6878 inserted in and removed from the running kernel whenever you want).
6879 The module will be called shaper.o. If you want to compile it as a
6880 module, say M here and read Documentation/modules.txt. If unsure,
6885 Fiber Distributed Data Interface is a high speed local area network
6886 design; essentially a replacement for high speed Ethernet. FDDI can
6887 run over copper or fiber. If you are connected to such a network and
6888 want a driver for the FDDI card in your computer, say Y here (and
6889 then also Y to the driver for your FDDI card, below). Most people
6892 Digital DEFEA and DEFPA adapter support
6894 This is support for the DIGITAL series of EISA (DEFEA) and PCI
6895 (DEFPA) controllers which can connect you to a local FDDI network.
6897 HIgh Performance Parallel Interface support (EXPERIMENTAL)
6899 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
6900 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
6901 can run over copper (25m) or fiber (300m on multi-mode or 10km on
6902 single-mode). HIPPI networks are commonly used for clusters and to
6903 connect to super computers. If you are connected to a HIPPI network
6904 and have a HIPPI network card in your computer that you want to use
6905 under Linux, say Y here (you must also remember to enable the driver
6906 for your HIPPI card below). Most people will say N here.
6908 CERN HIPPI PCI adapter support
6910 Say Y here if this is your PCI HIPPI network card.
6912 This driver is also available as a module ( = code which can be
6913 inserted in and removed from the running kernel whenever you want).
6914 The module will be called cern_hippi.o. If you want to compile it as
6915 a module, say M here and read Documentation/modules.txt. If unsure,
6918 Essential RoadRunner HIPPI PCI adapter support
6920 Say Y here if this is your PCI HIPPI network card.
6922 This driver is also available as a module ( = code which can be
6923 inserted in and removed from the running kernel whenever you want).
6924 The module will be called rrunner.o. If you want to compile it as
6925 a module, say M here and read Documentation/modules.txt. If unsure,
6928 Use large TX/RX rings
6929 CONFIG_ROADRUNNER_LARGE_RINGS
6930 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
6931 of additional memory to allow for fastest operation, both for
6932 transmitting and receiving. This memory cannot be used by any other
6933 kernel code or by user space programs. Say Y here only if you have
6938 If you have an Acorn system with one of these (AKA25) network cards,
6939 you should say Y to this option if you wish to use it with Linux.
6941 Acorn/ANT Ether3 card
6943 If you have an Acorn system with one of these network cards, you
6944 should say Y to this option if you wish to use it with Linux.
6948 If you have an Acorn system with one of these network cards, you
6949 should say Y to this option if you wish to use it with Linux.
6951 EBSA-110 Ethernet interface
6952 CONFIG_ARM_AM79C961A
6953 If you wish to compile a kernel for the EBSA-110, then you should
6954 always answer Y to this.
6956 Support CDROM drives that are not SCSI or IDE/ATAPI
6957 CONFIG_CD_NO_IDESCSI
6958 If you have a CDROM drive that is neither SCSI nor IDE/ATAPI, say Y
6959 here, otherwise N. Read the CDROM-HOWTO, available via FTP (user:
6960 anonymous) from ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6962 Note that the answer to this question doesn't directly affect the
6963 kernel: saying N will just cause this configure script to skip all
6964 the questions about these CDROM drives. If you are unsure what you
6965 have, say Y and find out whether you have one of the following
6968 For each of these drivers, a file Documentation/cdrom/<driver_name>
6969 exists. Especially in cases where you do not know exactly which kind
6970 of drive you have you should read there. Most of these drivers use a
6971 file drivers/cdrom/<driver_name>.h where you can define your
6972 interface parameters and switch some internal goodies.
6974 All these CDROM drivers are also usable as a module ( = code which
6975 can be inserted in and removed from the running kernel whenever you
6976 want). If you want to compile them as module, say M instead of Y and
6977 read Documentation/modules.txt.
6979 If you want to use any of these CDROM drivers, you also have to
6980 answer Y or M to "ISO 9660 CDROM filesystem support" below (this
6981 answer will get "defaulted" for you if you enable any of the Linux
6984 Sony CDU31A/CDU33A CDROM support
6986 These CDROM drives have a spring-pop-out caddyless drawer, and a
6987 rectangular green LED centered beneath it. NOTE: these CDROM drives
6988 will not be auto detected by the kernel at boot time; you have to
6989 provide the interface address as an option to the kernel at boot
6990 time as described in Documentation/cdrom/cdu31a or fill in your
6991 parameters into drivers/cdrom/cdu31a.c. Try "man bootparam" or
6992 see the documentation of your boot loader (lilo or loadlin) about
6993 how to pass options to the kernel. The lilo procedure is also
6994 explained in the SCSI-HOWTO.
6996 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
6997 filesystem support" below, because that's the filesystem used on
7000 This driver is also available as a module ( = code which can be
7001 inserted in and removed from the running kernel whenever you want).
7002 The module will be called cdu31a.o. If you want to compile it as a
7003 module, say M here and read Documentation/modules.txt.
7005 Standard Mitsumi [no XA/Multisession] CDROM support
7007 This is the older of the two drivers for the older Mitsumi models
7008 LU-005, FX-001 and FX-001D. This is not the right driver for the
7009 FX-001DE and the triple or quad speed models (all these are
7010 IDE/ATAPI models). Please also the file Documentation/cdrom/mcd.
7012 With the old LU-005 model, the whole drive chassis slides out for cd
7013 insertion. The FX-xxx models use a motorized tray type mechanism.
7014 Note that this driver does not support XA or MultiSession CDs
7015 (PhotoCDs). There is a new driver (next question) which can do
7016 this. If you want that one, say N here.
7018 If the driver doesn't work out of the box, you might want to have a
7019 look at drivers/cdrom/mcd.h.
7021 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7022 filesystem support" below, because that's the filesystem used on
7025 This driver is also available as a module ( = code which can be
7026 inserted in and removed from the running kernel whenever you want).
7027 The module will be called mcd.o. If you want to compile it as a
7028 module, say M here and read Documentation/modules.txt.
7030 IRQ channel for Mitsumi CD-ROM
7032 This allows you to specify the default value of the IRQ used by the
7033 driver. This setting can be overridden by passing the "mcd="
7034 parameter to the kernel at boot time (or at module load time if you
7035 said M to "Standard Mitsumi CDROM support").
7037 I/O base address for Mitsumi CD-ROM
7039 This allows you to specify the default value of the I/O base address
7040 used by the driver. This setting can be overridden by passing the
7041 "mcd=" parameter to the kernel at boot time (or at module load time
7042 if you said M to "Standard Mitsumi CDROM support").
7044 Mitsumi [XA/MultiSession] support
7046 Use this driver if you want to be able to read XA or MultiSession
7047 CDs (PhotoCDs) as well as ordinary CDs with your Mitsumi LU-005,
7048 FX-001 or FX-001D CDROM drive. In addition, this driver uses much
7049 less kernel memory than the old one, if that is a concern. This
7050 driver is able to support more than one drive, but each drive needs
7051 a separate interface card. Please read the file
7052 Documentation/cdrom/mcdx.
7054 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7055 filesystem support" below, because that's the filesystem used on
7058 This driver is also available as a module ( = code which can be
7059 inserted in and removed from the running kernel whenever you want).
7060 The module will be called mcdx.o. If you want to compile it as a
7061 module, say M here and read Documentation/modules.txt.
7063 Matsushita/Panasonic/Creative, Longshine, TEAC CDROM support
7065 This driver supports most of the drives which use the Panasonic or
7066 Sound Blaster interface. Please read the file
7067 Documentation/cdrom/sbpcd.
7069 The Matsushita CR-521, CR-522, CR-523, CR-562, CR-563 drives
7070 (sometimes labeled "Creative"), the Creative Labs CD200, the
7071 Longshine LCS-7260, the "IBM External ISA CDROM" (in fact a CR-56x
7072 model), the TEAC CD-55A fall under this category. Some other
7073 "electrically compatible" drives (Vertos, Genoa, some Funai models)
7074 are currently not supported; for the Sanyo H94A drive currently a
7075 separate driver (asked later) is responsible. Most drives have a
7076 uniquely shaped faceplate, with a caddyless motorized drawer, but
7077 without external brand markings. The older CR-52x drives have a
7078 caddy and manual loading/eject, but still no external markings. The
7079 driver is able to do an extended auto-probing for interface
7080 addresses and drive types; this can help to find facts in cases you
7081 are not sure, but can consume some time during the boot process if
7082 none of the supported drives gets found. Once your drive got found,
7083 you should enter the reported parameters into drivers/cdrom/sbpcd.h
7084 and set "DISTRIBUTION 0" there.
7086 This driver can support up to four CDROM controller cards, and each
7087 card can support up to four CDROM drives; if you say Y here, you
7088 will be asked how many controller cards you have. If compiled as a
7089 module, only one controller card (but with up to four drives) is
7092 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7093 filesystem support" below, because that's the filesystem used on
7096 This driver is also available as a module ( = code which can be
7097 inserted in and removed from the running kernel whenever you want).
7098 The module will be called sbpcd.o. If you want to compile it as a
7099 module, say M here and read Documentation/modules.txt.
7101 Matsushita/Panasonic, ... second CDROM controller support
7103 Say Y here only if you have two CDROM controller cards of this type
7104 (usually only if you have more than four drives). You should enter
7105 the parameters for the second, third and fourth interface card into
7106 linux/include/linux/sbpcd.h before compiling the new kernel. Read
7107 the file Documentation/cdrom/sbpcd.
7109 Aztech/Orchid/Okano/Wearnes/TXC/CyDROM CDROM support
7111 This is your driver if you have an Aztech CDA268-01A, Orchid
7112 CD-3110, Okano or Wearnes CDD110, Conrad TXC, or CyCDROM CR520 or
7113 CR540 CDROM drive. This driver -- just like all these CDROM drivers
7114 -- is NOT for CDROM drives with IDE/ATAPI interfaces, such as Aztech
7115 CDA269-031SE. Please read the file Documentation/cdrom/aztcd.
7117 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7118 filesystem support" below, because that's the filesystem used on
7121 This driver is also available as a module ( = code which can be
7122 inserted in and removed from the running kernel whenever you want).
7123 The module will be called aztcd.o. If you want to compile it as a
7124 module, say M here and read Documentation/modules.txt.
7126 Sony CDU535 CDROM support
7128 This is the driver for the older Sony CDU-535 and CDU-531 CDROM
7129 drives. Please read the file Documentation/cdrom/sonycd535.
7131 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7132 filesystem support" below, because that's the filesystem used on
7135 This driver is also available as a module ( = code which can be
7136 inserted in and removed from the running kernel whenever you want).
7137 The module will be called sonycd535.o. If you want to compile it as
7138 a module, say M here and read Documentation/modules.txt.
7140 Goldstar R420 CDROM support
7142 If this is your CDROM drive, say Y here. As described in the file
7143 linux/Documentation/cdrom/gscd, you might have to change a setting
7144 in the file linux/drivers/cdrom/gscd.h before compiling the
7145 kernel. Please read the file Documentation/cdrom/gscd.
7147 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7148 filesystem support" below, because that's the filesystem used on
7151 This driver is also available as a module ( = code which can be
7152 inserted in and removed from the running kernel whenever you want).
7153 The module will be called gscd.o. If you want to compile it as a
7154 module, say M here and read Documentation/modules.txt.
7156 Philips/LMS CM206 CDROM support
7158 If you have a Philips/LMS CDROM drive cm206 in combination with a
7159 cm260 host adapter card, say Y here. Please also read the file
7160 Documentation/cdrom/cm206.
7162 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7163 filesystem support" below, because that's the filesystem used on
7166 This driver is also available as a module ( = code which can be
7167 inserted in and removed from the running kernel whenever you want).
7168 The module will be called cm206.o. If you want to compile it as a
7169 module, say M here and read Documentation/modules.txt.
7171 Optics Storage DOLPHIN 8000AT CDROM support
7173 This is the driver for the 'DOLPHIN' drive with a 34-pin Sony
7174 compatible interface. It also works with the Lasermate CR328A. If
7175 you have one of those, say Y. This driver does not work for the
7176 Optics Storage 8001 drive; use the IDE-ATAPI CDROM driver for that
7177 one. Please read the file Documentation/cdrom/optcd.
7179 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7180 filesystem support" below, because that's the filesystem used on
7183 This driver is also available as a module ( = code which can be
7184 inserted in and removed from the running kernel whenever you want).
7185 The module will be called optcd.o. If you want to compile it as a
7186 module, say M here and read Documentation/modules.txt.
7188 Sanyo CDR-H94A CDROM support
7190 If this is your CDROM drive, say Y here and read the file
7191 Documentation/cdrom/sjcd. You should then also say Y or M to
7192 "ISO 9660 CDROM filesystem support" below, because that's the
7193 filesystem used on CDROMs.
7195 This driver is also available as a module ( = code which can be
7196 inserted in and removed from the running kernel whenever you want).
7197 The module will be called sjcd.o. If you want to compile it as a
7198 module, say M here and read Documentation/modules.txt.
7200 Soft configurable cdrom interface card support
7202 If you want to include boot-time initialization of any cdrom
7203 interface card that is software configurable, say Y here. Currently
7204 only the ISP16/MAD16/Mozart sound cards with built-in cdrom
7205 interfaces are supported.
7207 Note that the answer to this question doesn't directly affect the
7208 kernel: saying N will just cause this configure script to skip all
7209 the questions about these CDROM drives.
7211 ISP16/MAD16/Mozart soft configurable cdrom interface support
7213 These are sound cards with built-in cdrom interfaces using the OPTi
7214 82C928 or 82C929 chips. Say Y here to have them detected and
7215 possibly configured at boot time. In addition, You'll have to say Y
7216 to a driver for the particular cdrom drive you have attached to the
7217 card. Read Documentation/cdrom/isp16 for details.
7219 This driver is also available as a module ( = code which can be
7220 inserted in and removed from the running kernel whenever you want).
7221 The module will be called isp16.o. If you want to compile it as a
7222 module, say M here and read Documentation/modules.txt.
7226 If you say Y here, you will be able to set per user limits for disk
7227 usage (also called disk quotas). Currently, it works only for the
7228 ext2 filesystem. You need additional software in order to use quota
7229 support; for details, read the Quota mini-HOWTO, available via FTP
7230 (user: anonymous) in
7231 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini. Probably the quota
7232 support is only useful for multi user systems. If unsure, say N.
7234 Acorn's ADFS filesystem support (read only) (EXPERIMENTAL)
7236 The Advanced Disk File System is the filesystem used on floppy and
7237 hard disks by Acorn Systems. Currently in development, as a read-
7238 only driver for hard disks. These should be the first partition
7239 (eg. /dev/[sh]d?1) on each of your drives. If unsure, say N.
7243 Minix is a simple operating system used in many classes about OS's.
7244 The minix filesystem (method to organize files on a hard disk
7245 partition or a floppy disk) was the original filesystem for Linux,
7246 but has been superseded by the second extended filesystem ext2fs.
7247 You don't want to use the minix filesystem on your hard disk because
7248 of certain built-in restrictions, but it is sometimes found on older
7249 Linux floppy disks. This option will enlarge your kernel by about
7250 25 kB. If unsure, say N.
7252 If you want to compile this as a module ( = code which can be
7253 inserted in and removed from the running kernel whenever you want),
7254 say M here and read Documentation/modules.txt. The module will be
7255 called minix.o. Note that the filesystem of your root partition (the
7256 one containing the directory /) cannot be compiled as a module.
7258 Second extended fs support
7260 This is the de facto standard Linux filesystem (method to organize
7261 files on a storage device) for hard disks.
7263 You want to say Y here, unless you intend to use Linux exclusively
7264 from inside a DOS partition using the umsdos filesystem. The
7265 advantage of the latter is that you can get away without
7266 repartitioning your hard drive (which often implies backing
7267 everything up and restoring afterwards); the disadvantage is that
7268 Linux becomes susceptible to DOS viruses and that umsdos is somewhat
7269 slower than ext2fs. Even if you want to run Linux in this fashion,
7270 it might be a good idea to have ext2fs around: it enables you to
7271 read more floppy disks and facilitates the transition to a *real*
7272 Linux partition later. Another (rare) case which doesn't require
7273 ext2fs is a diskless Linux box which mounts all files over the
7274 network using NFS (in this case it's sufficient to say Y to "NFS
7275 filesystem support" below). Saying Y here will enlarge your kernel
7278 The Ext2fs-Undeletion mini-HOWTO, available via FTP (user:
7279 anonymous) from ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini,
7280 gives information about how to retrieve deleted files on ext2fs
7283 To change the behavior of ext2 filesystems, you can use the tune2fs
7284 utility ("man tune2fs"). To modify attributes of files and
7285 directories on ext2 filesystems, use chattr ("man chattr").
7287 Ext2fs partitions can be read from within DOS using the ext2tool
7288 command line tool package (available via FTP (user: anonymous) from
7289 ftp://metalab.unc.edu/pub/Linux/system/filesystems/ext2) and from
7290 within Windows NT using the ext2nt command line tool package from
7291 ftp://metalab.unc.edu/pub/Linux/utils/dos. Explore2fs is a graphical
7292 explorer for ext2fs partitions which runs on Windows 95 and Windows
7293 NT and includes experimental write support; it is available from
7294 http://jnewbigin-pc.it.swin.edu.au/Linux/Explore2fs.htm.
7296 If you want to compile this filesystem as a module ( = code which
7297 can be inserted in and removed from the running kernel whenever you
7298 want), say M here and read Documentation/modules.txt. The module
7299 will be called ext2.o. Be aware however that the filesystem of your
7300 root partition (the one containing the directory /) cannot be
7301 compiled as a module, and so this could be dangerous. Most everyone
7302 wants to say Y here.
7304 ISO 9660 CDROM filesystem support
7306 This is the standard filesystem used on CDROMs. It was previously
7307 known as "High Sierra Filesystem" and is called "hsfs" on other Unix
7308 systems. The so-called Rock-Ridge extensions which allow for long
7309 Unix filenames and symbolic links are also supported by this driver.
7310 If you have a CDROM drive and want to do more with it than just
7311 listen to audio CDs and watch its LEDs, say Y (and read
7312 Documentation/filesystems/isofs.txt and the CDROM-HOWTO, available
7313 via FTP (user: anonymous) from
7314 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO), thereby enlarging your
7315 kernel by about 27 kB; otherwise say N.
7317 If you want to compile this as a module ( = code which can be
7318 inserted in and removed from the running kernel whenever you want),
7319 say M here and read Documentation/modules.txt. The module will be
7322 Microsoft Joliet cdrom extensions
7324 Joliet is a Microsoft extension for the ISO 9660 CDROM filesystem
7325 which allows for long filenames in unicode format (unicode is the
7326 new 16 bit character code, successor to ASCII, which encodes the
7327 characters of almost all languages of the world; see
7328 http://www.unicode.org for more information; to browse the WWW, you
7329 need to have access to a machine on the Internet that has a program
7330 like lynx or netscape). Say Y here if you want to be able to read
7331 Joliet CDROMs under Linux.
7335 If you want to use one of the FAT-based filesystems (the MS-DOS,
7336 VFAT (Windows 95) and UMSDOS (used to run Linux on top of an
7337 ordinary DOS partition) filesystems), then you must say Y or M here
7338 to include FAT support. You will then be able to mount partitions or
7339 diskettes with FAT-based filesystems and transparently access the
7340 files on them, i.e. MSDOS files will look and behave just like all
7343 This FAT support is not a filesystem in itself, it only provides the
7344 foundation for the other filesystems. You will have to say Y or M to
7345 at least one of "msdos fs support" or "vfat fs support" in order to
7348 Another way to read and write MSDOS floppies and hard drive
7349 partitions from within Linux (but not transparently) is with the
7350 mtools ("man mtools") program suite. This doesn't require the FAT
7353 It is now also becoming possible to read and write compressed FAT
7354 filesystems; read Documentation/filesystems/fat_cvf.txt for details.
7356 The FAT support will enlarge your kernel by about 24 kB. If unsure,
7359 If you want to compile this as a module however ( = code which can
7360 be inserted in and removed from the running kernel whenever you
7361 want), say M here and read Documentation/modules.txt. The module
7362 will be called fat.o. Note that if you compile the FAT support as a
7363 module, you cannot compile any of the FAT-based filesystems into the
7364 kernel -- they will have to be modules as well. The filesystem of
7365 your root partition (the one containing the directory /) cannot be a
7366 module, so don't say M here if you intend to use UMSDOS as your root
7371 This allows you to mount MSDOS partitions of your hard drive (unless
7372 they are compressed; to access compressed MSDOS partitions under
7373 Linux, you can either use the DOS emulator DOSEMU, described in the
7374 DOSEMU-HOWTO, available via FTP (user: anonymous) at
7375 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO, or try dmsdosfs in
7376 ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs. If you
7377 intend to use dosemu with a non-compressed MSDOS partition, say Y
7378 here) and MSDOS floppies. This means that file access becomes
7379 transparent, i.e. the MSDOS files look and behave just like all
7382 If you want to use umsdos, the Unix-like filesystem on top of DOS,
7383 which allows you to run Linux from within a DOS partition without
7384 repartitioning, you'll have to say Y or M here.
7386 If you have Windows 95 or Windows NT installed on your MSDOS
7387 partitions, you should use the VFAT filesystem (say Y to "vfat fs
7388 support" below), or you will not be able to see the long filenames
7389 generated by Windows 95 / Windows NT.
7391 This option will enlarge your kernel by about 7 kB. If unsure,
7392 answer Y. This will only work if you said Y to "fat fs support" as
7393 well. If you want to compile this as a module however ( = code which
7394 can be inserted in and removed from the running kernel whenever you
7395 want), say M here and read Documentation/modules.txt. The module
7396 will be called msdos.o.
7400 This option provides support for normal Windows filesystems with
7401 long filenames. That includes non-compressed FAT-based filesystems
7402 used by Windows 95, Windows 98, Windows NT 4.0, and mtools.
7404 You cannot use the VFAT filesystem for your Linux root partition
7405 (the one containing the directory /); use UMSDOS instead if you
7406 want to run Linux from within a DOS partition (i.e. say Y to
7407 "umsdos: Unix like fs on top of std MSDOS fs", below).
7409 The VFAT support enlarges your kernel by about 10 kB and it only
7410 works if you said Y to the "fat fs support" above. Please read the
7411 file Documentation/filesystems/vfat.txt for details. If unsure,
7414 If you want to compile this as a module ( = code which can be
7415 inserted in and removed from the running kernel whenever you want),
7416 say M here and read Documentation/modules.txt. The module will be
7419 umsdos: Unix like fs on top of std MSDOS fs
7421 Say Y here if you want to run Linux from within an existing DOS
7422 partition of your hard drive. The advantage of this is that you can
7423 get away without repartitioning your hard drive (which often implies
7424 backing everything up and restoring afterwards) and hence you're
7425 able to quickly try out Linux or show it to your friends; the
7426 disadvantage is that Linux becomes susceptible to DOS viruses and
7427 that UMSDOS is somewhat slower than ext2fs. Another use of UMSDOS
7428 is to write files with long unix filenames to MSDOS floppies; it
7429 also allows Unix-style softlinks and owner/permissions of files on
7430 MSDOS floppies. You will need a program called umssync in order to
7431 make use of umsdos; read Documentation/filesystems/umsdos.txt.
7433 This option enlarges your kernel by about 25 kB and it only works if
7434 you said Y to both "fat fs support" and "msdos fs support" above. If
7435 you want to compile this as a module ( = code which can be inserted
7436 in and removed from the running kernel whenever you want), say M
7437 here and read Documentation/modules.txt. The module will be called
7438 umsdos.o. Note that the filesystem of your root partition (the one
7439 containing the directory /) cannot be a module, so saying M could be
7440 dangerous. If unsure, say N.
7442 /proc filesystem support
7444 This is a virtual filesystem providing information about the status
7445 of the system. "Virtual" means that it doesn't take up any space on
7446 your hard disk: the files are created on the fly by the kernel when
7447 you try to access them. Also, you cannot read the files with older
7448 version of the program less: you need to use more or cat.
7450 It's totally cool; for example, "cat /proc/interrupts" gives
7451 information about what the different IRQs are used for at the moment
7452 (there is a small number of Interrupt ReQuest lines in your computer
7453 that are used by the attached devices to gain the CPU's attention --
7454 often a source of trouble if two devices are mistakenly configured
7455 to use the same IRQ).
7457 The /proc filesystem is explained in the file
7458 Documentation/proc.txt, in the Kernel Hacker's Guide at
7459 http://www.redhat.com:8080/HyperNews/get/khg.html on the WWW (to
7460 browse the WWW, you need to have access to a machine on the Internet
7461 that has a program like lynx or netscape), and also on the proc(8)
7462 manpage ("man 8 proc").
7464 This option will enlarge your kernel by about 18 KB. Several
7465 programs depend on this, so everyone should say Y here.
7467 NFS filesystem support
7469 If you are connected to some other (usually local) Unix computer
7470 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
7471 on that computer (the NFS server) using the Network File Sharing
7472 protocol, say Y. "Mounting files" means that the client can access
7473 the files with usual UNIX commands as if they were sitting on the
7474 client's hard disk. For this to work, the server must run the
7475 programs nfsd and mountd (but does not need to have NFS filesystem
7476 support enabled in its kernel). NFS is explained in the Network
7477 Administrator's Guide, available via FTP (user: anonymous) in
7478 ftp://metalab.unc.edu/pub/Linux/docs/LDP, on its man page: "man
7479 nfs", and in the NFS-HOWTO.
7481 A superior but less widely used alternative to NFS is provided by
7482 the Coda filesystem; see "Coda filesystem support" below.
7484 If you say Y here, you should have said Y to TCP/IP networking also.
7485 This option would enlarge your kernel by about 27 kB.
7487 This filesystem is also available as a module ( = code which can be
7488 inserted in and removed from the running kernel whenever you want).
7489 The module is called nfs.o. If you want to compile it as a module,
7490 say M here and read Documentation/modules.txt.
7492 If you are configuring a diskless machine which will mount its root
7493 filesystem over NFS at boot time, say Y here and to "IP: kernel
7494 level autoconfiguration" above and to "Root file system on NFS"
7495 below. You cannot compile this driver as a module in this case.
7496 There are two packages designed for booting diskless machines over
7497 the net: netboot and etherboot, both available via FTP from
7498 ftp://metalab.unc.edu/pub/Linux/system/boot/ethernet/ .
7500 If you don't know what all this is about, say N.
7502 Root file system on NFS
7504 If you want your Linux box to mount its whole root filesystem (the
7505 one containing the directory /) from some other computer over the
7506 net via NFS (presumably because your box doesn't have a hard disk),
7507 say Y. Read Documentation/nfsroot.txt for details. It is likely that
7508 in this case, you also want to say Y to "IP: kernel level
7509 autoconfiguration" so that your box can discover its network address
7512 Most people say N here.
7516 If you want your Linux box to act as a NFS *server*, so that other
7517 computers on your local network which support NFS can access certain
7518 directories on your box transparently, you have two options: you can
7519 use the self-contained user space program nfsd, in which case you
7520 should say N here, or you can say Y and use this new experimental
7521 kernel based NFS server. The advantage of the kernel based solution
7522 is that it is faster; it might not be completely stable yet, though.
7524 In either case, you will need support software; the respective
7525 locations are given in the file Documentation/Changes in the NFS
7528 Please read the NFS-HOWTO, available via FTP (user: anonymous) from
7529 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
7531 The NFS server is also available as a module ( = code which can be
7532 inserted in and removed from the running kernel whenever you want).
7533 The module is called nfsd.o. If you want to compile it as a module,
7534 say M here and read Documentation/modules.txt. If unsure, say N.
7536 Emulate Sun NFS daemon
7538 If you would like for the server to allow clients to access
7539 directories that are mount points on the local filesystem (this is
7540 how nfsd behaves on Sun systems), say yes here. If unsure, say N.
7542 OS/2 HPFS filesystem support (read/write)
7544 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
7545 is the filesystem used for organizing files on OS/2 hard disk
7546 partitions. Say Y if you want to be able to read and write files
7547 on an OS/2 HPFS partition of your hard drive. OS/2 floppies however
7548 are in regular MSDOS format, so you don't need this option in order
7549 to be able to read them. Read Documentation/filesystems/hpfs.txt.
7551 Write support is new and experimental. I don't think it's so
7552 "experimental" that it corrupts disks. (but you know: "There's no
7553 warranty") There are many checks and filesystem is remounted read-only
7554 if any inconsistency found. I use it quite long time and it works.
7556 This driver may not be able to write to HPFS386 disks on Warp server.
7557 HPFS386 on Warp client seems to work ok. If some unknown HPFS386
7558 structures are deteced, they are not destroyed and filesystem is
7559 remounted read-only.
7561 This filesystem is also available as a module ( = code which can be
7562 inserted in and removed from the running kernel whenever you want).
7563 The module is called hpfs.o. If you want to compile it as a module,
7564 say M here and read Documentation/modules.txt. If unsure, say N.
7566 Windows NT NTFS support (read only)
7568 NTFS is the file system of Microsoft Windows NT. Say Y if you want
7569 to get read access to files on NTFS partitions of your hard drive.
7570 The Linux NTFS driver supports most of the mount options of the VFAT
7571 driver, see Documentation/filesystems/ntfs.txt. Saying Y here will
7572 give you read-only access to NTFS partitions.
7574 This code is also available as a module ( = code which can be
7575 inserted in and removed from the running kernel whenever you want).
7576 The module will be called ntfs.o. If you want to compile it as a
7577 module, say M here and read Documentation/modules.txt.
7579 NTFS read-write support (experimental)
7581 If you say Y here, you will (hopefully) be able to write to NTFS
7582 file systems as well as read from them. The read-write support
7583 in NTFS is far from being complete and is not well tested. If you
7584 enable this, back up your NTFS volume first since it may get
7589 System V and Coherent filesystem support
7591 SCO, Xenix and Coherent are commercial Unix systems for Intel
7592 machines. Saying Y here would allow you to read to and write from
7593 their floppies and hard disk partitions.
7595 If you have floppies or hard disk partitions like that, it is likely
7596 that they contain binaries from those other Unix systems; in order
7597 to run these binaries, you will want to install iBCS2 (Intel Binary
7598 Compatibility Standard is a kernel module which lets you run SCO,
7599 Xenix, Wyse, UnixWare, Dell Unix and System V programs under Linux
7600 and is often needed to run commercial software that's only available
7601 for those systems. It's available via FTP (user: anonymous) from
7602 ftp://tsx-11.mit.edu/pub/linux/BETA).
7604 If you only intend to mount files from some other Unix over the
7605 network using NFS, you don't need the System V filesystem support
7606 (but you need NFS filesystem support obviously).
7608 Note that this option is generally not needed for floppies, since a
7609 good portable way to transport files and directories between unixes
7610 (and even other operating systems) is given by the tar program ("man
7611 tar" or preferably "info tar"). Note also that this option has
7612 nothing whatsoever to do with the option "System V IPC". Read about
7613 the System V filesystem in Documentation/filesystems/sysv-fs.txt.
7614 Saying Y here will enlarge your kernel by about 34 KB.
7616 If you want to compile this as a module ( = code which can be
7617 inserted in and removed from the running kernel whenever you want),
7618 say M here and read Documentation/modules.txt. The module will be
7621 If you haven't heard about all of this before, it's safe to say N.
7623 Amiga FFS filesystem support
7625 The Fast File System (FFS) is the common filesystem used on hard
7626 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
7627 if you want to be able to read and write files from and to an Amiga
7628 FFS partition on your hard drive. Amiga floppies however cannot be
7629 read with this driver due to an incompatibility of the floppy
7630 controller used in an Amiga and the standard floppy controller in
7631 PCs and workstations. Read Documentation/filesystems/affs.txt and
7634 With this driver you can also mount disk files used by Bernd
7635 Schmidt's Un*X Amiga Emulator (http://www.freiburg.linux.de/~uae/;
7636 to browse the WWW, you need to have access to a machine on the
7637 Internet that has a program like lynx or netscape). If you want to
7638 do this, you will also need to say Y or M to "Loop device support",
7641 This filesystem is also available as a module ( = code which can be
7642 inserted in and removed from the running kernel whenever you want).
7643 The module is called affs.o. If you want to compile it as a module,
7644 say M here and read Documentation/modules.txt. If unsure, say N.
7646 Apple Macintosh filesystem support (experimental)
7648 If you say Y here, you will be able to mount Macintosh-formatted
7649 floppy disks and hard drive partitions with full read-write access.
7650 Please read fs/hfs/HFS.txt to learn about the available mount
7653 This filesystem support is also available as a module ( = code which
7654 can be inserted in and removed from the running kernel whenever you
7655 want). The module is called hfs.o. If you want to compile it as a
7656 module, say M here and read Documentation/modules.txt.
7658 ROM filesystem support
7660 This is a very small read-only filesystem mainly intended for
7661 initial ram disks of installation disks, but it could be used for
7662 other read-only media as well. Read
7663 Documentation/filesystems/romfs.txt for details.
7665 This filesystem support is also available as a module ( = code which
7666 can be inserted in and removed from the running kernel whenever you
7667 want). The module is called romfs.o. If you want to compile it as a
7668 module, say M here and read Documentation/modules.txt.
7670 If you don't know whether you need it, then you don't need it:
7673 QNX filesystem support (EXPERIMENTAL)
7675 This is the filesystem used by the operating system QNX 4. Say Y if
7676 you intend to mount QNX hard disks or floppies. Unless you say Y to
7677 "QNXFS read-write support" below, you will only be able to read
7680 This filesystem support is also available as a module ( = code which
7681 can be inserted in and removed from the running kernel whenever you
7682 want). The module is called qnx4.o. If you want to compile it as a
7683 module, say M here and read Documentation/modules.txt.
7687 QNXFS read-write support (FOR TESTING ONLY)
7689 Say Y if you want to test write support for QNX filesystems.
7691 Kernel automounter support
7693 The automounter is a tool to automatically mount remote filesystems
7694 on demand. This implementation is partially kernel-based to reduce
7695 overhead in the already-mounted case; this is unlike the BSD
7696 automounter (amd), which is a pure user space daemon.
7698 To use the automounter you need the user-space tools from
7699 ftp://ftp.kernel.org/pub/linux/daemons/autofs; you also want to
7700 answer Y to "NFS filesystem support", below.
7702 If you want to compile this as a module ( = code which can be
7703 inserted in and removed from the running kernel whenever you want),
7704 say M here and read Documentation/modules.txt. The module will be
7707 If you are not a part of a fairly large, distributed network, you
7708 probably do not need an automounter, and can say N here.
7710 UFS filesystem support
7712 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
7713 OpenBSD and NeXTstep) use a filesystem called UFS. Some System V
7714 Unixes can create and mount hard disk partitions and diskettes using
7715 this filesystem as well. Saying Y here will allow you to read from
7716 these partitions; if you also want to write to them, say Y to the
7717 experimental "UFS filesystem write support", below. Please read the
7718 file Documentation/filesystems/ufs.txt for more information.
7720 If you only intend to mount files from some other Unix over the
7721 network using NFS, you don't need the UFS filesystem support (but
7722 you need NFS filesystem support obviously).
7724 Note that this option is generally not needed for floppies, since a
7725 good portable way to transport files and directories between unixes
7726 (and even other operating systems) is given by the tar program ("man
7727 tar" or preferably "info tar").
7729 When accessing NeXTstep files, you may need to convert them from the
7730 NeXT character set to the Latin1 character set; use the program
7731 recode ("info recode") for this purpose.
7733 If you want to compile the UFS filesystem support as a module ( =
7734 code which can be inserted in and removed from the running kernel
7735 whenever you want), say M here and read Documentation/modules.txt.
7736 The module will be called ufs.o.
7738 If you haven't heard about all of this before, it's safe to say N.
7740 UFS filesystem write support (experimental)
7742 Say Y here if you want to try writing to UFS partitions. This is
7743 experimental, so you should back up your UFS partitions beforehand.
7745 EFS filesystem support (experimental)
7747 EFS is the filesystem used for CDROMs and filesystems by SGI's IRIX.
7748 This implementation only offers read-only access. If you don't know
7749 what all this is about, it's safe to say N. For more information
7750 about EFS see its homepage at http://aeschi.ch.eu.org/efs/.
7752 SGI disklabel support
7753 CONFIG_SGI_DISKLABEL
7754 Say Y to this only if you plan on mounting disks with SGI disklabels.
7755 This is not required to mount EFS-format CDROMs.
7757 BSD disklabel (FreeBSD partition tables) support
7758 CONFIG_BSD_DISKLABEL
7759 FreeBSD uses its own hard disk partition scheme on your PC. It
7760 requires only one entry in the primary partition table of your disk
7761 and manages it similarly to DOS extended partitions, putting in its
7762 first sector a new partition table in BSD disklabel format. Saying Y
7763 here allows you to read these disklabels and further mount FreeBSD
7764 partitions from within Linux if you have also said Y to "UFS
7765 filesystem support", above. If you don't know what all this is
7768 SMD disklabel (Sun partition tables) support
7769 CONFIG_SMD_DISKLABEL
7770 Like most systems, SunOS uses its own hard disk partition table
7771 format, incompatible with all others. Saying Y here allows you to
7772 read these partition tables and further mount SunOS disks from
7773 within Linux if you have also said Y to "UFS filesystem support",
7774 above. This is mainly used to carry data from a SPARC under SunOS to
7775 your Linux box via a removable medium like magneto-optical or ZIP
7776 drives; note however that a good portable way to transport files and
7777 directories between unixes (and even other operating systems) is
7778 given by the tar program ("man tar" or preferably "info tar"). If
7779 you don't know what all this is about, say N.
7781 Solaris (x86) partition table support
7782 CONFIG_SOLARIS_X86_PARTITION
7783 Like most systems, Solaris x86 uses its own hard disk partition
7784 table format, incompatible with all others. Saying Y here allows you
7785 to read these partition tables and further mount Solaris x86 disks
7786 from within Linux if you have also said Y to "UFS filesystem
7789 ADFS filesystem support (read only) (EXPERIMENTAL)
7791 The Acorn Disc Filing System is the standard filesystem of the
7792 RiscOS operating system which runs on Acorn's ARM-based Risc PC
7793 systems and the Acorn Archimedes range of machines. If you say Y
7794 here, Linux will be able to read from ADFS partitions on hard drives
7795 and from ADFS-formatted floppy discs.
7797 The ADFS partition should be the first partition (i.e.,
7798 /dev/[hs]d?1) on each of your drives.
7800 This code is also available as a module called adfs.o ( = code which
7801 can be inserted in and removed from the running kernel whenever you
7802 want). If you want to compile it as a module, say M here and read
7803 Documentation/modules.txt.
7807 /dev/pts filesystem for Unix98 PTYs
7809 You should say Y here if you said Y to "Unix98 PTY support" above.
7810 You'll then get a virtual filesystem which can be mounted on
7811 /dev/pts with "mount -t devpts". This, together with the pseudo
7812 terminal master multiplexer /dev/ptmx, is used for pseudo terminal
7813 support as described in The Open Group's Unix98 standard: in order
7814 to acquire a pseudo terminal, a process opens /dev/ptmx; the number
7815 of the pseudo terminal is then made available to the process and the
7816 pseudo terminal slave can be accessed as /dev/pts/<number>. What was
7817 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
7819 The GNU C library glibc 2.1 contains the requisite support for this
7820 mode of operation; you also need client programs that use the Unix98
7823 UnixWare slices support (EXPERIMENTAL)
7824 CONFIG_UNIXWARE_DISKLABEL
7825 Like some systems, UnixWare uses its own slice table inside a
7826 partition (VTOC - Virtual Table of Contents). Its format is
7827 incompatible with all other OSes. Saying Y here allows you to read
7828 VTOC and further mount UnixWare partitions read-only from within
7829 Linux if you have also said Y to "UFS filesystem support" or "System
7830 V and Coherent filesystem support", above.
7832 This is mainly used to carry data from a UnixWare box to your
7833 Linux box via a removable medium like magneto-optical, ZIP or
7834 removable IDE drives. Note, however, that a good portable way to
7835 transport files and directories between unixes (and even other
7836 operating systems) is given by the tar program ("man tar" or
7837 preferably "info tar").
7839 If you don't know what all this is about, say N.
7841 Macintosh partition map support
7842 CONFIG_MAC_PARTITION
7843 Say Y here if you want your Linux system to be able to read the
7844 partition tables of Macintosh hard drives, and thus use partitions
7847 SMB filesystem support (to mount Windows shares etc...)
7849 SMB (Server Message Block) is the protocol Windows for Workgroups
7850 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
7851 files and printers over local networks. Saying Y here allows you to
7852 mount their filesystems (often called "shares" in this context) and
7853 access them just like any other Unix directory. Currently, this
7854 works only if the Windows machines use TCP/IP as the underlying
7855 transport protocol, and not NetBEUI. For details, read
7856 Documentation/filesystems/smbfs.txt and the SMB-HOWTO, available via
7857 FTP (user: anonymous) from
7858 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
7860 Note: if you just want your box to act as an SMB *server* and make
7861 files and printing services available to Windows clients (which need
7862 to have a TCP/IP stack), you don't need to say Y here; you can use
7863 the program samba (available via FTP (user: anonymous) in
7864 ftp://metalab.unc.edu/pub/Linux/system/network/samba) for that.
7866 General information about how to connect Linux, Windows machines and
7867 Macs is on the WWW at http://www.eats.com/linux_mac_win.html (to
7868 browse the WWW, you need to have access to a machine on the Internet
7869 that has a program like lynx or netscape).
7871 If you want to compile the SMB support as a module ( = code which
7872 can be inserted in and removed from the running kernel whenever you
7873 want), say M here and read Documentation/modules.txt. The module
7874 will be called smbfs.o. Most people say N, however.
7876 Coda filesystem support
7878 Coda is an advanced network filesystem, similar to NFS in that it
7879 enables you to mount filesystems of a remote server and access them
7880 with regular Unix commands as if they were sitting on your hard
7881 disk. Coda has several advantages over NFS: support for disconnected
7882 operation (e.g. for laptops), read/write server replication,
7883 security model for authentication and encryption, persistent client
7884 caches and write back caching.
7886 If you say Y here, your Linux box will be able to act as a Coda
7887 *client*. You will need user level code as well, both for the client
7888 and server. Servers are currently user level, i.e. need no kernel
7889 support. Please read Documentation/filesystems/coda.txt and check
7890 out the Coda home page http://www.coda.cs.cmu.edu (to browse the
7891 WWW, you need to have access to a machine on the Internet that has a
7892 program like lynx or netscape).
7894 If you want to compile the coda client support as a module ( = code
7895 which can be inserted in and removed from the running kernel
7896 whenever you want), say M here and read Documentation/modules.txt.
7897 The module will be called coda.o.
7899 NCP filesystem support (to mount NetWare volumes)
7901 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
7902 used by Novell NetWare clients to talk to file servers. It is to IPX
7903 what NFS is to TCP/IP, if that helps. Saying Y here allows you to
7904 mount NetWare file server volumes and to access them just like any
7905 other Unix directory. For details, please read the file
7906 Documentation/filesystems/ncpfs.txt in the kernel source and the
7907 IPX-HOWTO on ftp://metalab.unc.edu/pub/Linux/docs/howto.
7909 You do not have to say Y here if you want your Linux box to act as a
7910 file *server* for Novell NetWare clients.
7912 General information about how to connect Linux, Windows machines and
7913 Macs is on the WWW at http://www.eats.com/linux_mac_win.html (to
7914 browse the WWW, you need to have access to a machine on the Internet
7915 that has a program like lynx or netscape).
7917 If you want to compile this as a module ( = code which can be
7918 inserted in and removed from the running kernel whenever you want),
7919 say M here and read Documentation/modules.txt. The module will be
7920 called ncpfs.o. Say N unless you are connected to a Novell network.
7923 CONFIG_NCPFS_PACKET_SIGNING
7924 NCP allows packets to be signed for stronger security. If you want
7925 security, say Y. Normal users can leave it off. To be able to use
7926 packet signing you must use ncpfs > 2.0.12.
7928 Proprietary file locking
7929 CONFIG_NCPFS_IOCTL_LOCKING
7930 Allows locking of records on remote volumes. Say N unless you have
7931 special applications which are able to utilize this locking scheme.
7933 Clear remove/delete inhibit when needed
7935 Allows manipulation of files flagged as Delete or Rename Inhibit. To
7936 use this feature you must mount volumes with the ncpmount parameter
7937 "-s" (ncpfs-2.0.12 and newer). Say Y unless you are not mounting
7938 volumes with -f 444.
7940 Use NFS namespace when available
7942 Allows you to utilize NFS namespace on NetWare servers. It brings
7943 you case sensitive filenames. Say Y. You can disable it at
7944 mount-time with the `-N nfs' parameter of ncpmount.
7946 Use OS2/LONG namespace when available
7948 Allows you to utilize OS2/LONG namespace on NetWare servers.
7949 Filenames in this namespace are limited to 255 characters, they are
7950 case insensitive, and case in names is preserved. Say Y. You can
7951 disable it at mount time with the -N os2 parameter of ncpmount.
7953 Lowercase DOS filenames on LONG namespace volume
7954 CONFIG_NCPFS_SMALLDOS
7955 If you say Y here, every filename on a NetWare server volume using
7956 the OS2/LONG namespace will be converted to lowercase characters.
7957 (For regular NetWare file server volumes with DOS namespace, this is
7958 done automatically, even if you say N here.) Saying N here will give
7959 you these filenames in uppercase.
7961 This is only a cosmetic option since the OS2/LONG namespace is case
7962 insensitive. The only major reason for this option is backward
7963 compatibility when moving from DOS to OS2/LONG namespace support.
7964 Long filenames (created by Win95) will not be affected.
7966 This option does not solve the problem that filenames appear
7967 differently under Linux and under Windows, since Windows does an
7968 additional conversions on the client side. You can achieve similar
7969 effects by saying Y to "Allow using of Native Language Support"
7972 Allow mounting of volume subdirectories
7973 CONFIG_NCPFS_MOUNT_SUBDIR
7974 Allows you to mount not only whole servers or whole volumes, but
7975 also subdirectories from a volume. It can be used to reexport data
7976 and so on. There is no reason to say N, so Y is recommended unless
7977 you count every byte.
7979 To utilize this feature you must use ncpfs-2.0.12 or newer.
7981 NDS interserver authentication domains
7982 CONFIG_NCPFS_NDS_DOMAINS
7983 This allows storing NDS private keys in kernel space where they
7984 can be used to authenticate another server as interserver NDS
7985 accesses need it. You must use ncpfs-2.0.12.1 or newer to utilize
7986 this feature. Say Y if you are using NDS connections to NetWare
7987 servers. Do not say Y if security is primary for you because root
7988 can read your session key (from /proc/kcore).
7990 Allow using of Native Language Support
7992 Allows you to use codepages and I/O charsets for file name
7993 translation between the server file system and input/output. This
7994 may be useful, if you want to access the server with other operating
7995 systems, e.g. Windows 95. See also NLS for more Information.
7997 To select codepages and I/O charsets use ncpfs-2.2.0.13 or newer.
7999 Symbolic links and mode permission bits
8001 This enables the use of symbolic links and an execute permission
8002 bit on NCPFS. The file server need not have long name space or NFS
8003 name space loaded for these to work.
8005 To use the new attributes, it is recommended to use the flags
8006 '-f 600 -d 755' on the ncpmount command line.
8009 CONFIG_NLS_CODEPAGE_437
8010 The Microsoft fat filesystem family can deal with filenames in
8011 native language character sets. These character sets are stored
8012 in so-called DOS codepages. You need to include the appropriate
8013 codepage if you want to be able to read/write these filenames on
8014 DOS/Windows partitions correctly. This does apply to the filenames
8015 only, not to the file contents. You can include several codepages;
8016 say Y here if you want to include the DOS codepage that is used in
8017 the United States and parts of Canada. This is recommended.
8020 CONFIG_NLS_CODEPAGE_737
8021 The Microsoft fat filesystem family can deal with filenames in
8022 native language character sets. These character sets are stored
8023 in so-called DOS codepages. You need to include the appropriate
8024 codepage if you want to be able to read/write these filenames on
8025 DOS/Windows partitions correctly. This does apply to the filenames
8026 only, not to the file contents. You can include several codepages;
8027 say Y here if you want to include the DOS codepage that is used for
8028 Greek. If unsure, say N.
8031 CONFIG_NLS_CODEPAGE_775
8032 The Microsoft fat filesystem family can deal with filenames in
8033 native language character sets. These character sets are stored
8034 in so-called DOS codepages. You need to include the appropriate
8035 codepage if you want to be able to read/write these filenames on
8036 DOS/Windows partitions correctly. This does apply to the filenames
8037 only, not to the file contents. You can include several codepages;
8038 say Y here if you want to include the DOS codepage that is used
8039 for the Baltic Rim Languages. If unsure, say N.
8042 CONFIG_NLS_CODEPAGE_850
8043 The Microsoft fat filesystem family can deal with filenames in
8044 native language character sets. These character sets are stored in
8045 so-called DOS codepages. You need to include the appropriate
8046 codepage if you want to be able to read/write these filenames on
8047 DOS/Windows partitions correctly. This does apply to the filenames
8048 only, not to the file contents. You can include several codepages;
8049 say Y here if you want to include the DOS codepage that is used for
8050 much of Europe -- United Kingdom, Germany, Spain, Italy, and [add
8051 more countries here]. It has some characters useful to many European
8052 languages that are not part of the US codepage 437.
8057 CONFIG_NLS_CODEPAGE_852
8058 The Microsoft fat filesystem family can deal with filenames in
8059 native language character sets. These character sets are stored in
8060 so-called DOS codepages. You need to include the appropriate
8061 codepage if you want to be able to read/write these filenames on
8062 DOS/Windows partitions correctly. This does apply to the filenames
8063 only, not to the file contents. You can include several codepages;
8064 say Y here if you want to include the Latin 2 codepage used by DOS
8065 for much of Central and Eastern Europe. It has all the required
8066 characters for these languages: Albanian, Croatian, Czech, English,
8067 Finnish, Hungarian, Irish, German, Polish, Romanian, Serbian (Latin
8068 transcription), Slovak, Slovenian, and Sorbian.
8071 CONFIG_NLS_CODEPAGE_855
8072 The Microsoft fat filesystem family can deal with filenames in
8073 native language character sets. These character sets are stored in
8074 so-called DOS codepages. You need to include the appropriate
8075 codepage if you want to be able to read/write these filenames on
8076 DOS/Windows partitions correctly. This does apply to the filenames
8077 only, not to the file contents. You can include several codepages;
8078 say Y here if you want to include the DOS codepage for Cyrillic.
8081 CONFIG_NLS_CODEPAGE_857
8082 The Microsoft fat filesystem family can deal with filenames in
8083 native language character sets. These character sets are stored in
8084 so-called DOS codepages. You need to include the appropriate
8085 codepage if you want to be able to read/write these filenames on
8086 DOS/Windows partitions correctly. This does apply to the filenames
8087 only, not to the file contents. You can include several codepages;
8088 say Y here if you want to include the DOS codepage for Turkish.
8091 CONFIG_NLS_CODEPAGE_860
8092 The Microsoft fat filesystem family can deal with filenames in
8093 native language character sets. These character sets are stored in
8094 so-called DOS codepages. You need to include the appropriate
8095 codepage if you want to be able to read/write these filenames on
8096 DOS/Windows partitions correctly. This does apply to the filenames
8097 only, not to the file contents. You can include several codepages;
8098 say Y here if you want to include the DOS codepage for Portuguese.
8101 CONFIG_NLS_CODEPAGE_861
8102 The Microsoft fat filesystem family can deal with filenames in
8103 native language character sets. These character sets are stored in
8104 so-called DOS codepages. You need to include the appropriate
8105 codepage if you want to be able to read/write these filenames on
8106 DOS/Windows partitions correctly. This does apply to the filenames
8107 only, not to the file contents. You can include several codepages;
8108 say Y here if you want to include the DOS codepage for Icelandic.
8111 CONFIG_NLS_CODEPAGE_862
8112 The Microsoft fat filesystem family can deal with filenames in
8113 native language character sets. These character sets are stored in
8114 so-called DOS codepages. You need to include the appropriate
8115 codepage if you want to be able to read/write these filenames on
8116 DOS/Windows partitions correctly. This does apply to the filenames
8117 only, not to the file contents. You can include several codepages;
8118 say Y here if you want to include the DOS codepage for Hebrew.
8121 CONFIG_NLS_CODEPAGE_863
8122 The Microsoft fat filesystem family can deal with filenames in
8123 native language character sets. These character sets are stored in
8124 so-called DOS codepages. You need to include the appropriate
8125 codepage if you want to be able to read/write these filenames on
8126 DOS/Windows partitions correctly. This does apply to the filenames
8127 only, not to the file contents. You can include several codepages;
8128 say Y here if you want to include the DOS codepage for Canadian
8132 CONFIG_NLS_CODEPAGE_864
8133 The Microsoft fat filesystem family can deal with filenames in
8134 native language character sets. These character sets are stored in
8135 so-called DOS codepages. You need to include the appropriate
8136 codepage if you want to be able to read/write these filenames on
8137 DOS/Windows partitions correctly. This does apply to the filenames
8138 only, not to the file contents. You can include several codepages;
8139 say Y here if you want to include the DOS codepage for Arabic.
8142 CONFIG_NLS_CODEPAGE_865
8143 The Microsoft fat filesystem family can deal with filenames in
8144 native language character sets. These character sets are stored in
8145 so-called DOS codepages. You need to include the appropriate
8146 codepage if you want to be able to read/write these filenames on
8147 DOS/Windows partitions correctly. This does apply to the filenames
8148 only, not to the file contents. You can include several codepages;
8149 say Y here if you want to include the DOS codepage for the Nordic
8153 CONFIG_NLS_CODEPAGE_866
8154 The Microsoft fat filesystem family can deal with filenames in
8155 native language character sets. These character sets are stored in
8156 so-called DOS codepages. You need to include the appropriate
8157 codepage if you want to be able to read/write these filenames on
8158 DOS/Windows partitions correctly. This does apply to the filenames
8159 only, not to the file contents. You can include several codepages;
8160 say Y here if you want to include the DOS codepage for
8164 CONFIG_NLS_CODEPAGE_869
8165 The Microsoft fat filesystem family can deal with filenames in
8166 native language character sets. These character sets are stored in
8167 so-called DOS codepages. You need to include the appropriate
8168 codepage if you want to be able to read/write these filenames on
8169 DOS/Windows partitions correctly. This does apply to the filenames
8170 only, not to the file contents. You can include several codepages;
8171 say Y here if you want to include the DOS codepage for Greek.
8173 ### Why do we have two codepages for Greek and Cyrillic?
8177 CONFIG_NLS_CODEPAGE_874
8178 The Microsoft fat filesystem family can deal with filenames in
8179 native language character sets. These character sets are stored in
8180 so-called DOS codepages. You need to include the appropriate
8181 codepage if you want to be able to read/write these filenames on
8182 DOS/Windows partitions correctly. This does apply to the filenames
8183 only, not to the file contents. You can include several codepages;
8184 say Y here if you want to include the DOS codepage for Thai.
8187 CONFIG_NLS_ISO8859_1
8188 If you want to display filenames with native language characters
8189 from the Microsoft fat filesystem family or from JOLIET CDROMs
8190 correctly on the screen, you need to include the appropriate
8191 input/output character sets. Say Y here for the Latin 1 character
8192 set, which covers most West European languages such as Albanian,
8193 Catalan, Danish, Dutch, English, Faeroese, Finnish, French, German,
8194 Galician, Irish, Icelandic, Italian, Norwegian, Portuguese, Spanish,
8195 and Swedish. It is also the default for the US. If unsure, say Y.
8198 CONFIG_NLS_ISO8859_2
8199 If you want to display filenames with native language characters
8200 from the Microsoft fat filesystem family or from JOLIET CDROMs
8201 correctly on the screen, you need to include the appropriate
8202 input/output character sets. Say Y here for the Latin 2 character
8203 set, which works for most Latin-written Slavic and Central European
8204 languages: Czech, German, Hungarian, Polish, Rumanian, Croatian,
8208 CONFIG_NLS_ISO8859_3
8209 If you want to display filenames with native language characters
8210 from the Microsoft fat filesystem family or from JOLIET CDROMs
8211 correctly on the screen, you need to include the appropriate
8212 input/output character sets. Say Y here for the Latin 3 character
8213 set, which is popular with authors of Esperanto, Galician, Maltese,
8217 CONFIG_NLS_ISO8859_4
8218 If you want to display filenames with native language characters
8219 from the Microsoft fat filesystem family or from JOLIET CDROMs
8220 correctly on the screen, you need to include the appropriate
8221 input/output character sets. Say Y here for the Latin 4 character
8222 set which introduces letters for Estonian, Latvian, and
8223 Lithuanian. It is an incomplete predecessor of Latin 6.
8226 CONFIG_NLS_ISO8859_5
8227 If you want to display filenames with native language characters
8228 from the Microsoft fat filesystem family or from JOLIET CDROMs
8229 correctly on the screen, you need to include the appropriate
8230 input/output character sets. Say Y here for ISO8859-5, a Cyrillic
8231 character set with which you can type Bulgarian, Byelorussian,
8232 Macedonian, Russian, Serbian, and Ukrainian. Note that the charset
8233 KOI8-R is preferred in Russia.
8236 CONFIG_NLS_ISO8859_6
8237 If you want to display filenames with native language characters
8238 from the Microsoft fat filesystem family or from JOLIET CDROMs
8239 correctly on the screen, you need to include the appropriate
8240 input/output character sets. Say Y here for ISO8859-6, the Arabic
8244 CONFIG_NLS_ISO8859_7
8245 If you want to display filenames with native language characters
8246 from the Microsoft fat filesystem family or from JOLIET CDROMs
8247 correctly on the screen, you need to include the appropriate
8248 input/output character sets. Say Y here for ISO8859-7, the Modern
8249 Greek character set.
8252 CONFIG_NLS_ISO8859_8
8253 If you want to display filenames with native language characters
8254 from the Microsoft fat filesystem family or from JOLIET CDROMs
8255 correctly on the screen, you need to include the appropriate
8256 input/output character sets. Say Y here for ISO8859-8, the Hebrew
8260 CONFIG_NLS_ISO8859_9
8261 If you want to display filenames with native language characters
8262 from the Microsoft fat filesystem family or from JOLIET CDROMs
8263 correctly on the screen, you need to include the appropriate
8264 input/output character sets. Say Y here for the Latin 5 character
8265 set, and it replaces the rarely needed Icelandic letters in Latin 1
8266 with the Turkish ones. Useful in Turkey.
8269 CONFIG_NLS_ISO8859_10
8270 If you want to display filenames with native language characters
8271 from the Microsoft fat filesystem family or from JOLIET CDROMs
8272 correctly on the screen, you need to include the appropriate
8273 input/output character sets. Say Y here for the Latin 6 character
8274 set, which adds the last Inuit (Greenlandic) and Sami (Lappish)
8275 letters that were missing in Latin 4 to cover the entire Nordic
8279 CONFIG_NLS_ISO8859_15
8280 If you want to display filenames with native language characters
8281 from the Microsoft fat filesystem family or from JOLIET CDROMs
8282 correctly on the screen, you need to include the appropriate
8283 input/output character sets. Say Y here for the Latin 9 character
8284 set, which covers most West European languages such as Albanian,
8285 Catalan, Danish, Dutch, English, Estonian, Faeroese, Finnish,
8286 French, German, Galician, Irish, Icelandic, Italian, Norwegian,
8287 Portuguese, Spanish, and Swedish. Latin 9 is an update to
8288 Latin 1 (ISO 8859-1) that removes a handful of rarely used
8289 characters and instead adds support for Estonian, corrects the
8290 support for French and Finnish, and adds the new Euro character. If
8295 If you want to display filenames with native language characters
8296 from the Microsoft fat filesystem family or from JOLIET CDROMs
8297 correctly on the screen, you need to include the appropriate
8298 input/output character sets. Say Y here for the preferred Russian
8303 If you say Y here, you will get support for terminal devices with
8304 display and keyboard devices. These are called "virtual" because you
8305 can run several virtual terminals (also called virtual consoles) on
8306 one physical terminal. This is rather useful, for example one
8307 virtual terminal can collect system messages and warnings, another
8308 one can be used for a text-mode user session, and a third could run
8309 an X session, all in parallel. Switching between virtual terminals
8310 is done with certain key combinations, usually Alt-<function key>.
8312 The setterm command ("man setterm") can be used to change the
8313 properties (such as colors) of a virtual terminal.
8315 You need at least one virtual terminal device in order to make use
8316 of your keyboard and monitor. Therefore, only people configuring an
8317 embedded system would want to say N here in order to save some
8318 memory; the only way to log into such a system is then via a serial
8319 or network connection.
8321 If unsure, say Y, or else you won't be able to do much with your new
8322 shiny Linux system :-)
8324 Support for console on virtual terminal
8326 The system console is the device which receives all kernel messages
8327 and warnings and which allows logins in single user mode. If you
8328 answer Y here, a virtual terminal (the device used to interact with
8329 a physical terminal) can be used as system console. This is the most
8330 common mode of operations, so you should say Y here unless you want
8331 the kernel messages be output only to a serial port (in which case
8332 you should say Y to "Console on serial port", below).
8334 If you do say Y here, by default the currently visible virtual
8335 terminal (/dev/tty0) will be used as system console. You can change
8336 that with a kernel command line option such as "console=tty3" which
8337 would use the third virtual terminal as system console. (Try "man
8338 bootparam" or see the documentation of your boot loader (lilo or
8339 loadlin) about how to pass options to the kernel at boot time. The
8340 lilo procedure is also explained in the SCSI-HOWTO, available via
8341 FTP (user: anonymous) in
8342 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.)
8346 Software generated cursor
8348 If you say Y here, you'll be able to do lots of nice things with the
8349 cursors of your virtual consoles -- for example turn them into
8350 non-blinking block cursors which are more visible on laptop screens,
8351 or change their colors depending on the virtual console they're on.
8352 See Documentation/VGA-softcursor.txt for more information.
8354 Support for PowerMac keyboard
8356 This option allows you to use an ADB keyboard attached to your
8357 machine. Note that this disables any other (ie. PS/2) keyboard
8358 support, even if your machine is physically capable of using both at
8361 If you use an ADB keyboard (4 pin connector), say Y here.
8362 If you use a PS/2 keyboard (6 pin connector), say N here.
8364 Standard/generic serial support
8366 This selects whether you want to include the driver for the standard
8367 serial ports. The standard answer is Y. People who might say N here
8368 are those that are setting up dedicated Ethernet WWW/FTP servers, or
8369 users that have one of the various bus mice instead of a serial
8370 mouse and don't intend to use their machine's standard serial port
8371 for anything. (Note that the Cyclades and Stallion multi serial port
8372 drivers do not need this driver built in for them to work.)
8374 If you want to compile this driver as a module, say M here and read
8375 Documentation/modules.txt. The module will be called serial.o.
8376 [WARNING: Do not compile this driver as a module if you are using
8377 non-standard serial ports, since the configuration information will
8378 be lost when the driver is unloaded. This limitation may be lifted
8381 BTW1: If you have a mouseman serial mouse which is not recognized by
8382 the X window system, try running gpm first.
8384 BTW2: If you intend to connect a so-called Winmodem to your
8385 machine's serial port, forget it. These modems are crippled and
8386 require proprietary drivers which are only available under Windows.
8388 Most people will say Y or M here, so that they can use serial mice,
8389 modems and similar devices connecting to the standard serial ports.
8391 Support for console on serial port
8392 CONFIG_SERIAL_CONSOLE
8393 If you say Y here, it will be possible to use a serial port as the
8394 system console (the system console is the device which receives all
8395 kernel messages and warnings and which allows logins in single user
8396 mode). This could be useful if some terminal or printer is connected
8397 to that serial port.
8399 Even if you say Y here, the currently visible virtual console
8400 (/dev/tty0) will still be used as the system console by default, but
8401 you can alter that using a kernel command line option such as
8402 "console=ttyS1". (Try "man bootparam" or see the documentation of
8403 your boot loader (lilo or loadlin) about how to pass options to the
8404 kernel at boot time. The lilo procedure is also explained in the
8405 SCSI-HOWTO, available via FTP (user: anonymous) in
8406 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.)
8408 If you don't have a VGA card installed and you say Y here, the
8409 kernel will automatically use the first serial line, /dev/ttyS0, as
8414 Support for PowerMac serial ports
8416 If you have Macintosh style serial ports (8 pin mini-DIN), say Y
8417 here. If you also have regular serial ports and enable the driver
8418 for them, you can't currently use the serial console feature.
8420 Comtrol Rocketport support
8422 This is a driver for the Comtrol Rocketport cards which provide
8423 multiple serial ports. You would need something like this to connect
8424 more than two modems to your Linux box, for instance in order to
8425 become a dial-in server.
8427 If you want to compile this driver as a module, say M here and read
8428 Documentation/modules.txt. The module will be called rocket.o.
8430 Digiboard Intelligent async support
8432 This is a driver for Digi International's Xx, Xeve, and Xem series
8433 of cards which provide multiple serial ports. You would need
8434 something like this to connect more than two modems to your Linux
8435 box, for instance in order to become a dial-in server. This driver
8436 supports the original PC (ISA) boards as well as PCI, and EISA. If
8437 you have a card like this, say Y here and read the file
8438 Documentation/digiepca.txt.
8440 NOTE: There is another, separate driver for the Digiboard PC boards:
8441 "Digiboard PC/Xx Support" below. You should (and can) only select
8442 one of the two drivers.
8444 If you want to compile this driver as a module, say M here and read
8445 Documentation/modules.txt. The module will be called epca.o.
8447 Digiboard PC/Xx Support
8449 This is a driver for the Digiboard PC/Xe, PC/Xi, and PC/Xeve cards
8450 that give you many serial ports. You would need something like this
8451 to connect more than two modems to your Linux box, for instance in
8452 order to become a dial-in server. If you have a card like that, say
8453 Y here and read the file Documentation/digiboard.txt.
8455 If you want to compile this driver as a module, say M here and read
8456 Documentation/modules.txt. The module will be called pcxx.o.
8458 SDL RISCom/8 card support
8460 This is a driver for the SDL Communications RISCom/8 multiport card,
8461 which gives you many serial ports. You would need something like
8462 this to connect more than two modems to your Linux box, for instance
8463 in order to become a dial-in server. If you have a card like that,
8464 say Y here and read the file Documentation/riscom8.txt.
8466 Also it's possible to say M here and compile this driver as kernel
8467 loadable module; the module will be called riscom8.o.
8469 Specialix IO8+ card support
8471 This is a driver for the Specialix IO8+ multiport card (both the
8472 ISA and the PCI version) which gives you many serial ports. You
8473 would need something like this to connect more than two modems to
8474 your Linux box, for instance in order to become a dial-in server.
8476 If you have a card like that, say Y here and read the file
8477 Documentation/specialix.txt. Also it's possible to say M here and
8478 compile this driver as kernel loadable module which will be called
8481 Specialix DTR/RTS pin is RTS
8482 CONFIG_SPECIALIX_RTSCTS
8483 The Specialix card can only support either RTS or DTR. If you say N
8484 here, the driver will use the pin as "DTR" when the tty is in
8485 software handshake mode. If you say Y here or hardware handshake is
8486 on, it will always be RTS. Read the file Documentation/specialix.txt
8487 for more information.
8489 Cyclades async mux support
8491 This is a driver for a card that gives you many serial ports. You
8492 would need something like this to connect more than two modems to
8493 your Linux box, for instance in order to become a dial-in server.
8494 For information about the Cyclades-Z card, read
8495 drivers/char/README.cycladesZ.
8497 As of 1.3.9x kernels, this driver's minor numbers start at 0 instead
8500 If you want to compile this as a module ( = code which can be
8501 inserted in and removed from the running kernel whenever you want),
8502 say M here and read Documentation/modules.txt. The module will be
8505 If you haven't heard about it, it's safe to say N.
8507 Cyclades-Z interrupt mode operation (EXPERIMENTAL)
8509 The Cyclades-Z family of multiport cards allows 2 (two) driver
8510 op modes: polling and interrupt. In polling mode, the driver will
8511 check the status of the Cyclades-Z ports every certain amount of
8512 time (which is called polling cycle and is configurable). In
8513 interrupt mode, it will use an interrupt line (IRQ) in order to check
8514 the status of the Cyclades-Z ports. The default op mode is polling.
8517 Stallion multiport serial support
8519 Stallion cards give you many serial ports. You would need something
8520 like this to connect more than two modems to your Linux box, for
8521 instance in order to become a dial-in server. If you say Y here, you
8522 will be asked for your specific card model in the next questions.
8523 Make sure to read drivers/char/README.stallion in this case. If you
8524 have never heard about all this, it's safe to say N.
8526 Stallion EasyIO or EC8/32 support
8528 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
8529 card, then this is for you; say Y. Make sure to read
8530 Documentation/stallion.txt.
8532 If you want to compile this as a module ( = code which can be
8533 inserted in and removed from the running kernel whenever you want),
8534 say M here and read Documentation/modules.txt. The module will be
8537 Stallion EC8/64, ONboard, Brumby support
8539 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
8540 serial multiport card, say Y here. Make sure to read
8541 Documentation/stallion.txt.
8543 To compile it as a module ( = code which can be inserted in and
8544 removed from the running kernel whenever you want), say M here and
8545 read Documentation/modules.txt. The module will be called
8548 Microgate SyncLink adapter support
8550 Provides support for the SyncLink ISA and PCI
8551 multiprotocol serial adapters. These adapters
8552 support asynchronous and HDLC bit synchronous
8553 communication up to 10Mbps (PCI adapter).
8555 This driver can only be built as a module ( = code which can be
8556 inserted in and removed from the running kernel whenever you want).
8557 The module will be called synclink.o. If you want to do that, say M
8560 Synchronous HDLC line discipline support
8562 Allows synchronous HDLC communications with
8563 tty device drivers that support synchronous
8564 HDLC such as the Microgate SyncLink adapter.
8566 This driver can only be built as a module ( = code which can be
8567 inserted in and removed from the running kernel whenever you want).
8568 The module will be called n_hdlc.o. If you want to do that, say M
8571 Hayes ESP serial port support
8573 This is a driver which supports Hayes ESP serial ports. Both single
8574 port cards and multiport cards are supported. Make sure to read
8575 Documentation/hayes-esp.txt.
8577 To compile this driver as a module ( = code which can be inserted in
8578 and removed from the running kernel whenever you want), say M here
8579 and read Documentation/modules.txt. The module will be called esp.o.
8582 Multi-Tech multiport card support
8584 This is a driver for the Multi-Tech cards which provide several
8585 serial ports. The driver is experimental and can currently only be
8586 built as a module ( = code which can be inserted in and removed from
8587 the running kernel whenever you want). Please read
8588 Documentation/modules.txt. The module will be called isicom.o
8592 A pseudo terminal (PTY) is a software device consisting of two
8593 halves: a master and a slave. The slave device behaves identical to
8594 a physical terminal; the master device is used by a process to
8595 read data from and write data to the slave, thereby emulating a
8596 terminal. Typical programs for the master side are telnet servers
8599 Linux has traditionally used the BSD-like names /dev/ptyxx for
8600 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
8601 has a number of problems. The GNU C library glibc 2.1 and later,
8602 however, supports the Unix98 naming standard: in order to acquire a
8603 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
8604 terminal is then made available to the process and the pseudo
8605 terminal slave can be accessed as /dev/pts/<number>. What was
8606 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
8608 The entries in /dev/pts/ are created on the fly by a virtual
8609 filesystem; therefore, if you say Y here you should say Y to
8610 "/dev/pts filesystem for Unix98 PTYs" as well.
8612 If you want to say Y here, you need to have the C library glibc 2.1
8613 or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
8614 Read the instructions in Documentation/Changes pertaining to pseudo
8615 terminals. It's safe to say N.
8617 Maximum number of Unix98 PTYs in use (0-2048)
8618 CONFIG_UNIX98_PTY_COUNT
8619 The maximum number of Unix98 PTYs that can be used at any one time.
8620 The default is 256, and should be enough for desktop systems. Server
8621 machines which support incoming telnet/rlogin/ssh connections and/or
8622 serve several X terminals may want to increase this: every incoming
8623 connection and every xterm uses up one PTY.
8625 When not in use, each additional set of 256 PTYs occupy
8626 approximately 8 KB of kernel memory on 32-bit architectures.
8628 Parallel printer support
8630 If you intend to attach a printer to the parallel port of your Linux
8631 box (as opposed to using a serial printer; if the connector at the
8632 printer has 9 or 25 holes ["female"], then it's serial), say Y. Also
8633 read the Printing-HOWTO, available via FTP (user: anonymous) in
8634 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
8636 It is possible to share one parallel port among several devices
8637 (e.g. printer and ZIP drive) and it is safe to compile the
8638 corresponding drivers into the kernel. If you want to compile this
8639 driver as a module however ( = code which can be inserted in and
8640 removed from the running kernel whenever you want), say M here and
8641 read Documentation/modules.txt and Documentation/parport.txt. The
8642 module will be called lp.o.
8644 If you have several parallel ports, you can specify which ports to
8645 use with the "lp" kernel command line option. (Try "man bootparam"
8646 or see the documentation of your boot loader (lilo or loadlin)
8647 about how to pass options to the kernel at boot time. The lilo
8648 procedure is also explained in the SCSI-HOWTO, available via FTP
8649 (user: anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.)
8650 The syntax of the "lp" command line option can be found in
8653 If you have more than 3 printers, you need to increase the LP_NO
8656 Support for console on line printer
8658 If you want kernel messages to be printed out as they occur, you
8659 can have a console on the printer. This option adds support for
8660 doing that; to actually get it to happen you need to pass the
8661 option "console=lp" to the kernel at boot time.
8663 Note that kernel messages can get lost if the printer is out of
8664 paper (or off, or unplugged, or too busy..), but this behaviour
8665 can be changed. See drivers/char/lp.c (do this at your own risk).
8669 Mouse Support (not serial mice)
8671 This is for machines with a bus mouse or a PS/2 mouse as opposed to
8672 a serial mouse. Most people have a regular serial MouseSystem or
8673 Microsoft mouse (made by Logitech) that plugs into a COM port
8674 (rectangular with 9 or 25 pins). These people say N here. If you
8675 have something else, read the Busmouse-HOWTO, available via FTP
8676 (user: anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO and
8679 If you have a laptop, you either have to check the documentation or
8680 experiment a bit to find out whether the trackball is a serial mouse
8681 or not; it's best to say Y here for you.
8683 Note that the answer to this question won't directly affect the
8684 kernel: saying N will just cause this configure script to skip all
8685 the questions about non-serial mice. If unsure, say Y.
8687 Logitech busmouse support
8689 Logitech mouse connected to a proprietary interface card. It's
8690 generally a round connector with 9 pins. Note that the newer mice
8691 made by Logitech don't use the Logitech protocol anymore; for those,
8692 you don't need this option. You want to read the Busmouse-HOWTO,
8693 available via FTP (user: anonymous) in
8694 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
8696 If you want to compile this as a module ( = code which can be
8697 inserted in and removed from the running kernel whenever you want),
8698 say M here and read Documentation/modules.txt. The module will be
8699 called busmouse.o. If you are unsure, say N and read the HOWTO
8700 nevertheless: it will tell you what you have.
8702 PS/2 mouse (aka "auxiliary device") support
8704 The PS/2 mouse connects to a special mouse port that looks much like
8705 the keyboard port (small circular connector with 6 pins). This way,
8706 the mouse does not use any serial ports. This port can also be used
8707 for other input devices like light pens, tablets, keypads. Compaq,
8708 AST and IBM all use this as their mouse port on currently shipping
8709 machines. The trackballs of some laptops are PS/2 mice also. In
8710 particular, the C&T 82C710 mouse on TI Travelmates is a PS/2 mouse.
8712 Although PS/2 mice are not technically bus mice, they are explained
8713 in detail in the Busmouse-HOWTO, available via FTP (user: anonymous)
8714 in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
8716 When using a PS/2 mouse, you can get problems if you want to use the
8717 mouse both on the Linux console and under X. Using the "-R" option
8718 of the Linux mouse managing program gpm (available from
8719 ftp://metalab.unc.edu/pub/Linux/system/Daemons) solves this
8720 problem, or you can get the "mconv" utility also from metalab.
8722 C&T 82C710 mouse port support (as on TI Travelmate)
8724 This is a certain kind of PS/2 mouse used on the TI Travelmate. If
8725 you are unsure, try first to say N here and come back if the mouse
8726 doesn't work. Read the Busmouse-HOWTO, available via FTP (user:
8727 anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
8729 PC110 digitizer pad support
8731 This drives the digitizer pad on the IBM PC110 palmtop (see
8732 http://toy.cabi.net; to browse the WWW, you need to have access to a
8733 machine on the Internet that has a program like lynx or
8734 netscape). It can turn the digitizer pad into a PS/2 mouse emulation
8735 with tap gestures or into an absolute pad.
8737 If you want to compile this as a module ( = code which can be
8738 inserted in and removed from the running kernel whenever you want),
8739 say M here and read Documentation/modules.txt. The module will be
8742 Microsoft busmouse support
8744 These animals (also called Inport mice) are connected to an
8745 expansion board using a round connector with 9 pins. If this is what
8746 you have, say Y and read the Busmouse-HOWTO, available via FTP
8747 (user: anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
8749 If you are unsure, say N and read the HOWTO nevertheless: it will
8750 tell you what you have. Also be aware that several vendors talk
8751 about 'Microsoft busmouse' and actually mean PS/2 busmouse -- so
8752 count the pins on the connector.
8754 If you want to compile this as a module ( = code which can be
8755 inserted in and removed from the running kernel whenever you want),
8756 say M here and read Documentation/modules.txt. The module will be
8757 called msbusmouse.o.
8759 ATIXL busmouse support
8760 CONFIG_ATIXL_BUSMOUSE
8761 This is a rare type of busmouse that is connected to the back of an
8762 ATI video card. Note that most ATI mice are actually Microsoft
8763 busmice. Read the Busmouse-HOWTO, available via FTP (user:
8764 anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
8766 If you want to compile this as a module ( = code which can be
8767 inserted in and removed from the running kernel whenever you want),
8768 say M here and read Documentation/modules.txt. The module will be
8769 called atixlmouse.o.
8771 If you are unsure, say N and read the HOWTO nevertheless: it will
8772 tell you what you have.
8774 Support for PowerMac ADB mouse
8776 If you have an ADB mouse (4 pin connector) as is common on
8777 Macintoshes, say Y here.
8781 If you have a non-SCSI tape drive like that, say Y. Or, if you want
8782 to compile this driver as a module ( = code which can be inserted in
8783 and removed from the running kernel whenever you want), say M here
8784 and read Documentation/modules.txt. The module will be called
8787 Do you want runtime configuration for QIC-02
8788 CONFIG_QIC02_DYNCONF
8789 You can either configure this driver once and for all by editing a
8790 header file (include/linux/tpqic02.h), in which case you should
8791 say N, or you can fetch a program via anonymous FTP which is able
8792 to configure this driver during runtime. The program to do this is
8793 called 'qic02conf' and it is part of the tpqic02-support-X.Y.tar.gz
8796 If you want to use the qic02conf program, say Y.
8798 Floppy tape drive (QIC-80/40/3010/3020/TR-1/TR-2/TR-3) support
8800 If you have a tape drive that is connected to your floppy
8801 controller, say Y here.
8803 Some tape drives (like the Seagate "Tape Store 3200" or the Iomega
8804 "Ditto 3200" or the Exabyte "Eagle TR-3") come with a "high speed"
8805 controller of their own. These drives (and their companion
8806 controllers) are also supported if you say Y here.
8808 If you have a special controller (such as the CMS FC-10, FC-20,
8809 Mountain Mach-II, or any controller that is based on the Intel 82078
8810 FDC like the high speed controllers by Seagate and Exabyte and
8811 Iomega's "Ditto Dash") you must configure it by selecting the
8812 appropriate entries from the "Floppy tape controllers" sub-menu
8813 below and possibly modify the default values for the IRQ and DMA
8814 channel and the IO base in ftape's configuration menu.
8816 If you want to use your floppy tape drive on a PCI-bus based system,
8817 please read the file drivers/char/ftape/README.PCI.
8819 The ftape kernel driver is also available as a runtime loadable
8820 module ( = code which can be inserted in and removed from the
8821 running kernel whenever you want). If you want to compile it as a
8822 module, say M here and read Documentation/modules.txt. The module
8823 will be called ftape.o.
8825 Note that the Ftape-HOWTO is out of date (sorry) and documents the
8826 older version 2.08 of this software but still contains useful
8827 information. There is a web page with more recent documentation at
8828 http://www-math.math.rwth-aachen.de/~LBFM/claus/ftape/ . This page
8829 always contains the latest release of the ftape driver and useful
8830 information (backup software, ftape related patches and
8831 documentation, FAQ). (To browse the WWW, you need to have access to
8832 a machine on the Internet that has a program like lynx or netscape.)
8833 Note that the file system interface has changed quite a bit compared
8834 to previous versions of ftape. Please read Documentation/ftape.txt.
8836 The file system interface for ftape
8838 Normally, you want to say Y or M. DON'T say N here or you
8839 WON'T BE ABLE TO USE YOUR FLOPPY TAPE DRIVE.
8841 The ftape module itself no longer contains the routines necessary
8842 to interface with the kernel VFS layer (i.e. to actually write data
8843 to and read data from the tape drive). Instead the file system
8844 interface (i.e. the hardware independent part of the driver) has
8845 been moved to a separate module.
8847 If you say M zftape will be compiled as a runtime loadable
8848 module ( = code which can be inserted in and removed from the
8849 running kernel whenever you want). In this case you should read
8850 Documentation/modules.txt. The module will be called zftape.o.
8852 Regardless of whether you say Y or M here, an additional runtime
8853 loadable module called `zft-compressor.o' which contains code to
8854 support user transparent on-the-fly compression based on Ross
8855 William's lzrw3 algorithm will be produced. If you have enabled the
8856 kernel module loader (i.e. have said Y to "Kernel module loader
8857 support", above) then `zft-compressor.o' will be loaded
8858 automatically by zftape when needed.
8860 Despite its name, zftape does NOT use compression by default. The
8861 file Documentation/ftape.txt contains a short description of the
8862 most important changes in the file system interface compared to
8863 previous versions of ftape. The ftape home page
8864 http://www-math.math.rwth-aachen.de/~LBFM/claus/ftape/ contains
8865 further information (to browse the WWW, you need to have access to a
8866 machine on the Internet that has a program like lynx or netscape).
8868 IMPORTANT NOTE: zftape can read archives created by previous
8869 versions of ftape and provide file mark support (i.e. fast skipping
8870 between tape archives) but previous version of ftape will lack file
8871 mark support when reading archives produced by zftape.
8873 Default block size for zftape
8874 CONFIG_ZFT_DFLT_BLK_SZ
8875 If unsure leave this at its default value, i.e. 10240. Note that
8876 you specify only the default block size here. The block size can be
8877 changed at run time using the MTSETBLK tape operation with the
8878 MTIOCTOP ioctl (i.e. with "mt -f /dev/qft0 setblk #BLKSZ" from the
8879 shell command line).
8881 The probably most striking difference between zftape and previous
8882 versions of ftape is the fact that all data must be written or read
8883 in multiples of a fixed block size. The block size defaults to
8884 10240 which is what GNU tar uses. The values for the block size
8885 should be either 1 or multiples of 1024 up to a maximum value of
8886 63488 (i.e. 62 K). If you specify `1' then zftape's builtin
8887 compression will be disabled.
8889 Reasonable values are `10240' (GNU tar's default block size),
8890 `5120' (afio's default block size), `32768' (default block size some
8891 backup programs assume for SCSI tape drives) or `1' (no restriction
8892 on block size, but disables builtin compression).
8894 Number of DMA buffers
8895 CONFIG_FT_NR_BUFFERS
8896 Please leave this at `3' unless you REALLY know what you are doing.
8897 It is not necessary to change this value. Values below 3 make the
8898 proper use of ftape impossible, values greater than 3 are a waste of
8899 memory. You can change the amount of DMA memory used by ftape at
8900 runtime with "mt -f /dev/qft0 setdrvbuffer #NUMBUFFERS". Each buffer
8901 wastes 32 KB of memory. Please note that this memory cannot be
8904 Procfs entry for ftape
8906 Optional. Saying Y will result in creation of a directory
8907 `/proc/ftape' under the proc file system. The files can be viewed
8908 with your favorite pager (i.e. use "more /proc/ftape/history" or
8909 "less /proc/ftape/history" or simply "cat /proc/ftape/history"). The
8910 file will contain some status information about the inserted
8911 cartridge, the kernel driver, your tape drive, the floppy disk
8912 controller and the error history for the most recent use of the
8913 kernel driver. Saying Y will enlarge the size of the ftape driver
8914 by approximately 2 KB.
8916 WARNING: When compiling ftape as a module (i.e. saying M to
8917 "Floppy tape drive") it is dangerous to use ftape's proc file system
8918 interface. Accessing `/proc/ftape' while the module is unloaded will
8919 result in a kernel Oops. This cannot be fixed from inside ftape.
8921 Controlling the amount of debugging output of ftape
8922 CONFIG_FT_NORMAL_DEBUG
8923 This option controls the amount of debugging output the ftape driver
8924 is ABLE to produce; it does not increase or diminish the debugging
8925 level itself. If unsure, leave this at its default setting,
8926 i.e. choose "Normal".
8928 Ftape can print lots of debugging messages to the system console
8929 resp. kernel log files. Reducing the amount of possible debugging
8930 output reduces the size of the kernel module by some KB, so it might
8931 be a good idea to use "None" for emergency boot floppies.
8933 If you want to save memory then the following strategy is
8934 recommended: leave this option at its default setting "Normal" until
8935 you know that the driver works as expected, afterwards reconfigure
8936 the kernel, this time specifying "Reduced" or "None" and recompile
8937 and install the kernel as usual. Note that choosing "Excessive"
8938 debugging output does not increase the amount of debugging output
8939 printed to the console but only makes it possible to produce
8940 "Excessive" debugging output.
8942 Please read Documentation/ftape.txt for a short description
8943 how to control the amount of debugging output.
8945 The floppy drive controller for ftape
8947 Only change this setting if you have a special controller. If you
8948 didn't plug any add-on card into your computer system but just
8949 plugged the floppy tape cable into the already existing floppy drive
8950 controller then you don't want to change the default setting,
8951 i.e. choose "Standard".
8953 Choose "MACH-2" if you have a Mountain Mach-2 controller.
8954 Choose "FC-10/FC-20" if you have a Colorado FC-10 or FC-20
8956 Choose "Alt/82078" if you have another controller that is located at
8957 an IO base address different from the standard floppy drive
8958 controller's base address of `0x3f0', or uses an IRQ (interrupt)
8959 channel different from `6', or a DMA channel different from
8960 `2'. This is necessary for any controller card that is based on
8961 Intel's 82078 FDC such as Seagate's, Exabyte's and Iomega's "high
8964 If you choose something other than "Standard" then please make
8965 sure that the settings for the IO base address and the IRQ and DMA
8966 channel in the configuration menus below are correct. Use the manual
8967 of your tape drive to determine the correct settings!
8969 If you are already successfully using your tape drive with another
8970 operating system then you definitely should use the same settings
8971 for the IO base, the IRQ and DMA channel that have proven to work
8974 Note that this menu lets you specify only the default setting for
8975 the hardware setup. The hardware configuration can be changed at
8976 boot time (when ftape is compiled into the kernel, i.e. if you
8977 have said Y to "Floppy tape drive") or module load time (i.e. if you
8978 have said M to "Floppy tape drive").
8980 Please read also the file Documentation/ftape.txt which
8981 contains a short description of the parameters that can be set at
8982 boot or load time. If you want to use your floppy tape drive on a
8983 PCI-bus based system, please read the file
8984 drivers/char/ftape/README.PCI.
8986 IO base of the floppy disk controller used with Ftape
8988 You don't need to specify a value if the following default
8989 settings for the base IO address are correct:
8990 <<< MACH-2 : 0x1E0 >>>
8991 <<< FC-10/FC-20: 0x180 >>>
8992 <<< Secondary : 0x370 >>>
8993 Secondary refers to a secondary FDC controller like the "high speed"
8994 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
8995 Please make sure that the setting for the IO base address
8996 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
8997 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
8998 successfully using the tape drive with another operating system then
8999 you definitely should use the same settings for the IO base that has
9000 proven to work with that other OS.
9002 Note that this menu lets you specify only the default setting for
9003 the IO base. The hardware configuration can be changed at boot time
9004 (when ftape is compiled into the kernel, i.e. if you specified Y to
9005 "Floppy tape drive") or module load time (i.e. if you have said M to
9006 "Floppy tape drive").
9008 Please read also the file Documentation/ftape.txt which contains a
9009 short description of the parameters that can be set at boot or load
9012 IRQ channel for the floppy disk controller used with Ftape
9014 You don't need to specify a value if the following default
9015 settings for the interrupt channel are correct:
9017 <<< FC-10/FC-20: 9 >>>
9018 <<< Secondary : 6 >>>
9019 Secondary refers to secondary a FDC controller like the "high speed"
9020 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
9021 Please make sure that the setting for the IO base address
9022 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
9023 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
9024 successfully using the tape drive with another operating system then
9025 you definitely should use the same settings for the IO base that has
9026 proven to work with that other OS.
9028 Note that this menu lets you specify only the default setting for
9029 the IRQ channel. The hardware configuration can be changed at boot
9030 time (when ftape is compiled into the kernel, i.e. if you said Y to
9031 "Floppy tape drive") or module load time (i.e. if you said M to
9032 "Floppy tape drive").
9034 Please read also the file Documentation/ftape.txt which contains a
9035 short description of the parameters that can be set at boot or load
9038 DMA channel for the floppy disk controller used with Ftape
9040 You don't need to specify a value if the following default
9041 settings for the DMA channel are correct:
9043 <<< FC-10/FC-20: 3 >>>
9044 <<< Secondary : 2 >>>
9045 Secondary refers to a secondary FDC controller like the "high speed"
9046 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
9047 Please make sure that the setting for the IO base address
9048 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
9049 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
9050 successfully using the tape drive with another operating system then
9051 you definitely should use the same settings for the IO base that has
9052 proven to work with that other OS.
9054 Note that this menu lets you specify only the default setting for
9055 the DMA channel. The hardware configuration can be changed at boot
9056 time (when ftape is compiled into the kernel, i.e. if you said Y to
9057 "Floppy tape drive") or module load time (i.e. if you said M to
9058 "Floppy tape drive").
9060 Please read also the file Documentation/ftape.txt which contains a
9061 short description of the parameters that can be set at boot or load
9064 FDC FIFO Threshold before requesting DMA service
9066 Set the FIFO threshold of the FDC. If this is higher the DMA
9067 controller may serve the FDC after a higher latency time. If this is
9068 lower, fewer DMA transfers occur leading to less bus contention.
9069 You may try to tune this if ftape annoys you with "reduced data
9070 rate because of excessive overrun errors" messages. However, this
9071 doesn't seem to have too much effect.
9073 If unsure, don't touch the initial value, i.e. leave it at "8".
9075 FDC maximum data rate
9076 CONFIG_FT_FDC_MAX_RATE
9077 With some motherboard/FDC combinations ftape will not be able to
9078 run your FDC/tape drive combination at the highest available
9079 speed. If this is the case you'll encounter "reduced data rate
9080 because of excessive overrun errors" messages and lots of retries
9081 before ftape finally decides to reduce the data rate.
9083 In this case it might be desirable to tell ftape beforehand that
9084 it need not try to run the tape drive at the highest available
9085 speed. If unsure, leave this disabled, i.e. leave it at 2000
9088 MTRR control and configuration
9090 On Intel P6 family processors (Pentium Pro, Pentium II and later)
9091 the Memory Type Range Registers (MTRRs) may be used to control
9092 processor access to memory ranges. This is most useful when you have
9093 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
9094 allows bus write transfers to be combined into a larger transfer
9095 before bursting over the PCI/AGP bus. This can increase performance
9096 of image write operations 2.5 times or more. This option creates a
9097 /proc/mtrr file which may be used to manipulate your
9098 MTRRs. Typically the X server should use this. This should have a
9099 reasonably generic interface so that similar control registers on
9100 other processors can be easily supported.
9102 The Cyrix 6x86, 6x86MX and M II processors have Address Range
9103 Registers (ARRs) which provide a similar functionality to MTRRs. For
9104 these, the ARRs are used to emulate the MTRRs.
9106 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
9107 MTRRs. These are supported.
9109 The Centaur C6 (WinChip) has 8 MCRs, allowing write-combining. These
9112 Saying Y here also fixes a problem with buggy SMP BIOSes which only
9113 set the MTRRs for the boot CPU and not the secondary CPUs. This can
9114 lead to all sorts of problems.
9116 You can safely say Y even if your machine doesn't have MTRRs, you'll
9117 just add about 3k to your kernel.
9119 See Documentation/mtrr.txt for more information.
9121 Main CPU frequency, only for DEC alpha machine
9122 CONFIG_FT_ALPHA_CLOCK
9123 On some DEC Alpha machines the CPU clock frequency cannot be
9124 determined automatically, so you need to specify it here ONLY if
9125 running a DEC Alpha, otherwise this setting has no effect.
9127 Zilog serial support
9129 If you are asked this question, something is wrong with config scripts.
9130 Zilog serial driver is always enabled in sparc architecture.
9132 Double Talk PC internal speech card support
9134 This driver is for the DoubleTalk PC, a speech synthesizer
9135 manufactured by RC Systems (http://www.rcsys.com/). It is also
9136 called the `internal DoubleTalk'. If you want to compile this as a
9137 module ( = code which can be inserted in and removed from the
9138 running kernel whenever you want), say M here and read
9139 Documentation/modules.txt. The module will be called dtlk.o.
9141 Advanced Power Management
9143 APM is a BIOS specification for saving power using several different
9144 techniques. This is mostly useful for battery powered laptops with
9145 APM compliant BIOSes. If you say Y here, the system time will be
9146 reset after a USER RESUME operation, the /proc/apm device will
9147 provide battery status information, and user-space programs will
9148 receive notification of APM "events" (e.g., battery status change).
9150 Supporting software is available; for more information, read the
9151 Battery Powered Linux mini-HOWTO, available via FTP (user:
9152 anonymous) from ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini.
9154 This driver does not spin down disk drives (see the hdparm(8)
9155 manpage ("man 8 hdparm") for that), and it doesn't turn off
9156 VESA-compliant "green" monitors.
9158 This driver does not support the TI 4000M TravelMate and the ACER
9159 486/DX4/75 because they don't have compliant BIOSes. Many "green"
9160 desktop machines also don't have compliant BIOSes, and this driver
9161 will cause those machines to panic during the boot phase (typically,
9162 these machines are using a data segment of 0040, which is reserved
9163 for the Linux kernel).
9165 If you are running Linux on a laptop, you may also want to read the
9166 Linux Laptop home page on the WWW at
9167 http://www.cs.utexas.edu/users/kharker/linux-laptop/ (to browse the
9168 WWW, you need to have access to a machine on the Internet that has a
9169 program like lynx or netscape).
9171 Generally, if you don't have a battery in your machine, there isn't
9172 much point in using this driver and you should say N. If you get
9173 random kernel OOPSes or reboots that don't seem to be related to
9174 anything, try disabling/enabling this option (or disabling/enabling
9177 Some other things you should try when experiencing seemingly random,
9180 1) make sure that you have enough swap space and that it is
9182 2) pass the "no-hlt" option to the kernel
9183 3) switch on floating point emulation in the kernel and pass
9184 the "no387" option to the kernel
9185 4) pass the "floppy=nodma" option to the kernel
9186 5) pass the "mem=4M" option to the kernel (thereby disabling
9187 all but the first 4 MB of RAM)
9188 6) make sure that the CPU is not over clocked.
9189 7) read the sig11 FAQ at http://www.bitwizard.nl/sig11/
9190 8) disable the cache from your BIOS settings
9191 9) install a fan for the video card or exchange video RAM
9192 10) install a better fan for the CPU
9193 11) exchange RAM chips
9194 12) exchange the motherboard.
9197 CONFIG_APM_IGNORE_USER_SUSPEND
9198 This option will ignore USER SUSPEND requests. On machines with a
9199 compliant APM BIOS, you want to say N. However, on the NEC Versa M
9200 series notebooks, it is necessary to say Y because of a BIOS bug.
9202 Enable APM at boot time
9203 CONFIG_APM_DO_ENABLE
9204 Enable APM features at boot time. From page 36 of the APM BIOS
9205 specification: "When disabled, the APM BIOS does not automatically
9206 power manage devices, enter the Standby State, enter the Suspend
9207 State, or take power saving steps in response to CPU Idle calls."
9208 This driver will make CPU Idle calls when Linux is idle (unless this
9209 feature is turned off -- see "Do CPU IDLE calls", below). This
9210 should always save battery power, but more complicated APM features
9211 will be dependent on your BIOS implementation. You may need to turn
9212 this option off if your computer hangs at boot time when using APM
9213 support, or if it beeps continuously instead of suspending. Turn
9214 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
9215 T400CDT. This is off by default since most machines do fine without
9220 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
9221 On some machines, this can activate improved power savings, such as
9222 a slowed CPU clock rate, when the machine is idle. These idle calls
9223 are made after the idle loop has run for some length of time (e.g.,
9224 333 mS). On some machines, this will cause a hang at boot time or
9225 whenever the CPU becomes idle. (On machines with more than one CPU,
9226 this option does nothing.)
9228 Enable console blanking using APM
9229 CONFIG_APM_DISPLAY_BLANK
9230 Enable console blanking using the APM. Some laptops can use this to
9231 turn off the LCD backlight when the screen blanker of the Linux
9232 virtual console blanks the screen. Note that this is only used by
9233 the virtual console screen blanker, and won't turn off the backlight
9234 when using the X Window system. This also doesn't have anything to
9235 do with your VESA-compliant power-saving monitor. Further, this
9236 option doesn't work for all laptops -- it might not turn off your
9237 backlight at all, or it might print a lot of errors to the console,
9238 especially if you are using gpm.
9240 Power off on shutdown
9241 CONFIG_APM_POWER_OFF
9242 Enable the ability to power off the computer after the Linux kernel
9243 is halted. You will need software (e.g., a suitable version of the
9244 halt(8) command ("man 8 halt")) to cause the computer to power down.
9245 Recent versions of the sysvinit package available from
9246 ftp://metalab.unc.edu/pub/Linux/system/daemons/init/ (user:
9247 anonymous) contain support for this ("halt -p" shuts down Linux and
9248 powers off the computer, if executed from runlevel 0). As with the
9249 other APM options, this option may not work reliably with some APM
9250 BIOS implementations.
9252 Ignore multiple suspend/standby events
9253 CONFIG_APM_IGNORE_MULTIPLE_SUSPEND
9254 This option is necessary on the IBM Thinkpad 560, but should work on
9255 all other laptops. When the APM BIOS returns multiple suspend or
9256 standby events while one is already being processed they will be
9257 ignored. Without this the Thinkpad 560 has troubles with the user
9258 level daemon apmd, and with the PCMCIA package pcmcia-cs.
9260 Ignore multiple suspend/resume cycles
9261 CONFIG_APM_IGNORE_SUSPEND_BOUNCE
9262 This option is necessary on the Dell Inspiron 3200 and others, but
9263 should be safe for all other laptops. When enabled, a system suspend
9264 event that occurs within three seconds of a resume is ignored.
9265 Without this the Inspiron will shut itself off a few seconds after
9266 you open the lid, requiring you to press the power button to resume
9267 it a second time. Say Y.
9269 RTC stores time in GMT
9270 CONFIG_APM_RTC_IS_GMT
9271 Say Y here if your RTC (Real Time Clock a.k.a. hardware clock)
9272 stores the time in GMT (Greenwich Mean Time). Say N if your RTC
9275 It is in fact recommended to store GMT in your RTC, because then you
9276 don't have to worry about daylight savings time changes. The only
9277 reason not to use GMT in your RTC is if you also run a broken OS
9278 that doesn't understand GMT.
9280 Allow interrupts during APM BIOS calls
9281 CONFIG_APM_ALLOW_INTS
9282 Normally we disable external interrupts while we are making calls to
9283 the APM BIOS as a measure to lessen the effects of a badly behaving
9284 BIOS implementation. The BIOS should reenable interrupts if it
9285 needs to. Unfortunately, some BIOSes do not - especially those in
9286 many of the newer IBM Thinkpads. If you experience hangs when you
9287 suspend, try setting this to Y. Otherwise, say N.
9289 Watchdog Timer Support
9291 If you say Y here (and to one of the following options) and create a
9292 character special file /dev/watchdog with major number 10 and minor
9293 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
9294 subsequently opening the file and then failing to write to it for
9295 longer than 1 minute will result in rebooting the machine. This
9296 could be useful for a networked machine that needs to come back
9297 online as fast as possible after a lock-up. There's both a watchdog
9298 implementation entirely in software (which can sometimes fail to
9299 reboot the machine) and a driver for hardware watchdog boards, which
9300 are more robust and can also keep track of the temperature inside
9301 your computer. For details, read Documentation/watchdog.txt in the
9304 The watchdog is usually used together with the watchdog daemon
9305 which is available via FTP (user: anonymous) from
9306 ftp://tsx-11.mit.edu/pub/linux/sources/sbin/. This daemon can also
9307 monitor NFS connections and can reboot the machine when the process
9312 Disable watchdog shutdown on close
9313 CONFIG_WATCHDOG_NOWAYOUT
9314 The default watchdog behaviour (which you get if you say N here) is
9315 to stop the timer if the process managing it closes the file
9316 /dev/watchdog. It's always remotely possible that this process might
9317 get killed. If you say Y here, the watchdog cannot be stopped once
9318 it has been started.
9322 If you have a WDT500P or WDT501P watchdog board, say Y here,
9323 otherwise N. It is not possible to probe for this board, which means
9324 that you have to set the IO port and IRQ it uses in the kernel
9325 source at the top of drivers/char/wdt.c.
9327 If you want to compile this as a module ( = code which can be
9328 inserted in and removed from the running kernel whenever you want),
9329 say M here and read Documentation/modules.txt. The module will be
9334 Saying Y here and creating a character special file /dev/temperature
9335 with major number 10 and minor number 131 ("man mknod") will give
9336 you a thermometer inside your computer: reading from
9337 /dev/temperature yields one byte, the temperature in degrees
9338 Fahrenheit. This works only if you have a WDT501P watchdog board
9343 Enable the Fan Tachometer on the WDT501. Only do this if you have a
9344 fan tachometer actually set up.
9347 CONFIG_SOFT_WATCHDOG
9348 A software monitoring watchdog. This will fail to reboot your system
9349 from some situations that the hardware watchdog will recover
9350 from. Equally it's a lot cheaper to install.
9352 This driver is also available as a module ( = code which can be
9353 inserted in and removed from the running kernel whenever you want).
9354 If you want to compile it as a module, say M here and read
9355 Documentation/modules.txt. The module will be called softdog.o.
9357 Berkshire Products PC Watchdog
9359 This is the driver for the Berkshire Products PC Watchdog card.
9360 This card simply watches your kernel to make sure it doesn't freeze,
9361 and if it does, it reboots your computer after a certain amount of
9362 time. This driver is like the WDT501 driver but for different
9363 hardware. Please read Documentation/pcwd-watchdog.txt. The PC
9364 watchdog cards can be ordered from http://www.berkprod.com. Some
9365 example rc.local files are available from ftp://ftp.bitgate.com.
9367 This driver is also available as a module ( = code which can be
9368 inserted in and removed from the running kernel whenever you want).
9369 The module is called pcwd.o. If you want to compile it as a module,
9370 say M here and read Documentation/modules.txt.
9372 Most people will say N.
9374 Acquire SBC Watchdog Timer
9376 This is the driver for the hardware watchdog on the PSC-6x86 Single
9377 Board Computer produced by Acquire Inc (and others). This watchdog
9378 simply watches your kernel to make sure it doesn't freeze, and if
9379 it does, it reboots your computer after a certain amount of time.
9381 This driver is like the WDT501 driver but for different hardware.
9382 This driver is also available as a module ( = code which can be
9383 inserted in and removed from the running kernel whenever you want).
9384 The module is called pscwdt.o. If you want to compile it as a
9385 module, say M here and read Documentation/modules.txt. Most people
9388 Enhanced Real Time Clock Support
9390 If you say Y here and create a character special file /dev/rtc with
9391 major number 10 and minor number 135 using mknod ("man mknod"), you
9392 will get access to the real time clock built into your computer.
9393 Every PC has such a clock built in. It can be used to generate
9394 signals from as low as 1Hz up to 8192Hz, and can also be used as a
9395 24 hour alarm. It reports status information via the file /proc/rtc
9396 and its behaviour is set by various ioctls on /dev/rtc.
9398 If you run Linux on a multiprocessor machine and said Y to
9399 "Symmetric Multi Processing" above, you should say Y here to read
9400 and set the RTC clock in an SMP compatible fashion.
9402 If you think you have a use for such a device (such as periodic data
9403 sampling), then say Y here, and read Documentation/rtc.txt for
9406 Tadpole ANA H8 Support
9408 The Hitachi H8/337 is a microcontroller used to deal with the power
9409 and thermal environment. If you say Y here, you will be able to
9410 communicate with it via a character special device.
9416 If you say Y here and create a character special file /dev/nvram
9417 with major number 10 and minor number 144 using mknod ("man mknod"),
9418 you get read and write access to the 50 bytes of non-volatile memory
9419 in the real time clock (RTC), which is contained in every PC and
9422 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
9423 on Ataris. /dev/nvram may be used to view settings there, or to
9424 change them (with some utility). It could also be used to frequently
9425 save a few bits of very important data that may not be lost over
9426 power-off and for which writing to disk is too insecure. Note
9427 however that most NVRAM space in a PC belongs to the BIOS and you
9428 should NEVER idly tamper with it. See Ralf Brown's interrupt list
9429 for a guide to the use of CMOS bytes by your BIOS.
9431 On Atari machines, /dev/nvram is always configured and does not need
9434 This driver is also available as a module ( = code which can be
9435 inserted in and removed from the running kernel whenever you want).
9436 The module will be called nvram.o. If you want to compile it as a
9437 module, say M here and read Documentation/modules.txt.
9439 Atomwide Serial Support
9440 CONFIG_ATOMWIDE_SERIAL
9441 If you have an Atomwide Serial card for an Acorn system, say Y to
9442 this option. The driver can handle 1, 2, or 3 port cards.
9445 The Serial Port Dual Serial Port
9446 CONFIG_DUALSP_SERIAL
9447 If you have the Serial Port's dual serial card for an Acorn system,
9448 say Y to this option. If unsure, say N
9452 If you have a joystick, you can say Y here to enable generic
9453 joystick support. You will also need to say Y or M to at least one
9454 of the hardware specific joystick drivers. This will make the
9455 joysticks available as /dev/jsX devices. Please read the file
9456 Documentation/joystick.txt which contains more information and the
9457 location of the joystick package that you'll need.
9459 This driver is also available as a module ( = code which can be
9460 inserted in and removed from the running kernel whenever you want).
9461 The module will be called joystick.o. If you want to compile it as a
9462 module, say M here and read Documentation/modules.txt.
9464 Classic PC analog joysticks and gamepads
9466 Say Y here if you have an analog joystick or gamepad that connects
9467 to the PC gameport. This supports many different types, including
9468 joysticks with throttle control, with rudders, or with extensions
9469 like additional hats and buttons compatible with CH Flightstick Pro,
9470 ThrustMaster FCS or 6 and 8 button gamepads. For more information on
9471 how to use the driver please read Documentation/joystick.txt
9473 FPGaming and MadCatz A3D controllers
9475 Say Y here if you have an FPGaming Assasin 3D, MadCatz Panther or
9476 MadCatz Panther XL. For more information on how to use the driver
9477 please read Documentation/joystick.txt
9479 Gravis GrIP joysticks and gamepads
9481 Say Y here if you have a Gravis GamePad Pro, Gravis Xterminator or
9482 Gravis Blackhawk Digital. For more information on how to use the
9483 driver please read Documentation/joystick.txt
9485 PDPI Lightning 4 gamecards
9486 CONFIG_JOY_LIGHTNING
9487 Say Y here if you have a PDPI Lightning 4 gamecard and an analog
9488 joystick or gamepad connected to it. For more information on how to
9489 use the driver please read Documentation/joystick.txt
9491 Logitech Digital joysticks and gamepads
9493 Say Y here if you have a Logitech WingMan Extreme Digital,
9494 Logitech ThunderPad Digital or Logitech CyberMan 2. For more
9495 information on how to use the driver please read
9496 Documentation/joystick.txt
9498 Microsoft SideWinder, Genius Digital joysticks and gamepads
9499 CONFIG_JOY_SIDEWINDER
9500 Say Y here if you have a Microsoft SideWinder 3d Pro, Microsoft
9501 SideWinder Precision Pro, Microsoft SideWinder Force Feedback Pro,
9502 Microsoft Sidewinder GamePad or Genius Flight2000 F-23 Digital. For
9503 more information on how to use the driver please read
9504 Documentation/joystick.txt
9506 ThrustMaster DirectConnect joysticks and gamepads
9507 CONFIG_JOY_THRUSTMASTER
9508 Say Y here if you have a ThrustMaster Millenium 3D Inceptor or a
9509 ThrustMaster 3D Rage Pad. For more information on how to use the
9510 driver please read Documentation/joystick.txt
9512 NES, SNES, PSX, Multisystem joysticks and gamepads
9514 Say Y here if you have a Nintendo Entertainment System gamepad,
9515 Super Nintendo Entertainment System gamepad, Sony PlayStation
9516 gamepad or a Multisystem -- Atari, Amiga, Commodore, Amstrad CPC
9517 joystick. For more information on how to use the driver please read
9518 Documentation/joystick.txt and Documentation/joystick-parport.txt
9520 Sega, Multisystem joysticks and gamepads
9522 Say Y here if you have a Sega Master System gamepad, Sega Genesis
9523 gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga,
9524 Commodore, Amstrad CPC joystick. For more information on how to use
9525 the driver please read Documentation/joystick.txt and
9526 Documentation/joystick-parport.txt
9528 TurboGraFX Multisystem joystick interface
9529 CONFIG_JOY_TURBOGRAFX
9530 Say Y here if you have the TurboGraFX interface by Steffen Schwenke,
9531 and want to use it with Multiststem -- Atari, Amiga, Commodore,
9532 Amstrad CPC joystick. For more information on how to use the driver
9533 please read Documentation/joystick.txt and
9534 Documentation/joystick-parport.txt
9538 Say Y here if you have an Amiga with a digital joystick connected
9539 to it. For more information on how to use the driver please read
9540 Documentation/joystick.txt
9542 Atomwide Serial Support
9543 CONFIG_ATOMWIDE_SERIAL
9544 If you have an Atomwide Serial card for an Acorn system, say Y to
9545 this option. The driver can handle 1, 2, or 3 port cards.
9548 The Serial Port Dual Serial Port
9549 CONFIG_DUALSP_SERIAL
9550 If you have the Serial Port's dual serial card for an Acorn system,
9551 say Y to this option. If unsure, say N
9555 If you enable this driver and create a character device node
9556 /dev/nwbutton with major and minor numbers 10 and 158 ("man mknod"),
9557 then every time the orange button is pressed a number of times, the
9558 number of times the button was pressed will be written to that device.
9559 This is most useful for applications, as yet unwritten, which perform
9560 actions based on how many times the button is pressed in a row.
9561 Do not hold the button down for too long, as the driver does not alter
9562 the behaviour of the hardware reset circuitry attached to the button;
9563 it will still execute a hard reset if the button is held down for
9564 longer than approximately five seconds.
9565 This driver is also available as a module ( = code which can be
9566 inserted in and removed from the running kernel whenever you want).
9567 If you want to compile it as a module, say M here and read
9568 Documentation/modules.txt. The module will be called nwbutton.o.
9569 Most people will answer Y to this question and "Reboot Using Button"
9570 below to be able to initiate a system shutdown from the button.
9573 CONFIG_NWBUTTON_REBOOT
9574 If you enable this option, then you will be able to initiate a system
9575 shutdown and reboot by pressing the orange button a number of times.
9576 The number of presses to initiate the shutdown is two by default, but
9577 this can be altered by modifying the value of NUM_PRESSES_REBOOT in
9578 nwbutton.h and recompiling the driver or, if you compile the driver as
9579 a module, you can specify the number of presses at load time with
9580 "insmod button reboot_count=<something>".
9584 If you have a sound card in your computer, i.e. if it can say more
9585 than an occasional beep, say Y. Be sure to have all the information
9586 about your sound card and its configuration down (I/O port,
9587 interrupt and DMA channel), because you will be asked for it.
9589 You want to read the Sound-HOWTO, available via FTP (user:
9590 anonymous) from ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. General
9591 information about the modular sound system is contained in the files
9592 Documentation/sound/Introduction. The file
9593 Documentation/sound/README.OSS contains some slightly outdated but
9594 still useful information as well.
9596 If you have a PnP sound card and you want to configure it at boot
9597 time using the ISA PnP tools (read
9598 http://www.roestock.demon.co.uk/isapnptools/ (to browse the WWW, you
9599 need to have access to a machine on the Internet that has a program
9600 like lynx or netscape)), then you need to compile the sound card
9601 support as a module ( = code which can be inserted in and removed
9602 from the running kernel whenever you want) and load that module
9603 after the PnP configuration is finished. To do this, say M here and
9604 read Documentation/modules.txt as well as
9605 Documentation/sound/README.modules; the module will be called
9608 I'm told that even without a sound card, you can make your computer
9609 say more than an occasional beep, by programming the PC speaker.
9610 Kernel patches and supporting utilities to do that are in the pcsp
9611 package, available at http://www.imladris.demon.co.uk/pcsp/.
9615 OSS is the Open Sound System suite of sound card drivers. They make
9616 sound programming easier since they provide a common API. Say Y or M
9617 here (the module will be called sound.o) if you haven't found a
9618 driver for your sound card above, then pick your driver from the
9621 Persistent DMA buffers
9623 Linux can often have problems allocating DMA buffers for ISA sound
9624 cards on machines with more than 16MB of RAM. This is because ISA
9625 DMA buffers must exist below the 16MB boundary and it is quite
9626 possible that a large enough free block in this region cannot be
9627 found after the machine has been running for a while. If you say Y
9628 here the DMA buffers (64Kb) will be allocated at boot time and kept
9629 until the shutdown. This option is only useful if you said Y to
9630 "OSS sound modules", above. If you said M to "OSS sound modules"
9631 then you can get the persistent DMA buffer functionality by passing
9632 the command-line argument "dmabuf=1" to the sound.o module.
9634 Say Y unless you have 16MB or less RAM or a PCI sound card.
9636 Support for Aztech Sound Galaxy (non-PnP) cards
9637 CONFIG_SOUND_SGALAXY
9638 This module initializes the older non Plug and Play sound galaxy
9639 cards from Aztech. It supports the Waverider Pro 32 - 3D and the
9640 Galaxy Washington 16.
9642 Support for AD1816(A) based cards (EXPERIMENTAL)
9644 Say M here if you have a sound card based on the Analog Devices
9647 NOTE: This driver is still EXPERIMENTAL.
9648 See Documentation/sound/AD1816 for further information.
9650 Yamaha OPL3-SA1 audio controller
9651 CONFIG_SOUND_OPL3SA1
9652 Say Y or M if you have a Yamaha OPL3-SA1 sound chip, which is
9653 usually built into motherboards. Read Documentation/sound/OPL3-SA
9656 ProAudioSpectrum 16 support
9658 Answer Y only if you have a Pro Audio Spectrum 16, ProAudio Studio
9659 16 or Logitech SoundMan 16 sound card. Don't answer Y if you have
9660 some other card made by Media Vision or Logitech since they are not
9663 100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support
9665 Answer Y if you have an original Sound Blaster card made by Creative
9666 Labs or a 100% hardware compatible clone (like the Thunderboard or
9667 SM Games). For an unknown card you may answer Y if the card claims
9668 to be Sound Blaster-compatible.
9670 Please read the file Documentation/sound/Soundblaster.
9672 You should also say Y here for cards based on the Avance Logic
9673 ALS-007 chip (read Documentation/sound/ALS007) and for cards based
9674 on ESS chips (read Documentation/sound/ESS1868 and
9675 Documentation/sound/ESS). If you have an SB AWE 32 or SB AWE 64, say
9676 Y here and also to "Additional lowlevel drivers" and to "SB32/AWE
9677 support" below and read Documentation/sound/INSTALL.awe. If you have
9678 an IBM Mwave card, say Y here and read Documentation/sound/mwave.
9680 You can say M here to compile this driver as a module; the module is
9683 Generic OPL2/OPL3 FM synthesizer support
9685 Answer Y if your card has a FM chip made by Yamaha (OPL2/OPL3/OPL4).
9686 Answering Y is usually a safe and recommended choice, however some
9687 cards may have software (TSR) FM emulation. Enabling FM support with
9688 these cards may cause trouble (I don't currently know of any such
9691 Please read the file Documentation/sound/OPL3 if your card has an
9697 #Loopback MIDI device support
9700 ### somebody please fill this in.
9703 Gravis Ultrasound support
9705 Say Y here for any type of Gravis Ultrasound card, including
9706 the GUS or GUS MAX. See also Documentation/sound/ultrasound for
9707 more information on configuring this card with modules.
9709 MPU-401 support (NOT for SB16)
9711 Be careful with this question. The MPU401 interface is supported by
9712 all sound cards. However, some natively supported cards have their
9713 own driver for MPU401. Enabling this MPU401 option with these cards
9714 will cause a conflict. Also, enabling MPU401 on a system that
9715 doesn't really have a MPU401 could cause some trouble. If your card
9716 was in the list of supported cards, look at the card specific
9717 instructions in the drivers/sound/Readme.cards file. It's safe to
9718 answer Y if you have a true MPU401 MIDI interface card.
9721 CONFIG_SOUND_UART6850
9722 This option enables support for MIDI interfaces based on the 6850
9723 UART chip. This interface is rarely found on sound cards. It's safe
9724 to answer N to this question.
9728 Say Y here for ARM systems with the VIDC video controller and 16-bit
9729 Linear sound DACs. If unsure, say N.
9731 PSS (AD1848, ADSP-2115, ESC614) support
9733 Answer Y or M if you have an Orchid SW32, Cardinal DSP16, Beethoven
9734 ADSP-16 or some other card based on the PSS chipset (AD1848 codec +
9735 ADSP-2115 DSP chip + Echo ESC614 ASIC CHIP). For more information on
9736 how to compile it into the kernel or as a module see the file
9737 Documentation/sound/PSS.
9739 Enable PSS mixer (Beethoven ADSP-16 and other compatible)
9741 Answer Y for Beethoven ADSP-16. You may try to say Y also for other
9742 cards if they have master volume, bass, treble, and you can't
9743 control it under Linux. If you answer N for Beethoven ADSP-16, you
9744 can't control master volume, bass, treble and synth volume.
9746 If you said M to "PSS support" above, you may enable or disable this
9747 PSS mixer with the module parameter pss_mixer. For more information
9748 see the file Documentation/sound/PSS.
9750 Have DSPxxx.LD firmware file
9751 CONFIG_PSS_HAVE_BOOT
9752 If you have the DSPxxx.LD file or SYNTH.LD file for you card, say Y
9753 to include this file. Without this file the synth device (OPL) may
9756 Full pathname of DSPxxx.LD firmware file
9757 CONFIG_PSS_BOOT_FILE
9758 Enter the full pathname of your DSPxxx.LD file or SYNTH.LD file,
9761 16 bit sampling option of GUS (_NOT_ GUS MAX)
9763 Answer Y if you have installed the 16 bit sampling daughtercard on
9764 your GUS. Answer N if you have a GUS MAX, since saying Y here
9765 disables GUS MAX support.
9769 Answer Y only if you have a Gravis Ultrasound MAX.
9771 Microsoft Sound System support
9773 Again think carefully before answering Y to this question. It's safe
9774 to answer Y if you have the original Windows Sound System card made
9775 by Microsoft or Aztech SG 16 Pro (or NX16 Pro). Also you may say Y
9776 in case your card is NOT among these:
9778 ATI Stereo F/X, AdLib, Audio Excell DSP16, Cardinal DSP16,
9779 Ensoniq SoundScape (and compatibles made by Reveal and Spea),
9780 Gravis Ultrasound, Gravis Ultrasound ACE, Gravis Ultrasound Max,
9781 Gravis Ultrasound with 16 bit option, Logitech Sound Man 16,
9782 Logitech SoundMan Games, Logitech SoundMan Wave, MAD16 Pro (OPTi
9783 82C929), Media Vision Jazz16, MediaTriX AudioTriX Pro, Microsoft
9784 Windows Sound System (MSS/WSS), Mozart (OAK OTI-601), Orchid
9785 SW32, Personal Sound System (PSS), Pro Audio Spectrum 16, Pro
9786 Audio Studio 16, Pro Sonic 16, Roland MPU-401 MIDI interface,
9787 Sound Blaster 1.0, Sound Blaster 16, Sound Blaster 16ASP, Sound
9788 Blaster 2.0, Sound Blaster AWE32, Sound Blaster Pro, TI TM4000M
9789 notebook, ThunderBoard, Turtle Beach Tropez, Yamaha FM
9790 synthesizers (OPL2, OPL3 and OPL4), 6850 UART MIDI Interface.
9792 For cards having native support in VoxWare, consult the card
9793 specific instructions in drivers/sound/Readme.cards. Some drivers
9794 have their own MSS support and saying Y to this option will cause a
9797 Ensoniq Soundscape support
9799 Answer Y if you have a sound card based on the Ensoniq SoundScape
9800 chipset. Such cards are being manufactured at least by Ensoniq, Spea
9801 and Reveal (Reveal makes also other cards).
9803 MediaTriX AudioTriX Pro support
9805 Answer Y if you have the AudioTriX Pro sound card manufactured
9808 Have TRXPRO.HEX firmware file
9809 CONFIG_TRIX_HAVE_BOOT
9810 The MediaTrix AudioTrix Pro has an on-board microcontroller which
9811 needs to be initialized by downloading the code from the file
9812 TRXPRO.HEX in the DOS driver directory. If you don't have the
9813 TRXPRO.HEX file handy you may skip this step. However, the SB and
9814 MPU-401 modes of AudioTrix Pro will not work without this file!
9816 Full pathname of TRXPRO.HEX firmware file
9817 CONFIG_TRIX_BOOT_FILE
9818 Enter the full pathname of your TRXPRO.HEX file, starting from /.
9820 Support for OPTi MAD16 and/or Mozart based cards
9822 Answer Y if your card has a Mozart (OAK OTI-601) or MAD16 (OPTi
9823 82C928 or 82C929 or 82C931) audio interface chip. For the 82C931,
9824 please read drivers/sound/README.C931. These chips are currently
9825 quite common so it's possible that many no-name cards have one of
9826 them. In addition the MAD16 chip is used in some cards made by known
9827 manufacturers such as Turtle Beach (Tropez), Reveal (some models)
9828 and Diamond (latest ones). Note however that the Tropez sound cards
9829 have their own driver; if you have one of those, say N here and Y or
9830 M to "Full support for Turtle Beach WaveFront", below.
9832 See also Documentation/sound/Opti and Documentation/sound/MAD16 for
9833 more information on setting these cards up as modules.
9835 Full support for Turtle Beach WaveFront synth/sound cards
9836 CONFIG_SOUND_WAVEFRONT
9837 Answer Y or M if you have a Tropez Plus, Tropez or Maui sound card
9838 and read the files Documentation/sound/Wavefront and
9839 Documentation/sound/Tropez+.
9841 Support MIDI in older MAD16 based cards (requires SB)
9842 CONFIG_MAD16_OLDCARD
9843 Answer Y (or M) if you have an older card based on the C928 or
9844 Mozart chipset and you want to have MIDI support. If you enable this
9845 option you also need to enable support for Sound Blaster.
9847 Support for Crystal CS4232 based (PnP) cards
9849 Say Y here if you have a card based on the Crystal CS4232 chip set,
9850 which uses its own Plug and Play protocol.
9852 See Documentation/sound/CS4232 for more information on configuring
9855 Support for Yamaha OPL3-SA2, SA3, and SAx based PnP cards
9856 CONFIG_SOUND_OPL3SA2
9857 Say Y or M if you have a card based on one of these Yamaha
9858 sound chipsets. Read Documentation/sound/OPL3-SA2 for more
9859 information on configuring these cards.
9861 Support for Turtle Beach Wave Front (Maui, Tropez) synthesizers
9863 Say Y here if you have a Turtle Beach Wave Front, Maui, or Tropez
9866 Have OSWF.MOT firmware file
9867 CONFIG_MAUI_HAVE_BOOT
9868 Turtle Beach Maui and Tropez sound cards have a microcontroller
9869 which needs to be initialized prior to use. OSWF.MOT is a file
9870 distributed with the card's DOS/Windows drivers. Answer Y if you
9873 Full pathname of OSWF.MOT firmware file
9874 CONFIG_MAUI_BOOT_FILE
9875 Enter the full pathname of your OSWF.MOT file, starting from /.
9877 Support for Turtle Beach MultiSound Classic, Tahiti, Monterey
9878 CONFIG_SOUND_MSNDCLAS
9879 Say M here if you have a Turtle Beach MultiSound Classic, Tahiti or
9880 Monterey (not for the Pinnacle or Fiji).
9882 See Documentation/sound/MultiSound for important information about
9885 Full pathname of MSNDINIT.BIN firmware file
9886 CONFIG_MSNDCLAS_INIT_FILE
9887 The MultiSound cards have two firmware files which are required for
9888 operation, and are not currently included. These files can be
9889 obtained from Turtle Beach. See Documentation/sound/MultiSound for
9890 information on how to obtain this.
9892 Full pathname of MSNDPERM.BIN firmware file
9893 CONFIG_MSNDCLAS_PERM_FILE
9894 The MultiSound cards have two firmware files which are required for
9895 operation, and are not currently included. These files can be
9896 obtained from Turtle Beach. See Documentation/sound/MultiSound for
9897 information on how to obtain this.
9899 Support for Turtle Beach MultiSound Pinnacle, Fiji
9900 CONFIG_SOUND_MSNDPIN
9901 Say M here if you have a Turtle Beach MultiSound Pinnacle or Fiji.
9902 See Documentation/sound/MultiSound for important information about
9905 Full pathname of PNDSPINI.BIN firmware file
9906 CONFIG_MSNDPIN_INIT_FILE
9907 The MultiSound cards have two firmware files which are required for
9908 operation, and are not currently included. These files can be
9909 obtained from Turtle Beach. See Documentation/sound/MultiSound for
9910 information on how to obtain this.
9912 Full pathname of PNDSPERM.BIN firmware file
9913 CONFIG_MSNDPIN_PERM_FILE
9914 The MultiSound cards have two firmware files which are required for
9915 operation, and are not currently included. These files can be
9916 obtained from Turtle Beach. See Documentation/sound/MultiSound for
9917 information on how to obtain this.
9919 MSND Pinnacle have S/PDIF I/O
9920 CONFIG_MSNDPIN_DIGITAL
9921 If you have the S/PDIF daughter board for the Pinnacle or Fiji,
9922 answer Y here; otherwise, say N. If you have this, you will be able
9923 to play and record from the S/PDIF port (digital signal). See
9924 Documentation/sound/MultiSound for information on how to make use of
9927 MSND Pinnacle non-PnP Mode
9928 CONFIG_MSNDPIN_NONPNP
9929 The Pinnacle and Fiji card resources can be configured either with
9930 PnP, or through a configuration port. Say Y here if your card is NOT
9931 in PnP mode. For the Pinnacle, configuration in non-PnP mode allows
9932 use of the IDE and joystick peripherals on the card as well; these
9933 do not show up when the card is in PnP mode. Specifying zero for any
9934 resource of a device will disable the device. If you are running the
9935 card in PnP mode, you must say N here and use isapnptools to
9936 configure the card's resources.
9938 MSND Pinnacle config port
9940 This is the port which the Pinnacle and Fiji uses to configure the
9941 card's resources when not in PnP mode. If your card is in PnP mode,
9942 then be sure to say N to the previous option, "MSND Pinnacle Non-PnP
9945 MSND buffer size (kB)
9946 CONFIG_MSND_FIFOSIZE
9947 Configures the size of each audio buffer, in kilobytes, for
9948 recording and playing in the MultiSound drivers (both the Classic
9949 and Pinnacle). Larger values reduce the chance of data overruns at
9950 the expense of overall latency. If unsure, use the default.
9952 /dev/dsp and /dev/audio support
9954 If you say Y here, you will get the /dev/dsp and /dev/audio devices;
9955 these are the analog-digital and digital-analog converter devices
9956 and are very useful, so say Y.
9958 MIDI interface support
9960 Answering N disables /dev/midixx devices and access to any MIDI
9961 ports using /dev/sequencer and /dev/music. This option also affects
9962 any MPU401 and/or General MIDI compatible devices. Answer Y.
9964 FM synthesizer (YM3812/OPL-3) support
9966 Answer Y here, unless you know you will not need the option.
9970 This is support for the sound cards on Sun workstations. The code
9971 does not exist yet, so you might as well say N here.
9973 Additional low level drivers
9974 CONFIG_LOWLEVEL_SOUND
9975 If you need additional low level sound drivers which have not yet
9976 appeared, say Y. The answer to this question does not directly
9977 affect the kernel; saying Y will simply cause this configure script
9978 to present you with more options. If unsure, say Y.
9980 ACI mixer (miroPCM12/PCM20)
9982 ACI (Audio Command Interface) is a protocol used to communicate with
9983 the microcontroller on some sound cards produced by miro, e.g. the
9984 miroSOUND PCM12 and PCM20. The main function of the ACI is to
9985 control the mixer and to get a product identification.
9987 This Voxware ACI driver currently only supports the ACI functions on
9988 the miroSOUND PCM12 and PCM20 cards. On the PCM20, ACI also controls
9989 the radio tuner. This is supported in the video4linux
9990 radio-miropcm20 driver.
9994 Say Y here if you have a Sound Blaster SB32, AWE32-PnP, SB AWE64 or
9995 similar sound card. See Documentation/sound/README.awe,
9996 Documentation/sound/AWE32 and the Soundblaster-AWE mini-HOWTO,
9997 available via FTP (user: anonymous) from
9998 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini for more info.
10000 Gallant's Audio Excel DSP 16 support (SC-6000 and SC-6600)
10002 Answer Y if you have a Gallant's Audio Excel DSP 16 card. This
10003 driver supports Audio Excel DSP 16 but not the III nor PnP versions
10006 The Gallant's Audio Excel DSP 16 card can emulate either an SBPro or
10007 a Microsoft Sound System card, so you should have said Y to either
10008 "100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support"
10009 or "Microsoft Sound System support", above, and you need to answer
10010 the "MSS emulation" and "SBPro emulation" questions below
10011 accordingly. You should say Y to one and only one of these two
10014 Read the drivers/sound/lowlevel/README.aedsp16 file and the head of
10015 drivers/sound/lowlevel/aedsp16.c as well as
10016 Documentation/sound/AudioExcelDSP16 to get more information about
10017 this driver and its configuration.
10019 I/O base for Audio Excel DSP 16
10020 CONFIG_AEDSP16_BASE
10021 This is the base I/O address of the Audio Excel DSP 16 card. It must
10022 be 220 or 240. If you compiled aedsp16.o as a module you can specify
10023 this parameter as 'io=0xNNN'.
10025 Audio Excel DSP 16 (SBPro emulation)
10026 CONFIG_AEDSP16_SBPRO
10027 Answer Y if you want your audio card to emulate Sound Blaster Pro.
10028 You should then say Y to "100% Sound Blaster compatibles
10029 (SB16/32/64, ESS, Jazz16) support" and N to "Audio Excel DSP 16 (MSS
10032 Audio Excel DSP 16 IRQ
10033 CONFIG_AEDSP16_SB_IRQ
10034 This is the IRQ of the Audio Excel DSP 16 card. It must be 5, 7, 9,
10035 10 or 11. If you compiled aedsp16.o as a module you can specify
10036 this parameter as 'irq=NN'.
10038 Audio Excel DSP 16 DMA
10039 CONFIG_AEDSP16_SB_DMA
10040 This is the IRQ of the Audio Excel DSP 16 card. It must be 0, 1 or 3.
10041 If you compiled aedsp16.o as a module you can specify this parameter
10044 Audio Excel DSP 16 (MSS emulation)
10046 Answer Y if you want your audio card to emulate Microsoft Sound
10047 System. You should then say Y to "Microsoft Sound System support"
10048 and say N to "Audio Excel DSP 16 (SBPro emulation)".
10050 Audio Excel DSP 16 IRQ
10051 CONFIG_AEDSP16_MSS_IRQ
10052 This is the IRQ of the Audio Excel DSP 16 card. It must be 5, 7, 9,
10053 10 or 11. If you compiled aedsp16.o as a module you can specify
10054 this parameter as 'irq=NN'.
10056 Audio Excel DSP 16 DMA
10057 CONFIG_AEDSP16_MSS_DMA
10058 This is the IRQ of the Audio Excel DSP 16 card. It must be 0, 1
10059 or 3. If you compiled aedsp16.o as a module you can specify this
10060 parameter as 'dma=NN'.
10062 SC-6600 based audio cards (new Audio Excel DSP 16)
10064 The SC6600 is the new version of DSP mounted on the Audio Excel DSP
10065 16 cards. Find in the manual the FCC ID of your audio card and
10066 answer Y if you have an SC6600 DSP.
10068 SC-6600 Joystick Interface
10070 Say Y here in order to use the joystick interface of the Audio Excel
10073 SC-6600 CDROM Interface
10074 CONFIG_SC6600_CDROM
10075 This is used to activate the the CDROM interface of the Audio Excel
10076 DSP 16 card. Enter: 0 for Sony, 1 for Panasonic, 2 for IDE, 4 for no
10079 Audio Excel DSP 16 (MPU401 emulation)
10080 CONFIG_AEDSP16_MPU401
10081 Answer Y if you want your audio card to emulate the MPU-401 midi
10082 interface. You should then also say Y to "MPU-401 support".
10084 Note that the I/O base for MPU-401 support of aedsp16 is the same
10085 you have selected for "MPU-401 support". If you are using this
10086 driver as a module you have to specify the MPU I/O base address with
10087 the parameter 'mpu_base=0xNNN'.
10089 MPU401 IRQ for Audio Excel DSP 16
10090 CONFIG_AEDSP16_MPU_IRQ
10091 This is the IRQ of the MPU-401 emulation of your Audio Excel DSP 16
10092 card. It must be 5, 7, 9, 10 or 0 (to disable MPU-401 interface). If
10093 you compiled aedsp16.o as a module you can specify this parameter as
10096 Ensoniq ES1370 based PCI sound cards
10097 CONFIG_SOUND_ES1370
10098 Say Y or M if you have a PCI sound card utilizing the Ensoniq
10099 ES1370 chipset, such as Ensoniq's AudioPCI (non-97). To find
10100 out if your sound card uses an ES1370 without removing your
10101 computer's cover, use lspci -n and look for the PCI ID
10102 1274:5000. Since Ensoniq was bought by Creative Labs,
10103 Sound Blaster 64/PCI models are either ES1370 or ES1371 based.
10104 This driver differs slightly from OSS/Free, so PLEASE READ
10105 Documentation/sound/es1370.
10107 Joystick support at boot time
10108 CONFIG_SOUND_ES1370_JOYPORT_BOOT
10109 Say Y here to use the joystick port of your sound card.
10111 Ensoniq ES1371 based PCI sound cards
10112 CONFIG_SOUND_ES1371
10113 Say Y or M if you have a PCI sound card utilizing the Ensoniq
10114 ES1371 chipset, such as Ensoniq's AudioPCI97. To find out if
10115 your sound card uses an ES1371 without removing your computer's
10116 cover, use lspci -n and look for the PCI ID 1274:1371. Since
10117 Ensoniq was bought by Creative Labs, Sound Blaster 64/PCI
10118 models are either ES1370 or ES1371 based. This driver differs
10119 slightly from OSS/Free, so PLEASE READ Documentation/sound/es1371.
10121 Joystick support at boot time
10122 CONFIG_SOUND_ES1371_JOYPORT_BOOT
10123 Say Y here to use the joystick port of your sound card.
10125 Gameport I/O-range selection
10126 CONFIG_SOUND_ES1371_GAMEPORT
10127 Select the I/O-range of the gameport on a ES1371 based sound card.
10128 The card uses 8 ioports and the gameport is available at all eight
10129 ioports. Legal hexadecimal values are 200, 208, 210 and 218.
10130 The joystick driver will by default use 0x201.
10131 Leave the default 200 unless you have a joystick not attached
10132 to your sound card.
10134 S3 SonicVibes based PCI sound cards
10135 CONFIG_SOUND_SONICVIBES
10136 Say Y or M if you have a PCI sound card utilizing the S3
10137 SonicVibes chipset. To find out if your sound card uses a
10138 SonicVibes chip without removing your computer's cover, use
10139 lspci -n and look for the PCI ID 5333:CA00. This driver
10140 differs slightly from OSS/Free, so PLEASE READ
10141 Documentation/sound/sonicvibes.
10143 Rockwell WaveArtist
10144 CONFIG_SOUND_WAVEARTIST
10145 Say Y here to include support for the Rockwell WaveArtist sound
10146 system. This driver is mainly for the NetWinder.
10148 Are you using a crosscompiler
10149 CONFIG_CROSSCOMPILE
10150 Say Y here if you are compiling the kernel on a different
10151 architecture than the one it is intended to run on.
10153 Build fp exception handler module
10154 CONFIG_MIPS_FPE_MODULE
10155 Build the floating point exception handler module. This option is
10156 only useful for people working on the floating point exception
10157 handler. If you don't, say N.
10159 Remote GDB kernel debugging
10160 CONFIG_REMOTE_DEBUG
10161 If you say Y here, it will be possible to remotely debug the MIPS
10162 kernel using gdb. This enlarges your kernel image disk size by
10163 several megabytes and requires a machine with more than 16 MB,
10164 better 32 MB RAM to avoid excessive linking time. This is only
10165 useful for kernel hackers. If unsure, say N.
10167 Magic System Request Key support
10169 If you say Y here, you will have some control over the system even
10170 if the system crashes for example during kernel debugging (e.g., you
10171 will be able to flush the buffer cache to disk, reboot the system
10172 immediately or dump some status information). This is accomplished
10173 by pressing various keys while holding SysRq (Alt+PrintScreen). The
10174 keys are documented in Documentation/sysrq.txt. Don't say Y unless
10175 you really know what this hack does.
10179 ISDN ("Integrated Services Digital Networks", called RNIS in France)
10180 is a special type of fully digital telephone service; it's mostly
10181 used to connect to your Internet service provider (with SLIP or
10182 PPP). The main advantage is that the speed is higher than ordinary
10183 modem/telephone connections, and that you can have voice
10184 conversations while downloading stuff. It only works if your
10185 computer is equipped with an ISDN card and both you and your service
10186 provider purchased an ISDN line from the phone company. For details,
10187 read http://alumni.caltech.edu/~dank/isdn/ on the WWW. (To browse
10188 the WWW, you need to have access to a machine on the Internet that
10189 has a program like lynx or netscape.)
10191 This driver allows you to use an ISDN-card for networking
10192 connections and as dialin/out device. The isdn-tty's have a built in
10193 AT-compatible modem emulator. Network devices support autodial,
10194 channel-bundling, callback and caller-authentication without having
10195 a daemon running. A reduced T.70 protocol is supported with tty's
10196 suitable for German BTX. On D-Channel, the protocols EDSS1
10197 (Euro-ISDN) and 1TR6 (German style) are supported. See
10198 Documentation/isdn/README for more information.
10200 If you want to compile the ISDN code as a module ( = code which can
10201 be inserted in and removed from the running kernel whenever you
10202 want), say M here and read Documentation/modules.txt. The module
10203 will be called isdn.o. If unsure, say N.
10205 Support synchronous PPP
10207 Over digital connections such as ISDN, there is no need to
10208 synchronize sender and recipient's clocks with start and stop bits
10209 as is done over analog telephone lines. Instead, one can use
10210 "synchronous PPP". Saying Y here will include this protocol. This
10211 protocol is used by Cisco and Sun for example. So you want to say Y
10212 here if the other end of your ISDN connection supports it. You will
10213 need a special version of pppd (called ipppd) for using this
10214 feature. See Documentation/isdn/README.syncppp and
10215 Documentation/isdn/syncPPP.FAQ for more information.
10217 Support generic MP (RFC 1717)
10219 With synchronous PPP enabled, it is possible to increase throughput
10220 by bundling several ISDN-connections, using this protocol. See
10221 Documentation/isdn/README.syncppp for more information.
10223 Use VJ-compression with synchronous PPP
10225 This enables Van Jacobson header compression for synchronous PPP.
10226 Say Y if the other end of the connection supports it.
10228 Support audio via ISDN
10230 If you say Y here, the modem-emulator will support a subset of the
10231 EIA Class 8 Voice commands. Using a getty with voice-support
10232 (mgetty+sendfax by gert@greenie.muc.de with an extension, available
10233 with the ISDN utility package for example), you will be able to use
10234 your Linux box as an ISDN-answering machine. Of course, this must be
10235 supported by the lowlevel driver also. Currently, the HiSax driver
10236 is the only voice-supporting driver. See
10237 Documentation/isdn/README.audio for more information.
10239 X.25 PLP on top of ISDN (EXPERIMENTAL)
10241 This experimental feature provides the X.25 protocol over ISDN
10242 connections. See Documentation/isdn/README.x25 for more information
10243 if you are thinking about using this.
10245 ICN 2B and 4B support
10246 CONFIG_ISDN_DRV_ICN
10247 This enables support for two kinds of ISDN-cards made by a German
10248 company called ICN. 2B is the standard version for a single ISDN
10249 line with two B-channels, 4B supports two ISDN lines. For running
10250 this card, additional firmware is necessary, which has to be
10251 downloaded into the card using a utility which is distributed
10252 separately. See Documentation/isdn/README and README.icn for more
10255 If you want to compile this as a module ( = code which can be
10256 inserted in and removed from the running kernel whenever you want),
10257 say M here and read Documentation/modules.txt. The module will be
10261 CONFIG_ISDN_DRV_LOOP
10262 This driver provides a virtual ISDN card. Its primary purpose is
10263 testing of linklevel features or configuration without getting
10264 charged by your service-provider for lots of phone calls.
10265 You need will need the loopctrl utility from the latest isdn4k-utils
10266 package to set up this driver.
10268 HiSax SiemensChipSet driver support
10269 CONFIG_ISDN_DRV_HISAX
10270 This is a driver supporting the Siemens chipset on various
10271 ISDN-cards (like AVM A1, Elsa ISDN cards, Teles S0-16.0, Teles
10272 S0-16.3, Teles S0-8, Teles/Creatix PnP, ITK micro ix1 and many
10275 HiSax is just the name of this driver, not the name of any hardware.
10277 If you have a card with such a chipset, you should say Y here and
10278 also to the configuration option of the driver for your particular
10281 If you want to compile this as a module ( = code which can be
10282 inserted in and removed from the running kernel whenever you want),
10283 say M here and read Documentation/modules.txt. The module will be
10284 called hisax.o. See Documentation/isdn/README.HiSax for more
10285 information on using this driver.
10287 HiSax Support for Teles 16.0/8.0
10289 This enables HiSax support for the Teles ISDN-cards S0-16.0, S0-8
10290 and many compatibles.
10292 See Documentation/isdn/README.HiSax on how to configure it using the
10293 different cards, a different D-channel protocol, or non-standard
10294 IRQ/port/shmem settings.
10296 HiSax Support for Teles 16.3 or PNP or PCMCIA
10298 This enables HiSax support for the Teles ISDN-cards S0-16.3 the
10299 Teles/Creatix PnP and the Teles PCMCIA.
10301 See Documentation/isdn/README.HiSax on how to configure it using the
10302 different cards, a different D-channel protocol, or non-standard
10305 HiSax Support for Teles 16.3c
10306 CONFIG_HISAX_TELES3C
10307 This enables HiSax support for the Teles ISDN-cards 16.3c.
10309 See Documentation/isdn/README.HiSax on how to configure it using the
10310 different cards, a different D-channel protocol, or non-standard
10313 HiSax Support for AVM A1 (Fritz)
10314 CONFIG_HISAX_AVM_A1
10315 This enables HiSax support for the AVM A1 (aka "Fritz").
10317 See Documentation/isdn/README.HiSax on how to configure it using the
10318 different cards, a different D-channel protocol, or non-standard
10321 HiSax Support for Elsa ISA cards
10323 This enables HiSax support for the Elsa Mircolink ISA cards, for the
10324 Elsa Quickstep series cards and Elsa PCMCIA.
10326 See Documentation/isdn/README.HiSax on how to configure it using the
10327 different cards, a different D-channel protocol, or non-standard
10330 HiSax Support for ITK ix1-micro Revision 2
10331 CONFIG_HISAX_IX1MICROR2
10332 This enables HiSax support for the ITK ix1-micro Revision 2 card.
10334 See Documentation/isdn/README.HiSax on how to configure it using the
10335 different cards, a different D-channel protocol, or non-standard
10338 HiSax Support for Eicon.Diehl Diva cards
10339 CONFIG_HISAX_DIEHLDIVA
10340 This enables HiSax support for the Eicon.Diehl Diva none PRO
10341 versions passive ISDN cards.
10343 See Documentation/isdn/README.HiSax on how to configure it using the
10344 different cards, a different D-channel protocol, or non-standard
10347 HiSax Support for ASUSCOM cards
10348 CONFIG_HISAX_ASUSCOM
10349 This enables HiSax support for the AsusCom and their OEM versions
10350 passive ISDN cards.
10352 See Documentation/isdn/README.HiSax on how to configure it using the
10353 different cards, a different D-channel protocol, or non-standard
10356 HiSax Support for TELEINT cards
10357 CONFIG_HISAX_TELEINT
10358 This enables HiSax support for the TELEINT SA1 semiactiv ISDN card.
10360 See Documentation/isdn/README.HiSax on how to configure it using the
10361 different cards, a different D-channel protocol, or non-standard
10364 HiSax Support for Sedlbauer speed card/win-star
10365 CONFIG_HISAX_SEDLBAUER
10366 This enables HiSax support for the Sedlbauer passive ISDN cards.
10368 See Documentation/isdn/README.HiSax on how to configure it using the
10369 different cards, a different D-channel protocol, or non-standard
10372 HiSax Support for USR Sportster internal TA
10373 CONFIG_HISAX_SPORTSTER
10374 This enables HiSax support for the USR Sportster internal TA card.
10376 See Documentation/isdn/README.HiSax on how to configure it using a
10377 different D-channel protocol, or non-standard IRQ/port settings.
10379 HiSax Support for MIC card
10381 This enables HiSax support for the ITH MIC card.
10383 See Documentation/isdn/README.HiSax on how to configure it using a
10384 different D-channel protocol, or non-standard IRQ/port settings.
10386 HiSax Support for NETjet card
10387 CONFIG_HISAX_NETJET
10388 This enables HiSax support for the NetJet from Traverse
10391 See Documentation/isdn/README.HiSax on how to configure it using a
10392 different D-channel protocol, or non-standard IRQ/port settings.
10394 HiSax Support for Niccy PnP/PCI card
10396 This enables HiSax support for the Dr. Neuhaus Niccy PnP or PCI.
10398 See Documentation/isdn/README.HiSax on how to configure it using a
10399 different D-channel protocol, or non-standard IRQ/port settings.
10401 HiSax Support for Am7930 (EXPERIMENTAL)
10402 CONFIG_HISAX_AMD7930
10403 This enables HiSax support for the AMD7930 chips on some SPARCs.
10404 This code is not finished yet.
10406 HiSax Support for EURO/DSS1
10408 Say Y or N according to the D-channel protocol which your local
10409 telephone service company provides.
10411 NOTE: If you say Y here and you have only one ISDN card installed,
10412 you cannot say Y to "HiSax Support for German 1TR6", below. And vice
10415 Support for German tariff info
10417 If you want that the HiSax hardware driver sends messages to the
10418 upper level of the isdn code on each AOCD (Advice Of Charge, During
10419 the call -- transmission of the fee information during a call) and
10420 on each AOCE (Advice Of Charge, at the End of the call --
10421 transmission of fee information at the end of the call), say Y here.
10422 This works only in Germany.
10424 Support for Australian Microlink service (not for std. EURO)
10426 If you are in Australia and connected to the Microlink telephone
10427 network, enable this, because there are little differences in
10430 Please don't enable this in other countries.
10432 HiSax Support for US/NI-1 (not released yet)
10434 Say Y or N according to the D-channel protocol which your local
10435 telephone service company provides.
10437 HiSax Support for German 1TR6
10439 Say Y or N according to the D-channel protocol which your local
10440 telephone service company provides.
10442 NOTE: If you say Y here and you have only one ISDN card installed,
10443 you cannot say Y to "HiSax Support for EURO/DSS1", above. And vice
10447 CONFIG_ISDN_DRV_PCBIT
10448 This enables support for the PCBIT ISDN-card. This card is
10449 manufactured in Portugal by Octal. For running this card, additional
10450 firmware is necessary, which has to be downloaded into the card
10451 using a utility which is distributed separately. See
10452 Documentation/isdn/README and Documentation/isdn/README.pcbit for
10455 If you want to compile this as a module ( = code which can be
10456 inserted in and removed from the running kernel whenever you want),
10457 say M here and read Documentation/modules.txt. The module will be
10460 Spellcaster support (EXPERIMENTAL)
10462 This enables support for the Spellcaster BRI ISDN boards. This
10463 driver currently builds only in a modularized version ( = code which
10464 can be inserted in and removed from the running kernel whenever you
10465 want, details in Documentation/modules.txt); the module will be
10466 called sc.o. See Documentation/isdn/README.sc and
10467 http://www.spellcast.com for more information (to browse the WWW,
10468 you need to have access to a machine on the Internet that has a
10469 program like lynx or netscape).
10471 AVM-B1 with CAPI2.0 support
10472 CONFIG_ISDN_DRV_AVMB1
10473 This enables support for the AVM B1 ISDN networking cards. In
10474 addition, a CAPI (Common ISDN Application Programming Interface, a
10475 standard making it easy for programs to access ISDN hardware, see
10476 http://www.capi.org/; to browse the WWW, you need to have access to
10477 a machine on the Internet that has a program like lynx or netscape)
10478 interface for this card is provided. In order to use this card,
10479 additional firmware is necessary, which has to be downloaded into
10480 the card using a utility which is distributed separately. Please
10481 read the file Documentation/isdn/README.avmb1.
10483 This code is also available as a module ( = code which can be
10484 inserted in and removed from the running kernel whenever you want).
10485 The module will be called avmb1.o. If you want to compile it as a
10486 module, say M here and read Documentation/modules.txt.
10488 Verbose reason code reporting (kernel size +=7K)
10489 CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON
10490 If you say Y here, the AVM B1 driver will give verbose reasons for
10491 disconnecting. This will increase the size of the kernel by 7 KB. If
10494 IBM Active 2000 support (EXPERIMENTAL)
10495 CONFIG_ISDN_DRV_ACT2000
10496 Say Y here if you have an IBM Active 2000 ISDN card. In order to use
10497 this card, additional firmware is necessary, which has to be loaded
10498 into the card using a utility which is part of the latest
10499 isdn4k-utils package. Please read the file
10500 Documentation/isdn/README.act2000 for more information.
10502 Support for AP1000 multicomputer
10504 This enables support for a SPARC based parallel multi-computer
10505 called AP1000+. For details on our efforts to port Linux to this
10506 machine see http://cap.anu.edu.au/cap/projects/linux (to browse the
10507 WWW, you need to have access to a machine on the Internet that has a
10508 program like lynx or netscape) or mail to hackers@cafe.anu.edu.au
10510 Support for Sun4 architecture
10512 Say Y here if, and only if, your machine is a Sun4. Note that
10513 a kernel compiled with this option will run only on Sun4.
10514 (And the current version will probably work only on sun4/330.)
10516 SPARC ESP SCSI support
10518 This is the driver for the Sun ESP SCSI host adapter. The ESP
10519 chipset is present in most SPARC-based computers.
10521 SPARC /dev/openprom compatibility driver
10522 CONFIG_SUN_OPENPROMIO
10523 This driver provides user programs with an interface to the SPARC
10524 PROM device tree. The driver implements a SunOS-compatible
10525 interface and a NetBSD-compatible interface.
10527 If you want to compile this as a module ( = code which can be
10528 inserted in and removed from the running kernel whenever you want),
10529 say M and read Documentation/modules.txt. If unsure, say Y.
10531 Mostek real time clock support
10532 CONFIG_SUN_MOSTEK_RTC
10533 The Mostek RTC chip is used on all knows Sun computers except
10534 some JavaStation-s. For a JavaStation you need to say Y both here
10537 Say Y here unless you are building a special purpose kernel.
10540 #Siemens SAB82532 serial support
10543 ### Please someone fill these in.
10547 # m68k-specific kernel options
10548 # Documented by Chris Lawrence <quango@themall.net> et al.
10552 This option enables support for the Amiga series of computers. If
10553 you plan to use this kernel on an Amiga, say Y here and browse the
10554 material available in Documentation/m68k; otherwise say N.
10558 This option enables support for the 68000-based Atari series of
10559 computers (including the TT, Falcon and Medusa). If you plan to use
10560 this kernel on an Atari, say Y here and browse the material
10561 available in Documentation/m68k; otherwise say N.
10565 This option enables support for the Hades Atari clone. If you plan
10566 to use this kernel on a Hades, say Y here; otherwise say N.
10570 This option enables support for the Apple Macintosh series of
10571 computers (yes, there is experimental support now, at least for part
10574 Say N unless you're willing to code the remaining necessary support.
10579 This option enables support for the HP9000/300 series of
10580 workstations. Support for these machines is still very experimental.
10581 If you plan to try to use the kernel on such a machine say Y here.
10582 Everybody else says N.
10586 If you anticipate running this kernel on a computer with a MC68020
10587 processor, say Y. Otherwise, say N. Note that the 68020 requires a
10588 68851 MMU (Memory Management Unit) to run Linux/m68k.
10592 If you anticipate running this kernel on a computer with a MC68030
10593 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
10594 work, as it does not include an MMU (Memory Management Unit).
10598 If you anticipate running this kernel on a computer with a MC68LC040
10599 or MC68040 processor, say Y. Otherwise, say N. Note that an
10600 MC68EC040 will not work, as it does not include an MMU (Memory
10605 If you anticipate running this kernel on a computer with a MC68060
10606 processor, say Y. Otherwise, say N.
10608 Advanced processor options
10609 CONFIG_ADVANCED_CPU
10610 This gives you access to some advanced options for the CPU. The
10611 defaults should be fine for most users, but these options may make
10612 it possible for you to improve performance somewhat if you know what
10613 you are doing. Most users should say N to this question.
10615 Use read-modify-write instructions
10617 This allows to use certain instructions that work with indivisible
10618 read-modify-write bus cycles. While this is faster than the
10619 workaround of disabling interrupts, it can conflict with DMA
10620 ( = direct memory access) on many Amiga systems, and it is also said
10621 to destabilize other machines. It is very likely that this will
10622 cause serious problems on any Amiga or Atari Medusa if set. The only
10623 configuration where it should work are 68030-based Ataris, where it
10624 apparently improves performance. But you've been warned! Unless you
10625 really know what you are doing, say N. Try Y only if you're quite
10628 Amiga AutoConfig Identification
10630 This enables support for automatic identification of Amiga expansion
10631 cards that obey the AutoConfig(tm) specification.
10632 Say Y if you want your expansion cards to be identified on bootup;
10633 it will enlarge your kernel by about 10 KB. The identification
10634 information is also available through /proc/zorro (say Y to
10635 "/proc filesystem support"!).
10637 Note that even if you say N here, you can still use your expansion
10638 cards. If in doubt, say Y.
10640 CONFIG_AMIGA_PCMCIA
10641 Include support in the kernel for pcmcia on Amiga 1200 and Amiga 600.
10642 If you intend to use pcmcia cards say Y; otherwise say N.
10644 Amiga GSP (TMS340x0) support
10646 Include support for Amiga graphics cards that use the Texas
10647 Instruments TMS340x0 GSP (Graphics Signal Processor) chips. Say Y
10648 if you want to use a DMI Resolver or Commodore A2410 (Lowell)
10649 graphics card on an Amiga; otherwise, say N.
10651 DMI Resolver support
10652 CONFIG_GSP_RESOLVER
10653 Include support in the kernel for the DMI Resolver graphics card. If
10654 you have one, say Y; otherwise, say N.
10658 Include support in the kernel for the Commodore/University of Lowell
10659 A2410 graphics card. If you have one, say Y; otherwise, say N.
10661 Amiga Zorro II ramdisk support
10663 This enables support for using Chip RAM and Zorro II RAM as a
10664 ramdisk or as a swap partition. Say Y if you want to include this
10665 driver in the kernel. This driver is also available as a module
10666 ( = code which can be inserted in and removed from the running
10667 kernel whenever you want). The module is called z2ram.o. If you want
10668 to compile it as a module, say M here and read
10669 Documentation/modules.txt.
10671 Atari ST-RAM swap support
10673 This enables support for using (parts of) ST-RAM as swap space,
10674 instead of as normal system memory. This can first enhance system
10675 performance if you have lots of alternate RAM (compared to the size
10676 of ST-RAM), because executable code always will reside in faster
10677 memory. ST-RAM will remain as ultra-fast swap space. On the other
10678 hand, it allows much improved dynamic allocations of ST-RAM buffers
10679 for device driver modules (e.g. floppy, ACSI, SLM printer, DMA
10680 sound). The probability that such allocations at module load time
10681 fail is drastically reduced.
10685 This enables support for the Atari ACSI interface. The driver
10686 supports hard disks and CD-ROMs, which have 512-byte sectors, or can
10687 be switched to that mode. Due to the ACSI command format, only disks
10688 up to 1 GB are supported. Special support for certain ACSI to SCSI
10689 adapters, which could relax that, isn't included yet. The ACSI
10690 driver is also the basis for certain other drivers for devices
10691 attached to the ACSI bus: Atari SLM laser printer, BioNet-100
10692 Ethernet, and PAMsNet Ethernet. If you want to use one of these
10693 devices, you need ACSI support, too.
10695 This driver is also available as a module ( = code which can be
10696 inserted in and removed from the running kernel whenever you want).
10697 The module will be called acsi.o.
10699 Probe all LUNs on each ACSI device
10700 CONFIG_ACSI_MULTI_LUN
10701 If you have a ACSI device that supports more than one LUN (Logical
10702 Unit Number), e.g. a CD jukebox, you should say Y here so that all
10703 will be found by the ACSI driver. An ACSI device with multiple LUNs
10704 acts logically like multiple ACSI devices. The vast majority of ACSI
10705 devices have only one LUN, and so most people can say N here and
10706 should in fact do so, because it is safer.
10708 Atari SLM laser printer support
10710 If you have an Atari SLM laser printer, say Y to include support for
10711 it in the kernel. Otherwise, say N. This driver is also available as
10712 a module ( = code which can be inserted in and removed from the
10713 running kernel whenever you want). The module will be called
10714 acsi_slm.o. Be warned: the driver needs much ST-RAM and can cause
10715 problems due to that fact!
10717 A3000 WD33C93A support
10719 If you have an Amiga 3000 and have SCSI devices connected to the
10720 built-in SCSI controller, say Y. Otherwise, say N. This driver is
10721 also available as a module ( = code which can be inserted in and
10722 removed from the running kernel whenever you want). The module is
10723 called wd33c93.o. If you want to compile it as a module, say M here
10724 and read Documentation/modules.txt.
10726 A2091 WD33C93A support
10728 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
10729 say N. This driver is also available as a module ( = code which can
10730 be inserted in and removed from the running kernel whenever you
10731 want). The module is called wd33c93.o. If you want to compile it as
10732 a module, say M here and read Documentation/modules.txt.
10734 GVP Series II WD33C93A support
10736 If you have a Great Valley Products Series II SCSI controller,
10737 answer Y. Also say Y if you have a later model of GVP SCSI
10738 controller (such as the GVP A4008 or a Combo board). Otherwise,
10739 answer N. This driver does NOT work for the T-Rex series of
10740 accelerators from TekMagic and GVP-M.
10742 This driver is also available as a module ( = code which can be
10743 inserted in and removed from the running kernel whenever you
10744 want). The module will be called gvp11.o. If you want to compile it
10745 as a module, say M here and read Documentation/modules.txt.
10747 Cyberstorm SCSI support
10748 CONFIG_CYBERSTORM_SCSI
10749 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
10750 accelerator board and the optional Cyberstorm SCSI controller,
10751 answer Y. Otherwise, say N.
10753 Cyberstorm II SCSI support
10754 CONFIG_CYBERSTORMII_SCSI
10755 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
10756 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
10759 Blizzard 2060 SCSI support
10760 CONFIG_BLZ2060_SCSI
10761 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
10762 and want to use the onboard SCSI controller, say Y. Otherwise,
10765 Blizzard 1230IV/1260 SCSI support
10766 CONFIG_BLZ1230_SCSI
10767 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
10768 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
10771 Blizzard PowerUP 603e+ SCSI support
10772 CONFIG_BLZ603EPLUS_SCSI
10773 If you have an Amiga 1200 with a Phase5 Blizzard PowerUP 603e+
10774 accelerator, say Y. Otherwise, say N.
10776 Fastlane SCSI support
10777 CONFIG_FASTLANE_SCSI
10778 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
10779 one in the near future, say Y to this question. Otherwise, say N.
10781 Atari native SCSI support
10783 If you have an Atari with built-in NCR5380 SCSI controller (TT,
10784 Falcon, ...) say Y to get it supported. Of course also, if you have
10785 a compatible SCSI controller (e.g. for Medusa). This driver is also
10786 available as a module ( = code which can be inserted in and removed
10787 from the running kernel whenever you want). The module is called
10788 atari_scsi.o. If you want to compile it as a module, say M here and
10789 read Documentation/modules.txt. This driver supports both styles of
10790 NCR integration into the system: the TT style (separate DMA), and
10791 the Falcon style (via ST-DMA, replacing ACSI). It does NOT support
10792 other schemes, like in the Hades (without DMA).
10794 Long delays for Toshiba CD-ROMs
10795 CONFIG_ATARI_SCSI_TOSHIBA_DELAY
10796 This option increases the delay after a SCSI arbitration to
10797 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
10798 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
10799 would impact performance a bit, so say N.
10801 Hades SCSI DMA emulator (EXPERIMENTAL)
10803 This option enables code which emulates the TT SCSI DMA chip on the
10804 Hades. This increases the SCSI transfer rates at least ten times
10805 compared to PIO transfers. Note that this code is experimental and
10806 has only been tested on a Hades with a 68060 processor. Before you
10807 use this, make backups of your entire hard disk.
10811 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
10814 This driver is also available as a module ( = code which can be
10815 inserted in and removed from the running kernel whenever you
10816 want). The module is called ariadne.o. If you want to compile it as
10817 a module, say M here and read Documentation/modules.txt.
10821 If you have a Village Tronic Ariadne II Ethernet adapter, say Y.
10824 This driver is also available as a module ( = code which can be
10825 inserted in and removed from the running kernel whenever you
10826 want). The module is called ariadne2.o. If you want to compile it as
10827 a module, say M here and read Documentation/modules.txt.
10831 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
10834 This driver is also available as a module ( = code which can be
10835 inserted in and removed from the running kernel whenever you
10836 want). The module is called a2065.o. If you want to compile it as a
10837 module, say M here and read Documentation/modules.txt.
10841 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
10843 This driver is also available as a module ( = code which can be
10844 inserted in and removed from the running kernel whenever you
10845 want). The module is called hydra.o. If you want to compile it as a
10846 module, say M here and read Documentation/modules.txt.
10848 Pcmcia NE2000 compatible support
10850 If you have a pcmcia ne2000 compatible adapter, say Y. Otherwise,
10853 This driver is also available as a module ( = code which can be
10854 inserted in and removed from the running kernel whenever you
10855 want). The module is called apne.o. If you want to compile it as a
10856 module, say M here and read Documentation/modules.txt.
10858 Atari Lance support
10860 Say Y to include support for several Atari Ethernet adapters based
10861 on the AMD Lance chipset: RieblCard (with or without battery), or
10862 PAMCard VME (also the version by Rhotron, with different addresses).
10865 CONFIG_ATARI_BIONET
10866 Say Y to include support for BioData's BioNet-100 Ethernet adapter
10867 for the ACSI port. The driver works (has to work...) with a polled
10868 I/O scheme, so it's rather slow :-(
10871 CONFIG_ATARI_PAMSNET
10872 Say Y to include support for the PAMsNet Ethernet adapter for the
10873 ACSI port ("ACSI node"). The driver works (has to work...) with a
10874 polled I/O scheme, so it's rather slow :-(
10876 Multiface Card III parallel support
10877 CONFIG_MULTIFACE_III_LP
10878 If you have a Multiface III card for your Amiga, and want to use its
10879 parallel port in Linux, say Y. Otherwise, say N.
10881 This driver is also available as a module ( = code which can be
10882 inserted in and removed from the running kernel whenever you want).
10883 The module is called lp_m68k.o. If you want to compile it as a
10884 module, say M here and read Documentation/modules.txt.
10886 Amiga mouse support
10888 If you want to be able to use an Amiga mouse in Linux, say Y.
10890 This driver is also available as a module ( = code which can be
10891 inserted in and removed from the running kernel whenever you want).
10892 The module is called amigamouse.o. If you want to compile it as a
10893 module, say M here and read Documentation/modules.txt.
10895 Amiga Copper Console
10897 This configures the console to use the Amiga's graphics coprocessor
10898 for scrolling, instead of using the CPU. This option markedly
10899 improves response times in the high color modes (5 bitplanes and
10900 up). If you would like to use this, say Y; otherwise, say N.
10902 Atari mouse support
10904 If you want to be able to use an Atari mouse in Linux, say Y.
10906 This driver is also available as a module ( = code which can be
10907 inserted in and removed from the running kernel whenever you want).
10908 The module is called atarimouse.o. If you want to compile it as a
10909 module, say M here and read Documentation/modules.txt.
10911 Atari MFP serial support
10912 CONFIG_ATARI_MFPSER
10913 If you like to use the MFP serial ports ("Modem1", "Serial1") under
10914 Linux, say Y. The driver equally supports all kinds of MFP serial
10915 ports and automatically detects whether Serial1 is available.
10917 This driver is also available as a module ( = code which can be
10918 inserted in and removed from the running kernel whenever you want).
10919 If you want to compile it as a module, say M here and read
10920 Documentation/modules.txt.
10922 Note for Falcon users: You also have an MFP port, it's just not
10923 wired to the outside... But you could use the port under Linux.
10925 Atari SCC serial support
10927 If you have serial ports based on a Zilog SCC chip (Modem2, Serial2,
10928 LAN) and like to use them under Linux, say Y. All built-in SCC's are
10929 supported (TT, MegaSTE, Falcon), and also the ST-ESCC. If you have
10930 two connectors for channel A (Serial2 and LAN), they are visible as
10931 two separate devices.
10933 This driver is also available as a module ( = code which can be
10934 inserted in and removed from the running kernel whenever you want).
10935 If you want to compile it as a module, say M here and read
10936 Documentation/modules.txt.
10938 Atari SCC serial DMA support
10939 CONFIG_ATARI_SCC_DMA
10940 This enables DMA support for receiving data on channel A of the SCC.
10941 If you have a TT you may say Y here and read
10942 drivers/char/atari_SCC.README. All other users should say N here,
10943 because only the TT has SCC-DMA, even if your machine keeps claiming
10946 Atari MIDI serial support
10948 If you want to use your Atari's MIDI port in Linux, say Y.
10950 This driver is also available as a module ( = code which can be
10951 inserted in and removed from the running kernel whenever you
10952 want). If you want to compile it as a module, say M here and read
10953 Documentation/modules.txt.
10955 Atari DSP56k Digital Signal Processor support
10956 CONFIG_ATARI_DSP56K
10957 If you want to be able to use the DSP56001 in Falcons, say Y. This
10958 driver is still experimental, and if you don't know what it is, or
10959 if you don't have this processor, just say N.
10961 This driver is also available as a module ( = code which can be
10962 inserted in and removed from the running kernel whenever you want).
10963 If you want to compile it as a module, say M here and read
10964 Documentation/modules.txt.
10966 Amiga builtin serial support
10967 CONFIG_AMIGA_BUILTIN_SERIAL
10968 If you want to use your Amiga's built-in serial port in Linux,
10971 This driver is also available as a module ( = code which can be
10972 inserted in and removed from the running kernel whenever you
10973 want). If you want to compile it as a module, say M here and read
10974 Documentation/modules.txt.
10976 GVP IO-Extender support
10978 If you want to use a GVP IO-Extender serial card in Linux, say Y.
10981 Multiface Card III serial support
10982 CONFIG_MULTIFACE_III_TTY
10983 If you want to use a Multiface III card's serial port in Linux,
10986 This driver is also available as a module ( = code which can be
10987 inserted in and removed from the running kernel whenever you want).
10988 If you want to compile it as a module, say M here and read
10989 Documentation/modules.txt.
10991 Amiga or Atari DMA sound support
10993 If you want to use the internal audio of your Atari or Amiga in
10994 Linux, answer Y to this question. This will provide a Sun-like
10995 /dev/audio, compatible with the Linux/i386 sound system. Otherwise,
10998 This driver is also available as a module ( = code which can be
10999 inserted in and removed from the running kernel whenever you
11000 want). If you want to compile it as a module, say M here and read
11001 Documentation/modules.txt.
11003 HP DCA serial support
11005 If you want to use the internal "DCA" serial ports on an HP300
11006 machine, say Y here.
11008 HP on-board LANCE support
11010 If you want to use the builtin "LANCE" Ethernet controller on an
11011 HP300 machine, say Y here.
11015 Say Y here to enable support for the "DIO" expansion bus used in
11016 HP300 machines. If you are using such a system you almost certainly
11019 MSDOS partition support
11020 CONFIG_MSDOS_PARTITION
11021 This option enables support for using hard disks that were
11022 partitioned on an MS-DOS system. This may be useful if you are
11023 sharing a hard disk between i386 and m68k Linux boxes, for example.
11024 Say Y if you need this feature; users who are only using their
11025 system-native partitioning scheme can say N here.
11029 There are two types of PowerPC chips supported. The more common
11030 types (601,603,604,740,750) and the embedded versions (821 and 860).
11031 Unless you are building a kernel for one of the embedded boards
11032 using the 821 or 860 choose 6xx.
11036 Linux currently supports several different kinds of PowerPC-based
11037 machines: Apple Power Macintoshes and clones (such as the Motorola
11038 Starmax series), PReP (PowerPC Reference Platform) machines such as
11039 the Motorola PowerStack, Amiga Power-Up systems (APUS), CHRP and the
11040 embedded MBX boards from Motorola. Currently, a single kernel binary
11041 only supports one type or the other. However, there is very early
11042 work on support for CHRP, PReP and PowerMac's from a single binary.
11044 Support for Open Firmware device tree in /proc
11045 CONFIG_PROC_DEVICETREE
11046 This option adds a device-tree directory under /proc which contains
11047 an image of the device tree that the kernel copies from Open
11048 Firmware. If unsure, say Y here.
11050 MESH (Power Mac internal SCSI) support
11052 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
11053 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
11054 other Power Macintoshes do). Say Y to include support for this SCSI
11055 adaptor. This driver is also available as a module called mesh.o
11056 ( = code which can be inserted in and removed from the running
11057 kernel whenever you want). If you want to compile it as a module,
11058 say M here and read Documentation/modules.txt.
11060 Maximum synchronous transfer rate
11061 CONFIG_SCSI_MESH_SYNC_RATE
11062 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
11063 drives a bus which is entirely internal to the machine (such as the
11064 7500, 7600, 8500, etc.), the MESH is capable of synchronous
11065 operation at up to 10 MB/s. On machines where the SCSI bus
11066 controlled by the MESH can have external devices connected, it is
11067 usually rated at 5 MB/s. 5 is a safe value here unless you know the
11068 MESH SCSI bus is internal only; in that case you can say 10. Say 0
11069 to disable synchronous operation.
11071 53C94 (Power Mac external SCSI) support
11072 CONFIG_SCSI_MAC53C94
11073 On Power Macintoshes (and clones) with two SCSI buses, the external
11074 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
11075 machines which only have one SCSI bus, such as the 7200, also use
11076 the 53C94. Say Y to include support for the 53C94.
11078 This driver is also available as a module called mac53c94.o ( = code
11079 which can be inserted in and removed from the running kernel
11080 whenever you want). If you want to compile it as a module, say M
11081 here and read Documentation/modules.txt.
11083 MACE (Power Mac Ethernet) support
11085 Power Macintoshes and clones with Ethernet built-in on the
11086 motherboard will usually use a MACE (Medium Access Control for
11087 Ethernet) interface. Say Y to include support for the MACE chip.
11089 This driver is also available as a module called mace.o ( = code
11090 which can be inserted in and removed from the running kernel
11091 whenever you want). If you want to compile it as a module, say M
11092 here and read Documentation/modules.txt.
11094 BMAC (G3 ethernet) support
11096 Say Y for support of BMAC Ethernet interfaces. These are used on G3
11099 This driver is also available as a module called bmac.o ( = code
11100 which can be inserted in and removed from the running kernel
11101 whenever you want). If you want to compile it as a module, say M
11102 here and read Documentation/modules.txt.
11106 Support for audio/video capture and overlay devices and FM radio
11107 cards. The exact capabilities of each device vary. User tools for
11108 this are available from
11109 ftp://ftp.uk.linux.org/pub/linux/video4linux.
11111 If you are interested in writing a driver for such an audio/video
11112 device or user software interacting with such a driver, please read
11113 the file Documentation/video4linux/API.html.
11115 This driver is also available as a module called videodev.o ( = code
11116 which can be inserted in and removed from the running kernel
11117 whenever you want). If you want to compile it as a module, say M
11118 here and read Documentation/modules.txt.
11120 AIMSlab RadioTrack (aka RadioReveal) support
11121 CONFIG_RADIO_RTRACK
11122 Choose Y here if you have one of these FM radio cards, and then fill
11123 in the port address below.
11125 Note that newer AIMSlab RadioTrack cards have a different chipset
11126 and are not supported by this driver. For these cards, use the
11127 RadioTrack II driver below.
11129 In order to control your radio card, you will need to use programs
11130 that are compatible with the Video for Linux API. Information on
11131 this API and pointers to "v4l" programs may be found on the WWW at
11132 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
11133 you need to have access to a machine on the Internet that has a
11134 program like lynx or netscape. More information is contained in the
11135 file Documentation/video4linux/radiotrack.txt.
11137 If you want to compile this driver as a module ( = code which can be
11138 inserted in and removed from the running kernel whenever you want),
11139 say M here and read Documentation/modules.txt. The module will be
11140 called radio-aimslab.o.
11142 RadioTrack i/o port
11143 CONFIG_RADIO_RTRACK_PORT
11144 Enter either 0x30f or 0x20f here. The card default is 0x30f, if you
11145 haven't changed the jumper setting on the card.
11147 AIMSlab RadioTrack II support
11148 CONFIG_RADIO_RTRACK2
11149 Choose Y here if you have this FM radio card, and then fill in the
11150 port address below.
11152 If you have GemTeks combined (PnP) sound- and radio card you must use
11153 this driver as a module and setup the card with isapnptools. You must
11154 also pass the module a suitable io parameter, 0x248 has been reported
11155 to be used by these cards.
11157 In order to control your radio card, you will need to use programs
11158 that are compatible with the Video for Linux API. Information on
11159 this API and pointers to "v4l" programs may be found on the WWW at
11160 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
11161 you need to have access to a machine on the Internet that has a
11162 program like lynx or netscape.
11164 If you want to compile this driver as a module ( = code which can be
11165 inserted in and removed from the running kernel whenever you want),
11166 say M here and read Documentation/modules.txt. The module will be
11167 called radio-rtrack2.o.
11169 RadioTrack II i/o port
11170 CONFIG_RADIO_RTRACK2_PORT
11171 Enter either 0x30c or 0x20c here. The card default is 0x30c, if you
11172 haven't changed the jumper setting on the card.
11174 Aztech/Packard Bell Radio
11175 CONFIG_RADIO_AZTECH
11176 Choose Y here if you have one of these FM radio cards, and then fill
11177 in the port address below.
11179 In order to control your radio card, you will need to use programs
11180 that are compatible with the Video for Linux API. Information on
11181 this API and pointers to "v4l" programs may be found on the WWW at
11182 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
11183 you need to have access to a machine on the Internet that has a
11184 program like lynx or netscape.
11186 If you want to compile this driver as a module ( = code which can be
11187 inserted in and removed from the running kernel whenever you want),
11188 say M here and read Documentation/modules.txt. The module will be
11189 called radio-aztech.o.
11191 Aztech/Packard Bell radio card i/o port
11192 CONFIG_RADIO_AZTECH_PORT
11193 Enter either 0x350 or 0x358 here. The card default is 0x350, if you
11194 haven't changed the setting of jumper JP3 on the card. Removing the
11195 jumper sets the card to 0x358.
11198 CONFIG_RADIO_SF16FMI
11199 Choose Y here if you have one of these FM radio cards, and then fill
11200 in the port address below.
11202 In order to control your radio card, you will need to use programs
11203 that are compatible with the Video for Linux API. Information on
11204 this API and pointers to "v4l" programs may be found on the WWW at
11205 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
11206 you need to have access to a machine on the Internet that has a
11207 program like lynx or netscape.
11209 If you want to compile this driver as a module ( = code which can be
11210 inserted in and removed from the running kernel whenever you want),
11211 say M here and read Documentation/modules.txt. The module will be
11212 called radio-sf16fmi.o
11214 SF16FMI I/O port (0x284 or 0x384)
11215 CONFIG_RADIO_SF16FMI_PORT
11216 Enter the I/O port of your SF16FMI radio card.
11219 CONFIG_RADIO_TYPHOON
11220 Choose Y here if you have one of these FM radio cards, and then fill
11221 in the port address and the frequency used for muting below.
11223 In order to control your radio card, you will need to use programs
11224 that are compatible with the Video for Linux API. Information on
11225 this API and pointers to "v4l" programs may be found on the WWW at
11226 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
11227 you need to have access to a machine on the Internet that has a
11228 program like lynx or netscape.
11230 If you want to compile this driver as a module ( = code which can be
11231 inserted in and removed from the running kernel whenever you want),
11232 say M here and read Documentation/modules.txt. The module will be
11233 called radio-typhoon.o
11235 Support for /proc/radio-typhoon
11236 CONFIG_RADIO_TYPHOON_PROC_FS
11237 Say Y here if you want the typhoon radio card driver to write
11238 status information (frequency, volume, muted, mute frequency,
11239 base address) to /proc/radio-typhoon. The file can be viewed with
11240 your favorite pager (i.e. use "more /proc/radio-typhoon" or "less
11241 /proc/radio-typhoon" or simply "cat /proc/radio-typhoon").
11243 Typhoon I/O port (0x316 or 0x336)
11244 CONFIG_RADIO_TYPHOON_PORT
11245 Enter the I/O port of your Typhoon or EcoRadio radio card.
11247 Typhoon frequency set when muting the device (kHz)
11248 CONFIG_RADIO_TYPHOON_MUTEFREQ
11249 Enter the frequency used for muting the radio. The device is never
11250 completely silent. If the volume is just turned down, you can still
11251 hear silent voices and music. For that reason, the frequency of the
11252 radio device is set to the frequency you can enter here whenever
11253 the device is muted. There should be no local radio station at that
11257 CONFIG_RADIO_ZOLTRIX
11258 Choose Y here if you have one of these FM radio cards, and then fill
11259 in the port address below.
11261 In order to control your radio card, you will need to use programs
11262 that are compatible with the Video for Linux API. Information on
11263 this API and pointers to "v4l" programs may be found on the WWW at
11264 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
11265 you need to have access to a machine on the Internet that has a
11266 program like lynx or netscape.
11268 If you want to compile this driver as a module ( = code which can be
11269 inserted in and removed from the running kernel whenever you want),
11270 say M here and read Documentation/modules.txt. The module will be
11271 called radio-zoltrix.o
11273 ZOLTRIX I/O port (0x20c or 0x30c)
11274 CONFIG_RADIO_ZOLTRIX_PORT
11275 Enter the I/O port of your Zoltrix radio card.
11277 ADS Cadet AM/FM Tuner
11279 Say Y here if this is your AM/FM radio card.
11281 In order to control your radio card, you will need to use programs
11282 that are compatible with the Video for Linux API. Information on
11283 this API and pointers to "v4l" programs may be found on the WWW at
11284 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
11285 you need to have access to a machine on the Internet that has a
11286 program like lynx or netscape.
11288 If you want to compile this driver as a module ( = code which can be
11289 inserted in and removed from the running kernel whenever you want),
11290 say M here and read Documentation/modules.txt. The module will be
11291 called radio-cadet.o
11294 CONFIG_RADIO_MIROPCM20
11295 Choose Y here if you have this FM radio card. You also need to say Y
11296 to "ACI mixer (miroPCM12/PCM20)" (in "additional low level sound
11297 drivers") for this to work.
11299 In order to control your radio card, you will need to use programs
11300 that are compatible with the Video for Linux API. Information on
11301 this API and pointers to "v4l" programs may be found on the WWW at
11302 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
11303 you need to have access to a machine on the Internet that has a
11304 program like lynx or netscape.
11306 If you want to compile this driver as a module ( = code which can be
11307 inserted in and removed from the running kernel whenever you want),
11308 say M here and read Documentation/modules.txt. The module will be
11309 called radio-miropcm20.o
11312 CONFIG_RADIO_GEMTEK
11313 Choose Y here if you have this FM radio card, and then fill in the
11314 port address below.
11316 In order to control your radio card, you will need to use programs
11317 that are compatible with the Video for Linux API. Information on
11318 this API and pointers to "v4l" programs may be found on the WWW at
11319 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
11320 you need to have access to a machine on the Internet that has a
11321 program like lynx or netscape.
11323 If you want to compile this driver as a module ( = code which can be
11324 inserted in and removed from the running kernel whenever you want),
11325 say M here and read Documentation/modules.txt. The module will be
11326 called radio-gemtek.o.
11329 CONFIG_RADIO_GEMTEK_PORT
11330 Enter either 0x20c, 0x30c, 0x24c or 0x34c here. The card default is
11331 0x34c, if you haven't changed the jumper setting on the card.
11333 PlanB Video-In for PowerMacs
11335 PlanB is the V4L driver for the PowerMac 7x00/8x00 series video
11336 input hardware. If you want to experiment with this, say Y.
11337 Otherwise, or if you don't understand a word, say N.
11338 See http://www.cpu.lu/~mlan/planb.html for more info.
11340 Saying M will compile this driver as a module (planb.o).
11342 TerraTec ActiveRadio
11343 CONFIG_RADIO_TERRATEC
11344 Choose Y here if you have this FM radio card, and then fill in the
11345 port address below. (TODO)
11347 Note: This driver is in its early stages. Right now volume and frequency
11348 control and muting works at least for me, but unfortunately i have not
11349 found anybody who wants to use this card with linux. So if it is this
11350 what YOU are trying to do right now, PLEASE DROP ME A NOTE!!
11351 Rolf Offermanns (rolf@offermanns.de)
11353 In order to control your radio card, you will need to use programs
11354 that are compatible with the Video for Linux API. Information on
11355 this API and pointers to "v4l" programs may be found on the WWW at
11356 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
11357 you need to have access to a machine on the Internet that has a
11358 program like lynx or netscape.
11361 If you want to compile this driver as a module ( = code which can be
11362 inserted in and removed from the running kernel whenever you want),
11363 say M here and read Documentation/modules.txt. The module will be
11364 called radio-terratec.o.
11367 BT848 Video For Linux
11369 Support for BT848 based frame grabber/overlay boards. This includes
11370 the Miro, Hauppauge and STB boards. Please read the material in
11371 Documentation/video4linux/bttv for more information.
11373 This driver is also available as a module called bttv.o ( = code
11374 which can be inserted in and removed from the running kernel
11375 whenever you want). If you want to compile it as a module, say M
11376 here and read Documentation/modules.txt.
11378 SAA5249 Teletext processor
11379 CONFIG_VIDEO_SAA5249
11380 Support for I2C bus based teletext using the SAA5249 chip. At the
11381 moment this is only useful on some European WinTV cards.
11383 This driver is also available as a module called saa5249.o ( = code
11384 which can be inserted in and removed from the running kernel
11385 whenever you want). If you want to compile it as a module, say M
11386 here and read Documentation/modules.txt.
11388 Quickcam BW Video For Linux
11389 CONFIG_VIDEO_BWQCAM
11390 Say Y have if you the black and white version of the QuickCam
11391 camera. See the next option for the color version.
11393 This driver is also available as a module called bw-qcam.o ( = code
11394 which can be inserted in and removed from the running kernel
11395 whenever you want). If you want to compile it as a module, say M
11396 here and read Documentation/modules.txt.
11398 Colour QuickCam Video For Linux
11400 This is the video4linux driver for the colour version of the
11401 Connectix Quickcam. If you have one of these cameras, say Y here,
11402 otherwise say N. This driver does not work with the original
11403 monochrome Quickcam, Quickcam VC or QuickClip. It is also available
11404 as a module (c-qcam.o).
11406 Mediavision Pro Movie Studio Video For Linux
11408 Say Y if you have such a thing. This driver is also available as a
11409 module called pms.o ( = code which can be inserted in and removed
11410 from the running kernel whenever you want). If you want to compile
11411 it as a module, say M here and read Documentation/modules.txt.
11413 Compaq SMART2 support
11415 This is the driver for Compaq Smart Array controllers.
11416 Everyone using these boards should say Y here.
11417 See "linux/Documentation/cpqarray.txt" for the current list of
11418 boards supported by this driver, and for further information
11419 on the use of this driver.
11426 This selects the processor type of your CPU. This is only used to
11427 determine C compiler optimization options, and can affect the
11428 compatibility of the kernel on other processors. If you specify
11429 ARM6, the kernel should work on all 32-bit processors. If you
11430 specify ARM2, ARM250 or ARM3, it should work on all 26-bit
11431 processors. If you're not sure, set it to "None".
11435 This selects what ARM system you wish to build the kernel for. It
11436 also selects to some extent the CPU type. If you are unsure what
11437 to set this option to, please consult any information supplied with
11440 Include support for Chalice CATS boards
11442 Say Y here if you intend to run this kernel on a CATS system.
11444 Include support for Intel EBSA285
11445 CONFIG_ARCH_EBSA285
11446 Say Y here if you intend to run this kernel on an EBSA-285 evaluation
11449 Include support for the NetWinder
11450 CONFIG_ARCH_NETWINDER
11451 Say Y here if you intend to run this kernel on the NetWinder.
11455 Say Y to include the NWFPE floating point emulator in the kernel. This
11456 is necessary to run most binaries. Linux does not currently support
11457 floating point hardware so you need to say Y here even if your machine
11458 has an FPA or floating point co-processor podule.
11460 It is also possible to say M to build the emulator as a module
11461 (nwfpe.o) or indeed to leave it out altogether. However, unless you
11462 know what you are doing this can easily render your machine unbootable.
11463 Saying Y is the safe option.
11465 You may say N here if you are going to load the Acorn FPEmulator
11466 early in the bootup.
11468 DS1620 Thermometer support
11470 Say Y here to include support for the thermal management hardware
11471 found in the NetWinder. This driver allows the user to control the
11472 temperature set points and to read the current temperature.
11474 It is also possible to say M here to build it as a module (ds1620.o)
11475 It is recommended to be used on a NetWinder, but it is not a
11478 Verbose kernel error messages
11479 CONFIG_DEBUG_ERRORS
11480 This option controls verbose debugging information which can be
11481 printed when the kernel detects an internal error. This debugging
11482 information is useful to kernel hackers when tracking down problems,
11483 but mostly meaningless to other people. It's safe to say Y unless
11484 you are concerned with the code size or don't want to see these
11487 Compile kernel with frame pointer
11488 CONFIG_FRAME_POINTER
11489 If you say Y here, the resulting kernel will be slightly larger and
11490 slower, but it will give useful debugging information. If you don't
11491 debug the kernel, you can say N.
11493 User fault debugging
11495 When a user program crashes due to an exception, the kernel can print
11496 a brief message explaining what the problem was. This is sometimes
11497 helpful for debugging but serves no purpose on a production system.
11498 Most people should say N here.
11500 Include gdb debugging information in kernel binary
11502 Say Y here to include source-level debugging information in the
11503 `vmlinux' binary image. This is handy if you want to use gdb or
11504 addr2line to debug the kernel. It has no impact on the in-memory
11505 footprint of the running kernel but it can increase the amount of
11506 time and disk space needed for compilation. If in doubt say N.
11508 Split initialisation functions into discardable section
11509 CONFIG_TEXT_SECTIONS
11510 Normally code that is only used during initialisation is collected
11511 into a special area of the kernel so that it can be discarded and
11512 the memory reclaimed when initialisation is complete. In addition,
11513 if the kernel you wish to build is able to run on multiple
11514 architectures, it allows the unused code to be discarded. Some
11515 versions of binutils, however, have a bug that causes the kernel
11516 to crash during startup when this option is enabled. Say Y unless
11517 you experience problems that you suspect may be caused by this.
11519 Disable pgtable cache
11520 CONFIG_NO_PGT_CACHE
11521 Normally the kernel maintains a `quicklist' of preallocated pagetable
11522 structures in order to increase performance. On machines with very
11523 few pages this may however be a loss. Say Y here to disable the pgtable
11526 RISC OS personality
11528 Say Y here to include the kernel code necessary if you want to run
11529 Acorn RISC OS/Arthur binaries under Linux. This code is still very
11530 experimental; if this sounds frightening, say N and sleep in peace.
11531 You can also say M here to compile this support as a module (which
11532 will be called arthur.o).
11534 Initial kernel command line
11536 On some architectures (EBSA110 and CATS), there is currently no way
11537 for the boot loader to pass arguments to the kernel. For these
11538 architectures, you should supply some command-line options at build
11539 time by entering them here. As a minimum, you should specify the
11540 memory size and the root device (eg, mem=64M root=/dev/nfs)
11542 Hardware alignment trap
11543 CONFIG_ALIGNMENT_TRAP
11544 ARM processors can not fetch/store information which is not naturally
11545 aligned on the bus, ie, a 4 byte fetch must start at an address divisable
11546 by 4. On 32-bit ARM processors, these instructions can be emulated in
11547 software with a severe performance impact. This is necessary for correct
11548 operation of some network protocols. With an IP-only configuration
11549 it is safe to say N, otherwise say Y.
11551 21285 serial port support
11552 CONFIG_SERIAL_21285
11553 If you have a machine based on a 21285 (Footbridge) StrongARM/PCI
11554 bridge you can enable its onboard serial port by enabling this
11555 option. The device has major ID 4, minor 64.
11557 Console on 21285 serial port
11558 CONFIG_SERIAL_21285_CONSOLE
11559 If you have enabled the serial port on the 21285 footbridge you can
11560 make it the console by answering 'Y' to this option.
11563 CONFIG_HOST_FOOTBRIDGE
11564 The 21285 Footbridge chip can operate in either `host mode' or
11565 `add-in' mode. Say Y if your 21285 is in host mode, and therefore
11566 is the configuration master, otherwise say N. This must not be
11567 set to 'Y' if the card is used in 'add-in' mode.
11569 MFM harddisk support
11571 Support the MFM hard drives on the Acorn Archimedes both
11572 on-board the A4x0 motherboards and via the Acorn MFM podules.
11573 Drives upto 64MB are supported. If you haven't got one of these
11574 machines or drives just say 'N'.
11576 Old Archimedes floppy (1772) support
11577 CONFIG_BLK_DEV_FD1772
11578 Support the floppy drive on the Acorn Archimedes (A300, A4x0, A540,
11579 R140 and R260) series of computers; it supports only 720K floppies
11580 at the moment. If you don't have one of these machines just answer
11583 Autodetect hard drive geometry
11584 CONFIG_BLK_DEV_MFM_AUTODETECT
11585 If you answer 'Y' the MFM code will attempt to automatically detect
11586 the cylinders/heads/sectors count on your hard drive. WARNING: This
11587 sometimes doesn't work and it also does some dodgy stuff which
11588 potentially might damage your drive.
11592 Say Y here if you want to build support for the IrDA (TM) protocols.
11593 The Infrared Data Associations (tm) specifies standards for wireless
11594 infrared communication and is supported by most laptops and PDA's.
11596 To use Linux support for the IrDA (tm) protocols, you will also need
11597 some user-space utilities like the irmanager and probably irattach
11598 as well. For more information, see the file
11599 Documentation/networking/irda.txt. You also want to read the
11600 IR-HOWTO, available from
11601 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
11603 This support is also available as a module. If you want to compile
11604 it as a module, say M here and read Documentation/modules.txt. The
11605 module will be called
11607 IrDA Cache last LSAP
11608 CONFIG_IRDA_CACHE_LAST_LSAP
11609 Say Y here if you want IrLMP to cache the last LSAP used. This makes
11610 sense since most frames will be sent/received on the same
11611 connection. Enabling this option will save a hash-lookup per frame.
11616 CONFIG_IRDA_FAST_RR
11617 Say Y here is you want IrLAP to send fast RR (Receive Ready) frames
11618 when acting as a primary station. This will make IrLAP send out a RR
11619 frame immediately when receiving a frame if its own transmit queue
11620 is currently empty. This will give a lot of speed improvement when
11621 receiving much data since the secondary station will not have to
11622 wait the max. turn around time before it is allowed to transmit the
11623 next time. If the transmit queue of the secondary is also empty the
11624 primary will back off waiting longer for sending out the RR frame
11625 until the timeout reaches the normal value. Enabling this option
11626 will make the IR-diode burn more power and thus reduce your battery
11633 Say Y here if you want the IrDA subsystem to write debug information
11634 to your syslog. You can change the debug level in
11635 /proc/sys/net/irda/debug
11637 If unsure, say Y (since it makes it easier to find the bugs).
11639 IrLAP Compression support
11640 CONFIG_IRDA_COMPRESSION
11641 Compression is _not_ part of the IrDA(tm) protocol specification,
11642 but it's working great! Linux is the first to try out compression
11643 support at the IrLAP layer. This means that you will only benefit
11644 from compression if you are running a Linux <-> Linux configuration.
11646 If you say Y here, you also need to say Y or M to a compression
11649 IrLAP Deflate Compression Protocol
11650 CONFIG_IRDA_DEFLATE
11651 Say Y here if you want to build support for the Deflate compression
11652 protocol. The deflate compression (GZIP) is exactly
11653 the same as the one used by the PPP protocol.
11655 If you want to compile this compression support as a module, say M
11656 here and read Documentation/modules.txt. The module will be called
11661 Say Y here if you want to build support for the IrLAN protocol. If
11662 you want to compile it as a module, say M here and read
11663 Documentation/modules.txt. IrLAN emulates an Ethernet and makes it
11664 possible to put up a wireless LAN using infrared beams.
11666 The IrLAN protocol can be used to talk with infrared access points
11667 like the HP NetbeamIR, or the ESI JetEye NET. You can also connect
11668 to another Linux machine running the IrLAN protocol for ad-hoc
11673 Say Y here if you want to build support for the IrCOMM protocol. If
11674 you want to compile it as a module, say M here and read
11675 Documentation/modules.txt. IrCOMM implements serial port emulation,
11676 and makes it possible to use all existing applications that
11677 understands TTY's with an infrared link. Thus you should be able to
11678 use application like PPP, minicom and others. Enabling this option
11679 will create two modules called ircomm and ircomm_tty. For more
11680 information go to http://www.pluto.dti.ne.jp/~thiguchi/irda/
11684 Say Y here if you want to build support for the IrLPT protocol. If
11685 you want to compile it as a module, say M here and read
11686 Documentation/modules.txt. IrLPT makes it possible to print
11687 documents to IrDA capable printers.
11689 IrLPT Client Protocol
11690 CONFIG_IRLPT_CLIENT
11691 Say Y here if you want to build support for the IrLPT client
11692 protocol. If you want to compile it as a module, say M here and read
11693 Documentation/modules.txt. The IrLPT client protocol can be used to
11694 print documents to IrDA compatible printers like the HP-5MP, or
11695 IrLPT printer adapters like the ACTiSYS IR-100M.
11697 IrLPT Server Protocol
11698 CONFIG_IRLPT_SERVER
11699 Say Y here if you want to build support for the IrLPT server
11700 protocol. If you want to compile it as a module, say M here and read
11701 Documentation/modules.txt. The IrLPT server protocol makes it
11702 possible to use a Linux machine as an infrared printer server for
11703 other laptops. So if your Linux machine has a cable connection to a
11704 printer, then other laptops can use the Linux machine to print out
11705 documents using infrared communication.
11707 IrTTY IrDA Device Driver
11709 Say Y here if you want to build support for the IrTTY line
11710 discipline. If you want to compile it as a module, say M here and
11711 read Documentation/modules.txt. IrTTY makes it possible to use
11712 Linux's own serial driver for all IrDA ports that are 16550
11713 compatible. Most IrDA chips are 16550 compatible so you should
11714 probably say Y to this option. Using IrTTY will however limit the
11715 speed of the connection to 115200 bps (IrDA SIR mode)
11719 IrPORT IrDA Device Driver
11721 Say Y here if you want to build support for the IrPORT IrDA device
11722 driver. If you want to compile it as a module, say M here and
11723 read Documentation/modules.txt. IrPORT can be used instead of
11724 IrTTY and sometimes this can be better. One example is if your
11725 IrDA port does not have echo-canceling, which will work OK with
11726 IrPORT since this driver is working in half-duplex mode only. You
11727 don't need to use irattach with IrPORT, but you just insert it
11728 the same way as FIR drivers (insmod irport io=0x3e8 irq=11).
11729 Notice that IrPORT is a SIR device driver which means that speed
11730 is limited to 115200 bps.
11734 Winbond W83977AF IrDA Device Driver
11736 Say Y here if you want to build IrDA support for the Winbond
11737 W83977AF super-io chipset. If you want to compile it as a module,
11738 say M here and read Documentation/modules.txt. This driver should be
11739 used for the IrDA chipset in the Corel NetWinder. The driver
11740 supports SIR, MIR and FIR (4Mbps) speeds.
11742 NSC PC87108 IrDA Device Driver
11744 Say Y here if you want to build support for the NSC PC87108 IrDA
11745 chipset. If you want to compile it as a module, say M here and
11746 read Documentation/modules.txt. This drivers currently only supports
11747 the ACTiSYS IR2000B ISA card and supports SIR, MIR and FIR (4Mbps)
11750 Sharp UIRCC IrDA Device Driver
11752 Say Y here if you want to build support for the Sharp UIRCC IrDA
11753 chipset. If you want to compile it as a module, say M here and
11754 read Documentation/modules.txt. This chipset is used by the Toshiba
11757 Toshiba Type-O IR Port Device Driver
11759 Say Y here if you want to build support for the Toshiba Type-O IR
11760 chipset. If you want to compile it as a module, say M here and
11761 read Documentation/modules.txt. This chipset is used by the Toshiba
11762 Libretto 100CT, and many more laptops.
11764 ESI JetEye PC Dongle
11766 Say Y here if you want to build support for the Extended Systems
11767 JetEye PC dongle. If you want to compile it as a module, say M here
11768 and read Documentation/modules.txt. The ESI dongle attaches to the
11769 normal 9-pin serial port connector, and can currently only be used
11770 by IrTTY. To activate support for ESI dongles you will have to
11771 insert "irattach -d esi" in the /etc/irda/drivers script.
11773 ACTiSYS IR-220L and IR220L+ dongle
11774 CONFIG_ACTISYS_DONGLE
11775 Say Y here if you want to build support for the ACTiSYS
11776 IR-220L and IR220L+ dongles. If you want to compile it as a module,
11777 say M here and read Documentation/modules.txt. The ACTiSYS dongles
11778 attaches to the normal 9-pin serial port connector, and can
11779 currently only be used by IrTTY. To activate support for ACTiSYS
11780 dongles you will have to insert "irattach -d actisys" or
11781 "irattach -d actisys_plus" in the/etc/irda/drivers script.
11783 Tekram IrMate 210B dongle
11784 CONFIG_TEKRAM_DONGLE
11785 Say Y here if you want to build support for the Tekram IrMate 210B
11786 dongle. If you want to compile it as a module, say M here
11787 and read Documentation/modules.txt. The Tekram dongle attaches to
11788 the normal 9-pin serial port connector, and can currently only be
11789 used by IrTTY. To activate support for Tekram dongles you will have
11790 to insert "irattach -d tekram" in the /etc/irda/drivers script.
11792 Greenwich GIrBIL dongle
11793 CONFIG_GIRBIL_DONGLE
11794 Say Y here if you want to build support for the Greenwich GIrBIL
11795 dongle. If you want to compile it as a module, say M here and read
11796 Documentation/modules.txt. The Greenwich dongle attaches to the
11797 normal 9-pin serial port connector, and can currently only be used
11798 by IrTTY. To activate support for Greenwich dongles you will have to
11799 insert "irattach -d girbil" in the /etc/irda/drivers script.
11801 Parallax Litelink dongle
11802 CONFIG_LITELINK_DONGLE
11803 Say Y here if you want to build support for the Parallax Litelink
11804 dongle. If you want to compile it as a module, say M here and read
11805 Documentation/modules.txt. The Parallax dongle attaches to the
11806 normal 9-pin serial port connector, and can currently only be used
11807 by IrTTY. To activate support for Parallax dongles you will have to
11808 insert "irattach -d litelink" in the /etc/irda/drivers script.
11810 VME (Motorola and BVM) support
11812 Say Y here if you want to build a kernel for a 680x0 based VME
11813 board. Boards currently supported include Motorola boards MVME162,
11814 MVME166, MVME167, MVME172, and MVME177. BVME4000 and BVME6000
11815 boards from BVM Ltd are also supported.
11817 MVME162, 166 and 167 support
11819 Say Y to include support for Motorola VME boards. This will build a
11820 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
11821 MVME177 boards. If you select this option you will have to select
11822 the appropriate drivers for SCSI, Ethernet and serial ports later
11825 BVME4000 and BVME6000 support
11827 Say Y to include support for VME boards from BVM Ltd. This will
11828 build a kernel which can run on BVME4000 and BVME6000 boards. If
11829 you select this option you will have to select the appropriate
11830 drivers for SCSI, Ethernet and serial ports later on.
11832 Use write-through caching for 68060 supervisor accesses
11833 CONFIG_060_WRITETHROUGH
11834 The 68060 generally uses copyback caching of recently accessed data.
11835 Copyback caching means that memory writes will be held in an on-chip
11836 cache and only written back to memory some time later. Saying Y
11837 here will force supervisor (kernel) accesses to use writethrough
11838 caching. Writethrough caching means that data is written to memory
11839 straight away, so that cache and memory data always agree.
11840 Writethrough caching is less efficient, but is needed for some
11841 drivers on 68060 based systems where the 68060 bus snooping signal
11842 is hardwired on. The 53c710 SCSI driver is known to suffer from
11845 NCR53C710 SCSI driver for MVME16x
11846 CONFIG_MVME16x_SCSI
11847 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
11848 SCSI controller chip. Almost everyone using one of these boards
11849 will want to say Y to this question.
11851 NCR53C710 SCSI driver for BVME6000
11852 CONFIG_BVME6000_SCSI
11853 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
11854 SCSI controller chip. Almost everyone using one of these boards
11855 will want to say Y to this question.
11857 MVME16x Ethernet support
11859 This is the driver for the Ethernet interface on the Motorola
11860 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
11861 driver for this chip in your kernel. If you want to compile it as
11862 a module, say M here and read Documentation/modules.txt.
11864 BVME6000 Ethernet support
11865 CONFIG_BVME6000_NET
11866 This is the driver for the Ethernet interface on BVME4000 and
11867 BVME6000 VME boards. Say Y here to include the driver for this chip
11868 in your kernel. If you want to compile it as a module, say M here
11869 and read Documentation/modules.txt.
11871 CD2401 support for MVME166/7 serial ports
11873 This is the driver for the serial ports on the Motorola MVME166,
11874 167, and 172 boards. Everyone using one of these boards should say
11877 SCC support for MVME162 serial ports
11879 This is the driver for the serial ports on the Motorola MVME162 and
11880 172 boards. Everyone using one of these boards should say Y here.
11882 SCC support for BVME6000 serial ports
11883 CONFIG_BVME6000_SCC
11884 This is the driver for the serial ports on the BVME4000 and BVME6000
11885 boards from BVM Ltd. Everyone using one of these boards should say
11888 Universal Serial Bus (USB) Support (Experimental)
11890 This will enable support for the Universal Serial Bus (USB). USB
11891 allows you to connect up to 127 external devices such as keyboards,
11892 mice, printers and modems to your computer through a USB connector.
11893 This code can also be built as a module (i.e. code outside the
11894 kernel that can be added and removed at runtime), consult
11895 Documentation/modules.txt for more information.
11897 UHCI (intel PIIX4 and others) support
11899 The UHCI is the USB host controller for many computers, and is built
11900 into all recent boards with intel PCI chipsets. This driver is
11901 needed for these motherboards to support USB.
11903 OHCI (compaq and some others) support
11905 The OHCI (Open Host Controller Interface) is the USB host controller
11906 on most non-Intel architectures, several USB-adding PCI cards, and
11907 is on several x86 compatibles with non-Intel chipsets. This driver
11908 is needed for these motherboards to support USB. There is presently
11909 two OHCI drivers in development. Say 'N' here if you would like to
11910 compile the other OHCI driver into the linux kernel.
11912 OHCI-HCD (other OHCI opt. Virt. Root Hub) support
11913 CONFIG_USB_OHCI_HCD
11914 The OHCI (Open Host Controller Interface) is the USB host controller
11915 on most non-Intel architectures, several USB-adding PCI cards, and
11916 is on several x86 compatibles with non-Intel chipsets. This driver
11917 is needed for these motherboards to support USB. There is presently
11918 two OHCI drivers in development.
11922 To expand beyond the USB ports on the computer, a device called a
11923 hub is used. This driver supports hubs, allowing them to be used.
11928 This driver allows mice to work under the USB stack. It currently
11929 patches into /dev/ps2aux, although it does not require the ps2
11930 mouse code to be included in the kernel as well.
11932 USB keyboard support
11934 This driver allows USB keyboards to work under the USB stack.
11936 USB audio parsing support (Preliminary)
11938 This driver will eventually handle audio devices, such
11941 USB Abstract Control Model support (Preliminary)
11943 This driver allows for devices which support the Abstract Control Model,
11944 including many USB-based modems, ISDN adapters, and network adapters.
11946 USB /proc filesystem entry support (Preliminary)
11948 This reports USB drivers and devices in the /proc filesystem.
11949 Entries are located in /proc/bus/usb.
11950 Note that you must enable support for the proc filesystem
11953 Support for user-space parallel port device drivers
11955 Saying Y to this adds support for /dev/parport device nodes. This
11956 is needed for programs that want low-level access to the parallel
11957 port, for instance deviceid (which displays Plug-and-Play device
11958 IDs) and vlp (which makes a Linux computer act as though it's a
11961 This is the parallel port equivalent of SCSI generic support (sg).
11962 It is safe to say N to this -- it is not needed for normal printing
11963 or parallel port CD-ROM/disk support.
11966 # A couple of things I keep forgetting:
11967 # capitalize: AppleTalk, Ethernet, DOS, DMA, FAT, FTP, Internet,
11968 # Intel, IRQ, Linux, MSDOS, NetWare, NetWinder, NFS,
11970 # two words: hard drive, hard disk, sound card, home page
11971 # other: it's safe to save; daemon; use --, not - or ---
11974 # This is used by Emacs' spell checker ispell.el:
11976 # LocalWords: CONFIG coprocessor DX Pentium SX lilo loadlin HOWTO ftp metalab
11977 # LocalWords: unc edu docs emu README kB BLK DEV FD Thinkpad fd MFM RLL IDE gz
11978 # LocalWords: cdrom diskless netboot nfs xzvf ATAPI MB ide pavia rubini pl pd
11979 # LocalWords: HD CDROMs IDECD NEC MITSUMI filesystem XT XD PCI BIOS cezar ATEN
11980 # LocalWords: ISA EISA Microchannel VESA BIOSes IPC SYSVIPC ipc Ctrl dmesg hlt
11981 # LocalWords: BINFMT Linkable http ac uk jo html GCC SPARC AVANTI CABRIOLET EB
11982 # LocalWords: netscape gcc LD CC toplevel MODVERSIONS insmod rmmod modprobe IP
11983 # LocalWords: genksyms INET loopback gatewaying ethernet PPP ARP Arp MEMSIZE
11984 # LocalWords: howto multicasting MULTICAST MBONE firewalling ipfw ACCT resp ip
11985 # LocalWords: proc acct IPIP encapsulator decapsulator klogd PCTCP RARP EXT PS
11986 # LocalWords: telnetting subnetted NAGLE rlogin NOSR ttyS TGA techinfo mbone nl
11987 # LocalWords: Mb SKB IPX Novell dosemu Appletalk DDP ATALK vmalloc visar ehome
11988 # LocalWords: SD CHR scsi thingy SG CD LUNs LUN jukebox Adaptec BusLogic EATA
11989 # LocalWords: buslogic DMA DPT ATT eata dma PIO UltraStor fdomain umsdos ext
11990 # LocalWords: QLOGIC qlogic TMC seagate Trantor ultrastor FASST wd NETDEVICES
11991 # LocalWords: unix BBS linux CSLIP PLIP Kirch's LDP CSlip SL SCC IRQ csustan
11992 # LocalWords: Turbo Laplink plip NCSA port's ReQuest IRQs EQL SMC AMD PCnet NE
11993 # LocalWords: COM ELPLUS Com EtherLinkIII VLB Arcnet Cabletron DEPCA DE carlos
11994 # LocalWords: depca EtherWorks EWRK ewrk SEEQ EtherExpress EEXPRESS NI xxx dia
11995 # LocalWords: EtherExpress WaveLAN wavelan PCLAN HPLAN VG SK Ansel Xen de ZNET
11996 # LocalWords: PCMCIA cb stanford LAN TEC RealTek ATP atp DLINK NetTools VISWS
11997 # LocalWords: TR Sony CDU caddyless cdu Mitsumi MCD cd mcd XA MultiSession CDA
11998 # LocalWords: Matsushita Panasonic SBPCD Soundblaster Longshine sbpcd Aztech
11999 # LocalWords: Okano Wearnes AZTCD CDD SE aztcd sonycd Goldstar GSCD Philips fs
12000 # LocalWords: LMS OPTCD Sanyo SJCD minix faqs xiafs XIA msdos mtools Cichocki
12001 # LocalWords: std softlinks umssync NetworkFileSharing nfsd mountd CDs HPFS TI
12002 # LocalWords: hpfs SYSV SCO iBCS Wyse WordPerfect tsx mit unixes sysv NR irisa
12003 # LocalWords: SMB WfW Cyclades async mux Logitech busmouse MouseSystem aka AST
12004 # LocalWords: PSMOUSE Compaq trackballs Travelmate Inport ATIXL ATI busmice ld
12005 # LocalWords: gpm config QIC DYNCONF FTAPE Stor Ftape ftape pcsndrv manpage NT
12006 # LocalWords: readprofile diskdrives org com masq EtherTalk tcp netrom sunacm
12007 # LocalWords: misc AIC aic pio scc Portmaster eql GIS PhotoCDs MCDX Perell PG
12008 # LocalWords: mcdx gscd optcd sjcd ISP hdparm Workgroups Lan samba PARIDE PCD
12009 # LocalWords: filesystems smbfs ATA ppp PCTech RZ www powerquest txt CMD ESDI
12010 # LocalWords: chipset FB multicast MROUTE appletalk ifconfig IBMTR multiport
12011 # LocalWords: Multisession STALDRV EasyIO EC EasyConnection ISTALLION ONboard
12012 # LocalWords: Brumby pci TNC cis ohio faq usenet NETLINK dev hydra ca Tyne mem
12013 # LocalWords: carleton Deskstation DECstation SUNFD JENSEN Noname XXXM SLiRP
12014 # LocalWords: pppd Zilog ZS SRM bootloader ez mainmenu rarp ipfwadm paride pcd
12015 # LocalWords: RTNETLINK mknod xos MTU lwared Macs mac netatalk macs cs Wolff
12016 # LocalWords: dartmouth flowerpt MultiMaster FlashPoint tudelft etherexpress
12017 # LocalWords: ICL EtherTeam ETH IDESCSI TXC SmartRAID SmartCache httpd sjc dlp
12018 # LocalWords: thesphere TwoServers BOOTP DHCP ncpfs BPQETHER BPQ MG HIPPI cern
12019 # LocalWords: bsd comp SPARCstation le SunOS ie Gracilis PackeTwin PT pt LU FX
12020 # LocalWords: FX TEAC CR LCS mS ramdisk IDETAPE cmd fperllo encis tcfs unisa
12021 # LocalWords: Vertos Genoa Funai hsfs NCP NetWare tgz APM apm ioctls UltraLite
12022 # LocalWords: TravelMate CDT LCD backlight VC RPC Mips AXP barlow cdrecord pg
12023 # LocalWords: PMAX MILO Alphas Multia Tseng linuxelf endian mipsel mips drv HT
12024 # LocalWords: kerneld callouts AdvanSys advansys Admin WDT DataStor EP verden
12025 # LocalWords: wdt hdb hdc bugfix SiS vlb Acculogic CSA DTC dtc Holtek ht QDI
12026 # LocalWords: QD qd UMC umc ALI ali lena fnet fr azstarnet cdr fb MDA ps esdi
12027 # LocalWords: Avanti XL AlphaStations Jensen DECpc AXPpci UDB Cabriolet MCA RC
12028 # LocalWords: AlphaPC mca AOUT OUTput PPro sipx gwdg lo nwe FourPort Boca unm
12029 # LocalWords: Keepalive linefill RELCOM keepalive analogue CDR conf CDI INIT
12030 # LocalWords: OPTi isp irq noisp VFAT vfat NTFS losetup dmsdosfs dosfs ISDN MP
12031 # LocalWords: NOWAYOUT behaviour dialin isdn callback BTX Teles ICN EDSS Cisco
12032 # LocalWords: ipppd syncppp RFC MPP VJ downloaded icn NICCY Creatix shmem ufr
12033 # LocalWords: ibp md ARCnet ether encap NDIS arcether ODI Amigas AmiTCP NetBSD
12034 # LocalWords: initrd tue util DES funet des OnNet BIOSP smc Travan Iomega CMS
12035 # LocalWords: FC DC dc PPA IOMEGA's ppa RNFS FMV Fujitsu ARPD arpd loran layes
12036 # LocalWords: FRAD indiana framerelay DLCI DCLIs Sangoma SDLA mrouted sync sec
12037 # LocalWords: Starmode Metricom MosquitoNet mosquitonet kbit nfsroot Digiboard
12038 # LocalWords: DIGI Xe Xeve digiboard UMISC touchscreens mtu ethernets HBAs MEX
12039 # LocalWords: Shifflett netcom js jshiffle WIC DECchip ELCP EtherPower dst RTC
12040 # LocalWords: rtc SMP lp Digi Intl RightSwitch DGRS dgrs AFFS Amiga UFS SDL AP
12041 # LocalWords: Solaris RISCom riscom syncPPP PCBIT pcbit sparc anu au artoo MFB
12042 # LocalWords: hitchcock Crynwr cnam pktdrvr NCSA's CyDROM CyCDROM FreeBSD NeXT
12043 # LocalWords: NeXTstep disklabel disklabels SMD FFS tm AmigaOS diskfiles Un IQ
12044 # LocalWords: Bernd informatik rwth aachen uae affs multihosting bytecode java
12045 # LocalWords: applets applet JDK ncsa cabi SNI Alphatronix readme LANs scarab
12046 # LocalWords: winsock RNIS caltech OSPF honour Honouring Mbit LocalTalk DEFRAG
12047 # LocalWords: localtalk download Packetwin Baycom baycom interwork ASCII JNT
12048 # LocalWords: Camtec proxying indyramp defragment defragmented UDP FAS FASXX
12049 # LocalWords: FastSCSI SIO FDC qlogicfas QLogic qlogicisp setbaycom ife ee LJ
12050 # LocalWords: ethz ch Travelmates ProAudioSpectrum ProAudio SoundMan SB SBPro
12051 # LocalWords: Thunderboard SM OPL FM ADLIB TSR Gravis MPU PSS ADI SW DSP codec
12052 # LocalWords: ADSP ESC ASIC daughtercard GUSMAX MSS NX AdLib Excell Ensoniq YM
12053 # LocalWords: SoundScape Spea MediaTriX AudioTriX WSS OTI ThunderBoard VoxWare
12054 # LocalWords: Soundscape SSCAPE TRIX MediaTrix PnP Maui dsp midixx EIA getty
12055 # LocalWords: mgetty sendfax gert greenie muc lowlevel Lasermate LanManager io
12056 # LocalWords: OOPSes trackball binghamton mobileip ncr IOMAPPED settags ns ser
12057 # LocalWords: setsync NEGO MPARITY autotuning prefetch PIIX cdwrite utils rc
12058 # LocalWords: PCWATCHDOG berkprod bitgate boldt ucsb jf kyoto jp euc Tetsuyasu
12059 # LocalWords: YAMADA tetsu cauchy nslab ntt nevod perm su doc kaf kheops wsc
12060 # LocalWords: traduc Bourgin dbourgin menuconfig kfill READMEs HOWTOs Virge WA
12061 # LocalWords: IDEDISK IDEFLOPPY EIDE firewalls QMAGIC ZMAGIC LocalWords opti
12062 # LocalWords: SVGATextMode vga svga Xkernel syr jmwobus comfaqs dhcp flakey GD
12063 # LocalWords: IPv IPng interoperability ipng ipv radio's tapr pkthome PLP nano
12064 # LocalWords: Ses Mhz sethdlc SOUNDMODEM WindowsSoundSystem smdiag pcf inka ES
12065 # LocalWords: smmixer ptt circ soundmodem MKISS FDDI DEFEA DEFPA DEFXX redhat
12066 # LocalWords: HyperNews khg mconv sed lina wuftpd MicroChannel netlink irc cum
12067 # LocalWords: raudio RealAudio PPROP NETBIOS GUI IBMMCA ELMC Racal Interlan fi
12068 # LocalWords: eth shapecfg src esp PCWD PREVSTAT bootparam sig bitwizard SBC
12069 # LocalWords: downloads AFSK TCM FP Karn KA FSK RUH LinkSys cron mouseman LLC
12070 # LocalWords: SyQuest SyQuest's CCITT MicroSolutions BPCD bpcd ESPSERIAL PROM
12071 # LocalWords: SUNESP openprom OPENPROMIO quango themall al TT MC MMU LC RMW AA
12072 # LocalWords: INSNS Ataris AutoConfig ZORRO OCS AMIFB Agnus Denise ECS CDTV GB
12073 # LocalWords: AGA Cybervision CYBER GSP TMS DMI Zorro ACSI ROMs SLM BioNet GVP
12074 # LocalWords: PAMsNet TekMagic Cyberstorm MkI CYBERSTORMII MkII BLZ onboard cx
12075 # LocalWords: Village Tronic ATARILANCE RieblCard PAMCard VME MFP sangoma LAPB
12076 # LocalWords: Rhotron BioData's Multiface AMIGAMOUSE COPCON Amiga's bitplanes
12077 # LocalWords: ATARIMOUSE MFPSER SCC's MegaSTE ESCC Atari's GVPIOEXT DMASOUND
12078 # LocalWords: fdutils cisco univercd rpcg htm iface lapb LAPBETHER tpqic qic
12079 # LocalWords: SYNTH xd en binfmt aout ipip terra ipx sd sr sg wic framebuffer
12080 # LocalWords: ibmmca lapbether mkiss dlci sdla fmv eepro eexpress ni hp ne es
12081 # LocalWords: ibmtr isofs ROMFS romfs pcxx cyclades istallion psaux msbusmouse
12082 # LocalWords: atixlmouse sbin softdog pcwd USS Lite ACI miroSOUND PCM miroPCM
12083 # LocalWords: microcontroller miro Voxware downloading teles acsi slm gvp ltpc
12084 # LocalWords: atari ariadne amigamouse atarimouse builtin IPDDP maths bradford
12085 # LocalWords: AppleTalk Farallon PhoneNet Zubkoff lnz SCCB HAPN WANs vesafb nt
12086 # LocalWords: wanrouter WANPIPE multiprotocol Mbps wanpipe EtherWORKS nodma SC
12087 # LocalWords: smp HiSax SiemensChipSet Siemens AVM Elsa ITK hisax PCC MICROR
12088 # LocalWords: Mircolink EURO DSS Spellcaster BRI sc spellcast Digiboards GPIO
12089 # LocalWords: SYMBIOS COMPAT SDMS rev ASUS Tekram HX VX API ibmmcascsi ASY asy
12090 # LocalWords: loader's PCnetPCI automounter AUTOFS amd autofs VT Gallant's Pnp
12091 # LocalWords: AEDSP aedsp enskip tik Sysctl sysctl PARPORT parport pnp IDs EPP
12092 # LocalWords: Autoprobe bart patrickr HDLS READBACK AB usr DAMA DS SparQ aten
12093 # LocalWords: Symbios PCscsi tmscsim RoamAbout GHz Hinds contrib mathematik ok
12094 # LocalWords: darmstadt okir DIGIEPCA International's Xem digiepca epca bootup
12095 # LocalWords: zorro CAPI AVMB capi avmb VP SYN syncookies EM em pc Ethertalk
12096 # LocalWords: Dayna DL Daynatalk LT PhoneNET ATB Daystar queueing CMDS SCBs ls
12097 # LocalWords: SCB STATS Thinnet ThunderLAN TLAN Netelligent NetFlex tlan james
12098 # LocalWords: caldera Preload Preloading slowdowns schoebel uni NBD nbd prog
12099 # LocalWords: stuttgart rdist TRANS hostnames mango jukeboxes ESS userland PD
12100 # LocalWords: hardlinked NAMETRANS env mtab fstab umount nologin runlevel gid
12101 # LocalWords: transname filespace adm Nodename hostname uname Kernelname bootp
12102 # LocalWords: KERNNAME kname ktype kernelname Kerneltype KERNTYPE Alt RX mdafb
12103 # LocalWords: dataless kerneltype SYSNAME Comtrol Rocketport palmtop fbset EGS
12104 # LocalWords: nvram SYSRQ SysRq PrintScreen sysrq NVRAMs NvRAM Shortwave RTTY
12105 # LocalWords: HFMODEM shortwave Sitor Amtor Pactor GTOR hfmodem hayes TX TMOUT
12106 # LocalWords: IDEPCI IDEDMA idedma PDC pdc TRM trm raidtools luthien nuclecu
12107 # LocalWords: unam mx miguel koobera uic EMUL solaris pp ieee lpsg co DMAs TOS
12108 # LocalWords: BLDCONFIG preloading jumperless BOOTINIT modutils multipath GRE
12109 # LocalWords: misconfigured autoconfiguration IPGRE ICMP tracert ipautofw PIM
12110 # LocalWords: netis rlynch autofw ipportfw monmouth ipsubs portforwarding pimd
12111 # LocalWords: portfw PIMSM netweb usc pim pf EUI aggregatable PB decapsulate
12112 # LocalWords: ipddp Decapsulation DECAP bool HAMRADIO tcpdump af CDs tx FBCON
12113 # LocalWords: ethertap multisession PPC MMIO GDT GDTH ICP gdth hamradio bpp
12114 # LocalWords: lmh weejock AIMSlab RadioTrack RTRACK HZP OptoSCC TRX rx TRXECHO
12115 # LocalWords: DMASCC paccomm dmascc addr cfg oevsv oe kib picpar FDX baudrate
12116 # LocalWords: baudrates fdx HDX hdx PSK kanren frforum QoS SCHED CBQ SCH sched
12117 # LocalWords: sch cbq CSZ Shenker Zhang csz SFQ sfq TBF tbf PFIFO fifo PRIO RW
12118 # LocalWords: prio Micom xIO dwmw rimi OMIRR omirr omirrd unicode ntfs cmu NIC
12119 # LocalWords: Braam braam Schmidt's freiburg nls codepages codepage Romanian
12120 # LocalWords: Slovak Slovenian Sorbian Nordic iso Catalan Faeroese Galician SZ
12121 # LocalWords: Valencian Slovene Esperanto Estonian Latvian Byelorussian KOI mt
12122 # LocalWords: charset Inuit Greenlandic Sami Lappish koi SOFTCURSOR softcursor
12123 # LocalWords: Specialix specialix DTR RTS RTSCTS cycladesZ Exabyte ftape's inr
12124 # LocalWords: Iomega's LBFM claus ZFTAPE VFS zftape zft William's lzrw DFLT kb
12125 # LocalWords: MTSETBLK MTIOCTOP qft setblk zftape's tar's afio's setdrvbuffer
12126 # LocalWords: Procfs Exabyte's THR FCD sysvinit init PSC pscwdt VMIDI Euro SAB
12127 # LocalWords: Mostek Fastlane PowerMac PReP PMAC PowerPC Macintoshes Starmax
12128 # LocalWords: PowerStack Starmaxes MCOMMON DEVICETREE ATY IMS IMSTT videodev
12129 # LocalWords: BT Hauppauge STB bttv Quickcam BW BWQCAM bw qcam Mediavision PMS
12130 # LocalWords: pms Avatar Freecom Imation Superdisk BPCK bpck COMM comm DSTR ru
12131 # LocalWords: dstr EPAT EPEZ epat EPIA epia FreeCom FRPW frpw KingByte KBIC HW
12132 # LocalWords: KingByte's kbic OnSpec ValuStore FASTROUTE fastroute FLOWCONTROL
12133 # LocalWords: struct APIC realtime OSs LynxOS CNC tmp cvf HFS hfs ADFS Risc os
12134 # LocalWords: adfs ncpmount namespace SUBDIR reexport NDS kcore FT SPX spx DAT
12135 # LocalWords: interserver BLKSZ NUMBUFFERS apmd Tadpole ANA roestock QuickCam
12136 # LocalWords: isapnptools Colour CQCAM colour Connectix QuickClip prive mentre
12137 # LocalWords: KMOD kmod conformant utexas kharker UnixWare Mwave cgi cl ts ibm
12138 # LocalWords: eXchange threepio oakland simtel pre ULTRAMCA EtherLink isa luik
12139 # LocalWords: EtherLink OpenBSD pts DEVPTS devpts ptmx ttyp glibc readback SA
12140 # LocalWords: mwave OLDCARD isdnloop linklevel loopctrl Eicon Diehl DIEHLDIVA
12141 # LocalWords: ASUSCOM AsusCom TELEINT semiactiv Sedlbauer Sportster TA MIC ITH
12142 # LocalWords: NETjet NetJet Niccy Neuhaus sparcs AOC AOCD AOCE Microlink SAA
12143 # LocalWords: teletext WinTV saa iproute tc Quadra Performa PowerBook tor AUN
12144 # LocalWords: setserial compsoc steve Econet econet AUNUDP psched TEQL TLE CLS
12145 # LocalWords: teql FW Ingres TwistedPair MTRR MTRRs mtrr cfs crypto TD ktti KT
12146 # LocalWords: PHd ICS ipchains adelaide rustcorp syslog Cumana steganography
12147 # LocalWords: AcornSCSI EcoSCSI EESOX EESOXSCSI Powertec POWERTECSCSI dec SF
12148 # LocalWords: RadioReveal gatekeeper aimslab aztech FMI sf fmi RTL rtl cesdis
12149 # LocalWords: Yellowfin gsfc nasa gov yellowfin pcnet Mylex LNE lne EtherH hs
12150 # LocalWords: EBSA chattr RiscOS Winmodem AGP Atomwide DUALSP pcsp robinson CT
12151 # LocalWords: SGALAXY Waverider DSPxxx TRXPRO AudioTrix OSWF MOT CFB DSY kbps
12152 # LocalWords: tuwien kkudielk LVD mega lun MAXTAGS Gbps arcnet Olicom SKTR SNA
12153 # LocalWords: SysKonnect sktr sna etherboot ufs NetBEUI MultiSound MSNDCLAS GX
12154 # LocalWords: MSNDINIT MSNDPERM MSNDPIN PNDSPINI PNDSPERM Ensoniq's RetinaZ SS
12155 # LocalWords: AudioPCI lspci SonicVibes sonicvibes SPARCs roadrunner CLgen UPA
12156 # LocalWords: swansea shtml Zoltrix zoltrix BINUTILS EGCS binutils VIDC DACs
12157 # LocalWords: CyberVision Cirrus PowerBooks Topcat SBUS CGsix TurboGX BWtwo SS
12158 # LocalWords: CGthree TCX unswapable vfb fbcon hicolor truecolor AFB ILBM SOC
12159 # LocalWords: IPLAN gracilis Fibre SBus SparcSTORAGE SV jnewbigin swin QNX qnx
12160 # LocalWords: PTY PTYS ptyxx ttyxx PTYs ssh sb Avance ALS pss pvv kerneli hd
12161 # LocalWords: synth WaveFront MSND NONPNP AudioExcelDSP STRAM APUS CHRP MBX Nx
12162 # LocalWords: PowerMac's BMAC radiotrack rtrack miropcm OFFBOARD HPT UDMA DVD
12163 # LocalWords: hpt fokus gmd Cyrix DXL SLC DLC NexGen MediaGX GXm IDT WinChip
12164 # LocalWords: MMX MII valkyrie mdacon vdolive VDOLive cuseeme CU hippi rrunner
12165 # LocalWords: SeeMe ipmasqadm juanjox ipmarkfw markfw TNCs Microdyne rhine lib
12166 # LocalWords: libc jsX gamepad gameport CHF FCS FPGaming MadCatz ASSASIN GrIP
12167 # LocalWords: Assasin gamepads GamePad PDPI gamecards gamecard WingMan BSP WCS
12168 # LocalWords: ThunderPad CyberMan SideWinder ThrustMaster DirectConnect NES XF
12169 # LocalWords: Millenium SNES PSX Multisystem Nintendo PlayStation Amstrad CPC
12170 # LocalWords: Sega TurboGraFX Steffen Schwenke Multiststem PDIF FIFOSIZE EPLUS
12171 # LocalWords: PowerUP RoadRunner tahallah dos functionkey setterm imladris Woz
12172 # LocalWords: PowerMacs Winbond Algorithmics ALGOR algor ECOFF IRIX SGI SGI's
12173 # LocalWords: gfx virtualized Xpmac mklinux XFree FBDev Woodhouse mvhi Seeq fp
12174 # LocalWords: SGISEEQ HIgh ADB ADBMOUSE crosscompiler CROSSCOMPILE FPE GDB gdb
12175 # LocalWords: JOYPORT rp spoofing DawiControl NOGENSUPP EEPROM HSSI Alessandro
12176 # LocalWords: singleprocessor tex MATHEMU FRIQ Maxell friq Alcor XLT AlphaBook
12177 # LocalWords: AlphaPCI DP LX Miata Mikasa Noritake RPX UX BX Takara EV PRIMO
12178 # LocalWords: TSC Matrox Productiva matroxfb matrox multihead ia linuxhq MFW
12179 # LocalWords: mfw AAA MCS Initio XXU initio imm AutoDetect IZIP CTR usec HDLC
12180 # LocalWords: COSA SRP muni cz kas cosa Alteon AceNIC acenic VTOC OSes GMT SAx
12181 # LocalWords: Inspiron localtime INTS Thinkpads Ralf Brown's Flightstick NNN
12182 # LocalWords: Xterminator Blackhawk NN mpu ioports DCA HPDCA HPLANCE DIO Corel
12183 # LocalWords: GemTek gemtek CMDLINE IrDA PDA's irmanager irattach RR AVA DN rg
12184 # LocalWords: uit dagb irda LSAP IrLMP RR's IrLAP IR alloc skb's kfree skb's
12185 # LocalWords: GZIP IrLAN NetbeamIR ESI JetEye IrOBEX IrCOMM TTY's minicom dti
12186 # LocalWords: ircomm ircomm pluto thiguchi IrTTY Linux's bps NetWinder MIR NSC
12187 # LocalWords: ACTiSYS Dongle dongle dongles esi actisys IrMate tekram BVM MVME
12188 # LocalWords: BVME BVME WRITETHROUGH copyback writethrough fwmark syncookie tu
12189 # LocalWords: alphalinux GOBIOS csn chemnitz nat ACARD AMI MegaRAID megaraid
12190 # LocalWords: QNXFS ISI isicom xterms Apollos VPN RCPCI rcpci sgi visws pcmcia
12191 # LocalWords: IrLPT UIRCC Tecra