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://www.linuxdoc.org/docs.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 APIC and IO-APIC Support on Uniprocessors
123 This option enables uniprocessor-kernels to switch into IO-APIC mode
124 if there is an IO-APIC in the system. Such a kernel will still boot
125 on IO-APIC-less systems with no slowdown at all. SMP kernels include
126 IO-APIC support unconditionally.
128 Kernel math emulation
129 CONFIG_MATH_EMULATION
130 Linux can emulate a math coprocessor (used for floating point
131 operations) if you don't have one. 486DX and Pentium processors have
132 a math coprocessor built in, 486SX and 386 do not, unless you added
133 a 487DX or 387, respectively. (The messages during boot time can
134 give you some hints here ["man dmesg"].) Everyone needs either a
135 coprocessor or this emulation.
137 If you don't have a math coprocessor, you need to say Y here; if you
138 say Y here even though you have a coprocessor, the coprocessor will
139 be used nevertheless. (This behavior can be changed with the kernel
140 command line option "no387", which comes handy if your coprocessor
141 is broken. Try "man bootparam" or see the documentation of your boot
142 loader (lilo or loadlin) about how to pass options to the kernel at
143 boot time. The lilo procedure is also explained in the SCSI-HOWTO,
144 available from http://www.linuxdoc.org/docs.html#howto .) This
145 means that it is a good idea to say Y here if you intend to use this
146 kernel on different machines.
148 More information about the internals of the Linux math coprocessor
149 emulation can be found in arch/i386/math-emu/README.
151 If you are not sure, say Y; apart from resulting in a 66 KB bigger
152 kernel, it won't hurt.
154 Timer and CPU usage LEDs
156 If you say Y here, the LEDs on your machine will be used
157 to provide useful information about your current system status.
159 If you are compiling a kernel for a NetWinder or EBSA-285, you will
160 be able to select which LEDs are active using the options below. If
161 you are compiling a kernel for the EBSA-110 however, the red LED
162 will simply flash regularly to indicate that the system is still
163 functional. It is safe to say Y here if you have a CATS system, but
164 the driver will do nothing.
168 If you say Y here, one of the system LEDs (the green one on the
169 NetWinder or the amber one on the EBSA285) will flash regularly to
170 indicate that the system is still operational. This is mainly
171 useful to kernel hackers who are debugging unstable kernels.
175 If you say Y here, the red LED will be used to give a good real
176 time indication of CPU usage, by lighting whenever the idle task
177 is not currently executing.
179 Kernel FP software completion (EXPERIMENTAL)
181 This option is required for IEEE compliant floating point arithmetic
182 on the Alpha. The only time you would ever not say Y is to say M in
183 order to debug the code. Say Y unless you know what you are doing.
187 If you are compiling a kernel which will never run on a machine
188 with more than 1 Gigabyte total physical RAM, answer "off"
189 here (default choice).
191 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
192 High memory is all the physical RAM that could not be directly
193 mapped by the kernel - ie. 3GB if there is 4GB RAM in the system,
194 7GB if there is 8GB RAM in the system.
196 If 4 Gigabytes physical RAM or less is used then answer "4GB" here.
198 If more than 4 Gigabytes is used then answer "64GB" here. This
199 selection turns Intel PAE (Physical Address Extension) mode on.
200 PAE implements 3-level paging on IA32 processors. PAE is fully
201 supported by Linux, PAE mode is implemented on all recent Intel
202 processors (PPro and better). NOTE: The "64GB" kernel will not
203 boot CPUs that not support PAE!
205 Normal PC floppy disk support
207 If you want to use the floppy disk drive(s) of your PC under Linux,
208 say Y. Information about this driver, especially important for IBM
209 Thinkpad users, is contained in drivers/block/README.fd. This file
210 also contains the location of the Floppy driver FAQ as well as
211 location of the fdutils package used to configure additional
212 parameters of the driver at run time.
214 This driver is also available as a module ( = code which can be
215 inserted in and removed from the running kernel whenever you want).
216 The module will be called floppy.o. If you want to compile it as a
217 module, say M here and read Documentation/modules.txt.
219 Support for PowerMac floppy
221 If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
222 floppy controller, say Y here. Most commonly found in PowerMacs.
226 Saying Y here will allow you to use a portion of your RAM memory as
227 a block device, so that you can make filesystems on it, read and
228 write to it and do all the other things that you can do with normal
229 block devices (such as hard drives). It is usually used to load and
230 store a copy of a minimal root file system off of a floppy into RAM
231 during the initial install of Linux.
233 Note that the kernel command line option "ramdisk=XX" is now
234 obsolete. For details, read Documentation/ramdisk.txt.
236 If you want to compile this as a module ( = code which can be
237 inserted in and removed from the running kernel whenever you want),
238 say M and read Documentation/modules.txt. The module will be called
241 Most normal users won't need the RAM disk functionality, and can
244 Initial RAM disk (initrd) support
245 CONFIG_BLK_DEV_INITRD
246 The initial RAM disk is a RAM disk that is loaded by the boot loader
247 (loadlin or lilo) and that is mounted as root before the normal boot
248 procedure. It is typically used to load modules needed to mount the
249 "real" root file system, etc. See Documentation/initrd.txt for
254 Saying Y here will allow you to use a regular file as a block
255 device; you can then create a file system on that block device and
256 mount it just as you would mount other block devices such as hard
257 drive partitions, CDROM drives or floppy drives.
259 This is useful if you want to check an ISO 9660 file system before
260 burning the CD, or if you want to use floppy images without first
261 writing them to floppy.
263 The loop device driver can also be used to "hide" a filesystem in a
264 disk partition, floppy, or regular file, either using encryption
265 (scrambling the data) or steganography (hiding the data in the low
266 bits of, say, a sound file). This is also safe if the file resides
267 on a remote file server. If you want to do this, you will first have
268 to acquire and install a kernel patch from
269 ftp://ftp.replay.com/pub/crypto/linux/all or
270 ftp://verden.pvv.org/pub/linux/kerneli/v2.1/ , and then you need to
271 say Y to this option.
273 Note that alternative ways to use encrypted filesystems are provided
274 by the cfs package, which can be gotten from
275 ftp://ftp.replay.com/pub/crypto/disk/ , and the newer tcfs package,
276 available at http://tcfs.dia.unisa.it/ . You do not need to say Y
277 here if you want to use one of these. However, using cfs requires
278 saying Y to "NFS filesystem support" below while using tcfs requires
279 applying a kernel patch.
281 To use the loop device, you need the losetup utility and a recent
282 version of the mount program, both contained in the util-linux
283 package. The location and current version number of util-linux is
284 contained in the file Documentation/Changes.
286 Note that this loop device has nothing to do with the loopback
287 device used for network connections from the machine to itself.
289 If you want to compile this driver as a module ( = code which can be
290 inserted in and removed from the running kernel whenever you want),
291 say M here and read Documentation/modules.txt. The module will be
294 Most users will answer N here.
296 Network Block Device support
298 Saying Y here will allow your computer to be a client for network
299 block devices, i.e. it will be able to use block devices exported by
300 servers (mount filesystems on them etc.). Communication between
301 client and server works over TCP/IP networking, but to the client
302 program this is hidden: it looks like a regular local file access to
303 a block device special file such as /dev/nd0.
305 Network block devices also allows you to run a block-device in
306 userland (making server and client physically the same computer,
307 communicating using the loopback network device).
309 Read Documentation/nbd.txt for more information, especially about
310 where to find the server code, which runs in user space and does not
311 need special kernel support.
313 Note that this has nothing to do with the network file systems NFS
314 or Coda; you can say N here even if you intend to use NFS or Coda.
316 If you want to compile this driver as a module ( = code which can be
317 inserted in and removed from the running kernel whenever you want),
318 say M here and read Documentation/modules.txt. The module will be
323 Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
325 If you say Y here, you will use the full-featured IDE driver to
326 control up to eight IDE interfaces, each being able to serve a
327 "master" and a "slave" device, for a total of up to sixteen IDE
328 disk/cdrom/tape/floppy drives. People with SCSI-only systems
331 Useful information about large (>540 MB) IDE disks, multiple
332 interfaces, what to do if IDE devices are not automatically
333 detected, sound card IDE ports, module support, and other topics, is
334 contained in Documentation/ide.txt. For detailed information about
335 hard drives, consult the Disk-HOWTO and the Multi-Disk-HOWTO,
336 available from http://www.linuxdoc.org/docs.html#howto .
338 To fine-tune IDE drive/interface parameters for improved
339 performance, look for the hdparm package at
340 ftp://metalab.unc.edu/pub/Linux/kernel/patches/diskdrives/ .
342 If you want to compile this driver as a module ( = code which can be
343 inserted in and removed from the running kernel whenever you want),
344 say M here and read Documentation/modules.txt and
345 Documentation/ide.txt. The module will be called ide.o. Do not
346 compile this driver as a module if your root filesystem (the one
347 containing the directory /) is located on an IDE device.
349 If you have one or more IDE drives, say Y or M here. If your system
350 has no IDE drives, or if memory requirements are really tight, you
351 could say N here, and select the "Old hard disk driver" below
352 instead to save about 13 KB of memory in the kernel.
354 Old hard disk (MFM/RLL/IDE) driver
355 CONFIG_BLK_DEV_HD_ONLY
356 There are two drivers for MFM/RLL/IDE hard disks. Most people use
357 the newer enhanced driver, but this old one is still around for two
358 reasons. Some older systems have strange timing problems and seem to
359 work only with the old driver (which itself does not work with some
360 newer systems). The other reason is that the old driver is smaller,
361 since it lacks the enhanced functionality of the new one. This makes
362 it a good choice for systems with very tight memory restrictions, or
363 for systems with only older MFM/RLL/ESDI drives. Choosing the old
364 driver can save 13 KB or so of kernel memory.
366 If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
367 instead of this one. For more detailed information, read the
368 Disk-HOWTO, available from
369 http://www.linuxdoc.org/docs.html#howto .
371 People with SCSI-only systems can say N here.
373 Use old disk-only driver on primary interface
374 CONFIG_BLK_DEV_HD_IDE
375 There are two drivers for MFM/RLL/IDE disks. Most people use just
376 the new enhanced driver by itself. This option however installs the
377 old hard disk driver to control the primary IDE/disk interface in
378 the system, leaving the new enhanced IDE driver to take care of only
379 the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from
380 having an IDE/ATAPI CDROM or tape drive connected to the primary IDE
381 interface. Choosing this option may be useful for older systems
382 which have MFM/RLL/ESDI controller+drives at the primary port
383 address (0x1f0), along with IDE drives at the secondary/3rd/4th port
386 Normally, just say N here; you will then use the new driver for all
389 People with SCSI-only systems don't need this and can say N here as
392 Include IDE/ATA-2 DISK support
393 CONFIG_BLK_DEV_IDEDISK
394 This will include enhanced support for MFM/RLL/IDE hard disks. If
395 you have a MFM/RLL/IDE disk, and there is no special reason to use
396 the old hard disk driver instead, say Y. If you have an SCSI-only
397 system, you can say N here.
399 If you want to compile this driver as a module ( = code which can be
400 inserted in and removed from the running kernel whenever you want),
401 say M here and read Documentation/modules.txt. The module will be
402 called ide-disk.o. Do not compile this driver as a module if your
403 root filesystem (the one containing the directory /) is located on
404 the IDE disk. If unsure, say Y.
406 Use multi-mode by default
407 CONFIG_IDEDISK_MULTI_MODE
408 If you get this error, try to say Y here:
410 hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
411 hda: set_multmode: error=0x04 { DriveStatusError }
415 Include IDE/ATAPI CDROM support
417 If you have a CDROM drive using the ATAPI protocol, say Y. ATAPI is
418 a newer protocol used by IDE CDROM and TAPE drives, similar to the
419 SCSI protocol. Most new CDROM drives use ATAPI, including the
420 NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
421 double(2X) or better speed drives.
423 If you say Y here, the CDROM drive will be identified at boot time
424 along with other IDE devices, as "hdb" or "hdc", or something
425 similar (check the boot messages with dmesg). If this is your only
426 CDROM drive, you can say N to all other CDROM options, but be sure
427 to say Y or M to "ISO 9660 CDROM filesystem support".
429 Read the CDROM-HOWTO, available from
430 http://www.linuxdoc.org/docs.html#howto and the file
431 Documentation/cdrom/ide-cd. Note that older versions of lilo (the
432 Linux boot loader) cannot properly deal with IDE/ATAPI CDROMs, so
433 install lilo-16 or higher, available from
434 ftp://metalab.unc.edu/pub/Linux/system/boot/lilo .
436 If you want to compile the driver as a module ( = code which can be
437 inserted in and removed from the running kernel whenever you want),
438 say M here and read Documentation/modules.txt. The module will be
441 Include IDE/ATAPI TAPE support
442 CONFIG_BLK_DEV_IDETAPE
443 If you have an IDE tape drive using the ATAPI protocol, say Y.
444 ATAPI is a newer protocol used by IDE tape and CDROM drives, similar
445 to the SCSI protocol. If you have an SCSI tape drive however, you
448 This now includes the OnStream DI-30 tape drive support.
449 Will not work with SCSI protocol, until there is support for the
450 SC-30 and SC-50 versions.
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 Must pass "hdx=scsi" per devices if you want the native EIDE sub-drivers
491 to skip over the native support. This is required for use of CD-RW's.
493 This is useful if you have an ATAPI device for which no native
494 driver has been written (for example, an ATAPI PD-CD or CDR drive);
495 you can then use this emulation together with an appropriate SCSI
496 device driver. In order to do this, say Y here and to "SCSI support"
497 and "SCSI generic support", below.
499 Note that this option does NOT allow you to attach SCSI devices to a
500 box that doesn't have a SCSI host adapter installed.
502 If both this SCSI emulation and native ATAPI support are compiled
503 into the kernel, the native support will be used.
505 People with SCSI-only systems can say N here. If unsure, say N.
508 CONFIG_BLK_DEV_ISAPNP
509 If you have an ISA EIDE card that is PnP and requires setup first
510 before scanning for devices, say Y here.
514 CMD640 chipset bugfix/support
515 CONFIG_BLK_DEV_CMD640
516 The CMD-Technologies CMD640 IDE chip is used on many common 486 and
517 Pentium motherboards, usually in combination with a "Neptune" or
518 "SiS" chipset. Unfortunately, it has a number of rather nasty
519 design flaws that can cause severe data corruption under many common
520 conditions. Say Y here to include code which tries to automatically
521 detect and correct the problems under Linux. This option also
522 enables access to the secondary IDE ports in some CMD640 based
525 This driver will work automatically in PCI based systems (most new
526 systems have PCI slots). But if your system uses VESA local bus
527 (VLB) instead of PCI, you must also supply a kernel boot parameter
528 to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man
529 bootparam" or see the documentation of your boot loader about how to
530 pass options to the kernel. The lilo procedure is also explained in
531 the SCSI-HOWTO, available from
532 http://www.linuxdoc.org/docs.html#howto .)
534 The CMD640 chip is also used on add-in cards by Acculogic, and on
535 the "CSA-6400E PCI to IDE controller" that some people have. For
536 details, read Documentation/ide.txt.
538 People with SCSI-only systems should say N here. If unsure, say Y.
540 CMD640 enhanced support
541 CONFIG_BLK_DEV_CMD640_ENHANCED
542 This option includes support for setting/autotuning PIO modes and
543 prefetch on CMD640 IDE interfaces. For details, read
544 Documentation/ide.txt. If you have a CMD640 IDE interface and your
545 BIOS does not already do this for you, then say Y here. Otherwise
548 RZ1000 chipset bugfix/support
549 CONFIG_BLK_DEV_RZ1000
550 The PC-Technologies RZ1000 IDE chip is used on many common 486 and
551 Pentium motherboards, usually along with the "Neptune" chipset.
552 Unfortunately, it has a rather nasty design flaw that can cause
553 severe data corruption under many conditions. Say Y here to include
554 code which automatically detects and corrects the problem under
555 Linux. This may slow disk throughput by a few percent, but at least
556 things will operate 100% reliably.
558 People with SCSI-only systems should say N here. If unsure, say Y.
560 Cyrix CS5530 MediaGX chipset support
561 CONFIG_BLK_DEV_CS5530
562 Include support for UDMA on the Cyrix MediaGX 5530 chipset. This
563 will automatically be detected and configured if found.
565 It is safe to say Y to this question.
567 Generic PCI IDE chipset support
568 CONFIG_BLK_DEV_IDEPCI
569 Say Y here for PCI systems which use IDE drive(s).
570 This option helps the IDE driver to automatically detect and
571 configure all PCI-based IDE interfaces in your system.
573 People with SCSI-only systems should say N here; if unsure say Y.
575 Generic PCI bus-master DMA support
576 CONFIG_BLK_DEV_IDEDMA_PCI
577 If your PCI system uses IDE drive(s) (as opposed to SCSI, say) and
578 is capable of bus-master DMA operation (most Pentium PCI systems),
579 you will want to say Y here to reduce CPU overhead. You can then use
580 the "hdparm" utility to enable DMA for drives for which it was not
581 enabled automatically. By default, DMA is not enabled automatically
582 for these drives, but you can change that by saying Y to the
583 following question "Use DMA by default when available". You can get
584 the latest version of the hdparm utility from
585 ftp://metalab.unc.edu/pub/Linux/system/hardware/ .
587 Read the comments at the beginning of drivers/block/idedma.c and the
588 file Documentation/ide.txt for more information.
590 It is safe to say Y to this question.
592 Good-Bad DMA Model-Firmware (EXPERIMENTAL)
593 CONFIG_IDEDMA_NEW_DRIVE_LISTINGS
594 If you say Y here, the model and firmware revision of your drive
595 will be compared against a blacklist of buggy drives that claim to
596 be (U)DMA capable but aren't. This is a blanket on/off test with no
599 Straight GNU GCC 2.7.3/2.8.X compilers are known to be safe;
600 whereas, many versions of EGCS have a problem and miscompile if you
605 Boot off-board chipsets first support
606 CONFIG_BLK_DEV_OFFBOARD
607 Normally, IDE controllers built into the motherboard (on-board
608 controllers) are assigned to ide0 and ide1 while those on add-in PCI
609 cards (off-board controllers) are relegated to ide2 and ide3.
610 Answering Y here will allow you to reverse the situation, with
611 off-board controllers on ide0/1 and on-board controllers on ide2/3.
612 This can improve the usability of some boot managers such as LILO
613 when booting from a drive on an off-board controller.
615 If you say Y here, and you actually want to reverse the device scan
616 order as explained above, you also need to issue the kernel command
617 line option "pci=reverse". (Try "man bootparam" or see the
618 documentation of your boot loader (lilo or loadlin) about how to
619 pass options to the kernel at boot time. The lilo procedure is also
620 explained in the SCSI-HOWTO, available from
621 http://www.linuxdoc.org/docs.html#howto .)
623 Note that, if you do this, the order of the hd* devices will be
624 rearranged which may require modification of fstab and other files.
628 Use DMA by default when available
629 CONFIG_IDEDMA_PCI_AUTO
630 Prior to kernel version 2.1.112, Linux used to automatically use
631 DMA for IDE drives and chipsets which support it. Due to concerns
632 about a couple of cases where buggy hardware may have caused damage,
633 the default is now to NOT use DMA automatically. To revert to the
634 previous behaviour, say Y to this question.
636 If you suspect your hardware is at all flakey, say N here.
637 Do NOT email the IDE kernel people regarding this issue!
639 It is normally safe to answer Y to this question unless your
640 motherboard uses a VIA VP2 chipset, in which case you should say N.
642 AEC6210 chipset support
643 CONFIG_BLK_DEV_AEC6210
644 This driver adds up to 4 more EIDE devices sharing a single
645 interrupt. This add-on card is a bootable PCI UDMA controller. In
646 order to get this card to initialize correctly in some cases, you
647 should say Y here, and preferably also to "Use DMA by default when
650 Please read the comments at the top of drivers/block/aec6210.c
652 ALI M15x3 chipset support
653 CONFIG_BLK_DEV_ALI15X3
654 This driver ensures (U)DMA support for ALI 1543 and 1543C,
655 1535, 1535D onboard chipsets. It also tests for Simplex mode and
656 enables normal dual channel support.
658 If you say Y here, you also need to say Y to "Use DMA by default
659 when available", above.
660 Please read the comments at the top of drivers/block/alim15x3.c
664 AMD7409 chipset support (EXPERIMENTAL)
665 CONFIG_BLK_DEV_AMD7409
666 This driver ensures (U)DMA support for AMD756 Viper chipset.
668 If you say Y here, you also need to say Y to "Use DMA by default
669 when available", above.
670 Please read the comments at the top of drivers/block/amd7409.c
674 CMD64X chipset support
675 CONFIG_BLK_DEV_CMD64X
676 Say Y here if you have an IDE controller which uses any of these chipsets,
677 CMD643, CMD646, or CMD648.
679 CMD64X chipset RAID support (EXPERIMENTAL) (WIP)
680 CONFIG_BLK_DEV_CMD64X
681 Work in progress for hardware raid ata-33/66..........rev 7 minimum.
684 CY82C693 chipset support (EXPERIMENTAL)
685 CONFIG_BLK_DEV_CY82C693
686 This driver adds detection and support for the CY82C693 chipset
687 used on Digital's PC-Alpha 164SX boards.
689 If you say Y here, you need to say Y to "Use DMA by default
690 when available" as well.
692 HPT34X chipset support
693 CONFIG_BLK_DEV_HPT34X
694 This driver adds up to 4 more EIDE devices sharing a single
695 interrupt. The HPT343 chipset in its current form is a non-bootable
696 controller; the HPT345/HPT363 chipset is a bootable (needs BIOS FIX)
697 PCI UDMA controllers. This driver requires dynamic tuning of the
698 chipset during the ide-probe at boot time. It is reported to support
699 DVD II drives, by the manufacturer.
701 HPT34X DMA support (EXPERIMENTAL)
702 CONFIG_BLK_DEV_HPT34X_DMA
703 you need to say Y to "Use DMA by default when available" if you say
706 Please read the comments at the top of drivers/block/hpt34x.c
708 HPT366 chipset support
709 CONFIG_BLK_DEV_HPT366
710 This is an Ultra DMA chipset for ATA-66.
712 This driver adds up to 4 more EIDE devices sharing a single
713 interrupt. The HPT366 chipset in its current form is a non-bootable.
714 This driver requires dynamic tuning of the chipset during the
715 ide-probe at boot. It is reported to support DVD II drives, by the
718 Please read the comments at the top of drivers/block/hpt366.c
720 HPT366 Fast Interrupt support (EXPERIMENTAL) (WIP)
721 CONFIG_HPT366_FAST_IRQ_PREDICTION
725 HPT366 mode three unsupported (EXPERIMENTAL) (WIP)
727 This is an undocumented mode that the HA366 can default to in many cases.
730 NS87415 support (EXPERIMENTAL)
731 CONFIG_BLK_DEV_NS87415
732 This driver adds detection and support for the NS87415 chip
733 (used in SPARC64, among others).
735 Please read the comments at the top of drivers/block/ns87415.c.
737 OPTi 82C621 enhanced support (EXPERIMENTAL)
738 CONFIG_BLK_DEV_OPTI621
739 This is a driver for the OPTi 82C621 EIDE controller.
740 Please read the comments at the top of drivers/block/opti621.c.
742 Intel PIIXn chipsets support
744 This driver adds PIO mode setting and tuning for all PIIX IDE
745 controllers by Intel. Since the BIOS can sometimes improperly tune
746 PIO 0-4 mode settings, this allows dynamic tuning of the chipset
747 via the standard end-user tool 'hdparm'.
749 Please read the comments at the top of drivers/block/piix.c
751 Should also include "PIIXn Tuning support" CONFIG_BLK_DEV_PIIX_TUNING
755 CONFIG_BLK_DEV_PIIX_TUNING
756 This driver extension adds DMA mode setting and tuning for all PIIX
757 IDE controllers by Intel. Since the BIOS can sometimes improperly
758 set up the device/adapter combination and speed limits, it has
759 become a necessity to back/forward speed devices as needed.
761 Case 430HX/440FX PIIX3 need speed limits to reduce UDMA to DMA mode
762 2 if the BIOS can not perform this task at initialization.
766 PROMISE PDC20246/PDC20262 support
767 CONFIG_BLK_DEV_PDC202XX
768 Promise Ultra33 or PDC20246
770 This driver adds up to 4 more EIDE devices sharing a single
771 interrupt. This add-on card is a bootable PCI UDMA controller. Since
772 multiple cards can be installed and there are BIOS ROM problems that
773 happen if the BIOS revisions of all installed cards (three-max) do
774 not match, the driver attempts to do dynamic tuning of the chipset at
775 boot-time for max-speed. Ultra33 BIOS 1.25 or newer is required for
776 more than one card. This card may require that you say Y to "Special
777 UDMA Feature (EXPERIMENTAL)".
779 Promise Ultra66 or PDC20262
781 This driver adds up to 4 more EIDE devices sharing a single
782 interrupt. This add-on card is a bootable PCI UDMA ATA-66
783 controller. The driver attempts to dynamic tuning of the chipset at
784 boot-time for max-speed. Note tested limits are UDMA-2. Ultra66 BIOS
785 1.11 or newer required.
787 If you say Y here, you need to say Y to "Use DMA by default when
790 Please read the comments at the top of drivers/block/pdc202xx.c
795 CONFIG_PDC202XX_FORCE_BURST_BIT
796 For PDC20246 and PDC20262 Ultra DMA chipsets. Designed originally
797 for PDC20246/Ultra33 that has BIOS setup failures when using 3 or
800 Please read the comments at the top of drivers/block/pdc202xx.c
804 Special Mode Feature (EXPERIMENTAL)
805 CONFIG_PDC202XX_FORCE_MASTER_MODE
806 For PDC20246 and PDC20262 Ultra DMA chipsets. This is reserved for
807 possible Hardware RAID 0,1 for the FastTrak Series.
811 Winbond SL82c105 support
812 CONFIG_BLK_DEV_SL82C105
813 If you have a Winbond SL82c105 IDE controller, say Y here to enable
814 special configuration for this chip. This is common on various CHRP
815 motherboards, but could be used elsewhere. If in doubt, say Y.
817 Tekram TRM290 chipset support (EXPERIMENTAL)
818 CONFIG_BLK_DEV_TRM290
819 This driver adds support for bus master DMA transfers
820 using the Tekram TRM290 PCI IDE chip. Volunteers are
821 needed for further tweaking and development.
822 Please read the comments at the top of drivers/block/trm290.c.
824 VIA82CXXX chipset support (EXPERIMENTAL)
825 CONFIG_BLK_DEV_VIA82CXXX
826 This allows you to to configure your chipset for a better use while
827 running (U)DMA: it will allow you to enable efficiently the second
828 channel dma usage, as it is may not be set by BIOS. It allows you to
829 run a kernel command line at boot time in order to set fifo config.
830 If no command line is provided, it will try to set fifo configuration
831 at its best. It will allow you to get a proc/ide/via display
832 (while running a "cat") provided you enabled "proc" support.
833 Please read the comments at the top of drivers/block/via82cxxx.c
835 If you say Y here, you also need to say Y to "Use DMA by default
836 when available", above.
840 Other IDE chipset support
842 Say Y here if you want to include enhanced support for various IDE
843 interface chipsets used on motherboards and add-on cards. You can
844 then pick your particular IDE chip from among the following options.
845 This enhanced support may be necessary for Linux to be able to
846 access the 3rd/4th drives in some systems. It may also enable
847 setting of higher speed I/O rates to improve system performance with
848 these chipsets. Most of these also require special kernel boot
849 parameters to actually turn on the support at runtime; you can find
850 a list of these in the file Documentation/ide.txt.
852 People with SCSI-only systems can say N here.
854 Generic 4 drives/port support
855 CONFIG_BLK_DEV_4DRIVES
856 Certain older chipsets, including the Tekram 690CD, use a single set
857 of I/O ports at 0x1f0 to control up to four drives, instead of the
858 customary two drives per port. Support for this can be enabled at
859 runtime using the "ide0=four" kernel boot parameter if you say Y
863 CONFIG_BLK_DEV_ALI14XX
864 This driver is enabled at runtime using the "ide0=ali14xx" kernel
865 boot parameter. It enables support for the secondary IDE interface
866 of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
867 I/O speeds to be set as well. See the files Documentation/ide.txt
868 and drivers/block/ali14xx.c for more info.
871 CONFIG_BLK_DEV_DTC2278
872 This driver is enabled at runtime using the "ide0=dtc2278" kernel
873 boot parameter. It enables support for the secondary IDE interface
874 of the DTC-2278 card, and permits faster I/O speeds to be set as
875 well. See the Documentation/ide.txt and drivers/block/dtc2278.c
878 Holtek HT6560B support
879 CONFIG_BLK_DEV_HT6560B
880 This driver is enabled at runtime using the "ide0=ht6560b" kernel
881 boot parameter. It enables support for the secondary IDE interface
882 of the Holtek card, and permits faster I/O speeds to be set as well.
883 See the Documentation/ide.txt and drivers/block/ht6560b.c files for
886 PROMISE DC4030 support (EXPERIMENTAL)
887 CONFIG_BLK_DEV_PDC4030
888 This driver provides support for the secondary IDE interface and
889 cache of Promise IDE chipsets, e.g. DC4030 and DC5030. This driver
890 is known to incur timeouts/retries during heavy I/O to drives
891 attached to the secondary interface. CDROM and TAPE devices are not
892 supported yet. This driver is enabled at runtime using the
893 "ide0=dc4030" kernel boot parameter. See the Documentation/ide.txt
894 and drivers/block/pdc4030.c files for more info.
897 CONFIG_BLK_DEV_QD6580
898 This driver is enabled at runtime using the "ide0=qd6580" kernel
899 boot parameter. It permits faster I/O speeds to be set. See the
900 files Documentation/ide.txt and drivers/block/qd6580.c for more
904 CONFIG_BLK_DEV_UMC8672
905 This driver is enabled at runtime using the "ide0=umc8672" kernel
906 boot parameter. It enables support for the secondary IDE interface
907 of the UMC-8672, and permits faster I/O speeds to be set as well.
908 See the files Documentation/ide.txt and drivers/block/umc8672.c for
911 PS/2 ESDI hard disk support
913 Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
916 If you want to compile the driver as a module ( = code which can be
917 inserted in and removed from the running kernel whenever you want),
918 say M here and read Documentation/modules.txt. The module will be
921 Amiga builtin Gayle IDE interface support
923 This is the IDE driver for the builtin IDE interface on some Amiga
924 models. It supports both the `A1200 style' (used in A600 and A1200)
925 and `A4000 style' (used in A4000 and A4000T) of the Gayle IDE
926 interface. Say Y if you have such an Amiga model and want to use IDE
927 devices (hard disks, CD-ROM drives, etc.) that are connected to the
928 builtin IDE interface.
930 Falcon IDE interface support
931 CONFIG_BLK_DEV_FALCON_IDE
932 This is the IDE driver for the builtin IDE interface on the Atari
933 Falcon. Say Y if you have a Falcon and want to use IDE devices (hard
934 disks, CD-ROM drives, etc.) that are connected to the builtin IDE
937 Amiga Buddha/Catweasel IDE interface support (EXPERIMENTAL)
938 CONFIG_BLK_DEV_BUDDHA
939 This is the IDE driver for the IDE interfaces on the Buddha and
940 Catweasel expansion boards. It supports up to two interfaces on the
941 Buddha and three on the Catweasel.
943 Say Y if you have a Buddha or Catweasel expansion board and want to
944 use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
945 to one of its IDE interfaces.
947 Amiga IDE Doubler support (EXPERIMENTAL)
948 CONFIG_BLK_DEV_IDEDOUBLER
949 This driver provides support for the so called `IDE doublers' (made
950 by various manufacturers, e.g. Eyetech) that can be connected to the
951 builtin IDE interface of some Amiga models. Using such an IDE
952 doubler, you can connect up to four instead of two IDE devices on
953 the Amiga's builtin IDE interface.
955 Note that the normal Amiga Gayle IDE driver may not work correctly
956 if you have an IDE doubler and don't enable this driver!
958 Say Y if you have an IDE doubler. The driver is enabled at kernel
959 runtime using the "ide=doubler" kernel boot parameter.
961 Support for PowerMac IDE devices (must also enable IDE)
962 CONFIG_BLK_DEV_IDE_PMAC
963 No help for CONFIG_BLK_DEV_IDE_PMAC
965 PowerMac IDE DMA support
966 CONFIG_BLK_DEV_IDEDMA_PMAC
967 No help for CONFIG_BLK_DEV_IDEDMA_PMAC
970 CONFIG_IDEDMA_PMAC_AUTO
971 No help for CONFIG_IDEDMA_PMAC_AUTO
973 Macintosh Quadra/Powerbook IDE interface support
974 CONFIG_BLK_DEV_MAC_IDE
975 This is the IDE driver for the builtin IDE interface on some m68k
976 Macintosh models. It supports both the `Quadra style' (used in
977 Quadra/ Centris 630 and Performa 588 models) and `Powerbook style'
978 (used in the Powerbook 150 and 190 models) IDE interface.
980 Say Y if you have such an Macintosh model and want to use IDE
981 devices (hard disks, CD-ROM drives, etc.) that are connected to the
982 builtin IDE interface.
984 ICS IDE interface support
985 CONFIG_BLK_DEV_IDE_ICSIDE
986 No help for CONFIG_BLK_DEV_IDE_ICSIDE
989 CONFIG_BLK_DEV_IDEDMA_ICS
990 No help for CONFIG_BLK_DEV_IDEDMA_ICS
992 Use ICS DMA by default
993 CONFIG_IDEDMA_ICS_AUTO
994 No help for CONFIG_IDEDMA_ICS_AUTO
996 RapIDE interface support
997 CONFIG_BLK_DEV_IDE_RAPIDE
998 No help for CONFIG_BLK_DEV_IDE_RAPIDE
1000 XT hard disk support
1002 Very old 8 bit hard disk controllers used in the IBM XT computer
1003 will be supported if you say Y here.
1005 If you want to compile the driver as a module ( = code which can be
1006 inserted in and removed from the running kernel whenever you want),
1007 say M here and read Documentation/modules.txt. The module will be
1010 It's pretty unlikely that you have one of these: say N.
1012 Mylex DAC960/DAC1100 PCI RAID Controller support
1013 CONFIG_BLK_DEV_DAC960
1014 This driver adds support for the Mylex DAC960, AcceleRAID, and
1015 eXtremeRAID PCI RAID controllers. See the file
1016 Documentation/README.DAC960 for further information about this
1019 If you want to compile the driver as a module ( = code which can be
1020 inserted in and removed from the running kernel whenever you want),
1021 say M here and read Documentation/modules.txt. The module will be
1024 Parallel port IDE device support
1026 There are many external CD-ROM and disk devices that connect through
1027 your computer's parallel port. Most of them are actually IDE devices
1028 using a parallel port IDE adapter. This option enables the PARIDE
1029 subsystem which contains drivers for many of these external drives.
1030 Read linux/Documentation/paride.txt for more information.
1032 If you have said Y to the "Parallel-port support" configuration
1033 option, you may share a single port between your printer and other
1034 parallel port devices. Answer Y to build PARIDE support into your
1035 kernel, or M if you would like to build it as a loadable module. If
1036 your parallel port support is in a loadable module, you must build
1037 PARIDE as a module. If you built PARIDE support into your kernel,
1038 you may still build the individual protocol modules and high-level
1039 drivers as loadable modules. If you build this support as a module,
1040 it will be called paride.o.
1042 To use the PARIDE support, you must say Y or M here and also to at
1043 least one high-level driver (e.g. "Parallel port IDE disks",
1044 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
1045 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
1046 "MicroSolutions backpack protocol", "DataStor Commuter protocol"
1049 Parallel port IDE disks
1051 This option enables the high-level driver for IDE-type disk 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 IDE driver, otherwise you should answer M to build
1055 it as a loadable module. The module will be called pd.o. You
1056 must also have at least one parallel port protocol driver in your
1057 system. Among the devices supported by this driver are the SyQuest
1058 EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack
1059 hard drives from MicroSolutions.
1061 Parallel port ATAPI CD-ROMs
1063 This option enables the high-level driver for ATAPI CD-ROM devices
1064 connected through a parallel port. If you chose to build PARIDE
1065 support into your kernel, you may answer Y here to build in the
1066 parallel port ATAPI CD-ROM driver, otherwise you should answer M to
1067 build it as a loadable module. The module will be called pcd.o. You
1068 must also have at least one parallel port protocol driver in your
1069 system. Among the devices supported by this driver are the
1070 MicroSolutions backpack CD-ROM drives and the Freecom Power CD. If
1071 you have such a CD-ROM drive, you should also say Y or M to "ISO
1072 9660 CDROM filesystem support" below, because that's the filesystem
1075 Parallel port ATAPI disks
1077 This option enables the high-level driver for ATAPI disk devices
1078 connected through a parallel port. If you chose to build PARIDE
1079 support into your kernel, you may answer Y here to build in the
1080 parallel port ATAPI disk driver, otherwise you should answer M
1081 to build it as a loadable module. The module will be called pf.o.
1082 You must also have at least one parallel port protocol driver in
1083 your system. Among the devices supported by this driver are the
1084 MicroSolutions backpack PD/CD drive and the Imation Superdisk
1087 Parallel port ATAPI tapes
1089 This option enables the high-level driver for ATAPI tape devices
1090 connected through a parallel port. If you chose to build PARIDE
1091 support into your kernel, you may answer Y here to build in the
1092 parallel port ATAPI disk driver, otherwise you should answer M
1093 to build it as a loadable module. The module will be called pt.o.
1094 You must also have at least one parallel port protocol driver in
1095 your system. Among the devices supported by this driver is the
1096 parallel port version of the HP 5GB drive.
1098 Parallel port generic ATAPI devices
1100 This option enables a special high-level driver for generic ATAPI
1101 devices connected through a parallel port. The driver allows user
1102 programs, such as cdrecord, to send ATAPI commands directly to a
1105 If you chose to build PARIDE support into your kernel, you may
1106 answer Y here to build in the parallel port generic ATAPI driver,
1107 otherwise you should answer M to build it as a loadable module. The
1108 module will be called pg.o.
1110 You must also have at least one parallel port protocol driver in
1113 This driver implements an API loosely related to the generic SCSI
1114 driver. See /usr/include/linux/pg.h for details.
1116 You can obtain the most recent version of cdrecord from
1117 ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/ . Versions 1.6.1a3 and
1118 later fully support this driver.
1120 ATEN EH-100 protocol
1122 This option enables support for the ATEN EH-100 parallel port IDE
1123 protocol. This protocol is used in some inexpensive low performance
1124 parallel port kits made in Hong Kong. If you chose to build PARIDE
1125 support into your kernel, you may answer Y here to build in the
1126 protocol driver, otherwise you should answer M to build it as a
1127 loadable module. The module will be called aten.o. You must also
1128 have a high-level driver for the type of device that you want to
1131 MicroSolutions backpack protocol
1133 This option enables support for the MicroSolutions backpack parallel
1134 port IDE protocol. If you chose to build PARIDE support into your
1135 kernel, you may answer Y here to build in the protocol driver,
1136 otherwise you should answer M to build it as a loadable module. The
1137 module will be called bpck.o. You must also have a high-level driver
1138 for the type of device that you want to support.
1140 DataStor Commuter protocol
1142 This option enables support for the Commuter parallel port IDE
1143 protocol from DataStor. If you chose to build PARIDE support
1144 into your kernel, you may answer Y here to build in the protocol
1145 driver, otherwise you should answer M to build it as a loadable
1146 module. The module will be called comm.o. You must also have
1147 a high-level driver for the type of device that you want to support.
1149 DataStor EP-2000 protocol
1151 This option enables support for the EP-2000 parallel port IDE
1152 protocol from DataStor. If you chose to build PARIDE support
1153 into your kernel, you may answer Y here to build in the protocol
1154 driver, otherwise you should answer M to build it as a loadable
1155 module. The module will be called dstr.o. You must also have
1156 a high-level driver for the type of device that you want to support.
1158 Shuttle EPAT/EPEZ protocol
1160 This option enables support for the EPAT parallel port IDE protocol.
1161 EPAT is a parallel port IDE adapter manufactured by Shuttle
1162 Technology and widely used in devices from major vendors such as
1163 Hewlett-Packard, SyQuest, Imation and Avatar. If you chose to build
1164 PARIDE support into your kernel, you may answer Y here to build in
1165 the protocol driver, otherwise you should answer M to build it as a
1166 loadable module. The module will be called epat.o. You must also
1167 have a high-level driver for the type of device that you want to
1170 Shuttle EPIA protocol
1172 This option enables support for the (obsolete) EPIA parallel port
1173 IDE protocol from Shuttle Technology. This adapter can still be
1174 found in some no-name kits. If you chose to build PARIDE support
1175 into your kernel, you may answer Y here to build in the protocol
1176 driver, otherwise you should answer M to build it as a loadable
1177 module. The module will be called epia.o. You must also have a
1178 high-level driver for the type of device that you want to support.
1180 FIT TD-2000 protocol
1182 This option enables support for the TD-2000 parallel port IDE
1183 protocol from Fidelity International Technology. This is a simple
1184 (low speed) adapter that is used in some portable hard drives. If
1185 you chose to build PARIDE support into your kernel, you may answer Y
1186 here to build in the protocol driver, otherwise you should answer M
1187 to build it as a loadable module. The module will be called ktti.o.
1188 You must also have a high-level driver for the type of device that
1189 you want to support.
1191 FIT TD-3000 protocol
1193 This option enables support for the TD-3000 parallel port IDE
1194 protocol from Fidelity International Technology. This protocol is
1195 used in newer models of their portable disk, CD-ROM and PD/CD
1196 devices. If you chose to build PARIDE support into your kernel, you
1197 may answer Y here to build in the protocol driver, otherwise you
1198 should answer M to build it as a loadable module. The module will be
1199 called fit3.o. You must also have a high-level driver for the type
1200 of device that you want to support.
1202 Freecom IQ ASIC-2 protocol
1204 This option enables support for version 2 of the Freecom IQ parallel
1205 port IDE adapter. This adapter is used by the Maxell Superdisk
1206 drive. If you chose to build PARIDE support into your kernel, you
1207 may answer Y here to build in the protocol driver, otherwise you
1208 should answer M to build it as a loadable module. The module will be
1209 called friq.o. You must also have a high-level driver for the type
1210 of device that you want to support.
1212 FreeCom power protocol
1214 This option enables support for the Freecom power parallel port IDE
1215 protocol. If you chose to build PARIDE support into your kernel, you
1216 may answer Y here to build in the protocol driver, otherwise you
1217 should answer M to build it as a loadable module. The module will be
1218 called frpw.o. You must also have a high-level driver for the type
1219 of device that you want to support.
1221 KingByte KBIC-951A/971A protocols
1223 This option enables support for the KBIC-951A and KBIC-971A parallel
1224 port IDE protocols from KingByte Information Corp. KingByte's
1225 adapters appear in many no-name portable disk and CD-ROM products,
1226 especially in Europe. If you chose to build PARIDE support into your
1227 kernel, you may answer Y here to build in the protocol driver,
1228 otherwise you should answer M to build it as a loadable module. The
1229 module will be called kbic.o. You must also have a high-level driver
1230 for the type of device that you want to support.
1234 This option enables support for the "PHd" parallel port IDE protocol
1235 from KT Technology. This is a simple (low speed) adapter that is
1236 used in some 2.5" portable hard drives. If you chose to build PARIDE
1237 support into your kernel, you may answer Y here to build in the
1238 protocol driver, otherwise you should answer M to build it as a
1239 loadable module. The module will be called ktti.o. You must also
1240 have a high-level driver for the type of device that you want to
1243 OnSpec 90c20 protocol
1245 This option enables support for the (obsolete) 90c20 parallel port
1246 IDE protocol from OnSpec (often marketed under the ValuStore brand
1247 name). If you chose to build PARIDE support into your kernel, you
1248 may answer Y here to build in the protocol driver, otherwise you
1249 should answer M to build it as a loadable module. The module will
1250 be called on20.o. You must also have a high-level driver for the
1251 type of device that you want to support.
1253 OnSpec 90c26 protocol
1255 This option enables support for the 90c26 parallel port IDE protocol
1256 from OnSpec Electronics (often marketed under the ValuStore brand
1257 name). If you chose to build PARIDE support into your kernel, you
1258 may answer Y here to build in the protocol driver, otherwise you
1259 should answer M to build it as a loadable module. The module will be
1260 called on26.o. You must also have a high-level driver for the type
1261 of device that you want to support.
1263 Logical Volume Manager (LVM) support
1265 This driver lets you combine several hard disks, hard disk partitions,
1266 multiple devices or even loop devices (for evaluation purposes) into
1267 a volume group. Imagine a volume group as a kind of virtual disk.
1268 Logical volumes, which can be thought of as virtual partitions,
1269 can be created in the volume group. You can resize volume groups and
1270 logical volumes after creation time, corresponding to new capacity needs.
1271 Logical volumes are accessed as block devices named
1272 /dev/VolumeGroupName/LogicalVolumeName.
1274 For details see /usr/src/linux/Documentaion/LVM-HOWTO.
1276 To get the newest software see <http://linux.msede.com/lvm>.
1278 Logical Volume Manager proc filesystem information
1280 If you say Y here, you are able to access overall Logical Volume Manager,
1281 Volume Group, Logical and Physical Volume information in /proc/lvm.
1283 To use this option, you have to check, that the "proc filesystem support"
1284 (CONFIG_PROC_FS) is enabled too.
1286 Multiple devices driver support
1288 This driver lets you combine several hard disk partitions into one
1289 logical block device. This can be used to simply append one
1290 partition to another one or to combine several redundant
1291 hard disks to a RAID1/4/5 device so as to provide protection against
1292 hard disk failures. This is called "Software RAID" since the
1293 combining of the partitions is done by the kernel. "Hardware RAID"
1294 means that the combining is done by a dedicated controller; if you
1295 have such a controller, you do not need to say Y here.
1297 More information about Software RAID on Linux is contained in the
1298 Software-RAID mini-HOWTO, available from
1299 http://www.linuxdoc.org/docs.html#howto . There you will also
1300 learn where to get the supporting user space utilities raidtools.
1304 Linear (append) mode
1306 If you say Y here, then your multiple devices driver will be able to
1307 use the so-called linear mode, i.e. it will combine the hard disk
1308 partitions by simply appending one to the other.
1310 If you want to compile this as a module ( = code which can be
1311 inserted in and removed from the running kernel whenever you want),
1312 say M here and read Documentation/modules.txt. The module will be
1317 RAID-0 (striping) mode
1319 If you say Y here, then your multiple devices driver will be able to
1320 use the so-called raid0 mode, i.e. it will combine the hard disk
1321 partitions into one logical device in such a fashion as to fill them
1322 up evenly, one chunk here and one chunk there. This will increase
1323 the throughput rate if the partitions reside on distinct disks.
1325 Information about Software RAID on Linux is contained in the
1326 Software-RAID mini-HOWTO, available from
1327 http://www.linuxdoc.org/docs.html#howto . There you will also
1328 learn where to get the supporting user space utilities raidtools.
1330 If you want to compile this as a module ( = code which can be
1331 inserted in and removed from the running kernel whenever you want),
1332 say M here and read Documentation/modules.txt. The module will be
1337 RAID-1 (mirroring) mode
1339 A RAID-1 set consists of several disk drives which are exact copies
1340 of each other. In the event of a mirror failure, the RAID driver
1341 will continue to use the operational mirrors in the set, providing
1342 an error free MD (multiple device) to the higher levels of the
1343 kernel. In a set with N drives, the available space is the capacity
1344 of a single drive, and the set protects against a failure of (N - 1)
1347 Information about Software RAID on Linux is contained in the
1348 Software-RAID mini-HOWTO, available from
1349 http://www.linuxdoc.org/docs.html#howto . There you will also
1350 learn where to get the supporting user space utilities raidtools.
1352 If you want to use such a RAID-1 set, say Y. This code is also
1353 available as a module called raid1.o ( = code which can be inserted
1354 in and removed from the running kernel whenever you want). If you
1355 want to compile it as a module, say M here and read
1356 Documentation/modules.txt.
1362 A RAID-5 set of N drives with a capacity of C MB per drive provides
1363 the capacity of C * (N - 1) drives, and protects against a failure
1364 of a single drive. For a given sector (row) number, (N - 1) drives
1365 contain data sectors, and one drive contains the parity protection.
1366 For a RAID-4 set, the parity blocks are present on a single drive,
1367 while a RAID-5 set distributes the parity across the drives in one
1368 of the available parity distribution methods.
1370 Information about Software RAID on Linux is contained in the
1371 Software-RAID mini-HOWTO, available from
1372 http://www.linuxdoc.org/docs.html#howto . There you will also
1373 learn where to get the supporting user space utilities raidtools.
1375 If you want to use such a RAID-4/RAID-5 set, say Y. This code is
1376 also available as a module called raid5.o ( = code which can be
1377 inserted in and removed from the running kernel whenever you want).
1378 If you want to compile it as a module, say M here and read
1379 Documentation/modules.txt.
1383 Boot support (linear, striped)
1385 To boot with an initial linear or striped md device you have to
1386 answer Y here. For lilo and loadlin options see the file
1387 Documentation/md.txt.
1389 Support for Deskstation RPC44
1390 CONFIG_DESKSTATION_RPC44
1391 This is a machine with a R4400 100 MHz CPU. To compile a Linux
1392 kernel that runs on these, say Y here. For details about Linux
1393 on the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1394 http://lena.fnet.fr/ .
1396 Support for Acer PICA 1 chipset
1398 This is a machine with a R4400 133/150 MHz CPU. To compile a Linux
1399 kernel that runs on these, say Y here. For details about Linux on
1400 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1401 http://lena.fnet.fr/ .
1403 Support for Algorithmics P4032 (EXPERIMENTAL)
1405 This is an evaluation board of the British company Algorithmics. The
1406 board uses the R4300 and a R5230 CPUs. For more information about
1407 this board see http://www.algor.co.uk .
1410 CONFIG_BLK_DEV_IDE_CARDS
1411 On Acorn systems, say Y here if you wish to use an IDE interface
1412 expansion card. If you do not or are unsure, say N to this.
1415 CONFIG_BLK_DEV_IDE_ICS
1416 On Acorn systems, say Y here if you wish to use the ICS IDE
1417 interface card. This is not required for ICS partition support.
1418 If you are unsure, say N to this.
1420 ADFS partition support
1422 This allows Linux on Acorn systems to determine its partitions in
1423 the 'non-ADFS' partition area of the hard disk - usually located
1424 after the ADFS partition. You are probably using this system, so
1425 you should say Y here.
1427 Support for Mips Magnum 4000
1428 CONFIG_MIPS_MAGNUM_4000
1429 This is a machine with a R4000 100 MHz CPU. To compile a Linux
1430 kernel that runs on these, say Y here. For details about Linux on
1431 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1432 http://lena.fnet.fr/ .
1434 Support for Olivetti M700
1435 CONFIG_OLIVETTI_M700
1436 This is a machine with a R4000 100 MHz CPU. To compile a Linux
1437 kernel that runs on these, say Y here. For details about Linux on
1438 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1439 http://lena.fnet.fr/ .
1443 Give the type of your machine's MIPS CPU. For this question, it
1444 suffices to give a unique prefix of the option you want to choose.
1445 In case of doubt select the R3000 CPU. The kernel will then run on
1446 other MIPS machines but with slightly reduced performance.
1448 Compile the kernel into the ECOFF object format
1450 Some machines require a kernel in the ECOFF format. You will have to
1451 say Y here for example if you want to use a Mips Magnum 3000 or a
1454 Generate little endian code
1455 CONFIG_CPU_LITTLE_ENDIAN
1456 Some MIPS machines can be configured for either little or big endian
1457 byte order. These modes require different kernels. Say Y if your
1458 machine is little endian, N if it's a big endian machine.
1460 Kernel support for IRIX binaries
1462 If you say Y here, the kernel will support running of IRIX binaries.
1463 You will need IRIX libraries for this to work.
1467 Unless you really know what you are doing, you should say Y here.
1468 The reason is that some programs need kernel networking support even
1469 when running on a stand-alone machine that isn't connected to any
1470 other computer. If you are upgrading from an older kernel, you
1471 should consider updating your networking tools too because changes
1472 in the kernel and the tools often go hand in hand. The tools are
1473 contained in the package net-tools, the location and version number
1474 of which are given in Documentation/Changes.
1476 For a general introduction to Linux networking, it is highly
1477 recommended to read the NET-3-HOWTO, available from
1478 http://www.linuxdoc.org/docs.html#howto .
1482 The Linux Socket Filter is derived from the Berkeley Packet Filter.
1483 If you say Y here, user-space programs can attach a filter to any
1484 socket and thereby tell the kernel that it should allow or disallow
1485 certain types of data to get through the socket. Linux Socket
1486 Filtering works on all socket types except TCP for now. See the text
1487 file linux/Documentation/networking/filter.txt for more information.
1490 Network packet filtering
1492 Netfilter is a framework for filtering and mangling network packets
1493 that pass through your Linux box.
1495 The most common use of packet filtering is to run your Linux box as
1496 a firewall protecting a local network from the Internet. The type of
1497 firewall provided by this kernel support is called a "packet
1498 filter", which means that it can reject individual network packets
1499 based on type, source, destination etc. The other kind of firewall,
1500 a "proxy-based" one, is more secure but more intrusive and more
1501 bothersome to set up; it inspects the network traffic much more
1502 closely, modifies it and has knowledge about the higher level
1503 protocols, which a packet filter lacks. Moreover, proxy-based
1504 firewalls often require changes to the programs running on the local
1505 clients. Proxy-based firewalls don't need support by the kernel, but
1506 they are often combined with a packet filter, which only works if
1509 You should also say Y here if you intend to use your Linux box as
1510 the gateway to the Internet for a local network of machines without
1511 globally valid IP addresses. This is called "masquerading": if one
1512 of the computers on your local network wants to send something to
1513 the outside, your box can "masquerade" as that computer, i.e. it
1514 forwards the traffic to the intended outside destination, but
1515 modifies the packets to make it look like they came from the
1516 firewall box itself. It works both ways: if the outside host
1517 replies, the Linux box will silently forward the traffic to the
1518 correct local computer. This way, the computers on your local net
1519 are completely invisible to the outside world, even though they can
1520 reach the outside and can receive replies. It is even possible to
1521 run globally visible servers from within a masqueraded local network
1522 using a mechanism called portforwarding. Masquerading is also often
1523 called NAT (Network Address Translation).
1525 Another use of Netfilter is in transparent proxying: if a machine on
1526 the local network tries to connect to an outside host, your Linux
1527 box can transparently forward the traffic to a local server,
1528 typically a caching proxy server.
1530 Various modules exist for netfilter which replace the previous
1531 masquerading (ipmasqadm), packet filtering (ipchains), transparent
1532 proxying, and portforwarding mechanisms. More information is
1533 available from http://netfilter.kernelnotes.org .
1535 Make sure to say N to "Fast switching" below if you intend to say Y
1536 here, as Fast switching currently bypasses netfilter.
1538 Chances are that you should say Y here if you compile a kernel which
1539 will run as a router and N for regular hosts. If unsure, say N.
1541 SYN flood protection
1543 Normal TCP/IP networking is open to an attack known as "SYN
1544 flooding". This denial-of-service attack prevents legitimate remote
1545 users from being able to connect to your computer during an ongoing
1546 attack and requires very little work from the attacker, who can
1547 operate from anywhere on the Internet.
1549 SYN cookies provide protection against this type of attack. If you
1550 say Y here, the TCP/IP stack will use a cryptographic challenge
1551 protocol known as "SYN cookies" to enable legitimate users to
1552 continue to connect, even when your machine is under attack. There
1553 is no need for the legitimate users to change their TCP/IP software;
1554 SYN cookies work transparently to them. For technical information
1555 about SYN cookies, check out
1556 ftp://koobera.math.uic.edu/syncookies.html .
1558 If you are SYN flooded, the source address reported by the kernel is
1559 likely to have been forged by the attacker; it is only reported as
1560 an aid in tracing the packets to their actual source and should not
1561 be taken as absolute truth.
1563 SYN cookies may prevent correct error reporting on clients when the
1564 server is really overloaded. If this happens frequently better turn
1567 If you say Y here, note that SYN cookies aren't enabled by default;
1568 you can enable them by saying Y to "/proc filesystem support" and
1569 "Sysctl support" below and executing the command
1571 echo 1 >/proc/sys/net/ipv4/tcp_syncookies
1573 at boot time after the proc filesystem has been mounted.
1577 Sun floppy controller support
1578 CONFIG_BLK_DEV_SUNFD
1579 This is support for floppy drives on Sun SPARC workstations. Say Y
1580 if you have a floppy drive, otherwise N. Easy.
1583 CONFIG_ALPHA_GENERIC
1584 This is the system type of your hardware. A "generic" kernel will
1585 run on any supported Alpha system. However, if you configure a
1586 kernel for your specific system, it will be faster and smaller.
1588 To find out what type of Alpha system you have, you may want to
1589 check out the Linux/Alpha FAQ, accessible on the WWW from
1590 http://www.alphalinux.org . In summary:
1592 Alcor/Alpha-XLT AS 600
1593 Alpha-XL XL-233, XL-266
1594 AlphaBook1 Alpha laptop
1595 Avanti AS 200, AS 205, AS 250, AS 255, AS 300, AS 400
1596 Cabriolet AlphaPC64, AlphaPCI64
1598 EB164 EB164 21164 evaluation board
1599 EB64+ EB64+ 21064 evaluation board
1600 EB66 EB66 21066 evaluation board
1601 EB66+ EB66+ 21066 evaluation board
1602 Jensen DECpc 150, DEC 2000 model 300,
1605 Miata Personal Workstation 433a, 433au, 500a,
1606 500au, 600a, or 600au
1608 Noname AXPpci33, UDB (Multia)
1609 Noritake AS 1000A, AS 600A, AS 800
1611 Rawhide AS 1200, AS 4000, AS 4100
1612 Ruffian RPX164-2, AlphaPC164-UX, AlphaPC164-BX
1614 Sable AS 2000, AS 2100
1617 If you don't know what to do, choose "generic".
1619 EV5 CPU daughtercard
1621 Say Y if you have an AS 1000 5/xxx or an AS 1000A 5/xxx.
1625 Say Y if you have an AS 2000 5/xxx or an AS 2100 5/xxx.
1627 Using SRM as bootloader
1629 There are two different types of booting firmware on Alphas: SRM,
1630 which is command line driven, and ARC, which uses menus and arrow
1631 keys. Details about the Linux/Alpha booting process are contained in
1632 the Linux/Alpha FAQ, accessible on the WWW from
1633 http://www.alphalinux.org .
1635 The usual way to load Linux on an Alpha machine is to use MILO
1636 (a bootloader that lets you pass command line parameters to the
1637 kernel just like lilo does for the x86 architecture) which can be
1638 loaded either from ARC or can be installed directly as a permanent
1639 firmware replacement from floppy (which requires changing a certain
1640 jumper on the motherboard). If you want to do either of these, say N
1641 here. If MILO doesn't work on your system (true for Jensen
1642 motherboards), you can bypass it altogether and boot Linux directly
1643 from an SRM console; say Y here in order to do that. Note that you
1644 won't be able to boot from an IDE disk using SRM.
1649 CONFIG_ALPHA_SRM_SETUP
1650 This option controls whether or not the PCI configuration set up by
1651 SRM is modified. If you say Y, the existing PCI configuration will
1654 Non-standard serial port support
1655 CONFIG_SERIAL_NONSTANDARD
1656 Say Y here if you have any non-standard serial boards -- boards
1657 which aren't supported using the standard "dumb" serial driver.
1658 This includes intelligent serial boards such as Cyclades,
1659 Digiboards, etc. These are usually used for systems that need many
1660 serial ports because they serve many terminals or dial-in
1663 Note that the answer to this question won't directly affect the
1664 kernel: saying N will just cause this configure script to skip all
1665 the questions about non-standard serial boards.
1667 Most people can say N here.
1669 Extended dumb serial driver options
1670 CONFIG_SERIAL_EXTENDED
1671 If you wish to use any non-standard features of the standard "dumb"
1672 driver, say Y here. This includes HUB6 support, shared serial
1673 interrupts, special multiport support, support for more than the
1674 four COM 1/2/3/4 boards, etc.
1676 Note that the answer to this question won't directly affect the
1677 kernel: saying N will just cause this configure script to skip all
1678 the questions about serial driver options. If unsure, say N.
1680 Support more than 4 serial ports
1681 CONFIG_SERIAL_MANY_PORTS
1682 Say Y here if you have dumb serial boards other than the four
1683 standard COM 1/2/3/4 ports. This may happen if you have an AST
1684 FourPort, Accent Async, Boca (read the Boca mini-HOWTO, available
1685 from http://www.linuxdoc.org/docs.html#howto ), or other custom
1686 serial port hardware which acts similar to standard serial port
1687 hardware. If you only use the standard COM 1/2/3/4 ports, you can
1688 say N here to save some memory. You can also say Y if you have an
1689 "intelligent" multiport card such as Cyclades, Digiboards, etc.
1691 Support for sharing serial interrupts
1692 CONFIG_SERIAL_SHARE_IRQ
1693 Some serial boards have hardware support which allows multiple dumb
1694 serial ports on the same board to share a single IRQ. To enable
1695 support for this in the serial driver, say Y here.
1697 Auto detect IRQ on standard ports (unsafe)
1698 CONFIG_SERIAL_DETECT_IRQ
1699 Say Y here if you want the kernel to try to guess which IRQ
1700 to use for your serial port.
1702 This is considered unsafe; it is far better to configure the IRQ in
1703 a boot script using the setserial command.
1707 Support special multiport boards
1708 CONFIG_SERIAL_MULTIPORT
1709 Some multiport serial ports have special ports which are used to
1710 signal when there are any serial ports on the board which need
1711 servicing. Say Y here to enable the serial driver to take advantage
1712 of those special I/O ports.
1714 SGI Zilog85C30 serial support
1716 If you want to use your SGI's built-in serial ports under Linux,
1719 SGI Newport Graphics support (EXPERIMENTAL)
1720 CONFIG_SGI_NEWPORT_GFX
1721 If you have an SGI machine and you want to compile the graphics
1722 drivers, say Y here. This will include the code for the
1723 /dev/graphics and /dev/gfx drivers into the kernel for supporting
1724 virtualized access to your graphics hardware.
1726 Support the Bell Technologies HUB6 card
1728 Say Y here to enable support in the dumb serial driver to support
1731 PCMCIA serial device support
1732 CONFIG_PCMCIA_SERIAL_CS
1733 Say Y here to enable support for 16-bit PCMCIA serial devices,
1734 including serial port cards, modems, and the modem functions of
1735 multifunction ethernet/modem cards.
1737 This driver is also available as a module ( = code which can be
1738 inserted in and removed from the running kernel whenever you want).
1739 The module will be called serial_cs.o. If you want to compile it as a
1740 module, say M here and read Documentation/modules.txt. If unsure,
1743 CardBus serial device support
1744 CONFIG_PCMCIA_SERIAL_CB
1745 Say Y here to enable support for CardBus serial devices, including
1746 the modem functions of multifunction ethernet/modem devices.
1748 This driver is also available as a module ( = code which can be
1749 inserted in and removed from the running kernel whenever you want).
1750 The module will be called serial_cb.o. If you want to compile it as a
1751 module, say M here and read Documentation/modules.txt. If unsure,
1756 Find out whether you have a PCI motherboard. PCI is the name of a
1757 bus system, i.e. the way the CPU talks to the other stuff inside
1758 your box. Other bus systems are ISA, EISA, Microchannel (MCA) or
1759 VESA. If you have PCI, say Y, otherwise N.
1761 The PCI-HOWTO, available from
1762 http://www.linuxdoc.org/docs.html#howto , contains valuable
1763 information about which PCI hardware does work under Linux and which
1768 On PCI systems, the BIOS can be used to detect the PCI devices and
1769 determine their configuration. However, some old PCI motherboards
1770 have BIOS bugs and may crash if this is done. Also, some embedded
1771 PCI-based systems don't have any BIOS at all. Linux can also try to
1772 detect the PCI hardware directly without using the BIOS.
1774 With this option, you can specify how Linux should detect the PCI
1775 devices. If you choose "BIOS", the BIOS will be used, if you choose
1776 "Direct", the BIOS won't be used, and if you choose "Any", the
1777 kernel will try the direct access method and falls back to the BIOS
1778 if that doesn't work. If unsure, go with the default.
1780 PCI device name database
1782 By default, the kernel contains a database of all known PCI device
1783 names to make the information in /proc/pci, /proc/ioports and similar
1784 files comprehensible to the user. This database increases size of
1785 the kernel image by about 80KB, but it gets freed after the system
1786 boots up, so it doesn't take up kernel memory. Anyway, if you are
1787 building an installation floppy or kernel for an embedded system
1788 where kernel image size really matters, you can disable this feature
1789 and you'll get device ID numbers instead of names.
1791 When in doubt, say Y.
1795 MicroChannel Architecture is found in some IBM PS/2 machines and
1796 laptops. It is a bus system similar to PCI or ISA. See
1797 Documentation/mca.txt (and especially the web page given there)
1798 before attempting to build an MCA bus kernel.
1800 SGI Visual Workstation support
1802 The SGI Visual Workstation series is an IA32-based workstation
1803 based on SGI systems chips with some legacy PC hardware attached.
1804 Say Y here to create a kernel to run on the SGI 320 or 540.
1805 A kernel compiled for the Visual Workstation will not run on other
1806 PC boards and vice versa.
1807 See Documentation/sgi-visws.txt for more.
1809 SGI Visual Workstation framebuffer support
1811 SGI Visual Workstation support for framebuffer graphics.
1815 The Intelligent Input/Output (I2O) architecture allows hardware
1816 drivers to be split into two parts: an operating system specific
1817 module called the OSM and an hardware specific module called the
1818 HDM. The OSM can talk to a whole range of HDM's, and ideally the
1819 HDM's are not OS dependent. This allows for the same HDM driver to
1820 be used under different operating systems if the relevant OSM is in
1821 place. In order for this to work, you need to have an I2O interface
1822 adapter card in your computer. This card contains a special I/O
1823 processor (IOP), thus allowing high speeds since the CPU does not
1824 have to deal with I/O.
1826 If you say Y here, you will get a choice of interface adapter
1827 drivers and OSM's with the following questions.
1829 This support is also available as a module ( = code which can be
1830 inserted in and removed from the running kernel whenever you want).
1831 If you want to compile it as a module, say M here and read
1832 Documentation/modules.txt. You will get modules called i2o_core.o
1839 Say Y for support of PCI bus I2O interface adapters. Currently this
1840 is the only variety supported, so you should say Y.
1842 This support is also available as a module called i2o_pci.o ( = code
1843 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 Include support for the I2O Block OSM. The Block OSM presents disk
1850 and other structured block devices to the operating system.
1852 This support is also available as a module called i2o_block.o ( =
1853 code which can be inserted in and removed from the running kernel
1854 whenever you want). If you want to compile it as a module, say M
1855 here and read Documentation/modules.txt.
1859 Include support for the LAN OSM. You will also need to include
1860 support for token ring or FDDI if you wish to use token ring or FDDI
1861 I2O cards with this driver.
1863 This support is also available as a module called i2o_lan.o ( = code
1864 which can be inserted in and removed from the running kernel
1865 whenever you want). If you want to compile it as a module, say M
1866 here and read Documentation/modules.txt.
1870 Allows direct SCSI access to SCSI devices on a SCSI or FibreChannel
1871 I2O controller. You can use both the SCSI and Block OSM together if
1874 This support is also available as a module called i2o_scsi.o ( =
1875 code which can be inserted in and removed from the running kernel
1876 whenever you want). If you want to compile it as a module, say M
1877 here and read Documentation/modules.txt.
1881 If you say Y here and to "/proc filesystem support", you will be
1882 able to read I2O related information from the virtual directory
1885 This support is also available as a module called i2o_proc.o ( =
1886 code which can be inserted in and removed from the running kernel
1887 whenever you want). If you want to compile it as a module, say M
1888 here and read Documentation/modules.txt.
1890 Plug and Play support
1892 Plug and Play (PnP) is a standard for peripherals which allows those
1893 peripherals to be configured by software, e.g. assign IRQ's or other
1894 parameters. No jumpers on the cards are needed, instead the values
1895 are provided to the cards from the BIOS, from the operating system,
1896 or using a user-space utility.
1898 Say Y here if you would like Linux to configure your Plug and Play
1899 devices. You should then also say Y to "ISA Plug and Play support",
1900 below. Alternatively, you can configure your PnP devices using the
1901 user space utilities contained in the isapnptools package.
1903 This support is also available as a module ( = code which can be
1904 inserted in and removed from the running kernel whenever you want).
1905 If you want to compile it as a module, say M here and read
1906 Documentation/modules.txt.
1908 ISA Plug and Play support
1910 Say Y here if you would like support for ISA Plug and Play devices.
1912 This support is also available as a module called isapnp.o ( =
1913 code which can be inserted in and removed from the running kernel
1914 whenever you want). If you want to compile it as a module, say M
1915 here and read Documentation/modules.txt.
1919 PCMCIA/CardBus support
1921 Include kernel support for PCMCIA and CardBus devices. Because
1922 PCMCIA support requires additional components that are not part of
1923 the kernel (i.e., the pcmcia-cs package), building PCMCIA into the
1924 kernel is generally not recommended unless you have a specific
1925 need. If unsure, say N.
1927 This driver is also available as a module ( = code which can be
1928 inserted in and removed from the running kernel whenever you want).
1929 When compiled this way, there will be modules called pcmcia_core.o
1930 and ds.o. If you want to compile it as a module, say M here and
1931 read Documentation/modules.txt.
1933 You will also need David Hinds' pcmcia-cs package (see the file
1934 Documentation/Changes for location). For more information, see the
1939 There are two types of PCMCIA devices: 16-bit PC Cards, and higher
1940 performance 32-bit CardBus devices. Use this option to include
1941 support for CardBus devices. If unsure, say Y.
1943 i82365/Yenta compatible bridge support
1945 Include support for PCMCIA and CardBus host bridges that are
1946 register compatible with the Intel i82365 and/or the Yenta
1947 specification: this includes virtually all modern PCMCIA bridges.
1950 Databook TCIC host bridge support
1952 Include support for the Databook TCIC family of PCMCIA host bridges.
1953 These are only found on a handful of old systems. If unsure, say N.
1957 Inter Process Communication is a suite of library functions and
1958 system calls which let processes (running programs) synchronize and
1959 exchange information. It is generally considered to be a good thing,
1960 and some programs won't run unless you say Y here. In particular, if
1961 you want to run the DOS emulator dosemu under Linux (read the
1962 DOSEMU-HOWTO, available from
1963 http://www.linuxdoc.org/docs.html#howto ), you'll need to say Y
1966 You can find documentation about IPC with "info ipc" and also in
1967 section 6.4 of the Linux Programmer's Guide, available from
1968 http://www.linuxdoc.org/docs.html#guide .
1970 Saying Y here enlarges your kernel by about 18 KB. Just say Y.
1972 BSD Process Accounting
1973 CONFIG_BSD_PROCESS_ACCT
1974 If you say Y here, a user level program will be able to instruct the
1975 kernel (via a special system call) to write process accounting
1976 information to a file: whenever a process exits, information about
1977 that process will be appended to the file by the kernel. The
1978 information includes things such as creation time, owning user,
1979 command name, memory usage, controlling terminal etc. (the complete
1980 list is in the struct acct in include/linux/acct.h). It is up to the
1981 user level program to do useful things with this information. This
1982 is generally a good idea, so say Y.
1986 The sysctl interface provides a means of dynamically changing
1987 certain kernel parameters and variables on the fly without requiring
1988 a recompile of the kernel or reboot of the system. The primary
1989 interface consists of a system call, but if you say Y to "/proc
1990 filesystem support", a tree of modifiable sysctl entries will be
1991 generated beneath the /proc/sys directory. They are explained in the
1992 files in Documentation/sysctl/. Note that enabling this option will
1993 enlarge the kernel by at least 8 KB.
1995 As it is generally a good thing, you should say Y here unless
1996 building a kernel for install/rescue disks or your system is very
1999 Kernel core (/proc/kcore) format
2001 If you enabled support for /proc filesystem then the file /proc/kcore
2002 will contain the kernel core image. This can be used in gdb:
2004 $ cd /usr/src/linux ; gdb vmlinux /proc/kcore
2006 Selecting ELF will make /proc/kcore appear in ELF core format as defined
2007 by the Executable and Linking Format specification. Selecting A.OUT will
2008 choose the old "a.out" format which may be necessary for some old versions
2009 of binutils or on some architectures.
2011 This is especially useful if you have compiled the kernel with "-g" option
2012 to preserve debugging information. It is mainly used for examining kernel
2013 data structures on the live kernel so if you don't understand what this
2014 means or are not a kernel hacker, just leave it at its default value ELF.
2016 Kernel support for ELF binaries
2018 ELF (Executable and Linkable Format) is a format for libraries and
2019 executables used across different architectures and operating
2020 systems. Saying Y here will enable your kernel to run ELF binaries
2021 and enlarge it by about 13 KB. ELF support under Linux has now all
2022 but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC)
2023 because it is portable (this does *not* mean that you will be able
2024 to run executables from different architectures or operating systems
2025 however) and makes building run-time libraries very easy. Many new
2026 executables are distributed solely in ELF format. You definitely
2029 Information about ELF is contained in the ELF HOWTO available from
2030 http://www.linuxdoc.org/docs.html#howto .
2032 If you find that after upgrading from Linux kernel 1.2 and saying Y
2033 here, you still can't run any ELF binaries (they just crash), then
2034 you'll have to install the newest ELF runtime libraries, including
2035 ld.so (check the file Documentation/Changes for location and latest
2038 If you want to compile this as a module ( = code which can be
2039 inserted in and removed from the running kernel whenever you want),
2040 say M here and read Documentation/modules.txt. The module will be
2041 called binfmt_elf.o. Saying M or N here is dangerous because some
2042 crucial programs on your system might be in ELF format.
2044 Kernel support for A.OUT binaries
2046 A.out (Assembler.OUTput) is a set of formats for libraries and
2047 executables used in the earliest versions of UNIX. Linux used the
2048 a.out formats QMAGIC and ZMAGIC until they were replaced with the
2051 As more and more programs are converted to ELF, the use for a.out
2052 will gradually diminish. If you disable this option it will reduce
2053 your kernel by one page. This is not much and by itself does not
2054 warrant removing support. However its removal is a good idea if you
2055 wish to ensure that absolutely none of your programs will use this
2056 older executable format. If you don't know what to answer at this
2057 point then answer Y. If someone told you "You need a kernel with
2058 QMAGIC support" then you'll have to say Y here. You may answer M to
2059 compile a.out support as a module and later load the module when you
2060 want to use a program or library in a.out format. The module will be
2061 called binfmt_aout.o. Saying M or N here is dangerous though,
2062 because some crucial programs on your system might still be in A.OUT
2065 Kernel support for Linux/Intel ELF binaries
2067 Say Y here if you want to be able to execute Linux/Intel ELF
2068 binaries just like native Alpha binaries on your Alpha machine. For
2069 this to work, you need to have the emulator /usr/bin/em86 in place.
2071 You can get the same functionality by saying N here and saying Y to
2072 "Kernel support for MISC binaries".
2074 You may answer M to compile the emulation support as a module and
2075 later load the module when you want to use a Linux/Intel binary. The
2076 module will be called binfmt_em86.o. If unsure, say Y.
2078 Kernel support for MISC binaries
2080 If you say Y here, it will be possible to plug wrapper-driven binary
2081 formats into the kernel. You will like this especially when you use
2082 programs that need an interpreter to run like Java, Python or
2083 Emacs-Lisp. It's also useful if you often run DOS executables under
2084 the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
2085 http://www.linuxdoc.org/docs.html#howto ). Once you have
2086 registered such a binary class with the kernel, you can start one of
2087 those programs simply by typing in its name at a shell prompt; Linux
2088 will automatically feed it to the correct interpreter.
2090 You can do other nice things, too. Read the file
2091 Documentation/binfmt_misc.txt to learn how to use this feature, and
2092 Documentation/java.txt for information about how to include Java
2095 You must say Y to "proc filesystem support" (CONFIG_PROC_FS) to
2096 use this part of the kernel.
2098 You may say M here for module support and later load the module when
2099 you have use for it; the module is called binfmt_misc.o. If you
2100 don't know what to answer at this point, say Y.
2102 Solaris binary emulation (EXPERIMENTAL)
2104 This is experimental code which will enable you to run (many)
2105 Solaris binaries on your SPARC Linux machine.
2107 This code is also available as a module ( = code which can be
2108 inserted in and removed from the running kernel whenever you want).
2109 The module will be called solaris.o. If you want to compile it as a
2110 module, say M here and read Documentation/modules.txt.
2114 This is the processor type of your CPU. This information is used for
2115 optimizing purposes. In order to compile a kernel that can run on
2116 all x86 CPU types (albeit not optimally fast), you can specify
2119 If you specify one of "486" or "586" or "Pentium" or "PPro", then
2120 the kernel will not necessarily run on earlier architectures (e.g. a
2121 Pentium optimized kernel will run on a PPro, but not necessarily on
2124 Here are the settings recommended for greatest speed:
2125 - "386" for the AMD/Cyrix/Intel 386DX/DXL/SL/SLC/SX, Cyrix/TI
2126 486DLC/DLC2 and UMC 486SX-S. Only "386" kernels will run on a 386
2128 - "486" for the AMD/Cyrix/IBM/Intel 486DX/DX2/DX4 or
2129 SL/SLC/SLC2/SLC3/SX/SX2, AMD/Cyrix 5x86, NexGen Nx586 and
2131 - "586" for generic Pentium CPUs, possibly lacking the TSC
2132 (time stamp counter) register.
2133 - "Pentium" for the Intel Pentium/Pentium MMX, AMD K5, K6 and
2135 - "PPro" for the Cyrix/IBM/National Semiconductor 6x86MX, MII and
2136 Intel Pentium II/Pentium Pro.
2138 If you don't know what to do, choose "386".
2142 Saying Y here will allow you to use Linux in text mode through a
2143 display that complies with the generic VGA standard. Virtually
2144 everyone wants that.
2146 The program SVGATextMode can be used to utilize SVGA video cards to
2147 their full potential in text mode. Download it from
2148 ftp://metalab.unc.edu/pub/Linux/utils/console .
2152 Video mode selection support
2154 This enables support for text mode selection on kernel startup. If
2155 you want to take advantage of some high-resolution text mode your
2156 card's BIOS offers, but the traditional Linux utilities like
2157 SVGATextMode don't, you can say Y here and set the mode using the
2158 "vga=" option from your boot loader (lilo or loadlin) or set
2159 "vga=ask" which brings up a video mode menu on kernel startup. (Try
2160 "man bootparam" or see the documentation of your boot loader about
2161 how to pass options to the kernel. The lilo procedure is also
2162 explained in the SCSI-HOWTO, available from
2163 http://www.linuxdoc.org/docs.html#howto .)
2165 Read the file Documentation/svga.txt for more information about the
2166 Video mode selection support. If unsure, say N.
2168 Support for frame buffer devices (EXPERIMENTAL)
2170 The frame buffer device provides an abstraction for the graphics
2171 hardware. It represents the frame buffer of some video hardware and
2172 allows application software to access the graphics hardware through
2173 a well-defined interface, so the software doesn't need to know
2174 anything about the low-level (hardware register) stuff.
2176 Frame buffer devices work identically across the different
2177 architectures supported by Linux and make the implementation of
2178 application programs easier and more portable; at this point, an X
2179 server exists which uses the frame buffer device exclusively.
2180 On several non-X86 architectures, the frame buffer device is the
2181 only way to use the graphics hardware.
2183 The device is accessed through special device nodes, usually located
2184 in the /dev directory, i.e. /dev/fb*.
2186 You need an utility program called fbset to make full use of frame
2187 buffer devices. Please read Documentation/fb/framebuffer.txt and the
2188 Framebuffer-HOWTO at
2189 http://www.tahallah.demon.co.uk/programming/prog.html for more
2192 Say Y here and to the driver for your graphics board below if you
2193 are compiling a kernel for a non-x86 architecture.
2195 If you are compiling for the x86 architecture, you can say Y if you
2196 want to play with it, but it is not essential. Please note that
2197 running graphical applications that directly touch the hardware
2198 (e.g. an accelerated X server) and that are not frame buffer
2199 device-aware may cause unexpected results. If unsure, say N.
2203 This is the frame buffer device driver for the Acorn VIDC graphics
2204 hardware found in Acorn RISC PCs and other ARM-based machines. If
2207 Apollo frame buffer device
2209 This is the frame buffer device driver for the monochrome graphics
2210 hardware found in some Apollo workstations.
2212 Amiga native chipset support
2214 This is the frame buffer device driver for the builtin graphics
2215 chipset found in Amigas.
2217 Amiga OCS chipset support
2219 This enables support for the original Agnus and Denise video chips,
2220 found in the Amiga 1000 and most A500's and A2000's. If you intend
2221 to run Linux on any of these systems, say Y; otherwise say N.
2223 Amiga ECS chipset support
2225 This enables support for the Enhanced Chip Set, found in later
2226 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
2227 you intend to run Linux on any of these systems, say Y; otherwise
2230 Amiga AGA chipset support
2232 This enables support for the Advanced Graphics Architecture (also
2233 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
2234 and CD32. If you intend to run Linux on any of these systems, say Y;
2237 Amiga CyberVision support
2239 This enables support for the Cybervision 64 graphics card from
2240 Phase5. Please note that its use is not all that intuitive (i.e. if
2241 you have any questions, be sure to ask!). Say N unless you have a
2242 Cybervision 64 or plan to get one before you next recompile the
2243 kernel. Please note that this driver DOES NOT support the
2244 Cybervision 64 3D card, as they use incompatible video chips.
2246 CyberPro 20x0 support
2248 This enables support for the Integraphics CyberPro 20x0 and 5000
2249 VGA chips used in the Rebel.com Netwinder and other machines.
2250 Say Y if you have a NetWinder or a graphics card containing this
2251 device, otherwise say N.
2253 Amiga CyberVision3D support (EXPERIMENTAL)
2255 This enables support for the Cybervision 64/3D graphics card from
2256 Phase5. Please note that its use is not all that intuitive (i.e. if
2257 you have any questions, be sure to ask!). Say N unless you have a
2258 Cybervision 64/3D or plan to get one before you next recompile the
2259 kernel. Please note that this driver DOES NOT support the older
2260 Cybervision 64 card, as they use incompatible video chips.
2262 Amiga RetinaZ3 support (EXPERIMENTAL)
2264 This enables support for the Retina Z3 graphics card. Say N unless
2265 you have a Retina Z3 or plan to get one before you next recompile
2268 Cirrus Logic generic driver (EXPERIMENTAL)
2270 This enables support for Cirrus Logic GD542x/543x based boards on
2271 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
2273 If you have a PCI-based system, this enables support for these
2274 chips: GD-543x, GD-544x, GD-5480.
2276 Please read the file Documentation/fb/clgenfb.txt.
2278 Say N unless you have such a graphics board or plan to get one
2279 before you next recompile the kernel.
2281 Permedia2 support (EXPERIMENTAL)
2283 Say Y here if this is your graphics board.
2287 Say Y here if you want to run Linux on an MC680x0-based Apollo
2288 Domain workstation such as the DN3500.
2290 Apollo 3c505 support
2291 CONFIG_APOLLO_ELPLUS
2292 Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
2293 If you don't have one made for Apollos, you can use one from a PC,
2294 except that your Apollo won't be able to boot from it (because the
2295 code in the ROM will be for a PC).
2297 Atari native chipset support
2299 This is the frame buffer device driver for the builtin graphics
2300 chipset found in Ataris.
2302 Open Firmware frame buffer device support
2304 Say Y if you want support with Open Firmware for your graphics
2307 S3 Trio frame buffer device support
2309 If you have a S3 Trio say Y. Say N for S3 Virge.
2311 ATI Mach64 display support (EXPERIMENTAL)
2313 This driver supports graphics boards with the ATI Mach64 chips.
2314 Say Y if you have such a graphics board.
2316 The driver is also available as a module ( = code which can be
2317 inserted and removed from the running kernel whenever you want). The
2318 module will be called atyfb.o. If you want to compile it as a
2319 module, say M here and read Documentation/modules.txt.
2321 ATI Rage128 display support (EXPERIMENTAL)
2323 This driver supports graphics boards with the ATI Rage128 chips.
2324 Say Y if you have such a graphics board.
2326 The driver is also available as a module ( = code which can be
2327 inserted and removed from the running kernel whenever you want). The
2328 module will be called aty128fb.o. If you want to compile it as a
2329 module, say M here and read Documentation/modules.txt.
2331 PowerMac "control" frame buffer device support
2333 This driver supports a frame buffer for the graphics adapter in the
2334 Power Macintosh 7300 and others.
2336 PowerMac "platinum" frame buffer device support
2338 This driver supports a frame buffer for the "platinum" graphics
2339 adapter in some Power Macintoshes.
2341 PowerMac "valkyrie" frame buffer device support
2343 This driver supports a frame buffer for the "valkyrie" graphics
2344 adapter in some Power Macintoshes.
2346 Chips 65550 display support
2348 This is the frame buffer device driver for the Chips & Technologies
2349 65550 graphics chip in PowerBooks.
2351 Mac frame buffer device
2353 This is the frame buffer device driver for the graphics hardware in
2356 HP300 frame buffer device
2358 This is the frame buffer device driver for the Topcat graphics
2359 hardware found in HP300 workstations.
2361 TGA frame buffer support
2363 This is the frame buffer device driver for generic TGA graphic
2364 cards. Say Y if you have one of those.
2366 VESA VGA graphics console
2368 This is the frame buffer device driver for generic VESA 2.0
2369 compliant graphic cards. The older VESA 1.2 cards are not supported.
2370 You will get a boot time penguin logo at no additional cost. Please
2371 read Documentation/fb/vesafb.txt. If unsure, say Y.
2373 VGA 16-color planar support
2374 CONFIG_FBCON_VGA_PLANES
2375 This low level frame buffer console driver enable the kernel to use
2376 the 16-color planar modes of the old VGA cards where the bits of each
2377 pixel are separated into 4 plans.
2378 Only answer Y here if you have an (very old) VGA card that isn't
2381 VGA 16-color graphics console
2383 This is the frame buffer device driver for VGA 16 color graphic
2384 cards. Say Y if you have such a card.
2386 This code is also available as a module. If you want to compile it
2387 as a module ( = code which can be inserted in and removed from the
2388 running kernel whenever you want), say M here and read
2389 Documentation/modules.txt. The module will be called vga16fb.o.
2393 This is the "high resolution" font for the VGA frame buffer (the one
2394 provided by the text console 80x25 mode.
2396 Support only 8 pixels wide fonts
2397 CONFIG_FBCON_FONTWIDTH8_ONLY
2398 Answer Y here will make the kernel provide only the 8x8 fonts (these
2399 are the less readable).
2403 This is the "high resolution" font for the VGA frame buffer (the one
2404 provided by the text console 80x50 (and higher) modes.
2405 Note this is a poor quality font. The VGA 8x16 font is quite a lot
2407 Given the resolution provided by the frame buffer device, anwser N
2410 Backward compatibility mode for Xpmac
2411 CONFIG_FB_COMPAT_XPMAC
2412 If you use the Xpmac X server (common with mklinux), you'll need to
2413 say Y here to use X. You should consider changing to XFree86 which
2414 includes a server that supports the frame buffer device directly
2417 Matrox unified accelerated driver (EXPERIMENTAL)
2419 Say Y here if you have Matrox Millennium, Matrox Millennium II,
2420 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
2421 Mystique G200, Matrox Millennium G200 or Matrox Marvel G200 video
2422 card in your box. At this time, support for the G100, Mystique G200
2423 and Marvel G200 is untested.
2425 This driver is also available as a module ( = code which can be
2426 inserted and removed from the running kernel whenever you want).
2427 The module will be called matroxfb.o. If you want to compile it as
2428 a module, say M here and read Documentation/modules.txt.
2430 You can pass several parameters to the driver at boot time or at
2431 module load time. The parameters look like "video=matrox:XXX", where
2432 the meaning of XXX can be found at the end of the main source file
2433 (drivers/video/matroxfb.c). Please see the file
2434 Documentation/fb/matroxfb.txt.
2436 Matrox Millennium support
2437 CONFIG_FB_MATROX_MILLENIUM
2438 Say Y here if you have a Matrox Millennium or Matrox Millennium II
2439 video card. If you select "Advanced lowlevel driver options" below,
2440 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
2441 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
2442 also use font widths different from 8.
2444 Matrox Mystique support
2445 CONFIG_FB_MATROX_MYSTIQUE
2446 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
2447 video card. If you select "Advanced lowlevel driver options" below,
2448 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
2449 packed pixel and 32 bpp packed pixel. You can also use font widths
2452 Matrox G100/G200/G400 support
2453 CONFIG_FB_MATROX_G100
2454 Say Y here if you have a Matrox Productiva G100, Matrox Mystique
2455 G200, Matrox Marvel G200 or Matrox Millennium G200 video card. If
2456 you select "Advanced lowlevel driver options", you should check 8
2457 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed pixel and 32
2458 bpp packed pixel. You can also use font widths different from 8.
2460 Matrox unified driver multihead support
2461 CONFIG_FB_MATROX_MULTIHEAD
2462 Say Y here if you have more than one (supported) Matrox device in
2463 your computer and you want to use all of them. If you have only one
2464 device, you should say N because the driver compiled with Y is
2465 larger and a bit slower, especially on ia32 (ix86).
2467 If you said M to "Matrox unified accelerated driver" and N here, you
2468 will still be able to use several Matrox devices simultaneously.
2469 This is slightly faster but uses 40 KB of kernel memory per Matrox
2470 card. You do this by inserting several instances of the module
2471 matroxfb.o into the kernel with insmod, supplying the parameter
2472 "dev=N" where N is 0, 1, etc. for the different Matrox devices.
2474 MDA text console (dual-headed)
2476 Say Y here if you have an old MDA or monochrome Hercules graphics
2477 adapter in your system acting as a second head ( = video card). You
2478 will then be able to use two monitors with your Linux system. Do not
2479 say Y here if your MDA card is the primary card in your system; the
2480 normal VGA driver will handle it.
2482 This driver is also available as a module ( = code which can be
2483 inserted and removed from the running kernel whenever you want).
2484 The module will be called mdacon.o. If you want to compile it as
2485 a module, say M here and read Documentation/modules.txt.
2489 SBUS and UPA frame buffers
2491 Say Y if you want support for SBUS or UPA based frame buffer device.
2493 Creator/Creator3D support
2495 This is the frame buffer device driver for the Creator and Creator3D
2498 CGsix (GX,TurboGX) support
2500 This is the frame buffer device driver for the CGsix (GX, TurboGX)
2505 This is the frame buffer device driver for the BWtwo frame buffer.
2509 This is the frame buffer device driver for the CGthree frame buffer.
2511 TCX (SS4/SS5 only) support
2513 This is the frame buffer device driver for the TCX 24/8bit frame
2516 Virtual Frame Buffer support (ONLY FOR TESTING!)
2518 This is a `virtual' frame buffer device. It operates on a chunk of
2519 unswapable kernel memory instead of on the memory of a graphics
2520 board. This means you cannot see any output sent to this frame
2521 buffer device, while it does consume precious memory. The main use
2522 of this frame buffer device is testing and debugging the frame
2523 buffer subsystem. Do NOT enable it for normal systems! To protect
2524 the innocent, it has to be enabled explicitly at boot time using the
2525 kernel option `video=vfb:'.
2527 This driver is also available as a module ( = code which can be
2528 inserted and removed from the running kernel whenever you want). The
2529 module will be called vfb.o. If you want to compile it as a module,
2530 say M here and read Documentation/modules.txt.
2534 Advanced low level driver options
2535 CONFIG_FBCON_ADVANCED
2536 The frame buffer console uses character drawing routines that are
2537 tailored to the specific organization of pixels in the memory of
2538 your graphics hardware. These are called the low level frame buffer
2539 console drivers. Note that they are used for text console output
2540 only; they are NOT needed for graphical applications.
2542 If you say N here, the needed low level drivers are automatically
2543 enabled, depending on what frame buffer devices you selected above.
2544 This is recommended for most users.
2546 If you say Y here, you have more fine-grained control over which low
2547 level drivers are enabled. You can e.g. leave out low level drivers
2548 for color depths you do not intend to use for text consoles.
2550 Low level frame buffer console drivers can be modules ( = code which
2551 can be inserted and removed from the running kernel whenever you
2552 want). The modules will be called fbcon-*.o. If you want to compile
2553 (some of) them as modules, read Documentation/modules.txt.
2559 This is the low level frame buffer console driver for monochrome
2560 (2 colors) packed pixels.
2562 2 bpp packed pixels support
2564 This is the low level frame buffer console driver for 2 bits per
2565 pixel (4 colors) packed pixels.
2567 4 bpp packed pixels support
2569 This is the low level frame buffer console driver for 4 bits per
2570 pixel (16 colors) packed pixels.
2572 8 bpp packed pixels support
2574 This is the low level frame buffer console driver for 8 bits per
2575 pixel (256 colors) packed pixels.
2577 16 bpp packed pixels support
2579 This is the low level frame buffer console driver for 15 or 16 bits
2580 per pixel (32K or 64K colors, also known as `hicolor') packed
2583 24 bpp packed pixels support
2585 This is the low level frame buffer console driver for 24 bits per
2586 pixel (16M colors, also known as `truecolor') packed pixels. It is
2587 NOT for `sparse' 32 bits per pixel mode.
2589 32 bpp packed pixels support
2591 This is the low level frame buffer console driver for 32 bits per
2592 pixel (16M colors, also known as `truecolor') sparse packed pixels.
2594 Amiga bitplanes support
2596 This is the low level frame buffer console driver for 1 to 8
2597 bitplanes (2 to 256 colors) on Amiga.
2599 Amiga interleaved bitplanes support
2601 This is the low level frame buffer console driver for 1 to 8
2602 interleaved bitplanes (2 to 256 colors) on Amiga.
2604 Atari interleaved bitplanes (2 planes) support
2605 CONFIG_FBCON_IPLAN2P2
2606 This is the low level frame buffer console driver for 2 interleaved
2607 bitplanes (4 colors) on Atari.
2609 Atari interleaved bitplanes (4 planes) support
2610 CONFIG_FBCON_IPLAN2P4
2611 This is the low level frame buffer console driver for 4 interleaved
2612 bitplanes (16 colors) on Atari.
2614 Atari interleaved bitplanes (8 planes) support
2615 CONFIG_FBCON_IPLAN2P8
2616 This is the low level frame buffer console driver for 8 interleaved
2617 bitplanes (256 colors) on Atari.
2619 Mac variable bpp packed pixels support
2621 This is the low level frame buffer console driver for 1/2/4/8/16/32
2622 bits per pixel packed pixels on Mac. It supports variable font
2623 widths for low resolution screens.
2625 #VGA 16-color planar support
2626 #CONFIG_FBCON_VGA_PLANES
2631 VGA characters/attributes support
2633 This is the low level frame buffer console driver for VGA text mode;
2634 it is used by frame buffer device drivers that support VGA text
2637 Parallel-port support
2639 If you want to use devices connected to your machine's parallel port
2640 (the connector at the computer with 25 holes), e.g. printer, ZIP
2641 drive, PLIP link (Parallel Line Internet Protocol is mainly used to
2642 create a mini network by connecting the parallel ports of two local
2643 machines) etc., then you need to say Y here; please read
2644 Documentation/parport.txt and drivers/parport/BUGS-parport.
2646 For extensive information about drivers for many devices attaching
2647 to the parallel port see http://www.torque.net/linux-pp.html on the
2650 It is possible to share a single parallel port among several devices
2651 and it is safe to compile all the corresponding drivers into the
2652 kernel. If you want to compile parallel port support as a module ( =
2653 code which can be inserted in and removed from the running kernel
2654 whenever you want), say M here and read Documentation/modules.txt.
2655 The module will be called parport.o. If you have more than one
2656 parallel port and want to specify which port and IRQ to be used by
2657 this driver at module load time, take a look at
2658 Documentation/networking/parport.txt.
2664 You should say Y here if you have a PC-style parallel port. All IBM
2665 PC compatible computers and some Alphas have PC-style parallel
2668 This code is also available as a module. If you want to compile it
2669 as a module ( = code which can be inserted in and removed from the
2670 running kernel whenever you want), say M here and read
2671 Documentation/modules.txt. The module will be called parport_pc.o.
2675 Use FIFO/DMA if available
2676 CONFIG_PARPORT_PC_FIFO
2677 Many parallel port chipsets provide hardware that can speed up
2678 printing. Say Y here if you want to take advantage of that.
2680 As well as actually having a FIFO, or DMA capability, the kernel
2681 will need to know which IRQ the parallel port has. By default,
2682 parallel port interrupts will not be used, and so neither will the
2683 FIFO. See Documentation/parport.txt to find out how to specify
2684 which IRQ/DMA to use.
2686 Support for PCMCIA management for PC-style ports
2687 CONFIG_PARPORT_PC_PCMCIA
2688 Say Y here if you need PCMCIA support for your PC-style parallel
2689 ports. If unsure, say N.
2691 Support foreign hardware
2692 CONFIG_PARPORT_OTHER
2693 Say Y here if you want to be able to load driver modules to support
2694 other non-standard types of parallel ports. This causes a
2695 performance loss, so most people say N.
2697 Sun Ultra/AX-style hardware
2699 Say Y here if you need support for the parallel port hardware on Sun
2700 Ultra/AX machines. This code is also available as a module (say M),
2701 called parport_ax.o. If in doubt, saying N is the safe plan.
2703 Support IEEE1284 status readback
2704 CONFIG_PRINTER_READBACK
2705 If you have a device on your parrallel port that support this protocol,
2706 this option'll enable it to report its status.
2707 It is safe to say Y.
2709 IEEE1284 transfer modes
2711 If you have a printer that supports status readback or device ID, or
2712 want to use a device that uses enhanced parallel port transfer modes
2713 such as EPP and ECP, say Y here to enable advanced IEEE 1284
2714 transfer modes. Also say Y if you want device ID information to
2715 appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
2717 Enable loadable module support
2719 Kernel modules are small pieces of compiled code which can be
2720 inserted in or removed from the running kernel, using the programs
2721 insmod and rmmod. This is described in the file
2722 Documentation/modules.txt, including the fact that you have to say
2723 "make modules" in order to compile the modules that you chose during
2724 kernel configuration. Modules can be device drivers, file systems,
2725 binary executable formats, and so on. If you think that you may want
2726 to make use of modules with this kernel in the future, then say Y
2727 here. If unsure, say Y.
2729 Set version information on all symbols for modules
2731 Usually, modules have to be recompiled whenever you switch to a new
2732 kernel. Saying Y here makes it possible, and safe, to use the
2733 same modules even after compiling a new kernel; this requires the
2734 program modprobe. All the software needed for module support is in
2735 the modutils package (check the file Documentation/Changes for
2736 location and latest version). NOTE: if you say Y here but don't
2737 have the program genksyms (which is also contained in the above
2738 mentioned modutils package), then the building of your kernel will
2739 fail. If you are going to use modules that are generated from
2740 non-kernel sources, you would benefit from this option. Otherwise
2741 it's not that important. So, N ought to be a safe bet.
2743 Kernel module loader support
2745 Normally when you have selected some drivers and/or filesystems to
2746 be created as loadable modules, you also have the responsibility to
2747 load the corresponding modules (using the programs insmod or
2748 modprobe) before you can use them. If you say Y here however, the
2749 kernel will be able to load modules for itself: when a part of the
2750 kernel needs a module, it runs modprobe with the appropriate
2751 arguments, thereby loading the module if it is available. (This is a
2752 replacement for kerneld.) Say Y here and read about configuring it
2753 in Documentation/kmod.txt.
2755 ARP daemon support (EXPERIMENTAL)
2757 Normally, the kernel maintains an internal cache which maps IP
2758 addresses to hardware addresses on the local network, so that
2759 Ethernet/Token Ring/ etc. frames are sent to the proper address on
2760 the physical networking layer. For small networks having a few
2761 hundred directly connected hosts or less, keeping this address
2762 resolution (ARP) cache inside the kernel works well. However,
2763 maintaining an internal ARP cache does not work well for very large
2764 switched networks, and will use a lot of kernel memory if TCP/IP
2765 connections are made to many machines on the network.
2767 If you say Y here, the kernel's internal ARP cache will never grow
2768 to more than 256 entries (the oldest entries are expired in a LIFO
2769 manner) and communication will be attempted with the user space ARP
2770 daemon arpd. Arpd then answers the address resolution request either
2771 from its own cache or by asking the net.
2773 This code is experimental and also obsolete. If you want to use it,
2774 you need to find a version of the daemon arpd on the net somewhere,
2775 and you should also say Y to "Kernel/User network link driver",
2776 below. If unsure, say N.
2780 These are the protocols used on the Internet and on most local
2781 Ethernets. It is highly recommended to say Y here (this will enlarge
2782 your kernel by about 144 KB), since some programs (e.g. the X window
2783 system) use TCP/IP even if your machine is not connected to any
2784 other computer. You will get the so-called loopback device which
2785 allows you to ping yourself (great fun, that!).
2787 For an excellent introduction to Linux networking, please read the
2788 NET-3-HOWTO, available from
2789 http://www.linuxdoc.org/docs.html#howto .
2791 This option is also necessary if you want to use the full power of
2792 term (term is a program which gives you almost full Internet
2793 connectivity if you have a regular dial up shell account on some
2794 Internet connected Unix computer; for more information, read
2795 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html ).
2797 If you say Y here and also to "/proc filesystem support" and "Sysctl
2798 support" below, you can change various aspects of the behavior of
2799 the TCP/IP code by writing to the (virtual) files in
2800 /proc/sys/net/ipv4/*; the options are explained in the file
2801 Documentation/Networking/ip-sysctl.txt.
2803 Short answer: say Y.
2807 This is code for addressing several networked computers at once,
2808 enlarging your kernel by about 2 kB. You need multicasting if you
2809 intend to participate in the MBONE, a high bandwidth network on top
2810 of the Internet which carries audio and video broadcasts. More
2811 information about the MBONE is on the WWW at
2812 http://www-itg.lbl.gov/mbone/ . Information about the multicast
2813 capabilities of the various network cards is contained in
2814 Documentation/networking/multicast.txt. For most people, it's safe
2818 CONFIG_IP_ADVANCED_ROUTER
2819 If you intend to run your Linux box mostly as a router, i.e. as a
2820 computer that forwards and redistributes network packets, say Y; you
2821 will then be presented with several options that allow more precise
2822 control about the routing process.
2824 The answer to this question won't directly affect the kernel:
2825 answering N will just cause this configure script to skip all the
2826 questions about advanced routing.
2828 Note that your box can only act as a router if you enable IP
2829 forwarding in your kernel; you can do that by saying Y to "/proc
2830 filesystem support" and "Sysctl support" below and executing the
2833 echo "1" > /proc/sys/net/ipv4/ip_forward
2835 at boot time after the /proc filesystem has been mounted.
2837 If you turn on IP forwarding, you will also get the rp_filter, which
2838 automatically rejects incoming packets if the routing table entry
2839 for their source address doesn't match the network interface they're
2840 arriving on. This has security advantages because it prevents the
2841 so-called IP spoofing, however it can pose problems if you use
2842 asymmetric routing (packets from you to a host take a different path
2843 than packets from that host to you) or if you operate a non-routing
2844 host which has several IP addresses on different interfaces. To turn
2847 echo 0 > /proc/sys/net/ipv4/conf/<device>/rp_filter
2849 echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter
2851 If unsure, say N here.
2854 CONFIG_IP_MULTIPLE_TABLES
2855 Normally, a router decides what to do with a received packet based
2856 solely on the packet's final destination address. If you say Y here,
2857 the Linux router will also be able to take the packet's source
2858 address into account. Furthermore, if you also say Y to "IP: use TOS
2859 value as routing key" below, the TOS (Type-Of-Service) field of the
2860 packet can be used for routing decisions as well. In addition, if
2861 you say Y here and to "IP: fast network address translation" below,
2862 the router will also be able to modify source and destination
2863 addresses of forwarded packets.
2865 If you are interested in this, please see the preliminary
2866 documentation at http://www.compendium.com.ar/policy-routing.txt and
2867 ftp://post.tepkom.ru/pub/vol2/Linux/docs/advanced-routing.tex . You
2868 will need supporting software from ftp://ftp.inr.ac.ru/ip-routing/
2872 IP: equal cost multipath
2873 CONFIG_IP_ROUTE_MULTIPATH
2874 Normally, the routing tables specify a single action to be taken in
2875 a deterministic manner for a given packet. If you say Y here
2876 however, it becomes possible to attach several actions to a packet
2877 pattern, in effect specifying several alternative paths to travel
2878 for those packets. The router considers all these paths to be of
2879 equal "cost" and chooses one of them in a non-deterministic fashion
2880 if a matching packet arrives.
2882 IP: use TOS value as routing key
2884 The header of every IP packet carries a TOS (Type of Service) value
2885 with which the packet requests a certain treatment, e.g. low latency
2886 (for interactive traffic), high throughput, or high reliability. If
2887 you say Y here, you will be able to specify different routes for
2888 packets with different TOS values.
2890 IP: use FWMARK value as routing key
2891 CONFIG_IP_ROUTE_FWMARK
2892 If you say Y here, you will be able to specify different routes for
2893 packets with different FWMARK ("firewalling mark") values
2894 (see ipchains(8), "-m" argument).
2896 IP: verbose route monitoring
2897 CONFIG_IP_ROUTE_VERBOSE
2898 If you say Y here, which is recommended, then the kernel will print
2899 verbose messages regarding the routing, for example warnings about
2900 received packets which look strange and could be evidence of an
2901 attack or a misconfigured system somewhere. The information is
2902 handled by the klogd daemon which is responsible for kernel messages
2905 IP: large routing tables
2906 CONFIG_IP_ROUTE_LARGE_TABLES
2907 If you have routing zones that grow to more than about 64 entries,
2908 you may want to say Y here to speed up the routing process.
2910 IP: fast network address translation
2912 If you say Y here, your router will be able to modify source and
2913 destination addresses of packets that pass through it, in a manner
2914 you specify. General information about Network Address Translation
2915 can be gotten from the document
2916 http://www.csn.tu-chemnitz.de/~mha/linux-ip-nat/diplom/nat.html
2918 IP: optimize as router not host
2920 Some Linux network drivers use a technique called copy and checksum
2921 to optimize host performance. For a machine which acts as a router
2922 most of the time and is forwarding most packets to another host this
2923 is however a loss. If you say Y here, copy and checksum will be
2924 switched off. In the future, it may make other changes which
2925 optimize for router operation.
2927 Note that your box can only act as a router if you enable IP
2928 forwarding in your kernel; you can do that by saying Y to "/proc
2929 filesystem support" and "Sysctl support" below and executing the
2932 echo "1" > /proc/sys/net/ipv4/ip_forward
2934 at boot time after the /proc filesystem has been mounted. You can do
2935 that even if you say N here.
2937 If unsure, say N here.
2939 IP: kernel level autoconfiguration
2941 This enables automatic configuration of IP addresses of devices and
2942 of the routing table during kernel boot, based on either information
2943 supplied at the kernel command line or by BOOTP or RARP protocols.
2944 You need to say Y only for diskless machines requiring network
2945 access to boot (in which case you want to say Y to "Root file system
2946 on NFS" as well), because all other machines configure the network
2947 in their startup scripts.
2951 If you want your Linux box to mount its whole root filesystem (the
2952 one containing the directory /) from some other computer over the
2953 net via NFS and you want the IP address of your computer to be
2954 discovered automatically at boot time using the BOOTP protocol (a
2955 special protocol designed for doing this job), say Y here. In case
2956 the boot ROM of your network card was designed for booting Linux and
2957 does BOOTP itself, providing all necessary information on the kernel
2958 command line, you can say N here. If unsure, say Y. Note that if you
2959 want to use BOOTP, a BOOTP server must be operating on your network.
2960 Read Documentation/nfsroot.txt for details.
2964 If you want your Linux box to mount its whole root filesystem (the
2965 one containing the directory /) from some other computer over the
2966 net via NFS and you want the IP address of your computer to be
2967 discovered automatically at boot time using the RARP protocol (an
2968 older protocol which is being obsoleted by BOOTP and DHCP), say Y
2969 here. Note that if you want to use RARP, a RARP server must be
2970 operating on your network. Read Documentation/nfsroot.txt for
2975 Tunneling means encapsulating data of one protocol type within
2976 another protocol and sending it over a channel that understands the
2977 encapsulating protocol. This particular tunneling driver implements
2978 encapsulation of IP within IP, which sounds kind of pointless, but
2979 can be useful if you want to make your (or some other) machine
2980 appear on a different network than it physically is, or to use
2981 mobile-IP facilities (allowing laptops to seamlessly move between
2982 networks without changing their IP addresses; check out
2983 http://anchor.cs.binghamton.edu/~mobileip/LJ/index.html ).
2985 Saying Y to this option will produce two modules ( = code which can
2986 be inserted in and removed from the running kernel whenever you
2987 want). Most people won't need this and can say N.
2989 IP: GRE tunnels over IP
2991 Tunneling means encapsulating data of one protocol type within
2992 another protocol and sending it over a channel that understands the
2993 encapsulating protocol. This particular tunneling driver implements
2994 GRE (Generic Routing Encapsulation) and at this time allows
2995 encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
2996 This driver is useful if the other endpoint is a Cisco router: Cisco
2997 likes GRE much better than the other Linux tunneling driver ("IP:
2998 tunneling" above). In addition, GRE allows multicast redistribution
3001 IP: broadcast GRE over IP
3002 CONFIG_NET_IPGRE_BROADCAST
3003 One application of GRE/IP is to construct a broadcast WAN (Wide Area
3004 Network), which looks like a normal Ethernet LAN (Local Area
3005 Network), but can be distributed all over the Internet. If you want
3006 to do that, say Y here and to "IP: multicast routing" below.
3008 IP: aliasing support
3010 Sometimes it is useful to give several IP addresses to a single
3011 physical network interface (serial port or Ethernet card). The most
3012 common case is that you want to serve different WWW or FTP documents
3013 to the outside depending on which of your host names was used to
3014 connect to you. This is called "multihosting" or "virtual domains"
3015 or "virtual hosting services" and is explained in the
3016 Virtual-Services-HOWTO, available from
3017 http://www.linuxdoc.org/docs.html#howto .
3019 Another scenario would be that there are two logical networks living
3020 on your local Ethernet and you want to access them both with the
3021 same Ethernet card. This can also be done if you say Y here.
3023 The configuration of these alias addresses is done with a special
3024 name syntax explained in Documentation/networking/alias.txt and in
3025 the IP-Alias mini-HOWTO. If you want this, say Y. Most people don't
3028 IP: multicast routing
3030 This is used if you want your machine to act as a router for IP
3031 packets that have several destination addresses. It is needed on the
3032 MBONE, a high bandwidth network on top of the Internet which carries
3033 audio and video broadcasts. In order to do that, you would most
3034 likely run the program mrouted. Information about the multicast
3035 capabilities of the various network cards is contained in
3036 Documentation/networking/multicast.txt. If you haven't heard about
3037 it, you don't need it.
3039 IP: PIM-SM version 1 support
3041 Kernel side support for Sparse Mode PIM (Protocol Independent
3042 Multicast) version 1. This multicast routing protocol is used widely
3043 because Cisco supports it. You need special software to use it
3044 (pimd-v1). Please see http://netweb.usc.edu/pim/ for more
3045 information about PIM.
3047 Say Y if you want to use PIM-SM v1. Note that you can say N here if
3048 you just want to use Dense Mode PIM.
3050 IP: PIM-SM version 2 support
3052 Kernel side support for Sparse Mode PIM version 2. In order to use
3053 this, you need an experimental routing daemon supporting it (pimd or
3054 gated-5). This routing protocol is not used widely, so say N unless
3055 you want to play with it.
3057 PC/TCP compatibility mode
3059 If you have been having difficulties telnetting to your Linux
3060 machine from a DOS system that uses (broken) PC/TCP networking
3061 software (all versions up to OnNet 2.0) over your local Ethernet try
3062 saying Y here. Everyone else says N.
3064 People having problems with NCSA telnet should see the file
3065 linux/Documentation/networking/ncsa-telnet.
3067 Assume subnets are local
3069 Say Y if you are on a subnetted network with all machines connected
3070 by Ethernet segments only, as this option optimizes network access
3071 for this special case. If there are other connections, e.g. SLIP
3072 links, between machines of your IP network, say N. If in doubt,
3073 answer N. The PATH mtu discovery facility will cover most cases
3076 Path MTU Discovery (normally enabled)
3077 CONFIG_PATH_MTU_DISCOVERY
3078 MTU (maximal transfer unit) is the size of the chunks we send out
3079 over the net. "Path MTU Discovery" means that, instead of always
3080 sending very small chunks, we start out sending big ones and if we
3081 then discover that some host along the way likes its chunks smaller,
3082 we adjust to a smaller size. This is good, so most people say Y
3085 However, some DOS software (versions of DOS NCSA telnet and Trumpet
3086 Winsock in PPP mode) is broken and won't be able to connect to your
3087 Linux machine correctly in all cases (especially through a terminal
3088 server) unless you say N here. See
3089 Documentation/networking/ncsa-telnet for the location of fixed NCSA
3090 telnet clients. If in doubt, say Y.
3092 Disable NAGLE algorithm (normally enabled)
3093 CONFIG_TCP_NAGLE_OFF
3094 The NAGLE algorithm works by requiring an acknowledgment before
3095 sending small IP frames (packets). This keeps tiny telnet and
3096 rlogin packets from congesting Wide Area Networks. Most people
3097 strongly recommend to say N here, thereby leaving NAGLE
3098 enabled. Those programs that would benefit from disabling this
3099 facility can do it on a per connection basis themselves.
3101 IP: Allow large windows (not recommended if <16 MB of memory)
3103 On high speed, long distance networks the performance limit on
3104 networking becomes the amount of data the sending machine can buffer
3105 until the other end confirms its reception. (At 45 Mbit/second there
3106 are a lot of bits between New York and London ...). If you say Y
3107 here, bigger buffers can be used which allows larger amounts of data
3108 to be "in flight" at any given time. It also means a user process
3109 can require a lot more memory for network buffers and thus this
3110 option is best used only on machines with 16 MB of memory or higher.
3111 Unless you are using long links with end to end speeds of over 2
3112 Mbit a second or satellite links this option will make no difference
3117 If you say Y here, you will include support for Unix domain sockets;
3118 sockets are the standard Unix mechanism for establishing and
3119 accessing network connections. Many commonly used programs such as
3120 the X Window system and syslog use these sockets even if your
3121 machine is not connected to any network. Unless you are working on
3122 an embedded system or something similar, you therefore definitely
3125 However, the socket support is also available as a module ( = code
3126 which can be inserted in and removed from the running kernel
3127 whenever you want). If you want to compile it as a module, say M
3128 here and read Documentation/modules.txt. The module will be called
3129 unix.o. If you try building this as a module and you have said Y to
3130 "Kernel module loader support" above, be sure to add 'alias net-pf-1
3131 unix' to your /etc/modules.conf file. Note that several important
3132 services won't work correctly if you say M here and then neglect to
3135 Say Y unless you know what you are doing.
3137 The IPv6 protocol (EXPERIMENTAL)
3139 This is experimental support for the next version of the Internet
3140 Protocol: IP version 6 (also called IPng "IP next generation").
3141 Features of this new protocol include: expanded address space,
3142 authentication and privacy, and seamless interoperability with the
3143 current version of IP (IP version 4). For general information about
3144 IPv6, see http://playground.sun.com/pub/ipng/html/ipng-main.html ;
3145 for specific information about IPv6 under Linux read the HOWTO at
3146 http://www.bieringer.de/linux/IPv6/ and the file net/ipv6/README in
3149 If you want to use IPv6, please upgrade to the newest net-tools as
3150 given in Documentation/Changes. You will still be able to do regular
3151 IPv4 networking as well.
3153 This protocol support is also available as a module ( = code which
3154 can be inserted in and removed from the running kernel whenever you
3155 want). The module will be called ipv6.o. If you want to compile it
3156 as a module, say M here and read Documentation/modules.txt.
3158 It is safe to say N here for now.
3160 IPv6: enable EUI-64 token format
3162 6bone, the network of computers using the IPv6 protocol, is moving
3163 to a new aggregatable address format and a new link local address
3164 assignment (EUI-64). Say Y if your site has upgraded already, or
3165 has started to upgrade.
3167 IPv6: disable provider based addresses
3169 Linux tries to operate correctly when your site has moved to EUI-64
3170 only partially. Unfortunately, the two address formats (old:
3171 "provider based" and new: "aggregatable") are incompatible. Say Y if
3172 your site finished the upgrade to EUI-64, and/or you encountered
3173 some problems caused by the presence of two link-local addresses on
3176 IPv6: routing messages via old netlink
3178 You can say Y here to receive routing messages from the IPv6 code
3179 through the old netlink interface. However, a better option is to
3180 say Y to "Kernel/User network link driver" and to "Routing
3185 This is support for the Novell networking protocol, IPX, commonly
3186 used for local networks of Windows machines. You need it if you want
3187 to access Novell NetWare file or print servers using the Linux
3188 Novell client ncpfs (available from
3189 ftp://metalab.unc.edu/pub/Linux/system/filesystems/ ) or from within
3190 the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
3191 http://www.linuxdoc.org/docs.html#howto ). In order to do the
3192 former, you'll also have to say Y to "NCP filesystem support",
3195 IPX is similar in scope to IP, while SPX, which runs on top of IPX,
3196 is similar to TCP. There is also experimental support for SPX in
3197 Linux (see "SPX networking", below).
3199 To turn your Linux box into a fully featured NetWare file server and
3200 IPX router, say Y here and fetch either lwared from
3201 ftp://metalab.unc.edu/pub/Linux/system/network/daemons/ or mars_nwe
3202 from ftp://ftp.gwdg.de/pub/linux/misc/ncpfs . For more information,
3203 read the IPX-HOWTO available from
3204 http://www.linuxdoc.org/docs.html#howto .
3206 General information about how to connect Linux, Windows machines and
3207 Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
3209 The IPX driver would enlarge your kernel by about 16 KB. This driver
3210 is also available as a module ( = code which can be inserted in and
3211 removed from the running kernel whenever you want). The module will
3212 be called ipx.o. If you want to compile it as a module, say M here
3213 and read Documentation/modules.txt. Unless you want to integrate
3214 your Linux box with a local Novell network, say N.
3216 IPX: Full internal IPX network
3218 Every IPX network has an address that identifies it. Sometimes it is
3219 useful to give an IPX "network" address to your Linux box as well
3220 (for example if your box is acting as a file server for different
3221 IPX networks: it will then be accessible from everywhere using the
3222 same address). The way this is done is to create a virtual internal
3223 "network" inside your box and to assign an IPX address to this
3224 network. Say Y here if you want to do this; read the IPX-HOWTO at
3225 http://www.linuxdoc.org/docs.html#howto for details.
3227 The full internal IPX network enables you to allocate sockets on
3228 different virtual nodes of the internal network. This is done by
3229 evaluating the field sipx_node of the socket address given to the
3230 bind call. So applications should always initialize the node field
3231 to 0 when binding a socket on the primary network. In this case the
3232 socket is assigned the default node that has been given to the
3233 kernel when the internal network was created. By enabling the full
3234 internal IPX network the cross-forwarding of packets targeted at
3235 'special' sockets to sockets listening on the primary network is
3236 disabled. This might break existing applications, especially RIP/SAP
3237 daemons. A RIP/SAP daemon that works well with the full internal net
3238 can be found on ftp://ftp.gwdg.de/pub/linux/misc/ncpfs .
3240 If you don't know what you are doing, say N.
3242 IPX: SPX networking (EXPERIMENTAL)
3244 The Sequenced Packet eXchange protocol is a transport layer protocol
3245 built on top of IPX. It is used in Novell NetWare systems for
3246 client-server applications and is similar to TCP (which runs on top
3249 Note that Novell NetWare file sharing does not use SPX; it uses a
3250 protocol called NCP, for which separate Linux support is available
3251 ("NCP filesystem support" below for the client side, and the user
3252 space programs lwared or mars_nwe for the server side).
3254 Say Y here if you have use for SPX; read the IPX-HOWTO at
3255 http://www.linuxdoc.org/docs.html#howto for details.
3257 This driver is also available as a module ( = code which can be
3258 inserted in and removed from the running kernel whenever you want).
3259 The module will be called af_spx.o. If you want to compile it as a
3260 module, say M here and read Documentation/modules.txt.
3262 DECnet networking (EXPERIMENTAL)
3264 The DECnet networking protocol was used in many products made by
3265 Digital (now Compaq). It provides reliable stream and sequenced
3266 packet communications over which run a variety of services similar
3267 to those which run over TCP/IP.
3269 To find some tools to use with the kernel layer support, please
3270 look at Patrick Caulfield's web site:
3271 http://linux.dreamtime.org/decnet/
3273 More detailed documentation is available in the
3274 Documentation/networking/decnet.txt file.
3276 Be sure to say Y to "/proc filesystem support" and "Sysctl support"
3277 below when using DECnet, since you will need sysctl support to aid
3278 in configuration at run time.
3280 The DECnet code is also available as a module ( = code which can be
3281 inserted in and removed from the running kernel whenever you want).
3282 The module is called decnet.o.
3284 DECnet SIOCFIGCONF support
3285 CONFIG_DECNET_SIOCGIFCONF
3286 This option should only be turned on if you are really sure that
3287 you know what you are doing. It can break other applications which
3288 use this system call and the proper way to get the information
3289 provided by this call is to use rtnetlink.
3293 DECnet Router Support (EXPERIMENTAL)
3294 CONFIG_DECNET_ROUTER
3295 Add support for turning your DECnet Endnode into a level 1 or 2
3296 router. This is an unfinished option for developers only. If you do
3297 turn it on, then make sure that you also say Y to "Kernel/User
3298 network link driver" and "Routing messages", since rtnetlink is the
3299 only current method of configuration.
3301 DECnet Raw Socket Support
3303 Add support for the SOCK_RAW type under DECnet. Used by userland
3304 routing programs to receive routing messages from the kernel and
3305 also as a general debugging aid to see what's going on "under the
3310 AppleTalk is the way Apple computers speak to each other on a
3311 network. If your Linux box is connected to such a network and you
3312 want to join the conversation, say Y. You will need to use the
3313 netatalk package so that your Linux box can act as a print and file
3314 server for Macs as well as access AppleTalk printers. Check out
3315 http://threepio.hitchcock.org/cgi-bin/faq/netatalk/faq.pl on the WWW
3316 for details. EtherTalk is the name used for AppleTalk over Ethernet
3317 and the cheaper and slower LocalTalk is AppleTalk over a proprietary
3318 Apple network using serial links. EtherTalk and LocalTalk are fully
3321 General information about how to connect Linux, Windows machines and
3322 Macs is on the WWW at http://www.eats.com/linux_mac_win.html The
3323 NET-3-HOWTO, available from
3324 http://www.linuxdoc.org/docs.html#howto , contains valuable
3325 information as well.
3327 This driver is also available as a module ( = code which can be
3328 inserted in and removed from the running kernel whenever you want).
3329 The module is called appletalk.o. If you want to compile it as a
3330 module, say M here and read Documentation/modules.txt. I hear that
3331 the GNU boycott of Apple is over, so even politically correct people
3332 are allowed to say Y here.
3334 AppleTalk-IP driver support
3336 This allows IP networking for users who only have AppleTalk
3337 networking available. This feature is experimental. With this
3338 driver, you can encapsulate IP inside AppleTalk (e.g. if your Linux
3339 box is stuck on an AppleTalk only network) or decapsulate (e.g. if
3340 you want your Linux box to act as an Internet gateway for a zoo of
3341 AppleTalk connected Macs). Please see the file
3342 Documentation/networking/ipddp.txt for more information.
3344 If you say Y here, the AppleTalk-IP support will be compiled into
3345 the kernel. In this case, you can either use encapsulation or
3346 decapsulation, but not both. With the following two questions, you
3347 decide which one you want.
3349 If you say M here, the AppleTalk-IP support will be compiled as a
3350 module ( = code which can be inserted in and removed from the
3351 running kernel whenever you want, read Documentation/modules.txt).
3352 The module is called ipddp.o. In this case, you will be able to use
3353 both encapsulation and decapsulation simultaneously, by loading two
3354 copies of the module and specifying different values for the module
3357 IP to AppleTalk-IP Encapsulation support
3359 If you say Y here, the AppleTalk-IP code will be able to encapsulate
3360 IP packets inside AppleTalk frames; this is useful if your Linux box
3361 is stuck on an AppleTalk network (which hopefully contains a
3362 decapsulator somewhere). Please see
3363 Documentation/networking/ipddp.txt for more information. If you said
3364 Y to "AppleTalk-IP driver support" above and you say Y here, then
3365 you cannot say Y to "AppleTalk-IP to IP Decapsulation support",
3368 AppleTalk-IP to IP Decapsulation support
3370 If you say Y here, the AppleTalk-IP code will be able to decapsulate
3371 AppleTalk-IP frames to IP packets; this is useful if you want your
3372 Linux box to act as an Internet gateway for an AppleTalk network.
3373 Please see Documentation/networking/ipddp.txt for more information.
3374 If you said Y to "AppleTalk-IP driver support" above and you say Y
3375 here, then you cannot say Y to "IP to AppleTalk-IP Encapsulation
3378 Apple/Farallon LocalTalk PC card support
3380 This allows you to use the AppleTalk PC card to connect to LocalTalk
3381 networks. The card is also known as the Farallon PhoneNet PC card.
3382 If you are in doubt, this card is the one with the 65C02 chip on it.
3383 You also need version 1.3.3 or later of the netatalk package.
3384 This driver is experimental, which means that it may not work.
3385 See the file Documentation/networking/ltpc.txt.
3387 COPS LocalTalk PC card support
3389 This allows you to use COPS AppleTalk cards to connect to LocalTalk
3390 networks. You also need version 1.3.3 or later of the netatalk
3391 package. This driver is experimental, which means that it may not
3392 work. This driver will only work if you choose "AppleTalk DDP"
3393 networking support, above.
3394 Please read the file Documentation/networking/cops.txt.
3396 Dayna firmware support
3398 Support COPS compatible cards with Dayna style firmware (Dayna
3399 DL2000/ Daynatalk/PC (half length), COPS LT-95, Farallon PhoneNET PC
3400 III, Farallon PhoneNET PC II).
3402 Tangent firmware support
3404 Support COPS compatible cards with Tangent style firmware (Tangent
3405 ATB_II, Novell NL-1000, Daystar Digital LT-200.
3407 Amateur Radio support
3409 If you want to connect your Linux box to an amateur radio, answer Y
3410 here. You want to read http://www.tapr.org/tapr/html/pkthome.html
3411 and the HAM-HOWTO and the AX25-HOWTO, both available from
3412 http://www.linuxdoc.org/docs.html#howto .
3414 Note that the answer to this question won't directly affect the
3415 kernel: saying N will just cause this configure script to skip all
3416 the questions about amateur radio.
3418 Amateur Radio AX.25 Level 2
3420 This is the protocol used for computer communication over amateur
3421 radio. It is either used by itself for point-to-point links, or to
3422 carry other protocols such as tcp/ip. To use it, you need a device
3423 that connects your Linux box to your amateur radio. You can either
3424 use a low speed TNC (a Terminal Node Controller acts as a kind of
3425 modem connecting your computer's serial port to your radio's
3426 microphone input and speaker output) supporting the KISS protocol or
3427 one of the various SCC cards that are supported by the generic Z8530
3428 or the DMA SCC driver. Another option are the Baycom modem serial
3429 and parallel port hacks or the sound card modem (supported by their
3430 own drivers). If you say Y here, you also have to say Y to one of
3433 Information about where to get supporting software for Linux amateur
3434 radio as well as information about how to configure an AX.25 port is
3435 contained in the AX25-HOWTO, available from
3436 http://www.linuxdoc.org/docs.html#howto . You might also want to
3437 check out the file Documentation/networking/ax25.txt in the kernel
3438 source. More information about digital amateur radio in general is
3439 on the WWW at http://www.tapr.org/tapr/html/pkthome.html .
3441 This driver is also available as a module ( = code which can be
3442 inserted in and removed from the running kernel whenever you want).
3443 The module will be called ax25.o. If you want to compile it as a
3444 module, say M here and read Documentation/modules.txt.
3446 AX.25 DAMA Slave support
3447 CONFIG_AX25_DAMA_SLAVE
3448 DAMA is a mechanism to prevent collisions when doing AX.25
3449 networking. A DAMA server (called "master") accepts incoming traffic
3450 from clients (called "slaves") and redistributes it to other slaves.
3451 If you say Y here, your Linux box will act as a DAMA slave; this is
3452 transparent in that you don't have to do any special DAMA
3453 configuration. (Linux cannot yet act as a DAMA server.) If unsure,
3456 AX.25 DAMA Master support
3457 CONFIG_AX25_DAMA_MASTER
3458 DAMA is a mechanism to prevent collisions when doing AX.25
3459 networking. A DAMA server (called "master") accepts incoming traffic
3460 from clients (called "slaves") and redistributes it to other
3461 slaves. If you say Y here, your Linux box will act as a DAMA server.
3464 Amateur Radio NET/ROM
3466 NET/ROM is a network layer protocol on top of AX.25 useful for
3469 A comprehensive listing of all the software for Linux amateur radio
3470 users as well as information about how to configure an AX.25 port is
3471 contained in the AX25-HOWTO, available from
3472 http://www.linuxdoc.org/docs.html#howto . You also might want to
3473 check out the file Documentation/networking/ax25.txt. More
3474 information about digital amateur radio in general is on the WWW at
3475 http://www.tapr.org/tapr/html/pkthome.html .
3477 This driver is also available as a module ( = code which can be
3478 inserted in and removed from the running kernel whenever you want).
3479 The module will be called netrom.o. If you want to compile it as a
3480 module, say M here and read Documentation/modules.txt.
3482 Amateur Radio X.25 PLP (Rose)
3484 The Packet Layer Protocol (PLP) is a way to route packets over X.25
3485 connections in general and amateur radio AX.25 connections in
3486 particular, essentially an alternative to NET/ROM.
3488 A comprehensive listing of all the software for Linux amateur radio
3489 users as well as information about how to configure an AX.25 port is
3490 contained in the AX25-HOWTO, available from
3491 http://www.linuxdoc.org/docs.html#howto . You also might want to
3492 check out the file Documentation/networking/ax25.txt. More
3493 information about digital amateur radio in general is on the WWW at
3494 http://www.tapr.org/tapr/html/pkthome.html .
3496 This driver is also available as a module ( = code which can be
3497 inserted in and removed from the running kernel whenever you want).
3498 The module will be called rose.o. If you want to compile it as a
3499 module, say M here and read Documentation/modules.txt.
3501 Serial port KISS driver for AX.25
3503 KISS is a protocol used for the exchange of data between a computer
3504 and a Terminal Node Controller (a small embedded system commonly
3505 used for networking over AX.25 amateur radio connections; it
3506 connects the computer's serial port with the radio's microphone
3507 input and speaker output).
3509 Although KISS is less advanced than the 6pack protocol, it has
3510 the advantage that it is already supported by most modern TNCs
3511 without the need for a firmware upgrade.
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. The module will be
3518 Serial port 6PACK driver for AX.25
3520 6pack is a transmission protocol for the data exchange between your
3521 PC and your TNC (the Terminal Node Controller acts as a kind of
3522 modem connecting your computer's serial port to your radio's
3523 microphone input and speaker output). This protocol can be used as
3524 an alternative to KISS for networking over AX.25 amateur radio
3525 connections, but it has some extended functionality.
3527 Note that this driver is still experimental and might cause
3528 problems. For details about the features and the usage of the
3529 driver, read Documentation/networking/6pack.txt.
3531 If you want to compile this driver as a module ( = code which can be
3532 inserted in and removed from the running kernel whenever you want),
3533 say M here and read Documentation/modules.txt. The module will be
3538 AX.25 is the protocol used for computer communication over amateur
3539 radio. If you say Y here, you will be able to send and receive AX.25
3540 traffic over Ethernet (also called "BPQ AX.25"), which could be
3541 useful if some other computer on your local network has a direct
3542 amateur radio connection.
3544 High-speed (DMA) SCC driver for AX.25
3546 This is a driver for high-speed SCC boards, i.e. those supporting
3547 DMA on one port. You usually use those boards to connect your
3548 computer to an amateur radio modem (such as the WA4DSY 56kbps
3549 modem), in order to send and receive AX.25 packet radio network
3552 Currently, this driver supports Ottawa PI/PI2
3553 (http://hydra.carleton.ca/info/pi2.html ) and Gracilis PackeTwin
3554 (http://www.paccomm.com/gracilis.html ) boards. They are detected
3555 automatically. If you have one of these cards, say Y here and read
3556 the AX25-HOWTO, available from
3557 http://www.linuxdoc.org/docs.html#howto .
3559 This driver can operate multiple boards simultaneously. If you
3560 compile it as a module (by saying M instead of Y), it will be called
3561 dmascc.o. If you don't pass any parameter to the driver, all
3562 possible I/O addresses are probed. This could irritate other devices
3563 that are currently not in use. You may specify the list of addresses
3564 to be probed by "dmascc=addr1,addr2,..." (when compiled into the
3565 kernel image) or "io=addr1,addr2,..." (when loaded as a module). The
3566 network interfaces will be called dmascc0 and dmascc1 for the board
3567 detected first, dmascc2 and dmascc3 for the second one, and so on.
3569 Before you configure each interface with ifconfig, you MUST set
3570 certain parameters, such as channel access timing, clock mode, and
3571 DMA channel. This is accomplished with a small utility program,
3572 dmascc_cfg, available at
3573 http://www.nt.tuwien.ac.at/~kkudielk/Linux/ .
3575 Z8530 SCC driver for AX.25
3577 These cards are used to connect your Linux box to an amateur radio
3578 in order to communicate with other computers. If you want to use
3579 this, read Documentation/networking/z8530drv.txt and the AX25-HOWTO,
3580 available from http://www.linuxdoc.org/docs.html#howto . Also
3581 make sure to say Y to "Amateur Radio AX.25 Level 2" support.
3583 If you want to compile this as a module ( = code which can be
3584 inserted in and removed from the running kernel whenever you want),
3585 say M here and read Documentation/modules.txt. The module will be
3588 additional delay for PA0HZP OptoSCC compatible boards
3590 Say Y here if you experience problems with the SCC driver not
3591 working properly; please read Documentation/networking/z8530drv.txt
3592 for details. If unsure, say N.
3594 #support for TRX that feedback the tx signal to rx
3597 ### Don't know what's going on here.
3601 YAM driver for AX.25
3603 The YAM is a modem for packet radio which connects to the serial
3604 port and includes some of the functions of a Terminal Node
3605 Controller. If you have one of those, say Y here.
3607 If you want to compile this as a module ( = code which can be
3608 inserted in and removed from the running kernel whenever you want),
3609 say M here and read Documentation/modules.txt.
3611 BAYCOM picpar and par96 driver for AX.25
3613 This is a driver for Baycom style simple amateur radio modems that
3614 connect to a parallel interface. The driver supports the picpar and
3615 par96 designs. To configure the driver, use the sethdlc utility
3616 available in the standard ax25 utilities package. For information on
3617 the modems, see http://www.baycom.de and the file
3618 Documentation/networking/baycom.txt.
3620 If you want to compile this driver as a module ( = code which can be
3621 inserted in and removed from the running kernel whenever you want),
3622 say M here and read Documentation/modules.txt. This is recommended.
3623 The module will be called baycom_par.o.
3625 BAYCOM EPP driver for AX.25
3627 This is a driver for Baycom style simple amateur radio modems that
3628 connect to a parallel interface. The driver supports the EPP
3629 designs. To configure the driver, use the sethdlc utility available
3630 in the standard ax25 utilities package. For information on the
3631 modems, see http://www.baycom.de and the file
3632 Documentation/networking/baycom.txt.
3634 If you want to compile this driver as a module ( = code which can be
3635 inserted in and removed from the running kernel whenever you want),
3636 say M here and read Documentation/modules.txt. This is recommended.
3637 The module will be called baycom_par.o.
3639 BAYCOM ser12 full duplex driver for AX.25
3640 CONFIG_BAYCOM_SER_FDX
3641 This is one of two drivers for Baycom style simple amateur radio
3642 modems that connect to a serial interface. The driver supports the
3643 ser12 design in full duplex mode. In addition, it allows the
3644 baudrate to be set between 300 and 4800 baud (however not all modems
3645 support all baudrates). This is the preferred driver. The next
3646 driver, "BAYCOM ser12 half duplex driver for AX.25" is the old
3647 driver and still provided in case this driver does not work with
3648 your serial interface chip. To configure the driver, use the sethdlc
3649 utility available in the standard ax25 utilities package. For
3650 information on the modems, see http://www.baycom.de and
3651 Documentation/networking/baycom.txt.
3653 If you want to compile this driver as a module ( = code which can be
3654 inserted in and removed from the running kernel whenever you want),
3655 say M here and read Documentation/modules.txt. This is recommended.
3656 The module will be called baycom_ser_fdx.o.
3658 BAYCOM ser12 half duplex driver for AX.25
3659 CONFIG_BAYCOM_SER_HDX
3660 This is one of two drivers for Baycom style simple amateur radio
3661 modems that connect to a serial interface. The driver supports the
3662 ser12 design in full duplex mode. This is the old driver. It is
3663 still provided in case your serial interface chip does not work with
3664 the full duplex driver. This driver is depreciated. To configure the
3665 driver, use the sethdlc utility available in the standard ax25
3666 utilities package. For information on the modems, see
3667 http://www.baycom.de and Documentation/networking/baycom.txt.
3669 If you want to compile this driver as a module ( = code which can be
3670 inserted in and removed from the running kernel whenever you want),
3671 say M here and read Documentation/modules.txt. This is recommended.
3672 The module will be called baycom_ser_hdx.o.
3674 Sound card modem driver for AX.25
3676 This experimental driver allows a standard Sound Blaster or
3677 WindowsSoundSystem compatible sound card to be used as a packet
3678 radio modem (NOT as a telephone modem!), to send digital traffic
3681 To configure the driver, use the sethdlc, smdiag and smmixer
3682 utilities available in the standard ax25 utilities package. For
3683 information on how to key the transmitter, see
3684 http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html and
3685 Documentation/networking/soundmodem.txt.
3687 If you want to compile this driver as a module ( = code which can be
3688 inserted in and removed from the running kernel whenever you want),
3689 say M here and read Documentation/modules.txt. This is recommended.
3690 The module will be called soundmodem.o.
3692 Sound card modem support for Sound Blaster and compatible cards
3693 CONFIG_SOUNDMODEM_SBC
3694 This option enables the soundmodem driver to use Sound Blaster and
3695 compatible cards. If you have a dual mode card (i.e. a WSS cards
3696 with a Sound Blaster emulation) you should say N here and Y to
3697 "Sound card modem support for WSS and Crystal cards", below, because
3698 this usually results in better performance. This option also
3699 supports SB16/32/64 in full duplex mode.
3701 Sound card modem support for WSS and Crystal cards
3702 CONFIG_SOUNDMODEM_WSS
3703 This option enables the soundmodem driver to use WindowsSoundSystem
3704 compatible cards. These cards feature a codec chip from either
3705 Analog Devices (such as AD1848, AD1845, AD1812) or Crystal
3706 Semiconductors (such as CS4248, CS423x). This option also supports
3707 the WSS full duplex operation which currently works with Crystal
3708 CS423x chips. If you don't need full duplex operation, do not enable
3709 it to save performance.
3711 Sound card modem support for 1200 baud AFSK modulation
3712 CONFIG_SOUNDMODEM_AFSK1200
3713 This option enables the soundmodem driver 1200 baud AFSK modem,
3714 compatible to popular modems using TCM3105 or AM7911. The
3715 demodulator requires about 12% of the CPU power of a Pentium 75 CPU
3718 Sound card modem support for 2400 baud AFSK modulation (7.3728MHz crystal)
3719 CONFIG_SOUNDMODEM_AFSK2400_7
3720 This option enables the soundmodem driver 2400 baud AFSK modem,
3721 compatible to TCM3105 modems (over-)clocked with a 7.3728MHz
3722 crystal. Note that the availability of this driver does _not_ imply
3723 that I recommend building such links. It is only here since users
3724 especially in eastern Europe have asked me to do so. In fact this
3725 modulation scheme has many disadvantages, mainly its incompatibility
3726 with many transceiver designs and the fact that the TCM3105 (if
3727 used) is operated widely outside its specifications.
3729 Sound card modem support for 2400 baud AFSK modulation (8MHz crystal)
3730 CONFIG_SOUNDMODEM_AFSK2400_8
3731 This option enables the soundmodem driver 2400 baud AFSK modem,
3732 compatible to TCM3105 modems (over-)clocked with an 8MHz crystal.
3733 Note that the availability of this driver does _not_ imply that I
3734 recommend building such links. It is only here since users
3735 especially in eastern Europe have asked me to do so. In fact this
3736 modulation scheme has many disadvantages, mainly its incompatibility
3737 with many transceiver designs and the fact that the TCM3105 (if
3738 used) is operated widely outside its specifications.
3740 Sound card modem support for 2666 baud AFSK modulation
3741 CONFIG_SOUNDMODEM_AFSK2666
3742 This option enables the soundmodem driver 2666 baud AFSK modem.
3743 This modem is experimental, and not compatible to anything
3746 Sound card modem support for 4800 baud 8PSK modulation
3747 CONFIG_SOUNDMODEM_PSK4800
3748 This option enables the soundmodem driver 4800 baud 8PSK modem.
3749 This modem is experimental, and not compatible to anything
3752 Sound card modem support for 4800 baud HAPN-1 modulation
3753 CONFIG_SOUNDMODEM_HAPN4800
3754 This option enables the soundmodem driver 4800 baud HAPN-1
3755 compatible modem. This modulation seems to be widely used 'down
3756 under' and in the Netherlands. Here, nobody uses it, so I could not
3757 test if it works. It is compatible to itself, however :-)
3759 Sound card modem support for 9600 baud FSK G3RUH modulation
3760 CONFIG_SOUNDMODEM_FSK9600
3761 This option enables the soundmodem driver 9600 baud FSK modem,
3762 compatible to the G3RUH standard. The demodulator requires about 4%
3763 of the CPU power of a Pentium 75 CPU per channel. You can say Y to
3764 both 1200 baud AFSK and 9600 baud FSK if you want (but obviously you
3765 can only use one protocol at a time, depending on what the other end
3768 CCITT X.25 Packet Layer (EXPERIMENTAL)
3770 X.25 is a set of standardized network protocols, similar in scope to
3771 frame relay; the one physical line from your box to the X.25 network
3772 entry point can carry several logical point-to-point connections
3773 (called "virtual circuits") to other computers connected to the X.25
3774 network. Governments, banks, and other organizations tend to use it
3775 to connect to each other or to form Wide Area Networks (WANs). Many
3776 countries have public X.25 networks. X.25 consists of two
3777 protocols: the higher level Packet Layer Protocol (PLP) (say Y here
3778 if you want that) and the lower level data link layer protocol LAPB
3779 (say Y to "LAPB Data Link Driver" below if you want that).
3781 You can read more about X.25 at http://www.sangoma.com/x25.htm and
3782 http://www.cisco.com/univercd/data/doc/software/11_0/rpcg/cx25.htm .
3783 Information about X.25 for Linux is contained in the files
3784 Documentation/networking/x25.txt and
3785 Documentation/networking/x25-iface.txt.
3787 One connects to an X.25 network either with a dedicated network card
3788 using the X.21 protocol (not yet supported by Linux) or one can do
3789 X.25 over a standard telephone line using an ordinary modem (say Y
3790 to "X.25 async driver" below) or over Ethernet using an ordinary
3791 Ethernet card and either the 802.2 LLC protocol (say Y to "802.2
3792 LLC" below) or LAPB over Ethernet (say Y to "LAPB Data Link Driver"
3793 and "LAPB over Ethernet driver" below).
3795 If you want to compile this driver as a module ( = code which can be
3796 inserted in and removed from the running kernel whenever you want),
3797 say M here and read Documentation/modules.txt. The module will be
3798 called x25.o. If unsure, say N.
3800 LAPB Data Link Driver (EXPERIMENTAL)
3802 Link Access Procedure, Balanced (LAPB) is the data link layer (i.e.
3803 the lower) part of the X.25 protocol. It offers a reliable
3804 connection service to exchange data frames with one other host, and
3805 it is used to transport higher level protocols (mostly X.25 Packet
3806 Layer, the higher part of X.25, but others are possible as well).
3807 Usually, LAPB is used with specialized X.21 network cards, but Linux
3808 currently supports LAPB only over Ethernet connections. If you want
3809 to use LAPB connections over Ethernet, say Y here and to "LAPB over
3810 Ethernet driver" below. Read
3811 Documentation/networking/lapb-module.txt for technical details.
3813 If you want to compile this driver as a module though ( = code which
3814 can be inserted in and removed from the running kernel whenever you
3815 want), say M here and read Documentation/modules.txt. The module
3816 will be called lapb.o. If unsure, say N.
3818 802.2 LLC (EXPERIMENTAL)
3820 This is a Logical Link Layer protocol used for X.25 connections over
3821 Ethernet, using ordinary Ethernet cards.
3823 Bridging (EXPERIMENTAL)
3825 If you say Y here, then your Linux box will be able to act as an
3826 Ethernet bridge, which means that the different Ethernet segments it
3827 is connected to will appear as one Ethernet to the participants.
3828 Several such bridges can work together to create even larger
3829 networks of Ethernets using the IEEE802.1 spanning tree algorithm.
3830 As this is a standard, Linux bridges will interwork properly with
3831 other third party bridge products.
3833 In order to use this, you'll need the bridge configuration tools
3834 available from ftp://shadow.cabi.net/pub/Linux . Please read the
3835 Bridge mini-HOWTO for more information. Note that if your box acts
3836 as a bridge, it probably contains several Ethernet devices, but the
3837 kernel is not able to recognize more than one at boot time without
3838 help; for details read the Ethernet-HOWTO, available from
3839 http://www.linuxdoc.org/docs.html#howto .
3841 The Bridging code is still in test. If unsure, say N.
3845 The Packet protocol is used by applications which communicate
3846 directly with network devices without an intermediate network
3847 protocol implemented in the kernel, e.g. tcpdump. If you want them
3850 This driver is also available as a module called af_packet.o ( =
3851 code which can be inserted in and removed from the running kernel
3852 whenever you want). If you want to compile it as a module, say M
3853 here and read Documentation/modules.txt; if you use modprobe or
3854 kmod, you may also want to add "alias net-pf-17 af_packet" to
3859 Packet socket: mmapped IO
3861 If you say Y here, the Packet protocol driver will use an IO
3862 mechanism that results in faster communication.
3866 Kernel/User network link driver
3868 This driver allows for two-way communication between the kernel and
3869 user processes; the user processes communicate with the kernel by
3870 reading from and writing to character special files in the /dev
3871 directory having major mode 36.
3873 So far, the kernel uses this feature to publish some network related
3874 information if you say Y to "Routing messages", below. You also need
3875 to say Y here if you want to use arpd, a daemon that helps keep the
3876 internal ARP cache (a mapping between IP addresses and hardware
3877 addresses on the local network) small. The ethertap device, which
3878 lets user space programs read and write raw Ethernet frames, also
3879 needs the network link driver.
3881 This driver is also available as a module called netlink_dev.o ( =
3882 code which can be inserted in and removed from the running kernel
3883 whenever you want). If you want to compile it as a module, say M
3884 here and read Documentation/modules.txt.
3890 If you say Y here and create a character special file /dev/route
3891 with major number 36 and minor number 0 using mknod ("man mknod"),
3892 you (or some user space utility) can read some network related
3893 routing information from that file. Everything you write to that
3894 file will be discarded.
3896 Netlink device emulation
3898 This is a backward compatibility option, choose Y for now.
3899 This option will be removed soon.
3901 Asynchronous Transfer Mode (ATM)
3903 ATM is a high-speed networking technology for Local Area Networks
3904 and Wide Area Networks. It uses a fixed packet size and is
3905 connection oriented, allowing for the negotiation of minimum
3906 bandwidth requirements.
3908 In order to participate in an ATM network, your Linux box needs an
3909 ATM networking card. If you have that, say Y here and to the driver
3910 of your ATM card below.
3912 Note that you need a set of user-space programs to actually make use
3913 of ATM. See the file Documentation/networking/atm.txt for further
3916 Classical IP over ATM
3918 Classical IP over ATM for PVCs and SVCs, supporting InARP and
3919 ATMARP. Typically you will either use LAN Emulation (LANE) or
3920 Classical IP to communicate with other IP hosts on your ATM network.
3922 Do NOT send ICMP if no neighbour
3923 CONFIG_ATM_CLIP_NO_ICMP
3924 Normally, an "ICMP host unreachable" message is sent if a neighbour
3925 cannot be reached because there is no VC to it in the kernel's
3926 ATMARP table. This may cause problems when ATMARP table entries are
3927 briefly removed during revalidation. If you say Y here, packets to
3928 such neighbours are silently discarded instead.
3930 LAN Emulation (LANE) support
3932 LAN Emulation emulates services of existing LANs across an ATM
3933 network. Besides operating as a normal ATM end station client, Linux
3934 LANE client can also act as an proxy client bridging packets between
3935 ELAN and Ethernet segments. You need LANE if you want to try MPOA.
3937 Multi-Protocol Over ATM (MPOA) support
3939 Multi-Protocol Over ATM allows ATM edge devices such as routers,
3940 bridges and ATM attached hosts establish direct ATM VCs across
3941 subnetwork boundaries. These shortcut connections bypass routers
3942 enhancing overall network performance.
3946 ATM over TCP driver. Useful mainly for development and for
3947 experiments. If unsure, say N.
3949 Efficient Networks ENI155P
3951 Driver for the Efficient Networks ENI155p series and SMC ATM
3952 Power155 155 Mbps ATM adapters. Both, the versions with 512kB and
3953 2MB on-board RAM (Efficient calls them "C" and "S", respectively),
3954 and the FPGA and the ASIC Tonga versions of the board are supported.
3955 The driver works with MMF (-MF or ...F) and UTP-5 (-U5 or ...D)
3958 Enable extended debugging
3959 CONFIG_ATM_ENI_DEBUG
3960 Extended debugging records various events and displays that list
3961 when an inconsistency is detected. This mechanism is faster than
3962 generally using printks, but still has some impact on performance.
3963 Note that extended debugging may create certain race conditions
3964 itself. Enable this ONLY if you suspect problems with the driver.
3966 Fine-tune burst settings
3967 CONFIG_ATM_ENI_TUNE_BURST
3968 In order to obtain good throughput, the ENI NIC can transfer
3969 multiple words of data per PCI bus access cycle. Such a multi-word
3970 transfer is called a burst.
3972 The default settings for the burst sizes are suitable for most PCI
3973 chipsets. However, in some cases, large bursts may overrun buffers
3974 in the PCI chipset and cause data corruption. In such cases, large
3975 bursts must be disabled and only (slower) small bursts can be used.
3976 The burst sizes can be set independently in the send (TX) and
3977 receive (RX) direction.
3979 Note that enabling many different burst sizes in the same direction
3980 may increase the cost of setting up a transfer such that the
3981 resulting throughput is lower than when using only the largest
3982 available burst size.
3984 Also, sometimes larger bursts lead to lower throughput, e.g. on an
3985 Intel 440FX board, a drop from 135 Mbps to 103 Mbps was observed
3986 when going from 8W to 16W bursts.
3988 Enable 16W TX bursts (discouraged)
3989 CONFIG_ATM_ENI_BURST_TX_16W
3990 Burst sixteen words at once in the send direction. This may work
3991 with recent PCI chipsets, but is known to fail with older chipsets.
3993 Enable 8W TX bursts (recommended)
3994 CONFIG_ATM_ENI_BURST_TX_8W
3995 Burst eight words at once in the send direction. This is the default
3998 Enable 4W TX bursts (optional)
3999 CONFIG_ATM_ENI_BURST_TX_4W
4000 Burst four words at once in the send direction. You may want to try
4001 this if you have disabled 8W bursts. Enabling 4W if 8W is also set
4002 may or may not improve throughput.
4004 Enable 2W TX bursts (optional)
4005 CONFIG_ATM_ENI_BURST_TX_2W
4006 Burst two words at once in the send direction. You may want to try
4007 this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or 8W
4008 are also set may or may not improve throughput.
4010 Enable 16W RX bursts (discouraged)
4011 CONFIG_ATM_ENI_BURST_RX_16W
4012 Burst sixteen words at once in the receive direction. This may work
4013 with recent PCI chipsets, but is known to fail with older chipsets.
4015 Enable 8W RX bursts (discouraged)
4016 CONFIG_ATM_ENI_BURST_RX_8W
4017 Burst eight words at once in the receive direction. This may work
4018 with recent PCI chipsets, but is known to fail with older chipsets,
4019 such as the Intel Neptune series.
4021 Enable 4W RX bursts (recommended)
4022 CONFIG_ATM_ENI_BURST_RX_4W
4023 Burst four words at once in the receive direction. This is the
4024 default setting. Enabling 4W if 8W is also set may or may not
4027 Enable 2W RX bursts (optional)
4028 CONFIG_ATM_ENI_BURST_RX_2W
4029 Burst two words at once in the receive direction. You may want to
4030 try this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or
4031 8W are also set may or may not improve throughput.
4033 ZeitNet ZN1221/ZN1225
4035 Driver for the ZeitNet ZN1221 (MMF) and ZN1225 (UTP-5) 155 Mbps ATM
4038 Enable extended debugging
4039 CONFIG_ATM_ZATM_DEBUG
4040 Extended debugging records various events and displays that list
4041 when an inconsistency is detected. This mechanism is faster than
4042 generally using printks, but still has some impact on performance.
4043 Note that extended debugging may create certain race conditions
4044 itself. Enable this ONLY if you suspect problems with the driver.
4046 Enable usec resolution timestamps
4047 CONFIG_ATM_ZATM_EXACT_TS
4048 The uPD98401 SAR chip supports a high-resolution timer (approx. 30
4049 MHz) that is used for very accurate reception timestamps. Because
4050 that timer overflows after 140 seconds, and also to avoid timer
4051 drift, time measurements need to be periodically synchronized with
4052 the normal system time. Enabling this feature will add some general
4053 overhead for timer synchronization and also per-packet overhead for
4056 IDT 77201/11 (NICStAR) (ForeRunnerLE)
4058 The NICStAR chipset family is used in a large number of ATM NICs for
4059 25 and for 155 Mbps, including IDT cards and the Fore ForeRunnerLE
4062 ForeRunner LE155 PHYsical layer
4063 CONFIG_ATM_NICSTAR_USE_SUNI
4064 Support for the S-UNI and compatible PHYsical layer chips. These are
4065 found in most 155Mbps NICStAR based ATM cards, namely in the
4066 ForeRunner LE155 cards. This driver provides detection of cable
4067 removal and reinsertion and provides some statistics. This driver
4068 doesn't have removal capability when compiled as a module, so if you
4069 need that capability don't include S-UNI support (it's not needed to
4070 make the card work).
4072 ForeRunner LE25 PHYsical layer
4073 CONFIG_ATM_NICSTAR_USE_IDT77105
4074 Support for the PHYsical layer chip in ForeRunner LE25 cards. In
4075 addition to cable removal/reinsertion detection, this driver allows
4076 you to control the loopback mode of the chip via a dedicated IOCTL.
4077 This driver is required for proper handling of temporary carrier
4078 loss, so if you have a 25Mbps NICStAR based ATM card you must say Y.
4080 Madge Ambassador (Collage PCI 155 Server)
4081 CONFIG_ATM_AMBASSADOR
4082 This is a driver for ATMizer based ATM card produced by Madge
4083 Networks Ltd. Say Y (or M to compile as a module named ambassador.o)
4084 here if you have one of these cards.
4086 Enable debugging messages
4087 CONFIG_ATM_AMBASSADOR_DEBUG
4088 Somewhat useful debugging messages are available. The choice of
4089 messages is controlled by a bitmap. This may be specified as a
4090 module argument (kernel command line argument as well?), changed
4091 dynamically using an ioctl (not yet) or changed by sending the
4092 string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
4093 drivers/atm/ambassador.h for the meanings of the bits in the mask.
4095 When active, these messages can have a significant impact on the
4096 speed of the driver, and the size of your syslog files! When
4097 inactive, they will have only a modest impact on performance.
4099 Madge Horizon [Ultra] (Collage PCI 25 and Collage PCI 155 Client)
4101 This is a driver for the Horizon chipset ATM adapter cards once
4102 produced by Madge Networks Ltd. Say Y (or M to compile as a module
4103 named horizon.o) here if you have one of these cards.
4105 Enable debugging messages
4106 CONFIG_ATM_HORIZON_DEBUG
4107 Somewhat useful debugging messages are available. The choice of
4108 messages is controlled by a bitmap. This may be specified as a
4109 module argument (kernel command line argument as well?), changed
4110 dynamically using an ioctl (not yet) or changed by sending the
4111 string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
4112 drivers/atm/horizon.h for the meanings of the bits in the mask.
4114 When active, these messages can have a significant impact on the
4115 speed of the driver, and the size of your syslog files! When
4116 inactive, they will have only a modest impact on performance.
4118 Interphase ATM PCI x575/x525/x531
4120 This is a driver for the Interphase (i)ChipSAR adapter cards
4121 which include a variety of variants in term of the size of the
4122 control memory (128K-1KVC, 512K-4KVC), the size of the packet
4123 memory (128K, 512K, 1M), and the PHY type (Single/Multi mode OC3,
4124 UTP155, UTP25, DS3 and E3). Go to:
4125 www.iphase.com/products/ClassSheet.cfm?ClassID=ATM
4126 for more info about the cards. Say Y (or M to compile as a module
4127 named iphase.o) here if you have one of these cards.
4129 See the file Documentation/networking/iphase.txt for further
4132 Enable debugging messages
4134 Somewhat useful debugging messages are available. The choice of
4135 messages is controlled by a bitmap. This may be specified as a
4136 module argument (kernel command line argument as well?), changed
4137 dynamically using an ioctl (Get the debug utility, iadbg, from
4138 ftp.iphase.com/pub/atm/pci). See the file drivers/atm/iphase.h
4139 for the meanings of the bits in the mask.
4141 When active, these messages can have a significant impact on the
4142 speed of the driver, and the size of your syslog files! When
4143 inactive, they will have only a modest impact on performance.
4147 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CDROM or
4148 any other SCSI device under Linux, say Y and make sure that you know
4149 the name of your SCSI host adapter (the card inside your computer
4150 that "speaks" the SCSI protocol, also called SCSI controller),
4151 because you will be asked for it.
4153 You also need to say Y here if you want support for the parallel
4154 port version of the 100 MB IOMEGA ZIP drive.
4156 Please read the SCSI-HOWTO, available from
4157 http://www.linuxdoc.org/docs.html#howto . The
4158 SCSI-Programming-HOWTO contains information about how to add or
4159 remove an SCSI device from a running Linux machine without
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 scsi_mod.o. If you want to compile it as a
4165 module, say M here and read Documentation/modules.txt and
4166 Documentation/scsi.txt. However, do not compile this as a module if
4167 your root filesystem (the one containing the directory /) is located
4172 If you want to use a SCSI hard disk or the SCSI or parallel port
4173 version of the IOMEGA ZIP drive under Linux, say Y and read the
4174 SCSI-HOWTO, the Disk-HOWTO and the Multi-Disk-HOWTO, available from
4175 http://www.linuxdoc.org/docs.html#howto . This is NOT for SCSI
4178 This driver is also available as a module ( = code which can be
4179 inserted in and removed from the running kernel whenever you want).
4180 The module will be called sd_mod.o. If you want to compile it as a
4181 module, say M here and read Documentation/modules.txt and
4182 Documentation/scsi.txt. Do not compile this driver as a module if
4183 your root filesystem (the one containing the directory /) is located
4184 on a SCSI disk. In this case, do not compile the driver for your
4185 SCSI host adapter (below) as a module either.
4188 CONFIG_SD_EXTRA_DEVS
4189 This controls the amount of additional space allocated in tables for
4190 drivers that are loaded as modules after the kernel is booted. In
4191 the event that the SCSI core itself was loaded as a module, this this
4192 value is the number of additional disks that can be loaded after the
4193 first host driver is loaded.
4195 Admittedly this isn't pretty, but there are tons of race conditions
4196 involved with resizing the internal arrays on the fly. Someday this
4197 flag will go away, and everything will work automatically.
4201 If you want to use a SCSI tape drive under Linux, say Y and read the
4202 SCSI-HOWTO, available from
4203 http://www.linuxdoc.org/docs.html#howto , and
4204 drivers/scsi/README.st in the kernel source. This is NOT for SCSI
4207 This driver is also available as a module ( = code which can be
4208 inserted in and removed from the running kernel whenever you want).
4209 The module will be called st.o. If you want to compile it as a
4210 module, say M here and read Documentation/modules.txt and
4211 Documentation/scsi.txt .
4214 CONFIG_ST_EXTRA_DEVS
4215 This controls the amount of additional space allocated in tables for
4216 drivers that are loaded as modules after the kernel is booted. In the
4217 event that the SCSI core itself was loaded as a module, this this value
4218 is the number of additional tape devices that can be loaded after the
4219 first host driver is loaded.
4221 Admittedly this isn't pretty, but there are tons of race conditions
4222 involved with resizing the internal arrays on the fly. Someday this
4223 flag will go away, and everything will work automatically.
4227 If you want to use a SCSI CDROM under Linux, say Y and read the
4228 SCSI-HOWTO and the CDROM-HOWTO at
4229 http://www.linuxdoc.org/docs.html#howto . Also make sure to say Y
4230 or M to "ISO 9660 CDROM filesystem support" later.
4232 This driver is also available as a module ( = code which can be
4233 inserted in and removed from the running kernel whenever you want).
4234 The module will be called sr_mod.o. If you want to compile it as a
4235 module, say M here and read Documentation/modules.txt and
4236 Documentation/scsi.txt .
4239 CONFIG_SR_EXTRA_DEVS
4240 This controls the amount of additional space allocated in tables for
4241 drivers that are loaded as modules after the kernel is booted. In the
4242 event that the SCSI core itself was loaded as a module, this this value
4243 is the number of additional CDROMs that can be loaded after the first
4244 host driver is loaded.
4246 Admittedly this isn't pretty, but there are tons of race conditions
4247 involved with resizing the internal arrays on the fly. Someday this
4248 flag will go away, and everything will work automatically.
4250 Enable vendor-specific extensions (for SCSI CDROM)
4251 CONFIG_BLK_DEV_SR_VENDOR
4252 This enables the usage of vendor specific SCSI commands. This is
4253 required to support multisession CDs with old NEC/TOSHIBA cdrom
4254 drives (and HP Writers). If you have such a drive and get the first
4255 session only, try saying Y here; everybody else says N.
4257 SCSI generic support
4259 If you want to use SCSI scanners, synthesizers or CD-writers or just
4260 about anything having "SCSI" in its name other than hard disks,
4261 CDROMs or tapes, say Y here. These won't be supported by the kernel
4262 directly, so you need some additional software which knows how to
4263 talk to these devices using the SCSI protocol. For CD-writers, you
4264 would need the program cdwrite, available from
4265 ftp://metalab.unc.edu/pub/Linux/utils/disk-management ; for other
4266 devices, it's possible that you'll have to write the driver software
4267 yourself, so have a look at the SCSI-HOWTO and at the
4268 SCSI-Programming-HOWTO, both available from
4269 http://www.linuxdoc.org/docs.html#howto . Please read the file
4270 Documentation/scsi-generic.txt for more information.
4272 If you want to compile this as a module ( = code which can be
4273 inserted in and removed from the running kernel whenever you want),
4274 say M here and read Documentation/modules.txt and
4275 Documentation/scsi.txt. The module will be called sg.o. If unsure,
4278 Debug new queueing code for SCSI
4279 CONFIG_SCSI_DEBUG_QUEUES
4280 This option turns on a lot of additional consistency checking for the new
4281 queueing code. This will adversely affect performance, but it is likely
4282 that bugs will be caught sooner if this is turned on. This will typically
4283 cause the kernel to panic if an error is detected, but it would have probably
4284 crashed if the panic weren't there. Comments/questions/problems to
4285 linux-scsi mailing list please. See http://www.andante.org/scsi_queue.html
4286 for more uptodate information.
4288 Probe all LUNs on each SCSI device
4289 CONFIG_SCSI_MULTI_LUN
4290 If you have a SCSI device that supports more than one LUN (Logical
4291 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
4292 can say Y here to force the SCSI driver to probe for multiple LUNs.
4293 A SCSI device with multiple LUNs acts logically like multiple SCSI
4294 devices. The vast majority of SCSI devices have only one LUN, and
4295 so most people can say N here and should in fact do so, because it
4298 Verbose SCSI error reporting (kernel size +=12K)
4299 CONFIG_SCSI_CONSTANTS
4300 The error messages regarding your SCSI hardware will be easier to
4301 understand if you say Y here; it will enlarge your kernel by about
4302 12 KB. If in doubt, say Y.
4304 SCSI logging facility
4306 This turns on a logging facility that can be used to debug a number
4307 of SCSI related problems.
4309 If you say Y here, no logging output will appear by default, but you
4310 can enable logging by saying Y to "/proc filesystem support" and
4311 "Sysctl support" below and executing the command
4313 echo "scsi log token [level]" > /proc/scsi/scsi
4315 at boot time after the /proc filesystem has been mounted.
4317 There are a number of things that can be used for 'token' (you can
4318 find them in the source: drivers/scsi/scsi.c), and this allows you
4319 to select the types of information you want, and the level allows
4320 you to select the level of verbosity.
4322 If you say N here, it may be harder to track down some types of SCSI
4323 problems. If you say Y here your kernel will be somewhat larger, but
4324 there should be no noticeable performance impact as long as you have
4327 AdvanSys SCSI support
4328 CONFIG_SCSI_ADVANSYS
4329 This is a driver for all SCSI host adapters manufactured by
4330 AdvanSys. It is documented in the kernel source in
4331 drivers/scsi/advansys.c.
4333 This driver is also available as a module ( = code which can be
4334 inserted in and removed from the running kernel whenever you want).
4335 If you want to compile it as a module, say M here and read
4336 Documentation/modules.txt. The module will be called advansys.o.
4338 Adaptec AHA152X/2825 support
4340 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
4341 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
4342 must be manually specified in this case.
4344 It is explained in section 3.3 of the SCSI-HOWTO, available from
4345 http://www.linuxdoc.org/docs.html#howto . You might also want to
4346 read the comments at the top of drivers/scsi/aha152x.c.
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 aha152x.o. If you want to compile it as a
4351 module, say M here and read Documentation/modules.txt.
4353 Adaptec AHA1542 support
4355 This is support for a SCSI host adapter. It is explained in section
4356 3.4 of the SCSI-HOWTO, available from
4357 http://www.linuxdoc.org/docs.html#howto . Note that Trantor was
4358 purchased by Adaptec, and some former Trantor products are being
4359 sold under the Adaptec name. If it doesn't work out of the box, you
4360 may have to change some settings in drivers/scsi/aha1542.h.
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 Adaptec AHA1740 support
4369 This is support for a SCSI host adapter. It is explained in section
4370 3.5 of the SCSI-HOWTO, available from
4371 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
4372 of the box, you may have to change some settings in
4373 drivers/scsi/aha1740.h.
4375 This driver is also available as a module ( = code which can be
4376 inserted in and removed from the running kernel whenever you want).
4377 The module will be called aha1740.o. If you want to compile it as a
4378 module, say M here and read Documentation/modules.txt.
4380 Adaptec AIC7xxx chipset SCSI controller support
4382 This is support for the various aic7xxx based Adaptec SCSI
4383 controllers. These include the 274x EISA cards; 284x VLB cards;
4384 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
4385 motherboard based SCSI controllers from Adaptec. It does not support
4386 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
4387 support them. It does not support the 2920 cards from Adaptec that
4388 use the Future Domain SCSI controller chip. For those cards, you
4389 need the "Future Domain 16xx SCSI support" driver.
4391 In general, if the controller is based on an Adaptec SCSI controller
4392 chip from the aic777x series or the aic78xx series, this driver
4393 should work. The only exception is the 7810 which is specifically
4394 not supported (that's the RAID controller chip on the AAA-13x
4397 Note that the AHA2920 SCSI host adapter is *not* supported by this
4398 driver; choose "Future Domain 16xx SCSI support" instead if you have
4401 Information on the configuration options for this controller can be
4402 found by checking the help file for each of the available
4403 configuration options. You should read drivers/scsi/README.aic7xxx
4404 at a minimum before contacting the maintainer with any questions.
4405 The SCSI-HOWTO, available from
4406 http://www.linuxdoc.org/docs.html#howto , can also be of great
4409 If you want to compile this driver as a module ( = code which can be
4410 inserted in and removed from the running kernel whenever you want),
4411 say M here and read Documentation/modules.txt. The module will be
4414 Enable or Disable Tagged Command Queueing by default
4415 CONFIG_AIC7XXX_TCQ_ON_BY_DEFAULT
4416 This option causes the aic7xxx driver to attempt to use Tagged
4417 Command Queueing (TCQ) on all devices that claim to support it.
4419 TCQ is a feature of SCSI-2 which improves performance: the host
4420 adapter can send several SCSI commands to a device's queue even if
4421 previous commands haven't finished yet. Because the device is
4422 intelligent, it can optimize its operations (like head positioning)
4423 based on its own request queue. Not all devices implement this
4426 If you say Y here, you can still turn off TCQ on troublesome devices
4427 with the use of the tag_info boot parameter. See the file
4428 drivers/scsi/README.aic7xxx for more information on that and other
4429 aic7xxx setup commands. If this option is turned off, you may still
4430 enable TCQ on known good devices by use of the tag_info boot
4433 If you are unsure about your devices then it is safest to say N
4436 However, TCQ can increase performance on some hard drives by as much
4437 as 50% or more, so it is recommended that if you say N here, you
4438 should at least read the README.aic7xxx file so you will know how to
4439 enable this option manually should your drives prove to be safe in
4442 Conversely, certain drives are known to lock up or cause bus resets
4443 when TCQ is enabled on them. If you have a Western Digital
4444 Enterprise SCSI drive for instance, then don't even bother to enable
4445 TCQ on it as the drive will become unreliable, and it will actually
4448 Default number of TCQ commands per device
4449 CONFIG_AIC7XXX_CMDS_PER_DEVICE
4450 Specify the number of commands you would like to allocate per SCSI
4451 device when Tagged Command Queueing (TCQ) is enabled on that device.
4453 Reasonable figures are in the range of 8 to 24 commands per device,
4454 but depending on hardware could be increased or decreased from that
4455 figure. If the number is too high for any particular device, the
4456 driver will automatically compensate usually after only 10 minutes
4457 of uptime. It will not hinder performance if some of your devices
4458 eventually have their command depth reduced, but is a waste of
4459 memory if all of your devices end up reducing this number down to a
4460 more reasonable figure.
4462 NOTE: Certain very broken drives are known to lock up when given
4463 more commands than they like to deal with. Quantum Fireball drives
4464 are the most common in this category. For the Quantum Fireball
4465 drives it is suggested to use no more than 8 commands per device.
4469 Collect statistics to report in /proc
4470 CONFIG_AIC7XXX_PROC_STATS
4471 This option tells the driver to keep track of how many commands have
4472 been sent to each particular device and report that information to
4473 the user via the /proc/scsi/aic7xxx/n file, where n is the number of
4474 the aic7xxx controller you want the information on. This adds a
4475 small amount of overhead to each and every SCSI command the aic7xxx
4476 driver handles, so if you aren't really interested in this
4477 information, it is best to leave it disabled. This will only work if
4478 you also say Y to "/proc filesystem support", below.
4482 Delay in seconds after SCSI bus reset
4483 CONFIG_AIC7XXX_RESET_DELAY
4484 This sets how long the driver will wait after resetting the SCSI bus
4485 before attempting to communicate with the devices on the SCSI bus
4486 again. This delay will be used during the reset phase at bootup time
4487 as well as after any reset that might occur during normal operation.
4488 Reasonable numbers range anywhere from 5 to 15 seconds depending on
4489 your devices. DAT tape drives are notorious for needing more time
4490 after a bus reset to be ready for the next command, but most hard
4491 drives and CD-ROM devices are ready in only a few seconds. This
4492 option has a maximum upper limit of 20 seconds to avoid bad
4493 interactions between the aic7xxx driver and the rest of the linux
4494 kernel. The default value has been reduced to 5 seconds. If this
4495 doesn't work with your hardware, try increasing this value.
4497 IBM ServeRAID Support
4499 This is support for the IBM ServeRAID hardware RAID controllers.
4500 Consult the SCSI-HOWTO, available via anonymous FTP from
4501 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO, and the file
4502 README.ips in drivers/scsi for more information. If this driver
4503 does not work correctly without modification please contact the
4504 author by email at ipslinux@us.ibm.com.
4506 BusLogic SCSI support
4507 CONFIG_SCSI_BUSLOGIC
4508 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
4509 Adapters. Consult the SCSI-HOWTO, available from
4510 http://www.linuxdoc.org/docs.html#howto , and the files
4511 README.BusLogic and README.FlashPoint in drivers/scsi for more
4512 information. If this driver does not work correctly without
4513 modification, please contact the author, Leonard N. Zubkoff, by
4514 email to lnz@dandelion.com.
4516 You can also build this driver as a module ( = code which can be
4517 inserted in and removed from the running kernel whenever you want),
4518 but only a single instance may be loaded. If you want to compile it
4519 as a module, say M here and read Documentation/modules.txt. The
4520 module will be called BusLogic.o.
4522 Omit BusLogic SCSI FlashPoint support
4523 CONFIG_SCSI_OMIT_FLASHPOINT
4524 This option allows you to omit the FlashPoint support from the
4525 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
4526 substantial, so users of MultiMaster Host Adapters may wish to omit
4529 DTC3180/3280 SCSI support
4531 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
4532 the SCSI-HOWTO, available from
4533 http://www.linuxdoc.org/docs.html#howto , and the file
4534 drivers/scsi/README.dtc3x80.
4536 This driver is also available as a module ( = code which can be
4537 inserted in and removed from the running kernel whenever you want).
4538 The module will be called dtc.o. If you want to compile it as a
4539 module, say M here and read Documentation/modules.txt.
4541 EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti, Alphatronix) support
4542 CONFIG_SCSI_EATA_DMA
4543 This is support for the EATA-DMA protocol compliant SCSI Host
4544 Adapters like the SmartCache III/IV, SmartRAID controller families
4545 and the DPT PM2011B and PM2012B controllers.
4547 Note that this driver is obsolete; if you have one of the above SCSI
4548 Host Adapters, you should normally say N here and Y to "EATA
4549 ISA/EISA/PCI support", below. Please read the SCSI-HOWTO, available
4550 from http://www.linuxdoc.org/docs.html#howto .
4552 This driver is also available as a module ( = code which can be
4553 inserted in and removed from the running kernel whenever you want).
4554 The module will be called eata_dma.o. If you want to compile it as a
4555 module, say M here and read Documentation/modules.txt.
4557 EATA-PIO (old DPT PM2001, PM2012A) support
4558 CONFIG_SCSI_EATA_PIO
4559 This driver supports all EATA-PIO protocol compliant SCSI Host
4560 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
4561 host adapters could also use this driver but are discouraged from
4562 doing so, since this driver only supports hard disks and lacks
4563 numerous features. You might want to have a look at the SCSI-HOWTO,
4564 available from http://www.linuxdoc.org/docs.html#howto .
4566 If you want to compile this as a module ( = code which can be
4567 inserted in and removed from the running kernel whenever you want),
4568 say M here and read Documentation/modules.txt. The module will be
4571 UltraStor 14F/34F support
4573 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
4574 The source at drivers/scsi/u14-34f.c contains some information about
4575 this hardware. If the driver doesn't work out of the box, you may
4576 have to change some settings in drivers/scsi/u14-34f.c. Read the
4577 SCSI-HOWTO, available from
4578 http://www.linuxdoc.org/docs.html#howto . Note that there is also
4579 another driver for the same hardware: "UltraStor SCSI support",
4580 below. You should say Y to both only if you want 24F support as
4583 This driver is also available as a module ( = code which can be
4584 inserted in and removed from the running kernel whenever you want).
4585 The module will be called u14-34f.o. If you want to compile it as a
4586 module, say M here and read Documentation/modules.txt.
4588 enable elevator sorting
4589 CONFIG_SCSI_U14_34F_LINKED_COMMANDS
4590 This option enables elevator sorting for all probed SCSI disks and
4591 CDROMs. It definitely reduces the average seek distance when doing
4592 random seeks, but this does not necessarily result in a noticeable
4593 performance improvement: your mileage may vary...
4595 The safe answer is N.
4597 maximum number of queued commands
4598 CONFIG_SCSI_U14_34F_MAX_TAGS
4599 This specifies how many SCSI commands can be maximally queued for
4600 each probed SCSI device. You should reduce the default value of 8
4601 only if you have disks with buggy or limited tagged command support.
4602 Minimum is 2 and maximum is 14. This value is also the window size
4603 used by the elevator sorting option above. The effective value used
4604 by the driver for each probed SCSI device is reported at boot time.
4606 Future Domain 16xx SCSI/AHA-2920A support
4607 CONFIG_SCSI_FUTURE_DOMAIN
4608 This is support for Future Domain's 16-bit SCSI host adapters
4609 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
4610 other adapters based on the Future Domain chipsets (Quantum
4611 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
4612 It is explained in section 3.7 of the SCSI-HOWTO, available from
4613 http://www.linuxdoc.org/docs.html#howto .
4615 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
4616 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
4617 controller support"). This Future Domain driver works with the older
4618 Adaptec AHA-2920A boards with a Future Domain chip on them.
4620 This driver is also available as a module ( = code which can be
4621 inserted in and removed from the running kernel whenever you want).
4622 The module will be called fdomain.o. If you want to compile it as a
4623 module, say M here and read Documentation/modules.txt.
4625 Future Domain MCS-600/700 SCSI support
4627 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
4628 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
4629 is identical to the MCS 700 and hence also supported by this driver.
4630 This driver also supports the Reply SB16/SCSI card (the SCSI part).
4631 It supports multiple adapters in the same system.
4633 This driver is also available as a module ( = code which can be
4634 inserted in and removed from the running kernel whenever you want).
4635 The module will be called fd_mcs.o. If you want to compile it as a
4636 module, say M here and read Documentation/modules.txt.
4638 Generic NCR5380/53c400 SCSI support
4639 CONFIG_SCSI_GENERIC_NCR5380
4640 This is the generic NCR family of SCSI controllers, not to be
4641 confused with the NCR 53c7 or 8xx controllers. It is explained in
4642 section 3.8 of the SCSI-HOWTO, available from
4643 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
4644 of the box, you may have to change some settings in
4645 drivers/scsi/g_NCR5380.h.
4647 This driver is also available as a module ( = code which can be
4648 inserted in and removed from the running kernel whenever you want).
4649 The module will be called g_NCR5380.o. If you want to compile it as
4650 a module, say M here and read Documentation/modules.txt.
4652 Enable NCR53c400 extensions
4653 CONFIG_SCSI_GENERIC_NCR53C400
4654 This enables certain optimizations for the NCR53c400 SCSI cards. You
4655 might as well try it out. Note that this driver will only probe for
4656 the Trantor T130B in its default configuration; you might have to
4657 pass a command line option to the kernel at boot time if it doesn't
4658 detect your card. See the file drivers/scsi/README.g_NCR5380 for
4661 NCR5380/53c400 mapping method (use Port for T130B)
4662 CONFIG_SCSI_G_NCR5380_PORT
4663 The NCR5380 and NCR53c400 SCSI controllers come in two varieties:
4664 port or memory mapped. You should know what you have. The most
4665 common card, Trantor T130B, uses port mapped mode.
4667 NCR53c7,8xx SCSI support
4668 CONFIG_SCSI_NCR53C7xx
4669 This is a driver for the 53c7 and 8xx NCR family of SCSI
4670 controllers, not to be confused with the NCR 5380 controllers. It is
4671 explained in section 3.8 of the SCSI-HOWTO, available from
4672 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
4673 of the box, you may have to change some settings in
4674 drivers/scsi/53c7,8xx.h. Please read drivers/scsi/README.ncr53c7xx
4675 for the available boot time command line options.
4677 Note: there is another driver for the 53c8xx family of controllers
4678 ("NCR53C8XX SCSI support" below). If you want to use them both, you
4679 need to say M to both and build them as modules, but only one may be
4680 active at a time. If you have a 53c8xx board, it's better to use the
4683 This driver is also available as a module ( = code which can be
4684 inserted in and removed from the running kernel whenever you want).
4685 The module will be called 53c7,8xx.o. If you want to compile it as a
4686 module, say M here and read Documentation/modules.txt.
4688 always negotiate synchronous transfers
4689 CONFIG_SCSI_NCR53C7xx_sync
4690 In general, this is good; however, it is a bit dangerous since there
4691 are some broken SCSI devices out there. Take your chances. Safe bet
4694 allow FAST-SCSI [10MHz]
4695 CONFIG_SCSI_NCR53C7xx_FAST
4696 This will enable 10MHz FAST-SCSI transfers with your host
4697 adapter. Some systems have problems with that speed, so it's safest
4701 CONFIG_SCSI_NCR53C7xx_DISCONNECT
4702 This enables the disconnect/reconnect feature of the NCR SCSI
4703 controller. When you say Y here, a slow SCSI device will not lock
4704 the SCSI bus while processing a request, allowing simultaneous use
4705 of e.g. a SCSI hard disk and SCSI tape or CD-ROM drive, and
4706 providing much better performance when using slow and fast SCSI
4707 devices at the same time. Some devices, however, do not operate
4708 properly with this option enabled, and will cause your SCSI system
4709 to hang, which might cause a system crash. The safe answer
4710 therefore is to say N.
4712 NCR53C8XX SCSI support
4713 CONFIG_SCSI_NCR53C8XX
4714 This is the BSD ncr driver adapted to Linux for the NCR53C8XX family
4715 of PCI-SCSI controllers. This driver supports parity checking,
4716 tagged command queuing and fast synchronous data transfers up to 80
4717 MB/s with wide FAST-40 LVD devices and controllers.
4719 Recent versions of the 53C8XX chips are better supported by the
4720 option "SYM53C8XX SCSI support", below.
4722 Note: there is yet another driver for the 53c8xx family of
4723 controllers ("NCR53c7,8xx SCSI support" above). If you want to use
4724 them both, you need to say M to both and build them as modules, but
4725 only one may be active at a time. If you have a 53c8xx board, you
4726 probably do not want to use the "NCR53c7,8xx SCSI support".
4728 Please read drivers/scsi/README.ncr53c8xx for more information.
4730 SYM53C8XX SCSI support
4731 CONFIG_SCSI_SYM53C8XX
4732 This driver supports all the features of recent 53C8XX chips (used
4733 in PCI SCSI controllers), notably the hardware phase mismatch
4734 feature of the SYM53C896.
4736 Older versions of the 53C8XX chips are not supported by this
4737 driver. If your system uses either a 810 rev. < 16, a 815, or a 825
4738 rev. < 16 PCI SCSI processor, you must use the generic NCR53C8XX
4739 driver ("NCR53C8XX SCSI support" above) or configure both the
4740 NCR53C8XX and this SYM53C8XX drivers either as module or linked to
4743 When both drivers are linked into the kernel, the SYM53C8XX driver
4744 is called first at initialization and you can use the 'excl=ioaddr'
4745 driver boot option to exclude attachment of adapters by the
4746 SYM53C8XX driver. For example, entering
4747 'sym53c8xx=excl:0xb400,excl=0xc000' at the lilo prompt prevents
4748 adapters at io address 0xb400 and 0xc000 from being attached by the
4749 SYM53C8XX driver, thus allowing the NCR53C8XX driver to attach them.
4750 The 'excl' option is also supported by the NCR53C8XX driver.
4752 Please read drivers/scsi/README.ncr53c8xx for more information.
4754 synchronous data transfers frequency
4755 CONFIG_SCSI_NCR53C8XX_SYNC
4756 The SCSI Parallel Interface-2 Standard defines 4 classes of transfer
4757 rates: FAST-5, FAST-10, FAST-20 and FAST-40. The numbers are
4758 respectively the maximum data transfer rates in mega-transfers per
4759 second for each class. For example, a FAST-20 Wide 16 device is able
4760 to transfer data at 20 million 16 bit packets per second for a total
4763 You may specify 0 if you want to only use asynchronous data
4764 transfers. This is the safest and slowest option. Otherwise, specify
4765 a value between 5 and 40, depending on the capability of your SCSI
4766 controller. The higher the number, the faster the data transfer.
4767 Note that 40 should normally be ok since the driver decreases the
4768 value automatically according to the controller's capabilities.
4770 Your answer to this question is ignored for controllers with NVRAM,
4771 since the driver will get this information from the user set-up. It
4772 also can be overridden using a boot setup option, as follows
4773 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
4774 for FAST-20 synchronous data transfer (20 mega-transfers per
4777 The normal answer therefore is not to go with the default but to
4778 select the maximum value 40 allowing the driver to use the maximum
4779 value supported by each controller. If this causes problems with
4780 your SCSI devices, you should come back and decrease the value.
4782 There is no safe option other than using good cabling, right
4783 terminations and SCSI conformant devices.
4786 CONFIG_SCSI_NCR53C8XX_IOMAPPED
4787 If you say Y here, the driver will use normal IO, as opposed to
4788 memory mapped IO. Memory mapped IO has less latency than normal IO
4789 and works for most Intel-based hardware. Under Linux/Alpha only
4790 normal IO is currently supported by the driver and so, this option
4791 has no effect on those systems.
4793 The normal answer therefore is N; try Y only if you encounter SCSI
4796 not allow targets to disconnect
4797 CONFIG_SCSI_NCR53C8XX_NO_DISCONNECT
4798 This option is only provided for safety if you suspect some SCSI
4799 device of yours to not support properly the target-disconnect
4800 feature. In that case, you would say Y here. In general however, to
4801 not allow targets to disconnect is not reasonable if there is more
4802 than 1 device on a SCSI bus. The normal answer therefore is N.
4804 default tagged command queue depth
4805 CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS
4806 "Tagged command queuing" is a feature of SCSI-2 which improves
4807 performance: the host adapter can send several SCSI commands to a
4808 device's queue even if previous commands haven't finished yet.
4809 Because the device is intelligent, it can optimize its operations
4810 (like head positioning) based on its own request queue. Some SCSI
4811 devices don't implement this properly; if you want to disable this
4812 feature, enter 0 or 1 here (it doesn't matter which).
4814 The default value is 8 and should be supported by most hard disks.
4815 This value can be overridden from the boot command line using the
4816 'tags' option as follows (example):
4817 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
4818 4, set queue depth to 16 for target 2 and target 3 on controller 0
4819 and set queue depth to 10 for target 0 / lun 2 on controller 1.
4821 The normal answer therefore is to go with the default 8 and to use
4822 a boot command line option for devices that need to use a different
4823 command queue depth.
4825 There is no safe option other than using good SCSI devices.
4827 maximum number of queued commands
4828 CONFIG_SCSI_NCR53C8XX_MAX_TAGS
4829 This option allows you to specify the maximum number of commands
4830 that can be queued to any device, when tagged command queuing is
4831 possible. The default value is 32. Minimum is 2, maximum is 64.
4832 Modern hard disks are able to support 64 tags and even more, but
4833 do not seem to be faster when more than 32 tags are being used.
4835 So, the normal answer here is to go with the default value 32 unless
4836 you are using very large hard disks with large cache (>= 1 MB) that
4837 are able to take advantage of more than 32 tagged commands.
4839 There is no safe option and the default answer is recommended.
4841 assume boards are SYMBIOS compatible (EXPERIMENTAL)
4842 CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT
4843 This option allows you to enable some features depending on GPIO
4844 wiring. These General Purpose Input/Output pins can be used for
4845 vendor specific features or implementation of the standard SYMBIOS
4846 features. Genuine SYMBIOS controllers use GPIO0 in output for
4847 controller LED and GPIO3 bit as a flag indicating
4848 singled-ended/differential interface. The Tekram DC-390U/F boards
4849 uses a different GPIO wiring.
4851 Your answer to this question is ignored if all your controllers have
4852 NVRAM, since the driver is able to detect the board type from the
4855 If all the controllers in your system are genuine SYMBIOS boards or
4856 use BIOS and drivers from SYMBIOS, you would want to say Y here,
4857 otherwise N. N is the safe answer.
4859 enable profiling statistics gathering
4860 CONFIG_SCSI_NCR53C8XX_PROFILE
4861 This option allows you to enable profiling information gathering.
4862 These statistics are not very accurate due to the low frequency
4863 of the kernel clock (100 Hz on i386) and have performance impact
4864 on systems that use very fast devices.
4866 The normal answer therefore is N.
4868 include support for the NCR PQS/PDS SCSI card
4869 CONFIG_SCSI_NCR53C8XX_PQS_PDS
4870 Say Y here if you have a special SCSI adapter produced by NCR
4871 corporation called a PCI Quad SCSI or PCI Dual SCSI. You do not need
4872 this if you do not have one of these adapters. However, since this
4873 device is detected as a specific PCI device, this option is quite
4876 The common answer here is N, but answering Y is safe.
4880 This is support for the IBM SCSI adapter found in many of the PS/2
4881 series computers. These machines have an MCA bus, so you need to
4882 answer Y to "MCA support" as well and read Documentation/mca.txt.
4884 If the adapter isn't found during boot (a common problem for models
4885 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
4886 option, where <pun> is the id of the SCSI subsystem (usually 7, but
4887 if that doesn't work check your reference diskette). Owners of model
4888 95 with a LED-matrix-display can in addition activate some activity
4889 info like under OS/2, but more informative, by setting
4890 'ibmmcascsi=display' as an additional kernel parameter. Try "man
4891 bootparam" or see the documentation of your boot loader about how to
4892 pass options to the kernel. The lilo procedure is also explained in
4893 the SCSI-HOWTO, available from
4894 http://www.linuxdoc.org/docs.html#howto .
4896 If you want to compile this driver as a module ( = code which can be
4897 inserted in and removed from the running kernel whenever you want),
4898 say M here and read Documentation/modules.txt. The module will be
4902 CONFIG_IBMMCA_SCSI_ORDER_STANDARD
4903 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
4904 are assigned to the drive letters, starting with the lowest SCSI-id
4905 (physical number -- pun) to be drive C:, as seen from DOS and
4906 similar operating systems. When looking into papers describing the
4907 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
4908 The SCSI-standard follows a hardware-hierarchy which says that id 7
4909 has the highest priority and id 0 the lowest. Therefore, the host
4910 adapters are still today everywhere placed as SCSI-id 7 by default.
4911 In the SCSI-standard, the drive letters express the priority of the
4912 disk. C: should be the hard disk, or a partition on it, with the
4913 highest priority. This must therefore be the disk with the highest
4914 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
4915 original definition of the SCSI-standard as also industrial- and
4916 process-control-machines, like VME-CPUs running under realtime-OSs
4917 (e.g. LynxOS, OS9) do.
4919 If you like to run Linux on your MCA-machine with the same
4920 assignment of hard disks as seen from e.g. DOS or OS/2 on your
4921 machine, which is in addition conformant to the SCSI-standard, you
4922 must say Y here. This is also necessary for MCA-Linux users who want
4923 to keep downward compatibility to older releases of the
4924 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
4927 If you like to have the lowest SCSI-id assigned as drive C:, as
4928 modern SCSI-BIOSes do, which does not conform to the standard, but
4929 is widespread and common in the PC-world of today, you must say N
4930 here. If unsure, say Y.
4932 Reset SCSI-devices at boot time
4933 CONFIG_IBMMCA_SCSI_DEV_RESET
4934 By default, SCSI-devices are reset when the machine is powered on.
4935 However, some devices exist, like special-control-devices,
4936 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
4937 not reset when switched on. If you say Y here, each device connected
4938 to your SCSI-bus will be issued a reset-command after it has been
4939 probed, while the kernel is booting. This may cause problems with
4940 more modern devices, like hard disks, which do not appreciate these
4941 reset commands, and can cause your system to hang. So say Y only if
4942 you know that one of your older devices needs it; N is the safe
4945 NCR 53C9x MCA support
4946 CONFIG_SCSI_MCA_53C9X
4947 Some Microchannel machines, notably the NCR 35xx line, use a SCSI
4948 controller based on the NCR 53C94. This driver will allow use of
4949 the controller on the 3550, and very possibly others.
4951 If you want to compile this as a module (= code which can be
4952 inserted and removed from the running kernel whenever you want), say
4953 M here and read Documentation/modules.txt. The module will be called
4956 Always IN2000 SCSI support
4958 This is support for an ISA bus SCSI host adapter. You'll find more
4959 information in drivers/scsi/in2000.readme. If it doesn't work out of
4960 the box, you may have to change the jumpers for IRQ or address
4963 If you want to compile this as a module ( = code which can be
4964 inserted in and removed from the running kernel whenever you want),
4965 say M here and read Documentation/modules.txt. The module will be
4968 Initio 91XXU(W) SCSI support
4970 This is support for the Initio 91XXU(W) SCSI host adapter. Please
4971 read the SCSI-HOWTO, available from
4972 http://www.linuxdoc.org/docs.html#howto .
4974 If you want to compile this as a module ( = code which can be
4975 inserted in and removed from the running kernel whenever you want),
4976 say M here and read Documentation/modules.txt. The module will be
4981 This is support for a SCSI host adapter. It is explained in section
4982 3.10 of the SCSI-HOWTO, available from
4983 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
4984 of the box, you may have to change some settings in
4985 drivers/scsi/pas16.h.
4987 This driver is also available as a module ( = code which can be
4988 inserted in and removed from the running kernel whenever you want).
4989 The module will be called pas16.o. If you want to compile it as a
4990 module, say M here and read Documentation/modules.txt.
4992 Initio INI-A100U2W SCSI support
4994 This is support for the Initio INI-A100U2W SCSI host adapter. Please
4995 read the SCSI-HOWTO, available from
4996 http://www.linuxdoc.org/docs.html#howto .
4998 If you want to compile this as a module ( = code which can be
4999 inserted in and removed from the running kernel whenever you want),
5000 say M here and read Documentation/modules.txt. The module will be
5005 This is support for the PCI2000I EIDE interface card which acts as a
5006 SCSI host adapter. Please read the SCSI-HOWTO, available from
5007 http://www.linuxdoc.org/docs.html#howto .
5009 This driver is also available as a module called pci2000.o ( = code
5010 which can be inserted in and removed from the running kernel
5011 whenever you want). If you want to compile it as a module, say M
5012 here and read Documentation/modules.txt.
5015 CONFIG_SCSI_PCI2220I
5016 This is support for the PCI2220i EIDE interface card which acts as a
5017 SCSI host adapter. Please read the SCSI-HOWTO, available from
5018 http://www.linuxdoc.org/docs.html#howto .
5020 This driver is also available as a module called pci2220i.o ( = code
5021 which can be inserted in and removed from the running kernel
5022 whenever you want). If you want to compile it as a module, say M
5023 here and read Documentation/modules.txt.
5027 This is support for the PSI240i EIDE interface card which acts as a
5028 SCSI host adapter. Please read the SCSI-HOWTO, available from
5029 http://www.linuxdoc.org/docs.html#howto .
5031 This driver is also available as a module called psi240i.o ( = code
5032 which can be inserted in and removed from the running kernel
5033 whenever you want). If you want to compile it as a module, say M
5034 here and read Documentation/modules.txt.
5036 Qlogic FAS SCSI support
5037 CONFIG_SCSI_QLOGIC_FAS
5038 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
5039 FastSCSI! cards as well as any other card based on the FASXX chip
5040 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
5042 This driver does NOT support the PCI versions of these cards. The
5043 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
5044 SCSI support"), below.
5046 Information about this driver is contained in
5047 drivers/scsi/README.qlogicfas. You should also read the SCSI-HOWTO,
5048 available from http://www.linuxdoc.org/docs.html#howto .
5050 This driver is also available as a module ( = code which can be
5051 inserted in and removed from the running kernel whenever you want).
5052 The module will be called qlogicfas.o. If you want to compile it as
5053 a module, say M here and read Documentation/modules.txt.
5055 Qlogic ISP SCSI support (EXPERIMENTAL)
5056 CONFIG_SCSI_QLOGIC_ISP
5057 This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
5058 IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
5059 card is supported by the "AM53/79C974 PCI SCSI" driver).
5061 If you say Y here, make sure to choose "BIOS" at the question "PCI
5064 Please read the file drivers/scsi/README.qlogicisp. You should also
5065 read the SCSI-HOWTO, available from
5066 http://www.linuxdoc.org/docs.html#howto .
5068 This driver is also available as a module ( = code which can be
5069 inserted in and removed from the running kernel whenever you want).
5070 The module will be called qlogicisp.o. If you want to compile it as
5071 a module, say M here and read Documentation/modules.txt.
5073 Qlogic ISP FC SCSI support
5074 CONFIG_SCSI_QLOGIC_FC
5075 This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
5077 This driver is also available as a module ( = code which can be
5078 inserted in and removed from the running kernel whenever you want).
5079 The module will be called qlogicfc.o. If you want to compile it as
5080 a module, say M here and read Documentation/modules.txt.
5082 Seagate ST-02 and Future Domain TMC-8xx SCSI support
5084 These are 8-bit SCSI controllers; the ST-01 is also supported by
5085 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
5086 available from http://www.linuxdoc.org/docs.html#howto . If it
5087 doesn't work out of the box, you may have to change some settings in
5088 drivers/scsi/seagate.h.
5090 This driver is also available as a module ( = code which can be
5091 inserted in and removed from the running kernel whenever you want).
5092 The module will be called seagate.o. If you want to compile it as a
5093 module, say M here and read Documentation/modules.txt.
5095 Trantor T128/T128F/T228 SCSI support
5097 This is support for a SCSI host adapter. It is explained in section
5098 3.11 of the SCSI-HOWTO, available from
5099 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
5100 of the box, you may have to change some settings in
5101 drivers/scsi/t128.h. Note that Trantor was purchased by Adaptec, and
5102 some former Trantor products are being sold under the Adaptec name.
5104 This driver is also available as a module ( = code which can be
5105 inserted in and removed from the running kernel whenever you want).
5106 The module will be called t128.o. If you want to compile it as a
5107 module, say M here and read Documentation/modules.txt.
5109 UltraStor SCSI support
5110 CONFIG_SCSI_ULTRASTOR
5111 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
5112 adapter family. This driver is explained in section 3.12 of the
5113 SCSI-HOWTO, available from
5114 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
5115 of the box, you may have to change some settings in
5116 drivers/scsi/ultrastor.h.
5118 Note that there is also another driver for the same hardware:
5119 "UltraStor 14F/34F support", above.
5121 If you want to compile this as a module ( = code which can be
5122 inserted in and removed from the running kernel whenever you want),
5123 say M here and read Documentation/modules.txt. The module will be
5126 7000FASST SCSI support
5127 CONFIG_SCSI_7000FASST
5128 This driver supports the Western Digital 7000 SCSI host adapter
5129 family. Some information is in the source: drivers/scsi/wd7000.c.
5131 This driver is also available as a module ( = code which can be
5132 inserted in and removed from the running kernel whenever you
5133 want). The module will be called wd7000.o. If you want to compile it
5134 as a module, say M here and read Documentation/modules.txt.
5138 This driver supports the ACARD 870U/W SCSI host adapter.
5140 This driver is also available as a module ( = code which can be
5141 inserted in and removed from the running kernel whenever you want).
5142 The module will be called atp870u.o. If you want to compile it as a
5143 module, say M here and read Documentation/modules.txt.
5145 EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support
5147 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
5148 ISA and all EISA i/o addresses are probed looking for the "EATA"
5149 signature. If you chose "BIOS" at the question "PCI access mode",
5150 the addresses of all the PCI SCSI controllers reported by the PCI
5151 subsystem are probed as well.
5153 You want to read the start of drivers/scsi/eata.c and the
5154 SCSI-HOWTO, available from
5155 http://www.linuxdoc.org/docs.html#howto .
5157 Note that there is also another driver for the same hardware
5158 available: "EATA-DMA support". You should say Y to only one of them.
5160 If you want to compile this as a module ( = code which can be
5161 inserted in and removed from the running kernel whenever you want),
5162 say M here and read Documentation/modules.txt. The module will be
5165 enable tagged command queuing
5166 CONFIG_SCSI_EATA_TAGGED_QUEUE
5167 This is a feature of SCSI-2 which improves performance: the host
5168 adapter can send several SCSI commands to a device's queue even if
5169 previous commands haven't finished yet. Most EATA adapters negotiate
5170 this feature automatically with the device, even if your answer is
5171 N. The safe answer is N.
5173 enable elevator sorting
5174 CONFIG_SCSI_EATA_LINKED_COMMANDS
5175 This option enables elevator sorting for all probed SCSI disks and
5176 CDROMs. It definitely reduces the average seek distance when doing
5177 random seeks, but this does not necessarily result in a noticeable
5178 performance improvement: your mileage may vary...
5179 The safe answer is N.
5181 maximum number of queued commands
5182 CONFIG_SCSI_EATA_MAX_TAGS
5183 This specifies how many SCSI commands can be maximally queued for
5184 each probed SCSI device. You should reduce the default value of 16
5185 only if you have disks with buggy or limited tagged command support.
5186 Minimum is 2 and maximum is 62. This value is also the window size
5187 used by the elevator sorting option above. The effective value used
5188 by the driver for each probed SCSI device is reported at boot time.
5190 NCR53c406a SCSI support
5191 CONFIG_SCSI_NCR53C406A
5192 This is support for the NCR53c406a SCSI host adapter. For user
5193 configurable parameters, check out drivers/scsi/NCR53c406.c in the
5194 kernel source. Also read the SCSI-HOWTO, available from
5195 http://www.linuxdoc.org/docs.html#howto .
5197 If you want to compile this driver as a module ( = code which can be
5198 inserted in and removed from the running kernel whenever you want),
5199 say M here and read Documentation/modules.txt. The module will be
5202 Symbios Logic sym53c416 support
5203 CONFIG_SCSI_SYM53C416
5204 This is support for the sym53c416 SCSI host adapter, the SCSI
5205 adapter that comes with some HP scanners. This driver requires that
5206 the sym53c416 is configured first using some sort of pnp
5207 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
5208 are using isapnp then you need to compile this driver as a module
5209 and then load it using insmod after isapnp has run. The parameters
5210 of the configured card(s) should be passed to the driver. The format
5213 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
5215 There is support for up to four adapters. If you want to compile
5216 this driver as a module ( = code which can be inserted in and
5217 removed from the running kernel whenever you want), say M here and
5218 read Documentation/modules.txt. The module will be called
5221 Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support
5223 This driver supports PCI SCSI host adapters based on the Am53C974A
5224 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
5225 PCscsi/PCnet (Am53/79C974) solutions.
5227 Documentation can be found in linux/drivers/scsi/README.tmscsim.
5229 Note that this driver does NOT support Tekram DC390W/U/F, which are
5230 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
5231 Also note that there is another generic Am53C974 driver,
5232 "AM53/79C974 PCI SCSI support" below. You can pick either one.
5234 If you want to compile this driver as a module ( = code which can be
5235 inserted in and removed from the running kernel whenever you want),
5236 say M here and read Documentation/modules.txt. The module will be
5239 Omit support for other Am53/79C974 based SCSI adapters
5240 CONFIG_SCSI_DC390T_NOGENSUPP
5241 If you say N here, the DC390(T) SCSI driver relies on the DC390
5242 EEPROM to get initial values for its settings, such as speed,
5243 termination, etc. If it can't find this EEPROM, it will use defaults
5244 or the user supplied boot/module parameters. For details on driver
5245 configuration see linux/drivers/scsi/README.tmscsim.
5247 If you say Y here and if no EEPROM is found, the driver gives up and
5248 thus only supports Tekram DC390(T) adapters. This can be useful if
5249 you have a DC390(T) and another Am53C974 based adapter, which, for
5250 some reason, you want to drive with the other AM53C974 driver.
5254 AM53/79C974 PCI SCSI support
5255 CONFIG_SCSI_AM53C974
5256 This is support for the AM53/79C974 SCSI host adapters. Please read
5257 drivers/scsi/README.AM53C974 for details. Also, the SCSI-HOWTO,
5258 available from http://www.linuxdoc.org/docs.html#howto , is for
5261 Note that there is another driver for AM53C974 based adapters:
5262 "Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support", above. You
5263 can pick either one.
5265 If you want to compile this driver as a module ( = code which can be
5266 inserted in and removed from the running kernel whenever you want),
5267 say M here and read Documentation/modules.txt. The module will be
5270 AMI MegaRAID support
5271 CONFIG_SCSI_MEGARAID
5272 This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490
5273 and 467 SCSI host adapters.
5275 If you want to compile this driver as a module ( = code which can be
5276 inserted in and removed from the running kernel whenever you want),
5277 say M here and read Documentation/modules.txt. The module will be
5280 GDT SCSI Disk Array Controller support
5282 This is a driver for all SCSI Disk Array Controllers (EISA/ISA/PCI)
5283 manufactured by ICP vortex. It is documented in the kernel source in
5284 drivers/scsi/gdth.c and drivers/scsi/gdth.h.
5286 This driver is also available as a module ( = code which can be
5287 inserted in and removed from the running kernel whenever you want).
5288 If you want to compile it as a module, say M here and read
5289 Documentation/modules.txt.
5291 IOMEGA parallel port (ppa - older drives)
5293 This driver supports older versions of IOMEGA's parallel port ZIP
5294 drive (a 100 MB removable media device).
5296 Note that you can say N here if you have the SCSI version of the ZIP
5297 drive: it will be supported automatically if you said Y to the
5298 generic "SCSI disk support", above.
5300 If you have the ZIP Plus drive or a more recent parallel port ZIP
5301 drive (if the supplied cable with the drive is labeled "AutoDetect")
5302 then you should say N here and Y to "IOMEGA parallel port (imm -
5303 newer drives)", below.
5305 For more information about this driver and how to use it you should
5306 read the file drivers/scsi/README.ppa. You should also read the
5307 SCSI-HOWTO, which is available from
5308 http://www.linuxdoc.org/docs.html#howto . If you use this driver,
5309 you will still be able to use the parallel port for other tasks,
5310 such as a printer; it is safe to compile both drivers into the
5313 This driver is also available as a module which can be inserted in
5314 and removed from the running kernel whenever you want. To compile
5315 this driver as a module, say M here and read
5316 Documentation/modules.txt. The module will be called ppa.o.
5318 IOMEGA parallel port (imm - newer drives)
5320 This driver supports newer versions of IOMEGA's parallel port ZIP
5321 drive (a 100 MB removable media device).
5323 Note that you can say N here if you have the SCSI version of the ZIP
5324 drive: it will be supported automatically if you said Y to the
5325 generic "SCSI disk support", above.
5327 If you have the ZIP Plus drive or a more recent parallel port ZIP
5328 drive (if the supplied cable with the drive is labeled "AutoDetect")
5329 then you should say Y here; if you have an older ZIP drive, say N
5330 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
5332 For more information about this driver and how to use it you should
5333 read the file drivers/scsi/README.ppa. You should also read the
5334 SCSI-HOWTO, which is available from
5335 http://www.linuxdoc.org/docs.html#howto . If you use this driver,
5336 you will still be able to use the parallel port for other tasks,
5337 such as a printer; it is safe to compile both drivers into the
5340 This driver is also available as a module which can be inserted in
5341 and removed from the running kernel whenever you want. To compile
5342 this driver as a module, say M here and read
5343 Documentation/modules.txt. The module will be called imm.o.
5345 Force the Iomega ZIP drivers to use EPP-16
5346 CONFIG_SCSI_IZIP_EPP16
5347 EPP (Enhanced Parallel Port) is a standard for parallel ports which
5348 allows them to act as expansion buses that can handle up to 64
5351 Some parallel port chipsets are slower than their motherboard, and
5352 so we have to control the state of the chipset's FIFO queue every
5353 now and then to avoid data loss. This will be done if you say Y
5356 Generally, saying Y is the safe option and slows things down a bit.
5358 Assume slow parallel port control register
5359 CONFIG_SCSI_IZIP_SLOW_CTR
5360 Some parallel ports are known to have excessive delays between
5361 changing the parallel port control register and good data being
5362 available on the parallel port data/status register. This option
5363 forces a small delay (1.0 usec to be exact) after changing the
5364 control register to let things settle out. Enabling this option may
5365 result in a big drop in performance but some very old parallel ports
5366 (found in 386 vintage machines) will not work properly.
5368 Generally, saying N is fine.
5370 SCSI Debug host simulator. (EXPERIMENTAL)
5372 This is a host adapter simulator that can be programmed to simulate
5373 a large number of conditions that could occur on a real bus. The
5374 advantage is that many hard to reproduce problems can be tested in a
5375 controlled environment where there is reduced risk of losing
5376 important data. This is primarily of use to people trying to debug
5377 the middle and upper layers of the SCSI subsystem. If unsure, say N.
5379 Fibre Channel support
5381 This is an experimental support for storage arrays connected to
5382 the system using Fibre Optic and the "X3.269-199X Fibre Channel
5383 Protocol for SCSI" specification. You'll also need the generic SCSI
5384 support, as well as the drivers for the storage array itself and
5385 for the interface adapter such as SOC. This subsystem could even
5386 serve for IP networking, with some code extensions.
5392 Serial Optical Channel is an interface card with one or two Fibre
5393 Optic ports, each of which can be connected to a disk array. Only
5394 the SBus incarnation of the adapter is supported at the moment.
5396 SparcSTORAGE Array 100 and 200 series
5398 If you never bought a disk array made by Sun, go with N.
5401 CONFIG_SCSI_ACORNSCSI_3
5402 This enables support for the Acorn SCSI card (aka30). If you have an
5403 Acorn system with one of these, say Y. If unsure, say N.
5405 Acorn SCSI tagged queue support
5406 CONFIG_SCSI_ACORNSCSI_TAGGED_QUEUE
5407 Say Y here to enable tagged queuing support on the Acorn SCSI card.
5409 This is a feature of SCSI-2 which improves performance: the host
5410 adapter can send several SCSI commands to a device's queue even if
5411 previous commands haven't finished yet. Some SCSI devices don't
5412 implement this properly, so the safe answer is N.
5414 Acorn SCSI Synchronous transfers support
5415 CONFIG_SCSI_ACORNSCSI_SYNC
5416 Say Y here to enable synchronous transfer negotiation with all
5417 targets on the Acorn SCSI card.
5419 In general, this improves performance; however some SCSI devices
5420 don't implement it properly, so the safe answer is N.
5424 This enables support for the Oak SCSI card. If you have an Acorn
5425 system with one of these, say Y. If unsure, say N.
5427 Cumana SCSI I support
5428 CONFIG_SCSI_CUMANA_1
5429 This enables support for the Cumana SCSI I card. If you have an
5430 Acorn system with one of these, say Y. If unsure, say N.
5432 Cumana SCSI II support (EXPERIMENTAL)
5433 CONFIG_SCSI_CUMANA_2
5434 This enables support for the Cumana SCSI II card. If you have an
5435 Acorn system with one of these, say Y. If unsure, say N.
5439 This enables support for the EcoSCSI card -- a small card that sits
5440 in the Econet socket. If you have an Acorn system with one of these,
5441 say Y. If unsure, say N.
5443 EESOX SCSI support (EXPERIMENTAL)
5444 CONFIG_SCSI_EESOXSCSI
5445 This enables support for the EESOX SCSI card. If you have an Acorn
5446 system with one of these, say Y, otherwise say N.
5448 Powertec SCSI support (EXPERIMENTAL)
5449 CONFIG_SCSI_POWERTECSCSI
5450 This enables support for the Powertec SCSI card on Acorn systems. If
5451 you have one of these, say Y. If unsure, say N.
5453 Network device support?
5455 You can say N here if you don't intend to connect your Linux box to
5456 any other computer at all or if all your connections will be over a
5457 telephone line with a modem either via UUCP (UUCP is a protocol to
5458 forward mail and news between unix hosts over telephone lines; read
5459 the UUCP-HOWTO, available from
5460 http://www.linuxdoc.org/docs.html#howto ) or dialing up a shell
5461 account or a BBS, even using term (term is a program which gives you
5462 almost full Internet connectivity if you have a regular dial up
5463 shell account on some Internet connected Unix computer. Read
5464 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html ).
5466 You'll have to say Y if your computer contains a network card that
5467 you want to use under Linux (make sure you know its name because you
5468 will be asked for it and read the Ethernet-HOWTO (especially if you
5469 plan to use more than one network card under Linux)) or if you want
5470 to use SLIP (Serial Line Internet Protocol is the protocol used to
5471 send Internet traffic over telephone lines or null modem cables) or
5472 CSLIP (compressed SLIP) or PPP (Point to Point Protocol, a better
5473 and newer replacement for SLIP) or PLIP (Parallel Line Internet
5474 Protocol is mainly used to create a mini network by connecting the
5475 parallel ports of two local machines) or AX.25/KISS (protocol for
5476 sending Internet traffic over amateur radio links).
5478 Make sure to read the NET-3-HOWTO. Eventually, you will have to read
5479 Olaf Kirch's excellent and free book "Network Administrator's
5480 Guide", to be found in ftp://metalab.unc.edu/pub/Linux/docs/LDP . If
5483 Dummy net driver support
5485 This is essentially a bit-bucket device (i.e. traffic you send to
5486 this device is consigned into oblivion) with a configurable IP
5487 address. It is most commonly used in order to make your currently
5488 inactive SLIP address seem like a real address for local programs.
5489 If you use SLIP or PPP, you might want to say Y here. Since this
5490 thing often comes in handy, the default is Y. It won't enlarge your
5491 kernel either. What a deal. Read about it in the Network
5492 Administrator's Guide, available from
5493 http://metalab.unc.edu/mdw/linux.html#guide .
5495 If you want to compile this as a module ( = code which can be
5496 inserted in and removed from the running kernel whenever you want),
5497 say M here and read Documentation/modules.txt. The module will be
5498 called dummy.o. If you want to use more than one dummy device at a
5499 time, you need to compile this driver as a module. Instead of
5500 'dummy', the devices will then be called 'dummy0', 'dummy1' etc.
5502 SLIP (serial line) support
5504 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
5505 connect to your Internet service provider or to connect to some
5506 other local Unix box or if you want to configure your Linux box as a
5507 Slip/CSlip server for other people to dial in. SLIP (Serial Line
5508 Internet Protocol) is a protocol used to send Internet traffic over
5509 serial connections such as telephone lines or null modem cables;
5510 nowadays, the protocol PPP is more commonly used for this same
5513 Normally, your access provider has to support SLIP in order for you
5514 to be able to use it, but there is now a SLIP emulator called SLiRP
5515 around (available via FTP (user: anonymous) from
5516 ftp://metalab.unc.edu/pub/Linux/system/network/serial/ ) which
5517 allows you to use SLIP over a regular dial up shell connection. If
5518 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
5519 NET-3-HOWTO, available from
5520 http://www.linuxdoc.org/docs.html#howto , explains how to
5521 configure SLIP. Note that you don't need this option if you just
5522 want to run term (term is a program which gives you almost full
5523 Internet connectivity if you have a regular dial up shell account on
5524 some Internet connected Unix computer. Read
5525 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html ). SLIP
5526 support will enlarge your kernel by about 4 KB. If unsure, say N.
5528 If you want to compile this as a module ( = code which can be
5529 inserted in and removed from the running kernel whenever you want),
5530 say M here and read Documentation/modules.txt as well as
5531 Documentation/networking/net-modules.txt. The module will be called
5534 CSLIP compressed headers
5535 CONFIG_SLIP_COMPRESSED
5536 This protocol is faster than SLIP because it uses compression on the
5537 TCP/IP headers (not on the data itself), but it has to be supported
5538 on both ends. Ask your access provider if you are not sure and
5539 answer Y, just in case. You will still be able to use plain SLIP. If
5540 you plan to use SLiRP, the SLIP emulator (available from
5541 ftp://metalab.unc.edu/pub/Linux/system/network/serial/ ) which allows
5542 you to use SLIP over a regular dial up shell connection, you
5543 definitely want to say Y here. The NET-3-HOWTO, available from
5544 http://www.linuxdoc.org/docs.html#howto , explains how to
5545 configure CSLIP. This won't enlarge your kernel.
5547 Keepalive and linefill
5549 Adds additional capabilities to the SLIP driver to support the
5550 RELCOM line fill and keepalive monitoring. Ideal on poor quality
5553 Six bit SLIP encapsulation
5554 CONFIG_SLIP_MODE_SLIP6
5555 Just occasionally you may need to run IP over hostile serial
5556 networks that don't pass all control characters or are only seven
5557 bit. Saying Y here adds an extra mode you can use with SLIP:
5558 "slip6". In this mode, SLIP will only send normal ASCII symbols over
5559 the serial device. Naturally, this has to be supported at the other
5560 end of the link as well. It's good enough, for example, to run IP
5561 over the async ports of a Camtec JNT Pad. If unsure, say N.
5563 PPP (point-to-point protocol) support
5565 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
5566 the same purpose: sending Internet traffic over telephone (and other
5567 serial) lines. Ask your access provider if they support it, because
5568 otherwise you can't use it; most internet access providers these
5569 days support PPP rather than SLIP.
5571 To use PPP, you need an additional program called pppd as described
5572 in Documentation/networking/ppp.txt and in the PPP-HOWTO, available
5573 at http://www.linuxdoc.org/docs.html#howto . If you upgrade
5574 from an older kernel, you might need to upgrade pppd as well. The
5575 PPP option enlarges your kernel by about 16 KB.
5577 There are actually two versions of PPP: the traditional PPP for
5578 asynchronous lines, such as regular analog phone lines, and
5579 synchronous PPP which can be used over digital ISDN lines for
5580 example. If you want to use PPP over phone lines or other
5581 asynchronous serial lines, you need to say Y (or M) here and also to
5582 the next option, "PPP support for async serial ports". For PPP over
5583 synchronous lines, you should say Y (or M) here and to "Support
5584 synchronous PPP", below.
5586 This driver is also available as a module ( = code which can be
5587 inserted in and removed from the running kernel whenever you want).
5588 If you said Y to "Version information on all symbols" above, then
5589 you cannot compile the PPP driver into the kernel; you can then only
5590 compile it as a module. The module will be called ppp_generic.o. If
5591 you want to compile it as a module, say M here and read
5592 Documentation/modules.txt as well as
5593 Documentation/networking/net-modules.txt.
5595 PPP support for async serial ports
5597 Say Y (or M) here if you want to be able to use PPP over standard
5598 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
5599 a modem (not a synchronous or ISDN modem) to contact your ISP, you
5602 This code is also available as a module (code which can be inserted
5603 into and removed from the running kernel). If you want to compile
5604 it as a module, say M here and read Documentation/modules.txt.
5607 Say Y (or M) here if you want to be able to use PPP over synchronous
5608 (HDLC) tty devices, such as the SyncLink adapter. These devices
5609 are often used for high-speed leased lines like T1/E1.
5611 This code is also available as a module (code which can be inserted
5612 into and removed from the running kernel). If you want to compile
5613 it as a module, say M here and read Documentation/modules.txt.
5615 PPP Deflate compression
5617 Support for the Deflate compression method for PPP, which uses the
5618 Deflate algorithm (the same algorithm that gzip uses) to compress
5619 each PPP packet before it is sent over the wire. The machine at the
5620 other end of the PPP link (usually your ISP) has to support the
5621 Deflate compression method as well for this to be useful. Even if
5622 they don't support it, it is safe to say Y here.
5624 This code is also available as a module (code which can be inserted
5625 into and removed from the running kernel). If you want to compile
5626 it as a module, say M here and read Documentation/modules.txt.
5628 PPP BSD-Compress compression
5630 Support for the BSD-Compress compression method for PPP, which uses
5631 the LZW compression method to compress each PPP packet before it is
5632 sent over the wire. The machine at the other end of the PPP link
5633 (usually your ISP) has to support the BSD-Compress compression
5634 method as well for this to be useful. Even if they don't support it,
5635 it is safe to say Y here.
5637 The PPP Deflate compression method ("PPP Deflate compression",
5638 above) is preferable to BSD-Compress, because it compresses better
5641 Note that the BSD compression code will always be compiled as a
5642 module; it is called bsd_comp.o and will show up in the directory
5643 modules once you have said "make modules". If unsure, say N.
5645 Wireless LAN (non-hamradio)
5647 Support for wireless LANs and everything having to do with radio,
5648 but not with amateur radio. Note that the answer to this question
5649 won't directly affect the kernel: saying N will just cause this
5650 configure script to skip all the questions about radio
5653 Some user-level drivers for scarab devices which don't require
5654 special kernel support are available from
5655 ftp://shadow.cabi.net/pub/Linux .
5657 STRIP (Metricom Starmode radio IP)
5659 Say Y if you have a Metricom radio and intend to use Starmode Radio
5660 IP. STRIP is a radio protocol developed for the MosquitoNet project
5661 (on the WWW at http://mosquitonet.stanford.edu/ ) to send Internet
5662 traffic using Metricom radios. Metricom radios are small, battery
5663 powered, 100kbit/sec packet radio transceivers, about the size and
5664 weight of a cellular telephone. (You may also have heard them called
5665 "Metricom modems" but we avoid the term "modem" because it misleads
5666 many people into thinking that you can plug a Metricom modem into a
5667 phone line and use it as a modem.)
5669 You can use STRIP on any Linux machine with a serial port, although
5670 it is obviously most useful for people with laptop computers. If you
5671 think you might get a Metricom radio in the future, there is no harm
5672 in saying Y to STRIP now, except that it makes the kernel a bit
5675 You can also compile this as a module ( = code which can be inserted
5676 in and removed from the running kernel whenever you want), say M
5677 here and read Documentation/modules.txt. The module will be called
5680 AT&T WaveLAN & DEC RoamAbout DS support
5682 The Lucent WaveLAN (formerly NCR and AT&T; or DEC RoamAbout DS) is
5683 a Radio LAN (wireless Ethernet-like Local Area Network) using the
5684 radio frequencies 900 MHz and 2.4 GHz.
5686 This driver support the ISA version of the WaveLAN card. A separate
5687 driver for the PCMCIA (PC-card) hardware is available in David
5688 Hinds' pcmcia-cs package (see the file Documentation/Changes for
5691 If you want to use an ISA WaveLAN card under Linux, say Y and read
5692 the Ethernet-HOWTO, available from
5693 http://www.linuxdoc.org/docs.html#howto . Some more specific
5694 information is contained in Documentation/networking/wavelan.txt and
5695 in the source code drivers/net/wavelan.p.h.
5697 You will also need the wireless tools package available from
5698 ftp://hyper.stanford.edu/pub/pcmcia/contrib/ . Please read the man
5699 pages contained therein.
5701 This driver is also available as a module ( = code which can be
5702 inserted in and removed from the running kernel whenever you want).
5703 The module will be called wavelan.o. If you want to compile it as a
5704 module, say M here and read Documentation/modules.txt as well as
5705 Documentation/networking/net-modules.txt.
5707 Aironet Arlan 655 & IC2200 DS support
5709 Aironet makes Arlan, a class of wireless LAN adapters. These use the
5710 www.Telxon.com chip, which is also used on several similar cards.
5711 This driver is tested on the 655 and IC2200 series cards. Look at
5712 http://www.ylenurme.ee/~elmer/655/ for latest information.
5714 The driver is built as two modules, arlan and arlan-proc. The latter
5715 is the /proc interface and is not needed most of time.
5717 On some computers the card ends up in non-valid state after some time.
5718 Use a ping-reset script to clear it.
5720 Aironet 4500/4800 series adapters
5722 www.aironet.com (recently bought by Cisco) makes these 802.11 DS
5723 adapters. Driver by Elmer Joandi (elmer@ylenurme.ee).
5724 Work sponsored by www.spectrumwireless.net and www.vendomar.ee
5725 This configuration option enables common code for all devices (PCI, ISA,
5727 module is aironet4500_core
5728 quickconfig parameters:
5729 SSID=tsunami - "The Password"
5730 adhoc=1 there are no Access Points around
5731 master=1 Adhoc master (the one who creates network sync)
5732 slave=1 Adhoc slave(btw, it is still forming own net
5734 channel=1..? meaningful in adhoc mode
5735 all other parameters can be set via proc interface
5736 These parameters belong to .._card module, but alas, they are here
5737 if you have problems with screwin up card, both_bap_lock=1 is conservative
5738 value (performance hit 15%)
5739 for any other configuration options look at ..._proc module
5741 Aironet 4500/4800 ISA/PCI/PNP/365 support
5742 CONFIG_AIRONET4500_NONCS
5743 This is module aironet4500_card, which includes _possibility_ to
5744 support for following
5746 ISA device in ISA mode(does not work currently)
5747 ISA device in PNP mode
5748 PCMCIA device _without_ cardservices, direct 365 chip INIT,
5749 does not work currently
5750 PCMCIA _with_ CardServices(normal way) is at another module
5751 radio parameters are currently configurable at ..._core module
5753 Aironet 4500/4800 PNP support
5754 CONFIG_AIRONET4500_PNP
5755 This option should be enabled for ISA cards, remember to enable
5756 PNP jumper on board.
5757 module aironet4500_card
5759 Aironet 4500/4800 PCI support
5760 CONFIG_AIRONET4500_PCI
5761 This option should be enabled for PCI cards
5762 module aironet4500_card
5764 Aironet 4500/4800 ISA broken support (EXPERIMENTAL)
5765 CONFIG_AIRONET4500_ISA
5766 This option enables support for ISA cards in non-PNP mode.
5767 Does not operate correctly by now.
5768 module aironet4500_card
5770 Aironet 4500/4800 I365 broken support (EXPERIMENTAL)
5771 CONFIG_AIRONET4500_I365
5772 This option enables support for PCMCIA cards on i365 controller
5773 _without_ cardservices. Doesnt have much sense and is not working
5774 properly. Comes from times where there was no PCMCIA support in
5775 kernel main source tree
5777 Aironet 4500/4800 PCMCIA support
5778 CONFIG_AIRONET4500_CS
5779 This option enables support for PCMCIA cards to be used with
5781 This is not for ISA and PCI adapters.
5782 module aironet4500_cs.o
5783 The same option is both on:
5784 1. PCMCIA netdevices configuring panel
5785 2. Wireless netdevices configuring panel
5786 Possibility to change this option depeds on options set in 2.
5788 Aironet 4500/4800 PROC interface
5789 CONFIG_AIRONET4500_PROC
5790 This option enables /proc/sys/aironet4500 interface for
5791 configuring the device.
5792 NOTE: it takes lot of memory. Compile it as module and remove
5794 module: aironet4500_proc
5795 additional info: look into drivers/net/aironet4500_rids.c
5796 this is quite human-readable(no need to know C)
5801 LAPB over Ethernet driver
5803 This is a driver for a pseudo device (typically called /dev/lapb0)
5804 which allows you to open an LAPB point-to-point connection to some
5805 other computer on your Ethernet network. In order to do this, you
5806 need to say Y or M to the driver for your Ethernet card as well as
5807 to "LAPB Data Link Driver".
5809 If you want to compile this driver as a module ( = code which can be
5810 inserted in and removed from the running kernel whenever you want),
5811 say M here and read Documentation/modules.txt. The module will be
5812 called lapbether.o. If unsure, say N.
5816 This is a driver for sending and receiving X.25 frames over regular
5817 asynchronous serial lines such as telephone lines equipped with
5818 ordinary modems. Experts should note that this driver doesn't
5819 currently comply with the asynchronous HDLS framing protocols in
5820 CCITT recommendation X.25.
5822 If you want to compile this driver as a module ( = code which can be
5823 inserted in and removed from the running kernel whenever you want),
5824 say M here and read Documentation/modules.txt. The module will be
5825 called x25_asy.o. If unsure, say N.
5827 PCMCIA network device support
5829 Say Y if you would like to include support for any PCMCIA network
5830 adapters. If unsure, say N.
5832 3Com 3c589 PCMCIA support
5834 Say Y here if you intend to attach a 3Com 3c589 or compatible PCMCIA
5835 (PC-card) Ethernet card to your computer.
5837 This driver is also available as a module ( = code which can be
5838 inserted in and removed from the running kernel whenever you want).
5839 The module will be called 3c589_cs.o. If you want to compile it as a
5840 module, say M here and read Documentation/modules.txt. If unsure,
5843 3Com 3c574 PCMCIA support
5845 Say Y here if you intend to attach a 3Com 3c574 or compatible PCMCIA
5846 (PC-card) Fast Ethernet card to your computer.
5848 This driver is also available as a module ( = code which can be
5849 inserted in and removed from the running kernel whenever you want).
5850 The module will be called 3c574_cs.o. If you want to compile it as a
5851 module, say M here and read Documentation/modules.txt. If unsure,
5854 Fujitsu FMV-J18x PCMCIA support
5855 CONFIG_PCMCIA_FMVJ18X
5856 Say Y here if you intend to attach a Fujitsu FMV-J18x or compatible
5857 PCMCIA (PC-card) Ethernet card to your computer.
5859 This driver is also available as a module ( = code which can be
5860 inserted in and removed from the running kernel whenever you want).
5861 The module will be called fmvj18x_cs.o. If you want to compile it as a
5862 module, say M here and read Documentation/modules.txt. If unsure,
5865 NE2000 compatible PCMCIA support
5867 Say Y here if you intend to attach an NE2000 compatible PCMCIA
5868 (PC-card) Ethernet or Fast Ethernet card to your computer.
5870 This driver is also available as a module ( = code which can be
5871 inserted in and removed from the running kernel whenever you want).
5872 The module will be called pcnet_cs.o. If you want to compile it as a
5873 module, say M here and read Documentation/modules.txt. If unsure,
5876 New Media PCMCIA support
5877 CONFIG_PCMCIA_NMCLAN
5878 Say Y here if you intend to attach a New Media Ethernet or LiveWire
5879 PCMCIA (PC-card) Ethernet card to your computer.
5881 This driver is also available as a module ( = code which can be
5882 inserted in and removed from the running kernel whenever you want).
5883 The module will be called nmclan_cs.o. If you want to compile it as a
5884 module, say M here and read Documentation/modules.txt. If unsure,
5887 SMC 91Cxx PCMCIA support
5888 CONFIG_PCMCIA_SMC91C92
5889 Say Y here if you intend to attach an SMC 91Cxx compatible PCMCIA
5890 (PC-card) Ethernet or Fast Ethernet card to your computer.
5892 This driver is also available as a module ( = code which can be
5893 inserted in and removed from the running kernel whenever you want).
5894 The module will be called smc91c92_cs.o. If you want to compile it as a
5895 module, say M here and read Documentation/modules.txt. If unsure,
5898 Xircom 16-bit PCMCIA support
5899 CONFIG_PCMCIA_XIRC2PS
5900 Say Y here if you intend to attach a Xircom 16-bit PCMCIA
5901 (PC-card) Ethernet or Fast Ethernet card to your computer.
5903 This driver is also available as a module ( = code which can be
5904 inserted in and removed from the running kernel whenever you want).
5905 The module will be called xirc2ps_cs.o. If you want to compile it as a
5906 module, say M here and read Documentation/modules.txt. If unsure,
5909 3Com 3c575 CardBus support
5911 This driver supports the 3Com 3c575 series of CardBus Fast Ethernet
5914 This driver can only be compiled as a module ( = code which can be
5915 inserted in and removed from the running kernel whenever you want).
5916 The module will be called 3c575_cb.o. If you want to do that, say M
5917 here and read Documentation/modules.txt. If unsure, say N.
5919 DEC Tulip CardBus support
5921 This driver supports CardBus Fast Ethernet adapters based on DEC
5922 Tulip and compatible chipsets.
5924 This driver can only be compiled as a module ( = code which can be
5925 inserted in and removed from the running kernel whenever you want).
5926 The module will be called tulip_cb.o. If you want to do that, say M
5927 here and read Documentation/modules.txt. If unsure, say N.
5929 SMC EPIC CardBus support
5930 CONFIG_PCMCIA_EPIC100
5931 This driver supports CardBus Fast Ethernet adapters based on the SMC
5934 This driver can only be compiled as a module ( = code which can be
5935 inserted in and removed from the running kernel whenever you want).
5936 The module will be called epic100_cb.o. If you want to do that, say
5937 M here and read Documentation/modules.txt. If unsure, say N.
5939 Aviator/Raytheon 2.4MHz wireless support
5941 Say Y here if you intend to attach an Aviator/Raytheon PCMCIA
5942 (PC-card) wireless Ethernet networking card to your computer.
5944 This driver is also available as a module ( = code which can be
5945 inserted in and removed from the running kernel whenever you want).
5946 The module will be called ray_cs.o. If you want to compile it as a
5947 module, say M here and read Documentation/modules.txt. If unsure,
5950 Xircom Netwave AirSurfer wireless support
5951 CONFIG_PCMCIA_NETWAVE
5952 Say Y here if you intend to attach a Xircom Netwave AirSurfer PCMCIA
5953 (PC-card) wireless Ethernet networking card to your computer.
5955 This driver is also available as a module ( = code which can be
5956 inserted in and removed from the running kernel whenever you want).
5957 The module will be called netwave_cs.o. If you want to compile it as a
5958 module, say M here and read Documentation/modules.txt. If unsure,
5961 AT&T/Lucent Wavelan wireless support
5962 CONFIG_PCMCIA_WAVELAN
5963 Say Y here if you intend to attach an AT&T/Lucent Wavelan PCMCIA
5964 (PC-card) wireless Ethernet networking card to your computer. This
5965 driver is for the non-IEEE-802.11 Wavelan cards.
5967 This driver is also available as a module ( = code which can be
5968 inserted in and removed from the running kernel whenever you want).
5969 The module will be called wavelan_cs.o. If you want to compile it as a
5970 module, say M here and read Documentation/modules.txt. If unsure,
5973 PLIP (parallel port) support
5975 PLIP (Parallel Line Internet Protocol) is used to create a
5976 reasonably fast mini network consisting of two (or, rarely, more)
5977 local machines. A PLIP link from a Linux box is a popular means to
5978 install a Linux distribution on a machine which doesn't have a CDROM
5979 drive (a minimal system has to be transferred with floppies first).
5980 The kernels on both machines need to have this PLIP option enabled
5983 The PLIP driver has two modes, mode 0 and mode 1. The parallel ports
5984 (the connectors at the computers with 25 holes) are connected with
5985 "null printer" or "Turbo Laplink" cables which can transmit 4 bits
5986 at a time (mode 0) or with special PLIP cables, to be used on
5987 bidirectional parallel ports only, which can transmit 8 bits at a
5988 time (mode 1); you can find the wiring of these cables in
5989 Documentation/networking/PLIP.txt. The cables can be up to 15m long.
5990 Mode 0 works also if one of the machines runs DOS/Windows and has
5991 some PLIP software installed, e.g. the Crynwr PLIP packet driver
5992 (http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html ) and
5993 winsock or NCSA's telnet.
5995 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
5996 as the NET-3-HOWTO, both available from
5997 http://www.linuxdoc.org/docs.html#howto . Note that the PLIP
5998 protocol has been changed and this PLIP driver won't work together
5999 with the PLIP support in Linux versions 1.0.x. This option enlarges
6000 your kernel by about 8 KB.
6002 If you want to compile this as a module ( = code which can be
6003 inserted in and removed from the running kernel whenever you want),
6004 say M here and read Documentation/modules.txt as well as
6005 Documentation/networking/net-modules.txt. The module will be called
6006 plip.o. If unsure, say Y or M, in case you buy a laptop later.
6008 EQL (serial line load balancing) support
6010 If you have two serial connections to some other computer (this
6011 usually requires two modems and two telephone lines) and you use
6012 SLIP (the protocol for sending Internet traffic over telephone
6013 lines) or PPP (a better SLIP) on them, you can make them behave like
6014 one double speed connection using this driver. Naturally, this has
6015 to be supported at the other end as well, either with a similar EQL
6016 Linux driver or with a Livingston Portmaster 2e.
6018 Say Y if you want this and read Documentation/networking/eql.txt.
6019 You may also want to read section 6.2 of the NET-3-HOWTO, available
6020 from http://www.linuxdoc.org/docs.html#howto .
6022 This driver is also available as a module ( = code which can be
6023 inserted in and removed from the running kernel whenever you want).
6024 The module will be called eql.o. If you want to compile it as a
6025 module, say M here and read Documentation/modules.txt. If unsure,
6028 Ethertap network tap (EXPERIMENTAL)
6030 If you say Y here (and have said Y to "Kernel/User network link
6031 driver", above) and create a character special file /dev/tap0 with
6032 major number 36 and minor number 16 using mknod ("man mknod"), you
6033 will be able to have a user space program read and write raw
6034 Ethernet frames from/to that special file. tap0 can be configured
6035 with ifconfig and route like any other Ethernet device but it is not
6036 connected to any physical LAN; everything written by the user to
6037 /dev/tap0 is treated by the kernel as if it had come in from a LAN
6038 to the device tap0; everything the kernel wants to send out over the
6039 device tap0 can instead be read by the user from /dev/tap0: the user
6040 mode program replaces the LAN that would be attached to an ordinary
6041 Ethernet device. Please read the file
6042 Documentation/networking/ethertap.txt for more information.
6044 This driver is also available as a module ( = code which can be
6045 inserted in and removed from the running kernel whenever you want).
6046 The module will be called ethertap.o. If you want to compile it as a
6047 module, say M here and read Documentation/modules.txt.
6049 If you don't know what to use this for, you don't need it.
6051 Sealevel Systems 4021 support
6052 CONFIG_SEALEVEL_4021
6053 This is a driver for the Sealevel Systems ACB 56 serial I/O adapter.
6055 This driver can only be compiled as a module ( = code which can be
6056 inserted in and removed from the running kernel whenever you want).
6057 If you want to do that, say M here. The module will be called
6060 Frame Relay (DLCI) support
6062 This is support for the frame relay protocol; frame relay is a fast
6063 low-cost way to connect to a remote Internet access provider or to
6064 form a private wide area network. The one physical line from your
6065 box to the local "switch" (i.e. the entry point to the frame relay
6066 network, usually at the phone company) can carry several logical
6067 point-to-point connections to other computers connected to the frame
6068 relay network. For a general explanation of the protocol, check out
6069 http://www.frforum.com/ on the WWW. To use frame relay, you need
6070 supporting hardware (called FRAD) and certain programs from the
6071 net-tools package as explained in
6072 Documentation/networking/framerelay.txt.
6074 This driver is also available as a module ( = code which can be
6075 inserted in and removed from the running kernel whenever you want).
6076 The module will be called dlci.o. If you want to compile it as a
6077 module, say M here and read Documentation/modules.txt.
6081 This is the maximal number of logical point-to-point frame relay
6082 connections (the identifiers of which are called DCLIs) that
6083 the driver can handle. The default is probably fine.
6087 You can specify here how many logical point-to-point frame relay
6088 connections (the identifiers of which are called DCLIs) should be
6089 handled by each of your hardware frame relay access devices. Go with
6092 Sangoma S502A FRAD support
6094 Say Y here if you need a driver for the Sangoma S502A, S502E, and
6095 S508 Frame Relay Access Devices. These are multi-protocol cards, but
6096 only frame relay is supported by the driver at this time. Please
6097 read Documentation/framerelay.txt.
6099 This driver is also available as a module ( = code which can be
6100 inserted in and removed from the running kernel whenever you want).
6101 The module will be called sdla.o. If you want to compile it as a
6102 module, say M here and read Documentation/modules.txt.
6104 Acorn Econet/AUN protocols (EXPERIMENTAL)
6106 Econet is a fairly old and slow networking protocol mainly used by
6107 Acorn computers to access file and print servers. It uses native
6108 Econet network cards. AUN is an implementation of the higher level
6109 parts of Econet that runs over ordinary Ethernet connections, on
6110 top of the UDP packet protocol, which in turn runs on top of the
6111 Internet protocol IP.
6113 If you say Y here, you can choose with the next two options whether
6114 to send Econet/AUN traffic over a UDP Ethernet connection or over
6115 a native Econet network card.
6117 This driver is also available as a module ( = code which can be
6118 inserted in and removed from the running kernel whenever you want).
6119 The module will be called econet.o. If you want to compile it as a
6120 module, say M here and read Documentation/modules.txt.
6123 CONFIG_ECONET_AUNUDP
6124 Say Y here if you want to send Econet/AUN traffic over a UDP
6125 connection (UDP is a packet based protocol that runs on top of the
6126 Internet protocol IP) using an ordinary Ethernet network card.
6129 CONFIG_ECONET_NATIVE
6130 Say Y here if you have a native Econet network card installed in
6135 Wide Area Networks (WANs), such as X.25, frame relay and leased
6136 lines, are used to interconnect Local Area Networks (LANs) over vast
6137 distances with data transfer rates significantly higher than those
6138 achievable with commonly used asynchronous modem connections.
6139 Usually, a quite expensive external device called a `WAN router' is
6140 needed to connect to a WAN.
6142 As an alternative, WAN routing can be built into the Linux kernel.
6143 With relatively inexpensive WAN interface cards available on the
6144 market, a perfectly usable router can be built for less than half
6145 the price of an external router. If you have one of those cards and
6146 wish to use your Linux box as a WAN router, say Y here and also to
6147 the WAN driver for your card, below. You will then need the
6148 wan-tools package which is available from ftp://ftp.sangoma.com .
6149 Read Documentation/networking/wan-router.txt for more information.
6151 The WAN routing support is also available as a module called
6152 wanrouter.o ( = code which can be inserted in and removed from the
6153 running kernel whenever you want). If you want to compile it as a
6154 module, say M here and read Documentation/modules.txt.
6158 Fast switching (read help!)
6159 CONFIG_NET_FASTROUTE
6160 Saying Y here enables direct NIC-to-NIC (NIC = Network Interface
6161 Card) data transfers on the local network, which is fast.
6163 IMPORTANT NOTE: This option is NOT COMPATIBLE with "Network packet
6164 filtering" (CONFIG_NETFILTER). Say N here if you say Y there.
6166 However, it will work with all options in the "IP: advanced router"
6167 section (except for "IP: use TOS value as routing key" and
6168 "IP: use FWMARK value as routing key").
6170 At the moment, few devices support fast switching (tulip is one of
6171 them, a modified 8390 driver can be found at
6172 ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz ).
6176 Forwarding between high speed interfaces
6177 CONFIG_NET_HW_FLOWCONTROL
6178 This option enables NIC (Network Interface Card) hardware throttling
6179 during periods of extremal congestion. At the moment only a couple
6180 of device drivers support it (really only one -- tulip, a modified
6181 8390 driver can be found at
6182 ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz ).
6184 Really, this option is applicable to any machine attached to a fast
6185 enough network, and even a 10 Mb NIC is able to kill a not very slow
6186 box, such as a 120MHz Pentium.
6188 However, do not say Y here if you did not experience any serious
6191 QoS and/or fair queueing
6193 When the kernel has several packets to send out over a network
6194 device, it has to decide which ones to send first, which ones to
6195 delay, and which ones to drop. This is the job of the packet
6196 scheduler, and several different algorithms for how to do this
6197 "fairly" have been proposed.
6199 If you say N here, you will get the standard packet scheduler, which
6200 is a FIFO (first come, first served). If you say Y here, you will be
6201 able to choose from among several alternative algorithms which can
6202 then be attached to different network devices. This is useful for
6203 example if some of your network devices are real time devices that
6204 need a certain minimum data flow rate, or if you need to limit the
6205 maximum data flow rate for traffic which matches specified criteria.
6206 This code is considered to be experimental.
6208 To administer these schedulers, you'll need the user-level utilities
6209 from the package iproute2+tc at ftp://ftp.inr.ac.ru/ip-routing/ .
6210 That package also contains some documentation; for more, check out
6211 http://snafu.freedom.org/linux2.2/iproute-notes.html .
6213 If you say Y here and to "/proc filesystem" below, you will be able
6214 to read status information about packet schedulers from the file
6217 The available schedulers are listed in the following questions; you
6218 can say Y to as many as you like. If unsure, say N now.
6220 CBQ packet scheduler
6222 Say Y here if you want to use the Class-Based Queueing (CBQ) packet
6223 scheduling algorithm for some of your network devices. This
6224 algorithm classifies the waiting packets into a tree-like hierarchy
6225 of classes; the leaves of this tree are in turn scheduled by
6226 separate algorithms (called "disciplines" in this context).
6228 See the top of net/sched/sch_cbq.c for references about the CBQ
6231 CBQ is a commonly used scheduler, so if you're unsure, you should
6232 say Y here. Then say Y to all the queueing algorithms below that you
6233 want to use as CBQ disciplines. Then say Y to "Packet classifier
6234 API" and say Y to all the classifiers you want to use; a classifier
6235 is a routine that allows you to sort your outgoing traffic into
6236 classes based on a certain criterion.
6238 This code is also available as a module called sch_cbq.o ( = code
6239 which can be inserted in and removed from the running kernel
6240 whenever you want). If you want to compile it as a module, say M
6241 here and read Documentation/modules.txt.
6243 CSZ packet scheduler
6245 Say Y here if you want to use the Clark-Shenker-Zhang (CSZ) packet
6246 scheduling algorithm for some of your network devices. At the
6247 moment, this is the only algorithm that can guarantee service for
6248 real-time applications (see the top of net/sched/sch_csz.c for
6249 details and references about the algorithm).
6251 Note: this scheduler is currently broken.
6253 This code is also available as a module called sch_csz.o ( = code
6254 which can be inserted in and removed from the running kernel
6255 whenever you want). If you want to compile it as a module, say M
6256 here and read Documentation/modules.txt.
6258 #ATM pseudo-scheduler
6264 The simplest PRIO pseudo scheduler
6266 Say Y here if you want to use an n-band priority queue packet
6267 "scheduler" for some of your network devices or as a leaf discipline
6268 for the CBQ scheduling algorithm. If unsure, say Y.
6270 This code is also available as a module called sch_prio.o ( = code
6271 which can be inserted in and removed from the running kernel
6272 whenever you want). If you want to compile it as a module, say M
6273 here and read Documentation/modules.txt.
6277 Say Y here if you want to use the Random Early Detection (RED)
6278 packet scheduling algorithm for some of your network devices (see
6279 the top of net/sched/sch_red.c for details and references about the
6282 This code is also available as a module called sch_red.o ( = code
6283 which can be inserted in and removed from the running kernel
6284 whenever you want). If you want to compile it as a module, say M
6285 here and read Documentation/modules.txt.
6289 Say Y here if you want to use the Stochastic Fairness Queueing (SFQ)
6290 packet scheduling algorithm for some of your network devices or as a
6291 leaf discipline for the CBQ scheduling algorithm (see the top of
6292 net/sched/sch_sfq.c for details and references about the SFQ
6295 This code is also available as a module called sch_sfq.o ( = code
6296 which can be inserted in and removed from the running kernel
6297 whenever you want). If you want to compile it as a module, say M
6298 here and read Documentation/modules.txt.
6302 Say Y here if you want to use the True Link Equalizer (TLE) packet
6303 scheduling algorithm for some of your network devices or as a leaf
6304 discipline for the CBQ scheduling algorithm. This queueing
6305 discipline allows the combination of several physical devices into
6306 one virtual device. (see the top of net/sched/sch_teql.c for
6309 This code is also available as a module called sch_teql.o ( = code
6310 which can be inserted in and removed from the running kernel
6311 whenever you want). If you want to compile it as a module, say M
6312 here and read Documentation/modules.txt.
6316 Say Y here if you want to use the Simple Token Bucket Filter (TBF)
6317 packet scheduling algorithm for some of your network devices or as a
6318 leaf discipline for the CBQ scheduling algorithm (see the top of
6319 net/sched/sch_tbf.c for a description of the TBF algorithm).
6321 This code is also available as a module called sch_tbf.o ( = code
6322 which can be inserted in and removed from the running kernel
6323 whenever you want). If you want to compile it as a module, say M
6324 here and read Documentation/modules.txt.
6328 Say Y here if you want to include Quality Of Service scheduling
6329 features, which means that you will be able to request certain
6330 rate-of-flow limits for your network devices.
6332 Note that the answer to this question won't directly affect the
6333 kernel: saying N will just cause this configure script to skip all
6334 the questions about QoS support.
6337 CONFIG_NET_ESTIMATOR
6338 In order for Quality of Service scheduling to work, the current
6339 rate-of-flow for a network device has to be estimated; if you say Y
6340 here, the kernel will do just that.
6342 Packet classifier API
6344 The CBQ scheduling algorithm requires that network packets which are
6345 scheduled to be sent out over a network device be classified
6346 according to some criterion. If you say Y here, you will get a
6347 choice of several different packet classifiers with the following
6350 Routing tables based classifier
6351 CONFIG_NET_CLS_ROUTE
6352 If you say Y here, you will be able to classify outgoing packets
6353 according to the route table entry they matched. If unsure, say Y.
6355 This code is also available as a module called cls_route.o ( = code
6356 which can be inserted in and removed from the running kernel
6357 whenever you want). If you want to compile it as a module, say M
6358 here and read Documentation/modules.txt.
6360 Firewall based classifier
6362 If you say Y here, you will be able to classify outgoing packets
6363 according to firewall criteria you specified.
6365 This code is also available as a module called cls_fw.o ( = code
6366 which can be inserted in and removed from the running kernel
6367 whenever you want). If you want to compile it as a module, say M
6368 here and read Documentation/modules.txt.
6372 If you say Y here, you will be able to classify outgoing packets
6373 according to their destination address. If unsure, say Y.
6375 This code is also available as a module called cls_u32.o ( = code
6376 which can be inserted in and removed from the running kernel
6377 whenever you want). If you want to compile it as a module, say M
6378 here and read Documentation/modules.txt
6380 Special RSVP classifier
6382 The Resource Reservation Protocol (RSVP) permits end systems to
6383 request a minimum and maximum data flow rate for a connection; this
6384 is important for real time data such as streaming sound or video.
6386 Say Y here if you want to be able to classify outgoing packets based
6387 on their RSVP requests.
6389 This code is also available as a module called cls_rsvp.o ( = code
6390 which can be inserted in and removed from the running kernel
6391 whenever you want). If you want to compile it as a module, say M
6392 here and read Documentation/modules.txt
6394 Special RSVP classifier for IPv6
6395 CONFIG_NET_CLS_RSVP6
6396 The Resource Reservation Protocol (RSVP) permits end systems to
6397 request a minimum and maximum data flow rate for a connection; this
6398 is important for real time data such as streaming sound or video.
6400 Say Y here if you want to be able to classify outgoing packets based
6401 on their RSVP requests and you are using the new Internet Protocol
6402 IPv6 as opposed to the older and more common IPv4.
6404 This code is also available as a module called cls_rsvp6.o ( = code
6405 which can be inserted in and removed from the running kernel
6406 whenever you want). If you want to compile it as a module, say M
6407 here and read Documentation/modules.txt
6410 # Ingres traffic policing
6411 # CONFIG_NET_CLS_POLICE
6413 ### Some expert please fill these in
6416 Network code profiler
6418 If you say Y here and to "/proc filesystem support" below, some
6419 obscure and undocumented information about the network code's
6420 performance will be written to /proc/net/profile. If you don't know
6421 what it is about, you don't need it: say N.
6423 Comtrol Hostess SV-11 support
6425 This is a network card for low speed synchronous serial links, at
6426 up to 256Kbps. It supports both PPP and Cisco HDLC.
6428 At this point, the driver can only be compiled as a module.
6430 COSA/SRP sync serial boards support
6432 This is a driver for COSA and SRP synchronous serial boards. These
6433 boards allow to connect synchronous serial devices (for example
6434 base-band modems, or any other device with the X.21, V.24, V.35 or
6435 V.36 interface) to your Linux box. The cards can work as the
6436 character device, synchronous PPP network device, or the Cisco HDLC
6439 To actually use the COSA or SRP board, you will need user-space
6440 utilities for downloading the firmware to the cards and to set them
6441 up. Look at the http://www.fi.muni.cz/~kas/cosa/ for more
6442 information about the cards (including the pointer to the user-space
6443 utilities). You can also read the comment at the top of the
6444 drivers/net/cosa.c for details about the cards and the driver
6447 The driver will be compiled as a module ( = code which can be
6448 inserted in and removed from the running kernel whenever you want).
6449 The module will be called cosa.o. For general information about
6450 modules read Documentation/modules.txt.
6452 # Fibre Channel driver support
6455 # Interphase 5526 Tachyon chipset based adaptor support
6458 Red Creek Hardware VPN (EXPERIMENTAL)
6460 This is a driver for hardware which provides a Virtual Private
6461 Network (VPN). Say Y if you have it.
6463 This code is also available as a module called rcpci.o ( = code
6464 which can be inserted in and removed from the running kernel
6465 whenever you want). If you want to compile it as a module, say M
6466 here and read Documentation/modules.txt.
6468 SBNI Leased Line Adapters
6470 This is a driver for ISA SBNI12-xx cards that is a low cost
6471 alternative to leased line modems. Say Y if you want to insert
6472 driver into kernel or say M to compile driver as a module.
6474 You can find more information and last versions of drivers and
6475 utilities at http://www.granch.ru. If you have any question you
6476 can mail to sbni@granch.ru.
6482 Say Y to this option if your Linux box contains a WAN card and you
6483 are planning to use the box as a WAN ( = Wide Area Network) router
6484 ( = device used to interconnect local area networks over wide area
6485 communication links, such as leased lines or public data networks,
6486 e.g. X.25 or frame relay) and you will be offered a list of drivers
6487 for WAN cards currently available. For more information, read
6488 Documentation/networking/wan-router.txt.
6490 Note that the answer to this question won't directly affect the
6491 kernel: saying N will just cause this configure script to skip all
6492 the questions about WAN card drivers. If unsure, say N.
6494 Sangoma WANPIPE(tm) multiprotocol cards
6495 CONFIG_VENDOR_SANGOMA
6496 WANPIPE from Sangoma Technologies Inc. (http://www.sangoma.com ) is a
6497 family of intelligent multiprotocol WAN adapters with data transfer
6498 rates up to T1 (1.544 Mbps). They are also known as Synchronous Data
6499 Link Adapters (SDLA) and designated S502E(A), S503 or S508. These
6500 cards support the X.25, Frame Relay, and PPP protocols. If you have
6501 one or more of these cards, say Y to this option; you may then also
6502 want to read the file Documentation/networking/wanpipe.txt. The next
6503 questions will ask you about the protocols you want the driver to
6506 The driver will be compiled as a module ( = code which can be
6507 inserted in and removed from the running kernel whenever you want).
6508 The module will be called wanpipe.o. For general information about
6509 modules read Documentation/modules.txt.
6511 Maximum number of cards
6512 CONFIG_WANPIPE_CARDS
6513 Enter number of WANPIPE adapters installed in your machine. The
6514 driver can support up to 8 cards. You may enter more than you
6515 actually have if you plan to add more cards in the future without
6516 re-compiling the driver, but remember that in this case you'll waste
6517 some kernel memory (about 1K per card).
6519 WANPIPE X.25 support
6521 Say Y to this option if you are planning to connect a WANPIPE card
6522 to an X.25 network. You should then also have said Y to "CCITT X.25
6523 Packet Layer" and "LAPB Data Link Driver", above. If you say N, the
6524 X.25 support will not be included in the driver (saves about 16 KB
6527 WANPIPE Frame Relay support
6529 Say Y to this option if you are planning to connect a WANPIPE card
6530 to a frame relay network. You should then also have said Y to "Frame
6531 Relay (DLCI) support", above. If you say N, the frame relay
6532 support will not be included in the driver (saves about 16 KB of
6537 Say Y to this option if you are planning to connect a WANPIPE card
6538 to a leased line using Point-to-Point protocol (PPP). You should
6539 then also have said Y to "PPP (point-to-point) support", above. If
6540 you say N, the PPP support will not be included in the driver (saves
6541 about 16 KB of kernel memory).
6543 Cyclom 2X(tm) multiprotocol cards (EXPERIMENTAL)
6544 CONFIG_CYCLADES_SYNC
6545 Cyclom 2X from Cyclades Corporation (http://www.cyclades.com and
6546 http://www.cyclades.com.br) is an intelligent multiprotocol WAN
6547 adapter with data transfer rates up to 512 Kbps. These cards support
6548 the X.25 and SNA related protocols. If you have one or more of these
6549 cards, say Y to this option. The next questions will ask you about
6550 the protocols you want the driver to support (for now only X.25 is
6553 While no documentation is available at this time please grab the
6554 wanconfig tarball in http://www.conectiva.com.br/~acme/cycsyn-devel
6555 (with minor changes to make it compile with the current wanrouter
6556 include files; efforts are being made to use the original package
6557 available at ftp://ftp.sangoma.com ).
6559 Feel free to contact me or the cycsyn-devel mailing list at
6560 acme@conectiva.com.br and cycsyn-devel@bazar.conectiva.com.br for
6561 additional details, I hope to have documentation available as soon
6562 as possible (Cyclades Brazil is writing the Documentation).
6564 The driver will be compiled as a module ( = code which can be
6565 inserted in and removed from the running kernel whenever you want).
6566 The module will be called cyclomx.o. For general information about
6567 modules read Documentation/modules.txt.
6569 Cyclom 2X X.25 support
6571 Say Y to this option if you are planning to connect a Cyclom 2X card
6574 If you say N, the X.25 support will not be included in the driver
6575 (saves about 11 KB of kernel memory).
6577 Ethernet (10 or 100Mbit)
6579 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
6580 type of Local Area Network (LAN) in universities and companies.
6582 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
6583 coaxial cable, linking computers in a chain), 10BASE-T or twisted
6584 pair (10 Mbps over twisted pair cable, linking computers to central
6585 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
6586 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
6587 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
6588 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
6589 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
6590 Ethernet (1 Gbps over optical fiber or short copper links).
6592 If your Linux machine will be connected to an Ethernet and you have
6593 an Ethernet network interface card (NIC) installed in your computer,
6594 say Y here and read the Ethernet-HOWTO, available from
6595 http://www.linuxdoc.org/docs.html#howto . You will then also have
6596 to say Y to the driver for your particular NIC.
6598 Note that the answer to this question won't directly affect the
6599 kernel: saying N will just cause this configure script to skip all
6600 the questions about Ethernet network cards. If unsure, say N.
6602 Sun LANCE Ethernet support
6604 This is support for lance Ethernet cards on Sun workstations such as
6605 the SPARCstation IPC (any SPARC with a network interface 'le0' under
6608 This driver is also available as a module ( = code which can be
6609 inserted in and removed from the running kernel whenever you want).
6610 The module will be called lance.o. If you want to compile it as a
6611 module, say M here and read Documentation/modules.txt.
6613 Sun Intel Ethernet support
6615 This is support for the Intel Ethernet cards on some Sun
6616 workstations (all those with a network interface 'ie0' under SunOS).
6618 Western Digital/SMC cards
6619 CONFIG_NET_VENDOR_SMC
6620 If you have a network (Ethernet) card belonging to this class, say Y
6621 and read the Ethernet-HOWTO, available from
6622 http://www.linuxdoc.org/docs.html#howto .
6624 Note that the answer to this question doesn't directly affect the
6625 kernel: saying N will just cause this configure script to skip all
6626 the questions about Western Digital cards. If you say Y, you will be
6627 asked for your specific card in the following questions.
6631 If you have a network (Ethernet) card of this type, say Y and read
6632 the Ethernet-HOWTO, available from
6633 http://www.linuxdoc.org/docs.html#howto .
6635 This driver is also available as a module ( = code which can be
6636 inserted in and removed from the running kernel whenever you want).
6637 The module will be called wd.o. If you want to compile it as a
6638 module, say M here and read Documentation/modules.txt as well as
6639 Documentation/networking/net-modules.txt.
6641 SMC Ultra MCA support
6643 If you have a network (Ethernet) card of this type and are running
6644 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
6645 available from http://www.linuxdoc.org/docs.html#howto .
6647 This driver is also available as a module ( = code which can be
6648 inserted in and removed from the running kernel whenever you want).
6649 The module will be called smc-mca.o. If you want to compile it as a
6650 module, say M here and read Documentation/modules.txt as well as
6651 Documentation/networking/net-modules.txt.
6655 If you have a network (Ethernet) card of this type, say Y and read
6656 the Ethernet-HOWTO, available from
6657 http://www.linuxdoc.org/docs.html#howto .
6659 Important: There have been many reports that, with some motherboards
6660 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
6661 such as some BusLogic models) causes corruption problems with many
6662 operating systems. The Linux smc-ultra driver has a work-around for
6663 this but keep it in mind if you have such a SCSI card and have
6666 This driver is also available as a module ( = code which can be
6667 inserted in and removed from the running kernel whenever you want).
6668 The module will be called smc-ultra.o. If you want to compile it as
6669 a module, say M here and read Documentation/modules.txt as well as
6670 Documentation/networking/net-modules.txt.
6672 SMC Ultra32 EISA support
6674 If you have a network (Ethernet) card of this type, say Y and read
6675 the Ethernet-HOWTO, available from
6676 http://www.linuxdoc.org/docs.html#howto .
6678 This driver is also available as a module ( = code which can be
6679 inserted in and removed from the running kernel whenever you want).
6680 The module will be called smc-ultra32.o. If you want to compile it
6681 as a module, say M here and read Documentation/modules.txt as well
6682 as Documentation/networking/net-modules.txt.
6686 This is support for the SMC9xxx based Ethernet cards. Choose this
6687 option if you have a DELL laptop with the docking station, or
6688 another SMC9192/9194 based chipset. Say Y if you want it compiled
6689 into the kernel, and read the file
6690 Documentation/networking/smc9.txt and the Ethernet-HOWTO, available
6691 from http://www.linuxdoc.org/docs.html#howto .
6693 This driver is also available as a module ( = code which can be
6694 inserted in and removed from the running kernel whenever you
6695 want). The module will be called smc9194.o. If you want to compile
6696 it as a module, say M here and read Documentation/modules.txt as
6697 well as Documentation/networking/net-modules.txt.
6701 This driver is for NE2000 compatible PCI cards. It will not work
6702 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
6703 support" below). If you have a PCI NE2000 network (Ethernet) card,
6704 say Y and read the Ethernet-HOWTO, available from
6705 http://www.linuxdoc.org/docs.html#howto .
6707 This driver is also available as a module ( = code which can be
6708 inserted in and removed from the running kernel whenever you want).
6709 The module will be called ne2k-pci.o. If you want to compile it as a
6710 module, say M here and read Documentation/modules.txt as well as
6711 Documentation/networking/net-modules.txt.
6715 This driver is for DM9102 compatible PCI cards from Davicom
6716 (http://www.davicom.com.tw)
6717 If you have a PCI DM9102 network (Ethernet) card, say Y.
6719 This driver is also available as a module ( = code which can be
6720 inserted in and removed from the running kernel whenever you want).
6721 The module will be called dmfe.o. If you want to compile it as a
6722 module, say M here and read Documentation/modules.txt as well as
6723 Documentation/networking/net-modules.txt.
6725 Racal-Interlan (Micom) NI cards
6726 CONFIG_NET_VENDOR_RACAL
6727 If you have a network (Ethernet) card belonging to this class, such
6728 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
6729 available from http://www.linuxdoc.org/docs.html#howto .
6731 Note that the answer to this question doesn't directly affect the
6732 kernel: saying N will just cause this configure script to skip all
6733 the questions about NI cards. If you say Y, you will be asked for
6734 your specific card in the following questions.
6736 NI5010 support (EXPERIMENTAL)
6738 If you have a network (Ethernet) card of this type, say Y and read
6739 the Ethernet-HOWTO, available from
6740 http://www.linuxdoc.org/docs.html#howto . Note that this is still
6743 This driver is also available as a module ( = code which can be
6744 inserted in and removed from the running kernel whenever you want).
6745 The module will be called ni5010.o. If you want to compile it as a
6746 module, say M here and read Documentation/modules.txt as well as
6747 Documentation/networking/net-modules.txt.
6751 If you have a network (Ethernet) card of this type, say Y and read
6752 the Ethernet-HOWTO, available from
6753 http://www.linuxdoc.org/docs.html#howto .
6755 This driver is also available as a module ( = code which can be
6756 inserted in and removed from the running kernel whenever you want).
6757 The module will be called ni52.o. If you want to compile it as a
6758 module, say M here and read Documentation/modules.txt as well as
6759 Documentation/networking/net-modules.txt.
6763 If you have a network (Ethernet) card of this type, say Y and read
6764 the Ethernet-HOWTO, available from
6765 http://www.linuxdoc.org/docs.html#howto .
6767 This driver is also available as a module ( = code which can be
6768 inserted in and removed from the running kernel whenever you want).
6769 The module will be called ni65.o. If you want to compile it as a
6770 module, say M here and read Documentation/modules.txt as well as
6771 Documentation/networking/net-modules.txt.
6773 RealTek 8129/8139 (not 8019/8029!) support
6775 This is a driver for the Fast Ethernet PCI network cards based on
6776 the RTL8129 and RTL8139 chips. If you have one of those, say Y and
6777 read the Ethernet-HOWTO, available from
6778 http://www.linuxdoc.org/docs.html#howto .
6780 If you want to compile this driver as a module ( = code which can be
6781 inserted in and removed from the running kernel whenever you want),
6782 say M here and read Documentation/modules.txt. This is recommended.
6783 The module will be called rtl8139.o.
6785 SiS 900 PCI Fast Ethernet Adapter support
6787 This is a driver for the Fast Ethernet PCI network cards based on
6788 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
6789 SiS 630 and SiS 540 chipsets. If you have one of those, say Y and
6790 read the Ethernet-HOWTO, available via FTP (user: anonymous) in
6791 ftp://metalab.unc.edu/pub/Linux/docs/HOWTO. Please read
6792 Documentation/networking/sis900.txt and comments at the beginning
6793 of drivers/net/sis900.c for more information.
6795 This driver also supports AMD 79C901 HomePNA such that you can use
6796 your phone line as network cable.
6798 If you want to compile this driver as a module ( = code which can be
6799 inserted in and removed from the running kernel whenever you want),
6800 say M here and read Documentation/modules.txt. This is recommended.
6801 The module will be called sis900.o.
6803 Packet Engines Yellowfin Gigabit-NIC support
6805 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
6806 adapter. This adapter is used by the Beowulf Linux cluster project.
6807 See http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html for
6808 more information about this driver in particular and Beowulf in
6811 If you want to compile this driver as a module ( = code which can be
6812 inserted in and removed from the running kernel whenever you want),
6813 say M here and read Documentation/modules.txt. This is recommended.
6814 The module will be called yellowfin.o.
6816 General Instruments Surfboard 1000
6818 This is a driver for the General Instrument (also known as
6819 NextLevel) SURFboard 1000 internal
6820 cable modem. This is an ISA card which is used by a number of cable
6821 TV companies to provide cable modem access. It's a one-way
6822 downstream-only cable modem, meaning that your upstream net link is
6823 provided by your regular phone modem.
6825 At present this driver only compiles as a module, so say M here if
6826 you have this card. The module will be called sb1000.o. Then read
6827 Documentation/networking/README.sb1000 for information on how to use
6828 this module, as it needs special ppp scripts for establishing a
6829 connection. Further documentation and the necessary scripts can be
6832 http://www.jacksonville.net/~fventuri/
6833 http://home.adelphia.net/~siglercm/sb1000.html
6834 http://linuxpower.cx/~cable/
6836 If you don't have this card, of course say N.
6838 Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support
6840 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
6841 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
6842 adapter. The driver allows for using the Jumbo Frame option (9000
6843 bytes/frame) however it requires that your switches can handle this
6844 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
6847 If you want to compile this driver as a module ( = code which can be
6848 inserted in and removed from the running kernel whenever you want),
6849 say M here and read Documentation/modules.txt. This is recommended.
6850 The module will be called acenic.o.
6852 Omit support for older Tigon I based AceNICs
6853 CONFIG_ACENIC_OMIT_TIGON_I
6854 Say Y here if you only have Tigon II based AceNICs and want to leave
6855 out support for the older Tigon I based cards which are no longer
6856 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
6857 version)). This will reduce the size of the driver object by
6858 app. 100KB. If you are not sure whether your card is a Tigon I or a
6859 Tigon II, say N here.
6861 The safe and default value for this is N.
6863 SysKonnect SK-98xx support
6865 Say Y here if you have a SysKonnect SK-98xx Gigabit Ethernet Server
6866 Adapter. The following adapters are supported by this driver:
6867 - SK-9841 (single link 1000Base-LX)
6868 - SK-9842 (dual link 1000Base-LX)
6869 - SK-9843 (single link 1000Base-SX)
6870 - SK-9844 (dual link 1000Base-SX)
6871 - SK-9821 (single link 1000Base-T)
6872 - SK-9822 (dual link 1000Base-T)
6873 The dual link adapters support a link-failover feature.
6874 Read Documentation/networking/sk98lin.txt for information about
6875 optional driver parameters.
6876 Questions concerning this driver may be addresse to:
6879 If you want to compile this driver as a module ( = code which can be
6880 inserted in and removed from the running kernel whenever you want),
6881 say M here and read Documentation/modules.txt. This is recommended.
6882 The module will be called sk98lin.o.
6884 AMD LANCE and PCnet (AT1500 and NE2100) support
6886 If you have a network (Ethernet) card of this type, say Y and read
6887 the Ethernet-HOWTO, available from
6888 http://www.linuxdoc.org/docs.html#howto . Some LinkSys cards are
6891 If you want to compile this driver as a module ( = code which can be
6892 inserted in and removed from the running kernel whenever you want),
6893 say M here and read Documentation/modules.txt. This is recommended.
6894 The module will be called lance.o.
6897 CONFIG_NET_VENDOR_3COM
6898 If you have a network (Ethernet) card belonging to this class, say Y
6899 and read the Ethernet-HOWTO, available from
6900 http://www.linuxdoc.org/docs.html#howto .
6902 Note that the answer to this question doesn't directly affect the
6903 kernel: saying N will just cause this configure script to skip all
6904 the questions about 3COM cards. If you say Y, you will be asked for
6905 your specific card in the following questions.
6909 If you have a network (Ethernet) card of this type, say Y and read
6910 the Ethernet-HOWTO, available from
6911 http://www.linuxdoc.org/docs.html#howto . Also, consider buying a
6912 new card, since the 3c501 is slow, broken, and obsolete: you will
6913 have problems. Some people suggest to ping ("man ping") a nearby
6914 machine every minute ("man cron") when using this card.
6916 This driver is also available as a module ( = code which can be
6917 inserted in and removed from the running kernel whenever you want).
6918 The module will be called 3c501.o. If you want to compile it as a
6919 module, say M here and read Documentation/modules.txt as well as
6920 Documentation/networking/net-modules.txt.
6924 If you have a network (Ethernet) card of this type, say Y and read
6925 the Ethernet-HOWTO, available from
6926 http://www.linuxdoc.org/docs.html#howto .
6928 This driver is also available as a module ( = code which can be
6929 inserted in and removed from the running kernel whenever you want).
6930 The module will be called 3c503.o. If you want to compile it as a
6931 module, say M here and read Documentation/modules.txt as well as
6932 Documentation/networking/net-modules.txt.
6936 Information about this network (Ethernet) card can be found in
6937 Documentation/networking/3c505.txt. If you have a card of this type,
6938 say Y and read the Ethernet-HOWTO, available from
6939 http://www.linuxdoc.org/docs.html#howto .
6941 If you want to compile this as a module ( = code which can be
6942 inserted in and removed from the running kernel whenever you want),
6943 say M here and read Documentation/modules.txt as well as
6944 Documentation/networking/net-modules.txt. The module will be called
6947 3c507 support (EXPERIMENTAL)
6949 If you have a network (Ethernet) card of this type, say Y and read
6950 the Ethernet-HOWTO, available from
6951 http://www.linuxdoc.org/docs.html#howto .
6953 This driver is also available as a module ( = code which can be
6954 inserted in and removed from the running kernel whenever you want).
6955 The module will be called 3c507.o. If you want to compile it as a
6956 module, say M here and read Documentation/modules.txt as well as
6957 Documentation/networking/net-modules.txt.
6961 If you have a network (Ethernet) card of this type, say Y and read
6962 the Ethernet-HOWTO, available from
6963 http://www.linuxdoc.org/docs.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 3c523.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.
6973 If you have a network (Ethernet) card of this type, say Y and read
6974 the Ethernet-HOWTO, available from
6975 http://www.linuxdoc.org/docs.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 3c527.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.
6985 If you have a network (Ethernet) card belonging to the 3Com
6986 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
6987 from http://www.linuxdoc.org/docs.html#howto .
6989 If your card is not working you may need to use the DOS
6990 setup disk to disable Plug & Play mode, and to select the default
6993 If you want to compile this as a module ( = code which can be
6994 inserted in and removed from the running kernel whenever you want),
6995 say M here and read Documentation/modules.txt as well as
6996 Documentation/networking/net-modules.txt. The module will be called
6999 3c590 series (592/595/597) "Vortex" support
7001 If you have a 3Com "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597)
7002 or "Boomerang" series (EtherLink XL 3c900 or 3c905) network
7003 (Ethernet) card, say Y and read the Ethernet-HOWTO, available from
7004 http://www.linuxdoc.org/docs.html#howto . More specific
7005 information is in Documentation/networking/vortex.txt and in the
7006 comments at the beginning of drivers/net/3c59x.c.
7008 If you want to compile this as a module ( = code which can be
7009 inserted in and removed from the running kernel whenever you want),
7010 say M here and read Documentation/modules.txt as well as
7011 Documentation/networking/net-modules.txt.
7015 If your network (Ethernet) card hasn't been mentioned yet and its
7016 bus system (that's the way the cards talks to the other components
7017 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
7018 Make sure you know the name of your card. Read the Ethernet-HOWTO,
7019 available from http://www.linuxdoc.org/docs.html#howto .
7023 Note that the answer to this question doesn't directly affect the
7024 kernel: saying N will just cause this configure script to skip all
7025 the remaining ISA network card questions. If you say Y, you will be
7026 asked for your specific card in the following questions.
7028 Generic ARCnet support
7030 If you have a network card of this type, say Y and check out the
7031 (arguably) beautiful poetry in Documentation/networking/arcnet.txt.
7033 You need both this driver, and the driver for the particular ARCnet
7034 chipset of your card. If you don't know, then it's probably a
7035 COM90xx type card, so say Y (or M) to "ARCnet COM90xx chipset
7038 You might also want to have a look at the Ethernet-HOWTO, available
7039 from http://www.linuxdoc.org/docs.html#howto (even though ARCnet
7040 is not really Ethernet).
7042 This driver is also available as a module ( = code which can be
7043 inserted in and removed from the running kernel whenever you want).
7044 The module will be called arcnet.o. If you want to compile it as a
7045 module, say M here and read Documentation/modules.txt as well as
7046 Documentation/networking/net-modules.txt.
7048 Enable arc0e (ARCnet "ether-encap" packet format)
7050 This allows you to use "Ethernet encapsulation" with your ARCnet
7051 card via the virtual arc0e device. You only need arc0e if you want
7052 to talk to nonstandard ARCnet software, specifically,
7053 DOS/Windows-style "NDIS" drivers. You do not need to say Y here to
7054 communicate with industry-standard RFC1201 implementations, like the
7055 arcether.com packet driver or most DOS/Windows ODI drivers. RFC1201
7056 is included automatically as the arc0 device. Please read the
7057 ARCnet documentation in Documentation/networking/arcnet.txt for more
7058 information about using arc0e and arc0s.
7060 Enable arc0s (ARCnet RFC1051 packet format)
7062 This allows you to use RFC1051 with your ARCnet card via the virtual
7063 arc0s device. You only need arc0s if you want to talk to ARCnet
7064 software complying with the "old" standard, specifically, the DOS
7065 arcnet.com packet driver, Amigas running AmiTCP, and some variants
7066 of NetBSD. You do not need to say Y here to communicate with
7067 industry-standard RFC1201 implementations, like the arcether.com
7068 packet driver or most DOS/Windows ODI drivers. RFC1201 is included
7069 automatically as the arc0 device. Please read the ARCnet
7070 documentation in Documentation/networking/arcnet.txt for more
7071 information about using arc0e and arc0s.
7073 ARCnet COM90xx (normal) chipset driver
7074 CONFIG_ARCNET_COM90xx
7075 This is the chipset driver for the standard COM90xx cards. If you
7076 have always used the old ARCnet driver without knowing what type of
7077 card you had, this is probably the one for you.
7079 This driver is also available as a module ( = code which can be
7080 inserted in and removed from the running kernel whenever you want).
7081 The module will be called com90xx.o. If you want to compile it as a
7082 module, say M here and read Documentation/modules.txt as well as
7083 Documentation/networking/net-modules.txt.
7085 ARCnet COM90xx (IO mapped) chipset driver
7086 CONFIG_ARCNET_COM90xxIO
7087 This is the chipset driver for the COM90xx cards, using them in
7088 IO-mapped mode instead of memory-mapped mode. This is slower than
7089 the normal driver. Only use it if your card doesn't support shared
7092 This driver is also available as a module ( = code which can be
7093 inserted in and removed from the running kernel whenever you want).
7094 The module will be called com90io.o. If you want to compile it as a
7095 module, say M here and read Documentation/modules.txt as well as
7096 Documentation/networking/net-modules.txt.
7098 ARCnet COM90xx (RIM I) chipset driver
7100 This is yet another chipset driver for the COM90xx cards, but this
7101 time only using memory-mapped mode, and no IO ports at all. This
7102 driver is completely untested, so if you have one of these cards,
7103 please mail David.Woodhouse@mvhi.com, especially if it works!
7105 This driver is also available as a module ( = code which can be
7106 inserted in and removed from the running kernel whenever you
7107 want). The module will be called arc-rimi.o. If you want to compile
7108 it as a module, say M here and read Documentation/modules.txt as
7109 well as Documentation/networking/net-modules.txt.
7111 ARCnet COM20020 chipset driver
7112 CONFIG_ARCNET_COM20020
7113 This is the driver for the new COM20020 chipset. It supports such
7114 things as promiscuous mode, so packet sniffing is possible, and
7115 extra diagnostic information.
7117 This driver is also available as a module ( = code which can be
7118 inserted in and removed from the running kernel whenever you want).
7119 The module will be called com20020.o. If you want to compile it as a
7120 module, say M here and read Documentation/modules.txt as well as
7121 Documentation/networking/net-modules.txt.
7123 Cabletron E21xx support
7125 If you have a network (Ethernet) card of this type, say Y and read
7126 the Ethernet-HOWTO, available from
7127 http://www.linuxdoc.org/docs.html#howto .
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 e2100.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.
7137 Support for CS89x0 chipset based Ethernet cards. If you have a
7138 network (Ethernet) card of this type, say Y and read the
7139 Ethernet-HOWTO, available from
7140 http://www.linuxdoc.org/docs.html#howto as well as
7141 Documentation/networking/cs89x0.txt.
7143 If you want to compile this as a module ( = code which can be
7144 inserted in and removed from the running kernel whenever you want),
7145 say M here and read Documentation/modules.txt as well as
7146 Documentation/networking/net-modules.txt. The module will be called
7151 If you have a network (Ethernet) card of this type, say Y and read
7152 the Ethernet-HOWTO, available from
7153 http://www.linuxdoc.org/docs.html#howto as well as
7154 drivers/net/depca.c.
7156 If you want to compile this as a module ( = code which can be
7157 inserted in and removed from the running kernel whenever you want),
7158 say M here and read Documentation/modules.txt as well as
7159 Documentation/networking/net-modules.txt. The module will be called
7162 EtherWorks 3 support
7164 This driver supports the DE203, DE204 and DE205 network (Ethernet)
7165 cards. If this is for you, say Y and read
7166 Documentation/networking/ewrk3.txt in the kernel source as well as
7167 the Ethernet-HOWTO, available from
7168 http://www.linuxdoc.org/docs.html#howto .
7170 If you want to compile this as a module ( = code which can be
7171 inserted in and removed from the running kernel whenever you want),
7172 say M here and read Documentation/modules.txt as well as
7173 Documentation/networking/net-modules.txt. The module will be called
7178 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
7179 is for you, read the Ethernet-HOWTO, available from
7180 http://www.linuxdoc.org/docs.html#howto .
7182 If you want to compile this as a module ( = code which can be
7183 inserted in and removed from the running kernel whenever you want),
7184 say M here and read Documentation/modules.txt as well as
7185 Documentation/networking/net-modules.txt. The module will be called
7190 If you have a network (Ethernet) card of this type, say Y and read
7191 the Ethernet-HOWTO, available from
7192 http://www.linuxdoc.org/docs.html#howto .
7194 This driver is also available as a module ( = code which can be
7195 inserted in and removed from the running kernel whenever you want).
7196 If you want to compile it as a module, say M here and read
7197 Documentation/modules.txt as well as
7198 Documentation/networking/net-modules.txt. The module will be called
7201 FMV-181/182/183/184 support
7203 If you have a Fujitsu FMV-181/182/183/184 network (Ethernet) card,
7204 say Y and read the Ethernet-HOWTO, available from
7205 http://www.linuxdoc.org/docs.html#howto .
7207 If you use an FMV-183 or FMV-184 and it is not working, you may need
7208 to disable Plug & Play mode of the card.
7210 This driver is also available as a module ( = code which can be
7211 inserted in and removed from the running kernel whenever you want).
7212 The module will be called fmv18x.o. If you want to compile it as a
7213 module, say M here and read Documentation/modules.txt as well as
7214 Documentation/networking/net-modules.txt.
7216 EtherExpress PRO support
7218 If you have a network (Ethernet) card of this type, say Y. Note
7219 however that the EtherExpress PRO/100 Ethernet card has its own
7220 separate driver. Please read the Ethernet-HOWTO, available from
7221 http://www.linuxdoc.org/docs.html#howto .
7223 This driver is also available as a module ( = code which can be
7224 inserted in and removed from the running kernel whenever you want).
7225 The module will be called eepro.o. If you want to compile it as a
7226 module, say M here and read Documentation/modules.txt as well as
7227 Documentation/networking/net-modules.txt.
7229 EtherExpress support
7231 If you have an EtherExpress16 network (Ethernet) card, say Y and
7232 read the Ethernet-HOWTO, available from
7233 http://www.linuxdoc.org/docs.html#howto . Note that the Intel
7234 EtherExpress16 card used to be regarded as a very poor choice
7235 because the driver was very unreliable. We now have a new driver
7236 that should do better.
7238 If you want to compile this driver as a module ( = code which can be
7239 inserted in and removed from the running kernel whenever you want),
7240 say M here and read Documentation/modules.txt as well as
7241 Documentation/networking/net-modules.txt. The module will be called
7244 HP PCLAN+ (27247B and 27252A) support
7246 If you have a network (Ethernet) card of this type, say Y and read
7247 the Ethernet-HOWTO, available from
7248 http://www.linuxdoc.org/docs.html#howto .
7250 This driver is also available as a module ( = code which can be
7251 inserted in and removed from the running kernel whenever you want).
7252 The module will be called hp-plus.o. If you want to compile it as a
7253 module, say M here and read Documentation/modules.txt as well as
7254 Documentation/networking/net-modules.txt.
7256 HP PCLAN (27245 and other 27xxx series) support
7258 If you have a network (Ethernet) card of this type, say Y and read
7259 the Ethernet-HOWTO, available from
7260 http://www.linuxdoc.org/docs.html#howto .
7262 This driver is also available as a module ( = code which can be
7263 inserted in and removed from the running kernel whenever you want).
7264 The module will be called hp.o. If you want to compile it as a
7265 module, say M here and read Documentation/modules.txt as well as
7266 Documentation/networking/net-modules.txt.
7268 HP 10/100VG PCLAN (ISA, EISA, PCI) support
7270 If you have a network (Ethernet) card of this type, say Y and read
7271 the Ethernet-HOWTO, available from
7272 http://www.linuxdoc.org/docs.html#howto .
7274 If you want to compile this as a module ( = code which can be
7275 inserted in and removed from the running kernel whenever you want),
7276 say M here and read Documentation/modules.txt as well as
7277 Documentation/networking/net-modules.txt. The module will be called
7280 NE2000/NE1000 support
7282 If you have a network (Ethernet) card of this type, say Y and read
7283 the Ethernet-HOWTO, available from
7284 http://www.linuxdoc.org/docs.html#howto . Many Ethernet cards
7285 without a specific driver are compatible with NE2000.
7287 If you have a PCI NE2000 card however, say N here and Y to "PCI
7288 NE2000 support", above. If you have a NE2000 card and are running on
7289 an MCA system (a bus system used on some IBM PS/2 computers and
7290 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
7293 This driver is also available as a module ( = code which can be
7294 inserted in and removed from the running kernel whenever you want).
7295 The module will be called ne.o. If you want to compile it as a
7296 module, say M here and read Documentation/modules.txt as well as
7297 Documentation/networking/net-modules.txt.
7301 If you have a network (Ethernet) card of this type, say Y and read
7302 the Ethernet-HOWTO, available from
7303 http://www.linuxdoc.org/docs.html#howto .
7305 NE/2 (ne2000 MCA version) support
7307 If you have a network (Ethernet) card of this type, say Y and read
7308 the Ethernet-HOWTO, available from
7309 http://www.linuxdoc.org/docs.html#howto .
7311 This driver is also available as a module ( = code which can be
7312 inserted in and removed from the running kernel whenever you want).
7313 The module will be called ne2.o. If you want to compile it as a
7314 module, say M here and read Documentation/modules.txt as well as
7315 Documentation/networking/net-modules.txt.
7319 These are Micro Channel ethernet adapters. You need to say Y to "MCA
7320 support" in order to use this driver. Supported cards are the SKnet
7321 Junior MC2 and the SKnet MC2(+). The driver automatically
7322 distinguishes between the two cards. Note that using multiple boards
7323 of different type hasn't been tested with this driver. Say Y if you
7324 have one of these ethernet adapters.
7326 This driver is also available as a module ( = code which can be
7327 inserted in and removed from the running kernel whenever you want).
7328 The module is called sk_mca.o. If you want to compile it as a
7329 module, say M here and read Documentation/modules.txt as well as
7330 Documentation/networking/net-modules.txt.
7332 EISA, VLB, PCI and on board controllers
7334 This is another class of network cards which attach directly to the
7335 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
7336 available from http://www.linuxdoc.org/docs.html#howto .
7338 Note that the answer to this question doesn't directly affect the
7339 kernel: saying N will just cause this configure script to skip all
7340 the questions about this class of network cards. If you say Y, you
7341 will be asked for your specific card in the following questions. If
7342 you are unsure, say Y.
7344 AMD PCnet32 (VLB and PCI) support
7346 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
7347 answer Y here and read the Ethernet-HOWTO, available from
7348 http://www.linuxdoc.org/docs.html#howto .
7350 This driver is also available as a module ( = code which can be
7351 inserted in and removed from the running kernel whenever you want).
7352 The module will be called pcnet32.o. If you want to compile it as a
7353 module, say M here and read Documentation/modules.txt as well as
7354 Documentation/networking/net-modules.txt.
7356 Ansel Communications EISA 3200 support
7358 If you have a network (Ethernet) card of this type, say Y and read
7359 the Ethernet-HOWTO, available from
7360 http://www.linuxdoc.org/docs.html#howto .
7362 This driver is also available as a module ( = code which can be
7363 inserted in and removed from the running kernel whenever you want).
7364 The module will be called ac3200.o. If you want to compile it as a
7365 module, say M here and read Documentation/modules.txt as well as
7366 Documentation/networking/net-modules.txt.
7368 Mylex EISA LNE390A/LNE390B support (EXPERIMENTAL)
7370 If you have a network (Ethernet) card of this type, say Y and read
7371 the Ethernet-HOWTO, available from
7372 http://www.linuxdoc.org/docs.html#howto .
7374 This driver is also available as a module ( = code which can be
7375 inserted in and removed from the running kernel whenever you want).
7376 The module will be called lne390.o. If you want to compile it as a
7377 module, say M here and read Documentation/modules.txt as well as
7378 Documentation/networking/net-modules.txt.
7380 Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)
7382 If you have a network (Ethernet) card of this type, say Y and read
7383 the Ethernet-HOWTO, available from
7384 http://www.linuxdoc.org/docs.html#howto . Note that this driver
7385 will NOT WORK for NE3200 cards as they are completely different.
7387 This driver is also available as a module ( = code which can be
7388 inserted in and removed from the running kernel whenever you want).
7389 The module will be called ne3210.o. If you want to compile it as a
7390 module, say M here and read Documentation/modules.txt as well as
7391 Documentation/networking/net-modules.txt.
7393 Apricot Xen-II on board Ethernet
7395 If you have a network (Ethernet) controller of this type, say Y and
7396 read the Ethernet-HOWTO, available from
7397 http://www.linuxdoc.org/docs.html#howto .
7399 If you want to compile this as a module ( = code which can be
7400 inserted in and removed from the running kernel whenever you want),
7401 say M here and read Documentation/modules.txt as well as
7402 Documentation/networking/net-modules.txt. The module will be called
7405 Generic DECchip & DIGITAL EtherWORKS PCI/EISA
7407 This is support for the DIGITAL series of PCI/EISA Ethernet cards.
7408 These include the DE425, DE434, DE435, DE450 and DE500 models. If
7409 you have a network card of this type, say Y and read the
7410 Ethernet-HOWTO, available from
7411 http://www.linuxdoc.org/docs.html#howto . More specific
7412 information is contained in Documentation/networking/de4x5.txt.
7414 This driver is also available as a module ( = code which can be
7415 inserted in and removed from the running kernel whenever you want).
7416 The module will be called de4x5.o. If you want to compile it as a
7417 module, say M here and read Documentation/modules.txt as well as
7418 Documentation/networking/net-modules.txt.
7420 DECchip Tulip (dc21x4x) PCI support
7422 This driver is developed for the SMC EtherPower series Ethernet
7423 cards and also works with cards based on the DECchip
7424 21040/21041/21140 (Tulip series) chips. Some LinkSys PCI cards are
7425 of this type. (If your card is NOT SMC EtherPower 10/100 PCI
7426 (smc9332dst), you can also try the driver for "Generic DECchip"
7427 cards, above. However, most people with a network card of this type
7428 will say Y here.) Do read the Ethernet-HOWTO, available from
7429 http://www.linuxdoc.org/docs.html#howto . More specific
7430 information is contained in Documentation/networking/tulip.txt.
7432 This driver is also available as a module ( = code which can be
7433 inserted in and removed from the running kernel whenever you want).
7434 The module will be called tulip.o. If you want to compile it as a
7435 module, say M here and read Documentation/modules.txt as well as
7436 Documentation/networking/net-modules.txt.
7438 Digi Intl. RightSwitch support
7440 This is support for the Digi International RightSwitch series of
7441 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
7442 models. If you have a network card of this type, say Y and read the
7443 Ethernet-HOWTO, available from
7444 http://www.linuxdoc.org/docs.html#howto . More specific
7445 information is contained in Documentation/networking/dgrs.txt.
7447 This driver is also available as a module ( = code which can be
7448 inserted in and removed from the running kernel whenever you want).
7449 The module will be called dgrs.o. If you want to compile it as a
7450 module, say M here and read Documentation/modules.txt as well as
7451 Documentation/networking/net-modules.txt.
7453 EtherExpress PRO/100 support
7454 CONFIG_EEXPRESS_PRO100
7455 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
7456 card, say Y and read the Ethernet-HOWTO, available from
7457 http://www.linuxdoc.org/docs.html#howto .
7459 This driver is also available as a module ( = code which can be
7460 inserted in and removed from the running kernel whenever you want).
7461 The module will be called eepro100.o. If you want to compile it as a
7462 module, say M here and read Documentation/modules.txt as well as
7463 Documentation/networking/net-modules.txt.
7465 ICL EtherTeam 16i/32 support (EXPERIMENTAL)
7467 If you have a network (Ethernet) card of this type, say Y and read
7468 the Ethernet-HOWTO, available from
7469 http://www.linuxdoc.org/docs.html#howto .
7471 This driver is also available as a module ( = code which can be
7472 inserted in and removed from the running kernel whenever you want).
7473 The module will be called eth16i.o. If you want to compile it as a
7474 module, say M here and read Documentation/modules.txt as well as
7475 Documentation/networking/net-modules.txt.
7477 TI ThunderLAN support (EXPERIMENTAL)
7479 If you have a PCI Ethernet network card based on the ThunderLAN chip
7480 which is supported by this driver, say Y and read the
7481 Ethernet-HOWTO, available from
7482 http://www.linuxdoc.org/docs.html#howto .
7484 Devices currently supported by this driver are Compaq Netelligent,
7485 Compaq NetFlex and Olicom cards. Please read the file
7486 Documentation/networking/tlan.txt for more details.
7488 This driver is also available as a module ( = code which can be
7489 inserted in and removed from the running kernel whenever you want).
7490 The module will be called tlan.o. If you want to compile it as a
7491 module, say M here and read Documentation/modules.txt as well as
7492 Documentation/networking/net-modules.txt.
7494 Please email feedback to torben.mathiasen@compaq.com.
7498 If you have a VIA "rhine" based network card (Rhine-I (3043) or
7499 Rhine-2 (VT86c100A)), say Y here.
7501 This driver is also available as a module ( = code which can be
7502 inserted in and removed from the running kernel whenever you want).
7503 The module will be called via-rhine.o. If you want to compile it as
7504 a module, say M here and read Documentation/modules.txt as well as
7505 Documentation/networking/net-modules.txt.
7507 Racal-Interlan EISA ES3210 support (EXPERIMENTAL)
7509 If you have a network (Ethernet) card of this type, say Y and read
7510 the Ethernet-HOWTO, available from
7511 http://www.linuxdoc.org/docs.html#howto .
7513 This driver is also available as a module ( = code which can be
7514 inserted in and removed from the running kernel whenever you want).
7515 The module will be called es3210.o. If you want to compile it as a
7516 module, say M here and read Documentation/modules.txt as well as
7517 Documentation/networking/net-modules.txt.
7519 SMC EtherPower II (EXPERIMENTAL)
7521 If you have an SMC EtherPower II 9432 PCI Ethernet network card
7522 which is based on the SMC83c170, say Y and read the Ethernet-HOWTO,
7523 available from http://www.linuxdoc.org/docs.html#howto .
7525 This driver is also available as a module ( = code which can be
7526 inserted in and removed from the running kernel whenever you want).
7527 The module will be called epic100.o. If you want to compile it as a
7528 module, say M here and read Documentation/modules.txt as well as
7529 Documentation/networking/net-modules.txt.
7531 SGI Seeq ethernet controller support
7533 Say Y here if you have an Seeq based Ethernet network card. This is
7534 used in many Silicon Graphics machines.
7536 Zenith Z-Note support (EXPERIMENTAL)
7538 The Zenith Z-Note notebook computer has a built-in network
7539 (Ethernet) card, and this is the Linux driver for it. Note that the
7540 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
7541 by this driver. Read the Ethernet-HOWTO, available from
7542 http://www.linuxdoc.org/docs.html#howto .
7544 Adaptec Starfire support
7545 CONFIG_ADAPTEC_STARFIRE
7546 If you have an Ethernet network card like this, say Y and read the
7547 Ethernet-HOWTO, available from
7548 http://www.linuxdoc.org/docs.html#howto .
7550 This driver is also available as a module ( = code which can be
7551 inserted in and removed from the running kernel whenever you want).
7552 The module will be called starfire.o. If you want to compile it as a
7553 module, say M here and read Documentation/modules.txt as well as
7554 Documentation/networking/net-modules.txt.
7556 Pocket and portable adapters
7558 Cute little network (Ethernet) devices which attach to the parallel
7559 port ("pocket adapters"), commonly used with laptops. If you have
7560 one of those, say Y and read the Ethernet-HOWTO, available from
7561 http://www.linuxdoc.org/docs.html#howto .
7563 If you want to plug a network (or some other) card into the PCMCIA
7564 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
7565 credit card size extension cards used by all modern laptops), you
7566 need the pcmcia-cs package (location contained in the file
7567 Documentation/Changes) and you can say N here.
7569 Laptop users should read the Linux Laptop home page at
7570 http://www.cs.utexas.edu/users/kharker/linux-laptop/ .
7572 Note that the answer to this question doesn't directly affect the
7573 kernel: saying N will just cause this configure script to skip all
7574 the questions about this class of network devices. If you say Y, you
7575 will be asked for your specific device in the following questions.
7577 AT-LAN-TEC/RealTek pocket adapter support
7579 This is a network (Ethernet) device which attaches to your parallel
7580 port. Read drivers/net/atp.c as well as the Ethernet-HOWTO,
7581 available from http://www.linuxdoc.org/docs.html#howto , if you
7582 want to use this. If you intend to use this driver, you should have
7583 said N to the Parallel Printer support, because the two drivers
7584 don't like each other.
7586 D-Link DE600 pocket adapter support
7588 This is a network (Ethernet) device which attaches to your parallel
7589 port. Read Documentation/networking/DLINK.txt as well as the
7590 Ethernet-HOWTO, available from
7591 http://www.linuxdoc.org/docs.html#howto , if you want to use
7592 this. It is possible to have several devices share a single parallel
7593 port and it is safe to compile the corresponding drivers into the
7596 If you want to compile this driver as a module however ( = code
7597 which can be inserted in and removed from the running kernel
7598 whenever you want), say M here and read Documentation/modules.txt.
7599 The module will be called de600.o.
7601 D-Link DE620 pocket adapter support
7603 This is a network (Ethernet) device which attaches to your parallel
7604 port. Read Documentation/networking/DLINK.txt as well as the
7605 Ethernet-HOWTO, available from
7606 http://www.linuxdoc.org/docs.html#howto , if you want to use
7607 this. It is possible to have several devices share a single parallel
7608 port and it is safe to compile the corresponding drivers into the
7611 If you want to compile this driver as a module however ( = code
7612 which can be inserted in and removed from the running kernel
7613 whenever you want), say M here and read Documentation/modules.txt.
7614 The module will be called de620.o.
7616 Token Ring driver support
7618 Token Ring is IBM's way of communication on a local network; the
7619 rest of the world uses Ethernet. To participate on a Token Ring
7620 network, you need a special Token ring network card. If you are
7621 connected to such a Token Ring network and want to use your Token
7622 Ring card under Linux, say Y here and to the driver for your
7623 particular card below and read the Token-Ring mini-HOWTO, available
7624 from http://www.linuxdoc.org/docs.html#howto . Most people can
7627 IBM Tropic chipset based adapter support
7629 This is support for all IBM Token Ring cards that don't use DMA. If
7630 you have such a beast, say Y and read the Token-Ring mini-HOWTO,
7631 available from http://www.linuxdoc.org/docs.html#howto .
7633 Warning: this driver will almost definitely fail if more than one
7634 active Token Ring card is present.
7636 This driver is also available as a module ( = code which can be
7637 inserted in and removed from the running kernel whenever you want).
7638 The module will be called ibmtr.o. If you want to compile it as a
7639 module, say M here and read Documentation/modules.txt.
7641 IBM Olympic chipset PCI adapter support
7643 This is support for all non-Lanstreamer IBM PCI Token Ring Cards.
7644 Specifically this is all IBM PCI, PCI Wake On Lan, PCI II, PCI II
7645 Wake On Lan, and PCI 100/16/4 adapters.
7647 If you have such an adapter, say Y and read the Token-Ring
7648 mini-HOWTO, available from
7649 http://www.linuxdoc.org/docs.html#howto .
7651 This driver is also available as a module ( = code which can be
7652 inserted in and removed from the running kernel whenever you want).
7653 The module will will be called olympic.o. If you want to compile it
7654 as a module, say M here and read Documentation/modules.txt.
7656 Also read the file Documentation/networking/olympic.txt or check the
7657 Linux Token Ring Project site for the latest information at
7658 http://www.linuxtr.net
7660 Generic TMS380 Token Ring ISA/PCI/MCA/EISA adapter support
7662 This driver provides generic support for token ring adapters
7663 based on the Texas Instruments TMS380 series chipsets. This
7664 includes the SysKonnect TR4/16(+) ISA (SK-4190), SysKonnect
7665 TR4/16(+) PCI (SK-4590), SysKonnect TR4/16 PCI (SK-4591),
7666 Compaq 4/16 PCI, Thomas-Conrad TC4048 4/16 PCI, and several
7667 Madge adapters. If selected, you will be asked to select
7668 which cards to support below. If you're using modules, each
7669 class of card will be supported by a seperate module.
7671 If you have such an adapter and would like to use it, say Y or M and
7672 read the Token-Ring mini-HOWTO, available from
7673 http://www.linuxdoc.org/docs.html#howto .
7675 Also read the file linux/Documentation/networking/tms380tr.txt or check
7676 http://www.auk.cx/tms380tr/
7678 Generic TMS380 PCI support
7680 This tms380 module supports generic TMS380-based PCI cards.
7682 These cards are known to work:
7683 - Compaq 4/16 TR PCI
7684 - SysKonnect TR4/16 PCI (SK-4590/SK-4591)
7685 - Thomas-Conrad TC4048 PCI 4/16
7686 - 3Com Token Link Velocity
7688 Madge Smart 16/4 PCI Mk2 support
7690 This tms380 module supports the Madge Smart 16/4 PCI Mk2 cards (51-02).
7692 Madge Smart 16/4 Ringode MicroChannel
7694 This tms380 module supports the Madge Smart 16/4 MC16 and MC32
7695 MicroChannel adapters
7697 SMC ISA TokenRing adapter support
7699 This is support for the ISA and MCA SMC Token Ring cards, specifically
7700 SMC TokenCard Elite (8115T) and SMC TokenCard Elite/A (8115T/A) adapters.
7702 If you have such an adapter and would like to use it, say Y or M and
7703 read the Token-Ring mini-HOWTO, available from
7704 http://www.linuxdoc.org/docs.html#howto .
7706 Traffic Shaper (EXPERIMENTAL)
7708 The traffic shaper is a virtual network device that allows you to
7709 limit the rate of outgoing data flow over some other network device.
7710 The traffic that you want to slow down can then be routed through
7711 these virtual devices. See Documentation/networking/shaper.txt for
7714 An alternative to this traffic shaper is the experimental
7715 Class-Based Queueing (CBQ) scheduling support which you get if you
7716 say Y to "QoS and/or fair queueing" above.
7718 To set up and configure shaper devices, you need the shapecfg
7719 program, available from ftp://shadow.cabi.net/pub/Linux in the
7722 This driver is also available as a module ( = code which can be
7723 inserted in and removed from the running kernel whenever you want).
7724 The module will be called shaper.o. If you want to compile it as a
7725 module, say M here and read Documentation/modules.txt. If unsure,
7730 Fiber Distributed Data Interface is a high speed local area network
7731 design; essentially a replacement for high speed Ethernet. FDDI can
7732 run over copper or fiber. If you are connected to such a network and
7733 want a driver for the FDDI card in your computer, say Y here (and
7734 then also Y to the driver for your FDDI card, below). Most people
7737 Digital DEFEA and DEFPA adapter support
7739 This is support for the DIGITAL series of EISA (DEFEA) and PCI
7740 (DEFPA) controllers which can connect you to a local FDDI network.
7742 HIgh Performance Parallel Interface support (EXPERIMENTAL)
7744 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
7745 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
7746 can run over copper (25m) or fiber (300m on multi-mode or 10km on
7747 single-mode). HIPPI networks are commonly used for clusters and to
7748 connect to super computers. If you are connected to a HIPPI network
7749 and have a HIPPI network card in your computer that you want to use
7750 under Linux, say Y here (you must also remember to enable the driver
7751 for your HIPPI card below). Most people will say N here.
7753 Essential RoadRunner HIPPI PCI adapter support
7755 Say Y here if this is your PCI HIPPI network card.
7757 This driver is also available as a module ( = code which can be
7758 inserted in and removed from the running kernel whenever you want).
7759 The module will be called rrunner.o. If you want to compile it as
7760 a module, say M here and read Documentation/modules.txt. If unsure,
7763 Use large TX/RX rings
7764 CONFIG_ROADRUNNER_LARGE_RINGS
7765 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
7766 of additional memory to allow for fastest operation, both for
7767 transmitting and receiving. This memory cannot be used by any other
7768 kernel code or by user space programs. Say Y here only if you have
7773 If you have an Acorn system with one of these (AKA25) network cards,
7774 you should say Y to this option if you wish to use it with Linux.
7776 Acorn/ANT Ether3 card
7778 If you have an Acorn system with one of these network cards, you
7779 should say Y to this option if you wish to use it with Linux.
7783 If you have an Acorn system with one of these network cards, you
7784 should say Y to this option if you wish to use it with Linux.
7786 EBSA-110 Ethernet interface
7787 CONFIG_ARM_AM79C961A
7788 If you wish to compile a kernel for the EBSA-110, then you should
7789 always answer Y to this.
7791 Support CDROM drives that are not SCSI or IDE/ATAPI
7792 CONFIG_CD_NO_IDESCSI
7793 If you have a CDROM drive that is neither SCSI nor IDE/ATAPI, say Y
7794 here, otherwise N. Read the CDROM-HOWTO, available from
7795 http://www.linuxdoc.org/docs.html#howto .
7797 Note that the answer to this question doesn't directly affect the
7798 kernel: saying N will just cause this configure script to skip all
7799 the questions about these CDROM drives. If you are unsure what you
7800 have, say Y and find out whether you have one of the following
7803 For each of these drivers, a file Documentation/cdrom/<driver_name>
7804 exists. Especially in cases where you do not know exactly which kind
7805 of drive you have you should read there. Most of these drivers use a
7806 file drivers/cdrom/<driver_name>.h where you can define your
7807 interface parameters and switch some internal goodies.
7809 All these CDROM drivers are also usable as a module ( = code which
7810 can be inserted in and removed from the running kernel whenever you
7811 want). If you want to compile them as module, say M instead of Y and
7812 read Documentation/modules.txt.
7814 If you want to use any of these CDROM drivers, you also have to
7815 answer Y or M to "ISO 9660 CDROM filesystem support" below (this
7816 answer will get "defaulted" for you if you enable any of the Linux
7819 Sony CDU31A/CDU33A CDROM support
7821 These CDROM drives have a spring-pop-out caddyless drawer, and a
7822 rectangular green LED centered beneath it. NOTE: these CDROM drives
7823 will not be auto detected by the kernel at boot time; you have to
7824 provide the interface address as an option to the kernel at boot
7825 time as described in Documentation/cdrom/cdu31a or fill in your
7826 parameters into drivers/cdrom/cdu31a.c. Try "man bootparam" or
7827 see the documentation of your boot loader (lilo or loadlin) about
7828 how to pass options to the kernel. The lilo procedure is also
7829 explained in the SCSI-HOWTO.
7831 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7832 filesystem support" below, because that's the filesystem used on
7835 This driver is also available as a module ( = code which can be
7836 inserted in and removed from the running kernel whenever you want).
7837 The module will be called cdu31a.o. If you want to compile it as a
7838 module, say M here and read Documentation/modules.txt.
7840 Standard Mitsumi [no XA/Multisession] CDROM support
7842 This is the older of the two drivers for the older Mitsumi models
7843 LU-005, FX-001 and FX-001D. This is not the right driver for the
7844 FX-001DE and the triple or quad speed models (all these are
7845 IDE/ATAPI models). Please also the file Documentation/cdrom/mcd.
7847 With the old LU-005 model, the whole drive chassis slides out for cd
7848 insertion. The FX-xxx models use a motorized tray type mechanism.
7849 Note that this driver does not support XA or MultiSession CDs
7850 (PhotoCDs). There is a new driver (next question) which can do
7851 this. If you want that one, say N here.
7853 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7854 filesystem support" below, because that's the filesystem used on
7857 This driver is also available as a module ( = code which can be
7858 inserted in and removed from the running kernel whenever you want).
7859 The module will be called mcd.o. If you want to compile it as a
7860 module, say M here and read Documentation/modules.txt.
7862 IRQ channel for Mitsumi CD-ROM
7864 This allows you to specify the default value of the IRQ used by the
7865 driver. This setting can be overridden by passing the "mcd="
7866 parameter to the kernel at boot time (or at module load time if you
7867 said M to "Standard Mitsumi CDROM support").
7869 I/O base address for Mitsumi CD-ROM
7871 This allows you to specify the default value of the I/O base address
7872 used by the driver. This setting can be overridden by passing the
7873 "mcd=" parameter to the kernel at boot time (or at module load time
7874 if you said M to "Standard Mitsumi CDROM support").
7876 Mitsumi [XA/MultiSession] support
7878 Use this driver if you want to be able to read XA or MultiSession
7879 CDs (PhotoCDs) as well as ordinary CDs with your Mitsumi LU-005,
7880 FX-001 or FX-001D CDROM drive. In addition, this driver uses much
7881 less kernel memory than the old one, if that is a concern. This
7882 driver is able to support more than one drive, but each drive needs
7883 a separate interface card. Please read the file
7884 Documentation/cdrom/mcdx.
7886 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7887 filesystem support" below, because that's the filesystem used on
7890 This driver is also available as a module ( = code which can be
7891 inserted in and removed from the running kernel whenever you want).
7892 The module will be called mcdx.o. If you want to compile it as a
7893 module, say M here and read Documentation/modules.txt.
7895 Matsushita/Panasonic/Creative, Longshine, TEAC CDROM support
7897 This driver supports most of the drives which use the Panasonic or
7898 Sound Blaster interface. Please read the file
7899 Documentation/cdrom/sbpcd.
7901 The Matsushita CR-521, CR-522, CR-523, CR-562, CR-563 drives
7902 (sometimes labeled "Creative"), the Creative Labs CD200, the
7903 Longshine LCS-7260, the "IBM External ISA CDROM" (in fact a CR-56x
7904 model), the TEAC CD-55A fall under this category. Some other
7905 "electrically compatible" drives (Vertos, Genoa, some Funai models)
7906 are currently not supported; for the Sanyo H94A drive currently a
7907 separate driver (asked later) is responsible. Most drives have a
7908 uniquely shaped faceplate, with a caddyless motorized drawer, but
7909 without external brand markings. The older CR-52x drives have a
7910 caddy and manual loading/eject, but still no external markings. The
7911 driver is able to do an extended auto-probing for interface
7912 addresses and drive types; this can help to find facts in cases you
7913 are not sure, but can consume some time during the boot process if
7914 none of the supported drives gets found. Once your drive got found,
7915 you should enter the reported parameters into drivers/cdrom/sbpcd.h
7916 and set "DISTRIBUTION 0" there.
7918 This driver can support up to four CDROM controller cards, and each
7919 card can support up to four CDROM drives; if you say Y here, you
7920 will be asked how many controller cards you have. If compiled as a
7921 module, only one controller card (but with up to four drives) is
7924 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7925 filesystem support" below, because that's the filesystem used on
7928 This driver is also available as a module ( = code which can be
7929 inserted in and removed from the running kernel whenever you want).
7930 The module will be called sbpcd.o. If you want to compile it as a
7931 module, say M here and read Documentation/modules.txt.
7933 Matsushita/Panasonic, ... second CDROM controller support
7935 Say Y here only if you have two CDROM controller cards of this type
7936 (usually only if you have more than four drives). You should enter
7937 the parameters for the second, third and fourth interface card into
7938 linux/include/linux/sbpcd.h before compiling the new kernel. Read
7939 the file Documentation/cdrom/sbpcd.
7941 Aztech/Orchid/Okano/Wearnes/TXC/CyDROM CDROM support
7943 This is your driver if you have an Aztech CDA268-01A, Orchid
7944 CD-3110, Okano or Wearnes CDD110, Conrad TXC, or CyCDROM CR520 or
7945 CR540 CDROM drive. This driver -- just like all these CDROM drivers
7946 -- is NOT for CDROM drives with IDE/ATAPI interfaces, such as Aztech
7947 CDA269-031SE. Please read the file Documentation/cdrom/aztcd.
7949 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7950 filesystem support" below, because that's the filesystem used on
7953 This driver is also available as a module ( = code which can be
7954 inserted in and removed from the running kernel whenever you want).
7955 The module will be called aztcd.o. If you want to compile it as a
7956 module, say M here and read Documentation/modules.txt.
7958 Sony CDU535 CDROM support
7960 This is the driver for the older Sony CDU-535 and CDU-531 CDROM
7961 drives. Please read the file Documentation/cdrom/sonycd535.
7963 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7964 filesystem support" below, because that's the filesystem used on
7967 This driver is also available as a module ( = code which can be
7968 inserted in and removed from the running kernel whenever you want).
7969 The module will be called sonycd535.o. If you want to compile it as
7970 a module, say M here and read Documentation/modules.txt.
7972 Goldstar R420 CDROM support
7974 If this is your CDROM drive, say Y here. As described in the file
7975 linux/Documentation/cdrom/gscd, you might have to change a setting
7976 in the file linux/drivers/cdrom/gscd.h before compiling the
7977 kernel. Please read the file Documentation/cdrom/gscd.
7979 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7980 filesystem support" below, because that's the filesystem used on
7983 This driver is also available as a module ( = code which can be
7984 inserted in and removed from the running kernel whenever you want).
7985 The module will be called gscd.o. If you want to compile it as a
7986 module, say M here and read Documentation/modules.txt.
7988 Philips/LMS CM206 CDROM support
7990 If you have a Philips/LMS CDROM drive cm206 in combination with a
7991 cm260 host adapter card, say Y here. Please also read the file
7992 Documentation/cdrom/cm206.
7994 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
7995 filesystem support" below, because that's the filesystem used on
7998 This driver is also available as a module ( = code which can be
7999 inserted in and removed from the running kernel whenever you want).
8000 The module will be called cm206.o. If you want to compile it as a
8001 module, say M here and read Documentation/modules.txt.
8003 Optics Storage DOLPHIN 8000AT CDROM support
8005 This is the driver for the 'DOLPHIN' drive with a 34-pin Sony
8006 compatible interface. It also works with the Lasermate CR328A. If
8007 you have one of those, say Y. This driver does not work for the
8008 Optics Storage 8001 drive; use the IDE-ATAPI CDROM driver for that
8009 one. Please read the file Documentation/cdrom/optcd.
8011 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
8012 filesystem support" below, because that's the filesystem used on
8015 This driver is also available as a module ( = code which can be
8016 inserted in and removed from the running kernel whenever you want).
8017 The module will be called optcd.o. If you want to compile it as a
8018 module, say M here and read Documentation/modules.txt.
8020 Sanyo CDR-H94A CDROM support
8022 If this is your CDROM drive, say Y here and read the file
8023 Documentation/cdrom/sjcd. You should then also say Y or M to
8024 "ISO 9660 CDROM filesystem support" below, because that's the
8025 filesystem used on CDROMs.
8027 This driver is also available as a module ( = code which can be
8028 inserted in and removed from the running kernel whenever you want).
8029 The module will be called sjcd.o. If you want to compile it as a
8030 module, say M here and read Documentation/modules.txt.
8032 Soft configurable cdrom interface card support
8034 If you want to include boot-time initialization of any cdrom
8035 interface card that is software configurable, say Y here. Currently
8036 only the ISP16/MAD16/Mozart sound cards with built-in cdrom
8037 interfaces are supported.
8039 Note that the answer to this question doesn't directly affect the
8040 kernel: saying N will just cause this configure script to skip all
8041 the questions about these CDROM drives.
8043 ISP16/MAD16/Mozart soft configurable cdrom interface support
8045 These are sound cards with built-in cdrom interfaces using the OPTi
8046 82C928 or 82C929 chips. Say Y here to have them detected and
8047 possibly configured at boot time. In addition, You'll have to say Y
8048 to a driver for the particular cdrom drive you have attached to the
8049 card. Read Documentation/cdrom/isp16 for details.
8051 This driver is also available as a module ( = code which can be
8052 inserted in and removed from the running kernel whenever you want).
8053 The module will be called isp16.o. If you want to compile it as a
8054 module, say M here and read Documentation/modules.txt.
8058 If you say Y here, you will be able to set per user limits for disk
8059 usage (also called disk quotas). Currently, it works only for the
8060 ext2 filesystem. You need additional software in order to use quota
8061 support; for details, read the Quota mini-HOWTO, available from
8062 http://www.linuxdoc.org/docs.html#howto . Probably the quota
8063 support is only useful for multi user systems. If unsure, say N.
8067 Universal Serial Bus (USB) is a specification for a serial bus
8068 subsystem which offers higher speeds and more features than the
8069 traditional PC serial port. The bus supplies power to peripherals
8070 and allows for hot swapping. Up to 127 USB peripherals can be
8071 connected to a single USB port in a tree structure. The USB port is
8072 the root of the tree, the peripherals are the leaves, and the inner
8073 nodes are special USB devices called hubs. Many newer PCs have USB
8074 ports and newer peripherals such as scanners, keyboards, mice,
8075 modems, and printers support the USB protocol and can be connected
8076 to the PC via those ports.
8078 Say Y here if your computer has a USB port and you want to
8079 use USB devices. You then need to say Y to at least one
8080 of "UHCI support" or "OHCI support" below (the type of interface
8081 that the USB hardware in your computer provides) and then choose
8082 from among the drivers for USB peripherals.
8084 This code is also available as a module ( = code which can be
8085 inserted in and removed from the running kernel whenever you want).
8086 The module will be called usbcore.o. If you want to compile it as a
8087 module, say M here and read Documentation/modules.txt.
8089 UHCI (intel PIIX4, VIA, ...) support?
8091 The Universal Host Controller Interface is a standard by Intel for
8092 accessing the USB hardware in the PC (which is also called the USB
8093 host controller). If your USB host controller conforms to this
8094 standard, say Y. All recent boards with Intel PCI chipsets (like
8095 intel 430TX, 440FX, 440LX, 440BX, i810, i820) conform to this standard.
8096 Also all VIA PCI chipsets (like VIA VP2, VP3, MVP3, Apollo Pro, Apollo
8097 Pro II or Apollo Pro 133).
8100 This code is also available as a module ( = code which can be
8101 inserted in and removed from the running kernel whenever you want).
8102 The module will be called usb-uhci.o. If you want to compile it as a
8103 module, say M here and read Documentation/modules.txt.
8105 USB-UHCI High Bandwidth support
8106 CONFIG_USB_UHCI_HIGH_BANDWIDTH
8107 This option enables the so called reclamation loop in usb-uhci, thus
8108 allowing much higher transfer bandwidth for USB-bulk and control
8109 messages; isochronous transfers (audio, video etc.) are not affected.
8110 Due to a very simple design of the UHCI controller, this may cause
8111 a significant PCI congestion under certain conditions. If you are
8112 experiencing a system slowdown, disable this option.
8116 UHCI (intel PIIX4, VIA, ...) alternate (JE) support?
8118 This is an alternate driver for UHCI support. It has been commonly
8119 been referred to as the "JE driver".
8121 The Universal Host Controller Interface is a standard by Intel for
8122 accessing the USB hardware in the PC (which is also called the USB
8123 host controller). If your USB host controller conforms to this
8124 standard, say Y. All recent boards with Intel PCI chipsets (like
8125 intel 430TX, 440FX, 440LX, 440BX, i810, i820) conform to this standard.
8126 Also all VIA PCI chipsets (like VIA VP2, VP3, MVP3, Apollo Pro, Apollo
8127 Pro II or Apollo Pro 133).
8130 This code is also available as a module ( = code which can be
8131 inserted in and removed from the running kernel whenever you want).
8132 The module will be called uhci.o. If you want to compile it as a
8133 module, say M here and read Documentation/modules.txt.
8135 OHCI (Compaq, iMacs, OPTi, SiS, ALi, ...) support?
8137 The Open Host Controller Interface is a standard by
8138 Compaq/Microsoft/National for accessing the USB PC hardware (also
8139 called USB host controller). If your USB host controller conforms
8140 to this standard, say Y. The USB host controllers on most
8141 non-Intel architectures and on several x86 compatibles with non-Intel
8142 chipsets - like SiS (actual 610, 610 and so on) or ALi (ALi IV, ALi V,
8143 Aladdin Pro..) - conform to this standard.
8145 You may want to read the file Documentation/usb/ohci.txt.
8147 This code is also available as a module ( = code which can be
8148 inserted in and removed from the running kernel whenever you want).
8149 The module will be called usb-ohci.o. If you want to compile it
8150 as a module, say M here and read Documentation/modules.txt.
8152 USB Human Interface Device (HID) support
8154 Say Y here if you want to connect a keyboard, mouse, joystick,
8155 graphic tablet, UPS or any other HID based devices to your computer
8158 USB HIDBP Keyboard support
8160 Say Y here if you don't want to use the generic HID driver for your
8161 USB keyboard and prefer to use the keyboard in its limited Boot
8162 Protocol mode. This driver is much smaller than the HID one.
8164 USB HIDBP Mouse support
8166 Say Y here if you don't want to use the generic HID driver for your
8167 USB mouse and prefer to use the mouse in its limited Boot Protocol
8168 mode. This driver is much smaller than the HID one.
8170 Wacom Graphire tablet support
8172 Say Y here if you want to use the USB version of the Wacom
8173 Graphire tablet. Make sure you select Mouse and Event support,
8174 don't select HID support, because this driver collides with it.
8175 Use HIDBP support for keyboards and mice instead if you need it.
8177 Logitech WingMan Force joystick support
8179 Say Y here if you want to use the Logitech WingMan Force with Linux
8180 on the USB port. No force-feedback support yet, but other than that,
8181 it should work like a normal joystick.
8184 CONFIG_INPUT_KEYBDEV
8185 Say Y here if you want your USB HID keyboard to be able to serve as
8189 CONFIG_INPUT_MOUSEDEV
8190 Say Y here if you want your USB HID mouse to be accessible as
8191 misc devices 32+ under /dev/, as an emulated PS/2 mouse.
8193 Mix all mice into one device
8194 CONFIG_INPUT_MOUSEDEV_MIX
8195 Say Y here if you want input from all your USB HID mice to be mixed
8196 into one misc device. If you say N, you'll have a separate
8197 device for each your USB mouse.
8199 Support for digitizers
8200 CONFIG_INPUT_MOUSEDEV_DIGITIZER
8201 Use this if you have a digitizer that doesn't emulate a mouse
8202 itself, and want to use it as a mouse.
8204 Horizontal screen resolution
8205 CONFIG_INPUT_MOUSEDEV_SCREEN_X
8206 For the mouse emulation to be correct, the mousedev driver needs
8207 to know the screen resolution you are using (in X).
8209 Vertical screen resolution
8210 CONFIG_INPUT_MOUSEDEV_SCREEN_Y
8211 For the mouse emulation to be correct, the mousedev driver needs
8212 to know the screen resolution you are using (in X).
8216 Say Y here if you want your USB HID joystick or gamepad to be
8217 accessible as /dev/js device. You can't use a normal joystick
8220 Event interface support
8222 Say Y here if you want your USB HID device events be accessible
8223 under /dev/inputX (misc 64+) in a generic way.
8224 This is the future ...
8228 Say Y here if you want to connect a USB scanner to your
8229 computer's USB port. Please read Documentation/usb/scanner.txt
8230 and Documentation/usb/scanner-hp-sane.txt for more information.
8232 This code is also available as a module ( = code which can be
8233 inserted in and removed from the running kernel whenever you want).
8234 The module will be called hp_scanner.o. If you want to compile it as
8235 a module, say M here and read Documentation/modules.txt.
8239 Say Y here if you want to connect USB audio equipment such as
8240 speakers to your computer's USB port.
8242 This code is also available as a module ( = code which can be
8243 inserted in and removed from the running kernel whenever you want).
8244 The module will be called audio.o. If you want to compile it as a
8245 module, say M here and read Documentation/modules.txt.
8247 USB Modem (CDC ACM) support
8249 This driver supports USB modems and ISDN adapters which support the
8250 Communication Device Class Abstract Control Model interface.
8252 This code is also available as a module ( = code which can be
8253 inserted in and removed from the running kernel whenever you want).
8254 The module will be called acm.o. If you want to compile it as a
8255 module, say M here and read Documentation/modules.txt.
8257 USB Serial converter support
8259 Say Y here if you want to connect a Connect Tech WhiteHEAT
8260 multi-port USB to serial converter; a Belkin, Peracom, or eTek
8261 single port USB to serial converter; or a Handspring Visor.
8262 Please read Documentation/usb/usb-serial.txt for more information.
8264 This code is also available as a module ( = code which can be
8265 inserted in and removed from the running kernel whenever you want).
8266 The module will be called usb-serial.o. If you want to compile it
8267 as a module, say M here and read Documentation/modules.txt.
8269 USB Generic Serial Driver
8270 CONFIG_USB_SERIAL_GENERIC
8271 Say Y here if you want to use the generic USB serial driver.
8272 Please read Documentation/usb/usb-serial.txt for more information
8273 on using this driver. It is recommended that the USB Serial
8274 Driver be compiled as a module for this driver to be used properly.
8276 USB ConnectTech WhiteHEAT Serial Driver
8277 CONFIG_USB_SERIAL_WHITEHEAT
8278 Say Y here if you want to use a ConnectTech WhiteHEAT 4 port
8279 USB to serial converter device.
8281 USB Handspring Visor Driver
8282 CONFIG_USB_SERIAL_VISOR
8283 Say Y here if you want to connect to your HandSpring Visor through
8284 its USB docking station. See http://usbvisor.sourceforge.net for
8285 more information on using this driver.
8289 Say Y here if you want to connect a USB printer to your computer's USB
8292 This code is also available as a module ( = code which can be
8293 inserted in and removed from the running kernel whenever you want).
8294 The module will be called printer.o. If you want to compile it as a
8295 module, say M here and read Documentation/modules.txt.
8297 USB CPiA Camera support
8299 Say Y here if you want to connect this type of camera to your
8300 computer's USB port.
8302 This driver uses the Video For Linux API. You must enable
8303 (Y or M in config) Video For Linux (under Character Devices)
8304 to use this driver. Information on this API and pointers to
8305 "v4l" programs may be found on the WWW at
8306 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
8308 This code is also available as a module ( = code which can be
8309 inserted in and removed from the running kernel whenever you want).
8310 The module will be called cpia.o. If you want to compile it as a
8311 module, say M here and read Documentation/modules.txt.
8313 USB IBM (Xirlink) C-It Camera support
8315 Say Y here if you want to connect this type of camera to your
8316 computer's USB port.
8318 This driver uses the Video For Linux API. You must enable
8319 (Y or M in config) Video For Linux (under Character Devices)
8320 to use this driver. Information on this API and pointers to
8321 "v4l" programs may be found on the WWW at
8322 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
8324 This code is also available as a module ( = code which can be
8325 inserted in and removed from the running kernel whenever you want).
8326 The module will be called ibmcam.o. If you want to compile it as a
8327 module, say M here and read Documentation/modules.txt. This camera
8328 has several configuration options which can be specified when you
8329 load the module. Read Documentation/usb/ibmcam.txt to learn more.
8331 USB OV511 Camera support
8333 Say Y here if you want to connect this type of camera to your
8334 computer's USB port. See Documentation/usb/ov511.txt for more
8335 information and for a list of supported cameras.
8337 This driver uses the Video For Linux API. You must enable
8338 (Y or M in config) Video For Linux (under Character Devices)
8339 to use this driver. Information on this API and pointers to
8340 "v4l" programs may be found on the WWW at
8341 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
8343 This code is also available as a module ( = code which can be
8344 inserted in and removed from the running kernel whenever you want).
8345 The module will be called ov511.o. If you want to compile it as a
8346 module, say M here and read Documentation/modules.txt.
8348 USB Kodak DC-2xx Camera support
8350 Say Y here if you want to connect this type of still camera to
8351 your computer's USB port. See Documentation/usb/dc2xx.txt for more
8352 information; some non-Kodak cameras may also work with this
8353 driver, given application support (such as www.gPhoto.org).
8355 This code is also available as a module ( = code which can be
8356 inserted in and removed from the running kernel whenever you want).
8357 The module will be called dc2xx.o. If you want to compile it as a
8358 module, say M here and read Documentation/modules.txt.
8360 USB Mass Storage support
8362 Say Y here if you want to connect USB mass storage devices to your
8363 computer's USB port.
8365 This code is also available as a module ( = code which can be
8366 inserted in and removed from the running kernel whenever you want).
8367 The module will be called usb-storage.o. If you want to compile it
8368 as a module, say M here and read Documentation/modules.txt.
8370 USB Mass Storage verbose debug
8371 CONFIG_USB_STORAGE_DEBUG
8372 Say Y here in order to have the USB Mass Storage code generate
8373 verbose debugging messages.
8375 USS720 parport driver
8377 This driver is for USB parallel port adapters that use the Lucent
8378 Technologies USS-720 chip. These adapters provide USB compatibility
8379 to peripherals designed with parallel port interfaces.
8381 The chip has two modes: automatic mode and manual mode. In automatic
8382 mode, it looks to the computer like a standard USB printer. Only
8383 printers may be connected to the USS-720 in this mode. The generic
8384 USB printer driver ("USB Printer support", above) may be used in
8385 that mode, and you can say N here if you want to use the chip only
8388 Manual mode is not limited to printers, any parallel port
8389 device should work. This driver utilizes manual mode.
8390 Note however that some operations are three orders of magnitude
8391 slower than on a PCI/ISA Parallel Port, so timing critical
8392 applications might not work.
8394 Say Y here if you own an USS-720 USB->Parport cable and intend to
8395 connect anything other than a printer to it.
8397 This code is also available as a module ( = code which can be
8398 inserted in and removed from the running kernel whenever you want).
8399 The module will be called uss720.o. If you want to compile it as a
8400 module, say M here and read Documentation/modules.txt.
8402 USB device filesystem
8404 This file system implements a "devices" file, that lists
8405 the currently connected to your USB busses, a "drivers" file
8406 that lists the USB kernel client drivers currently loaded,
8407 and for every connected device a file named "xxx/yyy", where
8408 xxx is the bus number and yyy the device number, that can be used
8409 by userspace drivers to talk to the device.
8411 Most users want to say Y here.
8415 A Digital Audio Broadcasting (DAB) Receiver for USB and Linux brought
8416 to you by the DAB-Team (http://dab.in.tum.de).
8417 This driver can be taken as an example for URB-based bulk, control, and
8418 isochronous transactions.
8420 This code is also available as a module ( = code which can be
8421 inserted in and removed from the running kernel whenever you want).
8422 The module will be called dabusb.o. If you want to compile it as a
8423 module, say M here and read Documentation/modules.txt.
8427 A driver for the Prolific PL-2302 USB to USB network device. This 'USB
8428 cable' connects two hosts via a point to point network with bandwidth of
8429 5Mbit/s. Configure this driver after connecting the USB cable via
8430 ifconfig plusb0 10.0.0.1 pointopoint 10.0.0.2
8431 (and vice versa on the other host).
8435 Advanced Configuration and Power Interface (ACPI) is an interface
8436 specification to support power management of peripherals. If your
8437 system supports it, say Y here.
8441 Minix is a simple operating system used in many classes about OS's.
8442 The minix filesystem (method to organize files on a hard disk
8443 partition or a floppy disk) was the original filesystem for Linux,
8444 but has been superseded by the second extended filesystem ext2fs.
8445 You don't want to use the minix filesystem on your hard disk because
8446 of certain built-in restrictions, but it is sometimes found on older
8447 Linux floppy disks. This option will enlarge your kernel by about
8448 28 kB. If unsure, say N.
8450 If you want to compile this as a module ( = code which can be
8451 inserted in and removed from the running kernel whenever you want),
8452 say M here and read Documentation/modules.txt. The module will be
8453 called minix.o. Note that the filesystem of your root partition (the
8454 one containing the directory /) cannot be compiled as a module.
8456 Second extended fs support
8458 This is the de facto standard Linux filesystem (method to organize
8459 files on a storage device) for hard disks.
8461 You want to say Y here, unless you intend to use Linux exclusively
8462 from inside a DOS partition using the umsdos filesystem. The
8463 advantage of the latter is that you can get away without
8464 repartitioning your hard drive (which often implies backing
8465 everything up and restoring afterwards); the disadvantage is that
8466 Linux becomes susceptible to DOS viruses and that umsdos is somewhat
8467 slower than ext2fs. Even if you want to run Linux in this fashion,
8468 it might be a good idea to have ext2fs around: it enables you to
8469 read more floppy disks and facilitates the transition to a *real*
8470 Linux partition later. Another (rare) case which doesn't require
8471 ext2fs is a diskless Linux box which mounts all files over the
8472 network using NFS (in this case it's sufficient to say Y to "NFS
8473 filesystem support" below). Saying Y here will enlarge your kernel
8476 The Ext2fs-Undeletion mini-HOWTO, available from
8477 http://www.linuxdoc.org/docs.html#howto , gives information about
8478 how to retrieve deleted files on ext2fs filesystems.
8480 To change the behavior of ext2 filesystems, you can use the tune2fs
8481 utility ("man tune2fs"). To modify attributes of files and
8482 directories on ext2 filesystems, use chattr ("man chattr").
8484 Ext2fs partitions can be read from within DOS using the ext2tool
8485 command line tool package (available via FTP (user: anonymous) from
8486 ftp://metalab.unc.edu/pub/Linux/system/filesystems/ext2 ) and from
8487 within Windows NT using the ext2nt command line tool package from
8488 ftp://metalab.unc.edu/pub/Linux/utils/dos . Explore2fs is a graphical
8489 explorer for ext2fs partitions which runs on Windows 95 and Windows
8490 NT and includes experimental write support; it is available from
8491 http://jnewbigin-pc.it.swin.edu.au/Linux/Explore2fs.htm .
8493 If you want to compile this filesystem as a module ( = code which
8494 can be inserted in and removed from the running kernel whenever you
8495 want), say M here and read Documentation/modules.txt. The module
8496 will be called ext2.o. Be aware however that the filesystem of your
8497 root partition (the one containing the directory /) cannot be
8498 compiled as a module, and so this could be dangerous. Most everyone
8499 wants to say Y here.
8501 SCO UnixWare BFS Support
8503 Boot Filesystem (BFS) is a filesystem used under SCO UnixWare to
8504 allow bootloader access the kernel image and other important files
8505 during the boot process. It is usually mounted under /stand and
8506 corresponds to the slice marked as "STAND" in the UnixWare
8507 partition. This is useful if you want to access files on your /stand
8508 slice from Linux. More information on this filesystem can be found in
8509 Documentation/filesystems/bfs.txt file. If you do not know what it is,
8512 If you want to compile this as a module ( = code which can be
8513 inserted in and removed from the running kernel whenever you want),
8514 say M here and read Documentation/modules.txt. The module will be
8515 called bfs.o. Note that the filesystem of your root partition (the
8516 one containing the directory /) cannot be compiled as a module.
8518 ISO 9660 CDROM filesystem support
8520 This is the standard filesystem used on CDROMs. It was previously
8521 known as "High Sierra Filesystem" and is called "hsfs" on other Unix
8522 systems. The so-called Rock-Ridge extensions which allow for long
8523 Unix filenames and symbolic links are also supported by this driver.
8524 If you have a CDROM drive and want to do more with it than just
8525 listen to audio CDs and watch its LEDs, say Y (and read
8526 Documentation/filesystems/isofs.txt and the CDROM-HOWTO, available
8527 from http://www.linuxdoc.org/docs.html#howto ), thereby
8528 enlarging your kernel by about 27 KB; otherwise say N.
8530 If you want to compile this as a module ( = code which can be
8531 inserted in and removed from the running kernel whenever you want),
8532 say M here and read Documentation/modules.txt. The module will be
8535 Microsoft Joliet CDROM extensions
8537 Joliet is a Microsoft extension for the ISO 9660 CDROM filesystem
8538 which allows for long filenames in unicode format (unicode is the
8539 new 16 bit character code, successor to ASCII, which encodes the
8540 characters of almost all languages of the world; see
8541 http://www.unicode.org for more information). Say Y here if you want
8542 to be able to read Joliet CDROMs under Linux.
8544 UDF Filesystem support (read only)
8546 This is the new filesystem used by some CDROMS and DVD drivers. Say
8547 Y if you intend to mount DVD discs or CDRW's written in packet mode,
8548 or if written to by other UDF utilities, such as DirectCD. Please
8549 read Documentation/filesystems/udf.txt.
8551 This filesystem support is also available as a module ( = code which
8552 can be inserted in and removed from the running kernel whenever you
8553 want). The module is called udf.o. If you want to compile it as a
8554 module, say M here and read Documentation/modules.txt.
8558 UDF write support (DANGEROUS)
8560 Say Y if you want to test write support for UDF filesystems.
8561 Due to lack of support for writing to CDR/CDRW's, this option
8562 is only supported for Hard Discs, DVD-RAM, and loopback files.
8566 If you want to use one of the FAT-based filesystems (the MS-DOS,
8567 VFAT (Windows 95) and UMSDOS (used to run Linux on top of an
8568 ordinary DOS partition) filesystems), then you must say Y or M here
8569 to include FAT support. You will then be able to mount partitions or
8570 diskettes with FAT-based filesystems and transparently access the
8571 files on them, i.e. MSDOS files will look and behave just like all
8574 This FAT support is not a filesystem in itself, it only provides the
8575 foundation for the other filesystems. You will have to say Y or M to
8576 at least one of "msdos fs support" or "vfat fs support" in order to
8579 Another way to read and write MSDOS floppies and hard drive
8580 partitions from within Linux (but not transparently) is with the
8581 mtools ("man mtools") program suite. This doesn't require the FAT
8584 It is now also becoming possible to read and write compressed FAT
8585 filesystems; read Documentation/filesystems/fat_cvf.txt for details.
8587 The FAT support will enlarge your kernel by about 37 KB. If unsure,
8590 If you want to compile this as a module however ( = code which can
8591 be inserted in and removed from the running kernel whenever you
8592 want), say M here and read Documentation/modules.txt. The module
8593 will be called fat.o. Note that if you compile the FAT support as a
8594 module, you cannot compile any of the FAT-based filesystems into the
8595 kernel -- they will have to be modules as well. The filesystem of
8596 your root partition (the one containing the directory /) cannot be a
8597 module, so don't say M here if you intend to use UMSDOS as your root
8602 This allows you to mount MSDOS partitions of your hard drive (unless
8603 they are compressed; to access compressed MSDOS partitions under
8604 Linux, you can either use the DOS emulator DOSEMU, described in the
8605 DOSEMU-HOWTO, available from
8606 http://www.linuxdoc.org/docs.html#howto , or try dmsdosfs in
8607 ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs . If you
8608 intend to use dosemu with a non-compressed MSDOS partition, say Y
8609 here) and MSDOS floppies. This means that file access becomes
8610 transparent, i.e. the MSDOS files look and behave just like all
8613 If you want to use umsdos, the Unix-like filesystem on top of DOS,
8614 which allows you to run Linux from within a DOS partition without
8615 repartitioning, you'll have to say Y or M here.
8617 If you have Windows 95 or Windows NT installed on your MSDOS
8618 partitions, you should use the VFAT filesystem (say Y to "vfat fs
8619 support" below), or you will not be able to see the long filenames
8620 generated by Windows 95 / Windows NT.
8622 This option will enlarge your kernel by about 7 KB. If unsure,
8623 answer Y. This will only work if you said Y to "fat fs support" as
8624 well. If you want to compile this as a module however ( = code which
8625 can be inserted in and removed from the running kernel whenever you
8626 want), say M here and read Documentation/modules.txt. The module
8627 will be called msdos.o.
8629 VFAT (Windows-95) fs support
8631 This option provides support for normal Windows filesystems with
8632 long filenames. That includes non-compressed FAT-based filesystems
8633 used by Windows 95, Windows 98, Windows NT 4.0, and mtools.
8635 You cannot use the VFAT filesystem for your Linux root partition
8636 (the one containing the directory /); use UMSDOS instead if you
8637 want to run Linux from within a DOS partition (i.e. say Y to
8638 "umsdos: Unix like fs on top of std MSDOS fs", below).
8640 The VFAT support enlarges your kernel by about 10 KB and it only
8641 works if you said Y to the "fat fs support" above. Please read the
8642 file Documentation/filesystems/vfat.txt for details. If unsure,
8645 If you want to compile this as a module ( = code which can be
8646 inserted in and removed from the running kernel whenever you want),
8647 say M here and read Documentation/modules.txt. The module will be
8650 UMSDOS: Unix-like filesystem on top of standard MSDOS filesystem
8652 Say Y here if you want to run Linux from within an existing DOS
8653 partition of your hard drive. The advantage of this is that you can
8654 get away without repartitioning your hard drive (which often implies
8655 backing everything up and restoring afterwards) and hence you're
8656 able to quickly try out Linux or show it to your friends; the
8657 disadvantage is that Linux becomes susceptible to DOS viruses and
8658 that UMSDOS is somewhat slower than ext2fs. Another use of UMSDOS
8659 is to write files with long unix filenames to MSDOS floppies; it
8660 also allows Unix-style softlinks and owner/permissions of files on
8661 MSDOS floppies. You will need a program called umssync in order to
8662 make use of umsdos; read Documentation/filesystems/umsdos.txt.
8664 To get utilities for initializing/checking UMSDOS filesystem, or
8665 latest patches and/or information, visit UMSDOS homepage at
8666 http://www.voyager.hr/~mnalis/umsdos/ .
8668 This option enlarges your kernel by about 28 KB and it only works if
8669 you said Y to both "fat fs support" and "msdos fs support" above. If
8670 you want to compile this as a module ( = code which can be inserted
8671 in and removed from the running kernel whenever you want), say M
8672 here and read Documentation/modules.txt. The module will be called
8673 umsdos.o. Note that the filesystem of your root partition (the one
8674 containing the directory /) cannot be a module, so saying M could be
8675 dangerous. If unsure, say N.
8677 /proc filesystem support
8679 This is a virtual filesystem providing information about the status
8680 of the system. "Virtual" means that it doesn't take up any space on
8681 your hard disk: the files are created on the fly by the kernel when
8682 you try to access them. Also, you cannot read the files with older
8683 version of the program less: you need to use more or cat.
8685 It's totally cool; for example, "cat /proc/interrupts" gives
8686 information about what the different IRQs are used for at the moment
8687 (there is a small number of Interrupt ReQuest lines in your computer
8688 that are used by the attached devices to gain the CPU's attention --
8689 often a source of trouble if two devices are mistakenly configured
8690 to use the same IRQ).
8692 The /proc filesystem is explained in the file
8693 Documentation/filesystems/proc.txt and on the proc(5) manpage ("man
8696 This option will enlarge your kernel by about 67 KB. Several
8697 programs depend on this, so everyone should say Y here.
8699 /dev filesystem support (EXPERIMENTAL)
8701 This is another virtual filesystem (like /proc) which provides the
8702 filesystem interface to device drivers, normally found in /dev.
8703 Devfs does not depend on major and minor number allocations. Device
8704 drivers register entries in /dev which appear automagically. Without
8705 devfs you need to populate /dev with hundreds, even thousands of
8707 This is work in progress. If you want to use this you *must* read
8708 Documentation/filesystems/devfs/README
8710 Enable devfs debugging output
8712 This option appears if you have CONFIG_DEVFS_FS enabled. Setting
8713 this to 'Y' enables devfs debugging output. See the file
8714 Documentation/filesystems/devfs/boot-options for more details.
8717 NFS filesystem support
8719 If you are connected to some other (usually local) Unix computer
8720 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
8721 on that computer (the NFS server) using the Network File Sharing
8722 protocol, say Y. "Mounting files" means that the client can access
8723 the files with usual UNIX commands as if they were sitting on the
8724 client's hard disk. For this to work, the server must run the
8725 programs nfsd and mountd (but does not need to have NFS filesystem
8726 support enabled in its kernel). NFS is explained in the Network
8727 Administrator's Guide, available from
8728 http://metalab.unc.edu/mdw/linux.html#guide , on its man page: "man
8729 nfs", and in the NFS-HOWTO.
8731 A superior but less widely used alternative to NFS is provided by
8732 the Coda filesystem; see "Coda filesystem support" below.
8734 If you say Y here, you should have said Y to TCP/IP networking also.
8735 This option would enlarge your kernel by about 27 KB.
8737 This filesystem is also available as a module ( = code which can be
8738 inserted in and removed from the running kernel whenever you want).
8739 The module is called nfs.o. If you want to compile it as a module,
8740 say M here and read Documentation/modules.txt.
8742 If you are configuring a diskless machine which will mount its root
8743 filesystem over NFS at boot time, say Y here and to "IP: kernel
8744 level autoconfiguration" above and to "Root file system on NFS"
8745 below. You cannot compile this driver as a module in this case.
8746 There are two packages designed for booting diskless machines over
8747 the net: netboot and etherboot, both available via FTP from
8748 ftp://metalab.unc.edu/pub/Linux/system/boot/ethernet/ .
8750 If you don't know what all this is about, say N.
8752 Root file system on NFS
8754 If you want your Linux box to mount its whole root filesystem (the
8755 one containing the directory /) from some other computer over the
8756 net via NFS (presumably because your box doesn't have a hard disk),
8757 say Y. Read Documentation/nfsroot.txt for details. It is likely that
8758 in this case, you also want to say Y to "IP: kernel level
8759 autoconfiguration" so that your box can discover its network address
8762 Most people say N here.
8766 If you want your Linux box to act as an NFS *server*, so that other
8767 computers on your local network which support NFS can access certain
8768 directories on your box transparently, you have two options: you can
8769 use the self-contained user space program nfsd, in which case you
8770 should say N here, or you can say Y and use the kernel based NFS
8771 server. The advantage of the kernel based solution is that it is
8774 In either case, you will need support software; the respective
8775 locations are given in the file Documentation/Changes in the NFS
8778 Please read the NFS-HOWTO, available from
8779 http://www.linuxdoc.org/HOWTO/NFS-HOWTO.html .
8782 The NFS server is also available as a module ( = code which can be
8783 inserted in and removed from the running kernel whenever you want).
8784 The module is called nfsd.o. If you want to compile it as a module,
8785 say M here and read Documentation/modules.txt. If unsure, say N.
8787 Provide NFSv3 server support (EXPERIMENTAL)
8789 If you would like to include the NFSv3 server was well as the NFSv2
8790 server, say Y here. File locking, via the NLMv4 protocol, is also
8791 supported. If unsure, say N.
8793 OS/2 HPFS filesystem support
8795 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
8796 is the filesystem used for organizing files on OS/2 hard disk
8797 partitions. Say Y if you want to be able to read files from an OS/2
8798 HPFS partition of your hard drive. OS/2 floppies however are in
8799 regular MSDOS format, so you don't need this option in order to be
8800 able to read them. Read Documentation/filesystems/hpfs.txt.
8802 This filesystem is also available as a module ( = code which can be
8803 inserted in and removed from the running kernel whenever you want).
8804 The module is called hpfs.o. If you want to compile it as a module,
8805 say M here and read Documentation/modules.txt. If unsure, say N.
8807 Windows NT NTFS support (read only)
8809 NTFS is the file system of Microsoft Windows NT. Say Y if you want
8810 to get read access to files on NTFS partitions of your hard drive.
8811 The Linux NTFS driver supports most of the mount options of the VFAT
8812 driver, see Documentation/filesystems/ntfs.txt. Saying Y here will
8813 give you read-only access to NTFS partitions.
8815 This code is also available as a module ( = code which can be
8816 inserted in and removed from the running kernel whenever you want).
8817 The module will be called ntfs.o. If you want to compile it as a
8818 module, say M here and read Documentation/modules.txt.
8820 NTFS write support (DANGEROUS)
8822 If you say Y here, you will (hopefully) be able to write to NTFS
8823 file systems as well as read from them. The read-write support
8824 in NTFS is far from being complete and is not well tested. If you
8825 enable this, back up your NTFS volume first since it may get
8830 System V and Coherent filesystem support (read only)
8832 SCO, Xenix and Coherent are commercial Unix systems for Intel
8833 machines. Saying Y here would allow you to read from their floppies
8834 and hard disk partitions.
8836 If you have floppies or hard disk partitions like that, it is likely
8837 that they contain binaries from those other Unix systems; in order
8838 to run these binaries, you will want to install iBCS2 (Intel Binary
8839 Compatibility Standard is a kernel module which lets you run SCO,
8840 Xenix, Wyse, UnixWare, Dell Unix and System V programs under Linux
8841 and is often needed to run commercial software that's only available
8842 for those systems. It's available via FTP (user: anonymous) from
8843 ftp://tsx-11.mit.edu/pub/linux/BETA ).
8845 If you only intend to mount files from some other Unix over the
8846 network using NFS, you don't need the System V filesystem support
8847 (but you need NFS filesystem support obviously).
8849 Note that this option is generally not needed for floppies, since a
8850 good portable way to transport files and directories between unixes
8851 (and even other operating systems) is given by the tar program ("man
8852 tar" or preferably "info tar"). Note also that this option has
8853 nothing whatsoever to do with the option "System V IPC". Read about
8854 the System V filesystem in Documentation/filesystems/sysv-fs.txt.
8855 Saying Y here will enlarge your kernel by about 27 kB.
8857 If you want to compile this as a module ( = code which can be
8858 inserted in and removed from the running kernel whenever you want),
8859 say M here and read Documentation/modules.txt. The module will be
8862 If you haven't heard about all of this before, it's safe to say N.
8864 SYSV filesystem write support (DANGEROUS)
8865 CONFIG_SYSV_FS_WRITE
8866 If you say Y here, you will (hopefully) be able to write to System V
8867 and Coherent file systems as well as read from them. The read-write
8868 support in SYSV is not well tested yet. If you enable this, back up
8869 your SYSV/Coherent volumes first since they may get damaged.
8873 Amiga FFS filesystem support
8875 The Fast File System (FFS) is the common filesystem used on hard
8876 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
8877 if you want to be able to read and write files from and to an Amiga
8878 FFS partition on your hard drive. Amiga floppies however cannot be
8879 read with this driver due to an incompatibility of the floppy
8880 controller used in an Amiga and the standard floppy controller in
8881 PCs and workstations. Read Documentation/filesystems/affs.txt and
8884 With this driver you can also mount disk files used by Bernd
8885 Schmidt's Un*X Amiga Emulator (http://www.freiburg.linux.de/~uae/ ).
8886 If you want to do this, you will also need to say Y or M to "Loop
8887 device support", above.
8889 This filesystem is also available as a module ( = code which can be
8890 inserted in and removed from the running kernel whenever you want).
8891 The module is called affs.o. If you want to compile it as a module,
8892 say M here and read Documentation/modules.txt. If unsure, say N.
8894 Apple Macintosh filesystem support (EXPERIMENTAL)
8896 If you say Y here, you will be able to mount Macintosh-formatted
8897 floppy disks and hard drive partitions with full read-write access.
8898 Please read fs/hfs/HFS.txt to learn about the available mount
8901 This filesystem support is also available as a module ( = code which
8902 can be inserted in and removed from the running kernel whenever you
8903 want). The module is called hfs.o. If you want to compile it as a
8904 module, say M here and read Documentation/modules.txt.
8906 ROM filesystem support
8908 This is a very small read-only filesystem mainly intended for
8909 initial ram disks of installation disks, but it could be used for
8910 other read-only media as well. Read
8911 Documentation/filesystems/romfs.txt for details.
8913 This filesystem support is also available as a module ( = code which
8914 can be inserted in and removed from the running kernel whenever you
8915 want). The module is called romfs.o. If you want to compile it as a
8916 module, say M here and read Documentation/modules.txt.
8918 If you don't know whether you need it, then you don't need it:
8921 QNX4 filesystem support (read only) (EXPERIMENTAL)
8923 This is the filesystem used by the operating system QNX 4. Say Y if
8924 you intend to mount QNX hard disks or floppies. Unless you say Y to
8925 "QNX4FS write support" below, you will only be able to read
8928 This filesystem support is also available as a module ( = code which
8929 can be inserted in and removed from the running kernel whenever you
8930 want). The module is called qnx4.o. If you want to compile it as a
8931 module, say M here and read Documentation/modules.txt.
8933 If you don't know whether you need it, then you don't need it:
8936 QNX4FS write support (DANGEROUS)
8938 Say Y if you want to test write support for QNX4 filesystems.
8940 Kernel automounter support
8942 The automounter is a tool to automatically mount remote filesystems
8943 on demand. This implementation is partially kernel-based to reduce
8944 overhead in the already-mounted case; this is unlike the BSD
8945 automounter (amd), which is a pure user space daemon.
8947 To use the automounter you need the user-space tools from
8948 ftp://ftp.kernel.org/pub/linux/daemons/autofs ; you also want to
8949 answer Y to "NFS filesystem support", below.
8951 If you want to compile this as a module ( = code which can be
8952 inserted in and removed from the running kernel whenever you want),
8953 say M here and read Documentation/modules.txt. The module will be
8956 If you are not a part of a fairly large, distributed network, you
8957 probably do not need an automounter, and can say N here.
8959 If you want to use the newer version of autofs with more features,
8960 say N here and select automounter v4.
8962 Kernel automounter v4 support
8964 The automounter is a tool to automatically mount remote filesystems
8965 on demand. This implementation is partially kernel-based to reduce
8966 overhead in the already-mounted case; this is unlike the BSD
8967 automounter (amd), which is a pure user space daemon.
8969 To use the automounter you need the user-space tools from
8970 ftp://ftp.kernel.org/pub/linux/daemons/autofs/testing-v4 ; you also
8971 want to answer Y to "NFS filesystem support", below.
8973 If you want to compile this as a module ( = code which can be
8974 inserted in and removed from the running kernel whenever you want),
8975 say M here and read Documentation/modules.txt. The module will be
8976 called autofs4.o. You will need to add "alias autofs autofs4" to
8977 your modules configuration file.
8979 If you are not a part of a fairly large, distributed network or don't
8980 have a laptop which needs to dynamically reconfigure to the local
8981 network, you probably do not need an automounter, and can say N here.
8983 EFS filesystem support (read only) (EXPERIMENTAL)
8985 EFS is an older filesystem used for non-ISO9660 CDROMs and hard disk
8986 partitions by SGI's IRIX operating system (IRIX 6.0 and newer uses
8987 the XFS filesystem for hard disk partitions however).
8989 This implementation only offers read-only access. If you don't know
8990 what all this is about, it's safe to say N. For more information
8991 about EFS see its home page at http://aeschi.ch.eu.org/efs/ .
8993 If you want to compile the EFS filesystem support as a module ( =
8994 code which can be inserted in and removed from the running kernel
8995 whenever you want), say M here and read Documentation/modules.txt.
8996 The module will be called efs.o.
8998 SGI disklabel support
8999 CONFIG_SGI_DISKLABEL
9000 Say Y to this only if you plan on mounting disks with SGI
9001 disklabels. This is not required to mount EFS-format CDROMs.
9003 UFS filesystem support (read only)
9005 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
9006 OpenBSD and NeXTstep) use a filesystem called UFS. Some System V
9007 Unixes can create and mount hard disk partitions and diskettes using
9008 this filesystem as well. Saying Y here will allow you to read from
9009 these partitions; if you also want to write to them, say Y to the
9010 experimental "UFS filesystem write support", below. Please read the
9011 file Documentation/filesystems/ufs.txt for more information.
9013 If you only intend to mount files from some other Unix over the
9014 network using NFS, you don't need the UFS filesystem support (but
9015 you need NFS filesystem support obviously).
9017 Note that this option is generally not needed for floppies, since a
9018 good portable way to transport files and directories between unixes
9019 (and even other operating systems) is given by the tar program ("man
9020 tar" or preferably "info tar").
9022 When accessing NeXTstep files, you may need to convert them from the
9023 NeXT character set to the Latin1 character set; use the program
9024 recode ("info recode") for this purpose.
9026 If you want to compile the UFS filesystem support as a module ( =
9027 code which can be inserted in and removed from the running kernel
9028 whenever you want), say M here and read Documentation/modules.txt.
9029 The module will be called ufs.o.
9031 If you haven't heard about all of this before, it's safe to say N.
9033 UFS filesystem write support (DANGEROUS)
9035 Say Y here if you want to try writing to UFS partitions. This is
9036 experimental, so you should back up your UFS partitions beforehand.
9038 Advanced partition selection
9039 CONFIG_PARTITION_ADVANCED
9040 Say Y here if you would like to use hard disks under Linux which
9041 were partitioned under an operating system running on a different
9042 architecture than your Linux system.
9044 Note that the answer to this question won't directly affect the
9045 kernel: saying N will just cause this configure script to skip all
9046 the questions about foreign partitioning schemes. If unsure, say N.
9048 Alpha OSF partition support
9049 CONFIG_OSF_PARTITION
9050 Say Y here if you would like to use hard disks under Linux which
9051 were partitioned on an Alpha machine.
9053 Macintosh partition map support
9054 CONFIG_MAC_PARTITION
9055 Say Y here if you would like to use hard disks under Linux which
9056 were partitioned on a Macintosh.
9058 PC BIOS (MSDOS partition tables) support
9059 CONFIG_MSDOS_PARTITION
9060 Say Y here if you would like to use hard disks under Linux which
9061 were partitioned on an x86 PC (not necessarily by DOS).
9063 BSD disklabel (FreeBSD partition tables) support
9064 CONFIG_BSD_DISKLABEL
9065 FreeBSD uses its own hard disk partition scheme on your PC. It
9066 requires only one entry in the primary partition table of your disk
9067 and manages it similarly to DOS extended partitions, putting in its
9068 first sector a new partition table in BSD disklabel format. Saying Y
9069 here allows you to read these disklabels and further mount FreeBSD
9070 partitions from within Linux if you have also said Y to "UFS
9071 filesystem support", above. If you don't know what all this is
9074 Sun partition tables support
9075 CONFIG_SUN_PARTITION
9076 Like most systems, SunOS uses its own hard disk partition table
9077 format, incompatible with all others. Saying Y here allows you to
9078 read these partition tables and further mount SunOS partitions from
9079 within Linux if you have also said Y to "UFS filesystem support",
9080 above. This is mainly used to carry data from a SPARC under SunOS to
9081 your Linux box via a removable medium like magneto-optical or ZIP
9082 drives; note however that a good portable way to transport files and
9083 directories between unixes (and even other operating systems) is
9084 given by the tar program ("man tar" or preferably "info tar"). If
9085 you don't know what all this is about, say N.
9087 Solaris (x86) partition table support
9088 CONFIG_SOLARIS_X86_PARTITION
9089 Like most systems, Solaris x86 uses its own hard disk partition
9090 table format, incompatible with all others. Saying Y here allows you
9091 to read these partition tables and further mount Solaris x86
9092 partitions from within Linux if you have also said Y to "UFS
9093 filesystem support", above.
9095 SGI partition support
9096 CONFIG_SGI_PARTITION
9097 Say Y here if you would like to be able to read the hard disk
9098 partition table format used by SGI machines.
9100 ADFS filesystem support (read only) (EXPERIMENTAL)
9102 The Acorn Disc Filing System is the standard filesystem of the
9103 RiscOS operating system which runs on Acorn's ARM-based Risc PC
9104 systems and the Acorn Archimedes range of machines. If you say Y
9105 here, Linux will be able to read from ADFS partitions on hard drives
9106 and from ADFS-formatted floppy discs.
9108 The ADFS partition should be the first partition (i.e.,
9109 /dev/[hs]d?1) on each of your drives. Please read the file
9110 Documentation/filesystems/adfs.txt for further details.
9112 This code is also available as a module called adfs.o ( = code which
9113 can be inserted in and removed from the running kernel whenever you
9114 want). If you want to compile it as a module, say M here and read
9115 Documentation/modules.txt.
9119 /dev/pts filesystem for Unix98 PTYs
9121 You should say Y here if you said Y to "Unix98 PTY support" above.
9122 You'll then get a virtual filesystem which can be mounted on
9123 /dev/pts with "mount -t devpts". This, together with the pseudo
9124 terminal master multiplexer /dev/ptmx, is used for pseudo terminal
9125 support as described in The Open Group's Unix98 standard: in order
9126 to acquire a pseudo terminal, a process opens /dev/ptmx; the number
9127 of the pseudo terminal is then made available to the process and the
9128 pseudo terminal slave can be accessed as /dev/pts/<number>. What was
9129 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
9131 The GNU C library glibc 2.1 contains the requisite support for this
9132 mode of operation; you also need client programs that use the Unix98
9135 Note that CONFIG_DEVFS_FS is a more general facility.
9137 UnixWare slices support (EXPERIMENTAL)
9138 CONFIG_UNIXWARE_DISKLABEL
9139 Like some systems, UnixWare uses its own slice table inside a
9140 partition (VTOC - Virtual Table of Contents). Its format is
9141 incompatible with all other OSes. Saying Y here allows you to read
9142 VTOC and further mount UnixWare partitions read-only from within
9143 Linux if you have also said Y to "UFS filesystem support" or "System
9144 V and Coherent filesystem support", above.
9146 This is mainly used to carry data from a UnixWare box to your
9147 Linux box via a removable medium like magneto-optical, ZIP or
9148 removable IDE drives. Note, however, that a good portable way to
9149 transport files and directories between unixes (and even other
9150 operating systems) is given by the tar program ("man tar" or
9151 preferably "info tar").
9153 If you don't know what all this is about, say N.
9155 SMB filesystem support (to mount Windows shares etc.)
9157 SMB (Server Message Block) is the protocol Windows for Workgroups
9158 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
9159 files and printers over local networks. Saying Y here allows you to
9160 mount their filesystems (often called "shares" in this context) and
9161 access them just like any other Unix directory. Currently, this
9162 works only if the Windows machines use TCP/IP as the underlying
9163 transport protocol, and not NetBEUI. For details, read
9164 Documentation/filesystems/smbfs.txt and the SMB-HOWTO, available
9165 from http://www.linuxdoc.org/docs.html#howto .
9167 Note: if you just want your box to act as an SMB *server* and make
9168 files and printing services available to Windows clients (which need
9169 to have a TCP/IP stack), you don't need to say Y here; you can use
9170 the program samba (available via FTP (user: anonymous) in
9171 ftp://metalab.unc.edu/pub/Linux/system/network/samba ) for that.
9173 General information about how to connect Linux, Windows machines and
9174 Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
9176 If you want to compile the SMB support as a module ( = code which
9177 can be inserted in and removed from the running kernel whenever you
9178 want), say M here and read Documentation/modules.txt. The module
9179 will be called smbfs.o. Most people say N, however.
9181 Coda filesystem support (advanced network fs)
9183 Coda is an advanced network filesystem, similar to NFS in that it
9184 enables you to mount filesystems of a remote server and access them
9185 with regular Unix commands as if they were sitting on your hard
9186 disk. Coda has several advantages over NFS: support for disconnected
9187 operation (e.g. for laptops), read/write server replication,
9188 security model for authentication and encryption, persistent client
9189 caches and write back caching.
9191 If you say Y here, your Linux box will be able to act as a Coda
9192 *client*. You will need user level code as well, both for the client
9193 and server. Servers are currently user level, i.e. need no kernel
9194 support. Please read Documentation/filesystems/coda.txt and check
9195 out the Coda home page http://www.coda.cs.cmu.edu .
9197 If you want to compile the coda client support as a module ( = code
9198 which can be inserted in and removed from the running kernel
9199 whenever you want), say M here and read Documentation/modules.txt.
9200 The module will be called coda.o.
9202 NCP filesystem support (to mount NetWare volumes)
9204 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
9205 used by Novell NetWare clients to talk to file servers. It is to IPX
9206 what NFS is to TCP/IP, if that helps. Saying Y here allows you to
9207 mount NetWare file server volumes and to access them just like any
9208 other Unix directory. For details, please read the file
9209 Documentation/filesystems/ncpfs.txt in the kernel source and the
9210 IPX-HOWTO from http://www.linuxdoc.org/docs.html#howto .
9212 You do not have to say Y here if you want your Linux box to act as a
9213 file *server* for Novell NetWare clients.
9215 General information about how to connect Linux, Windows machines and
9216 Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
9218 If you want to compile this as a module ( = code which can be
9219 inserted in and removed from the running kernel whenever you want),
9220 say M here and read Documentation/modules.txt. The module will be
9221 called ncpfs.o. Say N unless you are connected to a Novell network.
9224 CONFIG_NCPFS_PACKET_SIGNING
9225 NCP allows packets to be signed for stronger security. If you want
9226 security, say Y. Normal users can leave it off. To be able to use
9227 packet signing you must use ncpfs > 2.0.12.
9229 Proprietary file locking
9230 CONFIG_NCPFS_IOCTL_LOCKING
9231 Allows locking of records on remote volumes. Say N unless you have
9232 special applications which are able to utilize this locking scheme.
9234 Clear remove/delete inhibit when needed
9236 Allows manipulation of files flagged as Delete or Rename Inhibit. To
9237 use this feature you must mount volumes with the ncpmount parameter
9238 "-s" (ncpfs-2.0.12 and newer). Say Y unless you are not mounting
9239 volumes with -f 444.
9241 Use NFS namespace when available
9243 Allows you to utilize NFS namespace on NetWare servers. It brings
9244 you case sensitive filenames. Say Y. You can disable it at
9245 mount-time with the `-N nfs' parameter of ncpmount.
9247 Use OS2/LONG namespace when available
9249 Allows you to utilize OS2/LONG namespace on NetWare servers.
9250 Filenames in this namespace are limited to 255 characters, they are
9251 case insensitive, and case in names is preserved. Say Y. You can
9252 disable it at mount time with the -N os2 parameter of ncpmount.
9254 Lowercase DOS filenames on LONG namespace volume
9255 CONFIG_NCPFS_SMALLDOS
9256 If you say Y here, every filename on a NetWare server volume using
9257 the OS2/LONG namespace and created under DOS or on a volume using
9258 DOS namespace will be converted to lowercase characters.
9259 Saying N here will give you these filenames in uppercase.
9261 This is only a cosmetic option since the OS2/LONG namespace is case
9262 insensitive. The only major reason for this option is backward
9263 compatibility when moving from DOS to OS2/LONG namespace support.
9264 Long filenames (created by Win95) will not be affected.
9266 This option does not solve the problem that filenames appear
9267 differently under Linux and under Windows, since Windows does an
9268 additional conversions on the client side. You can achieve similar
9269 effects by saying Y to "Allow using of Native Language Support"
9272 Allow mounting of volume subdirectories
9273 CONFIG_NCPFS_MOUNT_SUBDIR
9274 Allows you to mount not only whole servers or whole volumes, but
9275 also subdirectories from a volume. It can be used to reexport data
9276 and so on. There is no reason to say N, so Y is recommended unless
9277 you count every byte.
9279 To utilize this feature you must use ncpfs-2.0.12 or newer.
9281 NDS interserver authentication domains
9282 CONFIG_NCPFS_NDS_DOMAINS
9283 This allows storing NDS private keys in kernel space where they
9284 can be used to authenticate another server as interserver NDS
9285 accesses need it. You must use ncpfs-2.0.12.1 or newer to utilize
9286 this feature. Say Y if you are using NDS connections to NetWare
9287 servers. Do not say Y if security is primary for you because root
9288 can read your session key (from /proc/kcore).
9290 Allow using of Native Language Support
9292 Allows you to use codepages and I/O charsets for file name
9293 translation between the server file system and input/output. This
9294 may be useful, if you want to access the server with other operating
9295 systems, e.g. Windows 95. See also NLS for more Information.
9297 To select codepages and I/O charsets use ncpfs-2.2.0.13 or newer.
9299 Symbolic links and mode permission bits
9301 This enables the use of symbolic links and an execute permission
9302 bit on NCPFS. The file server need not have long name space or NFS
9303 name space loaded for these to work.
9305 To use the new attributes, it is recommended to use the flags
9306 '-f 600 -d 755' on the ncpmount command line.
9309 CONFIG_NLS_CODEPAGE_437
9310 The Microsoft fat filesystem family can deal with filenames in
9311 native language character sets. These character sets are stored
9312 in so-called DOS codepages. You need to include the appropriate
9313 codepage if you want to be able to read/write these filenames on
9314 DOS/Windows partitions correctly. This does apply to the filenames
9315 only, not to the file contents. You can include several codepages;
9316 say Y here if you want to include the DOS codepage that is used in
9317 the United States and parts of Canada. This is recommended.
9320 CONFIG_NLS_CODEPAGE_737
9321 The Microsoft fat filesystem family can deal with filenames in
9322 native language character sets. These character sets are stored
9323 in so-called DOS codepages. You need to include the appropriate
9324 codepage if you want to be able to read/write these filenames on
9325 DOS/Windows partitions correctly. This does apply to the filenames
9326 only, not to the file contents. You can include several codepages;
9327 say Y here if you want to include the DOS codepage that is used for
9328 Greek. If unsure, say N.
9331 CONFIG_NLS_CODEPAGE_775
9332 The Microsoft fat filesystem family can deal with filenames in
9333 native language character sets. These character sets are stored
9334 in so-called DOS codepages. You need to include the appropriate
9335 codepage if you want to be able to read/write these filenames on
9336 DOS/Windows partitions correctly. This does apply to the filenames
9337 only, not to the file contents. You can include several codepages;
9338 say Y here if you want to include the DOS codepage that is used
9339 for the Baltic Rim Languages. If unsure, say N.
9342 CONFIG_NLS_CODEPAGE_850
9343 The Microsoft fat filesystem family can deal with filenames in
9344 native language character sets. These character sets are stored in
9345 so-called DOS codepages. You need to include the appropriate
9346 codepage if you want to be able to read/write these filenames on
9347 DOS/Windows partitions correctly. This does apply to the filenames
9348 only, not to the file contents. You can include several codepages;
9349 say Y here if you want to include the DOS codepage that is used for
9350 much of Europe -- United Kingdom, Germany, Spain, Italy, and [add
9351 more countries here]. It has some characters useful to many European
9352 languages that are not part of the US codepage 437.
9357 CONFIG_NLS_CODEPAGE_852
9358 The Microsoft fat filesystem family can deal with filenames in
9359 native language character sets. These character sets are stored in
9360 so-called DOS codepages. You need to include the appropriate
9361 codepage if you want to be able to read/write these filenames on
9362 DOS/Windows partitions correctly. This does apply to the filenames
9363 only, not to the file contents. You can include several codepages;
9364 say Y here if you want to include the Latin 2 codepage used by DOS
9365 for much of Central and Eastern Europe. It has all the required
9366 characters for these languages: Albanian, Croatian, Czech, English,
9367 Finnish, Hungarian, Irish, German, Polish, Romanian, Serbian (Latin
9368 transcription), Slovak, Slovenian, and Sorbian.
9371 CONFIG_NLS_CODEPAGE_855
9372 The Microsoft fat filesystem family can deal with filenames in
9373 native language character sets. These character sets are stored in
9374 so-called DOS codepages. You need to include the appropriate
9375 codepage if you want to be able to read/write these filenames on
9376 DOS/Windows partitions correctly. This does apply to the filenames
9377 only, not to the file contents. You can include several codepages;
9378 say Y here if you want to include the DOS codepage for Cyrillic.
9381 CONFIG_NLS_CODEPAGE_857
9382 The Microsoft fat filesystem family can deal with filenames in
9383 native language character sets. These character sets are stored in
9384 so-called DOS codepages. You need to include the appropriate
9385 codepage if you want to be able to read/write these filenames on
9386 DOS/Windows partitions correctly. This does apply to the filenames
9387 only, not to the file contents. You can include several codepages;
9388 say Y here if you want to include the DOS codepage for Turkish.
9391 CONFIG_NLS_CODEPAGE_860
9392 The Microsoft fat filesystem family can deal with filenames in
9393 native language character sets. These character sets are stored in
9394 so-called DOS codepages. You need to include the appropriate
9395 codepage if you want to be able to read/write these filenames on
9396 DOS/Windows partitions correctly. This does apply to the filenames
9397 only, not to the file contents. You can include several codepages;
9398 say Y here if you want to include the DOS codepage for Portuguese.
9401 CONFIG_NLS_CODEPAGE_861
9402 The Microsoft fat filesystem family can deal with filenames in
9403 native language character sets. These character sets are stored in
9404 so-called DOS codepages. You need to include the appropriate
9405 codepage if you want to be able to read/write these filenames on
9406 DOS/Windows partitions correctly. This does apply to the filenames
9407 only, not to the file contents. You can include several codepages;
9408 say Y here if you want to include the DOS codepage for Icelandic.
9411 CONFIG_NLS_CODEPAGE_862
9412 The Microsoft fat filesystem family can deal with filenames in
9413 native language character sets. These character sets are stored in
9414 so-called DOS codepages. You need to include the appropriate
9415 codepage if you want to be able to read/write these filenames on
9416 DOS/Windows partitions correctly. This does apply to the filenames
9417 only, not to the file contents. You can include several codepages;
9418 say Y here if you want to include the DOS codepage for Hebrew.
9421 CONFIG_NLS_CODEPAGE_863
9422 The Microsoft fat filesystem family can deal with filenames in
9423 native language character sets. These character sets are stored in
9424 so-called DOS codepages. You need to include the appropriate
9425 codepage if you want to be able to read/write these filenames on
9426 DOS/Windows partitions correctly. This does apply to the filenames
9427 only, not to the file contents. You can include several codepages;
9428 say Y here if you want to include the DOS codepage for Canadian
9432 CONFIG_NLS_CODEPAGE_864
9433 The Microsoft fat filesystem family can deal with filenames in
9434 native language character sets. These character sets are stored in
9435 so-called DOS codepages. You need to include the appropriate
9436 codepage if you want to be able to read/write these filenames on
9437 DOS/Windows partitions correctly. This does apply to the filenames
9438 only, not to the file contents. You can include several codepages;
9439 say Y here if you want to include the DOS codepage for Arabic.
9442 CONFIG_NLS_CODEPAGE_865
9443 The Microsoft fat filesystem family can deal with filenames in
9444 native language character sets. These character sets are stored in
9445 so-called DOS codepages. You need to include the appropriate
9446 codepage if you want to be able to read/write these filenames on
9447 DOS/Windows partitions correctly. This does apply to the filenames
9448 only, not to the file contents. You can include several codepages;
9449 say Y here if you want to include the DOS codepage for the Nordic
9453 CONFIG_NLS_CODEPAGE_866
9454 The Microsoft fat filesystem family can deal with filenames in
9455 native language character sets. These character sets are stored in
9456 so-called DOS codepages. You need to include the appropriate
9457 codepage if you want to be able to read/write these filenames on
9458 DOS/Windows partitions correctly. This does apply to the filenames
9459 only, not to the file contents. You can include several codepages;
9460 say Y here if you want to include the DOS codepage for
9464 CONFIG_NLS_CODEPAGE_869
9465 The Microsoft fat filesystem family can deal with filenames in
9466 native language character sets. These character sets are stored in
9467 so-called DOS codepages. You need to include the appropriate
9468 codepage if you want to be able to read/write these filenames on
9469 DOS/Windows partitions correctly. This does apply to the filenames
9470 only, not to the file contents. You can include several codepages;
9471 say Y here if you want to include the DOS codepage for Greek.
9473 ### Why do we have two codepages for Greek and Cyrillic?
9477 CONFIG_NLS_CODEPAGE_874
9478 The Microsoft fat filesystem family can deal with filenames in
9479 native language character sets. These character sets are stored in
9480 so-called DOS codepages. You need to include the appropriate
9481 codepage if you want to be able to read/write these filenames on
9482 DOS/Windows partitions correctly. This does apply to the filenames
9483 only, not to the file contents. You can include several codepages;
9484 say Y here if you want to include the DOS codepage for Thai.
9487 CONFIG_NLS_ISO8859_1
9488 If you want to display filenames with native language characters
9489 from the Microsoft fat filesystem family or from JOLIET CDROMs
9490 correctly on the screen, you need to include the appropriate
9491 input/output character sets. Say Y here for the Latin 1 character
9492 set, which covers most West European languages such as Albanian,
9493 Catalan, Danish, Dutch, English, Faeroese, Finnish, French, German,
9494 Galician, Irish, Icelandic, Italian, Norwegian, Portuguese, Spanish,
9495 and Swedish. It is also the default for the US. If unsure, say Y.
9498 CONFIG_NLS_ISO8859_2
9499 If you want to display filenames with native language characters
9500 from the Microsoft fat filesystem family or from JOLIET CDROMs
9501 correctly on the screen, you need to include the appropriate
9502 input/output character sets. Say Y here for the Latin 2 character
9503 set, which works for most Latin-written Slavic and Central European
9504 languages: Czech, German, Hungarian, Polish, Rumanian, Croatian,
9508 CONFIG_NLS_ISO8859_3
9509 If you want to display filenames with native language characters
9510 from the Microsoft fat filesystem family or from JOLIET CDROMs
9511 correctly on the screen, you need to include the appropriate
9512 input/output character sets. Say Y here for the Latin 3 character
9513 set, which is popular with authors of Esperanto, Galician, Maltese,
9517 CONFIG_NLS_ISO8859_4
9518 If you want to display filenames with native language characters
9519 from the Microsoft fat filesystem family or from JOLIET CDROMs
9520 correctly on the screen, you need to include the appropriate
9521 input/output character sets. Say Y here for the Latin 4 character
9522 set which introduces letters for Estonian, Latvian, and
9523 Lithuanian. It is an incomplete predecessor of Latin 6.
9526 CONFIG_NLS_ISO8859_5
9527 If you want to display filenames with native language characters
9528 from the Microsoft fat filesystem family or from JOLIET CDROMs
9529 correctly on the screen, you need to include the appropriate
9530 input/output character sets. Say Y here for ISO8859-5, a Cyrillic
9531 character set with which you can type Bulgarian, Byelorussian,
9532 Macedonian, Russian, Serbian, and Ukrainian. Note that the charset
9533 KOI8-R is preferred in Russia.
9536 CONFIG_NLS_ISO8859_6
9537 If you want to display filenames with native language characters
9538 from the Microsoft fat filesystem family or from JOLIET CDROMs
9539 correctly on the screen, you need to include the appropriate
9540 input/output character sets. Say Y here for ISO8859-6, the Arabic
9544 CONFIG_NLS_ISO8859_7
9545 If you want to display filenames with native language characters
9546 from the Microsoft fat filesystem family or from JOLIET CDROMs
9547 correctly on the screen, you need to include the appropriate
9548 input/output character sets. Say Y here for ISO8859-7, the Modern
9549 Greek character set.
9552 CONFIG_NLS_ISO8859_8
9553 If you want to display filenames with native language characters
9554 from the Microsoft fat filesystem family or from JOLIET CDROMs
9555 correctly on the screen, you need to include the appropriate
9556 input/output character sets. Say Y here for ISO8859-8, the Hebrew
9560 CONFIG_NLS_ISO8859_9
9561 If you want to display filenames with native language characters
9562 from the Microsoft fat filesystem family or from JOLIET CDROMs
9563 correctly on the screen, you need to include the appropriate
9564 input/output character sets. Say Y here for the Latin 5 character
9565 set, and it replaces the rarely needed Icelandic letters in Latin 1
9566 with the Turkish ones. Useful in Turkey.
9569 CONFIG_NLS_ISO8859_10
9570 If you want to display filenames with native language characters
9571 from the Microsoft fat filesystem family or from JOLIET CDROMs
9572 correctly on the screen, you need to include the appropriate
9573 input/output character sets. Say Y here for the Latin 6 character
9574 set, which adds the last Inuit (Greenlandic) and Sami (Lappish)
9575 letters that were missing in Latin 4 to cover the entire Nordic
9578 NLS ISO 8859-14 (Latin 8; Celtic)
9579 CONFIG_NLS_ISO8859_14
9580 If you want to display filenames with native language characters
9581 from the Microsoft fat filesystem family or from JOLIET CDROMs
9582 correctly on the screen, you need to include the appropriate
9583 input/output character sets. Say Y here for the Latin 8 character
9584 set, which adds the last accented vowels for Welsh (aka Cymraeg)
9585 (and Manx Gaelic) hat were missing in Latin 1.
9586 http://linux.speech.cymru.org/ has further information.
9589 CONFIG_NLS_ISO8859_15
9590 If you want to display filenames with native language characters
9591 from the Microsoft fat filesystem family or from JOLIET CDROMs
9592 correctly on the screen, you need to include the appropriate
9593 input/output character sets. Say Y here for the Latin 9 character
9594 set, which covers most West European languages such as Albanian,
9595 Catalan, Danish, Dutch, English, Estonian, Faeroese, Finnish,
9596 French, German, Galician, Irish, Icelandic, Italian, Norwegian,
9597 Portuguese, Spanish, and Swedish. Latin 9 is an update to
9598 Latin 1 (ISO 8859-1) that removes a handful of rarely used
9599 characters and instead adds support for Estonian, corrects the
9600 support for French and Finnish, and adds the new Euro character. If
9605 If you want to display filenames with native language characters
9606 from the Microsoft fat filesystem family or from JOLIET CDROMs
9607 correctly on the screen, you need to include the appropriate
9608 input/output character sets. Say Y here for the preferred Russian
9613 If you say Y here, you will get support for terminal devices with
9614 display and keyboard devices. These are called "virtual" because you
9615 can run several virtual terminals (also called virtual consoles) on
9616 one physical terminal. This is rather useful, for example one
9617 virtual terminal can collect system messages and warnings, another
9618 one can be used for a text-mode user session, and a third could run
9619 an X session, all in parallel. Switching between virtual terminals
9620 is done with certain key combinations, usually Alt-<function key>.
9622 The setterm command ("man setterm") can be used to change the
9623 properties (such as colors) of a virtual terminal.
9625 You need at least one virtual terminal device in order to make use
9626 of your keyboard and monitor. Therefore, only people configuring an
9627 embedded system would want to say N here in order to save some
9628 memory; the only way to log into such a system is then via a serial
9629 or network connection.
9631 If unsure, say Y, or else you won't be able to do much with your new
9632 shiny Linux system :-)
9634 Support for console on virtual terminal
9636 The system console is the device which receives all kernel messages
9637 and warnings and which allows logins in single user mode. If you
9638 answer Y here, a virtual terminal (the device used to interact with
9639 a physical terminal) can be used as system console. This is the most
9640 common mode of operations, so you should say Y here unless you want
9641 the kernel messages be output only to a serial port (in which case
9642 you should say Y to "Console on serial port", below).
9644 If you do say Y here, by default the currently visible virtual
9645 terminal (/dev/tty0) will be used as system console. You can change
9646 that with a kernel command line option such as "console=tty3" which
9647 would use the third virtual terminal as system console. (Try "man
9648 bootparam" or see the documentation of your boot loader (lilo or
9649 loadlin) about how to pass options to the kernel at boot time. The
9650 lilo procedure is also explained in the SCSI-HOWTO, available from
9651 http://www.linuxdoc.org/docs.html#howto .)
9655 Software generated cursor
9657 If you say Y here, you'll be able to do lots of nice things with the
9658 cursors of your virtual consoles -- for example turn them into
9659 non-blinking block cursors which are more visible on laptop screens,
9660 or change their colors depending on the virtual console they're on.
9661 See Documentation/VGA-softcursor.txt for more information.
9663 Support for PowerMac keyboard
9665 This option allows you to use an ADB keyboard attached to your
9666 machine. Note that this disables any other (ie. PS/2) keyboard
9667 support, even if your machine is physically capable of using both at
9670 If you use an ADB keyboard (4 pin connector), say Y here.
9671 If you use a PS/2 keyboard (6 pin connector), say N here.
9673 Standard/generic serial support
9675 This selects whether you want to include the driver for the standard
9676 serial ports. The standard answer is Y. People who might say N here
9677 are those that are setting up dedicated Ethernet WWW/FTP servers, or
9678 users that have one of the various bus mice instead of a serial
9679 mouse and don't intend to use their machine's standard serial port
9680 for anything. (Note that the Cyclades and Stallion multi serial port
9681 drivers do not need this driver built in for them to work.)
9683 If you want to compile this driver as a module, say M here and read
9684 Documentation/modules.txt. The module will be called serial.o.
9685 [WARNING: Do not compile this driver as a module if you are using
9686 non-standard serial ports, since the configuration information will
9687 be lost when the driver is unloaded. This limitation may be lifted
9690 BTW1: If you have a mouseman serial mouse which is not recognized by
9691 the X window system, try running gpm first.
9693 BTW2: If you intend to use a software modem (also called Winmodem)
9694 under Linux, forget it. These modems are crippled and require
9695 proprietary drivers which are only available under Windows.
9697 Most people will say Y or M here, so that they can use serial mice,
9698 modems and similar devices connecting to the standard serial ports.
9700 Support for console on serial port
9701 CONFIG_SERIAL_CONSOLE
9702 If you say Y here, it will be possible to use a serial port as the
9703 system console (the system console is the device which receives all
9704 kernel messages and warnings and which allows logins in single user
9705 mode). This could be useful if some terminal or printer is connected
9706 to that serial port.
9708 Even if you say Y here, the currently visible virtual console
9709 (/dev/tty0) will still be used as the system console by default, but
9710 you can alter that using a kernel command line option such as
9711 "console=ttyS1". (Try "man bootparam" or see the documentation of
9712 your boot loader (lilo or loadlin) about how to pass options to the
9713 kernel at boot time. The lilo procedure is also explained in the
9714 SCSI-HOWTO, available from
9715 http://www.linuxdoc.org/docs.html#howto .)
9717 If you don't have a VGA card installed and you say Y here, the
9718 kernel will automatically use the first serial line, /dev/ttyS0, as
9723 Support for PowerMac serial ports
9725 If you have Macintosh style serial ports (8 pin mini-DIN), say Y
9726 here. If you also have regular serial ports and enable the driver
9727 for them, you can't currently use the serial console feature.
9729 Comtrol Rocketport support
9731 This is a driver for the Comtrol Rocketport cards which provide
9732 multiple serial ports. You would need something like this to connect
9733 more than two modems to your Linux box, for instance in order to
9734 become a dial-in server.
9736 If you want to compile this driver as a module, say M here and read
9737 Documentation/modules.txt. The module will be called rocket.o.
9739 Digiboard Intelligent async support
9741 This is a driver for Digi International's Xx, Xeve, and Xem series
9742 of cards which provide multiple serial ports. You would need
9743 something like this to connect more than two modems to your Linux
9744 box, for instance in order to become a dial-in server. This driver
9745 supports the original PC (ISA) boards as well as PCI, and EISA. If
9746 you have a card like this, say Y here and read the file
9747 Documentation/digiepca.txt.
9749 NOTE: There is another, separate driver for the Digiboard PC boards:
9750 "Digiboard PC/Xx Support" below. You should (and can) only select
9751 one of the two drivers.
9753 If you want to compile this driver as a module, say M here and read
9754 Documentation/modules.txt. The module will be called epca.o.
9756 Digiboard PC/Xx Support
9758 This is a driver for the Digiboard PC/Xe, PC/Xi, and PC/Xeve cards
9759 that give you many serial ports. You would need something like this
9760 to connect more than two modems to your Linux box, for instance in
9761 order to become a dial-in server. If you have a card like that, say
9762 Y here and read the file Documentation/digiboard.txt.
9764 If you want to compile this driver as a module, say M here and read
9765 Documentation/modules.txt. The module will be called pcxx.o.
9767 SDL RISCom/8 card support
9769 This is a driver for the SDL Communications RISCom/8 multiport card,
9770 which gives you many serial ports. You would need something like
9771 this to connect more than two modems to your Linux box, for instance
9772 in order to become a dial-in server. If you have a card like that,
9773 say Y here and read the file Documentation/riscom8.txt.
9775 Also it's possible to say M here and compile this driver as kernel
9776 loadable module; the module will be called riscom8.o.
9778 Computone IntelliPort Plus serial support
9780 This driver supports the entire family of Intelliport II/Plus
9781 controllers with the exception of the MicroChannel controllers. It
9782 does not support products previous to the Intelliport II. These are
9783 multiport cards, which give you many serial ports. You would need
9784 something like this to connect more than two modems to your Linux
9785 box, for instance in order to become a dial-in server. If you have a
9786 card like that, say Y here and read Documentation/computone.txt.
9788 If you want to compile this as a module ( = code which can be
9789 inserted in and removed from the running kernel whenever you want),
9790 say M here and read Documentation/modules.txt. You will get two
9791 modules called ip2.o and ip2main.o.
9793 Specialix IO8+ card support
9795 This is a driver for the Specialix IO8+ multiport card (both the
9796 ISA and the PCI version) which gives you many serial ports. You
9797 would need something like this to connect more than two modems to
9798 your Linux box, for instance in order to become a dial-in server.
9800 If you have a card like that, say Y here and read the file
9801 Documentation/specialix.txt. Also it's possible to say M here and
9802 compile this driver as kernel loadable module which will be called
9805 Specialix DTR/RTS pin is RTS
9806 CONFIG_SPECIALIX_RTSCTS
9807 The Specialix card can only support either RTS or DTR. If you say N
9808 here, the driver will use the pin as "DTR" when the tty is in
9809 software handshake mode. If you say Y here or hardware handshake is
9810 on, it will always be RTS. Read the file Documentation/specialix.txt
9811 for more information.
9813 Cyclades async mux support
9815 This is a driver for a card that gives you many serial ports. You
9816 would need something like this to connect more than two modems to
9817 your Linux box, for instance in order to become a dial-in server.
9818 For information about the Cyclades-Z card, read
9819 drivers/char/README.cycladesZ.
9821 As of 1.3.9x kernels, this driver's minor numbers start at 0 instead
9824 If you want to compile this as a module ( = code which can be
9825 inserted in and removed from the running kernel whenever you want),
9826 say M here and read Documentation/modules.txt. The module will be
9829 If you haven't heard about it, it's safe to say N.
9831 Cyclades-Z interrupt mode operation (EXPERIMENTAL)
9833 The Cyclades-Z family of multiport cards allows 2 (two) driver
9834 op modes: polling and interrupt. In polling mode, the driver will
9835 check the status of the Cyclades-Z ports every certain amount of
9836 time (which is called polling cycle and is configurable). In
9837 interrupt mode, it will use an interrupt line (IRQ) in order to check
9838 the status of the Cyclades-Z ports. The default op mode is polling.
9841 Stallion multiport serial support
9843 Stallion cards give you many serial ports. You would need something
9844 like this to connect more than two modems to your Linux box, for
9845 instance in order to become a dial-in server. If you say Y here, you
9846 will be asked for your specific card model in the next questions.
9847 Make sure to read drivers/char/README.stallion in this case. If you
9848 have never heard about all this, it's safe to say N.
9850 Stallion EasyIO or EC8/32 support
9852 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
9853 card, then this is for you; say Y. Make sure to read
9854 Documentation/stallion.txt.
9856 If you want to compile this as a module ( = code which can be
9857 inserted in and removed from the running kernel whenever you want),
9858 say M here and read Documentation/modules.txt. The module will be
9861 Stallion EC8/64, ONboard, Brumby support
9863 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
9864 serial multiport card, say Y here. Make sure to read
9865 Documentation/stallion.txt.
9867 To compile it as a module ( = code which can be inserted in and
9868 removed from the running kernel whenever you want), say M here and
9869 read Documentation/modules.txt. The module will be called
9872 Microgate SyncLink adapter support
9874 Provides support for the SyncLink ISA and PCI
9875 multiprotocol serial adapters. These adapters
9876 support asynchronous and HDLC bit synchronous
9877 communication up to 10Mbps (PCI adapter).
9879 This driver can only be built as a module ( = code which can be
9880 inserted in and removed from the running kernel whenever you want).
9881 The module will be called synclink.o. If you want to do that, say M
9884 Synchronous HDLC line discipline support
9886 Allows synchronous HDLC communications with tty device drivers that
9887 support synchronous HDLC such as the Microgate SyncLink adapter.
9889 This driver can only be built as a module ( = code which can be
9890 inserted in and removed from the running kernel whenever you want).
9891 The module will be called n_hdlc.o. If you want to do that, say M
9894 Specialix SX (and SI) card support
9896 This is a driver for the SX and SI multiport serial cards.
9897 Please read the file Documentation/sx.txt for details.
9899 This driver can only be built as a module ( = code which can be
9900 inserted in and removed from the running kernel whenever you want).
9901 The module will be called sx.o. If you want to do that, say M here.
9903 Hayes ESP serial port support
9905 This is a driver which supports Hayes ESP serial ports. Both single
9906 port cards and multiport cards are supported. Make sure to read
9907 Documentation/hayes-esp.txt.
9909 To compile this driver as a module ( = code which can be inserted in
9910 and removed from the running kernel whenever you want), say M here
9911 and read Documentation/modules.txt. The module will be called esp.o.
9914 Multi-Tech multiport card support (EXPERIMENTAL)
9916 This is a driver for the Multi-Tech cards which provide several
9917 serial ports. The driver is experimental and can currently only be
9918 built as a module ( = code which can be inserted in and removed from
9919 the running kernel whenever you want). Please read
9920 Documentation/modules.txt. The module will be called isicom.o
9924 A pseudo terminal (PTY) is a software device consisting of two
9925 halves: a master and a slave. The slave device behaves identical to
9926 a physical terminal; the master device is used by a process to
9927 read data from and write data to the slave, thereby emulating a
9928 terminal. Typical programs for the master side are telnet servers
9931 Linux has traditionally used the BSD-like names /dev/ptyxx for
9932 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
9933 has a number of problems. The GNU C library glibc 2.1 and later,
9934 however, supports the Unix98 naming standard: in order to acquire a
9935 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
9936 terminal is then made available to the process and the pseudo
9937 terminal slave can be accessed as /dev/pts/<number>. What was
9938 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
9940 The entries in /dev/pts/ are created on the fly by a virtual
9941 filesystem; therefore, if you say Y here you should say Y to
9942 "/dev/pts filesystem for Unix98 PTYs" as well.
9944 If you want to say Y here, you need to have the C library glibc 2.1
9945 or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
9946 Read the instructions in Documentation/Changes pertaining to pseudo
9947 terminals. It's safe to say N.
9949 Maximum number of Unix98 PTYs in use (0-2048)
9950 CONFIG_UNIX98_PTY_COUNT
9951 The maximum number of Unix98 PTYs that can be used at any one time.
9952 The default is 256, and should be enough for desktop systems. Server
9953 machines which support incoming telnet/rlogin/ssh connections and/or
9954 serve several X terminals may want to increase this: every incoming
9955 connection and every xterm uses up one PTY.
9957 When not in use, each additional set of 256 PTYs occupy
9958 approximately 8 KB of kernel memory on 32-bit architectures.
9960 Parallel printer support
9962 If you intend to attach a printer to the parallel port of your Linux
9963 box (as opposed to using a serial printer; if the connector at the
9964 printer has 9 or 25 holes ["female"], then it's serial), say Y. Also
9965 read the Printing-HOWTO, available from
9966 http://www.linuxdoc.org/docs.html#howto .
9968 It is possible to share one parallel port among several devices
9969 (e.g. printer and ZIP drive) and it is safe to compile the
9970 corresponding drivers into the kernel. If you want to compile this
9971 driver as a module however ( = code which can be inserted in and
9972 removed from the running kernel whenever you want), say M here and
9973 read Documentation/modules.txt and Documentation/parport.txt. The
9974 module will be called lp.o.
9976 If you have several parallel ports, you can specify which ports to
9977 use with the "lp" kernel command line option. (Try "man bootparam"
9978 or see the documentation of your boot loader (lilo or loadlin) about
9979 how to pass options to the kernel at boot time. The lilo procedure
9980 is also explained in the SCSI-HOWTO, available from
9981 http://www.linuxdoc.org/docs.html#howto .) The syntax of the "lp"
9982 command line option can be found in drivers/char/lp.c.
9984 If you have more than 3 printers, you need to increase the LP_NO
9987 Support for console on line printer
9989 If you want kernel messages to be printed out as they occur, you
9990 can have a console on the printer. This option adds support for
9991 doing that; to actually get it to happen you need to pass the
9992 option "console=lp" to the kernel at boot time.
9994 Note that kernel messages can get lost if the printer is out of
9995 paper (or off, or unplugged, or too busy..), but this behaviour
9996 can be changed. See drivers/char/lp.c (do this at your own risk).
10002 Say Y here if your machine has a bus mouse as opposed to a serial
10003 mouse. Most people have a regular serial MouseSystem or
10004 Microsoft mouse (made by Logitech) that plugs into a COM port
10005 (rectangular with 9 or 25 pins). These people say N here. If you
10006 have something else, read the Busmouse-HOWTO, available from
10007 http://www.linuxdoc.org/docs.html#howto , and say Y here.
10009 If you have a laptop, you either have to check the documentation or
10010 experiment a bit to find out whether the trackball is a serial mouse
10011 or not; it's best to say Y here for you.
10013 This is the generic bus mouse driver code. If you have a bus mouse,
10014 you will have to say Y here and also to the specific driver for your
10017 This code is also available as a module ( = code which can be
10018 inserted in and removed from the running kernel whenever you want).
10019 The module will be called busmouse.o. If you want to compile it as a
10020 module, say M here and read Documentation/modules.txt.
10022 Mouse Support (not serial and bus mice)
10024 This is for machines with a mouse which is neither a serial nor a
10025 bus mouse. Examples are PS/2 mice (such as the track balls on some
10026 laptops) and some digitizer pads. Most people have a regular serial
10027 MouseSystem or Microsoft mouse (made by Logitech) that plugs into a
10028 COM port (rectangular with 9 or 25 pins). These people say N here.
10029 If you have something else, read the Busmouse-HOWTO, available from
10030 http://www.linuxdoc.org/docs.html#howto . This HOWTO contains
10031 information about all non-serial mice, not just bus mice.
10033 If you have a laptop, you either have to check the documentation or
10034 experiment a bit to find out whether the trackball is a serial mouse
10035 or not; it's best to say Y here for you.
10037 Note that the answer to this question won't directly affect the
10038 kernel: saying N will just cause this configure script to skip all
10039 the questions about non-serial mice. If unsure, say Y.
10041 Logitech busmouse support
10042 CONFIG_LOGIBUSMOUSE
10043 Logitech mouse connected to a proprietary interface card. It's
10044 generally a round connector with 9 pins. Note that the newer mice
10045 made by Logitech don't use the Logitech protocol anymore; for those,
10046 you don't need this option. You want to read the Busmouse-HOWTO ,
10047 available from http://www.linuxdoc.org/docs.html#howto .
10049 If you want to compile this as a module ( = code which can be
10050 inserted in and removed from the running kernel whenever you want),
10051 say M here and read Documentation/modules.txt. The module will be
10052 called busmouse.o. If you are unsure, say N and read the HOWTO
10053 nevertheless: it will tell you what you have.
10055 PS/2 mouse (aka "auxiliary device") support
10057 The PS/2 mouse connects to a special mouse port that looks much like
10058 the keyboard port (small circular connector with 6 pins). This way,
10059 the mouse does not use any serial ports. This port can also be used
10060 for other input devices like light pens, tablets, keypads. Compaq,
10061 AST and IBM all use this as their mouse port on currently shipping
10062 machines. The trackballs of some laptops are PS/2 mice also. In
10063 particular, the C&T 82C710 mouse on TI Travelmates is a PS/2 mouse.
10065 Although PS/2 mice are not technically bus mice, they are explained
10066 in detail in the Busmouse-HOWTO, available from
10067 http://www.linuxdoc.org/docs.html#howto .
10069 When using a PS/2 mouse, you can get problems if you want to use the
10070 mouse both on the Linux console and under X. Using the "-R" option
10071 of the Linux mouse managing program gpm (available from
10072 ftp://metalab.unc.edu/pub/Linux/system/mouse ) solves this
10073 problem, or you can get the "mconv2" utility from the same location.
10075 C&T 82C710 mouse port support (as on TI Travelmate)
10076 CONFIG_82C710_MOUSE
10077 This is a certain kind of PS/2 mouse used on the TI Travelmate. If
10078 you are unsure, try first to say N here and come back if the mouse
10079 doesn't work. Read the Busmouse-HOWTO, available from
10080 http://www.linuxdoc.org/docs.html#howto .
10082 PC110 digitizer pad support
10084 This drives the digitizer pad on the IBM PC110 palmtop. It can turn
10085 the digitizer pad into a PS/2 mouse emulation with tap gestures or
10086 into an absolute pad.
10088 If you want to compile this as a module ( = code which can be
10089 inserted in and removed from the running kernel whenever you want),
10090 say M here and read Documentation/modules.txt. The module will be
10093 Microsoft busmouse support
10095 These animals (also called Inport mice) are connected to an
10096 expansion board using a round connector with 9 pins. If this is what
10097 you have, say Y and read the Busmouse-HOWTO, available from
10098 http://www.linuxdoc.org/docs.html#howto .
10100 If you are unsure, say N and read the HOWTO nevertheless: it will
10101 tell you what you have. Also be aware that several vendors talk
10102 about 'Microsoft busmouse' and actually mean PS/2 busmouse -- so
10103 count the pins on the connector.
10105 If you want to compile this as a module ( = code which can be
10106 inserted in and removed from the running kernel whenever you want),
10107 say M here and read Documentation/modules.txt. The module will be
10108 called msbusmouse.o.
10110 Apple Desktop Bus mouse support
10112 Say Y here if you have this type of bus mouse (4 pin connector) as
10113 is common on Macintoshes. You may want to read the Busmouse-HOWTO,
10114 available from http://www.linuxdoc.org/docs.html#howto .
10116 If you want to compile this as a module ( = code which can be
10117 inserted in and removed from the running kernel whenever you want),
10118 say M here and read Documentation/modules.txt. The module will be
10121 ATIXL busmouse support
10122 CONFIG_ATIXL_BUSMOUSE
10123 This is a rare type of busmouse that is connected to the back of an
10124 ATI video card. Say Y if you have one of those. Note however that
10125 most mice by ATI are actually Microsoft busmice; you should say Y to
10126 "Microsoft busmouse support" above if you have one of those. Read
10127 the Busmouse-HOWTO, available from
10128 http://www.linuxdoc.org/docs.html#howto .
10130 If you want to compile this as a module ( = code which can be
10131 inserted in and removed from the running kernel whenever you want),
10132 say M here and read Documentation/modules.txt. The module will be
10133 called atixlmouse.o.
10135 If you are unsure, say N and read the HOWTO nevertheless: it will
10136 tell you what you have.
10138 QIC-02 tape support
10140 If you have a non-SCSI tape drive like that, say Y. Or, if you want
10141 to compile this driver as a module ( = code which can be inserted in
10142 and removed from the running kernel whenever you want), say M here
10143 and read Documentation/modules.txt. The module will be called
10146 Do you want runtime configuration for QIC-02
10147 CONFIG_QIC02_DYNCONF
10148 You can either configure this driver once and for all by editing a
10149 header file (include/linux/tpqic02.h), in which case you should
10150 say N, or you can fetch a program via anonymous FTP which is able
10151 to configure this driver during runtime. The program to do this is
10152 called 'qic02conf' and it is part of the tpqic02-support-X.Y.tar.gz
10155 If you want to use the qic02conf program, say Y.
10157 Floppy tape drive (QIC-80/40/3010/3020/TR-1/TR-2/TR-3) support
10159 If you have a tape drive that is connected to your floppy
10160 controller, say Y here.
10162 Some tape drives (like the Seagate "Tape Store 3200" or the Iomega
10163 "Ditto 3200" or the Exabyte "Eagle TR-3") come with a "high speed"
10164 controller of their own. These drives (and their companion
10165 controllers) are also supported if you say Y here.
10167 If you have a special controller (such as the CMS FC-10, FC-20,
10168 Mountain Mach-II, or any controller that is based on the Intel 82078
10169 FDC like the high speed controllers by Seagate and Exabyte and
10170 Iomega's "Ditto Dash") you must configure it by selecting the
10171 appropriate entries from the "Floppy tape controllers" sub-menu
10172 below and possibly modify the default values for the IRQ and DMA
10173 channel and the IO base in ftape's configuration menu.
10175 If you want to use your floppy tape drive on a PCI-bus based system,
10176 please read the file drivers/char/ftape/README.PCI.
10178 The ftape kernel driver is also available as a runtime loadable
10179 module ( = code which can be inserted in and removed from the
10180 running kernel whenever you want). If you want to compile it as a
10181 module, say M here and read Documentation/modules.txt. The module
10182 will be called ftape.o.
10184 Note that the Ftape-HOWTO is out of date (sorry) and documents the
10185 older version 2.08 of this software but still contains useful
10186 information. There is a web page with more recent documentation at
10187 http://www.math1.rwth-aachen.de/~heine/ftape/ . This page
10188 always contains the latest release of the ftape driver and useful
10189 information (backup software, ftape related patches and
10190 documentation, FAQ). Note that the file system interface has changed
10191 quite a bit compared to previous versions of ftape. Please read
10192 Documentation/ftape.txt.
10194 The file system interface for ftape
10196 Normally, you want to say Y or M. DON'T say N here or you
10197 WON'T BE ABLE TO USE YOUR FLOPPY TAPE DRIVE.
10199 The ftape module itself no longer contains the routines necessary
10200 to interface with the kernel VFS layer (i.e. to actually write data
10201 to and read data from the tape drive). Instead the file system
10202 interface (i.e. the hardware independent part of the driver) has
10203 been moved to a separate module.
10205 If you say M zftape will be compiled as a runtime loadable
10206 module ( = code which can be inserted in and removed from the
10207 running kernel whenever you want). In this case you should read
10208 Documentation/modules.txt. The module will be called zftape.o.
10210 Regardless of whether you say Y or M here, an additional runtime
10211 loadable module called `zft-compressor.o' which contains code to
10212 support user transparent on-the-fly compression based on Ross
10213 William's lzrw3 algorithm will be produced. If you have enabled the
10214 kernel module loader (i.e. have said Y to "Kernel module loader
10215 support", above) then `zft-compressor.o' will be loaded
10216 automatically by zftape when needed.
10218 Despite its name, zftape does NOT use compression by default. The
10219 file Documentation/ftape.txt contains a short description of the
10220 most important changes in the file system interface compared to
10221 previous versions of ftape. The ftape home page
10222 http://www-math.math.rwth-aachen.de/~LBFM/claus/ftape/ contains
10223 further information.
10225 IMPORTANT NOTE: zftape can read archives created by previous
10226 versions of ftape and provide file mark support (i.e. fast skipping
10227 between tape archives) but previous version of ftape will lack file
10228 mark support when reading archives produced by zftape.
10230 Default block size for zftape
10231 CONFIG_ZFT_DFLT_BLK_SZ
10232 If unsure leave this at its default value, i.e. 10240. Note that
10233 you specify only the default block size here. The block size can be
10234 changed at run time using the MTSETBLK tape operation with the
10235 MTIOCTOP ioctl (i.e. with "mt -f /dev/qft0 setblk #BLKSZ" from the
10236 shell command line).
10238 The probably most striking difference between zftape and previous
10239 versions of ftape is the fact that all data must be written or read
10240 in multiples of a fixed block size. The block size defaults to
10241 10240 which is what GNU tar uses. The values for the block size
10242 should be either 1 or multiples of 1024 up to a maximum value of
10243 63488 (i.e. 62 K). If you specify `1' then zftape's builtin
10244 compression will be disabled.
10246 Reasonable values are `10240' (GNU tar's default block size),
10247 `5120' (afio's default block size), `32768' (default block size some
10248 backup programs assume for SCSI tape drives) or `1' (no restriction
10249 on block size, but disables builtin compression).
10251 Number of DMA buffers
10252 CONFIG_FT_NR_BUFFERS
10253 Please leave this at `3' unless you REALLY know what you are doing.
10254 It is not necessary to change this value. Values below 3 make the
10255 proper use of ftape impossible, values greater than 3 are a waste of
10256 memory. You can change the amount of DMA memory used by ftape at
10257 runtime with "mt -f /dev/qft0 setdrvbuffer #NUMBUFFERS". Each buffer
10258 wastes 32 KB of memory. Please note that this memory cannot be
10261 Procfs entry for ftape
10263 Optional. Saying Y will result in creation of a directory
10264 `/proc/ftape' under the proc file system. The files can be viewed
10265 with your favorite pager (i.e. use "more /proc/ftape/history" or
10266 "less /proc/ftape/history" or simply "cat /proc/ftape/history"). The
10267 file will contain some status information about the inserted
10268 cartridge, the kernel driver, your tape drive, the floppy disk
10269 controller and the error history for the most recent use of the
10270 kernel driver. Saying Y will enlarge the size of the ftape driver
10271 by approximately 2 KB.
10273 WARNING: When compiling ftape as a module (i.e. saying M to
10274 "Floppy tape drive") it is dangerous to use ftape's proc file system
10275 interface. Accessing `/proc/ftape' while the module is unloaded will
10276 result in a kernel Oops. This cannot be fixed from inside ftape.
10278 Controlling the amount of debugging output of ftape
10279 CONFIG_FT_NORMAL_DEBUG
10280 This option controls the amount of debugging output the ftape driver
10281 is ABLE to produce; it does not increase or diminish the debugging
10282 level itself. If unsure, leave this at its default setting,
10283 i.e. choose "Normal".
10285 Ftape can print lots of debugging messages to the system console
10286 resp. kernel log files. Reducing the amount of possible debugging
10287 output reduces the size of the kernel module by some KB, so it might
10288 be a good idea to use "None" for emergency boot floppies.
10290 If you want to save memory then the following strategy is
10291 recommended: leave this option at its default setting "Normal" until
10292 you know that the driver works as expected, afterwards reconfigure
10293 the kernel, this time specifying "Reduced" or "None" and recompile
10294 and install the kernel as usual. Note that choosing "Excessive"
10295 debugging output does not increase the amount of debugging output
10296 printed to the console but only makes it possible to produce
10297 "Excessive" debugging output.
10299 Please read Documentation/ftape.txt for a short description
10300 how to control the amount of debugging output.
10302 The floppy drive controller for ftape
10304 Only change this setting if you have a special controller. If you
10305 didn't plug any add-on card into your computer system but just
10306 plugged the floppy tape cable into the already existing floppy drive
10307 controller then you don't want to change the default setting,
10308 i.e. choose "Standard".
10310 Choose "MACH-2" if you have a Mountain Mach-2 controller.
10311 Choose "FC-10/FC-20" if you have a Colorado FC-10 or FC-20
10313 Choose "Alt/82078" if you have another controller that is located at
10314 an IO base address different from the standard floppy drive
10315 controller's base address of `0x3f0', or uses an IRQ (interrupt)
10316 channel different from `6', or a DMA channel different from
10317 `2'. This is necessary for any controller card that is based on
10318 Intel's 82078 FDC such as Seagate's, Exabyte's and Iomega's "high
10319 speed" controllers.
10321 If you choose something other than "Standard" then please make
10322 sure that the settings for the IO base address and the IRQ and DMA
10323 channel in the configuration menus below are correct. Use the manual
10324 of your tape drive to determine the correct settings!
10326 If you are already successfully using your tape drive with another
10327 operating system then you definitely should use the same settings
10328 for the IO base, the IRQ and DMA channel that have proven to work
10329 with that other OS.
10331 Note that this menu lets you specify only the default setting for
10332 the hardware setup. The hardware configuration can be changed at
10333 boot time (when ftape is compiled into the kernel, i.e. if you
10334 have said Y to "Floppy tape drive") or module load time (i.e. if you
10335 have said M to "Floppy tape drive").
10337 Please read also the file Documentation/ftape.txt which
10338 contains a short description of the parameters that can be set at
10339 boot or load time. If you want to use your floppy tape drive on a
10340 PCI-bus based system, please read the file
10341 drivers/char/ftape/README.PCI.
10343 IO base of the floppy disk controller used with Ftape
10345 You don't need to specify a value if the following default
10346 settings for the base IO address are correct:
10347 <<< MACH-2 : 0x1E0 >>>
10348 <<< FC-10/FC-20: 0x180 >>>
10349 <<< Secondary : 0x370 >>>
10350 Secondary refers to a secondary FDC controller like the "high speed"
10351 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
10352 Please make sure that the setting for the IO base address
10353 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
10354 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
10355 successfully using the tape drive with another operating system then
10356 you definitely should use the same settings for the IO base that has
10357 proven to work with that other OS.
10359 Note that this menu lets you specify only the default setting for
10360 the IO base. The hardware configuration can be changed at boot time
10361 (when ftape is compiled into the kernel, i.e. if you specified Y to
10362 "Floppy tape drive") or module load time (i.e. if you have said M to
10363 "Floppy tape drive").
10365 Please read also the file Documentation/ftape.txt which contains a
10366 short description of the parameters that can be set at boot or load
10369 IRQ channel for the floppy disk controller used with Ftape
10371 You don't need to specify a value if the following default
10372 settings for the interrupt channel are correct:
10374 <<< FC-10/FC-20: 9 >>>
10375 <<< Secondary : 6 >>>
10376 Secondary refers to secondary a FDC controller like the "high speed"
10377 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
10378 Please make sure that the setting for the IO base address
10379 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
10380 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
10381 successfully using the tape drive with another operating system then
10382 you definitely should use the same settings for the IO base that has
10383 proven to work with that other OS.
10385 Note that this menu lets you specify only the default setting for
10386 the IRQ channel. The hardware configuration can be changed at boot
10387 time (when ftape is compiled into the kernel, i.e. if you said Y to
10388 "Floppy tape drive") or module load time (i.e. if you said M to
10389 "Floppy tape drive").
10391 Please read also the file Documentation/ftape.txt which contains a
10392 short description of the parameters that can be set at boot or load
10395 DMA channel for the floppy disk controller used with Ftape
10397 You don't need to specify a value if the following default
10398 settings for the DMA channel are correct:
10400 <<< FC-10/FC-20: 3 >>>
10401 <<< Secondary : 2 >>>
10402 Secondary refers to a secondary FDC controller like the "high speed"
10403 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
10404 Please make sure that the setting for the IO base address
10405 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
10406 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
10407 successfully using the tape drive with another operating system then
10408 you definitely should use the same settings for the IO base that has
10409 proven to work with that other OS.
10411 Note that this menu lets you specify only the default setting for
10412 the DMA channel. The hardware configuration can be changed at boot
10413 time (when ftape is compiled into the kernel, i.e. if you said Y to
10414 "Floppy tape drive") or module load time (i.e. if you said M to
10415 "Floppy tape drive").
10417 Please read also the file Documentation/ftape.txt which contains a
10418 short description of the parameters that can be set at boot or load
10421 FDC FIFO Threshold before requesting DMA service
10423 Set the FIFO threshold of the FDC. If this is higher the DMA
10424 controller may serve the FDC after a higher latency time. If this is
10425 lower, fewer DMA transfers occur leading to less bus contention.
10426 You may try to tune this if ftape annoys you with "reduced data
10427 rate because of excessive overrun errors" messages. However, this
10428 doesn't seem to have too much effect.
10430 If unsure, don't touch the initial value, i.e. leave it at "8".
10432 FDC maximum data rate
10433 CONFIG_FT_FDC_MAX_RATE
10434 With some motherboard/FDC combinations ftape will not be able to
10435 run your FDC/tape drive combination at the highest available
10436 speed. If this is the case you'll encounter "reduced data rate
10437 because of excessive overrun errors" messages and lots of retries
10438 before ftape finally decides to reduce the data rate.
10440 In this case it might be desirable to tell ftape beforehand that
10441 it need not try to run the tape drive at the highest available
10442 speed. If unsure, leave this disabled, i.e. leave it at 2000
10445 Direct Rendering Manager (XFree86 DRI support)
10447 Kernel-level support for the Direct Rendering Infrastructure (DRI)
10448 introduced in XFree86 4.x. These modules provide support for
10449 synchronization, security, and DMA transfers. Select the module that
10450 provides support for your graphics card.
10452 tdfx Direct Rendering Manager (XFree86 DRI support)
10454 Choose M here if you have a 3dfx Banshee/Voodoo3 graphics card.
10456 3dlabs GMX 2000 Direct Rendering Driver (XFree86 DRI support)
10458 Choose M here if you have a 3dlabs GMX 2000 graphics card.
10460 MTRR control and configuration
10462 On Intel P6 family processors (Pentium Pro, Pentium II and later)
10463 the Memory Type Range Registers (MTRRs) may be used to control
10464 processor access to memory ranges. This is most useful when you have
10465 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
10466 allows bus write transfers to be combined into a larger transfer
10467 before bursting over the PCI/AGP bus. This can increase performance
10468 of image write operations 2.5 times or more. This option creates a
10469 /proc/mtrr file which may be used to manipulate your
10470 MTRRs. Typically the X server should use this. This should have a
10471 reasonably generic interface so that similar control registers on
10472 other processors can be easily supported.
10474 The Cyrix 6x86, 6x86MX and M II processors have Address Range
10475 Registers (ARRs) which provide a similar functionality to MTRRs. For
10476 these, the ARRs are used to emulate the MTRRs, which means that it
10477 makes sense to say Y here for these processors as well.
10479 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
10480 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
10481 write-combining. All of these processors are supported by this code.
10483 The Centaur C6 (WinChip) has 8 MCRs, allowing write-combining. These
10486 Saying Y here also fixes a problem with buggy SMP BIOSes which only
10487 set the MTRRs for the boot CPU and not the secondary CPUs. This can
10488 lead to all sorts of problems.
10490 You can safely say Y even if your machine doesn't have MTRRs, you'll
10491 just add about 9K to your kernel.
10493 See Documentation/mtrr.txt for more information.
10495 Main CPU frequency, only for DEC alpha machine
10496 CONFIG_FT_ALPHA_CLOCK
10497 On some DEC Alpha machines the CPU clock frequency cannot be
10498 determined automatically, so you need to specify it here ONLY if
10499 running a DEC Alpha, otherwise this setting has no effect.
10501 Zilog serial support
10503 This driver does not exist at this point, so you might as well
10506 Double Talk PC internal speech card support
10508 This driver is for the DoubleTalk PC, a speech synthesizer
10509 manufactured by RC Systems (http://www.rcsys.com/ ). It is also
10510 called the `internal DoubleTalk'. If you want to compile this as a
10511 module ( = code which can be inserted in and removed from the
10512 running kernel whenever you want), say M here and read
10513 Documentation/modules.txt. The module will be called dtlk.o.
10515 Siemens R3964 serial protocol support
10517 This driver allows synchronous communication with devices using the
10518 Siemens R3964 packet protocol. Unless you are dealing with special
10519 hardware like PLCs, you are unlikely to need this.
10521 To compile this driver as a module ( = code which can be inserted in
10522 and removed from the running kernel whenever you want), say M here
10523 and read Documentation/modules.txt. The module will be called
10528 Applicom intelligent fieldbus card support
10530 This driver provides the kernel-side support for the intelligent
10531 fieldbus cards made by Applicom International. More information
10532 about these cards can be found on the WWW at the address
10533 http://www.applicom-int.com/ , or by email from David Woodhouse
10536 To compile this driver as a module ( = code which can be inserted in
10537 and removed from the running kernel whenever you want), say M here
10538 and read Documentation/modules.txt. The module will be called
10543 Enter S1 for sleep (EXPERIMENTAL)
10544 CONFIG_ACPI_S1_SLEEP
10545 This enable ACPI compliant devices to enter level 1 of ACPI saving
10546 power levels. Basically, this will let them entering in sleep mode.
10548 Advanced Power Management
10550 APM is a BIOS specification for saving power using several different
10551 techniques. This is mostly useful for battery powered laptops with
10552 APM compliant BIOSes. If you say Y here, the system time will be
10553 reset after a RESUME operation, the /proc/apm device will provide
10554 battery status information, and user-space programs will receive
10555 notification of APM "events" (e.g. battery status change).
10557 If you select "Y" here, you can disable actual use of the APM
10558 BIOS by passing the "apm=off" option to the kernel at boot time.
10560 Note that the APM support is almost completely disabled for
10561 machines with more than one CPU.
10563 Supporting software is available; for more information, read the
10564 Battery Powered Linux mini-HOWTO, available from
10565 http://www.linuxdoc.org/docs.html#howto .
10567 This driver does not spin down disk drives (see the hdparm(8)
10568 manpage ("man 8 hdparm") for that), and it doesn't turn off
10569 VESA-compliant "green" monitors.
10571 This driver does not support the TI 4000M TravelMate and the ACER
10572 486/DX4/75 because they don't have compliant BIOSes. Many "green"
10573 desktop machines also don't have compliant BIOSes, and this driver
10574 may cause those machines to panic during the boot phase.
10576 If you are running Linux on a laptop, you may also want to read the
10577 Linux Laptop home page on the WWW at
10578 http://www.cs.utexas.edu/users/kharker/linux-laptop/ .
10580 Generally, if you don't have a battery in your machine, there isn't
10581 much point in using this driver and you should say N. If you get
10582 random kernel OOPSes or reboots that don't seem to be related to
10583 anything, try disabling/enabling this option (or disabling/enabling
10586 Some other things you should try when experiencing seemingly random,
10589 1) make sure that you have enough swap space and that it is
10591 2) pass the "no-hlt" option to the kernel
10592 3) switch on floating point emulation in the kernel and pass
10593 the "no387" option to the kernel
10594 4) pass the "floppy=nodma" option to the kernel
10595 5) pass the "mem=4M" option to the kernel (thereby disabling
10596 all but the first 4 MB of RAM)
10597 6) make sure that the CPU is not over clocked.
10598 7) read the sig11 FAQ at http://www.bitwizard.nl/sig11/
10599 8) disable the cache from your BIOS settings
10600 9) install a fan for the video card or exchange video RAM
10601 10) install a better fan for the CPU
10602 11) exchange RAM chips
10603 12) exchange the motherboard.
10605 Ignore USER SUSPEND
10606 CONFIG_APM_IGNORE_USER_SUSPEND
10607 This option will ignore USER SUSPEND requests. On machines with a
10608 compliant APM BIOS, you want to say N. However, on the NEC Versa M
10609 series notebooks, it is necessary to say Y because of a BIOS bug.
10611 Enable APM at boot time
10612 CONFIG_APM_DO_ENABLE
10613 Enable APM features at boot time. From page 36 of the APM BIOS
10614 specification: "When disabled, the APM BIOS does not automatically
10615 power manage devices, enter the Standby State, enter the Suspend
10616 State, or take power saving steps in response to CPU Idle calls."
10617 This driver will make CPU Idle calls when Linux is idle (unless this
10618 feature is turned off -- see "Do CPU IDLE calls", below). This
10619 should always save battery power, but more complicated APM features
10620 will be dependent on your BIOS implementation. You may need to turn
10621 this option off if your computer hangs at boot time when using APM
10622 support, or if it beeps continuously instead of suspending. Turn
10623 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
10624 T400CDT. This is off by default since most machines do fine without
10628 CONFIG_APM_CPU_IDLE
10629 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
10630 On some machines, this can activate improved power savings, such as
10631 a slowed CPU clock rate, when the machine is idle. These idle calls
10632 are made after the idle loop has run for some length of time (e.g.,
10633 333 mS). On some machines, this will cause a hang at boot time or
10634 whenever the CPU becomes idle. (On machines with more than one CPU,
10635 this option does nothing.)
10637 Enable console blanking using APM
10638 CONFIG_APM_DISPLAY_BLANK
10639 Enable console blanking using the APM. Some laptops can use this to
10640 turn off the LCD backlight when the screen blanker of the Linux
10641 virtual console blanks the screen. Note that this is only used by
10642 the virtual console screen blanker, and won't turn off the backlight
10643 when using the X Window system. This also doesn't have anything to
10644 do with your VESA-compliant power-saving monitor. Further, this
10645 option doesn't work for all laptops -- it might not turn off your
10646 backlight at all, or it might print a lot of errors to the console,
10647 especially if you are using gpm.
10649 Ignore multiple suspend/standby events
10650 CONFIG_APM_IGNORE_MULTIPLE_SUSPEND
10651 This option is necessary on the IBM Thinkpad 560, but should work on
10652 all other laptops. When the APM BIOS returns multiple suspend or
10653 standby events while one is already being processed they will be
10654 ignored. Without this the Thinkpad 560 has troubles with the user
10655 level daemon apmd, and with the PCMCIA package pcmcia-cs.
10657 Ignore multiple suspend/resume cycles
10658 CONFIG_APM_IGNORE_SUSPEND_BOUNCE
10659 This option is necessary on the Dell Inspiron 3200 and others, but
10660 should be safe for all other laptops. When enabled, a system suspend
10661 event that occurs within three seconds of a resume is ignored.
10662 Without this the Inspiron will shut itself off a few seconds after
10663 you open the lid, requiring you to press the power button to resume
10664 it a second time. Say Y.
10666 RTC stores time in GMT
10667 CONFIG_APM_RTC_IS_GMT
10668 Say Y here if your RTC (Real Time Clock a.k.a. hardware clock)
10669 stores the time in GMT (Greenwich Mean Time). Say N if your RTC
10672 It is in fact recommended to store GMT in your RTC, because then you
10673 don't have to worry about daylight savings time changes. The only
10674 reason not to use GMT in your RTC is if you also run a broken OS
10675 that doesn't understand GMT.
10677 Allow interrupts during APM BIOS calls
10678 CONFIG_APM_ALLOW_INTS
10679 Normally we disable external interrupts while we are making calls to
10680 the APM BIOS as a measure to lessen the effects of a badly behaving
10681 BIOS implementation. The BIOS should reenable interrupts if it
10682 needs to. Unfortunately, some BIOSes do not - especially those in
10683 many of the newer IBM Thinkpads. If you experience hangs when you
10684 suspend, try setting this to Y. Otherwise, say N.
10686 Entry point offset fix (some Acer laptops)
10687 CONFIG_APM_BAD_ENTRY_OFFSET
10688 Some implementations of the APM BIOS provide the driver with a bad
10689 entry point offset. If you set this option to Y, then the upper
10690 sixteen bits of the offset will be set to zero. This is usually
10691 unnecessary but harmless. This is required for the Acer Travelmate
10692 510DX, Travelmate 510T and Extensa 503T. For others, say N.
10694 Use real mode APM BIOS call to power off
10695 CONFIG_APM_REAL_MODE_POWER_OFF
10696 Use real mode APM BIOS calls to switch off the computer. This is
10697 a work-around for a number of buggy BIOSes. Switch this option on if
10698 your computer crashes instead of powering off properly.
10700 Watchdog Timer Support
10702 If you say Y here (and to one of the following options) and create a
10703 character special file /dev/watchdog with major number 10 and minor
10704 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
10705 subsequently opening the file and then failing to write to it for
10706 longer than 1 minute will result in rebooting the machine. This
10707 could be useful for a networked machine that needs to come back
10708 online as fast as possible after a lock-up. There's both a watchdog
10709 implementation entirely in software (which can sometimes fail to
10710 reboot the machine) and a driver for hardware watchdog boards, which
10711 are more robust and can also keep track of the temperature inside
10712 your computer. For details, read Documentation/watchdog.txt in the
10715 The watchdog is usually used together with the watchdog daemon
10716 which is available via FTP (user: anonymous) from
10717 ftp://tsx-11.mit.edu/pub/linux/sources/sbin/ . This daemon can also
10718 monitor NFS connections and can reboot the machine when the process
10723 Disable watchdog shutdown on close
10724 CONFIG_WATCHDOG_NOWAYOUT
10725 The default watchdog behaviour (which you get if you say N here) is
10726 to stop the timer if the process managing it closes the file
10727 /dev/watchdog. It's always remotely possible that this process might
10728 get killed. If you say Y here, the watchdog cannot be stopped once
10729 it has been started.
10733 If you have a WDT500P or WDT501P watchdog board, say Y here,
10734 otherwise N. It is not possible to probe for this board, which means
10735 that you have to set the IO port and IRQ it uses in the kernel
10736 source at the top of drivers/char/wdt.c.
10738 If you want to compile this as a module ( = code which can be
10739 inserted in and removed from the running kernel whenever you want),
10740 say M here and read Documentation/modules.txt. The module will be
10745 Saying Y here and creating a character special file /dev/temperature
10746 with major number 10 and minor number 131 ("man mknod") will give
10747 you a thermometer inside your computer: reading from
10748 /dev/temperature yields one byte, the temperature in degrees
10749 Fahrenheit. This works only if you have a WDT501P watchdog board
10754 Enable the Fan Tachometer on the WDT501. Only do this if you have a
10755 fan tachometer actually set up.
10758 CONFIG_SOFT_WATCHDOG
10759 A software monitoring watchdog. This will fail to reboot your system
10760 from some situations that the hardware watchdog will recover
10761 from. Equally it's a lot cheaper to install.
10763 This driver is also available as a module ( = code which can be
10764 inserted in and removed from the running kernel whenever you want).
10765 If you want to compile it as a module, say M here and read
10766 Documentation/modules.txt. The module will be called softdog.o.
10768 Berkshire Products PC Watchdog
10770 This is the driver for the Berkshire Products PC Watchdog card.
10771 This card simply watches your kernel to make sure it doesn't freeze,
10772 and if it does, it reboots your computer after a certain amount of
10773 time. This driver is like the WDT501 driver but for different
10774 hardware. Please read Documentation/pcwd-watchdog.txt. The PC
10775 watchdog cards can be ordered from http://www.berkprod.com .
10777 This driver is also available as a module ( = code which can be
10778 inserted in and removed from the running kernel whenever you want).
10779 The module is called pcwd.o. If you want to compile it as a module,
10780 say M here and read Documentation/modules.txt.
10782 Most people will say N.
10784 Acquire SBC Watchdog Timer
10786 This is the driver for the hardware watchdog on the PSC-6x86 Single
10787 Board Computer produced by Acquire Inc (and others). This watchdog
10788 simply watches your kernel to make sure it doesn't freeze, and if
10789 it does, it reboots your computer after a certain amount of time.
10791 This driver is like the WDT501 driver but for different hardware.
10792 This driver is also available as a module ( = code which can be
10793 inserted in and removed from the running kernel whenever you want).
10794 The module is called pscwdt.o. If you want to compile it as a
10795 module, say M here and read Documentation/modules.txt. Most people
10798 Intel P6 CPU Microcode Update Support
10800 If you say Y here you will be able to update microcode on
10801 Intel processors in P6 family, e.g. Pentium Pro, Pentium II,
10802 Pentium III, Xeon etc. You will obviously need the actual microcode
10803 binary data itself which is not shipped with the Linux kernel.
10804 Contact Intel to obtain the latest revision of microcode for
10805 your CPU(s). With this support compiled you can use dd(1) to write
10806 microcode, for example:
10808 # dd if=/etc/microcode of=/proc/driver/microcode bs=98304 count=1
10810 You need to be superuser to do that.
10812 This driver is also available as a module ( = code which can be
10813 inserted in and removed from the running kernel whenever you want).
10814 The module will be called microcode.o. If you want to compile it as a
10815 module, say M here and read Documentation/modules.txt.
10817 Enhanced Real Time Clock Support
10819 If you say Y here and create a character special file /dev/rtc with
10820 major number 10 and minor number 135 using mknod ("man mknod"), you
10821 will get access to the real time clock built into your computer.
10822 Every PC has such a clock built in. It can be used to generate
10823 signals from as low as 1Hz up to 8192Hz, and can also be used
10824 as a 24 hour alarm. It reports status information via the file
10825 /proc/driver/rtc and its behaviour is set by various ioctls on
10828 If you run Linux on a multiprocessor machine and said Y to
10829 "Symmetric Multi Processing" above, you should say Y here to read
10830 and set the RTC in an SMP compatible fashion.
10832 If you think you have a use for such a device (such as periodic data
10833 sampling), then say Y here, and read Documentation/rtc.txt for
10836 Tadpole ANA H8 Support
10838 The Hitachi H8/337 is a microcontroller used to deal with the power
10839 and thermal environment. If you say Y here, you will be able to
10840 communicate with it via a character special device.
10846 If you say Y here and create a character special file /dev/nvram
10847 with major number 10 and minor number 144 using mknod ("man mknod"),
10848 you get read and write access to the 50 bytes of non-volatile memory
10849 in the real time clock (RTC), which is contained in every PC and
10852 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
10853 on Ataris. /dev/nvram may be used to view settings there, or to
10854 change them (with some utility). It could also be used to frequently
10855 save a few bits of very important data that may not be lost over
10856 power-off and for which writing to disk is too insecure. Note
10857 however that most NVRAM space in a PC belongs to the BIOS and you
10858 should NEVER idly tamper with it. See Ralf Brown's interrupt list
10859 for a guide to the use of CMOS bytes by your BIOS.
10861 On Atari machines, /dev/nvram is always configured and does not need
10864 This driver is also available as a module ( = code which can be
10865 inserted in and removed from the running kernel whenever you want).
10866 The module will be called nvram.o. If you want to compile it as a
10867 module, say M here and read Documentation/modules.txt.
10871 If you have a joystick, 6dof controller, gamepad, steering wheel,
10872 weapon control system or something like that you can say Y here to
10873 enable generic support for these controllers. You will also need to
10874 say Y or M to at least one of the hardware specific drivers. This
10875 will make the controllers available as /dev/jsX devices. Please read
10876 the file Documentation/joystick.txt which contains more information
10877 and the location of the joystick package that you'll need.
10881 Say Y here if you have a controller that connects to the PC
10882 gameport. This supports many different types, including joysticks
10883 with throttle control, with rudders, or with extensions like
10884 additional hats and buttons compatible with CH Flightstick Pro,
10885 ThrustMaster FCS or 6 and 8 button gamepads. For more information on
10886 how to use the driver please read Documentation/joystick.txt
10888 FPGaming and MadCatz A3D
10889 CONFIG_JOY_ASSASSIN
10890 Say Y here if you have an FPGaming or MadCatz controller using the
10891 A3D protocol over the PC gameport. For more information on how to
10892 use the driver please read Documentation/joystick.txt
10896 Say Y here if you have a Gravis controller using the GrIP protocol
10897 over the PC gameport. For more information on how to use the driver
10898 please read Documentation/joystick.txt
10901 CONFIG_JOY_LOGITECH
10902 Say Y here if you have a Logitech controller using the ADI
10903 protocol over the PC gameport. For more information on how to use
10904 the driver please read Documentation/joystick.txt
10906 Microsoft SideWinder
10907 CONFIG_JOY_SIDEWINDER
10908 Say Y here if you have a Microsoft controller using the Digital
10909 Overdrive protocol over PC gameport. For more information on how to
10910 use the driver please read Documentation/joystick.txt
10912 ThrustMaster DirectConnect
10913 CONFIG_JOY_THRUSTMASTER
10914 Say Y here if you have a ThrustMaster controller using the
10915 DirectConnect (BSP) protocol over the PC gameport. For more
10916 information on how to use the driver please read
10917 Documentation/joystick.txt
10919 Creative Labs Blaster
10920 CONFIG_JOY_CREATIVE
10921 Say Y here if you have a Creative Labs controller using the
10922 Blaster protocol over the PC gameport. For more information on how
10923 to use the driver please read Documentation/joystick.txt
10925 PDPI Lightning 4 card
10926 CONFIG_JOY_LIGHTNING
10927 Say Y here if you have a PDPI Lightning 4 gamecard and an analog
10928 joystick or gamepad connected to it. For more information on how to
10929 use the driver please read Documentation/joystick.txt
10931 Trident 4DWave and Aureal Vortex gameport
10933 Say Y here if you have a Trident 4DWave DX/NX or Aureal Vortex 1/2
10934 card and want to use its gameport in its enhanced digital mode
10935 with and ordinary analog joystick. For more information on how to
10936 use the driver please read Documentation/joystick.txt
10938 Magellan and Space Mouse
10939 CONFIG_JOY_MAGELLAN
10940 Say Y here if you have a Magellan or Space Mouse 6DOF controller
10941 connected to your computer's serial port. For more information on
10942 how to use the driver please read Documentation/joystick.txt
10944 SpaceTec SpaceOrb 360 and SpaceBall Avenger
10945 CONFIG_JOY_SPACEORB
10946 Say Y here if you have a SpaceOrb 360 or SpaceBall Avenger 6DOF
10947 controller connected to your computer's serial port. For more
10948 information on how to use the driver please read
10949 Documentation/joystick.txt
10951 SpaceTec SpaceBall 4000 FLX
10952 CONFIG_JOY_SPACEBALL
10953 Say Y here if you have a SpaceTec SpaceBall 4000 FLX
10954 controller connected to your computer's serial port. For more
10955 information on how to use the driver please read
10956 Documentation/joystick.txt
10958 Logitech WingMan Warrior
10960 Say Y here if you have a Logitech WingMan Warrior controller
10961 connected to your computer's serial port. For more information on
10962 how to use the driver please read Documentation/joystick.txt
10964 NES, SNES, N64, PSX, Multi
10966 Say Y here if you have a Nintendo Entertainment System gamepad,
10967 Super Nintendo Entertainment System gamepad, Nintendo 64 gamepad,
10968 Sony PlayStation gamepad or a Multisystem -- Atari, Amiga,
10969 Commodore, Amstrad CPC joystick connected to your parallel port.
10970 For more information on how to use the driver please read
10971 Documentation/joystick.txt and Documentation/joystick-parport.txt
10975 Say Y here if you have a Sega Master System gamepad, Sega Genesis
10976 gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga,
10977 Commodore, Amstrad CPC joystick connected to your parallel port. For
10978 more information on how to use the driver please read
10979 Documentation/joystick.txt and Documentation/joystick-parport.txt
10981 TurboGraFX interface
10982 CONFIG_JOY_TURBOGRAFX
10983 Say Y here if you have the TurboGraFX interface by Steffen Schwenke,
10984 and want to use it with Multiststem -- Atari, Amiga, Commodore,
10985 Amstrad CPC joystick. For more information on how to use the driver
10986 please read Documentation/joystick.txt and
10987 Documentation/joystick-parport.txt
10991 Say Y here if you have an Amiga with a digital joystick connected
10992 to it. For more information on how to use the driver please read
10993 Documentation/joystick.txt
10995 Atomwide Serial Support
10996 CONFIG_ATOMWIDE_SERIAL
10997 If you have an Atomwide Serial card for an Acorn system, say Y to
10998 this option. The driver can handle 1, 2, or 3 port cards.
11001 The Serial Port Dual Serial Port
11002 CONFIG_DUALSP_SERIAL
11003 If you have the Serial Port's dual serial card for an Acorn system,
11004 say Y to this option. If unsure, say N
11008 If you say Y here and create a character device node /dev/nwbutton
11009 with major and minor numbers 10 and 158 ("man mknod"), then every
11010 time the orange button is pressed a number of times, the number of
11011 times the button was pressed will be written to that device.
11013 This is most useful for applications, as yet unwritten, which
11014 perform actions based on how many times the button is pressed in a
11017 Do not hold the button down for too long, as the driver does not
11018 alter the behaviour of the hardware reset circuitry attached to the
11019 button; it will still execute a hard reset if the button is held
11020 down for longer than approximately five seconds.
11022 This driver is also available as a module ( = code which can be
11023 inserted in and removed from the running kernel whenever you want).
11024 If you want to compile it as a module, say M here and read
11025 Documentation/modules.txt. The module will be called nwbutton.o.
11027 Most people will answer Y to this question and "Reboot Using Button"
11028 below to be able to initiate a system shutdown from the button.
11030 Reboot Using Button
11031 CONFIG_NWBUTTON_REBOOT
11032 If you say Y here, then you will be able to initiate a system
11033 shutdown and reboot by pressing the orange button a number of times.
11034 The number of presses to initiate the shutdown is two by default,
11035 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
11036 in nwbutton.h and recompiling the driver or, if you compile the
11037 driver as a module, you can specify the number of presses at load
11038 time with "insmod button reboot_count=<something>".
11042 If you have a sound card in your computer, i.e. if it can say more
11043 than an occasional beep, say Y. Be sure to have all the information
11044 about your sound card and its configuration down (I/O port,
11045 interrupt and DMA channel), because you will be asked for it.
11047 You want to read the Sound-HOWTO, available from
11048 http://www.linuxdoc.org/docs.html#howto . General information
11049 about the modular sound system is contained in the files
11050 Documentation/sound/Introduction. The file
11051 Documentation/sound/README.OSS contains some slightly outdated but
11052 still useful information as well.
11054 If you have a PnP sound card and you want to configure it at boot
11055 time using the ISA PnP tools (read
11056 http://www.roestock.demon.co.uk/isapnptools/ ), then you need to
11057 compile the sound card support as a module ( = code which can be
11058 inserted in and removed from the running kernel whenever you want)
11059 and load that module after the PnP configuration is finished. To do
11060 this, say M here and read Documentation/modules.txt as well as
11061 Documentation/sound/README.modules; the module will be called
11064 I'm told that even without a sound card, you can make your computer
11065 say more than an occasional beep, by programming the PC speaker.
11066 Kernel patches and supporting utilities to do that are in the pcsp
11067 package, available at ftp://ftp.infradead.org/pub/pcsp/.
11071 OSS is the Open Sound System suite of sound card drivers. They make
11072 sound programming easier since they provide a common API. Say Y or M
11073 here (the module will be called sound.o) if you haven't found a
11074 driver for your sound card above, then pick your driver from the
11077 Persistent DMA buffers
11079 Linux can often have problems allocating DMA buffers for ISA sound
11080 cards on machines with more than 16MB of RAM. This is because ISA
11081 DMA buffers must exist below the 16MB boundary and it is quite
11082 possible that a large enough free block in this region cannot be
11083 found after the machine has been running for a while. If you say Y
11084 here the DMA buffers (64Kb) will be allocated at boot time and kept
11085 until the shutdown. This option is only useful if you said Y to
11086 "OSS sound modules", above. If you said M to "OSS sound modules"
11087 then you can get the persistent DMA buffer functionality by passing
11088 the command-line argument "dmabuf=1" to the sound.o module.
11090 Say Y unless you have 16MB or less RAM or a PCI sound card.
11092 Support for Aztech Sound Galaxy (non-PnP) cards
11093 CONFIG_SOUND_SGALAXY
11094 This module initializes the older non Plug and Play sound galaxy
11095 cards from Aztech. It supports the Waverider Pro 32 - 3D and the
11096 Galaxy Washington 16.
11098 Support for AD1816(A) based cards (EXPERIMENTAL)
11099 CONFIG_SOUND_AD1816
11100 Say M here if you have a sound card based on the Analog Devices
11103 NOTE: This driver is still EXPERIMENTAL.
11104 See Documentation/sound/AD1816 for further information.
11106 Yamaha OPL3-SA1 audio controller
11107 CONFIG_SOUND_OPL3SA1
11108 Say Y or M if you have a Yamaha OPL3-SA1 sound chip, which is
11109 usually built into motherboards. Read Documentation/sound/OPL3-SA
11112 ProAudioSpectrum 16 support
11114 Answer Y only if you have a Pro Audio Spectrum 16, ProAudio Studio
11115 16 or Logitech SoundMan 16 sound card. Don't answer Y if you have
11116 some other card made by Media Vision or Logitech since they are not
11119 100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support
11121 Answer Y if you have an original Sound Blaster card made by Creative
11122 Labs or a 100% hardware compatible clone (like the Thunderboard or
11123 SM Games). For an unknown card you may answer Y if the card claims
11124 to be Sound Blaster-compatible.
11126 Please read the file Documentation/sound/Soundblaster.
11128 You should also say Y here for cards based on the Avance Logic
11129 ALS-007 chip (read Documentation/sound/ALS007) and for cards based
11130 on ESS chips (read Documentation/sound/ESS1868 and
11131 Documentation/sound/ESS). If you have an SB AWE 32 or SB AWE 64, say
11132 Y here and also to "Additional lowlevel drivers" and to "SB32/AWE
11133 support" below and read Documentation/sound/INSTALL.awe. If you have
11134 an IBM Mwave card, say Y here and read Documentation/sound/mwave.
11136 You can say M here to compile this driver as a module; the module is
11139 #Loopback MIDI device support
11140 #CONFIG_SOUND_VMIDI
11142 ### somebody please fill this in.
11145 Gravis Ultrasound support
11147 Say Y here for any type of Gravis Ultrasound card, including
11148 the GUS or GUS MAX. See also Documentation/sound/ultrasound for
11149 more information on configuring this card with modules.
11151 MPU-401 support (NOT for SB16)
11152 CONFIG_SOUND_MPU401
11153 Be careful with this question. The MPU401 interface is supported by
11154 all sound cards. However, some natively supported cards have their
11155 own driver for MPU401. Enabling this MPU401 option with these cards
11156 will cause a conflict. Also, enabling MPU401 on a system that
11157 doesn't really have a MPU401 could cause some trouble. If your card
11158 was in the list of supported cards, look at the card specific
11159 instructions in the drivers/sound/Readme.cards file. It's safe to
11160 answer Y if you have a true MPU401 MIDI interface card.
11163 CONFIG_SOUND_UART6850
11164 This option enables support for MIDI interfaces based on the 6850
11165 UART chip. This interface is rarely found on sound cards. It's safe
11166 to answer N to this question.
11170 Say Y here for ARM systems with the VIDC video controller and 16-bit
11171 Linear sound DACs. If unsure, say N.
11173 PSS (AD1848, ADSP-2115, ESC614) support
11175 Answer Y or M if you have an Orchid SW32, Cardinal DSP16, Beethoven
11176 ADSP-16 or some other card based on the PSS chipset (AD1848 codec +
11177 ADSP-2115 DSP chip + Echo ESC614 ASIC CHIP). For more information on
11178 how to compile it into the kernel or as a module see the file
11179 Documentation/sound/PSS.
11181 Enable PSS mixer (Beethoven ADSP-16 and other compatible)
11183 Answer Y for Beethoven ADSP-16. You may try to say Y also for other
11184 cards if they have master volume, bass, treble, and you can't
11185 control it under Linux. If you answer N for Beethoven ADSP-16, you
11186 can't control master volume, bass, treble and synth volume.
11188 If you said M to "PSS support" above, you may enable or disable this
11189 PSS mixer with the module parameter pss_mixer. For more information
11190 see the file Documentation/sound/PSS.
11192 Have DSPxxx.LD firmware file
11193 CONFIG_PSS_HAVE_BOOT
11194 If you have the DSPxxx.LD file or SYNTH.LD file for you card, say Y
11195 to include this file. Without this file the synth device (OPL) may
11198 Full pathname of DSPxxx.LD firmware file
11199 CONFIG_PSS_BOOT_FILE
11200 Enter the full pathname of your DSPxxx.LD file or SYNTH.LD file,
11203 16 bit sampling option of GUS (_NOT_ GUS MAX)
11205 Answer Y if you have installed the 16 bit sampling daughtercard on
11206 your GUS. Answer N if you have a GUS MAX, since saying Y here
11207 disables GUS MAX support.
11210 CONFIG_SOUND_GUSMAX
11211 Answer Y only if you have a Gravis Ultrasound MAX.
11213 Microsoft Sound System support
11215 Again think carefully before answering Y to this question. It's safe
11216 to answer Y if you have the original Windows Sound System card made
11217 by Microsoft or Aztech SG 16 Pro (or NX16 Pro). Also you may say Y
11218 in case your card is NOT among these:
11220 ATI Stereo F/X, AdLib, Audio Excell DSP16, Cardinal DSP16,
11221 Ensoniq SoundScape (and compatibles made by Reveal and Spea),
11222 Gravis Ultrasound, Gravis Ultrasound ACE, Gravis Ultrasound Max,
11223 Gravis Ultrasound with 16 bit option, Logitech Sound Man 16,
11224 Logitech SoundMan Games, Logitech SoundMan Wave, MAD16 Pro (OPTi
11225 82C929), Media Vision Jazz16, MediaTriX AudioTriX Pro, Microsoft
11226 Windows Sound System (MSS/WSS), Mozart (OAK OTI-601), Orchid
11227 SW32, Personal Sound System (PSS), Pro Audio Spectrum 16, Pro
11228 Audio Studio 16, Pro Sonic 16, Roland MPU-401 MIDI interface,
11229 Sound Blaster 1.0, Sound Blaster 16, Sound Blaster 16ASP, Sound
11230 Blaster 2.0, Sound Blaster AWE32, Sound Blaster Pro, TI TM4000M
11231 notebook, ThunderBoard, Turtle Beach Tropez, Yamaha FM
11232 synthesizers (OPL2, OPL3 and OPL4), 6850 UART MIDI Interface.
11234 For cards having native support in VoxWare, consult the card
11235 specific instructions in drivers/sound/Readme.cards. Some drivers
11236 have their own MSS support and saying Y to this option will cause a
11239 SGI Visual Workstation on-board audio
11241 Say Y or M if you have an SGI Visual Workstation and you want to
11242 be able to use its on-board audio. Read Documentation/sound/visws
11243 for more info on this driver's capabilities.
11245 Ensoniq Soundscape support
11246 CONFIG_SOUND_SSCAPE
11247 Answer Y if you have a sound card based on the Ensoniq SoundScape
11248 chipset. Such cards are being manufactured at least by Ensoniq, Spea
11249 and Reveal (Reveal makes also other cards).
11251 MediaTriX AudioTriX Pro support
11253 Answer Y if you have the AudioTriX Pro sound card manufactured
11256 Have TRXPRO.HEX firmware file
11257 CONFIG_TRIX_HAVE_BOOT
11258 The MediaTrix AudioTrix Pro has an on-board microcontroller which
11259 needs to be initialized by downloading the code from the file
11260 TRXPRO.HEX in the DOS driver directory. If you don't have the
11261 TRXPRO.HEX file handy you may skip this step. However, the SB and
11262 MPU-401 modes of AudioTrix Pro will not work without this file!
11264 Full pathname of TRXPRO.HEX firmware file
11265 CONFIG_TRIX_BOOT_FILE
11266 Enter the full pathname of your TRXPRO.HEX file, starting from /.
11268 Support for OPTi MAD16 and/or Mozart based cards
11270 Answer Y if your card has a Mozart (OAK OTI-601) or MAD16 (OPTi
11271 82C928 or 82C929 or 82C931) audio interface chip. For the 82C931,
11272 please read drivers/sound/README.C931. These chips are currently
11273 quite common so it's possible that many no-name cards have one of
11274 them. In addition the MAD16 chip is used in some cards made by known
11275 manufacturers such as Turtle Beach (Tropez), Reveal (some models)
11276 and Diamond (latest ones). Note however that the Tropez sound cards
11277 have their own driver; if you have one of those, say N here and Y or
11278 M to "Full support for Turtle Beach WaveFront", below.
11280 See also Documentation/sound/Opti and Documentation/sound/MAD16 for
11281 more information on setting these cards up as modules.
11283 Full support for Turtle Beach WaveFront synth/sound cards
11284 CONFIG_SOUND_WAVEFRONT
11285 Answer Y or M if you have a Tropez Plus, Tropez or Maui sound card
11286 and read the files Documentation/sound/Wavefront and
11287 Documentation/sound/Tropez+.
11289 Support MIDI in older MAD16 based cards (requires SB)
11290 CONFIG_MAD16_OLDCARD
11291 Answer Y (or M) if you have an older card based on the C928 or
11292 Mozart chipset and you want to have MIDI support. If you enable this
11293 option you also need to enable support for Sound Blaster.
11295 Support for Crystal CS4232 based (PnP) cards
11296 CONFIG_SOUND_CS4232
11297 Say Y here if you have a card based on the Crystal CS4232 chip set,
11298 which uses its own Plug and Play protocol.
11300 See Documentation/sound/CS4232 for more information on configuring
11303 Support for Yamaha OPL3-SA2, SA3, and SAx based PnP cards
11304 CONFIG_SOUND_OPL3SA2
11305 Say Y or M if you have a card based on one of these Yamaha
11306 sound chipsets. Read Documentation/sound/OPL3-SA2 for more
11307 information on configuring these cards.
11309 Support for Turtle Beach Wave Front (Maui, Tropez) synthesizers
11311 Say Y here if you have a Turtle Beach Wave Front, Maui, or Tropez
11314 Have OSWF.MOT firmware file
11315 CONFIG_MAUI_HAVE_BOOT
11316 Turtle Beach Maui and Tropez sound cards have a microcontroller
11317 which needs to be initialized prior to use. OSWF.MOT is a file
11318 distributed with the card's DOS/Windows drivers. Answer Y if you
11321 Full pathname of OSWF.MOT firmware file
11322 CONFIG_MAUI_BOOT_FILE
11323 Enter the full pathname of your OSWF.MOT file, starting from /.
11325 Support for Turtle Beach MultiSound Classic, Tahiti, Monterey
11326 CONFIG_SOUND_MSNDCLAS
11327 Say M here if you have a Turtle Beach MultiSound Classic, Tahiti or
11328 Monterey (not for the Pinnacle or Fiji).
11330 See Documentation/sound/MultiSound for important information about
11333 Full pathname of MSNDINIT.BIN firmware file
11334 CONFIG_MSNDCLAS_INIT_FILE
11335 The MultiSound cards have two firmware files which are required for
11336 operation, and are not currently included. These files can be
11337 obtained from Turtle Beach. See Documentation/sound/MultiSound for
11338 information on how to obtain this.
11340 Full pathname of MSNDPERM.BIN firmware file
11341 CONFIG_MSNDCLAS_PERM_FILE
11342 The MultiSound cards have two firmware files which are required for
11343 operation, and are not currently included. These files can be
11344 obtained from Turtle Beach. See Documentation/sound/MultiSound for
11345 information on how to obtain this.
11347 Support for Turtle Beach MultiSound Pinnacle, Fiji
11348 CONFIG_SOUND_MSNDPIN
11349 Say M here if you have a Turtle Beach MultiSound Pinnacle or Fiji.
11350 See Documentation/sound/MultiSound for important information about
11353 Full pathname of PNDSPINI.BIN firmware file
11354 CONFIG_MSNDPIN_INIT_FILE
11355 The MultiSound cards have two firmware files which are required for
11356 operation, and are not currently included. These files can be
11357 obtained from Turtle Beach. See Documentation/sound/MultiSound for
11358 information on how to obtain this.
11360 Full pathname of PNDSPERM.BIN firmware file
11361 CONFIG_MSNDPIN_PERM_FILE
11362 The MultiSound cards have two firmware files which are required for
11363 operation, and are not currently included. These files can be
11364 obtained from Turtle Beach. See Documentation/sound/MultiSound for
11365 information on how to obtain this.
11367 MSND Pinnacle have S/PDIF I/O
11368 CONFIG_MSNDPIN_DIGITAL
11369 If you have the S/PDIF daughter board for the Pinnacle or Fiji,
11370 answer Y here; otherwise, say N. If you have this, you will be able
11371 to play and record from the S/PDIF port (digital signal). See
11372 Documentation/sound/MultiSound for information on how to make use of
11375 MSND Pinnacle non-PnP Mode
11376 CONFIG_MSNDPIN_NONPNP
11377 The Pinnacle and Fiji card resources can be configured either with
11378 PnP, or through a configuration port. Say Y here if your card is NOT
11379 in PnP mode. For the Pinnacle, configuration in non-PnP mode allows
11380 use of the IDE and joystick peripherals on the card as well; these
11381 do not show up when the card is in PnP mode. Specifying zero for any
11382 resource of a device will disable the device. If you are running the
11383 card in PnP mode, you must say N here and use isapnptools to
11384 configure the card's resources.
11386 MSND Pinnacle config port
11388 This is the port which the Pinnacle and Fiji uses to configure the
11389 card's resources when not in PnP mode. If your card is in PnP mode,
11390 then be sure to say N to the previous option, "MSND Pinnacle Non-PnP
11393 MSND buffer size (kB)
11394 CONFIG_MSND_FIFOSIZE
11395 Configures the size of each audio buffer, in kilobytes, for
11396 recording and playing in the MultiSound drivers (both the Classic
11397 and Pinnacle). Larger values reduce the chance of data overruns at
11398 the expense of overall latency. If unsure, use the default.
11400 /dev/dsp and /dev/audio support
11402 If you say Y here, you will get the /dev/dsp and /dev/audio devices;
11403 these are the analog-digital and digital-analog converter devices
11404 and are very useful, so say Y.
11406 MIDI interface support
11408 Answering N disables /dev/midixx devices and access to any MIDI
11409 ports using /dev/sequencer and /dev/music. This option also affects
11410 any MPU401 and/or General MIDI compatible devices. Answer Y.
11412 FM synthesizer (YM3812/OPL-3) support
11413 CONFIG_SOUND_YM3812
11414 Answer Y if your card has a FM chip made by Yamaha (OPL2/OPL3/OPL4).
11415 Answering Y is usually a safe and recommended choice, however some
11416 cards may have software (TSR) FM emulation. Enabling FM support with
11417 these cards may cause trouble (I don't currently know of any such
11419 Please read the file Documentation/sound/OPL3 if your card has an
11426 This is support for the sound cards on Sun workstations. The code
11427 does not exist yet, so you might as well say N here.
11429 Additional low level drivers
11430 CONFIG_LOWLEVEL_SOUND
11431 If you need additional low level sound drivers which have not yet
11432 appeared, say Y. The answer to this question does not directly
11433 affect the kernel; saying Y will simply cause this configure script
11434 to present you with more options. If unsure, say Y.
11436 ACI mixer (miroPCM12/PCM20)
11438 ACI (Audio Command Interface) is a protocol used to communicate with
11439 the microcontroller on some sound cards produced by miro, e.g. the
11440 miroSOUND PCM12 and PCM20. The main function of the ACI is to
11441 control the mixer and to get a product identification.
11443 This Voxware ACI driver currently only supports the ACI functions on
11444 the miroSOUND PCM12 and PCM20 cards. On the PCM20, ACI also controls
11445 the radio tuner. This is supported in the video4linux
11446 radio-miropcm20 driver.
11450 Say Y here if you have a Sound Blaster SB32, AWE32-PnP, SB AWE64 or
11451 similar sound card. See Documentation/sound/README.awe,
11452 Documentation/sound/AWE32 and the Soundblaster-AWE mini-HOWTO,
11453 available from http://www.linuxdoc.org/docs.html#howto for more
11456 Gallant's Audio Excel DSP 16 support (SC-6000 and SC-6600)
11458 Answer Y if you have a Gallant's Audio Excel DSP 16 card. This
11459 driver supports Audio Excel DSP 16 but not the III nor PnP versions
11462 The Gallant's Audio Excel DSP 16 card can emulate either an SBPro or
11463 a Microsoft Sound System card, so you should have said Y to either
11464 "100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support"
11465 or "Microsoft Sound System support", above, and you need to answer
11466 the "MSS emulation" and "SBPro emulation" questions below
11467 accordingly. You should say Y to one and only one of these two
11470 Read the drivers/sound/lowlevel/README.aedsp16 file and the head of
11471 drivers/sound/lowlevel/aedsp16.c as well as
11472 Documentation/sound/AudioExcelDSP16 to get more information about
11473 this driver and its configuration.
11475 I/O base for Audio Excel DSP 16
11476 CONFIG_AEDSP16_BASE
11477 This is the base I/O address of the Audio Excel DSP 16 card. It must
11478 be 220 or 240. If you compiled aedsp16.o as a module you can specify
11479 this parameter as 'io=0xNNN'.
11481 Audio Excel DSP 16 (SBPro emulation)
11482 CONFIG_AEDSP16_SBPRO
11483 Answer Y if you want your audio card to emulate Sound Blaster Pro.
11484 You should then say Y to "100% Sound Blaster compatibles
11485 (SB16/32/64, ESS, Jazz16) support" and N to "Audio Excel DSP 16 (MSS
11488 Audio Excel DSP 16 IRQ
11489 CONFIG_AEDSP16_SB_IRQ
11490 This is the IRQ of the Audio Excel DSP 16 card. It must be 5, 7, 9,
11491 10 or 11. If you compiled aedsp16.o as a module you can specify
11492 this parameter as 'irq=NN'.
11494 Audio Excel DSP 16 DMA
11495 CONFIG_AEDSP16_SB_DMA
11496 This is the IRQ of the Audio Excel DSP 16 card. It must be 0, 1 or
11497 3. If you compiled aedsp16.o as a module you can specify this
11498 parameter as 'dma=NN'.
11500 Audio Excel DSP 16 (MSS emulation)
11502 Answer Y if you want your audio card to emulate Microsoft Sound
11503 System. You should then say Y to "Microsoft Sound System support"
11504 and say N to "Audio Excel DSP 16 (SBPro emulation)".
11506 Audio Excel DSP 16 IRQ
11507 CONFIG_AEDSP16_MSS_IRQ
11508 This is the IRQ of the Audio Excel DSP 16 card. It must be 5, 7, 9,
11509 10 or 11. If you compiled aedsp16.o as a module you can specify
11510 this parameter as 'irq=NN'.
11512 Audio Excel DSP 16 DMA
11513 CONFIG_AEDSP16_MSS_DMA
11514 This is the IRQ of the Audio Excel DSP 16 card. It must be 0, 1
11515 or 3. If you compiled aedsp16.o as a module you can specify this
11516 parameter as 'dma=NN'.
11518 SC-6600 based audio cards (new Audio Excel DSP 16)
11520 The SC6600 is the new version of DSP mounted on the Audio Excel DSP
11521 16 cards. Find in the manual the FCC ID of your audio card and
11522 answer Y if you have an SC6600 DSP.
11524 SC-6600 Joystick Interface
11526 Say Y here in order to use the joystick interface of the Audio Excel
11529 SC-6600 CDROM Interface
11530 CONFIG_SC6600_CDROM
11531 This is used to activate the the CDROM interface of the Audio Excel
11532 DSP 16 card. Enter: 0 for Sony, 1 for Panasonic, 2 for IDE, 4 for no
11535 Audio Excel DSP 16 (MPU401 emulation)
11536 CONFIG_AEDSP16_MPU401
11537 Answer Y if you want your audio card to emulate the MPU-401 midi
11538 interface. You should then also say Y to "MPU-401 support".
11540 Note that the I/O base for MPU-401 support of aedsp16 is the same
11541 you have selected for "MPU-401 support". If you are using this
11542 driver as a module you have to specify the MPU I/O base address with
11543 the parameter 'mpu_base=0xNNN'.
11545 MPU401 IRQ for Audio Excel DSP 16
11546 CONFIG_AEDSP16_MPU_IRQ
11547 This is the IRQ of the MPU-401 emulation of your Audio Excel DSP 16
11548 card. It must be 5, 7, 9, 10 or 0 (to disable MPU-401 interface). If
11549 you compiled aedsp16.o as a module you can specify this parameter as
11552 Ensoniq ES1370 based PCI sound cards
11553 CONFIG_SOUND_ES1370
11554 Say Y or M if you have a PCI sound card utilizing the Ensoniq
11555 ES1370 chipset, such as Ensoniq's AudioPCI (non-97). To find
11556 out if your sound card uses an ES1370 without removing your
11557 computer's cover, use lspci -n and look for the PCI ID
11558 1274:5000. Since Ensoniq was bought by Creative Labs,
11559 Sound Blaster 64/PCI models are either ES1370 or ES1371 based.
11560 This driver differs slightly from OSS/Free, so PLEASE READ
11561 Documentation/sound/es1370.
11563 Ensoniq ES1371 based PCI sound cards
11564 CONFIG_SOUND_ES1371
11565 Say Y or M if you have a PCI sound card utilizing the Ensoniq
11566 ES1371 chipset, such as Ensoniq's AudioPCI97. To find out if
11567 your sound card uses an ES1371 without removing your computer's
11568 cover, use lspci -n and look for the PCI ID 1274:1371. Since
11569 Ensoniq was bought by Creative Labs, Sound Blaster 64/PCI
11570 models are either ES1370 or ES1371 based. This driver differs
11571 slightly from OSS/Free, so PLEASE READ Documentation/sound/es1371.
11573 ESS Solo1 based PCI sound cards (eg. SC1938)
11574 CONFIG_SOUND_ESSSOLO1
11575 Say Y or M if you have a PCI sound card utilizing the ESS Technology
11576 Solo1 chip. To find out if your sound card uses a
11577 Solo1 chip without removing your computer's cover, use
11578 lspci -n and look for the PCI ID 125D:1969. This driver
11579 differs slightly from OSS/Free, so PLEASE READ
11580 Documentation/sound/solo1.
11582 S3 SonicVibes based PCI sound cards
11583 CONFIG_SOUND_SONICVIBES
11584 Say Y or M if you have a PCI sound card utilizing the S3
11585 SonicVibes chipset. To find out if your sound card uses a
11586 SonicVibes chip without removing your computer's cover, use
11587 lspci -n and look for the PCI ID 5333:CA00. This driver
11588 differs slightly from OSS/Free, so PLEASE READ
11589 Documentation/sound/sonicvibes.
11591 Trident 4DWave DX/NX or SiS 7018 PCI Audio Core
11592 CONFIG_SOUND_TRIDENT
11593 Say Y or M if you have a PCI sound card utilizing the Trident
11594 4DWave-DX/NX chipset or your mother board chipset has SiS 7018
11595 built-in. The SiS 7018 PCI Audio Core is embedded in SiS960
11596 Super South Bridge and SiS540/630 Single Chipset.
11598 Use lspci -n to find out if your sound card or chipset uses
11599 Trident 4DWave or SiS 7018. PCI ID 1023:2000 or 1023:2001 stands
11600 for Trident 4Dwave. PCI ID 1039:7018 stands for SiS7018.
11602 This driver differs slightly from OSS/Free, so PLEASE READ the
11603 comments at of driver/sound/trident.c
11605 Rockwell WaveArtist
11606 CONFIG_SOUND_WAVEARTIST
11607 Say Y here to include support for the Rockwell WaveArtist sound
11608 system. This driver is mainly for the NetWinder.
11610 VIA 82Cxxx Audio Codec
11611 CONFIG_SOUND_VIA82CXXX
11612 Say Y here to include support for the audio codec found on
11613 VIA 82Cxxx-based chips. Typically these are built into a motherboard.
11614 DO NOT select SoundBlaster or Adlib with this driver, unless you have
11615 a SoundBlaster or Adlib card in addition to your VIA audio chip.
11617 NeoMagic 256AV/256ZX sound chipsets
11619 Say M here to include audio support for the NeoMagic 256AV/256ZX
11620 chipsets. These are the audio chipsets found in the Sony Z505S/SX/DX,
11621 some Sony F-series, and the Dell Latitude CPi and CPt laptops. It includes
11622 support for an AC97-compatible mixer and an apparently proprietary sound
11625 See Documentation/sound/NM256 for further information.
11627 ESS Maestro sound chipsets
11628 CONFIG_SOUND_MAESTRO
11629 Say Y or M if you have a sound system driven by ESS's Maestro line
11630 of PCI sound chips. These include the Maestro 1, Maestro 2, and
11631 Maestro 2E. See Documentation/sound/Maestro for more details.
11633 Are you using a crosscompiler
11634 CONFIG_CROSSCOMPILE
11635 Say Y here if you are compiling the kernel on a different
11636 architecture than the one it is intended to run on.
11638 Build fp exception handler module
11639 CONFIG_MIPS_FPE_MODULE
11640 Build the floating point exception handler module. This option is
11641 only useful for people working on the floating point exception
11642 handler. If you don't, say N.
11644 Remote GDB kernel debugging
11645 CONFIG_REMOTE_DEBUG
11646 If you say Y here, it will be possible to remotely debug the MIPS
11647 kernel using gdb. This enlarges your kernel image disk size by
11648 several megabytes and requires a machine with more than 16 MB,
11649 better 32 MB RAM to avoid excessive linking time. This is only
11650 useful for kernel hackers. If unsure, say N.
11652 Magic System Request Key support
11654 If you say Y here, you will have some control over the system even
11655 if the system crashes for example during kernel debugging (e.g., you
11656 will be able to flush the buffer cache to disk, reboot the system
11657 immediately or dump some status information). This is accomplished
11658 by pressing various keys while holding SysRq (Alt+PrintScreen). The
11659 keys are documented in Documentation/sysrq.txt. Don't say Y unless
11660 you really know what this hack does.
11664 ISDN ("Integrated Services Digital Networks", called RNIS in France)
11665 is a special type of fully digital telephone service; it's mostly
11666 used to connect to your Internet service provider (with SLIP or
11667 PPP). The main advantage is that the speed is higher than ordinary
11668 modem/telephone connections, and that you can have voice
11669 conversations while downloading stuff. It only works if your
11670 computer is equipped with an ISDN card and both you and your service
11671 provider purchased an ISDN line from the phone company. For details,
11672 read http://alumni.caltech.edu/~dank/isdn/ on the WWW.
11674 This driver allows you to use an ISDN-card for networking
11675 connections and as dialin/out device. The isdn-tty's have a built in
11676 AT-compatible modem emulator. Network devices support autodial,
11677 channel-bundling, callback and caller-authentication without having
11678 a daemon running. A reduced T.70 protocol is supported with tty's
11679 suitable for German BTX. On D-Channel, the protocols EDSS1
11680 (Euro-ISDN) and 1TR6 (German style) are supported. See
11681 Documentation/isdn/README for more information.
11683 If you want to compile the ISDN code as a module ( = code which can
11684 be inserted in and removed from the running kernel whenever you
11685 want), say M here and read Documentation/modules.txt. The module
11686 will be called isdn.o. If unsure, say N.
11688 Support synchronous PPP
11690 Over digital connections such as ISDN, there is no need to
11691 synchronize sender and recipient's clocks with start and stop bits
11692 as is done over analog telephone lines. Instead, one can use
11693 "synchronous PPP". Saying Y here will include this protocol. This
11694 protocol is used by Cisco and Sun for example. So you want to say Y
11695 here if the other end of your ISDN connection supports it. You will
11696 need a special version of pppd (called ipppd) for using this
11697 feature. See Documentation/isdn/README.syncppp and
11698 Documentation/isdn/syncPPP.FAQ for more information.
11700 Support generic MP (RFC 1717)
11702 With synchronous PPP enabled, it is possible to increase throughput
11703 by bundling several ISDN-connections, using this protocol. See
11704 Documentation/isdn/README.syncppp for more information.
11706 Use VJ-compression with synchronous PPP
11708 This enables Van Jacobson header compression for synchronous PPP.
11709 Say Y if the other end of the connection supports it.
11711 Support audio via ISDN
11713 If you say Y here, the modem-emulator will support a subset of the
11714 EIA Class 8 Voice commands. Using a getty with voice-support
11715 (mgetty+sendfax by gert@greenie.muc.de with an extension, available
11716 with the ISDN utility package for example), you will be able to use
11717 your Linux box as an ISDN-answering machine. Of course, this must be
11718 supported by the lowlevel driver also. Currently, the HiSax driver
11719 is the only voice-supporting driver. See
11720 Documentation/isdn/README.audio for more information.
11722 X.25 PLP on top of ISDN
11724 This feature provides the X.25 protocol over ISDN connections.
11725 See Documentation/isdn/README.x25 for more information
11726 if you are thinking about using this.
11728 ISDN diversion services support
11729 CONFIG_ISDN_DIVERSION
11730 This option allows you to use some supplementary diversion
11731 services in conjunction with the HiSax driver on an EURO/DSS1
11734 Supported options are CD (call deflection), CFU (Call forward
11735 unconditional), CFB (Call forward when busy) and CFNR (call forward
11736 not reachable). Additionally the actual CFU, CFB and CFNR state may
11739 The use of CFU, CFB, CFNR and interrogation may be limited to some
11740 countries. The keypad protocol is still not implemented. CD should
11741 work in all countries if the service has been subscribed to.
11743 Please read the file Documentation/isdn/README.diversion.
11745 ICN 2B and 4B support
11746 CONFIG_ISDN_DRV_ICN
11747 This enables support for two kinds of ISDN-cards made by a German
11748 company called ICN. 2B is the standard version for a single ISDN
11749 line with two B-channels, 4B supports two ISDN lines. For running
11750 this card, additional firmware is necessary, which has to be
11751 downloaded into the card using a utility which is distributed
11752 separately. See Documentation/isdn/README and README.icn for more
11755 If you want to compile this as a module ( = code which can be
11756 inserted in and removed from the running kernel whenever you want),
11757 say M here and read Documentation/modules.txt. The module will be
11761 CONFIG_ISDN_DRV_LOOP
11762 This driver provides a virtual ISDN card. Its primary purpose is
11763 testing of linklevel features or configuration without getting
11764 charged by your service-provider for lots of phone calls.
11765 You need will need the loopctrl utility from the latest isdn4k-utils
11766 package to set up this driver.
11768 HiSax SiemensChipSet driver support
11769 CONFIG_ISDN_DRV_HISAX
11770 This is a driver supporting the Siemens chipset on various
11771 ISDN-cards (like AVM A1, Elsa ISDN cards, Teles S0-16.0, Teles
11772 S0-16.3, Teles S0-8, Teles/Creatix PnP, ITK micro ix1 and many
11775 HiSax is just the name of this driver, not the name of any hardware.
11777 If you have a card with such a chipset, you should say Y here and
11778 also to the configuration option of the driver for your particular
11781 If you want to compile this as a module ( = code which can be
11782 inserted in and removed from the running kernel whenever you want),
11783 say M here and read Documentation/modules.txt. The module will be
11784 called hisax.o. See Documentation/isdn/README.HiSax for more
11785 information on using this driver.
11787 HiSax Support for EURO/DSS1
11789 Enable this if you have a EURO ISDN line.
11791 Support for german chargeinfo
11793 If you have german AOC, you can enable this to get the charginfo.
11795 Disable sending complete
11796 CONFIG_HISAX_NO_SENDCOMPLETE
11797 If you have trouble with some ugly exchanges or you live in
11798 Australia select this option.
11800 Disable sending low layer compatibility
11801 CONFIG_HISAX_NO_LLC
11802 If you have trouble with some ugly exchanges try to select this
11805 Disable keypad protocol option
11806 CONFIG_HISAX_NO_KEYPAD
11807 If you like to send special dialstrings including * or # without
11808 using the keypad protocol, select this option.
11810 HiSax Support for german 1TR6
11812 Enable this if you have a old german 1TR6 line.
11816 This enables HiSax support for the Teles ISDN-cards S0-16.0, S0-8
11817 and many compatibles.
11819 See Documentation/isdn/README.HiSax on how to configure it using the
11820 different cards, a different D-channel protocol, or non-standard
11821 IRQ/port/shmem settings.
11823 Teles 16.3 or PNP or PCMCIA
11825 This enables HiSax support for the Teles ISDN-cards S0-16.3 the
11826 Teles/Creatix PnP and the Teles PCMCIA.
11828 See Documentation/isdn/README.HiSax on how to configure it using the
11829 different cards, a different D-channel protocol, or non-standard
11833 CONFIG_HISAX_TELESPCI
11834 This enables HiSax support for the Teles PCI.
11835 See Documentation/isdn/README.HiSax on how to configure it.
11839 This enables HiSax support for the Teles/Creatix parallel port
11840 S0BOX. See Documentation/isdn/README.HiSax on how to configure it.
11843 CONFIG_HISAX_AVM_A1
11844 This enables HiSax support for the AVM A1 (aka "Fritz").
11846 See Documentation/isdn/README.HiSax on how to configure it using the
11847 different cards, a different D-channel protocol, or non-standard
11850 AVM PnP/PCI (Fritz!PNP/PCI)
11851 CONFIG_HISAX_FRITZPCI
11852 This enables HiSax support for the AVM "Fritz!PnP" and "Fritz!PCI".
11853 See Documentation/isdn/README.HiSax on how to configure it.
11855 AVM A1 PCMCIA (Fritz)
11856 CONFIG_HISAX_AVM_A1_PCMCIA
11857 This enables HiSax support for the AVM A1 "Fritz!PCMCIA").
11858 See Documentation/isdn/README.HiSax on how to configure it.
11862 This enables HiSax support for the Elsa Mircolink ISA cards, for the
11863 Elsa Quickstep series cards and Elsa PCMCIA.
11865 See Documentation/isdn/README.HiSax on how to configure it using the
11866 different cards, a different D-channel protocol, or non-standard
11869 ITK ix1-micro Revision 2
11870 CONFIG_HISAX_IX1MICROR2
11871 This enables HiSax support for the ITK ix1-micro Revision 2 card.
11873 See Documentation/isdn/README.HiSax on how to configure it using the
11874 different cards, a different D-channel protocol, or non-standard
11877 Eicon.Diehl Diva cards
11878 CONFIG_HISAX_DIEHLDIVA
11879 This enables HiSax support for the Eicon.Diehl Diva none PRO
11880 versions passive ISDN cards.
11882 See Documentation/isdn/README.HiSax on how to configure it using the
11883 different cards, a different D-channel protocol, or non-standard
11887 CONFIG_HISAX_ASUSCOM
11888 This enables HiSax support for the AsusCom and their OEM versions
11889 passive ISDN ISA cards.
11891 See Documentation/isdn/README.HiSax on how to configure it using the
11892 different cards, a different D-channel protocol, or non-standard
11896 CONFIG_HISAX_TELEINT
11897 This enables HiSax support for the TELEINT SA1 semiactiv ISDN card.
11899 See Documentation/isdn/README.HiSax on how to configure it using the
11900 different cards, a different D-channel protocol, or non-standard
11905 This enables HiSax support for the HFC-S 2BDS0 based cards, like
11908 See Documentation/isdn/README.HiSax on how to configure it using the
11909 different cards, a different D-channel protocol, or non-standard
11913 CONFIG_HISAX_SEDLBAUER
11914 This enables HiSax support for the Sedlbauer passive ISDN cards.
11916 See Documentation/isdn/README.HiSax on how to configure it using the
11917 different cards, a different D-channel protocol, or non-standard
11920 USR Sportster internal TA
11921 CONFIG_HISAX_SPORTSTER
11922 This enables HiSax support for the USR Sportster internal TA card.
11924 See Documentation/isdn/README.HiSax on how to configure it using a
11925 different D-channel protocol, or non-standard IRQ/port settings.
11929 This enables HiSax support for the ITH MIC card.
11931 See Documentation/isdn/README.HiSax on how to configure it using a
11932 different D-channel protocol, or non-standard IRQ/port settings.
11935 CONFIG_HISAX_NETJET
11936 This enables HiSax support for the NetJet from Traverse
11939 See Documentation/isdn/README.HiSax on how to configure it using a
11940 different D-channel protocol, or non-standard IRQ/port settings.
11944 This enables HiSax support for the Dr. Neuhaus Niccy PnP or PCI.
11946 See Documentation/isdn/README.HiSax on how to configure it using a
11947 different D-channel protocol, or non-standard IRQ/port settings.
11949 Siemens I-Surf card
11951 This enables HiSax support for the Siemens I-Talk/I-Surf card with
11953 See Documentation/isdn/README.HiSax on how to configure it using a
11954 different D-channel protocol, or non-standard IRQ/port settings.
11957 CONFIG_HISAX_HSTSAPHIR
11958 This enables HiSax support for the HST Saphir card.
11960 See Documentation/isdn/README.HiSax on how to configure it using a
11961 different D-channel protocol, or non-standard IRQ/port settings.
11964 CONFIG_HISAX_BKM_A4T
11965 This enables HiSax support for the Telekom A4T card.
11967 See Documentation/isdn/README.HiSax on how to configure it using a
11968 different D-channel protocol, or non-standard IRQ/port settings.
11971 CONFIG_HISAX_SCT_QUADRO
11972 This enables HiSax support for the Scitel Quadro card.
11974 See Documentation/isdn/README.HiSax on how to configure it using a
11975 different D-channel protocol, or non-standard IRQ/port settings.
11979 This enables HiSax support for the Gazel cards.
11981 See Documentation/isdn/README.HiSax on how to configure it using a
11982 different D-channel protocol, or non-standard IRQ/port settings.
11985 CONFIG_HISAX_HFC_PCI
11986 This enables HiSax support for the HFC-S PCI 2BDS0 based cards.
11988 For more informations see under Documentation/isdn/README.hfc-pci.
11990 Winbond W6692 based cards
11992 This enables HiSax support for Winbond W6692 based PCI ISDN cards.
11994 See Documentation/isdn/README.HiSax on how to configure it using a
11995 different D-channel protocol, or non-standard IRQ/port settings.
11997 HFC-S+, HFC-SP, HFC-PCMCIA cards (EXPERIMENTAL)
11998 CONFIG_HISAX_HFC_SX
11999 This enables HiSax support for the HFC-S+, HFC-SP and HFC-PCMCIA cards.
12000 This code is not finished yet.
12002 Am7930 (EXPERIMENTAL)
12003 CONFIG_HISAX_AMD7930
12004 This enables HiSax support for the AMD7930 chips on some SPARCs.
12005 This code is not finished yet.
12008 CONFIG_ISDN_DRV_PCBIT
12009 This enables support for the PCBIT ISDN-card. This card is
12010 manufactured in Portugal by Octal. For running this card, additional
12011 firmware is necessary, which has to be downloaded into the card
12012 using a utility which is distributed separately. See
12013 Documentation/isdn/README and Documentation/isdn/README.pcbit for
12016 If you want to compile this as a module ( = code which can be
12017 inserted in and removed from the running kernel whenever you want),
12018 say M here and read Documentation/modules.txt. The module will be
12021 Spellcaster support (EXPERIMENTAL)
12023 This enables support for the Spellcaster BRI ISDN boards. This
12024 driver currently builds only in a modularized version ( = code which
12025 can be inserted in and removed from the running kernel whenever you
12026 want, details in Documentation/modules.txt); the module will be
12027 called sc.o. See Documentation/isdn/README.sc and
12028 http://www.spellcast.com for more information.
12030 Eicon.Diehl active card support
12031 CONFIG_ISDN_DRV_EICON
12032 Say Y here if you have an Eicon active ISDN card. In order to use
12033 this card, additional firmware is necessary, which has to be loaded
12034 into the card using the eiconctrl utility which is part of the
12035 latest isdn4k-utils package. Please read the file
12036 Documentation/isdn/README.eicon for more information.
12038 Eicon old-type card support
12039 CONFIG_ISDN_DRV_EICON_ISA
12040 Say Y here if you have an old-type Eicon active ISDN card. In order
12041 to use this card, additional firmware is necessary, which has to be
12042 loaded into the card using the eiconctrl utility which is part of
12043 the latest isdn4k-utils package. Please read the file
12044 Documentation/isdn/README.eicon for more information.
12046 Support AT-Fax Class 2 commands
12047 CONFIG_ISDN_TTY_FAX
12048 If you say Y here, the modem-emulator will support a subset of the
12049 Fax Class 2 commands. Using a getty with fax-support
12050 (mgetty+sendfax, hylafax), you will be able to use your Linux box as
12051 an ISDN-fax-machine. This must be supported by the lowlevel driver
12052 also. See Documentation/isdn/README.fax for more information.
12054 AVM CAPI2.0 support
12055 CONFIG_ISDN_DRV_AVMB1
12056 This enables support for the AVM B1/T1 ISDN networking cards.In
12057 addition, a CAPI (Common ISDN Application Programming Interface, a
12058 standard making it easy for programs to access ISDN hardware, see
12059 http://www.capi.org/; to browse the WWW, you need to have access to
12060 a machine on the Internet that has a program like lynx or netscape)
12061 interface for this card is provided. In order to use this card,
12062 additional firmware is necessary, which has to be downloaded into
12063 the card using a utility which is distributed separately. Please
12064 read the file Documentation/isdn/README.avmb1.
12066 This code is also available as a module ( = code which can be
12067 inserted in and removed from the running kernel whenever you want).
12068 The module will be called avmb1.o. If you want to compile it as a
12069 module, say M here and read Documentation/modules.txt.
12072 CONFIG_ISDN_DRV_AVMB1_B1ISA
12073 Enable support for the ISA version of the AVM B1 card.
12076 CONFIG_ISDN_DRV_AVMB1_B1PCI
12077 Enable support for the PCI version of the AVM B1 card.
12079 AVM T1/T1-B ISA support
12080 CONFIG_ISDN_DRV_AVMB1_T1ISA
12081 Enable support for the AVM T1 T1B card.
12082 Note: This is a PRI card and handle 30 B-channels.
12084 AVM B1/M1/M2 PCMCIA support
12085 CONFIG_ISDN_DRV_AVMB1_B1PCMCIA
12086 Enable support for the PCMCIA version of the AVM B1 card.
12088 AVM T1/T1-B PCI support
12089 CONFIG_ISDN_DRV_AVMB1_T1PCI
12090 Enable support for the AVM T1 T1B card.
12091 Note: This is a PRI card and handle 30 B-channels.
12093 Verbose reason code reporting (kernel size +=7K)
12094 CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON
12095 If you say Y here, the AVM B1 driver will give verbose reasons for
12096 disconnecting. This will increase the size of the kernel by 7 KB. If
12100 IBM Active 2000 support (EXPERIMENTAL)
12101 CONFIG_ISDN_DRV_ACT2000
12102 Say Y here if you have an IBM Active 2000 ISDN card. In order to use
12103 this card, additional firmware is necessary, which has to be loaded
12104 into the card using a utility which is part of the latest
12105 isdn4k-utils package. Please read the file
12106 Documentation/isdn/README.act2000 for more information.
12108 Support for AP1000 multicomputer
12110 This enables support for a SPARC based parallel multi-computer
12111 called AP1000+. For details on our efforts to port Linux to this
12112 machine see http://cap.anu.edu.au/cap/projects/linux or mail to
12113 hackers@cafe.anu.edu.au
12115 Support for Sun4 architecture
12117 Say Y here if, and only if, your machine is a Sun4. Note that
12118 a kernel compiled with this option will run only on Sun4.
12119 (And the current version will probably work only on sun4/330.)
12121 SPARC ESP SCSI support
12123 This is the driver for the Sun ESP SCSI host adapter. The ESP
12124 chipset is present in most SPARC-based computers.
12126 SPARC /dev/openprom compatibility driver (EXPERIMENTAL)
12127 CONFIG_SUN_OPENPROMIO
12128 This driver provides user programs with an interface to the SPARC
12129 PROM device tree. The driver implements a SunOS-compatible
12130 interface and a NetBSD-compatible interface.
12132 If you want to compile this as a module ( = code which can be
12133 inserted in and removed from the running kernel whenever you want),
12134 say M and read Documentation/modules.txt. If unsure, say Y.
12136 Mostek real time clock support
12137 CONFIG_SUN_MOSTEK_RTC
12138 The Mostek RTC chip is used on all knows Sun computers except
12139 some JavaStations. For a JavaStation you need to say Y both here
12140 and to "Enhanced Real Time Clock Support".
12142 Say Y here unless you are building a special purpose kernel.
12144 JavaStation OS Flash SIMM (EXPERIMENTAL)
12146 This option enables a driver for JavaStation OS Flash driver.
12147 Say N unless you want to boot from your Flash SIMM.
12149 #Siemens SAB82532 serial support
12152 ### Please someone fill these in.
12155 IEEE 1394 (aka FireWire) support
12157 IEEE 1394 describes a high performance serial bus, which is also
12158 known as FireWire(tm) or i.Link(tm) and is used for connecting all
12159 sorts of devices (most notably digital video cameras).
12161 If you have FireWire hardware and want to use it, say Y here. This
12162 is the core support only, you will also need to select a driver for
12163 your IEEE 1394 adapter.
12165 If you want to compile this as a module ( = code which can be
12166 inserted in and removed from the running kernel whenever you want),
12167 say M here and read Documentation/modules.txt. The module will be
12170 FireWire is a trademark by Apple Inc. and i.Link is a trademark by
12173 TI PCILynx IEEE 1394 support
12174 CONFIG_IEEE1394_PCILYNX
12175 Say Y here if you have a IEEE-1394 controller with the Texas
12176 Instruments PCILynx chip. Note: this driver is written for revision
12177 2 of this chip and may not work with revision 0.
12179 If you want to compile this as a module ( = code which can be
12180 inserted in and removed from the running kernel whenever you want),
12181 say M here and read Documentation/modules.txt. The module will be
12184 Use local RAM on PCILynx board
12185 CONFIG_IEEE1394_PCILYNX_LOCALRAM
12186 This option makes the PCILynx driver use local RAM available on some
12187 PCILynx setups for Packet Control Lists. Local RAM may speed up
12188 command processing because no PCI transfers are necessary during
12189 use of the Packet Control Lists.
12191 Note that there are no known PCILynx systems providing local RAM
12192 except for the evaluation boards by Texas Instruments and that the
12193 PCILynx does not reliably report missing RAM.
12195 Unless you are absolutely sure that you have 64kB of local RAM and
12196 that you want to use it or if you don't know what this is all about,
12199 Adaptec AIC-5800 IEEE 1394 support
12200 CONFIG_IEEE1394_AIC5800
12201 Say Y here if you have a IEEE 1394 controller using the Adaptec
12202 AIC-5800 chip. All Adaptec host adapters (89xx series) use this
12203 chip, as well as miro's DV boards.
12205 If you want to compile this as a module ( = code which can be
12206 inserted in and removed from the running kernel whenever you want),
12207 say M here and read Documentation/modules.txt. The module will be
12210 OHCI (Open Host Controller Interface) support
12211 CONFIG_IEEE1394_OHCI1394
12212 Say Y here if you have a IEEE 1394 controller based on OHCI.
12213 The current driver was only tested with OHCI chipsets made
12214 by Texas Instruments. However, most third-party vendors use
12217 If you want to compile this as a module ( = code which can be
12218 inserted in and removed from the running kernel whenever you want),
12219 say M here and read Documentation/modules.txt. The module will be
12222 RAW IEEE 1394 I/O support
12223 CONFIG_IEEE1394_RAWIO
12224 Say Y here if you want support for the raw device. This is generally
12225 a good idea, so you should say Y here. The raw device enables
12226 direct communication of user programs to the IEEE 1394 bus.
12228 If you want to compile this as a module ( = code which can be
12229 inserted in and removed from the running kernel whenever you want),
12230 say M here and read Documentation/modules.txt. The module will be
12234 # m68k-specific kernel options
12235 # Documented by Chris Lawrence <quango@themall.net> et al.
12239 This option enables support for the Amiga series of computers. If
12240 you plan to use this kernel on an Amiga, say Y here and browse the
12241 material available in Documentation/m68k; otherwise say N.
12245 This option enables support for the 68000-based Atari series of
12246 computers (including the TT, Falcon and Medusa). If you plan to use
12247 this kernel on an Atari, say Y here and browse the material
12248 available in Documentation/m68k; otherwise say N.
12252 This option enables support for the Hades Atari clone. If you plan
12253 to use this kernel on a Hades, say Y here; otherwise say N.
12257 This option enables support for the Apple Macintosh series of
12258 computers (yes, there is experimental support now, at least for part
12261 Say N unless you're willing to code the remaining necessary support.
12266 This option enables support for the HP9000/300 series of
12267 workstations. Support for these machines is still very experimental.
12268 If you plan to try to use the kernel on such a machine say Y here.
12269 Everybody else says N.
12273 This option enables support for the Sun 3 series of workstations. Be
12274 warned that this support is very experimental. You will also want to
12275 say Y to 68020 support and N to the other processors below.
12276 Currently, it is not possible to build a kernel with support for the
12277 Sun 3 and something else, so make sure you have said N to all the
12278 other machines. This option does not support the sun3x series of
12279 machines (the Sun 3/80 and 3/460). If you don't want to compile a
12280 kernel for a Sun 3, say N.
12284 If you anticipate running this kernel on a computer with a MC68020
12285 processor, say Y. Otherwise, say N. Note that the 68020 requires a
12286 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
12287 Sun 3, which provides its own version.
12291 If you anticipate running this kernel on a computer with a MC68030
12292 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
12293 work, as it does not include an MMU (Memory Management Unit).
12297 If you anticipate running this kernel on a computer with a MC68LC040
12298 or MC68040 processor, say Y. Otherwise, say N. Note that an
12299 MC68EC040 will not work, as it does not include an MMU (Memory
12304 If you anticipate running this kernel on a computer with a MC68060
12305 processor, say Y. Otherwise, say N.
12307 Math emulation support (EXPERIMENTAL)
12309 At some point in the future, this will cause floating-point math
12310 instructions to be emulated by the kernel on machines that lack a
12311 floating-point math coprocessor. Thrill-seekers and chronically
12312 sleep-deprived psychotic hacker types can say Y now, everyone else
12313 should probably wait a while.
12315 Math emulation only kernel
12316 CONFIG_M68KFPU_EMU_ONLY
12317 This option prevents any floating-point instructions from being
12318 compiled into the kernel, thereby the kernel doesn't save any
12319 floating point context anymore during task switches, so this
12320 kernel will only be usable on machines without a floating-point
12321 math coprocessor. This makes the kernel a bit faster as no tests
12322 needs to be executed whether a floating-point instruction in the
12323 kernel should be executed or not.
12325 Math emulation extra precision
12326 CONFIG_M68KFPU_EMU_EXTRAPREC
12327 The fpu uses normally a few bit more during calculations for
12328 correct rounding, the emulator can (often) do the same but this
12329 extra calculation can cost quite some time, so you can disable
12330 it here. The emulator will then "only" calculate with a 64 bit
12331 mantissa and round slightly incorrect, what is more then enough
12334 Advanced processor options
12335 CONFIG_ADVANCED_CPU
12336 This gives you access to some advanced options for the CPU. The
12337 defaults should be fine for most users, but these options may make
12338 it possible for you to improve performance somewhat if you know what
12339 you are doing. Most users should say N to this question.
12341 Use read-modify-write instructions
12343 This allows to use certain instructions that work with indivisible
12344 read-modify-write bus cycles. While this is faster than the
12345 workaround of disabling interrupts, it can conflict with DMA
12346 ( = direct memory access) on many Amiga systems, and it is also said
12347 to destabilize other machines. It is very likely that this will
12348 cause serious problems on any Amiga or Atari Medusa if set. The only
12349 configuration where it should work are 68030-based Ataris, where it
12350 apparently improves performance. But you've been warned! Unless you
12351 really know what you are doing, say N. Try Y only if you're quite
12354 Amiga AutoConfig Identification
12356 This enables support for automatic identification of Amiga expansion
12357 cards that obey the AutoConfig(tm) specification.
12358 Say Y if you want your expansion cards to be identified on bootup;
12359 it will enlarge your kernel by about 10 KB. The identification
12360 information is also available through /proc/zorro (say Y to
12361 "/proc filesystem support"!).
12363 Note that even if you say N here, you can still use your expansion
12364 cards. If in doubt, say Y.
12366 Amiga 1200/600 PCMCIA support (EXPERIMENTAL)
12367 CONFIG_AMIGA_PCMCIA
12368 Include support in the kernel for pcmcia on Amiga 1200 and Amiga
12369 600. If you intend to use pcmcia cards say Y; otherwise say N.
12371 Amiga GSP (TMS340x0) support
12373 Include support for Amiga graphics cards that use the Texas
12374 Instruments TMS340x0 GSP (Graphics Signal Processor) chips. Say Y
12375 if you want to use a DMI Resolver or Commodore A2410 (Lowell)
12376 graphics card on an Amiga; otherwise, say N.
12378 DMI Resolver support
12379 CONFIG_GSP_RESOLVER
12380 Include support in the kernel for the DMI Resolver graphics card. If
12381 you have one, say Y; otherwise, say N.
12385 Include support in the kernel for the Commodore/University of Lowell
12386 A2410 graphics card. If you have one, say Y; otherwise, say N.
12388 Amiga Zorro II ramdisk support
12390 This enables support for using Chip RAM and Zorro II RAM as a
12391 ramdisk or as a swap partition. Say Y if you want to include this
12392 driver in the kernel. This driver is also available as a module
12393 ( = code which can be inserted in and removed from the running
12394 kernel whenever you want). The module is called z2ram.o. If you want
12395 to compile it as a module, say M here and read
12396 Documentation/modules.txt.
12398 Atari ST-RAM swap support
12400 This enables support for using (parts of) ST-RAM as swap space,
12401 instead of as normal system memory. This can first enhance system
12402 performance if you have lots of alternate RAM (compared to the size
12403 of ST-RAM), because executable code always will reside in faster
12404 memory. ST-RAM will remain as ultra-fast swap space. On the other
12405 hand, it allows much improved dynamic allocations of ST-RAM buffers
12406 for device driver modules (e.g. floppy, ACSI, SLM printer, DMA
12407 sound). The probability that such allocations at module load time
12408 fail is drastically reduced.
12412 This enables support for the Atari ACSI interface. The driver
12413 supports hard disks and CD-ROMs, which have 512-byte sectors, or can
12414 be switched to that mode. Due to the ACSI command format, only disks
12415 up to 1 GB are supported. Special support for certain ACSI to SCSI
12416 adapters, which could relax that, isn't included yet. The ACSI
12417 driver is also the basis for certain other drivers for devices
12418 attached to the ACSI bus: Atari SLM laser printer, BioNet-100
12419 Ethernet, and PAMsNet Ethernet. If you want to use one of these
12420 devices, you need ACSI support, too.
12422 This driver is also available as a module ( = code which can be
12423 inserted in and removed from the running kernel whenever you want).
12424 The module will be called acsi.o.
12426 Probe all LUNs on each ACSI device
12427 CONFIG_ACSI_MULTI_LUN
12428 If you have a ACSI device that supports more than one LUN (Logical
12429 Unit Number), e.g. a CD jukebox, you should say Y here so that all
12430 will be found by the ACSI driver. An ACSI device with multiple LUNs
12431 acts logically like multiple ACSI devices. The vast majority of ACSI
12432 devices have only one LUN, and so most people can say N here and
12433 should in fact do so, because it is safer.
12435 Atari SLM laser printer support
12437 If you have an Atari SLM laser printer, say Y to include support for
12438 it in the kernel. Otherwise, say N. This driver is also available as
12439 a module ( = code which can be inserted in and removed from the
12440 running kernel whenever you want). The module will be called
12441 acsi_slm.o. Be warned: the driver needs much ST-RAM and can cause
12442 problems due to that fact!
12444 A3000 WD33C93A support
12446 If you have an Amiga 3000 and have SCSI devices connected to the
12447 built-in SCSI controller, say Y. Otherwise, say N. This driver is
12448 also available as a module ( = code which can be inserted in and
12449 removed from the running kernel whenever you want). The module is
12450 called wd33c93.o. If you want to compile it as a module, say M here
12451 and read Documentation/modules.txt.
12453 A2091 WD33C93A support
12455 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
12456 say N. This driver is also available as a module ( = code which can
12457 be inserted in and removed from the running kernel whenever you
12458 want). The module is called wd33c93.o. If you want to compile it as
12459 a module, say M here and read Documentation/modules.txt.
12461 GVP Series II WD33C93A support
12463 If you have a Great Valley Products Series II SCSI controller,
12464 answer Y. Also say Y if you have a later model of GVP SCSI
12465 controller (such as the GVP A4008 or a Combo board). Otherwise,
12466 answer N. This driver does NOT work for the T-Rex series of
12467 accelerators from TekMagic and GVP-M.
12469 This driver is also available as a module ( = code which can be
12470 inserted in and removed from the running kernel whenever you
12471 want). The module will be called gvp11.o. If you want to compile it
12472 as a module, say M here and read Documentation/modules.txt.
12474 Cyberstorm SCSI support
12475 CONFIG_CYBERSTORM_SCSI
12476 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
12477 accelerator board and the optional Cyberstorm SCSI controller,
12478 answer Y. Otherwise, say N.
12480 Cyberstorm II SCSI support
12481 CONFIG_CYBERSTORMII_SCSI
12482 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
12483 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
12486 Blizzard 2060 SCSI support
12487 CONFIG_BLZ2060_SCSI
12488 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
12489 and want to use the onboard SCSI controller, say Y. Otherwise,
12492 Blizzard 1230IV/1260 SCSI support
12493 CONFIG_BLZ1230_SCSI
12494 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
12495 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
12498 Blizzard PowerUP 603e+ SCSI support (EXPERIMENTAL)
12499 CONFIG_BLZ603EPLUS_SCSI
12500 If you have an Amiga 1200 with a Phase5 Blizzard PowerUP 603e+
12501 accelerator, say Y. Otherwise, say N.
12503 Fastlane SCSI support
12504 CONFIG_FASTLANE_SCSI
12505 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
12506 one in the near future, say Y to this question. Otherwise, say N.
12508 Atari native SCSI support
12510 If you have an Atari with built-in NCR5380 SCSI controller (TT,
12511 Falcon, ...) say Y to get it supported. Of course also, if you have
12512 a compatible SCSI controller (e.g. for Medusa). This driver is also
12513 available as a module ( = code which can be inserted in and removed
12514 from the running kernel whenever you want). The module is called
12515 atari_scsi.o. If you want to compile it as a module, say M here and
12516 read Documentation/modules.txt. This driver supports both styles of
12517 NCR integration into the system: the TT style (separate DMA), and
12518 the Falcon style (via ST-DMA, replacing ACSI). It does NOT support
12519 other schemes, like in the Hades (without DMA).
12521 Long delays for Toshiba CD-ROMs
12522 CONFIG_ATARI_SCSI_TOSHIBA_DELAY
12523 This option increases the delay after a SCSI arbitration to
12524 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
12525 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
12526 would impact performance a bit, so say N.
12528 Hades SCSI DMA emulator
12530 This option enables code which emulates the TT SCSI DMA chip on the
12531 Hades. This increases the SCSI transfer rates at least ten times
12532 compared to PIO transfers.
12536 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
12539 This driver is also available as a module ( = code which can be
12540 inserted in and removed from the running kernel whenever you
12541 want). The module is called ariadne.o. If you want to compile it as
12542 a module, say M here and read Documentation/modules.txt.
12546 If you have a Village Tronic Ariadne II Ethernet adapter, say Y.
12549 This driver is also available as a module ( = code which can be
12550 inserted in and removed from the running kernel whenever you
12551 want). The module is called ariadne2.o. If you want to compile it as
12552 a module, say M here and read Documentation/modules.txt.
12556 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
12559 This driver is also available as a module ( = code which can be
12560 inserted in and removed from the running kernel whenever you
12561 want). The module is called a2065.o. If you want to compile it as a
12562 module, say M here and read Documentation/modules.txt.
12566 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
12568 This driver is also available as a module ( = code which can be
12569 inserted in and removed from the running kernel whenever you
12570 want). The module is called hydra.o. If you want to compile it as a
12571 module, say M here and read Documentation/modules.txt.
12573 Pcmcia NE2000 compatible support
12575 If you have a pcmcia ne2000 compatible adapter, say Y. Otherwise,
12578 This driver is also available as a module ( = code which can be
12579 inserted in and removed from the running kernel whenever you
12580 want). The module is called apne.o. If you want to compile it as a
12581 module, say M here and read Documentation/modules.txt.
12583 Atari Lance support
12585 Say Y to include support for several Atari Ethernet adapters based
12586 on the AMD Lance chipset: RieblCard (with or without battery), or
12587 PAMCard VME (also the version by Rhotron, with different addresses).
12590 CONFIG_ATARI_BIONET
12591 Say Y to include support for BioData's BioNet-100 Ethernet adapter
12592 for the ACSI port. The driver works (has to work...) with a polled
12593 I/O scheme, so it's rather slow :-(
12596 CONFIG_ATARI_PAMSNET
12597 Say Y to include support for the PAMsNet Ethernet adapter for the
12598 ACSI port ("ACSI node"). The driver works (has to work...) with a
12599 polled I/O scheme, so it's rather slow :-(
12601 Multiface Card III parallel support
12602 CONFIG_MULTIFACE_III_LP
12603 If you have a Multiface III card for your Amiga, and want to use its
12604 parallel port in Linux, say Y. Otherwise, say N.
12606 This driver is also available as a module ( = code which can be
12607 inserted in and removed from the running kernel whenever you want).
12608 The module is called lp_m68k.o. If you want to compile it as a
12609 module, say M here and read Documentation/modules.txt.
12611 Amiga mouse support
12613 If you want to be able to use an Amiga mouse in Linux, say Y.
12615 This driver is also available as a module ( = code which can be
12616 inserted in and removed from the running kernel whenever you want).
12617 The module is called amigamouse.o. If you want to compile it as a
12618 module, say M here and read Documentation/modules.txt.
12620 Amiga Copper Console
12622 This configures the console to use the Amiga's graphics coprocessor
12623 for scrolling, instead of using the CPU. This option markedly
12624 improves response times in the high color modes (5 bitplanes and
12625 up). If you would like to use this, say Y; otherwise, say N.
12627 Atari mouse support
12629 If you want to be able to use an Atari mouse in Linux, say Y.
12631 This driver is also available as a module ( = code which can be
12632 inserted in and removed from the running kernel whenever you want).
12633 The module is called atarimouse.o. If you want to compile it as a
12634 module, say M here and read Documentation/modules.txt.
12636 Atari MFP serial support
12637 CONFIG_ATARI_MFPSER
12638 If you like to use the MFP serial ports ("Modem1", "Serial1") under
12639 Linux, say Y. The driver equally supports all kinds of MFP serial
12640 ports and automatically detects whether Serial1 is available.
12642 This driver is also available as a module ( = code which can be
12643 inserted in and removed from the running kernel whenever you want).
12644 If you want to compile it as a module, say M here and read
12645 Documentation/modules.txt.
12647 Note for Falcon users: You also have an MFP port, it's just not
12648 wired to the outside... But you could use the port under Linux.
12650 Atari SCC serial support
12652 If you have serial ports based on a Zilog SCC chip (Modem2, Serial2,
12653 LAN) and like to use them under Linux, say Y. All built-in SCC's are
12654 supported (TT, MegaSTE, Falcon), and also the ST-ESCC. If you have
12655 two connectors for channel A (Serial2 and LAN), they are visible as
12656 two separate devices.
12658 This driver is also available as a module ( = code which can be
12659 inserted in and removed from the running kernel whenever you want).
12660 If you want to compile it as a module, say M here and read
12661 Documentation/modules.txt.
12663 Atari SCC serial DMA support
12664 CONFIG_ATARI_SCC_DMA
12665 This enables DMA support for receiving data on channel A of the SCC.
12666 If you have a TT you may say Y here and read
12667 drivers/char/atari_SCC.README. All other users should say N here,
12668 because only the TT has SCC-DMA, even if your machine keeps claiming
12671 Atari MIDI serial support
12673 If you want to use your Atari's MIDI port in Linux, say Y.
12675 This driver is also available as a module ( = code which can be
12676 inserted in and removed from the running kernel whenever you
12677 want). If you want to compile it as a module, say M here and read
12678 Documentation/modules.txt.
12680 Atari DSP56k Digital Signal Processor support (EXPERIMENTAL)
12681 CONFIG_ATARI_DSP56K
12682 If you want to be able to use the DSP56001 in Falcons, say Y. This
12683 driver is still experimental, and if you don't know what it is, or
12684 if you don't have this processor, just say N.
12686 This driver is also available as a module ( = code which can be
12687 inserted in and removed from the running kernel whenever you want).
12688 If you want to compile it as a module, say M here and read
12689 Documentation/modules.txt.
12691 Amiga builtin serial support
12692 CONFIG_AMIGA_BUILTIN_SERIAL
12693 If you want to use your Amiga's built-in serial port in Linux,
12696 This driver is also available as a module ( = code which can be
12697 inserted in and removed from the running kernel whenever you
12698 want). If you want to compile it as a module, say M here and read
12699 Documentation/modules.txt.
12701 GVP IO-Extender support
12703 If you want to use a GVP IO-Extender serial card in Linux, say Y.
12706 Multiface Card III serial support
12707 CONFIG_MULTIFACE_III_TTY
12708 If you want to use a Multiface III card's serial port in Linux,
12711 This driver is also available as a module ( = code which can be
12712 inserted in and removed from the running kernel whenever you want).
12713 If you want to compile it as a module, say M here and read
12714 Documentation/modules.txt.
12716 Amiga or Atari DMA sound support
12718 If you want to use the internal audio of your Atari or Amiga in
12719 Linux, answer Y to this question. This will provide a Sun-like
12720 /dev/audio, compatible with the Linux/i386 sound system. Otherwise,
12723 This driver is also available as a module ( = code which can be
12724 inserted in and removed from the running kernel whenever you
12725 want). If you want to compile it as a module, say M here and read
12726 Documentation/modules.txt.
12728 HP DCA serial support
12730 If you want to use the internal "DCA" serial ports on an HP300
12731 machine, say Y here.
12733 HP on-board LANCE support
12735 If you want to use the builtin "LANCE" Ethernet controller on an
12736 HP300 machine, say Y here.
12738 Sun 3 onboard LANCE support
12740 If you want to use the onboard AMD "LANCE" (le) Ethernet hardware
12741 on a Sun 3, you will need to say Y here.
12745 Say Y here to enable support for the "DIO" expansion bus used in
12746 HP300 machines. If you are using such a system you almost certainly
12751 There are three types of PowerPC chips supported. The more common
12752 types (601, 603, 604, 740, 750), the Motorola embedded versions (821,
12753 823, 850, 855, 860), and the IBM embedded versions (403 and 405).
12754 Unless you are building a kernel for one of the embedded processor
12755 systems, choose 6xx.
12759 Linux currently supports several different kinds of PowerPC-based
12760 machines: Apple Power Macintoshes and clones (such as the Motorola
12761 Starmax series), PReP (PowerPC Reference Platform) machines such as
12762 the Motorola PowerStack, Amiga Power-Up systems (APUS), CHRP and the
12763 embedded MBX boards from Motorola. Currently, a single kernel binary
12764 only supports one type or the other. However, there is very early
12765 work on support for CHRP, PReP and PowerMac's from a single binary.
12767 Support for Open Firmware device tree in /proc
12768 CONFIG_PROC_DEVICETREE
12769 This option adds a device-tree directory under /proc which contains
12770 an image of the device tree that the kernel copies from Open
12771 Firmware. If unsure, say Y here.
12773 MESH (Power Mac internal SCSI) support
12775 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
12776 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
12777 other Power Macintoshes do). Say Y to include support for this SCSI
12778 adaptor. This driver is also available as a module called mesh.o
12779 ( = code which can be inserted in and removed from the running
12780 kernel whenever you want). If you want to compile it as a module,
12781 say M here and read Documentation/modules.txt.
12783 Maximum synchronous transfer rate
12784 CONFIG_SCSI_MESH_SYNC_RATE
12785 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
12786 drives a bus which is entirely internal to the machine (such as the
12787 7500, 7600, 8500, etc.), the MESH is capable of synchronous
12788 operation at up to 10 MB/s. On machines where the SCSI bus
12789 controlled by the MESH can have external devices connected, it is
12790 usually rated at 5 MB/s. 5 is a safe value here unless you know the
12791 MESH SCSI bus is internal only; in that case you can say 10. Say 0
12792 to disable synchronous operation.
12794 53C94 (Power Mac external SCSI) support
12795 CONFIG_SCSI_MAC53C94
12796 On Power Macintoshes (and clones) with two SCSI buses, the external
12797 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
12798 machines which only have one SCSI bus, such as the 7200, also use
12799 the 53C94. Say Y to include support for the 53C94.
12801 This driver is also available as a module called mac53c94.o ( = code
12802 which can be inserted in and removed from the running kernel
12803 whenever you want). If you want to compile it as a module, say M
12804 here and read Documentation/modules.txt.
12806 MACE (Power Mac Ethernet) support
12808 Power Macintoshes and clones with Ethernet built-in on the
12809 motherboard will usually use a MACE (Medium Access Control for
12810 Ethernet) interface. Say Y to include support for the MACE chip.
12812 This driver is also available as a module called mace.o ( = code
12813 which can be inserted in and removed from the running kernel
12814 whenever you want). If you want to compile it as a module, say M
12815 here and read Documentation/modules.txt.
12817 BMAC (G3 ethernet) support
12819 Say Y for support of BMAC Ethernet interfaces. These are used on G3
12822 This driver is also available as a module called bmac.o ( = code
12823 which can be inserted in and removed from the running kernel
12824 whenever you want). If you want to compile it as a module, say M
12825 here and read Documentation/modules.txt.
12829 Support for audio/video capture and overlay devices and FM radio
12830 cards. The exact capabilities of each device vary. User tools for
12831 this are available from
12832 ftp://ftp.uk.linux.org/pub/linux/video4linux .
12834 If you are interested in writing a driver for such an audio/video
12835 device or user software interacting with such a driver, please read
12836 the file Documentation/video4linux/API.html.
12838 This driver is also available as a module called videodev.o ( = code
12839 which can be inserted in and removed from the running kernel
12840 whenever you want). If you want to compile it as a module, say M
12841 here and read Documentation/modules.txt.
12843 AIMSlab RadioTrack (aka RadioReveal) support
12844 CONFIG_RADIO_RTRACK
12845 Choose Y here if you have one of these FM radio cards, and then fill
12846 in the port address below.
12848 Note that newer AIMSlab RadioTrack cards have a different chipset
12849 and are not supported by this driver. For these cards, use the
12850 RadioTrack II driver below.
12852 If you have a GemTeks combined (PnP) sound- and radio card you must
12853 use this driver as a module and setup the card with isapnptools. You
12854 must also pass the module a suitable io parameter, 0x248 has been
12855 reported to be used by these cards.
12857 In order to control your radio card, you will need to use programs
12858 that are compatible with the Video for Linux API. Information on
12859 this API and pointers to "v4l" programs may be found on the WWW at
12860 http://roadrunner.swansea.uk.linux.org/v4l.shtml . More information
12861 is contained in the file Documentation/video4linux/radiotrack.txt.
12863 If you want to compile this driver as a module ( = code which can be
12864 inserted in and removed from the running kernel whenever you want),
12865 say M here and read Documentation/modules.txt. The module will be
12866 called radio-aimslab.o.
12868 RadioTrack i/o port
12869 CONFIG_RADIO_RTRACK_PORT
12870 Enter either 0x30f or 0x20f here. The card default is 0x30f, if you
12871 haven't changed the jumper setting on the card.
12873 AIMSlab RadioTrack II support
12874 CONFIG_RADIO_RTRACK2
12875 Choose Y here if you have this FM radio card, and then fill in the
12876 port address below.
12878 In order to control your radio card, you will need to use programs
12879 that are compatible with the Video for Linux API. Information on
12880 this API and pointers to "v4l" programs may be found on the WWW at
12881 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
12883 If you want to compile this driver as a module ( = code which can be
12884 inserted in and removed from the running kernel whenever you want),
12885 say M here and read Documentation/modules.txt. The module will be
12886 called radio-rtrack2.o.
12888 RadioTrack II i/o port
12889 CONFIG_RADIO_RTRACK2_PORT
12890 Enter either 0x30c or 0x20c here. The card default is 0x30c, if you
12891 haven't changed the jumper setting on the card.
12893 Aztech/Packard Bell Radio
12894 CONFIG_RADIO_AZTECH
12895 Choose Y here if you have one of these FM radio cards, and then fill
12896 in the port address below.
12898 In order to control your radio card, you will need to use programs
12899 that are compatible with the Video for Linux API. Information on
12900 this API and pointers to "v4l" programs may be found on the WWW at
12901 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
12903 If you want to compile this driver as a module ( = code which can be
12904 inserted in and removed from the running kernel whenever you want),
12905 say M here and read Documentation/modules.txt. The module will be
12906 called radio-aztech.o.
12908 Aztech/Packard Bell radio card i/o port
12909 CONFIG_RADIO_AZTECH_PORT
12910 Enter either 0x350 or 0x358 here. The card default is 0x350, if you
12911 haven't changed the setting of jumper JP3 on the card. Removing the
12912 jumper sets the card to 0x358.
12914 ADS Cadet AM/FM Radio Tuner Card
12916 Choose Y here if you have one of these AM/FM radio cards, and then
12917 fill in the port address below.
12919 In order to control your radio card, you will need to use programs
12920 that are compatible with the Video for Linux API. Information on
12921 this API and pointers to "v4l" programs may be found on the WWW at
12922 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
12924 Further documentation on this driver can be found on the WWW at
12925 http://linux.blackhawke.net/cadet.html .
12927 If you want to compile this driver as a module ( = code which can be
12928 inserted in and removed from the running kernel whenever you want),
12929 say M here and read Documentation/modules.txt. The module will be
12930 called radio-cadet.o.
12932 ADS Cadet AM/FM Radio Tuner Card I/O Port
12933 CONFIG_RADIO_CADET_PORT
12934 Enter the I/O address of the card here (most commonly 330).
12937 CONFIG_RADIO_SF16FMI
12938 Choose Y here if you have one of these FM radio cards, and then fill
12939 in the port address below.
12941 In order to control your radio card, you will need to use programs
12942 that are compatible with the Video for Linux API. Information on
12943 this API and pointers to "v4l" programs may be found on the WWW at
12944 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
12946 If you want to compile this driver as a module ( = code which can be
12947 inserted in and removed from the running kernel whenever you want),
12948 say M here and read Documentation/modules.txt. The module will be
12949 called radio-sf16fmi.o
12951 SF16FMI I/O port (0x284 or 0x384)
12952 CONFIG_RADIO_SF16FMI_PORT
12953 Enter the I/O port of your SF16FMI radio card.
12956 CONFIG_RADIO_TYPHOON
12957 Choose Y here if you have one of these FM radio cards, and then fill
12958 in the port address and the frequency used for muting below.
12960 In order to control your radio card, you will need to use programs
12961 that are compatible with the Video for Linux API. Information on
12962 this API and pointers to "v4l" programs may be found on the WWW at
12963 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
12965 If you want to compile this driver as a module ( = code which can be
12966 inserted in and removed from the running kernel whenever you want),
12967 say M here and read Documentation/modules.txt. The module will be
12968 called radio-typhoon.o
12970 Support for /proc/radio-typhoon
12971 CONFIG_RADIO_TYPHOON_PROC_FS
12972 Say Y here if you want the typhoon radio card driver to write
12973 status information (frequency, volume, muted, mute frequency,
12974 base address) to /proc/radio-typhoon. The file can be viewed with
12975 your favorite pager (i.e. use "more /proc/radio-typhoon" or "less
12976 /proc/radio-typhoon" or simply "cat /proc/radio-typhoon").
12978 Typhoon I/O port (0x316 or 0x336)
12979 CONFIG_RADIO_TYPHOON_PORT
12980 Enter the I/O port of your Typhoon or EcoRadio radio card.
12982 Typhoon frequency set when muting the device (kHz)
12983 CONFIG_RADIO_TYPHOON_MUTEFREQ
12984 Enter the frequency used for muting the radio. The device is never
12985 completely silent. If the volume is just turned down, you can still
12986 hear silent voices and music. For that reason, the frequency of the
12987 radio device is set to the frequency you can enter here whenever
12988 the device is muted. There should be no local radio station at that
12992 CONFIG_RADIO_ZOLTRIX
12993 Choose Y here if you have one of these FM radio cards, and then fill
12994 in the port address below.
12996 In order to control your radio card, you will need to use programs
12997 that are compatible with the Video for Linux API. Information on
12998 this API and pointers to "v4l" programs may be found on the WWW at
12999 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
13001 If you want to compile this driver as a module ( = code which can be
13002 inserted in and removed from the running kernel whenever you want),
13003 say M here and read Documentation/modules.txt. The module will be
13004 called radio-zoltrix.o
13006 ZOLTRIX I/O port (0x20c or 0x30c)
13007 CONFIG_RADIO_ZOLTRIX_PORT
13008 Enter the I/O port of your Zoltrix radio card.
13010 IIC on parallel port
13012 I2C is a simple serial bus system used in many micro controller
13013 applications. Saying Y here will allow you to use your parallel port
13014 as an I2C interface.
13016 If you want to compile this driver as a module ( = code which can be
13017 inserted in and removed from the running kernel whenever you want),
13018 say M here and read Documentation/modules.txt. The module will be
13019 called i2c-parport.o.
13022 CONFIG_RADIO_MIROPCM20
13023 Choose Y here if you have this FM radio card. You also need to say Y
13024 to "ACI mixer (miroPCM12/PCM20)" (in "additional low level sound
13025 drivers") for this to work.
13027 In order to control your radio card, you will need to use programs
13028 that are compatible with the Video for Linux API. Information on
13029 this API and pointers to "v4l" programs may be found on the WWW at
13030 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
13032 If you want to compile this driver as a module ( = code which can be
13033 inserted in and removed from the running kernel whenever you want),
13034 say M here and read Documentation/modules.txt. The module will be
13035 called radio-miropcm20.o
13038 CONFIG_RADIO_GEMTEK
13039 Choose Y here if you have this FM radio card, and then fill in the
13040 port address below.
13042 In order to control your radio card, you will need to use programs
13043 that are compatible with the Video for Linux API. Information on
13044 this API and pointers to "v4l" programs may be found on the WWW at
13045 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
13047 If you want to compile this driver as a module ( = code which can be
13048 inserted in and removed from the running kernel whenever you want),
13049 say M here and read Documentation/modules.txt. The module will be
13050 called radio-gemtek.o.
13053 CONFIG_RADIO_GEMTEK_PORT
13054 Enter either 0x20c, 0x30c, 0x24c or 0x34c here. The card default is
13055 0x34c, if you haven't changed the jumper setting on the card.
13057 PlanB Video-In for PowerMacs
13059 PlanB is the V4L driver for the PowerMac 7x00/8x00 series video
13060 input hardware. If you want to experiment with this, say Y.
13061 Otherwise, or if you don't understand a word, say N.
13062 See http://www.cpu.lu/~mlan/planb.html for more info.
13064 Saying M will compile this driver as a module (planb.o).
13066 TerraTec ActiveRadio
13067 CONFIG_RADIO_TERRATEC
13068 Choose Y here if you have this FM radio card, and then fill in the
13069 port address below. (TODO)
13071 Note: This driver is in its early stages. Right now volume and
13072 frequency control and muting works at least for me, but
13073 unfortunately i have not found anybody who wants to use this card
13074 with linux. So if it is this what YOU are trying to do right now,
13075 PLEASE DROP ME A NOTE!! Rolf Offermanns (rolf@offermanns.de)
13077 In order to control your radio card, you will need to use programs
13078 that are compatible with the Video for Linux API. Information on
13079 this API and pointers to "v4l" programs may be found on the WWW at
13080 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
13081 you need to have access to a machine on the Internet that has a
13082 program like lynx or netscape.
13084 If you want to compile this driver as a module ( = code which can be
13085 inserted in and removed from the running kernel whenever you want),
13086 say M here and read Documentation/modules.txt. The module will be
13087 called radio-terratec.o.
13089 # Zoran ZR36057/36060 support
13090 # CONFIG_VIDEO_ZORAN
13092 # Include support for Iomega Buz
13095 BT848 Video For Linux
13097 Support for BT848 based frame grabber/overlay boards. This includes
13098 the Miro, Hauppauge and STB boards. Please read the material in
13099 Documentation/video4linux/bttv for more information.
13101 This driver is also available as a module called bttv.o ( = code
13102 which can be inserted in and removed from the running kernel
13103 whenever you want). If you want to compile it as a module, say M
13104 here and read Documentation/modules.txt.
13106 ZR36120/36125 Video for Linux
13107 CONFIG_VIDEO_ZR36120
13108 Support for ZR36120/ZR36125 based frame grabber/overlay boards.
13109 This includes the Victor II, WaveWatcher, Video Wonder, Maxi-TV,
13110 and Buster boards. Please read the material in
13111 Documentation/video4linux/zr36120.txt for more information.
13113 This driver is also available as a module called zr36120.o ( = code
13114 which can be inserted in and removed from the running kernel
13115 whenever you want). If you want to compile it as a module, say M
13116 here and read Documentation/modules.txt.
13118 SAA5249 Teletext processor
13119 CONFIG_VIDEO_SAA5249
13120 Support for I2C bus based teletext using the SAA5249 chip. At the
13121 moment this is only useful on some European WinTV cards.
13123 This driver is also available as a module called saa5249.o ( = code
13124 which can be inserted in and removed from the running kernel
13125 whenever you want). If you want to compile it as a module, say M
13126 here and read Documentation/modules.txt.
13128 Quickcam BW Video For Linux
13129 CONFIG_VIDEO_BWQCAM
13130 Say Y have if you the black and white version of the QuickCam
13131 camera. See the next option for the color version.
13133 This driver is also available as a module called bw-qcam.o ( = code
13134 which can be inserted in and removed from the running kernel
13135 whenever you want). If you want to compile it as a module, say M
13136 here and read Documentation/modules.txt.
13138 Colour QuickCam Video For Linux
13140 This is the video4linux driver for the colour version of the
13141 Connectix Quickcam. If you have one of these cameras, say Y here,
13142 otherwise say N. This driver does not work with the original
13143 monochrome Quickcam, Quickcam VC or QuickClip. It is also available
13144 as a module (c-qcam.o).
13146 Mediavision Pro Movie Studio Video For Linux
13148 Say Y if you have such a thing. This driver is also available as a
13149 module called pms.o ( = code which can be inserted in and removed
13150 from the running kernel whenever you want). If you want to compile
13151 it as a module, say M here and read Documentation/modules.txt.
13153 Compaq SMART2 support
13155 This is the driver for Compaq Smart Array controllers.
13156 Everyone using these boards should say Y here.
13157 See the file Documentation/cpqarray.txt for the current list of
13158 boards supported by this driver, and for further information
13159 on the use of this driver.
13161 QuickNet Internet LineJack/PhoneJack support
13163 Say M if you have a telephony card manufactured by Quicknet
13164 Technologies, Inc. These include the Internet PhoneJACK and
13165 Internet LineJACK Telephony Cards.
13167 For the ISA versions of these products, you can configure the
13168 cards using the isapnp tools (pnpdump/isapnp) or you can use the
13169 isapnp support. Please read:
13171 /usr/src/linux/Documentation/telephony/ixj.txt.
13173 For more information on these cards, see Quicknet's website at:
13174 http://www.quicknet.net/
13176 If you do not have any Quicknet telephony cards, you can safely
13177 ignore this option.
13179 /dev/agpgart (AGP Support) (EXPERIMENTAL)
13181 The agpgart kernel module is necessary to use the AGP features
13182 of your 3D rendering video card. It acts as a sort of "AGP
13183 driver" for the motherboard's chipset.
13184 Loading this module into the kernel will allow the glx module to
13185 program the GART (graphics aperture relocation table) registers
13186 with appropriate values to transfer commands to the card.
13188 If you need more texture memory than you can get with the AGP GART
13189 (theoretically up to 256 megs, but in practice usually 64 or 128
13190 megs due to kernel allocation issues), you could use PCI accesses
13191 and have up to a couple gigs of texture space.
13193 Note that this is the only meas to have get XFree4/GLX use
13194 write-combining with MTRR support on AGP bus. Without, OpenGL
13195 direct rendering will be a lot slower but still faster than PIO.
13197 For the moment, most people should say no, unless you want to
13198 test the GLX component which can be downloaded from
13199 http://glx.on.openprojects.net/
13201 or need to use the 810 Xserver in XFree 3.3.6
13203 Intel 440LX/BX/GX support
13205 This option give you AGP support for the GLX component of the
13206 "soon to be released" XFree86-4 on Intel 440LX/BX/GX chipsets.
13208 For the moment, most people should say no, unless you want to
13209 test the GLX component which can be downloaded from
13210 http://glx.on.openprojects.net/
13212 Intel I810/I810 DC100/I810e support
13214 This option give you AGP support for the Xserver for the intel
13215 810 chipset boards. This is required to do any useful video
13218 VIA VP3/MVP3/Apollo Pro support
13220 This option give you AGP support for the GLX component of the
13221 "soon to be released" XFree86-4 on VIA MPV3/Apollo Pro chipsets.
13223 For the moment, most people should say no, unless you want to
13224 test the GLX component which can be downloaded from
13225 http://glx.on.openprojects.net/
13227 AMD Irongate support
13229 This option give you AGP support for the GLX component of the
13230 "soon to be released" XFree86-4 on Intel AMD Irongate chipset.
13232 For the moment, most people should say no, unless you want to
13233 test the GLX component which can be downloaded from
13234 http://glx.on.openprojects.net/
13236 Generic SiS support
13238 This option give you AGP support for the GLX component of the
13239 "soon to be released" XFree86-4 on Silicon Integrated Systems [SiS]
13242 Note than 5591/5592 AGP chipsets are NOT supported.
13244 For the moment, most people should say no, unless you want to
13245 test the GLX component which can be downloaded from
13246 http://glx.on.openprojects.net/
13250 This option give you AGP support for the GLX component of the
13251 "soon to be released" XFree86-4 on ALI M1541 chipset.
13253 For the moment, most people should say no, unless you want to
13254 test the GLX component which can be downloaded from
13255 http://glx.on.openprojects.net/
13262 This selects the processor type of your CPU. This is only used to
13263 determine C compiler optimization options, and can affect the
13264 compatibility of the kernel on other processors. If you specify
13265 ARM6, the kernel should work on all 32-bit processors. If you
13266 specify ARM2, ARM250 or ARM3, it should work on all 26-bit
13267 processors. If you're not sure, set it to "None".
13271 This selects what ARM system you wish to build the kernel for. It
13272 also selects to some extent the CPU type. If you are unsure what
13273 to set this option to, please consult any information supplied with
13276 Include support for Chalice CATS boards
13278 Say Y here if you intend to run this kernel on a CATS system.
13280 Include support for Intel EBSA285
13281 CONFIG_ARCH_EBSA285
13284 Include support for the NetWinder
13285 CONFIG_ARCH_NETWINDER
13286 Say Y here if you intend to run this kernel on the NetWinder.
13288 Virtual/Physical Memory Split
13290 If you are compiling a kernel which will never run on a machine
13291 with more than 1 Gigabyte total physical RAM, answer "3GB/1GB"
13292 here (default choice).
13294 On 32-bit x86 systems Linux can use up to 64 Gigabytes of physical
13295 memory. However 32-bit x86 processors have only 4 Gigabytes of
13296 virtual memory space. This option specifies the maximum amount of
13297 virtual memory space one process can potentially use. Certain types
13298 of applications (eg. database servers) perform better if they have
13299 as much virtual memory per process as possible.
13301 The remaining part of the 4G virtual memory space is used by the
13302 kernel to 'permanently map' as much physical memory as possible.
13303 Certain types of applications perform better if there is more
13304 'permanently mapped' kernel memory.
13306 [WARNING! Certain boards do not support PCI DMA to physical addresses
13307 bigger than 2 Gigabytes. Non-DMA-able memory must not be permanently
13308 mapped by the kernel, thus a 1G/3G split will not work on such boxes.]
13310 As you can see there is no 'perfect split' - the fundamental
13311 problem is that 4G of 32-bit virtual memory space is short. So
13312 you'll have to pick your own choice - depending on the application
13313 load of your box. A 2G/2G split is typically a good choice for a
13314 generic Linux server with lots of RAM.
13316 Any potentially remaining (not permanently mapped) part of physical
13317 memory is called 'high memory'. How much total high memory the kernel
13318 can handle is influenced by the (next) High Memory configuration option.
13320 The actual amount of total physical memory will either be
13321 autodetected or can be forced by using a kernel command line option
13322 such as "mem=256M". (Try "man bootparam" or see the documentation of
13323 your boot loader (lilo or loadlin) about how to pass options to the
13324 kernel at boot time. The lilo procedure is also explained in the
13325 SCSI-HOWTO, available from http://www.linuxdoc.org/docs.html#howto .)
13329 Say Y to include the NWFPE floating point emulator in the kernel.
13330 This is necessary to run most binaries. Linux does not currently
13331 support floating point hardware so you need to say Y here even if
13332 your machine has an FPA or floating point co-processor podule.
13334 It is also possible to say M to build the emulator as a module
13335 (nwfpe.o) or indeed to leave it out altogether. However, unless you
13336 know what you are doing this can easily render your machine
13337 unbootable. Saying Y is the safe option.
13339 You may say N here if you are going to load the Acorn FPEmulator
13340 early in the bootup.
13342 DS1620 Thermometer support
13344 Say Y here to include support for the thermal management hardware
13345 found in the NetWinder. This driver allows the user to control the
13346 temperature set points and to read the current temperature.
13348 It is also possible to say M here to build it as a module (ds1620.o)
13349 It is recommended to be used on a NetWinder, but it is not a
13352 Verbose kernel error messages
13353 CONFIG_DEBUG_ERRORS
13354 This option controls verbose debugging information which can be
13355 printed when the kernel detects an internal error. This debugging
13356 information is useful to kernel hackers when tracking down problems,
13357 but mostly meaningless to other people. It's safe to say Y unless
13358 you are concerned with the code size or don't want to see these
13361 Build Tools Selection
13362 CONFIG_BINUTILS_NEW
13363 Say Y here if and only if you're using GCC 2.8.1/EGCS with a
13364 binutils version >= 2.8.1 to compile the kernel (check with "gcc
13365 --version" and "ld -v").
13367 Compile kernel with frame pointer
13368 CONFIG_FRAME_POINTER
13369 If you say Y here, the resulting kernel will be slightly larger and
13370 slower, but it will give useful debugging information. If you don't
13371 debug the kernel, you can say N.
13373 User fault debugging
13375 When a user program crashes due to an exception, the kernel can
13376 print a brief message explaining what the problem was. This is
13377 sometimes helpful for debugging but serves no purpose on a
13378 production system. Most people should say N here.
13380 Include gdb debugging information in kernel binary
13382 Say Y here to include source-level debugging information in the
13383 `vmlinux' binary image. This is handy if you want to use gdb or
13384 addr2line to debug the kernel. It has no impact on the in-memory
13385 footprint of the running kernel but it can increase the amount of
13386 time and disk space needed for compilation of the kernel. If in
13389 Split initialisation functions into discardable section
13390 CONFIG_TEXT_SECTIONS
13391 If you say Y here, kernel code that is only used during
13392 initialisation is collected into a special area of the kernel so
13393 that it can be discarded and the memory reclaimed when
13394 initialisation is complete. In addition, if the kernel you wish to
13395 build is able to run on multiple architectures, it allows the unused
13396 code to be discarded. Some versions of binutils, however, have a bug
13397 that causes the kernel to crash during startup when this option is
13398 enabled. Say Y unless you experience problems that you suspect may
13401 Disable pgtable cache (EXPERIMENTAL)
13402 CONFIG_NO_PGT_CACHE
13403 Normally the kernel maintains a `quicklist' of preallocated
13404 pagetable structures in order to increase performance. On machines
13405 with very few pages this may however be a loss. Say Y here to
13406 disable the pgtable cache.
13408 RISC OS personality
13410 Say Y here to include the kernel code necessary if you want to run
13411 Acorn RISC OS/Arthur binaries under Linux. This code is still very
13412 experimental; if this sounds frightening, say N and sleep in peace.
13413 You can also say M here to compile this support as a module (which
13414 will be called arthur.o).
13416 Initial kernel command line
13418 On some architectures (EBSA110 and CATS), there is currently no way
13419 for the boot loader to pass arguments to the kernel. For these
13420 architectures, you should supply some command-line options at build
13421 time by entering them here. As a minimum, you should specify the
13422 memory size and the root device (e.g., mem=64M root=/dev/nfs)
13424 Hardware alignment trap (EXPERIMENTAL)
13425 CONFIG_ALIGNMENT_TRAP
13426 ARM processors can not fetch/store information which is not
13427 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
13428 address divisible by 4. On 32-bit ARM processors, these non-aligned
13429 fetch/store instructions will be emulated in software if you say
13430 here, which has a severe performance impact. This is necessary for
13431 correct operation of some network protocols. With an IP-only
13432 configuration it is safe to say N, otherwise say Y.
13434 21285 serial port support
13435 CONFIG_SERIAL_21285
13436 If you have a machine based on a 21285 (Footbridge) StrongARM/PCI
13437 bridge you can enable its onboard serial port by enabling this
13438 option. The device has major ID 4, minor 64.
13440 Console on 21285 serial port
13441 CONFIG_SERIAL_21285_CONSOLE
13442 If you have enabled the serial port on the 21285 footbridge you can
13443 make it the console by answering Y to this option.
13446 CONFIG_HOST_FOOTBRIDGE
13447 The 21285 Footbridge chip can operate in either `host mode' or
13448 `add-in' mode. Say Y if your 21285 is in host mode, and therefore
13449 is the configuration master, otherwise say N. This must not be
13450 set to Y if the card is used in 'add-in' mode.
13452 MFM hard disk support
13454 Support the MFM hard drives on the Acorn Archimedes both
13455 on-board the A4x0 motherboards and via the Acorn MFM podules.
13456 Drives up to 64MB are supported. If you haven't got one of these
13457 machines or drives just say N.
13459 Old Archimedes floppy (1772) support
13460 CONFIG_BLK_DEV_FD1772
13461 Support the floppy drive on the Acorn Archimedes (A300, A4x0, A540,
13462 R140 and R260) series of computers; it supports only 720K floppies
13463 at the moment. If you don't have one of these machines just answer
13466 Autodetect hard drive geometry
13467 CONFIG_BLK_DEV_MFM_AUTODETECT
13468 If you answer Y, the MFM code will attempt to automatically detect
13469 the cylinders/heads/sectors count on your hard drive. WARNING: This
13470 sometimes doesn't work and it also does some dodgy stuff which
13471 potentially might damage your drive.
13475 Say Y here if you want to build support for the IrDA (TM) protocols.
13476 The Infrared Data Associations (tm) specifies standards for wireless
13477 infrared communication and is supported by most laptops and PDA's.
13479 To use Linux support for the IrDA (tm) protocols, you will also need
13480 some user-space utilities like the irmanager and probably irattach
13481 as well. For more information, see the file
13482 Documentation/networking/irda.txt. You also want to read the
13483 IR-HOWTO, available at http://www.linuxdoc.org/docs.html#howto .
13485 This support is also available as a module. If you want to compile
13486 it as a module, say M here and read Documentation/modules.txt.
13488 IrDA Cache last LSAP
13489 CONFIG_IRDA_CACHE_LAST_LSAP
13490 Say Y here if you want IrLMP to cache the last LSAP used. This makes
13491 sense since most frames will be sent/received on the same
13492 connection. Enabling this option will save a hash-lookup per frame.
13497 CONFIG_IRDA_FAST_RR
13498 Say Y here is you want IrLAP to send fast RR (Receive Ready) frames
13499 when acting as a primary station. This will make IrLAP send out a RR
13500 frame immediately when receiving a frame if its own transmit queue
13501 is currently empty. This will give a lot of speed improvement when
13502 receiving much data since the secondary station will not have to
13503 wait the max. turn around time before it is allowed to transmit the
13504 next time. If the transmit queue of the secondary is also empty the
13505 primary will back off waiting longer for sending out the RR frame
13506 until the timeout reaches the normal value. Enabling this option
13507 will make the IR-diode burn more power and thus reduce your battery
13514 Say Y here if you want the IrDA subsystem to write debug information
13515 to your syslog. You can change the debug level in
13516 /proc/sys/net/irda/debug
13518 If unsure, say Y (since it makes it easier to find the bugs).
13520 IrLAP Compression support
13521 CONFIG_IRDA_COMPRESSION
13522 Compression is _not_ part of the IrDA(tm) protocol specification,
13523 but it's working great! Linux is the first to try out compression
13524 support at the IrLAP layer. This means that you will only benefit
13525 from compression if you are running a Linux <-> Linux configuration.
13527 If you say Y here, you also need to say Y or M to a compression
13530 IrLAP Deflate Compression Protocol (EXPERIMENTAL)
13531 CONFIG_IRDA_DEFLATE
13532 Say Y here if you want to build support for the Deflate compression
13533 protocol. The deflate compression (GZIP) is exactly
13534 the same as the one used by the PPP protocol.
13536 If you want to compile this compression support as a module, say M
13537 here and read Documentation/modules.txt. The module will be called
13542 Say Y here if you want to build support for the IrLAN protocol. If
13543 you want to compile it as a module, say M here and read
13544 Documentation/modules.txt. IrLAN emulates an Ethernet and makes it
13545 possible to put up a wireless LAN using infrared beams.
13547 The IrLAN protocol can be used to talk with infrared access points
13548 like the HP NetbeamIR, or the ESI JetEye NET. You can also connect
13549 to another Linux machine running the IrLAN protocol for ad-hoc
13554 Say Y here if you want to build support for the IrCOMM protocol. If
13555 you want to compile it as a module, say M here and read
13556 Documentation/modules.txt. IrCOMM implements serial port emulation,
13557 and makes it possible to use all existing applications that
13558 understands TTY's with an infrared link. Thus you should be able to
13559 use application like PPP, minicom and others. Enabling this option
13560 will create two modules called ircomm and ircomm-tty.
13562 IrTTY IrDA Device Driver
13564 Say Y here if you want to build support for the IrTTY line
13565 discipline. If you want to compile it as a module, say M here and
13566 read Documentation/modules.txt. IrTTY makes it possible to use
13567 Linux's own serial driver for all IrDA ports that are 16550
13568 compatible. Most IrDA chips are 16550 compatible so you should
13569 probably say Y to this option. Using IrTTY will however limit the
13570 speed of the connection to 115200 bps (IrDA SIR mode)
13574 IrPORT IrDA Device Driver
13576 Say Y here if you want to build support for the IrPORT IrDA device
13577 driver. If you want to compile it as a module, say M here and
13578 read Documentation/modules.txt. IrPORT can be used instead of
13579 IrTTY and sometimes this can be better. One example is if your
13580 IrDA port does not have echo-canceling, which will work OK with
13581 IrPORT since this driver is working in half-duplex mode only. You
13582 don't need to use irattach with IrPORT, but you just insert it
13583 the same way as FIR drivers (insmod irport io=0x3e8 irq=11).
13584 Notice that IrPORT is a SIR device driver which means that speed
13585 is limited to 115200 bps.
13589 SiS5513 chipset support
13590 CONFIG_BLK_DEV_SIS5513
13591 This driver ensures (U)DMA support for SIS5513 chipset based
13592 mainboards. SiS620/530 UDMA mode 4, SiS5600/5597 UDMA mode 2, all
13593 other DMA mode 2 limited chipsets are unsupported to date.
13595 If you say Y here, you need to say Y to "Use DMA by default when
13596 available" as well.
13598 Please read the comments at the top of drivers/block/sis5513.c
13600 Winbond W83977AF IrDA Device Driver
13602 Say Y here if you want to build IrDA support for the Winbond
13603 W83977AF super-io chipset. If you want to compile it as a module,
13604 say M here and read Documentation/modules.txt. This driver should be
13605 used for the IrDA chipset in the Corel NetWinder. The driver
13606 supports SIR, MIR and FIR (4Mbps) speeds.
13608 NSC PC87108 IrDA Device Driver
13610 Say Y here if you want to build support for the NSC PC87108 and
13611 PC87338 IrDA chipsets. If you want to compile it as a module, say M
13612 here and read Documentation/modules.txt. This driver supports SIR,
13613 MIR and FIR (4Mbps) speeds.
13615 Toshiba Type-O IR Port Device Driver
13617 Say Y here if you want to build support for the Toshiba Type-O IR
13618 chipset. If you want to compile it as a module, say M here and
13619 read Documentation/modules.txt. This chipset is used by the Toshiba
13620 Libretto 100CT, and many more laptops.
13622 ESI JetEye PC Dongle
13624 Say Y here if you want to build support for the Extended Systems
13625 JetEye PC dongle. If you want to compile it as a module, say M here
13626 and read Documentation/modules.txt. The ESI dongle attaches to the
13627 normal 9-pin serial port connector, and can currently only be used
13628 by IrTTY. To activate support for ESI dongles you will have to
13629 start irattach like this: "irattach -d esi".
13631 ACTiSYS IR-220L and IR220L+ dongle
13632 CONFIG_ACTISYS_DONGLE
13633 Say Y here if you want to build support for the ACTiSYS
13634 IR-220L and IR220L+ dongles. If you want to compile it as a module,
13635 say M here and read Documentation/modules.txt. The ACTiSYS dongles
13636 attaches to the normal 9-pin serial port connector, and can
13637 currently only be used by IrTTY. To activate support for ACTiSYS
13638 dongles you will have to start irattach like this:
13639 "irattach -d actisys" or "irattach -d actisys+".
13641 Tekram IrMate 210B dongle
13642 CONFIG_TEKRAM_DONGLE
13643 Say Y here if you want to build support for the Tekram IrMate 210B
13644 dongle. If you want to compile it as a module, say M here
13645 and read Documentation/modules.txt. The Tekram dongle attaches to
13646 the normal 9-pin serial port connector, and can currently only be
13647 used by IrTTY. To activate support for Tekram dongles you will have
13648 to start irattach like this: "irattach -d tekram".
13650 Greenwich GIrBIL dongle
13651 CONFIG_GIRBIL_DONGLE
13652 Say Y here if you want to build support for the Greenwich GIrBIL
13653 dongle. If you want to compile it as a module, say M here and read
13654 Documentation/modules.txt. The Greenwich dongle attaches to the
13655 normal 9-pin serial port connector, and can currently only be used
13656 by IrTTY. To activate support for Greenwich dongles you will have to
13657 insert "irattach -d girbil" in the /etc/irda/drivers script.
13659 Parallax Litelink dongle
13660 CONFIG_LITELINK_DONGLE
13661 Say Y here if you want to build support for the Parallax Litelink
13662 dongle. If you want to compile it as a module, say M here and read
13663 Documentation/modules.txt. The Parallax dongle attaches to the
13664 normal 9-pin serial port connector, and can currently only be used
13665 by IrTTY. To activate support for Parallax dongles you will have to
13666 start irattach like this "irattach -d litelink".
13668 VME (Motorola and BVM) support
13670 Say Y here if you want to build a kernel for a 680x0 based VME
13671 board. Boards currently supported include Motorola boards MVME162,
13672 MVME166, MVME167, MVME172, and MVME177. BVME4000 and BVME6000
13673 boards from BVM Ltd are also supported.
13675 MVME162, 166 and 167 support
13677 Say Y to include support for Motorola VME boards. This will build a
13678 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
13679 MVME177 boards. If you select this option you will have to select
13680 the appropriate drivers for SCSI, Ethernet and serial ports later
13683 BVME4000 and BVME6000 support
13685 Say Y to include support for VME boards from BVM Ltd. This will
13686 build a kernel which can run on BVME4000 and BVME6000 boards. If
13687 you select this option you will have to select the appropriate
13688 drivers for SCSI, Ethernet and serial ports later on.
13690 Use write-through caching for 68060 supervisor accesses
13691 CONFIG_060_WRITETHROUGH
13692 The 68060 generally uses copyback caching of recently accessed data.
13693 Copyback caching means that memory writes will be held in an on-chip
13694 cache and only written back to memory some time later. Saying Y
13695 here will force supervisor (kernel) accesses to use writethrough
13696 caching. Writethrough caching means that data is written to memory
13697 straight away, so that cache and memory data always agree.
13698 Writethrough caching is less efficient, but is needed for some
13699 drivers on 68060 based systems where the 68060 bus snooping signal
13700 is hardwired on. The 53c710 SCSI driver is known to suffer from
13703 NCR53C710 SCSI driver for MVME16x
13704 CONFIG_MVME16x_SCSI
13705 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
13706 SCSI controller chip. Almost everyone using one of these boards
13707 will want to say Y to this question.
13709 NCR53C710 SCSI driver for BVME6000
13710 CONFIG_BVME6000_SCSI
13711 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
13712 SCSI controller chip. Almost everyone using one of these boards
13713 will want to say Y to this question.
13715 Simple 53c710 SCSI support (Compaq, NCR machines)
13717 This is a driver for the NCR53C710 chip commonly found in Compaq and
13718 NCR machines. If you are looking for 53C710 support for an Amiga or
13719 some 680x0 based VME card then you probably want the other NCR53C710
13722 MVME16x Ethernet support
13724 This is the driver for the Ethernet interface on the Motorola
13725 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
13726 driver for this chip in your kernel. If you want to compile it as
13727 a module, say M here and read Documentation/modules.txt.
13729 BVME6000 Ethernet support
13730 CONFIG_BVME6000_NET
13731 This is the driver for the Ethernet interface on BVME4000 and
13732 BVME6000 VME boards. Say Y here to include the driver for this chip
13733 in your kernel. If you want to compile it as a module, say M here
13734 and read Documentation/modules.txt.
13736 CD2401 support for MVME166/7 serial ports
13738 This is the driver for the serial ports on the Motorola MVME166,
13739 167, and 172 boards. Everyone using one of these boards should say
13742 SCC support for MVME162 serial ports
13744 This is the driver for the serial ports on the Motorola MVME162 and
13745 172 boards. Everyone using one of these boards should say Y here.
13747 SCC support for BVME6000 serial ports
13748 CONFIG_BVME6000_SCC
13749 This is the driver for the serial ports on the BVME4000 and BVME6000
13750 boards from BVM Ltd. Everyone using one of these boards should say
13753 Support for user-space parallel port device drivers
13755 Saying Y to this adds support for /dev/parport device nodes. This
13756 is needed for programs that want portable access to the parallel
13757 port, for instance deviceid (which displays Plug-and-Play device
13760 This is the parallel port equivalent of SCSI generic support (sg).
13761 It is safe to say N to this -- it is not needed for normal printing
13762 or parallel port CD-ROM/disk support.
13764 This support is also available as a module. If you want to compile
13765 it as a module, say M here and read Documentation/modules.txt. The
13766 module will be called ppdev.o.
13770 Kernel httpd acceleration (EXPERIMENTAL)
13772 The kernel httpd acceleration daemon (kHTTPd) is a (limited)
13773 web server build into the kernel. It is limited since it can only
13774 serve files from the filesystem. Saying "M" here builds the
13775 kHTTPd module; this is NOT enough to have a working kHTTPd.
13776 For safety reasons, the module has to be activated by doing a
13777 "echo 1 > /proc/sys/net/khttpd/start" after inserting the module.
13779 Before using this, read the README in /usr/src/linux/net/khttpd !
13781 The kHTTPd is experimental. Be careful when using it on a production
13782 machine. Also note that kHTTPd doesn't support virtual servers yet.
13786 I2C (pronounce: I-square-C) is a slow bus protocol developed by
13787 Philips. SMBus, or System Management Bus is a sub-protocol of I2C.
13789 Both I2C and SMBus are supported here. You will need this for
13790 hardware sensors support, and in the future for Video for Linux
13793 Beside this option, you will also need to select specific drivers
13794 for your bus adapter(s).
13796 I2C bit-banging interfaces
13798 This allows you to use a range of I2C adapters called bit-banging
13799 adapters. Why they are called so is rather technical and uninteresting;
13800 but you need to select this if you own one of the adapters listed
13803 Philips style parallel port adapter
13804 CONFIG_I2C_PHILIPSPAR
13805 This supports parallel-port I2C adapters made by Philips. Unless you
13806 own such an adapter, you do not need to select this.
13810 This supports parallel-port I2C adapters called ELV. Unless you
13811 own such an adapter, you do not need to select this.
13813 Velleman K9000 adapter
13814 CONFIG_I2C_VELLEMAN
13815 This supports the Velleman K9000 parallel-port I2C adapter. Unless
13816 you own such an adapter, you do not need to select this.
13818 I2C PCF 8584 interfaces
13820 This allows you to use a range of I2C adapters called PCF
13821 adapters. Why they are called so is rather technical and uninteresting;
13822 but you need to select this if you own one of the adapters listed
13827 This supports the PCF8584 ISA bus I2C adapter. Unless you own such
13828 an adapter, you do not need to select this.
13830 I2C device interface
13832 Here you find the drivers which allow you to use the i2c-* device
13833 files, usually found in the /dev directory on your system. They
13834 make it possible to have user-space programs use the I2C bus.
13837 # A couple of things I keep forgetting:
13838 # capitalize: AppleTalk, Ethernet, DOS, DMA, FAT, FTP, Internet,
13839 # Intel, IRQ, Linux, MSDOS, NetWare, NetWinder, NFS,
13841 # two words: hard drive, hard disk, sound card, home page
13842 # other: it's safe to save; daemon; use --, not - or ---
13845 # This is used by Emacs' spell checker ispell.el:
13847 # LocalWords: CONFIG coprocessor DX Pentium SX lilo loadlin HOWTO ftp metalab
13848 # LocalWords: unc edu docs emu README kB BLK DEV FD Thinkpad fd MFM RLL IDE gz
13849 # LocalWords: cdrom diskless netboot nfs xzvf ATAPI MB ide pavia rubini pl pd
13850 # LocalWords: HD CDROMs IDECD NEC MITSUMI filesystem XT XD PCI BIOS cezar ATEN
13851 # LocalWords: ISA EISA Microchannel VESA BIOSes IPC SYSVIPC ipc Ctrl dmesg hlt
13852 # LocalWords: BINFMT Linkable http ac uk jo html GCC SPARC AVANTI CABRIOLET EB
13853 # LocalWords: netscape gcc LD CC toplevel MODVERSIONS insmod rmmod modprobe IP
13854 # LocalWords: genksyms INET loopback gatewaying ethernet PPP ARP Arp MEMSIZE
13855 # LocalWords: howto multicasting MULTICAST MBONE firewalling ipfw ACCT resp ip
13856 # LocalWords: proc acct IPIP encapsulator decapsulator klogd PCTCP RARP EXT PS
13857 # LocalWords: telnetting subnetted NAGLE rlogin NOSR ttyS TGA techinfo mbone nl
13858 # LocalWords: Mb SKB IPX Novell dosemu Appletalk DDP ATALK vmalloc visar ehome
13859 # LocalWords: SD CHR scsi thingy SG CD LUNs LUN jukebox Adaptec BusLogic EATA
13860 # LocalWords: buslogic DMA DPT ATT eata dma PIO UltraStor fdomain umsdos ext
13861 # LocalWords: QLOGIC qlogic TMC seagate Trantor ultrastor FASST wd NETDEVICES
13862 # LocalWords: unix BBS linux CSLIP PLIP Kirch's LDP CSlip SL SCC IRQ csustan
13863 # LocalWords: Turbo Laplink plip NCSA port's ReQuest IRQs EQL SMC AMD PCnet NE
13864 # LocalWords: COM ELPLUS Com EtherLinkIII VLB Arcnet Cabletron DEPCA DE carlos
13865 # LocalWords: depca EtherWorks EWRK ewrk SEEQ EtherExpress EEXPRESS NI xxx dia
13866 # LocalWords: EtherExpress WaveLAN wavelan PCLAN HPLAN VG SK Ansel Xen de ZNET
13867 # LocalWords: PCMCIA cb stanford LAN TEC RealTek ATP atp DLINK NetTools VISWS
13868 # LocalWords: TR Sony CDU caddyless cdu Mitsumi MCD cd mcd XA MultiSession CDA
13869 # LocalWords: Matsushita Panasonic SBPCD Soundblaster Longshine sbpcd Aztech
13870 # LocalWords: Okano Wearnes AZTCD CDD SE aztcd sonycd Goldstar GSCD Philips fs
13871 # LocalWords: LMS OPTCD Sanyo SJCD minix faqs xiafs XIA msdos mtools Cichocki
13872 # LocalWords: std softlinks umssync NetworkFileSharing nfsd mountd CDs HPFS TI
13873 # LocalWords: hpfs SYSV SCO iBCS Wyse WordPerfect tsx mit unixes sysv NR irisa
13874 # LocalWords: SMB WfW Cyclades async mux Logitech busmouse MouseSystem aka AST
13875 # LocalWords: PSMOUSE Compaq trackballs Travelmate Inport ATIXL ATI busmice ld
13876 # LocalWords: gpm config QIC DYNCONF FTAPE Stor Ftape ftape pcsndrv manpage NT
13877 # LocalWords: readprofile diskdrives org com masq EtherTalk tcp netrom sunacm
13878 # LocalWords: misc AIC aic pio scc Portmaster eql GIS PhotoCDs MCDX Perell PG
13879 # LocalWords: mcdx gscd optcd sjcd ISP hdparm Workgroups Lan samba PARIDE PCD
13880 # LocalWords: filesystems smbfs ATA ppp PCTech RZ www powerquest txt CMD ESDI
13881 # LocalWords: chipset FB multicast MROUTE appletalk ifconfig IBMTR multiport
13882 # LocalWords: Multisession STALDRV EasyIO EC EasyConnection ISTALLION ONboard
13883 # LocalWords: Brumby pci TNC cis ohio faq usenet NETLINK dev hydra ca Tyne mem
13884 # LocalWords: carleton Deskstation DECstation SUNFD JENSEN Noname XXXM SLiRP
13885 # LocalWords: pppd Zilog ZS SRM bootloader ez mainmenu rarp ipfwadm paride pcd
13886 # LocalWords: RTNETLINK mknod xos MTU lwared Macs mac netatalk macs cs Wolff
13887 # LocalWords: dartmouth flowerpt MultiMaster FlashPoint tudelft etherexpress
13888 # LocalWords: ICL EtherTeam ETH IDESCSI TXC SmartRAID SmartCache httpd sjc dlp
13889 # LocalWords: thesphere TwoServers BOOTP DHCP ncpfs BPQETHER BPQ MG HIPPI cern
13890 # LocalWords: bsd comp SPARCstation le SunOS ie Gracilis PackeTwin PT pt LU FX
13891 # LocalWords: FX TEAC CR LCS mS ramdisk IDETAPE cmd fperllo encis tcfs unisa
13892 # LocalWords: Vertos Genoa Funai hsfs NCP NetWare tgz APM apm ioctls UltraLite
13893 # LocalWords: TravelMate CDT LCD backlight VC RPC Mips AXP barlow cdrecord pg
13894 # LocalWords: PMAX MILO Alphas Multia Tseng linuxelf endian mipsel mips drv HT
13895 # LocalWords: kerneld callouts AdvanSys advansys Admin WDT DataStor EP verden
13896 # LocalWords: wdt hdb hdc bugfix SiS vlb Acculogic CSA DTC dtc Holtek ht QDI
13897 # LocalWords: QD qd UMC umc ALI ali lena fnet fr azstarnet cdr fb MDA ps esdi
13898 # LocalWords: Avanti XL AlphaStations Jensen DECpc AXPpci UDB Cabriolet MCA RC
13899 # LocalWords: AlphaPC mca AOUT OUTput PPro sipx gwdg lo nwe FourPort Boca unm
13900 # LocalWords: Keepalive linefill RELCOM keepalive analogue CDR conf CDI INIT
13901 # LocalWords: OPTi isp irq noisp VFAT vfat NTFS losetup dmsdosfs dosfs ISDN MP
13902 # LocalWords: NOWAYOUT behaviour dialin isdn callback BTX Teles ICN EDSS Cisco
13903 # LocalWords: ipppd syncppp RFC MPP VJ downloaded icn NICCY Creatix shmem ufr
13904 # LocalWords: ibp md ARCnet ether encap NDIS arcether ODI Amigas AmiTCP NetBSD
13905 # LocalWords: initrd tue util DES funet des OnNet BIOSP smc Travan Iomega CMS
13906 # LocalWords: FC DC dc PPA IOMEGA's ppa RNFS FMV Fujitsu ARPD arpd loran layes
13907 # LocalWords: FRAD indiana framerelay DLCI DCLIs Sangoma SDLA mrouted sync sec
13908 # LocalWords: Starmode Metricom MosquitoNet mosquitonet kbit nfsroot Digiboard
13909 # LocalWords: DIGI Xe Xeve digiboard UMISC touchscreens mtu ethernets HBAs MEX
13910 # LocalWords: Shifflett netcom js jshiffle WIC DECchip ELCP EtherPower dst RTC
13911 # LocalWords: rtc SMP lp Digi Intl RightSwitch DGRS dgrs AFFS Amiga UFS SDL AP
13912 # LocalWords: Solaris RISCom riscom syncPPP PCBIT pcbit sparc anu au artoo MFB
13913 # LocalWords: hitchcock Crynwr cnam pktdrvr NCSA's CyDROM CyCDROM FreeBSD NeXT
13914 # LocalWords: NeXTstep disklabel disklabels SMD FFS tm AmigaOS diskfiles Un IQ
13915 # LocalWords: Bernd informatik rwth aachen uae affs multihosting bytecode java
13916 # LocalWords: applets applet JDK ncsa cabi SNI Alphatronix readme LANs scarab
13917 # LocalWords: winsock RNIS caltech OSPF honour Honouring Mbit LocalTalk DEFRAG
13918 # LocalWords: localtalk download Packetwin Baycom baycom interwork ASCII JNT
13919 # LocalWords: Camtec proxying indyramp defragment defragmented UDP FAS FASXX
13920 # LocalWords: FastSCSI SIO FDC qlogicfas QLogic qlogicisp setbaycom ife ee LJ
13921 # LocalWords: ethz ch Travelmates ProAudioSpectrum ProAudio SoundMan SB SBPro
13922 # LocalWords: Thunderboard SM OPL FM ADLIB TSR Gravis MPU PSS ADI SW DSP codec
13923 # LocalWords: ADSP ESC ASIC daughtercard GUSMAX MSS NX AdLib Excell Ensoniq YM
13924 # LocalWords: SoundScape Spea MediaTriX AudioTriX WSS OTI ThunderBoard VoxWare
13925 # LocalWords: Soundscape SSCAPE TRIX MediaTrix PnP Maui dsp midixx EIA getty
13926 # LocalWords: mgetty sendfax gert greenie muc lowlevel Lasermate LanManager io
13927 # LocalWords: OOPSes trackball binghamton mobileip ncr IOMAPPED settags ns ser
13928 # LocalWords: setsync NEGO MPARITY autotuning prefetch PIIX cdwrite utils rc
13929 # LocalWords: PCWATCHDOG berkprod bitgate boldt ucsb jf kyoto jp euc Tetsuyasu
13930 # LocalWords: YAMADA tetsu cauchy nslab ntt nevod perm su doc kaf kheops wsc
13931 # LocalWords: traduc Bourgin dbourgin menuconfig kfill READMEs HOWTOs Virge WA
13932 # LocalWords: IDEDISK IDEFLOPPY EIDE firewalls QMAGIC ZMAGIC LocalWords opti
13933 # LocalWords: SVGATextMode vga svga Xkernel syr jmwobus comfaqs dhcp flakey GD
13934 # LocalWords: IPv IPng interoperability ipng ipv radio's tapr pkthome PLP nano
13935 # LocalWords: Ses Mhz sethdlc SOUNDMODEM WindowsSoundSystem smdiag pcf inka ES
13936 # LocalWords: smmixer ptt circ soundmodem MKISS FDDI DEFEA DEFPA DEFXX redhat
13937 # LocalWords: HyperNews khg mconv sed lina wuftpd MicroChannel netlink irc cum
13938 # LocalWords: raudio RealAudio PPROP NETBIOS GUI IBMMCA ELMC Racal Interlan fi
13939 # LocalWords: eth shapecfg src esp PCWD PREVSTAT bootparam sig bitwizard SBC
13940 # LocalWords: downloads AFSK TCM FP Karn KA FSK RUH LinkSys cron mouseman LLC
13941 # LocalWords: SyQuest SyQuest's CCITT MicroSolutions BPCD bpcd ESPSERIAL PROM
13942 # LocalWords: SUNESP openprom OPENPROMIO quango themall al TT MC MMU LC RMW AA
13943 # LocalWords: INSNS Ataris AutoConfig ZORRO OCS AMIFB Agnus Denise ECS CDTV GB
13944 # LocalWords: AGA Cybervision CYBER GSP TMS DMI Zorro ACSI ROMs SLM BioNet GVP
13945 # LocalWords: PAMsNet TekMagic Cyberstorm MkI CYBERSTORMII MkII BLZ onboard cx
13946 # LocalWords: Village Tronic ATARILANCE RieblCard PAMCard VME MFP sangoma LAPB
13947 # LocalWords: Rhotron BioData's Multiface AMIGAMOUSE COPCON Amiga's bitplanes
13948 # LocalWords: ATARIMOUSE MFPSER SCC's MegaSTE ESCC Atari's GVPIOEXT DMASOUND
13949 # LocalWords: fdutils cisco univercd rpcg htm iface lapb LAPBETHER tpqic qic
13950 # LocalWords: SYNTH xd en binfmt aout ipip terra ipx sd sr sg wic framebuffer
13951 # LocalWords: ibmmca lapbether mkiss dlci sdla fmv eepro eexpress ni hp ne es
13952 # LocalWords: ibmtr isofs ROMFS romfs pcxx cyclades istallion psaux msbusmouse
13953 # LocalWords: atixlmouse sbin softdog pcwd USS Lite ACI miroSOUND PCM miroPCM
13954 # LocalWords: microcontroller miro Voxware downloading teles acsi slm gvp ltpc
13955 # LocalWords: atari ariadne amigamouse atarimouse builtin IPDDP maths bradford
13956 # LocalWords: AppleTalk Farallon PhoneNet Zubkoff lnz SCCB HAPN WANs vesafb nt
13957 # LocalWords: wanrouter WANPIPE multiprotocol Mbps wanpipe EtherWORKS nodma SC
13958 # LocalWords: smp HiSax SiemensChipSet Siemens AVM Elsa ITK hisax PCC MICROR
13959 # LocalWords: Mircolink EURO DSS Spellcaster BRI sc spellcast Digiboards GPIO
13960 # LocalWords: SYMBIOS COMPAT SDMS rev ASUS Tekram HX VX API ibmmcascsi ASY asy
13961 # LocalWords: loader's PCnetPCI automounter AUTOFS amd autofs VT Gallant's Pnp
13962 # LocalWords: AEDSP aedsp enskip tik Sysctl sysctl PARPORT parport pnp IDs EPP
13963 # LocalWords: Autoprobe bart patrickr HDLS READBACK AB usr DAMA DS SparQ aten
13964 # LocalWords: Symbios PCscsi tmscsim RoamAbout GHz Hinds contrib mathematik ok
13965 # LocalWords: darmstadt okir DIGIEPCA International's Xem digiepca epca bootup
13966 # LocalWords: zorro CAPI AVMB capi avmb VP SYN syncookies EM em pc Ethertalk
13967 # LocalWords: Dayna DL Daynatalk LT PhoneNET ATB Daystar queueing CMDS SCBs ls
13968 # LocalWords: SCB STATS Thinnet ThunderLAN TLAN Netelligent NetFlex tlan james
13969 # LocalWords: caldera Preload Preloading slowdowns schoebel uni NBD nbd prog
13970 # LocalWords: stuttgart rdist TRANS hostnames mango jukeboxes ESS userland PD
13971 # LocalWords: hardlinked NAMETRANS env mtab fstab umount nologin runlevel gid
13972 # LocalWords: transname filespace adm Nodename hostname uname Kernelname bootp
13973 # LocalWords: KERNNAME kname ktype kernelname Kerneltype KERNTYPE Alt RX mdafb
13974 # LocalWords: dataless kerneltype SYSNAME Comtrol Rocketport palmtop fbset EGS
13975 # LocalWords: nvram SYSRQ SysRq PrintScreen sysrq NVRAMs NvRAM Shortwave RTTY
13976 # LocalWords: Sitor Amtor Pactor GTOR hayes TX TMOUT JFdocs HIGHMEM DAC IRQ's
13977 # LocalWords: IDEPCI IDEDMA idedma PDC pdc TRM trm raidtools luthien nuclecu
13978 # LocalWords: unam mx miguel koobera uic EMUL solaris pp ieee lpsg co DMAs TOS
13979 # LocalWords: BLDCONFIG preloading jumperless BOOTINIT modutils multipath GRE
13980 # LocalWords: misconfigured autoconfiguration IPGRE ICMP tracert ipautofw PIM
13981 # LocalWords: netis rlynch autofw ipportfw monmouth ipsubs portforwarding pimd
13982 # LocalWords: portfw PIMSM netweb usc pim pf EUI aggregatable PB decapsulate
13983 # LocalWords: ipddp Decapsulation DECAP bool HAMRADIO tcpdump af CDs tx FBCON
13984 # LocalWords: ethertap multisession PPC MMIO GDT GDTH ICP gdth hamradio bpp
13985 # LocalWords: lmh weejock AIMSlab RadioTrack RTRACK HZP OptoSCC TRX rx TRXECHO
13986 # LocalWords: DMASCC paccomm dmascc addr cfg oevsv oe kib picpar FDX baudrate
13987 # LocalWords: baudrates fdx HDX hdx PSK kanren frforum QoS SCHED CBQ SCH sched
13988 # LocalWords: sch cbq CSZ Shenker Zhang csz SFQ sfq TBF tbf PFIFO fifo PRIO RW
13989 # LocalWords: prio Micom xIO dwmw rimi OMIRR omirr omirrd unicode ntfs cmu NIC
13990 # LocalWords: Braam braam Schmidt's freiburg nls codepages codepage Romanian
13991 # LocalWords: Slovak Slovenian Sorbian Nordic iso Catalan Faeroese Galician SZ
13992 # LocalWords: Valencian Slovene Esperanto Estonian Latvian Byelorussian KOI mt
13993 # LocalWords: charset Inuit Greenlandic Sami Lappish koi SOFTCURSOR softcursor
13994 # LocalWords: Specialix specialix DTR RTS RTSCTS cycladesZ Exabyte ftape's inr
13995 # LocalWords: Iomega's LBFM claus ZFTAPE VFS zftape zft William's lzrw DFLT kb
13996 # LocalWords: MTSETBLK MTIOCTOP qft setblk zftape's tar's afio's setdrvbuffer
13997 # LocalWords: Procfs Exabyte's THR FCD sysvinit init PSC pscwdt VMIDI Euro SAB
13998 # LocalWords: Mostek Fastlane PowerMac PReP PMAC PowerPC Macintoshes Starmax
13999 # LocalWords: PowerStack Starmaxes MCOMMON DEVICETREE ATY IMS IMSTT videodev
14000 # LocalWords: BT Hauppauge STB bttv Quickcam BW BWQCAM bw qcam Mediavision PMS
14001 # LocalWords: pms Avatar Freecom Imation Superdisk BPCK bpck COMM comm DSTR ru
14002 # LocalWords: dstr EPAT EPEZ epat EPIA epia FreeCom FRPW frpw KingByte KBIC HW
14003 # LocalWords: KingByte's kbic OnSpec ValuStore FASTROUTE fastroute FLOWCONTROL
14004 # LocalWords: struct APIC realtime OSs LynxOS CNC tmp cvf HFS hfs ADFS Risc os
14005 # LocalWords: adfs ncpmount namespace SUBDIR reexport NDS kcore FT SPX spx DAT
14006 # LocalWords: interserver BLKSZ NUMBUFFERS apmd Tadpole ANA roestock QuickCam
14007 # LocalWords: isapnptools Colour CQCAM colour Connectix QuickClip prive mentre
14008 # LocalWords: KMOD kmod conformant utexas kharker UnixWare Mwave cgi cl ts ibm
14009 # LocalWords: eXchange threepio oakland simtel pre ULTRAMCA EtherLink isa luik
14010 # LocalWords: EtherLink OpenBSD pts DEVPTS devpts ptmx ttyp glibc readback SA
14011 # LocalWords: mwave OLDCARD isdnloop linklevel loopctrl Eicon Diehl DIEHLDIVA
14012 # LocalWords: ASUSCOM AsusCom TELEINT semiactiv Sedlbauer Sportster TA MIC ITH
14013 # LocalWords: NETjet NetJet Niccy Neuhaus sparcs AOC AOCD AOCE Microlink SAA
14014 # LocalWords: teletext WinTV saa iproute tc Quadra Performa PowerBook tor AUN
14015 # LocalWords: setserial compsoc steve Econet econet AUNUDP psched TEQL TLE CLS
14016 # LocalWords: teql FW Ingres TwistedPair MTRR MTRRs mtrr cfs crypto TD ktti KT
14017 # LocalWords: PHd ICS ipchains adelaide rustcorp syslog Cumana steganography
14018 # LocalWords: AcornSCSI EcoSCSI EESOX EESOXSCSI Powertec POWERTECSCSI dec SF
14019 # LocalWords: RadioReveal gatekeeper aimslab aztech FMI sf fmi RTL rtl cesdis
14020 # LocalWords: Yellowfin gsfc nasa gov yellowfin pcnet Mylex LNE lne EtherH hs
14021 # LocalWords: EBSA chattr RiscOS Winmodem AGP Atomwide DUALSP pcsp robinson CT
14022 # LocalWords: SGALAXY Waverider DSPxxx TRXPRO AudioTrix OSWF MOT CFB DSY kbps
14023 # LocalWords: tuwien kkudielk LVD mega lun MAXTAGS Gbps arcnet Olicom SKTR SNA
14024 # LocalWords: SysKonnect tms380tr sna etherboot ufs NetBEUI MultiSound MSNDCLAS GX
14025 # LocalWords: MSNDINIT MSNDPERM MSNDPIN PNDSPINI PNDSPERM Ensoniq's RetinaZ SS
14026 # LocalWords: AudioPCI lspci SonicVibes sonicvibes SPARCs roadrunner CLgen UPA
14027 # LocalWords: swansea shtml Zoltrix zoltrix BINUTILS EGCS binutils VIDC DACs
14028 # LocalWords: CyberVision Cirrus PowerBooks Topcat SBUS CGsix TurboGX BWtwo SS
14029 # LocalWords: CGthree TCX unswapable vfb fbcon hicolor truecolor AFB ILBM SOC
14030 # LocalWords: IPLAN gracilis Fibre SBus SparcSTORAGE SV jnewbigin swin QNX qnx
14031 # LocalWords: PTY PTYS ptyxx ttyxx PTYs ssh sb Avance ALS pss pvv kerneli hd
14032 # LocalWords: synth WaveFront MSND NONPNP AudioExcelDSP STRAM APUS CHRP MBX Nx
14033 # LocalWords: PowerMac's BMAC radiotrack rtrack miropcm OFFBOARD HPT UDMA DVD
14034 # LocalWords: hpt fokus gmd Cyrix DXL SLC DLC NexGen MediaGX GXm IDT WinChip
14035 # LocalWords: MMX MII valkyrie mdacon vdolive VDOLive cuseeme CU hippi rrunner
14036 # LocalWords: SeeMe ipmasqadm juanjox ipmarkfw markfw TNCs Microdyne rhine lib
14037 # LocalWords: libc jsX gamepad gameport CHF FCS FPGaming MadCatz ASSASIN GrIP
14038 # LocalWords: Assasin gamepads GamePad PDPI gamecards gamecard WingMan BSP WCS
14039 # LocalWords: ThunderPad CyberMan SideWinder ThrustMaster DirectConnect NES XF
14040 # LocalWords: Millenium SNES PSX Multisystem Nintendo PlayStation Amstrad CPC
14041 # LocalWords: Sega TurboGraFX Steffen Schwenke Multiststem PDIF FIFOSIZE EPLUS
14042 # LocalWords: PowerUP RoadRunner tahallah dos functionkey setterm imladris Woz
14043 # LocalWords: PowerMacs Winbond Algorithmics ALGOR algor ECOFF IRIX SGI SGI's
14044 # LocalWords: gfx virtualized Xpmac mklinux XFree FBDev Woodhouse mvhi Seeq fp
14045 # LocalWords: SGISEEQ HIgh ADB ADBMOUSE crosscompiler CROSSCOMPILE FPE GDB gdb
14046 # LocalWords: JOYPORT rp spoofing DawiControl NOGENSUPP EEPROM HSSI Alessandro
14047 # LocalWords: singleprocessor tex MATHEMU FRIQ Maxell friq Alcor XLT AlphaBook
14048 # LocalWords: AlphaPCI DP LX Miata Mikasa Noritake RPX UX BX Takara EV PRIMO
14049 # LocalWords: TSC Matrox Productiva matroxfb matrox multihead ia linuxhq MFW
14050 # LocalWords: mfw AAA MCS Initio XXU initio imm AutoDetect IZIP CTR usec HDLC
14051 # LocalWords: COSA SRP muni cz kas cosa Alteon AceNIC acenic VTOC OSes GMT SAx
14052 # LocalWords: Inspiron localtime INTS Thinkpads Ralf Brown's Flightstick NNN
14053 # LocalWords: Xterminator Blackhawk NN mpu ioports DCA HPDCA HPLANCE DIO Corel
14054 # LocalWords: GemTek gemtek CMDLINE IrDA PDA's irmanager irattach RR AVA DN rg
14055 # LocalWords: uit dagb irda LSAP IrLMP RR's IrLAP IR alloc skb's kfree skb's
14056 # LocalWords: GZIP IrLAN NetbeamIR ESI JetEye IrOBEX IrCOMM TTY's minicom dti
14057 # LocalWords: ircomm ircomm pluto thiguchi IrTTY Linux's bps NetWinder MIR NSC
14058 # LocalWords: ACTiSYS Dongle dongle dongles esi actisys IrMate tekram BVM MVME
14059 # LocalWords: BVME BVME WRITETHROUGH copyback writethrough fwmark syncookie tu
14060 # LocalWords: alphalinux GOBIOS csn chemnitz nat ACARD AMI MegaRAID megaraid
14061 # LocalWords: QNX4FS ISI isicom xterms Apollos VPN RCPCI rcpci sgi visws pcmcia
14062 # LocalWords: IrLPT UIRCC Tecra Strebel jstrebel suse Eichwalder ke INI INIA
14063 # LocalWords: FCP qlogicfc sym isapnp DTLK DoubleTalk rcsys dtlk DMAP SGIVW ar
14064 # LocalWords: dmabuf EcoRadio MUTEFREQ GIrBIL girbil tepkom vol mha diplom PQS
14065 # LocalWords: bmac Microgate SyncLink synclink hdlc excl ioaddr Tane tanep TCQ
14066 # LocalWords: PDS SMALLDOS charsets bigfoot kernelfr mcs cls fw rsvp SKnet sk
14067 # LocalWords: SKMC USB UHCI OHCI intel compaq usb ohci HCD Virt Compaq's hcd
14068 # LocalWords: VROOTHUB KBD ARRs MCRs NWBUTTON nwbutton NUM WaveArtist APNE cpu
14069 # LocalWords: apne blackhawke PlanB lu mlan planb NWFPE FPA nwfpe unbootable
14070 # LocalWords: FPEmulator ds vmlinux initialisation discardable pgtable PGT mdw
14071 # LocalWords: quicklist pagetable arthur StrongARM podule podules Autodetect
14072 # LocalWords: dodgy IrPORT irport Litelink litelink SuSE rtfm internet hda CY
14073 # LocalWords: multmode DriveReady SeekComplete DriveStatusError miscompile AEC
14074 # LocalWords: mainboard's Digital's alim FastTrak aec PIIXn piix Gayle Eyetech
14075 # LocalWords: Catweasel IDEDOUBLER Powerbook Centris ICSIDE RapIDE OSM HDM IOP
14076 # LocalWords: HDM's OSM's lan FibreChannel ECP autoprobe itg lbl ipmasq cjb IC
14077 # LocalWords: bieringer Caulfield's dreamtime decnet SIOCFIGCONF SIOCGIFCONF
14078 # LocalWords: rtnetlink Endnode Aironet Arlan Telxon ylenurme arlan ACB aeschi
14079 # LocalWords: Sealevel sealevel Cyclom br wanconfig tarball conectiva cycsyn
14080 # LocalWords: devel bazar cyclomx NetGear GA IBMOL Lanstreamer uhci eu efs CYZ
14081 # LocalWords: olympic linuxtr usbcore acm EZUSB downloader EFS XFS INTR op IIC
14082 # LocalWords: heine soundcore JavaStations JavaStation GemTeks TerraTec TODO
14083 # LocalWords: ActiveRadio Standalone terratec Rolf Offermanns rolf offermanns
14084 # LocalWords: Zoran ZR Buz LML CPQ DA cpqarray PPDEV deviceid vlp ppdev atyfb
14085 # LocalWords: AcceleRAID eXtremeRAID NETFILTER Netfilter masqueraded netfilter
14086 # LocalWords: kernelnotes Cardbus PCMCIA's CardBus clgenfb Permedia YAM MMAP
14087 # LocalWords: mmapped ATM atm PVCs SVCs InARP ATMARP neighbour neighbours MPOA
14088 # LocalWords: VCs ENI FPGA Tonga MMF MF UTP printks ZeitNet ZN ZATM uPD SAR PN
14089 # LocalWords: approx NICStAR NICs ForeRunnerLE Madge Collage ATMizer Dxxxx VCI
14090 # LocalWords: ServeRAID IPS ips ipslinux gzip BSDCOMP LZW RAYCS Interphase app
14091 # LocalWords: Tachyon IPHASE Surfboard NextLevel SURFboard jacksonville Tigon
14092 # LocalWords: fventuri adelphia siglercm linuxpower AceNICs Starfire starfire
14093 # LocalWords: ISOC CPiA cpia uss ACPI UDF DirectCD udf CDRW's OSF Manx acpi
14094 # LocalWords: Unixware cymru Computone IntelliPort Intelliport computone SI sx
14095 # LocalWords: adbmouse DRI DRM dlabs GMX PLCs Applicom fieldbus applicom int
14096 # LocalWords: VWSND eg ESSSOLO CFU CFNR scribed eiconctrl eicon hylafax KFPU
14097 # LocalWords: EXTRAPREC fpu mainboards KHTTPD kHTTPd khttpd Xcelerator
14098 # LocalWords: LOGIBUSMOUSE OV511 ov511 Integraphics