1 # Maintained by Axel Boldt (axel@uni-paderborn.de)
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 Pierre Tane (tanep@bigfoot.com), at
13 # http://www.traduc.org/kernelfr
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 # also includes infrastructure to support different languages.
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-2000 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, file systems, 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 the files Documentation/smp.tex, Documentation/smp.txt,
116 Documentation/i386/IO-APIC.txt, Documentation/nmi_watchdog.txt and 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 APIC (Advanced Programmable Interrupt Controller) is a scheme for
124 delivering hardware interrupt requests to the CPU. It is commonly
125 used on systems with several CPU's. If you have a single-CPU system
126 which uses APIC, you can say Y here to use it. If you say Y here
127 even though your machine doesn't have APIC, then the kernel will
128 still run with no slowdown at all.
130 If you have system with several CPU's, you do not need to say Y
131 here: APIC will be used automatically.
133 Kernel math emulation
134 CONFIG_MATH_EMULATION
135 Linux can emulate a math coprocessor (used for floating point
136 operations) if you don't have one. 486DX and Pentium processors have
137 a math coprocessor built in, 486SX and 386 do not, unless you added
138 a 487DX or 387, respectively. (The messages during boot time can
139 give you some hints here ["man dmesg"].) Everyone needs either a
140 coprocessor or this emulation.
142 If you don't have a math coprocessor, you need to say Y here; if you
143 say Y here even though you have a coprocessor, the coprocessor will
144 be used nevertheless. (This behavior can be changed with the kernel
145 command line option "no387", which comes handy if your coprocessor
146 is broken. Try "man bootparam" or see the documentation of your boot
147 loader (lilo or loadlin) about how to pass options to the kernel at
148 boot time.) This means that it is a good idea to say Y here if you
149 intend to use this kernel on different machines.
151 More information about the internals of the Linux math coprocessor
152 emulation can be found in arch/i386/math-emu/README.
154 If you are not sure, say Y; apart from resulting in a 66 KB bigger
155 kernel, it won't hurt.
157 Timer and CPU usage LEDs
159 If you say Y here, the LEDs on your machine will be used
160 to provide useful information about your current system status.
162 If you are compiling a kernel for a NetWinder or EBSA-285, you will
163 be able to select which LEDs are active using the options below. If
164 you are compiling a kernel for the EBSA-110 or the LART however, the
165 red LED will simply flash regularly to indicate that the system is
166 still functional. It is safe to say Y here if you have a CATS
167 system, but the driver will do nothing.
171 If you say Y here, one of the system LEDs (the green one on the
172 NetWinder, the amber one on the EBSA285, or the red one on the LART)
173 will flash regularly to indicate that the system is still
174 operational. This is mainly useful to kernel hackers who are
175 debugging unstable kernels.
177 The LART uses the same LED for both Timer LED and CPU usage LED
178 functions. You may choose to use both, but the Timer LED function
179 will overrule the CPU usage LED.
183 If you say Y here, the red LED will be used to give a good real
184 time indication of CPU usage, by lighting whenever the idle task
185 is not currently executing.
187 The LART uses the same LED for both Timer LED and CPU usage LED
188 functions. You may choose to use both, but the Timer LED function
189 will overrule the CPU usage LED.
191 Kernel FP software completion (EXPERIMENTAL)
193 This option is required for IEEE compliant floating point arithmetic
194 on the Alpha. The only time you would ever not say Y is to say M in
195 order to debug the code. Say Y unless you know what you are doing.
199 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
200 However, the address space of 32-bit x86 processors is only 4
201 Gigabytes large. That means that, if you have a large amount of
202 physical memory, not all of it can be "permanently mapped" by the
203 kernel. The physical memory that's not permanently mapped is called
206 If you are compiling a kernel which will never run on a machine with
207 more than 1 Gigabyte total physical RAM, answer "off" here (default
208 choice and suitable for most users). This will result in a "3GB/1GB"
209 split: 3GB are mapped so that each process sees a 3GB virtual memory
210 space and the remaining part of the 4GB virtual memory space is used
211 by the kernel to permanently map as much physical memory as
214 If the machine has between 1 and 4 Gigabytes physical RAM, then
217 If more than 4 Gigabytes is used then answer "64GB" here. This
218 selection turns Intel PAE (Physical Address Extension) mode on.
219 PAE implements 3-level paging on IA32 processors. PAE is fully
220 supported by Linux, PAE mode is implemented on all recent Intel
221 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
222 then the kernel will not boot on CPUs that don't support PAE!
224 The actual amount of total physical memory will either be
225 auto detected or can be forced by using a kernel command line option
226 such as "mem=256M". (Try "man bootparam" or see the documentation of
227 your boot loader (lilo or loadlin) about how to pass options to the
228 kernel at boot time.)
230 If unsure, say "off".
232 Normal PC floppy disk support
234 If you want to use the floppy disk drive(s) of your PC under Linux,
235 say Y. Information about this driver, especially important for IBM
236 Thinkpad users, is contained in Documentation/floppy.txt. That file
237 also contains the location of the Floppy driver FAQ as well as
238 location of the fdutils package used to configure additional
239 parameters of the driver at run time.
241 This driver is also available as a module ( = code which can be
242 inserted in and removed from the running kernel whenever you want).
243 The module will be called floppy.o. If you want to compile it as a
244 module, say M here and read Documentation/modules.txt.
246 Support for PowerMac floppy
248 If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
249 floppy controller, say Y here. Most commonly found in PowerMacs.
253 Saying Y here will allow you to use a portion of your RAM memory as
254 a block device, so that you can make file systems on it, read and
255 write to it and do all the other things that you can do with normal
256 block devices (such as hard drives). It is usually used to load and
257 store a copy of a minimal root file system off of a floppy into RAM
258 during the initial install of Linux.
260 Note that the kernel command line option "ramdisk=XX" is now
261 obsolete. For details, read Documentation/ramdisk.txt.
263 If you want to compile this as a module ( = code which can be
264 inserted in and removed from the running kernel whenever you want),
265 say M and read Documentation/modules.txt. The module will be called
268 Most normal users won't need the RAM disk functionality, and can
271 Initial RAM disk (initrd) support
272 CONFIG_BLK_DEV_INITRD
273 The initial RAM disk is a RAM disk that is loaded by the boot loader
274 (loadlin or lilo) and that is mounted as root before the normal boot
275 procedure. It is typically used to load modules needed to mount the
276 "real" root file system, etc. See Documentation/initrd.txt for
281 Saying Y here will allow you to use a regular file as a block
282 device; you can then create a file system on that block device and
283 mount it just as you would mount other block devices such as hard
284 drive partitions, CDROM drives or floppy drives. The loop devices
285 are block special device files with major number 7 and typically
286 called /dev/loop0, /dev/loop1 etc.
288 This is useful if you want to check an ISO 9660 file system before
289 burning the CD, or if you want to use floppy images without first
290 writing them to floppy. Furthermore, some Linux distributions avoid
291 the need for a dedicated Linux partition by keeping their complete
292 root file system inside a DOS FAT file using this loop device
295 The loop device driver can also be used to "hide" a file system in a
296 disk partition, floppy, or regular file, either using encryption
297 (scrambling the data) or steganography (hiding the data in the low
298 bits of, say, a sound file). This is also safe if the file resides
299 on a remote file server. If you want to do this, you will first have
300 to acquire and install a kernel patch from
301 ftp://ftp.kerneli.org/pub/kerneli/ , and then you need to
302 say Y to this option.
304 Note that alternative ways to use encrypted file systems are
305 provided by the cfs package, which can be gotten from
306 ftp://ftp.kerneli.org/pub/kerneli/net-source/ , and the newer tcfs
307 package, available at http://tcfs.dia.unisa.it/ . You do not need to
308 say Y here if you want to use one of these. However, using cfs
309 requires saying Y to "NFS file system support" below while using
310 tcfs requires applying a kernel patch. An alternative steganography
311 solution is provided by StegFS, also available from
312 ftp://ftp.kerneli.org/pub/kerneli/net-source/ .
314 To use the loop device, you need the losetup utility and a recent
315 version of the mount program, both contained in the util-linux
316 package. The location and current version number of util-linux is
317 contained in the file Documentation/Changes.
319 Note that this loop device has nothing to do with the loopback
320 device used for network connections from the machine to itself.
322 If you want to compile this driver as a module ( = code which can be
323 inserted in and removed from the running kernel whenever you want),
324 say M here and read Documentation/modules.txt. The module will be
327 Most users will answer N here.
329 Network Block Device support
331 Saying Y here will allow your computer to be a client for network
332 block devices, i.e. it will be able to use block devices exported by
333 servers (mount file systems on them etc.). Communication between
334 client and server works over TCP/IP networking, but to the client
335 program this is hidden: it looks like a regular local file access to
336 a block device special file such as /dev/nd0.
338 Network block devices also allows you to run a block-device in
339 userland (making server and client physically the same computer,
340 communicating using the loopback network device).
342 Read Documentation/nbd.txt for more information, especially about
343 where to find the server code, which runs in user space and does not
344 need special kernel support.
346 Note that this has nothing to do with the network file systems NFS
347 or Coda; you can say N here even if you intend to use NFS or Coda.
349 If you want to compile this driver as a module ( = code which can be
350 inserted in and removed from the running kernel whenever you want),
351 say M here and read Documentation/modules.txt. The module will be
356 ATA/IDE/MFM/RLL support
358 If you say Y here, your kernel will be able to manage low cost mass
359 storage units such as ATA/(E)IDE and ATAPI units. The most common
360 cases are IDE hard drives and ATAPI CDROM drives.
362 If your system is pure SCSI and doesn't use these interfaces, you
365 Integrated Disk Electronics (IDE aka ATA-1) is a connecting standard
366 for mass storage units such as hard disks. It was designed by
367 Western Digital and Compaq Computer in 1984. It was then named
368 ST506. Quite a number of disks use the IDE interface.
370 AT Attachment (ATA) is the superset of the IDE specifications.
371 ST506 was also called ATA-1.
373 Fast-IDE is ATA-2 (also named Fast ATA), Enhanced IDE (EIDE) is
374 ATA-3. It provides support for larger disks (up to 8.4GB by means of
375 the LBA standard), more disks (4 instead of 2) and for other mass
376 storage units such as tapes and cdrom. UDMA/33 (aka UltraDMA/33) is
377 ATA-4 and provides faster (and more CPU friendly) transfer modes
378 than previous PIO (Programmed processor Input/Output) from previous
379 ATA/IDE standards by means of fast DMA controllers.
381 ATA Packet Interface (ATAPI) is a protocol used by EIDE tape and
382 CDROM drives, similar in many respects to the SCSI protocol.
384 SMART IDE (Self Monitoring, Analysis and Reporting Technology) was
385 designed in order to prevent data corruption and disk crash by
386 detecting pre hardware failure conditions (heat, access time, and
387 the like...). Disks built since June 1995 may follow this
388 standard. The kernel itself don't manage this; however there are
389 quite a number of user programs such as smart that can query the
390 status of SMART parameters disk.
392 If you want to compile this driver as a module ( = code which can be
393 inserted in and removed from the running kernel whenever you want),
394 say M here and read Documentation/modules.txt. The module will be
397 For further information, please read Documentation/ide.txt.
401 Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
403 If you say Y here, you will use the full-featured IDE driver to
404 control up to ten ATA/IDE interfaces, each being able to serve a
405 "master" and a "slave" device, for a total of up to twenty ATA/IDE
406 disk/cdrom/tape/floppy drives.
408 Useful information about large (>540 MB) IDE disks, multiple
409 interfaces, what to do if ATA/IDE devices are not automatically
410 detected, sound card ATA/IDE ports, module support, and other
411 topics, is contained in Documentation/ide.txt. For detailed
412 information about hard drives, consult the Disk-HOWTO and the
413 Multi-Disk-HOWTO, available from
414 http://www.linuxdoc.org/docs.html#howto .
416 To fine-tune ATA/IDE drive/interface parameters for improved
417 performance, look for the hdparm package at
418 ftp://metalab.unc.edu/pub/Linux/kernel/patches/diskdrives/ .
420 If you want to compile this driver as a module ( = code which can be
421 inserted in and removed from the running kernel whenever you want),
422 say M here and read Documentation/modules.txt and
423 Documentation/ide.txt. The module will be called ide-mod.o. Do not
424 compile this driver as a module if your root file system (the one
425 containing the directory /) is located on an IDE device.
427 If you have one or more IDE drives, say Y or M here. If your system
428 has no IDE drives, or if memory requirements are really tight, you
429 could say N here, and select the "Old hard disk driver" below
430 instead to save about 13 KB of memory in the kernel.
432 Old hard disk (MFM/RLL/IDE) driver
433 CONFIG_BLK_DEV_HD_ONLY
434 There are two drivers for MFM/RLL/IDE hard disks. Most people use
435 the newer enhanced driver, but this old one is still around for two
436 reasons. Some older systems have strange timing problems and seem to
437 work only with the old driver (which itself does not work with some
438 newer systems). The other reason is that the old driver is smaller,
439 since it lacks the enhanced functionality of the new one. This makes
440 it a good choice for systems with very tight memory restrictions, or
441 for systems with only older MFM/RLL/ESDI drives. Choosing the old
442 driver can save 13 KB or so of kernel memory.
444 If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
445 instead of this one. For more detailed information, read the
446 Disk-HOWTO, available from
447 http://www.linuxdoc.org/docs.html#howto .
449 Use old disk-only driver on primary interface
450 CONFIG_BLK_DEV_HD_IDE
451 There are two drivers for MFM/RLL/IDE disks. Most people use just
452 the new enhanced driver by itself. This option however installs the
453 old hard disk driver to control the primary IDE/disk interface in
454 the system, leaving the new enhanced IDE driver to take care of only
455 the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from
456 having an IDE/ATAPI CDROM or tape drive connected to the primary IDE
457 interface. Choosing this option may be useful for older systems
458 which have MFM/RLL/ESDI controller+drives at the primary port
459 address (0x1f0), along with IDE drives at the secondary/3rd/4th port
462 Normally, just say N here; you will then use the new driver for all
465 Include IDE/ATA-2 DISK support
466 CONFIG_BLK_DEV_IDEDISK
467 This will include enhanced support for MFM/RLL/IDE hard disks. If
468 you have a MFM/RLL/IDE disk, and there is no special reason to use
469 the old hard disk driver instead, say Y. If you have an SCSI-only
470 system, you can say N here.
472 If you want to compile this driver as a module ( = code which can be
473 inserted in and removed from the running kernel whenever you want),
474 say M here and read Documentation/modules.txt. The module will be
475 called ide-disk.o. Do not compile this driver as a module if your
476 root file system (the one containing the directory /) is located on
477 the IDE disk. If unsure, say Y.
479 Use multi-mode by default
480 CONFIG_IDEDISK_MULTI_MODE
481 If you get this error, try to say Y here:
483 hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
484 hda: set_multmode: error=0x04 { DriveStatusError }
488 Include IDE/ATAPI CDROM support
490 If you have a CDROM drive using the ATAPI protocol, say Y. ATAPI is
491 a newer protocol used by IDE CDROM and TAPE drives, similar to the
492 SCSI protocol. Most new CDROM drives use ATAPI, including the
493 NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
494 double(2X) or better speed drives.
496 If you say Y here, the CDROM drive will be identified at boot time
497 along with other IDE devices, as "hdb" or "hdc", or something
498 similar (check the boot messages with dmesg). If this is your only
499 CDROM drive, you can say N to all other CDROM options, but be sure
500 to say Y or M to "ISO 9660 CDROM file system support".
502 Read the CDROM-HOWTO, available from
503 http://www.linuxdoc.org/docs.html#howto and the file
504 Documentation/cdrom/ide-cd. Note that older versions of lilo (the
505 Linux boot loader) cannot properly deal with IDE/ATAPI CDROMs, so
506 install lilo-16 or higher, available from
507 ftp://metalab.unc.edu/pub/Linux/system/boot/lilo .
509 If you want to compile the driver as a module ( = code which can be
510 inserted in and removed from the running kernel whenever you want),
511 say M here and read Documentation/modules.txt. The module will be
514 Include IDE/ATAPI TAPE support
515 CONFIG_BLK_DEV_IDETAPE
516 If you have an IDE tape drive using the ATAPI protocol, say Y.
517 ATAPI is a newer protocol used by IDE tape and CDROM drives, similar
518 to the SCSI protocol. If you have an SCSI tape drive however, you
521 You should also say Y if you have an OnStream DI-30 tape drive; this
522 will not work with the SCSI protocol, until there is support for the
523 SC-30 and SC-50 versions.
525 If you say Y here, the tape drive will be identified at boot time
526 along with other IDE devices, as "hdb" or "hdc", or something
527 similar, and will be mapped to a character device such as "ht0"
528 (check the boot messages with dmesg). Be sure to consult the
529 drivers/ide/ide-tape.c and Documentation/ide.txt files for usage
532 If you want to compile the driver as a module ( = code which can be
533 inserted in and removed from the running kernel whenever you want),
534 say M here and read Documentation/modules.txt. The module will be
537 Include IDE/ATAPI FLOPPY support
538 CONFIG_BLK_DEV_IDEFLOPPY
539 If you have an IDE floppy drive which uses the ATAPI protocol,
540 answer Y. ATAPI is a newer protocol used by IDE CDROM/tape/floppy
541 drives, similar to the SCSI protocol.
543 The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by
544 this driver. For information about jumper settings and the question
545 of when a ZIP drive uses a partition table, see
546 http://www.win.tue.nl/~aeb/linux/zip/zip-1.html .
547 (ATAPI PD-CD/CDR drives are not supported by this driver; support
548 for PD-CD/CDR drives is available if you answer Y to
549 "SCSI emulation support", below).
551 If you say Y here, the FLOPPY drive will be identified along with
552 other IDE devices, as "hdb" or "hdc", or something similar (check
553 the boot messages with dmesg).
555 If you want to compile the driver as a module ( = code which can be
556 inserted in and removed from the running kernel whenever you want),
557 say M here and read Documentation/modules.txt. The module will be
560 SCSI emulation support
561 CONFIG_BLK_DEV_IDESCSI
562 This will provide SCSI host adapter emulation for IDE ATAPI devices,
563 and will allow you to use a SCSI device driver instead of a native
566 This is useful if you have an ATAPI device for which no native
567 driver has been written (for example, an ATAPI PD-CD or CDR drive);
568 you can then use this emulation together with an appropriate SCSI
569 device driver. In order to do this, say Y here and to "SCSI support"
570 and "SCSI generic support", below. You must then provide the kernel
571 command line "hdx=scsi" (try "man bootparam" or see the
572 documentation of your boot loader (lilo or loadlin) about how to
573 pass options to the kernel at boot time) for devices if you want the
574 native EIDE sub-drivers to skip over the native support, so that
575 this SCSI emulation can be used instead. This is required for use of
578 Note that this option does NOT allow you to attach SCSI devices to a
579 box that doesn't have a SCSI host adapter installed.
581 If both this SCSI emulation and native ATAPI support are compiled
582 into the kernel, the native support will be used.
585 CONFIG_BLK_DEV_ISAPNP
586 If you have an ISA EIDE card that is PnP (Plug and Play) and
587 requires setup first before scanning for devices, say Y here.
591 CMD640 chipset bugfix/support
592 CONFIG_BLK_DEV_CMD640
593 The CMD-Technologies CMD640 IDE chip is used on many common 486 and
594 Pentium motherboards, usually in combination with a "Neptune" or
595 "SiS" chipset. Unfortunately, it has a number of rather nasty
596 design flaws that can cause severe data corruption under many common
597 conditions. Say Y here to include code which tries to automatically
598 detect and correct the problems under Linux. This option also
599 enables access to the secondary IDE ports in some CMD640 based
602 This driver will work automatically in PCI based systems (most new
603 systems have PCI slots). But if your system uses VESA local bus
604 (VLB) instead of PCI, you must also supply a kernel boot parameter
605 to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man
606 bootparam" or see the documentation of your boot loader about how to
607 pass options to the kernel.)
609 The CMD640 chip is also used on add-in cards by Acculogic, and on
610 the "CSA-6400E PCI to IDE controller" that some people have. For
611 details, read Documentation/ide.txt.
613 CMD640 enhanced support
614 CONFIG_BLK_DEV_CMD640_ENHANCED
615 This option includes support for setting/autotuning PIO modes and
616 prefetch on CMD640 IDE interfaces. For details, read
617 Documentation/ide.txt. If you have a CMD640 IDE interface and your
618 BIOS does not already do this for you, then say Y here. Otherwise
621 RZ1000 chipset bugfix/support
622 CONFIG_BLK_DEV_RZ1000
623 The PC-Technologies RZ1000 IDE chip is used on many common 486 and
624 Pentium motherboards, usually along with the "Neptune" chipset.
625 Unfortunately, it has a rather nasty design flaw that can cause
626 severe data corruption under many conditions. Say Y here to include
627 code which automatically detects and corrects the problem under
628 Linux. This may slow disk throughput by a few percent, but at least
629 things will operate 100% reliably.
631 Generic PCI IDE chipset support
632 CONFIG_BLK_DEV_IDEPCI
633 Say Y here for PCI systems which use IDE drive(s).
634 This option helps the IDE driver to automatically detect and
635 configure all PCI-based IDE interfaces in your system.
637 Support for sharing PCI IDE interrupts
638 CONFIG_IDEPCI_SHARE_IRQ
639 Some ATA/IDE chipsets have hardware support which allows for
640 sharing a single IRQ with other cards. To enable support for
641 this in the ATA/IDE driver, say Y here.
643 It is safe to say Y to this question, in most cases.
646 Generic PCI bus-master DMA support
647 CONFIG_BLK_DEV_IDEDMA_PCI
648 If your PCI system uses IDE drive(s) (as opposed to SCSI, say) and
649 is capable of bus-master DMA operation (most Pentium PCI systems),
650 you will want to say Y here to reduce CPU overhead. You can then use
651 the "hdparm" utility to enable DMA for drives for which it was not
652 enabled automatically. By default, DMA is not enabled automatically
653 for these drives, but you can change that by saying Y to the
654 following question "Use DMA by default when available". You can get
655 the latest version of the hdparm utility from
656 ftp://metalab.unc.edu/pub/Linux/system/hardware/ .
658 Read the comments at the beginning of drivers/ide/ide-dma.c and
659 the file Documentation/ide.txt for more information.
661 It is safe to say Y to this question.
663 Good-Bad DMA Model-Firmware (EXPERIMENTAL)
664 CONFIG_IDEDMA_NEW_DRIVE_LISTINGS
665 If you say Y here, the model and firmware revision of your drive
666 will be compared against a blacklist of buggy drives that claim to
667 be (U)DMA capable but aren't. This is a blanket on/off test with no
670 Straight GNU GCC 2.7.3/2.8.X compilers are known to be safe;
671 whereas, many versions of EGCS have a problem and miscompile if you
676 Boot off-board chipsets first support
677 CONFIG_BLK_DEV_OFFBOARD
678 Normally, IDE controllers built into the motherboard (on-board
679 controllers) are assigned to ide0 and ide1 while those on add-in PCI
680 cards (off-board controllers) are relegated to ide2 and ide3.
681 Answering Y here will allow you to reverse the situation, with
682 off-board controllers on ide0/1 and on-board controllers on ide2/3.
683 This can improve the usability of some boot managers such as lilo
684 when booting from a drive on an off-board controller.
686 If you say Y here, and you actually want to reverse the device scan
687 order as explained above, you also need to issue the kernel command
688 line option "ide=reverse". (Try "man bootparam" or see the
689 documentation of your boot loader (lilo or loadlin) about how to
690 pass options to the kernel at boot time.)
692 Note that, if you do this, the order of the hd* devices will be
693 rearranged which may require modification of fstab and other files.
697 Use DMA by default when available
698 CONFIG_IDEDMA_PCI_AUTO
699 Prior to kernel version 2.1.112, Linux used to automatically use
700 DMA for IDE drives and chipsets which support it. Due to concerns
701 about a couple of cases where buggy hardware may have caused damage,
702 the default is now to NOT use DMA automatically. To revert to the
703 previous behaviour, say Y to this question.
705 If you suspect your hardware is at all flakey, say N here.
706 Do NOT email the IDE kernel people regarding this issue!
708 It is normally safe to answer Y to this question unless your
709 motherboard uses a VIA VP2 chipset, in which case you should say N.
711 IGNORE word93 Validation BITS
713 Since various rules were applied and created ... et al. as it relates
714 the detection of vaild cable signals. This is a result of unclear terms
715 in ATA-4 and ATA-5 standards.
717 It is normally safe to answer Y; however, the default is N.
719 Various ATA, Work(s) In Progress (EXPERIMENTAL)
720 CONFIG_IDEDMA_PCI_WIP
721 If you enable this you will be able to use and test highly
722 developmental projects. If you say N, this configure script will
723 simply skip those options.
725 It is SAFEST to say N to this question.
727 3ware Hardware ATA-RAID support
728 CONFIG_BLK_DEV_3W_XXXX_RAID
729 3ware is the only hardware ATA-Raid product in Linux to date.
730 This card is 2,4, or 8 channel master mode support only.
731 SCSI support required!!!
733 http://www.3ware.com/
735 Please read the comments at the top of drivers/scsi/3w-xxxx.c
737 AEC62XX chipset support
738 CONFIG_BLK_DEV_AEC62XX
739 This driver adds up to 4 more EIDE devices sharing a single
740 interrupt. This add-on card is a bootable PCI UDMA controller. In
741 order to get this card to initialize correctly in some cases, you
742 should say Y here, and preferably also to "Use DMA by default when
745 The ATP850U/UF is an UltraDMA 33 chipset base.
746 The ATP860 is an UltraDMA 66 chipset base.
747 The ATP860M(acintosh) version is an UltraDMA 66 chipset base.
749 Please read the comments at the top of drivers/ide/aec62xx.c
750 If you say Y here, then say Y to "Use DMA by default when available" as
753 AEC62XX Tuning support
754 CONFIG_AEC62XX_TUNING
755 Please read the comments at the top of drivers/ide/aec62xx.c
758 ALI M15x3 chipset support
759 CONFIG_BLK_DEV_ALI15X3
760 This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C
761 onboard chipsets. It also tests for Simplex mode and enables
762 normal dual channel support.
764 If you say Y here, you also need to say Y to "Use DMA by default
765 when available", above.
766 Please read the comments at the top of drivers/ide/alim15x3.c
770 ALI M15x3 WDC support (DANGEROUS)
772 This allows for UltraDMA support for WDC drives that ignore CRC
773 checking. You are a fool for enabling this option, but there have
774 been requests. DO NOT COMPLAIN IF YOUR DRIVE HAS FS CORRUPTION, IF
775 YOU ENABLE THIS! No one will listen, just laugh for ignoring this
778 Using this option can allow WDC drives to run at ATA-4/5 transfer
779 rates with only an ATA-2 support structure.
783 AMD7409 chipset support
784 CONFIG_BLK_DEV_AMD7409
785 This driver ensures (U)DMA support for the AMD756 Viper chipset.
787 If you say Y here, you also need to say Y to "Use DMA by default
788 when available", above.
789 Please read the comments at the top of drivers/ide/amd7409.c
793 AMD Viper ATA-66 Override support (WIP)
794 CONFIG_AMD7409_OVERRIDE
795 This option auto-forces the ata66 flag.
796 This effect can be also invoked by calling "idex=ata66"
799 CMD64X chipset support
800 CONFIG_BLK_DEV_CMD64X
801 Say Y here if you have an IDE controller which uses any of these
802 chipsets: CMD643, CMD646, or CMD648.
804 CY82C693 chipset support
805 CONFIG_BLK_DEV_CY82C693
806 This driver adds detection and support for the CY82C693 chipset
807 used on Digital's PC-Alpha 164SX boards.
809 If you say Y here, you need to say Y to "Use DMA by default
810 when available" as well.
812 Cyrix CS5530 MediaGX chipset support
813 CONFIG_BLK_DEV_CS5530
814 Include support for UDMA on the Cyrix MediaGX 5530 chipset. This
815 will automatically be detected and configured if found.
817 It is safe to say Y to this question.
819 People with SCSI-only systems should say N here. If unsure, say Y.
821 HPT34X chipset support
822 CONFIG_BLK_DEV_HPT34X
823 This driver adds up to 4 more EIDE devices sharing a single
824 interrupt. The HPT343 chipset in its current form is a non-bootable
825 controller; the HPT345/HPT363 chipset is a bootable (needs BIOS FIX)
826 PCI UDMA controllers. This driver requires dynamic tuning of the
827 chipset during the ide-probe at boot time. It is reported to support
828 DVD II drives, by the manufacturer.
830 HPT34X AUTODMA support (WIP)
831 CONFIG_HPT34X_AUTODMA
832 This is a dangerous thing to attempt currently! Please read the
833 comments at the top of drivers/ide/hpt34x.c If you say Y here,
834 then say Y to "Use DMA by default when available" as well.
838 HPT366 chipset support
839 CONFIG_BLK_DEV_HPT366
840 HPT366 is an Ultra DMA chipset for ATA-66.
841 HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
842 HPT370 is an Ultra DMA chipset for ATA-100.
844 This driver adds up to 4 more EIDE devices sharing a single
847 The HPT366 chipset in its current form is bootable. One solution
848 for this problem are special LILO commands for redirecting the
849 reference to device 0x80. The other solution is to say Y to "Boot
850 off-board chipsets first support" (CONFIG_BLK_DEV_OFFBOARD) unless
851 your mother board has the chipset natively mounted. Regardless one
852 should use the fore mentioned option and call at LILO or include
853 "ide=reverse" in LILO's append-line.
855 This driver requires dynamic tuning of the chipset during the
856 ide-probe at boot. It is reported to support DVD II drives, by the
859 NS87415 support (EXPERIMENTAL)
860 CONFIG_BLK_DEV_NS87415
861 This driver adds detection and support for the NS87415 chip
862 (used in SPARC64, among others).
864 Please read the comments at the top of drivers/ide/ns87415.c.
866 OPTi 82C621 enhanced support (EXPERIMENTAL)
867 CONFIG_BLK_DEV_OPTI621
868 This is a driver for the OPTi 82C621 EIDE controller.
869 Please read the comments at the top of drivers/ide/opti621.c.
871 ServerWorks OSB4 chipset support (EXPERIMENTAL)
873 This driver adds PIO/DMA support for the Serverworks OSB4 chipset
875 Intel PIIXn chipsets support
877 This driver adds PIO mode setting and tuning for all PIIX IDE
878 controllers by Intel. Since the BIOS can sometimes improperly tune
879 PIO 0-4 mode settings, this allows dynamic tuning of the chipset
880 via the standard end-user tool 'hdparm'.
882 Please read the comments at the top of drivers/ide/piix.c.
884 If you say Y here, you should also say Y to "PIIXn Tuning support",
891 This driver extension adds DMA mode setting and tuning for all PIIX
892 IDE controllers by Intel. Since the BIOS can sometimes improperly
893 set up the device/adapter combination and speed limits, it has
894 become a necessity to back/forward speed devices as needed.
896 Case 430HX/440FX PIIX3 need speed limits to reduce UDMA to DMA mode
897 2 if the BIOS can not perform this task at initialization.
901 PROMISE PDC20246/PDC20262/PDC20267 support
902 CONFIG_BLK_DEV_PDC202XX
903 Promise Ultra33 or PDC20246
904 Promise Ultra66 or PDC20262
905 Promise Ultra100 or PDC20265/PDC20267
907 This driver adds up to 4 more EIDE devices sharing a single
908 interrupt. This add-on card is a bootable PCI UDMA controller. Since
909 multiple cards can be installed and there are BIOS ROM problems that
910 happen if the BIOS revisions of all installed cards (three-max) do
911 not match, the driver attempts to do dynamic tuning of the chipset
912 at boot-time for max-speed. Ultra33 BIOS 1.25 or newer is required
913 for more than one card. This card may require that you say Y to
914 "Special UDMA Feature (EXPERIMENTAL)".
916 If you say Y here, you need to say Y to "Use DMA by default when
919 Please read the comments at the top of drivers/ide/pdc202xx.c
923 Special UDMA Feature (EXPERIMENTAL)
924 CONFIG_PDC202XX_BURST
925 For PDC20246, PDC20262, PDC20265 and PDC20267 Ultra DMA chipsets.
926 Designed originally for PDC20246/Ultra33 that has BIOS setup
927 failures when using 3 or more cards.
929 Unknown for PDC20265/PDC20267 Ultra DMA 100.
931 Please read the comments at the top of drivers/ide/pdc202xx.c
935 SiS5513 chipset support
936 CONFIG_BLK_DEV_SIS5513
937 This driver ensures (U)DMA support for SIS5513 chipset based
938 mainboards. SiS620/530 UDMA mode 4, SiS5600/5597 UDMA mode 2, all
939 other DMA mode 2 limited chipsets are unsupported to date.
941 If you say Y here, you need to say Y to "Use DMA by default when
944 Please read the comments at the top of drivers/ide/sis5513.c
946 SLC90E66 chipset support
947 CONFIG_BLK_DEV_SLC90E66
948 This driver ensures (U)DMA support for Victroy66 SouthBridges for
949 SMsC with Intel NorthBridges. This is an Ultra66 based chipset.
950 The nice thing about it is that you can mix Ultra/DMA/PIO devices
951 and it will handle timing cycles. Since this is an improved look-a-like
952 to the PIIX4 it should be a nice addition.
954 If you say Y here, you need to say Y to "Use DMA by default when
957 Please read the comments at the top of drivers/ide/slc90e66.c
959 Winbond SL82c105 support
960 CONFIG_BLK_DEV_SL82C105
961 If you have a Winbond SL82c105 IDE controller, say Y here to enable
962 special configuration for this chip. This is common on various CHRP
963 motherboards, but could be used elsewhere. If in doubt, say Y.
965 Tekram TRM290 chipset support (EXPERIMENTAL)
966 CONFIG_BLK_DEV_TRM290
967 This driver adds support for bus master DMA transfers
968 using the Tekram TRM290 PCI IDE chip. Volunteers are
969 needed for further tweaking and development.
970 Please read the comments at the top of drivers/ide/trm290.c.
972 VIA82CXXX chipset support
973 CONFIG_BLK_DEV_VIA82CXXX
974 This allows you to to configure your chipset for a better use while
975 running (U)DMA: it will allow you to enable efficiently the second
976 channel dma usage, as it may not be set by BIOS. It allows you to
977 pass a kernel command line at boot time in order to set fifo
978 config. If no command line is provided, it will try to set fifo
979 configuration at its best. It will allow you to get information from
980 /proc/ide/via provided you enabled "proc" support.
982 Please read the comments at the top of drivers/ide/via82cxxx.c
984 If you say Y here, then say Y to "Use DMA by default when available"
989 VIA82CXXX Tuning support (WIP)
990 CONFIG_VIA82CXXX_TUNING
991 Please read the comments at the top of drivers/ide/via82cxxx.c
995 Other IDE chipset support
997 Say Y here if you want to include enhanced support for various IDE
998 interface chipsets used on motherboards and add-on cards. You can
999 then pick your particular IDE chip from among the following options.
1000 This enhanced support may be necessary for Linux to be able to
1001 access the 3rd/4th drives in some systems. It may also enable
1002 setting of higher speed I/O rates to improve system performance with
1003 these chipsets. Most of these also require special kernel boot
1004 parameters to actually turn on the support at runtime; you can find
1005 a list of these in the file Documentation/ide.txt.
1007 People with SCSI-only systems can say N here.
1009 Generic 4 drives/port support
1010 CONFIG_BLK_DEV_4DRIVES
1011 Certain older chipsets, including the Tekram 690CD, use a single set
1012 of I/O ports at 0x1f0 to control up to four drives, instead of the
1013 customary two drives per port. Support for this can be enabled at
1014 runtime using the "ide0=four" kernel boot parameter if you say Y
1018 CONFIG_BLK_DEV_ALI14XX
1019 This driver is enabled at runtime using the "ide0=ali14xx" kernel
1020 boot parameter. It enables support for the secondary IDE interface
1021 of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
1022 I/O speeds to be set as well. See the files Documentation/ide.txt
1023 and drivers/ide/ali14xx.c for more info.
1026 CONFIG_BLK_DEV_DTC2278
1027 This driver is enabled at runtime using the "ide0=dtc2278" kernel
1028 boot parameter. It enables support for the secondary IDE interface
1029 of the DTC-2278 card, and permits faster I/O speeds to be set as
1030 well. See the Documentation/ide.txt and drivers/ide/dtc2278.c
1031 files for more info.
1033 Holtek HT6560B support
1034 CONFIG_BLK_DEV_HT6560B
1035 This driver is enabled at runtime using the "ide0=ht6560b" kernel
1036 boot parameter. It enables support for the secondary IDE interface
1037 of the Holtek card, and permits faster I/O speeds to be set as well.
1038 See the Documentation/ide.txt and drivers/ide/ht6560b.c files for
1041 PROMISE DC4030 support (EXPERIMENTAL)
1042 CONFIG_BLK_DEV_PDC4030
1043 This driver provides support for the secondary IDE interface and
1044 cache of Promise IDE chipsets, e.g. DC4030 and DC5030. This driver
1045 is known to incur timeouts/retries during heavy I/O to drives
1046 attached to the secondary interface. CDROM and TAPE devices are not
1047 supported yet. This driver is enabled at runtime using the
1048 "ide0=dc4030" kernel boot parameter. See the Documentation/ide.txt
1049 and drivers/ide/pdc4030.c files for more info.
1052 CONFIG_BLK_DEV_QD6580
1053 This driver is enabled at runtime using the "ide0=qd6580" kernel
1054 boot parameter. It permits faster I/O speeds to be set. See the
1055 files Documentation/ide.txt and drivers/ide/qd6580.c for more
1059 CONFIG_BLK_DEV_UMC8672
1060 This driver is enabled at runtime using the "ide0=umc8672" kernel
1061 boot parameter. It enables support for the secondary IDE interface
1062 of the UMC-8672, and permits faster I/O speeds to be set as well.
1063 See the files Documentation/ide.txt and drivers/ide/umc8672.c for
1066 Amiga builtin Gayle IDE interface support
1067 CONFIG_BLK_DEV_GAYLE
1068 This is the IDE driver for the builtin IDE interface on some Amiga
1069 models. It supports both the `A1200 style' (used in A600 and A1200)
1070 and `A4000 style' (used in A4000 and A4000T) of the Gayle IDE
1071 interface. Say Y if you have such an Amiga model and want to use IDE
1072 devices (hard disks, CD-ROM drives, etc.) that are connected to the
1073 builtin IDE interface.
1075 Falcon IDE interface support
1076 CONFIG_BLK_DEV_FALCON_IDE
1077 This is the IDE driver for the builtin IDE interface on the Atari
1078 Falcon. Say Y if you have a Falcon and want to use IDE devices (hard
1079 disks, CD-ROM drives, etc.) that are connected to the builtin IDE
1082 Amiga Buddha/Catweasel IDE interface support (EXPERIMENTAL)
1083 CONFIG_BLK_DEV_BUDDHA
1084 This is the IDE driver for the IDE interfaces on the Buddha and
1085 Catweasel expansion boards. It supports up to two interfaces on the
1086 Buddha and three on the Catweasel.
1088 Say Y if you have a Buddha or Catweasel expansion board and want to
1089 use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
1090 to one of its IDE interfaces.
1092 Amiga IDE Doubler support (EXPERIMENTAL)
1093 CONFIG_BLK_DEV_IDEDOUBLER
1094 This driver provides support for the so-called `IDE doublers' (made
1095 by various manufacturers, e.g. Eyetech) that can be connected to the
1096 builtin IDE interface of some Amiga models. Using such an IDE
1097 doubler, you can connect up to four instead of two IDE devices on
1098 the Amiga's builtin IDE interface.
1100 Note that the normal Amiga Gayle IDE driver may not work correctly
1101 if you have an IDE doubler and don't enable this driver!
1103 Say Y if you have an IDE doubler. The driver is enabled at kernel
1104 runtime using the "ide=doubler" kernel boot parameter.
1106 Support for PowerMac IDE devices (must also enable IDE)
1107 CONFIG_BLK_DEV_IDE_PMAC
1108 This driver provides support for the built-in IDE controller on most
1109 of the recent Apple Power Macintoshes and PowerBooks.
1112 PowerMac IDE DMA support
1113 CONFIG_BLK_DEV_IDEDMA_PMAC
1114 This option allows the driver for the built-in IDE controller on
1115 Power Macintoshes and PowerBooks to use DMA (direct memory access)
1116 to transfer data to and from memory. Saying Y is safe and improves
1120 CONFIG_BLK_DEV_IDEDMA_PMAC_AUTO
1121 This option allows the driver for the built-in IDE controller on
1122 Power Macintoshes and PowerBooks to use DMA automatically, without
1123 it having to be explicitly enabled. This option is provided because
1124 of concerns about a couple of cases where using DMA on buggy PC
1125 hardware may have caused damage. Saying Y should be safe on all
1128 Macintosh Quadra/Powerbook IDE interface support
1129 CONFIG_BLK_DEV_MAC_IDE
1130 This is the IDE driver for the builtin IDE interface on some m68k
1131 Macintosh models. It supports both the `Quadra style' (used in
1132 Quadra/ Centris 630 and Performa 588 models) and `Powerbook style'
1133 (used in the Powerbook 150 and 190 models) IDE interface.
1135 Say Y if you have such an Macintosh model and want to use IDE
1136 devices (hard disks, CD-ROM drives, etc.) that are connected to the
1137 builtin IDE interface.
1139 ICS IDE interface support
1140 CONFIG_BLK_DEV_IDE_ICSIDE
1141 On Acorn systems, say Y here if you wish to use the ICS IDE
1142 interface card. This is not required for ICS partition support.
1143 If you are unsure, say N to this.
1146 CONFIG_BLK_DEV_IDEDMA_ICS
1147 Say Y here if you want to add DMA (Direct Memory Access) support to
1150 Use ICS DMA by default
1151 CONFIG_IDEDMA_ICS_AUTO
1152 Prior to kernel version 2.1.112, Linux used to automatically use
1153 DMA for IDE drives and chipsets which support it. Due to concerns
1154 about a couple of cases where buggy hardware may have caused damage,
1155 the default is now to NOT use DMA automatically. To revert to the
1156 previous behaviour, say Y to this question.
1158 If you suspect your hardware is at all flakey, say N here.
1159 Do NOT email the IDE kernel people regarding this issue!
1161 XT hard disk support
1163 Very old 8 bit hard disk controllers used in the IBM XT computer
1164 will be supported if you say Y here.
1166 If you want to compile the driver as a module ( = code which can be
1167 inserted in and removed from the running kernel whenever you want),
1168 say M here and read Documentation/modules.txt. The module will be
1171 It's pretty unlikely that you have one of these: say N.
1173 PS/2 ESDI hard disk support
1175 Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
1178 If you want to compile the driver as a module ( = code which can be
1179 inserted in and removed from the running kernel whenever you want),
1180 say M here and read Documentation/modules.txt. The module will be
1183 Mylex DAC960/DAC1100 PCI RAID Controller support
1184 CONFIG_BLK_DEV_DAC960
1185 This driver adds support for the Mylex DAC960, AcceleRAID, and
1186 eXtremeRAID PCI RAID controllers. See the file
1187 Documentation/README.DAC960 for further information about this
1190 If you want to compile the driver as a module ( = code which can be
1191 inserted in and removed from the running kernel whenever you want),
1192 say M here and read Documentation/modules.txt. The module will be
1195 Parallel port IDE device support
1197 There are many external CD-ROM and disk devices that connect through
1198 your computer's parallel port. Most of them are actually IDE devices
1199 using a parallel port IDE adapter. This option enables the PARIDE
1200 subsystem which contains drivers for many of these external drives.
1201 Read Documentation/paride.txt for more information.
1203 If you have said Y to the "Parallel-port support" configuration
1204 option, you may share a single port between your printer and other
1205 parallel port devices. Answer Y to build PARIDE support into your
1206 kernel, or M if you would like to build it as a loadable module. If
1207 your parallel port support is in a loadable module, you must build
1208 PARIDE as a module. If you built PARIDE support into your kernel,
1209 you may still build the individual protocol modules and high-level
1210 drivers as loadable modules. If you build this support as a module,
1211 it will be called paride.o.
1213 To use the PARIDE support, you must say Y or M here and also to at
1214 least one high-level driver (e.g. "Parallel port IDE disks",
1215 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
1216 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
1217 "MicroSolutions backpack protocol", "DataStor Commuter protocol"
1220 Parallel port IDE disks
1222 This option enables the high-level driver for IDE-type disk devices
1223 connected through a parallel port. If you chose to build PARIDE
1224 support into your kernel, you may answer Y here to build in the
1225 parallel port IDE driver, otherwise you should answer M to build
1226 it as a loadable module. The module will be called pd.o. You
1227 must also have at least one parallel port protocol driver in your
1228 system. Among the devices supported by this driver are the SyQuest
1229 EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack
1230 hard drives from MicroSolutions.
1232 Parallel port ATAPI CD-ROMs
1234 This option enables the high-level driver for ATAPI CD-ROM devices
1235 connected through a parallel port. If you chose to build PARIDE
1236 support into your kernel, you may answer Y here to build in the
1237 parallel port ATAPI CD-ROM driver, otherwise you should answer M to
1238 build it as a loadable module. The module will be called pcd.o. You
1239 must also have at least one parallel port protocol driver in your
1240 system. Among the devices supported by this driver are the
1241 MicroSolutions backpack CD-ROM drives and the Freecom Power CD. If
1242 you have such a CD-ROM drive, you should also say Y or M to "ISO
1243 9660 CDROM file system support" below, because that's the file
1244 system used on CDROMs.
1246 Parallel port ATAPI disks
1248 This option enables the high-level driver for ATAPI disk devices
1249 connected through a parallel port. If you chose to build PARIDE
1250 support into your kernel, you may answer Y here to build in the
1251 parallel port ATAPI disk driver, otherwise you should answer M
1252 to build it as a loadable module. The module will be called pf.o.
1253 You must also have at least one parallel port protocol driver in
1254 your system. Among the devices supported by this driver are the
1255 MicroSolutions backpack PD/CD drive and the Imation Superdisk
1258 Parallel port ATAPI tapes
1260 This option enables the high-level driver for ATAPI tape devices
1261 connected through a parallel port. If you chose to build PARIDE
1262 support into your kernel, you may answer Y here to build in the
1263 parallel port ATAPI disk driver, otherwise you should answer M
1264 to build it as a loadable module. The module will be called pt.o.
1265 You must also have at least one parallel port protocol driver in
1266 your system. Among the devices supported by this driver is the
1267 parallel port version of the HP 5GB drive.
1269 Parallel port generic ATAPI devices
1271 This option enables a special high-level driver for generic ATAPI
1272 devices connected through a parallel port. The driver allows user
1273 programs, such as cdrecord, to send ATAPI commands directly to a
1276 If you chose to build PARIDE support into your kernel, you may
1277 answer Y here to build in the parallel port generic ATAPI driver,
1278 otherwise you should answer M to build it as a loadable module. The
1279 module will be called pg.o.
1281 You must also have at least one parallel port protocol driver in
1284 This driver implements an API loosely related to the generic SCSI
1285 driver. See include/linux/pg.h for details.
1287 You can obtain the most recent version of cdrecord from
1288 ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/ . Versions 1.6.1a3 and
1289 later fully support this driver.
1291 ATEN EH-100 protocol
1293 This option enables support for the ATEN EH-100 parallel port IDE
1294 protocol. This protocol is used in some inexpensive low performance
1295 parallel port kits made in Hong Kong. If you chose to build PARIDE
1296 support into your kernel, you may answer Y here to build in the
1297 protocol driver, otherwise you should answer M to build it as a
1298 loadable module. The module will be called aten.o. You must also
1299 have a high-level driver for the type of device that you want to
1302 MicroSolutions backpack protocol
1304 This option enables support for the MicroSolutions backpack parallel
1305 port IDE protocol. If you chose to build PARIDE support into your
1306 kernel, you may answer Y here to build in the protocol driver,
1307 otherwise you should answer M to build it as a loadable module. The
1308 module will be called bpck.o. You must also have a high-level driver
1309 for the type of device that you want to support.
1311 DataStor Commuter protocol
1313 This option enables support for the Commuter parallel port IDE
1314 protocol from DataStor. If you chose to build PARIDE support
1315 into your kernel, you may answer Y here to build in the protocol
1316 driver, otherwise you should answer M to build it as a loadable
1317 module. The module will be called comm.o. You must also have
1318 a high-level driver for the type of device that you want to support.
1320 DataStor EP-2000 protocol
1322 This option enables support for the EP-2000 parallel port IDE
1323 protocol from DataStor. If you chose to build PARIDE support
1324 into your kernel, you may answer Y here to build in the protocol
1325 driver, otherwise you should answer M to build it as a loadable
1326 module. The module will be called dstr.o. You must also have
1327 a high-level driver for the type of device that you want to support.
1329 Shuttle EPAT/EPEZ protocol
1331 This option enables support for the EPAT parallel port IDE protocol.
1332 EPAT is a parallel port IDE adapter manufactured by Shuttle
1333 Technology and widely used in devices from major vendors such as
1334 Hewlett-Packard, SyQuest, Imation and Avatar. If you chose to build
1335 PARIDE support into your kernel, you may answer Y here to build in
1336 the protocol driver, otherwise you should answer M to build it as a
1337 loadable module. The module will be called epat.o. You must also
1338 have a high-level driver for the type of device that you want to
1341 Shuttle EPIA protocol
1343 This option enables support for the (obsolete) EPIA parallel port
1344 IDE protocol from Shuttle Technology. This adapter can still be
1345 found in some no-name kits. If you chose to build PARIDE support
1346 into your kernel, you may answer Y here to build in the protocol
1347 driver, otherwise you should answer M to build it as a loadable
1348 module. The module will be called epia.o. You must also have a
1349 high-level driver for the type of device that you want to support.
1351 FIT TD-2000 protocol
1353 This option enables support for the TD-2000 parallel port IDE
1354 protocol from Fidelity International Technology. This is a simple
1355 (low speed) adapter that is used in some portable hard drives. If
1356 you chose to build PARIDE support into your kernel, you may answer Y
1357 here to build in the protocol driver, otherwise you should answer M
1358 to build it as a loadable module. The module will be called ktti.o.
1359 You must also have a high-level driver for the type of device that
1360 you want to support.
1362 FIT TD-3000 protocol
1364 This option enables support for the TD-3000 parallel port IDE
1365 protocol from Fidelity International Technology. This protocol is
1366 used in newer models of their portable disk, CD-ROM and PD/CD
1367 devices. If you chose to build PARIDE support into your kernel, you
1368 may answer Y here to build in the protocol driver, otherwise you
1369 should answer M to build it as a loadable module. The module will be
1370 called fit3.o. You must also have a high-level driver for the type
1371 of device that you want to support.
1373 Freecom IQ ASIC-2 protocol
1375 This option enables support for version 2 of the Freecom IQ parallel
1376 port IDE adapter. This adapter is used by the Maxell Superdisk
1377 drive. If you chose to build PARIDE support into your kernel, you
1378 may answer Y here to build in the protocol driver, otherwise you
1379 should answer M to build it as a loadable module. The module will be
1380 called friq.o. You must also have a high-level driver for the type
1381 of device that you want to support.
1383 FreeCom power protocol
1385 This option enables support for the Freecom power parallel port IDE
1386 protocol. If you chose to build PARIDE support into your kernel, you
1387 may answer Y here to build in the protocol driver, otherwise you
1388 should answer M to build it as a loadable module. The module will be
1389 called frpw.o. You must also have a high-level driver for the type
1390 of device that you want to support.
1392 KingByte KBIC-951A/971A protocols
1394 This option enables support for the KBIC-951A and KBIC-971A parallel
1395 port IDE protocols from KingByte Information Corp. KingByte's
1396 adapters appear in many no-name portable disk and CD-ROM products,
1397 especially in Europe. If you chose to build PARIDE support into your
1398 kernel, you may answer Y here to build in the protocol driver,
1399 otherwise you should answer M to build it as a loadable module. The
1400 module will be called kbic.o. You must also have a high-level driver
1401 for the type of device that you want to support.
1405 This option enables support for the "PHd" parallel port IDE protocol
1406 from KT Technology. This is a simple (low speed) adapter that is
1407 used in some 2.5" portable hard drives. If you chose to build PARIDE
1408 support into your kernel, you may answer Y here to build in the
1409 protocol driver, otherwise you should answer M to build it as a
1410 loadable module. The module will be called ktti.o. You must also
1411 have a high-level driver for the type of device that you want to
1414 OnSpec 90c20 protocol
1416 This option enables support for the (obsolete) 90c20 parallel port
1417 IDE protocol from OnSpec (often marketed under the ValuStore brand
1418 name). If you chose to build PARIDE support into your kernel, you
1419 may answer Y here to build in the protocol driver, otherwise you
1420 should answer M to build it as a loadable module. The module will
1421 be called on20.o. You must also have a high-level driver for the
1422 type of device that you want to support.
1424 OnSpec 90c26 protocol
1426 This option enables support for the 90c26 parallel port IDE protocol
1427 from OnSpec Electronics (often marketed under the ValuStore brand
1428 name). If you chose to build PARIDE support into your kernel, you
1429 may answer Y here to build in the protocol driver, otherwise you
1430 should answer M to build it as a loadable module. The module will be
1431 called on26.o. You must also have a high-level driver for the type
1432 of device that you want to support.
1434 Logical Volume Manager (LVM) support
1436 This driver lets you combine several hard disks, hard disk
1437 partitions, multiple devices or even loop devices (for evaluation
1438 purposes) into a volume group. Imagine a volume group as a kind of
1439 virtual disk. Logical volumes, which can be thought of as virtual
1440 partitions, can be created in the volume group. You can resize
1441 volume groups and logical volumes after creation time, corresponding
1442 to new capacity needs. Logical volumes are accessed as block
1443 devices named /dev/VolumeGroupName/LogicalVolumeName.
1445 For details see Documentation/LVM-HOWTO. You will need supporting
1446 user space software; location is in Documentation/Changes.
1448 If you want to compile this support as a module ( = code which can
1449 be inserted in and removed from the running kernel whenever you
1450 want), say M here and read Documentation/modules.txt. The module
1451 will be called lvm-mod.o.
1453 Logical Volume Manager /proc file system information
1455 If you say Y here, you are able to access overall Logical Volume
1456 Manager, Volume Group, Logical and Physical Volume information in
1459 To use this option, you have to check, that the "/proc file system
1460 support" (CONFIG_PROC_FS) is enabled too.
1462 Multiple devices driver support
1464 This driver lets you combine several hard disk partitions into one
1465 logical block device. This can be used to simply append one
1466 partition to another one or to combine several redundant hard disks
1467 into a RAID1/4/5 device so as to provide protection against hard
1468 disk failures. This is called "Software RAID" since the combining of
1469 the partitions is done by the kernel. "Hardware RAID" means that the
1470 combining is done by a dedicated controller; if you have such a
1471 controller, you do not need to say Y here.
1473 More information about Software RAID on Linux is contained in the
1474 Software-RAID mini-HOWTO, available from
1475 http://www.linuxdoc.org/docs.html#howto . There you will also
1476 learn where to get the supporting user space utilities raidtools.
1480 Linear (append) mode
1482 If you say Y here, then your multiple devices driver will be able to
1483 use the so-called linear mode, i.e. it will combine the hard disk
1484 partitions by simply appending one to the other.
1486 If you want to compile this as a module ( = code which can be
1487 inserted in and removed from the running kernel whenever you want),
1488 say M here and read Documentation/modules.txt. The module will be
1493 RAID-0 (striping) mode
1495 If you say Y here, then your multiple devices driver will be able to
1496 use the so-called raid0 mode, i.e. it will combine the hard disk
1497 partitions into one logical device in such a fashion as to fill them
1498 up evenly, one chunk here and one chunk there. This will increase
1499 the throughput rate if the partitions reside on distinct disks.
1501 Information about Software RAID on Linux is contained in the
1502 Software-RAID mini-HOWTO, available from
1503 http://www.linuxdoc.org/docs.html#howto . There you will also
1504 learn where to get the supporting user space utilities raidtools.
1506 If you want to compile this as a module ( = code which can be
1507 inserted in and removed from the running kernel whenever you want),
1508 say M here and read Documentation/modules.txt. The module will be
1513 RAID-1/RAID-5 code (DANGEROUS)
1514 CONFIG_RAID15_DANGEROUS
1515 This new RAID1/RAID5 code has been freshly merged, and has not seen
1516 enough testing yet. While there are no known bugs in it, it might
1517 destroy your filesystems, eat your data and start World War III.
1518 You have been warned.
1522 RAID-1 (mirroring) mode
1524 A RAID-1 set consists of several disk drives which are exact copies
1525 of each other. In the event of a mirror failure, the RAID driver
1526 will continue to use the operational mirrors in the set, providing
1527 an error free MD (multiple device) to the higher levels of the
1528 kernel. In a set with N drives, the available space is the capacity
1529 of a single drive, and the set protects against a failure of (N - 1)
1532 Information about Software RAID on Linux is contained in the
1533 Software-RAID mini-HOWTO, available from
1534 http://www.linuxdoc.org/docs.html#howto . There you will also
1535 learn where to get the supporting user space utilities raidtools.
1537 If you want to use such a RAID-1 set, say Y. This code is also
1538 available as a module called raid1.o ( = code which can be inserted
1539 in and removed from the running kernel whenever you want). If you
1540 want to compile it as a module, say M here and read
1541 Documentation/modules.txt.
1547 A RAID-5 set of N drives with a capacity of C MB per drive provides
1548 the capacity of C * (N - 1) MB, and protects against a failure
1549 of a single drive. For a given sector (row) number, (N - 1) drives
1550 contain data sectors, and one drive contains the parity protection.
1551 For a RAID-4 set, the parity blocks are present on a single drive,
1552 while a RAID-5 set distributes the parity across the drives in one
1553 of the available parity distribution methods.
1555 Information about Software RAID on Linux is contained in the
1556 Software-RAID mini-HOWTO, available from
1557 http://www.linuxdoc.org/docs.html#howto . There you will also
1558 learn where to get the supporting user space utilities raidtools.
1560 If you want to use such a RAID-4/RAID-5 set, say Y. This code is
1561 also available as a module called raid5.o ( = code which can be
1562 inserted in and removed from the running kernel whenever you want).
1563 If you want to compile it as a module, say M here and read
1564 Documentation/modules.txt.
1570 To boot with an initial raid volume (any type) you can select
1571 autodetect, or answer Y here and appropriate options to the kernel
1573 For lilo and loadlin options see the file Documentation/md.txt.
1575 RAID AutoDetect support
1576 CONFIG_AUTODETECT_RAID
1577 An alternative to "Raid Boot support" is autodetect support.
1578 With this selected, any partitons of type 0xFD will be considered for
1579 inclusion in a RAID array. Information in the RAID-superblock on
1580 the partition will determine how it is included.
1582 Support for Acer PICA 1 chipset
1584 This is a machine with a R4400 133/150 MHz CPU. To compile a Linux
1585 kernel that runs on these, say Y here. For details about Linux on
1586 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1587 http://oss.sgi.com/mips .
1589 Support for Algorithmics P4032 (EXPERIMENTAL)
1591 This is an evaluation board of the British company Algorithmics. The
1592 board uses the R4300 and a R5230 CPUs. For more information about
1593 this board see http://www.algor.co.uk .
1595 Support for BAGET MIPS series
1597 This enables support for the Baget, a Russian embedded system. For
1598 more details about the Baget see the Linux/MIPS FAQ on
1599 http://oss.sgi.com/mips .
1601 Support for Cobalt Microserver
1602 CONFIG_COBALT_MICRO_SERVER
1603 This enables support for the Cobalt Microserver. For more information
1604 see the Linux/MIPS FAQ on http://oss.sgi.com/mips .
1608 This adds support for the Cobalt Microserver 2800. A kernel with this
1609 option selected will only work on the 2800.
1611 Support for DECstations
1613 This enables support for DEC's MIPS based workstations. For details
1614 see the Linux/MIPS FAQ on http://oss.sgi.com/mips and the
1615 DECstation porting pages on http://decstation.unix-ag.org .
1617 If you have one of the following DECstation Models you definitely
1618 want to choose R4xx0 for the CPU Type:
1625 otherwise choose R3000.
1627 Support for NEC DDB Vrc-5074
1629 This enables support for the VR5000-based NEC DDB Vrc-5074
1632 Support for Mips Magnum 4000
1633 CONFIG_MIPS_MAGNUM_4000
1634 This is a machine with a R4000 100 MHz CPU. To compile a Linux
1635 kernel that runs on these, say Y here. For details about Linux on
1636 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1637 http://oss.sgi.com/mips.
1639 Support for Olivetti M700
1640 CONFIG_OLIVETTI_M700
1641 This is a machine with a R4000 100 MHz CPU. To compile a Linux
1642 kernel that runs on these, say Y here. For details about Linux on
1643 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1644 http://oss.sgi.com/mips.
1646 Support for SGI IP22
1648 This are the SGI Indy, Challenge S and Indigo2, as well as certain
1649 OEM variants like the Tandem CMN B006S. To compile a Linux kernel
1650 that runs on these, say Y here.
1652 Support for SGI IP27
1653 This are the SGI Origin 200, Origin 2000 and Onyx 2 Graphics
1654 workstations. To compile a Linux kernel that runs on these, say Y
1658 CONFIG_SGI_SN0_N_MODE
1659 The nodes of Origin 200, Origin 2000 and Onyx 2 systems can be
1660 configured in either N-Modes which allows for more nodes or M-Mode
1661 which allows for more more memory. Your system is most probably
1662 running in M-Mode, so you should say N here.
1664 MIPS JAZZ onboard SONIC Ethernet support
1665 CONFIG_MIPS_JAZZ_SONIC
1666 This is the driver for the onboard card of of MIPS Magnum 4000,
1667 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
1669 MIPS JAZZ FAS216 SCSI support
1671 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1672 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1675 PCMCIA SCSI adapter support
1677 Say Y here if you intend to attach a PCMCIA or CardBus card to your
1678 computer which acts as a SCSI host adapter. These are credit card
1679 size devices often used with laptops.
1681 Note that the answer to this question won't directly affect the
1682 kernel: saying N will just cause this configure script to skip all
1683 the questions PCMCIA SCSI host adapters.
1685 Adaptec AHA152X PCMCIA support
1686 CONFIG_PCMCIA_AHA152X
1687 Say Y here if you intend to attach this type of PCMCIA SCSI host
1688 adapter to your computer.
1690 This driver is also available as a module called aha152x_cs.o ( =
1691 code which can be inserted in and removed from the running kernel
1692 whenever you want). If you want to compile it as a module, say M
1693 here and read Documentation/modules.txt.
1695 Qlogic PCMCIA support
1696 CONFIG_PCMCIA_QLOGIC
1697 Say Y here if you intend to attach this type of PCMCIA SCSI host
1698 adapter to your computer.
1700 This driver is also available as a module called qlogic_cs.o ( =
1701 code which can be inserted in and removed from the running kernel
1702 whenever you want). If you want to compile it as a module, say M
1703 here and read Documentation/modules.txt.
1705 Future Domain PCMCIA support
1706 CONFIG_PCMCIA_FDOMAIN
1707 Say Y here if you intend to attach this type of PCMCIA SCSI host
1708 adapter to your computer.
1710 This driver is also available as a module called fdomain_cs.o ( =
1711 code which can be inserted in and removed from the running kernel
1712 whenever you want). If you want to compile it as a module, say M
1713 here and read Documentation/modules.txt.
1715 Adaptec APA1480 CardBus support
1716 CONFIG_PCMCIA_APA1480
1717 Say Y here if you intend to attach this type of CardBus SCSI host
1718 adapter to your computer.
1720 This driver is also available as a module called apa1480_cb.o ( =
1721 code which can be inserted in and removed from the running kernel
1722 whenever you want). If you want to compile it as a module, say M
1723 here and read Documentation/modules.txt.
1727 Please make sure to pick the right CPU type. Linux/MIPS is not
1728 designed to be generic, i.e. Kernels compiled for R3000 CPUs will
1729 *not* work on R4000 Machines and vice versa.
1730 However, since most the supported Machines have an R4000 (or
1731 similar) CPU, R4xx0 might be a safe bet.
1732 If the resulting Kernel does not work try to recompile with R3000.
1734 Support for large 64-bit configurations
1735 CONFIG_MIPS_INSANE_LARGE
1736 MIPS R10000 does support a 44 bit / 16TB address space as opposed to
1737 previous 64-bit processors which only supported 40 bit / 1TB. If you
1738 need processes of more than 1TB virtual address space, say Y here.
1739 This will result in additional memory usage, so it is not
1740 recommended for normal users.
1742 Generate little endian code
1743 CONFIG_CPU_LITTLE_ENDIAN
1744 Some MIPS machines can be configured for either little or big endian
1745 byte order. These modes require different kernels. Say Y if your
1746 machine is little endian, N if it's a big endian machine.
1750 Unless you really know what you are doing, you should say Y here.
1751 The reason is that some programs need kernel networking support even
1752 when running on a stand-alone machine that isn't connected to any
1753 other computer. If you are upgrading from an older kernel, you
1754 should consider updating your networking tools too because changes
1755 in the kernel and the tools often go hand in hand. The tools are
1756 contained in the package net-tools, the location and version number
1757 of which are given in Documentation/Changes.
1759 For a general introduction to Linux networking, it is highly
1760 recommended to read the NET-3-HOWTO, available from
1761 http://www.linuxdoc.org/docs.html#howto .
1765 The Linux Socket Filter is derived from the Berkeley Packet Filter.
1766 If you say Y here, user-space programs can attach a filter to any
1767 socket and thereby tell the kernel that it should allow or disallow
1768 certain types of data to get through the socket. Linux Socket
1769 Filtering works on all socket types except TCP for now. See the text
1770 file Documentation/networking/filter.txt for more information.
1773 Network packet filtering
1775 Netfilter is a framework for filtering and mangling network packets
1776 that pass through your Linux box.
1778 The most common use of packet filtering is to run your Linux box as
1779 a firewall protecting a local network from the Internet. The type of
1780 firewall provided by this kernel support is called a "packet
1781 filter", which means that it can reject individual network packets
1782 based on type, source, destination etc. The other kind of firewall,
1783 a "proxy-based" one, is more secure but more intrusive and more
1784 bothersome to set up; it inspects the network traffic much more
1785 closely, modifies it and has knowledge about the higher level
1786 protocols, which a packet filter lacks. Moreover, proxy-based
1787 firewalls often require changes to the programs running on the local
1788 clients. Proxy-based firewalls don't need support by the kernel, but
1789 they are often combined with a packet filter, which only works if
1792 You should also say Y here if you intend to use your Linux box as
1793 the gateway to the Internet for a local network of machines without
1794 globally valid IP addresses. This is called "masquerading": if one
1795 of the computers on your local network wants to send something to
1796 the outside, your box can "masquerade" as that computer, i.e. it
1797 forwards the traffic to the intended outside destination, but
1798 modifies the packets to make it look like they came from the
1799 firewall box itself. It works both ways: if the outside host
1800 replies, the Linux box will silently forward the traffic to the
1801 correct local computer. This way, the computers on your local net
1802 are completely invisible to the outside world, even though they can
1803 reach the outside and can receive replies. It is even possible to
1804 run globally visible servers from within a masqueraded local network
1805 using a mechanism called portforwarding. Masquerading is also often
1806 called NAT (Network Address Translation).
1808 Another use of Netfilter is in transparent proxying: if a machine on
1809 the local network tries to connect to an outside host, your Linux
1810 box can transparently forward the traffic to a local server,
1811 typically a caching proxy server.
1813 Various modules exist for netfilter which replace the previous
1814 masquerading (ipmasqadm), packet filtering (ipchains), transparent
1815 proxying, and portforwarding mechanisms. Please see
1816 Documentation/Changes under "iptables" for the location of these
1819 Make sure to say N to "Fast switching" below if you intend to say Y
1820 here, as Fast switching currently bypasses netfilter.
1822 Chances are that you should say Y here if you compile a kernel which
1823 will run as a router and N for regular hosts. If unsure, say N.
1825 Network packet filtering debugging
1826 CONFIG_NETFILTER_DEBUG
1827 You can say Y here if you want to get additional messages useful in
1828 debugging the netfilter code.
1830 IP: connection tracking (required for masq/NAT)
1831 CONFIG_IP_NF_CONNTRACK
1832 Connection tracking keeps a record of what packets have passed
1833 through your machine, in order to figure out how they are related
1836 This is required to do Masquerading or other kinds of Network
1837 Address Translation (except for Fast NAT). It can also be used to
1838 enhance packet filtering (see `Connection state match support'
1841 If you want to compile it as a module, say M here and read
1842 Documentation/modules.txt. If unsure, say `N'.
1844 FTP protocol support
1846 Tracking FTP connections is problematic: special helpers are
1847 required for tracking them, and doing masquerading and other forms
1848 of Network Address Translation on them.
1850 If you want to compile it as a module, say M here and read
1851 Documentation/modules.txt. If unsure, say `Y'.
1853 IP: user space queueing via NETLINK (EXPERIMENTAL)
1855 Netfilter has the ability to queue packets to user space: the
1856 netlink device can be used to access them using this driver.
1858 If you want to compile it as a module, say M here and read
1859 Documentation/modules.txt. If unsure, say `N'.
1861 IP: ip tables support (required for filtering/masq/NAT)
1862 CONFIG_IP_NF_IPTABLES
1863 iptables is a general, extensible packet identification framework.
1864 The packet filtering and full NAT (masquerading, port forwarding,
1865 etc) subsystems now use this: say `Y' or `M' here if you want to use
1868 If you want to compile it as a module, say M here and read
1869 Documentation/modules.txt. If unsure, say `N'.
1872 CONFIG_IP_NF_MATCH_LIMIT
1873 limit matching allows you to control the rate at which a rule can be
1874 matched: mainly useful in combination with the LOG target ("LOG
1875 target support", below) and to avoid some Denial of Service attacks.
1877 If you want to compile it as a module, say M here and read
1878 Documentation/modules.txt. If unsure, say `N'.
1880 MAC address match support
1881 CONFIG_IP_NF_MATCH_MAC
1882 mac matching allows you to match packets based on the source
1883 ethernet address of the packet.
1885 If you want to compile it as a module, say M here and read
1886 Documentation/modules.txt. If unsure, say `N'.
1888 netfilter mark match support
1889 CONFIG_IP_NF_MATCH_MARK
1890 Netfilter mark matching allows you to match packets based on the
1891 `nfmark' value in the packet. This can be set by the MARK target
1894 If you want to compile it as a module, say M here and read
1895 Documentation/modules.txt. If unsure, say `N'.
1897 Multiple port match support
1898 CONFIG_IP_NF_MATCH_MULTIPORT
1899 Multiport matching allows you to match TCP or UDP packets based on
1900 a series of source or destination ports: normally a rule can only
1901 match a single range of ports.
1903 If you want to compile it as a module, say M here and read
1904 Documentation/modules.txt. If unsure, say `N'.
1907 CONFIG_IP_NF_MATCH_TOS
1908 TOS matching allows you to match packets based on the Type Of
1909 Service fields of the IP packet.
1911 If you want to compile it as a module, say M here and read
1912 Documentation/modules.txt. If unsure, say `N'.
1914 Connection state match support
1915 CONFIG_IP_NF_MATCH_STATE
1916 Connection state matching allows you to match packets based on their
1917 relationship to a tracked connection (ie. previous packets). This
1918 is a powerful tool for packet classification.
1920 If you want to compile it as a module, say M here and read
1921 Documentation/modules.txt. If unsure, say `N'.
1923 Unclean match support (EXPERIMENTAL)
1924 CONFIG_IP_NF_MATCH_UNCLEAN
1925 Unclean packet matching matches any strange or invalid packets, by
1926 looking at a series of fields in the IP, TCP, UDP and ICMP headers.
1928 If you want to compile it as a module, say M here and read
1929 Documentation/modules.txt. If unsure, say `N'.
1931 Owner match support (EXPERIMENTAL)
1932 CONFIG_IP_NF_MATCH_OWNER
1933 Packet owner matching allows you to match locally-generated packets
1934 based on who created them: the user, group, process or session.
1936 If you want to compile it as a module, say M here and read
1937 Documentation/modules.txt. If unsure, say `N'.
1941 Packet filtering defines a table `filter', which has a series of
1942 rules for simple packet filtering at local input, forwarding and
1943 local output. See the man page for iptables(8).
1945 If you want to compile it as a module, say M here and read
1946 Documentation/modules.txt. If unsure, say `N'.
1948 REJECT target support
1949 CONFIG_IP_NF_TARGET_REJECT
1950 The REJECT target allows a filtering rule to specify that an ICMP
1951 error should be issued in response to an incoming packet, rather
1952 than silently being dropped.
1954 If you want to compile it as a module, say M here and read
1955 Documentation/modules.txt. If unsure, say `N'.
1957 MIRROR target support (EXPERIMENTAL)
1958 CONFIG_IP_NF_TARGET_MIRROR
1959 The MIRROR target allows a filtering rule to specify that an
1960 incoming packet should be bounced back to the sender.
1962 If you want to compile it as a module, say M here and read
1963 Documentation/modules.txt. If unsure, say `N'.
1967 The Full NAT option allows masquerading, port forwarding and other
1968 forms of full Network Address Port Translation. It is controlled by
1969 the `nat' table in iptables: see the man page for iptables(8).
1971 If you want to compile it as a module, say M here and read
1972 Documentation/modules.txt. If unsure, say `N'.
1974 MASQUERADE target support
1975 CONFIG_IP_NF_TARGET_MASQUERADE
1976 Masquerading is a special case of NAT: all outgoing connections are
1977 changed to seem to come from a particular interface's address, and
1978 if the interface goes down, those connections are lost. This is
1979 only useful for dialup accounts with dynamic IP address (ie. your IP
1980 address will be different on next dialup).
1982 If you want to compile it as a module, say M here and read
1983 Documentation/modules.txt. If unsure, say `N'.
1985 REDIRECT target support
1986 CONFIG_IP_NF_TARGET_REDIRECT
1987 REDIRECT is a special case of NAT: all incoming connections are
1988 mapped onto the incoming interface's address, causing the packets to
1989 come to the local machine instead of passing through. This is
1990 useful for transparent proxies.
1992 If you want to compile it as a module, say M here and read
1993 Documentation/modules.txt. If unsure, say `N'.
1997 This option adds a `mangle' table to iptables: see the man page for
1998 iptables(8). This table is used for various packet alterations
1999 which can effect how the packet is routed.
2001 If you want to compile it as a module, say M here and read
2002 Documentation/modules.txt. If unsure, say `N'.
2005 CONFIG_IP_NF_TARGET_TOS
2006 This option adds a `TOS' target, which allows you to create rules in
2007 the `mangle' table which alter the Type Of Service field of an IP
2008 packet prior to routing.
2010 If you want to compile it as a module, say M here and read
2011 Documentation/modules.txt. If unsure, say `N'.
2014 CONFIG_IP_NF_TARGET_MARK
2015 This option adds a `MARK' target, which allows you to create rules
2016 in the `mangle' table which alter the netfilter mark (nfmark) field
2017 associated with the packet packet prior to routing. This can change
2018 the routing method (see `IP: use netfilter MARK value as routing
2019 key') and can also be used by other subsystems to change their
2022 If you want to compile it as a module, say M here and read
2023 Documentation/modules.txt. If unsure, say `N'.
2026 CONFIG_IP_NF_TARGET_LOG
2027 This option adds a `LOG' target, which allows you to create rules in
2028 any iptables table which records the packet header to the syslog.
2030 If you want to compile it as a module, say M here and read
2031 Documentation/modules.txt. If unsure, say `N'.
2033 ipchains (2.2-style) support
2034 CONFIG_IP_NF_COMPAT_IPCHAINS
2035 This option places ipchains (with masquerading and redirection
2036 support) back into the kernel, using the new netfilter
2037 infrastructure. It is not recommended for new installations (see
2038 `Packet filtering'). With this enabled, you should be able to use
2039 the ipchains tool exactly as in 2.2 kernels.
2041 If you want to compile it as a module, say M here and read
2042 Documentation/modules.txt. If unsure, say `N'.
2044 ipfwadm (2.0-style) support
2045 CONFIG_IP_NF_COMPAT_IPFWADM
2046 This option places ipfwadm (with masquerading and redirection
2047 support) back into the kernel, using the new netfilter
2048 infrastructure. It is not recommended for new installations (see
2049 `Packet filtering'). With this enabled, you should be able to use
2050 the ipfwadm tool exactly as in 2.0 kernels.
2052 If you want to compile it as a module, say M here and read
2053 Documentation/modules.txt. If unsure, say `N'.
2055 TCP Explicit Congestion Notification support
2057 Explicit Congestion Notification (ECN) allows routers to notify
2058 clients about network congestion, resulting in fewer dropped packets
2059 and increased network performance. This option adds ECN support to the
2060 Linux kernel, as well as a sysctl (/proc/sys/net/ipv4/tcp_ecn) which
2061 allows ECN support to be disabled at runtime.
2063 Note that, on the Internet, there are many broken firewalls which
2064 refuse connections from ECN-enabled machines, and it may be a while
2065 before these firewalls are fixed. Until then, to access a site behind
2066 such a firewall (some of which are major sites, at the time of this
2067 writing) you will have to disable this option, either by saying N now
2068 or by using the sysctl.
2072 SYN flood protection
2074 Normal TCP/IP networking is open to an attack known as "SYN
2075 flooding". This denial-of-service attack prevents legitimate remote
2076 users from being able to connect to your computer during an ongoing
2077 attack and requires very little work from the attacker, who can
2078 operate from anywhere on the Internet.
2080 SYN cookies provide protection against this type of attack. If you
2081 say Y here, the TCP/IP stack will use a cryptographic challenge
2082 protocol known as "SYN cookies" to enable legitimate users to
2083 continue to connect, even when your machine is under attack. There
2084 is no need for the legitimate users to change their TCP/IP software;
2085 SYN cookies work transparently to them. For technical information
2086 about SYN cookies, check out
2087 ftp://koobera.math.uic.edu/syncookies.html .
2089 If you are SYN flooded, the source address reported by the kernel is
2090 likely to have been forged by the attacker; it is only reported as
2091 an aid in tracing the packets to their actual source and should not
2092 be taken as absolute truth.
2094 SYN cookies may prevent correct error reporting on clients when the
2095 server is really overloaded. If this happens frequently better turn
2098 If you say Y here, note that SYN cookies aren't enabled by default;
2099 you can enable them by saying Y to "/proc file system support" and
2100 "Sysctl support" below and executing the command
2102 echo 1 >/proc/sys/net/ipv4/tcp_syncookies
2104 at boot time after the /proc file system has been mounted.
2109 CONFIG_ALPHA_GENERIC
2110 This is the system type of your hardware. A "generic" kernel will
2111 run on any supported Alpha system. However, if you configure a
2112 kernel for your specific system, it will be faster and smaller.
2114 To find out what type of Alpha system you have, you may want to
2115 check out the Linux/Alpha FAQ, accessible on the WWW from
2116 http://www.alphalinux.org . In summary:
2118 Alcor/Alpha-XLT AS 600
2119 Alpha-XL XL-233, XL-266
2120 AlphaBook1 Alpha laptop
2121 Avanti AS 200, AS 205, AS 250, AS 255, AS 300, AS 400
2122 Cabriolet AlphaPC64, AlphaPCI64
2124 EB164 EB164 21164 evaluation board
2125 EB64+ EB64+ 21064 evaluation board
2126 EB66 EB66 21066 evaluation board
2127 EB66+ EB66+ 21066 evaluation board
2128 Jensen DECpc 150, DEC 2000 model 300,
2131 Miata Personal Workstation 433a, 433au, 500a,
2132 500au, 600a, or 600au
2134 Noname AXPpci33, UDB (Multia)
2135 Noritake AS 1000A, AS 600A, AS 800
2137 Rawhide AS 1200, AS 4000, AS 4100
2138 Ruffian RPX164-2, AlphaPC164-UX, AlphaPC164-BX
2140 Sable AS 2000, AS 2100
2143 Wildfire AlphaServer GS 40/80/160/320
2145 If you don't know what to do, choose "generic".
2147 EV5 CPU daughtercard
2149 Say Y if you have an AS 1000 5/xxx or an AS 1000A 5/xxx.
2153 Say Y if you have an AS 2000 5/xxx or an AS 2100 5/xxx.
2155 Using SRM as bootloader
2157 There are two different types of booting firmware on Alphas: SRM,
2158 which is command line driven, and ARC, which uses menus and arrow
2159 keys. Details about the Linux/Alpha booting process are contained in
2160 the Linux/Alpha FAQ, accessible on the WWW from
2161 http://www.alphalinux.org .
2163 The usual way to load Linux on an Alpha machine is to use MILO
2164 (a bootloader that lets you pass command line parameters to the
2165 kernel just like lilo does for the x86 architecture) which can be
2166 loaded either from ARC or can be installed directly as a permanent
2167 firmware replacement from floppy (which requires changing a certain
2168 jumper on the motherboard). If you want to do either of these, say N
2169 here. If MILO doesn't work on your system (true for Jensen
2170 motherboards), you can bypass it altogether and boot Linux directly
2171 from an SRM console; say Y here in order to do that. Note that you
2172 won't be able to boot from an IDE disk using SRM.
2176 Legacy kernel start address
2177 CONFIG_ALPHA_LEGACY_START_ADDRESS
2178 The 2.4 kernel changed the kernel start address from 0x310000
2179 to 0x810000 to make room for the Wildfire's larger SRM console.
2181 If you're using aboot 0.7 or later, the bootloader will examine
2182 the ELF headers to determine where to transfer control. Unfortunately,
2183 most older bootloaders -- APB or MILO -- hardcoded the kernel
2184 start address rather than examining the ELF headers, and the result
2187 Say Y if you have a broken bootloader. Say N if you do not, or
2188 if you wish to run on Wildfire.
2190 Large VMALLOC support
2191 CONFIG_ALPHA_LARGE_VMALLOC
2192 Process creation and other aspects of virtual memory management
2193 can be streamlined if we restrict the kernel to one PGD for all
2194 vmalloc allocations. This equates to about 8GB.
2196 Under normal circumstances, this is so far and above what is needed
2197 as to be laughable. However, there are certain applications (such
2198 as benchmark-grade in-kernel web serving) that can make use of as
2199 much vmalloc space as is available.
2201 Say N unless you know you need gobs and gobs of vmalloc space.
2203 Non-standard serial port support
2204 CONFIG_SERIAL_NONSTANDARD
2205 Say Y here if you have any non-standard serial boards -- boards
2206 which aren't supported using the standard "dumb" serial driver.
2207 This includes intelligent serial boards such as Cyclades,
2208 Digiboards, etc. These are usually used for systems that need many
2209 serial ports because they serve many terminals or dial-in
2212 Note that the answer to this question won't directly affect the
2213 kernel: saying N will just cause this configure script to skip all
2214 the questions about non-standard serial boards.
2216 Most people can say N here.
2218 Extended dumb serial driver options
2219 CONFIG_SERIAL_EXTENDED
2220 If you wish to use any non-standard features of the standard "dumb"
2221 driver, say Y here. This includes HUB6 support, shared serial
2222 interrupts, special multiport support, support for more than the
2223 four COM 1/2/3/4 boards, etc.
2225 Note that the answer to this question won't directly affect the
2226 kernel: saying N will just cause this configure script to skip all
2227 the questions about serial driver options. If unsure, say N.
2229 Support more than 4 serial ports
2230 CONFIG_SERIAL_MANY_PORTS
2231 Say Y here if you have dumb serial boards other than the four
2232 standard COM 1/2/3/4 ports. This may happen if you have an AST
2233 FourPort, Accent Async, Boca (read the Boca mini-HOWTO, available
2234 from http://www.linuxdoc.org/docs.html#howto ), or other custom
2235 serial port hardware which acts similar to standard serial port
2236 hardware. If you only use the standard COM 1/2/3/4 ports, you can
2237 say N here to save some memory. You can also say Y if you have an
2238 "intelligent" multiport card such as Cyclades, Digiboards, etc.
2240 Support for sharing serial interrupts
2241 CONFIG_SERIAL_SHARE_IRQ
2242 Some serial boards have hardware support which allows multiple dumb
2243 serial ports on the same board to share a single IRQ. To enable
2244 support for this in the serial driver, say Y here.
2246 Auto detect IRQ on standard ports (unsafe)
2247 CONFIG_SERIAL_DETECT_IRQ
2248 Say Y here if you want the kernel to try to guess which IRQ
2249 to use for your serial port.
2251 This is considered unsafe; it is far better to configure the IRQ in
2252 a boot script using the setserial command.
2256 Support special multiport boards
2257 CONFIG_SERIAL_MULTIPORT
2258 Some multiport serial ports have special ports which are used to
2259 signal when there are any serial ports on the board which need
2260 servicing. Say Y here to enable the serial driver to take advantage
2261 of those special I/O ports.
2263 SGI PROM Console Support
2264 CONFIG_SGI_PROM_CONSOLE
2265 Say Y here if you want to use the PROMs for console I/O.
2267 SGI Zilog85C30 serial support
2269 If you want to use your SGI's built-in serial ports under Linux,
2272 SGI Newport Graphics support (EXPERIMENTAL)
2273 CONFIG_SGI_NEWPORT_GFX
2274 If you have an SGI machine and you want to compile the graphics
2275 drivers, say Y here. This will include the code for the
2276 /dev/graphics and /dev/gfx drivers into the kernel for supporting
2277 virtualized access to your graphics hardware.
2279 SGI Newport Console support
2280 CONFIG_SGI_NEWPORT_CONSOLE
2281 Say Y here if you want the console on the Newport aka XL graphics
2282 card of your Indy. Most people say Y here.
2284 SGI DS1286 RTC support
2286 If you say Y here and create a character special file /dev/rtc with
2287 major number 10 and minor number 135 using mknod ("man mknod"), you
2288 will get access to the real time clock built into your computer.
2289 Every SGI has such a clock built in. It reports status information
2290 via the file /proc/rtc and its behaviour is set by various ioctls on
2293 Support the Bell Technologies HUB6 card
2295 Say Y here to enable support in the dumb serial driver to support
2298 PCMCIA serial device support
2299 CONFIG_PCMCIA_SERIAL_CS
2300 Say Y here to enable support for 16-bit PCMCIA serial devices,
2301 including serial port cards, modems, and the modem functions of
2302 multi-function ethernet/modem cards. (PCMCIA- or PC-cards are
2303 credit-card size devices often used with laptops.)
2305 This driver is also available as a module ( = code which can be
2306 inserted in and removed from the running kernel whenever you want).
2307 The module will be called serial_cs.o. If you want to compile it as
2308 a module, say M here and read Documentation/modules.txt. If unsure,
2311 CardBus serial device support
2312 CONFIG_PCMCIA_SERIAL_CB
2313 Say Y here to enable support for CardBus serial devices, including
2314 serial port cards, modems, and the modem functions of multi-function
2315 ethernet/modem devices. (CardBus cards are the newer and better
2316 version of PCMCIA- or PC-cards: credit card size devices often
2319 This driver is also available as a module ( = code which can be
2320 inserted in and removed from the running kernel whenever you want).
2321 The module will be called serial_cb.o. If you want to compile it as
2322 a module, say M here and read Documentation/modules.txt. If unsure,
2325 /dev/agpgart (AGP Support) (EXPERIMENTAL)
2327 AGP (Accelerated Graphics Port) is a bus system mainly used to
2328 connect graphics cards to the rest of the system.
2330 If you have an AGP system and you say Y here, it will be possible to
2331 use the AGP features of your 3D rendering video card. This code acts
2332 as a sort of "AGP driver" for the motherboard's chipset. The glx
2333 module will then be able to program the GART (graphics aperture
2334 relocation table) registers with appropriate values to transfer
2335 commands to the card.
2337 If you need more texture memory than you can get with the AGP GART
2338 (theoretically up to 256 MB, but in practice usually 64 or 128 MB
2339 due to kernel allocation issues), you could use PCI accesses
2340 and have up to a couple gigs of texture space.
2342 Note that this is the only means to have XFree4/GLX use
2343 write-combining with MTRR support on the AGP bus. Without it, OpenGL
2344 direct rendering will be a lot slower but still faster than PIO.
2346 For the moment, you should probably say N, unless you want to test
2347 the GLX component for XFree86 3.3.6, which can be downloaded from
2348 http://utah-glx.sourceforge.net/ , or need to use the 810 Xserver in
2351 This driver is available as a module. If you want to compile it as a
2352 module, say M here and read Documentation/modules.txt. The module
2353 will be called agpgart.o.
2355 Intel 440LX/BX/GX support
2357 This option gives you AGP support for the GLX component of the
2358 XFree86 4.x on Intel 440LX/BX/GX, 815, and 840 chipsets.
2360 For the moment, you should probably say N, unless you want to test
2361 the GLX component for XFree86 3.3.6, which can be downloaded from
2362 http://utah-glx.sourceforge.net/ .
2364 Intel I810/I810 DC100/I810e support
2366 This option gives you AGP support for the Xserver on the Intel 810
2367 and 815 chipset boards for their on-board integrated graphics. This
2368 is required to do any useful video modes with these boards.
2372 This option gives you AGP support for the GLX component of the
2373 XFree86 4.x on VIA MPV3/Apollo Pro chipsets.
2375 For the moment, you should probably say N, unless you want to test
2376 the GLX component for XFree86 3.3.6, which can be downloaded from
2377 http://utah-glx.sourceforge.net/ .
2379 AMD Irongate support
2381 This option gives you AGP support for the GLX component of the
2382 XFree86 4.x on AMD Irongate chipset.
2384 For the moment, you should probably say N, unless you want to test
2385 the GLX component for XFree86 3.3.6, which can be downloaded from
2386 http://utah-glx.sourceforge.net/ .
2390 This option gives you AGP support for the GLX component of the "soon
2391 to be released" XFree86 4.x on Silicon Integrated Systems [SiS]
2394 Note that 5591/5592 AGP chipsets are NOT supported.
2396 For the moment, you should probably say N, unless you want to test
2397 the GLX component for XFree86 3.3.6, which can be downloaded from
2398 http://utah-glx.sourceforge.net/ .
2402 This option gives you AGP support for the GLX component of the
2403 XFree86 4.x on the ALi M1541 chipset.
2405 This chipset can do AGP 1x and 2x, but note that there is an
2406 acknowledged incompatibility with Matrox G200 cards. Due to
2407 timing issues, this chipset cannot do AGP 2x with the G200.
2408 This is a hardware limitation. AGP 1x seems to be fine, though.
2410 For the moment, you should probably say N, unless you want to test
2411 the GLX component for XFree86 3.3.6, which can be downloaded from
2412 http://utah-glx.sourceforge.net/ .
2416 Find out whether you have a PCI motherboard. PCI is the name of a
2417 bus system, i.e. the way the CPU talks to the other stuff inside
2418 your box. Other bus systems are ISA, EISA, Microchannel (MCA) or
2419 VESA. If you have PCI, say Y, otherwise N.
2421 The PCI-HOWTO, available from
2422 http://www.linuxdoc.org/docs.html#howto , contains valuable
2423 information about which PCI hardware does work under Linux and which
2427 CONFIG_PCI_INTEGRATOR
2428 Find out whether you have a PCI motherboard. PCI is the name of a
2429 bus system, i.e. the way the CPU talks to the other stuff inside
2430 your box. Other bus systems are ISA, EISA, Microchannel (MCA) or
2431 VESA. If you have PCI, say Y, otherwise N.
2433 The PCI-HOWTO, available from
2434 http://www.linuxdoc.org/docs.html#howto , contains valuable
2435 information about which PCI hardware does work under Linux and which
2440 Find out whether you have a PCI motherboard. PCI is the name of a
2441 bus system, i.e. the way the CPU talks to the other stuff inside
2442 your box. Other bus systems are ISA, EISA, Microchannel (MCA) or
2443 VESA. If you have PCI, say Y, otherwise N.
2445 The PCI-HOWTO, available from
2446 http://www.linuxdoc.org/docs.html#howto , contains valuable
2447 information about which PCI hardware does work under Linux and which
2452 On PCI systems, the BIOS can be used to detect the PCI devices and
2453 determine their configuration. However, some old PCI motherboards
2454 have BIOS bugs and may crash if this is done. Also, some embedded
2455 PCI-based systems don't have any BIOS at all. Linux can also try to
2456 detect the PCI hardware directly without using the BIOS.
2458 With this option, you can specify how Linux should detect the PCI
2459 devices. If you choose "BIOS", the BIOS will be used, if you choose
2460 "Direct", the BIOS won't be used, and if you choose "Any", the
2461 kernel will try the direct access method and falls back to the BIOS
2462 if that doesn't work. If unsure, go with the default, which is
2465 PCI device name database
2467 By default, the kernel contains a database of all known PCI device
2468 names to make the information in /proc/pci, /proc/ioports and
2469 similar files comprehensible to the user. This database increases
2470 size of the kernel image by about 80KB, but it gets freed after the
2471 system boots up, so it doesn't take up kernel memory. Anyway, if you
2472 are building an installation floppy or kernel for an embedded system
2473 where kernel image size really matters, you can disable this feature
2474 and you'll get device ID numbers instead of names.
2476 When in doubt, say Y.
2480 MicroChannel Architecture is found in some IBM PS/2 machines and
2481 laptops. It is a bus system similar to PCI or ISA. See
2482 Documentation/mca.txt (and especially the web page given there)
2483 before attempting to build an MCA bus kernel.
2487 The Extended Industry Standard Architecture (EISA) bus was
2488 developed as an open alternative to the IBM MicroChannel bus.
2490 The EISA bus provided some of the features of the IBM MicroChannel
2491 bus while maintaining backward compatibility with cards made for
2492 the older ISA bus. The EISA bus saw limited use between 1988 and 1995
2493 when it was made obsolete by the PCI bus.
2495 Say Y here if you are building a kernel for an EISA-based machine.
2499 SGI Visual Workstation support
2501 The SGI Visual Workstation series is an IA32-based workstation
2502 based on SGI systems chips with some legacy PC hardware attached.
2503 Say Y here to create a kernel to run on the SGI 320 or 540.
2504 A kernel compiled for the Visual Workstation will not run on other
2505 PC boards and vice versa.
2506 See Documentation/sgi-visws.txt for more.
2508 SGI Visual Workstation framebuffer support
2510 SGI Visual Workstation support for framebuffer graphics.
2514 The Intelligent Input/Output (I2O) architecture allows hardware
2515 drivers to be split into two parts: an operating system specific
2516 module called the OSM and an hardware specific module called the
2517 HDM. The OSM can talk to a whole range of HDM's, and ideally the
2518 HDM's are not OS dependent. This allows for the same HDM driver to
2519 be used under different operating systems if the relevant OSM is in
2520 place. In order for this to work, you need to have an I2O interface
2521 adapter card in your computer. This card contains a special I/O
2522 processor (IOP), thus allowing high speeds since the CPU does not
2523 have to deal with I/O.
2525 If you say Y here, you will get a choice of interface adapter
2526 drivers and OSM's with the following questions.
2528 This support is also available as a module ( = code which can be
2529 inserted in and removed from the running kernel whenever you want).
2530 If you want to compile it as a module, say M here and read
2531 Documentation/modules.txt. You will get modules called i2o_core.o
2538 Say Y for support of PCI bus I2O interface adapters. Currently this
2539 is the only variety supported, so you should say Y.
2541 This support is also available as a module called i2o_pci.o ( = code
2542 which can be inserted in and removed from the running kernel
2543 whenever you want). If you want to compile it as a module, say M
2544 here and read Documentation/modules.txt.
2548 Include support for the I2O Block OSM. The Block OSM presents disk
2549 and other structured block devices to the operating system.
2551 This support is also available as a module called i2o_block.o ( =
2552 code which can be inserted in and removed from the running kernel
2553 whenever you want). If you want to compile it as a module, say M
2554 here and read Documentation/modules.txt.
2558 Include support for the LAN OSM. You will also need to include
2559 support for token ring or FDDI if you wish to use token ring or FDDI
2560 I2O cards with this driver.
2562 This support is also available as a module called i2o_lan.o ( = code
2563 which can be inserted in and removed from the running kernel
2564 whenever you want). If you want to compile it as a module, say M
2565 here and read Documentation/modules.txt.
2569 Allows direct SCSI access to SCSI devices on a SCSI or FibreChannel
2570 I2O controller. You can use both the SCSI and Block OSM together if
2573 This support is also available as a module called i2o_scsi.o ( =
2574 code which can be inserted in and removed from the running kernel
2575 whenever you want). If you want to compile it as a module, say M
2576 here and read Documentation/modules.txt.
2580 If you say Y here and to "/proc file system support", you will be
2581 able to read I2O related information from the virtual directory
2584 This support is also available as a module called i2o_proc.o ( =
2585 code which can be inserted in and removed from the running kernel
2586 whenever you want). If you want to compile it as a module, say M
2587 here and read Documentation/modules.txt.
2589 Plug and Play support
2591 Plug and Play (PnP) is a standard for peripherals which allows those
2592 peripherals to be configured by software, e.g. assign IRQ's or other
2593 parameters. No jumpers on the cards are needed, instead the values
2594 are provided to the cards from the BIOS, from the operating system,
2595 or using a user-space utility.
2597 Say Y here if you would like Linux to configure your Plug and Play
2598 devices. You should then also say Y to "ISA Plug and Play support",
2599 below. Alternatively, you can say N here and configure your PnP
2600 devices using the user space utilities contained in the isapnptools
2603 This support is also available as a module ( = code which can be
2604 inserted in and removed from the running kernel whenever you want).
2605 If you want to compile it as a module, say M here and read
2606 Documentation/modules.txt.
2608 ISA Plug and Play support
2610 Say Y here if you would like support for ISA Plug and Play devices.
2611 Some information is in Documentation/isapnp.txt.
2613 This support is also available as a module called isapnp.o ( =
2614 code which can be inserted in and removed from the running kernel
2615 whenever you want). If you want to compile it as a module, say M
2616 here and read Documentation/modules.txt.
2620 Support for hot-pluggable devices
2622 Say Y here if you want to plug devices into your computer while
2623 the system is running, and be able to use them quickly. In many
2624 cases, the devices can likewise be unplugged at any time too.
2626 One well known example of this is PCMCIA- or PC-cards, credit-card
2627 size devices such as network cards, modems or hard drives which are
2628 plugged into slots found on all modern laptop computers.
2630 Another example, used on modern desktops as well as laptops, is USB.
2631 Enable HOTPLUG with USB and KMOD, and your kernel will automatically
2632 call out to a user mode "policy agent" to load modules and set up
2633 software needed to use USB devices you plug in. Get agent software
2634 (at http://www.linux-usb.org/policy.html) and install it.
2636 PCMCIA/Cardbus support
2638 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
2639 computer. These are credit-card size devices such as network cards,
2640 modems or hard drives often used with laptops computers. There are
2641 actually two varieties of these cards: the older 16 bit PCMCIA cards
2642 and the newer 32 bit CardBus cards. If you want to use CardBus
2643 cards, you need to say Y here and also to "CardBus support" below.
2645 To use your PC-cards, you will need supporting software from David
2646 Hinds' pcmcia-cs package (see the file Documentation/Changes for
2647 location). Please also read the PCMCIA-HOWTO, available from
2648 http://www.linuxdoc.org/docs.html#howto
2650 This driver is also available as a module ( = code which can be
2651 inserted in and removed from the running kernel whenever you want).
2652 When compiled this way, there will be modules called pcmcia_core.o
2653 and ds.o. If you want to compile it as a module, say M here and
2654 read Documentation/modules.txt.
2658 CardBus is a bus mastering architecture for PC-cards, which allows
2659 for 32 bit PC-cards (the original PCMCIA standard specifies only
2660 a 16 bit wide bus). Many newer PC-cards are actually CardBus cards.
2662 To use your PC-cards, you will need supporting software from David
2663 Hinds' pcmcia-cs package (see the file Documentation/Changes for
2668 i82365/Yenta compatible bridge support
2670 Say Y here to include support for PCMCIA and CardBus host bridges
2671 that are register compatible with the Intel i82365 and/or the Yenta
2672 specification: this includes virtually all modern PCMCIA bridges.
2673 "Bridge" is the name used for the hardware inside your computer that
2674 PCMCIA cards are plugged into. If unsure, say Y.
2676 Databook TCIC host bridge support
2678 Say Y here to include support for the Databook TCIC family of PCMCIA
2679 host bridges. These are only found on a handful of old systems.
2680 "Bridge" is the name used for the hardware inside your computer that
2681 PCMCIA cards are plugged into. If unsure, say N.
2685 Inter Process Communication is a suite of library functions and
2686 system calls which let processes (running programs) synchronize and
2687 exchange information. It is generally considered to be a good thing,
2688 and some programs won't run unless you say Y here. In particular, if
2689 you want to run the DOS emulator dosemu under Linux (read the
2690 DOSEMU-HOWTO, available from
2691 http://www.linuxdoc.org/docs.html#howto ), you'll need to say Y
2694 You can find documentation about IPC with "info ipc" and also in
2695 section 6.4 of the Linux Programmer's Guide, available from
2696 http://www.linuxdoc.org/docs.html#guide .
2698 Shared memory is now implemented using a new (minimal) virtual file
2699 system. To mount it automatically at system startup just add the
2700 following line to your /etc/fstab:
2702 none /dev/shm shm defaults 0 0
2704 Saying Y here enlarges your kernel by about 18 KB. Just say Y.
2706 BSD Process Accounting
2707 CONFIG_BSD_PROCESS_ACCT
2708 If you say Y here, a user level program will be able to instruct the
2709 kernel (via a special system call) to write process accounting
2710 information to a file: whenever a process exits, information about
2711 that process will be appended to the file by the kernel. The
2712 information includes things such as creation time, owning user,
2713 command name, memory usage, controlling terminal etc. (the complete
2714 list is in the struct acct in include/linux/acct.h). It is up to the
2715 user level program to do useful things with this information. This
2716 is generally a good idea, so say Y.
2720 The sysctl interface provides a means of dynamically changing
2721 certain kernel parameters and variables on the fly without requiring
2722 a recompile of the kernel or reboot of the system. The primary
2723 interface consists of a system call, but if you say Y to "/proc
2724 file system support", a tree of modifiable sysctl entries will be
2725 generated beneath the /proc/sys directory. They are explained in the
2726 files in Documentation/sysctl/. Note that enabling this option will
2727 enlarge the kernel by at least 8 KB.
2729 As it is generally a good thing, you should say Y here unless
2730 building a kernel for install/rescue disks or your system is very
2733 Kernel core (/proc/kcore) format
2735 If you enabled support for /proc file system then the file
2736 /proc/kcore will contain the kernel core image. This can be used
2739 $ cd /usr/src/linux ; gdb vmlinux /proc/kcore
2741 You have two choices here: ELF and A.OUT. Selecting ELF will make
2742 /proc/kcore appear in ELF core format as defined by the Executable
2743 and Linking Format specification. Selecting A.OUT will choose the
2744 old "a.out" format which may be necessary for some old versions
2745 of binutils or on some architectures.
2747 This is especially useful if you have compiled the kernel with the
2748 "-g" option to preserve debugging information. It is mainly used
2749 for examining kernel data structures on the live kernel so if you
2750 don't understand what this means or are not a kernel hacker, just
2751 leave it at its default value ELF.
2753 Kernel support for ELF binaries
2755 ELF (Executable and Linkable Format) is a format for libraries and
2756 executables used across different architectures and operating
2757 systems. Saying Y here will enable your kernel to run ELF binaries
2758 and enlarge it by about 13 KB. ELF support under Linux has now all
2759 but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC)
2760 because it is portable (this does *not* mean that you will be able
2761 to run executables from different architectures or operating systems
2762 however) and makes building run-time libraries very easy. Many new
2763 executables are distributed solely in ELF format. You definitely
2766 Information about ELF is contained in the ELF HOWTO available from
2767 http://www.linuxdoc.org/docs.html#howto .
2769 If you find that after upgrading from Linux kernel 1.2 and saying Y
2770 here, you still can't run any ELF binaries (they just crash), then
2771 you'll have to install the newest ELF runtime libraries, including
2772 ld.so (check the file Documentation/Changes for location and latest
2775 If you want to compile this as a module ( = code which can be
2776 inserted in and removed from the running kernel whenever you want),
2777 say M here and read Documentation/modules.txt. The module will be
2778 called binfmt_elf.o. Saying M or N here is dangerous because some
2779 crucial programs on your system might be in ELF format.
2781 Kernel support for A.OUT binaries
2783 A.out (Assembler.OUTput) is a set of formats for libraries and
2784 executables used in the earliest versions of UNIX. Linux used the
2785 a.out formats QMAGIC and ZMAGIC until they were replaced with the
2788 As more and more programs are converted to ELF, the use for a.out
2789 will gradually diminish. If you disable this option it will reduce
2790 your kernel by one page. This is not much and by itself does not
2791 warrant removing support. However its removal is a good idea if you
2792 wish to ensure that absolutely none of your programs will use this
2793 older executable format. If you don't know what to answer at this
2794 point then answer Y. If someone told you "You need a kernel with
2795 QMAGIC support" then you'll have to say Y here. You may answer M to
2796 compile a.out support as a module and later load the module when you
2797 want to use a program or library in a.out format. The module will be
2798 called binfmt_aout.o. Saying M or N here is dangerous though,
2799 because some crucial programs on your system might still be in A.OUT
2802 Kernel support for Linux/Intel ELF binaries
2804 Say Y here if you want to be able to execute Linux/Intel ELF
2805 binaries just like native Alpha binaries on your Alpha machine. For
2806 this to work, you need to have the emulator /usr/bin/em86 in place.
2808 You can get the same functionality by saying N here and saying Y to
2809 "Kernel support for MISC binaries".
2811 You may answer M to compile the emulation support as a module and
2812 later load the module when you want to use a Linux/Intel binary. The
2813 module will be called binfmt_em86.o. If unsure, say Y.
2815 Kernel support for MISC binaries
2817 If you say Y here, it will be possible to plug wrapper-driven binary
2818 formats into the kernel. You will like this especially when you use
2819 programs that need an interpreter to run like Java, Python or
2820 Emacs-Lisp. It's also useful if you often run DOS executables under
2821 the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
2822 http://www.linuxdoc.org/docs.html#howto ). Once you have
2823 registered such a binary class with the kernel, you can start one of
2824 those programs simply by typing in its name at a shell prompt; Linux
2825 will automatically feed it to the correct interpreter.
2827 You can do other nice things, too. Read the file
2828 Documentation/binfmt_misc.txt to learn how to use this feature, and
2829 Documentation/java.txt for information about how to include Java
2832 You must say Y to "/proc file system support" (CONFIG_PROC_FS) to
2833 use this part of the kernel.
2835 You may say M here for module support and later load the module when
2836 you have use for it; the module is called binfmt_misc.o. If you
2837 don't know what to answer at this point, say Y.
2839 Solaris binary emulation (EXPERIMENTAL)
2841 This is experimental code which will enable you to run (many)
2842 Solaris binaries on your SPARC Linux machine.
2844 This code is also available as a module ( = code which can be
2845 inserted in and removed from the running kernel whenever you want).
2846 The module will be called solaris.o. If you want to compile it as a
2847 module, say M here and read Documentation/modules.txt.
2851 This is the processor type of your CPU. This information is used for
2852 optimizing purposes. In order to compile a kernel that can run on
2853 all x86 CPU types (albeit not optimally fast), you can specify
2856 The kernel will not necessarily run on earlier architectures than
2857 the one you have chosen, e.g. a Pentium optimized kernel will run on
2858 a PPro, but not necessarily on a i486.
2860 Here are the settings recommended for greatest speed:
2861 - "386" for the AMD/Cyrix/Intel 386DX/DXL/SL/SLC/SX, Cyrix/TI
2862 486DLC/DLC2, UMC 486SX-S and NexGen Nx586. Only "386" kernels will
2863 run on a 386 class machine.
2864 - "486" for the AMD/Cyrix/IBM/Intel 486DX/DX2/DX4 or
2865 SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5D or U5S.
2866 - "586" for generic Pentium CPUs, possibly lacking the TSC
2867 (time stamp counter) register.
2868 - "Pentium-Classic" for the Intel Pentium.
2869 - "Pentium-MMX" for the Intel Pentium MMX.
2870 - "Pentium-Pro" for the Intel Pentium Pro/Celeron/Pentium II.
2871 - "Pentium-III" for the Intel Pentium III.
2872 - "Pentium-4" for the Intel Pentium 4
2873 - "K6" for the AMD K6, K6-II and K6-III (aka K6-3D).
2874 - "Athlon" for the AMD Athlon (K7).
2875 - "Crusoe" for the Transmeta Crusoe series.
2876 - "Winchip-C6" for original IDT Winchip.
2877 - "Winchip-2" for IDT Winchip 2.
2878 - "Winchip-2A" for IDT Winchips with 3dNow! capabilities.
2880 If you don't know what to do, choose "386".
2884 Saying Y here will allow you to use Linux in text mode through a
2885 display that complies with the generic VGA standard. Virtually
2886 everyone wants that.
2888 The program SVGATextMode can be used to utilize SVGA video cards to
2889 their full potential in text mode. Download it from
2890 ftp://metalab.unc.edu/pub/Linux/utils/console .
2894 Video mode selection support
2896 This enables support for text mode selection on kernel startup. If
2897 you want to take advantage of some high-resolution text mode your
2898 card's BIOS offers, but the traditional Linux utilities like
2899 SVGATextMode don't, you can say Y here and set the mode using the
2900 "vga=" option from your boot loader (lilo or loadlin) or set
2901 "vga=ask" which brings up a video mode menu on kernel startup. (Try
2902 "man bootparam" or see the documentation of your boot loader about
2903 how to pass options to the kernel.)
2905 Read the file Documentation/svga.txt for more information about the
2906 Video mode selection support. If unsure, say N.
2908 Support for frame buffer devices (EXPERIMENTAL)
2910 The frame buffer device provides an abstraction for the graphics
2911 hardware. It represents the frame buffer of some video hardware and
2912 allows application software to access the graphics hardware through
2913 a well-defined interface, so the software doesn't need to know
2914 anything about the low-level (hardware register) stuff.
2916 Frame buffer devices work identically across the different
2917 architectures supported by Linux and make the implementation of
2918 application programs easier and more portable; at this point, an X
2919 server exists which uses the frame buffer device exclusively.
2920 On several non-X86 architectures, the frame buffer device is the
2921 only way to use the graphics hardware.
2923 The device is accessed through special device nodes, usually located
2924 in the /dev directory, i.e. /dev/fb*.
2926 You need an utility program called fbset to make full use of frame
2927 buffer devices. Please read Documentation/fb/framebuffer.txt and the
2928 Framebuffer-HOWTO at
2929 http://www.tahallah.demon.co.uk/programming/prog.html for more
2932 Say Y here and to the driver for your graphics board below if you
2933 are compiling a kernel for a non-x86 architecture.
2935 If you are compiling for the x86 architecture, you can say Y if you
2936 want to play with it, but it is not essential. Please note that
2937 running graphical applications that directly touch the hardware
2938 (e.g. an accelerated X server) and that are not frame buffer
2939 device-aware may cause unexpected results. If unsure, say N.
2943 This is the frame buffer device driver for the Acorn VIDC graphics
2944 hardware found in Acorn RISC PCs and other ARM-based machines. If
2947 Amiga native chipset support
2949 This is the frame buffer device driver for the builtin graphics
2950 chipset found in Amigas.
2952 The driver is also available as a module ( = code which can be
2953 inserted and removed from the running kernel whenever you want). The
2954 module will be called amifb.o. If you want to compile it as a
2955 module, say M here and read Documentation/modules.txt.
2957 Amiga OCS chipset support
2959 This enables support for the original Agnus and Denise video chips,
2960 found in the Amiga 1000 and most A500's and A2000's. If you intend
2961 to run Linux on any of these systems, say Y; otherwise say N.
2963 Amiga ECS chipset support
2965 This enables support for the Enhanced Chip Set, found in later
2966 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
2967 you intend to run Linux on any of these systems, say Y; otherwise
2970 Amiga AGA chipset support
2972 This enables support for the Advanced Graphics Architecture (also
2973 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
2974 and CD32. If you intend to run Linux on any of these systems, say Y;
2977 Amiga CyberVision support
2979 This enables support for the Cybervision 64 graphics card from
2980 Phase5. Please note that its use is not all that intuitive (i.e. if
2981 you have any questions, be sure to ask!). Say N unless you have a
2982 Cybervision 64 or plan to get one before you next recompile the
2983 kernel. Please note that this driver DOES NOT support the
2984 Cybervision 64 3D card, as they use incompatible video chips.
2986 CyberPro 20x0 support
2988 This enables support for the Integraphics CyberPro 20x0 and 5000
2989 VGA chips used in the Rebel.com Netwinder and other machines.
2990 Say Y if you have a NetWinder or a graphics card containing this
2991 device, otherwise say N.
2993 Amiga CyberVision3D support (EXPERIMENTAL)
2995 This enables support for the Cybervision 64/3D graphics card from
2996 Phase5. Please note that its use is not all that intuitive (i.e. if
2997 you have any questions, be sure to ask!). Say N unless you have a
2998 Cybervision 64/3D or plan to get one before you next recompile the
2999 kernel. Please note that this driver DOES NOT support the older
3000 Cybervision 64 card, as they use incompatible video chips.
3002 Amiga RetinaZ3 support (EXPERIMENTAL)
3004 This enables support for the Retina Z3 graphics card. Say N unless
3005 you have a Retina Z3 or plan to get one before you next recompile
3008 Cirrus Logic generic driver (EXPERIMENTAL)
3010 This enables support for Cirrus Logic GD542x/543x based boards on
3011 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
3013 If you have a PCI-based system, this enables support for these
3014 chips: GD-543x, GD-544x, GD-5480.
3016 Please read the file Documentation/fb/clgenfb.txt.
3018 Say N unless you have such a graphics board or plan to get one
3019 before you next recompile the kernel.
3021 Permedia2 support (EXPERIMENTAL)
3023 Say Y here if this is your graphics board.
3027 Say Y here if you want to run Linux on an MC680x0-based Apollo
3028 Domain workstation such as the DN3500.
3030 Apollo 3c505 support
3031 CONFIG_APOLLO_ELPLUS
3032 Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
3033 If you don't have one made for Apollos, you can use one from a PC,
3034 except that your Apollo won't be able to boot from it (because the
3035 code in the ROM will be for a PC).
3037 Atari native chipset support
3039 This is the frame buffer device driver for the builtin graphics
3040 chipset found in Ataris.
3042 Open Firmware frame buffer device support
3044 Say Y if you want support with Open Firmware for your graphics
3047 S3 Trio frame buffer device support
3049 If you have a S3 Trio say Y. Say N for S3 Virge.
3051 3Dfx Banshee/Voodoo3 display support (EXPERIMENTAL)
3053 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
3054 chips. Say Y if you have such a graphics board.
3056 The driver is also available as a module ( = code which can be
3057 inserted and removed from the running kernel whenever you want). The
3058 module will be called tdfxfb.o. If you want to compile it as a
3059 module, say M here and read Documentation/modules.txt.
3061 nVidia Riva support (EXPERIMENTAL)
3063 This driver supports graphics boards with the nVidia Riva (aka TNTx)
3065 Say Y if you have such a graphics board.
3067 The driver is also available as a module ( = code which can be
3068 inserted and removed from the running kernel whenever you want). The
3069 module will be called rivafb.o. If you want to compile it as a
3070 module, say M here and read Documentation/modules.txt.
3072 ATI Mach64 display support (EXPERIMENTAL)
3074 This driver supports graphics boards with the ATI Mach64 chips.
3075 Say Y if you have such a graphics board.
3077 The driver is also available as a module ( = code which can be
3078 inserted and removed from the running kernel whenever you want). The
3079 module will be called atyfb.o. If you want to compile it as a
3080 module, say M here and read Documentation/modules.txt.
3082 ATI Rage128 display support (EXPERIMENTAL)
3084 This driver supports graphics boards with the ATI Rage128 chips.
3085 Say Y if you have such a graphics board and read
3086 Documentation/fb/aty128fb.txt.
3088 The driver is also available as a module ( = code which can be
3089 inserted and removed from the running kernel whenever you want). The
3090 module will be called aty128fb.o. If you want to compile it as a
3091 module, say M here and read Documentation/modules.txt.
3093 PowerMac "control" frame buffer device support
3095 This driver supports a frame buffer for the graphics adapter in the
3096 Power Macintosh 7300 and others.
3098 PowerMac "platinum" frame buffer device support
3100 This driver supports a frame buffer for the "platinum" graphics
3101 adapter in some Power Macintoshes.
3103 PowerMac "valkyrie" frame buffer device support
3105 This driver supports a frame buffer for the "valkyrie" graphics
3106 adapter in some Power Macintoshes.
3108 Chips 65550 display support
3110 This is the frame buffer device driver for the Chips & Technologies
3111 65550 graphics chip in PowerBooks.
3113 TGA frame buffer support
3115 This is the frame buffer device driver for generic TGA graphic
3116 cards. Say Y if you have one of those.
3118 VESA VGA graphics console
3120 This is the frame buffer device driver for generic VESA 2.0
3121 compliant graphic cards. The older VESA 1.2 cards are not supported.
3122 You will get a boot time penguin logo at no additional cost. Please
3123 read Documentation/fb/vesafb.txt. If unsure, say Y.
3125 VGA 16-color planar support
3126 CONFIG_FBCON_VGA_PLANES
3127 This low level frame buffer console driver enable the kernel to use
3128 the 16-color planar modes of the old VGA cards where the bits of
3129 each pixel are separated into 4 planes.
3131 Only answer Y here if you have a (very old) VGA card that isn't VESA
3134 VGA 16-color graphics console
3136 This is the frame buffer device driver for VGA 16 color graphic
3137 cards. Say Y if you have such a card.
3139 This code is also available as a module. If you want to compile it
3140 as a module ( = code which can be inserted in and removed from the
3141 running kernel whenever you want), say M here and read
3142 Documentation/modules.txt. The module will be called vga16fb.o.
3144 Select other compiled-in fonts
3146 Say Y here if you would like to use fonts other than the default
3147 your frame buffer console usually use.
3149 Note that the answer to this question won't directly affect the
3150 kernel: saying N will just cause this configure script to skip all
3151 the questions about foreign fonts.
3153 If unsure, say N (the default choices are safe).
3157 This is the "high resolution" font for the VGA frame buffer (the one
3158 provided by the VGA text console 80x25 mode.
3162 Support only 8 pixels wide fonts
3163 CONFIG_FBCON_FONTWIDTH8_ONLY
3164 Answer Y here will make the kernel provide only the 8x8 fonts (these
3165 are the less readable).
3169 Sparc console 8x16 font
3171 This is the high resolution console font for Sun machines. Say Y.
3173 Sparc console 12x22 font (not supported by all drivers)
3174 CONFIG_FONT_SUN12x22
3175 This is the high resolution console font for Sun machines with very
3176 big letters (like the letters used in the SPARC PROM). If the
3177 standard font is unreadable for you, say Y, otherwise say N.
3181 This is the "high resolution" font for the VGA frame buffer (the one
3182 provided by the text console 80x50 (and higher) modes).
3184 Note that this is a poor quality font. The VGA 8x16 font is quite a
3187 Given the resolution provided by the frame buffer device, answer N
3190 Backward compatibility mode for Xpmac
3191 CONFIG_FB_COMPAT_XPMAC
3192 If you use the Xpmac X server (common with mklinux), you'll need to
3193 say Y here to use X. You should consider changing to XFree86 which
3194 includes a server that supports the frame buffer device directly
3197 HGA monochrome support (EXPERIMENTAL)
3199 Say Y here if you have a Hercules mono graphics card.
3201 This driver is also available as a module ( = code which can be
3202 inserted and removed from the running kernel whenever you want).
3203 The module will be called hgafb.o. If you want to compile it as
3204 a module, say M here and read Documentation/modules.txt.
3206 As this card technology is 15 years old, most people will answer N
3209 Matrox unified accelerated driver (EXPERIMENTAL)
3211 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
3212 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
3213 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video or
3214 Matrox G400 card in your box. At this time, support for the G100,
3215 Mystique G200 and Marvel G200 is untested.
3217 This driver is also available as a module ( = code which can be
3218 inserted and removed from the running kernel whenever you want).
3219 The module will be called matroxfb.o. If you want to compile it as
3220 a module, say M here and read Documentation/modules.txt.
3222 You can pass several parameters to the driver at boot time or at
3223 module load time. The parameters look like "video=matrox:XXX", where
3224 the meaning of XXX can be found at the end of the main source file
3225 (drivers/video/matroxfb.c). Please see the file
3226 Documentation/fb/matroxfb.txt.
3228 Matrox Millennium support
3229 CONFIG_FB_MATROX_MILLENIUM
3230 Say Y here if you have a Matrox Millennium or Matrox Millennium II
3231 video card. If you select "Advanced lowlevel driver options" below,
3232 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
3233 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
3234 also use font widths different from 8.
3236 Matrox Mystique support
3237 CONFIG_FB_MATROX_MYSTIQUE
3238 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
3239 video card. If you select "Advanced lowlevel driver options" below,
3240 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
3241 packed pixel and 32 bpp packed pixel. You can also use font widths
3244 Matrox G100/G200/G400 support
3245 CONFIG_FB_MATROX_G100
3246 Say Y here if you have a Matrox Productiva G100, Matrox Mystique
3247 G200, Matrox Marvel G200 or Matrox Millennium G200 video card. If
3248 you select "Advanced lowlevel driver options", you should check 8
3249 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed pixel and 32
3250 bpp packed pixel. You can also use font widths different from 8.
3252 If you need support for G400 secondary head, you must first say Y to
3253 "I2C support" and "I2C bit-banging support" in the character devices
3254 section, and then to "Matrox I2C support" and "G400 second head
3255 support" here in the framebuffer section.
3258 CONFIG_FB_MATROX_I2C
3259 This drivers creates I2C buses which are needed for accessing the
3260 DDC (I2C) bus present on all Matroxes, an I2C bus which
3261 interconnects Matrox optional devices, like MGA-TVO on G200 and
3262 G400, and the secondary head DDC bus, present on G400 only.
3264 You can say Y or M here if you want to experiment with monitor
3265 detection code. You must say Y or M here if you want to use either
3266 second head of G400 or MGA-TVO on G200 or G400.
3268 If you compile it as module, it will create a module named
3271 Matrox G400 second head support
3272 CONFIG_FB_MATROX_MAVEN
3273 Say Y or M here if you want to use a secondary head (meaning two
3274 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
3275 head is not compatible with accelerated XFree 3.3.x SVGA servers -
3276 secondary head output is blanked while you are in X. With XFree
3277 3.9.17 preview you can use both heads if you use SVGA over fbdev or
3278 the fbdev driver on first head and the fbdev driver on second head.
3280 If you compile it as module, two modules are created,
3281 matroxfb_crtc2.o and matroxfb_maven.o. Matroxfb_maven is needed for
3282 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
3283 also load i2c-matroxfb to get it to run.
3285 The driver starts in monitor mode and you must use the matroxset
3286 tool (available at ftp://platan.vc.cvut.cz/pub/linux/matrox-latest)
3287 to switch it to PAL or NTSC or to swap primary and secondary head
3288 outputs. Secondary head driver also always start in 640x480
3289 resolution, you must use fbset to change it.
3291 Also do not forget that second head supports only 16 and 32 bpp
3292 packed pixels, so it is a good idea to compile them into the kernel
3293 too. You can use only some font widths, as the driver uses generic
3294 painting procedures (the secondary head does not use acceleration
3297 There is no need for enabling 'Matrox multihead support' if you have
3298 only one Matrox card in the box.
3300 Matrox unified driver multihead support
3301 CONFIG_FB_MATROX_MULTIHEAD
3302 Say Y here if you have more than one (supported) Matrox device in
3303 your computer and you want to use all of them for different monitors
3304 ("multihead"). If you have only one device, you should say N because
3305 the driver compiled with Y is larger and a bit slower, especially on
3308 If you said M to "Matrox unified accelerated driver" and N here, you
3309 will still be able to use several Matrox devices simultaneously:
3310 insert several instances of the module matroxfb.o into the kernel
3311 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
3312 for the different Matrox devices. This method is slightly faster but
3313 uses 40 KB of kernel memory per Matrox card.
3315 MDA text console (dual-headed)
3317 Say Y here if you have an old MDA or monochrome Hercules graphics
3318 adapter in your system acting as a second head ( = video card). You
3319 will then be able to use two monitors with your Linux system. Do not
3320 say Y here if your MDA card is the primary card in your system; the
3321 normal VGA driver will handle it.
3323 This driver is also available as a module ( = code which can be
3324 inserted and removed from the running kernel whenever you want).
3325 The module will be called mdacon.o. If you want to compile it as
3326 a module, say M here and read Documentation/modules.txt.
3330 SBUS and UPA frame buffers
3332 Say Y if you want support for SBUS or UPA based frame buffer device.
3334 Creator/Creator3D support
3336 This is the frame buffer device driver for the Creator and Creator3D
3339 CGsix (GX,TurboGX) support
3341 This is the frame buffer device driver for the CGsix (GX, TurboGX)
3346 This is the frame buffer device driver for the BWtwo frame buffer.
3350 This is the frame buffer device driver for the CGthree frame buffer.
3352 TCX (SS4/SS5 only) support
3354 This is the frame buffer device driver for the TCX 24/8bit frame
3357 Virtual Frame Buffer support (ONLY FOR TESTING!)
3359 This is a `virtual' frame buffer device. It operates on a chunk of
3360 unswapable kernel memory instead of on the memory of a graphics
3361 board. This means you cannot see any output sent to this frame
3362 buffer device, while it does consume precious memory. The main use
3363 of this frame buffer device is testing and debugging the frame
3364 buffer subsystem. Do NOT enable it for normal systems! To protect
3365 the innocent, it has to be enabled explicitly at boot time using the
3366 kernel option `video=vfb:'.
3368 This driver is also available as a module ( = code which can be
3369 inserted and removed from the running kernel whenever you want). The
3370 module will be called vfb.o. If you want to compile it as a module,
3371 say M here and read Documentation/modules.txt.
3376 This is a framebuffer device for the SA-1100 LCD Controller.
3377 See http://www.linux-fbdev.org/ for information on framebuffer
3380 If you plan to use the LCD display with your SA-1100 system, say
3383 Advanced low level driver options
3384 CONFIG_FBCON_ADVANCED
3385 The frame buffer console uses character drawing routines that are
3386 tailored to the specific organization of pixels in the memory of
3387 your graphics hardware. These are called the low level frame buffer
3388 console drivers. Note that they are used for text console output
3389 only; they are NOT needed for graphical applications.
3391 If you say N here, the needed low level drivers are automatically
3392 enabled, depending on what frame buffer devices you selected above.
3393 This is recommended for most users.
3395 If you say Y here, you have more fine-grained control over which low
3396 level drivers are enabled. You can e.g. leave out low level drivers
3397 for color depths you do not intend to use for text consoles.
3399 Low level frame buffer console drivers can be modules ( = code which
3400 can be inserted and removed from the running kernel whenever you
3401 want). The modules will be called fbcon-*.o. If you want to compile
3402 (some of) them as modules, read Documentation/modules.txt.
3408 This is the low level frame buffer console driver for monochrome
3409 (2 colors) packed pixels.
3411 2 bpp packed pixels support
3413 This is the low level frame buffer console driver for 2 bits per
3414 pixel (4 colors) packed pixels.
3416 4 bpp packed pixels support
3418 This is the low level frame buffer console driver for 4 bits per
3419 pixel (16 colors) packed pixels.
3421 8 bpp packed pixels support
3423 This is the low level frame buffer console driver for 8 bits per
3424 pixel (256 colors) packed pixels.
3426 16 bpp packed pixels support
3428 This is the low level frame buffer console driver for 15 or 16 bits
3429 per pixel (32K or 64K colors, also known as `hicolor') packed
3432 24 bpp packed pixels support
3434 This is the low level frame buffer console driver for 24 bits per
3435 pixel (16M colors, also known as `truecolor') packed pixels. It is
3436 NOT for `sparse' 32 bits per pixel mode.
3438 32 bpp packed pixels support
3440 This is the low level frame buffer console driver for 32 bits per
3441 pixel (16M colors, also known as `truecolor') sparse packed pixels.
3443 Amiga bitplanes support
3445 This is the low level frame buffer console driver for 1 to 8
3446 bitplanes (2 to 256 colors) on Amiga.
3448 Amiga interleaved bitplanes support
3450 This is the low level frame buffer console driver for 1 to 8
3451 interleaved bitplanes (2 to 256 colors) on Amiga.
3453 Atari interleaved bitplanes (2 planes) support
3454 CONFIG_FBCON_IPLAN2P2
3455 This is the low level frame buffer console driver for 2 interleaved
3456 bitplanes (4 colors) on Atari.
3458 Atari interleaved bitplanes (4 planes) support
3459 CONFIG_FBCON_IPLAN2P4
3460 This is the low level frame buffer console driver for 4 interleaved
3461 bitplanes (16 colors) on Atari.
3463 Atari interleaved bitplanes (8 planes) support
3464 CONFIG_FBCON_IPLAN2P8
3465 This is the low level frame buffer console driver for 8 interleaved
3466 bitplanes (256 colors) on Atari.
3468 Mac variable bpp packed pixels support
3470 This is the low level frame buffer console driver for 1/2/4/8/16/32
3471 bits per pixel packed pixels on Mac. It supports variable font
3472 widths for low resolution screens.
3474 HGA monochrome support (EXPERIMENTAL)
3476 This is the low level frame buffer console driver for Hercules mono
3479 VGA characters/attributes support
3481 This is the low level frame buffer console driver for VGA text mode;
3482 it is used by frame buffer device drivers that support VGA text
3485 Parallel-port support
3487 If you want to use devices connected to your machine's parallel port
3488 (the connector at the computer with 25 holes), e.g. printer, ZIP
3489 drive, PLIP link (Parallel Line Internet Protocol is mainly used to
3490 create a mini network by connecting the parallel ports of two local
3491 machines) etc., then you need to say Y here; please read
3492 Documentation/parport.txt and drivers/parport/BUGS-parport.
3494 For extensive information about drivers for many devices attaching
3495 to the parallel port see http://www.torque.net/linux-pp.html on the
3498 It is possible to share a single parallel port among several devices
3499 and it is safe to compile all the corresponding drivers into the
3500 kernel. If you want to compile parallel port support as a module ( =
3501 code which can be inserted in and removed from the running kernel
3502 whenever you want), say M here and read Documentation/modules.txt.
3503 The module will be called parport.o. If you have more than one
3504 parallel port and want to specify which port and IRQ to be used by
3505 this driver at module load time, take a look at
3506 Documentation/parport.txt.
3512 You should say Y here if you have a PC-style parallel port. All IBM
3513 PC compatible computers and some Alphas have PC-style parallel
3516 This code is also available as a module. If you want to compile it
3517 as a module ( = code which can be inserted in and removed from the
3518 running kernel whenever you want), say M here and read
3519 Documentation/modules.txt. The module will be called parport_pc.o.
3523 Use FIFO/DMA if available
3524 CONFIG_PARPORT_PC_FIFO
3525 Many parallel port chipsets provide hardware that can speed up
3526 printing. Say Y here if you want to take advantage of that.
3528 As well as actually having a FIFO, or DMA capability, the kernel
3529 will need to know which IRQ the parallel port has. By default,
3530 parallel port interrupts will not be used, and so neither will the
3531 FIFO. See Documentation/parport.txt to find out how to specify
3532 which IRQ/DMA to use.
3534 SuperIO chipset support (EXPERIMENTAL)
3535 CONFIG_PARPORT_PC_SUPERIO
3536 Saying Y here enables some probes for Super-IO chipsets in order to
3537 find out things like base addresses, IRQ lines and DMA channels. It
3540 Support for PCMCIA management for PC-style ports
3541 CONFIG_PARPORT_PC_PCMCIA
3542 Say Y here if you need PCMCIA support for your PC-style parallel
3543 ports. If unsure, say N.
3545 Support foreign hardware
3546 CONFIG_PARPORT_OTHER
3547 Say Y here if you want to be able to load driver modules to support
3548 other non-standard types of parallel ports. This causes a
3549 performance loss, so most people say N.
3551 Support IEEE1284 status readback
3552 CONFIG_PRINTER_READBACK
3553 If you have a device on your parallel port that support this
3554 protocol, this option will allow the device to report its status. It
3557 IEEE1284 transfer modes
3559 If you have a printer that supports status readback or device ID, or
3560 want to use a device that uses enhanced parallel port transfer modes
3561 such as EPP and ECP, say Y here to enable advanced IEEE 1284
3562 transfer modes. Also say Y if you want device ID information to
3563 appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
3565 Enable loadable module support
3567 Kernel modules are small pieces of compiled code which can be
3568 inserted in or removed from the running kernel, using the programs
3569 insmod and rmmod. This is described in the file
3570 Documentation/modules.txt, including the fact that you have to say
3571 "make modules" in order to compile the modules that you chose during
3572 kernel configuration. Modules can be device drivers, file systems,
3573 binary executable formats, and so on. If you think that you may want
3574 to make use of modules with this kernel in the future, then say Y
3575 here. If unsure, say Y.
3577 Set version information on all symbols for modules
3579 Usually, modules have to be recompiled whenever you switch to a new
3580 kernel. Saying Y here makes it possible, and safe, to use the
3581 same modules even after compiling a new kernel; this requires the
3582 program modprobe. All the software needed for module support is in
3583 the modutils package (check the file Documentation/Changes for
3584 location and latest version). NOTE: if you say Y here but don't
3585 have the program genksyms (which is also contained in the above
3586 mentioned modutils package), then the building of your kernel will
3587 fail. If you are going to use modules that are generated from
3588 non-kernel sources, you would benefit from this option. Otherwise
3589 it's not that important. So, N ought to be a safe bet.
3591 Kernel module loader support
3593 Normally when you have selected some drivers and/or file systems to
3594 be created as loadable modules, you also have the responsibility to
3595 load the corresponding modules (using the programs insmod or
3596 modprobe) before you can use them. If you say Y here however, the
3597 kernel will be able to load modules for itself: when a part of the
3598 kernel needs a module, it runs modprobe with the appropriate
3599 arguments, thereby loading the module if it is available. (This is a
3600 replacement for kerneld.) Say Y here and read about configuring it
3601 in Documentation/kmod.txt.
3603 ARP daemon support (EXPERIMENTAL)
3605 Normally, the kernel maintains an internal cache which maps IP
3606 addresses to hardware addresses on the local network, so that
3607 Ethernet/Token Ring/ etc. frames are sent to the proper address on
3608 the physical networking layer. For small networks having a few
3609 hundred directly connected hosts or less, keeping this address
3610 resolution (ARP) cache inside the kernel works well. However,
3611 maintaining an internal ARP cache does not work well for very large
3612 switched networks, and will use a lot of kernel memory if TCP/IP
3613 connections are made to many machines on the network.
3615 If you say Y here, the kernel's internal ARP cache will never grow
3616 to more than 256 entries (the oldest entries are expired in a LIFO
3617 manner) and communication will be attempted with the user space ARP
3618 daemon arpd. Arpd then answers the address resolution request either
3619 from its own cache or by asking the net.
3621 This code is experimental and also obsolete. If you want to use it,
3622 you need to find a version of the daemon arpd on the net somewhere,
3623 and you should also say Y to "Kernel/User network link driver",
3624 below. If unsure, say N.
3628 These are the protocols used on the Internet and on most local
3629 Ethernets. It is highly recommended to say Y here (this will enlarge
3630 your kernel by about 144 KB), since some programs (e.g. the X window
3631 system) use TCP/IP even if your machine is not connected to any
3632 other computer. You will get the so-called loopback device which
3633 allows you to ping yourself (great fun, that!).
3635 For an excellent introduction to Linux networking, please read the
3636 NET-3-HOWTO, available from
3637 http://www.linuxdoc.org/docs.html#howto .
3639 This option is also necessary if you want to use the full power of
3640 term (term is a program which gives you almost full Internet
3641 connectivity if you have a regular dial up shell account on some
3642 Internet connected Unix computer; for more information, read
3643 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html ).
3645 If you say Y here and also to "/proc file system support" and
3646 "Sysctl support" below, you can change various aspects of the
3647 behavior of the TCP/IP code by writing to the (virtual) files in
3648 /proc/sys/net/ipv4/*; the options are explained in the file
3649 Documentation/networking/ip-sysctl.txt.
3651 Short answer: say Y.
3655 This is code for addressing several networked computers at once,
3656 enlarging your kernel by about 2 KB. You need multicasting if you
3657 intend to participate in the MBONE, a high bandwidth network on top
3658 of the Internet which carries audio and video broadcasts. More
3659 information about the MBONE is on the WWW at
3660 http://www-itg.lbl.gov/mbone/ . Information about the multicast
3661 capabilities of the various network cards is contained in
3662 Documentation/networking/multicast.txt. For most people, it's safe
3666 CONFIG_IP_ADVANCED_ROUTER
3667 If you intend to run your Linux box mostly as a router, i.e. as a
3668 computer that forwards and redistributes network packets, say Y; you
3669 will then be presented with several options that allow more precise
3670 control about the routing process.
3672 The answer to this question won't directly affect the kernel:
3673 answering N will just cause this configure script to skip all the
3674 questions about advanced routing.
3676 Note that your box can only act as a router if you enable IP
3677 forwarding in your kernel; you can do that by saying Y to "/proc
3678 file system support" and "Sysctl support" below and executing the
3681 echo "1" > /proc/sys/net/ipv4/ip_forward
3683 at boot time after the /proc file system has been mounted.
3685 If you turn on IP forwarding, you will also get the rp_filter, which
3686 automatically rejects incoming packets if the routing table entry
3687 for their source address doesn't match the network interface they're
3688 arriving on. This has security advantages because it prevents the
3689 so-called IP spoofing, however it can pose problems if you use
3690 asymmetric routing (packets from you to a host take a different path
3691 than packets from that host to you) or if you operate a non-routing
3692 host which has several IP addresses on different interfaces. To turn
3695 echo 0 > /proc/sys/net/ipv4/conf/<device>/rp_filter
3697 echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter
3699 If unsure, say N here.
3702 CONFIG_IP_MULTIPLE_TABLES
3703 Normally, a router decides what to do with a received packet based
3704 solely on the packet's final destination address. If you say Y here,
3705 the Linux router will also be able to take the packet's source
3706 address into account. Furthermore, if you also say Y to "IP: use TOS
3707 value as routing key" below, the TOS (Type-Of-Service) field of the
3708 packet can be used for routing decisions as well. In addition, if
3709 you say Y here and to "IP: fast network address translation" below,
3710 the router will also be able to modify source and destination
3711 addresses of forwarded packets.
3713 If you are interested in this, please see the preliminary
3714 documentation at http://www.compendium.com.ar/policy-routing.txt and
3715 ftp://post.tepkom.ru/pub/vol2/Linux/docs/advanced-routing.tex . You
3716 will need supporting software from ftp://ftp.inr.ac.ru/ip-routing/
3720 IP: equal cost multipath
3721 CONFIG_IP_ROUTE_MULTIPATH
3722 Normally, the routing tables specify a single action to be taken in
3723 a deterministic manner for a given packet. If you say Y here
3724 however, it becomes possible to attach several actions to a packet
3725 pattern, in effect specifying several alternative paths to travel
3726 for those packets. The router considers all these paths to be of
3727 equal "cost" and chooses one of them in a non-deterministic fashion
3728 if a matching packet arrives.
3730 IP: use TOS value as routing key
3732 The header of every IP packet carries a TOS (Type Of Service) value
3733 with which the packet requests a certain treatment, e.g. low latency
3734 (for interactive traffic), high throughput, or high reliability. If
3735 you say Y here, you will be able to specify different routes for
3736 packets with different TOS values.
3738 IP: use netfilter MARK value as routing key
3739 CONFIG_IP_ROUTE_FWMARK
3740 If you say Y here, you will be able to specify different routes for
3741 packets with different mark values (see iptables(8), MARK target).
3743 IP: verbose route monitoring
3744 CONFIG_IP_ROUTE_VERBOSE
3745 If you say Y here, which is recommended, then the kernel will print
3746 verbose messages regarding the routing, for example warnings about
3747 received packets which look strange and could be evidence of an
3748 attack or a misconfigured system somewhere. The information is
3749 handled by the klogd daemon which is responsible for kernel messages
3752 IP: large routing tables
3753 CONFIG_IP_ROUTE_LARGE_TABLES
3754 If you have routing zones that grow to more than about 64 entries,
3755 you may want to say Y here to speed up the routing process.
3757 IP: fast network address translation
3759 If you say Y here, your router will be able to modify source and
3760 destination addresses of packets that pass through it, in a manner
3761 you specify. General information about Network Address Translation
3762 can be gotten from the document
3763 http://www.csn.tu-chemnitz.de/~mha/linux-ip-nat/diplom/nat.html
3765 IP: kernel level autoconfiguration
3767 This enables automatic configuration of IP addresses of devices and
3768 of the routing table during kernel boot, based on either information
3769 supplied on the kernel command line or by BOOTP or RARP protocols.
3770 You need to say Y only for diskless machines requiring network
3771 access to boot (in which case you want to say Y to "Root file system
3772 on NFS" as well), because all other machines configure the network
3773 in their startup scripts.
3777 If you want your Linux box to mount its whole root file system (the
3778 one containing the directory /) from some other computer over the
3779 net via NFS and you want the IP address of your computer to be
3780 discovered automatically at boot time using the BOOTP protocol (a
3781 special protocol designed for doing this job), say Y here. In case
3782 the boot ROM of your network card was designed for booting Linux and
3783 does BOOTP itself, providing all necessary information on the kernel
3784 command line, you can say N here. If unsure, say Y. Note that if you
3785 want to use BOOTP, a BOOTP server must be operating on your network.
3786 Read Documentation/nfsroot.txt for details.
3790 If you want your Linux box to mount its whole root file system (the
3791 one containing the directory /) from some other computer over the
3792 net via NFS and you want the IP address of your computer to be
3793 discovered automatically at boot time using the RARP protocol (an
3794 older protocol which is being obsoleted by BOOTP and DHCP), say Y
3795 here. Note that if you want to use RARP, a RARP server must be
3796 operating on your network. Read Documentation/nfsroot.txt for
3801 Tunneling means encapsulating data of one protocol type within
3802 another protocol and sending it over a channel that understands the
3803 encapsulating protocol. This particular tunneling driver implements
3804 encapsulation of IP within IP, which sounds kind of pointless, but
3805 can be useful if you want to make your (or some other) machine
3806 appear on a different network than it physically is, or to use
3807 mobile-IP facilities (allowing laptops to seamlessly move between
3808 networks without changing their IP addresses; check out
3809 http://anchor.cs.binghamton.edu/~mobileip/LJ/index.html ).
3811 Saying Y to this option will produce two modules ( = code which can
3812 be inserted in and removed from the running kernel whenever you
3813 want). Most people won't need this and can say N.
3815 IP: GRE tunnels over IP
3817 Tunneling means encapsulating data of one protocol type within
3818 another protocol and sending it over a channel that understands the
3819 encapsulating protocol. This particular tunneling driver implements
3820 GRE (Generic Routing Encapsulation) and at this time allows
3821 encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
3822 This driver is useful if the other endpoint is a Cisco router: Cisco
3823 likes GRE much better than the other Linux tunneling driver ("IP:
3824 tunneling" above). In addition, GRE allows multicast redistribution
3827 IP: broadcast GRE over IP
3828 CONFIG_NET_IPGRE_BROADCAST
3829 One application of GRE/IP is to construct a broadcast WAN (Wide Area
3830 Network), which looks like a normal Ethernet LAN (Local Area
3831 Network), but can be distributed all over the Internet. If you want
3832 to do that, say Y here and to "IP: multicast routing" below.
3834 IP: multicast routing
3836 This is used if you want your machine to act as a router for IP
3837 packets that have several destination addresses. It is needed on the
3838 MBONE, a high bandwidth network on top of the Internet which carries
3839 audio and video broadcasts. In order to do that, you would most
3840 likely run the program mrouted. Information about the multicast
3841 capabilities of the various network cards is contained in
3842 Documentation/networking/multicast.txt. If you haven't heard about
3843 it, you don't need it.
3845 IP: PIM-SM version 1 support
3847 Kernel side support for Sparse Mode PIM (Protocol Independent
3848 Multicast) version 1. This multicast routing protocol is used widely
3849 because Cisco supports it. You need special software to use it
3850 (pimd-v1). Please see http://netweb.usc.edu/pim/ for more
3851 information about PIM.
3853 Say Y if you want to use PIM-SM v1. Note that you can say N here if
3854 you just want to use Dense Mode PIM.
3856 IP: PIM-SM version 2 support
3858 Kernel side support for Sparse Mode PIM version 2. In order to use
3859 this, you need an experimental routing daemon supporting it (pimd or
3860 gated-5). This routing protocol is not used widely, so say N unless
3861 you want to play with it.
3863 PC/TCP compatibility mode
3865 If you have been having difficulties telnetting to your Linux
3866 machine from a DOS system that uses (broken) PC/TCP networking
3867 software (all versions up to OnNet 2.0) over your local Ethernet try
3868 saying Y here. Everyone else says N.
3870 People having problems with NCSA telnet should see the file
3871 Documentation/networking/ncsa-telnet.
3873 Path MTU Discovery (normally enabled)
3874 CONFIG_PATH_MTU_DISCOVERY
3875 MTU (maximal transfer unit) is the size of the chunks we send out
3876 over the net. "Path MTU Discovery" means that, instead of always
3877 sending very small chunks, we start out sending big ones and if we
3878 then discover that some host along the way likes its chunks smaller,
3879 we adjust to a smaller size. This is good, so most people say Y
3882 However, some DOS software (versions of DOS NCSA telnet and Trumpet
3883 Winsock in PPP mode) is broken and won't be able to connect to your
3884 Linux machine correctly in all cases (especially through a terminal
3885 server) unless you say N here. See
3886 Documentation/networking/ncsa-telnet for the location of fixed NCSA
3887 telnet clients. If in doubt, say Y.
3889 Disable NAGLE algorithm (normally enabled)
3890 CONFIG_TCP_NAGLE_OFF
3891 The NAGLE algorithm works by requiring an acknowledgment before
3892 sending small IP frames (packets). This keeps tiny telnet and
3893 rlogin packets from congesting Wide Area Networks. Most people
3894 strongly recommend to say N here, thereby leaving NAGLE
3895 enabled. Those programs that would benefit from disabling this
3896 facility can do it on a per connection basis themselves.
3898 IP: Allow large windows (not recommended if <16 MB of memory)
3900 On high speed, long distance networks the performance limit on
3901 networking becomes the amount of data the sending machine can buffer
3902 until the other end confirms its reception. (At 45 Mbit/second there
3903 are a lot of bits between New York and London ...). If you say Y
3904 here, bigger buffers can be used which allows larger amounts of data
3905 to be "in flight" at any given time. It also means a user process
3906 can require a lot more memory for network buffers and thus this
3907 option is best used only on machines with 16 MB of memory or higher.
3908 Unless you are using long links with end to end speeds of over 2
3909 Mbit a second or satellite links this option will make no difference
3914 If you say Y here, you will include support for Unix domain sockets;
3915 sockets are the standard Unix mechanism for establishing and
3916 accessing network connections. Many commonly used programs such as
3917 the X Window system and syslog use these sockets even if your
3918 machine is not connected to any network. Unless you are working on
3919 an embedded system or something similar, you therefore definitely
3922 However, the socket support is also available as a module ( = code
3923 which can be inserted in and removed from the running kernel
3924 whenever you want). If you want to compile it as a module, say M
3925 here and read Documentation/modules.txt. The module will be called
3926 unix.o. If you try building this as a module and you have said Y to
3927 "Kernel module loader support" above, be sure to add 'alias net-pf-1
3928 unix' to your /etc/modules.conf file. Note that several important
3929 services won't work correctly if you say M here and then neglect to
3932 Say Y unless you know what you are doing.
3934 The IPv6 protocol (EXPERIMENTAL)
3936 This is experimental support for the next version of the Internet
3937 Protocol: IP version 6 (also called IPng "IP next generation").
3938 Features of this new protocol include: expanded address space,
3939 authentication and privacy, and seamless interoperability with the
3940 current version of IP (IP version 4). For general information about
3941 IPv6, see http://playground.sun.com/pub/ipng/html/ipng-main.html ;
3942 for specific information about IPv6 under Linux read the HOWTO at
3943 http://www.bieringer.de/linux/IPv6/ and the file net/ipv6/README in
3946 If you want to use IPv6, please upgrade to the newest net-tools as
3947 given in Documentation/Changes. You will still be able to do regular
3948 IPv4 networking as well.
3950 This protocol support is also available as a module ( = code which
3951 can be inserted in and removed from the running kernel whenever you
3952 want). The module will be called ipv6.o. If you want to compile it
3953 as a module, say M here and read Documentation/modules.txt.
3955 It is safe to say N here for now.
3957 IPv6: enable EUI-64 token format
3959 6bone, the network of computers using the IPv6 protocol, is moving
3960 to a new aggregatable address format and a new link local address
3961 assignment (EUI-64). Say Y if your site has upgraded already, or
3962 has started to upgrade.
3964 IPv6: disable provider based addresses
3966 Linux tries to operate correctly when your site has moved to EUI-64
3967 only partially. Unfortunately, the two address formats (old:
3968 "provider based" and new: "aggregatable") are incompatible. Say Y if
3969 your site finished the upgrade to EUI-64, and/or you encountered
3970 some problems caused by the presence of two link-local addresses on
3973 IPv6: routing messages via old netlink
3975 You can say Y here to receive routing messages from the IPv6 code
3976 through the old netlink interface. However, a better option is to
3977 say Y to "Kernel/User network link driver" and to "Routing
3980 Kernel httpd acceleration (EXPERIMENTAL)
3982 The kernel httpd acceleration daemon (kHTTPd) is a (limited) web
3983 server built into the kernel. It is limited since it can only serve
3984 files from the file system and cannot deal with executable content
3985 such as CGI scripts. Serving files is sped up if you use kHTTPd.
3986 If kHTTPd is not able to fulfill a request, it can transparently
3987 pass it through to a user space web server such as apache.
3989 Saying "M" here builds the kHTTPd module; this is NOT enough to have
3990 a working kHTTPd. For safety reasons, the module has to be activated
3991 by doing a "echo 1 > /proc/sys/net/khttpd/start" after inserting the
3994 Before using this, read the README in net/khttpd !
3996 The kHTTPd is experimental. Be careful when using it on a production
3997 machine. Also note that kHTTPd doesn't support virtual servers yet.
4001 This is support for the Novell networking protocol, IPX, commonly
4002 used for local networks of Windows machines. You need it if you want
4003 to access Novell NetWare file or print servers using the Linux
4004 Novell client ncpfs (available from
4005 ftp://metalab.unc.edu/pub/Linux/system/filesystems/ ) or from within
4006 the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
4007 http://www.linuxdoc.org/docs.html#howto ). In order to do the
4008 former, you'll also have to say Y to "NCP file system support",
4011 IPX is similar in scope to IP, while SPX, which runs on top of IPX,
4012 is similar to TCP. There is also experimental support for SPX in
4013 Linux (see "SPX networking", below).
4015 To turn your Linux box into a fully featured NetWare file server and
4016 IPX router, say Y here and fetch either lwared from
4017 ftp://metalab.unc.edu/pub/Linux/system/network/daemons/ or mars_nwe
4018 from ftp://ftp.gwdg.de/pub/linux/misc/ncpfs . For more information,
4019 read the IPX-HOWTO available from
4020 http://www.linuxdoc.org/docs.html#howto .
4022 General information about how to connect Linux, Windows machines and
4023 Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
4025 The IPX driver would enlarge your kernel by about 16 KB. This driver
4026 is also available as a module ( = code which can be inserted in and
4027 removed from the running kernel whenever you want). The module will
4028 be called ipx.o. If you want to compile it as a module, say M here
4029 and read Documentation/modules.txt. Unless you want to integrate
4030 your Linux box with a local Novell network, say N.
4032 IPX: Full internal IPX network
4034 Every IPX network has an address that identifies it. Sometimes it is
4035 useful to give an IPX "network" address to your Linux box as well
4036 (for example if your box is acting as a file server for different
4037 IPX networks: it will then be accessible from everywhere using the
4038 same address). The way this is done is to create a virtual internal
4039 "network" inside your box and to assign an IPX address to this
4040 network. Say Y here if you want to do this; read the IPX-HOWTO at
4041 http://www.linuxdoc.org/docs.html#howto for details.
4043 The full internal IPX network enables you to allocate sockets on
4044 different virtual nodes of the internal network. This is done by
4045 evaluating the field sipx_node of the socket address given to the
4046 bind call. So applications should always initialize the node field
4047 to 0 when binding a socket on the primary network. In this case the
4048 socket is assigned the default node that has been given to the
4049 kernel when the internal network was created. By enabling the full
4050 internal IPX network the cross-forwarding of packets targeted at
4051 'special' sockets to sockets listening on the primary network is
4052 disabled. This might break existing applications, especially RIP/SAP
4053 daemons. A RIP/SAP daemon that works well with the full internal net
4054 can be found on ftp://ftp.gwdg.de/pub/linux/misc/ncpfs .
4056 If you don't know what you are doing, say N.
4058 IPX: SPX networking (EXPERIMENTAL)
4060 The Sequenced Packet eXchange protocol is a transport layer protocol
4061 built on top of IPX. It is used in Novell NetWare systems for
4062 client-server applications and is similar to TCP (which runs on top
4065 Note that Novell NetWare file sharing does not use SPX; it uses a
4066 protocol called NCP, for which separate Linux support is available
4067 ("NCP file system support" below for the client side, and the user
4068 space programs lwared or mars_nwe for the server side).
4070 Say Y here if you have use for SPX; read the IPX-HOWTO at
4071 http://www.linuxdoc.org/docs.html#howto for details.
4073 This driver is also available as a module ( = code which can be
4074 inserted in and removed from the running kernel whenever you want).
4075 The module will be called af_spx.o. If you want to compile it as a
4076 module, say M here and read Documentation/modules.txt.
4078 DECnet networking (EXPERIMENTAL)
4080 The DECnet networking protocol was used in many products made by
4081 Digital (now Compaq). It provides reliable stream and sequenced
4082 packet communications over which run a variety of services similar
4083 to those which run over TCP/IP.
4085 To find some tools to use with the kernel layer support, please
4086 look at Patrick Caulfield's web site:
4087 http://linux.dreamtime.org/decnet/
4089 More detailed documentation is available in the
4090 Documentation/networking/decnet.txt file.
4092 Be sure to say Y to "/proc file system support" and "Sysctl support"
4093 below when using DECnet, since you will need sysctl support to aid
4094 in configuration at run time.
4096 The DECnet code is also available as a module ( = code which can be
4097 inserted in and removed from the running kernel whenever you want).
4098 The module is called decnet.o.
4100 DECnet SIOCFIGCONF support
4101 CONFIG_DECNET_SIOCGIFCONF
4102 This option should only be turned on if you are really sure that
4103 you know what you are doing. It can break other applications which
4104 use this system call and the proper way to get the information
4105 provided by this call is to use rtnetlink.
4109 DECnet Router Support (EXPERIMENTAL)
4110 CONFIG_DECNET_ROUTER
4111 Add support for turning your DECnet Endnode into a level 1 or 2
4112 router. This is an unfinished option for developers only. If you do
4113 say Y here, then make sure that you also say Y to "Kernel/User
4114 network link driver", "Routing messages" and "Network packet
4115 filtering". The first two are required to allow configuration via
4116 rtnetlink (currently you need Alexey Kuznetsov's iproute2 package
4117 from ftp://ftp.inr.ac.ru). The "Network packet filtering" option
4118 will be required for the forthcoming routing daemon to work.
4120 See Documentation/networking/decnet.txt for more information.
4122 DECnet: use FWMARK value as routing key
4123 CONFIG_DECNET_ROUTE_FWMARK
4124 If you say Y here, you will be able to specify different routes for
4125 packets with different FWMARK ("firewalling mark") values
4126 (see ipchains(8), "-m" argument).
4128 Appletalk interfaces support
4130 AppleTalk is the way Apple computers speak to each other on a
4131 network. If your Linux box is connected to such a network and you
4132 want to join the conversation, say Y.
4134 AppleTalk protocol support
4136 AppleTalk is the way Apple computers speak to each other on a
4137 network. If your Linux box is connected to such a network and you
4138 want to join the conversation, say Y. You will need to use the
4139 netatalk package so that your Linux box can act as a print and file
4140 server for Macs as well as access AppleTalk printers. Check out
4141 http://threepio.hitchcock.org/cgi-bin/faq/netatalk/faq.pl on the WWW
4142 for details. EtherTalk is the name used for AppleTalk over Ethernet
4143 and the cheaper and slower LocalTalk is AppleTalk over a proprietary
4144 Apple network using serial links. EtherTalk and LocalTalk are fully
4147 General information about how to connect Linux, Windows machines and
4148 Macs is on the WWW at http://www.eats.com/linux_mac_win.html . The
4149 NET-3-HOWTO, available from
4150 http://www.linuxdoc.org/docs.html#howto , contains valuable
4151 information as well.
4153 This driver is also available as a module ( = code which can be
4154 inserted in and removed from the running kernel whenever you want).
4155 The module is called appletalk.o. If you want to compile it as a
4156 module, say M here and read Documentation/modules.txt. I hear that
4157 the GNU boycott of Apple is over, so even politically correct people
4158 are allowed to say Y here.
4160 AppleTalk-IP driver support
4162 This allows IP networking for users who only have AppleTalk
4163 networking available. This feature is experimental. With this
4164 driver, you can encapsulate IP inside AppleTalk (e.g. if your Linux
4165 box is stuck on an AppleTalk only network) or decapsulate (e.g. if
4166 you want your Linux box to act as an Internet gateway for a zoo of
4167 AppleTalk connected Macs). Please see the file
4168 Documentation/networking/ipddp.txt for more information.
4170 If you say Y here, the AppleTalk-IP support will be compiled into
4171 the kernel. In this case, you can either use encapsulation or
4172 decapsulation, but not both. With the following two questions, you
4173 decide which one you want.
4175 If you say M here, the AppleTalk-IP support will be compiled as a
4176 module ( = code which can be inserted in and removed from the
4177 running kernel whenever you want, read Documentation/modules.txt).
4178 The module is called ipddp.o. In this case, you will be able to use
4179 both encapsulation and decapsulation simultaneously, by loading two
4180 copies of the module and specifying different values for the module
4183 IP to AppleTalk-IP Encapsulation support
4185 If you say Y here, the AppleTalk-IP code will be able to encapsulate
4186 IP packets inside AppleTalk frames; this is useful if your Linux box
4187 is stuck on an AppleTalk network (which hopefully contains a
4188 decapsulator somewhere). Please see
4189 Documentation/networking/ipddp.txt for more information. If you said
4190 Y to "AppleTalk-IP driver support" above and you say Y here, then
4191 you cannot say Y to "AppleTalk-IP to IP Decapsulation support",
4194 AppleTalk-IP to IP Decapsulation support
4196 If you say Y here, the AppleTalk-IP code will be able to decapsulate
4197 AppleTalk-IP frames to IP packets; this is useful if you want your
4198 Linux box to act as an Internet gateway for an AppleTalk network.
4199 Please see Documentation/networking/ipddp.txt for more information.
4200 If you said Y to "AppleTalk-IP driver support" above and you say Y
4201 here, then you cannot say Y to "IP to AppleTalk-IP Encapsulation
4204 Apple/Farallon LocalTalk PC card support
4206 This allows you to use the AppleTalk PC card to connect to LocalTalk
4207 networks. The card is also known as the Farallon PhoneNet PC card.
4208 If you are in doubt, this card is the one with the 65C02 chip on it.
4209 You also need version 1.3.3 or later of the netatalk package.
4210 This driver is experimental, which means that it may not work.
4211 See the file Documentation/networking/ltpc.txt.
4213 COPS LocalTalk PC card support
4215 This allows you to use COPS AppleTalk cards to connect to LocalTalk
4216 networks. You also need version 1.3.3 or later of the netatalk
4217 package. This driver is experimental, which means that it may not
4218 work. This driver will only work if you choose "AppleTalk DDP"
4219 networking support, above.
4220 Please read the file Documentation/networking/cops.txt.
4222 Dayna firmware support
4224 Support COPS compatible cards with Dayna style firmware (Dayna
4225 DL2000/ Daynatalk/PC (half length), COPS LT-95, Farallon PhoneNET PC
4226 III, Farallon PhoneNET PC II).
4228 Tangent firmware support
4230 Support COPS compatible cards with Tangent style firmware (Tangent
4231 ATB_II, Novell NL-1000, Daystar Digital LT-200.
4233 Amateur Radio support
4235 If you want to connect your Linux box to an amateur radio, answer Y
4236 here. You want to read http://www.tapr.org/tapr/html/pkthome.html
4237 and the HAM-HOWTO and the AX25-HOWTO, both available from
4238 http://www.linuxdoc.org/docs.html#howto .
4240 Note that the answer to this question won't directly affect the
4241 kernel: saying N will just cause this configure script to skip all
4242 the questions about amateur radio.
4244 Amateur Radio AX.25 Level 2
4246 This is the protocol used for computer communication over amateur
4247 radio. It is either used by itself for point-to-point links, or to
4248 carry other protocols such as tcp/ip. To use it, you need a device
4249 that connects your Linux box to your amateur radio. You can either
4250 use a low speed TNC (a Terminal Node Controller acts as a kind of
4251 modem connecting your computer's serial port to your radio's
4252 microphone input and speaker output) supporting the KISS protocol or
4253 one of the various SCC cards that are supported by the generic Z8530
4254 or the DMA SCC driver. Another option are the Baycom modem serial
4255 and parallel port hacks or the sound card modem (supported by their
4256 own drivers). If you say Y here, you also have to say Y to one of
4259 Information about where to get supporting software for Linux amateur
4260 radio as well as information about how to configure an AX.25 port is
4261 contained in the AX25-HOWTO, available from
4262 http://www.linuxdoc.org/docs.html#howto . You might also want to
4263 check out the file Documentation/networking/ax25.txt in the kernel
4264 source. More information about digital amateur radio in general is
4265 on the WWW at http://www.tapr.org/tapr/html/pkthome.html .
4267 This driver is also available as a module ( = code which can be
4268 inserted in and removed from the running kernel whenever you want).
4269 The module will be called ax25.o. If you want to compile it as a
4270 module, say M here and read Documentation/modules.txt.
4272 AX.25 DAMA Slave support
4273 CONFIG_AX25_DAMA_SLAVE
4274 DAMA is a mechanism to prevent collisions when doing AX.25
4275 networking. A DAMA server (called "master") accepts incoming traffic
4276 from clients (called "slaves") and redistributes it to other slaves.
4277 If you say Y here, your Linux box will act as a DAMA slave; this is
4278 transparent in that you don't have to do any special DAMA
4279 configuration. (Linux cannot yet act as a DAMA server.) If unsure,
4282 AX.25 DAMA Master support
4283 CONFIG_AX25_DAMA_MASTER
4284 DAMA is a mechanism to prevent collisions when doing AX.25
4285 networking. A DAMA server (called "master") accepts incoming traffic
4286 from clients (called "slaves") and redistributes it to other
4287 slaves. If you say Y here, your Linux box will act as a DAMA server.
4290 Amateur Radio NET/ROM
4292 NET/ROM is a network layer protocol on top of AX.25 useful for
4295 A comprehensive listing of all the software for Linux amateur radio
4296 users as well as information about how to configure an AX.25 port is
4297 contained in the AX25-HOWTO, available from
4298 http://www.linuxdoc.org/docs.html#howto . You also might want to
4299 check out the file Documentation/networking/ax25.txt. More
4300 information about digital amateur radio in general is on the WWW at
4301 http://www.tapr.org/tapr/html/pkthome.html .
4303 This driver is also available as a module ( = code which can be
4304 inserted in and removed from the running kernel whenever you want).
4305 The module will be called netrom.o. If you want to compile it as a
4306 module, say M here and read Documentation/modules.txt.
4308 Amateur Radio X.25 PLP (Rose)
4310 The Packet Layer Protocol (PLP) is a way to route packets over X.25
4311 connections in general and amateur radio AX.25 connections in
4312 particular, essentially an alternative to NET/ROM.
4314 A comprehensive listing of all the software for Linux amateur radio
4315 users as well as information about how to configure an AX.25 port is
4316 contained in the AX25-HOWTO, available from
4317 http://www.linuxdoc.org/docs.html#howto . You also might want to
4318 check out the file Documentation/networking/ax25.txt. More
4319 information about digital amateur radio in general is on the WWW at
4320 http://www.tapr.org/tapr/html/pkthome.html .
4322 This driver is also available as a module ( = code which can be
4323 inserted in and removed from the running kernel whenever you want).
4324 The module will be called rose.o. If you want to compile it as a
4325 module, say M here and read Documentation/modules.txt.
4327 Serial port KISS driver for AX.25
4329 KISS is a protocol used for the exchange of data between a computer
4330 and a Terminal Node Controller (a small embedded system commonly
4331 used for networking over AX.25 amateur radio connections; it
4332 connects the computer's serial port with the radio's microphone
4333 input and speaker output).
4335 Although KISS is less advanced than the 6pack protocol, it has
4336 the advantage that it is already supported by most modern TNCs
4337 without the need for a firmware upgrade.
4339 If you want to compile this driver as a module ( = code which can be
4340 inserted in and removed from the running kernel whenever you want),
4341 say M here and read Documentation/modules.txt. The module will be
4344 Serial port 6PACK driver for AX.25
4346 6pack is a transmission protocol for the data exchange between your
4347 PC and your TNC (the Terminal Node Controller acts as a kind of
4348 modem connecting your computer's serial port to your radio's
4349 microphone input and speaker output). This protocol can be used as
4350 an alternative to KISS for networking over AX.25 amateur radio
4351 connections, but it has some extended functionality.
4353 Note that this driver is still experimental and might cause
4354 problems. For details about the features and the usage of the
4355 driver, read Documentation/networking/6pack.txt.
4357 If you want to compile this driver as a module ( = code which can be
4358 inserted in and removed from the running kernel whenever you want),
4359 say M here and read Documentation/modules.txt. The module will be
4364 AX.25 is the protocol used for computer communication over amateur
4365 radio. If you say Y here, you will be able to send and receive AX.25
4366 traffic over Ethernet (also called "BPQ AX.25"), which could be
4367 useful if some other computer on your local network has a direct
4368 amateur radio connection.
4370 High-speed (DMA) SCC driver for AX.25
4372 This is a driver for high-speed SCC boards, i.e. those supporting
4373 DMA on one port. You usually use those boards to connect your
4374 computer to an amateur radio modem (such as the WA4DSY 56kbps
4375 modem), in order to send and receive AX.25 packet radio network
4378 Currently, this driver supports Ottawa PI/PI2, Paccomm/Gracilis
4379 PackeTwin, and S5SCC/DMA boards. They are detected automatically.
4380 If you have one of these cards, say Y here and read the AX25-HOWTO,
4381 available from http://www.linuxdoc.org/docs.html#howto .
4383 This driver can operate multiple boards simultaneously. If you
4384 compile it as a module (by saying M instead of Y), it will be called
4385 dmascc.o. If you don't pass any parameter to the driver, all
4386 possible I/O addresses are probed. This could irritate other devices
4387 that are currently not in use. You may specify the list of addresses
4388 to be probed by "dmascc=addr1,addr2,..." (when compiled into the
4389 kernel image) or "io=addr1,addr2,..." (when loaded as a module). The
4390 network interfaces will be called dmascc0 and dmascc1 for the board
4391 detected first, dmascc2 and dmascc3 for the second one, and so on.
4393 Before you configure each interface with ifconfig, you MUST set
4394 certain parameters, such as channel access timing, clock mode, and
4395 DMA channel. This is accomplished with a small utility program,
4396 dmascc_cfg, available at
4397 http://www.nt.tuwien.ac.at/~kkudielk/Linux/ . Please be sure to get
4398 at least version 1.27 of dmascc_cfg, as older versions will not
4399 work with the current driver.
4401 Z8530 SCC driver for AX.25
4403 These cards are used to connect your Linux box to an amateur radio
4404 in order to communicate with other computers. If you want to use
4405 this, read Documentation/networking/z8530drv.txt and the AX25-HOWTO,
4406 available from http://www.linuxdoc.org/docs.html#howto . Also
4407 make sure to say Y to "Amateur Radio AX.25 Level 2" support.
4409 If you want to compile this 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 additional delay for PA0HZP OptoSCC compatible boards
4416 Say Y here if you experience problems with the SCC driver not
4417 working properly; please read Documentation/networking/z8530drv.txt
4418 for details. If unsure, say N.
4420 #support for TRX that feedback the tx signal to rx
4423 ### Don't know what's going on here.
4427 YAM driver for AX.25
4429 The YAM is a modem for packet radio which connects to the serial
4430 port and includes some of the functions of a Terminal Node
4431 Controller. If you have one of those, say Y here.
4433 If you want to compile this as a module ( = code which can be
4434 inserted in and removed from the running kernel whenever you want),
4435 say M here and read Documentation/modules.txt.
4437 BAYCOM picpar and par96 driver for AX.25
4439 This is a driver for Baycom style simple amateur radio modems that
4440 connect to a parallel interface. The driver supports the picpar and
4441 par96 designs. To configure the driver, use the sethdlc utility
4442 available in the standard ax25 utilities package. For information on
4443 the modems, see http://www.baycom.de and the file
4444 Documentation/networking/baycom.txt.
4446 If you want to compile this driver as a module ( = code which can be
4447 inserted in and removed from the running kernel whenever you want),
4448 say M here and read Documentation/modules.txt. This is recommended.
4449 The module will be called baycom_par.o.
4451 BAYCOM EPP driver for AX.25
4453 This is a driver for Baycom style simple amateur radio modems that
4454 connect to a parallel interface. The driver supports the EPP
4455 designs. To configure the driver, use the sethdlc utility available
4456 in the standard ax25 utilities package. For information on the
4457 modems, see http://www.baycom.de and the file
4458 Documentation/networking/baycom.txt.
4460 If you want to compile this driver as a module ( = code which can be
4461 inserted in and removed from the running kernel whenever you want),
4462 say M here and read Documentation/modules.txt. This is recommended.
4463 The module will be called baycom_par.o.
4465 BAYCOM ser12 full duplex driver for AX.25
4466 CONFIG_BAYCOM_SER_FDX
4467 This is one of two drivers for Baycom style simple amateur radio
4468 modems that connect to a serial interface. The driver supports the
4469 ser12 design in full duplex mode. In addition, it allows the
4470 baudrate to be set between 300 and 4800 baud (however not all modems
4471 support all baudrates). This is the preferred driver. The next
4472 driver, "BAYCOM ser12 half duplex driver for AX.25" is the old
4473 driver and still provided in case this driver does not work with
4474 your serial interface chip. To configure the driver, use the sethdlc
4475 utility available in the standard ax25 utilities package. For
4476 information on the modems, see http://www.baycom.de and
4477 Documentation/networking/baycom.txt.
4479 If you want to compile this driver as a module ( = code which can be
4480 inserted in and removed from the running kernel whenever you want),
4481 say M here and read Documentation/modules.txt. This is recommended.
4482 The module will be called baycom_ser_fdx.o.
4484 BAYCOM ser12 half duplex driver for AX.25
4485 CONFIG_BAYCOM_SER_HDX
4486 This is one of two drivers for Baycom style simple amateur radio
4487 modems that connect to a serial interface. The driver supports the
4488 ser12 design in full duplex mode. This is the old driver. It is
4489 still provided in case your serial interface chip does not work with
4490 the full duplex driver. This driver is depreciated. To configure the
4491 driver, use the sethdlc utility available in the standard ax25
4492 utilities package. For information on the modems, see
4493 http://www.baycom.de and Documentation/networking/baycom.txt.
4495 If you want to compile this driver as a module ( = code which can be
4496 inserted in and removed from the running kernel whenever you want),
4497 say M here and read Documentation/modules.txt. This is recommended.
4498 The module will be called baycom_ser_hdx.o.
4500 Sound card modem driver for AX.25
4502 This experimental driver allows a standard Sound Blaster or
4503 WindowsSoundSystem compatible sound card to be used as a packet
4504 radio modem (NOT as a telephone modem!), to send digital traffic
4507 To configure the driver, use the sethdlc, smdiag and smmixer
4508 utilities available in the standard ax25 utilities package. For
4509 information on how to key the transmitter, see
4510 http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html and
4511 Documentation/networking/soundmodem.txt.
4513 If you want to compile this driver as a module ( = code which can be
4514 inserted in and removed from the running kernel whenever you want),
4515 say M here and read Documentation/modules.txt. This is recommended.
4516 The module will be called soundmodem.o.
4518 Sound card modem support for Sound Blaster and compatible cards
4519 CONFIG_SOUNDMODEM_SBC
4520 This option enables the soundmodem driver to use Sound Blaster and
4521 compatible cards. If you have a dual mode card (i.e. a WSS cards
4522 with a Sound Blaster emulation) you should say N here and Y to
4523 "Sound card modem support for WSS and Crystal cards", below, because
4524 this usually results in better performance. This option also
4525 supports SB16/32/64 in full duplex mode.
4527 Sound card modem support for WSS and Crystal cards
4528 CONFIG_SOUNDMODEM_WSS
4529 This option enables the soundmodem driver to use WindowsSoundSystem
4530 compatible cards. These cards feature a codec chip from either
4531 Analog Devices (such as AD1848, AD1845, AD1812) or Crystal
4532 Semiconductors (such as CS4248, CS423x). This option also supports
4533 the WSS full duplex operation which currently works with Crystal
4534 CS423x chips. If you don't need full duplex operation, do not enable
4535 it to save performance.
4537 Sound card modem support for 1200 baud AFSK modulation
4538 CONFIG_SOUNDMODEM_AFSK1200
4539 This option enables the soundmodem driver 1200 baud AFSK modem,
4540 compatible to popular modems using TCM3105 or AM7911. The
4541 demodulator requires about 12% of the CPU power of a Pentium 75 CPU
4544 Sound card modem support for 2400 baud AFSK modulation (7.3728MHz crystal)
4545 CONFIG_SOUNDMODEM_AFSK2400_7
4546 This option enables the soundmodem driver 2400 baud AFSK modem,
4547 compatible to TCM3105 modems (over-)clocked with a 7.3728MHz
4548 crystal. Note that the availability of this driver does _not_ imply
4549 that I recommend building such links. It is only here since users
4550 especially in eastern Europe have asked me to do so. In fact this
4551 modulation scheme has many disadvantages, mainly its incompatibility
4552 with many transceiver designs and the fact that the TCM3105 (if
4553 used) is operated widely outside its specifications.
4555 Sound card modem support for 2400 baud AFSK modulation (8MHz crystal)
4556 CONFIG_SOUNDMODEM_AFSK2400_8
4557 This option enables the soundmodem driver 2400 baud AFSK modem,
4558 compatible to TCM3105 modems (over-)clocked with an 8MHz crystal.
4559 Note that the availability of this driver does _not_ imply that I
4560 recommend building such links. It is only here since users
4561 especially in eastern Europe have asked me to do so. In fact this
4562 modulation scheme has many disadvantages, mainly its incompatibility
4563 with many transceiver designs and the fact that the TCM3105 (if
4564 used) is operated widely outside its specifications.
4566 Sound card modem support for 2666 baud AFSK modulation
4567 CONFIG_SOUNDMODEM_AFSK2666
4568 This option enables the soundmodem driver 2666 baud AFSK modem.
4569 This modem is experimental, and not compatible to anything
4572 Sound card modem support for 4800 baud 8PSK modulation
4573 CONFIG_SOUNDMODEM_PSK4800
4574 This option enables the soundmodem driver 4800 baud 8PSK modem.
4575 This modem is experimental, and not compatible to anything
4578 Sound card modem support for 4800 baud HAPN-1 modulation
4579 CONFIG_SOUNDMODEM_HAPN4800
4580 This option enables the soundmodem driver 4800 baud HAPN-1
4581 compatible modem. This modulation seems to be widely used 'down
4582 under' and in the Netherlands. Here, nobody uses it, so I could not
4583 test if it works. It is compatible to itself, however :-)
4585 Sound card modem support for 9600 baud FSK G3RUH modulation
4586 CONFIG_SOUNDMODEM_FSK9600
4587 This option enables the soundmodem driver 9600 baud FSK modem,
4588 compatible to the G3RUH standard. The demodulator requires about 4%
4589 of the CPU power of a Pentium 75 CPU per channel. You can say Y to
4590 both 1200 baud AFSK and 9600 baud FSK if you want (but obviously you
4591 can only use one protocol at a time, depending on what the other end
4594 CCITT X.25 Packet Layer (EXPERIMENTAL)
4596 X.25 is a set of standardized network protocols, similar in scope to
4597 frame relay; the one physical line from your box to the X.25 network
4598 entry point can carry several logical point-to-point connections
4599 (called "virtual circuits") to other computers connected to the X.25
4600 network. Governments, banks, and other organizations tend to use it
4601 to connect to each other or to form Wide Area Networks (WANs). Many
4602 countries have public X.25 networks. X.25 consists of two
4603 protocols: the higher level Packet Layer Protocol (PLP) (say Y here
4604 if you want that) and the lower level data link layer protocol LAPB
4605 (say Y to "LAPB Data Link Driver" below if you want that).
4607 You can read more about X.25 at http://www.sangoma.com/x25.htm and
4608 http://www.cisco.com/univercd/data/doc/software/11_0/rpcg/cx25.htm .
4609 Information about X.25 for Linux is contained in the files
4610 Documentation/networking/x25.txt and
4611 Documentation/networking/x25-iface.txt.
4613 One connects to an X.25 network either with a dedicated network card
4614 using the X.21 protocol (not yet supported by Linux) or one can do
4615 X.25 over a standard telephone line using an ordinary modem (say Y
4616 to "X.25 async driver" below) or over Ethernet using an ordinary
4617 Ethernet card and either the 802.2 LLC protocol (say Y to "802.2
4618 LLC" below) or LAPB over Ethernet (say Y to "LAPB Data Link Driver"
4619 and "LAPB over Ethernet driver" below).
4621 If you want to compile this driver as a module ( = code which can be
4622 inserted in and removed from the running kernel whenever you want),
4623 say M here and read Documentation/modules.txt. The module will be
4624 called x25.o. If unsure, say N.
4626 LAPB Data Link Driver (EXPERIMENTAL)
4628 Link Access Procedure, Balanced (LAPB) is the data link layer (i.e.
4629 the lower) part of the X.25 protocol. It offers a reliable
4630 connection service to exchange data frames with one other host, and
4631 it is used to transport higher level protocols (mostly X.25 Packet
4632 Layer, the higher part of X.25, but others are possible as well).
4633 Usually, LAPB is used with specialized X.21 network cards, but Linux
4634 currently supports LAPB only over Ethernet connections. If you want
4635 to use LAPB connections over Ethernet, say Y here and to "LAPB over
4636 Ethernet driver" below. Read
4637 Documentation/networking/lapb-module.txt for technical details.
4639 If you want to compile this driver as a module though ( = code which
4640 can be inserted in and removed from the running kernel whenever you
4641 want), say M here and read Documentation/modules.txt. The module
4642 will be called lapb.o. If unsure, say N.
4644 802.2 LLC (EXPERIMENTAL)
4646 This is a Logical Link Layer protocol used for X.25 connections over
4647 Ethernet, using ordinary Ethernet cards.
4650 Frame Diverter (EXPERIMENTAL)
4652 The Frame Diverter allows you to divert packets from the
4653 network, that are not aimed at the interface receiving it (in
4654 promisc. mode). Typically, a Linux box setup as an ethernet bridge
4655 with the Frames Diverter on, can do some *really* transparent www
4656 caching using a Squid proxy for example.
4658 This is very usefull when you don't want to change your router's
4659 config (or if you simply don't have access to it).
4661 The other possible usages of diverting Ethernet Frames are numberous:
4662 - reroute smtp traffic to another interface
4663 - traffic-shape certain network streams
4664 - transparently proxy smtp connections
4667 For more informations, please refer to:
4668 http://www.freshmeat.net/projects/etherdivert
4669 http://perso.wanadoo.fr/magpie/EtherDivert.html
4673 802.1d Ethernet Bridging
4675 If you say Y here, then your Linux box will be able to act as an
4676 Ethernet bridge, which means that the different Ethernet segments it
4677 is connected to will appear as one Ethernet to the participants.
4678 Several such bridges can work together to create even larger
4679 networks of Ethernets using the IEEE 802.1 spanning tree algorithm.
4680 As this is a standard, Linux bridges will cooperate properly with
4681 other third party bridge products.
4683 In order to use the ethernet bridge, you'll need the bridge
4684 configuration tools; see Documentation/networking/bridge.txt for
4685 location. Please read the Bridge mini-HOWTO for more information.
4687 Note that if your box acts as a bridge, it probably contains several
4688 Ethernet devices, but the kernel is not able to recognize more than
4689 one at boot time without help; for details read the Ethernet-HOWTO,
4690 available from in http://www.linuxdoc.org/docs.html#howto .
4692 If you want to compile this code as a module ( = code which can be
4693 inserted in and removed from the running kernel whenever you want),
4694 say M here and read Documentation/modules.txt. The module will be
4701 The Packet protocol is used by applications which communicate
4702 directly with network devices without an intermediate network
4703 protocol implemented in the kernel, e.g. tcpdump. If you want them
4706 This driver is also available as a module called af_packet.o ( =
4707 code which can be inserted in and removed from the running kernel
4708 whenever you want). If you want to compile it as a module, say M
4709 here and read Documentation/modules.txt; if you use modprobe or
4710 kmod, you may also want to add "alias net-pf-17 af_packet" to
4715 Packet socket: mmapped IO
4717 If you say Y here, the Packet protocol driver will use an IO
4718 mechanism that results in faster communication.
4722 Kernel/User network link driver
4724 This driver allows for two-way communication between the kernel and
4725 user processes. It does so by creating a new socket family, PF_NETLINK.
4726 Over this socket, the kernel can send and receive datagrams carrying
4727 information. It is documented on many systems in netlink(7), a HOWTO is
4728 provided as well, for example on
4729 http://snafu.freedom.org/linux2.2/docs/netlink-HOWTO.html
4731 So far, the kernel uses this feature to publish some network related
4732 information if you say Y to "Routing messages", below. You also need
4733 to say Y here if you want to use arpd, a daemon that helps keep the
4734 internal ARP cache (a mapping between IP addresses and hardware
4735 addresses on the local network) small. The ethertap device, which
4736 lets user space programs read and write raw Ethernet frames, also
4737 needs the network link driver.
4743 If you say Y here, userspace programs can receive some network
4744 related routing information over the netlink. 'rtmon', supplied
4745 with the iproute2 package (ftp://ftp.inr.ac.ru), can read and
4746 interpret this data. Information sent to the kernel over this link
4749 Netlink device emulation
4751 This option will be removed soon. Any programs that want to use
4752 character special nodes like /dev/tap0 or /dev/route (all with major
4753 number 36) need this option, and need to be rewritten soon to use
4754 the real netlink socket.
4755 This is a backward compatibility option, choose Y for now.
4757 Asynchronous Transfer Mode (ATM)
4759 ATM is a high-speed networking technology for Local Area Networks
4760 and Wide Area Networks. It uses a fixed packet size and is
4761 connection oriented, allowing for the negotiation of minimum
4762 bandwidth requirements.
4764 In order to participate in an ATM network, your Linux box needs an
4765 ATM networking card. If you have that, say Y here and to the driver
4766 of your ATM card below.
4768 Note that you need a set of user-space programs to actually make use
4769 of ATM. See the file Documentation/networking/atm.txt for further
4772 Classical IP over ATM
4774 Classical IP over ATM for PVCs and SVCs, supporting InARP and
4775 ATMARP. If you want to communication with other IP hosts on your ATM
4776 network, you will typically either say Y here or to "LAN Emulation
4779 Do NOT send ICMP if no neighbour
4780 CONFIG_ATM_CLIP_NO_ICMP
4781 Normally, an "ICMP host unreachable" message is sent if a neighbour
4782 cannot be reached because there is no VC to it in the kernel's
4783 ATMARP table. This may cause problems when ATMARP table entries are
4784 briefly removed during revalidation. If you say Y here, packets to
4785 such neighbours are silently discarded instead.
4787 LAN Emulation (LANE) support
4789 LAN Emulation emulates services of existing LANs across an ATM
4790 network. Besides operating as a normal ATM end station client, Linux
4791 LANE client can also act as an proxy client bridging packets between
4792 ELAN and Ethernet segments. You need LANE if you want to try MPOA.
4794 Multi-Protocol Over ATM (MPOA) support
4796 Multi-Protocol Over ATM allows ATM edge devices such as routers,
4797 bridges and ATM attached hosts establish direct ATM VCs across
4798 subnetwork boundaries. These shortcut connections bypass routers
4799 enhancing overall network performance.
4803 ATM over TCP driver. Useful mainly for development and for
4804 experiments. If unsure, say N.
4806 Efficient Networks ENI155P
4808 Driver for the Efficient Networks ENI155p series and SMC ATM
4809 Power155 155 Mbps ATM adapters. Both, the versions with 512KB and
4810 2MB on-board RAM (Efficient calls them "C" and "S", respectively),
4811 and the FPGA and the ASIC Tonga versions of the board are supported.
4812 The driver works with MMF (-MF or ...F) and UTP-5 (-U5 or ...D)
4815 This driver is also available as a module. If you want to compile
4816 it as a module, say M here and read Documentation/modules.txt. The
4817 module will be called eni.o.
4819 Enable extended debugging
4820 CONFIG_ATM_ENI_DEBUG
4821 Extended debugging records various events and displays that list
4822 when an inconsistency is detected. This mechanism is faster than
4823 generally using printks, but still has some impact on performance.
4824 Note that extended debugging may create certain race conditions
4825 itself. Enable this ONLY if you suspect problems with the driver.
4827 Fine-tune burst settings
4828 CONFIG_ATM_ENI_TUNE_BURST
4829 In order to obtain good throughput, the ENI NIC can transfer
4830 multiple words of data per PCI bus access cycle. Such a multi-word
4831 transfer is called a burst.
4833 The default settings for the burst sizes are suitable for most PCI
4834 chipsets. However, in some cases, large bursts may overrun buffers
4835 in the PCI chipset and cause data corruption. In such cases, large
4836 bursts must be disabled and only (slower) small bursts can be used.
4837 The burst sizes can be set independently in the send (TX) and
4838 receive (RX) direction.
4840 Note that enabling many different burst sizes in the same direction
4841 may increase the cost of setting up a transfer such that the
4842 resulting throughput is lower than when using only the largest
4843 available burst size.
4845 Also, sometimes larger bursts lead to lower throughput, e.g. on an
4846 Intel 440FX board, a drop from 135 Mbps to 103 Mbps was observed
4847 when going from 8W to 16W bursts.
4849 Enable 16W TX bursts (discouraged)
4850 CONFIG_ATM_ENI_BURST_TX_16W
4851 Burst sixteen words at once in the send direction. This may work
4852 with recent PCI chipsets, but is known to fail with older chipsets.
4854 Enable 8W TX bursts (recommended)
4855 CONFIG_ATM_ENI_BURST_TX_8W
4856 Burst eight words at once in the send direction. This is the default
4859 Enable 4W TX bursts (optional)
4860 CONFIG_ATM_ENI_BURST_TX_4W
4861 Burst four words at once in the send direction. You may want to try
4862 this if you have disabled 8W bursts. Enabling 4W if 8W is also set
4863 may or may not improve throughput.
4865 Enable 2W TX bursts (optional)
4866 CONFIG_ATM_ENI_BURST_TX_2W
4867 Burst two words at once in the send direction. You may want to try
4868 this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or 8W
4869 are also set may or may not improve throughput.
4871 Enable 16W RX bursts (discouraged)
4872 CONFIG_ATM_ENI_BURST_RX_16W
4873 Burst sixteen words at once in the receive direction. This may work
4874 with recent PCI chipsets, but is known to fail with older chipsets.
4876 Enable 8W RX bursts (discouraged)
4877 CONFIG_ATM_ENI_BURST_RX_8W
4878 Burst eight words at once in the receive direction. This may work
4879 with recent PCI chipsets, but is known to fail with older chipsets,
4880 such as the Intel Neptune series.
4882 Enable 4W RX bursts (recommended)
4883 CONFIG_ATM_ENI_BURST_RX_4W
4884 Burst four words at once in the receive direction. This is the
4885 default setting. Enabling 4W if 8W is also set may or may not
4888 Enable 2W RX bursts (optional)
4889 CONFIG_ATM_ENI_BURST_RX_2W
4890 Burst two words at once in the receive direction. You may want to
4891 try this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or
4892 8W are also set may or may not improve throughput.
4894 ZeitNet ZN1221/ZN1225
4896 Driver for the ZeitNet ZN1221 (MMF) and ZN1225 (UTP-5) 155 Mbps ATM
4899 This driver is also available as a module. If you want to compile
4900 it as a module, say M here and read Documentation/modules.txt. The
4901 module will be called zatm.o.
4903 Enable extended debugging
4904 CONFIG_ATM_ZATM_DEBUG
4905 Extended debugging records various events and displays that list
4906 when an inconsistency is detected. This mechanism is faster than
4907 generally using printks, but still has some impact on performance.
4908 Note that extended debugging may create certain race conditions
4909 itself. Enable this ONLY if you suspect problems with the driver.
4911 Enable usec resolution timestamps
4912 CONFIG_ATM_ZATM_EXACT_TS
4913 The uPD98401 SAR chip supports a high-resolution timer (approx. 30
4914 MHz) that is used for very accurate reception timestamps. Because
4915 that timer overflows after 140 seconds, and also to avoid timer
4916 drift, time measurements need to be periodically synchronized with
4917 the normal system time. Enabling this feature will add some general
4918 overhead for timer synchronization and also per-packet overhead for
4921 IDT 77201/11 (NICStAR) (ForeRunnerLE)
4923 The NICStAR chipset family is used in a large number of ATM NICs for
4924 25 and for 155 Mbps, including IDT cards and the Fore ForeRunnerLE
4925 series. Say Y if you have one of those.
4927 This driver is also available as a module. If you want to compile
4928 it as a module, say M here and read Documentation/modules.txt. The
4929 module will be called nicstar.o.
4931 ForeRunner LE155 PHYsical layer
4932 CONFIG_ATM_NICSTAR_USE_SUNI
4933 Support for the S-UNI and compatible PHYsical layer chips. These are
4934 found in most 155Mbps NICStAR based ATM cards, namely in the
4935 ForeRunner LE155 cards. This driver provides detection of cable
4936 removal and reinsertion and provides some statistics. This driver
4937 doesn't have removal capability when compiled as a module, so if you
4938 need that capability don't include S-UNI support (it's not needed to
4939 make the card work).
4941 ForeRunner LE25 PHYsical layer
4942 CONFIG_ATM_NICSTAR_USE_IDT77105
4943 Support for the PHYsical layer chip in ForeRunner LE25 cards. In
4944 addition to cable removal/reinsertion detection, this driver allows
4945 you to control the loopback mode of the chip via a dedicated IOCTL.
4946 This driver is required for proper handling of temporary carrier
4947 loss, so if you have a 25Mbps NICStAR based ATM card you must say Y.
4949 Madge Ambassador (Collage PCI 155 Server)
4950 CONFIG_ATM_AMBASSADOR
4951 This is a driver for ATMizer based ATM card produced by Madge
4952 Networks Ltd. Say Y (or M to compile as a module named ambassador.o)
4953 here if you have one of these cards.
4955 Enable debugging messages
4956 CONFIG_ATM_AMBASSADOR_DEBUG
4957 Somewhat useful debugging messages are available. The choice of
4958 messages is controlled by a bitmap. This may be specified as a
4959 module argument (kernel command line argument as well?), changed
4960 dynamically using an ioctl (not yet) or changed by sending the
4961 string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
4962 drivers/atm/ambassador.h for the meanings of the bits in the mask.
4964 When active, these messages can have a significant impact on the
4965 speed of the driver, and the size of your syslog files! When
4966 inactive, they will have only a modest impact on performance.
4968 Madge Horizon [Ultra] (Collage PCI 25 and Collage PCI 155 Client)
4970 This is a driver for the Horizon chipset ATM adapter cards once
4971 produced by Madge Networks Ltd. Say Y (or M to compile as a module
4972 named horizon.o) here if you have one of these cards.
4974 Enable debugging messages
4975 CONFIG_ATM_HORIZON_DEBUG
4976 Somewhat useful debugging messages are available. The choice of
4977 messages is controlled by a bitmap. This may be specified as a
4978 module argument (kernel command line argument as well?), changed
4979 dynamically using an ioctl (not yet) or changed by sending the
4980 string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
4981 drivers/atm/horizon.h for the meanings of the bits in the mask.
4983 When active, these messages can have a significant impact on the
4984 speed of the driver, and the size of your syslog files! When
4985 inactive, they will have only a modest impact on performance.
4987 Interphase ATM PCI x575/x525/x531
4989 This is a driver for the Interphase (i)ChipSAR adapter cards
4990 which include a variety of variants in term of the size of the
4991 control memory (128K-1KVC, 512K-4KVC), the size of the packet
4992 memory (128K, 512K, 1M), and the PHY type (Single/Multi mode OC3,
4993 UTP155, UTP25, DS3 and E3). Go to:
4994 www.iphase.com/products/ClassSheet.cfm?ClassID=ATM
4995 for more info about the cards. Say Y (or M to compile as a module
4996 named iphase.o) here if you have one of these cards.
4998 See the file Documentation/networking/iphase.txt for further
5001 Enable debugging messages
5003 Somewhat useful debugging messages are available. The choice of
5004 messages is controlled by a bitmap. This may be specified as a
5005 module argument (kernel command line argument as well?), changed
5006 dynamically using an ioctl (Get the debug utility, iadbg, from
5007 ftp.iphase.com/pub/atm/pci). See the file drivers/atm/iphase.h
5008 for the meanings of the bits in the mask.
5010 When active, these messages can have a significant impact on the
5011 speed of the driver, and the size of your syslog files! When
5012 inactive, they will have only a modest impact on performance.
5014 Linux telephony support
5016 Say Y here if you have a telephony card, which for example allows
5017 you to use a regular phone for voice-over-IP applications.
5019 Note: this has nothing to do with modems. You do not need to say Y
5020 here in order to be able to use a modem under Linux.
5022 This support is also available as a module. If you want to compile
5023 it as a module, say M here and read Documentation/modules.txt. The
5024 module will be called phonedev.o.
5026 Compaq Smart Array support
5027 CONFIG_BLK_CPQ_CISS_DA
5028 This is the driver for Compaq Smart Array controllers.
5029 Everyone using these boards should say Y here.
5030 See Documentation/cciss.txt for the current list of
5031 boards supported by this driver, and for further information
5032 on the use of this driver.
5034 QuickNet Internet LineJack/PhoneJack support
5036 Say M if you have a telephony card manufactured by Quicknet
5037 Technologies, Inc. These include the Internet PhoneJACK and
5038 Internet LineJACK Telephony Cards. You will get a module called
5041 For the ISA versions of these products, you can configure the
5042 cards using the isapnp tools (pnpdump/isapnp) or you can use the
5043 isapnp support. Please read Documentation/telephony/ixj.txt.
5045 For more information on these cards, see Quicknet's web site at:
5046 http://www.quicknet.net/ .
5048 If you do not have any Quicknet telephony cards, you can safely
5051 FORE Systems 200E-series
5052 CONFIG_ATM_FORE200E_MAYBE
5053 This is a driver for the FORE Systems 200E-series ATM adapter
5054 cards. It simultaneously supports PCA-200E and SBA-200E models
5055 on PCI and SBUS hosts. Say Y (or M to compile as a module
5056 named fore_200e.o) here if you have one of these ATM adapters.
5058 Note that the driver will actually be compiled only if you
5059 additionally enable the support for PCA-200E and/or SBA-200E
5062 See the file Documentation/networking/fore200e.txt for further
5065 Enable PCA-200E card support on PCI-based hosts
5066 CONFIG_ATM_FORE200E_PCA
5067 Say Y here if you want your PCA-200E cards to be probed.
5069 Use default PCA-200E firmware
5070 CONFIG_ATM_FORE200E_PCA_DEFAULT_FW
5071 Use the default PCA-200E firmware data shipped with the driver.
5073 Normal users do not have to deal with the firmware stuff, so
5074 they should say Y here.
5076 Pathname of user-supplied binary firmware
5077 CONFIG_ATM_FORE200E_PCA_FW
5078 This defines the pathname of an alternative PCA-200E binary
5079 firmware image supplied by the user. This pathname may be
5080 absolute or relative to the drivers/atm directory.
5082 The driver comes with an adequate firmware image, so normal users do
5083 not have to supply an alternative one. They just say Y to "Use
5084 default PCA-200E firmware" instead.
5086 Enable SBA-200E card support on SBUS-based hosts
5087 CONFIG_ATM_FORE200E_SBA
5088 Say Y here if you want your SBA-200E cards to be probed.
5090 Use default SBA-200E firmware
5091 CONFIG_ATM_FORE200E_SBA_DEFAULT_FW
5092 Use the default SBA-200E firmware data shipped with the driver.
5094 Normal users do not have to deal with the firmware stuff, so
5095 they should say Y here.
5097 Pathname of user-supplied binary firmware
5098 CONFIG_ATM_FORE200E_SBA_FW
5099 This defines the pathname of an alternative SBA-200E binary
5100 firmware image supplied by the user. This pathname may be
5101 absolute or relative to the drivers/atm directory.
5103 The driver comes with an adequate firmware image, so normal users do
5104 not have to supply an alternative one. They just say Y to "Use
5105 default SBA-200E firmware", above.
5107 Maximum number of tx retries
5108 CONFIG_ATM_FORE200E_TX_RETRY
5109 Specifies the number of times the driver attempts to transmit
5110 a message before giving up, if the transmit queue of the ATM card
5111 is transiently saturated.
5113 Saturation of the transmit queue may occur only under extreme
5114 conditions, e.g. when a fast host continuously submits very small
5115 frames (<64 bytes) or raw AAL0 cells (48 bytes) to the ATM adapter.
5117 Note that under common conditions, it is unlikely that you encounter
5118 a saturation of the transmit queue, so the retry mechanism never
5121 Debugging level (0-3)
5122 CONFIG_ATM_FORE200E_DEBUG
5123 Specifies the level of debugging messages issued by the driver.
5124 The verbosity of the driver increases with the value of this
5127 When active, these messages can have a significant impact on
5128 the performances of the driver, and the size of your syslog files!
5129 Keep the debugging level to 0 during normal operations.
5133 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CDROM or
5134 any other SCSI device under Linux, say Y and make sure that you know
5135 the name of your SCSI host adapter (the card inside your computer
5136 that "speaks" the SCSI protocol, also called SCSI controller),
5137 because you will be asked for it.
5139 You also need to say Y here if you want support for the parallel
5140 port version of the 100 MB IOMEGA ZIP drive.
5142 Please read the SCSI-HOWTO, available from
5143 http://www.linuxdoc.org/docs.html#howto . The
5144 SCSI-Programming-HOWTO contains information about how to add or
5145 remove an SCSI device from a running Linux machine without
5148 This driver is also available as a module ( = code which can be
5149 inserted in and removed from the running kernel whenever you want).
5150 The module will be called scsi_mod.o. If you want to compile it as a
5151 module, say M here and read Documentation/modules.txt and
5152 Documentation/scsi.txt. However, do not compile this as a module if
5153 your root file system (the one containing the directory /) is
5154 located on a SCSI device.
5158 If you want to use a SCSI hard disk or the SCSI or parallel port
5159 version of the IOMEGA ZIP drive under Linux, say Y and read the
5160 SCSI-HOWTO, the Disk-HOWTO and the Multi-Disk-HOWTO, available from
5161 http://www.linuxdoc.org/docs.html#howto . This is NOT for SCSI
5164 This driver is also available as a module ( = code which can be
5165 inserted in and removed from the running kernel whenever you want).
5166 The module will be called sd_mod.o. If you want to compile it as a
5167 module, say M here and read Documentation/modules.txt and
5168 Documentation/scsi.txt. Do not compile this driver as a module if
5169 your root file system (the one containing the directory /) is
5170 located on a SCSI disk. In this case, do not compile the driver for
5171 your SCSI host adapter (below) as a module either.
5174 CONFIG_SD_EXTRA_DEVS
5175 This controls the amount of additional space allocated in tables for
5176 drivers that are loaded as modules after the kernel is booted. In
5177 the event that the SCSI core itself was loaded as a module, this
5178 value is the number of additional disks that can be loaded after the
5179 first host driver is loaded.
5181 Admittedly this isn't pretty, but there are tons of race conditions
5182 involved with resizing the internal arrays on the fly. Someday this
5183 flag will go away, and everything will work automatically.
5185 If you don't understand what's going on, go with the default.
5189 If you want to use a SCSI tape drive under Linux, say Y and read the
5190 SCSI-HOWTO, available from
5191 http://www.linuxdoc.org/docs.html#howto , and
5192 drivers/scsi/README.st in the kernel source. This is NOT for SCSI
5195 This driver is also available as a module ( = code which can be
5196 inserted in and removed from the running kernel whenever you want).
5197 The module will be called st.o. If you want to compile it as a
5198 module, say M here and read Documentation/modules.txt and
5199 Documentation/scsi.txt .
5203 If you want to use a SCSI CDROM under Linux, say Y and read the
5204 SCSI-HOWTO and the CDROM-HOWTO at
5205 http://www.linuxdoc.org/docs.html#howto . Also make sure to say Y
5206 or M to "ISO 9660 CDROM file system support" later.
5208 This driver is also available as a module ( = code which can be
5209 inserted in and removed from the running kernel whenever you want).
5210 The module will be called sr_mod.o. If you want to compile it as a
5211 module, say M here and read Documentation/modules.txt and
5212 Documentation/scsi.txt .
5215 CONFIG_SR_EXTRA_DEVS
5216 This controls the amount of additional space allocated in tables for
5217 drivers that are loaded as modules after the kernel is booted. In
5218 the event that the SCSI core itself was loaded as a module, this
5219 value is the number of additional CDROMs that can be loaded after
5220 the first host driver is loaded.
5222 Admittedly this isn't pretty, but there are tons of race conditions
5223 involved with resizing the internal arrays on the fly. Someday this
5224 flag will go away, and everything will work automatically.
5226 If you don't understand what's going on, go with the default.
5228 Enable vendor-specific extensions (for SCSI CDROM)
5229 CONFIG_BLK_DEV_SR_VENDOR
5230 This enables the usage of vendor specific SCSI commands. This is
5231 required to support multisession CDs with old NEC/TOSHIBA cdrom
5232 drives (and HP Writers). If you have such a drive and get the first
5233 session only, try saying Y here; everybody else says N.
5235 SCSI generic support
5237 If you want to use SCSI scanners, synthesizers or CD-writers or just
5238 about anything having "SCSI" in its name other than hard disks,
5239 CDROMs or tapes, say Y here. These won't be supported by the kernel
5240 directly, so you need some additional software which knows how to
5241 talk to these devices using the SCSI protocol:
5243 For scanners, look at SANE (http://www.mostang.com/sane). For CD
5244 writer software look at cdrecord
5245 (http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html)
5246 and for burning a "disk at once": cdrdao
5247 (http://www.ping.de/sites/daneb/cdrdao.html). Cdparanoia is a high
5248 quality digital reader of audio CDs (http://www.xiph.org/paranoia).
5249 For other devices, it's possible that you'll have to write the
5250 driver software yourself. Please read the file
5251 Documentation/scsi-generic.txt for more information.
5253 If you want to compile this as a module ( = code which can be
5254 inserted in and removed from the running kernel whenever you want),
5255 say M here and read Documentation/modules.txt and
5256 Documentation/scsi.txt. The module will be called sg.o. If unsure,
5259 Debug new queueing code for SCSI
5260 CONFIG_SCSI_DEBUG_QUEUES
5261 This option turns on a lot of additional consistency checking for
5262 the new queueing code. This will adversely affect performance, but
5263 it is likely that bugs will be caught sooner if this is turned on.
5264 This will typically cause the kernel to panic if an error is
5265 detected, but it would have probably crashed if the panic weren't
5266 there. Comments/questions/problems to linux-scsi mailing list
5267 please. See http://www.andante.org/scsi_queue.html for more
5268 up-to-date information.
5270 Probe all LUNs on each SCSI device
5271 CONFIG_SCSI_MULTI_LUN
5272 If you have a SCSI device that supports more than one LUN (Logical
5273 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
5274 can say Y here to force the SCSI driver to probe for multiple LUNs.
5275 A SCSI device with multiple LUNs acts logically like multiple SCSI
5276 devices. The vast majority of SCSI devices have only one LUN, and
5277 so most people can say N here and should in fact do so, because it
5280 Verbose SCSI error reporting (kernel size +=12K)
5281 CONFIG_SCSI_CONSTANTS
5282 The error messages regarding your SCSI hardware will be easier to
5283 understand if you say Y here; it will enlarge your kernel by about
5284 12 KB. If in doubt, say Y.
5286 SCSI logging facility
5288 This turns on a logging facility that can be used to debug a number
5289 of SCSI related problems.
5291 If you say Y here, no logging output will appear by default, but you
5292 can enable logging by saying Y to "/proc file system support" and
5293 "Sysctl support" below and executing the command
5295 echo "scsi log token [level]" > /proc/scsi/scsi
5297 at boot time after the /proc file system has been mounted.
5299 There are a number of things that can be used for 'token' (you can
5300 find them in the source: drivers/scsi/scsi.c), and this allows you
5301 to select the types of information you want, and the level allows
5302 you to select the level of verbosity.
5304 If you say N here, it may be harder to track down some types of SCSI
5305 problems. If you say Y here your kernel will be somewhat larger, but
5306 there should be no noticeable performance impact as long as you have
5309 AdvanSys SCSI support
5310 CONFIG_SCSI_ADVANSYS
5311 This is a driver for all SCSI host adapters manufactured by
5312 AdvanSys. It is documented in the kernel source in
5313 drivers/scsi/advansys.c.
5315 This driver is also available as a module ( = code which can be
5316 inserted in and removed from the running kernel whenever you want).
5317 If you want to compile it as a module, say M here and read
5318 Documentation/modules.txt. The module will be called advansys.o.
5320 Adaptec AHA152X/2825 support
5322 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
5323 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
5324 must be manually specified in this case.
5326 It is explained in section 3.3 of the SCSI-HOWTO, available from
5327 http://www.linuxdoc.org/docs.html#howto . You might also want to
5328 read the file drivers/scsi/README.aha152x.
5330 This driver is also available as a module ( = code which can be
5331 inserted in and removed from the running kernel whenever you want).
5332 The module will be called aha152x.o. If you want to compile it as a
5333 module, say M here and read Documentation/modules.txt.
5335 Adaptec AHA1542 support
5337 This is support for a SCSI host adapter. It is explained in section
5338 3.4 of the SCSI-HOWTO, available from
5339 http://www.linuxdoc.org/docs.html#howto . Note that Trantor was
5340 purchased by Adaptec, and some former Trantor products are being
5341 sold under the Adaptec name. If it doesn't work out of the box, you
5342 may have to change some settings in drivers/scsi/aha1542.h.
5344 If you want to compile this as a module ( = code which can be
5345 inserted in and removed from the running kernel whenever you want),
5346 say M here and read Documentation/modules.txt. The module will be
5349 Adaptec AHA1740 support
5351 This is support for a SCSI host adapter. It is explained in section
5352 3.5 of the SCSI-HOWTO, available from
5353 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
5354 of the box, you may have to change some settings in
5355 drivers/scsi/aha1740.h.
5357 This driver is also available as a module ( = code which can be
5358 inserted in and removed from the running kernel whenever you want).
5359 The module will be called aha1740.o. If you want to compile it as a
5360 module, say M here and read Documentation/modules.txt.
5362 Adaptec AIC7xxx chipset SCSI controller support
5364 This is support for the various aic7xxx based Adaptec SCSI
5365 controllers. These include the 274x EISA cards; 284x VLB cards;
5366 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
5367 motherboard based SCSI controllers from Adaptec. It does not support
5368 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
5369 support them. It does not support the 2920 cards from Adaptec that
5370 use the Future Domain SCSI controller chip. For those cards, you
5371 need the "Future Domain 16xx SCSI support" driver.
5373 In general, if the controller is based on an Adaptec SCSI controller
5374 chip from the aic777x series or the aic78xx series, this driver
5375 should work. The only exception is the 7810 which is specifically
5376 not supported (that's the RAID controller chip on the AAA-13x
5379 Note that the AHA2920 SCSI host adapter is *not* supported by this
5380 driver; choose "Future Domain 16xx SCSI support" instead if you have
5383 Information on the configuration options for this controller can be
5384 found by checking the help file for each of the available
5385 configuration options. You should read drivers/scsi/README.aic7xxx
5386 at a minimum before contacting the maintainer with any questions.
5387 The SCSI-HOWTO, available from
5388 http://www.linuxdoc.org/docs.html#howto , can also be of great
5391 If you want to compile this driver as a module ( = code which can be
5392 inserted in and removed from the running kernel whenever you want),
5393 say M here and read Documentation/modules.txt. The module will be
5396 Enable or Disable Tagged Command Queueing by default
5397 CONFIG_AIC7XXX_TCQ_ON_BY_DEFAULT
5398 This option causes the aic7xxx driver to attempt to use Tagged
5399 Command Queueing (TCQ) on all devices that claim to support it.
5401 TCQ is a feature of SCSI-2 which improves performance: the host
5402 adapter can send several SCSI commands to a device's queue even if
5403 previous commands haven't finished yet. Because the device is
5404 intelligent, it can optimize its operations (like head positioning)
5405 based on its own request queue. Not all devices implement this
5408 If you say Y here, you can still turn off TCQ on troublesome devices
5409 with the use of the tag_info boot parameter. See the file
5410 drivers/scsi/README.aic7xxx for more information on that and other
5411 aic7xxx setup commands. If this option is turned off, you may still
5412 enable TCQ on known good devices by use of the tag_info boot
5415 If you are unsure about your devices then it is safest to say N
5418 However, TCQ can increase performance on some hard drives by as much
5419 as 50% or more, so it is recommended that if you say N here, you
5420 should at least read the README.aic7xxx file so you will know how to
5421 enable this option manually should your drives prove to be safe in
5424 Conversely, certain drives are known to lock up or cause bus resets
5425 when TCQ is enabled on them. If you have a Western Digital
5426 Enterprise SCSI drive for instance, then don't even bother to enable
5427 TCQ on it as the drive will become unreliable, and it will actually
5430 Default number of TCQ commands per device
5431 CONFIG_AIC7XXX_CMDS_PER_DEVICE
5432 Specify the number of commands you would like to allocate per SCSI
5433 device when Tagged Command Queueing (TCQ) is enabled on that device.
5435 Reasonable figures are in the range of 8 to 24 commands per device,
5436 but depending on hardware could be increased or decreased from that
5437 figure. If the number is too high for any particular device, the
5438 driver will automatically compensate usually after only 10 minutes
5439 of uptime. It will not hinder performance if some of your devices
5440 eventually have their command depth reduced, but is a waste of
5441 memory if all of your devices end up reducing this number down to a
5442 more reasonable figure.
5444 NOTE: Certain very broken drives are known to lock up when given
5445 more commands than they like to deal with. Quantum Fireball drives
5446 are the most common in this category. For the Quantum Fireball
5447 drives it is suggested to use no more than 8 commands per device.
5451 Collect statistics to report in /proc
5452 CONFIG_AIC7XXX_PROC_STATS
5453 This option tells the driver to keep track of how many commands have
5454 been sent to each particular device and report that information to
5455 the user via the /proc/scsi/aic7xxx/n file, where n is the number of
5456 the aic7xxx controller you want the information on. This adds a
5457 small amount of overhead to each and every SCSI command the aic7xxx
5458 driver handles, so if you aren't really interested in this
5459 information, it is best to leave it disabled. This will only work if
5460 you also say Y to "/proc file system support", below.
5464 Delay in seconds after SCSI bus reset
5465 CONFIG_AIC7XXX_RESET_DELAY
5466 This sets how long the driver will wait after resetting the SCSI bus
5467 before attempting to communicate with the devices on the SCSI bus
5468 again. This delay will be used during the reset phase at bootup time
5469 as well as after any reset that might occur during normal operation.
5470 Reasonable numbers range anywhere from 5 to 15 seconds depending on
5471 your devices. DAT tape drives are notorious for needing more time
5472 after a bus reset to be ready for the next command, but most hard
5473 drives and CD-ROM devices are ready in only a few seconds. This
5474 option has a maximum upper limit of 20 seconds to avoid bad
5475 interactions between the aic7xxx driver and the rest of the Linux
5476 kernel. The default value has been reduced to 5 seconds. If this
5477 doesn't work with your hardware, try increasing this value.
5479 IBM ServeRAID Support
5481 This is support for the IBM ServeRAID hardware RAID controllers.
5482 See http://www.developer.ibm.com/welcome/netfinity/serveraid.html
5483 for more information. If this driver does not work correctly
5484 without modification please contact the author by email at
5485 ipslinux@us.ibm.com.
5487 You can build this driver as a module ( = code which can be
5488 inserted in and removed from the running kernel whenever you want),
5489 but only a single instance may be loaded. If you want to compile it
5490 as a module, say M here and read Documentation/modules.txt. The
5491 module will be called ips.o.
5493 BusLogic SCSI support
5494 CONFIG_SCSI_BUSLOGIC
5495 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
5496 Adapters. Consult the SCSI-HOWTO, available from
5497 http://www.linuxdoc.org/docs.html#howto , and the files
5498 README.BusLogic and README.FlashPoint in drivers/scsi for more
5499 information. If this driver does not work correctly without
5500 modification, please contact the author, Leonard N. Zubkoff, by
5501 email to lnz@dandelion.com.
5503 You can also build this driver as a module ( = code which can be
5504 inserted in and removed from the running kernel whenever you want),
5505 but only a single instance may be loaded. If you want to compile it
5506 as a module, say M here and read Documentation/modules.txt. The
5507 module will be called BusLogic.o.
5509 Omit BusLogic SCSI FlashPoint support
5510 CONFIG_SCSI_OMIT_FLASHPOINT
5511 This option allows you to omit the FlashPoint support from the
5512 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
5513 substantial, so users of MultiMaster Host Adapters may wish to omit
5516 DMX3191D SCSI support
5517 CONFIG_SCSI_DMX3191D
5518 This is support for Domex DMX3191D SCSI Host Adapters.
5520 This driver is also available as a module ( = code which can be
5521 inserted in and removed from the running kernel whenever you want).
5522 The module will be called dmx3191d.o. If you want to compile it as a
5523 module, say M here and read Documentation/modules.txt.
5525 DTC3180/3280 SCSI support
5527 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
5528 the SCSI-HOWTO, available from
5529 http://www.linuxdoc.org/docs.html#howto , and the file
5530 drivers/scsi/README.dtc3x80.
5532 This driver is also available as a module ( = code which can be
5533 inserted in and removed from the running kernel whenever you want).
5534 The module will be called dtc.o. If you want to compile it as a
5535 module, say M here and read Documentation/modules.txt.
5537 EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti, Alphatronix) support
5538 CONFIG_SCSI_EATA_DMA
5539 This is support for the EATA-DMA protocol compliant SCSI Host
5540 Adapters like the SmartCache III/IV, SmartRAID controller families
5541 and the DPT PM2011B and PM2012B controllers.
5543 Note that this driver is obsolete; if you have one of the above SCSI
5544 Host Adapters, you should normally say N here and Y to "EATA
5545 ISA/EISA/PCI support", below. Please read the SCSI-HOWTO, available
5546 from http://www.linuxdoc.org/docs.html#howto .
5548 This driver is also available as a module ( = code which can be
5549 inserted in and removed from the running kernel whenever you want).
5550 The module will be called eata_dma.o. If you want to compile it as a
5551 module, say M here and read Documentation/modules.txt.
5553 EATA-PIO (old DPT PM2001, PM2012A) support
5554 CONFIG_SCSI_EATA_PIO
5555 This driver supports all EATA-PIO protocol compliant SCSI Host
5556 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
5557 host adapters could also use this driver but are discouraged from
5558 doing so, since this driver only supports hard disks and lacks
5559 numerous features. You might want to have a look at the SCSI-HOWTO,
5560 available from http://www.linuxdoc.org/docs.html#howto .
5562 If you want to compile this as a module ( = code which can be
5563 inserted in and removed from the running kernel whenever you want),
5564 say M here and read Documentation/modules.txt. The module will be
5567 UltraStor 14F/34F support
5569 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
5570 The source at drivers/scsi/u14-34f.c contains some information about
5571 this hardware. If the driver doesn't work out of the box, you may
5572 have to change some settings in drivers/scsi/u14-34f.c. Read the
5573 SCSI-HOWTO, available from
5574 http://www.linuxdoc.org/docs.html#howto . Note that there is also
5575 another driver for the same hardware: "UltraStor SCSI support",
5576 below. You should say Y to both only if you want 24F support as
5579 This driver is also available as a module ( = code which can be
5580 inserted in and removed from the running kernel whenever you want).
5581 The module will be called u14-34f.o. If you want to compile it as a
5582 module, say M here and read Documentation/modules.txt.
5584 enable elevator sorting
5585 CONFIG_SCSI_U14_34F_LINKED_COMMANDS
5586 This option enables elevator sorting for all probed SCSI disks and
5587 CDROMs. It definitely reduces the average seek distance when doing
5588 random seeks, but this does not necessarily result in a noticeable
5589 performance improvement: your mileage may vary...
5591 The safe answer is N.
5593 maximum number of queued commands
5594 CONFIG_SCSI_U14_34F_MAX_TAGS
5595 This specifies how many SCSI commands can be maximally queued for
5596 each probed SCSI device. You should reduce the default value of 8
5597 only if you have disks with buggy or limited tagged command support.
5598 Minimum is 2 and maximum is 14. This value is also the window size
5599 used by the elevator sorting option above. The effective value used
5600 by the driver for each probed SCSI device is reported at boot time.
5602 Future Domain 16xx SCSI/AHA-2920A support
5603 CONFIG_SCSI_FUTURE_DOMAIN
5604 This is support for Future Domain's 16-bit SCSI host adapters
5605 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
5606 other adapters based on the Future Domain chipsets (Quantum
5607 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
5608 It is explained in section 3.7 of the SCSI-HOWTO, available from
5609 http://www.linuxdoc.org/docs.html#howto .
5611 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
5612 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
5613 controller support"). This Future Domain driver works with the older
5614 Adaptec AHA-2920A boards with a Future Domain chip on them.
5616 This driver is also available as a module ( = code which can be
5617 inserted in and removed from the running kernel whenever you want).
5618 The module will be called fdomain.o. If you want to compile it as a
5619 module, say M here and read Documentation/modules.txt.
5621 Future Domain MCS-600/700 SCSI support
5623 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
5624 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
5625 is identical to the MCS 700 and hence also supported by this driver.
5626 This driver also supports the Reply SB16/SCSI card (the SCSI part).
5627 It supports multiple adapters in the same system.
5629 This driver is also available as a module ( = code which can be
5630 inserted in and removed from the running kernel whenever you want).
5631 The module will be called fd_mcs.o. If you want to compile it as a
5632 module, say M here and read Documentation/modules.txt.
5634 Generic NCR5380/53c400 SCSI support
5635 CONFIG_SCSI_GENERIC_NCR5380
5636 This is the generic NCR family of SCSI controllers, not to be
5637 confused with the NCR 53c7 or 8xx controllers. It is explained in
5638 section 3.8 of the SCSI-HOWTO, available from
5639 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
5640 of the box, you may have to change some settings in
5641 drivers/scsi/g_NCR5380.h.
5643 This driver is also available as a module ( = code which can be
5644 inserted in and removed from the running kernel whenever you want).
5645 The module will be called g_NCR5380.o. If you want to compile it as
5646 a module, say M here and read Documentation/modules.txt.
5648 Enable NCR53c400 extensions
5649 CONFIG_SCSI_GENERIC_NCR53C400
5650 This enables certain optimizations for the NCR53c400 SCSI cards. You
5651 might as well try it out. Note that this driver will only probe for
5652 the Trantor T130B in its default configuration; you might have to
5653 pass a command line option to the kernel at boot time if it doesn't
5654 detect your card. See the file drivers/scsi/README.g_NCR5380 for
5657 NCR5380/53c400 mapping method (use Port for T130B)
5658 CONFIG_SCSI_G_NCR5380_PORT
5659 The NCR5380 and NCR53c400 SCSI controllers come in two varieties:
5660 port or memory mapped. You should know what you have. The most
5661 common card, Trantor T130B, uses port mapped mode.
5663 NCR53c7,8xx SCSI support
5664 CONFIG_SCSI_NCR53C7xx
5665 This is a driver for the 53c7 and 8xx NCR family of SCSI
5666 controllers, not to be confused with the NCR 5380 controllers. It is
5667 explained in section 3.8 of the SCSI-HOWTO, available from
5668 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
5669 of the box, you may have to change some settings in
5670 drivers/scsi/53c7,8xx.h. Please read drivers/scsi/README.ncr53c7xx
5671 for the available boot time command line options.
5673 Note: there is another driver for the 53c8xx family of controllers
5674 ("NCR53C8XX SCSI support" below). If you want to use them both, you
5675 need to say M to both and build them as modules, but only one may be
5676 active at a time. If you have a 53c8xx board, it's better to use the
5679 This driver is also available as a module ( = code which can be
5680 inserted in and removed from the running kernel whenever you want).
5681 The module will be called 53c7,8xx.o. If you want to compile it as a
5682 module, say M here and read Documentation/modules.txt.
5684 always negotiate synchronous transfers
5685 CONFIG_SCSI_NCR53C7xx_sync
5686 In general, this is good; however, it is a bit dangerous since there
5687 are some broken SCSI devices out there. Take your chances. Safe bet
5690 allow FAST-SCSI [10MHz]
5691 CONFIG_SCSI_NCR53C7xx_FAST
5692 This will enable 10MHz FAST-SCSI transfers with your host
5693 adapter. Some systems have problems with that speed, so it's safest
5697 CONFIG_SCSI_NCR53C7xx_DISCONNECT
5698 This enables the disconnect/reconnect feature of the NCR SCSI
5699 controller. When you say Y here, a slow SCSI device will not lock
5700 the SCSI bus while processing a request, allowing simultaneous use
5701 of e.g. a SCSI hard disk and SCSI tape or CD-ROM drive, and
5702 providing much better performance when using slow and fast SCSI
5703 devices at the same time. Some devices, however, do not operate
5704 properly with this option enabled, and will cause your SCSI system
5705 to hang, which might cause a system crash. The safe answer
5706 therefore is to say N.
5708 NCR53C8XX SCSI support
5709 CONFIG_SCSI_NCR53C8XX
5710 This is the BSD ncr driver adapted to Linux for the NCR53C8XX family
5711 of PCI-SCSI controllers. This driver supports parity checking,
5712 tagged command queuing and fast synchronous data transfers up to 80
5713 MB/s with wide FAST-40 LVD devices and controllers.
5715 Recent versions of the 53C8XX chips are better supported by the
5716 option "SYM53C8XX SCSI support", below.
5718 Note: there is yet another driver for the 53c8xx family of
5719 controllers ("NCR53c7,8xx SCSI support" above). If you want to use
5720 them both, you need to say M to both and build them as modules, but
5721 only one may be active at a time. If you have a 53c8xx board, you
5722 probably do not want to use the "NCR53c7,8xx SCSI support".
5724 Please read drivers/scsi/README.ncr53c8xx for more information.
5726 SYM53C8XX SCSI support
5727 CONFIG_SCSI_SYM53C8XX
5728 This driver supports all the features of recent 53C8XX chips (used
5729 in PCI SCSI controllers), notably the hardware phase mismatch
5730 feature of the SYM53C896.
5732 Older versions of the 53C8XX chips are not supported by this
5733 driver. If your system uses either a 810 rev. < 16, a 815, or a 825
5734 rev. < 16 PCI SCSI processor, you must use the generic NCR53C8XX
5735 driver ("NCR53C8XX SCSI support" above) or configure both the
5736 NCR53C8XX and this SYM53C8XX drivers either as module or linked to
5739 When both drivers are linked into the kernel, the SYM53C8XX driver
5740 is called first at initialization and you can use the 'excl=ioaddr'
5741 driver boot option to exclude attachment of adapters by the
5742 SYM53C8XX driver. For example, entering
5743 'sym53c8xx=excl:0xb400,excl=0xc000' at the lilo prompt prevents
5744 adapters at io address 0xb400 and 0xc000 from being attached by the
5745 SYM53C8XX driver, thus allowing the NCR53C8XX driver to attach them.
5746 The 'excl' option is also supported by the NCR53C8XX driver.
5748 Please read drivers/scsi/README.ncr53c8xx for more information.
5750 synchronous data transfers frequency
5751 CONFIG_SCSI_NCR53C8XX_SYNC
5752 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
5753 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers are
5754 respectively the maximum data transfer rates in mega-transfers per
5755 second for each class. For example, a FAST-20 Wide 16 device is able
5756 to transfer data at 20 million 16 bit packets per second for a total
5759 You may specify 0 if you want to only use asynchronous data
5760 transfers. This is the safest and slowest option. Otherwise, specify
5761 a value between 5 and 80, depending on the capability of your SCSI
5762 controller. The higher the number, the faster the data transfer.
5763 Note that 80 should normally be ok since the driver decreases the
5764 value automatically according to the controller's capabilities.
5766 Your answer to this question is ignored for controllers with NVRAM,
5767 since the driver will get this information from the user set-up. It
5768 also can be overridden using a boot setup option, as follows
5769 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
5770 for FAST-20 synchronous data transfer (20 mega-transfers per
5773 The normal answer therefore is not to go with the default but to
5774 select the maximum value 80 allowing the driver to use the maximum
5775 value supported by each controller. If this causes problems with
5776 your SCSI devices, you should come back and decrease the value.
5778 There is no safe option other than using good cabling, right
5779 terminations and SCSI conformant devices.
5782 CONFIG_SCSI_NCR53C8XX_IOMAPPED
5783 If you say Y here, the driver will use normal IO, as opposed to
5784 memory mapped IO. Memory mapped IO has less latency than normal IO
5785 and works for most Intel-based hardware. Under Linux/Alpha only
5786 normal IO is currently supported by the driver and so, this option
5787 has no effect on those systems.
5789 The normal answer therefore is N; try Y only if you encounter SCSI
5792 not allow targets to disconnect
5793 CONFIG_SCSI_NCR53C8XX_NO_DISCONNECT
5794 This option is only provided for safety if you suspect some SCSI
5795 device of yours to not support properly the target-disconnect
5796 feature. In that case, you would say Y here. In general however, to
5797 not allow targets to disconnect is not reasonable if there is more
5798 than 1 device on a SCSI bus. The normal answer therefore is N.
5800 default tagged command queue depth
5801 CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS
5802 "Tagged command queuing" is a feature of SCSI-2 which improves
5803 performance: the host adapter can send several SCSI commands to a
5804 device's queue even if previous commands haven't finished yet.
5805 Because the device is intelligent, it can optimize its operations
5806 (like head positioning) based on its own request queue. Some SCSI
5807 devices don't implement this properly; if you want to disable this
5808 feature, enter 0 or 1 here (it doesn't matter which).
5810 The default value is 8 and should be supported by most hard disks.
5811 This value can be overridden from the boot command line using the
5812 'tags' option as follows (example):
5813 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
5814 4, set queue depth to 16 for target 2 and target 3 on controller 0
5815 and set queue depth to 10 for target 0 / lun 2 on controller 1.
5817 The normal answer therefore is to go with the default 8 and to use
5818 a boot command line option for devices that need to use a different
5819 command queue depth.
5821 There is no safe option other than using good SCSI devices.
5823 maximum number of queued commands
5824 CONFIG_SCSI_NCR53C8XX_MAX_TAGS
5825 This option allows you to specify the maximum number of commands
5826 that can be queued to any device, when tagged command queuing is
5827 possible. The default value is 32. Minimum is 2, maximum is 64.
5828 Modern hard disks are able to support 64 tags and even more, but
5829 do not seem to be faster when more than 32 tags are being used.
5831 So, the normal answer here is to go with the default value 32 unless
5832 you are using very large hard disks with large cache (>= 1 MB) that
5833 are able to take advantage of more than 32 tagged commands.
5835 There is no safe option and the default answer is recommended.
5837 assume boards are SYMBIOS compatible (EXPERIMENTAL)
5838 CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT
5839 This option allows you to enable some features depending on GPIO
5840 wiring. These General Purpose Input/Output pins can be used for
5841 vendor specific features or implementation of the standard SYMBIOS
5842 features. Genuine SYMBIOS controllers use GPIO0 in output for
5843 controller LED and GPIO3 bit as a flag indicating
5844 singled-ended/differential interface. The Tekram DC-390U/F boards
5845 uses a different GPIO wiring.
5847 Your answer to this question is ignored if all your controllers have
5848 NVRAM, since the driver is able to detect the board type from the
5851 If all the controllers in your system are genuine SYMBIOS boards or
5852 use BIOS and drivers from SYMBIOS, you would want to say Y here,
5853 otherwise N. N is the safe answer.
5855 enable profiling statistics gathering
5856 CONFIG_SCSI_NCR53C8XX_PROFILE
5857 This option allows you to enable profiling information gathering.
5858 These statistics are not very accurate due to the low frequency
5859 of the kernel clock (100 Hz on i386) and have performance impact
5860 on systems that use very fast devices.
5862 The normal answer therefore is N.
5864 include support for the NCR PQS/PDS SCSI card
5865 CONFIG_SCSI_NCR53C8XX_PQS_PDS
5866 Say Y here if you have a special SCSI adapter produced by NCR
5867 corporation called a PCI Quad SCSI or PCI Dual SCSI. You do not need
5868 this if you do not have one of these adapters. However, since this
5869 device is detected as a specific PCI device, this option is quite
5872 The common answer here is N, but answering Y is safe.
5876 This is support for the IBM SCSI adapter found in many of the PS/2
5877 series computers. These machines have an MCA bus, so you need to
5878 answer Y to "MCA support" as well and read Documentation/mca.txt.
5880 If the adapter isn't found during boot (a common problem for models
5881 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
5882 option, where <pun> is the id of the SCSI subsystem (usually 7, but
5883 if that doesn't work check your reference diskette). Owners of model
5884 95 with a LED-matrix-display can in addition activate some activity
5885 info like under OS/2, but more informative, by setting
5886 'ibmmcascsi=display' as an additional kernel parameter. Try "man
5887 bootparam" or see the documentation of your boot loader about how to
5888 pass options to the kernel.
5890 If you want to compile this driver as a module ( = code which can be
5891 inserted in and removed from the running kernel whenever you want),
5892 say M here and read Documentation/modules.txt. The module will be
5896 CONFIG_IBMMCA_SCSI_ORDER_STANDARD
5897 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
5898 are assigned to the drive letters, starting with the lowest SCSI-id
5899 (physical number -- pun) to be drive C:, as seen from DOS and
5900 similar operating systems. When looking into papers describing the
5901 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
5902 The SCSI-standard follows a hardware-hierarchy which says that id 7
5903 has the highest priority and id 0 the lowest. Therefore, the host
5904 adapters are still today everywhere placed as SCSI-id 7 by default.
5905 In the SCSI-standard, the drive letters express the priority of the
5906 disk. C: should be the hard disk, or a partition on it, with the
5907 highest priority. This must therefore be the disk with the highest
5908 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
5909 original definition of the SCSI-standard as also industrial- and
5910 process-control-machines, like VME-CPUs running under realtime-OSs
5911 (e.g. LynxOS, OS9) do.
5913 If you like to run Linux on your MCA-machine with the same
5914 assignment of hard disks as seen from e.g. DOS or OS/2 on your
5915 machine, which is in addition conformant to the SCSI-standard, you
5916 must say Y here. This is also necessary for MCA-Linux users who want
5917 to keep downward compatibility to older releases of the
5918 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
5921 If you like to have the lowest SCSI-id assigned as drive C:, as
5922 modern SCSI-BIOSes do, which does not conform to the standard, but
5923 is widespread and common in the PC-world of today, you must say N
5924 here. If unsure, say Y.
5926 Reset SCSI-devices at boot time
5927 CONFIG_IBMMCA_SCSI_DEV_RESET
5928 By default, SCSI-devices are reset when the machine is powered on.
5929 However, some devices exist, like special-control-devices,
5930 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
5931 not reset when switched on. If you say Y here, each device connected
5932 to your SCSI-bus will be issued a reset-command after it has been
5933 probed, while the kernel is booting. This may cause problems with
5934 more modern devices, like hard disks, which do not appreciate these
5935 reset commands, and can cause your system to hang. So say Y only if
5936 you know that one of your older devices needs it; N is the safe
5939 NCR 53C9x MCA support
5940 CONFIG_SCSI_MCA_53C9X
5941 Some Microchannel machines, notably the NCR 35xx line, use a SCSI
5942 controller based on the NCR 53C94. This driver will allow use of
5943 the controller on the 3550, and very possibly others.
5945 If you want to compile this as a module (= code which can be
5946 inserted and removed from the running kernel whenever you want), say
5947 M here and read Documentation/modules.txt. The module will be called
5950 Always IN2000 SCSI support
5952 This is support for an ISA bus SCSI host adapter. You'll find more
5953 information in drivers/scsi/in2000.readme. If it doesn't work out of
5954 the box, you may have to change the jumpers for IRQ or address
5957 If you want to compile this as a module ( = code which can be
5958 inserted in and removed from the running kernel whenever you want),
5959 say M here and read Documentation/modules.txt. The module will be
5962 Initio 91XXU(W) SCSI support
5964 This is support for the Initio 91XXU(W) SCSI host adapter. Please
5965 read the SCSI-HOWTO, available from
5966 http://www.linuxdoc.org/docs.html#howto .
5968 If you want to compile this as a module ( = code which can be
5969 inserted in and removed from the running kernel whenever you want),
5970 say M here and read Documentation/modules.txt. The module will be
5975 This is support for a SCSI host adapter. It is explained in section
5976 3.10 of the SCSI-HOWTO, available from
5977 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
5978 of the box, you may have to change some settings in
5979 drivers/scsi/pas16.h.
5981 This driver is also available as a module ( = code which can be
5982 inserted in and removed from the running kernel whenever you want).
5983 The module will be called pas16.o. If you want to compile it as a
5984 module, say M here and read Documentation/modules.txt.
5986 Initio INI-A100U2W SCSI support
5988 This is support for the Initio INI-A100U2W SCSI host adapter. Please
5989 read the SCSI-HOWTO, available from
5990 http://www.linuxdoc.org/docs.html#howto .
5992 If you want to compile this as a module ( = code which can be
5993 inserted in and removed from the running kernel whenever you want),
5994 say M here and read Documentation/modules.txt. The module will be
5999 This is support for the PCI2000I EIDE interface card which acts as a
6000 SCSI host adapter. Please read the SCSI-HOWTO, available from
6001 http://www.linuxdoc.org/docs.html#howto .
6003 This driver is also available as a module called pci2000.o ( = code
6004 which can be inserted in and removed from the running kernel
6005 whenever you want). If you want to compile it as a module, say M
6006 here and read Documentation/modules.txt.
6009 CONFIG_SCSI_PCI2220I
6010 This is support for the PCI2220i EIDE interface card which acts as a
6011 SCSI host adapter. Please read the SCSI-HOWTO, available from
6012 http://www.linuxdoc.org/docs.html#howto .
6014 This driver is also available as a module called pci2220i.o ( = code
6015 which can be inserted in and removed from the running kernel
6016 whenever you want). If you want to compile it as a module, say M
6017 here and read Documentation/modules.txt.
6021 This is support for the PSI240i EIDE interface card which acts as a
6022 SCSI host adapter. Please read the SCSI-HOWTO, available from
6023 http://www.linuxdoc.org/docs.html#howto .
6025 This driver is also available as a module called psi240i.o ( = code
6026 which can be inserted in and removed from the running kernel
6027 whenever you want). If you want to compile it as a module, say M
6028 here and read Documentation/modules.txt.
6030 Qlogic FAS SCSI support
6031 CONFIG_SCSI_QLOGIC_FAS
6032 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
6033 FastSCSI! cards as well as any other card based on the FASXX chip
6034 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
6036 This driver does NOT support the PCI versions of these cards. The
6037 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
6038 SCSI support"), below.
6040 Information about this driver is contained in
6041 drivers/scsi/README.qlogicfas. You should also read the SCSI-HOWTO,
6042 available from http://www.linuxdoc.org/docs.html#howto .
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 qlogicfas.o. If you want to compile it as
6047 a module, say M here and read Documentation/modules.txt.
6049 Qlogic ISP SCSI support (EXPERIMENTAL)
6050 CONFIG_SCSI_QLOGIC_ISP
6051 This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
6052 IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
6053 card is supported by the "AM53/79C974 PCI SCSI" driver).
6055 If you say Y here, make sure to choose "BIOS" at the question "PCI
6058 Please read the file drivers/scsi/README.qlogicisp. You should also
6059 read the SCSI-HOWTO, available from
6060 http://www.linuxdoc.org/docs.html#howto .
6062 This driver is also available as a module ( = code which can be
6063 inserted in and removed from the running kernel whenever you want).
6064 The module will be called qlogicisp.o. If you want to compile it as
6065 a module, say M here and read Documentation/modules.txt.
6067 Qlogic ISP FC SCSI support
6068 CONFIG_SCSI_QLOGIC_FC
6069 This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
6071 This driver is also available as a module ( = code which can be
6072 inserted in and removed from the running kernel whenever you want).
6073 The module will be called qlogicfc.o. If you want to compile it as
6074 a module, say M here and read Documentation/modules.txt.
6076 Qlogic QLA 1280 SCSI support
6077 CONFIG_SCSI_QLOGIC_1280
6078 Say Y if you have a QLogic ISP1x80/1x160 SCSI host adapter.
6080 This driver is also available as a module ( = code which can be
6081 inserted in and removed from the running kernel whenever you want).
6082 The module will be called qla1280.o. If you want to compile it as
6083 a module, say M here and read Documentation/modules.txt.
6085 Seagate ST-02 and Future Domain TMC-8xx SCSI support
6087 These are 8-bit SCSI controllers; the ST-01 is also supported by
6088 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
6089 available from http://www.linuxdoc.org/docs.html#howto . If it
6090 doesn't work out of the box, you may have to change some settings in
6091 drivers/scsi/seagate.h.
6093 This driver is also available as a module ( = code which can be
6094 inserted in and removed from the running kernel whenever you want).
6095 The module will be called seagate.o. If you want to compile it as a
6096 module, say M here and read Documentation/modules.txt.
6098 Trantor T128/T128F/T228 SCSI support
6100 This is support for a SCSI host adapter. It is explained in section
6101 3.11 of the SCSI-HOWTO, available from
6102 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
6103 of the box, you may have to change some settings in
6104 drivers/scsi/t128.h. Note that Trantor was purchased by Adaptec, and
6105 some former Trantor products are being sold under the Adaptec name.
6107 This driver is also available as a module ( = code which can be
6108 inserted in and removed from the running kernel whenever you want).
6109 The module will be called t128.o. If you want to compile it as a
6110 module, say M here and read Documentation/modules.txt.
6112 UltraStor SCSI support
6113 CONFIG_SCSI_ULTRASTOR
6114 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
6115 adapter family. This driver is explained in section 3.12 of the
6116 SCSI-HOWTO, available from
6117 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
6118 of the box, you may have to change some settings in
6119 drivers/scsi/ultrastor.h.
6121 Note that there is also another driver for the same hardware:
6122 "UltraStor 14F/34F support", above.
6124 If you want to compile this as a module ( = code which can be
6125 inserted in and removed from the running kernel whenever you want),
6126 say M here and read Documentation/modules.txt. The module will be
6129 7000FASST SCSI support
6130 CONFIG_SCSI_7000FASST
6131 This driver supports the Western Digital 7000 SCSI host adapter
6132 family. Some information is in the source: drivers/scsi/wd7000.c.
6134 This driver is also available as a module ( = code which can be
6135 inserted in and removed from the running kernel whenever you
6136 want). The module will be called wd7000.o. If you want to compile it
6137 as a module, say M here and read Documentation/modules.txt.
6141 This driver supports the ACARD 870U/W SCSI host adapter.
6143 This driver is also available as a module ( = code which can be
6144 inserted in and removed from the running kernel whenever you want).
6145 The module will be called atp870u.o. If you want to compile it as a
6146 module, say M here and read Documentation/modules.txt.
6148 EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support
6150 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
6151 ISA and all EISA i/o addresses are probed looking for the "EATA"
6152 signature. If you chose "BIOS" at the question "PCI access mode",
6153 the addresses of all the PCI SCSI controllers reported by the PCI
6154 subsystem are probed as well.
6156 You want to read the start of drivers/scsi/eata.c and the
6157 SCSI-HOWTO, available from
6158 http://www.linuxdoc.org/docs.html#howto .
6160 Note that there is also another driver for the same hardware
6161 available: "EATA-DMA support". You should say Y to only one of them.
6163 If you want to compile this as a module ( = code which can be
6164 inserted in and removed from the running kernel whenever you want),
6165 say M here and read Documentation/modules.txt. The module will be
6168 enable tagged command queuing
6169 CONFIG_SCSI_EATA_TAGGED_QUEUE
6170 This is a feature of SCSI-2 which improves performance: the host
6171 adapter can send several SCSI commands to a device's queue even if
6172 previous commands haven't finished yet. Most EATA adapters negotiate
6173 this feature automatically with the device, even if your answer is
6174 N. The safe answer is N.
6176 enable elevator sorting
6177 CONFIG_SCSI_EATA_LINKED_COMMANDS
6178 This option enables elevator sorting for all probed SCSI disks and
6179 CDROMs. It definitely reduces the average seek distance when doing
6180 random seeks, but this does not necessarily result in a noticeable
6181 performance improvement: your mileage may vary...
6182 The safe answer is N.
6184 maximum number of queued commands
6185 CONFIG_SCSI_EATA_MAX_TAGS
6186 This specifies how many SCSI commands can be maximally queued for
6187 each probed SCSI device. You should reduce the default value of 16
6188 only if you have disks with buggy or limited tagged command support.
6189 Minimum is 2 and maximum is 62. This value is also the window size
6190 used by the elevator sorting option above. The effective value used
6191 by the driver for each probed SCSI device is reported at boot time.
6193 NCR53c406a SCSI support
6194 CONFIG_SCSI_NCR53C406A
6195 This is support for the NCR53c406a SCSI host adapter. For user
6196 configurable parameters, check out drivers/scsi/NCR53c406.c in the
6197 kernel source. Also read the SCSI-HOWTO, available from
6198 http://www.linuxdoc.org/docs.html#howto .
6200 If you want to compile this driver as a module ( = code which can be
6201 inserted in and removed from the running kernel whenever you want),
6202 say M here and read Documentation/modules.txt. The module will be
6205 Symbios Logic sym53c416 support
6206 CONFIG_SCSI_SYM53C416
6207 This is support for the sym53c416 SCSI host adapter, the SCSI
6208 adapter that comes with some HP scanners. This driver requires that
6209 the sym53c416 is configured first using some sort of pnp
6210 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
6211 are using isapnp then you need to compile this driver as a module
6212 and then load it using insmod after isapnp has run. The parameters
6213 of the configured card(s) should be passed to the driver. The format
6216 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
6218 There is support for up to four adapters. If you want to compile
6219 this driver as a module ( = code which can be inserted in and
6220 removed from the running kernel whenever you want), say M here and
6221 read Documentation/modules.txt. The module will be called
6224 Simple 53c710 SCSI support (Compaq, NCR machines)
6226 This is a simple driver for NCR53c710 based SCSI host adapters.
6228 More complex drivers for this chip are available ("NCR53c7,8xx SCSI
6229 support", above), but they require that the scsi chip be able to do
6230 DMA block moves between memory and on-chip registers, which can
6231 cause problems under certain conditions. This driver is designed to
6232 avoid these problems and is intended to work with any Intel machines
6233 using 53c710 chips, including various Compaq and NCR machines.
6235 Please read the comments at the top of the file
6236 drivers/scsi/sim710.c for more information.
6238 If you want to compile this driver as a module ( = code which can be
6239 inserted in and removed from the running kernel whenever you want),
6240 say M here and read Documentation/modules.txt. The module will be
6243 Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support
6245 This driver supports PCI SCSI host adapters based on the Am53C974A
6246 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
6247 PCscsi/PCnet (Am53/79C974) solutions.
6249 Documentation can be found in drivers/scsi/README.tmscsim.
6251 Note that this driver does NOT support Tekram DC390W/U/F, which are
6252 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
6253 Also note that there is another generic Am53C974 driver,
6254 "AM53/79C974 PCI SCSI support" below. You can pick either one.
6256 If you want to compile this driver as a module ( = code which can be
6257 inserted in and removed from the running kernel whenever you want),
6258 say M here and read Documentation/modules.txt. The module will be
6261 Omit support for other Am53/79C974 based SCSI adapters
6262 CONFIG_SCSI_DC390T_NOGENSUPP
6263 If you say N here, the DC390(T) SCSI driver relies on the DC390
6264 EEPROM to get initial values for its settings, such as speed,
6265 termination, etc. If it can't find this EEPROM, it will use defaults
6266 or the user supplied boot/module parameters. For details on driver
6267 configuration see drivers/scsi/README.tmscsim.
6269 If you say Y here and if no EEPROM is found, the driver gives up and
6270 thus only supports Tekram DC390(T) adapters. This can be useful if
6271 you have a DC390(T) and another Am53C974 based adapter, which, for
6272 some reason, you want to drive with the other AM53C974 driver.
6276 AM53/79C974 PCI SCSI support
6277 CONFIG_SCSI_AM53C974
6278 This is support for the AM53/79C974 SCSI host adapters. Please read
6279 drivers/scsi/README.AM53C974 for details. Also, the SCSI-HOWTO,
6280 available from http://www.linuxdoc.org/docs.html#howto , is for
6283 Note that there is another driver for AM53C974 based adapters:
6284 "Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support", above. You
6285 can pick either one.
6287 If you want to compile this driver as a module ( = code which can be
6288 inserted in and removed from the running kernel whenever you want),
6289 say M here and read Documentation/modules.txt. The module will be
6292 AMI MegaRAID support
6293 CONFIG_SCSI_MEGARAID
6294 This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490
6295 and 467 SCSI host adapters.
6297 If you want to compile this driver as a module ( = code which can be
6298 inserted in and removed from the running kernel whenever you want),
6299 say M here and read Documentation/modules.txt. The module will be
6302 GDT SCSI Disk Array Controller support
6304 This is a driver for all SCSI Disk Array Controllers (EISA/ISA/PCI)
6305 manufactured by ICP vortex. It is documented in the kernel source in
6306 drivers/scsi/gdth.c and drivers/scsi/gdth.h.
6308 This driver is also available as a module ( = code which can be
6309 inserted in and removed from the running kernel whenever you want).
6310 If you want to compile it as a module, say M here and read
6311 Documentation/modules.txt.
6313 IOMEGA parallel port (ppa - older drives)
6315 This driver supports older versions of IOMEGA's parallel port ZIP
6316 drive (a 100 MB removable media device).
6318 Note that you can say N here if you have the SCSI version of the ZIP
6319 drive: it will be supported automatically if you said Y to the
6320 generic "SCSI disk support", above.
6322 If you have the ZIP Plus drive or a more recent parallel port ZIP
6323 drive (if the supplied cable with the drive is labeled "AutoDetect")
6324 then you should say N here and Y to "IOMEGA parallel port (imm -
6325 newer drives)", below.
6327 For more information about this driver and how to use it you should
6328 read the file drivers/scsi/README.ppa. You should also read the
6329 SCSI-HOWTO, which is available from
6330 http://www.linuxdoc.org/docs.html#howto . If you use this driver,
6331 you will still be able to use the parallel port for other tasks,
6332 such as a printer; it is safe to compile both drivers into the
6335 This driver is also available as a module which can be inserted in
6336 and removed from the running kernel whenever you want. To compile
6337 this driver as a module, say M here and read
6338 Documentation/modules.txt. The module will be called ppa.o.
6340 IOMEGA parallel port (imm - newer drives)
6342 This driver supports newer versions of IOMEGA's parallel port ZIP
6343 drive (a 100 MB removable media device).
6345 Note that you can say N here if you have the SCSI version of the ZIP
6346 drive: it will be supported automatically if you said Y to the
6347 generic "SCSI disk support", above.
6349 If you have the ZIP Plus drive or a more recent parallel port ZIP
6350 drive (if the supplied cable with the drive is labeled "AutoDetect")
6351 then you should say Y here; if you have an older ZIP drive, say N
6352 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
6354 For more information about this driver and how to use it you should
6355 read the file drivers/scsi/README.ppa. You should also read the
6356 SCSI-HOWTO, which is available from
6357 http://www.linuxdoc.org/docs.html#howto . If you use this driver,
6358 you will still be able to use the parallel port for other tasks,
6359 such as a printer; it is safe to compile both drivers into the
6362 This driver is also available as a module which can be inserted in
6363 and removed from the running kernel whenever you want. To compile
6364 this driver as a module, say M here and read
6365 Documentation/modules.txt. The module will be called imm.o.
6367 Force the Iomega ZIP drivers to use EPP-16
6368 CONFIG_SCSI_IZIP_EPP16
6369 EPP (Enhanced Parallel Port) is a standard for parallel ports which
6370 allows them to act as expansion buses that can handle up to 64
6373 Some parallel port chipsets are slower than their motherboard, and
6374 so we have to control the state of the chipset's FIFO queue every
6375 now and then to avoid data loss. This will be done if you say Y
6378 Generally, saying Y is the safe option and slows things down a bit.
6380 Assume slow parallel port control register
6381 CONFIG_SCSI_IZIP_SLOW_CTR
6382 Some parallel ports are known to have excessive delays between
6383 changing the parallel port control register and good data being
6384 available on the parallel port data/status register. This option
6385 forces a small delay (1.0 usec to be exact) after changing the
6386 control register to let things settle out. Enabling this option may
6387 result in a big drop in performance but some very old parallel ports
6388 (found in 386 vintage machines) will not work properly.
6390 Generally, saying N is fine.
6392 Parallel port SCSI device support
6394 There are many external CD-ROM and disk devices that connect through
6395 your computer's parallel port. Lots of them are actually SCSI
6396 devices using a parallel port SCSI adapter. This option enables the
6397 ppSCSI subsystem which contains drivers for many of these external
6398 drives. You may also want to look at CONFIG_PARIDE (Parallel port
6399 IDE device support).
6401 If you built ppSCSI support into your kernel, you may still build
6402 the individual protocol modules and high-level drivers as loadable
6403 modules. If you build this support as a module, it will be called
6406 To use the ppSCSI support, you must say Y or M here and also to at
6407 least one protocol driver (e.g. "Shuttle EPST adapter", "Iomega VPI0
6408 adapter", "Shining ScarSCI adapter" etc.).
6410 Adaptec APA-348 adapter
6412 This option enables support for the APA-348 adapter from Adaptec
6413 (also known as Trantor T348). If you build this as a module it will
6416 Adaptec APA-358 adapter
6418 This option enables support for the APA-358 adapter from Adaptec
6419 (also known as Trantor T358). If you build this as a module it will
6424 This option enables support for the Iomega VPI0 adapter found in the
6425 original ZIP-100 drives and the Jaz Traveller. If you build this as
6426 a module it will be called vpi0.o.
6428 OnSpec 90c26 adapter
6429 CONFIG_PPSCSI_ONSCSI
6430 This option enables support for the OnSpec 90c26 in its SCSI adapter
6431 mode. If you build this as a module it will be called onscsi.o.
6433 Shining SparSCI adapter
6434 CONFIG_PPSCSI_SPARCSI
6435 This option enables support for the WBS-11A parallel port SCSI
6436 adapter. This adapter has been marketed by LinkSys as the
6437 "ParaSCSI+" and by Shining Technologies as the "SparCSI". If you
6438 build this as a module it will be called sparcsi.o.
6440 Shuttle EPSA-2 adapter
6442 This option enables support for the Shuttle Technologies EPSA2
6443 parallel port SCSI adapter. EPAS2 is a predecessor to the EPST. If
6444 you build this as a module it will be called epsa2.o.
6446 Shuttle EPST adapter
6448 This option enables support for the Shuttle Technologies EPST
6449 parallel port SCSI adapter. If you build this as a module is will
6452 SCSI Debug host simulator. (EXPERIMENTAL)
6454 This is a host adapter simulator that can be programmed to simulate
6455 a large number of conditions that could occur on a real bus. The
6456 advantage is that many hard to reproduce problems can be tested in a
6457 controlled environment where there is reduced risk of losing
6458 important data. This is primarily of use to people trying to debug
6459 the middle and upper layers of the SCSI subsystem. If unsure, say N.
6461 Fibre Channel support and FC4 SCSI support
6463 Fibre Channel is a high speed serial protocol mainly used to
6464 connect large storage devices to the computer; it is compatible with
6465 and intended to replace SCSI.
6467 This is an experimental support for storage arrays connected to your
6468 computer using optical fibre cables and the "X3.269-199X Fibre
6469 Channel Protocol for SCSI" specification. If you want to use this,
6470 you need to say Y here and to "SCSI support" as well as to the
6471 drivers for the storage array itself and for the interface adapter
6472 such as SOC or SOC+. This subsystem could even serve for IP
6473 networking, with some code extensions.
6479 Serial Optical Channel is an interface card with one or two Fibre
6480 Optic ports, each of which can be connected to a disk array. Note
6481 that if you have older firmware in the card, you'll need the
6482 microcode from the Solaris driver to make it work.
6484 This support is also available as a module called soc.o ( = code
6485 which can be inserted in and removed from the running kernel
6486 whenever you want). If you want to compile it as a module, say M
6487 here and read Documentation/modules.txt.
6489 Sun SOC+ (aka SOCAL)
6491 Serial Optical Channel Plus is an interface card with up to two
6492 Fibre Optic ports. This card supports FC Arbitrated Loop (usually
6493 A5000 or internal FC disks in E[3-6]000 machines through the
6494 Interface Board). You'll probably need the microcode from the
6495 Solaris driver to make it work.
6497 This support is also available as a module called socal.o ( = code
6498 which can be inserted in and removed from the running kernel
6499 whenever you want). If you want to compile it as a module, say M
6500 here and read Documentation/modules.txt.
6502 SparcSTORAGE Array 100 and 200 series
6504 If you never bought a disk array made by Sun, go with N.
6506 This support is also available as a module called pluto.o ( = code
6507 which can be inserted in and removed from the running kernel
6508 whenever you want). If you want to compile it as a module, say M
6509 here and read Documentation/modules.txt.
6511 Sun Enterprise Network Array (A5000 and EX500)
6513 This driver drives FC-AL disks connected through a Fibre Channel
6514 card using the drivers/fc4 layer (currently only SOCAL). The most
6515 common is either A5000 array or internal disks in E[3-6]000
6518 This support is also available as a module called fcal.o ( = code
6519 which can be inserted in and removed from the running kernel
6520 whenever you want). If you want to compile it as a module, say M
6521 here and read Documentation/modules.txt. If unsure, say N.
6524 CONFIG_SCSI_ACORNSCSI_3
6525 This enables support for the Acorn SCSI card (aka30). If you have an
6526 Acorn system with one of these, say Y. If unsure, say N.
6528 Acorn SCSI tagged queue support
6529 CONFIG_SCSI_ACORNSCSI_TAGGED_QUEUE
6530 Say Y here to enable tagged queuing support on the Acorn SCSI card.
6532 This is a feature of SCSI-2 which improves performance: the host
6533 adapter can send several SCSI commands to a device's queue even if
6534 previous commands haven't finished yet. Some SCSI devices don't
6535 implement this properly, so the safe answer is N.
6537 Acorn SCSI Synchronous transfers support
6538 CONFIG_SCSI_ACORNSCSI_SYNC
6539 Say Y here to enable synchronous transfer negotiation with all
6540 targets on the Acorn SCSI card.
6542 In general, this improves performance; however some SCSI devices
6543 don't implement it properly, so the safe answer is N.
6547 This enables support for the Oak SCSI card. If you have an Acorn
6548 system with one of these, say Y. If unsure, say N.
6550 Cumana SCSI I support
6551 CONFIG_SCSI_CUMANA_1
6552 This enables support for the Cumana SCSI I card. If you have an
6553 Acorn system with one of these, say Y. If unsure, say N.
6555 Cumana SCSI II support (EXPERIMENTAL)
6556 CONFIG_SCSI_CUMANA_2
6557 This enables support for the Cumana SCSI II card. If you have an
6558 Acorn system with one of these, say Y. If unsure, say N.
6562 This enables support for the EcoSCSI card -- a small card that sits
6563 in the Econet socket. If you have an Acorn system with one of these,
6564 say Y. If unsure, say N.
6566 EESOX SCSI support (EXPERIMENTAL)
6567 CONFIG_SCSI_EESOXSCSI
6568 This enables support for the EESOX SCSI card. If you have an Acorn
6569 system with one of these, say Y, otherwise say N.
6571 Powertec SCSI support (EXPERIMENTAL)
6572 CONFIG_SCSI_POWERTECSCSI
6573 This enables support for the Powertec SCSI card on Acorn systems. If
6574 you have one of these, say Y. If unsure, say N.
6576 IEEE 1394 (aka FireWire) support
6578 IEEE 1394 describes a high performance serial bus, which is also
6579 known as FireWire(tm) or i.Link(tm) and is used for connecting all
6580 sorts of devices (most notably digital video cameras) to your
6583 If you have FireWire hardware and want to use it, say Y here. This
6584 is the core support only, you will also need to select a driver for
6585 your IEEE 1394 adapter.
6587 If you want to compile this as a module ( = code which can be
6588 inserted in and removed from the running kernel whenever you want),
6589 say M here and read Documentation/modules.txt. The module will be
6592 TI PCILynx IEEE 1394 support
6593 CONFIG_IEEE1394_PCILYNX
6594 Say Y here if you have a IEEE-1394 controller with the Texas
6595 Instruments PCILynx chip. Note: this driver is written for revision
6596 2 of this chip and may not work with revision 0.
6598 If you want to compile this as a module ( = code which can be
6599 inserted in and removed from the running kernel whenever you want),
6600 say M here and read Documentation/modules.txt. The module will be
6603 Use local RAM on PCILynx board
6604 CONFIG_IEEE1394_PCILYNX_LOCALRAM
6605 This option makes the PCILynx driver use local RAM available on some
6606 PCILynx setups for Packet Control Lists. Local RAM is random access
6607 memory which resides on the PCILynx board as opposed to on your
6608 computer's motherboard. Local RAM may speed up command processing
6609 because no PCI transfers are necessary during use of the Packet
6612 Note that there are no known PCILynx systems providing local RAM
6613 except for the evaluation boards by Texas Instruments and that the
6614 PCILynx does not reliably report missing RAM. This means that it is
6615 dangerous to say Y here if you are not absolutely sure that your
6616 board provides 64KB of local RAM.
6620 Support for non-IEEE1394 local ports
6621 CONFIG_IEEE1394_PCILYNX_PORTS
6622 This option enables driver code to access the RAM, ROM and AUX ports
6623 of the PCILynx through character devices in /dev. If you don't know
6624 what this is about then you won't need it.
6628 Adaptec AIC-5800 IEEE 1394 support
6629 CONFIG_IEEE1394_AIC5800
6630 Say Y here if you have a IEEE 1394 controller using the Adaptec
6631 AIC-5800 chip. All Adaptec host adapters (89xx series) use this
6632 chip, as well as miro's DV boards.
6634 If you want to compile this as a module ( = code which can be
6635 inserted in and removed from the running kernel whenever you want),
6636 say M here and read Documentation/modules.txt. The module will be
6639 OHCI (Open Host Controller Interface) support
6640 CONFIG_IEEE1394_OHCI1394
6641 Say Y here if you have a IEEE 1394 controller based on OHCI.
6642 The current driver was only tested with OHCI chipsets made
6643 by Texas Instruments. However, most third-party vendors use
6646 If you want to compile this as a module ( = code which can be
6647 inserted in and removed from the running kernel whenever you want),
6648 say M here and read Documentation/modules.txt. The module will be
6651 Raw IEEE 1394 I/O support
6652 CONFIG_IEEE1394_RAWIO
6653 Say Y here if you want support for the raw device. This is generally
6654 a good idea, so you should say Y here. The raw device enables
6655 direct communication of user programs with the IEEE 1394 bus and
6656 thus with the attached peripherals.
6658 If you want to compile this as a module ( = code which can be
6659 inserted in and removed from the running kernel whenever you want),
6660 say M here and read Documentation/modules.txt. The module will be
6663 Excessive debugging output
6664 CONFIG_IEEE1394_VERBOSEDEBUG
6665 If you say Y here, you will get very verbose debugging logs from the
6666 subsystem which includes a dump of the header of every sent and
6667 received packet. This can amount to a high amount of data collected
6668 in a very short time which is usually also saved to disk by the
6669 system logging daemons.
6671 Say Y if you really want or need the debugging output, everyone else
6674 Network device support?
6676 You can say N here if you don't intend to connect your Linux box to
6677 any other computer at all or if all your connections will be over a
6678 telephone line with a modem either via UUCP (UUCP is a protocol to
6679 forward mail and news between unix hosts over telephone lines; read
6680 the UUCP-HOWTO, available from
6681 http://www.linuxdoc.org/docs.html#howto ) or dialing up a shell
6682 account or a BBS, even using term (term is a program which gives you
6683 almost full Internet connectivity if you have a regular dial up
6684 shell account on some Internet connected Unix computer. Read
6685 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html ).
6687 You'll have to say Y if your computer contains a network card that
6688 you want to use under Linux (make sure you know its name because you
6689 will be asked for it and read the Ethernet-HOWTO (especially if you
6690 plan to use more than one network card under Linux)) or if you want
6691 to use SLIP (Serial Line Internet Protocol is the protocol used to
6692 send Internet traffic over telephone lines or null modem cables) or
6693 CSLIP (compressed SLIP) or PPP (Point to Point Protocol, a better
6694 and newer replacement for SLIP) or PLIP (Parallel Line Internet
6695 Protocol is mainly used to create a mini network by connecting the
6696 parallel ports of two local machines) or AX.25/KISS (protocol for
6697 sending Internet traffic over amateur radio links).
6699 Make sure to read the NET-3-HOWTO. Eventually, you will have to read
6700 Olaf Kirch's excellent and free book "Network Administrator's
6701 Guide", to be found in http://www.linuxdoc.org/docs.html#guide . If
6704 Dummy net driver support
6706 This is essentially a bit-bucket device (i.e. traffic you send to
6707 this device is consigned into oblivion) with a configurable IP
6708 address. It is most commonly used in order to make your currently
6709 inactive SLIP address seem like a real address for local programs.
6710 If you use SLIP or PPP, you might want to say Y here. Since this
6711 thing often comes in handy, the default is Y. It won't enlarge your
6712 kernel either. What a deal. Read about it in the Network
6713 Administrator's Guide, available from
6714 http://www.linuxdoc.org/docs.html#guide .
6716 If you want to compile this as a module ( = code which can be
6717 inserted in and removed from the running kernel whenever you want),
6718 say M here and read Documentation/modules.txt. The module will be
6719 called dummy.o. If you want to use more than one dummy device at a
6720 time, you need to compile this driver as a module. Instead of
6721 'dummy', the devices will then be called 'dummy0', 'dummy1' etc.
6723 Bonding driver support
6725 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
6726 Channels together. This is called 'Etherchannel' by Cisco,
6727 'Trunking' by Sun, and 'Bonding' in Linux.
6729 If you have two ethernet connections to some other computer, you can
6730 make them behave like one double speed connection using this driver.
6731 Naturally, this has to be supported at the other end as well, either
6732 with a similar Bonding Linux driver, a Cisco 5500 switch or a
6733 SunTrunking SunSoft driver.
6735 This is similar to the EQL driver, but it merges Ethernet segments
6736 instead of serial lines.
6738 If you want to compile this as a module ( = code which can be
6739 inserted in and removed from the running kernel whenever you want),
6740 say M here and read Documentation/modules.txt. The module will be
6743 SLIP (serial line) support
6745 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
6746 connect to your Internet service provider or to connect to some
6747 other local Unix box or if you want to configure your Linux box as a
6748 Slip/CSlip server for other people to dial in. SLIP (Serial Line
6749 Internet Protocol) is a protocol used to send Internet traffic over
6750 serial connections such as telephone lines or null modem cables;
6751 nowadays, the protocol PPP is more commonly used for this same
6754 Normally, your access provider has to support SLIP in order for you
6755 to be able to use it, but there is now a SLIP emulator called SLiRP
6756 around (available via FTP (user: anonymous) from
6757 ftp://metalab.unc.edu/pub/Linux/system/network/serial/ ) which
6758 allows you to use SLIP over a regular dial up shell connection. If
6759 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
6760 NET-3-HOWTO, available from
6761 http://www.linuxdoc.org/docs.html#howto , explains how to
6762 configure SLIP. Note that you don't need this option if you just
6763 want to run term (term is a program which gives you almost full
6764 Internet connectivity if you have a regular dial up shell account on
6765 some Internet connected Unix computer. Read
6766 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html ). SLIP
6767 support will enlarge your kernel by about 4 KB. If unsure, say N.
6769 If you want to compile this as a module ( = code which can be
6770 inserted in and removed from the running kernel whenever you want),
6771 say M here and read Documentation/modules.txt as well as
6772 Documentation/networking/net-modules.txt. The module will be called
6775 CSLIP compressed headers
6776 CONFIG_SLIP_COMPRESSED
6777 This protocol is faster than SLIP because it uses compression on the
6778 TCP/IP headers (not on the data itself), but it has to be supported
6779 on both ends. Ask your access provider if you are not sure and
6780 answer Y, just in case. You will still be able to use plain SLIP. If
6781 you plan to use SLiRP, the SLIP emulator (available from
6782 ftp://metalab.unc.edu/pub/Linux/system/network/serial/ ) which
6783 allows you to use SLIP over a regular dial up shell connection, you
6784 definitely want to say Y here. The NET-3-HOWTO, available from
6785 http://www.linuxdoc.org/docs.html#howto , explains how to configure
6786 CSLIP. This won't enlarge your kernel.
6788 Keepalive and linefill
6790 Adds additional capabilities to the SLIP driver to support the
6791 RELCOM line fill and keepalive monitoring. Ideal on poor quality
6794 Six bit SLIP encapsulation
6795 CONFIG_SLIP_MODE_SLIP6
6796 Just occasionally you may need to run IP over hostile serial
6797 networks that don't pass all control characters or are only seven
6798 bit. Saying Y here adds an extra mode you can use with SLIP:
6799 "slip6". In this mode, SLIP will only send normal ASCII symbols over
6800 the serial device. Naturally, this has to be supported at the other
6801 end of the link as well. It's good enough, for example, to run IP
6802 over the async ports of a Camtec JNT Pad. If unsure, say N.
6804 PPP (point-to-point protocol) support
6806 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
6807 the same purpose: sending Internet traffic over telephone (and other
6808 serial) lines. Ask your access provider if they support it, because
6809 otherwise you can't use it; most internet access providers these
6810 days support PPP rather than SLIP.
6812 To use PPP, you need an additional program called pppd as described
6813 in Documentation/networking/ppp.txt and in the PPP-HOWTO, available
6814 at http://www.linuxdoc.org/docs.html#howto . If you upgrade
6815 from an older kernel, you might need to upgrade pppd as well. The
6816 PPP option enlarges your kernel by about 16 KB.
6818 There are actually two versions of PPP: the traditional PPP for
6819 asynchronous lines, such as regular analog phone lines, and
6820 synchronous PPP which can be used over digital ISDN lines for
6821 example. If you want to use PPP over phone lines or other
6822 asynchronous serial lines, you need to say Y (or M) here and also to
6823 the next option, "PPP support for async serial ports". For PPP over
6824 synchronous lines, you should say Y (or M) here and to "Support
6825 synchronous PPP", below.
6827 This driver is also available as a module ( = code which can be
6828 inserted in and removed from the running kernel whenever you want).
6829 If you said Y to "Version information on all symbols" above, then
6830 you cannot compile the PPP driver into the kernel; you can then only
6831 compile it as a module. The module will be called ppp_generic.o. If
6832 you want to compile it as a module, say M here and read
6833 Documentation/modules.txt as well as
6834 Documentation/networking/net-modules.txt.
6836 PPP multilink support (EXPERIMENTAL)
6837 CONFIG_PPP_MULTILINK
6838 PPP multilink is a protocol (defined in RFC 1990) which allows you
6839 to combine several (logical or physical) lines into one logical PPP
6840 connection, so that you can utilize your full bandwidth.
6842 This has to be supported at the other end as well and you need a
6843 version of the pppd daemon which understands the multilink protocol.
6847 PPP support for async serial ports
6849 Say Y (or M) here if you want to be able to use PPP over standard
6850 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
6851 a modem (not a synchronous or ISDN modem) to contact your ISP, you
6854 This code is also available as a module (code which can be inserted
6855 into and removed from the running kernel). If you want to compile
6856 it as a module, say M here and read Documentation/modules.txt.
6860 PPP support for sync tty ports
6862 Say Y (or M) here if you want to be able to use PPP over synchronous
6863 (HDLC) tty devices, such as the SyncLink adapter. These devices
6864 are often used for high-speed leased lines like T1/E1.
6866 This code is also available as a module (code which can be inserted
6867 into and removed from the running kernel). If you want to compile
6868 it as a module, say M here and read Documentation/modules.txt.
6870 PPP Deflate compression
6872 Support for the Deflate compression method for PPP, which uses the
6873 Deflate algorithm (the same algorithm that gzip uses) to compress
6874 each PPP packet before it is sent over the wire. The machine at the
6875 other end of the PPP link (usually your ISP) has to support the
6876 Deflate compression method as well for this to be useful. Even if
6877 they don't support it, it is safe to say Y here.
6879 This code is also available as a module (code which can be inserted
6880 into and removed from the running kernel). If you want to compile
6881 it as a module, say M here and read Documentation/modules.txt.
6883 PPP BSD-Compress compression
6885 Support for the BSD-Compress compression method for PPP, which uses
6886 the LZW compression method to compress each PPP packet before it is
6887 sent over the wire. The machine at the other end of the PPP link
6888 (usually your ISP) has to support the BSD-Compress compression
6889 method as well for this to be useful. Even if they don't support it,
6890 it is safe to say Y here.
6892 The PPP Deflate compression method ("PPP Deflate compression",
6893 above) is preferable to BSD-Compress, because it compresses better
6896 Note that the BSD compression code will always be compiled as a
6897 module; it is called bsd_comp.o and will show up in the directory
6898 modules once you have said "make modules". If unsure, say N.
6900 PPP over Ethernet (EXPERIMENTAL)
6902 Support for PPP over Ethernet.
6904 This driver requires a specially patched pppd daemon. The patch to
6905 pppd, along with binaries of a patched pppd package can be found at:
6906 http://www.math.uwaterloo.ca/~mostrows
6908 Wireless LAN (non-hamradio)
6910 Support for wireless LANs and everything having to do with radio,
6911 but not with amateur radio or FM broadcasting.
6913 Saying Y here also enables the Wireless Extensions (creates
6914 /proc/net/wireless and enables ifconfig access). The Wireless
6915 Extension is a generic API allowing a driver to expose to the user
6916 space configuration and statistics specific to common Wireless LANs.
6917 The beauty of it is that a single set of tool can support all the
6918 variations of Wireless LANs, regardless of their type (as long as
6919 the driver supports Wireless Extension). Another advantage is that
6920 these parameters may be changed on the fly without restarting the
6921 driver (or Linux). If you wish to use Wireless Extensions with
6922 wireless PCMCIA (PC-) cards, you need to say Y here; you can fetch
6924 http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html .
6926 Some user-level drivers for scarab devices which don't require
6927 special kernel support are available from
6928 ftp://shadow.cabi.net/pub/Linux .
6930 STRIP (Metricom Starmode radio IP)
6932 Say Y if you have a Metricom radio and intend to use Starmode Radio
6933 IP. STRIP is a radio protocol developed for the MosquitoNet project
6934 (on the WWW at http://mosquitonet.stanford.edu/ ) to send Internet
6935 traffic using Metricom radios. Metricom radios are small, battery
6936 powered, 100kbit/sec packet radio transceivers, about the size and
6937 weight of a cellular telephone. (You may also have heard them called
6938 "Metricom modems" but we avoid the term "modem" because it misleads
6939 many people into thinking that you can plug a Metricom modem into a
6940 phone line and use it as a modem.)
6942 You can use STRIP on any Linux machine with a serial port, although
6943 it is obviously most useful for people with laptop computers. If you
6944 think you might get a Metricom radio in the future, there is no harm
6945 in saying Y to STRIP now, except that it makes the kernel a bit
6948 You can also compile this as a module ( = code which can be inserted
6949 in and removed from the running kernel whenever you want), say M
6950 here and read Documentation/modules.txt. The module will be called
6953 AT&T WaveLAN & DEC RoamAbout DS support
6955 The Lucent WaveLAN (formerly NCR and AT&T; or DEC RoamAbout DS) is
6956 a Radio LAN (wireless Ethernet-like Local Area Network) using the
6957 radio frequencies 900 MHz and 2.4 GHz.
6959 This driver support the ISA version of the WaveLAN card. A separate
6960 driver for the PCMCIA (PC-card) hardware is available in David
6961 Hinds' pcmcia-cs package (see the file Documentation/Changes for
6964 If you want to use an ISA WaveLAN card under Linux, say Y and read
6965 the Ethernet-HOWTO, available from
6966 http://www.linuxdoc.org/docs.html#howto . Some more specific
6967 information is contained in Documentation/networking/wavelan.txt and
6968 in the source code drivers/net/wavelan.p.h.
6970 You will also need the wireless tools package available from
6971 http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html .
6972 Please read the man pages contained therein.
6974 This driver is also available as a module ( = code which can be
6975 inserted in and removed from the running kernel whenever you want).
6976 The module will be called wavelan.o. If you want to compile it as a
6977 module, say M here and read Documentation/modules.txt as well as
6978 Documentation/networking/net-modules.txt.
6980 Aironet Arlan 655 & IC2200 DS support
6982 Aironet makes Arlan, a class of wireless LAN adapters. These use the
6983 www.Telxon.com chip, which is also used on several similar cards.
6984 This driver is tested on the 655 and IC2200 series cards. Look at
6985 http://www.ylenurme.ee/~elmer/655/ for the latest information.
6987 The driver is built as two modules, arlan and arlan-proc. The latter
6988 is the /proc interface and is not needed most of time.
6990 On some computers the card ends up in non-valid state after some
6991 time. Use a ping-reset script to clear it.
6993 Aironet 4500/4800 series adapters
6995 www.aironet.com (recently bought by Cisco) makes these 802.11 DS
6996 adapters. Driver by Elmer Joandi (elmer@ylenurme.ee).
6998 Say Y here if you have such an adapter, and then say Y below to
6999 the option that applies to your particular type of card (PCI, ISA,
7002 This driver is also available as a module ( = code which can be
7003 inserted in and removed from the running kernel whenever you want).
7004 The module will be called aironet4500_core.o. If you want to
7005 compile it as a module, say M here and read
7006 Documentation/modules.txt as well as
7007 Documentation/networking/net-modules.txt.
7009 quick config parameters:
7010 SSID=tsunami - "The Password"
7011 adhoc=1 there are no Access Points around
7012 master=1 Adhoc master (the one who creates network
7014 slave=1 Adhoc slave (btw, it is still forming own net
7015 sometimes, and has problems with firmware...
7016 change IbssJoinNetTimeout from /proc...)
7017 channel=1..? meaningful in adhoc mode
7019 If you have problems with screwing up card, both_bap_lock=1 is a
7020 conservative value (performance hit 15%).
7022 All other parameters can be set via the proc interface.
7024 Aironet 4500/4800 ISA/PCI/PNP/365 support
7025 CONFIG_AIRONET4500_NONCS
7026 If you have an ISA, PCI or PCMCIA Aironet 4500/4800 wireless LAN
7027 card, say Y here, and then also to the options below that apply
7030 This driver is also available as a module ( = code which can be
7031 inserted in and removed from the running kernel whenever you want).
7032 The module will be called aironet4500_card.o. If you want to
7033 compile it as a module, say M here and read
7034 Documentation/modules.txt
7036 Aironet 4500/4800 PNP support
7037 CONFIG_AIRONET4500_PNP
7038 If you have an ISA Aironet 4500/4800 card which you want to use in
7039 PNP (Plug and Play) mode, say Y here. This is the recommended mode
7040 for ISA cards. Remember however to enable the PNP jumper on the
7041 board if you say Y here.
7043 Aironet 4500/4800 PCI support
7044 CONFIG_AIRONET4500_PCI
7045 If you have an PCI Aironet 4500/4800 card, say Y here.
7047 Aironet 4500/4800 ISA broken support (EXPERIMENTAL)
7048 CONFIG_AIRONET4500_ISA
7049 If you have an ISA Aironet 4500/4800 card which you want to run in
7050 non-PNP mode, say Y here. This is not recommended and does not work
7051 correctly at this point. Say N.
7053 Aironet 4500/4800 I365 broken support (EXPERIMENTAL)
7054 CONFIG_AIRONET4500_I365
7055 If you have a PCMCIA Aironet 4500/4800 card which you want to use
7056 without the standard PCMCIA cardservices provided by the pcmcia-cs
7057 package, say Y here. This is not recommended, so say N.
7059 Aironet 4500/4800 PCMCIA support
7060 CONFIG_AIRONET4500_CS
7061 Say Y here if you have a PCMCIA Aironet 4500/4800 card which you
7062 want to use with the standard PCMCIA cardservices provided by the
7065 This driver is also available as a module ( = code which can be
7066 inserted in and removed from the running kernel whenever you want).
7067 The module will be called aironet4500_cs.o. If you want to
7068 compile it as a module, say M here and read
7069 Documentation/modules.txt.
7071 Aironet 4500/4800 PROC interface
7072 CONFIG_AIRONET4500_PROC
7073 If you say Y here (and to the "/proc file system" below), you will
7074 be able to configure your Aironet card via the
7075 /proc/sys/aironet4500 interface.
7077 Additional info: look in drivers/net/aironet4500_rids.c.
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 aironet4500_proc.o. If you want to
7082 compile it as a module, say M here and read
7083 Documentation/modules.txt.
7085 NOTE: the proc interface uses a lot of memory, so it is recommended
7086 to compile it as a module and remove the module after
7089 LAPB over Ethernet driver
7091 This is a driver for a pseudo device (typically called /dev/lapb0)
7092 which allows you to open an LAPB point-to-point connection to some
7093 other computer on your Ethernet network. In order to do this, you
7094 need to say Y or M to the driver for your Ethernet card as well as
7095 to "LAPB Data Link Driver".
7097 If you want to compile this driver as a module ( = code which can be
7098 inserted in and removed from the running kernel whenever you want),
7099 say M here and read Documentation/modules.txt. The module will be
7100 called lapbether.o. If unsure, say N.
7104 This is a driver for sending and receiving X.25 frames over regular
7105 asynchronous serial lines such as telephone lines equipped with
7106 ordinary modems. Experts should note that this driver doesn't
7107 currently comply with the asynchronous HDLS framing protocols in
7108 CCITT recommendation X.25.
7110 If you want to compile this driver as a module ( = code which can be
7111 inserted in and removed from the running kernel whenever you want),
7112 say M here and read Documentation/modules.txt. The module will be
7113 called x25_asy.o. If unsure, say N.
7115 PCMCIA network device support
7117 Say Y if you would like to include support for any PCMCIA or CardBus
7118 network adapters, then say Y to the driver for your particular card
7119 below. PCMCIA- or PC-cards are credit-card size devices often used
7120 with laptops computers; CardBus is the newer and faster version of
7123 To use your PC-cards, you will need supporting software from David
7124 Hinds' pcmcia-cs package (see the file Documentation/Changes for
7125 location). You also want to check out the PCMCIA-HOWTO, available
7126 from http://www.linuxdoc.org/docs.html#howto .
7130 3Com 3c589 PCMCIA support
7132 Say Y here if you intend to attach a 3Com 3c589 or compatible PCMCIA
7133 (PC-card) Ethernet card to your computer.
7135 This driver is also available as a module ( = code which can be
7136 inserted in and removed from the running kernel whenever you want).
7137 The module will be called 3c589_cs.o. If you want to compile it as a
7138 module, say M here and read Documentation/modules.txt. If unsure,
7141 3Com 3c574 PCMCIA support
7143 Say Y here if you intend to attach a 3Com 3c574 or compatible PCMCIA
7144 (PC-card) Fast Ethernet card to your computer.
7146 This driver is also available as a module ( = code which can be
7147 inserted in and removed from the running kernel whenever you want).
7148 The module will be called 3c574_cs.o. If you want to compile it as a
7149 module, say M here and read Documentation/modules.txt. If unsure,
7152 Fujitsu FMV-J18x PCMCIA support
7153 CONFIG_PCMCIA_FMVJ18X
7154 Say Y here if you intend to attach a Fujitsu FMV-J18x or compatible
7155 PCMCIA (PC-card) Ethernet card to your computer.
7157 This driver is also available as a module ( = code which can be
7158 inserted in and removed from the running kernel whenever you want).
7159 The module will be called fmvj18x_cs.o. If you want to compile it as
7160 a module, say M here and read Documentation/modules.txt. If unsure,
7163 NE2000 compatible PCMCIA support
7165 Say Y here if you intend to attach an NE2000 compatible PCMCIA
7166 (PC-card) Ethernet or Fast Ethernet card to your computer.
7168 This driver is also available as a module ( = code which can be
7169 inserted in and removed from the running kernel whenever you want).
7170 The module will be called pcnet_cs.o. If you want to compile it as a
7171 module, say M here and read Documentation/modules.txt. If unsure,
7174 New Media PCMCIA support
7175 CONFIG_PCMCIA_NMCLAN
7176 Say Y here if you intend to attach a New Media Ethernet or LiveWire
7177 PCMCIA (PC-card) Ethernet card to your computer.
7179 This driver is also available as a module ( = code which can be
7180 inserted in and removed from the running kernel whenever you want).
7181 The module will be called nmclan_cs.o. If you want to compile it as
7182 a module, say M here and read Documentation/modules.txt. If unsure,
7185 SMC 91Cxx PCMCIA support
7186 CONFIG_PCMCIA_SMC91C92
7187 Say Y here if you intend to attach an SMC 91Cxx compatible PCMCIA
7188 (PC-card) Ethernet or Fast Ethernet card to your computer.
7190 This driver is also available as a module ( = code which can be
7191 inserted in and removed from the running kernel whenever you want).
7192 The module will be called smc91c92_cs.o. If you want to compile it
7193 as a module, say M here and read Documentation/modules.txt. If
7196 Xircom 16-bit PCMCIA support
7197 CONFIG_PCMCIA_XIRC2PS
7198 Say Y here if you intend to attach a Xircom 16-bit PCMCIA
7199 (PC-card) Ethernet or Fast Ethernet card to your computer.
7201 This driver is also available as a module ( = code which can be
7202 inserted in and removed from the running kernel whenever you want).
7203 The module will be called xirc2ps_cs.o. If you want to compile it as
7204 a module, say M here and read Documentation/modules.txt. If unsure,
7207 COM20020 ARCnet PCMCIA support
7208 CONFIG_ARCNET_COM20020_CS
7209 Say Y here if you intend to attach this type of ARCnet PCMCIA card
7212 This driver is also available as a module ( = code which can be
7213 inserted in and removed from the running kernel whenever you want).
7214 The module will be called com20020_cs.o. If you want to compile it
7215 as a module, say M here and read Documentation/modules.txt. If
7218 IBM PCMCIA Token Ring adapter support
7220 Say Y here if you intend to attach this type of Token Ring PCMCIA
7221 card to your computer. You then also need to say Y to "Token Ring
7224 This driver is also available as a module ( = code which can be
7225 inserted in and removed from the running kernel whenever you want).
7226 The module will be called ibmtr_cs.o. If you want to compile it
7227 as a module, say M here and read Documentation/modules.txt.
7229 Xircom Tulip-like CardBus support
7230 CONFIG_PCMCIA_XIRTULIP
7231 This driver is for the Digital "Tulip" Ethernet CardBus adapters.
7232 It should work with most DEC 21*4*-based chips/ethercards, as well
7233 as with work-alike chips from Lite-On (PNIC) and Macronix (MXIC) and
7236 This driver is also available as a module ( = code which can be
7237 inserted in and removed from the running kernel whenever you want).
7238 The module will be called xircom_tulip_cb.o. If you want to compile
7239 it as a module, say M here and read Documentation/modules.txt. If
7243 CONFIG_NET_PCMCIA_RADIO
7244 Say Y here if you would like to use a PCMCIA (PC-card) device to
7245 connect to a wireless local area network. Then say Y to the driver
7246 for your particular card below.
7248 To use your PC-cards, you will need supporting software from David
7249 Hinds' pcmcia-cs package (see the file Documentation/Changes for
7250 location). You also want to check out the PCMCIA-HOWTO, available
7251 from http://www.linuxdoc.org/docs.html#howto .
7253 Aviator/Raytheon 2.4MHz wireless support
7255 Say Y here if you intend to attach an Aviator/Raytheon PCMCIA
7256 (PC-card) wireless Ethernet networking card to your computer.
7257 Please read the file Documentation/networking/ray_cs.txt for
7260 This driver is also available as a module ( = code which can be
7261 inserted in and removed from the running kernel whenever you want).
7262 The module will be called ray_cs.o. If you want to compile it as a
7263 module, say M here and read Documentation/modules.txt. If unsure,
7266 Xircom Netwave AirSurfer wireless support
7267 CONFIG_PCMCIA_NETWAVE
7268 Say Y here if you intend to attach this type of PCMCIA (PC-card)
7269 wireless Ethernet networking card to your computer.
7271 This driver is also available as a module ( = code which can be
7272 inserted in and removed from the running kernel whenever you want).
7273 The module will be called netwave_cs.o. If you want to compile it as
7274 a module, say M here and read Documentation/modules.txt. If unsure,
7277 AT&T/Lucent Wavelan wireless support
7278 CONFIG_PCMCIA_WAVELAN
7279 Say Y here if you intend to attach an AT&T/Lucent Wavelan PCMCIA
7280 (PC-card) wireless Ethernet networking card to your computer. This
7281 driver is for the non-IEEE-802.11 Wavelan cards.
7283 This driver is also available as a module ( = code which can be
7284 inserted in and removed from the running kernel whenever you want).
7285 The module will be called wavelan_cs.o. If you want to compile it as
7286 a module, say M here and read Documentation/modules.txt. If unsure,
7289 PLIP (parallel port) support
7291 PLIP (Parallel Line Internet Protocol) is used to create a
7292 reasonably fast mini network consisting of two (or, rarely, more)
7293 local machines. A PLIP link from a Linux box is a popular means to
7294 install a Linux distribution on a machine which doesn't have a CDROM
7295 drive (a minimal system has to be transferred with floppies first).
7296 The kernels on both machines need to have this PLIP option enabled
7299 The PLIP driver has two modes, mode 0 and mode 1. The parallel ports
7300 (the connectors at the computers with 25 holes) are connected with
7301 "null printer" or "Turbo Laplink" cables which can transmit 4 bits
7302 at a time (mode 0) or with special PLIP cables, to be used on
7303 bidirectional parallel ports only, which can transmit 8 bits at a
7304 time (mode 1); you can find the wiring of these cables in
7305 Documentation/networking/PLIP.txt. The cables can be up to 15m long.
7306 Mode 0 works also if one of the machines runs DOS/Windows and has
7307 some PLIP software installed, e.g. the Crynwr PLIP packet driver
7308 (http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html ) and
7309 winsock or NCSA's telnet.
7311 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
7312 as the NET-3-HOWTO, both available from
7313 http://www.linuxdoc.org/docs.html#howto . Note that the PLIP
7314 protocol has been changed and this PLIP driver won't work together
7315 with the PLIP support in Linux versions 1.0.x. This option enlarges
7316 your kernel by about 8 KB.
7318 If you want to compile this as a module ( = code which can be
7319 inserted in and removed from the running kernel whenever you want),
7320 say M here and read Documentation/modules.txt as well as
7321 Documentation/networking/net-modules.txt. The module will be called
7322 plip.o. If unsure, say Y or M, in case you buy a laptop later.
7324 EQL (serial line load balancing) support
7326 If you have two serial connections to some other computer (this
7327 usually requires two modems and two telephone lines) and you use
7328 SLIP (the protocol for sending Internet traffic over telephone
7329 lines) or PPP (a better SLIP) on them, you can make them behave like
7330 one double speed connection using this driver. Naturally, this has
7331 to be supported at the other end as well, either with a similar EQL
7332 Linux driver or with a Livingston Portmaster 2e.
7334 Say Y if you want this and read Documentation/networking/eql.txt.
7335 You may also want to read section 6.2 of the NET-3-HOWTO, available
7336 from http://www.linuxdoc.org/docs.html#howto .
7338 This driver is also available as a module ( = code which can be
7339 inserted in and removed from the running kernel whenever you want).
7340 The module will be called eql.o. If you want to compile it as a
7341 module, say M here and read Documentation/modules.txt. If unsure,
7344 Universal TUN/TAP device driver.
7346 TUN/TAP provides packet reception and transmission for user space programs.
7347 It can be viewed as a simple Point-to-Point or Ethernet device, which
7348 instead of receiving packets from a physical media, receives them from
7349 user space program and instead of sending packets via physical media
7350 writes them to the user space program.
7352 When a program opens /dev/net/tun, driver creates and registers
7353 corresponding net device tunX or tapX. After a program closed above
7354 devices, driver will automatically delete tunXX or tapXX device and all
7355 routes corresponding to it.
7357 Please read Documentation/networking/tuntap.txt for more information.
7359 This driver is also available as a module ( = code which can be
7360 inserted in and removed from the running kernel whenever you want).
7361 The module will be called tun.o. If you want to compile it as a
7362 module, say M here and read Documentation/modules.txt.
7364 If you don't know what to use this for, you don't need it.
7366 Ethertap network tap (OBSOLETE)
7368 If you say Y here (and have said Y to "Kernel/User network link
7369 driver", above) and create a character special file /dev/tap0 with
7370 major number 36 and minor number 16 using mknod ("man mknod"), you
7371 will be able to have a user space program read and write raw
7372 Ethernet frames from/to that special file. tap0 can be configured
7373 with ifconfig and route like any other Ethernet device but it is not
7374 connected to any physical LAN; everything written by the user to
7375 /dev/tap0 is treated by the kernel as if it had come in from a LAN
7376 to the device tap0; everything the kernel wants to send out over the
7377 device tap0 can instead be read by the user from /dev/tap0: the user
7378 mode program replaces the LAN that would be attached to an ordinary
7379 Ethernet device. Please read the file
7380 Documentation/networking/ethertap.txt for more information.
7382 This driver is also available as a module ( = code which can be
7383 inserted in and removed from the running kernel whenever you want).
7384 The module will be called ethertap.o. If you want to compile it as a
7385 module, say M here and read Documentation/modules.txt.
7387 If you don't know what to use this for, you don't need it.
7389 Sealevel Systems 4021 support
7390 CONFIG_SEALEVEL_4021
7391 This is a driver for the Sealevel Systems ACB 56 serial I/O adapter.
7393 This driver can only be compiled as a module ( = code which can be
7394 inserted in and removed from the running kernel whenever you want).
7395 If you want to do that, say M here. The module will be called
7398 SyncLink HDLC/SYNCPPP support
7399 CONFIG_SYNCLINK_SYNCPPP
7400 Enables HDLC/SYNCPPP support for the SyncLink WAN driver.
7401 Normally the SyncLink WAN driver works with the main PPP
7402 driver (ppp.c) and pppd program. HDLC/SYNCPPP support allows use
7403 of the Cisco HDLC/PPP driver (syncppp.c).
7404 The SyncLink WAN driver (in character devices) must also be enabled.
7406 Frame Relay (DLCI) support
7408 This is support for the frame relay protocol; frame relay is a fast
7409 low-cost way to connect to a remote Internet access provider or to
7410 form a private wide area network. The one physical line from your
7411 box to the local "switch" (i.e. the entry point to the frame relay
7412 network, usually at the phone company) can carry several logical
7413 point-to-point connections to other computers connected to the frame
7414 relay network. For a general explanation of the protocol, check out
7415 http://www.frforum.com/ on the WWW. To use frame relay, you need
7416 supporting hardware (called FRAD) and certain programs from the
7417 net-tools package as explained in
7418 Documentation/networking/framerelay.txt.
7420 This driver is also available as a module ( = code which can be
7421 inserted in and removed from the running kernel whenever you want).
7422 The module will be called dlci.o. If you want to compile it as a
7423 module, say M here and read Documentation/modules.txt.
7427 This is the maximal number of logical point-to-point frame relay
7428 connections (the identifiers of which are called DCLIs) that
7429 the driver can handle. The default is probably fine.
7433 You can specify here how many logical point-to-point frame relay
7434 connections (the identifiers of which are called DCLIs) should be
7435 handled by each of your hardware frame relay access devices. Go with
7438 Sangoma S502A FRAD support
7440 Say Y here if you need a driver for the Sangoma S502A, S502E, and
7441 S508 Frame Relay Access Devices. These are multi-protocol cards, but
7442 only frame relay is supported by the driver at this time. Please
7443 read Documentation/framerelay.txt.
7445 This driver is also available as a module ( = code which can be
7446 inserted in and removed from the running kernel whenever you want).
7447 The module will be called sdla.o. If you want to compile it as a
7448 module, say M here and read Documentation/modules.txt.
7450 Acorn Econet/AUN protocols (EXPERIMENTAL)
7452 Econet is a fairly old and slow networking protocol mainly used by
7453 Acorn computers to access file and print servers. It uses native
7454 Econet network cards. AUN is an implementation of the higher level
7455 parts of Econet that runs over ordinary Ethernet connections, on
7456 top of the UDP packet protocol, which in turn runs on top of the
7457 Internet protocol IP.
7459 If you say Y here, you can choose with the next two options whether
7460 to send Econet/AUN traffic over a UDP Ethernet connection or over
7461 a native Econet network card.
7463 This driver is also available as a module ( = code which can be
7464 inserted in and removed from the running kernel whenever you want).
7465 The module will be called econet.o. If you want to compile it as a
7466 module, say M here and read Documentation/modules.txt.
7469 CONFIG_ECONET_AUNUDP
7470 Say Y here if you want to send Econet/AUN traffic over a UDP
7471 connection (UDP is a packet based protocol that runs on top of the
7472 Internet protocol IP) using an ordinary Ethernet network card.
7475 CONFIG_ECONET_NATIVE
7476 Say Y here if you have a native Econet network card installed in
7481 Wide Area Networks (WANs), such as X.25, frame relay and leased
7482 lines, are used to interconnect Local Area Networks (LANs) over vast
7483 distances with data transfer rates significantly higher than those
7484 achievable with commonly used asynchronous modem connections.
7485 Usually, a quite expensive external device called a `WAN router' is
7486 needed to connect to a WAN.
7488 As an alternative, WAN routing can be built into the Linux kernel.
7489 With relatively inexpensive WAN interface cards available on the
7490 market, a perfectly usable router can be built for less than half
7491 the price of an external router. If you have one of those cards and
7492 wish to use your Linux box as a WAN router, say Y here and also to
7493 the WAN driver for your card, below. You will then need the
7494 wan-tools package which is available from ftp://ftp.sangoma.com .
7495 Read Documentation/networking/wan-router.txt for more information.
7497 The WAN routing support is also available as a module called
7498 wanrouter.o ( = code which can be inserted in and removed from the
7499 running kernel whenever you want). If you want to compile it as a
7500 module, say M here and read Documentation/modules.txt.
7504 Fast switching (read help!)
7505 CONFIG_NET_FASTROUTE
7506 Saying Y here enables direct NIC-to-NIC (NIC = Network Interface
7507 Card) data transfers on the local network, which is fast.
7509 IMPORTANT NOTE: This option is NOT COMPATIBLE with "Network packet
7510 filtering" (CONFIG_NETFILTER). Say N here if you say Y there.
7512 However, it will work with all options in the "IP: advanced router"
7513 section (except for "IP: use TOS value as routing key" and
7514 "IP: use FWMARK value as routing key").
7516 At the moment, few devices support fast switching (tulip is one of
7517 them, a modified 8390 driver can be found at
7518 ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz ).
7522 Forwarding between high speed interfaces
7523 CONFIG_NET_HW_FLOWCONTROL
7524 This option enables NIC (Network Interface Card) hardware throttling
7525 during periods of extremal congestion. At the moment only a couple
7526 of device drivers support it (really only one -- tulip, a modified
7527 8390 driver can be found at
7528 ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz ).
7530 Really, this option is applicable to any machine attached to a fast
7531 enough network, and even a 10 Mb NIC is able to kill a not very slow
7532 box, such as a 120MHz Pentium.
7534 However, do not say Y here if you did not experience any serious
7537 QoS and/or fair queueing
7539 When the kernel has several packets to send out over a network
7540 device, it has to decide which ones to send first, which ones to
7541 delay, and which ones to drop. This is the job of the packet
7542 scheduler, and several different algorithms for how to do this
7543 "fairly" have been proposed.
7545 If you say N here, you will get the standard packet scheduler, which
7546 is a FIFO (first come, first served). If you say Y here, you will be
7547 able to choose from among several alternative algorithms which can
7548 then be attached to different network devices. This is useful for
7549 example if some of your network devices are real time devices that
7550 need a certain minimum data flow rate, or if you need to limit the
7551 maximum data flow rate for traffic which matches specified criteria.
7552 This code is considered to be experimental.
7554 To administer these schedulers, you'll need the user-level utilities
7555 from the package iproute2+tc at ftp://ftp.inr.ac.ru/ip-routing/ .
7556 That package also contains some documentation; for more, check out
7557 http://snafu.freedom.org/linux2.2/iproute-notes.html .
7559 This Quality of Service (QoS) support will enable you to use
7560 Differentiated Services (diffserv) and Resource Reservation Protocol
7561 (RSVP) on your Linux router if you also say Y to "QoS support",
7562 "Packet classifier API" and to some classifiers below. Documentation
7563 and software is at http://icawww1.epfl.ch/linux-diffserv/ .
7565 If you say Y here and to "/proc file system" below, you will be able
7566 to read status information about packet schedulers from the file
7569 The available schedulers are listed in the following questions; you
7570 can say Y to as many as you like. If unsure, say N now.
7572 CBQ packet scheduler
7574 Say Y here if you want to use the Class-Based Queueing (CBQ) packet
7575 scheduling algorithm for some of your network devices. This
7576 algorithm classifies the waiting packets into a tree-like hierarchy
7577 of classes; the leaves of this tree are in turn scheduled by
7578 separate algorithms (called "disciplines" in this context).
7580 See the top of net/sched/sch_cbq.c for references about the CBQ
7583 CBQ is a commonly used scheduler, so if you're unsure, you should
7584 say Y here. Then say Y to all the queueing algorithms below that you
7585 want to use as CBQ disciplines. Then say Y to "Packet classifier
7586 API" and say Y to all the classifiers you want to use; a classifier
7587 is a routine that allows you to sort your outgoing traffic into
7588 classes based on a certain criterion.
7590 This code is also available as a module called sch_cbq.o ( = code
7591 which can be inserted in and removed from the running kernel
7592 whenever you want). If you want to compile it as a module, say M
7593 here and read Documentation/modules.txt.
7595 CSZ packet scheduler
7597 Say Y here if you want to use the Clark-Shenker-Zhang (CSZ) packet
7598 scheduling algorithm for some of your network devices. At the
7599 moment, this is the only algorithm that can guarantee service for
7600 real-time applications (see the top of net/sched/sch_csz.c for
7601 details and references about the algorithm).
7603 Note: this scheduler is currently broken.
7605 This code is also available as a module called sch_csz.o ( = code
7606 which can be inserted in and removed from the running kernel
7607 whenever you want). If you want to compile it as a module, say M
7608 here and read Documentation/modules.txt.
7610 #ATM pseudo-scheduler
7616 The simplest PRIO pseudo scheduler
7618 Say Y here if you want to use an n-band priority queue packet
7619 "scheduler" for some of your network devices or as a leaf discipline
7620 for the CBQ scheduling algorithm. If unsure, say Y.
7622 This code is also available as a module called sch_prio.o ( = code
7623 which can be inserted in and removed from the running kernel
7624 whenever you want). If you want to compile it as a module, say M
7625 here and read Documentation/modules.txt.
7629 Say Y here if you want to use the Random Early Detection (RED)
7630 packet scheduling algorithm for some of your network devices (see
7631 the top of net/sched/sch_red.c for details and references about the
7634 This code is also available as a module called sch_red.o ( = code
7635 which can be inserted in and removed from the running kernel
7636 whenever you want). If you want to compile it as a module, say M
7637 here and read Documentation/modules.txt.
7641 Say Y here if you want to use the Stochastic Fairness Queueing (SFQ)
7642 packet scheduling algorithm for some of your network devices or as a
7643 leaf discipline for the CBQ scheduling algorithm (see the top of
7644 net/sched/sch_sfq.c for details and references about the SFQ
7647 This code is also available as a module called sch_sfq.o ( = code
7648 which can be inserted in and removed from the running kernel
7649 whenever you want). If you want to compile it as a module, say M
7650 here and read Documentation/modules.txt.
7654 Say Y here if you want to use the True Link Equalizer (TLE) packet
7655 scheduling algorithm for some of your network devices or as a leaf
7656 discipline for the CBQ scheduling algorithm. This queueing
7657 discipline allows the combination of several physical devices into
7658 one virtual device. (see the top of net/sched/sch_teql.c for
7661 This code is also available as a module called sch_teql.o ( = code
7662 which can be inserted in and removed from the running kernel
7663 whenever you want). If you want to compile it as a module, say M
7664 here and read Documentation/modules.txt.
7668 Say Y here if you want to use the Simple Token Bucket Filter (TBF)
7669 packet scheduling algorithm for some of your network devices or as a
7670 leaf discipline for the CBQ scheduling algorithm (see the top of
7671 net/sched/sch_tbf.c for a description of the TBF algorithm).
7673 This code is also available as a module called sch_tbf.o ( = code
7674 which can be inserted in and removed from the running kernel
7675 whenever you want). If you want to compile it as a module, say M
7676 here and read Documentation/modules.txt.
7679 #+tristate ' GRED queue' CONFIG_NET_SCH_GRED
7680 #+tristate ' Diffserv field marker' CONFIG_NET_SCH_DSMARK
7681 #+tristate ' Ingress Qdisc' CONFIG_NET_SCH_INGRESS
7685 Say Y here if you want to include Quality Of Service scheduling
7686 features, which means that you will be able to request certain
7687 rate-of-flow limits for your network devices.
7689 This Quality of Service (QoS) support will enable you to use
7690 Differentiated Services (diffserv) and Resource Reservation Protocol
7691 (RSVP) on your Linux router if you also say Y to "Packet classifier
7692 API" and to some classifiers below. Documentation and software is at
7693 http://icawww1.epfl.ch/linux-diffserv/ .
7695 Note that the answer to this question won't directly affect the
7696 kernel: saying N will just cause this configure script to skip all
7697 the questions about QoS support.
7700 CONFIG_NET_ESTIMATOR
7701 In order for Quality of Service scheduling to work, the current
7702 rate-of-flow for a network device has to be estimated; if you say Y
7703 here, the kernel will do just that.
7705 Packet classifier API
7707 The CBQ scheduling algorithm requires that network packets which are
7708 scheduled to be sent out over a network device be classified
7709 according to some criterion. If you say Y here, you will get a
7710 choice of several different packet classifiers with the following
7713 This will enable you to use Differentiated Services (diffserv) and
7714 Resource Reservation Protocol (RSVP) on your Linux router.
7715 Documentation and software is at
7716 http://icawww1.epfl.ch/linux-diffserv/ .
7719 #tristate ' TC index classifier' CONFIG_NET_CLS_TCINDEX
7721 Routing tables based classifier
7722 CONFIG_NET_CLS_ROUTE4
7723 If you say Y here, you will be able to classify outgoing packets
7724 according to the route table entry they matched. If unsure, say Y.
7726 This code is also available as a module called cls_route.o ( = code
7727 which can be inserted in and removed from the running kernel
7728 whenever you want). If you want to compile it as a module, say M
7729 here and read Documentation/modules.txt.
7731 Firewall based classifier
7733 If you say Y here, you will be able to classify outgoing packets
7734 according to firewall criteria you specified.
7736 This code is also available as a module called cls_fw.o ( = code
7737 which can be inserted in and removed from the running kernel
7738 whenever you want). If you want to compile it as a module, say M
7739 here and read Documentation/modules.txt.
7743 If you say Y here, you will be able to classify outgoing packets
7744 according to their destination address. If unsure, say Y.
7746 This code is also available as a module called cls_u32.o ( = code
7747 which can be inserted in and removed from the running kernel
7748 whenever you want). If you want to compile it as a module, say M
7749 here and read Documentation/modules.txt
7751 Special RSVP classifier
7753 The Resource Reservation Protocol (RSVP) permits end systems to
7754 request a minimum and maximum data flow rate for a connection; this
7755 is important for real time data such as streaming sound or video.
7757 Say Y here if you want to be able to classify outgoing packets based
7758 on their RSVP requests.
7760 This code is also available as a module called cls_rsvp.o ( = code
7761 which can be inserted in and removed from the running kernel
7762 whenever you want). If you want to compile it as a module, say M
7763 here and read Documentation/modules.txt
7765 Special RSVP classifier for IPv6
7766 CONFIG_NET_CLS_RSVP6
7767 The Resource Reservation Protocol (RSVP) permits end systems to
7768 request a minimum and maximum data flow rate for a connection; this
7769 is important for real time data such as streaming sound or video.
7771 Say Y here if you want to be able to classify outgoing packets based
7772 on their RSVP requests and you are using the new Internet Protocol
7773 IPv6 as opposed to the older and more common IPv4.
7775 This code is also available as a module called cls_rsvp6.o ( = code
7776 which can be inserted in and removed from the running kernel
7777 whenever you want). If you want to compile it as a module, say M
7778 here and read Documentation/modules.txt
7781 # Traffic policing (needed for in/egress)
7782 # CONFIG_NET_CLS_POLICE
7784 ### Some expert please fill these in
7787 Network code profiler
7789 If you say Y here and to "/proc file system support" below, some
7790 obscure and undocumented information about the network code's
7791 performance will be written to /proc/net/profile. If you don't know
7792 what it is about, you don't need it: say N.
7794 Wan interfaces support
7796 Wide Area Networks (WANs), such as X.25, frame relay and leased
7797 lines, are used to interconnect Local Area Networks (LANs) over vast
7798 distances with data transfer rates significantly higher than those
7799 achievable with commonly used asynchronous modem connections.
7800 Usually, a quite expensive external device called a `WAN router' is
7801 needed to connect to a WAN.
7803 As an alternative, a relatively inexpensive WAN interface card can
7804 allow your Linux box to directly connect to a WAN. If you have one
7805 of those cards and wish to use it under Linux, say Y here and also
7806 to the WAN driver for your card, below.
7810 Comtrol Hostess SV-11 support
7812 This is a network card for low speed synchronous serial links, at
7813 up to 256Kbps. It supports both PPP and Cisco HDLC.
7815 At this point, the driver can only be compiled as a module.
7817 COSA/SRP sync serial boards support
7819 This is a driver for COSA and SRP synchronous serial boards. These
7820 boards allow to connect synchronous serial devices (for example
7821 base-band modems, or any other device with the X.21, V.24, V.35 or
7822 V.36 interface) to your Linux box. The cards can work as the
7823 character device, synchronous PPP network device, or the Cisco HDLC
7826 To actually use the COSA or SRP board, you will need user-space
7827 utilities for downloading the firmware to the cards and to set them
7828 up. Look at the http://www.fi.muni.cz/~kas/cosa/ for more
7829 information about the cards (including the pointer to the user-space
7830 utilities). You can also read the comment at the top of the
7831 drivers/net/cosa.c for details about the cards and the driver
7834 The driver will be compiled as a module ( = code which can be
7835 inserted in and removed from the running kernel whenever you want).
7836 The module will be called cosa.o. For general information about
7837 modules read Documentation/modules.txt.
7839 Lan Media sync serial boards support
7841 This is a driver for the following Lan Media family of serial boards.
7843 LMC 1000 board allows you to connect synchronous serial devices (for
7844 example base-band modems, or any other device with the X.21, V.24,
7845 V.35 or V.36 interface) to your Linux box.
7847 LMC 1200 with on board DSU board allows you to connect your Linux
7848 box dirrectly to a T1 or E1 circuit.
7850 LMC 5200 board provides a HSSI interface capable of runnig up to
7851 52 mbits per second.
7853 LMC 5245 board connects directly to a T3 circuit saving the
7854 additional external hardware.
7856 To change setting such as syncPPP vs cisco HDLC or clock source you
7857 will need lmcctl. It it available at ftp.lanmedia.com.
7859 This code is also available as a module called lmc.o ( = code
7860 which can be inserted in and removed from the running kernel
7861 whenever you want). If you want to compile it as a module, say M
7862 here and read Documentation/modules.txt.
7864 Fibre Channel driver support
7866 Fibre Channel is a high speed serial protocol mainly used to connect
7867 large storage devices to the computer; it is compatible with and
7868 intended to replace SCSI.
7870 If you intend to use Fibre Channel, you need to have a Fibre channel
7871 adaptor card in your computer; say Y here and to the driver for your
7872 adaptor below. You also should have said Y to "SCSI support" and
7873 "SCSI generic support".
7875 Interphase 5526 Tachyon chipset based adaptor support
7877 Say Y here if you have a Fibre Channel adaptor of this kind.
7879 The driver is also available as a module ( = code which can be
7880 inserted in and removed from the running kernel whenever you want).
7881 The module will be called iph5526.o. For general information about
7882 modules read Documentation/modules.txt.
7884 Red Creek Hardware VPN (EXPERIMENTAL)
7886 This is a driver for hardware which provides a Virtual Private
7887 Network (VPN). Say Y if you have it.
7889 This code is also available as a module called rcpci.o ( = code
7890 which can be inserted in and removed from the running kernel
7891 whenever you want). If you want to compile it as a module, say M
7892 here and read Documentation/modules.txt.
7896 This is a driver for ISA SBNI12-xx cards which are low cost
7897 alternatives to leased line modems. Say Y if you want to insert
7898 the driver into the kernel or say M to compile it as a module (the
7899 module will be called sbni.o).
7901 You can find more information and last versions of drivers and
7902 utilities at http://www.granch.ru . If you have any question you
7903 can send email to sbni@granch.ru.
7908 CONFIG_WAN_ROUTER_DRIVERS
7909 If you have a WAN interface card and you want your Linux box to act
7910 as a WAN router, thereby connecting you Local Area Network to the
7911 outside world over the WAN connection, say Y here and then to the
7912 driver for your card below. In addition, you need to say Y to "Wan
7915 You will need the wan-tools package which is available from
7916 ftp://ftp.sangoma.com . Read Documentation/networking/wan-router.txt
7917 for more information.
7919 Note that the answer to this question won't directly affect the
7920 kernel: saying N will just cause this configure script to skip all
7921 the questions about WAN router drivers. If unsure, say N.
7923 Sangoma WANPIPE(tm) multiprotocol cards
7924 CONFIG_VENDOR_SANGOMA
7925 WANPIPE from Sangoma Technologies Inc. (http://www.sangoma.com ) is
7926 a family of intelligent multiprotocol WAN adapters with data
7927 transfer rates up to T1 (1.544 Mbps). They are also known as
7928 Synchronous Data Link Adapters (SDLA) and designated S502E(A), S503
7929 or S508. These cards support the X.25, Frame Relay, and PPP
7930 protocols. If you have one or more of these cards, say Y to this
7931 option; you may then also want to read the file
7932 Documentation/networking/wanpipe.txt. The next questions will ask
7933 you about the protocols you want the driver to support.
7935 The driver will be compiled as a module ( = code which can be
7936 inserted in and removed from the running kernel whenever you want).
7937 The module will be called wanpipe.o. For general information about
7938 modules read Documentation/modules.txt.
7940 Maximum number of cards
7941 CONFIG_WANPIPE_CARDS
7942 Enter number of WANPIPE adapters installed in your machine. The
7943 driver can support up to 8 cards. You may enter more than you
7944 actually have if you plan to add more cards in the future without
7945 re-compiling the driver, but remember that in this case you'll waste
7946 some kernel memory (about 1K per card).
7948 WANPIPE Cisco HDLC support
7949 CONFIG_WANPIPE_CHDLC
7950 Say Y to this option if you are planning to connect a WANPIPE card
7951 to a connection which uses the synchronous Cisco HDLC (High-level
7952 Data Link Control) protocol. This protocol is often used on
7953 high-speed leased lines like T1/E1.
7955 WANPIPE X.25 support
7957 Say Y to this option if you are planning to connect a WANPIPE card
7958 to an X.25 network. You should then also have said Y to "CCITT X.25
7959 Packet Layer" and "LAPB Data Link Driver", above. If you say N, the
7960 X.25 support will not be included in the driver (saves about 16 KB
7963 WANPIPE Frame Relay support
7965 Say Y to this option if you are planning to connect a WANPIPE card
7966 to a frame relay network. You should then also have said Y to "Frame
7967 Relay (DLCI) support", above. If you say N, the frame relay
7968 support will not be included in the driver (saves about 16 KB of
7973 Say Y to this option if you are planning to connect a WANPIPE card
7974 to a leased line using Point-to-Point protocol (PPP). You should
7975 then also have said Y to "PPP (point-to-point) support", above. If
7976 you say N, the PPP support will not be included in the driver (saves
7977 about 16 KB of kernel memory).
7979 MultiGate/COMX support
7981 Say Y if you want to use any board from the MultiGate (COMX) family.
7982 These boards are synchronous serial adapters for the PC,
7983 manufactured by ITConsult-Pro Co, Hungary.
7985 Read linux/Documentation/networking/comx.txt for help on configuring
7986 and using COMX interfaces. Further info on these cards can be found
7987 at http://www.itc.hu or <info@itc.hu>.
7989 You must say Y to "/proc file system support" (CONFIG_PROC_FS) to
7992 If you want to compile this as a module, say M and read
7993 Documentation/modules.txt. The module will be called comx.o.
7995 COMX/CMX/HiCOMX board support
7997 Hardware driver for the 'CMX', 'COMX' and 'HiCOMX' boards from the
7998 MultiGate family. Say Y if you have one of these.
8000 You will need additional firmware to use these cards, which are
8001 downloadable from ftp://ftp.itc.hu/.
8003 If you want to compile this as a module, say M and read
8004 Documentation/modules.txt. The module will be called comx-hw-comx.o.
8006 LoCOMX board support
8007 CONFIG_COMX_HW_LOCOMX
8008 Hardware driver for the 'LoCOMX' board from the MultiGate family.
8009 Say Y if you have a board like this.
8011 If you want to compile this as a module, say M and read
8012 Documentation/modules.txt. The module will be called
8015 MixCOM board support
8016 CONFIG_COMX_HW_MIXCOM
8017 Hardware driver for the 'MixCOM' board from the MultiGate family.
8018 Say Y if you have a board like this.
8020 If you want to use the watchdog device on this card, you should
8021 select it in the Watchdog Cards section of the Character Devices
8022 configuration. The ISDN interface of this card is Teles 16.3
8023 compatible, you should enable it in the ISDN configuration menu. The
8024 driver for the flash ROM of this card is available separately on
8027 If you want to compile this as a module, say M and read
8028 Documentation/modules.txt. The module will be called
8033 Hardware driver for the TCO timer built into the Intel i810 and i815
8034 chipset family. The TCO (Total Cost of Ownership) timer is a watchdog
8035 timer that will reboot the machine after it's second expiration. The
8036 expiration time can be configured by commandline argument
8037 "i810_margin=<n>" where <n> is the counter initial value. It is
8038 decremented every 0.6 secs, the default is 50 which gives a timeout
8039 of 30 seconds and one minute until reset.
8041 On some motherboards the driver may fail to reset the chipset's
8042 NO_REBOOT flag which prevents the watchdog from rebooting the machine.
8043 If this is the case you will get a kernel message like
8044 "i810tco init: failed to reset NO_REBOOT flag".
8046 If you want to compile this as a module, say M and read
8047 Documentation/modules.txt. The module will be called
8050 MultiGate Cisco-HDLC and synchronous PPP protocol support
8051 CONFIG_COMX_PROTO_PPP
8052 Cisco-HDLC and synchronous PPP protocol driver for all MultiGate
8053 boards. Say Y if you want to use either protocol on your MultiGate
8056 If you want to compile this as a module, say M and read
8057 Documentation/modules.txt. The module will be called
8060 MultiGate LAPB protocol support
8061 CONFIG_COMX_PROTO_LAPB
8062 LAPB protocol driver for all MultiGate boards. Say Y if you
8063 want to use this protocol on your MultiGate boards.
8065 If you want to compile this as a module, say M and read
8066 Documentation/modules.txt. The module will be called
8069 MultiGate Frame Relay protocol support
8070 CONFIG_COMX_PROTO_FR
8071 Frame Relay protocol driver for all MultiGate boards. Say Y if you
8072 want to use this protocol on your MultiGate boards.
8074 If you want to compile this as a module, say M and read
8075 Documentation/modules.txt. The module will be called
8078 Cyclom 2X(tm) multiprotocol cards (EXPERIMENTAL)
8079 CONFIG_CYCLADES_SYNC
8080 Cyclom 2X from Cyclades Corporation (http://www.cyclades.com and
8081 http://www.cyclades.com.br) is an intelligent multiprotocol WAN
8082 adapter with data transfer rates up to 512 Kbps. These cards support
8083 the X.25 and SNA related protocols. If you have one or more of these
8084 cards, say Y to this option. The next questions will ask you about
8085 the protocols you want the driver to support (for now only X.25 is
8088 While no documentation is available at this time please grab the
8089 wanconfig tarball in http://www.conectiva.com.br/~acme/cycsyn-devel
8090 (with minor changes to make it compile with the current wanrouter
8091 include files; efforts are being made to use the original package
8092 available at ftp://ftp.sangoma.com ).
8094 Feel free to contact me or the cycsyn-devel mailing list at
8095 acme@conectiva.com.br and cycsyn-devel@bazar.conectiva.com.br for
8096 additional details, I hope to have documentation available as soon
8097 as possible. (Cyclades Brazil is writing the Documentation).
8099 The driver will be compiled as a module ( = code which can be
8100 inserted in and removed from the running kernel whenever you want).
8101 The module will be called cyclomx.o. For general information about
8102 modules read Documentation/modules.txt.
8104 Cyclom 2X X.25 support
8106 Say Y to this option if you are planning to connect a Cyclom 2X card
8109 If you say N, the X.25 support will not be included in the driver
8110 (saves about 11 KB of kernel memory).
8112 Ethernet (10 or 100Mbit)
8114 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
8115 type of Local Area Network (LAN) in universities and companies.
8117 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
8118 coaxial cable, linking computers in a chain), 10BASE-T or twisted
8119 pair (10 Mbps over twisted pair cable, linking computers to central
8120 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
8121 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
8122 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
8123 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
8124 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
8125 Ethernet (1 Gbps over optical fiber or short copper links).
8127 If your Linux machine will be connected to an Ethernet and you have
8128 an Ethernet network interface card (NIC) installed in your computer,
8129 say Y here and read the Ethernet-HOWTO, available from
8130 http://www.linuxdoc.org/docs.html#howto . You will then also have
8131 to say Y to the driver for your particular NIC.
8133 Note that the answer to this question won't directly affect the
8134 kernel: saying N will just cause this configure script to skip all
8135 the questions about Ethernet network cards. If unsure, say N.
8137 Western Digital/SMC cards
8138 CONFIG_NET_VENDOR_SMC
8139 If you have a network (Ethernet) card belonging to this class, say Y
8140 and read the Ethernet-HOWTO, available from
8141 http://www.linuxdoc.org/docs.html#howto .
8143 Note that the answer to this question doesn't directly affect the
8144 kernel: saying N will just cause this configure script to skip all
8145 the questions about Western Digital cards. If you say Y, you will be
8146 asked for your specific card in the following questions.
8150 If you have a network (Ethernet) card of this type, say Y and read
8151 the Ethernet-HOWTO, available from
8152 http://www.linuxdoc.org/docs.html#howto .
8154 This driver is also available as a module ( = code which can be
8155 inserted in and removed from the running kernel whenever you want).
8156 The module will be called wd.o. If you want to compile it as a
8157 module, say M here and read Documentation/modules.txt as well as
8158 Documentation/networking/net-modules.txt.
8160 SMC Ultra MCA support
8162 If you have a network (Ethernet) card of this type and are running
8163 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
8164 available from http://www.linuxdoc.org/docs.html#howto .
8166 This driver is also available as a module ( = code which can be
8167 inserted in and removed from the running kernel whenever you want).
8168 The module will be called smc-mca.o. If you want to compile it as a
8169 module, say M here and read Documentation/modules.txt as well as
8170 Documentation/networking/net-modules.txt.
8174 If you have a network (Ethernet) card of this type, say Y and read
8175 the Ethernet-HOWTO, available from
8176 http://www.linuxdoc.org/docs.html#howto .
8178 Important: There have been many reports that, with some motherboards
8179 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
8180 such as some BusLogic models) causes corruption problems with many
8181 operating systems. The Linux smc-ultra driver has a work-around for
8182 this but keep it in mind if you have such a SCSI card and have
8185 This driver is also available as a module ( = code which can be
8186 inserted in and removed from the running kernel whenever you want).
8187 The module will be called smc-ultra.o. If you want to compile it as
8188 a module, say M here and read Documentation/modules.txt as well as
8189 Documentation/networking/net-modules.txt.
8191 SMC Ultra32 EISA support
8193 If you have a network (Ethernet) card of this type, say Y and read
8194 the Ethernet-HOWTO, available from
8195 http://www.linuxdoc.org/docs.html#howto .
8197 This driver is also available as a module ( = code which can be
8198 inserted in and removed from the running kernel whenever you want).
8199 The module will be called smc-ultra32.o. If you want to compile it
8200 as a module, say M here and read Documentation/modules.txt as well
8201 as Documentation/networking/net-modules.txt.
8205 This is support for the SMC9xxx based Ethernet cards. Choose this
8206 option if you have a DELL laptop with the docking station, or
8207 another SMC9192/9194 based chipset. Say Y if you want it compiled
8208 into the kernel, and read the file
8209 Documentation/networking/smc9.txt and the Ethernet-HOWTO, available
8210 from http://www.linuxdoc.org/docs.html#howto .
8212 This driver is also available as a module ( = code which can be
8213 inserted in and removed from the running kernel whenever you
8214 want). The module will be called smc9194.o. If you want to compile
8215 it as a module, say M here and read Documentation/modules.txt as
8216 well as Documentation/networking/net-modules.txt.
8220 This driver is for NE2000 compatible PCI cards. It will not work
8221 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
8222 support" below). If you have a PCI NE2000 network (Ethernet) card,
8223 say Y and read the Ethernet-HOWTO, available from
8224 http://www.linuxdoc.org/docs.html#howto .
8226 This driver also works for the following NE2000 clone cards:
8227 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
8228 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
8229 Holtek HT80232 Holtek HT80229
8231 This driver is also available as a module ( = code which can be
8232 inserted in and removed from the running kernel whenever you want).
8233 The module will be called ne2k-pci.o. If you want to compile it as a
8234 module, say M here and read Documentation/modules.txt as well as
8235 Documentation/networking/net-modules.txt.
8237 Racal-Interlan (Micom) NI cards
8238 CONFIG_NET_VENDOR_RACAL
8239 If you have a network (Ethernet) card belonging to this class, such
8240 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
8241 available from http://www.linuxdoc.org/docs.html#howto .
8243 Note that the answer to this question doesn't directly affect the
8244 kernel: saying N will just cause this configure script to skip all
8245 the questions about NI cards. If you say Y, you will be asked for
8246 your specific card in the following questions.
8248 NI5010 support (EXPERIMENTAL)
8250 If you have a network (Ethernet) card of this type, say Y and read
8251 the Ethernet-HOWTO, available from
8252 http://www.linuxdoc.org/docs.html#howto . Note that this is still
8255 This driver is also available as a module ( = code which can be
8256 inserted in and removed from the running kernel whenever you want).
8257 The module will be called ni5010.o. If you want to compile it as a
8258 module, say M here and read Documentation/modules.txt as well as
8259 Documentation/networking/net-modules.txt.
8263 If you have a network (Ethernet) card of this type, say Y and read
8264 the Ethernet-HOWTO, available from
8265 http://www.linuxdoc.org/docs.html#howto .
8267 This driver is also available as a module ( = code which can be
8268 inserted in and removed from the running kernel whenever you want).
8269 The module will be called ni52.o. If you want to compile it as a
8270 module, say M here and read Documentation/modules.txt as well as
8271 Documentation/networking/net-modules.txt.
8275 If you have a network (Ethernet) card of this type, say Y and read
8276 the Ethernet-HOWTO, available from
8277 http://www.linuxdoc.org/docs.html#howto .
8279 This driver is also available as a module ( = code which can be
8280 inserted in and removed from the running kernel whenever you want).
8281 The module will be called ni65.o. If you want to compile it as a
8282 module, say M here and read Documentation/modules.txt as well as
8283 Documentation/networking/net-modules.txt.
8285 RealTek 8129 (not 8019/8029/8139!) support (EXPERIMENTAL)
8287 This is NOT for RTL-8139 cards. Instead, select the 8139too driver
8289 This is a driver for the Fast Ethernet PCI network cards based on
8290 the RTL8129 chip. If you have one of those, say Y and
8291 read the Ethernet-HOWTO, available from
8292 http://www.linuxdoc.org/docs.html#howto .
8294 Note: the 8029 is a NE2000 PCI clone, you can use the NE2K-PCI driver.
8296 If you want to compile this driver as a module ( = code which can be
8297 inserted in and removed from the running kernel whenever you want),
8298 say M here and read Documentation/modules.txt. This is recommended.
8299 The module will be called rtl8129.o.
8301 RealTek RTL-8139 PCI Fast Ethernet Adapter support
8303 This is a driver for the Fast Ethernet PCI network cards based on
8304 the RTL8139 chips. If you have one of those, say Y and read
8305 Documentation/networking/8139too.txt as well as the Ethernet-HOWTO,
8306 available from http://www.linuxdoc.org/docs.html#howto .
8308 If you want to compile this driver as a module ( = code which can be
8309 inserted in and removed from the running kernel whenever you want),
8310 say M here and read Documentation/modules.txt. This is recommended.
8311 The module will be called 8139too.o.
8313 SiS 900 PCI Fast Ethernet Adapter support
8315 This is a driver for the Fast Ethernet PCI network cards based on
8316 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
8317 SiS 630 and SiS 540 chipsets. If you have one of those, say Y and
8318 read the Ethernet-HOWTO, available at
8319 http://www.linuxdoc.org/docs.html#howto . Please read
8320 Documentation/networking/sis900.txt and comments at the beginning of
8321 drivers/net/sis900.c for more information.
8323 This driver also supports AMD 79C901 HomePNA so that you can use
8324 your phone line as a network cable.
8326 If you want to compile this driver as a module ( = code which can be
8327 inserted in and removed from the running kernel whenever you want),
8328 say M here and read Documentation/modules.txt. This is recommended.
8329 The module will be called sis900.o.
8331 Packet Engines Yellowfin Gigabit-NIC support
8333 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
8334 adapter. This adapter is used by the Beowulf Linux cluster project.
8335 See http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html for
8336 more information about this driver in particular and Beowulf in
8339 If you want to compile this driver as a module ( = code which can be
8340 inserted in and removed from the running kernel whenever you want),
8341 say M here and read Documentation/modules.txt. This is recommended.
8342 The module will be called yellowfin.o.
8344 General Instruments Surfboard 1000
8346 This is a driver for the General Instrument (also known as
8347 NextLevel) SURFboard 1000 internal
8348 cable modem. This is an ISA card which is used by a number of cable
8349 TV companies to provide cable modem access. It's a one-way
8350 downstream-only cable modem, meaning that your upstream net link is
8351 provided by your regular phone modem.
8353 At present this driver only compiles as a module, so say M here if
8354 you have this card. The module will be called sb1000.o. Then read
8355 Documentation/networking/README.sb1000 for information on how to use
8356 this module, as it needs special ppp scripts for establishing a
8357 connection. Further documentation and the necessary scripts can be
8360 http://www.jacksonville.net/~fventuri/
8361 http://home.adelphia.net/~siglercm/sb1000.html
8362 http://linuxpower.cx/~cable/
8364 If you don't have this card, of course say N.
8366 Adaptec Starfire support (EXPERIMENTAL)
8367 CONFIG_ADAPTEC_STARFIRE
8368 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
8369 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
8370 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
8373 If you want to compile this driver as a module ( = code which can be
8374 inserted in and removed from the running kernel whenever you want),
8375 say M here and read Documentation/modules.txt. This is recommended.
8376 The module will be called starfile.o.
8378 Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support
8380 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
8381 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
8382 adapter. The driver allows for using the Jumbo Frame option (9000
8383 bytes/frame) however it requires that your switches can handle this
8384 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
8387 If you want to compile this driver as a module ( = code which can be
8388 inserted in and removed from the running kernel whenever you want),
8389 say M here and read Documentation/modules.txt. This is recommended.
8390 The module will be called acenic.o.
8392 Omit support for older Tigon I based AceNICs
8393 CONFIG_ACENIC_OMIT_TIGON_I
8394 Say Y here if you only have Tigon II based AceNICs and want to leave
8395 out support for the older Tigon I based cards which are no longer
8396 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
8397 version)). This will reduce the size of the driver object by
8398 app. 100KB. If you are not sure whether your card is a Tigon I or a
8399 Tigon II, say N here.
8401 The safe and default value for this is N.
8403 SysKonnect SK-98xx support
8405 Say Y here if you have a SysKonnect SK-98xx Gigabit Ethernet Server
8406 Adapter. The following adapters are supported by this driver:
8407 - SK-9841 (single link 1000Base-LX)
8408 - SK-9842 (dual link 1000Base-LX)
8409 - SK-9843 (single link 1000Base-SX)
8410 - SK-9844 (dual link 1000Base-SX)
8411 - SK-9821 (single link 1000Base-T)
8412 - SK-9822 (dual link 1000Base-T)
8413 - SK-9861 (single link Volition connector)
8414 - SK-9862 (dual link Volition connector)
8415 The driver also supports the following adapters from Allied Telesyn:
8418 The dual link adapters support a link-failover feature.
8419 Read Documentation/networking/sk98lin.txt for information about
8420 optional driver parameters.
8421 Questions concerning this driver may be addressed to:
8424 If you want to compile this driver as a module ( = code which can be
8425 inserted in and removed from the running kernel whenever you want),
8426 say M here and read Documentation/modules.txt. This is recommended.
8427 The module will be called sk98lin.o.
8429 MyriCOM Gigabit Ethernet support
8431 This driver supports MyriCOM Sbus gigabit ethernet cards.
8433 If you want to compile this driver as a module ( = code which can be
8434 inserted in and removed from the running kernel whenever you want),
8435 say M here and read Documentation/modules.txt. This is recommended.
8436 The module will be called myri_sbus.o.
8438 AMD LANCE and PCnet (AT1500 and NE2100) support
8440 If you have a network (Ethernet) card of this type, say Y and read
8441 the Ethernet-HOWTO, available from
8442 http://www.linuxdoc.org/docs.html#howto . Some LinkSys cards are
8445 If you want to compile this driver as a module ( = code which can be
8446 inserted in and removed from the running kernel whenever you want),
8447 say M here and read Documentation/modules.txt. This is recommended.
8448 The module will be called lance.o.
8452 If you have a network (Ethernet) card of this type, say Y and read
8453 the Ethernet-HOWTO, available from
8454 http://www.linuxdoc.org/docs.html#howto .
8457 CONFIG_NET_VENDOR_3COM
8458 If you have a network (Ethernet) card belonging to this class, say Y
8459 and read the Ethernet-HOWTO, available from
8460 http://www.linuxdoc.org/docs.html#howto .
8462 Note that the answer to this question doesn't directly affect the
8463 kernel: saying N will just cause this configure script to skip all
8464 the questions about 3COM cards. If you say Y, you will be asked for
8465 your specific card in the following questions.
8469 If you have a network (Ethernet) card of this type, say Y and read
8470 the Ethernet-HOWTO, available from
8471 http://www.linuxdoc.org/docs.html#howto . Also, consider buying a
8472 new card, since the 3c501 is slow, broken, and obsolete: you will
8473 have problems. Some people suggest to ping ("man ping") a nearby
8474 machine every minute ("man cron") when using this card.
8476 This driver is also available as a module ( = code which can be
8477 inserted in and removed from the running kernel whenever you want).
8478 The module will be called 3c501.o. If you want to compile it as a
8479 module, say M here and read Documentation/modules.txt as well as
8480 Documentation/networking/net-modules.txt.
8484 If you have a network (Ethernet) card of this type, say Y and read
8485 the Ethernet-HOWTO, available from
8486 http://www.linuxdoc.org/docs.html#howto .
8488 This driver is also available as a module ( = code which can be
8489 inserted in and removed from the running kernel whenever you want).
8490 The module will be called 3c503.o. If you want to compile it as a
8491 module, say M here and read Documentation/modules.txt as well as
8492 Documentation/networking/net-modules.txt.
8496 Information about this network (Ethernet) card can be found in
8497 Documentation/networking/3c505.txt. If you have a card of this type,
8498 say Y and read the Ethernet-HOWTO, available from
8499 http://www.linuxdoc.org/docs.html#howto .
8501 If you want to compile this as a module ( = code which can be
8502 inserted in and removed from the running kernel whenever you want),
8503 say M here and read Documentation/modules.txt as well as
8504 Documentation/networking/net-modules.txt. The module will be called
8507 3c507 support (EXPERIMENTAL)
8509 If you have a network (Ethernet) card of this type, say Y and read
8510 the Ethernet-HOWTO, available from
8511 http://www.linuxdoc.org/docs.html#howto .
8513 This driver is also available as a module ( = code which can be
8514 inserted in and removed from the running kernel whenever you want).
8515 The module will be called 3c507.o. If you want to compile it as a
8516 module, say M here and read Documentation/modules.txt as well as
8517 Documentation/networking/net-modules.txt.
8521 If you have a network (Ethernet) card of this type, say Y and read
8522 the Ethernet-HOWTO, available from
8523 http://www.linuxdoc.org/docs.html#howto .
8525 This driver is also available as a module ( = code which can be
8526 inserted in and removed from the running kernel whenever you want).
8527 The module will be called 3c523.o. If you want to compile it as a
8528 module, say M here and read Documentation/modules.txt as well as
8529 Documentation/networking/net-modules.txt.
8533 If you have a network (Ethernet) card of this type, say Y and read
8534 the Ethernet-HOWTO, available from
8535 http://www.linuxdoc.org/docs.html#howto .
8537 This driver is also available as a module ( = code which can be
8538 inserted in and removed from the running kernel whenever you want).
8539 The module will be called 3c527.o. If you want to compile it as a
8540 module, say M here and read Documentation/modules.txt as well as
8541 Documentation/networking/net-modules.txt.
8545 If you have a network (Ethernet) card belonging to the 3Com
8546 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
8547 from http://www.linuxdoc.org/docs.html#howto .
8549 If your card is not working you may need to use the DOS
8550 setup disk to disable Plug & Play mode, and to select the default
8553 If you want to compile this as a module ( = code which can be
8554 inserted in and removed from the running kernel whenever you want),
8555 say M here and read Documentation/modules.txt as well as
8556 Documentation/networking/net-modules.txt. The module will be called
8559 3c515 ISA Fast EtherLink
8561 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
8562 network card, say Y and read the Ethernet-HOWTO, available from
8563 http://www.linuxdoc.org/docs.html#howto .
8565 If you want to compile this as a module ( = code which can be
8566 inserted in and removed from the running kernel whenever you want),
8567 say M here and read Documentation/modules.txt as well as
8568 Documentation/networking/net-modules.txt. The module will be called
8571 3c59x/3c90x/3c575_Cardbus series "Vortex/Boomerang/Cyclone" support
8573 This option enables driver support for a large number of 10mbps and
8574 10/100mbps EISA, PCI and PCMCIA 3Com network cards:
8576 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
8577 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
8578 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
8579 "Tornado" (3c905) PCI
8580 "Hurricane" (3c555/3cSOHO) PCI
8582 If you have such a card, say Y and read the Ethernet-HOWTO, available
8583 from http://www.linuxdoc.org/docs.html#howto . More specific
8584 information is in Documentation/networking/vortex.txt and in the
8585 comments at the beginning of drivers/net/3c59x.c.
8587 If you want to compile this as a module ( = code which can be
8588 inserted in and removed from the running kernel whenever you want),
8589 say M here and read Documentation/modules.txt as well as
8590 Documentation/networking/net-modules.txt.
8594 If your network (Ethernet) card hasn't been mentioned yet and its
8595 bus system (that's the way the cards talks to the other components
8596 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
8597 Make sure you know the name of your card. Read the Ethernet-HOWTO,
8598 available from http://www.linuxdoc.org/docs.html#howto .
8602 Note that the answer to this question doesn't directly affect the
8603 kernel: saying N will just cause this configure script to skip all
8604 the remaining ISA network card questions. If you say Y, you will be
8605 asked for your specific card in the following questions.
8607 Generic ARCnet support
8609 If you have a network card of this type, say Y and check out the
8610 (arguably) beautiful poetry in Documentation/networking/arcnet.txt.
8612 You need both this driver, and the driver for the particular ARCnet
8613 chipset of your card. If you don't know, then it's probably a
8614 COM90xx type card, so say Y (or M) to "ARCnet COM90xx chipset
8617 You might also want to have a look at the Ethernet-HOWTO, available
8618 from http://www.linuxdoc.org/docs.html#howto (even though ARCnet
8619 is not really Ethernet).
8621 This driver is also available as a module ( = code which can be
8622 inserted in and removed from the running kernel whenever you want).
8623 The module will be called arcnet.o. If you want to compile it as a
8624 module, say M here and read Documentation/modules.txt as well as
8625 Documentation/networking/net-modules.txt.
8627 Enable arc0e (ARCnet "ether-encap" packet format)
8629 This allows you to use "Ethernet encapsulation" with your ARCnet
8630 card via the virtual arc0e device. You only need arc0e if you want
8631 to talk to nonstandard ARCnet software, specifically,
8632 DOS/Windows-style "NDIS" drivers. You do not need to say Y here to
8633 communicate with industry-standard RFC1201 implementations, like the
8634 arcether.com packet driver or most DOS/Windows ODI drivers. RFC1201
8635 is included automatically as the arc0 device. Please read the
8636 ARCnet documentation in Documentation/networking/arcnet.txt for more
8637 information about using arc0e and arc0s.
8639 Enable old ARCNet packet format (RFC 1051)
8641 This allows you to use RFC1051 with your ARCnet card via the virtual
8642 arc0s device. You only need arc0s if you want to talk to ARCnet
8643 software complying with the "old" standard, specifically, the DOS
8644 arcnet.com packet driver, Amigas running AmiTCP, and some variants
8645 of NetBSD. You do not need to say Y here to communicate with
8646 industry-standard RFC1201 implementations, like the arcether.com
8647 packet driver or most DOS/Windows ODI drivers. RFC1201 is included
8648 automatically as the arc0 device. Please read the ARCnet
8649 documentation in Documentation/networking/arcnet.txt for more
8650 information about using arc0e and arc0s.
8652 ARCnet COM90xx (normal) chipset driver
8653 CONFIG_ARCNET_COM90xx
8654 This is the chipset driver for the standard COM90xx cards. If you
8655 have always used the old ARCnet driver without knowing what type of
8656 card you had, this is probably the one for you.
8658 This driver is also available as a module ( = code which can be
8659 inserted in and removed from the running kernel whenever you want).
8660 The module will be called com90xx.o. If you want to compile it as a
8661 module, say M here and read Documentation/modules.txt as well as
8662 Documentation/networking/net-modules.txt.
8664 ARCnet COM90xx (IO mapped) chipset driver
8665 CONFIG_ARCNET_COM90xxIO
8666 This is the chipset driver for the COM90xx cards, using them in
8667 IO-mapped mode instead of memory-mapped mode. This is slower than
8668 the normal driver. Only use it if your card doesn't support shared
8671 This driver is also available as a module ( = code which can be
8672 inserted in and removed from the running kernel whenever you want).
8673 The module will be called com90io.o. If you want to compile it as a
8674 module, say M here and read Documentation/modules.txt as well as
8675 Documentation/networking/net-modules.txt.
8677 ARCnet COM90xx (RIM I) chipset driver
8679 This is yet another chipset driver for the COM90xx cards, but this
8680 time only using memory-mapped mode, and no IO ports at all. This
8681 driver is completely untested, so if you have one of these cards,
8682 please mail dwmw2@infradead.org, especially if it works!
8684 This driver is also available as a module ( = code which can be
8685 inserted in and removed from the running kernel whenever you
8686 want). The module will be called arc-rimi.o. If you want to compile
8687 it as a module, say M here and read Documentation/modules.txt as
8688 well as Documentation/networking/net-modules.txt.
8690 ARCnet COM20020 chipset driver
8691 CONFIG_ARCNET_COM20020
8692 This is the driver for the new COM20020 chipset. It supports such
8693 things as promiscuous mode, so packet sniffing is possible, and
8694 extra diagnostic information.
8696 This driver is also available as a module ( = code which can be
8697 inserted in and removed from the running kernel whenever you want).
8698 The module will be called com20020.o. If you want to compile it as a
8699 module, say M here and read Documentation/modules.txt as well as
8700 Documentation/networking/net-modules.txt.
8702 Cabletron E21xx support
8704 If you have a network (Ethernet) card of this type, say Y and read
8705 the Ethernet-HOWTO, available from
8706 http://www.linuxdoc.org/docs.html#howto .
8708 This driver is also available as a module ( = code which can be
8709 inserted in and removed from the running kernel whenever you want).
8710 The module will be called e2100.o. If you want to compile it as a
8711 module, say M here and read Documentation/modules.txt as well as
8712 Documentation/networking/net-modules.txt.
8716 Support for CS89x0 chipset based Ethernet cards. If you have a
8717 network (Ethernet) card of this type, say Y and read the
8718 Ethernet-HOWTO, available from
8719 http://www.linuxdoc.org/docs.html#howto as well as
8720 Documentation/networking/cs89x0.txt.
8722 If you want to compile this as a module ( = code which can be
8723 inserted in and removed from the running kernel whenever you want),
8724 say M here and read Documentation/modules.txt as well as
8725 Documentation/networking/net-modules.txt. The module will be called
8730 If you have a network (Ethernet) card of this type, say Y and read
8731 the Ethernet-HOWTO, available from
8732 http://www.linuxdoc.org/docs.html#howto as well as
8733 drivers/net/depca.c.
8735 If you want to compile this as a module ( = code which can be
8736 inserted in and removed from the running kernel whenever you want),
8737 say M here and read Documentation/modules.txt as well as
8738 Documentation/networking/net-modules.txt. The module will be called
8741 EtherWorks 3 support
8743 This driver supports the DE203, DE204 and DE205 network (Ethernet)
8744 cards. If this is for you, say Y and read
8745 Documentation/networking/ewrk3.txt in the kernel source as well as
8746 the Ethernet-HOWTO, available from
8747 http://www.linuxdoc.org/docs.html#howto .
8749 If you want to compile this as a module ( = code which can be
8750 inserted in and removed from the running kernel whenever you want),
8751 say M here and read Documentation/modules.txt as well as
8752 Documentation/networking/net-modules.txt. The module will be called
8757 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
8758 is for you, read the Ethernet-HOWTO, available from
8759 http://www.linuxdoc.org/docs.html#howto .
8761 If you want to compile this as a module ( = code which can be
8762 inserted in and removed from the running kernel whenever you want),
8763 say M here and read Documentation/modules.txt as well as
8764 Documentation/networking/net-modules.txt. The module will be called
8769 If you have a network (Ethernet) card of this type, say Y and read
8770 the Ethernet-HOWTO, available from
8771 http://www.linuxdoc.org/docs.html#howto .
8773 This driver is also available as a module ( = code which can be
8774 inserted in and removed from the running kernel whenever you want).
8775 If you want to compile it as a module, say M here and read
8776 Documentation/modules.txt as well as
8777 Documentation/networking/net-modules.txt. The module will be called
8780 FMV-181/182/183/184 support
8782 If you have a Fujitsu FMV-181/182/183/184 network (Ethernet) card,
8783 say Y and read the Ethernet-HOWTO, available from
8784 http://www.linuxdoc.org/docs.html#howto .
8786 If you use an FMV-183 or FMV-184 and it is not working, you may need
8787 to disable Plug & Play mode of the card.
8789 This driver is also available as a module ( = code which can be
8790 inserted in and removed from the running kernel whenever you want).
8791 The module will be called fmv18x.o. If you want to compile it as a
8792 module, say M here and read Documentation/modules.txt as well as
8793 Documentation/networking/net-modules.txt.
8795 EtherExpress PRO support
8797 If you have a network (Ethernet) card of this type, say Y. This
8798 driver supports intel i82595{FX,TX} based boards. Note however
8799 that the EtherExpress PRO/100 Ethernet card has its own separate
8800 driver. Please read the Ethernet-HOWTO, available from
8801 http://www.linuxdoc.org/docs.html#howto .
8803 This driver is also available as a module ( = code which can be
8804 inserted in and removed from the running kernel whenever you want).
8805 The module will be called eepro.o. If you want to compile it as a
8806 module, say M here and read Documentation/modules.txt as well as
8807 Documentation/networking/net-modules.txt.
8809 EtherExpress support
8811 If you have an EtherExpress16 network (Ethernet) card, say Y and
8812 read the Ethernet-HOWTO, available from
8813 http://www.linuxdoc.org/docs.html#howto . Note that the Intel
8814 EtherExpress16 card used to be regarded as a very poor choice
8815 because the driver was very unreliable. We now have a new driver
8816 that should do better.
8818 If you want to compile this driver as a module ( = code which can be
8819 inserted in and removed from the running kernel whenever you want),
8820 say M here and read Documentation/modules.txt as well as
8821 Documentation/networking/net-modules.txt. The module will be called
8824 Packet Engines Hamachi GNIC-II support
8826 If you have a Gigabit Ethernet card of this type, say Y and read
8827 the Ethernet-HOWTO, available from
8828 http://www.linuxdoc.org/docs.html#howto .
8830 If you want to compile this as a module ( = code which can be
8831 inserted in and removed from the running kernel whenever you want),
8832 say M here and read Documentation/modules.txt as well as
8833 Documentation/networking/net-modules.txt. The module will be called
8836 HP PCLAN+ (27247B and 27252A) support
8838 If you have a network (Ethernet) card of this type, say Y and read
8839 the Ethernet-HOWTO, available from
8840 http://www.linuxdoc.org/docs.html#howto .
8842 This driver is also available as a module ( = code which can be
8843 inserted in and removed from the running kernel whenever you want).
8844 The module will be called hp-plus.o. If you want to compile it as a
8845 module, say M here and read Documentation/modules.txt as well as
8846 Documentation/networking/net-modules.txt.
8848 HP PCLAN (27245 and other 27xxx series) support
8850 If you have a network (Ethernet) card of this type, say Y and read
8851 the Ethernet-HOWTO, available from
8852 http://www.linuxdoc.org/docs.html#howto .
8854 This driver is also available as a module ( = code which can be
8855 inserted in and removed from the running kernel whenever you want).
8856 The module will be called hp.o. If you want to compile it as a
8857 module, say M here and read Documentation/modules.txt as well as
8858 Documentation/networking/net-modules.txt.
8860 HP 10/100VG PCLAN (ISA, EISA, PCI) support
8862 If you have a network (Ethernet) card of this type, say Y and read
8863 the Ethernet-HOWTO, available from
8864 http://www.linuxdoc.org/docs.html#howto .
8866 If you want to compile this as a module ( = code which can be
8867 inserted in and removed from the running kernel whenever you want),
8868 say M here and read Documentation/modules.txt as well as
8869 Documentation/networking/net-modules.txt. The module will be called
8872 NE2000/NE1000 support
8874 If you have a network (Ethernet) card of this type, say Y and read
8875 the Ethernet-HOWTO, available from
8876 http://www.linuxdoc.org/docs.html#howto . Many Ethernet cards
8877 without a specific driver are compatible with NE2000.
8879 If you have a PCI NE2000 card however, say N here and Y to "PCI
8880 NE2000 support", above. If you have a NE2000 card and are running on
8881 an MCA system (a bus system used on some IBM PS/2 computers and
8882 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
8885 This driver is also available as a module ( = code which can be
8886 inserted in and removed from the running kernel whenever you want).
8887 The module will be called ne.o. If you want to compile it as a
8888 module, say M here and read Documentation/modules.txt as well as
8889 Documentation/networking/net-modules.txt.
8891 National Semiconductor DP83810 series PCI Ethernet support
8893 This driver is for the National Semiconductor DP83810 series,
8894 including the 83815 chip.
8895 More specific information and updates are available from
8896 http://www.scyld.com/network/natsemi.html
8900 If you have a network (Ethernet) card of this type, say Y and read
8901 the Ethernet-HOWTO, available from
8902 http://www.linuxdoc.org/docs.html#howto .
8904 NE/2 (ne2000 MCA version) support
8906 If you have a network (Ethernet) card of this type, say Y and read
8907 the Ethernet-HOWTO, available from
8908 http://www.linuxdoc.org/docs.html#howto .
8910 This driver is also available as a module ( = code which can be
8911 inserted in and removed from the running kernel whenever you want).
8912 The module will be called ne2.o. If you want to compile it as a
8913 module, say M here and read Documentation/modules.txt as well as
8914 Documentation/networking/net-modules.txt.
8918 These are Micro Channel ethernet adapters. You need to say Y to "MCA
8919 support" in order to use this driver. Supported cards are the SKnet
8920 Junior MC2 and the SKnet MC2(+). The driver automatically
8921 distinguishes between the two cards. Note that using multiple boards
8922 of different type hasn't been tested with this driver. Say Y if you
8923 have one of these ethernet adapters.
8925 This driver is also available as a module ( = code which can be
8926 inserted in and removed from the running kernel whenever you want).
8927 The module is called sk_mca.o. If you want to compile it as a
8928 module, say M here and read Documentation/modules.txt as well as
8929 Documentation/networking/net-modules.txt.
8931 IBM LAN Adapter/A support
8933 This is a Micro Channel ethernet adapter. You need to set CONFIG_MCA
8934 to use this driver. It is both available as an in-kernel driver and
8935 as a module ( = code which can be inserted in and removed from the
8936 running kernel whenever you want). If you want to compile it as a module,
8937 say M here and read Documentation/modules.txt as well as
8938 Documentation/networking/net-modules.txt. If you plan to use more than
8939 one network card under linux, read the Multiple-Ethernet-mini-HOWTO,
8940 available from sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. The only
8941 currently supported card is the IBM LAN Adapter/A for Ethernet. It will
8942 both support 16K and 32K memory windows, however a 32K window gives
8943 a better security against packet losses. Usage of multiple boards with
8944 this driver should be possible, but has not been tested up to now due
8945 to lack of hardware.
8947 EISA, VLB, PCI and on board controllers
8949 This is another class of network cards which attach directly to the
8950 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
8951 available from http://www.linuxdoc.org/docs.html#howto .
8953 Note that the answer to this question doesn't directly affect the
8954 kernel: saying N will just cause this configure script to skip all
8955 the questions about this class of network cards. If you say Y, you
8956 will be asked for your specific card in the following questions. If
8957 you are unsure, say Y.
8959 AMD PCnet32 (VLB and PCI) support
8961 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
8962 answer Y here and read the Ethernet-HOWTO, available from
8963 http://www.linuxdoc.org/docs.html#howto .
8965 This driver is also available as a module ( = code which can be
8966 inserted in and removed from the running kernel whenever you want).
8967 The module will be called pcnet32.o. If you want to compile it as a
8968 module, say M here and read Documentation/modules.txt as well as
8969 Documentation/networking/net-modules.txt.
8971 Ansel Communications EISA 3200 support
8973 If you have a network (Ethernet) card of this type, say Y and read
8974 the Ethernet-HOWTO, available from
8975 http://www.linuxdoc.org/docs.html#howto .
8977 This driver is also available as a module ( = code which can be
8978 inserted in and removed from the running kernel whenever you want).
8979 The module will be called ac3200.o. If you want to compile it as a
8980 module, say M here and read Documentation/modules.txt as well as
8981 Documentation/networking/net-modules.txt.
8983 Mylex EISA LNE390A/LNE390B support (EXPERIMENTAL)
8985 If you have a network (Ethernet) card of this type, say Y and read
8986 the Ethernet-HOWTO, available from
8987 http://www.linuxdoc.org/docs.html#howto .
8989 This driver is also available as a module ( = code which can be
8990 inserted in and removed from the running kernel whenever you want).
8991 The module will be called lne390.o. If you want to compile it as a
8992 module, say M here and read Documentation/modules.txt as well as
8993 Documentation/networking/net-modules.txt.
8995 Novell/Eagle/Microdyne NE3210 EISA support
8997 If you have a network (Ethernet) card of this type, say Y and read
8998 the Ethernet-HOWTO, available from
8999 http://www.linuxdoc.org/docs.html#howto . Note that this driver
9000 will NOT WORK for NE3200 cards as they are completely different.
9002 This driver is also available as a module ( = code which can be
9003 inserted in and removed from the running kernel whenever you want).
9004 The module will be called ne3210.o. If you want to compile it as a
9005 module, say M here and read Documentation/modules.txt as well as
9006 Documentation/networking/net-modules.txt.
9008 Apricot Xen-II on board Ethernet
9010 If you have a network (Ethernet) controller of this type, say Y and
9011 read the Ethernet-HOWTO, available from
9012 http://www.linuxdoc.org/docs.html#howto .
9014 If you want to compile this as a module ( = code which can be
9015 inserted in and removed from the running kernel whenever you want),
9016 say M here and read Documentation/modules.txt as well as
9017 Documentation/networking/net-modules.txt. The module will be called
9020 Generic DECchip & DIGITAL EtherWORKS PCI/EISA
9022 This is support for the DIGITAL series of PCI/EISA Ethernet cards.
9023 These include the DE425, DE434, DE435, DE450 and DE500 models. If
9024 you have a network card of this type, say Y and read the
9025 Ethernet-HOWTO, available from
9026 http://www.linuxdoc.org/docs.html#howto . More specific
9027 information is contained in Documentation/networking/de4x5.txt.
9029 This driver is also available as a module ( = code which can be
9030 inserted in and removed from the running kernel whenever you want).
9031 The module will be called de4x5.o. If you want to compile it as a
9032 module, say M here and read Documentation/modules.txt as well as
9033 Documentation/networking/net-modules.txt.
9035 DECchip Tulip (dc21x4x) PCI support
9037 This driver is developed for the SMC EtherPower series Ethernet
9038 cards and also works with cards based on the DECchip
9039 21040/21041/21140 (Tulip series) chips. Some LinkSys PCI cards are
9040 of this type. (If your card is NOT SMC EtherPower 10/100 PCI
9041 (smc9332dst), you can also try the driver for "Generic DECchip"
9042 cards, above. However, most people with a network card of this type
9043 will say Y here.) Do read the Ethernet-HOWTO, available from
9044 http://www.linuxdoc.org/docs.html#howto . More specific
9045 information is contained in Documentation/networking/tulip.txt.
9047 This driver is also available as a module ( = code which can be
9048 inserted in and removed from the running kernel whenever you want).
9049 The module will be called tulip.o. If you want to compile it as a
9050 module, say M here and read Documentation/modules.txt as well as
9051 Documentation/networking/net-modules.txt.
9053 Digi Intl. RightSwitch support
9055 This is support for the Digi International RightSwitch series of
9056 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
9057 models. If you have a network card of this type, say Y and read the
9058 Ethernet-HOWTO, available from
9059 http://www.linuxdoc.org/docs.html#howto . More specific
9060 information is contained in Documentation/networking/dgrs.txt.
9062 This driver is also available as a module ( = code which can be
9063 inserted in and removed from the running kernel whenever you want).
9064 The module will be called dgrs.o. If you want to compile it as a
9065 module, say M here and read Documentation/modules.txt as well as
9066 Documentation/networking/net-modules.txt.
9068 EtherExpress PRO/100 support
9070 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
9071 card, say Y and read the Ethernet-HOWTO, available from
9072 http://www.linuxdoc.org/docs.html#howto .
9074 This driver is also available as a module ( = code which can be
9075 inserted in and removed from the running kernel whenever you want).
9076 The module will be called eepro100.o. If you want to compile it as a
9077 module, say M here and read Documentation/modules.txt as well as
9078 Documentation/networking/net-modules.txt.
9080 Enable Power Management (EXPERIMENTAL)
9082 Many Intel EtherExpress PRO/100 PCI network cards are capable
9083 of providing power management capabilities. To make use of these
9084 capabilities, say Y.
9086 WARNING: This option is intended for kernel developers and testers.
9087 It is still very experimental, with some people reporting complete
9090 It is recommended to say N here.
9092 ICL EtherTeam 16i/32 support (EXPERIMENTAL)
9094 If you have a network (Ethernet) card of this type, say Y and read
9095 the Ethernet-HOWTO, available from
9096 http://www.linuxdoc.org/docs.html#howto .
9098 This driver is also available as a module ( = code which can be
9099 inserted in and removed from the running kernel whenever you want).
9100 The module will be called eth16i.o. If you want to compile it as a
9101 module, say M here and read Documentation/modules.txt as well as
9102 Documentation/networking/net-modules.txt.
9104 TI ThunderLAN support (EXPERIMENTAL)
9106 If you have a PCI Ethernet network card based on the ThunderLAN chip
9107 which is supported by this driver, say Y and read the
9108 Ethernet-HOWTO, available from
9109 http://www.linuxdoc.org/docs.html#howto .
9111 Devices currently supported by this driver are Compaq Netelligent,
9112 Compaq NetFlex and Olicom cards. Please read the file
9113 Documentation/networking/tlan.txt for more details.
9115 This driver is also available as a module ( = code which can be
9116 inserted in and removed from the running kernel whenever you want).
9117 The module will be called tlan.o. If you want to compile it as a
9118 module, say M here and read Documentation/modules.txt as well as
9119 Documentation/networking/net-modules.txt.
9121 Please email feedback to torben.mathiasen@compaq.com.
9125 If you have a VIA "rhine" based network card (Rhine-I (3043) or
9126 Rhine-2 (VT86c100A)), say Y here.
9128 This driver is also available as a module ( = code which can be
9129 inserted in and removed from the running kernel whenever you want).
9130 The module will be called via-rhine.o. If you want to compile it as
9131 a module, say M here and read Documentation/modules.txt as well as
9132 Documentation/networking/net-modules.txt.
9134 PCI DM9102(A)/DM9132/DM9801 support
9136 This driver is for DM9102(A)/DM9132/DM9801 compatible PCI cards from
9137 Davicom ( http://www.davicom.com.tw ). If you have such a network
9138 (Ethernet) card, say Y. Some information is contained in the file
9139 Documentation/networking/dmfe.txt.
9141 This driver is also available as a module ( = code which can be
9142 inserted in and removed from the running kernel whenever you want).
9143 The module will be called dmfe.o. If you want to compile it as a
9144 module, say M here and read Documentation/modules.txt as well as
9145 Documentation/networking/net-modules.txt.
9147 Racal-Interlan EISA ES3210 support (EXPERIMENTAL)
9149 If you have a network (Ethernet) card of this type, say Y and read
9150 the Ethernet-HOWTO, available from
9151 http://www.linuxdoc.org/docs.html#howto .
9153 This driver is also available as a module ( = code which can be
9154 inserted in and removed from the running kernel whenever you want).
9155 The module will be called es3210.o. If you want to compile it as a
9156 module, say M here and read Documentation/modules.txt as well as
9157 Documentation/networking/net-modules.txt.
9161 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
9162 which is based on the SMC83c17x (EPIC/100).
9163 More specific information and updates are available from
9164 http://www.scyld.com/network/epic100.html
9166 SGI Seeq ethernet controller support
9168 Say Y here if you have an Seeq based Ethernet network card. This is
9169 used in many Silicon Graphics machines.
9171 Sundance "Alta" PCI Ethernet support
9173 This driver is for the Sundance "Alta" chip.
9174 More specific information and updates are available from
9175 http://www.scyld.com/network/sundance.html
9177 Winbond W89c840 PCI Ethernet support
9179 This driver is for the Winbond W89c840 chip. It also works with
9180 the TX9882 chip on the Compex RL100-ATX board.
9181 More specific information and updates are available from
9182 http://www.scyld.com/network/drivers.html
9184 Zenith Z-Note support (EXPERIMENTAL)
9186 The Zenith Z-Note notebook computer has a built-in network
9187 (Ethernet) card, and this is the Linux driver for it. Note that the
9188 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
9189 by this driver. Read the Ethernet-HOWTO, available from
9190 http://www.linuxdoc.org/docs.html#howto .
9192 Pocket and portable adapters
9194 Cute little network (Ethernet) devices which attach to the parallel
9195 port ("pocket adapters"), commonly used with laptops. If you have
9196 one of those, say Y and read the Ethernet-HOWTO, available from
9197 http://www.linuxdoc.org/docs.html#howto .
9199 If you want to plug a network (or some other) card into the PCMCIA
9200 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
9201 credit card size extension cards used by all modern laptops), you
9202 need the pcmcia-cs package (location contained in the file
9203 Documentation/Changes) and you can say N here.
9205 Laptop users should read the Linux Laptop home page at
9206 http://www.cs.utexas.edu/users/kharker/linux-laptop/ .
9208 Note that the answer to this question doesn't directly affect the
9209 kernel: saying N will just cause this configure script to skip all
9210 the questions about this class of network devices. If you say Y, you
9211 will be asked for your specific device in the following questions.
9213 AT-LAN-TEC/RealTek pocket adapter support
9215 This is a network (Ethernet) device which attaches to your parallel
9216 port. Read drivers/net/atp.c as well as the Ethernet-HOWTO,
9217 available from http://www.linuxdoc.org/docs.html#howto , if you
9218 want to use this. If you intend to use this driver, you should have
9219 said N to the "Parallel printer support", because the two drivers
9220 don't like each other.
9222 If you want to compile this driver as a module however ( = code
9223 which can be inserted in and removed from the running kernel
9224 whenever you want), say M here and read Documentation/modules.txt.
9225 The module will be called atp.o.
9227 D-Link DE600 pocket adapter support
9229 This is a network (Ethernet) device which attaches to your parallel
9230 port. Read Documentation/networking/DLINK.txt as well as the
9231 Ethernet-HOWTO, available from
9232 http://www.linuxdoc.org/docs.html#howto , if you want to use
9233 this. It is possible to have several devices share a single parallel
9234 port and it is safe to compile the corresponding drivers into the
9237 If you want to compile this driver as a module however ( = code
9238 which can be inserted in and removed from the running kernel
9239 whenever you want), say M here and read Documentation/modules.txt.
9240 The module will be called de600.o.
9242 D-Link DE620 pocket adapter support
9244 This is a network (Ethernet) device which attaches to your parallel
9245 port. Read Documentation/networking/DLINK.txt as well as the
9246 Ethernet-HOWTO, available from
9247 http://www.linuxdoc.org/docs.html#howto , if you want to use
9248 this. It is possible to have several devices share a single parallel
9249 port and it is safe to compile the corresponding drivers into the
9252 If you want to compile this driver as a module however ( = code
9253 which can be inserted in and removed from the running kernel
9254 whenever you want), say M here and read Documentation/modules.txt.
9255 The module will be called de620.o.
9257 Token Ring driver support
9259 Token Ring is IBM's way of communication on a local network; the
9260 rest of the world uses Ethernet. To participate on a Token Ring
9261 network, you need a special Token ring network card. If you are
9262 connected to such a Token Ring network and want to use your Token
9263 Ring card under Linux, say Y here and to the driver for your
9264 particular card below and read the Token-Ring mini-HOWTO, available
9265 from http://www.linuxdoc.org/docs.html#howto . Most people can
9268 IBM Tropic chipset based adapter support
9270 This is support for all IBM Token Ring cards that don't use DMA. If
9271 you have such a beast, say Y and read the Token-Ring mini-HOWTO,
9272 available from http://www.linuxdoc.org/docs.html#howto .
9274 Warning: this driver will almost definitely fail if more than one
9275 active Token Ring card is present.
9277 This driver is also available as a module ( = code which can be
9278 inserted in and removed from the running kernel whenever you want).
9279 The module will be called ibmtr.o. If you want to compile it as a
9280 module, say M here and read Documentation/modules.txt.
9282 IBM Olympic chipset PCI adapter support
9284 This is support for all non-Lanstreamer IBM PCI Token Ring Cards.
9285 Specifically this is all IBM PCI, PCI Wake On Lan, PCI II, PCI II
9286 Wake On Lan, and PCI 100/16/4 adapters.
9288 If you have such an adapter, say Y and read the Token-Ring
9289 mini-HOWTO, available from
9290 http://www.linuxdoc.org/docs.html#howto .
9292 This driver is also available as a module ( = code which can be
9293 inserted in and removed from the running kernel whenever you want).
9294 The module will will be called olympic.o. If you want to compile it
9295 as a module, say M here and read Documentation/modules.txt.
9297 Also read the file Documentation/networking/olympic.txt or check the
9298 Linux Token Ring Project site for the latest information at
9299 http://www.linuxtr.net .
9301 IBM Lanstreamer chipset PCI adapter support
9303 This is support for IBM Lanstreamer PCI Token Ring Cards.
9305 If you have such an adapter, say Y and read the Token-Ring
9306 mini-HOWTO available via FTP (user:anonymous) from
9307 ftp://metalab.unc/edu/pub/Linux/docs/HOWTO.
9309 This driver is also available as a modules ( = code which can be
9310 inserted in and removed from the running kernel whenever you want).
9311 The modules will be called lanstreamer.o. If you want to compile it
9312 as a module, say M here and read Documentation/modules.txt.
9314 Generic TMS380 Token Ring ISA/PCI/MCA/EISA adapter support
9316 This driver provides generic support for token ring adapters
9317 based on the Texas Instruments TMS380 series chipsets. This
9318 includes the SysKonnect TR4/16(+) ISA (SK-4190), SysKonnect
9319 TR4/16(+) PCI (SK-4590), SysKonnect TR4/16 PCI (SK-4591),
9320 Compaq 4/16 PCI, Thomas-Conrad TC4048 4/16 PCI, and several
9321 Madge adapters. If you say Y here, you will be asked to select
9322 which cards to support below. If you're using modules, each
9323 class of card will be supported by a separate module.
9325 If you have such an adapter and would like to use it, say Y and
9326 read the Token-Ring mini-HOWTO, available from
9327 http://www.linuxdoc.org/docs.html#howto .
9329 Also read the file Documentation/networking/tms380tr.txt or
9330 check http://www.auk.cx/tms380tr/ .
9332 This driver is also available as a module ( = code which can be
9333 inserted in and removed from the running kernel whenever you want).
9334 The module will will be called tms380tr.o. If you want to compile it
9335 as a module, say M here and read Documentation/modules.txt.
9337 Generic TMS380 PCI support
9339 This tms380 module supports generic TMS380-based PCI cards.
9341 These cards are known to work:
9342 - Compaq 4/16 TR PCI
9343 - SysKonnect TR4/16 PCI (SK-4590/SK-4591)
9344 - Thomas-Conrad TC4048 PCI 4/16
9345 - 3Com Token Link Velocity
9347 This driver is available as a module ( = code which can be
9348 inserted in and removed from the running kernel whenever you want).
9349 The module will will be called tmspci.o. If you want to compile it
9350 as a module, say M here and read Documentation/modules.txt.
9352 Madge Smart 16/4 PCI Mk2 support
9354 This tms380 module supports the Madge Smart 16/4 PCI Mk2
9357 This driver is available as a module ( = code which can be
9358 inserted in and removed from the running kernel whenever you want).
9359 The module will will be called abyss.o. If you want to compile it
9360 as a module, say M here and read Documentation/modules.txt.
9362 Madge Smart 16/4 Ringode MicroChannel
9364 This tms380 module supports the Madge Smart 16/4 MC16 and MC32
9365 MicroChannel adapters.
9367 This driver is available as a module ( = code which can be
9368 inserted in and removed from the running kernel whenever you want).
9369 The module will will be called madgemc.o. If you want to compile it
9370 as a module, say M here and read Documentation/modules.txt.
9372 SMC ISA TokenRing adapter support
9374 This is support for the ISA and MCA SMC Token Ring cards,
9375 specifically SMC TokenCard Elite (8115T) and SMC TokenCard Elite/A
9378 If you have such an adapter and would like to use it, say Y or M and
9379 read the Token-Ring mini-HOWTO, available from
9380 http://www.linuxdoc.org/docs.html#howto and the file
9381 Documentation/networking/smctr.txt.
9383 This driver is also available as a module ( = code which can be
9384 inserted in and removed from the running kernel whenever you want).
9385 The module will will be called smctr.o. If you want to compile it
9386 as a module, say M here and read Documentation/modules.txt.
9388 Sun Happy Meal 10/100baseT support
9390 This driver supports the "hme" interface present on most Ultra
9391 systems and as an option on older Sbus systems. This driver supports
9392 both PCI and Sbus devices. This driver also supports the "qfe" quad
9393 100baseT device available in both PCI and Sbus configurations.
9395 This support is also available as a module called sunhme.o ( = code
9396 which can be inserted in and removed from the running kernel
9397 whenever you want). If you want to compile it as a module, say M
9398 here and read Documentation/modules.txt.
9402 This driver supports the "le" interface present on all 32-bit Sparc
9403 systems, on some older Ultra systems and as an Sbus option.
9405 This support is also available as a module called sunlance.o ( =
9406 code which can be inserted in and removed from the running kernel
9407 whenever you want). If you want to compile it as a module, say M
9408 here and read Documentation/modules.txt.
9410 Sun BigMAC 10/100baseT support (EXPERIMENTAL)
9412 This driver supports the "be" interface available as an Sbus option.
9413 This is Sun's older 100baseT ethernet device.
9415 This support is also available as a module called sunbmac.o ( = code
9416 which can be inserted in and removed from the running kernel
9417 whenever you want). If you want to compile it as a module, say M
9418 here and read Documentation/modules.txt.
9420 Sun QuadEthernet support
9422 This driver supports the "qe" 10baseT ethernet device, available as
9423 an Sbus option. Note that this is not the same as Quad FastEthernet
9424 "qfe" which is supported by the Happy Meal driver instead.
9426 This support is also available as a module called sunqe.o ( = code
9427 which can be inserted in and removed from the running kernel
9428 whenever you want). If you want to compile it as a module, say M
9429 here and read Documentation/modules.txt.
9431 Traffic Shaper (EXPERIMENTAL)
9433 The traffic shaper is a virtual network device that allows you to
9434 limit the rate of outgoing data flow over some other network device.
9435 The traffic that you want to slow down can then be routed through
9436 these virtual devices. See Documentation/networking/shaper.txt for
9439 An alternative to this traffic shaper is the experimental
9440 Class-Based Queueing (CBQ) scheduling support which you get if you
9441 say Y to "QoS and/or fair queueing" above.
9443 To set up and configure shaper devices, you need the shapecfg
9444 program, available from ftp://shadow.cabi.net/pub/Linux in the
9447 This driver is also available as a module ( = code which can be
9448 inserted in and removed from the running kernel whenever you want).
9449 The module will be called shaper.o. If you want to compile it as a
9450 module, say M here and read Documentation/modules.txt. If unsure,
9455 Fiber Distributed Data Interface is a high speed local area network
9456 design; essentially a replacement for high speed Ethernet. FDDI can
9457 run over copper or fiber. If you are connected to such a network and
9458 want a driver for the FDDI card in your computer, say Y here (and
9459 then also Y to the driver for your FDDI card, below). Most people
9462 Digital DEFEA and DEFPA adapter support
9464 This is support for the DIGITAL series of EISA (DEFEA) and PCI
9465 (DEFPA) controllers which can connect you to a local FDDI network.
9467 SysKonnect FDDI PCI support
9469 Say Y here if you have a SysKonnect FDDI PCI adapter.
9470 The following adapters are supported by this driver:
9471 - SK-5521 (SK-NET FDDI-UP)
9472 - SK-5522 (SK-NET FDDI-UP DAS)
9473 - SK-5541 (SK-NET FDDI-FP)
9474 - SK-5543 (SK-NET FDDI-LP)
9475 - SK-5544 (SK-NET FDDI-LP DAS)
9476 - SK-5821 (SK-NET FDDI-UP64)
9477 - SK-5822 (SK-NET FDDI-UP64 DAS)
9478 - SK-5841 (SK-NET FDDI-FP64)
9479 - SK-5843 (SK-NET FDDI-LP64)
9480 - SK-5844 (SK-NET FDDI-LP64 DAS)
9481 - Netelligent 100 FDDI DAS Fibre SC
9482 - Netelligent 100 FDDI SAS Fibre SC
9483 - Netelligent 100 FDDI DAS UTP
9484 - Netelligent 100 FDDI SAS UTP
9485 - Netelligent 100 FDDI SAS Fibre MIC
9487 Read Documentation/networking/skfp.txt for information about
9490 Questions concerning this driver can be addressed to:
9493 If you want to compile this driver as a module ( = code which can be
9494 inserted in and removed from the running kernel whenever you want),
9495 say M here and read Documentation/modules.txt. This is recommended.
9496 The module will be called skfp.o.
9498 HIgh Performance Parallel Interface support (EXPERIMENTAL)
9500 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
9501 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
9502 can run over copper (25m) or fiber (300m on multi-mode or 10km on
9503 single-mode). HIPPI networks are commonly used for clusters and to
9504 connect to super computers. If you are connected to a HIPPI network
9505 and have a HIPPI network card in your computer that you want to use
9506 under Linux, say Y here (you must also remember to enable the driver
9507 for your HIPPI card below). Most people will say N here.
9509 Essential RoadRunner HIPPI PCI adapter support
9511 Say Y here if this is your PCI HIPPI network card.
9513 This driver is also available as a module ( = code which can be
9514 inserted in and removed from the running kernel whenever you want).
9515 The module will be called rrunner.o. If you want to compile it as
9516 a module, say M here and read Documentation/modules.txt. If unsure,
9519 Use large TX/RX rings
9520 CONFIG_ROADRUNNER_LARGE_RINGS
9521 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
9522 of additional memory to allow for fastest operation, both for
9523 transmitting and receiving. This memory cannot be used by any other
9524 kernel code or by user space programs. Say Y here only if you have
9529 If you have an Acorn system with one of these (AKA25) network cards,
9530 you should say Y to this option if you wish to use it with Linux.
9532 Acorn/ANT Ether3 card
9534 If you have an Acorn system with one of these network cards, you
9535 should say Y to this option if you wish to use it with Linux.
9539 If you have an Acorn system with one of these network cards, you
9540 should say Y to this option if you wish to use it with Linux.
9542 EBSA-110 Ethernet interface
9543 CONFIG_ARM_AM79C961A
9544 If you wish to compile a kernel for the EBSA-110, then you should
9545 always answer Y to this.
9547 Support CDROM drives that are not SCSI or IDE/ATAPI
9548 CONFIG_CD_NO_IDESCSI
9549 If you have a CDROM drive that is neither SCSI nor IDE/ATAPI, say Y
9550 here, otherwise N. Read the CDROM-HOWTO, available from
9551 http://www.linuxdoc.org/docs.html#howto .
9553 Note that the answer to this question doesn't directly affect the
9554 kernel: saying N will just cause this configure script to skip all
9555 the questions about these CDROM drives. If you are unsure what you
9556 have, say Y and find out whether you have one of the following
9559 For each of these drivers, a file Documentation/cdrom/<driver_name>
9560 exists. Especially in cases where you do not know exactly which kind
9561 of drive you have you should read there. Most of these drivers use a
9562 file drivers/cdrom/<driver_name>.h where you can define your
9563 interface parameters and switch some internal goodies.
9565 All these CDROM drivers are also usable as a module ( = code which
9566 can be inserted in and removed from the running kernel whenever you
9567 want). If you want to compile them as module, say M instead of Y and
9568 read Documentation/modules.txt.
9570 If you want to use any of these CDROM drivers, you also have to
9571 answer Y or M to "ISO 9660 CDROM file system support" below (this
9572 answer will get "defaulted" for you if you enable any of the Linux
9575 Sony CDU31A/CDU33A CDROM support
9577 These CDROM drives have a spring-pop-out caddyless drawer, and a
9578 rectangular green LED centered beneath it. NOTE: these CDROM drives
9579 will not be auto detected by the kernel at boot time; you have to
9580 provide the interface address as an option to the kernel at boot
9581 time as described in Documentation/cdrom/cdu31a or fill in your
9582 parameters into drivers/cdrom/cdu31a.c. Try "man bootparam" or
9583 see the documentation of your boot loader (lilo or loadlin) about
9584 how to pass options to the kernel.
9586 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9587 file system support" below, because that's the file system used on
9590 This driver is also available as a module ( = code which can be
9591 inserted in and removed from the running kernel whenever you want).
9592 The module will be called cdu31a.o. If you want to compile it as a
9593 module, say M here and read Documentation/modules.txt.
9595 Standard Mitsumi [no XA/Multisession] CDROM support
9597 This is the older of the two drivers for the older Mitsumi models
9598 LU-005, FX-001 and FX-001D. This is not the right driver for the
9599 FX-001DE and the triple or quad speed models (all these are
9600 IDE/ATAPI models). Please also the file Documentation/cdrom/mcd.
9602 With the old LU-005 model, the whole drive chassis slides out for cd
9603 insertion. The FX-xxx models use a motorized tray type mechanism.
9604 Note that this driver does not support XA or MultiSession CDs
9605 (PhotoCDs). There is a new driver (next question) which can do
9606 this. If you want that one, say N here.
9608 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9609 file system support" below, because that's the file system used on
9612 This driver is also available as a module ( = code which can be
9613 inserted in and removed from the running kernel whenever you want).
9614 The module will be called mcd.o. If you want to compile it as a
9615 module, say M here and read Documentation/modules.txt.
9617 IRQ channel for Mitsumi CD-ROM
9619 This allows you to specify the default value of the IRQ used by the
9620 driver. This setting can be overridden by passing the "mcd="
9621 parameter to the kernel at boot time (or at module load time if you
9622 said M to "Standard Mitsumi CDROM support").
9624 I/O base address for Mitsumi CD-ROM
9626 This allows you to specify the default value of the I/O base address
9627 used by the driver. This setting can be overridden by passing the
9628 "mcd=" parameter to the kernel at boot time (or at module load time
9629 if you said M to "Standard Mitsumi CDROM support").
9631 Mitsumi [XA/MultiSession] support
9633 Use this driver if you want to be able to read XA or MultiSession
9634 CDs (PhotoCDs) as well as ordinary CDs with your Mitsumi LU-005,
9635 FX-001 or FX-001D CDROM drive. In addition, this driver uses much
9636 less kernel memory than the old one, if that is a concern. This
9637 driver is able to support more than one drive, but each drive needs
9638 a separate interface card. Please read the file
9639 Documentation/cdrom/mcdx.
9641 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9642 file system support" below, because that's the file system used on
9645 This driver is also available as a module ( = code which can be
9646 inserted in and removed from the running kernel whenever you want).
9647 The module will be called mcdx.o. If you want to compile it as a
9648 module, say M here and read Documentation/modules.txt.
9650 Matsushita/Panasonic/Creative, Longshine, TEAC CDROM support
9652 This driver supports most of the drives which use the Panasonic or
9653 Sound Blaster interface. Please read the file
9654 Documentation/cdrom/sbpcd.
9656 The Matsushita CR-521, CR-522, CR-523, CR-562, CR-563 drives
9657 (sometimes labeled "Creative"), the Creative Labs CD200, the
9658 Longshine LCS-7260, the "IBM External ISA CDROM" (in fact a CR-56x
9659 model), the TEAC CD-55A fall under this category. Some other
9660 "electrically compatible" drives (Vertos, Genoa, some Funai models)
9661 are currently not supported; for the Sanyo H94A drive currently a
9662 separate driver (asked later) is responsible. Most drives have a
9663 uniquely shaped faceplate, with a caddyless motorized drawer, but
9664 without external brand markings. The older CR-52x drives have a
9665 caddy and manual loading/eject, but still no external markings. The
9666 driver is able to do an extended auto-probing for interface
9667 addresses and drive types; this can help to find facts in cases you
9668 are not sure, but can consume some time during the boot process if
9669 none of the supported drives gets found. Once your drive got found,
9670 you should enter the reported parameters into drivers/cdrom/sbpcd.h
9671 and set "DISTRIBUTION 0" there.
9673 This driver can support up to four CDROM controller cards, and each
9674 card can support up to four CDROM drives; if you say Y here, you
9675 will be asked how many controller cards you have. If compiled as a
9676 module, only one controller card (but with up to four drives) is
9679 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9680 file system support" below, because that's the file system used on
9683 This driver is also available as a module ( = code which can be
9684 inserted in and removed from the running kernel whenever you want).
9685 The module will be called sbpcd.o. If you want to compile it as a
9686 module, say M here and read Documentation/modules.txt.
9688 Matsushita/Panasonic, ... second CDROM controller support
9690 Say Y here only if you have two CDROM controller cards of this type
9691 (usually only if you have more than four drives). You should enter
9692 the parameters for the second, third and fourth interface card into
9693 include/linux/sbpcd.h before compiling the new kernel. Read
9694 the file Documentation/cdrom/sbpcd.
9696 Aztech/Orchid/Okano/Wearnes/TXC/CyDROM CDROM support
9698 This is your driver if you have an Aztech CDA268-01A, Orchid
9699 CD-3110, Okano or Wearnes CDD110, Conrad TXC, or CyCDROM CR520 or
9700 CR540 CDROM drive. This driver -- just like all these CDROM drivers
9701 -- is NOT for CDROM drives with IDE/ATAPI interfaces, such as Aztech
9702 CDA269-031SE. Please read the file Documentation/cdrom/aztcd.
9704 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9705 file system support" below, because that's the file system used on
9708 This driver is also available as a module ( = code which can be
9709 inserted in and removed from the running kernel whenever you want).
9710 The module will be called aztcd.o. If you want to compile it as a
9711 module, say M here and read Documentation/modules.txt.
9713 Sony CDU535 CDROM support
9715 This is the driver for the older Sony CDU-535 and CDU-531 CDROM
9716 drives. Please read the file Documentation/cdrom/sonycd535.
9718 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9719 file system support" below, because that's the file system used on
9722 This driver is also available as a module ( = code which can be
9723 inserted in and removed from the running kernel whenever you want).
9724 The module will be called sonycd535.o. If you want to compile it as
9725 a module, say M here and read Documentation/modules.txt.
9727 Goldstar R420 CDROM support
9729 If this is your CDROM drive, say Y here. As described in the file
9730 Documentation/cdrom/gscd, you might have to change a setting
9731 in the file drivers/cdrom/gscd.h before compiling the
9732 kernel. Please read the file Documentation/cdrom/gscd.
9734 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9735 file system support" below, because that's the file system used on
9738 This driver is also available as a module ( = code which can be
9739 inserted in and removed from the running kernel whenever you want).
9740 The module will be called gscd.o. If you want to compile it as a
9741 module, say M here and read Documentation/modules.txt.
9743 Philips/LMS CM206 CDROM support
9745 If you have a Philips/LMS CDROM drive cm206 in combination with a
9746 cm260 host adapter card, say Y here. Please also read the file
9747 Documentation/cdrom/cm206.
9749 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9750 file system support" below, because that's the file system used on
9753 This driver is also available as a module ( = code which can be
9754 inserted in and removed from the running kernel whenever you want).
9755 The module will be called cm206.o. If you want to compile it as a
9756 module, say M here and read Documentation/modules.txt.
9758 Optics Storage DOLPHIN 8000AT CDROM support
9760 This is the driver for the 'DOLPHIN' drive with a 34-pin Sony
9761 compatible interface. It also works with the Lasermate CR328A. If
9762 you have one of those, say Y. This driver does not work for the
9763 Optics Storage 8001 drive; use the IDE-ATAPI CDROM driver for that
9764 one. Please read the file Documentation/cdrom/optcd.
9766 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9767 file system support" below, because that's the file system used on
9770 This driver is also available as a module ( = code which can be
9771 inserted in and removed from the running kernel whenever you want).
9772 The module will be called optcd.o. If you want to compile it as a
9773 module, say M here and read Documentation/modules.txt.
9775 Sanyo CDR-H94A CDROM support
9777 If this is your CDROM drive, say Y here and read the file
9778 Documentation/cdrom/sjcd. You should then also say Y or M to
9779 "ISO 9660 CDROM file system support" below, because that's the
9780 file system used on CDROMs.
9782 This driver is also available as a module ( = code which can be
9783 inserted in and removed from the running kernel whenever you want).
9784 The module will be called sjcd.o. If you want to compile it as a
9785 module, say M here and read Documentation/modules.txt.
9787 ISP16/MAD16/Mozart soft configurable cdrom interface support
9789 These are sound cards with built-in cdrom interfaces using the OPTi
9790 82C928 or 82C929 chips. Say Y here to have them detected and
9791 possibly configured at boot time. In addition, You'll have to say Y
9792 to a driver for the particular cdrom drive you have attached to the
9793 card. Read Documentation/cdrom/isp16 for details.
9795 This driver is also available as a module ( = code which can be
9796 inserted in and removed from the running kernel whenever you want).
9797 The module will be called isp16.o. If you want to compile it as a
9798 module, say M here and read Documentation/modules.txt.
9802 If you say Y here, you will be able to set per user limits for disk
9803 usage (also called disk quotas). Currently, it works only for the
9804 ext2 file system. You need additional software in order to use quota
9805 support; for details, read the Quota mini-HOWTO, available from
9806 http://www.linuxdoc.org/docs.html#howto . Probably the quota
9807 support is only useful for multi user systems. If unsure, say N.
9809 Memory Technology Device (MTD) support
9811 Memory Technology Devices are flash, RAM and similar chips, often
9812 used for solid state filesystems on embedded devices. This option
9813 will provide the generic support for MTD drivers to register
9814 themselves with the kernel and for potential users of MTD devices
9815 to enumerate the devices which are present and obtain a handle on
9816 them. It will also allow you to select individual drivers for
9817 particular hardware and users of MTD device. If unsure, say N.
9819 M-Systems Disk-On-Chip 1000 support
9821 This provides an MTD device driver for the M-Systems DiskOnChip
9822 1000 devices, which are obsolete so you probably want to say 'N'.
9824 M-Systems Disk-On-Chip 2000 support
9826 This provides an MTD device driver for the M-Systems DiskOnChip
9827 2000 devices. If you use this, you probably also want the NFTL
9828 'NAND Flash Translation Layer' below, which is used to emulate
9829 a block device by using a kind of filesystem on the flash chips.
9831 M-Systems Disk-On-Chip Millennium support
9833 This provides an MTD device driver for the M-Systems DiskOnChip
9834 Millennium devices. If you use this, you probably also want the
9835 NFTL 'NAND Flash Translation Layer' below, which is used to emulate
9836 a block device by using a kind of filesystem on the flash chips.
9838 Use extra onboard system memory as MTD device
9840 If your CPU cannot cache all of the physical memory in your machine,
9841 you can still use it for storage or swap by using this driver to
9842 present it to the system as a Memory Technology Device.
9844 Ramix PMC551 PCI Mezzanine ram card support
9846 This provides an MTD device driver for the Ramix PMC551 RAM card.
9847 If you have one, you probably want to enable this.
9849 PMC551 256M DRAM Bugfix.
9850 CONFIG_MTD_PMC551_BUGFIX
9851 Some PMC551 boards hacve invalid column and row mux values. This
9852 option will fix them, but will break other memory configurations.
9854 Debugging RAM test driver
9856 This enables a test MTD device driver which uses vmalloc() to
9857 provide storage. You probably want to say 'N' unless you're
9858 testing stuff, or unless you want to use it in place of a ramdisk
9859 when I've eventually got round to making the CONFIG_BLK_DEV option
9860 and you've turned it off.
9862 Common Flash Interface (CFI) support
9864 Intel's Common Flash Interface specification provides a universal
9865 method for probing the capabilities of flash devices. If you wish
9866 to support any device which uses CFI-compliant devices, you need
9867 to enable this option.
9869 CFI support for Intel/Sharp Extended Command Set chips
9870 CONFIG_MTD_CFI_INTELEXT
9871 The Common Flash Interface defines a number of different command
9872 sets which a CFI-compliant chip may claim to implement. This code
9873 provides support for one of those command sets, used on Intel
9874 Strataflash and other parts.
9876 Flash chip mapping in physical memory
9878 This provides a 'mapping' driver which allows the CFI probe and
9879 command set driver code to communicate with flash chips which
9880 are mapped physically into the CPU's memory. You will need to
9881 configure the physical address and size of the flash chips on
9882 your particular board.
9884 Physical start location of flash chip mapping
9885 CONFIG_MTD_PHYSMAP_START
9886 This is the physical memory location at which the flash chips
9887 are mapped on your particular target board. Refer to the
9888 memory map which should hopefully be in the documentation for
9891 Physical length of flash chip mapping
9892 CONFIG_MTD_PHYSMAP_LEN
9893 This is the total length of the mapping of the flash chips on
9894 your particular board. If there is space, or aliases, in the
9895 physical memory map between the chips, this could be larger
9896 than the total amount of flash present. Refer to the memory
9897 map which should hopefully be in the documentation for your
9900 Flash chip mapping on Mixcom piggyback card
9902 This supports the paging arrangement for access to flash chips
9903 on the Mixcom piggyback card, allowing the flash chip drivers
9904 to get on with their job of driving the flash chips without
9905 having to know about the paging. If you have one of these boards,
9906 you probably want to enable this mapping driver.
9908 Flash chip mapping on Nora
9910 If you had to ask, you don't have one. Say 'N'.
9912 Flash chip mapping on Octagon 5066 SBC
9914 This provides a 'mapping' driver which supports the way in which
9915 the flash chips are connected in the Octagon-5066 Single Board
9916 Computer. You will also need to complete and enable the driver
9917 for JEDEC flash chips.
9919 Flash chip mapping on RPXlite PPC board
9921 The RPXLite PowerPC board has CFI-compliant chips mapped in
9922 a strange sparse mapping. This 'mapping' driver supports that
9923 arrangement, allowing the CFI probe and command set driver code
9924 to communicate with the chips on the RPXLite board.
9926 Flash chip mapping on Tempustech VMAX SBC301
9928 This provides a 'mapping' driver which supports the way in which
9929 the flash chips are connected in the Tempustech VMAX SBC301 Single
9930 Board Computer. You will also need to complete and enable the driver
9931 for JEDEC flash chips.
9933 Direct chardevice access to MTD devices
9935 This provides a character device for each MTD device present in
9936 the system, allowing the user to read and write directly to the
9937 memory chips, and also use ioctl() to obtain information about
9938 the device, or to erase parts of it.
9940 Pseudo-blockdevice access to MTD devices
9942 Although flash chips have an erase size too large to useful as
9943 block devices, it is possible to use MTD devices which are based
9944 on RAM chips in this manner. This blockdevice user of MTD devices
9945 performs that function. At the moment, it is also required for
9946 the Journalling Flash File System to obtain a handle on the MTD
9947 device when it's mounted - although the JFFS doesn't actually use
9948 any of the functions of the mtdblock device.
9950 Later, it may be extended to perform read/erase/modify/write cycles
9951 on flash chips to emulate a smaller block size. Needless to say,
9952 this is very unsafe, but could be useful for filesystems which are
9953 almost never written to.
9955 FTL (Flash Translation Layer) support
9957 This provides support for the original Flash Translation Layer which
9958 is part of the PCMCIA specification. It uses a kind of pseudo-
9959 filesystem on a flash device to emulate a block device with 512-byte
9960 sectors, on top of which you put a 'normal' filesystem. You may find
9961 that the algorithms used in this code are patented unless you live
9962 in the Free World where software patents aren't legal - in the USA
9963 you are only permitted to use this on PCMCIA hardware, although
9964 under the terms of the GPL you're obviously permitted to copy,
9965 modify and distribute the code as you wish. Just not use it.
9967 NFTL (NAND Flash Translation Layer) support
9969 This provides support for the NAND Flash Translation Layer which is
9970 used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
9971 filesystem on a flash device to emulate a block device with 512-byte
9972 sectors, on top of which you put a 'normal' filesystem. You may find
9973 that the algorithms used in this code are patented unless you live
9974 in the Free World where software patents aren't legal - in the USA
9975 you are only permitted to use this on DiskOnChip hardware, although
9976 under the terms of the GPL you're obviously permitted to copy,
9977 modify and distribute the code as you wish. Just not use it.
9979 Write support for NFTL (EXPERIMENTAL)
9981 If you're lucky, this will actually work. Don't whinge if it doesn't.
9982 Contact dwmw2@infradead.org if you want to help to make it more
9987 Universal Serial Bus (USB) is a specification for a serial bus
9988 subsystem which offers higher speeds and more features than the
9989 traditional PC serial port. The bus supplies power to peripherals
9990 and allows for hot swapping. Up to 127 USB peripherals can be
9991 connected to a single USB port in a tree structure. The USB port is
9992 the root of the tree, the peripherals are the leaves and the inner
9993 nodes are special USB devices called hubs. Many newer PC's have USB
9994 ports and newer peripherals such as scanners, keyboards, mice,
9995 modems, and printers support the USB protocol and can be connected
9996 to the PC via those ports.
9998 Say Y here if your computer has a USB port and you want to use USB
9999 devices. You then need to say Y to at least one of "UHCI support" or
10000 "OHCI support" below (the type of interface that the USB hardware in
10001 your computer provides to the operating system) and then choose from
10002 among the drivers for USB peripherals. You may want to check out the
10003 information provided in Documentation/usb/ and especially the links
10004 given in Documentation/usb/usb-help.txt.
10006 This code is also available as a module ( = code which can be
10007 inserted in and removed from the running kernel whenever you want).
10008 The module will be called usbcore.o. If you want to compile it as a
10009 module, say M here and read Documentation/modules.txt.
10011 USB verbose debug messages
10013 Say Y here if you want the USB core & hub drivers to produce a bunch
10014 of debug messages to the system log. Select this if you are having a
10015 problem with USB support and want to see more of what is going on.
10017 UHCI (intel PIIX4, VIA, ...) support?
10019 The Universal Host Controller Interface is a standard by Intel for
10020 accessing the USB hardware in the PC (which is also called the USB
10021 host controller). If your USB host controller conforms to this
10022 standard, you may want to say Y, but see below. All recent boards
10023 with Intel PCI chipsets (like intel 430TX, 440FX, 440LX, 440BX,
10024 i810, i820) conform to this standard. Also all VIA PCI chipsets
10025 (like VIA VP2, VP3, MVP3, Apollo Pro, Apollo Pro II or Apollo Pro
10028 Currently there exist two drivers for UHCI host controllers: this
10029 one and the so-called JE driver, which you can get from
10030 "UHCI alternate (JE) support", below. You need only one.
10032 This code is also available as a module ( = code which can be
10033 inserted in and removed from the running kernel whenever you want).
10034 The module will be called usb-uhci.o. If you want to compile it as a
10035 module, say M here and read Documentation/modules.txt.
10037 UHCI (intel PIIX4, VIA, ...) alternate (JE) support?
10038 CONFIG_USB_UHCI_ALT
10039 The Universal Host Controller Interface is a standard by Intel for
10040 accessing the USB hardware in the PC (which is also called the USB
10041 host controller). If your USB host controller conforms to this
10042 standard, you may want to say Y, but see below. All recent boards
10043 with Intel PCI chipsets (like intel 430TX, 440FX, 440LX, 440BX,
10044 i810, i820) conform to this standard. Also all VIA PCI chipsets
10045 (like VIA VP2, VP3, MVP3, Apollo Pro, Apollo Pro II or Apollo Pro
10046 133). If unsure, say Y.
10048 Currently there exist two drivers for UHCI host controllers: this
10049 so-called JE driver, and the one you get from "UHCI support", above.
10052 This code is also available as a module ( = code which can be
10053 inserted in and removed from the running kernel whenever you want).
10054 The module will be called uhci.o. If you want to compile it as a
10055 module, say M here and read Documentation/modules.txt.
10057 UHCI unlink optimizations (EXPERIMENTAL)
10058 CONFIG_USB_UHCI_ALT_UNLINK_OPTIMIZE
10059 This option currently does nothing. You may say Y or N.
10061 OHCI (Compaq, iMacs, OPTi, SiS, ALi, ...) support
10063 The Open Host Controller Interface is a standard by
10064 Compaq/Microsoft/National for accessing the USB PC hardware (also
10065 called USB host controller). If your USB host controller conforms to
10066 this standard, say Y. The USB host controllers on most non-Intel
10067 architectures and on several x86 compatibles with non-Intel chipsets
10068 -- like SiS (aktual 610, 610 and so on) or ALi (ALi IV, ALi V,
10069 Aladdin Pro..) -- conform to this standard.
10071 You may want to read the file Documentation/usb/ohci.txt.
10073 This code is also available as a module ( = code which can be
10074 inserted in and removed from the running kernel whenever you want).
10075 The module will be called usb-ohci.o. If you want to compile it
10076 as a module, say M here and read Documentation/modules.txt.
10078 USB Human Interface Device (full HID) support
10080 Say Y here if you want full HID support to connect keyboards,
10081 mice, joysticks, graphic tablets, or any other HID based devices
10082 to your computer via USB. You can't use this driver and the
10083 HIDBP (Boot Protocol) keyboard and mouse drivers at the same time.
10084 More information is available: Documentation/usb/input.txt.
10088 This code is also available as a module ( = code which can be
10089 inserted in and removed from the running kernel whenever you want).
10090 The module will be called hid.o. If you want to compile it as a
10091 module, say M here and read Documentation/modules.txt.
10093 USB HIDBP Keyboard (basic) support
10095 Say Y here if you don't want to use the generic HID driver for your
10096 USB keyboard and prefer to use the keyboard in its limited Boot
10097 Protocol mode instead. This driver is much smaller than the HID one.
10099 This code is also available as a module ( = code which can be
10100 inserted in and removed from the running kernel whenever you want).
10101 The module will be called usbkbd.o. If you want to compile it as a
10102 module, say M here and read Documentation/modules.txt.
10106 USB HIDBP Mouse (basic) support
10108 Say Y here if you don't want to use the generic HID driver for your
10109 USB mouse and prefer to use the mouse in its limited Boot Protocol
10110 mode instead. This driver is much smaller than the HID one.
10112 This code is also available as a module ( = code which can be
10113 inserted in and removed from the running kernel whenever you want).
10114 The module will be called usbmouse.o. If you want to compile it as
10115 a module, say M here and read Documentation/modules.txt.
10119 Wacom Intuos/Graphire tablet support
10121 Say Y here if you want to use the USB version of the Wacom Intuos
10122 or Graphire tablet. Make sure to say Y to "Mouse support"
10123 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
10124 (CONFIG_INPUT_EVDEV) as well.
10126 This driver is also available as a module ( = code which can be
10127 inserted in and removed from the running kernel whenever you want).
10128 The module will be called wacom.o. If you want to compile it as a
10129 module, say M here and read Documentation/modules.txt.
10131 Logitech WingMan Force joystick support
10133 Say Y here if you want to use the Logitech WingMan Force with Linux
10134 on the USB port. No force-feedback support yet, but other than that
10135 it should work like a normal joystick.
10137 This driver is also available as a module ( = code which can be
10138 inserted in and removed from the running kernel whenever you want).
10139 The module will be called wmforce.o. If you want to compile it as a
10140 module, say M here and read Documentation/modules.txt.
10142 Use input layer for ADB devices
10143 CONFIG_INPUT_ADBHID
10144 Say Y here if you want to have ADB (Apple Desktop Bus) HID devices
10145 such as keyboards, mice, joysticks, or graphic tablets handled by the
10146 input layer. If you say Y here, make sure to say Y to the
10147 corresponding drivers "Keyboard support" (CONFIG_INPUT_KEYBDEV),
10148 "Mouse Support" (CONFIG_INPUT_MOUSEDEV) and "Event interface support"
10149 (CONFIG_INPUT_EVDEV) as well.
10151 If you say N here, you still have the option of using the old ADB
10152 keyboard and mouse drivers.
10157 CONFIG_INPUT_KEYBDEV
10158 Say Y here if you want your USB HID keyboard (or an ADB keyboard
10159 handled by the input layer) to be able to serve as a system keyboard.
10161 This driver is also available as a module ( = code which can be
10162 inserted in and removed from the running kernel whenever you want).
10163 The module will be called keybdev.o. If you want to compile it as a
10164 module, say M here and read Documentation/modules.txt.
10167 CONFIG_INPUT_MOUSEDEV
10168 Say Y here if you want your USB HID mouse (or ADB mouse handled by
10169 the input layer) to be accessible as char devices 13:32+ -
10170 /dev/input/mouseX and 13:63 - /dev/input/mice as an emulated ImPS/2
10171 mouse. That way, all user space programs will be able to use your
10176 This driver is also available as a module ( = code which can be
10177 inserted in and removed from the running kernel whenever you want).
10178 The module will be called mousedev.o. If you want to compile it as
10179 a module, say M here and read Documentation/modules.txt.
10181 Horizontal screen resolution
10182 CONFIG_INPUT_MOUSEDEV_SCREEN_X
10183 If you're using a digitizer, or a graphic tablet, and want to use
10184 it as a mouse then the mousedev driver needs to know the X window
10185 screen resolution you are using to correctly scale the data. If
10186 you're not using a digitizer, this value is ignored.
10188 Vertical screen resolution
10189 CONFIG_INPUT_MOUSEDEV_SCREEN_Y
10190 If you're using a digitizer, or a graphic tablet, and want to use
10191 it as a mouse then the mousedev driver needs to know the X window
10192 screen resolution you are using to correctly scale the data. If
10193 you're not using a digitizer, this value is ignored.
10196 CONFIG_INPUT_JOYDEV
10197 Say Y here if you want your USB HID joystick or gamepad to be
10198 accessible as char device 13:0+ - /dev/input/jsX device.
10200 This driver is also available as a module ( = code which can be
10201 inserted in and removed from the running kernel whenever you want).
10202 The module will be called joydev.o. If you want to compile it as a
10203 module, say M here and read Documentation/modules.txt.
10205 Event interface support
10207 Say Y here if you want your USB or ADB HID device events be accessible
10208 under char device 13:64+ - /dev/input/eventX in a generic way.
10209 This is the future ...
10211 USB Scanner support
10213 Say Y here if you want to connect a USB scanner to your computer's
10214 USB port. Please read Documentation/usb/scanner.txt and
10215 Documentation/usb/scanner-hp-sane.txt for more information.
10217 This code is also available as a module ( = code which can be
10218 inserted in and removed from the running kernel whenever you want).
10219 The module will be called scanner.o. If you want to compile it as
10220 a module, say M here and read Documentation/modules.txt.
10224 Say Y here if you want to connect UAB audio equipment such as
10225 speakers to your computer's USB port.
10227 This code is also available as a module ( = code which can be
10228 inserted in and removed from the running kernel whenever you want).
10229 The module will be called audio.o. If you want to compile it as a
10230 module, say M here and read Documentation/modules.txt.
10232 USB Modem (CDC ACM) support
10234 This driver supports USB modems and ISDN adapters which support the
10235 Communication Device Class Abstract Control Model interface.
10236 Please read Documentation/usb/acm.txt for details.
10238 This code is also available as a module ( = code which can be
10239 inserted in and removed from the running kernel whenever you want).
10240 The module will be called acm.o. If you want to compile it as a
10241 module, say M here and read Documentation/modules.txt.
10243 USB Serial converter support
10245 Say Y here if you have a USB device that provides normal serial
10246 ports, and you want to connect it to your USB bus. Supported devices
10247 are the Tech WhiteHEAT multi-port USB to serial converter, and the
10248 FTDI or Keyspan single port USB to serial converter Handspring
10249 Visor. In addition to saying Y here, you need to say Y to the driver
10250 for your specific hardware below. Some other devices may also be
10251 used if you say Y to "USB Generic Serial Driver", below.
10253 Please read Documentation/usb/usb-serial.txt for more information.
10255 This code is also available as a module ( = code which can be
10256 inserted in and removed from the running kernel whenever you want).
10257 The module will be called usbserial.o. If you want to compile it
10258 as a module, say M here and read Documentation/modules.txt.
10260 USB Generic Serial Driver
10261 CONFIG_USB_SERIAL_GENERIC
10262 Say Y here if you want to use the generic USB serial driver. Please
10263 read Documentation/usb/usb-serial.txt for more information on using
10264 this driver. It is recommended that the "USB Serial converter
10265 support" be compiled as a module for this driver to be used
10268 USB ConnectTech WhiteHEAT Serial Driver
10269 CONFIG_USB_SERIAL_WHITEHEAT
10270 Say Y here if you want to use a ConnectTech WhiteHEAT 4 port
10271 USB to serial converter device.
10273 This code is also available as a module ( = code which can be
10274 inserted in and removed from the running kernel whenever you want).
10275 The module will be called whiteheat.o. If you want to compile it as a
10276 module, say M here and read Documentation/modules.txt.
10278 USB Handspring Visor Driver
10279 CONFIG_USB_SERIAL_VISOR
10280 Say Y here if you want to connect to your HandSpring Visor through
10281 its USB docking station. See http://usbvisor.sourceforge.net for
10282 more information on using this driver.
10284 This code is also available as a module ( = code which can be
10285 inserted in and removed from the running kernel whenever you want).
10286 The module will be called visor.o. If you want to compile it as a
10287 module, say M here and read Documentation/modules.txt.
10289 USB Belkin and Paracom Single Port Serial Driver
10290 CONFIG_USB_SERIAL_BELKIN
10291 Say Y here if you want to use a Belkin USB Serial single port
10292 adaptor (F5U103 is one of the model numbers) or the Peracom single
10293 port USB to serial adapter.
10295 This code is also available as a module ( = code which can be
10296 inserted in and removed from the running kernel whenever you want).
10297 The module will be called belkin_sa.o. If you want to compile it as
10298 a module, say M here and read Documentation/modules.txt.
10300 USB FTDI Single Port Serial Driver
10301 CONFIG_USB_SERIAL_FTDI_SIO
10302 Say Y here if you want to use a FTDI SIO single port USB to serial
10303 converter device. The implementation I have is called the USC-1000.
10305 See http://reality.sgi.com/bryder_wellington/ftdi_sio for more
10306 information on this driver and the device.
10308 This code is also available as a module ( = code which can be
10309 inserted in and removed from the running kernel whenever you want).
10310 The module will be called ftdi_sio.o. If you want to compile it as a
10311 module, say M here and read Documentation/modules.txt.
10313 USB Keyspan PDA Single Port Serial Driver
10314 CONFIG_USB_SERIAL_KEYSPAN_PDA
10315 Say Y here if you want to use a Keyspan PDA single port USB to
10316 serial converter device. This driver makes use of firmware
10317 developed from scratch by Brian Warner.
10319 This code is also available as a module ( = code which can be
10320 inserted in and removed from the running kernel whenever you want).
10321 The module will be called keyspan_pda.o. If you want to compile it
10322 as a module, say M here and read Documentation/modules.txt.
10324 USB Keyspan USA-xxx Serial Driver
10325 CONFIG_USB_SERIAL_KEYSPAN
10326 Say Y here if you want to use Keyspan USB to serial converter
10327 devices. This driver makes use of Keyspan's official firmware
10328 and was developed with their support. You must also include
10329 firmware to support your particular device(s).
10331 See http://www.linuxcare.com.au/hugh/keyspan.html for
10334 This code is also available as a module ( = code which can be
10335 inserted in and removed from the running kernel whenever you want).
10336 The module will be called keyspan.o. If you want to compile it as a
10337 module, say M here and read Documentation/modules.txt.
10339 USB Keyspan USA-28 Firmware
10340 CONFIG_USB_SERIAL_KEYSPAN_USA28
10341 Say Y here to include firmware for the USA-28 converter.
10343 USB Keyspan USA-28X Firmware
10344 CONFIG_USB_SERIAL_KEYSPAN_USA28X
10345 Say Y here to include firmware for the USA-28X converter.
10347 USB Keyspan USA-19 Firmware
10348 CONFIG_USB_SERIAL_KEYSPAN_USA19
10349 Say Y here to include firmware for the USA-19 converter.
10351 USB Keyspan USA-18X Firmware
10352 CONFIG_USB_SERIAL_KEYSPAN_USA18X
10353 Say Y here to include firmware for the USA-18X converter.
10355 USB Keyspan USA-19W Firmware
10356 CONFIG_USB_SERIAL_KEYSPAN_USA19W
10357 Say Y here to include firmware for the USA-19W converter.
10359 USB ZyXEL omni.net LCD Plus Driver
10360 CONFIG_USB_SERIAL_OMNINET
10361 Say Y here if you want to use a ZyXEL omni.net LCD ISDN TA.
10363 This code is also available as a module ( = code which can be
10364 inserted in and removed from the running kernel whenever you want).
10365 The module will be called omninet.o. If you want to compile it as a
10366 module, say M here and read Documentation/modules.txt.
10368 USB Digi International AccelePort USB Serial Driver
10369 CONFIG_USB_SERIAL_DIGI_ACCELEPORT
10370 Say Y here if you want to use Digi AccelePort USB 2 or 4 devices,
10371 2 port (plus parallel port) and 4 port USB serial converters. The
10372 parallel port on the USB 2 appears as a third serial port on Linux.
10373 The Digi Acceleport USB 8 is not yet supported by this driver.
10375 This driver works under SMP with the usb-uhci driver. It does not
10376 work under SMP with the uhci driver.
10378 This code is also available as a module ( = code which can be
10379 inserted in and removed from the running kernel whenever you want).
10380 The module will be called digi_acceleport.o. If you want to compile
10381 it as a module, say M here and read Documentation/modules.txt.
10383 USB Empeg empeg-car Mark I/II Driver
10384 CONFIG_USB_SERIAL_EMPEG
10385 Say Y here if you want to connect to your Empeg empeg-car Mark I/II
10386 mp3 player via USB. The driver uses a single ttyUSB{0,1,2,...}
10387 device node. See Documentation/usb/usb-serial.txt for more
10388 tidbits of information.
10390 This code is also available as a module ( = code which can be
10391 inserted in and removed from the running kernel whenever you want).
10392 The module will be called empeg.o. If you want to compile it as a
10393 module, say M here and read Documentation/modules.txt.
10395 USB Serial Converter verbose debug
10396 CONFIG_USB_SERIAL_DEBUG
10397 Say Y here if you want verbose debug messages from the USB Serial
10400 USB Printer support
10402 Say Y here if you want to connect a USB printer to your computer's
10405 This code is also available as a module ( = code which can be
10406 inserted in and removed from the running kernel whenever you want).
10407 The module will be called printer.o. If you want to compile it as a
10408 module, say M here and read Documentation/modules.txt.
10410 USB IBM (Xirlink) C-It Camera support
10412 Say Y here if you want to connect a IBM "C-It" camera, also known as
10413 "Xirlink PC Camera" to your computer's USB port. For more
10414 information, read Documentation/usb/ibmcam.txt.
10416 This driver uses the Video For Linux API. You must enable
10417 (Y or M in config) Video For Linux (under Character Devices)
10418 to use this driver. Information on this API and pointers to
10419 "v4l" programs may be found on the WWW at
10420 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
10422 This code is also available as a module ( = code which can be
10423 inserted in and removed from the running kernel whenever you want).
10424 The module will be called ibmcam.o. If you want to compile it as a
10425 module, say M here and read Documentation/modules.txt. This camera
10426 has several configuration options which can be specified when you
10427 load the module. Read Documentation/usb/ibmcam.txt to learn more.
10429 USB OV511 Camera support
10431 Say Y here if you want to connect this type of camera to your
10432 computer's USB port. See Documentation/usb/ov511.txt for more
10433 information and for a list of supported cameras.
10435 This driver uses the Video For Linux API. You must say Y or M to
10436 "Video For Linux" (under Character Devices) to use this driver.
10437 Information on this API and pointers to "v4l" programs may be found
10438 on the WWW at http://roadrunner.swansea.uk.linux.org/v4l.shtml .
10440 This code is also available as a module ( = code which can be
10441 inserted in and removed from the running kernel whenever you want).
10442 The module will be called ov511.o. If you want to compile it as a
10443 module, say M here and read Documentation/modules.txt.
10445 USB ADMtek Pegasus-based ethernet device support
10447 Say Y if you want to use your USB ethernet device. Supported
10448 cards until now are:
10449 ADMtek AN986 Pegasus (eval. board)
10450 ADMtek ADM8511 Pegasus II (eval. board)
10453 Corega FEter USB-TX
10454 MELCO/BUFFALO LUA-TX
10455 D-Link DSB-650TX, DSB-650TX-PNA, DSB-650, DU-E10, DU-E100
10456 Linksys USB100TX, USB10TX
10457 LANEED Ethernet LD-USB/TX
10459 SOHOware NUB Ethernet
10461 Any Pegasus II based board also are supported.
10462 If you have devices with vendor IDs other than noted above
10463 you should add them in the driver code and send a message
10464 to me (petkan@dce.bg) for update.
10466 This code is also available as a module ( = code which can be
10467 inserted in and removed from the running kernel whenever you want).
10468 The module will be called pegasus.o. If you want to compile it as a
10469 module, say M here and read Documentation/modules.txt.
10471 USB Kodak DC-2xx Camera support
10473 Say Y here if you want to connect this type of still camera to
10474 your computer's USB port. See Documentation/usb/dc2xx.txt for more
10475 information; some non-Kodak cameras may also work with this
10476 driver, given application support (such as www.gPhoto.org).
10478 This code is also available as a module ( = code which can be
10479 inserted in and removed from the running kernel whenever you want).
10480 The module will be called dc2xx.o. If you want to compile it as a
10481 module, say M here and read Documentation/modules.txt.
10483 USB Mustek MDC800 Digital Camera Support
10485 Say Y here if you want to connect this type of still camera to
10486 your computer's USB port. This driver can be used with gphoto 0.4.3
10487 and higher (look at http://www.gphoto.org ).
10488 To use it create a device node with "mknod /dev/mustek c 180 32" and
10489 configure it in your software.
10491 This code is also available as a module ( = code which can be
10492 inserted in and removed from the running kernel whenever you want).
10493 The module will be called mdc800.o. If you want to compile it as a
10494 module, say M here and read Documentation/modules.txt.
10496 USB Mass Storage support
10498 Say Y here if you want to connect USB mass storage devices to your
10499 computer's USB port.
10501 This code is also available as a module ( = code which can be
10502 inserted in and removed from the running kernel whenever you want).
10503 The module will be called usb-storage.o. If you want to compile it
10504 as a module, say M here and read Documentation/modules.txt.
10506 USB Mass Storage verbose debug
10507 CONFIG_USB_STORAGE_DEBUG
10508 Say Y here in order to have the USB Mass Storage code generate
10509 verbose debugging messages.
10511 USS720 parport driver
10513 This driver is for USB parallel port adapters that use the Lucent
10514 Technologies USS-720 chip. These cables are plugged into your USB
10515 port and provide USB compatibility to peripherals designed with
10516 parallel port interfaces.
10518 The chip has two modes: automatic mode and manual mode. In automatic
10519 mode, it looks to the computer like a standard USB printer. Only
10520 printers may be connected to the USS-720 in this mode. The generic
10521 USB printer driver ("USB Printer support", above) may be used in
10522 that mode, and you can say N here if you want to use the chip only
10525 Manual mode is not limited to printers, any parallel port
10526 device should work. This driver utilizes manual mode.
10527 Note however that some operations are three orders of magnitude
10528 slower than on a PCI/ISA Parallel Port, so timing critical
10529 applications might not work.
10531 Say Y here if you own an USS-720 USB->Parport cable and intend to
10532 connect anything other than a printer to it.
10534 This code is also available as a module ( = code which can be
10535 inserted in and removed from the running kernel whenever you want).
10536 The module will be called uss720.o. If you want to compile it as a
10537 module, say M here and read Documentation/modules.txt.
10539 USB device file system
10540 CONFIG_USB_DEVICEFS
10541 If you say Y here (and to "/proc file system support" below), you
10542 will get a file /proc/usb/devices which lists the devices currently
10543 connected to your USB busses, a file /proc/usb/drivers which lists
10544 the USB kernel client drivers currently loaded, and for every
10545 connected device a file named "/proc/usb/xxx/yyy", where xxx is the
10546 bus number and yyy the device number; the latter files can be used
10547 by user space programs to talk directly to the device. These files
10548 are "virtual", meaning they are generated on the fly and not stored
10551 For the format of the /proc/usb/ files, please read
10552 Documentation/usb/proc_usb_info.txt.
10554 Please note that this code is completely unrelated to devfs, the
10555 "/dev file system support".
10557 Most users want to say Y here.
10559 USB Bandwidth allocation
10560 CONFIG_USB_BANDWIDTH
10561 If you say Y here, the USB subsystem enforces USB bandwidth
10562 allocation and will prevent some device opens from succeeding
10563 if they would cause USB bandwidth usage to go above 90% of
10566 If you say N here, these conditions will cause warning messages
10567 about USB bandwidth usage to be logged and some devices or
10568 drivers may not work correctly.
10572 A Digital Audio Broadcasting (DAB) Receiver for USB and Linux
10573 brought to you by the DAB-Team (http://dab.in.tum.de). This driver
10574 can be taken as an example for URB-based bulk, control, and
10575 isochronous transactions. URB's are explained in
10576 Documentation/usb/URB.txt.
10578 This code is also available as a module ( = code which can be
10579 inserted in and removed from the running kernel whenever you want).
10580 The module will be called dabusb.o. If you want to compile it as a
10581 module, say M here and read Documentation/modules.txt.
10585 A driver for the Prolific PL-2302 USB-to-USB network device. This
10586 'USB cable' connects two hosts via a point-to-point network with
10587 bandwidth of 5 Mbit/s. Configure this driver after connecting the
10588 USB cable via ifconfig plusb0 10.0.0.1 pointopoint 10.0.0.2 (and
10589 vice versa on the other host).
10591 This code is also available as a module ( = code which can be
10592 inserted in and removed from the running kernel whenever you want).
10593 The module will be called plusb.o. If you want to compile it as a
10594 module, say M here and read Documentation/modules.txt.
10596 USB Diamond Rio500 support
10598 Say Y here if you want to connect a USB Rio500 mp3 player to your
10599 computer's USB port. Please read Documentation/usb/rio.txt
10600 for more information.
10602 This code is also available as a module ( = code which can be
10603 inserted in and removed from the running kernel whenever you want).
10604 The module will be called rio500.o. If you want to compile it as
10605 a module, say M here and read Documentation/modules.txt.
10607 D-Link DSB-R100 FM radio support
10609 Say Y here if you want to connect this type of radio to your
10610 computer's USB port. Note that the audio is not digital, and
10611 you must connect the line out connector to a sound card or a
10614 This driver uses the Video For Linux API. You must enable
10615 (Y or M in config) Video For Linux (under Character Devices)
10616 to use this driver. Information on this API and pointers to
10617 "v4l" programs may be found on the WWW at
10618 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
10620 This code is also available as a module ( = code which can be
10621 inserted in and removed from the running kernel whenever you want).
10622 The module will be called dsbr100.o. If you want to compile it as a
10623 module, say M here and read Documentation/modules.txt.
10625 Microtek USB scanner support
10626 CONFIG_USB_MICROTEK
10627 Say Y here if you want support for the Microtek X6USB and possibly
10628 some other scanners by that vendor. The scanner will appear as a
10629 scsi generic device to the rest of the system.
10630 A patched version of SANE is necessary to use the
10631 scanner. It's available at
10632 http://fachschaft.cup.uni-muenchen.de/~neukum/scanner.html
10633 This driver can be compiled as a module.
10635 USB Bluetooth support
10636 CONFIG_USB_BLUETOOTH
10637 Say Y here if you want to connect a USB Bluetooth device to your
10638 computer's USB port. You will need the Bluetooth stack (available
10639 at http://developer.axis.com/software/index.shtml) to fully use
10642 This code is also available as a module ( = code which can be
10643 inserted in and removed from the running kernel whenever you want).
10644 The module will be called bluetooth.o. If you want to compile it as
10645 a module, say M here and read Documentation/modules.txt.
10649 Minix is a simple operating system used in many classes about OS's.
10650 The minix file system (method to organize files on a hard disk
10651 partition or a floppy disk) was the original file system for Linux,
10652 but has been superseded by the second extended file system ext2fs.
10653 You don't want to use the minix file system on your hard disk
10654 because of certain built-in restrictions, but it is sometimes found
10655 on older Linux floppy disks. This option will enlarge your kernel by
10656 about 28 KB. If unsure, say N.
10658 If you want to compile this as a module ( = code which can be
10659 inserted in and removed from the running kernel whenever you want),
10660 say M here and read Documentation/modules.txt. The module will be
10661 called minix.o. Note that the file system of your root partition
10662 (the one containing the directory /) cannot be compiled as a module.
10664 Second extended fs support
10666 This is the de facto standard Linux file system (method to organize
10667 files on a storage device) for hard disks.
10669 You want to say Y here, unless you intend to use Linux exclusively
10670 from inside a DOS partition using the UMSDOS file system. The
10671 advantage of the latter is that you can get away without
10672 repartitioning your hard drive (which often implies backing
10673 everything up and restoring afterwards); the disadvantage is that
10674 Linux becomes susceptible to DOS viruses and that UMSDOS is somewhat
10675 slower than ext2fs. Even if you want to run Linux in this fashion,
10676 it might be a good idea to have ext2fs around: it enables you to
10677 read more floppy disks and facilitates the transition to a *real*
10678 Linux partition later. Another (rare) case which doesn't require
10679 ext2fs is a diskless Linux box which mounts all files over the
10680 network using NFS (in this case it's sufficient to say Y to "NFS
10681 file system support" below). Saying Y here will enlarge your kernel
10684 The Ext2fs-Undeletion mini-HOWTO, available from
10685 http://www.linuxdoc.org/docs.html#howto , gives information about
10686 how to retrieve deleted files on ext2fs file systems.
10688 To change the behavior of ext2 file systems, you can use the tune2fs
10689 utility ("man tune2fs"). To modify attributes of files and
10690 directories on ext2 file systems, use chattr ("man chattr").
10692 Ext2fs partitions can be read from within DOS using the ext2tool
10693 command line tool package (available via FTP (user: anonymous) from
10694 ftp://metalab.unc.edu/pub/Linux/system/filesystems/ext2 ) and from
10695 within Windows NT using the ext2nt command line tool package from
10696 ftp://metalab.unc.edu/pub/Linux/utils/dos . Explore2fs is a
10697 graphical explorer for ext2fs partitions which runs on Windows 95
10698 and Windows NT and includes experimental write support; it is
10700 http://jnewbigin-pc.it.swin.edu.au/Linux/Explore2fs.htm .
10702 If you want to compile this file system as a module ( = code which
10703 can be inserted in and removed from the running kernel whenever you
10704 want), say M here and read Documentation/modules.txt. The module
10705 will be called ext2.o. Be aware however that the file system of your
10706 root partition (the one containing the directory /) cannot be
10707 compiled as a module, and so this could be dangerous. Most everyone
10708 wants to say Y here.
10710 BFS file system support (EXPERIMENTAL)
10712 Boot File System (BFS) is a file system used under SCO UnixWare to
10713 allow the bootloader access to the kernel image and other important
10714 files during the boot process. It is usually mounted under /stand
10715 and corresponds to the slice marked as "STAND" in the UnixWare
10716 partition. You should say Y if you want to read or write
10717 the files on your /stand slice from within Linux. You then also
10718 need to say Y to "UnixWare slices support", below. More information
10719 about the BFS file system is contained in the file
10720 Documentation/filesystems/bfs.txt.
10722 If you don't know what this is about, say N.
10724 If you want to compile this as a module ( = code which can be
10725 inserted in and removed from the running kernel whenever you want),
10726 say M here and read Documentation/modules.txt. The module will be
10727 called bfs.o. Note that the file system of your root partition (the
10728 one containing the directory /) cannot be compiled as a module.
10730 Compressed ROM file system support
10732 Saying Y here includes support for CramFs (Compressed ROM File
10733 System). Cramfs is designed to be a simple, small, and compressed
10734 file system for ROM based embedded systems. CramFs is read-only,
10735 limited to 256MB file systems (with 16MB files), and doesn't support
10736 16/32 bits uid/gid, hard links and timestamps.
10738 See Documentation/filesystems/cramfs.txt and fs/cramfs/README
10739 for further information.
10741 If you want to compile this as a module ( = code which can be
10742 inserted in and removed from the running kernel whenever you want),
10743 say M here and read Documentation/modules.txt. The module will be
10744 called cramfs.o. Note that the root file system (the one containing
10745 the directory /) cannot be compiled as a module.
10749 Simple RAM-based file system support
10751 Ramfs is a file system which keeps all files in RAM. It allows
10752 read and write access.
10754 In contrast to RAM disks, which get allocated a fixed amount of RAM,
10755 ramfs grows and shrinks to accommodate the files it contains.
10757 Before you can use this RAM-based file system, it has to be mounted,
10758 meaning it has to be given a location in the directory hierarchy. If
10759 you want to use the location /ramfiles for example, you would have
10760 to create that directory first and then mount the file system by
10761 saying "mount -t ramfs ramfs /ramfiles" or the equivalent line in
10762 /etc/fstab. Everything is "virtual" in the sense that no files will
10763 be created on your hard drive; if you reboot, everything in
10764 /ramfiles will be lost.
10766 If you want to compile this as a module ( = code which can be
10767 inserted in and removed from the running kernel whenever you want),
10768 say M here and read Documentation/modules.txt. The module will be
10771 ISO 9660 CDROM file system support
10773 This is the standard file system used on CDROMs. It was previously
10774 known as "High Sierra File System" and is called "hsfs" on other
10775 Unix systems. The so-called Rock-Ridge extensions which allow for
10776 long Unix filenames and symbolic links are also supported by this
10777 driver. If you have a CDROM drive and want to do more with it than
10778 just listen to audio CDs and watch its LEDs, say Y (and read
10779 Documentation/filesystems/isofs.txt and the CDROM-HOWTO, available
10780 from http://www.linuxdoc.org/docs.html#howto ), thereby enlarging
10781 your kernel by about 27 KB; otherwise say N.
10783 If you want to compile this as a module ( = code which can be
10784 inserted in and removed from the running kernel whenever you want),
10785 say M here and read Documentation/modules.txt. The module will be
10788 Microsoft Joliet CDROM extensions
10790 Joliet is a Microsoft extension for the ISO 9660 CDROM file system
10791 which allows for long filenames in unicode format (unicode is the
10792 new 16 bit character code, successor to ASCII, which encodes the
10793 characters of almost all languages of the world; see
10794 http://www.unicode.org for more information). Say Y here if you want
10795 to be able to read Joliet CDROMs under Linux.
10797 UDF File System support (read only)
10799 This is the new file system used on some CDROMs and DVDs. Say Y if
10800 you intend to mount DVD discs or CDRW's written in packet mode, or
10801 if written to by other UDF utilities, such as DirectCD. This UDF
10802 file system support is read-only. If you want to write to UDF
10803 file systems on some media, you need to say Y to "UDF read-write
10804 support" below in addition. Please read
10805 Documentation/filesystems/udf.txt.
10807 This file system support is also available as a module ( = code
10808 which can be inserted in and removed from the running kernel
10809 whenever you want). The module is called udf.o. If you want to
10810 compile it as a module, say M here and read
10811 Documentation/modules.txt.
10815 UDF write support (DANGEROUS)
10817 Say Y if you want to test write support for UDF file systems.
10818 Due to lack of support for writing to CDR/CDRW's, this option
10819 is only supported for hard discs, DVD-RAM, and loopback files.
10823 If you want to use one of the FAT-based file systems (the MS-DOS,
10824 VFAT (Windows 95) and UMSDOS (used to run Linux on top of an
10825 ordinary DOS partition) file systems), then you must say Y or M here
10826 to include FAT support. You will then be able to mount partitions or
10827 diskettes with FAT-based file systems and transparently access the
10828 files on them, i.e. MSDOS files will look and behave just like all
10831 This FAT support is not a file system in itself, it only provides
10832 the foundation for the other file systems. You will have to say Y or
10833 M to at least one of "MSDOS fs support" or "VFAT fs support" in
10834 order to make use of it.
10836 Another way to read and write MSDOS floppies and hard drive
10837 partitions from within Linux (but not transparently) is with the
10838 mtools ("man mtools") program suite. You don't need to say Y here in
10841 If you need to move large files on floppies between a DOS and a
10842 Linux box, say Y here, mount the floppy under Linux with an MSDOS
10843 file system and use GNU tar's M option. GNU tar is a program
10844 available for Unix and DOS ("man tar" or "info tar").
10846 It is now also becoming possible to read and write compressed FAT
10847 file systems; read Documentation/filesystems/fat_cvf.txt for
10850 The FAT support will enlarge your kernel by about 37 KB. If unsure,
10853 If you want to compile this as a module however ( = code which can
10854 be inserted in and removed from the running kernel whenever you
10855 want), say M here and read Documentation/modules.txt. The module
10856 will be called fat.o. Note that if you compile the FAT support as a
10857 module, you cannot compile any of the FAT-based file systems into
10858 the kernel -- they will have to be modules as well. The file system
10859 of your root partition (the one containing the directory /) cannot
10860 be a module, so don't say M here if you intend to use UMSDOS as your
10865 This allows you to mount MSDOS partitions of your hard drive (unless
10866 they are compressed; to access compressed MSDOS partitions under
10867 Linux, you can either use the DOS emulator DOSEMU, described in the
10868 DOSEMU-HOWTO, available from
10869 http://www.linuxdoc.org/docs.html#howto , or try dmsdosfs in
10870 ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs . If you
10871 intend to use dosemu with a non-compressed MSDOS partition, say Y
10872 here) and MSDOS floppies. This means that file access becomes
10873 transparent, i.e. the MSDOS files look and behave just like all
10876 If you want to use UMSDOS, the Unix-like file system on top of a
10877 DOS file system, which allows you to run Linux from within a DOS
10878 partition without repartitioning, you'll have to say Y or M here.
10880 If you have Windows 95 or Windows NT installed on your MSDOS
10881 partitions, you should use the VFAT file system (say Y to "VFAT fs
10882 support" below), or you will not be able to see the long filenames
10883 generated by Windows 95 / Windows NT.
10885 This option will enlarge your kernel by about 7 KB. If unsure,
10886 answer Y. This will only work if you said Y to "DOS FAT fs support"
10887 as well. If you want to compile this as a module however ( = code
10888 which can be inserted in and removed from the running kernel
10889 whenever you want), say M here and read Documentation/modules.txt.
10890 The module will be called msdos.o.
10892 VFAT (Windows-95) fs support
10894 This option provides support for normal Windows file systems with
10895 long filenames. That includes non-compressed FAT-based file systems
10896 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
10897 programs from the mtools package.
10899 You cannot use the VFAT file system for your Linux root partition
10900 (the one containing the directory /); use UMSDOS instead if you
10901 want to run Linux from within a DOS partition (i.e. say Y to
10902 "UMSDOS: Unix like fs on top of std MSDOS fs", below).
10904 The VFAT support enlarges your kernel by about 10 KB and it only
10905 works if you said Y to the "DOS FAT fs support" above. Please read
10906 the file Documentation/filesystems/vfat.txt for details. If unsure,
10909 If you want to compile this as a module ( = code which can be
10910 inserted in and removed from the running kernel whenever you want),
10911 say M here and read Documentation/modules.txt. The module will be
10914 UMSDOS: Unix-like file system on top of standard MSDOS fs
10916 Say Y here if you want to run Linux from within an existing DOS
10917 partition of your hard drive. The advantage of this is that you can
10918 get away without repartitioning your hard drive (which often implies
10919 backing everything up and restoring afterwards) and hence you're
10920 able to quickly try out Linux or show it to your friends; the
10921 disadvantage is that Linux becomes susceptible to DOS viruses and
10922 that UMSDOS is somewhat slower than ext2fs. Another use of UMSDOS
10923 is to write files with long unix filenames to MSDOS floppies; it
10924 also allows Unix-style soft-links and owner/permissions of files on
10925 MSDOS floppies. You will need a program called umssync in order to
10926 make use of UMSDOS; read Documentation/filesystems/umsdos.txt.
10928 To get utilities for initializing/checking UMSDOS file system, or
10929 latest patches and/or information, visit the UMSDOS home page at
10930 http://www.voyager.hr/~mnalis/umsdos/ .
10932 This option enlarges your kernel by about 28 KB and it only works if
10933 you said Y to both "DOS FAT fs support" and "MSDOS fs support"
10934 above. If you want to compile this as a module ( = code which can be
10935 inserted in and removed from the running kernel whenever you want),
10936 say M here and read Documentation/modules.txt. The module will be
10937 called umsdos.o. Note that the file system of your root partition
10938 (the one containing the directory /) cannot be a module, so saying M
10939 could be dangerous. If unsure, say N.
10941 /proc file system support
10943 This is a virtual file system providing information about the status
10944 of the system. "Virtual" means that it doesn't take up any space on
10945 your hard disk: the files are created on the fly by the kernel when
10946 you try to access them. Also, you cannot read the files with older
10947 version of the program less: you need to use more or cat.
10949 It's totally cool; for example, "cat /proc/interrupts" gives
10950 information about what the different IRQs are used for at the moment
10951 (there is a small number of Interrupt ReQuest lines in your computer
10952 that are used by the attached devices to gain the CPU's attention --
10953 often a source of trouble if two devices are mistakenly configured
10954 to use the same IRQ). The program procinfo to display some
10955 information about your system gathered from the /proc file system.
10957 Before you can use the /proc file system, it has to be mounted,
10958 meaning it has to be given a location in the directory hierarchy.
10959 That location should be /proc. A command such as "mount -t proc proc
10960 /proc" or the equivalent line in /etc/fstab does the job.
10962 The /proc file system is explained in the file
10963 Documentation/filesystems/proc.txt and on the proc(5) manpage ("man
10966 This option will enlarge your kernel by about 67 KB. Several
10967 programs depend on this, so everyone should say Y here.
10969 /dev file system support (EXPERIMENTAL)
10971 This is support for devfs, a virtual file system (like /proc) which
10972 provides the file system interface to device drivers, normally found
10973 in /dev. Devfs does not depend on major and minor number
10974 allocations. Device drivers register entries in /dev which then
10975 appear automatically, which means that the system administrator does
10976 not have to create character and block special device files in the
10977 /dev directory using the mknod command (or MAKEDEV script) anymore.
10979 This is work in progress. If you want to use this, you *must* read
10980 the material in Documentation/filesystems/devfs/, especially the
10985 Enable automatic mounting at boot
10987 This option appears if you have CONFIG_DEVFS_FS enabled. Setting
10988 this to 'Y' will make the kernel automatically mount devfs onto /dev
10989 when the system is booted, before the init thread is started.
10990 You can override this with the "devfs=nomount" boot option.
10996 If you say Y here, then the /dev file system code will generate
10997 debugging messages. See the file
10998 Documentation/filesystems/devfs/boot-options for more details.
11002 NFS file system support
11004 If you are connected to some other (usually local) Unix computer
11005 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
11006 on that computer (the NFS server) using the Network File Sharing
11007 protocol, say Y. "Mounting files" means that the client can access
11008 the files with usual UNIX commands as if they were sitting on the
11009 client's hard disk. For this to work, the server must run the
11010 programs nfsd and mountd (but does not need to have NFS file system
11011 support enabled in its kernel). NFS is explained in the Network
11012 Administrator's Guide, available from
11013 http://www.linuxdoc.org/docs.html#guide , on its man page: "man
11014 nfs", and in the NFS-HOWTO.
11016 A superior but less widely used alternative to NFS is provided by
11017 the Coda file system; see "Coda file system support" below.
11019 If you say Y here, you should have said Y to TCP/IP networking also.
11020 This option would enlarge your kernel by about 27 KB.
11022 This file system is also available as a module ( = code which can be
11023 inserted in and removed from the running kernel whenever you want).
11024 The module is called nfs.o. If you want to compile it as a module,
11025 say M here and read Documentation/modules.txt.
11027 If you are configuring a diskless machine which will mount its root
11028 file system over NFS at boot time, say Y here and to "IP: kernel
11029 level autoconfiguration" above and to "Root file system on NFS"
11030 below. You cannot compile this driver as a module in this case.
11031 There are two packages designed for booting diskless machines over
11032 the net: netboot and etherboot, both available via FTP from
11033 ftp://metalab.unc.edu/pub/Linux/system/boot/ethernet/ .
11035 If you don't know what all this is about, say N.
11037 Provide NFSv3 client support (EXPERIMENTAL)
11039 Say Y here if you want your NFS client to be able to speak the newer
11040 version 3 of the NFS protocol.
11044 Root file system on NFS
11046 If you want your Linux box to mount its whole root file system (the
11047 one containing the directory /) from some other computer over the
11048 net via NFS (presumably because your box doesn't have a hard disk),
11049 say Y. Read Documentation/nfsroot.txt for details. It is likely that
11050 in this case, you also want to say Y to "IP: kernel level
11051 autoconfiguration" so that your box can discover its network address
11054 Most people say N here.
11058 If you want your Linux box to act as an NFS *server*, so that other
11059 computers on your local network which support NFS can access certain
11060 directories on your box transparently, you have two options: you can
11061 use the self-contained user space program nfsd, in which case you
11062 should say N here, or you can say Y and use the kernel based NFS
11063 server. The advantage of the kernel based solution is that it is
11066 In either case, you will need support software; the respective
11067 locations are given in the file Documentation/Changes in the NFS
11070 If you say Y here, you will get support for version 2 of the NFS
11071 protocol (NFSv2). If you also want NFSv3, say Y to the next question
11074 Please read the NFS-HOWTO, available from
11075 http://www.linuxdoc.org/docs.html#howto .
11077 The NFS server is also available as a module ( = code which can be
11078 inserted in and removed from the running kernel whenever you want).
11079 The module is called nfsd.o. If you want to compile it as a module,
11080 say M here and read Documentation/modules.txt. If unsure, say N.
11082 Provide NFSv3 server support
11084 If you would like to include the NFSv3 server as well as the NFSv2
11085 server, say Y here. If unsure, say Y.
11087 Provide NFS over TCP server support DEVELOPER ONLY
11089 If you are a developer and want to work on fixing problems with
11090 NFS server over TCP support, say Y here. If unsure, say N.
11092 Some problems can be found by looking for FIXME in net/sunrpc/svcsock.c
11094 OS/2 HPFS file system support
11096 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
11097 is the file system used for organizing files on OS/2 hard disk
11098 partitions. Say Y if you want to be able to read files from and
11099 write files to an OS/2 HPFS partition on your hard drive. OS/2
11100 floppies however are in regular MSDOS format, so you don't need this
11101 option in order to be able to read them. Read
11102 Documentation/filesystems/hpfs.txt.
11104 This file system is also available as a module ( = code which can be
11105 inserted in and removed from the running kernel whenever you want).
11106 The module is called hpfs.o. If you want to compile it as a module,
11107 say M here and read Documentation/modules.txt. If unsure, say N.
11109 NTFS support (read only)
11111 NTFS is the file system of Microsoft Windows NT. Say Y if you want
11112 to get read access to files on NTFS partitions of your hard drive.
11113 The Linux NTFS driver supports most of the mount options of the VFAT
11114 driver, see Documentation/filesystems/ntfs.txt. Saying Y here will
11115 give you read-only access to NTFS partitions.
11117 This code is also available as a module ( = code which can be
11118 inserted in and removed from the running kernel whenever you want).
11119 The module will be called ntfs.o. If you want to compile it as a
11120 module, say M here and read Documentation/modules.txt.
11122 NTFS write support (DANGEROUS)
11124 If you say Y here, you will (maybe) be able to write to NTFS file
11125 systems as well as read from them. The read-write support in
11126 NTFS is far from being complete and is not well tested. If you
11127 say Y here, back up your NTFS volume first since it may get
11128 damaged. Also, make sure to run chkdsk from within Microsoft
11129 Windows NT after having performed any writes to a NTFS partition
11130 from Linux to detect any problems as early as possible.
11131 Please note that write support is limited to Windows NT4 and
11136 System V and Coherent file system support (read only)
11138 SCO, Xenix and Coherent are commercial Unix systems for Intel
11139 machines. Saying Y here would allow you to read from their floppies
11140 and hard disk partitions. If you also want to write to these media,
11141 say Y to "SYSV file system write support" below.
11143 If you have floppies or hard disk partitions like that, it is likely
11144 that they contain binaries from those other Unix systems; in order
11145 to run these binaries, you will want to install iBCS2 (Intel Binary
11146 Compatibility Standard is a kernel module which lets you run SCO,
11147 Xenix, Wyse, UnixWare, Dell Unix and System V programs under Linux
11148 and is often needed to run commercial software that's only available
11149 for those systems. It's available via FTP (user: anonymous) from
11150 ftp://tsx-11.mit.edu/pub/linux/BETA ).
11152 If you only intend to mount files from some other Unix over the
11153 network using NFS, you don't need the System V file system support
11154 (but you need NFS file system support obviously).
11156 Note that this option is generally not needed for floppies, since a
11157 good portable way to transport files and directories between unixes
11158 (and even other operating systems) is given by the tar program ("man
11159 tar" or preferably "info tar"). Note also that this option has
11160 nothing whatsoever to do with the option "System V IPC". Read about
11161 the System V file system in Documentation/filesystems/sysv-fs.txt.
11162 Saying Y here will enlarge your kernel by about 27 KB.
11164 If you want to compile this as a module ( = code which can be
11165 inserted in and removed from the running kernel whenever you want),
11166 say M here and read Documentation/modules.txt. The module will be
11169 If you haven't heard about all of this before, it's safe to say N.
11171 SYSV file system write support (DANGEROUS)
11172 CONFIG_SYSV_FS_WRITE
11173 If you say Y here, you will be able to write to hard drive
11174 partitions and floppy disks which carry a SYSV file system used the
11175 commercial Unixes SCO, Xenix and Coherent.
11177 This support is experimental and you may destroy your data. If
11180 Amiga FFS file system support
11182 The Fast File System (FFS) is the common file system used on hard
11183 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
11184 if you want to be able to read and write files from and to an Amiga
11185 FFS partition on your hard drive. Amiga floppies however cannot be
11186 read with this driver due to an incompatibility of the floppy
11187 controller used in an Amiga and the standard floppy controller in
11188 PCs and workstations. Read Documentation/filesystems/affs.txt and
11191 With this driver you can also mount disk files used by Bernd
11192 Schmidt's Un*X Amiga Emulator (http://www.freiburg.linux.de/~uae/ ).
11193 If you want to do this, you will also need to say Y or M to "Loop
11194 device support", above.
11196 This file system is also available as a module ( = code which can be
11197 inserted in and removed from the running kernel whenever you want).
11198 The module is called affs.o. If you want to compile it as a module,
11199 say M here and read Documentation/modules.txt. If unsure, say N.
11201 Apple Macintosh file system support (EXPERIMENTAL)
11203 If you say Y here, you will be able to mount Macintosh-formatted
11204 floppy disks and hard drive partitions with full read-write access.
11205 Please read fs/hfs/HFS.txt to learn about the available mount
11208 This file system support is also available as a module ( = code
11209 which can be inserted in and removed from the running kernel
11210 whenever you want). The module is called hfs.o. If you want to
11211 compile it as a module, say M here and read
11212 Documentation/modules.txt.
11214 ROM file system support
11216 This is a very small read-only file system mainly intended for
11217 initial ram disks of installation disks, but it could be used for
11218 other read-only media as well. Read
11219 Documentation/filesystems/romfs.txt for details.
11221 This file system support is also available as a module ( = code
11222 which can be inserted in and removed from the running kernel
11223 whenever you want). The module is called romfs.o. If you want to
11224 compile it as a module, say M here and read
11225 Documentation/modules.txt. Note that the file system of your root
11226 partition (the one containing the directory /) cannot be a module.
11228 If you don't know whether you need it, then you don't need it:
11231 QNX4 file system support (read only) (EXPERIMENTAL)
11233 This is the file system used by the operating system QNX 4. Say Y if
11234 you intend to mount QNX hard disks or floppies. Unless you say Y to
11235 "QNX4FS read-write support" below, you will only be able to read
11236 these file systems.
11238 This file system support is also available as a module ( = code
11239 which can be inserted in and removed from the running kernel
11240 whenever you want). The module is called qnx4.o. If you want to
11241 compile it as a module, say M here and read
11242 Documentation/modules.txt.
11244 If you don't know whether you need it, then you don't need it:
11247 QNX4FS write support (DANGEROUS)
11249 Say Y if you want to test write support for QNX4 file systems.
11251 Kernel automounter support
11253 The automounter is a tool to automatically mount remote file systems
11254 on demand. This implementation is partially kernel-based to reduce
11255 overhead in the already-mounted case; this is unlike the BSD
11256 automounter (amd), which is a pure user space daemon.
11258 To use the automounter you need the user-space tools from the autofs
11259 package; you can find the location in Documentation/Changes. You
11260 also want to answer Y to "NFS file system support", below.
11262 If you want to use the newer version of the automounter with more
11263 features, say N here and say Y to "Kernel automounter v4 support",
11266 If you want to compile this as a module ( = code which can be
11267 inserted in and removed from the running kernel whenever you want),
11268 say M here and read Documentation/modules.txt. The module will be
11271 If you are not a part of a fairly large, distributed network, you
11272 probably do not need an automounter, and can say N here.
11274 Kernel automounter v4 support
11276 The automounter is a tool to automatically mount remote file systems
11277 on demand. This implementation is partially kernel-based to reduce
11278 overhead in the already-mounted case; this is unlike the BSD
11279 automounter (amd), which is a pure user space daemon.
11281 To use the automounter you need the user-space tools from
11282 ftp://ftp.kernel.org/pub/linux/daemons/autofs/testing-v4 ; you also
11283 want to answer Y to "NFS file system support", below.
11285 If you want to compile this as a module ( = code which can be
11286 inserted in and removed from the running kernel whenever you want),
11287 say M here and read Documentation/modules.txt. The module will be
11288 called autofs4.o. You will need to add "alias autofs autofs4" to
11289 your modules configuration file.
11291 If you are not a part of a fairly large, distributed network or
11292 don't have a laptop which needs to dynamically reconfigure to the
11293 local network, you probably do not need an automounter, and can say
11296 EFS file system support (read-only) (EXPERIMENTAL)
11298 EFS is an older file system used for non-ISO9660 CDROMs and hard
11299 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
11300 uses the XFS file system for hard disk partitions however).
11302 This implementation only offers read-only access. If you don't know
11303 what all this is about, it's safe to say N. For more information
11304 about EFS see its home page at http://aeschi.ch.eu.org/efs/ .
11306 If you want to compile the EFS file system support as a module ( =
11307 code which can be inserted in and removed from the running kernel
11308 whenever you want), say M here and read Documentation/modules.txt.
11309 The module will be called efs.o.
11311 Journalling Flash File System (JFFS) support (EXPERIMENTAL)
11313 JFFS is a new file system designed for use on flash memory devices
11314 rather than on block devices. It was developed on the 2.0 kernel
11315 by Axis Communications AB for use on their Linux-based products,
11316 and released under GPL, then 'borrowed' and ported to work with
11317 the 2.4 kernel and the new Memory Technology Device system.
11319 The 2.4 port is experimental and not yet supported by Axis. Basically,
11320 the good bits are probably theirs, and if it's broken in 2.4 it's
11321 probably our fault. See http://www.developer.axis.com/software/jffs/
11322 for more information about JFFS.
11324 Any potential patches or queries should be sent to Axis' mailing
11325 list for JFFS: <jffs-dev@axis.com>
11327 UFS file system support (read-only)
11329 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
11330 OpenBSD and NeXTstep) use a file system called UFS. Some System V
11331 Unixes can create and mount hard disk partitions and diskettes using
11332 this file system as well. Saying Y here will allow you to read from
11333 these partitions; if you also want to write to them, say Y to the
11334 experimental "UFS file system write support", below. Please read the
11335 file Documentation/filesystems/ufs.txt for more information.
11337 If you only intend to mount files from some other Unix over the
11338 network using NFS, you don't need the UFS file system support (but
11339 you need NFS file system support obviously).
11341 Note that this option is generally not needed for floppies, since a
11342 good portable way to transport files and directories between unixes
11343 (and even other operating systems) is given by the tar program ("man
11344 tar" or preferably "info tar").
11346 When accessing NeXTstep files, you may need to convert them from the
11347 NeXT character set to the Latin1 character set; use the program
11348 recode ("info recode") for this purpose.
11350 If you want to compile the UFS file system support as a module ( =
11351 code which can be inserted in and removed from the running kernel
11352 whenever you want), say M here and read Documentation/modules.txt.
11353 The module will be called ufs.o.
11355 If you haven't heard about all of this before, it's safe to say N.
11357 UFS file system write support (DANGEROUS)
11358 CONFIG_UFS_FS_WRITE
11359 Say Y here if you want to try writing to UFS partitions. This is
11360 experimental, so you should back up your UFS partitions beforehand.
11362 Advanced partition selection
11363 CONFIG_PARTITION_ADVANCED
11364 Say Y here if you would like to use hard disks under Linux which
11365 were partitioned under an operating system running on a different
11366 architecture than your Linux system.
11368 Note that the answer to this question won't directly affect the
11369 kernel: saying N will just cause this configure script to skip all
11370 the questions about foreign partitioning schemes.
11374 Alpha OSF partition support
11375 CONFIG_OSF_PARTITION
11376 Say Y here if you would like to use hard disks under Linux which
11377 were partitioned on an Alpha machine.
11379 Macintosh partition map support
11380 CONFIG_MAC_PARTITION
11381 Say Y here if you would like to use hard disks under Linux which
11382 were partitioned on a Macintosh.
11384 PC BIOS (MSDOS partition tables) support
11385 CONFIG_MSDOS_PARTITION
11386 Say Y here if you would like to use hard disks under Linux which
11387 were partitioned on an x86 PC (not necessarily by DOS).
11389 BSD disklabel (FreeBSD partition tables) support
11390 CONFIG_BSD_DISKLABEL
11391 FreeBSD uses its own hard disk partition scheme on your PC. It
11392 requires only one entry in the primary partition table of your disk
11393 and manages it similarly to DOS extended partitions, putting in its
11394 first sector a new partition table in BSD disklabel format. Saying Y
11395 here allows you to read these disklabels and further mount FreeBSD
11396 partitions from within Linux if you have also said Y to "UFS
11397 file system support", above. If you don't know what all this is
11400 Sun partition tables support
11401 CONFIG_SUN_PARTITION
11402 Like most systems, SunOS uses its own hard disk partition table
11403 format, incompatible with all others. Saying Y here allows you to
11404 read these partition tables and further mount SunOS partitions from
11405 within Linux if you have also said Y to "UFS file system support",
11406 above. This is mainly used to carry data from a SPARC under SunOS to
11407 your Linux box via a removable medium like magneto-optical or ZIP
11408 drives; note however that a good portable way to transport files and
11409 directories between unixes (and even other operating systems) is
11410 given by the tar program ("man tar" or preferably "info tar"). If
11411 you don't know what all this is about, say N.
11413 Solaris (x86) partition table support
11414 CONFIG_SOLARIS_X86_PARTITION
11415 Like most systems, Solaris x86 uses its own hard disk partition
11416 table format, incompatible with all others. Saying Y here allows you
11417 to read these partition tables and further mount Solaris x86
11418 partitions from within Linux if you have also said Y to "UFS
11419 file system support", above.
11421 SGI partition support
11422 CONFIG_SGI_PARTITION
11423 Say Y here if you would like to be able to read the hard disk
11424 partition table format used by SGI machines.
11426 ADFS file system support (EXPERIMENTAL)
11428 The Acorn Disc Filing System is the standard file system of the
11429 RiscOS operating system which runs on Acorn's ARM-based Risc PC
11430 systems and the Acorn Archimedes range of machines. If you say Y
11431 here, Linux will be able to read from ADFS partitions on hard drives
11432 and from ADFS-formatted floppy discs. If you also want to be able to
11433 write to those devices, say Y to "ADFS write support" below.
11435 The ADFS partition should be the first partition (i.e.,
11436 /dev/[hs]d?1) on each of your drives. Please read the file
11437 Documentation/filesystems/adfs.txt for further details.
11439 This code is also available as a module called adfs.o ( = code which
11440 can be inserted in and removed from the running kernel whenever you
11441 want). If you want to compile it as a module, say M here and read
11442 Documentation/modules.txt.
11446 ADFS write support (DANGEROUS)
11448 If you say Y here, you will be able to write to ADFS partitions on
11449 hard drives and ADFS-formatted floppy disks. This is experimental
11450 codes, so if you're unsure, say N.
11452 /dev/pts file system for Unix98 PTYs
11454 You should say Y here if you said Y to "Unix98 PTY support" above.
11455 You'll then get a virtual file system which can be mounted on
11456 /dev/pts with "mount -t devpts". This, together with the pseudo
11457 terminal master multiplexer /dev/ptmx, is used for pseudo terminal
11458 support as described in The Open Group's Unix98 standard: in order
11459 to acquire a pseudo terminal, a process opens /dev/ptmx; the number
11460 of the pseudo terminal is then made available to the process and the
11461 pseudo terminal slave can be accessed as /dev/pts/<number>. What was
11462 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
11464 The GNU C library glibc 2.1 contains the requisite support for this
11465 mode of operation; you also need client programs that use the Unix98
11466 API. Please read Documentation/Changes for more information about
11467 the Unix98 pty devices.
11469 Note that the experimental "/dev file system support"
11470 (CONFIG_DEVFS_FS) is a more general facility.
11472 UnixWare slices support (EXPERIMENTAL)
11473 CONFIG_UNIXWARE_DISKLABEL
11474 Like some systems, UnixWare uses its own slice table inside a
11475 partition (VTOC - Virtual Table of Contents). Its format is
11476 incompatible with all other OSes. Saying Y here allows you to read
11477 VTOC and further mount UnixWare partitions read-only from within
11478 Linux if you have also said Y to "UFS file system support" or
11479 "System V and Coherent file system support", above.
11481 This is mainly used to carry data from a UnixWare box to your
11482 Linux box via a removable medium like magneto-optical, ZIP or
11483 removable IDE drives. Note, however, that a good portable way to
11484 transport files and directories between unixes (and even other
11485 operating systems) is given by the tar program ("man tar" or
11486 preferably "info tar").
11488 If you don't know what all this is about, say N.
11490 SMB file system support (to mount Windows shares etc.)
11492 SMB (Server Message Block) is the protocol Windows for Workgroups
11493 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
11494 files and printers over local networks. Saying Y here allows you to
11495 mount their file systems (often called "shares" in this context) and
11496 access them just like any other Unix directory. Currently, this
11497 works only if the Windows machines use TCP/IP as the underlying
11498 transport protocol, and not NetBEUI. For details, read
11499 Documentation/filesystems/smbfs.txt and the SMB-HOWTO, available
11500 from http://www.linuxdoc.org/docs.html#howto .
11502 Note: if you just want your box to act as an SMB *server* and make
11503 files and printing services available to Windows clients (which need
11504 to have a TCP/IP stack), you don't need to say Y here; you can use
11505 the program samba (available via FTP (user: anonymous) in
11506 ftp://metalab.unc.edu/pub/Linux/system/network/samba ) for that.
11508 General information about how to connect Linux, Windows machines and
11509 Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
11511 If you want to compile the SMB support as a module ( = code which
11512 can be inserted in and removed from the running kernel whenever you
11513 want), say M here and read Documentation/modules.txt. The module
11514 will be called smbfs.o. Most people say N, however.
11517 CONFIG_SMB_NLS_DEFAULT
11518 Enabling this will make smbfs use nls translations by default. You
11519 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
11520 settings and you need to give the default nls for the SMB server as
11521 CONFIG_SMB_NLS_REMOTE.
11523 The nls settings can be changed at mount time, if your smbmount
11524 supports that, using the codepage and iocharset parameters.
11526 Currently no smbmount distributed with samba supports this, it is
11527 assumed future versions will. In the meantime you can get an
11528 unofficial patch for samba 2.0.7 from:
11529 http://www.hojdpunkten.ac.se/054/samba/index.html
11531 nls support setting
11532 CONFIG_SMB_NLS_REMOTE
11533 This setting allows you to specify a default value for which
11534 codepage the server uses. If this field is left blank no
11535 translations will be done by default. The local codepage/charset
11536 default to CONFIG_NLS_DEFAULT.
11538 The nls settings can be changed at mount time, if your smbmount
11539 supports that, using the codepage and iocharset parameters.
11541 Currently no smbmount distributed with samba supports this, it is
11542 assumed future versions will. In the meantime you can get an
11543 unofficial patch for samba 2.0.7 from:
11544 http://www.hojdpunkten.ac.se/054/samba/index.html
11546 Coda file system support (advanced network fs)
11548 Coda is an advanced network file system, similar to NFS in that it
11549 enables you to mount file systems of a remote server and access them
11550 with regular Unix commands as if they were sitting on your hard
11551 disk. Coda has several advantages over NFS: support for disconnected
11552 operation (e.g. for laptops), read/write server replication,
11553 security model for authentication and encryption, persistent client
11554 caches and write back caching.
11556 If you say Y here, your Linux box will be able to act as a Coda
11557 *client*. You will need user level code as well, both for the client
11558 and server. Servers are currently user level, i.e. they need no
11559 kernel support. Please read Documentation/filesystems/coda.txt and
11560 check out the Coda home page http://www.coda.cs.cmu.edu .
11562 If you want to compile the coda client support as a module ( = code
11563 which can be inserted in and removed from the running kernel
11564 whenever you want), say M here and read Documentation/modules.txt.
11565 The module will be called coda.o.
11567 NCP file system support (to mount NetWare volumes)
11569 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
11570 used by Novell NetWare clients to talk to file servers. It is to IPX
11571 what NFS is to TCP/IP, if that helps. Saying Y here allows you to
11572 mount NetWare file server volumes and to access them just like any
11573 other Unix directory. For details, please read the file
11574 Documentation/filesystems/ncpfs.txt in the kernel source and the
11575 IPX-HOWTO from http://www.linuxdoc.org/docs.html#howto .
11577 You do not have to say Y here if you want your Linux box to act as a
11578 file *server* for Novell NetWare clients.
11580 General information about how to connect Linux, Windows machines and
11581 Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
11583 If you want to compile this as a module ( = code which can be
11584 inserted in and removed from the running kernel whenever you want),
11585 say M here and read Documentation/modules.txt. The module will be
11586 called ncpfs.o. Say N unless you are connected to a Novell network.
11589 CONFIG_NCPFS_PACKET_SIGNING
11590 NCP allows packets to be signed for stronger security. If you want
11591 security, say Y. Normal users can leave it off. To be able to use
11592 packet signing you must use ncpfs > 2.0.12.
11594 Proprietary file locking
11595 CONFIG_NCPFS_IOCTL_LOCKING
11596 Allows locking of records on remote volumes. Say N unless you have
11597 special applications which are able to utilize this locking scheme.
11599 Clear remove/delete inhibit when needed
11600 CONFIG_NCPFS_STRONG
11601 Allows manipulation of files flagged as Delete or Rename Inhibit. To
11602 use this feature you must mount volumes with the ncpmount parameter
11603 "-s" (ncpfs-2.0.12 and newer). Say Y unless you are not mounting
11604 volumes with -f 444.
11606 Use NFS namespace when available
11607 CONFIG_NCPFS_NFS_NS
11608 Allows you to utilize NFS namespace on NetWare servers. It brings
11609 you case sensitive filenames. Say Y. You can disable it at
11610 mount-time with the `-N nfs' parameter of ncpmount.
11612 Use OS2/LONG namespace when available
11613 CONFIG_NCPFS_OS2_NS
11614 Allows you to utilize OS2/LONG namespace on NetWare servers.
11615 Filenames in this namespace are limited to 255 characters, they are
11616 case insensitive, and case in names is preserved. Say Y. You can
11617 disable it at mount time with the -N os2 parameter of ncpmount.
11619 Lowercase DOS filenames on LONG namespace volume
11620 CONFIG_NCPFS_SMALLDOS
11621 If you say Y here, every filename on a NetWare server volume using
11622 the OS2/LONG namespace and created under DOS or on a volume using
11623 DOS namespace will be converted to lowercase characters.
11624 Saying N here will give you these filenames in uppercase.
11626 This is only a cosmetic option since the OS2/LONG namespace is case
11627 insensitive. The only major reason for this option is backward
11628 compatibility when moving from DOS to OS2/LONG namespace support.
11629 Long filenames (created by Win95) will not be affected.
11631 This option does not solve the problem that filenames appear
11632 differently under Linux and under Windows, since Windows does an
11633 additional conversions on the client side. You can achieve similar
11634 effects by saying Y to "Allow using of Native Language Support"
11637 Allow mounting of volume subdirectories
11638 CONFIG_NCPFS_MOUNT_SUBDIR
11639 Allows you to mount not only whole servers or whole volumes, but
11640 also subdirectories from a volume. It can be used to reexport data
11641 and so on. There is no reason to say N, so Y is recommended unless
11642 you count every byte.
11644 To utilize this feature you must use ncpfs-2.0.12 or newer.
11646 NDS authentication support
11647 CONFIG_NCPFS_NDS_DOMAINS
11648 This allows storing NDS private keys in kernel space where they
11649 can be used to authenticate another server as interserver NDS
11650 accesses need it. You must use ncpfs-2.0.12.1 or newer to utilize
11651 this feature. Say Y if you are using NDS connections to NetWare
11652 servers. Do not say Y if security is primary for you because root
11653 can read your session key (from /proc/kcore).
11655 Allow using of Native Language Support
11657 Allows you to use codepages and I/O charsets for file name
11658 translation between the server file system and input/output. This
11659 may be useful, if you want to access the server with other operating
11660 systems, e.g. Windows 95. See also NLS for more Information.
11662 To select codepages and I/O charsets use ncpfs-2.2.0.13 or newer.
11664 Symbolic links and mode permission bits
11665 CONFIG_NCPFS_EXTRAS
11666 This enables the use of symbolic links and an execute permission
11667 bit on NCPFS. The file server need not have long name space or NFS
11668 name space loaded for these to work.
11670 To use the new attributes, it is recommended to use the flags
11671 '-f 600 -d 755' on the ncpmount command line.
11673 nls default codepage
11675 The default NLS used when mounting filesystem. Currently, the valid
11677 big5, cp437, cp737, cp775, cp850, cp852, cp855, cp857, cp860, cp861,
11678 cp862, cp863, cp864, cp865, cp866, cp869, cp874, cp932, cp936,
11679 cp949, cp950, euc-jp, euc-kr, gb2312, iso8859-1, iso8859-2, iso8859-3,
11680 iso8859-4, iso8859-5, iso8859-6, iso8859-7, iso8859-8, iso8859-9,
11681 iso8859-14, iso8859-15, koi8-r, sjis
11682 If you specify a wrong value, it will use the built-in NLS; compatible
11685 If unsure, specify it as "iso8859-1".
11688 CONFIG_NLS_CODEPAGE_437
11689 The Microsoft FAT file system family can deal with filenames in
11690 native language character sets. These character sets are stored
11691 in so-called DOS codepages. You need to include the appropriate
11692 codepage if you want to be able to read/write these filenames on
11693 DOS/Windows partitions correctly. This does apply to the filenames
11694 only, not to the file contents. You can include several codepages;
11695 say Y here if you want to include the DOS codepage that is used in
11696 the United States and parts of Canada. This is recommended.
11699 CONFIG_NLS_CODEPAGE_737
11700 The Microsoft FAT file system family can deal with filenames in
11701 native language character sets. These character sets are stored
11702 in so-called DOS codepages. You need to include the appropriate
11703 codepage if you want to be able to read/write these filenames on
11704 DOS/Windows partitions correctly. This does apply to the filenames
11705 only, not to the file contents. You can include several codepages;
11706 say Y here if you want to include the DOS codepage that is used for
11707 Greek. If unsure, say N.
11710 CONFIG_NLS_CODEPAGE_775
11711 The Microsoft FAT file system family can deal with filenames in
11712 native language character sets. These character sets are stored
11713 in so-called DOS codepages. You need to include the appropriate
11714 codepage if you want to be able to read/write these filenames on
11715 DOS/Windows partitions correctly. This does apply to the filenames
11716 only, not to the file contents. You can include several codepages;
11717 say Y here if you want to include the DOS codepage that is used
11718 for the Baltic Rim Languages. If unsure, say N.
11721 CONFIG_NLS_CODEPAGE_850
11722 The Microsoft FAT file system family can deal with filenames in
11723 native language character sets. These character sets are stored in
11724 so-called DOS codepages. You need to include the appropriate
11725 codepage if you want to be able to read/write these filenames on
11726 DOS/Windows partitions correctly. This does apply to the filenames
11727 only, not to the file contents. You can include several codepages;
11728 say Y here if you want to include the DOS codepage that is used for
11729 much of Europe -- United Kingdom, Germany, Spain, Italy, and [add
11730 more countries here]. It has some characters useful to many European
11731 languages that are not part of the US codepage 437.
11736 CONFIG_NLS_CODEPAGE_852
11737 The Microsoft FAT file system family can deal with filenames in
11738 native language character sets. These character sets are stored in
11739 so-called DOS codepages. You need to include the appropriate
11740 codepage if you want to be able to read/write these filenames on
11741 DOS/Windows partitions correctly. This does apply to the filenames
11742 only, not to the file contents. You can include several codepages;
11743 say Y here if you want to include the Latin 2 codepage used by DOS
11744 for much of Central and Eastern Europe. It has all the required
11745 characters for these languages: Albanian, Croatian, Czech, English,
11746 Finnish, Hungarian, Irish, German, Polish, Romanian, Serbian (Latin
11747 transcription), Slovak, Slovenian, and Sorbian.
11750 CONFIG_NLS_CODEPAGE_855
11751 The Microsoft FAT file system family can deal with filenames in
11752 native language character sets. These character sets are stored in
11753 so-called DOS codepages. You need to include the appropriate
11754 codepage if you want to be able to read/write these filenames on
11755 DOS/Windows partitions correctly. This does apply to the filenames
11756 only, not to the file contents. You can include several codepages;
11757 say Y here if you want to include the DOS codepage for Cyrillic.
11760 CONFIG_NLS_CODEPAGE_857
11761 The Microsoft FAT file system family can deal with filenames in
11762 native language character sets. These character sets are stored in
11763 so-called DOS codepages. You need to include the appropriate
11764 codepage if you want to be able to read/write these filenames on
11765 DOS/Windows partitions correctly. This does apply to the filenames
11766 only, not to the file contents. You can include several codepages;
11767 say Y here if you want to include the DOS codepage for Turkish.
11770 CONFIG_NLS_CODEPAGE_860
11771 The Microsoft FAT file system family can deal with filenames in
11772 native language character sets. These character sets are stored in
11773 so-called DOS codepages. You need to include the appropriate
11774 codepage if you want to be able to read/write these filenames on
11775 DOS/Windows partitions correctly. This does apply to the filenames
11776 only, not to the file contents. You can include several codepages;
11777 say Y here if you want to include the DOS codepage for Portuguese.
11780 CONFIG_NLS_CODEPAGE_861
11781 The Microsoft FAT file system family can deal with filenames in
11782 native language character sets. These character sets are stored in
11783 so-called DOS codepages. You need to include the appropriate
11784 codepage if you want to be able to read/write these filenames on
11785 DOS/Windows partitions correctly. This does apply to the filenames
11786 only, not to the file contents. You can include several codepages;
11787 say Y here if you want to include the DOS codepage for Icelandic.
11790 CONFIG_NLS_CODEPAGE_862
11791 The Microsoft FAT file system family can deal with filenames in
11792 native language character sets. These character sets are stored in
11793 so-called DOS codepages. You need to include the appropriate
11794 codepage if you want to be able to read/write these filenames on
11795 DOS/Windows partitions correctly. This does apply to the filenames
11796 only, not to the file contents. You can include several codepages;
11797 say Y here if you want to include the DOS codepage for Hebrew.
11800 CONFIG_NLS_CODEPAGE_863
11801 The Microsoft FAT file system family can deal with filenames in
11802 native language character sets. These character sets are stored in
11803 so-called DOS codepages. You need to include the appropriate
11804 codepage if you want to be able to read/write these filenames on
11805 DOS/Windows partitions correctly. This does apply to the filenames
11806 only, not to the file contents. You can include several codepages;
11807 say Y here if you want to include the DOS codepage for Canadian
11811 CONFIG_NLS_CODEPAGE_864
11812 The Microsoft FAT file system family can deal with filenames in
11813 native language character sets. These character sets are stored in
11814 so-called DOS codepages. You need to include the appropriate
11815 codepage if you want to be able to read/write these filenames on
11816 DOS/Windows partitions correctly. This does apply to the filenames
11817 only, not to the file contents. You can include several codepages;
11818 say Y here if you want to include the DOS codepage for Arabic.
11821 CONFIG_NLS_CODEPAGE_865
11822 The Microsoft FAT file system family can deal with filenames in
11823 native language character sets. These character sets are stored in
11824 so-called DOS codepages. You need to include the appropriate
11825 codepage if you want to be able to read/write these filenames on
11826 DOS/Windows partitions correctly. This does apply to the filenames
11827 only, not to the file contents. You can include several codepages;
11828 say Y here if you want to include the DOS codepage for the Nordic
11829 European countries.
11832 CONFIG_NLS_CODEPAGE_866
11833 The Microsoft FAT file system family can deal with filenames in
11834 native language character sets. These character sets are stored in
11835 so-called DOS codepages. You need to include the appropriate
11836 codepage if you want to be able to read/write these filenames on
11837 DOS/Windows partitions correctly. This does apply to the filenames
11838 only, not to the file contents. You can include several codepages;
11839 say Y here if you want to include the DOS codepage for
11843 CONFIG_NLS_CODEPAGE_869
11844 The Microsoft FAT file system family can deal with filenames in
11845 native language character sets. These character sets are stored in
11846 so-called DOS codepages. You need to include the appropriate
11847 codepage if you want to be able to read/write these filenames on
11848 DOS/Windows partitions correctly. This does apply to the filenames
11849 only, not to the file contents. You can include several codepages;
11850 say Y here if you want to include the DOS codepage for Greek.
11853 CONFIG_NLS_CODEPAGE_874
11854 The Microsoft FAT file system family can deal with filenames in
11855 native language character sets. These character sets are stored in
11856 so-called DOS codepages. You need to include the appropriate
11857 codepage if you want to be able to read/write these filenames on
11858 DOS/Windows partitions correctly. This does apply to the filenames
11859 only, not to the file contents. You can include several codepages;
11860 say Y here if you want to include the DOS codepage for Thai.
11863 CONFIG_NLS_CODEPAGE_932
11864 The Microsoft fat filesystem family can deal with filenames in
11865 native language character sets. These character sets are stored in
11866 so-called DOS codepages. You need to include the appropriate
11867 codepage if you want to be able to read/write these filenames on
11868 DOS/Windows partitions correctly. This does apply to the filenames
11869 only, not to the file contents. You can include several codepages;
11870 say Y here if you want to include the DOS codepage for Shift-JIS
11871 or EUC-JP. To use EUC-JP, you can use 'euc-jp' as mount option or
11872 NLS Default value during kernel configuration , instead of 'cp932'
11875 CONFIG_NLS_CODEPAGE_936
11876 The Microsoft fat filesystem family can deal with filenames in
11877 native language character sets. These character sets are stored in
11878 so-called DOS codepages. You need to include the appropriate
11879 codepage if you want to be able to read/write these filenames on
11880 DOS/Windows partitions correctly. This does apply to the filenames
11881 only, not to the file contents. You can include several codepages;
11882 say Y here if you want to include the DOS codepage for Simplified
11886 CONFIG_NLS_CODEPAGE_949
11887 The Microsoft fat filesystem family can deal with filenames in
11888 native language character sets. These character sets are stored in
11889 so-called DOS codepages. You need to include the appropriate
11890 codepage if you want to be able to read/write these filenames on
11891 DOS/Windows partitions correctly. This does apply to the filenames
11892 only, not to the file contents. You can include several codepages;
11893 say Y here if you want to include the DOS codepage for UHC.
11896 CONFIG_NLS_CODEPAGE_950
11897 The Microsoft fat filesystem family can deal with filenames in
11898 native language character sets. These character sets are stored in
11899 so-called DOS codepages. You need to include the appropriate
11900 codepage if you want to be able to read/write these filenames on
11901 DOS/Windows partitions correctly. This does apply to the filenames
11902 only, not to the file contents. You can include several codepages;
11903 say Y here if you want to include the DOS codepage for Traditional
11907 CONFIG_NLS_ISO8859_1
11908 If you want to display filenames with native language characters
11909 from the Microsoft FAT file system family or from JOLIET CDROMs
11910 correctly on the screen, you need to include the appropriate
11911 input/output character sets. Say Y here for the Latin 1 character
11912 set, which covers most West European languages such as Albanian,
11913 Catalan, Danish, Dutch, English, Faeroese, Finnish, French, German,
11914 Galician, Irish, Icelandic, Italian, Norwegian, Portuguese, Spanish,
11915 and Swedish. It is also the default for the US. If unsure, say Y.
11918 CONFIG_NLS_ISO8859_2
11919 If you want to display filenames with native language characters
11920 from the Microsoft FAT file system family or from JOLIET CDROMs
11921 correctly on the screen, you need to include the appropriate
11922 input/output character sets. Say Y here for the Latin 2 character
11923 set, which works for most Latin-written Slavic and Central European
11924 languages: Czech, German, Hungarian, Polish, Rumanian, Croatian,
11928 CONFIG_NLS_ISO8859_3
11929 If you want to display filenames with native language characters
11930 from the Microsoft FAT file system family or from JOLIET CDROMs
11931 correctly on the screen, you need to include the appropriate
11932 input/output character sets. Say Y here for the Latin 3 character
11933 set, which is popular with authors of Esperanto, Galician, Maltese,
11937 CONFIG_NLS_ISO8859_4
11938 If you want to display filenames with native language characters
11939 from the Microsoft FAT file system family or from JOLIET CDROMs
11940 correctly on the screen, you need to include the appropriate
11941 input/output character sets. Say Y here for the Latin 4 character
11942 set which introduces letters for Estonian, Latvian, and
11943 Lithuanian. It is an incomplete predecessor of Latin 6.
11946 CONFIG_NLS_ISO8859_5
11947 If you want to display filenames with native language characters
11948 from the Microsoft FAT file system family or from JOLIET CDROMs
11949 correctly on the screen, you need to include the appropriate
11950 input/output character sets. Say Y here for ISO8859-5, a Cyrillic
11951 character set with which you can type Bulgarian, Byelorussian,
11952 Macedonian, Russian, Serbian, and Ukrainian. Note that the charset
11953 KOI8-R is preferred in Russia.
11956 CONFIG_NLS_ISO8859_6
11957 If you want to display filenames with native language characters
11958 from the Microsoft FAT file system family or from JOLIET CDROMs
11959 correctly on the screen, you need to include the appropriate
11960 input/output character sets. Say Y here for ISO8859-6, the Arabic
11964 CONFIG_NLS_ISO8859_7
11965 If you want to display filenames with native language characters
11966 from the Microsoft FAT file system family or from JOLIET CDROMs
11967 correctly on the screen, you need to include the appropriate
11968 input/output character sets. Say Y here for ISO8859-7, the Modern
11969 Greek character set.
11972 CONFIG_NLS_ISO8859_8
11973 If you want to display filenames with native language characters
11974 from the Microsoft FAT file system family or from JOLIET CDROMs
11975 correctly on the screen, you need to include the appropriate
11976 input/output character sets. Say Y here for ISO8859-8, the Hebrew
11980 CONFIG_NLS_ISO8859_9
11981 If you want to display filenames with native language characters
11982 from the Microsoft FAT file system family or from JOLIET CDROMs
11983 correctly on the screen, you need to include the appropriate
11984 input/output character sets. Say Y here for the Latin 5 character
11985 set, and it replaces the rarely needed Icelandic letters in Latin 1
11986 with the Turkish ones. Useful in Turkey.
11989 CONFIG_NLS_ISO8859_10
11990 If you want to display filenames with native language characters
11991 from the Microsoft FAT file system family or from JOLIET CDROMs
11992 correctly on the screen, you need to include the appropriate
11993 input/output character sets. Say Y here for the Latin 6 character
11994 set, which adds the last Inuit (Greenlandic) and Sami (Lappish)
11995 letters that were missing in Latin 4 to cover the entire Nordic
11998 NLS ISO 8859-14 (Latin 8; Celtic)
11999 CONFIG_NLS_ISO8859_14
12000 If you want to display filenames with native language characters
12001 from the Microsoft FAT file system family or from JOLIET CDROMs
12002 correctly on the screen, you need to include the appropriate
12003 input/output character sets. Say Y here for the Latin 8 character
12004 set, which adds the last accented vowels for Welsh (aka Cymraeg)
12005 (and Manx Gaelic) hat were missing in Latin 1.
12006 http://linux.speech.cymru.org/ has further information.
12009 CONFIG_NLS_ISO8859_15
12010 If you want to display filenames with native language characters
12011 from the Microsoft FAT file system family or from JOLIET CDROMs
12012 correctly on the screen, you need to include the appropriate
12013 input/output character sets. Say Y here for the Latin 9 character
12014 set, which covers most West European languages such as Albanian,
12015 Catalan, Danish, Dutch, English, Estonian, Faeroese, Finnish,
12016 French, German, Galician, Irish, Icelandic, Italian, Norwegian,
12017 Portuguese, Spanish, and Swedish. Latin 9 is an update to
12018 Latin 1 (ISO 8859-1) that removes a handful of rarely used
12019 characters and instead adds support for Estonian, corrects the
12020 support for French and Finnish, and adds the new Euro character. If
12025 If you want to display filenames with native language characters
12026 from the Microsoft FAT file system family or from JOLIET CDROMs
12027 correctly on the screen, you need to include the appropriate
12028 input/output character sets. Say Y here for the preferred Russian
12033 If you say Y here, you will get support for terminal devices with
12034 display and keyboard devices. These are called "virtual" because you
12035 can run several virtual terminals (also called virtual consoles) on
12036 one physical terminal. This is rather useful, for example one
12037 virtual terminal can collect system messages and warnings, another
12038 one can be used for a text-mode user session, and a third could run
12039 an X session, all in parallel. Switching between virtual terminals
12040 is done with certain key combinations, usually Alt-<function key>.
12042 The setterm command ("man setterm") can be used to change the
12043 properties (such as colors or beeping) of a virtual terminal. The
12044 man page console_codes(4) ("man console_codes") contains the special
12045 character sequences that can be used to change those properties
12046 directly. The fonts used on virtual terminals can be changed with
12047 the setfont ("man setfont") command and the key bindings are defined
12048 with the loadkeys ("man loadkeys") command.
12050 You need at least one virtual terminal device in order to make use
12051 of your keyboard and monitor. Therefore, only people configuring an
12052 embedded system would want to say N here in order to save some
12053 memory; the only way to log into such a system is then via a serial
12054 or network connection.
12056 If unsure, say Y, or else you won't be able to do much with your new
12057 shiny Linux system :-)
12059 Support for console on virtual terminal
12061 The system console is the device which receives all kernel messages
12062 and warnings and which allows logins in single user mode. If you
12063 answer Y here, a virtual terminal (the device used to interact with
12064 a physical terminal) can be used as system console. This is the most
12065 common mode of operations, so you should say Y here unless you want
12066 the kernel messages be output only to a serial port (in which case
12067 you should say Y to "Console on serial port", below).
12069 If you do say Y here, by default the currently visible virtual
12070 terminal (/dev/tty0) will be used as system console. You can change
12071 that with a kernel command line option such as "console=tty3" which
12072 would use the third virtual terminal as system console. (Try "man
12073 bootparam" or see the documentation of your boot loader (lilo or
12074 loadlin) about how to pass options to the kernel at boot time.)
12078 Support for PowerMac keyboard
12079 CONFIG_MAC_KEYBOARD
12080 This option allows you to use an ADB keyboard attached to your
12081 machine. Note that this disables any other (ie. PS/2) keyboard
12082 support, even if your machine is physically capable of using both at
12085 If you use an ADB keyboard (4 pin connector), say Y here.
12086 If you use a PS/2 keyboard (6 pin connector), say N here.
12088 Standard/generic serial support
12090 This selects whether you want to include the driver for the standard
12091 serial ports. The standard answer is Y. People who might say N here
12092 are those that are setting up dedicated Ethernet WWW/FTP servers, or
12093 users that have one of the various bus mice instead of a serial
12094 mouse and don't intend to use their machine's standard serial port
12095 for anything. (Note that the Cyclades and Stallion multi serial port
12096 drivers do not need this driver built in for them to work.)
12098 If you want to compile this driver as a module, say M here and read
12099 Documentation/modules.txt. The module will be called serial.o.
12100 [WARNING: Do not compile this driver as a module if you are using
12101 non-standard serial ports, since the configuration information will
12102 be lost when the driver is unloaded. This limitation may be lifted
12105 BTW1: If you have a mouseman serial mouse which is not recognized by
12106 the X window system, try running gpm first.
12108 BTW2: If you intend to use a software modem (also called Winmodem)
12109 under Linux, forget it. These modems are crippled and require
12110 proprietary drivers which are only available under Windows.
12112 Most people will say Y or M here, so that they can use serial mice,
12113 modems and similar devices connecting to the standard serial ports.
12115 Support for console on serial port
12116 CONFIG_SERIAL_CONSOLE
12117 If you say Y here, it will be possible to use a serial port as the
12118 system console (the system console is the device which receives all
12119 kernel messages and warnings and which allows logins in single user
12120 mode). This could be useful if some terminal or printer is connected
12121 to that serial port.
12123 Even if you say Y here, the currently visible virtual console
12124 (/dev/tty0) will still be used as the system console by default, but
12125 you can alter that using a kernel command line option such as
12126 "console=ttyS1". (Try "man bootparam" or see the documentation of
12127 your boot loader (lilo or loadlin) about how to pass options to the
12128 kernel at boot time.)
12130 If you don't have a VGA card installed and you say Y here, the
12131 kernel will automatically use the first serial line, /dev/ttyS0, as
12136 Support for PowerMac serial ports
12138 If you have Macintosh style serial ports (8 pin mini-DIN), say Y
12139 here. If you also have regular serial ports and enable the driver
12140 for them, you can't currently use the serial console feature.
12142 Comtrol Rocketport support
12144 This is a driver for the Comtrol Rocketport cards which provide
12145 multiple serial ports. You would need something like this to connect
12146 more than two modems to your Linux box, for instance in order to
12147 become a dial-in server.
12149 If you want to compile this driver as a module, say M here and read
12150 Documentation/modules.txt. The module will be called rocket.o.
12152 Digiboard Intelligent async support
12154 This is a driver for Digi International's Xx, Xeve, and Xem series
12155 of cards which provide multiple serial ports. You would need
12156 something like this to connect more than two modems to your Linux
12157 box, for instance in order to become a dial-in server. This driver
12158 supports the original PC (ISA) boards as well as PCI, and EISA. If
12159 you have a card like this, say Y here and read the file
12160 Documentation/digiepca.txt.
12162 NOTE: There is another, separate driver for the Digiboard PC boards:
12163 "Digiboard PC/Xx Support" below. You should (and can) only select
12164 one of the two drivers.
12166 If you want to compile this driver as a module, say M here and read
12167 Documentation/modules.txt. The module will be called epca.o.
12169 Digiboard PC/Xx Support
12171 This is a driver for the Digiboard PC/Xe, PC/Xi, and PC/Xeve cards
12172 that give you many serial ports. You would need something like this
12173 to connect more than two modems to your Linux box, for instance in
12174 order to become a dial-in server. If you have a card like that, say
12175 Y here and read the file Documentation/digiboard.txt.
12177 If you want to compile this driver as a module, say M here and read
12178 Documentation/modules.txt. The module will be called pcxx.o.
12180 SDL RISCom/8 card support
12182 This is a driver for the SDL Communications RISCom/8 multiport card,
12183 which gives you many serial ports. You would need something like
12184 this to connect more than two modems to your Linux box, for instance
12185 in order to become a dial-in server. If you have a card like that,
12186 say Y here and read the file Documentation/riscom8.txt.
12188 Also it's possible to say M here and compile this driver as kernel
12189 loadable module; the module will be called riscom8.o.
12191 Computone IntelliPort Plus serial support
12193 This driver supports the entire family of Intelliport II/Plus
12194 controllers with the exception of the MicroChannel controllers and
12195 products previous to the Intelliport II. These are multiport cards,
12196 which give you many serial ports. You would need something like
12197 this to connect more than two modems to your Linux box, for
12198 instance in order to become a dial-in server. If you have a
12199 card like that, say Y here and read Documentation/computone.txt.
12201 If you want to compile this as a module ( = code which can be
12202 inserted in and removed from the running kernel whenever you want),
12203 say M here and read Documentation/modules.txt. You will get two
12204 modules called ip2.o and ip2main.o.
12206 Specialix IO8+ card support
12208 This is a driver for the Specialix IO8+ multiport card (both the
12209 ISA and the PCI version) which gives you many serial ports. You
12210 would need something like this to connect more than two modems to
12211 your Linux box, for instance in order to become a dial-in server.
12213 If you have a card like that, say Y here and read the file
12214 Documentation/specialix.txt. Also it's possible to say M here and
12215 compile this driver as kernel loadable module which will be called
12218 Specialix DTR/RTS pin is RTS
12219 CONFIG_SPECIALIX_RTSCTS
12220 The Specialix card can only support either RTS or DTR. If you say N
12221 here, the driver will use the pin as "DTR" when the tty is in
12222 software handshake mode. If you say Y here or hardware handshake is
12223 on, it will always be RTS. Read the file Documentation/specialix.txt
12224 for more information.
12226 Cyclades async mux support
12228 This is a driver for a card that gives you many serial ports. You
12229 would need something like this to connect more than two modems to
12230 your Linux box, for instance in order to become a dial-in server.
12231 For information about the Cyclades-Z card, read
12232 drivers/char/README.cycladesZ.
12234 As of 1.3.9x kernels, this driver's minor numbers start at 0 instead
12237 If you want to compile this as a module ( = code which can be
12238 inserted in and removed from the running kernel whenever you want),
12239 say M here and read Documentation/modules.txt. The module will be
12242 If you haven't heard about it, it's safe to say N.
12244 Cyclades-Z interrupt mode operation (EXPERIMENTAL)
12246 The Cyclades-Z family of multiport cards allows 2 (two) driver op
12247 modes: polling and interrupt. In polling mode, the driver will check
12248 the status of the Cyclades-Z ports every certain amount of time
12249 (which is called polling cycle and is configurable). In interrupt
12250 mode, it will use an interrupt line (IRQ) in order to check the
12251 status of the Cyclades-Z ports. The default op mode is polling. If
12254 Stallion multiport serial support
12256 Stallion cards give you many serial ports. You would need something
12257 like this to connect more than two modems to your Linux box, for
12258 instance in order to become a dial-in server. If you say Y here, you
12259 will be asked for your specific card model in the next questions.
12260 Make sure to read drivers/char/README.stallion in this case. If you
12261 have never heard about all this, it's safe to say N.
12263 Stallion EasyIO or EC8/32 support
12265 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
12266 card, then this is for you; say Y. Make sure to read
12267 Documentation/stallion.txt.
12269 If you want to compile this as a module ( = code which can be
12270 inserted in and removed from the running kernel whenever you want),
12271 say M here and read Documentation/modules.txt. The module will be
12274 Stallion EC8/64, ONboard, Brumby support
12276 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
12277 serial multiport card, say Y here. Make sure to read
12278 Documentation/stallion.txt.
12280 To compile it as a module ( = code which can be inserted in and
12281 removed from the running kernel whenever you want), say M here and
12282 read Documentation/modules.txt. The module will be called
12285 Microgate SyncLink adapter support
12287 Provides support for the SyncLink ISA and PCI
12288 multiprotocol serial adapters. These adapters
12289 support asynchronous and HDLC bit synchronous
12290 communication up to 10Mbps (PCI adapter).
12292 This driver can only be built as a module ( = code which can be
12293 inserted in and removed from the running kernel whenever you want).
12294 The module will be called synclink.o. If you want to do that, say M
12297 Synchronous HDLC line discipline support
12299 Allows synchronous HDLC communications with tty device drivers that
12300 support synchronous HDLC such as the Microgate SyncLink adapter.
12302 This driver can only be built as a module ( = code which can be
12303 inserted in and removed from the running kernel whenever you want).
12304 The module will be called n_hdlc.o. If you want to do that, say M
12307 Specialix SX (and SI) card support
12309 This is a driver for the SX and SI multiport serial cards.
12310 Please read the file Documentation/sx.txt for details.
12312 This driver can only be built as a module ( = code which can be
12313 inserted in and removed from the running kernel whenever you want).
12314 The module will be called sx.o. If you want to do that, say M here.
12316 Hayes ESP serial port support
12318 This is a driver which supports Hayes ESP serial ports. Both single
12319 port cards and multiport cards are supported. Make sure to read
12320 Documentation/hayes-esp.txt.
12322 To compile this driver as a module ( = code which can be inserted in
12323 and removed from the running kernel whenever you want), say M here
12324 and read Documentation/modules.txt. The module will be called esp.o.
12327 Moxa Intellio support
12328 CONFIG_MOXA_INTELLIO
12329 Say Y here if you have a Moxa Intellio multiport serial card.
12331 This driver can also be built as a module ( = code which can be
12332 inserted in and removed from the running kernel whenever you want).
12333 The module will be called moxa.o. If you want to do that, say M
12336 Moxa SmartIO support
12337 CONFIG_MOXA_SMARTIO
12338 Say Y here if you have a Moxa SmartIO multiport serial card.
12340 This driver can also be built as a module ( = code which can be
12341 inserted in and removed from the running kernel whenever you want).
12342 The module will be called mxser.o. If you want to do that, say M
12345 Multi-Tech multiport card support (EXPERIMENTAL)
12347 This is a driver for the Multi-Tech cards which provide several
12348 serial ports. The driver is experimental and can currently only be
12349 built as a module ( = code which can be inserted in and removed from
12350 the running kernel whenever you want). Please read
12351 Documentation/modules.txt. The module will be called isicom.o
12355 A pseudo terminal (PTY) is a software device consisting of two
12356 halves: a master and a slave. The slave device behaves identical to
12357 a physical terminal; the master device is used by a process to
12358 read data from and write data to the slave, thereby emulating a
12359 terminal. Typical programs for the master side are telnet servers
12362 Linux has traditionally used the BSD-like names /dev/ptyxx for
12363 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
12364 has a number of problems. The GNU C library glibc 2.1 and later,
12365 however, supports the Unix98 naming standard: in order to acquire a
12366 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
12367 terminal is then made available to the process and the pseudo
12368 terminal slave can be accessed as /dev/pts/<number>. What was
12369 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
12371 The entries in /dev/pts/ are created on the fly by a virtual
12372 file system; therefore, if you say Y here you should say Y to
12373 "/dev/pts file system for Unix98 PTYs" as well.
12375 If you want to say Y here, you need to have the C library glibc 2.1
12376 or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
12377 Read the instructions in Documentation/Changes pertaining to pseudo
12378 terminals. It's safe to say N.
12380 Maximum number of Unix98 PTYs in use (0-2048)
12381 CONFIG_UNIX98_PTY_COUNT
12382 The maximum number of Unix98 PTYs that can be used at any one time.
12383 The default is 256, and should be enough for desktop systems. Server
12384 machines which support incoming telnet/rlogin/ssh connections and/or
12385 serve several X terminals may want to increase this: every incoming
12386 connection and every xterm uses up one PTY.
12388 When not in use, each additional set of 256 PTYs occupy
12389 approximately 8 KB of kernel memory on 32-bit architectures.
12391 Parallel printer support
12393 If you intend to attach a printer to the parallel port of your Linux
12394 box (as opposed to using a serial printer; if the connector at the
12395 printer has 9 or 25 holes ["female"], then it's serial), say Y. Also
12396 read the Printing-HOWTO, available from
12397 http://www.linuxdoc.org/docs.html#howto .
12399 It is possible to share one parallel port among several devices
12400 (e.g. printer and ZIP drive) and it is safe to compile the
12401 corresponding drivers into the kernel. If you want to compile this
12402 driver as a module however ( = code which can be inserted in and
12403 removed from the running kernel whenever you want), say M here and
12404 read Documentation/modules.txt and Documentation/parport.txt. The
12405 module will be called lp.o.
12407 If you have several parallel ports, you can specify which ports to
12408 use with the "lp" kernel command line option. (Try "man bootparam"
12409 or see the documentation of your boot loader (lilo or loadlin) about
12410 how to pass options to the kernel at boot time.) The syntax of the
12411 "lp" command line option can be found in drivers/char/lp.c.
12413 If you have more than 3 printers, you need to increase the LP_NO
12416 Support for console on line printer
12418 If you want kernel messages to be printed out as they occur, you
12419 can have a console on the printer. This option adds support for
12420 doing that; to actually get it to happen you need to pass the
12421 option "console=lp0" to the kernel at boot time.
12423 Note that kernel messages can get lost if the printer is out of
12424 paper (or off, or unplugged, or too busy..), but this behaviour
12425 can be changed. See drivers/char/lp.c (do this at your own risk).
12429 Support for user-space parallel port device drivers
12431 Saying Y to this adds support for /dev/parport device nodes. This
12432 is needed for programs that want portable access to the parallel
12433 port, for instance deviceid (which displays Plug-and-Play device
12436 This is the parallel port equivalent of SCSI generic support (sg).
12437 It is safe to say N to this -- it is not needed for normal printing
12438 or parallel port CD-ROM/disk support.
12440 This support is also available as a module. If you want to compile
12441 it as a module, say M here and read Documentation/modules.txt. The
12442 module will be called ppdev.o.
12448 I2C (pronounce: I-square-C) is a slow serial bus protocol used in
12449 many micro controller applications and developed by Philips. SMBus,
12450 or System Management Bus is a subset of the I2C protocol. More
12451 information is contained in the directory Documentation/i2c/,
12452 especially in the file called "summary" there.
12454 Both I2C and SMBus are supported here. You will need this for
12455 hardware sensors support, and also for Video for Linux support.
12456 Specifically, if you want to use a BT848 based frame grabber/overlay
12457 boards under Linux, say Y here and also to "I2C bit-banging
12458 interfaces", below.
12460 If you want I2C support, you should say Y here and also to the
12461 specific driver for your bus adapter(s) below. If you say Y to
12462 "/proc file system" below, you will then get a /proc interface which
12463 is documented in Documentation/i2c/proc-interface.
12465 This I2C support is also available as a module. If you want to
12466 compile it as a module, say M here and read
12467 Documentation/modules.txt. The module will be called i2c-core.o.
12469 I2C bit-banging interfaces
12471 This allows you to use a range of I2C adapters called bit-banging
12472 adapters. Say Y if you own an I2C adapter belonging to this class
12473 and then say Y to the specific driver for you adapter below.
12475 This support is also available as a module. If you want to compile
12476 it as a module, say M here and read Documentation/modules.txt. The
12477 module will be called i2c-algo-bit.o.
12479 Philips style parallel port adapter
12480 CONFIG_I2C_PHILIPSPAR
12481 This supports parallel-port I2C adapters made by Philips. Say Y if
12482 you own such an adapter.
12484 This driver is also available as a module. If you want to compile
12485 it as a module, say M here and read Documentation/modules.txt. The
12486 module will be called i2c-philips-par.o.
12488 Note that if you want support for different parallel port devices,
12489 life will be much easier if you compile them all as modules.
12493 This supports parallel-port I2C adapters called ELV. Say Y if you
12494 own such an adapter.
12496 This driver is also available as a module. If you want to compile
12497 it as a module, say M here and read Documentation/modules.txt. The
12498 module will be called i2c-elv.o.
12500 Velleman K9000 adapter
12501 CONFIG_I2C_VELLEMAN
12502 This supports the Velleman K9000 parallel-port I2C adapter. Say Y if
12503 you own such an adapter.
12505 This driver is also available as a module. If you want to compile
12506 it as a module, say M here and read Documentation/modules.txt. The
12507 module will be called i2c-velleman.o.
12509 I2C PCF 8584 interfaces
12511 This allows you to use a range of I2C adapters called PCF adapters.
12512 Say Y if you own an I2C adapter belonging to this class and then say
12513 Y to the specific driver for you adapter below.
12515 This support is also available as a module. If you want to compile
12516 it as a module, say M here and read Documentation/modules.txt. The
12517 module will be called i2c-algo-pcf.o.
12521 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own such
12524 This driver is also available as a module. If you want to compile
12525 it as a module, say M here and read Documentation/modules.txt. The
12526 module will be called i2c-elektor.o.
12528 I2C device interface
12530 Say Y here to use i2c-* device files, usually found in the /dev
12531 directory on your system. They make it possible to have user-space
12532 programs use the I2C bus. Information on how to do this is contained
12533 in the file Documentation/i2c/dev-interface.
12535 This code is also available as a module. If you want to compile
12536 it as a module, say M here and read Documentation/modules.txt. The
12537 module will be called i2c-dev.o.
12541 Say Y here if your machine has a bus mouse as opposed to a serial
12542 mouse. Most people have a regular serial MouseSystem or
12543 Microsoft mouse (made by Logitech) that plugs into a COM port
12544 (rectangular with 9 or 25 pins). These people say N here. If you
12545 have something else, read the Busmouse-HOWTO, available from
12546 http://www.linuxdoc.org/docs.html#howto , and say Y here.
12548 If you have a laptop, you either have to check the documentation or
12549 experiment a bit to find out whether the trackball is a serial mouse
12550 or not; it's best to say Y here for you.
12552 This is the generic bus mouse driver code. If you have a bus mouse,
12553 you will have to say Y here and also to the specific driver for your
12556 This code is also available as a module ( = code which can be
12557 inserted in and removed from the running kernel whenever you want).
12558 The module will be called busmouse.o. If you want to compile it as a
12559 module, say M here and read Documentation/modules.txt.
12561 Mouse Support (not serial and bus mice)
12563 This is for machines with a mouse which is neither a serial nor a
12564 bus mouse. Examples are PS/2 mice (such as the track balls on some
12565 laptops) and some digitizer pads. Most people have a regular serial
12566 MouseSystem or Microsoft mouse (made by Logitech) that plugs into a
12567 COM port (rectangular with 9 or 25 pins). These people say N here.
12568 If you have something else, read the Busmouse-HOWTO, available from
12569 http://www.linuxdoc.org/docs.html#howto . This HOWTO contains
12570 information about all non-serial mice, not just bus mice.
12572 If you have a laptop, you either have to check the documentation or
12573 experiment a bit to find out whether the trackball is a serial mouse
12574 or not; it's best to say Y here for you.
12576 Note that the answer to this question won't directly affect the
12577 kernel: saying N will just cause this configure script to skip all
12578 the questions about non-serial mice. If unsure, say Y.
12580 Logitech busmouse support
12581 CONFIG_LOGIBUSMOUSE
12582 Logitech mouse connected to a proprietary interface card. It's
12583 generally a round connector with 9 pins. Note that the newer mice
12584 made by Logitech don't use the Logitech protocol anymore; for those,
12585 you don't need this option. You want to read the Busmouse-HOWTO ,
12586 available from http://www.linuxdoc.org/docs.html#howto .
12588 If you want to compile this as a module ( = code which can be
12589 inserted in and removed from the running kernel whenever you want),
12590 say M here and read Documentation/modules.txt. The module will be
12591 called busmouse.o. If you are unsure, say N and read the HOWTO
12592 nevertheless: it will tell you what you have.
12594 PS/2 mouse (aka "auxiliary device") support
12596 The PS/2 mouse connects to a special mouse port that looks much like
12597 the keyboard port (small circular connector with 6 pins). This way,
12598 the mouse does not use any serial ports. This port can also be used
12599 for other input devices like light pens, tablets, keypads. Compaq,
12600 AST and IBM all use this as their mouse port on currently shipping
12601 machines. The trackballs of some laptops are PS/2 mice also. In
12602 particular, the C&T 82C710 mouse on TI Travelmates is a PS/2 mouse.
12604 Although PS/2 mice are not technically bus mice, they are explained
12605 in detail in the Busmouse-HOWTO, available from
12606 http://www.linuxdoc.org/docs.html#howto .
12608 When using a PS/2 mouse, you can get problems if you want to use the
12609 mouse both on the Linux console and under X. Using the "-R" option
12610 of the Linux mouse managing program gpm (available from
12611 ftp://metalab.unc.edu/pub/Linux/system/mouse ) solves this
12612 problem, or you can get the "mconv2" utility from the same location.
12614 C&T 82C710 mouse port support (as on TI Travelmate)
12615 CONFIG_82C710_MOUSE
12616 This is a certain kind of PS/2 mouse used on the TI Travelmate. If
12617 you are unsure, try first to say N here and come back if the mouse
12618 doesn't work. Read the Busmouse-HOWTO, available from
12619 http://www.linuxdoc.org/docs.html#howto .
12621 PC110 digitizer pad support
12623 This drives the digitizer pad on the IBM PC110 palmtop. It can turn
12624 the digitizer pad into a PS/2 mouse emulation with tap gestures or
12625 into an absolute pad.
12627 If you want to compile this as a module ( = code which can be
12628 inserted in and removed from the running kernel whenever you want),
12629 say M here and read Documentation/modules.txt. The module will be
12632 Microsoft busmouse support
12634 These animals (also called Inport mice) are connected to an
12635 expansion board using a round connector with 9 pins. If this is what
12636 you have, say Y and read the Busmouse-HOWTO, available from
12637 http://www.linuxdoc.org/docs.html#howto .
12639 If you are unsure, say N and read the HOWTO nevertheless: it will
12640 tell you what you have. Also be aware that several vendors talk
12641 about 'Microsoft busmouse' and actually mean PS/2 busmouse -- so
12642 count the pins on the connector.
12644 If you want to compile this as a module ( = code which can be
12645 inserted in and removed from the running kernel whenever you want),
12646 say M here and read Documentation/modules.txt. The module will be
12647 called msbusmouse.o.
12649 Apple Desktop Bus mouse support
12651 Say Y here if you have this type of bus mouse (4 pin connector) as
12652 is common on Macintoshes. You may want to read the Busmouse-HOWTO,
12653 available from http://www.linuxdoc.org/docs.html#howto .
12655 If you want to compile this as a module ( = code which can be
12656 inserted in and removed from the running kernel whenever you want),
12657 say M here and read Documentation/modules.txt. The module will be
12660 ATIXL busmouse support
12661 CONFIG_ATIXL_BUSMOUSE
12662 This is a rare type of busmouse that is connected to the back of an
12663 ATI video card. Say Y if you have one of those. Note however that
12664 most mice by ATI are actually Microsoft busmice; you should say Y to
12665 "Microsoft busmouse support" above if you have one of those. Read
12666 the Busmouse-HOWTO, available from
12667 http://www.linuxdoc.org/docs.html#howto .
12669 If you want to compile this as a module ( = code which can be
12670 inserted in and removed from the running kernel whenever you want),
12671 say M here and read Documentation/modules.txt. The module will be
12672 called atixlmouse.o.
12674 If you are unsure, say N and read the HOWTO nevertheless: it will
12675 tell you what you have.
12677 QIC-02 tape support
12679 If you have a non-SCSI tape drive like that, say Y. Or, if you want
12680 to compile this driver as a module ( = code which can be inserted in
12681 and removed from the running kernel whenever you want), say M here
12682 and read Documentation/modules.txt. The module will be called
12685 Do you want runtime configuration for QIC-02
12686 CONFIG_QIC02_DYNCONF
12687 You can either configure this driver once and for all by editing a
12688 header file (include/linux/tpqic02.h), in which case you should
12689 say N, or you can fetch a program via anonymous FTP which is able
12690 to configure this driver during runtime. The program to do this is
12691 called 'qic02conf' and it is part of the tpqic02-support-X.Y.tar.gz
12694 If you want to use the qic02conf program, say Y.
12696 Floppy tape drive (QIC-80/40/3010/3020/TR-1/TR-2/TR-3) support
12698 If you have a tape drive that is connected to your floppy
12699 controller, say Y here.
12701 Some tape drives (like the Seagate "Tape Store 3200" or the Iomega
12702 "Ditto 3200" or the Exabyte "Eagle TR-3") come with a "high speed"
12703 controller of their own. These drives (and their companion
12704 controllers) are also supported if you say Y here.
12706 If you have a special controller (such as the CMS FC-10, FC-20,
12707 Mountain Mach-II, or any controller that is based on the Intel 82078
12708 FDC like the high speed controllers by Seagate and Exabyte and
12709 Iomega's "Ditto Dash") you must configure it by selecting the
12710 appropriate entries from the "Floppy tape controllers" sub-menu
12711 below and possibly modify the default values for the IRQ and DMA
12712 channel and the IO base in ftape's configuration menu.
12714 If you want to use your floppy tape drive on a PCI-bus based system,
12715 please read the file drivers/char/ftape/README.PCI.
12717 The ftape kernel driver is also available as a runtime loadable
12718 module ( = code which can be inserted in and removed from the
12719 running kernel whenever you want). If you want to compile it as a
12720 module, say M here and read Documentation/modules.txt. The module
12721 will be called ftape.o.
12723 Note that the Ftape-HOWTO is out of date (sorry) and documents the
12724 older version 2.08 of this software but still contains useful
12725 information. There is a web page with more recent documentation at
12726 http://www.math1.rwth-aachen.de/~heine/ftape/ . This page
12727 always contains the latest release of the ftape driver and useful
12728 information (backup software, ftape related patches and
12729 documentation, FAQ). Note that the file system interface has changed
12730 quite a bit compared to previous versions of ftape. Please read
12731 Documentation/ftape.txt.
12733 The file system interface for ftape
12735 Normally, you want to say Y or M. DON'T say N here or you
12736 WON'T BE ABLE TO USE YOUR FLOPPY TAPE DRIVE.
12738 The ftape module itself no longer contains the routines necessary
12739 to interface with the kernel VFS layer (i.e. to actually write data
12740 to and read data from the tape drive). Instead the file system
12741 interface (i.e. the hardware independent part of the driver) has
12742 been moved to a separate module.
12744 If you say M zftape will be compiled as a runtime loadable
12745 module ( = code which can be inserted in and removed from the
12746 running kernel whenever you want). In this case you should read
12747 Documentation/modules.txt. The module will be called zftape.o.
12749 Regardless of whether you say Y or M here, an additional runtime
12750 loadable module called `zft-compressor.o' which contains code to
12751 support user transparent on-the-fly compression based on Ross
12752 William's lzrw3 algorithm will be produced. If you have enabled the
12753 kernel module loader (i.e. have said Y to "Kernel module loader
12754 support", above) then `zft-compressor.o' will be loaded
12755 automatically by zftape when needed.
12757 Despite its name, zftape does NOT use compression by default. The
12758 file Documentation/ftape.txt contains a short description of the
12759 most important changes in the file system interface compared to
12760 previous versions of ftape. The ftape home page
12761 http://www-math.math.rwth-aachen.de/~LBFM/claus/ftape/ contains
12762 further information.
12764 IMPORTANT NOTE: zftape can read archives created by previous
12765 versions of ftape and provide file mark support (i.e. fast skipping
12766 between tape archives) but previous version of ftape will lack file
12767 mark support when reading archives produced by zftape.
12769 Default block size for zftape
12770 CONFIG_ZFT_DFLT_BLK_SZ
12771 If unsure leave this at its default value, i.e. 10240. Note that
12772 you specify only the default block size here. The block size can be
12773 changed at run time using the MTSETBLK tape operation with the
12774 MTIOCTOP ioctl (i.e. with "mt -f /dev/qft0 setblk #BLKSZ" from the
12775 shell command line).
12777 The probably most striking difference between zftape and previous
12778 versions of ftape is the fact that all data must be written or read
12779 in multiples of a fixed block size. The block size defaults to
12780 10240 which is what GNU tar uses. The values for the block size
12781 should be either 1 or multiples of 1024 up to a maximum value of
12782 63488 (i.e. 62 K). If you specify `1' then zftape's builtin
12783 compression will be disabled.
12785 Reasonable values are `10240' (GNU tar's default block size),
12786 `5120' (afio's default block size), `32768' (default block size some
12787 backup programs assume for SCSI tape drives) or `1' (no restriction
12788 on block size, but disables builtin compression).
12790 Number of DMA buffers
12791 CONFIG_FT_NR_BUFFERS
12792 Please leave this at `3' unless you REALLY know what you are doing.
12793 It is not necessary to change this value. Values below 3 make the
12794 proper use of ftape impossible, values greater than 3 are a waste of
12795 memory. You can change the amount of DMA memory used by ftape at
12796 runtime with "mt -f /dev/qft0 setdrvbuffer #NUMBUFFERS". Each buffer
12797 wastes 32 KB of memory. Please note that this memory cannot be
12800 Procfs entry for ftape
12802 Optional. Saying Y will result in creation of a directory
12803 `/proc/ftape' under the /proc file system. The files can be viewed
12804 with your favorite pager (i.e. use "more /proc/ftape/history" or
12805 "less /proc/ftape/history" or simply "cat /proc/ftape/history"). The
12806 file will contain some status information about the inserted
12807 cartridge, the kernel driver, your tape drive, the floppy disk
12808 controller and the error history for the most recent use of the
12809 kernel driver. Saying Y will enlarge the size of the ftape driver
12810 by approximately 2 KB.
12812 WARNING: When compiling ftape as a module (i.e. saying M to "Floppy
12813 tape drive") it is dangerous to use ftape's /proc file system
12814 interface. Accessing `/proc/ftape' while the module is unloaded will
12815 result in a kernel Oops. This cannot be fixed from inside ftape.
12817 Controlling the amount of debugging output of ftape
12818 CONFIG_FT_NORMAL_DEBUG
12819 This option controls the amount of debugging output the ftape driver
12820 is ABLE to produce; it does not increase or diminish the debugging
12821 level itself. If unsure, leave this at its default setting,
12822 i.e. choose "Normal".
12824 Ftape can print lots of debugging messages to the system console
12825 resp. kernel log files. Reducing the amount of possible debugging
12826 output reduces the size of the kernel module by some KB, so it might
12827 be a good idea to use "None" for emergency boot floppies.
12829 If you want to save memory then the following strategy is
12830 recommended: leave this option at its default setting "Normal" until
12831 you know that the driver works as expected, afterwards reconfigure
12832 the kernel, this time specifying "Reduced" or "None" and recompile
12833 and install the kernel as usual. Note that choosing "Excessive"
12834 debugging output does not increase the amount of debugging output
12835 printed to the console but only makes it possible to produce
12836 "Excessive" debugging output.
12838 Please read Documentation/ftape.txt for a short description
12839 how to control the amount of debugging output.
12841 The floppy drive controller for ftape
12843 Only change this setting if you have a special controller. If you
12844 didn't plug any add-on card into your computer system but just
12845 plugged the floppy tape cable into the already existing floppy drive
12846 controller then you don't want to change the default setting,
12847 i.e. choose "Standard".
12849 Choose "MACH-2" if you have a Mountain Mach-2 controller.
12850 Choose "FC-10/FC-20" if you have a Colorado FC-10 or FC-20
12852 Choose "Alt/82078" if you have another controller that is located at
12853 an IO base address different from the standard floppy drive
12854 controller's base address of `0x3f0', or uses an IRQ (interrupt)
12855 channel different from `6', or a DMA channel different from
12856 `2'. This is necessary for any controller card that is based on
12857 Intel's 82078 FDC such as Seagate's, Exabyte's and Iomega's "high
12858 speed" controllers.
12860 If you choose something other than "Standard" then please make
12861 sure that the settings for the IO base address and the IRQ and DMA
12862 channel in the configuration menus below are correct. Use the manual
12863 of your tape drive to determine the correct settings!
12865 If you are already successfully using your tape drive with another
12866 operating system then you definitely should use the same settings
12867 for the IO base, the IRQ and DMA channel that have proven to work
12868 with that other OS.
12870 Note that this menu lets you specify only the default setting for
12871 the hardware setup. The hardware configuration can be changed at
12872 boot time (when ftape is compiled into the kernel, i.e. if you
12873 have said Y to "Floppy tape drive") or module load time (i.e. if you
12874 have said M to "Floppy tape drive").
12876 Please read also the file Documentation/ftape.txt which
12877 contains a short description of the parameters that can be set at
12878 boot or load time. If you want to use your floppy tape drive on a
12879 PCI-bus based system, please read the file
12880 drivers/char/ftape/README.PCI.
12882 IO base of the floppy disk controller used with Ftape
12884 You don't need to specify a value if the following default
12885 settings for the base IO address are correct:
12886 <<< MACH-2 : 0x1E0 >>>
12887 <<< FC-10/FC-20: 0x180 >>>
12888 <<< Secondary : 0x370 >>>
12889 Secondary refers to a secondary FDC controller like the "high speed"
12890 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
12891 Please make sure that the setting for the IO base address
12892 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
12893 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
12894 successfully using the tape drive with another operating system then
12895 you definitely should use the same settings for the IO base that has
12896 proven to work with that other OS.
12898 Note that this menu lets you specify only the default setting for
12899 the IO base. The hardware configuration can be changed at boot time
12900 (when ftape is compiled into the kernel, i.e. if you specified Y to
12901 "Floppy tape drive") or module load time (i.e. if you have said M to
12902 "Floppy tape drive").
12904 Please read also the file Documentation/ftape.txt which contains a
12905 short description of the parameters that can be set at boot or load
12908 IRQ channel for the floppy disk controller used with Ftape
12910 You don't need to specify a value if the following default
12911 settings for the interrupt channel are correct:
12913 <<< FC-10/FC-20: 9 >>>
12914 <<< Secondary : 6 >>>
12915 Secondary refers to secondary a FDC controller like the "high speed"
12916 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
12917 Please make sure that the setting for the IO base address
12918 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
12919 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
12920 successfully using the tape drive with another operating system then
12921 you definitely should use the same settings for the IO base that has
12922 proven to work with that other OS.
12924 Note that this menu lets you specify only the default setting for
12925 the IRQ channel. The hardware configuration can be changed at boot
12926 time (when ftape is compiled into the kernel, i.e. if you said Y to
12927 "Floppy tape drive") or module load time (i.e. if you said M to
12928 "Floppy tape drive").
12930 Please read also the file Documentation/ftape.txt which contains a
12931 short description of the parameters that can be set at boot or load
12934 DMA channel for the floppy disk controller used with Ftape
12936 You don't need to specify a value if the following default
12937 settings for the DMA channel are correct:
12939 <<< FC-10/FC-20: 3 >>>
12940 <<< Secondary : 2 >>>
12941 Secondary refers to a secondary FDC controller like the "high speed"
12942 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
12943 Please make sure that the setting for the IO base address
12944 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
12945 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
12946 successfully using the tape drive with another operating system then
12947 you definitely should use the same settings for the IO base that has
12948 proven to work with that other OS.
12950 Note that this menu lets you specify only the default setting for
12951 the DMA channel. The hardware configuration can be changed at boot
12952 time (when ftape is compiled into the kernel, i.e. if you said Y to
12953 "Floppy tape drive") or module load time (i.e. if you said M to
12954 "Floppy tape drive").
12956 Please read also the file Documentation/ftape.txt which contains a
12957 short description of the parameters that can be set at boot or load
12960 FDC FIFO Threshold before requesting DMA service
12962 Set the FIFO threshold of the FDC. If this is higher the DMA
12963 controller may serve the FDC after a higher latency time. If this is
12964 lower, fewer DMA transfers occur leading to less bus contention.
12965 You may try to tune this if ftape annoys you with "reduced data
12966 rate because of excessive overrun errors" messages. However, this
12967 doesn't seem to have too much effect.
12969 If unsure, don't touch the initial value, i.e. leave it at "8".
12971 FDC maximum data rate
12972 CONFIG_FT_FDC_MAX_RATE
12973 With some motherboard/FDC combinations ftape will not be able to
12974 run your FDC/tape drive combination at the highest available
12975 speed. If this is the case you'll encounter "reduced data rate
12976 because of excessive overrun errors" messages and lots of retries
12977 before ftape finally decides to reduce the data rate.
12979 In this case it might be desirable to tell ftape beforehand that
12980 it need not try to run the tape drive at the highest available
12981 speed. If unsure, leave this disabled, i.e. leave it at 2000
12984 Direct Rendering Manager (XFree86 DRI support)
12986 Kernel-level support for the Direct Rendering Infrastructure (DRI)
12987 introduced in XFree86 4.0. If you say Y here, you need to select
12988 the module that's right for your graphics card from the list below.
12989 These modules provide support for synchronization, security, and
12990 DMA transfers. Please see http://dri.sourceforge.net for more
12991 details. You should also select and configure AGP
12992 (/dev/agpgart) support.
12994 3dfx Banshee/Voodoo3+
12996 Choose this option if you have a 3dfx Banshee or Voodoo3 (or later),
12997 graphics card. If M is selected, the module will be called tdfx.o.
13001 Choose this option if you have a 3dlabs GMX 2000 graphics card.
13002 If M is selected, the module will be called gamma.o.
13006 Choose this option if you have an ATI Rage 128 graphics card. If M
13007 is selected, the module will be called r128.o. AGP support for
13008 this card is strongly suggested (unless you have a PCI version).
13012 Choose this option if you have an Intel I810 graphics card. If M is
13013 selected, the module will be called i810.o. AGP support is required
13014 for this driver to work.
13018 Choose this option if you have a Matrox g200 or g400 graphics card. If M
13019 is selected, the module will be called mga.o. AGP support is required
13020 for this driver to work.
13022 MTRR control and configuration
13024 On Intel P6 family processors (Pentium Pro, Pentium II and later)
13025 the Memory Type Range Registers (MTRRs) may be used to control
13026 processor access to memory ranges. This is most useful if you have
13027 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
13028 allows bus write transfers to be combined into a larger transfer
13029 before bursting over the PCI/AGP bus. This can increase performance
13030 of image write operations 2.5 times or more. Saying Y here creates a
13031 /proc/mtrr file which may be used to manipulate your processor's
13032 MTRRs. Typically the X server should use this.
13034 This code has a reasonably generic interface so that similar
13035 control registers on other processors can be easily supported
13038 The Cyrix 6x86, 6x86MX and M II processors have Address Range
13039 Registers (ARRs) which provide a similar functionality to MTRRs. For
13040 these, the ARRs are used to emulate the MTRRs.
13041 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
13042 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
13043 write-combining. All of these processors are supported by this code
13044 and it makes sense to say Y here if you have one of them.
13046 Saying Y here also fixes a problem with buggy SMP BIOSes which only
13047 set the MTRRs for the boot CPU and not for the secondary CPUs. This
13048 can lead to all sorts of problems, so it's good to say Y here.
13050 You can safely say Y even if your machine doesn't have MTRRs, you'll
13051 just add about 9 KB to your kernel.
13053 See Documentation/mtrr.txt for more information.
13055 Main CPU frequency, only for DEC alpha machine
13056 CONFIG_FT_ALPHA_CLOCK
13057 On some DEC Alpha machines the CPU clock frequency cannot be
13058 determined automatically, so you need to specify it here ONLY if
13059 running a DEC Alpha, otherwise this setting has no effect.
13061 Double Talk PC internal speech card support
13063 This driver is for the DoubleTalk PC, a speech synthesizer
13064 manufactured by RC Systems (http://www.rcsys.com/ ). It is also
13065 called the `internal DoubleTalk'. If you want to compile this as a
13066 module ( = code which can be inserted in and removed from the
13067 running kernel whenever you want), say M here and read
13068 Documentation/modules.txt. The module will be called dtlk.o.
13070 Siemens R3964 serial protocol support
13072 This driver allows synchronous communication with devices using the
13073 Siemens R3964 packet protocol. Unless you are dealing with special
13074 hardware like PLCs, you are unlikely to need this.
13076 To compile this driver as a module ( = code which can be inserted in
13077 and removed from the running kernel whenever you want), say M here
13078 and read Documentation/modules.txt. The module will be called
13083 Applicom intelligent fieldbus card support
13085 This driver provides the kernel-side support for the intelligent
13086 fieldbus cards made by Applicom International. More information
13087 about these cards can be found on the WWW at the address
13088 http://www.applicom-int.com/ , or by email from David Woodhouse
13089 <dwmw2@infradead.org>.
13091 To compile this driver as a module ( = code which can be inserted in
13092 and removed from the running kernel whenever you want), say M here
13093 and read Documentation/modules.txt. The module will be called
13098 Intel Random Number Generator support
13100 This driver provides kernel-side support for the Random Number
13101 Generator hardware found on Intel i8xx-based motherboards.
13103 Both a character driver, used to read() entropy data, and a timer
13104 function which automatically adds entropy directly into the
13105 kernel pool, are exported by this driver.
13107 To compile this driver as a module ( = code which can be inserted in
13108 and removed from the running kernel whenever you want), say M here
13109 and read Documentation/modules.txt. The module will be called
13114 Power Management support
13116 "Power Management" means that parts of your computer are shut
13117 off or put into a power conserving "sleep" mode if they are not
13118 being used. There are two competing standards for doing this: APM
13119 and ACPI. If you want to use either one, say Y here and then also to
13120 the requisite support below.
13122 Power Management is most important for battery powered laptop
13123 computers; if you have a laptop, check out the Linux Laptop home
13125 http://www.cs.utexas.edu/users/kharker/linux-laptop/ and the Battery
13126 Powered Linux mini-HOWTO, available from
13127 http://www.linuxdoc.org/docs.html#howto .
13129 Note that, even if you say N here, Linux on the x86 architecture
13130 will issue the hlt instruction if nothing is to be done, thereby
13131 sending the processor to sleep and saving power.
13135 The Advanced Configuration and Power Interface is a standard
13136 designed to allow the operating system more control over power
13137 management issues, such as suspending a computer in a low power
13138 consumption state after a certain time of inaction. It aims to be
13139 an improved version of APM (see below). ACPI has to be
13140 supported by the motherboard. You can read more about the standard
13141 at http://www.teleport.com/~acpi/ .
13143 If your computer supports ACPI and you want to use it, say Y here.
13144 You will then need supporting software; for location and more
13145 information, please read Documentation/pm.txt and the Battery
13146 Powered Linux mini-HOWTO, available from
13147 http://www.linuxdoc.org/docs.html#howto .
13149 If you say Y here and also to "Advanced Power Management" (APM)
13150 below, then ACPI has precedence in the sense that, if your hardware
13151 supports ACPI, it will be used and APM won't.
13153 ACPI interpreter (EXPERIMENTAL)
13154 CONFIG_ACPI_INTERPRETER
13155 If you say Y here, an ACPI interpreter will be included in your
13156 kernel, eventually making the full range of ACPI features
13157 available on systems that support ACPI. Note, this option will
13158 enlarge your kernel by about 120K.
13160 The interpreter is currently experimental so only say Y if
13161 you know what you are doing.
13163 Enter S1 for sleep (EXPERIMENTAL)
13164 CONFIG_ACPI_S1_SLEEP
13165 If you say Y here, ACPI compliant devices can enter level 1 of ACPI
13166 saving power levels. Basically, this will let them enter sleep mode.
13168 Advanced Power Management BIOS support
13170 APM is a BIOS specification for saving power using several different
13171 techniques. This is mostly useful for battery powered laptops with
13172 APM compliant BIOSes. If you say Y here, the system time will be
13173 reset after a RESUME operation, the /proc/apm device will provide
13174 battery status information, and user-space programs will receive
13175 notification of APM "events" (e.g. battery status change).
13177 If you select "Y" here, you can disable actual use of the APM
13178 BIOS by passing the "apm=off" option to the kernel at boot time.
13180 Note that the APM support is almost completely disabled for
13181 machines with more than one CPU.
13183 In order to use APM, you will need supporting software. For location
13184 and more information, read Documentation/pm.txt and the Battery
13185 Powered Linux mini-HOWTO, available from
13186 http://www.linuxdoc.org/docs.html#howto .
13188 This driver does not spin down disk drives (see the hdparm(8)
13189 manpage ("man 8 hdparm") for that), and it doesn't turn off
13190 VESA-compliant "green" monitors.
13192 This driver does not support the TI 4000M TravelMate and the ACER
13193 486/DX4/75 because they don't have compliant BIOSes. Many "green"
13194 desktop machines also don't have compliant BIOSes, and this driver
13195 may cause those machines to panic during the boot phase.
13197 Generally, if you don't have a battery in your machine, there isn't
13198 much point in using this driver and you should say N. If you get
13199 random kernel OOPSes or reboots that don't seem to be related to
13200 anything, try disabling/enabling this option (or disabling/enabling
13203 Some other things you should try when experiencing seemingly random,
13206 1) make sure that you have enough swap space and that it is
13208 2) pass the "no-hlt" option to the kernel
13209 3) switch on floating point emulation in the kernel and pass
13210 the "no387" option to the kernel
13211 4) pass the "floppy=nodma" option to the kernel
13212 5) pass the "mem=4M" option to the kernel (thereby disabling
13213 all but the first 4 MB of RAM)
13214 6) make sure that the CPU is not over clocked.
13215 7) read the sig11 FAQ at http://www.bitwizard.nl/sig11/
13216 8) disable the cache from your BIOS settings
13217 9) install a fan for the video card or exchange video RAM
13218 10) install a better fan for the CPU
13219 11) exchange RAM chips
13220 12) exchange the motherboard.
13222 To compile this driver as a module ( = code which can be inserted in
13223 and removed from the running kernel whenever you want), say M here
13224 and read Documentation/modules.txt. The module will be called
13227 Ignore USER SUSPEND
13228 CONFIG_APM_IGNORE_USER_SUSPEND
13229 This option will ignore USER SUSPEND requests. On machines with a
13230 compliant APM BIOS, you want to say N. However, on the NEC Versa M
13231 series notebooks, it is necessary to say Y because of a BIOS bug.
13233 Enable APM at boot time
13234 CONFIG_APM_DO_ENABLE
13235 Enable APM features at boot time. From page 36 of the APM BIOS
13236 specification: "When disabled, the APM BIOS does not automatically
13237 power manage devices, enter the Standby State, enter the Suspend
13238 State, or take power saving steps in response to CPU Idle calls."
13239 This driver will make CPU Idle calls when Linux is idle (unless this
13240 feature is turned off -- see "Do CPU IDLE calls", below). This
13241 should always save battery power, but more complicated APM features
13242 will be dependent on your BIOS implementation. You may need to turn
13243 this option off if your computer hangs at boot time when using APM
13244 support, or if it beeps continuously instead of suspending. Turn
13245 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
13246 T400CDT. This is off by default since most machines do fine without
13250 CONFIG_APM_CPU_IDLE
13251 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
13252 On some machines, this can activate improved power savings, such as
13253 a slowed CPU clock rate, when the machine is idle. These idle calls
13254 are made after the idle loop has run for some length of time (e.g.,
13255 333 mS). On some machines, this will cause a hang at boot time or
13256 whenever the CPU becomes idle. (On machines with more than one CPU,
13257 this option does nothing.)
13259 Enable console blanking using APM
13260 CONFIG_APM_DISPLAY_BLANK
13261 Enable console blanking using the APM. Some laptops can use this to
13262 turn off the LCD backlight when the screen blanker of the Linux
13263 virtual console blanks the screen. Note that this is only used by
13264 the virtual console screen blanker, and won't turn off the backlight
13265 when using the X Window system. This also doesn't have anything to
13266 do with your VESA-compliant power-saving monitor. Further, this
13267 option doesn't work for all laptops -- it might not turn off your
13268 backlight at all, or it might print a lot of errors to the console,
13269 especially if you are using gpm.
13271 RTC stores time in GMT
13272 CONFIG_APM_RTC_IS_GMT
13273 Say Y here if your RTC (Real Time Clock a.k.a. hardware clock)
13274 stores the time in GMT (Greenwich Mean Time). Say N if your RTC
13277 It is in fact recommended to store GMT in your RTC, because then you
13278 don't have to worry about daylight savings time changes. The only
13279 reason not to use GMT in your RTC is if you also run a broken OS
13280 that doesn't understand GMT.
13282 Allow interrupts during APM BIOS calls
13283 CONFIG_APM_ALLOW_INTS
13284 Normally we disable external interrupts while we are making calls to
13285 the APM BIOS as a measure to lessen the effects of a badly behaving
13286 BIOS implementation. The BIOS should reenable interrupts if it
13287 needs to. Unfortunately, some BIOSes do not -- especially those in
13288 many of the newer IBM Thinkpads. If you experience hangs when you
13289 suspend, try setting this to Y. Otherwise, say N.
13291 Use real mode APM BIOS call to power off
13292 CONFIG_APM_REAL_MODE_POWER_OFF
13293 Use real mode APM BIOS calls to switch off the computer. This is
13294 a work-around for a number of buggy BIOSes. Switch this option on if
13295 your computer crashes instead of powering off properly.
13297 Watchdog Timer Support
13299 If you say Y here (and to one of the following options) and create a
13300 character special file /dev/watchdog with major number 10 and minor
13301 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
13302 subsequently opening the file and then failing to write to it for
13303 longer than 1 minute will result in rebooting the machine. This
13304 could be useful for a networked machine that needs to come back
13305 online as fast as possible after a lock-up. There's both a watchdog
13306 implementation entirely in software (which can sometimes fail to
13307 reboot the machine) and a driver for hardware watchdog boards, which
13308 are more robust and can also keep track of the temperature inside
13309 your computer. For details, read Documentation/watchdog.txt in the
13312 The watchdog is usually used together with the watchdog daemon
13313 which is available via FTP (user: anonymous) from
13314 ftp://tsx-11.mit.edu/pub/linux/sources/sbin/ . This daemon can also
13315 monitor NFS connections and can reboot the machine when the process
13320 Disable watchdog shutdown on close
13321 CONFIG_WATCHDOG_NOWAYOUT
13322 The default watchdog behaviour (which you get if you say N here) is
13323 to stop the timer if the process managing it closes the file
13324 /dev/watchdog. It's always remotely possible that this process might
13325 get killed. If you say Y here, the watchdog cannot be stopped once
13326 it has been started.
13330 If you have a WDT500P or WDT501P watchdog board, say Y here,
13331 otherwise N. It is not possible to probe for this board, which means
13332 that you have to inform the kernel about the IO port and IRQ using
13333 the "wdt=" kernel option (try "man bootparam" or see the
13334 documentation of your boot loader (lilo or loadlin) about how to
13335 pass options to the kernel at boot time).
13337 If you want to compile this as a module ( = code which can be
13338 inserted in and removed from the running kernel whenever you want),
13339 say M here and read Documentation/modules.txt. The module will be
13342 WDT PCI Watchdog timer
13344 If you have a PCI WDT500/501 watchdog board, say Y here,
13345 otherwise N. It is not possible to probe for this board, which means
13346 that you have to inform the kernel about the IO port and IRQ using
13347 the "wdt=" kernel option (try "man bootparam" or see the
13348 documentation of your boot loader (lilo or loadlin) about how to
13349 pass options to the kernel at boot time).
13351 If you want to compile this as a module ( = code which can be
13352 inserted in and removed from the running kernel whenever you want),
13353 say M here and read Documentation/modules.txt. The module will be
13358 Saying Y here and creating a character special file /dev/temperature
13359 with major number 10 and minor number 131 ("man mknod") will give
13360 you a thermometer inside your computer: reading from
13361 /dev/temperature yields one byte, the temperature in degrees
13362 Fahrenheit. This works only if you have a WDT501P watchdog board
13367 Enable the Fan Tachometer on the WDT501. Only do this if you have a
13368 fan tachometer actually set up.
13371 CONFIG_SOFT_WATCHDOG
13372 A software monitoring watchdog. This will fail to reboot your system
13373 from some situations that the hardware watchdog will recover
13374 from. Equally it's a lot cheaper to install.
13376 This driver is also available as a module ( = code which can be
13377 inserted in and removed from the running kernel whenever you want).
13378 If you want to compile it as a module, say M here and read
13379 Documentation/modules.txt. The module will be called softdog.o.
13381 Berkshire Products PC Watchdog
13383 This is the driver for the Berkshire Products PC Watchdog card.
13384 This card simply watches your kernel to make sure it doesn't freeze,
13385 and if it does, it reboots your computer after a certain amount of
13386 time. This driver is like the WDT501 driver but for different
13387 hardware. Please read Documentation/pcwd-watchdog.txt. The PC
13388 watchdog cards can be ordered from http://www.berkprod.com .
13390 This driver is also available as a module ( = code which can be
13391 inserted in and removed from the running kernel whenever you want).
13392 The module is called pcwd.o. If you want to compile it as a module,
13393 say M here and read Documentation/modules.txt.
13395 Most people will say N.
13397 Acquire SBC Watchdog Timer
13399 This is the driver for the hardware watchdog on the PSC-6x86 Single
13400 Board Computer produced by Acquire Inc (and others). This watchdog
13401 simply watches your kernel to make sure it doesn't freeze, and if
13402 it does, it reboots your computer after a certain amount of time.
13404 This driver is like the WDT501 driver but for different hardware.
13405 This driver is also available as a module ( = code which can be
13406 inserted in and removed from the running kernel whenever you want).
13407 The module is called pscwdt.o. If you want to compile it as a
13408 module, say M here and read Documentation/modules.txt. Most people
13413 This is a driver for the Mixcom hardware watchdog cards. This
13414 watchdog simply watches your kernel to make sure it doesn't freeze,
13415 and if it does, it reboots your computer after a certain amount of
13418 This driver is also available as a module ( = code which can be
13419 inserted in and removed from the running kernel whenever you want).
13420 The module is called mixcomwd.o. If you want to compile it as a
13421 module, say M here and read Documentation/modules.txt. Most people
13424 Toshiba Laptop support
13426 If you intend to run this the kernel on a Toshiba portable say yes
13427 here. This adds a driver to safely access the System Management
13428 Mode of the CPU on Toshiba portables. The System Management Mode
13429 is used to set the BIOS and power saving options on Toshiba portables.
13431 For information on utilities to make use of this driver see the
13432 Toshiba Linux utilities website at:
13433 http://www.buzzard.org.uk/toshiba/
13435 /dev/cpu/microcode - Intel P6 CPU microcode support
13437 If you say Y here and also to "/dev file system support" in the
13438 'File systems' section, you will be able to update the microcode on
13439 Intel processors in the P6 family, e.g. Pentium Pro, Pentium II,
13440 Pentium III, Xeon etc. You will obviously need the actual microcode
13441 binary data itself which is not shipped with the Linux kernel.
13443 For latest news and information on obtaining all the required
13444 ingredients for this driver, check:
13445 http://www.urbanmyth.org/microcode/
13447 This driver is also available as a module ( = code which can be
13448 inserted in and removed from the running kernel whenever you want).
13449 The module will be called microcode.o. If you want to compile it as
13450 a module, say M here and read Documentation/modules.txt.
13452 /dev/cpu/*/msr - Model-specific register support
13454 This device gives privileged processes access to the x86
13455 Model-Specific Registers (MSRs). It is a character device with
13456 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
13457 MSR accesses are directed to a specific CPU on multi-processor
13460 /dev/cpu/*/cpuid - CPU information support
13462 This device gives processes access to the x86 CPUID instruction to
13463 be executed on a specific processor. It is a character device
13464 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
13467 Enhanced Real Time Clock Support
13469 If you say Y here and create a character special file /dev/rtc with
13470 major number 10 and minor number 135 using mknod ("man mknod"), you
13471 will get access to the real time clock (or hardware clock) built
13472 into your computer.
13474 Every PC has such a clock built in. It can be used to generate
13475 signals from as low as 1Hz up to 8192Hz, and can also be used
13476 as a 24 hour alarm. It reports status information via the file
13477 /proc/driver/rtc and its behaviour is set by various ioctls on
13480 If you run Linux on a multiprocessor machine and said Y to
13481 "Symmetric Multi Processing" above, you should say Y here to read
13482 and set the RTC in an SMP compatible fashion.
13484 If you think you have a use for such a device (such as periodic data
13485 sampling), then say Y here, and read Documentation/rtc.txt for
13488 This driver is also available as a module ( = code which can be
13489 inserted in and removed from the running kernel whenever you want).
13490 The module is called rtc.o. If you want to compile it as a module,
13491 say M here and read Documentation/modules.txt.
13494 #EFI Real Time Clock Services
13497 Tadpole ANA H8 Support
13499 The Hitachi H8/337 is a microcontroller used to deal with the power
13500 and thermal environment. If you say Y here, you will be able to
13501 communicate with it via a character special device.
13507 If you say Y here and create a character special file /dev/nvram
13508 with major number 10 and minor number 144 using mknod ("man mknod"),
13509 you get read and write access to the 50 bytes of non-volatile memory
13510 in the real time clock (RTC), which is contained in every PC and
13513 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
13514 on Ataris. /dev/nvram may be used to view settings there, or to
13515 change them (with some utility). It could also be used to frequently
13516 save a few bits of very important data that may not be lost over
13517 power-off and for which writing to disk is too insecure. Note
13518 however that most NVRAM space in a PC belongs to the BIOS and you
13519 should NEVER idly tamper with it. See Ralf Brown's interrupt list
13520 for a guide to the use of CMOS bytes by your BIOS.
13522 On Atari machines, /dev/nvram is always configured and does not need
13525 This driver is also available as a module ( = code which can be
13526 inserted in and removed from the running kernel whenever you want).
13527 The module will be called nvram.o. If you want to compile it as a
13528 module, say M here and read Documentation/modules.txt.
13532 If you have a joystick, 6dof controller, gamepad, steering wheel,
13533 weapon control system or something like that you can say Y here to
13534 enable generic support for these controllers. You will also need to
13535 say Y or M to at least one of the hardware specific drivers. This
13536 will make the controllers available as /dev/input/jsX devices.
13537 Please read the file Documentation/joystick.txt which contains more
13538 information and the location of the joystick package that you'll
13543 Say Y here if you have an ISA, ISAPnP or PCI standard gameport.
13544 For more information on how to use the driver please read
13545 Documentation/joystick.txt
13547 This driver is also available as a module ( = code which can be
13548 inserted in and removed from the running kernel whenever you want).
13549 The module will be called ns558.o. If you want to compile
13550 it as a module, say M here and read Documentation/modules.txt.
13552 PDPI Lightning 4 gamecard
13553 CONFIG_INPUT_LIGHTNING
13554 Say Y here if you have a PDPI Lightning 4 gamecard. For more
13555 information on how to use the driver please read
13556 Documentation/joystick.txt
13558 This driver is also available as a module ( = code which can be
13559 inserted in and removed from the running kernel whenever you want).
13560 The module will be called lightning.o. If you want to compile
13561 it as a module, say M here and read Documentation/modules.txt.
13563 Aureal Vortex and Trident 4DWave gameports
13564 CONFIG_INPUT_PCIGAME
13565 Say Y here if you have a Trident 4DWave DX/NX or Aureal Vortex 1/2
13566 card. For more information on how to use the driver please read
13567 Documentation/joystick.txt
13569 This driver is also available as a module ( = code which can be
13570 inserted in and removed from the running kernel whenever you want).
13571 The module will be called pcigame.o. If you want to compile
13572 it as a module, say M here and read Documentation/modules.txt.
13574 Classic PC analog joysticks and gamepads
13575 CONFIG_INPUT_ANALOG
13576 Say Y here if you have a controller that connects to the PC
13577 gameport. This supports many different types, including joysticks
13578 with throttle control, with rudders, or with extensions like
13579 additional hats and buttons compatible with CH Flightstick Pro,
13580 ThrustMaster FCS, 6 and 8 button gamepads, or Saitek Cyborg
13581 joysticks. For more information on how to use the driver please read
13582 Documentation/joystick.txt
13584 This driver is also available as a module ( = code which can be
13585 inserted in and removed from the running kernel whenever you want).
13586 The module will be called analog.o. If you want to compile
13587 it as a module, say M here and read Documentation/modules.txt.
13589 Assasin 3D and MadCatz Panther devices
13591 Say Y here if you have an FPGaming or MadCatz controller using the
13592 A3D protocol over the PC gameport. For more information on how to
13593 use the driver please read Documentation/joystick.txt
13595 This driver is also available as a module ( = code which can be
13596 inserted in and removed from the running kernel whenever you want).
13597 The module will be called a3d.o. If you want to compile
13598 it as a module, say M here and read Documentation/modules.txt.
13600 Logitech ADI digital joysticks and gamepads
13602 Say Y here if you have a Logitech controller using the ADI
13603 protocol over the PC gameport. For more information on how to use
13604 the driver please read Documentation/joystick.txt
13606 This driver is also available as a module ( = code which can be
13607 inserted in and removed from the running kernel whenever you want).
13608 The module will be called adi.o. If you want to compile
13609 it as a module, say M here and read Documentation/modules.txt.
13611 Creative Labs Blaster Cobra gamepad
13613 Say Y here if you have a Creative Labs Blaster Cobra gamepad.
13614 For more information on how to use the driver please read
13615 Documentation/joystick.txt
13617 This driver is also available as a module ( = code which can be
13618 inserted in and removed from the running kernel whenever you want).
13619 The module will be called cobra.o. If you want to compile
13620 it as a module, say M here and read Documentation/modules.txt.
13622 Genius Flight2000 Digital joysticks and gamepads
13624 Say Y here if you have a Genius Flight2000 or MaxFighter
13625 digitally communicating joystick or gamepad. For more information
13626 on how to use the driver please read Documentation/joystick.txt
13628 This driver is also available as a module ( = code which can be
13629 inserted in and removed from the running kernel whenever you want).
13630 The module will be called gf2k.o. If you want to compile
13631 it as a module, say M here and read Documentation/modules.txt.
13633 Gravis GrIP joysticks and gamepads
13635 Say Y here if you have a Gravis controller using the GrIP protocol
13636 over the PC gameport. For more information on how to use the driver
13637 please read Documentation/joystick.txt
13639 This driver is also available as a module ( = code which can be
13640 inserted in and removed from the running kernel whenever you want).
13641 The module will be called grip.o. If you want to compile
13642 it as a module, say M here and read Documentation/modules.txt.
13644 InterAct digital joysticks and gamepads
13645 CONFIG_INPUT_INTERACT
13646 Say Y hereif you have an InterAct gameport or joystick
13647 communicating digitally over the gameport. For more information on
13648 how to use the driver please read Documentation/joystick.txt
13650 This driver is also available as a module ( = code which can be
13651 inserted in and removed from the running kernel whenever you want).
13652 The module will be called interact.o. If you want to compile
13653 it as a module, say M here and read Documentation/modules.txt.
13655 ThrustMaster DirectConnect joysticks and gamepads
13657 Say Y here if you have a ThrustMaster controller using the
13658 DirectConnect (BSP) protocol over the PC gameport. For more
13659 information on how to use the driver please read
13660 Documentation/joystick.txt
13662 This driver is also available as a module ( = code which can be
13663 inserted in and removed from the running kernel whenever you want).
13664 The module will be called tmdc.o. If you want to compile
13665 it as a module, say M here and read Documentation/modules.txt.
13667 Microsoft SideWinder digital joysticks and gamepads
13668 CONFIG_INPUT_SIDEWINDER
13669 Say Y here if you have a Microsoft controller using the Digital
13670 Overdrive protocol over PC gameport. For more information on how to
13671 use the driver please read Documentation/joystick.txt
13673 This driver is also available as a module ( = code which can be
13674 inserted in and removed from the running kernel whenever you want).
13675 The module will be called sidewinder.o. If you want to compile
13676 it as a module, say M here and read Documentation/modules.txt.
13678 Serial port input line discipline
13679 CONFIG_INPUT_SERPORT
13680 Say Y hereif you plan to use a joystick that communicates over the
13681 serial (COM) port. For more information on how to use the driver
13682 please read Documentation/joystick.txt
13684 This driver is also available as a module ( = code which can be
13685 inserted in and removed from the running kernel whenever you want).
13686 The module will be called serport.o. If you want to compile
13687 it as a module, say M here and read Documentation/modules.txt.
13689 Logitech WingMan Warrior joystick
13690 CONFIG_INPUT_WARRIOR
13691 Say Y here if you have a Logitech WingMan Warrior joystick
13692 connected to your computer's serial port. For more information on
13693 how to use the driver please read Documentation/joystick.txt
13695 This driver is also available as a module ( = code which can be
13696 inserted in and removed from the running kernel whenever you want).
13697 The module will be called warrior.o. If you want to compile
13698 it as a module, say M here and read Documentation/modules.txt.
13700 LogiCad3d Magellan/SpaceMouse 6dof controller
13701 CONFIG_INPUT_MAGELLAN
13702 Say Y here if you have a Magellan or Space Mouse 6DOF controller
13703 connected to your computer's serial port. For more information on
13704 how to use the driver please read Documentation/joystick.txt
13706 This driver is also available as a module ( = code which can be
13707 inserted in and removed from the running kernel whenever you want).
13708 The module will be called magellan.o. If you want to compile
13709 it as a module, say M here and read Documentation/modules.txt.
13711 SpaceTec SpaceOrb/Avenger 6dof controller
13712 CONFIG_INPUT_SPACEORB
13713 Say Y here if you have a SpaceOrb 360 or SpaceBall Avenger 6DOF
13714 controller connected to your computer's serial port. For more
13715 information on how to use the driver please read
13716 Documentation/joystick.txt
13718 This driver is also available as a module ( = code which can be
13719 inserted in and removed from the running kernel whenever you want).
13720 The module will be called spaceorb.o. If you want to compile
13721 it as a module, say M here and read Documentation/modules.txt.
13723 SpaceTec SpaceBall 4000 FLX 6dof controller
13724 CONFIG_INPUT_SPACEBALL
13725 Say Y here if you have a SpaceTec SpaceBall 4000 FLX controller
13726 connected to your computer's serial port. For more information on
13727 how to use the driver please read Documentation/joystick.txt
13729 I-Force joysticks/wheels
13730 CONFIG_INPUT_IFORCE_232
13731 Say Y here if you have an I-Force joystick or steering wheel
13732 connected to your serial (COM) port. For more information on
13733 how to use the driver please read Documentation/joystick.txt
13735 This driver is also available as a module ( = code which can be
13736 inserted in and removed from the running kernel whenever you want).
13737 The module will be called iforce.o. If you want to compile
13738 it as a module, say M here and read Documentation/modules.txt.
13740 I-Force joysticks/wheels
13741 CONFIG_INPUT_IFORCE_USB
13742 Say Y here if you have an I-Force joystick or steering wheel
13743 connected to your USB port. For more information on how to use the
13744 driver please read Documentation/joystick.txt
13746 This driver is also available as a module ( = code which can be
13747 inserted in and removed from the running kernel whenever you want).
13748 The module will be called iforce.o. If you want to compile
13749 it as a module, say M here and read Documentation/modules.txt.
13751 Multisystem, Sega Genesis, Saturn joysticks and gamepads
13753 Say Y here if you have a Sega Master System gamepad, Sega Genesis
13754 gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga,
13755 Commodore, Amstrad CPC joystick connected to your parallel port.
13756 For more information on how to use the driver please read
13757 Documentation/joystick.txt and Documentation/joystick-parport.txt.
13759 This driver is also available as a module ( = code which can be
13760 inserted in and removed from the running kernel whenever you want).
13761 The module will be called db9.o. If you want to compile
13762 it as a module, say M here and read Documentation/modules.txt.
13764 Multisystem, NES, SNES, N64, PSX joysticks and gamepads
13765 CONFIG_INPUT_GAMECON
13766 Say Y here if you have a Nintendo Entertainment System gamepad,
13767 Super Nintendo Entertainment System gamepad, Nintendo 64 gamepad,
13768 Sony PlayStation gamepad or a Multisystem -- Atari, Amiga,
13769 Commodore, Amstrad CPC joystick connected to your parallel port.
13770 For more information on how to use the driver please read
13771 Documentation/joystick.txt and Documentation/joystick-parport.txt
13773 This driver is also available as a module ( = code which can be
13774 inserted in and removed from the running kernel whenever you want).
13775 The module will be called gamecon.o. If you want to compile
13776 it as a module, say M here and read Documentation/modules.txt.
13778 Multisystem joysticks via TurboGraFX device
13779 CONFIG_INPUT_TURBOGRAFX
13780 Say Y here if you have the TurboGraFX interface by Steffen
13781 Schwenke, and want to use it with Multiststem -- Atari, Amiga,
13782 Commodore, Amstrad CPC joystick. For more information on how to use
13783 the driver please read Documentation/joystick.txt and
13784 Documentation/joystick-parport.txt
13786 This driver is also available as a module ( = code which can be
13787 inserted in and removed from the running kernel whenever you want).
13788 The module will be called turbografx.o. If you want to compile
13789 it as a module, say M here and read Documentation/modules.txt.
13792 CONFIG_INPUT_AMIJOY
13793 Say Y here if you have an Amiga with a digital joystick connected
13794 to it. For more information on how to use the driver please read
13795 Documentation/joystick.txt
13797 This driver is also available as a module ( = code which can be
13798 inserted in and removed from the running kernel whenever you want).
13799 The module will be called joy-amiga.o. If you want to compile
13800 it as a module, say M here and read Documentation/modules.txt.
13802 Atomwide Serial Support
13803 CONFIG_ATOMWIDE_SERIAL
13804 If you have an Atomwide Serial card for an Acorn system, say Y to
13805 this option. The driver can handle 1, 2, or 3 port cards.
13808 The Serial Port Dual Serial Port
13809 CONFIG_DUALSP_SERIAL
13810 If you have the Serial Port's dual serial card for an Acorn system,
13811 say Y to this option. If unsure, say N
13815 If you say Y here and create a character device node /dev/nwbutton
13816 with major and minor numbers 10 and 158 ("man mknod"), then every
13817 time the orange button is pressed a number of times, the number of
13818 times the button was pressed will be written to that device.
13820 This is most useful for applications, as yet unwritten, which
13821 perform actions based on how many times the button is pressed in a
13824 Do not hold the button down for too long, as the driver does not
13825 alter the behaviour of the hardware reset circuitry attached to the
13826 button; it will still execute a hard reset if the button is held
13827 down for longer than approximately five seconds.
13829 This driver is also available as a module ( = code which can be
13830 inserted in and removed from the running kernel whenever you want).
13831 If you want to compile it as a module, say M here and read
13832 Documentation/modules.txt. The module will be called nwbutton.o.
13834 Most people will answer Y to this question and "Reboot Using Button"
13835 below to be able to initiate a system shutdown from the button.
13837 Reboot Using Button
13838 CONFIG_NWBUTTON_REBOOT
13839 If you say Y here, then you will be able to initiate a system
13840 shutdown and reboot by pressing the orange button a number of times.
13841 The number of presses to initiate the shutdown is two by default,
13842 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
13843 in nwbutton.h and recompiling the driver or, if you compile the
13844 driver as a module, you can specify the number of presses at load
13845 time with "insmod button reboot_count=<something>".
13849 If you have a sound card in your computer, i.e. if it can say more
13850 than an occasional beep, say Y. Be sure to have all the information
13851 about your sound card and its configuration down (I/O port,
13852 interrupt and DMA channel), because you will be asked for it.
13854 You want to read the Sound-HOWTO, available from
13855 http://www.linuxdoc.org/docs.html#howto . General information
13856 about the modular sound system is contained in the files
13857 Documentation/sound/Introduction. The file
13858 Documentation/sound/README.OSS contains some slightly outdated but
13859 still useful information as well.
13861 If you have a PnP sound card and you want to configure it at boot
13862 time using the ISA PnP tools (read
13863 http://www.roestock.demon.co.uk/isapnptools/ ), then you need to
13864 compile the sound card support as a module ( = code which can be
13865 inserted in and removed from the running kernel whenever you want)
13866 and load that module after the PnP configuration is finished. To do
13867 this, say M here and read Documentation/modules.txt as well as
13868 Documentation/sound/README.modules; the module will be called
13871 I'm told that even without a sound card, you can make your computer
13872 say more than an occasional beep, by programming the PC speaker.
13873 Kernel patches and supporting utilities to do that are in the pcsp
13874 package, available at ftp://ftp.infradead.org/pub/pcsp/ .
13878 OSS is the Open Sound System suite of sound card drivers. They make
13879 sound programming easier since they provide a common API. Say Y or M
13880 here (the module will be called sound.o) if you haven't found a
13881 driver for your sound card above, then pick your driver from the
13884 Persistent DMA buffers
13886 Linux can often have problems allocating DMA buffers for ISA sound
13887 cards on machines with more than 16MB of RAM. This is because ISA
13888 DMA buffers must exist below the 16MB boundary and it is quite
13889 possible that a large enough free block in this region cannot be
13890 found after the machine has been running for a while. If you say Y
13891 here the DMA buffers (64Kb) will be allocated at boot time and kept
13892 until the shutdown. This option is only useful if you said Y to
13893 "OSS sound modules", above. If you said M to "OSS sound modules"
13894 then you can get the persistent DMA buffer functionality by passing
13895 the command-line argument "dmabuf=1" to the sound.o module.
13897 Say Y unless you have 16MB or less RAM or a PCI sound card.
13899 Support for Aztech Sound Galaxy (non-PnP) cards
13900 CONFIG_SOUND_SGALAXY
13901 This module initializes the older non Plug and Play sound galaxy
13902 cards from Aztech. It supports the Waverider Pro 32 - 3D and the
13903 Galaxy Washington 16.
13905 If you compile the driver into the kernel, you have to add
13906 "sgalaxy=<io>,<irq>,<dma>,<dma2>,<sgbase>" to the kernel command
13909 Support for AD1816(A) based cards (EXPERIMENTAL)
13910 CONFIG_SOUND_AD1816
13911 Say M here if you have a sound card based on the Analog Devices
13914 If you compile the driver into the kernel, you have to add
13915 "ad1816=<io>,<irq>,<dma>,<dma2>" to the kernel command line.
13917 Yamaha OPL3-SA1 audio controller
13918 CONFIG_SOUND_OPL3SA1
13919 Say Y or M if you have a Yamaha OPL3-SA1 sound chip, which is
13920 usually built into motherboards. Read Documentation/sound/OPL3-SA
13923 If you compile the driver into the kernel, you have to add
13924 "opl3sa=<io>,<irq>,<dma>,<dma2>,<mpuio>,<mpuirq>" to the kernel
13927 ProAudioSpectrum 16 support
13929 Answer Y only if you have a Pro Audio Spectrum 16, ProAudio Studio
13930 16 or Logitech SoundMan 16 sound card. Answer N if you have some
13931 other card made by Media Vision or Logitech since those are not
13932 PAS16 compatible. Please read Documentation/sound/PAS16.
13934 If you compile the driver into the kernel, you have to add
13935 "pas2=<io>,<irq>,<dma>,<dma2>,<sbio>,<sbirq>,<sbdma>,<sbdma2>
13936 to the kernel command line.
13938 100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support
13940 Answer Y if you have an original Sound Blaster card made by Creative
13941 Labs or a 100% hardware compatible clone (like the Thunderboard or
13942 SM Games). For an unknown card you may answer Y if the card claims
13943 to be Sound Blaster-compatible.
13945 Please read the file Documentation/sound/Soundblaster.
13947 You should also say Y here for cards based on the Avance Logic
13948 ALS-007 and ALS-1X0 chips (read Documentation/sound/ALS) and for cards
13949 based on ESS chips (read Documentation/sound/ESS1868 and
13950 Documentation/sound/ESS). If you have an SB AWE 32 or SB AWE 64, say
13951 Y here and also to "AWE32 synth" below and read
13952 Documentation/sound/INSTALL.awe. If you have an IBM Mwave card, say
13953 Y here and read Documentation/sound/mwave.
13955 If you compile the driver into the kernel and don't want to use
13956 isapnp, you have to add "sb=<io>,<irq>,<dma>,<dma2>" to the kernel
13959 You can say M here to compile this driver as a module; the module is
13962 #Loopback MIDI device support
13963 #CONFIG_SOUND_VMIDI
13965 ### somebody please fill this in.
13968 Gravis Ultrasound support
13970 Say Y here for any type of Gravis Ultrasound card, including
13971 the GUS or GUS MAX. See also Documentation/sound/ultrasound for
13972 more information on configuring this card with modules.
13974 If you compile the driver into the kernel, you have to add
13975 "gus=<io>,<irq>,<dma>,<dma2>" to the kernel command line.
13977 MPU-401 support (NOT for SB16)
13978 CONFIG_SOUND_MPU401
13979 Be careful with this question. The MPU401 interface is supported by
13980 all sound cards. However, some natively supported cards have their
13981 own driver for MPU401. Enabling this MPU401 option with these cards
13982 will cause a conflict. Also, enabling MPU401 on a system that
13983 doesn't really have a MPU401 could cause some trouble. If your card
13984 was in the list of supported cards, look at the card specific
13985 instructions in the drivers/sound/Readme.cards file. It's safe to
13986 answer Y if you have a true MPU401 MIDI interface card.
13988 If you compile the driver into the kernel, you have to add
13989 "mpu401=<io>,<irq>" to the kernel command line.
13992 CONFIG_SOUND_UART6850
13993 This option enables support for MIDI interfaces based on the 6850
13994 UART chip. This interface is rarely found on sound cards. It's safe
13995 to answer N to this question.
13997 If you compile the driver into the kernel, you have to add
13998 "uart6850=<io>,<irq>" to the kernel command line.
14000 PSS (AD1848, ADSP-2115, ESC614) support
14002 Answer Y or M if you have an Orchid SW32, Cardinal DSP16, Beethoven
14003 ADSP-16 or some other card based on the PSS chipset (AD1848 codec +
14004 ADSP-2115 DSP chip + Echo ESC614 ASIC CHIP). For more information on
14005 how to compile it into the kernel or as a module see the file
14006 Documentation/sound/PSS.
14008 If you compile the driver into the kernel, you have to add
14009 "pss=<io>,<mssio>,<mssirq>,<mssdma>,<mpuio>,<mpuirq>" to the kernel
14012 Enable PSS mixer (Beethoven ADSP-16 and other compatible)
14014 Answer Y for Beethoven ADSP-16. You may try to say Y also for other
14015 cards if they have master volume, bass, treble, and you can't
14016 control it under Linux. If you answer N for Beethoven ADSP-16, you
14017 can't control master volume, bass, treble and synth volume.
14019 If you said M to "PSS support" above, you may enable or disable this
14020 PSS mixer with the module parameter pss_mixer. For more information
14021 see the file Documentation/sound/PSS.
14023 Have DSPxxx.LD firmware file
14024 CONFIG_PSS_HAVE_BOOT
14025 If you have the DSPxxx.LD file or SYNTH.LD file for you card, say Y
14026 to include this file. Without this file the synth device (OPL) may
14029 Full pathname of DSPxxx.LD firmware file
14030 CONFIG_PSS_BOOT_FILE
14031 Enter the full pathname of your DSPxxx.LD file or SYNTH.LD file,
14034 Microsoft Sound System support
14036 Again think carefully before answering Y to this question. It's safe
14037 to answer Y if you have the original Windows Sound System card made
14038 by Microsoft or Aztech SG 16 Pro (or NX16 Pro). Also you may say Y
14039 in case your card is NOT among these:
14041 ATI Stereo F/X, AdLib, Audio Excell DSP16, Cardinal DSP16,
14042 Ensoniq SoundScape (and compatibles made by Reveal and Spea),
14043 Gravis Ultrasound, Gravis Ultrasound ACE, Gravis Ultrasound Max,
14044 Gravis Ultrasound with 16 bit option, Logitech Sound Man 16,
14045 Logitech SoundMan Games, Logitech SoundMan Wave, MAD16 Pro (OPTi
14046 82C929), Media Vision Jazz16, MediaTriX AudioTriX Pro, Microsoft
14047 Windows Sound System (MSS/WSS), Mozart (OAK OTI-601), Orchid
14048 SW32, Personal Sound System (PSS), Pro Audio Spectrum 16, Pro
14049 Audio Studio 16, Pro Sonic 16, Roland MPU-401 MIDI interface,
14050 Sound Blaster 1.0, Sound Blaster 16, Sound Blaster 16ASP, Sound
14051 Blaster 2.0, Sound Blaster AWE32, Sound Blaster Pro, TI TM4000M
14052 notebook, ThunderBoard, Turtle Beach Tropez, Yamaha FM
14053 synthesizers (OPL2, OPL3 and OPL4), 6850 UART MIDI Interface.
14055 For cards having native support in VoxWare, consult the card
14056 specific instructions in drivers/sound/Readme.cards. Some drivers
14057 have their own MSS support and saying Y to this option will cause a
14060 If you compile the driver into the kernel, you have to add
14061 "ad1848=<io>,<irq>,<dma>,<dma2>[,<type>]" to the kernel command
14064 SGI Visual Workstation on-board audio
14066 Say Y or M if you have an SGI Visual Workstation and you want to
14067 be able to use its on-board audio. Read Documentation/sound/vwsnd
14068 for more info on this driver's capabilities.
14070 Ensoniq Soundscape support
14071 CONFIG_SOUND_SSCAPE
14072 Answer Y if you have a sound card based on the Ensoniq SoundScape
14073 chipset. Such cards are being manufactured at least by Ensoniq, Spea
14074 and Reveal (Reveal makes also other cards).
14076 If you compile the driver into the kernel, you have to add
14077 "sscape=<io>,<irq>,<dma>,<mpuio>,<mpuirq>" to the kernel command
14080 MediaTriX AudioTriX Pro support
14082 Answer Y if you have the AudioTriX Pro sound card manufactured
14085 Have TRXPRO.HEX firmware file
14086 CONFIG_TRIX_HAVE_BOOT
14087 The MediaTrix AudioTrix Pro has an on-board microcontroller which
14088 needs to be initialized by downloading the code from the file
14089 TRXPRO.HEX in the DOS driver directory. If you don't have the
14090 TRXPRO.HEX file handy you may skip this step. However, the SB and
14091 MPU-401 modes of AudioTrix Pro will not work without this file!
14093 Full pathname of TRXPRO.HEX firmware file
14094 CONFIG_TRIX_BOOT_FILE
14095 Enter the full pathname of your TRXPRO.HEX file, starting from /.
14097 Support for OPTi MAD16 and/or Mozart based cards
14099 Answer Y if your card has a Mozart (OAK OTI-601) or MAD16 (OPTi
14100 82C928 or 82C929 or 82C931) audio interface chip. These chips are
14101 quite common so it's possible that many no-name cards have one of
14102 them. In addition the MAD16 chip is used in some cards made by known
14103 manufacturers such as Turtle Beach (Tropez), Reveal (some models)
14104 and Diamond (latest ones). Note however that the Tropez sound cards
14105 have their own driver; if you have one of those, say N here and Y or
14106 M to "Full support for Turtle Beach WaveFront", below.
14108 If you compile the driver into the kernel, you have to add
14109 "mad16=<io>,<irq>,<dma>,<dma2>,<mpuio>,<mpuirq>" to the
14110 kernel command line.
14112 See also Documentation/sound/Opti and Documentation/sound/MAD16 for
14113 more information on setting these cards up as modules.
14115 Full support for Turtle Beach WaveFront synth/sound cards
14116 CONFIG_SOUND_WAVEFRONT
14117 Answer Y or M if you have a Tropez Plus, Tropez or Maui sound card
14118 and read the files Documentation/sound/Wavefront and
14119 Documentation/sound/Tropez+.
14121 Support MIDI in older MAD16 based cards (requires SB)
14122 CONFIG_MAD16_OLDCARD
14123 Answer Y (or M) if you have an older card based on the C928 or
14124 Mozart chipset and you want to have MIDI support. If you enable this
14125 option you also need to enable support for Sound Blaster.
14127 Support for Crystal CS4232 based (PnP) cards
14128 CONFIG_SOUND_CS4232
14129 Say Y here if you have a card based on the Crystal CS4232 chip set,
14130 which uses its own Plug and Play protocol.
14132 If you compile the driver into the kernel, you have to add
14133 "cs4232=<io>,<irq>,<dma>,<dma2>,<mpuio>,<mpuirq>" to the kernel
14136 See Documentation/sound/CS4232 for more information on configuring
14139 Support for Yamaha OPL3-SA2, SA3, and SAx based PnP cards
14140 CONFIG_SOUND_OPL3SA2
14141 Say Y or M if you have a card based on one of these Yamaha
14142 sound chipsets. Read Documentation/sound/OPL3-SA2 for more
14143 information on configuring these cards.
14145 If you compile the driver into the kernel, you have to add
14146 "opl3sa2=<io>,<irq>,<dma>,<dma2>,<mssio>,<mpuio>" to the kernel
14149 Support for Turtle Beach Wave Front (Maui, Tropez) synthesizers
14151 Say Y here if you have a Turtle Beach Wave Front, Maui, or Tropez
14154 If you compile the driver into the kernel, you have to add
14155 "maui=<io>,<irq>" to the kernel command line.
14157 Have OSWF.MOT firmware file
14158 CONFIG_MAUI_HAVE_BOOT
14159 Turtle Beach Maui and Tropez sound cards have a microcontroller
14160 which needs to be initialized prior to use. OSWF.MOT is a file
14161 distributed with the card's DOS/Windows drivers. Answer Y if you
14164 Full pathname of OSWF.MOT firmware file
14165 CONFIG_MAUI_BOOT_FILE
14166 Enter the full pathname of your OSWF.MOT file, starting from /.
14168 Support for Turtle Beach MultiSound Classic, Tahiti, Monterey
14169 CONFIG_SOUND_MSNDCLAS
14170 Say M here if you have a Turtle Beach MultiSound Classic, Tahiti or
14171 Monterey (not for the Pinnacle or Fiji).
14173 See Documentation/sound/MultiSound for important information about
14176 Full pathname of MSNDINIT.BIN firmware file
14177 CONFIG_MSNDCLAS_INIT_FILE
14178 The MultiSound cards have two firmware files which are required for
14179 operation, and are not currently included. These files can be
14180 obtained from Turtle Beach. See Documentation/sound/MultiSound for
14181 information on how to obtain this.
14183 Full pathname of MSNDPERM.BIN firmware file
14184 CONFIG_MSNDCLAS_PERM_FILE
14185 The MultiSound cards have two firmware files which are required for
14186 operation, and are not currently included. These files can be
14187 obtained from Turtle Beach. See Documentation/sound/MultiSound for
14188 information on how to obtain this.
14190 Support for Turtle Beach MultiSound Pinnacle, Fiji
14191 CONFIG_SOUND_MSNDPIN
14192 Say M here if you have a Turtle Beach MultiSound Pinnacle or Fiji.
14193 See Documentation/sound/MultiSound for important information about
14196 Full pathname of PNDSPINI.BIN firmware file
14197 CONFIG_MSNDPIN_INIT_FILE
14198 The MultiSound cards have two firmware files which are required for
14199 operation, and are not currently included. These files can be
14200 obtained from Turtle Beach. See Documentation/sound/MultiSound for
14201 information on how to obtain this.
14203 Full pathname of PNDSPERM.BIN firmware file
14204 CONFIG_MSNDPIN_PERM_FILE
14205 The MultiSound cards have two firmware files which are required for
14206 operation, and are not currently included. These files can be
14207 obtained from Turtle Beach. See Documentation/sound/MultiSound for
14208 information on how to obtain this.
14210 MSND Pinnacle have S/PDIF I/O
14211 CONFIG_MSNDPIN_DIGITAL
14212 If you have the S/PDIF daughter board for the Pinnacle or Fiji,
14213 answer Y here; otherwise, say N. If you have this, you will be able
14214 to play and record from the S/PDIF port (digital signal). See
14215 Documentation/sound/MultiSound for information on how to make use of
14218 MSND Pinnacle non-PnP Mode
14219 CONFIG_MSNDPIN_NONPNP
14220 The Pinnacle and Fiji card resources can be configured either with
14221 PnP, or through a configuration port. Say Y here if your card is NOT
14222 in PnP mode. For the Pinnacle, configuration in non-PnP mode allows
14223 use of the IDE and joystick peripherals on the card as well; these
14224 do not show up when the card is in PnP mode. Specifying zero for any
14225 resource of a device will disable the device. If you are running the
14226 card in PnP mode, you must say N here and use isapnptools to
14227 configure the card's resources.
14229 MSND Pinnacle config port
14231 This is the port which the Pinnacle and Fiji uses to configure the
14232 card's resources when not in PnP mode. If your card is in PnP mode,
14233 then be sure to say N to the previous option, "MSND Pinnacle Non-PnP
14236 MSND buffer size (kB)
14237 CONFIG_MSND_FIFOSIZE
14238 Configures the size of each audio buffer, in kilobytes, for
14239 recording and playing in the MultiSound drivers (both the Classic
14240 and Pinnacle). Larger values reduce the chance of data overruns at
14241 the expense of overall latency. If unsure, use the default.
14243 FM synthesizer (YM3812/OPL-3) support
14244 CONFIG_SOUND_YM3812
14245 Answer Y if your card has a FM chip made by Yamaha (OPL2/OPL3/OPL4).
14246 Answering Y is usually a safe and recommended choice, however some
14247 cards may have software (TSR) FM emulation. Enabling FM support with
14248 these cards may cause trouble (I don't currently know of any such
14250 Please read the file Documentation/sound/OPL3 if your card has an
14253 If you compile the driver into the kernel, you have to add
14254 "opl3=<io>" to the kernel command line.
14258 ACI mixer (miroPCM12/PCM20)
14259 CONFIG_SOUND_ACI_MIXER
14260 ACI (Audio Command Interface) is a protocol used to communicate with
14261 the microcontroller on some sound cards produced by miro, e.g. the
14262 miroSOUND PCM12 and PCM20. The main function of the ACI is to
14263 control the mixer and to get a product identification.
14265 This Voxware ACI driver currently only supports the ACI functions on
14266 the miroSOUND PCM12 and PCM20 cards. On the PCM20, ACI also controls
14267 the radio tuner. This is supported in the video4linux
14268 radio-miropcm20 driver.
14271 CONFIG_SOUND_AWE32_SYNTH
14272 Say Y here if you have a Sound Blaster SB32, AWE32-PnP, SB AWE64 or
14273 similar sound card. See Documentation/sound/README.awe,
14274 Documentation/sound/AWE32 and the Soundblaster-AWE mini-HOWTO,
14275 available from http://www.linuxdoc.org/docs.html#howto for more
14278 Gallant's Audio Excel DSP 16 support (SC-6000 and SC-6600)
14279 CONFIG_SOUND_AEDSP16
14280 Answer Y if you have a Gallant's Audio Excel DSP 16 card. This
14281 driver supports Audio Excel DSP 16 but not the III nor PnP versions
14284 The Gallant's Audio Excel DSP 16 card can emulate either an SBPro or
14285 a Microsoft Sound System card, so you should have said Y to either
14286 "100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support"
14287 or "Microsoft Sound System support", above, and you need to answer
14288 the "MSS emulation" and "SBPro emulation" questions below
14289 accordingly. You should say Y to one and only one of these two
14292 Read the drivers/sound/lowlevel/README.aedsp16 file and the head of
14293 drivers/sound/lowlevel/aedsp16.c as well as
14294 Documentation/sound/AudioExcelDSP16 to get more information about
14295 this driver and its configuration.
14297 Audio Excel DSP 16 (SBPro emulation)
14298 CONFIG_AEDSP16_SBPRO
14299 Answer Y if you want your audio card to emulate Sound Blaster Pro.
14300 You should then say Y to "100% Sound Blaster compatibles
14301 (SB16/32/64, ESS, Jazz16) support" and N to "Audio Excel DSP 16 (MSS
14304 If you compile the driver into the kernel, you have to add
14305 "aedsp16=<io>,<irq>,<dma>,<mssio>,<mpuio>,<mouirq>" to the kernel
14308 Audio Excel DSP 16 (MSS emulation)
14310 Answer Y if you want your audio card to emulate Microsoft Sound
14311 System. You should then say Y to "Microsoft Sound System support"
14312 and say N to "Audio Excel DSP 16 (SBPro emulation)".
14314 SC-6600 based audio cards (new Audio Excel DSP 16)
14316 The SC6600 is the new version of DSP mounted on the Audio Excel DSP
14317 16 cards. Find in the manual the FCC ID of your audio card and
14318 answer Y if you have an SC6600 DSP.
14320 SC-6600 Joystick Interface
14322 Say Y here in order to use the joystick interface of the Audio Excel
14325 SC-6600 CDROM Interface
14326 CONFIG_SC6600_CDROM
14327 This is used to activate the the CDROM interface of the Audio Excel
14328 DSP 16 card. Enter: 0 for Sony, 1 for Panasonic, 2 for IDE, 4 for no
14331 Audio Excel DSP 16 (MPU401 emulation)
14332 CONFIG_AEDSP16_MPU401
14333 Answer Y if you want your audio card to emulate the MPU-401 midi
14334 interface. You should then also say Y to "MPU-401 support".
14336 Note that the I/O base for MPU-401 support of aedsp16 is the same
14337 you have selected for "MPU-401 support". If you are using this
14338 driver as a module you have to specify the MPU I/O base address with
14339 the parameter 'mpu_base=0xNNN'.
14341 Creative EMU10K1 based PCI sound cards
14342 CONFIG_SOUND_EMU10K1
14343 Say Y or M if you have a PCI sound card using the EMU10K1
14344 chipset, such as the Creative SBLive!, SB PCI512 or Emu-APS.
14346 Crystal SoundFusion (CS4280/461x)
14347 CONFIG_SOUND_FUSION
14348 This module drives the Crystal SoundFusion devices (CS4280/46xx series)
14349 when wired as native sound drivers with AC97 codecs. If this driver
14350 does not work try the CS4232 driver.
14352 Ensoniq ES1370 based PCI sound cards
14353 CONFIG_SOUND_ES1370
14354 Say Y or M if you have a PCI sound card utilizing the Ensoniq
14355 ES1370 chipset, such as Ensoniq's AudioPCI (non-97). To find
14356 out if your sound card uses an ES1370 without removing your
14357 computer's cover, use lspci -n and look for the PCI ID
14358 1274:5000. Since Ensoniq was bought by Creative Labs,
14359 Sound Blaster 64/PCI models are either ES1370 or ES1371 based.
14360 This driver differs slightly from OSS/Free, so PLEASE READ
14361 Documentation/sound/es1370.
14363 Ensoniq ES1371 based PCI sound cards
14364 CONFIG_SOUND_ES1371
14365 Say Y or M if you have a PCI sound card utilizing the Ensoniq
14366 ES1371 chipset, such as Ensoniq's AudioPCI97. To find out if
14367 your sound card uses an ES1371 without removing your computer's
14368 cover, use lspci -n and look for the PCI ID 1274:1371. Since
14369 Ensoniq was bought by Creative Labs, Sound Blaster 64/PCI
14370 models are either ES1370 or ES1371 based. This driver differs
14371 slightly from OSS/Free, so PLEASE READ Documentation/sound/es1371.
14373 ESS Solo1 based PCI sound cards (eg. SC1938)
14374 CONFIG_SOUND_ESSSOLO1
14375 Say Y or M if you have a PCI sound card utilizing the ESS Technology
14376 Solo1 chip. To find out if your sound card uses a
14377 Solo1 chip without removing your computer's cover, use
14378 lspci -n and look for the PCI ID 125D:1969. This driver
14379 differs slightly from OSS/Free, so PLEASE READ
14380 Documentation/sound/solo1.
14382 S3 SonicVibes based PCI sound cards
14383 CONFIG_SOUND_SONICVIBES
14384 Say Y or M if you have a PCI sound card utilizing the S3
14385 SonicVibes chipset. To find out if your sound card uses a
14386 SonicVibes chip without removing your computer's cover, use
14387 lspci -n and look for the PCI ID 5333:CA00. This driver
14388 differs slightly from OSS/Free, so PLEASE READ
14389 Documentation/sound/sonicvibes.
14391 Trident 4DWave DX/NX, SiS 7018 or ALi 5451 PCI Audio Core
14392 CONFIG_SOUND_TRIDENT
14393 Say Y or M if you have a PCI sound card utilizing the Trident
14394 4DWave-DX/NX chipset or your mother board chipset has SiS 7018
14395 or ALi 5451 built-in. The SiS 7018 PCI Audio Core is embedded
14396 in SiS960 Super South Bridge and SiS540/630 Single Chipset.
14397 The ALi 5451 PCI Audio Core is embedded in ALi M1535, M1535D,
14398 M1535+ or M1535D+ South Bridge.
14400 Use lspci -n to find out if your sound card or chipset uses
14401 Trident 4DWave or SiS 7018. PCI ID 1023:2000 or 1023:2001 stands
14402 for Trident 4Dwave. PCI ID 1039:7018 stands for SiS7018. PCI ID
14403 10B9:5451 stands for ALi5451.
14405 This driver supports S/PDIF in/out (record/playback) for ALi 5451
14406 embedded in ALi M1535+ and M1535D+. Note that they aren't all
14407 enabled by default; you can enable them by saying Y to "/proc file
14408 system support" and "Sysctl support", and after the /proc file
14409 system has been mounted, executing the command
14411 command what is enabled
14413 echo 0>/proc/ALi5451 pcm out is also set to S/PDIF out. (Default).
14415 echo 1>/proc/ALi5451 use S/PDIF out to output pcm data.
14417 echo 2>/proc/ALi5451 use S/PDIF out to output non-pcm data.(AC3...).
14419 echo 3>/proc/ALi5451 record from Ac97 in(MIC, Line in...). (Default).
14421 echo 4>/proc/ALi5451 no matter Ac97 settings, record from S/PDIF in.
14424 This driver differs slightly from OSS/Free, so PLEASE READ the
14425 comments at the top of driver/sound/trident.c
14427 Rockwell WaveArtist
14428 CONFIG_SOUND_WAVEARTIST
14429 Say Y here to include support for the Rockwell WaveArtist sound
14430 system. This driver is mainly for the NetWinder.
14432 VIA 82Cxxx Audio Codec
14433 CONFIG_SOUND_VIA82CXXX
14434 Say Y here to include support for the audio codec found on VIA
14435 82Cxxx-based chips. Typically these are built into a motherboard. DO
14436 NOT select Sound Blaster or Adlib with this driver, unless you have
14437 a Sound Blaster or Adlib card in addition to your VIA audio chip.
14439 NeoMagic 256AV/256ZX sound chipsets
14441 Say M here to include audio support for the NeoMagic 256AV/256ZX
14442 chipsets. These are the audio chipsets found in the Sony
14443 Z505S/SX/DX, some Sony F-series, and the Dell Latitude CPi and CPt
14444 laptops. It includes support for an AC97-compatible mixer and an
14445 apparently proprietary sound engine.
14447 See Documentation/sound/NM256 for further information.
14449 ESS Maestro sound chipsets
14450 CONFIG_SOUND_MAESTRO
14451 Say Y or M if you have a sound system driven by ESS's Maestro line
14452 of PCI sound chips. These include the Maestro 1, Maestro 2, and
14453 Maestro 2E. See Documentation/sound/Maestro for more details.
14455 Are you using a crosscompiler
14456 CONFIG_CROSSCOMPILE
14457 Say Y here if you are compiling the kernel on a different
14458 architecture than the one it is intended to run on.
14460 Kernel support for Linux/MIPS 32-bit binary compatibility
14461 CONFIG_MIPS32_COMPAT
14462 Select this option if you want Linux/MIPS 32-bit binary
14463 compatibility. Since all software available for Linux/MIPS is
14464 currently 32-bit you should say Y here.
14466 Build fp exception handler module
14467 CONFIG_MIPS_FPE_MODULE
14468 Build the floating point exception handler module. This option is
14469 only useful for people working on the floating point exception
14470 handler. If you don't, say N.
14472 Remote GDB kernel debugging
14473 CONFIG_REMOTE_DEBUG
14474 If you say Y here, it will be possible to remotely debug the MIPS
14475 kernel using gdb. This enlarges your kernel image disk size by
14476 several megabytes and requires a machine with more than 16 MB,
14477 better 32 MB RAM to avoid excessive linking time. This is only
14478 useful for kernel hackers. If unsure, say N.
14480 Magic System Request Key support
14482 If you say Y here, you will have some control over the system even
14483 if the system crashes for example during kernel debugging (e.g., you
14484 will be able to flush the buffer cache to disk, reboot the system
14485 immediately or dump some status information). This is accomplished
14486 by pressing various keys while holding SysRq (Alt+PrintScreen). It
14487 also works on a serial console (on PC hardware at least), if you
14488 send a BREAK and then within 5 seconds a command keypress. The
14489 keys are documented in Documentation/sysrq.txt. Don't say Y unless
14490 you really know what this hack does.
14494 ISDN ("Integrated Services Digital Networks", called RNIS in France)
14495 is a special type of fully digital telephone service; it's mostly
14496 used to connect to your Internet service provider (with SLIP or
14497 PPP). The main advantage is that the speed is higher than ordinary
14498 modem/telephone connections, and that you can have voice
14499 conversations while downloading stuff. It only works if your
14500 computer is equipped with an ISDN card and both you and your service
14501 provider purchased an ISDN line from the phone company. For details,
14502 read http://alumni.caltech.edu/~dank/isdn/ on the WWW.
14504 This driver allows you to use an ISDN-card for networking
14505 connections and as dialin/out device. The isdn-tty's have a built in
14506 AT-compatible modem emulator. Network devices support autodial,
14507 channel-bundling, callback and caller-authentication without having
14508 a daemon running. A reduced T.70 protocol is supported with tty's
14509 suitable for German BTX. On D-Channel, the protocols EDSS1
14510 (Euro-ISDN) and 1TR6 (German style) are supported. See
14511 Documentation/isdn/README for more information.
14513 If you want to compile the ISDN code as a module ( = code which can
14514 be inserted in and removed from the running kernel whenever you
14515 want), say M here and read Documentation/modules.txt. The module
14516 will be called isdn.o. If unsure, say N.
14518 Support synchronous PPP
14520 Over digital connections such as ISDN, there is no need to
14521 synchronize sender and recipient's clocks with start and stop bits
14522 as is done over analog telephone lines. Instead, one can use
14523 "synchronous PPP". Saying Y here will include this protocol. This
14524 protocol is used by Cisco and Sun for example. So you want to say Y
14525 here if the other end of your ISDN connection supports it. You will
14526 need a special version of pppd (called ipppd) for using this
14527 feature. See Documentation/isdn/README.syncppp and
14528 Documentation/isdn/syncPPP.FAQ for more information.
14530 Support generic MP (RFC 1717)
14532 With synchronous PPP enabled, it is possible to increase throughput
14533 by bundling several ISDN-connections, using this protocol. See
14534 Documentation/isdn/README.syncppp for more information.
14536 Use VJ-compression with synchronous PPP
14538 This enables Van Jacobson header compression for synchronous PPP.
14539 Say Y if the other end of the connection supports it.
14541 Support audio via ISDN
14543 If you say Y here, the modem-emulator will support a subset of the
14544 EIA Class 8 Voice commands. Using a getty with voice-support
14545 (mgetty+sendfax by gert@greenie.muc.de with an extension, available
14546 with the ISDN utility package for example), you will be able to use
14547 your Linux box as an ISDN-answering machine. Of course, this must be
14548 supported by the lowlevel driver also. Currently, the HiSax driver
14549 is the only voice-supporting driver. See
14550 Documentation/isdn/README.audio for more information.
14552 X.25 PLP on top of ISDN
14554 This feature provides the X.25 protocol over ISDN connections.
14555 See Documentation/isdn/README.x25 for more information
14556 if you are thinking about using this.
14558 ISDN diversion services support
14559 CONFIG_ISDN_DIVERSION
14560 This option allows you to use some supplementary diversion
14561 services in conjunction with the HiSax driver on an EURO/DSS1
14564 Supported options are CD (call deflection), CFU (Call forward
14565 unconditional), CFB (Call forward when busy) and CFNR (call forward
14566 not reachable). Additionally the actual CFU, CFB and CFNR state may
14569 The use of CFU, CFB, CFNR and interrogation may be limited to some
14570 countries. The keypad protocol is still not implemented. CD should
14571 work in all countries if the service has been subscribed to.
14573 Please read the file Documentation/isdn/README.diversion.
14575 ICN 2B and 4B support
14576 CONFIG_ISDN_DRV_ICN
14577 This enables support for two kinds of ISDN-cards made by a German
14578 company called ICN. 2B is the standard version for a single ISDN
14579 line with two B-channels, 4B supports two ISDN lines. For running
14580 this card, additional firmware is necessary, which has to be
14581 downloaded into the card using a utility which is distributed
14582 separately. See Documentation/isdn/README and README.icn for more
14585 If you want to compile this as a module ( = code which can be
14586 inserted in and removed from the running kernel whenever you want),
14587 say M here and read Documentation/modules.txt. The module will be
14591 CONFIG_ISDN_DRV_LOOP
14592 This driver provides a virtual ISDN card. Its primary purpose is
14593 testing of linklevel features or configuration without getting
14594 charged by your service-provider for lots of phone calls.
14595 You need will need the loopctrl utility from the latest isdn4k-utils
14596 package to set up this driver.
14598 HiSax SiemensChipSet driver support
14599 CONFIG_ISDN_DRV_HISAX
14600 This is a driver supporting the Siemens chipset on various
14601 ISDN-cards (like AVM A1, Elsa ISDN cards, Teles S0-16.0, Teles
14602 S0-16.3, Teles S0-8, Teles/Creatix PnP, ITK micro ix1 and many
14605 HiSax is just the name of this driver, not the name of any hardware.
14607 If you have a card with such a chipset, you should say Y here and
14608 also to the configuration option of the driver for your particular
14611 If you want to compile this as a module ( = code which can be
14612 inserted in and removed from the running kernel whenever you want),
14613 say M here and read Documentation/modules.txt. The module will be
14614 called hisax.o. See Documentation/isdn/README.HiSax for more
14615 information on using this driver.
14617 HiSax Support for EURO/DSS1
14619 Say Y or N according to the D-channel protocol which your local
14620 telephone service company provides.
14622 The call control protocol E-DSS1 is used in most European countries.
14623 If unsure, say yes.
14625 Support for german charge info
14627 If you want that the HiSax hardware driver sends messages to the
14628 upper level of the isdn code on each AOCD (Advice Of Charge, During
14629 the call -- transmission of the fee information during a call) and
14630 on each AOCE (Advice Of Charge, at the End of the call --
14631 transmission of fee information at the end of the call), say Y here.
14632 This works only in Germany.
14634 Disable sending complete
14635 CONFIG_HISAX_NO_SENDCOMPLETE
14636 If you have trouble with some ugly exchanges or you live in
14637 Australia select this option.
14639 Disable sending low layer compatibility
14640 CONFIG_HISAX_NO_LLC
14641 If you have trouble with some ugly exchanges try to select this
14644 Disable keypad protocol option
14645 CONFIG_HISAX_NO_KEYPAD
14646 If you like to send special dial strings including * or # without
14647 using the keypad protocol, select this option.
14649 HiSax Support for German 1TR6
14651 Say Y or N according to the D-channel protocol which your local
14652 telephone service company provides.
14654 1TR6 is an old call control protocol which was used in Germany
14655 before E-DSS1 was established. Nowadays, all new lines in Germany
14658 HiSax Support for US NI1
14660 Enable this if you like to use ISDN in US on a NI1 basic rate interface.
14664 This enables HiSax support for the Teles ISDN-cards S0-16.0, S0-8
14665 and many compatibles.
14667 See Documentation/isdn/README.HiSax on how to configure it using the
14668 different cards, a different D-channel protocol, or non-standard
14669 IRQ/port/shmem settings.
14671 Teles 16.3 or PNP or PCMCIA
14673 This enables HiSax support for the Teles ISDN-cards S0-16.3 the
14674 Teles/Creatix PnP and the Teles PCMCIA.
14676 See Documentation/isdn/README.HiSax on how to configure it using the
14677 different cards, a different D-channel protocol, or non-standard
14681 CONFIG_HISAX_TELESPCI
14682 This enables HiSax support for the Teles PCI.
14683 See Documentation/isdn/README.HiSax on how to configure it.
14687 This enables HiSax support for the Teles/Creatix parallel port
14688 S0BOX. See Documentation/isdn/README.HiSax on how to configure it.
14691 CONFIG_HISAX_AVM_A1
14692 This enables HiSax support for the AVM A1 (aka "Fritz").
14694 See Documentation/isdn/README.HiSax on how to configure it using the
14695 different cards, a different D-channel protocol, or non-standard
14698 AVM PnP/PCI (Fritz!PNP/PCI)
14699 CONFIG_HISAX_FRITZPCI
14700 This enables HiSax support for the AVM "Fritz!PnP" and "Fritz!PCI".
14701 See Documentation/isdn/README.HiSax on how to configure it.
14703 AVM A1 PCMCIA (Fritz)
14704 CONFIG_HISAX_AVM_A1_PCMCIA
14705 This enables HiSax support for the AVM A1 "Fritz!PCMCIA").
14706 See Documentation/isdn/README.HiSax on how to configure it.
14710 This enables HiSax support for the Elsa Mircolink ISA cards, for the
14711 Elsa Quickstep series cards and Elsa PCMCIA.
14713 See Documentation/isdn/README.HiSax on how to configure it using the
14714 different cards, a different D-channel protocol, or non-standard
14717 ITK ix1-micro Revision 2
14718 CONFIG_HISAX_IX1MICROR2
14719 This enables HiSax support for the ITK ix1-micro Revision 2 card.
14721 See Documentation/isdn/README.HiSax on how to configure it using the
14722 different cards, a different D-channel protocol, or non-standard
14725 Eicon.Diehl Diva cards
14726 CONFIG_HISAX_DIEHLDIVA
14727 This enables HiSax support for the Eicon.Diehl Diva none PRO
14728 versions passive ISDN cards.
14730 See Documentation/isdn/README.HiSax on how to configure it using the
14731 different cards, a different D-channel protocol, or non-standard
14735 CONFIG_HISAX_ASUSCOM
14736 This enables HiSax support for the AsusCom and their OEM versions
14737 passive ISDN ISA cards.
14739 See Documentation/isdn/README.HiSax on how to configure it using the
14740 different cards, a different D-channel protocol, or non-standard
14744 CONFIG_HISAX_TELEINT
14745 This enables HiSax support for the TELEINT SA1 semiactiv ISDN card.
14747 See Documentation/isdn/README.HiSax on how to configure it using the
14748 different cards, a different D-channel protocol, or non-standard
14753 This enables HiSax support for the HFC-S 2BDS0 based cards, like
14756 See Documentation/isdn/README.HiSax on how to configure it using the
14757 different cards, a different D-channel protocol, or non-standard
14761 CONFIG_HISAX_SEDLBAUER
14762 This enables HiSax support for the Sedlbauer passive ISDN cards.
14764 See Documentation/isdn/README.HiSax on how to configure it using the
14765 different cards, a different D-channel protocol, or non-standard
14768 USR Sportster internal TA
14769 CONFIG_HISAX_SPORTSTER
14770 This enables HiSax support for the USR Sportster internal TA card.
14772 See Documentation/isdn/README.HiSax on how to configure it using a
14773 different D-channel protocol, or non-standard IRQ/port settings.
14777 This enables HiSax support for the ITH MIC card.
14779 See Documentation/isdn/README.HiSax on how to configure it using a
14780 different D-channel protocol, or non-standard IRQ/port settings.
14783 CONFIG_HISAX_NETJET
14784 This enables HiSax support for the NetJet from Traverse
14787 See Documentation/isdn/README.HiSax on how to configure it using a
14788 different D-channel protocol, or non-standard IRQ/port settings.
14791 CONFIG_HISAX_NETJET_U
14792 This enables HiSax support for the Netspider U interface ISDN card from
14793 Traverse Technologies.
14794 See Documentation/isdn/README.HiSax on how to configure it using a
14795 different D-channel protocol, or non-standard IRQ/port settings.
14799 This enables HiSax support for the Dr. Neuhaus Niccy PnP or PCI.
14801 See Documentation/isdn/README.HiSax on how to configure it using a
14802 different D-channel protocol, or non-standard IRQ/port settings.
14804 Siemens I-Surf card
14806 This enables HiSax support for the Siemens I-Talk/I-Surf card with
14808 See Documentation/isdn/README.HiSax on how to configure it using a
14809 different D-channel protocol, or non-standard IRQ/port settings.
14812 CONFIG_HISAX_HSTSAPHIR
14813 This enables HiSax support for the HST Saphir card.
14815 See Documentation/isdn/README.HiSax on how to configure it using a
14816 different D-channel protocol, or non-standard IRQ/port settings.
14819 CONFIG_HISAX_BKM_A4T
14820 This enables HiSax support for the Telekom A4T card.
14822 See Documentation/isdn/README.HiSax on how to configure it using a
14823 different D-channel protocol, or non-standard IRQ/port settings.
14826 CONFIG_HISAX_SCT_QUADRO
14827 This enables HiSax support for the Scitel Quadro card.
14829 See Documentation/isdn/README.HiSax on how to configure it using a
14830 different D-channel protocol, or non-standard IRQ/port settings.
14834 This enables HiSax support for the Gazel cards.
14836 See Documentation/isdn/README.HiSax on how to configure it using a
14837 different D-channel protocol, or non-standard IRQ/port settings.
14840 CONFIG_HISAX_HFC_PCI
14841 This enables HiSax support for the HFC-S PCI 2BDS0 based cards.
14843 For more informations see under Documentation/isdn/README.hfc-pci.
14845 Winbond W6692 based cards
14847 This enables HiSax support for Winbond W6692 based PCI ISDN cards.
14849 See Documentation/isdn/README.HiSax on how to configure it using a
14850 different D-channel protocol, or non-standard IRQ/port settings.
14852 HFC-S+, HFC-SP, HFC-PCMCIA cards (EXPERIMENTAL)
14853 CONFIG_HISAX_HFC_SX
14854 This enables HiSax support for the HFC-S+, HFC-SP and HFC-PCMCIA
14855 cards. This code is not finished yet.
14857 Am7930 (EXPERIMENTAL)
14858 CONFIG_HISAX_AMD7930
14859 This enables HiSax support for the AMD7930 chips on some SPARCs.
14860 This code is not finished yet.
14863 CONFIG_ISDN_DRV_PCBIT
14864 This enables support for the PCBIT ISDN-card. This card is
14865 manufactured in Portugal by Octal. For running this card, additional
14866 firmware is necessary, which has to be downloaded into the card
14867 using a utility which is distributed separately. See
14868 Documentation/isdn/README and Documentation/isdn/README.pcbit for
14871 If you want to compile this as a module ( = code which can be
14872 inserted in and removed from the running kernel whenever you want),
14873 say M here and read Documentation/modules.txt. The module will be
14876 Spellcaster support (EXPERIMENTAL)
14878 This enables support for the Spellcaster BRI ISDN boards. This
14879 driver currently builds only in a modularized version ( = code which
14880 can be inserted in and removed from the running kernel whenever you
14881 want, details in Documentation/modules.txt); the module will be
14882 called sc.o. See Documentation/isdn/README.sc and
14883 http://www.spellcast.com for more information.
14885 Eicon active card support
14886 CONFIG_ISDN_DRV_EICON
14887 Say Y here if you have an Eicon active ISDN card. In order to use
14888 this card, additional firmware is necessary, which has to be loaded
14889 into the card using the eiconctrl utility which is part of the
14890 latest isdn4k-utils package. Please read the file
14891 Documentation/isdn/README.eicon for more information.
14893 Eicon Diva Server card support
14894 CONFIG_ISDN_DRV_EICON_PCI
14895 Say Y here if you have an Eicon Diva Server (BRI/PRI/4BRI) ISDN card.
14896 Please read Documentation/isdn/README.eicon for more information.
14898 Eicon old-type card support
14899 CONFIG_ISDN_DRV_EICON_ISA
14900 Say Y here if you have an old-type Eicon active ISDN card. In order
14901 to use this card, additional firmware is necessary, which has to be
14902 loaded into the card using the eiconctrl utility which is part of
14903 the latest isdn4k-utils package. Please read the file
14904 Documentation/isdn/README.eicon for more information.
14906 Eicon driver type standalone
14907 CONFIG_ISDN_DRV_EICON_STANDALONE
14908 Enable this option if you want the eicon driver as standalone
14909 version with no interface to the ISDN4Linux isdn module. If you
14910 say Y here, the eicon module only supports the Diva Server PCI
14911 cards and will provide its own IDI interface. You should say N
14914 Support AT-Fax Class 1 and 2 commands
14915 CONFIG_ISDN_TTY_FAX
14916 If you say Y here, the modem-emulator will support a subset of the
14917 Fax Class 1 and 2 commands. Using a getty with fax-support
14918 (mgetty+sendfax, hylafax), you will be able to use your Linux box as
14919 an ISDN-fax-machine. This must be supported by the lowlevel driver
14920 also. See Documentation/isdn/README.fax for more information.
14924 This provides the CAPI (Common ISDN Application Programming
14925 Interface, a standard making it easy for programs to access ISDN
14926 hardware, see http://www.capi.org/ . This is needed for AVM's set of
14927 active ISDN controllers like B1, T1, M1.
14929 This code is also available as a module ( = code which can be
14930 inserted in and removed from the running kernel whenever you want).
14931 The modules will be called capi.o and kernelcapi.o. If you want to
14932 compile it as a module, say M here and read
14933 Documentation/modules.txt.
14936 CONFIG_ISDN_DRV_AVMB1_B1ISA
14937 Enable support for the ISA version of the AVM B1 card.
14940 CONFIG_ISDN_DRV_AVMB1_B1PCI
14941 Enable support for the PCI version of the AVM B1 card.
14943 AVM B1 PCI V4 support
14944 CONFIG_ISDN_DRV_AVMB1_B1PCIV4
14945 Enable support for the V4 version of AVM B1 PCI card.
14947 AVM T1/T1-B ISA support
14948 CONFIG_ISDN_DRV_AVMB1_T1ISA
14949 Enable support for the AVM T1 T1B card.
14950 Note: This is a PRI card and handle 30 B-channels.
14952 AVM B1/M1/M2 PCMCIA support
14953 CONFIG_ISDN_DRV_AVMB1_B1PCMCIA
14954 Enable support for the PCMCIA version of the AVM B1 card.
14956 AVM T1/T1-B PCI support
14957 CONFIG_ISDN_DRV_AVMB1_T1PCI
14958 Enable support for the AVM T1 T1B card.
14959 Note: This is a PRI card and handle 30 B-channels.
14962 CONFIG_ISDN_DRV_AVMB1_C4
14963 Enable support for the AVM C4 PCI card.
14964 This card handle 4 BRI ISDN lines (8 channels).
14966 Verbose reason code reporting (kernel size +=7K)
14967 CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON
14968 If you say Y here, the AVM B1 driver will give verbose reasons for
14969 disconnecting. This will increase the size of the kernel by 7 KB. If
14972 IBM Active 2000 support (EXPERIMENTAL)
14973 CONFIG_ISDN_DRV_ACT2000
14974 Say Y here if you have an IBM Active 2000 ISDN card. In order to use
14975 this card, additional firmware is necessary, which has to be loaded
14976 into the card using a utility which is part of the latest
14977 isdn4k-utils package. Please read the file
14978 Documentation/isdn/README.act2000 for more information.
14980 Hypercope HYSDN cards (Champ, Ergo, Metro) support (module)
14982 Say Y here if you have one of Hypercope's active PCI ISDN cards
14983 Champ, Ergo and Metro. You will then get a module called hysdn.o.
14984 Please read the file Documentation/isdn/README.hysdn for more
14987 HYSDN CAPI 2.0 support
14989 Say Y here if you like to use Hypercope's CAPI 2.0 interface
14991 Support for Sun4 architecture
14993 Say Y here if, and only if, your machine is a Sun4. Note that
14994 a kernel compiled with this option will run only on Sun4.
14995 (And the current version will probably work only on sun4/330.)
14997 SPARC ESP SCSI support
14999 This is the driver for the Sun ESP SCSI host adapter. The ESP
15000 chipset is present in most SPARC SBUS-based computers.
15002 This support is also available as a module called esp.o ( = code
15003 which can be inserted in and removed from the running kernel
15004 whenever you want). If you want to compile it as a module, say M
15005 here and read Documentation/modules.txt.
15007 PTI Qlogic, ISP Driver
15008 CONFIG_SCSI_QLOGICPTI
15009 This driver supports SBUS SCSI controllers from PTI or QLogic. These
15010 controllers are known under Solaris as qpti and in the openprom as
15011 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
15012 driven by a different driver.
15014 This support is also available as a module called qlogicpti.o ( =
15015 code which can be inserted in and removed from the running kernel
15016 whenever you want). If you want to compile it as a module, say M
15017 here and read Documentation/modules.txt.
15019 SPARC /dev/openprom compatibility driver (EXPERIMENTAL)
15020 CONFIG_SUN_OPENPROMIO
15021 This driver provides user programs with an interface to the SPARC
15022 PROM device tree. The driver implements a SunOS-compatible
15023 interface and a NetBSD-compatible interface.
15025 If you want to compile this as a module ( = code which can be
15026 inserted in and removed from the running kernel whenever you want),
15027 say M and read Documentation/modules.txt. If unsure, say Y.
15029 Openprom tree appears in /proc/openprom
15030 CONFIG_SUN_OPENPROMFS
15031 If you say Y, the OpenPROM device tree will be available as a
15032 virtual file system, which you can mount to /proc/openprom by "mount
15033 -t openpromfs none /proc/openprom".
15035 If you want to compile the /proc/openprom support as a module ( =
15036 code which can be inserted in and removed from the running kernel
15037 whenever you want), say M here and read Documentation/modules.txt.
15038 The module will be called openpromfs.o. If unsure, say M.
15040 Kernel support for Linux/Sparc 32bit binary compatibility
15041 CONFIG_SPARC32_COMPAT
15042 This allows you to run 32-bit binaries on your Ultra.
15043 Everybody wants this; say Y.
15045 Kernel support for 32-bit ELF binaries
15046 CONFIG_BINFMT_ELF32
15047 This allows you to run 32-bit Linux/ELF binaries on your Ultra.
15048 Everybody wants this; say Y.
15050 Kernel support for 32-bit (ie. SunOS) a.out binaries
15051 CONFIG_BINFMT_AOUT32
15052 This allows you to run 32-bit a.out format binaries on your Ultra.
15053 If you want to run SunOS binaries (see SunOS binary emulation below)
15054 or other a.out binaries, say Y. If unsure, say N.
15056 SunOS binary emulation
15058 This allows you to run most SunOS binaries. If you want to do this,
15059 say Y here and place appropriate files in /usr/gnemul/sunos. See
15060 http://www.ultralinux.org/faq.html for more information. If you want
15061 to run SunOS binaries on an Ultra you must also say Y to "Kernel
15062 support for 32-bit a.out binaries" above.
15064 Mostek real time clock support
15065 CONFIG_SUN_MOSTEK_RTC
15066 The Mostek RTC chip is used on all known Sun computers except
15067 some JavaStations. For a JavaStation you need to say Y both here
15068 and to "Enhanced Real Time Clock Support".
15070 Say Y here unless you are building a special purpose kernel.
15072 OBP Flash Device support
15074 The OpenBoot PROM on Ultra systems is flashable. If you want to be
15075 able to upgrade the OBP firmware, say Y here.
15077 JavaStation OS Flash SIMM
15079 If you say Y here, you will be able to boot from your JavaStation's
15082 Siemens SAB82532 serial support
15084 This driver supports the serial ports on newer (PCI) Ultra systems.
15085 Say Y if you want to be able to use your serial ports.
15087 Aurora Multiboard 1600se (EXPERIMENTAL)
15089 The Aurora Multiboard is a multi-port high-speed serial controller.
15090 If you have one of these, say Y.
15092 Audio support (EXPERIMENTAL)
15094 This driver provides support for the build-in sound devices on most
15095 Sun machines. If you want to be able to use this, select this option
15096 and one or more of the lowlevel drivers below. See
15097 http://www.dementia.org/~shadow/sparcaudio.html for more
15100 AMD7930 Lowlevel Driver
15101 CONFIG_SPARCAUDIO_AMD7930
15102 This driver supports the AMD 7930 chip found on sun4c, 4/6xx, and
15103 SparcClassic systems.
15105 CS4231 Lowlevel Driver
15106 CONFIG_SPARCAUDIO_CS4231
15107 This driver supports the Crystal Semiconductor CS4231 chip found on
15108 the SS4, SS5, and Ultras.
15110 DBRI Lowlevel Driver
15111 CONFIG_SPARCAUDIO_DBRI
15112 This driver supports the DBRI audio interface found on the SS10,
15113 SS20, Sparcbook 3, and Voyager systems.
15115 Dummy lowlevel Driver
15116 CONFIG_SPARCAUDIO_DUMMY
15117 This is a pseudo-driver used for debugging and testing the
15118 sparcaudio subsystem. Say N unless you want to work on this
15121 Sparc hardware (EXPERIMENTAL)
15122 CONFIG_PARPORT_SUNBPP
15123 This driver provides support for the bidirectional parallel port
15124 found on many Sun machines. Note that many of the newer Ultras
15125 actually have pc style hardware instead.
15128 # m68k-specific kernel options
15129 # Documented by Chris Lawrence <quango@themall.net> et al.
15133 This option enables support for the Amiga series of computers. If
15134 you plan to use this kernel on an Amiga, say Y here and browse the
15135 material available in Documentation/m68k; otherwise say N.
15139 This option enables support for the 68000-based Atari series of
15140 computers (including the TT, Falcon and Medusa). If you plan to use
15141 this kernel on an Atari, say Y here and browse the material
15142 available in Documentation/m68k; otherwise say N.
15146 This option enables support for the Hades Atari clone. If you plan
15147 to use this kernel on a Hades, say Y here; otherwise say N.
15151 This option enables support for the Apple Macintosh series of
15152 computers (yes, there is experimental support now, at least for part
15155 Say N unless you're willing to code the remaining necessary support.
15160 This option enables support for the HP9000/300 series of
15161 workstations. Support for these machines is still very experimental.
15162 If you plan to try to use the kernel on such a machine say Y here.
15163 Everybody else says N.
15167 This option enables support for the Sun 3x series of workstations.
15168 Be warned that this support is very experimental. You will also want
15169 to say Y to 68020 support and N to the other processors below.
15171 If you don't want to compile a kernel for a Sun 3x, say N.
15175 If you anticipate running this kernel on a computer with a MC68020
15176 processor, say Y. Otherwise, say N. Note that the 68020 requires a
15177 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
15178 Sun 3, which provides its own version.
15182 If you anticipate running this kernel on a computer with a MC68030
15183 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
15184 work, as it does not include an MMU (Memory Management Unit).
15188 If you anticipate running this kernel on a computer with a MC68LC040
15189 or MC68040 processor, say Y. Otherwise, say N. Note that an
15190 MC68EC040 will not work, as it does not include an MMU (Memory
15195 If you anticipate running this kernel on a computer with a MC68060
15196 processor, say Y. Otherwise, say N.
15198 Math emulation support (EXPERIMENTAL)
15200 At some point in the future, this will cause floating-point math
15201 instructions to be emulated by the kernel on machines that lack a
15202 floating-point math coprocessor. Thrill-seekers and chronically
15203 sleep-deprived psychotic hacker types can say Y now, everyone else
15204 should probably wait a while.
15206 Math emulation only kernel
15207 CONFIG_M68KFPU_EMU_ONLY
15208 This option prevents any floating-point instructions from being
15209 compiled into the kernel, thereby the kernel doesn't save any
15210 floating point context anymore during task switches, so this
15211 kernel will only be usable on machines without a floating-point
15212 math coprocessor. This makes the kernel a bit faster as no tests
15213 needs to be executed whether a floating-point instruction in the
15214 kernel should be executed or not.
15216 Math emulation extra precision
15217 CONFIG_M68KFPU_EMU_EXTRAPREC
15218 The fpu uses normally a few bit more during calculations for
15219 correct rounding, the emulator can (often) do the same but this
15220 extra calculation can cost quite some time, so you can disable
15221 it here. The emulator will then "only" calculate with a 64 bit
15222 mantissa and round slightly incorrect, what is more then enough
15225 Advanced configuration options
15227 This gives you access to some advanced options for the CPU. The
15228 defaults should be fine for most users, but these options may make
15229 it possible for you to improve performance somewhat if you know what
15232 Note that the answer to this question won't directly affect the
15233 kernel: saying N will just cause this configure script to skip all
15234 the questions about these options.
15236 Most users should say N to this question.
15238 Use read-modify-write instructions
15240 This allows to use certain instructions that work with indivisible
15241 read-modify-write bus cycles. While this is faster than the
15242 workaround of disabling interrupts, it can conflict with DMA
15243 ( = direct memory access) on many Amiga systems, and it is also said
15244 to destabilize other machines. It is very likely that this will
15245 cause serious problems on any Amiga or Atari Medusa if set. The only
15246 configuration where it should work are 68030-based Ataris, where it
15247 apparently improves performance. But you've been warned! Unless you
15248 really know what you are doing, say N. Try Y only if you're quite
15253 This enables support for the Zorro bus in the Amiga. If you have
15254 expansion cards in your Amiga that conform to the Amiga
15255 AutoConfig(tm) specification, say Y, otherwise N. Note that even
15256 expansion cards that do not fit in the Zorro slots but fit in e.g.
15257 the CPU slot may fall in this category, so you have to say Y to let
15260 Zorro device name database
15262 By default, the kernel contains a database of all known Zorro device
15263 names to make the information in /proc/iomem comprehensible to the
15264 user. This database increases the size of the kernel image by about
15265 15KB, but it gets freed after the system boots up, so it doesn't
15266 take up kernel memory. Anyway, if you are building an installation
15267 floppy or kernel for an embedded system where kernel image size
15268 really matters, you can disable this feature and you'll get device
15269 ID numbers instead of names.
15271 When in doubt, say Y.
15273 Amiga 1200/600 PCMCIA support (EXPERIMENTAL)
15274 CONFIG_AMIGA_PCMCIA
15275 Include support in the kernel for pcmcia on Amiga 1200 and Amiga
15276 600. If you intend to use pcmcia cards say Y; otherwise say N.
15278 Amiga Zorro II ramdisk support
15280 This enables support for using Chip RAM and Zorro II RAM as a
15281 ramdisk or as a swap partition. Say Y if you want to include this
15282 driver in the kernel. This driver is also available as a module
15283 ( = code which can be inserted in and removed from the running
15284 kernel whenever you want). The module is called z2ram.o. If you want
15285 to compile it as a module, say M here and read
15286 Documentation/modules.txt.
15288 Atari ST-RAM swap support
15290 This enables support for using (parts of) ST-RAM as swap space,
15291 instead of as normal system memory. This can first enhance system
15292 performance if you have lots of alternate RAM (compared to the size
15293 of ST-RAM), because executable code always will reside in faster
15294 memory. ST-RAM will remain as ultra-fast swap space. On the other
15295 hand, it allows much improved dynamic allocations of ST-RAM buffers
15296 for device driver modules (e.g. floppy, ACSI, SLM printer, DMA
15297 sound). The probability that such allocations at module load time
15298 fail is drastically reduced.
15302 This enables support for the Atari ACSI interface. The driver
15303 supports hard disks and CD-ROMs, which have 512-byte sectors, or can
15304 be switched to that mode. Due to the ACSI command format, only disks
15305 up to 1 GB are supported. Special support for certain ACSI to SCSI
15306 adapters, which could relax that, isn't included yet. The ACSI
15307 driver is also the basis for certain other drivers for devices
15308 attached to the ACSI bus: Atari SLM laser printer, BioNet-100
15309 Ethernet, and PAMsNet Ethernet. If you want to use one of these
15310 devices, you need ACSI support, too.
15312 This driver is also available as a module ( = code which can be
15313 inserted in and removed from the running kernel whenever you want).
15314 The module will be called acsi.o.
15316 Probe all LUNs on each ACSI device
15317 CONFIG_ACSI_MULTI_LUN
15318 If you have a ACSI device that supports more than one LUN (Logical
15319 Unit Number), e.g. a CD jukebox, you should say Y here so that all
15320 will be found by the ACSI driver. An ACSI device with multiple LUNs
15321 acts logically like multiple ACSI devices. The vast majority of ACSI
15322 devices have only one LUN, and so most people can say N here and
15323 should in fact do so, because it is safer.
15325 Atari SLM laser printer support
15327 If you have an Atari SLM laser printer, say Y to include support for
15328 it in the kernel. Otherwise, say N. This driver is also available as
15329 a module ( = code which can be inserted in and removed from the
15330 running kernel whenever you want). The module will be called
15331 acsi_slm.o. Be warned: the driver needs much ST-RAM and can cause
15332 problems due to that fact!
15334 A3000 WD33C93A support
15336 If you have an Amiga 3000 and have SCSI devices connected to the
15337 built-in SCSI controller, say Y. Otherwise, say N. This driver is
15338 also available as a module ( = code which can be inserted in and
15339 removed from the running kernel whenever you want). The module is
15340 called wd33c93.o. If you want to compile it as a module, say M here
15341 and read Documentation/modules.txt.
15343 A2091 WD33C93A support
15345 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
15346 say N. This driver is also available as a module ( = code which can
15347 be inserted in and removed from the running kernel whenever you
15348 want). The module is called wd33c93.o. If you want to compile it as
15349 a module, say M here and read Documentation/modules.txt.
15351 GVP Series II WD33C93A support
15353 If you have a Great Valley Products Series II SCSI controller,
15354 answer Y. Also say Y if you have a later model of GVP SCSI
15355 controller (such as the GVP A4008 or a Combo board). Otherwise,
15356 answer N. This driver does NOT work for the T-Rex series of
15357 accelerators from TekMagic and GVP-M.
15359 This driver is also available as a module ( = code which can be
15360 inserted in and removed from the running kernel whenever you
15361 want). The module will be called gvp11.o. If you want to compile it
15362 as a module, say M here and read Documentation/modules.txt.
15364 Cyberstorm SCSI support
15365 CONFIG_CYBERSTORM_SCSI
15366 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
15367 accelerator board and the optional Cyberstorm SCSI controller,
15368 answer Y. Otherwise, say N.
15370 Cyberstorm II SCSI support
15371 CONFIG_CYBERSTORMII_SCSI
15372 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
15373 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
15376 Blizzard 2060 SCSI support (EXPERIMENTAL)
15377 CONFIG_BLZ2060_SCSI
15378 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
15379 and want to use the onboard SCSI controller, say Y. Otherwise,
15382 Blizzard 1230IV/1260 SCSI support
15383 CONFIG_BLZ1230_SCSI
15384 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
15385 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
15388 Blizzard PowerUP 603e+ SCSI support
15389 CONFIG_BLZ603EPLUS_SCSI
15390 If you have an Amiga 1200 with a Phase5 Blizzard PowerUP 603e+
15391 accelerator, say Y. Otherwise, say N.
15393 Fastlane SCSI support
15394 CONFIG_FASTLANE_SCSI
15395 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
15396 one in the near future, say Y to this question. Otherwise, say N.
15398 Atari native SCSI support
15400 If you have an Atari with built-in NCR5380 SCSI controller (TT,
15401 Falcon, ...) say Y to get it supported. Of course also, if you have
15402 a compatible SCSI controller (e.g. for Medusa). This driver is also
15403 available as a module ( = code which can be inserted in and removed
15404 from the running kernel whenever you want). The module is called
15405 atari_scsi.o. If you want to compile it as a module, say M here and
15406 read Documentation/modules.txt. This driver supports both styles of
15407 NCR integration into the system: the TT style (separate DMA), and
15408 the Falcon style (via ST-DMA, replacing ACSI). It does NOT support
15409 other schemes, like in the Hades (without DMA).
15411 Long delays for Toshiba CD-ROMs
15412 CONFIG_ATARI_SCSI_TOSHIBA_DELAY
15413 This option increases the delay after a SCSI arbitration to
15414 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
15415 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
15416 would impact performance a bit, so say N.
15418 Hades SCSI DMA emulator
15420 This option enables code which emulates the TT SCSI DMA chip on the
15421 Hades. This increases the SCSI transfer rates at least ten times
15422 compared to PIO transfers.
15426 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
15429 This driver is also available as a module ( = code which can be
15430 inserted in and removed from the running kernel whenever you
15431 want). The module is called ariadne.o. If you want to compile it as
15432 a module, say M here and read Documentation/modules.txt.
15436 If you have a Village Tronic Ariadne II Ethernet adapter, say Y.
15439 This driver is also available as a module ( = code which can be
15440 inserted in and removed from the running kernel whenever you
15441 want). The module is called ariadne2.o. If you want to compile it as
15442 a module, say M here and read Documentation/modules.txt.
15446 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
15449 This driver is also available as a module ( = code which can be
15450 inserted in and removed from the running kernel whenever you
15451 want). The module is called a2065.o. If you want to compile it as a
15452 module, say M here and read Documentation/modules.txt.
15456 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
15458 This driver is also available as a module ( = code which can be
15459 inserted in and removed from the running kernel whenever you
15460 want). The module is called hydra.o. If you want to compile it as a
15461 module, say M here and read Documentation/modules.txt.
15463 Pcmcia NE2000 compatible support
15465 If you have a pcmcia ne2000 compatible adapter, say Y. Otherwise,
15468 This driver is also available as a module ( = code which can be
15469 inserted in and removed from the running kernel whenever you
15470 want). The module is called apne.o. If you want to compile it as a
15471 module, say M here and read Documentation/modules.txt.
15473 Atari Lance support
15475 Say Y to include support for several Atari Ethernet adapters based
15476 on the AMD Lance chipset: RieblCard (with or without battery), or
15477 PAMCard VME (also the version by Rhotron, with different addresses).
15480 CONFIG_ATARI_BIONET
15481 Say Y to include support for BioData's BioNet-100 Ethernet adapter
15482 for the ACSI port. The driver works (has to work...) with a polled
15483 I/O scheme, so it's rather slow :-(
15486 CONFIG_ATARI_PAMSNET
15487 Say Y to include support for the PAMsNet Ethernet adapter for the
15488 ACSI port ("ACSI node"). The driver works (has to work...) with a
15489 polled I/O scheme, so it's rather slow :-(
15491 Amiga mouse support
15493 If you want to be able to use an Amiga mouse in Linux, say Y.
15495 This driver is also available as a module ( = code which can be
15496 inserted in and removed from the running kernel whenever you want).
15497 The module is called amigamouse.o. If you want to compile it as a
15498 module, say M here and read Documentation/modules.txt.
15500 Atari mouse support
15502 If you want to be able to use an Atari mouse in Linux, say Y.
15504 This driver is also available as a module ( = code which can be
15505 inserted in and removed from the running kernel whenever you want).
15506 The module is called atarimouse.o. If you want to compile it as a
15507 module, say M here and read Documentation/modules.txt.
15509 Atari MFP serial support
15510 CONFIG_ATARI_MFPSER
15511 If you like to use the MFP serial ports ("Modem1", "Serial1") under
15512 Linux, say Y. The driver equally supports all kinds of MFP serial
15513 ports and automatically detects whether Serial1 is available.
15515 This driver is also available as a module ( = code which can be
15516 inserted in and removed from the running kernel whenever you want).
15517 If you want to compile it as a module, say M here and read
15518 Documentation/modules.txt.
15520 Note for Falcon users: You also have an MFP port, it's just not
15521 wired to the outside... But you could use the port under Linux.
15523 Atari SCC serial support
15525 If you have serial ports based on a Zilog SCC chip (Modem2, Serial2,
15526 LAN) and like to use them under Linux, say Y. All built-in SCC's are
15527 supported (TT, MegaSTE, Falcon), and also the ST-ESCC. If you have
15528 two connectors for channel A (Serial2 and LAN), they are visible as
15529 two separate devices.
15531 This driver is also available as a module ( = code which can be
15532 inserted in and removed from the running kernel whenever you want).
15533 If you want to compile it as a module, say M here and read
15534 Documentation/modules.txt.
15536 Atari SCC serial DMA support
15537 CONFIG_ATARI_SCC_DMA
15538 This enables DMA support for receiving data on channel A of the SCC.
15539 If you have a TT you may say Y here and read
15540 drivers/char/atari_SCC.README. All other users should say N here,
15541 because only the TT has SCC-DMA, even if your machine keeps claiming
15544 Atari MIDI serial support
15546 If you want to use your Atari's MIDI port in Linux, say Y.
15548 This driver is also available as a module ( = code which can be
15549 inserted in and removed from the running kernel whenever you
15550 want). If you want to compile it as a module, say M here and read
15551 Documentation/modules.txt.
15553 Atari DSP56k Digital Signal Processor support (EXPERIMENTAL)
15554 CONFIG_ATARI_DSP56K
15555 If you want to be able to use the DSP56001 in Falcons, say Y. This
15556 driver is still experimental, and if you don't know what it is, or
15557 if you don't have this processor, just say N.
15559 This driver is also available as a module ( = code which can be
15560 inserted in and removed from the running kernel whenever you want).
15561 If you want to compile it as a module, say M here and read
15562 Documentation/modules.txt.
15564 Amiga builtin serial support
15565 CONFIG_AMIGA_BUILTIN_SERIAL
15566 If you want to use your Amiga's built-in serial port in Linux,
15569 This driver is also available as a module ( = code which can be
15570 inserted in and removed from the running kernel whenever you
15571 want). If you want to compile it as a module, say M here and read
15572 Documentation/modules.txt.
15574 GVP IO-Extender support
15576 If you want to use a GVP IO-Extender serial card in Linux, say Y.
15579 Multiface Card III serial support
15580 CONFIG_MULTIFACE_III_TTY
15581 If you want to use a Multiface III card's serial port in Linux,
15584 This driver is also available as a module ( = code which can be
15585 inserted in and removed from the running kernel whenever you want).
15586 If you want to compile it as a module, say M here and read
15587 Documentation/modules.txt.
15589 Atari DMA sound support
15590 CONFIG_DMASOUND_ATARI
15591 If you want to use the internal audio of your Atari in Linux, answer
15592 Y to this question. This will provide a Sun-like /dev/audio,
15593 compatible with the Linux/i386 sound system. Otherwise, say N.
15595 This driver is also available as a module ( = code which can be
15596 inserted in and removed from the running kernel whenever you
15597 want). If you want to compile it as a module, say M here and read
15598 Documentation/modules.txt.
15600 PowerMac DMA sound support
15601 CONFIG_DMASOUND_AWACS
15602 If you want to use the internal audio of your PowerMac in Linux,
15603 answer Y to this question. This will provide a Sun-like /dev/audio,
15604 compatible with the Linux/i386 sound system. Otherwise, say N.
15606 This driver is also available as a module ( = code which can be
15607 inserted in and removed from the running kernel whenever you
15608 want). If you want to compile it as a module, say M here and read
15609 Documentation/modules.txt.
15611 Amiga DMA sound support
15612 CONFIG_DMASOUND_PAULA
15613 If you want to use the internal audio of your Amiga in Linux, answer
15614 Y to this question. This will provide a Sun-like /dev/audio,
15615 compatible with the Linux/i386 sound system. Otherwise, say N.
15617 This driver is also available as a module ( = code which can be
15618 inserted in and removed from the running kernel whenever you
15619 want). If you want to compile it as a module, say M here and read
15620 Documentation/modules.txt.
15623 CONFIG_DMASOUND_Q40
15624 If you want to use the internal audio of your Q40 in Linux, answer
15625 Y to this question. This will provide a Sun-like /dev/audio,
15626 compatible with the Linux/i386 sound system. Otherwise, say N.
15628 This driver is also available as a module ( = code which can be
15629 inserted in and removed from the running kernel whenever you
15630 want). If you want to compile it as a module, say M here and read
15631 Documentation/modules.txt.
15633 HP DCA serial support
15635 If you want to use the internal "DCA" serial ports on an HP300
15636 machine, say Y here.
15638 HP on-board LANCE support
15640 If you want to use the builtin "LANCE" Ethernet controller on an
15641 HP300 machine, say Y here.
15645 Say Y here to enable support for the "DIO" expansion bus used in
15646 HP300 machines. If you are using such a system you almost certainly
15651 There are four types of PowerPC chips supported. The more common
15652 types (601, 603, 604, 740, 750), the Motorola embedded versions
15653 (821, 823, 850, 855, 860), the IBM embedded versions (403 and
15654 405) and the high end 64 bit Power processors (Power 3, Power 4).
15655 Unless you are building a kernel for one of the embedded
15656 processor systems, or a 64 bit IBM RS/6000, choose 6xx. Note that
15657 the kernel runs in 32-bit mode even on 64-bit chips.
15661 Linux currently supports several different kinds of PowerPC-based
15662 machines: Apple Power Macintoshes and clones (such as the Motorola
15663 Starmax series), PReP (PowerPC Reference Platform) machines such as
15664 the Motorola PowerStack, Amiga Power-Up systems (APUS), CHRP and the
15665 embedded MBX boards from Motorola. Currently, a single kernel binary
15666 only supports one type or the other. However, there is very early
15667 work on support for CHRP, PReP and PowerMac's from a single binary.
15669 Power management support for PowerBooks
15671 This provides support for putting a PowerBook to sleep; it also
15672 enables media bay support. Power management works on the
15673 PB2400/3400/3500, Wallstreet, Lombard, and Bronze PowerBook G3. You
15674 must get the power management daemon, pmud, to make it work and you
15675 must have the /dev/pmu device (see the pmud README).
15677 Get pmud from ftp://linuxcare.com.au/pub/ppclinux/pmud/
15679 If you have a PowerBook, you should say Y.
15681 You may also want to compile the dma sound driver as a module and
15682 have it autoloaded. The act of removing the module shuts down the
15683 sound hardware for more power savings.
15685 Mac-on-Linux support
15687 This option enables low-level support for Mac-on-Linux.
15688 MOL lets you run MacOS and Linux simultaneously. Please
15689 visit <http://www.maconlinux.org> for more information.
15692 ADB raw keycode support
15693 CONFIG_MAC_ADBKEYCODES
15694 This provides support for sending raw ADB keycodes to console
15695 devices. This is the default up to 2.4.0, but in future this may be
15696 phased out in favor of generic Linux keycodes. If you say Y here, you
15697 can dynamically switch via the
15698 /proc/sys/dev/mac_hid/keyboard_sends_linux_keycodes
15699 sysctl and with the "keyboard_sends_linux_keycodes=" kernel argument.
15701 If unsure, say Y here.
15703 Mouse button 2+3 emulation support
15704 CONFIG_MAC_EMUMOUSEBTN
15705 This provides generic support for emulating the 2nd and 3rd mouse
15706 button with keypresses. If you say Y here, the emulation is still
15707 disabled by default. The emulation is controlled by these sysctl entries:
15708 /proc/sys/dev/mac_hid/mouse_button_emulation
15709 /proc/sys/dev/mac_hid/mouse_button2_keycode
15710 /proc/sys/dev/mac_hid/mouse_button3_keycode
15712 Enhanced Real Time Clock Support
15714 If you say Y here and create a character special file /dev/rtc with
15715 major number 10 and minor number 135 using mknod ("man mknod"), you
15716 will get access to the real time clock (or hardware clock) built
15717 into your computer.
15719 If unsure, say Y here.
15721 Support for Open Firmware device tree in /proc
15722 CONFIG_PROC_DEVICETREE
15723 This option adds a device-tree directory under /proc which contains
15724 an image of the device tree that the kernel copies from Open
15725 Firmware. If unsure, say Y here.
15727 MESH (Power Mac internal SCSI) support
15729 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
15730 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
15731 other Power Macintoshes do). Say Y to include support for this SCSI
15732 adaptor. This driver is also available as a module called mesh.o
15733 ( = code which can be inserted in and removed from the running
15734 kernel whenever you want). If you want to compile it as a module,
15735 say M here and read Documentation/modules.txt.
15737 Maximum synchronous transfer rate
15738 CONFIG_SCSI_MESH_SYNC_RATE
15739 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
15740 drives a bus which is entirely internal to the machine (such as the
15741 7500, 7600, 8500, etc.), the MESH is capable of synchronous
15742 operation at up to 10 MB/s. On machines where the SCSI bus
15743 controlled by the MESH can have external devices connected, it is
15744 usually rated at 5 MB/s. 5 is a safe value here unless you know the
15745 MESH SCSI bus is internal only; in that case you can say 10. Say 0
15746 to disable synchronous operation.
15748 53C94 (Power Mac external SCSI) support
15749 CONFIG_SCSI_MAC53C94
15750 On Power Macintoshes (and clones) with two SCSI buses, the external
15751 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
15752 machines which only have one SCSI bus, such as the 7200, also use
15753 the 53C94. Say Y to include support for the 53C94.
15755 This driver is also available as a module called mac53c94.o ( = code
15756 which can be inserted in and removed from the running kernel
15757 whenever you want). If you want to compile it as a module, say M
15758 here and read Documentation/modules.txt.
15760 MACE (Power Mac Ethernet) support
15762 Power Macintoshes and clones with Ethernet built-in on the
15763 motherboard will usually use a MACE (Medium Access Control for
15764 Ethernet) interface. Say Y to include support for the MACE chip.
15766 This driver is also available as a module called mace.o ( = code
15767 which can be inserted in and removed from the running kernel
15768 whenever you want). If you want to compile it as a module, say M
15769 here and read Documentation/modules.txt.
15771 BMAC (G3 ethernet) support
15773 Say Y for support of BMAC Ethernet interfaces. These are used on G3
15776 This driver is also available as a module called bmac.o ( = code
15777 which can be inserted in and removed from the running kernel
15778 whenever you want). If you want to compile it as a module, say M
15779 here and read Documentation/modules.txt.
15781 GMAC (G4/iBook ethernet) support
15783 Say Y for support of GMAC Ethernet interfaces. These are used on G4
15784 and iBook computers.
15786 This driver is also available as a module called gmac.o ( = code
15787 which can be inserted in and removed from the running kernel
15788 whenever you want). If you want to compile it as a module, say M
15789 here and read Documentation/modules.txt.
15791 Symbios 53c885 (Synergy ethernet) support
15793 This is and Ethernet driver for the dual-function NCR 53C885
15794 SCSI/Ethernet controller.
15796 This driver is also available as a module called ncr885e.o ( = code
15797 which can be inserted in and removed from the running kernel
15798 whenever you want). If you want to compile it as a module, say M
15799 here and read Documentation/modules.txt.
15801 National DP83902AV (Oak ethernet) support
15803 Say Y if your machine has this type of Ethernet network card.
15805 This driver is also available as a module called oaknet.o ( = code
15806 which can be inserted in and removed from the running kernel
15807 whenever you want). If you want to compile it as a module, say M
15808 here and read Documentation/modules.txt.
15812 Support for audio/video capture and overlay devices and FM radio
15813 cards. The exact capabilities of each device vary. User tools for
15814 this are available from
15815 ftp://ftp.uk.linux.org/pub/linux/video4linux .
15817 If you are interested in writing a driver for such an audio/video
15818 device or user software interacting with such a driver, please read
15819 the file Documentation/video4linux/API.html.
15821 This driver is also available as a module called videodev.o ( = code
15822 which can be inserted in and removed from the running kernel
15823 whenever you want). If you want to compile it as a module, say M
15824 here and read Documentation/modules.txt.
15826 Video For Linux /proc file system information
15827 CONFIG_VIDEO_PROC_FS
15828 If you say Y here, you are able to access video device information
15831 To use this option, you have to check, that the "/proc file system
15832 support" (CONFIG_PROC_FS) is enabled too.
15834 AIMSlab RadioTrack (aka RadioReveal) support
15835 CONFIG_RADIO_RTRACK
15836 Choose Y here if you have one of these FM radio cards, and then fill
15837 in the port address below.
15839 Note that newer AIMSlab RadioTrack cards have a different chipset
15840 and are not supported by this driver. For these cards, use the
15841 RadioTrack II driver below.
15843 If you have a GemTeks combined (PnP) sound- and radio card you must
15844 use this driver as a module and setup the card with isapnptools. You
15845 must also pass the module a suitable io parameter, 0x248 has been
15846 reported to be used by these cards.
15848 In order to control your radio card, you will need to use programs
15849 that are compatible with the Video for Linux API. Information on
15850 this API and pointers to "v4l" programs may be found on the WWW at
15851 http://roadrunner.swansea.uk.linux.org/v4l.shtml . More information
15852 is contained in the file Documentation/video4linux/radiotrack.txt.
15854 If you want to compile this driver as a module ( = code which can be
15855 inserted in and removed from the running kernel whenever you want),
15856 say M here and read Documentation/modules.txt. The module will be
15857 called radio-aimslab.o.
15859 RadioTrack i/o port
15860 CONFIG_RADIO_RTRACK_PORT
15861 Enter either 0x30f or 0x20f here. The card default is 0x30f, if you
15862 haven't changed the jumper setting on the card.
15864 AIMSlab RadioTrack II support
15865 CONFIG_RADIO_RTRACK2
15866 Choose Y here if you have this FM radio card, and then fill in the
15867 port address below.
15869 In order to control your radio card, you will need to use programs
15870 that are compatible with the Video for Linux API. Information on
15871 this API and pointers to "v4l" programs may be found on the WWW at
15872 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15874 If you want to compile this driver as a module ( = code which can be
15875 inserted in and removed from the running kernel whenever you want),
15876 say M here and read Documentation/modules.txt. The module will be
15877 called radio-rtrack2.o.
15879 RadioTrack II i/o port
15880 CONFIG_RADIO_RTRACK2_PORT
15881 Enter either 0x30c or 0x20c here. The card default is 0x30c, if you
15882 haven't changed the jumper setting on the card.
15884 Aztech/Packard Bell Radio
15885 CONFIG_RADIO_AZTECH
15886 Choose Y here if you have one of these FM radio cards, and then fill
15887 in the port address below.
15889 In order to control your radio card, you will need to use programs
15890 that are compatible with the Video for Linux API. Information on
15891 this API and pointers to "v4l" programs may be found on the WWW at
15892 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15894 If you want to compile this driver as a module ( = code which can be
15895 inserted in and removed from the running kernel whenever you want),
15896 say M here and read Documentation/modules.txt. The module will be
15897 called radio-aztech.o.
15899 Aztech/Packard Bell radio card i/o port
15900 CONFIG_RADIO_AZTECH_PORT
15901 Enter either 0x350 or 0x358 here. The card default is 0x350, if you
15902 haven't changed the setting of jumper JP3 on the card. Removing the
15903 jumper sets the card to 0x358.
15905 ADS Cadet AM/FM Radio Tuner Card
15907 Choose Y here if you have one of these AM/FM radio cards, and then
15908 fill in the port address below.
15910 In order to control your radio card, you will need to use programs
15911 that are compatible with the Video for Linux API. Information on
15912 this API and pointers to "v4l" programs may be found on the WWW at
15913 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15915 Further documentation on this driver can be found on the WWW at
15916 http://linux.blackhawke.net/cadet.html .
15918 If you want to compile this driver as a module ( = code which can be
15919 inserted in and removed from the running kernel whenever you want),
15920 say M here and read Documentation/modules.txt. The module will be
15921 called radio-cadet.o.
15924 CONFIG_RADIO_SF16FMI
15925 Choose Y here if you have one of these FM radio cards, and then fill
15926 in the port address below.
15928 In order to control your radio card, you will need to use programs
15929 that are compatible with the Video for Linux API. Information on
15930 this API and pointers to "v4l" programs may be found on the WWW at
15931 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15933 If you want to compile this driver as a module ( = code which can be
15934 inserted in and removed from the running kernel whenever you want),
15935 say M here and read Documentation/modules.txt. The module will be
15936 called radio-sf16fmi.o
15938 SF16FMI I/O port (0x284 or 0x384)
15939 CONFIG_RADIO_SF16FMI_PORT
15940 Enter the I/O port of your SF16FMI radio card.
15943 CONFIG_RADIO_TYPHOON
15944 Choose Y here if you have one of these FM radio cards, and then fill
15945 in the port address and the frequency used for muting below.
15947 In order to control your radio card, you will need to use programs
15948 that are compatible with the Video for Linux API. Information on
15949 this API and pointers to "v4l" programs may be found on the WWW at
15950 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15952 If you want to compile this driver as a module ( = code which can be
15953 inserted in and removed from the running kernel whenever you want),
15954 say M here and read Documentation/modules.txt. The module will be
15955 called radio-typhoon.o
15957 Support for /proc/radio-typhoon
15958 CONFIG_RADIO_TYPHOON_PROC_FS
15959 Say Y here if you want the typhoon radio card driver to write
15960 status information (frequency, volume, muted, mute frequency,
15961 base address) to /proc/radio-typhoon. The file can be viewed with
15962 your favorite pager (i.e. use "more /proc/radio-typhoon" or "less
15963 /proc/radio-typhoon" or simply "cat /proc/radio-typhoon").
15965 Typhoon I/O port (0x316 or 0x336)
15966 CONFIG_RADIO_TYPHOON_PORT
15967 Enter the I/O port of your Typhoon or EcoRadio radio card.
15969 Typhoon frequency set when muting the device (kHz)
15970 CONFIG_RADIO_TYPHOON_MUTEFREQ
15971 Enter the frequency used for muting the radio. The device is never
15972 completely silent. If the volume is just turned down, you can still
15973 hear silent voices and music. For that reason, the frequency of the
15974 radio device is set to the frequency you can enter here whenever
15975 the device is muted. There should be no local radio station at that
15979 CONFIG_RADIO_ZOLTRIX
15980 Choose Y here if you have one of these FM radio cards, and then fill
15981 in the port address below.
15983 In order to control your radio card, you will need to use programs
15984 that are compatible with the Video for Linux API. Information on
15985 this API and pointers to "v4l" programs may be found on the WWW at
15986 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15988 If you want to compile this driver as a module ( = code which can be
15989 inserted in and removed from the running kernel whenever you want),
15990 say M here and read Documentation/modules.txt. The module will be
15991 called radio-zoltrix.o
15993 ZOLTRIX I/O port (0x20c or 0x30c)
15994 CONFIG_RADIO_ZOLTRIX_PORT
15995 Enter the I/O port of your Zoltrix radio card.
15997 IIC on parallel port
15999 I2C is a simple serial bus system used in many micro controller
16000 applications. Saying Y here will allow you to use your parallel port
16001 as an I2C interface.
16003 If you want to compile this driver as a module ( = code which can be
16004 inserted in and removed from the running kernel whenever you want),
16005 say M here and read Documentation/modules.txt. The module will be
16006 called i2c-parport.o.
16009 CONFIG_RADIO_MIROPCM20
16010 Choose Y here if you have this FM radio card. You also need to say Y
16011 to "ACI mixer (miroPCM12/PCM20)" (in "additional low level sound
16012 drivers") for this to work.
16014 In order to control your radio card, you will need to use programs
16015 that are compatible with the Video for Linux API. Information on
16016 this API and pointers to "v4l" programs may be found on the WWW at
16017 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
16019 If you want to compile this driver as a module ( = code which can be
16020 inserted in and removed from the running kernel whenever you want),
16021 say M here and read Documentation/modules.txt. The module will be
16022 called radio-miropcm20.o
16025 CONFIG_RADIO_GEMTEK
16026 Choose Y here if you have this FM radio card, and then fill in the
16027 port address below.
16029 In order to control your radio card, you will need to use programs
16030 that are compatible with the Video for Linux API. Information on
16031 this API and pointers to "v4l" programs may be found on the WWW at
16032 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
16034 If you want to compile this driver as a module ( = code which can be
16035 inserted in and removed from the running kernel whenever you want),
16036 say M here and read Documentation/modules.txt. The module will be
16037 called radio-gemtek.o.
16040 CONFIG_RADIO_GEMTEK_PORT
16041 Enter either 0x20c, 0x30c, 0x24c or 0x34c here. The card default is
16042 0x34c, if you haven't changed the jumper setting on the card. On
16043 Sound Vision 16 Gold PnP with FM Radio (ESS1869+FM Gemtek), the i/o
16046 PlanB Video-In for PowerMacs
16048 PlanB is the V4L driver for the PowerMac 7x00/8x00 series video
16049 input hardware. If you want to experiment with this, say Y.
16050 Otherwise, or if you don't understand a word, say N.
16051 See http://www.cpu.lu/~mlan/planb.html for more info.
16053 Saying M will compile this driver as a module (planb.o).
16055 TerraTec ActiveRadio
16056 CONFIG_RADIO_TERRATEC
16057 Choose Y here if you have this FM radio card, and then fill in the
16058 port address below. (TODO)
16060 Note: This driver is in its early stages. Right now volume and
16061 frequency control and muting works at least for me, but
16062 unfortunately i have not found anybody who wants to use this card
16063 with Linux. So if it is this what YOU are trying to do right now,
16064 PLEASE DROP ME A NOTE!! Rolf Offermanns (rolf@offermanns.de)
16066 In order to control your radio card, you will need to use programs
16067 that are compatible with the Video for Linux API. Information on
16068 this API and pointers to "v4l" programs may be found on the WWW at
16069 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
16071 If you want to compile this driver as a module ( = code which can be
16072 inserted in and removed from the running kernel whenever you want),
16073 say M here and read Documentation/modules.txt. The module will be
16074 called radio-terratec.o.
16076 Terratec i/o port (normally 0x590)
16077 CONFIG_RADIO_TERRATEC_PORT
16078 Fill in the i/o port of your TerraTec FM radio card. If unsure, go
16082 # Zoran ZR36057/36060 support
16083 # CONFIG_VIDEO_ZORAN
16085 # Include support for Iomega Buz
16088 Trust FM radio card
16090 This is a driver for the Trust FM radio cards. Say Y if you have
16091 such a card and want to use it under Linux.
16093 This driver is also available as a module called radio-trust.o ( =
16094 code which can be inserted in and removed from the running kernel
16095 whenever you want). If you want to compile it as a module, say M
16096 here and read Documentation/modules.txt.
16098 Trust i/o port (usually 0x350 or 0x358)
16099 CONFIG_RADIO_TRUST_PORT
16100 Enter the i/o port of your Trust FM radio card. If unsure, try the
16101 values "0x350" or "0x358".
16103 BT848 Video For Linux
16105 Support for BT848 based frame grabber/overlay boards. This includes
16106 the Miro, Hauppauge and STB boards. Please read the material in
16107 Documentation/video4linux/bttv for more information.
16109 If you say Y or M here, you need to say Y or M to "I2C support" and
16110 "I2C bit-banging interfaces" in the character device section.
16112 This driver is available as a module called bttv.o ( = code
16113 which can be inserted in and removed from the running kernel
16114 whenever you want). If you want to compile it as a module, say M
16115 here and read Documentation/modules.txt.
16117 ZR36120/36125 Video for Linux
16118 CONFIG_VIDEO_ZR36120
16119 Support for ZR36120/ZR36125 based frame grabber/overlay boards.
16120 This includes the Victor II, WaveWatcher, Video Wonder, Maxi-TV,
16121 and Buster boards. Please read the material in
16122 Documentation/video4linux/zr36120.txt for more information.
16124 This driver is also available as a module called zr36120.o ( = code
16125 which can be inserted in and removed from the running kernel
16126 whenever you want). If you want to compile it as a module, say M
16127 here and read Documentation/modules.txt.
16129 SAA5249 Teletext processor
16130 CONFIG_VIDEO_SAA5249
16131 Support for I2C bus based teletext using the SAA5249 chip. At the
16132 moment this is only useful on some European WinTV cards.
16134 This driver is also available as a module called saa5249.o ( = code
16135 which can be inserted in and removed from the running kernel
16136 whenever you want). If you want to compile it as a module, say M
16137 here and read Documentation/modules.txt.
16139 Quickcam BW Video For Linux
16140 CONFIG_VIDEO_BWQCAM
16141 Say Y have if you the black and white version of the QuickCam
16142 camera. See the next option for the color version.
16144 This driver is also available as a module called bw-qcam.o ( = code
16145 which can be inserted in and removed from the running kernel
16146 whenever you want). If you want to compile it as a module, say M
16147 here and read Documentation/modules.txt.
16149 Colour QuickCam Video For Linux
16151 This is the video4linux driver for the colour version of the
16152 Connectix Quickcam. If you have one of these cameras, say Y here,
16153 otherwise say N. This driver does not work with the original
16154 monochrome Quickcam, Quickcam VC or QuickClip. It is also available
16155 as a module (c-qcam.o). Read Documentation/video4linux/CQcam.txt for
16158 CPiA Video For Linux
16160 This is the video4linux driver for cameras based on Vision's CPiA
16161 (Colour Processor Interface ASIC), such as the Creative Labs Video
16162 Blaster Webcam II. If you have one of these cameras, say Y here
16163 and select parallel port and/or USB lowlevel support below,
16164 otherwise say N. This will not work with the Creative Webcam III.
16166 Please read Documentation/video4linux/README.cpia for more
16169 This driver is also available as a module (cpia.o).
16171 CPiA Parallel Port Lowlevel Support
16172 CONFIG_VIDEO_CPIA_PP
16173 This is the lowlevel parallel port support for cameras based on
16174 Vision's CPiA (Colour Processor Interface ASIC), such as the
16175 Creative Webcam II. If you have the parallel port version of one
16176 of these cameras, say Y here, otherwise say N. It is also available
16177 as a module (cpia_pp.o).
16179 CPiA USB Lowlevel Support
16180 CONFIG_VIDEO_CPIA_USB
16181 This is the lowlevel USB support for cameras based on Vision's CPiA
16182 (Colour Processor Interface ASIC), such as the Creative Webcam II.
16183 If you have the USB version of one of these cameras, say Y here,
16184 otherwise say N. This will not work with the Creative Webcam III.
16185 It is also available as a module (cpia_usb.o).
16187 Mediavision Pro Movie Studio Video For Linux
16189 Say Y if you have such a thing. This driver is also available as a
16190 module called pms.o ( = code which can be inserted in and removed
16191 from the running kernel whenever you want). If you want to compile
16192 it as a module, say M here and read Documentation/modules.txt.
16194 SAB3036 tuner support
16196 Say Y here to include support for Philips SAB3036 compatible tuners.
16197 If in doubt, say N.
16199 Compaq SMART2 support
16201 This is the driver for Compaq Smart Array controllers.
16202 Everyone using these boards should say Y here.
16203 See the file Documentation/cpqarray.txt for the current list of
16204 boards supported by this driver, and for further information
16205 on the use of this driver.
16212 This selects what ARM system you wish to build the kernel for. It
16213 also selects to some extent the CPU type. If you are unsure what
16214 to set this option to, please consult any information supplied with
16217 2MB physical memory
16219 Say Y here if your Archimedes or A5000 system has only 2MB of
16220 memory, otherwise say N. The resulting kernel will not run on a
16221 machine with 4MB of memory.
16223 Include support for the CATS
16225 Say Y here if you intend to run this kernel on the CATS.
16227 Saying N will reduce the size of the Footbridge kernel.
16229 Include support for the EBSA285
16230 CONFIG_ARCH_EBSA285
16231 Say Y here if you intend to run this kernel on the EBSA285 card
16232 in host ("central function") mode.
16234 Saying N will reduce the size of the Footbridge kernel.
16236 Include support for the LinkUp Systems L7200 SDB
16238 Say Y here if you intend to run this kernel on a LinkUp Systems
16239 L7200 Software Development Board which uses an ARM720T processor.
16240 Information on this board can be obtained at:
16242 http://www.linkupsys.com/
16244 If you have any questions or comments about the Linux kernel port
16245 to this board, send e-mail to sjhill@cotw.com
16247 Include support for the NetWinder
16248 CONFIG_ARCH_NETWINDER
16249 Say Y here if you intend to run this kernel on the Rebel.COM
16250 NetWinder. Information about this machine can be found at:
16252 http://www.netwinder.org/
16254 Saying N will reduce the size of the Footbridge kernel.
16256 Include support for the Compaq Personal Server
16257 CONFIG_ARCH_PERSONAL_SERVER
16258 Say Y here if you intend to run this kernel on the Compaq
16261 Saying N will reduce the size of the Footbridge kernel.
16263 The Compaq Personal Server is not available for purchase.
16264 There are no product plans beyond the current research
16265 prototypes at this time. Information is available at:
16267 http://crl.research.compaq.com/projects/personalserver
16269 If you have any questions or comments about the Compaq Personal
16270 Server, send e-mail to skiff@crl.dec.com
16272 Include support for Assabet
16273 CONFIG_SA1100_ASSABET
16274 Say Y here if you are using the Intel(R) StrongARM(R) SA-1110
16275 Microprocessor Development Board (also known as the Assabet).
16277 Include support for Neponset
16278 CONFIG_ASSABET_NEPONSET
16279 Say Y here if you are using the Intel(R) StrongARM(R) SA-1110
16280 Microprocessor Development Board (Assabet) with the SA-1111
16281 Development Board (Nepon).
16283 Include support for the Compaq iPAQ H3600 (Bitsy)
16284 CONFIG_SA1100_BITSY
16285 Say Y here if you intend to run this kernel on the Compaq iPAQ
16286 H3600 handheld computer. Information about this machine and the
16287 Linux port to this machine can be found at:
16289 http://www.handhelds.org/Compaq/index.html#iPAQ_H3600
16290 http://www.compaq.com/products/handhelds/pocketpc/
16292 Include support for Brutus
16293 CONFIG_SA1100_BRUTUS
16294 Say Y here if you are using the Intel(R) StrongARM(R) SA-1100
16295 Microprocessor Development Board (also known as the Brutus).
16297 Include support for LART
16299 Say Y here if you are using the Linux Advanced Radio Terminal
16300 (also known as the LART). See http://www.lart.tudelft.nl/ for
16301 information on the LART.
16303 Include support for GraphicsClient
16304 CONFIG_SA1100_GRAPHICSCLIENT
16305 Say Y here if you are using an Applied Data Systems Intel(R)
16306 StrongARM(R) SA-1100 based Graphics Client SBC. See
16307 http://www.flatpanels.com/ for information on this system.
16309 Include support for Victor
16310 CONFIG_SA1100_VICTOR
16311 Say Y here if you are using a Visu Aide Intel(R) StrongARM(R)
16312 SA-1100 based Victor Digital Talking Book Reader. See
16313 http://www.visuaide.com/pagevictor.en.html for information on
16316 Support ARM610 processor
16318 Say Y here if you wish to include support for the ARM610 processor.
16320 Support ARM710 processor
16322 Say Y here if you wish to include support for the ARM710 processor.
16324 Support StrongARM(R) SA-110 processor
16326 Say Y here if you wish to include support for the Intel(R)
16327 StrongARM(R) SA-110 processor.
16329 Support ARM720 processor
16331 Say Y here if you wish to include support for the ARM720 processor.
16335 Say Y here if you wish to include support for the ARM920 processor.
16337 Support ARM610 processor
16339 Say Y here if you wish to include support for the ARM610 processor.
16341 Support ARM710 processor
16343 Say Y here if you wish to include support for the ARM710 processor.
16345 Support StrongARM(R) SA-110 processor
16347 Say Y here if you wish to include support for the Intel(R)
16348 StrongARM(R) SA-110 processor.
16350 Support ARM720 processor
16352 Say Y here if you wish to include support for the ARM720 processor.
16356 Say Y here if you wish to include support for the ARM920 processor.
16360 Say Y to include the NWFPE floating point emulator in the kernel.
16361 This is necessary to run most binaries. Linux does not currently
16362 support floating point hardware so you need to say Y here even if
16363 your machine has an FPA or floating point co-processor podule.
16365 It is also possible to say M to build the emulator as a module
16366 (nwfpe.o) or indeed to leave it out altogether. However, unless you
16367 know what you are doing this can easily render your machine
16368 unbootable. Saying Y is the safe option.
16370 You may say N here if you are going to load the Acorn FPEmulator
16371 early in the bootup.
16373 DS1620 Thermometer support
16375 Say Y here to include support for the thermal management hardware
16376 found in the NetWinder. This driver allows the user to control the
16377 temperature set points and to read the current temperature.
16379 It is also possible to say M here to build it as a module (ds1620.o)
16380 It is recommended to be used on a NetWinder, but it is not a
16383 Verbose kernel error messages
16384 CONFIG_DEBUG_ERRORS
16385 This option controls verbose debugging information which can be
16386 printed when the kernel detects an internal error. This debugging
16387 information is useful to kernel hackers when tracking down problems,
16388 but mostly meaningless to other people. It's safe to say Y unless
16389 you are concerned with the code size or don't want to see these
16392 Compile kernel with frame pointer
16393 CONFIG_FRAME_POINTER
16394 If you say Y here, the resulting kernel will be slightly larger and
16395 slower, but it will give useful debugging information. If you don't
16396 debug the kernel, you can say N.
16398 User fault debugging
16400 When a user program crashes due to an exception, the kernel can
16401 print a brief message explaining what the problem was. This is
16402 sometimes helpful for debugging but serves no purpose on a
16403 production system. Most people should say N here.
16405 Include gdb debugging information in kernel binary
16407 Say Y here to include source-level debugging information in the
16408 `vmlinux' binary image. This is handy if you want to use gdb or
16409 addr2line to debug the kernel. It has no impact on the in-memory
16410 footprint of the running kernel but it can increase the amount of
16411 time and disk space needed for compilation of the kernel. If in
16414 Kernel low-level debugging functions
16416 Say Y here to include definitions of printascii, printchar, printhex
16417 in the kernel. This is helpful if you are debugging code that
16418 executes before the console is initialized.
16420 Kernel low-level debugging messages via footbridge serial port
16421 CONFIG_DEBUG_DC21285_PORT
16422 Say Y here if you want the low-level print routines to direct their
16423 output to the serial port in the DC21285 (Footbridge).
16425 Split initialisation functions into discardable section
16426 CONFIG_TEXT_SECTIONS
16427 If you say Y here, kernel code that is only used during
16428 initialisation is collected into a special area of the kernel so
16429 that it can be discarded and the memory reclaimed when
16430 initialisation is complete. In addition, if the kernel you wish to
16431 build is able to run on multiple architectures, it allows the unused
16432 code to be discarded. Some versions of binutils, however, have a bug
16433 that causes the kernel to crash during startup when this option is
16434 enabled. Say Y unless you experience problems that you suspect may
16437 Disable pgtable cache (EXPERIMENTAL)
16438 CONFIG_NO_PGT_CACHE
16439 Normally the kernel maintains a `quicklist' of preallocated
16440 pagetable structures in order to increase performance. On machines
16441 with very few pages this may however be a loss. Say Y here to
16442 disable the pgtable cache.
16444 RISC OS personality
16446 Say Y here to include the kernel code necessary if you want to run
16447 Acorn RISC OS/Arthur binaries under Linux. This code is still very
16448 experimental; if this sounds frightening, say N and sleep in peace.
16449 You can also say M here to compile this support as a module (which
16450 will be called arthur.o).
16452 Initial kernel command line
16454 On some architectures (EBSA110 and CATS), there is currently no way
16455 for the boot loader to pass arguments to the kernel. For these
16456 architectures, you should supply some command-line options at build
16457 time by entering them here. As a minimum, you should specify the
16458 memory size and the root device (e.g., mem=64M root=/dev/nfs)
16460 Hardware alignment trap (EXPERIMENTAL)
16461 CONFIG_ALIGNMENT_TRAP
16462 ARM processors can not fetch/store information which is not
16463 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
16464 address divisible by 4. On 32-bit ARM processors, these non-aligned
16465 fetch/store instructions will be emulated in software if you say
16466 here, which has a severe performance impact. This is necessary for
16467 correct operation of some network protocols. With an IP-only
16468 configuration it is safe to say N, otherwise say Y.
16470 21285 serial port support
16471 CONFIG_SERIAL_21285
16472 If you have a machine based on a 21285 (Footbridge) StrongARM(R)/
16473 PCI bridge you can enable its onboard serial port by enabling this
16474 option. The device has major ID 4, minor 64.
16476 Console on 21285 serial port
16477 CONFIG_SERIAL_21285_CONSOLE
16478 If you have enabled the serial port on the 21285 footbridge you can
16479 make it the console by answering Y to this option.
16481 SA1100 serial port support
16482 CONFIG_SERIAL_SA1100
16483 If you have a machine based on a SA1100/SA1110 StrongARM CPU you can
16484 enable its onboard serial port by enabling this option.
16485 Please read Documentation/arm/SA1100/serial_UART for further info.
16487 Console on SA1100 serial port
16488 CONFIG_SERIAL_SA1100_CONSOLE
16489 If you have enabled the serial port on the SA1100/SA1110 StrongARM
16490 CPU you can make it the console by answering Y to this option.
16492 L7200 serial port support
16493 CONFIG_SERIAL_L7200
16494 If you have a LinkUp Systems L7200 board you can enable its two
16495 onboard serial ports by enabling this option. The device numbers
16496 are major ID 4 with minor 64 and 65 respectively.
16498 Console on L7200 serial port
16499 CONFIG_SERIAL_L7200_CONSOLE
16500 If you have enabled the serial ports on the L7200 development board
16501 you can make the first serial port the console by answering Y to
16505 CONFIG_HOST_FOOTBRIDGE
16506 The 21285 Footbridge chip can operate in either `host mode' or
16507 `add-in' mode. Say Y if your 21285 is in host mode, and therefore
16508 is the configuration master, otherwise say N. This must not be
16509 set to Y if the card is used in 'add-in' mode.
16511 MFM hard disk support
16513 Support the MFM hard drives on the Acorn Archimedes both
16514 on-board the A4x0 motherboards and via the Acorn MFM podules.
16515 Drives up to 64MB are supported. If you haven't got one of these
16516 machines or drives just say N.
16518 Old Archimedes floppy (1772) support
16519 CONFIG_BLK_DEV_FD1772
16520 Support the floppy drive on the Acorn Archimedes (A300, A4x0, A540,
16521 R140 and R260) series of computers; it supports only 720K floppies
16522 at the moment. If you don't have one of these machines just answer
16525 Autodetect hard drive geometry
16526 CONFIG_BLK_DEV_MFM_AUTODETECT
16527 If you answer Y, the MFM code will attempt to automatically detect
16528 the cylinders/heads/sectors count on your hard drive. WARNING: This
16529 sometimes doesn't work and it also does some dodgy stuff which
16530 potentially might damage your drive.
16532 NetWinder /dev/flash support
16534 If you say Y here and create a character device /dev/flash with
16535 major 10 and minor 160 you can manipulate the flash ROM containing
16536 the NetWinder firmware. Be careful as accidentally overwriting the
16537 flash contents can render your computer unbootable. On no account
16538 allow random users access to this device. :-)
16540 This driver is also available as a module ( = code which can be
16541 inserted in and removed from the running kernel whenever you want).
16542 The module will be called nwflash.o. If you want to compile it as a
16543 module, say M here and read Documentation/modules.txt.
16545 If you're not sure, say N.
16547 Footbridge internal watchdog
16548 CONFIG_21285_WATCHDOG
16549 The Intel Footbridge chip contains a builtin watchdog circuit. Say Y
16550 here if you wish to use this. Alternatively say M to compile the
16551 driver as a module, which will be called wdt285.o.
16553 This driver does not work on all machines. In particular, early CATS
16554 boards have hardware problems that will cause the machine to simply
16555 lock up if the watchdog fires.
16557 "If in doubt, leave it out" - say N.
16559 NetWinder WB977 watchdog
16560 CONFIG_977_WATCHDOG
16561 Say Y here to include support for the WB977 watchdog included in
16562 NetWinder machines. Alternatively say M to compile the driver as
16563 a module, which will be called wdt977.o.
16565 Not sure? It's safe to say N.
16567 IrDA subsystem support
16569 Say Y here if you want to build support for the IrDA (TM) protocols.
16570 The Infrared Data Associations (tm) specifies standards for wireless
16571 infrared communication and is supported by most laptops and PDA's.
16573 To use Linux support for the IrDA (tm) protocols, you will also need
16574 some user-space utilities like the irmanager and probably irattach
16575 as well. For more information, see the file
16576 Documentation/networking/irda.txt. You also want to read the
16577 IR-HOWTO, available at http://www.linuxdoc.org/docs.html#howto .
16579 This support is also available as a module called irda.o. If you
16580 want to compile it as a module, say M here and read
16581 Documentation/modules.txt.
16583 IrDA Cache last LSAP
16584 CONFIG_IRDA_CACHE_LAST_LSAP
16585 Say Y here if you want IrLMP to cache the last LSAP used. This makes
16586 sense since most frames will be sent/received on the same
16587 connection. Enabling this option will save a hash-lookup per frame.
16592 CONFIG_IRDA_FAST_RR
16593 Say Y here is you want IrLAP to send fast RR (Receive Ready) frames
16594 when acting as a primary station. This will make IrLAP send out a RR
16595 frame immediately when receiving a frame if its own transmit queue
16596 is currently empty. This will give a lot of speed improvement when
16597 receiving much data since the secondary station will not have to
16598 wait the max. turn around time before it is allowed to transmit the
16599 next time. If the transmit queue of the secondary is also empty the
16600 primary will back off waiting longer for sending out the RR frame
16601 until the timeout reaches the normal value. Enabling this option
16602 will make the IR-diode burn more power and thus reduce your battery
16609 Say Y here if you want the IrDA subsystem to write debug information
16610 to your syslog. You can change the debug level in
16611 /proc/sys/net/irda/debug
16613 If unsure, say Y (since it makes it easier to find the bugs).
16615 IrLAP Compression support
16616 CONFIG_IRDA_COMPRESSION
16617 Compression is _not_ part of the IrDA(tm) protocol specification,
16618 but it's working great! Linux is the first to try out compression
16619 support at the IrLAP layer. This means that you will only benefit
16620 from compression if you are running a Linux <-> Linux configuration.
16622 If you say Y here, you also need to say Y or M to a compression
16625 IrLAP Deflate Compression Protocol (EXPERIMENTAL)
16626 CONFIG_IRDA_DEFLATE
16627 Say Y here if you want to build support for the Deflate compression
16628 protocol. The deflate compression (GZIP) is exactly
16629 the same as the one used by the PPP protocol.
16631 If you want to compile this compression support as a module, say M
16632 here and read Documentation/modules.txt. The module will be called
16637 Say Y here if you want to build support for the IrLAN protocol. If
16638 you want to compile it as a module (irlan.o), say M here and read
16639 Documentation/modules.txt. IrLAN emulates an Ethernet and makes it
16640 possible to put up a wireless LAN using infrared beams.
16642 The IrLAN protocol can be used to talk with infrared access points
16643 like the HP NetbeamIR, or the ESI JetEye NET. You can also connect
16644 to another Linux machine running the IrLAN protocol for ad-hoc
16649 Say Y here if you want to build support for the IrCOMM protocol. If
16650 you want to compile it as a module (you will get ircomm.o and
16651 ircomm-tty.o), say M here and read Documentation/modules.txt. IrCOMM
16652 implements serial port emulation, and makes it possible to use all
16653 existing applications that understands TTY's with an infrared link.
16654 Thus you should be able to use application like PPP, minicom and
16655 others. Enabling this option will create two modules called ircomm
16658 IrTTY IrDA Device Driver
16660 Say Y here if you want to build support for the IrTTY line
16661 discipline. If you want to compile it as a module (irtty.o), say M
16662 here and read Documentation/modules.txt. IrTTY makes it possible to
16663 use Linux's own serial driver for all IrDA ports that are 16550
16664 compatible. Most IrDA chips are 16550 compatible so you should
16665 probably say Y to this option. Using IrTTY will however limit the
16666 speed of the connection to 115200 bps (IrDA SIR mode)
16670 IrPORT IrDA Device Driver
16672 Say Y here if you want to build support for the IrPORT IrDA device
16673 driver. If you want to compile it as a module (irport.o), say M here
16674 and read Documentation/modules.txt. IrPORT can be used instead of
16675 IrTTY and sometimes this can be better. One example is if your IrDA
16676 port does not have echo-canceling, which will work OK with IrPORT
16677 since this driver is working in half-duplex mode only. You don't
16678 need to use irattach with IrPORT, but you just insert it the same
16679 way as FIR drivers (insmod irport io=0x3e8 irq=11). Notice that
16680 IrPORT is a SIR device driver which means that speed is limited to
16685 Winbond W83977AF IrDA Device Driver
16687 Say Y here if you want to build IrDA support for the Winbond
16688 W83977AF super-io chipset. This driver should be used for the IrDA
16689 chipset in the Corel NetWinder. The driver supports SIR, MIR and FIR
16692 If you want to compile it as a module, say M here and read
16693 Documentation/modules.txt. The module will be called w83977af_ir.o.
16695 NSC PC87108 IrDA Device Driver
16697 Say Y here if you want to build support for the NSC PC87108 and
16698 PC87338 IrDA chipsets. This driver supports SIR,
16699 MIR and FIR (4Mbps) speeds.
16701 If you want to compile it as a module, say M here and read
16702 Documentation/modules.txt. The module will be called nsc-ircc.o.
16704 Toshiba Type-O IR Port Device Driver
16706 Say Y here if you want to build support for the Toshiba Type-O IR
16707 chipset. This chipset is used by the Toshiba Libretto 100CT, and
16708 many more laptops. If you want to compile it as a module, say M here
16709 and read Documentation/modules.txt. The module will be called
16712 SMC IrCC (Experimental)
16713 CONFIG_SMC_IRCC_FIR
16714 Say Y here if you want to build support for the SMC Infrared
16715 Communications Controller. It is used in the Fujitsu Lifebook 635t
16716 and Sony PCG-505TX. If you want to compile it as a module, say M
16717 here and read Documentation/modules.txt. The module will be called
16720 Serial dongle support
16722 Say Y here if you have an infrared device that connects to your
16723 computer's serial port. These devices are called dongles. Then say Y
16724 or M to the driver for your particular dongle below.
16726 Note that the answer to this question won't directly affect the
16727 kernel: saying N will just cause this configure script to skip all
16728 the questions about serial dongles.
16730 ESI JetEye PC Dongle
16732 Say Y here if you want to build support for the Extended Systems
16733 JetEye PC dongle. If you want to compile it as a module, say M here
16734 and read Documentation/modules.txt. The ESI dongle attaches to the
16735 normal 9-pin serial port connector, and can currently only be used
16736 by IrTTY. To activate support for ESI dongles you will have to
16737 start irattach like this: "irattach -d esi".
16739 ACTiSYS IR-220L and IR220L+ dongle
16740 CONFIG_ACTISYS_DONGLE
16741 Say Y here if you want to build support for the ACTiSYS
16742 IR-220L and IR220L+ dongles. If you want to compile it as a module,
16743 say M here and read Documentation/modules.txt. The ACTiSYS dongles
16744 attaches to the normal 9-pin serial port connector, and can
16745 currently only be used by IrTTY. To activate support for ACTiSYS
16746 dongles you will have to start irattach like this:
16747 "irattach -d actisys" or "irattach -d actisys+".
16749 Tekram IrMate 210B dongle
16750 CONFIG_TEKRAM_DONGLE
16751 Say Y here if you want to build support for the Tekram IrMate 210B
16752 dongle. If you want to compile it as a module, say M here
16753 and read Documentation/modules.txt. The Tekram dongle attaches to
16754 the normal 9-pin serial port connector, and can currently only be
16755 used by IrTTY. To activate support for Tekram dongles you will have
16756 to start irattach like this: "irattach -d tekram".
16758 Greenwich GIrBIL dongle
16759 CONFIG_GIRBIL_DONGLE
16760 Say Y here if you want to build support for the Greenwich GIrBIL
16761 dongle. If you want to compile it as a module, say M here and read
16762 Documentation/modules.txt. The Greenwich dongle attaches to the
16763 normal 9-pin serial port connector, and can currently only be used
16764 by IrTTY. To activate support for Greenwich dongles you will have to
16765 insert "irattach -d girbil" in the /etc/irda/drivers script.
16767 Parallax Litelink dongle
16768 CONFIG_LITELINK_DONGLE
16769 Say Y here if you want to build support for the Parallax Litelink
16770 dongle. If you want to compile it as a module, say M here and read
16771 Documentation/modules.txt. The Parallax dongle attaches to the
16772 normal 9-pin serial port connector, and can currently only be used
16773 by IrTTY. To activate support for Parallax dongles you will have to
16774 start irattach like this "irattach -d litelink".
16777 CONFIG_OLD_BELKIN_DONGLE
16778 Say Y here if you want to build support for the Adaptec Airport 1000
16779 and 2000 dongles. If you want to compile it as a module, say M here
16780 and read Documentation/modules.txt. The module will be called
16781 old_belkin.o. Some information is contained in the comments at the
16782 top of drivers/net/irda/old_belkin.c.
16784 VME (Motorola and BVM) support
16786 Say Y here if you want to build a kernel for a 680x0 based VME
16787 board. Boards currently supported include Motorola boards MVME162,
16788 MVME166, MVME167, MVME172, and MVME177. BVME4000 and BVME6000
16789 boards from BVM Ltd are also supported.
16791 MVME162, 166 and 167 support
16793 Say Y to include support for Motorola VME boards. This will build a
16794 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
16795 MVME177 boards. If you select this option you will have to select
16796 the appropriate drivers for SCSI, Ethernet and serial ports later
16799 BVME4000 and BVME6000 support
16801 Say Y to include support for VME boards from BVM Ltd. This will
16802 build a kernel which can run on BVME4000 and BVME6000 boards. If
16803 you select this option you will have to select the appropriate
16804 drivers for SCSI, Ethernet and serial ports later on.
16806 Use write-through caching for 68060 supervisor accesses
16807 CONFIG_060_WRITETHROUGH
16808 The 68060 generally uses copyback caching of recently accessed data.
16809 Copyback caching means that memory writes will be held in an on-chip
16810 cache and only written back to memory some time later. Saying Y
16811 here will force supervisor (kernel) accesses to use writethrough
16812 caching. Writethrough caching means that data is written to memory
16813 straight away, so that cache and memory data always agree.
16814 Writethrough caching is less efficient, but is needed for some
16815 drivers on 68060 based systems where the 68060 bus snooping signal
16816 is hardwired on. The 53c710 SCSI driver is known to suffer from
16819 NCR53C710 SCSI driver for MVME16x
16820 CONFIG_MVME16x_SCSI
16821 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
16822 SCSI controller chip. Almost everyone using one of these boards
16823 will want to say Y to this question.
16825 NCR53C710 SCSI driver for BVME6000
16826 CONFIG_BVME6000_SCSI
16827 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
16828 SCSI controller chip. Almost everyone using one of these boards
16829 will want to say Y to this question.
16831 MVME16x Ethernet support
16833 This is the driver for the Ethernet interface on the Motorola
16834 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
16835 driver for this chip in your kernel. If you want to compile it as
16836 a module, say M here and read Documentation/modules.txt.
16838 BVME6000 Ethernet support
16839 CONFIG_BVME6000_NET
16840 This is the driver for the Ethernet interface on BVME4000 and
16841 BVME6000 VME boards. Say Y here to include the driver for this chip
16842 in your kernel. If you want to compile it as a module, say M here
16843 and read Documentation/modules.txt.
16845 CD2401 support for MVME166/7 serial ports
16847 This is the driver for the serial ports on the Motorola MVME166,
16848 167, and 172 boards. Everyone using one of these boards should say
16851 SCC support for MVME162 serial ports
16853 This is the driver for the serial ports on the Motorola MVME162 and
16854 172 boards. Everyone using one of these boards should say Y here.
16856 SCC support for BVME6000 serial ports
16857 CONFIG_BVME6000_SCC
16858 This is the driver for the serial ports on the BVME4000 and BVME6000
16859 boards from BVM Ltd. Everyone using one of these boards should say
16862 7-Segment Display support
16864 This is the driver for the 7-segment display and LED present on
16865 Sun Microsystems CompactPCI models CP1400 and CP1500.
16867 This driver is also available as a module ( = code which can be
16868 inserted in and removed from the running kernel whenever you want).
16869 The module will be called display7seg.o. If you want to compile it
16870 as a module, say M here and read Documentation/modules.txt.
16872 If you do not have a CompactPCI model CP1400 or CP1500, or
16873 another UltraSPARC-IIi-cEngine boardset with a 7-segment display,
16874 you should say N to this option.
16877 CONFIG_IA64_GENERIC
16878 This selects the system type of your hardware. A "generic" kernel
16879 will run on any supported IA-64 system. However, if you configure
16880 a kernel for your specific system, it will be faster and smaller.
16882 To find out what type of IA-64 system you have, you may want to
16883 check the IA-64 Linux web site at http://www.linux-ia64.org/.
16884 As of the time of this writing, most hardware is DIG compliant,
16885 so the "DIG-compliant" option is usually the right choice.
16887 HP-simulator For the HP simulator (http://software.hp.com/ia64linux/).
16888 SN1-simulator For the SGI SN1 simulator.
16889 DIG-compliant For DIG ("Developer's Interface Guide") compliant system.
16891 If you don't know what to do, choose "generic".
16894 CONFIG_IA64_PAGE_SIZE_4KB
16896 This lets you select the page size of the kernel. For best IA-64
16897 performance, a page size of 8KB or 16KB is recommended. For best
16898 IA-32 compatibility, a page size of 4KB should be selected (the vast
16899 majority of IA-32 binaries work perfectly fine with a larger page
16900 size). For Itanium systems, do NOT chose a page size larger than
16903 4KB For best IA-32 compatibility
16904 8KB For best IA-64 performance
16905 16KB For best IA-64 performance
16906 64KB Not for Itanium.
16908 If you don't know what to do, choose 8KB.
16910 Enable Itanium A-step specific code
16911 CONFIG_ITANIUM_ASTEP_SPECIFIC
16912 Select this option to build a kernel for an Itanium prototype system
16913 with an A-step CPU. You have an A-step CPU if the "revision" field in
16914 /proc/cpuinfo is 0.
16916 Enable Itanium A1-step specific code
16917 CONFIG_ITANIUM_A1_SPECIFIC
16918 Select this option to build a kernel for an Itanium prototype system
16919 with an A1-step CPU. If you don't know whether you have an A1-step CPU,
16920 you probably don't and you can answer "no" here.
16922 Enable Itanium B-step specific code
16923 CONFIG_ITANIUM_BSTEP_SPECIFIC
16924 Select this option to build a kernel for an Itanium prototype system
16925 with a B-step CPU. You have a B-step CPU if the "revision" field in
16926 /proc/cpuinfo has a value in the range from 1 to 4.
16928 Enable Itanium B0-step specific code
16929 CONFIG_ITANIUM_B0_SPECIFIC
16930 Select this option to bild a kernel for an Itanium prototype system
16931 with a B0-step CPU. You have a B0-step CPU if the "revision" field in
16932 /proc/cpuinfo is 1.
16934 Force interrupt redirection
16935 CONFIG_IA64_HAVE_IRQREDIR
16936 Select this option if you know that your system has the ability to
16937 redirect interrupts to different CPUs. Select N here if you're
16940 Enable use of global TLB purge instruction (ptc.g)
16941 CONFIG_ITANIUM_PTCG
16942 Say Y here if you want the kernel to use the IA-64 "ptc.g"
16943 instruction to flush the TLB on all CPUs. Select N here if
16946 Enable SoftSDV hacks
16947 CONFIG_IA64_SOFTSDV_HACKS
16948 Say Y here to enable hacks to make the kernel work on the Intel
16949 SoftSDV simulator. Select N here if you're unsure.
16952 CONFIG_IA64_AZUSA_HACKS
16953 Say Y here to enable hacks to make the kernel work on the NEC
16954 AzusA platform. Select N here if you're unsure.
16956 Force socket buffers below 4GB?
16957 CONFIG_SKB_BELOW_4GB
16958 Most of today's network interface cards (NICs) support DMA to
16959 the low 32 bits of the address space only. On machines with
16960 more then 4GB of memory, this can cause the system to slow
16961 down if there is no I/O TLB hardware. Turning this option on
16962 avoids the slow-down by forcing socket buffers to be allocated
16963 from memory below 4GB. The downside is that your system could
16964 run out of memory below 4GB before all memory has been used up.
16965 If you're unsure how to answer this question, answer Y.
16967 Enable IA-64 Machine Check Abort
16969 Say Y here to enable machine check support for IA-64. If you're
16972 Performance monitor support
16974 Selects whether support for the IA-64 performance monitor hardware
16975 is included in the kernel. This makes some kernel data-structures a
16976 little bigger and slows down execution a bit, but it is still
16977 usually a good idea to turn this on. If you're unsure, say N.
16980 CONFIG_IA64_PALINFO
16981 If you say Y here, you are able to get PAL (Processor Abstraction
16982 Layer) information in /proc/pal. This contains useful information
16983 about the processors in your systems, such as cache and TLB sizes
16984 and the PAL firmware version in use.
16986 To use this option, you have to check that the "/proc file system
16987 support" (CONFIG_PROC_FS) is enabled, too.
16990 # A couple of things I keep forgetting:
16991 # capitalize: AppleTalk, Ethernet, DOS, DMA, FAT, FTP, Internet,
16992 # Intel, IRQ, ISDN, Linux, MSDOS, NetWare, NetWinder,
16993 # NFS, PCI, SCSI, SPARC
16994 # two words: file system, hard drive, hard disk, home page,
16995 # user space, web site
16996 # other: it's safe to save; daemon; use --, not - or ---;
16997 # use KB for 1024 bytes, not kB or K.
17000 # This is used by Emacs' spell checker ispell.el:
17002 # LocalWords: CONFIG coprocessor DX Pentium SX lilo loadlin HOWTO ftp metalab
17003 # LocalWords: unc edu docs emu README kB BLK DEV FD Thinkpad fd MFM RLL IDE gz
17004 # LocalWords: cdrom diskless netboot nfs xzvf ATAPI MB ide pavia rubini pl pd
17005 # LocalWords: HD CDROMs IDECD NEC MITSUMI filesystem XT XD PCI BIOS cezar ATEN
17006 # LocalWords: ISA EISA Microchannel VESA BIOSes IPC SYSVIPC ipc Ctrl dmesg hlt
17007 # LocalWords: BINFMT Linkable http ac uk jo html GCC SPARC AVANTI CABRIOLET EB
17008 # LocalWords: netscape gcc LD CC toplevel MODVERSIONS insmod rmmod modprobe IP
17009 # LocalWords: genksyms INET loopback gatewaying ethernet PPP ARP Arp MEMSIZE
17010 # LocalWords: howto multicasting MULTICAST MBONE firewalling ipfw ACCT resp ip
17011 # LocalWords: proc acct IPIP encapsulator decapsulator klogd PCTCP RARP EXT PS
17012 # LocalWords: telnetting subnetted NAGLE rlogin NOSR ttyS TGA techinfo mbone nl
17013 # LocalWords: Mb SKB IPX Novell dosemu Appletalk DDP ATALK vmalloc visar ehome
17014 # LocalWords: SD CHR scsi thingy SG CD LUNs LUN jukebox Adaptec BusLogic EATA
17015 # LocalWords: buslogic DMA DPT ATT eata dma PIO UltraStor fdomain umsdos ext
17016 # LocalWords: QLOGIC qlogic TMC seagate Trantor ultrastor FASST wd NETDEVICES
17017 # LocalWords: unix BBS linux CSLIP PLIP Kirch's LDP CSlip SL SCC IRQ csustan
17018 # LocalWords: Turbo Laplink plip NCSA port's ReQuest IRQs EQL SMC AMD PCnet NE
17019 # LocalWords: COM ELPLUS Com EtherLinkIII VLB Arcnet Cabletron DEPCA DE carlos
17020 # LocalWords: depca EtherWorks EWRK ewrk SEEQ EtherExpress EEXPRESS NI xxx dia
17021 # LocalWords: EtherExpress WaveLAN wavelan PCLAN HPLAN VG SK Ansel Xen de ZNET
17022 # LocalWords: PCMCIA cb stanford LAN TEC RealTek ATP atp DLINK NetTools VISWS
17023 # LocalWords: TR Sony CDU caddyless cdu Mitsumi MCD cd mcd XA MultiSession CDA
17024 # LocalWords: Matsushita Panasonic SBPCD Soundblaster Longshine sbpcd Aztech
17025 # LocalWords: Okano Wearnes AZTCD CDD SE aztcd sonycd Goldstar GSCD Philips fs
17026 # LocalWords: LMS OPTCD Sanyo SJCD minix faqs xiafs XIA msdos mtools Cichocki
17027 # LocalWords: std softlinks umssync NetworkFileSharing nfsd mountd CDs HPFS TI
17028 # LocalWords: hpfs SYSV SCO iBCS Wyse WordPerfect tsx mit unixes sysv NR irisa
17029 # LocalWords: SMB WfW Cyclades async mux Logitech busmouse MouseSystem aka AST
17030 # LocalWords: PSMOUSE Compaq trackballs Travelmate Inport ATIXL ATI busmice ld
17031 # LocalWords: gpm config QIC DYNCONF FTAPE Stor Ftape ftape pcsndrv manpage NT
17032 # LocalWords: readprofile diskdrives org com masq EtherTalk tcp netrom sunacm
17033 # LocalWords: misc AIC aic pio scc Portmaster eql GIS PhotoCDs MCDX Perell PG
17034 # LocalWords: mcdx gscd optcd sjcd ISP hdparm Workgroups Lan samba PARIDE PCD
17035 # LocalWords: filesystems smbfs ATA ppp PCTech RZ www powerquest txt CMD ESDI
17036 # LocalWords: chipset FB multicast MROUTE appletalk ifconfig IBMTR multiport
17037 # LocalWords: Multisession STALDRV EasyIO EC EasyConnection ISTALLION ONboard
17038 # LocalWords: Brumby pci TNC cis ohio faq usenet NETLINK dev hydra ca Tyne mem
17039 # LocalWords: carleton DECstation SUNFD JENSEN Noname XXXM SLiRP LILO's amifb
17040 # LocalWords: pppd Zilog ZS SRM bootloader ez mainmenu rarp ipfwadm paride pcd
17041 # LocalWords: RTNETLINK mknod xos MTU lwared Macs mac netatalk macs cs Wolff
17042 # LocalWords: dartmouth flowerpt MultiMaster FlashPoint tudelft etherexpress
17043 # LocalWords: ICL EtherTeam ETH IDESCSI TXC SmartRAID SmartCache httpd sjc dlp
17044 # LocalWords: thesphere TwoServers BOOTP DHCP ncpfs BPQETHER BPQ MG HIPPI cern
17045 # LocalWords: bsd comp SPARCstation le SunOS ie Gracilis PackeTwin PT pt LU FX
17046 # LocalWords: FX TEAC CR LCS mS ramdisk IDETAPE cmd fperllo encis tcfs unisa
17047 # LocalWords: Vertos Genoa Funai hsfs NCP NetWare tgz APM apm ioctls UltraLite
17048 # LocalWords: TravelMate CDT LCD backlight VC RPC Mips AXP barlow cdrecord pg
17049 # LocalWords: PMAX MILO Alphas Multia Tseng linuxelf endian mipsel mips drv HT
17050 # LocalWords: kerneld callouts AdvanSys advansys Admin WDT DataStor EP verden
17051 # LocalWords: wdt hdb hdc bugfix SiS vlb Acculogic CSA DTC dtc Holtek ht QDI
17052 # LocalWords: QD qd UMC umc ALI ali lena fnet fr azstarnet cdr fb MDA ps esdi
17053 # LocalWords: Avanti XL AlphaStations Jensen DECpc AXPpci UDB Cabriolet MCA RC
17054 # LocalWords: AlphaPC mca AOUT OUTput PPro sipx gwdg lo nwe FourPort Boca unm
17055 # LocalWords: Keepalive linefill RELCOM keepalive analogue CDR conf CDI INIT
17056 # LocalWords: OPTi isp irq noisp VFAT vfat NTFS losetup dmsdosfs dosfs ISDN MP
17057 # LocalWords: NOWAYOUT behaviour dialin isdn callback BTX Teles XXXX LVM lvm
17059 # LocalWords: ipppd syncppp RFC MPP VJ downloaded icn NICCY Creatix shmem ufr
17060 # LocalWords: ibp md ARCnet ether encap NDIS arcether ODI Amigas AmiTCP NetBSD
17061 # LocalWords: initrd tue util DES funet des OnNet BIOSP smc Travan Iomega CMS
17062 # LocalWords: FC DC dc PPA IOMEGA's ppa RNFS FMV Fujitsu ARPD arpd loran layes
17063 # LocalWords: FRAD indiana framerelay DLCI DCLIs Sangoma SDLA mrouted sync sec
17064 # LocalWords: Starmode Metricom MosquitoNet mosquitonet kbit nfsroot Digiboard
17065 # LocalWords: DIGI Xe Xeve digiboard UMISC touchscreens mtu ethernets HBAs MEX
17066 # LocalWords: Shifflett netcom js jshiffle WIC DECchip ELCP EtherPower dst RTC
17067 # LocalWords: rtc SMP lp Digi Intl RightSwitch DGRS dgrs AFFS Amiga UFS SDL AP
17068 # LocalWords: Solaris RISCom riscom syncPPP PCBIT pcbit sparc anu au artoo MFB
17069 # LocalWords: hitchcock Crynwr cnam pktdrvr NCSA's CyDROM CyCDROM FreeBSD NeXT
17070 # LocalWords: NeXTstep disklabel disklabels SMD FFS tm AmigaOS diskfiles Un IQ
17071 # LocalWords: Bernd informatik rwth aachen uae affs multihosting bytecode java
17072 # LocalWords: applets applet JDK ncsa cabi SNI Alphatronix readme LANs scarab
17073 # LocalWords: winsock RNIS caltech OSPF honour Honouring Mbit LocalTalk DEFRAG
17074 # LocalWords: localtalk download Packetwin Baycom baycom interwork ASCII JNT
17075 # LocalWords: Camtec proxying indyramp defragment defragmented UDP FAS FASXX
17076 # LocalWords: FastSCSI SIO FDC qlogicfas QLogic qlogicisp setbaycom ife ee LJ
17077 # LocalWords: ethz ch Travelmates ProAudioSpectrum ProAudio SoundMan SB SBPro
17078 # LocalWords: Thunderboard SM OPL FM ADLIB TSR Gravis MPU PSS ADI SW DSP codec
17079 # LocalWords: ADSP ESC ASIC daughtercard GUSMAX MSS NX AdLib Excell Ensoniq YM
17080 # LocalWords: SoundScape Spea MediaTriX AudioTriX WSS OTI ThunderBoard VoxWare
17081 # LocalWords: Soundscape SSCAPE TRIX MediaTrix PnP Maui dsp midixx EIA getty
17082 # LocalWords: mgetty sendfax gert greenie muc lowlevel Lasermate LanManager io
17083 # LocalWords: OOPSes trackball binghamton mobileip ncr IOMAPPED settags ns ser
17084 # LocalWords: setsync NEGO MPARITY autotuning prefetch PIIX cdwrite utils rc
17085 # LocalWords: PCWATCHDOG berkprod bitgate boldt ucsb jf kyoto jp euc Tetsuyasu
17086 # LocalWords: YAMADA tetsu cauchy nslab ntt nevod perm su doc kaf kheops wsc
17087 # LocalWords: traduc Bourgin dbourgin menuconfig kfill READMEs HOWTOs Virge WA
17088 # LocalWords: IDEDISK IDEFLOPPY EIDE firewalls QMAGIC ZMAGIC LocalWords opti
17089 # LocalWords: SVGATextMode vga svga Xkernel syr jmwobus comfaqs dhcp flakey GD
17090 # LocalWords: IPv IPng interoperability ipng ipv radio's tapr pkthome PLP nano
17091 # LocalWords: Ses Mhz sethdlc SOUNDMODEM WindowsSoundSystem smdiag pcf inka ES
17092 # LocalWords: smmixer ptt circ soundmodem MKISS FDDI DEFEA DEFPA DEFXX redhat
17093 # LocalWords: HyperNews khg mconv sed lina wuftpd MicroChannel netlink irc cum
17094 # LocalWords: raudio RealAudio PPROP NETBIOS GUI IBMMCA ELMC Racal Interlan fi
17095 # LocalWords: eth shapecfg src esp PCWD PREVSTAT bootparam sig bitwizard SBC
17096 # LocalWords: downloads AFSK TCM FP Karn KA FSK RUH LinkSys cron mouseman LLC
17097 # LocalWords: SyQuest SyQuest's CCITT MicroSolutions BPCD bpcd ESPSERIAL PROM
17098 # LocalWords: SUNESP openprom OPENPROMIO quango themall al TT MC MMU LC RMW AA
17099 # LocalWords: INSNS Ataris AutoConfig ZORRO OCS AMIFB Agnus Denise ECS CDTV GB
17100 # LocalWords: AGA Cybervision CYBER GSP TMS DMI Zorro ACSI ROMs SLM BioNet GVP
17101 # LocalWords: PAMsNet TekMagic Cyberstorm MkI CYBERSTORMII MkII BLZ onboard cx
17102 # LocalWords: Village Tronic ATARILANCE RieblCard PAMCard VME MFP sangoma LAPB
17103 # LocalWords: Rhotron BioData's Multiface AMIGAMOUSE COPCON Amiga's bitplanes
17104 # LocalWords: ATARIMOUSE MFPSER SCC's MegaSTE ESCC Atari's GVPIOEXT DMASOUND
17105 # LocalWords: fdutils cisco univercd rpcg htm iface lapb LAPBETHER tpqic qic
17106 # LocalWords: SYNTH xd en binfmt aout ipip terra ipx sd sr sg wic framebuffer
17107 # LocalWords: ibmmca lapbether mkiss dlci sdla fmv eepro eexpress ni hp ne es
17108 # LocalWords: ibmtr isofs ROMFS romfs pcxx cyclades istallion psaux msbusmouse
17109 # LocalWords: atixlmouse sbin softdog pcwd USS Lite ACI miroSOUND PCM miroPCM
17110 # LocalWords: microcontroller miro Voxware downloading teles acsi slm gvp ltpc
17111 # LocalWords: atari ariadne amigamouse atarimouse builtin IPDDP maths bradford
17112 # LocalWords: AppleTalk Farallon PhoneNet Zubkoff lnz SCCB HAPN WANs vesafb nt
17113 # LocalWords: wanrouter WANPIPE multiprotocol Mbps wanpipe EtherWORKS nodma SC
17114 # LocalWords: smp HiSax SiemensChipSet Siemens AVM Elsa ITK hisax PCC MICROR
17115 # LocalWords: Mircolink EURO DSS Spellcaster BRI sc spellcast Digiboards GPIO
17116 # LocalWords: SYMBIOS COMPAT SDMS rev ASUS Tekram HX VX API ibmmcascsi ASY asy
17117 # LocalWords: loader's PCnetPCI automounter AUTOFS amd autofs VT Gallant's Pnp
17118 # LocalWords: AEDSP aedsp enskip tik Sysctl sysctl PARPORT parport pnp IDs EPP
17119 # LocalWords: Autoprobe bart patrickr HDLS READBACK AB usr DAMA DS SparQ aten
17120 # LocalWords: Symbios PCscsi tmscsim RoamAbout GHz Hinds contrib mathematik ok
17121 # LocalWords: darmstadt okir DIGIEPCA International's Xem digiepca epca bootup
17122 # LocalWords: zorro CAPI AVMB capi avmb VP SYN syncookies EM em pc Ethertalk
17123 # LocalWords: Dayna DL Daynatalk LT PhoneNET ATB Daystar queueing CMDS SCBs ls
17124 # LocalWords: SCB STATS Thinnet ThunderLAN TLAN Netelligent NetFlex tlan james
17125 # LocalWords: caldera Preload Preloading slowdowns schoebel uni NBD nbd prog
17126 # LocalWords: stuttgart rdist TRANS hostnames mango jukeboxes ESS userland PD
17127 # LocalWords: hardlinked NAMETRANS env mtab fstab umount nologin runlevel gid
17128 # LocalWords: adm Nodename hostname uname Kernelname bootp nmi DI OV StegFS
17129 # LocalWords: KERNNAME kname ktype kernelname Kerneltype KERNTYPE Alt RX mdafb
17130 # LocalWords: dataless kerneltype SYSNAME Comtrol Rocketport palmtop fbset EGS
17131 # LocalWords: nvram SYSRQ SysRq PrintScreen sysrq NVRAMs NvRAM Shortwave RTTY
17132 # LocalWords: Sitor Amtor Pactor GTOR hayes TX TMOUT JFdocs BIGMEM DAC IRQ's
17133 # LocalWords: IDEPCI IDEDMA PDC pdc TRM trm raidtools luthien nuclecu BAGET VR
17134 # LocalWords: unam mx miguel koobera uic EMUL solaris pp ieee lpsg co DMAs TOS
17135 # LocalWords: BLDCONFIG preloading jumperless BOOTINIT modutils multipath GRE
17136 # LocalWords: misconfigured autoconfiguration IPGRE ICMP tracert ipautofw PIM
17137 # LocalWords: netis rlynch autofw ipportfw monmouth ipsubs portforwarding pimd
17138 # LocalWords: portfw PIMSM netweb usc pim pf EUI aggregatable PB decapsulate
17139 # LocalWords: ipddp Decapsulation DECAP bool HAMRADIO tcpdump af CDs tx FBCON
17140 # LocalWords: ethertap multisession PPC MMIO GDT GDTH ICP gdth hamradio bpp
17141 # LocalWords: lmh weejock AIMSlab RadioTrack RTRACK HZP OptoSCC TRX rx TRXECHO
17142 # LocalWords: DMASCC paccomm dmascc addr cfg oevsv oe kib picpar FDX baudrate
17143 # LocalWords: baudrates fdx HDX hdx PSK kanren frforum QoS SCHED CBQ SCH sched
17144 # LocalWords: sch cbq CSZ Shenker Zhang csz SFQ sfq TBF tbf PFIFO fifo PRIO RW
17145 # LocalWords: prio Micom xIO dwmw rimi OMIRR omirr omirrd unicode ntfs cmu NIC
17146 # LocalWords: Braam braam Schmidt's freiburg nls codepages codepage Romanian
17147 # LocalWords: Slovak Slovenian Sorbian Nordic iso Catalan Faeroese Galician SZ
17148 # LocalWords: Valencian Slovene Esperanto Estonian Latvian Byelorussian KOI mt
17149 # LocalWords: charset Inuit Greenlandic Sami Lappish koi Alexey Kuznetsov's sa
17150 # LocalWords: Specialix specialix DTR RTS RTSCTS cycladesZ Exabyte ftape's inr
17151 # LocalWords: Iomega's LBFM claus ZFTAPE VFS zftape zft William's lzrw DFLT kb
17152 # LocalWords: MTSETBLK MTIOCTOP qft setblk zftape's tar's afio's setdrvbuffer
17153 # LocalWords: Procfs Exabyte's THR FCD sysvinit init PSC pscwdt VMIDI Euro SAB
17154 # LocalWords: Mostek Fastlane PowerMac PReP PMAC PowerPC Macintoshes Starmax
17155 # LocalWords: PowerStack Starmaxes MCOMMON DEVICETREE ATY IMS IMSTT videodev
17156 # LocalWords: BT Hauppauge STB bttv Quickcam BW BWQCAM bw qcam Mediavision PMS
17157 # LocalWords: pms Avatar Freecom Imation Superdisk BPCK bpck COMM comm DSTR ru
17158 # LocalWords: dstr EPAT EPEZ epat EPIA epia FreeCom FRPW frpw KingByte KBIC HW
17159 # LocalWords: KingByte's kbic OnSpec ValuStore FASTROUTE fastroute FLOWCONTROL
17160 # LocalWords: struct APIC realtime OSs LynxOS CNC tmp cvf HFS hfs ADFS Risc os
17161 # LocalWords: adfs ncpmount namespace SUBDIR reexport NDS kcore FT SPX spx DAT
17162 # LocalWords: interserver BLKSZ NUMBUFFERS apmd Tadpole ANA roestock QuickCam
17163 # LocalWords: isapnptools Colour CQCAM colour Connectix QuickClip prive mentre
17164 # LocalWords: KMOD kmod conformant utexas kharker UnixWare Mwave cgi cl ts ibm
17165 # LocalWords: eXchange threepio oakland simtel pre ULTRAMCA EtherLink isa luik
17166 # LocalWords: EtherLink OpenBSD pts DEVPTS devpts ptmx ttyp glibc readback SA
17167 # LocalWords: mwave OLDCARD isdnloop linklevel loopctrl Eicon Diehl DIEHLDIVA
17168 # LocalWords: ASUSCOM AsusCom TELEINT semiactiv Sedlbauer Sportster TA MIC ITH
17169 # LocalWords: NETjet NetJet Niccy Neuhaus sparcs AOC AOCD AOCE Microlink SAA
17170 # LocalWords: teletext WinTV saa iproute tc Quadra Performa PowerBook tor AUN
17171 # LocalWords: setserial compsoc steve Econet econet AUNUDP psched TEQL TLE CLS
17172 # LocalWords: teql FW Ingres TwistedPair MTRR MTRRs mtrr cfs crypto TD ktti KT
17173 # LocalWords: PHd ICS ipchains adelaide rustcorp syslog Cumana steganography
17174 # LocalWords: AcornSCSI EcoSCSI EESOX EESOXSCSI Powertec POWERTECSCSI dec SF
17175 # LocalWords: RadioReveal gatekeeper aimslab aztech FMI sf fmi RTL rtl cesdis
17176 # LocalWords: Yellowfin gsfc nasa gov yellowfin pcnet Mylex LNE lne EtherH hs
17177 # LocalWords: EBSA chattr RiscOS Winmodem AGP Atomwide DUALSP pcsp robinson CT
17178 # LocalWords: SGALAXY Waverider DSPxxx TRXPRO AudioTrix OSWF MOT CFB DSY kbps
17179 # LocalWords: tuwien kkudielk LVD mega lun MAXTAGS Gbps arcnet Olicom SNA PAE
17180 # LocalWords: SysKonnect tms sna etherboot ufs NetBEUI MultiSound MSNDCLAS GX
17181 # LocalWords: MSNDINIT MSNDPERM MSNDPIN PNDSPINI PNDSPERM Ensoniq's RetinaZ SS
17182 # LocalWords: AudioPCI lspci SonicVibes sonicvibes SPARCs roadrunner CLgen UPA
17183 # LocalWords: swansea shtml Zoltrix zoltrix BINUTILS EGCS binutils VIDC DACs
17184 # LocalWords: CyberVision Cirrus PowerBooks Topcat SBUS CGsix TurboGX BWtwo SS
17185 # LocalWords: CGthree TCX unswapable vfb fbcon hicolor truecolor AFB ILBM SOC
17186 # LocalWords: IPLAN gracilis Fibre SBus SparcSTORAGE SV jnewbigin swin QNX qnx
17187 # LocalWords: PTY PTYS ptyxx ttyxx PTYs ssh sb Avance ALS pss pvv kerneli hd
17188 # LocalWords: synth WaveFront MSND NONPNP AudioExcelDSP STRAM APUS CHRP MBX Nx
17189 # LocalWords: PowerMac's BMAC radiotrack rtrack miropcm OFFBOARD HPT UDMA DVD
17190 # LocalWords: hpt fokus gmd Cyrix DXL SLC DLC NexGen MediaGX GXm IDT WinChip
17191 # LocalWords: MMX MII valkyrie mdacon vdolive VDOLive cuseeme CU hippi rrunner
17192 # LocalWords: SeeMe ipmasqadm juanjox ipmarkfw markfw TNCs Microdyne rhine lib
17193 # LocalWords: libc jsX gamepad gameport CHF FCS FPGaming MadCatz ASSASIN GrIP
17194 # LocalWords: Assasin gamepads GamePad PDPI gamecards gamecard WingMan BSP WCS
17195 # LocalWords: ThunderPad CyberMan SideWinder ThrustMaster DirectConnect NES XF
17196 # LocalWords: Millenium SNES PSX Multisystem Nintendo PlayStation Amstrad CPC
17197 # LocalWords: Sega TurboGraFX Steffen Schwenke Multiststem PDIF FIFOSIZE EPLUS
17198 # LocalWords: PowerUP RoadRunner tahallah dos functionkey setterm imladris Woz
17199 # LocalWords: PowerMacs Winbond Algorithmics ALGOR algor ECOFF IRIX SGI SGI's
17200 # LocalWords: gfx virtualized Xpmac mklinux XFree FBDev Woodhouse mvhi Seeq fp
17201 # LocalWords: SGISEEQ HIgh ADB ADBMOUSE crosscompiler CROSSCOMPILE FPE GDB gdb
17202 # LocalWords: JOYPORT rp spoofing DawiControl NOGENSUPP EEPROM HSSI Alessandro
17203 # LocalWords: singleprocessor tex MATHEMU FRIQ Maxell friq Alcor XLT AlphaBook
17204 # LocalWords: AlphaPCI DP LX Miata Mikasa Noritake RPX UX BX Takara EV PRIMO
17205 # LocalWords: TSC Matrox Productiva matroxfb matrox multihead ia linuxhq MFW
17206 # LocalWords: mfw AAA MCS Initio XXU initio imm AutoDetect IZIP CTR usec HDLC
17207 # LocalWords: COSA SRP muni cz kas cosa Alteon AceNIC acenic VTOC OSes GMT SAx
17208 # LocalWords: Inspiron localtime INTS Thinkpads Ralf Brown's Flightstick NNN
17209 # LocalWords: Xterminator Blackhawk NN mpu ioports DCA HPDCA HPLANCE DIO Corel
17210 # LocalWords: GemTek gemtek CMDLINE IrDA PDA's irmanager irattach RR AVA DN rg
17211 # LocalWords: uit dagb irda LSAP IrLMP RR's IrLAP IR alloc skb's kfree skb's
17212 # LocalWords: GZIP IrLAN NetbeamIR ESI JetEye IrOBEX IrCOMM TTY's minicom dti
17213 # LocalWords: ircomm ircomm pluto thiguchi IrTTY Linux's bps NetWinder MIR NSC
17214 # LocalWords: ACTiSYS Dongle dongle dongles esi actisys IrMate tekram BVM MVME
17215 # LocalWords: BVME BVME WRITETHROUGH copyback writethrough fwmark syncookie tu
17216 # LocalWords: alphalinux GOBIOS csn chemnitz nat ACARD AMI MegaRAID megaraid
17217 # LocalWords: QNXFS ISI isicom xterms Apollos VPN RCPCI rcpci sgi visws pcmcia
17218 # LocalWords: IrLPT UIRCC Tecra Strebel jstrebel suse Eichwalder ke INI INIA
17219 # LocalWords: FCP qlogicfc sym isapnp DTLK DoubleTalk rcsys dtlk DMAP SGIVW ar
17220 # LocalWords: dmabuf EcoRadio MUTEFREQ GIrBIL girbil tepkom vol mha diplom PQS
17221 # LocalWords: bmac Microgate SyncLink synclink hdlc excl ioaddr Tane tanep TCQ
17222 # LocalWords: PDS SMALLDOS charsets bigfoot kernelfr mcs cls fw rsvp SKnet sk
17223 # LocalWords: SKMC USB UHCI OHCI intel compaq usb ohci HCD Virt Compaq's hcd
17224 # LocalWords: VROOTHUB KBD ARRs MCRs NWBUTTON nwbutton NUM WaveArtist APNE cpu
17225 # LocalWords: apne blackhawke PlanB lu mlan planb NWFPE FPA nwfpe unbootable
17226 # LocalWords: FPEmulator ds vmlinux initialisation discardable pgtable PGT mdw
17227 # LocalWords: quicklist pagetable arthur StrongARM podule podules Autodetect
17228 # LocalWords: dodgy IrPORT irport Litelink litelink SuSE rtfm internet hda CY
17229 # LocalWords: multmode DriveReady SeekComplete DriveStatusError miscompile AEC
17230 # LocalWords: mainboard's Digital's alim FastTrak aec PIIXn piix Gayle Eyetech
17231 # LocalWords: Catweasel IDEDOUBLER Powerbook Centris ICSIDE RapIDE OSM HDM IOP
17232 # LocalWords: HDM's OSM's lan FibreChannel ECP autoprobe itg lbl ipmasq cjb IC
17233 # LocalWords: bieringer Caulfield's dreamtime decnet SIOCFIGCONF SIOCGIFCONF
17234 # LocalWords: rtnetlink Endnode Aironet Arlan Telxon ylenurme arlan ACB aeschi
17235 # LocalWords: Sealevel sealevel Cyclom br wanconfig tarball conectiva cycsyn
17236 # LocalWords: devel bazar cyclomx NetGear GA IBMOL Lanstreamer uhci eu efs CYZ
17237 # LocalWords: olympic linuxtr usbcore acm EZUSB downloader EFS XFS INTR op IIC
17238 # LocalWords: heine soundcore JavaStations JavaStation GemTeks TerraTec TODO
17239 # LocalWords: ActiveRadio Standalone terratec Rolf Offermanns rolf offermanns
17240 # LocalWords: Zoran ZR Buz LML CPQ DA cpqarray PPDEV deviceid vlp ppdev atyfb
17241 # LocalWords: AcceleRAID eXtremeRAID NETFILTER Netfilter masqueraded netfilter
17242 # LocalWords: kernelnotes Cardbus PCMCIA's CardBus clgenfb Permedia YAM MMAP
17243 # LocalWords: mmapped ATM atm PVCs SVCs InARP ATMARP neighbour neighbours MPOA
17244 # LocalWords: VCs ENI FPGA Tonga MMF MF UTP printks ZeitNet ZN ZATM uPD SAR PN
17245 # LocalWords: approx NICStAR NICs ForeRunnerLE Madge Collage ATMizer Dxxxx VCI
17246 # LocalWords: ServeRAID IPS ips ipslinux gzip BSDCOMP LZW RAYCS Interphase app
17247 # LocalWords: Tachyon IPHASE Surfboard NextLevel SURFboard jacksonville Tigon
17248 # LocalWords: fventuri adelphia siglercm linuxpower AceNICs Starfire starfire
17249 # LocalWords: ISOC CPiA cpia uss ACPI UDF DirectCD udf CDRW's OSF Manx acpi DM
17250 # LocalWords: Unixware cymru Computone IntelliPort Intelliport computone SI sx
17251 # LocalWords: adbmouse DRI DRM dlabs GMX PLCs Applicom fieldbus applicom int
17252 # LocalWords: VWSND eg ESSSOLO CFU CFNR scribed eiconctrl eicon hylafax KFPU
17253 # LocalWords: EXTRAPREC fpu mainboards KHTTPD kHTTPd khttpd Xcelerator SBNI tw
17254 # LocalWords: LOGIBUSMOUSE Granch granch sbni Raylink NOHIGHMEM Athlon SIM sim
17255 # LocalWords: hpl Tourrilhes DuraLAN starfile Davicom davicom dmfe auk tms tr
17256 # LocalWords: TokenExpress Belkin Peracom eTek DVDs infradead Cxxx Adlib AV ZX
17257 # LocalWords: NeoMagic CPi CPt Celeron decapsulation Undeletion BFS bfs nVidia
17258 # LocalWords: OnStream Irongate Riva phonedev QuickNet LineJack PhoneJack IXJ
17259 # LocalWords: Quicknet PhoneJACK LineJACK ixj pnpdump Quicknet's Joandi SSID
17260 # LocalWords: aironet quickconfig adhoc btw bap NONCS cardservices Xircom lin
17261 # LocalWords: Netwave AirSurfer netwave HomePNA failover MVP iMacs ALi aktual
17262 # LocalWords: Aladin HIDBP usbkbd KEYBDEV MOUSEDEV JOYDEV EVDEV UAB WhiteHEAT
17263 # LocalWords: Handspring ov DABUSB URB URB's dabusb CRAMFS NFSv ELV IOAPIC WIP
17264 # LocalWords: NLMv SMBus ALGOBIT algo PHILIPSPAR philips elv Velleman velleman
17265 # LocalWords: ALGOPCF Elektor elektor CHARDEV dfx TDFX tdfx Extensa dof gravis
17266 # LocalWords: assasin logitech Overdrive thrustmaster DWave Aureal magellan db
17267 # LocalWords: SpaceTec SpaceOrb SpaceBall spaceorb FLX spaceball turbografx zr
17268 # LocalWords: amiga ESS's WaveWatcher Maxi belkin RW's ata glx GART MPV Baget
17269 # LocalWords: OpenGL Xserver agpgart HOTPLUG CyberPro Integraphics Netwinder
17270 # LocalWords: aty FONTWIDTH eni zatm nicstar ForeRunner OC DECstations DEC's
17271 # LocalWords: PHYsical SUNI reinsertion ChipSAR KVC PHY ClassID iphase iadbg
17272 # LocalWords: DEVS FireWire PCILynx pcilynx LOCALRAM miro's DV RAWIO GRED Mk
17273 # LocalWords: Diffserv DSMARK Ingress Qdisc TCINDEX TMSPCI tmspci Ringode JE
17274 # LocalWords: MADGEMC madgemc TokenRing SMCTR TokenCard smctr Wacom Graphire
17275 # LocalWords: WMFORCE mousedev ConnectTech HandSpring Xirlink IBMCAM ibmcam SN
17276 # LocalWords: DEVICEFS yyy Cymraeg Dwave SIMM JSFLASH JavaStation's multilink
17277 # LocalWords: nsc ircc DDB Vrc CMN TB PROMs Vino rivafb DDC Matroxes MGA TVO
17278 # LocalWords: MAVEN fbdev crtc maven matroxset NTSC PCA SBA AAL SKFP DAS SAS
17279 # LocalWords: skfp Intuos ADMtek's pegasus PLUSB plusb pointopoint mp rio Xeon
17280 # LocalWords: DEVFS devfs dd bs EDSS german TELESPCI FRITZPCI HFC HFCS BDS HST
17281 # LocalWords: ISURF ISAR Saphir HSTSAPHIR Telekom BKM Scitel Quadro SCT Gazel
17282 # LocalWords: SP PRI Hypercope HYSDN Hypercope's hysdn IbssJoinNetTimeout FTDI
17283 # LocalWords: ARCNet Keyspan PDA ADMtek sgalaxy sgbase opl mpuio mpuirq sbio
17284 # LocalWords: sbirq sbdma gus uart mssio mssirq mssdma sscape maui mouirq iph
17285 # LocalWords: CHDLC UPS's usbmouse wacom wmforce keybdev joydev fibre Trunking
17286 # LocalWords: Etherchannel IOC Moxa Intellio moxa SmartIO mxser Mixcom EFI ir
17287 # LocalWords: MIXCOMWD mixcomwd SENDCOMPLETE GMAC iBook gmac OAKNET oaknet PCG
17288 # LocalWords: diffserv irlan irtty toshoboe IrCC Lifebook idex AUTODMA FIP Cxx
17289 # LocalWords: Yenta Databook TCIC FMVJ fmvj NMCLAN LiveWire nmclan XIRC xirc
17290 # LocalWords: loadkeys setfont shm SuperIO soc SOCAL socal FCAL fc fcal COMX
17291 # LocalWords: MultiGate ITConsult comx CMX HiCOMX downloadable hw LoCOMX PROTO
17292 # LocalWords: locomx MixCOM mixcom proto MyriCOM MYRI Sbus myri sbus IBMLS hme
17293 # LocalWords: lanstreamer baseT HAPPYMEAL qfe sunhme SUNLANCE sunlance BigMAC
17294 # LocalWords: SUNBMAC sunbmac QuadEthernet SUNQE qe FastEthernet sunqe DSB PTI
17295 # LocalWords: DSBR dsbr procinfo QLOGICPTI qpti ptisp QLGC qlogicpti se LBA NF
17296 # LocalWords: OPENPROMFS OpenPROM openpromfs OBP OpenBoot flashable Multiboard
17297 # LocalWords: SPARCAUDIO SparcClassic Ultras DBRI Sparcbook sparcaudio SUNBPP
17298 # LocalWords: UltraDMA WDC CRC CONNTRACK IPTABLES iptables nfmark interface's
17299 # LocalWords: tdfxfb TNTx HGA hgafb VERBOSEDEBUG SunTrunking SunSoft XIRTULIP
17300 # LocalWords: ethercards PNIC Macronix MXIC ASIX xircom Mustek MDC gphoto mdc
17301 # LocalWords: CramFs Cramfs uid cramfs AVM's kernelcapi PCIV cdrdao Cdparanoia
17302 # LocalWords: DMX Domex dmx wellington ftdi sio Accton Billington Corega FEter
17303 # LocalWords: MELCO LUA PNA Linksys SNC chkdsk AWACS Webcam RAMFS Ramfs ramfs
17304 # LocalWords: ramfiles MAKEDEV pty WDTPCI APA apa