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.3.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.
173 This option is required if you want to utilize physical memory which
174 is not covered by the kernel virtual address space (> 1GB).
176 Normal PC floppy disk support
178 If you want to use the floppy disk drive(s) of your PC under Linux,
179 say Y. Information about this driver, especially important for IBM
180 Thinkpad users, is contained in drivers/block/README.fd. This file
181 also contains the location of the Floppy driver FAQ as well as
182 location of the fdutils package used to configure additional
183 parameters of the driver at run time.
185 This driver is also available as a module ( = code which can be
186 inserted in and removed from the running kernel whenever you want).
187 The module will be called floppy.o. If you want to compile it as a
188 module, say M here and read Documentation/modules.txt.
190 Support for PowerMac floppy
192 If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
193 floppy controller, say Y here. Most commonly found in PowerMacs.
197 Saying Y here will allow you to use a portion of your RAM memory as
198 a block device, so that you can make filesystems on it, read and
199 write to it and do all the other things that you can do with normal
200 block devices (such as hard drives). It is usually used to load and
201 store a copy of a minimal root file system off of a floppy into RAM
202 during the initial install of Linux.
204 Note that the kernel command line option "ramdisk=XX" is now
205 obsolete. For details, read Documentation/ramdisk.txt.
207 If you want to compile this as a module ( = code which can be
208 inserted in and removed from the running kernel whenever you want),
209 say M and read Documentation/modules.txt. The module will be called
212 Most normal users won't need the RAM disk functionality, and can
215 Initial RAM disk (initrd) support
216 CONFIG_BLK_DEV_INITRD
217 The initial RAM disk is a RAM disk that is loaded by the boot loader
218 (loadlin or lilo) and that is mounted as root before the normal boot
219 procedure. It is typically used to load modules needed to mount the
220 "real" root file system, etc. See Documentation/initrd.txt for
225 Saying Y here will allow you to use a regular file as a block
226 device; you can then create a file system on that block device and
227 mount it just as you would mount other block devices such as hard
228 drive partitions, CDROM drives or floppy drives.
230 This is useful if you want to check an ISO 9660 file system before
231 burning the CD, or if you want to use floppy images without first
232 writing them to floppy.
234 The loop device driver can also be used to "hide" a filesystem in a
235 disk partition, floppy, or regular file, either using encryption
236 (scrambling the data) or steganography (hiding the data in the low
237 bits of, say, a sound file). This is also safe if the file resides
238 on a remote file server. If you want to do this, you will first have
239 to acquire and install a kernel patch from
240 ftp://ftp.replay.com/pub/crypto/linux/all or
241 ftp://verden.pvv.org/pub/linux/kerneli/v2.1/, and then you need to
242 say Y to this option.
244 Note that alternative ways to use encrypted filesystems are provided
245 by the cfs package, which can be gotten via FTP (user: anonymous)
246 from ftp://ftp.replay.com/pub/crypto/disk/, and the newer tcfs
247 package, available at http://tcfs.dia.unisa.it/. You do not need to
248 say Y here if you want to use one of these. However, using cfs
249 requires saying Y to "NFS filesystem support" below while using tcfs
250 requires applying a kernel patch.
252 To use the loop device, you need the losetup utility and a recent
253 version of the mount program, both contained in the util-linux
254 package. The location and current version number of util-linux is
255 contained in the file Documentation/Changes.
257 Note that this loop device has nothing to do with the loopback
258 device used for network connections from the machine to itself.
260 If you want to compile this driver as a module ( = code which can be
261 inserted in and removed from the running kernel whenever you want),
262 say M here and read Documentation/modules.txt. The module will be
265 Most users will answer N here.
267 Network Block Device support
269 Saying Y here will allow your computer to be a client for network
270 block devices, i.e. it will be able to use block devices exported by
271 servers (mount filesystems on them etc.). Communication between
272 client and server works over TCP/IP networking, but to the client
273 program this is hidden: it looks like a regular local file access to
274 a block device special file such as /dev/nd0.
276 Network block devices also allows you to run a block-device in
277 userland (making server and client physically the same computer,
278 communicating using the loopback network device).
280 Read Documentation/nbd.txt for more information, especially about
281 where to find the server code, which runs in user space and does not
282 need special kernel support.
284 Note that this has nothing to do with the network file systems NFS
285 or Coda; you can say N here even if you intend to use NFS or Coda.
287 If you want to compile this driver as a module ( = code which can be
288 inserted in and removed from the running kernel whenever you want),
289 say M here and read Documentation/modules.txt. The module will be
294 Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
296 If you say Y here, you will use the full-featured IDE driver to
297 control up to eight IDE interfaces, each being able to serve a
298 "master" and a "slave" device, for a total of up to sixteen (16)
299 IDE disk/cdrom/tape/floppy drives. People with SCSI-only systems
302 Useful information about large (>540 MB) IDE disks, multiple
303 interfaces, what to do if IDE devices are not automatically
304 detected, sound card IDE ports, module support, and other topics, is
305 contained in Documentation/ide.txt. For detailed information about
306 hard drives, consult the Disk-HOWTO and the Multi-Disk-HOWTO,
307 available via FTP (user: anonymous) from
308 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
310 To fine-tune IDE drive/interface parameters for improved
311 performance, look for the hdparm package at
312 ftp://metalab.unc.edu/pub/Linux/kernel/patches/diskdrives/
314 If you want to compile this driver as a module ( = code which can be
315 inserted in and removed from the running kernel whenever you want),
316 say M here and read Documentation/modules.txt and
317 Documentation/ide.txt. The module will be called ide.o. Do not
318 compile this driver as a module if your root filesystem (the one
319 containing the directory /) is located on an IDE device.
321 If you have one or more IDE drives, say Y or M here. If your system
322 has no IDE drives, or if memory requirements are really tight, you
323 could say N here, and select the "Old hard disk driver" below
324 instead to save about 13 KB of memory in the kernel.
326 Old hard disk (MFM/RLL/IDE) driver
327 CONFIG_BLK_DEV_HD_ONLY
328 There are two drivers for MFM/RLL/IDE hard disks. Most people use
329 the newer enhanced driver, but this old one is still around for two
330 reasons. Some older systems have strange timing problems and seem to
331 work only with the old driver (which itself does not work with some
332 newer systems). The other reason is that the old driver is smaller,
333 since it lacks the enhanced functionality of the new one. This makes
334 it a good choice for systems with very tight memory restrictions, or
335 for systems with only older MFM/RLL/ESDI drives. Choosing the old
336 driver can save 13 KB or so of kernel memory.
338 If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
339 instead of this one. For more detailed information, read the
340 Disk-HOWTO, available via FTP (user: anonymous) from
341 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
343 People with SCSI-only systems can say N here.
345 Use old disk-only driver on primary interface
346 CONFIG_BLK_DEV_HD_IDE
347 There are two drivers for MFM/RLL/IDE disks. Most people use just
348 the new enhanced driver by itself. This option however installs the
349 old hard disk driver to control the primary IDE/disk interface in
350 the system, leaving the new enhanced IDE driver to take care of only
351 the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from
352 having an IDE/ATAPI CDROM or tape drive connected to the primary IDE
353 interface. Choosing this option may be useful for older systems
354 which have MFM/RLL/ESDI controller+drives at the primary port
355 address (0x1f0), along with IDE drives at the secondary/3rd/4th port
358 Normally, just say N here; you will then use the new driver for all
361 People with SCSI-only systems don't need this and can say N here as
364 Include IDE/ATA-2 DISK support
365 CONFIG_BLK_DEV_IDEDISK
366 This will include enhanced support for MFM/RLL/IDE hard disks. If
367 you have a MFM/RLL/IDE disk, and there is no special reason to use
368 the old hard disk driver instead, say Y. If you have an SCSI-only
369 system, you can say N here.
371 If you want to compile this driver as a module ( = code which can be
372 inserted in and removed from the running kernel whenever you want),
373 say M here and read Documentation/modules.txt. The module will be
374 called ide-disk.o. Do not compile this driver as a module if your
375 root filesystem (the one containing the directory /) is located on
376 the IDE disk. If unsure, say Y.
378 Use multi-mode by default
379 CONFIG_IDEDISK_MULTI_MODE
380 If you get this error, try to enable this option.
382 hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
383 hda: set_multmode: error=0x04 { DriveStatusError }
387 Include IDE/ATAPI CDROM support
389 If you have a CDROM drive using the ATAPI protocol, say Y. ATAPI is
390 a newer protocol used by IDE CDROM and TAPE drives, similar to the
391 SCSI protocol. Most new CDROM drives use ATAPI, including the
392 NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
393 double(2X) or better speed drives.
395 If you say Y here, the CDROM drive will be identified at boot time
396 along with other IDE devices, as "hdb" or "hdc", or something
397 similar (check the boot messages with dmesg). If this is your only
398 CDROM drive, you can say N to all other CDROM options, but be sure
399 to say Y or M to "ISO 9660 CDROM filesystem support".
401 Read the CDROM-HOWTO, available via FTP (user: anonymous) in
402 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO and the file
403 Documentation/cdrom/ide-cd. Note that older versions of lilo (the
404 Linux boot loader) cannot properly deal with IDE/ATAPI CDROMs, so
405 install lilo-16 or higher, available from
406 ftp://metalab.unc.edu/pub/Linux/system/Linux-boot/lilo.
408 If you want to compile the driver as a module ( = code which can be
409 inserted in and removed from the running kernel whenever you want),
410 say M here and read Documentation/modules.txt. The module will be
413 Include CD-Changer Reporting
415 If you have an IDE/ATAPI multi-slot cd-changer and you want
416 to report which slots have disk-present, say Y. If you say Y
417 and there is not a multi-slot cdrom present, this code is skipped.
419 This could be the bases of multi-disk access based on multi-mounts.
420 This is still pie-in-the-sky.
424 Include IDE/ATAPI TAPE support
425 CONFIG_BLK_DEV_IDETAPE
426 If you have an IDE tape drive using the ATAPI protocol, say Y.
427 ATAPI is a newer protocol used by IDE tape and CDROM drives, similar
428 to the SCSI protocol. If you have an SCSI tape drive however, you
431 If you say Y here, the tape drive will be identified at boot time
432 along with other IDE devices, as "hdb" or "hdc", or something
433 similar, and will be mapped to a character device such as "ht0"
434 (check the boot messages with dmesg). Be sure to consult the
435 drivers/block/ide-tape.c and Documentation/ide.txt files for usage
438 If you want to compile the driver as a module ( = code which can be
439 inserted in and removed from the running kernel whenever you want),
440 say M here and read Documentation/modules.txt. The module will be
443 Include IDE/ATAPI FLOPPY support
444 CONFIG_BLK_DEV_IDEFLOPPY
445 If you have an IDE floppy drive which uses the ATAPI protocol,
446 answer Y. ATAPI is a newer protocol used by IDE CDROM/tape/floppy
447 drives, similar to the SCSI protocol.
449 The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by
450 this driver. (ATAPI PD-CD/CDR drives are not supported by this
451 driver; support for PD-CD/CDR drives is available if you answer Y to
452 "SCSI emulation support", below).
454 If you say Y here, the FLOPPY drive will be identified along with
455 other IDE devices, as "hdb" or "hdc", or something similar (check
456 the boot messages with dmesg).
458 If you want to compile the driver as a module ( = code which can be
459 inserted in and removed from the running kernel whenever you want),
460 say M here and read Documentation/modules.txt. The module will be
463 SCSI emulation support
464 CONFIG_BLK_DEV_IDESCSI
465 This will provide SCSI host adapter emulation for IDE ATAPI devices,
466 and will allow you to use a SCSI device driver instead of a native
469 This is useful if you have an ATAPI device for which no native
470 driver has been written (for example, an ATAPI PD-CD or CDR drive);
471 you can then use this emulation together with an appropriate SCSI
472 device driver. In order to do this, say Y here and to "SCSI support"
473 and "SCSI generic support", below.
475 Note that this option does NOT allow you to attach SCSI devices to a
476 box that doesn't have a SCSI host adapter installed.
478 If both this SCSI emulation and native ATAPI support are compiled
479 into the kernel, the native support will be used.
481 People with SCSI-only systems can say N here. If unsure, say N.
483 CMD640 chipset bugfix/support
484 CONFIG_BLK_DEV_CMD640
485 The CMD-Technologies CMD640 IDE chip is used on many common 486 and
486 Pentium motherboards, usually in combination with a "Neptune" or
487 "SiS" chipset. Unfortunately, it has a number of rather nasty
488 design flaws that can cause severe data corruption under many common
489 conditions. Say Y here to include code which tries to automatically
490 detect and correct the problems under Linux. This option also
491 enables access to the secondary IDE ports in some CMD640 based
494 This driver will work automatically in PCI based systems (most new
495 systems have PCI slots). But if your system uses VESA local bus
496 (VLB) instead of PCI, you must also supply a kernel boot parameter
497 to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man
498 bootparam" or see the documentation of your boot loader about how to
499 pass options to the kernel. The lilo procedure is also explained in
500 the SCSI-HOWTO, available via FTP (user: anonymous) in
501 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.)
503 The CMD640 chip is also used on add-in cards by Acculogic, and on
504 the "CSA-6400E PCI to IDE controller" that some people have. For
505 details, read Documentation/ide.txt.
507 People with SCSI-only systems should say N here. If unsure, say Y.
509 CMD640 enhanced support
510 CONFIG_BLK_DEV_CMD640_ENHANCED
511 This option includes support for setting/autotuning PIO modes and
512 prefetch on CMD640 IDE interfaces. For details, read
513 Documentation/ide.txt. If you have a CMD640 IDE interface and your
514 BIOS does not already do this for you, then say Y here. Otherwise
517 RZ1000 chipset bugfix/support
518 CONFIG_BLK_DEV_RZ1000
519 The PC-Technologies RZ1000 IDE chip is used on many common 486 and
520 Pentium motherboards, usually along with the "Neptune" chipset.
521 Unfortunately, it has a rather nasty design flaw that can cause
522 severe data corruption under many conditions. Say Y here to include
523 code which automatically detects and corrects the problem under
524 Linux. This may slow disk throughput by a few percent, but at least
525 things will operate 100% reliably.
527 People with SCSI-only systems should say N here. If unsure, say Y.
529 Generic PCI IDE chipset support
530 CONFIG_BLK_DEV_IDEPCI
531 Say Y here for PCI systems which use IDE drive(s).
532 This option helps the IDE driver to automatically detect and
533 configure all PCI-based IDE interfaces in your system.
535 People with SCSI-only systems should say N here; if unsure say Y.
537 Generic PCI bus-master DMA support
538 CONFIG_BLK_DEV_IDEDMA_PCI
539 If your PCI system uses IDE drive(s) (as opposed to SCSI, say) and
540 is capable of bus-master DMA operation (most Pentium PCI systems),
541 you will want to say Y here to reduce CPU overhead. You can then use
542 the "hdparm" utility to enable DMA for drives for which it was not
543 enabled automatically. By default, DMA is not enabled automatically
544 for these drives, but you can change that by saying Y to the
545 following question "Use DMA by default when available". You can get
546 the latest version of the hdparm utility via anonymous FTP from
547 ftp://metalab.unc.edu/pub/Linux/system/hardware/.
549 Read the comments at the beginning of drivers/block/idedma.c and the
550 file Documentation/ide.txt for more information.
552 It is safe to say Y to this question.
554 Use DMA by default when available
555 CONFIG_IDEDMA_PCI_AUTO
556 Prior to kernel version 2.1.112, Linux used to automatically use
557 DMA for IDE drives and chipsets which support it. Due to concerns
558 about a couple of cases where buggy hardware may have caused damage,
559 the default is now to NOT use DMA automatically. To revert to the
560 previous behaviour, say Y to this question.
562 If you suspect your hardware is at all flakey, say N here.
563 Do NOT email the IDE kernel people regarding this issue!
565 It is normally safe to answer Y to this question unless your
566 motherboard uses a VIA VP2 chipset, in which case you should say N.
568 Good-Bad DMA Model-Firmware (EXPERIMENTAL)
569 IDEDMA_NEW_DRIVE_LISTINGS
570 This test compares both the model and firmware revision for buggy drives
571 that claim to (U)DMA capable. This is a blanket on/off test with no speed
572 limit options. Straight GNU GCC 2.7.3/2.8.X compilers are known to be safe;
573 whereas, many versions of EGCS have a problem and miscompile.
577 Boot off-board chipsets first support
578 CONFIG_BLK_DEV_OFFBOARD
579 Normally, IDE controllers built into the motherboard (on-board
580 controllers) are assigned to ide0 and ide1 while those on add-in PCI
581 cards (off-board controllers) are relegated to ide2 and ide3.
582 Answering Y here will reverse the situation, with off-board
583 controllers on ide0/1 and on-board controllers on ide2/3. This can
584 improve the usability of some boot managers such as LILO when
585 booting from a drive on an off-board controller.
587 Requires that all onboard ide controllers be disabled or calling
588 "pci=reverse" to invert the device scan order.
590 Note that, if you say Y here, the order of the hd* devices will be
591 rearranged which may require modification of fstab and other files.
595 AEC6210 chipset support
596 CONFIG_BLK_DEV_AEC6210
597 This driver adds up to 4 more eide devices sharing a single interrupt.
598 This add-on card is a bootable PCI UDMA controller. In order to get this
599 card to initialize correctly in some cases, you should include this driver.
601 This prefers CONFIG_IDEDMA_PCI_AUTO to be enabled, regardless.
603 Please read the comments at the top of drivers/block/aec6210.c
605 ALI M15x3 chipset support (EXPERIMENTAL)
606 CONFIG_BLK_DEV_ALI15X3
607 This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C
608 onboard chipsets. It also tests for Simplex mode and enables
609 normal dual channel support.
611 This requires CONFIG_IDEDMA_PCI_AUTO to be enabled.
613 Please read the comments at the top of drivers/block/alim15x3.c
617 CMD646 chipset support (EXPERIMENTAL)
618 CONFIG_BLK_DEV_CMD646
619 Say Y here if you have an IDE controller like this.
621 CY82C693 chipset support (EXPERIMENTAL)
622 CONFIG_BLK_DEV_CY82C693
624 This driver adds detection and support for the CY82C693 chipset
625 used on Digital's PC-Alpha 164SX boards.
627 This requires CONFIG_IDEDMA_PCI_AUTO to be enabled.
629 Please read the comments at the top of drivers/block/cy82c693.c
631 HPT34X chipset support
632 CONFIG_BLK_DEV_HPT34X
633 This driver adds up to 4 more EIDE devices sharing a single
634 interrupt. The HPT343 chipset in its current form is a non-bootable or
635 HPT345/HPT363 chipset is bootable (needs BIOS FIX) PCI UDMA controllers.
636 This driver requires dynamic tuning of the chipset during the ide-probe
637 at boot. It is reported to support DVD II drives, by the manufacturer.
639 Please read the comments at the top of drivers/block/hpt34x.c
641 HPT34X DMA support (DANGEROUS)
642 CONFIG_BLK_DEV_HPT34X_DMA
643 This requires CONFIG_IDEDMA_PCI_AUTO to be enabled.
645 Please read the comments at the top of drivers/block/hpt34x.c
647 HPT366 chipset support
648 CONFIG_BLK_DEV_HPT366
649 This is an Ultra DMA chipset for ATA-66.
650 This driver adds up to 4 more EIDE devices sharing a single
651 interrupt. The HPT366 chipset in its current form is a non-bootable.
652 This driver requires dynamic tuning of the chipset during the ide-probe
653 at boot. It is reported to support DVD II drives, by the manufacturer.
655 Please read the comments at the top of drivers/block/hpt366.c
657 Intel PIIXn chipsets support
659 This driver adds PIO mode setting and tuning for all PIIX IDE
660 controllers by Intel. Since the BIOS can sometimes improperly tune
661 PIO 0-4 mode settings, this allows dynamic tuning of the chipset
662 via the standard end-user tool 'hdparm'.
664 Please read the comments at the top of drivers/block/piix.c
668 PIIXn Tuning support (EXPERIMENTAL)
669 CONFIG_BLK_DEV_PIIX_TUNING
670 This driver extension adds DMA mode setting and tuning for all PIIX IDE
671 controllers by Intel. Since the BIOS can sometimes improperly setup
672 the device/adapter combination and speed limits, It has become a necessity
673 to back/forward speed devices as needed.
675 Case 430HX/440FX PIIX3 need speed limits to reduce UDMA to DMA mode 2
676 if the BIOS can to perform this task at INIT.
680 NS87415 support (EXPERIMENTAL)
681 CONFIG_BLK_DEV_NS87415
682 This driver adds detection and support for the NS87415 chip
683 (used in SPARC64, among others).
685 Please read the comments at the top of drivers/block/ns87415.c.
687 OPTi 82C621 enhanced support (EXPERIMENTAL)
688 CONFIG_BLK_DEV_OPTI621
689 This is a driver for the OPTi 82C621 EIDE controller.
690 Please read the comments at the top of drivers/block/opti621.c.
692 PROMISE PDC20246/PDC20262 support
693 CONFIG_BLK_DEV_PDC202XX
694 Promise Ultra33 or PDC20246.
695 This driver adds up to 4 more eide devices sharing a single interrupt.
696 This add-on card is a bootable PCI UDMA controller.
697 Since multiple cards can be installed and there are BIOS ROM problems
698 that happen if the BIOS revisions of all installed cards (three-max)
699 do not match. Should you be unable to make new BIOS chips with a burner,
700 the driver attempts to dynamic tuning of the chipset at boot-time
701 for max-speed. Ultra33 BIOS 1.25 or new required for more than one card.
702 This card may require "PDC202XX Special UDMA Feature (EXPERIMENTAL)".
704 Promise Ultra66 or PDC20262.
705 This driver adds up to 4 more eide devices sharing a single interrupt.
706 This add-on card is a bootable PCI UDMA ATA-66 controller.
707 The driver attempts to dynamic tuning of the chipset at boot-time
708 for max-speed. Note tested limits are UDMA-2.
709 Ultra66 BIOS 1.11 or newer required.
711 This requires CONFIG_IDEDMA_PCI_AUTO to be enabled.
713 Please read the comments at the top of drivers/block/pdc202xx.c
717 Special UDMA Feature (EXPERIMENTAL)
718 PDC202XX_FORCE_BURST_BIT
719 For PDC20246 and PDC20262 Ultra DMA chipsets.
720 Designed originally for PDC20246/Ultra33 that has BIOS setup failures
721 when using 3 or more cards.
723 Please read the comments at the top of drivers/block/pdc202xx.c
727 Special Mode Feature (DANGEROUS)
728 PDC202XX_FORCE_MASTER_MODE
729 For PDC20246 and PDC20262 Ultra DMA chipsets.
730 This is reserved for possible Hardware RAID 0,1 for the FastTrak Series.
734 SiS5513 chipset support
735 CONFIG_BLK_DEV_SIS5513
736 This driver ensures (U)DMA support for SIS5513 chipset based mainboards.
737 SiS620/530 UDMA mode 4, SiS5600/5597 UDMA mode 2, all other DMA mode 2
738 limited chipsets are unsupported to date.
740 This requires CONFIG_IDEDMA_PCI_AUTO to be enabled.
742 Please read the comments at the top of drivers/block/sis5513.c
744 Winbond SL82c105 support
745 CONFIG_BLK_DEV_SL82C105
746 If you have a Winbond SL82c105 IDE controller, say Y here to enable
747 special configuration for this chip. This is common on various CHRP
748 motherboards, but could be used elsewhere. If in doubt, say Y.
750 Tekram TRM290 chipset support (EXPERIMENTAL)
751 CONFIG_BLK_DEV_TRM290
752 This driver adds support for bus master DMA transfers
753 using the Tekram TRM290 PCI IDE chip. Volunteers are
754 needed for further tweaking and development.
755 Please read the comments at the top of drivers/block/trm290.c.
757 VIA82C586 chipset support (EXPERIMENTAL)
758 CONFIG_BLK_DEV_VIA82C586
759 This allows you to to configure your chipset for a better use while
760 running (U)DMA: it will allow you to enable efficiently the second
761 channel dma usage, as it is may not be set by BIOS. It allows you to
762 run a kernel command line at boot time in order to set fifo config.
763 If no command line is provided, it will try to set fifo configuration
764 at its best. It will allow you to get a proc/ide/via display
765 (while running a "cat") provided you enabled "proc" support and
766 set DISPLAY_APOLLO_TIMINGS in via82c586.c
768 This requires CONFIG_IDEDMA_PCI_AUTO to be enabled.
772 Support for PowerMac IDE devices (must also enable IDE)
773 CONFIG_BLK_DEV_IDE_PMAC
774 No help for CONFIG_BLK_DEV_IDE_PMAC
776 PowerMac IDE DMA support
777 CONFIG_BLK_DEV_IDEDMA_PMAC
778 No help for CONFIG_BLK_DEV_IDEDMA_PMAC
781 CONFIG_IDEDMA_PMAC_AUTO
782 No help for CONFIG_IDEDMA_PMAC_AUTO
784 ICS IDE interface support
785 CONFIG_BLK_DEV_IDE_ICSIDE
786 No help for CONFIG_BLK_DEV_IDE_ICSIDE
789 CONFIG_BLK_DEV_IDEDMA_ICS
790 No help for CONFIG_BLK_DEV_IDEDMA_ICS
792 Use ICS DMA by default
793 CONFIG_IDEDMA_ICS_AUTO
794 No help for CONFIG_IDEDMA_ICS_AUTO
796 RapIDE interface support
797 CONFIG_BLK_DEV_IDE_RAPIDE
798 No help for CONFIG_BLK_DEV_IDE_RAPIDE
800 Other IDE chipset support
802 Say Y here if you want to include enhanced support for various IDE
803 interface chipsets used on motherboards and add-on cards. You can
804 then pick your particular IDE chip from among the following options.
805 This enhanced support may be necessary for Linux to be able to
806 access the 3rd/4th drives in some systems. It may also enable
807 setting of higher speed I/O rates to improve system performance with
808 these chipsets. Most of these also require special kernel boot
809 parameters to actually turn on the support at runtime; you can find
810 a list of these in the file Documentation/ide.txt.
812 People with SCSI-only systems can say N here.
814 Generic 4 drives/port support
815 CONFIG_BLK_DEV_4DRIVES
816 Certain older chipsets, including the Tekram 690CD, use a single set
817 of I/O ports at 0x1f0 to control up to four drives, instead of the
818 customary two drives per port. Support for this can be enabled at
819 runtime using the "ide0=four" kernel boot parameter if you say Y
823 CONFIG_BLK_DEV_ALI14XX
824 This driver is enabled at runtime using the "ide0=ali14xx" kernel
825 boot parameter. It enables support for the secondary IDE interface
826 of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
827 I/O speeds to be set as well. See the files Documentation/ide.txt
828 and drivers/block/ali14xx.c for more info.
831 CONFIG_BLK_DEV_DTC2278
832 This driver is enabled at runtime using the "ide0=dtc2278" kernel
833 boot parameter. It enables support for the secondary IDE interface
834 of the DTC-2278 card, and permits faster I/O speeds to be set as
835 well. See the Documentation/ide.txt and drivers/block/dtc2278.c
838 Holtek HT6560B support
839 CONFIG_BLK_DEV_HT6560B
840 This driver is enabled at runtime using the "ide0=ht6560b" kernel
841 boot parameter. It enables support for the secondary IDE interface
842 of the Holtek card, and permits faster I/O speeds to be set as well.
843 See the Documentation/ide.txt and drivers/block/ht6560b.c files for
846 PROMISE DC4030 support (EXPERIMENTAL)
847 CONFIG_BLK_DEV_PDC4030
848 This driver provides support for the secondary IDE interface and
849 cache of Promise IDE chipsets, e.g. DC4030 and DC5030. This driver
850 is known to incur timeouts/retries during heavy I/O to drives
851 attached to the secondary interface. CDROM and TAPE devices are not
852 supported yet. This driver is enabled at runtime using the
853 "ide0=dc4030" kernel boot parameter. See the Documentation/ide.txt
854 and drivers/block/pdc4030.c files for more info.
857 CONFIG_BLK_DEV_QD6580
858 This driver is enabled at runtime using the "ide0=qd6580" kernel
859 boot parameter. It permits faster I/O speeds to be set. See the
860 files Documentation/ide.txt and drivers/block/qd6580.c for more
864 CONFIG_BLK_DEV_UMC8672
865 This driver is enabled at runtime using the "ide0=umc8672" kernel
866 boot parameter. It enables support for the secondary IDE interface
867 of the UMC-8672, and permits faster I/O speeds to be set as well.
868 See the files Documentation/ide.txt and drivers/block/umc8672.c for
871 Amiga builtin Gayle IDE interface support
873 This is the IDE driver for the builtin IDE interface on some Amiga
874 models. It supports both the `A1200 style' (used in A600 and A1200)
875 and `A4000 style' (used in A4000 and A4000T) of the Gayle IDE interface.
876 Say Y if you have such an Amiga model and want to use IDE devices
877 (hard disks, CD-ROM drives, etc.) that are connected to the builtin
880 Amiga IDE Doubler support (EXPERIMENTAL)
881 CONFIG_BLK_DEV_IDEDOUBLER
882 This driver provides support for the so called `IDE doublers' (made by
883 various manufacturers, e.g. Eyetech) that can be connected to the
884 builtin IDE interface of some Amiga models. Using such an IDE doubler,
885 you can connect up to four instead of two IDE devices on the Amiga's
886 builtin IDE interface.
887 Note that the normal Amiga Gayle IDE driver may not work correctly if
888 you have an IDE doubler and don't enable this driver!
889 Say Y if you have an IDE doubler. The driver is enabled at kernel
890 runtime using the "ide=doubler" kernel boot parameter.
892 Amiga Buddha/Catweasel IDE interface support (EXPERIMENTAL)
893 CONFIG_BLK_DEV_BUDDHA
894 This is the IDE driver for the IDE interfaces on the Buddha and
895 Catweasel expansion boards. It supports up to two interfaces on the
896 Buddha and three on the Catweasel.
897 Say Y if you have a Buddha or Catweasel expansion board and want to
898 use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
899 to one of its IDE interfaces.
901 Falcon IDE interface support
902 CONFIG_BLK_DEV_FALCON_IDE
903 This is the IDE driver for the builtin IDE interface on the Atari Falcon.
904 Say Y if you have a Falcon and want to use IDE devices (hard disks,
905 CD-ROM drives, etc.) that are connected to the builtin IDE interface.
907 Macintosh Quadra/Powerbook IDE interface support
908 CONFIG_BLK_DEV_MAC_IDE
909 This is the IDE driver for the builtin IDE interface on the some m68k
910 Macintosh models. It supports both the `Quadra style' (used in Quadra/
911 Centris 630 and Performa 588 models) and `Powerbook style' (used in the
912 Powerbook 150 and 190 models) IDE interface.
913 Say Y if you have such an Macintosh model and want to use IDE devices
914 (hard disks, CD-ROM drives, etc.) that are connected to the builtin
917 PS/2 ESDI hard disk support
919 Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
922 If you want to compile the driver as a module ( = code which can be
923 inserted in and removed from the running kernel whenever you want),
924 say M here and read Documentation/modules.txt. The module will be
929 Very old 8 bit hard disk controllers used in the IBM XT computer
930 will be supported if you say Y here.
932 If you want to compile the driver as a module ( = code which can be
933 inserted in and removed from the running kernel whenever you want),
934 say M here and read Documentation/modules.txt. The module will be
937 It's pretty unlikely that you have one of these: say N.
939 Mylex DAC960/DAC1100 PCI RAID Controller support
940 CONFIG_BLK_DEV_DAC960
941 This driver adds support for the Mylex DAC960, AcceleRAID, and
942 eXtremeRAID PCI RAID controllers. See README.DAC960 for further
943 information about this driver.
945 If you want to compile the driver as a module ( = code which can be
946 inserted in and removed from the running kernel whenever you want),
947 say M here and read Documentation/modules.txt. The module will be
950 Parallel port IDE device support
952 There are many external CD-ROM and disk devices that connect through
953 your computer's parallel port. Most of them are actually IDE devices
954 using a parallel port IDE adapter. This option enables the PARIDE
955 subsystem which contains drivers for many of these external drives.
956 Read linux/Documentation/paride.txt for more information.
958 If you have said Y to the "Parallel-port support" configuration
959 option, you may share a single port between your printer and other
960 parallel port devices. Answer Y to build PARIDE support into your
961 kernel, or M if you would like to build it as a loadable module. If
962 your parallel port support is in a loadable module, you must build
963 PARIDE as a module. If you built PARIDE support into your kernel,
964 you may still build the individual protocol modules and high-level
965 drivers as loadable modules. If you build this support as a module,
966 it will be called paride.o.
968 To use the PARIDE support, you must say Y or M here and also to at
969 least one high-level driver (e.g. "Parallel port IDE disks",
970 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
971 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
972 "MicroSolutions backpack protocol", "DataStor Commuter protocol"
975 Parallel port IDE disks
977 This option enables the high-level driver for IDE-type disk devices
978 connected through a parallel port. If you chose to build PARIDE
979 support into your kernel, you may answer Y here to build in the
980 parallel port IDE driver, otherwise you should answer M to build
981 it as a loadable module. The module will be called pd.o. You
982 must also have at least one parallel port protocol driver in your
983 system. Among the devices supported by this driver are the SyQuest
984 EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack
985 hard drives from MicroSolutions.
987 Parallel port ATAPI CD-ROMs
989 This option enables the high-level driver for ATAPI CD-ROM devices
990 connected through a parallel port. If you chose to build PARIDE
991 support into your kernel, you may answer Y here to build in the
992 parallel port ATAPI CD-ROM driver, otherwise you should answer M to
993 build it as a loadable module. The module will be called pcd.o. You
994 must also have at least one parallel port protocol driver in your
995 system. Among the devices supported by this driver are the
996 MicroSolutions backpack CD-ROM drives and the Freecom Power CD. If
997 you have such a CD-ROM drive, you should also say Y or M to "ISO
998 9660 CDROM filesystem support" below, because that's the filesystem
1001 Parallel port ATAPI disks
1003 This option enables the high-level driver for ATAPI disk devices
1004 connected through a parallel port. If you chose to build PARIDE
1005 support into your kernel, you may answer Y here to build in the
1006 parallel port ATAPI disk driver, otherwise you should answer M
1007 to build it as a loadable module. The module will be called pf.o.
1008 You must also have at least one parallel port protocol driver in
1009 your system. Among the devices supported by this driver are the
1010 MicroSolutions backpack PD/CD drive and the Imation Superdisk
1013 Parallel port ATAPI tapes
1015 This option enables the high-level driver for ATAPI tape devices
1016 connected through a parallel port. If you chose to build PARIDE
1017 support into your kernel, you may answer Y here to build in the
1018 parallel port ATAPI disk driver, otherwise you should answer M
1019 to build it as a loadable module. The module will be called pt.o.
1020 You must also have at least one parallel port protocol driver in
1021 your system. Among the devices supported by this driver is the
1022 parallel port version of the HP 5GB drive.
1024 Parallel port generic ATAPI devices
1026 This option enables a special high-level driver for generic ATAPI
1027 devices connected through a parallel port. The driver allows user
1028 programs, such as cdrecord, to send ATAPI commands directly to a
1031 If you chose to build PARIDE support into your kernel, you may
1032 answer Y here to build in the parallel port generic ATAPI driver,
1033 otherwise you should answer M to build it as a loadable module. The
1034 module will be called pg.o.
1036 You must also have at least one parallel port protocol driver in
1039 This driver implements an API loosely related to the generic SCSI
1040 driver. See /usr/include/linux/pg.h for details.
1042 You can obtain the most recent version of cdrecord from
1043 ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/ . Versions 1.6.1a3 and
1044 later fully support this driver.
1046 ATEN EH-100 protocol
1048 This option enables support for the ATEN EH-100 parallel port IDE
1049 protocol. This protocol is used in some inexpensive low performance
1050 parallel port kits made in Hong Kong. If you chose to build PARIDE
1051 support into your kernel, you may answer Y here to build in the
1052 protocol driver, otherwise you should answer M to build it as a
1053 loadable module. The module will be called aten.o. You must also
1054 have a high-level driver for the type of device that you want to
1057 MicroSolutions backpack protocol
1059 This option enables support for the MicroSolutions backpack parallel
1060 port IDE protocol. If you chose to build PARIDE support into your
1061 kernel, you may answer Y here to build in the protocol driver,
1062 otherwise you should answer M to build it as a loadable module. The
1063 module will be called bpck.o. You must also have a high-level driver
1064 for the type of device that you want to support.
1066 DataStor Commuter protocol
1068 This option enables support for the Commuter parallel port IDE
1069 protocol from DataStor. If you chose to build PARIDE support
1070 into your kernel, you may answer Y here to build in the protocol
1071 driver, otherwise you should answer M to build it as a loadable
1072 module. The module will be called comm.o. You must also have
1073 a high-level driver for the type of device that you want to support.
1075 DataStor EP-2000 protocol
1077 This option enables support for the EP-2000 parallel port IDE
1078 protocol from DataStor. If you chose to build PARIDE support
1079 into your kernel, you may answer Y here to build in the protocol
1080 driver, otherwise you should answer M to build it as a loadable
1081 module. The module will be called dstr.o. You must also have
1082 a high-level driver for the type of device that you want to support.
1084 Shuttle EPAT/EPEZ protocol
1086 This option enables support for the EPAT parallel port IDE protocol.
1087 EPAT is a parallel port IDE adapter manufactured by Shuttle
1088 Technology and widely used in devices from major vendors such as
1089 Hewlett-Packard, SyQuest, Imation and Avatar. If you chose to build
1090 PARIDE support into your kernel, you may answer Y here to build in
1091 the protocol driver, otherwise you should answer M to build it as a
1092 loadable module. The module will be called epat.o. You must also
1093 have a high-level driver for the type of device that you want to
1096 Shuttle EPIA protocol
1098 This option enables support for the (obsolete) EPIA parallel port
1099 IDE protocol from Shuttle Technology. This adapter can still be
1100 found in some no-name kits. If you chose to build PARIDE support
1101 into your kernel, you may answer Y here to build in the protocol
1102 driver, otherwise you should answer M to build it as a loadable
1103 module. The module will be called epia.o. You must also have a
1104 high-level driver for the type of device that you want to support.
1106 FIT TD-2000 protocol
1108 This option enables support for the TD-2000 parallel port IDE
1109 protocol from Fidelity International Technology. This is a simple
1110 (low speed) adapter that is used in some portable hard drives. If
1111 you chose to build PARIDE support into your kernel, you may answer Y
1112 here to build in the protocol driver, otherwise you should answer M
1113 to build it as a loadable module. The module will be called ktti.o.
1114 You must also have a high-level driver for the type of device that
1115 you want to support.
1117 FIT TD-3000 protocol
1119 This option enables support for the TD-3000 parallel port IDE
1120 protocol from Fidelity International Technology. This protocol is
1121 used in newer models of their portable disk, CD-ROM and PD/CD
1122 devices. If you chose to build PARIDE support into your kernel, you
1123 may answer Y here to build in the protocol driver, otherwise you
1124 should answer M to build it as a loadable module. The module will be
1125 called fit3.o. You must also have a high-level driver for the type
1126 of device that you want to support.
1128 Freecom IQ ASIC-2 protocol
1130 This option enables support for version 2 of the Freecom IQ parallel
1131 port IDE adapter. This adapter is used by the Maxell Superdisk
1132 drive. If you chose to build PARIDE support into your kernel, you
1133 may answer Y here to build in the protocol driver, otherwise you
1134 should answer M to build it as a loadable module. The module will be
1135 called friq.o. You must also have a high-level driver for the type
1136 of device that you want to support.
1138 FreeCom power protocol
1140 This option enables support for the Freecom power parallel port IDE
1141 protocol. If you chose to build PARIDE support into your kernel, you
1142 may answer Y here to build in the protocol driver, otherwise you
1143 should answer M to build it as a loadable module. The module will be
1144 called frpw.o. You must also have a high-level driver for the type
1145 of device that you want to support.
1147 KingByte KBIC-951A/971A protocols
1149 This option enables support for the KBIC-951A and KBIC-971A parallel
1150 port IDE protocols from KingByte Information Corp. KingByte's
1151 adapters appear in many no-name portable disk and CD-ROM products,
1152 especially in Europe. If you chose to build PARIDE support into your
1153 kernel, you may answer Y here to build in the protocol driver,
1154 otherwise you should answer M to build it as a loadable module. The
1155 module will be called kbic.o. You must also have a high-level driver
1156 for the type of device that you want to support.
1160 This option enables support for the "PHd" parallel port IDE protocol
1161 from KT Technology. This is a simple (low speed) adapter that is
1162 used in some 2.5" portable hard drives. If you chose to build PARIDE
1163 support into your kernel, you may answer Y here to build in the
1164 protocol driver, otherwise you should answer M to build it as a
1165 loadable module. The module will be called ktti.o. You must also
1166 have a high-level driver for the type of device that you want to
1169 OnSpec 90c20 protocol
1171 This option enables support for the (obsolete) 90c20 parallel port
1172 IDE protocol from OnSpec (often marketed under the ValuStore brand
1173 name). If you chose to build PARIDE support into your kernel, you
1174 may answer Y here to build in the protocol driver, otherwise you
1175 should answer M to build it as a loadable module. The module will
1176 be called on20.o. You must also have a high-level driver for the
1177 type of device that you want to support.
1179 OnSpec 90c26 protocol
1181 This option enables support for the 90c26 parallel port IDE protocol
1182 from OnSpec Electronics (often marketed under the ValuStore brand
1183 name). If you chose to build PARIDE support into your kernel, you
1184 may answer Y here to build in the protocol driver, otherwise you
1185 should answer M to build it as a loadable module. The module will be
1186 called on26.o. You must also have a high-level driver for the type
1187 of device that you want to support.
1189 Multiple devices driver support
1191 This driver lets you combine several hard disk partitions into one
1192 logical block device. This can be used to simply append one
1193 partition to another one or to combine several redundant
1194 hard disks to a RAID1/4/5 device so as to provide protection against
1195 hard disk failures. This is called "Software RAID" since the
1196 combining of the partitions is done by the kernel. "Hardware RAID"
1197 means that the combining is done by a dedicated controller; if you
1198 have such a controller, you do not need to say Y here.
1200 More information about Software RAID on Linux is contained in the
1201 Software-RAID mini-HOWTO, available via FTP (user: anonymous) from
1202 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini. There you will also
1203 learn where to get the supporting user space utilities raidtools.
1207 Linear (append) mode
1209 If you say Y here, then your multiple devices driver will be able to
1210 use the so-called linear mode, i.e. it will combine the hard disk
1211 partitions by simply appending one to the other.
1213 If you want to compile this as a module ( = code which can be
1214 inserted in and removed from the running kernel whenever you want),
1215 say M here and read Documentation/modules.txt. The module will be
1220 RAID-0 (striping) mode
1222 If you say Y here, then your multiple devices driver will be able to
1223 use the so-called raid0 mode, i.e. it will combine the hard disk
1224 partitions into one logical device in such a fashion as to fill them
1225 up evenly, one chunk here and one chunk there. This will increase
1226 the throughput rate if the partitions reside on distinct disks.
1228 Information about Software RAID on Linux is contained in the
1229 Software-RAID mini-HOWTO, available via FTP (user: anonymous) from
1230 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini. There you will also
1231 learn where to get the supporting user space utilities raidtools.
1233 If you want to compile this as a module ( = code which can be
1234 inserted in and removed from the running kernel whenever you want),
1235 say M here and read Documentation/modules.txt. The module will be
1240 RAID-1 (mirroring) mode
1242 A RAID-1 set consists of several disk drives which are exact copies
1243 of each other. In the event of a mirror failure, the RAID driver
1244 will continue to use the operational mirrors in the set, providing
1245 an error free MD (multiple device) to the higher levels of the
1246 kernel. In a set with N drives, the available space is the capacity
1247 of a single drive, and the set protects against a failure of (N - 1)
1250 Information about Software RAID on Linux is contained in the
1251 Software-RAID mini-HOWTO, available via FTP (user: anonymous) from
1252 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini. There you will also
1253 learn where to get the supporting user space utilities raidtools.
1255 If you want to use such a RAID-1 set, say Y. This code is also
1256 available as a module called raid1.o ( = code which can be inserted
1257 in and removed from the running kernel whenever you want). If you
1258 want to compile it as a module, say M here and read
1259 Documentation/modules.txt.
1265 A RAID-5 set of N drives with a capacity of C MB per drive provides
1266 the capacity of C * (N - 1) drives, and protects against a failure
1267 of a single drive. For a given sector (row) number, (N - 1) drives
1268 contain data sectors, and one drive contains the parity protection.
1269 For a RAID-4 set, the parity blocks are present on a single drive,
1270 while a RAID-5 set distributes the parity across the drives in one
1271 of the available parity distribution methods.
1273 Information about Software RAID on Linux is contained in the
1274 Software-RAID mini-HOWTO, available via FTP (user: anonymous) from
1275 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini. There you will also
1276 learn where to get the supporting user space utilities raidtools.
1278 If you want to use such a RAID-4/RAID-5 set, say Y. This code is
1279 also available as a module called raid5.o ( = code which can be
1280 inserted in and removed from the running kernel whenever you want).
1281 If you want to compile it as a module, say M here and read
1282 Documentation/modules.txt.
1286 Boot support (linear, striped)
1288 To boot with an initial linear or striped md device you have to
1289 answer Y here. For lilo and loadlin options see the file
1290 Documentation/md.txt.
1292 Support for Deskstation RPC44
1293 CONFIG_DESKSTATION_RPC44
1294 This is a machine with a R4400 100 MHz CPU. To compile a Linux
1295 kernel that runs on these, say Y here. For details about Linux
1296 on the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1297 http://lena.fnet.fr/ (To browse the WWW, you need to
1298 have access to a machine on the Internet that has a program like
1301 Support for Acer PICA 1 chipset
1303 This is a machine with a R4400 133/150 MHz CPU. To compile a Linux
1304 kernel that runs on these, say Y here. For details about Linux on
1305 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1306 http://lena.fnet.fr/ (To browse the WWW, you need to have access to
1307 a machine on the Internet that has a program like lynx or netscape).
1309 Support for Algorithmics P4032
1311 This is an evaluation board of the British company Algorithmics. The
1312 board uses the R4300 and a R5230 CPUs. For more information about
1313 this board see http://www.algor.co.uk.
1316 CONFIG_BLK_DEV_IDE_CARDS
1317 On Acorn systems, enable this if you wish to use an IDE interface
1318 expansion card. If you do not or are unsure, say N to this.
1321 CONFIG_BLK_DEV_IDE_ICS
1322 On Acorn systems, enable this if you wish to use the ICS IDE
1323 interface card. This is not required for ICS partition support.
1324 If you are unsure, say N to this.
1326 ADFS partition support
1328 This allows Linux on Acorn systems to determine its partitions in
1329 the 'non-ADFS' partition area of the hard disk - usually located
1330 after the ADFS partition. You are probably using this system, so
1331 you should enable it.
1333 Support for Mips Magnum 4000
1334 CONFIG_MIPS_MAGNUM_4000
1335 This is a machine with a R4000 100 MHz CPU. To compile a Linux
1336 kernel that runs on these, say Y here. For details about Linux on
1337 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1338 http://lena.fnet.fr/ (To browse the WWW, you need to have access to
1339 a machine on the Internet that has a program like lynx or netscape).
1341 Support for Olivetti M700
1342 CONFIG_OLIVETTI_M700
1343 This is a machine with a R4000 100 MHz CPU. To compile a Linux
1344 kernel that runs on these, say Y here. For details about Linux on
1345 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1346 http://lena.fnet.fr/ (To browse the WWW, you need to have access to
1347 a machine on the Internet that has a program like lynx or netscape).
1351 Give the type of your machine's MIPS CPU. For this question, it
1352 suffices to give a unique prefix of the option you want to choose.
1353 In case of doubt select the R3000 CPU. The kernel will then run on
1354 other MIPS machines but with slightly reduced performance.
1356 Compile the kernel into the ECOFF object format
1358 Some machines require a kernel in the ECOFF format. You will have to
1359 say Y here for example if you want to use a Mips Magnum 3000 or a
1362 Generate little endian code
1363 CONFIG_CPU_LITTLE_ENDIAN
1364 Some MIPS machines can be configured for either little or big endian
1365 byte order. These modes require different kernels. Say Y if your
1366 machine is little endian, N if it's a big endian machine.
1368 Kernel support for IRIX binaries
1370 If you say Y here, the kernel will support running of IRIX binaries.
1371 You will need IRIX libraries for this to work.
1375 Unless you really know what you are doing, you should say Y here.
1376 The reason is that some programs need kernel networking support even
1377 when running on a stand-alone machine that isn't connected to any
1378 other computer. If you are upgrading from an older kernel, you
1379 should consider updating your networking tools too because changes
1380 in the kernel and the tools often go hand in hand. The tools are
1381 contained in the package net-tools, the location and version number
1382 of which are given in Documentation/Changes.
1384 For a general introduction to Linux networking, it is highly
1385 recommended to read the NET-3-HOWTO, available via FTP (user:
1386 anonymous) from ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
1390 The Linux Socket Filter is derived from the Berkeley Packet Filter.
1391 If you say Y here, user-space programs can attach a filter to any
1392 socket and thereby tell the kernel that it should allow or disallow
1393 certain types of data to get through the socket. Linux Socket
1394 Filtering works on all socket types except TCP for now. See the text
1395 file linux/Documentation/networking/filter.txt for more information.
1398 Network packet filtering
1400 Netfilter is a framework for filtering and mangling packets.
1401 Various modules exist for netfilter which replace the previous
1402 masquerading (ipmasqadm), packet filtering (ipchains), transparent
1403 proxying, and portforwarding mechanisms. Enabling this option
1404 makes minor alterations to allow these modules to hook into the
1405 packet stream. More information is available from
1406 http://netfilter.kernelnotes.org (to browse the WWW, you need
1407 to have access to a machine on the Internet that has a program like
1410 Make sure to say N to "Fast switching" below if you intend to say Y
1411 here, as Fast switching currently bypasses netfilter.
1413 Chances are that you should say Y here for every machine which is
1414 run as a router and N for every regular host. If unsure, say N.
1416 Network packet filtering debugging
1417 CONFIG_NETFILTER_DEBUG
1418 Say Y to make sure packets aren't leaking.
1420 SYN flood protection
1422 Normal TCP/IP networking is open to an attack known as "SYN
1423 flooding". This denial-of-service attack prevents legitimate remote
1424 users from being able to connect to your computer during an ongoing
1425 attack and requires very little work from the attacker, who can
1426 operate from anywhere on the Internet.
1428 SYN cookies provide protection against this type of attack. If you
1429 say Y here, the TCP/IP stack will use a cryptographic challenge
1430 protocol known as "SYN cookies" to enable legitimate users to
1431 continue to connect, even when your machine is under attack. There
1432 is no need for the legitimate users to change their TCP/IP software;
1433 SYN cookies work transparently to them. For technical information
1434 about SYN cookies, check out
1435 ftp://koobera.math.uic.edu/pub/docs/syncookies-archive.
1437 If you are SYN flooded, the source address reported by the kernel is
1438 likely to have been forged by the attacker; it is only reported as
1439 an aid in tracing the packets to their actual source and should not
1440 be taken as absolute truth.
1442 SYN cookies may prevent correct error reporting on clients when the
1443 server is really overloaded. If this happens frequently better turn
1446 If you say Y here, note that SYN cookies aren't enabled by default;
1447 you can enable them by saying Y to "/proc filesystem support" and
1448 "Sysctl support" below and executing the command
1450 echo 1 >/proc/sys/net/ipv4/tcp_syncookies
1452 at boot time after the proc filesystem has been mounted.
1456 Sun floppy controller support
1457 CONFIG_BLK_DEV_SUNFD
1458 This is support for floppy drives on Sun SPARC workstations. Say Y
1459 if you have a floppy drive, otherwise N. Easy.
1462 CONFIG_ALPHA_GENERIC
1463 This is the system type of your hardware. A "generic" kernel will
1464 run on any supported Alpha system. However, if you configure a
1465 kernel for your specific system, it will be faster and smaller.
1467 To find out what type of Alpha system you have, you may want to
1468 check out the Linux/Alpha FAQ, accessible on the WWW from
1469 http://www.alphalinux.org (To browse the WWW, you need to
1470 have access to a machine on the Internet that has a program like
1471 lynx or netscape). In summary:
1473 Alcor/Alpha-XLT AS 600
1474 Alpha-XL XL-233, XL-266
1475 AlphaBook1 Alpha laptop
1476 Avanti AS 200, AS 205, AS 250, AS 255, AS 300, AS 400
1477 Cabriolet AlphaPC64, AlphaPCI64
1479 EB164 EB164 21164 evaluation board
1480 EB64+ EB64+ 21064 evaluation board
1481 EB66 EB66 21066 evaluation board
1482 EB66+ EB66+ 21066 evaluation board
1483 Jensen DECpc 150, DEC 2000 model 300,
1486 Miata Personal Workstation 433a, 433au, 500a,
1487 500au, 600a, or 600au
1489 Noname AXPpci33, UDB (Multia)
1490 Noritake AS 1000A, AS 600A, AS 800
1492 Rawhide AS 1200, AS 4000, AS 4100
1493 Ruffian RPX164-2, AlphaPC164-UX, AlphaPC164-BX
1495 Sable AS 2000, AS 2100
1498 If you don't know what to do, choose "generic".
1500 EV5 CPU daughtercard
1502 Say Y if you have an AS 1000 5/xxx or an AS 1000A 5/xxx.
1506 Say Y if you have an AS 2000 5/xxx or an AS 2100 5/xxx.
1508 Using SRM as bootloader
1510 There are two different types of booting firmware on Alphas: SRM,
1511 which is command line driven, and ARC, which uses menus and arrow
1512 keys. Details about the Linux/Alpha booting process are contained in
1513 the Linux/Alpha FAQ, accessible on the WWW from
1514 http://www.alphalinux.org (To browse the WWW, you need to
1515 have access to a machine on the Internet that has a program like
1518 The usual way to load Linux on an Alpha machine is to use MILO
1519 (a bootloader that lets you pass command line parameters to the
1520 kernel just like lilo does for the x86 architecture) which can be
1521 loaded either from ARC or can be installed directly as a permanent
1522 firmware replacement from floppy (which requires changing a certain
1523 jumper on the motherboard). If you want to do either of these, say N
1524 here. If MILO doesn't work on your system (true for Jensen
1525 motherboards), you can bypass it altogether and boot Linux directly
1526 from an SRM console; say Y here in order to do that. Note that you
1527 won't be able to boot from an IDE disk using SRM.
1532 CONFIG_ALPHA_SRM_SETUP
1533 This option controls whether or not the PCI configuration set up by
1534 SRM is modified. If you say Y, the existing PCI configuration will
1537 Non-standard serial port support
1538 CONFIG_SERIAL_NONSTANDARD
1539 Say Y here if you have any non-standard serial boards -- boards
1540 which aren't supported using the standard "dumb" serial driver.
1541 This includes intelligent serial boards such as Cyclades,
1542 Digiboards, etc. These are usually used for systems that need many
1543 serial ports because they serve many terminals or dial-in
1546 Note that the answer to this question won't directly affect the
1547 kernel: saying N will just cause this configure script to skip all
1548 the questions about non-standard serial boards.
1550 Most people can say N here.
1552 Extended dumb serial driver options
1553 CONFIG_SERIAL_EXTENDED
1554 If you wish to use any non-standard features of the standard "dumb"
1555 driver, say Y here. This includes HUB6 support, shared serial
1556 interrupts, special multiport support, support for more than the
1557 four COM 1/2/3/4 boards, etc.
1559 Note that the answer to this question won't directly affect the
1560 kernel: saying N will just cause this configure script to skip all
1561 the questions about serial driver options. If unsure, say N.
1563 Support more than 4 serial ports
1564 CONFIG_SERIAL_MANY_PORTS
1565 Say Y here if you have dumb serial boards other than the four
1566 standard COM 1/2/3/4 ports. This may happen if you have an AST
1567 FourPort, Accent Async, Boca (read the Boca mini-HOWTO, available
1568 via FTP (user: anonymous) from
1569 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini), or other custom
1570 serial port hardware which acts similar to standard serial port
1571 hardware. If you only use the standard COM 1/2/3/4 ports, you can
1572 say N here to save some memory. You can also say Y if you have an
1573 "intelligent" multiport card such as Cyclades, Digiboards, etc.
1575 Support for sharing serial interrupts
1576 CONFIG_SERIAL_SHARE_IRQ
1577 Some serial boards have hardware support which allows multiple dumb
1578 serial ports on the same board to share a single IRQ. To enable
1579 support for this in the serial driver, say Y here.
1581 Auto detect IRQ on standard ports (unsafe)
1582 CONFIG_SERIAL_DETECT_IRQ
1583 Say Y here if you want the kernel to try to guess which IRQ
1584 to use for your serial port.
1586 This is considered unsafe; it is far better to configure the IRQ in
1587 a boot script using the setserial command.
1591 Support special multiport boards
1592 CONFIG_SERIAL_MULTIPORT
1593 Some multiport serial ports have special ports which are used to
1594 signal when there are any serial ports on the board which need
1595 servicing. Say Y here to enable the serial driver to take advantage
1596 of those special I/O ports.
1598 SGI Zilog85C30 serial support
1600 If you want to use your SGI's built-in serial ports under Linux,
1603 SGI Newport Graphics support
1604 CONFIG_SGI_NEWPORT_GFX
1605 If you have an SGI machine and you want to compile the graphics
1606 drivers, say Y here. This will include the code for the
1607 /dev/graphics and /dev/gfx drivers into the kernel for supporting
1608 virtualized access to your graphics hardware.
1610 Support the Bell Technologies HUB6 card
1612 Say Y here to enable support in the dumb serial driver to support
1617 Find out whether you have a PCI motherboard. PCI is the name of a
1618 bus system, i.e. the way the CPU talks to the other stuff inside
1619 your box. Other bus systems are ISA, EISA, Microchannel (MCA) or
1620 VESA. If you have PCI, say Y, otherwise N.
1622 The PCI-HOWTO, available via FTP (user: anonymous) in
1623 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO, contains valuable
1624 information about which PCI hardware does work under Linux and which
1629 On PCI systems, the BIOS can be used to detect the PCI devices and
1630 determine their configuration. However, some old PCI motherboards
1631 have BIOS bugs and may crash if this is done. Also, some embedded
1632 PCI-based systems don't have any BIOS at all. Linux can also try to
1633 detect the PCI hardware directly without using the BIOS.
1635 With this option, you can specify how Linux should detect the PCI
1636 devices. If you choose "BIOS", the BIOS will be used, if you choose
1637 "Direct", the BIOS won't be used, and if you choose "Any", the
1638 kernel will try the direct access method and falls back to the BIOS
1639 if that doesn't work. If unsure, go with the default.
1643 MicroChannel Architecture is found in some IBM PS/2 machines and
1644 laptops. It is a bus system similar to PCI or ISA. See
1645 Documentation/mca.txt (and especially the web page given there)
1646 before attempting to build an MCA bus kernel.
1648 SGI Visual Workstation support
1650 The SGI Visual Workstation series is an IA32-based workstation
1651 based on SGI systems chips with some legacy PC hardware attached.
1652 Say Y here to create a kernel to run on the SGI 320 or 540.
1653 A kernel compiled for the Visual Workstation will not run on other
1654 PC boards and vice versa.
1655 See Documentation/sgi-visws.txt for more.
1657 SGI Visual Workstation framebuffer support
1659 SGI Visual Workstation support for framebuffer graphics.
1663 The Intelligent Input/Output (I2O) architecture allows
1664 hardware drivers to be split into two parts: an operating system
1665 specific module called the OSM and an hardware specific module
1666 called the HDM. The OSM can talk to a whole range of HDM's, and
1667 ideally the HDM's are not OS dependent. This allows for the same
1668 driver to be used under different operating systems if the relevant
1669 OSM is in place. If you say Y here, you will get a choice of OSM's
1670 with the following questions.
1672 This support is also available as a module ( = code which can be
1673 inserted in and removed from the running kernel whenever you want).
1674 If you want to compile it as a module, say M here and read
1675 Documentation/modules.txt.
1681 Build in support for PCI bus I2O interface adapters. Currently this
1682 is the only variety supported.
1686 Include support for the I2O Block OSM. The Block OSM presents disk and
1687 other structured block devices to the operating system.
1691 Include support for the LAN OSM. You will also need to include support
1692 for token ring or fddi if you wish to use token ring or FDDI I2O cards
1697 Allow direct scsi access to scsi devices on a SCSI or FibreChannel I2O
1698 controller. You can use both the SCSI and Block OSM together if you wish.
1702 Inter Process Communication is a suite of library functions and
1703 system calls which let processes (running programs) synchronize
1704 and exchange information. It is generally considered to be a good
1705 thing, and some programs won't run unless you say Y here. In
1706 particular, if you want to run the DOS emulator dosemu under Linux
1707 (read the DOSEMU-HOWTO, available via FTP (user: anonymous) in
1708 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO), you'll need to say Y
1711 You can find documentation about IPC with "info ipc" and also in
1712 section 6.4 of the Linux Programmer's Guide, available via FTP
1713 (user: anonymous) from
1714 ftp://metalab.unc.edu/pub/Linux/docs/LDP/programmers-guide.
1716 Saying Y here enlarges your kernel by about 7 KB. Just say Y.
1718 BSD Process Accounting
1719 CONFIG_BSD_PROCESS_ACCT
1720 If you say Y here, a user level program will be able to instruct the
1721 kernel (via a special system call) to write process accounting
1722 information to a file: whenever a process exits, information about
1723 that process will be appended to the file by the kernel. The
1724 information includes things such as creation time, owning user,
1725 command name, memory usage, controlling terminal etc. (the complete
1726 list is in the struct acct in include/linux/acct.h). It is up to the
1727 user level program to do useful things with this information. This
1728 is generally a good idea, so say Y.
1732 The sysctl interface provides a means of dynamically changing
1733 certain kernel parameters and variables on the fly without requiring
1734 a recompile of the kernel or reboot of the system. The primary
1735 interface consists of a system call, but if the /proc filesystem is
1736 enabled, a tree of modifiable sysctl entries will be generated
1737 beneath the /proc/sys directory. They are explained in the files in
1738 Documentation/sysctl/. Note that enabling this option will enlarge
1739 the kernel by at least 8 KB.
1741 As it is generally a good thing, you should say Y here unless
1742 building a kernel for install/rescue disks or your system is very
1745 Kernel support for ELF binaries
1747 ELF (Executable and Linkable Format) is a format for libraries and
1748 executables used across different architectures and operating
1749 systems. Saying Y here will enable your kernel to run ELF binaries
1750 and enlarge it by about 2 KB. ELF support under Linux has now all
1751 but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC)
1752 because it is portable (this does *not* mean that you will be able
1753 to run executables from different architectures or operating systems
1754 however) and makes building run-time libraries very easy. Many new
1755 executables are distributed solely in ELF format. You definitely
1758 Information about ELF is contained in the ELF HOWTO available via
1759 FTP (user: anonymous) at ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
1761 If you find that after upgrading from Linux kernel 1.2 and saying Y
1762 here, you still can't run any ELF binaries (they just crash), then
1763 you'll have to install the newest ELF runtime libraries, including
1764 ld.so (check the file Documentation/Changes for location and latest
1767 If you want to compile this as a module ( = code which can be
1768 inserted in and removed from the running kernel whenever you want),
1769 say M here and read Documentation/modules.txt. The module will be
1770 called binfmt_elf.o. Saying M or N here is dangerous because some
1771 crucial programs on your system might be in ELF format.
1773 Kernel support for A.OUT binaries
1775 A.out (Assembler.OUTput) is a set of formats for libraries and
1776 executables used in the earliest versions of UNIX. Linux used the
1777 a.out formats QMAGIC and ZMAGIC until they were replaced with the
1780 As more and more programs are converted to ELF, the use for a.out
1781 will gradually diminish. If you disable this option it will reduce
1782 your kernel by one page. This is not much and by itself does not
1783 warrant removing support. However its removal is a good idea if you
1784 wish to ensure that absolutely none of your programs will use this
1785 older executable format. If you don't know what to answer at this
1786 point then answer Y. If someone told you "You need a kernel with
1787 QMAGIC support" then you'll have to say Y here. You may answer M to
1788 compile a.out support as a module and later load the module when you
1789 want to use a program or library in a.out format. The module will be
1790 called binfmt_aout.o. Saying M or N here is dangerous though,
1791 because some crucial programs on your system might still be in A.OUT
1794 Kernel support for Linux/Intel ELF binaries
1796 Say Y here if you want to be able to execute Linux/Intel ELF
1797 binaries just like native Alpha binaries on your Alpha machine. For
1798 this to work, you need to have the emulator /usr/bin/em86 in place.
1799 You may answer M to compile the emulation support as a module and
1800 later load the module when you want to use a Linux/Intel binary. The
1801 module will be called binfmt_em86.o. If unsure, say Y.
1803 Kernel support for MISC binaries
1805 If you say Y here, it will be possible to plug wrapper-driven binary
1806 formats into the kernel. You will like this especially when you use
1807 programs that need an interpreter to run like Java, Python or
1808 Emacs-Lisp. It's also useful if you often run DOS executables under
1809 the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available in
1810 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO). Once you have
1811 registered such a binary class with the kernel, you can start one of
1812 those programs simply by typing in its name at a shell prompt; Linux
1813 will automatically feed it to the correct interpreter.
1815 If you say Y here, you won't need "Kernel support for JAVA binaries"
1816 (CONFIG_BINFMT_JAVA) or "Kernel support for Linux/Intel ELF
1817 binaries" (CONFIG_BINFMT_EM86), as this is a more general solution.
1819 You can do other nice things, too. Read
1820 Documentation/binfmt_misc.txt to learn how to use this feature, and
1821 Documentation/java.txt for information about how to include Java
1824 You must say Y to "proc filesystem support" (CONFIG_PROC_FS) to
1825 use this part of the kernel.
1827 You may say M here for module support and later load the module when
1828 you have use for it; the module is called binfmt_misc.o. If you
1829 don't know what to answer at this point, say Y.
1831 Solaris binary emulation
1833 This is experimental code which will enable you to run (many)
1834 Solaris binaries on your SPARC Linux machine.
1836 This code is also available as a module ( = code which can be
1837 inserted in and removed from the running kernel whenever you want).
1838 The module will be called solaris.o. If you want to compile it as a
1839 module, say M here and read Documentation/modules.txt.
1843 This is the processor type of your CPU. This information is used for
1844 optimizing purposes. In order to compile a kernel that can run on
1845 all x86 CPU types (albeit not optimally fast), you can specify
1848 If you specify one of "486" or "586" or "Pentium" or "PPro", then
1849 the kernel will not necessarily run on earlier architectures (e.g. a
1850 Pentium optimized kernel will run on a PPro, but not necessarily on
1853 Here are the settings recommended for greatest speed:
1854 - "386" for the AMD/Cyrix/Intel 386DX/DXL/SL/SLC/SX, Cyrix/TI
1855 486DLC/DLC2 and UMC 486SX-S. Only "386" kernels will run on a 386
1857 - "486" for the AMD/Cyrix/IBM/Intel DX4 or 486DX/DX2/SL/SX/SX2,
1858 AMD/Cyrix 5x86, NexGen Nx586 and UMC U5D or U5S.
1859 - "586" for generic Pentium CPUs, possibly lacking the TSC
1860 (time stamp counter) register.
1861 - "Pentium" for the Intel Pentium/Pentium MMX, AMD K5, K6 and
1863 - "PPro" for the Cyrix/IBM/National Semiconductor 6x86MX, MII and
1864 Intel Pentium II/Pentium Pro.
1866 If you don't know what to do, choose "386".
1870 Saying Y here will allow you to use Linux in text mode through a
1871 display that complies with the generic VGA standard. Virtually
1872 everyone wants that.
1874 The program SVGATextMode can be used to utilize SVGA video cards to
1875 their full potential in text mode. Download it via FTP (user:
1876 anonymous) from ftp://metalab.unc.edu/pub/Linux/utils/console.
1880 Video mode selection support
1882 This enables support for text mode selection on kernel startup. If
1883 you want to take advantage of some high-resolution text mode your
1884 card's BIOS offers, but the traditional Linux utilities like
1885 SVGATextMode don't, you can say Y here and set the mode using the
1886 "vga=" option from your boot loader (lilo or loadlin) or set
1887 "vga=ask" which brings up a video mode menu on kernel startup. Try
1888 "man bootparam" or see the documentation of your boot loader about
1889 how to pass options to the kernel. The lilo procedure is also
1890 explained in the SCSI-HOWTO, available via FTP (user: anonymous) in
1891 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Read
1892 Documentation/svga.txt for more information about the Video mode
1893 selection support. If unsure, say N.
1895 Support for frame buffer devices (EXPERIMENTAL)
1897 The frame buffer device provides an abstraction for the graphics
1898 hardware. It represents the frame buffer of some video hardware and
1899 allows application software to access the graphics hardware through
1900 a well-defined interface, so the software doesn't need to know
1901 anything about the low-level (hardware register) stuff.
1903 Frame buffer devices work identically across the different
1904 architectures supported by Linux and make the implementation of
1905 application programs easier and more portable; at this point, an X
1906 server exists which uses the frame buffer device exclusively.
1907 On several non-X86 architectures, the frame buffer device is the
1908 only way to use the graphics hardware.
1910 The device is accessed through special device nodes, usually located
1911 in the /dev directory, i.e. /dev/fb*.
1913 You need an utility program called fbset to make full use of frame
1914 buffer devices. Please read Documentation/fb/framebuffer.txt and the
1915 Framebuffer-HOWTO at
1916 http://www.tahallah.demon.co.uk/programming/prog.html for more
1919 Say Y here and to the driver for your graphics board below if you
1920 are compiling a kernel for a non-x86 architecture.
1922 If you are compiling for the x86 architecture, you can say Y if you
1923 want to play with it, but it is not essential. Please note that
1924 running graphical applications that directly touch the hardware
1925 (e.g. an accelerated X server) and that are not frame buffer
1926 device-aware may cause unexpected results. If unsure, say N.
1930 This is the frame buffer device driver for the Acorn VIDC graphics
1933 Apollo frame buffer device
1935 This is the frame buffer device driver for the monochrome graphics
1936 hardware found in some Apollo workstations.
1938 Amiga native chipset support
1940 This is the frame buffer device driver for the builtin graphics
1941 chipset found in Amigas.
1943 Amiga OCS chipset support
1945 This enables support for the original Agnus and Denise video chips,
1946 found in the Amiga 1000 and most A500's and A2000's. If you intend
1947 to run Linux on any of these systems, say Y; otherwise say N.
1949 Amiga ECS chipset support
1951 This enables support for the Enhanced Chip Set, found in later
1952 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
1953 you intend to run Linux on any of these systems, say Y; otherwise
1956 Amiga AGA chipset support
1958 This enables support for the Advanced Graphics Architecture (also
1959 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
1960 and CD32. If you intend to run Linux on any of these systems, say Y;
1963 Amiga CyberVision support
1965 This enables support for the Cybervision 64 graphics card from
1966 Phase5. Please note that its use is not all that intuitive (i.e. if
1967 you have any questions, be sure to ask!). Say N unless you have a
1968 Cybervision 64 or plan to get one before you next recompile the
1969 kernel. Please note that this driver DOES NOT support the
1970 Cybervision 64 3D card, as they use incompatible video chips.
1972 Amiga CyberVision3D support (EXPERIMENTAL)
1974 This enables support for the Cybervision 64/3D graphics card from
1975 Phase5. Please note that its use is not all that intuitive (i.e. if
1976 you have any questions, be sure to ask!). Say N unless you have a
1977 Cybervision 64/3D or plan to get one before you next recompile the
1978 kernel. Please note that this driver DOES NOT support the older
1979 Cybervision 64 card, as they use incompatible video chips.
1981 Amiga RetinaZ3 support (EXPERIMENTAL)
1983 This enables support for the Retina Z3 graphics card. Say N unless
1984 you have a Retina Z3 or plan to get one before you next recompile
1987 Cirrus Logic generic driver (EXPERIMENTAL)
1989 This enables support for Cirrus Logic GD542x/543x based boards on
1990 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
1991 If you have a PCI-based system, this enables support for these chips:
1992 GD-543x, GD-544x, GD-5480.
1993 Say N unless you have such a graphics board or plan to get one
1994 before you next recompile the kernel.
1998 Say Y here if you want to run Linux on an MC680x0-based Apollo
1999 Domain workstation such as the DN3500.
2001 Apollo 3c505 support
2002 CONFIG_APOLLO_ELPLUS
2003 Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
2004 If you don't have one made for Apollos, you can use one from a PC,
2005 except that your Apollo won't be able to boot from it (because the
2006 code in the ROM will be for a PC).
2008 Atari native chipset support
2010 This is the frame buffer device driver for the builtin graphics
2011 chipset found in Ataris.
2013 Open Firmware frame buffer device support
2015 Say Y if you want support with Open Firmware for your graphics
2018 S3 Trio frame buffer device support
2020 If you have a S3 Trio say Y. Say N for S3 Virge.
2022 ATI Mach64 display support
2024 This driver supports graphics boards with the ATI Mach64 chips.
2026 PowerMac "control" frame buffer device support
2028 This driver supports a frame buffer for the graphics adapter in the
2029 Power Macintosh 7300 and others.
2031 PowerMac "platinum" frame buffer device support
2033 This driver supports a frame buffer for the "platinum" graphics
2034 adapter in some Power Macintoshes.
2036 PowerMac "valkyrie" frame buffer device support
2038 This driver supports a frame buffer for the "valkyrie" graphics
2039 adapter in some Power Macintoshes.
2041 Chips 65550 display support
2043 This is the frame buffer device driver for the Chips & Technologies
2044 65550 graphics chip in PowerBooks.
2046 Mac frame buffer device
2048 This is the frame buffer device driver for the graphics hardware in
2051 HP300 frame buffer device
2053 This is the frame buffer device driver for the Topcat graphics
2054 hardware found in HP300 workstations.
2056 TGA frame buffer support
2058 This is the frame buffer device driver for generic TGA graphic
2059 cards. Say Y if you have one of those.
2061 VESA VGA graphics console
2063 This is the frame buffer device driver for generic VESA 2.0
2064 compliant graphic cards. The older VESA 1.2 cards are not supported.
2065 You will get a boot time penguin logo at no additional cost. Please
2066 read Documentation/fb/vesafb.txt. If unsure, say Y.
2068 VGA 16-color graphics console
2070 This is the frame buffer device driver for VGA 16 color graphic
2071 cards. Say Y if you have such a card.
2073 Backward compatibility mode for Xpmac
2074 CONFIG_FB_COMPAT_XPMAC
2075 If you use the Xpmac X server (common with mklinux), you'll need to
2076 say Y here to use X. You should consider changing to XFree86 which
2077 includes a server that supports the frame buffer device directly
2080 Matrox unified accelerated driver
2082 Say Y here if you have Matrox Millennium, Matrox Millennium II,
2083 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
2084 Mystique G200, Matrox Millennium G200 or Matrox Marvel G200 video
2085 card in your box. At this time, support for the G100, Mystique G200
2086 and Marvel G200 is untested.
2088 This driver is also available as a module ( = code which can be
2089 inserted and removed from the running kernel whenever you want).
2090 The module will be called matroxfb.o. If you want to compile it as
2091 a module, say M here and read Documentation/modules.txt.
2093 You can pass several parameters to the driver at boot time or at
2094 module load time. The parameters look like "video=matrox:XXX", where
2095 the meaning of XXX can be found at the end of the main source file
2096 (drivers/video/matroxfb.c). Please see the file
2097 Documentation/fb/matroxfb.txt.
2099 Matrox Millennium support
2100 CONFIG_FB_MATROX_MILLENIUM
2101 Say Y here if you have a Matrox Millennium or Matrox Millennium II
2102 video card. If you select "Advanced lowlevel driver options" below,
2103 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
2104 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
2105 also use font widths different from 8.
2107 Matrox Mystique support
2108 CONFIG_FB_MATROX_MYSTIQUE
2109 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
2110 video card. If you select "Advanced lowlevel driver options" below,
2111 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
2112 packed pixel and 32 bpp packed pixel. You can also use font widths
2115 Matrox G100/G200 support
2116 CONFIG_FB_MATROX_G100
2117 Say Y here if you have a Matrox Productiva G100, Matrox Mystique
2118 G200, Matrox Marvel G200 or Matrox Millennium G200 video card. If
2119 you select "Advanced lowlevel driver options", you should check 8
2120 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed pixel and 32
2121 bpp packed pixel. You can also use font widths different from 8.
2123 Matrox unified driver multihead support
2124 CONFIG_FB_MATROX_MULTIHEAD
2125 Say Y here if you have more than one (supported) Matrox device in
2126 your computer and you want to use all of them. If you have only one
2127 device, you should say N because the driver compiled with Y is
2128 larger and a bit slower, especially on ia32 (ix86).
2130 If you said M to "Matrox unified accelerated driver" and N here, you
2131 will still be able to use several Matrox devices simultaneously.
2132 This is slightly faster but uses 40 KB of kernel memory per Matrox
2133 card. You do this by inserting several instances of the module
2134 matroxfb.o into the kernel with insmod, supplying the parameter
2135 "dev=N" where N is 0, 1, etc. for the different Matrox devices.
2137 MDA text console (dual-headed)
2139 Say Y here if you have an old MDA or monochrome Hercules graphics
2140 adapter in your system acting as a second head ( = video card). You
2141 will then be able to use two monitors with your Linux system. Do not
2142 say Y here if your MDA card is the primary card in your system; the
2143 normal VGA driver will handle it.
2145 This driver is also available as a module ( = code which can be
2146 inserted and removed from the running kernel whenever you want).
2147 The module will be called mdacon.o. If you want to compile it as
2148 a module, say M here and read Documentation/modules.txt.
2152 SBUS and UPA frame buffers
2154 Say Y if you want support for SBUS or UPA based frame buffer device.
2156 Creator/Creator3D support
2158 This is the frame buffer device driver for the Creator and Creator3D
2161 CGsix (GX,TurboGX) support
2163 This is the frame buffer device driver for the CGsix (GX, TurboGX)
2168 This is the frame buffer device driver for the BWtwo frame buffer.
2172 This is the frame buffer device driver for the CGthree frame buffer.
2174 TCX (SS4/SS5 only) support
2176 This is the frame buffer device driver for the TCX 24/8bit frame
2179 Virtual Frame Buffer support (ONLY FOR TESTING!)
2181 This is a `virtual' frame buffer device. It operates on a chunk of
2182 unswapable kernel memory instead of on the memory of a graphics
2183 board. This means you cannot see any output sent to this frame
2184 buffer device, while it does consume precious memory. The main use
2185 of this frame buffer device is testing and debugging the frame
2186 buffer subsystem. Do NOT enable it for normal systems! To protect
2187 the innocent, it has to be enabled explicitly at boot time using the
2188 kernel option `video=vfb:'.
2190 This driver is also available as a module ( = code which can be
2191 inserted and removed from the running kernel whenever you want). The
2192 module will be called vfb.o. If you want to compile it as a module,
2193 say M here and read Documentation/modules.txt.
2197 Advanced low level driver options
2198 CONFIG_FBCON_ADVANCED
2199 The frame buffer console uses character drawing routines that are
2200 tailored to the specific organization of pixels in the memory of
2201 your graphics hardware. These are called the low level frame buffer
2202 console drivers. Note that they are used for text console output
2203 only; they are NOT needed for graphical applications.
2205 If you say N here, the needed low level drivers are automatically
2206 enabled, depending on what frame buffer devices you selected above.
2207 This is recommended for most users.
2209 If you say Y here, you have more fine-grained control over which low
2210 level drivers are enabled. You can e.g. leave out low level drivers
2211 for color depths you do not intend to use for text consoles.
2213 Low level frame buffer console drivers can be modules ( = code which
2214 can be inserted and removed from the running kernel whenever you
2215 want). The modules will be called fbcon-*.o. If you want to compile
2216 (some of) them as modules, read Documentation/modules.txt.
2222 This is the low level frame buffer console driver for monochrome
2223 (2 colors) packed pixels.
2225 2 bpp packed pixels support
2227 This is the low level frame buffer console driver for 2 bits per
2228 pixel (4 colors) packed pixels.
2230 4 bpp packed pixels support
2232 This is the low level frame buffer console driver for 4 bits per
2233 pixel (16 colors) packed pixels.
2235 8 bpp packed pixels support
2237 This is the low level frame buffer console driver for 8 bits per
2238 pixel (256 colors) packed pixels.
2240 16 bpp packed pixels support
2242 This is the low level frame buffer console driver for 15 or 16 bits
2243 per pixel (32K or 64K colors, also known as `hicolor') packed
2246 24 bpp packed pixels support
2248 This is the low level frame buffer console driver for 24 bits per
2249 pixel (16M colors, also known as `truecolor') packed pixels. It is
2250 NOT for `sparse' 32 bits per pixel mode.
2252 32 bpp packed pixels support
2254 This is the low level frame buffer console driver for 32 bits per
2255 pixel (16M colors, also known as `truecolor') sparse packed pixels.
2257 Amiga bitplanes support
2259 This is the low level frame buffer console driver for 1 to 8
2260 bitplanes (2 to 256 colors) on Amiga.
2262 Amiga interleaved bitplanes support
2264 This is the low level frame buffer console driver for 1 to 8
2265 interleaved bitplanes (2 to 256 colors) on Amiga.
2267 Atari interleaved bitplanes (2 planes) support
2268 CONFIG_FBCON_IPLAN2P2
2269 This is the low level frame buffer console driver for 2 interleaved
2270 bitplanes (4 colors) on Atari.
2272 Atari interleaved bitplanes (4 planes) support
2273 CONFIG_FBCON_IPLAN2P4
2274 This is the low level frame buffer console driver for 4 interleaved
2275 bitplanes (16 colors) on Atari.
2277 Atari interleaved bitplanes (8 planes) support
2278 CONFIG_FBCON_IPLAN2P8
2279 This is the low level frame buffer console driver for 8 interleaved
2280 bitplanes (256 colors) on Atari.
2282 Mac variable bpp packed pixels support
2284 This is the low level frame buffer console driver for 1/2/4/8/16/32
2285 bits per pixel packed pixels on Mac. It supports variable font
2286 widths for low resolution screens.
2288 VGA characters/attributes support
2290 This is the low level frame buffer console driver for VGA text mode;
2291 it is used by frame buffer device drivers that support VGA text mode.
2293 Parallel-port support
2295 If you want to use devices connected to your machine's parallel port
2296 (the connector at the computer with 25 holes), e.g. printer, ZIP
2297 drive, PLIP link (Parallel Line Internet Protocol is mainly used to
2298 create a mini network by connecting the parallel ports of two local
2299 machines) etc., then you need to say Y here; please read
2300 Documentation/parport.txt and drivers/misc/BUGS-parport.
2302 For extensive information about drivers for many devices attaching
2303 to the parallel port see http://www.torque.net/linux-pp.html on the
2304 WWW (to browse the WWW, you need to have access to a machine on the
2305 Internet that has a program like lynx or netscape).
2307 It is possible to share a single parallel port among several devices
2308 and it is safe to compile all the corresponding drivers into the
2309 kernel. If you want to compile parallel port support as a module ( =
2310 code which can be inserted in and removed from the running kernel
2311 whenever you want), say M here and read Documentation/modules.txt.
2312 The module will be called parport.o. If you have more than one
2313 parallel port and want to specify which port and IRQ to be used by
2314 this driver at module load time, take a look at
2315 Documentation/networking/parport.txt.
2321 You should say Y here if you have a PC-style parallel port. All IBM
2322 PC compatible computers and some Alphas have PC-style parallel
2325 This code is also available as a module. If you want to compile it
2326 as a module ( = code which can be inserted in and removed from the
2327 running kernel whenever you want), say M here and read
2328 Documentation/modules.txt. The module will be called parport_pc.o.
2332 Use FIFO/DMA if available
2333 CONFIG_PARPORT_PC_FIFO
2334 Many parallel port chipsets provide hardware that can speed up
2335 printing. Say Y here if you want to take advantage of that.
2337 As well as actually having a FIFO, or DMA capability, the kernel
2338 will need to know which IRQ the parallel port has. By default,
2339 parallel port interrupts will not be used, and so neither will the
2340 FIFO. See Documentation/parport.txt to find out how to specify
2341 which IRQ/DMA to use.
2343 Support foreign hardware
2344 CONFIG_PARPORT_OTHER
2345 Say Y here if you want to be able to load driver modules to support
2346 other non-standard types of parallel ports. This causes a
2347 performance loss, so most people say N.
2349 Sun Ultra/AX-style hardware
2351 Say Y here if you need support for the parallel port hardware on Sun
2352 Ultra/AX machines. This code is also available as a module (say M),
2353 called parport_ax.o. If in doubt, saying N is the safe plan.
2355 IEEE1284 transfer modes
2357 If you have a printer that supports status readback or device ID, or
2358 want to use a device that uses enhanced parallel port transfer modes
2359 such as EPP and ECP, say Y here to enable advanced IEEE 1284
2360 transfer modes. Also say Y if you want device ID information to
2361 appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
2363 Enable loadable module support
2365 Kernel modules are small pieces of compiled code which can be
2366 inserted in or removed from the running kernel, using the programs
2367 insmod and rmmod. This is described in the file
2368 Documentation/modules.txt, including the fact that you have to say
2369 "make modules" in order to compile the modules that you chose during
2370 kernel configuration. Modules can be device drivers, file systems,
2371 binary executable formats, and so on. If you think that you may want
2372 to make use of modules with this kernel in the future, then say Y
2373 here. If unsure, say Y.
2375 Set version information on all symbols for modules
2377 Usually, modules have to be recompiled whenever you switch to a new
2378 kernel. Saying Y here makes it possible, and safe, to use the
2379 same modules even after compiling a new kernel; this requires the
2380 program modprobe. All the software needed for module support is in
2381 the modutils package (check the file Documentation/Changes for
2382 location and latest version). NOTE: if you say Y here but don't
2383 have the program genksyms (which is also contained in the above
2384 mentioned modutils package), then the building of your kernel will
2385 fail. If you are going to use modules that are generated from
2386 non-kernel sources, you would benefit from this option. Otherwise
2387 it's not that important. So, N ought to be a safe bet.
2389 Kernel module loader support
2391 Normally when you have selected some drivers and/or filesystems to
2392 be created as loadable modules, you also have the responsibility to
2393 load the corresponding modules (using the programs insmod or
2394 modprobe) before you can use them. If you say Y here however, the
2395 kernel will be able to load modules for itself: when a part of the
2396 kernel needs a module, it runs modprobe with the appropriate
2397 arguments, thereby loading the module if it is available. (This is a
2398 replacement for kerneld.) Say Y here and read about configuring it
2399 in Documentation/kmod.txt.
2401 ARP daemon support (EXPERIMENTAL)
2403 Normally, the kernel maintains an internal cache which maps IP
2404 addresses to hardware addresses on the local network, so that
2405 Ethernet/Token Ring/ etc. frames are sent to the proper address on
2406 the physical networking layer. For small networks having a few
2407 hundred directly connected hosts or less, keeping this address
2408 resolution (ARP) cache inside the kernel works well. However,
2409 maintaining an internal ARP cache does not work well for very large
2410 switched networks, and will use a lot of kernel memory if TCP/IP
2411 connections are made to many machines on the network.
2413 If you say Y here, the kernel's internal ARP cache will never grow
2414 to more than 256 entries (the oldest entries are expired in a LIFO
2415 manner) and communication will be attempted with the user space ARP
2416 daemon arpd. Arpd then answers the address resolution request either
2417 from its own cache or by asking the net.
2419 This code is experimental. If you do say Y here, you should obtain a
2420 copy of arpd from http://www.loran.com/~layes/arpd/index.html, and
2421 you should also say Y to "Kernel/User network link driver", below.
2426 These are the protocols used on the Internet and on most local
2427 Ethernets. It is highly recommended to say Y here (this will enlarge
2428 your kernel by about 35 KB), since some programs (e.g. the X window
2429 system) use TCP/IP even if your machine is not connected to any
2430 other computer. You will get the so-called loopback device which
2431 allows you to ping yourself (great fun, that!).
2433 For an excellent introduction to Linux networking, please read the
2434 NET-3-HOWTO, available via FTP (user: anonymous) from
2435 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
2437 This option is also necessary if you want to use the full power of
2438 term (term is a program which gives you almost full Internet
2439 connectivity if you have a regular dial up shell account on some
2440 Internet connected Unix computer; for more information, read
2441 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html).
2443 If you say Y here and also to "/proc filesystem support" and "Sysctl
2444 support" below, you can change various aspects of the behavior of
2445 the TCP/IP code by writing to the (virtual) files in
2446 /proc/sys/net/ipv4/*; the options are explained in the file
2447 Documentation/Networking/ip-sysctl.txt.
2449 Short answer: say Y.
2453 This is code for addressing several networked computers at once,
2454 enlarging your kernel by about 2 kB. You need multicasting if you
2455 intend to participate in the MBONE, a high bandwidth network on top
2456 of the Internet which carries audio and video broadcasts. More
2457 information about the MBONE is on the WWW at
2458 http://www.best.com/~prince/techinfo/mbone.html (to browse the WWW,
2459 you need to have access to a machine on the Internet that has a
2460 program like lynx or netscape). Information about the multicast
2461 capabilities of the various network cards is contained in
2462 Documentation/networking/multicast.txt. For most people, it's safe
2466 CONFIG_IP_ADVANCED_ROUTER
2467 If you intend to run your Linux box mostly as a router, i.e. as a
2468 computer that forwards and redistributes network packets, say Y; you
2469 will then be presented with several options that allow more precise
2470 control about the routing process.
2472 The answer to this question won't directly affect the kernel:
2473 answering N will just cause this configure script to skip all the
2474 questions about advanced routing.
2476 Note that your box can only act as a router if you enable IP
2477 forwarding in your kernel; you can do that by saying Y to "/proc
2478 filesystem support" and "Sysctl support" below and executing the
2481 echo "1" > /proc/sys/net/ipv4/ip_forward
2483 at boot time after the /proc filesystem has been mounted.
2485 If you turn on IP forwarding, you will also get the rp_filter, which
2486 automatically rejects incoming packets if the routing table entry
2487 for their source address doesn't match the network interface they're
2488 arriving on. This has security advantages because it prevents the
2489 so-called IP spoofing, however it can pose problems if you use
2490 asymmetric routing (packets from you to a host take a different path
2491 than packets from that host to you) or if you operate a non-routing
2492 host which has several IP addresses on different interfaces. To turn
2495 echo 0 > /proc/sys/net/ipv4/conf/<device>/rp_filter
2497 echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter
2499 If unsure, say N here.
2502 CONFIG_IP_MULTIPLE_TABLES
2503 Normally, a router decides what to do with a received packet based
2504 solely on the packet's final destination address. If you say Y here,
2505 the Linux router will also be able to take the packet's source
2506 address into account. Furthermore, if you also say Y to "IP: use TOS
2507 value as routing key" below, the TOS (Type-Of-Service) field of the
2508 packet can be used for routing decisions as well. In addition, if
2509 you say Y here and to "IP: fast network address translation" below,
2510 the router will also be able to modify source and destination
2511 addresses of forwarded packets.
2513 If you are interested in this, please see the preliminary
2514 documentation at http://www.compendium.com.ar/policy-routing.txt and
2515 ftp://post.tepkom.ru/pub/vol2/Linux/docs/advanced-routing.tex. You
2516 will need supporting software from ftp://ftp.inr.ac.ru/ip-routing/
2520 IP: equal cost multipath
2521 CONFIG_IP_ROUTE_MULTIPATH
2522 Normally, the routing tables specify a single action to be taken in
2523 a deterministic manner for a given packet. If you say Y here
2524 however, it becomes possible to attach several actions to a packet
2525 pattern, in effect specifying several alternative paths to travel
2526 for those packets. The router considers all these paths to be of
2527 equal "cost" and chooses one of them in a non-deterministic fashion
2528 if a matching packet arrives.
2530 IP: use TOS value as routing key
2532 The header of every IP packet carries a TOS (Type of Service) value
2533 with which the packet requests a certain treatment, e.g. low latency
2534 (for interactive traffic), high throughput, or high reliability. If
2535 you say Y here, you will be able to specify different routes for
2536 packets with different TOS values.
2538 IP: use FWMARK value as routing key
2539 CONFIG_IP_ROUTE_FWMARK
2540 If you say Y here, you will be able to specify different routes for
2541 packets with different FWMARK ("firewalling mark") values
2542 (see ipchains(8), "-m" argument).
2544 IP: verbose route monitoring
2545 CONFIG_IP_ROUTE_VERBOSE
2546 If you say Y here, which is recommended, then the kernel will print
2547 verbose messages regarding the routing, for example warnings about
2548 received packets which look strange and could be evidence of an
2549 attack or a misconfigured system somewhere. The information is
2550 handled by the klogd daemon which is responsible for kernel messages
2553 IP: large routing tables
2554 CONFIG_IP_ROUTE_LARGE_TABLES
2555 If you have routing zones that grow to more than about 64 entries,
2556 you may want to say Y here to speed up the routing process.
2558 IP: fast network address translation
2560 If you say Y here, your router will be able to modify source and
2561 destination addresses of packets that pass through it, in a manner
2562 you specify. General information about Network Address Translation
2563 can be gotten from the document
2564 http://www.csn.tu-chemnitz.de/~mha/linux-ip-nat/diplom/nat.html
2566 IP: optimize as router not host
2568 Some Linux network drivers use a technique called copy and checksum
2569 to optimize host performance. For a machine which acts as a router
2570 most of the time and is forwarding most packets to another host this
2571 is however a loss. If you say Y here, copy and checksum will be
2572 switched off. In the future, it may make other changes which
2573 optimize for router operation.
2575 Note that your box can only act as a router if you enable IP
2576 forwarding in your kernel; you can do that by saying Y to "/proc
2577 filesystem support" and "Sysctl support" below and executing the
2580 echo "1" > /proc/sys/net/ipv4/ip_forward
2582 at boot time after the /proc filesystem has been mounted. You can do
2583 that even if you say N here.
2585 If unsure, say N here.
2587 IP: kernel level autoconfiguration
2589 This enables automatic configuration of IP addresses of devices and
2590 of the routing table during kernel boot, based on either information
2591 supplied at the kernel command line or by BOOTP or RARP protocols.
2592 You need to say Y only for diskless machines requiring network
2593 access to boot (in which case you want to say Y to "Root file system
2594 on NFS" as well), because all other machines configure the network
2595 in their startup scripts.
2599 If you want your Linux box to mount its whole root filesystem (the
2600 one containing the directory /) from some other computer over the
2601 net via NFS and you want the IP address of your computer to be
2602 discovered automatically at boot time using the BOOTP protocol (a
2603 special protocol designed for doing this job), say Y here. In case
2604 the boot ROM of your network card was designed for booting Linux and
2605 does BOOTP itself, providing all necessary information on the kernel
2606 command line, you can say N here. If unsure, say Y. Note that if you
2607 want to use BOOTP, a BOOTP server must be operating on your network.
2608 Read Documentation/nfsroot.txt for details.
2612 If you want your Linux box to mount its whole root filesystem (the
2613 one containing the directory /) from some other computer over the
2614 net via NFS and you want the IP address of your computer to be
2615 discovered automatically at boot time using the RARP protocol (an
2616 older protocol which is being obsoleted by BOOTP and DHCP), say Y
2617 here. Note that if you want to use RARP, a RARP server must be
2618 operating on your network. Read Documentation/nfsroot.txt for
2623 Tunneling means encapsulating data of one protocol type within
2624 another protocol and sending it over a channel that understands the
2625 encapsulating protocol. This particular tunneling driver implements
2626 encapsulation of IP within IP, which sounds kind of pointless, but
2627 can be useful if you want to make your (or some other) machine
2628 appear on a different network than it physically is, or to use
2629 mobile-IP facilities (allowing laptops to seamlessly move between
2630 networks without changing their IP addresses; check out
2631 http://anchor.cs.binghamton.edu/~mobileip/LJ/index.html).
2633 Saying Y to this option will produce two modules ( = code which can
2634 be inserted in and removed from the running kernel whenever you
2635 want). Most people won't need this and can say N.
2637 IP: GRE tunnels over IP
2639 Tunneling means encapsulating data of one protocol type within
2640 another protocol and sending it over a channel that understands the
2641 encapsulating protocol. This particular tunneling driver implements
2642 GRE (Generic Routing Encapsulation) and at this time allows
2643 encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
2644 This driver is useful if the other endpoint is a Cisco router: Cisco
2645 likes GRE much better than the other Linux tunneling driver ("IP:
2646 tunneling" above). In addition, GRE allows multicast redistribution
2649 IP: broadcast GRE over IP
2650 CONFIG_NET_IPGRE_BROADCAST
2651 One application of GRE/IP is to construct a broadcast WAN (Wide Area
2652 Network), which looks like a normal Ethernet LAN (Local Area
2653 Network), but can be distributed all over the Internet. If you want
2654 to do that, say Y here and to "IP: multicast routing" below.
2656 IP: aliasing support
2658 Sometimes it is useful to give several IP addresses to a single
2659 physical network interface (serial port or Ethernet card). The most
2660 common case is that you want to serve different WWW or ftp documents
2661 to the outside depending on which of your host names was used to
2662 connect to you. This is called "multihosting" or "virtual domains"
2663 or "virtual hosting services" and is explained in detail on the WWW
2664 at http://www.thesphere.com/~dlp/TwoServers/ (to browse the WWW, you
2665 need to have access to a machine on the Internet that has a program
2666 like lynx or netscape) and also in the Virtual-Services-HOWTO,
2667 available via FTP (user: anonymous) from
2668 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
2670 Another scenario would be that there are two logical networks living
2671 on your local Ethernet and you want to access them both with the
2672 same Ethernet card. This can also be done if you say Y here.
2674 The configuration of these alias addresses is done with a special
2675 name syntax explained in Documentation/networking/alias.txt and in
2676 the IP-Alias mini-HOWTO. If you want this, say Y. Most people don't
2679 IP: multicast routing
2681 This is used if you want your machine to act as a router for IP
2682 packets that have several destination addresses. It is needed on the
2683 MBONE, a high bandwidth network on top of the Internet which carries
2684 audio and video broadcasts. In order to do that, you would most
2685 likely run the program mrouted. Information about the multicast
2686 capabilities of the various network cards is contained in
2687 Documentation/networking/multicast.txt. If you haven't heard about
2688 it, you don't need it.
2690 IP: PIM-SM version 1 support
2692 Kernel side support for Sparse Mode PIM (Protocol Independent
2693 Multicast) version 1. This multicast routing protocol is used widely
2694 because Cisco supports it. You need special software to use it
2695 (pimd-v1). Please see http://netweb.usc.edu/pim/ for more
2696 information about PIM (to browse the WWW, you need to have access to
2697 a machine on the Internet that has a program like lynx or
2700 Say Y if you want to use PIM-SM v1. Note that you can say N here if
2701 you just want to use Dense Mode PIM.
2703 IP: PIM-SM version 2 support
2705 Kernel side support for Sparse Mode PIM version 2. In order to use
2706 this, you need an experimental routing daemon supporting it (pimd or
2707 gated-5). This routing protocol is not used widely, so say N unless
2708 you want to play with it.
2710 PC/TCP compatibility mode
2712 If you have been having difficulties telnetting to your Linux
2713 machine from a DOS system that uses (broken) PC/TCP networking
2714 software (all versions up to OnNet 2.0) over your local Ethernet try
2715 saying Y here. Everyone else says N.
2717 People having problems with NCSA telnet should see the file
2718 linux/Documentation/networking/ncsa-telnet.
2722 If there are (usually diskless or portable) machines on your local
2723 network that know their hardware Ethernet addresses but don't know
2724 their IP addresses upon startup, they can send out a Reverse Address
2725 Resolution Protocol (RARP) request to find out their own IP
2726 addresses. Diskless Sun 3 machines use this procedure at boot time,
2727 and diskless Linux boxes can be configured to do it as well.
2729 If you want your Linux box to be able to *answer* such requests,
2730 answer Y here; you'll then have to run the program rarp ("man rarp")
2733 If you actually want to use a diskless Sun 3 machine as an X
2734 terminal to Linux, say Y here and fetch Linux-Xkernel from
2735 ftp://metalab.unc.edu/pub/Linux/system/network/boot.net/.
2737 Superior solutions to the problem of booting and configuring
2738 machines over a net connection are given by the protocol BOOTP and
2739 its successor DHCP. See the DHCP FAQ
2740 http://web.syr.edu/~jmwobus/comfaqs/dhcp.faq.html for details (to
2741 browse the WWW, you need to have access to a machine on the Internet
2742 that has a program like lynx or netscape).
2744 If you want to compile RARP support as a module ( = code which can
2745 be inserted in and removed from the running kernel whenever you
2746 want), say M here and read Documentation/modules.txt. The module
2747 will be called rarp.o.
2749 If you don't understand a word of the above, say N and rest in
2752 Assume subnets are local
2754 Say Y if you are on a subnetted network with all machines connected
2755 by Ethernet segments only, as this option optimizes network access
2756 for this special case. If there are other connections, e.g. SLIP
2757 links, between machines of your IP network, say N. If in doubt,
2758 answer N. The PATH mtu discovery facility will cover most cases
2761 Path MTU Discovery (normally enabled)
2762 CONFIG_PATH_MTU_DISCOVERY
2763 MTU (maximal transfer unit) is the size of the chunks we send out
2764 over the net. "Path MTU Discovery" means that, instead of always
2765 sending very small chunks, we start out sending big ones and if we
2766 then discover that some host along the way likes its chunks smaller,
2767 we adjust to a smaller size. This is good, so most people say Y
2770 However, some DOS software (versions of DOS NCSA telnet and Trumpet
2771 Winsock in PPP mode) is broken and won't be able to connect to your
2772 Linux machine correctly in all cases (especially through a terminal
2773 server) unless you say N here. See
2774 Documentation/networking/ncsa-telnet for the location of fixed NCSA
2775 telnet clients. If in doubt, say Y.
2777 Disable NAGLE algorithm (normally enabled)
2778 CONFIG_TCP_NAGLE_OFF
2779 The NAGLE algorithm works by requiring an acknowledgment before
2780 sending small IP frames (packets). This keeps tiny telnet and
2781 rlogin packets from congesting Wide Area Networks. Most people
2782 strongly recommend to say N here, thereby leaving NAGLE
2783 enabled. Those programs that would benefit from disabling this
2784 facility can do it on a per connection basis themselves.
2786 IP: Allow large windows (not recommended if <16 MB of memory)
2788 On high speed, long distance networks the performance limit on
2789 networking becomes the amount of data the sending machine can buffer
2790 until the other end confirms its reception. (At 45 Mbit/second there
2791 are a lot of bits between New York and London ...). If you say Y
2792 here, bigger buffers can be used which allows larger amounts of data
2793 to be "in flight" at any given time. It also means a user process
2794 can require a lot more memory for network buffers and thus this
2795 option is best used only on machines with 16 MB of memory or higher.
2796 Unless you are using long links with end to end speeds of over 2
2797 Mbit a second or satellite links this option will make no difference
2802 If you say Y here, you will include support for Unix domain sockets;
2803 sockets are the standard Unix mechanism for establishing and
2804 accessing network connections. Many commonly used programs such as
2805 the X Window system and syslog use these sockets even if your
2806 machine is not connected to any network. Unless you are working on
2807 an embedded system or something similar, you therefore definitely
2810 However, the socket support is also available as a module ( = code
2811 which can be inserted in and removed from the running kernel
2812 whenever you want). If you want to compile it as a module, say M
2813 here and read Documentation/modules.txt. The module will be called
2814 unix.o. If you try building this as a module and you have said Y to
2815 "Kernel module loader support" above, be sure to add 'alias net-pf-1
2816 unix' to your /etc/conf.modules file. Note that several important
2817 services won't work correctly if you say M here and then neglect to
2820 Say Y unless you know what you are doing.
2824 This is experimental support for the next version of the Internet
2825 Protocol: IP version 6 (also called IPng "IP next generation").
2826 Features of this new protocol include: expanded address space,
2827 authentication and privacy, and seamless interoperability with the
2828 current version of IP (IP version 4). For general information about
2829 IPv6, see http://playground.sun.com/pub/ipng/html/ipng-main.html (to
2830 browse the WWW, you need to have access to a machine on the Internet
2831 that has a program like lynx or netscape); for specific information
2832 about IPv6 under Linux read http://www.bieringer.de/linux/IPv6/ and
2833 the file net/ipv6/README in the kernel source.
2835 If you want to use IPv6, please upgrade to the newest net-tools as
2836 given in Documentation/Changes. You will still be able to do regular
2837 IPv4 networking as well.
2839 This protocol support is also available as a module ( = code which
2840 can be inserted in and removed from the running kernel whenever you
2841 want). The module will be called ipv6.o. If you want to compile it
2842 as a module, say M here and read Documentation/modules.txt.
2844 It is safe to say N here for now.
2846 IPv6: enable EUI-64 token format
2848 6bone, the network of computers using the IPv6 protocol, is moving
2849 to a new aggregatable address format and a new link local address
2850 assignment (EUI-64). Say Y if your site has upgraded already, or
2851 has started to upgrade.
2853 IPv6: disable provider based addresses
2855 Linux tries to operate correctly when your site has moved to EUI-64
2856 only partially. Unfortunately, the two address formats (old:
2857 "provider based" and new: "aggregatable") are incompatible. Say Y if
2858 your site finished the upgrade to EUI-64, and/or you encountered
2859 some problems caused by the presence of two link-local addresses on
2862 IPv6: routing messages via old netlink
2864 You can say Y here to receive routing messages from the IPv6 code
2865 through the old netlink interface. However, a better option is to
2866 say Y to "Kernel/User network link driver" and to "Routing
2871 This is support for the Novell networking protocol, IPX, commonly
2872 used for local networks of Windows machines. You need it if you want
2873 to access Novell NetWare file or print servers using the Linux
2874 Novell client ncpfs (available via FTP (user: anonymous) from
2875 ftp://metalab.unc.edu/pub/Linux/system/filesystems/) or from within
2876 the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available in
2877 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO). In order to do the
2878 former, you'll also have to say Y to "NCP filesystem support",
2881 IPX is similar in scope to IP, while SPX, which runs on top of IPX,
2882 is similar to TCP. There is also experimental support for SPX in
2883 Linux (see "SPX networking", below).
2885 To turn your Linux box into a fully featured NetWare file server and
2886 IPX router, say Y here and fetch either lwared from
2887 ftp://metalab.unc.edu/pub/Linux/system/network/daemons/ or mars_nwe
2888 from ftp://ftp.gwdg.de/pub/linux/misc/ncpfs. For more information,
2889 read the IPX-HOWTO in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
2891 General information about how to connect Linux, Windows machines and
2892 Macs is on the WWW at http://www.eats.com/linux_mac_win.html (to
2893 browse the WWW, you need to have access to a machine on the Internet
2894 that has a program like lynx or netscape).
2896 The IPX driver would enlarge your kernel by about 5 kB. This driver
2897 is also available as a module ( = code which can be inserted in and
2898 removed from the running kernel whenever you want). The module will
2899 be called ipx.o. If you want to compile it as a module, say M here
2900 and read Documentation/modules.txt. Unless you want to integrate
2901 your Linux box with a local Novell network, say N.
2903 IPX: Full internal IPX network
2905 Every IPX network has an address that identifies it. Sometimes it is
2906 useful to give an IPX "network" address to your Linux box as well
2907 (for example if your box is acting as a file server for different
2908 IPX networks: it will then be accessible from everywhere using the
2909 same address). The way this is done is to create a virtual internal
2910 "network" inside your box and to assign an IPX address to this
2911 network. Say Y here if you want to do this; read the IPX-HOWTO at
2912 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO for details.
2914 The full internal IPX network enables you to allocate sockets on
2915 different virtual nodes of the internal network. This is done by
2916 evaluating the field sipx_node of the socket address given to the
2917 bind call. So applications should always initialize the node field
2918 to 0 when binding a socket on the primary network. In this case the
2919 socket is assigned the default node that has been given to the
2920 kernel when the internal network was created. By enabling the full
2921 internal IPX network the cross-forwarding of packets targeted at
2922 'special' sockets to sockets listening on the primary network is
2923 disabled. This might break existing applications, especially RIP/SAP
2924 daemons. A RIP/SAP daemon that works well with the full internal net
2925 can be found on ftp://ftp.gwdg.de/pub/linux/misc/ncpfs.
2927 If you don't know what you are doing, say N.
2929 IPX: SPX networking (EXPERIMENTAL)
2931 The Sequenced Packet eXchange protocol is a transport layer protocol
2932 built on top of IPX. It is used in Novell NetWare systems for
2933 client-server applications and is similar to TCP (which runs on top
2936 Note that Novell NetWare file sharing does not use SPX; it uses a
2937 protocol called NCP, for which separate Linux support is available
2938 ("NCP filesystem support" below for the client side, and the user
2939 space programs lwared or mars_nwe for the server side).
2941 Say Y here if you have use for SPX; read the IPX-HOWTO at
2942 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO for details.
2944 This driver is also available as a module ( = code which can be
2945 inserted in and removed from the running kernel whenever you want).
2946 The module will be called af_spx.o. If you want to compile it as a
2947 module, say M here and read Documentation/modules.txt.
2951 The DECnet networking protocol was used in many products made by
2952 Digital (now Compaq). It provides reliable stream and sequenced
2953 packet communications over which run a variety of services similar
2954 to those which run over TCP/IP.
2956 To find some tools to use with the kernel layer support, please
2957 look at Patrick Caulfield's web site:
2958 http://linux.dreamtime.org/decnet/
2960 More detailed documentation is available in the
2961 Documentation/networking/decnet.txt file.
2963 Be sure to turn on the CONFIG_PROCFS and CONFIG_SYSCTL options
2964 when using DECnet, since you will need sysctl support to aid in
2965 configuration at run time.
2967 DECnet SIOCFIGCONF support
2968 CONFIG_DECNET_SIOCGIFCONF
2969 This option should only be turned on if you are really sure that
2970 you know what you are doing. It can break other applications which
2971 use this system call and the proper way to get the information
2972 provided by this call is to use rtnetlink.
2974 DECnet Router Support
2975 CONFIG_DECNET_ROUTER
2976 Add support for turning your DECnet Endnode into a level 1 or 2
2977 router. This is an unfinished option for developers only. If you
2978 do turn it on, then make sure you also have rtnetlink configured
2979 in, since thats the only current method of configuration.
2981 DECnet Raw Socket Support
2983 Add support for the SOCK_RAW type under DECnet. Used by userland
2984 routing programs to receive routing messages from the kernel and
2985 also as a general debugging aid to see whats going on "under the hood".
2989 AppleTalk is the way Apple computers speak to each other on a
2990 network. If your Linux box is connected to such a network and you
2991 want to join the conversation, say Y. You will need to use the
2992 netatalk package so that your Linux box can act as a print and file
2993 server for Macs as well as access AppleTalk printers. Check out
2994 http://threepio.hitchcock.org/cgi-bin/faq/netatalk/faq.pl on the WWW
2995 for details (to browse the WWW, you need to have access to a machine
2996 on the Internet that has a program like lynx or netscape). EtherTalk
2997 is the name used for AppleTalk over Ethernet and the cheaper and
2998 slower LocalTalk is AppleTalk over a proprietary Apple network using
2999 serial links. EtherTalk and LocalTalk are fully supported by Linux.
3001 General information about how to connect Linux, Windows machines and
3002 Macs is on the WWW at http://www.eats.com/linux_mac_win.html
3003 The NET-3-HOWTO, available via FTP (user: anonymous) in
3004 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO contains valuable
3005 information as well.
3007 This driver is also available as a module ( = code which can be
3008 inserted in and removed from the running kernel whenever you want).
3009 The module is called appletalk.o. If you want to compile it as a
3010 module, say M here and read Documentation/modules.txt. I hear that
3011 the GNU boycott of Apple is over, so even politically correct people
3012 are allowed to say Y here.
3014 AppleTalk-IP driver support
3016 This allows IP networking for users who only have AppleTalk
3017 networking available. This feature is experimental. With this
3018 driver, you can encapsulate IP inside AppleTalk (e.g. if your Linux
3019 box is stuck on an AppleTalk only network) or decapsulate (e.g. if
3020 you want your Linux box to act as an Internet gateway for a zoo of
3021 AppleTalk connected Macs). Please see the file
3022 Documentation/networking/ipddp.txt for more information.
3024 If you say Y here, the AppleTalk-IP support will be compiled into
3025 the kernel. In this case, you can either use encapsulation or
3026 decapsulation, but not both. With the following two questions, you
3027 decide which one you want.
3029 If you say M here, the AppleTalk-IP support will be compiled as a
3030 module ( = code which can be inserted in and removed from the
3031 running kernel whenever you want, read Documentation/modules.txt).
3032 The module is called ipddp.o. In this case, you will be able to use
3033 both encapsulation and decapsulation simultaneously, by loading two
3034 copies of the module and specifying different values for the module
3037 IP to AppleTalk-IP Encapsulation support
3039 If you say Y here, the AppleTalk-IP code will be able to encapsulate
3040 IP packets inside AppleTalk frames; this is useful if your Linux box
3041 is stuck on an AppleTalk network (which hopefully contains a
3042 decapsulator somewhere). Please see
3043 Documentation/networking/ipddp.txt for more information. If you said
3044 Y to "AppleTalk-IP driver support" above and you say Y here, then
3045 you cannot say Y to "AppleTalk-IP to IP Decapsulation support",
3048 AppleTalk-IP to IP Decapsulation support
3050 If you say Y here, the AppleTalk-IP code will be able to decapsulate
3051 AppleTalk-IP frames to IP packets; this is useful if you want your
3052 Linux box to act as an Internet gateway for an AppleTalk network.
3053 Please see Documentation/networking/ipddp.txt for more information.
3054 If you said Y to "AppleTalk-IP driver support" above and you say Y
3055 here, then you cannot say Y to "IP to AppleTalk-IP Encapsulation
3058 Apple/Farallon LocalTalk PC card support
3060 This allows you to use the AppleTalk PC card to connect to LocalTalk
3061 networks. The card is also known as the Farallon PhoneNet PC card.
3062 If you are in doubt, this card is the one with the 65C02 chip on it.
3063 You also need version 1.3.3 or later of the netatalk package.
3064 This driver is experimental, which means that it may not work.
3065 See the file Documentation/networking/ltpc.txt.
3067 COPS LocalTalk PC card support
3069 This allows you to use COPS AppleTalk cards to connect to LocalTalk
3070 networks. You also need version 1.3.3 or later of the netatalk
3071 package. This driver is experimental, which means that it may not
3072 work. This driver will only work if you choose "AppleTalk DDP"
3073 networking support, above.
3074 Please read the file Documentation/networking/cops.txt.
3076 Dayna firmware support
3078 Support COPS compatible cards with Dayna style firmware (Dayna
3079 DL2000/ Daynatalk/PC (half length), COPS LT-95, Farallon PhoneNET PC
3080 III, Farallon PhoneNET PC II).
3082 Tangent firmware support
3084 Support COPS compatible cards with Tangent style firmware (Tangent
3085 ATB_II, Novell NL-1000, Daystar Digital LT-200.
3087 Amateur Radio support
3089 If you want to connect your Linux box to an amateur radio, answer Y
3090 here. You want to read http://www.tapr.org/tapr/html/pkthome.html
3091 (to browse the WWW, you need to have access to a machine on the
3092 Internet that has a program like lynx or netscape) and the HAM-HOWTO
3093 and the AX25-HOWTO, both available via FTP (user: anonymous) from
3094 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
3096 Note that the answer to this question won't directly affect the
3097 kernel: saying N will just cause this configure script to skip all
3098 the questions about amateur radio.
3100 Amateur Radio AX.25 Level 2
3102 This is the protocol used for computer communication over amateur
3103 radio. It is either used by itself for point-to-point links, or to
3104 carry other protocols such as tcp/ip. To use it, you need a device
3105 that connects your Linux box to your amateur radio. You can either
3106 use a low speed TNC (a Terminal Node Controller acts as a kind of
3107 modem connecting your computer's serial port to your radio's
3108 microphone input and speaker output) supporting the KISS protocol or
3109 one of the various SCC cards that are supported by the generic Z8530
3110 or the DMA SCC driver. Another option are the Baycom modem serial
3111 and parallel port hacks or the sound card modem (supported by their
3112 own drivers). If you say Y here, you also have to say Y to one of
3115 Information about where to get supporting software for Linux amateur
3116 radio as well as information about how to configure an AX.25 port is
3117 contained in the AX25-HOWTO, available via FTP (user: anonymous) in
3118 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. You might also want to
3119 check out the file Documentation/networking/ax25.txt in the kernel
3120 source. More information about digital amateur radio in general is
3121 on the WWW at http://www.tapr.org/tapr/html/pkthome.html. (To browse
3122 the WWW, you need to have access to a machine on the Internet that
3123 has a program like lynx or netscape).
3125 This driver is also available as a module ( = code which can be
3126 inserted in and removed from the running kernel whenever you want).
3127 The module will be called ax25.o. If you want to compile it as a
3128 module, say M here and read Documentation/modules.txt.
3130 AX.25 DAMA Slave support
3131 CONFIG_AX25_DAMA_SLAVE
3132 DAMA is a mechanism to prevent collisions when doing AX.25
3133 networking. A DAMA server (called "master") accepts incoming traffic
3134 from clients (called "slaves") and redistributes it to other slaves.
3135 If you say Y here, your Linux box will act as a DAMA slave; this is
3136 transparent in that you don't have to do any special DAMA
3137 configuration. (Linux cannot yet act as a DAMA server.) If unsure,
3140 AX.25 DAMA Master support
3141 CONFIG_AX25_DAMA_MASTER
3142 DAMA is a mechanism to prevent collisions when doing AX.25
3143 networking. A DAMA server (called "master") accepts incoming traffic
3144 from clients (called "slaves") and redistributes it to other
3145 slaves. If you say Y here, your Linux box will act as a DAMA server.
3148 Amateur Radio NET/ROM
3150 NET/ROM is a network layer protocol on top of AX.25 useful for
3153 A comprehensive listing of all the software for Linux amateur radio
3154 users as well as information about how to configure an AX.25 port is
3155 contained in the AX25-HOWTO, available via FTP (user: anonymous) in
3156 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. You also might want to
3157 check out the file Documentation/networking/ax25.txt. More
3158 information about digital amateur radio in general is on the WWW at
3159 http://www.tapr.org/tapr/html/pkthome.html (to browse the WWW, you
3160 need to have access to a machine on the Internet that has a program
3161 like lynx or netscape).
3163 This driver is also available as a module ( = code which can be
3164 inserted in and removed from the running kernel whenever you want).
3165 The module will be called netrom.o. If you want to compile it as a
3166 module, say M here and read Documentation/modules.txt.
3168 Amateur Radio X.25 PLP (Rose)
3170 The Packet Layer Protocol (PLP) is a way to route packets over X.25
3171 connections in general and amateur radio AX.25 connections in
3172 particular, essentially an alternative to NET/ROM.
3174 A comprehensive listing of all the software for Linux amateur radio
3175 users as well as information about how to configure an AX.25 port is
3176 contained in the AX25-HOWTO, available via FTP (user: anonymous) in
3177 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. You also might want to
3178 check out the file Documentation/networking/ax25.txt. More
3179 information about digital amateur radio in general is on the WWW at
3180 http://www.tapr.org/tapr/html/pkthome.html (to browse the WWW, you
3181 need to have access to a machine on the Internet that has a program
3182 like lynx or netscape).
3184 This driver is also available as a module ( = code which can be
3185 inserted in and removed from the running kernel whenever you want).
3186 The module will be called rose.o. If you want to compile it as a
3187 module, say M here and read Documentation/modules.txt.
3189 Serial port KISS driver for AX.25
3191 KISS is a protocol used for the exchange of data between a computer
3192 and a Terminal Node Controller (a small embedded system commonly
3193 used for networking over AX.25 amateur radio connections; it
3194 connects the computer's serial port with the radio's microphone
3195 input and speaker output).
3197 Although KISS is less advanced than the 6pack protocol, it has
3198 the advantage that it is already supported by most modern TNCs
3199 without the need for a firmware upgrade.
3201 If you want to compile this driver as a module ( = code which can be
3202 inserted in and removed from the running kernel whenever you want),
3203 say M here and read Documentation/modules.txt. The module will be
3206 Serial port 6PACK driver for AX.25
3208 6pack is a transmission protocol for the data exchange between your
3209 PC and your TNC (the Terminal Node Controller acts as a kind of
3210 modem connecting your computer's serial port to your radio's
3211 microphone input and speaker output). This protocol can be used as
3212 an alternative to KISS for networking over AX.25 amateur radio
3213 connections, but it has some extended functionality.
3215 Note that this driver is still experimental and might cause
3216 problems. For details about the features and the usage of the
3217 driver, read Documentation/networking/6pack.txt.
3219 If you want to compile this driver as a module ( = code which can be
3220 inserted in and removed from the running kernel whenever you want),
3221 say M here and read Documentation/modules.txt. The module will be
3226 AX.25 is the protocol used for computer communication over amateur
3227 radio. If you say Y here, you will be able to send and receive AX.25
3228 traffic over Ethernet (also called "BPQ AX.25"), which could be
3229 useful if some other computer on your local network has a direct
3230 amateur radio connection.
3232 High-speed (DMA) SCC driver for AX.25
3234 This is a driver for high-speed SCC boards, i.e. those supporting
3235 DMA on one port. You usually use those boards to connect your
3236 computer to an amateur radio modem (such as the WA4DSY 56kbps
3237 modem), in order to send and receive AX.25 packet radio network
3240 Currently, this driver supports Ottawa PI/PI2
3241 (http://hydra.carleton.ca/info/pi2.html) and Gracilis PackeTwin
3242 (http://www.paccomm.com/gracilis.html) boards. They are detected
3243 automatically. If you have one of these cards, say Y here and read
3244 the AX25-HOWTO, available via FTP (user: anonymous) in
3245 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/.
3247 This driver can operate multiple boards simultaneously. If you
3248 compile it as a module (by saying M instead of Y), it will be called
3249 dmascc.o. If you don't pass any parameter to the driver, all
3250 possible I/O addresses are probed. This could irritate other devices
3251 that are currently not in use. You may specify the list of addresses
3252 to be probed by "dmascc=addr1,addr2,..." (when compiled into the
3253 kernel image) or "io=addr1,addr2,..." (when loaded as a module). The
3254 network interfaces will be called dmascc0 and dmascc1 for the board
3255 detected first, dmascc2 and dmascc3 for the second one, and so on.
3257 Before you configure each interface with ifconfig, you MUST set
3258 certain parameters, such as channel access timing, clock mode, and
3259 DMA channel. This is accomplished with a small utility program,
3260 dmascc_cfg, available at
3261 http://www.nt.tuwien.ac.at/~kkudielk/Linux/. (To browse the WWW, you
3262 need to have access to a machine on the Internet that has a program
3263 like lynx or netscape).
3265 Z8530 SCC driver for AX.25
3267 These cards are used to connect your Linux box to an amateur radio
3268 in order to communicate with other computers. If you want to use
3269 this, read Documentation/networking/z8530drv.txt and the
3270 AX25-HOWTO, available via FTP (user: anonymous) at
3271 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Also make sure to say Y
3272 to "Amateur Radio AX.25 Level 2" support.
3274 If you want to compile this as a module ( = code which can be
3275 inserted in and removed from the running kernel whenever you want),
3276 say M here and read Documentation/modules.txt. The module will be
3279 additional delay for PA0HZP OptoSCC compatible boards
3281 Say Y here if you experience problems with the SCC driver not
3282 working properly; please read Documentation/networking/z8530drv.txt
3283 for details. If unsure, say N.
3285 #support for TRX that feedback the tx signal to rx
3288 ### Don't know what's going on here.
3291 YAM driver for AX.25
3293 Support for the YAM modem on serial port. If you want to compile this
3294 as a module ( = code which can be inserted in and removed from the
3295 running kernel whenever you want), say M here and read
3296 Documentation/modules.txt.
3298 BAYCOM picpar and par96 driver for AX.25
3300 This is a driver for Baycom style simple amateur radio modems that
3301 connect to a parallel interface. The driver supports the picpar and
3302 par96 designs. To configure the driver, use the sethdlc utility
3303 available in the standard ax25 utilities package. For information on
3304 the modems, see http://www.baycom.de (to browse the WWW, you need to
3305 have access to a machine on the Internet that has a program like
3306 lynx or netscape) and Documentation/networking/baycom.txt.
3308 If you want to compile this driver as a module ( = code which can be
3309 inserted in and removed from the running kernel whenever you want),
3310 say M here and read Documentation/modules.txt. This is recommended.
3311 The module will be called baycom_par.o.
3313 BAYCOM EPP driver for AX.25
3315 This is a driver for Baycom style simple amateur radio modems that
3316 connect to a parallel interface. The driver supports the EPP
3317 designs. To configure the driver, use the sethdlc utility available
3318 in the standard ax25 utilities package. For information on the
3319 modems, see http://www.baycom.de (to browse the WWW, you need to
3320 have access to a machine on the Internet that has a program like
3321 lynx or netscape) and Documentation/networking/baycom.txt.
3323 If you want to compile this driver as a module ( = code which can be
3324 inserted in and removed from the running kernel whenever you want),
3325 say M here and read Documentation/modules.txt. This is recommended.
3326 The module will be called baycom_par.o.
3328 BAYCOM ser12 full duplex driver for AX.25
3329 CONFIG_BAYCOM_SER_FDX
3330 This is one of two drivers for Baycom style simple amateur radio
3331 modems that connect to a serial interface. The driver supports the
3332 ser12 design in full duplex mode. In addition, it allows the
3333 baudrate to be set between 300 and 4800 baud (however not all modems
3334 support all baudrates). This is the preferred driver. The next
3335 driver, "BAYCOM ser12 half duplex driver for AX.25" is the old
3336 driver and still provided in case this driver does not work with
3337 your serial interface chip. To configure the driver, use the sethdlc
3338 utility available in the standard ax25 utilities package. For
3339 information on the modems, see http://www.baycom.de (to browse the
3340 WWW, you need to have access to a machine on the Internet that has a
3341 program like lynx or netscape) and
3342 Documentation/networking/baycom.txt.
3344 If you want to compile this driver as a module ( = code which can be
3345 inserted in and removed from the running kernel whenever you want),
3346 say M here and read Documentation/modules.txt. This is recommended.
3347 The module will be called baycom_ser_fdx.o.
3349 BAYCOM ser12 half duplex driver for AX.25
3350 CONFIG_BAYCOM_SER_HDX
3351 This is one of two drivers for Baycom style simple amateur radio
3352 modems that connect to a serial interface. The driver supports the
3353 ser12 design in full duplex mode. This is the old driver. It is
3354 still provided in case your serial interface chip does not work with
3355 the full duplex driver. This driver is depreciated. To configure
3356 the driver, use the sethdlc utility available in the standard ax25
3357 utilities package. For information on the modems, see
3358 http://www.baycom.de (to browse the WWW, you need to have access to
3359 a machine on the Internet that has a program like lynx or netscape)
3360 and Documentation/networking/baycom.txt.
3362 If you want to compile this driver as a module ( = code which can be
3363 inserted in and removed from the running kernel whenever you want),
3364 say M here and read Documentation/modules.txt. This is recommended.
3365 The module will be called baycom_ser_hdx.o.
3367 Sound card modem driver for AX.25
3369 This experimental driver allows a standard Sound Blaster or
3370 WindowsSoundSystem compatible sound card to be used as a packet
3371 radio modem (NOT as a telephone modem!), to send digital traffic
3374 To configure the driver, use the sethdlc, smdiag and smmixer
3375 utilities available in the standard ax25 utilities package. For
3376 information on how to key the transmitter, see
3377 http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html (to browse
3378 the WWW, you need to have access to a machine on the Internet that
3379 has a program like lynx or netscape) and
3380 Documentation/networking/soundmodem.txt.
3382 If you want to compile this driver as a module ( = code which can be
3383 inserted in and removed from the running kernel whenever you want),
3384 say M here and read Documentation/modules.txt. This is recommended.
3385 The module will be called soundmodem.o.
3387 Sound card modem support for Sound Blaster and compatible cards
3388 CONFIG_SOUNDMODEM_SBC
3389 This option enables the soundmodem driver to use Sound Blaster and
3390 compatible cards. If you have a dual mode card (i.e. a WSS cards
3391 with a Sound Blaster emulation) you should say N here and Y to
3392 "Sound card modem support for WSS and Crystal cards", below, because
3393 this usually results in better performance. This option also
3394 supports SB16/32/64 in full duplex mode.
3396 Sound card modem support for WSS and Crystal cards
3397 CONFIG_SOUNDMODEM_WSS
3398 This option enables the soundmodem driver to use WindowsSoundSystem
3399 compatible cards. These cards feature a codec chip from either
3400 Analog Devices (such as AD1848, AD1845, AD1812) or Crystal
3401 Semiconductors (such as CS4248, CS423x). This option also supports
3402 the WSS full duplex operation which currently works with Crystal
3403 CS423x chips. If you don't need full duplex operation, do not enable
3404 it to save performance.
3406 Sound card modem support for 1200 baud AFSK modulation
3407 CONFIG_SOUNDMODEM_AFSK1200
3408 This option enables the soundmodem driver 1200 baud AFSK modem,
3409 compatible to popular modems using TCM3105 or AM7911. The
3410 demodulator requires about 12% of the CPU power of a Pentium 75 CPU
3413 Sound card modem support for 2400 baud AFSK modulation (7.3728MHz crystal)
3414 CONFIG_SOUNDMODEM_AFSK2400_7
3415 This option enables the soundmodem driver 2400 baud AFSK modem,
3416 compatible to TCM3105 modems (over-)clocked with a 7.3728MHz
3417 crystal. Note that the availability of this driver does _not_ imply
3418 that I recommend building such links. It is only here since users
3419 especially in eastern Europe have asked me to do so. In fact this
3420 modulation scheme has many disadvantages, mainly its incompatibility
3421 with many transceiver designs and the fact that the TCM3105 (if
3422 used) is operated widely outside its specifications.
3424 Sound card modem support for 2400 baud AFSK modulation (8MHz crystal)
3425 CONFIG_SOUNDMODEM_AFSK2400_8
3426 This option enables the soundmodem driver 2400 baud AFSK modem,
3427 compatible to TCM3105 modems (over-)clocked with an 8MHz crystal.
3428 Note that the availability of this driver does _not_ imply that I
3429 recommend building such links. It is only here since users
3430 especially in eastern Europe have asked me to do so. In fact this
3431 modulation scheme has many disadvantages, mainly its incompatibility
3432 with many transceiver designs and the fact that the TCM3105 (if
3433 used) is operated widely outside its specifications.
3435 Sound card modem support for 2666 baud AFSK modulation
3436 CONFIG_SOUNDMODEM_AFSK2666
3437 This option enables the soundmodem driver 2666 baud AFSK modem.
3438 This modem is experimental, and not compatible to anything
3441 Sound card modem support for 4800 baud 8PSK modulation
3442 CONFIG_SOUNDMODEM_PSK4800
3443 This option enables the soundmodem driver 4800 baud 8PSK modem.
3444 This modem is experimental, and not compatible to anything
3447 Sound card modem support for 4800 baud HAPN-1 modulation
3448 CONFIG_SOUNDMODEM_HAPN4800
3449 This option enables the soundmodem driver 4800 baud HAPN-1
3450 compatible modem. This modulation seems to be widely used 'down
3451 under' and in the Netherlands. Here, nobody uses it, so I could not
3452 test if it works. It is compatible to itself, however :-)
3454 Sound card modem support for 9600 baud FSK G3RUH modulation
3455 CONFIG_SOUNDMODEM_FSK9600
3456 This option enables the soundmodem driver 9600 baud FSK modem,
3457 compatible to the G3RUH standard. The demodulator requires about 4%
3458 of the CPU power of a Pentium 75 CPU per channel. You can say Y to
3459 both 1200 baud AFSK and 9600 baud FSK if you want (but obviously you
3460 can only use one protocol at a time, depending on what the other end
3463 CCITT X.25 Packet Layer
3465 X.25 is a set of standardized network protocols, similar in scope to
3466 frame relay; the one physical line from your box to the X.25 network
3467 entry point can carry several logical point-to-point connections
3468 (called "virtual circuits") to other computers connected to the X.25
3469 network. Governments, banks, and other organizations tend to use it
3470 to connect to each other or to form Wide Area Networks (WANs). Many
3471 countries have public X.25 networks. X.25 consists of two
3472 protocols: the higher level Packet Layer Protocol (PLP) (say Y here
3473 if you want that) and the lower level data link layer protocol LAPB
3474 (say Y to "LAPB Data Link Driver" below if you want that).
3476 You can read more about X.25 at http://www.sangoma.com/x25.html and
3477 http://www.cisco.com/univercd/data/doc/software/11_0/rpcg/cx25.htm
3478 (to browse the WWW, you need to have access to a machine on the
3479 Internet that has a program like lynx or netscape). Information
3480 about X.25 for Linux is contained in the files
3481 Documentation/networking/x25.txt and
3482 Documentation/networking/x25-iface.txt.
3484 One connects to an X.25 network either with a dedicated network card
3485 using the X.21 protocol (not yet supported by Linux) or one can do
3486 X.25 over a standard telephone line using an ordinary modem (say Y
3487 to "X.25 async driver" below) or over Ethernet using an ordinary
3488 Ethernet card and either the 802.2 LLC protocol (say Y to "802.2
3489 LLC" below) or LAPB over Ethernet (say Y to "LAPB Data Link Driver"
3490 and "LAPB over Ethernet driver" below).
3492 If you want to compile this driver as a module ( = code which can be
3493 inserted in and removed from the running kernel whenever you want),
3494 say M here and read Documentation/modules.txt. The module will be
3495 called x25.o. If unsure, say N.
3497 LAPB Data Link Driver (EXPERIMENTAL)
3499 Link Access Procedure, Balanced (LAPB) is the data link layer (i.e.
3500 the lower) part of the X.25 protocol. It offers a reliable
3501 connection service to exchange data frames with one other host, and
3502 it is used to transport higher level protocols (mostly X.25 Packet
3503 Layer, the higher part of X.25, but others are possible as well).
3504 Usually, LAPB is used with specialized X.21 network cards, but Linux
3505 currently supports LAPB only over Ethernet connections. If you want
3506 to use LAPB connections over Ethernet, say Y here and to "LAPB over
3507 Ethernet driver" below. Read
3508 Documentation/networking/lapb-module.txt for technical details.
3510 If you want to compile this driver as a module though ( = code which
3511 can be inserted in and removed from the running kernel whenever you
3512 want), say M here and read Documentation/modules.txt. The module
3513 will be called lapb.o. If unsure, say N.
3515 802.2 LLC (VERY EXPERIMENTAL)
3517 This is a Logical Link Layer protocol used for X.25 connections over
3518 Ethernet, using ordinary Ethernet cards.
3520 Bridging (EXPERIMENTAL)
3522 If you say Y here, then your Linux box will be able to act as an
3523 Ethernet bridge, which means that the different Ethernet segments it
3524 is connected to will appear as one Ethernet to the participants.
3525 Several such bridges can work together to create even larger
3526 networks of Ethernets using the IEEE802.1 spanning tree algorithm.
3527 As this is a standard, Linux bridges will interwork properly with
3528 other third party bridge products.
3530 In order to use this, you'll need the bridge configuration tools
3531 available via FTP (user: anonymous) from
3532 ftp://shadow.cabi.net/pub/Linux. Please read the Bridge mini-HOWTO
3533 for more information. Note that if your box acts as a bridge, it
3534 probably contains several Ethernet devices, but the kernel is not
3535 able to recognize more than one at boot time without help; for
3536 details read the Ethernet-HOWTO, available via FTP (user: anonymous)
3537 in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. The Bridging code is
3538 still in test. If unsure, say N.
3542 The Packet protocol is used by applications which communicate
3543 directly with network devices without an intermediate network
3544 protocol implemented in the kernel, e.g. tcpdump. If you want them
3545 to work, choose Y. This driver is also available as a module called
3546 af_packet.o ( = code which can be inserted in and removed from the
3547 running kernel whenever you want). If you want to compile it as a
3548 module, say M here and read Documentation/modules.txt. If unsure,
3551 Kernel/User network link driver
3553 This driver allows for two-way communication between certain parts
3554 of the kernel or modules and user processes; the user processes are
3555 able to read from and write to character special files in the /dev
3556 directory having major mode 36. So far, the kernel uses it to
3557 publish some network related information if you say Y to "Routing
3558 messages", below. You also need to say Y here if you want to use
3559 arpd, a daemon that helps keep the internal ARP cache (a mapping
3560 between IP addresses and hardware addresses on the local network)
3561 small. The ethertap device, which lets user space programs read and
3562 write raw Ethernet frames, also needs the network link driver. If
3567 If you say Y here and create a character special file /dev/route
3568 with major number 36 and minor number 0 using mknod ("man mknod"),
3569 you (or some user space utility) can read some network related
3570 routing information from that file. Everything you write to that
3571 file will be discarded.
3573 Netlink device emulation
3575 This is a backward compatibility option, choose Y for now.
3576 This option will be removed soon.
3578 Asynchronous Transfer Mode (ATM)
3580 Kernel support for ATM. Note that you need a set of user-space programs
3581 to actually make use of ATM. See Documentation/atm.txt for further
3584 Classical IP over ATM
3586 Classical IP over ATM for PVCs and SVCs, supporting InARP and ATMARP.
3587 Typically you will either use LAN Emulation (LANE) or Classical IP to
3588 communicate with other IP hosts on your ATM network.
3590 Do NOT send ICMP if no neighbour
3591 CONFIG_ATM_CLIP_NO_ICMP
3592 Normally, an ICMP host unreachable message is sent if a neighbour cannot
3593 be reached because there is no VC to it in the kernel's ATMARP table.
3594 This may cause problems when ATMARP table entries are briefly removed
3595 during revalidation. If this configuration option is set to "yes",
3596 packets to such neighbours are silently discarded instead.
3598 LAN Emulation (LANE) support
3600 LAN Emulation emulates services of existing LANs across an ATM network.
3601 Besides operating as a normal ATM end station client, Linux LANE client
3602 can also act as an proxy client bridging packets between ELAN and
3603 Ethernet segments. You need LANE if you want to try MPOA.
3605 Multi-Protocol Over ATM (MPOA) support
3607 Multi-Protocol Over ATM allows ATM edge devices such as routers,
3608 bridges and ATM attached hosts establish direct ATM VCs across
3609 subnetwork boundaries. These shortcut connections bypass routers
3610 enhancing overall network performance.
3614 ATM over TCP driver. Useful mainly for development and for experiments.
3616 Efficient Networks ENI155P
3618 Driver for the Efficient Networks ENI155p series and SMC ATM Power155
3619 155 Mbps ATM adapters. Both, the versions with 512kB and 2MB on-board
3620 RAM (Efficient calls them "C" and "S", respectively), and the FPGA and
3621 the ASIC Tonga versions of the board are supported. The driver works
3622 with MMF (-MF or ...F) and UTP-5 (-U5 or ...D) adapters.
3624 Enable extended debugging
3625 CONFIG_ATM_ENI_DEBUG
3626 Extended debugging records various events and displays that list when
3627 an inconsistency is detected. This mechanism is faster than generally
3628 using printks, but still has some impact on performance. Note that
3629 extended debugging may create certain race conditions itself. Enable
3630 this ONLY if you suspect problems with the driver.
3632 Fine-tune burst settings
3633 CONFIG_ATM_ENI_TUNE_BURST
3634 In order to obtain good throughput, the ENI NIC can transfer multiple
3635 words of data per PCI bus access cycle. Such a multi-word transfer is
3638 The default settings for the burst sizes are suitable for most PCI
3639 chipsets. However, in some cases, large bursts may overrun buffers in
3640 the PCI chipset and cause data corruption. In such cases, large bursts
3641 must be disabled and only (slower) small bursts can be used. The burst
3642 sizes can be set independently in the send (TX) and receive (RX)
3645 Note that enabling many different burst sizes in the same direction
3646 may increase the cost of setting up a transfer such that the resulting
3647 throughput is lower than when using only the largest available burst
3650 Also, sometimes larger bursts lead to lower throughput, e.g. on an
3651 Intel 440FX board, a drop from 135 Mbps to 103 Mbps was observed when
3652 going from 8W to 16W bursts.
3654 Enable 16W TX bursts (discouraged)
3655 CONFIG_ATM_ENI_BURST_TX_16W
3656 Burst sixteed words at once in the send direction. This may work with
3657 recent PCI chipsets, but is known to fail with older chipsets.
3659 Enable 8W TX bursts (recommended)
3660 CONFIG_ATM_ENI_BURST_TX_8W
3661 Burst eight words at once in the send direction. This is the default
3664 Enable 4W TX bursts (optional)
3665 CONFIG_ATM_ENI_BURST_TX_4W
3666 Burst four words at once in the send direction. You may want to try this
3667 if you have disabled 8W bursts. Enabling 4W if 8W is also set may or may
3668 not improve throughput.
3670 Enable 2W TX bursts (optional)
3671 CONFIG_ATM_ENI_BURST_TX_2W
3672 Burst two words at once in the send direction. You may want to try this
3673 if you have disabled 4W and 8W bursts. Enabling 2W if 4W or 8W are also
3674 set may or may not improve throughput.
3676 Enable 16W RX bursts (discouraged)
3677 CONFIG_ATM_ENI_BURST_RX_16W
3678 Burst sixteen words at once in the receive direction. This may work with
3679 recent PCI chipsets, but is known to fail with older chipsets.
3681 Enable 8W RX bursts (discouraged)
3682 CONFIG_ATM_ENI_BURST_RX_8W
3683 Burst eight words at once in the receive direction. This may work with
3684 recent PCI chipsets, but is known to fail with older chipsets, such as
3685 the Intel Neptune series.
3687 Enable 4W RX bursts (recommended)
3688 CONFIG_ATM_ENI_BURST_RX_4W
3689 Burst four words at once in the receive direction. This is the default
3690 setting. Enabling 4W if 8W is also set may or may not improve throughput.
3692 Enable 2W RX bursts (optional)
3693 CONFIG_ATM_ENI_BURST_RX_2W
3694 Burst two words at once in the receive direction. You may want to try
3695 this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or 8W are
3696 also set may or may not improve throughput.
3698 ZeitNet ZN1221/ZN1225
3700 Driver for the ZeitNet ZN1221 (MMF) and ZN1225 (UTP-5) 155 Mbps ATM
3703 Enable extended debugging
3704 CONFIG_ATM_ZATM_DEBUG
3705 Extended debugging records various events and displays that list when
3706 an inconsistency is detected. This mechanism is faster than generally
3707 using printks, but still has some impact on performance. Note that
3708 extended debugging may create certain race conditions itself. Enable
3709 this ONLY if you suspect problems with the driver.
3711 Enable usec resolution timestamps
3712 CONFIG_ATM_ZATM_EXACT_TS
3713 The uPD98401 SAR chip supports a high-resolution timer (approx. 30 MHz)
3714 that is used for very accurate reception timestamps. Because that timer
3715 overflows after 140 seconds, and also to avoid timer drift, time
3716 measurements need to be periodically synchronized with the normal
3717 system time. Enabling this feature will add some general overhead for
3718 timer synchronization and also per-packet overhead for time conversion.
3722 The NICStAR chipset family is used in a large number of ATM NICs for
3723 25 and for 155 Mbps, including IDT cards and the Fore ForeRunnerLE
3726 Madge Ambassador (Collage PCI 155 Server)
3727 CONFIG_ATM_AMBASSADOR
3728 This is a driver for ATMizer based ATM card produced by Madge
3729 Networks Ltd. Say Y (or M to compile as a module named ambassador.o)
3730 here if you have one of these cards.
3732 Enable debugging messages
3733 CONFIG_ATM_AMBASSADOR_DEBUG
3734 Somewhat useful debugging messages are available. The choice of
3735 messages is controlled by a bitmap. This may be specified as a
3736 module argument (kernel command line argument as well?), changed
3737 dynamically using an ioctl (not yet) or changed by sending the
3738 string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
3739 drivers/atm/ambassador.h for the meanings of the bits in the mask.
3741 When active, these messages can have a significant impact on the
3742 speed of the driver, and the size of your syslog files! When
3743 inactive, they will have only a modest impact on performance.
3745 Madge Horizon [Ultra] (Collage PCI 25 and Collage PCI 155 Client)
3747 This is a driver for the Horizon chipset ATM adapter cards once
3748 produced by Madge Networks Ltd. Say Y (or M to compile as a module
3749 named horizon.o) here if you have one of these cards.
3751 Enable debugging messages
3752 CONFIG_ATM_HORIZON_DEBUG
3753 Somewhat useful debugging messages are available. The choice of
3754 messages is controlled by a bitmap. This may be specified as a
3755 module argument (kernel command line argument as well?), changed
3756 dynamically using an ioctl (not yet) or changed by sending the
3757 string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
3758 drivers/atm/horizon.h for the meanings of the bits in the mask.
3760 When active, these messages can have a significant impact on the
3761 speed of the driver, and the size of your syslog files! When
3762 inactive, they will have only a modest impact on performance.
3766 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CDROM or
3767 any other SCSI device under Linux, say Y and make sure that you know
3768 the name of your SCSI host adapter (the card inside your computer
3769 that "speaks" the SCSI protocol, also called SCSI controller),
3770 because you will be asked for it.
3772 You also need to say Y here if you want support for the parallel
3773 port version of the 100 MB IOMEGA ZIP drive.
3775 Please read the SCSI-HOWTO, available via FTP (user: anonymous) in
3776 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. The
3777 SCSI-Programming-HOWTO contains information about how to add or
3778 remove an SCSI device from a running Linux machine without
3781 This driver is also available as a module ( = code which can be
3782 inserted in and removed from the running kernel whenever you want).
3783 The module will be called scsi_mod.o. If you want to compile it as a
3784 module, say M here and read Documentation/modules.txt and
3785 Documentation/scsi.txt. However, do not compile this as a module if
3786 your root filesystem (the one containing the directory /) is located
3791 If you want to use a SCSI hard disk or the SCSI or parallel port
3792 version of the IOMEGA ZIP drive under Linux, say Y and read the
3793 SCSI-HOWTO, the Disk-HOWTO and the Multi-Disk-HOWTO, available via
3794 FTP (user: anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
3795 This is NOT for SCSI CDROMs.
3797 This driver is also available as a module ( = code which can be
3798 inserted in and removed from the running kernel whenever you want).
3799 The module will be called sd_mod.o. If you want to compile it as a
3800 module, say M here and read Documentation/modules.txt and
3801 Documentation/scsi.txt. Do not compile this driver as a module if
3802 your root filesystem (the one containing the directory /) is located
3803 on a SCSI disk. In this case, do not compile the driver for your
3804 SCSI host adapter (below) as a module either.
3808 If you want to use a SCSI tape drive under Linux, say Y and read the
3809 SCSI-HOWTO, available via FTP (user: anonymous) in
3810 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO and
3811 drivers/scsi/README.st in the kernel source. This is NOT for SCSI
3814 This driver is also available as a module ( = code which can be
3815 inserted in and removed from the running kernel whenever you want).
3816 The module will be called st.o. If you want to compile it as a
3817 module, say M here and read Documentation/modules.txt and
3818 Documentation/scsi.txt .
3822 If you want to use a SCSI CDROM under Linux, say Y and read the
3823 SCSI-HOWTO and the CDROM-HOWTO from
3824 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Also make sure to say Y
3825 or M to "ISO 9660 CDROM filesystem support" later.
3827 This driver is also available as a module ( = code which can be
3828 inserted in and removed from the running kernel whenever you want).
3829 The module will be called sr_mod.o. If you want to compile it as a
3830 module, say M here and read Documentation/modules.txt and
3831 Documentation/scsi.txt .
3833 Enable vendor-specific extensions (for SCSI CDROM)
3834 CONFIG_BLK_DEV_SR_VENDOR
3835 This enables the usage of vendor specific SCSI commands. This is
3836 required to support multisession CDs with old NEC/TOSHIBA cdrom
3837 drives (and HP Writers). If you have such a drive and get the first
3838 session only, try saying Y here; everybody else says N.
3840 SCSI generic support
3842 If you want to use SCSI scanners, synthesizers or CD-writers or just
3843 about anything having "SCSI" in its name other than hard disks,
3844 CDROMs or tapes, say Y here. These won't be supported by the kernel
3845 directly, so you need some additional software which knows how to
3846 talk to these devices using the SCSI protocol. For CD-writers, you
3847 would need the program cdwrite, available via FTP (user: anonymous)
3848 from ftp://metalab.unc.edu/pub/Linux/utils/disk-management; for
3849 other devices, it's possible that you'll have to write the driver
3850 software yourself, so have a look at the SCSI-HOWTO and at the
3851 SCSI-Programming-HOWTO, both available via FTP (user: anonymous) in
3852 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Please read the file
3853 Documentation/scsi-generic.txt for more information.
3855 If you want to compile this as a module ( = code which can be
3856 inserted in and removed from the running kernel whenever you want),
3857 say M here and read Documentation/modules.txt and
3858 Documentation/scsi.txt. The module will be called sg.o. If unsure,
3861 Probe all LUNs on each SCSI device
3862 CONFIG_SCSI_MULTI_LUN
3863 If you have a SCSI device that supports more than one LUN (Logical
3864 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
3865 can say Y here to force the SCSI driver to probe for multiple LUNs.
3866 A SCSI device with multiple LUNs acts logically like multiple SCSI
3867 devices. The vast majority of SCSI devices have only one LUN, and
3868 so most people can say N here and should in fact do so, because it
3871 Verbose SCSI error reporting (kernel size +=12K)
3872 CONFIG_SCSI_CONSTANTS
3873 The error messages regarding your SCSI hardware will be easier to
3874 understand if you say Y here; it will enlarge your kernel by about
3875 12 KB. If in doubt, say Y.
3877 SCSI logging facility
3879 This turns on a logging facility that can be used to debug a number
3880 of SCSI related problems.
3882 If you say Y here, no logging output will appear by default, but you
3883 can enable logging by saying Y to "/proc filesystem support" and
3884 "Sysctl support" below and executing the command
3886 echo "scsi log token [level]" > /proc/scsi/scsi
3888 at boot time after the /proc filesystem has been mounted.
3890 There are a number of things that can be used for 'token' (you can
3891 find them in the source: drivers/scsi/scsi.c), and this allows you
3892 to select the types of information you want, and the level allows
3893 you to select the level of verbosity.
3895 If you say N here, it may be harder to track down some types of SCSI
3896 problems. If you say Y here your kernel will be somewhat larger, but
3897 there should be no noticeable performance impact as long as you have
3900 AdvanSys SCSI support
3901 CONFIG_SCSI_ADVANSYS
3902 This is a driver for all SCSI host adapters manufactured by
3903 AdvanSys. It is documented in the kernel source in
3904 drivers/scsi/advansys.c.
3906 This driver is also available as a module ( = code which can be
3907 inserted in and removed from the running kernel whenever you want).
3908 If you want to compile it as a module, say M here and read
3909 Documentation/modules.txt. The module will be called advansys.o.
3911 Adaptec AHA152X/2825 support
3913 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
3914 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
3915 must be manually specified in this case.
3917 It is explained in section 3.3 of the SCSI-HOWTO, available via FTP
3918 (user: anonymous) at ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. You
3919 might also want to read the comments at the top of
3920 drivers/scsi/aha152x.c.
3922 This driver is also available as a module ( = code which can be
3923 inserted in and removed from the running kernel whenever you want).
3924 The module will be called aha152x.o. If you want to compile it as a
3925 module, say M here and read Documentation/modules.txt.
3927 Adaptec AHA1542 support
3929 This is support for a SCSI host adapter. It is explained in section
3930 3.4 of the SCSI-HOWTO, available via FTP (user: anonymous) at
3931 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Note that Trantor was
3932 recently purchased by Adaptec, and some former Trantor products are
3933 being sold under the Adaptec name. If it doesn't work out of the
3934 box, you may have to change some settings in drivers/scsi/aha1542.h.
3936 If you want to compile this as a module ( = code which can be
3937 inserted in and removed from the running kernel whenever you want),
3938 say M here and read Documentation/modules.txt. The module will be
3941 Adaptec AHA1740 support
3943 This is support for a SCSI host adapter. It is explained in section
3944 3.5 of the SCSI-HOWTO, available via FTP (user: anonymous) at
3945 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work out
3946 of the box, you may have to change some settings in
3947 drivers/scsi/aha1740.h.
3949 This driver is also available as a module ( = code which can be
3950 inserted in and removed from the running kernel whenever you want).
3951 The module will be called aha1740.o. If you want to compile it as a
3952 module, say M here and read Documentation/modules.txt.
3954 Adaptec AIC7xxx chipset SCSI controller support
3956 This is support for the various aic7xxx based Adaptec SCSI
3957 controllers. These include the 274x EISA cards; 284x VLB cards;
3958 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
3959 motherboard based SCSI controllers from Adaptec. It does not support
3960 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
3961 support them. It does not support the 2920 cards from Adaptec that
3962 use the Future Domain SCSI controller chip. For those cards, you
3963 need the "Future Domain 16xx SCSI support" driver.
3965 In general, if the controller is based on an Adaptec SCSI controller
3966 chip from the aic777x series or the aic78xx series, this driver
3967 should work. The only exception is the 7810 which is specifically
3968 not supported (that's the RAID controller chip on the AAA-13x
3971 Note that the AHA2920 SCSI host adapter is *not* supported by this
3972 driver; choose "Future Domain 16xx SCSI support" instead if you have
3975 Information on the configuration options for this controller can be
3976 found by checking the help file for each of the available
3977 configuration options. You should read drivers/scsi/README.aic7xxx
3978 at a minimum before contacting the maintainer with any questions.
3979 The SCSI-HOWTO, available via FTP (user: anonymous) at
3980 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO can also be of great
3983 If you want to compile this driver as a module ( = code which can be
3984 inserted in and removed from the running kernel whenever you want),
3985 say M here and read Documentation/modules.txt. The module will be
3988 Enable or Disable Tagged Command Queueing by default
3989 CONFIG_AIC7XXX_TCQ_ON_BY_DEFAULT
3990 This option causes the aic7xxx driver to attempt to use tagged command
3991 queueing on any devices that claim to support it. If this is set to yes,
3992 you can still turn off TCQ on troublesome devices with the use of the
3993 tag_info boot parameter. See /usr/src/linux/drivers/scsi/README.aic7xxx
3994 for more information on that and other aic7xxx setup commands. If this
3995 option is turned off, you may still enable TCQ on known good devices by
3996 use of the tag_info boot parameter.
3998 If you are unsure about your devices then it is safest to say N here.
4000 However, TCQ can increase performance on some hard drives by as much
4001 as 50% or more, so I would recommend that if you say N here, that you
4002 at least read the README.aic7xxx file so you will know how to enable
4003 this option manually should your drives prove to be safe in regards
4006 Conversely, certain drives are known to lock up or cause bus resets when
4007 TCQ is enabled on them. If you have a Western Digital Enterprise SCSI
4008 drive for instance, then don't even bother to enable TCQ on it as the
4009 drive will become unreliable, and it will actually reduce performance.
4011 Default number of TCQ commands per device
4012 CONFIG_AIC7XXX_CMDS_PER_DEVICE
4013 Specify the number of commands you would like to allocate per SCSI
4014 device when Tagged Command Queueing (TCQ) is enabled on that device.
4016 Reasonable figures are in the range of 8 to 24 commands per device,
4017 but depending on hardware could be increased or decreased from that
4018 figure. If the number is too high for any particular device, the
4019 driver will automatically compensate usually after only 10 minutes
4020 of uptime. It will not hinder performance if some of your devices
4021 eventually have their command depth reduced, but is a waste of memory
4022 if all of your devices end up reducing this number down to a more
4025 NOTE: Certain very broken drives are known to lock up when given more
4026 commands than they like to deal with. Quantum Fireball drives are the
4027 most common in this category. For the Quantum Fireball drives I would
4028 suggest no more than 8 commands per device.
4032 Collect statistics to report in /proc
4033 CONFIG_AIC7XXX_PROC_STATS
4034 This option tells the driver to keep track of how many commands have
4035 been sent to each particular device and report that information to
4036 the user via the /proc/scsi/aic7xxx/n file, where n is the number of
4037 the aic7xxx controller you want the information on. This adds a
4038 small amount of overhead to each and every SCSI command the aic7xxx
4039 driver handles, so if you aren't really interested in this
4040 information, it is best to leave it disabled. This will only work if
4041 you also say Y to "/proc filesystem support", below.
4045 Delay in seconds after SCSI bus reset
4046 CONFIG_AIC7XXX_RESET_DELAY
4047 This sets how long the driver will wait after resetting the SCSI bus
4048 before attempting to communicate with the devices on the SCSI bus
4049 again. This delay will be used during the reset phase at bootup time
4050 as well as after any reset that might occur during normal operation.
4051 Reasonable numbers range anywhere from 5 to 15 seconds depending on
4052 your devices. DAT tape drives are notorious for needing more time
4053 after a bus reset to be ready for the next command, but most hard
4054 drives and CD-ROM devices are ready in only a few seconds. This
4055 option has a maximum upper limit of 20 seconds to avoid bad
4056 interactions between the aic7xxx driver and the rest of the linux
4057 kernel. The default value has been reduced to 5 seconds. If this
4058 doesn't work with your hardware, try increasing this value.
4060 IBM ServeRAID Support
4062 This is support for the IBM ServeRAID hardware RAID controllers.
4063 Consult the SCSI-HOWTO, available via anonymous FTP from
4064 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO, and the file
4065 README.ips in drivers/scsi for more information. If this driver
4066 does not work correctly without modification please contact the
4067 author by email at ipslinux@us.ibm.com.
4069 BusLogic SCSI support
4070 CONFIG_SCSI_BUSLOGIC
4071 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
4072 Adapters. Consult the SCSI-HOWTO, available via anonymous FTP from
4073 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO, and the files
4074 README.BusLogic and README.FlashPoint in drivers/scsi for more
4075 information. If this driver does not work correctly without
4076 modification, please contact the author, Leonard N. Zubkoff, by
4077 email to lnz@dandelion.com.
4079 You can also build this driver as a module ( = code which can be
4080 inserted in and removed from the running kernel whenever you want),
4081 but only a single instance may be loaded. If you want to compile it
4082 as a module, say M here and read Documentation/modules.txt. The
4083 module will be called BusLogic.o.
4085 Omit BusLogic SCSI FlashPoint support
4086 CONFIG_SCSI_OMIT_FLASHPOINT
4087 This option allows you to omit the FlashPoint support from the
4088 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
4089 substantial, so users of MultiMaster Host Adapters may wish to omit
4092 DTC3180/3280 SCSI support
4094 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
4095 the SCSI-HOWTO, available via FTP (user: anonymous) at
4096 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO and the file
4097 drivers/scsi/README.dtc3x80.
4099 This driver is also available as a module ( = code which can be
4100 inserted in and removed from the running kernel whenever you want).
4101 The module will be called dtc.o. If you want to compile it as a
4102 module, say M here and read Documentation/modules.txt.
4104 EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti, Alphatronix) support
4105 CONFIG_SCSI_EATA_DMA
4106 This is support for the EATA-DMA protocol compliant SCSI Host
4107 Adapters like the SmartCache III/IV, SmartRAID controller families
4108 and the DPT PM2011B and PM2012B controllers.
4110 Note that this driver is obsolete; if you have one of the above SCSI
4111 Host Adapters, you should normally say N here and Y to "EATA
4112 ISA/EISA/PCI support", below. Please read the SCSI-HOWTO, available
4113 via FTP (user: anonymous) at
4114 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4116 This driver is also available as a module ( = code which can be
4117 inserted in and removed from the running kernel whenever you want).
4118 The module will be called eata_dma.o. If you want to compile it as a
4119 module, say M here and read Documentation/modules.txt.
4121 EATA-PIO (old DPT PM2001, PM2012A) support
4122 CONFIG_SCSI_EATA_PIO
4123 This driver supports all EATA-PIO protocol compliant SCSI Host
4124 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
4125 host adapters could also use this driver but are discouraged from
4126 doing so, since this driver only supports hard disks and lacks
4127 numerous features. You might want to have a look at the SCSI-HOWTO,
4128 available via FTP (user: anonymous) at
4129 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4131 If you want to compile this as a module ( = code which can be
4132 inserted in and removed from the running kernel whenever you want),
4133 say M here and read Documentation/modules.txt. The module will be
4136 UltraStor 14F/34F support
4138 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
4139 The source at drivers/scsi/u14-34f.c contains some information about
4140 this hardware. If the driver doesn't work out of the box, you may
4141 have to change some settings in drivers/scsi/u14-34f.c. Read the
4142 SCSI-HOWTO, available via FTP (user: anonymous) at
4143 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Note that there is also
4144 another driver for the same hardware: "UltraStor SCSI support",
4145 below. You should say Y to both only if you want 24F support as
4148 This driver is also available as a module ( = code which can be
4149 inserted in and removed from the running kernel whenever you want).
4150 The module will be called u14-34f.o. If you want to compile it as a
4151 module, say M here and read Documentation/modules.txt.
4153 enable elevator sorting
4154 CONFIG_SCSI_U14_34F_LINKED_COMMANDS
4155 This option enables elevator sorting for all probed SCSI disks and
4156 CDROMs. It definitely reduces the average seek distance when doing
4157 random seeks, but this does not necessarily result in a noticeable
4158 performance improvement: your mileage may vary...
4160 The safe answer is N.
4162 maximum number of queued commands
4163 CONFIG_SCSI_U14_34F_MAX_TAGS
4164 This specifies how many SCSI commands can be maximally queued for
4165 each probed SCSI device. You should reduce the default value of 8
4166 only if you have disks with buggy or limited tagged command support.
4167 Minimum is 2 and maximum is 14. This value is also the window size
4168 used by the elevator sorting option above. The effective value used
4169 by the driver for each probed SCSI device is reported at boot time.
4171 Future Domain 16xx SCSI/AHA-2920A support
4172 CONFIG_SCSI_FUTURE_DOMAIN
4173 This is support for Future Domain's 16-bit SCSI host adapters
4174 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
4175 other adapters based on the Future Domain chipsets (Quantum
4176 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
4177 It is explained in section 3.7 of the SCSI-HOWTO, available via FTP
4178 (user: anonymous) at ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4180 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
4181 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
4182 controller support"). This Future Domain driver works with the older
4183 Adaptec AHA-2920A boards with a Future Domain chip on them.
4185 This driver is also available as a module ( = code which can be
4186 inserted in and removed from the running kernel whenever you want).
4187 The module will be called fdomain.o. If you want to compile it as a
4188 module, say M here and read Documentation/modules.txt.
4190 Future Domain MCS-600/700 SCSI support
4192 This is support for Future Domain MCS 600/700 MCA SCSI adapters. Some
4193 PS/2 computers are equipped with IBM Fast SCSI Adapter/A which is
4194 identical to the MCS 700 and hence also supported by this driver.
4195 This driver also supports the Reply SB16/SCSI card (the SCSI part).
4196 It supports multiple adapters in the same system.
4198 Generic NCR5380/53c400 SCSI support
4199 CONFIG_SCSI_GENERIC_NCR5380
4200 This is the generic NCR family of SCSI controllers, not to be
4201 confused with the NCR 53c7 or 8xx controllers. It is explained in
4202 section 3.8 of the SCSI-HOWTO, available via FTP (user: anonymous)
4203 at ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work
4204 out of the box, you may have to change some settings in
4205 drivers/scsi/g_NCR5380.h.
4207 This driver is also available as a module ( = code which can be
4208 inserted in and removed from the running kernel whenever you want).
4209 The module will be called g_NCR5380.o. If you want to compile it as
4210 a module, say M here and read Documentation/modules.txt.
4212 Enable NCR53c400 extensions
4213 CONFIG_SCSI_GENERIC_NCR53C400
4214 This enables certain optimizations for the NCR53c400 SCSI cards. You
4215 might as well try it out. Note that this driver will only probe for
4216 the Trantor T130B in its default configuration; you might have to
4217 pass a command line option to the kernel at boot time if it doesn't
4218 detect your card. See the file drivers/scsi/README.g_NCR5380 for
4221 NCR5380/53c400 mapping method (use Port for T130B)
4222 CONFIG_SCSI_G_NCR5380_PORT
4223 The NCR5380 and NCR53c400 SCSI controllers come in two varieties:
4224 port or memory mapped. You should know what you have. The most
4225 common card, Trantor T130B, uses port mapped mode.
4227 NCR53c7,8xx SCSI support
4228 CONFIG_SCSI_NCR53C7xx
4229 This is a driver for the 53c7 and 8xx NCR family of SCSI
4230 controllers, not to be confused with the NCR 5380 controllers. It is
4231 explained in section 3.8 of the SCSI-HOWTO, available via FTP (user:
4232 anonymous) at ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. If it
4233 doesn't work out of the box, you may have to change some settings in
4234 drivers/scsi/53c7,8xx.h. Please read drivers/scsi/README.ncr53c7xx
4235 for the available boot time command line options.
4237 Note: there is another driver for the 53c8xx family of controllers
4238 ("NCR53C8XX SCSI support" below). If you want to use them both, you
4239 need to say M to both and build them as modules, but only one may be
4240 active at a time. If you have a 53c8xx board, it's better to use the
4243 This driver is also available as a module ( = code which can be
4244 inserted in and removed from the running kernel whenever you want).
4245 The module will be called 53c7,8xx.o. If you want to compile it as a
4246 module, say M here and read Documentation/modules.txt.
4248 always negotiate synchronous transfers
4249 CONFIG_SCSI_NCR53C7xx_sync
4250 In general, this is good; however, it is a bit dangerous since there
4251 are some broken SCSI devices out there. Take your chances. Safe bet
4254 allow FAST-SCSI [10MHz]
4255 CONFIG_SCSI_NCR53C7xx_FAST
4256 This will enable 10MHz FAST-SCSI transfers with your host
4257 adapter. Some systems have problems with that speed, so it's safest
4261 CONFIG_SCSI_NCR53C7xx_DISCONNECT
4262 This enables the disconnect/reconnect feature of the NCR SCSI
4263 controller. When you say Y here, a slow SCSI device will not lock
4264 the SCSI bus while processing a request, allowing simultaneous use
4265 of e.g. a SCSI hard disk and SCSI tape or CD-ROM drive, and
4266 providing much better performance when using slow and fast SCSI
4267 devices at the same time. Some devices, however, do not operate
4268 properly with this option enabled, and will cause your SCSI system
4269 to hang, which might cause a system crash. The safe answer
4270 therefore is to say N.
4272 NCR53C8XX SCSI support
4273 CONFIG_SCSI_NCR53C8XX
4274 This is the BSD ncr driver adapted to Linux for the NCR53C8XX family
4275 of PCI-SCSI controllers. This driver supports parity checking,
4276 tagged command queuing and fast synchronous data transfers up to 80
4277 MB/s with wide FAST-40 LVD devices and controllers.
4279 Recent versions of the 53C8XX chips are better supported by the
4280 option "SYM53C8XX SCSI support", below.
4282 Note: there is yet another driver for the 53c8xx family of controllers
4283 ("NCR53c7,8xx SCSI support" above). If you want to use them both,
4284 you need to say M to both and build them as modules, but only one
4285 may be active at a time. If you have a 53c8xx board, you probably do
4286 not want to use the "NCR53c7,8xx SCSI support".
4288 Please read drivers/scsi/README.ncr53c8xx for more information.
4290 SYM53C8XX SCSI support
4291 CONFIG_SCSI_SYM53C8XX
4292 This driver supports all the features of recent 53C8XX chips (used
4293 in PCI SCSI controllers), notably the hardware phase mismatch
4294 feature of the SYM53C896.
4296 Older versions of the 53C8XX chips are not supported by this
4297 driver. If your system uses either a 810 rev. < 16, a 815, or a 825
4298 rev. < 16 PCI SCSI processor, you must use the generic NCR53C8XX
4299 driver ("NCR53C8XX SCSI support" above) or configure both the
4300 NCR53C8XX and this SYM53C8XX drivers either as module or linked to
4303 When both drivers are linked to the kernel, the SYM53C8XX driver is
4304 called first at initialization and you can use the 'excl=ioaddr'
4305 driver boot option to exclude attachment of adapters by the SYM53C8XX
4306 driver. For instance, entering 'sym53c8xx=excl:0xb400,excl=0xc000' at
4307 lilo prompt prevents adapters at io address 0xb400 and 0xc000 from
4308 being attached by the SYM53C8XX driver, thus allowing the NCR53C8XX
4309 driver to attach them. The 'excl' option is also supported by the
4312 Please read drivers/scsi/README.ncr53c8xx for more information.
4314 synchronous data transfers frequency
4315 CONFIG_SCSI_NCR53C8XX_SYNC
4316 The SCSI Parallel Interface-2 Standard defines 4 classes of transfer
4317 rates: FAST-5, FAST-10, FAST-20 and FAST-40. The numbers are
4318 respectively the maximum data transfer rates in mega-transfers per
4319 second for each class. For example, a FAST-20 Wide 16 device is able
4320 to transfer data at 20 million 16 bit packets per second for a total
4323 You may specify 0 if you want to only use asynchronous data
4324 transfers. This is the safest and slowest option. Otherwise, specify
4325 a value between 5 and 40, depending on the capability of your SCSI
4326 controller. The higher the number, the faster the data transfer.
4327 Note that 40 should normally be ok since the driver decreases the
4328 value automatically according to the controller's capabilities.
4330 Your answer to this question is ignored for controllers with NVRAM,
4331 since the driver will get this information from the user set-up. It
4332 also can be overridden using a boot setup option, as follows
4333 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
4334 for FAST-20 synchronous data transfer (20 mega-transfers per
4337 The normal answer therefore is not to go with the default but to
4338 select the maximum value 40 allowing the driver to use the maximum
4339 value supported by each controller. If this causes problems with
4340 your SCSI devices, you should come back and decrease the value.
4342 There is no safe option other than using good cabling, right
4343 terminations and SCSI conformant devices.
4346 CONFIG_SCSI_NCR53C8XX_IOMAPPED
4347 If you say Y here, the driver will use normal IO, as opposed to
4348 memory mapped IO. Memory mapped IO has less latency than normal IO
4349 and works for most Intel-based hardware. Under Linux/Alpha only
4350 normal IO is currently supported by the driver and so, this option
4351 has no effect on those systems.
4353 The normal answer therefore is N; try Y only if you encounter SCSI
4356 not allow targets to disconnect
4357 CONFIG_SCSI_NCR53C8XX_NO_DISCONNECT
4358 This option is only provided for safety if you suspect some SCSI
4359 device of yours to not support properly the target-disconnect
4360 feature. In that case, you would say Y here. In general however, to
4361 not allow targets to disconnect is not reasonable if there is more
4362 than 1 device on a SCSI bus. The normal answer therefore is N.
4364 default tagged command queue depth
4365 CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS
4366 "Tagged command queuing" is a feature of SCSI-2 which improves
4367 performance: the host adapter can send several SCSI commands to a
4368 device's queue even if previous commands haven't finished yet. Some
4369 SCSI devices don't implement this properly; if you want to disable
4370 this feature, enter 0 or 1 here (it doesn't matter which).
4372 The default value is 8 and should be supported by most hard disks.
4373 This value can be overridden from the boot command line using the
4374 'tags' option as follows (example):
4375 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
4376 4, set queue depth to 16 for target 2 and target 3 on controller 0
4377 and set queue depth to 10 for target 0 / lun 2 on controller 1.
4379 The normal answer therefore is to go with the default 8 and to use
4380 a boot command line option for devices that need to use a different
4381 command queue depth.
4383 There is no safe option other than using good SCSI devices.
4385 maximum number of queued commands
4386 CONFIG_SCSI_NCR53C8XX_MAX_TAGS
4387 This option allows you to specify the maximum number of commands
4388 that can be queued to any device, when tagged command queuing is
4389 possible. The default value is 32. Minimum is 2, maximum is 64.
4390 Modern hard disks are able to support 64 tags and even more, but
4391 do not seem to be faster when more than 32 tags are being used.
4393 So, the normal answer here is to go with the default value 32 unless
4394 you are using very large hard disks with large cache (>= 1 MB) that
4395 are able to take advantage of more than 32 tagged commands.
4397 There is no safe option and the default answer is recommended.
4399 assume boards are SYMBIOS compatible
4400 CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT
4401 This option allows you to enable some features depending on GPIO
4402 wiring. These General Purpose Input/Output pins can be used for
4403 vendor specific features or implementation of the standard SYMBIOS
4404 features. Genuine SYMBIOS controllers use GPIO0 in output for
4405 controller LED and GPIO3 bit as a flag indicating
4406 singled-ended/differential interface. The Tekram DC-390U/F boards
4407 uses a different GPIO wiring.
4409 Your answer to this question is ignored if all your controllers have
4410 NVRAM, since the driver is able to detect the board type from the
4413 If all the controllers in your system are genuine SYMBIOS boards or
4414 use BIOS and drivers from SYMBIOS, you would want to say Y here,
4415 otherwise N. N is the safe answer.
4417 enable profiling statistics gathering
4418 CONFIG_SCSI_NCR53C8XX_PROFILE
4419 This option allows you to enable profiling information gathering.
4420 These statistics are not very accurate due to the low frequency
4421 of the kernel clock (100 Hz on i386) and have performance impact
4422 on systems that use very fast devices.
4424 The normal answer therefore is N.
4426 include support for the NCR PQS/PDS SCSI card
4427 CONFIG_SCSI_NCR53C8XX_PQS_PDS
4428 Say Y here if you have a special SCSI adapter produced by NCR
4429 corporation called a PCI Quad SCSI or PCI Dual SCSI. You do not need
4430 this if you do not have one of these adapters. However, since this
4431 device is detected as a specific PCI device, this option is quite
4434 The common answer here is N, but answering Y is safe.
4438 This is support for the IBM SCSI adapter found in many of the PS/2
4439 series computers. These machines have an MCA bus, so you need to
4440 answer Y to "MCA support" as well and read Documentation/mca.txt.
4442 If the adapter isn't found during boot (a common problem for models
4443 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
4444 option, where <pun> is the id of the SCSI subsystem (usually 7, but
4445 if that doesn't work check your reference diskette). Owners of model
4446 95 with a LED-matrix-display can in addition activate some activity
4447 info like under OS/2, but more informative, by setting
4448 'ibmmcascsi=display' as an additional kernel parameter. Try "man
4449 bootparam" or see the documentation of your boot loader about how to
4450 pass options to the kernel. The lilo procedure is also explained in
4451 the SCSI-HOWTO, available via FTP (user: anonymous) in
4452 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4454 If you want to compile this driver as a module ( = code which can be
4455 inserted in and removed from the running kernel whenever you want),
4456 say M here and read Documentation/modules.txt. The module will be
4460 CONFIG_IBMMCA_SCSI_ORDER_STANDARD
4461 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
4462 are assigned to the drive letters, starting with the lowest SCSI-id
4463 (physical number -- pun) to be drive C:, as seen from DOS and
4464 similar operating systems. When looking into papers describing the
4465 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
4466 The SCSI-standard follows a hardware-hierarchy which says that id 7
4467 has the highest priority and id 0 the lowest. Therefore, the host
4468 adapters are still today everywhere placed as SCSI-id 7 by default.
4469 In the SCSI-standard, the drive letters express the priority of the
4470 disk. C: should be the hard disk, or a partition on it, with the
4471 highest priority. This must therefore be the disk with the highest
4472 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
4473 original definition of the SCSI-standard as also industrial- and
4474 process-control-machines, like VME-CPUs running under realtime-OSs
4475 (e.g. LynxOS, OS9) do.
4477 If you like to run Linux on your MCA-machine with the same
4478 assignment of hard disks as seen from e.g. DOS or OS/2 on your
4479 machine, which is in addition conformant to the SCSI-standard, you
4480 must say Y here. This is also necessary for MCA-Linux users who want
4481 to keep downward compatibility to older releases of the
4482 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
4485 If you like to have the lowest SCSI-id assigned as drive C:, as
4486 modern SCSI-BIOSes do, which does not conform to the standard, but
4487 is widespread and common in the PC-world of today, you must say N
4488 here. If unsure, say Y.
4490 Reset SCSI-devices at boot time
4491 CONFIG_IBMMCA_SCSI_DEV_RESET
4492 By default, SCSI-devices are reset when the machine is powered on.
4493 However, some devices exist, like special-control-devices,
4494 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
4495 not reset when switched on. If you say Y here, each device connected
4496 to your SCSI-bus will be issued a reset-command after it has been
4497 probed, while the kernel is booting. This may cause problems with
4498 more modern devices, like hard disks, which do not appreciate these
4499 reset commands, and can cause your system to hang. So say Y only if
4500 you know that one of your older devices needs it; N is the safe
4503 NCR 53C9x MCA support
4504 CONFIG_SCSI_MCA_53C9X
4505 Some Microchannel machines, notably the NCR 35xx line, use a SCSI
4506 controller based on the NCR 53C94. This driver will allow use of
4507 the controller on the 3550, and very possibly others.
4509 If you want to compile this as a module (= code which can be
4510 inserted and removed from the running kernel whenever you want), say
4511 M here and read Documentation/modules.txt. The module will be called
4514 Always IN2000 SCSI support
4516 This is support for an ISA bus SCSI host adapter. You'll find more
4517 information in drivers/scsi/in2000.readme. If it doesn't work out of
4518 the box, you may have to change the jumpers for IRQ or address
4521 If you want to compile this as a module ( = code which can be
4522 inserted in and removed from the running kernel whenever you want),
4523 say M here and read Documentation/modules.txt. The module will be
4526 Initio 91XXU(W) SCSI support
4528 This is support for the Initio 91XXU(W) SCSI host adapter.
4529 Please read the SCSI-HOWTO, available via FTP (user: anonymous) at
4530 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4532 If you want to compile this as a module ( = code which can be
4533 inserted in and removed from the running kernel whenever you want),
4534 say M here and read Documentation/modules.txt. The module will be
4539 This is support for a SCSI host adapter. It is explained in section
4540 3.10 of the SCSI-HOWTO, available via FTP (user: anonymous) at
4541 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work out
4542 of the box, you may have to change some settings in
4543 drivers/scsi/pas16.h.
4545 This driver is also available as a module ( = code which can be
4546 inserted in and removed from the running kernel whenever you want).
4547 The module will be called pas16.o. If you want to compile it as a
4548 module, say M here and read Documentation/modules.txt.
4550 Initio INI-A100U2W SCSI support
4552 This is support for the Initio INI-A100U2W SCSI host adapter.
4553 Please read the SCSI-HOWTO, available via FTP (user: anonymous) at
4554 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4556 If you want to compile this as a module ( = code which can be
4557 inserted in and removed from the running kernel whenever you want),
4558 say M here and read Documentation/modules.txt. The module will be
4563 This is support for the PCI2000I EIDE interface card which acts as a
4564 SCSI host adapter. Please read the SCSI-HOWTO, available via FTP
4565 (user: anonymous) at ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4567 This driver is also available as a module called pci2000.o ( = code
4568 which can be inserted in and removed from the running kernel
4569 whenever you want). If you want to compile it as a module, say M
4570 here and read Documentation/modules.txt.
4573 CONFIG_SCSI_PCI2220I
4574 This is support for the PCI2220i EIDE interface card which acts as a
4575 SCSI host adapter. Please read the SCSI-HOWTO, available via FTP
4576 (user: anonymous) at ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4578 This driver is also available as a module called pci2220i.o ( = code
4579 which can be inserted in and removed from the running kernel
4580 whenever you want). If you want to compile it as a module, say M
4581 here and read Documentation/modules.txt.
4585 This is support for the PSI240i EIDE interface card which acts as a
4586 SCSI host adapter. Please read the SCSI-HOWTO, available via FTP
4587 (user: anonymous) at ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4589 This driver is also available as a module called psi240i.o ( = code
4590 which can be inserted in and removed from the running kernel
4591 whenever you want). If you want to compile it as a module, say M
4592 here and read Documentation/modules.txt.
4594 Qlogic FAS SCSI support
4595 CONFIG_SCSI_QLOGIC_FAS
4596 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
4597 FastSCSI! cards as well as any other card based on the FASXX chip
4598 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
4600 This driver does NOT support the PCI versions of these cards. The
4601 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
4602 SCSI support"), below.
4604 Information about this driver is contained in
4605 drivers/scsi/README.qlogicfas. You should also read the SCSI-HOWTO,
4606 available via FTP (user: anonymous) at
4607 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4609 This driver is also available as a module ( = code which can be
4610 inserted in and removed from the running kernel whenever you want).
4611 The module will be called qlogicfas.o. If you want to compile it as
4612 a module, say M here and read Documentation/modules.txt.
4614 Qlogic ISP SCSI support (EXPERIMENTAL)
4615 CONFIG_SCSI_QLOGIC_ISP
4616 This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
4617 IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
4618 card is supported by the "AM53/79C974 PCI SCSI" driver).
4620 If you say Y here, make sure to choose "BIOS" at the question "PCI
4623 Please read the file drivers/scsi/README.qlogicisp. You should also
4624 read the SCSI-HOWTO, available via FTP (user: anonymous) at
4625 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4627 This driver is also available as a module ( = code which can be
4628 inserted in and removed from the running kernel whenever you want).
4629 The module will be called qlogicisp.o. If you want to compile it as
4630 a module, say M here and read Documentation/modules.txt.
4632 Qlogic ISP FC SCSI support
4633 CONFIG_SCSI_QLOGIC_FC
4634 This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
4636 This driver is also available as a module ( = code which can be
4637 inserted in and removed from the running kernel whenever you want).
4638 The module will be called qlogicfc.o. If you want to compile it as
4639 a module, say M here and read Documentation/modules.txt.
4641 Seagate ST-02 and Future Domain TMC-8xx SCSI support
4643 These are 8-bit SCSI controllers; the ST-01 is also supported by
4644 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
4645 available via FTP (user: anonymous) at
4646 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work out
4647 of the box, you may have to change some settings in
4648 drivers/scsi/seagate.h.
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 seagate.o. If you want to compile it as a
4653 module, say M here and read Documentation/modules.txt.
4655 Trantor T128/T128F/T228 SCSI support
4657 This is support for a SCSI host adapter. It is explained in section
4658 3.11 of the SCSI-HOWTO, available via FTP (user: anonymous) at
4659 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work out
4660 of the box, you may have to change some settings in
4661 drivers/scsi/t128.h. Note that Trantor was purchased by Adaptec, and
4662 some former Trantor products are being sold under the Adaptec name.
4664 This driver is also available as a module ( = code which can be
4665 inserted in and removed from the running kernel whenever you want).
4666 The module will be called t128.o. If you want to compile it as a
4667 module, say M here and read Documentation/modules.txt.
4669 UltraStor SCSI support
4670 CONFIG_SCSI_ULTRASTOR
4671 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
4672 adapter family. This driver is explained in section 3.12 of the
4673 SCSI-HOWTO, available via FTP (user: anonymous) at
4674 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work out
4675 of the box, you may have to change some settings in
4676 drivers/scsi/ultrastor.h.
4678 Note that there is also another driver for the same hardware:
4679 "UltraStor 14F/34F support", above.
4681 If you want to compile this as a module ( = code which can be
4682 inserted in and removed from the running kernel whenever you want),
4683 say M here and read Documentation/modules.txt. The module will be
4686 7000FASST SCSI support
4687 CONFIG_SCSI_7000FASST
4688 This driver supports the Western Digital 7000 SCSI host adapter
4689 family. Some information is in the source: drivers/scsi/wd7000.c.
4691 This driver is also available as a module ( = code which can be
4692 inserted in and removed from the running kernel whenever you
4693 want). The module will be called wd7000.o. If you want to compile it
4694 as a module, say M here and read Documentation/modules.txt.
4698 This driver supports the ACARD 870U/W SCSI host adapter.
4700 This driver is also available as a module ( = code which can be
4701 inserted in and removed from the running kernel whenever you want).
4702 The module will be called atp870u.o. If you want to compile it as a
4703 module, say M here and read Documentation/modules.txt.
4705 EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support
4707 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
4708 ISA and all EISA i/o addresses are probed looking for the "EATA"
4709 signature. If you chose "BIOS" at the question "PCI access mode",
4710 the addresses of all the PCI SCSI controllers reported by the PCI
4711 subsystem are probed as well.
4713 You want to read the start of drivers/scsi/eata.c and the
4714 SCSI-HOWTO, available via FTP (user: anonymous) at
4715 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4717 Note that there is also another driver for the same hardware
4718 available: "EATA-DMA support". You should say Y to only one of them.
4720 If you want to compile this as a module ( = code which can be
4721 inserted in and removed from the running kernel whenever you want),
4722 say M here and read Documentation/modules.txt. The module will be
4725 enable tagged command queuing
4726 CONFIG_SCSI_EATA_TAGGED_QUEUE
4727 This is a feature of SCSI-2 which improves performance: the host
4728 adapter can send several SCSI commands to a device's queue even if
4729 previous commands haven't finished yet. Most EATA adapters negotiate
4730 this feature automatically with the device, even if your answer is
4731 N. The safe answer is N.
4733 enable elevator sorting
4734 CONFIG_SCSI_EATA_LINKED_COMMANDS
4735 This option enables elevator sorting for all probed SCSI disks and
4736 CDROMs. It definitely reduces the average seek distance when doing
4737 random seeks, but this does not necessarily result in a noticeable
4738 performance improvement: your mileage may vary...
4739 The safe answer is N.
4741 maximum number of queued commands
4742 CONFIG_SCSI_EATA_MAX_TAGS
4743 This specifies how many SCSI commands can be maximally queued for
4744 each probed SCSI device. You should reduce the default value of 16
4745 only if you have disks with buggy or limited tagged command support.
4746 Minimum is 2 and maximum is 62. This value is also the window size
4747 used by the elevator sorting option above. The effective value used
4748 by the driver for each probed SCSI device is reported at boot time.
4750 NCR53c406a SCSI support
4751 CONFIG_SCSI_NCR53C406A
4752 This is support for the NCR53c406a SCSI host adapter. For user
4753 configurable parameters, check out drivers/scsi/NCR53c406.c in the
4754 kernel source. Also read the SCSI-HOWTO, available via FTP (user:
4755 anonymous) at ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
4757 If you want to compile this driver as a module ( = code which can be
4758 inserted in and removed from the running kernel whenever you want),
4759 say M here and read Documentation/modules.txt. The module will be
4762 Symbios Logic sym53c416 support
4763 CONFIG_SCSI_SYM53C416
4764 This is support for the sym53c416 SCSI host adapter, the SCSI
4765 adapter that comes with some HP scanners. This driver requires that
4766 the sym53c416 is configured first using some sort of pnp
4767 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
4768 are using isapnp then you need to compile this driver as a module
4769 and then load it using insmod after isapnp has run. The parameters
4770 of the configured card(s) should be passed to the driver. The format
4773 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
4775 There is support for up to four adapters. If you want to compile
4776 this driver as a module ( = code which can be inserted in and
4777 removed from the running kernel whenever you want), say M here and
4778 read Documentation/modules.txt. The module will be called
4781 Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support
4783 This driver supports PCI SCSI host adapters based on the Am53C974A
4784 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
4785 PCscsi/PCnet (Am53/79C974) solutions.
4787 Documentation can be found in linux/drivers/scsi/README.tmscsim.
4789 Note that this driver does NOT support Tekram DC390W/U/F, which are
4790 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
4791 Also note that there is another generic Am53C974 driver,
4792 "AM53/79C974 PCI SCSI support" below. You can pick either one.
4794 If you want to compile this driver as a module ( = code which can be
4795 inserted in and removed from the running kernel whenever you want),
4796 say M here and read Documentation/modules.txt. The module will be
4799 Omit support for other Am53/79C974 based SCSI adapters
4800 CONFIG_SCSI_DC390T_NOGENSUPP
4801 If you say N here, the DC390(T) SCSI driver relies on the DC390
4802 EEPROM to get initial values for its settings, such as speed,
4803 termination, etc. If it can't find this EEPROM, it will use defaults
4804 or the user supplied boot/module parameters. For details on driver
4805 configuration see linux/drivers/scsi/README.tmscsim.
4807 If you say Y here and if no EEPROM is found, the driver gives up and
4808 thus only supports Tekram DC390(T) adapters. This can be useful if
4809 you have a DC390(T) and another Am53C974 based adapter, which, for
4810 some reason, you want to drive with the other AM53C974 driver.
4814 AM53/79C974 PCI SCSI support
4815 CONFIG_SCSI_AM53C974
4816 This is support for the AM53/79C974 SCSI host adapters. Please read
4817 drivers/scsi/README.AM53C974 for details. Also, the SCSI-HOWTO,
4818 available via FTP (user: anonymous) at
4819 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO, is for you.
4821 Note that there is another driver for AM53C974 based adapters:
4822 "Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support", above. You
4823 can pick either one.
4825 If you want to compile this driver as a module ( = code which can be
4826 inserted in and removed from the running kernel whenever you want),
4827 say M here and read Documentation/modules.txt. The module will be
4830 AMI MegaRAID support
4831 CONFIG_SCSI_MEGARAID
4832 This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490
4833 and 467 SCSI host adapters.
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
4843 #Concurrent IO commands on MegaRAID
4844 #CONFIG_MEGARAID_MULTI_IO
4846 GDT SCSI Disk Array Controller support
4848 This is a driver for all SCSI Disk Array Controllers (EISA/ISA/PCI)
4849 manufactured by ICP vortex. It is documented in the kernel source in
4850 drivers/scsi/gdth.c and drivers/scsi/gdth.h.
4852 This driver is also available as a module ( = code which can be
4853 inserted in and removed from the running kernel whenever you want).
4854 If you want to compile it as a module, say M here and read
4855 Documentation/modules.txt.
4857 IOMEGA parallel port (ppa - older drives)
4859 This driver supports older versions of IOMEGA's parallel port ZIP
4860 drive (a 100 MB removable media device).
4862 Note that you can say N here if you have the SCSI version of the ZIP
4863 drive: it will be supported automatically if you said Y to the
4864 generic "SCSI disk support", above.
4866 If you have the ZIP Plus drive or a more recent parallel port ZIP
4867 drive (if the supplied cable with the drive is labeled "AutoDetect")
4868 then you should say N here and Y to "IOMEGA parallel port (imm -
4869 newer drives)", below.
4871 For more information about this driver and how to use it you should
4872 read the file drivers/scsi/README.ppa. You should also read the
4873 SCSI-HOWTO, which is available via FTP (user: anonymous) from
4874 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. If you use this driver,
4875 you will still be able to use the parallel port for other tasks,
4876 such as a printer; it is safe to compile both drivers into the
4879 This driver is also available as a module which can be inserted in
4880 and removed from the running kernel whenever you want. To compile
4881 this driver as a module, say M here and read
4882 Documentation/modules.txt. The module will be called ppa.o.
4884 IOMEGA parallel port (imm - newer drives)
4886 This driver supports newer versions of IOMEGA's parallel port ZIP
4887 drive (a 100 MB removable media device).
4889 Note that you can say N here if you have the SCSI version of the ZIP
4890 drive: it will be supported automatically if you said Y to the
4891 generic "SCSI disk support", above.
4893 If you have the ZIP Plus drive or a more recent parallel port ZIP
4894 drive (if the supplied cable with the drive is labeled "AutoDetect")
4895 then you should say Y here; if you have an older ZIP drive, say N
4896 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
4898 For more information about this driver and how to use it you should
4899 read the file drivers/scsi/README.ppa. You should also read the
4900 SCSI-HOWTO, which is available via FTP (user: anonymous) from
4901 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. If you use this driver,
4902 you will still be able to use the parallel port for other tasks,
4903 such as a printer; it is safe to compile both drivers into the
4906 This driver is also available as a module which can be inserted in
4907 and removed from the running kernel whenever you want. To compile
4908 this driver as a module, say M here and read
4909 Documentation/modules.txt. The module will be called imm.o.
4911 Force the Iomega ZIP drivers to use EPP-16
4912 CONFIG_SCSI_IZIP_EPP16
4913 EPP (Enhanced Parallel Port) is a standard for parallel ports which
4914 allows them to act as expansion buses that can handle up to 64
4917 Some parallel port chipsets are slower than their motherboard, and
4918 so we have to control the state of the chipset's FIFO queue every
4919 now and then to avoid data loss. This will be done if you say Y
4922 Generally, saying Y is the safe option and slows things down a bit.
4924 Assume slow parallel port control register
4925 CONFIG_SCSI_IZIP_SLOW_CTR
4926 Some parallel ports are known to have excessive delays between
4927 changing the parallel port control register and good data being
4928 available on the parallel port data/status register. This option
4929 forces a small delay (1.0 usec to be exact) after changing the
4930 control register to let things settle out. Enabling this option may
4931 result in a big drop in performance but some very old parallel ports
4932 (found in 386 vintage machines) will not work properly.
4934 Generally, saying N is fine.
4936 SCSI Debug host simulator.
4938 This is a host adapter simulator that can be programmed to simulate
4939 a large number of conditions that could occur on a real bus. The
4940 advantage is that many hard to reproduce problems can be tested in a
4941 controlled environment where there is reduced risk of losing
4942 important data. This is primarily of use to people trying to debug
4943 the middle and upper layers of the SCSI subsystem. If unsure, say N.
4945 Fibre Channel support
4947 This is an experimental support for storage arrays connected to
4948 the system using Fibre Optic and the "X3.269-199X Fibre Channel
4949 Protocol for SCSI" specification. You'll also need the generic SCSI
4950 support, as well as the drivers for the storage array itself and
4951 for the interface adapter such as SOC. This subsystem could even
4952 serve for IP networking, with some code extensions.
4958 Serial Optical Channel is an interface card with one or two Fibre
4959 Optic ports, each of which can be connected to a disk array. Only
4960 the SBus incarnation of the adapter is supported at the moment.
4962 SparcSTORAGE Array 100 and 200 series
4964 If you never bought a disk array made by Sun, go with N.
4967 CONFIG_SCSI_ACORNSCSI_3
4968 This enables support for the Acorn SCSI card (aka30). If you have an
4969 Acorn system with one of these, say Y. If unsure, say N.
4971 Acorn SCSI tagged queue support
4972 CONFIG_SCSI_ACORNSCSI_TAGGED_QUEUE
4973 Say Y here to enable tagged queuing support on the Acorn SCSI card.
4975 This is a feature of SCSI-2 which improves performance: the host
4976 adapter can send several SCSI commands to a device's queue even if
4977 previous commands haven't finished yet. Some SCSI devices don't
4978 implement this properly, so the safe answer is N.
4980 Acorn SCSI Synchronous transfers support
4981 CONFIG_SCSI_ACORNSCSI_SYNC
4982 Say Y here to enable synchronous transfer negotiation with all
4983 targets on the Acorn SCSI card.
4985 In general, this improves performance; however some SCSI devices
4986 don't implement it properly, so the safe answer is N.
4990 This enables support for the Oak SCSI card. If you have an Acorn
4991 system with one of these, say Y. If unsure, say N.
4993 Cumana SCSI I support
4994 CONFIG_SCSI_CUMANA_1
4995 This enables support for the Cumana SCSI I card. If you have an
4996 Acorn system with one of these, say Y. If unsure, say N.
4998 Cumana SCSI II support
4999 CONFIG_SCSI_CUMANA_2
5000 This enables support for the Cumana SCSI II card. If you have an
5001 Acorn system with one of these, say Y. If unsure, say N.
5005 This enables support for the EcoSCSI card -- a small card that sits
5006 in the Econet socket. If you have an Acorn system with one of these,
5007 say Y. If unsure, say N.
5010 CONFIG_SCSI_EESOXSCSI
5011 This enables support for the EESOX SCSI card. If you have an Acorn
5012 system with one of these, say Y, otherwise say N.
5014 Powertec SCSI support
5015 CONFIG_SCSI_POWERTECSCSI
5016 This enables support for the Powertec SCSI card on Acorn systems. If
5017 you have one of these, say Y. If unsure, say N.
5019 Network device support?
5021 You can say N here if you don't intend to connect your Linux box to
5022 any other computer at all or if all your connections will be over a
5023 telephone line with a modem either via UUCP (UUCP is a protocol to
5024 forward mail and news between unix hosts over telephone lines; read
5025 the UUCP-HOWTO, available via FTP (user: anonymous) in
5026 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO) or dialing up a shell
5027 account or a BBS, even using term (term is a program which gives you
5028 almost full Internet connectivity if you have a regular dial up
5029 shell account on some Internet connected Unix computer. Read
5030 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html (to browse
5031 the WWW, you need to have access to a machine on the Internet that
5032 has a program like lynx or netscape)).
5034 You'll have to say Y if your computer contains a network card that
5035 you want to use under Linux (make sure you know its name because you
5036 will be asked for it and read the Ethernet-HOWTO (especially if you
5037 plan to use more than one network card under Linux), available from
5038 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini) or if you want to
5039 use SLIP (Serial Line Internet Protocol is the protocol used to send
5040 Internet traffic over telephone lines or null modem cables) or CSLIP
5041 (compressed SLIP) or PPP (Point to Point Protocol, a better and
5042 newer replacement for SLIP) or PLIP (Parallel Line Internet Protocol
5043 is mainly used to create a mini network by connecting the parallel
5044 ports of two local machines) or AX.25/KISS (protocol for sending
5045 Internet traffic over amateur radio links).
5047 Make sure to read the NET-3-HOWTO. Eventually, you will have to read
5048 Olaf Kirch's excellent and free book "Network Administrator's
5049 Guide", to be found in ftp://metalab.unc.edu/pub/Linux/docs/LDP. If
5052 Dummy net driver support
5054 This is essentially a bit-bucket device (i.e. traffic you send to
5055 this device is consigned into oblivion) with a configurable IP
5056 address. It is most commonly used in order to make your currently
5057 inactive SLIP address seem like a real address for local programs.
5058 If you use SLIP or PPP, you might want to say Y here. Read about it
5059 in the Network Administrator's Guide, available via FTP (user:
5060 anonymous) from ftp://metalab.unc.edu/pub/Linux/docs/LDP. Since this
5061 thing often comes in handy, the default is Y. It won't enlarge your
5062 kernel either. What a deal.
5064 If you want to compile this as a module ( = code which can be
5065 inserted in and removed from the running kernel whenever you want),
5066 say M here and read Documentation/modules.txt. The module will be
5067 called dummy.o. If you want to use more than one dummy device at a
5068 time, you need to compile this driver as a module. Instead of
5069 'dummy', the devices will then be called 'dummy0', 'dummy1' etc.
5071 SLIP (serial line) support
5073 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
5074 connect to your Internet service provider or to connect to some
5075 other local Unix box or if you want to configure your Linux box as a
5076 Slip/CSlip server for other people to dial in. SLIP (Serial Line
5077 Internet Protocol) is a protocol used to send Internet traffic over
5078 serial connections such as telephone lines or null modem cables;
5079 nowadays, the protocol PPP is more commonly used for this same
5082 Normally, your access provider has to support SLIP in order for you
5083 to be able to use it, but there is now a SLIP emulator called SLiRP
5084 around (available via FTP (user: anonymous) from
5085 ftp://metalab.unc.edu/pub/Linux/system/network/serial/ ) which
5086 allows you to use SLIP over a regular dial up shell connection. If
5087 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
5088 NET-3-HOWTO, available via FTP (user: anonymous) in
5089 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO, explains how to
5090 configure SLIP. Note that you don't need this option if you just
5091 want to run term (term is a program which gives you almost full
5092 Internet connectivity if you have a regular dial up shell account on
5093 some Internet connected Unix computer. Read
5094 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html (to browse
5095 the WWW, you need to have access to a machine on the Internet that
5096 has a program like lynx or netscape)). SLIP support will enlarge
5097 your kernel by about 4 KB. If unsure, say N.
5099 If you want to compile this as a module ( = code which can be
5100 inserted in and removed from the running kernel whenever you want),
5101 say M here and read Documentation/modules.txt as well as
5102 Documentation/networking/net-modules.txt. The module will be called
5105 CSLIP compressed headers
5106 CONFIG_SLIP_COMPRESSED
5107 This protocol is faster than SLIP because it uses compression on the
5108 TCP/IP headers (not on the data itself), but it has to be supported
5109 on both ends. Ask your access provider if you are not sure and
5110 answer Y, just in case. You will still be able to use plain SLIP. If
5111 you plan to use SLiRP, the SLIP emulator (available via FTP (user:
5113 ftp://metalab.unc.edu/pub/Linux/system/network/serial/) which allows
5114 you to use SLIP over a regular dial up shell connection, you
5115 definitely want to say Y here. The NET-3-HOWTO, available via FTP
5116 (user: anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO,
5117 explains how to configure CSLIP. This won't enlarge your kernel.
5119 Keepalive and linefill
5121 Adds additional capabilities to the SLIP driver to support the
5122 RELCOM line fill and keepalive monitoring. Ideal on poor quality
5125 Six bit SLIP encapsulation
5126 CONFIG_SLIP_MODE_SLIP6
5127 Just occasionally you may need to run IP over hostile serial
5128 networks that don't pass all control characters or are only seven
5129 bit. Saying Y here adds an extra mode you can use with SLIP:
5130 "slip6". In this mode, SLIP will only send normal ASCII symbols over
5131 the serial device. Naturally, this has to be supported at the other
5132 end of the link as well. It's good enough, for example, to run IP
5133 over the async ports of a Camtec JNT Pad. If unsure, say N.
5135 PPP (point-to-point protocol) support
5137 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
5138 the same purpose: sending Internet traffic over telephone (and other
5139 serial) lines. Most ISPs these days support PPP rather than SLIP.
5141 To use PPP, you need an additional program called pppd as described
5142 in Documentation/networking/ppp.txt and in the PPP-HOWTO, available
5143 from ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. If you upgrade
5144 from an older kernel, you might need to upgrade pppd as well. The
5145 PPP option enlarges your kernel by about 16 KB.
5147 Almost always, if you answer Y or M to this question, you should
5148 give the same answer to the next question, about PPP support for
5151 This driver is also available as a module ( = code which can be
5152 inserted in and removed from the running kernel whenever you want).
5153 If you said Y to "Version information on all symbols" above, then
5154 you cannot compile the PPP driver into the kernel; you can then only
5155 compile it as a module. The module will be called ppp_generic.o. If
5156 you want to compile it as a module, say M here and read
5157 Documentation/modules.txt as well as
5158 Documentation/networking/net-modules.txt.
5160 PPP support for async serial ports
5162 Say Y (or M) here if you want to be able to use PPP over standard
5163 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
5164 a modem (not a synchronous or ISDN modem) to contact your ISP, you
5167 This code is also available as a module (code which can be inserted
5168 into and removed from the running kernel). If you want to compile
5169 it as a module, say M here and read Documentation/modules.txt.
5171 PPP Deflate compression
5173 Support for the Deflate compression method for PPP, which uses the
5174 Deflate algorithm (the same algorithm that gzip uses) to compress
5175 each PPP packet before it is sent over the wire. The peer (the
5176 machine at the other end of the PPP link, usually your ISP) has to
5177 support the Deflate compression method as well for this to be
5180 This code is also available as a module (code which can be inserted
5181 into and removed from the running kernel). If you want to compile
5182 it as a module, say M here and read Documentation/modules.txt.
5184 PPP BSD-Compress compression
5186 Support for the BSD-Compress compression method for PPP, which uses
5187 the LZW compression method to compress each PPP packet before it is
5188 sent over the wire. The peer (the other end of the PPP link) has to
5189 support the BSD-Compress compression method as well for this to be
5190 useful. The PPP Deflate compression method is preferable to
5191 BSD-Compress, because it compresses better and is patent-free.
5193 Note that the BSD compression code will always be compiled as a
5194 module; it is called bsd_comp.o and will show up in the directory
5195 modules once you have said "make modules". If unsure, say N.
5197 Wireless LAN (non-hamradio)
5199 Support for wireless LANs and everything having to do with radio,
5200 but not with amateur radio. Note that the answer to this question
5201 won't directly affect the kernel: saying N will just cause this
5202 configure script to skip all the questions about radio
5205 Some user-level drivers for scarab devices which don't require
5206 special kernel support are available via FTP (user: anonymous) from
5207 ftp://shadow.cabi.net/pub/Linux.
5209 STRIP (Metricom Starmode radio IP)
5211 Say Y if you have a Metricom radio and intend to use Starmode Radio
5212 IP. STRIP is a radio protocol developed for the MosquitoNet project
5213 (On the WWW at http://mosquitonet.stanford.edu/; to browse the WWW,
5214 you need to have access to a machine on the Internet that has a
5215 program like lynx or netscape) to send Internet traffic using
5216 Metricom radios. Metricom radios are small, battery powered,
5217 100kbit/sec packet radio transceivers, about the size and weight of
5218 a cellular telephone. (You may also have heard them called
5219 "Metricom modems" but we avoid the term "modem" because it misleads
5220 many people into thinking that you can plug a Metricom modem into a
5221 phone line and use it as a modem.)
5223 You can use STRIP on any Linux machine with a serial port, although
5224 it is obviously most useful for people with laptop computers. If you
5225 think you might get a Metricom radio in the future, there is no harm
5226 in saying Y to STRIP now, except that it makes the kernel a bit
5229 You can also compile this as a module ( = code which can be inserted
5230 in and removed from the running kernel whenever you want), say M
5231 here and read Documentation/modules.txt. The module will be called
5234 AT&T WaveLAN & DEC RoamAbout DS support
5236 The Lucent WaveLAN (formerly NCR and AT&T; or DEC RoamAbout DS) is
5237 a Radio LAN (wireless Ethernet-like Local Area Network) using the
5238 radio frequencies 900 MHz and 2.4 GHz.
5240 This driver support the ISA version of the WaveLAN card. A separate
5241 driver for the PCMCIA (PC-card) hardware is available in David
5242 Hinds' pcmcia-cs package (see the file Documentation/Changes for
5245 If you want to use an ISA WaveLAN card under Linux, say Y and read
5246 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5247 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Some more specific
5248 information is contained in Documentation/networking/wavelan.txt and
5249 in the source code drivers/net/wavelan.p.h.
5251 You will also need the wireless tools package available from
5252 ftp://ftp.inka.de/pub/comp/Linux/networking/NetTools/contrib/.
5253 Please read the man pages contained therein.
5255 This driver is also available as a module ( = code which can be
5256 inserted in and removed from the running kernel whenever you want).
5257 The module will be called wavelan.o. If you want to compile it as a
5258 module, say M here and read Documentation/modules.txt as well as
5259 Documentation/networking/net-modules.txt.
5261 Aironet Arlan 655 & IC2200 DS support
5263 Aironet makes Arlan. www.aironet.com. Uses www.Telxon.com chip, which is
5264 used on several similar cards. Driver is tested on 655 and IC2200 series.
5265 Look for http://www.ylenurme.ee/~elmer/655/ for latest information.
5266 Driver is build as two modules, arlan and arlan-proc. The later is /proc
5267 interface and not needed most of time.
5268 On some computers the card ends up in non-valid state after some time.
5269 Use a ping-reset script to clear it.
5272 LAPB over Ethernet driver
5274 This is a driver for a pseudo device (typically called /dev/lapb0)
5275 which allows you to open an LAPB point-to-point connection to some
5276 other computer on your Ethernet network. In order to do this, you
5277 need to say Y or M to the driver for your Ethernet card as well as
5278 to "LAPB Data Link Driver".
5280 If you want to compile this driver as a module ( = code which can be
5281 inserted in and removed from the running kernel whenever you want),
5282 say M here and read Documentation/modules.txt. The module will be
5283 called lapbether.o. If unsure, say N.
5287 This is a driver for sending and receiving X.25 frames over regular
5288 asynchronous serial lines such as telephone lines equipped with
5289 ordinary modems. Experts should note that this driver doesn't
5290 currently comply with the asynchronous HDLS framing protocols in
5291 CCITT recommendation X.25.
5293 If you want to compile this driver as a module ( = code which can be
5294 inserted in and removed from the running kernel whenever you want),
5295 say M here and read Documentation/modules.txt. The module will be
5296 called x25_asy.o. If unsure, say N.
5298 PLIP (parallel port) support
5300 PLIP (Parallel Line Internet Protocol) is used to create a
5301 reasonably fast mini network consisting of two (or, rarely, more)
5302 local machines. A PLIP link from a Linux box is a popular means to
5303 install a Linux distribution on a machine which doesn't have a CDROM
5304 drive (a minimal system has to be transferred with floppies first).
5305 The kernels on both machines need to have this PLIP option enabled
5308 The PLIP driver has two modes, mode 0 and mode 1. The parallel ports
5309 (the connectors at the computers with 25 holes) are connected with
5310 "null printer" or "Turbo Laplink" cables which can transmit 4 bits
5311 at a time (mode 0) or with special PLIP cables, to be used on
5312 bidirectional parallel ports only, which can transmit 8 bits at a
5313 time (mode 1); you can find the wiring of these cables in
5314 Documentation/networking/PLIP.txt. The cables can be up to 15m long.
5315 Mode 0 works also if one of the machines runs DOS/Windows and has
5316 some PLIP software installed, e.g. the Crynwr PLIP packet driver
5317 (http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html; to browse
5318 the WWW, you need to have access to a machine on the Internet that
5319 has a program like lynx or netscape) and winsock or NCSA's telnet.
5321 If you want to use PLIP, say Y and read the PLIP mini-HOWTO,
5322 available via FTP (user: anonymous) in
5323 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini as well as the
5324 NET-3-HOWTO in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Note that
5325 the PLIP protocol was changed and this PLIP driver won't work
5326 together with the PLIP support in Linux versions 1.0.x. This option
5327 enlarges your kernel by about 8 KB.
5329 If you want to compile this as a module ( = code which can be
5330 inserted in and removed from the running kernel whenever you want),
5331 say M here and read Documentation/modules.txt as well as
5332 Documentation/networking/net-modules.txt. The module will be called
5333 plip.o. If unsure, say Y or M, in case you buy a laptop later.
5335 EQL (serial line load balancing) support
5337 If you have two serial connections to some other computer (this
5338 usually requires two modems and two telephone lines) and you use
5339 SLIP (the protocol for sending Internet traffic over telephone
5340 lines) or PPP (a better SLIP) on them, you can make them behave like
5341 one double speed connection using this driver. Naturally, this has
5342 to be supported at the other end as well, either with a similar EQL
5343 Linux driver or with a Livingston Portmaster 2e.
5345 Say Y if you want this and read Documentation/networking/eql.txt.
5346 You may also want to read section 6.2 of the NET-3-HOWTO, available
5347 via FTP (user: anonymous) from
5348 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
5350 This driver is also available as a module ( = code which can be
5351 inserted in and removed from the running kernel whenever you want).
5352 The module will be called eql.o. If you want to compile it as a
5353 module, say M here and read Documentation/modules.txt. If unsure,
5356 Ethertap network tap
5358 If you say Y here (and have said Y to "Kernel/User network link
5359 driver", above) and create a character special file /dev/tap0 with
5360 major number 36 and minor number 16 using mknod ("man mknod"), you
5361 will be able to have a user space program read and write raw
5362 Ethernet frames from/to that special file. tap0 can be configured
5363 with ifconfig and route like any other Ethernet device but it is not
5364 connected to any physical LAN; everything written by the user to
5365 /dev/tap0 is treated by the kernel as if it had come in from a LAN
5366 to the device tap0; everything the kernel wants to send out over the
5367 device tap0 can instead be read by the user from /dev/tap0: the user
5368 mode program replaces the LAN that would be attached to an ordinary
5369 Ethernet device. Please read the file
5370 Documentation/networking/ethertap.txt for more information.
5372 This driver is also available as a module ( = code which can be
5373 inserted in and removed from the running kernel whenever you want).
5374 The module will be called ethertap.o. If you want to compile it as a
5375 module, say M here and read Documentation/modules.txt. If you don't
5376 know what to use this for, you don't need it.
5378 Sealevel Systems 4021 support
5379 CONFIG_SEALEVEL_4021
5380 This is a driver for the Sealevel Systems ACB 56 serial I/O adapter.
5382 This driver can only be compiled as a module ( = code which can be
5383 inserted in and removed from the running kernel whenever you want).
5384 If you want to do that, say M here. The module will be called
5387 Frame Relay (DLCI) support
5389 This is support for the frame relay protocol; frame relay is a fast
5390 low-cost way to connect to a remote Internet access provider or to
5391 form a private wide area network. The one physical line from your
5392 box to the local "switch" (i.e. the entry point to the frame relay
5393 network, usually at the phone company) can carry several logical
5394 point-to-point connections to other computers connected to the frame
5395 relay network. For a general explanation of the protocol, check out
5396 http://www.frforum.com/ on the WWW. (To browse the WWW, you need to
5397 have access to a machine on the Internet that has a program like
5398 lynx or netscape.) To use frame relay, you need supporting hardware
5399 (called FRAD) and certain programs from the net-tools package as
5400 explained in Documentation/networking/framerelay.txt.
5402 This driver is also available as a module ( = code which can be
5403 inserted in and removed from the running kernel whenever you want).
5404 The module will be called dlci.o. If you want to compile it as a
5405 module, say M here and read Documentation/modules.txt.
5409 This is the maximal number of logical point-to-point frame relay
5410 connections (the identifiers of which are called DCLIs) that
5411 the driver can handle. The default is probably fine.
5415 You can specify here how many logical point-to-point frame relay
5416 connections (the identifiers of which are called DCLIs) should be
5417 handled by each of your hardware frame relay access devices. Go with
5420 Sangoma S502A FRAD support
5422 Say Y here if you need a driver for the Sangoma S502A, S502E, and
5423 S508 Frame Relay Access Devices. These are multi-protocol cards, but
5424 only frame relay is supported by the driver at this time. Please
5425 read Documentation/framerelay.txt.
5427 This driver is also available as a module ( = code which can be
5428 inserted in and removed from the running kernel whenever you want).
5429 The module will be called sdla.o. If you want to compile it as a
5430 module, say M here and read Documentation/modules.txt.
5432 Acorn Econet/AUN protocols (EXPERIMENTAL)
5434 Econet is a fairly old and slow networking protocol mainly used by
5435 Acorn computers to access file and print servers. It uses native
5436 Econet network cards. AUN is an implementation of the higher level
5437 parts of Econet that runs over ordinary Ethernet connections, on
5438 top of the UDP packet protocol, which in turn runs on top of the
5439 Internet protocol IP.
5441 If you say Y here, you can choose with the next two options whether
5442 to send Econet/AUN traffic over a UDP Ethernet connection or over
5443 a native Econet network card.
5445 This driver is also available as a module ( = code which can be
5446 inserted in and removed from the running kernel whenever you want).
5447 The module will be called econet.o. If you want to compile it as a
5448 module, say M here and read Documentation/modules.txt.
5451 CONFIG_ECONET_AUNUDP
5452 Say Y here if you want to send Econet/AUN traffic over a UDP
5453 connection (UDP is a packet based protocol that runs on top of the
5454 Internet protocol IP) using an ordinary Ethernet network card.
5457 CONFIG_ECONET_NATIVE
5458 Say Y here if you have a native Econet network card installed in
5463 Wide Area Networks (WANs), such as X.25, frame relay and leased
5464 lines, are used to interconnect Local Area Networks (LANs) over vast
5465 distances with data transfer rates significantly higher than those
5466 achievable with commonly used asynchronous modem connections.
5467 Usually, a quite expensive external device called a `WAN router' is
5468 needed to connect to a WAN.
5470 As an alternative, WAN routing can be built into the Linux kernel.
5471 With relatively inexpensive WAN interface cards available on the
5472 market, a perfectly usable router can be built for less than half
5473 the price of an external router. If you have one of those cards and
5474 wish to use your Linux box as a WAN router, say Y here and also to
5475 the WAN driver for your card, below. You will then need the
5476 wan-tools package which is available via FTP (user: anonymous) from
5477 ftp://ftp.sangoma.com. Read Documentation/networking/wan-router.txt
5478 for more information.
5480 The WAN routing support is also available as a module called
5481 wanrouter.o ( = code which can be inserted in and removed from the
5482 running kernel whenever you want). If you want to compile it as a
5483 module, say M here and read Documentation/modules.txt.
5487 Fast switching (read help!)
5488 CONFIG_NET_FASTROUTE
5489 Saying Y here enables direct NIC-to-NIC (NIC = Network Interface
5490 Card) data transfers, which is fast.
5492 *** This option is NOT COMPATIBLE with several important ***
5493 *** networking options: especially CONFIG_NETFILTER. ***
5494 *** Say N here if you intend to use Linux as a firewall. ***
5496 However, it will work with all options in CONFIG_IP_ADVANCED_ROUTER
5497 section (except for CONFIG_IP_ROUTE_TOS and CONFIG_IP_ROUTE_FWMARK).
5498 At the moment, few devices support fast switching (tulip is one of
5499 them, modified 8390 can be found at
5500 ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz).
5504 Forwarding between high speed interfaces
5505 CONFIG_NET_HW_FLOWCONTROL
5506 This option enables NIC (Network Interface Card) hardware throttling
5507 during periods of extremal congestion. At the moment only a couple
5508 of device drivers support it (really only one -- tulip, modified
5509 8390 can be found at
5510 ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz).
5511 Really, this option is applicable to any machine attached to a fast enough
5512 network, and even a 10 Mb NIC is able to kill a not very slow box,
5513 such as a 120MHz Pentium.
5515 However, do not say Y here if you did not experience any serious
5518 CPU is too slow to handle full bandwidth
5520 If you suspect that your CPU is not fast enough to handle the
5521 full bandwidth of your network connection, try saying Y here. If
5524 QoS and/or fair queueing
5526 When the kernel has several packets to send out over the network
5527 devices, it has to make a decision which one to send first. This is
5528 especially important if some of the network devices are real time
5529 devices that need a certain minimum data flow rate. There are
5530 several different algorithms for how to do this "fairly"; they are
5531 called packet schedulers. If you want to stick to the default
5532 scheduling algorithm, say N here. If you want to experiment with a
5533 couple of different algorithms, say Y. You can then attach different
5534 schedulers to different network devices. Currently, this is only
5535 recommended for experts.
5537 To administer these schedulers, you'll need the user-level utilities
5538 from the package iproute2+tc at ftp://ftp.inr.ac.ru/ip-routing/
5540 If you say Y here and to "/proc filesystem" below, you will be able
5541 to read status information about priority schedulers from the file
5544 The available schedulers are listed in the following questions; you
5545 can say Y to as many as you like. If unsure, say N now.
5547 CBQ packet scheduler
5549 Say Y here if you want to use the Class-Based Queueing (CBQ) packet
5550 scheduling algorithm for some of your network devices. This
5551 algorithm classifies the waiting packets into a tree-like hierarchy
5552 of classes; the leaves of this tree are in turn scheduled by
5553 separate algorithms (called "disciplines" in this context) which you
5554 can choose below from among the various queueing algorithms. See the
5555 top of net/sched/sch_cbq.c for references about the CBQ algorithm.
5557 This code is also available as a module called sch_cbq.o ( = code
5558 which can be inserted in and removed from the running kernel
5559 whenever you want). If you want to compile it as a module, say M
5560 here and read Documentation/modules.txt.
5562 CSZ packet scheduler
5564 Say Y here if you want to use the Clark-Shenker-Zhang (CSZ) packet
5565 scheduling algorithm for some of your network devices. At the
5566 moment, this is the only algorithm that can guarantee service for
5567 real-time applications (see the top of net/sched/sch_csz.c for
5568 details and references about the algorithm).
5570 Note: this scheduler is currently broken.
5572 This code is also available as a module called sch_csz.o ( = code
5573 which can be inserted in and removed from the running kernel
5574 whenever you want). If you want to compile it as a module, say M
5575 here and read Documentation/modules.txt.
5577 The simplest PRIO pseudo scheduler
5579 Say Y here if you want to use an n-band priority queue packet
5580 "scheduler" for some of your network devices or as a leaf discipline
5581 for the CBQ scheduling algorithm.
5583 This code is also available as a module called sch_prio.o ( = code
5584 which can be inserted in and removed from the running kernel
5585 whenever you want). If you want to compile it as a module, say M
5586 here and read Documentation/modules.txt.
5590 Say Y here if you want to use the Random Early Detection (RED)
5591 packet scheduling algorithm for some of your network devices (see
5592 the top of net/sched/sch_red.c for details and references about the
5595 This code is also available as a module called sch_red.o ( = code
5596 which can be inserted in and removed from the running kernel
5597 whenever you want). If you want to compile it as a module, say M
5598 here and read Documentation/modules.txt.
5602 Say Y here if you want to use the Stochastic Fairness Queueing (SFQ)
5603 packet scheduling algorithm for some of your network devices or as a
5604 leaf discipline for the CBQ scheduling algorithm (see the top of
5605 net/sched/sch_sfq.c for details and references about the SFQ
5608 This code is also available as a module called sch_sfq.o ( = code
5609 which can be inserted in and removed from the running kernel
5610 whenever you want). If you want to compile it as a module, say M
5611 here and read Documentation/modules.txt.
5615 Say Y here if you want to use the True Link Equalizer (TLE) packet
5616 scheduling algorithm for some of your network devices or as a leaf
5617 discipline for the CBQ scheduling algorithm. This queueing
5618 discipline allows the combination of several physical devices into
5619 one virtual device. (see the top of net/sched/sch_teql.c for
5622 This code is also available as a module called sch_teql.o ( = code
5623 which can be inserted in and removed from the running kernel
5624 whenever you want). If you want to compile it as a module, say M
5625 here and read Documentation/modules.txt.
5629 Say Y here if you want to use the Simple Token Bucket Filter (TBF)
5630 packet scheduling algorithm for some of your network devices or as a
5631 leaf discipline for the CBQ scheduling algorithm (see the top of
5632 net/sched/sch_tbf.c for a description of the TBF algorithm).
5634 This code is also available as a module called sch_tbf.o ( = code
5635 which can be inserted in and removed from the running kernel
5636 whenever you want). If you want to compile it as a module, say M
5637 here and read Documentation/modules.txt.
5641 Say Y here if you want to include Quality Of Service scheduling
5642 features, which means that you will be able to request certain
5643 rate-of-flow limits for your net devices.
5645 Note that the answer to this question won't directly affect the
5646 kernel: saying N will just cause this configure script to skip all
5647 the questions about QoS support.
5650 CONFIG_NET_ESTIMATOR
5651 In order for Quality of Service scheduling to work, the current
5652 rate-of-flow for a network device has to be estimated; if you say Y
5653 here, the kernel will do just that.
5655 Packet classifier API
5657 The CBQ scheduling algorithm requires that network packets which are
5658 scheduled to be sent out over a network device be classified in some
5659 way. If you say Y here, you will get a choice of several different
5660 packet classifiers with the following questions.
5662 # Routing tables based classifier
5663 # CONFIG_NET_CLS_ROUTE
5665 # Firewall based classifier
5669 # CONFIG_NET_CLS_U32
5671 # Special RSVP classifier
5672 # CONFIG_NET_CLS_RSVP
5674 # Special RSVP classifier for IPv6
5675 # CONFIG_NET_CLS_RSVP6
5677 # Ingres traffic policing
5678 # CONFIG_NET_CLS_POLICE
5680 ### Some expert please fill these in
5683 Network code profiler
5685 If you say Y here and to "/proc filesystem support" below, some
5686 obscure and undocumented information about the network code's
5687 performance will be written to /proc/net/profile. If you don't know
5688 what it is about, you don't need it: say N.
5690 Comtrol Hostess SV-11 support
5692 This is a network card for low speed synchronous serial links, at
5693 up to 256Kbps. It supports both PPP and Cisco HDLC.
5695 At this point, the driver can only be compiled as a module.
5697 COSA/SRP sync serial boards support
5699 This is a driver for COSA and SRP synchronous serial boards. These
5700 boards allow to connect synchronous serial devices (for example
5701 base-band modems, or any other device with the X.21, V.24, V.35 or
5702 V.36 interface) to your Linux box. The cards can work as the
5703 character device, synchronous PPP network device, or the Cisco HDLC
5706 To actually use the COSA or SRP board, you will need user-space
5707 utilities for downloading the firmware to the cards and to set them
5708 up. Look at the http://www.fi.muni.cz/~kas/cosa/ for more
5709 information about the cards (including the pointer to the user-space
5710 utilities). You can also read the comment at the top of the
5711 drivers/net/cosa.c for details about the cards and the driver
5714 The driver will be compiled as a module ( = code which can be
5715 inserted in and removed from the running kernel whenever you want).
5716 The module will be called cosa.o. For general information about
5717 modules read Documentation/modules.txt.
5719 Red Creek Hardware VPN (EXPERIMENTAL)
5721 This is a driver for hardware which provides a Virtual Private
5722 Network (VPN). Say Y if you have it.
5724 This code is also available as a module called rcpci.o ( = code
5725 which can be inserted in and removed from the running kernel
5726 whenever you want). If you want to compile it as a module, say M
5727 here and read Documentation/modules.txt.
5731 Say Y to this option if your Linux box contains a WAN card and you
5732 are planning to use the box as a WAN ( = Wide Area Network) router
5733 ( = device used to interconnect local area networks over wide area
5734 communication links, such as leased lines or public data networks,
5735 e.g. X.25 or frame relay) and you will be offered a list of drivers
5736 for WAN cards currently available. For more information, read
5737 Documentation/networking/wan-router.txt.
5739 Note that the answer to this question won't directly affect the
5740 kernel: saying N will just cause this configure script to skip all
5741 the questions about WAN card drivers. If unsure, say N.
5743 Sangoma WANPIPE(tm) multiprotocol cards
5744 CONFIG_VENDOR_SANGOMA
5745 WANPIPE from Sangoma Technologies Inc. (http://www.sangoma.com; to
5746 browse the WWW, you need to have access to a machine on the Internet
5747 that has a program like lynx or netscape) is a family of intelligent
5748 multiprotocol WAN adapters with data transfer rates up to T1 (1.544
5749 Mbps). They are also known as Synchronous Data Link Adapters (SDLA)
5750 and designated S502E(A), S503 or S508. These cards support the X.25,
5751 Frame Relay, and PPP protocols. If you have one or more of these
5752 cards, say Y to this option; you may then also want to read the file
5753 Documentation/networking/wanpipe.txt. The next questions will ask
5754 you about the protocols you want the driver to support.
5756 The driver will be compiled as a module ( = code which can be
5757 inserted in and removed from the running kernel whenever you want).
5758 The module will be called wanpipe.o. For general information about
5759 modules read Documentation/modules.txt.
5761 Maximum number of cards
5762 CONFIG_WANPIPE_CARDS
5763 Enter number of WANPIPE adapters installed in your machine. The
5764 driver can support up to 8 cards. You may enter more than you
5765 actually have if you plan to add more cards in the future without
5766 re-compiling the driver, but remember that in this case you'll waste
5767 some kernel memory (about 1K per card).
5769 WANPIPE X.25 support
5771 Say Y to this option if you are planning to connect a WANPIPE card
5772 to an X.25 network. You should then also have said Y to "CCITT X.25
5773 Packet Layer" and "LAPB Data Link Driver", above. If you say N, the
5774 X.25 support will not be included in the driver (saves about 16 KB
5777 WANPIPE Frame Relay support
5779 Say Y to this option if you are planning to connect a WANPIPE card
5780 to a frame relay network. You should then also have said Y to "Frame
5781 Relay (DLCI) support", above. If you say N, the frame relay
5782 support will not be included in the driver (saves about 16 KB of
5787 Say Y to this option if you are planning to connect a WANPIPE card
5788 to a leased line using Point-to-Point protocol (PPP). You should
5789 then also have said Y to "PPP (point-to-point) support", above. If
5790 you say N, the PPP support will not be included in the driver (saves
5791 about 16 KB of kernel memory).
5793 Cyclom 2X(tm) multiprotocol cards
5794 CONFIG_CYCLADES_SYNC
5795 Cyclom 2X from Cyclades Corporation (http://www.cyclades.com and
5796 http://www.cyclades.com.br; to browse the WWW, you need to have
5797 access to a machine on the Internet that has a program like lynx or
5798 netscape) is an intelligent multiprotocol WAN adapter with data
5799 transfer rates up to 512 Kbps). These cards support the X.25 and SNA
5800 related protocols. If you have one or more of these cards, say Y to
5801 this option. The next questions will ask you about the protocols you
5802 want the driver to support (for now only X.25 is supported).
5804 While no documentation is available at this time please grab the
5805 wanconfig tarball in http://www.conectiva.com.br/~acme/cycsyn-devel
5806 (with minor changes to make it compile with the current wanrouter
5807 include files; efforts are being made to use the original package
5808 available at ftp://ftp.sangoma.com).
5810 Feel free to contact me or the cycsyn-devel mailing list at
5811 acme@conectiva.com.br and cycsyn-devel@bazar.conectiva.com.br for
5812 aditional details, I hope to have documentation available as soon
5815 The driver will be compiled as a module ( = code which can be
5816 inserted in and removed from the running kernel whenever you want).
5817 The module will be called cyclomx.o. For general information about
5818 modules read Documentation/modules.txt.
5820 Cyclom 2X X.25 support
5822 Say Y to this option if you are planning to connect a Cyclom 2X card
5824 If you say N, the X.25 support will not be included in the driver
5825 (saves about 11 KB of kernel memory).
5827 Ethernet (10 or 100Mbit)
5829 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
5830 type of Local Area Network (LAN) in universities and companies.
5832 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
5833 coaxial cable, linking computers in a chain), 10BASE-T or twisted
5834 pair (10 Mbps over twisted pair cable, linking computers to central
5835 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
5836 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
5837 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
5838 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
5839 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
5840 Ethernet (1 Gbps over optical fiber or short copper links).
5842 If your Linux machine will be connected to an Ethernet and you have
5843 an Ethernet network interface card (NIC) installed in your computer,
5844 say Y here and read the Ethernet-HOWTO, available via FTP (user:
5845 anonymous) from ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. You will
5846 then also have to say Y to the driver for your particular NIC.
5848 Note that the answer to this question won't directly affect the
5849 kernel: saying N will just cause this configure script to skip all
5850 the questions about Ethernet network cards. If unsure, say N.
5852 Sun LANCE Ethernet support
5854 This is support for lance Ethernet cards on Sun workstations such as
5855 the SPARCstation IPC (any SPARC with a network interface 'le0' under
5858 This driver is also available as a module ( = code which can be
5859 inserted in and removed from the running kernel whenever you want).
5860 The module will be called lance.o. If you want to compile it as a
5861 module, say M here and read Documentation/modules.txt.
5863 Sun Intel Ethernet support
5865 This is support for the Intel Ethernet cards on some Sun
5866 workstations (all those with a network interface 'ie0' under SunOS).
5868 Western Digital/SMC cards
5869 CONFIG_NET_VENDOR_SMC
5870 If you have a network (Ethernet) card belonging to this class, say Y
5871 and read the Ethernet-HOWTO, available via FTP (user: anonymous) in
5872 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
5874 Note that the answer to this question doesn't directly affect the
5875 kernel: saying N will just cause this configure script to skip all
5876 the questions about Western Digital cards. If you say Y, you will be
5877 asked for your specific card in the following questions.
5881 If you have a network (Ethernet) card of this type, say Y and read
5882 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5883 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
5885 This driver is also available as a module ( = code which can be
5886 inserted in and removed from the running kernel whenever you want).
5887 The module will be called wd.o. If you want to compile it as a
5888 module, say M here and read Documentation/modules.txt as well as
5889 Documentation/networking/net-modules.txt.
5891 SMC Ultra MCA support
5893 If you have a network (Ethernet) card of this type and are running
5894 an MCA based system (PS/2), say Y and read
5895 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5896 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
5898 This driver is also available as a module ( = code which can be
5899 inserted in and removed from the running kernel whenever you want).
5900 The module will be called smc-mca.o. If you want to compile it as a
5901 module, say M here and read Documentation/modules.txt as well as
5902 Documentation/networking/net-modules.txt.
5906 If you have a network (Ethernet) card of this type, say Y and read
5907 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5908 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
5910 Important: There have been many reports that, with some motherboards
5911 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
5912 such as some BusLogic models) causes corruption problems with many
5913 operating systems. The Linux smc-ultra driver has a work-around for
5914 this but keep it in mind if you have such a SCSI card and have
5917 This driver is also available as a module ( = code which can be
5918 inserted in and removed from the running kernel whenever you want).
5919 The module will be called smc-ultra.o. If you want to compile it as
5920 a module, say M here and read Documentation/modules.txt as well as
5921 Documentation/networking/net-modules.txt.
5923 SMC Ultra32 EISA support
5925 If you have a network (Ethernet) card of this type, say Y and read
5926 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5927 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
5929 This driver is also available as a module ( = code which can be
5930 inserted in and removed from the running kernel whenever you want).
5931 The module will be called smc-ultra32.o. If you want to compile it
5932 as a module, say M here and read Documentation/modules.txt as well
5933 as Documentation/networking/net-modules.txt.
5937 This is support for the SMC9xxx based Ethernet cards. Choose this
5938 option if you have a DELL laptop with the docking station, or
5939 another SMC9192/9194 based chipset. Say Y if you want it compiled
5940 into the kernel, and read the file
5941 Documentation/networking/smc9.txt and the Ethernet-HOWTO, available
5942 via FTP (user: anonymous) in
5943 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
5945 This driver is also available as a module ( = code which can be
5946 inserted in and removed from the running kernel whenever you
5947 want). The module will be called smc9194.o. If you want to compile
5948 it as a module, say M here and read Documentation/modules.txt as
5949 well as Documentation/networking/net-modules.txt.
5953 This driver is for NE2000 compatible PCI cards. It will not work
5954 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
5955 support" below). If you have a PCI NE2000 network (Ethernet) card,
5956 say Y and read the Ethernet-HOWTO, available via FTP (user:
5957 anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
5959 This driver is also available as a module ( = code which can be
5960 inserted in and removed from the running kernel whenever you want).
5961 The module will be called ne2k-pci.o. If you want to compile it as a
5962 module, say M here and read Documentation/modules.txt as well as
5963 Documentation/networking/net-modules.txt.
5965 Racal-Interlan (Micom) NI cards
5966 CONFIG_NET_VENDOR_RACAL
5967 If you have a network (Ethernet) card belonging to this class, such
5968 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
5969 available via FTP (user: anonymous) in
5970 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
5972 Note that the answer to this question doesn't directly affect the
5973 kernel: saying N will just cause this configure script to skip all
5974 the questions about NI cards. If you say Y, you will be asked for
5975 your specific card in the following questions.
5979 If you have a network (Ethernet) card of this type, say Y and read
5980 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5981 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Note that this is still
5984 This driver is also available as a module ( = code which can be
5985 inserted in and removed from the running kernel whenever you want).
5986 The module will be called ni5010.o. If you want to compile it as a
5987 module, say M here and read Documentation/modules.txt as well as
5988 Documentation/networking/net-modules.txt.
5992 If you have a network (Ethernet) card of this type, say Y and read
5993 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5994 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 ni52.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.
6004 If you have a network (Ethernet) card of this type, say Y and read
6005 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6006 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6008 This driver is also available as a module ( = code which can be
6009 inserted in and removed from the running kernel whenever you want).
6010 The module will be called ni65.o. If you want to compile it as a
6011 module, say M here and read Documentation/modules.txt as well as
6012 Documentation/networking/net-modules.txt.
6014 RealTek 8129/8139 (not 8019/8029!) support
6016 This is a driver for the Fast Ethernet PCI network cards based on
6017 the RTL8129 and RTL8139 chips. If you have one of those, say Y and
6018 read the Ethernet-HOWTO, available via FTP (user: anonymous) in
6019 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6021 If you want to compile this driver as a module ( = code which can be
6022 inserted in and removed from the running kernel whenever you want),
6023 say M here and read Documentation/modules.txt. This is recommended.
6024 The module will be called rtl8139.o.
6026 Packet Engines Yellowfin Gigabit-NIC support
6028 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
6029 adapter. This adapter is used by the Beowulf Linux cluster project.
6030 See http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html for
6031 more information about this driver in particular and Beowulf in
6032 general (to browse the WWW, you need to have access to a machine on
6033 the Internet that has a program like lynx or netscape).
6035 If you want to compile this driver as a module ( = code which can be
6036 inserted in and removed from the running kernel whenever you want),
6037 say M here and read Documentation/modules.txt. This is recommended.
6038 The module will be called yellowfin.o.
6040 General Instruments Surfboard 1000
6042 This is a driver for the General Instrument SURFboard 1000 internal cable
6043 modem. This is an ISA card which is used by a number of cable TV companies
6044 to provide cable modem access. It's a one-way downstream-only cable modem,
6045 meaning that your upstream net link is provided by your regular phone modem.
6047 At present this driver only compiles as a module, so say M here if you
6048 have this card. Then read Documentation/networking/README.sb1000 for
6049 information on how to use this module, as it needs special ppp scripts for
6050 establishing a connection. Further documentation and the necessary scripts
6053 http://www.jacksonville.net/~fventuri/
6054 http://home.adelphia.net/~siglercm/sb1000.html
6055 http://linuxpower.cx/~cable/
6057 If you don't have this card, of course say N.
6059 Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support
6061 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
6062 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
6063 adapter. The driver allows for using the Jumbo Frame option (9000
6064 bytes/frame) however it requires that your switches can handle this
6065 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
6068 If you want to compile this driver as a module ( = code which can be
6069 inserted in and removed from the running kernel whenever you want),
6070 say M here and read Documentation/modules.txt. This is recommended.
6071 The module will be called acenic.o.
6073 Omit support for older Tigon I based AceNICs
6074 CONFIG_ACENIC_OMIT_TIGON_I
6075 Say Y here if you only have Tigon II based AceNICs and want to leave
6076 out support for the older Tigon I based cards which are no longer
6077 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
6078 version)). This will reduce the size of the driver object by
6079 app. 100KB. If you are not sure whether your card is a Tigon I or a
6080 Tigon II, say N here.
6082 The safe and default value for this is N.
6084 AMD LANCE and PCnet (AT1500 and NE2100) support
6086 If you have a network (Ethernet) card of this type, say Y and read
6087 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6088 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Some LinkSys cards are
6091 If you want to compile this driver as a module ( = code which can be
6092 inserted in and removed from the running kernel whenever you want),
6093 say M here and read Documentation/modules.txt. This is recommended.
6094 The module will be called lance.o.
6097 CONFIG_NET_VENDOR_3COM
6098 If you have a network (Ethernet) card belonging to this class, say Y
6099 and read the Ethernet-HOWTO, available via FTP (user: anonymous) in
6100 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6102 Note that the answer to this question doesn't directly affect the
6103 kernel: saying N will just cause this configure script to skip all
6104 the questions about 3COM cards. If you say Y, you will be asked for
6105 your specific card in the following questions.
6109 If you have a network (Ethernet) card of this type, say Y and read
6110 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6111 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Also, consider buying a
6112 new card, since the 3c501 is slow, broken, and obsolete: you will
6113 have problems. Some people suggest to ping ("man ping") a nearby
6114 machine every minute ("man cron") when using this card.
6116 This driver is also available as a module ( = code which can be
6117 inserted in and removed from the running kernel whenever you want).
6118 The module will be called 3c501.o. If you want to compile it as a
6119 module, say M here and read Documentation/modules.txt as well as
6120 Documentation/networking/net-modules.txt.
6124 If you have a network (Ethernet) card of this type, say Y and read
6125 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6126 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6128 This driver is also available as a module ( = code which can be
6129 inserted in and removed from the running kernel whenever you want).
6130 The module will be called 3c503.o. If you want to compile it as a
6131 module, say M here and read Documentation/modules.txt as well as
6132 Documentation/networking/net-modules.txt.
6136 Information about this network (Ethernet) card can be found in
6137 Documentation/networking/3c505.txt. If you have a card of this type,
6138 say Y and read the Ethernet-HOWTO, available via FTP (user:
6139 anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6141 If you want to compile this as a module ( = code which can be
6142 inserted in and removed from the running kernel whenever you want),
6143 say M here and read Documentation/modules.txt as well as
6144 Documentation/networking/net-modules.txt. The module will be called
6149 If you have a network (Ethernet) card of this type, say Y and read
6150 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6151 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6153 This driver is also available as a module ( = code which can be
6154 inserted in and removed from the running kernel whenever you want).
6155 The module will be called 3c507.o. If you want to compile it as a
6156 module, say M here and read Documentation/modules.txt as well as
6157 Documentation/networking/net-modules.txt.
6161 If you have a network (Ethernet) card of this type, say Y and read
6162 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6163 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6165 This driver is also available as a module ( = code which can be
6166 inserted in and removed from the running kernel whenever you want).
6167 The module will be called 3c523.o. If you want to compile it as a
6168 module, say M here and read Documentation/modules.txt as well as
6169 Documentation/networking/net-modules.txt.
6173 If you have a network (Ethernet) card of this type, say Y and read
6174 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6175 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6177 This driver is also available as a module ( = code which can be
6178 inserted in and removed from the running kernel whenever you want).
6179 The module will be called 3c527.o. If you want to compile it as a
6180 module, say M here and read Documentation/modules.txt as well as
6181 Documentation/networking/net-modules.txt.
6185 If you have a network (Ethernet) card belonging to the 3Com
6186 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
6187 via FTP (user: anonymous) in
6188 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6190 If your card is not working you may need to use the DOS
6191 setup disk to disable Plug & Play mode, and to select the default
6194 If you want to compile this as a module ( = code which can be
6195 inserted in and removed from the running kernel whenever you want),
6196 say M here and read Documentation/modules.txt as well as
6197 Documentation/networking/net-modules.txt. The module will be called
6200 3c590 series (592/595/597) "Vortex" support
6202 If you have a 3Com "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597)
6203 or "Boomerang" series (EtherLink XL 3c900 or 3c905) network
6204 (Ethernet) card, say Y and read the Ethernet-HOWTO, available via
6205 FTP (user: anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6206 More specific information is in Documentation/networking/vortex.txt
6207 and in the comments at the beginning of drivers/net/3c59x.c.
6209 If you want to compile this as a module ( = code which can be
6210 inserted in and removed from the running kernel whenever you want),
6211 say M here and read Documentation/modules.txt as well as
6212 Documentation/networking/net-modules.txt.
6216 If your network (Ethernet) card hasn't been mentioned yet and its
6217 bus system (that's the way the cards talks to the other components
6218 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
6219 Make sure you know the name of your card. Read the Ethernet-HOWTO,
6220 available via FTP (user: anonymous) in
6221 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. If unsure, say Y.
6223 Note that the answer to this question doesn't directly affect the
6224 kernel: saying N will just cause this configure script to skip all
6225 the remaining ISA network card questions. If you say Y, you will be
6226 asked for your specific card in the following questions.
6228 Generic ARCnet support
6230 If you have a network card of this type, say Y and check out the
6231 (arguably) beautiful poetry in Documentation/networking/arcnet.txt.
6233 You need both this driver, and the driver for the particular ARCnet
6234 chipset of your card. If you don't know, then it's probably a
6235 COM90xx type card, so say Y (or M) to "ARCnet COM90xx chipset
6238 You might also want to have a look at the Ethernet-HOWTO, available
6239 via FTP (user: anonymous) in
6240 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO (even though ARCnet is
6241 not really Ethernet).
6243 This driver is also available as a module ( = code which can be
6244 inserted in and removed from the running kernel whenever you want).
6245 The module will be called arcnet.o. If you want to compile it as a
6246 module, say M here and read Documentation/modules.txt as well as
6247 Documentation/networking/net-modules.txt.
6249 Enable arc0e (ARCnet "ether-encap" packet format)
6251 This allows you to use "Ethernet encapsulation" with your ARCnet
6252 card via the virtual arc0e device. You only need arc0e if you want
6253 to talk to nonstandard ARCnet software, specifically,
6254 DOS/Windows-style "NDIS" drivers. You do not need to say Y here to
6255 communicate with industry-standard RFC1201 implementations, like the
6256 arcether.com packet driver or most DOS/Windows ODI drivers. RFC1201
6257 is included automatically as the arc0 device. Please read the
6258 ARCnet documentation in Documentation/networking/arcnet.txt for more
6259 information about using arc0e and arc0s.
6261 Enable arc0s (ARCnet RFC1051 packet format)
6263 This allows you to use RFC1051 with your ARCnet card via the virtual
6264 arc0s device. You only need arc0s if you want to talk to ARCnet
6265 software complying with the "old" standard, specifically, the DOS
6266 arcnet.com packet driver, Amigas running AmiTCP, and some variants
6267 of NetBSD. You do not need to say Y here to communicate with
6268 industry-standard RFC1201 implementations, like the arcether.com
6269 packet driver or most DOS/Windows ODI drivers. RFC1201 is included
6270 automatically as the arc0 device. Please read the ARCnet
6271 documentation in Documentation/networking/arcnet.txt for more
6272 information about using arc0e and arc0s.
6274 ARCnet COM90xx (normal) chipset driver
6275 CONFIG_ARCNET_COM90xx
6276 This is the chipset driver for the standard COM90xx cards. If you
6277 have always used the old ARCnet driver without knowing what type of
6278 card you had, this is probably the one for you.
6280 This driver is also available as a module ( = code which can be
6281 inserted in and removed from the running kernel whenever you want).
6282 The module will be called com90xx.o. If you want to compile it as a
6283 module, say M here and read Documentation/modules.txt as well as
6284 Documentation/networking/net-modules.txt.
6286 ARCnet COM90xx (IO mapped) chipset driver
6287 CONFIG_ARCNET_COM90xxIO
6288 This is the chipset driver for the COM90xx cards, using them in
6289 IO-mapped mode instead of memory-mapped mode. This is slower than
6290 the normal driver. Only use it if your card doesn't support shared
6293 This driver is also available as a module ( = code which can be
6294 inserted in and removed from the running kernel whenever you want).
6295 The module will be called com90io.o. If you want to compile it as a
6296 module, say M here and read Documentation/modules.txt as well as
6297 Documentation/networking/net-modules.txt.
6299 ARCnet COM90xx (RIM I) chipset driver
6301 This is yet another chipset driver for the COM90xx cards, but this
6302 time only using memory-mapped mode, and no IO ports at all. This
6303 driver is completely untested, so if you have one of these cards,
6304 please mail David.Woodhouse@mvhi.com, especially if it works!
6306 This driver is also available as a module ( = code which can be
6307 inserted in and removed from the running kernel whenever you
6308 want). The module will be called arc-rimi.o. If you want to compile
6309 it as a module, say M here and read Documentation/modules.txt as
6310 well as Documentation/networking/net-modules.txt.
6312 ARCnet COM20020 chipset driver
6313 CONFIG_ARCNET_COM20020
6314 This is the driver for the new COM20020 chipset. It supports such
6315 things as promiscuous mode, so packet sniffing is possible, and
6316 extra diagnostic information.
6318 This driver is also available as a module ( = code which can be
6319 inserted in and removed from the running kernel whenever you want).
6320 The module will be called com20020.o. If you want to compile it as a
6321 module, say M here and read Documentation/modules.txt as well as
6322 Documentation/networking/net-modules.txt.
6324 Cabletron E21xx support
6326 If you have a network (Ethernet) card of this type, say Y and read
6327 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6328 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6330 This driver is also available as a module ( = code which can be
6331 inserted in and removed from the running kernel whenever you want).
6332 The module will be called e2100.o. If you want to compile it as a
6333 module, say M here and read Documentation/modules.txt as well as
6334 Documentation/networking/net-modules.txt.
6338 Support for CS89x0 chipset based Ethernet cards. If you have a
6339 network (Ethernet) card of this type, say Y and read the
6340 Ethernet-HOWTO, available via FTP (user: anonymous) in
6341 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO as well as
6342 Documentation/networking/cs89x0.txt.
6344 If you want to compile this as a module ( = code which can be
6345 inserted in and removed from the running kernel whenever you want),
6346 say M here and read Documentation/modules.txt as well as
6347 Documentation/networking/net-modules.txt. The module will be called
6352 If you have a network (Ethernet) card of this type, say Y and read
6353 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6354 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO as well as
6355 drivers/net/depca.c.
6357 If you want to compile this as a module ( = code which can be
6358 inserted in and removed from the running kernel whenever you want),
6359 say M here and read Documentation/modules.txt as well as
6360 Documentation/networking/net-modules.txt. The module will be called
6363 EtherWorks 3 support
6365 This driver supports the DE203, DE204 and DE205 network (Ethernet)
6366 cards. If this is for you, say Y and read
6367 Documentation/networking/ewrk3.txt in the kernel source as well as
6368 the Ethernet-HOWTO, available via FTP (user: anonymous) from
6369 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6371 If you want to compile this as a module ( = code which can be
6372 inserted in and removed from the running kernel whenever you want),
6373 say M here and read Documentation/modules.txt as well as
6374 Documentation/networking/net-modules.txt. The module will be called
6379 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
6380 is for you, read the Ethernet-HOWTO, available via FTP (user:
6381 anonymous) from ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6385 If you have a network (Ethernet) card of this type, say Y and read
6386 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6387 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6389 This driver is also available as a module ( = code which can be
6390 inserted in and removed from the running kernel whenever you want).
6391 If you want to compile it as a module, say M here and read
6392 Documentation/modules.txt as well as
6393 Documentation/networking/net-modules.txt. The module will be called
6396 FMV-181/182/183/184 support
6398 If you have a Fujitsu FMV-181/182/183/184 network (Ethernet) card,
6399 say Y and read the Ethernet-HOWTO, available via FTP (user:
6400 anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6402 If you use an FMV-183 or FMV-184 and it is not working, you may need
6403 to disable Plug & Play mode of the card.
6405 This driver is also available as a module ( = code which can be
6406 inserted in and removed from the running kernel whenever you want).
6407 The module will be called fmv18x.o. If you want to compile it as a
6408 module, say M here and read Documentation/modules.txt as well as
6409 Documentation/networking/net-modules.txt.
6411 EtherExpress PRO support
6413 If you have a network (Ethernet) card of this type, say Y. Note
6414 however that the EtherExpress PRO/100 Ethernet card has its own
6415 separate driver. Please read the Ethernet-HOWTO, available via FTP
6416 (user: anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6418 This driver is also available as a module ( = code which can be
6419 inserted in and removed from the running kernel whenever you want).
6420 The module will be called eepro.o. If you want to compile it as a
6421 module, say M here and read Documentation/modules.txt as well as
6422 Documentation/networking/net-modules.txt.
6424 EtherExpress support
6426 If you have an EtherExpress16 network (Ethernet) card, say Y and
6427 read the Ethernet-HOWTO, available via FTP (user: anonymous) in
6428 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Note that the Intel
6429 EtherExpress16 card used to be regarded as a very poor choice
6430 because the driver was very unreliable. We now have a new driver
6431 that should do better.
6433 If you want to compile this driver as a module ( = code which can be
6434 inserted in and removed from the running kernel whenever you want),
6435 say M here and read Documentation/modules.txt as well as
6436 Documentation/networking/net-modules.txt. The module will be called
6439 HP PCLAN+ (27247B and 27252A) support
6441 If you have a network (Ethernet) card of this type, say Y and read
6442 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6443 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6445 This driver is also available as a module ( = code which can be
6446 inserted in and removed from the running kernel whenever you want).
6447 The module will be called hp-plus.o. If you want to compile it as a
6448 module, say M here and read Documentation/modules.txt as well as
6449 Documentation/networking/net-modules.txt.
6451 HP PCLAN (27245 and other 27xxx series) support
6453 If you have a network (Ethernet) card of this type, say Y and read
6454 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6455 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6457 This driver is also available as a module ( = code which can be
6458 inserted in and removed from the running kernel whenever you want).
6459 The module will be called hp.o. If you want to compile it as a
6460 module, say M here and read Documentation/modules.txt as well as
6461 Documentation/networking/net-modules.txt.
6463 HP 10/100VG PCLAN (ISA, EISA, PCI) support
6465 If you have a network (Ethernet) card of this type, say Y and read
6466 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6467 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6469 If you want to compile this as a module ( = code which can be
6470 inserted in and removed from the running kernel whenever you want),
6471 say M here and read Documentation/modules.txt as well as
6472 Documentation/networking/net-modules.txt. The module will be called
6475 NE2000/NE1000 support
6477 If you have a network (Ethernet) card of this type, say Y and read
6478 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6479 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Many Ethernet cards
6480 without a specific driver are compatible with NE2000.
6482 If you have a PCI NE2000 card however, say N here and Y to "PCI
6483 NE2000 support", above. If you have a NE2000 card and are running on
6484 an MCA system (a bus system used on some IBM PS/2 computers and
6485 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
6488 This driver is also available as a module ( = code which can be
6489 inserted in and removed from the running kernel whenever you want).
6490 The module will be called ne.o. If you want to compile it as a
6491 module, say M here and read Documentation/modules.txt as well as
6492 Documentation/networking/net-modules.txt.
6496 If you have a network (Ethernet) card of this type, say Y and read
6497 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6498 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6500 NE/2 (ne2000 MCA version) support
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 This driver is also available as a module ( = code which can be
6507 inserted in and removed from the running kernel whenever you want).
6508 The module will be called ne2.o. If you want to compile it as a
6509 module, say M here and read Documentation/modules.txt as well as
6510 Documentation/networking/net-modules.txt.
6514 This are Micro Channel ethernet adapters. You need to set CONFIG_MCA
6515 to use this driver. It's both available as an in-kernel driver and
6516 as a module ( = code which can be inserted in and removed from the
6517 running kernel whenever you want). If you want to compile it as a module,
6518 say M here and read Documentation/modules.txt as well as
6519 Documentation/networking/net-modules.txt. If you plan to use more than
6520 one network card under linux, read the Multiple-Ethernet-mini-HOWTO,
6521 available from sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. Supported
6522 cards are the SKnet Junior MC2 and the SKnet MC2(+). Distinguishing
6523 both cards is done automatically. Note that using multiple boards
6524 of different type hasn't been tested with this driver.
6526 EISA, VLB, PCI and on board controllers
6528 This is another class of network cards which attach directly to the
6529 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
6530 available via FTP (user: anonymous) from
6531 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6533 Note that the answer to this question doesn't directly affect the
6534 kernel: saying N will just cause this configure script to skip all
6535 the questions about this class of network cards. If you say Y, you
6536 will be asked for your specific card in the following questions. If
6537 you are unsure, say Y.
6539 AMD PCnet32 (VLB and PCI) support
6541 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
6542 answer Y here and read the Ethernet-HOWTO, available via FTP (user:
6543 anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6545 This driver is also available as a module ( = code which can be
6546 inserted in and removed from the running kernel whenever you want).
6547 The module will be called pcnet32.o. If you want to compile it as a
6548 module, say M here and read Documentation/modules.txt as well as
6549 Documentation/networking/net-modules.txt.
6551 Ansel Communications EISA 3200 support
6553 If you have a network (Ethernet) card of this type, say Y and read
6554 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6555 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6557 This driver is also available as a module ( = code which can be
6558 inserted in and removed from the running kernel whenever you want).
6559 The module will be called ac3200.o. If you want to compile it as a
6560 module, say M here and read Documentation/modules.txt as well as
6561 Documentation/networking/net-modules.txt.
6563 Mylex EISA LNE390A/LNE390B support
6565 If you have a network (Ethernet) card of this type, say Y and read
6566 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6567 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6569 This driver is also available as a module ( = code which can be
6570 inserted in and removed from the running kernel whenever you want).
6571 The module will be called lne390.o. If you want to compile it as a
6572 module, say M here and read Documentation/modules.txt as well as
6573 Documentation/networking/net-modules.txt.
6575 Novell/Eagle/Microdyne NE3210 EISA support
6577 If you have a network (Ethernet) card of this type, say Y and read
6578 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6579 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Note that this driver
6580 will NOT WORK for NE3200 cards as they are completely different.
6582 This driver is also available as a module ( = code which can be
6583 inserted in and removed from the running kernel whenever you want).
6584 The module will be called ne3210.o. If you want to compile it as a
6585 module, say M here and read Documentation/modules.txt as well as
6586 Documentation/networking/net-modules.txt.
6588 Apricot Xen-II on board Ethernet
6590 If you have a network (Ethernet) controller of this type, say Y and
6591 read the Ethernet-HOWTO, available via FTP (user: anonymous) in
6592 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6594 If you want to compile this as a module ( = code which can be
6595 inserted in and removed from the running kernel whenever you want),
6596 say M here and read Documentation/modules.txt as well as
6597 Documentation/networking/net-modules.txt. The module will be called
6600 Generic DECchip & DIGITAL EtherWORKS PCI/EISA
6602 This is support for the DIGITAL series of PCI/EISA Ethernet cards.
6603 These include the DE425, DE434, DE435, DE450 and DE500 models. If
6604 you have a network card of this type, say Y and read the
6605 Ethernet-HOWTO, available via FTP (user: anonymous) in
6606 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. More specific
6607 information is contained in Documentation/networking/de4x5.txt.
6609 This driver is also available as a module ( = code which can be
6610 inserted in and removed from the running kernel whenever you want).
6611 The module will be called de4x5.o. If you want to compile it as a
6612 module, say M here and read Documentation/modules.txt as well as
6613 Documentation/networking/net-modules.txt.
6615 DECchip Tulip (dc21x4x) PCI support
6617 This driver is developed for the SMC EtherPower series Ethernet
6618 cards and also works with cards based on the DECchip
6619 21040/21041/21140 (Tulip series) chips. Some LinkSys PCI cards are
6620 of this type. (If your card is NOT SMC EtherPower 10/100 PCI
6621 (smc9332dst), you can also try the driver for "Generic DECchip"
6622 cards, above. However, most people with a network card of this type
6623 will say Y here.) Do read the Ethernet-HOWTO, available via FTP
6624 (user: anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6625 More specific information is contained in
6626 Documentation/networking/tulip.txt.
6628 This driver is also available as a module ( = code which can be
6629 inserted in and removed from the running kernel whenever you want).
6630 The module will be called tulip.o. If you want to compile it as a
6631 module, say M here and read Documentation/modules.txt as well as
6632 Documentation/networking/net-modules.txt.
6634 Digi Intl. RightSwitch support
6636 This is support for the Digi International RightSwitch series of
6637 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
6638 models. If you have a network card of this type, say Y and read the
6639 Ethernet-HOWTO, available via FTP (user: anonymous) in
6640 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. More specific
6641 information is contained in Documentation/networking/dgrs.txt.
6643 This driver is also available as a module ( = code which can be
6644 inserted in and removed from the running kernel whenever you want).
6645 The module will be called dgrs.o. If you want to compile it as a
6646 module, say M here and read Documentation/modules.txt as well as
6647 Documentation/networking/net-modules.txt.
6649 EtherExpress PRO/100 support
6650 CONFIG_EEXPRESS_PRO100
6651 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
6652 card, say Y and read the Ethernet-HOWTO, available via FTP (user:
6653 anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6655 This driver is also available as a module ( = code which can be
6656 inserted in and removed from the running kernel whenever you want).
6657 The module will be called eepro100.o. If you want to compile it as a
6658 module, say M here and read Documentation/modules.txt as well as
6659 Documentation/networking/net-modules.txt.
6661 ICL EtherTeam 16i/32 support
6663 If you have a network (Ethernet) card of this type, say Y and read
6664 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6665 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6667 This driver is also available as a module ( = code which can be
6668 inserted in and removed from the running kernel whenever you want).
6669 The module will be called eth16i.o. If you want to compile it as a
6670 module, say M here and read Documentation/modules.txt as well as
6671 Documentation/networking/net-modules.txt.
6673 TI ThunderLAN support (EXPERIMENTAL)
6675 If you have a PCI Ethernet network card based on the ThunderLAN chip
6676 which is supported by this driver, say Y and read the
6677 Ethernet-HOWTO, available via FTP (user: anonymous) in
6678 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6680 Devices currently supported by this driver are Compaq Netelligent,
6681 Compaq NetFlex and Olicom cards. Please read the file
6682 Documentation/networking/tlan.txt for more details.
6684 This driver is also available as a module ( = code which can be
6685 inserted in and removed from the running kernel whenever you want).
6686 The module will be called tlan.o. If you want to compile it as a
6687 module, say M here and read Documentation/modules.txt as well as
6688 Documentation/networking/net-modules.txt.
6690 Please email feedback to james.banks@caldera.com.
6694 If you have a VIA "rhine" based network card (Rhine-I (3043) or
6695 Rhine-2 (VT86c100A)), say Y here.
6697 This driver is also available as a module ( = code which can be
6698 inserted in and removed from the running kernel whenever you want).
6699 The module will be called via-rhine.o. If you want to compile it as
6700 a module, say M here and read Documentation/modules.txt as well as
6701 Documentation/networking/net-modules.txt.
6703 Racal-Interlan EISA ES3210 support
6705 If you have a network (Ethernet) card of this type, say Y and read
6706 the Ethernet-HOWTO, available via FTP (user: anonymous) in
6707 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6709 This driver is also available as a module ( = code which can be
6710 inserted in and removed from the running kernel whenever you want).
6711 The module will be called es3210.o. If you want to compile it as a
6712 module, say M here and read Documentation/modules.txt as well as
6713 Documentation/networking/net-modules.txt.
6715 SMC EtherPower II (EXPERIMENTAL)
6717 If you have an SMC EtherPower II 9432 PCI Ethernet network card
6718 which is based on the SMC83c170, say Y and read the Ethernet-HOWTO,
6719 available via FTP (user: anonymous) in
6720 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6722 This driver is also available as a module ( = code which can be
6723 inserted in and removed from the running kernel whenever you want).
6724 The module will be called epic100.o. If you want to compile it as a
6725 module, say M here and read Documentation/modules.txt as well as
6726 Documentation/networking/net-modules.txt.
6728 SGI Seeq ethernet controller support
6730 Say Y here if you have an Seeq based Ethernet network card. This is
6731 used in many Silicon Graphics machines.
6733 Zenith Z-Note support
6735 The Zenith Z-Note notebook computer has a built-in network
6736 (Ethernet) card, and this is the Linux driver for it. Note that the
6737 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
6738 by this driver. Read the Ethernet-HOWTO, available via FTP (user:
6739 anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6741 Pocket and portable adapters
6743 Cute little network (Ethernet) devices which attach to the parallel
6744 port ("pocket adapters"), commonly used with laptops. If you have
6745 one of those, say Y and read the Ethernet-HOWTO, available via FTP
6746 (user: anonymous) from ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6748 If you want to plug a network (or some other) card into the PCMCIA
6749 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
6750 credit card size extension cards used by all modern laptops), you
6751 need the pcmcia-cs package (location contained in the file
6752 Documentation/Changes) and you can say N here.
6754 Laptop users should read the Linux Laptop home page at
6755 http://www.cs.utexas.edu/users/kharker/linux-laptop/ (to browse the
6756 WWW, you need to have access to a machine on the Internet that has a
6757 program like lynx or netscape).
6759 Note that the answer to this question doesn't directly affect the
6760 kernel: saying N will just cause this configure script to skip all
6761 the questions about this class of network devices. If you say Y, you
6762 will be asked for your specific device in the following questions.
6764 AT-LAN-TEC/RealTek pocket adapter support
6766 This is a network (Ethernet) device which attaches to your parallel
6767 port. Read drivers/net/atp.c as well as the Ethernet-HOWTO,
6768 available via FTP (user: anonymous) from
6769 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO if you want to use this.
6770 If you intend to use this driver, you should have said N to the
6771 Parallel Printer support, because the two drivers don't like each
6774 D-Link DE600 pocket adapter support
6776 This is a network (Ethernet) device which attaches to your parallel
6777 port. Read Documentation/networking/DLINK.txt as well as the
6778 Ethernet-HOWTO, available via FTP (user: anonymous) from
6779 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO if you want to use this.
6780 It is possible to have several devices share a single parallel port
6781 and it is safe to compile the corresponding drivers into the kernel.
6783 If you want to compile this driver as a module however ( = code
6784 which can be inserted in and removed from the running kernel
6785 whenever you want), say M here and read Documentation/modules.txt.
6786 The module will be called de600.o.
6788 D-Link DE620 pocket adapter support
6790 This is a network (Ethernet) device which attaches to your parallel
6791 port. Read Documentation/networking/DLINK.txt as well as the
6792 Ethernet-HOWTO, available via FTP (user: anonymous) from
6793 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO if you want to use this.
6794 It is possible to have several devices share a single parallel port
6795 and it is safe to compile the corresponding drivers into the kernel.
6797 If you want to compile this driver as a module however ( = code
6798 which can be inserted in and removed from the running kernel
6799 whenever you want), say M here and read Documentation/modules.txt.
6800 The module will be called de620.o.
6802 Token Ring driver support
6804 Token Ring is IBM's way of communication on a local network; the
6805 rest of the world uses Ethernet. To participate on a Token Ring
6806 network, you need a special Token ring network card. If you are
6807 connected to such a Token Ring network and want to use your Token
6808 Ring card under Linux, say Y here and to the driver for your
6809 particular card below and read the Token-Ring mini-HOWTO, available
6810 via FTP (user:anonymous) from
6811 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Most people can say N
6814 IBM Tropic chipset based adapter support
6816 This is support for all IBM Token Ring cards that don't use DMA. If
6817 you have such a beast, say Y and read the Token-Ring mini-HOWTO,
6818 available via FTP (user:anonymous) from
6819 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6821 Warning: this driver will almost definitely fail if more than one
6822 active Token Ring card is present.
6824 This driver is also available as a module ( = code which can be
6825 inserted in and removed from the running kernel whenever you want).
6826 The module will be called ibmtr.o. If you want to compile it as a
6827 module, say M here and read Documentation/modules.txt.
6829 IBM Olympic chipset PCI adapter support
6831 This is support for all non-Lanstreamer IBM PCI Token Ring Cards.
6832 Specifically this is all IBM PCI, PCI Wake On Lan, PCI II, PCI II
6833 Wake On Lan, and PCI 100/16/4 adapters.
6835 If you have such an adapter, say Y and read the Token-Ring mini-HOWTO,
6836 available via FTP (user:anonymous) from
6837 ftp://metalab.unc/edu/pub/Linux/docs/HOWTO.
6839 This driver is also available as a module ( = code which can be
6840 inserted in and removed from the running kernel whenever you want).
6841 The module will will be called olympic.o. If you want to compile it as a
6842 module, say M here and read Documentation/modules.txt.
6844 Also read the linux/Documentation/networking/olympic.txt or check the
6845 Linux Token Ring Project site for the latest information at
6846 http://www.linuxtr.net
6848 SysKonnect adapter support
6850 This is support for all SysKonnect Token Ring cards, specifically
6851 SysKonnect TR4/16(+) ISA (SK-4190), SysKonnect TR4/16(+) PCI
6852 (SK-4590), SysKonnect TR4/16 PCI (SK-4591) adapters.
6854 If you have such an adapter and would like to use it, say Y or M and
6855 read the Token-Ring mini-HOWTO, available via FTP (user: anonymous)
6856 from ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6858 Also read the file linux/Documentation/networking/sktr.txt or check
6859 the Linux-SNA WWW site for the latest information at
6860 http://samba.anu.edu.au/linux-sna/documents/drivers/SysKonnect/
6862 Traffic Shaper (EXPERIMENTAL)
6864 The traffic shaper is a virtual network device that allows you to
6865 limit the rate of outgoing data flow over some other network
6866 device. See Documentation/networking/shaper.txt for more
6867 information. To set up and configure shaper devices, you need the
6868 shapecfg program, available via FTP (user: anonymous) from
6869 ftp://shadow.cabi.net/pub/Linux in the shaper package.
6871 This driver is also available as a module ( = code which can be
6872 inserted in and removed from the running kernel whenever you want).
6873 The module will be called shaper.o. If you want to compile it as a
6874 module, say M here and read Documentation/modules.txt. If unsure,
6879 Fiber Distributed Data Interface is a high speed local area network
6880 design; essentially a replacement for high speed Ethernet. FDDI can
6881 run over copper or fiber. If you are connected to such a network and
6882 want a driver for the FDDI card in your computer, say Y here (and
6883 then also Y to the driver for your FDDI card, below). Most people
6886 Digital DEFEA and DEFPA adapter support
6888 This is support for the DIGITAL series of EISA (DEFEA) and PCI
6889 (DEFPA) controllers which can connect you to a local FDDI network.
6891 HIgh Performance Parallel Interface support (EXPERIMENTAL)
6893 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
6894 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
6895 can run over copper (25m) or fiber (300m on multi-mode or 10km on
6896 single-mode). HIPPI networks are commonly used for clusters and to
6897 connect to super computers. If you are connected to a HIPPI network
6898 and have a HIPPI network card in your computer that you want to use
6899 under Linux, say Y here (you must also remember to enable the driver
6900 for your HIPPI card below). Most people will say N here.
6902 CERN HIPPI PCI adapter support
6904 Say Y here if this is your PCI HIPPI network card.
6906 This driver is also available as a module ( = code which can be
6907 inserted in and removed from the running kernel whenever you want).
6908 The module will be called cern_hippi.o. If you want to compile it as
6909 a module, say M here and read Documentation/modules.txt. If unsure,
6912 Essential RoadRunner HIPPI PCI adapter support
6914 Say Y here if this is your PCI HIPPI network card.
6916 This driver is also available as a module ( = code which can be
6917 inserted in and removed from the running kernel whenever you want).
6918 The module will be called rrunner.o. If you want to compile it as
6919 a module, say M here and read Documentation/modules.txt. If unsure,
6922 Use large TX/RX rings
6923 CONFIG_ROADRUNNER_LARGE_RINGS
6924 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
6925 of additional memory to allow for fastest operation, both for
6926 transmitting and receiving. This memory cannot be used by any other
6927 kernel code or by user space programs. Say Y here only if you have
6932 If you have an Acorn system with one of these (AKA25) network cards,
6933 you should say Y to this option if you wish to use it with Linux.
6935 Acorn/ANT Ether3 card
6937 If you have an Acorn system with one of these network cards, you
6938 should say Y to this option if you wish to use it with Linux.
6942 If you have an Acorn system with one of these network cards, you
6943 should say Y to this option if you wish to use it with Linux.
6945 EBSA-110 Ethernet interface
6946 CONFIG_ARM_AM79C961A
6947 If you wish to compile a kernel for the EBSA-110, then you should
6948 always answer Y to this.
6950 Support CDROM drives that are not SCSI or IDE/ATAPI
6951 CONFIG_CD_NO_IDESCSI
6952 If you have a CDROM drive that is neither SCSI nor IDE/ATAPI, say Y
6953 here, otherwise N. Read the CDROM-HOWTO, available via FTP (user:
6954 anonymous) from ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
6956 Note that the answer to this question doesn't directly affect the
6957 kernel: saying N will just cause this configure script to skip all
6958 the questions about these CDROM drives. If you are unsure what you
6959 have, say Y and find out whether you have one of the following
6962 For each of these drivers, a file Documentation/cdrom/<driver_name>
6963 exists. Especially in cases where you do not know exactly which kind
6964 of drive you have you should read there. Most of these drivers use a
6965 file drivers/cdrom/<driver_name>.h where you can define your
6966 interface parameters and switch some internal goodies.
6968 All these CDROM drivers are also usable as a module ( = code which
6969 can be inserted in and removed from the running kernel whenever you
6970 want). If you want to compile them as module, say M instead of Y and
6971 read Documentation/modules.txt.
6973 If you want to use any of these CDROM drivers, you also have to
6974 answer Y or M to "ISO 9660 CDROM filesystem support" below (this
6975 answer will get "defaulted" for you if you enable any of the Linux
6978 Sony CDU31A/CDU33A CDROM support
6980 These CDROM drives have a spring-pop-out caddyless drawer, and a
6981 rectangular green LED centered beneath it. NOTE: these CDROM drives
6982 will not be auto detected by the kernel at boot time; you have to
6983 provide the interface address as an option to the kernel at boot
6984 time as described in Documentation/cdrom/cdu31a or fill in your
6985 parameters into drivers/cdrom/cdu31a.c. Try "man bootparam" or
6986 see the documentation of your boot loader (lilo or loadlin) about
6987 how to pass options to the kernel. The lilo procedure is also
6988 explained in the SCSI-HOWTO.
6990 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
6991 filesystem support" below, because that's the filesystem used on
6994 This driver is also available as a module ( = code which can be
6995 inserted in and removed from the running kernel whenever you want).
6996 The module will be called cdu31a.o. If you want to compile it as a
6997 module, say M here and read Documentation/modules.txt.
6999 Standard Mitsumi [no XA/Multisession] CDROM support
7001 This is the older of the two drivers for the older Mitsumi models
7002 LU-005, FX-001 and FX-001D. This is not the right driver for the
7003 FX-001DE and the triple or quad speed models (all these are
7004 IDE/ATAPI models). Please also the file Documentation/cdrom/mcd.
7006 With the old LU-005 model, the whole drive chassis slides out for cd
7007 insertion. The FX-xxx models use a motorized tray type mechanism.
7008 Note that this driver does not support XA or MultiSession CDs
7009 (PhotoCDs). There is a new driver (next question) which can do
7010 this. If you want that one, say N here.
7012 If the driver doesn't work out of the box, you might want to have a
7013 look at drivers/cdrom/mcd.h.
7015 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7016 filesystem support" below, because that's the filesystem used on
7019 This driver is also available as a module ( = code which can be
7020 inserted in and removed from the running kernel whenever you want).
7021 The module will be called mcd.o. If you want to compile it as a
7022 module, say M here and read Documentation/modules.txt.
7024 IRQ channel for Mitsumi CD-ROM
7026 This allows you to specify the default value of the IRQ used by the
7027 driver. This setting can be overridden by passing the "mcd="
7028 parameter to the kernel at boot time (or at module load time if you
7029 said M to "Standard Mitsumi CDROM support").
7031 I/O base address for Mitsumi CD-ROM
7033 This allows you to specify the default value of the I/O base address
7034 used by the driver. This setting can be overridden by passing the
7035 "mcd=" parameter to the kernel at boot time (or at module load time
7036 if you said M to "Standard Mitsumi CDROM support").
7038 Mitsumi [XA/MultiSession] support
7040 Use this driver if you want to be able to read XA or MultiSession
7041 CDs (PhotoCDs) as well as ordinary CDs with your Mitsumi LU-005,
7042 FX-001 or FX-001D CDROM drive. In addition, this driver uses much
7043 less kernel memory than the old one, if that is a concern. This
7044 driver is able to support more than one drive, but each drive needs
7045 a separate interface card. Please read the file
7046 Documentation/cdrom/mcdx.
7048 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7049 filesystem support" below, because that's the filesystem used on
7052 This driver is also available as a module ( = code which can be
7053 inserted in and removed from the running kernel whenever you want).
7054 The module will be called mcdx.o. If you want to compile it as a
7055 module, say M here and read Documentation/modules.txt.
7057 Matsushita/Panasonic/Creative, Longshine, TEAC CDROM support
7059 This driver supports most of the drives which use the Panasonic or
7060 Sound Blaster interface. Please read the file
7061 Documentation/cdrom/sbpcd.
7063 The Matsushita CR-521, CR-522, CR-523, CR-562, CR-563 drives
7064 (sometimes labeled "Creative"), the Creative Labs CD200, the
7065 Longshine LCS-7260, the "IBM External ISA CDROM" (in fact a CR-56x
7066 model), the TEAC CD-55A fall under this category. Some other
7067 "electrically compatible" drives (Vertos, Genoa, some Funai models)
7068 are currently not supported; for the Sanyo H94A drive currently a
7069 separate driver (asked later) is responsible. Most drives have a
7070 uniquely shaped faceplate, with a caddyless motorized drawer, but
7071 without external brand markings. The older CR-52x drives have a
7072 caddy and manual loading/eject, but still no external markings. The
7073 driver is able to do an extended auto-probing for interface
7074 addresses and drive types; this can help to find facts in cases you
7075 are not sure, but can consume some time during the boot process if
7076 none of the supported drives gets found. Once your drive got found,
7077 you should enter the reported parameters into drivers/cdrom/sbpcd.h
7078 and set "DISTRIBUTION 0" there.
7080 This driver can support up to four CDROM controller cards, and each
7081 card can support up to four CDROM drives; if you say Y here, you
7082 will be asked how many controller cards you have. If compiled as a
7083 module, only one controller card (but with up to four drives) is
7086 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7087 filesystem support" below, because that's the filesystem used on
7090 This driver is also available as a module ( = code which can be
7091 inserted in and removed from the running kernel whenever you want).
7092 The module will be called sbpcd.o. If you want to compile it as a
7093 module, say M here and read Documentation/modules.txt.
7095 Matsushita/Panasonic, ... second CDROM controller support
7097 Say Y here only if you have two CDROM controller cards of this type
7098 (usually only if you have more than four drives). You should enter
7099 the parameters for the second, third and fourth interface card into
7100 linux/include/linux/sbpcd.h before compiling the new kernel. Read
7101 the file Documentation/cdrom/sbpcd.
7103 Aztech/Orchid/Okano/Wearnes/TXC/CyDROM CDROM support
7105 This is your driver if you have an Aztech CDA268-01A, Orchid
7106 CD-3110, Okano or Wearnes CDD110, Conrad TXC, or CyCDROM CR520 or
7107 CR540 CDROM drive. This driver -- just like all these CDROM drivers
7108 -- is NOT for CDROM drives with IDE/ATAPI interfaces, such as Aztech
7109 CDA269-031SE. Please read the file Documentation/cdrom/aztcd.
7111 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7112 filesystem support" below, because that's the filesystem used on
7115 This driver is also available as a module ( = code which can be
7116 inserted in and removed from the running kernel whenever you want).
7117 The module will be called aztcd.o. If you want to compile it as a
7118 module, say M here and read Documentation/modules.txt.
7120 Sony CDU535 CDROM support
7122 This is the driver for the older Sony CDU-535 and CDU-531 CDROM
7123 drives. Please read the file Documentation/cdrom/sonycd535.
7125 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7126 filesystem support" below, because that's the filesystem used on
7129 This driver is also available as a module ( = code which can be
7130 inserted in and removed from the running kernel whenever you want).
7131 The module will be called sonycd535.o. If you want to compile it as
7132 a module, say M here and read Documentation/modules.txt.
7134 Goldstar R420 CDROM support
7136 If this is your CDROM drive, say Y here. As described in the file
7137 linux/Documentation/cdrom/gscd, you might have to change a setting
7138 in the file linux/drivers/cdrom/gscd.h before compiling the
7139 kernel. Please read the file Documentation/cdrom/gscd.
7141 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7142 filesystem support" below, because that's the filesystem used on
7145 This driver is also available as a module ( = code which can be
7146 inserted in and removed from the running kernel whenever you want).
7147 The module will be called gscd.o. If you want to compile it as a
7148 module, say M here and read Documentation/modules.txt.
7150 Philips/LMS CM206 CDROM support
7152 If you have a Philips/LMS CDROM drive cm206 in combination with a
7153 cm260 host adapter card, say Y here. Please also read the file
7154 Documentation/cdrom/cm206.
7156 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7157 filesystem support" below, because that's the filesystem used on
7160 This driver is also available as a module ( = code which can be
7161 inserted in and removed from the running kernel whenever you want).
7162 The module will be called cm206.o. If you want to compile it as a
7163 module, say M here and read Documentation/modules.txt.
7165 Optics Storage DOLPHIN 8000AT CDROM support
7167 This is the driver for the 'DOLPHIN' drive with a 34-pin Sony
7168 compatible interface. It also works with the Lasermate CR328A. If
7169 you have one of those, say Y. This driver does not work for the
7170 Optics Storage 8001 drive; use the IDE-ATAPI CDROM driver for that
7171 one. Please read the file Documentation/cdrom/optcd.
7173 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7174 filesystem support" below, because that's the filesystem used on
7177 This driver is also available as a module ( = code which can be
7178 inserted in and removed from the running kernel whenever you want).
7179 The module will be called optcd.o. If you want to compile it as a
7180 module, say M here and read Documentation/modules.txt.
7182 Sanyo CDR-H94A CDROM support
7184 If this is your CDROM drive, say Y here and read the file
7185 Documentation/cdrom/sjcd. You should then also say Y or M to
7186 "ISO 9660 CDROM filesystem support" below, because that's the
7187 filesystem used on CDROMs.
7189 This driver is also available as a module ( = code which can be
7190 inserted in and removed from the running kernel whenever you want).
7191 The module will be called sjcd.o. If you want to compile it as a
7192 module, say M here and read Documentation/modules.txt.
7194 Soft configurable cdrom interface card support
7196 If you want to include boot-time initialization of any cdrom
7197 interface card that is software configurable, say Y here. Currently
7198 only the ISP16/MAD16/Mozart sound cards with built-in cdrom
7199 interfaces are supported.
7201 Note that the answer to this question doesn't directly affect the
7202 kernel: saying N will just cause this configure script to skip all
7203 the questions about these CDROM drives.
7205 ISP16/MAD16/Mozart soft configurable cdrom interface support
7207 These are sound cards with built-in cdrom interfaces using the OPTi
7208 82C928 or 82C929 chips. Say Y here to have them detected and
7209 possibly configured at boot time. In addition, You'll have to say Y
7210 to a driver for the particular cdrom drive you have attached to the
7211 card. Read Documentation/cdrom/isp16 for details.
7213 This driver is also available as a module ( = code which can be
7214 inserted in and removed from the running kernel whenever you want).
7215 The module will be called isp16.o. If you want to compile it as a
7216 module, say M here and read Documentation/modules.txt.
7220 If you say Y here, you will be able to set per user limits for disk
7221 usage (also called disk quotas). Currently, it works only for the
7222 ext2 filesystem. You need additional software in order to use quota
7223 support; for details, read the Quota mini-HOWTO, available via FTP
7224 (user: anonymous) in
7225 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini. Probably the quota
7226 support is only useful for multi user systems. If unsure, say N.
7228 Acorn's ADFS filesystem support (read only) (EXPERIMENTAL)
7230 The Advanced Disk File System is the filesystem used on floppy and
7231 hard disks by Acorn Systems. Currently in development, as a read-
7232 only driver for hard disks. These should be the first partition
7233 (eg. /dev/[sh]d?1) on each of your drives. If unsure, say N.
7237 Minix is a simple operating system used in many classes about OS's.
7238 The minix filesystem (method to organize files on a hard disk
7239 partition or a floppy disk) was the original filesystem for Linux,
7240 but has been superseded by the second extended filesystem ext2fs.
7241 You don't want to use the minix filesystem on your hard disk because
7242 of certain built-in restrictions, but it is sometimes found on older
7243 Linux floppy disks. This option will enlarge your kernel by about
7244 28 kB. If unsure, say N.
7246 If you want to compile this as a module ( = code which can be
7247 inserted in and removed from the running kernel whenever you want),
7248 say M here and read Documentation/modules.txt. The module will be
7249 called minix.o. Note that the filesystem of your root partition (the
7250 one containing the directory /) cannot be compiled as a module.
7252 Second extended fs support
7254 This is the de facto standard Linux filesystem (method to organize
7255 files on a storage device) for hard disks.
7257 You want to say Y here, unless you intend to use Linux exclusively
7258 from inside a DOS partition using the umsdos filesystem. The
7259 advantage of the latter is that you can get away without
7260 repartitioning your hard drive (which often implies backing
7261 everything up and restoring afterwards); the disadvantage is that
7262 Linux becomes susceptible to DOS viruses and that umsdos is somewhat
7263 slower than ext2fs. Even if you want to run Linux in this fashion,
7264 it might be a good idea to have ext2fs around: it enables you to
7265 read more floppy disks and facilitates the transition to a *real*
7266 Linux partition later. Another (rare) case which doesn't require
7267 ext2fs is a diskless Linux box which mounts all files over the
7268 network using NFS (in this case it's sufficient to say Y to "NFS
7269 filesystem support" below). Saying Y here will enlarge your kernel
7272 The Ext2fs-Undeletion mini-HOWTO, available via FTP (user:
7273 anonymous) from ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini,
7274 gives information about how to retrieve deleted files on ext2fs
7277 To change the behavior of ext2 filesystems, you can use the tune2fs
7278 utility ("man tune2fs"). To modify attributes of files and
7279 directories on ext2 filesystems, use chattr ("man chattr").
7281 Ext2fs partitions can be read from within DOS using the ext2tool
7282 command line tool package (available via FTP (user: anonymous) from
7283 ftp://metalab.unc.edu/pub/Linux/system/filesystems/ext2) and from
7284 within Windows NT using the ext2nt command line tool package from
7285 ftp://metalab.unc.edu/pub/Linux/utils/dos. Explore2fs is a graphical
7286 explorer for ext2fs partitions which runs on Windows 95 and Windows
7287 NT and includes experimental write support; it is available from
7288 http://jnewbigin-pc.it.swin.edu.au/Linux/Explore2fs.htm.
7290 If you want to compile this filesystem as a module ( = code which
7291 can be inserted in and removed from the running kernel whenever you
7292 want), say M here and read Documentation/modules.txt. The module
7293 will be called ext2.o. Be aware however that the filesystem of your
7294 root partition (the one containing the directory /) cannot be
7295 compiled as a module, and so this could be dangerous. Most everyone
7296 wants to say Y here.
7298 ISO 9660 CDROM filesystem support
7300 This is the standard filesystem used on CDROMs. It was previously
7301 known as "High Sierra Filesystem" and is called "hsfs" on other Unix
7302 systems. The so-called Rock-Ridge extensions which allow for long
7303 Unix filenames and symbolic links are also supported by this driver.
7304 If you have a CDROM drive and want to do more with it than just
7305 listen to audio CDs and watch its LEDs, say Y (and read
7306 Documentation/filesystems/isofs.txt and the CDROM-HOWTO, available
7307 via FTP (user: anonymous) from
7308 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO), thereby enlarging your
7309 kernel by about 27 kB; otherwise say N.
7311 If you want to compile this as a module ( = code which can be
7312 inserted in and removed from the running kernel whenever you want),
7313 say M here and read Documentation/modules.txt. The module will be
7316 Microsoft Joliet cdrom extensions
7318 Joliet is a Microsoft extension for the ISO 9660 CDROM filesystem
7319 which allows for long filenames in unicode format (unicode is the
7320 new 16 bit character code, successor to ASCII, which encodes the
7321 characters of almost all languages of the world; see
7322 http://www.unicode.org for more information; to browse the WWW, you
7323 need to have access to a machine on the Internet that has a program
7324 like lynx or netscape). Say Y here if you want to be able to read
7325 Joliet CDROMs under Linux.
7327 UDF Filesystem support
7329 This is the new filesystem used by some CDROMS and DVD drivers.
7330 Say Y if you intend to mount DVD discs or CDRWs written in packet mode,
7331 or if written to by other UDF utilities, such as DirectCD.
7333 This filesystem support is also available as a module ( = code which
7334 can be inserted in and removed from the running kernel whenever you
7335 want). The module is called udf.o. If you want to compile it as a
7336 module, say M here and read Documentation/modules.txt.
7340 UDF read-write support (EXPERIMENTAL)
7342 Say Y if you want to test write support for UDF filesystems.
7343 Due to lack of support for writing to CDR/CDRW's, this option
7344 is only supported for Hard Discs, DVD-RAM, and loopback files.
7348 If you want to use one of the FAT-based filesystems (the MS-DOS,
7349 VFAT (Windows 95) and UMSDOS (used to run Linux on top of an
7350 ordinary DOS partition) filesystems), then you must say Y or M here
7351 to include FAT support. You will then be able to mount partitions or
7352 diskettes with FAT-based filesystems and transparently access the
7353 files on them, i.e. MSDOS files will look and behave just like all
7356 This FAT support is not a filesystem in itself, it only provides the
7357 foundation for the other filesystems. You will have to say Y or M to
7358 at least one of "msdos fs support" or "vfat fs support" in order to
7361 Another way to read and write MSDOS floppies and hard drive
7362 partitions from within Linux (but not transparently) is with the
7363 mtools ("man mtools") program suite. This doesn't require the FAT
7366 It is now also becoming possible to read and write compressed FAT
7367 filesystems; read Documentation/filesystems/fat_cvf.txt for details.
7369 The FAT support will enlarge your kernel by about 24 kB. If unsure,
7372 If you want to compile this as a module however ( = code which can
7373 be inserted in and removed from the running kernel whenever you
7374 want), say M here and read Documentation/modules.txt. The module
7375 will be called fat.o. Note that if you compile the FAT support as a
7376 module, you cannot compile any of the FAT-based filesystems into the
7377 kernel -- they will have to be modules as well. The filesystem of
7378 your root partition (the one containing the directory /) cannot be a
7379 module, so don't say M here if you intend to use UMSDOS as your root
7384 This allows you to mount MSDOS partitions of your hard drive (unless
7385 they are compressed; to access compressed MSDOS partitions under
7386 Linux, you can either use the DOS emulator DOSEMU, described in the
7387 DOSEMU-HOWTO, available via FTP (user: anonymous) at
7388 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO, or try dmsdosfs in
7389 ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs. If you
7390 intend to use dosemu with a non-compressed MSDOS partition, say Y
7391 here) and MSDOS floppies. This means that file access becomes
7392 transparent, i.e. the MSDOS files look and behave just like all
7395 If you want to use umsdos, the Unix-like filesystem on top of DOS,
7396 which allows you to run Linux from within a DOS partition without
7397 repartitioning, you'll have to say Y or M here.
7399 If you have Windows 95 or Windows NT installed on your MSDOS
7400 partitions, you should use the VFAT filesystem (say Y to "vfat fs
7401 support" below), or you will not be able to see the long filenames
7402 generated by Windows 95 / Windows NT.
7404 This option will enlarge your kernel by about 7 kB. If unsure,
7405 answer Y. This will only work if you said Y to "fat fs support" as
7406 well. If you want to compile this as a module however ( = code which
7407 can be inserted in and removed from the running kernel whenever you
7408 want), say M here and read Documentation/modules.txt. The module
7409 will be called msdos.o.
7413 This option provides support for normal Windows filesystems with
7414 long filenames. That includes non-compressed FAT-based filesystems
7415 used by Windows 95, Windows 98, Windows NT 4.0, and mtools.
7417 You cannot use the VFAT filesystem for your Linux root partition
7418 (the one containing the directory /); use UMSDOS instead if you
7419 want to run Linux from within a DOS partition (i.e. say Y to
7420 "umsdos: Unix like fs on top of std MSDOS fs", below).
7422 The VFAT support enlarges your kernel by about 10 kB and it only
7423 works if you said Y to the "fat fs support" above. Please read the
7424 file Documentation/filesystems/vfat.txt for details. If unsure,
7427 If you want to compile this as a module ( = code which can be
7428 inserted in and removed from the running kernel whenever you want),
7429 say M here and read Documentation/modules.txt. The module will be
7432 umsdos: Unix like fs on top of std MSDOS fs
7434 Say Y here if you want to run Linux from within an existing DOS
7435 partition of your hard drive. The advantage of this is that you can
7436 get away without repartitioning your hard drive (which often implies
7437 backing everything up and restoring afterwards) and hence you're
7438 able to quickly try out Linux or show it to your friends; the
7439 disadvantage is that Linux becomes susceptible to DOS viruses and
7440 that UMSDOS is somewhat slower than ext2fs. Another use of UMSDOS
7441 is to write files with long unix filenames to MSDOS floppies; it
7442 also allows Unix-style softlinks and owner/permissions of files on
7443 MSDOS floppies. You will need a program called umssync in order to
7444 make use of umsdos; read Documentation/filesystems/umsdos.txt.
7446 This option enlarges your kernel by about 25 kB and it only works if
7447 you said Y to both "fat fs support" and "msdos fs support" above. If
7448 you want to compile this as a module ( = code which can be inserted
7449 in and removed from the running kernel whenever you want), say M
7450 here and read Documentation/modules.txt. The module will be called
7451 umsdos.o. Note that the filesystem of your root partition (the one
7452 containing the directory /) cannot be a module, so saying M could be
7453 dangerous. If unsure, say N.
7455 /proc filesystem support
7457 This is a virtual filesystem providing information about the status
7458 of the system. "Virtual" means that it doesn't take up any space on
7459 your hard disk: the files are created on the fly by the kernel when
7460 you try to access them. Also, you cannot read the files with older
7461 version of the program less: you need to use more or cat.
7463 It's totally cool; for example, "cat /proc/interrupts" gives
7464 information about what the different IRQs are used for at the moment
7465 (there is a small number of Interrupt ReQuest lines in your computer
7466 that are used by the attached devices to gain the CPU's attention --
7467 often a source of trouble if two devices are mistakenly configured
7468 to use the same IRQ).
7470 The /proc filesystem is explained in the file
7471 Documentation/proc.txt, in the Kernel Hacker's Guide at
7472 http://www.redhat.com:8080/HyperNews/get/khg.html on the WWW (to
7473 browse the WWW, you need to have access to a machine on the Internet
7474 that has a program like lynx or netscape), and also on the proc(8)
7475 manpage ("man 8 proc").
7477 This option will enlarge your kernel by about 67 KB. Several
7478 programs depend on this, so everyone should say Y here.
7480 NFS filesystem support
7482 If you are connected to some other (usually local) Unix computer
7483 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
7484 on that computer (the NFS server) using the Network File Sharing
7485 protocol, say Y. "Mounting files" means that the client can access
7486 the files with usual UNIX commands as if they were sitting on the
7487 client's hard disk. For this to work, the server must run the
7488 programs nfsd and mountd (but does not need to have NFS filesystem
7489 support enabled in its kernel). NFS is explained in the Network
7490 Administrator's Guide, available via FTP (user: anonymous) in
7491 ftp://metalab.unc.edu/pub/Linux/docs/LDP, on its man page: "man
7492 nfs", and in the NFS-HOWTO.
7494 A superior but less widely used alternative to NFS is provided by
7495 the Coda filesystem; see "Coda filesystem support" below.
7497 If you say Y here, you should have said Y to TCP/IP networking also.
7498 This option would enlarge your kernel by about 27 kB.
7500 This filesystem is also available as a module ( = code which can be
7501 inserted in and removed from the running kernel whenever you want).
7502 The module is called nfs.o. If you want to compile it as a module,
7503 say M here and read Documentation/modules.txt.
7505 If you are configuring a diskless machine which will mount its root
7506 filesystem over NFS at boot time, say Y here and to "IP: kernel
7507 level autoconfiguration" above and to "Root file system on NFS"
7508 below. You cannot compile this driver as a module in this case.
7509 There are two packages designed for booting diskless machines over
7510 the net: netboot and etherboot, both available via FTP from
7511 ftp://metalab.unc.edu/pub/Linux/system/boot/ethernet/ .
7513 If you don't know what all this is about, say N.
7515 Root file system on NFS
7517 If you want your Linux box to mount its whole root filesystem (the
7518 one containing the directory /) from some other computer over the
7519 net via NFS (presumably because your box doesn't have a hard disk),
7520 say Y. Read Documentation/nfsroot.txt for details. It is likely that
7521 in this case, you also want to say Y to "IP: kernel level
7522 autoconfiguration" so that your box can discover its network address
7525 Most people say N here.
7529 If you want your Linux box to act as a NFS *server*, so that other
7530 computers on your local network which support NFS can access certain
7531 directories on your box transparently, you have two options: you can
7532 use the self-contained user space program nfsd, in which case you
7533 should say N here, or you can say Y and use this new experimental
7534 kernel based NFS server. The advantage of the kernel based solution
7535 is that it is faster; it might not be completely stable yet, though.
7537 In either case, you will need support software; the respective
7538 locations are given in the file Documentation/Changes in the NFS
7541 Please read the NFS-HOWTO, available via FTP (user: anonymous) from
7542 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
7544 The NFS server is also available as a module ( = code which can be
7545 inserted in and removed from the running kernel whenever you want).
7546 The module is called nfsd.o. If you want to compile it as a module,
7547 say M here and read Documentation/modules.txt. If unsure, say N.
7549 Emulate Sun NFS daemon
7551 If you would like for the server to allow clients to access
7552 directories that are mount points on the local filesystem (this is
7553 how nfsd behaves on Sun systems), say yes here. If unsure, say N.
7555 OS/2 HPFS filesystem support (read/write)
7557 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
7558 is the filesystem used for organizing files on OS/2 hard disk
7559 partitions. Say Y if you want to be able to read and write files
7560 on an OS/2 HPFS partition of your hard drive. OS/2 floppies however
7561 are in regular MSDOS format, so you don't need this option in order
7562 to be able to read them. Read Documentation/filesystems/hpfs.txt.
7564 Write support is new and experimental. I don't think it's so
7565 "experimental" that it corrupts disks. (but you know: "There's no
7566 warranty") There are many checks and filesystem is remounted read-only
7567 if any inconsistency found. I use it quite long time and it works.
7569 This driver may not be able to write to HPFS386 disks on Warp server.
7570 HPFS386 on Warp client seems to work ok. If some unknown HPFS386
7571 structures are deteced, they are not destroyed and filesystem is
7572 remounted read-only.
7574 This filesystem 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 is called hpfs.o. If you want to compile it as a module,
7577 say M here and read Documentation/modules.txt. If unsure, say N.
7579 Windows NT NTFS support (read only)
7581 NTFS is the file system of Microsoft Windows NT. Say Y if you want
7582 to get read access to files on NTFS partitions of your hard drive.
7583 The Linux NTFS driver supports most of the mount options of the VFAT
7584 driver, see Documentation/filesystems/ntfs.txt. Saying Y here will
7585 give you read-only access to NTFS partitions.
7587 This code is also available as a module ( = code which can be
7588 inserted in and removed from the running kernel whenever you want).
7589 The module will be called ntfs.o. If you want to compile it as a
7590 module, say M here and read Documentation/modules.txt.
7592 NTFS read-write support (experimental)
7594 If you say Y here, you will (hopefully) be able to write to NTFS
7595 file systems as well as read from them. The read-write support
7596 in NTFS is far from being complete and is not well tested. If you
7597 enable this, back up your NTFS volume first since it may get
7602 System V and Coherent filesystem support
7604 SCO, Xenix and Coherent are commercial Unix systems for Intel
7605 machines. Saying Y here would allow you to read to and write from
7606 their floppies and hard disk partitions.
7608 If you have floppies or hard disk partitions like that, it is likely
7609 that they contain binaries from those other Unix systems; in order
7610 to run these binaries, you will want to install iBCS2 (Intel Binary
7611 Compatibility Standard is a kernel module which lets you run SCO,
7612 Xenix, Wyse, UnixWare, Dell Unix and System V programs under Linux
7613 and is often needed to run commercial software that's only available
7614 for those systems. It's available via FTP (user: anonymous) from
7615 ftp://tsx-11.mit.edu/pub/linux/BETA).
7617 If you only intend to mount files from some other Unix over the
7618 network using NFS, you don't need the System V filesystem support
7619 (but you need NFS filesystem support obviously).
7621 Note that this option is generally not needed for floppies, since a
7622 good portable way to transport files and directories between unixes
7623 (and even other operating systems) is given by the tar program ("man
7624 tar" or preferably "info tar"). Note also that this option has
7625 nothing whatsoever to do with the option "System V IPC". Read about
7626 the System V filesystem in Documentation/filesystems/sysv-fs.txt.
7627 Saying Y here will enlarge your kernel by about 34 KB.
7629 If you want to compile this as a module ( = code which can be
7630 inserted in and removed from the running kernel whenever you want),
7631 say M here and read Documentation/modules.txt. The module will be
7634 If you haven't heard about all of this before, it's safe to say N.
7636 Amiga FFS filesystem support
7638 The Fast File System (FFS) is the common filesystem used on hard
7639 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
7640 if you want to be able to read and write files from and to an Amiga
7641 FFS partition on your hard drive. Amiga floppies however cannot be
7642 read with this driver due to an incompatibility of the floppy
7643 controller used in an Amiga and the standard floppy controller in
7644 PCs and workstations. Read Documentation/filesystems/affs.txt and
7647 With this driver you can also mount disk files used by Bernd
7648 Schmidt's Un*X Amiga Emulator (http://www.freiburg.linux.de/~uae/;
7649 to browse the WWW, you need to have access to a machine on the
7650 Internet that has a program like lynx or netscape). If you want to
7651 do this, you will also need to say Y or M to "Loop device support",
7654 This filesystem is also available as a module ( = code which can be
7655 inserted in and removed from the running kernel whenever you want).
7656 The module is called affs.o. If you want to compile it as a module,
7657 say M here and read Documentation/modules.txt. If unsure, say N.
7659 Apple Macintosh filesystem support (experimental)
7661 If you say Y here, you will be able to mount Macintosh-formatted
7662 floppy disks and hard drive partitions with full read-write access.
7663 Please read fs/hfs/HFS.txt to learn about the available mount
7666 This filesystem support is also available as a module ( = code which
7667 can be inserted in and removed from the running kernel whenever you
7668 want). The module is called hfs.o. If you want to compile it as a
7669 module, say M here and read Documentation/modules.txt.
7671 ROM filesystem support
7673 This is a very small read-only filesystem mainly intended for
7674 initial ram disks of installation disks, but it could be used for
7675 other read-only media as well. Read
7676 Documentation/filesystems/romfs.txt for details.
7678 This filesystem support is also available as a module ( = code which
7679 can be inserted in and removed from the running kernel whenever you
7680 want). The module is called romfs.o. If you want to compile it as a
7681 module, say M here and read Documentation/modules.txt.
7683 If you don't know whether you need it, then you don't need it:
7686 QNX filesystem support (EXPERIMENTAL)
7688 This is the filesystem used by the operating system QNX 4. Say Y if
7689 you intend to mount QNX hard disks or floppies. Unless you say Y to
7690 "QNXFS read-write support" below, you will only be able to read
7693 This filesystem support is also available as a module ( = code which
7694 can be inserted in and removed from the running kernel whenever you
7695 want). The module is called qnx4.o. If you want to compile it as a
7696 module, say M here and read Documentation/modules.txt.
7700 QNXFS read-write support (FOR TESTING ONLY)
7702 Say Y if you want to test write support for QNX filesystems.
7704 Kernel automounter support
7706 The automounter is a tool to automatically mount remote filesystems
7707 on demand. This implementation is partially kernel-based to reduce
7708 overhead in the already-mounted case; this is unlike the BSD
7709 automounter (amd), which is a pure user space daemon.
7711 To use the automounter you need the user-space tools from
7712 ftp://ftp.kernel.org/pub/linux/daemons/autofs; you also want to
7713 answer Y to "NFS filesystem support", below.
7715 If you want to compile this as a module ( = code which can be
7716 inserted in and removed from the running kernel whenever you want),
7717 say M here and read Documentation/modules.txt. The module will be
7720 If you are not a part of a fairly large, distributed network, you
7721 probably do not need an automounter, and can say N here.
7723 UFS filesystem support
7725 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
7726 OpenBSD and NeXTstep) use a filesystem called UFS. Some System V
7727 Unixes can create and mount hard disk partitions and diskettes using
7728 this filesystem as well. Saying Y here will allow you to read from
7729 these partitions; if you also want to write to them, say Y to the
7730 experimental "UFS filesystem write support", below. Please read the
7731 file Documentation/filesystems/ufs.txt for more information.
7733 If you only intend to mount files from some other Unix over the
7734 network using NFS, you don't need the UFS filesystem support (but
7735 you need NFS filesystem support obviously).
7737 Note that this option is generally not needed for floppies, since a
7738 good portable way to transport files and directories between unixes
7739 (and even other operating systems) is given by the tar program ("man
7740 tar" or preferably "info tar").
7742 When accessing NeXTstep files, you may need to convert them from the
7743 NeXT character set to the Latin1 character set; use the program
7744 recode ("info recode") for this purpose.
7746 If you want to compile the UFS filesystem support as a module ( =
7747 code which can be inserted in and removed from the running kernel
7748 whenever you want), say M here and read Documentation/modules.txt.
7749 The module will be called ufs.o.
7751 If you haven't heard about all of this before, it's safe to say N.
7753 UFS filesystem write support (experimental)
7755 Say Y here if you want to try writing to UFS partitions. This is
7756 experimental, so you should back up your UFS partitions beforehand.
7758 EFS filesystem support (experimental)
7760 EFS is the filesystem used for CDROMs and filesystems by SGI's IRIX.
7761 This implementation only offers read-only access. If you don't know
7762 what all this is about, it's safe to say N. For more information
7763 about EFS see its homepage at http://aeschi.ch.eu.org/efs/.
7765 SGI disklabel support
7766 CONFIG_SGI_DISKLABEL
7767 Say Y to this only if you plan on mounting disks with SGI disklabels.
7768 This is not required to mount EFS-format CDROMs.
7770 EFS filesystem support (experimental)
7772 EFS is the filesystem used for CDROMs and filesystems by SGI's IRIX.
7773 This implementation only offers read-only access. If you don't know
7774 what all this is about, it's safe to say N. For more information
7775 about EFS see it's homepage at http://aeschi.ch.eu.org/efs.
7777 SGI disklabel support
7778 CONFIG_SGI_DISKLABEL
7779 Say Y to this only if you plan on mounting disks with SGI disklabels.
7780 This is not required to mount EFS-format CDROMs.
7782 BSD disklabel (FreeBSD partition tables) support
7783 CONFIG_BSD_DISKLABEL
7784 FreeBSD uses its own hard disk partition scheme on your PC. It
7785 requires only one entry in the primary partition table of your disk
7786 and manages it similarly to DOS extended partitions, putting in its
7787 first sector a new partition table in BSD disklabel format. Saying Y
7788 here allows you to read these disklabels and further mount FreeBSD
7789 partitions from within Linux if you have also said Y to "UFS
7790 filesystem support", above. If you don't know what all this is
7793 SMD disklabel (Sun partition tables) support
7794 CONFIG_SMD_DISKLABEL
7795 Like most systems, SunOS uses its own hard disk partition table
7796 format, incompatible with all others. Saying Y here allows you to
7797 read these partition tables and further mount SunOS disks from
7798 within Linux if you have also said Y to "UFS filesystem support",
7799 above. This is mainly used to carry data from a SPARC under SunOS to
7800 your Linux box via a removable medium like magneto-optical or ZIP
7801 drives; note however that a good portable way to transport files and
7802 directories between unixes (and even other operating systems) is
7803 given by the tar program ("man tar" or preferably "info tar"). If
7804 you don't know what all this is about, say N.
7806 Solaris (x86) partition table support
7807 CONFIG_SOLARIS_X86_PARTITION
7808 Like most systems, Solaris x86 uses its own hard disk partition
7809 table format, incompatible with all others. Saying Y here allows you
7810 to read these partition tables and further mount Solaris x86 disks
7811 from within Linux if you have also said Y to "UFS filesystem
7814 ADFS filesystem support (read only) (EXPERIMENTAL)
7816 The Acorn Disc Filing System is the standard filesystem of the
7817 RiscOS operating system which runs on Acorn's ARM-based Risc PC
7818 systems and the Acorn Archimedes range of machines. If you say Y
7819 here, Linux will be able to read from ADFS partitions on hard drives
7820 and from ADFS-formatted floppy discs.
7822 The ADFS partition should be the first partition (i.e.,
7823 /dev/[hs]d?1) on each of your drives.
7825 This code is also available as a module called adfs.o ( = code which
7826 can be inserted in and removed from the running kernel whenever you
7827 want). If you want to compile it as a module, say M here and read
7828 Documentation/modules.txt.
7832 /dev/pts filesystem for Unix98 PTYs
7834 You should say Y here if you said Y to "Unix98 PTY support" above.
7835 You'll then get a virtual filesystem which can be mounted on
7836 /dev/pts with "mount -t devpts". This, together with the pseudo
7837 terminal master multiplexer /dev/ptmx, is used for pseudo terminal
7838 support as described in The Open Group's Unix98 standard: in order
7839 to acquire a pseudo terminal, a process opens /dev/ptmx; the number
7840 of the pseudo terminal is then made available to the process and the
7841 pseudo terminal slave can be accessed as /dev/pts/<number>. What was
7842 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
7844 The GNU C library glibc 2.1 contains the requisite support for this
7845 mode of operation; you also need client programs that use the Unix98
7848 UnixWare slices support (EXPERIMENTAL)
7849 CONFIG_UNIXWARE_DISKLABEL
7850 Like some systems, UnixWare uses its own slice table inside a
7851 partition (VTOC - Virtual Table of Contents). Its format is
7852 incompatible with all other OSes. Saying Y here allows you to read
7853 VTOC and further mount UnixWare partitions read-only from within
7854 Linux if you have also said Y to "UFS filesystem support" or "System
7855 V and Coherent filesystem support", above.
7857 This is mainly used to carry data from a UnixWare box to your
7858 Linux box via a removable medium like magneto-optical, ZIP or
7859 removable IDE drives. Note, however, that a good portable way to
7860 transport files and directories between unixes (and even other
7861 operating systems) is given by the tar program ("man tar" or
7862 preferably "info tar").
7864 If you don't know what all this is about, say N.
7866 Macintosh partition map support
7867 CONFIG_MAC_PARTITION
7868 Say Y here if you want your Linux system to be able to read the
7869 partition tables of Macintosh hard drives, and thus use partitions
7872 SMB filesystem support (to mount Windows shares etc...)
7874 SMB (Server Message Block) is the protocol Windows for Workgroups
7875 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
7876 files and printers over local networks. Saying Y here allows you to
7877 mount their filesystems (often called "shares" in this context) and
7878 access them just like any other Unix directory. Currently, this
7879 works only if the Windows machines use TCP/IP as the underlying
7880 transport protocol, and not NetBEUI. For details, read
7881 Documentation/filesystems/smbfs.txt and the SMB-HOWTO, available via
7882 FTP (user: anonymous) from
7883 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
7885 Note: if you just want your box to act as an SMB *server* and make
7886 files and printing services available to Windows clients (which need
7887 to have a TCP/IP stack), you don't need to say Y here; you can use
7888 the program samba (available via FTP (user: anonymous) in
7889 ftp://metalab.unc.edu/pub/Linux/system/network/samba) for that.
7891 General information about how to connect Linux, Windows machines and
7892 Macs is on the WWW at http://www.eats.com/linux_mac_win.html (to
7893 browse the WWW, you need to have access to a machine on the Internet
7894 that has a program like lynx or netscape).
7896 If you want to compile the SMB support as a module ( = code which
7897 can be inserted in and removed from the running kernel whenever you
7898 want), say M here and read Documentation/modules.txt. The module
7899 will be called smbfs.o. Most people say N, however.
7901 Coda filesystem support
7903 Coda is an advanced network filesystem, similar to NFS in that it
7904 enables you to mount filesystems of a remote server and access them
7905 with regular Unix commands as if they were sitting on your hard
7906 disk. Coda has several advantages over NFS: support for disconnected
7907 operation (e.g. for laptops), read/write server replication,
7908 security model for authentication and encryption, persistent client
7909 caches and write back caching.
7911 If you say Y here, your Linux box will be able to act as a Coda
7912 *client*. You will need user level code as well, both for the client
7913 and server. Servers are currently user level, i.e. need no kernel
7914 support. Please read Documentation/filesystems/coda.txt and check
7915 out the Coda home page http://www.coda.cs.cmu.edu (to browse the
7916 WWW, you need to have access to a machine on the Internet that has a
7917 program like lynx or netscape).
7919 If you want to compile the coda client support as a module ( = code
7920 which can be inserted in and removed from the running kernel
7921 whenever you want), say M here and read Documentation/modules.txt.
7922 The module will be called coda.o.
7924 NCP filesystem support (to mount NetWare volumes)
7926 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
7927 used by Novell NetWare clients to talk to file servers. It is to IPX
7928 what NFS is to TCP/IP, if that helps. Saying Y here allows you to
7929 mount NetWare file server volumes and to access them just like any
7930 other Unix directory. For details, please read the file
7931 Documentation/filesystems/ncpfs.txt in the kernel source and the
7932 IPX-HOWTO on ftp://metalab.unc.edu/pub/Linux/docs/howto.
7934 You do not have to say Y here if you want your Linux box to act as a
7935 file *server* for Novell NetWare clients.
7937 General information about how to connect Linux, Windows machines and
7938 Macs is on the WWW at http://www.eats.com/linux_mac_win.html (to
7939 browse the WWW, you need to have access to a machine on the Internet
7940 that has a program like lynx or netscape).
7942 If you want to compile this as a module ( = code which can be
7943 inserted in and removed from the running kernel whenever you want),
7944 say M here and read Documentation/modules.txt. The module will be
7945 called ncpfs.o. Say N unless you are connected to a Novell network.
7948 CONFIG_NCPFS_PACKET_SIGNING
7949 NCP allows packets to be signed for stronger security. If you want
7950 security, say Y. Normal users can leave it off. To be able to use
7951 packet signing you must use ncpfs > 2.0.12.
7953 Proprietary file locking
7954 CONFIG_NCPFS_IOCTL_LOCKING
7955 Allows locking of records on remote volumes. Say N unless you have
7956 special applications which are able to utilize this locking scheme.
7958 Clear remove/delete inhibit when needed
7960 Allows manipulation of files flagged as Delete or Rename Inhibit. To
7961 use this feature you must mount volumes with the ncpmount parameter
7962 "-s" (ncpfs-2.0.12 and newer). Say Y unless you are not mounting
7963 volumes with -f 444.
7965 Use NFS namespace when available
7967 Allows you to utilize NFS namespace on NetWare servers. It brings
7968 you case sensitive filenames. Say Y. You can disable it at
7969 mount-time with the `-N nfs' parameter of ncpmount.
7971 Use OS2/LONG namespace when available
7973 Allows you to utilize OS2/LONG namespace on NetWare servers.
7974 Filenames in this namespace are limited to 255 characters, they are
7975 case insensitive, and case in names is preserved. Say Y. You can
7976 disable it at mount time with the -N os2 parameter of ncpmount.
7978 Lowercase DOS filenames on LONG namespace volume
7979 CONFIG_NCPFS_SMALLDOS
7980 If you say Y here, every filename on a NetWare server volume using
7981 the OS2/LONG namespace will be converted to lowercase characters.
7982 (For regular NetWare file server volumes with DOS namespace, this is
7983 done automatically, even if you say N here.) Saying N here will give
7984 you these filenames in uppercase.
7986 This is only a cosmetic option since the OS2/LONG namespace is case
7987 insensitive. The only major reason for this option is backward
7988 compatibility when moving from DOS to OS2/LONG namespace support.
7989 Long filenames (created by Win95) will not be affected.
7991 This option does not solve the problem that filenames appear
7992 differently under Linux and under Windows, since Windows does an
7993 additional conversions on the client side. You can achieve similar
7994 effects by saying Y to "Allow using of Native Language Support"
7997 Allow mounting of volume subdirectories
7998 CONFIG_NCPFS_MOUNT_SUBDIR
7999 Allows you to mount not only whole servers or whole volumes, but
8000 also subdirectories from a volume. It can be used to reexport data
8001 and so on. There is no reason to say N, so Y is recommended unless
8002 you count every byte.
8004 To utilize this feature you must use ncpfs-2.0.12 or newer.
8006 NDS interserver authentication domains
8007 CONFIG_NCPFS_NDS_DOMAINS
8008 This allows storing NDS private keys in kernel space where they
8009 can be used to authenticate another server as interserver NDS
8010 accesses need it. You must use ncpfs-2.0.12.1 or newer to utilize
8011 this feature. Say Y if you are using NDS connections to NetWare
8012 servers. Do not say Y if security is primary for you because root
8013 can read your session key (from /proc/kcore).
8015 Allow using of Native Language Support
8017 Allows you to use codepages and I/O charsets for file name
8018 translation between the server file system and input/output. This
8019 may be useful, if you want to access the server with other operating
8020 systems, e.g. Windows 95. See also NLS for more Information.
8022 To select codepages and I/O charsets use ncpfs-2.2.0.13 or newer.
8024 Symbolic links and mode permission bits
8026 This enables the use of symbolic links and an execute permission
8027 bit on NCPFS. The file server need not have long name space or NFS
8028 name space loaded for these to work.
8030 To use the new attributes, it is recommended to use the flags
8031 '-f 600 -d 755' on the ncpmount command line.
8034 CONFIG_NLS_CODEPAGE_437
8035 The Microsoft fat filesystem family can deal with filenames in
8036 native language character sets. These character sets are stored
8037 in so-called DOS codepages. You need to include the appropriate
8038 codepage if you want to be able to read/write these filenames on
8039 DOS/Windows partitions correctly. This does apply to the filenames
8040 only, not to the file contents. You can include several codepages;
8041 say Y here if you want to include the DOS codepage that is used in
8042 the United States and parts of Canada. This is recommended.
8045 CONFIG_NLS_CODEPAGE_737
8046 The Microsoft fat filesystem family can deal with filenames in
8047 native language character sets. These character sets are stored
8048 in so-called DOS codepages. You need to include the appropriate
8049 codepage if you want to be able to read/write these filenames on
8050 DOS/Windows partitions correctly. This does apply to the filenames
8051 only, not to the file contents. You can include several codepages;
8052 say Y here if you want to include the DOS codepage that is used for
8053 Greek. If unsure, say N.
8056 CONFIG_NLS_CODEPAGE_775
8057 The Microsoft fat filesystem family can deal with filenames in
8058 native language character sets. These character sets are stored
8059 in so-called DOS codepages. You need to include the appropriate
8060 codepage if you want to be able to read/write these filenames on
8061 DOS/Windows partitions correctly. This does apply to the filenames
8062 only, not to the file contents. You can include several codepages;
8063 say Y here if you want to include the DOS codepage that is used
8064 for the Baltic Rim Languages. If unsure, say N.
8067 CONFIG_NLS_CODEPAGE_850
8068 The Microsoft fat filesystem family can deal with filenames in
8069 native language character sets. These character sets are stored in
8070 so-called DOS codepages. You need to include the appropriate
8071 codepage if you want to be able to read/write these filenames on
8072 DOS/Windows partitions correctly. This does apply to the filenames
8073 only, not to the file contents. You can include several codepages;
8074 say Y here if you want to include the DOS codepage that is used for
8075 much of Europe -- United Kingdom, Germany, Spain, Italy, and [add
8076 more countries here]. It has some characters useful to many European
8077 languages that are not part of the US codepage 437.
8082 CONFIG_NLS_CODEPAGE_852
8083 The Microsoft fat filesystem family can deal with filenames in
8084 native language character sets. These character sets are stored in
8085 so-called DOS codepages. You need to include the appropriate
8086 codepage if you want to be able to read/write these filenames on
8087 DOS/Windows partitions correctly. This does apply to the filenames
8088 only, not to the file contents. You can include several codepages;
8089 say Y here if you want to include the Latin 2 codepage used by DOS
8090 for much of Central and Eastern Europe. It has all the required
8091 characters for these languages: Albanian, Croatian, Czech, English,
8092 Finnish, Hungarian, Irish, German, Polish, Romanian, Serbian (Latin
8093 transcription), Slovak, Slovenian, and Sorbian.
8096 CONFIG_NLS_CODEPAGE_855
8097 The Microsoft fat filesystem family can deal with filenames in
8098 native language character sets. These character sets are stored in
8099 so-called DOS codepages. You need to include the appropriate
8100 codepage if you want to be able to read/write these filenames on
8101 DOS/Windows partitions correctly. This does apply to the filenames
8102 only, not to the file contents. You can include several codepages;
8103 say Y here if you want to include the DOS codepage for Cyrillic.
8106 CONFIG_NLS_CODEPAGE_857
8107 The Microsoft fat filesystem family can deal with filenames in
8108 native language character sets. These character sets are stored in
8109 so-called DOS codepages. You need to include the appropriate
8110 codepage if you want to be able to read/write these filenames on
8111 DOS/Windows partitions correctly. This does apply to the filenames
8112 only, not to the file contents. You can include several codepages;
8113 say Y here if you want to include the DOS codepage for Turkish.
8116 CONFIG_NLS_CODEPAGE_860
8117 The Microsoft fat filesystem family can deal with filenames in
8118 native language character sets. These character sets are stored in
8119 so-called DOS codepages. You need to include the appropriate
8120 codepage if you want to be able to read/write these filenames on
8121 DOS/Windows partitions correctly. This does apply to the filenames
8122 only, not to the file contents. You can include several codepages;
8123 say Y here if you want to include the DOS codepage for Portuguese.
8126 CONFIG_NLS_CODEPAGE_861
8127 The Microsoft fat filesystem family can deal with filenames in
8128 native language character sets. These character sets are stored in
8129 so-called DOS codepages. You need to include the appropriate
8130 codepage if you want to be able to read/write these filenames on
8131 DOS/Windows partitions correctly. This does apply to the filenames
8132 only, not to the file contents. You can include several codepages;
8133 say Y here if you want to include the DOS codepage for Icelandic.
8136 CONFIG_NLS_CODEPAGE_862
8137 The Microsoft fat filesystem family can deal with filenames in
8138 native language character sets. These character sets are stored in
8139 so-called DOS codepages. You need to include the appropriate
8140 codepage if you want to be able to read/write these filenames on
8141 DOS/Windows partitions correctly. This does apply to the filenames
8142 only, not to the file contents. You can include several codepages;
8143 say Y here if you want to include the DOS codepage for Hebrew.
8146 CONFIG_NLS_CODEPAGE_863
8147 The Microsoft fat filesystem family can deal with filenames in
8148 native language character sets. These character sets are stored in
8149 so-called DOS codepages. You need to include the appropriate
8150 codepage if you want to be able to read/write these filenames on
8151 DOS/Windows partitions correctly. This does apply to the filenames
8152 only, not to the file contents. You can include several codepages;
8153 say Y here if you want to include the DOS codepage for Canadian
8157 CONFIG_NLS_CODEPAGE_864
8158 The Microsoft fat filesystem family can deal with filenames in
8159 native language character sets. These character sets are stored in
8160 so-called DOS codepages. You need to include the appropriate
8161 codepage if you want to be able to read/write these filenames on
8162 DOS/Windows partitions correctly. This does apply to the filenames
8163 only, not to the file contents. You can include several codepages;
8164 say Y here if you want to include the DOS codepage for Arabic.
8167 CONFIG_NLS_CODEPAGE_865
8168 The Microsoft fat filesystem family can deal with filenames in
8169 native language character sets. These character sets are stored in
8170 so-called DOS codepages. You need to include the appropriate
8171 codepage if you want to be able to read/write these filenames on
8172 DOS/Windows partitions correctly. This does apply to the filenames
8173 only, not to the file contents. You can include several codepages;
8174 say Y here if you want to include the DOS codepage for the Nordic
8178 CONFIG_NLS_CODEPAGE_866
8179 The Microsoft fat filesystem family can deal with filenames in
8180 native language character sets. These character sets are stored in
8181 so-called DOS codepages. You need to include the appropriate
8182 codepage if you want to be able to read/write these filenames on
8183 DOS/Windows partitions correctly. This does apply to the filenames
8184 only, not to the file contents. You can include several codepages;
8185 say Y here if you want to include the DOS codepage for
8189 CONFIG_NLS_CODEPAGE_869
8190 The Microsoft fat filesystem family can deal with filenames in
8191 native language character sets. These character sets are stored in
8192 so-called DOS codepages. You need to include the appropriate
8193 codepage if you want to be able to read/write these filenames on
8194 DOS/Windows partitions correctly. This does apply to the filenames
8195 only, not to the file contents. You can include several codepages;
8196 say Y here if you want to include the DOS codepage for Greek.
8198 ### Why do we have two codepages for Greek and Cyrillic?
8202 CONFIG_NLS_CODEPAGE_874
8203 The Microsoft fat filesystem family can deal with filenames in
8204 native language character sets. These character sets are stored in
8205 so-called DOS codepages. You need to include the appropriate
8206 codepage if you want to be able to read/write these filenames on
8207 DOS/Windows partitions correctly. This does apply to the filenames
8208 only, not to the file contents. You can include several codepages;
8209 say Y here if you want to include the DOS codepage for Thai.
8212 CONFIG_NLS_ISO8859_1
8213 If you want to display filenames with native language characters
8214 from the Microsoft fat filesystem family or from JOLIET CDROMs
8215 correctly on the screen, you need to include the appropriate
8216 input/output character sets. Say Y here for the Latin 1 character
8217 set, which covers most West European languages such as Albanian,
8218 Catalan, Danish, Dutch, English, Faeroese, Finnish, French, German,
8219 Galician, Irish, Icelandic, Italian, Norwegian, Portuguese, Spanish,
8220 and Swedish. It is also the default for the US. If unsure, say Y.
8223 CONFIG_NLS_ISO8859_2
8224 If you want to display filenames with native language characters
8225 from the Microsoft fat filesystem family or from JOLIET CDROMs
8226 correctly on the screen, you need to include the appropriate
8227 input/output character sets. Say Y here for the Latin 2 character
8228 set, which works for most Latin-written Slavic and Central European
8229 languages: Czech, German, Hungarian, Polish, Rumanian, Croatian,
8233 CONFIG_NLS_ISO8859_3
8234 If you want to display filenames with native language characters
8235 from the Microsoft fat filesystem family or from JOLIET CDROMs
8236 correctly on the screen, you need to include the appropriate
8237 input/output character sets. Say Y here for the Latin 3 character
8238 set, which is popular with authors of Esperanto, Galician, Maltese,
8242 CONFIG_NLS_ISO8859_4
8243 If you want to display filenames with native language characters
8244 from the Microsoft fat filesystem family or from JOLIET CDROMs
8245 correctly on the screen, you need to include the appropriate
8246 input/output character sets. Say Y here for the Latin 4 character
8247 set which introduces letters for Estonian, Latvian, and
8248 Lithuanian. It is an incomplete predecessor of Latin 6.
8251 CONFIG_NLS_ISO8859_5
8252 If you want to display filenames with native language characters
8253 from the Microsoft fat filesystem family or from JOLIET CDROMs
8254 correctly on the screen, you need to include the appropriate
8255 input/output character sets. Say Y here for ISO8859-5, a Cyrillic
8256 character set with which you can type Bulgarian, Byelorussian,
8257 Macedonian, Russian, Serbian, and Ukrainian. Note that the charset
8258 KOI8-R is preferred in Russia.
8261 CONFIG_NLS_ISO8859_6
8262 If you want to display filenames with native language characters
8263 from the Microsoft fat filesystem family or from JOLIET CDROMs
8264 correctly on the screen, you need to include the appropriate
8265 input/output character sets. Say Y here for ISO8859-6, the Arabic
8269 CONFIG_NLS_ISO8859_7
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 ISO8859-7, the Modern
8274 Greek character set.
8277 CONFIG_NLS_ISO8859_8
8278 If you want to display filenames with native language characters
8279 from the Microsoft fat filesystem family or from JOLIET CDROMs
8280 correctly on the screen, you need to include the appropriate
8281 input/output character sets. Say Y here for ISO8859-8, the Hebrew
8285 CONFIG_NLS_ISO8859_9
8286 If you want to display filenames with native language characters
8287 from the Microsoft fat filesystem family or from JOLIET CDROMs
8288 correctly on the screen, you need to include the appropriate
8289 input/output character sets. Say Y here for the Latin 5 character
8290 set, and it replaces the rarely needed Icelandic letters in Latin 1
8291 with the Turkish ones. Useful in Turkey.
8294 CONFIG_NLS_ISO8859_10
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 Latin 6 character
8299 set, which adds the last Inuit (Greenlandic) and Sami (Lappish)
8300 letters that were missing in Latin 4 to cover the entire Nordic
8304 CONFIG_NLS_ISO8859_14
8305 If you want to display filenames with native language characters
8306 from the Microsoft fat filesystem family or from JOLIET CDROMs
8307 correctly on the screen, you need to include the appropriate
8308 input/output character sets. Say Y here for the Latin 8 character
8309 set, which adds the last accented vowels for Welsh (and Manx Gaelic)
8310 that were missing in Latin 1. http://linux.speech.cymru.org/
8311 has further information.
8314 CONFIG_NLS_ISO8859_15
8315 If you want to display filenames with native language characters
8316 from the Microsoft fat filesystem family or from JOLIET CDROMs
8317 correctly on the screen, you need to include the appropriate
8318 input/output character sets. Say Y here for the Latin 9 character
8319 set, which covers most West European languages such as Albanian,
8320 Catalan, Danish, Dutch, English, Estonian, Faeroese, Finnish,
8321 French, German, Galician, Irish, Icelandic, Italian, Norwegian,
8322 Portuguese, Spanish, and Swedish. Latin 9 is an update to
8323 Latin 1 (ISO 8859-1) that removes a handful of rarely used
8324 characters and instead adds support for Estonian, corrects the
8325 support for French and Finnish, and adds the new Euro character. If
8330 If you want to display filenames with native language characters
8331 from the Microsoft fat filesystem family or from JOLIET CDROMs
8332 correctly on the screen, you need to include the appropriate
8333 input/output character sets. Say Y here for the preferred Russian
8338 If you say Y here, you will get support for terminal devices with
8339 display and keyboard devices. These are called "virtual" because you
8340 can run several virtual terminals (also called virtual consoles) on
8341 one physical terminal. This is rather useful, for example one
8342 virtual terminal can collect system messages and warnings, another
8343 one can be used for a text-mode user session, and a third could run
8344 an X session, all in parallel. Switching between virtual terminals
8345 is done with certain key combinations, usually Alt-<function key>.
8347 The setterm command ("man setterm") can be used to change the
8348 properties (such as colors) of a virtual terminal.
8350 You need at least one virtual terminal device in order to make use
8351 of your keyboard and monitor. Therefore, only people configuring an
8352 embedded system would want to say N here in order to save some
8353 memory; the only way to log into such a system is then via a serial
8354 or network connection.
8356 If unsure, say Y, or else you won't be able to do much with your new
8357 shiny Linux system :-)
8359 Support for console on virtual terminal
8361 The system console is the device which receives all kernel messages
8362 and warnings and which allows logins in single user mode. If you
8363 answer Y here, a virtual terminal (the device used to interact with
8364 a physical terminal) can be used as system console. This is the most
8365 common mode of operations, so you should say Y here unless you want
8366 the kernel messages be output only to a serial port (in which case
8367 you should say Y to "Console on serial port", below).
8369 If you do say Y here, by default the currently visible virtual
8370 terminal (/dev/tty0) will be used as system console. You can change
8371 that with a kernel command line option such as "console=tty3" which
8372 would use the third virtual terminal as system console. (Try "man
8373 bootparam" or see the documentation of your boot loader (lilo or
8374 loadlin) about how to pass options to the kernel at boot time. The
8375 lilo procedure is also explained in the SCSI-HOWTO, available via
8376 FTP (user: anonymous) in
8377 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.)
8381 Software generated cursor
8383 If you say Y here, you'll be able to do lots of nice things with the
8384 cursors of your virtual consoles -- for example turn them into
8385 non-blinking block cursors which are more visible on laptop screens,
8386 or change their colors depending on the virtual console they're on.
8387 See Documentation/VGA-softcursor.txt for more information.
8389 Support for PowerMac keyboard
8391 This option allows you to use an ADB keyboard attached to your
8392 machine. Note that this disables any other (ie. PS/2) keyboard
8393 support, even if your machine is physically capable of using both at
8396 If you use an ADB keyboard (4 pin connector), say Y here.
8397 If you use a PS/2 keyboard (6 pin connector), say N here.
8399 Standard/generic serial support
8401 This selects whether you want to include the driver for the standard
8402 serial ports. The standard answer is Y. People who might say N here
8403 are those that are setting up dedicated Ethernet WWW/FTP servers, or
8404 users that have one of the various bus mice instead of a serial
8405 mouse and don't intend to use their machine's standard serial port
8406 for anything. (Note that the Cyclades and Stallion multi serial port
8407 drivers do not need this driver built in for them to work.)
8409 If you want to compile this driver as a module, say M here and read
8410 Documentation/modules.txt. The module will be called serial.o.
8411 [WARNING: Do not compile this driver as a module if you are using
8412 non-standard serial ports, since the configuration information will
8413 be lost when the driver is unloaded. This limitation may be lifted
8416 BTW1: If you have a mouseman serial mouse which is not recognized by
8417 the X window system, try running gpm first.
8419 BTW2: If you intend to connect a so-called Winmodem to your
8420 machine's serial port, forget it. These modems are crippled and
8421 require proprietary drivers which are only available under Windows.
8423 Most people will say Y or M here, so that they can use serial mice,
8424 modems and similar devices connecting to the standard serial ports.
8426 Support for console on serial port
8427 CONFIG_SERIAL_CONSOLE
8428 If you say Y here, it will be possible to use a serial port as the
8429 system console (the system console is the device which receives all
8430 kernel messages and warnings and which allows logins in single user
8431 mode). This could be useful if some terminal or printer is connected
8432 to that serial port.
8434 Even if you say Y here, the currently visible virtual console
8435 (/dev/tty0) will still be used as the system console by default, but
8436 you can alter that using a kernel command line option such as
8437 "console=ttyS1". (Try "man bootparam" or see the documentation of
8438 your boot loader (lilo or loadlin) about how to pass options to the
8439 kernel at boot time. The lilo procedure is also explained in the
8440 SCSI-HOWTO, available via FTP (user: anonymous) in
8441 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.)
8443 If you don't have a VGA card installed and you say Y here, the
8444 kernel will automatically use the first serial line, /dev/ttyS0, as
8449 Support for PowerMac serial ports
8451 If you have Macintosh style serial ports (8 pin mini-DIN), say Y
8452 here. If you also have regular serial ports and enable the driver
8453 for them, you can't currently use the serial console feature.
8455 Comtrol Rocketport support
8457 This is a driver for the Comtrol Rocketport cards which provide
8458 multiple serial ports. You would need something like this to connect
8459 more than two modems to your Linux box, for instance in order to
8460 become a dial-in server.
8462 If you want to compile this driver as a module, say M here and read
8463 Documentation/modules.txt. The module will be called rocket.o.
8465 Digiboard Intelligent async support
8467 This is a driver for Digi International's Xx, Xeve, and Xem series
8468 of cards which provide multiple serial ports. You would need
8469 something like this to connect more than two modems to your Linux
8470 box, for instance in order to become a dial-in server. This driver
8471 supports the original PC (ISA) boards as well as PCI, and EISA. If
8472 you have a card like this, say Y here and read the file
8473 Documentation/digiepca.txt.
8475 NOTE: There is another, separate driver for the Digiboard PC boards:
8476 "Digiboard PC/Xx Support" below. You should (and can) only select
8477 one of the two drivers.
8479 If you want to compile this driver as a module, say M here and read
8480 Documentation/modules.txt. The module will be called epca.o.
8482 Digiboard PC/Xx Support
8484 This is a driver for the Digiboard PC/Xe, PC/Xi, and PC/Xeve cards
8485 that give you many serial ports. You would need something like this
8486 to connect more than two modems to your Linux box, for instance in
8487 order to become a dial-in server. If you have a card like that, say
8488 Y here and read the file Documentation/digiboard.txt.
8490 If you want to compile this driver as a module, say M here and read
8491 Documentation/modules.txt. The module will be called pcxx.o.
8493 SDL RISCom/8 card support
8495 This is a driver for the SDL Communications RISCom/8 multiport card,
8496 which gives you many serial ports. You would need something like
8497 this to connect more than two modems to your Linux box, for instance
8498 in order to become a dial-in server. If you have a card like that,
8499 say Y here and read the file Documentation/riscom8.txt.
8501 Also it's possible to say M here and compile this driver as kernel
8502 loadable module; the module will be called riscom8.o.
8504 Specialix IO8+ card support
8506 This is a driver for the Specialix IO8+ multiport card (both the
8507 ISA and the PCI version) which gives you many serial ports. You
8508 would need something like this to connect more than two modems to
8509 your Linux box, for instance in order to become a dial-in server.
8511 If you have a card like that, say Y here and read the file
8512 Documentation/specialix.txt. Also it's possible to say M here and
8513 compile this driver as kernel loadable module which will be called
8516 Specialix DTR/RTS pin is RTS
8517 CONFIG_SPECIALIX_RTSCTS
8518 The Specialix card can only support either RTS or DTR. If you say N
8519 here, the driver will use the pin as "DTR" when the tty is in
8520 software handshake mode. If you say Y here or hardware handshake is
8521 on, it will always be RTS. Read the file Documentation/specialix.txt
8522 for more information.
8524 Cyclades async mux support
8526 This is a driver for a card that gives you many serial ports. You
8527 would need something like this to connect more than two modems to
8528 your Linux box, for instance in order to become a dial-in server.
8529 For information about the Cyclades-Z card, read
8530 drivers/char/README.cycladesZ.
8532 As of 1.3.9x kernels, this driver's minor numbers start at 0 instead
8535 If you want to compile this as a module ( = code which can be
8536 inserted in and removed from the running kernel whenever you want),
8537 say M here and read Documentation/modules.txt. The module will be
8540 If you haven't heard about it, it's safe to say N.
8542 Cyclades-Z interrupt mode operation (EXPERIMENTAL)
8544 The Cyclades-Z family of multiport cards allows 2 (two) driver
8545 op modes: polling and interrupt. In polling mode, the driver will
8546 check the status of the Cyclades-Z ports every certain amount of
8547 time (which is called polling cycle and is configurable). In
8548 interrupt mode, it will use an interrupt line (IRQ) in order to check
8549 the status of the Cyclades-Z ports. The default op mode is polling.
8552 Stallion multiport serial support
8554 Stallion cards give you many serial ports. You would need something
8555 like this to connect more than two modems to your Linux box, for
8556 instance in order to become a dial-in server. If you say Y here, you
8557 will be asked for your specific card model in the next questions.
8558 Make sure to read drivers/char/README.stallion in this case. If you
8559 have never heard about all this, it's safe to say N.
8561 Stallion EasyIO or EC8/32 support
8563 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
8564 card, then this is for you; say Y. Make sure to read
8565 Documentation/stallion.txt.
8567 If you want to compile this as a module ( = code which can be
8568 inserted in and removed from the running kernel whenever you want),
8569 say M here and read Documentation/modules.txt. The module will be
8572 Stallion EC8/64, ONboard, Brumby support
8574 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
8575 serial multiport card, say Y here. Make sure to read
8576 Documentation/stallion.txt.
8578 To compile it as a module ( = code which can be inserted in and
8579 removed from the running kernel whenever you want), say M here and
8580 read Documentation/modules.txt. The module will be called
8583 Microgate SyncLink adapter support
8585 Provides support for the SyncLink ISA and PCI
8586 multiprotocol serial adapters. These adapters
8587 support asynchronous and HDLC bit synchronous
8588 communication up to 10Mbps (PCI adapter).
8590 This driver can only be built as a module ( = code which can be
8591 inserted in and removed from the running kernel whenever you want).
8592 The module will be called synclink.o. If you want to do that, say M
8595 Synchronous HDLC line discipline support
8597 Allows synchronous HDLC communications with
8598 tty device drivers that support synchronous
8599 HDLC such as the Microgate SyncLink adapter.
8601 This driver can only be built as a module ( = code which can be
8602 inserted in and removed from the running kernel whenever you want).
8603 The module will be called n_hdlc.o. If you want to do that, say M
8606 Hayes ESP serial port support
8608 This is a driver which supports Hayes ESP serial ports. Both single
8609 port cards and multiport cards are supported. Make sure to read
8610 Documentation/hayes-esp.txt.
8612 To compile this driver as a module ( = code which can be inserted in
8613 and removed from the running kernel whenever you want), say M here
8614 and read Documentation/modules.txt. The module will be called esp.o.
8617 Multi-Tech multiport card support
8619 This is a driver for the Multi-Tech cards which provide several
8620 serial ports. The driver is experimental and can currently only be
8621 built as a module ( = code which can be inserted in and removed from
8622 the running kernel whenever you want). Please read
8623 Documentation/modules.txt. The module will be called isicom.o
8627 A pseudo terminal (PTY) is a software device consisting of two
8628 halves: a master and a slave. The slave device behaves identical to
8629 a physical terminal; the master device is used by a process to
8630 read data from and write data to the slave, thereby emulating a
8631 terminal. Typical programs for the master side are telnet servers
8634 Linux has traditionally used the BSD-like names /dev/ptyxx for
8635 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
8636 has a number of problems. The GNU C library glibc 2.1 and later,
8637 however, supports the Unix98 naming standard: in order to acquire a
8638 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
8639 terminal is then made available to the process and the pseudo
8640 terminal slave can be accessed as /dev/pts/<number>. What was
8641 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
8643 The entries in /dev/pts/ are created on the fly by a virtual
8644 filesystem; therefore, if you say Y here you should say Y to
8645 "/dev/pts filesystem for Unix98 PTYs" as well.
8647 If you want to say Y here, you need to have the C library glibc 2.1
8648 or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
8649 Read the instructions in Documentation/Changes pertaining to pseudo
8650 terminals. It's safe to say N.
8652 Maximum number of Unix98 PTYs in use (0-2048)
8653 CONFIG_UNIX98_PTY_COUNT
8654 The maximum number of Unix98 PTYs that can be used at any one time.
8655 The default is 256, and should be enough for desktop systems. Server
8656 machines which support incoming telnet/rlogin/ssh connections and/or
8657 serve several X terminals may want to increase this: every incoming
8658 connection and every xterm uses up one PTY.
8660 When not in use, each additional set of 256 PTYs occupy
8661 approximately 8 KB of kernel memory on 32-bit architectures.
8663 Parallel printer support
8665 If you intend to attach a printer to the parallel port of your Linux
8666 box (as opposed to using a serial printer; if the connector at the
8667 printer has 9 or 25 holes ["female"], then it's serial), say Y. Also
8668 read the Printing-HOWTO, available via FTP (user: anonymous) in
8669 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
8671 It is possible to share one parallel port among several devices
8672 (e.g. printer and ZIP drive) and it is safe to compile the
8673 corresponding drivers into the kernel. If you want to compile this
8674 driver as a module however ( = code which can be inserted in and
8675 removed from the running kernel whenever you want), say M here and
8676 read Documentation/modules.txt and Documentation/parport.txt. The
8677 module will be called lp.o.
8679 If you have several parallel ports, you can specify which ports to
8680 use with the "lp" kernel command line option. (Try "man bootparam"
8681 or see the documentation of your boot loader (lilo or loadlin)
8682 about how to pass options to the kernel at boot time. The lilo
8683 procedure is also explained in the SCSI-HOWTO, available via FTP
8684 (user: anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.)
8685 The syntax of the "lp" command line option can be found in
8688 If you have more than 3 printers, you need to increase the LP_NO
8691 Support for console on line printer
8693 If you want kernel messages to be printed out as they occur, you
8694 can have a console on the printer. This option adds support for
8695 doing that; to actually get it to happen you need to pass the
8696 option "console=lp" to the kernel at boot time.
8698 Note that kernel messages can get lost if the printer is out of
8699 paper (or off, or unplugged, or too busy..), but this behaviour
8700 can be changed. See drivers/char/lp.c (do this at your own risk).
8704 Mouse Support (not serial mice)
8706 This is for machines with a bus mouse or a PS/2 mouse as opposed to
8707 a serial mouse. Most people have a regular serial MouseSystem or
8708 Microsoft mouse (made by Logitech) that plugs into a COM port
8709 (rectangular with 9 or 25 pins). These people say N here. If you
8710 have something else, read the Busmouse-HOWTO, available via FTP
8711 (user: anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO and
8714 If you have a laptop, you either have to check the documentation or
8715 experiment a bit to find out whether the trackball is a serial mouse
8716 or not; it's best to say Y here for you.
8718 Note that the answer to this question won't directly affect the
8719 kernel: saying N will just cause this configure script to skip all
8720 the questions about non-serial mice. If unsure, say Y.
8722 Logitech busmouse support
8724 Logitech mouse connected to a proprietary interface card. It's
8725 generally a round connector with 9 pins. Note that the newer mice
8726 made by Logitech don't use the Logitech protocol anymore; for those,
8727 you don't need this option. You want to read the Busmouse-HOWTO,
8728 available via FTP (user: anonymous) in
8729 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
8731 If you want to compile this as a module ( = code which can be
8732 inserted in and removed from the running kernel whenever you want),
8733 say M here and read Documentation/modules.txt. The module will be
8734 called busmouse.o. If you are unsure, say N and read the HOWTO
8735 nevertheless: it will tell you what you have.
8737 PS/2 mouse (aka "auxiliary device") support
8739 The PS/2 mouse connects to a special mouse port that looks much like
8740 the keyboard port (small circular connector with 6 pins). This way,
8741 the mouse does not use any serial ports. This port can also be used
8742 for other input devices like light pens, tablets, keypads. Compaq,
8743 AST and IBM all use this as their mouse port on currently shipping
8744 machines. The trackballs of some laptops are PS/2 mice also. In
8745 particular, the C&T 82C710 mouse on TI Travelmates is a PS/2 mouse.
8747 Although PS/2 mice are not technically bus mice, they are explained
8748 in detail in the Busmouse-HOWTO, available via FTP (user: anonymous)
8749 in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
8751 When using a PS/2 mouse, you can get problems if you want to use the
8752 mouse both on the Linux console and under X. Using the "-R" option
8753 of the Linux mouse managing program gpm (available from
8754 ftp://metalab.unc.edu/pub/Linux/system/Daemons) solves this
8755 problem, or you can get the "mconv" utility also from metalab.
8757 C&T 82C710 mouse port support (as on TI Travelmate)
8759 This is a certain kind of PS/2 mouse used on the TI Travelmate. If
8760 you are unsure, try first to say N here and come back if the mouse
8761 doesn't work. Read the Busmouse-HOWTO, available via FTP (user:
8762 anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
8764 PC110 digitizer pad support
8766 This drives the digitizer pad on the IBM PC110 palmtop (see
8767 http://toy.cabi.net; to browse the WWW, you need to have access to a
8768 machine on the Internet that has a program like lynx or
8769 netscape). It can turn the digitizer pad into a PS/2 mouse emulation
8770 with tap gestures or into an absolute pad.
8772 If you want to compile this as a module ( = code which can be
8773 inserted in and removed from the running kernel whenever you want),
8774 say M here and read Documentation/modules.txt. The module will be
8777 Microsoft busmouse support
8779 These animals (also called Inport mice) are connected to an
8780 expansion board using a round connector with 9 pins. If this is what
8781 you have, say Y and read the Busmouse-HOWTO, available via FTP
8782 (user: anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
8784 If you are unsure, say N and read the HOWTO nevertheless: it will
8785 tell you what you have. Also be aware that several vendors talk
8786 about 'Microsoft busmouse' and actually mean PS/2 busmouse -- so
8787 count the pins on the connector.
8789 If you want to compile this as a module ( = code which can be
8790 inserted in and removed from the running kernel whenever you want),
8791 say M here and read Documentation/modules.txt. The module will be
8792 called msbusmouse.o.
8794 ATIXL busmouse support
8795 CONFIG_ATIXL_BUSMOUSE
8796 This is a rare type of busmouse that is connected to the back of an
8797 ATI video card. Note that most ATI mice are actually Microsoft
8798 busmice. Read the Busmouse-HOWTO, available via FTP (user:
8799 anonymous) in ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
8801 If you want to compile this as a module ( = code which can be
8802 inserted in and removed from the running kernel whenever you want),
8803 say M here and read Documentation/modules.txt. The module will be
8804 called atixlmouse.o.
8806 If you are unsure, say N and read the HOWTO nevertheless: it will
8807 tell you what you have.
8809 Support for PowerMac ADB mouse
8811 If you have an ADB mouse (4 pin connector) as is common on
8812 Macintoshes, say Y here.
8816 If you have a non-SCSI tape drive like that, say Y. Or, if you want
8817 to compile this driver as a module ( = code which can be inserted in
8818 and removed from the running kernel whenever you want), say M here
8819 and read Documentation/modules.txt. The module will be called
8822 Do you want runtime configuration for QIC-02
8823 CONFIG_QIC02_DYNCONF
8824 You can either configure this driver once and for all by editing a
8825 header file (include/linux/tpqic02.h), in which case you should
8826 say N, or you can fetch a program via anonymous FTP which is able
8827 to configure this driver during runtime. The program to do this is
8828 called 'qic02conf' and it is part of the tpqic02-support-X.Y.tar.gz
8831 If you want to use the qic02conf program, say Y.
8833 Floppy tape drive (QIC-80/40/3010/3020/TR-1/TR-2/TR-3) support
8835 If you have a tape drive that is connected to your floppy
8836 controller, say Y here.
8838 Some tape drives (like the Seagate "Tape Store 3200" or the Iomega
8839 "Ditto 3200" or the Exabyte "Eagle TR-3") come with a "high speed"
8840 controller of their own. These drives (and their companion
8841 controllers) are also supported if you say Y here.
8843 If you have a special controller (such as the CMS FC-10, FC-20,
8844 Mountain Mach-II, or any controller that is based on the Intel 82078
8845 FDC like the high speed controllers by Seagate and Exabyte and
8846 Iomega's "Ditto Dash") you must configure it by selecting the
8847 appropriate entries from the "Floppy tape controllers" sub-menu
8848 below and possibly modify the default values for the IRQ and DMA
8849 channel and the IO base in ftape's configuration menu.
8851 If you want to use your floppy tape drive on a PCI-bus based system,
8852 please read the file drivers/char/ftape/README.PCI.
8854 The ftape kernel driver is also available as a runtime loadable
8855 module ( = code which can be inserted in and removed from the
8856 running kernel whenever you want). If you want to compile it as a
8857 module, say M here and read Documentation/modules.txt. The module
8858 will be called ftape.o.
8860 Note that the Ftape-HOWTO is out of date (sorry) and documents the
8861 older version 2.08 of this software but still contains useful
8862 information. There is a web page with more recent documentation at
8863 http://www-math.math.rwth-aachen.de/~LBFM/claus/ftape/ . This page
8864 always contains the latest release of the ftape driver and useful
8865 information (backup software, ftape related patches and
8866 documentation, FAQ). (To browse the WWW, you need to have access to
8867 a machine on the Internet that has a program like lynx or netscape.)
8868 Note that the file system interface has changed quite a bit compared
8869 to previous versions of ftape. Please read Documentation/ftape.txt.
8871 The file system interface for ftape
8873 Normally, you want to say Y or M. DON'T say N here or you
8874 WON'T BE ABLE TO USE YOUR FLOPPY TAPE DRIVE.
8876 The ftape module itself no longer contains the routines necessary
8877 to interface with the kernel VFS layer (i.e. to actually write data
8878 to and read data from the tape drive). Instead the file system
8879 interface (i.e. the hardware independent part of the driver) has
8880 been moved to a separate module.
8882 If you say M zftape will be compiled as a runtime loadable
8883 module ( = code which can be inserted in and removed from the
8884 running kernel whenever you want). In this case you should read
8885 Documentation/modules.txt. The module will be called zftape.o.
8887 Regardless of whether you say Y or M here, an additional runtime
8888 loadable module called `zft-compressor.o' which contains code to
8889 support user transparent on-the-fly compression based on Ross
8890 William's lzrw3 algorithm will be produced. If you have enabled the
8891 kernel module loader (i.e. have said Y to "Kernel module loader
8892 support", above) then `zft-compressor.o' will be loaded
8893 automatically by zftape when needed.
8895 Despite its name, zftape does NOT use compression by default. The
8896 file Documentation/ftape.txt contains a short description of the
8897 most important changes in the file system interface compared to
8898 previous versions of ftape. The ftape home page
8899 http://www-math.math.rwth-aachen.de/~LBFM/claus/ftape/ contains
8900 further information (to browse the WWW, you need to have access to a
8901 machine on the Internet that has a program like lynx or netscape).
8903 IMPORTANT NOTE: zftape can read archives created by previous
8904 versions of ftape and provide file mark support (i.e. fast skipping
8905 between tape archives) but previous version of ftape will lack file
8906 mark support when reading archives produced by zftape.
8908 Default block size for zftape
8909 CONFIG_ZFT_DFLT_BLK_SZ
8910 If unsure leave this at its default value, i.e. 10240. Note that
8911 you specify only the default block size here. The block size can be
8912 changed at run time using the MTSETBLK tape operation with the
8913 MTIOCTOP ioctl (i.e. with "mt -f /dev/qft0 setblk #BLKSZ" from the
8914 shell command line).
8916 The probably most striking difference between zftape and previous
8917 versions of ftape is the fact that all data must be written or read
8918 in multiples of a fixed block size. The block size defaults to
8919 10240 which is what GNU tar uses. The values for the block size
8920 should be either 1 or multiples of 1024 up to a maximum value of
8921 63488 (i.e. 62 K). If you specify `1' then zftape's builtin
8922 compression will be disabled.
8924 Reasonable values are `10240' (GNU tar's default block size),
8925 `5120' (afio's default block size), `32768' (default block size some
8926 backup programs assume for SCSI tape drives) or `1' (no restriction
8927 on block size, but disables builtin compression).
8929 Number of DMA buffers
8930 CONFIG_FT_NR_BUFFERS
8931 Please leave this at `3' unless you REALLY know what you are doing.
8932 It is not necessary to change this value. Values below 3 make the
8933 proper use of ftape impossible, values greater than 3 are a waste of
8934 memory. You can change the amount of DMA memory used by ftape at
8935 runtime with "mt -f /dev/qft0 setdrvbuffer #NUMBUFFERS". Each buffer
8936 wastes 32 KB of memory. Please note that this memory cannot be
8939 Procfs entry for ftape
8941 Optional. Saying Y will result in creation of a directory
8942 `/proc/ftape' under the proc file system. The files can be viewed
8943 with your favorite pager (i.e. use "more /proc/ftape/history" or
8944 "less /proc/ftape/history" or simply "cat /proc/ftape/history"). The
8945 file will contain some status information about the inserted
8946 cartridge, the kernel driver, your tape drive, the floppy disk
8947 controller and the error history for the most recent use of the
8948 kernel driver. Saying Y will enlarge the size of the ftape driver
8949 by approximately 2 KB.
8951 WARNING: When compiling ftape as a module (i.e. saying M to
8952 "Floppy tape drive") it is dangerous to use ftape's proc file system
8953 interface. Accessing `/proc/ftape' while the module is unloaded will
8954 result in a kernel Oops. This cannot be fixed from inside ftape.
8956 Controlling the amount of debugging output of ftape
8957 CONFIG_FT_NORMAL_DEBUG
8958 This option controls the amount of debugging output the ftape driver
8959 is ABLE to produce; it does not increase or diminish the debugging
8960 level itself. If unsure, leave this at its default setting,
8961 i.e. choose "Normal".
8963 Ftape can print lots of debugging messages to the system console
8964 resp. kernel log files. Reducing the amount of possible debugging
8965 output reduces the size of the kernel module by some KB, so it might
8966 be a good idea to use "None" for emergency boot floppies.
8968 If you want to save memory then the following strategy is
8969 recommended: leave this option at its default setting "Normal" until
8970 you know that the driver works as expected, afterwards reconfigure
8971 the kernel, this time specifying "Reduced" or "None" and recompile
8972 and install the kernel as usual. Note that choosing "Excessive"
8973 debugging output does not increase the amount of debugging output
8974 printed to the console but only makes it possible to produce
8975 "Excessive" debugging output.
8977 Please read Documentation/ftape.txt for a short description
8978 how to control the amount of debugging output.
8980 The floppy drive controller for ftape
8982 Only change this setting if you have a special controller. If you
8983 didn't plug any add-on card into your computer system but just
8984 plugged the floppy tape cable into the already existing floppy drive
8985 controller then you don't want to change the default setting,
8986 i.e. choose "Standard".
8988 Choose "MACH-2" if you have a Mountain Mach-2 controller.
8989 Choose "FC-10/FC-20" if you have a Colorado FC-10 or FC-20
8991 Choose "Alt/82078" if you have another controller that is located at
8992 an IO base address different from the standard floppy drive
8993 controller's base address of `0x3f0', or uses an IRQ (interrupt)
8994 channel different from `6', or a DMA channel different from
8995 `2'. This is necessary for any controller card that is based on
8996 Intel's 82078 FDC such as Seagate's, Exabyte's and Iomega's "high
8999 If you choose something other than "Standard" then please make
9000 sure that the settings for the IO base address and the IRQ and DMA
9001 channel in the configuration menus below are correct. Use the manual
9002 of your tape drive to determine the correct settings!
9004 If you are already successfully using your tape drive with another
9005 operating system then you definitely should use the same settings
9006 for the IO base, the IRQ and DMA channel that have proven to work
9009 Note that this menu lets you specify only the default setting for
9010 the hardware setup. The hardware configuration can be changed at
9011 boot time (when ftape is compiled into the kernel, i.e. if you
9012 have said Y to "Floppy tape drive") or module load time (i.e. if you
9013 have said M to "Floppy tape drive").
9015 Please read also the file Documentation/ftape.txt which
9016 contains a short description of the parameters that can be set at
9017 boot or load time. If you want to use your floppy tape drive on a
9018 PCI-bus based system, please read the file
9019 drivers/char/ftape/README.PCI.
9021 IO base of the floppy disk controller used with Ftape
9023 You don't need to specify a value if the following default
9024 settings for the base IO address are correct:
9025 <<< MACH-2 : 0x1E0 >>>
9026 <<< FC-10/FC-20: 0x180 >>>
9027 <<< Secondary : 0x370 >>>
9028 Secondary refers to a secondary FDC controller like the "high speed"
9029 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
9030 Please make sure that the setting for the IO base address
9031 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
9032 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
9033 successfully using the tape drive with another operating system then
9034 you definitely should use the same settings for the IO base that has
9035 proven to work with that other OS.
9037 Note that this menu lets you specify only the default setting for
9038 the IO base. The hardware configuration can be changed at boot time
9039 (when ftape is compiled into the kernel, i.e. if you specified Y to
9040 "Floppy tape drive") or module load time (i.e. if you have said M to
9041 "Floppy tape drive").
9043 Please read also the file Documentation/ftape.txt which contains a
9044 short description of the parameters that can be set at boot or load
9047 IRQ channel for the floppy disk controller used with Ftape
9049 You don't need to specify a value if the following default
9050 settings for the interrupt channel are correct:
9052 <<< FC-10/FC-20: 9 >>>
9053 <<< Secondary : 6 >>>
9054 Secondary refers to secondary a FDC controller like the "high speed"
9055 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
9056 Please make sure that the setting for the IO base address
9057 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
9058 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
9059 successfully using the tape drive with another operating system then
9060 you definitely should use the same settings for the IO base that has
9061 proven to work with that other OS.
9063 Note that this menu lets you specify only the default setting for
9064 the IRQ channel. The hardware configuration can be changed at boot
9065 time (when ftape is compiled into the kernel, i.e. if you said Y to
9066 "Floppy tape drive") or module load time (i.e. if you said M to
9067 "Floppy tape drive").
9069 Please read also the file Documentation/ftape.txt which contains a
9070 short description of the parameters that can be set at boot or load
9073 DMA channel for the floppy disk controller used with Ftape
9075 You don't need to specify a value if the following default
9076 settings for the DMA channel are correct:
9078 <<< FC-10/FC-20: 3 >>>
9079 <<< Secondary : 2 >>>
9080 Secondary refers to a secondary FDC controller like the "high speed"
9081 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
9082 Please make sure that the setting for the IO base address
9083 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
9084 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
9085 successfully using the tape drive with another operating system then
9086 you definitely should use the same settings for the IO base that has
9087 proven to work with that other OS.
9089 Note that this menu lets you specify only the default setting for
9090 the DMA channel. The hardware configuration can be changed at boot
9091 time (when ftape is compiled into the kernel, i.e. if you said Y to
9092 "Floppy tape drive") or module load time (i.e. if you said M to
9093 "Floppy tape drive").
9095 Please read also the file Documentation/ftape.txt which contains a
9096 short description of the parameters that can be set at boot or load
9099 FDC FIFO Threshold before requesting DMA service
9101 Set the FIFO threshold of the FDC. If this is higher the DMA
9102 controller may serve the FDC after a higher latency time. If this is
9103 lower, fewer DMA transfers occur leading to less bus contention.
9104 You may try to tune this if ftape annoys you with "reduced data
9105 rate because of excessive overrun errors" messages. However, this
9106 doesn't seem to have too much effect.
9108 If unsure, don't touch the initial value, i.e. leave it at "8".
9110 FDC maximum data rate
9111 CONFIG_FT_FDC_MAX_RATE
9112 With some motherboard/FDC combinations ftape will not be able to
9113 run your FDC/tape drive combination at the highest available
9114 speed. If this is the case you'll encounter "reduced data rate
9115 because of excessive overrun errors" messages and lots of retries
9116 before ftape finally decides to reduce the data rate.
9118 In this case it might be desirable to tell ftape beforehand that
9119 it need not try to run the tape drive at the highest available
9120 speed. If unsure, leave this disabled, i.e. leave it at 2000
9123 MTRR control and configuration
9125 On Intel P6 family processors (Pentium Pro, Pentium II and later)
9126 the Memory Type Range Registers (MTRRs) may be used to control
9127 processor access to memory ranges. This is most useful when you have
9128 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
9129 allows bus write transfers to be combined into a larger transfer
9130 before bursting over the PCI/AGP bus. This can increase performance
9131 of image write operations 2.5 times or more. This option creates a
9132 /proc/mtrr file which may be used to manipulate your
9133 MTRRs. Typically the X server should use this. This should have a
9134 reasonably generic interface so that similar control registers on
9135 other processors can be easily supported.
9137 The Cyrix 6x86, 6x86MX and M II processors have Address Range
9138 Registers (ARRs) which provide a similar functionality to MTRRs. For
9139 these, the ARRs are used to emulate the MTRRs.
9141 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
9142 MTRRs. These are supported.
9144 The Centaur C6 (WinChip) has 8 MCRs, allowing write-combining. These
9147 Saying Y here also fixes a problem with buggy SMP BIOSes which only
9148 set the MTRRs for the boot CPU and not the secondary CPUs. This can
9149 lead to all sorts of problems.
9151 You can safely say Y even if your machine doesn't have MTRRs, you'll
9152 just add about 3k to your kernel.
9154 See Documentation/mtrr.txt for more information.
9156 Main CPU frequency, only for DEC alpha machine
9157 CONFIG_FT_ALPHA_CLOCK
9158 On some DEC Alpha machines the CPU clock frequency cannot be
9159 determined automatically, so you need to specify it here ONLY if
9160 running a DEC Alpha, otherwise this setting has no effect.
9162 Zilog serial support
9164 If you are asked this question, something is wrong with config scripts.
9165 Zilog serial driver is always enabled in sparc architecture.
9167 Double Talk PC internal speech card support
9169 This driver is for the DoubleTalk PC, a speech synthesizer
9170 manufactured by RC Systems (http://www.rcsys.com/). It is also
9171 called the `internal DoubleTalk'. If you want to compile this as a
9172 module ( = code which can be inserted in and removed from the
9173 running kernel whenever you want), say M here and read
9174 Documentation/modules.txt. The module will be called dtlk.o.
9176 Siemens R3964 serial protocol support
9178 This driver allows syncronous communication with devices using the
9179 Siemens R3964 packet protocol. Unless you are dealing with special
9180 hardware like PLCs, you are unlikely to need this.
9182 To compile this driver as a module ( = code which can be inserted in
9183 and removed from the running kernel whenever you want), say M here
9184 and read Documentation/modules.txt. The module will be called
9189 Applicom intelligent fieldbus card support
9191 This driver provides the kernel-side support for the intelligent
9192 fieldbus cards made by Applicom International. More information
9193 about these cards can be found on the WWW at the address
9194 http://www.applicom-int.com/ (to browse the WWW, you need to have
9195 access to a machine on the Internet that has a program like lynx
9196 or netscape), or by email from David Woodhouse <dwmw2@mvhi.com>.
9198 To compile this driver as a module ( = code which can be inserted in
9199 and removed from the running kernel whenever you want), say M here
9200 and read Documentation/modules.txt. The module will be called
9205 Advanced Power Management
9207 APM is a BIOS specification for saving power using several different
9208 techniques. This is mostly useful for battery powered laptops with
9209 APM compliant BIOSes. If you say Y here, the system time will be
9210 reset after a USER RESUME operation, the /proc/apm device will
9211 provide battery status information, and user-space programs will
9212 receive notification of APM "events" (e.g., battery status change).
9214 Supporting software is available; for more information, read the
9215 Battery Powered Linux mini-HOWTO, available via FTP (user:
9216 anonymous) from ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini.
9218 This driver does not spin down disk drives (see the hdparm(8)
9219 manpage ("man 8 hdparm") for that), and it doesn't turn off
9220 VESA-compliant "green" monitors.
9222 This driver does not support the TI 4000M TravelMate and the ACER
9223 486/DX4/75 because they don't have compliant BIOSes. Many "green"
9224 desktop machines also don't have compliant BIOSes, and this driver
9225 will cause those machines to panic during the boot phase (typically,
9226 these machines are using a data segment of 0040, which is reserved
9227 for the Linux kernel).
9229 If you are running Linux on a laptop, you may also want to read the
9230 Linux Laptop home page on the WWW at
9231 http://www.cs.utexas.edu/users/kharker/linux-laptop/ (to browse the
9232 WWW, you need to have access to a machine on the Internet that has a
9233 program like lynx or netscape).
9235 Generally, if you don't have a battery in your machine, there isn't
9236 much point in using this driver and you should say N. If you get
9237 random kernel OOPSes or reboots that don't seem to be related to
9238 anything, try disabling/enabling this option (or disabling/enabling
9241 Some other things you should try when experiencing seemingly random,
9244 1) make sure that you have enough swap space and that it is
9246 2) pass the "no-hlt" option to the kernel
9247 3) switch on floating point emulation in the kernel and pass
9248 the "no387" option to the kernel
9249 4) pass the "floppy=nodma" option to the kernel
9250 5) pass the "mem=4M" option to the kernel (thereby disabling
9251 all but the first 4 MB of RAM)
9252 6) make sure that the CPU is not over clocked.
9253 7) read the sig11 FAQ at http://www.bitwizard.nl/sig11/
9254 8) disable the cache from your BIOS settings
9255 9) install a fan for the video card or exchange video RAM
9256 10) install a better fan for the CPU
9257 11) exchange RAM chips
9258 12) exchange the motherboard.
9261 CONFIG_APM_IGNORE_USER_SUSPEND
9262 This option will ignore USER SUSPEND requests. On machines with a
9263 compliant APM BIOS, you want to say N. However, on the NEC Versa M
9264 series notebooks, it is necessary to say Y because of a BIOS bug.
9266 Enable APM at boot time
9267 CONFIG_APM_DO_ENABLE
9268 Enable APM features at boot time. From page 36 of the APM BIOS
9269 specification: "When disabled, the APM BIOS does not automatically
9270 power manage devices, enter the Standby State, enter the Suspend
9271 State, or take power saving steps in response to CPU Idle calls."
9272 This driver will make CPU Idle calls when Linux is idle (unless this
9273 feature is turned off -- see "Do CPU IDLE calls", below). This
9274 should always save battery power, but more complicated APM features
9275 will be dependent on your BIOS implementation. You may need to turn
9276 this option off if your computer hangs at boot time when using APM
9277 support, or if it beeps continuously instead of suspending. Turn
9278 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
9279 T400CDT. This is off by default since most machines do fine without
9284 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
9285 On some machines, this can activate improved power savings, such as
9286 a slowed CPU clock rate, when the machine is idle. These idle calls
9287 are made after the idle loop has run for some length of time (e.g.,
9288 333 mS). On some machines, this will cause a hang at boot time or
9289 whenever the CPU becomes idle. (On machines with more than one CPU,
9290 this option does nothing.)
9292 Enable console blanking using APM
9293 CONFIG_APM_DISPLAY_BLANK
9294 Enable console blanking using the APM. Some laptops can use this to
9295 turn off the LCD backlight when the screen blanker of the Linux
9296 virtual console blanks the screen. Note that this is only used by
9297 the virtual console screen blanker, and won't turn off the backlight
9298 when using the X Window system. This also doesn't have anything to
9299 do with your VESA-compliant power-saving monitor. Further, this
9300 option doesn't work for all laptops -- it might not turn off your
9301 backlight at all, or it might print a lot of errors to the console,
9302 especially if you are using gpm.
9304 Power off on shutdown
9305 CONFIG_APM_POWER_OFF
9306 Enable the ability to power off the computer after the Linux kernel
9307 is halted. You will need software (e.g., a suitable version of the
9308 halt(8) command ("man 8 halt")) to cause the computer to power down.
9309 Recent versions of the sysvinit package available from
9310 ftp://metalab.unc.edu/pub/Linux/system/daemons/init/ (user:
9311 anonymous) contain support for this ("halt -p" shuts down Linux and
9312 powers off the computer, if executed from runlevel 0). As with the
9313 other APM options, this option may not work reliably with some APM
9314 BIOS implementations.
9316 Ignore multiple suspend/standby events
9317 CONFIG_APM_IGNORE_MULTIPLE_SUSPEND
9318 This option is necessary on the IBM Thinkpad 560, but should work on
9319 all other laptops. When the APM BIOS returns multiple suspend or
9320 standby events while one is already being processed they will be
9321 ignored. Without this the Thinkpad 560 has troubles with the user
9322 level daemon apmd, and with the PCMCIA package pcmcia-cs.
9324 Ignore multiple suspend/resume cycles
9325 CONFIG_APM_IGNORE_SUSPEND_BOUNCE
9326 This option is necessary on the Dell Inspiron 3200 and others, but
9327 should be safe for all other laptops. When enabled, a system suspend
9328 event that occurs within three seconds of a resume is ignored.
9329 Without this the Inspiron will shut itself off a few seconds after
9330 you open the lid, requiring you to press the power button to resume
9331 it a second time. Say Y.
9333 RTC stores time in GMT
9334 CONFIG_APM_RTC_IS_GMT
9335 Say Y here if your RTC (Real Time Clock a.k.a. hardware clock)
9336 stores the time in GMT (Greenwich Mean Time). Say N if your RTC
9339 It is in fact recommended to store GMT in your RTC, because then you
9340 don't have to worry about daylight savings time changes. The only
9341 reason not to use GMT in your RTC is if you also run a broken OS
9342 that doesn't understand GMT.
9344 Allow interrupts during APM BIOS calls
9345 CONFIG_APM_ALLOW_INTS
9346 Normally we disable external interrupts while we are making calls to
9347 the APM BIOS as a measure to lessen the effects of a badly behaving
9348 BIOS implementation. The BIOS should reenable interrupts if it
9349 needs to. Unfortunately, some BIOSes do not - especially those in
9350 many of the newer IBM Thinkpads. If you experience hangs when you
9351 suspend, try setting this to Y. Otherwise, say N.
9353 Watchdog Timer Support
9355 If you say Y here (and to one of the following options) and create a
9356 character special file /dev/watchdog with major number 10 and minor
9357 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
9358 subsequently opening the file and then failing to write to it for
9359 longer than 1 minute will result in rebooting the machine. This
9360 could be useful for a networked machine that needs to come back
9361 online as fast as possible after a lock-up. There's both a watchdog
9362 implementation entirely in software (which can sometimes fail to
9363 reboot the machine) and a driver for hardware watchdog boards, which
9364 are more robust and can also keep track of the temperature inside
9365 your computer. For details, read Documentation/watchdog.txt in the
9368 The watchdog is usually used together with the watchdog daemon
9369 which is available via FTP (user: anonymous) from
9370 ftp://tsx-11.mit.edu/pub/linux/sources/sbin/. This daemon can also
9371 monitor NFS connections and can reboot the machine when the process
9376 Disable watchdog shutdown on close
9377 CONFIG_WATCHDOG_NOWAYOUT
9378 The default watchdog behaviour (which you get if you say N here) is
9379 to stop the timer if the process managing it closes the file
9380 /dev/watchdog. It's always remotely possible that this process might
9381 get killed. If you say Y here, the watchdog cannot be stopped once
9382 it has been started.
9386 If you have a WDT500P or WDT501P watchdog board, say Y here,
9387 otherwise N. It is not possible to probe for this board, which means
9388 that you have to set the IO port and IRQ it uses in the kernel
9389 source at the top of drivers/char/wdt.c.
9391 If you want to compile this as a module ( = code which can be
9392 inserted in and removed from the running kernel whenever you want),
9393 say M here and read Documentation/modules.txt. The module will be
9398 Saying Y here and creating a character special file /dev/temperature
9399 with major number 10 and minor number 131 ("man mknod") will give
9400 you a thermometer inside your computer: reading from
9401 /dev/temperature yields one byte, the temperature in degrees
9402 Fahrenheit. This works only if you have a WDT501P watchdog board
9407 Enable the Fan Tachometer on the WDT501. Only do this if you have a
9408 fan tachometer actually set up.
9411 CONFIG_SOFT_WATCHDOG
9412 A software monitoring watchdog. This will fail to reboot your system
9413 from some situations that the hardware watchdog will recover
9414 from. Equally it's a lot cheaper to install.
9416 This driver is also available as a module ( = code which can be
9417 inserted in and removed from the running kernel whenever you want).
9418 If you want to compile it as a module, say M here and read
9419 Documentation/modules.txt. The module will be called softdog.o.
9421 Berkshire Products PC Watchdog
9423 This is the driver for the Berkshire Products PC Watchdog card.
9424 This card simply watches your kernel to make sure it doesn't freeze,
9425 and if it does, it reboots your computer after a certain amount of
9426 time. This driver is like the WDT501 driver but for different
9427 hardware. Please read Documentation/pcwd-watchdog.txt. The PC
9428 watchdog cards can be ordered from http://www.berkprod.com. Some
9429 example rc.local files are available from ftp://ftp.bitgate.com.
9431 This driver is also available as a module ( = code which can be
9432 inserted in and removed from the running kernel whenever you want).
9433 The module is called pcwd.o. If you want to compile it as a module,
9434 say M here and read Documentation/modules.txt.
9436 Most people will say N.
9438 Acquire SBC Watchdog Timer
9440 This is the driver for the hardware watchdog on the PSC-6x86 Single
9441 Board Computer produced by Acquire Inc (and others). This watchdog
9442 simply watches your kernel to make sure it doesn't freeze, and if
9443 it does, it reboots your computer after a certain amount of time.
9445 This driver is like the WDT501 driver but for different hardware.
9446 This driver is also available as a module ( = code which can be
9447 inserted in and removed from the running kernel whenever you want).
9448 The module is called pscwdt.o. If you want to compile it as a
9449 module, say M here and read Documentation/modules.txt. Most people
9452 Enhanced Real Time Clock Support
9454 If you say Y here and create a character special file /dev/rtc with
9455 major number 10 and minor number 135 using mknod ("man mknod"), you
9456 will get access to the real time clock built into your computer.
9457 Every PC has such a clock built in. It can be used to generate
9458 signals from as low as 1Hz up to 8192Hz, and can also be used as a
9459 24 hour alarm. It reports status information via the file /proc/rtc
9460 and its behaviour is set by various ioctls on /dev/rtc.
9462 If you run Linux on a multiprocessor machine and said Y to
9463 "Symmetric Multi Processing" above, you should say Y here to read
9464 and set the RTC in an SMP compatible fashion.
9466 If you think you have a use for such a device (such as periodic data
9467 sampling), then say Y here, and read Documentation/rtc.txt for
9470 Tadpole ANA H8 Support
9472 The Hitachi H8/337 is a microcontroller used to deal with the power
9473 and thermal environment. If you say Y here, you will be able to
9474 communicate with it via a character special device.
9480 If you say Y here and create a character special file /dev/nvram
9481 with major number 10 and minor number 144 using mknod ("man mknod"),
9482 you get read and write access to the 50 bytes of non-volatile memory
9483 in the real time clock (RTC), which is contained in every PC and
9486 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
9487 on Ataris. /dev/nvram may be used to view settings there, or to
9488 change them (with some utility). It could also be used to frequently
9489 save a few bits of very important data that may not be lost over
9490 power-off and for which writing to disk is too insecure. Note
9491 however that most NVRAM space in a PC belongs to the BIOS and you
9492 should NEVER idly tamper with it. See Ralf Brown's interrupt list
9493 for a guide to the use of CMOS bytes by your BIOS.
9495 On Atari machines, /dev/nvram is always configured and does not need
9498 This driver is also available as a module ( = code which can be
9499 inserted in and removed from the running kernel whenever you want).
9500 The module will be called nvram.o. If you want to compile it as a
9501 module, say M here and read Documentation/modules.txt.
9503 Atomwide Serial Support
9504 CONFIG_ATOMWIDE_SERIAL
9505 If you have an Atomwide Serial card for an Acorn system, say Y to
9506 this option. The driver can handle 1, 2, or 3 port cards.
9509 The Serial Port Dual Serial Port
9510 CONFIG_DUALSP_SERIAL
9511 If you have the Serial Port's dual serial card for an Acorn system,
9512 say Y to this option. If unsure, say N
9516 If you have a joystick, you can say Y here to enable generic
9517 joystick support. You will also need to say Y or M to at least one
9518 of the hardware specific joystick drivers. This will make the
9519 joysticks available as /dev/jsX devices. Please read the file
9520 Documentation/joystick.txt which contains more information and the
9521 location of the joystick package that you'll need.
9523 This driver is also available as a module ( = code which can be
9524 inserted in and removed from the running kernel whenever you want).
9525 The module will be called joystick.o. If you want to compile it as a
9526 module, say M here and read Documentation/modules.txt.
9528 Classic PC analog joysticks and gamepads
9530 Say Y here if you have an analog joystick or gamepad that connects
9531 to the PC gameport. This supports many different types, including
9532 joysticks with throttle control, with rudders, or with extensions
9533 like additional hats and buttons compatible with CH Flightstick Pro,
9534 ThrustMaster FCS or 6 and 8 button gamepads. For more information on
9535 how to use the driver please read Documentation/joystick.txt
9537 FPGaming and MadCatz A3D controllers
9539 Say Y here if you have an FPGaming Assasin 3D, MadCatz Panther or
9540 MadCatz Panther XL. For more information on how to use the driver
9541 please read Documentation/joystick.txt
9543 Gravis GrIP joysticks and gamepads
9545 Say Y here if you have a Gravis GamePad Pro, Gravis Xterminator or
9546 Gravis Blackhawk Digital. For more information on how to use the
9547 driver please read Documentation/joystick.txt
9549 PDPI Lightning 4 gamecards
9550 CONFIG_JOY_LIGHTNING
9551 Say Y here if you have a PDPI Lightning 4 gamecard and an analog
9552 joystick or gamepad connected to it. For more information on how to
9553 use the driver please read Documentation/joystick.txt
9555 Logitech Digital joysticks and gamepads
9557 Say Y here if you have a Logitech WingMan Extreme Digital,
9558 Logitech ThunderPad Digital or Logitech CyberMan 2. For more
9559 information on how to use the driver please read
9560 Documentation/joystick.txt
9562 Microsoft SideWinder, Genius Digital joysticks and gamepads
9563 CONFIG_JOY_SIDEWINDER
9564 Say Y here if you have a Microsoft SideWinder 3d Pro, Microsoft
9565 SideWinder Precision Pro, Microsoft SideWinder Force Feedback Pro,
9566 Microsoft Sidewinder GamePad or Genius Flight2000 F-23 Digital. For
9567 more information on how to use the driver please read
9568 Documentation/joystick.txt
9570 ThrustMaster DirectConnect joysticks and gamepads
9571 CONFIG_JOY_THRUSTMASTER
9572 Say Y here if you have a ThrustMaster Millenium 3D Inceptor or a
9573 ThrustMaster 3D Rage Pad. For more information on how to use the
9574 driver please read Documentation/joystick.txt
9576 NES, SNES, PSX, Multisystem joysticks and gamepads
9578 Say Y here if you have a Nintendo Entertainment System gamepad,
9579 Super Nintendo Entertainment System gamepad, Sony PlayStation
9580 gamepad or a Multisystem -- Atari, Amiga, Commodore, Amstrad CPC
9581 joystick. For more information on how to use the driver please read
9582 Documentation/joystick.txt and Documentation/joystick-parport.txt
9584 Sega, Multisystem joysticks and gamepads
9586 Say Y here if you have a Sega Master System gamepad, Sega Genesis
9587 gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga,
9588 Commodore, Amstrad CPC joystick. For more information on how to use
9589 the driver please read Documentation/joystick.txt and
9590 Documentation/joystick-parport.txt
9592 TurboGraFX Multisystem joystick interface
9593 CONFIG_JOY_TURBOGRAFX
9594 Say Y here if you have the TurboGraFX interface by Steffen Schwenke,
9595 and want to use it with Multiststem -- Atari, Amiga, Commodore,
9596 Amstrad CPC joystick. For more information on how to use the driver
9597 please read Documentation/joystick.txt and
9598 Documentation/joystick-parport.txt
9602 Say Y here if you have an Amiga with a digital joystick connected
9603 to it. For more information on how to use the driver please read
9604 Documentation/joystick.txt
9606 Atomwide Serial Support
9607 CONFIG_ATOMWIDE_SERIAL
9608 If you have an Atomwide Serial card for an Acorn system, say Y to
9609 this option. The driver can handle 1, 2, or 3 port cards.
9612 The Serial Port Dual Serial Port
9613 CONFIG_DUALSP_SERIAL
9614 If you have the Serial Port's dual serial card for an Acorn system,
9615 say Y to this option. If unsure, say N
9619 If you enable this driver and create a character device node
9620 /dev/nwbutton with major and minor numbers 10 and 158 ("man mknod"),
9621 then every time the orange button is pressed a number of times, the
9622 number of times the button was pressed will be written to that device.
9623 This is most useful for applications, as yet unwritten, which perform
9624 actions based on how many times the button is pressed in a row.
9625 Do not hold the button down for too long, as the driver does not alter
9626 the behaviour of the hardware reset circuitry attached to the button;
9627 it will still execute a hard reset if the button is held down for
9628 longer than approximately five seconds.
9629 This driver is also available as a module ( = code which can be
9630 inserted in and removed from the running kernel whenever you want).
9631 If you want to compile it as a module, say M here and read
9632 Documentation/modules.txt. The module will be called nwbutton.o.
9633 Most people will answer Y to this question and "Reboot Using Button"
9634 below to be able to initiate a system shutdown from the button.
9637 CONFIG_NWBUTTON_REBOOT
9638 If you enable this option, then you will be able to initiate a system
9639 shutdown and reboot by pressing the orange button a number of times.
9640 The number of presses to initiate the shutdown is two by default, but
9641 this can be altered by modifying the value of NUM_PRESSES_REBOOT in
9642 nwbutton.h and recompiling the driver or, if you compile the driver as
9643 a module, you can specify the number of presses at load time with
9644 "insmod button reboot_count=<something>".
9648 If you have a sound card in your computer, i.e. if it can say more
9649 than an occasional beep, say Y. Be sure to have all the information
9650 about your sound card and its configuration down (I/O port,
9651 interrupt and DMA channel), because you will be asked for it.
9653 You want to read the Sound-HOWTO, available via FTP (user:
9654 anonymous) from ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. General
9655 information about the modular sound system is contained in the files
9656 Documentation/sound/Introduction. The file
9657 Documentation/sound/README.OSS contains some slightly outdated but
9658 still useful information as well.
9660 If you have a PnP sound card and you want to configure it at boot
9661 time using the ISA PnP tools (read
9662 http://www.roestock.demon.co.uk/isapnptools/ (to browse the WWW, you
9663 need to have access to a machine on the Internet that has a program
9664 like lynx or netscape)), then you need to compile the sound card
9665 support as a module ( = code which can be inserted in and removed
9666 from the running kernel whenever you want) and load that module
9667 after the PnP configuration is finished. To do this, say M here and
9668 read Documentation/modules.txt as well as
9669 Documentation/sound/README.modules; the module will be called
9672 I'm told that even without a sound card, you can make your computer
9673 say more than an occasional beep, by programming the PC speaker.
9674 Kernel patches and supporting utilities to do that are in the pcsp
9675 package, available at http://www.imladris.demon.co.uk/pcsp/.
9679 OSS is the Open Sound System suite of sound card drivers. They make
9680 sound programming easier since they provide a common API. Say Y or M
9681 here (the module will be called sound.o) if you haven't found a
9682 driver for your sound card above, then pick your driver from the
9685 Persistent DMA buffers
9687 Linux can often have problems allocating DMA buffers for ISA sound
9688 cards on machines with more than 16MB of RAM. This is because ISA
9689 DMA buffers must exist below the 16MB boundary and it is quite
9690 possible that a large enough free block in this region cannot be
9691 found after the machine has been running for a while. If you say Y
9692 here the DMA buffers (64Kb) will be allocated at boot time and kept
9693 until the shutdown. This option is only useful if you said Y to
9694 "OSS sound modules", above. If you said M to "OSS sound modules"
9695 then you can get the persistent DMA buffer functionality by passing
9696 the command-line argument "dmabuf=1" to the sound.o module.
9698 Say Y unless you have 16MB or less RAM or a PCI sound card.
9700 Support for Aztech Sound Galaxy (non-PnP) cards
9701 CONFIG_SOUND_SGALAXY
9702 This module initializes the older non Plug and Play sound galaxy
9703 cards from Aztech. It supports the Waverider Pro 32 - 3D and the
9704 Galaxy Washington 16.
9706 Support for AD1816(A) based cards (EXPERIMENTAL)
9708 Say M here if you have a sound card based on the Analog Devices
9711 NOTE: This driver is still EXPERIMENTAL.
9712 See Documentation/sound/AD1816 for further information.
9714 Yamaha OPL3-SA1 audio controller
9715 CONFIG_SOUND_OPL3SA1
9716 Say Y or M if you have a Yamaha OPL3-SA1 sound chip, which is
9717 usually built into motherboards. Read Documentation/sound/OPL3-SA
9720 ProAudioSpectrum 16 support
9722 Answer Y only if you have a Pro Audio Spectrum 16, ProAudio Studio
9723 16 or Logitech SoundMan 16 sound card. Don't answer Y if you have
9724 some other card made by Media Vision or Logitech since they are not
9727 100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support
9729 Answer Y if you have an original Sound Blaster card made by Creative
9730 Labs or a 100% hardware compatible clone (like the Thunderboard or
9731 SM Games). For an unknown card you may answer Y if the card claims
9732 to be Sound Blaster-compatible.
9734 Please read the file Documentation/sound/Soundblaster.
9736 You should also say Y here for cards based on the Avance Logic
9737 ALS-007 chip (read Documentation/sound/ALS007) and for cards based
9738 on ESS chips (read Documentation/sound/ESS1868 and
9739 Documentation/sound/ESS). If you have an SB AWE 32 or SB AWE 64, say
9740 Y here and also to "Additional lowlevel drivers" and to "SB32/AWE
9741 support" below and read Documentation/sound/INSTALL.awe. If you have
9742 an IBM Mwave card, say Y here and read Documentation/sound/mwave.
9744 You can say M here to compile this driver as a module; the module is
9747 Generic OPL2/OPL3 FM synthesizer support
9749 Answer Y if your card has a FM chip made by Yamaha (OPL2/OPL3/OPL4).
9750 Answering Y is usually a safe and recommended choice, however some
9751 cards may have software (TSR) FM emulation. Enabling FM support with
9752 these cards may cause trouble (I don't currently know of any such
9755 Please read the file Documentation/sound/OPL3 if your card has an
9761 #Loopback MIDI device support
9764 ### somebody please fill this in.
9767 Gravis Ultrasound support
9769 Say Y here for any type of Gravis Ultrasound card, including
9770 the GUS or GUS MAX. See also Documentation/sound/ultrasound for
9771 more information on configuring this card with modules.
9773 MPU-401 support (NOT for SB16)
9775 Be careful with this question. The MPU401 interface is supported by
9776 all sound cards. However, some natively supported cards have their
9777 own driver for MPU401. Enabling this MPU401 option with these cards
9778 will cause a conflict. Also, enabling MPU401 on a system that
9779 doesn't really have a MPU401 could cause some trouble. If your card
9780 was in the list of supported cards, look at the card specific
9781 instructions in the drivers/sound/Readme.cards file. It's safe to
9782 answer Y if you have a true MPU401 MIDI interface card.
9785 CONFIG_SOUND_UART6850
9786 This option enables support for MIDI interfaces based on the 6850
9787 UART chip. This interface is rarely found on sound cards. It's safe
9788 to answer N to this question.
9792 Say Y here for ARM systems with the VIDC video controller and 16-bit
9793 Linear sound DACs. If unsure, say N.
9795 PSS (AD1848, ADSP-2115, ESC614) support
9797 Answer Y or M if you have an Orchid SW32, Cardinal DSP16, Beethoven
9798 ADSP-16 or some other card based on the PSS chipset (AD1848 codec +
9799 ADSP-2115 DSP chip + Echo ESC614 ASIC CHIP). For more information on
9800 how to compile it into the kernel or as a module see the file
9801 Documentation/sound/PSS.
9803 Enable PSS mixer (Beethoven ADSP-16 and other compatible)
9805 Answer Y for Beethoven ADSP-16. You may try to say Y also for other
9806 cards if they have master volume, bass, treble, and you can't
9807 control it under Linux. If you answer N for Beethoven ADSP-16, you
9808 can't control master volume, bass, treble and synth volume.
9810 If you said M to "PSS support" above, you may enable or disable this
9811 PSS mixer with the module parameter pss_mixer. For more information
9812 see the file Documentation/sound/PSS.
9814 Have DSPxxx.LD firmware file
9815 CONFIG_PSS_HAVE_BOOT
9816 If you have the DSPxxx.LD file or SYNTH.LD file for you card, say Y
9817 to include this file. Without this file the synth device (OPL) may
9820 Full pathname of DSPxxx.LD firmware file
9821 CONFIG_PSS_BOOT_FILE
9822 Enter the full pathname of your DSPxxx.LD file or SYNTH.LD file,
9825 16 bit sampling option of GUS (_NOT_ GUS MAX)
9827 Answer Y if you have installed the 16 bit sampling daughtercard on
9828 your GUS. Answer N if you have a GUS MAX, since saying Y here
9829 disables GUS MAX support.
9833 Answer Y only if you have a Gravis Ultrasound MAX.
9835 Microsoft Sound System support
9837 Again think carefully before answering Y to this question. It's safe
9838 to answer Y if you have the original Windows Sound System card made
9839 by Microsoft or Aztech SG 16 Pro (or NX16 Pro). Also you may say Y
9840 in case your card is NOT among these:
9842 ATI Stereo F/X, AdLib, Audio Excell DSP16, Cardinal DSP16,
9843 Ensoniq SoundScape (and compatibles made by Reveal and Spea),
9844 Gravis Ultrasound, Gravis Ultrasound ACE, Gravis Ultrasound Max,
9845 Gravis Ultrasound with 16 bit option, Logitech Sound Man 16,
9846 Logitech SoundMan Games, Logitech SoundMan Wave, MAD16 Pro (OPTi
9847 82C929), Media Vision Jazz16, MediaTriX AudioTriX Pro, Microsoft
9848 Windows Sound System (MSS/WSS), Mozart (OAK OTI-601), Orchid
9849 SW32, Personal Sound System (PSS), Pro Audio Spectrum 16, Pro
9850 Audio Studio 16, Pro Sonic 16, Roland MPU-401 MIDI interface,
9851 Sound Blaster 1.0, Sound Blaster 16, Sound Blaster 16ASP, Sound
9852 Blaster 2.0, Sound Blaster AWE32, Sound Blaster Pro, TI TM4000M
9853 notebook, ThunderBoard, Turtle Beach Tropez, Yamaha FM
9854 synthesizers (OPL2, OPL3 and OPL4), 6850 UART MIDI Interface.
9856 For cards having native support in VoxWare, consult the card
9857 specific instructions in drivers/sound/Readme.cards. Some drivers
9858 have their own MSS support and saying Y to this option will cause a
9861 Ensoniq Soundscape support
9863 Answer Y if you have a sound card based on the Ensoniq SoundScape
9864 chipset. Such cards are being manufactured at least by Ensoniq, Spea
9865 and Reveal (Reveal makes also other cards).
9867 MediaTriX AudioTriX Pro support
9869 Answer Y if you have the AudioTriX Pro sound card manufactured
9872 Have TRXPRO.HEX firmware file
9873 CONFIG_TRIX_HAVE_BOOT
9874 The MediaTrix AudioTrix Pro has an on-board microcontroller which
9875 needs to be initialized by downloading the code from the file
9876 TRXPRO.HEX in the DOS driver directory. If you don't have the
9877 TRXPRO.HEX file handy you may skip this step. However, the SB and
9878 MPU-401 modes of AudioTrix Pro will not work without this file!
9880 Full pathname of TRXPRO.HEX firmware file
9881 CONFIG_TRIX_BOOT_FILE
9882 Enter the full pathname of your TRXPRO.HEX file, starting from /.
9884 Support for OPTi MAD16 and/or Mozart based cards
9886 Answer Y if your card has a Mozart (OAK OTI-601) or MAD16 (OPTi
9887 82C928 or 82C929 or 82C931) audio interface chip. For the 82C931,
9888 please read drivers/sound/README.C931. These chips are currently
9889 quite common so it's possible that many no-name cards have one of
9890 them. In addition the MAD16 chip is used in some cards made by known
9891 manufacturers such as Turtle Beach (Tropez), Reveal (some models)
9892 and Diamond (latest ones). Note however that the Tropez sound cards
9893 have their own driver; if you have one of those, say N here and Y or
9894 M to "Full support for Turtle Beach WaveFront", below.
9896 See also Documentation/sound/Opti and Documentation/sound/MAD16 for
9897 more information on setting these cards up as modules.
9899 Full support for Turtle Beach WaveFront synth/sound cards
9900 CONFIG_SOUND_WAVEFRONT
9901 Answer Y or M if you have a Tropez Plus, Tropez or Maui sound card
9902 and read the files Documentation/sound/Wavefront and
9903 Documentation/sound/Tropez+.
9905 Support MIDI in older MAD16 based cards (requires SB)
9906 CONFIG_MAD16_OLDCARD
9907 Answer Y (or M) if you have an older card based on the C928 or
9908 Mozart chipset and you want to have MIDI support. If you enable this
9909 option you also need to enable support for Sound Blaster.
9911 Support for Crystal CS4232 based (PnP) cards
9913 Say Y here if you have a card based on the Crystal CS4232 chip set,
9914 which uses its own Plug and Play protocol.
9916 See Documentation/sound/CS4232 for more information on configuring
9919 Support for Yamaha OPL3-SA2, SA3, and SAx based PnP cards
9920 CONFIG_SOUND_OPL3SA2
9921 Say Y or M if you have a card based on one of these Yamaha
9922 sound chipsets. Read Documentation/sound/OPL3-SA2 for more
9923 information on configuring these cards.
9925 Support for Turtle Beach Wave Front (Maui, Tropez) synthesizers
9927 Say Y here if you have a Turtle Beach Wave Front, Maui, or Tropez
9930 Have OSWF.MOT firmware file
9931 CONFIG_MAUI_HAVE_BOOT
9932 Turtle Beach Maui and Tropez sound cards have a microcontroller
9933 which needs to be initialized prior to use. OSWF.MOT is a file
9934 distributed with the card's DOS/Windows drivers. Answer Y if you
9937 Full pathname of OSWF.MOT firmware file
9938 CONFIG_MAUI_BOOT_FILE
9939 Enter the full pathname of your OSWF.MOT file, starting from /.
9941 Support for Turtle Beach MultiSound Classic, Tahiti, Monterey
9942 CONFIG_SOUND_MSNDCLAS
9943 Say M here if you have a Turtle Beach MultiSound Classic, Tahiti or
9944 Monterey (not for the Pinnacle or Fiji).
9946 See Documentation/sound/MultiSound for important information about
9949 Full pathname of MSNDINIT.BIN firmware file
9950 CONFIG_MSNDCLAS_INIT_FILE
9951 The MultiSound cards have two firmware files which are required for
9952 operation, and are not currently included. These files can be
9953 obtained from Turtle Beach. See Documentation/sound/MultiSound for
9954 information on how to obtain this.
9956 Full pathname of MSNDPERM.BIN firmware file
9957 CONFIG_MSNDCLAS_PERM_FILE
9958 The MultiSound cards have two firmware files which are required for
9959 operation, and are not currently included. These files can be
9960 obtained from Turtle Beach. See Documentation/sound/MultiSound for
9961 information on how to obtain this.
9963 Support for Turtle Beach MultiSound Pinnacle, Fiji
9964 CONFIG_SOUND_MSNDPIN
9965 Say M here if you have a Turtle Beach MultiSound Pinnacle or Fiji.
9966 See Documentation/sound/MultiSound for important information about
9969 Full pathname of PNDSPINI.BIN firmware file
9970 CONFIG_MSNDPIN_INIT_FILE
9971 The MultiSound cards have two firmware files which are required for
9972 operation, and are not currently included. These files can be
9973 obtained from Turtle Beach. See Documentation/sound/MultiSound for
9974 information on how to obtain this.
9976 Full pathname of PNDSPERM.BIN firmware file
9977 CONFIG_MSNDPIN_PERM_FILE
9978 The MultiSound cards have two firmware files which are required for
9979 operation, and are not currently included. These files can be
9980 obtained from Turtle Beach. See Documentation/sound/MultiSound for
9981 information on how to obtain this.
9983 MSND Pinnacle have S/PDIF I/O
9984 CONFIG_MSNDPIN_DIGITAL
9985 If you have the S/PDIF daughter board for the Pinnacle or Fiji,
9986 answer Y here; otherwise, say N. If you have this, you will be able
9987 to play and record from the S/PDIF port (digital signal). See
9988 Documentation/sound/MultiSound for information on how to make use of
9991 MSND Pinnacle non-PnP Mode
9992 CONFIG_MSNDPIN_NONPNP
9993 The Pinnacle and Fiji card resources can be configured either with
9994 PnP, or through a configuration port. Say Y here if your card is NOT
9995 in PnP mode. For the Pinnacle, configuration in non-PnP mode allows
9996 use of the IDE and joystick peripherals on the card as well; these
9997 do not show up when the card is in PnP mode. Specifying zero for any
9998 resource of a device will disable the device. If you are running the
9999 card in PnP mode, you must say N here and use isapnptools to
10000 configure the card's resources.
10002 MSND Pinnacle config port
10004 This is the port which the Pinnacle and Fiji uses to configure the
10005 card's resources when not in PnP mode. If your card is in PnP mode,
10006 then be sure to say N to the previous option, "MSND Pinnacle Non-PnP
10009 MSND buffer size (kB)
10010 CONFIG_MSND_FIFOSIZE
10011 Configures the size of each audio buffer, in kilobytes, for
10012 recording and playing in the MultiSound drivers (both the Classic
10013 and Pinnacle). Larger values reduce the chance of data overruns at
10014 the expense of overall latency. If unsure, use the default.
10016 /dev/dsp and /dev/audio support
10018 If you say Y here, you will get the /dev/dsp and /dev/audio devices;
10019 these are the analog-digital and digital-analog converter devices
10020 and are very useful, so say Y.
10022 MIDI interface support
10024 Answering N disables /dev/midixx devices and access to any MIDI
10025 ports using /dev/sequencer and /dev/music. This option also affects
10026 any MPU401 and/or General MIDI compatible devices. Answer Y.
10028 FM synthesizer (YM3812/OPL-3) support
10029 CONFIG_SOUND_YM3812
10030 Answer Y here, unless you know you will not need the option.
10034 This is support for the sound cards on Sun workstations. The code
10035 does not exist yet, so you might as well say N here.
10037 Additional low level drivers
10038 CONFIG_LOWLEVEL_SOUND
10039 If you need additional low level sound drivers which have not yet
10040 appeared, say Y. The answer to this question does not directly
10041 affect the kernel; saying Y will simply cause this configure script
10042 to present you with more options. If unsure, say Y.
10044 ACI mixer (miroPCM12/PCM20)
10046 ACI (Audio Command Interface) is a protocol used to communicate with
10047 the microcontroller on some sound cards produced by miro, e.g. the
10048 miroSOUND PCM12 and PCM20. The main function of the ACI is to
10049 control the mixer and to get a product identification.
10051 This Voxware ACI driver currently only supports the ACI functions on
10052 the miroSOUND PCM12 and PCM20 cards. On the PCM20, ACI also controls
10053 the radio tuner. This is supported in the video4linux
10054 radio-miropcm20 driver.
10058 Say Y here if you have a Sound Blaster SB32, AWE32-PnP, SB AWE64 or
10059 similar sound card. See Documentation/sound/README.awe,
10060 Documentation/sound/AWE32 and the Soundblaster-AWE mini-HOWTO,
10061 available via FTP (user: anonymous) from
10062 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini for more info.
10064 Gallant's Audio Excel DSP 16 support (SC-6000 and SC-6600)
10066 Answer Y if you have a Gallant's Audio Excel DSP 16 card. This
10067 driver supports Audio Excel DSP 16 but not the III nor PnP versions
10070 The Gallant's Audio Excel DSP 16 card can emulate either an SBPro or
10071 a Microsoft Sound System card, so you should have said Y to either
10072 "100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support"
10073 or "Microsoft Sound System support", above, and you need to answer
10074 the "MSS emulation" and "SBPro emulation" questions below
10075 accordingly. You should say Y to one and only one of these two
10078 Read the drivers/sound/lowlevel/README.aedsp16 file and the head of
10079 drivers/sound/lowlevel/aedsp16.c as well as
10080 Documentation/sound/AudioExcelDSP16 to get more information about
10081 this driver and its configuration.
10083 I/O base for Audio Excel DSP 16
10084 CONFIG_AEDSP16_BASE
10085 This is the base I/O address of the Audio Excel DSP 16 card. It must
10086 be 220 or 240. If you compiled aedsp16.o as a module you can specify
10087 this parameter as 'io=0xNNN'.
10089 Audio Excel DSP 16 (SBPro emulation)
10090 CONFIG_AEDSP16_SBPRO
10091 Answer Y if you want your audio card to emulate Sound Blaster Pro.
10092 You should then say Y to "100% Sound Blaster compatibles
10093 (SB16/32/64, ESS, Jazz16) support" and N to "Audio Excel DSP 16 (MSS
10096 Audio Excel DSP 16 IRQ
10097 CONFIG_AEDSP16_SB_IRQ
10098 This is the IRQ of the Audio Excel DSP 16 card. It must be 5, 7, 9,
10099 10 or 11. If you compiled aedsp16.o as a module you can specify
10100 this parameter as 'irq=NN'.
10102 Audio Excel DSP 16 DMA
10103 CONFIG_AEDSP16_SB_DMA
10104 This is the IRQ of the Audio Excel DSP 16 card. It must be 0, 1 or 3.
10105 If you compiled aedsp16.o as a module you can specify this parameter
10108 Audio Excel DSP 16 (MSS emulation)
10110 Answer Y if you want your audio card to emulate Microsoft Sound
10111 System. You should then say Y to "Microsoft Sound System support"
10112 and say N to "Audio Excel DSP 16 (SBPro emulation)".
10114 Audio Excel DSP 16 IRQ
10115 CONFIG_AEDSP16_MSS_IRQ
10116 This is the IRQ of the Audio Excel DSP 16 card. It must be 5, 7, 9,
10117 10 or 11. If you compiled aedsp16.o as a module you can specify
10118 this parameter as 'irq=NN'.
10120 Audio Excel DSP 16 DMA
10121 CONFIG_AEDSP16_MSS_DMA
10122 This is the IRQ of the Audio Excel DSP 16 card. It must be 0, 1
10123 or 3. If you compiled aedsp16.o as a module you can specify this
10124 parameter as 'dma=NN'.
10126 SC-6600 based audio cards (new Audio Excel DSP 16)
10128 The SC6600 is the new version of DSP mounted on the Audio Excel DSP
10129 16 cards. Find in the manual the FCC ID of your audio card and
10130 answer Y if you have an SC6600 DSP.
10132 SC-6600 Joystick Interface
10134 Say Y here in order to use the joystick interface of the Audio Excel
10137 SC-6600 CDROM Interface
10138 CONFIG_SC6600_CDROM
10139 This is used to activate the the CDROM interface of the Audio Excel
10140 DSP 16 card. Enter: 0 for Sony, 1 for Panasonic, 2 for IDE, 4 for no
10143 Audio Excel DSP 16 (MPU401 emulation)
10144 CONFIG_AEDSP16_MPU401
10145 Answer Y if you want your audio card to emulate the MPU-401 midi
10146 interface. You should then also say Y to "MPU-401 support".
10148 Note that the I/O base for MPU-401 support of aedsp16 is the same
10149 you have selected for "MPU-401 support". If you are using this
10150 driver as a module you have to specify the MPU I/O base address with
10151 the parameter 'mpu_base=0xNNN'.
10153 MPU401 IRQ for Audio Excel DSP 16
10154 CONFIG_AEDSP16_MPU_IRQ
10155 This is the IRQ of the MPU-401 emulation of your Audio Excel DSP 16
10156 card. It must be 5, 7, 9, 10 or 0 (to disable MPU-401 interface). If
10157 you compiled aedsp16.o as a module you can specify this parameter as
10160 SGI Visual Workstation on-board audio
10162 Say Y or M if you have an SGI Visual Workstation and you want to
10163 be able to use its on-board audio. Read Documentation/sound/visws
10164 for more info on this driver's capabilities.
10166 Ensoniq ES1370 based PCI sound cards
10167 CONFIG_SOUND_ES1370
10168 Say Y or M if you have a PCI sound card utilizing the Ensoniq
10169 ES1370 chipset, such as Ensoniq's AudioPCI (non-97). To find
10170 out if your sound card uses an ES1370 without removing your
10171 computer's cover, use lspci -n and look for the PCI ID
10172 1274:5000. Since Ensoniq was bought by Creative Labs,
10173 Sound Blaster 64/PCI models are either ES1370 or ES1371 based.
10174 This driver differs slightly from OSS/Free, so PLEASE READ
10175 Documentation/sound/es1370.
10177 Joystick support at boot time
10178 CONFIG_SOUND_ES1370_JOYPORT_BOOT
10179 Say Y here to use the joystick port of your sound card.
10181 Ensoniq ES1371 based PCI sound cards
10182 CONFIG_SOUND_ES1371
10183 Say Y or M if you have a PCI sound card utilizing the Ensoniq
10184 ES1371 chipset, such as Ensoniq's AudioPCI97. To find out if
10185 your sound card uses an ES1371 without removing your computer's
10186 cover, use lspci -n and look for the PCI ID 1274:1371. Since
10187 Ensoniq was bought by Creative Labs, Sound Blaster 64/PCI
10188 models are either ES1370 or ES1371 based. This driver differs
10189 slightly from OSS/Free, so PLEASE READ Documentation/sound/es1371.
10191 Joystick support at boot time
10192 CONFIG_SOUND_ES1371_JOYPORT_BOOT
10193 Say Y here to use the joystick port of your sound card.
10195 Gameport I/O-range selection
10196 CONFIG_SOUND_ES1371_GAMEPORT
10197 Select the I/O-range of the gameport on a ES1371 based sound card.
10198 The card uses 8 ioports and the gameport is available at all eight
10199 ioports. Legal hexadecimal values are 200, 208, 210 and 218.
10200 The joystick driver will by default use 0x201.
10201 Leave the default 200 unless you have a joystick not attached
10202 to your sound card.
10204 ESS Solo1 based PCI sound cards (eg. SC1938)
10205 CONFIG_SOUND_ESSSOLO1
10206 Say Y or M if you have a PCI sound card utilizing the ESS Technology
10207 Solo1 chip. To find out if your sound card uses a
10208 Solo1 chip without removing your computer's cover, use
10209 lspci -n and look for the PCI ID 125D:1969. This driver
10210 differs slightly from OSS/Free, so PLEASE READ
10211 Documentation/sound/solo1.
10213 S3 SonicVibes based PCI sound cards
10214 CONFIG_SOUND_SONICVIBES
10215 Say Y or M if you have a PCI sound card utilizing the S3
10216 SonicVibes chipset. To find out if your sound card uses a
10217 SonicVibes chip without removing your computer's cover, use
10218 lspci -n and look for the PCI ID 5333:CA00. This driver
10219 differs slightly from OSS/Free, so PLEASE READ
10220 Documentation/sound/sonicvibes.
10222 Rockwell WaveArtist
10223 CONFIG_SOUND_WAVEARTIST
10224 Say Y here to include support for the Rockwell WaveArtist sound
10225 system. This driver is mainly for the NetWinder.
10227 Are you using a crosscompiler
10228 CONFIG_CROSSCOMPILE
10229 Say Y here if you are compiling the kernel on a different
10230 architecture than the one it is intended to run on.
10232 Build fp exception handler module
10233 CONFIG_MIPS_FPE_MODULE
10234 Build the floating point exception handler module. This option is
10235 only useful for people working on the floating point exception
10236 handler. If you don't, say N.
10238 Remote GDB kernel debugging
10239 CONFIG_REMOTE_DEBUG
10240 If you say Y here, it will be possible to remotely debug the MIPS
10241 kernel using gdb. This enlarges your kernel image disk size by
10242 several megabytes and requires a machine with more than 16 MB,
10243 better 32 MB RAM to avoid excessive linking time. This is only
10244 useful for kernel hackers. If unsure, say N.
10246 Magic System Request Key support
10248 If you say Y here, you will have some control over the system even
10249 if the system crashes for example during kernel debugging (e.g., you
10250 will be able to flush the buffer cache to disk, reboot the system
10251 immediately or dump some status information). This is accomplished
10252 by pressing various keys while holding SysRq (Alt+PrintScreen). The
10253 keys are documented in Documentation/sysrq.txt. Don't say Y unless
10254 you really know what this hack does.
10258 ISDN ("Integrated Services Digital Networks", called RNIS in France)
10259 is a special type of fully digital telephone service; it's mostly
10260 used to connect to your Internet service provider (with SLIP or
10261 PPP). The main advantage is that the speed is higher than ordinary
10262 modem/telephone connections, and that you can have voice
10263 conversations while downloading stuff. It only works if your
10264 computer is equipped with an ISDN card and both you and your service
10265 provider purchased an ISDN line from the phone company. For details,
10266 read http://alumni.caltech.edu/~dank/isdn/ on the WWW. (To browse
10267 the WWW, you need to have access to a machine on the Internet that
10268 has a program like lynx or netscape.)
10270 This driver allows you to use an ISDN-card for networking
10271 connections and as dialin/out device. The isdn-tty's have a built in
10272 AT-compatible modem emulator. Network devices support autodial,
10273 channel-bundling, callback and caller-authentication without having
10274 a daemon running. A reduced T.70 protocol is supported with tty's
10275 suitable for German BTX. On D-Channel, the protocols EDSS1
10276 (Euro-ISDN) and 1TR6 (German style) are supported. See
10277 Documentation/isdn/README for more information.
10279 If you want to compile the ISDN code as a module ( = code which can
10280 be inserted in and removed from the running kernel whenever you
10281 want), say M here and read Documentation/modules.txt. The module
10282 will be called isdn.o. If unsure, say N.
10284 Support synchronous PPP
10286 Over digital connections such as ISDN, there is no need to
10287 synchronize sender and recipient's clocks with start and stop bits
10288 as is done over analog telephone lines. Instead, one can use
10289 "synchronous PPP". Saying Y here will include this protocol. This
10290 protocol is used by Cisco and Sun for example. So you want to say Y
10291 here if the other end of your ISDN connection supports it. You will
10292 need a special version of pppd (called ipppd) for using this
10293 feature. See Documentation/isdn/README.syncppp and
10294 Documentation/isdn/syncPPP.FAQ for more information.
10296 Support generic MP (RFC 1717)
10298 With synchronous PPP enabled, it is possible to increase throughput
10299 by bundling several ISDN-connections, using this protocol. See
10300 Documentation/isdn/README.syncppp for more information.
10302 Use VJ-compression with synchronous PPP
10304 This enables Van Jacobson header compression for synchronous PPP.
10305 Say Y if the other end of the connection supports it.
10307 Support audio via ISDN
10309 If you say Y here, the modem-emulator will support a subset of the
10310 EIA Class 8 Voice commands. Using a getty with voice-support
10311 (mgetty+sendfax by gert@greenie.muc.de with an extension, available
10312 with the ISDN utility package for example), you will be able to use
10313 your Linux box as an ISDN-answering machine. Of course, this must be
10314 supported by the lowlevel driver also. Currently, the HiSax driver
10315 is the only voice-supporting driver. See
10316 Documentation/isdn/README.audio for more information.
10318 X.25 PLP on top of ISDN (EXPERIMENTAL)
10320 This experimental feature provides the X.25 protocol over ISDN
10321 connections. See Documentation/isdn/README.x25 for more information
10322 if you are thinking about using this.
10324 ISDN diversion services support
10325 CONFIG_ISDN_DIVERSION
10326 This option allows you to use some supplementary diversion
10327 services in conjunction with the HiSax driver on an EURO/DSS1
10328 line. Supported options are CD (call deflection), CFU (Call
10329 forward unconditional), CFB (Call forward when busy) and CFNR
10330 (call forward not reachable).
10331 Additionally the actual CFU, CFB and CFNR state may be
10332 interrogated. The use of CFU, CFB, CFNR and interrogation may
10333 be limited to some countries. The keypad protocol is still not
10335 CD should work in all countries if this service has been sub-
10338 ICN 2B and 4B support
10339 CONFIG_ISDN_DRV_ICN
10340 This enables support for two kinds of ISDN-cards made by a German
10341 company called ICN. 2B is the standard version for a single ISDN
10342 line with two B-channels, 4B supports two ISDN lines. For running
10343 this card, additional firmware is necessary, which has to be
10344 downloaded into the card using a utility which is distributed
10345 separately. See Documentation/isdn/README and README.icn for more
10348 If you want to compile this as a module ( = code which can be
10349 inserted in and removed from the running kernel whenever you want),
10350 say M here and read Documentation/modules.txt. The module will be
10354 CONFIG_ISDN_DRV_LOOP
10355 This driver provides a virtual ISDN card. Its primary purpose is
10356 testing of linklevel features or configuration without getting
10357 charged by your service-provider for lots of phone calls.
10358 You need will need the loopctrl utility from the latest isdn4k-utils
10359 package to set up this driver.
10361 HiSax SiemensChipSet driver support
10362 CONFIG_ISDN_DRV_HISAX
10363 This is a driver supporting the Siemens chipset on various
10364 ISDN-cards (like AVM A1, Elsa ISDN cards, Teles S0-16.0, Teles
10365 S0-16.3, Teles S0-8, Teles/Creatix PnP, ITK micro ix1 and many
10368 HiSax is just the name of this driver, not the name of any hardware.
10370 If you have a card with such a chipset, you should say Y here and
10371 also to the configuration option of the driver for your particular
10374 If you want to compile this as a module ( = code which can be
10375 inserted in and removed from the running kernel whenever you want),
10376 say M here and read Documentation/modules.txt. The module will be
10377 called hisax.o. See Documentation/isdn/README.HiSax for more
10378 information on using this driver.
10380 HiSax Support for Teles 16.0/8.0
10382 This enables HiSax support for the Teles ISDN-cards S0-16.0, S0-8
10383 and many compatibles.
10385 See Documentation/isdn/README.HiSax on how to configure it using the
10386 different cards, a different D-channel protocol, or non-standard
10387 IRQ/port/shmem settings.
10389 HiSax Support for Teles 16.3 or PNP or PCMCIA
10391 This enables HiSax support for the Teles ISDN-cards S0-16.3 the
10392 Teles/Creatix PnP and the Teles PCMCIA.
10394 See Documentation/isdn/README.HiSax on how to configure it using the
10395 different cards, a different D-channel protocol, or non-standard
10398 HiSax Support for Teles 16.3c
10399 CONFIG_HISAX_TELES3C
10400 This enables HiSax support for the Teles ISDN-cards 16.3c.
10402 See Documentation/isdn/README.HiSax on how to configure it using the
10403 different cards, a different D-channel protocol, or non-standard
10406 HiSax Support for AVM A1 (Fritz)
10407 CONFIG_HISAX_AVM_A1
10408 This enables HiSax support for the AVM A1 (aka "Fritz").
10410 See Documentation/isdn/README.HiSax on how to configure it using the
10411 different cards, a different D-channel protocol, or non-standard
10414 HiSax Support for Elsa ISA cards
10416 This enables HiSax support for the Elsa Mircolink ISA cards, for the
10417 Elsa Quickstep series cards and Elsa PCMCIA.
10419 See Documentation/isdn/README.HiSax on how to configure it using the
10420 different cards, a different D-channel protocol, or non-standard
10423 HiSax Support for ITK ix1-micro Revision 2
10424 CONFIG_HISAX_IX1MICROR2
10425 This enables HiSax support for the ITK ix1-micro Revision 2 card.
10427 See Documentation/isdn/README.HiSax on how to configure it using the
10428 different cards, a different D-channel protocol, or non-standard
10431 HiSax Support for Eicon.Diehl Diva cards
10432 CONFIG_HISAX_DIEHLDIVA
10433 This enables HiSax support for the Eicon.Diehl Diva none PRO
10434 versions passive ISDN cards.
10436 See Documentation/isdn/README.HiSax on how to configure it using the
10437 different cards, a different D-channel protocol, or non-standard
10440 HiSax Support for ASUSCOM cards
10441 CONFIG_HISAX_ASUSCOM
10442 This enables HiSax support for the AsusCom and their OEM versions
10443 passive ISDN cards.
10445 See Documentation/isdn/README.HiSax on how to configure it using the
10446 different cards, a different D-channel protocol, or non-standard
10449 HiSax Support for TELEINT cards
10450 CONFIG_HISAX_TELEINT
10451 This enables HiSax support for the TELEINT SA1 semiactiv ISDN card.
10453 See Documentation/isdn/README.HiSax on how to configure it using the
10454 different cards, a different D-channel protocol, or non-standard
10457 HiSax Support for Sedlbauer speed card/win-star
10458 CONFIG_HISAX_SEDLBAUER
10459 This enables HiSax support for the Sedlbauer passive ISDN cards.
10461 See Documentation/isdn/README.HiSax on how to configure it using the
10462 different cards, a different D-channel protocol, or non-standard
10465 HiSax Support for USR Sportster internal TA
10466 CONFIG_HISAX_SPORTSTER
10467 This enables HiSax support for the USR Sportster internal TA card.
10469 See Documentation/isdn/README.HiSax on how to configure it using a
10470 different D-channel protocol, or non-standard IRQ/port settings.
10472 HiSax Support for MIC card
10474 This enables HiSax support for the ITH MIC card.
10476 See Documentation/isdn/README.HiSax on how to configure it using a
10477 different D-channel protocol, or non-standard IRQ/port settings.
10479 HiSax Support for NETjet card
10480 CONFIG_HISAX_NETJET
10481 This enables HiSax support for the NetJet from Traverse
10484 See Documentation/isdn/README.HiSax on how to configure it using a
10485 different D-channel protocol, or non-standard IRQ/port settings.
10487 HiSax Support for Niccy PnP/PCI card
10489 This enables HiSax support for the Dr. Neuhaus Niccy PnP or PCI.
10491 See Documentation/isdn/README.HiSax on how to configure it using a
10492 different D-channel protocol, or non-standard IRQ/port settings.
10494 HiSax Support for Am7930 (EXPERIMENTAL)
10495 CONFIG_HISAX_AMD7930
10496 This enables HiSax support for the AMD7930 chips on some SPARCs.
10497 This code is not finished yet.
10499 HiSax Support for EURO/DSS1
10501 Say Y or N according to the D-channel protocol which your local
10502 telephone service company provides.
10504 NOTE: If you say Y here and you have only one ISDN card installed,
10505 you cannot say Y to "HiSax Support for German 1TR6", below. And vice
10508 Support for German tariff info
10510 If you want that the HiSax hardware driver sends messages to the
10511 upper level of the isdn code on each AOCD (Advice Of Charge, During
10512 the call -- transmission of the fee information during a call) and
10513 on each AOCE (Advice Of Charge, at the End of the call --
10514 transmission of fee information at the end of the call), say Y here.
10515 This works only in Germany.
10517 Support for Australian Microlink service (not for std. EURO)
10519 If you are in Australia and connected to the Microlink telephone
10520 network, enable this, because there are little differences in
10523 Please don't enable this in other countries.
10525 HiSax Support for US/NI-1 (not released yet)
10527 Say Y or N according to the D-channel protocol which your local
10528 telephone service company provides.
10530 HiSax Support for German 1TR6
10532 Say Y or N according to the D-channel protocol which your local
10533 telephone service company provides.
10535 NOTE: If you say Y here and you have only one ISDN card installed,
10536 you cannot say Y to "HiSax Support for EURO/DSS1", above. And vice
10540 CONFIG_ISDN_DRV_PCBIT
10541 This enables support for the PCBIT ISDN-card. This card is
10542 manufactured in Portugal by Octal. For running this card, additional
10543 firmware is necessary, which has to be downloaded into the card
10544 using a utility which is distributed separately. See
10545 Documentation/isdn/README and Documentation/isdn/README.pcbit for
10548 If you want to compile this as a module ( = code which can be
10549 inserted in and removed from the running kernel whenever you want),
10550 say M here and read Documentation/modules.txt. The module will be
10553 Spellcaster support (EXPERIMENTAL)
10555 This enables support for the Spellcaster BRI ISDN boards. This
10556 driver currently builds only in a modularized version ( = code which
10557 can be inserted in and removed from the running kernel whenever you
10558 want, details in Documentation/modules.txt); the module will be
10559 called sc.o. See Documentation/isdn/README.sc and
10560 http://www.spellcast.com for more information (to browse the WWW,
10561 you need to have access to a machine on the Internet that has a
10562 program like lynx or netscape).
10564 Eicon.Diehl active card support
10565 CONFIG_ISDN_DRV_EICON
10566 Say Y here if you have an Eicon active ISDN card. In order to use
10567 this card, additional firmware is necessary, which has to be loaded
10568 into the card using the eiconctrl utility which is part of the latest
10569 isdn4k-utils package. Please read the file
10570 Documentation/isdn/README.eicon for more information.
10572 Eicon old-type card support
10573 CONFIG_ISDN_DRV_EICON_ISA
10574 Say Y here if you have an old-type Eicon active ISDN card. In order to
10575 use this card, additional firmware is necessary, which has to be loaded
10576 into the card using the eiconctrl utility which is part of the latest
10577 isdn4k-utils package. Please read the file
10578 Documentation/isdn/README.eicon for more information.
10580 Support AT-Fax Class 2 commands
10581 CONFIG_ISDN_TTY_FAX
10582 If you say Y here, the modem-emulator will support a subset of the
10583 Fax Class 2 commands. Using a getty with fax-support
10584 (mgetty+sendfax, hylafax), you will be able to use your Linux box
10585 as an ISDN-fax-machine. This must be supported by the lowlevel driver
10586 also. See Documentation/isdn/README.fax for more information.
10588 AVM-B1 with CAPI2.0 support
10589 CONFIG_ISDN_DRV_AVMB1
10590 This enables support for the AVM B1 ISDN networking cards. In
10591 addition, a CAPI (Common ISDN Application Programming Interface, a
10592 standard making it easy for programs to access ISDN hardware, see
10593 http://www.capi.org/; to browse the WWW, you need to have access to
10594 a machine on the Internet that has a program like lynx or netscape)
10595 interface for this card is provided. In order to use this card,
10596 additional firmware is necessary, which has to be downloaded into
10597 the card using a utility which is distributed separately. Please
10598 read the file Documentation/isdn/README.avmb1.
10600 This code is also available as a module ( = code which can be
10601 inserted in and removed from the running kernel whenever you want).
10602 The module will be called avmb1.o. If you want to compile it as a
10603 module, say M here and read Documentation/modules.txt.
10605 Verbose reason code reporting (kernel size +=7K)
10606 CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON
10607 If you say Y here, the AVM B1 driver will give verbose reasons for
10608 disconnecting. This will increase the size of the kernel by 7 KB. If
10611 IBM Active 2000 support (EXPERIMENTAL)
10612 CONFIG_ISDN_DRV_ACT2000
10613 Say Y here if you have an IBM Active 2000 ISDN card. In order to use
10614 this card, additional firmware is necessary, which has to be loaded
10615 into the card using a utility which is part of the latest
10616 isdn4k-utils package. Please read the file
10617 Documentation/isdn/README.act2000 for more information.
10619 Support for AP1000 multicomputer
10621 This enables support for a SPARC based parallel multi-computer
10622 called AP1000+. For details on our efforts to port Linux to this
10623 machine see http://cap.anu.edu.au/cap/projects/linux (to browse the
10624 WWW, you need to have access to a machine on the Internet that has a
10625 program like lynx or netscape) or mail to hackers@cafe.anu.edu.au
10627 Support for Sun4 architecture
10629 Say Y here if, and only if, your machine is a Sun4. Note that
10630 a kernel compiled with this option will run only on Sun4.
10631 (And the current version will probably work only on sun4/330.)
10633 SPARC ESP SCSI support
10635 This is the driver for the Sun ESP SCSI host adapter. The ESP
10636 chipset is present in most SPARC-based computers.
10638 SPARC /dev/openprom compatibility driver
10639 CONFIG_SUN_OPENPROMIO
10640 This driver provides user programs with an interface to the SPARC
10641 PROM device tree. The driver implements a SunOS-compatible
10642 interface and a NetBSD-compatible interface.
10644 If you want to compile this as a module ( = code which can be
10645 inserted in and removed from the running kernel whenever you want),
10646 say M and read Documentation/modules.txt. If unsure, say Y.
10648 Mostek real time clock support
10649 CONFIG_SUN_MOSTEK_RTC
10650 The Mostek RTC chip is used on all knows Sun computers except
10651 some JavaStation-s. For a JavaStation you need to say Y both here
10654 Say Y here unless you are building a special purpose kernel.
10657 #Siemens SAB82532 serial support
10660 ### Please someone fill these in.
10664 # m68k-specific kernel options
10665 # Documented by Chris Lawrence <quango@themall.net> et al.
10669 This option enables support for the Amiga series of computers. If
10670 you plan to use this kernel on an Amiga, say Y here and browse the
10671 material available in Documentation/m68k; otherwise say N.
10675 This option enables support for the 68000-based Atari series of
10676 computers (including the TT, Falcon and Medusa). If you plan to use
10677 this kernel on an Atari, say Y here and browse the material
10678 available in Documentation/m68k; otherwise say N.
10682 This option enables support for the Hades Atari clone. If you plan
10683 to use this kernel on a Hades, say Y here; otherwise say N.
10687 This option enables support for the Apple Macintosh series of
10688 computers (yes, there is experimental support now, at least for part
10691 Say N unless you're willing to code the remaining necessary support.
10696 This option enables support for the HP9000/300 series of
10697 workstations. Support for these machines is still very experimental.
10698 If you plan to try to use the kernel on such a machine say Y here.
10699 Everybody else says N.
10703 This option enables support for the Sun 3 series of workstations.
10704 Be warned that this support is very experimental. You will also
10705 want to say Y to 68020 support and N to the other processors below.
10706 Currently, it is not possible to build a kernel with support for
10707 the Sun 3 and and something else, so make sure you have said N to
10708 all the other machines. This option does not support the sun3x series
10709 of machines (the Sun 3/80 and 3/460). If you don't want to compile a
10710 kernel for a Sun 3, say N.
10714 If you anticipate running this kernel on a computer with a MC68020
10715 processor, say Y. Otherwise, say N. Note that the 68020 requires a
10716 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
10717 Sun 3, which provides its own version.
10721 If you anticipate running this kernel on a computer with a MC68030
10722 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
10723 work, as it does not include an MMU (Memory Management Unit).
10727 If you anticipate running this kernel on a computer with a MC68LC040
10728 or MC68040 processor, say Y. Otherwise, say N. Note that an
10729 MC68EC040 will not work, as it does not include an MMU (Memory
10734 If you anticipate running this kernel on a computer with a MC68060
10735 processor, say Y. Otherwise, say N.
10737 Math emulation support
10739 At some point in the future, this will cause floating-point math
10740 instructions to be emulated by the kernel on machines that lack a
10741 floating-point math coprocessor. Thrill-seekers and chronically
10742 sleep-deprived psychotic hacker types can say Y now, everyone else
10743 should probably wait a while.
10745 Math emulation only kernel
10746 CONFIG_M68KFPU_EMU_ONLY
10747 This option prevents any floating-point instructions from being
10748 compiled into the kernel, thereby the kernel doesn't save any
10749 floating point context anymore during task switches, so this
10750 kernel will only be usable on machines without a floating-point
10751 math coprocessor. This makes the kernel a bit faster as no tests
10752 needs to be executed whether a floating-point instruction in the
10753 kernel should be executed or not.
10755 Math emulation extra precision
10756 CONFIG_M68KFPU_EMU_EXTRAPREC
10757 The fpu uses normally a few bit more during calculations for
10758 correct rounding, the emulator can (often) do the same but this
10759 extra calculation can cost quite some time, so you can disable
10760 it here. The emulator will then "only" calculate with a 64 bit
10761 mantissa and round slightly incorrect, what is more then enough
10764 Advanced processor options
10765 CONFIG_ADVANCED_CPU
10766 This gives you access to some advanced options for the CPU. The
10767 defaults should be fine for most users, but these options may make
10768 it possible for you to improve performance somewhat if you know what
10769 you are doing. Most users should say N to this question.
10771 Use read-modify-write instructions
10773 This allows to use certain instructions that work with indivisible
10774 read-modify-write bus cycles. While this is faster than the
10775 workaround of disabling interrupts, it can conflict with DMA
10776 ( = direct memory access) on many Amiga systems, and it is also said
10777 to destabilize other machines. It is very likely that this will
10778 cause serious problems on any Amiga or Atari Medusa if set. The only
10779 configuration where it should work are 68030-based Ataris, where it
10780 apparently improves performance. But you've been warned! Unless you
10781 really know what you are doing, say N. Try Y only if you're quite
10784 Amiga AutoConfig Identification
10786 This enables support for automatic identification of Amiga expansion
10787 cards that obey the AutoConfig(tm) specification.
10788 Say Y if you want your expansion cards to be identified on bootup;
10789 it will enlarge your kernel by about 10 KB. The identification
10790 information is also available through /proc/zorro (say Y to
10791 "/proc filesystem support"!).
10793 Note that even if you say N here, you can still use your expansion
10794 cards. If in doubt, say Y.
10796 CONFIG_AMIGA_PCMCIA
10797 Include support in the kernel for pcmcia on Amiga 1200 and Amiga 600.
10798 If you intend to use pcmcia cards say Y; otherwise say N.
10800 Amiga GSP (TMS340x0) support
10802 Include support for Amiga graphics cards that use the Texas
10803 Instruments TMS340x0 GSP (Graphics Signal Processor) chips. Say Y
10804 if you want to use a DMI Resolver or Commodore A2410 (Lowell)
10805 graphics card on an Amiga; otherwise, say N.
10807 DMI Resolver support
10808 CONFIG_GSP_RESOLVER
10809 Include support in the kernel for the DMI Resolver graphics card. If
10810 you have one, say Y; otherwise, say N.
10814 Include support in the kernel for the Commodore/University of Lowell
10815 A2410 graphics card. If you have one, say Y; otherwise, say N.
10817 Amiga Zorro II ramdisk support
10819 This enables support for using Chip RAM and Zorro II RAM as a
10820 ramdisk or as a swap partition. Say Y if you want to include this
10821 driver in the kernel. This driver is also available as a module
10822 ( = code which can be inserted in and removed from the running
10823 kernel whenever you want). The module is called z2ram.o. If you want
10824 to compile it as a module, say M here and read
10825 Documentation/modules.txt.
10827 Atari ST-RAM swap support
10829 This enables support for using (parts of) ST-RAM as swap space,
10830 instead of as normal system memory. This can first enhance system
10831 performance if you have lots of alternate RAM (compared to the size
10832 of ST-RAM), because executable code always will reside in faster
10833 memory. ST-RAM will remain as ultra-fast swap space. On the other
10834 hand, it allows much improved dynamic allocations of ST-RAM buffers
10835 for device driver modules (e.g. floppy, ACSI, SLM printer, DMA
10836 sound). The probability that such allocations at module load time
10837 fail is drastically reduced.
10841 This enables support for the Atari ACSI interface. The driver
10842 supports hard disks and CD-ROMs, which have 512-byte sectors, or can
10843 be switched to that mode. Due to the ACSI command format, only disks
10844 up to 1 GB are supported. Special support for certain ACSI to SCSI
10845 adapters, which could relax that, isn't included yet. The ACSI
10846 driver is also the basis for certain other drivers for devices
10847 attached to the ACSI bus: Atari SLM laser printer, BioNet-100
10848 Ethernet, and PAMsNet Ethernet. If you want to use one of these
10849 devices, you need ACSI support, too.
10851 This driver is also available as a module ( = code which can be
10852 inserted in and removed from the running kernel whenever you want).
10853 The module will be called acsi.o.
10855 Probe all LUNs on each ACSI device
10856 CONFIG_ACSI_MULTI_LUN
10857 If you have a ACSI device that supports more than one LUN (Logical
10858 Unit Number), e.g. a CD jukebox, you should say Y here so that all
10859 will be found by the ACSI driver. An ACSI device with multiple LUNs
10860 acts logically like multiple ACSI devices. The vast majority of ACSI
10861 devices have only one LUN, and so most people can say N here and
10862 should in fact do so, because it is safer.
10864 Atari SLM laser printer support
10866 If you have an Atari SLM laser printer, say Y to include support for
10867 it in the kernel. Otherwise, say N. This driver is also available as
10868 a module ( = code which can be inserted in and removed from the
10869 running kernel whenever you want). The module will be called
10870 acsi_slm.o. Be warned: the driver needs much ST-RAM and can cause
10871 problems due to that fact!
10873 A3000 WD33C93A support
10875 If you have an Amiga 3000 and have SCSI devices connected to the
10876 built-in SCSI controller, say Y. Otherwise, say N. This driver is
10877 also available as a module ( = code which can be inserted in and
10878 removed from the running kernel whenever you want). The module is
10879 called wd33c93.o. If you want to compile it as a module, say M here
10880 and read Documentation/modules.txt.
10882 A2091 WD33C93A support
10884 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
10885 say N. This driver is also available as a module ( = code which can
10886 be inserted in and removed from the running kernel whenever you
10887 want). The module is called wd33c93.o. If you want to compile it as
10888 a module, say M here and read Documentation/modules.txt.
10890 GVP Series II WD33C93A support
10892 If you have a Great Valley Products Series II SCSI controller,
10893 answer Y. Also say Y if you have a later model of GVP SCSI
10894 controller (such as the GVP A4008 or a Combo board). Otherwise,
10895 answer N. This driver does NOT work for the T-Rex series of
10896 accelerators from TekMagic and GVP-M.
10898 This driver is also available as a module ( = code which can be
10899 inserted in and removed from the running kernel whenever you
10900 want). The module will be called gvp11.o. If you want to compile it
10901 as a module, say M here and read Documentation/modules.txt.
10903 Cyberstorm SCSI support
10904 CONFIG_CYBERSTORM_SCSI
10905 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
10906 accelerator board and the optional Cyberstorm SCSI controller,
10907 answer Y. Otherwise, say N.
10909 Cyberstorm II SCSI support
10910 CONFIG_CYBERSTORMII_SCSI
10911 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
10912 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
10915 Blizzard 2060 SCSI support
10916 CONFIG_BLZ2060_SCSI
10917 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
10918 and want to use the onboard SCSI controller, say Y. Otherwise,
10921 Blizzard 1230IV/1260 SCSI support
10922 CONFIG_BLZ1230_SCSI
10923 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
10924 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
10927 Blizzard PowerUP 603e+ SCSI support
10928 CONFIG_BLZ603EPLUS_SCSI
10929 If you have an Amiga 1200 with a Phase5 Blizzard PowerUP 603e+
10930 accelerator, say Y. Otherwise, say N.
10932 Fastlane SCSI support
10933 CONFIG_FASTLANE_SCSI
10934 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
10935 one in the near future, say Y to this question. Otherwise, say N.
10937 Atari native SCSI support
10939 If you have an Atari with built-in NCR5380 SCSI controller (TT,
10940 Falcon, ...) say Y to get it supported. Of course also, if you have
10941 a compatible SCSI controller (e.g. for Medusa). This driver is also
10942 available as a module ( = code which can be inserted in and removed
10943 from the running kernel whenever you want). The module is called
10944 atari_scsi.o. If you want to compile it as a module, say M here and
10945 read Documentation/modules.txt. This driver supports both styles of
10946 NCR integration into the system: the TT style (separate DMA), and
10947 the Falcon style (via ST-DMA, replacing ACSI). It does NOT support
10948 other schemes, like in the Hades (without DMA).
10950 Long delays for Toshiba CD-ROMs
10951 CONFIG_ATARI_SCSI_TOSHIBA_DELAY
10952 This option increases the delay after a SCSI arbitration to
10953 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
10954 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
10955 would impact performance a bit, so say N.
10957 Hades SCSI DMA emulator (EXPERIMENTAL)
10959 This option enables code which emulates the TT SCSI DMA chip on the
10960 Hades. This increases the SCSI transfer rates at least ten times
10961 compared to PIO transfers. Note that this code is experimental and
10962 has only been tested on a Hades with a 68060 processor. Before you
10963 use this, make backups of your entire hard disk.
10967 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
10970 This driver is also available as a module ( = code which can be
10971 inserted in and removed from the running kernel whenever you
10972 want). The module is called ariadne.o. If you want to compile it as
10973 a module, say M here and read Documentation/modules.txt.
10977 If you have a Village Tronic Ariadne II Ethernet adapter, say Y.
10980 This driver is also available as a module ( = code which can be
10981 inserted in and removed from the running kernel whenever you
10982 want). The module is called ariadne2.o. If you want to compile it as
10983 a module, say M here and read Documentation/modules.txt.
10987 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
10990 This driver is also available as a module ( = code which can be
10991 inserted in and removed from the running kernel whenever you
10992 want). The module is called a2065.o. If you want to compile it as a
10993 module, say M here and read Documentation/modules.txt.
10997 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
10999 This driver is also available as a module ( = code which can be
11000 inserted in and removed from the running kernel whenever you
11001 want). The module is called hydra.o. If you want to compile it as a
11002 module, say M here and read Documentation/modules.txt.
11004 Pcmcia NE2000 compatible support
11006 If you have a pcmcia ne2000 compatible adapter, say Y. Otherwise,
11009 This driver is also available as a module ( = code which can be
11010 inserted in and removed from the running kernel whenever you
11011 want). The module is called apne.o. If you want to compile it as a
11012 module, say M here and read Documentation/modules.txt.
11014 Atari Lance support
11016 Say Y to include support for several Atari Ethernet adapters based
11017 on the AMD Lance chipset: RieblCard (with or without battery), or
11018 PAMCard VME (also the version by Rhotron, with different addresses).
11021 CONFIG_ATARI_BIONET
11022 Say Y to include support for BioData's BioNet-100 Ethernet adapter
11023 for the ACSI port. The driver works (has to work...) with a polled
11024 I/O scheme, so it's rather slow :-(
11027 CONFIG_ATARI_PAMSNET
11028 Say Y to include support for the PAMsNet Ethernet adapter for the
11029 ACSI port ("ACSI node"). The driver works (has to work...) with a
11030 polled I/O scheme, so it's rather slow :-(
11032 Multiface Card III parallel support
11033 CONFIG_MULTIFACE_III_LP
11034 If you have a Multiface III card for your Amiga, and want to use its
11035 parallel port in Linux, say Y. Otherwise, say N.
11037 This driver is also available as a module ( = code which can be
11038 inserted in and removed from the running kernel whenever you want).
11039 The module is called lp_m68k.o. If you want to compile it as a
11040 module, say M here and read Documentation/modules.txt.
11042 Amiga mouse support
11044 If you want to be able to use an Amiga mouse in Linux, say Y.
11046 This driver is also available as a module ( = code which can be
11047 inserted in and removed from the running kernel whenever you want).
11048 The module is called amigamouse.o. If you want to compile it as a
11049 module, say M here and read Documentation/modules.txt.
11051 Amiga Copper Console
11053 This configures the console to use the Amiga's graphics coprocessor
11054 for scrolling, instead of using the CPU. This option markedly
11055 improves response times in the high color modes (5 bitplanes and
11056 up). If you would like to use this, say Y; otherwise, say N.
11058 Atari mouse support
11060 If you want to be able to use an Atari mouse in Linux, say Y.
11062 This driver is also available as a module ( = code which can be
11063 inserted in and removed from the running kernel whenever you want).
11064 The module is called atarimouse.o. If you want to compile it as a
11065 module, say M here and read Documentation/modules.txt.
11067 Atari MFP serial support
11068 CONFIG_ATARI_MFPSER
11069 If you like to use the MFP serial ports ("Modem1", "Serial1") under
11070 Linux, say Y. The driver equally supports all kinds of MFP serial
11071 ports and automatically detects whether Serial1 is available.
11073 This driver is also available as a module ( = code which can be
11074 inserted in and removed from the running kernel whenever you want).
11075 If you want to compile it as a module, say M here and read
11076 Documentation/modules.txt.
11078 Note for Falcon users: You also have an MFP port, it's just not
11079 wired to the outside... But you could use the port under Linux.
11081 Atari SCC serial support
11083 If you have serial ports based on a Zilog SCC chip (Modem2, Serial2,
11084 LAN) and like to use them under Linux, say Y. All built-in SCC's are
11085 supported (TT, MegaSTE, Falcon), and also the ST-ESCC. If you have
11086 two connectors for channel A (Serial2 and LAN), they are visible as
11087 two separate devices.
11089 This driver is also available as a module ( = code which can be
11090 inserted in and removed from the running kernel whenever you want).
11091 If you want to compile it as a module, say M here and read
11092 Documentation/modules.txt.
11094 Atari SCC serial DMA support
11095 CONFIG_ATARI_SCC_DMA
11096 This enables DMA support for receiving data on channel A of the SCC.
11097 If you have a TT you may say Y here and read
11098 drivers/char/atari_SCC.README. All other users should say N here,
11099 because only the TT has SCC-DMA, even if your machine keeps claiming
11102 Atari MIDI serial support
11104 If you want to use your Atari's MIDI port in Linux, say Y.
11106 This driver is also available as a module ( = code which can be
11107 inserted in and removed from the running kernel whenever you
11108 want). If you want to compile it as a module, say M here and read
11109 Documentation/modules.txt.
11111 Atari DSP56k Digital Signal Processor support
11112 CONFIG_ATARI_DSP56K
11113 If you want to be able to use the DSP56001 in Falcons, say Y. This
11114 driver is still experimental, and if you don't know what it is, or
11115 if you don't have this processor, just say N.
11117 This driver is also available as a module ( = code which can be
11118 inserted in and removed from the running kernel whenever you want).
11119 If you want to compile it as a module, say M here and read
11120 Documentation/modules.txt.
11122 Amiga builtin serial support
11123 CONFIG_AMIGA_BUILTIN_SERIAL
11124 If you want to use your Amiga's built-in serial port in Linux,
11127 This driver is also available as a module ( = code which can be
11128 inserted in and removed from the running kernel whenever you
11129 want). If you want to compile it as a module, say M here and read
11130 Documentation/modules.txt.
11132 GVP IO-Extender support
11134 If you want to use a GVP IO-Extender serial card in Linux, say Y.
11137 Multiface Card III serial support
11138 CONFIG_MULTIFACE_III_TTY
11139 If you want to use a Multiface III card's serial port in Linux,
11142 This driver is also available as a module ( = code which can be
11143 inserted in and removed from the running kernel whenever you want).
11144 If you want to compile it as a module, say M here and read
11145 Documentation/modules.txt.
11147 Amiga or Atari DMA sound support
11149 If you want to use the internal audio of your Atari or Amiga in
11150 Linux, answer Y to this question. This will provide a Sun-like
11151 /dev/audio, compatible with the Linux/i386 sound system. Otherwise,
11154 This driver is also available as a module ( = code which can be
11155 inserted in and removed from the running kernel whenever you
11156 want). If you want to compile it as a module, say M here and read
11157 Documentation/modules.txt.
11159 HP DCA serial support
11161 If you want to use the internal "DCA" serial ports on an HP300
11162 machine, say Y here.
11164 HP on-board LANCE support
11166 If you want to use the builtin "LANCE" Ethernet controller on an
11167 HP300 machine, say Y here.
11169 Sun 3 onboard LANCE support
11171 If you want to use the onboard AMD "LANCE" (le) Ethernet hardware
11172 on a Sun 3, you will need to say Y here.
11176 Say Y here to enable support for the "DIO" expansion bus used in
11177 HP300 machines. If you are using such a system you almost certainly
11180 MSDOS partition support
11181 CONFIG_MSDOS_PARTITION
11182 This option enables support for using hard disks that were
11183 partitioned on an MS-DOS system. This may be useful if you are
11184 sharing a hard disk between i386 and m68k Linux boxes, for example.
11185 Say Y if you need this feature; users who are only using their
11186 system-native partitioning scheme can say N here.
11190 There are two types of PowerPC chips supported. The more common
11191 types (601,603,604,740,750) and the embedded versions (821 and 860).
11192 Unless you are building a kernel for one of the embedded boards
11193 using the 821 or 860 choose 6xx.
11197 Linux currently supports several different kinds of PowerPC-based
11198 machines: Apple Power Macintoshes and clones (such as the Motorola
11199 Starmax series), PReP (PowerPC Reference Platform) machines such as
11200 the Motorola PowerStack, Amiga Power-Up systems (APUS), CHRP and the
11201 embedded MBX boards from Motorola. Currently, a single kernel binary
11202 only supports one type or the other. However, there is very early
11203 work on support for CHRP, PReP and PowerMac's from a single binary.
11205 Support for Open Firmware device tree in /proc
11206 CONFIG_PROC_DEVICETREE
11207 This option adds a device-tree directory under /proc which contains
11208 an image of the device tree that the kernel copies from Open
11209 Firmware. If unsure, say Y here.
11211 MESH (Power Mac internal SCSI) support
11213 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
11214 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
11215 other Power Macintoshes do). Say Y to include support for this SCSI
11216 adaptor. This driver is also available as a module called mesh.o
11217 ( = code which can be inserted in and removed from the running
11218 kernel whenever you want). If you want to compile it as a module,
11219 say M here and read Documentation/modules.txt.
11221 Maximum synchronous transfer rate
11222 CONFIG_SCSI_MESH_SYNC_RATE
11223 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
11224 drives a bus which is entirely internal to the machine (such as the
11225 7500, 7600, 8500, etc.), the MESH is capable of synchronous
11226 operation at up to 10 MB/s. On machines where the SCSI bus
11227 controlled by the MESH can have external devices connected, it is
11228 usually rated at 5 MB/s. 5 is a safe value here unless you know the
11229 MESH SCSI bus is internal only; in that case you can say 10. Say 0
11230 to disable synchronous operation.
11232 53C94 (Power Mac external SCSI) support
11233 CONFIG_SCSI_MAC53C94
11234 On Power Macintoshes (and clones) with two SCSI buses, the external
11235 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
11236 machines which only have one SCSI bus, such as the 7200, also use
11237 the 53C94. Say Y to include support for the 53C94.
11239 This driver is also available as a module called mac53c94.o ( = code
11240 which can be inserted in and removed from the running kernel
11241 whenever you want). If you want to compile it as a module, say M
11242 here and read Documentation/modules.txt.
11244 MACE (Power Mac Ethernet) support
11246 Power Macintoshes and clones with Ethernet built-in on the
11247 motherboard will usually use a MACE (Medium Access Control for
11248 Ethernet) interface. Say Y to include support for the MACE chip.
11250 This driver is also available as a module called mace.o ( = code
11251 which can be inserted in and removed from the running kernel
11252 whenever you want). If you want to compile it as a module, say M
11253 here and read Documentation/modules.txt.
11255 BMAC (G3 ethernet) support
11257 Say Y for support of BMAC Ethernet interfaces. These are used on G3
11260 This driver is also available as a module called bmac.o ( = code
11261 which can be inserted in and removed from the running kernel
11262 whenever you want). If you want to compile it as a module, say M
11263 here and read Documentation/modules.txt.
11267 Support for audio/video capture and overlay devices and FM radio
11268 cards. The exact capabilities of each device vary. User tools for
11269 this are available from
11270 ftp://ftp.uk.linux.org/pub/linux/video4linux.
11272 If you are interested in writing a driver for such an audio/video
11273 device or user software interacting with such a driver, please read
11274 the file Documentation/video4linux/API.html.
11276 This driver is also available as a module called videodev.o ( = code
11277 which can be inserted in and removed from the running kernel
11278 whenever you want). If you want to compile it as a module, say M
11279 here and read Documentation/modules.txt.
11281 Direct Rendering Manager (XFree86 DRI support)
11283 Kernel-level support for the Direct Rendering Infrastructure (DRI)
11284 introduced in XFree86 4.x. These modules provide support for
11285 synchronization, security, and DMA transfers. Select the module that
11286 provides support for your graphics card.
11288 3dlabs GMX 2000 Direct Rendering Driver (XFree86 DRI support)
11290 Choose M here if you have a 3dlabs GMX 2000 graphics card.
11292 AIMSlab RadioTrack (aka RadioReveal) support
11293 CONFIG_RADIO_RTRACK
11294 Choose Y here if you have one of these FM radio cards, and then fill
11295 in the port address below.
11297 Note that newer AIMSlab RadioTrack cards have a different chipset
11298 and are not supported by this driver. For these cards, use the
11299 RadioTrack II driver below.
11301 In order to control your radio card, you will need to use programs
11302 that are compatible with the Video for Linux API. Information on
11303 this API and pointers to "v4l" programs may be found on the WWW at
11304 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
11305 you need to have access to a machine on the Internet that has a
11306 program like lynx or netscape. More information is contained in the
11307 file Documentation/video4linux/radiotrack.txt.
11309 If you want to compile this driver as a module ( = code which can be
11310 inserted in and removed from the running kernel whenever you want),
11311 say M here and read Documentation/modules.txt. The module will be
11312 called radio-aimslab.o.
11314 RadioTrack i/o port
11315 CONFIG_RADIO_RTRACK_PORT
11316 Enter either 0x30f or 0x20f here. The card default is 0x30f, if you
11317 haven't changed the jumper setting on the card.
11319 AIMSlab RadioTrack II support
11320 CONFIG_RADIO_RTRACK2
11321 Choose Y here if you have this FM radio card, and then fill in the
11322 port address below.
11324 If you have GemTeks combined (PnP) sound- and radio card you must use
11325 this driver as a module and setup the card with isapnptools. You must
11326 also pass the module a suitable io parameter, 0x248 has been reported
11327 to be used by these cards.
11329 In order to control your radio card, you will need to use programs
11330 that are compatible with the Video for Linux API. Information on
11331 this API and pointers to "v4l" programs may be found on the WWW at
11332 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
11333 you need to have access to a machine on the Internet that has a
11334 program like lynx or netscape.
11336 If you want to compile this driver as a module ( = code which can be
11337 inserted in and removed from the running kernel whenever you want),
11338 say M here and read Documentation/modules.txt. The module will be
11339 called radio-rtrack2.o.
11341 RadioTrack II i/o port
11342 CONFIG_RADIO_RTRACK2_PORT
11343 Enter either 0x30c or 0x20c here. The card default is 0x30c, if you
11344 haven't changed the jumper setting on the card.
11346 Aztech/Packard Bell Radio
11347 CONFIG_RADIO_AZTECH
11348 Choose Y here if you have one of these FM radio cards, and then fill
11349 in the port address below.
11351 In order to control your radio card, you will need to use programs
11352 that are compatible with the Video for Linux API. Information on
11353 this API and pointers to "v4l" programs may be found on the WWW at
11354 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
11355 you need to have access to a machine on the Internet that has a
11356 program like lynx or netscape.
11358 If you want to compile this driver as a module ( = code which can be
11359 inserted in and removed from the running kernel whenever you want),
11360 say M here and read Documentation/modules.txt. The module will be
11361 called radio-aztech.o.
11363 Aztech/Packard Bell radio card i/o port
11364 CONFIG_RADIO_AZTECH_PORT
11365 Enter either 0x350 or 0x358 here. The card default is 0x350, if you
11366 haven't changed the setting of jumper JP3 on the card. Removing the
11367 jumper sets the card to 0x358.
11370 CONFIG_RADIO_SF16FMI
11371 Choose Y here if you have one of these FM radio cards, and then fill
11372 in the port address below.
11374 In order to control your radio card, you will need to use programs
11375 that are compatible with the Video for Linux API. Information on
11376 this API and pointers to "v4l" programs may be found on the WWW at
11377 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
11378 you need to have access to a machine on the Internet that has a
11379 program like lynx or netscape.
11381 If you want to compile this driver as a module ( = code which can be
11382 inserted in and removed from the running kernel whenever you want),
11383 say M here and read Documentation/modules.txt. The module will be
11384 called radio-sf16fmi.o
11386 SF16FMI I/O port (0x284 or 0x384)
11387 CONFIG_RADIO_SF16FMI_PORT
11388 Enter the I/O port of your SF16FMI radio card.
11391 CONFIG_RADIO_TYPHOON
11392 Choose Y here if you have one of these FM radio cards, and then fill
11393 in the port address and the frequency used for muting below.
11395 In order to control your radio card, you will need to use programs
11396 that are compatible with the Video for Linux API. Information on
11397 this API and pointers to "v4l" programs may be found on the WWW at
11398 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
11399 you need to have access to a machine on the Internet that has a
11400 program like lynx or netscape.
11402 If you want to compile this driver as a module ( = code which can be
11403 inserted in and removed from the running kernel whenever you want),
11404 say M here and read Documentation/modules.txt. The module will be
11405 called radio-typhoon.o
11407 Support for /proc/radio-typhoon
11408 CONFIG_RADIO_TYPHOON_PROC_FS
11409 Say Y here if you want the typhoon radio card driver to write
11410 status information (frequency, volume, muted, mute frequency,
11411 base address) to /proc/radio-typhoon. The file can be viewed with
11412 your favorite pager (i.e. use "more /proc/radio-typhoon" or "less
11413 /proc/radio-typhoon" or simply "cat /proc/radio-typhoon").
11415 Typhoon I/O port (0x316 or 0x336)
11416 CONFIG_RADIO_TYPHOON_PORT
11417 Enter the I/O port of your Typhoon or EcoRadio radio card.
11419 Typhoon frequency set when muting the device (kHz)
11420 CONFIG_RADIO_TYPHOON_MUTEFREQ
11421 Enter the frequency used for muting the radio. The device is never
11422 completely silent. If the volume is just turned down, you can still
11423 hear silent voices and music. For that reason, the frequency of the
11424 radio device is set to the frequency you can enter here whenever
11425 the device is muted. There should be no local radio station at that
11429 CONFIG_RADIO_ZOLTRIX
11430 Choose Y here if you have one of these FM radio cards, and then fill
11431 in the port address below.
11433 In order to control your radio card, you will need to use programs
11434 that are compatible with the Video for Linux API. Information on
11435 this API and pointers to "v4l" programs may be found on the WWW at
11436 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
11437 you need to have access to a machine on the Internet that has a
11438 program like lynx or netscape.
11440 If you want to compile this driver as a module ( = code which can be
11441 inserted in and removed from the running kernel whenever you want),
11442 say M here and read Documentation/modules.txt. The module will be
11443 called radio-zoltrix.o
11445 ZOLTRIX I/O port (0x20c or 0x30c)
11446 CONFIG_RADIO_ZOLTRIX_PORT
11447 Enter the I/O port of your Zoltrix radio card.
11449 ADS Cadet AM/FM Tuner
11451 Say Y here if this is your AM/FM radio card.
11453 In order to control your radio card, you will need to use programs
11454 that are compatible with the Video for Linux API. Information on
11455 this API and pointers to "v4l" programs may be found on the WWW at
11456 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
11457 you need to have access to a machine on the Internet that has a
11458 program like lynx or netscape.
11460 If you want to compile this driver as a module ( = code which can be
11461 inserted in and removed from the running kernel whenever you want),
11462 say M here and read Documentation/modules.txt. The module will be
11463 called radio-cadet.o
11466 CONFIG_RADIO_MIROPCM20
11467 Choose Y here if you have this FM radio card. You also need to say Y
11468 to "ACI mixer (miroPCM12/PCM20)" (in "additional low level sound
11469 drivers") for this to work.
11471 In order to control your radio card, you will need to use programs
11472 that are compatible with the Video for Linux API. Information on
11473 this API and pointers to "v4l" programs may be found on the WWW at
11474 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
11475 you need to have access to a machine on the Internet that has a
11476 program like lynx or netscape.
11478 If you want to compile this driver as a module ( = code which can be
11479 inserted in and removed from the running kernel whenever you want),
11480 say M here and read Documentation/modules.txt. The module will be
11481 called radio-miropcm20.o
11484 CONFIG_RADIO_GEMTEK
11485 Choose Y here if you have this FM radio card, and then fill in the
11486 port address below.
11488 In order to control your radio card, you will need to use programs
11489 that are compatible with the Video for Linux API. Information on
11490 this API and pointers to "v4l" programs may be found on the WWW at
11491 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
11492 you need to have access to a machine on the Internet that has a
11493 program like lynx or netscape.
11495 If you want to compile this driver as a module ( = code which can be
11496 inserted in and removed from the running kernel whenever you want),
11497 say M here and read Documentation/modules.txt. The module will be
11498 called radio-gemtek.o.
11501 CONFIG_RADIO_GEMTEK_PORT
11502 Enter either 0x20c, 0x30c, 0x24c or 0x34c here. The card default is
11503 0x34c, if you haven't changed the jumper setting on the card.
11505 PlanB Video-In for PowerMacs
11507 PlanB is the V4L driver for the PowerMac 7x00/8x00 series video
11508 input hardware. If you want to experiment with this, say Y.
11509 Otherwise, or if you don't understand a word, say N.
11510 See http://www.cpu.lu/~mlan/planb.html for more info.
11512 Saying M will compile this driver as a module (planb.o).
11514 TerraTec ActiveRadio
11515 CONFIG_RADIO_TERRATEC
11516 Choose Y here if you have this FM radio card, and then fill in the
11517 port address below. (TODO)
11519 Note: This driver is in its early stages. Right now volume and frequency
11520 control and muting works at least for me, but unfortunately i have not
11521 found anybody who wants to use this card with linux. So if it is this
11522 what YOU are trying to do right now, PLEASE DROP ME A NOTE!!
11523 Rolf Offermanns (rolf@offermanns.de)
11525 In order to control your radio card, you will need to use programs
11526 that are compatible with the Video for Linux API. Information on
11527 this API and pointers to "v4l" programs may be found on the WWW at
11528 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
11529 you need to have access to a machine on the Internet that has a
11530 program like lynx or netscape.
11533 If you want to compile this driver as a module ( = code which can be
11534 inserted in and removed from the running kernel whenever you want),
11535 say M here and read Documentation/modules.txt. The module will be
11536 called radio-terratec.o.
11539 BT848 Video For Linux
11541 Support for BT848 based frame grabber/overlay boards. This includes
11542 the Miro, Hauppauge and STB boards. Please read the material in
11543 Documentation/video4linux/bttv for more information.
11545 This driver is also available as a module called bttv.o ( = code
11546 which can be inserted in and removed from the running kernel
11547 whenever you want). If you want to compile it as a module, say M
11548 here and read Documentation/modules.txt.
11550 SAA5249 Teletext processor
11551 CONFIG_VIDEO_SAA5249
11552 Support for I2C bus based teletext using the SAA5249 chip. At the
11553 moment this is only useful on some European WinTV cards.
11555 This driver is also available as a module called saa5249.o ( = code
11556 which can be inserted in and removed from the running kernel
11557 whenever you want). If you want to compile it as a module, say M
11558 here and read Documentation/modules.txt.
11560 Quickcam BW Video For Linux
11561 CONFIG_VIDEO_BWQCAM
11562 Say Y have if you the black and white version of the QuickCam
11563 camera. See the next option for the color version.
11565 This driver is also available as a module called bw-qcam.o ( = code
11566 which can be inserted in and removed from the running kernel
11567 whenever you want). If you want to compile it as a module, say M
11568 here and read Documentation/modules.txt.
11570 Colour QuickCam Video For Linux
11572 This is the video4linux driver for the colour version of the
11573 Connectix Quickcam. If you have one of these cameras, say Y here,
11574 otherwise say N. This driver does not work with the original
11575 monochrome Quickcam, Quickcam VC or QuickClip. It is also available
11576 as a module (c-qcam.o).
11578 Mediavision Pro Movie Studio Video For Linux
11580 Say Y if you have such a thing. This driver is also available as a
11581 module called pms.o ( = code which can be inserted in and removed
11582 from the running kernel whenever you want). If you want to compile
11583 it as a module, say M here and read Documentation/modules.txt.
11585 Compaq SMART2 support
11587 This is the driver for Compaq Smart Array controllers.
11588 Everyone using these boards should say Y here.
11589 See "linux/Documentation/cpqarray.txt" for the current list of
11590 boards supported by this driver, and for further information
11591 on the use of this driver.
11598 This selects the processor type of your CPU. This is only used to
11599 determine C compiler optimization options, and can affect the
11600 compatibility of the kernel on other processors. If you specify
11601 ARM6, the kernel should work on all 32-bit processors. If you
11602 specify ARM2, ARM250 or ARM3, it should work on all 26-bit
11603 processors. If you're not sure, set it to "None".
11607 This selects what ARM system you wish to build the kernel for. It
11608 also selects to some extent the CPU type. If you are unsure what
11609 to set this option to, please consult any information supplied with
11612 Include support for Chalice CATS boards
11614 Say Y here if you intend to run this kernel on a CATS system.
11616 Include support for Intel EBSA285
11617 CONFIG_ARCH_EBSA285
11618 Say Y here if you intend to run this kernel on an EBSA-285 evaluation
11621 Include support for the NetWinder
11622 CONFIG_ARCH_NETWINDER
11623 Say Y here if you intend to run this kernel on the NetWinder.
11627 Say Y to include the NWFPE floating point emulator in the kernel. This
11628 is necessary to run most binaries. Linux does not currently support
11629 floating point hardware so you need to say Y here even if your machine
11630 has an FPA or floating point co-processor podule.
11632 It is also possible to say M to build the emulator as a module
11633 (nwfpe.o) or indeed to leave it out altogether. However, unless you
11634 know what you are doing this can easily render your machine unbootable.
11635 Saying Y is the safe option.
11637 You may say N here if you are going to load the Acorn FPEmulator
11638 early in the bootup.
11640 DS1620 Thermometer support
11642 Say Y here to include support for the thermal management hardware
11643 found in the NetWinder. This driver allows the user to control the
11644 temperature set points and to read the current temperature.
11646 It is also possible to say M here to build it as a module (ds1620.o)
11647 It is recommended to be used on a NetWinder, but it is not a
11650 Verbose kernel error messages
11651 CONFIG_DEBUG_ERRORS
11652 This option controls verbose debugging information which can be
11653 printed when the kernel detects an internal error. This debugging
11654 information is useful to kernel hackers when tracking down problems,
11655 but mostly meaningless to other people. It's safe to say Y unless
11656 you are concerned with the code size or don't want to see these
11659 Compile kernel with frame pointer
11660 CONFIG_FRAME_POINTER
11661 If you say Y here, the resulting kernel will be slightly larger and
11662 slower, but it will give useful debugging information. If you don't
11663 debug the kernel, you can say N.
11665 User fault debugging
11667 When a user program crashes due to an exception, the kernel can print
11668 a brief message explaining what the problem was. This is sometimes
11669 helpful for debugging but serves no purpose on a production system.
11670 Most people should say N here.
11672 Include gdb debugging information in kernel binary
11674 Say Y here to include source-level debugging information in the
11675 `vmlinux' binary image. This is handy if you want to use gdb or
11676 addr2line to debug the kernel. It has no impact on the in-memory
11677 footprint of the running kernel but it can increase the amount of
11678 time and disk space needed for compilation. If in doubt say N.
11680 Split initialisation functions into discardable section
11681 CONFIG_TEXT_SECTIONS
11682 Normally code that is only used during initialisation is collected
11683 into a special area of the kernel so that it can be discarded and
11684 the memory reclaimed when initialisation is complete. In addition,
11685 if the kernel you wish to build is able to run on multiple
11686 architectures, it allows the unused code to be discarded. Some
11687 versions of binutils, however, have a bug that causes the kernel
11688 to crash during startup when this option is enabled. Say Y unless
11689 you experience problems that you suspect may be caused by this.
11691 Disable pgtable cache
11692 CONFIG_NO_PGT_CACHE
11693 Normally the kernel maintains a `quicklist' of preallocated pagetable
11694 structures in order to increase performance. On machines with very
11695 few pages this may however be a loss. Say Y here to disable the pgtable
11698 RISC OS personality
11700 Say Y here to include the kernel code necessary if you want to run
11701 Acorn RISC OS/Arthur binaries under Linux. This code is still very
11702 experimental; if this sounds frightening, say N and sleep in peace.
11703 You can also say M here to compile this support as a module (which
11704 will be called arthur.o).
11706 Initial kernel command line
11708 On some architectures (EBSA110 and CATS), there is currently no way
11709 for the boot loader to pass arguments to the kernel. For these
11710 architectures, you should supply some command-line options at build
11711 time by entering them here. As a minimum, you should specify the
11712 memory size and the root device (eg, mem=64M root=/dev/nfs)
11714 Hardware alignment trap
11715 CONFIG_ALIGNMENT_TRAP
11716 ARM processors can not fetch/store information which is not naturally
11717 aligned on the bus, ie, a 4 byte fetch must start at an address divisable
11718 by 4. On 32-bit ARM processors, these instructions can be emulated in
11719 software with a severe performance impact. This is necessary for correct
11720 operation of some network protocols. With an IP-only configuration
11721 it is safe to say N, otherwise say Y.
11723 21285 serial port support
11724 CONFIG_SERIAL_21285
11725 If you have a machine based on a 21285 (Footbridge) StrongARM/PCI
11726 bridge you can enable its onboard serial port by enabling this
11727 option. The device has major ID 4, minor 64.
11729 Console on 21285 serial port
11730 CONFIG_SERIAL_21285_CONSOLE
11731 If you have enabled the serial port on the 21285 footbridge you can
11732 make it the console by answering 'Y' to this option.
11735 CONFIG_HOST_FOOTBRIDGE
11736 The 21285 Footbridge chip can operate in either `host mode' or
11737 `add-in' mode. Say Y if your 21285 is in host mode, and therefore
11738 is the configuration master, otherwise say N. This must not be
11739 set to 'Y' if the card is used in 'add-in' mode.
11741 MFM harddisk support
11743 Support the MFM hard drives on the Acorn Archimedes both
11744 on-board the A4x0 motherboards and via the Acorn MFM podules.
11745 Drives upto 64MB are supported. If you haven't got one of these
11746 machines or drives just say 'N'.
11748 Old Archimedes floppy (1772) support
11749 CONFIG_BLK_DEV_FD1772
11750 Support the floppy drive on the Acorn Archimedes (A300, A4x0, A540,
11751 R140 and R260) series of computers; it supports only 720K floppies
11752 at the moment. If you don't have one of these machines just answer
11755 Autodetect hard drive geometry
11756 CONFIG_BLK_DEV_MFM_AUTODETECT
11757 If you answer 'Y' the MFM code will attempt to automatically detect
11758 the cylinders/heads/sectors count on your hard drive. WARNING: This
11759 sometimes doesn't work and it also does some dodgy stuff which
11760 potentially might damage your drive.
11764 Say Y here if you want to build support for the IrDA (TM) protocols.
11765 The Infrared Data Associations (tm) specifies standards for wireless
11766 infrared communication and is supported by most laptops and PDA's.
11768 To use Linux support for the IrDA (tm) protocols, you will also need
11769 some user-space utilities like the irmanager and probably irattach
11770 as well. For more information, see the file
11771 Documentation/networking/irda.txt. You also want to read the
11772 IR-HOWTO, available from
11773 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO.
11775 This support is also available as a module. If you want to compile
11776 it as a module, say M here and read Documentation/modules.txt. The
11777 module will be called
11779 IrDA Cache last LSAP
11780 CONFIG_IRDA_CACHE_LAST_LSAP
11781 Say Y here if you want IrLMP to cache the last LSAP used. This makes
11782 sense since most frames will be sent/received on the same
11783 connection. Enabling this option will save a hash-lookup per frame.
11788 CONFIG_IRDA_FAST_RR
11789 Say Y here is you want IrLAP to send fast RR (Receive Ready) frames
11790 when acting as a primary station. This will make IrLAP send out a RR
11791 frame immediately when receiving a frame if its own transmit queue
11792 is currently empty. This will give a lot of speed improvement when
11793 receiving much data since the secondary station will not have to
11794 wait the max. turn around time before it is allowed to transmit the
11795 next time. If the transmit queue of the secondary is also empty the
11796 primary will back off waiting longer for sending out the RR frame
11797 until the timeout reaches the normal value. Enabling this option
11798 will make the IR-diode burn more power and thus reduce your battery
11805 Say Y here if you want the IrDA subsystem to write debug information
11806 to your syslog. You can change the debug level in
11807 /proc/sys/net/irda/debug
11809 If unsure, say Y (since it makes it easier to find the bugs).
11811 IrLAP Compression support
11812 CONFIG_IRDA_COMPRESSION
11813 Compression is _not_ part of the IrDA(tm) protocol specification,
11814 but it's working great! Linux is the first to try out compression
11815 support at the IrLAP layer. This means that you will only benefit
11816 from compression if you are running a Linux <-> Linux configuration.
11818 If you say Y here, you also need to say Y or M to a compression
11821 IrLAP Deflate Compression Protocol
11822 CONFIG_IRDA_DEFLATE
11823 Say Y here if you want to build support for the Deflate compression
11824 protocol. The deflate compression (GZIP) is exactly
11825 the same as the one used by the PPP protocol.
11827 If you want to compile this compression support as a module, say M
11828 here and read Documentation/modules.txt. The module will be called
11833 Say Y here if you want to build support for the IrLAN protocol. If
11834 you want to compile it as a module, say M here and read
11835 Documentation/modules.txt. IrLAN emulates an Ethernet and makes it
11836 possible to put up a wireless LAN using infrared beams.
11838 The IrLAN protocol can be used to talk with infrared access points
11839 like the HP NetbeamIR, or the ESI JetEye NET. You can also connect
11840 to another Linux machine running the IrLAN protocol for ad-hoc
11845 Say Y here if you want to build support for the IrCOMM protocol. If
11846 you want to compile it as a module, say M here and read
11847 Documentation/modules.txt. IrCOMM implements serial port emulation,
11848 and makes it possible to use all existing applications that
11849 understands TTY's with an infrared link. Thus you should be able to
11850 use application like PPP, minicom and others. Enabling this option
11851 will create two modules called ircomm and ircomm_tty. For more
11852 information go to http://www.pluto.dti.ne.jp/~thiguchi/irda/
11854 IrTTY IrDA Device Driver
11856 Say Y here if you want to build support for the IrTTY line
11857 discipline. If you want to compile it as a module, say M here and
11858 read Documentation/modules.txt. IrTTY makes it possible to use
11859 Linux's own serial driver for all IrDA ports that are 16550
11860 compatible. Most IrDA chips are 16550 compatible so you should
11861 probably say Y to this option. Using IrTTY will however limit the
11862 speed of the connection to 115200 bps (IrDA SIR mode)
11866 IrPORT IrDA Device Driver
11868 Say Y here if you want to build support for the IrPORT IrDA device
11869 driver. If you want to compile it as a module, say M here and
11870 read Documentation/modules.txt. IrPORT can be used instead of
11871 IrTTY and sometimes this can be better. One example is if your
11872 IrDA port does not have echo-canceling, which will work OK with
11873 IrPORT since this driver is working in half-duplex mode only. You
11874 don't need to use irattach with IrPORT, but you just insert it
11875 the same way as FIR drivers (insmod irport io=0x3e8 irq=11).
11876 Notice that IrPORT is a SIR device driver which means that speed
11877 is limited to 115200 bps.
11881 Winbond W83977AF IrDA Device Driver
11883 Say Y here if you want to build IrDA support for the Winbond
11884 W83977AF super-io chipset. If you want to compile it as a module,
11885 say M here and read Documentation/modules.txt. This driver should be
11886 used for the IrDA chipset in the Corel NetWinder. The driver
11887 supports SIR, MIR and FIR (4Mbps) speeds.
11889 NSC PC87108 IrDA Device Driver
11891 Say Y here if you want to build support for the NSC PC87108 IrDA
11892 chipset. If you want to compile it as a module, say M here and
11893 read Documentation/modules.txt. This drivers currently only supports
11894 the ACTiSYS IR2000B ISA card and supports SIR, MIR and FIR (4Mbps)
11897 Sharp UIRCC IrDA Device Driver
11899 Say Y here if you want to build support for the Sharp UIRCC IrDA
11900 chipset. If you want to compile it as a module, say M here and
11901 read Documentation/modules.txt. This chipset is used by the Toshiba
11904 Toshiba Type-O IR Port Device Driver
11906 Say Y here if you want to build support for the Toshiba Type-O IR
11907 chipset. If you want to compile it as a module, say M here and
11908 read Documentation/modules.txt. This chipset is used by the Toshiba
11909 Libretto 100CT, and many more laptops.
11911 ESI JetEye PC Dongle
11913 Say Y here if you want to build support for the Extended Systems
11914 JetEye PC dongle. If you want to compile it as a module, say M here
11915 and read Documentation/modules.txt. The ESI dongle attaches to the
11916 normal 9-pin serial port connector, and can currently only be used
11917 by IrTTY. To activate support for ESI dongles you will have to
11918 insert "irattach -d esi" in the /etc/irda/drivers script.
11920 ACTiSYS IR-220L and IR220L+ dongle
11921 CONFIG_ACTISYS_DONGLE
11922 Say Y here if you want to build support for the ACTiSYS
11923 IR-220L and IR220L+ dongles. If you want to compile it as a module,
11924 say M here and read Documentation/modules.txt. The ACTiSYS dongles
11925 attaches to the normal 9-pin serial port connector, and can
11926 currently only be used by IrTTY. To activate support for ACTiSYS
11927 dongles you will have to insert "irattach -d actisys" or
11928 "irattach -d actisys_plus" in the/etc/irda/drivers script.
11930 Tekram IrMate 210B dongle
11931 CONFIG_TEKRAM_DONGLE
11932 Say Y here if you want to build support for the Tekram IrMate 210B
11933 dongle. If you want to compile it as a module, say M here
11934 and read Documentation/modules.txt. The Tekram dongle attaches to
11935 the normal 9-pin serial port connector, and can currently only be
11936 used by IrTTY. To activate support for Tekram dongles you will have
11937 to insert "irattach -d tekram" in the /etc/irda/drivers script.
11939 Greenwich GIrBIL dongle
11940 CONFIG_GIRBIL_DONGLE
11941 Say Y here if you want to build support for the Greenwich GIrBIL
11942 dongle. If you want to compile it as a module, say M here and read
11943 Documentation/modules.txt. The Greenwich dongle attaches to the
11944 normal 9-pin serial port connector, and can currently only be used
11945 by IrTTY. To activate support for Greenwich dongles you will have to
11946 insert "irattach -d girbil" in the /etc/irda/drivers script.
11948 Adaptec Airport 1000 and 2000 dongle
11949 CONFIG_AIRPORT_DONGLE
11950 Say Y here if you want to build support for the Adaptec Airport 1000
11951 and 2000 dongles. If you want to compile it as a module, say M here
11952 and read Documentation/modules.txt. The Airport dongle attaches to
11953 the normal 9-pin serial port connector, and can currently only be
11954 used by IrTTY. To activate support for Airport dongles you will have
11955 to insert "irattach -d airport" in the /etc/irda/drivers script.
11957 Parallax Litelink dongle
11958 CONFIG_LITELINK_DONGLE
11959 Say Y here if you want to build support for the Parallax Litelink
11960 dongle. If you want to compile it as a module, say M here and read
11961 Documentation/modules.txt. The Parallax dongle attaches to the
11962 normal 9-pin serial port connector, and can currently only be used
11963 by IrTTY. To activate support for Parallax dongles you will have to
11964 insert "irattach -d litelink" in the /etc/irda/drivers script.
11966 VME (Motorola and BVM) support
11968 Say Y here if you want to build a kernel for a 680x0 based VME
11969 board. Boards currently supported include Motorola boards MVME162,
11970 MVME166, MVME167, MVME172, and MVME177. BVME4000 and BVME6000
11971 boards from BVM Ltd are also supported.
11973 MVME162, 166 and 167 support
11975 Say Y to include support for Motorola VME boards. This will build a
11976 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
11977 MVME177 boards. If you select this option you will have to select
11978 the appropriate drivers for SCSI, Ethernet and serial ports later
11981 BVME4000 and BVME6000 support
11983 Say Y to include support for VME boards from BVM Ltd. This will
11984 build a kernel which can run on BVME4000 and BVME6000 boards. If
11985 you select this option you will have to select the appropriate
11986 drivers for SCSI, Ethernet and serial ports later on.
11988 Use write-through caching for 68060 supervisor accesses
11989 CONFIG_060_WRITETHROUGH
11990 The 68060 generally uses copyback caching of recently accessed data.
11991 Copyback caching means that memory writes will be held in an on-chip
11992 cache and only written back to memory some time later. Saying Y
11993 here will force supervisor (kernel) accesses to use writethrough
11994 caching. Writethrough caching means that data is written to memory
11995 straight away, so that cache and memory data always agree.
11996 Writethrough caching is less efficient, but is needed for some
11997 drivers on 68060 based systems where the 68060 bus snooping signal
11998 is hardwired on. The 53c710 SCSI driver is known to suffer from
12001 NCR53C710 SCSI driver for MVME16x
12002 CONFIG_MVME16x_SCSI
12003 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
12004 SCSI controller chip. Almost everyone using one of these boards
12005 will want to say Y to this question.
12007 NCR53C710 SCSI driver for BVME6000
12008 CONFIG_BVME6000_SCSI
12009 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
12010 SCSI controller chip. Almost everyone using one of these boards
12011 will want to say Y to this question.
12013 MVME16x Ethernet support
12015 This is the driver for the Ethernet interface on the Motorola
12016 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
12017 driver for this chip in your kernel. If you want to compile it as
12018 a module, say M here and read Documentation/modules.txt.
12020 BVME6000 Ethernet support
12021 CONFIG_BVME6000_NET
12022 This is the driver for the Ethernet interface on BVME4000 and
12023 BVME6000 VME boards. Say Y here to include the driver for this chip
12024 in your kernel. If you want to compile it as a module, say M here
12025 and read Documentation/modules.txt.
12027 CD2401 support for MVME166/7 serial ports
12029 This is the driver for the serial ports on the Motorola MVME166,
12030 167, and 172 boards. Everyone using one of these boards should say
12033 SCC support for MVME162 serial ports
12035 This is the driver for the serial ports on the Motorola MVME162 and
12036 172 boards. Everyone using one of these boards should say Y here.
12038 SCC support for BVME6000 serial ports
12039 CONFIG_BVME6000_SCC
12040 This is the driver for the serial ports on the BVME4000 and BVME6000
12041 boards from BVM Ltd. Everyone using one of these boards should say
12044 Universal Serial Bus (USB) Support (Experimental)
12046 This will enable support for the Universal Serial Bus (USB). USB
12047 allows you to connect up to 127 external devices such as keyboards,
12048 mice, printers and modems to your computer through a USB connector.
12049 This code can also be built as a module (i.e. code outside the
12050 kernel that can be added and removed at runtime), consult
12051 Documentation/modules.txt for more information.
12053 UHCI (intel PIIX4 and others) support
12055 The UHCI is the USB host controller for many computers, and is built
12056 into all recent boards with intel PCI chipsets. This driver is
12057 needed for these motherboards to support USB.
12059 OHCI (compaq and some others) support
12061 The OHCI (Open Host Controller Interface) is the USB host controller
12062 on most non-Intel architectures, several USB-adding PCI cards, and
12063 is on several x86 compatibles with non-Intel chipsets. This driver
12064 is needed for these motherboards to support USB. There is presently
12065 two OHCI drivers in development. Say 'N' here if you would like to
12066 compile the other OHCI driver into the linux kernel.
12068 OHCI-HCD (other OHCI opt. Virt. Root Hub) support
12069 CONFIG_USB_OHCI_HCD
12070 The OHCI (Open Host Controller Interface) is the USB host controller
12071 on most non-Intel architectures, several USB-adding PCI cards, and
12072 is on several x86 compatibles with non-Intel chipsets. This driver
12073 is needed for these motherboards to support USB. There is presently
12074 two OHCI drivers in development.
12078 To expand beyond the USB ports on the computer, a device called a
12079 hub is used. This driver supports hubs, allowing them to be used.
12084 This driver allows mice to work under the USB stack. It currently
12085 patches into /dev/ps2aux, although it does not require the ps2
12086 mouse code to be included in the kernel as well.
12088 USB keyboard support
12090 This driver allows USB keyboards to work under the USB stack.
12092 USB audio parsing support (Preliminary)
12094 This driver will eventually handle audio devices, such
12097 USB Communications Device Class (ACM) support (Preliminary)
12099 This driver handles devices which support the Abstract Control Model,
12100 a subtype of the USB Communications Device Class. This includes many
12101 USB-based modems and ISDN adapters. Add special files with:
12102 mknod /dev/ttyACM0 c 166 0
12103 mknod /dev/ttyACM1 c 166 1
12104 mknod /dev/ttyACM2 c 166 2
12105 mknod /dev/ttyACM3 c 166 3
12107 USB Printer Device Class support (Preliminary)
12109 This is a generic driver for USB printers.
12111 USS720 parport driver
12113 This driver is for USB parallel port adapters that use the
12114 Lucent Technologies USS-720 chip.
12116 The chip has two modes: automatic mode and manual mode.
12117 In automatic mode, it looks like a standard USB printer. Only
12118 Printers may be connected to the USS-720 in this mode.
12119 The generic USB printer driver (CONFIG_USB_PRINTER, above)
12120 may be used in that mode.
12122 Manual mode is not limited to printers, any parallel port
12123 device should work. This driver utilizes manual mode.
12124 Note however that some operations are three orders of a magnitude
12125 slower than on a PCI/ISA Parallel Port, so timing critical
12126 applications might not work.
12128 Say Y or M if you own an USS-720 USB->Parport cable and
12129 intend to connect anything other than a printer to it.
12131 USB /proc filesystem entry support (Preliminary)
12133 This reports USB drivers and devices in the /proc filesystem.
12134 Entries are located in /proc/bus/usb.
12135 Note that you must enable support for the proc filesystem
12138 Support for user-space parallel port device drivers
12140 Saying Y to this adds support for /dev/parport device nodes. This
12141 is needed for programs that want low-level access to the parallel
12142 port, for instance deviceid (which displays Plug-and-Play device
12143 IDs) and vlp (which makes a Linux computer act as though it's a
12146 This is the parallel port equivalent of SCSI generic support (sg).
12147 It is safe to say N to this -- it is not needed for normal printing
12148 or parallel port CD-ROM/disk support.
12150 Kernel httpd acceleration (experimental)
12152 The kernel httpd acceleration daemon (kHTTPd) is a (limited)
12153 webserver build into the kernel. It is limited since it can only
12154 serve files from the filesystem. Saying "M" here builds the
12155 kHTTPd module; this is NOT enough to have a working kHTTPd.
12156 For safety reasons, the module has to be activated by doing a
12157 "echo 1 > /proc/sys/net/khttpd/start" after inserting the module.
12159 Before using this, read the README in /usr/src/linux/net/khttpd !
12161 The kHTTPd is experimental. Be careful when using it on a production
12162 machine. Also note that kHTTPd doesn't support virtual servers yet.
12166 # A couple of things I keep forgetting:
12167 # capitalize: AppleTalk, Ethernet, DOS, DMA, FAT, FTP, Internet,
12168 # Intel, IRQ, Linux, MSDOS, NetWare, NetWinder, NFS,
12170 # two words: hard drive, hard disk, sound card, home page
12171 # other: it's safe to save; daemon; use --, not - or ---
12174 # This is used by Emacs' spell checker ispell.el:
12176 # LocalWords: CONFIG coprocessor DX Pentium SX lilo loadlin HOWTO ftp metalab
12177 # LocalWords: unc edu docs emu README kB BLK DEV FD Thinkpad fd MFM RLL IDE gz
12178 # LocalWords: cdrom diskless netboot nfs xzvf ATAPI MB ide pavia rubini pl pd
12179 # LocalWords: HD CDROMs IDECD NEC MITSUMI filesystem XT XD PCI BIOS cezar ATEN
12180 # LocalWords: ISA EISA Microchannel VESA BIOSes IPC SYSVIPC ipc Ctrl dmesg hlt
12181 # LocalWords: BINFMT Linkable http ac uk jo html GCC SPARC AVANTI CABRIOLET EB
12182 # LocalWords: netscape gcc LD CC toplevel MODVERSIONS insmod rmmod modprobe IP
12183 # LocalWords: genksyms INET loopback gatewaying ethernet PPP ARP Arp MEMSIZE
12184 # LocalWords: howto multicasting MULTICAST MBONE firewalling ipfw ACCT resp ip
12185 # LocalWords: proc acct IPIP encapsulator decapsulator klogd PCTCP RARP EXT PS
12186 # LocalWords: telnetting subnetted NAGLE rlogin NOSR ttyS TGA techinfo mbone nl
12187 # LocalWords: Mb SKB IPX Novell dosemu Appletalk DDP ATALK vmalloc visar ehome
12188 # LocalWords: SD CHR scsi thingy SG CD LUNs LUN jukebox Adaptec BusLogic EATA
12189 # LocalWords: buslogic DMA DPT ATT eata dma PIO UltraStor fdomain umsdos ext
12190 # LocalWords: QLOGIC qlogic TMC seagate Trantor ultrastor FASST wd NETDEVICES
12191 # LocalWords: unix BBS linux CSLIP PLIP Kirch's LDP CSlip SL SCC IRQ csustan
12192 # LocalWords: Turbo Laplink plip NCSA port's ReQuest IRQs EQL SMC AMD PCnet NE
12193 # LocalWords: COM ELPLUS Com EtherLinkIII VLB Arcnet Cabletron DEPCA DE carlos
12194 # LocalWords: depca EtherWorks EWRK ewrk SEEQ EtherExpress EEXPRESS NI xxx dia
12195 # LocalWords: EtherExpress WaveLAN wavelan PCLAN HPLAN VG SK Ansel Xen de ZNET
12196 # LocalWords: PCMCIA cb stanford LAN TEC RealTek ATP atp DLINK NetTools VISWS
12197 # LocalWords: TR Sony CDU caddyless cdu Mitsumi MCD cd mcd XA MultiSession CDA
12198 # LocalWords: Matsushita Panasonic SBPCD Soundblaster Longshine sbpcd Aztech
12199 # LocalWords: Okano Wearnes AZTCD CDD SE aztcd sonycd Goldstar GSCD Philips fs
12200 # LocalWords: LMS OPTCD Sanyo SJCD minix faqs xiafs XIA msdos mtools Cichocki
12201 # LocalWords: std softlinks umssync NetworkFileSharing nfsd mountd CDs HPFS TI
12202 # LocalWords: hpfs SYSV SCO iBCS Wyse WordPerfect tsx mit unixes sysv NR irisa
12203 # LocalWords: SMB WfW Cyclades async mux Logitech busmouse MouseSystem aka AST
12204 # LocalWords: PSMOUSE Compaq trackballs Travelmate Inport ATIXL ATI busmice ld
12205 # LocalWords: gpm config QIC DYNCONF FTAPE Stor Ftape ftape pcsndrv manpage NT
12206 # LocalWords: readprofile diskdrives org com masq EtherTalk tcp netrom sunacm
12207 # LocalWords: misc AIC aic pio scc Portmaster eql GIS PhotoCDs MCDX Perell PG
12208 # LocalWords: mcdx gscd optcd sjcd ISP hdparm Workgroups Lan samba PARIDE PCD
12209 # LocalWords: filesystems smbfs ATA ppp PCTech RZ www powerquest txt CMD ESDI
12210 # LocalWords: chipset FB multicast MROUTE appletalk ifconfig IBMTR multiport
12211 # LocalWords: Multisession STALDRV EasyIO EC EasyConnection ISTALLION ONboard
12212 # LocalWords: Brumby pci TNC cis ohio faq usenet NETLINK dev hydra ca Tyne mem
12213 # LocalWords: carleton Deskstation DECstation SUNFD JENSEN Noname XXXM SLiRP
12214 # LocalWords: pppd Zilog ZS SRM bootloader ez mainmenu rarp ipfwadm paride pcd
12215 # LocalWords: RTNETLINK mknod xos MTU lwared Macs mac netatalk macs cs Wolff
12216 # LocalWords: dartmouth flowerpt MultiMaster FlashPoint tudelft etherexpress
12217 # LocalWords: ICL EtherTeam ETH IDESCSI TXC SmartRAID SmartCache httpd sjc dlp
12218 # LocalWords: thesphere TwoServers BOOTP DHCP ncpfs BPQETHER BPQ MG HIPPI cern
12219 # LocalWords: bsd comp SPARCstation le SunOS ie Gracilis PackeTwin PT pt LU FX
12220 # LocalWords: FX TEAC CR LCS mS ramdisk IDETAPE cmd fperllo encis tcfs unisa
12221 # LocalWords: Vertos Genoa Funai hsfs NCP NetWare tgz APM apm ioctls UltraLite
12222 # LocalWords: TravelMate CDT LCD backlight VC RPC Mips AXP barlow cdrecord pg
12223 # LocalWords: PMAX MILO Alphas Multia Tseng linuxelf endian mipsel mips drv HT
12224 # LocalWords: kerneld callouts AdvanSys advansys Admin WDT DataStor EP verden
12225 # LocalWords: wdt hdb hdc bugfix SiS vlb Acculogic CSA DTC dtc Holtek ht QDI
12226 # LocalWords: QD qd UMC umc ALI ali lena fnet fr azstarnet cdr fb MDA ps esdi
12227 # LocalWords: Avanti XL AlphaStations Jensen DECpc AXPpci UDB Cabriolet MCA RC
12228 # LocalWords: AlphaPC mca AOUT OUTput PPro sipx gwdg lo nwe FourPort Boca unm
12229 # LocalWords: Keepalive linefill RELCOM keepalive analogue CDR conf CDI INIT
12230 # LocalWords: OPTi isp irq noisp VFAT vfat NTFS losetup dmsdosfs dosfs ISDN MP
12231 # LocalWords: NOWAYOUT behaviour dialin isdn callback BTX Teles ICN EDSS Cisco
12232 # LocalWords: ipppd syncppp RFC MPP VJ downloaded icn NICCY Creatix shmem ufr
12233 # LocalWords: ibp md ARCnet ether encap NDIS arcether ODI Amigas AmiTCP NetBSD
12234 # LocalWords: initrd tue util DES funet des OnNet BIOSP smc Travan Iomega CMS
12235 # LocalWords: FC DC dc PPA IOMEGA's ppa RNFS FMV Fujitsu ARPD arpd loran layes
12236 # LocalWords: FRAD indiana framerelay DLCI DCLIs Sangoma SDLA mrouted sync sec
12237 # LocalWords: Starmode Metricom MosquitoNet mosquitonet kbit nfsroot Digiboard
12238 # LocalWords: DIGI Xe Xeve digiboard UMISC touchscreens mtu ethernets HBAs MEX
12239 # LocalWords: Shifflett netcom js jshiffle WIC DECchip ELCP EtherPower dst RTC
12240 # LocalWords: rtc SMP lp Digi Intl RightSwitch DGRS dgrs AFFS Amiga UFS SDL AP
12241 # LocalWords: Solaris RISCom riscom syncPPP PCBIT pcbit sparc anu au artoo MFB
12242 # LocalWords: hitchcock Crynwr cnam pktdrvr NCSA's CyDROM CyCDROM FreeBSD NeXT
12243 # LocalWords: NeXTstep disklabel disklabels SMD FFS tm AmigaOS diskfiles Un IQ
12244 # LocalWords: Bernd informatik rwth aachen uae affs multihosting bytecode java
12245 # LocalWords: applets applet JDK ncsa cabi SNI Alphatronix readme LANs scarab
12246 # LocalWords: winsock RNIS caltech OSPF honour Honouring Mbit LocalTalk DEFRAG
12247 # LocalWords: localtalk download Packetwin Baycom baycom interwork ASCII JNT
12248 # LocalWords: Camtec proxying indyramp defragment defragmented UDP FAS FASXX
12249 # LocalWords: FastSCSI SIO FDC qlogicfas QLogic qlogicisp setbaycom ife ee LJ
12250 # LocalWords: ethz ch Travelmates ProAudioSpectrum ProAudio SoundMan SB SBPro
12251 # LocalWords: Thunderboard SM OPL FM ADLIB TSR Gravis MPU PSS ADI SW DSP codec
12252 # LocalWords: ADSP ESC ASIC daughtercard GUSMAX MSS NX AdLib Excell Ensoniq YM
12253 # LocalWords: SoundScape Spea MediaTriX AudioTriX WSS OTI ThunderBoard VoxWare
12254 # LocalWords: Soundscape SSCAPE TRIX MediaTrix PnP Maui dsp midixx EIA getty
12255 # LocalWords: mgetty sendfax gert greenie muc lowlevel Lasermate LanManager io
12256 # LocalWords: OOPSes trackball binghamton mobileip ncr IOMAPPED settags ns ser
12257 # LocalWords: setsync NEGO MPARITY autotuning prefetch PIIX cdwrite utils rc
12258 # LocalWords: PCWATCHDOG berkprod bitgate boldt ucsb jf kyoto jp euc Tetsuyasu
12259 # LocalWords: YAMADA tetsu cauchy nslab ntt nevod perm su doc kaf kheops wsc
12260 # LocalWords: traduc Bourgin dbourgin menuconfig kfill READMEs HOWTOs Virge WA
12261 # LocalWords: IDEDISK IDEFLOPPY EIDE firewalls QMAGIC ZMAGIC LocalWords opti
12262 # LocalWords: SVGATextMode vga svga Xkernel syr jmwobus comfaqs dhcp flakey GD
12263 # LocalWords: IPv IPng interoperability ipng ipv radio's tapr pkthome PLP nano
12264 # LocalWords: Ses Mhz sethdlc SOUNDMODEM WindowsSoundSystem smdiag pcf inka ES
12265 # LocalWords: smmixer ptt circ soundmodem MKISS FDDI DEFEA DEFPA DEFXX redhat
12266 # LocalWords: HyperNews khg mconv sed lina wuftpd MicroChannel netlink irc cum
12267 # LocalWords: raudio RealAudio PPROP NETBIOS GUI IBMMCA ELMC Racal Interlan fi
12268 # LocalWords: eth shapecfg src esp PCWD PREVSTAT bootparam sig bitwizard SBC
12269 # LocalWords: downloads AFSK TCM FP Karn KA FSK RUH LinkSys cron mouseman LLC
12270 # LocalWords: SyQuest SyQuest's CCITT MicroSolutions BPCD bpcd ESPSERIAL PROM
12271 # LocalWords: SUNESP openprom OPENPROMIO quango themall al TT MC MMU LC RMW AA
12272 # LocalWords: INSNS Ataris AutoConfig ZORRO OCS AMIFB Agnus Denise ECS CDTV GB
12273 # LocalWords: AGA Cybervision CYBER GSP TMS DMI Zorro ACSI ROMs SLM BioNet GVP
12274 # LocalWords: PAMsNet TekMagic Cyberstorm MkI CYBERSTORMII MkII BLZ onboard cx
12275 # LocalWords: Village Tronic ATARILANCE RieblCard PAMCard VME MFP sangoma LAPB
12276 # LocalWords: Rhotron BioData's Multiface AMIGAMOUSE COPCON Amiga's bitplanes
12277 # LocalWords: ATARIMOUSE MFPSER SCC's MegaSTE ESCC Atari's GVPIOEXT DMASOUND
12278 # LocalWords: fdutils cisco univercd rpcg htm iface lapb LAPBETHER tpqic qic
12279 # LocalWords: SYNTH xd en binfmt aout ipip terra ipx sd sr sg wic framebuffer
12280 # LocalWords: ibmmca lapbether mkiss dlci sdla fmv eepro eexpress ni hp ne es
12281 # LocalWords: ibmtr isofs ROMFS romfs pcxx cyclades istallion psaux msbusmouse
12282 # LocalWords: atixlmouse sbin softdog pcwd USS Lite ACI miroSOUND PCM miroPCM
12283 # LocalWords: microcontroller miro Voxware downloading teles acsi slm gvp ltpc
12284 # LocalWords: atari ariadne amigamouse atarimouse builtin IPDDP maths bradford
12285 # LocalWords: AppleTalk Farallon PhoneNet Zubkoff lnz SCCB HAPN WANs vesafb nt
12286 # LocalWords: wanrouter WANPIPE multiprotocol Mbps wanpipe EtherWORKS nodma SC
12287 # LocalWords: smp HiSax SiemensChipSet Siemens AVM Elsa ITK hisax PCC MICROR
12288 # LocalWords: Mircolink EURO DSS Spellcaster BRI sc spellcast Digiboards GPIO
12289 # LocalWords: SYMBIOS COMPAT SDMS rev ASUS Tekram HX VX API ibmmcascsi ASY asy
12290 # LocalWords: loader's PCnetPCI automounter AUTOFS amd autofs VT Gallant's Pnp
12291 # LocalWords: AEDSP aedsp enskip tik Sysctl sysctl PARPORT parport pnp IDs EPP
12292 # LocalWords: Autoprobe bart patrickr HDLS READBACK AB usr DAMA DS SparQ aten
12293 # LocalWords: Symbios PCscsi tmscsim RoamAbout GHz Hinds contrib mathematik ok
12294 # LocalWords: darmstadt okir DIGIEPCA International's Xem digiepca epca bootup
12295 # LocalWords: zorro CAPI AVMB capi avmb VP SYN syncookies EM em pc Ethertalk
12296 # LocalWords: Dayna DL Daynatalk LT PhoneNET ATB Daystar queueing CMDS SCBs ls
12297 # LocalWords: SCB STATS Thinnet ThunderLAN TLAN Netelligent NetFlex tlan james
12298 # LocalWords: caldera Preload Preloading slowdowns schoebel uni NBD nbd prog
12299 # LocalWords: stuttgart rdist TRANS hostnames mango jukeboxes ESS userland PD
12300 # LocalWords: hardlinked NAMETRANS env mtab fstab umount nologin runlevel gid
12301 # LocalWords: transname filespace adm Nodename hostname uname Kernelname bootp
12302 # LocalWords: KERNNAME kname ktype kernelname Kerneltype KERNTYPE Alt RX mdafb
12303 # LocalWords: dataless kerneltype SYSNAME Comtrol Rocketport palmtop fbset EGS
12304 # LocalWords: nvram SYSRQ SysRq PrintScreen sysrq NVRAMs NvRAM Shortwave RTTY
12305 # LocalWords: hayes TX TMOUT
12306 # LocalWords: IDEPCI IDEDMA idedma PDC pdc TRM trm raidtools luthien nuclecu
12307 # LocalWords: unam mx miguel koobera uic EMUL solaris pp ieee lpsg co DMAs TOS
12308 # LocalWords: BLDCONFIG preloading jumperless BOOTINIT modutils multipath GRE
12309 # LocalWords: misconfigured autoconfiguration IPGRE ICMP tracert ipautofw PIM
12310 # LocalWords: netis rlynch autofw ipportfw monmouth ipsubs portforwarding pimd
12311 # LocalWords: portfw PIMSM netweb usc pim pf EUI aggregatable PB decapsulate
12312 # LocalWords: ipddp Decapsulation DECAP bool HAMRADIO tcpdump af CDs tx FBCON
12313 # LocalWords: ethertap multisession PPC MMIO GDT GDTH ICP gdth hamradio bpp
12314 # LocalWords: lmh weejock AIMSlab RadioTrack RTRACK HZP OptoSCC TRX rx TRXECHO
12315 # LocalWords: DMASCC paccomm dmascc addr cfg oevsv oe kib picpar FDX baudrate
12316 # LocalWords: baudrates fdx HDX hdx PSK kanren frforum QoS SCHED CBQ SCH sched
12317 # LocalWords: sch cbq CSZ Shenker Zhang csz SFQ sfq TBF tbf PFIFO fifo PRIO RW
12318 # LocalWords: prio Micom xIO dwmw rimi OMIRR omirr omirrd unicode ntfs cmu NIC
12319 # LocalWords: Braam braam Schmidt's freiburg nls codepages codepage Romanian
12320 # LocalWords: Slovak Slovenian Sorbian Nordic iso Catalan Faeroese Galician SZ
12321 # LocalWords: Valencian Slovene Esperanto Estonian Latvian Byelorussian KOI mt
12322 # LocalWords: charset Inuit Greenlandic Sami Lappish koi SOFTCURSOR softcursor
12323 # LocalWords: Specialix specialix DTR RTS RTSCTS cycladesZ Exabyte ftape's inr
12324 # LocalWords: Iomega's LBFM claus ZFTAPE VFS zftape zft William's lzrw DFLT kb
12325 # LocalWords: MTSETBLK MTIOCTOP qft setblk zftape's tar's afio's setdrvbuffer
12326 # LocalWords: Procfs Exabyte's THR FCD sysvinit init PSC pscwdt VMIDI Euro SAB
12327 # LocalWords: Mostek Fastlane PowerMac PReP PMAC PowerPC Macintoshes Starmax
12328 # LocalWords: PowerStack Starmaxes MCOMMON DEVICETREE ATY IMS IMSTT videodev
12329 # LocalWords: BT Hauppauge STB bttv Quickcam BW BWQCAM bw qcam Mediavision PMS
12330 # LocalWords: pms Avatar Freecom Imation Superdisk BPCK bpck COMM comm DSTR ru
12331 # LocalWords: dstr EPAT EPEZ epat EPIA epia FreeCom FRPW frpw KingByte KBIC HW
12332 # LocalWords: KingByte's kbic OnSpec ValuStore FASTROUTE fastroute FLOWCONTROL
12333 # LocalWords: struct APIC realtime OSs LynxOS CNC tmp cvf HFS hfs ADFS Risc os
12334 # LocalWords: adfs ncpmount namespace SUBDIR reexport NDS kcore FT SPX spx DAT
12335 # LocalWords: interserver BLKSZ NUMBUFFERS apmd Tadpole ANA roestock QuickCam
12336 # LocalWords: isapnptools Colour CQCAM colour Connectix QuickClip prive mentre
12337 # LocalWords: KMOD kmod conformant utexas kharker UnixWare Mwave cgi cl ts ibm
12338 # LocalWords: eXchange threepio oakland simtel pre ULTRAMCA EtherLink isa luik
12339 # LocalWords: EtherLink OpenBSD pts DEVPTS devpts ptmx ttyp glibc readback SA
12340 # LocalWords: mwave OLDCARD isdnloop linklevel loopctrl Eicon Diehl DIEHLDIVA
12341 # LocalWords: ASUSCOM AsusCom TELEINT semiactiv Sedlbauer Sportster TA MIC ITH
12342 # LocalWords: NETjet NetJet Niccy Neuhaus sparcs AOC AOCD AOCE Microlink SAA
12343 # LocalWords: teletext WinTV saa iproute tc Quadra Performa PowerBook tor AUN
12344 # LocalWords: setserial compsoc steve Econet econet AUNUDP psched TEQL TLE CLS
12345 # LocalWords: teql FW Ingres TwistedPair MTRR MTRRs mtrr cfs crypto TD ktti KT
12346 # LocalWords: PHd ICS ipchains adelaide rustcorp syslog Cumana steganography
12347 # LocalWords: AcornSCSI EcoSCSI EESOX EESOXSCSI Powertec POWERTECSCSI dec SF
12348 # LocalWords: RadioReveal gatekeeper aimslab aztech FMI sf fmi RTL rtl cesdis
12349 # LocalWords: Yellowfin gsfc nasa gov yellowfin pcnet Mylex LNE lne EtherH hs
12350 # LocalWords: EBSA chattr RiscOS Winmodem AGP Atomwide DUALSP pcsp robinson CT
12351 # LocalWords: SGALAXY Waverider DSPxxx TRXPRO AudioTrix OSWF MOT CFB DSY kbps
12352 # LocalWords: tuwien kkudielk LVD mega lun MAXTAGS Gbps arcnet Olicom SKTR SNA
12353 # LocalWords: SysKonnect sktr sna etherboot ufs NetBEUI MultiSound MSNDCLAS GX
12354 # LocalWords: MSNDINIT MSNDPERM MSNDPIN PNDSPINI PNDSPERM Ensoniq's RetinaZ SS
12355 # LocalWords: AudioPCI lspci SonicVibes sonicvibes SPARCs roadrunner CLgen UPA
12356 # LocalWords: swansea shtml Zoltrix zoltrix BINUTILS EGCS binutils VIDC DACs
12357 # LocalWords: CyberVision Cirrus PowerBooks Topcat SBUS CGsix TurboGX BWtwo SS
12358 # LocalWords: CGthree TCX unswapable vfb fbcon hicolor truecolor AFB ILBM SOC
12359 # LocalWords: IPLAN gracilis Fibre SBus SparcSTORAGE SV jnewbigin swin QNX qnx
12360 # LocalWords: PTY PTYS ptyxx ttyxx PTYs ssh sb Avance ALS pss pvv kerneli hd
12361 # LocalWords: synth WaveFront MSND NONPNP AudioExcelDSP STRAM APUS CHRP MBX Nx
12362 # LocalWords: PowerMac's BMAC radiotrack rtrack miropcm OFFBOARD HPT UDMA DVD
12363 # LocalWords: hpt fokus gmd Cyrix DXL SLC DLC NexGen MediaGX GXm IDT WinChip
12364 # LocalWords: MMX MII valkyrie mdacon vdolive VDOLive cuseeme CU hippi rrunner
12365 # LocalWords: SeeMe ipmasqadm juanjox ipmarkfw markfw TNCs Microdyne rhine lib
12366 # LocalWords: libc jsX gamepad gameport CHF FCS FPGaming MadCatz ASSASIN GrIP
12367 # LocalWords: Assasin gamepads GamePad PDPI gamecards gamecard WingMan BSP WCS
12368 # LocalWords: ThunderPad CyberMan SideWinder ThrustMaster DirectConnect NES XF
12369 # LocalWords: Millenium SNES PSX Multisystem Nintendo PlayStation Amstrad CPC
12370 # LocalWords: Sega TurboGraFX Steffen Schwenke Multiststem PDIF FIFOSIZE EPLUS
12371 # LocalWords: PowerUP RoadRunner tahallah dos functionkey setterm imladris Woz
12372 # LocalWords: PowerMacs Winbond Algorithmics ALGOR algor ECOFF IRIX SGI SGI's
12373 # LocalWords: gfx virtualized Xpmac mklinux XFree FBDev Woodhouse mvhi Seeq fp
12374 # LocalWords: SGISEEQ HIgh ADB ADBMOUSE crosscompiler CROSSCOMPILE FPE GDB gdb
12375 # LocalWords: JOYPORT rp spoofing DawiControl NOGENSUPP EEPROM HSSI Alessandro
12376 # LocalWords: singleprocessor tex MATHEMU FRIQ Maxell friq Alcor XLT AlphaBook
12377 # LocalWords: AlphaPCI DP LX Miata Mikasa Noritake RPX UX BX Takara EV PRIMO
12378 # LocalWords: TSC Matrox Productiva matroxfb matrox multihead ia linuxhq MFW
12379 # LocalWords: mfw AAA MCS Initio XXU initio imm AutoDetect IZIP CTR usec HDLC
12380 # LocalWords: COSA SRP muni cz kas cosa Alteon AceNIC acenic VTOC OSes GMT SAx
12381 # LocalWords: Inspiron localtime INTS Thinkpads Ralf Brown's Flightstick NNN
12382 # LocalWords: Xterminator Blackhawk NN mpu ioports DCA HPDCA HPLANCE DIO Corel
12383 # LocalWords: GemTek gemtek CMDLINE IrDA PDA's irmanager irattach RR AVA DN rg
12384 # LocalWords: uit dagb irda LSAP IrLMP RR's IrLAP IR alloc skb's kfree skb's
12385 # LocalWords: GZIP IrLAN NetbeamIR ESI JetEye IrOBEX IrCOMM TTY's minicom dti
12386 # LocalWords: ircomm ircomm pluto thiguchi IrTTY Linux's bps NetWinder MIR NSC
12387 # LocalWords: ACTiSYS Dongle dongle dongles esi actisys IrMate tekram BVM MVME
12388 # LocalWords: BVME BVME WRITETHROUGH copyback writethrough fwmark syncookie tu
12389 # LocalWords: alphalinux GOBIOS csn chemnitz nat ACARD AMI MegaRAID megaraid
12390 # LocalWords: QNXFS ISI isicom xterms Apollos VPN RCPCI rcpci sgi visws pcmcia
12391 # LocalWords: IrLPT UIRCC Tecra