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, maintained by the JF Project (JF@linux.or.jp), at
9 # http://www.linux.or.jp/JF/JFdocs/Configure.help/
10 # - Russian, by kaf@linux.nevod.perm.su, at
11 # http://nevod.perm.su/service/linux/doc/kernel/Configure.help
12 # - French, by Tane Pierre (tanep@bigfoot.com), at
13 # http://www.kernelfr.org
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 SuSE, at http://www.suse.de/~ke/kernel . This patch
21 # includes infrastructure to support different languages as well.
23 # To access a document on the WWW, you need to have a direct Internet
24 # connection and a browser program such as netscape or lynx. If you
25 # only have email access, you can still use FTP and WWW servers: send
26 # an email to mail-server@rtfm.mit.edu with the text
27 # send usenet/news.answers/internet-services/access-via-email
28 # in the body of the message.
30 # Information about what a kernel is, what it does, how to patch and
31 # compile it and much more is contained in the Kernel-HOWTO, available
32 # at http://metalab.unc.edu/mdw/linux.html#howto . Before you start
33 # compiling, make sure that you have the necessary versions of all
34 # programs and libraries required to compile and run this kernel; they
35 # are listed in the file Documentation/Changes. Make sure to read the
36 # toplevel kernel README file as well.
38 # Format of this file: description<nl>variable<nl>help text<nl><nl>. If
39 # the question being documented is of type "choice", we list only the
40 # first occurring config variable. The help texts may contain empty
41 # lines, but every non-empty line must be indented two positions.
42 # Order of the help texts does not matter, however, no variable should
43 # be documented twice: if it is, only the first occurrence will be
44 # used by Configure. We try to keep the help texts of related variables
45 # close together. Lines starting with `#' are ignored. To be nice to
46 # menuconfig, limit your line length to 70 characters. Use emacs'
47 # kfill.el to edit and ispell.el to spell check this file or you lose.
49 # If you add a help text to this file, please try to be as gentle as
50 # possible. Don't use unexplained acronyms and generally write for the
51 # hypothetical ignorant but intelligent user who has just bought a PC,
52 # removed Windows, installed Linux and is now recompiling the kernel
53 # for the first time. Tell them what to do if they're unsure. Technical
54 # information should go in a README in the Documentation directory.
55 # Mention all the relevant READMEs and HOWTOs in the help text.
56 # Repetitions are fine since the help texts are not meant to be read
59 # All this was shamelessly stolen from several different sources. Many
60 # thanks to all the contributors. Feel free to use these help texts in
61 # your own kernel configuration tools. The texts are copyrighted (c)
62 # 1995-1999 by Axel Boldt and many others and are governed by the GNU
63 # General Public License.
65 Prompt for development and/or incomplete code/drivers
67 Some of the various things that Linux supports (such as network
68 drivers, filesystems, network protocols, etc.) can be in a state
69 of development where the functionality, stability, or the level of
70 testing is not yet high enough for general use. This is usually
71 known as the "alpha-test" phase amongst developers. If a feature is
72 currently in alpha-test, then the developers usually discourage
73 uninformed widespread use of this feature by the general public to
74 avoid "Why doesn't this work?" type mail messages. However, active
75 testing and use of these systems is welcomed. Just be aware that it
76 may not meet the normal level of reliability or it may fail to work
77 in some special cases. Detailed bug reports from people familiar
78 with the kernel internals are usually welcomed by the developers
79 (before submitting bug reports, please read the documents README,
80 MAINTAINERS, REPORTING_BUGS, Documentation/BUG-HUNTING, and
81 Documentation/oops-tracing.txt in the kernel source).
83 This option will also make obsoleted drivers available. These are
84 drivers that have been replaced by something else, and/or are
85 scheduled to be removed in a future kernel release.
87 Unless you intend to help test and develop a feature or driver that
88 falls into this category, or you have a situation that requires
89 using these features, you should probably say N here, which will
90 cause this configure script to present you with fewer choices. If
91 you say Y here, you will be offered the choice of using features or
92 drivers that are currently considered to be in the alpha-test phase.
94 Symmetric Multi Processing
96 This enables support for systems with more than one CPU. If you have
97 a system with only one CPU, like most personal computers, say N. If
98 you have a system with more than one CPU, say Y.
100 If you say N here, the kernel will run on single and multiprocessor
101 machines, but will use only one CPU of a multiprocessor machine. If
102 you say Y here, the kernel will run on many, but not all,
103 singleprocessor machines. On a singleprocessor machine, the kernel
104 will run faster if you say N here.
106 Note that if you say Y here and choose architecture "586" or
107 "Pentium" under "Processor family", the kernel will not work on 486
108 architectures. Similarly, multiprocessor kernels for the "PPro"
109 architecture may not work on all Pentium based boards.
111 People using multiprocessor machines who say Y here should also say
112 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
113 Management" code will be disabled if you say Y here.
115 See also: Documentation/SMP.txt, Documentation/smp.tex,
116 Documentation/smp.txt, and Documentation/IO-APIC.txt. Also see the
117 SMP-FAQ on the WWW at http://www.irisa.fr/prive/mentre/smp-faq/ .
119 If you don't know what to do here, say N.
121 Kernel math emulation
122 CONFIG_MATH_EMULATION
123 Linux can emulate a math coprocessor (used for floating point
124 operations) if you don't have one. 486DX and Pentium processors have
125 a math coprocessor built in, 486SX and 386 do not, unless you added
126 a 487DX or 387, respectively. (The messages during boot time can
127 give you some hints here ["man dmesg"].) Everyone needs either a
128 coprocessor or this emulation.
130 If you don't have a math coprocessor, you need to say Y here; if you
131 say Y here even though you have a coprocessor, the coprocessor will
132 be used nevertheless. (This behavior can be changed with the kernel
133 command line option "no387", which comes handy if your coprocessor
134 is broken. Try "man bootparam" or see the documentation of your boot
135 loader (lilo or loadlin) about how to pass options to the kernel at
136 boot time. The lilo procedure is also explained in the SCSI-HOWTO,
137 available from http://metalab.unc.edu/mdw/linux.html#howto .) This
138 means that it is a good idea to say Y here if you intend to use this
139 kernel on different machines.
141 More information about the internals of the Linux math coprocessor
142 emulation can be found in arch/i386/math-emu/README.
144 If you are not sure, say Y; apart from resulting in a 66 KB bigger
145 kernel, it won't hurt.
147 Timer and CPU usage LEDs
149 If you say Y here, the LEDs on your machine will be used
150 to provide useful information about your current system status.
152 If you are compiling a kernel for a NetWinder or EBSA-285, you will
153 be able to select which LEDs are active using the options below. If
154 you are compiling a kernel for the EBSA-110 however, the red LED
155 will simply flash regularly to indicate that the system is still
156 functional. It is safe to say Y here if you have a CATS system, but
157 the driver will do nothing.
161 If you say Y here, one of the system LEDs (the green one on the
162 NetWinder or the amber one on the EBSA285) will flash regularly to
163 indicate that the system is still operational. This is mainly
164 useful to kernel hackers who are debugging unstable kernels.
168 If you say Y here, the red LED will be used to give a good real
169 time indication of CPU usage, by lighting whenever the idle task
170 is not currently executing.
172 Kernel FP software completion (EXPERIMENTAL)
174 This option is required for IEEE compliant floating point arithmetic
175 on the Alpha. The only time you would ever not say Y is to say M in
176 order to debug the code. Say Y unless you know what you are doing.
180 If you are compiling a kernel which will never run on a machine
181 with more than 1 Gigabyte total physical RAM, answer "off"
182 here (default choice).
184 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
185 High memory is all the physical RAM that could not be directly
186 mapped by the kernel - ie. 3GB if there is 4GB RAM in the system,
187 7GB if there is 8GB RAM in the system.
189 If 4 Gigabytes physical RAM or less is used then answer "4GB" here.
191 If more than 4 Gigabytes is used then answer "64GB" here. This
192 selection turns Intel PAE (Physical Address Extension) mode on.
193 PAE implements 3-level paging on IA32 processors. PAE is fully
194 supported by Linux, PAE mode is implemented on all recent Intel
195 processors (PPro and better). NOTE: The "64GB" kernel will not
196 boot CPUs that not support PAE!
198 Normal PC floppy disk support
200 If you want to use the floppy disk drive(s) of your PC under Linux,
201 say Y. Information about this driver, especially important for IBM
202 Thinkpad users, is contained in drivers/block/README.fd. This file
203 also contains the location of the Floppy driver FAQ as well as
204 location of the fdutils package used to configure additional
205 parameters of the driver at run time.
207 This driver is also available as a module ( = code which can be
208 inserted in and removed from the running kernel whenever you want).
209 The module will be called floppy.o. If you want to compile it as a
210 module, say M here and read Documentation/modules.txt.
212 Support for PowerMac floppy
214 If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
215 floppy controller, say Y here. Most commonly found in PowerMacs.
219 Saying Y here will allow you to use a portion of your RAM memory as
220 a block device, so that you can make filesystems on it, read and
221 write to it and do all the other things that you can do with normal
222 block devices (such as hard drives). It is usually used to load and
223 store a copy of a minimal root file system off of a floppy into RAM
224 during the initial install of Linux.
226 Note that the kernel command line option "ramdisk=XX" is now
227 obsolete. For details, read Documentation/ramdisk.txt.
229 If you want to compile this as a module ( = code which can be
230 inserted in and removed from the running kernel whenever you want),
231 say M and read Documentation/modules.txt. The module will be called
234 Most normal users won't need the RAM disk functionality, and can
237 Initial RAM disk (initrd) support
238 CONFIG_BLK_DEV_INITRD
239 The initial RAM disk is a RAM disk that is loaded by the boot loader
240 (loadlin or lilo) and that is mounted as root before the normal boot
241 procedure. It is typically used to load modules needed to mount the
242 "real" root file system, etc. See Documentation/initrd.txt for
247 Saying Y here will allow you to use a regular file as a block
248 device; you can then create a file system on that block device and
249 mount it just as you would mount other block devices such as hard
250 drive partitions, CDROM drives or floppy drives.
252 This is useful if you want to check an ISO 9660 file system before
253 burning the CD, or if you want to use floppy images without first
254 writing them to floppy.
256 The loop device driver can also be used to "hide" a filesystem in a
257 disk partition, floppy, or regular file, either using encryption
258 (scrambling the data) or steganography (hiding the data in the low
259 bits of, say, a sound file). This is also safe if the file resides
260 on a remote file server. If you want to do this, you will first have
261 to acquire and install a kernel patch from
262 ftp://ftp.replay.com/pub/crypto/linux/all or
263 ftp://verden.pvv.org/pub/linux/kerneli/v2.1/ , and then you need to
264 say Y to this option.
266 Note that alternative ways to use encrypted filesystems are provided
267 by the cfs package, which can be gotten from
268 ftp://ftp.replay.com/pub/crypto/disk/ , and the newer tcfs package,
269 available at http://tcfs.dia.unisa.it/ . You do not need to say Y
270 here if you want to use one of these. However, using cfs requires
271 saying Y to "NFS filesystem support" below while using tcfs requires
272 applying a kernel patch.
274 To use the loop device, you need the losetup utility and a recent
275 version of the mount program, both contained in the util-linux
276 package. The location and current version number of util-linux is
277 contained in the file Documentation/Changes.
279 Note that this loop device has nothing to do with the loopback
280 device used for network connections from the machine to itself.
282 If you want to compile this driver as a module ( = code which can be
283 inserted in and removed from the running kernel whenever you want),
284 say M here and read Documentation/modules.txt. The module will be
287 Most users will answer N here.
289 Network Block Device support
291 Saying Y here will allow your computer to be a client for network
292 block devices, i.e. it will be able to use block devices exported by
293 servers (mount filesystems on them etc.). Communication between
294 client and server works over TCP/IP networking, but to the client
295 program this is hidden: it looks like a regular local file access to
296 a block device special file such as /dev/nd0.
298 Network block devices also allows you to run a block-device in
299 userland (making server and client physically the same computer,
300 communicating using the loopback network device).
302 Read Documentation/nbd.txt for more information, especially about
303 where to find the server code, which runs in user space and does not
304 need special kernel support.
306 Note that this has nothing to do with the network file systems NFS
307 or Coda; you can say N here even if you intend to use NFS or Coda.
309 If you want to compile this driver as a module ( = code which can be
310 inserted in and removed from the running kernel whenever you want),
311 say M here and read Documentation/modules.txt. The module will be
316 Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
318 If you say Y here, you will use the full-featured IDE driver to
319 control up to eight IDE interfaces, each being able to serve a
320 "master" and a "slave" device, for a total of up to sixteen IDE
321 disk/cdrom/tape/floppy drives. People with SCSI-only systems
324 Useful information about large (>540 MB) IDE disks, multiple
325 interfaces, what to do if IDE devices are not automatically
326 detected, sound card IDE ports, module support, and other topics, is
327 contained in Documentation/ide.txt. For detailed information about
328 hard drives, consult the Disk-HOWTO and the Multi-Disk-HOWTO,
329 available from http://metalab.unc.edu/mdw/linux.html#howto .
331 To fine-tune IDE drive/interface parameters for improved
332 performance, look for the hdparm package at
333 ftp://metalab.unc.edu/pub/Linux/kernel/patches/diskdrives/ .
335 If you want to compile this driver as a module ( = code which can be
336 inserted in and removed from the running kernel whenever you want),
337 say M here and read Documentation/modules.txt and
338 Documentation/ide.txt. The module will be called ide.o. Do not
339 compile this driver as a module if your root filesystem (the one
340 containing the directory /) is located on an IDE device.
342 If you have one or more IDE drives, say Y or M here. If your system
343 has no IDE drives, or if memory requirements are really tight, you
344 could say N here, and select the "Old hard disk driver" below
345 instead to save about 13 KB of memory in the kernel.
347 Old hard disk (MFM/RLL/IDE) driver
348 CONFIG_BLK_DEV_HD_ONLY
349 There are two drivers for MFM/RLL/IDE hard disks. Most people use
350 the newer enhanced driver, but this old one is still around for two
351 reasons. Some older systems have strange timing problems and seem to
352 work only with the old driver (which itself does not work with some
353 newer systems). The other reason is that the old driver is smaller,
354 since it lacks the enhanced functionality of the new one. This makes
355 it a good choice for systems with very tight memory restrictions, or
356 for systems with only older MFM/RLL/ESDI drives. Choosing the old
357 driver can save 13 KB or so of kernel memory.
359 If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
360 instead of this one. For more detailed information, read the
361 Disk-HOWTO, available from
362 http://metalab.unc.edu/mdw/linux.html#howto .
364 People with SCSI-only systems can say N here.
366 Use old disk-only driver on primary interface
367 CONFIG_BLK_DEV_HD_IDE
368 There are two drivers for MFM/RLL/IDE disks. Most people use just
369 the new enhanced driver by itself. This option however installs the
370 old hard disk driver to control the primary IDE/disk interface in
371 the system, leaving the new enhanced IDE driver to take care of only
372 the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from
373 having an IDE/ATAPI CDROM or tape drive connected to the primary IDE
374 interface. Choosing this option may be useful for older systems
375 which have MFM/RLL/ESDI controller+drives at the primary port
376 address (0x1f0), along with IDE drives at the secondary/3rd/4th port
379 Normally, just say N here; you will then use the new driver for all
382 People with SCSI-only systems don't need this and can say N here as
385 Include IDE/ATA-2 DISK support
386 CONFIG_BLK_DEV_IDEDISK
387 This will include enhanced support for MFM/RLL/IDE hard disks. If
388 you have a MFM/RLL/IDE disk, and there is no special reason to use
389 the old hard disk driver instead, say Y. If you have an SCSI-only
390 system, you can say N here.
392 If you want to compile this driver as a module ( = code which can be
393 inserted in and removed from the running kernel whenever you want),
394 say M here and read Documentation/modules.txt. The module will be
395 called ide-disk.o. Do not compile this driver as a module if your
396 root filesystem (the one containing the directory /) is located on
397 the IDE disk. If unsure, say Y.
399 Use multi-mode by default
400 CONFIG_IDEDISK_MULTI_MODE
401 If you get this error, try to say Y here:
403 hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
404 hda: set_multmode: error=0x04 { DriveStatusError }
408 Include IDE/ATAPI CDROM support
410 If you have a CDROM drive using the ATAPI protocol, say Y. ATAPI is
411 a newer protocol used by IDE CDROM and TAPE drives, similar to the
412 SCSI protocol. Most new CDROM drives use ATAPI, including the
413 NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
414 double(2X) or better speed drives.
416 If you say Y here, the CDROM drive will be identified at boot time
417 along with other IDE devices, as "hdb" or "hdc", or something
418 similar (check the boot messages with dmesg). If this is your only
419 CDROM drive, you can say N to all other CDROM options, but be sure
420 to say Y or M to "ISO 9660 CDROM filesystem support".
422 Read the CDROM-HOWTO, available from
423 http://metalab.unc.edu/mdw/linux.html#howto and the file
424 Documentation/cdrom/ide-cd. Note that older versions of lilo (the
425 Linux boot loader) cannot properly deal with IDE/ATAPI CDROMs, so
426 install lilo-16 or higher, available from
427 ftp://metalab.unc.edu/pub/Linux/system/boot/lilo .
429 If you want to compile the driver as a module ( = code which can be
430 inserted in and removed from the running kernel whenever you want),
431 say M here and read Documentation/modules.txt. The module will be
434 Include CD-Changer Reporting
436 If you have an IDE/ATAPI multi-slot cd-changer and you want
437 to report which slots have a disk present, say Y. If you say Y
438 and there is no multi-slot cdrom present, this code is skipped.
440 This code could be the basis of multi-disk access based on
441 multi-mounts, but this is still pie-in-the-sky.
445 Include IDE/ATAPI TAPE support
446 CONFIG_BLK_DEV_IDETAPE
447 If you have an IDE tape drive using the ATAPI protocol, say Y.
448 ATAPI is a newer protocol used by IDE tape and CDROM drives, similar
449 to the SCSI protocol. If you have an SCSI tape drive however, you
452 If you say Y here, the tape drive will be identified at boot time
453 along with other IDE devices, as "hdb" or "hdc", or something
454 similar, and will be mapped to a character device such as "ht0"
455 (check the boot messages with dmesg). Be sure to consult the
456 drivers/block/ide-tape.c and Documentation/ide.txt files for usage
459 If you want to compile the driver as a module ( = code which can be
460 inserted in and removed from the running kernel whenever you want),
461 say M here and read Documentation/modules.txt. The module will be
464 Include IDE/ATAPI FLOPPY support
465 CONFIG_BLK_DEV_IDEFLOPPY
466 If you have an IDE floppy drive which uses the ATAPI protocol,
467 answer Y. ATAPI is a newer protocol used by IDE CDROM/tape/floppy
468 drives, similar to the SCSI protocol.
470 The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by
471 this driver. (ATAPI PD-CD/CDR drives are not supported by this
472 driver; support for PD-CD/CDR drives is available if you answer Y to
473 "SCSI emulation support", below).
475 If you say Y here, the FLOPPY drive will be identified along with
476 other IDE devices, as "hdb" or "hdc", or something similar (check
477 the boot messages with dmesg).
479 If you want to compile the driver as a module ( = code which can be
480 inserted in and removed from the running kernel whenever you want),
481 say M here and read Documentation/modules.txt. The module will be
484 SCSI emulation support
485 CONFIG_BLK_DEV_IDESCSI
486 This will provide SCSI host adapter emulation for IDE ATAPI devices,
487 and will allow you to use a SCSI device driver instead of a native
490 This is useful if you have an ATAPI device for which no native
491 driver has been written (for example, an ATAPI PD-CD or CDR drive);
492 you can then use this emulation together with an appropriate SCSI
493 device driver. In order to do this, say Y here and to "SCSI support"
494 and "SCSI generic support", below.
496 Note that this option does NOT allow you to attach SCSI devices to a
497 box that doesn't have a SCSI host adapter installed.
499 If both this SCSI emulation and native ATAPI support are compiled
500 into the kernel, the native support will be used.
502 People with SCSI-only systems can say N here. If unsure, say N.
504 CMD640 chipset bugfix/support
505 CONFIG_BLK_DEV_CMD640
506 The CMD-Technologies CMD640 IDE chip is used on many common 486 and
507 Pentium motherboards, usually in combination with a "Neptune" or
508 "SiS" chipset. Unfortunately, it has a number of rather nasty
509 design flaws that can cause severe data corruption under many common
510 conditions. Say Y here to include code which tries to automatically
511 detect and correct the problems under Linux. This option also
512 enables access to the secondary IDE ports in some CMD640 based
515 This driver will work automatically in PCI based systems (most new
516 systems have PCI slots). But if your system uses VESA local bus
517 (VLB) instead of PCI, you must also supply a kernel boot parameter
518 to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man
519 bootparam" or see the documentation of your boot loader about how to
520 pass options to the kernel. The lilo procedure is also explained in
521 the SCSI-HOWTO, available from
522 http://metalab.unc.edu/mdw/linux.html#howto .)
524 The CMD640 chip is also used on add-in cards by Acculogic, and on
525 the "CSA-6400E PCI to IDE controller" that some people have. For
526 details, read Documentation/ide.txt.
528 People with SCSI-only systems should say N here. If unsure, say Y.
530 CMD640 enhanced support
531 CONFIG_BLK_DEV_CMD640_ENHANCED
532 This option includes support for setting/autotuning PIO modes and
533 prefetch on CMD640 IDE interfaces. For details, read
534 Documentation/ide.txt. If you have a CMD640 IDE interface and your
535 BIOS does not already do this for you, then say Y here. Otherwise
538 RZ1000 chipset bugfix/support
539 CONFIG_BLK_DEV_RZ1000
540 The PC-Technologies RZ1000 IDE chip is used on many common 486 and
541 Pentium motherboards, usually along with the "Neptune" chipset.
542 Unfortunately, it has a rather nasty design flaw that can cause
543 severe data corruption under many conditions. Say Y here to include
544 code which automatically detects and corrects the problem under
545 Linux. This may slow disk throughput by a few percent, but at least
546 things will operate 100% reliably.
548 People with SCSI-only systems should say N here. If unsure, say Y.
550 Generic PCI IDE chipset support
551 CONFIG_BLK_DEV_IDEPCI
552 Say Y here for PCI systems which use IDE drive(s).
553 This option helps the IDE driver to automatically detect and
554 configure all PCI-based IDE interfaces in your system.
556 People with SCSI-only systems should say N here; if unsure say Y.
558 Generic PCI bus-master DMA support
559 CONFIG_BLK_DEV_IDEDMA_PCI
560 If your PCI system uses IDE drive(s) (as opposed to SCSI, say) and
561 is capable of bus-master DMA operation (most Pentium PCI systems),
562 you will want to say Y here to reduce CPU overhead. You can then use
563 the "hdparm" utility to enable DMA for drives for which it was not
564 enabled automatically. By default, DMA is not enabled automatically
565 for these drives, but you can change that by saying Y to the
566 following question "Use DMA by default when available". You can get
567 the latest version of the hdparm utility from
568 ftp://metalab.unc.edu/pub/Linux/system/hardware/ .
570 Read the comments at the beginning of drivers/block/idedma.c and the
571 file Documentation/ide.txt for more information.
573 It is safe to say Y to this question.
575 Good-Bad DMA Model-Firmware (EXPERIMENTAL)
576 IDEDMA_NEW_DRIVE_LISTINGS
577 If you say Y here, the model and firmware revision of your drive
578 will be compared against a blacklist of buggy drives that claim to
579 be (U)DMA capable but aren't. This is a blanket on/off test with no
582 Straight GNU GCC 2.7.3/2.8.X compilers are known to be safe;
583 whereas, many versions of EGCS have a problem and miscompile if you
588 Boot off-board chipsets first support
589 CONFIG_BLK_DEV_OFFBOARD
590 Normally, IDE controllers built into the motherboard (on-board
591 controllers) are assigned to ide0 and ide1 while those on add-in PCI
592 cards (off-board controllers) are relegated to ide2 and ide3.
593 Answering Y here will allow you to reverse the situation, with
594 off-board controllers on ide0/1 and on-board controllers on ide2/3.
595 This can improve the usability of some boot managers such as LILO
596 when booting from a drive on an off-board controller.
598 If you say Y here, and you actually want to reverse the device scan
599 order as explained above, you also need to issue the kernel command
600 line option "pci=reverse". (Try "man bootparam" or see the
601 documentation of your boot loader (lilo or loadlin) about how to
602 pass options to the kernel at boot time. The lilo procedure is also
603 explained in the SCSI-HOWTO, available from
604 http://metalab.unc.edu/mdw/linux.html#howto .)
606 Note that, if you do this, the order of the hd* devices will be
607 rearranged which may require modification of fstab and other files.
611 Use DMA by default when available
612 CONFIG_IDEDMA_PCI_AUTO
613 Prior to kernel version 2.1.112, Linux used to automatically use
614 DMA for IDE drives and chipsets which support it. Due to concerns
615 about a couple of cases where buggy hardware may have caused damage,
616 the default is now to NOT use DMA automatically. To revert to the
617 previous behaviour, say Y to this question.
619 If you suspect your hardware is at all flakey, say N here.
620 Do NOT email the IDE kernel people regarding this issue!
622 It is normally safe to answer Y to this question unless your
623 motherboard uses a VIA VP2 chipset, in which case you should say N.
625 AEC6210 chipset support
626 CONFIG_BLK_DEV_AEC6210
627 This driver adds up to 4 more EIDE devices sharing a single
628 interrupt. This add-on card is a bootable PCI UDMA controller. In
629 order to get this card to initialize correctly in some cases, you
630 should say Y here, and preferably also to "Use DMA by default when
633 Please read the comments at the top of drivers/block/aec6210.c
635 ALI M15x3 chipset support (EXPERIMENTAL)
636 CONFIG_BLK_DEV_ALI15X3
637 This driver ensures (U)DMA support for ALI 1543 and 1543C,
638 1535, 1535D onboard chipsets. It also tests for Simplex mode and
639 enables normal dual channel support.
641 If you say Y here, you also need to say Y to "Use DMA by default
642 when available", above.
644 Please read the comments at the top of drivers/block/alim15x3.c
648 CMD646 chipset support (EXPERIMENTAL)
649 CONFIG_BLK_DEV_CMD646
650 Say Y here if you have an IDE controller which uses this chipset.
652 CY82C693 chipset support (EXPERIMENTAL)
653 CONFIG_BLK_DEV_CY82C693
654 This driver adds detection and support for the CY82C693 chipset
655 used on Digital's PC-Alpha 164SX boards.
657 If you say Y here, you need to say Y to "Use DMA by default
658 when available" as well.
660 HPT34X chipset support
661 CONFIG_BLK_DEV_HPT34X
662 This driver adds up to 4 more EIDE devices sharing a single
663 interrupt. The HPT343 chipset in its current form is a non-bootable
664 controller; the HPT345/HPT363 chipset is a bootable (needs BIOS FIX)
665 PCI UDMA controllers. This driver requires dynamic tuning of the
666 chipset during the ide-probe at boot time. It is reported to support
667 DVD II drives, by the manufacturer.
669 HPT34X DMA support (EXPERIMENTAL)
670 CONFIG_BLK_DEV_HPT34X_DMA
671 you need to say Y to "Use DMA by default when available" if you say
674 Please read the comments at the top of drivers/block/hpt34x.c
676 HPT366 chipset support
677 CONFIG_BLK_DEV_HPT366
678 This is an Ultra DMA chipset for ATA-66.
680 This driver adds up to 4 more EIDE devices sharing a single
681 interrupt. The HPT366 chipset in its current form is a non-bootable.
682 This driver requires dynamic tuning of the chipset during the
683 ide-probe at boot. It is reported to support DVD II drives, by the
686 Please read the comments at the top of drivers/block/hpt366.c
688 HPT366 Fast Interrupt support (EXPERIMENTAL)
689 HPT366_FAST_IRQ_PREDICTION
693 NS87415 support (EXPERIMENTAL)
694 CONFIG_BLK_DEV_NS87415
695 This driver adds detection and support for the NS87415 chip
696 (used in SPARC64, among others).
698 Please read the comments at the top of drivers/block/ns87415.c.
700 OPTi 82C621 enhanced support (EXPERIMENTAL)
701 CONFIG_BLK_DEV_OPTI621
702 This is a driver for the OPTi 82C621 EIDE controller.
703 Please read the comments at the top of drivers/block/opti621.c.
705 Intel PIIXn chipsets support
707 This driver adds PIO mode setting and tuning for all PIIX IDE
708 controllers by Intel. Since the BIOS can sometimes improperly tune
709 PIO 0-4 mode settings, this allows dynamic tuning of the chipset
710 via the standard end-user tool 'hdparm'.
712 Please read the comments at the top of drivers/block/piix.c
717 CONFIG_BLK_DEV_PIIX_TUNING
718 This driver extension adds DMA mode setting and tuning for all PIIX
719 IDE controllers by Intel. Since the BIOS can sometimes improperly
720 set up the device/adapter combination and speed limits, it has
721 become a necessity to back/forward speed devices as needed.
723 Case 430HX/440FX PIIX3 need speed limits to reduce UDMA to DMA mode
724 2 if the BIOS can not perform this task at initialization.
728 PROMISE PDC20246/PDC20262 support
729 CONFIG_BLK_DEV_PDC202XX
730 Promise Ultra33 or PDC20246
732 This driver adds up to 4 more EIDE devices sharing a single
733 interrupt. This add-on card is a bootable PCI UDMA controller. Since
734 multiple cards can be installed and there are BIOS ROM problems that
735 happen if the BIOS revisions of all installed cards (three-max) do
736 not match, the driver attempts to do dynamic tuning of the chipset at
737 boot-time for max-speed. Ultra33 BIOS 1.25 or newer is required for
738 more than one card. This card may require that you say Y to "Special
739 UDMA Feature (EXPERIMENTAL)".
741 Promise Ultra66 or PDC20262
743 This driver adds up to 4 more EIDE devices sharing a single
744 interrupt. This add-on card is a bootable PCI UDMA ATA-66
745 controller. The driver attempts to dynamic tuning of the chipset at
746 boot-time for max-speed. Note tested limits are UDMA-2. Ultra66 BIOS
747 1.11 or newer required.
749 If you say Y here, you need to say Y to "Use DMA by default when
752 Please read the comments at the top of drivers/block/pdc202xx.c
757 PDC202XX_FORCE_BURST_BIT
758 For PDC20246 and PDC20262 Ultra DMA chipsets. Designed originally
759 for PDC20246/Ultra33 that has BIOS setup failures when using 3 or
762 Please read the comments at the top of drivers/block/pdc202xx.c
766 Special Mode Feature (EXPERIMENTAL)
767 PDC202XX_FORCE_MASTER_MODE
768 For PDC20246 and PDC20262 Ultra DMA chipsets. This is reserved for
769 possible Hardware RAID 0,1 for the FastTrak Series.
773 Winbond SL82c105 support
774 CONFIG_BLK_DEV_SL82C105
775 If you have a Winbond SL82c105 IDE controller, say Y here to enable
776 special configuration for this chip. This is common on various CHRP
777 motherboards, but could be used elsewhere. If in doubt, say Y.
779 Tekram TRM290 chipset support (EXPERIMENTAL)
780 CONFIG_BLK_DEV_TRM290
781 This driver adds support for bus master DMA transfers
782 using the Tekram TRM290 PCI IDE chip. Volunteers are
783 needed for further tweaking and development.
784 Please read the comments at the top of drivers/block/trm290.c.
786 VIA82CXXX chipset support (EXPERIMENTAL)
787 CONFIG_BLK_DEV_VIA82CXXX
788 This allows you to to configure your chipset for a better use while
789 running (U)DMA: it will allow you to enable efficiently the second
790 channel dma usage, as it is may not be set by BIOS. It allows you to
791 run a kernel command line at boot time in order to set fifo config.
792 If no command line is provided, it will try to set fifo configuration
793 at its best. It will allow you to get a proc/ide/via display
794 (while running a "cat") provided you enabled "proc" support.
795 Please read the comments at the top of drivers/block/via82cxxx.c
797 If you say Y here, you also need to say Y to "Use DMA by default
798 when available", above.
802 Other IDE chipset support
804 Say Y here if you want to include enhanced support for various IDE
805 interface chipsets used on motherboards and add-on cards. You can
806 then pick your particular IDE chip from among the following options.
807 This enhanced support may be necessary for Linux to be able to
808 access the 3rd/4th drives in some systems. It may also enable
809 setting of higher speed I/O rates to improve system performance with
810 these chipsets. Most of these also require special kernel boot
811 parameters to actually turn on the support at runtime; you can find
812 a list of these in the file Documentation/ide.txt.
814 People with SCSI-only systems can say N here.
816 Generic 4 drives/port support
817 CONFIG_BLK_DEV_4DRIVES
818 Certain older chipsets, including the Tekram 690CD, use a single set
819 of I/O ports at 0x1f0 to control up to four drives, instead of the
820 customary two drives per port. Support for this can be enabled at
821 runtime using the "ide0=four" kernel boot parameter if you say Y
825 CONFIG_BLK_DEV_ALI14XX
826 This driver is enabled at runtime using the "ide0=ali14xx" kernel
827 boot parameter. It enables support for the secondary IDE interface
828 of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
829 I/O speeds to be set as well. See the files Documentation/ide.txt
830 and drivers/block/ali14xx.c for more info.
833 CONFIG_BLK_DEV_DTC2278
834 This driver is enabled at runtime using the "ide0=dtc2278" kernel
835 boot parameter. It enables support for the secondary IDE interface
836 of the DTC-2278 card, and permits faster I/O speeds to be set as
837 well. See the Documentation/ide.txt and drivers/block/dtc2278.c
840 Holtek HT6560B support
841 CONFIG_BLK_DEV_HT6560B
842 This driver is enabled at runtime using the "ide0=ht6560b" kernel
843 boot parameter. It enables support for the secondary IDE interface
844 of the Holtek card, and permits faster I/O speeds to be set as well.
845 See the Documentation/ide.txt and drivers/block/ht6560b.c files for
848 PROMISE DC4030 support (EXPERIMENTAL)
849 CONFIG_BLK_DEV_PDC4030
850 This driver provides support for the secondary IDE interface and
851 cache of Promise IDE chipsets, e.g. DC4030 and DC5030. This driver
852 is known to incur timeouts/retries during heavy I/O to drives
853 attached to the secondary interface. CDROM and TAPE devices are not
854 supported yet. This driver is enabled at runtime using the
855 "ide0=dc4030" kernel boot parameter. See the Documentation/ide.txt
856 and drivers/block/pdc4030.c files for more info.
859 CONFIG_BLK_DEV_QD6580
860 This driver is enabled at runtime using the "ide0=qd6580" kernel
861 boot parameter. It permits faster I/O speeds to be set. See the
862 files Documentation/ide.txt and drivers/block/qd6580.c for more
866 CONFIG_BLK_DEV_UMC8672
867 This driver is enabled at runtime using the "ide0=umc8672" kernel
868 boot parameter. It enables support for the secondary IDE interface
869 of the UMC-8672, and permits faster I/O speeds to be set as well.
870 See the files Documentation/ide.txt and drivers/block/umc8672.c for
873 PS/2 ESDI hard disk support
875 Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
878 If you want to compile the driver as a module ( = code which can be
879 inserted in and removed from the running kernel whenever you want),
880 say M here and read Documentation/modules.txt. The module will be
883 Amiga builtin Gayle IDE interface support
885 This is the IDE driver for the builtin IDE interface on some Amiga
886 models. It supports both the `A1200 style' (used in A600 and A1200)
887 and `A4000 style' (used in A4000 and A4000T) of the Gayle IDE
888 interface. Say Y if you have such an Amiga model and want to use IDE
889 devices (hard disks, CD-ROM drives, etc.) that are connected to the
890 builtin IDE interface.
892 Falcon IDE interface support
893 CONFIG_BLK_DEV_FALCON_IDE
894 This is the IDE driver for the builtin IDE interface on the Atari
895 Falcon. Say Y if you have a Falcon and want to use IDE devices (hard
896 disks, CD-ROM drives, etc.) that are connected to the builtin IDE
899 Amiga Buddha/Catweasel IDE interface support (EXPERIMENTAL)
900 CONFIG_BLK_DEV_BUDDHA
901 This is the IDE driver for the IDE interfaces on the Buddha and
902 Catweasel expansion boards. It supports up to two interfaces on the
903 Buddha and three on the Catweasel.
905 Say Y if you have a Buddha or Catweasel expansion board and want to
906 use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
907 to one of its IDE interfaces.
909 Amiga IDE Doubler support (EXPERIMENTAL)
910 CONFIG_BLK_DEV_IDEDOUBLER
911 This driver provides support for the so called `IDE doublers' (made
912 by various manufacturers, e.g. Eyetech) that can be connected to the
913 builtin IDE interface of some Amiga models. Using such an IDE
914 doubler, you can connect up to four instead of two IDE devices on
915 the Amiga's builtin IDE interface.
917 Note that the normal Amiga Gayle IDE driver may not work correctly
918 if you have an IDE doubler and don't enable this driver!
920 Say Y if you have an IDE doubler. The driver is enabled at kernel
921 runtime using the "ide=doubler" kernel boot parameter.
923 Support for PowerMac IDE devices (must also enable IDE)
924 CONFIG_BLK_DEV_IDE_PMAC
925 No help for CONFIG_BLK_DEV_IDE_PMAC
927 PowerMac IDE DMA support
928 CONFIG_BLK_DEV_IDEDMA_PMAC
929 No help for CONFIG_BLK_DEV_IDEDMA_PMAC
932 CONFIG_IDEDMA_PMAC_AUTO
933 No help for CONFIG_IDEDMA_PMAC_AUTO
935 Macintosh Quadra/Powerbook IDE interface support
936 CONFIG_BLK_DEV_MAC_IDE
937 This is the IDE driver for the builtin IDE interface on some m68k
938 Macintosh models. It supports both the `Quadra style' (used in
939 Quadra/ Centris 630 and Performa 588 models) and `Powerbook style'
940 (used in the Powerbook 150 and 190 models) IDE interface.
942 Say Y if you have such an Macintosh model and want to use IDE
943 devices (hard disks, CD-ROM drives, etc.) that are connected to the
944 builtin IDE interface.
946 ICS IDE interface support
947 CONFIG_BLK_DEV_IDE_ICSIDE
948 No help for CONFIG_BLK_DEV_IDE_ICSIDE
951 CONFIG_BLK_DEV_IDEDMA_ICS
952 No help for CONFIG_BLK_DEV_IDEDMA_ICS
954 Use ICS DMA by default
955 CONFIG_IDEDMA_ICS_AUTO
956 No help for CONFIG_IDEDMA_ICS_AUTO
958 RapIDE interface support
959 CONFIG_BLK_DEV_IDE_RAPIDE
960 No help for CONFIG_BLK_DEV_IDE_RAPIDE
964 Very old 8 bit hard disk controllers used in the IBM XT computer
965 will be supported if you say Y here.
967 If you want to compile the driver as a module ( = code which can be
968 inserted in and removed from the running kernel whenever you want),
969 say M here and read Documentation/modules.txt. The module will be
972 It's pretty unlikely that you have one of these: say N.
974 Mylex DAC960/DAC1100 PCI RAID Controller support
975 CONFIG_BLK_DEV_DAC960
976 This driver adds support for the Mylex DAC960, AcceleRAID, and
977 eXtremeRAID PCI RAID controllers. See the file
978 Documentation/README.DAC960 for further information about this
981 If you want to compile the driver as a module ( = code which can be
982 inserted in and removed from the running kernel whenever you want),
983 say M here and read Documentation/modules.txt. The module will be
986 Parallel port IDE device support
988 There are many external CD-ROM and disk devices that connect through
989 your computer's parallel port. Most of them are actually IDE devices
990 using a parallel port IDE adapter. This option enables the PARIDE
991 subsystem which contains drivers for many of these external drives.
992 Read linux/Documentation/paride.txt for more information.
994 If you have said Y to the "Parallel-port support" configuration
995 option, you may share a single port between your printer and other
996 parallel port devices. Answer Y to build PARIDE support into your
997 kernel, or M if you would like to build it as a loadable module. If
998 your parallel port support is in a loadable module, you must build
999 PARIDE as a module. If you built PARIDE support into your kernel,
1000 you may still build the individual protocol modules and high-level
1001 drivers as loadable modules. If you build this support as a module,
1002 it will be called paride.o.
1004 To use the PARIDE support, you must say Y or M here and also to at
1005 least one high-level driver (e.g. "Parallel port IDE disks",
1006 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
1007 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
1008 "MicroSolutions backpack protocol", "DataStor Commuter protocol"
1011 Parallel port IDE disks
1013 This option enables the high-level driver for IDE-type disk devices
1014 connected through a parallel port. If you chose to build PARIDE
1015 support into your kernel, you may answer Y here to build in the
1016 parallel port IDE driver, otherwise you should answer M to build
1017 it as a loadable module. The module will be called pd.o. You
1018 must also have at least one parallel port protocol driver in your
1019 system. Among the devices supported by this driver are the SyQuest
1020 EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack
1021 hard drives from MicroSolutions.
1023 Parallel port ATAPI CD-ROMs
1025 This option enables the high-level driver for ATAPI CD-ROM devices
1026 connected through a parallel port. If you chose to build PARIDE
1027 support into your kernel, you may answer Y here to build in the
1028 parallel port ATAPI CD-ROM driver, otherwise you should answer M to
1029 build it as a loadable module. The module will be called pcd.o. You
1030 must also have at least one parallel port protocol driver in your
1031 system. Among the devices supported by this driver are the
1032 MicroSolutions backpack CD-ROM drives and the Freecom Power CD. If
1033 you have such a CD-ROM drive, you should also say Y or M to "ISO
1034 9660 CDROM filesystem support" below, because that's the filesystem
1037 Parallel port ATAPI disks
1039 This option enables the high-level driver for ATAPI disk devices
1040 connected through a parallel port. If you chose to build PARIDE
1041 support into your kernel, you may answer Y here to build in the
1042 parallel port ATAPI disk driver, otherwise you should answer M
1043 to build it as a loadable module. The module will be called pf.o.
1044 You must also have at least one parallel port protocol driver in
1045 your system. Among the devices supported by this driver are the
1046 MicroSolutions backpack PD/CD drive and the Imation Superdisk
1049 Parallel port ATAPI tapes
1051 This option enables the high-level driver for ATAPI tape devices
1052 connected through a parallel port. If you chose to build PARIDE
1053 support into your kernel, you may answer Y here to build in the
1054 parallel port ATAPI disk driver, otherwise you should answer M
1055 to build it as a loadable module. The module will be called pt.o.
1056 You must also have at least one parallel port protocol driver in
1057 your system. Among the devices supported by this driver is the
1058 parallel port version of the HP 5GB drive.
1060 Parallel port generic ATAPI devices
1062 This option enables a special high-level driver for generic ATAPI
1063 devices connected through a parallel port. The driver allows user
1064 programs, such as cdrecord, to send ATAPI commands directly to a
1067 If you chose to build PARIDE support into your kernel, you may
1068 answer Y here to build in the parallel port generic ATAPI driver,
1069 otherwise you should answer M to build it as a loadable module. The
1070 module will be called pg.o.
1072 You must also have at least one parallel port protocol driver in
1075 This driver implements an API loosely related to the generic SCSI
1076 driver. See /usr/include/linux/pg.h for details.
1078 You can obtain the most recent version of cdrecord from
1079 ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/ . Versions 1.6.1a3 and
1080 later fully support this driver.
1082 ATEN EH-100 protocol
1084 This option enables support for the ATEN EH-100 parallel port IDE
1085 protocol. This protocol is used in some inexpensive low performance
1086 parallel port kits made in Hong Kong. If you chose to build PARIDE
1087 support into your kernel, you may answer Y here to build in the
1088 protocol driver, otherwise you should answer M to build it as a
1089 loadable module. The module will be called aten.o. You must also
1090 have a high-level driver for the type of device that you want to
1093 MicroSolutions backpack protocol
1095 This option enables support for the MicroSolutions backpack parallel
1096 port IDE protocol. If you chose to build PARIDE support into your
1097 kernel, you may answer Y here to build in the protocol driver,
1098 otherwise you should answer M to build it as a loadable module. The
1099 module will be called bpck.o. You must also have a high-level driver
1100 for the type of device that you want to support.
1102 DataStor Commuter protocol
1104 This option enables support for the Commuter parallel port IDE
1105 protocol from DataStor. If you chose to build PARIDE support
1106 into your kernel, you may answer Y here to build in the protocol
1107 driver, otherwise you should answer M to build it as a loadable
1108 module. The module will be called comm.o. You must also have
1109 a high-level driver for the type of device that you want to support.
1111 DataStor EP-2000 protocol
1113 This option enables support for the EP-2000 parallel port IDE
1114 protocol from DataStor. If you chose to build PARIDE support
1115 into your kernel, you may answer Y here to build in the protocol
1116 driver, otherwise you should answer M to build it as a loadable
1117 module. The module will be called dstr.o. You must also have
1118 a high-level driver for the type of device that you want to support.
1120 Shuttle EPAT/EPEZ protocol
1122 This option enables support for the EPAT parallel port IDE protocol.
1123 EPAT is a parallel port IDE adapter manufactured by Shuttle
1124 Technology and widely used in devices from major vendors such as
1125 Hewlett-Packard, SyQuest, Imation and Avatar. If you chose to build
1126 PARIDE support into your kernel, you may answer Y here to build in
1127 the protocol driver, otherwise you should answer M to build it as a
1128 loadable module. The module will be called epat.o. You must also
1129 have a high-level driver for the type of device that you want to
1132 Shuttle EPIA protocol
1134 This option enables support for the (obsolete) EPIA parallel port
1135 IDE protocol from Shuttle Technology. This adapter can still be
1136 found in some no-name kits. If you chose to build PARIDE support
1137 into your kernel, you may answer Y here to build in the protocol
1138 driver, otherwise you should answer M to build it as a loadable
1139 module. The module will be called epia.o. You must also have a
1140 high-level driver for the type of device that you want to support.
1142 FIT TD-2000 protocol
1144 This option enables support for the TD-2000 parallel port IDE
1145 protocol from Fidelity International Technology. This is a simple
1146 (low speed) adapter that is used in some portable hard drives. If
1147 you chose to build PARIDE support into your kernel, you may answer Y
1148 here to build in the protocol driver, otherwise you should answer M
1149 to build it as a loadable module. The module will be called ktti.o.
1150 You must also have a high-level driver for the type of device that
1151 you want to support.
1153 FIT TD-3000 protocol
1155 This option enables support for the TD-3000 parallel port IDE
1156 protocol from Fidelity International Technology. This protocol is
1157 used in newer models of their portable disk, CD-ROM and PD/CD
1158 devices. If you chose to build PARIDE support into your kernel, you
1159 may answer Y here to build in the protocol driver, otherwise you
1160 should answer M to build it as a loadable module. The module will be
1161 called fit3.o. You must also have a high-level driver for the type
1162 of device that you want to support.
1164 Freecom IQ ASIC-2 protocol
1166 This option enables support for version 2 of the Freecom IQ parallel
1167 port IDE adapter. This adapter is used by the Maxell Superdisk
1168 drive. If you chose to build PARIDE support into your kernel, you
1169 may answer Y here to build in the protocol driver, otherwise you
1170 should answer M to build it as a loadable module. The module will be
1171 called friq.o. You must also have a high-level driver for the type
1172 of device that you want to support.
1174 FreeCom power protocol
1176 This option enables support for the Freecom power parallel port IDE
1177 protocol. If you chose to build PARIDE support into your kernel, you
1178 may answer Y here to build in the protocol driver, otherwise you
1179 should answer M to build it as a loadable module. The module will be
1180 called frpw.o. You must also have a high-level driver for the type
1181 of device that you want to support.
1183 KingByte KBIC-951A/971A protocols
1185 This option enables support for the KBIC-951A and KBIC-971A parallel
1186 port IDE protocols from KingByte Information Corp. KingByte's
1187 adapters appear in many no-name portable disk and CD-ROM products,
1188 especially in Europe. If you chose to build PARIDE support into your
1189 kernel, you may answer Y here to build in the protocol driver,
1190 otherwise you should answer M to build it as a loadable module. The
1191 module will be called kbic.o. You must also have a high-level driver
1192 for the type of device that you want to support.
1196 This option enables support for the "PHd" parallel port IDE protocol
1197 from KT Technology. This is a simple (low speed) adapter that is
1198 used in some 2.5" portable hard drives. If you chose to build PARIDE
1199 support into your kernel, you may answer Y here to build in the
1200 protocol driver, otherwise you should answer M to build it as a
1201 loadable module. The module will be called ktti.o. You must also
1202 have a high-level driver for the type of device that you want to
1205 OnSpec 90c20 protocol
1207 This option enables support for the (obsolete) 90c20 parallel port
1208 IDE protocol from OnSpec (often marketed under the ValuStore brand
1209 name). If you chose to build PARIDE support into your kernel, you
1210 may answer Y here to build in the protocol driver, otherwise you
1211 should answer M to build it as a loadable module. The module will
1212 be called on20.o. You must also have a high-level driver for the
1213 type of device that you want to support.
1215 OnSpec 90c26 protocol
1217 This option enables support for the 90c26 parallel port IDE protocol
1218 from OnSpec Electronics (often marketed under the ValuStore brand
1219 name). If you chose to build PARIDE support into your kernel, you
1220 may answer Y here to build in the protocol driver, otherwise you
1221 should answer M to build it as a loadable module. The module will be
1222 called on26.o. You must also have a high-level driver for the type
1223 of device that you want to support.
1225 Multiple devices driver support
1227 This driver lets you combine several hard disk partitions into one
1228 logical block device. This can be used to simply append one
1229 partition to another one or to combine several redundant
1230 hard disks to a RAID1/4/5 device so as to provide protection against
1231 hard disk failures. This is called "Software RAID" since the
1232 combining of the partitions is done by the kernel. "Hardware RAID"
1233 means that the combining is done by a dedicated controller; if you
1234 have such a controller, you do not need to say Y here.
1236 More information about Software RAID on Linux is contained in the
1237 Software-RAID mini-HOWTO, available from
1238 http://metalab.unc.edu/mdw/linux.html#howto . There you will also
1239 learn where to get the supporting user space utilities raidtools.
1243 Linear (append) mode
1245 If you say Y here, then your multiple devices driver will be able to
1246 use the so-called linear mode, i.e. it will combine the hard disk
1247 partitions by simply appending one to the other.
1249 If you want to compile this as a module ( = code which can be
1250 inserted in and removed from the running kernel whenever you want),
1251 say M here and read Documentation/modules.txt. The module will be
1256 RAID-0 (striping) mode
1258 If you say Y here, then your multiple devices driver will be able to
1259 use the so-called raid0 mode, i.e. it will combine the hard disk
1260 partitions into one logical device in such a fashion as to fill them
1261 up evenly, one chunk here and one chunk there. This will increase
1262 the throughput rate if the partitions reside on distinct disks.
1264 Information about Software RAID on Linux is contained in the
1265 Software-RAID mini-HOWTO, available from
1266 http://metalab.unc.edu/mdw/linux.html#howto . There you will also
1267 learn where to get the supporting user space utilities raidtools.
1269 If you want to compile this as a module ( = code which can be
1270 inserted in and removed from the running kernel whenever you want),
1271 say M here and read Documentation/modules.txt. The module will be
1276 RAID-1 (mirroring) mode
1278 A RAID-1 set consists of several disk drives which are exact copies
1279 of each other. In the event of a mirror failure, the RAID driver
1280 will continue to use the operational mirrors in the set, providing
1281 an error free MD (multiple device) to the higher levels of the
1282 kernel. In a set with N drives, the available space is the capacity
1283 of a single drive, and the set protects against a failure of (N - 1)
1286 Information about Software RAID on Linux is contained in the
1287 Software-RAID mini-HOWTO, available from
1288 http://metalab.unc.edu/mdw/linux.html#howto . There you will also
1289 learn where to get the supporting user space utilities raidtools.
1291 If you want to use such a RAID-1 set, say Y. This code is also
1292 available as a module called raid1.o ( = code which can be inserted
1293 in and removed from the running kernel whenever you want). If you
1294 want to compile it as a module, say M here and read
1295 Documentation/modules.txt.
1301 A RAID-5 set of N drives with a capacity of C MB per drive provides
1302 the capacity of C * (N - 1) drives, and protects against a failure
1303 of a single drive. For a given sector (row) number, (N - 1) drives
1304 contain data sectors, and one drive contains the parity protection.
1305 For a RAID-4 set, the parity blocks are present on a single drive,
1306 while a RAID-5 set distributes the parity across the drives in one
1307 of the available parity distribution methods.
1309 Information about Software RAID on Linux is contained in the
1310 Software-RAID mini-HOWTO, available from
1311 http://metalab.unc.edu/mdw/linux.html#howto . There you will also
1312 learn where to get the supporting user space utilities raidtools.
1314 If you want to use such a RAID-4/RAID-5 set, say Y. This code is
1315 also available as a module called raid5.o ( = code which can be
1316 inserted in and removed from the running kernel whenever you want).
1317 If you want to compile it as a module, say M here and read
1318 Documentation/modules.txt.
1322 Boot support (linear, striped)
1324 To boot with an initial linear or striped md device you have to
1325 answer Y here. For lilo and loadlin options see the file
1326 Documentation/md.txt.
1328 Support for Deskstation RPC44
1329 CONFIG_DESKSTATION_RPC44
1330 This is a machine with a R4400 100 MHz CPU. To compile a Linux
1331 kernel that runs on these, say Y here. For details about Linux
1332 on the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1333 http://lena.fnet.fr/ .
1335 Support for Acer PICA 1 chipset
1337 This is a machine with a R4400 133/150 MHz CPU. To compile a Linux
1338 kernel that runs on these, say Y here. For details about Linux on
1339 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1340 http://lena.fnet.fr/ .
1342 Support for Algorithmics P4032 (EXPERIMENTAL)
1344 This is an evaluation board of the British company Algorithmics. The
1345 board uses the R4300 and a R5230 CPUs. For more information about
1346 this board see http://www.algor.co.uk .
1349 CONFIG_BLK_DEV_IDE_CARDS
1350 On Acorn systems, say Y here if you wish to use an IDE interface
1351 expansion card. If you do not or are unsure, say N to this.
1354 CONFIG_BLK_DEV_IDE_ICS
1355 On Acorn systems, say Y here if you wish to use the ICS IDE
1356 interface card. This is not required for ICS partition support.
1357 If you are unsure, say N to this.
1359 ADFS partition support
1361 This allows Linux on Acorn systems to determine its partitions in
1362 the 'non-ADFS' partition area of the hard disk - usually located
1363 after the ADFS partition. You are probably using this system, so
1364 you should say Y here.
1366 Support for Mips Magnum 4000
1367 CONFIG_MIPS_MAGNUM_4000
1368 This is a machine with a R4000 100 MHz CPU. To compile a Linux
1369 kernel that runs on these, say Y here. For details about Linux on
1370 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1371 http://lena.fnet.fr/ .
1373 Support for Olivetti M700
1374 CONFIG_OLIVETTI_M700
1375 This is a machine with a R4000 100 MHz CPU. To compile a Linux
1376 kernel that runs on these, say Y here. For details about Linux on
1377 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1378 http://lena.fnet.fr/ .
1382 Give the type of your machine's MIPS CPU. For this question, it
1383 suffices to give a unique prefix of the option you want to choose.
1384 In case of doubt select the R3000 CPU. The kernel will then run on
1385 other MIPS machines but with slightly reduced performance.
1387 Compile the kernel into the ECOFF object format
1389 Some machines require a kernel in the ECOFF format. You will have to
1390 say Y here for example if you want to use a Mips Magnum 3000 or a
1393 Generate little endian code
1394 CONFIG_CPU_LITTLE_ENDIAN
1395 Some MIPS machines can be configured for either little or big endian
1396 byte order. These modes require different kernels. Say Y if your
1397 machine is little endian, N if it's a big endian machine.
1399 Kernel support for IRIX binaries
1401 If you say Y here, the kernel will support running of IRIX binaries.
1402 You will need IRIX libraries for this to work.
1406 Unless you really know what you are doing, you should say Y here.
1407 The reason is that some programs need kernel networking support even
1408 when running on a stand-alone machine that isn't connected to any
1409 other computer. If you are upgrading from an older kernel, you
1410 should consider updating your networking tools too because changes
1411 in the kernel and the tools often go hand in hand. The tools are
1412 contained in the package net-tools, the location and version number
1413 of which are given in Documentation/Changes.
1415 For a general introduction to Linux networking, it is highly
1416 recommended to read the NET-3-HOWTO, available from
1417 http://metalab.unc.edu/mdw/linux.html#howto .
1421 The Linux Socket Filter is derived from the Berkeley Packet Filter.
1422 If you say Y here, user-space programs can attach a filter to any
1423 socket and thereby tell the kernel that it should allow or disallow
1424 certain types of data to get through the socket. Linux Socket
1425 Filtering works on all socket types except TCP for now. See the text
1426 file linux/Documentation/networking/filter.txt for more information.
1429 Network packet filtering
1431 Netfilter is a framework for filtering and mangling network packets
1432 that pass through your Linux box.
1434 The most common use of packet filtering is to run your Linux box as
1435 a firewall protecting a local network from the Internet. The type of
1436 firewall provided by this kernel support is called a "packet
1437 filter", which means that it can reject individual network packets
1438 based on type, source, destination etc. The other kind of firewall,
1439 a "proxy-based" one, is more secure but more intrusive and more
1440 bothersome to set up; it inspects the network traffic much more
1441 closely, modifies it and has knowledge about the higher level
1442 protocols, which a packet filter lacks. Moreover, proxy-based
1443 firewalls often require changes to the programs running on the local
1444 clients. Proxy-based firewalls don't need support by the kernel, but
1445 they are often combined with a packet filter, which only works if
1448 You should also say Y here if you intend to use your Linux box as
1449 the gateway to the Internet for a local network of machines without
1450 globally valid IP addresses. This is called "masquerading": if one
1451 of the computers on your local network wants to send something to
1452 the outside, your box can "masquerade" as that computer, i.e. it
1453 forwards the traffic to the intended outside destination, but
1454 modifies the packets to make it look like they came from the
1455 firewall box itself. It works both ways: if the outside host
1456 replies, the Linux box will silently forward the traffic to the
1457 correct local computer. This way, the computers on your local net
1458 are completely invisible to the outside world, even though they can
1459 reach the outside and can receive replies. It is even possible to
1460 run globally visible servers from within a masqueraded local network
1461 using a mechanism called portforwarding. Masquerading is also often
1462 called NAT (Network Address Translation).
1464 Another use of Netfilter is in transparent proxying: if a machine on
1465 the local network tries to connect to an outside host, your Linux
1466 box can transparently forward the traffic to a local server,
1467 typically a caching proxy server.
1469 Various modules exist for netfilter which replace the previous
1470 masquerading (ipmasqadm), packet filtering (ipchains), transparent
1471 proxying, and portforwarding mechanisms. More information is
1472 available from http://netfilter.kernelnotes.org .
1474 Make sure to say N to "Fast switching" below if you intend to say Y
1475 here, as Fast switching currently bypasses netfilter.
1477 Chances are that you should say Y here if you compile a kernel which
1478 will run as a router and N for regular hosts. If unsure, say N.
1480 Network packet filtering debugging
1481 CONFIG_NETFILTER_DEBUG
1482 Say Y to make sure packets aren't leaking.
1484 SYN flood protection
1486 Normal TCP/IP networking is open to an attack known as "SYN
1487 flooding". This denial-of-service attack prevents legitimate remote
1488 users from being able to connect to your computer during an ongoing
1489 attack and requires very little work from the attacker, who can
1490 operate from anywhere on the Internet.
1492 SYN cookies provide protection against this type of attack. If you
1493 say Y here, the TCP/IP stack will use a cryptographic challenge
1494 protocol known as "SYN cookies" to enable legitimate users to
1495 continue to connect, even when your machine is under attack. There
1496 is no need for the legitimate users to change their TCP/IP software;
1497 SYN cookies work transparently to them. For technical information
1498 about SYN cookies, check out
1499 ftp://koobera.math.uic.edu/pub/docs/syncookies-archive .
1501 If you are SYN flooded, the source address reported by the kernel is
1502 likely to have been forged by the attacker; it is only reported as
1503 an aid in tracing the packets to their actual source and should not
1504 be taken as absolute truth.
1506 SYN cookies may prevent correct error reporting on clients when the
1507 server is really overloaded. If this happens frequently better turn
1510 If you say Y here, note that SYN cookies aren't enabled by default;
1511 you can enable them by saying Y to "/proc filesystem support" and
1512 "Sysctl support" below and executing the command
1514 echo 1 >/proc/sys/net/ipv4/tcp_syncookies
1516 at boot time after the proc filesystem has been mounted.
1520 Sun floppy controller support
1521 CONFIG_BLK_DEV_SUNFD
1522 This is support for floppy drives on Sun SPARC workstations. Say Y
1523 if you have a floppy drive, otherwise N. Easy.
1526 CONFIG_ALPHA_GENERIC
1527 This is the system type of your hardware. A "generic" kernel will
1528 run on any supported Alpha system. However, if you configure a
1529 kernel for your specific system, it will be faster and smaller.
1531 To find out what type of Alpha system you have, you may want to
1532 check out the Linux/Alpha FAQ, accessible on the WWW from
1533 http://www.alphalinux.org . In summary:
1535 Alcor/Alpha-XLT AS 600
1536 Alpha-XL XL-233, XL-266
1537 AlphaBook1 Alpha laptop
1538 Avanti AS 200, AS 205, AS 250, AS 255, AS 300, AS 400
1539 Cabriolet AlphaPC64, AlphaPCI64
1541 EB164 EB164 21164 evaluation board
1542 EB64+ EB64+ 21064 evaluation board
1543 EB66 EB66 21066 evaluation board
1544 EB66+ EB66+ 21066 evaluation board
1545 Jensen DECpc 150, DEC 2000 model 300,
1548 Miata Personal Workstation 433a, 433au, 500a,
1549 500au, 600a, or 600au
1551 Noname AXPpci33, UDB (Multia)
1552 Noritake AS 1000A, AS 600A, AS 800
1554 Rawhide AS 1200, AS 4000, AS 4100
1555 Ruffian RPX164-2, AlphaPC164-UX, AlphaPC164-BX
1557 Sable AS 2000, AS 2100
1560 If you don't know what to do, choose "generic".
1562 EV5 CPU daughtercard
1564 Say Y if you have an AS 1000 5/xxx or an AS 1000A 5/xxx.
1568 Say Y if you have an AS 2000 5/xxx or an AS 2100 5/xxx.
1570 Using SRM as bootloader
1572 There are two different types of booting firmware on Alphas: SRM,
1573 which is command line driven, and ARC, which uses menus and arrow
1574 keys. Details about the Linux/Alpha booting process are contained in
1575 the Linux/Alpha FAQ, accessible on the WWW from
1576 http://www.alphalinux.org .
1578 The usual way to load Linux on an Alpha machine is to use MILO
1579 (a bootloader that lets you pass command line parameters to the
1580 kernel just like lilo does for the x86 architecture) which can be
1581 loaded either from ARC or can be installed directly as a permanent
1582 firmware replacement from floppy (which requires changing a certain
1583 jumper on the motherboard). If you want to do either of these, say N
1584 here. If MILO doesn't work on your system (true for Jensen
1585 motherboards), you can bypass it altogether and boot Linux directly
1586 from an SRM console; say Y here in order to do that. Note that you
1587 won't be able to boot from an IDE disk using SRM.
1592 CONFIG_ALPHA_SRM_SETUP
1593 This option controls whether or not the PCI configuration set up by
1594 SRM is modified. If you say Y, the existing PCI configuration will
1597 Non-standard serial port support
1598 CONFIG_SERIAL_NONSTANDARD
1599 Say Y here if you have any non-standard serial boards -- boards
1600 which aren't supported using the standard "dumb" serial driver.
1601 This includes intelligent serial boards such as Cyclades,
1602 Digiboards, etc. These are usually used for systems that need many
1603 serial ports because they serve many terminals or dial-in
1606 Note that the answer to this question won't directly affect the
1607 kernel: saying N will just cause this configure script to skip all
1608 the questions about non-standard serial boards.
1610 Most people can say N here.
1612 Extended dumb serial driver options
1613 CONFIG_SERIAL_EXTENDED
1614 If you wish to use any non-standard features of the standard "dumb"
1615 driver, say Y here. This includes HUB6 support, shared serial
1616 interrupts, special multiport support, support for more than the
1617 four COM 1/2/3/4 boards, etc.
1619 Note that the answer to this question won't directly affect the
1620 kernel: saying N will just cause this configure script to skip all
1621 the questions about serial driver options. If unsure, say N.
1623 Support more than 4 serial ports
1624 CONFIG_SERIAL_MANY_PORTS
1625 Say Y here if you have dumb serial boards other than the four
1626 standard COM 1/2/3/4 ports. This may happen if you have an AST
1627 FourPort, Accent Async, Boca (read the Boca mini-HOWTO, available
1628 from http://metalab.unc.edu/mdw/linux.html#howto ), or other custom
1629 serial port hardware which acts similar to standard serial port
1630 hardware. If you only use the standard COM 1/2/3/4 ports, you can
1631 say N here to save some memory. You can also say Y if you have an
1632 "intelligent" multiport card such as Cyclades, Digiboards, etc.
1634 Support for sharing serial interrupts
1635 CONFIG_SERIAL_SHARE_IRQ
1636 Some serial boards have hardware support which allows multiple dumb
1637 serial ports on the same board to share a single IRQ. To enable
1638 support for this in the serial driver, say Y here.
1640 Auto detect IRQ on standard ports (unsafe)
1641 CONFIG_SERIAL_DETECT_IRQ
1642 Say Y here if you want the kernel to try to guess which IRQ
1643 to use for your serial port.
1645 This is considered unsafe; it is far better to configure the IRQ in
1646 a boot script using the setserial command.
1650 Support special multiport boards
1651 CONFIG_SERIAL_MULTIPORT
1652 Some multiport serial ports have special ports which are used to
1653 signal when there are any serial ports on the board which need
1654 servicing. Say Y here to enable the serial driver to take advantage
1655 of those special I/O ports.
1657 SGI Zilog85C30 serial support
1659 If you want to use your SGI's built-in serial ports under Linux,
1662 SGI Newport Graphics support (EXPERIMENTAL)
1663 CONFIG_SGI_NEWPORT_GFX
1664 If you have an SGI machine and you want to compile the graphics
1665 drivers, say Y here. This will include the code for the
1666 /dev/graphics and /dev/gfx drivers into the kernel for supporting
1667 virtualized access to your graphics hardware.
1669 Support the Bell Technologies HUB6 card
1671 Say Y here to enable support in the dumb serial driver to support
1674 PCMCIA serial device support
1675 CONFIG_PCMCIA_SERIAL_CS
1676 Say Y here to enable support for 16-bit PCMCIA serial devices,
1677 including serial port cards, modems, and the modem functions of
1678 multifunction ethernet/modem cards.
1680 This driver is also available as a module ( = code which can be
1681 inserted in and removed from the running kernel whenever you want).
1682 The module will be called serial_cs.o. If you want to compile it as a
1683 module, say M here and read Documentation/modules.txt. If unsure,
1686 CardBus serial device support
1687 CONFIG_PCMCIA_SERIAL_CB
1688 Say Y here to enable support for CardBus serial devices, including
1689 the modem functions of multifunction ethernet/modem devices.
1691 This driver is also available as a module ( = code which can be
1692 inserted in and removed from the running kernel whenever you want).
1693 The module will be called serial_cb.o. If you want to compile it as a
1694 module, say M here and read Documentation/modules.txt. If unsure,
1699 Find out whether you have a PCI motherboard. PCI is the name of a
1700 bus system, i.e. the way the CPU talks to the other stuff inside
1701 your box. Other bus systems are ISA, EISA, Microchannel (MCA) or
1702 VESA. If you have PCI, say Y, otherwise N.
1704 The PCI-HOWTO, available from
1705 http://metalab.unc.edu/mdw/linux.html#howto , contains valuable
1706 information about which PCI hardware does work under Linux and which
1711 On PCI systems, the BIOS can be used to detect the PCI devices and
1712 determine their configuration. However, some old PCI motherboards
1713 have BIOS bugs and may crash if this is done. Also, some embedded
1714 PCI-based systems don't have any BIOS at all. Linux can also try to
1715 detect the PCI hardware directly without using the BIOS.
1717 With this option, you can specify how Linux should detect the PCI
1718 devices. If you choose "BIOS", the BIOS will be used, if you choose
1719 "Direct", the BIOS won't be used, and if you choose "Any", the
1720 kernel will try the direct access method and falls back to the BIOS
1721 if that doesn't work. If unsure, go with the default.
1725 MicroChannel Architecture is found in some IBM PS/2 machines and
1726 laptops. It is a bus system similar to PCI or ISA. See
1727 Documentation/mca.txt (and especially the web page given there)
1728 before attempting to build an MCA bus kernel.
1730 SGI Visual Workstation support
1732 The SGI Visual Workstation series is an IA32-based workstation
1733 based on SGI systems chips with some legacy PC hardware attached.
1734 Say Y here to create a kernel to run on the SGI 320 or 540.
1735 A kernel compiled for the Visual Workstation will not run on other
1736 PC boards and vice versa.
1737 See Documentation/sgi-visws.txt for more.
1739 SGI Visual Workstation framebuffer support
1741 SGI Visual Workstation support for framebuffer graphics.
1745 The Intelligent Input/Output (I2O) architecture allows hardware
1746 drivers to be split into two parts: an operating system specific
1747 module called the OSM and an hardware specific module called the
1748 HDM. The OSM can talk to a whole range of HDM's, and ideally the
1749 HDM's are not OS dependent. This allows for the same HDM driver to
1750 be used under different operating systems if the relevant OSM is in
1751 place. In order for this to work, you need to have an I2O interface
1752 adapter card in your computer. This card contains a special I/O
1753 processor (IOP), thus allowing high speeds since the CPU does not
1754 have to deal with I/O.
1756 If you say Y here, you will get a choice of interface adapter
1757 drivers and OSM's with the following questions.
1759 This support is also available as a module ( = code which can be
1760 inserted in and removed from the running kernel whenever you want).
1761 If you want to compile it as a module, say M here and read
1762 Documentation/modules.txt. You will get modules called i2o_core.o
1769 Say Y for support of PCI bus I2O interface adapters. Currently this
1770 is the only variety supported, so you should say Y.
1772 This support is also available as a module called i2o_pci.o ( = code
1773 which can be inserted in and removed from the running kernel
1774 whenever you want). If you want to compile it as a module, say M
1775 here and read Documentation/modules.txt.
1779 Include support for the I2O Block OSM. The Block OSM presents disk
1780 and other structured block devices to the operating system.
1782 This support is also available as a module called i2o_block.o ( =
1783 code which can be inserted in and removed from the running kernel
1784 whenever you want). If you want to compile it as a module, say M
1785 here and read Documentation/modules.txt.
1789 Include support for the LAN OSM. You will also need to include
1790 support for token ring or FDDI if you wish to use token ring or FDDI
1791 I2O cards with this driver.
1793 This support is also available as a module called i2o_lan.o ( = code
1794 which can be inserted in and removed from the running kernel
1795 whenever you want). If you want to compile it as a module, say M
1796 here and read Documentation/modules.txt.
1800 Allows direct SCSI access to SCSI devices on a SCSI or FibreChannel
1801 I2O controller. You can use both the SCSI and Block OSM together if
1804 This support is also available as a module called i2o_scsi.o ( =
1805 code which can be inserted in and removed from the running kernel
1806 whenever you want). If you want to compile it as a module, say M
1807 here and read Documentation/modules.txt.
1811 If you say Y here and to "/proc filesystem support", you will be
1812 able to read I2O related information from the virtual directory
1815 This support is also available as a module called i2o_proc.o ( =
1816 code which can be inserted in and removed from the running kernel
1817 whenever you want). If you want to compile it as a module, say M
1818 here and read Documentation/modules.txt.
1820 Plug and Play support
1822 Plug and Play (PnP) is a standard for peripherals which allows those
1823 peripherals to be configured by software, e.g. assign IRQ's or other
1824 parameters. No jumpers on the cards are needed, instead the values
1825 are provided to the cards from the BIOS, from the operating system,
1826 or using a user-space utility.
1828 Say Y here if you would like Linux to configure your Plug and Play
1829 devices. You should then also say Y to "ISA Plug and Play support",
1830 below. Alternatively, you can configure your PnP devices using the
1831 user space utilities contained in the isapnptools package.
1833 This support is also available as a module ( = code which can be
1834 inserted in and removed from the running kernel whenever you want).
1835 If you want to compile it as a module, say M here and read
1836 Documentation/modules.txt.
1838 ISA Plug and Play support
1840 Say Y here if you would like support for ISA Plug and Play devices.
1842 This support is also available as a module called isapnp.o ( =
1843 code which can be inserted in and removed from the running kernel
1844 whenever you want). If you want to compile it as a module, say M
1845 here and read Documentation/modules.txt.
1849 PCMCIA/CardBus support
1851 Include kernel support for PCMCIA and CardBus devices. Because
1852 PCMCIA support requires additional components that are not part of
1853 the kernel (i.e., the pcmcia-cs package), building PCMCIA into the
1854 kernel is generally not recommended unless you have a specific
1855 need. If unsure, say N.
1857 This driver is also available as a module ( = code which can be
1858 inserted in and removed from the running kernel whenever you want).
1859 When compiled this way, there will be modules called pcmcia_core.o
1860 and ds.o. If you want to compile it as a module, say M here and
1861 read Documentation/modules.txt.
1863 You will also need David Hinds' pcmcia-cs package (see the file
1864 Documentation/Changes for location). For more information, see the
1869 There are two types of PCMCIA devices: 16-bit PC Cards, and higher
1870 performance 32-bit CardBus devices. Use this option to include
1871 support for CardBus devices. If unsure, say Y.
1873 i82365/Yenta compatible bridge support
1875 Include support for PCMCIA and CardBus host bridges that are
1876 register compatible with the Intel i82365 and/or the Yenta
1877 specification: this includes virtually all modern PCMCIA bridges.
1880 Databook TCIC host bridge support
1882 Include support for the Databook TCIC family of PCMCIA host bridges.
1883 These are only found on a handful of old systems. If unsure, say N.
1887 Inter Process Communication is a suite of library functions and
1888 system calls which let processes (running programs) synchronize and
1889 exchange information. It is generally considered to be a good thing,
1890 and some programs won't run unless you say Y here. In particular, if
1891 you want to run the DOS emulator dosemu under Linux (read the
1892 DOSEMU-HOWTO, available from
1893 http://metalab.unc.edu/mdw/linux.html#howto ), you'll need to say Y
1896 You can find documentation about IPC with "info ipc" and also in
1897 section 6.4 of the Linux Programmer's Guide, available from
1898 http://metalab.unc.edu/mdw/linux.html#guide .
1900 Saying Y here enlarges your kernel by about 18 KB. Just say Y.
1902 BSD Process Accounting
1903 CONFIG_BSD_PROCESS_ACCT
1904 If you say Y here, a user level program will be able to instruct the
1905 kernel (via a special system call) to write process accounting
1906 information to a file: whenever a process exits, information about
1907 that process will be appended to the file by the kernel. The
1908 information includes things such as creation time, owning user,
1909 command name, memory usage, controlling terminal etc. (the complete
1910 list is in the struct acct in include/linux/acct.h). It is up to the
1911 user level program to do useful things with this information. This
1912 is generally a good idea, so say Y.
1916 The sysctl interface provides a means of dynamically changing
1917 certain kernel parameters and variables on the fly without requiring
1918 a recompile of the kernel or reboot of the system. The primary
1919 interface consists of a system call, but if you say Y to "/proc
1920 filesystem support", a tree of modifiable sysctl entries will be
1921 generated beneath the /proc/sys directory. They are explained in the
1922 files in Documentation/sysctl/. Note that enabling this option will
1923 enlarge the kernel by at least 8 KB.
1925 As it is generally a good thing, you should say Y here unless
1926 building a kernel for install/rescue disks or your system is very
1929 Kernel core (/proc/kcore) format
1931 If you enabled support for /proc filesystem then the file /proc/kcore
1932 will contain the kernel core image. This can be used in gdb:
1934 $ cd /usr/src/linux ; gdb vmlinux /proc/kcore
1936 Selecting ELF will make /proc/kcore appear in ELF core format as defined
1937 by the Executable and Linking Format specification. Selecting A.OUT will
1938 choose the old "a.out" format which may be necessary for some old versions
1939 of binutils or on some architectures.
1941 This is especially useful if you have compiled the kernel with "-g" option
1942 to preserve debugging information. It is mainly used for examining kernel
1943 data structures on the live kernel so if you don't understand what this
1944 means or are not a kernel hacker, just leave it at its default value ELF.
1946 Kernel support for ELF binaries
1948 ELF (Executable and Linkable Format) is a format for libraries and
1949 executables used across different architectures and operating
1950 systems. Saying Y here will enable your kernel to run ELF binaries
1951 and enlarge it by about 13 KB. ELF support under Linux has now all
1952 but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC)
1953 because it is portable (this does *not* mean that you will be able
1954 to run executables from different architectures or operating systems
1955 however) and makes building run-time libraries very easy. Many new
1956 executables are distributed solely in ELF format. You definitely
1959 Information about ELF is contained in the ELF HOWTO available from
1960 http://metalab.unc.edu/mdw/linux.html#howto .
1962 If you find that after upgrading from Linux kernel 1.2 and saying Y
1963 here, you still can't run any ELF binaries (they just crash), then
1964 you'll have to install the newest ELF runtime libraries, including
1965 ld.so (check the file Documentation/Changes for location and latest
1968 If you want to compile this as a module ( = code which can be
1969 inserted in and removed from the running kernel whenever you want),
1970 say M here and read Documentation/modules.txt. The module will be
1971 called binfmt_elf.o. Saying M or N here is dangerous because some
1972 crucial programs on your system might be in ELF format.
1974 Kernel support for A.OUT binaries
1976 A.out (Assembler.OUTput) is a set of formats for libraries and
1977 executables used in the earliest versions of UNIX. Linux used the
1978 a.out formats QMAGIC and ZMAGIC until they were replaced with the
1981 As more and more programs are converted to ELF, the use for a.out
1982 will gradually diminish. If you disable this option it will reduce
1983 your kernel by one page. This is not much and by itself does not
1984 warrant removing support. However its removal is a good idea if you
1985 wish to ensure that absolutely none of your programs will use this
1986 older executable format. If you don't know what to answer at this
1987 point then answer Y. If someone told you "You need a kernel with
1988 QMAGIC support" then you'll have to say Y here. You may answer M to
1989 compile a.out support as a module and later load the module when you
1990 want to use a program or library in a.out format. The module will be
1991 called binfmt_aout.o. Saying M or N here is dangerous though,
1992 because some crucial programs on your system might still be in A.OUT
1995 Kernel support for Linux/Intel ELF binaries
1997 Say Y here if you want to be able to execute Linux/Intel ELF
1998 binaries just like native Alpha binaries on your Alpha machine. For
1999 this to work, you need to have the emulator /usr/bin/em86 in place.
2001 You can get the same functionality by saying N here and saying Y to
2002 "Kernel support for MISC binaries".
2004 You may answer M to compile the emulation support as a module and
2005 later load the module when you want to use a Linux/Intel binary. The
2006 module will be called binfmt_em86.o. If unsure, say Y.
2008 Kernel support for MISC binaries
2010 If you say Y here, it will be possible to plug wrapper-driven binary
2011 formats into the kernel. You will like this especially when you use
2012 programs that need an interpreter to run like Java, Python or
2013 Emacs-Lisp. It's also useful if you often run DOS executables under
2014 the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
2015 http://metalab.unc.edu/mdw/linux.html#howto ). Once you have
2016 registered such a binary class with the kernel, you can start one of
2017 those programs simply by typing in its name at a shell prompt; Linux
2018 will automatically feed it to the correct interpreter.
2020 You can do other nice things, too. Read the file
2021 Documentation/binfmt_misc.txt to learn how to use this feature, and
2022 Documentation/java.txt for information about how to include Java
2025 You must say Y to "proc filesystem support" (CONFIG_PROC_FS) to
2026 use this part of the kernel.
2028 You may say M here for module support and later load the module when
2029 you have use for it; the module is called binfmt_misc.o. If you
2030 don't know what to answer at this point, say Y.
2032 Solaris binary emulation (EXPERIMENTAL)
2034 This is experimental code which will enable you to run (many)
2035 Solaris binaries on your SPARC Linux machine.
2037 This code is also available as a module ( = code which can be
2038 inserted in and removed from the running kernel whenever you want).
2039 The module will be called solaris.o. If you want to compile it as a
2040 module, say M here and read Documentation/modules.txt.
2044 This is the processor type of your CPU. This information is used for
2045 optimizing purposes. In order to compile a kernel that can run on
2046 all x86 CPU types (albeit not optimally fast), you can specify
2049 If you specify one of "486" or "586" or "Pentium" or "PPro", then
2050 the kernel will not necessarily run on earlier architectures (e.g. a
2051 Pentium optimized kernel will run on a PPro, but not necessarily on
2054 Here are the settings recommended for greatest speed:
2055 - "386" for the AMD/Cyrix/Intel 386DX/DXL/SL/SLC/SX, Cyrix/TI
2056 486DLC/DLC2 and UMC 486SX-S. Only "386" kernels will run on a 386
2058 - "486" for the AMD/Cyrix/IBM/Intel 486DX/DX2/DX4 or
2059 SL/SLC/SLC2/SLC3/SX/SX2, AMD/Cyrix 5x86, NexGen Nx586 and
2061 - "586" for generic Pentium CPUs, possibly lacking the TSC
2062 (time stamp counter) register.
2063 - "Pentium" for the Intel Pentium/Pentium MMX, AMD K5, K6 and
2065 - "PPro" for the Cyrix/IBM/National Semiconductor 6x86MX, MII and
2066 Intel Pentium II/Pentium Pro.
2068 If you don't know what to do, choose "386".
2072 Saying Y here will allow you to use Linux in text mode through a
2073 display that complies with the generic VGA standard. Virtually
2074 everyone wants that.
2076 The program SVGATextMode can be used to utilize SVGA video cards to
2077 their full potential in text mode. Download it from
2078 ftp://metalab.unc.edu/pub/Linux/utils/console .
2082 Video mode selection support
2084 This enables support for text mode selection on kernel startup. If
2085 you want to take advantage of some high-resolution text mode your
2086 card's BIOS offers, but the traditional Linux utilities like
2087 SVGATextMode don't, you can say Y here and set the mode using the
2088 "vga=" option from your boot loader (lilo or loadlin) or set
2089 "vga=ask" which brings up a video mode menu on kernel startup. (Try
2090 "man bootparam" or see the documentation of your boot loader about
2091 how to pass options to the kernel. The lilo procedure is also
2092 explained in the SCSI-HOWTO, available from
2093 http://metalab.unc.edu/mdw/linux.html#howto .)
2095 Read the file Documentation/svga.txt for more information about the
2096 Video mode selection support. If unsure, say N.
2098 Support for frame buffer devices (EXPERIMENTAL)
2100 The frame buffer device provides an abstraction for the graphics
2101 hardware. It represents the frame buffer of some video hardware and
2102 allows application software to access the graphics hardware through
2103 a well-defined interface, so the software doesn't need to know
2104 anything about the low-level (hardware register) stuff.
2106 Frame buffer devices work identically across the different
2107 architectures supported by Linux and make the implementation of
2108 application programs easier and more portable; at this point, an X
2109 server exists which uses the frame buffer device exclusively.
2110 On several non-X86 architectures, the frame buffer device is the
2111 only way to use the graphics hardware.
2113 The device is accessed through special device nodes, usually located
2114 in the /dev directory, i.e. /dev/fb*.
2116 You need an utility program called fbset to make full use of frame
2117 buffer devices. Please read Documentation/fb/framebuffer.txt and the
2118 Framebuffer-HOWTO at
2119 http://www.tahallah.demon.co.uk/programming/prog.html for more
2122 Say Y here and to the driver for your graphics board below if you
2123 are compiling a kernel for a non-x86 architecture.
2125 If you are compiling for the x86 architecture, you can say Y if you
2126 want to play with it, but it is not essential. Please note that
2127 running graphical applications that directly touch the hardware
2128 (e.g. an accelerated X server) and that are not frame buffer
2129 device-aware may cause unexpected results. If unsure, say N.
2133 This is the frame buffer device driver for the Acorn VIDC graphics
2136 Apollo frame buffer device
2138 This is the frame buffer device driver for the monochrome graphics
2139 hardware found in some Apollo workstations.
2141 Amiga native chipset support
2143 This is the frame buffer device driver for the builtin graphics
2144 chipset found in Amigas.
2146 Amiga OCS chipset support
2148 This enables support for the original Agnus and Denise video chips,
2149 found in the Amiga 1000 and most A500's and A2000's. If you intend
2150 to run Linux on any of these systems, say Y; otherwise say N.
2152 Amiga ECS chipset support
2154 This enables support for the Enhanced Chip Set, found in later
2155 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
2156 you intend to run Linux on any of these systems, say Y; otherwise
2159 Amiga AGA chipset support
2161 This enables support for the Advanced Graphics Architecture (also
2162 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
2163 and CD32. If you intend to run Linux on any of these systems, say Y;
2166 Amiga CyberVision support
2168 This enables support for the Cybervision 64 graphics card from
2169 Phase5. Please note that its use is not all that intuitive (i.e. if
2170 you have any questions, be sure to ask!). Say N unless you have a
2171 Cybervision 64 or plan to get one before you next recompile the
2172 kernel. Please note that this driver DOES NOT support the
2173 Cybervision 64 3D card, as they use incompatible video chips.
2175 Amiga CyberVision3D support (EXPERIMENTAL)
2177 This enables support for the Cybervision 64/3D graphics card from
2178 Phase5. Please note that its use is not all that intuitive (i.e. if
2179 you have any questions, be sure to ask!). Say N unless you have a
2180 Cybervision 64/3D or plan to get one before you next recompile the
2181 kernel. Please note that this driver DOES NOT support the older
2182 Cybervision 64 card, as they use incompatible video chips.
2184 Amiga RetinaZ3 support (EXPERIMENTAL)
2186 This enables support for the Retina Z3 graphics card. Say N unless
2187 you have a Retina Z3 or plan to get one before you next recompile
2190 Cirrus Logic generic driver (EXPERIMENTAL)
2192 This enables support for Cirrus Logic GD542x/543x based boards on
2193 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
2195 If you have a PCI-based system, this enables support for these
2196 chips: GD-543x, GD-544x, GD-5480.
2198 Please read the file Documentation/fb/clgenfb.txt.
2200 Say N unless you have such a graphics board or plan to get one
2201 before you next recompile the kernel.
2203 Permedia2 support (EXPERIMENTAL)
2205 Say Y here if this is your graphics board.
2209 Say Y here if you want to run Linux on an MC680x0-based Apollo
2210 Domain workstation such as the DN3500.
2212 Apollo 3c505 support
2213 CONFIG_APOLLO_ELPLUS
2214 Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
2215 If you don't have one made for Apollos, you can use one from a PC,
2216 except that your Apollo won't be able to boot from it (because the
2217 code in the ROM will be for a PC).
2219 Atari native chipset support
2221 This is the frame buffer device driver for the builtin graphics
2222 chipset found in Ataris.
2224 Open Firmware frame buffer device support
2226 Say Y if you want support with Open Firmware for your graphics
2229 S3 Trio frame buffer device support
2231 If you have a S3 Trio say Y. Say N for S3 Virge.
2233 ATI Mach64 display support
2234 CONFIG_FB_ATY (EXPERIMENTAL)
2235 This driver supports graphics boards with the ATI Mach64 chips.
2236 Say Y if you have such a graphics board.
2238 The driver is also available as a module ( = code which can be
2239 inserted and removed from the running kernel whenever you want). The
2240 module will be called atyfb.o. If you want to compile it as a
2241 module, say M here and read Documentation/modules.txt.
2243 PowerMac "control" frame buffer device support
2245 This driver supports a frame buffer for the graphics adapter in the
2246 Power Macintosh 7300 and others.
2248 PowerMac "platinum" frame buffer device support
2250 This driver supports a frame buffer for the "platinum" graphics
2251 adapter in some Power Macintoshes.
2253 PowerMac "valkyrie" frame buffer device support
2255 This driver supports a frame buffer for the "valkyrie" graphics
2256 adapter in some Power Macintoshes.
2258 Chips 65550 display support
2260 This is the frame buffer device driver for the Chips & Technologies
2261 65550 graphics chip in PowerBooks.
2263 Mac frame buffer device
2265 This is the frame buffer device driver for the graphics hardware in
2268 HP300 frame buffer device
2270 This is the frame buffer device driver for the Topcat graphics
2271 hardware found in HP300 workstations.
2273 TGA frame buffer support
2275 This is the frame buffer device driver for generic TGA graphic
2276 cards. Say Y if you have one of those.
2278 VESA VGA graphics console
2280 This is the frame buffer device driver for generic VESA 2.0
2281 compliant graphic cards. The older VESA 1.2 cards are not supported.
2282 You will get a boot time penguin logo at no additional cost. Please
2283 read Documentation/fb/vesafb.txt. If unsure, say Y.
2285 VGA 16-color graphics console
2287 This is the frame buffer device driver for VGA 16 color graphic
2288 cards. Say Y if you have such a card.
2290 This code is also available as a module. If you want to compile it
2291 as a module ( = code which can be inserted in and removed from the
2292 running kernel whenever you want), say M here and read
2293 Documentation/modules.txt. The module will be called vga16fb.o.
2295 Backward compatibility mode for Xpmac
2296 CONFIG_FB_COMPAT_XPMAC
2297 If you use the Xpmac X server (common with mklinux), you'll need to
2298 say Y here to use X. You should consider changing to XFree86 which
2299 includes a server that supports the frame buffer device directly
2302 Matrox unified accelerated driver (EXPERIMENTAL)
2304 Say Y here if you have Matrox Millennium, Matrox Millennium II,
2305 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
2306 Mystique G200, Matrox Millennium G200 or Matrox Marvel G200 video
2307 card in your box. At this time, support for the G100, Mystique G200
2308 and Marvel G200 is untested.
2310 This driver is also available as a module ( = code which can be
2311 inserted and removed from the running kernel whenever you want).
2312 The module will be called matroxfb.o. If you want to compile it as
2313 a module, say M here and read Documentation/modules.txt.
2315 You can pass several parameters to the driver at boot time or at
2316 module load time. The parameters look like "video=matrox:XXX", where
2317 the meaning of XXX can be found at the end of the main source file
2318 (drivers/video/matroxfb.c). Please see the file
2319 Documentation/fb/matroxfb.txt.
2321 Matrox Millennium support
2322 CONFIG_FB_MATROX_MILLENIUM
2323 Say Y here if you have a Matrox Millennium or Matrox Millennium II
2324 video card. If you select "Advanced lowlevel driver options" below,
2325 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
2326 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
2327 also use font widths different from 8.
2329 Matrox Mystique support
2330 CONFIG_FB_MATROX_MYSTIQUE
2331 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
2332 video card. If you select "Advanced lowlevel driver options" below,
2333 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
2334 packed pixel and 32 bpp packed pixel. You can also use font widths
2337 Matrox G100/G200/G400 support
2338 CONFIG_FB_MATROX_G100
2339 Say Y here if you have a Matrox Productiva G100, Matrox Mystique
2340 G200, Matrox Marvel G200 or Matrox Millennium G200 video card. If
2341 you select "Advanced lowlevel driver options", you should check 8
2342 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed pixel and 32
2343 bpp packed pixel. You can also use font widths different from 8.
2345 Matrox unified driver multihead support
2346 CONFIG_FB_MATROX_MULTIHEAD
2347 Say Y here if you have more than one (supported) Matrox device in
2348 your computer and you want to use all of them. If you have only one
2349 device, you should say N because the driver compiled with Y is
2350 larger and a bit slower, especially on ia32 (ix86).
2352 If you said M to "Matrox unified accelerated driver" and N here, you
2353 will still be able to use several Matrox devices simultaneously.
2354 This is slightly faster but uses 40 KB of kernel memory per Matrox
2355 card. You do this by inserting several instances of the module
2356 matroxfb.o into the kernel with insmod, supplying the parameter
2357 "dev=N" where N is 0, 1, etc. for the different Matrox devices.
2359 MDA text console (dual-headed)
2361 Say Y here if you have an old MDA or monochrome Hercules graphics
2362 adapter in your system acting as a second head ( = video card). You
2363 will then be able to use two monitors with your Linux system. Do not
2364 say Y here if your MDA card is the primary card in your system; the
2365 normal VGA driver will handle it.
2367 This driver is also available as a module ( = code which can be
2368 inserted and removed from the running kernel whenever you want).
2369 The module will be called mdacon.o. If you want to compile it as
2370 a module, say M here and read Documentation/modules.txt.
2374 SBUS and UPA frame buffers
2376 Say Y if you want support for SBUS or UPA based frame buffer device.
2378 Creator/Creator3D support
2380 This is the frame buffer device driver for the Creator and Creator3D
2383 CGsix (GX,TurboGX) support
2385 This is the frame buffer device driver for the CGsix (GX, TurboGX)
2390 This is the frame buffer device driver for the BWtwo frame buffer.
2394 This is the frame buffer device driver for the CGthree frame buffer.
2396 TCX (SS4/SS5 only) support
2398 This is the frame buffer device driver for the TCX 24/8bit frame
2401 Virtual Frame Buffer support (ONLY FOR TESTING!)
2403 This is a `virtual' frame buffer device. It operates on a chunk of
2404 unswapable kernel memory instead of on the memory of a graphics
2405 board. This means you cannot see any output sent to this frame
2406 buffer device, while it does consume precious memory. The main use
2407 of this frame buffer device is testing and debugging the frame
2408 buffer subsystem. Do NOT enable it for normal systems! To protect
2409 the innocent, it has to be enabled explicitly at boot time using the
2410 kernel option `video=vfb:'.
2412 This driver is also available as a module ( = code which can be
2413 inserted and removed from the running kernel whenever you want). The
2414 module will be called vfb.o. If you want to compile it as a module,
2415 say M here and read Documentation/modules.txt.
2419 Advanced low level driver options
2420 CONFIG_FBCON_ADVANCED
2421 The frame buffer console uses character drawing routines that are
2422 tailored to the specific organization of pixels in the memory of
2423 your graphics hardware. These are called the low level frame buffer
2424 console drivers. Note that they are used for text console output
2425 only; they are NOT needed for graphical applications.
2427 If you say N here, the needed low level drivers are automatically
2428 enabled, depending on what frame buffer devices you selected above.
2429 This is recommended for most users.
2431 If you say Y here, you have more fine-grained control over which low
2432 level drivers are enabled. You can e.g. leave out low level drivers
2433 for color depths you do not intend to use for text consoles.
2435 Low level frame buffer console drivers can be modules ( = code which
2436 can be inserted and removed from the running kernel whenever you
2437 want). The modules will be called fbcon-*.o. If you want to compile
2438 (some of) them as modules, read Documentation/modules.txt.
2444 This is the low level frame buffer console driver for monochrome
2445 (2 colors) packed pixels.
2447 2 bpp packed pixels support
2449 This is the low level frame buffer console driver for 2 bits per
2450 pixel (4 colors) packed pixels.
2452 4 bpp packed pixels support
2454 This is the low level frame buffer console driver for 4 bits per
2455 pixel (16 colors) packed pixels.
2457 8 bpp packed pixels support
2459 This is the low level frame buffer console driver for 8 bits per
2460 pixel (256 colors) packed pixels.
2462 16 bpp packed pixels support
2464 This is the low level frame buffer console driver for 15 or 16 bits
2465 per pixel (32K or 64K colors, also known as `hicolor') packed
2468 24 bpp packed pixels support
2470 This is the low level frame buffer console driver for 24 bits per
2471 pixel (16M colors, also known as `truecolor') packed pixels. It is
2472 NOT for `sparse' 32 bits per pixel mode.
2474 32 bpp packed pixels support
2476 This is the low level frame buffer console driver for 32 bits per
2477 pixel (16M colors, also known as `truecolor') sparse packed pixels.
2479 Amiga bitplanes support
2481 This is the low level frame buffer console driver for 1 to 8
2482 bitplanes (2 to 256 colors) on Amiga.
2484 Amiga interleaved bitplanes support
2486 This is the low level frame buffer console driver for 1 to 8
2487 interleaved bitplanes (2 to 256 colors) on Amiga.
2489 Atari interleaved bitplanes (2 planes) support
2490 CONFIG_FBCON_IPLAN2P2
2491 This is the low level frame buffer console driver for 2 interleaved
2492 bitplanes (4 colors) on Atari.
2494 Atari interleaved bitplanes (4 planes) support
2495 CONFIG_FBCON_IPLAN2P4
2496 This is the low level frame buffer console driver for 4 interleaved
2497 bitplanes (16 colors) on Atari.
2499 Atari interleaved bitplanes (8 planes) support
2500 CONFIG_FBCON_IPLAN2P8
2501 This is the low level frame buffer console driver for 8 interleaved
2502 bitplanes (256 colors) on Atari.
2504 Mac variable bpp packed pixels support
2506 This is the low level frame buffer console driver for 1/2/4/8/16/32
2507 bits per pixel packed pixels on Mac. It supports variable font
2508 widths for low resolution screens.
2510 #VGA 16-color planar support
2511 #CONFIG_FBCON_VGA_PLANES
2516 VGA characters/attributes support
2518 This is the low level frame buffer console driver for VGA text mode;
2519 it is used by frame buffer device drivers that support VGA text
2522 Parallel-port support
2524 If you want to use devices connected to your machine's parallel port
2525 (the connector at the computer with 25 holes), e.g. printer, ZIP
2526 drive, PLIP link (Parallel Line Internet Protocol is mainly used to
2527 create a mini network by connecting the parallel ports of two local
2528 machines) etc., then you need to say Y here; please read
2529 Documentation/parport.txt and drivers/misc/BUGS-parport.
2531 For extensive information about drivers for many devices attaching
2532 to the parallel port see http://www.torque.net/linux-pp.html on the
2535 It is possible to share a single parallel port among several devices
2536 and it is safe to compile all the corresponding drivers into the
2537 kernel. If you want to compile parallel port support as a module ( =
2538 code which can be inserted in and removed from the running kernel
2539 whenever you want), say M here and read Documentation/modules.txt.
2540 The module will be called parport.o. If you have more than one
2541 parallel port and want to specify which port and IRQ to be used by
2542 this driver at module load time, take a look at
2543 Documentation/networking/parport.txt.
2549 You should say Y here if you have a PC-style parallel port. All IBM
2550 PC compatible computers and some Alphas have PC-style parallel
2553 This code is also available as a module. If you want to compile it
2554 as a module ( = code which can be inserted in and removed from the
2555 running kernel whenever you want), say M here and read
2556 Documentation/modules.txt. The module will be called parport_pc.o.
2560 Use FIFO/DMA if available
2561 CONFIG_PARPORT_PC_FIFO
2562 Many parallel port chipsets provide hardware that can speed up
2563 printing. Say Y here if you want to take advantage of that.
2565 As well as actually having a FIFO, or DMA capability, the kernel
2566 will need to know which IRQ the parallel port has. By default,
2567 parallel port interrupts will not be used, and so neither will the
2568 FIFO. See Documentation/parport.txt to find out how to specify
2569 which IRQ/DMA to use.
2571 Support for PCMCIA management for PC-style ports
2572 CONFIG_PARPORT_PC_PCMCIA
2573 Say Y here if you need PCMCIA support for your PC-style parallel
2574 ports. If unsure, say N.
2576 Support foreign hardware
2577 CONFIG_PARPORT_OTHER
2578 Say Y here if you want to be able to load driver modules to support
2579 other non-standard types of parallel ports. This causes a
2580 performance loss, so most people say N.
2582 Sun Ultra/AX-style hardware
2584 Say Y here if you need support for the parallel port hardware on Sun
2585 Ultra/AX machines. This code is also available as a module (say M),
2586 called parport_ax.o. If in doubt, saying N is the safe plan.
2588 IEEE1284 transfer modes
2590 If you have a printer that supports status readback or device ID, or
2591 want to use a device that uses enhanced parallel port transfer modes
2592 such as EPP and ECP, say Y here to enable advanced IEEE 1284
2593 transfer modes. Also say Y if you want device ID information to
2594 appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
2596 Enable loadable module support
2598 Kernel modules are small pieces of compiled code which can be
2599 inserted in or removed from the running kernel, using the programs
2600 insmod and rmmod. This is described in the file
2601 Documentation/modules.txt, including the fact that you have to say
2602 "make modules" in order to compile the modules that you chose during
2603 kernel configuration. Modules can be device drivers, file systems,
2604 binary executable formats, and so on. If you think that you may want
2605 to make use of modules with this kernel in the future, then say Y
2606 here. If unsure, say Y.
2608 Set version information on all symbols for modules
2610 Usually, modules have to be recompiled whenever you switch to a new
2611 kernel. Saying Y here makes it possible, and safe, to use the
2612 same modules even after compiling a new kernel; this requires the
2613 program modprobe. All the software needed for module support is in
2614 the modutils package (check the file Documentation/Changes for
2615 location and latest version). NOTE: if you say Y here but don't
2616 have the program genksyms (which is also contained in the above
2617 mentioned modutils package), then the building of your kernel will
2618 fail. If you are going to use modules that are generated from
2619 non-kernel sources, you would benefit from this option. Otherwise
2620 it's not that important. So, N ought to be a safe bet.
2622 Kernel module loader support
2624 Normally when you have selected some drivers and/or filesystems to
2625 be created as loadable modules, you also have the responsibility to
2626 load the corresponding modules (using the programs insmod or
2627 modprobe) before you can use them. If you say Y here however, the
2628 kernel will be able to load modules for itself: when a part of the
2629 kernel needs a module, it runs modprobe with the appropriate
2630 arguments, thereby loading the module if it is available. (This is a
2631 replacement for kerneld.) Say Y here and read about configuring it
2632 in Documentation/kmod.txt.
2634 ARP daemon support (EXPERIMENTAL)
2636 Normally, the kernel maintains an internal cache which maps IP
2637 addresses to hardware addresses on the local network, so that
2638 Ethernet/Token Ring/ etc. frames are sent to the proper address on
2639 the physical networking layer. For small networks having a few
2640 hundred directly connected hosts or less, keeping this address
2641 resolution (ARP) cache inside the kernel works well. However,
2642 maintaining an internal ARP cache does not work well for very large
2643 switched networks, and will use a lot of kernel memory if TCP/IP
2644 connections are made to many machines on the network.
2646 If you say Y here, the kernel's internal ARP cache will never grow
2647 to more than 256 entries (the oldest entries are expired in a LIFO
2648 manner) and communication will be attempted with the user space ARP
2649 daemon arpd. Arpd then answers the address resolution request either
2650 from its own cache or by asking the net.
2652 This code is experimental and also obsolete. If you want to use it,
2653 you need to find a version of the daemon arpd on the net somewhere,
2654 and you should also say Y to "Kernel/User network link driver",
2655 below. If unsure, say N.
2659 These are the protocols used on the Internet and on most local
2660 Ethernets. It is highly recommended to say Y here (this will enlarge
2661 your kernel by about 144 KB), since some programs (e.g. the X window
2662 system) use TCP/IP even if your machine is not connected to any
2663 other computer. You will get the so-called loopback device which
2664 allows you to ping yourself (great fun, that!).
2666 For an excellent introduction to Linux networking, please read the
2667 NET-3-HOWTO, available from
2668 http://metalab.unc.edu/mdw/linux.html#howto .
2670 This option is also necessary if you want to use the full power of
2671 term (term is a program which gives you almost full Internet
2672 connectivity if you have a regular dial up shell account on some
2673 Internet connected Unix computer; for more information, read
2674 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html ).
2676 If you say Y here and also to "/proc filesystem support" and "Sysctl
2677 support" below, you can change various aspects of the behavior of
2678 the TCP/IP code by writing to the (virtual) files in
2679 /proc/sys/net/ipv4/*; the options are explained in the file
2680 Documentation/Networking/ip-sysctl.txt.
2682 Short answer: say Y.
2686 This is code for addressing several networked computers at once,
2687 enlarging your kernel by about 2 kB. You need multicasting if you
2688 intend to participate in the MBONE, a high bandwidth network on top
2689 of the Internet which carries audio and video broadcasts. More
2690 information about the MBONE is on the WWW at
2691 http://www-itg.lbl.gov/mbone/ . Information about the multicast
2692 capabilities of the various network cards is contained in
2693 Documentation/networking/multicast.txt. For most people, it's safe
2697 CONFIG_IP_ADVANCED_ROUTER
2698 If you intend to run your Linux box mostly as a router, i.e. as a
2699 computer that forwards and redistributes network packets, say Y; you
2700 will then be presented with several options that allow more precise
2701 control about the routing process.
2703 The answer to this question won't directly affect the kernel:
2704 answering N will just cause this configure script to skip all the
2705 questions about advanced routing.
2707 Note that your box can only act as a router if you enable IP
2708 forwarding in your kernel; you can do that by saying Y to "/proc
2709 filesystem support" and "Sysctl support" below and executing the
2712 echo "1" > /proc/sys/net/ipv4/ip_forward
2714 at boot time after the /proc filesystem has been mounted.
2716 If you turn on IP forwarding, you will also get the rp_filter, which
2717 automatically rejects incoming packets if the routing table entry
2718 for their source address doesn't match the network interface they're
2719 arriving on. This has security advantages because it prevents the
2720 so-called IP spoofing, however it can pose problems if you use
2721 asymmetric routing (packets from you to a host take a different path
2722 than packets from that host to you) or if you operate a non-routing
2723 host which has several IP addresses on different interfaces. To turn
2726 echo 0 > /proc/sys/net/ipv4/conf/<device>/rp_filter
2728 echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter
2730 If unsure, say N here.
2733 CONFIG_IP_MULTIPLE_TABLES
2734 Normally, a router decides what to do with a received packet based
2735 solely on the packet's final destination address. If you say Y here,
2736 the Linux router will also be able to take the packet's source
2737 address into account. Furthermore, if you also say Y to "IP: use TOS
2738 value as routing key" below, the TOS (Type-Of-Service) field of the
2739 packet can be used for routing decisions as well. In addition, if
2740 you say Y here and to "IP: fast network address translation" below,
2741 the router will also be able to modify source and destination
2742 addresses of forwarded packets.
2744 If you are interested in this, please see the preliminary
2745 documentation at http://www.compendium.com.ar/policy-routing.txt and
2746 ftp://post.tepkom.ru/pub/vol2/Linux/docs/advanced-routing.tex . You
2747 will need supporting software from ftp://ftp.inr.ac.ru/ip-routing/
2751 IP: equal cost multipath
2752 CONFIG_IP_ROUTE_MULTIPATH
2753 Normally, the routing tables specify a single action to be taken in
2754 a deterministic manner for a given packet. If you say Y here
2755 however, it becomes possible to attach several actions to a packet
2756 pattern, in effect specifying several alternative paths to travel
2757 for those packets. The router considers all these paths to be of
2758 equal "cost" and chooses one of them in a non-deterministic fashion
2759 if a matching packet arrives.
2761 IP: use TOS value as routing key
2763 The header of every IP packet carries a TOS (Type of Service) value
2764 with which the packet requests a certain treatment, e.g. low latency
2765 (for interactive traffic), high throughput, or high reliability. If
2766 you say Y here, you will be able to specify different routes for
2767 packets with different TOS values.
2769 IP: use FWMARK value as routing key
2770 CONFIG_IP_ROUTE_FWMARK
2771 If you say Y here, you will be able to specify different routes for
2772 packets with different FWMARK ("firewalling mark") values
2773 (see ipchains(8), "-m" argument).
2775 IP: verbose route monitoring
2776 CONFIG_IP_ROUTE_VERBOSE
2777 If you say Y here, which is recommended, then the kernel will print
2778 verbose messages regarding the routing, for example warnings about
2779 received packets which look strange and could be evidence of an
2780 attack or a misconfigured system somewhere. The information is
2781 handled by the klogd daemon which is responsible for kernel messages
2784 IP: large routing tables
2785 CONFIG_IP_ROUTE_LARGE_TABLES
2786 If you have routing zones that grow to more than about 64 entries,
2787 you may want to say Y here to speed up the routing process.
2789 IP: fast network address translation
2791 If you say Y here, your router will be able to modify source and
2792 destination addresses of packets that pass through it, in a manner
2793 you specify. General information about Network Address Translation
2794 can be gotten from the document
2795 http://www.csn.tu-chemnitz.de/~mha/linux-ip-nat/diplom/nat.html
2797 IP: optimize as router not host
2799 Some Linux network drivers use a technique called copy and checksum
2800 to optimize host performance. For a machine which acts as a router
2801 most of the time and is forwarding most packets to another host this
2802 is however a loss. If you say Y here, copy and checksum will be
2803 switched off. In the future, it may make other changes which
2804 optimize for router operation.
2806 Note that your box can only act as a router if you enable IP
2807 forwarding in your kernel; you can do that by saying Y to "/proc
2808 filesystem support" and "Sysctl support" below and executing the
2811 echo "1" > /proc/sys/net/ipv4/ip_forward
2813 at boot time after the /proc filesystem has been mounted. You can do
2814 that even if you say N here.
2816 If unsure, say N here.
2818 IP: kernel level autoconfiguration
2820 This enables automatic configuration of IP addresses of devices and
2821 of the routing table during kernel boot, based on either information
2822 supplied at the kernel command line or by BOOTP or RARP protocols.
2823 You need to say Y only for diskless machines requiring network
2824 access to boot (in which case you want to say Y to "Root file system
2825 on NFS" as well), because all other machines configure the network
2826 in their startup scripts.
2830 If you want your Linux box to mount its whole root filesystem (the
2831 one containing the directory /) from some other computer over the
2832 net via NFS and you want the IP address of your computer to be
2833 discovered automatically at boot time using the BOOTP protocol (a
2834 special protocol designed for doing this job), say Y here. In case
2835 the boot ROM of your network card was designed for booting Linux and
2836 does BOOTP itself, providing all necessary information on the kernel
2837 command line, you can say N here. If unsure, say Y. Note that if you
2838 want to use BOOTP, a BOOTP server must be operating on your network.
2839 Read Documentation/nfsroot.txt for details.
2843 If you want your Linux box to mount its whole root filesystem (the
2844 one containing the directory /) from some other computer over the
2845 net via NFS and you want the IP address of your computer to be
2846 discovered automatically at boot time using the RARP protocol (an
2847 older protocol which is being obsoleted by BOOTP and DHCP), say Y
2848 here. Note that if you want to use RARP, a RARP server must be
2849 operating on your network. Read Documentation/nfsroot.txt for
2854 Tunneling means encapsulating data of one protocol type within
2855 another protocol and sending it over a channel that understands the
2856 encapsulating protocol. This particular tunneling driver implements
2857 encapsulation of IP within IP, which sounds kind of pointless, but
2858 can be useful if you want to make your (or some other) machine
2859 appear on a different network than it physically is, or to use
2860 mobile-IP facilities (allowing laptops to seamlessly move between
2861 networks without changing their IP addresses; check out
2862 http://anchor.cs.binghamton.edu/~mobileip/LJ/index.html ).
2864 Saying Y to this option will produce two modules ( = code which can
2865 be inserted in and removed from the running kernel whenever you
2866 want). Most people won't need this and can say N.
2868 IP: GRE tunnels over IP
2870 Tunneling means encapsulating data of one protocol type within
2871 another protocol and sending it over a channel that understands the
2872 encapsulating protocol. This particular tunneling driver implements
2873 GRE (Generic Routing Encapsulation) and at this time allows
2874 encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
2875 This driver is useful if the other endpoint is a Cisco router: Cisco
2876 likes GRE much better than the other Linux tunneling driver ("IP:
2877 tunneling" above). In addition, GRE allows multicast redistribution
2880 IP: broadcast GRE over IP
2881 CONFIG_NET_IPGRE_BROADCAST
2882 One application of GRE/IP is to construct a broadcast WAN (Wide Area
2883 Network), which looks like a normal Ethernet LAN (Local Area
2884 Network), but can be distributed all over the Internet. If you want
2885 to do that, say Y here and to "IP: multicast routing" below.
2887 IP: aliasing support
2889 Sometimes it is useful to give several IP addresses to a single
2890 physical network interface (serial port or Ethernet card). The most
2891 common case is that you want to serve different WWW or FTP documents
2892 to the outside depending on which of your host names was used to
2893 connect to you. This is called "multihosting" or "virtual domains"
2894 or "virtual hosting services" and is explained in the
2895 Virtual-Services-HOWTO, available from
2896 http://metalab.unc.edu/mdw/linux.html#howto .
2898 Another scenario would be that there are two logical networks living
2899 on your local Ethernet and you want to access them both with the
2900 same Ethernet card. This can also be done if you say Y here.
2902 The configuration of these alias addresses is done with a special
2903 name syntax explained in Documentation/networking/alias.txt and in
2904 the IP-Alias mini-HOWTO. If you want this, say Y. Most people don't
2907 IP: multicast routing
2909 This is used if you want your machine to act as a router for IP
2910 packets that have several destination addresses. It is needed on the
2911 MBONE, a high bandwidth network on top of the Internet which carries
2912 audio and video broadcasts. In order to do that, you would most
2913 likely run the program mrouted. Information about the multicast
2914 capabilities of the various network cards is contained in
2915 Documentation/networking/multicast.txt. If you haven't heard about
2916 it, you don't need it.
2918 IP: PIM-SM version 1 support
2920 Kernel side support for Sparse Mode PIM (Protocol Independent
2921 Multicast) version 1. This multicast routing protocol is used widely
2922 because Cisco supports it. You need special software to use it
2923 (pimd-v1). Please see http://netweb.usc.edu/pim/ for more
2924 information about PIM.
2926 Say Y if you want to use PIM-SM v1. Note that you can say N here if
2927 you just want to use Dense Mode PIM.
2929 IP: PIM-SM version 2 support
2931 Kernel side support for Sparse Mode PIM version 2. In order to use
2932 this, you need an experimental routing daemon supporting it (pimd or
2933 gated-5). This routing protocol is not used widely, so say N unless
2934 you want to play with it.
2936 PC/TCP compatibility mode
2938 If you have been having difficulties telnetting to your Linux
2939 machine from a DOS system that uses (broken) PC/TCP networking
2940 software (all versions up to OnNet 2.0) over your local Ethernet try
2941 saying Y here. Everyone else says N.
2943 People having problems with NCSA telnet should see the file
2944 linux/Documentation/networking/ncsa-telnet.
2946 Assume subnets are local
2948 Say Y if you are on a subnetted network with all machines connected
2949 by Ethernet segments only, as this option optimizes network access
2950 for this special case. If there are other connections, e.g. SLIP
2951 links, between machines of your IP network, say N. If in doubt,
2952 answer N. The PATH mtu discovery facility will cover most cases
2955 Path MTU Discovery (normally enabled)
2956 CONFIG_PATH_MTU_DISCOVERY
2957 MTU (maximal transfer unit) is the size of the chunks we send out
2958 over the net. "Path MTU Discovery" means that, instead of always
2959 sending very small chunks, we start out sending big ones and if we
2960 then discover that some host along the way likes its chunks smaller,
2961 we adjust to a smaller size. This is good, so most people say Y
2964 However, some DOS software (versions of DOS NCSA telnet and Trumpet
2965 Winsock in PPP mode) is broken and won't be able to connect to your
2966 Linux machine correctly in all cases (especially through a terminal
2967 server) unless you say N here. See
2968 Documentation/networking/ncsa-telnet for the location of fixed NCSA
2969 telnet clients. If in doubt, say Y.
2971 Disable NAGLE algorithm (normally enabled)
2972 CONFIG_TCP_NAGLE_OFF
2973 The NAGLE algorithm works by requiring an acknowledgment before
2974 sending small IP frames (packets). This keeps tiny telnet and
2975 rlogin packets from congesting Wide Area Networks. Most people
2976 strongly recommend to say N here, thereby leaving NAGLE
2977 enabled. Those programs that would benefit from disabling this
2978 facility can do it on a per connection basis themselves.
2980 IP: Allow large windows (not recommended if <16 MB of memory)
2982 On high speed, long distance networks the performance limit on
2983 networking becomes the amount of data the sending machine can buffer
2984 until the other end confirms its reception. (At 45 Mbit/second there
2985 are a lot of bits between New York and London ...). If you say Y
2986 here, bigger buffers can be used which allows larger amounts of data
2987 to be "in flight" at any given time. It also means a user process
2988 can require a lot more memory for network buffers and thus this
2989 option is best used only on machines with 16 MB of memory or higher.
2990 Unless you are using long links with end to end speeds of over 2
2991 Mbit a second or satellite links this option will make no difference
2996 If you say Y here, you will include support for Unix domain sockets;
2997 sockets are the standard Unix mechanism for establishing and
2998 accessing network connections. Many commonly used programs such as
2999 the X Window system and syslog use these sockets even if your
3000 machine is not connected to any network. Unless you are working on
3001 an embedded system or something similar, you therefore definitely
3004 However, the socket support is also available as a module ( = code
3005 which can be inserted in and removed from the running kernel
3006 whenever you want). If you want to compile it as a module, say M
3007 here and read Documentation/modules.txt. The module will be called
3008 unix.o. If you try building this as a module and you have said Y to
3009 "Kernel module loader support" above, be sure to add 'alias net-pf-1
3010 unix' to your /etc/modules.conf file. Note that several important
3011 services won't work correctly if you say M here and then neglect to
3014 Say Y unless you know what you are doing.
3016 The IPv6 protocol (EXPERIMENTAL)
3018 This is experimental support for the next version of the Internet
3019 Protocol: IP version 6 (also called IPng "IP next generation").
3020 Features of this new protocol include: expanded address space,
3021 authentication and privacy, and seamless interoperability with the
3022 current version of IP (IP version 4). For general information about
3023 IPv6, see http://playground.sun.com/pub/ipng/html/ipng-main.html ;
3024 for specific information about IPv6 under Linux read the HOWTO at
3025 http://www.bieringer.de/linux/IPv6/ and the file net/ipv6/README in
3028 If you want to use IPv6, please upgrade to the newest net-tools as
3029 given in Documentation/Changes. You will still be able to do regular
3030 IPv4 networking as well.
3032 This protocol support is also available as a module ( = code which
3033 can be inserted in and removed from the running kernel whenever you
3034 want). The module will be called ipv6.o. If you want to compile it
3035 as a module, say M here and read Documentation/modules.txt.
3037 It is safe to say N here for now.
3039 IPv6: enable EUI-64 token format
3041 6bone, the network of computers using the IPv6 protocol, is moving
3042 to a new aggregatable address format and a new link local address
3043 assignment (EUI-64). Say Y if your site has upgraded already, or
3044 has started to upgrade.
3046 IPv6: disable provider based addresses
3048 Linux tries to operate correctly when your site has moved to EUI-64
3049 only partially. Unfortunately, the two address formats (old:
3050 "provider based" and new: "aggregatable") are incompatible. Say Y if
3051 your site finished the upgrade to EUI-64, and/or you encountered
3052 some problems caused by the presence of two link-local addresses on
3055 IPv6: routing messages via old netlink
3057 You can say Y here to receive routing messages from the IPv6 code
3058 through the old netlink interface. However, a better option is to
3059 say Y to "Kernel/User network link driver" and to "Routing
3064 This is support for the Novell networking protocol, IPX, commonly
3065 used for local networks of Windows machines. You need it if you want
3066 to access Novell NetWare file or print servers using the Linux
3067 Novell client ncpfs (available from
3068 ftp://metalab.unc.edu/pub/Linux/system/filesystems/ ) or from within
3069 the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
3070 http://metalab.unc.edu/mdw/linux.html#howto ). In order to do the
3071 former, you'll also have to say Y to "NCP filesystem support",
3074 IPX is similar in scope to IP, while SPX, which runs on top of IPX,
3075 is similar to TCP. There is also experimental support for SPX in
3076 Linux (see "SPX networking", below).
3078 To turn your Linux box into a fully featured NetWare file server and
3079 IPX router, say Y here and fetch either lwared from
3080 ftp://metalab.unc.edu/pub/Linux/system/network/daemons/ or mars_nwe
3081 from ftp://ftp.gwdg.de/pub/linux/misc/ncpfs . For more information,
3082 read the IPX-HOWTO available from
3083 http://metalab.unc.edu/mdw/linux.html#howto .
3085 General information about how to connect Linux, Windows machines and
3086 Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
3088 The IPX driver would enlarge your kernel by about 16 KB. This driver
3089 is also available as a module ( = code which can be inserted in and
3090 removed from the running kernel whenever you want). The module will
3091 be called ipx.o. If you want to compile it as a module, say M here
3092 and read Documentation/modules.txt. Unless you want to integrate
3093 your Linux box with a local Novell network, say N.
3095 IPX: Full internal IPX network
3097 Every IPX network has an address that identifies it. Sometimes it is
3098 useful to give an IPX "network" address to your Linux box as well
3099 (for example if your box is acting as a file server for different
3100 IPX networks: it will then be accessible from everywhere using the
3101 same address). The way this is done is to create a virtual internal
3102 "network" inside your box and to assign an IPX address to this
3103 network. Say Y here if you want to do this; read the IPX-HOWTO at
3104 http://metalab.unc.edu/mdw/linux.html#howto for details.
3106 The full internal IPX network enables you to allocate sockets on
3107 different virtual nodes of the internal network. This is done by
3108 evaluating the field sipx_node of the socket address given to the
3109 bind call. So applications should always initialize the node field
3110 to 0 when binding a socket on the primary network. In this case the
3111 socket is assigned the default node that has been given to the
3112 kernel when the internal network was created. By enabling the full
3113 internal IPX network the cross-forwarding of packets targeted at
3114 'special' sockets to sockets listening on the primary network is
3115 disabled. This might break existing applications, especially RIP/SAP
3116 daemons. A RIP/SAP daemon that works well with the full internal net
3117 can be found on ftp://ftp.gwdg.de/pub/linux/misc/ncpfs .
3119 If you don't know what you are doing, say N.
3121 IPX: SPX networking (EXPERIMENTAL)
3123 The Sequenced Packet eXchange protocol is a transport layer protocol
3124 built on top of IPX. It is used in Novell NetWare systems for
3125 client-server applications and is similar to TCP (which runs on top
3128 Note that Novell NetWare file sharing does not use SPX; it uses a
3129 protocol called NCP, for which separate Linux support is available
3130 ("NCP filesystem support" below for the client side, and the user
3131 space programs lwared or mars_nwe for the server side).
3133 Say Y here if you have use for SPX; read the IPX-HOWTO at
3134 http://metalab.unc.edu/mdw/linux.html#howto for details.
3136 This driver is also available as a module ( = code which can be
3137 inserted in and removed from the running kernel whenever you want).
3138 The module will be called af_spx.o. If you want to compile it as a
3139 module, say M here and read Documentation/modules.txt.
3141 DECnet networking (EXPERIMENTAL)
3143 The DECnet networking protocol was used in many products made by
3144 Digital (now Compaq). It provides reliable stream and sequenced
3145 packet communications over which run a variety of services similar
3146 to those which run over TCP/IP.
3148 To find some tools to use with the kernel layer support, please
3149 look at Patrick Caulfield's web site:
3150 http://linux.dreamtime.org/decnet/
3152 More detailed documentation is available in the
3153 Documentation/networking/decnet.txt file.
3155 Be sure to say Y to "/proc filesystem support" and "Sysctl support"
3156 below when using DECnet, since you will need sysctl support to aid
3157 in configuration at run time.
3159 The DECnet code is also available as a module ( = code which can be
3160 inserted in and removed from the running kernel whenever you want).
3161 The module is called decnet.o.
3163 DECnet SIOCFIGCONF support
3164 CONFIG_DECNET_SIOCGIFCONF
3165 This option should only be turned on if you are really sure that
3166 you know what you are doing. It can break other applications which
3167 use this system call and the proper way to get the information
3168 provided by this call is to use rtnetlink.
3172 DECnet Router Support (EXPERIMENTAL)
3173 CONFIG_DECNET_ROUTER
3174 Add support for turning your DECnet Endnode into a level 1 or 2
3175 router. This is an unfinished option for developers only. If you do
3176 turn it on, then make sure that you also say Y to "Kernel/User
3177 network link driver" and "Routing messages", since rtnetlink is the
3178 only current method of configuration.
3180 DECnet Raw Socket Support
3182 Add support for the SOCK_RAW type under DECnet. Used by userland
3183 routing programs to receive routing messages from the kernel and
3184 also as a general debugging aid to see what's going on "under the
3189 AppleTalk is the way Apple computers speak to each other on a
3190 network. If your Linux box is connected to such a network and you
3191 want to join the conversation, say Y. You will need to use the
3192 netatalk package so that your Linux box can act as a print and file
3193 server for Macs as well as access AppleTalk printers. Check out
3194 http://threepio.hitchcock.org/cgi-bin/faq/netatalk/faq.pl on the WWW
3195 for details. EtherTalk is the name used for AppleTalk over Ethernet
3196 and the cheaper and slower LocalTalk is AppleTalk over a proprietary
3197 Apple network using serial links. EtherTalk and LocalTalk are fully
3200 General information about how to connect Linux, Windows machines and
3201 Macs is on the WWW at http://www.eats.com/linux_mac_win.html The
3202 NET-3-HOWTO, available from
3203 http://metalab.unc.edu/mdw/linux.html#howto , contains valuable
3204 information as well.
3206 This driver is also available as a module ( = code which can be
3207 inserted in and removed from the running kernel whenever you want).
3208 The module is called appletalk.o. If you want to compile it as a
3209 module, say M here and read Documentation/modules.txt. I hear that
3210 the GNU boycott of Apple is over, so even politically correct people
3211 are allowed to say Y here.
3213 AppleTalk-IP driver support
3215 This allows IP networking for users who only have AppleTalk
3216 networking available. This feature is experimental. With this
3217 driver, you can encapsulate IP inside AppleTalk (e.g. if your Linux
3218 box is stuck on an AppleTalk only network) or decapsulate (e.g. if
3219 you want your Linux box to act as an Internet gateway for a zoo of
3220 AppleTalk connected Macs). Please see the file
3221 Documentation/networking/ipddp.txt for more information.
3223 If you say Y here, the AppleTalk-IP support will be compiled into
3224 the kernel. In this case, you can either use encapsulation or
3225 decapsulation, but not both. With the following two questions, you
3226 decide which one you want.
3228 If you say M here, the AppleTalk-IP support will be compiled as a
3229 module ( = code which can be inserted in and removed from the
3230 running kernel whenever you want, read Documentation/modules.txt).
3231 The module is called ipddp.o. In this case, you will be able to use
3232 both encapsulation and decapsulation simultaneously, by loading two
3233 copies of the module and specifying different values for the module
3236 IP to AppleTalk-IP Encapsulation support
3238 If you say Y here, the AppleTalk-IP code will be able to encapsulate
3239 IP packets inside AppleTalk frames; this is useful if your Linux box
3240 is stuck on an AppleTalk network (which hopefully contains a
3241 decapsulator somewhere). Please see
3242 Documentation/networking/ipddp.txt for more information. If you said
3243 Y to "AppleTalk-IP driver support" above and you say Y here, then
3244 you cannot say Y to "AppleTalk-IP to IP Decapsulation support",
3247 AppleTalk-IP to IP Decapsulation support
3249 If you say Y here, the AppleTalk-IP code will be able to decapsulate
3250 AppleTalk-IP frames to IP packets; this is useful if you want your
3251 Linux box to act as an Internet gateway for an AppleTalk network.
3252 Please see Documentation/networking/ipddp.txt for more information.
3253 If you said Y to "AppleTalk-IP driver support" above and you say Y
3254 here, then you cannot say Y to "IP to AppleTalk-IP Encapsulation
3257 Apple/Farallon LocalTalk PC card support
3259 This allows you to use the AppleTalk PC card to connect to LocalTalk
3260 networks. The card is also known as the Farallon PhoneNet PC card.
3261 If you are in doubt, this card is the one with the 65C02 chip on it.
3262 You also need version 1.3.3 or later of the netatalk package.
3263 This driver is experimental, which means that it may not work.
3264 See the file Documentation/networking/ltpc.txt.
3266 COPS LocalTalk PC card support
3268 This allows you to use COPS AppleTalk cards to connect to LocalTalk
3269 networks. You also need version 1.3.3 or later of the netatalk
3270 package. This driver is experimental, which means that it may not
3271 work. This driver will only work if you choose "AppleTalk DDP"
3272 networking support, above.
3273 Please read the file Documentation/networking/cops.txt.
3275 Dayna firmware support
3277 Support COPS compatible cards with Dayna style firmware (Dayna
3278 DL2000/ Daynatalk/PC (half length), COPS LT-95, Farallon PhoneNET PC
3279 III, Farallon PhoneNET PC II).
3281 Tangent firmware support
3283 Support COPS compatible cards with Tangent style firmware (Tangent
3284 ATB_II, Novell NL-1000, Daystar Digital LT-200.
3286 Amateur Radio support
3288 If you want to connect your Linux box to an amateur radio, answer Y
3289 here. You want to read http://www.tapr.org/tapr/html/pkthome.html
3290 and the HAM-HOWTO and the AX25-HOWTO, both available from
3291 http://metalab.unc.edu/mdw/linux.html#howto .
3293 Note that the answer to this question won't directly affect the
3294 kernel: saying N will just cause this configure script to skip all
3295 the questions about amateur radio.
3297 Amateur Radio AX.25 Level 2
3299 This is the protocol used for computer communication over amateur
3300 radio. It is either used by itself for point-to-point links, or to
3301 carry other protocols such as tcp/ip. To use it, you need a device
3302 that connects your Linux box to your amateur radio. You can either
3303 use a low speed TNC (a Terminal Node Controller acts as a kind of
3304 modem connecting your computer's serial port to your radio's
3305 microphone input and speaker output) supporting the KISS protocol or
3306 one of the various SCC cards that are supported by the generic Z8530
3307 or the DMA SCC driver. Another option are the Baycom modem serial
3308 and parallel port hacks or the sound card modem (supported by their
3309 own drivers). If you say Y here, you also have to say Y to one of
3312 Information about where to get supporting software for Linux amateur
3313 radio as well as information about how to configure an AX.25 port is
3314 contained in the AX25-HOWTO, available from
3315 http://metalab.unc.edu/mdw/linux.html#howto . You might also want to
3316 check out the file Documentation/networking/ax25.txt in the kernel
3317 source. More information about digital amateur radio in general is
3318 on the WWW at http://www.tapr.org/tapr/html/pkthome.html .
3320 This driver is also available as a module ( = code which can be
3321 inserted in and removed from the running kernel whenever you want).
3322 The module will be called ax25.o. If you want to compile it as a
3323 module, say M here and read Documentation/modules.txt.
3325 AX.25 DAMA Slave support
3326 CONFIG_AX25_DAMA_SLAVE
3327 DAMA is a mechanism to prevent collisions when doing AX.25
3328 networking. A DAMA server (called "master") accepts incoming traffic
3329 from clients (called "slaves") and redistributes it to other slaves.
3330 If you say Y here, your Linux box will act as a DAMA slave; this is
3331 transparent in that you don't have to do any special DAMA
3332 configuration. (Linux cannot yet act as a DAMA server.) If unsure,
3335 AX.25 DAMA Master support
3336 CONFIG_AX25_DAMA_MASTER
3337 DAMA is a mechanism to prevent collisions when doing AX.25
3338 networking. A DAMA server (called "master") accepts incoming traffic
3339 from clients (called "slaves") and redistributes it to other
3340 slaves. If you say Y here, your Linux box will act as a DAMA server.
3343 Amateur Radio NET/ROM
3345 NET/ROM is a network layer protocol on top of AX.25 useful for
3348 A comprehensive listing of all the software for Linux amateur radio
3349 users as well as information about how to configure an AX.25 port is
3350 contained in the AX25-HOWTO, available from
3351 http://metalab.unc.edu/mdw/linux.html#howto . You also might want to
3352 check out the file Documentation/networking/ax25.txt. More
3353 information about digital amateur radio in general is on the WWW at
3354 http://www.tapr.org/tapr/html/pkthome.html .
3356 This driver is also available as a module ( = code which can be
3357 inserted in and removed from the running kernel whenever you want).
3358 The module will be called netrom.o. If you want to compile it as a
3359 module, say M here and read Documentation/modules.txt.
3361 Amateur Radio X.25 PLP (Rose)
3363 The Packet Layer Protocol (PLP) is a way to route packets over X.25
3364 connections in general and amateur radio AX.25 connections in
3365 particular, essentially an alternative to NET/ROM.
3367 A comprehensive listing of all the software for Linux amateur radio
3368 users as well as information about how to configure an AX.25 port is
3369 contained in the AX25-HOWTO, available from
3370 http://metalab.unc.edu/mdw/linux.html#howto . You also might want to
3371 check out the file Documentation/networking/ax25.txt. More
3372 information about digital amateur radio in general is on the WWW at
3373 http://www.tapr.org/tapr/html/pkthome.html .
3375 This driver is also available as a module ( = code which can be
3376 inserted in and removed from the running kernel whenever you want).
3377 The module will be called rose.o. If you want to compile it as a
3378 module, say M here and read Documentation/modules.txt.
3380 Serial port KISS driver for AX.25
3382 KISS is a protocol used for the exchange of data between a computer
3383 and a Terminal Node Controller (a small embedded system commonly
3384 used for networking over AX.25 amateur radio connections; it
3385 connects the computer's serial port with the radio's microphone
3386 input and speaker output).
3388 Although KISS is less advanced than the 6pack protocol, it has
3389 the advantage that it is already supported by most modern TNCs
3390 without the need for a firmware upgrade.
3392 If you want to compile this driver as a module ( = code which can be
3393 inserted in and removed from the running kernel whenever you want),
3394 say M here and read Documentation/modules.txt. The module will be
3397 Serial port 6PACK driver for AX.25
3399 6pack is a transmission protocol for the data exchange between your
3400 PC and your TNC (the Terminal Node Controller acts as a kind of
3401 modem connecting your computer's serial port to your radio's
3402 microphone input and speaker output). This protocol can be used as
3403 an alternative to KISS for networking over AX.25 amateur radio
3404 connections, but it has some extended functionality.
3406 Note that this driver is still experimental and might cause
3407 problems. For details about the features and the usage of the
3408 driver, read Documentation/networking/6pack.txt.
3410 If you want to compile this driver as a module ( = code which can be
3411 inserted in and removed from the running kernel whenever you want),
3412 say M here and read Documentation/modules.txt. The module will be
3417 AX.25 is the protocol used for computer communication over amateur
3418 radio. If you say Y here, you will be able to send and receive AX.25
3419 traffic over Ethernet (also called "BPQ AX.25"), which could be
3420 useful if some other computer on your local network has a direct
3421 amateur radio connection.
3423 High-speed (DMA) SCC driver for AX.25
3425 This is a driver for high-speed SCC boards, i.e. those supporting
3426 DMA on one port. You usually use those boards to connect your
3427 computer to an amateur radio modem (such as the WA4DSY 56kbps
3428 modem), in order to send and receive AX.25 packet radio network
3431 Currently, this driver supports Ottawa PI/PI2
3432 (http://hydra.carleton.ca/info/pi2.html ) and Gracilis PackeTwin
3433 (http://www.paccomm.com/gracilis.html ) boards. They are detected
3434 automatically. If you have one of these cards, say Y here and read
3435 the AX25-HOWTO, available from
3436 http://metalab.unc.edu/mdw/linux.html#howto .
3438 This driver can operate multiple boards simultaneously. If you
3439 compile it as a module (by saying M instead of Y), it will be called
3440 dmascc.o. If you don't pass any parameter to the driver, all
3441 possible I/O addresses are probed. This could irritate other devices
3442 that are currently not in use. You may specify the list of addresses
3443 to be probed by "dmascc=addr1,addr2,..." (when compiled into the
3444 kernel image) or "io=addr1,addr2,..." (when loaded as a module). The
3445 network interfaces will be called dmascc0 and dmascc1 for the board
3446 detected first, dmascc2 and dmascc3 for the second one, and so on.
3448 Before you configure each interface with ifconfig, you MUST set
3449 certain parameters, such as channel access timing, clock mode, and
3450 DMA channel. This is accomplished with a small utility program,
3451 dmascc_cfg, available at
3452 http://www.nt.tuwien.ac.at/~kkudielk/Linux/ .
3454 Z8530 SCC driver for AX.25
3456 These cards are used to connect your Linux box to an amateur radio
3457 in order to communicate with other computers. If you want to use
3458 this, read Documentation/networking/z8530drv.txt and the AX25-HOWTO,
3459 available from http://metalab.unc.edu/mdw/linux.html#howto . Also
3460 make sure to say Y to "Amateur Radio AX.25 Level 2" support.
3462 If you want to compile this as a module ( = code which can be
3463 inserted in and removed from the running kernel whenever you want),
3464 say M here and read Documentation/modules.txt. The module will be
3467 additional delay for PA0HZP OptoSCC compatible boards
3469 Say Y here if you experience problems with the SCC driver not
3470 working properly; please read Documentation/networking/z8530drv.txt
3471 for details. If unsure, say N.
3473 #support for TRX that feedback the tx signal to rx
3476 ### Don't know what's going on here.
3480 YAM driver for AX.25
3482 The YAM is a modem for packet radio which connects to the serial
3483 port and includes some of the functions of a Terminal Node
3484 Controller. If you have one of those, say Y here.
3486 If you want to compile this as a module ( = code which can be
3487 inserted in and removed from the running kernel whenever you want),
3488 say M here and read Documentation/modules.txt.
3490 BAYCOM picpar and par96 driver for AX.25
3492 This is a driver for Baycom style simple amateur radio modems that
3493 connect to a parallel interface. The driver supports the picpar and
3494 par96 designs. To configure the driver, use the sethdlc utility
3495 available in the standard ax25 utilities package. For information on
3496 the modems, see http://www.baycom.de and the file
3497 Documentation/networking/baycom.txt.
3499 If you want to compile this driver as a module ( = code which can be
3500 inserted in and removed from the running kernel whenever you want),
3501 say M here and read Documentation/modules.txt. This is recommended.
3502 The module will be called baycom_par.o.
3504 BAYCOM EPP driver for AX.25
3506 This is a driver for Baycom style simple amateur radio modems that
3507 connect to a parallel interface. The driver supports the EPP
3508 designs. To configure the driver, use the sethdlc utility available
3509 in the standard ax25 utilities package. For information on the
3510 modems, see http://www.baycom.de and the file
3511 Documentation/networking/baycom.txt.
3513 If you want to compile this driver as a module ( = code which can be
3514 inserted in and removed from the running kernel whenever you want),
3515 say M here and read Documentation/modules.txt. This is recommended.
3516 The module will be called baycom_par.o.
3518 BAYCOM ser12 full duplex driver for AX.25
3519 CONFIG_BAYCOM_SER_FDX
3520 This is one of two drivers for Baycom style simple amateur radio
3521 modems that connect to a serial interface. The driver supports the
3522 ser12 design in full duplex mode. In addition, it allows the
3523 baudrate to be set between 300 and 4800 baud (however not all modems
3524 support all baudrates). This is the preferred driver. The next
3525 driver, "BAYCOM ser12 half duplex driver for AX.25" is the old
3526 driver and still provided in case this driver does not work with
3527 your serial interface chip. To configure the driver, use the sethdlc
3528 utility available in the standard ax25 utilities package. For
3529 information on the modems, see http://www.baycom.de and
3530 Documentation/networking/baycom.txt.
3532 If you want to compile this driver as a module ( = code which can be
3533 inserted in and removed from the running kernel whenever you want),
3534 say M here and read Documentation/modules.txt. This is recommended.
3535 The module will be called baycom_ser_fdx.o.
3537 BAYCOM ser12 half duplex driver for AX.25
3538 CONFIG_BAYCOM_SER_HDX
3539 This is one of two drivers for Baycom style simple amateur radio
3540 modems that connect to a serial interface. The driver supports the
3541 ser12 design in full duplex mode. This is the old driver. It is
3542 still provided in case your serial interface chip does not work with
3543 the full duplex driver. This driver is depreciated. To configure the
3544 driver, use the sethdlc utility available in the standard ax25
3545 utilities package. For information on the modems, see
3546 http://www.baycom.de and Documentation/networking/baycom.txt.
3548 If you want to compile this driver as a module ( = code which can be
3549 inserted in and removed from the running kernel whenever you want),
3550 say M here and read Documentation/modules.txt. This is recommended.
3551 The module will be called baycom_ser_hdx.o.
3553 Sound card modem driver for AX.25
3555 This experimental driver allows a standard Sound Blaster or
3556 WindowsSoundSystem compatible sound card to be used as a packet
3557 radio modem (NOT as a telephone modem!), to send digital traffic
3560 To configure the driver, use the sethdlc, smdiag and smmixer
3561 utilities available in the standard ax25 utilities package. For
3562 information on how to key the transmitter, see
3563 http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html and
3564 Documentation/networking/soundmodem.txt.
3566 If you want to compile this driver as a module ( = code which can be
3567 inserted in and removed from the running kernel whenever you want),
3568 say M here and read Documentation/modules.txt. This is recommended.
3569 The module will be called soundmodem.o.
3571 Sound card modem support for Sound Blaster and compatible cards
3572 CONFIG_SOUNDMODEM_SBC
3573 This option enables the soundmodem driver to use Sound Blaster and
3574 compatible cards. If you have a dual mode card (i.e. a WSS cards
3575 with a Sound Blaster emulation) you should say N here and Y to
3576 "Sound card modem support for WSS and Crystal cards", below, because
3577 this usually results in better performance. This option also
3578 supports SB16/32/64 in full duplex mode.
3580 Sound card modem support for WSS and Crystal cards
3581 CONFIG_SOUNDMODEM_WSS
3582 This option enables the soundmodem driver to use WindowsSoundSystem
3583 compatible cards. These cards feature a codec chip from either
3584 Analog Devices (such as AD1848, AD1845, AD1812) or Crystal
3585 Semiconductors (such as CS4248, CS423x). This option also supports
3586 the WSS full duplex operation which currently works with Crystal
3587 CS423x chips. If you don't need full duplex operation, do not enable
3588 it to save performance.
3590 Sound card modem support for 1200 baud AFSK modulation
3591 CONFIG_SOUNDMODEM_AFSK1200
3592 This option enables the soundmodem driver 1200 baud AFSK modem,
3593 compatible to popular modems using TCM3105 or AM7911. The
3594 demodulator requires about 12% of the CPU power of a Pentium 75 CPU
3597 Sound card modem support for 2400 baud AFSK modulation (7.3728MHz crystal)
3598 CONFIG_SOUNDMODEM_AFSK2400_7
3599 This option enables the soundmodem driver 2400 baud AFSK modem,
3600 compatible to TCM3105 modems (over-)clocked with a 7.3728MHz
3601 crystal. Note that the availability of this driver does _not_ imply
3602 that I recommend building such links. It is only here since users
3603 especially in eastern Europe have asked me to do so. In fact this
3604 modulation scheme has many disadvantages, mainly its incompatibility
3605 with many transceiver designs and the fact that the TCM3105 (if
3606 used) is operated widely outside its specifications.
3608 Sound card modem support for 2400 baud AFSK modulation (8MHz crystal)
3609 CONFIG_SOUNDMODEM_AFSK2400_8
3610 This option enables the soundmodem driver 2400 baud AFSK modem,
3611 compatible to TCM3105 modems (over-)clocked with an 8MHz crystal.
3612 Note that the availability of this driver does _not_ imply that I
3613 recommend building such links. It is only here since users
3614 especially in eastern Europe have asked me to do so. In fact this
3615 modulation scheme has many disadvantages, mainly its incompatibility
3616 with many transceiver designs and the fact that the TCM3105 (if
3617 used) is operated widely outside its specifications.
3619 Sound card modem support for 2666 baud AFSK modulation
3620 CONFIG_SOUNDMODEM_AFSK2666
3621 This option enables the soundmodem driver 2666 baud AFSK modem.
3622 This modem is experimental, and not compatible to anything
3625 Sound card modem support for 4800 baud 8PSK modulation
3626 CONFIG_SOUNDMODEM_PSK4800
3627 This option enables the soundmodem driver 4800 baud 8PSK modem.
3628 This modem is experimental, and not compatible to anything
3631 Sound card modem support for 4800 baud HAPN-1 modulation
3632 CONFIG_SOUNDMODEM_HAPN4800
3633 This option enables the soundmodem driver 4800 baud HAPN-1
3634 compatible modem. This modulation seems to be widely used 'down
3635 under' and in the Netherlands. Here, nobody uses it, so I could not
3636 test if it works. It is compatible to itself, however :-)
3638 Sound card modem support for 9600 baud FSK G3RUH modulation
3639 CONFIG_SOUNDMODEM_FSK9600
3640 This option enables the soundmodem driver 9600 baud FSK modem,
3641 compatible to the G3RUH standard. The demodulator requires about 4%
3642 of the CPU power of a Pentium 75 CPU per channel. You can say Y to
3643 both 1200 baud AFSK and 9600 baud FSK if you want (but obviously you
3644 can only use one protocol at a time, depending on what the other end
3647 CCITT X.25 Packet Layer (EXPERIMENTAL)
3649 X.25 is a set of standardized network protocols, similar in scope to
3650 frame relay; the one physical line from your box to the X.25 network
3651 entry point can carry several logical point-to-point connections
3652 (called "virtual circuits") to other computers connected to the X.25
3653 network. Governments, banks, and other organizations tend to use it
3654 to connect to each other or to form Wide Area Networks (WANs). Many
3655 countries have public X.25 networks. X.25 consists of two
3656 protocols: the higher level Packet Layer Protocol (PLP) (say Y here
3657 if you want that) and the lower level data link layer protocol LAPB
3658 (say Y to "LAPB Data Link Driver" below if you want that).
3660 You can read more about X.25 at http://www.sangoma.com/x25.htm and
3661 http://www.cisco.com/univercd/data/doc/software/11_0/rpcg/cx25.htm .
3662 Information about X.25 for Linux is contained in the files
3663 Documentation/networking/x25.txt and
3664 Documentation/networking/x25-iface.txt.
3666 One connects to an X.25 network either with a dedicated network card
3667 using the X.21 protocol (not yet supported by Linux) or one can do
3668 X.25 over a standard telephone line using an ordinary modem (say Y
3669 to "X.25 async driver" below) or over Ethernet using an ordinary
3670 Ethernet card and either the 802.2 LLC protocol (say Y to "802.2
3671 LLC" below) or LAPB over Ethernet (say Y to "LAPB Data Link Driver"
3672 and "LAPB over Ethernet driver" below).
3674 If you want to compile this driver as a module ( = code which can be
3675 inserted in and removed from the running kernel whenever you want),
3676 say M here and read Documentation/modules.txt. The module will be
3677 called x25.o. If unsure, say N.
3679 LAPB Data Link Driver (EXPERIMENTAL)
3681 Link Access Procedure, Balanced (LAPB) is the data link layer (i.e.
3682 the lower) part of the X.25 protocol. It offers a reliable
3683 connection service to exchange data frames with one other host, and
3684 it is used to transport higher level protocols (mostly X.25 Packet
3685 Layer, the higher part of X.25, but others are possible as well).
3686 Usually, LAPB is used with specialized X.21 network cards, but Linux
3687 currently supports LAPB only over Ethernet connections. If you want
3688 to use LAPB connections over Ethernet, say Y here and to "LAPB over
3689 Ethernet driver" below. Read
3690 Documentation/networking/lapb-module.txt for technical details.
3692 If you want to compile this driver as a module though ( = code which
3693 can be inserted in and removed from the running kernel whenever you
3694 want), say M here and read Documentation/modules.txt. The module
3695 will be called lapb.o. If unsure, say N.
3697 802.2 LLC (EXPERIMENTAL)
3699 This is a Logical Link Layer protocol used for X.25 connections over
3700 Ethernet, using ordinary Ethernet cards.
3702 Bridging (EXPERIMENTAL)
3704 If you say Y here, then your Linux box will be able to act as an
3705 Ethernet bridge, which means that the different Ethernet segments it
3706 is connected to will appear as one Ethernet to the participants.
3707 Several such bridges can work together to create even larger
3708 networks of Ethernets using the IEEE802.1 spanning tree algorithm.
3709 As this is a standard, Linux bridges will interwork properly with
3710 other third party bridge products.
3712 In order to use this, you'll need the bridge configuration tools
3713 available from ftp://shadow.cabi.net/pub/Linux . Please read the
3714 Bridge mini-HOWTO for more information. Note that if your box acts
3715 as a bridge, it probably contains several Ethernet devices, but the
3716 kernel is not able to recognize more than one at boot time without
3717 help; for details read the Ethernet-HOWTO, available from
3718 http://metalab.unc.edu/mdw/linux.html#howto .
3720 The Bridging code is still in test. If unsure, say N.
3724 The Packet protocol is used by applications which communicate
3725 directly with network devices without an intermediate network
3726 protocol implemented in the kernel, e.g. tcpdump. If you want them
3729 This driver is also available as a module called af_packet.o ( =
3730 code which can be inserted in and removed from the running kernel
3731 whenever you want). If you want to compile it as a module, say M
3732 here and read Documentation/modules.txt; if you use modprobe or
3733 kmod, you may also want to add "alias net-pf-17 af_packet" to
3738 Packet socket: mmapped IO
3740 If you say Y here, the Packet protocol driver will use an IO
3741 mechanism that results in faster communication.
3745 Kernel/User network link driver
3747 This driver allows for two-way communication between the kernel and
3748 user processes; the user processes communicate with the kernel by
3749 reading from and writing to character special files in the /dev
3750 directory having major mode 36.
3752 So far, the kernel uses this feature to publish some network related
3753 information if you say Y to "Routing messages", below. You also need
3754 to say Y here if you want to use arpd, a daemon that helps keep the
3755 internal ARP cache (a mapping between IP addresses and hardware
3756 addresses on the local network) small. The ethertap device, which
3757 lets user space programs read and write raw Ethernet frames, also
3758 needs the network link driver.
3760 This driver is also available as a module called netlink_dev.o ( =
3761 code which can be inserted in and removed from the running kernel
3762 whenever you want). If you want to compile it as a module, say M
3763 here and read Documentation/modules.txt.
3769 If you say Y here and create a character special file /dev/route
3770 with major number 36 and minor number 0 using mknod ("man mknod"),
3771 you (or some user space utility) can read some network related
3772 routing information from that file. Everything you write to that
3773 file will be discarded.
3775 Netlink device emulation
3777 This is a backward compatibility option, choose Y for now.
3778 This option will be removed soon.
3780 Asynchronous Transfer Mode (ATM)
3782 ATM is a high-speed networking technology for Local Area Networks
3783 and Wide Area Networks. It uses a fixed packet size and is
3784 connection oriented, allowing for the negotiation of minimum
3785 bandwidth requirements.
3787 In order to participate in an ATM network, your Linux box needs an
3788 ATM networking card. If you have that, say Y here and to the driver
3789 of your ATM card below.
3791 Note that you need a set of user-space programs to actually make use
3792 of ATM. See the file Documentation/atm.txt for further details.
3794 Classical IP over ATM
3796 Classical IP over ATM for PVCs and SVCs, supporting InARP and
3797 ATMARP. Typically you will either use LAN Emulation (LANE) or
3798 Classical IP to communicate with other IP hosts on your ATM network.
3800 Do NOT send ICMP if no neighbour
3801 CONFIG_ATM_CLIP_NO_ICMP
3802 Normally, an "ICMP host unreachable" message is sent if a neighbour
3803 cannot be reached because there is no VC to it in the kernel's
3804 ATMARP table. This may cause problems when ATMARP table entries are
3805 briefly removed during revalidation. If you say Y here, packets to
3806 such neighbours are silently discarded instead.
3808 LAN Emulation (LANE) support
3810 LAN Emulation emulates services of existing LANs across an ATM
3811 network. Besides operating as a normal ATM end station client, Linux
3812 LANE client can also act as an proxy client bridging packets between
3813 ELAN and Ethernet segments. You need LANE if you want to try MPOA.
3815 Multi-Protocol Over ATM (MPOA) support
3817 Multi-Protocol Over ATM allows ATM edge devices such as routers,
3818 bridges and ATM attached hosts establish direct ATM VCs across
3819 subnetwork boundaries. These shortcut connections bypass routers
3820 enhancing overall network performance.
3824 ATM over TCP driver. Useful mainly for development and for
3825 experiments. If unsure, say N.
3827 Efficient Networks ENI155P
3829 Driver for the Efficient Networks ENI155p series and SMC ATM
3830 Power155 155 Mbps ATM adapters. Both, the versions with 512kB and
3831 2MB on-board RAM (Efficient calls them "C" and "S", respectively),
3832 and the FPGA and the ASIC Tonga versions of the board are supported.
3833 The driver works with MMF (-MF or ...F) and UTP-5 (-U5 or ...D)
3836 Enable extended debugging
3837 CONFIG_ATM_ENI_DEBUG
3838 Extended debugging records various events and displays that list
3839 when an inconsistency is detected. This mechanism is faster than
3840 generally using printks, but still has some impact on performance.
3841 Note that extended debugging may create certain race conditions
3842 itself. Enable this ONLY if you suspect problems with the driver.
3844 Fine-tune burst settings
3845 CONFIG_ATM_ENI_TUNE_BURST
3846 In order to obtain good throughput, the ENI NIC can transfer
3847 multiple words of data per PCI bus access cycle. Such a multi-word
3848 transfer is called a burst.
3850 The default settings for the burst sizes are suitable for most PCI
3851 chipsets. However, in some cases, large bursts may overrun buffers
3852 in the PCI chipset and cause data corruption. In such cases, large
3853 bursts must be disabled and only (slower) small bursts can be used.
3854 The burst sizes can be set independently in the send (TX) and
3855 receive (RX) direction.
3857 Note that enabling many different burst sizes in the same direction
3858 may increase the cost of setting up a transfer such that the
3859 resulting throughput is lower than when using only the largest
3860 available burst size.
3862 Also, sometimes larger bursts lead to lower throughput, e.g. on an
3863 Intel 440FX board, a drop from 135 Mbps to 103 Mbps was observed
3864 when going from 8W to 16W bursts.
3866 Enable 16W TX bursts (discouraged)
3867 CONFIG_ATM_ENI_BURST_TX_16W
3868 Burst sixteen words at once in the send direction. This may work
3869 with recent PCI chipsets, but is known to fail with older chipsets.
3871 Enable 8W TX bursts (recommended)
3872 CONFIG_ATM_ENI_BURST_TX_8W
3873 Burst eight words at once in the send direction. This is the default
3876 Enable 4W TX bursts (optional)
3877 CONFIG_ATM_ENI_BURST_TX_4W
3878 Burst four words at once in the send direction. You may want to try
3879 this if you have disabled 8W bursts. Enabling 4W if 8W is also set
3880 may or may not improve throughput.
3882 Enable 2W TX bursts (optional)
3883 CONFIG_ATM_ENI_BURST_TX_2W
3884 Burst two words at once in the send direction. You may want to try
3885 this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or 8W
3886 are also set may or may not improve throughput.
3888 Enable 16W RX bursts (discouraged)
3889 CONFIG_ATM_ENI_BURST_RX_16W
3890 Burst sixteen words at once in the receive direction. This may work
3891 with recent PCI chipsets, but is known to fail with older chipsets.
3893 Enable 8W RX bursts (discouraged)
3894 CONFIG_ATM_ENI_BURST_RX_8W
3895 Burst eight words at once in the receive direction. This may work
3896 with recent PCI chipsets, but is known to fail with older chipsets,
3897 such as the Intel Neptune series.
3899 Enable 4W RX bursts (recommended)
3900 CONFIG_ATM_ENI_BURST_RX_4W
3901 Burst four words at once in the receive direction. This is the
3902 default setting. Enabling 4W if 8W is also set may or may not
3905 Enable 2W RX bursts (optional)
3906 CONFIG_ATM_ENI_BURST_RX_2W
3907 Burst two words at once in the receive direction. You may want to
3908 try this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or
3909 8W are also set may or may not improve throughput.
3911 ZeitNet ZN1221/ZN1225
3913 Driver for the ZeitNet ZN1221 (MMF) and ZN1225 (UTP-5) 155 Mbps ATM
3916 Enable extended debugging
3917 CONFIG_ATM_ZATM_DEBUG
3918 Extended debugging records various events and displays that list
3919 when an inconsistency is detected. This mechanism is faster than
3920 generally using printks, but still has some impact on performance.
3921 Note that extended debugging may create certain race conditions
3922 itself. Enable this ONLY if you suspect problems with the driver.
3924 Enable usec resolution timestamps
3925 CONFIG_ATM_ZATM_EXACT_TS
3926 The uPD98401 SAR chip supports a high-resolution timer (approx. 30
3927 MHz) that is used for very accurate reception timestamps. Because
3928 that timer overflows after 140 seconds, and also to avoid timer
3929 drift, time measurements need to be periodically synchronized with
3930 the normal system time. Enabling this feature will add some general
3931 overhead for timer synchronization and also per-packet overhead for
3936 The NICStAR chipset family is used in a large number of ATM NICs for
3937 25 and for 155 Mbps, including IDT cards and the Fore ForeRunnerLE
3940 Madge Ambassador (Collage PCI 155 Server)
3941 CONFIG_ATM_AMBASSADOR
3942 This is a driver for ATMizer based ATM card produced by Madge
3943 Networks Ltd. Say Y (or M to compile as a module named ambassador.o)
3944 here if you have one of these cards.
3946 Enable debugging messages
3947 CONFIG_ATM_AMBASSADOR_DEBUG
3948 Somewhat useful debugging messages are available. The choice of
3949 messages is controlled by a bitmap. This may be specified as a
3950 module argument (kernel command line argument as well?), changed
3951 dynamically using an ioctl (not yet) or changed by sending the
3952 string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
3953 drivers/atm/ambassador.h for the meanings of the bits in the mask.
3955 When active, these messages can have a significant impact on the
3956 speed of the driver, and the size of your syslog files! When
3957 inactive, they will have only a modest impact on performance.
3959 Madge Horizon [Ultra] (Collage PCI 25 and Collage PCI 155 Client)
3961 This is a driver for the Horizon chipset ATM adapter cards once
3962 produced by Madge Networks Ltd. Say Y (or M to compile as a module
3963 named horizon.o) here if you have one of these cards.
3965 Enable debugging messages
3966 CONFIG_ATM_HORIZON_DEBUG
3967 Somewhat useful debugging messages are available. The choice of
3968 messages is controlled by a bitmap. This may be specified as a
3969 module argument (kernel command line argument as well?), changed
3970 dynamically using an ioctl (not yet) or changed by sending the
3971 string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
3972 drivers/atm/horizon.h for the meanings of the bits in the mask.
3974 When active, these messages can have a significant impact on the
3975 speed of the driver, and the size of your syslog files! When
3976 inactive, they will have only a modest impact on performance.
3980 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CDROM or
3981 any other SCSI device under Linux, say Y and make sure that you know
3982 the name of your SCSI host adapter (the card inside your computer
3983 that "speaks" the SCSI protocol, also called SCSI controller),
3984 because you will be asked for it.
3986 You also need to say Y here if you want support for the parallel
3987 port version of the 100 MB IOMEGA ZIP drive.
3989 Please read the SCSI-HOWTO, available from
3990 http://metalab.unc.edu/mdw/linux.html#howto . The
3991 SCSI-Programming-HOWTO contains information about how to add or
3992 remove an SCSI device from a running Linux machine without
3995 This driver is also available as a module ( = code which can be
3996 inserted in and removed from the running kernel whenever you want).
3997 The module will be called scsi_mod.o. If you want to compile it as a
3998 module, say M here and read Documentation/modules.txt and
3999 Documentation/scsi.txt. However, do not compile this as a module if
4000 your root filesystem (the one containing the directory /) is located
4005 If you want to use a SCSI hard disk or the SCSI or parallel port
4006 version of the IOMEGA ZIP drive under Linux, say Y and read the
4007 SCSI-HOWTO, the Disk-HOWTO and the Multi-Disk-HOWTO, available from
4008 http://metalab.unc.edu/mdw/linux.html#howto . This is NOT for SCSI
4011 This driver is also available as a module ( = code which can be
4012 inserted in and removed from the running kernel whenever you want).
4013 The module will be called sd_mod.o. If you want to compile it as a
4014 module, say M here and read Documentation/modules.txt and
4015 Documentation/scsi.txt. Do not compile this driver as a module if
4016 your root filesystem (the one containing the directory /) is located
4017 on a SCSI disk. In this case, do not compile the driver for your
4018 SCSI host adapter (below) as a module either.
4022 If you want to use a SCSI tape drive under Linux, say Y and read the
4023 SCSI-HOWTO, available from
4024 http://metalab.unc.edu/mdw/linux.html#howto , and
4025 drivers/scsi/README.st in the kernel source. This is NOT for SCSI
4028 This driver is also available as a module ( = code which can be
4029 inserted in and removed from the running kernel whenever you want).
4030 The module will be called st.o. If you want to compile it as a
4031 module, say M here and read Documentation/modules.txt and
4032 Documentation/scsi.txt .
4036 If you want to use a SCSI CDROM under Linux, say Y and read the
4037 SCSI-HOWTO and the CDROM-HOWTO at
4038 http://metalab.unc.edu/mdw/linux.html#howto . Also make sure to say Y
4039 or M to "ISO 9660 CDROM filesystem support" later.
4041 This driver is also available as a module ( = code which can be
4042 inserted in and removed from the running kernel whenever you want).
4043 The module will be called sr_mod.o. If you want to compile it as a
4044 module, say M here and read Documentation/modules.txt and
4045 Documentation/scsi.txt .
4047 Enable vendor-specific extensions (for SCSI CDROM)
4048 CONFIG_BLK_DEV_SR_VENDOR
4049 This enables the usage of vendor specific SCSI commands. This is
4050 required to support multisession CDs with old NEC/TOSHIBA cdrom
4051 drives (and HP Writers). If you have such a drive and get the first
4052 session only, try saying Y here; everybody else says N.
4054 SCSI generic support
4056 If you want to use SCSI scanners, synthesizers or CD-writers or just
4057 about anything having "SCSI" in its name other than hard disks,
4058 CDROMs or tapes, say Y here. These won't be supported by the kernel
4059 directly, so you need some additional software which knows how to
4060 talk to these devices using the SCSI protocol. For CD-writers, you
4061 would need the program cdwrite, available from
4062 ftp://metalab.unc.edu/pub/Linux/utils/disk-management ; for other
4063 devices, it's possible that you'll have to write the driver software
4064 yourself, so have a look at the SCSI-HOWTO and at the
4065 SCSI-Programming-HOWTO, both available from
4066 http://metalab.unc.edu/mdw/linux.html#howto . Please read the file
4067 Documentation/scsi-generic.txt for more information.
4069 If you want to compile this as a module ( = code which can be
4070 inserted in and removed from the running kernel whenever you want),
4071 say M here and read Documentation/modules.txt and
4072 Documentation/scsi.txt. The module will be called sg.o. If unsure,
4075 Probe all LUNs on each SCSI device
4076 CONFIG_SCSI_MULTI_LUN
4077 If you have a SCSI device that supports more than one LUN (Logical
4078 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
4079 can say Y here to force the SCSI driver to probe for multiple LUNs.
4080 A SCSI device with multiple LUNs acts logically like multiple SCSI
4081 devices. The vast majority of SCSI devices have only one LUN, and
4082 so most people can say N here and should in fact do so, because it
4085 Verbose SCSI error reporting (kernel size +=12K)
4086 CONFIG_SCSI_CONSTANTS
4087 The error messages regarding your SCSI hardware will be easier to
4088 understand if you say Y here; it will enlarge your kernel by about
4089 12 KB. If in doubt, say Y.
4091 SCSI logging facility
4093 This turns on a logging facility that can be used to debug a number
4094 of SCSI related problems.
4096 If you say Y here, no logging output will appear by default, but you
4097 can enable logging by saying Y to "/proc filesystem support" and
4098 "Sysctl support" below and executing the command
4100 echo "scsi log token [level]" > /proc/scsi/scsi
4102 at boot time after the /proc filesystem has been mounted.
4104 There are a number of things that can be used for 'token' (you can
4105 find them in the source: drivers/scsi/scsi.c), and this allows you
4106 to select the types of information you want, and the level allows
4107 you to select the level of verbosity.
4109 If you say N here, it may be harder to track down some types of SCSI
4110 problems. If you say Y here your kernel will be somewhat larger, but
4111 there should be no noticeable performance impact as long as you have
4114 AdvanSys SCSI support
4115 CONFIG_SCSI_ADVANSYS
4116 This is a driver for all SCSI host adapters manufactured by
4117 AdvanSys. It is documented in the kernel source in
4118 drivers/scsi/advansys.c.
4120 This driver is also available as a module ( = code which can be
4121 inserted in and removed from the running kernel whenever you want).
4122 If you want to compile it as a module, say M here and read
4123 Documentation/modules.txt. The module will be called advansys.o.
4125 Adaptec AHA152X/2825 support
4127 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
4128 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
4129 must be manually specified in this case.
4131 It is explained in section 3.3 of the SCSI-HOWTO, available from
4132 http://metalab.unc.edu/mdw/linux.html#howto . You might also want to
4133 read the comments at the top of drivers/scsi/aha152x.c.
4135 This driver is also available as a module ( = code which can be
4136 inserted in and removed from the running kernel whenever you want).
4137 The module will be called aha152x.o. If you want to compile it as a
4138 module, say M here and read Documentation/modules.txt.
4140 Adaptec AHA1542 support
4142 This is support for a SCSI host adapter. It is explained in section
4143 3.4 of the SCSI-HOWTO, available from
4144 http://metalab.unc.edu/mdw/linux.html#howto . Note that Trantor was
4145 purchased by Adaptec, and some former Trantor products are being
4146 sold under the Adaptec name. If it doesn't work out of the box, you
4147 may have to change some settings in drivers/scsi/aha1542.h.
4149 If you want to compile this as a module ( = code which can be
4150 inserted in and removed from the running kernel whenever you want),
4151 say M here and read Documentation/modules.txt. The module will be
4154 Adaptec AHA1740 support
4156 This is support for a SCSI host adapter. It is explained in section
4157 3.5 of the SCSI-HOWTO, available from
4158 http://metalab.unc.edu/mdw/linux.html#howto . If it doesn't work out
4159 of the box, you may have to change some settings in
4160 drivers/scsi/aha1740.h.
4162 This driver is also available as a module ( = code which can be
4163 inserted in and removed from the running kernel whenever you want).
4164 The module will be called aha1740.o. If you want to compile it as a
4165 module, say M here and read Documentation/modules.txt.
4167 Adaptec AIC7xxx chipset SCSI controller support
4169 This is support for the various aic7xxx based Adaptec SCSI
4170 controllers. These include the 274x EISA cards; 284x VLB cards;
4171 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
4172 motherboard based SCSI controllers from Adaptec. It does not support
4173 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
4174 support them. It does not support the 2920 cards from Adaptec that
4175 use the Future Domain SCSI controller chip. For those cards, you
4176 need the "Future Domain 16xx SCSI support" driver.
4178 In general, if the controller is based on an Adaptec SCSI controller
4179 chip from the aic777x series or the aic78xx series, this driver
4180 should work. The only exception is the 7810 which is specifically
4181 not supported (that's the RAID controller chip on the AAA-13x
4184 Note that the AHA2920 SCSI host adapter is *not* supported by this
4185 driver; choose "Future Domain 16xx SCSI support" instead if you have
4188 Information on the configuration options for this controller can be
4189 found by checking the help file for each of the available
4190 configuration options. You should read drivers/scsi/README.aic7xxx
4191 at a minimum before contacting the maintainer with any questions.
4192 The SCSI-HOWTO, available from
4193 http://metalab.unc.edu/mdw/linux.html#howto , can also be of great
4196 If you want to compile this driver as a module ( = code which can be
4197 inserted in and removed from the running kernel whenever you want),
4198 say M here and read Documentation/modules.txt. The module will be
4201 Enable or Disable Tagged Command Queueing by default
4202 CONFIG_AIC7XXX_TCQ_ON_BY_DEFAULT
4203 This option causes the aic7xxx driver to attempt to use Tagged
4204 Command Queueing (TCQ) on all devices that claim to support it.
4206 TCQ is a feature of SCSI-2 which improves performance: the host
4207 adapter can send several SCSI commands to a device's queue even if
4208 previous commands haven't finished yet. Because the device is
4209 intelligent, it can optimize its operations (like head positioning)
4210 based on its own request queue. Not all devices implement this
4213 If you say Y here, you can still turn off TCQ on troublesome devices
4214 with the use of the tag_info boot parameter. See the file
4215 drivers/scsi/README.aic7xxx for more information on that and other
4216 aic7xxx setup commands. If this option is turned off, you may still
4217 enable TCQ on known good devices by use of the tag_info boot
4220 If you are unsure about your devices then it is safest to say N
4223 However, TCQ can increase performance on some hard drives by as much
4224 as 50% or more, so it is recommended that if you say N here, you
4225 should at least read the README.aic7xxx file so you will know how to
4226 enable this option manually should your drives prove to be safe in
4229 Conversely, certain drives are known to lock up or cause bus resets
4230 when TCQ is enabled on them. If you have a Western Digital
4231 Enterprise SCSI drive for instance, then don't even bother to enable
4232 TCQ on it as the drive will become unreliable, and it will actually
4235 Default number of TCQ commands per device
4236 CONFIG_AIC7XXX_CMDS_PER_DEVICE
4237 Specify the number of commands you would like to allocate per SCSI
4238 device when Tagged Command Queueing (TCQ) is enabled on that device.
4240 Reasonable figures are in the range of 8 to 24 commands per device,
4241 but depending on hardware could be increased or decreased from that
4242 figure. If the number is too high for any particular device, the
4243 driver will automatically compensate usually after only 10 minutes
4244 of uptime. It will not hinder performance if some of your devices
4245 eventually have their command depth reduced, but is a waste of
4246 memory if all of your devices end up reducing this number down to a
4247 more reasonable figure.
4249 NOTE: Certain very broken drives are known to lock up when given
4250 more commands than they like to deal with. Quantum Fireball drives
4251 are the most common in this category. For the Quantum Fireball
4252 drives it is suggested to use no more than 8 commands per device.
4256 Collect statistics to report in /proc
4257 CONFIG_AIC7XXX_PROC_STATS
4258 This option tells the driver to keep track of how many commands have
4259 been sent to each particular device and report that information to
4260 the user via the /proc/scsi/aic7xxx/n file, where n is the number of
4261 the aic7xxx controller you want the information on. This adds a
4262 small amount of overhead to each and every SCSI command the aic7xxx
4263 driver handles, so if you aren't really interested in this
4264 information, it is best to leave it disabled. This will only work if
4265 you also say Y to "/proc filesystem support", below.
4269 Delay in seconds after SCSI bus reset
4270 CONFIG_AIC7XXX_RESET_DELAY
4271 This sets how long the driver will wait after resetting the SCSI bus
4272 before attempting to communicate with the devices on the SCSI bus
4273 again. This delay will be used during the reset phase at bootup time
4274 as well as after any reset that might occur during normal operation.
4275 Reasonable numbers range anywhere from 5 to 15 seconds depending on
4276 your devices. DAT tape drives are notorious for needing more time
4277 after a bus reset to be ready for the next command, but most hard
4278 drives and CD-ROM devices are ready in only a few seconds. This
4279 option has a maximum upper limit of 20 seconds to avoid bad
4280 interactions between the aic7xxx driver and the rest of the linux
4281 kernel. The default value has been reduced to 5 seconds. If this
4282 doesn't work with your hardware, try increasing this value.
4284 IBM ServeRAID Support
4286 This is support for the IBM ServeRAID hardware RAID controllers.
4287 Consult the SCSI-HOWTO, available via anonymous FTP from
4288 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO, and the file
4289 README.ips in drivers/scsi for more information. If this driver
4290 does not work correctly without modification please contact the
4291 author by email at ipslinux@us.ibm.com.
4293 IBM ServeRAID Support
4295 This is support for the IBM ServeRAID hardware RAID controllers.
4296 Consult the SCSI-HOWTO, available via anonymous FTP from
4297 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO, and the file
4298 README.ips in drivers/scsi for more information. If this driver
4299 does not work correctly without modification please contact the
4300 author by email at ipslinux@us.ibm.com.
4302 BusLogic SCSI support
4303 CONFIG_SCSI_BUSLOGIC
4304 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
4305 Adapters. Consult the SCSI-HOWTO, available from
4306 http://metalab.unc.edu/mdw/linux.html#howto , and the files
4307 README.BusLogic and README.FlashPoint in drivers/scsi for more
4308 information. If this driver does not work correctly without
4309 modification, please contact the author, Leonard N. Zubkoff, by
4310 email to lnz@dandelion.com.
4312 You can also build this driver as a module ( = code which can be
4313 inserted in and removed from the running kernel whenever you want),
4314 but only a single instance may be loaded. If you want to compile it
4315 as a module, say M here and read Documentation/modules.txt. The
4316 module will be called BusLogic.o.
4318 Omit BusLogic SCSI FlashPoint support
4319 CONFIG_SCSI_OMIT_FLASHPOINT
4320 This option allows you to omit the FlashPoint support from the
4321 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
4322 substantial, so users of MultiMaster Host Adapters may wish to omit
4325 DTC3180/3280 SCSI support
4327 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
4328 the SCSI-HOWTO, available from
4329 http://metalab.unc.edu/mdw/linux.html#howto , and the file
4330 drivers/scsi/README.dtc3x80.
4332 This driver is also available as a module ( = code which can be
4333 inserted in and removed from the running kernel whenever you want).
4334 The module will be called dtc.o. If you want to compile it as a
4335 module, say M here and read Documentation/modules.txt.
4337 EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti, Alphatronix) support
4338 CONFIG_SCSI_EATA_DMA
4339 This is support for the EATA-DMA protocol compliant SCSI Host
4340 Adapters like the SmartCache III/IV, SmartRAID controller families
4341 and the DPT PM2011B and PM2012B controllers.
4343 Note that this driver is obsolete; if you have one of the above SCSI
4344 Host Adapters, you should normally say N here and Y to "EATA
4345 ISA/EISA/PCI support", below. Please read the SCSI-HOWTO, available
4346 from http://metalab.unc.edu/mdw/linux.html#howto .
4348 This driver is also available as a module ( = code which can be
4349 inserted in and removed from the running kernel whenever you want).
4350 The module will be called eata_dma.o. If you want to compile it as a
4351 module, say M here and read Documentation/modules.txt.
4353 EATA-PIO (old DPT PM2001, PM2012A) support
4354 CONFIG_SCSI_EATA_PIO
4355 This driver supports all EATA-PIO protocol compliant SCSI Host
4356 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
4357 host adapters could also use this driver but are discouraged from
4358 doing so, since this driver only supports hard disks and lacks
4359 numerous features. You might want to have a look at the SCSI-HOWTO,
4360 available from http://metalab.unc.edu/mdw/linux.html#howto .
4362 If you want to compile this as a module ( = code which can be
4363 inserted in and removed from the running kernel whenever you want),
4364 say M here and read Documentation/modules.txt. The module will be
4367 UltraStor 14F/34F support
4369 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
4370 The source at drivers/scsi/u14-34f.c contains some information about
4371 this hardware. If the driver doesn't work out of the box, you may
4372 have to change some settings in drivers/scsi/u14-34f.c. Read the
4373 SCSI-HOWTO, available from
4374 http://metalab.unc.edu/mdw/linux.html#howto . Note that there is also
4375 another driver for the same hardware: "UltraStor SCSI support",
4376 below. You should say Y to both only if you want 24F support as
4379 This driver is also available as a module ( = code which can be
4380 inserted in and removed from the running kernel whenever you want).
4381 The module will be called u14-34f.o. If you want to compile it as a
4382 module, say M here and read Documentation/modules.txt.
4384 enable elevator sorting
4385 CONFIG_SCSI_U14_34F_LINKED_COMMANDS
4386 This option enables elevator sorting for all probed SCSI disks and
4387 CDROMs. It definitely reduces the average seek distance when doing
4388 random seeks, but this does not necessarily result in a noticeable
4389 performance improvement: your mileage may vary...
4391 The safe answer is N.
4393 maximum number of queued commands
4394 CONFIG_SCSI_U14_34F_MAX_TAGS
4395 This specifies how many SCSI commands can be maximally queued for
4396 each probed SCSI device. You should reduce the default value of 8
4397 only if you have disks with buggy or limited tagged command support.
4398 Minimum is 2 and maximum is 14. This value is also the window size
4399 used by the elevator sorting option above. The effective value used
4400 by the driver for each probed SCSI device is reported at boot time.
4402 Future Domain 16xx SCSI/AHA-2920A support
4403 CONFIG_SCSI_FUTURE_DOMAIN
4404 This is support for Future Domain's 16-bit SCSI host adapters
4405 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
4406 other adapters based on the Future Domain chipsets (Quantum
4407 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
4408 It is explained in section 3.7 of the SCSI-HOWTO, available from
4409 http://metalab.unc.edu/mdw/linux.html#howto .
4411 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
4412 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
4413 controller support"). This Future Domain driver works with the older
4414 Adaptec AHA-2920A boards with a Future Domain chip on them.
4416 This driver is also available as a module ( = code which can be
4417 inserted in and removed from the running kernel whenever you want).
4418 The module will be called fdomain.o. If you want to compile it as a
4419 module, say M here and read Documentation/modules.txt.
4421 Future Domain MCS-600/700 SCSI support
4423 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
4424 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
4425 is identical to the MCS 700 and hence also supported by this driver.
4426 This driver also supports the Reply SB16/SCSI card (the SCSI part).
4427 It supports multiple adapters in the same system.
4429 This driver is also available as a module ( = code which can be
4430 inserted in and removed from the running kernel whenever you want).
4431 The module will be called fd_mcs.o. If you want to compile it as a
4432 module, say M here and read Documentation/modules.txt.
4434 Generic NCR5380/53c400 SCSI support
4435 CONFIG_SCSI_GENERIC_NCR5380
4436 This is the generic NCR family of SCSI controllers, not to be
4437 confused with the NCR 53c7 or 8xx controllers. It is explained in
4438 section 3.8 of the SCSI-HOWTO, available from
4439 http://metalab.unc.edu/mdw/linux.html#howto . If it doesn't work out
4440 of the box, you may have to change some settings in
4441 drivers/scsi/g_NCR5380.h.
4443 This driver is also available as a module ( = code which can be
4444 inserted in and removed from the running kernel whenever you want).
4445 The module will be called g_NCR5380.o. If you want to compile it as
4446 a module, say M here and read Documentation/modules.txt.
4448 Enable NCR53c400 extensions
4449 CONFIG_SCSI_GENERIC_NCR53C400
4450 This enables certain optimizations for the NCR53c400 SCSI cards. You
4451 might as well try it out. Note that this driver will only probe for
4452 the Trantor T130B in its default configuration; you might have to
4453 pass a command line option to the kernel at boot time if it doesn't
4454 detect your card. See the file drivers/scsi/README.g_NCR5380 for
4457 NCR5380/53c400 mapping method (use Port for T130B)
4458 CONFIG_SCSI_G_NCR5380_PORT
4459 The NCR5380 and NCR53c400 SCSI controllers come in two varieties:
4460 port or memory mapped. You should know what you have. The most
4461 common card, Trantor T130B, uses port mapped mode.
4463 NCR53c7,8xx SCSI support
4464 CONFIG_SCSI_NCR53C7xx
4465 This is a driver for the 53c7 and 8xx NCR family of SCSI
4466 controllers, not to be confused with the NCR 5380 controllers. It is
4467 explained in section 3.8 of the SCSI-HOWTO, available from
4468 http://metalab.unc.edu/mdw/linux.html#howto . If it doesn't work out
4469 of the box, you may have to change some settings in
4470 drivers/scsi/53c7,8xx.h. Please read drivers/scsi/README.ncr53c7xx
4471 for the available boot time command line options.
4473 Note: there is another driver for the 53c8xx family of controllers
4474 ("NCR53C8XX SCSI support" below). If you want to use them both, you
4475 need to say M to both and build them as modules, but only one may be
4476 active at a time. If you have a 53c8xx board, it's better to use the
4479 This driver is also available as a module ( = code which can be
4480 inserted in and removed from the running kernel whenever you want).
4481 The module will be called 53c7,8xx.o. If you want to compile it as a
4482 module, say M here and read Documentation/modules.txt.
4484 always negotiate synchronous transfers
4485 CONFIG_SCSI_NCR53C7xx_sync
4486 In general, this is good; however, it is a bit dangerous since there
4487 are some broken SCSI devices out there. Take your chances. Safe bet
4490 allow FAST-SCSI [10MHz]
4491 CONFIG_SCSI_NCR53C7xx_FAST
4492 This will enable 10MHz FAST-SCSI transfers with your host
4493 adapter. Some systems have problems with that speed, so it's safest
4497 CONFIG_SCSI_NCR53C7xx_DISCONNECT
4498 This enables the disconnect/reconnect feature of the NCR SCSI
4499 controller. When you say Y here, a slow SCSI device will not lock
4500 the SCSI bus while processing a request, allowing simultaneous use
4501 of e.g. a SCSI hard disk and SCSI tape or CD-ROM drive, and
4502 providing much better performance when using slow and fast SCSI
4503 devices at the same time. Some devices, however, do not operate
4504 properly with this option enabled, and will cause your SCSI system
4505 to hang, which might cause a system crash. The safe answer
4506 therefore is to say N.
4508 NCR53C8XX SCSI support
4509 CONFIG_SCSI_NCR53C8XX
4510 This is the BSD ncr driver adapted to Linux for the NCR53C8XX family
4511 of PCI-SCSI controllers. This driver supports parity checking,
4512 tagged command queuing and fast synchronous data transfers up to 80
4513 MB/s with wide FAST-40 LVD devices and controllers.
4515 Recent versions of the 53C8XX chips are better supported by the
4516 option "SYM53C8XX SCSI support", below.
4518 Note: there is yet another driver for the 53c8xx family of
4519 controllers ("NCR53c7,8xx SCSI support" above). If you want to use
4520 them both, you need to say M to both and build them as modules, but
4521 only one may be active at a time. If you have a 53c8xx board, you
4522 probably do not want to use the "NCR53c7,8xx SCSI support".
4524 Please read drivers/scsi/README.ncr53c8xx for more information.
4526 SYM53C8XX SCSI support
4527 CONFIG_SCSI_SYM53C8XX
4528 This driver supports all the features of recent 53C8XX chips (used
4529 in PCI SCSI controllers), notably the hardware phase mismatch
4530 feature of the SYM53C896.
4532 Older versions of the 53C8XX chips are not supported by this
4533 driver. If your system uses either a 810 rev. < 16, a 815, or a 825
4534 rev. < 16 PCI SCSI processor, you must use the generic NCR53C8XX
4535 driver ("NCR53C8XX SCSI support" above) or configure both the
4536 NCR53C8XX and this SYM53C8XX drivers either as module or linked to
4539 When both drivers are linked into the kernel, the SYM53C8XX driver
4540 is called first at initialization and you can use the 'excl=ioaddr'
4541 driver boot option to exclude attachment of adapters by the
4542 SYM53C8XX driver. For example, entering
4543 'sym53c8xx=excl:0xb400,excl=0xc000' at the lilo prompt prevents
4544 adapters at io address 0xb400 and 0xc000 from being attached by the
4545 SYM53C8XX driver, thus allowing the NCR53C8XX driver to attach them.
4546 The 'excl' option is also supported by the NCR53C8XX driver.
4548 Please read drivers/scsi/README.ncr53c8xx for more information.
4550 synchronous data transfers frequency
4551 CONFIG_SCSI_NCR53C8XX_SYNC
4552 The SCSI Parallel Interface-2 Standard defines 4 classes of transfer
4553 rates: FAST-5, FAST-10, FAST-20 and FAST-40. The numbers are
4554 respectively the maximum data transfer rates in mega-transfers per
4555 second for each class. For example, a FAST-20 Wide 16 device is able
4556 to transfer data at 20 million 16 bit packets per second for a total
4559 You may specify 0 if you want to only use asynchronous data
4560 transfers. This is the safest and slowest option. Otherwise, specify
4561 a value between 5 and 40, depending on the capability of your SCSI
4562 controller. The higher the number, the faster the data transfer.
4563 Note that 40 should normally be ok since the driver decreases the
4564 value automatically according to the controller's capabilities.
4566 Your answer to this question is ignored for controllers with NVRAM,
4567 since the driver will get this information from the user set-up. It
4568 also can be overridden using a boot setup option, as follows
4569 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
4570 for FAST-20 synchronous data transfer (20 mega-transfers per
4573 The normal answer therefore is not to go with the default but to
4574 select the maximum value 40 allowing the driver to use the maximum
4575 value supported by each controller. If this causes problems with
4576 your SCSI devices, you should come back and decrease the value.
4578 There is no safe option other than using good cabling, right
4579 terminations and SCSI conformant devices.
4582 CONFIG_SCSI_NCR53C8XX_IOMAPPED
4583 If you say Y here, the driver will use normal IO, as opposed to
4584 memory mapped IO. Memory mapped IO has less latency than normal IO
4585 and works for most Intel-based hardware. Under Linux/Alpha only
4586 normal IO is currently supported by the driver and so, this option
4587 has no effect on those systems.
4589 The normal answer therefore is N; try Y only if you encounter SCSI
4592 not allow targets to disconnect
4593 CONFIG_SCSI_NCR53C8XX_NO_DISCONNECT
4594 This option is only provided for safety if you suspect some SCSI
4595 device of yours to not support properly the target-disconnect
4596 feature. In that case, you would say Y here. In general however, to
4597 not allow targets to disconnect is not reasonable if there is more
4598 than 1 device on a SCSI bus. The normal answer therefore is N.
4600 default tagged command queue depth
4601 CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS
4602 "Tagged command queuing" is a feature of SCSI-2 which improves
4603 performance: the host adapter can send several SCSI commands to a
4604 device's queue even if previous commands haven't finished yet.
4605 Because the device is intelligent, it can optimize its operations
4606 (like head positioning) based on its own request queue. Some SCSI
4607 devices don't implement this properly; if you want to disable this
4608 feature, enter 0 or 1 here (it doesn't matter which).
4610 The default value is 8 and should be supported by most hard disks.
4611 This value can be overridden from the boot command line using the
4612 'tags' option as follows (example):
4613 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
4614 4, set queue depth to 16 for target 2 and target 3 on controller 0
4615 and set queue depth to 10 for target 0 / lun 2 on controller 1.
4617 The normal answer therefore is to go with the default 8 and to use
4618 a boot command line option for devices that need to use a different
4619 command queue depth.
4621 There is no safe option other than using good SCSI devices.
4623 maximum number of queued commands
4624 CONFIG_SCSI_NCR53C8XX_MAX_TAGS
4625 This option allows you to specify the maximum number of commands
4626 that can be queued to any device, when tagged command queuing is
4627 possible. The default value is 32. Minimum is 2, maximum is 64.
4628 Modern hard disks are able to support 64 tags and even more, but
4629 do not seem to be faster when more than 32 tags are being used.
4631 So, the normal answer here is to go with the default value 32 unless
4632 you are using very large hard disks with large cache (>= 1 MB) that
4633 are able to take advantage of more than 32 tagged commands.
4635 There is no safe option and the default answer is recommended.
4637 assume boards are SYMBIOS compatible (EXPERIMENTAL)
4638 CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT
4639 This option allows you to enable some features depending on GPIO
4640 wiring. These General Purpose Input/Output pins can be used for
4641 vendor specific features or implementation of the standard SYMBIOS
4642 features. Genuine SYMBIOS controllers use GPIO0 in output for
4643 controller LED and GPIO3 bit as a flag indicating
4644 singled-ended/differential interface. The Tekram DC-390U/F boards
4645 uses a different GPIO wiring.
4647 Your answer to this question is ignored if all your controllers have
4648 NVRAM, since the driver is able to detect the board type from the
4651 If all the controllers in your system are genuine SYMBIOS boards or
4652 use BIOS and drivers from SYMBIOS, you would want to say Y here,
4653 otherwise N. N is the safe answer.
4655 enable profiling statistics gathering
4656 CONFIG_SCSI_NCR53C8XX_PROFILE
4657 This option allows you to enable profiling information gathering.
4658 These statistics are not very accurate due to the low frequency
4659 of the kernel clock (100 Hz on i386) and have performance impact
4660 on systems that use very fast devices.
4662 The normal answer therefore is N.
4664 include support for the NCR PQS/PDS SCSI card
4665 CONFIG_SCSI_NCR53C8XX_PQS_PDS
4666 Say Y here if you have a special SCSI adapter produced by NCR
4667 corporation called a PCI Quad SCSI or PCI Dual SCSI. You do not need
4668 this if you do not have one of these adapters. However, since this
4669 device is detected as a specific PCI device, this option is quite
4672 The common answer here is N, but answering Y is safe.
4676 This is support for the IBM SCSI adapter found in many of the PS/2
4677 series computers. These machines have an MCA bus, so you need to
4678 answer Y to "MCA support" as well and read Documentation/mca.txt.
4680 If the adapter isn't found during boot (a common problem for models
4681 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
4682 option, where <pun> is the id of the SCSI subsystem (usually 7, but
4683 if that doesn't work check your reference diskette). Owners of model
4684 95 with a LED-matrix-display can in addition activate some activity
4685 info like under OS/2, but more informative, by setting
4686 'ibmmcascsi=display' as an additional kernel parameter. Try "man
4687 bootparam" or see the documentation of your boot loader about how to
4688 pass options to the kernel. The lilo procedure is also explained in
4689 the SCSI-HOWTO, available from
4690 http://metalab.unc.edu/mdw/linux.html#howto .
4692 If you want to compile this driver as a module ( = code which can be
4693 inserted in and removed from the running kernel whenever you want),
4694 say M here and read Documentation/modules.txt. The module will be
4698 CONFIG_IBMMCA_SCSI_ORDER_STANDARD
4699 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
4700 are assigned to the drive letters, starting with the lowest SCSI-id
4701 (physical number -- pun) to be drive C:, as seen from DOS and
4702 similar operating systems. When looking into papers describing the
4703 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
4704 The SCSI-standard follows a hardware-hierarchy which says that id 7
4705 has the highest priority and id 0 the lowest. Therefore, the host
4706 adapters are still today everywhere placed as SCSI-id 7 by default.
4707 In the SCSI-standard, the drive letters express the priority of the
4708 disk. C: should be the hard disk, or a partition on it, with the
4709 highest priority. This must therefore be the disk with the highest
4710 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
4711 original definition of the SCSI-standard as also industrial- and
4712 process-control-machines, like VME-CPUs running under realtime-OSs
4713 (e.g. LynxOS, OS9) do.
4715 If you like to run Linux on your MCA-machine with the same
4716 assignment of hard disks as seen from e.g. DOS or OS/2 on your
4717 machine, which is in addition conformant to the SCSI-standard, you
4718 must say Y here. This is also necessary for MCA-Linux users who want
4719 to keep downward compatibility to older releases of the
4720 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
4723 If you like to have the lowest SCSI-id assigned as drive C:, as
4724 modern SCSI-BIOSes do, which does not conform to the standard, but
4725 is widespread and common in the PC-world of today, you must say N
4726 here. If unsure, say Y.
4728 Reset SCSI-devices at boot time
4729 CONFIG_IBMMCA_SCSI_DEV_RESET
4730 By default, SCSI-devices are reset when the machine is powered on.
4731 However, some devices exist, like special-control-devices,
4732 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
4733 not reset when switched on. If you say Y here, each device connected
4734 to your SCSI-bus will be issued a reset-command after it has been
4735 probed, while the kernel is booting. This may cause problems with
4736 more modern devices, like hard disks, which do not appreciate these
4737 reset commands, and can cause your system to hang. So say Y only if
4738 you know that one of your older devices needs it; N is the safe
4741 NCR 53C9x MCA support
4742 CONFIG_SCSI_MCA_53C9X
4743 Some Microchannel machines, notably the NCR 35xx line, use a SCSI
4744 controller based on the NCR 53C94. This driver will allow use of
4745 the controller on the 3550, and very possibly others.
4747 If you want to compile this as a module (= code which can be
4748 inserted and removed from the running kernel whenever you want), say
4749 M here and read Documentation/modules.txt. The module will be called
4752 Always IN2000 SCSI support
4754 This is support for an ISA bus SCSI host adapter. You'll find more
4755 information in drivers/scsi/in2000.readme. If it doesn't work out of
4756 the box, you may have to change the jumpers for IRQ or address
4759 If you want to compile this as a module ( = code which can be
4760 inserted in and removed from the running kernel whenever you want),
4761 say M here and read Documentation/modules.txt. The module will be
4764 Initio 91XXU(W) SCSI support
4766 This is support for the Initio 91XXU(W) SCSI host adapter. Please
4767 read the SCSI-HOWTO, available from
4768 http://metalab.unc.edu/mdw/linux.html#howto .
4770 If you want to compile this as a module ( = code which can be
4771 inserted in and removed from the running kernel whenever you want),
4772 say M here and read Documentation/modules.txt. The module will be
4777 This is support for a SCSI host adapter. It is explained in section
4778 3.10 of the SCSI-HOWTO, available from
4779 http://metalab.unc.edu/mdw/linux.html#howto . If it doesn't work out
4780 of the box, you may have to change some settings in
4781 drivers/scsi/pas16.h.
4783 This driver is also available as a module ( = code which can be
4784 inserted in and removed from the running kernel whenever you want).
4785 The module will be called pas16.o. If you want to compile it as a
4786 module, say M here and read Documentation/modules.txt.
4788 Initio INI-A100U2W SCSI support
4790 This is support for the Initio INI-A100U2W SCSI host adapter. Please
4791 read the SCSI-HOWTO, available from
4792 http://metalab.unc.edu/mdw/linux.html#howto .
4794 If you want to compile this 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
4801 This is support for the PCI2000I EIDE interface card which acts as a
4802 SCSI host adapter. Please read the SCSI-HOWTO, available from
4803 http://metalab.unc.edu/mdw/linux.html#howto .
4805 This driver is also available as a module called pci2000.o ( = code
4806 which can be inserted in and removed from the running kernel
4807 whenever you want). If you want to compile it as a module, say M
4808 here and read Documentation/modules.txt.
4811 CONFIG_SCSI_PCI2220I
4812 This is support for the PCI2220i EIDE interface card which acts as a
4813 SCSI host adapter. Please read the SCSI-HOWTO, available from
4814 http://metalab.unc.edu/mdw/linux.html#howto .
4816 This driver is also available as a module called pci2220i.o ( = code
4817 which can be inserted in and removed from the running kernel
4818 whenever you want). If you want to compile it as a module, say M
4819 here and read Documentation/modules.txt.
4823 This is support for the PSI240i EIDE interface card which acts as a
4824 SCSI host adapter. Please read the SCSI-HOWTO, available from
4825 http://metalab.unc.edu/mdw/linux.html#howto .
4827 This driver is also available as a module called psi240i.o ( = code
4828 which can be inserted in and removed from the running kernel
4829 whenever you want). If you want to compile it as a module, say M
4830 here and read Documentation/modules.txt.
4832 Qlogic FAS SCSI support
4833 CONFIG_SCSI_QLOGIC_FAS
4834 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
4835 FastSCSI! cards as well as any other card based on the FASXX chip
4836 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
4838 This driver does NOT support the PCI versions of these cards. The
4839 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
4840 SCSI support"), below.
4842 Information about this driver is contained in
4843 drivers/scsi/README.qlogicfas. You should also read the SCSI-HOWTO,
4844 available from http://metalab.unc.edu/mdw/linux.html#howto .
4846 This driver is also available as a module ( = code which can be
4847 inserted in and removed from the running kernel whenever you want).
4848 The module will be called qlogicfas.o. If you want to compile it as
4849 a module, say M here and read Documentation/modules.txt.
4851 Qlogic ISP SCSI support (EXPERIMENTAL)
4852 CONFIG_SCSI_QLOGIC_ISP
4853 This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
4854 IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
4855 card is supported by the "AM53/79C974 PCI SCSI" driver).
4857 If you say Y here, make sure to choose "BIOS" at the question "PCI
4860 Please read the file drivers/scsi/README.qlogicisp. You should also
4861 read the SCSI-HOWTO, available from
4862 http://metalab.unc.edu/mdw/linux.html#howto .
4864 This driver is also available as a module ( = code which can be
4865 inserted in and removed from the running kernel whenever you want).
4866 The module will be called qlogicisp.o. If you want to compile it as
4867 a module, say M here and read Documentation/modules.txt.
4869 Qlogic ISP FC SCSI support
4870 CONFIG_SCSI_QLOGIC_FC
4871 This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
4873 This driver is also available as a module ( = code which can be
4874 inserted in and removed from the running kernel whenever you want).
4875 The module will be called qlogicfc.o. If you want to compile it as
4876 a module, say M here and read Documentation/modules.txt.
4878 Seagate ST-02 and Future Domain TMC-8xx SCSI support
4880 These are 8-bit SCSI controllers; the ST-01 is also supported by
4881 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
4882 available from http://metalab.unc.edu/mdw/linux.html#howto . If it
4883 doesn't work out of the box, you may have to change some settings in
4884 drivers/scsi/seagate.h.
4886 This driver is also available as a module ( = code which can be
4887 inserted in and removed from the running kernel whenever you want).
4888 The module will be called seagate.o. If you want to compile it as a
4889 module, say M here and read Documentation/modules.txt.
4891 Trantor T128/T128F/T228 SCSI support
4893 This is support for a SCSI host adapter. It is explained in section
4894 3.11 of the SCSI-HOWTO, available from
4895 http://metalab.unc.edu/mdw/linux.html#howto . If it doesn't work out
4896 of the box, you may have to change some settings in
4897 drivers/scsi/t128.h. Note that Trantor was purchased by Adaptec, and
4898 some former Trantor products are being sold under the Adaptec name.
4900 This driver is also available as a module ( = code which can be
4901 inserted in and removed from the running kernel whenever you want).
4902 The module will be called t128.o. If you want to compile it as a
4903 module, say M here and read Documentation/modules.txt.
4905 UltraStor SCSI support
4906 CONFIG_SCSI_ULTRASTOR
4907 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
4908 adapter family. This driver is explained in section 3.12 of the
4909 SCSI-HOWTO, available from
4910 http://metalab.unc.edu/mdw/linux.html#howto . If it doesn't work out
4911 of the box, you may have to change some settings in
4912 drivers/scsi/ultrastor.h.
4914 Note that there is also another driver for the same hardware:
4915 "UltraStor 14F/34F support", above.
4917 If you want to compile this as a module ( = code which can be
4918 inserted in and removed from the running kernel whenever you want),
4919 say M here and read Documentation/modules.txt. The module will be
4922 7000FASST SCSI support
4923 CONFIG_SCSI_7000FASST
4924 This driver supports the Western Digital 7000 SCSI host adapter
4925 family. Some information is in the source: drivers/scsi/wd7000.c.
4927 This driver is also available as a module ( = code which can be
4928 inserted in and removed from the running kernel whenever you
4929 want). The module will be called wd7000.o. If you want to compile it
4930 as a module, say M here and read Documentation/modules.txt.
4934 This driver supports the ACARD 870U/W SCSI host adapter.
4936 This driver is also available as a module ( = code which can be
4937 inserted in and removed from the running kernel whenever you want).
4938 The module will be called atp870u.o. If you want to compile it as a
4939 module, say M here and read Documentation/modules.txt.
4941 EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support
4943 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
4944 ISA and all EISA i/o addresses are probed looking for the "EATA"
4945 signature. If you chose "BIOS" at the question "PCI access mode",
4946 the addresses of all the PCI SCSI controllers reported by the PCI
4947 subsystem are probed as well.
4949 You want to read the start of drivers/scsi/eata.c and the
4950 SCSI-HOWTO, available from
4951 http://metalab.unc.edu/mdw/linux.html#howto .
4953 Note that there is also another driver for the same hardware
4954 available: "EATA-DMA support". You should say Y to only one of them.
4956 If you want to compile this as a module ( = code which can be
4957 inserted in and removed from the running kernel whenever you want),
4958 say M here and read Documentation/modules.txt. The module will be
4961 enable tagged command queuing
4962 CONFIG_SCSI_EATA_TAGGED_QUEUE
4963 This is a feature of SCSI-2 which improves performance: the host
4964 adapter can send several SCSI commands to a device's queue even if
4965 previous commands haven't finished yet. Most EATA adapters negotiate
4966 this feature automatically with the device, even if your answer is
4967 N. The safe answer is N.
4969 enable elevator sorting
4970 CONFIG_SCSI_EATA_LINKED_COMMANDS
4971 This option enables elevator sorting for all probed SCSI disks and
4972 CDROMs. It definitely reduces the average seek distance when doing
4973 random seeks, but this does not necessarily result in a noticeable
4974 performance improvement: your mileage may vary...
4975 The safe answer is N.
4977 maximum number of queued commands
4978 CONFIG_SCSI_EATA_MAX_TAGS
4979 This specifies how many SCSI commands can be maximally queued for
4980 each probed SCSI device. You should reduce the default value of 16
4981 only if you have disks with buggy or limited tagged command support.
4982 Minimum is 2 and maximum is 62. This value is also the window size
4983 used by the elevator sorting option above. The effective value used
4984 by the driver for each probed SCSI device is reported at boot time.
4986 NCR53c406a SCSI support
4987 CONFIG_SCSI_NCR53C406A
4988 This is support for the NCR53c406a SCSI host adapter. For user
4989 configurable parameters, check out drivers/scsi/NCR53c406.c in the
4990 kernel source. Also read the SCSI-HOWTO, available from
4991 http://metalab.unc.edu/mdw/linux.html#howto .
4993 If you want to compile this driver as a module ( = code which can be
4994 inserted in and removed from the running kernel whenever you want),
4995 say M here and read Documentation/modules.txt. The module will be
4998 Symbios Logic sym53c416 support
4999 CONFIG_SCSI_SYM53C416
5000 This is support for the sym53c416 SCSI host adapter, the SCSI
5001 adapter that comes with some HP scanners. This driver requires that
5002 the sym53c416 is configured first using some sort of pnp
5003 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
5004 are using isapnp then you need to compile this driver as a module
5005 and then load it using insmod after isapnp has run. The parameters
5006 of the configured card(s) should be passed to the driver. The format
5009 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
5011 There is support for up to four adapters. If you want to compile
5012 this driver as a module ( = code which can be inserted in and
5013 removed from the running kernel whenever you want), say M here and
5014 read Documentation/modules.txt. The module will be called
5017 Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support
5019 This driver supports PCI SCSI host adapters based on the Am53C974A
5020 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
5021 PCscsi/PCnet (Am53/79C974) solutions.
5023 Documentation can be found in linux/drivers/scsi/README.tmscsim.
5025 Note that this driver does NOT support Tekram DC390W/U/F, which are
5026 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
5027 Also note that there is another generic Am53C974 driver,
5028 "AM53/79C974 PCI SCSI support" below. You can pick either one.
5030 If you want to compile this driver as a module ( = code which can be
5031 inserted in and removed from the running kernel whenever you want),
5032 say M here and read Documentation/modules.txt. The module will be
5035 Omit support for other Am53/79C974 based SCSI adapters
5036 CONFIG_SCSI_DC390T_NOGENSUPP
5037 If you say N here, the DC390(T) SCSI driver relies on the DC390
5038 EEPROM to get initial values for its settings, such as speed,
5039 termination, etc. If it can't find this EEPROM, it will use defaults
5040 or the user supplied boot/module parameters. For details on driver
5041 configuration see linux/drivers/scsi/README.tmscsim.
5043 If you say Y here and if no EEPROM is found, the driver gives up and
5044 thus only supports Tekram DC390(T) adapters. This can be useful if
5045 you have a DC390(T) and another Am53C974 based adapter, which, for
5046 some reason, you want to drive with the other AM53C974 driver.
5050 AM53/79C974 PCI SCSI support
5051 CONFIG_SCSI_AM53C974
5052 This is support for the AM53/79C974 SCSI host adapters. Please read
5053 drivers/scsi/README.AM53C974 for details. Also, the SCSI-HOWTO,
5054 available from http://metalab.unc.edu/mdw/linux.html#howto , is for
5057 Note that there is another driver for AM53C974 based adapters:
5058 "Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support", above. You
5059 can pick either one.
5061 If you want to compile this driver as a module ( = code which can be
5062 inserted in and removed from the running kernel whenever you want),
5063 say M here and read Documentation/modules.txt. The module will be
5066 AMI MegaRAID support
5067 CONFIG_SCSI_MEGARAID
5068 This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490
5069 and 467 SCSI host adapters.
5071 If you want to compile this driver as a module ( = code which can be
5072 inserted in and removed from the running kernel whenever you want),
5073 say M here and read Documentation/modules.txt. The module will be
5076 GDT SCSI Disk Array Controller support
5078 This is a driver for all SCSI Disk Array Controllers (EISA/ISA/PCI)
5079 manufactured by ICP vortex. It is documented in the kernel source in
5080 drivers/scsi/gdth.c and drivers/scsi/gdth.h.
5082 This driver is also available as a module ( = code which can be
5083 inserted in and removed from the running kernel whenever you want).
5084 If you want to compile it as a module, say M here and read
5085 Documentation/modules.txt.
5087 IOMEGA parallel port (ppa - older drives)
5089 This driver supports older versions of IOMEGA's parallel port ZIP
5090 drive (a 100 MB removable media device).
5092 Note that you can say N here if you have the SCSI version of the ZIP
5093 drive: it will be supported automatically if you said Y to the
5094 generic "SCSI disk support", above.
5096 If you have the ZIP Plus drive or a more recent parallel port ZIP
5097 drive (if the supplied cable with the drive is labeled "AutoDetect")
5098 then you should say N here and Y to "IOMEGA parallel port (imm -
5099 newer drives)", below.
5101 For more information about this driver and how to use it you should
5102 read the file drivers/scsi/README.ppa. You should also read the
5103 SCSI-HOWTO, which is available from
5104 http://metalab.unc.edu/mdw/linux.html#howto . If you use this driver,
5105 you will still be able to use the parallel port for other tasks,
5106 such as a printer; it is safe to compile both drivers into the
5109 This driver is also available as a module which can be inserted in
5110 and removed from the running kernel whenever you want. To compile
5111 this driver as a module, say M here and read
5112 Documentation/modules.txt. The module will be called ppa.o.
5114 IOMEGA parallel port (imm - newer drives)
5116 This driver supports newer versions of IOMEGA's parallel port ZIP
5117 drive (a 100 MB removable media device).
5119 Note that you can say N here if you have the SCSI version of the ZIP
5120 drive: it will be supported automatically if you said Y to the
5121 generic "SCSI disk support", above.
5123 If you have the ZIP Plus drive or a more recent parallel port ZIP
5124 drive (if the supplied cable with the drive is labeled "AutoDetect")
5125 then you should say Y here; if you have an older ZIP drive, say N
5126 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
5128 For more information about this driver and how to use it you should
5129 read the file drivers/scsi/README.ppa. You should also read the
5130 SCSI-HOWTO, which is available from
5131 http://metalab.unc.edu/mdw/linux.html#howto . If you use this driver,
5132 you will still be able to use the parallel port for other tasks,
5133 such as a printer; it is safe to compile both drivers into the
5136 This driver is also available as a module which can be inserted in
5137 and removed from the running kernel whenever you want. To compile
5138 this driver as a module, say M here and read
5139 Documentation/modules.txt. The module will be called imm.o.
5141 Force the Iomega ZIP drivers to use EPP-16
5142 CONFIG_SCSI_IZIP_EPP16
5143 EPP (Enhanced Parallel Port) is a standard for parallel ports which
5144 allows them to act as expansion buses that can handle up to 64
5147 Some parallel port chipsets are slower than their motherboard, and
5148 so we have to control the state of the chipset's FIFO queue every
5149 now and then to avoid data loss. This will be done if you say Y
5152 Generally, saying Y is the safe option and slows things down a bit.
5154 Assume slow parallel port control register
5155 CONFIG_SCSI_IZIP_SLOW_CTR
5156 Some parallel ports are known to have excessive delays between
5157 changing the parallel port control register and good data being
5158 available on the parallel port data/status register. This option
5159 forces a small delay (1.0 usec to be exact) after changing the
5160 control register to let things settle out. Enabling this option may
5161 result in a big drop in performance but some very old parallel ports
5162 (found in 386 vintage machines) will not work properly.
5164 Generally, saying N is fine.
5166 SCSI Debug host simulator. (EXPERIMENTAL)
5168 This is a host adapter simulator that can be programmed to simulate
5169 a large number of conditions that could occur on a real bus. The
5170 advantage is that many hard to reproduce problems can be tested in a
5171 controlled environment where there is reduced risk of losing
5172 important data. This is primarily of use to people trying to debug
5173 the middle and upper layers of the SCSI subsystem. If unsure, say N.
5175 Fibre Channel support
5177 This is an experimental support for storage arrays connected to
5178 the system using Fibre Optic and the "X3.269-199X Fibre Channel
5179 Protocol for SCSI" specification. You'll also need the generic SCSI
5180 support, as well as the drivers for the storage array itself and
5181 for the interface adapter such as SOC. This subsystem could even
5182 serve for IP networking, with some code extensions.
5188 Serial Optical Channel is an interface card with one or two Fibre
5189 Optic ports, each of which can be connected to a disk array. Only
5190 the SBus incarnation of the adapter is supported at the moment.
5192 SparcSTORAGE Array 100 and 200 series
5194 If you never bought a disk array made by Sun, go with N.
5197 CONFIG_SCSI_ACORNSCSI_3
5198 This enables support for the Acorn SCSI card (aka30). If you have an
5199 Acorn system with one of these, say Y. If unsure, say N.
5201 Acorn SCSI tagged queue support
5202 CONFIG_SCSI_ACORNSCSI_TAGGED_QUEUE
5203 Say Y here to enable tagged queuing support on the Acorn SCSI card.
5205 This is a feature of SCSI-2 which improves performance: the host
5206 adapter can send several SCSI commands to a device's queue even if
5207 previous commands haven't finished yet. Some SCSI devices don't
5208 implement this properly, so the safe answer is N.
5210 Acorn SCSI Synchronous transfers support
5211 CONFIG_SCSI_ACORNSCSI_SYNC
5212 Say Y here to enable synchronous transfer negotiation with all
5213 targets on the Acorn SCSI card.
5215 In general, this improves performance; however some SCSI devices
5216 don't implement it properly, so the safe answer is N.
5220 This enables support for the Oak SCSI card. If you have an Acorn
5221 system with one of these, say Y. If unsure, say N.
5223 Cumana SCSI I support
5224 CONFIG_SCSI_CUMANA_1
5225 This enables support for the Cumana SCSI I card. If you have an
5226 Acorn system with one of these, say Y. If unsure, say N.
5228 Cumana SCSI II support (EXPERIMENTAL)
5229 CONFIG_SCSI_CUMANA_2
5230 This enables support for the Cumana SCSI II card. If you have an
5231 Acorn system with one of these, say Y. If unsure, say N.
5235 This enables support for the EcoSCSI card -- a small card that sits
5236 in the Econet socket. If you have an Acorn system with one of these,
5237 say Y. If unsure, say N.
5239 EESOX SCSI support (EXPERIMENTAL)
5240 CONFIG_SCSI_EESOXSCSI
5241 This enables support for the EESOX SCSI card. If you have an Acorn
5242 system with one of these, say Y, otherwise say N.
5244 Powertec SCSI support (EXPERIMENTAL)
5245 CONFIG_SCSI_POWERTECSCSI
5246 This enables support for the Powertec SCSI card on Acorn systems. If
5247 you have one of these, say Y. If unsure, say N.
5249 Network device support?
5251 You can say N here if you don't intend to connect your Linux box to
5252 any other computer at all or if all your connections will be over a
5253 telephone line with a modem either via UUCP (UUCP is a protocol to
5254 forward mail and news between unix hosts over telephone lines; read
5255 the UUCP-HOWTO, available from
5256 http://metalab.unc.edu/mdw/linux.html#howto ) or dialing up a shell
5257 account or a BBS, even using term (term is a program which gives you
5258 almost full Internet connectivity if you have a regular dial up
5259 shell account on some Internet connected Unix computer. Read
5260 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html ).
5262 You'll have to say Y if your computer contains a network card that
5263 you want to use under Linux (make sure you know its name because you
5264 will be asked for it and read the Ethernet-HOWTO (especially if you
5265 plan to use more than one network card under Linux)) or if you want
5266 to use SLIP (Serial Line Internet Protocol is the protocol used to
5267 send Internet traffic over telephone lines or null modem cables) or
5268 CSLIP (compressed SLIP) or PPP (Point to Point Protocol, a better
5269 and newer replacement for SLIP) or PLIP (Parallel Line Internet
5270 Protocol is mainly used to create a mini network by connecting the
5271 parallel ports of two local machines) or AX.25/KISS (protocol for
5272 sending Internet traffic over amateur radio links).
5274 Make sure to read the NET-3-HOWTO. Eventually, you will have to read
5275 Olaf Kirch's excellent and free book "Network Administrator's
5276 Guide", to be found in ftp://metalab.unc.edu/pub/Linux/docs/LDP . If
5279 Dummy net driver support
5281 This is essentially a bit-bucket device (i.e. traffic you send to
5282 this device is consigned into oblivion) with a configurable IP
5283 address. It is most commonly used in order to make your currently
5284 inactive SLIP address seem like a real address for local programs.
5285 If you use SLIP or PPP, you might want to say Y here. Since this
5286 thing often comes in handy, the default is Y. It won't enlarge your
5287 kernel either. What a deal. Read about it in the Network
5288 Administrator's Guide, available from
5289 http://metalab.unc.edu/mdw/linux.html#guide .
5291 If you want to compile this as a module ( = code which can be
5292 inserted in and removed from the running kernel whenever you want),
5293 say M here and read Documentation/modules.txt. The module will be
5294 called dummy.o. If you want to use more than one dummy device at a
5295 time, you need to compile this driver as a module. Instead of
5296 'dummy', the devices will then be called 'dummy0', 'dummy1' etc.
5298 SLIP (serial line) support
5300 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
5301 connect to your Internet service provider or to connect to some
5302 other local Unix box or if you want to configure your Linux box as a
5303 Slip/CSlip server for other people to dial in. SLIP (Serial Line
5304 Internet Protocol) is a protocol used to send Internet traffic over
5305 serial connections such as telephone lines or null modem cables;
5306 nowadays, the protocol PPP is more commonly used for this same
5309 Normally, your access provider has to support SLIP in order for you
5310 to be able to use it, but there is now a SLIP emulator called SLiRP
5311 around (available via FTP (user: anonymous) from
5312 ftp://metalab.unc.edu/pub/Linux/system/network/serial/ ) which
5313 allows you to use SLIP over a regular dial up shell connection. If
5314 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
5315 NET-3-HOWTO, available from
5316 http://metalab.unc.edu/mdw/linux.html#howto , explains how to
5317 configure SLIP. Note that you don't need this option if you just
5318 want to run term (term is a program which gives you almost full
5319 Internet connectivity if you have a regular dial up shell account on
5320 some Internet connected Unix computer. Read
5321 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html ). SLIP
5322 support will enlarge your kernel by about 4 KB. If unsure, say N.
5324 If you want to compile this as a module ( = code which can be
5325 inserted in and removed from the running kernel whenever you want),
5326 say M here and read Documentation/modules.txt as well as
5327 Documentation/networking/net-modules.txt. The module will be called
5330 CSLIP compressed headers
5331 CONFIG_SLIP_COMPRESSED
5332 This protocol is faster than SLIP because it uses compression on the
5333 TCP/IP headers (not on the data itself), but it has to be supported
5334 on both ends. Ask your access provider if you are not sure and
5335 answer Y, just in case. You will still be able to use plain SLIP. If
5336 you plan to use SLiRP, the SLIP emulator (available from
5337 ftp://metalab.unc.edu/pub/Linux/system/network/serial/ ) which allows
5338 you to use SLIP over a regular dial up shell connection, you
5339 definitely want to say Y here. The NET-3-HOWTO, available from
5340 http://metalab.unc.edu/mdw/linux.html#howto , explains how to
5341 configure CSLIP. This won't enlarge your kernel.
5343 Keepalive and linefill
5345 Adds additional capabilities to the SLIP driver to support the
5346 RELCOM line fill and keepalive monitoring. Ideal on poor quality
5349 Six bit SLIP encapsulation
5350 CONFIG_SLIP_MODE_SLIP6
5351 Just occasionally you may need to run IP over hostile serial
5352 networks that don't pass all control characters or are only seven
5353 bit. Saying Y here adds an extra mode you can use with SLIP:
5354 "slip6". In this mode, SLIP will only send normal ASCII symbols over
5355 the serial device. Naturally, this has to be supported at the other
5356 end of the link as well. It's good enough, for example, to run IP
5357 over the async ports of a Camtec JNT Pad. If unsure, say N.
5359 PPP (point-to-point protocol) support
5361 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
5362 the same purpose: sending Internet traffic over telephone (and other
5363 serial) lines. Ask your access provider if they support it, because
5364 otherwise you can't use it; most internet access providers these
5365 days support PPP rather than SLIP.
5367 To use PPP, you need an additional program called pppd as described
5368 in Documentation/networking/ppp.txt and in the PPP-HOWTO, available
5369 at http://metalab.unc.edu/mdw/linux.html#howto . If you upgrade
5370 from an older kernel, you might need to upgrade pppd as well. The
5371 PPP option enlarges your kernel by about 16 KB.
5373 There are actually two versions of PPP: the traditional PPP for
5374 asynchronous lines, such as regular analog phone lines, and
5375 synchronous PPP which can be used over digital ISDN lines for
5376 example. If you want to use PPP over phone lines or other
5377 asynchronous serial lines, you need to say Y (or M) here and also to
5378 the next option, "PPP support for async serial ports". For PPP over
5379 synchronous lines, you should say Y (or M) here and to "Support
5380 synchronous PPP", below.
5382 This driver is also available as a module ( = code which can be
5383 inserted in and removed from the running kernel whenever you want).
5384 If you said Y to "Version information on all symbols" above, then
5385 you cannot compile the PPP driver into the kernel; you can then only
5386 compile it as a module. The module will be called ppp_generic.o. If
5387 you want to compile it as a module, say M here and read
5388 Documentation/modules.txt as well as
5389 Documentation/networking/net-modules.txt.
5391 PPP support for async serial ports
5393 Say Y (or M) here if you want to be able to use PPP over standard
5394 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
5395 a modem (not a synchronous or ISDN modem) to contact your ISP, you
5398 This code is also available as a module (code which can be inserted
5399 into and removed from the running kernel). If you want to compile
5400 it as a module, say M here and read Documentation/modules.txt.
5403 Say Y (or M) here if you want to be able to use PPP over synchronous
5404 (HDLC) tty devices, such as the SyncLink adapter. These devices
5405 are often used for high-speed leased lines like T1/E1.
5407 This code is also available as a module (code which can be inserted
5408 into and removed from the running kernel). If you want to compile
5409 it as a module, say M here and read Documentation/modules.txt.
5411 PPP Deflate compression
5413 Support for the Deflate compression method for PPP, which uses the
5414 Deflate algorithm (the same algorithm that gzip uses) to compress
5415 each PPP packet before it is sent over the wire. The machine at the
5416 other end of the PPP link (usually your ISP) has to support the
5417 Deflate compression method as well for this to be useful. Even if
5418 they don't support it, it is safe to say Y here.
5420 This code is also available as a module (code which can be inserted
5421 into and removed from the running kernel). If you want to compile
5422 it as a module, say M here and read Documentation/modules.txt.
5424 PPP BSD-Compress compression
5426 Support for the BSD-Compress compression method for PPP, which uses
5427 the LZW compression method to compress each PPP packet before it is
5428 sent over the wire. The machine at the other end of the PPP link
5429 (usually your ISP) has to support the BSD-Compress compression
5430 method as well for this to be useful. Even if they don't support it,
5431 it is safe to say Y here.
5433 The PPP Deflate compression method ("PPP Deflate compression",
5434 above) is preferable to BSD-Compress, because it compresses better
5437 Note that the BSD compression code will always be compiled as a
5438 module; it is called bsd_comp.o and will show up in the directory
5439 modules once you have said "make modules". If unsure, say N.
5441 Wireless LAN (non-hamradio)
5443 Support for wireless LANs and everything having to do with radio,
5444 but not with amateur radio. Note that the answer to this question
5445 won't directly affect the kernel: saying N will just cause this
5446 configure script to skip all the questions about radio
5449 Some user-level drivers for scarab devices which don't require
5450 special kernel support are available from
5451 ftp://shadow.cabi.net/pub/Linux .
5453 STRIP (Metricom Starmode radio IP)
5455 Say Y if you have a Metricom radio and intend to use Starmode Radio
5456 IP. STRIP is a radio protocol developed for the MosquitoNet project
5457 (on the WWW at http://mosquitonet.stanford.edu/ ) to send Internet
5458 traffic using Metricom radios. Metricom radios are small, battery
5459 powered, 100kbit/sec packet radio transceivers, about the size and
5460 weight of a cellular telephone. (You may also have heard them called
5461 "Metricom modems" but we avoid the term "modem" because it misleads
5462 many people into thinking that you can plug a Metricom modem into a
5463 phone line and use it as a modem.)
5465 You can use STRIP on any Linux machine with a serial port, although
5466 it is obviously most useful for people with laptop computers. If you
5467 think you might get a Metricom radio in the future, there is no harm
5468 in saying Y to STRIP now, except that it makes the kernel a bit
5471 You can also compile this as a module ( = code which can be inserted
5472 in and removed from the running kernel whenever you want), say M
5473 here and read Documentation/modules.txt. The module will be called
5476 AT&T WaveLAN & DEC RoamAbout DS support
5478 The Lucent WaveLAN (formerly NCR and AT&T; or DEC RoamAbout DS) is
5479 a Radio LAN (wireless Ethernet-like Local Area Network) using the
5480 radio frequencies 900 MHz and 2.4 GHz.
5482 This driver support the ISA version of the WaveLAN card. A separate
5483 driver for the PCMCIA (PC-card) hardware is available in David
5484 Hinds' pcmcia-cs package (see the file Documentation/Changes for
5487 If you want to use an ISA WaveLAN card under Linux, say Y and read
5488 the Ethernet-HOWTO, available from
5489 http://metalab.unc.edu/mdw/linux.html#howto . Some more specific
5490 information is contained in Documentation/networking/wavelan.txt and
5491 in the source code drivers/net/wavelan.p.h.
5493 You will also need the wireless tools package available from
5494 ftp://hyper.stanford.edu/pub/pcmcia/contrib/ . Please read the man
5495 pages contained therein.
5497 This driver is also available as a module ( = code which can be
5498 inserted in and removed from the running kernel whenever you want).
5499 The module will be called wavelan.o. If you want to compile it as a
5500 module, say M here and read Documentation/modules.txt as well as
5501 Documentation/networking/net-modules.txt.
5503 Aironet Arlan 655 & IC2200 DS support
5505 Aironet makes Arlan, a class of wireless LAN adapters. These use the
5506 www.Telxon.com chip, which is also used on several similar cards.
5507 This driver is tested on the 655 and IC2200 series cards. Look at
5508 http://www.ylenurme.ee/~elmer/655/ for latest information.
5510 The driver is built as two modules, arlan and arlan-proc. The latter
5511 is the /proc interface and is not needed most of time.
5513 On some computers the card ends up in non-valid state after some time.
5514 Use a ping-reset script to clear it.
5516 LAPB over Ethernet driver
5518 This is a driver for a pseudo device (typically called /dev/lapb0)
5519 which allows you to open an LAPB point-to-point connection to some
5520 other computer on your Ethernet network. In order to do this, you
5521 need to say Y or M to the driver for your Ethernet card as well as
5522 to "LAPB Data Link Driver".
5524 If you want to compile this driver as a module ( = code which can be
5525 inserted in and removed from the running kernel whenever you want),
5526 say M here and read Documentation/modules.txt. The module will be
5527 called lapbether.o. If unsure, say N.
5531 This is a driver for sending and receiving X.25 frames over regular
5532 asynchronous serial lines such as telephone lines equipped with
5533 ordinary modems. Experts should note that this driver doesn't
5534 currently comply with the asynchronous HDLS framing protocols in
5535 CCITT recommendation X.25.
5537 If you want to compile this driver as a module ( = code which can be
5538 inserted in and removed from the running kernel whenever you want),
5539 say M here and read Documentation/modules.txt. The module will be
5540 called x25_asy.o. If unsure, say N.
5542 PCMCIA network device support
5544 Say Y if you would like to include support for any PCMCIA network
5545 adapters. If unsure, say N.
5547 3Com 3c589 PCMCIA support
5549 Say Y here if you intend to attach a 3Com 3c589 or compatible PCMCIA
5550 (PC-card) Ethernet card to your computer.
5552 This driver is also available as a module ( = code which can be
5553 inserted in and removed from the running kernel whenever you want).
5554 The module will be called 3c589_cs.o. If you want to compile it as a
5555 module, say M here and read Documentation/modules.txt. If unsure,
5558 3Com 3c574 PCMCIA support
5560 Say Y here if you intend to attach a 3Com 3c574 or compatible PCMCIA
5561 (PC-card) Fast Ethernet card to your computer.
5563 This driver is also available as a module ( = code which can be
5564 inserted in and removed from the running kernel whenever you want).
5565 The module will be called 3c574_cs.o. If you want to compile it as a
5566 module, say M here and read Documentation/modules.txt. If unsure,
5569 Fujitsu FMV-J18x PCMCIA support
5570 CONFIG_PCMCIA_FMVJ18X
5571 Say Y here if you intend to attach a Fujitsu FMV-J18x or compatible
5572 PCMCIA (PC-card) Ethernet card to your computer.
5574 This driver is also available as a module ( = code which can be
5575 inserted in and removed from the running kernel whenever you want).
5576 The module will be called fmvj18x_cs.o. If you want to compile it as a
5577 module, say M here and read Documentation/modules.txt. If unsure,
5580 NE2000 compatible PCMCIA support
5582 Say Y here if you intend to attach an NE2000 compatible PCMCIA
5583 (PC-card) Ethernet or Fast Ethernet card to your computer.
5585 This driver is also available as a module ( = code which can be
5586 inserted in and removed from the running kernel whenever you want).
5587 The module will be called pcnet_cs.o. If you want to compile it as a
5588 module, say M here and read Documentation/modules.txt. If unsure,
5591 New Media PCMCIA support
5592 CONFIG_PCMCIA_NMCLAN
5593 Say Y here if you intend to attach a New Media Ethernet or LiveWire
5594 PCMCIA (PC-card) Ethernet card to your computer.
5596 This driver is also available as a module ( = code which can be
5597 inserted in and removed from the running kernel whenever you want).
5598 The module will be called nmclan_cs.o. If you want to compile it as a
5599 module, say M here and read Documentation/modules.txt. If unsure,
5602 SMC 91Cxx PCMCIA support
5603 CONFIG_PCMCIA_SMC91C92
5604 Say Y here if you intend to attach an SMC 91Cxx compatible PCMCIA
5605 (PC-card) Ethernet or Fast Ethernet card to your computer.
5607 This driver is also available as a module ( = code which can be
5608 inserted in and removed from the running kernel whenever you want).
5609 The module will be called smc91c92_cs.o. If you want to compile it as a
5610 module, say M here and read Documentation/modules.txt. If unsure,
5613 Xircom 16-bit PCMCIA support
5614 CONFIG_PCMCIA_XIRC2PS
5615 Say Y here if you intend to attach a Xircom 16-bit PCMCIA
5616 (PC-card) Ethernet or Fast Ethernet card to your computer.
5618 This driver is also available as a module ( = code which can be
5619 inserted in and removed from the running kernel whenever you want).
5620 The module will be called xirc2ps_cs.o. If you want to compile it as a
5621 module, say M here and read Documentation/modules.txt. If unsure,
5624 3Com 3c575 CardBus support
5626 This driver supports the 3Com 3c575 series of CardBus Fast Ethernet
5629 This driver can only be compiled as a module ( = code which can be
5630 inserted in and removed from the running kernel whenever you want).
5631 The module will be called 3c575_cb.o. If you want to do that, say M
5632 here and read Documentation/modules.txt. If unsure, say N.
5634 DEC Tulip CardBus support
5636 This driver supports CardBus Fast Ethernet adapters based on DEC
5637 Tulip and compatible chipsets.
5639 This driver can only be compiled as a module ( = code which can be
5640 inserted in and removed from the running kernel whenever you want).
5641 The module will be called tulip_cb.o. If you want to do that, say M
5642 here and read Documentation/modules.txt. If unsure, say N.
5644 SMC EPIC CardBus support
5645 CONFIG_PCMCIA_EPIC100
5646 This driver supports CardBus Fast Ethernet adapters based on the SMC
5649 This driver can only be compiled as a module ( = code which can be
5650 inserted in and removed from the running kernel whenever you want).
5651 The module will be called epic100_cb.o. If you want to do that, say
5652 M here and read Documentation/modules.txt. If unsure, say N.
5654 Aviator/Raytheon 2.4MHz wireless support
5656 Say Y here if you intend to attach an Aviator/Raytheon PCMCIA
5657 (PC-card) wireless Ethernet networking card to your computer.
5659 This driver is also available as a module ( = code which can be
5660 inserted in and removed from the running kernel whenever you want).
5661 The module will be called ray_cs.o. If you want to compile it as a
5662 module, say M here and read Documentation/modules.txt. If unsure,
5665 Xircom Netwave AirSurfer wireless support
5666 CONFIG_PCMCIA_NETWAVE
5667 Say Y here if you intend to attach a Xircom Netwave AirSurfer PCMCIA
5668 (PC-card) wireless Ethernet networking card to your computer.
5670 This driver is also available as a module ( = code which can be
5671 inserted in and removed from the running kernel whenever you want).
5672 The module will be called netwave_cs.o. If you want to compile it as a
5673 module, say M here and read Documentation/modules.txt. If unsure,
5676 AT&T/Lucent Wavelan wireless support
5677 CONFIG_PCMCIA_WAVELAN
5678 Say Y here if you intend to attach an AT&T/Lucent Wavelan PCMCIA
5679 (PC-card) wireless Ethernet networking card to your computer. This
5680 driver is for the non-IEEE-802.11 Wavelan cards.
5682 This driver is also available as a module ( = code which can be
5683 inserted in and removed from the running kernel whenever you want).
5684 The module will be called wavelan_cs.o. If you want to compile it as a
5685 module, say M here and read Documentation/modules.txt. If unsure,
5688 PLIP (parallel port) support
5690 PLIP (Parallel Line Internet Protocol) is used to create a
5691 reasonably fast mini network consisting of two (or, rarely, more)
5692 local machines. A PLIP link from a Linux box is a popular means to
5693 install a Linux distribution on a machine which doesn't have a CDROM
5694 drive (a minimal system has to be transferred with floppies first).
5695 The kernels on both machines need to have this PLIP option enabled
5698 The PLIP driver has two modes, mode 0 and mode 1. The parallel ports
5699 (the connectors at the computers with 25 holes) are connected with
5700 "null printer" or "Turbo Laplink" cables which can transmit 4 bits
5701 at a time (mode 0) or with special PLIP cables, to be used on
5702 bidirectional parallel ports only, which can transmit 8 bits at a
5703 time (mode 1); you can find the wiring of these cables in
5704 Documentation/networking/PLIP.txt. The cables can be up to 15m long.
5705 Mode 0 works also if one of the machines runs DOS/Windows and has
5706 some PLIP software installed, e.g. the Crynwr PLIP packet driver
5707 (http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html ) and
5708 winsock or NCSA's telnet.
5710 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
5711 as the NET-3-HOWTO, both available from
5712 http://metalab.unc.edu/mdw/linux.html#howto . Note that the PLIP
5713 protocol has been changed and this PLIP driver won't work together
5714 with the PLIP support in Linux versions 1.0.x. This option enlarges
5715 your kernel by about 8 KB.
5717 If you want to compile this as a module ( = code which can be
5718 inserted in and removed from the running kernel whenever you want),
5719 say M here and read Documentation/modules.txt as well as
5720 Documentation/networking/net-modules.txt. The module will be called
5721 plip.o. If unsure, say Y or M, in case you buy a laptop later.
5723 EQL (serial line load balancing) support
5725 If you have two serial connections to some other computer (this
5726 usually requires two modems and two telephone lines) and you use
5727 SLIP (the protocol for sending Internet traffic over telephone
5728 lines) or PPP (a better SLIP) on them, you can make them behave like
5729 one double speed connection using this driver. Naturally, this has
5730 to be supported at the other end as well, either with a similar EQL
5731 Linux driver or with a Livingston Portmaster 2e.
5733 Say Y if you want this and read Documentation/networking/eql.txt.
5734 You may also want to read section 6.2 of the NET-3-HOWTO, available
5735 from http://metalab.unc.edu/mdw/linux.html#howto .
5737 This driver is also available as a module ( = code which can be
5738 inserted in and removed from the running kernel whenever you want).
5739 The module will be called eql.o. If you want to compile it as a
5740 module, say M here and read Documentation/modules.txt. If unsure,
5743 Ethertap network tap (EXPERIMENTAL)
5745 If you say Y here (and have said Y to "Kernel/User network link
5746 driver", above) and create a character special file /dev/tap0 with
5747 major number 36 and minor number 16 using mknod ("man mknod"), you
5748 will be able to have a user space program read and write raw
5749 Ethernet frames from/to that special file. tap0 can be configured
5750 with ifconfig and route like any other Ethernet device but it is not
5751 connected to any physical LAN; everything written by the user to
5752 /dev/tap0 is treated by the kernel as if it had come in from a LAN
5753 to the device tap0; everything the kernel wants to send out over the
5754 device tap0 can instead be read by the user from /dev/tap0: the user
5755 mode program replaces the LAN that would be attached to an ordinary
5756 Ethernet device. Please read the file
5757 Documentation/networking/ethertap.txt for more information.
5759 This driver is also available as a module ( = code which can be
5760 inserted in and removed from the running kernel whenever you want).
5761 The module will be called ethertap.o. If you want to compile it as a
5762 module, say M here and read Documentation/modules.txt.
5764 If you don't know what to use this for, you don't need it.
5766 Sealevel Systems 4021 support
5767 CONFIG_SEALEVEL_4021
5768 This is a driver for the Sealevel Systems ACB 56 serial I/O adapter.
5770 This driver can only be compiled as a module ( = code which can be
5771 inserted in and removed from the running kernel whenever you want).
5772 If you want to do that, say M here. The module will be called
5775 Frame Relay (DLCI) support
5777 This is support for the frame relay protocol; frame relay is a fast
5778 low-cost way to connect to a remote Internet access provider or to
5779 form a private wide area network. The one physical line from your
5780 box to the local "switch" (i.e. the entry point to the frame relay
5781 network, usually at the phone company) can carry several logical
5782 point-to-point connections to other computers connected to the frame
5783 relay network. For a general explanation of the protocol, check out
5784 http://www.frforum.com/ on the WWW. To use frame relay, you need
5785 supporting hardware (called FRAD) and certain programs from the
5786 net-tools package as explained in
5787 Documentation/networking/framerelay.txt.
5789 This driver is also available as a module ( = code which can be
5790 inserted in and removed from the running kernel whenever you want).
5791 The module will be called dlci.o. If you want to compile it as a
5792 module, say M here and read Documentation/modules.txt.
5796 This is the maximal number of logical point-to-point frame relay
5797 connections (the identifiers of which are called DCLIs) that
5798 the driver can handle. The default is probably fine.
5802 You can specify here how many logical point-to-point frame relay
5803 connections (the identifiers of which are called DCLIs) should be
5804 handled by each of your hardware frame relay access devices. Go with
5807 Sangoma S502A FRAD support
5809 Say Y here if you need a driver for the Sangoma S502A, S502E, and
5810 S508 Frame Relay Access Devices. These are multi-protocol cards, but
5811 only frame relay is supported by the driver at this time. Please
5812 read Documentation/framerelay.txt.
5814 This driver is also available as a module ( = code which can be
5815 inserted in and removed from the running kernel whenever you want).
5816 The module will be called sdla.o. If you want to compile it as a
5817 module, say M here and read Documentation/modules.txt.
5819 Acorn Econet/AUN protocols (EXPERIMENTAL)
5821 Econet is a fairly old and slow networking protocol mainly used by
5822 Acorn computers to access file and print servers. It uses native
5823 Econet network cards. AUN is an implementation of the higher level
5824 parts of Econet that runs over ordinary Ethernet connections, on
5825 top of the UDP packet protocol, which in turn runs on top of the
5826 Internet protocol IP.
5828 If you say Y here, you can choose with the next two options whether
5829 to send Econet/AUN traffic over a UDP Ethernet connection or over
5830 a native Econet network card.
5832 This driver is also available as a module ( = code which can be
5833 inserted in and removed from the running kernel whenever you want).
5834 The module will be called econet.o. If you want to compile it as a
5835 module, say M here and read Documentation/modules.txt.
5838 CONFIG_ECONET_AUNUDP
5839 Say Y here if you want to send Econet/AUN traffic over a UDP
5840 connection (UDP is a packet based protocol that runs on top of the
5841 Internet protocol IP) using an ordinary Ethernet network card.
5844 CONFIG_ECONET_NATIVE
5845 Say Y here if you have a native Econet network card installed in
5850 Wide Area Networks (WANs), such as X.25, frame relay and leased
5851 lines, are used to interconnect Local Area Networks (LANs) over vast
5852 distances with data transfer rates significantly higher than those
5853 achievable with commonly used asynchronous modem connections.
5854 Usually, a quite expensive external device called a `WAN router' is
5855 needed to connect to a WAN.
5857 As an alternative, WAN routing can be built into the Linux kernel.
5858 With relatively inexpensive WAN interface cards available on the
5859 market, a perfectly usable router can be built for less than half
5860 the price of an external router. If you have one of those cards and
5861 wish to use your Linux box as a WAN router, say Y here and also to
5862 the WAN driver for your card, below. You will then need the
5863 wan-tools package which is available from ftp://ftp.sangoma.com .
5864 Read Documentation/networking/wan-router.txt for more information.
5866 The WAN routing support is also available as a module called
5867 wanrouter.o ( = code which can be inserted in and removed from the
5868 running kernel whenever you want). If you want to compile it as a
5869 module, say M here and read Documentation/modules.txt.
5873 Fast switching (read help!)
5874 CONFIG_NET_FASTROUTE
5875 Saying Y here enables direct NIC-to-NIC (NIC = Network Interface
5876 Card) data transfers on the local network, which is fast.
5878 IMPORTANT NOTE: This option is NOT COMPATIBLE with "Network packet
5879 filtering" (CONFIG_NETFILTER). Say N here if you say Y there.
5881 However, it will work with all options in the "IP: advanced router"
5882 section (except for "IP: use TOS value as routing key" and
5883 "IP: use FWMARK value as routing key").
5885 At the moment, few devices support fast switching (tulip is one of
5886 them, a modified 8390 driver can be found at
5887 ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz ).
5891 Forwarding between high speed interfaces
5892 CONFIG_NET_HW_FLOWCONTROL
5893 This option enables NIC (Network Interface Card) hardware throttling
5894 during periods of extremal congestion. At the moment only a couple
5895 of device drivers support it (really only one -- tulip, a modified
5896 8390 driver can be found at
5897 ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz ).
5899 Really, this option is applicable to any machine attached to a fast
5900 enough network, and even a 10 Mb NIC is able to kill a not very slow
5901 box, such as a 120MHz Pentium.
5903 However, do not say Y here if you did not experience any serious
5906 QoS and/or fair queueing
5908 When the kernel has several packets to send out over a network
5909 device, it has to decide which ones to send first, which ones to
5910 delay, and which ones to drop. This is the job of the packet
5911 scheduler, and several different algorithms for how to do this
5912 "fairly" have been proposed.
5914 If you say N here, you will get the standard packet scheduler, which
5915 is a FIFO (first come, first served). If you say Y here, you will be
5916 able to choose from among several alternative algorithms which can
5917 then be attached to different network devices. This is useful for
5918 example if some of your network devices are real time devices that
5919 need a certain minimum data flow rate, or if you need to limit the
5920 maximum data flow rate for traffic which matches specified criteria.
5921 This code is considered to be experimental.
5923 To administer these schedulers, you'll need the user-level utilities
5924 from the package iproute2+tc at ftp://ftp.inr.ac.ru/ip-routing/ .
5925 That package also contains some documentation; for more, check out
5926 http://snafu.freedom.org/linux2.2/iproute-notes.html .
5928 If you say Y here and to "/proc filesystem" below, you will be able
5929 to read status information about packet schedulers from the file
5932 The available schedulers are listed in the following questions; you
5933 can say Y to as many as you like. If unsure, say N now.
5935 CBQ packet scheduler
5937 Say Y here if you want to use the Class-Based Queueing (CBQ) packet
5938 scheduling algorithm for some of your network devices. This
5939 algorithm classifies the waiting packets into a tree-like hierarchy
5940 of classes; the leaves of this tree are in turn scheduled by
5941 separate algorithms (called "disciplines" in this context).
5943 See the top of net/sched/sch_cbq.c for references about the CBQ
5946 CBQ is a commonly used scheduler, so if you're unsure, you should
5947 say Y here. Then say Y to all the queueing algorithms below that you
5948 want to use as CBQ disciplines. Then say Y to "Packet classifier
5949 API" and say Y to all the classifiers you want to use; a classifier
5950 is a routine that allows you to sort your outgoing traffic into
5951 classes based on a certain criterion.
5953 This code is also available as a module called sch_cbq.o ( = code
5954 which can be inserted in and removed from the running kernel
5955 whenever you want). If you want to compile it as a module, say M
5956 here and read Documentation/modules.txt.
5958 CSZ packet scheduler
5960 Say Y here if you want to use the Clark-Shenker-Zhang (CSZ) packet
5961 scheduling algorithm for some of your network devices. At the
5962 moment, this is the only algorithm that can guarantee service for
5963 real-time applications (see the top of net/sched/sch_csz.c for
5964 details and references about the algorithm).
5966 Note: this scheduler is currently broken.
5968 This code is also available as a module called sch_csz.o ( = code
5969 which can be inserted in and removed from the running kernel
5970 whenever you want). If you want to compile it as a module, say M
5971 here and read Documentation/modules.txt.
5973 #ATM pseudo-scheduler
5979 The simplest PRIO pseudo scheduler
5981 Say Y here if you want to use an n-band priority queue packet
5982 "scheduler" for some of your network devices or as a leaf discipline
5983 for the CBQ scheduling algorithm. If unsure, say Y.
5985 This code is also available as a module called sch_prio.o ( = code
5986 which can be inserted in and removed from the running kernel
5987 whenever you want). If you want to compile it as a module, say M
5988 here and read Documentation/modules.txt.
5992 Say Y here if you want to use the Random Early Detection (RED)
5993 packet scheduling algorithm for some of your network devices (see
5994 the top of net/sched/sch_red.c for details and references about the
5997 This code is also available as a module called sch_red.o ( = code
5998 which can be inserted in and removed from the running kernel
5999 whenever you want). If you want to compile it as a module, say M
6000 here and read Documentation/modules.txt.
6004 Say Y here if you want to use the Stochastic Fairness Queueing (SFQ)
6005 packet scheduling algorithm for some of your network devices or as a
6006 leaf discipline for the CBQ scheduling algorithm (see the top of
6007 net/sched/sch_sfq.c for details and references about the SFQ
6010 This code is also available as a module called sch_sfq.o ( = code
6011 which can be inserted in and removed from the running kernel
6012 whenever you want). If you want to compile it as a module, say M
6013 here and read Documentation/modules.txt.
6017 Say Y here if you want to use the True Link Equalizer (TLE) packet
6018 scheduling algorithm for some of your network devices or as a leaf
6019 discipline for the CBQ scheduling algorithm. This queueing
6020 discipline allows the combination of several physical devices into
6021 one virtual device. (see the top of net/sched/sch_teql.c for
6024 This code is also available as a module called sch_teql.o ( = code
6025 which can be inserted in and removed from the running kernel
6026 whenever you want). If you want to compile it as a module, say M
6027 here and read Documentation/modules.txt.
6031 Say Y here if you want to use the Simple Token Bucket Filter (TBF)
6032 packet scheduling algorithm for some of your network devices or as a
6033 leaf discipline for the CBQ scheduling algorithm (see the top of
6034 net/sched/sch_tbf.c for a description of the TBF algorithm).
6036 This code is also available as a module called sch_tbf.o ( = code
6037 which can be inserted in and removed from the running kernel
6038 whenever you want). If you want to compile it as a module, say M
6039 here and read Documentation/modules.txt.
6043 Say Y here if you want to include Quality Of Service scheduling
6044 features, which means that you will be able to request certain
6045 rate-of-flow limits for your network devices.
6047 Note that the answer to this question won't directly affect the
6048 kernel: saying N will just cause this configure script to skip all
6049 the questions about QoS support.
6052 CONFIG_NET_ESTIMATOR
6053 In order for Quality of Service scheduling to work, the current
6054 rate-of-flow for a network device has to be estimated; if you say Y
6055 here, the kernel will do just that.
6057 Packet classifier API
6059 The CBQ scheduling algorithm requires that network packets which are
6060 scheduled to be sent out over a network device be classified
6061 according to some criterion. If you say Y here, you will get a
6062 choice of several different packet classifiers with the following
6065 Routing tables based classifier
6066 CONFIG_NET_CLS_ROUTE
6067 If you say Y here, you will be able to classify outgoing packets
6068 according to the route table entry they matched. If unsure, say Y.
6070 This code is also available as a module called cls_route.o ( = code
6071 which can be inserted in and removed from the running kernel
6072 whenever you want). If you want to compile it as a module, say M
6073 here and read Documentation/modules.txt.
6075 Firewall based classifier
6077 If you say Y here, you will be able to classify outgoing packets
6078 according to firewall criteria you specified.
6080 This code is also available as a module called cls_fw.o ( = code
6081 which can be inserted in and removed from the running kernel
6082 whenever you want). If you want to compile it as a module, say M
6083 here and read Documentation/modules.txt.
6087 If you say Y here, you will be able to classify outgoing packets
6088 according to their destination address. If unsure, say Y.
6090 This code is also available as a module called cls_u32.o ( = code
6091 which can be inserted in and removed from the running kernel
6092 whenever you want). If you want to compile it as a module, say M
6093 here and read Documentation/modules.txt
6095 Special RSVP classifier
6097 The Resource Reservation Protocol (RSVP) permits end systems to
6098 request a minimum and maximum data flow rate for a connection; this
6099 is important for real time data such as streaming sound or video.
6101 Say Y here if you want to be able to classify outgoing packets based
6102 on their RSVP requests.
6104 This code is also available as a module called cls_rsvp.o ( = code
6105 which can be inserted in and removed from the running kernel
6106 whenever you want). If you want to compile it as a module, say M
6107 here and read Documentation/modules.txt
6109 Special RSVP classifier for IPv6
6110 CONFIG_NET_CLS_RSVP6
6111 The Resource Reservation Protocol (RSVP) permits end systems to
6112 request a minimum and maximum data flow rate for a connection; this
6113 is important for real time data such as streaming sound or video.
6115 Say Y here if you want to be able to classify outgoing packets based
6116 on their RSVP requests and you are using the new Internet Protocol
6117 IPv6 as opposed to the older and more common IPv4.
6119 This code is also available as a module called cls_rsvp6.o ( = code
6120 which can be inserted in and removed from the running kernel
6121 whenever you want). If you want to compile it as a module, say M
6122 here and read Documentation/modules.txt
6125 # Ingres traffic policing
6126 # CONFIG_NET_CLS_POLICE
6128 ### Some expert please fill these in
6131 Network code profiler
6133 If you say Y here and to "/proc filesystem support" below, some
6134 obscure and undocumented information about the network code's
6135 performance will be written to /proc/net/profile. If you don't know
6136 what it is about, you don't need it: say N.
6138 Comtrol Hostess SV-11 support
6140 This is a network card for low speed synchronous serial links, at
6141 up to 256Kbps. It supports both PPP and Cisco HDLC.
6143 At this point, the driver can only be compiled as a module.
6145 COSA/SRP sync serial boards support
6147 This is a driver for COSA and SRP synchronous serial boards. These
6148 boards allow to connect synchronous serial devices (for example
6149 base-band modems, or any other device with the X.21, V.24, V.35 or
6150 V.36 interface) to your Linux box. The cards can work as the
6151 character device, synchronous PPP network device, or the Cisco HDLC
6154 To actually use the COSA or SRP board, you will need user-space
6155 utilities for downloading the firmware to the cards and to set them
6156 up. Look at the http://www.fi.muni.cz/~kas/cosa/ for more
6157 information about the cards (including the pointer to the user-space
6158 utilities). You can also read the comment at the top of the
6159 drivers/net/cosa.c for details about the cards and the driver
6162 The driver will be compiled as a module ( = code which can be
6163 inserted in and removed from the running kernel whenever you want).
6164 The module will be called cosa.o. For general information about
6165 modules read Documentation/modules.txt.
6167 # Fibre Channel driver support
6170 # Interphase 5526 Tachyon chipset based adaptor support
6173 Red Creek Hardware VPN (EXPERIMENTAL)
6175 This is a driver for hardware which provides a Virtual Private
6176 Network (VPN). Say Y if you have it.
6178 This code is also available as a module called rcpci.o ( = code
6179 which can be inserted in and removed from the running kernel
6180 whenever you want). If you want to compile it as a module, say M
6181 here and read Documentation/modules.txt.
6183 SBNI Leased Line Adapters
6185 This is a driver for ISA SBNI12-xx cards that is a low cost
6186 alternative to leased line modems. Say Y if you want to insert
6187 driver into kernel or say M to compile driver as a module.
6189 You can find more information and last versions of drivers and
6190 utilities at http://www.granch.ru. If you have any question you
6191 can mail to sbni@granch.ru.
6197 Say Y to this option if your Linux box contains a WAN card and you
6198 are planning to use the box as a WAN ( = Wide Area Network) router
6199 ( = device used to interconnect local area networks over wide area
6200 communication links, such as leased lines or public data networks,
6201 e.g. X.25 or frame relay) and you will be offered a list of drivers
6202 for WAN cards currently available. For more information, read
6203 Documentation/networking/wan-router.txt.
6205 Note that the answer to this question won't directly affect the
6206 kernel: saying N will just cause this configure script to skip all
6207 the questions about WAN card drivers. If unsure, say N.
6209 Sangoma WANPIPE(tm) multiprotocol cards
6210 CONFIG_VENDOR_SANGOMA
6211 WANPIPE from Sangoma Technologies Inc. (http://www.sangoma.com ) is a
6212 family of intelligent multiprotocol WAN adapters with data transfer
6213 rates up to T1 (1.544 Mbps). They are also known as Synchronous Data
6214 Link Adapters (SDLA) and designated S502E(A), S503 or S508. These
6215 cards support the X.25, Frame Relay, and PPP protocols. If you have
6216 one or more of these cards, say Y to this option; you may then also
6217 want to read the file Documentation/networking/wanpipe.txt. The next
6218 questions will ask you about the protocols you want the driver to
6221 The driver will be compiled as a module ( = code which can be
6222 inserted in and removed from the running kernel whenever you want).
6223 The module will be called wanpipe.o. For general information about
6224 modules read Documentation/modules.txt.
6226 Maximum number of cards
6227 CONFIG_WANPIPE_CARDS
6228 Enter number of WANPIPE adapters installed in your machine. The
6229 driver can support up to 8 cards. You may enter more than you
6230 actually have if you plan to add more cards in the future without
6231 re-compiling the driver, but remember that in this case you'll waste
6232 some kernel memory (about 1K per card).
6234 WANPIPE X.25 support
6236 Say Y to this option if you are planning to connect a WANPIPE card
6237 to an X.25 network. You should then also have said Y to "CCITT X.25
6238 Packet Layer" and "LAPB Data Link Driver", above. If you say N, the
6239 X.25 support will not be included in the driver (saves about 16 KB
6242 WANPIPE Frame Relay support
6244 Say Y to this option if you are planning to connect a WANPIPE card
6245 to a frame relay network. You should then also have said Y to "Frame
6246 Relay (DLCI) support", above. If you say N, the frame relay
6247 support will not be included in the driver (saves about 16 KB of
6252 Say Y to this option if you are planning to connect a WANPIPE card
6253 to a leased line using Point-to-Point protocol (PPP). You should
6254 then also have said Y to "PPP (point-to-point) support", above. If
6255 you say N, the PPP support will not be included in the driver (saves
6256 about 16 KB of kernel memory).
6258 Cyclom 2X(tm) multiprotocol cards (EXPERIMENTAL)
6259 CONFIG_CYCLADES_SYNC
6260 Cyclom 2X from Cyclades Corporation (http://www.cyclades.com and
6261 http://www.cyclades.com.br ) is an intelligent multiprotocol WAN
6262 adapter with data transfer rates up to 512 Kbps. These cards support
6263 the X.25 and SNA related protocols. If you have one or more of these
6264 cards, say Y to this option. The next questions will ask you about
6265 the protocols you want the driver to support (for now only X.25 is
6268 While no documentation is available at this time please grab the
6269 wanconfig tarball in http://www.conectiva.com.br/~acme/cycsyn-devel
6270 (with minor changes to make it compile with the current wanrouter
6271 include files; efforts are being made to use the original package
6272 available at ftp://ftp.sangoma.com ).
6274 Feel free to contact me or the cycsyn-devel mailing list at
6275 acme@conectiva.com.br and cycsyn-devel@bazar.conectiva.com.br for
6276 additional details, I hope to have documentation available as soon
6279 The driver will be compiled as a module ( = code which can be
6280 inserted in and removed from the running kernel whenever you want).
6281 The module will be called cyclomx.o. For general information about
6282 modules read Documentation/modules.txt.
6284 Cyclom 2X X.25 support
6286 Say Y to this option if you are planning to connect a Cyclom 2X card
6289 If you say N, the X.25 support will not be included in the driver
6290 (saves about 11 KB of kernel memory).
6292 Ethernet (10 or 100Mbit)
6294 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
6295 type of Local Area Network (LAN) in universities and companies.
6297 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
6298 coaxial cable, linking computers in a chain), 10BASE-T or twisted
6299 pair (10 Mbps over twisted pair cable, linking computers to central
6300 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
6301 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
6302 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
6303 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
6304 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
6305 Ethernet (1 Gbps over optical fiber or short copper links).
6307 If your Linux machine will be connected to an Ethernet and you have
6308 an Ethernet network interface card (NIC) installed in your computer,
6309 say Y here and read the Ethernet-HOWTO, available from
6310 http://metalab.unc.edu/mdw/linux.html#howto . You will then also have
6311 to say Y to the driver for your particular NIC.
6313 Note that the answer to this question won't directly affect the
6314 kernel: saying N will just cause this configure script to skip all
6315 the questions about Ethernet network cards. If unsure, say N.
6317 Sun LANCE Ethernet support
6319 This is support for lance Ethernet cards on Sun workstations such as
6320 the SPARCstation IPC (any SPARC with a network interface 'le0' under
6323 This driver is also available as a module ( = code which can be
6324 inserted in and removed from the running kernel whenever you want).
6325 The module will be called lance.o. If you want to compile it as a
6326 module, say M here and read Documentation/modules.txt.
6328 Sun Intel Ethernet support
6330 This is support for the Intel Ethernet cards on some Sun
6331 workstations (all those with a network interface 'ie0' under SunOS).
6333 Western Digital/SMC cards
6334 CONFIG_NET_VENDOR_SMC
6335 If you have a network (Ethernet) card belonging to this class, say Y
6336 and read the Ethernet-HOWTO, available from
6337 http://metalab.unc.edu/mdw/linux.html#howto .
6339 Note that the answer to this question doesn't directly affect the
6340 kernel: saying N will just cause this configure script to skip all
6341 the questions about Western Digital cards. If you say Y, you will be
6342 asked for your specific card in the following questions.
6346 If you have a network (Ethernet) card of this type, say Y and read
6347 the Ethernet-HOWTO, available from
6348 http://metalab.unc.edu/mdw/linux.html#howto .
6350 This driver is also available as a module ( = code which can be
6351 inserted in and removed from the running kernel whenever you want).
6352 The module will be called wd.o. If you want to compile it as a
6353 module, say M here and read Documentation/modules.txt as well as
6354 Documentation/networking/net-modules.txt.
6356 SMC Ultra MCA support
6358 If you have a network (Ethernet) card of this type and are running
6359 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
6360 available from http://metalab.unc.edu/mdw/linux.html#howto .
6362 This driver is also available as a module ( = code which can be
6363 inserted in and removed from the running kernel whenever you want).
6364 The module will be called smc-mca.o. If you want to compile it as a
6365 module, say M here and read Documentation/modules.txt as well as
6366 Documentation/networking/net-modules.txt.
6370 If you have a network (Ethernet) card of this type, say Y and read
6371 the Ethernet-HOWTO, available from
6372 http://metalab.unc.edu/mdw/linux.html#howto .
6374 Important: There have been many reports that, with some motherboards
6375 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
6376 such as some BusLogic models) causes corruption problems with many
6377 operating systems. The Linux smc-ultra driver has a work-around for
6378 this but keep it in mind if you have such a SCSI card and have
6381 This driver is also available as a module ( = code which can be
6382 inserted in and removed from the running kernel whenever you want).
6383 The module will be called smc-ultra.o. If you want to compile it as
6384 a module, say M here and read Documentation/modules.txt as well as
6385 Documentation/networking/net-modules.txt.
6387 SMC Ultra32 EISA support
6389 If you have a network (Ethernet) card of this type, say Y and read
6390 the Ethernet-HOWTO, available from
6391 http://metalab.unc.edu/mdw/linux.html#howto .
6393 This driver is also available as a module ( = code which can be
6394 inserted in and removed from the running kernel whenever you want).
6395 The module will be called smc-ultra32.o. If you want to compile it
6396 as a module, say M here and read Documentation/modules.txt as well
6397 as Documentation/networking/net-modules.txt.
6401 This is support for the SMC9xxx based Ethernet cards. Choose this
6402 option if you have a DELL laptop with the docking station, or
6403 another SMC9192/9194 based chipset. Say Y if you want it compiled
6404 into the kernel, and read the file
6405 Documentation/networking/smc9.txt and the Ethernet-HOWTO, available
6406 from http://metalab.unc.edu/mdw/linux.html#howto .
6408 This driver is also available as a module ( = code which can be
6409 inserted in and removed from the running kernel whenever you
6410 want). The module will be called smc9194.o. If you want to compile
6411 it as a module, say M here and read Documentation/modules.txt as
6412 well as Documentation/networking/net-modules.txt.
6416 This driver is for NE2000 compatible PCI cards. It will not work
6417 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
6418 support" below). If you have a PCI NE2000 network (Ethernet) card,
6419 say Y and read the Ethernet-HOWTO, available from
6420 http://metalab.unc.edu/mdw/linux.html#howto .
6422 This driver is also available as a module ( = code which can be
6423 inserted in and removed from the running kernel whenever you want).
6424 The module will be called ne2k-pci.o. If you want to compile it as a
6425 module, say M here and read Documentation/modules.txt as well as
6426 Documentation/networking/net-modules.txt.
6430 This driver is for DM9102 compatible PCI cards from Davicom
6431 (http://www.davicom.com.tw)
6432 If you have a PCI DM9102 network (Ethernet) card, say Y.
6434 This driver is also available as a module ( = code which can be
6435 inserted in and removed from the running kernel whenever you want).
6436 The module will be called dmfe.o. If you want to compile it as a
6437 module, say M here and read Documentation/modules.txt as well as
6438 Documentation/networking/net-modules.txt.
6440 Racal-Interlan (Micom) NI cards
6441 CONFIG_NET_VENDOR_RACAL
6442 If you have a network (Ethernet) card belonging to this class, such
6443 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
6444 available from http://metalab.unc.edu/mdw/linux.html#howto .
6446 Note that the answer to this question doesn't directly affect the
6447 kernel: saying N will just cause this configure script to skip all
6448 the questions about NI cards. If you say Y, you will be asked for
6449 your specific card in the following questions.
6451 NI5010 support (EXPERIMENTAL)
6453 If you have a network (Ethernet) card of this type, say Y and read
6454 the Ethernet-HOWTO, available from
6455 http://metalab.unc.edu/mdw/linux.html#howto . Note that this is still
6458 This driver is also available as a module ( = code which can be
6459 inserted in and removed from the running kernel whenever you want).
6460 The module will be called ni5010.o. If you want to compile it as a
6461 module, say M here and read Documentation/modules.txt as well as
6462 Documentation/networking/net-modules.txt.
6466 If you have a network (Ethernet) card of this type, say Y and read
6467 the Ethernet-HOWTO, available from
6468 http://metalab.unc.edu/mdw/linux.html#howto .
6470 This driver is also available as a module ( = code which can be
6471 inserted in and removed from the running kernel whenever you want).
6472 The module will be called ni52.o. If you want to compile it as a
6473 module, say M here and read Documentation/modules.txt as well as
6474 Documentation/networking/net-modules.txt.
6478 If you have a network (Ethernet) card of this type, say Y and read
6479 the Ethernet-HOWTO, available from
6480 http://metalab.unc.edu/mdw/linux.html#howto .
6482 This driver is also available as a module ( = code which can be
6483 inserted in and removed from the running kernel whenever you want).
6484 The module will be called ni65.o. If you want to compile it as a
6485 module, say M here and read Documentation/modules.txt as well as
6486 Documentation/networking/net-modules.txt.
6488 RealTek 8129/8139 (not 8019/8029!) support
6490 This is a driver for the Fast Ethernet PCI network cards based on
6491 the RTL8129 and RTL8139 chips. If you have one of those, say Y and
6492 read the Ethernet-HOWTO, available from
6493 http://metalab.unc.edu/mdw/linux.html#howto .
6495 If you want to compile this driver as a module ( = code which can be
6496 inserted in and removed from the running kernel whenever you want),
6497 say M here and read Documentation/modules.txt. This is recommended.
6498 The module will be called rtl8139.o.
6500 SiS 900 PCI Fast Ethernet Adapter support
6502 This is a driver for the Fast Ethernet PCI network cards based on
6503 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
6504 SiS 630 and SiS 540 chipsets. If you have one of those, say Y and
6505 read the Ethernet-HOWTO, available via FTP (user: anonymous) in
6506 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Please read
6507 Documentation/networking/sis900.txt and comments at the beginning
6508 of drivers/net/sis900.c for more information.
6510 This driver also supports AMD 79C901 HomePNA such that you can use
6511 your phone line as network cable.
6513 If you want to compile this driver as a module ( = code which can be
6514 inserted in and removed from the running kernel whenever you want),
6515 say M here and read Documentation/modules.txt. This is recommended.
6516 The module will be called sis900.o.
6518 Packet Engines Yellowfin Gigabit-NIC support
6520 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
6521 adapter. This adapter is used by the Beowulf Linux cluster project.
6522 See http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html for
6523 more information about this driver in particular and Beowulf in
6526 If you want to compile this driver as a module ( = code which can be
6527 inserted in and removed from the running kernel whenever you want),
6528 say M here and read Documentation/modules.txt. This is recommended.
6529 The module will be called yellowfin.o.
6531 General Instruments Surfboard 1000
6533 This is a driver for the General Instrument (also known as
6534 NextLevel) SURFboard 1000 internal
6535 cable modem. This is an ISA card which is used by a number of cable
6536 TV companies to provide cable modem access. It's a one-way
6537 downstream-only cable modem, meaning that your upstream net link is
6538 provided by your regular phone modem.
6540 At present this driver only compiles as a module, so say M here if
6541 you have this card. The module will be called sb1000.o. Then read
6542 Documentation/networking/README.sb1000 for information on how to use
6543 this module, as it needs special ppp scripts for establishing a
6544 connection. Further documentation and the necessary scripts can be
6547 http://www.jacksonville.net/~fventuri/
6548 http://home.adelphia.net/~siglercm/sb1000.html
6549 http://linuxpower.cx/~cable/
6551 If you don't have this card, of course say N.
6553 Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support
6555 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
6556 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
6557 adapter. The driver allows for using the Jumbo Frame option (9000
6558 bytes/frame) however it requires that your switches can handle this
6559 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
6562 If you want to compile this driver as a module ( = code which can be
6563 inserted in and removed from the running kernel whenever you want),
6564 say M here and read Documentation/modules.txt. This is recommended.
6565 The module will be called acenic.o.
6567 Omit support for older Tigon I based AceNICs
6568 CONFIG_ACENIC_OMIT_TIGON_I
6569 Say Y here if you only have Tigon II based AceNICs and want to leave
6570 out support for the older Tigon I based cards which are no longer
6571 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
6572 version)). This will reduce the size of the driver object by
6573 app. 100KB. If you are not sure whether your card is a Tigon I or a
6574 Tigon II, say N here.
6576 The safe and default value for this is N.
6578 SysKonnect SK-98xx support
6580 Say Y here if you have a SysKonnect SK-98xx Gigabit Ethernet Server
6581 Adapter. The following adapters are supported by this driver:
6582 - SK-9841 (single link 1000Base-LX)
6583 - SK-9842 (dual link 1000Base-LX)
6584 - SK-9843 (single link 1000Base-SX)
6585 - SK-9844 (dual link 1000Base-SX)
6586 - SK-9821 (single link 1000Base-T)
6587 - SK-9822 (dual link 1000Base-T)
6588 The dual link adapters support a link-failover feature.
6589 Read Documentation/networking/sk98lin.txt for information about
6590 optional driver parameters.
6591 Questions concerning this driver may be addresse to:
6594 If you want to compile this driver 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. This is recommended.
6597 The module will be called sk98lin.o.
6599 AMD LANCE and PCnet (AT1500 and NE2100) support
6601 If you have a network (Ethernet) card of this type, say Y and read
6602 the Ethernet-HOWTO, available from
6603 http://metalab.unc.edu/mdw/linux.html#howto . Some LinkSys cards are
6606 If you want to compile this driver as a module ( = code which can be
6607 inserted in and removed from the running kernel whenever you want),
6608 say M here and read Documentation/modules.txt. This is recommended.
6609 The module will be called lance.o.
6612 CONFIG_NET_VENDOR_3COM
6613 If you have a network (Ethernet) card belonging to this class, say Y
6614 and read the Ethernet-HOWTO, available from
6615 http://metalab.unc.edu/mdw/linux.html#howto .
6617 Note that the answer to this question doesn't directly affect the
6618 kernel: saying N will just cause this configure script to skip all
6619 the questions about 3COM cards. If you say Y, you will be asked for
6620 your specific card in the following questions.
6624 If you have a network (Ethernet) card of this type, say Y and read
6625 the Ethernet-HOWTO, available from
6626 http://metalab.unc.edu/mdw/linux.html#howto . Also, consider buying a
6627 new card, since the 3c501 is slow, broken, and obsolete: you will
6628 have problems. Some people suggest to ping ("man ping") a nearby
6629 machine every minute ("man cron") when using this card.
6631 This driver is also available as a module ( = code which can be
6632 inserted in and removed from the running kernel whenever you want).
6633 The module will be called 3c501.o. If you want to compile it as a
6634 module, say M here and read Documentation/modules.txt as well as
6635 Documentation/networking/net-modules.txt.
6639 If you have a network (Ethernet) card of this type, say Y and read
6640 the Ethernet-HOWTO, available from
6641 http://metalab.unc.edu/mdw/linux.html#howto .
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 3c503.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.
6651 Information about this network (Ethernet) card can be found in
6652 Documentation/networking/3c505.txt. If you have a card of this type,
6653 say Y and read the Ethernet-HOWTO, available from
6654 http://metalab.unc.edu/mdw/linux.html#howto .
6656 If you want to compile this as a module ( = code which can be
6657 inserted in and removed from the running kernel whenever you want),
6658 say M here and read Documentation/modules.txt as well as
6659 Documentation/networking/net-modules.txt. The module will be called
6662 3c507 support (EXPERIMENTAL)
6664 If you have a network (Ethernet) card of this type, say Y and read
6665 the Ethernet-HOWTO, available from
6666 http://metalab.unc.edu/mdw/linux.html#howto .
6668 This driver is also available as a module ( = code which can be
6669 inserted in and removed from the running kernel whenever you want).
6670 The module will be called 3c507.o. If you want to compile it as a
6671 module, say M here and read Documentation/modules.txt as well as
6672 Documentation/networking/net-modules.txt.
6676 If you have a network (Ethernet) card of this type, say Y and read
6677 the Ethernet-HOWTO, available from
6678 http://metalab.unc.edu/mdw/linux.html#howto .
6680 This driver is also available as a module ( = code which can be
6681 inserted in and removed from the running kernel whenever you want).
6682 The module will be called 3c523.o. If you want to compile it as a
6683 module, say M here and read Documentation/modules.txt as well as
6684 Documentation/networking/net-modules.txt.
6688 If you have a network (Ethernet) card of this type, say Y and read
6689 the Ethernet-HOWTO, available from
6690 http://metalab.unc.edu/mdw/linux.html#howto .
6692 This driver is also available as a module ( = code which can be
6693 inserted in and removed from the running kernel whenever you want).
6694 The module will be called 3c527.o. If you want to compile it as a
6695 module, say M here and read Documentation/modules.txt as well as
6696 Documentation/networking/net-modules.txt.
6700 If you have a network (Ethernet) card belonging to the 3Com
6701 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
6702 from http://metalab.unc.edu/mdw/linux.html#howto .
6704 If your card is not working you may need to use the DOS
6705 setup disk to disable Plug & Play mode, and to select the default
6708 If you want to compile this as a module ( = code which can be
6709 inserted in and removed from the running kernel whenever you want),
6710 say M here and read Documentation/modules.txt as well as
6711 Documentation/networking/net-modules.txt. The module will be called
6714 3c590 series (592/595/597) "Vortex" support
6716 If you have a 3Com "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597)
6717 or "Boomerang" series (EtherLink XL 3c900 or 3c905) network
6718 (Ethernet) card, say Y and read the Ethernet-HOWTO, available from
6719 http://metalab.unc.edu/mdw/linux.html#howto . More specific
6720 information is in Documentation/networking/vortex.txt and in the
6721 comments at the beginning of drivers/net/3c59x.c.
6723 If you want to compile this as a module ( = code which can be
6724 inserted in and removed from the running kernel whenever you want),
6725 say M here and read Documentation/modules.txt as well as
6726 Documentation/networking/net-modules.txt.
6730 If your network (Ethernet) card hasn't been mentioned yet and its
6731 bus system (that's the way the cards talks to the other components
6732 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
6733 Make sure you know the name of your card. Read the Ethernet-HOWTO,
6734 available from http://metalab.unc.edu/mdw/linux.html#howto .
6738 Note that the answer to this question doesn't directly affect the
6739 kernel: saying N will just cause this configure script to skip all
6740 the remaining ISA network card questions. If you say Y, you will be
6741 asked for your specific card in the following questions.
6743 Generic ARCnet support
6745 If you have a network card of this type, say Y and check out the
6746 (arguably) beautiful poetry in Documentation/networking/arcnet.txt.
6748 You need both this driver, and the driver for the particular ARCnet
6749 chipset of your card. If you don't know, then it's probably a
6750 COM90xx type card, so say Y (or M) to "ARCnet COM90xx chipset
6753 You might also want to have a look at the Ethernet-HOWTO, available
6754 from http://metalab.unc.edu/mdw/linux.html#howto (even though ARCnet
6755 is not really Ethernet).
6757 This driver is also available as a module ( = code which can be
6758 inserted in and removed from the running kernel whenever you want).
6759 The module will be called arcnet.o. If you want to compile it as a
6760 module, say M here and read Documentation/modules.txt as well as
6761 Documentation/networking/net-modules.txt.
6763 Enable arc0e (ARCnet "ether-encap" packet format)
6765 This allows you to use "Ethernet encapsulation" with your ARCnet
6766 card via the virtual arc0e device. You only need arc0e if you want
6767 to talk to nonstandard ARCnet software, specifically,
6768 DOS/Windows-style "NDIS" drivers. You do not need to say Y here to
6769 communicate with industry-standard RFC1201 implementations, like the
6770 arcether.com packet driver or most DOS/Windows ODI drivers. RFC1201
6771 is included automatically as the arc0 device. Please read the
6772 ARCnet documentation in Documentation/networking/arcnet.txt for more
6773 information about using arc0e and arc0s.
6775 Enable arc0s (ARCnet RFC1051 packet format)
6777 This allows you to use RFC1051 with your ARCnet card via the virtual
6778 arc0s device. You only need arc0s if you want to talk to ARCnet
6779 software complying with the "old" standard, specifically, the DOS
6780 arcnet.com packet driver, Amigas running AmiTCP, and some variants
6781 of NetBSD. You do not need to say Y here to communicate with
6782 industry-standard RFC1201 implementations, like the arcether.com
6783 packet driver or most DOS/Windows ODI drivers. RFC1201 is included
6784 automatically as the arc0 device. Please read the ARCnet
6785 documentation in Documentation/networking/arcnet.txt for more
6786 information about using arc0e and arc0s.
6788 ARCnet COM90xx (normal) chipset driver
6789 CONFIG_ARCNET_COM90xx
6790 This is the chipset driver for the standard COM90xx cards. If you
6791 have always used the old ARCnet driver without knowing what type of
6792 card you had, this is probably the one for you.
6794 This driver is also available as a module ( = code which can be
6795 inserted in and removed from the running kernel whenever you want).
6796 The module will be called com90xx.o. If you want to compile it as a
6797 module, say M here and read Documentation/modules.txt as well as
6798 Documentation/networking/net-modules.txt.
6800 ARCnet COM90xx (IO mapped) chipset driver
6801 CONFIG_ARCNET_COM90xxIO
6802 This is the chipset driver for the COM90xx cards, using them in
6803 IO-mapped mode instead of memory-mapped mode. This is slower than
6804 the normal driver. Only use it if your card doesn't support shared
6807 This driver is also available as a module ( = code which can be
6808 inserted in and removed from the running kernel whenever you want).
6809 The module will be called com90io.o. If you want to compile it as a
6810 module, say M here and read Documentation/modules.txt as well as
6811 Documentation/networking/net-modules.txt.
6813 ARCnet COM90xx (RIM I) chipset driver
6815 This is yet another chipset driver for the COM90xx cards, but this
6816 time only using memory-mapped mode, and no IO ports at all. This
6817 driver is completely untested, so if you have one of these cards,
6818 please mail David.Woodhouse@mvhi.com, especially if it works!
6820 This driver is also available as a module ( = code which can be
6821 inserted in and removed from the running kernel whenever you
6822 want). The module will be called arc-rimi.o. If you want to compile
6823 it as a module, say M here and read Documentation/modules.txt as
6824 well as Documentation/networking/net-modules.txt.
6826 ARCnet COM20020 chipset driver
6827 CONFIG_ARCNET_COM20020
6828 This is the driver for the new COM20020 chipset. It supports such
6829 things as promiscuous mode, so packet sniffing is possible, and
6830 extra diagnostic information.
6832 This driver is also available as a module ( = code which can be
6833 inserted in and removed from the running kernel whenever you want).
6834 The module will be called com20020.o. If you want to compile it as a
6835 module, say M here and read Documentation/modules.txt as well as
6836 Documentation/networking/net-modules.txt.
6838 Cabletron E21xx support
6840 If you have a network (Ethernet) card of this type, say Y and read
6841 the Ethernet-HOWTO, available from
6842 http://metalab.unc.edu/mdw/linux.html#howto .
6844 This driver is also available as a module ( = code which can be
6845 inserted in and removed from the running kernel whenever you want).
6846 The module will be called e2100.o. If you want to compile it as a
6847 module, say M here and read Documentation/modules.txt as well as
6848 Documentation/networking/net-modules.txt.
6852 Support for CS89x0 chipset based Ethernet cards. If you have a
6853 network (Ethernet) card of this type, say Y and read the
6854 Ethernet-HOWTO, available from
6855 http://metalab.unc.edu/mdw/linux.html#howto as well as
6856 Documentation/networking/cs89x0.txt.
6858 If you want to compile this as a module ( = code which can be
6859 inserted in and removed from the running kernel whenever you want),
6860 say M here and read Documentation/modules.txt as well as
6861 Documentation/networking/net-modules.txt. The module will be called
6866 If you have a network (Ethernet) card of this type, say Y and read
6867 the Ethernet-HOWTO, available from
6868 http://metalab.unc.edu/mdw/linux.html#howto as well as
6869 drivers/net/depca.c.
6871 If you want to compile this as a module ( = code which can be
6872 inserted in and removed from the running kernel whenever you want),
6873 say M here and read Documentation/modules.txt as well as
6874 Documentation/networking/net-modules.txt. The module will be called
6877 EtherWorks 3 support
6879 This driver supports the DE203, DE204 and DE205 network (Ethernet)
6880 cards. If this is for you, say Y and read
6881 Documentation/networking/ewrk3.txt in the kernel source as well as
6882 the Ethernet-HOWTO, available from
6883 http://metalab.unc.edu/mdw/linux.html#howto .
6885 If you want to compile this as a module ( = code which can be
6886 inserted in and removed from the running kernel whenever you want),
6887 say M here and read Documentation/modules.txt as well as
6888 Documentation/networking/net-modules.txt. The module will be called
6893 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
6894 is for you, read the Ethernet-HOWTO, available from
6895 http://metalab.unc.edu/mdw/linux.html#howto .
6897 If you want to compile this as a module ( = code which can be
6898 inserted in and removed from the running kernel whenever you want),
6899 say M here and read Documentation/modules.txt as well as
6900 Documentation/networking/net-modules.txt. The module will be called
6905 If you have a network (Ethernet) card of this type, say Y and read
6906 the Ethernet-HOWTO, available from
6907 http://metalab.unc.edu/mdw/linux.html#howto .
6909 This driver is also available as a module ( = code which can be
6910 inserted in and removed from the running kernel whenever you want).
6911 If you want to compile it as a module, say M here and read
6912 Documentation/modules.txt as well as
6913 Documentation/networking/net-modules.txt. The module will be called
6916 FMV-181/182/183/184 support
6918 If you have a Fujitsu FMV-181/182/183/184 network (Ethernet) card,
6919 say Y and read the Ethernet-HOWTO, available from
6920 http://metalab.unc.edu/mdw/linux.html#howto .
6922 If you use an FMV-183 or FMV-184 and it is not working, you may need
6923 to disable Plug & Play mode of the card.
6925 This driver is also available as a module ( = code which can be
6926 inserted in and removed from the running kernel whenever you want).
6927 The module will be called fmv18x.o. If you want to compile it as a
6928 module, say M here and read Documentation/modules.txt as well as
6929 Documentation/networking/net-modules.txt.
6931 EtherExpress PRO support
6933 If you have a network (Ethernet) card of this type, say Y. Note
6934 however that the EtherExpress PRO/100 Ethernet card has its own
6935 separate driver. Please read the Ethernet-HOWTO, available from
6936 http://metalab.unc.edu/mdw/linux.html#howto .
6938 This driver is also available as a module ( = code which can be
6939 inserted in and removed from the running kernel whenever you want).
6940 The module will be called eepro.o. If you want to compile it as a
6941 module, say M here and read Documentation/modules.txt as well as
6942 Documentation/networking/net-modules.txt.
6944 EtherExpress support
6946 If you have an EtherExpress16 network (Ethernet) card, say Y and
6947 read the Ethernet-HOWTO, available from
6948 http://metalab.unc.edu/mdw/linux.html#howto . Note that the Intel
6949 EtherExpress16 card used to be regarded as a very poor choice
6950 because the driver was very unreliable. We now have a new driver
6951 that should do better.
6953 If you want to compile this driver as a module ( = code which can be
6954 inserted in and removed from the running kernel whenever you want),
6955 say M here and read Documentation/modules.txt as well as
6956 Documentation/networking/net-modules.txt. The module will be called
6959 HP PCLAN+ (27247B and 27252A) support
6961 If you have a network (Ethernet) card of this type, say Y and read
6962 the Ethernet-HOWTO, available from
6963 http://metalab.unc.edu/mdw/linux.html#howto .
6965 This driver is also available as a module ( = code which can be
6966 inserted in and removed from the running kernel whenever you want).
6967 The module will be called hp-plus.o. If you want to compile it as a
6968 module, say M here and read Documentation/modules.txt as well as
6969 Documentation/networking/net-modules.txt.
6971 HP PCLAN (27245 and other 27xxx series) support
6973 If you have a network (Ethernet) card of this type, say Y and read
6974 the Ethernet-HOWTO, available from
6975 http://metalab.unc.edu/mdw/linux.html#howto .
6977 This driver is also available as a module ( = code which can be
6978 inserted in and removed from the running kernel whenever you want).
6979 The module will be called hp.o. If you want to compile it as a
6980 module, say M here and read Documentation/modules.txt as well as
6981 Documentation/networking/net-modules.txt.
6983 HP 10/100VG PCLAN (ISA, EISA, PCI) support
6985 If you have a network (Ethernet) card of this type, say Y and read
6986 the Ethernet-HOWTO, available from
6987 http://metalab.unc.edu/mdw/linux.html#howto .
6989 If you want to compile this as a module ( = code which can be
6990 inserted in and removed from the running kernel whenever you want),
6991 say M here and read Documentation/modules.txt as well as
6992 Documentation/networking/net-modules.txt. The module will be called
6995 NE2000/NE1000 support
6997 If you have a network (Ethernet) card of this type, say Y and read
6998 the Ethernet-HOWTO, available from
6999 http://metalab.unc.edu/mdw/linux.html#howto . Many Ethernet cards
7000 without a specific driver are compatible with NE2000.
7002 If you have a PCI NE2000 card however, say N here and Y to "PCI
7003 NE2000 support", above. If you have a NE2000 card and are running on
7004 an MCA system (a bus system used on some IBM PS/2 computers and
7005 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
7008 This driver is also available as a module ( = code which can be
7009 inserted in and removed from the running kernel whenever you want).
7010 The module will be called ne.o. If you want to compile it as a
7011 module, say M here and read Documentation/modules.txt as well as
7012 Documentation/networking/net-modules.txt.
7016 If you have a network (Ethernet) card of this type, say Y and read
7017 the Ethernet-HOWTO, available from
7018 http://metalab.unc.edu/mdw/linux.html#howto .
7020 NE/2 (ne2000 MCA version) support
7022 If you have a network (Ethernet) card of this type, say Y and read
7023 the Ethernet-HOWTO, available from
7024 http://metalab.unc.edu/mdw/linux.html#howto .
7026 This driver is also available as a module ( = code which can be
7027 inserted in and removed from the running kernel whenever you want).
7028 The module will be called ne2.o. If you want to compile it as a
7029 module, say M here and read Documentation/modules.txt as well as
7030 Documentation/networking/net-modules.txt.
7034 These are Micro Channel ethernet adapters. You need to say Y to "MCA
7035 support" in order to use this driver. Supported cards are the SKnet
7036 Junior MC2 and the SKnet MC2(+). The driver automatically
7037 distinguishes between the two cards. Note that using multiple boards
7038 of different type hasn't been tested with this driver. Say Y if you
7039 have one of these ethernet adapters.
7041 This driver is also available as a module ( = code which can be
7042 inserted in and removed from the running kernel whenever you want).
7043 The module is called sk_mca.o. If you want to compile it as a
7044 module, say M here and read Documentation/modules.txt as well as
7045 Documentation/networking/net-modules.txt.
7047 EISA, VLB, PCI and on board controllers
7049 This is another class of network cards which attach directly to the
7050 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
7051 available from http://metalab.unc.edu/mdw/linux.html#howto .
7053 Note that the answer to this question doesn't directly affect the
7054 kernel: saying N will just cause this configure script to skip all
7055 the questions about this class of network cards. If you say Y, you
7056 will be asked for your specific card in the following questions. If
7057 you are unsure, say Y.
7059 AMD PCnet32 (VLB and PCI) support
7061 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
7062 answer Y here and read the Ethernet-HOWTO, available from
7063 http://metalab.unc.edu/mdw/linux.html#howto .
7065 This driver is also available as a module ( = code which can be
7066 inserted in and removed from the running kernel whenever you want).
7067 The module will be called pcnet32.o. If you want to compile it as a
7068 module, say M here and read Documentation/modules.txt as well as
7069 Documentation/networking/net-modules.txt.
7071 Ansel Communications EISA 3200 support
7073 If you have a network (Ethernet) card of this type, say Y and read
7074 the Ethernet-HOWTO, available from
7075 http://metalab.unc.edu/mdw/linux.html#howto .
7077 This driver is also available as a module ( = code which can be
7078 inserted in and removed from the running kernel whenever you want).
7079 The module will be called ac3200.o. If you want to compile it as a
7080 module, say M here and read Documentation/modules.txt as well as
7081 Documentation/networking/net-modules.txt.
7083 Mylex EISA LNE390A/LNE390B support (EXPERIMENTAL)
7085 If you have a network (Ethernet) card of this type, say Y and read
7086 the Ethernet-HOWTO, available from
7087 http://metalab.unc.edu/mdw/linux.html#howto .
7089 This driver is also available as a module ( = code which can be
7090 inserted in and removed from the running kernel whenever you want).
7091 The module will be called lne390.o. If you want to compile it as a
7092 module, say M here and read Documentation/modules.txt as well as
7093 Documentation/networking/net-modules.txt.
7095 Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)
7097 If you have a network (Ethernet) card of this type, say Y and read
7098 the Ethernet-HOWTO, available from
7099 http://metalab.unc.edu/mdw/linux.html#howto . Note that this driver
7100 will NOT WORK for NE3200 cards as they are completely different.
7102 This driver is also available as a module ( = code which can be
7103 inserted in and removed from the running kernel whenever you want).
7104 The module will be called ne3210.o. If you want to compile it as a
7105 module, say M here and read Documentation/modules.txt as well as
7106 Documentation/networking/net-modules.txt.
7108 Apricot Xen-II on board Ethernet
7110 If you have a network (Ethernet) controller of this type, say Y and
7111 read the Ethernet-HOWTO, available from
7112 http://metalab.unc.edu/mdw/linux.html#howto .
7114 If you want to compile this as a module ( = code which can be
7115 inserted in and removed from the running kernel whenever you want),
7116 say M here and read Documentation/modules.txt as well as
7117 Documentation/networking/net-modules.txt. The module will be called
7120 Generic DECchip & DIGITAL EtherWORKS PCI/EISA
7122 This is support for the DIGITAL series of PCI/EISA Ethernet cards.
7123 These include the DE425, DE434, DE435, DE450 and DE500 models. If
7124 you have a network card of this type, say Y and read the
7125 Ethernet-HOWTO, available from
7126 http://metalab.unc.edu/mdw/linux.html#howto . More specific
7127 information is contained in Documentation/networking/de4x5.txt.
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 de4x5.o. If you want to compile it as a
7132 module, say M here and read Documentation/modules.txt as well as
7133 Documentation/networking/net-modules.txt.
7135 DECchip Tulip (dc21x4x) PCI support
7137 This driver is developed for the SMC EtherPower series Ethernet
7138 cards and also works with cards based on the DECchip
7139 21040/21041/21140 (Tulip series) chips. Some LinkSys PCI cards are
7140 of this type. (If your card is NOT SMC EtherPower 10/100 PCI
7141 (smc9332dst), you can also try the driver for "Generic DECchip"
7142 cards, above. However, most people with a network card of this type
7143 will say Y here.) Do read the Ethernet-HOWTO, available from
7144 http://metalab.unc.edu/mdw/linux.html#howto . More specific
7145 information is contained in Documentation/networking/tulip.txt.
7147 This driver is also available as a module ( = code which can be
7148 inserted in and removed from the running kernel whenever you want).
7149 The module will be called tulip.o. If you want to compile it as a
7150 module, say M here and read Documentation/modules.txt as well as
7151 Documentation/networking/net-modules.txt.
7153 Digi Intl. RightSwitch support
7155 This is support for the Digi International RightSwitch series of
7156 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
7157 models. If you have a network card of this type, say Y and read the
7158 Ethernet-HOWTO, available from
7159 http://metalab.unc.edu/mdw/linux.html#howto . More specific
7160 information is contained in Documentation/networking/dgrs.txt.
7162 This driver is also available as a module ( = code which can be
7163 inserted in and removed from the running kernel whenever you want).
7164 The module will be called dgrs.o. If you want to compile it as a
7165 module, say M here and read Documentation/modules.txt as well as
7166 Documentation/networking/net-modules.txt.
7168 EtherExpress PRO/100 support
7169 CONFIG_EEXPRESS_PRO100
7170 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
7171 card, say Y and read the Ethernet-HOWTO, available from
7172 http://metalab.unc.edu/mdw/linux.html#howto .
7174 This driver is also available as a module ( = code which can be
7175 inserted in and removed from the running kernel whenever you want).
7176 The module will be called eepro100.o. If you want to compile it as a
7177 module, say M here and read Documentation/modules.txt as well as
7178 Documentation/networking/net-modules.txt.
7180 ICL EtherTeam 16i/32 support (EXPERIMENTAL)
7182 If you have a network (Ethernet) card of this type, say Y and read
7183 the Ethernet-HOWTO, available from
7184 http://metalab.unc.edu/mdw/linux.html#howto .
7186 This driver is also available as a module ( = code which can be
7187 inserted in and removed from the running kernel whenever you want).
7188 The module will be called eth16i.o. If you want to compile it as a
7189 module, say M here and read Documentation/modules.txt as well as
7190 Documentation/networking/net-modules.txt.
7192 TI ThunderLAN support (EXPERIMENTAL)
7194 If you have a PCI Ethernet network card based on the ThunderLAN chip
7195 which is supported by this driver, say Y and read the
7196 Ethernet-HOWTO, available from
7197 http://metalab.unc.edu/mdw/linux.html#howto .
7199 Devices currently supported by this driver are Compaq Netelligent,
7200 Compaq NetFlex and Olicom cards. Please read the file
7201 Documentation/networking/tlan.txt for more details.
7203 This driver is also available as a module ( = code which can be
7204 inserted in and removed from the running kernel whenever you want).
7205 The module will be called tlan.o. If you want to compile it as a
7206 module, say M here and read Documentation/modules.txt as well as
7207 Documentation/networking/net-modules.txt.
7209 Please email feedback to james.banks@caldera.com.
7213 If you have a VIA "rhine" based network card (Rhine-I (3043) or
7214 Rhine-2 (VT86c100A)), say Y here.
7216 This driver is also available as a module ( = code which can be
7217 inserted in and removed from the running kernel whenever you want).
7218 The module will be called via-rhine.o. If you want to compile it as
7219 a module, say M here and read Documentation/modules.txt as well as
7220 Documentation/networking/net-modules.txt.
7222 Racal-Interlan EISA ES3210 support (EXPERIMENTAL)
7224 If you have a network (Ethernet) card of this type, say Y and read
7225 the Ethernet-HOWTO, available from
7226 http://metalab.unc.edu/mdw/linux.html#howto .
7228 This driver is also available as a module ( = code which can be
7229 inserted in and removed from the running kernel whenever you want).
7230 The module will be called es3210.o. If you want to compile it as a
7231 module, say M here and read Documentation/modules.txt as well as
7232 Documentation/networking/net-modules.txt.
7234 SMC EtherPower II (EXPERIMENTAL)
7236 If you have an SMC EtherPower II 9432 PCI Ethernet network card
7237 which is based on the SMC83c170, say Y and read the Ethernet-HOWTO,
7238 available from http://metalab.unc.edu/mdw/linux.html#howto .
7240 This driver is also available as a module ( = code which can be
7241 inserted in and removed from the running kernel whenever you want).
7242 The module will be called epic100.o. If you want to compile it as a
7243 module, say M here and read Documentation/modules.txt as well as
7244 Documentation/networking/net-modules.txt.
7246 SGI Seeq ethernet controller support
7248 Say Y here if you have an Seeq based Ethernet network card. This is
7249 used in many Silicon Graphics machines.
7251 Zenith Z-Note support (EXPERIMENTAL)
7253 The Zenith Z-Note notebook computer has a built-in network
7254 (Ethernet) card, and this is the Linux driver for it. Note that the
7255 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
7256 by this driver. Read the Ethernet-HOWTO, available from
7257 http://metalab.unc.edu/mdw/linux.html#howto .
7259 Adaptec Starfire support
7260 CONFIG_ADAPTEC_STARFIRE
7261 If you have an Ethernet network card like this, say Y and read the
7262 Ethernet-HOWTO, available from
7263 http://metalab.unc.edu/mdw/linux.html#howto .
7265 This driver is also available as a module ( = code which can be
7266 inserted in and removed from the running kernel whenever you want).
7267 The module will be called starfire.o. If you want to compile it as a
7268 module, say M here and read Documentation/modules.txt as well as
7269 Documentation/networking/net-modules.txt.
7271 Pocket and portable adapters
7273 Cute little network (Ethernet) devices which attach to the parallel
7274 port ("pocket adapters"), commonly used with laptops. If you have
7275 one of those, say Y and read the Ethernet-HOWTO, available from
7276 http://metalab.unc.edu/mdw/linux.html#howto .
7278 If you want to plug a network (or some other) card into the PCMCIA
7279 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
7280 credit card size extension cards used by all modern laptops), you
7281 need the pcmcia-cs package (location contained in the file
7282 Documentation/Changes) and you can say N here.
7284 Laptop users should read the Linux Laptop home page at
7285 http://www.cs.utexas.edu/users/kharker/linux-laptop/ .
7287 Note that the answer to this question doesn't directly affect the
7288 kernel: saying N will just cause this configure script to skip all
7289 the questions about this class of network devices. If you say Y, you
7290 will be asked for your specific device in the following questions.
7292 AT-LAN-TEC/RealTek pocket adapter support
7294 This is a network (Ethernet) device which attaches to your parallel
7295 port. Read drivers/net/atp.c as well as the Ethernet-HOWTO,
7296 available from http://metalab.unc.edu/mdw/linux.html#howto , if you
7297 want to use this. If you intend to use this driver, you should have
7298 said N to the Parallel Printer support, because the two drivers
7299 don't like each other.
7301 D-Link DE600 pocket adapter support
7303 This is a network (Ethernet) device which attaches to your parallel
7304 port. Read Documentation/networking/DLINK.txt as well as the
7305 Ethernet-HOWTO, available from
7306 http://metalab.unc.edu/mdw/linux.html#howto , if you want to use
7307 this. It is possible to have several devices share a single parallel
7308 port and it is safe to compile the corresponding drivers into the
7311 If you want to compile this driver as a module however ( = code
7312 which can be inserted in and removed from the running kernel
7313 whenever you want), say M here and read Documentation/modules.txt.
7314 The module will be called de600.o.
7316 D-Link DE620 pocket adapter support
7318 This is a network (Ethernet) device which attaches to your parallel
7319 port. Read Documentation/networking/DLINK.txt as well as the
7320 Ethernet-HOWTO, available from
7321 http://metalab.unc.edu/mdw/linux.html#howto , if you want to use
7322 this. It is possible to have several devices share a single parallel
7323 port and it is safe to compile the corresponding drivers into the
7326 If you want to compile this driver as a module however ( = code
7327 which can be inserted in and removed from the running kernel
7328 whenever you want), say M here and read Documentation/modules.txt.
7329 The module will be called de620.o.
7331 Token Ring driver support
7333 Token Ring is IBM's way of communication on a local network; the
7334 rest of the world uses Ethernet. To participate on a Token Ring
7335 network, you need a special Token ring network card. If you are
7336 connected to such a Token Ring network and want to use your Token
7337 Ring card under Linux, say Y here and to the driver for your
7338 particular card below and read the Token-Ring mini-HOWTO, available
7339 from http://metalab.unc.edu/mdw/linux.html#howto . Most people can
7342 IBM Tropic chipset based adapter support
7344 This is support for all IBM Token Ring cards that don't use DMA. If
7345 you have such a beast, say Y and read the Token-Ring mini-HOWTO,
7346 available from http://metalab.unc.edu/mdw/linux.html#howto .
7348 Warning: this driver will almost definitely fail if more than one
7349 active Token Ring card is present.
7351 This driver is also available as a module ( = code which can be
7352 inserted in and removed from the running kernel whenever you want).
7353 The module will be called ibmtr.o. If you want to compile it as a
7354 module, say M here and read Documentation/modules.txt.
7356 IBM Olympic chipset PCI adapter support
7358 This is support for all non-Lanstreamer IBM PCI Token Ring Cards.
7359 Specifically this is all IBM PCI, PCI Wake On Lan, PCI II, PCI II
7360 Wake On Lan, and PCI 100/16/4 adapters.
7362 If you have such an adapter, say Y and read the Token-Ring
7363 mini-HOWTO, available from
7364 http://metalab.unc.edu/mdw/linux.html#howto .
7366 This driver is also available as a module ( = code which can be
7367 inserted in and removed from the running kernel whenever you want).
7368 The module will will be called olympic.o. If you want to compile it
7369 as a module, say M here and read Documentation/modules.txt.
7371 Also read the file Documentation/networking/olympic.txt or check the
7372 Linux Token Ring Project site for the latest information at
7373 http://www.linuxtr.net
7375 Generic TMS380 Token Ring ISA/PCI adapter support
7377 This driver provides generic support for token ring adapters
7378 based on the Texas Instruments TMS380 series chipsets. This
7379 includes the SysKonnect TR4/16(+) ISA (SK-4190), SysKonnect
7380 TR4/16(+) PCI (SK-4590), SysKonnect TR4/16 PCI (SK-4591),
7381 Compaq 4/16 PCI, Thomas-Conrad TC4048 4/16 PCI, and Intel
7382 TokenExpress 4/16 and PRO ISA adapters.
7384 If you have such an adapter and would like to use it, say Y or M and
7385 read the Token-Ring mini-HOWTO, available from
7386 http://metalab.unc.edu/mdw/linux.html#howto .
7388 Also read the file linux/Documentation/networking/sktr.txt or check
7389 http://www.auk.cx/tms380tr/
7391 Traffic Shaper (EXPERIMENTAL)
7393 The traffic shaper is a virtual network device that allows you to
7394 limit the rate of outgoing data flow over some other network device.
7395 The traffic that you want to slow down can then be routed through
7396 these virtual devices. See Documentation/networking/shaper.txt for
7399 An alternative to this traffic shaper is the experimental
7400 Class-Based Queueing (CBQ) scheduling support which you get if you
7401 say Y to "QoS and/or fair queueing" above.
7403 To set up and configure shaper devices, you need the shapecfg
7404 program, available from ftp://shadow.cabi.net/pub/Linux in the
7407 This driver is also available as a module ( = code which can be
7408 inserted in and removed from the running kernel whenever you want).
7409 The module will be called shaper.o. If you want to compile it as a
7410 module, say M here and read Documentation/modules.txt. If unsure,
7415 Fiber Distributed Data Interface is a high speed local area network
7416 design; essentially a replacement for high speed Ethernet. FDDI can
7417 run over copper or fiber. If you are connected to such a network and
7418 want a driver for the FDDI card in your computer, say Y here (and
7419 then also Y to the driver for your FDDI card, below). Most people
7422 Digital DEFEA and DEFPA adapter support
7424 This is support for the DIGITAL series of EISA (DEFEA) and PCI
7425 (DEFPA) controllers which can connect you to a local FDDI network.
7427 HIgh Performance Parallel Interface support (EXPERIMENTAL)
7429 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
7430 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
7431 can run over copper (25m) or fiber (300m on multi-mode or 10km on
7432 single-mode). HIPPI networks are commonly used for clusters and to
7433 connect to super computers. If you are connected to a HIPPI network
7434 and have a HIPPI network card in your computer that you want to use
7435 under Linux, say Y here (you must also remember to enable the driver
7436 for your HIPPI card below). Most people will say N here.
7438 Essential RoadRunner HIPPI PCI adapter support
7440 Say Y here if this is your PCI HIPPI network card.
7442 This driver is also available as a module ( = code which can be
7443 inserted in and removed from the running kernel whenever you want).
7444 The module will be called rrunner.o. If you want to compile it as
7445 a module, say M here and read Documentation/modules.txt. If unsure,
7448 Use large TX/RX rings
7449 CONFIG_ROADRUNNER_LARGE_RINGS
7450 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
7451 of additional memory to allow for fastest operation, both for
7452 transmitting and receiving. This memory cannot be used by any other
7453 kernel code or by user space programs. Say Y here only if you have
7458 If you have an Acorn system with one of these (AKA25) network cards,
7459 you should say Y to this option if you wish to use it with Linux.
7461 Acorn/ANT Ether3 card
7463 If you have an Acorn system with one of these network cards, you
7464 should say Y to this option if you wish to use it with Linux.
7468 If you have an Acorn system with one of these network cards, you
7469 should say Y to this option if you wish to use it with Linux.
7471 EBSA-110 Ethernet interface
7472 CONFIG_ARM_AM79C961A
7473 If you wish to compile a kernel for the EBSA-110, then you should
7474 always answer Y to this.
7476 Support CDROM drives that are not SCSI or IDE/ATAPI
7477 CONFIG_CD_NO_IDESCSI
7478 If you have a CDROM drive that is neither SCSI nor IDE/ATAPI, say Y
7479 here, otherwise N. Read the CDROM-HOWTO, available from
7480 http://metalab.unc.edu/mdw/linux.html#howto .
7482 Note that the answer to this question doesn't directly affect the
7483 kernel: saying N will just cause this configure script to skip all
7484 the questions about these CDROM drives. If you are unsure what you
7485 have, say Y and find out whether you have one of the following
7488 For each of these drivers, a file Documentation/cdrom/<driver_name>
7489 exists. Especially in cases where you do not know exactly which kind
7490 of drive you have you should read there. Most of these drivers use a
7491 file drivers/cdrom/<driver_name>.h where you can define your
7492 interface parameters and switch some internal goodies.
7494 All these CDROM drivers are also usable as a module ( = code which
7495 can be inserted in and removed from the running kernel whenever you
7496 want). If you want to compile them as module, say M instead of Y and
7497 read Documentation/modules.txt.
7499 If you want to use any of these CDROM drivers, you also have to
7500 answer Y or M to "ISO 9660 CDROM filesystem support" below (this
7501 answer will get "defaulted" for you if you enable any of the Linux
7504 Sony CDU31A/CDU33A CDROM support
7506 These CDROM drives have a spring-pop-out caddyless drawer, and a
7507 rectangular green LED centered beneath it. NOTE: these CDROM drives
7508 will not be auto detected by the kernel at boot time; you have to
7509 provide the interface address as an option to the kernel at boot
7510 time as described in Documentation/cdrom/cdu31a or fill in your
7511 parameters into drivers/cdrom/cdu31a.c. Try "man bootparam" or
7512 see the documentation of your boot loader (lilo or loadlin) about
7513 how to pass options to the kernel. The lilo procedure is also
7514 explained in the SCSI-HOWTO.
7516 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7517 filesystem support" below, because that's the filesystem used on
7520 This driver is also available as a module ( = code which can be
7521 inserted in and removed from the running kernel whenever you want).
7522 The module will be called cdu31a.o. If you want to compile it as a
7523 module, say M here and read Documentation/modules.txt.
7525 Standard Mitsumi [no XA/Multisession] CDROM support
7527 This is the older of the two drivers for the older Mitsumi models
7528 LU-005, FX-001 and FX-001D. This is not the right driver for the
7529 FX-001DE and the triple or quad speed models (all these are
7530 IDE/ATAPI models). Please also the file Documentation/cdrom/mcd.
7532 With the old LU-005 model, the whole drive chassis slides out for cd
7533 insertion. The FX-xxx models use a motorized tray type mechanism.
7534 Note that this driver does not support XA or MultiSession CDs
7535 (PhotoCDs). There is a new driver (next question) which can do
7536 this. If you want that one, say N here.
7538 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7539 filesystem support" below, because that's the filesystem used on
7542 This driver is also available as a module ( = code which can be
7543 inserted in and removed from the running kernel whenever you want).
7544 The module will be called mcd.o. If you want to compile it as a
7545 module, say M here and read Documentation/modules.txt.
7547 IRQ channel for Mitsumi CD-ROM
7549 This allows you to specify the default value of the IRQ used by the
7550 driver. This setting can be overridden by passing the "mcd="
7551 parameter to the kernel at boot time (or at module load time if you
7552 said M to "Standard Mitsumi CDROM support").
7554 I/O base address for Mitsumi CD-ROM
7556 This allows you to specify the default value of the I/O base address
7557 used by the driver. This setting can be overridden by passing the
7558 "mcd=" parameter to the kernel at boot time (or at module load time
7559 if you said M to "Standard Mitsumi CDROM support").
7561 Mitsumi [XA/MultiSession] support
7563 Use this driver if you want to be able to read XA or MultiSession
7564 CDs (PhotoCDs) as well as ordinary CDs with your Mitsumi LU-005,
7565 FX-001 or FX-001D CDROM drive. In addition, this driver uses much
7566 less kernel memory than the old one, if that is a concern. This
7567 driver is able to support more than one drive, but each drive needs
7568 a separate interface card. Please read the file
7569 Documentation/cdrom/mcdx.
7571 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7572 filesystem support" below, because that's the filesystem used on
7575 This driver is also available as a module ( = code which can be
7576 inserted in and removed from the running kernel whenever you want).
7577 The module will be called mcdx.o. If you want to compile it as a
7578 module, say M here and read Documentation/modules.txt.
7580 Matsushita/Panasonic/Creative, Longshine, TEAC CDROM support
7582 This driver supports most of the drives which use the Panasonic or
7583 Sound Blaster interface. Please read the file
7584 Documentation/cdrom/sbpcd.
7586 The Matsushita CR-521, CR-522, CR-523, CR-562, CR-563 drives
7587 (sometimes labeled "Creative"), the Creative Labs CD200, the
7588 Longshine LCS-7260, the "IBM External ISA CDROM" (in fact a CR-56x
7589 model), the TEAC CD-55A fall under this category. Some other
7590 "electrically compatible" drives (Vertos, Genoa, some Funai models)
7591 are currently not supported; for the Sanyo H94A drive currently a
7592 separate driver (asked later) is responsible. Most drives have a
7593 uniquely shaped faceplate, with a caddyless motorized drawer, but
7594 without external brand markings. The older CR-52x drives have a
7595 caddy and manual loading/eject, but still no external markings. The
7596 driver is able to do an extended auto-probing for interface
7597 addresses and drive types; this can help to find facts in cases you
7598 are not sure, but can consume some time during the boot process if
7599 none of the supported drives gets found. Once your drive got found,
7600 you should enter the reported parameters into drivers/cdrom/sbpcd.h
7601 and set "DISTRIBUTION 0" there.
7603 This driver can support up to four CDROM controller cards, and each
7604 card can support up to four CDROM drives; if you say Y here, you
7605 will be asked how many controller cards you have. If compiled as a
7606 module, only one controller card (but with up to four drives) is
7609 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7610 filesystem support" below, because that's the filesystem used on
7613 This driver is also available as a module ( = code which can be
7614 inserted in and removed from the running kernel whenever you want).
7615 The module will be called sbpcd.o. If you want to compile it as a
7616 module, say M here and read Documentation/modules.txt.
7618 Matsushita/Panasonic, ... second CDROM controller support
7620 Say Y here only if you have two CDROM controller cards of this type
7621 (usually only if you have more than four drives). You should enter
7622 the parameters for the second, third and fourth interface card into
7623 linux/include/linux/sbpcd.h before compiling the new kernel. Read
7624 the file Documentation/cdrom/sbpcd.
7626 Aztech/Orchid/Okano/Wearnes/TXC/CyDROM CDROM support
7628 This is your driver if you have an Aztech CDA268-01A, Orchid
7629 CD-3110, Okano or Wearnes CDD110, Conrad TXC, or CyCDROM CR520 or
7630 CR540 CDROM drive. This driver -- just like all these CDROM drivers
7631 -- is NOT for CDROM drives with IDE/ATAPI interfaces, such as Aztech
7632 CDA269-031SE. Please read the file Documentation/cdrom/aztcd.
7634 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7635 filesystem support" below, because that's the filesystem used on
7638 This driver is also available as a module ( = code which can be
7639 inserted in and removed from the running kernel whenever you want).
7640 The module will be called aztcd.o. If you want to compile it as a
7641 module, say M here and read Documentation/modules.txt.
7643 Sony CDU535 CDROM support
7645 This is the driver for the older Sony CDU-535 and CDU-531 CDROM
7646 drives. Please read the file Documentation/cdrom/sonycd535.
7648 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7649 filesystem support" below, because that's the filesystem used on
7652 This driver is also available as a module ( = code which can be
7653 inserted in and removed from the running kernel whenever you want).
7654 The module will be called sonycd535.o. If you want to compile it as
7655 a module, say M here and read Documentation/modules.txt.
7657 Goldstar R420 CDROM support
7659 If this is your CDROM drive, say Y here. As described in the file
7660 linux/Documentation/cdrom/gscd, you might have to change a setting
7661 in the file linux/drivers/cdrom/gscd.h before compiling the
7662 kernel. Please read the file Documentation/cdrom/gscd.
7664 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7665 filesystem support" below, because that's the filesystem used on
7668 This driver is also available as a module ( = code which can be
7669 inserted in and removed from the running kernel whenever you want).
7670 The module will be called gscd.o. If you want to compile it as a
7671 module, say M here and read Documentation/modules.txt.
7673 Philips/LMS CM206 CDROM support
7675 If you have a Philips/LMS CDROM drive cm206 in combination with a
7676 cm260 host adapter card, say Y here. Please also read the file
7677 Documentation/cdrom/cm206.
7679 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7680 filesystem support" below, because that's the filesystem used on
7683 This driver is also available as a module ( = code which can be
7684 inserted in and removed from the running kernel whenever you want).
7685 The module will be called cm206.o. If you want to compile it as a
7686 module, say M here and read Documentation/modules.txt.
7688 Optics Storage DOLPHIN 8000AT CDROM support
7690 This is the driver for the 'DOLPHIN' drive with a 34-pin Sony
7691 compatible interface. It also works with the Lasermate CR328A. If
7692 you have one of those, say Y. This driver does not work for the
7693 Optics Storage 8001 drive; use the IDE-ATAPI CDROM driver for that
7694 one. Please read the file Documentation/cdrom/optcd.
7696 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7697 filesystem support" below, because that's the filesystem used on
7700 This driver is also available as a module ( = code which can be
7701 inserted in and removed from the running kernel whenever you want).
7702 The module will be called optcd.o. If you want to compile it as a
7703 module, say M here and read Documentation/modules.txt.
7705 Sanyo CDR-H94A CDROM support
7707 If this is your CDROM drive, say Y here and read the file
7708 Documentation/cdrom/sjcd. You should then also say Y or M to
7709 "ISO 9660 CDROM filesystem support" below, because that's the
7710 filesystem used on CDROMs.
7712 This driver is also available as a module ( = code which can be
7713 inserted in and removed from the running kernel whenever you want).
7714 The module will be called sjcd.o. If you want to compile it as a
7715 module, say M here and read Documentation/modules.txt.
7717 Soft configurable cdrom interface card support
7719 If you want to include boot-time initialization of any cdrom
7720 interface card that is software configurable, say Y here. Currently
7721 only the ISP16/MAD16/Mozart sound cards with built-in cdrom
7722 interfaces are supported.
7724 Note that the answer to this question doesn't directly affect the
7725 kernel: saying N will just cause this configure script to skip all
7726 the questions about these CDROM drives.
7728 ISP16/MAD16/Mozart soft configurable cdrom interface support
7730 These are sound cards with built-in cdrom interfaces using the OPTi
7731 82C928 or 82C929 chips. Say Y here to have them detected and
7732 possibly configured at boot time. In addition, You'll have to say Y
7733 to a driver for the particular cdrom drive you have attached to the
7734 card. Read Documentation/cdrom/isp16 for details.
7736 This driver is also available as a module ( = code which can be
7737 inserted in and removed from the running kernel whenever you want).
7738 The module will be called isp16.o. If you want to compile it as a
7739 module, say M here and read Documentation/modules.txt.
7743 If you say Y here, you will be able to set per user limits for disk
7744 usage (also called disk quotas). Currently, it works only for the
7745 ext2 filesystem. You need additional software in order to use quota
7746 support; for details, read the Quota mini-HOWTO, available from
7747 http://metalab.unc.edu/mdw/linux.html#howto . Probably the quota
7748 support is only useful for multi user systems. If unsure, say N.
7750 Support for USB (EXPERIMENTAL)
7752 Universal Serial Bus (USB) is a specification for a serial bus
7753 system which offers higher speeds and more features than the
7754 traditional PC serial port. The bus supplies power to peripherals
7755 and allows for hot swapping. Up to 127 USB peripherals can be
7756 connected to a single USB port in a tree structure; the USB port is
7757 the root of the tree, the peripherals are the leafs and the inner
7758 nodes are special USB devices called hubs. Many newer PC's have USB
7759 ports and newer peripherals such as scanners, keyboards, mice,
7760 modems and printers support the USB protocol and can be connected to
7761 the PC via those ports.
7763 Say Y here if your computer has a USB port and you want to
7764 experiment with USB devices. You then need to say Y to at least one
7765 of "UHCI support" or "OHCI support" below (the type of interface
7766 that the USB hardware in your computer provides) and then choose
7767 from among the drivers for USB peripherals.
7769 This code is also available as a module ( = code which can be
7770 inserted in and removed from the running kernel whenever you want).
7771 The module will be called usbcore.o. If you want to compile it as a
7772 module, say M here and read Documentation/modules.txt.
7774 UHCI (intel PIIX4 and others) support?
7776 The Universal Host Controller Interface is a standard by Intel for
7777 accessing the USB hardware in the PC (which is also called the USB
7778 host controller). If your USB host controller conforms to this
7779 standard, say Y. All recent boards with Intel PCI chipsets conform
7780 to this standard. If unsure, say Y.
7782 This code is also available as a module ( = code which can be
7783 inserted in and removed from the running kernel whenever you want).
7784 The module will be called usb-uhci.o. If you want to compile it as a
7785 module, say M here and read Documentation/modules.txt.
7787 OHCI (compaq and some others) support?
7789 The Open Host Controller Interface is a standard by Compaq for
7790 accessing the USB PC hardware (also called USB host controller). If
7791 your USB host controller conforms to this standard, say Y. The USB
7792 host controllers on most non-Intel architectures and on several x86
7793 compatibles with non-Intel chipsets conform to this standard.
7795 There are currently two OHCI drivers in development. You should
7796 compile at most one. The other one is "OHCI-HCD (other OHCI opt.
7797 Virt. Root Hub) support?", below.
7799 You may want to read the file drivers/usb/README.ohci.
7801 This code is also available as a module ( = code which can be
7802 inserted in and removed from the running kernel whenever you want).
7803 The module will be called usb-ohci.o. If you want to compile it as a
7804 module, say M here and read Documentation/modules.txt.
7806 Enable tons of OHCI debugging output
7807 CONFIG_USB_OHCI_DEBUG
7808 Say Y here in order to have the OHCI code generate verbose debugging
7811 OHCI-HCD (other OHCI opt. Virt. Root Hub) support?
7813 This is an alternative driver for USB PC hardware (also called USB
7814 host controller) which complies with Compaq's Open Host Controller
7815 Interface. You may want to read the file
7816 drivers/usb/README.ohci_hcd.
7818 There are currently two OHCI drivers in development. You should
7819 compile at most one. The other one is "OHCI (compaq and some others)
7822 This code is also available as a module ( = code which can be
7823 inserted in and removed from the running kernel whenever you want).
7824 The module will be called usb-ohci-hcd.o. If you want to compile it
7825 as a module, say M here and read Documentation/modules.txt.
7827 OHCI-HCD Virtual Root Hub
7828 CONFIG_USB_OHCI_VROOTHUB
7829 The virtual root hub support is currently unstable, so you probably
7830 want to say N unless you are a hacker. But you aren't a hacker since
7831 you are reading help texts.
7833 Enable lots of ISOC debugging output
7834 CONFIG_USB_DEBUG_ISOC
7835 Say Y here if you want to get lots of debugging output related to
7840 Say Y here if you want to connect several USB devices to a single
7841 USB port. You will need an USB hub to do this.
7845 This code is also available as a module ( = code which can be
7846 inserted in and removed from the running kernel whenever you want).
7847 The module will be called hub.o. If you want to compile it as a
7848 module, say M here and read Documentation/modules.txt.
7852 Say Y here if you want to connect a USB mouse to your computer's USB
7855 This code is also available as a module ( = code which can be
7856 inserted in and removed from the running kernel whenever you want).
7857 The module will be called mouse.o. If you want to compile it as a
7858 module, say M here and read Documentation/modules.txt.
7860 USB HP scanner support
7861 CONFIG_USB_HP_SCANNER
7862 Say Y here if you want to connect a USB HP scanner to your
7863 computer's USB port. Please read drivers/usb/README.hp_scanner
7864 for more information.
7866 This code is also available as a module ( = code which can be
7867 inserted in and removed from the running kernel whenever you want).
7868 The module will be called hp_scanner.o. If you want to compile it as
7869 a module, say M here and read Documentation/modules.txt.
7871 USB keyboard support
7873 Say Y here if you want to connect a USB keyboard to your computer's
7876 This code is also available as a module ( = code which can be
7877 inserted in and removed from the running kernel whenever you want).
7878 The module will be called usb-keyboard.o. If you want to compile it
7879 as a module, say M here and read Documentation/modules.txt.
7881 USB audio parsing support
7883 Say Y here if you want to connect audio equipment such as USB
7884 speakers to your computer's USB port.
7886 This code is also available as a module ( = code which can be
7887 inserted in and removed from the running kernel whenever you want).
7888 The module will be called audio.o. If you want to compile it as a
7889 module, say M here and read Documentation/modules.txt.
7891 USB Communications Device Class (ACM) support (Preliminary)
7893 This driver allows for devices which support the Abstract Control
7894 Model, including many USB-based modems, ISDN adapters, and network
7897 This code is also available as a module ( = code which can be
7898 inserted in and removed from the running kernel whenever you want).
7899 The module will be called acm.o. If you want to compile it as a
7900 module, say M here and read Documentation/modules.txt.
7902 USB Belkin and Peracom serial support
7904 Say Y here if you want to connect a Belkin, Peracom, or eTek
7905 single port USB to serial converter.
7907 This code is also available as a module ( = code which can be
7908 inserted in and removed from the running kernel whenever you want).
7909 The module will be called usb-serial.o. If you want to compile it
7910 as a module, say M here and read Documentation/modules.txt.
7914 Say Y here if you want to connect a printer to your computer's USB
7917 This code is also available as a module ( = code which can be
7918 inserted in and removed from the running kernel whenever you want).
7919 The module will be called printer.o. If you want to compile it as a
7920 module, say M here and read Documentation/modules.txt.
7922 USB CPiA Camera support
7924 Say Y here if you want to connect this type of camera to your
7925 computer's USB port.
7927 This code is also available as a module ( = code which can be
7928 inserted in and removed from the running kernel whenever you want).
7929 The module will be called cpia.o. If you want to compile it as a
7930 module, say M here and read Documentation/modules.txt.
7932 USB Kodak DC-2xx Camera support
7934 Say Y here if you want to connect this type of still camera to
7935 your computer's USB port. See drivers/usb/README.dc2xx for more
7936 information; some non-Kodak cameras may also work with this
7937 driver, given application support (such as www.gPhoto.org).
7939 This code is also available as a module ( = code which can be
7940 inserted in and removed from the running kernel whenever you want).
7941 The module will be called dc2xx.o. If you want to compile it as a
7942 module, say M here and read Documentation/modules.txt.
7946 Say Y here if you want to connect SCSI devices to your computer's
7949 USB SCSI verbose debug
7950 CONFIG_USB_SCSI_DEBUG
7951 Say Y here in order to have the USB SCSI code generate verbose
7954 #EZUSB Firmware downloader
7957 USS720 parport driver
7959 This driver is for USB parallel port adapters that use the Lucent
7960 Technologies USS-720 chip. These adapters provide USB compatibility
7961 to peripherals designed with parallel port interfaces.
7963 The chip has two modes: automatic mode and manual mode. In automatic
7964 mode, it looks to the computer like a standard USB printer. Only
7965 printers may be connected to the USS-720 in this mode. The generic
7966 USB printer driver ("USB Printer support", above) may be used in
7967 that mode, and you can say N here if you want to use the chip only
7970 Manual mode is not limited to printers, any parallel port
7971 device should work. This driver utilizes manual mode.
7972 Note however that some operations are three orders of a magnitude
7973 slower than on a PCI/ISA Parallel Port, so timing critical
7974 applications might not work.
7976 Say Y here if you own an USS-720 USB->Parport cable and intend to
7977 connect anything other than a printer to it.
7979 This code is also available as a module ( = code which can be
7980 inserted in and removed from the running kernel whenever you want).
7981 The module will be called uss720.o. If you want to compile it as a
7982 module, say M here and read Documentation/modules.txt.
7984 USB /proc filesystem entry support (Preliminary)
7986 This reports USB drivers and devices in the /proc filesystem.
7987 Entries are located in /proc/bus/usb. The entries are described in
7988 the file Documentation/proc_usb_info.txt.
7990 Note that you must say Y to "/proc filesystem support" below for
7995 Advanced Configuration and Power Interface (ACPI) is an interface
7996 specification to support power management of peripherals. If your
7997 system supports it, say Y here.
8001 Minix is a simple operating system used in many classes about OS's.
8002 The minix filesystem (method to organize files on a hard disk
8003 partition or a floppy disk) was the original filesystem for Linux,
8004 but has been superseded by the second extended filesystem ext2fs.
8005 You don't want to use the minix filesystem on your hard disk because
8006 of certain built-in restrictions, but it is sometimes found on older
8007 Linux floppy disks. This option will enlarge your kernel by about
8008 28 kB. If unsure, say N.
8010 If you want to compile this as a module ( = code which can be
8011 inserted in and removed from the running kernel whenever you want),
8012 say M here and read Documentation/modules.txt. The module will be
8013 called minix.o. Note that the filesystem of your root partition (the
8014 one containing the directory /) cannot be compiled as a module.
8016 Second extended fs support
8018 This is the de facto standard Linux filesystem (method to organize
8019 files on a storage device) for hard disks.
8021 You want to say Y here, unless you intend to use Linux exclusively
8022 from inside a DOS partition using the umsdos filesystem. The
8023 advantage of the latter is that you can get away without
8024 repartitioning your hard drive (which often implies backing
8025 everything up and restoring afterwards); the disadvantage is that
8026 Linux becomes susceptible to DOS viruses and that umsdos is somewhat
8027 slower than ext2fs. Even if you want to run Linux in this fashion,
8028 it might be a good idea to have ext2fs around: it enables you to
8029 read more floppy disks and facilitates the transition to a *real*
8030 Linux partition later. Another (rare) case which doesn't require
8031 ext2fs is a diskless Linux box which mounts all files over the
8032 network using NFS (in this case it's sufficient to say Y to "NFS
8033 filesystem support" below). Saying Y here will enlarge your kernel
8036 The Ext2fs-Undeletion mini-HOWTO, available from
8037 http://metalab.unc.edu/mdw/linux.html#howto , gives information about
8038 how to retrieve deleted files on ext2fs filesystems.
8040 To change the behavior of ext2 filesystems, you can use the tune2fs
8041 utility ("man tune2fs"). To modify attributes of files and
8042 directories on ext2 filesystems, use chattr ("man chattr").
8044 Ext2fs partitions can be read from within DOS using the ext2tool
8045 command line tool package (available via FTP (user: anonymous) from
8046 ftp://metalab.unc.edu/pub/Linux/system/filesystems/ext2 ) and from
8047 within Windows NT using the ext2nt command line tool package from
8048 ftp://metalab.unc.edu/pub/Linux/utils/dos . Explore2fs is a graphical
8049 explorer for ext2fs partitions which runs on Windows 95 and Windows
8050 NT and includes experimental write support; it is available from
8051 http://jnewbigin-pc.it.swin.edu.au/Linux/Explore2fs.htm .
8053 If you want to compile this filesystem as a module ( = code which
8054 can be inserted in and removed from the running kernel whenever you
8055 want), say M here and read Documentation/modules.txt. The module
8056 will be called ext2.o. Be aware however that the filesystem of your
8057 root partition (the one containing the directory /) cannot be
8058 compiled as a module, and so this could be dangerous. Most everyone
8059 wants to say Y here.
8061 SCO UnixWare BFS Support
8063 Boot Filesystem (BFS) is a filesystem used under SCO UnixWare to
8064 allow bootloader access the kernel image and other important files
8065 during the boot process. It is usually mounted under /stand and
8066 corresponds to the slice marked as "STAND" in the UnixWare
8067 partition. This is useful if you want to access files on your /stand
8068 slice from Linux. More information on this filesystem can be found in
8069 Documentation/filesystems/bfs.txt file. If you do not know what it is,
8072 If you want to compile this as a module ( = code which can be
8073 inserted in and removed from the running kernel whenever you want),
8074 say M here and read Documentation/modules.txt. The module will be
8075 called bfs.o. Note that the filesystem of your root partition (the
8076 one containing the directory /) cannot be compiled as a module.
8078 ISO 9660 CDROM filesystem support
8080 This is the standard filesystem used on CDROMs. It was previously
8081 known as "High Sierra Filesystem" and is called "hsfs" on other Unix
8082 systems. The so-called Rock-Ridge extensions which allow for long
8083 Unix filenames and symbolic links are also supported by this driver.
8084 If you have a CDROM drive and want to do more with it than just
8085 listen to audio CDs and watch its LEDs, say Y (and read
8086 Documentation/filesystems/isofs.txt and the CDROM-HOWTO, available
8087 from http://metalab.unc.edu/mdw/linux.html#howto ), thereby
8088 enlarging your kernel by about 27 KB; otherwise say N.
8090 If you want to compile this as a module ( = code which can be
8091 inserted in and removed from the running kernel whenever you want),
8092 say M here and read Documentation/modules.txt. The module will be
8095 Microsoft Joliet CDROM extensions
8097 Joliet is a Microsoft extension for the ISO 9660 CDROM filesystem
8098 which allows for long filenames in unicode format (unicode is the
8099 new 16 bit character code, successor to ASCII, which encodes the
8100 characters of almost all languages of the world; see
8101 http://www.unicode.org for more information). Say Y here if you want
8102 to be able to read Joliet CDROMs under Linux.
8104 UDF Filesystem support (read only)
8106 This is the new filesystem used by some CDROMS and DVD drivers. Say
8107 Y if you intend to mount DVD discs or CDRW's written in packet mode,
8108 or if written to by other UDF utilities, such as DirectCD. Please
8109 read Documentation/filesystems/udf.txt.
8111 This filesystem support is also available as a module ( = code which
8112 can be inserted in and removed from the running kernel whenever you
8113 want). The module is called udf.o. If you want to compile it as a
8114 module, say M here and read Documentation/modules.txt.
8118 UDF write support (DANGEROUS)
8120 Say Y if you want to test write support for UDF filesystems.
8121 Due to lack of support for writing to CDR/CDRW's, this option
8122 is only supported for Hard Discs, DVD-RAM, and loopback files.
8126 If you want to use one of the FAT-based filesystems (the MS-DOS,
8127 VFAT (Windows 95) and UMSDOS (used to run Linux on top of an
8128 ordinary DOS partition) filesystems), then you must say Y or M here
8129 to include FAT support. You will then be able to mount partitions or
8130 diskettes with FAT-based filesystems and transparently access the
8131 files on them, i.e. MSDOS files will look and behave just like all
8134 This FAT support is not a filesystem in itself, it only provides the
8135 foundation for the other filesystems. You will have to say Y or M to
8136 at least one of "msdos fs support" or "vfat fs support" in order to
8139 Another way to read and write MSDOS floppies and hard drive
8140 partitions from within Linux (but not transparently) is with the
8141 mtools ("man mtools") program suite. This doesn't require the FAT
8144 It is now also becoming possible to read and write compressed FAT
8145 filesystems; read Documentation/filesystems/fat_cvf.txt for details.
8147 The FAT support will enlarge your kernel by about 37 KB. If unsure,
8150 If you want to compile this as a module however ( = code which can
8151 be inserted in and removed from the running kernel whenever you
8152 want), say M here and read Documentation/modules.txt. The module
8153 will be called fat.o. Note that if you compile the FAT support as a
8154 module, you cannot compile any of the FAT-based filesystems into the
8155 kernel -- they will have to be modules as well. The filesystem of
8156 your root partition (the one containing the directory /) cannot be a
8157 module, so don't say M here if you intend to use UMSDOS as your root
8162 This allows you to mount MSDOS partitions of your hard drive (unless
8163 they are compressed; to access compressed MSDOS partitions under
8164 Linux, you can either use the DOS emulator DOSEMU, described in the
8165 DOSEMU-HOWTO, available from
8166 http://metalab.unc.edu/mdw/linux.html#howto , or try dmsdosfs in
8167 ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs . If you
8168 intend to use dosemu with a non-compressed MSDOS partition, say Y
8169 here) and MSDOS floppies. This means that file access becomes
8170 transparent, i.e. the MSDOS files look and behave just like all
8173 If you want to use umsdos, the Unix-like filesystem on top of DOS,
8174 which allows you to run Linux from within a DOS partition without
8175 repartitioning, you'll have to say Y or M here.
8177 If you have Windows 95 or Windows NT installed on your MSDOS
8178 partitions, you should use the VFAT filesystem (say Y to "vfat fs
8179 support" below), or you will not be able to see the long filenames
8180 generated by Windows 95 / Windows NT.
8182 This option will enlarge your kernel by about 7 KB. If unsure,
8183 answer Y. This will only work if you said Y to "fat fs support" as
8184 well. If you want to compile this as a module however ( = code which
8185 can be inserted in and removed from the running kernel whenever you
8186 want), say M here and read Documentation/modules.txt. The module
8187 will be called msdos.o.
8189 VFAT (Windows-95) fs support
8191 This option provides support for normal Windows filesystems with
8192 long filenames. That includes non-compressed FAT-based filesystems
8193 used by Windows 95, Windows 98, Windows NT 4.0, and mtools.
8195 You cannot use the VFAT filesystem for your Linux root partition
8196 (the one containing the directory /); use UMSDOS instead if you
8197 want to run Linux from within a DOS partition (i.e. say Y to
8198 "umsdos: Unix like fs on top of std MSDOS fs", below).
8200 The VFAT support enlarges your kernel by about 10 KB and it only
8201 works if you said Y to the "fat fs support" above. Please read the
8202 file Documentation/filesystems/vfat.txt for details. If unsure,
8205 If you want to compile this as a module ( = code which can be
8206 inserted in and removed from the running kernel whenever you want),
8207 say M here and read Documentation/modules.txt. The module will be
8210 UMSDOS: Unix-like filesystem on top of standard MSDOS filesystem
8212 Say Y here if you want to run Linux from within an existing DOS
8213 partition of your hard drive. The advantage of this is that you can
8214 get away without repartitioning your hard drive (which often implies
8215 backing everything up and restoring afterwards) and hence you're
8216 able to quickly try out Linux or show it to your friends; the
8217 disadvantage is that Linux becomes susceptible to DOS viruses and
8218 that UMSDOS is somewhat slower than ext2fs. Another use of UMSDOS
8219 is to write files with long unix filenames to MSDOS floppies; it
8220 also allows Unix-style softlinks and owner/permissions of files on
8221 MSDOS floppies. You will need a program called umssync in order to
8222 make use of umsdos; read Documentation/filesystems/umsdos.txt.
8224 This option enlarges your kernel by about 28 KB and it only works if
8225 you said Y to both "fat fs support" and "msdos fs support" above. If
8226 you want to compile this as a module ( = code which can be inserted
8227 in and removed from the running kernel whenever you want), say M
8228 here and read Documentation/modules.txt. The module will be called
8229 umsdos.o. Note that the filesystem of your root partition (the one
8230 containing the directory /) cannot be a module, so saying M could be
8231 dangerous. If unsure, say N.
8233 /proc filesystem support
8235 This is a virtual filesystem providing information about the status
8236 of the system. "Virtual" means that it doesn't take up any space on
8237 your hard disk: the files are created on the fly by the kernel when
8238 you try to access them. Also, you cannot read the files with older
8239 version of the program less: you need to use more or cat.
8241 It's totally cool; for example, "cat /proc/interrupts" gives
8242 information about what the different IRQs are used for at the moment
8243 (there is a small number of Interrupt ReQuest lines in your computer
8244 that are used by the attached devices to gain the CPU's attention --
8245 often a source of trouble if two devices are mistakenly configured
8246 to use the same IRQ).
8248 The /proc filesystem is explained in the file
8249 Documentation/filesystems/proc.txt and on the proc(5) manpage ("man
8252 This option will enlarge your kernel by about 67 KB. Several
8253 programs depend on this, so everyone should say Y here.
8255 NFS filesystem support
8257 If you are connected to some other (usually local) Unix computer
8258 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
8259 on that computer (the NFS server) using the Network File Sharing
8260 protocol, say Y. "Mounting files" means that the client can access
8261 the files with usual UNIX commands as if they were sitting on the
8262 client's hard disk. For this to work, the server must run the
8263 programs nfsd and mountd (but does not need to have NFS filesystem
8264 support enabled in its kernel). NFS is explained in the Network
8265 Administrator's Guide, available from
8266 http://metalab.unc.edu/mdw/linux.html#guide , on its man page: "man
8267 nfs", and in the NFS-HOWTO.
8269 A superior but less widely used alternative to NFS is provided by
8270 the Coda filesystem; see "Coda filesystem support" below.
8272 If you say Y here, you should have said Y to TCP/IP networking also.
8273 This option would enlarge your kernel by about 27 KB.
8275 This filesystem is also available as a module ( = code which can be
8276 inserted in and removed from the running kernel whenever you want).
8277 The module is called nfs.o. If you want to compile it as a module,
8278 say M here and read Documentation/modules.txt.
8280 If you are configuring a diskless machine which will mount its root
8281 filesystem over NFS at boot time, say Y here and to "IP: kernel
8282 level autoconfiguration" above and to "Root file system on NFS"
8283 below. You cannot compile this driver as a module in this case.
8284 There are two packages designed for booting diskless machines over
8285 the net: netboot and etherboot, both available via FTP from
8286 ftp://metalab.unc.edu/pub/Linux/system/boot/ethernet/ .
8288 If you don't know what all this is about, say N.
8290 Root file system on NFS
8292 If you want your Linux box to mount its whole root filesystem (the
8293 one containing the directory /) from some other computer over the
8294 net via NFS (presumably because your box doesn't have a hard disk),
8295 say Y. Read Documentation/nfsroot.txt for details. It is likely that
8296 in this case, you also want to say Y to "IP: kernel level
8297 autoconfiguration" so that your box can discover its network address
8300 Most people say N here.
8302 NFS server support (EXPERIMENTAL)
8304 If you want your Linux box to act as a NFS *server*, so that other
8305 computers on your local network which support NFS can access certain
8306 directories on your box transparently, you have two options: you can
8307 use the self-contained user space program nfsd, in which case you
8308 should say N here, or you can say Y and use this new experimental
8309 kernel based NFS server. The advantage of the kernel based solution
8310 is that it is faster; it might not be completely stable yet, though.
8312 In either case, you will need support software; the respective
8313 locations are given in the file Documentation/Changes in the NFS
8316 Please read the NFS-HOWTO, available from
8317 http://metalab.unc.edu/mdw/linux.html#howto .
8319 The NFS server is also available as a module ( = code which can be
8320 inserted in and removed from the running kernel whenever you want).
8321 The module is called nfsd.o. If you want to compile it as a module,
8322 say M here and read Documentation/modules.txt. If unsure, say N.
8324 Emulate SUN NFS server
8326 If you would like for the server to allow clients to access
8327 directories that are mount points on the local filesystem (this is
8328 how nfsd behaves on Sun systems), say Y here. If unsure, say N.
8330 OS/2 HPFS filesystem support
8332 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
8333 is the filesystem used for organizing files on OS/2 hard disk
8334 partitions. Say Y if you want to be able to read files from an OS/2
8335 HPFS partition of your hard drive. OS/2 floppies however are in
8336 regular MSDOS format, so you don't need this option in order to be
8337 able to read them. Read Documentation/filesystems/hpfs.txt.
8339 This filesystem is also available as a module ( = code which can be
8340 inserted in and removed from the running kernel whenever you want).
8341 The module is called hpfs.o. If you want to compile it as a module,
8342 say M here and read Documentation/modules.txt. If unsure, say N.
8344 Windows NT NTFS support (read only)
8346 NTFS is the file system of Microsoft Windows NT. Say Y if you want
8347 to get read access to files on NTFS partitions of your hard drive.
8348 The Linux NTFS driver supports most of the mount options of the VFAT
8349 driver, see Documentation/filesystems/ntfs.txt. Saying Y here will
8350 give you read-only access to NTFS partitions.
8352 This code is also available as a module ( = code which can be
8353 inserted in and removed from the running kernel whenever you want).
8354 The module will be called ntfs.o. If you want to compile it as a
8355 module, say M here and read Documentation/modules.txt.
8357 NTFS write support (DANGEROUS)
8359 If you say Y here, you will (hopefully) be able to write to NTFS
8360 file systems as well as read from them. The read-write support
8361 in NTFS is far from being complete and is not well tested. If you
8362 enable this, back up your NTFS volume first since it may get
8367 System V and Coherent filesystem support (read only)
8369 SCO, Xenix and Coherent are commercial Unix systems for Intel
8370 machines. Saying Y here would allow you to read from their floppies
8371 and hard disk partitions.
8373 If you have floppies or hard disk partitions like that, it is likely
8374 that they contain binaries from those other Unix systems; in order
8375 to run these binaries, you will want to install iBCS2 (Intel Binary
8376 Compatibility Standard is a kernel module which lets you run SCO,
8377 Xenix, Wyse, UnixWare, Dell Unix and System V programs under Linux
8378 and is often needed to run commercial software that's only available
8379 for those systems. It's available via FTP (user: anonymous) from
8380 ftp://tsx-11.mit.edu/pub/linux/BETA ).
8382 If you only intend to mount files from some other Unix over the
8383 network using NFS, you don't need the System V filesystem support
8384 (but you need NFS filesystem support obviously).
8386 Note that this option is generally not needed for floppies, since a
8387 good portable way to transport files and directories between unixes
8388 (and even other operating systems) is given by the tar program ("man
8389 tar" or preferably "info tar"). Note also that this option has
8390 nothing whatsoever to do with the option "System V IPC". Read about
8391 the System V filesystem in Documentation/filesystems/sysv-fs.txt.
8392 Saying Y here will enlarge your kernel by about 27 kB.
8394 If you want to compile this as a module ( = code which can be
8395 inserted in and removed from the running kernel whenever you want),
8396 say M here and read Documentation/modules.txt. The module will be
8399 If you haven't heard about all of this before, it's safe to say N.
8401 SYSV filesystem write support (DANGEROUS)
8402 CONFIG_SYSV_FS_WRITE
8403 If you say Y here, you will (hopefully) be able to write to System V
8404 and Coherent file systems as well as read from them. The read-write
8405 support in SYSV is not well tested yet. If you enable this, back up
8406 your SYSV/Coherent volumes first since they may get damaged.
8410 Amiga FFS filesystem support
8412 The Fast File System (FFS) is the common filesystem used on hard
8413 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
8414 if you want to be able to read and write files from and to an Amiga
8415 FFS partition on your hard drive. Amiga floppies however cannot be
8416 read with this driver due to an incompatibility of the floppy
8417 controller used in an Amiga and the standard floppy controller in
8418 PCs and workstations. Read Documentation/filesystems/affs.txt and
8421 With this driver you can also mount disk files used by Bernd
8422 Schmidt's Un*X Amiga Emulator (http://www.freiburg.linux.de/~uae/ ).
8423 If you want to do this, you will also need to say Y or M to "Loop
8424 device support", above.
8426 This filesystem is also available as a module ( = code which can be
8427 inserted in and removed from the running kernel whenever you want).
8428 The module is called affs.o. If you want to compile it as a module,
8429 say M here and read Documentation/modules.txt. If unsure, say N.
8431 Apple Macintosh filesystem support (EXPERIMENTAL)
8433 If you say Y here, you will be able to mount Macintosh-formatted
8434 floppy disks and hard drive partitions with full read-write access.
8435 Please read fs/hfs/HFS.txt to learn about the available mount
8438 This filesystem support is also available as a module ( = code which
8439 can be inserted in and removed from the running kernel whenever you
8440 want). The module is called hfs.o. If you want to compile it as a
8441 module, say M here and read Documentation/modules.txt.
8443 ROM filesystem support
8445 This is a very small read-only filesystem mainly intended for
8446 initial ram disks of installation disks, but it could be used for
8447 other read-only media as well. Read
8448 Documentation/filesystems/romfs.txt for details.
8450 This filesystem support is also available as a module ( = code which
8451 can be inserted in and removed from the running kernel whenever you
8452 want). The module is called romfs.o. If you want to compile it as a
8453 module, say M here and read Documentation/modules.txt.
8455 If you don't know whether you need it, then you don't need it:
8458 QNX filesystem support (read only) (EXPERIMENTAL)
8460 This is the filesystem used by the operating system QNX 4. Say Y if
8461 you intend to mount QNX hard disks or floppies. Unless you say Y to
8462 "QNXFS read-write support" below, you will only be able to read
8465 This filesystem support is also available as a module ( = code which
8466 can be inserted in and removed from the running kernel whenever you
8467 want). The module is called qnx4.o. If you want to compile it as a
8468 module, say M here and read Documentation/modules.txt.
8472 QNXFS write support (DANGEROUS)
8474 Say Y if you want to test write support for QNX filesystems.
8476 Kernel automounter support
8478 The automounter is a tool to automatically mount remote filesystems
8479 on demand. This implementation is partially kernel-based to reduce
8480 overhead in the already-mounted case; this is unlike the BSD
8481 automounter (amd), which is a pure user space daemon.
8483 To use the automounter you need the user-space tools from
8484 ftp://ftp.kernel.org/pub/linux/daemons/autofs ; you also want to
8485 answer Y to "NFS filesystem support", below.
8487 If you want to compile this as a module ( = code which can be
8488 inserted in and removed from the running kernel whenever you want),
8489 say M here and read Documentation/modules.txt. The module will be
8492 If you are not a part of a fairly large, distributed network, you
8493 probably do not need an automounter, and can say N here.
8495 EFS filesystem support (read only) (EXPERIMENTAL)
8497 EFS is an older filesystem used for non-ISO9660 CDROMs and hard disk
8498 partitions by SGI's IRIX operating system (IRIX 6.0 and newer uses
8499 the XFS filesystem for hard disk partitions however).
8501 This implementation only offers read-only access. If you don't know
8502 what all this is about, it's safe to say N. For more information
8503 about EFS see its home page at http://aeschi.ch.eu.org/efs/ .
8505 If you want to compile the EFS filesystem support as a module ( =
8506 code which can be inserted in and removed from the running kernel
8507 whenever you want), say M here and read Documentation/modules.txt.
8508 The module will be called efs.o.
8510 SGI disklabel support
8511 CONFIG_SGI_DISKLABEL
8512 Say Y to this only if you plan on mounting disks with SGI
8513 disklabels. This is not required to mount EFS-format CDROMs.
8515 UFS filesystem support (read only)
8517 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
8518 OpenBSD and NeXTstep) use a filesystem called UFS. Some System V
8519 Unixes can create and mount hard disk partitions and diskettes using
8520 this filesystem as well. Saying Y here will allow you to read from
8521 these partitions; if you also want to write to them, say Y to the
8522 experimental "UFS filesystem write support", below. Please read the
8523 file Documentation/filesystems/ufs.txt for more information.
8525 If you only intend to mount files from some other Unix over the
8526 network using NFS, you don't need the UFS filesystem support (but
8527 you need NFS filesystem support obviously).
8529 Note that this option is generally not needed for floppies, since a
8530 good portable way to transport files and directories between unixes
8531 (and even other operating systems) is given by the tar program ("man
8532 tar" or preferably "info tar").
8534 When accessing NeXTstep files, you may need to convert them from the
8535 NeXT character set to the Latin1 character set; use the program
8536 recode ("info recode") for this purpose.
8538 If you want to compile the UFS filesystem support as a module ( =
8539 code which can be inserted in and removed from the running kernel
8540 whenever you want), say M here and read Documentation/modules.txt.
8541 The module will be called ufs.o.
8543 If you haven't heard about all of this before, it's safe to say N.
8545 UFS filesystem write support (DANGEROUS)
8547 Say Y here if you want to try writing to UFS partitions. This is
8548 experimental, so you should back up your UFS partitions beforehand.
8550 Advanced partition selection
8551 CONFIG_PARTITION_ADVANCED
8552 Say Y here if you would like to use hard disks under Linux which
8553 were partitioned under an operating system running on a different
8554 architecture than your Linux system.
8556 Note that the answer to this question won't directly affect the
8557 kernel: saying N will just cause this configure script to skip all
8558 the questions about foreign partitioning schemes. If unsure, say N.
8560 Alpha OSF partition support
8561 CONFIG_OSF_PARTITION
8562 Say Y here if you would like to use hard disks under Linux which
8563 were partitioned on an Alpha machine.
8565 Macintosh partition map support
8566 CONFIG_MAC_PARTITION
8567 Say Y here if you would like to use hard disks under Linux which
8568 were partitioned on a Macintosh.
8570 PC BIOS (MSDOS partition tables) support
8571 CONFIG_MSDOS_PARTITION
8572 Say Y here if you would like to use hard disks under Linux which
8573 were partitioned on an x86 PC (not necessarily by DOS).
8575 BSD disklabel (FreeBSD partition tables) support
8576 CONFIG_BSD_DISKLABEL
8577 FreeBSD uses its own hard disk partition scheme on your PC. It
8578 requires only one entry in the primary partition table of your disk
8579 and manages it similarly to DOS extended partitions, putting in its
8580 first sector a new partition table in BSD disklabel format. Saying Y
8581 here allows you to read these disklabels and further mount FreeBSD
8582 partitions from within Linux if you have also said Y to "UFS
8583 filesystem support", above. If you don't know what all this is
8586 Sun partition tables support
8587 CONFIG_SUN_PARTITION
8588 Like most systems, SunOS uses its own hard disk partition table
8589 format, incompatible with all others. Saying Y here allows you to
8590 read these partition tables and further mount SunOS partitions from
8591 within Linux if you have also said Y to "UFS filesystem support",
8592 above. This is mainly used to carry data from a SPARC under SunOS to
8593 your Linux box via a removable medium like magneto-optical or ZIP
8594 drives; note however that a good portable way to transport files and
8595 directories between unixes (and even other operating systems) is
8596 given by the tar program ("man tar" or preferably "info tar"). If
8597 you don't know what all this is about, say N.
8599 Solaris (x86) partition table support
8600 CONFIG_SOLARIS_X86_PARTITION
8601 Like most systems, Solaris x86 uses its own hard disk partition
8602 table format, incompatible with all others. Saying Y here allows you
8603 to read these partition tables and further mount Solaris x86
8604 partitions from within Linux if you have also said Y to "UFS
8605 filesystem support", above.
8607 SGI partition support
8608 CONFIG_SGI_PARTITION
8609 Say Y here if you would like to be able to read the hard disk
8610 partition table format used by SGI machines.
8612 ADFS filesystem support (read only) (EXPERIMENTAL)
8614 The Acorn Disc Filing System is the standard filesystem of the
8615 RiscOS operating system which runs on Acorn's ARM-based Risc PC
8616 systems and the Acorn Archimedes range of machines. If you say Y
8617 here, Linux will be able to read from ADFS partitions on hard drives
8618 and from ADFS-formatted floppy discs.
8620 The ADFS partition should be the first partition (i.e.,
8621 /dev/[hs]d?1) on each of your drives. Please read the file
8622 Documentation/filesystems/adfs.txt for further details.
8624 This code is also available as a module called adfs.o ( = code which
8625 can be inserted in and removed from the running kernel whenever you
8626 want). If you want to compile it as a module, say M here and read
8627 Documentation/modules.txt.
8631 /dev/pts filesystem for Unix98 PTYs
8633 You should say Y here if you said Y to "Unix98 PTY support" above.
8634 You'll then get a virtual filesystem which can be mounted on
8635 /dev/pts with "mount -t devpts". This, together with the pseudo
8636 terminal master multiplexer /dev/ptmx, is used for pseudo terminal
8637 support as described in The Open Group's Unix98 standard: in order
8638 to acquire a pseudo terminal, a process opens /dev/ptmx; the number
8639 of the pseudo terminal is then made available to the process and the
8640 pseudo 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 GNU C library glibc 2.1 contains the requisite support for this
8644 mode of operation; you also need client programs that use the Unix98
8647 UnixWare slices support (EXPERIMENTAL)
8648 CONFIG_UNIXWARE_DISKLABEL
8649 Like some systems, UnixWare uses its own slice table inside a
8650 partition (VTOC - Virtual Table of Contents). Its format is
8651 incompatible with all other OSes. Saying Y here allows you to read
8652 VTOC and further mount UnixWare partitions read-only from within
8653 Linux if you have also said Y to "UFS filesystem support" or "System
8654 V and Coherent filesystem support", above.
8656 This is mainly used to carry data from a UnixWare box to your
8657 Linux box via a removable medium like magneto-optical, ZIP or
8658 removable IDE drives. Note, however, that a good portable way to
8659 transport files and directories between unixes (and even other
8660 operating systems) is given by the tar program ("man tar" or
8661 preferably "info tar").
8663 If you don't know what all this is about, say N.
8665 SMB filesystem support (to mount Windows shares etc.)
8667 SMB (Server Message Block) is the protocol Windows for Workgroups
8668 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
8669 files and printers over local networks. Saying Y here allows you to
8670 mount their filesystems (often called "shares" in this context) and
8671 access them just like any other Unix directory. Currently, this
8672 works only if the Windows machines use TCP/IP as the underlying
8673 transport protocol, and not NetBEUI. For details, read
8674 Documentation/filesystems/smbfs.txt and the SMB-HOWTO, available
8675 from http://metalab.unc.edu/mdw/linux.html#howto .
8677 Note: if you just want your box to act as an SMB *server* and make
8678 files and printing services available to Windows clients (which need
8679 to have a TCP/IP stack), you don't need to say Y here; you can use
8680 the program samba (available via FTP (user: anonymous) in
8681 ftp://metalab.unc.edu/pub/Linux/system/network/samba ) for that.
8683 General information about how to connect Linux, Windows machines and
8684 Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
8686 If you want to compile the SMB support as a module ( = code which
8687 can be inserted in and removed from the running kernel whenever you
8688 want), say M here and read Documentation/modules.txt. The module
8689 will be called smbfs.o. Most people say N, however.
8691 Coda filesystem support (advanced network fs)
8693 Coda is an advanced network filesystem, similar to NFS in that it
8694 enables you to mount filesystems of a remote server and access them
8695 with regular Unix commands as if they were sitting on your hard
8696 disk. Coda has several advantages over NFS: support for disconnected
8697 operation (e.g. for laptops), read/write server replication,
8698 security model for authentication and encryption, persistent client
8699 caches and write back caching.
8701 If you say Y here, your Linux box will be able to act as a Coda
8702 *client*. You will need user level code as well, both for the client
8703 and server. Servers are currently user level, i.e. need no kernel
8704 support. Please read Documentation/filesystems/coda.txt and check
8705 out the Coda home page http://www.coda.cs.cmu.edu .
8707 If you want to compile the coda client support as a module ( = code
8708 which can be inserted in and removed from the running kernel
8709 whenever you want), say M here and read Documentation/modules.txt.
8710 The module will be called coda.o.
8712 NCP filesystem support (to mount NetWare volumes)
8714 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
8715 used by Novell NetWare clients to talk to file servers. It is to IPX
8716 what NFS is to TCP/IP, if that helps. Saying Y here allows you to
8717 mount NetWare file server volumes and to access them just like any
8718 other Unix directory. For details, please read the file
8719 Documentation/filesystems/ncpfs.txt in the kernel source and the
8720 IPX-HOWTO from http://metalab.unc.edu/mdw/linux.html#howto .
8722 You do not have to say Y here if you want your Linux box to act as a
8723 file *server* for Novell NetWare clients.
8725 General information about how to connect Linux, Windows machines and
8726 Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
8728 If you want to compile this as a module ( = code which can be
8729 inserted in and removed from the running kernel whenever you want),
8730 say M here and read Documentation/modules.txt. The module will be
8731 called ncpfs.o. Say N unless you are connected to a Novell network.
8734 CONFIG_NCPFS_PACKET_SIGNING
8735 NCP allows packets to be signed for stronger security. If you want
8736 security, say Y. Normal users can leave it off. To be able to use
8737 packet signing you must use ncpfs > 2.0.12.
8739 Proprietary file locking
8740 CONFIG_NCPFS_IOCTL_LOCKING
8741 Allows locking of records on remote volumes. Say N unless you have
8742 special applications which are able to utilize this locking scheme.
8744 Clear remove/delete inhibit when needed
8746 Allows manipulation of files flagged as Delete or Rename Inhibit. To
8747 use this feature you must mount volumes with the ncpmount parameter
8748 "-s" (ncpfs-2.0.12 and newer). Say Y unless you are not mounting
8749 volumes with -f 444.
8751 Use NFS namespace when available
8753 Allows you to utilize NFS namespace on NetWare servers. It brings
8754 you case sensitive filenames. Say Y. You can disable it at
8755 mount-time with the `-N nfs' parameter of ncpmount.
8757 Use OS2/LONG namespace when available
8759 Allows you to utilize OS2/LONG namespace on NetWare servers.
8760 Filenames in this namespace are limited to 255 characters, they are
8761 case insensitive, and case in names is preserved. Say Y. You can
8762 disable it at mount time with the -N os2 parameter of ncpmount.
8764 Lowercase DOS filenames on LONG namespace volume
8765 CONFIG_NCPFS_SMALLDOS
8766 If you say Y here, every filename on a NetWare server volume using
8767 the OS2/LONG namespace will be converted to lowercase characters.
8768 (For regular NetWare file server volumes with DOS namespace, this is
8769 done automatically, even if you say N here.) Saying N here will give
8770 you these filenames in uppercase.
8772 This is only a cosmetic option since the OS2/LONG namespace is case
8773 insensitive. The only major reason for this option is backward
8774 compatibility when moving from DOS to OS2/LONG namespace support.
8775 Long filenames (created by Win95) will not be affected.
8777 This option does not solve the problem that filenames appear
8778 differently under Linux and under Windows, since Windows does an
8779 additional conversions on the client side. You can achieve similar
8780 effects by saying Y to "Allow using of Native Language Support"
8783 Allow mounting of volume subdirectories
8784 CONFIG_NCPFS_MOUNT_SUBDIR
8785 Allows you to mount not only whole servers or whole volumes, but
8786 also subdirectories from a volume. It can be used to reexport data
8787 and so on. There is no reason to say N, so Y is recommended unless
8788 you count every byte.
8790 To utilize this feature you must use ncpfs-2.0.12 or newer.
8792 NDS interserver authentication domains
8793 CONFIG_NCPFS_NDS_DOMAINS
8794 This allows storing NDS private keys in kernel space where they
8795 can be used to authenticate another server as interserver NDS
8796 accesses need it. You must use ncpfs-2.0.12.1 or newer to utilize
8797 this feature. Say Y if you are using NDS connections to NetWare
8798 servers. Do not say Y if security is primary for you because root
8799 can read your session key (from /proc/kcore).
8801 Allow using of Native Language Support
8803 Allows you to use codepages and I/O charsets for file name
8804 translation between the server file system and input/output. This
8805 may be useful, if you want to access the server with other operating
8806 systems, e.g. Windows 95. See also NLS for more Information.
8808 To select codepages and I/O charsets use ncpfs-2.2.0.13 or newer.
8810 Symbolic links and mode permission bits
8812 This enables the use of symbolic links and an execute permission
8813 bit on NCPFS. The file server need not have long name space or NFS
8814 name space loaded for these to work.
8816 To use the new attributes, it is recommended to use the flags
8817 '-f 600 -d 755' on the ncpmount command line.
8820 CONFIG_NLS_CODEPAGE_437
8821 The Microsoft fat filesystem family can deal with filenames in
8822 native language character sets. These character sets are stored
8823 in so-called DOS codepages. You need to include the appropriate
8824 codepage if you want to be able to read/write these filenames on
8825 DOS/Windows partitions correctly. This does apply to the filenames
8826 only, not to the file contents. You can include several codepages;
8827 say Y here if you want to include the DOS codepage that is used in
8828 the United States and parts of Canada. This is recommended.
8831 CONFIG_NLS_CODEPAGE_737
8832 The Microsoft fat filesystem family can deal with filenames in
8833 native language character sets. These character sets are stored
8834 in so-called DOS codepages. You need to include the appropriate
8835 codepage if you want to be able to read/write these filenames on
8836 DOS/Windows partitions correctly. This does apply to the filenames
8837 only, not to the file contents. You can include several codepages;
8838 say Y here if you want to include the DOS codepage that is used for
8839 Greek. If unsure, say N.
8842 CONFIG_NLS_CODEPAGE_775
8843 The Microsoft fat filesystem family can deal with filenames in
8844 native language character sets. These character sets are stored
8845 in so-called DOS codepages. You need to include the appropriate
8846 codepage if you want to be able to read/write these filenames on
8847 DOS/Windows partitions correctly. This does apply to the filenames
8848 only, not to the file contents. You can include several codepages;
8849 say Y here if you want to include the DOS codepage that is used
8850 for the Baltic Rim Languages. If unsure, say N.
8853 CONFIG_NLS_CODEPAGE_850
8854 The Microsoft fat filesystem family can deal with filenames in
8855 native language character sets. These character sets are stored in
8856 so-called DOS codepages. You need to include the appropriate
8857 codepage if you want to be able to read/write these filenames on
8858 DOS/Windows partitions correctly. This does apply to the filenames
8859 only, not to the file contents. You can include several codepages;
8860 say Y here if you want to include the DOS codepage that is used for
8861 much of Europe -- United Kingdom, Germany, Spain, Italy, and [add
8862 more countries here]. It has some characters useful to many European
8863 languages that are not part of the US codepage 437.
8868 CONFIG_NLS_CODEPAGE_852
8869 The Microsoft fat filesystem family can deal with filenames in
8870 native language character sets. These character sets are stored in
8871 so-called DOS codepages. You need to include the appropriate
8872 codepage if you want to be able to read/write these filenames on
8873 DOS/Windows partitions correctly. This does apply to the filenames
8874 only, not to the file contents. You can include several codepages;
8875 say Y here if you want to include the Latin 2 codepage used by DOS
8876 for much of Central and Eastern Europe. It has all the required
8877 characters for these languages: Albanian, Croatian, Czech, English,
8878 Finnish, Hungarian, Irish, German, Polish, Romanian, Serbian (Latin
8879 transcription), Slovak, Slovenian, and Sorbian.
8882 CONFIG_NLS_CODEPAGE_855
8883 The Microsoft fat filesystem family can deal with filenames in
8884 native language character sets. These character sets are stored in
8885 so-called DOS codepages. You need to include the appropriate
8886 codepage if you want to be able to read/write these filenames on
8887 DOS/Windows partitions correctly. This does apply to the filenames
8888 only, not to the file contents. You can include several codepages;
8889 say Y here if you want to include the DOS codepage for Cyrillic.
8892 CONFIG_NLS_CODEPAGE_857
8893 The Microsoft fat filesystem family can deal with filenames in
8894 native language character sets. These character sets are stored in
8895 so-called DOS codepages. You need to include the appropriate
8896 codepage if you want to be able to read/write these filenames on
8897 DOS/Windows partitions correctly. This does apply to the filenames
8898 only, not to the file contents. You can include several codepages;
8899 say Y here if you want to include the DOS codepage for Turkish.
8902 CONFIG_NLS_CODEPAGE_860
8903 The Microsoft fat filesystem family can deal with filenames in
8904 native language character sets. These character sets are stored in
8905 so-called DOS codepages. You need to include the appropriate
8906 codepage if you want to be able to read/write these filenames on
8907 DOS/Windows partitions correctly. This does apply to the filenames
8908 only, not to the file contents. You can include several codepages;
8909 say Y here if you want to include the DOS codepage for Portuguese.
8912 CONFIG_NLS_CODEPAGE_861
8913 The Microsoft fat filesystem family can deal with filenames in
8914 native language character sets. These character sets are stored in
8915 so-called DOS codepages. You need to include the appropriate
8916 codepage if you want to be able to read/write these filenames on
8917 DOS/Windows partitions correctly. This does apply to the filenames
8918 only, not to the file contents. You can include several codepages;
8919 say Y here if you want to include the DOS codepage for Icelandic.
8922 CONFIG_NLS_CODEPAGE_862
8923 The Microsoft fat filesystem family can deal with filenames in
8924 native language character sets. These character sets are stored in
8925 so-called DOS codepages. You need to include the appropriate
8926 codepage if you want to be able to read/write these filenames on
8927 DOS/Windows partitions correctly. This does apply to the filenames
8928 only, not to the file contents. You can include several codepages;
8929 say Y here if you want to include the DOS codepage for Hebrew.
8932 CONFIG_NLS_CODEPAGE_863
8933 The Microsoft fat filesystem family can deal with filenames in
8934 native language character sets. These character sets are stored in
8935 so-called DOS codepages. You need to include the appropriate
8936 codepage if you want to be able to read/write these filenames on
8937 DOS/Windows partitions correctly. This does apply to the filenames
8938 only, not to the file contents. You can include several codepages;
8939 say Y here if you want to include the DOS codepage for Canadian
8943 CONFIG_NLS_CODEPAGE_864
8944 The Microsoft fat filesystem family can deal with filenames in
8945 native language character sets. These character sets are stored in
8946 so-called DOS codepages. You need to include the appropriate
8947 codepage if you want to be able to read/write these filenames on
8948 DOS/Windows partitions correctly. This does apply to the filenames
8949 only, not to the file contents. You can include several codepages;
8950 say Y here if you want to include the DOS codepage for Arabic.
8953 CONFIG_NLS_CODEPAGE_865
8954 The Microsoft fat filesystem family can deal with filenames in
8955 native language character sets. These character sets are stored in
8956 so-called DOS codepages. You need to include the appropriate
8957 codepage if you want to be able to read/write these filenames on
8958 DOS/Windows partitions correctly. This does apply to the filenames
8959 only, not to the file contents. You can include several codepages;
8960 say Y here if you want to include the DOS codepage for the Nordic
8964 CONFIG_NLS_CODEPAGE_866
8965 The Microsoft fat filesystem family can deal with filenames in
8966 native language character sets. These character sets are stored in
8967 so-called DOS codepages. You need to include the appropriate
8968 codepage if you want to be able to read/write these filenames on
8969 DOS/Windows partitions correctly. This does apply to the filenames
8970 only, not to the file contents. You can include several codepages;
8971 say Y here if you want to include the DOS codepage for
8975 CONFIG_NLS_CODEPAGE_869
8976 The Microsoft fat filesystem family can deal with filenames in
8977 native language character sets. These character sets are stored in
8978 so-called DOS codepages. You need to include the appropriate
8979 codepage if you want to be able to read/write these filenames on
8980 DOS/Windows partitions correctly. This does apply to the filenames
8981 only, not to the file contents. You can include several codepages;
8982 say Y here if you want to include the DOS codepage for Greek.
8984 ### Why do we have two codepages for Greek and Cyrillic?
8988 CONFIG_NLS_CODEPAGE_874
8989 The Microsoft fat filesystem family can deal with filenames in
8990 native language character sets. These character sets are stored in
8991 so-called DOS codepages. You need to include the appropriate
8992 codepage if you want to be able to read/write these filenames on
8993 DOS/Windows partitions correctly. This does apply to the filenames
8994 only, not to the file contents. You can include several codepages;
8995 say Y here if you want to include the DOS codepage for Thai.
8998 CONFIG_NLS_ISO8859_1
8999 If you want to display filenames with native language characters
9000 from the Microsoft fat filesystem family or from JOLIET CDROMs
9001 correctly on the screen, you need to include the appropriate
9002 input/output character sets. Say Y here for the Latin 1 character
9003 set, which covers most West European languages such as Albanian,
9004 Catalan, Danish, Dutch, English, Faeroese, Finnish, French, German,
9005 Galician, Irish, Icelandic, Italian, Norwegian, Portuguese, Spanish,
9006 and Swedish. It is also the default for the US. If unsure, say Y.
9009 CONFIG_NLS_ISO8859_2
9010 If you want to display filenames with native language characters
9011 from the Microsoft fat filesystem family or from JOLIET CDROMs
9012 correctly on the screen, you need to include the appropriate
9013 input/output character sets. Say Y here for the Latin 2 character
9014 set, which works for most Latin-written Slavic and Central European
9015 languages: Czech, German, Hungarian, Polish, Rumanian, Croatian,
9019 CONFIG_NLS_ISO8859_3
9020 If you want to display filenames with native language characters
9021 from the Microsoft fat filesystem family or from JOLIET CDROMs
9022 correctly on the screen, you need to include the appropriate
9023 input/output character sets. Say Y here for the Latin 3 character
9024 set, which is popular with authors of Esperanto, Galician, Maltese,
9028 CONFIG_NLS_ISO8859_4
9029 If you want to display filenames with native language characters
9030 from the Microsoft fat filesystem family or from JOLIET CDROMs
9031 correctly on the screen, you need to include the appropriate
9032 input/output character sets. Say Y here for the Latin 4 character
9033 set which introduces letters for Estonian, Latvian, and
9034 Lithuanian. It is an incomplete predecessor of Latin 6.
9037 CONFIG_NLS_ISO8859_5
9038 If you want to display filenames with native language characters
9039 from the Microsoft fat filesystem family or from JOLIET CDROMs
9040 correctly on the screen, you need to include the appropriate
9041 input/output character sets. Say Y here for ISO8859-5, a Cyrillic
9042 character set with which you can type Bulgarian, Byelorussian,
9043 Macedonian, Russian, Serbian, and Ukrainian. Note that the charset
9044 KOI8-R is preferred in Russia.
9047 CONFIG_NLS_ISO8859_6
9048 If you want to display filenames with native language characters
9049 from the Microsoft fat filesystem family or from JOLIET CDROMs
9050 correctly on the screen, you need to include the appropriate
9051 input/output character sets. Say Y here for ISO8859-6, the Arabic
9055 CONFIG_NLS_ISO8859_7
9056 If you want to display filenames with native language characters
9057 from the Microsoft fat filesystem family or from JOLIET CDROMs
9058 correctly on the screen, you need to include the appropriate
9059 input/output character sets. Say Y here for ISO8859-7, the Modern
9060 Greek character set.
9063 CONFIG_NLS_ISO8859_8
9064 If you want to display filenames with native language characters
9065 from the Microsoft fat filesystem family or from JOLIET CDROMs
9066 correctly on the screen, you need to include the appropriate
9067 input/output character sets. Say Y here for ISO8859-8, the Hebrew
9071 CONFIG_NLS_ISO8859_9
9072 If you want to display filenames with native language characters
9073 from the Microsoft fat filesystem family or from JOLIET CDROMs
9074 correctly on the screen, you need to include the appropriate
9075 input/output character sets. Say Y here for the Latin 5 character
9076 set, and it replaces the rarely needed Icelandic letters in Latin 1
9077 with the Turkish ones. Useful in Turkey.
9080 CONFIG_NLS_ISO8859_10
9081 If you want to display filenames with native language characters
9082 from the Microsoft fat filesystem family or from JOLIET CDROMs
9083 correctly on the screen, you need to include the appropriate
9084 input/output character sets. Say Y here for the Latin 6 character
9085 set, which adds the last Inuit (Greenlandic) and Sami (Lappish)
9086 letters that were missing in Latin 4 to cover the entire Nordic
9089 NLS ISO 8859-14 (Latin 8; Celtic)
9090 CONFIG_NLS_ISO8859_14
9091 If you want to display filenames with native language characters
9092 from the Microsoft fat filesystem family or from JOLIET CDROMs
9093 correctly on the screen, you need to include the appropriate
9094 input/output character sets. Say Y here for the Latin 8 character
9095 set, which adds the last accented vowels for Welsh (and Manx Gaelic)
9096 that were missing in Latin 1. http://linux.speech.cymru.org/
9097 has further information.
9100 CONFIG_NLS_ISO8859_15
9101 If you want to display filenames with native language characters
9102 from the Microsoft fat filesystem family or from JOLIET CDROMs
9103 correctly on the screen, you need to include the appropriate
9104 input/output character sets. Say Y here for the Latin 9 character
9105 set, which covers most West European languages such as Albanian,
9106 Catalan, Danish, Dutch, English, Estonian, Faeroese, Finnish,
9107 French, German, Galician, Irish, Icelandic, Italian, Norwegian,
9108 Portuguese, Spanish, and Swedish. Latin 9 is an update to
9109 Latin 1 (ISO 8859-1) that removes a handful of rarely used
9110 characters and instead adds support for Estonian, corrects the
9111 support for French and Finnish, and adds the new Euro character. If
9116 If you want to display filenames with native language characters
9117 from the Microsoft fat filesystem family or from JOLIET CDROMs
9118 correctly on the screen, you need to include the appropriate
9119 input/output character sets. Say Y here for the preferred Russian
9124 If you say Y here, you will get support for terminal devices with
9125 display and keyboard devices. These are called "virtual" because you
9126 can run several virtual terminals (also called virtual consoles) on
9127 one physical terminal. This is rather useful, for example one
9128 virtual terminal can collect system messages and warnings, another
9129 one can be used for a text-mode user session, and a third could run
9130 an X session, all in parallel. Switching between virtual terminals
9131 is done with certain key combinations, usually Alt-<function key>.
9133 The setterm command ("man setterm") can be used to change the
9134 properties (such as colors) of a virtual terminal.
9136 You need at least one virtual terminal device in order to make use
9137 of your keyboard and monitor. Therefore, only people configuring an
9138 embedded system would want to say N here in order to save some
9139 memory; the only way to log into such a system is then via a serial
9140 or network connection.
9142 If unsure, say Y, or else you won't be able to do much with your new
9143 shiny Linux system :-)
9145 Support for console on virtual terminal
9147 The system console is the device which receives all kernel messages
9148 and warnings and which allows logins in single user mode. If you
9149 answer Y here, a virtual terminal (the device used to interact with
9150 a physical terminal) can be used as system console. This is the most
9151 common mode of operations, so you should say Y here unless you want
9152 the kernel messages be output only to a serial port (in which case
9153 you should say Y to "Console on serial port", below).
9155 If you do say Y here, by default the currently visible virtual
9156 terminal (/dev/tty0) will be used as system console. You can change
9157 that with a kernel command line option such as "console=tty3" which
9158 would use the third virtual terminal as system console. (Try "man
9159 bootparam" or see the documentation of your boot loader (lilo or
9160 loadlin) about how to pass options to the kernel at boot time. The
9161 lilo procedure is also explained in the SCSI-HOWTO, available from
9162 http://metalab.unc.edu/mdw/linux.html#howto .)
9166 Software generated cursor
9168 If you say Y here, you'll be able to do lots of nice things with the
9169 cursors of your virtual consoles -- for example turn them into
9170 non-blinking block cursors which are more visible on laptop screens,
9171 or change their colors depending on the virtual console they're on.
9172 See Documentation/VGA-softcursor.txt for more information.
9174 Support for PowerMac keyboard
9176 This option allows you to use an ADB keyboard attached to your
9177 machine. Note that this disables any other (ie. PS/2) keyboard
9178 support, even if your machine is physically capable of using both at
9181 If you use an ADB keyboard (4 pin connector), say Y here.
9182 If you use a PS/2 keyboard (6 pin connector), say N here.
9184 Standard/generic serial support
9186 This selects whether you want to include the driver for the standard
9187 serial ports. The standard answer is Y. People who might say N here
9188 are those that are setting up dedicated Ethernet WWW/FTP servers, or
9189 users that have one of the various bus mice instead of a serial
9190 mouse and don't intend to use their machine's standard serial port
9191 for anything. (Note that the Cyclades and Stallion multi serial port
9192 drivers do not need this driver built in for them to work.)
9194 If you want to compile this driver as a module, say M here and read
9195 Documentation/modules.txt. The module will be called serial.o.
9196 [WARNING: Do not compile this driver as a module if you are using
9197 non-standard serial ports, since the configuration information will
9198 be lost when the driver is unloaded. This limitation may be lifted
9201 BTW1: If you have a mouseman serial mouse which is not recognized by
9202 the X window system, try running gpm first.
9204 BTW2: If you intend to use a software modem (also called Winmodem)
9205 under Linux, forget it. These modems are crippled and require
9206 proprietary drivers which are only available under Windows.
9208 Most people will say Y or M here, so that they can use serial mice,
9209 modems and similar devices connecting to the standard serial ports.
9211 Support for console on serial port
9212 CONFIG_SERIAL_CONSOLE
9213 If you say Y here, it will be possible to use a serial port as the
9214 system console (the system console is the device which receives all
9215 kernel messages and warnings and which allows logins in single user
9216 mode). This could be useful if some terminal or printer is connected
9217 to that serial port.
9219 Even if you say Y here, the currently visible virtual console
9220 (/dev/tty0) will still be used as the system console by default, but
9221 you can alter that using a kernel command line option such as
9222 "console=ttyS1". (Try "man bootparam" or see the documentation of
9223 your boot loader (lilo or loadlin) about how to pass options to the
9224 kernel at boot time. The lilo procedure is also explained in the
9225 SCSI-HOWTO, available from
9226 http://metalab.unc.edu/mdw/linux.html#howto .)
9228 If you don't have a VGA card installed and you say Y here, the
9229 kernel will automatically use the first serial line, /dev/ttyS0, as
9234 Support for PowerMac serial ports
9236 If you have Macintosh style serial ports (8 pin mini-DIN), say Y
9237 here. If you also have regular serial ports and enable the driver
9238 for them, you can't currently use the serial console feature.
9240 Comtrol Rocketport support
9242 This is a driver for the Comtrol Rocketport cards which provide
9243 multiple serial ports. You would need something like this to connect
9244 more than two modems to your Linux box, for instance in order to
9245 become a dial-in server.
9247 If you want to compile this driver as a module, say M here and read
9248 Documentation/modules.txt. The module will be called rocket.o.
9250 Digiboard Intelligent async support
9252 This is a driver for Digi International's Xx, Xeve, and Xem series
9253 of cards which provide multiple serial ports. You would need
9254 something like this to connect more than two modems to your Linux
9255 box, for instance in order to become a dial-in server. This driver
9256 supports the original PC (ISA) boards as well as PCI, and EISA. If
9257 you have a card like this, say Y here and read the file
9258 Documentation/digiepca.txt.
9260 NOTE: There is another, separate driver for the Digiboard PC boards:
9261 "Digiboard PC/Xx Support" below. You should (and can) only select
9262 one of the two drivers.
9264 If you want to compile this driver as a module, say M here and read
9265 Documentation/modules.txt. The module will be called epca.o.
9267 Digiboard PC/Xx Support
9269 This is a driver for the Digiboard PC/Xe, PC/Xi, and PC/Xeve cards
9270 that give you many serial ports. You would need something like this
9271 to connect more than two modems to your Linux box, for instance in
9272 order to become a dial-in server. If you have a card like that, say
9273 Y here and read the file Documentation/digiboard.txt.
9275 If you want to compile this driver as a module, say M here and read
9276 Documentation/modules.txt. The module will be called pcxx.o.
9278 SDL RISCom/8 card support
9280 This is a driver for the SDL Communications RISCom/8 multiport card,
9281 which gives you many serial ports. You would need something like
9282 this to connect more than two modems to your Linux box, for instance
9283 in order to become a dial-in server. If you have a card like that,
9284 say Y here and read the file Documentation/riscom8.txt.
9286 Also it's possible to say M here and compile this driver as kernel
9287 loadable module; the module will be called riscom8.o.
9289 Computone IntelliPort Plus serial support
9291 This driver supports the entire family of Intelliport II/Plus
9292 controllers with the exception of the MicroChannel controllers. It
9293 does not support products previous to the Intelliport II. These are
9294 multiport cards, which give you many serial ports. You would need
9295 something like this to connect more than two modems to your Linux
9296 box, for instance in order to become a dial-in server. If you have a
9297 card like that, say Y here and read Documentation/computone.txt.
9299 If you want to compile this as a module ( = code which can be
9300 inserted in and removed from the running kernel whenever you want),
9301 say M here and read Documentation/modules.txt. You will get two
9302 modules called ip2.o and ip2main.o.
9304 Specialix IO8+ card support
9306 This is a driver for the Specialix IO8+ multiport card (both the
9307 ISA and the PCI version) which gives you many serial ports. You
9308 would need something like this to connect more than two modems to
9309 your Linux box, for instance in order to become a dial-in server.
9311 If you have a card like that, say Y here and read the file
9312 Documentation/specialix.txt. Also it's possible to say M here and
9313 compile this driver as kernel loadable module which will be called
9316 Specialix DTR/RTS pin is RTS
9317 CONFIG_SPECIALIX_RTSCTS
9318 The Specialix card can only support either RTS or DTR. If you say N
9319 here, the driver will use the pin as "DTR" when the tty is in
9320 software handshake mode. If you say Y here or hardware handshake is
9321 on, it will always be RTS. Read the file Documentation/specialix.txt
9322 for more information.
9324 Cyclades async mux support
9326 This is a driver for a card that gives you many serial ports. You
9327 would need something like this to connect more than two modems to
9328 your Linux box, for instance in order to become a dial-in server.
9329 For information about the Cyclades-Z card, read
9330 drivers/char/README.cycladesZ.
9332 As of 1.3.9x kernels, this driver's minor numbers start at 0 instead
9335 If you want to compile this as a module ( = code which can be
9336 inserted in and removed from the running kernel whenever you want),
9337 say M here and read Documentation/modules.txt. The module will be
9340 If you haven't heard about it, it's safe to say N.
9342 Cyclades-Z interrupt mode operation (EXPERIMENTAL)
9344 The Cyclades-Z family of multiport cards allows 2 (two) driver
9345 op modes: polling and interrupt. In polling mode, the driver will
9346 check the status of the Cyclades-Z ports every certain amount of
9347 time (which is called polling cycle and is configurable). In
9348 interrupt mode, it will use an interrupt line (IRQ) in order to check
9349 the status of the Cyclades-Z ports. The default op mode is polling.
9352 Stallion multiport serial support
9354 Stallion cards give you many serial ports. You would need something
9355 like this to connect more than two modems to your Linux box, for
9356 instance in order to become a dial-in server. If you say Y here, you
9357 will be asked for your specific card model in the next questions.
9358 Make sure to read drivers/char/README.stallion in this case. If you
9359 have never heard about all this, it's safe to say N.
9361 Stallion EasyIO or EC8/32 support
9363 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
9364 card, then this is for you; say Y. Make sure to read
9365 Documentation/stallion.txt.
9367 If you want to compile this as a module ( = code which can be
9368 inserted in and removed from the running kernel whenever you want),
9369 say M here and read Documentation/modules.txt. The module will be
9372 Stallion EC8/64, ONboard, Brumby support
9374 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
9375 serial multiport card, say Y here. Make sure to read
9376 Documentation/stallion.txt.
9378 To compile it as a module ( = code which can be inserted in and
9379 removed from the running kernel whenever you want), say M here and
9380 read Documentation/modules.txt. The module will be called
9383 Microgate SyncLink adapter support
9385 Provides support for the SyncLink ISA and PCI
9386 multiprotocol serial adapters. These adapters
9387 support asynchronous and HDLC bit synchronous
9388 communication up to 10Mbps (PCI adapter).
9390 This driver can only be built as a module ( = code which can be
9391 inserted in and removed from the running kernel whenever you want).
9392 The module will be called synclink.o. If you want to do that, say M
9395 Synchronous HDLC line discipline support
9397 Allows synchronous HDLC communications with tty device drivers that
9398 support synchronous HDLC such as the Microgate SyncLink adapter.
9400 This driver can only be built as a module ( = code which can be
9401 inserted in and removed from the running kernel whenever you want).
9402 The module will be called n_hdlc.o. If you want to do that, say M
9405 Specialix SX (and SI) card support
9407 This is a driver for the SX and SI multiport serial cards.
9408 Please read the file Documentation/sx.txt for details.
9410 This driver can only be built as a module ( = code which can be
9411 inserted in and removed from the running kernel whenever you want).
9412 The module will be called sx.o. If you want to do that, say M here.
9414 Hayes ESP serial port support
9416 This is a driver which supports Hayes ESP serial ports. Both single
9417 port cards and multiport cards are supported. Make sure to read
9418 Documentation/hayes-esp.txt.
9420 To compile this driver as a module ( = code which can be inserted in
9421 and removed from the running kernel whenever you want), say M here
9422 and read Documentation/modules.txt. The module will be called esp.o.
9425 Multi-Tech multiport card support (EXPERIMENTAL)
9427 This is a driver for the Multi-Tech cards which provide several
9428 serial ports. The driver is experimental and can currently only be
9429 built as a module ( = code which can be inserted in and removed from
9430 the running kernel whenever you want). Please read
9431 Documentation/modules.txt. The module will be called isicom.o
9435 A pseudo terminal (PTY) is a software device consisting of two
9436 halves: a master and a slave. The slave device behaves identical to
9437 a physical terminal; the master device is used by a process to
9438 read data from and write data to the slave, thereby emulating a
9439 terminal. Typical programs for the master side are telnet servers
9442 Linux has traditionally used the BSD-like names /dev/ptyxx for
9443 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
9444 has a number of problems. The GNU C library glibc 2.1 and later,
9445 however, supports the Unix98 naming standard: in order to acquire a
9446 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
9447 terminal is then made available to the process and the pseudo
9448 terminal slave can be accessed as /dev/pts/<number>. What was
9449 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
9451 The entries in /dev/pts/ are created on the fly by a virtual
9452 filesystem; therefore, if you say Y here you should say Y to
9453 "/dev/pts filesystem for Unix98 PTYs" as well.
9455 If you want to say Y here, you need to have the C library glibc 2.1
9456 or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
9457 Read the instructions in Documentation/Changes pertaining to pseudo
9458 terminals. It's safe to say N.
9460 Maximum number of Unix98 PTYs in use (0-2048)
9461 CONFIG_UNIX98_PTY_COUNT
9462 The maximum number of Unix98 PTYs that can be used at any one time.
9463 The default is 256, and should be enough for desktop systems. Server
9464 machines which support incoming telnet/rlogin/ssh connections and/or
9465 serve several X terminals may want to increase this: every incoming
9466 connection and every xterm uses up one PTY.
9468 When not in use, each additional set of 256 PTYs occupy
9469 approximately 8 KB of kernel memory on 32-bit architectures.
9471 Parallel printer support
9473 If you intend to attach a printer to the parallel port of your Linux
9474 box (as opposed to using a serial printer; if the connector at the
9475 printer has 9 or 25 holes ["female"], then it's serial), say Y. Also
9476 read the Printing-HOWTO, available from
9477 http://metalab.unc.edu/mdw/linux.html#howto .
9479 It is possible to share one parallel port among several devices
9480 (e.g. printer and ZIP drive) and it is safe to compile the
9481 corresponding drivers into the kernel. If you want to compile this
9482 driver as a module however ( = code which can be inserted in and
9483 removed from the running kernel whenever you want), say M here and
9484 read Documentation/modules.txt and Documentation/parport.txt. The
9485 module will be called lp.o.
9487 If you have several parallel ports, you can specify which ports to
9488 use with the "lp" kernel command line option. (Try "man bootparam"
9489 or see the documentation of your boot loader (lilo or loadlin) about
9490 how to pass options to the kernel at boot time. The lilo procedure
9491 is also explained in the SCSI-HOWTO, available from
9492 http://metalab.unc.edu/mdw/linux.html#howto .) The syntax of the "lp"
9493 command line option can be found in drivers/char/lp.c.
9495 If you have more than 3 printers, you need to increase the LP_NO
9498 Support for console on line printer
9500 If you want kernel messages to be printed out as they occur, you
9501 can have a console on the printer. This option adds support for
9502 doing that; to actually get it to happen you need to pass the
9503 option "console=lp" to the kernel at boot time.
9505 Note that kernel messages can get lost if the printer is out of
9506 paper (or off, or unplugged, or too busy..), but this behaviour
9507 can be changed. See drivers/char/lp.c (do this at your own risk).
9513 Say Y here if your machine has a bus mouse as opposed to a serial
9514 mouse. Most people have a regular serial MouseSystem or
9515 Microsoft mouse (made by Logitech) that plugs into a COM port
9516 (rectangular with 9 or 25 pins). These people say N here. If you
9517 have something else, read the Busmouse-HOWTO, available from
9518 http://metalab.unc.edu/mdw/linux.html#howto , and say Y here.
9520 If you have a laptop, you either have to check the documentation or
9521 experiment a bit to find out whether the trackball is a serial mouse
9522 or not; it's best to say Y here for you.
9524 This is the generic bus mouse driver code. If you have a bus mouse,
9525 you will have to say Y here and also to the specific driver for your
9528 This code is also available as a module ( = code which can be
9529 inserted in and removed from the running kernel whenever you want).
9530 The module will be called busmouse.o. If you want to compile it as a
9531 module, say M here and read Documentation/modules.txt.
9533 Mouse Support (not serial and bus mice)
9535 This is for machines with a mouse which is neither a serial nor a
9536 bus mouse. Examples are PS/2 mice (such as the track balls on some
9537 laptops) and some digitizer pads. Most people have a regular serial
9538 MouseSystem or Microsoft mouse (made by Logitech) that plugs into a
9539 COM port (rectangular with 9 or 25 pins). These people say N here.
9540 If you have something else, read the Busmouse-HOWTO, available from
9541 http://metalab.unc.edu/mdw/linux.html#howto . This HOWTO contains
9542 information about all non-serial mice, not just bus mice.
9544 If you have a laptop, you either have to check the documentation or
9545 experiment a bit to find out whether the trackball is a serial mouse
9546 or not; it's best to say Y here for you.
9548 Note that the answer to this question won't directly affect the
9549 kernel: saying N will just cause this configure script to skip all
9550 the questions about non-serial mice. If unsure, say Y.
9552 Logitech busmouse support
9554 Logitech mouse connected to a proprietary interface card. It's
9555 generally a round connector with 9 pins. Note that the newer mice
9556 made by Logitech don't use the Logitech protocol anymore; for those,
9557 you don't need this option. You want to read the Busmouse-HOWTO ,
9558 available from http://metalab.unc.edu/mdw/linux.html#howto .
9560 If you want to compile this as a module ( = code which can be
9561 inserted in and removed from the running kernel whenever you want),
9562 say M here and read Documentation/modules.txt. The module will be
9563 called busmouse.o. If you are unsure, say N and read the HOWTO
9564 nevertheless: it will tell you what you have.
9566 PS/2 mouse (aka "auxiliary device") support
9568 The PS/2 mouse connects to a special mouse port that looks much like
9569 the keyboard port (small circular connector with 6 pins). This way,
9570 the mouse does not use any serial ports. This port can also be used
9571 for other input devices like light pens, tablets, keypads. Compaq,
9572 AST and IBM all use this as their mouse port on currently shipping
9573 machines. The trackballs of some laptops are PS/2 mice also. In
9574 particular, the C&T 82C710 mouse on TI Travelmates is a PS/2 mouse.
9576 Although PS/2 mice are not technically bus mice, they are explained
9577 in detail in the Busmouse-HOWTO, available from
9578 http://metalab.unc.edu/mdw/linux.html#howto .
9580 When using a PS/2 mouse, you can get problems if you want to use the
9581 mouse both on the Linux console and under X. Using the "-R" option
9582 of the Linux mouse managing program gpm (available from
9583 ftp://metalab.unc.edu/pub/Linux/system/mouse ) solves this
9584 problem, or you can get the "mconv2" utility from the same location.
9586 C&T 82C710 mouse port support (as on TI Travelmate)
9588 This is a certain kind of PS/2 mouse used on the TI Travelmate. If
9589 you are unsure, try first to say N here and come back if the mouse
9590 doesn't work. Read the Busmouse-HOWTO, available from
9591 http://metalab.unc.edu/mdw/linux.html#howto .
9593 PC110 digitizer pad support
9595 This drives the digitizer pad on the IBM PC110 palmtop. It can turn
9596 the digitizer pad into a PS/2 mouse emulation with tap gestures or
9597 into an absolute pad.
9599 If you want to compile this as a module ( = code which can be
9600 inserted in and removed from the running kernel whenever you want),
9601 say M here and read Documentation/modules.txt. The module will be
9604 Microsoft busmouse support
9606 These animals (also called Inport mice) are connected to an
9607 expansion board using a round connector with 9 pins. If this is what
9608 you have, say Y and read the Busmouse-HOWTO, available from
9609 http://metalab.unc.edu/mdw/linux.html#howto .
9611 If you are unsure, say N and read the HOWTO nevertheless: it will
9612 tell you what you have. Also be aware that several vendors talk
9613 about 'Microsoft busmouse' and actually mean PS/2 busmouse -- so
9614 count the pins on the connector.
9616 If you want to compile this as a module ( = code which can be
9617 inserted in and removed from the running kernel whenever you want),
9618 say M here and read Documentation/modules.txt. The module will be
9619 called msbusmouse.o.
9621 Apple Desktop Bus mouse support
9623 Say Y here if you have this type of bus mouse (4 pin connector) as
9624 is common on Macintoshes. You may want to read the Busmouse-HOWTO,
9625 available from http://metalab.unc.edu/mdw/linux.html#howto .
9627 If you want to compile this as a module ( = code which can be
9628 inserted in and removed from the running kernel whenever you want),
9629 say M here and read Documentation/modules.txt. The module will be
9632 ATIXL busmouse support
9633 CONFIG_ATIXL_BUSMOUSE
9634 This is a rare type of busmouse that is connected to the back of an
9635 ATI video card. Say Y if you have one of those. Note however that
9636 most mice by ATI are actually Microsoft busmice; you should say Y to
9637 "Microsoft busmouse support" above if you have one of those. Read
9638 the Busmouse-HOWTO, available from
9639 http://metalab.unc.edu/mdw/linux.html#howto .
9641 If you want to compile this as a module ( = code which can be
9642 inserted in and removed from the running kernel whenever you want),
9643 say M here and read Documentation/modules.txt. The module will be
9644 called atixlmouse.o.
9646 If you are unsure, say N and read the HOWTO nevertheless: it will
9647 tell you what you have.
9651 If you have a non-SCSI tape drive like that, say Y. Or, if you want
9652 to compile this driver as a module ( = code which can be inserted in
9653 and removed from the running kernel whenever you want), say M here
9654 and read Documentation/modules.txt. The module will be called
9657 Do you want runtime configuration for QIC-02
9658 CONFIG_QIC02_DYNCONF
9659 You can either configure this driver once and for all by editing a
9660 header file (include/linux/tpqic02.h), in which case you should
9661 say N, or you can fetch a program via anonymous FTP which is able
9662 to configure this driver during runtime. The program to do this is
9663 called 'qic02conf' and it is part of the tpqic02-support-X.Y.tar.gz
9666 If you want to use the qic02conf program, say Y.
9668 Floppy tape drive (QIC-80/40/3010/3020/TR-1/TR-2/TR-3) support
9670 If you have a tape drive that is connected to your floppy
9671 controller, say Y here.
9673 Some tape drives (like the Seagate "Tape Store 3200" or the Iomega
9674 "Ditto 3200" or the Exabyte "Eagle TR-3") come with a "high speed"
9675 controller of their own. These drives (and their companion
9676 controllers) are also supported if you say Y here.
9678 If you have a special controller (such as the CMS FC-10, FC-20,
9679 Mountain Mach-II, or any controller that is based on the Intel 82078
9680 FDC like the high speed controllers by Seagate and Exabyte and
9681 Iomega's "Ditto Dash") you must configure it by selecting the
9682 appropriate entries from the "Floppy tape controllers" sub-menu
9683 below and possibly modify the default values for the IRQ and DMA
9684 channel and the IO base in ftape's configuration menu.
9686 If you want to use your floppy tape drive on a PCI-bus based system,
9687 please read the file drivers/char/ftape/README.PCI.
9689 The ftape kernel driver is also available as a runtime loadable
9690 module ( = code which can be inserted in and removed from the
9691 running kernel whenever you want). If you want to compile it as a
9692 module, say M here and read Documentation/modules.txt. The module
9693 will be called ftape.o.
9695 Note that the Ftape-HOWTO is out of date (sorry) and documents the
9696 older version 2.08 of this software but still contains useful
9697 information. There is a web page with more recent documentation at
9698 http://www.math1.rwth-aachen.de/~heine/ftape/ . This page
9699 always contains the latest release of the ftape driver and useful
9700 information (backup software, ftape related patches and
9701 documentation, FAQ). Note that the file system interface has changed
9702 quite a bit compared to previous versions of ftape. Please read
9703 Documentation/ftape.txt.
9705 The file system interface for ftape
9707 Normally, you want to say Y or M. DON'T say N here or you
9708 WON'T BE ABLE TO USE YOUR FLOPPY TAPE DRIVE.
9710 The ftape module itself no longer contains the routines necessary
9711 to interface with the kernel VFS layer (i.e. to actually write data
9712 to and read data from the tape drive). Instead the file system
9713 interface (i.e. the hardware independent part of the driver) has
9714 been moved to a separate module.
9716 If you say M zftape will be compiled as a runtime loadable
9717 module ( = code which can be inserted in and removed from the
9718 running kernel whenever you want). In this case you should read
9719 Documentation/modules.txt. The module will be called zftape.o.
9721 Regardless of whether you say Y or M here, an additional runtime
9722 loadable module called `zft-compressor.o' which contains code to
9723 support user transparent on-the-fly compression based on Ross
9724 William's lzrw3 algorithm will be produced. If you have enabled the
9725 kernel module loader (i.e. have said Y to "Kernel module loader
9726 support", above) then `zft-compressor.o' will be loaded
9727 automatically by zftape when needed.
9729 Despite its name, zftape does NOT use compression by default. The
9730 file Documentation/ftape.txt contains a short description of the
9731 most important changes in the file system interface compared to
9732 previous versions of ftape. The ftape home page
9733 http://www-math.math.rwth-aachen.de/~LBFM/claus/ftape/ contains
9734 further information.
9736 IMPORTANT NOTE: zftape can read archives created by previous
9737 versions of ftape and provide file mark support (i.e. fast skipping
9738 between tape archives) but previous version of ftape will lack file
9739 mark support when reading archives produced by zftape.
9741 Default block size for zftape
9742 CONFIG_ZFT_DFLT_BLK_SZ
9743 If unsure leave this at its default value, i.e. 10240. Note that
9744 you specify only the default block size here. The block size can be
9745 changed at run time using the MTSETBLK tape operation with the
9746 MTIOCTOP ioctl (i.e. with "mt -f /dev/qft0 setblk #BLKSZ" from the
9747 shell command line).
9749 The probably most striking difference between zftape and previous
9750 versions of ftape is the fact that all data must be written or read
9751 in multiples of a fixed block size. The block size defaults to
9752 10240 which is what GNU tar uses. The values for the block size
9753 should be either 1 or multiples of 1024 up to a maximum value of
9754 63488 (i.e. 62 K). If you specify `1' then zftape's builtin
9755 compression will be disabled.
9757 Reasonable values are `10240' (GNU tar's default block size),
9758 `5120' (afio's default block size), `32768' (default block size some
9759 backup programs assume for SCSI tape drives) or `1' (no restriction
9760 on block size, but disables builtin compression).
9762 Number of DMA buffers
9763 CONFIG_FT_NR_BUFFERS
9764 Please leave this at `3' unless you REALLY know what you are doing.
9765 It is not necessary to change this value. Values below 3 make the
9766 proper use of ftape impossible, values greater than 3 are a waste of
9767 memory. You can change the amount of DMA memory used by ftape at
9768 runtime with "mt -f /dev/qft0 setdrvbuffer #NUMBUFFERS". Each buffer
9769 wastes 32 KB of memory. Please note that this memory cannot be
9772 Procfs entry for ftape
9774 Optional. Saying Y will result in creation of a directory
9775 `/proc/ftape' under the proc file system. The files can be viewed
9776 with your favorite pager (i.e. use "more /proc/ftape/history" or
9777 "less /proc/ftape/history" or simply "cat /proc/ftape/history"). The
9778 file will contain some status information about the inserted
9779 cartridge, the kernel driver, your tape drive, the floppy disk
9780 controller and the error history for the most recent use of the
9781 kernel driver. Saying Y will enlarge the size of the ftape driver
9782 by approximately 2 KB.
9784 WARNING: When compiling ftape as a module (i.e. saying M to
9785 "Floppy tape drive") it is dangerous to use ftape's proc file system
9786 interface. Accessing `/proc/ftape' while the module is unloaded will
9787 result in a kernel Oops. This cannot be fixed from inside ftape.
9789 Controlling the amount of debugging output of ftape
9790 CONFIG_FT_NORMAL_DEBUG
9791 This option controls the amount of debugging output the ftape driver
9792 is ABLE to produce; it does not increase or diminish the debugging
9793 level itself. If unsure, leave this at its default setting,
9794 i.e. choose "Normal".
9796 Ftape can print lots of debugging messages to the system console
9797 resp. kernel log files. Reducing the amount of possible debugging
9798 output reduces the size of the kernel module by some KB, so it might
9799 be a good idea to use "None" for emergency boot floppies.
9801 If you want to save memory then the following strategy is
9802 recommended: leave this option at its default setting "Normal" until
9803 you know that the driver works as expected, afterwards reconfigure
9804 the kernel, this time specifying "Reduced" or "None" and recompile
9805 and install the kernel as usual. Note that choosing "Excessive"
9806 debugging output does not increase the amount of debugging output
9807 printed to the console but only makes it possible to produce
9808 "Excessive" debugging output.
9810 Please read Documentation/ftape.txt for a short description
9811 how to control the amount of debugging output.
9813 The floppy drive controller for ftape
9815 Only change this setting if you have a special controller. If you
9816 didn't plug any add-on card into your computer system but just
9817 plugged the floppy tape cable into the already existing floppy drive
9818 controller then you don't want to change the default setting,
9819 i.e. choose "Standard".
9821 Choose "MACH-2" if you have a Mountain Mach-2 controller.
9822 Choose "FC-10/FC-20" if you have a Colorado FC-10 or FC-20
9824 Choose "Alt/82078" if you have another controller that is located at
9825 an IO base address different from the standard floppy drive
9826 controller's base address of `0x3f0', or uses an IRQ (interrupt)
9827 channel different from `6', or a DMA channel different from
9828 `2'. This is necessary for any controller card that is based on
9829 Intel's 82078 FDC such as Seagate's, Exabyte's and Iomega's "high
9832 If you choose something other than "Standard" then please make
9833 sure that the settings for the IO base address and the IRQ and DMA
9834 channel in the configuration menus below are correct. Use the manual
9835 of your tape drive to determine the correct settings!
9837 If you are already successfully using your tape drive with another
9838 operating system then you definitely should use the same settings
9839 for the IO base, the IRQ and DMA channel that have proven to work
9842 Note that this menu lets you specify only the default setting for
9843 the hardware setup. The hardware configuration can be changed at
9844 boot time (when ftape is compiled into the kernel, i.e. if you
9845 have said Y to "Floppy tape drive") or module load time (i.e. if you
9846 have said M to "Floppy tape drive").
9848 Please read also the file Documentation/ftape.txt which
9849 contains a short description of the parameters that can be set at
9850 boot or load time. If you want to use your floppy tape drive on a
9851 PCI-bus based system, please read the file
9852 drivers/char/ftape/README.PCI.
9854 IO base of the floppy disk controller used with Ftape
9856 You don't need to specify a value if the following default
9857 settings for the base IO address are correct:
9858 <<< MACH-2 : 0x1E0 >>>
9859 <<< FC-10/FC-20: 0x180 >>>
9860 <<< Secondary : 0x370 >>>
9861 Secondary refers to a secondary FDC controller like the "high speed"
9862 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
9863 Please make sure that the setting for the IO base address
9864 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
9865 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
9866 successfully using the tape drive with another operating system then
9867 you definitely should use the same settings for the IO base that has
9868 proven to work with that other OS.
9870 Note that this menu lets you specify only the default setting for
9871 the IO base. The hardware configuration can be changed at boot time
9872 (when ftape is compiled into the kernel, i.e. if you specified Y to
9873 "Floppy tape drive") or module load time (i.e. if you have said M to
9874 "Floppy tape drive").
9876 Please read also the file Documentation/ftape.txt which contains a
9877 short description of the parameters that can be set at boot or load
9880 IRQ channel for the floppy disk controller used with Ftape
9882 You don't need to specify a value if the following default
9883 settings for the interrupt channel are correct:
9885 <<< FC-10/FC-20: 9 >>>
9886 <<< Secondary : 6 >>>
9887 Secondary refers to secondary a FDC controller like the "high speed"
9888 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
9889 Please make sure that the setting for the IO base address
9890 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
9891 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
9892 successfully using the tape drive with another operating system then
9893 you definitely should use the same settings for the IO base that has
9894 proven to work with that other OS.
9896 Note that this menu lets you specify only the default setting for
9897 the IRQ channel. The hardware configuration can be changed at boot
9898 time (when ftape is compiled into the kernel, i.e. if you said Y to
9899 "Floppy tape drive") or module load time (i.e. if you said M to
9900 "Floppy tape drive").
9902 Please read also the file Documentation/ftape.txt which contains a
9903 short description of the parameters that can be set at boot or load
9906 DMA channel for the floppy disk controller used with Ftape
9908 You don't need to specify a value if the following default
9909 settings for the DMA channel are correct:
9911 <<< FC-10/FC-20: 3 >>>
9912 <<< Secondary : 2 >>>
9913 Secondary refers to a secondary FDC controller like the "high speed"
9914 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
9915 Please make sure that the setting for the IO base address
9916 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
9917 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
9918 successfully using the tape drive with another operating system then
9919 you definitely should use the same settings for the IO base that has
9920 proven to work with that other OS.
9922 Note that this menu lets you specify only the default setting for
9923 the DMA channel. The hardware configuration can be changed at boot
9924 time (when ftape is compiled into the kernel, i.e. if you said Y to
9925 "Floppy tape drive") or module load time (i.e. if you said M to
9926 "Floppy tape drive").
9928 Please read also the file Documentation/ftape.txt which contains a
9929 short description of the parameters that can be set at boot or load
9932 FDC FIFO Threshold before requesting DMA service
9934 Set the FIFO threshold of the FDC. If this is higher the DMA
9935 controller may serve the FDC after a higher latency time. If this is
9936 lower, fewer DMA transfers occur leading to less bus contention.
9937 You may try to tune this if ftape annoys you with "reduced data
9938 rate because of excessive overrun errors" messages. However, this
9939 doesn't seem to have too much effect.
9941 If unsure, don't touch the initial value, i.e. leave it at "8".
9943 FDC maximum data rate
9944 CONFIG_FT_FDC_MAX_RATE
9945 With some motherboard/FDC combinations ftape will not be able to
9946 run your FDC/tape drive combination at the highest available
9947 speed. If this is the case you'll encounter "reduced data rate
9948 because of excessive overrun errors" messages and lots of retries
9949 before ftape finally decides to reduce the data rate.
9951 In this case it might be desirable to tell ftape beforehand that
9952 it need not try to run the tape drive at the highest available
9953 speed. If unsure, leave this disabled, i.e. leave it at 2000
9956 Direct Rendering Manager (XFree86 DRI support)
9958 Kernel-level support for the Direct Rendering Infrastructure (DRI)
9959 introduced in XFree86 4.x. These modules provide support for
9960 synchronization, security, and DMA transfers. Select the module that
9961 provides support for your graphics card.
9963 3dlabs GMX 2000 Direct Rendering Driver (XFree86 DRI support)
9965 Choose M here if you have a 3dlabs GMX 2000 graphics card.
9967 MTRR control and configuration
9969 On Intel P6 family processors (Pentium Pro, Pentium II and later)
9970 the Memory Type Range Registers (MTRRs) may be used to control
9971 processor access to memory ranges. This is most useful when you have
9972 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
9973 allows bus write transfers to be combined into a larger transfer
9974 before bursting over the PCI/AGP bus. This can increase performance
9975 of image write operations 2.5 times or more. This option creates a
9976 /proc/mtrr file which may be used to manipulate your
9977 MTRRs. Typically the X server should use this. This should have a
9978 reasonably generic interface so that similar control registers on
9979 other processors can be easily supported.
9981 The Cyrix 6x86, 6x86MX and M II processors have Address Range
9982 Registers (ARRs) which provide a similar functionality to MTRRs. For
9983 these, the ARRs are used to emulate the MTRRs, which means that it
9984 makes sense to say Y here for these processors as well.
9986 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
9987 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
9988 write-combining. All of these processors are supported by this code.
9990 The Centaur C6 (WinChip) has 8 MCRs, allowing write-combining. These
9993 Saying Y here also fixes a problem with buggy SMP BIOSes which only
9994 set the MTRRs for the boot CPU and not the secondary CPUs. This can
9995 lead to all sorts of problems.
9997 You can safely say Y even if your machine doesn't have MTRRs, you'll
9998 just add about 9K to your kernel.
10000 See Documentation/mtrr.txt for more information.
10002 Main CPU frequency, only for DEC alpha machine
10003 CONFIG_FT_ALPHA_CLOCK
10004 On some DEC Alpha machines the CPU clock frequency cannot be
10005 determined automatically, so you need to specify it here ONLY if
10006 running a DEC Alpha, otherwise this setting has no effect.
10008 Zilog serial support
10010 This driver does not exist at this point, so you might as well
10013 Double Talk PC internal speech card support
10015 This driver is for the DoubleTalk PC, a speech synthesizer
10016 manufactured by RC Systems (http://www.rcsys.com/ ). It is also
10017 called the `internal DoubleTalk'. If you want to compile this as a
10018 module ( = code which can be inserted in and removed from the
10019 running kernel whenever you want), say M here and read
10020 Documentation/modules.txt. The module will be called dtlk.o.
10022 Siemens R3964 serial protocol support
10024 This driver allows synchronous communication with devices using the
10025 Siemens R3964 packet protocol. Unless you are dealing with special
10026 hardware like PLCs, you are unlikely to need this.
10028 To compile this driver as a module ( = code which can be inserted in
10029 and removed from the running kernel whenever you want), say M here
10030 and read Documentation/modules.txt. The module will be called
10035 Applicom intelligent fieldbus card support
10037 This driver provides the kernel-side support for the intelligent
10038 fieldbus cards made by Applicom International. More information
10039 about these cards can be found on the WWW at the address
10040 http://www.applicom-int.com/ , or by email from David Woodhouse
10043 To compile this driver as a module ( = code which can be inserted in
10044 and removed from the running kernel whenever you want), say M here
10045 and read Documentation/modules.txt. The module will be called
10050 Advanced Power Management
10052 APM is a BIOS specification for saving power using several different
10053 techniques. This is mostly useful for battery powered laptops with
10054 APM compliant BIOSes. If you say Y here, the system time will be
10055 reset after a RESUME operation, the /proc/apm device will provide
10056 battery status information, and user-space programs will receive
10057 notification of APM "events" (e.g. battery status change).
10059 If you select "Y" here, you can disable actual use of the APM
10060 BIOS by passing the "apm=off" option to the kernel at boot time.
10062 Note that the APM support is almost completely disabled for
10063 machines with more than one CPU.
10065 Supporting software is available; for more information, read the
10066 Battery Powered Linux mini-HOWTO, available from
10067 http://metalab.unc.edu/mdw/linux.html#howto .
10069 This driver does not spin down disk drives (see the hdparm(8)
10070 manpage ("man 8 hdparm") for that), and it doesn't turn off
10071 VESA-compliant "green" monitors.
10073 This driver does not support the TI 4000M TravelMate and the ACER
10074 486/DX4/75 because they don't have compliant BIOSes. Many "green"
10075 desktop machines also don't have compliant BIOSes, and this driver
10076 may cause those machines to panic during the boot phase.
10078 If you are running Linux on a laptop, you may also want to read the
10079 Linux Laptop home page on the WWW at
10080 http://www.cs.utexas.edu/users/kharker/linux-laptop/ .
10082 Generally, if you don't have a battery in your machine, there isn't
10083 much point in using this driver and you should say N. If you get
10084 random kernel OOPSes or reboots that don't seem to be related to
10085 anything, try disabling/enabling this option (or disabling/enabling
10088 Some other things you should try when experiencing seemingly random,
10091 1) make sure that you have enough swap space and that it is
10093 2) pass the "no-hlt" option to the kernel
10094 3) switch on floating point emulation in the kernel and pass
10095 the "no387" option to the kernel
10096 4) pass the "floppy=nodma" option to the kernel
10097 5) pass the "mem=4M" option to the kernel (thereby disabling
10098 all but the first 4 MB of RAM)
10099 6) make sure that the CPU is not over clocked.
10100 7) read the sig11 FAQ at http://www.bitwizard.nl/sig11/
10101 8) disable the cache from your BIOS settings
10102 9) install a fan for the video card or exchange video RAM
10103 10) install a better fan for the CPU
10104 11) exchange RAM chips
10105 12) exchange the motherboard.
10107 This driver is also available as a module ( = code which can be
10108 inserted in and removed from the running kernel whenever you want).
10109 If you want to compile it as a module, say M here and read
10110 Documentation/modules.txt. The module will be called apm.o.
10112 Ignore USER SUSPEND
10113 CONFIG_APM_IGNORE_USER_SUSPEND
10114 This option will ignore USER SUSPEND requests. On machines with a
10115 compliant APM BIOS, you want to say N. However, on the NEC Versa M
10116 series notebooks, it is necessary to say Y because of a BIOS bug.
10118 Enable APM at boot time
10119 CONFIG_APM_DO_ENABLE
10120 Enable APM features at boot time. From page 36 of the APM BIOS
10121 specification: "When disabled, the APM BIOS does not automatically
10122 power manage devices, enter the Standby State, enter the Suspend
10123 State, or take power saving steps in response to CPU Idle calls."
10124 This driver will make CPU Idle calls when Linux is idle (unless this
10125 feature is turned off -- see "Do CPU IDLE calls", below). This
10126 should always save battery power, but more complicated APM features
10127 will be dependent on your BIOS implementation. You may need to turn
10128 this option off if your computer hangs at boot time when using APM
10129 support, or if it beeps continuously instead of suspending. Turn
10130 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
10131 T400CDT. This is off by default since most machines do fine without
10135 CONFIG_APM_CPU_IDLE
10136 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
10137 On some machines, this can activate improved power savings, such as
10138 a slowed CPU clock rate, when the machine is idle. These idle calls
10139 are made after the idle loop has run for some length of time (e.g.,
10140 333 mS). On some machines, this will cause a hang at boot time or
10141 whenever the CPU becomes idle. (On machines with more than one CPU,
10142 this option does nothing.)
10144 Enable console blanking using APM
10145 CONFIG_APM_DISPLAY_BLANK
10146 Enable console blanking using the APM. Some laptops can use this to
10147 turn off the LCD backlight when the screen blanker of the Linux
10148 virtual console blanks the screen. Note that this is only used by
10149 the virtual console screen blanker, and won't turn off the backlight
10150 when using the X Window system. This also doesn't have anything to
10151 do with your VESA-compliant power-saving monitor. Further, this
10152 option doesn't work for all laptops -- it might not turn off your
10153 backlight at all, or it might print a lot of errors to the console,
10154 especially if you are using gpm.
10156 Power off on shutdown
10157 CONFIG_APM_POWER_OFF
10158 Enable the ability to power off the computer after the Linux kernel
10159 is halted. You will need software (e.g., a suitable version of the
10160 halt(8) command ("man 8 halt")) to cause the computer to power down.
10161 Recent versions of the sysvinit package available from
10162 ftp://metalab.unc.edu/pub/Linux/system/daemons/init/ contain support
10163 for this ("halt -p" shuts down Linux and powers off the computer, if
10164 executed from runlevel 0). As with the other APM options, this
10165 option may not work reliably with some APM BIOS implementations.
10167 Ignore multiple suspend/standby events
10168 CONFIG_APM_IGNORE_MULTIPLE_SUSPEND
10169 This option is necessary on the IBM Thinkpad 560, but should work on
10170 all other laptops. When the APM BIOS returns multiple suspend or
10171 standby events while one is already being processed they will be
10172 ignored. Without this the Thinkpad 560 has troubles with the user
10173 level daemon apmd, and with the PCMCIA package pcmcia-cs.
10175 Ignore multiple suspend/resume cycles
10176 CONFIG_APM_IGNORE_SUSPEND_BOUNCE
10177 This option is necessary on the Dell Inspiron 3200 and others, but
10178 should be safe for all other laptops. When enabled, a system suspend
10179 event that occurs within three seconds of a resume is ignored.
10180 Without this the Inspiron will shut itself off a few seconds after
10181 you open the lid, requiring you to press the power button to resume
10182 it a second time. Say Y.
10184 RTC stores time in GMT
10185 CONFIG_APM_RTC_IS_GMT
10186 Say Y here if your RTC (Real Time Clock a.k.a. hardware clock)
10187 stores the time in GMT (Greenwich Mean Time). Say N if your RTC
10190 It is in fact recommended to store GMT in your RTC, because then you
10191 don't have to worry about daylight savings time changes. The only
10192 reason not to use GMT in your RTC is if you also run a broken OS
10193 that doesn't understand GMT.
10195 Allow interrupts during APM BIOS calls
10196 CONFIG_APM_ALLOW_INTS
10197 Normally we disable external interrupts while we are making calls to
10198 the APM BIOS as a measure to lessen the effects of a badly behaving
10199 BIOS implementation. The BIOS should reenable interrupts if it
10200 needs to. Unfortunately, some BIOSes do not - especially those in
10201 many of the newer IBM Thinkpads. If you experience hangs when you
10202 suspend, try setting this to Y. Otherwise, say N.
10204 Watchdog Timer Support
10206 If you say Y here (and to one of the following options) and create a
10207 character special file /dev/watchdog with major number 10 and minor
10208 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
10209 subsequently opening the file and then failing to write to it for
10210 longer than 1 minute will result in rebooting the machine. This
10211 could be useful for a networked machine that needs to come back
10212 online as fast as possible after a lock-up. There's both a watchdog
10213 implementation entirely in software (which can sometimes fail to
10214 reboot the machine) and a driver for hardware watchdog boards, which
10215 are more robust and can also keep track of the temperature inside
10216 your computer. For details, read Documentation/watchdog.txt in the
10219 The watchdog is usually used together with the watchdog daemon
10220 which is available via FTP (user: anonymous) from
10221 ftp://tsx-11.mit.edu/pub/linux/sources/sbin/ . This daemon can also
10222 monitor NFS connections and can reboot the machine when the process
10227 Disable watchdog shutdown on close
10228 CONFIG_WATCHDOG_NOWAYOUT
10229 The default watchdog behaviour (which you get if you say N here) is
10230 to stop the timer if the process managing it closes the file
10231 /dev/watchdog. It's always remotely possible that this process might
10232 get killed. If you say Y here, the watchdog cannot be stopped once
10233 it has been started.
10237 If you have a WDT500P or WDT501P watchdog board, say Y here,
10238 otherwise N. It is not possible to probe for this board, which means
10239 that you have to set the IO port and IRQ it uses in the kernel
10240 source at the top of drivers/char/wdt.c.
10242 If you want to compile this as a module ( = code which can be
10243 inserted in and removed from the running kernel whenever you want),
10244 say M here and read Documentation/modules.txt. The module will be
10249 Saying Y here and creating a character special file /dev/temperature
10250 with major number 10 and minor number 131 ("man mknod") will give
10251 you a thermometer inside your computer: reading from
10252 /dev/temperature yields one byte, the temperature in degrees
10253 Fahrenheit. This works only if you have a WDT501P watchdog board
10258 Enable the Fan Tachometer on the WDT501. Only do this if you have a
10259 fan tachometer actually set up.
10262 CONFIG_SOFT_WATCHDOG
10263 A software monitoring watchdog. This will fail to reboot your system
10264 from some situations that the hardware watchdog will recover
10265 from. Equally it's a lot cheaper to install.
10267 This driver is also available as a module ( = code which can be
10268 inserted in and removed from the running kernel whenever you want).
10269 If you want to compile it as a module, say M here and read
10270 Documentation/modules.txt. The module will be called softdog.o.
10272 Berkshire Products PC Watchdog
10274 This is the driver for the Berkshire Products PC Watchdog card.
10275 This card simply watches your kernel to make sure it doesn't freeze,
10276 and if it does, it reboots your computer after a certain amount of
10277 time. This driver is like the WDT501 driver but for different
10278 hardware. Please read Documentation/pcwd-watchdog.txt. The PC
10279 watchdog cards can be ordered from http://www.berkprod.com .
10281 This driver is also available as a module ( = code which can be
10282 inserted in and removed from the running kernel whenever you want).
10283 The module is called pcwd.o. If you want to compile it as a module,
10284 say M here and read Documentation/modules.txt.
10286 Most people will say N.
10288 Acquire SBC Watchdog Timer
10290 This is the driver for the hardware watchdog on the PSC-6x86 Single
10291 Board Computer produced by Acquire Inc (and others). This watchdog
10292 simply watches your kernel to make sure it doesn't freeze, and if
10293 it does, it reboots your computer after a certain amount of time.
10295 This driver is like the WDT501 driver but for different hardware.
10296 This driver is also available as a module ( = code which can be
10297 inserted in and removed from the running kernel whenever you want).
10298 The module is called pscwdt.o. If you want to compile it as a
10299 module, say M here and read Documentation/modules.txt. Most people
10302 Enhanced Real Time Clock Support
10304 If you say Y here and create a character special file /dev/rtc with
10305 major number 10 and minor number 135 using mknod ("man mknod"), you
10306 will get access to the real time clock built into your computer.
10307 Every PC has such a clock built in. It can be used to generate
10308 signals from as low as 1Hz up to 8192Hz, and can also be used as a
10309 24 hour alarm. It reports status information via the file /proc/rtc
10310 and its behaviour is set by various ioctls on /dev/rtc.
10312 If you run Linux on a multiprocessor machine and said Y to
10313 "Symmetric Multi Processing" above, you should say Y here to read
10314 and set the RTC in an SMP compatible fashion.
10316 If you think you have a use for such a device (such as periodic data
10317 sampling), then say Y here, and read Documentation/rtc.txt for
10320 Tadpole ANA H8 Support
10322 The Hitachi H8/337 is a microcontroller used to deal with the power
10323 and thermal environment. If you say Y here, you will be able to
10324 communicate with it via a character special device.
10330 If you say Y here and create a character special file /dev/nvram
10331 with major number 10 and minor number 144 using mknod ("man mknod"),
10332 you get read and write access to the 50 bytes of non-volatile memory
10333 in the real time clock (RTC), which is contained in every PC and
10336 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
10337 on Ataris. /dev/nvram may be used to view settings there, or to
10338 change them (with some utility). It could also be used to frequently
10339 save a few bits of very important data that may not be lost over
10340 power-off and for which writing to disk is too insecure. Note
10341 however that most NVRAM space in a PC belongs to the BIOS and you
10342 should NEVER idly tamper with it. See Ralf Brown's interrupt list
10343 for a guide to the use of CMOS bytes by your BIOS.
10345 On Atari machines, /dev/nvram is always configured and does not need
10348 This driver is also available as a module ( = code which can be
10349 inserted in and removed from the running kernel whenever you want).
10350 The module will be called nvram.o. If you want to compile it as a
10351 module, say M here and read Documentation/modules.txt.
10355 If you have a joystick, you can say Y here to enable generic
10356 joystick support. You will also need to say Y or M to at least one
10357 of the hardware specific joystick drivers. This will make the
10358 joysticks available as /dev/jsX devices. Please read the file
10359 Documentation/joystick.txt which contains more information and the
10360 location of the joystick package that you'll need.
10362 This driver is also available as a module ( = code which can be
10363 inserted in and removed from the running kernel whenever you want).
10364 The module will be called joystick.o. If you want to compile it as a
10365 module, say M here and read Documentation/modules.txt.
10367 Classic PC analog joysticks and gamepads
10369 Say Y here if you have an analog joystick or gamepad that connects
10370 to the PC gameport. This supports many different types, including
10371 joysticks with throttle control, with rudders, or with extensions
10372 like additional hats and buttons compatible with CH Flightstick Pro,
10373 ThrustMaster FCS or 6 and 8 button gamepads. For more information on
10374 how to use the driver please read Documentation/joystick.txt
10376 FPGaming and MadCatz A3D controllers
10378 Say Y here if you have an FPGaming Assasin 3D, MadCatz Panther or
10379 MadCatz Panther XL. For more information on how to use the driver
10380 please read Documentation/joystick.txt
10382 Gravis GrIP joysticks and gamepads
10384 Say Y here if you have a Gravis GamePad Pro, Gravis Xterminator or
10385 Gravis Blackhawk Digital. For more information on how to use the
10386 driver please read Documentation/joystick.txt
10388 PDPI Lightning 4 gamecards
10389 CONFIG_JOY_LIGHTNING
10390 Say Y here if you have a PDPI Lightning 4 gamecard and an analog
10391 joystick or gamepad connected to it. For more information on how to
10392 use the driver please read Documentation/joystick.txt
10394 Logitech Digital joysticks and gamepads
10395 CONFIG_JOY_LOGITECH
10396 Say Y here if you have a Logitech WingMan Extreme Digital,
10397 Logitech ThunderPad Digital or Logitech CyberMan 2. For more
10398 information on how to use the driver please read
10399 Documentation/joystick.txt
10401 Microsoft SideWinder, Genius Digital joysticks and gamepads
10402 CONFIG_JOY_SIDEWINDER
10403 Say Y here if you have a Microsoft SideWinder 3d Pro, Microsoft
10404 SideWinder Precision Pro, Microsoft SideWinder Force Feedback Pro,
10405 Microsoft Sidewinder GamePad or Genius Flight2000 F-23 Digital. For
10406 more information on how to use the driver please read
10407 Documentation/joystick.txt
10409 ThrustMaster DirectConnect joysticks and gamepads
10410 CONFIG_JOY_THRUSTMASTER
10411 Say Y here if you have a ThrustMaster Millenium 3D Inceptor or a
10412 ThrustMaster 3D Rage Pad. For more information on how to use the
10413 driver please read Documentation/joystick.txt
10415 NES, SNES, PSX, Multisystem joysticks and gamepads
10417 Say Y here if you have a Nintendo Entertainment System gamepad,
10418 Super Nintendo Entertainment System gamepad, Sony PlayStation
10419 gamepad or a Multisystem -- Atari, Amiga, Commodore, Amstrad CPC
10420 joystick. For more information on how to use the driver please read
10421 Documentation/joystick.txt and Documentation/joystick-parport.txt
10423 Sega, Multisystem joysticks and gamepads
10425 Say Y here if you have a Sega Master System gamepad, Sega Genesis
10426 gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga,
10427 Commodore, Amstrad CPC joystick. For more information on how to use
10428 the driver please read Documentation/joystick.txt and
10429 Documentation/joystick-parport.txt
10431 TurboGraFX Multisystem joystick interface
10432 CONFIG_JOY_TURBOGRAFX
10433 Say Y here if you have the TurboGraFX interface by Steffen Schwenke,
10434 and want to use it with Multiststem -- Atari, Amiga, Commodore,
10435 Amstrad CPC joystick. For more information on how to use the driver
10436 please read Documentation/joystick.txt and
10437 Documentation/joystick-parport.txt
10441 Say Y here if you have an Amiga with a digital joystick connected
10442 to it. For more information on how to use the driver please read
10443 Documentation/joystick.txt
10445 Atomwide Serial Support
10446 CONFIG_ATOMWIDE_SERIAL
10447 If you have an Atomwide Serial card for an Acorn system, say Y to
10448 this option. The driver can handle 1, 2, or 3 port cards.
10451 The Serial Port Dual Serial Port
10452 CONFIG_DUALSP_SERIAL
10453 If you have the Serial Port's dual serial card for an Acorn system,
10454 say Y to this option. If unsure, say N
10458 If you say Y here and create a character device node /dev/nwbutton
10459 with major and minor numbers 10 and 158 ("man mknod"), then every
10460 time the orange button is pressed a number of times, the number of
10461 times the button was pressed will be written to that device.
10463 This is most useful for applications, as yet unwritten, which
10464 perform actions based on how many times the button is pressed in a
10467 Do not hold the button down for too long, as the driver does not
10468 alter the behaviour of the hardware reset circuitry attached to the
10469 button; it will still execute a hard reset if the button is held
10470 down for longer than approximately five seconds.
10472 This driver is also available as a module ( = code which can be
10473 inserted in and removed from the running kernel whenever you want).
10474 If you want to compile it as a module, say M here and read
10475 Documentation/modules.txt. The module will be called nwbutton.o.
10477 Most people will answer Y to this question and "Reboot Using Button"
10478 below to be able to initiate a system shutdown from the button.
10480 Reboot Using Button
10481 CONFIG_NWBUTTON_REBOOT
10482 If you say Y here, then you will be able to initiate a system
10483 shutdown and reboot by pressing the orange button a number of times.
10484 The number of presses to initiate the shutdown is two by default,
10485 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
10486 in nwbutton.h and recompiling the driver or, if you compile the
10487 driver as a module, you can specify the number of presses at load
10488 time with "insmod button reboot_count=<something>".
10492 If you have a sound card in your computer, i.e. if it can say more
10493 than an occasional beep, say Y. Be sure to have all the information
10494 about your sound card and its configuration down (I/O port,
10495 interrupt and DMA channel), because you will be asked for it.
10497 You want to read the Sound-HOWTO, available from
10498 http://metalab.unc.edu/mdw/linux.html#howto . General information
10499 about the modular sound system is contained in the files
10500 Documentation/sound/Introduction. The file
10501 Documentation/sound/README.OSS contains some slightly outdated but
10502 still useful information as well.
10504 If you have a PnP sound card and you want to configure it at boot
10505 time using the ISA PnP tools (read
10506 http://www.roestock.demon.co.uk/isapnptools/ ), then you need to
10507 compile the sound card support as a module ( = code which can be
10508 inserted in and removed from the running kernel whenever you want)
10509 and load that module after the PnP configuration is finished. To do
10510 this, say M here and read Documentation/modules.txt as well as
10511 Documentation/sound/README.modules; the module will be called
10514 I'm told that even without a sound card, you can make your computer
10515 say more than an occasional beep, by programming the PC speaker.
10516 Kernel patches and supporting utilities to do that are in the pcsp
10517 package, available at ftp://ftp.infradead.org/pub/pcsp/.
10521 OSS is the Open Sound System suite of sound card drivers. They make
10522 sound programming easier since they provide a common API. Say Y or M
10523 here (the module will be called sound.o) if you haven't found a
10524 driver for your sound card above, then pick your driver from the
10527 Persistent DMA buffers
10529 Linux can often have problems allocating DMA buffers for ISA sound
10530 cards on machines with more than 16MB of RAM. This is because ISA
10531 DMA buffers must exist below the 16MB boundary and it is quite
10532 possible that a large enough free block in this region cannot be
10533 found after the machine has been running for a while. If you say Y
10534 here the DMA buffers (64Kb) will be allocated at boot time and kept
10535 until the shutdown. This option is only useful if you said Y to
10536 "OSS sound modules", above. If you said M to "OSS sound modules"
10537 then you can get the persistent DMA buffer functionality by passing
10538 the command-line argument "dmabuf=1" to the sound.o module.
10540 Say Y unless you have 16MB or less RAM or a PCI sound card.
10542 Support for Aztech Sound Galaxy (non-PnP) cards
10543 CONFIG_SOUND_SGALAXY
10544 This module initializes the older non Plug and Play sound galaxy
10545 cards from Aztech. It supports the Waverider Pro 32 - 3D and the
10546 Galaxy Washington 16.
10548 Support for AD1816(A) based cards (EXPERIMENTAL)
10549 CONFIG_SOUND_AD1816
10550 Say M here if you have a sound card based on the Analog Devices
10553 NOTE: This driver is still EXPERIMENTAL.
10554 See Documentation/sound/AD1816 for further information.
10556 Yamaha OPL3-SA1 audio controller
10557 CONFIG_SOUND_OPL3SA1
10558 Say Y or M if you have a Yamaha OPL3-SA1 sound chip, which is
10559 usually built into motherboards. Read Documentation/sound/OPL3-SA
10562 ProAudioSpectrum 16 support
10564 Answer Y only if you have a Pro Audio Spectrum 16, ProAudio Studio
10565 16 or Logitech SoundMan 16 sound card. Don't answer Y if you have
10566 some other card made by Media Vision or Logitech since they are not
10569 100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support
10571 Answer Y if you have an original Sound Blaster card made by Creative
10572 Labs or a 100% hardware compatible clone (like the Thunderboard or
10573 SM Games). For an unknown card you may answer Y if the card claims
10574 to be Sound Blaster-compatible.
10576 Please read the file Documentation/sound/Soundblaster.
10578 You should also say Y here for cards based on the Avance Logic
10579 ALS-007 chip (read Documentation/sound/ALS007) and for cards based
10580 on ESS chips (read Documentation/sound/ESS1868 and
10581 Documentation/sound/ESS). If you have an SB AWE 32 or SB AWE 64, say
10582 Y here and also to "Additional lowlevel drivers" and to "SB32/AWE
10583 support" below and read Documentation/sound/INSTALL.awe. If you have
10584 an IBM Mwave card, say Y here and read Documentation/sound/mwave.
10586 You can say M here to compile this driver as a module; the module is
10589 Generic OPL2/OPL3 FM synthesizer support
10591 Answer Y if your card has a FM chip made by Yamaha (OPL2/OPL3/OPL4).
10592 Answering Y is usually a safe and recommended choice, however some
10593 cards may have software (TSR) FM emulation. Enabling FM support with
10594 these cards may cause trouble (I don't currently know of any such
10597 Please read the file Documentation/sound/OPL3 if your card has an
10603 #Loopback MIDI device support
10604 #CONFIG_SOUND_VMIDI
10606 ### somebody please fill this in.
10609 Gravis Ultrasound support
10611 Say Y here for any type of Gravis Ultrasound card, including
10612 the GUS or GUS MAX. See also Documentation/sound/ultrasound for
10613 more information on configuring this card with modules.
10615 MPU-401 support (NOT for SB16)
10616 CONFIG_SOUND_MPU401
10617 Be careful with this question. The MPU401 interface is supported by
10618 all sound cards. However, some natively supported cards have their
10619 own driver for MPU401. Enabling this MPU401 option with these cards
10620 will cause a conflict. Also, enabling MPU401 on a system that
10621 doesn't really have a MPU401 could cause some trouble. If your card
10622 was in the list of supported cards, look at the card specific
10623 instructions in the drivers/sound/Readme.cards file. It's safe to
10624 answer Y if you have a true MPU401 MIDI interface card.
10627 CONFIG_SOUND_UART6850
10628 This option enables support for MIDI interfaces based on the 6850
10629 UART chip. This interface is rarely found on sound cards. It's safe
10630 to answer N to this question.
10634 Say Y here for ARM systems with the VIDC video controller and 16-bit
10635 Linear sound DACs. If unsure, say N.
10637 PSS (AD1848, ADSP-2115, ESC614) support
10639 Answer Y or M if you have an Orchid SW32, Cardinal DSP16, Beethoven
10640 ADSP-16 or some other card based on the PSS chipset (AD1848 codec +
10641 ADSP-2115 DSP chip + Echo ESC614 ASIC CHIP). For more information on
10642 how to compile it into the kernel or as a module see the file
10643 Documentation/sound/PSS.
10645 Enable PSS mixer (Beethoven ADSP-16 and other compatible)
10647 Answer Y for Beethoven ADSP-16. You may try to say Y also for other
10648 cards if they have master volume, bass, treble, and you can't
10649 control it under Linux. If you answer N for Beethoven ADSP-16, you
10650 can't control master volume, bass, treble and synth volume.
10652 If you said M to "PSS support" above, you may enable or disable this
10653 PSS mixer with the module parameter pss_mixer. For more information
10654 see the file Documentation/sound/PSS.
10656 Have DSPxxx.LD firmware file
10657 CONFIG_PSS_HAVE_BOOT
10658 If you have the DSPxxx.LD file or SYNTH.LD file for you card, say Y
10659 to include this file. Without this file the synth device (OPL) may
10662 Full pathname of DSPxxx.LD firmware file
10663 CONFIG_PSS_BOOT_FILE
10664 Enter the full pathname of your DSPxxx.LD file or SYNTH.LD file,
10667 16 bit sampling option of GUS (_NOT_ GUS MAX)
10669 Answer Y if you have installed the 16 bit sampling daughtercard on
10670 your GUS. Answer N if you have a GUS MAX, since saying Y here
10671 disables GUS MAX support.
10674 CONFIG_SOUND_GUSMAX
10675 Answer Y only if you have a Gravis Ultrasound MAX.
10677 Microsoft Sound System support
10679 Again think carefully before answering Y to this question. It's safe
10680 to answer Y if you have the original Windows Sound System card made
10681 by Microsoft or Aztech SG 16 Pro (or NX16 Pro). Also you may say Y
10682 in case your card is NOT among these:
10684 ATI Stereo F/X, AdLib, Audio Excell DSP16, Cardinal DSP16,
10685 Ensoniq SoundScape (and compatibles made by Reveal and Spea),
10686 Gravis Ultrasound, Gravis Ultrasound ACE, Gravis Ultrasound Max,
10687 Gravis Ultrasound with 16 bit option, Logitech Sound Man 16,
10688 Logitech SoundMan Games, Logitech SoundMan Wave, MAD16 Pro (OPTi
10689 82C929), Media Vision Jazz16, MediaTriX AudioTriX Pro, Microsoft
10690 Windows Sound System (MSS/WSS), Mozart (OAK OTI-601), Orchid
10691 SW32, Personal Sound System (PSS), Pro Audio Spectrum 16, Pro
10692 Audio Studio 16, Pro Sonic 16, Roland MPU-401 MIDI interface,
10693 Sound Blaster 1.0, Sound Blaster 16, Sound Blaster 16ASP, Sound
10694 Blaster 2.0, Sound Blaster AWE32, Sound Blaster Pro, TI TM4000M
10695 notebook, ThunderBoard, Turtle Beach Tropez, Yamaha FM
10696 synthesizers (OPL2, OPL3 and OPL4), 6850 UART MIDI Interface.
10698 For cards having native support in VoxWare, consult the card
10699 specific instructions in drivers/sound/Readme.cards. Some drivers
10700 have their own MSS support and saying Y to this option will cause a
10703 SGI Visual Workstation on-board audio
10705 Say Y or M if you have an SGI Visual Workstation and you want to
10706 be able to use its on-board audio. Read Documentation/sound/visws
10707 for more info on this driver's capabilities.
10709 Ensoniq Soundscape support
10710 CONFIG_SOUND_SSCAPE
10711 Answer Y if you have a sound card based on the Ensoniq SoundScape
10712 chipset. Such cards are being manufactured at least by Ensoniq, Spea
10713 and Reveal (Reveal makes also other cards).
10715 MediaTriX AudioTriX Pro support
10717 Answer Y if you have the AudioTriX Pro sound card manufactured
10720 Have TRXPRO.HEX firmware file
10721 CONFIG_TRIX_HAVE_BOOT
10722 The MediaTrix AudioTrix Pro has an on-board microcontroller which
10723 needs to be initialized by downloading the code from the file
10724 TRXPRO.HEX in the DOS driver directory. If you don't have the
10725 TRXPRO.HEX file handy you may skip this step. However, the SB and
10726 MPU-401 modes of AudioTrix Pro will not work without this file!
10728 Full pathname of TRXPRO.HEX firmware file
10729 CONFIG_TRIX_BOOT_FILE
10730 Enter the full pathname of your TRXPRO.HEX file, starting from /.
10732 Support for OPTi MAD16 and/or Mozart based cards
10734 Answer Y if your card has a Mozart (OAK OTI-601) or MAD16 (OPTi
10735 82C928 or 82C929 or 82C931) audio interface chip. For the 82C931,
10736 please read drivers/sound/README.C931. These chips are currently
10737 quite common so it's possible that many no-name cards have one of
10738 them. In addition the MAD16 chip is used in some cards made by known
10739 manufacturers such as Turtle Beach (Tropez), Reveal (some models)
10740 and Diamond (latest ones). Note however that the Tropez sound cards
10741 have their own driver; if you have one of those, say N here and Y or
10742 M to "Full support for Turtle Beach WaveFront", below.
10744 See also Documentation/sound/Opti and Documentation/sound/MAD16 for
10745 more information on setting these cards up as modules.
10747 Full support for Turtle Beach WaveFront synth/sound cards
10748 CONFIG_SOUND_WAVEFRONT
10749 Answer Y or M if you have a Tropez Plus, Tropez or Maui sound card
10750 and read the files Documentation/sound/Wavefront and
10751 Documentation/sound/Tropez+.
10753 Support MIDI in older MAD16 based cards (requires SB)
10754 CONFIG_MAD16_OLDCARD
10755 Answer Y (or M) if you have an older card based on the C928 or
10756 Mozart chipset and you want to have MIDI support. If you enable this
10757 option you also need to enable support for Sound Blaster.
10759 Support for Crystal CS4232 based (PnP) cards
10760 CONFIG_SOUND_CS4232
10761 Say Y here if you have a card based on the Crystal CS4232 chip set,
10762 which uses its own Plug and Play protocol.
10764 See Documentation/sound/CS4232 for more information on configuring
10767 Support for Yamaha OPL3-SA2, SA3, and SAx based PnP cards
10768 CONFIG_SOUND_OPL3SA2
10769 Say Y or M if you have a card based on one of these Yamaha
10770 sound chipsets. Read Documentation/sound/OPL3-SA2 for more
10771 information on configuring these cards.
10773 Support for Turtle Beach Wave Front (Maui, Tropez) synthesizers
10775 Say Y here if you have a Turtle Beach Wave Front, Maui, or Tropez
10778 Have OSWF.MOT firmware file
10779 CONFIG_MAUI_HAVE_BOOT
10780 Turtle Beach Maui and Tropez sound cards have a microcontroller
10781 which needs to be initialized prior to use. OSWF.MOT is a file
10782 distributed with the card's DOS/Windows drivers. Answer Y if you
10785 Full pathname of OSWF.MOT firmware file
10786 CONFIG_MAUI_BOOT_FILE
10787 Enter the full pathname of your OSWF.MOT file, starting from /.
10789 Support for Turtle Beach MultiSound Classic, Tahiti, Monterey
10790 CONFIG_SOUND_MSNDCLAS
10791 Say M here if you have a Turtle Beach MultiSound Classic, Tahiti or
10792 Monterey (not for the Pinnacle or Fiji).
10794 See Documentation/sound/MultiSound for important information about
10797 Full pathname of MSNDINIT.BIN firmware file
10798 CONFIG_MSNDCLAS_INIT_FILE
10799 The MultiSound cards have two firmware files which are required for
10800 operation, and are not currently included. These files can be
10801 obtained from Turtle Beach. See Documentation/sound/MultiSound for
10802 information on how to obtain this.
10804 Full pathname of MSNDPERM.BIN firmware file
10805 CONFIG_MSNDCLAS_PERM_FILE
10806 The MultiSound cards have two firmware files which are required for
10807 operation, and are not currently included. These files can be
10808 obtained from Turtle Beach. See Documentation/sound/MultiSound for
10809 information on how to obtain this.
10811 Support for Turtle Beach MultiSound Pinnacle, Fiji
10812 CONFIG_SOUND_MSNDPIN
10813 Say M here if you have a Turtle Beach MultiSound Pinnacle or Fiji.
10814 See Documentation/sound/MultiSound for important information about
10817 Full pathname of PNDSPINI.BIN firmware file
10818 CONFIG_MSNDPIN_INIT_FILE
10819 The MultiSound cards have two firmware files which are required for
10820 operation, and are not currently included. These files can be
10821 obtained from Turtle Beach. See Documentation/sound/MultiSound for
10822 information on how to obtain this.
10824 Full pathname of PNDSPERM.BIN firmware file
10825 CONFIG_MSNDPIN_PERM_FILE
10826 The MultiSound cards have two firmware files which are required for
10827 operation, and are not currently included. These files can be
10828 obtained from Turtle Beach. See Documentation/sound/MultiSound for
10829 information on how to obtain this.
10831 MSND Pinnacle have S/PDIF I/O
10832 CONFIG_MSNDPIN_DIGITAL
10833 If you have the S/PDIF daughter board for the Pinnacle or Fiji,
10834 answer Y here; otherwise, say N. If you have this, you will be able
10835 to play and record from the S/PDIF port (digital signal). See
10836 Documentation/sound/MultiSound for information on how to make use of
10839 MSND Pinnacle non-PnP Mode
10840 CONFIG_MSNDPIN_NONPNP
10841 The Pinnacle and Fiji card resources can be configured either with
10842 PnP, or through a configuration port. Say Y here if your card is NOT
10843 in PnP mode. For the Pinnacle, configuration in non-PnP mode allows
10844 use of the IDE and joystick peripherals on the card as well; these
10845 do not show up when the card is in PnP mode. Specifying zero for any
10846 resource of a device will disable the device. If you are running the
10847 card in PnP mode, you must say N here and use isapnptools to
10848 configure the card's resources.
10850 MSND Pinnacle config port
10852 This is the port which the Pinnacle and Fiji uses to configure the
10853 card's resources when not in PnP mode. If your card is in PnP mode,
10854 then be sure to say N to the previous option, "MSND Pinnacle Non-PnP
10857 MSND buffer size (kB)
10858 CONFIG_MSND_FIFOSIZE
10859 Configures the size of each audio buffer, in kilobytes, for
10860 recording and playing in the MultiSound drivers (both the Classic
10861 and Pinnacle). Larger values reduce the chance of data overruns at
10862 the expense of overall latency. If unsure, use the default.
10864 /dev/dsp and /dev/audio support
10866 If you say Y here, you will get the /dev/dsp and /dev/audio devices;
10867 these are the analog-digital and digital-analog converter devices
10868 and are very useful, so say Y.
10870 MIDI interface support
10872 Answering N disables /dev/midixx devices and access to any MIDI
10873 ports using /dev/sequencer and /dev/music. This option also affects
10874 any MPU401 and/or General MIDI compatible devices. Answer Y.
10876 FM synthesizer (YM3812/OPL-3) support
10877 CONFIG_SOUND_YM3812
10878 Answer Y here, unless you know you will not need the option.
10882 This is support for the sound cards on Sun workstations. The code
10883 does not exist yet, so you might as well say N here.
10885 Additional low level drivers
10886 CONFIG_LOWLEVEL_SOUND
10887 If you need additional low level sound drivers which have not yet
10888 appeared, say Y. The answer to this question does not directly
10889 affect the kernel; saying Y will simply cause this configure script
10890 to present you with more options. If unsure, say Y.
10892 ACI mixer (miroPCM12/PCM20)
10894 ACI (Audio Command Interface) is a protocol used to communicate with
10895 the microcontroller on some sound cards produced by miro, e.g. the
10896 miroSOUND PCM12 and PCM20. The main function of the ACI is to
10897 control the mixer and to get a product identification.
10899 This Voxware ACI driver currently only supports the ACI functions on
10900 the miroSOUND PCM12 and PCM20 cards. On the PCM20, ACI also controls
10901 the radio tuner. This is supported in the video4linux
10902 radio-miropcm20 driver.
10906 Say Y here if you have a Sound Blaster SB32, AWE32-PnP, SB AWE64 or
10907 similar sound card. See Documentation/sound/README.awe,
10908 Documentation/sound/AWE32 and the Soundblaster-AWE mini-HOWTO,
10909 available from http://metalab.unc.edu/mdw/linux.html#howto for more
10912 Gallant's Audio Excel DSP 16 support (SC-6000 and SC-6600)
10914 Answer Y if you have a Gallant's Audio Excel DSP 16 card. This
10915 driver supports Audio Excel DSP 16 but not the III nor PnP versions
10918 The Gallant's Audio Excel DSP 16 card can emulate either an SBPro or
10919 a Microsoft Sound System card, so you should have said Y to either
10920 "100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support"
10921 or "Microsoft Sound System support", above, and you need to answer
10922 the "MSS emulation" and "SBPro emulation" questions below
10923 accordingly. You should say Y to one and only one of these two
10926 Read the drivers/sound/lowlevel/README.aedsp16 file and the head of
10927 drivers/sound/lowlevel/aedsp16.c as well as
10928 Documentation/sound/AudioExcelDSP16 to get more information about
10929 this driver and its configuration.
10931 I/O base for Audio Excel DSP 16
10932 CONFIG_AEDSP16_BASE
10933 This is the base I/O address of the Audio Excel DSP 16 card. It must
10934 be 220 or 240. If you compiled aedsp16.o as a module you can specify
10935 this parameter as 'io=0xNNN'.
10937 Audio Excel DSP 16 (SBPro emulation)
10938 CONFIG_AEDSP16_SBPRO
10939 Answer Y if you want your audio card to emulate Sound Blaster Pro.
10940 You should then say Y to "100% Sound Blaster compatibles
10941 (SB16/32/64, ESS, Jazz16) support" and N to "Audio Excel DSP 16 (MSS
10944 Audio Excel DSP 16 IRQ
10945 CONFIG_AEDSP16_SB_IRQ
10946 This is the IRQ of the Audio Excel DSP 16 card. It must be 5, 7, 9,
10947 10 or 11. If you compiled aedsp16.o as a module you can specify
10948 this parameter as 'irq=NN'.
10950 Audio Excel DSP 16 DMA
10951 CONFIG_AEDSP16_SB_DMA
10952 This is the IRQ of the Audio Excel DSP 16 card. It must be 0, 1 or
10953 3. If you compiled aedsp16.o as a module you can specify this
10954 parameter as 'dma=NN'.
10956 Audio Excel DSP 16 (MSS emulation)
10958 Answer Y if you want your audio card to emulate Microsoft Sound
10959 System. You should then say Y to "Microsoft Sound System support"
10960 and say N to "Audio Excel DSP 16 (SBPro emulation)".
10962 Audio Excel DSP 16 IRQ
10963 CONFIG_AEDSP16_MSS_IRQ
10964 This is the IRQ of the Audio Excel DSP 16 card. It must be 5, 7, 9,
10965 10 or 11. If you compiled aedsp16.o as a module you can specify
10966 this parameter as 'irq=NN'.
10968 Audio Excel DSP 16 DMA
10969 CONFIG_AEDSP16_MSS_DMA
10970 This is the IRQ of the Audio Excel DSP 16 card. It must be 0, 1
10971 or 3. If you compiled aedsp16.o as a module you can specify this
10972 parameter as 'dma=NN'.
10974 SC-6600 based audio cards (new Audio Excel DSP 16)
10976 The SC6600 is the new version of DSP mounted on the Audio Excel DSP
10977 16 cards. Find in the manual the FCC ID of your audio card and
10978 answer Y if you have an SC6600 DSP.
10980 SC-6600 Joystick Interface
10982 Say Y here in order to use the joystick interface of the Audio Excel
10985 SC-6600 CDROM Interface
10986 CONFIG_SC6600_CDROM
10987 This is used to activate the the CDROM interface of the Audio Excel
10988 DSP 16 card. Enter: 0 for Sony, 1 for Panasonic, 2 for IDE, 4 for no
10991 Audio Excel DSP 16 (MPU401 emulation)
10992 CONFIG_AEDSP16_MPU401
10993 Answer Y if you want your audio card to emulate the MPU-401 midi
10994 interface. You should then also say Y to "MPU-401 support".
10996 Note that the I/O base for MPU-401 support of aedsp16 is the same
10997 you have selected for "MPU-401 support". If you are using this
10998 driver as a module you have to specify the MPU I/O base address with
10999 the parameter 'mpu_base=0xNNN'.
11001 MPU401 IRQ for Audio Excel DSP 16
11002 CONFIG_AEDSP16_MPU_IRQ
11003 This is the IRQ of the MPU-401 emulation of your Audio Excel DSP 16
11004 card. It must be 5, 7, 9, 10 or 0 (to disable MPU-401 interface). If
11005 you compiled aedsp16.o as a module you can specify this parameter as
11008 Ensoniq ES1370 based PCI sound cards
11009 CONFIG_SOUND_ES1370
11010 Say Y or M if you have a PCI sound card utilizing the Ensoniq
11011 ES1370 chipset, such as Ensoniq's AudioPCI (non-97). To find
11012 out if your sound card uses an ES1370 without removing your
11013 computer's cover, use lspci -n and look for the PCI ID
11014 1274:5000. Since Ensoniq was bought by Creative Labs,
11015 Sound Blaster 64/PCI models are either ES1370 or ES1371 based.
11016 This driver differs slightly from OSS/Free, so PLEASE READ
11017 Documentation/sound/es1370.
11019 Ensoniq ES1371 based PCI sound cards
11020 CONFIG_SOUND_ES1371
11021 Say Y or M if you have a PCI sound card utilizing the Ensoniq
11022 ES1371 chipset, such as Ensoniq's AudioPCI97. To find out if
11023 your sound card uses an ES1371 without removing your computer's
11024 cover, use lspci -n and look for the PCI ID 1274:1371. Since
11025 Ensoniq was bought by Creative Labs, Sound Blaster 64/PCI
11026 models are either ES1370 or ES1371 based. This driver differs
11027 slightly from OSS/Free, so PLEASE READ Documentation/sound/es1371.
11029 ESS Solo1 based PCI sound cards (eg. SC1938)
11030 CONFIG_SOUND_ESSSOLO1
11031 Say Y or M if you have a PCI sound card utilizing the ESS Technology
11032 Solo1 chip. To find out if your sound card uses a
11033 Solo1 chip without removing your computer's cover, use
11034 lspci -n and look for the PCI ID 125D:1969. This driver
11035 differs slightly from OSS/Free, so PLEASE READ
11036 Documentation/sound/solo1.
11038 S3 SonicVibes based PCI sound cards
11039 CONFIG_SOUND_SONICVIBES
11040 Say Y or M if you have a PCI sound card utilizing the S3
11041 SonicVibes chipset. To find out if your sound card uses a
11042 SonicVibes chip without removing your computer's cover, use
11043 lspci -n and look for the PCI ID 5333:CA00. This driver
11044 differs slightly from OSS/Free, so PLEASE READ
11045 Documentation/sound/sonicvibes.
11047 Rockwell WaveArtist
11048 CONFIG_SOUND_WAVEARTIST
11049 Say Y here to include support for the Rockwell WaveArtist sound
11050 system. This driver is mainly for the NetWinder.
11052 VIA 82Cxxx Audio Codec
11053 CONFIG_SOUND_VIA82CXXX
11054 Say Y here to include support for the audio codec found on
11055 VIA 82Cxxx-based chips. Typically these are built into a motherboard.
11056 DO NOT select SoundBlaster or Adlib with this driver, unless you have
11057 a SoundBlaster or Adlib card in addition to your VIA audio chip.
11059 NeoMagic 256AV/256ZX sound chipsets
11061 Say M here to include audio support for the NeoMagic 256AV/256ZX
11062 chipsets. These are the audio chipsets found in the Sony Z505S/SX/DX,
11063 some Sony F-series, and the Dell Latitude CPi and CPt laptops. It includes
11064 support for an AC97-compatible mixer and an apparently proprietary sound
11067 See Documentation/sound/NM256 for further information.
11069 Are you using a crosscompiler
11070 CONFIG_CROSSCOMPILE
11071 Say Y here if you are compiling the kernel on a different
11072 architecture than the one it is intended to run on.
11074 Build fp exception handler module
11075 CONFIG_MIPS_FPE_MODULE
11076 Build the floating point exception handler module. This option is
11077 only useful for people working on the floating point exception
11078 handler. If you don't, say N.
11080 Remote GDB kernel debugging
11081 CONFIG_REMOTE_DEBUG
11082 If you say Y here, it will be possible to remotely debug the MIPS
11083 kernel using gdb. This enlarges your kernel image disk size by
11084 several megabytes and requires a machine with more than 16 MB,
11085 better 32 MB RAM to avoid excessive linking time. This is only
11086 useful for kernel hackers. If unsure, say N.
11088 Magic System Request Key support
11090 If you say Y here, you will have some control over the system even
11091 if the system crashes for example during kernel debugging (e.g., you
11092 will be able to flush the buffer cache to disk, reboot the system
11093 immediately or dump some status information). This is accomplished
11094 by pressing various keys while holding SysRq (Alt+PrintScreen). The
11095 keys are documented in Documentation/sysrq.txt. Don't say Y unless
11096 you really know what this hack does.
11100 ISDN ("Integrated Services Digital Networks", called RNIS in France)
11101 is a special type of fully digital telephone service; it's mostly
11102 used to connect to your Internet service provider (with SLIP or
11103 PPP). The main advantage is that the speed is higher than ordinary
11104 modem/telephone connections, and that you can have voice
11105 conversations while downloading stuff. It only works if your
11106 computer is equipped with an ISDN card and both you and your service
11107 provider purchased an ISDN line from the phone company. For details,
11108 read http://alumni.caltech.edu/~dank/isdn/ on the WWW.
11110 This driver allows you to use an ISDN-card for networking
11111 connections and as dialin/out device. The isdn-tty's have a built in
11112 AT-compatible modem emulator. Network devices support autodial,
11113 channel-bundling, callback and caller-authentication without having
11114 a daemon running. A reduced T.70 protocol is supported with tty's
11115 suitable for German BTX. On D-Channel, the protocols EDSS1
11116 (Euro-ISDN) and 1TR6 (German style) are supported. See
11117 Documentation/isdn/README for more information.
11119 If you want to compile the ISDN code as a module ( = code which can
11120 be inserted in and removed from the running kernel whenever you
11121 want), say M here and read Documentation/modules.txt. The module
11122 will be called isdn.o. If unsure, say N.
11124 Support synchronous PPP
11126 Over digital connections such as ISDN, there is no need to
11127 synchronize sender and recipient's clocks with start and stop bits
11128 as is done over analog telephone lines. Instead, one can use
11129 "synchronous PPP". Saying Y here will include this protocol. This
11130 protocol is used by Cisco and Sun for example. So you want to say Y
11131 here if the other end of your ISDN connection supports it. You will
11132 need a special version of pppd (called ipppd) for using this
11133 feature. See Documentation/isdn/README.syncppp and
11134 Documentation/isdn/syncPPP.FAQ for more information.
11136 Support generic MP (RFC 1717)
11138 With synchronous PPP enabled, it is possible to increase throughput
11139 by bundling several ISDN-connections, using this protocol. See
11140 Documentation/isdn/README.syncppp for more information.
11142 Use VJ-compression with synchronous PPP
11144 This enables Van Jacobson header compression for synchronous PPP.
11145 Say Y if the other end of the connection supports it.
11147 Support audio via ISDN
11149 If you say Y here, the modem-emulator will support a subset of the
11150 EIA Class 8 Voice commands. Using a getty with voice-support
11151 (mgetty+sendfax by gert@greenie.muc.de with an extension, available
11152 with the ISDN utility package for example), you will be able to use
11153 your Linux box as an ISDN-answering machine. Of course, this must be
11154 supported by the lowlevel driver also. Currently, the HiSax driver
11155 is the only voice-supporting driver. See
11156 Documentation/isdn/README.audio for more information.
11158 X.25 PLP on top of ISDN
11160 This feature provides the X.25 protocol over ISDN connections.
11161 See Documentation/isdn/README.x25 for more information
11162 if you are thinking about using this.
11164 ISDN diversion services support
11165 CONFIG_ISDN_DIVERSION
11166 This option allows you to use some supplementary diversion
11167 services in conjunction with the HiSax driver on an EURO/DSS1
11170 Supported options are CD (call deflection), CFU (Call forward
11171 unconditional), CFB (Call forward when busy) and CFNR (call forward
11172 not reachable). Additionally the actual CFU, CFB and CFNR state may
11175 The use of CFU, CFB, CFNR and interrogation may be limited to some
11176 countries. The keypad protocol is still not implemented. CD should
11177 work in all countries if the service has been subscribed to.
11179 Please read the file Documentation/isdn/README.diversion.
11181 ICN 2B and 4B support
11182 CONFIG_ISDN_DRV_ICN
11183 This enables support for two kinds of ISDN-cards made by a German
11184 company called ICN. 2B is the standard version for a single ISDN
11185 line with two B-channels, 4B supports two ISDN lines. For running
11186 this card, additional firmware is necessary, which has to be
11187 downloaded into the card using a utility which is distributed
11188 separately. See Documentation/isdn/README and README.icn for more
11191 If you want to compile this as a module ( = code which can be
11192 inserted in and removed from the running kernel whenever you want),
11193 say M here and read Documentation/modules.txt. The module will be
11197 CONFIG_ISDN_DRV_LOOP
11198 This driver provides a virtual ISDN card. Its primary purpose is
11199 testing of linklevel features or configuration without getting
11200 charged by your service-provider for lots of phone calls.
11201 You need will need the loopctrl utility from the latest isdn4k-utils
11202 package to set up this driver.
11204 HiSax SiemensChipSet driver support
11205 CONFIG_ISDN_DRV_HISAX
11206 This is a driver supporting the Siemens chipset on various
11207 ISDN-cards (like AVM A1, Elsa ISDN cards, Teles S0-16.0, Teles
11208 S0-16.3, Teles S0-8, Teles/Creatix PnP, ITK micro ix1 and many
11211 HiSax is just the name of this driver, not the name of any hardware.
11213 If you have a card with such a chipset, you should say Y here and
11214 also to the configuration option of the driver for your particular
11217 If you want to compile this as a module ( = code which can be
11218 inserted in and removed from the running kernel whenever you want),
11219 say M here and read Documentation/modules.txt. The module will be
11220 called hisax.o. See Documentation/isdn/README.HiSax for more
11221 information on using this driver.
11223 HiSax Support for EURO/DSS1
11225 Enable this if you have a EURO ISDN line.
11227 Support for german chargeinfo
11229 If you have german AOC, you can enable this to get the charginfo.
11231 Disable sending complete
11232 CONFIG_HISAX_NO_SENDCOMPLETE
11233 If you have trouble with some ugly exchanges or you live in
11234 Australia select this option.
11236 Disable sending low layer compatibility
11237 CONFIG_HISAX_NO_LLC
11238 If you have trouble with some ugly exchanges try to select this
11241 HiSax Support for german 1TR6
11243 Enable this if you have a old german 1TR6 line.
11245 HiSax Support for Teles 16.0/8.0
11247 This enables HiSax support for the Teles ISDN-cards S0-16.0, S0-8
11248 and many compatibles.
11250 See Documentation/isdn/README.HiSax on how to configure it using the
11251 different cards, a different D-channel protocol, or non-standard
11252 IRQ/port/shmem settings.
11254 HiSax Support for Teles 16.3 or PNP or PCMCIA
11256 This enables HiSax support for the Teles ISDN-cards S0-16.3 the
11257 Teles/Creatix PnP and the Teles PCMCIA.
11259 See Documentation/isdn/README.HiSax on how to configure it using the
11260 different cards, a different D-channel protocol, or non-standard
11263 HiSax Support for Teles PCI
11264 CONFIG_HISAX_TELESPCI
11265 This enables HiSax support for the Teles PCI.
11266 See Documentation/isdn/README.HiSax on how to configure it.
11268 HiSax Support for Teles S0Box
11270 This enables HiSax support for the Teles/Creatix parallel port
11271 S0BOX. See Documentation/isdn/README.HiSax on how to configure it.
11273 HiSax Support for AVM A1 (Fritz)
11274 CONFIG_HISAX_AVM_A1
11275 This enables HiSax support for the AVM A1 (aka "Fritz").
11277 See Documentation/isdn/README.HiSax on how to configure it using the
11278 different cards, a different D-channel protocol, or non-standard
11281 HiSax Support for AVM PnP/PCI (Fritz!PNP/PCI)
11282 CONFIG_HISAX_FRITZPCI
11283 This enables HiSax support for the AVM "Fritz!PnP" and "Fritz!PCI".
11284 See Documentation/isdn/README.HiSax on how to configure it.
11286 HiSax Support for AVM A1 PCMCIA (Fritz)
11287 CONFIG_HISAX_AVM_A1_PCMCIA
11288 This enables HiSax support for the AVM A1 "Fritz!PCMCIA").
11289 See Documentation/isdn/README.HiSax on how to configure it.
11291 HiSax Support for Elsa cards
11293 This enables HiSax support for the Elsa Mircolink ISA cards, for the
11294 Elsa Quickstep series cards and Elsa PCMCIA.
11296 See Documentation/isdn/README.HiSax on how to configure it using the
11297 different cards, a different D-channel protocol, or non-standard
11300 HiSax Support for ITK ix1-micro Revision 2
11301 CONFIG_HISAX_IX1MICROR2
11302 This enables HiSax support for the ITK ix1-micro Revision 2 card.
11304 See Documentation/isdn/README.HiSax on how to configure it using the
11305 different cards, a different D-channel protocol, or non-standard
11308 HiSax Support for Eicon.Diehl Diva cards
11309 CONFIG_HISAX_DIEHLDIVA
11310 This enables HiSax support for the Eicon.Diehl Diva none PRO
11311 versions passive ISDN cards.
11313 See Documentation/isdn/README.HiSax on how to configure it using the
11314 different cards, a different D-channel protocol, or non-standard
11317 HiSax Support for ASUSCOM cards
11318 CONFIG_HISAX_ASUSCOM
11319 This enables HiSax support for the AsusCom and their OEM versions
11320 passive ISDN cards.
11322 See Documentation/isdn/README.HiSax on how to configure it using the
11323 different cards, a different D-channel protocol, or non-standard
11326 HiSax Support for TELEINT cards
11327 CONFIG_HISAX_TELEINT
11328 This enables HiSax support for the TELEINT SA1 semiactiv ISDN card.
11330 See Documentation/isdn/README.HiSax on how to configure it using the
11331 different cards, a different D-channel protocol, or non-standard
11334 HiSax Support for HFC-S based cards
11336 This enables HiSax support for the HFC-S 2BDS0 based cards, like
11339 See Documentation/isdn/README.HiSax on how to configure it using the
11340 different cards, a different D-channel protocol, or non-standard
11343 HiSax Support for Sedlbauer cards
11344 CONFIG_HISAX_SEDLBAUER
11345 This enables HiSax support for the Sedlbauer passive ISDN cards.
11347 See Documentation/isdn/README.HiSax on how to configure it using the
11348 different cards, a different D-channel protocol, or non-standard
11351 HiSax Support for USR Sportster internal TA
11352 CONFIG_HISAX_SPORTSTER
11353 This enables HiSax support for the USR Sportster internal TA card.
11355 See Documentation/isdn/README.HiSax on how to configure it using a
11356 different D-channel protocol, or non-standard IRQ/port settings.
11358 HiSax Support for MIC card
11360 This enables HiSax support for the ITH MIC card.
11362 See Documentation/isdn/README.HiSax on how to configure it using a
11363 different D-channel protocol, or non-standard IRQ/port settings.
11365 HiSax Support for NETjet card
11366 CONFIG_HISAX_NETJET
11367 This enables HiSax support for the NetJet from Traverse
11370 See Documentation/isdn/README.HiSax on how to configure it using a
11371 different D-channel protocol, or non-standard IRQ/port settings.
11373 HiSax Support for Niccy PnP/PCI card
11375 This enables HiSax support for the Dr. Neuhaus Niccy PnP or PCI.
11377 See Documentation/isdn/README.HiSax on how to configure it using a
11378 different D-channel protocol, or non-standard IRQ/port settings.
11380 HiSax Support for Siemens I-Surf card
11382 This enables HiSax support for the Siemens I-Talk/I-Surf card with
11384 See Documentation/isdn/README.HiSax on how to configure it using a
11385 different D-channel protocol, or non-standard IRQ/port settings.
11387 HiSax Support for HST Saphir card
11388 CONFIG_HISAX_HSTSAPHIR
11389 This enables HiSax support for the HST Saphir card.
11391 See Documentation/isdn/README.HiSax on how to configure it using a
11392 different D-channel protocol, or non-standard IRQ/port settings.
11394 HiSax Support for Telekom A4T card
11395 CONFIG_HISAX_BKM_A4T
11396 This enables HiSax support for the Telekom A4T card.
11398 See Documentation/isdn/README.HiSax on how to configure it using a
11399 different D-channel protocol, or non-standard IRQ/port settings.
11401 HiSax Support for Scitel Quadro card
11402 CONFIG_HISAX_SCT_QUADRO
11403 This enables HiSax support for the Scitel Quadro card.
11405 See Documentation/isdn/README.HiSax on how to configure it using a
11406 different D-channel protocol, or non-standard IRQ/port settings.
11408 HiSax Support for Gazel cards
11410 This enables HiSax support for the Gazel cards.
11412 See Documentation/isdn/README.HiSax on how to configure it using a
11413 different D-channel protocol, or non-standard IRQ/port settings.
11415 HiSax Support for HFC PCI-Bus cards
11416 CONFIG_HISAX_HFC_PCI
11417 This enables HiSax support for the HFC-S PCI 2BDS0 based cards.
11419 For more informations see under Documentation/isdn/README.hfc-pci.
11421 HiSax Support for Winbond W6692 based cards
11423 This enables HiSax support for Winbond W6692 based PCI ISDN cards.
11425 See Documentation/isdn/README.HiSax on how to configure it using a
11426 different D-channel protocol, or non-standard IRQ/port settings.
11428 HiSax Support for Am7930 (EXPERIMENTAL)
11429 CONFIG_HISAX_AMD7930
11430 This enables HiSax support for the AMD7930 chips on some SPARCs.
11431 This code is not finished yet.
11434 CONFIG_ISDN_DRV_PCBIT
11435 This enables support for the PCBIT ISDN-card. This card is
11436 manufactured in Portugal by Octal. For running this card, additional
11437 firmware is necessary, which has to be downloaded into the card
11438 using a utility which is distributed separately. See
11439 Documentation/isdn/README and Documentation/isdn/README.pcbit for
11442 If you want to compile this as a module ( = code which can be
11443 inserted in and removed from the running kernel whenever you want),
11444 say M here and read Documentation/modules.txt. The module will be
11447 Spellcaster support (EXPERIMENTAL)
11449 This enables support for the Spellcaster BRI ISDN boards. This
11450 driver currently builds only in a modularized version ( = code which
11451 can be inserted in and removed from the running kernel whenever you
11452 want, details in Documentation/modules.txt); the module will be
11453 called sc.o. See Documentation/isdn/README.sc and
11454 http://www.spellcast.com for more information.
11456 Eicon.Diehl active card support
11457 CONFIG_ISDN_DRV_EICON
11458 Say Y here if you have an Eicon active ISDN card. In order to use
11459 this card, additional firmware is necessary, which has to be loaded
11460 into the card using the eiconctrl utility which is part of the
11461 latest isdn4k-utils package. Please read the file
11462 Documentation/isdn/README.eicon for more information.
11464 Eicon old-type card support
11465 CONFIG_ISDN_DRV_EICON_ISA
11466 Say Y here if you have an old-type Eicon active ISDN card. In order
11467 to use this card, additional firmware is necessary, which has to be
11468 loaded into the card using the eiconctrl utility which is part of
11469 the latest isdn4k-utils package. Please read the file
11470 Documentation/isdn/README.eicon for more information.
11472 Support AT-Fax Class 2 commands
11473 CONFIG_ISDN_TTY_FAX
11474 If you say Y here, the modem-emulator will support a subset of the
11475 Fax Class 2 commands. Using a getty with fax-support
11476 (mgetty+sendfax, hylafax), you will be able to use your Linux box as
11477 an ISDN-fax-machine. This must be supported by the lowlevel driver
11478 also. See Documentation/isdn/README.fax for more information.
11480 AVM CAPI2.0 support
11481 CONFIG_ISDN_DRV_AVMB1
11482 This enables support for the AVM B1/T1 ISDN networking cards.In
11483 addition, a CAPI (Common ISDN Application Programming Interface, a
11484 standard making it easy for programs to access ISDN hardware, see
11485 http://www.capi.org/; to browse the WWW, you need to have access to
11486 a machine on the Internet that has a program like lynx or netscape)
11487 interface for this card is provided. In order to use this card,
11488 additional firmware is necessary, which has to be downloaded into
11489 the card using a utility which is distributed separately. Please
11490 read the file Documentation/isdn/README.avmb1.
11492 This code is also available as a module ( = code which can be
11493 inserted in and removed from the running kernel whenever you want).
11494 The module will be called avmb1.o. If you want to compile it as a
11495 module, say M here and read Documentation/modules.txt.
11498 CONFIG_ISDN_DRV_AVMB1_B1ISA
11499 Enable support for the ISA version of the AVM B1 card.
11502 CONFIG_ISDN_DRV_AVMB1_B1PCI
11503 Enable support for the PCI version of the AVM B1 card.
11505 AVM T1/T1-B ISA support
11506 CONFIG_ISDN_DRV_AVMB1_T1ISA
11507 Enable support for the AVM T1 T1B card.
11508 Note: This is a PRI card and handle 30 B-channels.
11510 AVM B1/M1/M2 PCMCIA support
11511 CONFIG_ISDN_DRV_AVMB1_B1PCMCIA
11512 Enable support for the PCMCIA version of the AVM B1 card.
11514 AVM T1/T1-B PCI support
11515 CONFIG_ISDN_DRV_AVMB1_T1PCI
11516 Enable support for the AVM T1 T1B card.
11517 Note: This is a PRI card and handle 30 B-channels.
11519 Verbose reason code reporting (kernel size +=7K)
11520 CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON
11521 If you say Y here, the AVM B1 driver will give verbose reasons for
11522 disconnecting. This will increase the size of the kernel by 7 KB. If
11526 IBM Active 2000 support (EXPERIMENTAL)
11527 CONFIG_ISDN_DRV_ACT2000
11528 Say Y here if you have an IBM Active 2000 ISDN card. In order to use
11529 this card, additional firmware is necessary, which has to be loaded
11530 into the card using a utility which is part of the latest
11531 isdn4k-utils package. Please read the file
11532 Documentation/isdn/README.act2000 for more information.
11534 Support for AP1000 multicomputer
11536 This enables support for a SPARC based parallel multi-computer
11537 called AP1000+. For details on our efforts to port Linux to this
11538 machine see http://cap.anu.edu.au/cap/projects/linux or mail to
11539 hackers@cafe.anu.edu.au
11541 Support for Sun4 architecture
11543 Say Y here if, and only if, your machine is a Sun4. Note that
11544 a kernel compiled with this option will run only on Sun4.
11545 (And the current version will probably work only on sun4/330.)
11547 SPARC ESP SCSI support
11549 This is the driver for the Sun ESP SCSI host adapter. The ESP
11550 chipset is present in most SPARC-based computers.
11552 SPARC /dev/openprom compatibility driver (EXPERIMENTAL)
11553 CONFIG_SUN_OPENPROMIO
11554 This driver provides user programs with an interface to the SPARC
11555 PROM device tree. The driver implements a SunOS-compatible
11556 interface and a NetBSD-compatible interface.
11558 If you want to compile this as a module ( = code which can be
11559 inserted in and removed from the running kernel whenever you want),
11560 say M and read Documentation/modules.txt. If unsure, say Y.
11562 Mostek real time clock support
11563 CONFIG_SUN_MOSTEK_RTC
11564 The Mostek RTC chip is used on all knows Sun computers except
11565 some JavaStations. For a JavaStation you need to say Y both here
11566 and to "Enhanced Real Time Clock Support".
11568 Say Y here unless you are building a special purpose kernel.
11570 #Siemens SAB82532 serial support
11573 ### Please someone fill these in.
11577 # m68k-specific kernel options
11578 # Documented by Chris Lawrence <quango@themall.net> et al.
11582 This option enables support for the Amiga series of computers. If
11583 you plan to use this kernel on an Amiga, say Y here and browse the
11584 material available in Documentation/m68k; otherwise say N.
11588 This option enables support for the 68000-based Atari series of
11589 computers (including the TT, Falcon and Medusa). If you plan to use
11590 this kernel on an Atari, say Y here and browse the material
11591 available in Documentation/m68k; otherwise say N.
11595 This option enables support for the Hades Atari clone. If you plan
11596 to use this kernel on a Hades, say Y here; otherwise say N.
11600 This option enables support for the Apple Macintosh series of
11601 computers (yes, there is experimental support now, at least for part
11604 Say N unless you're willing to code the remaining necessary support.
11609 This option enables support for the HP9000/300 series of
11610 workstations. Support for these machines is still very experimental.
11611 If you plan to try to use the kernel on such a machine say Y here.
11612 Everybody else says N.
11616 This option enables support for the Sun 3 series of workstations. Be
11617 warned that this support is very experimental. You will also want to
11618 say Y to 68020 support and N to the other processors below.
11619 Currently, it is not possible to build a kernel with support for the
11620 Sun 3 and something else, so make sure you have said N to all the
11621 other machines. This option does not support the sun3x series of
11622 machines (the Sun 3/80 and 3/460). If you don't want to compile a
11623 kernel for a Sun 3, say N.
11627 If you anticipate running this kernel on a computer with a MC68020
11628 processor, say Y. Otherwise, say N. Note that the 68020 requires a
11629 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
11630 Sun 3, which provides its own version.
11634 If you anticipate running this kernel on a computer with a MC68030
11635 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
11636 work, as it does not include an MMU (Memory Management Unit).
11640 If you anticipate running this kernel on a computer with a MC68LC040
11641 or MC68040 processor, say Y. Otherwise, say N. Note that an
11642 MC68EC040 will not work, as it does not include an MMU (Memory
11647 If you anticipate running this kernel on a computer with a MC68060
11648 processor, say Y. Otherwise, say N.
11650 Math emulation support (EXPERIMENTAL)
11652 At some point in the future, this will cause floating-point math
11653 instructions to be emulated by the kernel on machines that lack a
11654 floating-point math coprocessor. Thrill-seekers and chronically
11655 sleep-deprived psychotic hacker types can say Y now, everyone else
11656 should probably wait a while.
11658 Math emulation only kernel
11659 CONFIG_M68KFPU_EMU_ONLY
11660 This option prevents any floating-point instructions from being
11661 compiled into the kernel, thereby the kernel doesn't save any
11662 floating point context anymore during task switches, so this
11663 kernel will only be usable on machines without a floating-point
11664 math coprocessor. This makes the kernel a bit faster as no tests
11665 needs to be executed whether a floating-point instruction in the
11666 kernel should be executed or not.
11668 Math emulation extra precision
11669 CONFIG_M68KFPU_EMU_EXTRAPREC
11670 The fpu uses normally a few bit more during calculations for
11671 correct rounding, the emulator can (often) do the same but this
11672 extra calculation can cost quite some time, so you can disable
11673 it here. The emulator will then "only" calculate with a 64 bit
11674 mantissa and round slightly incorrect, what is more then enough
11677 Advanced processor options
11678 CONFIG_ADVANCED_CPU
11679 This gives you access to some advanced options for the CPU. The
11680 defaults should be fine for most users, but these options may make
11681 it possible for you to improve performance somewhat if you know what
11682 you are doing. Most users should say N to this question.
11684 Use read-modify-write instructions
11686 This allows to use certain instructions that work with indivisible
11687 read-modify-write bus cycles. While this is faster than the
11688 workaround of disabling interrupts, it can conflict with DMA
11689 ( = direct memory access) on many Amiga systems, and it is also said
11690 to destabilize other machines. It is very likely that this will
11691 cause serious problems on any Amiga or Atari Medusa if set. The only
11692 configuration where it should work are 68030-based Ataris, where it
11693 apparently improves performance. But you've been warned! Unless you
11694 really know what you are doing, say N. Try Y only if you're quite
11697 Amiga AutoConfig Identification
11699 This enables support for automatic identification of Amiga expansion
11700 cards that obey the AutoConfig(tm) specification.
11701 Say Y if you want your expansion cards to be identified on bootup;
11702 it will enlarge your kernel by about 10 KB. The identification
11703 information is also available through /proc/zorro (say Y to
11704 "/proc filesystem support"!).
11706 Note that even if you say N here, you can still use your expansion
11707 cards. If in doubt, say Y.
11709 Amiga 1200/600 PCMCIA support (EXPERIMENTAL)
11710 CONFIG_AMIGA_PCMCIA
11711 Include support in the kernel for pcmcia on Amiga 1200 and Amiga
11712 600. If you intend to use pcmcia cards say Y; otherwise say N.
11714 Amiga GSP (TMS340x0) support
11716 Include support for Amiga graphics cards that use the Texas
11717 Instruments TMS340x0 GSP (Graphics Signal Processor) chips. Say Y
11718 if you want to use a DMI Resolver or Commodore A2410 (Lowell)
11719 graphics card on an Amiga; otherwise, say N.
11721 DMI Resolver support
11722 CONFIG_GSP_RESOLVER
11723 Include support in the kernel for the DMI Resolver graphics card. If
11724 you have one, say Y; otherwise, say N.
11728 Include support in the kernel for the Commodore/University of Lowell
11729 A2410 graphics card. If you have one, say Y; otherwise, say N.
11731 Amiga Zorro II ramdisk support
11733 This enables support for using Chip RAM and Zorro II RAM as a
11734 ramdisk or as a swap partition. Say Y if you want to include this
11735 driver in the kernel. This driver is also available as a module
11736 ( = code which can be inserted in and removed from the running
11737 kernel whenever you want). The module is called z2ram.o. If you want
11738 to compile it as a module, say M here and read
11739 Documentation/modules.txt.
11741 Atari ST-RAM swap support
11743 This enables support for using (parts of) ST-RAM as swap space,
11744 instead of as normal system memory. This can first enhance system
11745 performance if you have lots of alternate RAM (compared to the size
11746 of ST-RAM), because executable code always will reside in faster
11747 memory. ST-RAM will remain as ultra-fast swap space. On the other
11748 hand, it allows much improved dynamic allocations of ST-RAM buffers
11749 for device driver modules (e.g. floppy, ACSI, SLM printer, DMA
11750 sound). The probability that such allocations at module load time
11751 fail is drastically reduced.
11755 This enables support for the Atari ACSI interface. The driver
11756 supports hard disks and CD-ROMs, which have 512-byte sectors, or can
11757 be switched to that mode. Due to the ACSI command format, only disks
11758 up to 1 GB are supported. Special support for certain ACSI to SCSI
11759 adapters, which could relax that, isn't included yet. The ACSI
11760 driver is also the basis for certain other drivers for devices
11761 attached to the ACSI bus: Atari SLM laser printer, BioNet-100
11762 Ethernet, and PAMsNet Ethernet. If you want to use one of these
11763 devices, you need ACSI support, too.
11765 This driver is also available as a module ( = code which can be
11766 inserted in and removed from the running kernel whenever you want).
11767 The module will be called acsi.o.
11769 Probe all LUNs on each ACSI device
11770 CONFIG_ACSI_MULTI_LUN
11771 If you have a ACSI device that supports more than one LUN (Logical
11772 Unit Number), e.g. a CD jukebox, you should say Y here so that all
11773 will be found by the ACSI driver. An ACSI device with multiple LUNs
11774 acts logically like multiple ACSI devices. The vast majority of ACSI
11775 devices have only one LUN, and so most people can say N here and
11776 should in fact do so, because it is safer.
11778 Atari SLM laser printer support
11780 If you have an Atari SLM laser printer, say Y to include support for
11781 it in the kernel. Otherwise, say N. This driver is also available as
11782 a module ( = code which can be inserted in and removed from the
11783 running kernel whenever you want). The module will be called
11784 acsi_slm.o. Be warned: the driver needs much ST-RAM and can cause
11785 problems due to that fact!
11787 A3000 WD33C93A support
11789 If you have an Amiga 3000 and have SCSI devices connected to the
11790 built-in SCSI controller, say Y. Otherwise, say N. This driver is
11791 also available as a module ( = code which can be inserted in and
11792 removed from the running kernel whenever you want). The module is
11793 called wd33c93.o. If you want to compile it as a module, say M here
11794 and read Documentation/modules.txt.
11796 A2091 WD33C93A support
11798 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
11799 say N. This driver is also available as a module ( = code which can
11800 be inserted in and removed from the running kernel whenever you
11801 want). The module is called wd33c93.o. If you want to compile it as
11802 a module, say M here and read Documentation/modules.txt.
11804 GVP Series II WD33C93A support
11806 If you have a Great Valley Products Series II SCSI controller,
11807 answer Y. Also say Y if you have a later model of GVP SCSI
11808 controller (such as the GVP A4008 or a Combo board). Otherwise,
11809 answer N. This driver does NOT work for the T-Rex series of
11810 accelerators from TekMagic and GVP-M.
11812 This driver is also available as a module ( = code which can be
11813 inserted in and removed from the running kernel whenever you
11814 want). The module will be called gvp11.o. If you want to compile it
11815 as a module, say M here and read Documentation/modules.txt.
11817 Cyberstorm SCSI support
11818 CONFIG_CYBERSTORM_SCSI
11819 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
11820 accelerator board and the optional Cyberstorm SCSI controller,
11821 answer Y. Otherwise, say N.
11823 Cyberstorm II SCSI support
11824 CONFIG_CYBERSTORMII_SCSI
11825 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
11826 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
11829 Blizzard 2060 SCSI support
11830 CONFIG_BLZ2060_SCSI
11831 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
11832 and want to use the onboard SCSI controller, say Y. Otherwise,
11835 Blizzard 1230IV/1260 SCSI support
11836 CONFIG_BLZ1230_SCSI
11837 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
11838 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
11841 Blizzard PowerUP 603e+ SCSI support (EXPERIMENTAL)
11842 CONFIG_BLZ603EPLUS_SCSI
11843 If you have an Amiga 1200 with a Phase5 Blizzard PowerUP 603e+
11844 accelerator, say Y. Otherwise, say N.
11846 Fastlane SCSI support
11847 CONFIG_FASTLANE_SCSI
11848 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
11849 one in the near future, say Y to this question. Otherwise, say N.
11851 Atari native SCSI support
11853 If you have an Atari with built-in NCR5380 SCSI controller (TT,
11854 Falcon, ...) say Y to get it supported. Of course also, if you have
11855 a compatible SCSI controller (e.g. for Medusa). This driver is also
11856 available as a module ( = code which can be inserted in and removed
11857 from the running kernel whenever you want). The module is called
11858 atari_scsi.o. If you want to compile it as a module, say M here and
11859 read Documentation/modules.txt. This driver supports both styles of
11860 NCR integration into the system: the TT style (separate DMA), and
11861 the Falcon style (via ST-DMA, replacing ACSI). It does NOT support
11862 other schemes, like in the Hades (without DMA).
11864 Long delays for Toshiba CD-ROMs
11865 CONFIG_ATARI_SCSI_TOSHIBA_DELAY
11866 This option increases the delay after a SCSI arbitration to
11867 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
11868 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
11869 would impact performance a bit, so say N.
11871 Hades SCSI DMA emulator (EXPERIMENTAL)
11873 This option enables code which emulates the TT SCSI DMA chip on the
11874 Hades. This increases the SCSI transfer rates at least ten times
11875 compared to PIO transfers. Note that this code is experimental and
11876 has only been tested on a Hades with a 68060 processor. Before you
11877 use this, make backups of your entire hard disk.
11881 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
11884 This driver is also available as a module ( = code which can be
11885 inserted in and removed from the running kernel whenever you
11886 want). The module is called ariadne.o. If you want to compile it as
11887 a module, say M here and read Documentation/modules.txt.
11891 If you have a Village Tronic Ariadne II Ethernet adapter, say Y.
11894 This driver is also available as a module ( = code which can be
11895 inserted in and removed from the running kernel whenever you
11896 want). The module is called ariadne2.o. If you want to compile it as
11897 a module, say M here and read Documentation/modules.txt.
11901 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
11904 This driver is also available as a module ( = code which can be
11905 inserted in and removed from the running kernel whenever you
11906 want). The module is called a2065.o. If you want to compile it as a
11907 module, say M here and read Documentation/modules.txt.
11911 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
11913 This driver is also available as a module ( = code which can be
11914 inserted in and removed from the running kernel whenever you
11915 want). The module is called hydra.o. If you want to compile it as a
11916 module, say M here and read Documentation/modules.txt.
11918 Pcmcia NE2000 compatible support
11920 If you have a pcmcia ne2000 compatible adapter, say Y. Otherwise,
11923 This driver is also available as a module ( = code which can be
11924 inserted in and removed from the running kernel whenever you
11925 want). The module is called apne.o. If you want to compile it as a
11926 module, say M here and read Documentation/modules.txt.
11928 Atari Lance support
11930 Say Y to include support for several Atari Ethernet adapters based
11931 on the AMD Lance chipset: RieblCard (with or without battery), or
11932 PAMCard VME (also the version by Rhotron, with different addresses).
11935 CONFIG_ATARI_BIONET
11936 Say Y to include support for BioData's BioNet-100 Ethernet adapter
11937 for the ACSI port. The driver works (has to work...) with a polled
11938 I/O scheme, so it's rather slow :-(
11941 CONFIG_ATARI_PAMSNET
11942 Say Y to include support for the PAMsNet Ethernet adapter for the
11943 ACSI port ("ACSI node"). The driver works (has to work...) with a
11944 polled I/O scheme, so it's rather slow :-(
11946 Multiface Card III parallel support
11947 CONFIG_MULTIFACE_III_LP
11948 If you have a Multiface III card for your Amiga, and want to use its
11949 parallel port in Linux, say Y. Otherwise, say N.
11951 This driver is also available as a module ( = code which can be
11952 inserted in and removed from the running kernel whenever you want).
11953 The module is called lp_m68k.o. If you want to compile it as a
11954 module, say M here and read Documentation/modules.txt.
11956 Amiga mouse support
11958 If you want to be able to use an Amiga mouse in Linux, say Y.
11960 This driver is also available as a module ( = code which can be
11961 inserted in and removed from the running kernel whenever you want).
11962 The module is called amigamouse.o. If you want to compile it as a
11963 module, say M here and read Documentation/modules.txt.
11965 Amiga Copper Console
11967 This configures the console to use the Amiga's graphics coprocessor
11968 for scrolling, instead of using the CPU. This option markedly
11969 improves response times in the high color modes (5 bitplanes and
11970 up). If you would like to use this, say Y; otherwise, say N.
11972 Atari mouse support
11974 If you want to be able to use an Atari mouse in Linux, say Y.
11976 This driver is also available as a module ( = code which can be
11977 inserted in and removed from the running kernel whenever you want).
11978 The module is called atarimouse.o. If you want to compile it as a
11979 module, say M here and read Documentation/modules.txt.
11981 Atari MFP serial support
11982 CONFIG_ATARI_MFPSER
11983 If you like to use the MFP serial ports ("Modem1", "Serial1") under
11984 Linux, say Y. The driver equally supports all kinds of MFP serial
11985 ports and automatically detects whether Serial1 is available.
11987 This driver is also available as a module ( = code which can be
11988 inserted in and removed from the running kernel whenever you want).
11989 If you want to compile it as a module, say M here and read
11990 Documentation/modules.txt.
11992 Note for Falcon users: You also have an MFP port, it's just not
11993 wired to the outside... But you could use the port under Linux.
11995 Atari SCC serial support
11997 If you have serial ports based on a Zilog SCC chip (Modem2, Serial2,
11998 LAN) and like to use them under Linux, say Y. All built-in SCC's are
11999 supported (TT, MegaSTE, Falcon), and also the ST-ESCC. If you have
12000 two connectors for channel A (Serial2 and LAN), they are visible as
12001 two separate devices.
12003 This driver is also available as a module ( = code which can be
12004 inserted in and removed from the running kernel whenever you want).
12005 If you want to compile it as a module, say M here and read
12006 Documentation/modules.txt.
12008 Atari SCC serial DMA support
12009 CONFIG_ATARI_SCC_DMA
12010 This enables DMA support for receiving data on channel A of the SCC.
12011 If you have a TT you may say Y here and read
12012 drivers/char/atari_SCC.README. All other users should say N here,
12013 because only the TT has SCC-DMA, even if your machine keeps claiming
12016 Atari MIDI serial support
12018 If you want to use your Atari's MIDI port in Linux, say Y.
12020 This driver is also available as a module ( = code which can be
12021 inserted in and removed from the running kernel whenever you
12022 want). If you want to compile it as a module, say M here and read
12023 Documentation/modules.txt.
12025 Atari DSP56k Digital Signal Processor support (EXPERIMENTAL)
12026 CONFIG_ATARI_DSP56K
12027 If you want to be able to use the DSP56001 in Falcons, say Y. This
12028 driver is still experimental, and if you don't know what it is, or
12029 if you don't have this processor, just say N.
12031 This driver is also available as a module ( = code which can be
12032 inserted in and removed from the running kernel whenever you want).
12033 If you want to compile it as a module, say M here and read
12034 Documentation/modules.txt.
12036 Amiga builtin serial support
12037 CONFIG_AMIGA_BUILTIN_SERIAL
12038 If you want to use your Amiga's built-in serial port in Linux,
12041 This driver is also available as a module ( = code which can be
12042 inserted in and removed from the running kernel whenever you
12043 want). If you want to compile it as a module, say M here and read
12044 Documentation/modules.txt.
12046 GVP IO-Extender support
12048 If you want to use a GVP IO-Extender serial card in Linux, say Y.
12051 Multiface Card III serial support
12052 CONFIG_MULTIFACE_III_TTY
12053 If you want to use a Multiface III card's serial port in Linux,
12056 This driver is also available as a module ( = code which can be
12057 inserted in and removed from the running kernel whenever you want).
12058 If you want to compile it as a module, say M here and read
12059 Documentation/modules.txt.
12061 Amiga or Atari DMA sound support
12063 If you want to use the internal audio of your Atari or Amiga in
12064 Linux, answer Y to this question. This will provide a Sun-like
12065 /dev/audio, compatible with the Linux/i386 sound system. Otherwise,
12068 This driver is also available as a module ( = code which can be
12069 inserted in and removed from the running kernel whenever you
12070 want). If you want to compile it as a module, say M here and read
12071 Documentation/modules.txt.
12073 HP DCA serial support
12075 If you want to use the internal "DCA" serial ports on an HP300
12076 machine, say Y here.
12078 HP on-board LANCE support
12080 If you want to use the builtin "LANCE" Ethernet controller on an
12081 HP300 machine, say Y here.
12083 Sun 3 onboard LANCE support
12085 If you want to use the onboard AMD "LANCE" (le) Ethernet hardware
12086 on a Sun 3, you will need to say Y here.
12090 Say Y here to enable support for the "DIO" expansion bus used in
12091 HP300 machines. If you are using such a system you almost certainly
12096 There are two types of PowerPC chips supported. The more common
12097 types (601,603,604,740,750) and the embedded versions (821 and 860).
12098 Unless you are building a kernel for one of the embedded boards
12099 using the 821 or 860 choose 6xx.
12103 Linux currently supports several different kinds of PowerPC-based
12104 machines: Apple Power Macintoshes and clones (such as the Motorola
12105 Starmax series), PReP (PowerPC Reference Platform) machines such as
12106 the Motorola PowerStack, Amiga Power-Up systems (APUS), CHRP and the
12107 embedded MBX boards from Motorola. Currently, a single kernel binary
12108 only supports one type or the other. However, there is very early
12109 work on support for CHRP, PReP and PowerMac's from a single binary.
12111 Support for Open Firmware device tree in /proc
12112 CONFIG_PROC_DEVICETREE
12113 This option adds a device-tree directory under /proc which contains
12114 an image of the device tree that the kernel copies from Open
12115 Firmware. If unsure, say Y here.
12117 MESH (Power Mac internal SCSI) support
12119 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
12120 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
12121 other Power Macintoshes do). Say Y to include support for this SCSI
12122 adaptor. This driver is also available as a module called mesh.o
12123 ( = code which can be inserted in and removed from the running
12124 kernel whenever you want). If you want to compile it as a module,
12125 say M here and read Documentation/modules.txt.
12127 Maximum synchronous transfer rate
12128 CONFIG_SCSI_MESH_SYNC_RATE
12129 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
12130 drives a bus which is entirely internal to the machine (such as the
12131 7500, 7600, 8500, etc.), the MESH is capable of synchronous
12132 operation at up to 10 MB/s. On machines where the SCSI bus
12133 controlled by the MESH can have external devices connected, it is
12134 usually rated at 5 MB/s. 5 is a safe value here unless you know the
12135 MESH SCSI bus is internal only; in that case you can say 10. Say 0
12136 to disable synchronous operation.
12138 53C94 (Power Mac external SCSI) support
12139 CONFIG_SCSI_MAC53C94
12140 On Power Macintoshes (and clones) with two SCSI buses, the external
12141 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
12142 machines which only have one SCSI bus, such as the 7200, also use
12143 the 53C94. Say Y to include support for the 53C94.
12145 This driver is also available as a module called mac53c94.o ( = code
12146 which can be inserted in and removed from the running kernel
12147 whenever you want). If you want to compile it as a module, say M
12148 here and read Documentation/modules.txt.
12150 MACE (Power Mac Ethernet) support
12152 Power Macintoshes and clones with Ethernet built-in on the
12153 motherboard will usually use a MACE (Medium Access Control for
12154 Ethernet) interface. Say Y to include support for the MACE chip.
12156 This driver is also available as a module called mace.o ( = code
12157 which can be inserted in and removed from the running kernel
12158 whenever you want). If you want to compile it as a module, say M
12159 here and read Documentation/modules.txt.
12161 BMAC (G3 ethernet) support
12163 Say Y for support of BMAC Ethernet interfaces. These are used on G3
12166 This driver is also available as a module called bmac.o ( = code
12167 which can be inserted in and removed from the running kernel
12168 whenever you want). If you want to compile it as a module, say M
12169 here and read Documentation/modules.txt.
12173 Support for audio/video capture and overlay devices and FM radio
12174 cards. The exact capabilities of each device vary. User tools for
12175 this are available from
12176 ftp://ftp.uk.linux.org/pub/linux/video4linux .
12178 If you are interested in writing a driver for such an audio/video
12179 device or user software interacting with such a driver, please read
12180 the file Documentation/video4linux/API.html.
12182 This driver is also available as a module called videodev.o ( = code
12183 which can be inserted in and removed from the running kernel
12184 whenever you want). If you want to compile it as a module, say M
12185 here and read Documentation/modules.txt.
12187 AIMSlab RadioTrack (aka RadioReveal) support
12188 CONFIG_RADIO_RTRACK
12189 Choose Y here if you have one of these FM radio cards, and then fill
12190 in the port address below.
12192 Note that newer AIMSlab RadioTrack cards have a different chipset
12193 and are not supported by this driver. For these cards, use the
12194 RadioTrack II driver below.
12196 If you have a GemTeks combined (PnP) sound- and radio card you must
12197 use this driver as a module and setup the card with isapnptools. You
12198 must also pass the module a suitable io parameter, 0x248 has been
12199 reported to be used by these cards.
12201 In order to control your radio card, you will need to use programs
12202 that are compatible with the Video for Linux API. Information on
12203 this API and pointers to "v4l" programs may be found on the WWW at
12204 http://roadrunner.swansea.uk.linux.org/v4l.shtml . More information
12205 is contained in the file Documentation/video4linux/radiotrack.txt.
12207 If you want to compile this driver as a module ( = code which can be
12208 inserted in and removed from the running kernel whenever you want),
12209 say M here and read Documentation/modules.txt. The module will be
12210 called radio-aimslab.o.
12212 RadioTrack i/o port
12213 CONFIG_RADIO_RTRACK_PORT
12214 Enter either 0x30f or 0x20f here. The card default is 0x30f, if you
12215 haven't changed the jumper setting on the card.
12217 AIMSlab RadioTrack II support
12218 CONFIG_RADIO_RTRACK2
12219 Choose Y here if you have this FM radio card, and then fill in the
12220 port address below.
12222 In order to control your radio card, you will need to use programs
12223 that are compatible with the Video for Linux API. Information on
12224 this API and pointers to "v4l" programs may be found on the WWW at
12225 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
12227 If you want to compile this driver as a module ( = code which can be
12228 inserted in and removed from the running kernel whenever you want),
12229 say M here and read Documentation/modules.txt. The module will be
12230 called radio-rtrack2.o.
12232 RadioTrack II i/o port
12233 CONFIG_RADIO_RTRACK2_PORT
12234 Enter either 0x30c or 0x20c here. The card default is 0x30c, if you
12235 haven't changed the jumper setting on the card.
12237 Aztech/Packard Bell Radio
12238 CONFIG_RADIO_AZTECH
12239 Choose Y here if you have one of these FM radio cards, and then fill
12240 in the port address below.
12242 In order to control your radio card, you will need to use programs
12243 that are compatible with the Video for Linux API. Information on
12244 this API and pointers to "v4l" programs may be found on the WWW at
12245 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
12247 If you want to compile this driver as a module ( = code which can be
12248 inserted in and removed from the running kernel whenever you want),
12249 say M here and read Documentation/modules.txt. The module will be
12250 called radio-aztech.o.
12252 Aztech/Packard Bell radio card i/o port
12253 CONFIG_RADIO_AZTECH_PORT
12254 Enter either 0x350 or 0x358 here. The card default is 0x350, if you
12255 haven't changed the setting of jumper JP3 on the card. Removing the
12256 jumper sets the card to 0x358.
12258 ADS Cadet AM/FM Radio Tuner Card
12260 Choose Y here if you have one of these AM/FM radio cards, and then
12261 fill in the port address below.
12263 In order to control your radio card, you will need to use programs
12264 that are compatible with the Video for Linux API. Information on
12265 this API and pointers to "v4l" programs may be found on the WWW at
12266 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
12268 Further documentation on this driver can be found on the WWW at
12269 http://linux.blackhawke.net/cadet.html .
12271 If you want to compile this driver as a module ( = code which can be
12272 inserted in and removed from the running kernel whenever you want),
12273 say M here and read Documentation/modules.txt. The module will be
12274 called radio-cadet.o.
12276 ADS Cadet AM/FM Radio Tuner Card I/O Port
12277 CONFIG_RADIO_CADET_PORT
12278 Enter the I/O address of the card here (most commonly 330).
12281 CONFIG_RADIO_SF16FMI
12282 Choose Y here if you have one of these FM radio cards, and then fill
12283 in the port address below.
12285 In order to control your radio card, you will need to use programs
12286 that are compatible with the Video for Linux API. Information on
12287 this API and pointers to "v4l" programs may be found on the WWW at
12288 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
12290 If you want to compile this driver as a module ( = code which can be
12291 inserted in and removed from the running kernel whenever you want),
12292 say M here and read Documentation/modules.txt. The module will be
12293 called radio-sf16fmi.o
12295 SF16FMI I/O port (0x284 or 0x384)
12296 CONFIG_RADIO_SF16FMI_PORT
12297 Enter the I/O port of your SF16FMI radio card.
12300 CONFIG_RADIO_TYPHOON
12301 Choose Y here if you have one of these FM radio cards, and then fill
12302 in the port address and the frequency used for muting below.
12304 In order to control your radio card, you will need to use programs
12305 that are compatible with the Video for Linux API. Information on
12306 this API and pointers to "v4l" programs may be found on the WWW at
12307 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
12309 If you want to compile this driver as a module ( = code which can be
12310 inserted in and removed from the running kernel whenever you want),
12311 say M here and read Documentation/modules.txt. The module will be
12312 called radio-typhoon.o
12314 Support for /proc/radio-typhoon
12315 CONFIG_RADIO_TYPHOON_PROC_FS
12316 Say Y here if you want the typhoon radio card driver to write
12317 status information (frequency, volume, muted, mute frequency,
12318 base address) to /proc/radio-typhoon. The file can be viewed with
12319 your favorite pager (i.e. use "more /proc/radio-typhoon" or "less
12320 /proc/radio-typhoon" or simply "cat /proc/radio-typhoon").
12322 Typhoon I/O port (0x316 or 0x336)
12323 CONFIG_RADIO_TYPHOON_PORT
12324 Enter the I/O port of your Typhoon or EcoRadio radio card.
12326 Typhoon frequency set when muting the device (kHz)
12327 CONFIG_RADIO_TYPHOON_MUTEFREQ
12328 Enter the frequency used for muting the radio. The device is never
12329 completely silent. If the volume is just turned down, you can still
12330 hear silent voices and music. For that reason, the frequency of the
12331 radio device is set to the frequency you can enter here whenever
12332 the device is muted. There should be no local radio station at that
12336 CONFIG_RADIO_ZOLTRIX
12337 Choose Y here if you have one of these FM radio cards, and then fill
12338 in the port address below.
12340 In order to control your radio card, you will need to use programs
12341 that are compatible with the Video for Linux API. Information on
12342 this API and pointers to "v4l" programs may be found on the WWW at
12343 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
12345 If you want to compile this driver as a module ( = code which can be
12346 inserted in and removed from the running kernel whenever you want),
12347 say M here and read Documentation/modules.txt. The module will be
12348 called radio-zoltrix.o
12350 ZOLTRIX I/O port (0x20c or 0x30c)
12351 CONFIG_RADIO_ZOLTRIX_PORT
12352 Enter the I/O port of your Zoltrix radio card.
12354 IIC on parallel port
12356 I2C is a simple serial bus system used in many micro controller
12357 applications. Saying Y here will allow you to use your parallel port
12358 as an I2C interface.
12360 If you want to compile this driver as a module ( = code which can be
12361 inserted in and removed from the running kernel whenever you want),
12362 say M here and read Documentation/modules.txt. The module will be
12363 called i2c-parport.o.
12366 CONFIG_RADIO_MIROPCM20
12367 Choose Y here if you have this FM radio card. You also need to say Y
12368 to "ACI mixer (miroPCM12/PCM20)" (in "additional low level sound
12369 drivers") for this to work.
12371 In order to control your radio card, you will need to use programs
12372 that are compatible with the Video for Linux API. Information on
12373 this API and pointers to "v4l" programs may be found on the WWW at
12374 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
12376 If you want to compile this driver as a module ( = code which can be
12377 inserted in and removed from the running kernel whenever you want),
12378 say M here and read Documentation/modules.txt. The module will be
12379 called radio-miropcm20.o
12382 CONFIG_RADIO_GEMTEK
12383 Choose Y here if you have this FM radio card, and then fill in the
12384 port address below.
12386 In order to control your radio card, you will need to use programs
12387 that are compatible with the Video for Linux API. Information on
12388 this API and pointers to "v4l" programs may be found on the WWW at
12389 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
12391 If you want to compile this driver as a module ( = code which can be
12392 inserted in and removed from the running kernel whenever you want),
12393 say M here and read Documentation/modules.txt. The module will be
12394 called radio-gemtek.o.
12397 CONFIG_RADIO_GEMTEK_PORT
12398 Enter either 0x20c, 0x30c, 0x24c or 0x34c here. The card default is
12399 0x34c, if you haven't changed the jumper setting on the card.
12401 PlanB Video-In for PowerMacs
12403 PlanB is the V4L driver for the PowerMac 7x00/8x00 series video
12404 input hardware. If you want to experiment with this, say Y.
12405 Otherwise, or if you don't understand a word, say N.
12406 See http://www.cpu.lu/~mlan/planb.html for more info.
12408 Saying M will compile this driver as a module (planb.o).
12410 TerraTec ActiveRadio
12411 CONFIG_RADIO_TERRATEC
12412 Choose Y here if you have this FM radio card, and then fill in the
12413 port address below. (TODO)
12415 Note: This driver is in its early stages. Right now volume and
12416 frequency control and muting works at least for me, but
12417 unfortunately i have not found anybody who wants to use this card
12418 with linux. So if it is this what YOU are trying to do right now,
12419 PLEASE DROP ME A NOTE!! Rolf Offermanns (rolf@offermanns.de)
12421 In order to control your radio card, you will need to use programs
12422 that are compatible with the Video for Linux API. Information on
12423 this API and pointers to "v4l" programs may be found on the WWW at
12424 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
12425 you need to have access to a machine on the Internet that has a
12426 program like lynx or netscape.
12428 If you want to compile this driver as a module ( = code which can be
12429 inserted in and removed from the running kernel whenever you want),
12430 say M here and read Documentation/modules.txt. The module will be
12431 called radio-terratec.o.
12433 # Zoran ZR36057/36060 support
12434 # CONFIG_VIDEO_ZORAN
12436 # Include support for Iomega Buz
12439 BT848 Video For Linux
12441 Support for BT848 based frame grabber/overlay boards. This includes
12442 the Miro, Hauppauge and STB boards. Please read the material in
12443 Documentation/video4linux/bttv for more information.
12445 This driver is also available as a module called bttv.o ( = code
12446 which can be inserted in and removed from the running kernel
12447 whenever you want). If you want to compile it as a module, say M
12448 here and read Documentation/modules.txt.
12450 ZR36120/36125 Video for Linux
12451 CONFIG_VIDEO_ZR36120
12452 Support for ZR36120/ZR36125 based frame grabber/overlay boards.
12453 This includes the Victor II, WaveWatcher, Video Wonder, Maxi-TV,
12454 and Buster boards. Please read the material in
12455 Documentation/video4linux/zr36120.txt for more information.
12457 This driver is also available as a module called zr36120.o ( = code
12458 which can be inserted in and removed from the running kernel
12459 whenever you want). If you want to compile it as a module, say M
12460 here and read Documentation/modules.txt.
12462 SAA5249 Teletext processor
12463 CONFIG_VIDEO_SAA5249
12464 Support for I2C bus based teletext using the SAA5249 chip. At the
12465 moment this is only useful on some European WinTV cards.
12467 This driver is also available as a module called saa5249.o ( = code
12468 which can be inserted in and removed from the running kernel
12469 whenever you want). If you want to compile it as a module, say M
12470 here and read Documentation/modules.txt.
12472 Quickcam BW Video For Linux
12473 CONFIG_VIDEO_BWQCAM
12474 Say Y have if you the black and white version of the QuickCam
12475 camera. See the next option for the color version.
12477 This driver is also available as a module called bw-qcam.o ( = code
12478 which can be inserted in and removed from the running kernel
12479 whenever you want). If you want to compile it as a module, say M
12480 here and read Documentation/modules.txt.
12482 Colour QuickCam Video For Linux
12484 This is the video4linux driver for the colour version of the
12485 Connectix Quickcam. If you have one of these cameras, say Y here,
12486 otherwise say N. This driver does not work with the original
12487 monochrome Quickcam, Quickcam VC or QuickClip. It is also available
12488 as a module (c-qcam.o).
12490 Mediavision Pro Movie Studio Video For Linux
12492 Say Y if you have such a thing. This driver is also available as a
12493 module called pms.o ( = code which can be inserted in and removed
12494 from the running kernel whenever you want). If you want to compile
12495 it as a module, say M here and read Documentation/modules.txt.
12497 Compaq SMART2 support
12499 This is the driver for Compaq Smart Array controllers.
12500 Everyone using these boards should say Y here.
12501 See the file Documentation/cpqarray.txt for the current list of
12502 boards supported by this driver, and for further information
12503 on the use of this driver.
12510 This selects the processor type of your CPU. This is only used to
12511 determine C compiler optimization options, and can affect the
12512 compatibility of the kernel on other processors. If you specify
12513 ARM6, the kernel should work on all 32-bit processors. If you
12514 specify ARM2, ARM250 or ARM3, it should work on all 26-bit
12515 processors. If you're not sure, set it to "None".
12519 This selects what ARM system you wish to build the kernel for. It
12520 also selects to some extent the CPU type. If you are unsure what
12521 to set this option to, please consult any information supplied with
12524 Include support for Chalice CATS boards
12526 Say Y here if you intend to run this kernel on a CATS system.
12528 Include support for Intel EBSA285
12529 CONFIG_ARCH_EBSA285
12532 Include support for the NetWinder
12533 CONFIG_ARCH_NETWINDER
12534 Say Y here if you intend to run this kernel on the NetWinder.
12536 Virtual/Physical Memory Split
12538 If you are compiling a kernel which will never run on a machine
12539 with more than 1 Gigabyte total physical RAM, answer "3GB/1GB"
12540 here (default choice).
12542 On 32-bit x86 systems Linux can use up to 64 Gigabytes of physical
12543 memory. However 32-bit x86 processors have only 4 Gigabytes of
12544 virtual memory space. This option specifies the maximum amount of
12545 virtual memory space one process can potentially use. Certain types
12546 of applications (eg. database servers) perform better if they have
12547 as much virtual memory per process as possible.
12549 The remaining part of the 4G virtual memory space is used by the
12550 kernel to 'permanently map' as much physical memory as possible.
12551 Certain types of applications perform better if there is more
12552 'permanently mapped' kernel memory.
12554 [WARNING! Certain boards do not support PCI DMA to physical addresses
12555 bigger than 2 Gigabytes. Non-DMA-able memory must not be permanently
12556 mapped by the kernel, thus a 1G/3G split will not work on such boxes.]
12558 As you can see there is no 'perfect split' - the fundamental
12559 problem is that 4G of 32-bit virtual memory space is short. So
12560 you'll have to pick your own choice - depending on the application
12561 load of your box. A 2G/2G split is typically a good choice for a
12562 generic Linux server with lots of RAM.
12564 Any potentially remaining (not permanently mapped) part of physical
12565 memory is called 'high memory'. How much total high memory the kernel
12566 can handle is influenced by the (next) High Memory configuration option.
12568 The actual amount of total physical memory will either be
12569 autodetected or can be forced by using a kernel command line option
12570 such as "mem=256M". (Try "man bootparam" or see the documentation of
12571 your boot loader (lilo or loadlin) about how to pass options to the
12572 kernel at boot time. The lilo procedure is also explained in the
12573 SCSI-HOWTO, available from http://metalab.unc.edu/mdw/linux.html#howto .)
12577 Say Y to include the NWFPE floating point emulator in the kernel.
12578 This is necessary to run most binaries. Linux does not currently
12579 support floating point hardware so you need to say Y here even if
12580 your machine has an FPA or floating point co-processor podule.
12582 It is also possible to say M to build the emulator as a module
12583 (nwfpe.o) or indeed to leave it out altogether. However, unless you
12584 know what you are doing this can easily render your machine
12585 unbootable. Saying Y is the safe option.
12587 You may say N here if you are going to load the Acorn FPEmulator
12588 early in the bootup.
12590 DS1620 Thermometer support
12592 Say Y here to include support for the thermal management hardware
12593 found in the NetWinder. This driver allows the user to control the
12594 temperature set points and to read the current temperature.
12596 It is also possible to say M here to build it as a module (ds1620.o)
12597 It is recommended to be used on a NetWinder, but it is not a
12600 Verbose kernel error messages
12601 CONFIG_DEBUG_ERRORS
12602 This option controls verbose debugging information which can be
12603 printed when the kernel detects an internal error. This debugging
12604 information is useful to kernel hackers when tracking down problems,
12605 but mostly meaningless to other people. It's safe to say Y unless
12606 you are concerned with the code size or don't want to see these
12609 Build Tools Selection
12610 CONFIG_BINUTILS_NEW
12611 Say Y here if and only if you're using GCC 2.8.1/EGCS with a
12612 binutils version >= 2.8.1 to compile the kernel (check with "gcc
12613 --version" and "ld -v").
12615 Compile kernel with frame pointer
12616 CONFIG_FRAME_POINTER
12617 If you say Y here, the resulting kernel will be slightly larger and
12618 slower, but it will give useful debugging information. If you don't
12619 debug the kernel, you can say N.
12621 User fault debugging
12623 When a user program crashes due to an exception, the kernel can
12624 print a brief message explaining what the problem was. This is
12625 sometimes helpful for debugging but serves no purpose on a
12626 production system. Most people should say N here.
12628 Include gdb debugging information in kernel binary
12630 Say Y here to include source-level debugging information in the
12631 `vmlinux' binary image. This is handy if you want to use gdb or
12632 addr2line to debug the kernel. It has no impact on the in-memory
12633 footprint of the running kernel but it can increase the amount of
12634 time and disk space needed for compilation of the kernel. If in
12637 Split initialisation functions into discardable section
12638 CONFIG_TEXT_SECTIONS
12639 If you say Y here, kernel code that is only used during
12640 initialisation is collected into a special area of the kernel so
12641 that it can be discarded and the memory reclaimed when
12642 initialisation is complete. In addition, if the kernel you wish to
12643 build is able to run on multiple architectures, it allows the unused
12644 code to be discarded. Some versions of binutils, however, have a bug
12645 that causes the kernel to crash during startup when this option is
12646 enabled. Say Y unless you experience problems that you suspect may
12649 Disable pgtable cache (EXPERIMENTAL)
12650 CONFIG_NO_PGT_CACHE
12651 Normally the kernel maintains a `quicklist' of preallocated
12652 pagetable structures in order to increase performance. On machines
12653 with very few pages this may however be a loss. Say Y here to
12654 disable the pgtable cache.
12656 RISC OS personality
12658 Say Y here to include the kernel code necessary if you want to run
12659 Acorn RISC OS/Arthur binaries under Linux. This code is still very
12660 experimental; if this sounds frightening, say N and sleep in peace.
12661 You can also say M here to compile this support as a module (which
12662 will be called arthur.o).
12664 Initial kernel command line
12666 On some architectures (EBSA110 and CATS), there is currently no way
12667 for the boot loader to pass arguments to the kernel. For these
12668 architectures, you should supply some command-line options at build
12669 time by entering them here. As a minimum, you should specify the
12670 memory size and the root device (e.g., mem=64M root=/dev/nfs)
12672 Hardware alignment trap (EXPERIMENTAL)
12673 CONFIG_ALIGNMENT_TRAP
12674 ARM processors can not fetch/store information which is not
12675 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
12676 address divisible by 4. On 32-bit ARM processors, these non-aligned
12677 fetch/store instructions will be emulated in software if you say
12678 here, which has a severe performance impact. This is necessary for
12679 correct operation of some network protocols. With an IP-only
12680 configuration it is safe to say N, otherwise say Y.
12682 21285 serial port support
12683 CONFIG_SERIAL_21285
12684 If you have a machine based on a 21285 (Footbridge) StrongARM/PCI
12685 bridge you can enable its onboard serial port by enabling this
12686 option. The device has major ID 4, minor 64.
12688 Console on 21285 serial port
12689 CONFIG_SERIAL_21285_CONSOLE
12690 If you have enabled the serial port on the 21285 footbridge you can
12691 make it the console by answering Y to this option.
12694 CONFIG_HOST_FOOTBRIDGE
12695 The 21285 Footbridge chip can operate in either `host mode' or
12696 `add-in' mode. Say Y if your 21285 is in host mode, and therefore
12697 is the configuration master, otherwise say N. This must not be
12698 set to Y if the card is used in 'add-in' mode.
12700 MFM hard disk support
12702 Support the MFM hard drives on the Acorn Archimedes both
12703 on-board the A4x0 motherboards and via the Acorn MFM podules.
12704 Drives up to 64MB are supported. If you haven't got one of these
12705 machines or drives just say N.
12707 Old Archimedes floppy (1772) support
12708 CONFIG_BLK_DEV_FD1772
12709 Support the floppy drive on the Acorn Archimedes (A300, A4x0, A540,
12710 R140 and R260) series of computers; it supports only 720K floppies
12711 at the moment. If you don't have one of these machines just answer
12714 Autodetect hard drive geometry
12715 CONFIG_BLK_DEV_MFM_AUTODETECT
12716 If you answer Y, the MFM code will attempt to automatically detect
12717 the cylinders/heads/sectors count on your hard drive. WARNING: This
12718 sometimes doesn't work and it also does some dodgy stuff which
12719 potentially might damage your drive.
12723 Say Y here if you want to build support for the IrDA (TM) protocols.
12724 The Infrared Data Associations (tm) specifies standards for wireless
12725 infrared communication and is supported by most laptops and PDA's.
12727 To use Linux support for the IrDA (tm) protocols, you will also need
12728 some user-space utilities like the irmanager and probably irattach
12729 as well. For more information, see the file
12730 Documentation/networking/irda.txt. You also want to read the
12731 IR-HOWTO, available at http://metalab.unc.edu/mdw/linux.html#howto .
12733 This support is also available as a module. If you want to compile
12734 it as a module, say M here and read Documentation/modules.txt.
12736 IrDA Cache last LSAP
12737 CONFIG_IRDA_CACHE_LAST_LSAP
12738 Say Y here if you want IrLMP to cache the last LSAP used. This makes
12739 sense since most frames will be sent/received on the same
12740 connection. Enabling this option will save a hash-lookup per frame.
12745 CONFIG_IRDA_FAST_RR
12746 Say Y here is you want IrLAP to send fast RR (Receive Ready) frames
12747 when acting as a primary station. This will make IrLAP send out a RR
12748 frame immediately when receiving a frame if its own transmit queue
12749 is currently empty. This will give a lot of speed improvement when
12750 receiving much data since the secondary station will not have to
12751 wait the max. turn around time before it is allowed to transmit the
12752 next time. If the transmit queue of the secondary is also empty the
12753 primary will back off waiting longer for sending out the RR frame
12754 until the timeout reaches the normal value. Enabling this option
12755 will make the IR-diode burn more power and thus reduce your battery
12762 Say Y here if you want the IrDA subsystem to write debug information
12763 to your syslog. You can change the debug level in
12764 /proc/sys/net/irda/debug
12766 If unsure, say Y (since it makes it easier to find the bugs).
12768 IrLAP Compression support
12769 CONFIG_IRDA_COMPRESSION
12770 Compression is _not_ part of the IrDA(tm) protocol specification,
12771 but it's working great! Linux is the first to try out compression
12772 support at the IrLAP layer. This means that you will only benefit
12773 from compression if you are running a Linux <-> Linux configuration.
12775 If you say Y here, you also need to say Y or M to a compression
12778 IrLAP Deflate Compression Protocol (EXPERIMENTAL)
12779 CONFIG_IRDA_DEFLATE
12780 Say Y here if you want to build support for the Deflate compression
12781 protocol. The deflate compression (GZIP) is exactly
12782 the same as the one used by the PPP protocol.
12784 If you want to compile this compression support as a module, say M
12785 here and read Documentation/modules.txt. The module will be called
12790 Say Y here if you want to build support for the IrLAN protocol. If
12791 you want to compile it as a module, say M here and read
12792 Documentation/modules.txt. IrLAN emulates an Ethernet and makes it
12793 possible to put up a wireless LAN using infrared beams.
12795 The IrLAN protocol can be used to talk with infrared access points
12796 like the HP NetbeamIR, or the ESI JetEye NET. You can also connect
12797 to another Linux machine running the IrLAN protocol for ad-hoc
12802 Say Y here if you want to build support for the IrCOMM protocol. If
12803 you want to compile it as a module, say M here and read
12804 Documentation/modules.txt. IrCOMM implements serial port emulation,
12805 and makes it possible to use all existing applications that
12806 understands TTY's with an infrared link. Thus you should be able to
12807 use application like PPP, minicom and others. Enabling this option
12808 will create two modules called ircomm and ircomm_tty. For more
12809 information go to http://www.pluto.dti.ne.jp/~thiguchi/irda/
12811 IrTTY IrDA Device Driver
12813 Say Y here if you want to build support for the IrTTY line
12814 discipline. If you want to compile it as a module, say M here and
12815 read Documentation/modules.txt. IrTTY makes it possible to use
12816 Linux's own serial driver for all IrDA ports that are 16550
12817 compatible. Most IrDA chips are 16550 compatible so you should
12818 probably say Y to this option. Using IrTTY will however limit the
12819 speed of the connection to 115200 bps (IrDA SIR mode)
12823 IrPORT IrDA Device Driver
12825 Say Y here if you want to build support for the IrPORT IrDA device
12826 driver. If you want to compile it as a module, say M here and
12827 read Documentation/modules.txt. IrPORT can be used instead of
12828 IrTTY and sometimes this can be better. One example is if your
12829 IrDA port does not have echo-canceling, which will work OK with
12830 IrPORT since this driver is working in half-duplex mode only. You
12831 don't need to use irattach with IrPORT, but you just insert it
12832 the same way as FIR drivers (insmod irport io=0x3e8 irq=11).
12833 Notice that IrPORT is a SIR device driver which means that speed
12834 is limited to 115200 bps.
12838 SiS5513 chipset support
12839 CONFIG_BLK_DEV_SIS5513
12840 This driver ensures (U)DMA support for SIS5513 chipset based
12841 mainboards. SiS620/530 UDMA mode 4, SiS5600/5597 UDMA mode 2, all
12842 other DMA mode 2 limited chipsets are unsupported to date.
12844 If you say Y here, you need to say Y to "Use DMA by default when
12845 available" as well.
12847 Please read the comments at the top of drivers/block/sis5513.c
12849 Winbond W83977AF IrDA Device Driver
12851 Say Y here if you want to build IrDA support for the Winbond
12852 W83977AF super-io chipset. If you want to compile it as a module,
12853 say M here and read Documentation/modules.txt. This driver should be
12854 used for the IrDA chipset in the Corel NetWinder. The driver
12855 supports SIR, MIR and FIR (4Mbps) speeds.
12857 NSC PC87108 IrDA Device Driver
12859 Say Y here if you want to build support for the NSC PC87108 IrDA
12860 chipset. If you want to compile it as a module, say M here and
12861 read Documentation/modules.txt. This drivers currently only supports
12862 the ACTiSYS IR2000B ISA card and supports SIR, MIR and FIR (4Mbps)
12865 Toshiba Type-O IR Port Device Driver
12867 Say Y here if you want to build support for the Toshiba Type-O IR
12868 chipset. If you want to compile it as a module, say M here and
12869 read Documentation/modules.txt. This chipset is used by the Toshiba
12870 Libretto 100CT, and many more laptops.
12872 ESI JetEye PC Dongle
12874 Say Y here if you want to build support for the Extended Systems
12875 JetEye PC dongle. If you want to compile it as a module, say M here
12876 and read Documentation/modules.txt. The ESI dongle attaches to the
12877 normal 9-pin serial port connector, and can currently only be used
12878 by IrTTY. To activate support for ESI dongles you will have to
12879 insert "irattach -d esi" in the /etc/irda/drivers script.
12881 ACTiSYS IR-220L and IR220L+ dongle
12882 CONFIG_ACTISYS_DONGLE
12883 Say Y here if you want to build support for the ACTiSYS
12884 IR-220L and IR220L+ dongles. If you want to compile it as a module,
12885 say M here and read Documentation/modules.txt. The ACTiSYS dongles
12886 attaches to the normal 9-pin serial port connector, and can
12887 currently only be used by IrTTY. To activate support for ACTiSYS
12888 dongles you will have to insert "irattach -d actisys" or
12889 "irattach -d actisys_plus" in the/etc/irda/drivers script.
12891 Tekram IrMate 210B dongle
12892 CONFIG_TEKRAM_DONGLE
12893 Say Y here if you want to build support for the Tekram IrMate 210B
12894 dongle. If you want to compile it as a module, say M here
12895 and read Documentation/modules.txt. The Tekram dongle attaches to
12896 the normal 9-pin serial port connector, and can currently only be
12897 used by IrTTY. To activate support for Tekram dongles you will have
12898 to insert "irattach -d tekram" in the /etc/irda/drivers script.
12900 Greenwich GIrBIL dongle
12901 CONFIG_GIRBIL_DONGLE
12902 Say Y here if you want to build support for the Greenwich GIrBIL
12903 dongle. If you want to compile it as a module, say M here and read
12904 Documentation/modules.txt. The Greenwich dongle attaches to the
12905 normal 9-pin serial port connector, and can currently only be used
12906 by IrTTY. To activate support for Greenwich dongles you will have to
12907 insert "irattach -d girbil" in the /etc/irda/drivers script.
12909 Parallax Litelink dongle
12910 CONFIG_LITELINK_DONGLE
12911 Say Y here if you want to build support for the Parallax Litelink
12912 dongle. If you want to compile it as a module, say M here and read
12913 Documentation/modules.txt. The Parallax dongle attaches to the
12914 normal 9-pin serial port connector, and can currently only be used
12915 by IrTTY. To activate support for Parallax dongles you will have to
12916 insert "irattach -d litelink" in the /etc/irda/drivers script.
12918 Adaptec Airport 1000 and 2000 dongle
12919 CONFIG_AIRPORT_DONGLE
12920 Say Y here if you want to build support for the Adaptec Airport 1000
12921 and 2000 dongles. If you want to compile it as a module, say M here
12922 and read Documentation/modules.txt. The module will be called
12923 airport.o. The Airport dongle attaches to the normal 9-pin serial
12924 port connector, and can currently only be used by IrTTY. To activate
12925 support for Airport dongles you will have to insert "irattach -d
12926 airport" in the /etc/irda/drivers script.
12928 VME (Motorola and BVM) support
12930 Say Y here if you want to build a kernel for a 680x0 based VME
12931 board. Boards currently supported include Motorola boards MVME162,
12932 MVME166, MVME167, MVME172, and MVME177. BVME4000 and BVME6000
12933 boards from BVM Ltd are also supported.
12935 MVME162, 166 and 167 support
12937 Say Y to include support for Motorola VME boards. This will build a
12938 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
12939 MVME177 boards. If you select this option you will have to select
12940 the appropriate drivers for SCSI, Ethernet and serial ports later
12943 BVME4000 and BVME6000 support
12945 Say Y to include support for VME boards from BVM Ltd. This will
12946 build a kernel which can run on BVME4000 and BVME6000 boards. If
12947 you select this option you will have to select the appropriate
12948 drivers for SCSI, Ethernet and serial ports later on.
12950 Use write-through caching for 68060 supervisor accesses
12951 CONFIG_060_WRITETHROUGH
12952 The 68060 generally uses copyback caching of recently accessed data.
12953 Copyback caching means that memory writes will be held in an on-chip
12954 cache and only written back to memory some time later. Saying Y
12955 here will force supervisor (kernel) accesses to use writethrough
12956 caching. Writethrough caching means that data is written to memory
12957 straight away, so that cache and memory data always agree.
12958 Writethrough caching is less efficient, but is needed for some
12959 drivers on 68060 based systems where the 68060 bus snooping signal
12960 is hardwired on. The 53c710 SCSI driver is known to suffer from
12963 NCR53C710 SCSI driver for MVME16x
12964 CONFIG_MVME16x_SCSI
12965 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
12966 SCSI controller chip. Almost everyone using one of these boards
12967 will want to say Y to this question.
12969 NCR53C710 SCSI driver for BVME6000
12970 CONFIG_BVME6000_SCSI
12971 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
12972 SCSI controller chip. Almost everyone using one of these boards
12973 will want to say Y to this question.
12975 Simple 53c710 SCSI support (Compaq, NCR machines)
12977 This is a driver for the NCR53C710 chip commonly found in Compaq and
12978 NCR machines. If you are looking for 53C710 support for an Amiga or
12979 some 680x0 based VME card then you probably want the other NCR53C710
12982 MVME16x Ethernet support
12984 This is the driver for the Ethernet interface on the Motorola
12985 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
12986 driver for this chip in your kernel. If you want to compile it as
12987 a module, say M here and read Documentation/modules.txt.
12989 BVME6000 Ethernet support
12990 CONFIG_BVME6000_NET
12991 This is the driver for the Ethernet interface on BVME4000 and
12992 BVME6000 VME boards. Say Y here to include the driver for this chip
12993 in your kernel. If you want to compile it as a module, say M here
12994 and read Documentation/modules.txt.
12996 CD2401 support for MVME166/7 serial ports
12998 This is the driver for the serial ports on the Motorola MVME166,
12999 167, and 172 boards. Everyone using one of these boards should say
13002 SCC support for MVME162 serial ports
13004 This is the driver for the serial ports on the Motorola MVME162 and
13005 172 boards. Everyone using one of these boards should say Y here.
13007 SCC support for BVME6000 serial ports
13008 CONFIG_BVME6000_SCC
13009 This is the driver for the serial ports on the BVME4000 and BVME6000
13010 boards from BVM Ltd. Everyone using one of these boards should say
13013 Support for user-space parallel port device drivers
13015 Saying Y to this adds support for /dev/parport device nodes. This
13016 is needed for programs that want portable access to the parallel
13017 port, for instance deviceid (which displays Plug-and-Play device
13020 This is the parallel port equivalent of SCSI generic support (sg).
13021 It is safe to say N to this -- it is not needed for normal printing
13022 or parallel port CD-ROM/disk support.
13024 This support is also available as a module. If you want to compile
13025 it as a module, say M here and read Documentation/modules.txt. The
13026 module will be called ppdev.o.
13030 Kernel httpd acceleration (EXPERIMENTAL)
13032 The kernel httpd acceleration daemon (kHTTPd) is a (limited)
13033 web server build into the kernel. It is limited since it can only
13034 serve files from the filesystem. Saying "M" here builds the
13035 kHTTPd module; this is NOT enough to have a working kHTTPd.
13036 For safety reasons, the module has to be activated by doing a
13037 "echo 1 > /proc/sys/net/khttpd/start" after inserting the module.
13039 Before using this, read the README in /usr/src/linux/net/khttpd !
13041 The kHTTPd is experimental. Be careful when using it on a production
13042 machine. Also note that kHTTPd doesn't support virtual servers yet.
13045 # A couple of things I keep forgetting:
13046 # capitalize: AppleTalk, Ethernet, DOS, DMA, FAT, FTP, Internet,
13047 # Intel, IRQ, Linux, MSDOS, NetWare, NetWinder, NFS,
13049 # two words: hard drive, hard disk, sound card, home page
13050 # other: it's safe to save; daemon; use --, not - or ---
13053 # This is used by Emacs' spell checker ispell.el:
13055 # LocalWords: CONFIG coprocessor DX Pentium SX lilo loadlin HOWTO ftp metalab
13056 # LocalWords: unc edu docs emu README kB BLK DEV FD Thinkpad fd MFM RLL IDE gz
13057 # LocalWords: cdrom diskless netboot nfs xzvf ATAPI MB ide pavia rubini pl pd
13058 # LocalWords: HD CDROMs IDECD NEC MITSUMI filesystem XT XD PCI BIOS cezar ATEN
13059 # LocalWords: ISA EISA Microchannel VESA BIOSes IPC SYSVIPC ipc Ctrl dmesg hlt
13060 # LocalWords: BINFMT Linkable http ac uk jo html GCC SPARC AVANTI CABRIOLET EB
13061 # LocalWords: netscape gcc LD CC toplevel MODVERSIONS insmod rmmod modprobe IP
13062 # LocalWords: genksyms INET loopback gatewaying ethernet PPP ARP Arp MEMSIZE
13063 # LocalWords: howto multicasting MULTICAST MBONE firewalling ipfw ACCT resp ip
13064 # LocalWords: proc acct IPIP encapsulator decapsulator klogd PCTCP RARP EXT PS
13065 # LocalWords: telnetting subnetted NAGLE rlogin NOSR ttyS TGA techinfo mbone nl
13066 # LocalWords: Mb SKB IPX Novell dosemu Appletalk DDP ATALK vmalloc visar ehome
13067 # LocalWords: SD CHR scsi thingy SG CD LUNs LUN jukebox Adaptec BusLogic EATA
13068 # LocalWords: buslogic DMA DPT ATT eata dma PIO UltraStor fdomain umsdos ext
13069 # LocalWords: QLOGIC qlogic TMC seagate Trantor ultrastor FASST wd NETDEVICES
13070 # LocalWords: unix BBS linux CSLIP PLIP Kirch's LDP CSlip SL SCC IRQ csustan
13071 # LocalWords: Turbo Laplink plip NCSA port's ReQuest IRQs EQL SMC AMD PCnet NE
13072 # LocalWords: COM ELPLUS Com EtherLinkIII VLB Arcnet Cabletron DEPCA DE carlos
13073 # LocalWords: depca EtherWorks EWRK ewrk SEEQ EtherExpress EEXPRESS NI xxx dia
13074 # LocalWords: EtherExpress WaveLAN wavelan PCLAN HPLAN VG SK Ansel Xen de ZNET
13075 # LocalWords: PCMCIA cb stanford LAN TEC RealTek ATP atp DLINK NetTools VISWS
13076 # LocalWords: TR Sony CDU caddyless cdu Mitsumi MCD cd mcd XA MultiSession CDA
13077 # LocalWords: Matsushita Panasonic SBPCD Soundblaster Longshine sbpcd Aztech
13078 # LocalWords: Okano Wearnes AZTCD CDD SE aztcd sonycd Goldstar GSCD Philips fs
13079 # LocalWords: LMS OPTCD Sanyo SJCD minix faqs xiafs XIA msdos mtools Cichocki
13080 # LocalWords: std softlinks umssync NetworkFileSharing nfsd mountd CDs HPFS TI
13081 # LocalWords: hpfs SYSV SCO iBCS Wyse WordPerfect tsx mit unixes sysv NR irisa
13082 # LocalWords: SMB WfW Cyclades async mux Logitech busmouse MouseSystem aka AST
13083 # LocalWords: PSMOUSE Compaq trackballs Travelmate Inport ATIXL ATI busmice ld
13084 # LocalWords: gpm config QIC DYNCONF FTAPE Stor Ftape ftape pcsndrv manpage NT
13085 # LocalWords: readprofile diskdrives org com masq EtherTalk tcp netrom sunacm
13086 # LocalWords: misc AIC aic pio scc Portmaster eql GIS PhotoCDs MCDX Perell PG
13087 # LocalWords: mcdx gscd optcd sjcd ISP hdparm Workgroups Lan samba PARIDE PCD
13088 # LocalWords: filesystems smbfs ATA ppp PCTech RZ www powerquest txt CMD ESDI
13089 # LocalWords: chipset FB multicast MROUTE appletalk ifconfig IBMTR multiport
13090 # LocalWords: Multisession STALDRV EasyIO EC EasyConnection ISTALLION ONboard
13091 # LocalWords: Brumby pci TNC cis ohio faq usenet NETLINK dev hydra ca Tyne mem
13092 # LocalWords: carleton Deskstation DECstation SUNFD JENSEN Noname XXXM SLiRP
13093 # LocalWords: pppd Zilog ZS SRM bootloader ez mainmenu rarp ipfwadm paride pcd
13094 # LocalWords: RTNETLINK mknod xos MTU lwared Macs mac netatalk macs cs Wolff
13095 # LocalWords: dartmouth flowerpt MultiMaster FlashPoint tudelft etherexpress
13096 # LocalWords: ICL EtherTeam ETH IDESCSI TXC SmartRAID SmartCache httpd sjc dlp
13097 # LocalWords: thesphere TwoServers BOOTP DHCP ncpfs BPQETHER BPQ MG HIPPI cern
13098 # LocalWords: bsd comp SPARCstation le SunOS ie Gracilis PackeTwin PT pt LU FX
13099 # LocalWords: FX TEAC CR LCS mS ramdisk IDETAPE cmd fperllo encis tcfs unisa
13100 # LocalWords: Vertos Genoa Funai hsfs NCP NetWare tgz APM apm ioctls UltraLite
13101 # LocalWords: TravelMate CDT LCD backlight VC RPC Mips AXP barlow cdrecord pg
13102 # LocalWords: PMAX MILO Alphas Multia Tseng linuxelf endian mipsel mips drv HT
13103 # LocalWords: kerneld callouts AdvanSys advansys Admin WDT DataStor EP verden
13104 # LocalWords: wdt hdb hdc bugfix SiS vlb Acculogic CSA DTC dtc Holtek ht QDI
13105 # LocalWords: QD qd UMC umc ALI ali lena fnet fr azstarnet cdr fb MDA ps esdi
13106 # LocalWords: Avanti XL AlphaStations Jensen DECpc AXPpci UDB Cabriolet MCA RC
13107 # LocalWords: AlphaPC mca AOUT OUTput PPro sipx gwdg lo nwe FourPort Boca unm
13108 # LocalWords: Keepalive linefill RELCOM keepalive analogue CDR conf CDI INIT
13109 # LocalWords: OPTi isp irq noisp VFAT vfat NTFS losetup dmsdosfs dosfs ISDN MP
13110 # LocalWords: NOWAYOUT behaviour dialin isdn callback BTX Teles ICN EDSS Cisco
13111 # LocalWords: ipppd syncppp RFC MPP VJ downloaded icn NICCY Creatix shmem ufr
13112 # LocalWords: ibp md ARCnet ether encap NDIS arcether ODI Amigas AmiTCP NetBSD
13113 # LocalWords: initrd tue util DES funet des OnNet BIOSP smc Travan Iomega CMS
13114 # LocalWords: FC DC dc PPA IOMEGA's ppa RNFS FMV Fujitsu ARPD arpd loran layes
13115 # LocalWords: FRAD indiana framerelay DLCI DCLIs Sangoma SDLA mrouted sync sec
13116 # LocalWords: Starmode Metricom MosquitoNet mosquitonet kbit nfsroot Digiboard
13117 # LocalWords: DIGI Xe Xeve digiboard UMISC touchscreens mtu ethernets HBAs MEX
13118 # LocalWords: Shifflett netcom js jshiffle WIC DECchip ELCP EtherPower dst RTC
13119 # LocalWords: rtc SMP lp Digi Intl RightSwitch DGRS dgrs AFFS Amiga UFS SDL AP
13120 # LocalWords: Solaris RISCom riscom syncPPP PCBIT pcbit sparc anu au artoo MFB
13121 # LocalWords: hitchcock Crynwr cnam pktdrvr NCSA's CyDROM CyCDROM FreeBSD NeXT
13122 # LocalWords: NeXTstep disklabel disklabels SMD FFS tm AmigaOS diskfiles Un IQ
13123 # LocalWords: Bernd informatik rwth aachen uae affs multihosting bytecode java
13124 # LocalWords: applets applet JDK ncsa cabi SNI Alphatronix readme LANs scarab
13125 # LocalWords: winsock RNIS caltech OSPF honour Honouring Mbit LocalTalk DEFRAG
13126 # LocalWords: localtalk download Packetwin Baycom baycom interwork ASCII JNT
13127 # LocalWords: Camtec proxying indyramp defragment defragmented UDP FAS FASXX
13128 # LocalWords: FastSCSI SIO FDC qlogicfas QLogic qlogicisp setbaycom ife ee LJ
13129 # LocalWords: ethz ch Travelmates ProAudioSpectrum ProAudio SoundMan SB SBPro
13130 # LocalWords: Thunderboard SM OPL FM ADLIB TSR Gravis MPU PSS ADI SW DSP codec
13131 # LocalWords: ADSP ESC ASIC daughtercard GUSMAX MSS NX AdLib Excell Ensoniq YM
13132 # LocalWords: SoundScape Spea MediaTriX AudioTriX WSS OTI ThunderBoard VoxWare
13133 # LocalWords: Soundscape SSCAPE TRIX MediaTrix PnP Maui dsp midixx EIA getty
13134 # LocalWords: mgetty sendfax gert greenie muc lowlevel Lasermate LanManager io
13135 # LocalWords: OOPSes trackball binghamton mobileip ncr IOMAPPED settags ns ser
13136 # LocalWords: setsync NEGO MPARITY autotuning prefetch PIIX cdwrite utils rc
13137 # LocalWords: PCWATCHDOG berkprod bitgate boldt ucsb jf kyoto jp euc Tetsuyasu
13138 # LocalWords: YAMADA tetsu cauchy nslab ntt nevod perm su doc kaf kheops wsc
13139 # LocalWords: traduc Bourgin dbourgin menuconfig kfill READMEs HOWTOs Virge WA
13140 # LocalWords: IDEDISK IDEFLOPPY EIDE firewalls QMAGIC ZMAGIC LocalWords opti
13141 # LocalWords: SVGATextMode vga svga Xkernel syr jmwobus comfaqs dhcp flakey GD
13142 # LocalWords: IPv IPng interoperability ipng ipv radio's tapr pkthome PLP nano
13143 # LocalWords: Ses Mhz sethdlc SOUNDMODEM WindowsSoundSystem smdiag pcf inka ES
13144 # LocalWords: smmixer ptt circ soundmodem MKISS FDDI DEFEA DEFPA DEFXX redhat
13145 # LocalWords: HyperNews khg mconv sed lina wuftpd MicroChannel netlink irc cum
13146 # LocalWords: raudio RealAudio PPROP NETBIOS GUI IBMMCA ELMC Racal Interlan fi
13147 # LocalWords: eth shapecfg src esp PCWD PREVSTAT bootparam sig bitwizard SBC
13148 # LocalWords: downloads AFSK TCM FP Karn KA FSK RUH LinkSys cron mouseman LLC
13149 # LocalWords: SyQuest SyQuest's CCITT MicroSolutions BPCD bpcd ESPSERIAL PROM
13150 # LocalWords: SUNESP openprom OPENPROMIO quango themall al TT MC MMU LC RMW AA
13151 # LocalWords: INSNS Ataris AutoConfig ZORRO OCS AMIFB Agnus Denise ECS CDTV GB
13152 # LocalWords: AGA Cybervision CYBER GSP TMS DMI Zorro ACSI ROMs SLM BioNet GVP
13153 # LocalWords: PAMsNet TekMagic Cyberstorm MkI CYBERSTORMII MkII BLZ onboard cx
13154 # LocalWords: Village Tronic ATARILANCE RieblCard PAMCard VME MFP sangoma LAPB
13155 # LocalWords: Rhotron BioData's Multiface AMIGAMOUSE COPCON Amiga's bitplanes
13156 # LocalWords: ATARIMOUSE MFPSER SCC's MegaSTE ESCC Atari's GVPIOEXT DMASOUND
13157 # LocalWords: fdutils cisco univercd rpcg htm iface lapb LAPBETHER tpqic qic
13158 # LocalWords: SYNTH xd en binfmt aout ipip terra ipx sd sr sg wic framebuffer
13159 # LocalWords: ibmmca lapbether mkiss dlci sdla fmv eepro eexpress ni hp ne es
13160 # LocalWords: ibmtr isofs ROMFS romfs pcxx cyclades istallion psaux msbusmouse
13161 # LocalWords: atixlmouse sbin softdog pcwd USS Lite ACI miroSOUND PCM miroPCM
13162 # LocalWords: microcontroller miro Voxware downloading teles acsi slm gvp ltpc
13163 # LocalWords: atari ariadne amigamouse atarimouse builtin IPDDP maths bradford
13164 # LocalWords: AppleTalk Farallon PhoneNet Zubkoff lnz SCCB HAPN WANs vesafb nt
13165 # LocalWords: wanrouter WANPIPE multiprotocol Mbps wanpipe EtherWORKS nodma SC
13166 # LocalWords: smp HiSax SiemensChipSet Siemens AVM Elsa ITK hisax PCC MICROR
13167 # LocalWords: Mircolink EURO DSS Spellcaster BRI sc spellcast Digiboards GPIO
13168 # LocalWords: SYMBIOS COMPAT SDMS rev ASUS Tekram HX VX API ibmmcascsi ASY asy
13169 # LocalWords: loader's PCnetPCI automounter AUTOFS amd autofs VT Gallant's Pnp
13170 # LocalWords: AEDSP aedsp enskip tik Sysctl sysctl PARPORT parport pnp IDs EPP
13171 # LocalWords: Autoprobe bart patrickr HDLS READBACK AB usr DAMA DS SparQ aten
13172 # LocalWords: Symbios PCscsi tmscsim RoamAbout GHz Hinds contrib mathematik ok
13173 # LocalWords: darmstadt okir DIGIEPCA International's Xem digiepca epca bootup
13174 # LocalWords: zorro CAPI AVMB capi avmb VP SYN syncookies EM em pc Ethertalk
13175 # LocalWords: Dayna DL Daynatalk LT PhoneNET ATB Daystar queueing CMDS SCBs ls
13176 # LocalWords: SCB STATS Thinnet ThunderLAN TLAN Netelligent NetFlex tlan james
13177 # LocalWords: caldera Preload Preloading slowdowns schoebel uni NBD nbd prog
13178 # LocalWords: stuttgart rdist TRANS hostnames mango jukeboxes ESS userland PD
13179 # LocalWords: hardlinked NAMETRANS env mtab fstab umount nologin runlevel gid
13180 # LocalWords: transname filespace adm Nodename hostname uname Kernelname bootp
13181 # LocalWords: KERNNAME kname ktype kernelname Kerneltype KERNTYPE Alt RX mdafb
13182 # LocalWords: dataless kerneltype SYSNAME Comtrol Rocketport palmtop fbset EGS
13183 # LocalWords: nvram SYSRQ SysRq PrintScreen sysrq NVRAMs NvRAM Shortwave RTTY
13184 # LocalWords: Sitor Amtor Pactor GTOR hayes TX TMOUT JFdocs HIGHMEM DAC IRQ's
13185 # LocalWords: IDEPCI IDEDMA idedma PDC pdc TRM trm raidtools luthien nuclecu
13186 # LocalWords: unam mx miguel koobera uic EMUL solaris pp ieee lpsg co DMAs TOS
13187 # LocalWords: BLDCONFIG preloading jumperless BOOTINIT modutils multipath GRE
13188 # LocalWords: misconfigured autoconfiguration IPGRE ICMP tracert ipautofw PIM
13189 # LocalWords: netis rlynch autofw ipportfw monmouth ipsubs portforwarding pimd
13190 # LocalWords: portfw PIMSM netweb usc pim pf EUI aggregatable PB decapsulate
13191 # LocalWords: ipddp Decapsulation DECAP bool HAMRADIO tcpdump af CDs tx FBCON
13192 # LocalWords: ethertap multisession PPC MMIO GDT GDTH ICP gdth hamradio bpp
13193 # LocalWords: lmh weejock AIMSlab RadioTrack RTRACK HZP OptoSCC TRX rx TRXECHO
13194 # LocalWords: DMASCC paccomm dmascc addr cfg oevsv oe kib picpar FDX baudrate
13195 # LocalWords: baudrates fdx HDX hdx PSK kanren frforum QoS SCHED CBQ SCH sched
13196 # LocalWords: sch cbq CSZ Shenker Zhang csz SFQ sfq TBF tbf PFIFO fifo PRIO RW
13197 # LocalWords: prio Micom xIO dwmw rimi OMIRR omirr omirrd unicode ntfs cmu NIC
13198 # LocalWords: Braam braam Schmidt's freiburg nls codepages codepage Romanian
13199 # LocalWords: Slovak Slovenian Sorbian Nordic iso Catalan Faeroese Galician SZ
13200 # LocalWords: Valencian Slovene Esperanto Estonian Latvian Byelorussian KOI mt
13201 # LocalWords: charset Inuit Greenlandic Sami Lappish koi SOFTCURSOR softcursor
13202 # LocalWords: Specialix specialix DTR RTS RTSCTS cycladesZ Exabyte ftape's inr
13203 # LocalWords: Iomega's LBFM claus ZFTAPE VFS zftape zft William's lzrw DFLT kb
13204 # LocalWords: MTSETBLK MTIOCTOP qft setblk zftape's tar's afio's setdrvbuffer
13205 # LocalWords: Procfs Exabyte's THR FCD sysvinit init PSC pscwdt VMIDI Euro SAB
13206 # LocalWords: Mostek Fastlane PowerMac PReP PMAC PowerPC Macintoshes Starmax
13207 # LocalWords: PowerStack Starmaxes MCOMMON DEVICETREE ATY IMS IMSTT videodev
13208 # LocalWords: BT Hauppauge STB bttv Quickcam BW BWQCAM bw qcam Mediavision PMS
13209 # LocalWords: pms Avatar Freecom Imation Superdisk BPCK bpck COMM comm DSTR ru
13210 # LocalWords: dstr EPAT EPEZ epat EPIA epia FreeCom FRPW frpw KingByte KBIC HW
13211 # LocalWords: KingByte's kbic OnSpec ValuStore FASTROUTE fastroute FLOWCONTROL
13212 # LocalWords: struct APIC realtime OSs LynxOS CNC tmp cvf HFS hfs ADFS Risc os
13213 # LocalWords: adfs ncpmount namespace SUBDIR reexport NDS kcore FT SPX spx DAT
13214 # LocalWords: interserver BLKSZ NUMBUFFERS apmd Tadpole ANA roestock QuickCam
13215 # LocalWords: isapnptools Colour CQCAM colour Connectix QuickClip prive mentre
13216 # LocalWords: KMOD kmod conformant utexas kharker UnixWare Mwave cgi cl ts ibm
13217 # LocalWords: eXchange threepio oakland simtel pre ULTRAMCA EtherLink isa luik
13218 # LocalWords: EtherLink OpenBSD pts DEVPTS devpts ptmx ttyp glibc readback SA
13219 # LocalWords: mwave OLDCARD isdnloop linklevel loopctrl Eicon Diehl DIEHLDIVA
13220 # LocalWords: ASUSCOM AsusCom TELEINT semiactiv Sedlbauer Sportster TA MIC ITH
13221 # LocalWords: NETjet NetJet Niccy Neuhaus sparcs AOC AOCD AOCE Microlink SAA
13222 # LocalWords: teletext WinTV saa iproute tc Quadra Performa PowerBook tor AUN
13223 # LocalWords: setserial compsoc steve Econet econet AUNUDP psched TEQL TLE CLS
13224 # LocalWords: teql FW Ingres TwistedPair MTRR MTRRs mtrr cfs crypto TD ktti KT
13225 # LocalWords: PHd ICS ipchains adelaide rustcorp syslog Cumana steganography
13226 # LocalWords: AcornSCSI EcoSCSI EESOX EESOXSCSI Powertec POWERTECSCSI dec SF
13227 # LocalWords: RadioReveal gatekeeper aimslab aztech FMI sf fmi RTL rtl cesdis
13228 # LocalWords: Yellowfin gsfc nasa gov yellowfin pcnet Mylex LNE lne EtherH hs
13229 # LocalWords: EBSA chattr RiscOS Winmodem AGP Atomwide DUALSP pcsp robinson CT
13230 # LocalWords: SGALAXY Waverider DSPxxx TRXPRO AudioTrix OSWF MOT CFB DSY kbps
13231 # LocalWords: tuwien kkudielk LVD mega lun MAXTAGS Gbps arcnet Olicom SKTR SNA
13232 # LocalWords: SysKonnect tms380tr sna etherboot ufs NetBEUI MultiSound MSNDCLAS GX
13233 # LocalWords: MSNDINIT MSNDPERM MSNDPIN PNDSPINI PNDSPERM Ensoniq's RetinaZ SS
13234 # LocalWords: AudioPCI lspci SonicVibes sonicvibes SPARCs roadrunner CLgen UPA
13235 # LocalWords: swansea shtml Zoltrix zoltrix BINUTILS EGCS binutils VIDC DACs
13236 # LocalWords: CyberVision Cirrus PowerBooks Topcat SBUS CGsix TurboGX BWtwo SS
13237 # LocalWords: CGthree TCX unswapable vfb fbcon hicolor truecolor AFB ILBM SOC
13238 # LocalWords: IPLAN gracilis Fibre SBus SparcSTORAGE SV jnewbigin swin QNX qnx
13239 # LocalWords: PTY PTYS ptyxx ttyxx PTYs ssh sb Avance ALS pss pvv kerneli hd
13240 # LocalWords: synth WaveFront MSND NONPNP AudioExcelDSP STRAM APUS CHRP MBX Nx
13241 # LocalWords: PowerMac's BMAC radiotrack rtrack miropcm OFFBOARD HPT UDMA DVD
13242 # LocalWords: hpt fokus gmd Cyrix DXL SLC DLC NexGen MediaGX GXm IDT WinChip
13243 # LocalWords: MMX MII valkyrie mdacon vdolive VDOLive cuseeme CU hippi rrunner
13244 # LocalWords: SeeMe ipmasqadm juanjox ipmarkfw markfw TNCs Microdyne rhine lib
13245 # LocalWords: libc jsX gamepad gameport CHF FCS FPGaming MadCatz ASSASIN GrIP
13246 # LocalWords: Assasin gamepads GamePad PDPI gamecards gamecard WingMan BSP WCS
13247 # LocalWords: ThunderPad CyberMan SideWinder ThrustMaster DirectConnect NES XF
13248 # LocalWords: Millenium SNES PSX Multisystem Nintendo PlayStation Amstrad CPC
13249 # LocalWords: Sega TurboGraFX Steffen Schwenke Multiststem PDIF FIFOSIZE EPLUS
13250 # LocalWords: PowerUP RoadRunner tahallah dos functionkey setterm imladris Woz
13251 # LocalWords: PowerMacs Winbond Algorithmics ALGOR algor ECOFF IRIX SGI SGI's
13252 # LocalWords: gfx virtualized Xpmac mklinux XFree FBDev Woodhouse mvhi Seeq fp
13253 # LocalWords: SGISEEQ HIgh ADB ADBMOUSE crosscompiler CROSSCOMPILE FPE GDB gdb
13254 # LocalWords: JOYPORT rp spoofing DawiControl NOGENSUPP EEPROM HSSI Alessandro
13255 # LocalWords: singleprocessor tex MATHEMU FRIQ Maxell friq Alcor XLT AlphaBook
13256 # LocalWords: AlphaPCI DP LX Miata Mikasa Noritake RPX UX BX Takara EV PRIMO
13257 # LocalWords: TSC Matrox Productiva matroxfb matrox multihead ia linuxhq MFW
13258 # LocalWords: mfw AAA MCS Initio XXU initio imm AutoDetect IZIP CTR usec HDLC
13259 # LocalWords: COSA SRP muni cz kas cosa Alteon AceNIC acenic VTOC OSes GMT SAx
13260 # LocalWords: Inspiron localtime INTS Thinkpads Ralf Brown's Flightstick NNN
13261 # LocalWords: Xterminator Blackhawk NN mpu ioports DCA HPDCA HPLANCE DIO Corel
13262 # LocalWords: GemTek gemtek CMDLINE IrDA PDA's irmanager irattach RR AVA DN rg
13263 # LocalWords: uit dagb irda LSAP IrLMP RR's IrLAP IR alloc skb's kfree skb's
13264 # LocalWords: GZIP IrLAN NetbeamIR ESI JetEye IrOBEX IrCOMM TTY's minicom dti
13265 # LocalWords: ircomm ircomm pluto thiguchi IrTTY Linux's bps NetWinder MIR NSC
13266 # LocalWords: ACTiSYS Dongle dongle dongles esi actisys IrMate tekram BVM MVME
13267 # LocalWords: BVME BVME WRITETHROUGH copyback writethrough fwmark syncookie tu
13268 # LocalWords: alphalinux GOBIOS csn chemnitz nat ACARD AMI MegaRAID megaraid
13269 # LocalWords: QNXFS ISI isicom xterms Apollos VPN RCPCI rcpci sgi visws pcmcia
13270 # LocalWords: IrLPT UIRCC Tecra Strebel jstrebel suse Eichwalder ke INI INIA
13271 # LocalWords: FCP qlogicfc sym isapnp DTLK DoubleTalk rcsys dtlk DMAP SGIVW ar
13272 # LocalWords: dmabuf EcoRadio MUTEFREQ GIrBIL girbil tepkom vol mha diplom PQS
13273 # LocalWords: bmac Microgate SyncLink synclink hdlc excl ioaddr Tane tanep TCQ
13274 # LocalWords: PDS SMALLDOS charsets bigfoot kernelfr mcs cls fw rsvp SKnet sk
13275 # LocalWords: SKMC USB UHCI OHCI intel compaq usb ohci HCD Virt Compaq's hcd
13276 # LocalWords: VROOTHUB KBD ARRs MCRs NWBUTTON nwbutton NUM WaveArtist APNE cpu
13277 # LocalWords: apne blackhawke PlanB lu mlan planb NWFPE FPA nwfpe unbootable
13278 # LocalWords: FPEmulator ds vmlinux initialisation discardable pgtable PGT mdw
13279 # LocalWords: quicklist pagetable arthur StrongARM podule podules Autodetect
13280 # LocalWords: dodgy IrPORT irport Litelink litelink SuSE rtfm internet hda CY
13281 # LocalWords: multmode DriveReady SeekComplete DriveStatusError miscompile AEC
13282 # LocalWords: mainboard's Digital's alim FastTrak aec PIIXn piix Gayle Eyetech
13283 # LocalWords: Catweasel IDEDOUBLER Powerbook Centris ICSIDE RapIDE OSM HDM IOP
13284 # LocalWords: HDM's OSM's lan FibreChannel ECP autoprobe itg lbl ipmasq cjb IC
13285 # LocalWords: bieringer Caulfield's dreamtime decnet SIOCFIGCONF SIOCGIFCONF
13286 # LocalWords: rtnetlink Endnode Aironet Arlan Telxon ylenurme arlan ACB aeschi
13287 # LocalWords: Sealevel sealevel Cyclom br wanconfig tarball conectiva cycsyn
13288 # LocalWords: devel bazar cyclomx NetGear GA IBMOL Lanstreamer uhci eu efs CYZ
13289 # LocalWords: olympic linuxtr usbcore acm EZUSB downloader EFS XFS INTR op IIC
13290 # LocalWords: heine soundcore JavaStations JavaStation GemTeks TerraTec TODO
13291 # LocalWords: ActiveRadio Standalone terratec Rolf Offermanns rolf offermanns
13292 # LocalWords: Zoran ZR Buz LML CPQ DA cpqarray PPDEV deviceid vlp ppdev atyfb
13293 # LocalWords: AcceleRAID eXtremeRAID NETFILTER Netfilter masqueraded netfilter
13294 # LocalWords: kernelnotes Cardbus PCMCIA's CardBus clgenfb Permedia YAM MMAP
13295 # LocalWords: mmapped ATM atm PVCs SVCs InARP ATMARP neighbour neighbours MPOA
13296 # LocalWords: VCs ENI FPGA Tonga MMF MF UTP printks ZeitNet ZN ZATM uPD SAR PN
13297 # LocalWords: approx NICStAR NICs ForeRunnerLE Madge Collage ATMizer Dxxxx VCI
13298 # LocalWords: ServeRAID IPS ips ipslinux gzip BSDCOMP LZW RAYCS Interphase app
13299 # LocalWords: Tachyon IPHASE Surfboard NextLevel SURFboard jacksonville Tigon
13300 # LocalWords: fventuri adelphia siglercm linuxpower AceNICs Starfire starfire
13301 # LocalWords: ISOC CPiA cpia uss ACPI UDF DirectCD udf CDRW's OSF Manx acpi
13302 # LocalWords: Unixware cymru Computone IntelliPort Intelliport computone SI sx
13303 # LocalWords: adbmouse DRI DRM dlabs GMX PLCs Applicom fieldbus applicom int
13304 # LocalWords: VWSND eg ESSSOLO CFU CFNR scribed eiconctrl eicon hylafax KFPU
13305 # LocalWords: EXTRAPREC fpu mainboards KHTTPD kHTTPd khttpd Xcelerator
13306 # LocalWords: LOGIBUSMOUSE