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,
3214 Matrox G400 or G450 card in your box. At this time, support for the G100
3215 is untested and support for G450 is highly experimental.
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/G450 support
3245 CONFIG_FB_MATROX_G100
3246 Say Y here if you have a Matrox G100, G200, G400 or G450 based
3247 video card. If you select "Advanced lowlevel driver options", you
3248 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
3249 pixel and 32 bpp packed pixel. You can also use font widths
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 WARNING !!! This support does not work with G450 !!!
3275 Say Y or M here if you want to use a secondary head (meaning two
3276 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
3277 head is not compatible with accelerated XFree 3.3.x SVGA servers -
3278 secondary head output is blanked while you are in X. With XFree
3279 3.9.17 preview you can use both heads if you use SVGA over fbdev or
3280 the fbdev driver on first head and the fbdev driver on second head.
3282 If you compile it as module, two modules are created,
3283 matroxfb_crtc2.o and matroxfb_maven.o. Matroxfb_maven is needed for
3284 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
3285 also load i2c-matroxfb to get it to run.
3287 The driver starts in monitor mode and you must use the matroxset
3288 tool (available at ftp://platan.vc.cvut.cz/pub/linux/matrox-latest)
3289 to switch it to PAL or NTSC or to swap primary and secondary head
3290 outputs. Secondary head driver also always start in 640x480
3291 resolution, you must use fbset to change it.
3293 Also do not forget that second head supports only 16 and 32 bpp
3294 packed pixels, so it is a good idea to compile them into the kernel
3295 too. You can use only some font widths, as the driver uses generic
3296 painting procedures (the secondary head does not use acceleration
3299 There is no need for enabling 'Matrox multihead support' if you have
3300 only one Matrox card in the box.
3302 Matrox G450 second head support
3303 CONFIG_FB_MATROX_G450
3304 Say Y or M here if you want to use a secondary head (meaning two
3305 monitors in parallel) on G450.
3307 If you compile it as module, two modules are created,
3308 matroxfb_crtc2.o and matroxfb_g450.o. Both modules are needed if you
3309 want two independent display devices.
3311 The driver starts in monitor mode and currently does not support
3312 output in TV modes. You must use the matroxset tool (available
3313 at ftp://platan.vc.cvut.cz/pub/linux/matrox-latest) to swap primary
3314 and secondary head outputs. Secondary head driver always start in
3315 640x480 resolution and you must use fbset to change it.
3317 Also do not forget that second head supports only 16 and 32 bpp
3318 packed pixels, so it is a good idea to compile them into the kernel
3319 too. You can use only some font widths, as the driver uses generic
3320 painting procedures (the secondary head does not use acceleration
3323 There is no need for enabling 'Matrox multihead support' if you have
3324 only one Matrox card in the box.
3326 Matrox unified driver multihead support
3327 CONFIG_FB_MATROX_MULTIHEAD
3328 Say Y here if you have more than one (supported) Matrox device in
3329 your computer and you want to use all of them for different monitors
3330 ("multihead"). If you have only one device, you should say N because
3331 the driver compiled with Y is larger and a bit slower, especially on
3334 If you said M to "Matrox unified accelerated driver" and N here, you
3335 will still be able to use several Matrox devices simultaneously:
3336 insert several instances of the module matroxfb.o into the kernel
3337 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
3338 for the different Matrox devices. This method is slightly faster but
3339 uses 40 KB of kernel memory per Matrox card.
3341 MDA text console (dual-headed)
3343 Say Y here if you have an old MDA or monochrome Hercules graphics
3344 adapter in your system acting as a second head ( = video card). You
3345 will then be able to use two monitors with your Linux system. Do not
3346 say Y here if your MDA card is the primary card in your system; the
3347 normal VGA driver will handle it.
3349 This driver is also available as a module ( = code which can be
3350 inserted and removed from the running kernel whenever you want).
3351 The module will be called mdacon.o. If you want to compile it as
3352 a module, say M here and read Documentation/modules.txt.
3356 SBUS and UPA frame buffers
3358 Say Y if you want support for SBUS or UPA based frame buffer device.
3360 Creator/Creator3D support
3362 This is the frame buffer device driver for the Creator and Creator3D
3365 CGsix (GX,TurboGX) support
3367 This is the frame buffer device driver for the CGsix (GX, TurboGX)
3372 This is the frame buffer device driver for the BWtwo frame buffer.
3376 This is the frame buffer device driver for the CGthree frame buffer.
3378 TCX (SS4/SS5 only) support
3380 This is the frame buffer device driver for the TCX 24/8bit frame
3383 Virtual Frame Buffer support (ONLY FOR TESTING!)
3385 This is a `virtual' frame buffer device. It operates on a chunk of
3386 unswapable kernel memory instead of on the memory of a graphics
3387 board. This means you cannot see any output sent to this frame
3388 buffer device, while it does consume precious memory. The main use
3389 of this frame buffer device is testing and debugging the frame
3390 buffer subsystem. Do NOT enable it for normal systems! To protect
3391 the innocent, it has to be enabled explicitly at boot time using the
3392 kernel option `video=vfb:'.
3394 This driver is also available as a module ( = code which can be
3395 inserted and removed from the running kernel whenever you want). The
3396 module will be called vfb.o. If you want to compile it as a module,
3397 say M here and read Documentation/modules.txt.
3402 This is a framebuffer device for the SA-1100 LCD Controller.
3403 See http://www.linux-fbdev.org/ for information on framebuffer
3406 If you plan to use the LCD display with your SA-1100 system, say
3409 Advanced low level driver options
3410 CONFIG_FBCON_ADVANCED
3411 The frame buffer console uses character drawing routines that are
3412 tailored to the specific organization of pixels in the memory of
3413 your graphics hardware. These are called the low level frame buffer
3414 console drivers. Note that they are used for text console output
3415 only; they are NOT needed for graphical applications.
3417 If you say N here, the needed low level drivers are automatically
3418 enabled, depending on what frame buffer devices you selected above.
3419 This is recommended for most users.
3421 If you say Y here, you have more fine-grained control over which low
3422 level drivers are enabled. You can e.g. leave out low level drivers
3423 for color depths you do not intend to use for text consoles.
3425 Low level frame buffer console drivers can be modules ( = code which
3426 can be inserted and removed from the running kernel whenever you
3427 want). The modules will be called fbcon-*.o. If you want to compile
3428 (some of) them as modules, read Documentation/modules.txt.
3434 This is the low level frame buffer console driver for monochrome
3435 (2 colors) packed pixels.
3437 2 bpp packed pixels support
3439 This is the low level frame buffer console driver for 2 bits per
3440 pixel (4 colors) packed pixels.
3442 4 bpp packed pixels support
3444 This is the low level frame buffer console driver for 4 bits per
3445 pixel (16 colors) packed pixels.
3447 8 bpp packed pixels support
3449 This is the low level frame buffer console driver for 8 bits per
3450 pixel (256 colors) packed pixels.
3452 16 bpp packed pixels support
3454 This is the low level frame buffer console driver for 15 or 16 bits
3455 per pixel (32K or 64K colors, also known as `hicolor') packed
3458 24 bpp packed pixels support
3460 This is the low level frame buffer console driver for 24 bits per
3461 pixel (16M colors, also known as `truecolor') packed pixels. It is
3462 NOT for `sparse' 32 bits per pixel mode.
3464 32 bpp packed pixels support
3466 This is the low level frame buffer console driver for 32 bits per
3467 pixel (16M colors, also known as `truecolor') sparse packed pixels.
3469 Amiga bitplanes support
3471 This is the low level frame buffer console driver for 1 to 8
3472 bitplanes (2 to 256 colors) on Amiga.
3474 Amiga interleaved bitplanes support
3476 This is the low level frame buffer console driver for 1 to 8
3477 interleaved bitplanes (2 to 256 colors) on Amiga.
3479 Atari interleaved bitplanes (2 planes) support
3480 CONFIG_FBCON_IPLAN2P2
3481 This is the low level frame buffer console driver for 2 interleaved
3482 bitplanes (4 colors) on Atari.
3484 Atari interleaved bitplanes (4 planes) support
3485 CONFIG_FBCON_IPLAN2P4
3486 This is the low level frame buffer console driver for 4 interleaved
3487 bitplanes (16 colors) on Atari.
3489 Atari interleaved bitplanes (8 planes) support
3490 CONFIG_FBCON_IPLAN2P8
3491 This is the low level frame buffer console driver for 8 interleaved
3492 bitplanes (256 colors) on Atari.
3494 Mac variable bpp packed pixels support
3496 This is the low level frame buffer console driver for 1/2/4/8/16/32
3497 bits per pixel packed pixels on Mac. It supports variable font
3498 widths for low resolution screens.
3500 HGA monochrome support (EXPERIMENTAL)
3502 This is the low level frame buffer console driver for Hercules mono
3505 VGA characters/attributes support
3507 This is the low level frame buffer console driver for VGA text mode;
3508 it is used by frame buffer device drivers that support VGA text
3511 Parallel-port support
3513 If you want to use devices connected to your machine's parallel port
3514 (the connector at the computer with 25 holes), e.g. printer, ZIP
3515 drive, PLIP link (Parallel Line Internet Protocol is mainly used to
3516 create a mini network by connecting the parallel ports of two local
3517 machines) etc., then you need to say Y here; please read
3518 Documentation/parport.txt and drivers/parport/BUGS-parport.
3520 For extensive information about drivers for many devices attaching
3521 to the parallel port see http://www.torque.net/linux-pp.html on the
3524 It is possible to share a single parallel port among several devices
3525 and it is safe to compile all the corresponding drivers into the
3526 kernel. If you want to compile parallel port support as a module ( =
3527 code which can be inserted in and removed from the running kernel
3528 whenever you want), say M here and read Documentation/modules.txt.
3529 The module will be called parport.o. If you have more than one
3530 parallel port and want to specify which port and IRQ to be used by
3531 this driver at module load time, take a look at
3532 Documentation/parport.txt.
3538 You should say Y here if you have a PC-style parallel port. All IBM
3539 PC compatible computers and some Alphas have PC-style parallel
3542 This code is also available as a module. If you want to compile it
3543 as a module ( = code which can be inserted in and removed from the
3544 running kernel whenever you want), say M here and read
3545 Documentation/modules.txt. The module will be called parport_pc.o.
3549 Use FIFO/DMA if available
3550 CONFIG_PARPORT_PC_FIFO
3551 Many parallel port chipsets provide hardware that can speed up
3552 printing. Say Y here if you want to take advantage of that.
3554 As well as actually having a FIFO, or DMA capability, the kernel
3555 will need to know which IRQ the parallel port has. By default,
3556 parallel port interrupts will not be used, and so neither will the
3557 FIFO. See Documentation/parport.txt to find out how to specify
3558 which IRQ/DMA to use.
3560 SuperIO chipset support (EXPERIMENTAL)
3561 CONFIG_PARPORT_PC_SUPERIO
3562 Saying Y here enables some probes for Super-IO chipsets in order to
3563 find out things like base addresses, IRQ lines and DMA channels. It
3566 Support for PCMCIA management for PC-style ports
3567 CONFIG_PARPORT_PC_PCMCIA
3568 Say Y here if you need PCMCIA support for your PC-style parallel
3569 ports. If unsure, say N.
3571 Support foreign hardware
3572 CONFIG_PARPORT_OTHER
3573 Say Y here if you want to be able to load driver modules to support
3574 other non-standard types of parallel ports. This causes a
3575 performance loss, so most people say N.
3577 Sun Ultra/AX-style hardware
3579 Say Y here if you need support for the parallel port hardware on Sun
3580 Ultra/AX machines. This code is also available as a module (say M),
3581 called parport_ax.o. If in doubt, saying N is the safe plan.
3583 Amiga built-in parallel port support
3584 CONFIG_PARPORT_AMIGA
3585 Say Y here if you need support for the parallel port hardware on
3586 Amiga machines. This code is also available as a module (say M),
3587 called parport_amiga.o. If in doubt, saying N is the safe plan.
3589 Atari built-in parallel port support
3590 CONFIG_PARPORT_ATARI
3591 Say Y here if you need support for the parallel port hardware on
3592 Atari machines. This code is also available as a module (say M),
3593 called parport_atari.o. If in doubt, saying N is the safe plan.
3595 Multiface 3 parallel port card support
3597 Say Y here if you need parallel port support for the MFC3 card.
3598 This code is also available as a module (say M), called
3599 parport_mfc3.o. If in doubt, saying N is the safe plan.
3601 Support IEEE1284 status readback
3602 CONFIG_PRINTER_READBACK
3603 If you have a device on your parallel port that support this
3604 protocol, this option will allow the device to report its status. It
3607 IEEE1284 transfer modes
3609 If you have a printer that supports status readback or device ID, or
3610 want to use a device that uses enhanced parallel port transfer modes
3611 such as EPP and ECP, say Y here to enable advanced IEEE 1284
3612 transfer modes. Also say Y if you want device ID information to
3613 appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
3615 Enable loadable module support
3617 Kernel modules are small pieces of compiled code which can be
3618 inserted in or removed from the running kernel, using the programs
3619 insmod and rmmod. This is described in the file
3620 Documentation/modules.txt, including the fact that you have to say
3621 "make modules" in order to compile the modules that you chose during
3622 kernel configuration. Modules can be device drivers, file systems,
3623 binary executable formats, and so on. If you think that you may want
3624 to make use of modules with this kernel in the future, then say Y
3625 here. If unsure, say Y.
3627 Set version information on all symbols for modules
3629 Usually, modules have to be recompiled whenever you switch to a new
3630 kernel. Saying Y here makes it possible, and safe, to use the
3631 same modules even after compiling a new kernel; this requires the
3632 program modprobe. All the software needed for module support is in
3633 the modutils package (check the file Documentation/Changes for
3634 location and latest version). NOTE: if you say Y here but don't
3635 have the program genksyms (which is also contained in the above
3636 mentioned modutils package), then the building of your kernel will
3637 fail. If you are going to use modules that are generated from
3638 non-kernel sources, you would benefit from this option. Otherwise
3639 it's not that important. So, N ought to be a safe bet.
3641 Kernel module loader support
3643 Normally when you have selected some drivers and/or file systems to
3644 be created as loadable modules, you also have the responsibility to
3645 load the corresponding modules (using the programs insmod or
3646 modprobe) before you can use them. If you say Y here however, the
3647 kernel will be able to load modules for itself: when a part of the
3648 kernel needs a module, it runs modprobe with the appropriate
3649 arguments, thereby loading the module if it is available. (This is a
3650 replacement for kerneld.) Say Y here and read about configuring it
3651 in Documentation/kmod.txt.
3653 ARP daemon support (EXPERIMENTAL)
3655 Normally, the kernel maintains an internal cache which maps IP
3656 addresses to hardware addresses on the local network, so that
3657 Ethernet/Token Ring/ etc. frames are sent to the proper address on
3658 the physical networking layer. For small networks having a few
3659 hundred directly connected hosts or less, keeping this address
3660 resolution (ARP) cache inside the kernel works well. However,
3661 maintaining an internal ARP cache does not work well for very large
3662 switched networks, and will use a lot of kernel memory if TCP/IP
3663 connections are made to many machines on the network.
3665 If you say Y here, the kernel's internal ARP cache will never grow
3666 to more than 256 entries (the oldest entries are expired in a LIFO
3667 manner) and communication will be attempted with the user space ARP
3668 daemon arpd. Arpd then answers the address resolution request either
3669 from its own cache or by asking the net.
3671 This code is experimental and also obsolete. If you want to use it,
3672 you need to find a version of the daemon arpd on the net somewhere,
3673 and you should also say Y to "Kernel/User network link driver",
3674 below. If unsure, say N.
3678 These are the protocols used on the Internet and on most local
3679 Ethernets. It is highly recommended to say Y here (this will enlarge
3680 your kernel by about 144 KB), since some programs (e.g. the X window
3681 system) use TCP/IP even if your machine is not connected to any
3682 other computer. You will get the so-called loopback device which
3683 allows you to ping yourself (great fun, that!).
3685 For an excellent introduction to Linux networking, please read the
3686 NET-3-HOWTO, available from
3687 http://www.linuxdoc.org/docs.html#howto .
3689 This option is also necessary if you want to use the full power of
3690 term (term is a program which gives you almost full Internet
3691 connectivity if you have a regular dial up shell account on some
3692 Internet connected Unix computer; for more information, read
3693 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html ).
3695 If you say Y here and also to "/proc file system support" and
3696 "Sysctl support" below, you can change various aspects of the
3697 behavior of the TCP/IP code by writing to the (virtual) files in
3698 /proc/sys/net/ipv4/*; the options are explained in the file
3699 Documentation/networking/ip-sysctl.txt.
3701 Short answer: say Y.
3705 This is code for addressing several networked computers at once,
3706 enlarging your kernel by about 2 KB. You need multicasting if you
3707 intend to participate in the MBONE, a high bandwidth network on top
3708 of the Internet which carries audio and video broadcasts. More
3709 information about the MBONE is on the WWW at
3710 http://www-itg.lbl.gov/mbone/ . Information about the multicast
3711 capabilities of the various network cards is contained in
3712 Documentation/networking/multicast.txt. For most people, it's safe
3716 CONFIG_IP_ADVANCED_ROUTER
3717 If you intend to run your Linux box mostly as a router, i.e. as a
3718 computer that forwards and redistributes network packets, say Y; you
3719 will then be presented with several options that allow more precise
3720 control about the routing process.
3722 The answer to this question won't directly affect the kernel:
3723 answering N will just cause this configure script to skip all the
3724 questions about advanced routing.
3726 Note that your box can only act as a router if you enable IP
3727 forwarding in your kernel; you can do that by saying Y to "/proc
3728 file system support" and "Sysctl support" below and executing the
3731 echo "1" > /proc/sys/net/ipv4/ip_forward
3733 at boot time after the /proc file system has been mounted.
3735 If you turn on IP forwarding, you will also get the rp_filter, which
3736 automatically rejects incoming packets if the routing table entry
3737 for their source address doesn't match the network interface they're
3738 arriving on. This has security advantages because it prevents the
3739 so-called IP spoofing, however it can pose problems if you use
3740 asymmetric routing (packets from you to a host take a different path
3741 than packets from that host to you) or if you operate a non-routing
3742 host which has several IP addresses on different interfaces. To turn
3745 echo 0 > /proc/sys/net/ipv4/conf/<device>/rp_filter
3747 echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter
3749 If unsure, say N here.
3752 CONFIG_IP_MULTIPLE_TABLES
3753 Normally, a router decides what to do with a received packet based
3754 solely on the packet's final destination address. If you say Y here,
3755 the Linux router will also be able to take the packet's source
3756 address into account. Furthermore, if you also say Y to "IP: use TOS
3757 value as routing key" below, the TOS (Type-Of-Service) field of the
3758 packet can be used for routing decisions as well. In addition, if
3759 you say Y here and to "IP: fast network address translation" below,
3760 the router will also be able to modify source and destination
3761 addresses of forwarded packets.
3763 If you are interested in this, please see the preliminary
3764 documentation at http://www.compendium.com.ar/policy-routing.txt and
3765 ftp://post.tepkom.ru/pub/vol2/Linux/docs/advanced-routing.tex . You
3766 will need supporting software from ftp://ftp.inr.ac.ru/ip-routing/
3770 IP: equal cost multipath
3771 CONFIG_IP_ROUTE_MULTIPATH
3772 Normally, the routing tables specify a single action to be taken in
3773 a deterministic manner for a given packet. If you say Y here
3774 however, it becomes possible to attach several actions to a packet
3775 pattern, in effect specifying several alternative paths to travel
3776 for those packets. The router considers all these paths to be of
3777 equal "cost" and chooses one of them in a non-deterministic fashion
3778 if a matching packet arrives.
3780 IP: use TOS value as routing key
3782 The header of every IP packet carries a TOS (Type Of Service) value
3783 with which the packet requests a certain treatment, e.g. low latency
3784 (for interactive traffic), high throughput, or high reliability. If
3785 you say Y here, you will be able to specify different routes for
3786 packets with different TOS values.
3788 IP: use netfilter MARK value as routing key
3789 CONFIG_IP_ROUTE_FWMARK
3790 If you say Y here, you will be able to specify different routes for
3791 packets with different mark values (see iptables(8), MARK target).
3793 IP: verbose route monitoring
3794 CONFIG_IP_ROUTE_VERBOSE
3795 If you say Y here, which is recommended, then the kernel will print
3796 verbose messages regarding the routing, for example warnings about
3797 received packets which look strange and could be evidence of an
3798 attack or a misconfigured system somewhere. The information is
3799 handled by the klogd daemon which is responsible for kernel messages
3802 IP: large routing tables
3803 CONFIG_IP_ROUTE_LARGE_TABLES
3804 If you have routing zones that grow to more than about 64 entries,
3805 you may want to say Y here to speed up the routing process.
3807 IP: fast network address translation
3809 If you say Y here, your router will be able to modify source and
3810 destination addresses of packets that pass through it, in a manner
3811 you specify. General information about Network Address Translation
3812 can be gotten from the document
3813 http://www.csn.tu-chemnitz.de/~mha/linux-ip-nat/diplom/nat.html
3815 IP: kernel level autoconfiguration
3817 This enables automatic configuration of IP addresses of devices and
3818 of the routing table during kernel boot, based on either information
3819 supplied on the kernel command line or by BOOTP or RARP protocols.
3820 You need to say Y only for diskless machines requiring network
3821 access to boot (in which case you want to say Y to "Root file system
3822 on NFS" as well), because all other machines configure the network
3823 in their startup scripts.
3827 If you want your Linux box to mount its whole root file system (the
3828 one containing the directory /) from some other computer over the
3829 net via NFS and you want the IP address of your computer to be
3830 discovered automatically at boot time using the BOOTP protocol (a
3831 special protocol designed for doing this job), say Y here. In case
3832 the boot ROM of your network card was designed for booting Linux and
3833 does BOOTP itself, providing all necessary information on the kernel
3834 command line, you can say N here. If unsure, say Y. Note that if you
3835 want to use BOOTP, a BOOTP server must be operating on your network.
3836 Read Documentation/nfsroot.txt for details.
3840 If you want your Linux box to mount its whole root file system (the
3841 one containing the directory /) from some other computer over the
3842 net via NFS and you want the IP address of your computer to be
3843 discovered automatically at boot time using the RARP protocol (an
3844 older protocol which is being obsoleted by BOOTP and DHCP), say Y
3845 here. Note that if you want to use RARP, a RARP server must be
3846 operating on your network. Read Documentation/nfsroot.txt for
3851 Tunneling means encapsulating data of one protocol type within
3852 another protocol and sending it over a channel that understands the
3853 encapsulating protocol. This particular tunneling driver implements
3854 encapsulation of IP within IP, which sounds kind of pointless, but
3855 can be useful if you want to make your (or some other) machine
3856 appear on a different network than it physically is, or to use
3857 mobile-IP facilities (allowing laptops to seamlessly move between
3858 networks without changing their IP addresses; check out
3859 http://anchor.cs.binghamton.edu/~mobileip/LJ/index.html ).
3861 Saying Y to this option will produce two modules ( = code which can
3862 be inserted in and removed from the running kernel whenever you
3863 want). Most people won't need this and can say N.
3865 IP: GRE tunnels over IP
3867 Tunneling means encapsulating data of one protocol type within
3868 another protocol and sending it over a channel that understands the
3869 encapsulating protocol. This particular tunneling driver implements
3870 GRE (Generic Routing Encapsulation) and at this time allows
3871 encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
3872 This driver is useful if the other endpoint is a Cisco router: Cisco
3873 likes GRE much better than the other Linux tunneling driver ("IP:
3874 tunneling" above). In addition, GRE allows multicast redistribution
3877 IP: broadcast GRE over IP
3878 CONFIG_NET_IPGRE_BROADCAST
3879 One application of GRE/IP is to construct a broadcast WAN (Wide Area
3880 Network), which looks like a normal Ethernet LAN (Local Area
3881 Network), but can be distributed all over the Internet. If you want
3882 to do that, say Y here and to "IP: multicast routing" below.
3884 IP: multicast routing
3886 This is used if you want your machine to act as a router for IP
3887 packets that have several destination addresses. It is needed on the
3888 MBONE, a high bandwidth network on top of the Internet which carries
3889 audio and video broadcasts. In order to do that, you would most
3890 likely run the program mrouted. Information about the multicast
3891 capabilities of the various network cards is contained in
3892 Documentation/networking/multicast.txt. If you haven't heard about
3893 it, you don't need it.
3895 IP: PIM-SM version 1 support
3897 Kernel side support for Sparse Mode PIM (Protocol Independent
3898 Multicast) version 1. This multicast routing protocol is used widely
3899 because Cisco supports it. You need special software to use it
3900 (pimd-v1). Please see http://netweb.usc.edu/pim/ for more
3901 information about PIM.
3903 Say Y if you want to use PIM-SM v1. Note that you can say N here if
3904 you just want to use Dense Mode PIM.
3906 IP: PIM-SM version 2 support
3908 Kernel side support for Sparse Mode PIM version 2. In order to use
3909 this, you need an experimental routing daemon supporting it (pimd or
3910 gated-5). This routing protocol is not used widely, so say N unless
3911 you want to play with it.
3913 PC/TCP compatibility mode
3915 If you have been having difficulties telnetting to your Linux
3916 machine from a DOS system that uses (broken) PC/TCP networking
3917 software (all versions up to OnNet 2.0) over your local Ethernet try
3918 saying Y here. Everyone else says N.
3920 People having problems with NCSA telnet should see the file
3921 Documentation/networking/ncsa-telnet.
3923 Path MTU Discovery (normally enabled)
3924 CONFIG_PATH_MTU_DISCOVERY
3925 MTU (maximal transfer unit) is the size of the chunks we send out
3926 over the net. "Path MTU Discovery" means that, instead of always
3927 sending very small chunks, we start out sending big ones and if we
3928 then discover that some host along the way likes its chunks smaller,
3929 we adjust to a smaller size. This is good, so most people say Y
3932 However, some DOS software (versions of DOS NCSA telnet and Trumpet
3933 Winsock in PPP mode) is broken and won't be able to connect to your
3934 Linux machine correctly in all cases (especially through a terminal
3935 server) unless you say N here. See
3936 Documentation/networking/ncsa-telnet for the location of fixed NCSA
3937 telnet clients. If in doubt, say Y.
3939 Disable NAGLE algorithm (normally enabled)
3940 CONFIG_TCP_NAGLE_OFF
3941 The NAGLE algorithm works by requiring an acknowledgment before
3942 sending small IP frames (packets). This keeps tiny telnet and
3943 rlogin packets from congesting Wide Area Networks. Most people
3944 strongly recommend to say N here, thereby leaving NAGLE
3945 enabled. Those programs that would benefit from disabling this
3946 facility can do it on a per connection basis themselves.
3948 IP: Allow large windows (not recommended if <16 MB of memory)
3950 On high speed, long distance networks the performance limit on
3951 networking becomes the amount of data the sending machine can buffer
3952 until the other end confirms its reception. (At 45 Mbit/second there
3953 are a lot of bits between New York and London ...). If you say Y
3954 here, bigger buffers can be used which allows larger amounts of data
3955 to be "in flight" at any given time. It also means a user process
3956 can require a lot more memory for network buffers and thus this
3957 option is best used only on machines with 16 MB of memory or higher.
3958 Unless you are using long links with end to end speeds of over 2
3959 Mbit a second or satellite links this option will make no difference
3964 If you say Y here, you will include support for Unix domain sockets;
3965 sockets are the standard Unix mechanism for establishing and
3966 accessing network connections. Many commonly used programs such as
3967 the X Window system and syslog use these sockets even if your
3968 machine is not connected to any network. Unless you are working on
3969 an embedded system or something similar, you therefore definitely
3972 However, the socket support is also available as a module ( = code
3973 which can be inserted in and removed from the running kernel
3974 whenever you want). If you want to compile it as a module, say M
3975 here and read Documentation/modules.txt. The module will be called
3976 unix.o. If you try building this as a module and you have said Y to
3977 "Kernel module loader support" above, be sure to add 'alias net-pf-1
3978 unix' to your /etc/modules.conf file. Note that several important
3979 services won't work correctly if you say M here and then neglect to
3982 Say Y unless you know what you are doing.
3984 The IPv6 protocol (EXPERIMENTAL)
3986 This is experimental support for the next version of the Internet
3987 Protocol: IP version 6 (also called IPng "IP next generation").
3988 Features of this new protocol include: expanded address space,
3989 authentication and privacy, and seamless interoperability with the
3990 current version of IP (IP version 4). For general information about
3991 IPv6, see http://playground.sun.com/pub/ipng/html/ipng-main.html ;
3992 for specific information about IPv6 under Linux read the HOWTO at
3993 http://www.bieringer.de/linux/IPv6/ and the file net/ipv6/README in
3996 If you want to use IPv6, please upgrade to the newest net-tools as
3997 given in Documentation/Changes. You will still be able to do regular
3998 IPv4 networking as well.
4000 This protocol support is also available as a module ( = code which
4001 can be inserted in and removed from the running kernel whenever you
4002 want). The module will be called ipv6.o. If you want to compile it
4003 as a module, say M here and read Documentation/modules.txt.
4005 It is safe to say N here for now.
4007 IPv6: enable EUI-64 token format
4009 6bone, the network of computers using the IPv6 protocol, is moving
4010 to a new aggregatable address format and a new link local address
4011 assignment (EUI-64). Say Y if your site has upgraded already, or
4012 has started to upgrade.
4014 IPv6: disable provider based addresses
4016 Linux tries to operate correctly when your site has moved to EUI-64
4017 only partially. Unfortunately, the two address formats (old:
4018 "provider based" and new: "aggregatable") are incompatible. Say Y if
4019 your site finished the upgrade to EUI-64, and/or you encountered
4020 some problems caused by the presence of two link-local addresses on
4023 IPv6: routing messages via old netlink
4025 You can say Y here to receive routing messages from the IPv6 code
4026 through the old netlink interface. However, a better option is to
4027 say Y to "Kernel/User network link driver" and to "Routing
4030 Kernel httpd acceleration (EXPERIMENTAL)
4032 The kernel httpd acceleration daemon (kHTTPd) is a (limited) web
4033 server built into the kernel. It is limited since it can only serve
4034 files from the file system and cannot deal with executable content
4035 such as CGI scripts. Serving files is sped up if you use kHTTPd.
4036 If kHTTPd is not able to fulfill a request, it can transparently
4037 pass it through to a user space web server such as apache.
4039 Saying "M" here builds the kHTTPd module; this is NOT enough to have
4040 a working kHTTPd. For safety reasons, the module has to be activated
4041 by doing a "echo 1 > /proc/sys/net/khttpd/start" after inserting the
4044 Before using this, read the README in net/khttpd !
4046 The kHTTPd is experimental. Be careful when using it on a production
4047 machine. Also note that kHTTPd doesn't support virtual servers yet.
4051 This is support for the Novell networking protocol, IPX, commonly
4052 used for local networks of Windows machines. You need it if you want
4053 to access Novell NetWare file or print servers using the Linux
4054 Novell client ncpfs (available from
4055 ftp://metalab.unc.edu/pub/Linux/system/filesystems/ ) or from within
4056 the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
4057 http://www.linuxdoc.org/docs.html#howto ). In order to do the
4058 former, you'll also have to say Y to "NCP file system support",
4061 IPX is similar in scope to IP, while SPX, which runs on top of IPX,
4062 is similar to TCP. There is also experimental support for SPX in
4063 Linux (see "SPX networking", below).
4065 To turn your Linux box into a fully featured NetWare file server and
4066 IPX router, say Y here and fetch either lwared from
4067 ftp://metalab.unc.edu/pub/Linux/system/network/daemons/ or mars_nwe
4068 from ftp://ftp.gwdg.de/pub/linux/misc/ncpfs . For more information,
4069 read the IPX-HOWTO available from
4070 http://www.linuxdoc.org/docs.html#howto .
4072 General information about how to connect Linux, Windows machines and
4073 Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
4075 The IPX driver would enlarge your kernel by about 16 KB. This driver
4076 is also available as a module ( = code which can be inserted in and
4077 removed from the running kernel whenever you want). The module will
4078 be called ipx.o. If you want to compile it as a module, say M here
4079 and read Documentation/modules.txt. Unless you want to integrate
4080 your Linux box with a local Novell network, say N.
4082 IPX: Full internal IPX network
4084 Every IPX network has an address that identifies it. Sometimes it is
4085 useful to give an IPX "network" address to your Linux box as well
4086 (for example if your box is acting as a file server for different
4087 IPX networks: it will then be accessible from everywhere using the
4088 same address). The way this is done is to create a virtual internal
4089 "network" inside your box and to assign an IPX address to this
4090 network. Say Y here if you want to do this; read the IPX-HOWTO at
4091 http://www.linuxdoc.org/docs.html#howto for details.
4093 The full internal IPX network enables you to allocate sockets on
4094 different virtual nodes of the internal network. This is done by
4095 evaluating the field sipx_node of the socket address given to the
4096 bind call. So applications should always initialize the node field
4097 to 0 when binding a socket on the primary network. In this case the
4098 socket is assigned the default node that has been given to the
4099 kernel when the internal network was created. By enabling the full
4100 internal IPX network the cross-forwarding of packets targeted at
4101 'special' sockets to sockets listening on the primary network is
4102 disabled. This might break existing applications, especially RIP/SAP
4103 daemons. A RIP/SAP daemon that works well with the full internal net
4104 can be found on ftp://ftp.gwdg.de/pub/linux/misc/ncpfs .
4106 If you don't know what you are doing, say N.
4108 IPX: SPX networking (EXPERIMENTAL)
4110 The Sequenced Packet eXchange protocol is a transport layer protocol
4111 built on top of IPX. It is used in Novell NetWare systems for
4112 client-server applications and is similar to TCP (which runs on top
4115 Note that Novell NetWare file sharing does not use SPX; it uses a
4116 protocol called NCP, for which separate Linux support is available
4117 ("NCP file system support" below for the client side, and the user
4118 space programs lwared or mars_nwe for the server side).
4120 Say Y here if you have use for SPX; read the IPX-HOWTO at
4121 http://www.linuxdoc.org/docs.html#howto for details.
4123 This driver is also available as a module ( = code which can be
4124 inserted in and removed from the running kernel whenever you want).
4125 The module will be called af_spx.o. If you want to compile it as a
4126 module, say M here and read Documentation/modules.txt.
4128 DECnet networking (EXPERIMENTAL)
4130 The DECnet networking protocol was used in many products made by
4131 Digital (now Compaq). It provides reliable stream and sequenced
4132 packet communications over which run a variety of services similar
4133 to those which run over TCP/IP.
4135 To find some tools to use with the kernel layer support, please
4136 look at Patrick Caulfield's web site:
4137 http://linux.dreamtime.org/decnet/
4139 More detailed documentation is available in the
4140 Documentation/networking/decnet.txt file.
4142 Be sure to say Y to "/proc file system support" and "Sysctl support"
4143 below when using DECnet, since you will need sysctl support to aid
4144 in configuration at run time.
4146 The DECnet code is also available as a module ( = code which can be
4147 inserted in and removed from the running kernel whenever you want).
4148 The module is called decnet.o.
4150 DECnet SIOCFIGCONF support
4151 CONFIG_DECNET_SIOCGIFCONF
4152 This option should only be turned on if you are really sure that
4153 you know what you are doing. It can break other applications which
4154 use this system call and the proper way to get the information
4155 provided by this call is to use rtnetlink.
4159 DECnet Router Support (EXPERIMENTAL)
4160 CONFIG_DECNET_ROUTER
4161 Add support for turning your DECnet Endnode into a level 1 or 2
4162 router. This is an unfinished option for developers only. If you do
4163 say Y here, then make sure that you also say Y to "Kernel/User
4164 network link driver", "Routing messages" and "Network packet
4165 filtering". The first two are required to allow configuration via
4166 rtnetlink (currently you need Alexey Kuznetsov's iproute2 package
4167 from ftp://ftp.inr.ac.ru). The "Network packet filtering" option
4168 will be required for the forthcoming routing daemon to work.
4170 See Documentation/networking/decnet.txt for more information.
4172 DECnet: use FWMARK value as routing key
4173 CONFIG_DECNET_ROUTE_FWMARK
4174 If you say Y here, you will be able to specify different routes for
4175 packets with different FWMARK ("firewalling mark") values
4176 (see ipchains(8), "-m" argument).
4178 Appletalk interfaces support
4180 AppleTalk is the way Apple computers speak to each other on a
4181 network. If your Linux box is connected to such a network and you
4182 want to join the conversation, say Y.
4184 AppleTalk protocol support
4186 AppleTalk is the way Apple computers speak to each other on a
4187 network. If your Linux box is connected to such a network and you
4188 want to join the conversation, say Y. You will need to use the
4189 netatalk package so that your Linux box can act as a print and file
4190 server for Macs as well as access AppleTalk printers. Check out
4191 http://threepio.hitchcock.org/cgi-bin/faq/netatalk/faq.pl on the WWW
4192 for details. EtherTalk is the name used for AppleTalk over Ethernet
4193 and the cheaper and slower LocalTalk is AppleTalk over a proprietary
4194 Apple network using serial links. EtherTalk and LocalTalk are fully
4197 General information about how to connect Linux, Windows machines and
4198 Macs is on the WWW at http://www.eats.com/linux_mac_win.html . The
4199 NET-3-HOWTO, available from
4200 http://www.linuxdoc.org/docs.html#howto , contains valuable
4201 information as well.
4203 This driver is also available as a module ( = code which can be
4204 inserted in and removed from the running kernel whenever you want).
4205 The module is called appletalk.o. If you want to compile it as a
4206 module, say M here and read Documentation/modules.txt. I hear that
4207 the GNU boycott of Apple is over, so even politically correct people
4208 are allowed to say Y here.
4210 AppleTalk-IP driver support
4212 This allows IP networking for users who only have AppleTalk
4213 networking available. This feature is experimental. With this
4214 driver, you can encapsulate IP inside AppleTalk (e.g. if your Linux
4215 box is stuck on an AppleTalk only network) or decapsulate (e.g. if
4216 you want your Linux box to act as an Internet gateway for a zoo of
4217 AppleTalk connected Macs). Please see the file
4218 Documentation/networking/ipddp.txt for more information.
4220 If you say Y here, the AppleTalk-IP support will be compiled into
4221 the kernel. In this case, you can either use encapsulation or
4222 decapsulation, but not both. With the following two questions, you
4223 decide which one you want.
4225 If you say M here, the AppleTalk-IP support will be compiled as a
4226 module ( = code which can be inserted in and removed from the
4227 running kernel whenever you want, read Documentation/modules.txt).
4228 The module is called ipddp.o. In this case, you will be able to use
4229 both encapsulation and decapsulation simultaneously, by loading two
4230 copies of the module and specifying different values for the module
4233 IP to AppleTalk-IP Encapsulation support
4235 If you say Y here, the AppleTalk-IP code will be able to encapsulate
4236 IP packets inside AppleTalk frames; this is useful if your Linux box
4237 is stuck on an AppleTalk network (which hopefully contains a
4238 decapsulator somewhere). Please see
4239 Documentation/networking/ipddp.txt for more information. If you said
4240 Y to "AppleTalk-IP driver support" above and you say Y here, then
4241 you cannot say Y to "AppleTalk-IP to IP Decapsulation support",
4244 AppleTalk-IP to IP Decapsulation support
4246 If you say Y here, the AppleTalk-IP code will be able to decapsulate
4247 AppleTalk-IP frames to IP packets; this is useful if you want your
4248 Linux box to act as an Internet gateway for an AppleTalk network.
4249 Please see Documentation/networking/ipddp.txt for more information.
4250 If you said Y to "AppleTalk-IP driver support" above and you say Y
4251 here, then you cannot say Y to "IP to AppleTalk-IP Encapsulation
4254 Apple/Farallon LocalTalk PC card support
4256 This allows you to use the AppleTalk PC card to connect to LocalTalk
4257 networks. The card is also known as the Farallon PhoneNet PC card.
4258 If you are in doubt, this card is the one with the 65C02 chip on it.
4259 You also need version 1.3.3 or later of the netatalk package.
4260 This driver is experimental, which means that it may not work.
4261 See the file Documentation/networking/ltpc.txt.
4263 COPS LocalTalk PC card support
4265 This allows you to use COPS AppleTalk cards to connect to LocalTalk
4266 networks. You also need version 1.3.3 or later of the netatalk
4267 package. This driver is experimental, which means that it may not
4268 work. This driver will only work if you choose "AppleTalk DDP"
4269 networking support, above.
4270 Please read the file Documentation/networking/cops.txt.
4272 Dayna firmware support
4274 Support COPS compatible cards with Dayna style firmware (Dayna
4275 DL2000/ Daynatalk/PC (half length), COPS LT-95, Farallon PhoneNET PC
4276 III, Farallon PhoneNET PC II).
4278 Tangent firmware support
4280 Support COPS compatible cards with Tangent style firmware (Tangent
4281 ATB_II, Novell NL-1000, Daystar Digital LT-200.
4283 Amateur Radio support
4285 If you want to connect your Linux box to an amateur radio, answer Y
4286 here. You want to read http://www.tapr.org/tapr/html/pkthome.html
4287 and the HAM-HOWTO and the AX25-HOWTO, both available from
4288 http://www.linuxdoc.org/docs.html#howto .
4290 Note that the answer to this question won't directly affect the
4291 kernel: saying N will just cause this configure script to skip all
4292 the questions about amateur radio.
4294 Amateur Radio AX.25 Level 2
4296 This is the protocol used for computer communication over amateur
4297 radio. It is either used by itself for point-to-point links, or to
4298 carry other protocols such as tcp/ip. To use it, you need a device
4299 that connects your Linux box to your amateur radio. You can either
4300 use a low speed TNC (a Terminal Node Controller acts as a kind of
4301 modem connecting your computer's serial port to your radio's
4302 microphone input and speaker output) supporting the KISS protocol or
4303 one of the various SCC cards that are supported by the generic Z8530
4304 or the DMA SCC driver. Another option are the Baycom modem serial
4305 and parallel port hacks or the sound card modem (supported by their
4306 own drivers). If you say Y here, you also have to say Y to one of
4309 Information about where to get supporting software for Linux amateur
4310 radio as well as information about how to configure an AX.25 port is
4311 contained in the AX25-HOWTO, available from
4312 http://www.linuxdoc.org/docs.html#howto . You might also want to
4313 check out the file Documentation/networking/ax25.txt in the kernel
4314 source. More information about digital amateur radio in general is
4315 on the WWW at http://www.tapr.org/tapr/html/pkthome.html .
4317 This driver is also available as a module ( = code which can be
4318 inserted in and removed from the running kernel whenever you want).
4319 The module will be called ax25.o. If you want to compile it as a
4320 module, say M here and read Documentation/modules.txt.
4322 AX.25 DAMA Slave support
4323 CONFIG_AX25_DAMA_SLAVE
4324 DAMA is a mechanism to prevent collisions when doing AX.25
4325 networking. A DAMA server (called "master") accepts incoming traffic
4326 from clients (called "slaves") and redistributes it to other slaves.
4327 If you say Y here, your Linux box will act as a DAMA slave; this is
4328 transparent in that you don't have to do any special DAMA
4329 configuration. (Linux cannot yet act as a DAMA server.) If unsure,
4332 AX.25 DAMA Master support
4333 CONFIG_AX25_DAMA_MASTER
4334 DAMA is a mechanism to prevent collisions when doing AX.25
4335 networking. A DAMA server (called "master") accepts incoming traffic
4336 from clients (called "slaves") and redistributes it to other
4337 slaves. If you say Y here, your Linux box will act as a DAMA server.
4340 Amateur Radio NET/ROM
4342 NET/ROM is a network layer protocol on top of AX.25 useful for
4345 A comprehensive listing of all the software for Linux amateur radio
4346 users as well as information about how to configure an AX.25 port is
4347 contained in the AX25-HOWTO, available from
4348 http://www.linuxdoc.org/docs.html#howto . You also might want to
4349 check out the file Documentation/networking/ax25.txt. More
4350 information about digital amateur radio in general is on the WWW at
4351 http://www.tapr.org/tapr/html/pkthome.html .
4353 This driver is also available as a module ( = code which can be
4354 inserted in and removed from the running kernel whenever you want).
4355 The module will be called netrom.o. If you want to compile it as a
4356 module, say M here and read Documentation/modules.txt.
4358 Amateur Radio X.25 PLP (Rose)
4360 The Packet Layer Protocol (PLP) is a way to route packets over X.25
4361 connections in general and amateur radio AX.25 connections in
4362 particular, essentially an alternative to NET/ROM.
4364 A comprehensive listing of all the software for Linux amateur radio
4365 users as well as information about how to configure an AX.25 port is
4366 contained in the AX25-HOWTO, available from
4367 http://www.linuxdoc.org/docs.html#howto . You also might want to
4368 check out the file Documentation/networking/ax25.txt. More
4369 information about digital amateur radio in general is on the WWW at
4370 http://www.tapr.org/tapr/html/pkthome.html .
4372 This driver is also available as a module ( = code which can be
4373 inserted in and removed from the running kernel whenever you want).
4374 The module will be called rose.o. If you want to compile it as a
4375 module, say M here and read Documentation/modules.txt.
4377 Serial port KISS driver for AX.25
4379 KISS is a protocol used for the exchange of data between a computer
4380 and a Terminal Node Controller (a small embedded system commonly
4381 used for networking over AX.25 amateur radio connections; it
4382 connects the computer's serial port with the radio's microphone
4383 input and speaker output).
4385 Although KISS is less advanced than the 6pack protocol, it has
4386 the advantage that it is already supported by most modern TNCs
4387 without the need for a firmware upgrade.
4389 If you want to compile this driver as a module ( = code which can be
4390 inserted in and removed from the running kernel whenever you want),
4391 say M here and read Documentation/modules.txt. The module will be
4394 Serial port 6PACK driver for AX.25
4396 6pack is a transmission protocol for the data exchange between your
4397 PC and your TNC (the Terminal Node Controller acts as a kind of
4398 modem connecting your computer's serial port to your radio's
4399 microphone input and speaker output). This protocol can be used as
4400 an alternative to KISS for networking over AX.25 amateur radio
4401 connections, but it has some extended functionality.
4403 Note that this driver is still experimental and might cause
4404 problems. For details about the features and the usage of the
4405 driver, read Documentation/networking/6pack.txt.
4407 If you want to compile this driver as a module ( = code which can be
4408 inserted in and removed from the running kernel whenever you want),
4409 say M here and read Documentation/modules.txt. The module will be
4414 AX.25 is the protocol used for computer communication over amateur
4415 radio. If you say Y here, you will be able to send and receive AX.25
4416 traffic over Ethernet (also called "BPQ AX.25"), which could be
4417 useful if some other computer on your local network has a direct
4418 amateur radio connection.
4420 High-speed (DMA) SCC driver for AX.25
4422 This is a driver for high-speed SCC boards, i.e. those supporting
4423 DMA on one port. You usually use those boards to connect your
4424 computer to an amateur radio modem (such as the WA4DSY 56kbps
4425 modem), in order to send and receive AX.25 packet radio network
4428 Currently, this driver supports Ottawa PI/PI2, Paccomm/Gracilis
4429 PackeTwin, and S5SCC/DMA boards. They are detected automatically.
4430 If you have one of these cards, say Y here and read the AX25-HOWTO,
4431 available from http://www.linuxdoc.org/docs.html#howto .
4433 This driver can operate multiple boards simultaneously. If you
4434 compile it as a module (by saying M instead of Y), it will be called
4435 dmascc.o. If you don't pass any parameter to the driver, all
4436 possible I/O addresses are probed. This could irritate other devices
4437 that are currently not in use. You may specify the list of addresses
4438 to be probed by "dmascc=addr1,addr2,..." (when compiled into the
4439 kernel image) or "io=addr1,addr2,..." (when loaded as a module). The
4440 network interfaces will be called dmascc0 and dmascc1 for the board
4441 detected first, dmascc2 and dmascc3 for the second one, and so on.
4443 Before you configure each interface with ifconfig, you MUST set
4444 certain parameters, such as channel access timing, clock mode, and
4445 DMA channel. This is accomplished with a small utility program,
4446 dmascc_cfg, available at
4447 http://www.nt.tuwien.ac.at/~kkudielk/Linux/ . Please be sure to get
4448 at least version 1.27 of dmascc_cfg, as older versions will not
4449 work with the current driver.
4451 Z8530 SCC driver for AX.25
4453 These cards are used to connect your Linux box to an amateur radio
4454 in order to communicate with other computers. If you want to use
4455 this, read Documentation/networking/z8530drv.txt and the AX25-HOWTO,
4456 available from http://www.linuxdoc.org/docs.html#howto . Also
4457 make sure to say Y to "Amateur Radio AX.25 Level 2" support.
4459 If you want to compile this as a module ( = code which can be
4460 inserted in and removed from the running kernel whenever you want),
4461 say M here and read Documentation/modules.txt. The module will be
4464 additional delay for PA0HZP OptoSCC compatible boards
4466 Say Y here if you experience problems with the SCC driver not
4467 working properly; please read Documentation/networking/z8530drv.txt
4468 for details. If unsure, say N.
4470 #support for TRX that feedback the tx signal to rx
4473 ### Don't know what's going on here.
4477 YAM driver for AX.25
4479 The YAM is a modem for packet radio which connects to the serial
4480 port and includes some of the functions of a Terminal Node
4481 Controller. If you have one of those, say Y here.
4483 If you want to compile this as a module ( = code which can be
4484 inserted in and removed from the running kernel whenever you want),
4485 say M here and read Documentation/modules.txt.
4487 BAYCOM picpar and par96 driver for AX.25
4489 This is a driver for Baycom style simple amateur radio modems that
4490 connect to a parallel interface. The driver supports the picpar and
4491 par96 designs. To configure the driver, use the sethdlc utility
4492 available in the standard ax25 utilities package. For information on
4493 the modems, see http://www.baycom.de and the file
4494 Documentation/networking/baycom.txt.
4496 If you want to compile this driver as a module ( = code which can be
4497 inserted in and removed from the running kernel whenever you want),
4498 say M here and read Documentation/modules.txt. This is recommended.
4499 The module will be called baycom_par.o.
4501 BAYCOM EPP driver for AX.25
4503 This is a driver for Baycom style simple amateur radio modems that
4504 connect to a parallel interface. The driver supports the EPP
4505 designs. To configure the driver, use the sethdlc utility available
4506 in the standard ax25 utilities package. For information on the
4507 modems, see http://www.baycom.de and the file
4508 Documentation/networking/baycom.txt.
4510 If you want to compile this driver as a module ( = code which can be
4511 inserted in and removed from the running kernel whenever you want),
4512 say M here and read Documentation/modules.txt. This is recommended.
4513 The module will be called baycom_par.o.
4515 BAYCOM ser12 full duplex driver for AX.25
4516 CONFIG_BAYCOM_SER_FDX
4517 This is one of two drivers for Baycom style simple amateur radio
4518 modems that connect to a serial interface. The driver supports the
4519 ser12 design in full duplex mode. In addition, it allows the
4520 baudrate to be set between 300 and 4800 baud (however not all modems
4521 support all baudrates). This is the preferred driver. The next
4522 driver, "BAYCOM ser12 half duplex driver for AX.25" is the old
4523 driver and still provided in case this driver does not work with
4524 your serial interface chip. To configure the driver, use the sethdlc
4525 utility available in the standard ax25 utilities package. For
4526 information on the modems, see http://www.baycom.de and
4527 Documentation/networking/baycom.txt.
4529 If you want to compile this driver as a module ( = code which can be
4530 inserted in and removed from the running kernel whenever you want),
4531 say M here and read Documentation/modules.txt. This is recommended.
4532 The module will be called baycom_ser_fdx.o.
4534 BAYCOM ser12 half duplex driver for AX.25
4535 CONFIG_BAYCOM_SER_HDX
4536 This is one of two drivers for Baycom style simple amateur radio
4537 modems that connect to a serial interface. The driver supports the
4538 ser12 design in full duplex mode. This is the old driver. It is
4539 still provided in case your serial interface chip does not work with
4540 the full duplex driver. This driver is depreciated. To configure the
4541 driver, use the sethdlc utility available in the standard ax25
4542 utilities package. For information on the modems, see
4543 http://www.baycom.de and Documentation/networking/baycom.txt.
4545 If you want to compile this driver as a module ( = code which can be
4546 inserted in and removed from the running kernel whenever you want),
4547 say M here and read Documentation/modules.txt. This is recommended.
4548 The module will be called baycom_ser_hdx.o.
4550 Sound card modem driver for AX.25
4552 This experimental driver allows a standard Sound Blaster or
4553 WindowsSoundSystem compatible sound card to be used as a packet
4554 radio modem (NOT as a telephone modem!), to send digital traffic
4557 To configure the driver, use the sethdlc, smdiag and smmixer
4558 utilities available in the standard ax25 utilities package. For
4559 information on how to key the transmitter, see
4560 http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html and
4561 Documentation/networking/soundmodem.txt.
4563 If you want to compile this driver as a module ( = code which can be
4564 inserted in and removed from the running kernel whenever you want),
4565 say M here and read Documentation/modules.txt. This is recommended.
4566 The module will be called soundmodem.o.
4568 Sound card modem support for Sound Blaster and compatible cards
4569 CONFIG_SOUNDMODEM_SBC
4570 This option enables the soundmodem driver to use Sound Blaster and
4571 compatible cards. If you have a dual mode card (i.e. a WSS cards
4572 with a Sound Blaster emulation) you should say N here and Y to
4573 "Sound card modem support for WSS and Crystal cards", below, because
4574 this usually results in better performance. This option also
4575 supports SB16/32/64 in full duplex mode.
4577 Sound card modem support for WSS and Crystal cards
4578 CONFIG_SOUNDMODEM_WSS
4579 This option enables the soundmodem driver to use WindowsSoundSystem
4580 compatible cards. These cards feature a codec chip from either
4581 Analog Devices (such as AD1848, AD1845, AD1812) or Crystal
4582 Semiconductors (such as CS4248, CS423x). This option also supports
4583 the WSS full duplex operation which currently works with Crystal
4584 CS423x chips. If you don't need full duplex operation, do not enable
4585 it to save performance.
4587 Sound card modem support for 1200 baud AFSK modulation
4588 CONFIG_SOUNDMODEM_AFSK1200
4589 This option enables the soundmodem driver 1200 baud AFSK modem,
4590 compatible to popular modems using TCM3105 or AM7911. The
4591 demodulator requires about 12% of the CPU power of a Pentium 75 CPU
4594 Sound card modem support for 2400 baud AFSK modulation (7.3728MHz crystal)
4595 CONFIG_SOUNDMODEM_AFSK2400_7
4596 This option enables the soundmodem driver 2400 baud AFSK modem,
4597 compatible to TCM3105 modems (over-)clocked with a 7.3728MHz
4598 crystal. Note that the availability of this driver does _not_ imply
4599 that I recommend building such links. It is only here since users
4600 especially in eastern Europe have asked me to do so. In fact this
4601 modulation scheme has many disadvantages, mainly its incompatibility
4602 with many transceiver designs and the fact that the TCM3105 (if
4603 used) is operated widely outside its specifications.
4605 Sound card modem support for 2400 baud AFSK modulation (8MHz crystal)
4606 CONFIG_SOUNDMODEM_AFSK2400_8
4607 This option enables the soundmodem driver 2400 baud AFSK modem,
4608 compatible to TCM3105 modems (over-)clocked with an 8MHz crystal.
4609 Note that the availability of this driver does _not_ imply that I
4610 recommend building such links. It is only here since users
4611 especially in eastern Europe have asked me to do so. In fact this
4612 modulation scheme has many disadvantages, mainly its incompatibility
4613 with many transceiver designs and the fact that the TCM3105 (if
4614 used) is operated widely outside its specifications.
4616 Sound card modem support for 2666 baud AFSK modulation
4617 CONFIG_SOUNDMODEM_AFSK2666
4618 This option enables the soundmodem driver 2666 baud AFSK modem.
4619 This modem is experimental, and not compatible to anything
4622 Sound card modem support for 4800 baud 8PSK modulation
4623 CONFIG_SOUNDMODEM_PSK4800
4624 This option enables the soundmodem driver 4800 baud 8PSK modem.
4625 This modem is experimental, and not compatible to anything
4628 Sound card modem support for 4800 baud HAPN-1 modulation
4629 CONFIG_SOUNDMODEM_HAPN4800
4630 This option enables the soundmodem driver 4800 baud HAPN-1
4631 compatible modem. This modulation seems to be widely used 'down
4632 under' and in the Netherlands. Here, nobody uses it, so I could not
4633 test if it works. It is compatible to itself, however :-)
4635 Sound card modem support for 9600 baud FSK G3RUH modulation
4636 CONFIG_SOUNDMODEM_FSK9600
4637 This option enables the soundmodem driver 9600 baud FSK modem,
4638 compatible to the G3RUH standard. The demodulator requires about 4%
4639 of the CPU power of a Pentium 75 CPU per channel. You can say Y to
4640 both 1200 baud AFSK and 9600 baud FSK if you want (but obviously you
4641 can only use one protocol at a time, depending on what the other end
4644 CCITT X.25 Packet Layer (EXPERIMENTAL)
4646 X.25 is a set of standardized network protocols, similar in scope to
4647 frame relay; the one physical line from your box to the X.25 network
4648 entry point can carry several logical point-to-point connections
4649 (called "virtual circuits") to other computers connected to the X.25
4650 network. Governments, banks, and other organizations tend to use it
4651 to connect to each other or to form Wide Area Networks (WANs). Many
4652 countries have public X.25 networks. X.25 consists of two
4653 protocols: the higher level Packet Layer Protocol (PLP) (say Y here
4654 if you want that) and the lower level data link layer protocol LAPB
4655 (say Y to "LAPB Data Link Driver" below if you want that).
4657 You can read more about X.25 at http://www.sangoma.com/x25.htm and
4658 http://www.cisco.com/univercd/data/doc/software/11_0/rpcg/cx25.htm .
4659 Information about X.25 for Linux is contained in the files
4660 Documentation/networking/x25.txt and
4661 Documentation/networking/x25-iface.txt.
4663 One connects to an X.25 network either with a dedicated network card
4664 using the X.21 protocol (not yet supported by Linux) or one can do
4665 X.25 over a standard telephone line using an ordinary modem (say Y
4666 to "X.25 async driver" below) or over Ethernet using an ordinary
4667 Ethernet card and either the 802.2 LLC protocol (say Y to "802.2
4668 LLC" below) or LAPB over Ethernet (say Y to "LAPB Data Link Driver"
4669 and "LAPB over Ethernet driver" below).
4671 If you want to compile this driver as a module ( = code which can be
4672 inserted in and removed from the running kernel whenever you want),
4673 say M here and read Documentation/modules.txt. The module will be
4674 called x25.o. If unsure, say N.
4676 LAPB Data Link Driver (EXPERIMENTAL)
4678 Link Access Procedure, Balanced (LAPB) is the data link layer (i.e.
4679 the lower) part of the X.25 protocol. It offers a reliable
4680 connection service to exchange data frames with one other host, and
4681 it is used to transport higher level protocols (mostly X.25 Packet
4682 Layer, the higher part of X.25, but others are possible as well).
4683 Usually, LAPB is used with specialized X.21 network cards, but Linux
4684 currently supports LAPB only over Ethernet connections. If you want
4685 to use LAPB connections over Ethernet, say Y here and to "LAPB over
4686 Ethernet driver" below. Read
4687 Documentation/networking/lapb-module.txt for technical details.
4689 If you want to compile this driver as a module though ( = code which
4690 can be inserted in and removed from the running kernel whenever you
4691 want), say M here and read Documentation/modules.txt. The module
4692 will be called lapb.o. If unsure, say N.
4694 802.2 LLC (EXPERIMENTAL)
4696 This is a Logical Link Layer protocol used for X.25 connections over
4697 Ethernet, using ordinary Ethernet cards.
4700 Frame Diverter (EXPERIMENTAL)
4702 The Frame Diverter allows you to divert packets from the
4703 network, that are not aimed at the interface receiving it (in
4704 promisc. mode). Typically, a Linux box setup as an ethernet bridge
4705 with the Frames Diverter on, can do some *really* transparent www
4706 caching using a Squid proxy for example.
4708 This is very usefull when you don't want to change your router's
4709 config (or if you simply don't have access to it).
4711 The other possible usages of diverting Ethernet Frames are numberous:
4712 - reroute smtp traffic to another interface
4713 - traffic-shape certain network streams
4714 - transparently proxy smtp connections
4717 For more informations, please refer to:
4718 http://www.freshmeat.net/projects/etherdivert
4719 http://perso.wanadoo.fr/magpie/EtherDivert.html
4723 802.1d Ethernet Bridging
4725 If you say Y here, then your Linux box will be able to act as an
4726 Ethernet bridge, which means that the different Ethernet segments it
4727 is connected to will appear as one Ethernet to the participants.
4728 Several such bridges can work together to create even larger
4729 networks of Ethernets using the IEEE 802.1 spanning tree algorithm.
4730 As this is a standard, Linux bridges will cooperate properly with
4731 other third party bridge products.
4733 In order to use the ethernet bridge, you'll need the bridge
4734 configuration tools; see Documentation/networking/bridge.txt for
4735 location. Please read the Bridge mini-HOWTO for more information.
4737 Note that if your box acts as a bridge, it probably contains several
4738 Ethernet devices, but the kernel is not able to recognize more than
4739 one at boot time without help; for details read the Ethernet-HOWTO,
4740 available from in http://www.linuxdoc.org/docs.html#howto .
4742 If you want to compile this code as a module ( = code which can be
4743 inserted in and removed from the running kernel whenever you want),
4744 say M here and read Documentation/modules.txt. The module will be
4751 The Packet protocol is used by applications which communicate
4752 directly with network devices without an intermediate network
4753 protocol implemented in the kernel, e.g. tcpdump. If you want them
4756 This driver is also available as a module called af_packet.o ( =
4757 code which can be inserted in and removed from the running kernel
4758 whenever you want). If you want to compile it as a module, say M
4759 here and read Documentation/modules.txt; if you use modprobe or
4760 kmod, you may also want to add "alias net-pf-17 af_packet" to
4765 Packet socket: mmapped IO
4767 If you say Y here, the Packet protocol driver will use an IO
4768 mechanism that results in faster communication.
4772 Kernel/User network link driver
4774 This driver allows for two-way communication between the kernel and
4775 user processes. It does so by creating a new socket family, PF_NETLINK.
4776 Over this socket, the kernel can send and receive datagrams carrying
4777 information. It is documented on many systems in netlink(7), a HOWTO is
4778 provided as well, for example on
4779 http://snafu.freedom.org/linux2.2/docs/netlink-HOWTO.html
4781 So far, the kernel uses this feature to publish some network related
4782 information if you say Y to "Routing messages", below. You also need
4783 to say Y here if you want to use arpd, a daemon that helps keep the
4784 internal ARP cache (a mapping between IP addresses and hardware
4785 addresses on the local network) small. The ethertap device, which
4786 lets user space programs read and write raw Ethernet frames, also
4787 needs the network link driver.
4793 If you say Y here, userspace programs can receive some network
4794 related routing information over the netlink. 'rtmon', supplied
4795 with the iproute2 package (ftp://ftp.inr.ac.ru), can read and
4796 interpret this data. Information sent to the kernel over this link
4799 Netlink device emulation
4801 This option will be removed soon. Any programs that want to use
4802 character special nodes like /dev/tap0 or /dev/route (all with major
4803 number 36) need this option, and need to be rewritten soon to use
4804 the real netlink socket.
4805 This is a backward compatibility option, choose Y for now.
4807 Asynchronous Transfer Mode (ATM)
4809 ATM is a high-speed networking technology for Local Area Networks
4810 and Wide Area Networks. It uses a fixed packet size and is
4811 connection oriented, allowing for the negotiation of minimum
4812 bandwidth requirements.
4814 In order to participate in an ATM network, your Linux box needs an
4815 ATM networking card. If you have that, say Y here and to the driver
4816 of your ATM card below.
4818 Note that you need a set of user-space programs to actually make use
4819 of ATM. See the file Documentation/networking/atm.txt for further
4822 Classical IP over ATM
4824 Classical IP over ATM for PVCs and SVCs, supporting InARP and
4825 ATMARP. If you want to communication with other IP hosts on your ATM
4826 network, you will typically either say Y here or to "LAN Emulation
4829 Do NOT send ICMP if no neighbour
4830 CONFIG_ATM_CLIP_NO_ICMP
4831 Normally, an "ICMP host unreachable" message is sent if a neighbour
4832 cannot be reached because there is no VC to it in the kernel's
4833 ATMARP table. This may cause problems when ATMARP table entries are
4834 briefly removed during revalidation. If you say Y here, packets to
4835 such neighbours are silently discarded instead.
4837 LAN Emulation (LANE) support
4839 LAN Emulation emulates services of existing LANs across an ATM
4840 network. Besides operating as a normal ATM end station client, Linux
4841 LANE client can also act as an proxy client bridging packets between
4842 ELAN and Ethernet segments. You need LANE if you want to try MPOA.
4844 Multi-Protocol Over ATM (MPOA) support
4846 Multi-Protocol Over ATM allows ATM edge devices such as routers,
4847 bridges and ATM attached hosts establish direct ATM VCs across
4848 subnetwork boundaries. These shortcut connections bypass routers
4849 enhancing overall network performance.
4853 ATM over TCP driver. Useful mainly for development and for
4854 experiments. If unsure, say N.
4856 Efficient Networks ENI155P
4858 Driver for the Efficient Networks ENI155p series and SMC ATM
4859 Power155 155 Mbps ATM adapters. Both, the versions with 512KB and
4860 2MB on-board RAM (Efficient calls them "C" and "S", respectively),
4861 and the FPGA and the ASIC Tonga versions of the board are supported.
4862 The driver works with MMF (-MF or ...F) and UTP-5 (-U5 or ...D)
4865 This driver is also available as a module. If you want to compile
4866 it as a module, say M here and read Documentation/modules.txt. The
4867 module will be called eni.o.
4869 Enable extended debugging
4870 CONFIG_ATM_ENI_DEBUG
4871 Extended debugging records various events and displays that list
4872 when an inconsistency is detected. This mechanism is faster than
4873 generally using printks, but still has some impact on performance.
4874 Note that extended debugging may create certain race conditions
4875 itself. Enable this ONLY if you suspect problems with the driver.
4877 Fine-tune burst settings
4878 CONFIG_ATM_ENI_TUNE_BURST
4879 In order to obtain good throughput, the ENI NIC can transfer
4880 multiple words of data per PCI bus access cycle. Such a multi-word
4881 transfer is called a burst.
4883 The default settings for the burst sizes are suitable for most PCI
4884 chipsets. However, in some cases, large bursts may overrun buffers
4885 in the PCI chipset and cause data corruption. In such cases, large
4886 bursts must be disabled and only (slower) small bursts can be used.
4887 The burst sizes can be set independently in the send (TX) and
4888 receive (RX) direction.
4890 Note that enabling many different burst sizes in the same direction
4891 may increase the cost of setting up a transfer such that the
4892 resulting throughput is lower than when using only the largest
4893 available burst size.
4895 Also, sometimes larger bursts lead to lower throughput, e.g. on an
4896 Intel 440FX board, a drop from 135 Mbps to 103 Mbps was observed
4897 when going from 8W to 16W bursts.
4899 Enable 16W TX bursts (discouraged)
4900 CONFIG_ATM_ENI_BURST_TX_16W
4901 Burst sixteen words at once in the send direction. This may work
4902 with recent PCI chipsets, but is known to fail with older chipsets.
4904 Enable 8W TX bursts (recommended)
4905 CONFIG_ATM_ENI_BURST_TX_8W
4906 Burst eight words at once in the send direction. This is the default
4909 Enable 4W TX bursts (optional)
4910 CONFIG_ATM_ENI_BURST_TX_4W
4911 Burst four words at once in the send direction. You may want to try
4912 this if you have disabled 8W bursts. Enabling 4W if 8W is also set
4913 may or may not improve throughput.
4915 Enable 2W TX bursts (optional)
4916 CONFIG_ATM_ENI_BURST_TX_2W
4917 Burst two words at once in the send direction. You may want to try
4918 this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or 8W
4919 are also set may or may not improve throughput.
4921 Enable 16W RX bursts (discouraged)
4922 CONFIG_ATM_ENI_BURST_RX_16W
4923 Burst sixteen words at once in the receive direction. This may work
4924 with recent PCI chipsets, but is known to fail with older chipsets.
4926 Enable 8W RX bursts (discouraged)
4927 CONFIG_ATM_ENI_BURST_RX_8W
4928 Burst eight words at once in the receive direction. This may work
4929 with recent PCI chipsets, but is known to fail with older chipsets,
4930 such as the Intel Neptune series.
4932 Enable 4W RX bursts (recommended)
4933 CONFIG_ATM_ENI_BURST_RX_4W
4934 Burst four words at once in the receive direction. This is the
4935 default setting. Enabling 4W if 8W is also set may or may not
4938 Enable 2W RX bursts (optional)
4939 CONFIG_ATM_ENI_BURST_RX_2W
4940 Burst two words at once in the receive direction. You may want to
4941 try this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or
4942 8W are also set may or may not improve throughput.
4944 ZeitNet ZN1221/ZN1225
4946 Driver for the ZeitNet ZN1221 (MMF) and ZN1225 (UTP-5) 155 Mbps ATM
4949 This driver is also available as a module. If you want to compile
4950 it as a module, say M here and read Documentation/modules.txt. The
4951 module will be called zatm.o.
4953 Enable extended debugging
4954 CONFIG_ATM_ZATM_DEBUG
4955 Extended debugging records various events and displays that list
4956 when an inconsistency is detected. This mechanism is faster than
4957 generally using printks, but still has some impact on performance.
4958 Note that extended debugging may create certain race conditions
4959 itself. Enable this ONLY if you suspect problems with the driver.
4961 Enable usec resolution timestamps
4962 CONFIG_ATM_ZATM_EXACT_TS
4963 The uPD98401 SAR chip supports a high-resolution timer (approx. 30
4964 MHz) that is used for very accurate reception timestamps. Because
4965 that timer overflows after 140 seconds, and also to avoid timer
4966 drift, time measurements need to be periodically synchronized with
4967 the normal system time. Enabling this feature will add some general
4968 overhead for timer synchronization and also per-packet overhead for
4971 IDT 77201/11 (NICStAR) (ForeRunnerLE)
4973 The NICStAR chipset family is used in a large number of ATM NICs for
4974 25 and for 155 Mbps, including IDT cards and the Fore ForeRunnerLE
4975 series. Say Y if you have one of those.
4977 This driver is also available as a module. If you want to compile
4978 it as a module, say M here and read Documentation/modules.txt. The
4979 module will be called nicstar.o.
4981 ForeRunner LE155 PHYsical layer
4982 CONFIG_ATM_NICSTAR_USE_SUNI
4983 Support for the S-UNI and compatible PHYsical layer chips. These are
4984 found in most 155Mbps NICStAR based ATM cards, namely in the
4985 ForeRunner LE155 cards. This driver provides detection of cable
4986 removal and reinsertion and provides some statistics. This driver
4987 doesn't have removal capability when compiled as a module, so if you
4988 need that capability don't include S-UNI support (it's not needed to
4989 make the card work).
4991 ForeRunner LE25 PHYsical layer
4992 CONFIG_ATM_NICSTAR_USE_IDT77105
4993 Support for the PHYsical layer chip in ForeRunner LE25 cards. In
4994 addition to cable removal/reinsertion detection, this driver allows
4995 you to control the loopback mode of the chip via a dedicated IOCTL.
4996 This driver is required for proper handling of temporary carrier
4997 loss, so if you have a 25Mbps NICStAR based ATM card you must say Y.
4999 Madge Ambassador (Collage PCI 155 Server)
5000 CONFIG_ATM_AMBASSADOR
5001 This is a driver for ATMizer based ATM card produced by Madge
5002 Networks Ltd. Say Y (or M to compile as a module named ambassador.o)
5003 here if you have one of these cards.
5005 Enable debugging messages
5006 CONFIG_ATM_AMBASSADOR_DEBUG
5007 Somewhat useful debugging messages are available. The choice of
5008 messages is controlled by a bitmap. This may be specified as a
5009 module argument (kernel command line argument as well?), changed
5010 dynamically using an ioctl (not yet) or changed by sending the
5011 string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
5012 drivers/atm/ambassador.h for the meanings of the bits in the mask.
5014 When active, these messages can have a significant impact on the
5015 speed of the driver, and the size of your syslog files! When
5016 inactive, they will have only a modest impact on performance.
5018 Madge Horizon [Ultra] (Collage PCI 25 and Collage PCI 155 Client)
5020 This is a driver for the Horizon chipset ATM adapter cards once
5021 produced by Madge Networks Ltd. Say Y (or M to compile as a module
5022 named horizon.o) here if you have one of these cards.
5024 Enable debugging messages
5025 CONFIG_ATM_HORIZON_DEBUG
5026 Somewhat useful debugging messages are available. The choice of
5027 messages is controlled by a bitmap. This may be specified as a
5028 module argument (kernel command line argument as well?), changed
5029 dynamically using an ioctl (not yet) or changed by sending the
5030 string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
5031 drivers/atm/horizon.h for the meanings of the bits in the mask.
5033 When active, these messages can have a significant impact on the
5034 speed of the driver, and the size of your syslog files! When
5035 inactive, they will have only a modest impact on performance.
5037 Interphase ATM PCI x575/x525/x531
5039 This is a driver for the Interphase (i)ChipSAR adapter cards
5040 which include a variety of variants in term of the size of the
5041 control memory (128K-1KVC, 512K-4KVC), the size of the packet
5042 memory (128K, 512K, 1M), and the PHY type (Single/Multi mode OC3,
5043 UTP155, UTP25, DS3 and E3). Go to:
5044 www.iphase.com/products/ClassSheet.cfm?ClassID=ATM
5045 for more info about the cards. Say Y (or M to compile as a module
5046 named iphase.o) here if you have one of these cards.
5048 See the file Documentation/networking/iphase.txt for further
5051 Enable debugging messages
5053 Somewhat useful debugging messages are available. The choice of
5054 messages is controlled by a bitmap. This may be specified as a
5055 module argument (kernel command line argument as well?), changed
5056 dynamically using an ioctl (Get the debug utility, iadbg, from
5057 ftp.iphase.com/pub/atm/pci). See the file drivers/atm/iphase.h
5058 for the meanings of the bits in the mask.
5060 When active, these messages can have a significant impact on the
5061 speed of the driver, and the size of your syslog files! When
5062 inactive, they will have only a modest impact on performance.
5064 Linux telephony support
5066 Say Y here if you have a telephony card, which for example allows
5067 you to use a regular phone for voice-over-IP applications.
5069 Note: this has nothing to do with modems. You do not need to say Y
5070 here in order to be able to use a modem under Linux.
5072 This support is also available as a module. If you want to compile
5073 it as a module, say M here and read Documentation/modules.txt. The
5074 module will be called phonedev.o.
5076 Compaq Smart Array support
5077 CONFIG_BLK_CPQ_CISS_DA
5078 This is the driver for Compaq Smart Array controllers.
5079 Everyone using these boards should say Y here.
5080 See Documentation/cciss.txt for the current list of
5081 boards supported by this driver, and for further information
5082 on the use of this driver.
5084 QuickNet Internet LineJack/PhoneJack support
5086 Say M if you have a telephony card manufactured by Quicknet
5087 Technologies, Inc. These include the Internet PhoneJACK and
5088 Internet LineJACK Telephony Cards. You will get a module called
5091 For the ISA versions of these products, you can configure the
5092 cards using the isapnp tools (pnpdump/isapnp) or you can use the
5093 isapnp support. Please read Documentation/telephony/ixj.txt.
5095 For more information on these cards, see Quicknet's web site at:
5096 http://www.quicknet.net/ .
5098 If you do not have any Quicknet telephony cards, you can safely
5101 FORE Systems 200E-series
5102 CONFIG_ATM_FORE200E_MAYBE
5103 This is a driver for the FORE Systems 200E-series ATM adapter
5104 cards. It simultaneously supports PCA-200E and SBA-200E models
5105 on PCI and SBUS hosts. Say Y (or M to compile as a module
5106 named fore_200e.o) here if you have one of these ATM adapters.
5108 Note that the driver will actually be compiled only if you
5109 additionally enable the support for PCA-200E and/or SBA-200E
5112 See the file Documentation/networking/fore200e.txt for further
5115 Enable PCA-200E card support on PCI-based hosts
5116 CONFIG_ATM_FORE200E_PCA
5117 Say Y here if you want your PCA-200E cards to be probed.
5119 Use default PCA-200E firmware
5120 CONFIG_ATM_FORE200E_PCA_DEFAULT_FW
5121 Use the default PCA-200E firmware data shipped with the driver.
5123 Normal users do not have to deal with the firmware stuff, so
5124 they should say Y here.
5126 Pathname of user-supplied binary firmware
5127 CONFIG_ATM_FORE200E_PCA_FW
5128 This defines the pathname of an alternative PCA-200E binary
5129 firmware image supplied by the user. This pathname may be
5130 absolute or relative to the drivers/atm directory.
5132 The driver comes with an adequate firmware image, so normal users do
5133 not have to supply an alternative one. They just say Y to "Use
5134 default PCA-200E firmware" instead.
5136 Enable SBA-200E card support on SBUS-based hosts
5137 CONFIG_ATM_FORE200E_SBA
5138 Say Y here if you want your SBA-200E cards to be probed.
5140 Use default SBA-200E firmware
5141 CONFIG_ATM_FORE200E_SBA_DEFAULT_FW
5142 Use the default SBA-200E firmware data shipped with the driver.
5144 Normal users do not have to deal with the firmware stuff, so
5145 they should say Y here.
5147 Pathname of user-supplied binary firmware
5148 CONFIG_ATM_FORE200E_SBA_FW
5149 This defines the pathname of an alternative SBA-200E binary
5150 firmware image supplied by the user. This pathname may be
5151 absolute or relative to the drivers/atm directory.
5153 The driver comes with an adequate firmware image, so normal users do
5154 not have to supply an alternative one. They just say Y to "Use
5155 default SBA-200E firmware", above.
5157 Maximum number of tx retries
5158 CONFIG_ATM_FORE200E_TX_RETRY
5159 Specifies the number of times the driver attempts to transmit
5160 a message before giving up, if the transmit queue of the ATM card
5161 is transiently saturated.
5163 Saturation of the transmit queue may occur only under extreme
5164 conditions, e.g. when a fast host continuously submits very small
5165 frames (<64 bytes) or raw AAL0 cells (48 bytes) to the ATM adapter.
5167 Note that under common conditions, it is unlikely that you encounter
5168 a saturation of the transmit queue, so the retry mechanism never
5171 Debugging level (0-3)
5172 CONFIG_ATM_FORE200E_DEBUG
5173 Specifies the level of debugging messages issued by the driver.
5174 The verbosity of the driver increases with the value of this
5177 When active, these messages can have a significant impact on
5178 the performances of the driver, and the size of your syslog files!
5179 Keep the debugging level to 0 during normal operations.
5183 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CDROM or
5184 any other SCSI device under Linux, say Y and make sure that you know
5185 the name of your SCSI host adapter (the card inside your computer
5186 that "speaks" the SCSI protocol, also called SCSI controller),
5187 because you will be asked for it.
5189 You also need to say Y here if you want support for the parallel
5190 port version of the 100 MB IOMEGA ZIP drive.
5192 Please read the SCSI-HOWTO, available from
5193 http://www.linuxdoc.org/docs.html#howto . The
5194 SCSI-Programming-HOWTO contains information about how to add or
5195 remove an SCSI device from a running Linux machine without
5198 This driver is also available as a module ( = code which can be
5199 inserted in and removed from the running kernel whenever you want).
5200 The module will be called scsi_mod.o. If you want to compile it as a
5201 module, say M here and read Documentation/modules.txt and
5202 Documentation/scsi.txt. However, do not compile this as a module if
5203 your root file system (the one containing the directory /) is
5204 located on a SCSI device.
5208 If you want to use a SCSI hard disk or the SCSI or parallel port
5209 version of the IOMEGA ZIP drive under Linux, say Y and read the
5210 SCSI-HOWTO, the Disk-HOWTO and the Multi-Disk-HOWTO, available from
5211 http://www.linuxdoc.org/docs.html#howto . This is NOT for SCSI
5214 This driver is also available as a module ( = code which can be
5215 inserted in and removed from the running kernel whenever you want).
5216 The module will be called sd_mod.o. If you want to compile it as a
5217 module, say M here and read Documentation/modules.txt and
5218 Documentation/scsi.txt. Do not compile this driver as a module if
5219 your root file system (the one containing the directory /) is
5220 located on a SCSI disk. In this case, do not compile the driver for
5221 your SCSI host adapter (below) as a module either.
5224 CONFIG_SD_EXTRA_DEVS
5225 This controls the amount of additional space allocated in tables for
5226 drivers that are loaded as modules after the kernel is booted. In
5227 the event that the SCSI core itself was loaded as a module, this
5228 value is the number of additional disks that can be loaded after the
5229 first host driver is loaded.
5231 Admittedly this isn't pretty, but there are tons of race conditions
5232 involved with resizing the internal arrays on the fly. Someday this
5233 flag will go away, and everything will work automatically.
5235 If you don't understand what's going on, go with the default.
5239 If you want to use a SCSI tape drive under Linux, say Y and read the
5240 SCSI-HOWTO, available from
5241 http://www.linuxdoc.org/docs.html#howto , and
5242 drivers/scsi/README.st in the kernel source. This is NOT for SCSI
5245 This driver is also available as a module ( = code which can be
5246 inserted in and removed from the running kernel whenever you want).
5247 The module will be called st.o. If you want to compile it as a
5248 module, say M here and read Documentation/modules.txt and
5249 Documentation/scsi.txt .
5253 If you want to use a SCSI CDROM under Linux, say Y and read the
5254 SCSI-HOWTO and the CDROM-HOWTO at
5255 http://www.linuxdoc.org/docs.html#howto . Also make sure to say Y
5256 or M to "ISO 9660 CDROM file system support" later.
5258 This driver is also available as a module ( = code which can be
5259 inserted in and removed from the running kernel whenever you want).
5260 The module will be called sr_mod.o. If you want to compile it as a
5261 module, say M here and read Documentation/modules.txt and
5262 Documentation/scsi.txt .
5265 CONFIG_SR_EXTRA_DEVS
5266 This controls the amount of additional space allocated in tables for
5267 drivers that are loaded as modules after the kernel is booted. In
5268 the event that the SCSI core itself was loaded as a module, this
5269 value is the number of additional CDROMs that can be loaded after
5270 the first host driver is loaded.
5272 Admittedly this isn't pretty, but there are tons of race conditions
5273 involved with resizing the internal arrays on the fly. Someday this
5274 flag will go away, and everything will work automatically.
5276 If you don't understand what's going on, go with the default.
5278 Enable vendor-specific extensions (for SCSI CDROM)
5279 CONFIG_BLK_DEV_SR_VENDOR
5280 This enables the usage of vendor specific SCSI commands. This is
5281 required to support multisession CDs with old NEC/TOSHIBA cdrom
5282 drives (and HP Writers). If you have such a drive and get the first
5283 session only, try saying Y here; everybody else says N.
5285 SCSI generic support
5287 If you want to use SCSI scanners, synthesizers or CD-writers or just
5288 about anything having "SCSI" in its name other than hard disks,
5289 CDROMs or tapes, say Y here. These won't be supported by the kernel
5290 directly, so you need some additional software which knows how to
5291 talk to these devices using the SCSI protocol:
5293 For scanners, look at SANE (http://www.mostang.com/sane). For CD
5294 writer software look at cdrecord
5295 (http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html)
5296 and for burning a "disk at once": cdrdao
5297 (http://www.ping.de/sites/daneb/cdrdao.html). Cdparanoia is a high
5298 quality digital reader of audio CDs (http://www.xiph.org/paranoia).
5299 For other devices, it's possible that you'll have to write the
5300 driver software yourself. Please read the file
5301 Documentation/scsi-generic.txt for more information.
5303 If you want to compile this as a module ( = code which can be
5304 inserted in and removed from the running kernel whenever you want),
5305 say M here and read Documentation/modules.txt and
5306 Documentation/scsi.txt. The module will be called sg.o. If unsure,
5309 Debug new queueing code for SCSI
5310 CONFIG_SCSI_DEBUG_QUEUES
5311 This option turns on a lot of additional consistency checking for
5312 the new queueing code. This will adversely affect performance, but
5313 it is likely that bugs will be caught sooner if this is turned on.
5314 This will typically cause the kernel to panic if an error is
5315 detected, but it would have probably crashed if the panic weren't
5316 there. Comments/questions/problems to linux-scsi mailing list
5317 please. See http://www.andante.org/scsi_queue.html for more
5318 up-to-date information.
5320 Probe all LUNs on each SCSI device
5321 CONFIG_SCSI_MULTI_LUN
5322 If you have a SCSI device that supports more than one LUN (Logical
5323 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
5324 can say Y here to force the SCSI driver to probe for multiple LUNs.
5325 A SCSI device with multiple LUNs acts logically like multiple SCSI
5326 devices. The vast majority of SCSI devices have only one LUN, and
5327 so most people can say N here and should in fact do so, because it
5330 Verbose SCSI error reporting (kernel size +=12K)
5331 CONFIG_SCSI_CONSTANTS
5332 The error messages regarding your SCSI hardware will be easier to
5333 understand if you say Y here; it will enlarge your kernel by about
5334 12 KB. If in doubt, say Y.
5336 SCSI logging facility
5338 This turns on a logging facility that can be used to debug a number
5339 of SCSI related problems.
5341 If you say Y here, no logging output will appear by default, but you
5342 can enable logging by saying Y to "/proc file system support" and
5343 "Sysctl support" below and executing the command
5345 echo "scsi log token [level]" > /proc/scsi/scsi
5347 at boot time after the /proc file system has been mounted.
5349 There are a number of things that can be used for 'token' (you can
5350 find them in the source: drivers/scsi/scsi.c), and this allows you
5351 to select the types of information you want, and the level allows
5352 you to select the level of verbosity.
5354 If you say N here, it may be harder to track down some types of SCSI
5355 problems. If you say Y here your kernel will be somewhat larger, but
5356 there should be no noticeable performance impact as long as you have
5359 AdvanSys SCSI support
5360 CONFIG_SCSI_ADVANSYS
5361 This is a driver for all SCSI host adapters manufactured by
5362 AdvanSys. It is documented in the kernel source in
5363 drivers/scsi/advansys.c.
5365 This driver is also available as a module ( = code which can be
5366 inserted in and removed from the running kernel whenever you want).
5367 If you want to compile it as a module, say M here and read
5368 Documentation/modules.txt. The module will be called advansys.o.
5370 Adaptec AHA152X/2825 support
5372 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
5373 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
5374 must be manually specified in this case.
5376 It is explained in section 3.3 of the SCSI-HOWTO, available from
5377 http://www.linuxdoc.org/docs.html#howto . You might also want to
5378 read the file drivers/scsi/README.aha152x.
5380 This driver is also available as a module ( = code which can be
5381 inserted in and removed from the running kernel whenever you want).
5382 The module will be called aha152x.o. If you want to compile it as a
5383 module, say M here and read Documentation/modules.txt.
5385 Adaptec AHA1542 support
5387 This is support for a SCSI host adapter. It is explained in section
5388 3.4 of the SCSI-HOWTO, available from
5389 http://www.linuxdoc.org/docs.html#howto . Note that Trantor was
5390 purchased by Adaptec, and some former Trantor products are being
5391 sold under the Adaptec name. If it doesn't work out of the box, you
5392 may have to change some settings in drivers/scsi/aha1542.h.
5394 If you want to compile this as a module ( = code which can be
5395 inserted in and removed from the running kernel whenever you want),
5396 say M here and read Documentation/modules.txt. The module will be
5399 Adaptec AHA1740 support
5401 This is support for a SCSI host adapter. It is explained in section
5402 3.5 of the SCSI-HOWTO, available from
5403 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
5404 of the box, you may have to change some settings in
5405 drivers/scsi/aha1740.h.
5407 This driver is also available as a module ( = code which can be
5408 inserted in and removed from the running kernel whenever you want).
5409 The module will be called aha1740.o. If you want to compile it as a
5410 module, say M here and read Documentation/modules.txt.
5412 Adaptec AIC7xxx chipset SCSI controller support
5414 This is support for the various aic7xxx based Adaptec SCSI
5415 controllers. These include the 274x EISA cards; 284x VLB cards;
5416 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
5417 motherboard based SCSI controllers from Adaptec. It does not support
5418 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
5419 support them. It does not support the 2920 cards from Adaptec that
5420 use the Future Domain SCSI controller chip. For those cards, you
5421 need the "Future Domain 16xx SCSI support" driver.
5423 In general, if the controller is based on an Adaptec SCSI controller
5424 chip from the aic777x series or the aic78xx series, this driver
5425 should work. The only exception is the 7810 which is specifically
5426 not supported (that's the RAID controller chip on the AAA-13x
5429 Note that the AHA2920 SCSI host adapter is *not* supported by this
5430 driver; choose "Future Domain 16xx SCSI support" instead if you have
5433 Information on the configuration options for this controller can be
5434 found by checking the help file for each of the available
5435 configuration options. You should read drivers/scsi/README.aic7xxx
5436 at a minimum before contacting the maintainer with any questions.
5437 The SCSI-HOWTO, available from
5438 http://www.linuxdoc.org/docs.html#howto , can also be of great
5441 If you want to compile this driver as a module ( = code which can be
5442 inserted in and removed from the running kernel whenever you want),
5443 say M here and read Documentation/modules.txt. The module will be
5446 Enable or Disable Tagged Command Queueing by default
5447 CONFIG_AIC7XXX_TCQ_ON_BY_DEFAULT
5448 This option causes the aic7xxx driver to attempt to use Tagged
5449 Command Queueing (TCQ) on all devices that claim to support it.
5451 TCQ is a feature of SCSI-2 which improves performance: the host
5452 adapter can send several SCSI commands to a device's queue even if
5453 previous commands haven't finished yet. Because the device is
5454 intelligent, it can optimize its operations (like head positioning)
5455 based on its own request queue. Not all devices implement this
5458 If you say Y here, you can still turn off TCQ on troublesome devices
5459 with the use of the tag_info boot parameter. See the file
5460 drivers/scsi/README.aic7xxx for more information on that and other
5461 aic7xxx setup commands. If this option is turned off, you may still
5462 enable TCQ on known good devices by use of the tag_info boot
5465 If you are unsure about your devices then it is safest to say N
5468 However, TCQ can increase performance on some hard drives by as much
5469 as 50% or more, so it is recommended that if you say N here, you
5470 should at least read the README.aic7xxx file so you will know how to
5471 enable this option manually should your drives prove to be safe in
5474 Conversely, certain drives are known to lock up or cause bus resets
5475 when TCQ is enabled on them. If you have a Western Digital
5476 Enterprise SCSI drive for instance, then don't even bother to enable
5477 TCQ on it as the drive will become unreliable, and it will actually
5480 Default number of TCQ commands per device
5481 CONFIG_AIC7XXX_CMDS_PER_DEVICE
5482 Specify the number of commands you would like to allocate per SCSI
5483 device when Tagged Command Queueing (TCQ) is enabled on that device.
5485 Reasonable figures are in the range of 8 to 24 commands per device,
5486 but depending on hardware could be increased or decreased from that
5487 figure. If the number is too high for any particular device, the
5488 driver will automatically compensate usually after only 10 minutes
5489 of uptime. It will not hinder performance if some of your devices
5490 eventually have their command depth reduced, but is a waste of
5491 memory if all of your devices end up reducing this number down to a
5492 more reasonable figure.
5494 NOTE: Certain very broken drives are known to lock up when given
5495 more commands than they like to deal with. Quantum Fireball drives
5496 are the most common in this category. For the Quantum Fireball
5497 drives it is suggested to use no more than 8 commands per device.
5501 Collect statistics to report in /proc
5502 CONFIG_AIC7XXX_PROC_STATS
5503 This option tells the driver to keep track of how many commands have
5504 been sent to each particular device and report that information to
5505 the user via the /proc/scsi/aic7xxx/n file, where n is the number of
5506 the aic7xxx controller you want the information on. This adds a
5507 small amount of overhead to each and every SCSI command the aic7xxx
5508 driver handles, so if you aren't really interested in this
5509 information, it is best to leave it disabled. This will only work if
5510 you also say Y to "/proc file system support", below.
5514 Delay in seconds after SCSI bus reset
5515 CONFIG_AIC7XXX_RESET_DELAY
5516 This sets how long the driver will wait after resetting the SCSI bus
5517 before attempting to communicate with the devices on the SCSI bus
5518 again. This delay will be used during the reset phase at bootup time
5519 as well as after any reset that might occur during normal operation.
5520 Reasonable numbers range anywhere from 5 to 15 seconds depending on
5521 your devices. DAT tape drives are notorious for needing more time
5522 after a bus reset to be ready for the next command, but most hard
5523 drives and CD-ROM devices are ready in only a few seconds. This
5524 option has a maximum upper limit of 20 seconds to avoid bad
5525 interactions between the aic7xxx driver and the rest of the Linux
5526 kernel. The default value has been reduced to 5 seconds. If this
5527 doesn't work with your hardware, try increasing this value.
5529 IBM ServeRAID Support
5531 This is support for the IBM ServeRAID hardware RAID controllers.
5532 See http://www.developer.ibm.com/welcome/netfinity/serveraid.html
5533 for more information. If this driver does not work correctly
5534 without modification please contact the author by email at
5535 ipslinux@us.ibm.com.
5537 You can build this driver as a module ( = code which can be
5538 inserted in and removed from the running kernel whenever you want),
5539 but only a single instance may be loaded. If you want to compile it
5540 as a module, say M here and read Documentation/modules.txt. The
5541 module will be called ips.o.
5543 BusLogic SCSI support
5544 CONFIG_SCSI_BUSLOGIC
5545 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
5546 Adapters. Consult the SCSI-HOWTO, available from
5547 http://www.linuxdoc.org/docs.html#howto , and the files
5548 README.BusLogic and README.FlashPoint in drivers/scsi for more
5549 information. If this driver does not work correctly without
5550 modification, please contact the author, Leonard N. Zubkoff, by
5551 email to lnz@dandelion.com.
5553 You can also build this driver as a module ( = code which can be
5554 inserted in and removed from the running kernel whenever you want),
5555 but only a single instance may be loaded. If you want to compile it
5556 as a module, say M here and read Documentation/modules.txt. The
5557 module will be called BusLogic.o.
5559 Omit BusLogic SCSI FlashPoint support
5560 CONFIG_SCSI_OMIT_FLASHPOINT
5561 This option allows you to omit the FlashPoint support from the
5562 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
5563 substantial, so users of MultiMaster Host Adapters may wish to omit
5566 DMX3191D SCSI support
5567 CONFIG_SCSI_DMX3191D
5568 This is support for Domex DMX3191D SCSI Host Adapters.
5570 This driver is also available as a module ( = code which can be
5571 inserted in and removed from the running kernel whenever you want).
5572 The module will be called dmx3191d.o. If you want to compile it as a
5573 module, say M here and read Documentation/modules.txt.
5575 DTC3180/3280 SCSI support
5577 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
5578 the SCSI-HOWTO, available from
5579 http://www.linuxdoc.org/docs.html#howto , and the file
5580 drivers/scsi/README.dtc3x80.
5582 This driver is also available as a module ( = code which can be
5583 inserted in and removed from the running kernel whenever you want).
5584 The module will be called dtc.o. If you want to compile it as a
5585 module, say M here and read Documentation/modules.txt.
5587 EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti, Alphatronix) support
5588 CONFIG_SCSI_EATA_DMA
5589 This is support for the EATA-DMA protocol compliant SCSI Host
5590 Adapters like the SmartCache III/IV, SmartRAID controller families
5591 and the DPT PM2011B and PM2012B controllers.
5593 Note that this driver is obsolete; if you have one of the above SCSI
5594 Host Adapters, you should normally say N here and Y to "EATA
5595 ISA/EISA/PCI support", below. Please read the SCSI-HOWTO, available
5596 from http://www.linuxdoc.org/docs.html#howto .
5598 This driver is also available as a module ( = code which can be
5599 inserted in and removed from the running kernel whenever you want).
5600 The module will be called eata_dma.o. If you want to compile it as a
5601 module, say M here and read Documentation/modules.txt.
5603 EATA-PIO (old DPT PM2001, PM2012A) support
5604 CONFIG_SCSI_EATA_PIO
5605 This driver supports all EATA-PIO protocol compliant SCSI Host
5606 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
5607 host adapters could also use this driver but are discouraged from
5608 doing so, since this driver only supports hard disks and lacks
5609 numerous features. You might want to have a look at the SCSI-HOWTO,
5610 available from http://www.linuxdoc.org/docs.html#howto .
5612 If you want to compile this as a module ( = code which can be
5613 inserted in and removed from the running kernel whenever you want),
5614 say M here and read Documentation/modules.txt. The module will be
5617 UltraStor 14F/34F support
5619 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
5620 The source at drivers/scsi/u14-34f.c contains some information about
5621 this hardware. If the driver doesn't work out of the box, you may
5622 have to change some settings in drivers/scsi/u14-34f.c. Read the
5623 SCSI-HOWTO, available from
5624 http://www.linuxdoc.org/docs.html#howto . Note that there is also
5625 another driver for the same hardware: "UltraStor SCSI support",
5626 below. You should say Y to both only if you want 24F support as
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 u14-34f.o. If you want to compile it as a
5632 module, say M here and read Documentation/modules.txt.
5634 enable elevator sorting
5635 CONFIG_SCSI_U14_34F_LINKED_COMMANDS
5636 This option enables elevator sorting for all probed SCSI disks and
5637 CDROMs. It definitely reduces the average seek distance when doing
5638 random seeks, but this does not necessarily result in a noticeable
5639 performance improvement: your mileage may vary...
5641 The safe answer is N.
5643 maximum number of queued commands
5644 CONFIG_SCSI_U14_34F_MAX_TAGS
5645 This specifies how many SCSI commands can be maximally queued for
5646 each probed SCSI device. You should reduce the default value of 8
5647 only if you have disks with buggy or limited tagged command support.
5648 Minimum is 2 and maximum is 14. This value is also the window size
5649 used by the elevator sorting option above. The effective value used
5650 by the driver for each probed SCSI device is reported at boot time.
5652 Future Domain 16xx SCSI/AHA-2920A support
5653 CONFIG_SCSI_FUTURE_DOMAIN
5654 This is support for Future Domain's 16-bit SCSI host adapters
5655 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
5656 other adapters based on the Future Domain chipsets (Quantum
5657 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
5658 It is explained in section 3.7 of the SCSI-HOWTO, available from
5659 http://www.linuxdoc.org/docs.html#howto .
5661 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
5662 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
5663 controller support"). This Future Domain driver works with the older
5664 Adaptec AHA-2920A boards with a Future Domain chip on them.
5666 This driver is also available as a module ( = code which can be
5667 inserted in and removed from the running kernel whenever you want).
5668 The module will be called fdomain.o. If you want to compile it as a
5669 module, say M here and read Documentation/modules.txt.
5671 Future Domain MCS-600/700 SCSI support
5673 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
5674 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
5675 is identical to the MCS 700 and hence also supported by this driver.
5676 This driver also supports the Reply SB16/SCSI card (the SCSI part).
5677 It supports multiple adapters in the same system.
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 fd_mcs.o. If you want to compile it as a
5682 module, say M here and read Documentation/modules.txt.
5684 Generic NCR5380/53c400 SCSI support
5685 CONFIG_SCSI_GENERIC_NCR5380
5686 This is the generic NCR family of SCSI controllers, not to be
5687 confused with the NCR 53c7 or 8xx controllers. It is explained in
5688 section 3.8 of the SCSI-HOWTO, available from
5689 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
5690 of the box, you may have to change some settings in
5691 drivers/scsi/g_NCR5380.h.
5693 This driver is also available as a module ( = code which can be
5694 inserted in and removed from the running kernel whenever you want).
5695 The module will be called g_NCR5380.o. If you want to compile it as
5696 a module, say M here and read Documentation/modules.txt.
5698 Enable NCR53c400 extensions
5699 CONFIG_SCSI_GENERIC_NCR53C400
5700 This enables certain optimizations for the NCR53c400 SCSI cards. You
5701 might as well try it out. Note that this driver will only probe for
5702 the Trantor T130B in its default configuration; you might have to
5703 pass a command line option to the kernel at boot time if it doesn't
5704 detect your card. See the file drivers/scsi/README.g_NCR5380 for
5707 NCR5380/53c400 mapping method (use Port for T130B)
5708 CONFIG_SCSI_G_NCR5380_PORT
5709 The NCR5380 and NCR53c400 SCSI controllers come in two varieties:
5710 port or memory mapped. You should know what you have. The most
5711 common card, Trantor T130B, uses port mapped mode.
5713 NCR53c7,8xx SCSI support
5714 CONFIG_SCSI_NCR53C7xx
5715 This is a driver for the 53c7 and 8xx NCR family of SCSI
5716 controllers, not to be confused with the NCR 5380 controllers. It is
5717 explained in section 3.8 of the SCSI-HOWTO, available from
5718 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
5719 of the box, you may have to change some settings in
5720 drivers/scsi/53c7,8xx.h. Please read drivers/scsi/README.ncr53c7xx
5721 for the available boot time command line options.
5723 Note: there is another driver for the 53c8xx family of controllers
5724 ("NCR53C8XX SCSI support" below). If you want to use them both, you
5725 need to say M to both and build them as modules, but only one may be
5726 active at a time. If you have a 53c8xx board, it's better to use the
5729 This driver is also available as a module ( = code which can be
5730 inserted in and removed from the running kernel whenever you want).
5731 The module will be called 53c7,8xx.o. If you want to compile it as a
5732 module, say M here and read Documentation/modules.txt.
5734 always negotiate synchronous transfers
5735 CONFIG_SCSI_NCR53C7xx_sync
5736 In general, this is good; however, it is a bit dangerous since there
5737 are some broken SCSI devices out there. Take your chances. Safe bet
5740 allow FAST-SCSI [10MHz]
5741 CONFIG_SCSI_NCR53C7xx_FAST
5742 This will enable 10MHz FAST-SCSI transfers with your host
5743 adapter. Some systems have problems with that speed, so it's safest
5747 CONFIG_SCSI_NCR53C7xx_DISCONNECT
5748 This enables the disconnect/reconnect feature of the NCR SCSI
5749 controller. When you say Y here, a slow SCSI device will not lock
5750 the SCSI bus while processing a request, allowing simultaneous use
5751 of e.g. a SCSI hard disk and SCSI tape or CD-ROM drive, and
5752 providing much better performance when using slow and fast SCSI
5753 devices at the same time. Some devices, however, do not operate
5754 properly with this option enabled, and will cause your SCSI system
5755 to hang, which might cause a system crash. The safe answer
5756 therefore is to say N.
5758 NCR53C8XX SCSI support
5759 CONFIG_SCSI_NCR53C8XX
5760 This is the BSD ncr driver adapted to Linux for the NCR53C8XX family
5761 of PCI-SCSI controllers. This driver supports parity checking,
5762 tagged command queuing and fast synchronous data transfers up to 80
5763 MB/s with wide FAST-40 LVD devices and controllers.
5765 Recent versions of the 53C8XX chips are better supported by the
5766 option "SYM53C8XX SCSI support", below.
5768 Note: there is yet another driver for the 53c8xx family of
5769 controllers ("NCR53c7,8xx SCSI support" above). If you want to use
5770 them both, you need to say M to both and build them as modules, but
5771 only one may be active at a time. If you have a 53c8xx board, you
5772 probably do not want to use the "NCR53c7,8xx SCSI support".
5774 Please read drivers/scsi/README.ncr53c8xx for more information.
5776 SYM53C8XX SCSI support
5777 CONFIG_SCSI_SYM53C8XX
5778 This driver supports all the features of recent 53C8XX chips (used
5779 in PCI SCSI controllers), notably the hardware phase mismatch
5780 feature of the SYM53C896.
5782 Older versions of the 53C8XX chips are not supported by this
5783 driver. If your system uses either a 810 rev. < 16, a 815, or a 825
5784 rev. < 16 PCI SCSI processor, you must use the generic NCR53C8XX
5785 driver ("NCR53C8XX SCSI support" above) or configure both the
5786 NCR53C8XX and this SYM53C8XX drivers either as module or linked to
5789 When both drivers are linked into the kernel, the SYM53C8XX driver
5790 is called first at initialization and you can use the 'excl=ioaddr'
5791 driver boot option to exclude attachment of adapters by the
5792 SYM53C8XX driver. For example, entering
5793 'sym53c8xx=excl:0xb400,excl=0xc000' at the lilo prompt prevents
5794 adapters at io address 0xb400 and 0xc000 from being attached by the
5795 SYM53C8XX driver, thus allowing the NCR53C8XX driver to attach them.
5796 The 'excl' option is also supported by the NCR53C8XX driver.
5798 Please read drivers/scsi/README.ncr53c8xx for more information.
5800 synchronous data transfers frequency
5801 CONFIG_SCSI_NCR53C8XX_SYNC
5802 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
5803 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers are
5804 respectively the maximum data transfer rates in mega-transfers per
5805 second for each class. For example, a FAST-20 Wide 16 device is able
5806 to transfer data at 20 million 16 bit packets per second for a total
5809 You may specify 0 if you want to only use asynchronous data
5810 transfers. This is the safest and slowest option. Otherwise, specify
5811 a value between 5 and 80, depending on the capability of your SCSI
5812 controller. The higher the number, the faster the data transfer.
5813 Note that 80 should normally be ok since the driver decreases the
5814 value automatically according to the controller's capabilities.
5816 Your answer to this question is ignored for controllers with NVRAM,
5817 since the driver will get this information from the user set-up. It
5818 also can be overridden using a boot setup option, as follows
5819 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
5820 for FAST-20 synchronous data transfer (20 mega-transfers per
5823 The normal answer therefore is not to go with the default but to
5824 select the maximum value 80 allowing the driver to use the maximum
5825 value supported by each controller. If this causes problems with
5826 your SCSI devices, you should come back and decrease the value.
5828 There is no safe option other than using good cabling, right
5829 terminations and SCSI conformant devices.
5832 CONFIG_SCSI_NCR53C8XX_IOMAPPED
5833 If you say Y here, the driver will use normal IO, as opposed to
5834 memory mapped IO. Memory mapped IO has less latency than normal IO
5835 and works for most Intel-based hardware. Under Linux/Alpha only
5836 normal IO is currently supported by the driver and so, this option
5837 has no effect on those systems.
5839 The normal answer therefore is N; try Y only if you encounter SCSI
5842 not allow targets to disconnect
5843 CONFIG_SCSI_NCR53C8XX_NO_DISCONNECT
5844 This option is only provided for safety if you suspect some SCSI
5845 device of yours to not support properly the target-disconnect
5846 feature. In that case, you would say Y here. In general however, to
5847 not allow targets to disconnect is not reasonable if there is more
5848 than 1 device on a SCSI bus. The normal answer therefore is N.
5850 default tagged command queue depth
5851 CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS
5852 "Tagged command queuing" is a feature of SCSI-2 which improves
5853 performance: the host adapter can send several SCSI commands to a
5854 device's queue even if previous commands haven't finished yet.
5855 Because the device is intelligent, it can optimize its operations
5856 (like head positioning) based on its own request queue. Some SCSI
5857 devices don't implement this properly; if you want to disable this
5858 feature, enter 0 or 1 here (it doesn't matter which).
5860 The default value is 8 and should be supported by most hard disks.
5861 This value can be overridden from the boot command line using the
5862 'tags' option as follows (example):
5863 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
5864 4, set queue depth to 16 for target 2 and target 3 on controller 0
5865 and set queue depth to 10 for target 0 / lun 2 on controller 1.
5867 The normal answer therefore is to go with the default 8 and to use
5868 a boot command line option for devices that need to use a different
5869 command queue depth.
5871 There is no safe option other than using good SCSI devices.
5873 maximum number of queued commands
5874 CONFIG_SCSI_NCR53C8XX_MAX_TAGS
5875 This option allows you to specify the maximum number of commands
5876 that can be queued to any device, when tagged command queuing is
5877 possible. The default value is 32. Minimum is 2, maximum is 64.
5878 Modern hard disks are able to support 64 tags and even more, but
5879 do not seem to be faster when more than 32 tags are being used.
5881 So, the normal answer here is to go with the default value 32 unless
5882 you are using very large hard disks with large cache (>= 1 MB) that
5883 are able to take advantage of more than 32 tagged commands.
5885 There is no safe option and the default answer is recommended.
5887 assume boards are SYMBIOS compatible (EXPERIMENTAL)
5888 CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT
5889 This option allows you to enable some features depending on GPIO
5890 wiring. These General Purpose Input/Output pins can be used for
5891 vendor specific features or implementation of the standard SYMBIOS
5892 features. Genuine SYMBIOS controllers use GPIO0 in output for
5893 controller LED and GPIO3 bit as a flag indicating
5894 singled-ended/differential interface. The Tekram DC-390U/F boards
5895 uses a different GPIO wiring.
5897 Your answer to this question is ignored if all your controllers have
5898 NVRAM, since the driver is able to detect the board type from the
5901 If all the controllers in your system are genuine SYMBIOS boards or
5902 use BIOS and drivers from SYMBIOS, you would want to say Y here,
5903 otherwise N. N is the safe answer.
5905 enable profiling statistics gathering
5906 CONFIG_SCSI_NCR53C8XX_PROFILE
5907 This option allows you to enable profiling information gathering.
5908 These statistics are not very accurate due to the low frequency
5909 of the kernel clock (100 Hz on i386) and have performance impact
5910 on systems that use very fast devices.
5912 The normal answer therefore is N.
5914 include support for the NCR PQS/PDS SCSI card
5915 CONFIG_SCSI_NCR53C8XX_PQS_PDS
5916 Say Y here if you have a special SCSI adapter produced by NCR
5917 corporation called a PCI Quad SCSI or PCI Dual SCSI. You do not need
5918 this if you do not have one of these adapters. However, since this
5919 device is detected as a specific PCI device, this option is quite
5922 The common answer here is N, but answering Y is safe.
5926 This is support for the IBM SCSI adapter found in many of the PS/2
5927 series computers. These machines have an MCA bus, so you need to
5928 answer Y to "MCA support" as well and read Documentation/mca.txt.
5930 If the adapter isn't found during boot (a common problem for models
5931 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
5932 option, where <pun> is the id of the SCSI subsystem (usually 7, but
5933 if that doesn't work check your reference diskette). Owners of model
5934 95 with a LED-matrix-display can in addition activate some activity
5935 info like under OS/2, but more informative, by setting
5936 'ibmmcascsi=display' as an additional kernel parameter. Try "man
5937 bootparam" or see the documentation of your boot loader about how to
5938 pass options to the kernel.
5940 If you want to compile this driver as a module ( = code which can be
5941 inserted in and removed from the running kernel whenever you want),
5942 say M here and read Documentation/modules.txt. The module will be
5946 CONFIG_IBMMCA_SCSI_ORDER_STANDARD
5947 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
5948 are assigned to the drive letters, starting with the lowest SCSI-id
5949 (physical number -- pun) to be drive C:, as seen from DOS and
5950 similar operating systems. When looking into papers describing the
5951 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
5952 The SCSI-standard follows a hardware-hierarchy which says that id 7
5953 has the highest priority and id 0 the lowest. Therefore, the host
5954 adapters are still today everywhere placed as SCSI-id 7 by default.
5955 In the SCSI-standard, the drive letters express the priority of the
5956 disk. C: should be the hard disk, or a partition on it, with the
5957 highest priority. This must therefore be the disk with the highest
5958 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
5959 original definition of the SCSI-standard as also industrial- and
5960 process-control-machines, like VME-CPUs running under realtime-OSs
5961 (e.g. LynxOS, OS9) do.
5963 If you like to run Linux on your MCA-machine with the same
5964 assignment of hard disks as seen from e.g. DOS or OS/2 on your
5965 machine, which is in addition conformant to the SCSI-standard, you
5966 must say Y here. This is also necessary for MCA-Linux users who want
5967 to keep downward compatibility to older releases of the
5968 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
5971 If you like to have the lowest SCSI-id assigned as drive C:, as
5972 modern SCSI-BIOSes do, which does not conform to the standard, but
5973 is widespread and common in the PC-world of today, you must say N
5974 here. If unsure, say Y.
5976 Reset SCSI-devices at boot time
5977 CONFIG_IBMMCA_SCSI_DEV_RESET
5978 By default, SCSI-devices are reset when the machine is powered on.
5979 However, some devices exist, like special-control-devices,
5980 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
5981 not reset when switched on. If you say Y here, each device connected
5982 to your SCSI-bus will be issued a reset-command after it has been
5983 probed, while the kernel is booting. This may cause problems with
5984 more modern devices, like hard disks, which do not appreciate these
5985 reset commands, and can cause your system to hang. So say Y only if
5986 you know that one of your older devices needs it; N is the safe
5989 NCR 53C9x MCA support
5990 CONFIG_SCSI_MCA_53C9X
5991 Some Microchannel machines, notably the NCR 35xx line, use a SCSI
5992 controller based on the NCR 53C94. This driver will allow use of
5993 the controller on the 3550, and very possibly others.
5995 If you want to compile this as a module (= code which can be
5996 inserted and removed from the running kernel whenever you want), say
5997 M here and read Documentation/modules.txt. The module will be called
6000 Always IN2000 SCSI support
6002 This is support for an ISA bus SCSI host adapter. You'll find more
6003 information in drivers/scsi/in2000.readme. If it doesn't work out of
6004 the box, you may have to change the jumpers for IRQ or address
6007 If you want to compile this as a module ( = code which can be
6008 inserted in and removed from the running kernel whenever you want),
6009 say M here and read Documentation/modules.txt. The module will be
6012 Initio 91XXU(W) SCSI support
6014 This is support for the Initio 91XXU(W) SCSI host adapter. Please
6015 read the SCSI-HOWTO, available from
6016 http://www.linuxdoc.org/docs.html#howto .
6018 If you want to compile this as a module ( = code which can be
6019 inserted in and removed from the running kernel whenever you want),
6020 say M here and read Documentation/modules.txt. The module will be
6025 This is support for a SCSI host adapter. It is explained in section
6026 3.10 of the SCSI-HOWTO, available from
6027 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
6028 of the box, you may have to change some settings in
6029 drivers/scsi/pas16.h.
6031 This driver is also available as a module ( = code which can be
6032 inserted in and removed from the running kernel whenever you want).
6033 The module will be called pas16.o. If you want to compile it as a
6034 module, say M here and read Documentation/modules.txt.
6036 Initio INI-A100U2W SCSI support
6038 This is support for the Initio INI-A100U2W SCSI host adapter. Please
6039 read the SCSI-HOWTO, available from
6040 http://www.linuxdoc.org/docs.html#howto .
6042 If you want to compile this as a module ( = code which can be
6043 inserted in and removed from the running kernel whenever you want),
6044 say M here and read Documentation/modules.txt. The module will be
6049 This is support for the PCI2000I EIDE interface card which acts as a
6050 SCSI host adapter. Please read the SCSI-HOWTO, available from
6051 http://www.linuxdoc.org/docs.html#howto .
6053 This driver is also available as a module called pci2000.o ( = code
6054 which can be inserted in and removed from the running kernel
6055 whenever you want). If you want to compile it as a module, say M
6056 here and read Documentation/modules.txt.
6059 CONFIG_SCSI_PCI2220I
6060 This is support for the PCI2220i EIDE interface card which acts as a
6061 SCSI host adapter. Please read the SCSI-HOWTO, available from
6062 http://www.linuxdoc.org/docs.html#howto .
6064 This driver is also available as a module called pci2220i.o ( = code
6065 which can be inserted in and removed from the running kernel
6066 whenever you want). If you want to compile it as a module, say M
6067 here and read Documentation/modules.txt.
6071 This is support for the PSI240i EIDE interface card which acts as a
6072 SCSI host adapter. Please read the SCSI-HOWTO, available from
6073 http://www.linuxdoc.org/docs.html#howto .
6075 This driver is also available as a module called psi240i.o ( = code
6076 which can be inserted in and removed from the running kernel
6077 whenever you want). If you want to compile it as a module, say M
6078 here and read Documentation/modules.txt.
6080 Qlogic FAS SCSI support
6081 CONFIG_SCSI_QLOGIC_FAS
6082 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
6083 FastSCSI! cards as well as any other card based on the FASXX chip
6084 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
6086 This driver does NOT support the PCI versions of these cards. The
6087 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
6088 SCSI support"), below.
6090 Information about this driver is contained in
6091 drivers/scsi/README.qlogicfas. You should also read the SCSI-HOWTO,
6092 available from http://www.linuxdoc.org/docs.html#howto .
6094 This driver is also available as a module ( = code which can be
6095 inserted in and removed from the running kernel whenever you want).
6096 The module will be called qlogicfas.o. If you want to compile it as
6097 a module, say M here and read Documentation/modules.txt.
6099 Qlogic ISP SCSI support (EXPERIMENTAL)
6100 CONFIG_SCSI_QLOGIC_ISP
6101 This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
6102 IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
6103 card is supported by the "AM53/79C974 PCI SCSI" driver).
6105 If you say Y here, make sure to choose "BIOS" at the question "PCI
6108 Please read the file drivers/scsi/README.qlogicisp. You should also
6109 read the SCSI-HOWTO, available from
6110 http://www.linuxdoc.org/docs.html#howto .
6112 This driver is also available as a module ( = code which can be
6113 inserted in and removed from the running kernel whenever you want).
6114 The module will be called qlogicisp.o. If you want to compile it as
6115 a module, say M here and read Documentation/modules.txt.
6117 Qlogic ISP FC SCSI support
6118 CONFIG_SCSI_QLOGIC_FC
6119 This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
6121 This driver is also available as a module ( = code which can be
6122 inserted in and removed from the running kernel whenever you want).
6123 The module will be called qlogicfc.o. If you want to compile it as
6124 a module, say M here and read Documentation/modules.txt.
6126 Qlogic QLA 1280 SCSI support
6127 CONFIG_SCSI_QLOGIC_1280
6128 Say Y if you have a QLogic ISP1x80/1x160 SCSI host adapter.
6130 This driver is also available as a module ( = code which can be
6131 inserted in and removed from the running kernel whenever you want).
6132 The module will be called qla1280.o. If you want to compile it as
6133 a module, say M here and read Documentation/modules.txt.
6135 Seagate ST-02 and Future Domain TMC-8xx SCSI support
6137 These are 8-bit SCSI controllers; the ST-01 is also supported by
6138 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
6139 available from http://www.linuxdoc.org/docs.html#howto . If it
6140 doesn't work out of the box, you may have to change some settings in
6141 drivers/scsi/seagate.h.
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 seagate.o. If you want to compile it as a
6146 module, say M here and read Documentation/modules.txt.
6148 Trantor T128/T128F/T228 SCSI support
6150 This is support for a SCSI host adapter. It is explained in section
6151 3.11 of the SCSI-HOWTO, available from
6152 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
6153 of the box, you may have to change some settings in
6154 drivers/scsi/t128.h. Note that Trantor was purchased by Adaptec, and
6155 some former Trantor products are being sold under the Adaptec name.
6157 This driver is also available as a module ( = code which can be
6158 inserted in and removed from the running kernel whenever you want).
6159 The module will be called t128.o. If you want to compile it as a
6160 module, say M here and read Documentation/modules.txt.
6162 UltraStor SCSI support
6163 CONFIG_SCSI_ULTRASTOR
6164 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
6165 adapter family. This driver is explained in section 3.12 of the
6166 SCSI-HOWTO, available from
6167 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
6168 of the box, you may have to change some settings in
6169 drivers/scsi/ultrastor.h.
6171 Note that there is also another driver for the same hardware:
6172 "UltraStor 14F/34F support", above.
6174 If you want to compile this as a module ( = code which can be
6175 inserted in and removed from the running kernel whenever you want),
6176 say M here and read Documentation/modules.txt. The module will be
6179 7000FASST SCSI support
6180 CONFIG_SCSI_7000FASST
6181 This driver supports the Western Digital 7000 SCSI host adapter
6182 family. Some information is in the source: drivers/scsi/wd7000.c.
6184 This driver is also available as a module ( = code which can be
6185 inserted in and removed from the running kernel whenever you
6186 want). The module will be called wd7000.o. If you want to compile it
6187 as a module, say M here and read Documentation/modules.txt.
6191 This driver supports the ACARD 870U/W SCSI host adapter.
6193 This driver is also available as a module ( = code which can be
6194 inserted in and removed from the running kernel whenever you want).
6195 The module will be called atp870u.o. If you want to compile it as a
6196 module, say M here and read Documentation/modules.txt.
6198 EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support
6200 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
6201 ISA and all EISA i/o addresses are probed looking for the "EATA"
6202 signature. If you chose "BIOS" at the question "PCI access mode",
6203 the addresses of all the PCI SCSI controllers reported by the PCI
6204 subsystem are probed as well.
6206 You want to read the start of drivers/scsi/eata.c and the
6207 SCSI-HOWTO, available from
6208 http://www.linuxdoc.org/docs.html#howto .
6210 Note that there is also another driver for the same hardware
6211 available: "EATA-DMA support". You should say Y to only one of them.
6213 If you want to compile this as a module ( = code which can be
6214 inserted in and removed from the running kernel whenever you want),
6215 say M here and read Documentation/modules.txt. The module will be
6218 enable tagged command queuing
6219 CONFIG_SCSI_EATA_TAGGED_QUEUE
6220 This is a feature of SCSI-2 which improves performance: the host
6221 adapter can send several SCSI commands to a device's queue even if
6222 previous commands haven't finished yet. Most EATA adapters negotiate
6223 this feature automatically with the device, even if your answer is
6224 N. The safe answer is N.
6226 enable elevator sorting
6227 CONFIG_SCSI_EATA_LINKED_COMMANDS
6228 This option enables elevator sorting for all probed SCSI disks and
6229 CDROMs. It definitely reduces the average seek distance when doing
6230 random seeks, but this does not necessarily result in a noticeable
6231 performance improvement: your mileage may vary...
6232 The safe answer is N.
6234 maximum number of queued commands
6235 CONFIG_SCSI_EATA_MAX_TAGS
6236 This specifies how many SCSI commands can be maximally queued for
6237 each probed SCSI device. You should reduce the default value of 16
6238 only if you have disks with buggy or limited tagged command support.
6239 Minimum is 2 and maximum is 62. This value is also the window size
6240 used by the elevator sorting option above. The effective value used
6241 by the driver for each probed SCSI device is reported at boot time.
6243 NCR53c406a SCSI support
6244 CONFIG_SCSI_NCR53C406A
6245 This is support for the NCR53c406a SCSI host adapter. For user
6246 configurable parameters, check out drivers/scsi/NCR53c406.c in the
6247 kernel source. Also read the SCSI-HOWTO, available from
6248 http://www.linuxdoc.org/docs.html#howto .
6250 If you want to compile this driver as a module ( = code which can be
6251 inserted in and removed from the running kernel whenever you want),
6252 say M here and read Documentation/modules.txt. The module will be
6255 Symbios Logic sym53c416 support
6256 CONFIG_SCSI_SYM53C416
6257 This is support for the sym53c416 SCSI host adapter, the SCSI
6258 adapter that comes with some HP scanners. This driver requires that
6259 the sym53c416 is configured first using some sort of pnp
6260 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
6261 are using isapnp then you need to compile this driver as a module
6262 and then load it using insmod after isapnp has run. The parameters
6263 of the configured card(s) should be passed to the driver. The format
6266 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
6268 There is support for up to four adapters. If you want to compile
6269 this driver as a module ( = code which can be inserted in and
6270 removed from the running kernel whenever you want), say M here and
6271 read Documentation/modules.txt. The module will be called
6274 Simple 53c710 SCSI support (Compaq, NCR machines)
6276 This is a simple driver for NCR53c710 based SCSI host adapters.
6278 More complex drivers for this chip are available ("NCR53c7,8xx SCSI
6279 support", above), but they require that the scsi chip be able to do
6280 DMA block moves between memory and on-chip registers, which can
6281 cause problems under certain conditions. This driver is designed to
6282 avoid these problems and is intended to work with any Intel machines
6283 using 53c710 chips, including various Compaq and NCR machines.
6285 Please read the comments at the top of the file
6286 drivers/scsi/sim710.c for more information.
6288 If you want to compile this driver as a module ( = code which can be
6289 inserted in and removed from the running kernel whenever you want),
6290 say M here and read Documentation/modules.txt. The module will be
6293 Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support
6295 This driver supports PCI SCSI host adapters based on the Am53C974A
6296 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
6297 PCscsi/PCnet (Am53/79C974) solutions.
6299 Documentation can be found in drivers/scsi/README.tmscsim.
6301 Note that this driver does NOT support Tekram DC390W/U/F, which are
6302 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
6303 Also note that there is another generic Am53C974 driver,
6304 "AM53/79C974 PCI SCSI support" below. You can pick either one.
6306 If you want to compile this driver as a module ( = code which can be
6307 inserted in and removed from the running kernel whenever you want),
6308 say M here and read Documentation/modules.txt. The module will be
6311 Omit support for other Am53/79C974 based SCSI adapters
6312 CONFIG_SCSI_DC390T_NOGENSUPP
6313 If you say N here, the DC390(T) SCSI driver relies on the DC390
6314 EEPROM to get initial values for its settings, such as speed,
6315 termination, etc. If it can't find this EEPROM, it will use defaults
6316 or the user supplied boot/module parameters. For details on driver
6317 configuration see drivers/scsi/README.tmscsim.
6319 If you say Y here and if no EEPROM is found, the driver gives up and
6320 thus only supports Tekram DC390(T) adapters. This can be useful if
6321 you have a DC390(T) and another Am53C974 based adapter, which, for
6322 some reason, you want to drive with the other AM53C974 driver.
6326 AM53/79C974 PCI SCSI support
6327 CONFIG_SCSI_AM53C974
6328 This is support for the AM53/79C974 SCSI host adapters. Please read
6329 drivers/scsi/README.AM53C974 for details. Also, the SCSI-HOWTO,
6330 available from http://www.linuxdoc.org/docs.html#howto , is for
6333 Note that there is another driver for AM53C974 based adapters:
6334 "Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support", above. You
6335 can pick either one.
6337 If you want to compile this driver as a module ( = code which can be
6338 inserted in and removed from the running kernel whenever you want),
6339 say M here and read Documentation/modules.txt. The module will be
6342 AMI MegaRAID support
6343 CONFIG_SCSI_MEGARAID
6344 This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490
6345 and 467 SCSI host adapters.
6347 If you want to compile this driver as a module ( = code which can be
6348 inserted in and removed from the running kernel whenever you want),
6349 say M here and read Documentation/modules.txt. The module will be
6352 GDT SCSI Disk Array Controller support
6354 This is a driver for all SCSI Disk Array Controllers (EISA/ISA/PCI)
6355 manufactured by ICP vortex. It is documented in the kernel source in
6356 drivers/scsi/gdth.c and drivers/scsi/gdth.h.
6358 This driver is also available as a module ( = code which can be
6359 inserted in and removed from the running kernel whenever you want).
6360 If you want to compile it as a module, say M here and read
6361 Documentation/modules.txt.
6363 IOMEGA parallel port (ppa - older drives)
6365 This driver supports older versions of IOMEGA's parallel port ZIP
6366 drive (a 100 MB removable media device).
6368 Note that you can say N here if you have the SCSI version of the ZIP
6369 drive: it will be supported automatically if you said Y to the
6370 generic "SCSI disk support", above.
6372 If you have the ZIP Plus drive or a more recent parallel port ZIP
6373 drive (if the supplied cable with the drive is labeled "AutoDetect")
6374 then you should say N here and Y to "IOMEGA parallel port (imm -
6375 newer drives)", below.
6377 For more information about this driver and how to use it you should
6378 read the file drivers/scsi/README.ppa. You should also read the
6379 SCSI-HOWTO, which is available from
6380 http://www.linuxdoc.org/docs.html#howto . If you use this driver,
6381 you will still be able to use the parallel port for other tasks,
6382 such as a printer; it is safe to compile both drivers into the
6385 This driver is also available as a module which can be inserted in
6386 and removed from the running kernel whenever you want. To compile
6387 this driver as a module, say M here and read
6388 Documentation/modules.txt. The module will be called ppa.o.
6390 IOMEGA parallel port (imm - newer drives)
6392 This driver supports newer versions of IOMEGA's parallel port ZIP
6393 drive (a 100 MB removable media device).
6395 Note that you can say N here if you have the SCSI version of the ZIP
6396 drive: it will be supported automatically if you said Y to the
6397 generic "SCSI disk support", above.
6399 If you have the ZIP Plus drive or a more recent parallel port ZIP
6400 drive (if the supplied cable with the drive is labeled "AutoDetect")
6401 then you should say Y here; if you have an older ZIP drive, say N
6402 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
6404 For more information about this driver and how to use it you should
6405 read the file drivers/scsi/README.ppa. You should also read the
6406 SCSI-HOWTO, which is available from
6407 http://www.linuxdoc.org/docs.html#howto . If you use this driver,
6408 you will still be able to use the parallel port for other tasks,
6409 such as a printer; it is safe to compile both drivers into the
6412 This driver is also available as a module which can be inserted in
6413 and removed from the running kernel whenever you want. To compile
6414 this driver as a module, say M here and read
6415 Documentation/modules.txt. The module will be called imm.o.
6417 Force the Iomega ZIP drivers to use EPP-16
6418 CONFIG_SCSI_IZIP_EPP16
6419 EPP (Enhanced Parallel Port) is a standard for parallel ports which
6420 allows them to act as expansion buses that can handle up to 64
6423 Some parallel port chipsets are slower than their motherboard, and
6424 so we have to control the state of the chipset's FIFO queue every
6425 now and then to avoid data loss. This will be done if you say Y
6428 Generally, saying Y is the safe option and slows things down a bit.
6430 Assume slow parallel port control register
6431 CONFIG_SCSI_IZIP_SLOW_CTR
6432 Some parallel ports are known to have excessive delays between
6433 changing the parallel port control register and good data being
6434 available on the parallel port data/status register. This option
6435 forces a small delay (1.0 usec to be exact) after changing the
6436 control register to let things settle out. Enabling this option may
6437 result in a big drop in performance but some very old parallel ports
6438 (found in 386 vintage machines) will not work properly.
6440 Generally, saying N is fine.
6442 Parallel port SCSI device support
6444 There are many external CD-ROM and disk devices that connect through
6445 your computer's parallel port. Lots of them are actually SCSI
6446 devices using a parallel port SCSI adapter. This option enables the
6447 ppSCSI subsystem which contains drivers for many of these external
6448 drives. You may also want to look at CONFIG_PARIDE (Parallel port
6449 IDE device support).
6451 If you built ppSCSI support into your kernel, you may still build
6452 the individual protocol modules and high-level drivers as loadable
6453 modules. If you build this support as a module, it will be called
6456 To use the ppSCSI support, you must say Y or M here and also to at
6457 least one protocol driver (e.g. "Shuttle EPST adapter", "Iomega VPI0
6458 adapter", "Shining ScarSCI adapter" etc.).
6460 Adaptec APA-348 adapter
6462 This option enables support for the APA-348 adapter from Adaptec
6463 (also known as Trantor T348). If you build this as a module it will
6466 Adaptec APA-358 adapter
6468 This option enables support for the APA-358 adapter from Adaptec
6469 (also known as Trantor T358). If you build this as a module it will
6474 This option enables support for the Iomega VPI0 adapter found in the
6475 original ZIP-100 drives and the Jaz Traveller. If you build this as
6476 a module it will be called vpi0.o.
6478 OnSpec 90c26 adapter
6479 CONFIG_PPSCSI_ONSCSI
6480 This option enables support for the OnSpec 90c26 in its SCSI adapter
6481 mode. If you build this as a module it will be called onscsi.o.
6483 Shining SparSCI adapter
6484 CONFIG_PPSCSI_SPARCSI
6485 This option enables support for the WBS-11A parallel port SCSI
6486 adapter. This adapter has been marketed by LinkSys as the
6487 "ParaSCSI+" and by Shining Technologies as the "SparCSI". If you
6488 build this as a module it will be called sparcsi.o.
6490 Shuttle EPSA-2 adapter
6492 This option enables support for the Shuttle Technologies EPSA2
6493 parallel port SCSI adapter. EPAS2 is a predecessor to the EPST. If
6494 you build this as a module it will be called epsa2.o.
6496 Shuttle EPST adapter
6498 This option enables support for the Shuttle Technologies EPST
6499 parallel port SCSI adapter. If you build this as a module is will
6502 SCSI Debug host simulator. (EXPERIMENTAL)
6504 This is a host adapter simulator that can be programmed to simulate
6505 a large number of conditions that could occur on a real bus. The
6506 advantage is that many hard to reproduce problems can be tested in a
6507 controlled environment where there is reduced risk of losing
6508 important data. This is primarily of use to people trying to debug
6509 the middle and upper layers of the SCSI subsystem. If unsure, say N.
6511 Fibre Channel support and FC4 SCSI support
6513 Fibre Channel is a high speed serial protocol mainly used to
6514 connect large storage devices to the computer; it is compatible with
6515 and intended to replace SCSI.
6517 This is an experimental support for storage arrays connected to your
6518 computer using optical fibre cables and the "X3.269-199X Fibre
6519 Channel Protocol for SCSI" specification. If you want to use this,
6520 you need to say Y here and to "SCSI support" as well as to the
6521 drivers for the storage array itself and for the interface adapter
6522 such as SOC or SOC+. This subsystem could even serve for IP
6523 networking, with some code extensions.
6529 Serial Optical Channel is an interface card with one or two Fibre
6530 Optic ports, each of which can be connected to a disk array. Note
6531 that if you have older firmware in the card, you'll need the
6532 microcode from the Solaris driver to make it work.
6534 This support is also available as a module called soc.o ( = code
6535 which can be inserted in and removed from the running kernel
6536 whenever you want). If you want to compile it as a module, say M
6537 here and read Documentation/modules.txt.
6539 Sun SOC+ (aka SOCAL)
6541 Serial Optical Channel Plus is an interface card with up to two
6542 Fibre Optic ports. This card supports FC Arbitrated Loop (usually
6543 A5000 or internal FC disks in E[3-6]000 machines through the
6544 Interface Board). You'll probably need the microcode from the
6545 Solaris driver to make it work.
6547 This support is also available as a module called socal.o ( = code
6548 which can be inserted in and removed from the running kernel
6549 whenever you want). If you want to compile it as a module, say M
6550 here and read Documentation/modules.txt.
6552 SparcSTORAGE Array 100 and 200 series
6554 If you never bought a disk array made by Sun, go with N.
6556 This support is also available as a module called pluto.o ( = code
6557 which can be inserted in and removed from the running kernel
6558 whenever you want). If you want to compile it as a module, say M
6559 here and read Documentation/modules.txt.
6561 Sun Enterprise Network Array (A5000 and EX500)
6563 This driver drives FC-AL disks connected through a Fibre Channel
6564 card using the drivers/fc4 layer (currently only SOCAL). The most
6565 common is either A5000 array or internal disks in E[3-6]000
6568 This support is also available as a module called fcal.o ( = code
6569 which can be inserted in and removed from the running kernel
6570 whenever you want). If you want to compile it as a module, say M
6571 here and read Documentation/modules.txt. If unsure, say N.
6574 CONFIG_SCSI_ACORNSCSI_3
6575 This enables support for the Acorn SCSI card (aka30). If you have an
6576 Acorn system with one of these, say Y. If unsure, say N.
6578 Acorn SCSI tagged queue support
6579 CONFIG_SCSI_ACORNSCSI_TAGGED_QUEUE
6580 Say Y here to enable tagged queuing support on the Acorn SCSI card.
6582 This is a feature of SCSI-2 which improves performance: the host
6583 adapter can send several SCSI commands to a device's queue even if
6584 previous commands haven't finished yet. Some SCSI devices don't
6585 implement this properly, so the safe answer is N.
6587 Acorn SCSI Synchronous transfers support
6588 CONFIG_SCSI_ACORNSCSI_SYNC
6589 Say Y here to enable synchronous transfer negotiation with all
6590 targets on the Acorn SCSI card.
6592 In general, this improves performance; however some SCSI devices
6593 don't implement it properly, so the safe answer is N.
6597 This enables support for the Oak SCSI card. If you have an Acorn
6598 system with one of these, say Y. If unsure, say N.
6600 Cumana SCSI I support
6601 CONFIG_SCSI_CUMANA_1
6602 This enables support for the Cumana SCSI I card. If you have an
6603 Acorn system with one of these, say Y. If unsure, say N.
6605 Cumana SCSI II support (EXPERIMENTAL)
6606 CONFIG_SCSI_CUMANA_2
6607 This enables support for the Cumana SCSI II card. If you have an
6608 Acorn system with one of these, say Y. If unsure, say N.
6612 This enables support for the EcoSCSI card -- a small card that sits
6613 in the Econet socket. If you have an Acorn system with one of these,
6614 say Y. If unsure, say N.
6616 EESOX SCSI support (EXPERIMENTAL)
6617 CONFIG_SCSI_EESOXSCSI
6618 This enables support for the EESOX SCSI card. If you have an Acorn
6619 system with one of these, say Y, otherwise say N.
6621 Powertec SCSI support (EXPERIMENTAL)
6622 CONFIG_SCSI_POWERTECSCSI
6623 This enables support for the Powertec SCSI card on Acorn systems. If
6624 you have one of these, say Y. If unsure, say N.
6626 IEEE 1394 (aka FireWire) support
6628 IEEE 1394 describes a high performance serial bus, which is also
6629 known as FireWire(tm) or i.Link(tm) and is used for connecting all
6630 sorts of devices (most notably digital video cameras) to your
6633 If you have FireWire hardware and want to use it, say Y here. This
6634 is the core support only, you will also need to select a driver for
6635 your IEEE 1394 adapter.
6637 If you want to compile this as a module ( = code which can be
6638 inserted in and removed from the running kernel whenever you want),
6639 say M here and read Documentation/modules.txt. The module will be
6642 TI PCILynx IEEE 1394 support
6643 CONFIG_IEEE1394_PCILYNX
6644 Say Y here if you have a IEEE-1394 controller with the Texas
6645 Instruments PCILynx chip. Note: this driver is written for revision
6646 2 of this chip and may not work with revision 0.
6648 If you want to compile this as a module ( = code which can be
6649 inserted in and removed from the running kernel whenever you want),
6650 say M here and read Documentation/modules.txt. The module will be
6653 Use local RAM on PCILynx board
6654 CONFIG_IEEE1394_PCILYNX_LOCALRAM
6655 This option makes the PCILynx driver use local RAM available on some
6656 PCILynx setups for Packet Control Lists. Local RAM is random access
6657 memory which resides on the PCILynx board as opposed to on your
6658 computer's motherboard. Local RAM may speed up command processing
6659 because no PCI transfers are necessary during use of the Packet
6662 Note that there are no known PCILynx systems providing local RAM
6663 except for the evaluation boards by Texas Instruments and that the
6664 PCILynx does not reliably report missing RAM. This means that it is
6665 dangerous to say Y here if you are not absolutely sure that your
6666 board provides 64KB of local RAM.
6670 Support for non-IEEE1394 local ports
6671 CONFIG_IEEE1394_PCILYNX_PORTS
6672 This option enables driver code to access the RAM, ROM and AUX ports
6673 of the PCILynx through character devices in /dev. If you don't know
6674 what this is about then you won't need it.
6678 Adaptec AIC-5800 IEEE 1394 support
6679 CONFIG_IEEE1394_AIC5800
6680 Say Y here if you have a IEEE 1394 controller using the Adaptec
6681 AIC-5800 chip. All Adaptec host adapters (89xx series) use this
6682 chip, as well as miro's DV boards.
6684 If you want to compile this as a module ( = code which can be
6685 inserted in and removed from the running kernel whenever you want),
6686 say M here and read Documentation/modules.txt. The module will be
6689 OHCI (Open Host Controller Interface) support
6690 CONFIG_IEEE1394_OHCI1394
6691 Say Y here if you have a IEEE 1394 controller based on OHCI.
6692 The current driver was only tested with OHCI chipsets made
6693 by Texas Instruments. However, most third-party vendors use
6696 If you want to compile this as a module ( = code which can be
6697 inserted in and removed from the running kernel whenever you want),
6698 say M here and read Documentation/modules.txt. The module will be
6701 Raw IEEE 1394 I/O support
6702 CONFIG_IEEE1394_RAWIO
6703 Say Y here if you want support for the raw device. This is generally
6704 a good idea, so you should say Y here. The raw device enables
6705 direct communication of user programs with the IEEE 1394 bus and
6706 thus with the attached peripherals.
6708 If you want to compile this as a module ( = code which can be
6709 inserted in and removed from the running kernel whenever you want),
6710 say M here and read Documentation/modules.txt. The module will be
6713 Excessive debugging output
6714 CONFIG_IEEE1394_VERBOSEDEBUG
6715 If you say Y here, you will get very verbose debugging logs from the
6716 subsystem which includes a dump of the header of every sent and
6717 received packet. This can amount to a high amount of data collected
6718 in a very short time which is usually also saved to disk by the
6719 system logging daemons.
6721 Say Y if you really want or need the debugging output, everyone else
6724 Network device support?
6726 You can say N here if you don't intend to connect your Linux box to
6727 any other computer at all or if all your connections will be over a
6728 telephone line with a modem either via UUCP (UUCP is a protocol to
6729 forward mail and news between unix hosts over telephone lines; read
6730 the UUCP-HOWTO, available from
6731 http://www.linuxdoc.org/docs.html#howto ) or dialing up a shell
6732 account or a BBS, even using term (term is a program which gives you
6733 almost full Internet connectivity if you have a regular dial up
6734 shell account on some Internet connected Unix computer. Read
6735 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html ).
6737 You'll have to say Y if your computer contains a network card that
6738 you want to use under Linux (make sure you know its name because you
6739 will be asked for it and read the Ethernet-HOWTO (especially if you
6740 plan to use more than one network card under Linux)) or if you want
6741 to use SLIP (Serial Line Internet Protocol is the protocol used to
6742 send Internet traffic over telephone lines or null modem cables) or
6743 CSLIP (compressed SLIP) or PPP (Point to Point Protocol, a better
6744 and newer replacement for SLIP) or PLIP (Parallel Line Internet
6745 Protocol is mainly used to create a mini network by connecting the
6746 parallel ports of two local machines) or AX.25/KISS (protocol for
6747 sending Internet traffic over amateur radio links).
6749 Make sure to read the NET-3-HOWTO. Eventually, you will have to read
6750 Olaf Kirch's excellent and free book "Network Administrator's
6751 Guide", to be found in http://www.linuxdoc.org/docs.html#guide . If
6754 Dummy net driver support
6756 This is essentially a bit-bucket device (i.e. traffic you send to
6757 this device is consigned into oblivion) with a configurable IP
6758 address. It is most commonly used in order to make your currently
6759 inactive SLIP address seem like a real address for local programs.
6760 If you use SLIP or PPP, you might want to say Y here. Since this
6761 thing often comes in handy, the default is Y. It won't enlarge your
6762 kernel either. What a deal. Read about it in the Network
6763 Administrator's Guide, available from
6764 http://www.linuxdoc.org/docs.html#guide .
6766 If you want to compile this as a module ( = code which can be
6767 inserted in and removed from the running kernel whenever you want),
6768 say M here and read Documentation/modules.txt. The module will be
6769 called dummy.o. If you want to use more than one dummy device at a
6770 time, you need to compile this driver as a module. Instead of
6771 'dummy', the devices will then be called 'dummy0', 'dummy1' etc.
6773 Bonding driver support
6775 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
6776 Channels together. This is called 'Etherchannel' by Cisco,
6777 'Trunking' by Sun, and 'Bonding' in Linux.
6779 If you have two ethernet connections to some other computer, you can
6780 make them behave like one double speed connection using this driver.
6781 Naturally, this has to be supported at the other end as well, either
6782 with a similar Bonding Linux driver, a Cisco 5500 switch or a
6783 SunTrunking SunSoft driver.
6785 This is similar to the EQL driver, but it merges Ethernet segments
6786 instead of serial lines.
6788 If you want to compile this as a module ( = code which can be
6789 inserted in and removed from the running kernel whenever you want),
6790 say M here and read Documentation/modules.txt. The module will be
6793 SLIP (serial line) support
6795 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
6796 connect to your Internet service provider or to connect to some
6797 other local Unix box or if you want to configure your Linux box as a
6798 Slip/CSlip server for other people to dial in. SLIP (Serial Line
6799 Internet Protocol) is a protocol used to send Internet traffic over
6800 serial connections such as telephone lines or null modem cables;
6801 nowadays, the protocol PPP is more commonly used for this same
6804 Normally, your access provider has to support SLIP in order for you
6805 to be able to use it, but there is now a SLIP emulator called SLiRP
6806 around (available via FTP (user: anonymous) from
6807 ftp://metalab.unc.edu/pub/Linux/system/network/serial/ ) which
6808 allows you to use SLIP over a regular dial up shell connection. If
6809 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
6810 NET-3-HOWTO, available from
6811 http://www.linuxdoc.org/docs.html#howto , explains how to
6812 configure SLIP. Note that you don't need this option if you just
6813 want to run term (term is a program which gives you almost full
6814 Internet connectivity if you have a regular dial up shell account on
6815 some Internet connected Unix computer. Read
6816 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html ). SLIP
6817 support will enlarge your kernel by about 4 KB. If unsure, say N.
6819 If you want to compile this as a module ( = code which can be
6820 inserted in and removed from the running kernel whenever you want),
6821 say M here and read Documentation/modules.txt as well as
6822 Documentation/networking/net-modules.txt. The module will be called
6825 CSLIP compressed headers
6826 CONFIG_SLIP_COMPRESSED
6827 This protocol is faster than SLIP because it uses compression on the
6828 TCP/IP headers (not on the data itself), but it has to be supported
6829 on both ends. Ask your access provider if you are not sure and
6830 answer Y, just in case. You will still be able to use plain SLIP. If
6831 you plan to use SLiRP, the SLIP emulator (available from
6832 ftp://metalab.unc.edu/pub/Linux/system/network/serial/ ) which
6833 allows you to use SLIP over a regular dial up shell connection, you
6834 definitely want to say Y here. The NET-3-HOWTO, available from
6835 http://www.linuxdoc.org/docs.html#howto , explains how to configure
6836 CSLIP. This won't enlarge your kernel.
6838 Keepalive and linefill
6840 Adds additional capabilities to the SLIP driver to support the
6841 RELCOM line fill and keepalive monitoring. Ideal on poor quality
6844 Six bit SLIP encapsulation
6845 CONFIG_SLIP_MODE_SLIP6
6846 Just occasionally you may need to run IP over hostile serial
6847 networks that don't pass all control characters or are only seven
6848 bit. Saying Y here adds an extra mode you can use with SLIP:
6849 "slip6". In this mode, SLIP will only send normal ASCII symbols over
6850 the serial device. Naturally, this has to be supported at the other
6851 end of the link as well. It's good enough, for example, to run IP
6852 over the async ports of a Camtec JNT Pad. If unsure, say N.
6854 PPP (point-to-point protocol) support
6856 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
6857 the same purpose: sending Internet traffic over telephone (and other
6858 serial) lines. Ask your access provider if they support it, because
6859 otherwise you can't use it; most internet access providers these
6860 days support PPP rather than SLIP.
6862 To use PPP, you need an additional program called pppd as described
6863 in Documentation/networking/ppp.txt and in the PPP-HOWTO, available
6864 at http://www.linuxdoc.org/docs.html#howto . If you upgrade
6865 from an older kernel, you might need to upgrade pppd as well. The
6866 PPP option enlarges your kernel by about 16 KB.
6868 There are actually two versions of PPP: the traditional PPP for
6869 asynchronous lines, such as regular analog phone lines, and
6870 synchronous PPP which can be used over digital ISDN lines for
6871 example. If you want to use PPP over phone lines or other
6872 asynchronous serial lines, you need to say Y (or M) here and also to
6873 the next option, "PPP support for async serial ports". For PPP over
6874 synchronous lines, you should say Y (or M) here and to "Support
6875 synchronous PPP", below.
6877 This driver is also available as a module ( = code which can be
6878 inserted in and removed from the running kernel whenever you want).
6879 If you said Y to "Version information on all symbols" above, then
6880 you cannot compile the PPP driver into the kernel; you can then only
6881 compile it as a module. The module will be called ppp_generic.o. If
6882 you want to compile it as a module, say M here and read
6883 Documentation/modules.txt as well as
6884 Documentation/networking/net-modules.txt.
6886 PPP multilink support (EXPERIMENTAL)
6887 CONFIG_PPP_MULTILINK
6888 PPP multilink is a protocol (defined in RFC 1990) which allows you
6889 to combine several (logical or physical) lines into one logical PPP
6890 connection, so that you can utilize your full bandwidth.
6892 This has to be supported at the other end as well and you need a
6893 version of the pppd daemon which understands the multilink protocol.
6897 PPP support for async serial ports
6899 Say Y (or M) here if you want to be able to use PPP over standard
6900 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
6901 a modem (not a synchronous or ISDN modem) to contact your ISP, you
6904 This code is also available as a module (code which can be inserted
6905 into and removed from the running kernel). If you want to compile
6906 it as a module, say M here and read Documentation/modules.txt.
6910 PPP support for sync tty ports
6912 Say Y (or M) here if you want to be able to use PPP over synchronous
6913 (HDLC) tty devices, such as the SyncLink adapter. These devices
6914 are often used for high-speed leased lines like T1/E1.
6916 This code is also available as a module (code which can be inserted
6917 into and removed from the running kernel). If you want to compile
6918 it as a module, say M here and read Documentation/modules.txt.
6920 PPP Deflate compression
6922 Support for the Deflate compression method for PPP, which uses the
6923 Deflate algorithm (the same algorithm that gzip uses) to compress
6924 each PPP packet before it is sent over the wire. The machine at the
6925 other end of the PPP link (usually your ISP) has to support the
6926 Deflate compression method as well for this to be useful. Even if
6927 they don't support it, it is safe to say Y here.
6929 This code is also available as a module (code which can be inserted
6930 into and removed from the running kernel). If you want to compile
6931 it as a module, say M here and read Documentation/modules.txt.
6933 PPP BSD-Compress compression
6935 Support for the BSD-Compress compression method for PPP, which uses
6936 the LZW compression method to compress each PPP packet before it is
6937 sent over the wire. The machine at the other end of the PPP link
6938 (usually your ISP) has to support the BSD-Compress compression
6939 method as well for this to be useful. Even if they don't support it,
6940 it is safe to say Y here.
6942 The PPP Deflate compression method ("PPP Deflate compression",
6943 above) is preferable to BSD-Compress, because it compresses better
6946 Note that the BSD compression code will always be compiled as a
6947 module; it is called bsd_comp.o and will show up in the directory
6948 modules once you have said "make modules". If unsure, say N.
6950 PPP over Ethernet (EXPERIMENTAL)
6952 Support for PPP over Ethernet.
6954 This driver requires a specially patched pppd daemon. The patch to
6955 pppd, along with binaries of a patched pppd package can be found at:
6956 http://www.math.uwaterloo.ca/~mostrows
6958 Wireless LAN (non-hamradio)
6960 Support for wireless LANs and everything having to do with radio,
6961 but not with amateur radio or FM broadcasting.
6963 Saying Y here also enables the Wireless Extensions (creates
6964 /proc/net/wireless and enables ifconfig access). The Wireless
6965 Extension is a generic API allowing a driver to expose to the user
6966 space configuration and statistics specific to common Wireless LANs.
6967 The beauty of it is that a single set of tool can support all the
6968 variations of Wireless LANs, regardless of their type (as long as
6969 the driver supports Wireless Extension). Another advantage is that
6970 these parameters may be changed on the fly without restarting the
6971 driver (or Linux). If you wish to use Wireless Extensions with
6972 wireless PCMCIA (PC-) cards, you need to say Y here; you can fetch
6974 http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html .
6976 Some user-level drivers for scarab devices which don't require
6977 special kernel support are available from
6978 ftp://shadow.cabi.net/pub/Linux .
6980 STRIP (Metricom Starmode radio IP)
6982 Say Y if you have a Metricom radio and intend to use Starmode Radio
6983 IP. STRIP is a radio protocol developed for the MosquitoNet project
6984 (on the WWW at http://mosquitonet.stanford.edu/ ) to send Internet
6985 traffic using Metricom radios. Metricom radios are small, battery
6986 powered, 100kbit/sec packet radio transceivers, about the size and
6987 weight of a cellular telephone. (You may also have heard them called
6988 "Metricom modems" but we avoid the term "modem" because it misleads
6989 many people into thinking that you can plug a Metricom modem into a
6990 phone line and use it as a modem.)
6992 You can use STRIP on any Linux machine with a serial port, although
6993 it is obviously most useful for people with laptop computers. If you
6994 think you might get a Metricom radio in the future, there is no harm
6995 in saying Y to STRIP now, except that it makes the kernel a bit
6998 You can also compile this as a module ( = code which can be inserted
6999 in and removed from the running kernel whenever you want), say M
7000 here and read Documentation/modules.txt. The module will be called
7003 AT&T WaveLAN & DEC RoamAbout DS support
7005 The Lucent WaveLAN (formerly NCR and AT&T; or DEC RoamAbout DS) is
7006 a Radio LAN (wireless Ethernet-like Local Area Network) using the
7007 radio frequencies 900 MHz and 2.4 GHz.
7009 This driver support the ISA version of the WaveLAN card. A separate
7010 driver for the PCMCIA (PC-card) hardware is available in David
7011 Hinds' pcmcia-cs package (see the file Documentation/Changes for
7014 If you want to use an ISA WaveLAN card under Linux, say Y and read
7015 the Ethernet-HOWTO, available from
7016 http://www.linuxdoc.org/docs.html#howto . Some more specific
7017 information is contained in Documentation/networking/wavelan.txt and
7018 in the source code drivers/net/wavelan.p.h.
7020 You will also need the wireless tools package available from
7021 http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html .
7022 Please read the man pages contained therein.
7024 This driver is also available as a module ( = code which can be
7025 inserted in and removed from the running kernel whenever you want).
7026 The module will be called wavelan.o. If you want to compile it as a
7027 module, say M here and read Documentation/modules.txt as well as
7028 Documentation/networking/net-modules.txt.
7030 Aironet Arlan 655 & IC2200 DS support
7032 Aironet makes Arlan, a class of wireless LAN adapters. These use the
7033 www.Telxon.com chip, which is also used on several similar cards.
7034 This driver is tested on the 655 and IC2200 series cards. Look at
7035 http://www.ylenurme.ee/~elmer/655/ for the latest information.
7037 The driver is built as two modules, arlan and arlan-proc. The latter
7038 is the /proc interface and is not needed most of time.
7040 On some computers the card ends up in non-valid state after some
7041 time. Use a ping-reset script to clear it.
7043 Aironet 4500/4800 series adapters
7045 www.aironet.com (recently bought by Cisco) makes these 802.11 DS
7046 adapters. Driver by Elmer Joandi (elmer@ylenurme.ee).
7048 Say Y here if you have such an adapter, and then say Y below to
7049 the option that applies to your particular type of card (PCI, ISA,
7052 This driver is also available as a module ( = code which can be
7053 inserted in and removed from the running kernel whenever you want).
7054 The module will be called aironet4500_core.o. If you want to
7055 compile it as a module, say M here and read
7056 Documentation/modules.txt as well as
7057 Documentation/networking/net-modules.txt.
7059 quick config parameters:
7060 SSID=tsunami - "The Password"
7061 adhoc=1 there are no Access Points around
7062 master=1 Adhoc master (the one who creates network
7064 slave=1 Adhoc slave (btw, it is still forming own net
7065 sometimes, and has problems with firmware...
7066 change IbssJoinNetTimeout from /proc...)
7067 channel=1..? meaningful in adhoc mode
7069 If you have problems with screwing up card, both_bap_lock=1 is a
7070 conservative value (performance hit 15%).
7072 All other parameters can be set via the proc interface.
7074 Aironet 4500/4800 ISA/PCI/PNP/365 support
7075 CONFIG_AIRONET4500_NONCS
7076 If you have an ISA, PCI or PCMCIA Aironet 4500/4800 wireless LAN
7077 card, say Y here, and then also to the options below that apply
7080 This driver is also available as a module ( = code which can be
7081 inserted in and removed from the running kernel whenever you want).
7082 The module will be called aironet4500_card.o. If you want to
7083 compile it as a module, say M here and read
7084 Documentation/modules.txt
7086 Aironet 4500/4800 PNP support
7087 CONFIG_AIRONET4500_PNP
7088 If you have an ISA Aironet 4500/4800 card which you want to use in
7089 PNP (Plug and Play) mode, say Y here. This is the recommended mode
7090 for ISA cards. Remember however to enable the PNP jumper on the
7091 board if you say Y here.
7093 Aironet 4500/4800 PCI support
7094 CONFIG_AIRONET4500_PCI
7095 If you have an PCI Aironet 4500/4800 card, say Y here.
7097 Aironet 4500/4800 ISA broken support (EXPERIMENTAL)
7098 CONFIG_AIRONET4500_ISA
7099 If you have an ISA Aironet 4500/4800 card which you want to run in
7100 non-PNP mode, say Y here. This is not recommended and does not work
7101 correctly at this point. Say N.
7103 Aironet 4500/4800 I365 broken support (EXPERIMENTAL)
7104 CONFIG_AIRONET4500_I365
7105 If you have a PCMCIA Aironet 4500/4800 card which you want to use
7106 without the standard PCMCIA cardservices provided by the pcmcia-cs
7107 package, say Y here. This is not recommended, so say N.
7109 Aironet 4500/4800 PCMCIA support
7110 CONFIG_AIRONET4500_CS
7111 Say Y here if you have a PCMCIA Aironet 4500/4800 card which you
7112 want to use with the standard PCMCIA cardservices provided by the
7115 This driver is also available as a module ( = code which can be
7116 inserted in and removed from the running kernel whenever you want).
7117 The module will be called aironet4500_cs.o. If you want to
7118 compile it as a module, say M here and read
7119 Documentation/modules.txt.
7121 Aironet 4500/4800 PROC interface
7122 CONFIG_AIRONET4500_PROC
7123 If you say Y here (and to the "/proc file system" below), you will
7124 be able to configure your Aironet card via the
7125 /proc/sys/aironet4500 interface.
7127 Additional info: look in drivers/net/aironet4500_rids.c.
7129 This driver is also available as a module ( = code which can be
7130 inserted in and removed from the running kernel whenever you want).
7131 The module will be called aironet4500_proc.o. If you want to
7132 compile it as a module, say M here and read
7133 Documentation/modules.txt.
7135 NOTE: the proc interface uses a lot of memory, so it is recommended
7136 to compile it as a module and remove the module after
7139 LAPB over Ethernet driver
7141 This is a driver for a pseudo device (typically called /dev/lapb0)
7142 which allows you to open an LAPB point-to-point connection to some
7143 other computer on your Ethernet network. In order to do this, you
7144 need to say Y or M to the driver for your Ethernet card as well as
7145 to "LAPB Data Link Driver".
7147 If you want to compile this driver as a module ( = code which can be
7148 inserted in and removed from the running kernel whenever you want),
7149 say M here and read Documentation/modules.txt. The module will be
7150 called lapbether.o. If unsure, say N.
7154 This is a driver for sending and receiving X.25 frames over regular
7155 asynchronous serial lines such as telephone lines equipped with
7156 ordinary modems. Experts should note that this driver doesn't
7157 currently comply with the asynchronous HDLS framing protocols in
7158 CCITT recommendation X.25.
7160 If you want to compile this driver as a module ( = code which can be
7161 inserted in and removed from the running kernel whenever you want),
7162 say M here and read Documentation/modules.txt. The module will be
7163 called x25_asy.o. If unsure, say N.
7165 PCMCIA network device support
7167 Say Y if you would like to include support for any PCMCIA or CardBus
7168 network adapters, then say Y to the driver for your particular card
7169 below. PCMCIA- or PC-cards are credit-card size devices often used
7170 with laptops computers; CardBus is the newer and faster version of
7173 To use your PC-cards, you will need supporting software from David
7174 Hinds' pcmcia-cs package (see the file Documentation/Changes for
7175 location). You also want to check out the PCMCIA-HOWTO, available
7176 from http://www.linuxdoc.org/docs.html#howto .
7180 3Com 3c589 PCMCIA support
7182 Say Y here if you intend to attach a 3Com 3c589 or compatible PCMCIA
7183 (PC-card) Ethernet card to your computer.
7185 This driver is also available as a module ( = code which can be
7186 inserted in and removed from the running kernel whenever you want).
7187 The module will be called 3c589_cs.o. If you want to compile it as a
7188 module, say M here and read Documentation/modules.txt. If unsure,
7191 3Com 3c574 PCMCIA support
7193 Say Y here if you intend to attach a 3Com 3c574 or compatible PCMCIA
7194 (PC-card) Fast Ethernet card to your computer.
7196 This driver is also available as a module ( = code which can be
7197 inserted in and removed from the running kernel whenever you want).
7198 The module will be called 3c574_cs.o. If you want to compile it as a
7199 module, say M here and read Documentation/modules.txt. If unsure,
7202 Fujitsu FMV-J18x PCMCIA support
7203 CONFIG_PCMCIA_FMVJ18X
7204 Say Y here if you intend to attach a Fujitsu FMV-J18x or compatible
7205 PCMCIA (PC-card) Ethernet card to your computer.
7207 This driver is also available as a module ( = code which can be
7208 inserted in and removed from the running kernel whenever you want).
7209 The module will be called fmvj18x_cs.o. If you want to compile it as
7210 a module, say M here and read Documentation/modules.txt. If unsure,
7213 NE2000 compatible PCMCIA support
7215 Say Y here if you intend to attach an NE2000 compatible PCMCIA
7216 (PC-card) Ethernet or Fast Ethernet card to your computer.
7218 This driver is also available as a module ( = code which can be
7219 inserted in and removed from the running kernel whenever you want).
7220 The module will be called pcnet_cs.o. If you want to compile it as a
7221 module, say M here and read Documentation/modules.txt. If unsure,
7224 New Media PCMCIA support
7225 CONFIG_PCMCIA_NMCLAN
7226 Say Y here if you intend to attach a New Media Ethernet or LiveWire
7227 PCMCIA (PC-card) Ethernet card to your computer.
7229 This driver is also available as a module ( = code which can be
7230 inserted in and removed from the running kernel whenever you want).
7231 The module will be called nmclan_cs.o. If you want to compile it as
7232 a module, say M here and read Documentation/modules.txt. If unsure,
7235 SMC 91Cxx PCMCIA support
7236 CONFIG_PCMCIA_SMC91C92
7237 Say Y here if you intend to attach an SMC 91Cxx compatible PCMCIA
7238 (PC-card) Ethernet or Fast Ethernet card to your computer.
7240 This driver is also available as a module ( = code which can be
7241 inserted in and removed from the running kernel whenever you want).
7242 The module will be called smc91c92_cs.o. If you want to compile it
7243 as a module, say M here and read Documentation/modules.txt. If
7246 Xircom 16-bit PCMCIA support
7247 CONFIG_PCMCIA_XIRC2PS
7248 Say Y here if you intend to attach a Xircom 16-bit PCMCIA
7249 (PC-card) Ethernet or Fast Ethernet card to your computer.
7251 This driver is also available as a module ( = code which can be
7252 inserted in and removed from the running kernel whenever you want).
7253 The module will be called xirc2ps_cs.o. If you want to compile it as
7254 a module, say M here and read Documentation/modules.txt. If unsure,
7257 COM20020 ARCnet PCMCIA support
7258 CONFIG_ARCNET_COM20020_CS
7259 Say Y here if you intend to attach this type of ARCnet PCMCIA card
7262 This driver is also available as a module ( = code which can be
7263 inserted in and removed from the running kernel whenever you want).
7264 The module will be called com20020_cs.o. If you want to compile it
7265 as a module, say M here and read Documentation/modules.txt. If
7268 IBM PCMCIA Token Ring adapter support
7270 Say Y here if you intend to attach this type of Token Ring PCMCIA
7271 card to your computer. You then also need to say Y to "Token Ring
7274 This driver is also available as a module ( = code which can be
7275 inserted in and removed from the running kernel whenever you want).
7276 The module will be called ibmtr_cs.o. If you want to compile it
7277 as a module, say M here and read Documentation/modules.txt.
7279 Xircom Tulip-like CardBus support
7280 CONFIG_PCMCIA_XIRTULIP
7281 This driver is for the Digital "Tulip" Ethernet CardBus adapters.
7282 It should work with most DEC 21*4*-based chips/ethercards, as well
7283 as with work-alike chips from Lite-On (PNIC) and Macronix (MXIC) and
7286 This driver is also available as a module ( = code which can be
7287 inserted in and removed from the running kernel whenever you want).
7288 The module will be called xircom_tulip_cb.o. If you want to compile
7289 it as a module, say M here and read Documentation/modules.txt. If
7293 CONFIG_NET_PCMCIA_RADIO
7294 Say Y here if you would like to use a PCMCIA (PC-card) device to
7295 connect to a wireless local area network. Then say Y to the driver
7296 for your particular card below.
7298 To use your PC-cards, you will need supporting software from David
7299 Hinds' pcmcia-cs package (see the file Documentation/Changes for
7300 location). You also want to check out the PCMCIA-HOWTO, available
7301 from http://www.linuxdoc.org/docs.html#howto .
7303 Aviator/Raytheon 2.4MHz wireless support
7305 Say Y here if you intend to attach an Aviator/Raytheon PCMCIA
7306 (PC-card) wireless Ethernet networking card to your computer.
7307 Please read the file Documentation/networking/ray_cs.txt for
7310 This driver is also available as a module ( = code which can be
7311 inserted in and removed from the running kernel whenever you want).
7312 The module will be called ray_cs.o. If you want to compile it as a
7313 module, say M here and read Documentation/modules.txt. If unsure,
7316 Xircom Netwave AirSurfer wireless support
7317 CONFIG_PCMCIA_NETWAVE
7318 Say Y here if you intend to attach this type of PCMCIA (PC-card)
7319 wireless Ethernet networking card to your computer.
7321 This driver is also available as a module ( = code which can be
7322 inserted in and removed from the running kernel whenever you want).
7323 The module will be called netwave_cs.o. If you want to compile it as
7324 a module, say M here and read Documentation/modules.txt. If unsure,
7327 AT&T/Lucent Wavelan wireless support
7328 CONFIG_PCMCIA_WAVELAN
7329 Say Y here if you intend to attach an AT&T/Lucent Wavelan PCMCIA
7330 (PC-card) wireless Ethernet networking card to your computer. This
7331 driver is for the non-IEEE-802.11 Wavelan cards.
7333 This driver is also available as a module ( = code which can be
7334 inserted in and removed from the running kernel whenever you want).
7335 The module will be called wavelan_cs.o. If you want to compile it as
7336 a module, say M here and read Documentation/modules.txt. If unsure,
7339 PLIP (parallel port) support
7341 PLIP (Parallel Line Internet Protocol) is used to create a
7342 reasonably fast mini network consisting of two (or, rarely, more)
7343 local machines. A PLIP link from a Linux box is a popular means to
7344 install a Linux distribution on a machine which doesn't have a CDROM
7345 drive (a minimal system has to be transferred with floppies first).
7346 The kernels on both machines need to have this PLIP option enabled
7349 The PLIP driver has two modes, mode 0 and mode 1. The parallel ports
7350 (the connectors at the computers with 25 holes) are connected with
7351 "null printer" or "Turbo Laplink" cables which can transmit 4 bits
7352 at a time (mode 0) or with special PLIP cables, to be used on
7353 bidirectional parallel ports only, which can transmit 8 bits at a
7354 time (mode 1); you can find the wiring of these cables in
7355 Documentation/networking/PLIP.txt. The cables can be up to 15m long.
7356 Mode 0 works also if one of the machines runs DOS/Windows and has
7357 some PLIP software installed, e.g. the Crynwr PLIP packet driver
7358 (http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html ) and
7359 winsock or NCSA's telnet.
7361 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
7362 as the NET-3-HOWTO, both available from
7363 http://www.linuxdoc.org/docs.html#howto . Note that the PLIP
7364 protocol has been changed and this PLIP driver won't work together
7365 with the PLIP support in Linux versions 1.0.x. This option enlarges
7366 your kernel by about 8 KB.
7368 If you want to compile this as a module ( = code which can be
7369 inserted in and removed from the running kernel whenever you want),
7370 say M here and read Documentation/modules.txt as well as
7371 Documentation/networking/net-modules.txt. The module will be called
7372 plip.o. If unsure, say Y or M, in case you buy a laptop later.
7374 EQL (serial line load balancing) support
7376 If you have two serial connections to some other computer (this
7377 usually requires two modems and two telephone lines) and you use
7378 SLIP (the protocol for sending Internet traffic over telephone
7379 lines) or PPP (a better SLIP) on them, you can make them behave like
7380 one double speed connection using this driver. Naturally, this has
7381 to be supported at the other end as well, either with a similar EQL
7382 Linux driver or with a Livingston Portmaster 2e.
7384 Say Y if you want this and read Documentation/networking/eql.txt.
7385 You may also want to read section 6.2 of the NET-3-HOWTO, available
7386 from http://www.linuxdoc.org/docs.html#howto .
7388 This driver is also available as a module ( = code which can be
7389 inserted in and removed from the running kernel whenever you want).
7390 The module will be called eql.o. If you want to compile it as a
7391 module, say M here and read Documentation/modules.txt. If unsure,
7394 Universal TUN/TAP device driver.
7396 TUN/TAP provides packet reception and transmission for user space programs.
7397 It can be viewed as a simple Point-to-Point or Ethernet device, which
7398 instead of receiving packets from a physical media, receives them from
7399 user space program and instead of sending packets via physical media
7400 writes them to the user space program.
7402 When a program opens /dev/net/tun, driver creates and registers
7403 corresponding net device tunX or tapX. After a program closed above
7404 devices, driver will automatically delete tunXX or tapXX device and all
7405 routes corresponding to it.
7407 Please read Documentation/networking/tuntap.txt for more information.
7409 This driver is also available as a module ( = code which can be
7410 inserted in and removed from the running kernel whenever you want).
7411 The module will be called tun.o. If you want to compile it as a
7412 module, say M here and read Documentation/modules.txt.
7414 If you don't know what to use this for, you don't need it.
7416 Ethertap network tap (OBSOLETE)
7418 If you say Y here (and have said Y to "Kernel/User network link
7419 driver", above) and create a character special file /dev/tap0 with
7420 major number 36 and minor number 16 using mknod ("man mknod"), you
7421 will be able to have a user space program read and write raw
7422 Ethernet frames from/to that special file. tap0 can be configured
7423 with ifconfig and route like any other Ethernet device but it is not
7424 connected to any physical LAN; everything written by the user to
7425 /dev/tap0 is treated by the kernel as if it had come in from a LAN
7426 to the device tap0; everything the kernel wants to send out over the
7427 device tap0 can instead be read by the user from /dev/tap0: the user
7428 mode program replaces the LAN that would be attached to an ordinary
7429 Ethernet device. Please read the file
7430 Documentation/networking/ethertap.txt for more information.
7432 This driver is also available as a module ( = code which can be
7433 inserted in and removed from the running kernel whenever you want).
7434 The module will be called ethertap.o. If you want to compile it as a
7435 module, say M here and read Documentation/modules.txt.
7437 If you don't know what to use this for, you don't need it.
7439 Sealevel Systems 4021 support
7440 CONFIG_SEALEVEL_4021
7441 This is a driver for the Sealevel Systems ACB 56 serial I/O adapter.
7443 This driver can only be compiled as a module ( = code which can be
7444 inserted in and removed from the running kernel whenever you want).
7445 If you want to do that, say M here. The module will be called
7448 SyncLink HDLC/SYNCPPP support
7449 CONFIG_SYNCLINK_SYNCPPP
7450 Enables HDLC/SYNCPPP support for the SyncLink WAN driver.
7451 Normally the SyncLink WAN driver works with the main PPP
7452 driver (ppp.c) and pppd program. HDLC/SYNCPPP support allows use
7453 of the Cisco HDLC/PPP driver (syncppp.c).
7454 The SyncLink WAN driver (in character devices) must also be enabled.
7456 Frame Relay (DLCI) support
7458 This is support for the frame relay protocol; frame relay is a fast
7459 low-cost way to connect to a remote Internet access provider or to
7460 form a private wide area network. The one physical line from your
7461 box to the local "switch" (i.e. the entry point to the frame relay
7462 network, usually at the phone company) can carry several logical
7463 point-to-point connections to other computers connected to the frame
7464 relay network. For a general explanation of the protocol, check out
7465 http://www.frforum.com/ on the WWW. To use frame relay, you need
7466 supporting hardware (called FRAD) and certain programs from the
7467 net-tools package as explained in
7468 Documentation/networking/framerelay.txt.
7470 This driver is also available as a module ( = code which can be
7471 inserted in and removed from the running kernel whenever you want).
7472 The module will be called dlci.o. If you want to compile it as a
7473 module, say M here and read Documentation/modules.txt.
7477 This is the maximal number of logical point-to-point frame relay
7478 connections (the identifiers of which are called DCLIs) that
7479 the driver can handle. The default is probably fine.
7483 You can specify here how many logical point-to-point frame relay
7484 connections (the identifiers of which are called DCLIs) should be
7485 handled by each of your hardware frame relay access devices. Go with
7488 Sangoma S502A FRAD support
7490 Say Y here if you need a driver for the Sangoma S502A, S502E, and
7491 S508 Frame Relay Access Devices. These are multi-protocol cards, but
7492 only frame relay is supported by the driver at this time. Please
7493 read Documentation/framerelay.txt.
7495 This driver is also available as a module ( = code which can be
7496 inserted in and removed from the running kernel whenever you want).
7497 The module will be called sdla.o. If you want to compile it as a
7498 module, say M here and read Documentation/modules.txt.
7500 Acorn Econet/AUN protocols (EXPERIMENTAL)
7502 Econet is a fairly old and slow networking protocol mainly used by
7503 Acorn computers to access file and print servers. It uses native
7504 Econet network cards. AUN is an implementation of the higher level
7505 parts of Econet that runs over ordinary Ethernet connections, on
7506 top of the UDP packet protocol, which in turn runs on top of the
7507 Internet protocol IP.
7509 If you say Y here, you can choose with the next two options whether
7510 to send Econet/AUN traffic over a UDP Ethernet connection or over
7511 a native Econet network card.
7513 This driver is also available as a module ( = code which can be
7514 inserted in and removed from the running kernel whenever you want).
7515 The module will be called econet.o. If you want to compile it as a
7516 module, say M here and read Documentation/modules.txt.
7519 CONFIG_ECONET_AUNUDP
7520 Say Y here if you want to send Econet/AUN traffic over a UDP
7521 connection (UDP is a packet based protocol that runs on top of the
7522 Internet protocol IP) using an ordinary Ethernet network card.
7525 CONFIG_ECONET_NATIVE
7526 Say Y here if you have a native Econet network card installed in
7531 Wide Area Networks (WANs), such as X.25, frame relay and leased
7532 lines, are used to interconnect Local Area Networks (LANs) over vast
7533 distances with data transfer rates significantly higher than those
7534 achievable with commonly used asynchronous modem connections.
7535 Usually, a quite expensive external device called a `WAN router' is
7536 needed to connect to a WAN.
7538 As an alternative, WAN routing can be built into the Linux kernel.
7539 With relatively inexpensive WAN interface cards available on the
7540 market, a perfectly usable router can be built for less than half
7541 the price of an external router. If you have one of those cards and
7542 wish to use your Linux box as a WAN router, say Y here and also to
7543 the WAN driver for your card, below. You will then need the
7544 wan-tools package which is available from ftp://ftp.sangoma.com .
7545 Read Documentation/networking/wan-router.txt for more information.
7547 The WAN routing support is also available as a module called
7548 wanrouter.o ( = code which can be inserted in and removed from the
7549 running kernel whenever you want). If you want to compile it as a
7550 module, say M here and read Documentation/modules.txt.
7554 Fast switching (read help!)
7555 CONFIG_NET_FASTROUTE
7556 Saying Y here enables direct NIC-to-NIC (NIC = Network Interface
7557 Card) data transfers on the local network, which is fast.
7559 IMPORTANT NOTE: This option is NOT COMPATIBLE with "Network packet
7560 filtering" (CONFIG_NETFILTER). Say N here if you say Y there.
7562 However, it will work with all options in the "IP: advanced router"
7563 section (except for "IP: use TOS value as routing key" and
7564 "IP: use FWMARK value as routing key").
7566 At the moment, few devices support fast switching (tulip is one of
7567 them, a modified 8390 driver can be found at
7568 ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz ).
7572 Forwarding between high speed interfaces
7573 CONFIG_NET_HW_FLOWCONTROL
7574 This option enables NIC (Network Interface Card) hardware throttling
7575 during periods of extremal congestion. At the moment only a couple
7576 of device drivers support it (really only one -- tulip, a modified
7577 8390 driver can be found at
7578 ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz ).
7580 Really, this option is applicable to any machine attached to a fast
7581 enough network, and even a 10 Mb NIC is able to kill a not very slow
7582 box, such as a 120MHz Pentium.
7584 However, do not say Y here if you did not experience any serious
7587 QoS and/or fair queueing
7589 When the kernel has several packets to send out over a network
7590 device, it has to decide which ones to send first, which ones to
7591 delay, and which ones to drop. This is the job of the packet
7592 scheduler, and several different algorithms for how to do this
7593 "fairly" have been proposed.
7595 If you say N here, you will get the standard packet scheduler, which
7596 is a FIFO (first come, first served). If you say Y here, you will be
7597 able to choose from among several alternative algorithms which can
7598 then be attached to different network devices. This is useful for
7599 example if some of your network devices are real time devices that
7600 need a certain minimum data flow rate, or if you need to limit the
7601 maximum data flow rate for traffic which matches specified criteria.
7602 This code is considered to be experimental.
7604 To administer these schedulers, you'll need the user-level utilities
7605 from the package iproute2+tc at ftp://ftp.inr.ac.ru/ip-routing/ .
7606 That package also contains some documentation; for more, check out
7607 http://snafu.freedom.org/linux2.2/iproute-notes.html .
7609 This Quality of Service (QoS) support will enable you to use
7610 Differentiated Services (diffserv) and Resource Reservation Protocol
7611 (RSVP) on your Linux router if you also say Y to "QoS support",
7612 "Packet classifier API" and to some classifiers below. Documentation
7613 and software is at http://icawww1.epfl.ch/linux-diffserv/ .
7615 If you say Y here and to "/proc file system" below, you will be able
7616 to read status information about packet schedulers from the file
7619 The available schedulers are listed in the following questions; you
7620 can say Y to as many as you like. If unsure, say N now.
7622 CBQ packet scheduler
7624 Say Y here if you want to use the Class-Based Queueing (CBQ) packet
7625 scheduling algorithm for some of your network devices. This
7626 algorithm classifies the waiting packets into a tree-like hierarchy
7627 of classes; the leaves of this tree are in turn scheduled by
7628 separate algorithms (called "disciplines" in this context).
7630 See the top of net/sched/sch_cbq.c for references about the CBQ
7633 CBQ is a commonly used scheduler, so if you're unsure, you should
7634 say Y here. Then say Y to all the queueing algorithms below that you
7635 want to use as CBQ disciplines. Then say Y to "Packet classifier
7636 API" and say Y to all the classifiers you want to use; a classifier
7637 is a routine that allows you to sort your outgoing traffic into
7638 classes based on a certain criterion.
7640 This code is also available as a module called sch_cbq.o ( = code
7641 which can be inserted in and removed from the running kernel
7642 whenever you want). If you want to compile it as a module, say M
7643 here and read Documentation/modules.txt.
7645 CSZ packet scheduler
7647 Say Y here if you want to use the Clark-Shenker-Zhang (CSZ) packet
7648 scheduling algorithm for some of your network devices. At the
7649 moment, this is the only algorithm that can guarantee service for
7650 real-time applications (see the top of net/sched/sch_csz.c for
7651 details and references about the algorithm).
7653 Note: this scheduler is currently broken.
7655 This code is also available as a module called sch_csz.o ( = code
7656 which can be inserted in and removed from the running kernel
7657 whenever you want). If you want to compile it as a module, say M
7658 here and read Documentation/modules.txt.
7660 #ATM pseudo-scheduler
7666 The simplest PRIO pseudo scheduler
7668 Say Y here if you want to use an n-band priority queue packet
7669 "scheduler" for some of your network devices or as a leaf discipline
7670 for the CBQ scheduling algorithm. If unsure, say Y.
7672 This code is also available as a module called sch_prio.o ( = code
7673 which can be inserted in and removed from the running kernel
7674 whenever you want). If you want to compile it as a module, say M
7675 here and read Documentation/modules.txt.
7679 Say Y here if you want to use the Random Early Detection (RED)
7680 packet scheduling algorithm for some of your network devices (see
7681 the top of net/sched/sch_red.c for details and references about the
7684 This code is also available as a module called sch_red.o ( = code
7685 which can be inserted in and removed from the running kernel
7686 whenever you want). If you want to compile it as a module, say M
7687 here and read Documentation/modules.txt.
7691 Say Y here if you want to use the Stochastic Fairness Queueing (SFQ)
7692 packet scheduling algorithm for some of your network devices or as a
7693 leaf discipline for the CBQ scheduling algorithm (see the top of
7694 net/sched/sch_sfq.c for details and references about the SFQ
7697 This code is also available as a module called sch_sfq.o ( = code
7698 which can be inserted in and removed from the running kernel
7699 whenever you want). If you want to compile it as a module, say M
7700 here and read Documentation/modules.txt.
7704 Say Y here if you want to use the True Link Equalizer (TLE) packet
7705 scheduling algorithm for some of your network devices or as a leaf
7706 discipline for the CBQ scheduling algorithm. This queueing
7707 discipline allows the combination of several physical devices into
7708 one virtual device. (see the top of net/sched/sch_teql.c for
7711 This code is also available as a module called sch_teql.o ( = code
7712 which can be inserted in and removed from the running kernel
7713 whenever you want). If you want to compile it as a module, say M
7714 here and read Documentation/modules.txt.
7718 Say Y here if you want to use the Simple Token Bucket Filter (TBF)
7719 packet scheduling algorithm for some of your network devices or as a
7720 leaf discipline for the CBQ scheduling algorithm (see the top of
7721 net/sched/sch_tbf.c for a description of the TBF algorithm).
7723 This code is also available as a module called sch_tbf.o ( = code
7724 which can be inserted in and removed from the running kernel
7725 whenever you want). If you want to compile it as a module, say M
7726 here and read Documentation/modules.txt.
7729 #+tristate ' GRED queue' CONFIG_NET_SCH_GRED
7730 #+tristate ' Diffserv field marker' CONFIG_NET_SCH_DSMARK
7731 #+tristate ' Ingress Qdisc' CONFIG_NET_SCH_INGRESS
7735 Say Y here if you want to include Quality Of Service scheduling
7736 features, which means that you will be able to request certain
7737 rate-of-flow limits for your network devices.
7739 This Quality of Service (QoS) support will enable you to use
7740 Differentiated Services (diffserv) and Resource Reservation Protocol
7741 (RSVP) on your Linux router if you also say Y to "Packet classifier
7742 API" and to some classifiers below. Documentation and software is at
7743 http://icawww1.epfl.ch/linux-diffserv/ .
7745 Note that the answer to this question won't directly affect the
7746 kernel: saying N will just cause this configure script to skip all
7747 the questions about QoS support.
7750 CONFIG_NET_ESTIMATOR
7751 In order for Quality of Service scheduling to work, the current
7752 rate-of-flow for a network device has to be estimated; if you say Y
7753 here, the kernel will do just that.
7755 Packet classifier API
7757 The CBQ scheduling algorithm requires that network packets which are
7758 scheduled to be sent out over a network device be classified
7759 according to some criterion. If you say Y here, you will get a
7760 choice of several different packet classifiers with the following
7763 This will enable you to use Differentiated Services (diffserv) and
7764 Resource Reservation Protocol (RSVP) on your Linux router.
7765 Documentation and software is at
7766 http://icawww1.epfl.ch/linux-diffserv/ .
7769 #tristate ' TC index classifier' CONFIG_NET_CLS_TCINDEX
7771 Routing tables based classifier
7772 CONFIG_NET_CLS_ROUTE4
7773 If you say Y here, you will be able to classify outgoing packets
7774 according to the route table entry they matched. If unsure, say Y.
7776 This code is also available as a module called cls_route.o ( = code
7777 which can be inserted in and removed from the running kernel
7778 whenever you want). If you want to compile it as a module, say M
7779 here and read Documentation/modules.txt.
7781 Firewall based classifier
7783 If you say Y here, you will be able to classify outgoing packets
7784 according to firewall criteria you specified.
7786 This code is also available as a module called cls_fw.o ( = code
7787 which can be inserted in and removed from the running kernel
7788 whenever you want). If you want to compile it as a module, say M
7789 here and read Documentation/modules.txt.
7793 If you say Y here, you will be able to classify outgoing packets
7794 according to their destination address. If unsure, say Y.
7796 This code is also available as a module called cls_u32.o ( = code
7797 which can be inserted in and removed from the running kernel
7798 whenever you want). If you want to compile it as a module, say M
7799 here and read Documentation/modules.txt
7801 Special RSVP classifier
7803 The Resource Reservation Protocol (RSVP) permits end systems to
7804 request a minimum and maximum data flow rate for a connection; this
7805 is important for real time data such as streaming sound or video.
7807 Say Y here if you want to be able to classify outgoing packets based
7808 on their RSVP requests.
7810 This code is also available as a module called cls_rsvp.o ( = code
7811 which can be inserted in and removed from the running kernel
7812 whenever you want). If you want to compile it as a module, say M
7813 here and read Documentation/modules.txt
7815 Special RSVP classifier for IPv6
7816 CONFIG_NET_CLS_RSVP6
7817 The Resource Reservation Protocol (RSVP) permits end systems to
7818 request a minimum and maximum data flow rate for a connection; this
7819 is important for real time data such as streaming sound or video.
7821 Say Y here if you want to be able to classify outgoing packets based
7822 on their RSVP requests and you are using the new Internet Protocol
7823 IPv6 as opposed to the older and more common IPv4.
7825 This code is also available as a module called cls_rsvp6.o ( = code
7826 which can be inserted in and removed from the running kernel
7827 whenever you want). If you want to compile it as a module, say M
7828 here and read Documentation/modules.txt
7831 # Traffic policing (needed for in/egress)
7832 # CONFIG_NET_CLS_POLICE
7834 ### Some expert please fill these in
7837 Network code profiler
7839 If you say Y here and to "/proc file system support" below, some
7840 obscure and undocumented information about the network code's
7841 performance will be written to /proc/net/profile. If you don't know
7842 what it is about, you don't need it: say N.
7844 Wan interfaces support
7846 Wide Area Networks (WANs), such as X.25, frame relay and leased
7847 lines, are used to interconnect Local Area Networks (LANs) over vast
7848 distances with data transfer rates significantly higher than those
7849 achievable with commonly used asynchronous modem connections.
7850 Usually, a quite expensive external device called a `WAN router' is
7851 needed to connect to a WAN.
7853 As an alternative, a relatively inexpensive WAN interface card can
7854 allow your Linux box to directly connect to a WAN. If you have one
7855 of those cards and wish to use it under Linux, say Y here and also
7856 to the WAN driver for your card, below.
7860 Comtrol Hostess SV-11 support
7862 This is a network card for low speed synchronous serial links, at
7863 up to 256Kbps. It supports both PPP and Cisco HDLC.
7865 At this point, the driver can only be compiled as a module.
7867 COSA/SRP sync serial boards support
7869 This is a driver for COSA and SRP synchronous serial boards. These
7870 boards allow to connect synchronous serial devices (for example
7871 base-band modems, or any other device with the X.21, V.24, V.35 or
7872 V.36 interface) to your Linux box. The cards can work as the
7873 character device, synchronous PPP network device, or the Cisco HDLC
7876 To actually use the COSA or SRP board, you will need user-space
7877 utilities for downloading the firmware to the cards and to set them
7878 up. Look at the http://www.fi.muni.cz/~kas/cosa/ for more
7879 information about the cards (including the pointer to the user-space
7880 utilities). You can also read the comment at the top of the
7881 drivers/net/cosa.c for details about the cards and the driver
7884 The driver will be compiled as a module ( = code which can be
7885 inserted in and removed from the running kernel whenever you want).
7886 The module will be called cosa.o. For general information about
7887 modules read Documentation/modules.txt.
7889 Lan Media sync serial boards support
7891 This is a driver for the following Lan Media family of serial boards.
7893 LMC 1000 board allows you to connect synchronous serial devices (for
7894 example base-band modems, or any other device with the X.21, V.24,
7895 V.35 or V.36 interface) to your Linux box.
7897 LMC 1200 with on board DSU board allows you to connect your Linux
7898 box dirrectly to a T1 or E1 circuit.
7900 LMC 5200 board provides a HSSI interface capable of runnig up to
7901 52 mbits per second.
7903 LMC 5245 board connects directly to a T3 circuit saving the
7904 additional external hardware.
7906 To change setting such as syncPPP vs cisco HDLC or clock source you
7907 will need lmcctl. It it available at ftp.lanmedia.com.
7909 This code is also available as a module called lmc.o ( = code
7910 which can be inserted in and removed from the running kernel
7911 whenever you want). If you want to compile it as a module, say M
7912 here and read Documentation/modules.txt.
7914 Fibre Channel driver support
7916 Fibre Channel is a high speed serial protocol mainly used to connect
7917 large storage devices to the computer; it is compatible with and
7918 intended to replace SCSI.
7920 If you intend to use Fibre Channel, you need to have a Fibre channel
7921 adaptor card in your computer; say Y here and to the driver for your
7922 adaptor below. You also should have said Y to "SCSI support" and
7923 "SCSI generic support".
7925 Interphase 5526 Tachyon chipset based adaptor support
7927 Say Y here if you have a Fibre Channel adaptor of this kind.
7929 The driver is also available as a module ( = code which can be
7930 inserted in and removed from the running kernel whenever you want).
7931 The module will be called iph5526.o. For general information about
7932 modules read Documentation/modules.txt.
7934 Red Creek Hardware VPN (EXPERIMENTAL)
7936 This is a driver for hardware which provides a Virtual Private
7937 Network (VPN). Say Y if you have it.
7939 This code is also available as a module called rcpci.o ( = code
7940 which can be inserted in and removed from the running kernel
7941 whenever you want). If you want to compile it as a module, say M
7942 here and read Documentation/modules.txt.
7946 This is a driver for ISA SBNI12-xx cards which are low cost
7947 alternatives to leased line modems. Say Y if you want to insert
7948 the driver into the kernel or say M to compile it as a module (the
7949 module will be called sbni.o).
7951 You can find more information and last versions of drivers and
7952 utilities at http://www.granch.ru . If you have any question you
7953 can send email to sbni@granch.ru.
7958 CONFIG_WAN_ROUTER_DRIVERS
7959 If you have a WAN interface card and you want your Linux box to act
7960 as a WAN router, thereby connecting you Local Area Network to the
7961 outside world over the WAN connection, say Y here and then to the
7962 driver for your card below. In addition, you need to say Y to "Wan
7965 You will need the wan-tools package which is available from
7966 ftp://ftp.sangoma.com . Read Documentation/networking/wan-router.txt
7967 for more information.
7969 Note that the answer to this question won't directly affect the
7970 kernel: saying N will just cause this configure script to skip all
7971 the questions about WAN router drivers. If unsure, say N.
7973 Sangoma WANPIPE(tm) multiprotocol cards
7974 CONFIG_VENDOR_SANGOMA
7975 WANPIPE from Sangoma Technologies Inc. (http://www.sangoma.com ) is
7976 a family of intelligent multiprotocol WAN adapters with data
7977 transfer rates up to T1 (1.544 Mbps). They are also known as
7978 Synchronous Data Link Adapters (SDLA) and designated S502E(A), S503
7979 or S508. These cards support the X.25, Frame Relay, and PPP
7980 protocols. If you have one or more of these cards, say Y to this
7981 option; you may then also want to read the file
7982 Documentation/networking/wanpipe.txt. The next questions will ask
7983 you about the protocols you want the driver to support.
7985 The driver will be compiled as a module ( = code which can be
7986 inserted in and removed from the running kernel whenever you want).
7987 The module will be called wanpipe.o. For general information about
7988 modules read Documentation/modules.txt.
7990 Maximum number of cards
7991 CONFIG_WANPIPE_CARDS
7992 Enter number of WANPIPE adapters installed in your machine. The
7993 driver can support up to 8 cards. You may enter more than you
7994 actually have if you plan to add more cards in the future without
7995 re-compiling the driver, but remember that in this case you'll waste
7996 some kernel memory (about 1K per card).
7998 WANPIPE Cisco HDLC support
7999 CONFIG_WANPIPE_CHDLC
8000 Say Y to this option if you are planning to connect a WANPIPE card
8001 to a connection which uses the synchronous Cisco HDLC (High-level
8002 Data Link Control) protocol. This protocol is often used on
8003 high-speed leased lines like T1/E1.
8005 WANPIPE X.25 support
8007 Say Y to this option if you are planning to connect a WANPIPE card
8008 to an X.25 network. You should then also have said Y to "CCITT X.25
8009 Packet Layer" and "LAPB Data Link Driver", above. If you say N, the
8010 X.25 support will not be included in the driver (saves about 16 KB
8013 WANPIPE Frame Relay support
8015 Say Y to this option if you are planning to connect a WANPIPE card
8016 to a frame relay network. You should then also have said Y to "Frame
8017 Relay (DLCI) support", above. If you say N, the frame relay
8018 support will not be included in the driver (saves about 16 KB of
8023 Say Y to this option if you are planning to connect a WANPIPE card
8024 to a leased line using Point-to-Point protocol (PPP). You should
8025 then also have said Y to "PPP (point-to-point) support", above. If
8026 you say N, the PPP support will not be included in the driver (saves
8027 about 16 KB of kernel memory).
8029 MultiGate/COMX support
8031 Say Y if you want to use any board from the MultiGate (COMX) family.
8032 These boards are synchronous serial adapters for the PC,
8033 manufactured by ITConsult-Pro Co, Hungary.
8035 Read linux/Documentation/networking/comx.txt for help on configuring
8036 and using COMX interfaces. Further info on these cards can be found
8037 at http://www.itc.hu or <info@itc.hu>.
8039 You must say Y to "/proc file system support" (CONFIG_PROC_FS) to
8042 If you want to compile this as a module, say M and read
8043 Documentation/modules.txt. The module will be called comx.o.
8045 COMX/CMX/HiCOMX board support
8047 Hardware driver for the 'CMX', 'COMX' and 'HiCOMX' boards from the
8048 MultiGate family. Say Y if you have one of these.
8050 You will need additional firmware to use these cards, which are
8051 downloadable from ftp://ftp.itc.hu/.
8053 If you want to compile this as a module, say M and read
8054 Documentation/modules.txt. The module will be called comx-hw-comx.o.
8056 LoCOMX board support
8057 CONFIG_COMX_HW_LOCOMX
8058 Hardware driver for the 'LoCOMX' board from the MultiGate family.
8059 Say Y if you have a board like this.
8061 If you want to compile this as a module, say M and read
8062 Documentation/modules.txt. The module will be called
8065 MixCOM board support
8066 CONFIG_COMX_HW_MIXCOM
8067 Hardware driver for the 'MixCOM' board from the MultiGate family.
8068 Say Y if you have a board like this.
8070 If you want to use the watchdog device on this card, you should
8071 select it in the Watchdog Cards section of the Character Devices
8072 configuration. The ISDN interface of this card is Teles 16.3
8073 compatible, you should enable it in the ISDN configuration menu. The
8074 driver for the flash ROM of this card is available separately on
8077 If you want to compile this as a module, say M and read
8078 Documentation/modules.txt. The module will be called
8083 Hardware driver for the TCO timer built into the Intel i810 and i815
8084 chipset family. The TCO (Total Cost of Ownership) timer is a watchdog
8085 timer that will reboot the machine after it's second expiration. The
8086 expiration time can be configured by commandline argument
8087 "i810_margin=<n>" where <n> is the counter initial value. It is
8088 decremented every 0.6 secs, the default is 50 which gives a timeout
8089 of 30 seconds and one minute until reset.
8091 On some motherboards the driver may fail to reset the chipset's
8092 NO_REBOOT flag which prevents the watchdog from rebooting the machine.
8093 If this is the case you will get a kernel message like
8094 "i810tco init: failed to reset NO_REBOOT flag".
8096 If you want to compile this as a module, say M and read
8097 Documentation/modules.txt. The module will be called
8100 MultiGate Cisco-HDLC and synchronous PPP protocol support
8101 CONFIG_COMX_PROTO_PPP
8102 Cisco-HDLC and synchronous PPP protocol driver for all MultiGate
8103 boards. Say Y if you want to use either protocol on your MultiGate
8106 If you want to compile this as a module, say M and read
8107 Documentation/modules.txt. The module will be called
8110 MultiGate LAPB protocol support
8111 CONFIG_COMX_PROTO_LAPB
8112 LAPB protocol driver for all MultiGate boards. Say Y if you
8113 want to use this protocol on your MultiGate boards.
8115 If you want to compile this as a module, say M and read
8116 Documentation/modules.txt. The module will be called
8119 MultiGate Frame Relay protocol support
8120 CONFIG_COMX_PROTO_FR
8121 Frame Relay protocol driver for all MultiGate boards. Say Y if you
8122 want to use this protocol on your MultiGate boards.
8124 If you want to compile this as a module, say M and read
8125 Documentation/modules.txt. The module will be called
8128 Cyclom 2X(tm) multiprotocol cards (EXPERIMENTAL)
8129 CONFIG_CYCLADES_SYNC
8130 Cyclom 2X from Cyclades Corporation (http://www.cyclades.com and
8131 http://www.cyclades.com.br) is an intelligent multiprotocol WAN
8132 adapter with data transfer rates up to 512 Kbps. These cards support
8133 the X.25 and SNA related protocols. If you have one or more of these
8134 cards, say Y to this option. The next questions will ask you about
8135 the protocols you want the driver to support (for now only X.25 is
8138 While no documentation is available at this time please grab the
8139 wanconfig tarball in http://www.conectiva.com.br/~acme/cycsyn-devel
8140 (with minor changes to make it compile with the current wanrouter
8141 include files; efforts are being made to use the original package
8142 available at ftp://ftp.sangoma.com ).
8144 Feel free to contact me or the cycsyn-devel mailing list at
8145 acme@conectiva.com.br and cycsyn-devel@bazar.conectiva.com.br for
8146 additional details, I hope to have documentation available as soon
8147 as possible. (Cyclades Brazil is writing the Documentation).
8149 The driver will be compiled as a module ( = code which can be
8150 inserted in and removed from the running kernel whenever you want).
8151 The module will be called cyclomx.o. For general information about
8152 modules read Documentation/modules.txt.
8154 Cyclom 2X X.25 support
8156 Say Y to this option if you are planning to connect a Cyclom 2X card
8159 If you say N, the X.25 support will not be included in the driver
8160 (saves about 11 KB of kernel memory).
8162 Ethernet (10 or 100Mbit)
8164 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
8165 type of Local Area Network (LAN) in universities and companies.
8167 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
8168 coaxial cable, linking computers in a chain), 10BASE-T or twisted
8169 pair (10 Mbps over twisted pair cable, linking computers to central
8170 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
8171 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
8172 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
8173 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
8174 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
8175 Ethernet (1 Gbps over optical fiber or short copper links).
8177 If your Linux machine will be connected to an Ethernet and you have
8178 an Ethernet network interface card (NIC) installed in your computer,
8179 say Y here and read the Ethernet-HOWTO, available from
8180 http://www.linuxdoc.org/docs.html#howto . You will then also have
8181 to say Y to the driver for your particular NIC.
8183 Note that the answer to this question won't directly affect the
8184 kernel: saying N will just cause this configure script to skip all
8185 the questions about Ethernet network cards. If unsure, say N.
8187 Western Digital/SMC cards
8188 CONFIG_NET_VENDOR_SMC
8189 If you have a network (Ethernet) card belonging to this class, say Y
8190 and read the Ethernet-HOWTO, available from
8191 http://www.linuxdoc.org/docs.html#howto .
8193 Note that the answer to this question doesn't directly affect the
8194 kernel: saying N will just cause this configure script to skip all
8195 the questions about Western Digital cards. If you say Y, you will be
8196 asked for your specific card in the following questions.
8200 If you have a network (Ethernet) card of this type, say Y and read
8201 the Ethernet-HOWTO, available from
8202 http://www.linuxdoc.org/docs.html#howto .
8204 This driver is also available as a module ( = code which can be
8205 inserted in and removed from the running kernel whenever you want).
8206 The module will be called wd.o. If you want to compile it as a
8207 module, say M here and read Documentation/modules.txt as well as
8208 Documentation/networking/net-modules.txt.
8210 SMC Ultra MCA support
8212 If you have a network (Ethernet) card of this type and are running
8213 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
8214 available from http://www.linuxdoc.org/docs.html#howto .
8216 This driver is also available as a module ( = code which can be
8217 inserted in and removed from the running kernel whenever you want).
8218 The module will be called smc-mca.o. If you want to compile it as a
8219 module, say M here and read Documentation/modules.txt as well as
8220 Documentation/networking/net-modules.txt.
8224 If you have a network (Ethernet) card of this type, say Y and read
8225 the Ethernet-HOWTO, available from
8226 http://www.linuxdoc.org/docs.html#howto .
8228 Important: There have been many reports that, with some motherboards
8229 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
8230 such as some BusLogic models) causes corruption problems with many
8231 operating systems. The Linux smc-ultra driver has a work-around for
8232 this but keep it in mind if you have such a SCSI card and have
8235 This driver is also available as a module ( = code which can be
8236 inserted in and removed from the running kernel whenever you want).
8237 The module will be called smc-ultra.o. If you want to compile it as
8238 a module, say M here and read Documentation/modules.txt as well as
8239 Documentation/networking/net-modules.txt.
8241 SMC Ultra32 EISA support
8243 If you have a network (Ethernet) card of this type, say Y and read
8244 the Ethernet-HOWTO, available from
8245 http://www.linuxdoc.org/docs.html#howto .
8247 This driver is also available as a module ( = code which can be
8248 inserted in and removed from the running kernel whenever you want).
8249 The module will be called smc-ultra32.o. If you want to compile it
8250 as a module, say M here and read Documentation/modules.txt as well
8251 as Documentation/networking/net-modules.txt.
8255 This is support for the SMC9xxx based Ethernet cards. Choose this
8256 option if you have a DELL laptop with the docking station, or
8257 another SMC9192/9194 based chipset. Say Y if you want it compiled
8258 into the kernel, and read the file
8259 Documentation/networking/smc9.txt and the Ethernet-HOWTO, available
8260 from http://www.linuxdoc.org/docs.html#howto .
8262 This driver is also available as a module ( = code which can be
8263 inserted in and removed from the running kernel whenever you
8264 want). The module will be called smc9194.o. If you want to compile
8265 it as a module, say M here and read Documentation/modules.txt as
8266 well as Documentation/networking/net-modules.txt.
8270 This driver is for NE2000 compatible PCI cards. It will not work
8271 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
8272 support" below). If you have a PCI NE2000 network (Ethernet) card,
8273 say Y and read the Ethernet-HOWTO, available from
8274 http://www.linuxdoc.org/docs.html#howto .
8276 This driver also works for the following NE2000 clone cards:
8277 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
8278 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
8279 Holtek HT80232 Holtek HT80229
8281 This driver is also available as a module ( = code which can be
8282 inserted in and removed from the running kernel whenever you want).
8283 The module will be called ne2k-pci.o. If you want to compile it as a
8284 module, say M here and read Documentation/modules.txt as well as
8285 Documentation/networking/net-modules.txt.
8287 Racal-Interlan (Micom) NI cards
8288 CONFIG_NET_VENDOR_RACAL
8289 If you have a network (Ethernet) card belonging to this class, such
8290 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
8291 available from http://www.linuxdoc.org/docs.html#howto .
8293 Note that the answer to this question doesn't directly affect the
8294 kernel: saying N will just cause this configure script to skip all
8295 the questions about NI cards. If you say Y, you will be asked for
8296 your specific card in the following questions.
8298 NI5010 support (EXPERIMENTAL)
8300 If you have a network (Ethernet) card of this type, say Y and read
8301 the Ethernet-HOWTO, available from
8302 http://www.linuxdoc.org/docs.html#howto . Note that this is still
8305 This driver is also available as a module ( = code which can be
8306 inserted in and removed from the running kernel whenever you want).
8307 The module will be called ni5010.o. If you want to compile it as a
8308 module, say M here and read Documentation/modules.txt as well as
8309 Documentation/networking/net-modules.txt.
8313 If you have a network (Ethernet) card of this type, say Y and read
8314 the Ethernet-HOWTO, available from
8315 http://www.linuxdoc.org/docs.html#howto .
8317 This driver is also available as a module ( = code which can be
8318 inserted in and removed from the running kernel whenever you want).
8319 The module will be called ni52.o. If you want to compile it as a
8320 module, say M here and read Documentation/modules.txt as well as
8321 Documentation/networking/net-modules.txt.
8325 If you have a network (Ethernet) card of this type, say Y and read
8326 the Ethernet-HOWTO, available from
8327 http://www.linuxdoc.org/docs.html#howto .
8329 This driver is also available as a module ( = code which can be
8330 inserted in and removed from the running kernel whenever you want).
8331 The module will be called ni65.o. If you want to compile it as a
8332 module, say M here and read Documentation/modules.txt as well as
8333 Documentation/networking/net-modules.txt.
8335 RealTek 8129 (not 8019/8029/8139!) support (EXPERIMENTAL)
8337 This is NOT for RTL-8139 cards. Instead, select the 8139too driver
8339 This is a driver for the Fast Ethernet PCI network cards based on
8340 the RTL8129 chip. If you have one of those, say Y and
8341 read the Ethernet-HOWTO, available from
8342 http://www.linuxdoc.org/docs.html#howto .
8344 Note: the 8029 is a NE2000 PCI clone, you can use the NE2K-PCI driver.
8346 If you want to compile this driver as a module ( = code which can be
8347 inserted in and removed from the running kernel whenever you want),
8348 say M here and read Documentation/modules.txt. This is recommended.
8349 The module will be called rtl8129.o.
8351 RealTek RTL-8139 PCI Fast Ethernet Adapter support
8353 This is a driver for the Fast Ethernet PCI network cards based on
8354 the RTL8139 chips. If you have one of those, say Y and read
8355 Documentation/networking/8139too.txt as well as the Ethernet-HOWTO,
8356 available from http://www.linuxdoc.org/docs.html#howto .
8358 If you want to compile this driver as a module ( = code which can be
8359 inserted in and removed from the running kernel whenever you want),
8360 say M here and read Documentation/modules.txt. This is recommended.
8361 The module will be called 8139too.o.
8363 SiS 900 PCI Fast Ethernet Adapter support
8365 This is a driver for the Fast Ethernet PCI network cards based on
8366 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
8367 SiS 630 and SiS 540 chipsets. If you have one of those, say Y and
8368 read the Ethernet-HOWTO, available at
8369 http://www.linuxdoc.org/docs.html#howto . Please read
8370 Documentation/networking/sis900.txt and comments at the beginning of
8371 drivers/net/sis900.c for more information.
8373 This driver also supports AMD 79C901 HomePNA so that you can use
8374 your phone line as a network cable.
8376 If you want to compile this driver as a module ( = code which can be
8377 inserted in and removed from the running kernel whenever you want),
8378 say M here and read Documentation/modules.txt. This is recommended.
8379 The module will be called sis900.o.
8381 Packet Engines Yellowfin Gigabit-NIC support
8383 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
8384 adapter. This adapter is used by the Beowulf Linux cluster project.
8385 See http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html for
8386 more information about this driver in particular and Beowulf in
8389 If you want to compile this driver as a module ( = code which can be
8390 inserted in and removed from the running kernel whenever you want),
8391 say M here and read Documentation/modules.txt. This is recommended.
8392 The module will be called yellowfin.o.
8394 General Instruments Surfboard 1000
8396 This is a driver for the General Instrument (also known as
8397 NextLevel) SURFboard 1000 internal
8398 cable modem. This is an ISA card which is used by a number of cable
8399 TV companies to provide cable modem access. It's a one-way
8400 downstream-only cable modem, meaning that your upstream net link is
8401 provided by your regular phone modem.
8403 At present this driver only compiles as a module, so say M here if
8404 you have this card. The module will be called sb1000.o. Then read
8405 Documentation/networking/README.sb1000 for information on how to use
8406 this module, as it needs special ppp scripts for establishing a
8407 connection. Further documentation and the necessary scripts can be
8410 http://www.jacksonville.net/~fventuri/
8411 http://home.adelphia.net/~siglercm/sb1000.html
8412 http://linuxpower.cx/~cable/
8414 If you don't have this card, of course say N.
8416 Adaptec Starfire support (EXPERIMENTAL)
8417 CONFIG_ADAPTEC_STARFIRE
8418 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
8419 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
8420 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
8423 If you want to compile this driver as a module ( = code which can be
8424 inserted in and removed from the running kernel whenever you want),
8425 say M here and read Documentation/modules.txt. This is recommended.
8426 The module will be called starfile.o.
8428 Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support
8430 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
8431 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
8432 adapter. The driver allows for using the Jumbo Frame option (9000
8433 bytes/frame) however it requires that your switches can handle this
8434 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
8437 If you want to compile this driver as a module ( = code which can be
8438 inserted in and removed from the running kernel whenever you want),
8439 say M here and read Documentation/modules.txt. This is recommended.
8440 The module will be called acenic.o.
8442 Omit support for older Tigon I based AceNICs
8443 CONFIG_ACENIC_OMIT_TIGON_I
8444 Say Y here if you only have Tigon II based AceNICs and want to leave
8445 out support for the older Tigon I based cards which are no longer
8446 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
8447 version)). This will reduce the size of the driver object by
8448 app. 100KB. If you are not sure whether your card is a Tigon I or a
8449 Tigon II, say N here.
8451 The safe and default value for this is N.
8453 SysKonnect SK-98xx support
8455 Say Y here if you have a SysKonnect SK-98xx Gigabit Ethernet Server
8456 Adapter. The following adapters are supported by this driver:
8457 - SK-9841 (single link 1000Base-LX)
8458 - SK-9842 (dual link 1000Base-LX)
8459 - SK-9843 (single link 1000Base-SX)
8460 - SK-9844 (dual link 1000Base-SX)
8461 - SK-9821 (single link 1000Base-T)
8462 - SK-9822 (dual link 1000Base-T)
8463 - SK-9861 (single link Volition connector)
8464 - SK-9862 (dual link Volition connector)
8465 The driver also supports the following adapters from Allied Telesyn:
8468 The dual link adapters support a link-failover feature.
8469 Read Documentation/networking/sk98lin.txt for information about
8470 optional driver parameters.
8471 Questions concerning this driver may be addressed to:
8474 If you want to compile this driver as a module ( = code which can be
8475 inserted in and removed from the running kernel whenever you want),
8476 say M here and read Documentation/modules.txt. This is recommended.
8477 The module will be called sk98lin.o.
8479 MyriCOM Gigabit Ethernet support
8481 This driver supports MyriCOM Sbus gigabit ethernet cards.
8483 If you want to compile this driver as a module ( = code which can be
8484 inserted in and removed from the running kernel whenever you want),
8485 say M here and read Documentation/modules.txt. This is recommended.
8486 The module will be called myri_sbus.o.
8488 AMD LANCE and PCnet (AT1500 and NE2100) support
8490 If you have a network (Ethernet) card of this type, say Y and read
8491 the Ethernet-HOWTO, available from
8492 http://www.linuxdoc.org/docs.html#howto . Some LinkSys cards are
8495 If you want to compile this driver as a module ( = code which can be
8496 inserted in and removed from the running kernel whenever you want),
8497 say M here and read Documentation/modules.txt. This is recommended.
8498 The module will be called lance.o.
8502 If you have a network (Ethernet) card of this type, say Y and read
8503 the Ethernet-HOWTO, available from
8504 http://www.linuxdoc.org/docs.html#howto .
8507 CONFIG_NET_VENDOR_3COM
8508 If you have a network (Ethernet) card belonging to this class, say Y
8509 and read the Ethernet-HOWTO, available from
8510 http://www.linuxdoc.org/docs.html#howto .
8512 Note that the answer to this question doesn't directly affect the
8513 kernel: saying N will just cause this configure script to skip all
8514 the questions about 3COM cards. If you say Y, you will be asked for
8515 your specific card in the following questions.
8519 If you have a network (Ethernet) card of this type, say Y and read
8520 the Ethernet-HOWTO, available from
8521 http://www.linuxdoc.org/docs.html#howto . Also, consider buying a
8522 new card, since the 3c501 is slow, broken, and obsolete: you will
8523 have problems. Some people suggest to ping ("man ping") a nearby
8524 machine every minute ("man cron") when using this card.
8526 This driver is also available as a module ( = code which can be
8527 inserted in and removed from the running kernel whenever you want).
8528 The module will be called 3c501.o. If you want to compile it as a
8529 module, say M here and read Documentation/modules.txt as well as
8530 Documentation/networking/net-modules.txt.
8534 If you have a network (Ethernet) card of this type, say Y and read
8535 the Ethernet-HOWTO, available from
8536 http://www.linuxdoc.org/docs.html#howto .
8538 This driver is also available as a module ( = code which can be
8539 inserted in and removed from the running kernel whenever you want).
8540 The module will be called 3c503.o. If you want to compile it as a
8541 module, say M here and read Documentation/modules.txt as well as
8542 Documentation/networking/net-modules.txt.
8546 Information about this network (Ethernet) card can be found in
8547 Documentation/networking/3c505.txt. If you have a card of this type,
8548 say Y and read the Ethernet-HOWTO, available from
8549 http://www.linuxdoc.org/docs.html#howto .
8551 If you want to compile this as a module ( = code which can be
8552 inserted in and removed from the running kernel whenever you want),
8553 say M here and read Documentation/modules.txt as well as
8554 Documentation/networking/net-modules.txt. The module will be called
8557 3c507 support (EXPERIMENTAL)
8559 If you have a network (Ethernet) card of this type, say Y and read
8560 the Ethernet-HOWTO, available from
8561 http://www.linuxdoc.org/docs.html#howto .
8563 This driver is also available as a module ( = code which can be
8564 inserted in and removed from the running kernel whenever you want).
8565 The module will be called 3c507.o. If you want to compile it as a
8566 module, say M here and read Documentation/modules.txt as well as
8567 Documentation/networking/net-modules.txt.
8571 If you have a network (Ethernet) card of this type, say Y and read
8572 the Ethernet-HOWTO, available from
8573 http://www.linuxdoc.org/docs.html#howto .
8575 This driver is also available as a module ( = code which can be
8576 inserted in and removed from the running kernel whenever you want).
8577 The module will be called 3c523.o. If you want to compile it as a
8578 module, say M here and read Documentation/modules.txt as well as
8579 Documentation/networking/net-modules.txt.
8583 If you have a network (Ethernet) card of this type, say Y and read
8584 the Ethernet-HOWTO, available from
8585 http://www.linuxdoc.org/docs.html#howto .
8587 This driver is also available as a module ( = code which can be
8588 inserted in and removed from the running kernel whenever you want).
8589 The module will be called 3c527.o. If you want to compile it as a
8590 module, say M here and read Documentation/modules.txt as well as
8591 Documentation/networking/net-modules.txt.
8595 If you have a network (Ethernet) card belonging to the 3Com
8596 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
8597 from http://www.linuxdoc.org/docs.html#howto .
8599 If your card is not working you may need to use the DOS
8600 setup disk to disable Plug & Play mode, and to select the default
8603 If you want to compile this as a module ( = code which can be
8604 inserted in and removed from the running kernel whenever you want),
8605 say M here and read Documentation/modules.txt as well as
8606 Documentation/networking/net-modules.txt. The module will be called
8609 3c515 ISA Fast EtherLink
8611 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
8612 network card, say Y and read the Ethernet-HOWTO, available from
8613 http://www.linuxdoc.org/docs.html#howto .
8615 If you want to compile this as a module ( = code which can be
8616 inserted in and removed from the running kernel whenever you want),
8617 say M here and read Documentation/modules.txt as well as
8618 Documentation/networking/net-modules.txt. The module will be called
8621 3c59x/3c90x/3c575_Cardbus series "Vortex/Boomerang/Cyclone" support
8623 This option enables driver support for a large number of 10mbps and
8624 10/100mbps EISA, PCI and PCMCIA 3Com network cards:
8626 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
8627 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
8628 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
8629 "Tornado" (3c905) PCI
8630 "Hurricane" (3c555/3cSOHO) PCI
8632 If you have such a card, say Y and read the Ethernet-HOWTO, available
8633 from http://www.linuxdoc.org/docs.html#howto . More specific
8634 information is in Documentation/networking/vortex.txt and in the
8635 comments at the beginning of drivers/net/3c59x.c.
8637 If you want to compile this as a module ( = code which can be
8638 inserted in and removed from the running kernel whenever you want),
8639 say M here and read Documentation/modules.txt as well as
8640 Documentation/networking/net-modules.txt.
8644 If your network (Ethernet) card hasn't been mentioned yet and its
8645 bus system (that's the way the cards talks to the other components
8646 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
8647 Make sure you know the name of your card. Read the Ethernet-HOWTO,
8648 available from http://www.linuxdoc.org/docs.html#howto .
8652 Note that the answer to this question doesn't directly affect the
8653 kernel: saying N will just cause this configure script to skip all
8654 the remaining ISA network card questions. If you say Y, you will be
8655 asked for your specific card in the following questions.
8657 Generic ARCnet support
8659 If you have a network card of this type, say Y and check out the
8660 (arguably) beautiful poetry in Documentation/networking/arcnet.txt.
8662 You need both this driver, and the driver for the particular ARCnet
8663 chipset of your card. If you don't know, then it's probably a
8664 COM90xx type card, so say Y (or M) to "ARCnet COM90xx chipset
8667 You might also want to have a look at the Ethernet-HOWTO, available
8668 from http://www.linuxdoc.org/docs.html#howto (even though ARCnet
8669 is not really Ethernet).
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 arcnet.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 Enable arc0e (ARCnet "ether-encap" packet format)
8679 This allows you to use "Ethernet encapsulation" with your ARCnet
8680 card via the virtual arc0e device. You only need arc0e if you want
8681 to talk to nonstandard ARCnet software, specifically,
8682 DOS/Windows-style "NDIS" drivers. You do not need to say Y here to
8683 communicate with industry-standard RFC1201 implementations, like the
8684 arcether.com packet driver or most DOS/Windows ODI drivers. RFC1201
8685 is included automatically as the arc0 device. Please read the
8686 ARCnet documentation in Documentation/networking/arcnet.txt for more
8687 information about using arc0e and arc0s.
8689 Enable old ARCNet packet format (RFC 1051)
8691 This allows you to use RFC1051 with your ARCnet card via the virtual
8692 arc0s device. You only need arc0s if you want to talk to ARCnet
8693 software complying with the "old" standard, specifically, the DOS
8694 arcnet.com packet driver, Amigas running AmiTCP, and some variants
8695 of NetBSD. You do not need to say Y here to communicate with
8696 industry-standard RFC1201 implementations, like the arcether.com
8697 packet driver or most DOS/Windows ODI drivers. RFC1201 is included
8698 automatically as the arc0 device. Please read the ARCnet
8699 documentation in Documentation/networking/arcnet.txt for more
8700 information about using arc0e and arc0s.
8702 ARCnet COM90xx (normal) chipset driver
8703 CONFIG_ARCNET_COM90xx
8704 This is the chipset driver for the standard COM90xx cards. If you
8705 have always used the old ARCnet driver without knowing what type of
8706 card you had, this is probably the one for you.
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 com90xx.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.
8714 ARCnet COM90xx (IO mapped) chipset driver
8715 CONFIG_ARCNET_COM90xxIO
8716 This is the chipset driver for the COM90xx cards, using them in
8717 IO-mapped mode instead of memory-mapped mode. This is slower than
8718 the normal driver. Only use it if your card doesn't support shared
8721 This driver is also available as a module ( = code which can be
8722 inserted in and removed from the running kernel whenever you want).
8723 The module will be called com90io.o. If you want to compile it as a
8724 module, say M here and read Documentation/modules.txt as well as
8725 Documentation/networking/net-modules.txt.
8727 ARCnet COM90xx (RIM I) chipset driver
8729 This is yet another chipset driver for the COM90xx cards, but this
8730 time only using memory-mapped mode, and no IO ports at all. This
8731 driver is completely untested, so if you have one of these cards,
8732 please mail dwmw2@infradead.org, especially if it works!
8734 This driver is also available as a module ( = code which can be
8735 inserted in and removed from the running kernel whenever you
8736 want). The module will be called arc-rimi.o. If you want to compile
8737 it as a module, say M here and read Documentation/modules.txt as
8738 well as Documentation/networking/net-modules.txt.
8740 ARCnet COM20020 chipset driver
8741 CONFIG_ARCNET_COM20020
8742 This is the driver for the new COM20020 chipset. It supports such
8743 things as promiscuous mode, so packet sniffing is possible, and
8744 extra diagnostic information.
8746 This driver is also available as a module ( = code which can be
8747 inserted in and removed from the running kernel whenever you want).
8748 The module will be called com20020.o. If you want to compile it as a
8749 module, say M here and read Documentation/modules.txt as well as
8750 Documentation/networking/net-modules.txt.
8752 Cabletron E21xx support
8754 If you have a network (Ethernet) card of this type, say Y and read
8755 the Ethernet-HOWTO, available from
8756 http://www.linuxdoc.org/docs.html#howto .
8758 This driver is also available as a module ( = code which can be
8759 inserted in and removed from the running kernel whenever you want).
8760 The module will be called e2100.o. If you want to compile it as a
8761 module, say M here and read Documentation/modules.txt as well as
8762 Documentation/networking/net-modules.txt.
8766 Support for CS89x0 chipset based Ethernet cards. If you have a
8767 network (Ethernet) card of this type, say Y and read the
8768 Ethernet-HOWTO, available from
8769 http://www.linuxdoc.org/docs.html#howto as well as
8770 Documentation/networking/cs89x0.txt.
8772 If you want to compile this as a module ( = code which can be
8773 inserted in and removed from the running kernel whenever you want),
8774 say M here and read Documentation/modules.txt as well as
8775 Documentation/networking/net-modules.txt. The module will be called
8780 If you have a network (Ethernet) card of this type, say Y and read
8781 the Ethernet-HOWTO, available from
8782 http://www.linuxdoc.org/docs.html#howto as well as
8783 drivers/net/depca.c.
8785 If you want to compile this as a module ( = code which can be
8786 inserted in and removed from the running kernel whenever you want),
8787 say M here and read Documentation/modules.txt as well as
8788 Documentation/networking/net-modules.txt. The module will be called
8791 EtherWorks 3 support
8793 This driver supports the DE203, DE204 and DE205 network (Ethernet)
8794 cards. If this is for you, say Y and read
8795 Documentation/networking/ewrk3.txt in the kernel source as well as
8796 the Ethernet-HOWTO, available from
8797 http://www.linuxdoc.org/docs.html#howto .
8799 If you want to compile this as a module ( = code which can be
8800 inserted in and removed from the running kernel whenever you want),
8801 say M here and read Documentation/modules.txt as well as
8802 Documentation/networking/net-modules.txt. The module will be called
8807 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
8808 is for you, read the Ethernet-HOWTO, available from
8809 http://www.linuxdoc.org/docs.html#howto .
8811 If you want to compile this as a module ( = code which can be
8812 inserted in and removed from the running kernel whenever you want),
8813 say M here and read Documentation/modules.txt as well as
8814 Documentation/networking/net-modules.txt. The module will be called
8819 If you have a network (Ethernet) card of this type, say Y and read
8820 the Ethernet-HOWTO, available from
8821 http://www.linuxdoc.org/docs.html#howto .
8823 This driver is also available as a module ( = code which can be
8824 inserted in and removed from the running kernel whenever you want).
8825 If you want to compile it as a module, say M here and read
8826 Documentation/modules.txt as well as
8827 Documentation/networking/net-modules.txt. The module will be called
8830 FMV-181/182/183/184 support
8832 If you have a Fujitsu FMV-181/182/183/184 network (Ethernet) card,
8833 say Y and read the Ethernet-HOWTO, available from
8834 http://www.linuxdoc.org/docs.html#howto .
8836 If you use an FMV-183 or FMV-184 and it is not working, you may need
8837 to disable Plug & Play mode of the card.
8839 This driver is also available as a module ( = code which can be
8840 inserted in and removed from the running kernel whenever you want).
8841 The module will be called fmv18x.o. If you want to compile it as a
8842 module, say M here and read Documentation/modules.txt as well as
8843 Documentation/networking/net-modules.txt.
8845 EtherExpress PRO support
8847 If you have a network (Ethernet) card of this type, say Y. This
8848 driver supports intel i82595{FX,TX} based boards. Note however
8849 that the EtherExpress PRO/100 Ethernet card has its own separate
8850 driver. Please read the Ethernet-HOWTO, available from
8851 http://www.linuxdoc.org/docs.html#howto .
8853 This driver is also available as a module ( = code which can be
8854 inserted in and removed from the running kernel whenever you want).
8855 The module will be called eepro.o. If you want to compile it as a
8856 module, say M here and read Documentation/modules.txt as well as
8857 Documentation/networking/net-modules.txt.
8859 EtherExpress support
8861 If you have an EtherExpress16 network (Ethernet) card, say Y and
8862 read the Ethernet-HOWTO, available from
8863 http://www.linuxdoc.org/docs.html#howto . Note that the Intel
8864 EtherExpress16 card used to be regarded as a very poor choice
8865 because the driver was very unreliable. We now have a new driver
8866 that should do better.
8868 If you want to compile this driver as a module ( = code which can be
8869 inserted in and removed from the running kernel whenever you want),
8870 say M here and read Documentation/modules.txt as well as
8871 Documentation/networking/net-modules.txt. The module will be called
8874 Packet Engines Hamachi GNIC-II support
8876 If you have a Gigabit Ethernet card of this type, say Y and read
8877 the Ethernet-HOWTO, available from
8878 http://www.linuxdoc.org/docs.html#howto .
8880 If you want to compile this as a module ( = code which can be
8881 inserted in and removed from the running kernel whenever you want),
8882 say M here and read Documentation/modules.txt as well as
8883 Documentation/networking/net-modules.txt. The module will be called
8886 HP PCLAN+ (27247B and 27252A) support
8888 If you have a network (Ethernet) card of this type, say Y and read
8889 the Ethernet-HOWTO, available from
8890 http://www.linuxdoc.org/docs.html#howto .
8892 This driver is also available as a module ( = code which can be
8893 inserted in and removed from the running kernel whenever you want).
8894 The module will be called hp-plus.o. If you want to compile it as a
8895 module, say M here and read Documentation/modules.txt as well as
8896 Documentation/networking/net-modules.txt.
8898 HP PCLAN (27245 and other 27xxx series) support
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 This driver is also available as a module ( = code which can be
8905 inserted in and removed from the running kernel whenever you want).
8906 The module will be called hp.o. If you want to compile it as a
8907 module, say M here and read Documentation/modules.txt as well as
8908 Documentation/networking/net-modules.txt.
8910 HP 10/100VG PCLAN (ISA, EISA, PCI) support
8912 If you have a network (Ethernet) card of this type, say Y and read
8913 the Ethernet-HOWTO, available from
8914 http://www.linuxdoc.org/docs.html#howto .
8916 If you want to compile this as a module ( = code which can be
8917 inserted in and removed from the running kernel whenever you want),
8918 say M here and read Documentation/modules.txt as well as
8919 Documentation/networking/net-modules.txt. The module will be called
8922 NE2000/NE1000 support
8924 If you have a network (Ethernet) card of this type, say Y and read
8925 the Ethernet-HOWTO, available from
8926 http://www.linuxdoc.org/docs.html#howto . Many Ethernet cards
8927 without a specific driver are compatible with NE2000.
8929 If you have a PCI NE2000 card however, say N here and Y to "PCI
8930 NE2000 support", above. If you have a NE2000 card and are running on
8931 an MCA system (a bus system used on some IBM PS/2 computers and
8932 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
8935 This driver is also available as a module ( = code which can be
8936 inserted in and removed from the running kernel whenever you want).
8937 The module will be called ne.o. If you want to compile it as a
8938 module, say M here and read Documentation/modules.txt as well as
8939 Documentation/networking/net-modules.txt.
8941 National Semiconductor DP83810 series PCI Ethernet support
8943 This driver is for the National Semiconductor DP83810 series,
8944 including the 83815 chip.
8945 More specific information and updates are available from
8946 http://www.scyld.com/network/natsemi.html
8950 If you have a network (Ethernet) card of this type, say Y and read
8951 the Ethernet-HOWTO, available from
8952 http://www.linuxdoc.org/docs.html#howto .
8954 NE/2 (ne2000 MCA version) support
8956 If you have a network (Ethernet) card of this type, say Y and read
8957 the Ethernet-HOWTO, available from
8958 http://www.linuxdoc.org/docs.html#howto .
8960 This driver is also available as a module ( = code which can be
8961 inserted in and removed from the running kernel whenever you want).
8962 The module will be called ne2.o. If you want to compile it as a
8963 module, say M here and read Documentation/modules.txt as well as
8964 Documentation/networking/net-modules.txt.
8968 These are Micro Channel ethernet adapters. You need to say Y to "MCA
8969 support" in order to use this driver. Supported cards are the SKnet
8970 Junior MC2 and the SKnet MC2(+). The driver automatically
8971 distinguishes between the two cards. Note that using multiple boards
8972 of different type hasn't been tested with this driver. Say Y if you
8973 have one of these ethernet adapters.
8975 This driver is also available as a module ( = code which can be
8976 inserted in and removed from the running kernel whenever you want).
8977 The module is called sk_mca.o. If you want to compile it as a
8978 module, say M here and read Documentation/modules.txt as well as
8979 Documentation/networking/net-modules.txt.
8981 IBM LAN Adapter/A support
8983 This is a Micro Channel ethernet adapter. You need to set CONFIG_MCA
8984 to use this driver. It is both available as an in-kernel driver and
8985 as a module ( = code which can be inserted in and removed from the
8986 running kernel whenever you want). If you want to compile it as a module,
8987 say M here and read Documentation/modules.txt as well as
8988 Documentation/networking/net-modules.txt. If you plan to use more than
8989 one network card under linux, read the Multiple-Ethernet-mini-HOWTO,
8990 available from sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. The only
8991 currently supported card is the IBM LAN Adapter/A for Ethernet. It will
8992 both support 16K and 32K memory windows, however a 32K window gives
8993 a better security against packet losses. Usage of multiple boards with
8994 this driver should be possible, but has not been tested up to now due
8995 to lack of hardware.
8997 EISA, VLB, PCI and on board controllers
8999 This is another class of network cards which attach directly to the
9000 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
9001 available from http://www.linuxdoc.org/docs.html#howto .
9003 Note that the answer to this question doesn't directly affect the
9004 kernel: saying N will just cause this configure script to skip all
9005 the questions about this class of network cards. If you say Y, you
9006 will be asked for your specific card in the following questions. If
9007 you are unsure, say Y.
9009 AMD PCnet32 (VLB and PCI) support
9011 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
9012 answer Y here and read the Ethernet-HOWTO, available from
9013 http://www.linuxdoc.org/docs.html#howto .
9015 This driver is also available as a module ( = code which can be
9016 inserted in and removed from the running kernel whenever you want).
9017 The module will be called pcnet32.o. If you want to compile it as a
9018 module, say M here and read Documentation/modules.txt as well as
9019 Documentation/networking/net-modules.txt.
9021 Ansel Communications EISA 3200 support
9023 If you have a network (Ethernet) card of this type, say Y and read
9024 the Ethernet-HOWTO, available from
9025 http://www.linuxdoc.org/docs.html#howto .
9027 This driver is also available as a module ( = code which can be
9028 inserted in and removed from the running kernel whenever you want).
9029 The module will be called ac3200.o. If you want to compile it as a
9030 module, say M here and read Documentation/modules.txt as well as
9031 Documentation/networking/net-modules.txt.
9033 Mylex EISA LNE390A/LNE390B support (EXPERIMENTAL)
9035 If you have a network (Ethernet) card of this type, say Y and read
9036 the Ethernet-HOWTO, available from
9037 http://www.linuxdoc.org/docs.html#howto .
9039 This driver is also available as a module ( = code which can be
9040 inserted in and removed from the running kernel whenever you want).
9041 The module will be called lne390.o. If you want to compile it as a
9042 module, say M here and read Documentation/modules.txt as well as
9043 Documentation/networking/net-modules.txt.
9045 Novell/Eagle/Microdyne NE3210 EISA support
9047 If you have a network (Ethernet) card of this type, say Y and read
9048 the Ethernet-HOWTO, available from
9049 http://www.linuxdoc.org/docs.html#howto . Note that this driver
9050 will NOT WORK for NE3200 cards as they are completely different.
9052 This driver is also available as a module ( = code which can be
9053 inserted in and removed from the running kernel whenever you want).
9054 The module will be called ne3210.o. If you want to compile it as a
9055 module, say M here and read Documentation/modules.txt as well as
9056 Documentation/networking/net-modules.txt.
9058 Apricot Xen-II on board Ethernet
9060 If you have a network (Ethernet) controller of this type, say Y and
9061 read the Ethernet-HOWTO, available from
9062 http://www.linuxdoc.org/docs.html#howto .
9064 If you want to compile this as a module ( = code which can be
9065 inserted in and removed from the running kernel whenever you want),
9066 say M here and read Documentation/modules.txt as well as
9067 Documentation/networking/net-modules.txt. The module will be called
9070 Generic DECchip & DIGITAL EtherWORKS PCI/EISA
9072 This is support for the DIGITAL series of PCI/EISA Ethernet cards.
9073 These include the DE425, DE434, DE435, DE450 and DE500 models. If
9074 you have a network card of this type, say Y and read the
9075 Ethernet-HOWTO, available from
9076 http://www.linuxdoc.org/docs.html#howto . More specific
9077 information is contained in Documentation/networking/de4x5.txt.
9079 This driver is also available as a module ( = code which can be
9080 inserted in and removed from the running kernel whenever you want).
9081 The module will be called de4x5.o. If you want to compile it as a
9082 module, say M here and read Documentation/modules.txt as well as
9083 Documentation/networking/net-modules.txt.
9085 DECchip Tulip (dc21x4x) PCI support
9087 This driver is developed for the SMC EtherPower series Ethernet
9088 cards and also works with cards based on the DECchip
9089 21040/21041/21140 (Tulip series) chips. Some LinkSys PCI cards are
9090 of this type. (If your card is NOT SMC EtherPower 10/100 PCI
9091 (smc9332dst), you can also try the driver for "Generic DECchip"
9092 cards, above. However, most people with a network card of this type
9093 will say Y here.) Do read the Ethernet-HOWTO, available from
9094 http://www.linuxdoc.org/docs.html#howto . More specific
9095 information is contained in Documentation/networking/tulip.txt.
9097 This driver is also available as a module ( = code which can be
9098 inserted in and removed from the running kernel whenever you want).
9099 The module will be called tulip.o. If you want to compile it as a
9100 module, say M here and read Documentation/modules.txt as well as
9101 Documentation/networking/net-modules.txt.
9103 Digi Intl. RightSwitch support
9105 This is support for the Digi International RightSwitch series of
9106 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
9107 models. If you have a network card of this type, say Y and read the
9108 Ethernet-HOWTO, available from
9109 http://www.linuxdoc.org/docs.html#howto . More specific
9110 information is contained in Documentation/networking/dgrs.txt.
9112 This driver is also available as a module ( = code which can be
9113 inserted in and removed from the running kernel whenever you want).
9114 The module will be called dgrs.o. If you want to compile it as a
9115 module, say M here and read Documentation/modules.txt as well as
9116 Documentation/networking/net-modules.txt.
9118 EtherExpress PRO/100 support
9120 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
9121 card, say Y and read the Ethernet-HOWTO, available from
9122 http://www.linuxdoc.org/docs.html#howto .
9124 This driver is also available as a module ( = code which can be
9125 inserted in and removed from the running kernel whenever you want).
9126 The module will be called eepro100.o. If you want to compile it as a
9127 module, say M here and read Documentation/modules.txt as well as
9128 Documentation/networking/net-modules.txt.
9130 Enable Power Management (EXPERIMENTAL)
9132 Many Intel EtherExpress PRO/100 PCI network cards are capable
9133 of providing power management capabilities. To make use of these
9134 capabilities, say Y.
9136 WARNING: This option is intended for kernel developers and testers.
9137 It is still very experimental, with some people reporting complete
9140 It is recommended to say N here.
9142 ICL EtherTeam 16i/32 support (EXPERIMENTAL)
9144 If you have a network (Ethernet) card of this type, say Y and read
9145 the Ethernet-HOWTO, available from
9146 http://www.linuxdoc.org/docs.html#howto .
9148 This driver is also available as a module ( = code which can be
9149 inserted in and removed from the running kernel whenever you want).
9150 The module will be called eth16i.o. If you want to compile it as a
9151 module, say M here and read Documentation/modules.txt as well as
9152 Documentation/networking/net-modules.txt.
9154 TI ThunderLAN support (EXPERIMENTAL)
9156 If you have a PCI Ethernet network card based on the ThunderLAN chip
9157 which is supported by this driver, say Y and read the
9158 Ethernet-HOWTO, available from
9159 http://www.linuxdoc.org/docs.html#howto .
9161 Devices currently supported by this driver are Compaq Netelligent,
9162 Compaq NetFlex and Olicom cards. Please read the file
9163 Documentation/networking/tlan.txt for more details.
9165 This driver is also available as a module ( = code which can be
9166 inserted in and removed from the running kernel whenever you want).
9167 The module will be called tlan.o. If you want to compile it as a
9168 module, say M here and read Documentation/modules.txt as well as
9169 Documentation/networking/net-modules.txt.
9171 Please email feedback to torben.mathiasen@compaq.com.
9175 If you have a VIA "rhine" based network card (Rhine-I (3043) or
9176 Rhine-2 (VT86c100A)), say Y here.
9178 This driver is also available as a module ( = code which can be
9179 inserted in and removed from the running kernel whenever you want).
9180 The module will be called via-rhine.o. If you want to compile it as
9181 a module, say M here and read Documentation/modules.txt as well as
9182 Documentation/networking/net-modules.txt.
9184 PCI DM9102(A)/DM9132/DM9801 support
9186 This driver is for DM9102(A)/DM9132/DM9801 compatible PCI cards from
9187 Davicom ( http://www.davicom.com.tw ). If you have such a network
9188 (Ethernet) card, say Y. Some information is contained in the file
9189 Documentation/networking/dmfe.txt.
9191 This driver is also available as a module ( = code which can be
9192 inserted in and removed from the running kernel whenever you want).
9193 The module will be called dmfe.o. If you want to compile it as a
9194 module, say M here and read Documentation/modules.txt as well as
9195 Documentation/networking/net-modules.txt.
9197 Racal-Interlan EISA ES3210 support (EXPERIMENTAL)
9199 If you have a network (Ethernet) card of this type, say Y and read
9200 the Ethernet-HOWTO, available from
9201 http://www.linuxdoc.org/docs.html#howto .
9203 This driver is also available as a module ( = code which can be
9204 inserted in and removed from the running kernel whenever you want).
9205 The module will be called es3210.o. If you want to compile it as a
9206 module, say M here and read Documentation/modules.txt as well as
9207 Documentation/networking/net-modules.txt.
9211 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
9212 which is based on the SMC83c17x (EPIC/100).
9213 More specific information and updates are available from
9214 http://www.scyld.com/network/epic100.html
9216 SGI Seeq ethernet controller support
9218 Say Y here if you have an Seeq based Ethernet network card. This is
9219 used in many Silicon Graphics machines.
9221 Sundance "Alta" PCI Ethernet support
9223 This driver is for the Sundance "Alta" chip.
9224 More specific information and updates are available from
9225 http://www.scyld.com/network/sundance.html
9227 Winbond W89c840 PCI Ethernet support
9229 This driver is for the Winbond W89c840 chip. It also works with
9230 the TX9882 chip on the Compex RL100-ATX board.
9231 More specific information and updates are available from
9232 http://www.scyld.com/network/drivers.html
9234 Zenith Z-Note support (EXPERIMENTAL)
9236 The Zenith Z-Note notebook computer has a built-in network
9237 (Ethernet) card, and this is the Linux driver for it. Note that the
9238 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
9239 by this driver. Read the Ethernet-HOWTO, available from
9240 http://www.linuxdoc.org/docs.html#howto .
9242 Pocket and portable adapters
9244 Cute little network (Ethernet) devices which attach to the parallel
9245 port ("pocket adapters"), commonly used with laptops. If you have
9246 one of those, say Y and read the Ethernet-HOWTO, available from
9247 http://www.linuxdoc.org/docs.html#howto .
9249 If you want to plug a network (or some other) card into the PCMCIA
9250 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
9251 credit card size extension cards used by all modern laptops), you
9252 need the pcmcia-cs package (location contained in the file
9253 Documentation/Changes) and you can say N here.
9255 Laptop users should read the Linux Laptop home page at
9256 http://www.cs.utexas.edu/users/kharker/linux-laptop/ .
9258 Note that the answer to this question doesn't directly affect the
9259 kernel: saying N will just cause this configure script to skip all
9260 the questions about this class of network devices. If you say Y, you
9261 will be asked for your specific device in the following questions.
9263 AT-LAN-TEC/RealTek pocket adapter support
9265 This is a network (Ethernet) device which attaches to your parallel
9266 port. Read drivers/net/atp.c as well as the Ethernet-HOWTO,
9267 available from http://www.linuxdoc.org/docs.html#howto , if you
9268 want to use this. If you intend to use this driver, you should have
9269 said N to the "Parallel printer support", because the two drivers
9270 don't like each other.
9272 If you want to compile this driver as a module however ( = code
9273 which can be inserted in and removed from the running kernel
9274 whenever you want), say M here and read Documentation/modules.txt.
9275 The module will be called atp.o.
9277 D-Link DE600 pocket adapter support
9279 This is a network (Ethernet) device which attaches to your parallel
9280 port. Read Documentation/networking/DLINK.txt as well as the
9281 Ethernet-HOWTO, available from
9282 http://www.linuxdoc.org/docs.html#howto , if you want to use
9283 this. It is possible to have several devices share a single parallel
9284 port and it is safe to compile the corresponding drivers into the
9287 If you want to compile this driver as a module however ( = code
9288 which can be inserted in and removed from the running kernel
9289 whenever you want), say M here and read Documentation/modules.txt.
9290 The module will be called de600.o.
9292 D-Link DE620 pocket adapter support
9294 This is a network (Ethernet) device which attaches to your parallel
9295 port. Read Documentation/networking/DLINK.txt as well as the
9296 Ethernet-HOWTO, available from
9297 http://www.linuxdoc.org/docs.html#howto , if you want to use
9298 this. It is possible to have several devices share a single parallel
9299 port and it is safe to compile the corresponding drivers into the
9302 If you want to compile this driver as a module however ( = code
9303 which can be inserted in and removed from the running kernel
9304 whenever you want), say M here and read Documentation/modules.txt.
9305 The module will be called de620.o.
9307 Token Ring driver support
9309 Token Ring is IBM's way of communication on a local network; the
9310 rest of the world uses Ethernet. To participate on a Token Ring
9311 network, you need a special Token ring network card. If you are
9312 connected to such a Token Ring network and want to use your Token
9313 Ring card under Linux, say Y here and to the driver for your
9314 particular card below and read the Token-Ring mini-HOWTO, available
9315 from http://www.linuxdoc.org/docs.html#howto . Most people can
9318 IBM Tropic chipset based adapter support
9320 This is support for all IBM Token Ring cards that don't use DMA. If
9321 you have such a beast, say Y and read the Token-Ring mini-HOWTO,
9322 available from http://www.linuxdoc.org/docs.html#howto .
9324 Warning: this driver will almost definitely fail if more than one
9325 active Token Ring card is present.
9327 This driver is also available as a module ( = code which can be
9328 inserted in and removed from the running kernel whenever you want).
9329 The module will be called ibmtr.o. If you want to compile it as a
9330 module, say M here and read Documentation/modules.txt.
9332 IBM Olympic chipset PCI adapter support
9334 This is support for all non-Lanstreamer IBM PCI Token Ring Cards.
9335 Specifically this is all IBM PCI, PCI Wake On Lan, PCI II, PCI II
9336 Wake On Lan, and PCI 100/16/4 adapters.
9338 If you have such an adapter, say Y and read the Token-Ring
9339 mini-HOWTO, available from
9340 http://www.linuxdoc.org/docs.html#howto .
9342 This driver is also available as a module ( = code which can be
9343 inserted in and removed from the running kernel whenever you want).
9344 The module will will be called olympic.o. If you want to compile it
9345 as a module, say M here and read Documentation/modules.txt.
9347 Also read the file Documentation/networking/olympic.txt or check the
9348 Linux Token Ring Project site for the latest information at
9349 http://www.linuxtr.net .
9351 IBM Lanstreamer chipset PCI adapter support
9353 This is support for IBM Lanstreamer PCI Token Ring Cards.
9355 If you have such an adapter, say Y and read the Token-Ring
9356 mini-HOWTO available via FTP (user:anonymous) from
9357 ftp://metalab.unc/edu/pub/Linux/docs/HOWTO.
9359 This driver is also available as a modules ( = code which can be
9360 inserted in and removed from the running kernel whenever you want).
9361 The modules will be called lanstreamer.o. If you want to compile it
9362 as a module, say M here and read Documentation/modules.txt.
9364 Generic TMS380 Token Ring ISA/PCI/MCA/EISA adapter support
9366 This driver provides generic support for token ring adapters
9367 based on the Texas Instruments TMS380 series chipsets. This
9368 includes the SysKonnect TR4/16(+) ISA (SK-4190), SysKonnect
9369 TR4/16(+) PCI (SK-4590), SysKonnect TR4/16 PCI (SK-4591),
9370 Compaq 4/16 PCI, Thomas-Conrad TC4048 4/16 PCI, and several
9371 Madge adapters. If you say Y here, you will be asked to select
9372 which cards to support below. If you're using modules, each
9373 class of card will be supported by a separate module.
9375 If you have such an adapter and would like to use it, say Y and
9376 read the Token-Ring mini-HOWTO, available from
9377 http://www.linuxdoc.org/docs.html#howto .
9379 Also read the file Documentation/networking/tms380tr.txt or
9380 check http://www.auk.cx/tms380tr/ .
9382 This driver is also available as a module ( = code which can be
9383 inserted in and removed from the running kernel whenever you want).
9384 The module will will be called tms380tr.o. If you want to compile it
9385 as a module, say M here and read Documentation/modules.txt.
9387 Generic TMS380 PCI support
9389 This tms380 module supports generic TMS380-based PCI cards.
9391 These cards are known to work:
9392 - Compaq 4/16 TR PCI
9393 - SysKonnect TR4/16 PCI (SK-4590/SK-4591)
9394 - Thomas-Conrad TC4048 PCI 4/16
9395 - 3Com Token Link Velocity
9397 This driver is available as a module ( = code which can be
9398 inserted in and removed from the running kernel whenever you want).
9399 The module will will be called tmspci.o. If you want to compile it
9400 as a module, say M here and read Documentation/modules.txt.
9402 Madge Smart 16/4 PCI Mk2 support
9404 This tms380 module supports the Madge Smart 16/4 PCI Mk2
9407 This driver is available as a module ( = code which can be
9408 inserted in and removed from the running kernel whenever you want).
9409 The module will will be called abyss.o. If you want to compile it
9410 as a module, say M here and read Documentation/modules.txt.
9412 Madge Smart 16/4 Ringode MicroChannel
9414 This tms380 module supports the Madge Smart 16/4 MC16 and MC32
9415 MicroChannel adapters.
9417 This driver is available as a module ( = code which can be
9418 inserted in and removed from the running kernel whenever you want).
9419 The module will will be called madgemc.o. If you want to compile it
9420 as a module, say M here and read Documentation/modules.txt.
9422 SMC ISA TokenRing adapter support
9424 This is support for the ISA and MCA SMC Token Ring cards,
9425 specifically SMC TokenCard Elite (8115T) and SMC TokenCard Elite/A
9428 If you have such an adapter and would like to use it, say Y or M and
9429 read the Token-Ring mini-HOWTO, available from
9430 http://www.linuxdoc.org/docs.html#howto and the file
9431 Documentation/networking/smctr.txt.
9433 This driver is also available as a module ( = code which can be
9434 inserted in and removed from the running kernel whenever you want).
9435 The module will will be called smctr.o. If you want to compile it
9436 as a module, say M here and read Documentation/modules.txt.
9438 Sun Happy Meal 10/100baseT support
9440 This driver supports the "hme" interface present on most Ultra
9441 systems and as an option on older Sbus systems. This driver supports
9442 both PCI and Sbus devices. This driver also supports the "qfe" quad
9443 100baseT device available in both PCI and Sbus configurations.
9445 This support is also available as a module called sunhme.o ( = code
9446 which can be inserted in and removed from the running kernel
9447 whenever you want). If you want to compile it as a module, say M
9448 here and read Documentation/modules.txt.
9452 This driver supports the "le" interface present on all 32-bit Sparc
9453 systems, on some older Ultra systems and as an Sbus option.
9455 This support is also available as a module called sunlance.o ( =
9456 code which can be inserted in and removed from the running kernel
9457 whenever you want). If you want to compile it as a module, say M
9458 here and read Documentation/modules.txt.
9460 Sun BigMAC 10/100baseT support (EXPERIMENTAL)
9462 This driver supports the "be" interface available as an Sbus option.
9463 This is Sun's older 100baseT ethernet device.
9465 This support is also available as a module called sunbmac.o ( = code
9466 which can be inserted in and removed from the running kernel
9467 whenever you want). If you want to compile it as a module, say M
9468 here and read Documentation/modules.txt.
9470 Sun QuadEthernet support
9472 This driver supports the "qe" 10baseT ethernet device, available as
9473 an Sbus option. Note that this is not the same as Quad FastEthernet
9474 "qfe" which is supported by the Happy Meal driver instead.
9476 This support is also available as a module called sunqe.o ( = code
9477 which can be inserted in and removed from the running kernel
9478 whenever you want). If you want to compile it as a module, say M
9479 here and read Documentation/modules.txt.
9481 Traffic Shaper (EXPERIMENTAL)
9483 The traffic shaper is a virtual network device that allows you to
9484 limit the rate of outgoing data flow over some other network device.
9485 The traffic that you want to slow down can then be routed through
9486 these virtual devices. See Documentation/networking/shaper.txt for
9489 An alternative to this traffic shaper is the experimental
9490 Class-Based Queueing (CBQ) scheduling support which you get if you
9491 say Y to "QoS and/or fair queueing" above.
9493 To set up and configure shaper devices, you need the shapecfg
9494 program, available from ftp://shadow.cabi.net/pub/Linux in the
9497 This driver is also available as a module ( = code which can be
9498 inserted in and removed from the running kernel whenever you want).
9499 The module will be called shaper.o. If you want to compile it as a
9500 module, say M here and read Documentation/modules.txt. If unsure,
9505 Fiber Distributed Data Interface is a high speed local area network
9506 design; essentially a replacement for high speed Ethernet. FDDI can
9507 run over copper or fiber. If you are connected to such a network and
9508 want a driver for the FDDI card in your computer, say Y here (and
9509 then also Y to the driver for your FDDI card, below). Most people
9512 Digital DEFEA and DEFPA adapter support
9514 This is support for the DIGITAL series of EISA (DEFEA) and PCI
9515 (DEFPA) controllers which can connect you to a local FDDI network.
9517 SysKonnect FDDI PCI support
9519 Say Y here if you have a SysKonnect FDDI PCI adapter.
9520 The following adapters are supported by this driver:
9521 - SK-5521 (SK-NET FDDI-UP)
9522 - SK-5522 (SK-NET FDDI-UP DAS)
9523 - SK-5541 (SK-NET FDDI-FP)
9524 - SK-5543 (SK-NET FDDI-LP)
9525 - SK-5544 (SK-NET FDDI-LP DAS)
9526 - SK-5821 (SK-NET FDDI-UP64)
9527 - SK-5822 (SK-NET FDDI-UP64 DAS)
9528 - SK-5841 (SK-NET FDDI-FP64)
9529 - SK-5843 (SK-NET FDDI-LP64)
9530 - SK-5844 (SK-NET FDDI-LP64 DAS)
9531 - Netelligent 100 FDDI DAS Fibre SC
9532 - Netelligent 100 FDDI SAS Fibre SC
9533 - Netelligent 100 FDDI DAS UTP
9534 - Netelligent 100 FDDI SAS UTP
9535 - Netelligent 100 FDDI SAS Fibre MIC
9537 Read Documentation/networking/skfp.txt for information about
9540 Questions concerning this driver can be addressed to:
9543 If you want to compile this driver as a module ( = code which can be
9544 inserted in and removed from the running kernel whenever you want),
9545 say M here and read Documentation/modules.txt. This is recommended.
9546 The module will be called skfp.o.
9548 HIgh Performance Parallel Interface support (EXPERIMENTAL)
9550 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
9551 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
9552 can run over copper (25m) or fiber (300m on multi-mode or 10km on
9553 single-mode). HIPPI networks are commonly used for clusters and to
9554 connect to super computers. If you are connected to a HIPPI network
9555 and have a HIPPI network card in your computer that you want to use
9556 under Linux, say Y here (you must also remember to enable the driver
9557 for your HIPPI card below). Most people will say N here.
9559 Essential RoadRunner HIPPI PCI adapter support
9561 Say Y here if this is your PCI HIPPI network card.
9563 This driver is also available as a module ( = code which can be
9564 inserted in and removed from the running kernel whenever you want).
9565 The module will be called rrunner.o. If you want to compile it as
9566 a module, say M here and read Documentation/modules.txt. If unsure,
9569 Use large TX/RX rings
9570 CONFIG_ROADRUNNER_LARGE_RINGS
9571 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
9572 of additional memory to allow for fastest operation, both for
9573 transmitting and receiving. This memory cannot be used by any other
9574 kernel code or by user space programs. Say Y here only if you have
9579 If you have an Acorn system with one of these (AKA25) network cards,
9580 you should say Y to this option if you wish to use it with Linux.
9582 Acorn/ANT Ether3 card
9584 If you have an Acorn system with one of these network cards, you
9585 should say Y to this option if you wish to use it with Linux.
9589 If you have an Acorn system with one of these network cards, you
9590 should say Y to this option if you wish to use it with Linux.
9592 EBSA-110 Ethernet interface
9593 CONFIG_ARM_AM79C961A
9594 If you wish to compile a kernel for the EBSA-110, then you should
9595 always answer Y to this.
9597 Support CDROM drives that are not SCSI or IDE/ATAPI
9598 CONFIG_CD_NO_IDESCSI
9599 If you have a CDROM drive that is neither SCSI nor IDE/ATAPI, say Y
9600 here, otherwise N. Read the CDROM-HOWTO, available from
9601 http://www.linuxdoc.org/docs.html#howto .
9603 Note that the answer to this question doesn't directly affect the
9604 kernel: saying N will just cause this configure script to skip all
9605 the questions about these CDROM drives. If you are unsure what you
9606 have, say Y and find out whether you have one of the following
9609 For each of these drivers, a file Documentation/cdrom/<driver_name>
9610 exists. Especially in cases where you do not know exactly which kind
9611 of drive you have you should read there. Most of these drivers use a
9612 file drivers/cdrom/<driver_name>.h where you can define your
9613 interface parameters and switch some internal goodies.
9615 All these CDROM drivers are also usable as a module ( = code which
9616 can be inserted in and removed from the running kernel whenever you
9617 want). If you want to compile them as module, say M instead of Y and
9618 read Documentation/modules.txt.
9620 If you want to use any of these CDROM drivers, you also have to
9621 answer Y or M to "ISO 9660 CDROM file system support" below (this
9622 answer will get "defaulted" for you if you enable any of the Linux
9625 Sony CDU31A/CDU33A CDROM support
9627 These CDROM drives have a spring-pop-out caddyless drawer, and a
9628 rectangular green LED centered beneath it. NOTE: these CDROM drives
9629 will not be auto detected by the kernel at boot time; you have to
9630 provide the interface address as an option to the kernel at boot
9631 time as described in Documentation/cdrom/cdu31a or fill in your
9632 parameters into drivers/cdrom/cdu31a.c. Try "man bootparam" or
9633 see the documentation of your boot loader (lilo or loadlin) about
9634 how to pass options to the kernel.
9636 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9637 file system support" below, because that's the file system used on
9640 This driver is also available as a module ( = code which can be
9641 inserted in and removed from the running kernel whenever you want).
9642 The module will be called cdu31a.o. If you want to compile it as a
9643 module, say M here and read Documentation/modules.txt.
9645 Standard Mitsumi [no XA/Multisession] CDROM support
9647 This is the older of the two drivers for the older Mitsumi models
9648 LU-005, FX-001 and FX-001D. This is not the right driver for the
9649 FX-001DE and the triple or quad speed models (all these are
9650 IDE/ATAPI models). Please also the file Documentation/cdrom/mcd.
9652 With the old LU-005 model, the whole drive chassis slides out for cd
9653 insertion. The FX-xxx models use a motorized tray type mechanism.
9654 Note that this driver does not support XA or MultiSession CDs
9655 (PhotoCDs). There is a new driver (next question) which can do
9656 this. If you want that one, say N here.
9658 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9659 file system support" below, because that's the file system used on
9662 This driver is also available as a module ( = code which can be
9663 inserted in and removed from the running kernel whenever you want).
9664 The module will be called mcd.o. If you want to compile it as a
9665 module, say M here and read Documentation/modules.txt.
9667 IRQ channel for Mitsumi CD-ROM
9669 This allows you to specify the default value of the IRQ used by the
9670 driver. This setting can be overridden by passing the "mcd="
9671 parameter to the kernel at boot time (or at module load time if you
9672 said M to "Standard Mitsumi CDROM support").
9674 I/O base address for Mitsumi CD-ROM
9676 This allows you to specify the default value of the I/O base address
9677 used by the driver. This setting can be overridden by passing the
9678 "mcd=" parameter to the kernel at boot time (or at module load time
9679 if you said M to "Standard Mitsumi CDROM support").
9681 Mitsumi [XA/MultiSession] support
9683 Use this driver if you want to be able to read XA or MultiSession
9684 CDs (PhotoCDs) as well as ordinary CDs with your Mitsumi LU-005,
9685 FX-001 or FX-001D CDROM drive. In addition, this driver uses much
9686 less kernel memory than the old one, if that is a concern. This
9687 driver is able to support more than one drive, but each drive needs
9688 a separate interface card. Please read the file
9689 Documentation/cdrom/mcdx.
9691 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9692 file system support" below, because that's the file system used on
9695 This driver is also available as a module ( = code which can be
9696 inserted in and removed from the running kernel whenever you want).
9697 The module will be called mcdx.o. If you want to compile it as a
9698 module, say M here and read Documentation/modules.txt.
9700 Matsushita/Panasonic/Creative, Longshine, TEAC CDROM support
9702 This driver supports most of the drives which use the Panasonic or
9703 Sound Blaster interface. Please read the file
9704 Documentation/cdrom/sbpcd.
9706 The Matsushita CR-521, CR-522, CR-523, CR-562, CR-563 drives
9707 (sometimes labeled "Creative"), the Creative Labs CD200, the
9708 Longshine LCS-7260, the "IBM External ISA CDROM" (in fact a CR-56x
9709 model), the TEAC CD-55A fall under this category. Some other
9710 "electrically compatible" drives (Vertos, Genoa, some Funai models)
9711 are currently not supported; for the Sanyo H94A drive currently a
9712 separate driver (asked later) is responsible. Most drives have a
9713 uniquely shaped faceplate, with a caddyless motorized drawer, but
9714 without external brand markings. The older CR-52x drives have a
9715 caddy and manual loading/eject, but still no external markings. The
9716 driver is able to do an extended auto-probing for interface
9717 addresses and drive types; this can help to find facts in cases you
9718 are not sure, but can consume some time during the boot process if
9719 none of the supported drives gets found. Once your drive got found,
9720 you should enter the reported parameters into drivers/cdrom/sbpcd.h
9721 and set "DISTRIBUTION 0" there.
9723 This driver can support up to four CDROM controller cards, and each
9724 card can support up to four CDROM drives; if you say Y here, you
9725 will be asked how many controller cards you have. If compiled as a
9726 module, only one controller card (but with up to four drives) is
9729 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9730 file system support" below, because that's the file system used on
9733 This driver is also available as a module ( = code which can be
9734 inserted in and removed from the running kernel whenever you want).
9735 The module will be called sbpcd.o. If you want to compile it as a
9736 module, say M here and read Documentation/modules.txt.
9738 Matsushita/Panasonic, ... second CDROM controller support
9740 Say Y here only if you have two CDROM controller cards of this type
9741 (usually only if you have more than four drives). You should enter
9742 the parameters for the second, third and fourth interface card into
9743 include/linux/sbpcd.h before compiling the new kernel. Read
9744 the file Documentation/cdrom/sbpcd.
9746 Aztech/Orchid/Okano/Wearnes/TXC/CyDROM CDROM support
9748 This is your driver if you have an Aztech CDA268-01A, Orchid
9749 CD-3110, Okano or Wearnes CDD110, Conrad TXC, or CyCDROM CR520 or
9750 CR540 CDROM drive. This driver -- just like all these CDROM drivers
9751 -- is NOT for CDROM drives with IDE/ATAPI interfaces, such as Aztech
9752 CDA269-031SE. Please read the file Documentation/cdrom/aztcd.
9754 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9755 file system support" below, because that's the file system used on
9758 This driver is also available as a module ( = code which can be
9759 inserted in and removed from the running kernel whenever you want).
9760 The module will be called aztcd.o. If you want to compile it as a
9761 module, say M here and read Documentation/modules.txt.
9763 Sony CDU535 CDROM support
9765 This is the driver for the older Sony CDU-535 and CDU-531 CDROM
9766 drives. Please read the file Documentation/cdrom/sonycd535.
9768 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9769 file system support" below, because that's the file system used on
9772 This driver is also available as a module ( = code which can be
9773 inserted in and removed from the running kernel whenever you want).
9774 The module will be called sonycd535.o. If you want to compile it as
9775 a module, say M here and read Documentation/modules.txt.
9777 Goldstar R420 CDROM support
9779 If this is your CDROM drive, say Y here. As described in the file
9780 Documentation/cdrom/gscd, you might have to change a setting
9781 in the file drivers/cdrom/gscd.h before compiling the
9782 kernel. Please read the file Documentation/cdrom/gscd.
9784 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9785 file system support" below, because that's the file system used on
9788 This driver is also available as a module ( = code which can be
9789 inserted in and removed from the running kernel whenever you want).
9790 The module will be called gscd.o. If you want to compile it as a
9791 module, say M here and read Documentation/modules.txt.
9793 Philips/LMS CM206 CDROM support
9795 If you have a Philips/LMS CDROM drive cm206 in combination with a
9796 cm260 host adapter card, say Y here. Please also read the file
9797 Documentation/cdrom/cm206.
9799 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9800 file system support" below, because that's the file system used on
9803 This driver is also available as a module ( = code which can be
9804 inserted in and removed from the running kernel whenever you want).
9805 The module will be called cm206.o. If you want to compile it as a
9806 module, say M here and read Documentation/modules.txt.
9808 Optics Storage DOLPHIN 8000AT CDROM support
9810 This is the driver for the 'DOLPHIN' drive with a 34-pin Sony
9811 compatible interface. It also works with the Lasermate CR328A. If
9812 you have one of those, say Y. This driver does not work for the
9813 Optics Storage 8001 drive; use the IDE-ATAPI CDROM driver for that
9814 one. Please read the file Documentation/cdrom/optcd.
9816 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9817 file system support" below, because that's the file system used on
9820 This driver is also available as a module ( = code which can be
9821 inserted in and removed from the running kernel whenever you want).
9822 The module will be called optcd.o. If you want to compile it as a
9823 module, say M here and read Documentation/modules.txt.
9825 Sanyo CDR-H94A CDROM support
9827 If this is your CDROM drive, say Y here and read the file
9828 Documentation/cdrom/sjcd. You should then also say Y or M to
9829 "ISO 9660 CDROM file system support" below, because that's the
9830 file system used on CDROMs.
9832 This driver is also available as a module ( = code which can be
9833 inserted in and removed from the running kernel whenever you want).
9834 The module will be called sjcd.o. If you want to compile it as a
9835 module, say M here and read Documentation/modules.txt.
9837 ISP16/MAD16/Mozart soft configurable cdrom interface support
9839 These are sound cards with built-in cdrom interfaces using the OPTi
9840 82C928 or 82C929 chips. Say Y here to have them detected and
9841 possibly configured at boot time. In addition, You'll have to say Y
9842 to a driver for the particular cdrom drive you have attached to the
9843 card. Read Documentation/cdrom/isp16 for details.
9845 This driver is also available as a module ( = code which can be
9846 inserted in and removed from the running kernel whenever you want).
9847 The module will be called isp16.o. If you want to compile it as a
9848 module, say M here and read Documentation/modules.txt.
9852 If you say Y here, you will be able to set per user limits for disk
9853 usage (also called disk quotas). Currently, it works only for the
9854 ext2 file system. You need additional software in order to use quota
9855 support; for details, read the Quota mini-HOWTO, available from
9856 http://www.linuxdoc.org/docs.html#howto . Probably the quota
9857 support is only useful for multi user systems. If unsure, say N.
9859 Memory Technology Device (MTD) support
9861 Memory Technology Devices are flash, RAM and similar chips, often
9862 used for solid state filesystems on embedded devices. This option
9863 will provide the generic support for MTD drivers to register
9864 themselves with the kernel and for potential users of MTD devices
9865 to enumerate the devices which are present and obtain a handle on
9866 them. It will also allow you to select individual drivers for
9867 particular hardware and users of MTD device. If unsure, say N.
9869 M-Systems Disk-On-Chip 1000 support
9871 This provides an MTD device driver for the M-Systems DiskOnChip
9872 1000 devices, which are obsolete so you probably want to say 'N'.
9874 M-Systems Disk-On-Chip 2000 support
9876 This provides an MTD device driver for the M-Systems DiskOnChip
9877 2000 devices. If you use this, you probably also want the NFTL
9878 'NAND Flash Translation Layer' below, which is used to emulate
9879 a block device by using a kind of filesystem on the flash chips.
9881 M-Systems Disk-On-Chip Millennium support
9883 This provides an MTD device driver for the M-Systems DiskOnChip
9884 Millennium devices. If you use this, you probably also want the
9885 NFTL 'NAND Flash Translation Layer' below, which is used to emulate
9886 a block device by using a kind of filesystem on the flash chips.
9888 Use extra onboard system memory as MTD device
9890 If your CPU cannot cache all of the physical memory in your machine,
9891 you can still use it for storage or swap by using this driver to
9892 present it to the system as a Memory Technology Device.
9894 Ramix PMC551 PCI Mezzanine ram card support
9896 This provides an MTD device driver for the Ramix PMC551 RAM card.
9897 If you have one, you probably want to enable this.
9899 PMC551 256M DRAM Bugfix.
9900 CONFIG_MTD_PMC551_BUGFIX
9901 Some PMC551 boards hacve invalid column and row mux values. This
9902 option will fix them, but will break other memory configurations.
9904 Debugging RAM test driver
9906 This enables a test MTD device driver which uses vmalloc() to
9907 provide storage. You probably want to say 'N' unless you're
9908 testing stuff, or unless you want to use it in place of a ramdisk
9909 when I've eventually got round to making the CONFIG_BLK_DEV option
9910 and you've turned it off.
9912 Common Flash Interface (CFI) support
9914 Intel's Common Flash Interface specification provides a universal
9915 method for probing the capabilities of flash devices. If you wish
9916 to support any device which uses CFI-compliant devices, you need
9917 to enable this option.
9919 CFI support for Intel/Sharp Extended Command Set chips
9920 CONFIG_MTD_CFI_INTELEXT
9921 The Common Flash Interface defines a number of different command
9922 sets which a CFI-compliant chip may claim to implement. This code
9923 provides support for one of those command sets, used on Intel
9924 Strataflash and other parts.
9926 Flash chip mapping in physical memory
9928 This provides a 'mapping' driver which allows the CFI probe and
9929 command set driver code to communicate with flash chips which
9930 are mapped physically into the CPU's memory. You will need to
9931 configure the physical address and size of the flash chips on
9932 your particular board.
9934 Physical start location of flash chip mapping
9935 CONFIG_MTD_PHYSMAP_START
9936 This is the physical memory location at which the flash chips
9937 are mapped on your particular target board. Refer to the
9938 memory map which should hopefully be in the documentation for
9941 Physical length of flash chip mapping
9942 CONFIG_MTD_PHYSMAP_LEN
9943 This is the total length of the mapping of the flash chips on
9944 your particular board. If there is space, or aliases, in the
9945 physical memory map between the chips, this could be larger
9946 than the total amount of flash present. Refer to the memory
9947 map which should hopefully be in the documentation for your
9950 Flash chip mapping on Mixcom piggyback card
9952 This supports the paging arrangement for access to flash chips
9953 on the Mixcom piggyback card, allowing the flash chip drivers
9954 to get on with their job of driving the flash chips without
9955 having to know about the paging. If you have one of these boards,
9956 you probably want to enable this mapping driver.
9958 Flash chip mapping on Nora
9960 If you had to ask, you don't have one. Say 'N'.
9962 Flash chip mapping on Octagon 5066 SBC
9964 This provides a 'mapping' driver which supports the way in which
9965 the flash chips are connected in the Octagon-5066 Single Board
9966 Computer. You will also need to complete and enable the driver
9967 for JEDEC flash chips.
9969 Flash chip mapping on RPXlite PPC board
9971 The RPXLite PowerPC board has CFI-compliant chips mapped in
9972 a strange sparse mapping. This 'mapping' driver supports that
9973 arrangement, allowing the CFI probe and command set driver code
9974 to communicate with the chips on the RPXLite board.
9976 Flash chip mapping on Tempustech VMAX SBC301
9978 This provides a 'mapping' driver which supports the way in which
9979 the flash chips are connected in the Tempustech VMAX SBC301 Single
9980 Board Computer. You will also need to complete and enable the driver
9981 for JEDEC flash chips.
9983 Direct chardevice access to MTD devices
9985 This provides a character device for each MTD device present in
9986 the system, allowing the user to read and write directly to the
9987 memory chips, and also use ioctl() to obtain information about
9988 the device, or to erase parts of it.
9990 Pseudo-blockdevice access to MTD devices
9992 Although flash chips have an erase size too large to useful as
9993 block devices, it is possible to use MTD devices which are based
9994 on RAM chips in this manner. This blockdevice user of MTD devices
9995 performs that function. At the moment, it is also required for
9996 the Journalling Flash File System to obtain a handle on the MTD
9997 device when it's mounted - although the JFFS doesn't actually use
9998 any of the functions of the mtdblock device.
10000 Later, it may be extended to perform read/erase/modify/write cycles
10001 on flash chips to emulate a smaller block size. Needless to say,
10002 this is very unsafe, but could be useful for filesystems which are
10003 almost never written to.
10005 FTL (Flash Translation Layer) support
10007 This provides support for the original Flash Translation Layer which
10008 is part of the PCMCIA specification. It uses a kind of pseudo-
10009 filesystem on a flash device to emulate a block device with 512-byte
10010 sectors, on top of which you put a 'normal' filesystem. You may find
10011 that the algorithms used in this code are patented unless you live
10012 in the Free World where software patents aren't legal - in the USA
10013 you are only permitted to use this on PCMCIA hardware, although
10014 under the terms of the GPL you're obviously permitted to copy,
10015 modify and distribute the code as you wish. Just not use it.
10017 NFTL (NAND Flash Translation Layer) support
10019 This provides support for the NAND Flash Translation Layer which is
10020 used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
10021 filesystem on a flash device to emulate a block device with 512-byte
10022 sectors, on top of which you put a 'normal' filesystem. You may find
10023 that the algorithms used in this code are patented unless you live
10024 in the Free World where software patents aren't legal - in the USA
10025 you are only permitted to use this on DiskOnChip hardware, although
10026 under the terms of the GPL you're obviously permitted to copy,
10027 modify and distribute the code as you wish. Just not use it.
10029 Write support for NFTL (EXPERIMENTAL)
10031 If you're lucky, this will actually work. Don't whinge if it doesn't.
10032 Contact dwmw2@infradead.org if you want to help to make it more
10037 Universal Serial Bus (USB) is a specification for a serial bus
10038 subsystem which offers higher speeds and more features than the
10039 traditional PC serial port. The bus supplies power to peripherals
10040 and allows for hot swapping. Up to 127 USB peripherals can be
10041 connected to a single USB port in a tree structure. The USB port is
10042 the root of the tree, the peripherals are the leaves and the inner
10043 nodes are special USB devices called hubs. Many newer PC's have USB
10044 ports and newer peripherals such as scanners, keyboards, mice,
10045 modems, and printers support the USB protocol and can be connected
10046 to the PC via those ports.
10048 Say Y here if your computer has a USB port and you want to use USB
10049 devices. You then need to say Y to at least one of "UHCI support" or
10050 "OHCI support" below (the type of interface that the USB hardware in
10051 your computer provides to the operating system) and then choose from
10052 among the drivers for USB peripherals. You may want to check out the
10053 information provided in Documentation/usb/ and especially the links
10054 given in Documentation/usb/usb-help.txt.
10056 This code is also available as a module ( = code which can be
10057 inserted in and removed from the running kernel whenever you want).
10058 The module will be called usbcore.o. If you want to compile it as a
10059 module, say M here and read Documentation/modules.txt.
10061 USB verbose debug messages
10063 Say Y here if you want the USB core & hub drivers to produce a bunch
10064 of debug messages to the system log. Select this if you are having a
10065 problem with USB support and want to see more of what is going on.
10067 UHCI (intel PIIX4, VIA, ...) support?
10069 The Universal Host Controller Interface is a standard by Intel for
10070 accessing the USB hardware in the PC (which is also called the USB
10071 host controller). If your USB host controller conforms to this
10072 standard, you may want to say Y, but see below. All recent boards
10073 with Intel PCI chipsets (like intel 430TX, 440FX, 440LX, 440BX,
10074 i810, i820) conform to this standard. Also all VIA PCI chipsets
10075 (like VIA VP2, VP3, MVP3, Apollo Pro, Apollo Pro II or Apollo Pro
10078 Currently there exist two drivers for UHCI host controllers: this
10079 one and the so-called JE driver, which you can get from
10080 "UHCI alternate (JE) support", below. You need only one.
10082 This code is also available as a module ( = code which can be
10083 inserted in and removed from the running kernel whenever you want).
10084 The module will be called usb-uhci.o. If you want to compile it as a
10085 module, say M here and read Documentation/modules.txt.
10087 UHCI (intel PIIX4, VIA, ...) alternate (JE) support?
10088 CONFIG_USB_UHCI_ALT
10089 The Universal Host Controller Interface is a standard by Intel for
10090 accessing the USB hardware in the PC (which is also called the USB
10091 host controller). If your USB host controller conforms to this
10092 standard, you may want to say Y, but see below. All recent boards
10093 with Intel PCI chipsets (like intel 430TX, 440FX, 440LX, 440BX,
10094 i810, i820) conform to this standard. Also all VIA PCI chipsets
10095 (like VIA VP2, VP3, MVP3, Apollo Pro, Apollo Pro II or Apollo Pro
10096 133). If unsure, say Y.
10098 Currently there exist two drivers for UHCI host controllers: this
10099 so-called JE driver, and the one you get from "UHCI support", above.
10102 This code is also available as a module ( = code which can be
10103 inserted in and removed from the running kernel whenever you want).
10104 The module will be called uhci.o. If you want to compile it as a
10105 module, say M here and read Documentation/modules.txt.
10107 UHCI unlink optimizations (EXPERIMENTAL)
10108 CONFIG_USB_UHCI_ALT_UNLINK_OPTIMIZE
10109 This option currently does nothing. You may say Y or N.
10111 OHCI (Compaq, iMacs, OPTi, SiS, ALi, ...) support
10113 The Open Host Controller Interface is a standard by
10114 Compaq/Microsoft/National for accessing the USB PC hardware (also
10115 called USB host controller). If your USB host controller conforms to
10116 this standard, say Y. The USB host controllers on most non-Intel
10117 architectures and on several x86 compatibles with non-Intel chipsets
10118 -- like SiS (aktual 610, 610 and so on) or ALi (ALi IV, ALi V,
10119 Aladdin Pro..) -- conform to this standard.
10121 You may want to read the file Documentation/usb/ohci.txt.
10123 This code is also available as a module ( = code which can be
10124 inserted in and removed from the running kernel whenever you want).
10125 The module will be called usb-ohci.o. If you want to compile it
10126 as a module, say M here and read Documentation/modules.txt.
10128 USB Human Interface Device (full HID) support
10130 Say Y here if you want full HID support to connect keyboards,
10131 mice, joysticks, graphic tablets, or any other HID based devices
10132 to your computer via USB. You can't use this driver and the
10133 HIDBP (Boot Protocol) keyboard and mouse drivers at the same time.
10134 More information is available: Documentation/usb/input.txt.
10138 This code is also available as a module ( = code which can be
10139 inserted in and removed from the running kernel whenever you want).
10140 The module will be called hid.o. If you want to compile it as a
10141 module, say M here and read Documentation/modules.txt.
10143 USB HIDBP Keyboard (basic) support
10145 Say Y here if you don't want to use the generic HID driver for your
10146 USB keyboard and prefer to use the keyboard in its limited Boot
10147 Protocol mode instead. This driver is much smaller than the HID one.
10149 This code is also available as a module ( = code which can be
10150 inserted in and removed from the running kernel whenever you want).
10151 The module will be called usbkbd.o. If you want to compile it as a
10152 module, say M here and read Documentation/modules.txt.
10156 USB HIDBP Mouse (basic) support
10158 Say Y here if you don't want to use the generic HID driver for your
10159 USB mouse and prefer to use the mouse in its limited Boot Protocol
10160 mode instead. This driver is much smaller than the HID one.
10162 This code is also available as a module ( = code which can be
10163 inserted in and removed from the running kernel whenever you want).
10164 The module will be called usbmouse.o. If you want to compile it as
10165 a module, say M here and read Documentation/modules.txt.
10169 Wacom Intuos/Graphire tablet support
10171 Say Y here if you want to use the USB version of the Wacom Intuos
10172 or Graphire tablet. Make sure to say Y to "Mouse support"
10173 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
10174 (CONFIG_INPUT_EVDEV) as well.
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 wacom.o. If you want to compile it as a
10179 module, say M here and read Documentation/modules.txt.
10181 Logitech WingMan Force joystick support
10183 Say Y here if you want to use the Logitech WingMan Force with Linux
10184 on the USB port. No force-feedback support yet, but other than that
10185 it should work like a normal joystick.
10187 This driver is also available as a module ( = code which can be
10188 inserted in and removed from the running kernel whenever you want).
10189 The module will be called wmforce.o. If you want to compile it as a
10190 module, say M here and read Documentation/modules.txt.
10192 Use input layer for ADB devices
10193 CONFIG_INPUT_ADBHID
10194 Say Y here if you want to have ADB (Apple Desktop Bus) HID devices
10195 such as keyboards, mice, joysticks, or graphic tablets handled by the
10196 input layer. If you say Y here, make sure to say Y to the
10197 corresponding drivers "Keyboard support" (CONFIG_INPUT_KEYBDEV),
10198 "Mouse Support" (CONFIG_INPUT_MOUSEDEV) and "Event interface support"
10199 (CONFIG_INPUT_EVDEV) as well.
10201 If you say N here, you still have the option of using the old ADB
10202 keyboard and mouse drivers.
10207 CONFIG_INPUT_KEYBDEV
10208 Say Y here if you want your USB HID keyboard (or an ADB keyboard
10209 handled by the input layer) to be able to serve as a system keyboard.
10211 This driver is also available as a module ( = code which can be
10212 inserted in and removed from the running kernel whenever you want).
10213 The module will be called keybdev.o. If you want to compile it as a
10214 module, say M here and read Documentation/modules.txt.
10217 CONFIG_INPUT_MOUSEDEV
10218 Say Y here if you want your USB HID mouse (or ADB mouse handled by
10219 the input layer) to be accessible as char devices 13:32+ -
10220 /dev/input/mouseX and 13:63 - /dev/input/mice as an emulated ImPS/2
10221 mouse. That way, all user space programs will be able to use your
10226 This driver is also available as a module ( = code which can be
10227 inserted in and removed from the running kernel whenever you want).
10228 The module will be called mousedev.o. If you want to compile it as
10229 a module, say M here and read Documentation/modules.txt.
10231 Horizontal screen resolution
10232 CONFIG_INPUT_MOUSEDEV_SCREEN_X
10233 If you're using a digitizer, or a graphic tablet, and want to use
10234 it as a mouse then the mousedev driver needs to know the X window
10235 screen resolution you are using to correctly scale the data. If
10236 you're not using a digitizer, this value is ignored.
10238 Vertical screen resolution
10239 CONFIG_INPUT_MOUSEDEV_SCREEN_Y
10240 If you're using a digitizer, or a graphic tablet, and want to use
10241 it as a mouse then the mousedev driver needs to know the X window
10242 screen resolution you are using to correctly scale the data. If
10243 you're not using a digitizer, this value is ignored.
10246 CONFIG_INPUT_JOYDEV
10247 Say Y here if you want your USB HID joystick or gamepad to be
10248 accessible as char device 13:0+ - /dev/input/jsX device.
10250 This driver is also available as a module ( = code which can be
10251 inserted in and removed from the running kernel whenever you want).
10252 The module will be called joydev.o. If you want to compile it as a
10253 module, say M here and read Documentation/modules.txt.
10255 Event interface support
10257 Say Y here if you want your USB or ADB HID device events be accessible
10258 under char device 13:64+ - /dev/input/eventX in a generic way.
10259 This is the future ...
10261 USB Scanner support
10263 Say Y here if you want to connect a USB scanner to your computer's
10264 USB port. Please read Documentation/usb/scanner.txt and
10265 Documentation/usb/scanner-hp-sane.txt for more information.
10267 This code is also available as a module ( = code which can be
10268 inserted in and removed from the running kernel whenever you want).
10269 The module will be called scanner.o. If you want to compile it as
10270 a module, say M here and read Documentation/modules.txt.
10274 Say Y here if you want to connect UAB audio equipment such as
10275 speakers to your computer's USB port.
10277 This code is also available as a module ( = code which can be
10278 inserted in and removed from the running kernel whenever you want).
10279 The module will be called audio.o. If you want to compile it as a
10280 module, say M here and read Documentation/modules.txt.
10282 USB Modem (CDC ACM) support
10284 This driver supports USB modems and ISDN adapters which support the
10285 Communication Device Class Abstract Control Model interface.
10286 Please read Documentation/usb/acm.txt for details.
10288 This code is also available as a module ( = code which can be
10289 inserted in and removed from the running kernel whenever you want).
10290 The module will be called acm.o. If you want to compile it as a
10291 module, say M here and read Documentation/modules.txt.
10293 USB Serial converter support
10295 Say Y here if you have a USB device that provides normal serial
10296 ports, and you want to connect it to your USB bus. Supported devices
10297 are the Tech WhiteHEAT multi-port USB to serial converter, and the
10298 FTDI or Keyspan single port USB to serial converter Handspring
10299 Visor. In addition to saying Y here, you need to say Y to the driver
10300 for your specific hardware below. Some other devices may also be
10301 used if you say Y to "USB Generic Serial Driver", below.
10303 Please read Documentation/usb/usb-serial.txt for more information.
10305 This code is also available as a module ( = code which can be
10306 inserted in and removed from the running kernel whenever you want).
10307 The module will be called usbserial.o. If you want to compile it
10308 as a module, say M here and read Documentation/modules.txt.
10310 USB Generic Serial Driver
10311 CONFIG_USB_SERIAL_GENERIC
10312 Say Y here if you want to use the generic USB serial driver. Please
10313 read Documentation/usb/usb-serial.txt for more information on using
10314 this driver. It is recommended that the "USB Serial converter
10315 support" be compiled as a module for this driver to be used
10318 USB ConnectTech WhiteHEAT Serial Driver
10319 CONFIG_USB_SERIAL_WHITEHEAT
10320 Say Y here if you want to use a ConnectTech WhiteHEAT 4 port
10321 USB to serial converter device.
10323 This code is also available as a module ( = code which can be
10324 inserted in and removed from the running kernel whenever you want).
10325 The module will be called whiteheat.o. If you want to compile it as a
10326 module, say M here and read Documentation/modules.txt.
10328 USB Handspring Visor Driver
10329 CONFIG_USB_SERIAL_VISOR
10330 Say Y here if you want to connect to your HandSpring Visor through
10331 its USB docking station. See http://usbvisor.sourceforge.net for
10332 more information on using this driver.
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 visor.o. If you want to compile it as a
10337 module, say M here and read Documentation/modules.txt.
10339 USB Belkin and Paracom Single Port Serial Driver
10340 CONFIG_USB_SERIAL_BELKIN
10341 Say Y here if you want to use a Belkin USB Serial single port
10342 adaptor (F5U103 is one of the model numbers) or the Peracom single
10343 port USB to serial adapter.
10345 This code is also available as a module ( = code which can be
10346 inserted in and removed from the running kernel whenever you want).
10347 The module will be called belkin_sa.o. If you want to compile it as
10348 a module, say M here and read Documentation/modules.txt.
10350 USB FTDI Single Port Serial Driver
10351 CONFIG_USB_SERIAL_FTDI_SIO
10352 Say Y here if you want to use a FTDI SIO single port USB to serial
10353 converter device. The implementation I have is called the USC-1000.
10355 See http://reality.sgi.com/bryder_wellington/ftdi_sio for more
10356 information on this driver and the device.
10358 This code is also available as a module ( = code which can be
10359 inserted in and removed from the running kernel whenever you want).
10360 The module will be called ftdi_sio.o. If you want to compile it as a
10361 module, say M here and read Documentation/modules.txt.
10363 USB Keyspan PDA Single Port Serial Driver
10364 CONFIG_USB_SERIAL_KEYSPAN_PDA
10365 Say Y here if you want to use a Keyspan PDA single port USB to
10366 serial converter device. This driver makes use of firmware
10367 developed from scratch by Brian Warner.
10369 This code is also available as a module ( = code which can be
10370 inserted in and removed from the running kernel whenever you want).
10371 The module will be called keyspan_pda.o. If you want to compile it
10372 as a module, say M here and read Documentation/modules.txt.
10374 USB Keyspan USA-xxx Serial Driver
10375 CONFIG_USB_SERIAL_KEYSPAN
10376 Say Y here if you want to use Keyspan USB to serial converter
10377 devices. This driver makes use of Keyspan's official firmware
10378 and was developed with their support. You must also include
10379 firmware to support your particular device(s).
10381 See http://www.linuxcare.com.au/hugh/keyspan.html for
10384 This code is also available as a module ( = code which can be
10385 inserted in and removed from the running kernel whenever you want).
10386 The module will be called keyspan.o. If you want to compile it as a
10387 module, say M here and read Documentation/modules.txt.
10389 USB Keyspan USA-28 Firmware
10390 CONFIG_USB_SERIAL_KEYSPAN_USA28
10391 Say Y here to include firmware for the USA-28 converter.
10393 USB Keyspan USA-28X Firmware
10394 CONFIG_USB_SERIAL_KEYSPAN_USA28X
10395 Say Y here to include firmware for the USA-28X converter.
10397 USB Keyspan USA-19 Firmware
10398 CONFIG_USB_SERIAL_KEYSPAN_USA19
10399 Say Y here to include firmware for the USA-19 converter.
10401 USB Keyspan USA-18X Firmware
10402 CONFIG_USB_SERIAL_KEYSPAN_USA18X
10403 Say Y here to include firmware for the USA-18X converter.
10405 USB Keyspan USA-19W Firmware
10406 CONFIG_USB_SERIAL_KEYSPAN_USA19W
10407 Say Y here to include firmware for the USA-19W converter.
10409 USB ZyXEL omni.net LCD Plus Driver
10410 CONFIG_USB_SERIAL_OMNINET
10411 Say Y here if you want to use a ZyXEL omni.net LCD ISDN TA.
10413 This code is also available as a module ( = code which can be
10414 inserted in and removed from the running kernel whenever you want).
10415 The module will be called omninet.o. If you want to compile it as a
10416 module, say M here and read Documentation/modules.txt.
10418 USB Digi International AccelePort USB Serial Driver
10419 CONFIG_USB_SERIAL_DIGI_ACCELEPORT
10420 Say Y here if you want to use Digi AccelePort USB 2 or 4 devices,
10421 2 port (plus parallel port) and 4 port USB serial converters. The
10422 parallel port on the USB 2 appears as a third serial port on Linux.
10423 The Digi Acceleport USB 8 is not yet supported by this driver.
10425 This driver works under SMP with the usb-uhci driver. It does not
10426 work under SMP with the uhci driver.
10428 This code is also available as a module ( = code which can be
10429 inserted in and removed from the running kernel whenever you want).
10430 The module will be called digi_acceleport.o. If you want to compile
10431 it as a module, say M here and read Documentation/modules.txt.
10433 USB Empeg empeg-car Mark I/II Driver
10434 CONFIG_USB_SERIAL_EMPEG
10435 Say Y here if you want to connect to your Empeg empeg-car Mark I/II
10436 mp3 player via USB. The driver uses a single ttyUSB{0,1,2,...}
10437 device node. See Documentation/usb/usb-serial.txt for more
10438 tidbits of information.
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 empeg.o. If you want to compile it as a
10443 module, say M here and read Documentation/modules.txt.
10445 USB MCT Single Port Serial Driver
10446 CONFIG_USB_SERIAL_MCT_U232
10447 Say Y here if you want to use a USB Serial single port adapter from
10448 Magic Control Technology Corp. (U232 is one of the model numbers).
10450 This code is also available as a module ( = code which can be
10451 inserted in and removed from the running kernel whenever you want).
10452 The module will be called mct_u232.o. If you want to compile it as
10453 a module, say M here and read Documentation/modules.txt.
10455 USB Serial Converter verbose debug
10456 CONFIG_USB_SERIAL_DEBUG
10457 Say Y here if you want verbose debug messages from the USB Serial
10460 USB Printer support
10462 Say Y here if you want to connect a USB printer to your computer's
10465 This code is also available as a module ( = code which can be
10466 inserted in and removed from the running kernel whenever you want).
10467 The module will be called printer.o. If you want to compile it as a
10468 module, say M here and read Documentation/modules.txt.
10470 USB IBM (Xirlink) C-It Camera support
10472 Say Y here if you want to connect a IBM "C-It" camera, also known as
10473 "Xirlink PC Camera" to your computer's USB port. For more
10474 information, read Documentation/usb/ibmcam.txt.
10476 This driver uses the Video For Linux API. You must enable
10477 (Y or M in config) Video For Linux (under Character Devices)
10478 to use this driver. Information on this API and pointers to
10479 "v4l" programs may be found on the WWW at
10480 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
10482 This code is also available as a module ( = code which can be
10483 inserted in and removed from the running kernel whenever you want).
10484 The module will be called ibmcam.o. If you want to compile it as a
10485 module, say M here and read Documentation/modules.txt. This camera
10486 has several configuration options which can be specified when you
10487 load the module. Read Documentation/usb/ibmcam.txt to learn more.
10489 USB OV511 Camera support
10491 Say Y here if you want to connect this type of camera to your
10492 computer's USB port. See Documentation/usb/ov511.txt for more
10493 information and for a list of supported cameras.
10495 This driver uses the Video For Linux API. You must say Y or M to
10496 "Video For Linux" (under Character Devices) to use this driver.
10497 Information on this API and pointers to "v4l" programs may be found
10498 on the WWW at http://roadrunner.swansea.uk.linux.org/v4l.shtml .
10500 This code is also available as a module ( = code which can be
10501 inserted in and removed from the running kernel whenever you want).
10502 The module will be called ov511.o. If you want to compile it as a
10503 module, say M here and read Documentation/modules.txt.
10505 USB ADMtek Pegasus-based ethernet device support
10507 Say Y if you want to use your USB ethernet device. Supported
10508 cards until now are:
10509 ADMtek AN986 Pegasus (eval. board)
10510 ADMtek ADM8511 Pegasus II (eval. board)
10513 Corega FEter USB-TX
10514 MELCO/BUFFALO LUA-TX
10515 D-Link DSB-650TX, DSB-650TX-PNA, DSB-650, DU-E10, DU-E100
10516 Linksys USB100TX, USB10TX
10517 LANEED Ethernet LD-USB/TX
10519 SOHOware NUB Ethernet
10521 Any Pegasus II based board also are supported.
10522 If you have devices with vendor IDs other than noted above
10523 you should add them in the driver code and send a message
10524 to me (petkan@dce.bg) for update.
10526 This code is also available as a module ( = code which can be
10527 inserted in and removed from the running kernel whenever you want).
10528 The module will be called pegasus.o. If you want to compile it as a
10529 module, say M here and read Documentation/modules.txt.
10531 USB Kodak DC-2xx Camera support
10533 Say Y here if you want to connect this type of still camera to
10534 your computer's USB port. See Documentation/usb/dc2xx.txt for more
10535 information; some non-Kodak cameras may also work with this
10536 driver, given application support (such as www.gPhoto.org).
10538 This code is also available as a module ( = code which can be
10539 inserted in and removed from the running kernel whenever you want).
10540 The module will be called dc2xx.o. If you want to compile it as a
10541 module, say M here and read Documentation/modules.txt.
10543 USB Mustek MDC800 Digital Camera Support
10545 Say Y here if you want to connect this type of still camera to
10546 your computer's USB port. This driver can be used with gphoto 0.4.3
10547 and higher (look at http://www.gphoto.org ).
10548 To use it create a device node with "mknod /dev/mustek c 180 32" and
10549 configure it in your software.
10551 This code is also available as a module ( = code which can be
10552 inserted in and removed from the running kernel whenever you want).
10553 The module will be called mdc800.o. If you want to compile it as a
10554 module, say M here and read Documentation/modules.txt.
10556 USB Mass Storage support
10558 Say Y here if you want to connect USB mass storage devices to your
10559 computer's USB port.
10561 This code is also available as a module ( = code which can be
10562 inserted in and removed from the running kernel whenever you want).
10563 The module will be called usb-storage.o. If you want to compile it
10564 as a module, say M here and read Documentation/modules.txt.
10566 USB Mass Storage verbose debug
10567 CONFIG_USB_STORAGE_DEBUG
10568 Say Y here in order to have the USB Mass Storage code generate
10569 verbose debugging messages.
10571 USS720 parport driver
10573 This driver is for USB parallel port adapters that use the Lucent
10574 Technologies USS-720 chip. These cables are plugged into your USB
10575 port and provide USB compatibility to peripherals designed with
10576 parallel port interfaces.
10578 The chip has two modes: automatic mode and manual mode. In automatic
10579 mode, it looks to the computer like a standard USB printer. Only
10580 printers may be connected to the USS-720 in this mode. The generic
10581 USB printer driver ("USB Printer support", above) may be used in
10582 that mode, and you can say N here if you want to use the chip only
10585 Manual mode is not limited to printers, any parallel port
10586 device should work. This driver utilizes manual mode.
10587 Note however that some operations are three orders of magnitude
10588 slower than on a PCI/ISA Parallel Port, so timing critical
10589 applications might not work.
10591 Say Y here if you own an USS-720 USB->Parport cable and intend to
10592 connect anything other than a printer to it.
10594 This code is also available as a module ( = code which can be
10595 inserted in and removed from the running kernel whenever you want).
10596 The module will be called uss720.o. If you want to compile it as a
10597 module, say M here and read Documentation/modules.txt.
10599 USB device file system
10600 CONFIG_USB_DEVICEFS
10601 If you say Y here (and to "/proc file system support" below), you
10602 will get a file /proc/usb/devices which lists the devices currently
10603 connected to your USB busses, a file /proc/usb/drivers which lists
10604 the USB kernel client drivers currently loaded, and for every
10605 connected device a file named "/proc/usb/xxx/yyy", where xxx is the
10606 bus number and yyy the device number; the latter files can be used
10607 by user space programs to talk directly to the device. These files
10608 are "virtual", meaning they are generated on the fly and not stored
10611 For the format of the /proc/usb/ files, please read
10612 Documentation/usb/proc_usb_info.txt.
10614 Please note that this code is completely unrelated to devfs, the
10615 "/dev file system support".
10617 Most users want to say Y here.
10619 USB Bandwidth allocation
10620 CONFIG_USB_BANDWIDTH
10621 If you say Y here, the USB subsystem enforces USB bandwidth
10622 allocation and will prevent some device opens from succeeding
10623 if they would cause USB bandwidth usage to go above 90% of
10626 If you say N here, these conditions will cause warning messages
10627 about USB bandwidth usage to be logged and some devices or
10628 drivers may not work correctly.
10632 A Digital Audio Broadcasting (DAB) Receiver for USB and Linux
10633 brought to you by the DAB-Team (http://dab.in.tum.de). This driver
10634 can be taken as an example for URB-based bulk, control, and
10635 isochronous transactions. URB's are explained in
10636 Documentation/usb/URB.txt.
10638 This code is also available as a module ( = code which can be
10639 inserted in and removed from the running kernel whenever you want).
10640 The module will be called dabusb.o. If you want to compile it as a
10641 module, say M here and read Documentation/modules.txt.
10645 A driver for the Prolific PL-2302 USB-to-USB network device. This
10646 'USB cable' connects two hosts via a point-to-point network with
10647 bandwidth of 5 Mbit/s. Configure this driver after connecting the
10648 USB cable via ifconfig plusb0 10.0.0.1 pointopoint 10.0.0.2 (and
10649 vice versa on the other host).
10651 This code is also available as a module ( = code which can be
10652 inserted in and removed from the running kernel whenever you want).
10653 The module will be called plusb.o. If you want to compile it as a
10654 module, say M here and read Documentation/modules.txt.
10656 USB Diamond Rio500 support
10658 Say Y here if you want to connect a USB Rio500 mp3 player to your
10659 computer's USB port. Please read Documentation/usb/rio.txt
10660 for more information.
10662 This code is also available as a module ( = code which can be
10663 inserted in and removed from the running kernel whenever you want).
10664 The module will be called rio500.o. If you want to compile it as
10665 a module, say M here and read Documentation/modules.txt.
10667 D-Link DSB-R100 FM radio support
10669 Say Y here if you want to connect this type of radio to your
10670 computer's USB port. Note that the audio is not digital, and
10671 you must connect the line out connector to a sound card or a
10674 This driver uses the Video For Linux API. You must enable
10675 (Y or M in config) Video For Linux (under Character Devices)
10676 to use this driver. Information on this API and pointers to
10677 "v4l" programs may be found on the WWW at
10678 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
10680 This code is also available as a module ( = code which can be
10681 inserted in and removed from the running kernel whenever you want).
10682 The module will be called dsbr100.o. If you want to compile it as a
10683 module, say M here and read Documentation/modules.txt.
10685 Microtek USB scanner support
10686 CONFIG_USB_MICROTEK
10687 Say Y here if you want support for the Microtek X6USB and possibly
10688 some other scanners by that vendor. The scanner will appear as a
10689 scsi generic device to the rest of the system.
10690 A patched version of SANE is necessary to use the
10691 scanner. It's available at
10692 http://fachschaft.cup.uni-muenchen.de/~neukum/scanner.html
10693 This driver can be compiled as a module.
10695 USB Bluetooth support
10696 CONFIG_USB_BLUETOOTH
10697 Say Y here if you want to connect a USB Bluetooth device to your
10698 computer's USB port. You will need the Bluetooth stack (available
10699 at http://developer.axis.com/software/index.shtml) to fully use
10702 This code is also available as a module ( = code which can be
10703 inserted in and removed from the running kernel whenever you want).
10704 The module will be called bluetooth.o. If you want to compile it as
10705 a module, say M here and read Documentation/modules.txt.
10709 Minix is a simple operating system used in many classes about OS's.
10710 The minix file system (method to organize files on a hard disk
10711 partition or a floppy disk) was the original file system for Linux,
10712 but has been superseded by the second extended file system ext2fs.
10713 You don't want to use the minix file system on your hard disk
10714 because of certain built-in restrictions, but it is sometimes found
10715 on older Linux floppy disks. This option will enlarge your kernel by
10716 about 28 KB. If unsure, say N.
10718 If you want to compile this as a module ( = code which can be
10719 inserted in and removed from the running kernel whenever you want),
10720 say M here and read Documentation/modules.txt. The module will be
10721 called minix.o. Note that the file system of your root partition
10722 (the one containing the directory /) cannot be compiled as a module.
10724 Second extended fs support
10726 This is the de facto standard Linux file system (method to organize
10727 files on a storage device) for hard disks.
10729 You want to say Y here, unless you intend to use Linux exclusively
10730 from inside a DOS partition using the UMSDOS file system. The
10731 advantage of the latter is that you can get away without
10732 repartitioning your hard drive (which often implies backing
10733 everything up and restoring afterwards); the disadvantage is that
10734 Linux becomes susceptible to DOS viruses and that UMSDOS is somewhat
10735 slower than ext2fs. Even if you want to run Linux in this fashion,
10736 it might be a good idea to have ext2fs around: it enables you to
10737 read more floppy disks and facilitates the transition to a *real*
10738 Linux partition later. Another (rare) case which doesn't require
10739 ext2fs is a diskless Linux box which mounts all files over the
10740 network using NFS (in this case it's sufficient to say Y to "NFS
10741 file system support" below). Saying Y here will enlarge your kernel
10744 The Ext2fs-Undeletion mini-HOWTO, available from
10745 http://www.linuxdoc.org/docs.html#howto , gives information about
10746 how to retrieve deleted files on ext2fs file systems.
10748 To change the behavior of ext2 file systems, you can use the tune2fs
10749 utility ("man tune2fs"). To modify attributes of files and
10750 directories on ext2 file systems, use chattr ("man chattr").
10752 Ext2fs partitions can be read from within DOS using the ext2tool
10753 command line tool package (available via FTP (user: anonymous) from
10754 ftp://metalab.unc.edu/pub/Linux/system/filesystems/ext2 ) and from
10755 within Windows NT using the ext2nt command line tool package from
10756 ftp://metalab.unc.edu/pub/Linux/utils/dos . Explore2fs is a
10757 graphical explorer for ext2fs partitions which runs on Windows 95
10758 and Windows NT and includes experimental write support; it is
10760 http://jnewbigin-pc.it.swin.edu.au/Linux/Explore2fs.htm .
10762 If you want to compile this file system as a module ( = code which
10763 can be inserted in and removed from the running kernel whenever you
10764 want), say M here and read Documentation/modules.txt. The module
10765 will be called ext2.o. Be aware however that the file system of your
10766 root partition (the one containing the directory /) cannot be
10767 compiled as a module, and so this could be dangerous. Most everyone
10768 wants to say Y here.
10770 BFS file system support (EXPERIMENTAL)
10772 Boot File System (BFS) is a file system used under SCO UnixWare to
10773 allow the bootloader access to the kernel image and other important
10774 files during the boot process. It is usually mounted under /stand
10775 and corresponds to the slice marked as "STAND" in the UnixWare
10776 partition. You should say Y if you want to read or write
10777 the files on your /stand slice from within Linux. You then also
10778 need to say Y to "UnixWare slices support", below. More information
10779 about the BFS file system is contained in the file
10780 Documentation/filesystems/bfs.txt.
10782 If you don't know what this is about, say N.
10784 If you want to compile this as a module ( = code which can be
10785 inserted in and removed from the running kernel whenever you want),
10786 say M here and read Documentation/modules.txt. The module will be
10787 called bfs.o. Note that the file system of your root partition (the
10788 one containing the directory /) cannot be compiled as a module.
10790 Compressed ROM file system support
10792 Saying Y here includes support for CramFs (Compressed ROM File
10793 System). Cramfs is designed to be a simple, small, and compressed
10794 file system for ROM based embedded systems. CramFs is read-only,
10795 limited to 256MB file systems (with 16MB files), and doesn't support
10796 16/32 bits uid/gid, hard links and timestamps.
10798 See Documentation/filesystems/cramfs.txt and fs/cramfs/README
10799 for further information.
10801 If you want to compile this as a module ( = code which can be
10802 inserted in and removed from the running kernel whenever you want),
10803 say M here and read Documentation/modules.txt. The module will be
10804 called cramfs.o. Note that the root file system (the one containing
10805 the directory /) cannot be compiled as a module.
10809 Simple RAM-based file system support
10811 Ramfs is a file system which keeps all files in RAM. It allows
10812 read and write access.
10814 In contrast to RAM disks, which get allocated a fixed amount of RAM,
10815 ramfs grows and shrinks to accommodate the files it contains.
10817 Before you can use this RAM-based file system, it has to be mounted,
10818 meaning it has to be given a location in the directory hierarchy. If
10819 you want to use the location /ramfiles for example, you would have
10820 to create that directory first and then mount the file system by
10821 saying "mount -t ramfs ramfs /ramfiles" or the equivalent line in
10822 /etc/fstab. Everything is "virtual" in the sense that no files will
10823 be created on your hard drive; if you reboot, everything in
10824 /ramfiles will be lost.
10826 If you want to compile this as a module ( = code which can be
10827 inserted in and removed from the running kernel whenever you want),
10828 say M here and read Documentation/modules.txt. The module will be
10831 ISO 9660 CDROM file system support
10833 This is the standard file system used on CDROMs. It was previously
10834 known as "High Sierra File System" and is called "hsfs" on other
10835 Unix systems. The so-called Rock-Ridge extensions which allow for
10836 long Unix filenames and symbolic links are also supported by this
10837 driver. If you have a CDROM drive and want to do more with it than
10838 just listen to audio CDs and watch its LEDs, say Y (and read
10839 Documentation/filesystems/isofs.txt and the CDROM-HOWTO, available
10840 from http://www.linuxdoc.org/docs.html#howto ), thereby enlarging
10841 your kernel by about 27 KB; otherwise say N.
10843 If you want to compile this as a module ( = code which can be
10844 inserted in and removed from the running kernel whenever you want),
10845 say M here and read Documentation/modules.txt. The module will be
10848 Microsoft Joliet CDROM extensions
10850 Joliet is a Microsoft extension for the ISO 9660 CDROM file system
10851 which allows for long filenames in unicode format (unicode is the
10852 new 16 bit character code, successor to ASCII, which encodes the
10853 characters of almost all languages of the world; see
10854 http://www.unicode.org for more information). Say Y here if you want
10855 to be able to read Joliet CDROMs under Linux.
10857 UDF File System support (read only)
10859 This is the new file system used on some CDROMs and DVDs. Say Y if
10860 you intend to mount DVD discs or CDRW's written in packet mode, or
10861 if written to by other UDF utilities, such as DirectCD. This UDF
10862 file system support is read-only. If you want to write to UDF
10863 file systems on some media, you need to say Y to "UDF read-write
10864 support" below in addition. Please read
10865 Documentation/filesystems/udf.txt.
10867 This file system support is also available as a module ( = code
10868 which can be inserted in and removed from the running kernel
10869 whenever you want). The module is called udf.o. If you want to
10870 compile it as a module, say M here and read
10871 Documentation/modules.txt.
10875 UDF write support (DANGEROUS)
10877 Say Y if you want to test write support for UDF file systems.
10878 Due to lack of support for writing to CDR/CDRW's, this option
10879 is only supported for hard discs, DVD-RAM, and loopback files.
10883 If you want to use one of the FAT-based file systems (the MS-DOS,
10884 VFAT (Windows 95) and UMSDOS (used to run Linux on top of an
10885 ordinary DOS partition) file systems), then you must say Y or M here
10886 to include FAT support. You will then be able to mount partitions or
10887 diskettes with FAT-based file systems and transparently access the
10888 files on them, i.e. MSDOS files will look and behave just like all
10891 This FAT support is not a file system in itself, it only provides
10892 the foundation for the other file systems. You will have to say Y or
10893 M to at least one of "MSDOS fs support" or "VFAT fs support" in
10894 order to make use of it.
10896 Another way to read and write MSDOS floppies and hard drive
10897 partitions from within Linux (but not transparently) is with the
10898 mtools ("man mtools") program suite. You don't need to say Y here in
10901 If you need to move large files on floppies between a DOS and a
10902 Linux box, say Y here, mount the floppy under Linux with an MSDOS
10903 file system and use GNU tar's M option. GNU tar is a program
10904 available for Unix and DOS ("man tar" or "info tar").
10906 It is now also becoming possible to read and write compressed FAT
10907 file systems; read Documentation/filesystems/fat_cvf.txt for
10910 The FAT support will enlarge your kernel by about 37 KB. If unsure,
10913 If you want to compile this as a module however ( = code which can
10914 be inserted in and removed from the running kernel whenever you
10915 want), say M here and read Documentation/modules.txt. The module
10916 will be called fat.o. Note that if you compile the FAT support as a
10917 module, you cannot compile any of the FAT-based file systems into
10918 the kernel -- they will have to be modules as well. The file system
10919 of your root partition (the one containing the directory /) cannot
10920 be a module, so don't say M here if you intend to use UMSDOS as your
10925 This allows you to mount MSDOS partitions of your hard drive (unless
10926 they are compressed; to access compressed MSDOS partitions under
10927 Linux, you can either use the DOS emulator DOSEMU, described in the
10928 DOSEMU-HOWTO, available from
10929 http://www.linuxdoc.org/docs.html#howto , or try dmsdosfs in
10930 ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs . If you
10931 intend to use dosemu with a non-compressed MSDOS partition, say Y
10932 here) and MSDOS floppies. This means that file access becomes
10933 transparent, i.e. the MSDOS files look and behave just like all
10936 If you want to use UMSDOS, the Unix-like file system on top of a
10937 DOS file system, which allows you to run Linux from within a DOS
10938 partition without repartitioning, you'll have to say Y or M here.
10940 If you have Windows 95 or Windows NT installed on your MSDOS
10941 partitions, you should use the VFAT file system (say Y to "VFAT fs
10942 support" below), or you will not be able to see the long filenames
10943 generated by Windows 95 / Windows NT.
10945 This option will enlarge your kernel by about 7 KB. If unsure,
10946 answer Y. This will only work if you said Y to "DOS FAT fs support"
10947 as well. If you want to compile this as a module however ( = code
10948 which can be inserted in and removed from the running kernel
10949 whenever you want), say M here and read Documentation/modules.txt.
10950 The module will be called msdos.o.
10952 VFAT (Windows-95) fs support
10954 This option provides support for normal Windows file systems with
10955 long filenames. That includes non-compressed FAT-based file systems
10956 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
10957 programs from the mtools package.
10959 You cannot use the VFAT file system for your Linux root partition
10960 (the one containing the directory /); use UMSDOS instead if you
10961 want to run Linux from within a DOS partition (i.e. say Y to
10962 "UMSDOS: Unix like fs on top of std MSDOS fs", below).
10964 The VFAT support enlarges your kernel by about 10 KB and it only
10965 works if you said Y to the "DOS FAT fs support" above. Please read
10966 the file Documentation/filesystems/vfat.txt for details. If unsure,
10969 If you want to compile this as a module ( = code which can be
10970 inserted in and removed from the running kernel whenever you want),
10971 say M here and read Documentation/modules.txt. The module will be
10974 UMSDOS: Unix-like file system on top of standard MSDOS fs
10976 Say Y here if you want to run Linux from within an existing DOS
10977 partition of your hard drive. The advantage of this is that you can
10978 get away without repartitioning your hard drive (which often implies
10979 backing everything up and restoring afterwards) and hence you're
10980 able to quickly try out Linux or show it to your friends; the
10981 disadvantage is that Linux becomes susceptible to DOS viruses and
10982 that UMSDOS is somewhat slower than ext2fs. Another use of UMSDOS
10983 is to write files with long unix filenames to MSDOS floppies; it
10984 also allows Unix-style soft-links and owner/permissions of files on
10985 MSDOS floppies. You will need a program called umssync in order to
10986 make use of UMSDOS; read Documentation/filesystems/umsdos.txt.
10988 To get utilities for initializing/checking UMSDOS file system, or
10989 latest patches and/or information, visit the UMSDOS home page at
10990 http://www.voyager.hr/~mnalis/umsdos/ .
10992 This option enlarges your kernel by about 28 KB and it only works if
10993 you said Y to both "DOS FAT fs support" and "MSDOS fs support"
10994 above. If you want to compile this as a module ( = code which can be
10995 inserted in and removed from the running kernel whenever you want),
10996 say M here and read Documentation/modules.txt. The module will be
10997 called umsdos.o. Note that the file system of your root partition
10998 (the one containing the directory /) cannot be a module, so saying M
10999 could be dangerous. If unsure, say N.
11001 /proc file system support
11003 This is a virtual file system providing information about the status
11004 of the system. "Virtual" means that it doesn't take up any space on
11005 your hard disk: the files are created on the fly by the kernel when
11006 you try to access them. Also, you cannot read the files with older
11007 version of the program less: you need to use more or cat.
11009 It's totally cool; for example, "cat /proc/interrupts" gives
11010 information about what the different IRQs are used for at the moment
11011 (there is a small number of Interrupt ReQuest lines in your computer
11012 that are used by the attached devices to gain the CPU's attention --
11013 often a source of trouble if two devices are mistakenly configured
11014 to use the same IRQ). The program procinfo to display some
11015 information about your system gathered from the /proc file system.
11017 Before you can use the /proc file system, it has to be mounted,
11018 meaning it has to be given a location in the directory hierarchy.
11019 That location should be /proc. A command such as "mount -t proc proc
11020 /proc" or the equivalent line in /etc/fstab does the job.
11022 The /proc file system is explained in the file
11023 Documentation/filesystems/proc.txt and on the proc(5) manpage ("man
11026 This option will enlarge your kernel by about 67 KB. Several
11027 programs depend on this, so everyone should say Y here.
11029 /dev file system support (EXPERIMENTAL)
11031 This is support for devfs, a virtual file system (like /proc) which
11032 provides the file system interface to device drivers, normally found
11033 in /dev. Devfs does not depend on major and minor number
11034 allocations. Device drivers register entries in /dev which then
11035 appear automatically, which means that the system administrator does
11036 not have to create character and block special device files in the
11037 /dev directory using the mknod command (or MAKEDEV script) anymore.
11039 This is work in progress. If you want to use this, you *must* read
11040 the material in Documentation/filesystems/devfs/, especially the
11045 Enable automatic mounting at boot
11047 This option appears if you have CONFIG_DEVFS_FS enabled. Setting
11048 this to 'Y' will make the kernel automatically mount devfs onto /dev
11049 when the system is booted, before the init thread is started.
11050 You can override this with the "devfs=nomount" boot option.
11056 If you say Y here, then the /dev file system code will generate
11057 debugging messages. See the file
11058 Documentation/filesystems/devfs/boot-options for more details.
11062 NFS file system support
11064 If you are connected to some other (usually local) Unix computer
11065 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
11066 on that computer (the NFS server) using the Network File Sharing
11067 protocol, say Y. "Mounting files" means that the client can access
11068 the files with usual UNIX commands as if they were sitting on the
11069 client's hard disk. For this to work, the server must run the
11070 programs nfsd and mountd (but does not need to have NFS file system
11071 support enabled in its kernel). NFS is explained in the Network
11072 Administrator's Guide, available from
11073 http://www.linuxdoc.org/docs.html#guide , on its man page: "man
11074 nfs", and in the NFS-HOWTO.
11076 A superior but less widely used alternative to NFS is provided by
11077 the Coda file system; see "Coda file system support" below.
11079 If you say Y here, you should have said Y to TCP/IP networking also.
11080 This option would enlarge your kernel by about 27 KB.
11082 This file system is also available as a module ( = code which can be
11083 inserted in and removed from the running kernel whenever you want).
11084 The module is called nfs.o. If you want to compile it as a module,
11085 say M here and read Documentation/modules.txt.
11087 If you are configuring a diskless machine which will mount its root
11088 file system over NFS at boot time, say Y here and to "IP: kernel
11089 level autoconfiguration" above and to "Root file system on NFS"
11090 below. You cannot compile this driver as a module in this case.
11091 There are two packages designed for booting diskless machines over
11092 the net: netboot and etherboot, both available via FTP from
11093 ftp://metalab.unc.edu/pub/Linux/system/boot/ethernet/ .
11095 If you don't know what all this is about, say N.
11097 Provide NFSv3 client support (EXPERIMENTAL)
11099 Say Y here if you want your NFS client to be able to speak the newer
11100 version 3 of the NFS protocol.
11104 Root file system on NFS
11106 If you want your Linux box to mount its whole root file system (the
11107 one containing the directory /) from some other computer over the
11108 net via NFS (presumably because your box doesn't have a hard disk),
11109 say Y. Read Documentation/nfsroot.txt for details. It is likely that
11110 in this case, you also want to say Y to "IP: kernel level
11111 autoconfiguration" so that your box can discover its network address
11114 Most people say N here.
11118 If you want your Linux box to act as an NFS *server*, so that other
11119 computers on your local network which support NFS can access certain
11120 directories on your box transparently, you have two options: you can
11121 use the self-contained user space program nfsd, in which case you
11122 should say N here, or you can say Y and use the kernel based NFS
11123 server. The advantage of the kernel based solution is that it is
11126 In either case, you will need support software; the respective
11127 locations are given in the file Documentation/Changes in the NFS
11130 If you say Y here, you will get support for version 2 of the NFS
11131 protocol (NFSv2). If you also want NFSv3, say Y to the next question
11134 Please read the NFS-HOWTO, available from
11135 http://www.linuxdoc.org/docs.html#howto .
11137 The NFS server is also available as a module ( = code which can be
11138 inserted in and removed from the running kernel whenever you want).
11139 The module is called nfsd.o. If you want to compile it as a module,
11140 say M here and read Documentation/modules.txt. If unsure, say N.
11142 Provide NFSv3 server support
11144 If you would like to include the NFSv3 server as well as the NFSv2
11145 server, say Y here. If unsure, say Y.
11147 Provide NFS over TCP server support DEVELOPER ONLY
11149 If you are a developer and want to work on fixing problems with
11150 NFS server over TCP support, say Y here. If unsure, say N.
11152 Some problems can be found by looking for FIXME in net/sunrpc/svcsock.c
11154 OS/2 HPFS file system support
11156 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
11157 is the file system used for organizing files on OS/2 hard disk
11158 partitions. Say Y if you want to be able to read files from and
11159 write files to an OS/2 HPFS partition on your hard drive. OS/2
11160 floppies however are in regular MSDOS format, so you don't need this
11161 option in order to be able to read them. Read
11162 Documentation/filesystems/hpfs.txt.
11164 This file system is also available as a module ( = code which can be
11165 inserted in and removed from the running kernel whenever you want).
11166 The module is called hpfs.o. If you want to compile it as a module,
11167 say M here and read Documentation/modules.txt. If unsure, say N.
11169 NTFS support (read only)
11171 NTFS is the file system of Microsoft Windows NT. Say Y if you want
11172 to get read access to files on NTFS partitions of your hard drive.
11173 The Linux NTFS driver supports most of the mount options of the VFAT
11174 driver, see Documentation/filesystems/ntfs.txt. Saying Y here will
11175 give you read-only access to NTFS partitions.
11177 This code is also available as a module ( = code which can be
11178 inserted in and removed from the running kernel whenever you want).
11179 The module will be called ntfs.o. If you want to compile it as a
11180 module, say M here and read Documentation/modules.txt.
11182 NTFS write support (DANGEROUS)
11184 If you say Y here, you will (maybe) be able to write to NTFS file
11185 systems as well as read from them. The read-write support in
11186 NTFS is far from being complete and is not well tested. If you
11187 say Y here, back up your NTFS volume first since it may get
11188 damaged. Also, make sure to run chkdsk from within Microsoft
11189 Windows NT after having performed any writes to a NTFS partition
11190 from Linux to detect any problems as early as possible.
11191 Please note that write support is limited to Windows NT4 and
11196 System V and Coherent file system support (read only)
11198 SCO, Xenix and Coherent are commercial Unix systems for Intel
11199 machines. Saying Y here would allow you to read from their floppies
11200 and hard disk partitions. If you also want to write to these media,
11201 say Y to "SYSV file system write support" below.
11203 If you have floppies or hard disk partitions like that, it is likely
11204 that they contain binaries from those other Unix systems; in order
11205 to run these binaries, you will want to install iBCS2 (Intel Binary
11206 Compatibility Standard is a kernel module which lets you run SCO,
11207 Xenix, Wyse, UnixWare, Dell Unix and System V programs under Linux
11208 and is often needed to run commercial software that's only available
11209 for those systems. It's available via FTP (user: anonymous) from
11210 ftp://tsx-11.mit.edu/pub/linux/BETA ).
11212 If you only intend to mount files from some other Unix over the
11213 network using NFS, you don't need the System V file system support
11214 (but you need NFS file system support obviously).
11216 Note that this option is generally not needed for floppies, since a
11217 good portable way to transport files and directories between unixes
11218 (and even other operating systems) is given by the tar program ("man
11219 tar" or preferably "info tar"). Note also that this option has
11220 nothing whatsoever to do with the option "System V IPC". Read about
11221 the System V file system in Documentation/filesystems/sysv-fs.txt.
11222 Saying Y here will enlarge your kernel by about 27 KB.
11224 If you want to compile this as a module ( = code which can be
11225 inserted in and removed from the running kernel whenever you want),
11226 say M here and read Documentation/modules.txt. The module will be
11229 If you haven't heard about all of this before, it's safe to say N.
11231 SYSV file system write support (DANGEROUS)
11232 CONFIG_SYSV_FS_WRITE
11233 If you say Y here, you will be able to write to hard drive
11234 partitions and floppy disks which carry a SYSV file system used the
11235 commercial Unixes SCO, Xenix and Coherent.
11237 This support is experimental and you may destroy your data. If
11240 Amiga FFS file system support
11242 The Fast File System (FFS) is the common file system used on hard
11243 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
11244 if you want to be able to read and write files from and to an Amiga
11245 FFS partition on your hard drive. Amiga floppies however cannot be
11246 read with this driver due to an incompatibility of the floppy
11247 controller used in an Amiga and the standard floppy controller in
11248 PCs and workstations. Read Documentation/filesystems/affs.txt and
11251 With this driver you can also mount disk files used by Bernd
11252 Schmidt's Un*X Amiga Emulator (http://www.freiburg.linux.de/~uae/ ).
11253 If you want to do this, you will also need to say Y or M to "Loop
11254 device support", above.
11256 This file system is also available as a module ( = code which can be
11257 inserted in and removed from the running kernel whenever you want).
11258 The module is called affs.o. If you want to compile it as a module,
11259 say M here and read Documentation/modules.txt. If unsure, say N.
11261 Apple Macintosh file system support (EXPERIMENTAL)
11263 If you say Y here, you will be able to mount Macintosh-formatted
11264 floppy disks and hard drive partitions with full read-write access.
11265 Please read fs/hfs/HFS.txt to learn about the available mount
11268 This file system support is also available as a module ( = code
11269 which can be inserted in and removed from the running kernel
11270 whenever you want). The module is called hfs.o. If you want to
11271 compile it as a module, say M here and read
11272 Documentation/modules.txt.
11274 ROM file system support
11276 This is a very small read-only file system mainly intended for
11277 initial ram disks of installation disks, but it could be used for
11278 other read-only media as well. Read
11279 Documentation/filesystems/romfs.txt for details.
11281 This file system support is also available as a module ( = code
11282 which can be inserted in and removed from the running kernel
11283 whenever you want). The module is called romfs.o. If you want to
11284 compile it as a module, say M here and read
11285 Documentation/modules.txt. Note that the file system of your root
11286 partition (the one containing the directory /) cannot be a module.
11288 If you don't know whether you need it, then you don't need it:
11291 QNX4 file system support (read only) (EXPERIMENTAL)
11293 This is the file system used by the operating system QNX 4. Say Y if
11294 you intend to mount QNX hard disks or floppies. Unless you say Y to
11295 "QNX4FS read-write support" below, you will only be able to read
11296 these file systems.
11298 This file system support is also available as a module ( = code
11299 which can be inserted in and removed from the running kernel
11300 whenever you want). The module is called qnx4.o. If you want to
11301 compile it as a module, say M here and read
11302 Documentation/modules.txt.
11304 If you don't know whether you need it, then you don't need it:
11307 QNX4FS write support (DANGEROUS)
11309 Say Y if you want to test write support for QNX4 file systems.
11311 Kernel automounter support
11313 The automounter is a tool to automatically mount remote file systems
11314 on demand. This implementation is partially kernel-based to reduce
11315 overhead in the already-mounted case; this is unlike the BSD
11316 automounter (amd), which is a pure user space daemon.
11318 To use the automounter you need the user-space tools from the autofs
11319 package; you can find the location in Documentation/Changes. You
11320 also want to answer Y to "NFS file system support", below.
11322 If you want to use the newer version of the automounter with more
11323 features, say N here and say Y to "Kernel automounter v4 support",
11326 If you want to compile this as a module ( = code which can be
11327 inserted in and removed from the running kernel whenever you want),
11328 say M here and read Documentation/modules.txt. The module will be
11331 If you are not a part of a fairly large, distributed network, you
11332 probably do not need an automounter, and can say N here.
11334 Kernel automounter v4 support
11336 The automounter is a tool to automatically mount remote file systems
11337 on demand. This implementation is partially kernel-based to reduce
11338 overhead in the already-mounted case; this is unlike the BSD
11339 automounter (amd), which is a pure user space daemon.
11341 To use the automounter you need the user-space tools from
11342 ftp://ftp.kernel.org/pub/linux/daemons/autofs/testing-v4 ; you also
11343 want to answer Y to "NFS file system support", below.
11345 If you want to compile this as a module ( = code which can be
11346 inserted in and removed from the running kernel whenever you want),
11347 say M here and read Documentation/modules.txt. The module will be
11348 called autofs4.o. You will need to add "alias autofs autofs4" to
11349 your modules configuration file.
11351 If you are not a part of a fairly large, distributed network or
11352 don't have a laptop which needs to dynamically reconfigure to the
11353 local network, you probably do not need an automounter, and can say
11356 EFS file system support (read-only) (EXPERIMENTAL)
11358 EFS is an older file system used for non-ISO9660 CDROMs and hard
11359 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
11360 uses the XFS file system for hard disk partitions however).
11362 This implementation only offers read-only access. If you don't know
11363 what all this is about, it's safe to say N. For more information
11364 about EFS see its home page at http://aeschi.ch.eu.org/efs/ .
11366 If you want to compile the EFS file system support as a module ( =
11367 code which can be inserted in and removed from the running kernel
11368 whenever you want), say M here and read Documentation/modules.txt.
11369 The module will be called efs.o.
11371 Journalling Flash File System (JFFS) support (EXPERIMENTAL)
11373 JFFS is a new file system designed for use on flash memory devices
11374 rather than on block devices. It was developed on the 2.0 kernel
11375 by Axis Communications AB for use on their Linux-based products,
11376 and released under GPL, then 'borrowed' and ported to work with
11377 the 2.4 kernel and the new Memory Technology Device system.
11379 The 2.4 port is experimental and not yet supported by Axis. Basically,
11380 the good bits are probably theirs, and if it's broken in 2.4 it's
11381 probably our fault. See http://www.developer.axis.com/software/jffs/
11382 for more information about JFFS.
11384 Any potential patches or queries should be sent to Axis' mailing
11385 list for JFFS: <jffs-dev@axis.com>
11387 UFS file system support (read-only)
11389 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
11390 OpenBSD and NeXTstep) use a file system called UFS. Some System V
11391 Unixes can create and mount hard disk partitions and diskettes using
11392 this file system as well. Saying Y here will allow you to read from
11393 these partitions; if you also want to write to them, say Y to the
11394 experimental "UFS file system write support", below. Please read the
11395 file Documentation/filesystems/ufs.txt for more information.
11397 If you only intend to mount files from some other Unix over the
11398 network using NFS, you don't need the UFS file system support (but
11399 you need NFS file system support obviously).
11401 Note that this option is generally not needed for floppies, since a
11402 good portable way to transport files and directories between unixes
11403 (and even other operating systems) is given by the tar program ("man
11404 tar" or preferably "info tar").
11406 When accessing NeXTstep files, you may need to convert them from the
11407 NeXT character set to the Latin1 character set; use the program
11408 recode ("info recode") for this purpose.
11410 If you want to compile the UFS file system support as a module ( =
11411 code which can be inserted in and removed from the running kernel
11412 whenever you want), say M here and read Documentation/modules.txt.
11413 The module will be called ufs.o.
11415 If you haven't heard about all of this before, it's safe to say N.
11417 UFS file system write support (DANGEROUS)
11418 CONFIG_UFS_FS_WRITE
11419 Say Y here if you want to try writing to UFS partitions. This is
11420 experimental, so you should back up your UFS partitions beforehand.
11422 Advanced partition selection
11423 CONFIG_PARTITION_ADVANCED
11424 Say Y here if you would like to use hard disks under Linux which
11425 were partitioned under an operating system running on a different
11426 architecture than your Linux system.
11428 Note that the answer to this question won't directly affect the
11429 kernel: saying N will just cause this configure script to skip all
11430 the questions about foreign partitioning schemes.
11434 Alpha OSF partition support
11435 CONFIG_OSF_PARTITION
11436 Say Y here if you would like to use hard disks under Linux which
11437 were partitioned on an Alpha machine.
11439 Macintosh partition map support
11440 CONFIG_MAC_PARTITION
11441 Say Y here if you would like to use hard disks under Linux which
11442 were partitioned on a Macintosh.
11444 PC BIOS (MSDOS partition tables) support
11445 CONFIG_MSDOS_PARTITION
11446 Say Y here if you would like to use hard disks under Linux which
11447 were partitioned on an x86 PC (not necessarily by DOS).
11449 BSD disklabel (FreeBSD partition tables) support
11450 CONFIG_BSD_DISKLABEL
11451 FreeBSD uses its own hard disk partition scheme on your PC. It
11452 requires only one entry in the primary partition table of your disk
11453 and manages it similarly to DOS extended partitions, putting in its
11454 first sector a new partition table in BSD disklabel format. Saying Y
11455 here allows you to read these disklabels and further mount FreeBSD
11456 partitions from within Linux if you have also said Y to "UFS
11457 file system support", above. If you don't know what all this is
11460 Sun partition tables support
11461 CONFIG_SUN_PARTITION
11462 Like most systems, SunOS uses its own hard disk partition table
11463 format, incompatible with all others. Saying Y here allows you to
11464 read these partition tables and further mount SunOS partitions from
11465 within Linux if you have also said Y to "UFS file system support",
11466 above. This is mainly used to carry data from a SPARC under SunOS to
11467 your Linux box via a removable medium like magneto-optical or ZIP
11468 drives; note however that a good portable way to transport files and
11469 directories between unixes (and even other operating systems) is
11470 given by the tar program ("man tar" or preferably "info tar"). If
11471 you don't know what all this is about, say N.
11473 Solaris (x86) partition table support
11474 CONFIG_SOLARIS_X86_PARTITION
11475 Like most systems, Solaris x86 uses its own hard disk partition
11476 table format, incompatible with all others. Saying Y here allows you
11477 to read these partition tables and further mount Solaris x86
11478 partitions from within Linux if you have also said Y to "UFS
11479 file system support", above.
11481 SGI partition support
11482 CONFIG_SGI_PARTITION
11483 Say Y here if you would like to be able to read the hard disk
11484 partition table format used by SGI machines.
11486 ADFS file system support (EXPERIMENTAL)
11488 The Acorn Disc Filing System is the standard file system of the
11489 RiscOS operating system which runs on Acorn's ARM-based Risc PC
11490 systems and the Acorn Archimedes range of machines. If you say Y
11491 here, Linux will be able to read from ADFS partitions on hard drives
11492 and from ADFS-formatted floppy discs. If you also want to be able to
11493 write to those devices, say Y to "ADFS write support" below.
11495 The ADFS partition should be the first partition (i.e.,
11496 /dev/[hs]d?1) on each of your drives. Please read the file
11497 Documentation/filesystems/adfs.txt for further details.
11499 This code is also available as a module called adfs.o ( = code which
11500 can be inserted in and removed from the running kernel whenever you
11501 want). If you want to compile it as a module, say M here and read
11502 Documentation/modules.txt.
11506 ADFS write support (DANGEROUS)
11508 If you say Y here, you will be able to write to ADFS partitions on
11509 hard drives and ADFS-formatted floppy disks. This is experimental
11510 codes, so if you're unsure, say N.
11512 /dev/pts file system for Unix98 PTYs
11514 You should say Y here if you said Y to "Unix98 PTY support" above.
11515 You'll then get a virtual file system which can be mounted on
11516 /dev/pts with "mount -t devpts". This, together with the pseudo
11517 terminal master multiplexer /dev/ptmx, is used for pseudo terminal
11518 support as described in The Open Group's Unix98 standard: in order
11519 to acquire a pseudo terminal, a process opens /dev/ptmx; the number
11520 of the pseudo terminal is then made available to the process and the
11521 pseudo terminal slave can be accessed as /dev/pts/<number>. What was
11522 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
11524 The GNU C library glibc 2.1 contains the requisite support for this
11525 mode of operation; you also need client programs that use the Unix98
11526 API. Please read Documentation/Changes for more information about
11527 the Unix98 pty devices.
11529 Note that the experimental "/dev file system support"
11530 (CONFIG_DEVFS_FS) is a more general facility.
11532 UnixWare slices support (EXPERIMENTAL)
11533 CONFIG_UNIXWARE_DISKLABEL
11534 Like some systems, UnixWare uses its own slice table inside a
11535 partition (VTOC - Virtual Table of Contents). Its format is
11536 incompatible with all other OSes. Saying Y here allows you to read
11537 VTOC and further mount UnixWare partitions read-only from within
11538 Linux if you have also said Y to "UFS file system support" or
11539 "System V and Coherent file system support", above.
11541 This is mainly used to carry data from a UnixWare box to your
11542 Linux box via a removable medium like magneto-optical, ZIP or
11543 removable IDE drives. Note, however, that a good portable way to
11544 transport files and directories between unixes (and even other
11545 operating systems) is given by the tar program ("man tar" or
11546 preferably "info tar").
11548 If you don't know what all this is about, say N.
11550 SMB file system support (to mount Windows shares etc.)
11552 SMB (Server Message Block) is the protocol Windows for Workgroups
11553 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
11554 files and printers over local networks. Saying Y here allows you to
11555 mount their file systems (often called "shares" in this context) and
11556 access them just like any other Unix directory. Currently, this
11557 works only if the Windows machines use TCP/IP as the underlying
11558 transport protocol, and not NetBEUI. For details, read
11559 Documentation/filesystems/smbfs.txt and the SMB-HOWTO, available
11560 from http://www.linuxdoc.org/docs.html#howto .
11562 Note: if you just want your box to act as an SMB *server* and make
11563 files and printing services available to Windows clients (which need
11564 to have a TCP/IP stack), you don't need to say Y here; you can use
11565 the program samba (available via FTP (user: anonymous) in
11566 ftp://metalab.unc.edu/pub/Linux/system/network/samba ) for that.
11568 General information about how to connect Linux, Windows machines and
11569 Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
11571 If you want to compile the SMB support as a module ( = code which
11572 can be inserted in and removed from the running kernel whenever you
11573 want), say M here and read Documentation/modules.txt. The module
11574 will be called smbfs.o. Most people say N, however.
11577 CONFIG_SMB_NLS_DEFAULT
11578 Enabling this will make smbfs use nls translations by default. You
11579 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
11580 settings and you need to give the default nls for the SMB server as
11581 CONFIG_SMB_NLS_REMOTE.
11583 The nls settings can be changed at mount time, if your smbmount
11584 supports that, using the codepage and iocharset parameters.
11586 Currently no smbmount distributed with samba supports this, it is
11587 assumed future versions will. In the meantime you can get an
11588 unofficial patch for samba 2.0.7 from:
11589 http://www.hojdpunkten.ac.se/054/samba/index.html
11591 nls support setting
11592 CONFIG_SMB_NLS_REMOTE
11593 This setting allows you to specify a default value for which
11594 codepage the server uses. If this field is left blank no
11595 translations will be done by default. The local codepage/charset
11596 default to CONFIG_NLS_DEFAULT.
11598 The nls settings can be changed at mount time, if your smbmount
11599 supports that, using the codepage and iocharset parameters.
11601 Currently no smbmount distributed with samba supports this, it is
11602 assumed future versions will. In the meantime you can get an
11603 unofficial patch for samba 2.0.7 from:
11604 http://www.hojdpunkten.ac.se/054/samba/index.html
11606 Coda file system support (advanced network fs)
11608 Coda is an advanced network file system, similar to NFS in that it
11609 enables you to mount file systems of a remote server and access them
11610 with regular Unix commands as if they were sitting on your hard
11611 disk. Coda has several advantages over NFS: support for disconnected
11612 operation (e.g. for laptops), read/write server replication,
11613 security model for authentication and encryption, persistent client
11614 caches and write back caching.
11616 If you say Y here, your Linux box will be able to act as a Coda
11617 *client*. You will need user level code as well, both for the client
11618 and server. Servers are currently user level, i.e. they need no
11619 kernel support. Please read Documentation/filesystems/coda.txt and
11620 check out the Coda home page http://www.coda.cs.cmu.edu .
11622 If you want to compile the coda client support as a module ( = code
11623 which can be inserted in and removed from the running kernel
11624 whenever you want), say M here and read Documentation/modules.txt.
11625 The module will be called coda.o.
11627 NCP file system support (to mount NetWare volumes)
11629 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
11630 used by Novell NetWare clients to talk to file servers. It is to IPX
11631 what NFS is to TCP/IP, if that helps. Saying Y here allows you to
11632 mount NetWare file server volumes and to access them just like any
11633 other Unix directory. For details, please read the file
11634 Documentation/filesystems/ncpfs.txt in the kernel source and the
11635 IPX-HOWTO from http://www.linuxdoc.org/docs.html#howto .
11637 You do not have to say Y here if you want your Linux box to act as a
11638 file *server* for Novell NetWare clients.
11640 General information about how to connect Linux, Windows machines and
11641 Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
11643 If you want to compile this as a module ( = code which can be
11644 inserted in and removed from the running kernel whenever you want),
11645 say M here and read Documentation/modules.txt. The module will be
11646 called ncpfs.o. Say N unless you are connected to a Novell network.
11649 CONFIG_NCPFS_PACKET_SIGNING
11650 NCP allows packets to be signed for stronger security. If you want
11651 security, say Y. Normal users can leave it off. To be able to use
11652 packet signing you must use ncpfs > 2.0.12.
11654 Proprietary file locking
11655 CONFIG_NCPFS_IOCTL_LOCKING
11656 Allows locking of records on remote volumes. Say N unless you have
11657 special applications which are able to utilize this locking scheme.
11659 Clear remove/delete inhibit when needed
11660 CONFIG_NCPFS_STRONG
11661 Allows manipulation of files flagged as Delete or Rename Inhibit. To
11662 use this feature you must mount volumes with the ncpmount parameter
11663 "-s" (ncpfs-2.0.12 and newer). Say Y unless you are not mounting
11664 volumes with -f 444.
11666 Use NFS namespace when available
11667 CONFIG_NCPFS_NFS_NS
11668 Allows you to utilize NFS namespace on NetWare servers. It brings
11669 you case sensitive filenames. Say Y. You can disable it at
11670 mount-time with the `-N nfs' parameter of ncpmount.
11672 Use OS2/LONG namespace when available
11673 CONFIG_NCPFS_OS2_NS
11674 Allows you to utilize OS2/LONG namespace on NetWare servers.
11675 Filenames in this namespace are limited to 255 characters, they are
11676 case insensitive, and case in names is preserved. Say Y. You can
11677 disable it at mount time with the -N os2 parameter of ncpmount.
11679 Lowercase DOS filenames on LONG namespace volume
11680 CONFIG_NCPFS_SMALLDOS
11681 If you say Y here, every filename on a NetWare server volume using
11682 the OS2/LONG namespace and created under DOS or on a volume using
11683 DOS namespace will be converted to lowercase characters.
11684 Saying N here will give you these filenames in uppercase.
11686 This is only a cosmetic option since the OS2/LONG namespace is case
11687 insensitive. The only major reason for this option is backward
11688 compatibility when moving from DOS to OS2/LONG namespace support.
11689 Long filenames (created by Win95) will not be affected.
11691 This option does not solve the problem that filenames appear
11692 differently under Linux and under Windows, since Windows does an
11693 additional conversions on the client side. You can achieve similar
11694 effects by saying Y to "Allow using of Native Language Support"
11697 Allow mounting of volume subdirectories
11698 CONFIG_NCPFS_MOUNT_SUBDIR
11699 Allows you to mount not only whole servers or whole volumes, but
11700 also subdirectories from a volume. It can be used to reexport data
11701 and so on. There is no reason to say N, so Y is recommended unless
11702 you count every byte.
11704 To utilize this feature you must use ncpfs-2.0.12 or newer.
11706 NDS authentication support
11707 CONFIG_NCPFS_NDS_DOMAINS
11708 This allows storing NDS private keys in kernel space where they
11709 can be used to authenticate another server as interserver NDS
11710 accesses need it. You must use ncpfs-2.0.12.1 or newer to utilize
11711 this feature. Say Y if you are using NDS connections to NetWare
11712 servers. Do not say Y if security is primary for you because root
11713 can read your session key (from /proc/kcore).
11715 Allow using of Native Language Support
11717 Allows you to use codepages and I/O charsets for file name
11718 translation between the server file system and input/output. This
11719 may be useful, if you want to access the server with other operating
11720 systems, e.g. Windows 95. See also NLS for more Information.
11722 To select codepages and I/O charsets use ncpfs-2.2.0.13 or newer.
11724 Symbolic links and mode permission bits
11725 CONFIG_NCPFS_EXTRAS
11726 This enables the use of symbolic links and an execute permission
11727 bit on NCPFS. The file server need not have long name space or NFS
11728 name space loaded for these to work.
11730 To use the new attributes, it is recommended to use the flags
11731 '-f 600 -d 755' on the ncpmount command line.
11733 nls default codepage
11735 The default NLS used when mounting filesystem. Currently, the valid
11737 big5, cp437, cp737, cp775, cp850, cp852, cp855, cp857, cp860, cp861,
11738 cp862, cp863, cp864, cp865, cp866, cp869, cp874, cp932, cp936,
11739 cp949, cp950, euc-jp, euc-kr, gb2312, iso8859-1, iso8859-2, iso8859-3,
11740 iso8859-4, iso8859-5, iso8859-6, iso8859-7, iso8859-8, iso8859-9,
11741 iso8859-14, iso8859-15, koi8-r, sjis
11742 If you specify a wrong value, it will use the built-in NLS; compatible
11745 If unsure, specify it as "iso8859-1".
11748 CONFIG_NLS_CODEPAGE_437
11749 The Microsoft FAT file system family can deal with filenames in
11750 native language character sets. These character sets are stored
11751 in so-called DOS codepages. You need to include the appropriate
11752 codepage if you want to be able to read/write these filenames on
11753 DOS/Windows partitions correctly. This does apply to the filenames
11754 only, not to the file contents. You can include several codepages;
11755 say Y here if you want to include the DOS codepage that is used in
11756 the United States and parts of Canada. This is recommended.
11759 CONFIG_NLS_CODEPAGE_737
11760 The Microsoft FAT file system family can deal with filenames in
11761 native language character sets. These character sets are stored
11762 in so-called DOS codepages. You need to include the appropriate
11763 codepage if you want to be able to read/write these filenames on
11764 DOS/Windows partitions correctly. This does apply to the filenames
11765 only, not to the file contents. You can include several codepages;
11766 say Y here if you want to include the DOS codepage that is used for
11767 Greek. If unsure, say N.
11770 CONFIG_NLS_CODEPAGE_775
11771 The Microsoft FAT file system family can deal with filenames in
11772 native language character sets. These character sets are stored
11773 in 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 that is used
11778 for the Baltic Rim Languages. If unsure, say N.
11781 CONFIG_NLS_CODEPAGE_850
11782 The Microsoft FAT file system family can deal with filenames in
11783 native language character sets. These character sets are stored in
11784 so-called DOS codepages. You need to include the appropriate
11785 codepage if you want to be able to read/write these filenames on
11786 DOS/Windows partitions correctly. This does apply to the filenames
11787 only, not to the file contents. You can include several codepages;
11788 say Y here if you want to include the DOS codepage that is used for
11789 much of Europe -- United Kingdom, Germany, Spain, Italy, and [add
11790 more countries here]. It has some characters useful to many European
11791 languages that are not part of the US codepage 437.
11796 CONFIG_NLS_CODEPAGE_852
11797 The Microsoft FAT file system family can deal with filenames in
11798 native language character sets. These character sets are stored in
11799 so-called DOS codepages. You need to include the appropriate
11800 codepage if you want to be able to read/write these filenames on
11801 DOS/Windows partitions correctly. This does apply to the filenames
11802 only, not to the file contents. You can include several codepages;
11803 say Y here if you want to include the Latin 2 codepage used by DOS
11804 for much of Central and Eastern Europe. It has all the required
11805 characters for these languages: Albanian, Croatian, Czech, English,
11806 Finnish, Hungarian, Irish, German, Polish, Romanian, Serbian (Latin
11807 transcription), Slovak, Slovenian, and Sorbian.
11810 CONFIG_NLS_CODEPAGE_855
11811 The Microsoft FAT file system family can deal with filenames in
11812 native language character sets. These character sets are stored in
11813 so-called DOS codepages. You need to include the appropriate
11814 codepage if you want to be able to read/write these filenames on
11815 DOS/Windows partitions correctly. This does apply to the filenames
11816 only, not to the file contents. You can include several codepages;
11817 say Y here if you want to include the DOS codepage for Cyrillic.
11820 CONFIG_NLS_CODEPAGE_857
11821 The Microsoft FAT file system family can deal with filenames in
11822 native language character sets. These character sets are stored in
11823 so-called DOS codepages. You need to include the appropriate
11824 codepage if you want to be able to read/write these filenames on
11825 DOS/Windows partitions correctly. This does apply to the filenames
11826 only, not to the file contents. You can include several codepages;
11827 say Y here if you want to include the DOS codepage for Turkish.
11830 CONFIG_NLS_CODEPAGE_860
11831 The Microsoft FAT file system family can deal with filenames in
11832 native language character sets. These character sets are stored in
11833 so-called DOS codepages. You need to include the appropriate
11834 codepage if you want to be able to read/write these filenames on
11835 DOS/Windows partitions correctly. This does apply to the filenames
11836 only, not to the file contents. You can include several codepages;
11837 say Y here if you want to include the DOS codepage for Portuguese.
11840 CONFIG_NLS_CODEPAGE_861
11841 The Microsoft FAT file system family can deal with filenames in
11842 native language character sets. These character sets are stored in
11843 so-called DOS codepages. You need to include the appropriate
11844 codepage if you want to be able to read/write these filenames on
11845 DOS/Windows partitions correctly. This does apply to the filenames
11846 only, not to the file contents. You can include several codepages;
11847 say Y here if you want to include the DOS codepage for Icelandic.
11850 CONFIG_NLS_CODEPAGE_862
11851 The Microsoft FAT file system family can deal with filenames in
11852 native language character sets. These character sets are stored in
11853 so-called DOS codepages. You need to include the appropriate
11854 codepage if you want to be able to read/write these filenames on
11855 DOS/Windows partitions correctly. This does apply to the filenames
11856 only, not to the file contents. You can include several codepages;
11857 say Y here if you want to include the DOS codepage for Hebrew.
11860 CONFIG_NLS_CODEPAGE_863
11861 The Microsoft FAT file system family can deal with filenames in
11862 native language character sets. These character sets are stored in
11863 so-called DOS codepages. You need to include the appropriate
11864 codepage if you want to be able to read/write these filenames on
11865 DOS/Windows partitions correctly. This does apply to the filenames
11866 only, not to the file contents. You can include several codepages;
11867 say Y here if you want to include the DOS codepage for Canadian
11871 CONFIG_NLS_CODEPAGE_864
11872 The Microsoft FAT file system family can deal with filenames in
11873 native language character sets. These character sets are stored in
11874 so-called DOS codepages. You need to include the appropriate
11875 codepage if you want to be able to read/write these filenames on
11876 DOS/Windows partitions correctly. This does apply to the filenames
11877 only, not to the file contents. You can include several codepages;
11878 say Y here if you want to include the DOS codepage for Arabic.
11881 CONFIG_NLS_CODEPAGE_865
11882 The Microsoft FAT file system family can deal with filenames in
11883 native language character sets. These character sets are stored in
11884 so-called DOS codepages. You need to include the appropriate
11885 codepage if you want to be able to read/write these filenames on
11886 DOS/Windows partitions correctly. This does apply to the filenames
11887 only, not to the file contents. You can include several codepages;
11888 say Y here if you want to include the DOS codepage for the Nordic
11889 European countries.
11892 CONFIG_NLS_CODEPAGE_866
11893 The Microsoft FAT file system family can deal with filenames in
11894 native language character sets. These character sets are stored in
11895 so-called DOS codepages. You need to include the appropriate
11896 codepage if you want to be able to read/write these filenames on
11897 DOS/Windows partitions correctly. This does apply to the filenames
11898 only, not to the file contents. You can include several codepages;
11899 say Y here if you want to include the DOS codepage for
11903 CONFIG_NLS_CODEPAGE_869
11904 The Microsoft FAT file system family can deal with filenames in
11905 native language character sets. These character sets are stored in
11906 so-called DOS codepages. You need to include the appropriate
11907 codepage if you want to be able to read/write these filenames on
11908 DOS/Windows partitions correctly. This does apply to the filenames
11909 only, not to the file contents. You can include several codepages;
11910 say Y here if you want to include the DOS codepage for Greek.
11913 CONFIG_NLS_CODEPAGE_874
11914 The Microsoft FAT file system family can deal with filenames in
11915 native language character sets. These character sets are stored in
11916 so-called DOS codepages. You need to include the appropriate
11917 codepage if you want to be able to read/write these filenames on
11918 DOS/Windows partitions correctly. This does apply to the filenames
11919 only, not to the file contents. You can include several codepages;
11920 say Y here if you want to include the DOS codepage for Thai.
11923 CONFIG_NLS_CODEPAGE_932
11924 The Microsoft fat filesystem family can deal with filenames in
11925 native language character sets. These character sets are stored in
11926 so-called DOS codepages. You need to include the appropriate
11927 codepage if you want to be able to read/write these filenames on
11928 DOS/Windows partitions correctly. This does apply to the filenames
11929 only, not to the file contents. You can include several codepages;
11930 say Y here if you want to include the DOS codepage for Shift-JIS
11931 or EUC-JP. To use EUC-JP, you can use 'euc-jp' as mount option or
11932 NLS Default value during kernel configuration , instead of 'cp932'
11935 CONFIG_NLS_CODEPAGE_936
11936 The Microsoft fat filesystem family can deal with filenames in
11937 native language character sets. These character sets are stored in
11938 so-called DOS codepages. You need to include the appropriate
11939 codepage if you want to be able to read/write these filenames on
11940 DOS/Windows partitions correctly. This does apply to the filenames
11941 only, not to the file contents. You can include several codepages;
11942 say Y here if you want to include the DOS codepage for Simplified
11946 CONFIG_NLS_CODEPAGE_949
11947 The Microsoft fat filesystem family can deal with filenames in
11948 native language character sets. These character sets are stored in
11949 so-called DOS codepages. You need to include the appropriate
11950 codepage if you want to be able to read/write these filenames on
11951 DOS/Windows partitions correctly. This does apply to the filenames
11952 only, not to the file contents. You can include several codepages;
11953 say Y here if you want to include the DOS codepage for UHC.
11956 CONFIG_NLS_CODEPAGE_950
11957 The Microsoft fat filesystem family can deal with filenames in
11958 native language character sets. These character sets are stored in
11959 so-called DOS codepages. You need to include the appropriate
11960 codepage if you want to be able to read/write these filenames on
11961 DOS/Windows partitions correctly. This does apply to the filenames
11962 only, not to the file contents. You can include several codepages;
11963 say Y here if you want to include the DOS codepage for Traditional
11967 CONFIG_NLS_ISO8859_1
11968 If you want to display filenames with native language characters
11969 from the Microsoft FAT file system family or from JOLIET CDROMs
11970 correctly on the screen, you need to include the appropriate
11971 input/output character sets. Say Y here for the Latin 1 character
11972 set, which covers most West European languages such as Albanian,
11973 Catalan, Danish, Dutch, English, Faeroese, Finnish, French, German,
11974 Galician, Irish, Icelandic, Italian, Norwegian, Portuguese, Spanish,
11975 and Swedish. It is also the default for the US. If unsure, say Y.
11978 CONFIG_NLS_ISO8859_2
11979 If you want to display filenames with native language characters
11980 from the Microsoft FAT file system family or from JOLIET CDROMs
11981 correctly on the screen, you need to include the appropriate
11982 input/output character sets. Say Y here for the Latin 2 character
11983 set, which works for most Latin-written Slavic and Central European
11984 languages: Czech, German, Hungarian, Polish, Rumanian, Croatian,
11988 CONFIG_NLS_ISO8859_3
11989 If you want to display filenames with native language characters
11990 from the Microsoft FAT file system family or from JOLIET CDROMs
11991 correctly on the screen, you need to include the appropriate
11992 input/output character sets. Say Y here for the Latin 3 character
11993 set, which is popular with authors of Esperanto, Galician, Maltese,
11997 CONFIG_NLS_ISO8859_4
11998 If you want to display filenames with native language characters
11999 from the Microsoft FAT file system family or from JOLIET CDROMs
12000 correctly on the screen, you need to include the appropriate
12001 input/output character sets. Say Y here for the Latin 4 character
12002 set which introduces letters for Estonian, Latvian, and
12003 Lithuanian. It is an incomplete predecessor of Latin 6.
12006 CONFIG_NLS_ISO8859_5
12007 If you want to display filenames with native language characters
12008 from the Microsoft FAT file system family or from JOLIET CDROMs
12009 correctly on the screen, you need to include the appropriate
12010 input/output character sets. Say Y here for ISO8859-5, a Cyrillic
12011 character set with which you can type Bulgarian, Byelorussian,
12012 Macedonian, Russian, Serbian, and Ukrainian. Note that the charset
12013 KOI8-R is preferred in Russia.
12016 CONFIG_NLS_ISO8859_6
12017 If you want to display filenames with native language characters
12018 from the Microsoft FAT file system family or from JOLIET CDROMs
12019 correctly on the screen, you need to include the appropriate
12020 input/output character sets. Say Y here for ISO8859-6, the Arabic
12024 CONFIG_NLS_ISO8859_7
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 ISO8859-7, the Modern
12029 Greek character set.
12032 CONFIG_NLS_ISO8859_8
12033 If you want to display filenames with native language characters
12034 from the Microsoft FAT file system family or from JOLIET CDROMs
12035 correctly on the screen, you need to include the appropriate
12036 input/output character sets. Say Y here for ISO8859-8, the Hebrew
12040 CONFIG_NLS_ISO8859_9
12041 If you want to display filenames with native language characters
12042 from the Microsoft FAT file system family or from JOLIET CDROMs
12043 correctly on the screen, you need to include the appropriate
12044 input/output character sets. Say Y here for the Latin 5 character
12045 set, and it replaces the rarely needed Icelandic letters in Latin 1
12046 with the Turkish ones. Useful in Turkey.
12049 CONFIG_NLS_ISO8859_10
12050 If you want to display filenames with native language characters
12051 from the Microsoft FAT file system family or from JOLIET CDROMs
12052 correctly on the screen, you need to include the appropriate
12053 input/output character sets. Say Y here for the Latin 6 character
12054 set, which adds the last Inuit (Greenlandic) and Sami (Lappish)
12055 letters that were missing in Latin 4 to cover the entire Nordic
12058 NLS ISO 8859-14 (Latin 8; Celtic)
12059 CONFIG_NLS_ISO8859_14
12060 If you want to display filenames with native language characters
12061 from the Microsoft FAT file system family or from JOLIET CDROMs
12062 correctly on the screen, you need to include the appropriate
12063 input/output character sets. Say Y here for the Latin 8 character
12064 set, which adds the last accented vowels for Welsh (aka Cymraeg)
12065 (and Manx Gaelic) hat were missing in Latin 1.
12066 http://linux.speech.cymru.org/ has further information.
12069 CONFIG_NLS_ISO8859_15
12070 If you want to display filenames with native language characters
12071 from the Microsoft FAT file system family or from JOLIET CDROMs
12072 correctly on the screen, you need to include the appropriate
12073 input/output character sets. Say Y here for the Latin 9 character
12074 set, which covers most West European languages such as Albanian,
12075 Catalan, Danish, Dutch, English, Estonian, Faeroese, Finnish,
12076 French, German, Galician, Irish, Icelandic, Italian, Norwegian,
12077 Portuguese, Spanish, and Swedish. Latin 9 is an update to
12078 Latin 1 (ISO 8859-1) that removes a handful of rarely used
12079 characters and instead adds support for Estonian, corrects the
12080 support for French and Finnish, and adds the new Euro character. If
12085 If you want to display filenames with native language characters
12086 from the Microsoft FAT file system family or from JOLIET CDROMs
12087 correctly on the screen, you need to include the appropriate
12088 input/output character sets. Say Y here for the preferred Russian
12093 If you say Y here, you will get support for terminal devices with
12094 display and keyboard devices. These are called "virtual" because you
12095 can run several virtual terminals (also called virtual consoles) on
12096 one physical terminal. This is rather useful, for example one
12097 virtual terminal can collect system messages and warnings, another
12098 one can be used for a text-mode user session, and a third could run
12099 an X session, all in parallel. Switching between virtual terminals
12100 is done with certain key combinations, usually Alt-<function key>.
12102 The setterm command ("man setterm") can be used to change the
12103 properties (such as colors or beeping) of a virtual terminal. The
12104 man page console_codes(4) ("man console_codes") contains the special
12105 character sequences that can be used to change those properties
12106 directly. The fonts used on virtual terminals can be changed with
12107 the setfont ("man setfont") command and the key bindings are defined
12108 with the loadkeys ("man loadkeys") command.
12110 You need at least one virtual terminal device in order to make use
12111 of your keyboard and monitor. Therefore, only people configuring an
12112 embedded system would want to say N here in order to save some
12113 memory; the only way to log into such a system is then via a serial
12114 or network connection.
12116 If unsure, say Y, or else you won't be able to do much with your new
12117 shiny Linux system :-)
12119 Support for console on virtual terminal
12121 The system console is the device which receives all kernel messages
12122 and warnings and which allows logins in single user mode. If you
12123 answer Y here, a virtual terminal (the device used to interact with
12124 a physical terminal) can be used as system console. This is the most
12125 common mode of operations, so you should say Y here unless you want
12126 the kernel messages be output only to a serial port (in which case
12127 you should say Y to "Console on serial port", below).
12129 If you do say Y here, by default the currently visible virtual
12130 terminal (/dev/tty0) will be used as system console. You can change
12131 that with a kernel command line option such as "console=tty3" which
12132 would use the third virtual terminal as system console. (Try "man
12133 bootparam" or see the documentation of your boot loader (lilo or
12134 loadlin) about how to pass options to the kernel at boot time.)
12138 Support for PowerMac keyboard
12139 CONFIG_MAC_KEYBOARD
12140 This option allows you to use an ADB keyboard attached to your
12141 machine. Note that this disables any other (ie. PS/2) keyboard
12142 support, even if your machine is physically capable of using both at
12145 If you use an ADB keyboard (4 pin connector), say Y here.
12146 If you use a PS/2 keyboard (6 pin connector), say N here.
12148 Standard/generic serial support
12150 This selects whether you want to include the driver for the standard
12151 serial ports. The standard answer is Y. People who might say N here
12152 are those that are setting up dedicated Ethernet WWW/FTP servers, or
12153 users that have one of the various bus mice instead of a serial
12154 mouse and don't intend to use their machine's standard serial port
12155 for anything. (Note that the Cyclades and Stallion multi serial port
12156 drivers do not need this driver built in for them to work.)
12158 If you want to compile this driver as a module, say M here and read
12159 Documentation/modules.txt. The module will be called serial.o.
12160 [WARNING: Do not compile this driver as a module if you are using
12161 non-standard serial ports, since the configuration information will
12162 be lost when the driver is unloaded. This limitation may be lifted
12165 BTW1: If you have a mouseman serial mouse which is not recognized by
12166 the X window system, try running gpm first.
12168 BTW2: If you intend to use a software modem (also called Winmodem)
12169 under Linux, forget it. These modems are crippled and require
12170 proprietary drivers which are only available under Windows.
12172 Most people will say Y or M here, so that they can use serial mice,
12173 modems and similar devices connecting to the standard serial ports.
12175 Support for console on serial port
12176 CONFIG_SERIAL_CONSOLE
12177 If you say Y here, it will be possible to use a serial port as the
12178 system console (the system console is the device which receives all
12179 kernel messages and warnings and which allows logins in single user
12180 mode). This could be useful if some terminal or printer is connected
12181 to that serial port.
12183 Even if you say Y here, the currently visible virtual console
12184 (/dev/tty0) will still be used as the system console by default, but
12185 you can alter that using a kernel command line option such as
12186 "console=ttyS1". (Try "man bootparam" or see the documentation of
12187 your boot loader (lilo or loadlin) about how to pass options to the
12188 kernel at boot time.)
12190 If you don't have a VGA card installed and you say Y here, the
12191 kernel will automatically use the first serial line, /dev/ttyS0, as
12196 Support for PowerMac serial ports
12198 If you have Macintosh style serial ports (8 pin mini-DIN), say Y
12199 here. If you also have regular serial ports and enable the driver
12200 for them, you can't currently use the serial console feature.
12202 Comtrol Rocketport support
12204 This is a driver for the Comtrol Rocketport cards which provide
12205 multiple serial ports. You would need something like this to connect
12206 more than two modems to your Linux box, for instance in order to
12207 become a dial-in server.
12209 If you want to compile this driver as a module, say M here and read
12210 Documentation/modules.txt. The module will be called rocket.o.
12212 Digiboard Intelligent async support
12214 This is a driver for Digi International's Xx, Xeve, and Xem series
12215 of cards which provide multiple serial ports. You would need
12216 something like this to connect more than two modems to your Linux
12217 box, for instance in order to become a dial-in server. This driver
12218 supports the original PC (ISA) boards as well as PCI, and EISA. If
12219 you have a card like this, say Y here and read the file
12220 Documentation/digiepca.txt.
12222 NOTE: There is another, separate driver for the Digiboard PC boards:
12223 "Digiboard PC/Xx Support" below. You should (and can) only select
12224 one of the two drivers.
12226 If you want to compile this driver as a module, say M here and read
12227 Documentation/modules.txt. The module will be called epca.o.
12229 Digiboard PC/Xx Support
12231 This is a driver for the Digiboard PC/Xe, PC/Xi, and PC/Xeve cards
12232 that give you many serial ports. You would need something like this
12233 to connect more than two modems to your Linux box, for instance in
12234 order to become a dial-in server. If you have a card like that, say
12235 Y here and read the file Documentation/digiboard.txt.
12237 If you want to compile this driver as a module, say M here and read
12238 Documentation/modules.txt. The module will be called pcxx.o.
12240 SDL RISCom/8 card support
12242 This is a driver for the SDL Communications RISCom/8 multiport card,
12243 which gives you many serial ports. You would need something like
12244 this to connect more than two modems to your Linux box, for instance
12245 in order to become a dial-in server. If you have a card like that,
12246 say Y here and read the file Documentation/riscom8.txt.
12248 Also it's possible to say M here and compile this driver as kernel
12249 loadable module; the module will be called riscom8.o.
12251 Computone IntelliPort Plus serial support
12253 This driver supports the entire family of Intelliport II/Plus
12254 controllers with the exception of the MicroChannel controllers and
12255 products previous to the Intelliport II. These are multiport cards,
12256 which give you many serial ports. You would need something like
12257 this to connect more than two modems to your Linux box, for
12258 instance in order to become a dial-in server. If you have a
12259 card like that, say Y here and read Documentation/computone.txt.
12261 If you want to compile this as a module ( = code which can be
12262 inserted in and removed from the running kernel whenever you want),
12263 say M here and read Documentation/modules.txt. You will get two
12264 modules called ip2.o and ip2main.o.
12266 Specialix IO8+ card support
12268 This is a driver for the Specialix IO8+ multiport card (both the
12269 ISA and the PCI version) which gives you many serial ports. You
12270 would need something like this to connect more than two modems to
12271 your Linux box, for instance in order to become a dial-in server.
12273 If you have a card like that, say Y here and read the file
12274 Documentation/specialix.txt. Also it's possible to say M here and
12275 compile this driver as kernel loadable module which will be called
12278 Specialix DTR/RTS pin is RTS
12279 CONFIG_SPECIALIX_RTSCTS
12280 The Specialix card can only support either RTS or DTR. If you say N
12281 here, the driver will use the pin as "DTR" when the tty is in
12282 software handshake mode. If you say Y here or hardware handshake is
12283 on, it will always be RTS. Read the file Documentation/specialix.txt
12284 for more information.
12286 Cyclades async mux support
12288 This is a driver for a card that gives you many serial ports. You
12289 would need something like this to connect more than two modems to
12290 your Linux box, for instance in order to become a dial-in server.
12291 For information about the Cyclades-Z card, read
12292 drivers/char/README.cycladesZ.
12294 As of 1.3.9x kernels, this driver's minor numbers start at 0 instead
12297 If you want to compile this as a module ( = code which can be
12298 inserted in and removed from the running kernel whenever you want),
12299 say M here and read Documentation/modules.txt. The module will be
12302 If you haven't heard about it, it's safe to say N.
12304 Cyclades-Z interrupt mode operation (EXPERIMENTAL)
12306 The Cyclades-Z family of multiport cards allows 2 (two) driver op
12307 modes: polling and interrupt. In polling mode, the driver will check
12308 the status of the Cyclades-Z ports every certain amount of time
12309 (which is called polling cycle and is configurable). In interrupt
12310 mode, it will use an interrupt line (IRQ) in order to check the
12311 status of the Cyclades-Z ports. The default op mode is polling. If
12314 Stallion multiport serial support
12316 Stallion cards give you many serial ports. You would need something
12317 like this to connect more than two modems to your Linux box, for
12318 instance in order to become a dial-in server. If you say Y here, you
12319 will be asked for your specific card model in the next questions.
12320 Make sure to read drivers/char/README.stallion in this case. If you
12321 have never heard about all this, it's safe to say N.
12323 Stallion EasyIO or EC8/32 support
12325 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
12326 card, then this is for you; say Y. Make sure to read
12327 Documentation/stallion.txt.
12329 If you want to compile this as a module ( = code which can be
12330 inserted in and removed from the running kernel whenever you want),
12331 say M here and read Documentation/modules.txt. The module will be
12334 Stallion EC8/64, ONboard, Brumby support
12336 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
12337 serial multiport card, say Y here. Make sure to read
12338 Documentation/stallion.txt.
12340 To compile it as a module ( = code which can be inserted in and
12341 removed from the running kernel whenever you want), say M here and
12342 read Documentation/modules.txt. The module will be called
12345 Microgate SyncLink adapter support
12347 Provides support for the SyncLink ISA and PCI
12348 multiprotocol serial adapters. These adapters
12349 support asynchronous and HDLC bit synchronous
12350 communication up to 10Mbps (PCI adapter).
12352 This driver can only be built as a module ( = code which can be
12353 inserted in and removed from the running kernel whenever you want).
12354 The module will be called synclink.o. If you want to do that, say M
12357 Synchronous HDLC line discipline support
12359 Allows synchronous HDLC communications with tty device drivers that
12360 support synchronous HDLC such as the Microgate SyncLink adapter.
12362 This driver can only be built as a module ( = code which can be
12363 inserted in and removed from the running kernel whenever you want).
12364 The module will be called n_hdlc.o. If you want to do that, say M
12367 Specialix SX (and SI) card support
12369 This is a driver for the SX and SI multiport serial cards.
12370 Please read the file Documentation/sx.txt for details.
12372 This driver can only be built as a module ( = code which can be
12373 inserted in and removed from the running kernel whenever you want).
12374 The module will be called sx.o. If you want to do that, say M here.
12376 Hayes ESP serial port support
12378 This is a driver which supports Hayes ESP serial ports. Both single
12379 port cards and multiport cards are supported. Make sure to read
12380 Documentation/hayes-esp.txt.
12382 To compile this driver as a module ( = code which can be inserted in
12383 and removed from the running kernel whenever you want), say M here
12384 and read Documentation/modules.txt. The module will be called esp.o.
12387 Moxa Intellio support
12388 CONFIG_MOXA_INTELLIO
12389 Say Y here if you have a Moxa Intellio multiport serial card.
12391 This driver can also be built as a module ( = code which can be
12392 inserted in and removed from the running kernel whenever you want).
12393 The module will be called moxa.o. If you want to do that, say M
12396 Moxa SmartIO support
12397 CONFIG_MOXA_SMARTIO
12398 Say Y here if you have a Moxa SmartIO multiport serial card.
12400 This driver can also be built as a module ( = code which can be
12401 inserted in and removed from the running kernel whenever you want).
12402 The module will be called mxser.o. If you want to do that, say M
12405 Multi-Tech multiport card support (EXPERIMENTAL)
12407 This is a driver for the Multi-Tech cards which provide several
12408 serial ports. The driver is experimental and can currently only be
12409 built as a module ( = code which can be inserted in and removed from
12410 the running kernel whenever you want). Please read
12411 Documentation/modules.txt. The module will be called isicom.o
12415 A pseudo terminal (PTY) is a software device consisting of two
12416 halves: a master and a slave. The slave device behaves identical to
12417 a physical terminal; the master device is used by a process to
12418 read data from and write data to the slave, thereby emulating a
12419 terminal. Typical programs for the master side are telnet servers
12422 Linux has traditionally used the BSD-like names /dev/ptyxx for
12423 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
12424 has a number of problems. The GNU C library glibc 2.1 and later,
12425 however, supports the Unix98 naming standard: in order to acquire a
12426 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
12427 terminal is then made available to the process and the pseudo
12428 terminal slave can be accessed as /dev/pts/<number>. What was
12429 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
12431 The entries in /dev/pts/ are created on the fly by a virtual
12432 file system; therefore, if you say Y here you should say Y to
12433 "/dev/pts file system for Unix98 PTYs" as well.
12435 If you want to say Y here, you need to have the C library glibc 2.1
12436 or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
12437 Read the instructions in Documentation/Changes pertaining to pseudo
12438 terminals. It's safe to say N.
12440 Maximum number of Unix98 PTYs in use (0-2048)
12441 CONFIG_UNIX98_PTY_COUNT
12442 The maximum number of Unix98 PTYs that can be used at any one time.
12443 The default is 256, and should be enough for desktop systems. Server
12444 machines which support incoming telnet/rlogin/ssh connections and/or
12445 serve several X terminals may want to increase this: every incoming
12446 connection and every xterm uses up one PTY.
12448 When not in use, each additional set of 256 PTYs occupy
12449 approximately 8 KB of kernel memory on 32-bit architectures.
12451 Parallel printer support
12453 If you intend to attach a printer to the parallel port of your Linux
12454 box (as opposed to using a serial printer; if the connector at the
12455 printer has 9 or 25 holes ["female"], then it's serial), say Y. Also
12456 read the Printing-HOWTO, available from
12457 http://www.linuxdoc.org/docs.html#howto .
12459 It is possible to share one parallel port among several devices
12460 (e.g. printer and ZIP drive) and it is safe to compile the
12461 corresponding drivers into the kernel. If you want to compile this
12462 driver as a module however ( = code which can be inserted in and
12463 removed from the running kernel whenever you want), say M here and
12464 read Documentation/modules.txt and Documentation/parport.txt. The
12465 module will be called lp.o.
12467 If you have several parallel ports, you can specify which ports to
12468 use with the "lp" kernel command line option. (Try "man bootparam"
12469 or see the documentation of your boot loader (lilo or loadlin) about
12470 how to pass options to the kernel at boot time.) The syntax of the
12471 "lp" command line option can be found in drivers/char/lp.c.
12473 If you have more than 3 printers, you need to increase the LP_NO
12476 Support for console on line printer
12478 If you want kernel messages to be printed out as they occur, you
12479 can have a console on the printer. This option adds support for
12480 doing that; to actually get it to happen you need to pass the
12481 option "console=lp0" to the kernel at boot time.
12483 Note that kernel messages can get lost if the printer is out of
12484 paper (or off, or unplugged, or too busy..), but this behaviour
12485 can be changed. See drivers/char/lp.c (do this at your own risk).
12489 Support for user-space parallel port device drivers
12491 Saying Y to this adds support for /dev/parport device nodes. This
12492 is needed for programs that want portable access to the parallel
12493 port, for instance deviceid (which displays Plug-and-Play device
12496 This is the parallel port equivalent of SCSI generic support (sg).
12497 It is safe to say N to this -- it is not needed for normal printing
12498 or parallel port CD-ROM/disk support.
12500 This support is also available as a module. If you want to compile
12501 it as a module, say M here and read Documentation/modules.txt. The
12502 module will be called ppdev.o.
12508 I2C (pronounce: I-square-C) is a slow serial bus protocol used in
12509 many micro controller applications and developed by Philips. SMBus,
12510 or System Management Bus is a subset of the I2C protocol. More
12511 information is contained in the directory Documentation/i2c/,
12512 especially in the file called "summary" there.
12514 Both I2C and SMBus are supported here. You will need this for
12515 hardware sensors support, and also for Video for Linux support.
12516 Specifically, if you want to use a BT848 based frame grabber/overlay
12517 boards under Linux, say Y here and also to "I2C bit-banging
12518 interfaces", below.
12520 If you want I2C support, you should say Y here and also to the
12521 specific driver for your bus adapter(s) below. If you say Y to
12522 "/proc file system" below, you will then get a /proc interface which
12523 is documented in Documentation/i2c/proc-interface.
12525 This I2C support is also available as a module. If you want to
12526 compile it as a module, say M here and read
12527 Documentation/modules.txt. The module will be called i2c-core.o.
12529 I2C bit-banging interfaces
12531 This allows you to use a range of I2C adapters called bit-banging
12532 adapters. Say Y if you own an I2C adapter belonging to this class
12533 and then say Y to the specific driver for you adapter below.
12535 This support 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-algo-bit.o.
12539 Philips style parallel port adapter
12540 CONFIG_I2C_PHILIPSPAR
12541 This supports parallel-port I2C adapters made by Philips. Say Y if
12542 you own such an adapter.
12544 This driver is also available as a module. If you want to compile
12545 it as a module, say M here and read Documentation/modules.txt. The
12546 module will be called i2c-philips-par.o.
12548 Note that if you want support for different parallel port devices,
12549 life will be much easier if you compile them all as modules.
12553 This supports parallel-port I2C adapters called ELV. Say Y if you
12554 own such an adapter.
12556 This driver is also available as a module. If you want to compile
12557 it as a module, say M here and read Documentation/modules.txt. The
12558 module will be called i2c-elv.o.
12560 Velleman K9000 adapter
12561 CONFIG_I2C_VELLEMAN
12562 This supports the Velleman K9000 parallel-port I2C adapter. Say Y if
12563 you own such an adapter.
12565 This driver is also available as a module. If you want to compile
12566 it as a module, say M here and read Documentation/modules.txt. The
12567 module will be called i2c-velleman.o.
12569 I2C PCF 8584 interfaces
12571 This allows you to use a range of I2C adapters called PCF adapters.
12572 Say Y if you own an I2C adapter belonging to this class and then say
12573 Y to the specific driver for you adapter below.
12575 This support is also available as a module. If you want to compile
12576 it as a module, say M here and read Documentation/modules.txt. The
12577 module will be called i2c-algo-pcf.o.
12581 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own such
12584 This driver is also available as a module. If you want to compile
12585 it as a module, say M here and read Documentation/modules.txt. The
12586 module will be called i2c-elektor.o.
12588 I2C device interface
12590 Say Y here to use i2c-* device files, usually found in the /dev
12591 directory on your system. They make it possible to have user-space
12592 programs use the I2C bus. Information on how to do this is contained
12593 in the file Documentation/i2c/dev-interface.
12595 This code is also available as a module. If you want to compile
12596 it as a module, say M here and read Documentation/modules.txt. The
12597 module will be called i2c-dev.o.
12601 Say Y here if your machine has a bus mouse as opposed to a serial
12602 mouse. Most people have a regular serial MouseSystem or
12603 Microsoft mouse (made by Logitech) that plugs into a COM port
12604 (rectangular with 9 or 25 pins). These people say N here. If you
12605 have something else, read the Busmouse-HOWTO, available from
12606 http://www.linuxdoc.org/docs.html#howto , and say Y here.
12608 If you have a laptop, you either have to check the documentation or
12609 experiment a bit to find out whether the trackball is a serial mouse
12610 or not; it's best to say Y here for you.
12612 This is the generic bus mouse driver code. If you have a bus mouse,
12613 you will have to say Y here and also to the specific driver for your
12616 This code is also available as a module ( = code which can be
12617 inserted in and removed from the running kernel whenever you want).
12618 The module will be called busmouse.o. If you want to compile it as a
12619 module, say M here and read Documentation/modules.txt.
12621 Mouse Support (not serial and bus mice)
12623 This is for machines with a mouse which is neither a serial nor a
12624 bus mouse. Examples are PS/2 mice (such as the track balls on some
12625 laptops) and some digitizer pads. Most people have a regular serial
12626 MouseSystem or Microsoft mouse (made by Logitech) that plugs into a
12627 COM port (rectangular with 9 or 25 pins). These people say N here.
12628 If you have something else, read the Busmouse-HOWTO, available from
12629 http://www.linuxdoc.org/docs.html#howto . This HOWTO contains
12630 information about all non-serial mice, not just bus mice.
12632 If you have a laptop, you either have to check the documentation or
12633 experiment a bit to find out whether the trackball is a serial mouse
12634 or not; it's best to say Y here for you.
12636 Note that the answer to this question won't directly affect the
12637 kernel: saying N will just cause this configure script to skip all
12638 the questions about non-serial mice. If unsure, say Y.
12640 Logitech busmouse support
12641 CONFIG_LOGIBUSMOUSE
12642 Logitech mouse connected to a proprietary interface card. It's
12643 generally a round connector with 9 pins. Note that the newer mice
12644 made by Logitech don't use the Logitech protocol anymore; for those,
12645 you don't need this option. You want to read the Busmouse-HOWTO ,
12646 available from http://www.linuxdoc.org/docs.html#howto .
12648 If you want to compile this as a module ( = code which can be
12649 inserted in and removed from the running kernel whenever you want),
12650 say M here and read Documentation/modules.txt. The module will be
12651 called busmouse.o. If you are unsure, say N and read the HOWTO
12652 nevertheless: it will tell you what you have.
12654 PS/2 mouse (aka "auxiliary device") support
12656 The PS/2 mouse connects to a special mouse port that looks much like
12657 the keyboard port (small circular connector with 6 pins). This way,
12658 the mouse does not use any serial ports. This port can also be used
12659 for other input devices like light pens, tablets, keypads. Compaq,
12660 AST and IBM all use this as their mouse port on currently shipping
12661 machines. The trackballs of some laptops are PS/2 mice also. In
12662 particular, the C&T 82C710 mouse on TI Travelmates is a PS/2 mouse.
12664 Although PS/2 mice are not technically bus mice, they are explained
12665 in detail in the Busmouse-HOWTO, available from
12666 http://www.linuxdoc.org/docs.html#howto .
12668 When using a PS/2 mouse, you can get problems if you want to use the
12669 mouse both on the Linux console and under X. Using the "-R" option
12670 of the Linux mouse managing program gpm (available from
12671 ftp://metalab.unc.edu/pub/Linux/system/mouse ) solves this
12672 problem, or you can get the "mconv2" utility from the same location.
12674 C&T 82C710 mouse port support (as on TI Travelmate)
12675 CONFIG_82C710_MOUSE
12676 This is a certain kind of PS/2 mouse used on the TI Travelmate. If
12677 you are unsure, try first to say N here and come back if the mouse
12678 doesn't work. Read the Busmouse-HOWTO, available from
12679 http://www.linuxdoc.org/docs.html#howto .
12681 PC110 digitizer pad support
12683 This drives the digitizer pad on the IBM PC110 palmtop. It can turn
12684 the digitizer pad into a PS/2 mouse emulation with tap gestures or
12685 into an absolute pad.
12687 If you want to compile this as a module ( = code which can be
12688 inserted in and removed from the running kernel whenever you want),
12689 say M here and read Documentation/modules.txt. The module will be
12692 Microsoft busmouse support
12694 These animals (also called Inport mice) are connected to an
12695 expansion board using a round connector with 9 pins. If this is what
12696 you have, say Y and read the Busmouse-HOWTO, available from
12697 http://www.linuxdoc.org/docs.html#howto .
12699 If you are unsure, say N and read the HOWTO nevertheless: it will
12700 tell you what you have. Also be aware that several vendors talk
12701 about 'Microsoft busmouse' and actually mean PS/2 busmouse -- so
12702 count the pins on the connector.
12704 If you want to compile this as a module ( = code which can be
12705 inserted in and removed from the running kernel whenever you want),
12706 say M here and read Documentation/modules.txt. The module will be
12707 called msbusmouse.o.
12709 Apple Desktop Bus mouse support
12711 Say Y here if you have this type of bus mouse (4 pin connector) as
12712 is common on Macintoshes. You may want to read the Busmouse-HOWTO,
12713 available from http://www.linuxdoc.org/docs.html#howto .
12715 If you want to compile this as a module ( = code which can be
12716 inserted in and removed from the running kernel whenever you want),
12717 say M here and read Documentation/modules.txt. The module will be
12720 ATIXL busmouse support
12721 CONFIG_ATIXL_BUSMOUSE
12722 This is a rare type of busmouse that is connected to the back of an
12723 ATI video card. Say Y if you have one of those. Note however that
12724 most mice by ATI are actually Microsoft busmice; you should say Y to
12725 "Microsoft busmouse support" above if you have one of those. Read
12726 the Busmouse-HOWTO, available from
12727 http://www.linuxdoc.org/docs.html#howto .
12729 If you want to compile this as a module ( = code which can be
12730 inserted in and removed from the running kernel whenever you want),
12731 say M here and read Documentation/modules.txt. The module will be
12732 called atixlmouse.o.
12734 If you are unsure, say N and read the HOWTO nevertheless: it will
12735 tell you what you have.
12737 QIC-02 tape support
12739 If you have a non-SCSI tape drive like that, say Y. Or, if you want
12740 to compile this driver as a module ( = code which can be inserted in
12741 and removed from the running kernel whenever you want), say M here
12742 and read Documentation/modules.txt. The module will be called
12745 Do you want runtime configuration for QIC-02
12746 CONFIG_QIC02_DYNCONF
12747 You can either configure this driver once and for all by editing a
12748 header file (include/linux/tpqic02.h), in which case you should
12749 say N, or you can fetch a program via anonymous FTP which is able
12750 to configure this driver during runtime. The program to do this is
12751 called 'qic02conf' and it is part of the tpqic02-support-X.Y.tar.gz
12754 If you want to use the qic02conf program, say Y.
12756 Floppy tape drive (QIC-80/40/3010/3020/TR-1/TR-2/TR-3) support
12758 If you have a tape drive that is connected to your floppy
12759 controller, say Y here.
12761 Some tape drives (like the Seagate "Tape Store 3200" or the Iomega
12762 "Ditto 3200" or the Exabyte "Eagle TR-3") come with a "high speed"
12763 controller of their own. These drives (and their companion
12764 controllers) are also supported if you say Y here.
12766 If you have a special controller (such as the CMS FC-10, FC-20,
12767 Mountain Mach-II, or any controller that is based on the Intel 82078
12768 FDC like the high speed controllers by Seagate and Exabyte and
12769 Iomega's "Ditto Dash") you must configure it by selecting the
12770 appropriate entries from the "Floppy tape controllers" sub-menu
12771 below and possibly modify the default values for the IRQ and DMA
12772 channel and the IO base in ftape's configuration menu.
12774 If you want to use your floppy tape drive on a PCI-bus based system,
12775 please read the file drivers/char/ftape/README.PCI.
12777 The ftape kernel driver is also available as a runtime loadable
12778 module ( = code which can be inserted in and removed from the
12779 running kernel whenever you want). If you want to compile it as a
12780 module, say M here and read Documentation/modules.txt. The module
12781 will be called ftape.o.
12783 Note that the Ftape-HOWTO is out of date (sorry) and documents the
12784 older version 2.08 of this software but still contains useful
12785 information. There is a web page with more recent documentation at
12786 http://www.math1.rwth-aachen.de/~heine/ftape/ . This page
12787 always contains the latest release of the ftape driver and useful
12788 information (backup software, ftape related patches and
12789 documentation, FAQ). Note that the file system interface has changed
12790 quite a bit compared to previous versions of ftape. Please read
12791 Documentation/ftape.txt.
12793 The file system interface for ftape
12795 Normally, you want to say Y or M. DON'T say N here or you
12796 WON'T BE ABLE TO USE YOUR FLOPPY TAPE DRIVE.
12798 The ftape module itself no longer contains the routines necessary
12799 to interface with the kernel VFS layer (i.e. to actually write data
12800 to and read data from the tape drive). Instead the file system
12801 interface (i.e. the hardware independent part of the driver) has
12802 been moved to a separate module.
12804 If you say M zftape will be compiled as a runtime loadable
12805 module ( = code which can be inserted in and removed from the
12806 running kernel whenever you want). In this case you should read
12807 Documentation/modules.txt. The module will be called zftape.o.
12809 Regardless of whether you say Y or M here, an additional runtime
12810 loadable module called `zft-compressor.o' which contains code to
12811 support user transparent on-the-fly compression based on Ross
12812 William's lzrw3 algorithm will be produced. If you have enabled the
12813 kernel module loader (i.e. have said Y to "Kernel module loader
12814 support", above) then `zft-compressor.o' will be loaded
12815 automatically by zftape when needed.
12817 Despite its name, zftape does NOT use compression by default. The
12818 file Documentation/ftape.txt contains a short description of the
12819 most important changes in the file system interface compared to
12820 previous versions of ftape. The ftape home page
12821 http://www-math.math.rwth-aachen.de/~LBFM/claus/ftape/ contains
12822 further information.
12824 IMPORTANT NOTE: zftape can read archives created by previous
12825 versions of ftape and provide file mark support (i.e. fast skipping
12826 between tape archives) but previous version of ftape will lack file
12827 mark support when reading archives produced by zftape.
12829 Default block size for zftape
12830 CONFIG_ZFT_DFLT_BLK_SZ
12831 If unsure leave this at its default value, i.e. 10240. Note that
12832 you specify only the default block size here. The block size can be
12833 changed at run time using the MTSETBLK tape operation with the
12834 MTIOCTOP ioctl (i.e. with "mt -f /dev/qft0 setblk #BLKSZ" from the
12835 shell command line).
12837 The probably most striking difference between zftape and previous
12838 versions of ftape is the fact that all data must be written or read
12839 in multiples of a fixed block size. The block size defaults to
12840 10240 which is what GNU tar uses. The values for the block size
12841 should be either 1 or multiples of 1024 up to a maximum value of
12842 63488 (i.e. 62 K). If you specify `1' then zftape's builtin
12843 compression will be disabled.
12845 Reasonable values are `10240' (GNU tar's default block size),
12846 `5120' (afio's default block size), `32768' (default block size some
12847 backup programs assume for SCSI tape drives) or `1' (no restriction
12848 on block size, but disables builtin compression).
12850 Number of DMA buffers
12851 CONFIG_FT_NR_BUFFERS
12852 Please leave this at `3' unless you REALLY know what you are doing.
12853 It is not necessary to change this value. Values below 3 make the
12854 proper use of ftape impossible, values greater than 3 are a waste of
12855 memory. You can change the amount of DMA memory used by ftape at
12856 runtime with "mt -f /dev/qft0 setdrvbuffer #NUMBUFFERS". Each buffer
12857 wastes 32 KB of memory. Please note that this memory cannot be
12860 Procfs entry for ftape
12862 Optional. Saying Y will result in creation of a directory
12863 `/proc/ftape' under the /proc file system. The files can be viewed
12864 with your favorite pager (i.e. use "more /proc/ftape/history" or
12865 "less /proc/ftape/history" or simply "cat /proc/ftape/history"). The
12866 file will contain some status information about the inserted
12867 cartridge, the kernel driver, your tape drive, the floppy disk
12868 controller and the error history for the most recent use of the
12869 kernel driver. Saying Y will enlarge the size of the ftape driver
12870 by approximately 2 KB.
12872 WARNING: When compiling ftape as a module (i.e. saying M to "Floppy
12873 tape drive") it is dangerous to use ftape's /proc file system
12874 interface. Accessing `/proc/ftape' while the module is unloaded will
12875 result in a kernel Oops. This cannot be fixed from inside ftape.
12877 Controlling the amount of debugging output of ftape
12878 CONFIG_FT_NORMAL_DEBUG
12879 This option controls the amount of debugging output the ftape driver
12880 is ABLE to produce; it does not increase or diminish the debugging
12881 level itself. If unsure, leave this at its default setting,
12882 i.e. choose "Normal".
12884 Ftape can print lots of debugging messages to the system console
12885 resp. kernel log files. Reducing the amount of possible debugging
12886 output reduces the size of the kernel module by some KB, so it might
12887 be a good idea to use "None" for emergency boot floppies.
12889 If you want to save memory then the following strategy is
12890 recommended: leave this option at its default setting "Normal" until
12891 you know that the driver works as expected, afterwards reconfigure
12892 the kernel, this time specifying "Reduced" or "None" and recompile
12893 and install the kernel as usual. Note that choosing "Excessive"
12894 debugging output does not increase the amount of debugging output
12895 printed to the console but only makes it possible to produce
12896 "Excessive" debugging output.
12898 Please read Documentation/ftape.txt for a short description
12899 how to control the amount of debugging output.
12901 The floppy drive controller for ftape
12903 Only change this setting if you have a special controller. If you
12904 didn't plug any add-on card into your computer system but just
12905 plugged the floppy tape cable into the already existing floppy drive
12906 controller then you don't want to change the default setting,
12907 i.e. choose "Standard".
12909 Choose "MACH-2" if you have a Mountain Mach-2 controller.
12910 Choose "FC-10/FC-20" if you have a Colorado FC-10 or FC-20
12912 Choose "Alt/82078" if you have another controller that is located at
12913 an IO base address different from the standard floppy drive
12914 controller's base address of `0x3f0', or uses an IRQ (interrupt)
12915 channel different from `6', or a DMA channel different from
12916 `2'. This is necessary for any controller card that is based on
12917 Intel's 82078 FDC such as Seagate's, Exabyte's and Iomega's "high
12918 speed" controllers.
12920 If you choose something other than "Standard" then please make
12921 sure that the settings for the IO base address and the IRQ and DMA
12922 channel in the configuration menus below are correct. Use the manual
12923 of your tape drive to determine the correct settings!
12925 If you are already successfully using your tape drive with another
12926 operating system then you definitely should use the same settings
12927 for the IO base, the IRQ and DMA channel that have proven to work
12928 with that other OS.
12930 Note that this menu lets you specify only the default setting for
12931 the hardware setup. The hardware configuration can be changed at
12932 boot time (when ftape is compiled into the kernel, i.e. if you
12933 have said Y to "Floppy tape drive") or module load time (i.e. if you
12934 have said M to "Floppy tape drive").
12936 Please read also the file Documentation/ftape.txt which
12937 contains a short description of the parameters that can be set at
12938 boot or load time. If you want to use your floppy tape drive on a
12939 PCI-bus based system, please read the file
12940 drivers/char/ftape/README.PCI.
12942 IO base of the floppy disk controller used with Ftape
12944 You don't need to specify a value if the following default
12945 settings for the base IO address are correct:
12946 <<< MACH-2 : 0x1E0 >>>
12947 <<< FC-10/FC-20: 0x180 >>>
12948 <<< Secondary : 0x370 >>>
12949 Secondary refers to a secondary FDC controller like the "high speed"
12950 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
12951 Please make sure that the setting for the IO base address
12952 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
12953 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
12954 successfully using the tape drive with another operating system then
12955 you definitely should use the same settings for the IO base that has
12956 proven to work with that other OS.
12958 Note that this menu lets you specify only the default setting for
12959 the IO base. The hardware configuration can be changed at boot time
12960 (when ftape is compiled into the kernel, i.e. if you specified Y to
12961 "Floppy tape drive") or module load time (i.e. if you have said M to
12962 "Floppy tape drive").
12964 Please read also the file Documentation/ftape.txt which contains a
12965 short description of the parameters that can be set at boot or load
12968 IRQ channel for the floppy disk controller used with Ftape
12970 You don't need to specify a value if the following default
12971 settings for the interrupt channel are correct:
12973 <<< FC-10/FC-20: 9 >>>
12974 <<< Secondary : 6 >>>
12975 Secondary refers to secondary a FDC controller like the "high speed"
12976 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
12977 Please make sure that the setting for the IO base address
12978 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
12979 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
12980 successfully using the tape drive with another operating system then
12981 you definitely should use the same settings for the IO base that has
12982 proven to work with that other OS.
12984 Note that this menu lets you specify only the default setting for
12985 the IRQ channel. The hardware configuration can be changed at boot
12986 time (when ftape is compiled into the kernel, i.e. if you said Y to
12987 "Floppy tape drive") or module load time (i.e. if you said M to
12988 "Floppy tape drive").
12990 Please read also the file Documentation/ftape.txt which contains a
12991 short description of the parameters that can be set at boot or load
12994 DMA channel for the floppy disk controller used with Ftape
12996 You don't need to specify a value if the following default
12997 settings for the DMA channel are correct:
12999 <<< FC-10/FC-20: 3 >>>
13000 <<< Secondary : 2 >>>
13001 Secondary refers to a secondary FDC controller like the "high speed"
13002 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
13003 Please make sure that the setting for the IO base address
13004 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
13005 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
13006 successfully using the tape drive with another operating system then
13007 you definitely should use the same settings for the IO base that has
13008 proven to work with that other OS.
13010 Note that this menu lets you specify only the default setting for
13011 the DMA channel. The hardware configuration can be changed at boot
13012 time (when ftape is compiled into the kernel, i.e. if you said Y to
13013 "Floppy tape drive") or module load time (i.e. if you said M to
13014 "Floppy tape drive").
13016 Please read also the file Documentation/ftape.txt which contains a
13017 short description of the parameters that can be set at boot or load
13020 FDC FIFO Threshold before requesting DMA service
13022 Set the FIFO threshold of the FDC. If this is higher the DMA
13023 controller may serve the FDC after a higher latency time. If this is
13024 lower, fewer DMA transfers occur leading to less bus contention.
13025 You may try to tune this if ftape annoys you with "reduced data
13026 rate because of excessive overrun errors" messages. However, this
13027 doesn't seem to have too much effect.
13029 If unsure, don't touch the initial value, i.e. leave it at "8".
13031 FDC maximum data rate
13032 CONFIG_FT_FDC_MAX_RATE
13033 With some motherboard/FDC combinations ftape will not be able to
13034 run your FDC/tape drive combination at the highest available
13035 speed. If this is the case you'll encounter "reduced data rate
13036 because of excessive overrun errors" messages and lots of retries
13037 before ftape finally decides to reduce the data rate.
13039 In this case it might be desirable to tell ftape beforehand that
13040 it need not try to run the tape drive at the highest available
13041 speed. If unsure, leave this disabled, i.e. leave it at 2000
13044 Direct Rendering Manager (XFree86 DRI support)
13046 Kernel-level support for the Direct Rendering Infrastructure (DRI)
13047 introduced in XFree86 4.0. If you say Y here, you need to select
13048 the module that's right for your graphics card from the list below.
13049 These modules provide support for synchronization, security, and
13050 DMA transfers. Please see http://dri.sourceforge.net for more
13051 details. You should also select and configure AGP
13052 (/dev/agpgart) support.
13054 3dfx Banshee/Voodoo3+
13056 Choose this option if you have a 3dfx Banshee or Voodoo3 (or later),
13057 graphics card. If M is selected, the module will be called tdfx.o.
13061 Choose this option if you have a 3dlabs GMX 2000 graphics card.
13062 If M is selected, the module will be called gamma.o.
13066 Choose this option if you have an ATI Rage 128 graphics card. If M
13067 is selected, the module will be called r128.o. AGP support for
13068 this card is strongly suggested (unless you have a PCI version).
13072 Choose this option if you have an Intel I810 graphics card. If M is
13073 selected, the module will be called i810.o. AGP support is required
13074 for this driver to work.
13078 Choose this option if you have a Matrox g200 or g400 graphics card. If M
13079 is selected, the module will be called mga.o. AGP support is required
13080 for this driver to work.
13082 MTRR control and configuration
13084 On Intel P6 family processors (Pentium Pro, Pentium II and later)
13085 the Memory Type Range Registers (MTRRs) may be used to control
13086 processor access to memory ranges. This is most useful if you have
13087 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
13088 allows bus write transfers to be combined into a larger transfer
13089 before bursting over the PCI/AGP bus. This can increase performance
13090 of image write operations 2.5 times or more. Saying Y here creates a
13091 /proc/mtrr file which may be used to manipulate your processor's
13092 MTRRs. Typically the X server should use this.
13094 This code has a reasonably generic interface so that similar
13095 control registers on other processors can be easily supported
13098 The Cyrix 6x86, 6x86MX and M II processors have Address Range
13099 Registers (ARRs) which provide a similar functionality to MTRRs. For
13100 these, the ARRs are used to emulate the MTRRs.
13101 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
13102 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
13103 write-combining. All of these processors are supported by this code
13104 and it makes sense to say Y here if you have one of them.
13106 Saying Y here also fixes a problem with buggy SMP BIOSes which only
13107 set the MTRRs for the boot CPU and not for the secondary CPUs. This
13108 can lead to all sorts of problems, so it's good to say Y here.
13110 You can safely say Y even if your machine doesn't have MTRRs, you'll
13111 just add about 9 KB to your kernel.
13113 See Documentation/mtrr.txt for more information.
13115 Main CPU frequency, only for DEC alpha machine
13116 CONFIG_FT_ALPHA_CLOCK
13117 On some DEC Alpha machines the CPU clock frequency cannot be
13118 determined automatically, so you need to specify it here ONLY if
13119 running a DEC Alpha, otherwise this setting has no effect.
13121 Double Talk PC internal speech card support
13123 This driver is for the DoubleTalk PC, a speech synthesizer
13124 manufactured by RC Systems (http://www.rcsys.com/ ). It is also
13125 called the `internal DoubleTalk'. If you want to compile this as a
13126 module ( = code which can be inserted in and removed from the
13127 running kernel whenever you want), say M here and read
13128 Documentation/modules.txt. The module will be called dtlk.o.
13130 Siemens R3964 serial protocol support
13132 This driver allows synchronous communication with devices using the
13133 Siemens R3964 packet protocol. Unless you are dealing with special
13134 hardware like PLCs, you are unlikely to need this.
13136 To compile this driver as a module ( = code which can be inserted in
13137 and removed from the running kernel whenever you want), say M here
13138 and read Documentation/modules.txt. The module will be called
13143 Applicom intelligent fieldbus card support
13145 This driver provides the kernel-side support for the intelligent
13146 fieldbus cards made by Applicom International. More information
13147 about these cards can be found on the WWW at the address
13148 http://www.applicom-int.com/ , or by email from David Woodhouse
13149 <dwmw2@infradead.org>.
13151 To compile this driver as a module ( = code which can be inserted in
13152 and removed from the running kernel whenever you want), say M here
13153 and read Documentation/modules.txt. The module will be called
13158 Intel Random Number Generator support
13160 This driver provides kernel-side support for the Random Number
13161 Generator hardware found on Intel i8xx-based motherboards.
13163 Both a character driver, used to read() entropy data, and a timer
13164 function which automatically adds entropy directly into the
13165 kernel pool, are exported by this driver.
13167 To compile this driver as a module ( = code which can be inserted in
13168 and removed from the running kernel whenever you want), say M here
13169 and read Documentation/modules.txt. The module will be called
13174 Power Management support
13176 "Power Management" means that parts of your computer are shut
13177 off or put into a power conserving "sleep" mode if they are not
13178 being used. There are two competing standards for doing this: APM
13179 and ACPI. If you want to use either one, say Y here and then also to
13180 the requisite support below.
13182 Power Management is most important for battery powered laptop
13183 computers; if you have a laptop, check out the Linux Laptop home
13185 http://www.cs.utexas.edu/users/kharker/linux-laptop/ and the Battery
13186 Powered Linux mini-HOWTO, available from
13187 http://www.linuxdoc.org/docs.html#howto .
13189 Note that, even if you say N here, Linux on the x86 architecture
13190 will issue the hlt instruction if nothing is to be done, thereby
13191 sending the processor to sleep and saving power.
13195 ACPI/OSPM support for Linux is currently under development. As such,
13196 this support is preliminary and EXPERIMENTAL. Configuring ACPI support
13197 enables kernel interfaces that allow higher level software (OSPM) to
13198 manipulate ACPI defined hardware and software interfaces, including
13199 the evaluation of ACPI control methods. If unsure, choose N here.
13200 Note, this option will enlarge your kernel by about 120K.
13202 This support requires an ACPI compliant platform (hardware/firmware).
13203 If both ACPI and Advanced Power Management (APM) support are
13204 configured, ACPI is used.
13206 This code DOES NOT currently provide a complete OSPM implementation --
13207 it has not yet reached APM's level of functionality. When fully
13208 implemented, Linux ACPI/OSPM will provide a more robust functional
13209 replacement for legacy configuration and power management interfaces,
13210 including the Plug-and-Play BIOS specification (PNP BIOS), the Multi-
13211 Processor Specification (MPS), and the Advanced Power Management
13212 specification (APM).
13214 Linux support for ACPI/OSPM is based on Intel Corporation's ACPI
13215 Component Architecture (ACPI CA). The latest ACPI CA source code,
13216 documentation, debug builds, and implementation status information
13217 can be downloaded from:
13218 http://developer.intel.com/technology/iapc/acpi/downloads.htm
13220 The ACPI mailing list may also be of interest:
13221 http://phobos.fs.tum.de/acpi/index.html
13223 Advanced Power Management BIOS support
13225 APM is a BIOS specification for saving power using several different
13226 techniques. This is mostly useful for battery powered laptops with
13227 APM compliant BIOSes. If you say Y here, the system time will be
13228 reset after a RESUME operation, the /proc/apm device will provide
13229 battery status information, and user-space programs will receive
13230 notification of APM "events" (e.g. battery status change).
13232 If you select "Y" here, you can disable actual use of the APM
13233 BIOS by passing the "apm=off" option to the kernel at boot time.
13235 Note that the APM support is almost completely disabled for
13236 machines with more than one CPU.
13238 In order to use APM, you will need supporting software. For location
13239 and more information, read Documentation/pm.txt and the Battery
13240 Powered Linux mini-HOWTO, available from
13241 http://www.linuxdoc.org/docs.html#howto .
13243 This driver does not spin down disk drives (see the hdparm(8)
13244 manpage ("man 8 hdparm") for that), and it doesn't turn off
13245 VESA-compliant "green" monitors.
13247 This driver does not support the TI 4000M TravelMate and the ACER
13248 486/DX4/75 because they don't have compliant BIOSes. Many "green"
13249 desktop machines also don't have compliant BIOSes, and this driver
13250 may cause those machines to panic during the boot phase.
13252 Generally, if you don't have a battery in your machine, there isn't
13253 much point in using this driver and you should say N. If you get
13254 random kernel OOPSes or reboots that don't seem to be related to
13255 anything, try disabling/enabling this option (or disabling/enabling
13258 Some other things you should try when experiencing seemingly random,
13261 1) make sure that you have enough swap space and that it is
13263 2) pass the "no-hlt" option to the kernel
13264 3) switch on floating point emulation in the kernel and pass
13265 the "no387" option to the kernel
13266 4) pass the "floppy=nodma" option to the kernel
13267 5) pass the "mem=4M" option to the kernel (thereby disabling
13268 all but the first 4 MB of RAM)
13269 6) make sure that the CPU is not over clocked.
13270 7) read the sig11 FAQ at http://www.bitwizard.nl/sig11/
13271 8) disable the cache from your BIOS settings
13272 9) install a fan for the video card or exchange video RAM
13273 10) install a better fan for the CPU
13274 11) exchange RAM chips
13275 12) exchange the motherboard.
13277 To compile this driver as a module ( = code which can be inserted in
13278 and removed from the running kernel whenever you want), say M here
13279 and read Documentation/modules.txt. The module will be called
13282 Ignore USER SUSPEND
13283 CONFIG_APM_IGNORE_USER_SUSPEND
13284 This option will ignore USER SUSPEND requests. On machines with a
13285 compliant APM BIOS, you want to say N. However, on the NEC Versa M
13286 series notebooks, it is necessary to say Y because of a BIOS bug.
13288 Enable APM at boot time
13289 CONFIG_APM_DO_ENABLE
13290 Enable APM features at boot time. From page 36 of the APM BIOS
13291 specification: "When disabled, the APM BIOS does not automatically
13292 power manage devices, enter the Standby State, enter the Suspend
13293 State, or take power saving steps in response to CPU Idle calls."
13294 This driver will make CPU Idle calls when Linux is idle (unless this
13295 feature is turned off -- see "Do CPU IDLE calls", below). This
13296 should always save battery power, but more complicated APM features
13297 will be dependent on your BIOS implementation. You may need to turn
13298 this option off if your computer hangs at boot time when using APM
13299 support, or if it beeps continuously instead of suspending. Turn
13300 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
13301 T400CDT. This is off by default since most machines do fine without
13305 CONFIG_APM_CPU_IDLE
13306 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
13307 On some machines, this can activate improved power savings, such as
13308 a slowed CPU clock rate, when the machine is idle. These idle calls
13309 are made after the idle loop has run for some length of time (e.g.,
13310 333 mS). On some machines, this will cause a hang at boot time or
13311 whenever the CPU becomes idle. (On machines with more than one CPU,
13312 this option does nothing.)
13314 Enable console blanking using APM
13315 CONFIG_APM_DISPLAY_BLANK
13316 Enable console blanking using the APM. Some laptops can use this to
13317 turn off the LCD backlight when the screen blanker of the Linux
13318 virtual console blanks the screen. Note that this is only used by
13319 the virtual console screen blanker, and won't turn off the backlight
13320 when using the X Window system. This also doesn't have anything to
13321 do with your VESA-compliant power-saving monitor. Further, this
13322 option doesn't work for all laptops -- it might not turn off your
13323 backlight at all, or it might print a lot of errors to the console,
13324 especially if you are using gpm.
13326 RTC stores time in GMT
13327 CONFIG_APM_RTC_IS_GMT
13328 Say Y here if your RTC (Real Time Clock a.k.a. hardware clock)
13329 stores the time in GMT (Greenwich Mean Time). Say N if your RTC
13332 It is in fact recommended to store GMT in your RTC, because then you
13333 don't have to worry about daylight savings time changes. The only
13334 reason not to use GMT in your RTC is if you also run a broken OS
13335 that doesn't understand GMT.
13337 Allow interrupts during APM BIOS calls
13338 CONFIG_APM_ALLOW_INTS
13339 Normally we disable external interrupts while we are making calls to
13340 the APM BIOS as a measure to lessen the effects of a badly behaving
13341 BIOS implementation. The BIOS should reenable interrupts if it
13342 needs to. Unfortunately, some BIOSes do not -- especially those in
13343 many of the newer IBM Thinkpads. If you experience hangs when you
13344 suspend, try setting this to Y. Otherwise, say N.
13346 Use real mode APM BIOS call to power off
13347 CONFIG_APM_REAL_MODE_POWER_OFF
13348 Use real mode APM BIOS calls to switch off the computer. This is
13349 a work-around for a number of buggy BIOSes. Switch this option on if
13350 your computer crashes instead of powering off properly.
13352 Watchdog Timer Support
13354 If you say Y here (and to one of the following options) and create a
13355 character special file /dev/watchdog with major number 10 and minor
13356 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
13357 subsequently opening the file and then failing to write to it for
13358 longer than 1 minute will result in rebooting the machine. This
13359 could be useful for a networked machine that needs to come back
13360 online as fast as possible after a lock-up. There's both a watchdog
13361 implementation entirely in software (which can sometimes fail to
13362 reboot the machine) and a driver for hardware watchdog boards, which
13363 are more robust and can also keep track of the temperature inside
13364 your computer. For details, read Documentation/watchdog.txt in the
13367 The watchdog is usually used together with the watchdog daemon
13368 which is available via FTP (user: anonymous) from
13369 ftp://tsx-11.mit.edu/pub/linux/sources/sbin/ . This daemon can also
13370 monitor NFS connections and can reboot the machine when the process
13375 Disable watchdog shutdown on close
13376 CONFIG_WATCHDOG_NOWAYOUT
13377 The default watchdog behaviour (which you get if you say N here) is
13378 to stop the timer if the process managing it closes the file
13379 /dev/watchdog. It's always remotely possible that this process might
13380 get killed. If you say Y here, the watchdog cannot be stopped once
13381 it has been started.
13385 If you have a WDT500P or WDT501P watchdog board, say Y here,
13386 otherwise N. It is not possible to probe for this board, which means
13387 that you have to inform the kernel about the IO port and IRQ using
13388 the "wdt=" kernel option (try "man bootparam" or see the
13389 documentation of your boot loader (lilo or loadlin) about how to
13390 pass options to the kernel at boot time).
13392 If you want to compile this as a module ( = code which can be
13393 inserted in and removed from the running kernel whenever you want),
13394 say M here and read Documentation/modules.txt. The module will be
13397 WDT PCI Watchdog timer
13399 If you have a PCI WDT500/501 watchdog board, say Y here,
13400 otherwise N. It is not possible to probe for this board, which means
13401 that you have to inform the kernel about the IO port and IRQ using
13402 the "wdt=" kernel option (try "man bootparam" or see the
13403 documentation of your boot loader (lilo or loadlin) about how to
13404 pass options to the kernel at boot time).
13406 If you want to compile this as a module ( = code which can be
13407 inserted in and removed from the running kernel whenever you want),
13408 say M here and read Documentation/modules.txt. The module will be
13413 Saying Y here and creating a character special file /dev/temperature
13414 with major number 10 and minor number 131 ("man mknod") will give
13415 you a thermometer inside your computer: reading from
13416 /dev/temperature yields one byte, the temperature in degrees
13417 Fahrenheit. This works only if you have a WDT501P watchdog board
13422 Enable the Fan Tachometer on the WDT501. Only do this if you have a
13423 fan tachometer actually set up.
13426 CONFIG_SOFT_WATCHDOG
13427 A software monitoring watchdog. This will fail to reboot your system
13428 from some situations that the hardware watchdog will recover
13429 from. Equally it's a lot cheaper to install.
13431 This driver is also available as a module ( = code which can be
13432 inserted in and removed from the running kernel whenever you want).
13433 If you want to compile it as a module, say M here and read
13434 Documentation/modules.txt. The module will be called softdog.o.
13436 Berkshire Products PC Watchdog
13438 This is the driver for the Berkshire Products PC Watchdog card.
13439 This card simply watches your kernel to make sure it doesn't freeze,
13440 and if it does, it reboots your computer after a certain amount of
13441 time. This driver is like the WDT501 driver but for different
13442 hardware. Please read Documentation/pcwd-watchdog.txt. The PC
13443 watchdog cards can be ordered from http://www.berkprod.com .
13445 This driver is also available as a module ( = code which can be
13446 inserted in and removed from the running kernel whenever you want).
13447 The module is called pcwd.o. If you want to compile it as a module,
13448 say M here and read Documentation/modules.txt.
13450 Most people will say N.
13452 Acquire SBC Watchdog Timer
13454 This is the driver for the hardware watchdog on the PSC-6x86 Single
13455 Board Computer produced by Acquire Inc (and others). This watchdog
13456 simply watches your kernel to make sure it doesn't freeze, and if
13457 it does, it reboots your computer after a certain amount of time.
13459 This driver is like the WDT501 driver but for different hardware.
13460 This driver is also available as a module ( = code which can be
13461 inserted in and removed from the running kernel whenever you want).
13462 The module is called pscwdt.o. If you want to compile it as a
13463 module, say M here and read Documentation/modules.txt. Most people
13468 This is a driver for the Mixcom hardware watchdog cards. This
13469 watchdog simply watches your kernel to make sure it doesn't freeze,
13470 and if it does, it reboots your computer after a certain amount of
13473 This driver is also available as a module ( = code which can be
13474 inserted in and removed from the running kernel whenever you want).
13475 The module is called mixcomwd.o. If you want to compile it as a
13476 module, say M here and read Documentation/modules.txt. Most people
13479 Toshiba Laptop support
13481 If you intend to run this the kernel on a Toshiba portable say yes
13482 here. This adds a driver to safely access the System Management
13483 Mode of the CPU on Toshiba portables. The System Management Mode
13484 is used to set the BIOS and power saving options on Toshiba portables.
13486 For information on utilities to make use of this driver see the
13487 Toshiba Linux utilities website at:
13488 http://www.buzzard.org.uk/toshiba/
13490 /dev/cpu/microcode - Intel IA32 CPU microcode support
13492 If you say Y here and also to "/dev file system support" in the
13493 'File systems' section, you will be able to update the microcode on
13494 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
13495 Pentium III, Pentium 4, Xeon etc. You will obviously need the actual
13496 microcode binary data itself which is not shipped with the Linux kernel.
13498 For latest news and information on obtaining all the required
13499 ingredients for this driver, check:
13500 http://www.urbanmyth.org/microcode/
13502 This driver is also available as a module ( = code which can be
13503 inserted in and removed from the running kernel whenever you want).
13504 The module will be called microcode.o. If you want to compile it as
13505 a module, say M here and read Documentation/modules.txt. If you use
13506 modprobe or kmod you may also want to add the line
13507 'alias char-major-10-184 microcode' to your /etc/modules.conf file.
13509 /dev/cpu/*/msr - Model-specific register support
13511 This device gives privileged processes access to the x86
13512 Model-Specific Registers (MSRs). It is a character device with
13513 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
13514 MSR accesses are directed to a specific CPU on multi-processor
13517 /dev/cpu/*/cpuid - CPU information support
13519 This device gives processes access to the x86 CPUID instruction to
13520 be executed on a specific processor. It is a character device
13521 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
13524 Enhanced Real Time Clock Support
13526 If you say Y here and create a character special file /dev/rtc with
13527 major number 10 and minor number 135 using mknod ("man mknod"), you
13528 will get access to the real time clock (or hardware clock) built
13529 into your computer.
13531 Every PC has such a clock built in. It can be used to generate
13532 signals from as low as 1Hz up to 8192Hz, and can also be used
13533 as a 24 hour alarm. It reports status information via the file
13534 /proc/driver/rtc and its behaviour is set by various ioctls on
13537 If you run Linux on a multiprocessor machine and said Y to
13538 "Symmetric Multi Processing" above, you should say Y here to read
13539 and set the RTC in an SMP compatible fashion.
13541 If you think you have a use for such a device (such as periodic data
13542 sampling), then say Y here, and read Documentation/rtc.txt for
13545 This driver is also available as a module ( = code which can be
13546 inserted in and removed from the running kernel whenever you want).
13547 The module is called rtc.o. If you want to compile it as a module,
13548 say M here and read Documentation/modules.txt.
13551 #EFI Real Time Clock Services
13554 Tadpole ANA H8 Support
13556 The Hitachi H8/337 is a microcontroller used to deal with the power
13557 and thermal environment. If you say Y here, you will be able to
13558 communicate with it via a character special device.
13564 If you say Y here and create a character special file /dev/nvram
13565 with major number 10 and minor number 144 using mknod ("man mknod"),
13566 you get read and write access to the 50 bytes of non-volatile memory
13567 in the real time clock (RTC), which is contained in every PC and
13570 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
13571 on Ataris. /dev/nvram may be used to view settings there, or to
13572 change them (with some utility). It could also be used to frequently
13573 save a few bits of very important data that may not be lost over
13574 power-off and for which writing to disk is too insecure. Note
13575 however that most NVRAM space in a PC belongs to the BIOS and you
13576 should NEVER idly tamper with it. See Ralf Brown's interrupt list
13577 for a guide to the use of CMOS bytes by your BIOS.
13579 On Atari machines, /dev/nvram is always configured and does not need
13582 This driver is also available as a module ( = code which can be
13583 inserted in and removed from the running kernel whenever you want).
13584 The module will be called nvram.o. If you want to compile it as a
13585 module, say M here and read Documentation/modules.txt.
13589 If you have a joystick, 6dof controller, gamepad, steering wheel,
13590 weapon control system or something like that you can say Y here to
13591 enable generic support for these controllers. You will also need to
13592 say Y or M to at least one of the hardware specific drivers. This
13593 will make the controllers available as /dev/input/jsX devices.
13594 Please read the file Documentation/joystick.txt which contains more
13595 information and the location of the joystick package that you'll
13600 Say Y here if you have an ISA, ISAPnP or PCI standard gameport.
13601 For more information on how to use the driver please read
13602 Documentation/joystick.txt
13604 This driver is also available as a module ( = code which can be
13605 inserted in and removed from the running kernel whenever you want).
13606 The module will be called ns558.o. If you want to compile
13607 it as a module, say M here and read Documentation/modules.txt.
13609 PDPI Lightning 4 gamecard
13610 CONFIG_INPUT_LIGHTNING
13611 Say Y here if you have a PDPI Lightning 4 gamecard. For more
13612 information on how to use the driver please read
13613 Documentation/joystick.txt
13615 This driver is also available as a module ( = code which can be
13616 inserted in and removed from the running kernel whenever you want).
13617 The module will be called lightning.o. If you want to compile
13618 it as a module, say M here and read Documentation/modules.txt.
13620 Aureal Vortex and Trident 4DWave gameports
13621 CONFIG_INPUT_PCIGAME
13622 Say Y here if you have a Trident 4DWave DX/NX or Aureal Vortex 1/2
13623 card. For more information on how to use the driver please read
13624 Documentation/joystick.txt
13626 This driver is also available as a module ( = code which can be
13627 inserted in and removed from the running kernel whenever you want).
13628 The module will be called pcigame.o. If you want to compile
13629 it as a module, say M here and read Documentation/modules.txt.
13631 Classic PC analog joysticks and gamepads
13632 CONFIG_INPUT_ANALOG
13633 Say Y here if you have a controller that connects to the PC
13634 gameport. This supports many different types, including joysticks
13635 with throttle control, with rudders, or with extensions like
13636 additional hats and buttons compatible with CH Flightstick Pro,
13637 ThrustMaster FCS, 6 and 8 button gamepads, or Saitek Cyborg
13638 joysticks. For more information on how to use the driver please read
13639 Documentation/joystick.txt
13641 This driver is also available as a module ( = code which can be
13642 inserted in and removed from the running kernel whenever you want).
13643 The module will be called analog.o. If you want to compile
13644 it as a module, say M here and read Documentation/modules.txt.
13646 Assasin 3D and MadCatz Panther devices
13648 Say Y here if you have an FPGaming or MadCatz controller using the
13649 A3D protocol over the PC gameport. For more information on how to
13650 use the driver please read Documentation/joystick.txt
13652 This driver is also available as a module ( = code which can be
13653 inserted in and removed from the running kernel whenever you want).
13654 The module will be called a3d.o. If you want to compile
13655 it as a module, say M here and read Documentation/modules.txt.
13657 Logitech ADI digital joysticks and gamepads
13659 Say Y here if you have a Logitech controller using the ADI
13660 protocol over the PC gameport. For more information on how to use
13661 the driver please read Documentation/joystick.txt
13663 This driver is also available as a module ( = code which can be
13664 inserted in and removed from the running kernel whenever you want).
13665 The module will be called adi.o. If you want to compile
13666 it as a module, say M here and read Documentation/modules.txt.
13668 Creative Labs Blaster Cobra gamepad
13670 Say Y here if you have a Creative Labs Blaster Cobra gamepad.
13671 For more information on how to use the driver please read
13672 Documentation/joystick.txt
13674 This driver is also available as a module ( = code which can be
13675 inserted in and removed from the running kernel whenever you want).
13676 The module will be called cobra.o. If you want to compile
13677 it as a module, say M here and read Documentation/modules.txt.
13679 Genius Flight2000 Digital joysticks and gamepads
13681 Say Y here if you have a Genius Flight2000 or MaxFighter
13682 digitally communicating joystick or gamepad. For more information
13683 on how to use the driver please read Documentation/joystick.txt
13685 This driver is also available as a module ( = code which can be
13686 inserted in and removed from the running kernel whenever you want).
13687 The module will be called gf2k.o. If you want to compile
13688 it as a module, say M here and read Documentation/modules.txt.
13690 Gravis GrIP joysticks and gamepads
13692 Say Y here if you have a Gravis controller using the GrIP protocol
13693 over the PC gameport. For more information on how to use the driver
13694 please read Documentation/joystick.txt
13696 This driver is also available as a module ( = code which can be
13697 inserted in and removed from the running kernel whenever you want).
13698 The module will be called grip.o. If you want to compile
13699 it as a module, say M here and read Documentation/modules.txt.
13701 InterAct digital joysticks and gamepads
13702 CONFIG_INPUT_INTERACT
13703 Say Y hereif you have an InterAct gameport or joystick
13704 communicating digitally over the gameport. For more information on
13705 how to use the driver please read Documentation/joystick.txt
13707 This driver is also available as a module ( = code which can be
13708 inserted in and removed from the running kernel whenever you want).
13709 The module will be called interact.o. If you want to compile
13710 it as a module, say M here and read Documentation/modules.txt.
13712 ThrustMaster DirectConnect joysticks and gamepads
13714 Say Y here if you have a ThrustMaster controller using the
13715 DirectConnect (BSP) protocol over the PC gameport. For more
13716 information on how to use the driver please read
13717 Documentation/joystick.txt
13719 This driver is also available as a module ( = code which can be
13720 inserted in and removed from the running kernel whenever you want).
13721 The module will be called tmdc.o. If you want to compile
13722 it as a module, say M here and read Documentation/modules.txt.
13724 Microsoft SideWinder digital joysticks and gamepads
13725 CONFIG_INPUT_SIDEWINDER
13726 Say Y here if you have a Microsoft controller using the Digital
13727 Overdrive protocol over PC gameport. For more information on how to
13728 use the driver please read Documentation/joystick.txt
13730 This driver is also available as a module ( = code which can be
13731 inserted in and removed from the running kernel whenever you want).
13732 The module will be called sidewinder.o. If you want to compile
13733 it as a module, say M here and read Documentation/modules.txt.
13735 Serial port input line discipline
13736 CONFIG_INPUT_SERPORT
13737 Say Y hereif you plan to use a joystick that communicates over the
13738 serial (COM) port. For more information on how to use the driver
13739 please read Documentation/joystick.txt
13741 This driver is also available as a module ( = code which can be
13742 inserted in and removed from the running kernel whenever you want).
13743 The module will be called serport.o. If you want to compile
13744 it as a module, say M here and read Documentation/modules.txt.
13746 Logitech WingMan Warrior joystick
13747 CONFIG_INPUT_WARRIOR
13748 Say Y here if you have a Logitech WingMan Warrior joystick
13749 connected to your computer's serial port. For more information on
13750 how to use the driver please read Documentation/joystick.txt
13752 This driver is also available as a module ( = code which can be
13753 inserted in and removed from the running kernel whenever you want).
13754 The module will be called warrior.o. If you want to compile
13755 it as a module, say M here and read Documentation/modules.txt.
13757 LogiCad3d Magellan/SpaceMouse 6dof controller
13758 CONFIG_INPUT_MAGELLAN
13759 Say Y here if you have a Magellan or Space Mouse 6DOF controller
13760 connected to your computer's serial port. For more information on
13761 how to use the driver please read Documentation/joystick.txt
13763 This driver is also available as a module ( = code which can be
13764 inserted in and removed from the running kernel whenever you want).
13765 The module will be called magellan.o. If you want to compile
13766 it as a module, say M here and read Documentation/modules.txt.
13768 SpaceTec SpaceOrb/Avenger 6dof controller
13769 CONFIG_INPUT_SPACEORB
13770 Say Y here if you have a SpaceOrb 360 or SpaceBall Avenger 6DOF
13771 controller connected to your computer's serial port. For more
13772 information on how to use the driver please read
13773 Documentation/joystick.txt
13775 This driver is also available as a module ( = code which can be
13776 inserted in and removed from the running kernel whenever you want).
13777 The module will be called spaceorb.o. If you want to compile
13778 it as a module, say M here and read Documentation/modules.txt.
13780 SpaceTec SpaceBall 4000 FLX 6dof controller
13781 CONFIG_INPUT_SPACEBALL
13782 Say Y here if you have a SpaceTec SpaceBall 4000 FLX controller
13783 connected to your computer's serial port. For more information on
13784 how to use the driver please read Documentation/joystick.txt
13786 I-Force joysticks/wheels
13787 CONFIG_INPUT_IFORCE_232
13788 Say Y here if you have an I-Force joystick or steering wheel
13789 connected to your serial (COM) port. For more information on
13790 how to use the driver please read Documentation/joystick.txt
13792 This driver is also available as a module ( = code which can be
13793 inserted in and removed from the running kernel whenever you want).
13794 The module will be called iforce.o. If you want to compile
13795 it as a module, say M here and read Documentation/modules.txt.
13797 I-Force joysticks/wheels
13798 CONFIG_INPUT_IFORCE_USB
13799 Say Y here if you have an I-Force joystick or steering wheel
13800 connected to your USB port. For more information on how to use the
13801 driver please read Documentation/joystick.txt
13803 This driver is also available as a module ( = code which can be
13804 inserted in and removed from the running kernel whenever you want).
13805 The module will be called iforce.o. If you want to compile
13806 it as a module, say M here and read Documentation/modules.txt.
13808 Multisystem, Sega Genesis, Saturn joysticks and gamepads
13810 Say Y here if you have a Sega Master System gamepad, Sega Genesis
13811 gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga,
13812 Commodore, Amstrad CPC joystick connected to your parallel port.
13813 For more information on how to use the driver please read
13814 Documentation/joystick.txt and Documentation/joystick-parport.txt.
13816 This driver is also available as a module ( = code which can be
13817 inserted in and removed from the running kernel whenever you want).
13818 The module will be called db9.o. If you want to compile
13819 it as a module, say M here and read Documentation/modules.txt.
13821 Multisystem, NES, SNES, N64, PSX joysticks and gamepads
13822 CONFIG_INPUT_GAMECON
13823 Say Y here if you have a Nintendo Entertainment System gamepad,
13824 Super Nintendo Entertainment System gamepad, Nintendo 64 gamepad,
13825 Sony PlayStation gamepad or a Multisystem -- Atari, Amiga,
13826 Commodore, Amstrad CPC joystick connected to your parallel port.
13827 For more information on how to use the driver please read
13828 Documentation/joystick.txt and Documentation/joystick-parport.txt
13830 This driver is also available as a module ( = code which can be
13831 inserted in and removed from the running kernel whenever you want).
13832 The module will be called gamecon.o. If you want to compile
13833 it as a module, say M here and read Documentation/modules.txt.
13835 Multisystem joysticks via TurboGraFX device
13836 CONFIG_INPUT_TURBOGRAFX
13837 Say Y here if you have the TurboGraFX interface by Steffen
13838 Schwenke, and want to use it with Multiststem -- Atari, Amiga,
13839 Commodore, Amstrad CPC joystick. For more information on how to use
13840 the driver please read Documentation/joystick.txt and
13841 Documentation/joystick-parport.txt
13843 This driver is also available as a module ( = code which can be
13844 inserted in and removed from the running kernel whenever you want).
13845 The module will be called turbografx.o. If you want to compile
13846 it as a module, say M here and read Documentation/modules.txt.
13849 CONFIG_INPUT_AMIJOY
13850 Say Y here if you have an Amiga with a digital joystick connected
13851 to it. For more information on how to use the driver please read
13852 Documentation/joystick.txt
13854 This driver is also available as a module ( = code which can be
13855 inserted in and removed from the running kernel whenever you want).
13856 The module will be called joy-amiga.o. If you want to compile
13857 it as a module, say M here and read Documentation/modules.txt.
13859 Atomwide Serial Support
13860 CONFIG_ATOMWIDE_SERIAL
13861 If you have an Atomwide Serial card for an Acorn system, say Y to
13862 this option. The driver can handle 1, 2, or 3 port cards.
13865 The Serial Port Dual Serial Port
13866 CONFIG_DUALSP_SERIAL
13867 If you have the Serial Port's dual serial card for an Acorn system,
13868 say Y to this option. If unsure, say N
13872 If you say Y here and create a character device node /dev/nwbutton
13873 with major and minor numbers 10 and 158 ("man mknod"), then every
13874 time the orange button is pressed a number of times, the number of
13875 times the button was pressed will be written to that device.
13877 This is most useful for applications, as yet unwritten, which
13878 perform actions based on how many times the button is pressed in a
13881 Do not hold the button down for too long, as the driver does not
13882 alter the behaviour of the hardware reset circuitry attached to the
13883 button; it will still execute a hard reset if the button is held
13884 down for longer than approximately five seconds.
13886 This driver is also available as a module ( = code which can be
13887 inserted in and removed from the running kernel whenever you want).
13888 If you want to compile it as a module, say M here and read
13889 Documentation/modules.txt. The module will be called nwbutton.o.
13891 Most people will answer Y to this question and "Reboot Using Button"
13892 below to be able to initiate a system shutdown from the button.
13894 Reboot Using Button
13895 CONFIG_NWBUTTON_REBOOT
13896 If you say Y here, then you will be able to initiate a system
13897 shutdown and reboot by pressing the orange button a number of times.
13898 The number of presses to initiate the shutdown is two by default,
13899 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
13900 in nwbutton.h and recompiling the driver or, if you compile the
13901 driver as a module, you can specify the number of presses at load
13902 time with "insmod button reboot_count=<something>".
13906 If you have a sound card in your computer, i.e. if it can say more
13907 than an occasional beep, say Y. Be sure to have all the information
13908 about your sound card and its configuration down (I/O port,
13909 interrupt and DMA channel), because you will be asked for it.
13911 You want to read the Sound-HOWTO, available from
13912 http://www.linuxdoc.org/docs.html#howto . General information
13913 about the modular sound system is contained in the files
13914 Documentation/sound/Introduction. The file
13915 Documentation/sound/README.OSS contains some slightly outdated but
13916 still useful information as well.
13918 If you have a PnP sound card and you want to configure it at boot
13919 time using the ISA PnP tools (read
13920 http://www.roestock.demon.co.uk/isapnptools/ ), then you need to
13921 compile the sound card support as a module ( = code which can be
13922 inserted in and removed from the running kernel whenever you want)
13923 and load that module after the PnP configuration is finished. To do
13924 this, say M here and read Documentation/modules.txt as well as
13925 Documentation/sound/README.modules; the module will be called
13928 I'm told that even without a sound card, you can make your computer
13929 say more than an occasional beep, by programming the PC speaker.
13930 Kernel patches and supporting utilities to do that are in the pcsp
13931 package, available at ftp://ftp.infradead.org/pub/pcsp/ .
13935 OSS is the Open Sound System suite of sound card drivers. They make
13936 sound programming easier since they provide a common API. Say Y or M
13937 here (the module will be called sound.o) if you haven't found a
13938 driver for your sound card above, then pick your driver from the
13941 Persistent DMA buffers
13943 Linux can often have problems allocating DMA buffers for ISA sound
13944 cards on machines with more than 16MB of RAM. This is because ISA
13945 DMA buffers must exist below the 16MB boundary and it is quite
13946 possible that a large enough free block in this region cannot be
13947 found after the machine has been running for a while. If you say Y
13948 here the DMA buffers (64Kb) will be allocated at boot time and kept
13949 until the shutdown. This option is only useful if you said Y to
13950 "OSS sound modules", above. If you said M to "OSS sound modules"
13951 then you can get the persistent DMA buffer functionality by passing
13952 the command-line argument "dmabuf=1" to the sound.o module.
13954 Say Y unless you have 16MB or less RAM or a PCI sound card.
13956 Support for Aztech Sound Galaxy (non-PnP) cards
13957 CONFIG_SOUND_SGALAXY
13958 This module initializes the older non Plug and Play sound galaxy
13959 cards from Aztech. It supports the Waverider Pro 32 - 3D and the
13960 Galaxy Washington 16.
13962 If you compile the driver into the kernel, you have to add
13963 "sgalaxy=<io>,<irq>,<dma>,<dma2>,<sgbase>" to the kernel command
13966 Support for AD1816(A) based cards (EXPERIMENTAL)
13967 CONFIG_SOUND_AD1816
13968 Say M here if you have a sound card based on the Analog Devices
13971 If you compile the driver into the kernel, you have to add
13972 "ad1816=<io>,<irq>,<dma>,<dma2>" to the kernel command line.
13974 Yamaha OPL3-SA1 audio controller
13975 CONFIG_SOUND_OPL3SA1
13976 Say Y or M if you have a Yamaha OPL3-SA1 sound chip, which is
13977 usually built into motherboards. Read Documentation/sound/OPL3-SA
13980 If you compile the driver into the kernel, you have to add
13981 "opl3sa=<io>,<irq>,<dma>,<dma2>,<mpuio>,<mpuirq>" to the kernel
13984 ProAudioSpectrum 16 support
13986 Answer Y only if you have a Pro Audio Spectrum 16, ProAudio Studio
13987 16 or Logitech SoundMan 16 sound card. Answer N if you have some
13988 other card made by Media Vision or Logitech since those are not
13989 PAS16 compatible. Please read Documentation/sound/PAS16.
13991 If you compile the driver into the kernel, you have to add
13992 "pas2=<io>,<irq>,<dma>,<dma2>,<sbio>,<sbirq>,<sbdma>,<sbdma2>
13993 to the kernel command line.
13995 100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support
13997 Answer Y if you have an original Sound Blaster card made by Creative
13998 Labs or a 100% hardware compatible clone (like the Thunderboard or
13999 SM Games). For an unknown card you may answer Y if the card claims
14000 to be Sound Blaster-compatible.
14002 Please read the file Documentation/sound/Soundblaster.
14004 You should also say Y here for cards based on the Avance Logic
14005 ALS-007 and ALS-1X0 chips (read Documentation/sound/ALS) and for cards
14006 based on ESS chips (read Documentation/sound/ESS1868 and
14007 Documentation/sound/ESS). If you have an SB AWE 32 or SB AWE 64, say
14008 Y here and also to "AWE32 synth" below and read
14009 Documentation/sound/INSTALL.awe. If you have an IBM Mwave card, say
14010 Y here and read Documentation/sound/mwave.
14012 If you compile the driver into the kernel and don't want to use
14013 isapnp, you have to add "sb=<io>,<irq>,<dma>,<dma2>" to the kernel
14016 You can say M here to compile this driver as a module; the module is
14019 #Loopback MIDI device support
14020 #CONFIG_SOUND_VMIDI
14022 ### somebody please fill this in.
14025 Gravis Ultrasound support
14027 Say Y here for any type of Gravis Ultrasound card, including
14028 the GUS or GUS MAX. See also Documentation/sound/ultrasound for
14029 more information on configuring this card with modules.
14031 If you compile the driver into the kernel, you have to add
14032 "gus=<io>,<irq>,<dma>,<dma2>" to the kernel command line.
14034 MPU-401 support (NOT for SB16)
14035 CONFIG_SOUND_MPU401
14036 Be careful with this question. The MPU401 interface is supported by
14037 all sound cards. However, some natively supported cards have their
14038 own driver for MPU401. Enabling this MPU401 option with these cards
14039 will cause a conflict. Also, enabling MPU401 on a system that
14040 doesn't really have a MPU401 could cause some trouble. If your card
14041 was in the list of supported cards, look at the card specific
14042 instructions in the drivers/sound/Readme.cards file. It's safe to
14043 answer Y if you have a true MPU401 MIDI interface card.
14045 If you compile the driver into the kernel, you have to add
14046 "mpu401=<io>,<irq>" to the kernel command line.
14049 CONFIG_SOUND_UART6850
14050 This option enables support for MIDI interfaces based on the 6850
14051 UART chip. This interface is rarely found on sound cards. It's safe
14052 to answer N to this question.
14054 If you compile the driver into the kernel, you have to add
14055 "uart6850=<io>,<irq>" to the kernel command line.
14057 PSS (AD1848, ADSP-2115, ESC614) support
14059 Answer Y or M if you have an Orchid SW32, Cardinal DSP16, Beethoven
14060 ADSP-16 or some other card based on the PSS chipset (AD1848 codec +
14061 ADSP-2115 DSP chip + Echo ESC614 ASIC CHIP). For more information on
14062 how to compile it into the kernel or as a module see the file
14063 Documentation/sound/PSS.
14065 If you compile the driver into the kernel, you have to add
14066 "pss=<io>,<mssio>,<mssirq>,<mssdma>,<mpuio>,<mpuirq>" to the kernel
14069 Enable PSS mixer (Beethoven ADSP-16 and other compatible)
14071 Answer Y for Beethoven ADSP-16. You may try to say Y also for other
14072 cards if they have master volume, bass, treble, and you can't
14073 control it under Linux. If you answer N for Beethoven ADSP-16, you
14074 can't control master volume, bass, treble and synth volume.
14076 If you said M to "PSS support" above, you may enable or disable this
14077 PSS mixer with the module parameter pss_mixer. For more information
14078 see the file Documentation/sound/PSS.
14080 Have DSPxxx.LD firmware file
14081 CONFIG_PSS_HAVE_BOOT
14082 If you have the DSPxxx.LD file or SYNTH.LD file for you card, say Y
14083 to include this file. Without this file the synth device (OPL) may
14086 Full pathname of DSPxxx.LD firmware file
14087 CONFIG_PSS_BOOT_FILE
14088 Enter the full pathname of your DSPxxx.LD file or SYNTH.LD file,
14091 Microsoft Sound System support
14093 Again think carefully before answering Y to this question. It's safe
14094 to answer Y if you have the original Windows Sound System card made
14095 by Microsoft or Aztech SG 16 Pro (or NX16 Pro). Also you may say Y
14096 in case your card is NOT among these:
14098 ATI Stereo F/X, AdLib, Audio Excell DSP16, Cardinal DSP16,
14099 Ensoniq SoundScape (and compatibles made by Reveal and Spea),
14100 Gravis Ultrasound, Gravis Ultrasound ACE, Gravis Ultrasound Max,
14101 Gravis Ultrasound with 16 bit option, Logitech Sound Man 16,
14102 Logitech SoundMan Games, Logitech SoundMan Wave, MAD16 Pro (OPTi
14103 82C929), Media Vision Jazz16, MediaTriX AudioTriX Pro, Microsoft
14104 Windows Sound System (MSS/WSS), Mozart (OAK OTI-601), Orchid
14105 SW32, Personal Sound System (PSS), Pro Audio Spectrum 16, Pro
14106 Audio Studio 16, Pro Sonic 16, Roland MPU-401 MIDI interface,
14107 Sound Blaster 1.0, Sound Blaster 16, Sound Blaster 16ASP, Sound
14108 Blaster 2.0, Sound Blaster AWE32, Sound Blaster Pro, TI TM4000M
14109 notebook, ThunderBoard, Turtle Beach Tropez, Yamaha FM
14110 synthesizers (OPL2, OPL3 and OPL4), 6850 UART MIDI Interface.
14112 For cards having native support in VoxWare, consult the card
14113 specific instructions in drivers/sound/Readme.cards. Some drivers
14114 have their own MSS support and saying Y to this option will cause a
14117 If you compile the driver into the kernel, you have to add
14118 "ad1848=<io>,<irq>,<dma>,<dma2>[,<type>]" to the kernel command
14121 SGI Visual Workstation on-board audio
14123 Say Y or M if you have an SGI Visual Workstation and you want to
14124 be able to use its on-board audio. Read Documentation/sound/vwsnd
14125 for more info on this driver's capabilities.
14127 Ensoniq Soundscape support
14128 CONFIG_SOUND_SSCAPE
14129 Answer Y if you have a sound card based on the Ensoniq SoundScape
14130 chipset. Such cards are being manufactured at least by Ensoniq, Spea
14131 and Reveal (Reveal makes also other cards).
14133 If you compile the driver into the kernel, you have to add
14134 "sscape=<io>,<irq>,<dma>,<mpuio>,<mpuirq>" to the kernel command
14137 MediaTriX AudioTriX Pro support
14139 Answer Y if you have the AudioTriX Pro sound card manufactured
14142 Have TRXPRO.HEX firmware file
14143 CONFIG_TRIX_HAVE_BOOT
14144 The MediaTrix AudioTrix Pro has an on-board microcontroller which
14145 needs to be initialized by downloading the code from the file
14146 TRXPRO.HEX in the DOS driver directory. If you don't have the
14147 TRXPRO.HEX file handy you may skip this step. However, the SB and
14148 MPU-401 modes of AudioTrix Pro will not work without this file!
14150 Full pathname of TRXPRO.HEX firmware file
14151 CONFIG_TRIX_BOOT_FILE
14152 Enter the full pathname of your TRXPRO.HEX file, starting from /.
14154 Support for OPTi MAD16 and/or Mozart based cards
14156 Answer Y if your card has a Mozart (OAK OTI-601) or MAD16 (OPTi
14157 82C928 or 82C929 or 82C931) audio interface chip. These chips are
14158 quite common so it's possible that many no-name cards have one of
14159 them. In addition the MAD16 chip is used in some cards made by known
14160 manufacturers such as Turtle Beach (Tropez), Reveal (some models)
14161 and Diamond (latest ones). Note however that the Tropez sound cards
14162 have their own driver; if you have one of those, say N here and Y or
14163 M to "Full support for Turtle Beach WaveFront", below.
14165 If you compile the driver into the kernel, you have to add
14166 "mad16=<io>,<irq>,<dma>,<dma2>,<mpuio>,<mpuirq>" to the
14167 kernel command line.
14169 See also Documentation/sound/Opti and Documentation/sound/MAD16 for
14170 more information on setting these cards up as modules.
14172 Full support for Turtle Beach WaveFront synth/sound cards
14173 CONFIG_SOUND_WAVEFRONT
14174 Answer Y or M if you have a Tropez Plus, Tropez or Maui sound card
14175 and read the files Documentation/sound/Wavefront and
14176 Documentation/sound/Tropez+.
14178 Support MIDI in older MAD16 based cards (requires SB)
14179 CONFIG_MAD16_OLDCARD
14180 Answer Y (or M) if you have an older card based on the C928 or
14181 Mozart chipset and you want to have MIDI support. If you enable this
14182 option you also need to enable support for Sound Blaster.
14184 Support for Crystal CS4232 based (PnP) cards
14185 CONFIG_SOUND_CS4232
14186 Say Y here if you have a card based on the Crystal CS4232 chip set,
14187 which uses its own Plug and Play protocol.
14189 If you compile the driver into the kernel, you have to add
14190 "cs4232=<io>,<irq>,<dma>,<dma2>,<mpuio>,<mpuirq>" to the kernel
14193 See Documentation/sound/CS4232 for more information on configuring
14196 Support for Yamaha OPL3-SA2, SA3, and SAx based PnP cards
14197 CONFIG_SOUND_OPL3SA2
14198 Say Y or M if you have a card based on one of these Yamaha
14199 sound chipsets. Read Documentation/sound/OPL3-SA2 for more
14200 information on configuring these cards.
14202 If you compile the driver into the kernel, you have to add
14203 "opl3sa2=<io>,<irq>,<dma>,<dma2>,<mssio>,<mpuio>" to the kernel
14206 Support for Turtle Beach Wave Front (Maui, Tropez) synthesizers
14208 Say Y here if you have a Turtle Beach Wave Front, Maui, or Tropez
14211 If you compile the driver into the kernel, you have to add
14212 "maui=<io>,<irq>" to the kernel command line.
14214 Have OSWF.MOT firmware file
14215 CONFIG_MAUI_HAVE_BOOT
14216 Turtle Beach Maui and Tropez sound cards have a microcontroller
14217 which needs to be initialized prior to use. OSWF.MOT is a file
14218 distributed with the card's DOS/Windows drivers. Answer Y if you
14221 Full pathname of OSWF.MOT firmware file
14222 CONFIG_MAUI_BOOT_FILE
14223 Enter the full pathname of your OSWF.MOT file, starting from /.
14225 Support for Turtle Beach MultiSound Classic, Tahiti, Monterey
14226 CONFIG_SOUND_MSNDCLAS
14227 Say M here if you have a Turtle Beach MultiSound Classic, Tahiti or
14228 Monterey (not for the Pinnacle or Fiji).
14230 See Documentation/sound/MultiSound for important information about
14233 Full pathname of MSNDINIT.BIN firmware file
14234 CONFIG_MSNDCLAS_INIT_FILE
14235 The MultiSound cards have two firmware files which are required for
14236 operation, and are not currently included. These files can be
14237 obtained from Turtle Beach. See Documentation/sound/MultiSound for
14238 information on how to obtain this.
14240 Full pathname of MSNDPERM.BIN firmware file
14241 CONFIG_MSNDCLAS_PERM_FILE
14242 The MultiSound cards have two firmware files which are required for
14243 operation, and are not currently included. These files can be
14244 obtained from Turtle Beach. See Documentation/sound/MultiSound for
14245 information on how to obtain this.
14247 Support for Turtle Beach MultiSound Pinnacle, Fiji
14248 CONFIG_SOUND_MSNDPIN
14249 Say M here if you have a Turtle Beach MultiSound Pinnacle or Fiji.
14250 See Documentation/sound/MultiSound for important information about
14253 Full pathname of PNDSPINI.BIN firmware file
14254 CONFIG_MSNDPIN_INIT_FILE
14255 The MultiSound cards have two firmware files which are required for
14256 operation, and are not currently included. These files can be
14257 obtained from Turtle Beach. See Documentation/sound/MultiSound for
14258 information on how to obtain this.
14260 Full pathname of PNDSPERM.BIN firmware file
14261 CONFIG_MSNDPIN_PERM_FILE
14262 The MultiSound cards have two firmware files which are required for
14263 operation, and are not currently included. These files can be
14264 obtained from Turtle Beach. See Documentation/sound/MultiSound for
14265 information on how to obtain this.
14267 MSND Pinnacle have S/PDIF I/O
14268 CONFIG_MSNDPIN_DIGITAL
14269 If you have the S/PDIF daughter board for the Pinnacle or Fiji,
14270 answer Y here; otherwise, say N. If you have this, you will be able
14271 to play and record from the S/PDIF port (digital signal). See
14272 Documentation/sound/MultiSound for information on how to make use of
14275 MSND Pinnacle non-PnP Mode
14276 CONFIG_MSNDPIN_NONPNP
14277 The Pinnacle and Fiji card resources can be configured either with
14278 PnP, or through a configuration port. Say Y here if your card is NOT
14279 in PnP mode. For the Pinnacle, configuration in non-PnP mode allows
14280 use of the IDE and joystick peripherals on the card as well; these
14281 do not show up when the card is in PnP mode. Specifying zero for any
14282 resource of a device will disable the device. If you are running the
14283 card in PnP mode, you must say N here and use isapnptools to
14284 configure the card's resources.
14286 MSND Pinnacle config port
14288 This is the port which the Pinnacle and Fiji uses to configure the
14289 card's resources when not in PnP mode. If your card is in PnP mode,
14290 then be sure to say N to the previous option, "MSND Pinnacle Non-PnP
14293 MSND buffer size (kB)
14294 CONFIG_MSND_FIFOSIZE
14295 Configures the size of each audio buffer, in kilobytes, for
14296 recording and playing in the MultiSound drivers (both the Classic
14297 and Pinnacle). Larger values reduce the chance of data overruns at
14298 the expense of overall latency. If unsure, use the default.
14300 FM synthesizer (YM3812/OPL-3) support
14301 CONFIG_SOUND_YM3812
14302 Answer Y if your card has a FM chip made by Yamaha (OPL2/OPL3/OPL4).
14303 Answering Y is usually a safe and recommended choice, however some
14304 cards may have software (TSR) FM emulation. Enabling FM support with
14305 these cards may cause trouble (I don't currently know of any such
14307 Please read the file Documentation/sound/OPL3 if your card has an
14310 If you compile the driver into the kernel, you have to add
14311 "opl3=<io>" to the kernel command line.
14315 ACI mixer (miroPCM12/PCM20)
14316 CONFIG_SOUND_ACI_MIXER
14317 ACI (Audio Command Interface) is a protocol used to communicate with
14318 the microcontroller on some sound cards produced by miro, e.g. the
14319 miroSOUND PCM12 and PCM20. The main function of the ACI is to
14320 control the mixer and to get a product identification.
14322 This Voxware ACI driver currently only supports the ACI functions on
14323 the miroSOUND PCM12 and PCM20 cards. On the PCM20, ACI also controls
14324 the radio tuner. This is supported in the video4linux
14325 radio-miropcm20 driver.
14328 CONFIG_SOUND_AWE32_SYNTH
14329 Say Y here if you have a Sound Blaster SB32, AWE32-PnP, SB AWE64 or
14330 similar sound card. See Documentation/sound/README.awe,
14331 Documentation/sound/AWE32 and the Soundblaster-AWE mini-HOWTO,
14332 available from http://www.linuxdoc.org/docs.html#howto for more
14335 Gallant's Audio Excel DSP 16 support (SC-6000 and SC-6600)
14336 CONFIG_SOUND_AEDSP16
14337 Answer Y if you have a Gallant's Audio Excel DSP 16 card. This
14338 driver supports Audio Excel DSP 16 but not the III nor PnP versions
14341 The Gallant's Audio Excel DSP 16 card can emulate either an SBPro or
14342 a Microsoft Sound System card, so you should have said Y to either
14343 "100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support"
14344 or "Microsoft Sound System support", above, and you need to answer
14345 the "MSS emulation" and "SBPro emulation" questions below
14346 accordingly. You should say Y to one and only one of these two
14349 Read the drivers/sound/lowlevel/README.aedsp16 file and the head of
14350 drivers/sound/lowlevel/aedsp16.c as well as
14351 Documentation/sound/AudioExcelDSP16 to get more information about
14352 this driver and its configuration.
14354 Audio Excel DSP 16 (SBPro emulation)
14355 CONFIG_AEDSP16_SBPRO
14356 Answer Y if you want your audio card to emulate Sound Blaster Pro.
14357 You should then say Y to "100% Sound Blaster compatibles
14358 (SB16/32/64, ESS, Jazz16) support" and N to "Audio Excel DSP 16 (MSS
14361 If you compile the driver into the kernel, you have to add
14362 "aedsp16=<io>,<irq>,<dma>,<mssio>,<mpuio>,<mouirq>" to the kernel
14365 Audio Excel DSP 16 (MSS emulation)
14367 Answer Y if you want your audio card to emulate Microsoft Sound
14368 System. You should then say Y to "Microsoft Sound System support"
14369 and say N to "Audio Excel DSP 16 (SBPro emulation)".
14371 SC-6600 based audio cards (new Audio Excel DSP 16)
14373 The SC6600 is the new version of DSP mounted on the Audio Excel DSP
14374 16 cards. Find in the manual the FCC ID of your audio card and
14375 answer Y if you have an SC6600 DSP.
14377 SC-6600 Joystick Interface
14379 Say Y here in order to use the joystick interface of the Audio Excel
14382 SC-6600 CDROM Interface
14383 CONFIG_SC6600_CDROM
14384 This is used to activate the the CDROM interface of the Audio Excel
14385 DSP 16 card. Enter: 0 for Sony, 1 for Panasonic, 2 for IDE, 4 for no
14388 Audio Excel DSP 16 (MPU401 emulation)
14389 CONFIG_AEDSP16_MPU401
14390 Answer Y if you want your audio card to emulate the MPU-401 midi
14391 interface. You should then also say Y to "MPU-401 support".
14393 Note that the I/O base for MPU-401 support of aedsp16 is the same
14394 you have selected for "MPU-401 support". If you are using this
14395 driver as a module you have to specify the MPU I/O base address with
14396 the parameter 'mpu_base=0xNNN'.
14398 Creative EMU10K1 based PCI sound cards
14399 CONFIG_SOUND_EMU10K1
14400 Say Y or M if you have a PCI sound card using the EMU10K1
14401 chipset, such as the Creative SBLive!, SB PCI512 or Emu-APS.
14403 Crystal SoundFusion (CS4280/461x)
14404 CONFIG_SOUND_FUSION
14405 This module drives the Crystal SoundFusion devices (CS4280/46xx series)
14406 when wired as native sound drivers with AC97 codecs. If this driver
14407 does not work try the CS4232 driver.
14409 Ensoniq ES1370 based PCI sound cards
14410 CONFIG_SOUND_ES1370
14411 Say Y or M if you have a PCI sound card utilizing the Ensoniq
14412 ES1370 chipset, such as Ensoniq's AudioPCI (non-97). To find
14413 out if your sound card uses an ES1370 without removing your
14414 computer's cover, use lspci -n and look for the PCI ID
14415 1274:5000. Since Ensoniq was bought by Creative Labs,
14416 Sound Blaster 64/PCI models are either ES1370 or ES1371 based.
14417 This driver differs slightly from OSS/Free, so PLEASE READ
14418 Documentation/sound/es1370.
14420 Ensoniq ES1371 based PCI sound cards
14421 CONFIG_SOUND_ES1371
14422 Say Y or M if you have a PCI sound card utilizing the Ensoniq
14423 ES1371 chipset, such as Ensoniq's AudioPCI97. To find out if
14424 your sound card uses an ES1371 without removing your computer's
14425 cover, use lspci -n and look for the PCI ID 1274:1371. Since
14426 Ensoniq was bought by Creative Labs, Sound Blaster 64/PCI
14427 models are either ES1370 or ES1371 based. This driver differs
14428 slightly from OSS/Free, so PLEASE READ Documentation/sound/es1371.
14430 ESS Solo1 based PCI sound cards (eg. SC1938)
14431 CONFIG_SOUND_ESSSOLO1
14432 Say Y or M if you have a PCI sound card utilizing the ESS Technology
14433 Solo1 chip. To find out if your sound card uses a
14434 Solo1 chip without removing your computer's cover, use
14435 lspci -n and look for the PCI ID 125D:1969. This driver
14436 differs slightly from OSS/Free, so PLEASE READ
14437 Documentation/sound/solo1.
14439 S3 SonicVibes based PCI sound cards
14440 CONFIG_SOUND_SONICVIBES
14441 Say Y or M if you have a PCI sound card utilizing the S3
14442 SonicVibes chipset. To find out if your sound card uses a
14443 SonicVibes chip without removing your computer's cover, use
14444 lspci -n and look for the PCI ID 5333:CA00. This driver
14445 differs slightly from OSS/Free, so PLEASE READ
14446 Documentation/sound/sonicvibes.
14448 Trident 4DWave DX/NX, SiS 7018 or ALi 5451 PCI Audio Core
14449 CONFIG_SOUND_TRIDENT
14450 Say Y or M if you have a PCI sound card utilizing the Trident
14451 4DWave-DX/NX chipset or your mother board chipset has SiS 7018
14452 or ALi 5451 built-in. The SiS 7018 PCI Audio Core is embedded
14453 in SiS960 Super South Bridge and SiS540/630 Single Chipset.
14454 The ALi 5451 PCI Audio Core is embedded in ALi M1535, M1535D,
14455 M1535+ or M1535D+ South Bridge.
14457 Use lspci -n to find out if your sound card or chipset uses
14458 Trident 4DWave or SiS 7018. PCI ID 1023:2000 or 1023:2001 stands
14459 for Trident 4Dwave. PCI ID 1039:7018 stands for SiS7018. PCI ID
14460 10B9:5451 stands for ALi5451.
14462 This driver supports S/PDIF in/out (record/playback) for ALi 5451
14463 embedded in ALi M1535+ and M1535D+. Note that they aren't all
14464 enabled by default; you can enable them by saying Y to "/proc file
14465 system support" and "Sysctl support", and after the /proc file
14466 system has been mounted, executing the command
14468 command what is enabled
14470 echo 0>/proc/ALi5451 pcm out is also set to S/PDIF out. (Default).
14472 echo 1>/proc/ALi5451 use S/PDIF out to output pcm data.
14474 echo 2>/proc/ALi5451 use S/PDIF out to output non-pcm data.(AC3...).
14476 echo 3>/proc/ALi5451 record from Ac97 in(MIC, Line in...). (Default).
14478 echo 4>/proc/ALi5451 no matter Ac97 settings, record from S/PDIF in.
14481 This driver differs slightly from OSS/Free, so PLEASE READ the
14482 comments at the top of driver/sound/trident.c
14484 Rockwell WaveArtist
14485 CONFIG_SOUND_WAVEARTIST
14486 Say Y here to include support for the Rockwell WaveArtist sound
14487 system. This driver is mainly for the NetWinder.
14489 VIA 82Cxxx Audio Codec
14490 CONFIG_SOUND_VIA82CXXX
14491 Say Y here to include support for the audio codec found on VIA
14492 82Cxxx-based chips. Typically these are built into a motherboard. DO
14493 NOT select Sound Blaster or Adlib with this driver, unless you have
14494 a Sound Blaster or Adlib card in addition to your VIA audio chip.
14496 NeoMagic 256AV/256ZX sound chipsets
14498 Say M here to include audio support for the NeoMagic 256AV/256ZX
14499 chipsets. These are the audio chipsets found in the Sony
14500 Z505S/SX/DX, some Sony F-series, and the Dell Latitude CPi and CPt
14501 laptops. It includes support for an AC97-compatible mixer and an
14502 apparently proprietary sound engine.
14504 See Documentation/sound/NM256 for further information.
14506 ESS Maestro sound chipsets
14507 CONFIG_SOUND_MAESTRO
14508 Say Y or M if you have a sound system driven by ESS's Maestro line
14509 of PCI sound chips. These include the Maestro 1, Maestro 2, and
14510 Maestro 2E. See Documentation/sound/Maestro for more details.
14512 Are you using a crosscompiler
14513 CONFIG_CROSSCOMPILE
14514 Say Y here if you are compiling the kernel on a different
14515 architecture than the one it is intended to run on.
14517 Kernel support for Linux/MIPS 32-bit binary compatibility
14518 CONFIG_MIPS32_COMPAT
14519 Select this option if you want Linux/MIPS 32-bit binary
14520 compatibility. Since all software available for Linux/MIPS is
14521 currently 32-bit you should say Y here.
14523 Build fp exception handler module
14524 CONFIG_MIPS_FPE_MODULE
14525 Build the floating point exception handler module. This option is
14526 only useful for people working on the floating point exception
14527 handler. If you don't, say N.
14529 Remote GDB kernel debugging
14530 CONFIG_REMOTE_DEBUG
14531 If you say Y here, it will be possible to remotely debug the MIPS
14532 kernel using gdb. This enlarges your kernel image disk size by
14533 several megabytes and requires a machine with more than 16 MB,
14534 better 32 MB RAM to avoid excessive linking time. This is only
14535 useful for kernel hackers. If unsure, say N.
14537 Magic System Request Key support
14539 If you say Y here, you will have some control over the system even
14540 if the system crashes for example during kernel debugging (e.g., you
14541 will be able to flush the buffer cache to disk, reboot the system
14542 immediately or dump some status information). This is accomplished
14543 by pressing various keys while holding SysRq (Alt+PrintScreen). It
14544 also works on a serial console (on PC hardware at least), if you
14545 send a BREAK and then within 5 seconds a command keypress. The
14546 keys are documented in Documentation/sysrq.txt. Don't say Y unless
14547 you really know what this hack does.
14551 ISDN ("Integrated Services Digital Networks", called RNIS in France)
14552 is a special type of fully digital telephone service; it's mostly
14553 used to connect to your Internet service provider (with SLIP or
14554 PPP). The main advantage is that the speed is higher than ordinary
14555 modem/telephone connections, and that you can have voice
14556 conversations while downloading stuff. It only works if your
14557 computer is equipped with an ISDN card and both you and your service
14558 provider purchased an ISDN line from the phone company. For details,
14559 read http://alumni.caltech.edu/~dank/isdn/ on the WWW.
14561 This driver allows you to use an ISDN-card for networking
14562 connections and as dialin/out device. The isdn-tty's have a built in
14563 AT-compatible modem emulator. Network devices support autodial,
14564 channel-bundling, callback and caller-authentication without having
14565 a daemon running. A reduced T.70 protocol is supported with tty's
14566 suitable for German BTX. On D-Channel, the protocols EDSS1
14567 (Euro-ISDN) and 1TR6 (German style) are supported. See
14568 Documentation/isdn/README for more information.
14570 If you want to compile the ISDN code as a module ( = code which can
14571 be inserted in and removed from the running kernel whenever you
14572 want), say M here and read Documentation/modules.txt. The module
14573 will be called isdn.o. If unsure, say N.
14575 Support synchronous PPP
14577 Over digital connections such as ISDN, there is no need to
14578 synchronize sender and recipient's clocks with start and stop bits
14579 as is done over analog telephone lines. Instead, one can use
14580 "synchronous PPP". Saying Y here will include this protocol. This
14581 protocol is used by Cisco and Sun for example. So you want to say Y
14582 here if the other end of your ISDN connection supports it. You will
14583 need a special version of pppd (called ipppd) for using this
14584 feature. See Documentation/isdn/README.syncppp and
14585 Documentation/isdn/syncPPP.FAQ for more information.
14587 Support generic MP (RFC 1717)
14589 With synchronous PPP enabled, it is possible to increase throughput
14590 by bundling several ISDN-connections, using this protocol. See
14591 Documentation/isdn/README.syncppp for more information.
14593 Use VJ-compression with synchronous PPP
14595 This enables Van Jacobson header compression for synchronous PPP.
14596 Say Y if the other end of the connection supports it.
14598 Support audio via ISDN
14600 If you say Y here, the modem-emulator will support a subset of the
14601 EIA Class 8 Voice commands. Using a getty with voice-support
14602 (mgetty+sendfax by gert@greenie.muc.de with an extension, available
14603 with the ISDN utility package for example), you will be able to use
14604 your Linux box as an ISDN-answering machine. Of course, this must be
14605 supported by the lowlevel driver also. Currently, the HiSax driver
14606 is the only voice-supporting driver. See
14607 Documentation/isdn/README.audio for more information.
14609 X.25 PLP on top of ISDN
14611 This feature provides the X.25 protocol over ISDN connections.
14612 See Documentation/isdn/README.x25 for more information
14613 if you are thinking about using this.
14615 ISDN diversion services support
14616 CONFIG_ISDN_DIVERSION
14617 This option allows you to use some supplementary diversion
14618 services in conjunction with the HiSax driver on an EURO/DSS1
14621 Supported options are CD (call deflection), CFU (Call forward
14622 unconditional), CFB (Call forward when busy) and CFNR (call forward
14623 not reachable). Additionally the actual CFU, CFB and CFNR state may
14626 The use of CFU, CFB, CFNR and interrogation may be limited to some
14627 countries. The keypad protocol is still not implemented. CD should
14628 work in all countries if the service has been subscribed to.
14630 Please read the file Documentation/isdn/README.diversion.
14632 ICN 2B and 4B support
14633 CONFIG_ISDN_DRV_ICN
14634 This enables support for two kinds of ISDN-cards made by a German
14635 company called ICN. 2B is the standard version for a single ISDN
14636 line with two B-channels, 4B supports two ISDN lines. For running
14637 this card, additional firmware is necessary, which has to be
14638 downloaded into the card using a utility which is distributed
14639 separately. See Documentation/isdn/README and README.icn for more
14642 If you want to compile this as a module ( = code which can be
14643 inserted in and removed from the running kernel whenever you want),
14644 say M here and read Documentation/modules.txt. The module will be
14648 CONFIG_ISDN_DRV_LOOP
14649 This driver provides a virtual ISDN card. Its primary purpose is
14650 testing of linklevel features or configuration without getting
14651 charged by your service-provider for lots of phone calls.
14652 You need will need the loopctrl utility from the latest isdn4k-utils
14653 package to set up this driver.
14655 HiSax SiemensChipSet driver support
14656 CONFIG_ISDN_DRV_HISAX
14657 This is a driver supporting the Siemens chipset on various
14658 ISDN-cards (like AVM A1, Elsa ISDN cards, Teles S0-16.0, Teles
14659 S0-16.3, Teles S0-8, Teles/Creatix PnP, ITK micro ix1 and many
14662 HiSax is just the name of this driver, not the name of any hardware.
14664 If you have a card with such a chipset, you should say Y here and
14665 also to the configuration option of the driver for your particular
14668 If you want to compile this as a module ( = code which can be
14669 inserted in and removed from the running kernel whenever you want),
14670 say M here and read Documentation/modules.txt. The module will be
14671 called hisax.o. See Documentation/isdn/README.HiSax for more
14672 information on using this driver.
14674 HiSax Support for EURO/DSS1
14676 Say Y or N according to the D-channel protocol which your local
14677 telephone service company provides.
14679 The call control protocol E-DSS1 is used in most European countries.
14680 If unsure, say yes.
14682 Support for german charge info
14684 If you want that the HiSax hardware driver sends messages to the
14685 upper level of the isdn code on each AOCD (Advice Of Charge, During
14686 the call -- transmission of the fee information during a call) and
14687 on each AOCE (Advice Of Charge, at the End of the call --
14688 transmission of fee information at the end of the call), say Y here.
14689 This works only in Germany.
14691 Disable sending complete
14692 CONFIG_HISAX_NO_SENDCOMPLETE
14693 If you have trouble with some ugly exchanges or you live in
14694 Australia select this option.
14696 Disable sending low layer compatibility
14697 CONFIG_HISAX_NO_LLC
14698 If you have trouble with some ugly exchanges try to select this
14701 Disable keypad protocol option
14702 CONFIG_HISAX_NO_KEYPAD
14703 If you like to send special dial strings including * or # without
14704 using the keypad protocol, select this option.
14706 HiSax Support for German 1TR6
14708 Say Y or N according to the D-channel protocol which your local
14709 telephone service company provides.
14711 1TR6 is an old call control protocol which was used in Germany
14712 before E-DSS1 was established. Nowadays, all new lines in Germany
14715 HiSax Support for US NI1
14717 Enable this if you like to use ISDN in US on a NI1 basic rate interface.
14721 This enables HiSax support for the Teles ISDN-cards S0-16.0, S0-8
14722 and many compatibles.
14724 See Documentation/isdn/README.HiSax on how to configure it using the
14725 different cards, a different D-channel protocol, or non-standard
14726 IRQ/port/shmem settings.
14728 Teles 16.3 or PNP or PCMCIA
14730 This enables HiSax support for the Teles ISDN-cards S0-16.3 the
14731 Teles/Creatix PnP and the Teles PCMCIA.
14733 See Documentation/isdn/README.HiSax on how to configure it using the
14734 different cards, a different D-channel protocol, or non-standard
14738 CONFIG_HISAX_TELESPCI
14739 This enables HiSax support for the Teles PCI.
14740 See Documentation/isdn/README.HiSax on how to configure it.
14744 This enables HiSax support for the Teles/Creatix parallel port
14745 S0BOX. See Documentation/isdn/README.HiSax on how to configure it.
14748 CONFIG_HISAX_AVM_A1
14749 This enables HiSax support for the AVM A1 (aka "Fritz").
14751 See Documentation/isdn/README.HiSax on how to configure it using the
14752 different cards, a different D-channel protocol, or non-standard
14755 AVM PnP/PCI (Fritz!PNP/PCI)
14756 CONFIG_HISAX_FRITZPCI
14757 This enables HiSax support for the AVM "Fritz!PnP" and "Fritz!PCI".
14758 See Documentation/isdn/README.HiSax on how to configure it.
14760 AVM A1 PCMCIA (Fritz)
14761 CONFIG_HISAX_AVM_A1_PCMCIA
14762 This enables HiSax support for the AVM A1 "Fritz!PCMCIA").
14763 See Documentation/isdn/README.HiSax on how to configure it.
14767 This enables HiSax support for the Elsa Mircolink ISA cards, for the
14768 Elsa Quickstep series cards and Elsa PCMCIA.
14770 See Documentation/isdn/README.HiSax on how to configure it using the
14771 different cards, a different D-channel protocol, or non-standard
14774 ITK ix1-micro Revision 2
14775 CONFIG_HISAX_IX1MICROR2
14776 This enables HiSax support for the ITK ix1-micro Revision 2 card.
14778 See Documentation/isdn/README.HiSax on how to configure it using the
14779 different cards, a different D-channel protocol, or non-standard
14782 Eicon.Diehl Diva cards
14783 CONFIG_HISAX_DIEHLDIVA
14784 This enables HiSax support for the Eicon.Diehl Diva none PRO
14785 versions passive ISDN cards.
14787 See Documentation/isdn/README.HiSax on how to configure it using the
14788 different cards, a different D-channel protocol, or non-standard
14792 CONFIG_HISAX_ASUSCOM
14793 This enables HiSax support for the AsusCom and their OEM versions
14794 passive ISDN ISA cards.
14796 See Documentation/isdn/README.HiSax on how to configure it using the
14797 different cards, a different D-channel protocol, or non-standard
14801 CONFIG_HISAX_TELEINT
14802 This enables HiSax support for the TELEINT SA1 semiactiv ISDN card.
14804 See Documentation/isdn/README.HiSax on how to configure it using the
14805 different cards, a different D-channel protocol, or non-standard
14810 This enables HiSax support for the HFC-S 2BDS0 based cards, like
14813 See Documentation/isdn/README.HiSax on how to configure it using the
14814 different cards, a different D-channel protocol, or non-standard
14818 CONFIG_HISAX_SEDLBAUER
14819 This enables HiSax support for the Sedlbauer passive ISDN cards.
14821 See Documentation/isdn/README.HiSax on how to configure it using the
14822 different cards, a different D-channel protocol, or non-standard
14825 USR Sportster internal TA
14826 CONFIG_HISAX_SPORTSTER
14827 This enables HiSax support for the USR Sportster internal TA 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 ITH MIC card.
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_NETJET
14841 This enables HiSax support for the NetJet from Traverse
14844 See Documentation/isdn/README.HiSax on how to configure it using a
14845 different D-channel protocol, or non-standard IRQ/port settings.
14848 CONFIG_HISAX_NETJET_U
14849 This enables HiSax support for the Netspider U interface ISDN card from
14850 Traverse Technologies.
14851 See Documentation/isdn/README.HiSax on how to configure it using a
14852 different D-channel protocol, or non-standard IRQ/port settings.
14856 This enables HiSax support for the Dr. Neuhaus Niccy PnP or PCI.
14858 See Documentation/isdn/README.HiSax on how to configure it using a
14859 different D-channel protocol, or non-standard IRQ/port settings.
14861 Siemens I-Surf card
14863 This enables HiSax support for the Siemens I-Talk/I-Surf card with
14865 See Documentation/isdn/README.HiSax on how to configure it using a
14866 different D-channel protocol, or non-standard IRQ/port settings.
14869 CONFIG_HISAX_HSTSAPHIR
14870 This enables HiSax support for the HST Saphir card.
14872 See Documentation/isdn/README.HiSax on how to configure it using a
14873 different D-channel protocol, or non-standard IRQ/port settings.
14876 CONFIG_HISAX_BKM_A4T
14877 This enables HiSax support for the Telekom A4T card.
14879 See Documentation/isdn/README.HiSax on how to configure it using a
14880 different D-channel protocol, or non-standard IRQ/port settings.
14883 CONFIG_HISAX_SCT_QUADRO
14884 This enables HiSax support for the Scitel Quadro card.
14886 See Documentation/isdn/README.HiSax on how to configure it using a
14887 different D-channel protocol, or non-standard IRQ/port settings.
14891 This enables HiSax support for the Gazel cards.
14893 See Documentation/isdn/README.HiSax on how to configure it using a
14894 different D-channel protocol, or non-standard IRQ/port settings.
14897 CONFIG_HISAX_HFC_PCI
14898 This enables HiSax support for the HFC-S PCI 2BDS0 based cards.
14900 For more informations see under Documentation/isdn/README.hfc-pci.
14902 Winbond W6692 based cards
14904 This enables HiSax support for Winbond W6692 based PCI ISDN cards.
14906 See Documentation/isdn/README.HiSax on how to configure it using a
14907 different D-channel protocol, or non-standard IRQ/port settings.
14909 HFC-S+, HFC-SP, HFC-PCMCIA cards (EXPERIMENTAL)
14910 CONFIG_HISAX_HFC_SX
14911 This enables HiSax support for the HFC-S+, HFC-SP and HFC-PCMCIA
14912 cards. This code is not finished yet.
14914 Am7930 (EXPERIMENTAL)
14915 CONFIG_HISAX_AMD7930
14916 This enables HiSax support for the AMD7930 chips on some SPARCs.
14917 This code is not finished yet.
14920 CONFIG_ISDN_DRV_PCBIT
14921 This enables support for the PCBIT ISDN-card. This card is
14922 manufactured in Portugal by Octal. For running this card, additional
14923 firmware is necessary, which has to be downloaded into the card
14924 using a utility which is distributed separately. See
14925 Documentation/isdn/README and Documentation/isdn/README.pcbit for
14928 If you want to compile this as a module ( = code which can be
14929 inserted in and removed from the running kernel whenever you want),
14930 say M here and read Documentation/modules.txt. The module will be
14933 Spellcaster support (EXPERIMENTAL)
14935 This enables support for the Spellcaster BRI ISDN boards. This
14936 driver currently builds only in a modularized version ( = code which
14937 can be inserted in and removed from the running kernel whenever you
14938 want, details in Documentation/modules.txt); the module will be
14939 called sc.o. See Documentation/isdn/README.sc and
14940 http://www.spellcast.com for more information.
14942 Eicon active card support
14943 CONFIG_ISDN_DRV_EICON
14944 Say Y here if you have an Eicon active ISDN card. In order to use
14945 this card, additional firmware is necessary, which has to be loaded
14946 into the card using the eiconctrl utility which is part of the
14947 latest isdn4k-utils package. Please read the file
14948 Documentation/isdn/README.eicon for more information.
14950 Eicon Diva Server card support
14951 CONFIG_ISDN_DRV_EICON_PCI
14952 Say Y here if you have an Eicon Diva Server (BRI/PRI/4BRI) ISDN card.
14953 Please read Documentation/isdn/README.eicon for more information.
14955 Eicon old-type card support
14956 CONFIG_ISDN_DRV_EICON_ISA
14957 Say Y here if you have an old-type Eicon active ISDN card. In order
14958 to use this card, additional firmware is necessary, which has to be
14959 loaded into the card using the eiconctrl utility which is part of
14960 the latest isdn4k-utils package. Please read the file
14961 Documentation/isdn/README.eicon for more information.
14963 Eicon driver type standalone
14964 CONFIG_ISDN_DRV_EICON_STANDALONE
14965 Enable this option if you want the eicon driver as standalone
14966 version with no interface to the ISDN4Linux isdn module. If you
14967 say Y here, the eicon module only supports the Diva Server PCI
14968 cards and will provide its own IDI interface. You should say N
14971 Support AT-Fax Class 1 and 2 commands
14972 CONFIG_ISDN_TTY_FAX
14973 If you say Y here, the modem-emulator will support a subset of the
14974 Fax Class 1 and 2 commands. Using a getty with fax-support
14975 (mgetty+sendfax, hylafax), you will be able to use your Linux box as
14976 an ISDN-fax-machine. This must be supported by the lowlevel driver
14977 also. See Documentation/isdn/README.fax for more information.
14981 This provides the CAPI (Common ISDN Application Programming
14982 Interface, a standard making it easy for programs to access ISDN
14983 hardware, see http://www.capi.org/ . This is needed for AVM's set of
14984 active ISDN controllers like B1, T1, M1.
14986 This code is also available as a module ( = code which can be
14987 inserted in and removed from the running kernel whenever you want).
14988 The modules will be called capi.o and kernelcapi.o. If you want to
14989 compile it as a module, say M here and read
14990 Documentation/modules.txt.
14993 CONFIG_ISDN_DRV_AVMB1_B1ISA
14994 Enable support for the ISA version of the AVM B1 card.
14997 CONFIG_ISDN_DRV_AVMB1_B1PCI
14998 Enable support for the PCI version of the AVM B1 card.
15000 AVM B1 PCI V4 support
15001 CONFIG_ISDN_DRV_AVMB1_B1PCIV4
15002 Enable support for the V4 version of AVM B1 PCI card.
15004 AVM T1/T1-B ISA support
15005 CONFIG_ISDN_DRV_AVMB1_T1ISA
15006 Enable support for the AVM T1 T1B card.
15007 Note: This is a PRI card and handle 30 B-channels.
15009 AVM B1/M1/M2 PCMCIA support
15010 CONFIG_ISDN_DRV_AVMB1_B1PCMCIA
15011 Enable support for the PCMCIA version of the AVM B1 card.
15013 AVM T1/T1-B PCI support
15014 CONFIG_ISDN_DRV_AVMB1_T1PCI
15015 Enable support for the AVM T1 T1B card.
15016 Note: This is a PRI card and handle 30 B-channels.
15019 CONFIG_ISDN_DRV_AVMB1_C4
15020 Enable support for the AVM C4 PCI card.
15021 This card handle 4 BRI ISDN lines (8 channels).
15023 Verbose reason code reporting (kernel size +=7K)
15024 CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON
15025 If you say Y here, the AVM B1 driver will give verbose reasons for
15026 disconnecting. This will increase the size of the kernel by 7 KB. If
15029 IBM Active 2000 support (EXPERIMENTAL)
15030 CONFIG_ISDN_DRV_ACT2000
15031 Say Y here if you have an IBM Active 2000 ISDN card. In order to use
15032 this card, additional firmware is necessary, which has to be loaded
15033 into the card using a utility which is part of the latest
15034 isdn4k-utils package. Please read the file
15035 Documentation/isdn/README.act2000 for more information.
15037 Hypercope HYSDN cards (Champ, Ergo, Metro) support (module)
15039 Say Y here if you have one of Hypercope's active PCI ISDN cards
15040 Champ, Ergo and Metro. You will then get a module called hysdn.o.
15041 Please read the file Documentation/isdn/README.hysdn for more
15044 HYSDN CAPI 2.0 support
15046 Say Y here if you like to use Hypercope's CAPI 2.0 interface
15048 Support for Sun4 architecture
15050 Say Y here if, and only if, your machine is a Sun4. Note that
15051 a kernel compiled with this option will run only on Sun4.
15052 (And the current version will probably work only on sun4/330.)
15054 SPARC ESP SCSI support
15056 This is the driver for the Sun ESP SCSI host adapter. The ESP
15057 chipset is present in most SPARC SBUS-based computers.
15059 This support is also available as a module called esp.o ( = code
15060 which can be inserted in and removed from the running kernel
15061 whenever you want). If you want to compile it as a module, say M
15062 here and read Documentation/modules.txt.
15064 PTI Qlogic, ISP Driver
15065 CONFIG_SCSI_QLOGICPTI
15066 This driver supports SBUS SCSI controllers from PTI or QLogic. These
15067 controllers are known under Solaris as qpti and in the openprom as
15068 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
15069 driven by a different driver.
15071 This support is also available as a module called qlogicpti.o ( =
15072 code which can be inserted in and removed from the running kernel
15073 whenever you want). If you want to compile it as a module, say M
15074 here and read Documentation/modules.txt.
15076 SPARC /dev/openprom compatibility driver (EXPERIMENTAL)
15077 CONFIG_SUN_OPENPROMIO
15078 This driver provides user programs with an interface to the SPARC
15079 PROM device tree. The driver implements a SunOS-compatible
15080 interface and a NetBSD-compatible interface.
15082 If you want to compile this as a module ( = code which can be
15083 inserted in and removed from the running kernel whenever you want),
15084 say M and read Documentation/modules.txt. If unsure, say Y.
15086 Openprom tree appears in /proc/openprom
15087 CONFIG_SUN_OPENPROMFS
15088 If you say Y, the OpenPROM device tree will be available as a
15089 virtual file system, which you can mount to /proc/openprom by "mount
15090 -t openpromfs none /proc/openprom".
15092 If you want to compile the /proc/openprom support as a module ( =
15093 code which can be inserted in and removed from the running kernel
15094 whenever you want), say M here and read Documentation/modules.txt.
15095 The module will be called openpromfs.o. If unsure, say M.
15097 Kernel support for Linux/Sparc 32bit binary compatibility
15098 CONFIG_SPARC32_COMPAT
15099 This allows you to run 32-bit binaries on your Ultra.
15100 Everybody wants this; say Y.
15102 Kernel support for 32-bit ELF binaries
15103 CONFIG_BINFMT_ELF32
15104 This allows you to run 32-bit Linux/ELF binaries on your Ultra.
15105 Everybody wants this; say Y.
15107 Kernel support for 32-bit (ie. SunOS) a.out binaries
15108 CONFIG_BINFMT_AOUT32
15109 This allows you to run 32-bit a.out format binaries on your Ultra.
15110 If you want to run SunOS binaries (see SunOS binary emulation below)
15111 or other a.out binaries, say Y. If unsure, say N.
15113 SunOS binary emulation
15115 This allows you to run most SunOS binaries. If you want to do this,
15116 say Y here and place appropriate files in /usr/gnemul/sunos. See
15117 http://www.ultralinux.org/faq.html for more information. If you want
15118 to run SunOS binaries on an Ultra you must also say Y to "Kernel
15119 support for 32-bit a.out binaries" above.
15121 Mostek real time clock support
15122 CONFIG_SUN_MOSTEK_RTC
15123 The Mostek RTC chip is used on all known Sun computers except
15124 some JavaStations. For a JavaStation you need to say Y both here
15125 and to "Enhanced Real Time Clock Support".
15127 Say Y here unless you are building a special purpose kernel.
15129 OBP Flash Device support
15131 The OpenBoot PROM on Ultra systems is flashable. If you want to be
15132 able to upgrade the OBP firmware, say Y here.
15134 JavaStation OS Flash SIMM
15136 If you say Y here, you will be able to boot from your JavaStation's
15139 Siemens SAB82532 serial support
15141 This driver supports the serial ports on newer (PCI) Ultra systems.
15142 Say Y if you want to be able to use your serial ports.
15144 Aurora Multiboard 1600se (EXPERIMENTAL)
15146 The Aurora Multiboard is a multi-port high-speed serial controller.
15147 If you have one of these, say Y.
15149 Audio support (EXPERIMENTAL)
15151 This driver provides support for the build-in sound devices on most
15152 Sun machines. If you want to be able to use this, select this option
15153 and one or more of the lowlevel drivers below. See
15154 http://www.dementia.org/~shadow/sparcaudio.html for more
15157 AMD7930 Lowlevel Driver
15158 CONFIG_SPARCAUDIO_AMD7930
15159 This driver supports the AMD 7930 chip found on sun4c, 4/6xx, and
15160 SparcClassic systems.
15162 CS4231 Lowlevel Driver
15163 CONFIG_SPARCAUDIO_CS4231
15164 This driver supports the Crystal Semiconductor CS4231 chip found on
15165 the SS4, SS5, and Ultras.
15167 DBRI Lowlevel Driver
15168 CONFIG_SPARCAUDIO_DBRI
15169 This driver supports the DBRI audio interface found on the SS10,
15170 SS20, Sparcbook 3, and Voyager systems.
15172 Dummy lowlevel Driver
15173 CONFIG_SPARCAUDIO_DUMMY
15174 This is a pseudo-driver used for debugging and testing the
15175 sparcaudio subsystem. Say N unless you want to work on this
15178 Sparc hardware (EXPERIMENTAL)
15179 CONFIG_PARPORT_SUNBPP
15180 This driver provides support for the bidirectional parallel port
15181 found on many Sun machines. Note that many of the newer Ultras
15182 actually have pc style hardware instead.
15185 # m68k-specific kernel options
15186 # Documented by Chris Lawrence <quango@themall.net> et al.
15190 This option enables support for the Amiga series of computers. If
15191 you plan to use this kernel on an Amiga, say Y here and browse the
15192 material available in Documentation/m68k; otherwise say N.
15196 This option enables support for the 68000-based Atari series of
15197 computers (including the TT, Falcon and Medusa). If you plan to use
15198 this kernel on an Atari, say Y here and browse the material
15199 available in Documentation/m68k; otherwise say N.
15203 This option enables support for the Hades Atari clone. If you plan
15204 to use this kernel on a Hades, say Y here; otherwise say N.
15208 This option enables support for the Apple Macintosh series of
15209 computers (yes, there is experimental support now, at least for part
15212 Say N unless you're willing to code the remaining necessary support.
15217 This option enables support for the HP9000/300 series of
15218 workstations. Support for these machines is still very experimental.
15219 If you plan to try to use the kernel on such a machine say Y here.
15220 Everybody else says N.
15224 This option enables support for the Sun 3x series of workstations.
15225 Be warned that this support is very experimental. You will also want
15226 to say Y to 68020 support and N to the other processors below.
15228 If you don't want to compile a kernel for a Sun 3x, say N.
15232 If you anticipate running this kernel on a computer with a MC68020
15233 processor, say Y. Otherwise, say N. Note that the 68020 requires a
15234 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
15235 Sun 3, which provides its own version.
15239 If you anticipate running this kernel on a computer with a MC68030
15240 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
15241 work, as it does not include an MMU (Memory Management Unit).
15245 If you anticipate running this kernel on a computer with a MC68LC040
15246 or MC68040 processor, say Y. Otherwise, say N. Note that an
15247 MC68EC040 will not work, as it does not include an MMU (Memory
15252 If you anticipate running this kernel on a computer with a MC68060
15253 processor, say Y. Otherwise, say N.
15255 Math emulation support (EXPERIMENTAL)
15257 At some point in the future, this will cause floating-point math
15258 instructions to be emulated by the kernel on machines that lack a
15259 floating-point math coprocessor. Thrill-seekers and chronically
15260 sleep-deprived psychotic hacker types can say Y now, everyone else
15261 should probably wait a while.
15263 Math emulation only kernel
15264 CONFIG_M68KFPU_EMU_ONLY
15265 This option prevents any floating-point instructions from being
15266 compiled into the kernel, thereby the kernel doesn't save any
15267 floating point context anymore during task switches, so this
15268 kernel will only be usable on machines without a floating-point
15269 math coprocessor. This makes the kernel a bit faster as no tests
15270 needs to be executed whether a floating-point instruction in the
15271 kernel should be executed or not.
15273 Math emulation extra precision
15274 CONFIG_M68KFPU_EMU_EXTRAPREC
15275 The fpu uses normally a few bit more during calculations for
15276 correct rounding, the emulator can (often) do the same but this
15277 extra calculation can cost quite some time, so you can disable
15278 it here. The emulator will then "only" calculate with a 64 bit
15279 mantissa and round slightly incorrect, what is more then enough
15282 Advanced configuration options
15284 This gives you access to some advanced options for the CPU. The
15285 defaults should be fine for most users, but these options may make
15286 it possible for you to improve performance somewhat if you know what
15289 Note that the answer to this question won't directly affect the
15290 kernel: saying N will just cause this configure script to skip all
15291 the questions about these options.
15293 Most users should say N to this question.
15295 Use read-modify-write instructions
15297 This allows to use certain instructions that work with indivisible
15298 read-modify-write bus cycles. While this is faster than the
15299 workaround of disabling interrupts, it can conflict with DMA
15300 ( = direct memory access) on many Amiga systems, and it is also said
15301 to destabilize other machines. It is very likely that this will
15302 cause serious problems on any Amiga or Atari Medusa if set. The only
15303 configuration where it should work are 68030-based Ataris, where it
15304 apparently improves performance. But you've been warned! Unless you
15305 really know what you are doing, say N. Try Y only if you're quite
15310 This enables support for the Zorro bus in the Amiga. If you have
15311 expansion cards in your Amiga that conform to the Amiga
15312 AutoConfig(tm) specification, say Y, otherwise N. Note that even
15313 expansion cards that do not fit in the Zorro slots but fit in e.g.
15314 the CPU slot may fall in this category, so you have to say Y to let
15317 Zorro device name database
15319 By default, the kernel contains a database of all known Zorro device
15320 names to make the information in /proc/iomem comprehensible to the
15321 user. This database increases the size of the kernel image by about
15322 15KB, but it gets freed after the system boots up, so it doesn't
15323 take up kernel memory. Anyway, if you are building an installation
15324 floppy or kernel for an embedded system where kernel image size
15325 really matters, you can disable this feature and you'll get device
15326 ID numbers instead of names.
15328 When in doubt, say Y.
15330 Amiga 1200/600 PCMCIA support (EXPERIMENTAL)
15331 CONFIG_AMIGA_PCMCIA
15332 Include support in the kernel for pcmcia on Amiga 1200 and Amiga
15333 600. If you intend to use pcmcia cards say Y; otherwise say N.
15335 Amiga Zorro II ramdisk support
15337 This enables support for using Chip RAM and Zorro II RAM as a
15338 ramdisk or as a swap partition. Say Y if you want to include this
15339 driver in the kernel. This driver is also available as a module
15340 ( = code which can be inserted in and removed from the running
15341 kernel whenever you want). The module is called z2ram.o. If you want
15342 to compile it as a module, say M here and read
15343 Documentation/modules.txt.
15345 Atari ST-RAM swap support
15347 This enables support for using (parts of) ST-RAM as swap space,
15348 instead of as normal system memory. This can first enhance system
15349 performance if you have lots of alternate RAM (compared to the size
15350 of ST-RAM), because executable code always will reside in faster
15351 memory. ST-RAM will remain as ultra-fast swap space. On the other
15352 hand, it allows much improved dynamic allocations of ST-RAM buffers
15353 for device driver modules (e.g. floppy, ACSI, SLM printer, DMA
15354 sound). The probability that such allocations at module load time
15355 fail is drastically reduced.
15359 This enables support for the Atari ACSI interface. The driver
15360 supports hard disks and CD-ROMs, which have 512-byte sectors, or can
15361 be switched to that mode. Due to the ACSI command format, only disks
15362 up to 1 GB are supported. Special support for certain ACSI to SCSI
15363 adapters, which could relax that, isn't included yet. The ACSI
15364 driver is also the basis for certain other drivers for devices
15365 attached to the ACSI bus: Atari SLM laser printer, BioNet-100
15366 Ethernet, and PAMsNet Ethernet. If you want to use one of these
15367 devices, you need ACSI support, too.
15369 This driver is also available as a module ( = code which can be
15370 inserted in and removed from the running kernel whenever you want).
15371 The module will be called acsi.o.
15373 Probe all LUNs on each ACSI device
15374 CONFIG_ACSI_MULTI_LUN
15375 If you have a ACSI device that supports more than one LUN (Logical
15376 Unit Number), e.g. a CD jukebox, you should say Y here so that all
15377 will be found by the ACSI driver. An ACSI device with multiple LUNs
15378 acts logically like multiple ACSI devices. The vast majority of ACSI
15379 devices have only one LUN, and so most people can say N here and
15380 should in fact do so, because it is safer.
15382 Atari SLM laser printer support
15384 If you have an Atari SLM laser printer, say Y to include support for
15385 it in the kernel. Otherwise, say N. This driver is also available as
15386 a module ( = code which can be inserted in and removed from the
15387 running kernel whenever you want). The module will be called
15388 acsi_slm.o. Be warned: the driver needs much ST-RAM and can cause
15389 problems due to that fact!
15391 A3000 WD33C93A support
15393 If you have an Amiga 3000 and have SCSI devices connected to the
15394 built-in SCSI controller, say Y. Otherwise, say N. This driver is
15395 also available as a module ( = code which can be inserted in and
15396 removed from the running kernel whenever you want). The module is
15397 called wd33c93.o. If you want to compile it as a module, say M here
15398 and read Documentation/modules.txt.
15400 A2091 WD33C93A support
15402 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
15403 say N. This driver is also available as a module ( = code which can
15404 be inserted in and removed from the running kernel whenever you
15405 want). The module is called wd33c93.o. If you want to compile it as
15406 a module, say M here and read Documentation/modules.txt.
15408 GVP Series II WD33C93A support
15410 If you have a Great Valley Products Series II SCSI controller,
15411 answer Y. Also say Y if you have a later model of GVP SCSI
15412 controller (such as the GVP A4008 or a Combo board). Otherwise,
15413 answer N. This driver does NOT work for the T-Rex series of
15414 accelerators from TekMagic and GVP-M.
15416 This driver is also available as a module ( = code which can be
15417 inserted in and removed from the running kernel whenever you
15418 want). The module will be called gvp11.o. If you want to compile it
15419 as a module, say M here and read Documentation/modules.txt.
15421 Cyberstorm SCSI support
15422 CONFIG_CYBERSTORM_SCSI
15423 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
15424 accelerator board and the optional Cyberstorm SCSI controller,
15425 answer Y. Otherwise, say N.
15427 Cyberstorm II SCSI support
15428 CONFIG_CYBERSTORMII_SCSI
15429 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
15430 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
15433 Blizzard 2060 SCSI support (EXPERIMENTAL)
15434 CONFIG_BLZ2060_SCSI
15435 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
15436 and want to use the onboard SCSI controller, say Y. Otherwise,
15439 Blizzard 1230IV/1260 SCSI support
15440 CONFIG_BLZ1230_SCSI
15441 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
15442 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
15445 Blizzard PowerUP 603e+ SCSI support
15446 CONFIG_BLZ603EPLUS_SCSI
15447 If you have an Amiga 1200 with a Phase5 Blizzard PowerUP 603e+
15448 accelerator, say Y. Otherwise, say N.
15450 Fastlane SCSI support
15451 CONFIG_FASTLANE_SCSI
15452 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
15453 one in the near future, say Y to this question. Otherwise, say N.
15455 Atari native SCSI support
15457 If you have an Atari with built-in NCR5380 SCSI controller (TT,
15458 Falcon, ...) say Y to get it supported. Of course also, if you have
15459 a compatible SCSI controller (e.g. for Medusa). This driver is also
15460 available as a module ( = code which can be inserted in and removed
15461 from the running kernel whenever you want). The module is called
15462 atari_scsi.o. If you want to compile it as a module, say M here and
15463 read Documentation/modules.txt. This driver supports both styles of
15464 NCR integration into the system: the TT style (separate DMA), and
15465 the Falcon style (via ST-DMA, replacing ACSI). It does NOT support
15466 other schemes, like in the Hades (without DMA).
15468 Long delays for Toshiba CD-ROMs
15469 CONFIG_ATARI_SCSI_TOSHIBA_DELAY
15470 This option increases the delay after a SCSI arbitration to
15471 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
15472 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
15473 would impact performance a bit, so say N.
15475 Hades SCSI DMA emulator
15477 This option enables code which emulates the TT SCSI DMA chip on the
15478 Hades. This increases the SCSI transfer rates at least ten times
15479 compared to PIO transfers.
15483 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
15486 This driver is also available as a module ( = code which can be
15487 inserted in and removed from the running kernel whenever you
15488 want). The module is called ariadne.o. If you want to compile it as
15489 a module, say M here and read Documentation/modules.txt.
15493 If you have a Village Tronic Ariadne II Ethernet adapter, say Y.
15496 This driver is also available as a module ( = code which can be
15497 inserted in and removed from the running kernel whenever you
15498 want). The module is called ariadne2.o. If you want to compile it as
15499 a module, say M here and read Documentation/modules.txt.
15503 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
15506 This driver is also available as a module ( = code which can be
15507 inserted in and removed from the running kernel whenever you
15508 want). The module is called a2065.o. If you want to compile it as a
15509 module, say M here and read Documentation/modules.txt.
15513 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
15515 This driver is also available as a module ( = code which can be
15516 inserted in and removed from the running kernel whenever you
15517 want). The module is called hydra.o. If you want to compile it as a
15518 module, say M here and read Documentation/modules.txt.
15520 Pcmcia NE2000 compatible support
15522 If you have a pcmcia ne2000 compatible adapter, say Y. Otherwise,
15525 This driver is also available as a module ( = code which can be
15526 inserted in and removed from the running kernel whenever you
15527 want). The module is called apne.o. If you want to compile it as a
15528 module, say M here and read Documentation/modules.txt.
15530 Atari Lance support
15532 Say Y to include support for several Atari Ethernet adapters based
15533 on the AMD Lance chipset: RieblCard (with or without battery), or
15534 PAMCard VME (also the version by Rhotron, with different addresses).
15537 CONFIG_ATARI_BIONET
15538 Say Y to include support for BioData's BioNet-100 Ethernet adapter
15539 for the ACSI port. The driver works (has to work...) with a polled
15540 I/O scheme, so it's rather slow :-(
15543 CONFIG_ATARI_PAMSNET
15544 Say Y to include support for the PAMsNet Ethernet adapter for the
15545 ACSI port ("ACSI node"). The driver works (has to work...) with a
15546 polled I/O scheme, so it's rather slow :-(
15548 Amiga mouse support
15550 If you want to be able to use an Amiga mouse in Linux, say Y.
15552 This driver is also available as a module ( = code which can be
15553 inserted in and removed from the running kernel whenever you want).
15554 The module is called amigamouse.o. If you want to compile it as a
15555 module, say M here and read Documentation/modules.txt.
15557 Atari mouse support
15559 If you want to be able to use an Atari mouse in Linux, say Y.
15561 This driver is also available as a module ( = code which can be
15562 inserted in and removed from the running kernel whenever you want).
15563 The module is called atarimouse.o. If you want to compile it as a
15564 module, say M here and read Documentation/modules.txt.
15566 Atari MFP serial support
15567 CONFIG_ATARI_MFPSER
15568 If you like to use the MFP serial ports ("Modem1", "Serial1") under
15569 Linux, say Y. The driver equally supports all kinds of MFP serial
15570 ports and automatically detects whether Serial1 is available.
15572 This driver is also available as a module ( = code which can be
15573 inserted in and removed from the running kernel whenever you want).
15574 If you want to compile it as a module, say M here and read
15575 Documentation/modules.txt.
15577 Note for Falcon users: You also have an MFP port, it's just not
15578 wired to the outside... But you could use the port under Linux.
15580 Atari SCC serial support
15582 If you have serial ports based on a Zilog SCC chip (Modem2, Serial2,
15583 LAN) and like to use them under Linux, say Y. All built-in SCC's are
15584 supported (TT, MegaSTE, Falcon), and also the ST-ESCC. If you have
15585 two connectors for channel A (Serial2 and LAN), they are visible as
15586 two separate devices.
15588 This driver is also available as a module ( = code which can be
15589 inserted in and removed from the running kernel whenever you want).
15590 If you want to compile it as a module, say M here and read
15591 Documentation/modules.txt.
15593 Atari SCC serial DMA support
15594 CONFIG_ATARI_SCC_DMA
15595 This enables DMA support for receiving data on channel A of the SCC.
15596 If you have a TT you may say Y here and read
15597 drivers/char/atari_SCC.README. All other users should say N here,
15598 because only the TT has SCC-DMA, even if your machine keeps claiming
15601 Atari MIDI serial support
15603 If you want to use your Atari's MIDI port in Linux, say Y.
15605 This driver is also available as a module ( = code which can be
15606 inserted in and removed from the running kernel whenever you
15607 want). If you want to compile it as a module, say M here and read
15608 Documentation/modules.txt.
15610 Atari DSP56k Digital Signal Processor support (EXPERIMENTAL)
15611 CONFIG_ATARI_DSP56K
15612 If you want to be able to use the DSP56001 in Falcons, say Y. This
15613 driver is still experimental, and if you don't know what it is, or
15614 if you don't have this processor, just say N.
15616 This driver is also available as a module ( = code which can be
15617 inserted in and removed from the running kernel whenever you want).
15618 If you want to compile it as a module, say M here and read
15619 Documentation/modules.txt.
15621 Amiga builtin serial support
15622 CONFIG_AMIGA_BUILTIN_SERIAL
15623 If you want to use your Amiga's built-in serial port in Linux,
15626 This driver is also available as a module ( = code which can be
15627 inserted in and removed from the running kernel whenever you
15628 want). If you want to compile it as a module, say M here and read
15629 Documentation/modules.txt.
15631 GVP IO-Extender support
15633 If you want to use a GVP IO-Extender serial card in Linux, say Y.
15636 Multiface Card III serial support
15637 CONFIG_MULTIFACE_III_TTY
15638 If you want to use a Multiface III card's serial port in Linux,
15641 This driver is also available as a module ( = code which can be
15642 inserted in and removed from the running kernel whenever you want).
15643 If you want to compile it as a module, say M here and read
15644 Documentation/modules.txt.
15646 Atari DMA sound support
15647 CONFIG_DMASOUND_ATARI
15648 If you want to use the internal audio of your Atari in Linux, answer
15649 Y to this question. This will provide a Sun-like /dev/audio,
15650 compatible with the Linux/i386 sound system. Otherwise, say N.
15652 This driver is also available as a module ( = code which can be
15653 inserted in and removed from the running kernel whenever you
15654 want). If you want to compile it as a module, say M here and read
15655 Documentation/modules.txt.
15657 PowerMac DMA sound support
15658 CONFIG_DMASOUND_AWACS
15659 If you want to use the internal audio of your PowerMac in Linux,
15660 answer Y to this question. This will provide a Sun-like /dev/audio,
15661 compatible with the Linux/i386 sound system. Otherwise, say N.
15663 This driver is also available as a module ( = code which can be
15664 inserted in and removed from the running kernel whenever you
15665 want). If you want to compile it as a module, say M here and read
15666 Documentation/modules.txt.
15668 Amiga DMA sound support
15669 CONFIG_DMASOUND_PAULA
15670 If you want to use the internal audio of your Amiga in Linux, answer
15671 Y to this question. This will provide a Sun-like /dev/audio,
15672 compatible with the Linux/i386 sound system. Otherwise, say N.
15674 This driver is also available as a module ( = code which can be
15675 inserted in and removed from the running kernel whenever you
15676 want). If you want to compile it as a module, say M here and read
15677 Documentation/modules.txt.
15680 CONFIG_DMASOUND_Q40
15681 If you want to use the internal audio of your Q40 in Linux, answer
15682 Y to this question. This will provide a Sun-like /dev/audio,
15683 compatible with the Linux/i386 sound system. Otherwise, say N.
15685 This driver is also available as a module ( = code which can be
15686 inserted in and removed from the running kernel whenever you
15687 want). If you want to compile it as a module, say M here and read
15688 Documentation/modules.txt.
15690 HP DCA serial support
15692 If you want to use the internal "DCA" serial ports on an HP300
15693 machine, say Y here.
15695 HP on-board LANCE support
15697 If you want to use the builtin "LANCE" Ethernet controller on an
15698 HP300 machine, say Y here.
15702 Say Y here to enable support for the "DIO" expansion bus used in
15703 HP300 machines. If you are using such a system you almost certainly
15708 There are four types of PowerPC chips supported. The more common
15709 types (601, 603, 604, 740, 750), the Motorola embedded versions
15710 (821, 823, 850, 855, 860), the IBM embedded versions (403 and
15711 405) and the high end 64 bit Power processors (Power 3, Power 4).
15712 Unless you are building a kernel for one of the embedded
15713 processor systems, or a 64 bit IBM RS/6000, choose 6xx. Note that
15714 the kernel runs in 32-bit mode even on 64-bit chips.
15718 Linux currently supports several different kinds of PowerPC-based
15719 machines: Apple Power Macintoshes and clones (such as the Motorola
15720 Starmax series), PReP (PowerPC Reference Platform) machines such as
15721 the Motorola PowerStack, Amiga Power-Up systems (APUS), CHRP and the
15722 embedded MBX boards from Motorola. Currently, a single kernel binary
15723 only supports one type or the other. However, there is very early
15724 work on support for CHRP, PReP and PowerMac's from a single binary.
15726 Power management support for PowerBooks
15728 This provides support for putting a PowerBook to sleep; it also
15729 enables media bay support. Power management works on the
15730 PB2400/3400/3500, Wallstreet, Lombard, and Bronze PowerBook G3. You
15731 must get the power management daemon, pmud, to make it work and you
15732 must have the /dev/pmu device (see the pmud README).
15734 Get pmud from ftp://linuxcare.com.au/pub/ppclinux/pmud/
15736 If you have a PowerBook, you should say Y.
15738 You may also want to compile the dma sound driver as a module and
15739 have it autoloaded. The act of removing the module shuts down the
15740 sound hardware for more power savings.
15742 Mac-on-Linux support
15744 This option enables low-level support for Mac-on-Linux.
15745 MOL lets you run MacOS and Linux simultaneously. Please
15746 visit <http://www.maconlinux.org> for more information.
15749 ADB raw keycode support
15750 CONFIG_MAC_ADBKEYCODES
15751 This provides support for sending raw ADB keycodes to console
15752 devices. This is the default up to 2.4.0, but in future this may be
15753 phased out in favor of generic Linux keycodes. If you say Y here, you
15754 can dynamically switch via the
15755 /proc/sys/dev/mac_hid/keyboard_sends_linux_keycodes
15756 sysctl and with the "keyboard_sends_linux_keycodes=" kernel argument.
15758 If unsure, say Y here.
15760 Mouse button 2+3 emulation support
15761 CONFIG_MAC_EMUMOUSEBTN
15762 This provides generic support for emulating the 2nd and 3rd mouse
15763 button with keypresses. If you say Y here, the emulation is still
15764 disabled by default. The emulation is controlled by these sysctl entries:
15765 /proc/sys/dev/mac_hid/mouse_button_emulation
15766 /proc/sys/dev/mac_hid/mouse_button2_keycode
15767 /proc/sys/dev/mac_hid/mouse_button3_keycode
15769 Enhanced Real Time Clock Support
15771 If you say Y here and create a character special file /dev/rtc with
15772 major number 10 and minor number 135 using mknod ("man mknod"), you
15773 will get access to the real time clock (or hardware clock) built
15774 into your computer.
15776 If unsure, say Y here.
15778 Support for Open Firmware device tree in /proc
15779 CONFIG_PROC_DEVICETREE
15780 This option adds a device-tree directory under /proc which contains
15781 an image of the device tree that the kernel copies from Open
15782 Firmware. If unsure, say Y here.
15784 MESH (Power Mac internal SCSI) support
15786 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
15787 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
15788 other Power Macintoshes do). Say Y to include support for this SCSI
15789 adaptor. This driver is also available as a module called mesh.o
15790 ( = code which can be inserted in and removed from the running
15791 kernel whenever you want). If you want to compile it as a module,
15792 say M here and read Documentation/modules.txt.
15794 Maximum synchronous transfer rate
15795 CONFIG_SCSI_MESH_SYNC_RATE
15796 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
15797 drives a bus which is entirely internal to the machine (such as the
15798 7500, 7600, 8500, etc.), the MESH is capable of synchronous
15799 operation at up to 10 MB/s. On machines where the SCSI bus
15800 controlled by the MESH can have external devices connected, it is
15801 usually rated at 5 MB/s. 5 is a safe value here unless you know the
15802 MESH SCSI bus is internal only; in that case you can say 10. Say 0
15803 to disable synchronous operation.
15805 53C94 (Power Mac external SCSI) support
15806 CONFIG_SCSI_MAC53C94
15807 On Power Macintoshes (and clones) with two SCSI buses, the external
15808 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
15809 machines which only have one SCSI bus, such as the 7200, also use
15810 the 53C94. Say Y to include support for the 53C94.
15812 This driver is also available as a module called mac53c94.o ( = code
15813 which can be inserted in and removed from the running kernel
15814 whenever you want). If you want to compile it as a module, say M
15815 here and read Documentation/modules.txt.
15817 MACE (Power Mac Ethernet) support
15819 Power Macintoshes and clones with Ethernet built-in on the
15820 motherboard will usually use a MACE (Medium Access Control for
15821 Ethernet) interface. Say Y to include support for the MACE chip.
15823 This driver is also available as a module called mace.o ( = code
15824 which can be inserted in and removed from the running kernel
15825 whenever you want). If you want to compile it as a module, say M
15826 here and read Documentation/modules.txt.
15828 BMAC (G3 ethernet) support
15830 Say Y for support of BMAC Ethernet interfaces. These are used on G3
15833 This driver is also available as a module called bmac.o ( = code
15834 which can be inserted in and removed from the running kernel
15835 whenever you want). If you want to compile it as a module, say M
15836 here and read Documentation/modules.txt.
15838 GMAC (G4/iBook ethernet) support
15840 Say Y for support of GMAC Ethernet interfaces. These are used on G4
15841 and iBook computers.
15843 This driver is also available as a module called gmac.o ( = code
15844 which can be inserted in and removed from the running kernel
15845 whenever you want). If you want to compile it as a module, say M
15846 here and read Documentation/modules.txt.
15848 Symbios 53c885 (Synergy ethernet) support
15850 This is and Ethernet driver for the dual-function NCR 53C885
15851 SCSI/Ethernet controller.
15853 This driver is also available as a module called ncr885e.o ( = code
15854 which can be inserted in and removed from the running kernel
15855 whenever you want). If you want to compile it as a module, say M
15856 here and read Documentation/modules.txt.
15858 National DP83902AV (Oak ethernet) support
15860 Say Y if your machine has this type of Ethernet network card.
15862 This driver is also available as a module called oaknet.o ( = code
15863 which can be inserted in and removed from the running kernel
15864 whenever you want). If you want to compile it as a module, say M
15865 here and read Documentation/modules.txt.
15869 Support for audio/video capture and overlay devices and FM radio
15870 cards. The exact capabilities of each device vary. User tools for
15871 this are available from
15872 ftp://ftp.uk.linux.org/pub/linux/video4linux .
15874 If you are interested in writing a driver for such an audio/video
15875 device or user software interacting with such a driver, please read
15876 the file Documentation/video4linux/API.html.
15878 This driver is also available as a module called videodev.o ( = code
15879 which can be inserted in and removed from the running kernel
15880 whenever you want). If you want to compile it as a module, say M
15881 here and read Documentation/modules.txt.
15883 Video For Linux /proc file system information
15884 CONFIG_VIDEO_PROC_FS
15885 If you say Y here, you are able to access video device information
15888 To use this option, you have to check, that the "/proc file system
15889 support" (CONFIG_PROC_FS) is enabled too.
15891 AIMSlab RadioTrack (aka RadioReveal) support
15892 CONFIG_RADIO_RTRACK
15893 Choose Y here if you have one of these FM radio cards, and then fill
15894 in the port address below.
15896 Note that newer AIMSlab RadioTrack cards have a different chipset
15897 and are not supported by this driver. For these cards, use the
15898 RadioTrack II driver below.
15900 If you have a GemTeks combined (PnP) sound- and radio card you must
15901 use this driver as a module and setup the card with isapnptools. You
15902 must also pass the module a suitable io parameter, 0x248 has been
15903 reported to be used by these cards.
15905 In order to control your radio card, you will need to use programs
15906 that are compatible with the Video for Linux API. Information on
15907 this API and pointers to "v4l" programs may be found on the WWW at
15908 http://roadrunner.swansea.uk.linux.org/v4l.shtml . More information
15909 is contained in the file Documentation/video4linux/radiotrack.txt.
15911 If you want to compile this driver as a module ( = code which can be
15912 inserted in and removed from the running kernel whenever you want),
15913 say M here and read Documentation/modules.txt. The module will be
15914 called radio-aimslab.o.
15916 RadioTrack i/o port
15917 CONFIG_RADIO_RTRACK_PORT
15918 Enter either 0x30f or 0x20f here. The card default is 0x30f, if you
15919 haven't changed the jumper setting on the card.
15921 AIMSlab RadioTrack II support
15922 CONFIG_RADIO_RTRACK2
15923 Choose Y here if you have this FM radio card, and then fill in the
15924 port address below.
15926 In order to control your radio card, you will need to use programs
15927 that are compatible with the Video for Linux API. Information on
15928 this API and pointers to "v4l" programs may be found on the WWW at
15929 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15931 If you want to compile this driver as a module ( = code which can be
15932 inserted in and removed from the running kernel whenever you want),
15933 say M here and read Documentation/modules.txt. The module will be
15934 called radio-rtrack2.o.
15936 RadioTrack II i/o port
15937 CONFIG_RADIO_RTRACK2_PORT
15938 Enter either 0x30c or 0x20c here. The card default is 0x30c, if you
15939 haven't changed the jumper setting on the card.
15941 Aztech/Packard Bell Radio
15942 CONFIG_RADIO_AZTECH
15943 Choose Y here if you have one of these FM radio cards, and then fill
15944 in the port address below.
15946 In order to control your radio card, you will need to use programs
15947 that are compatible with the Video for Linux API. Information on
15948 this API and pointers to "v4l" programs may be found on the WWW at
15949 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15951 If you want to compile this driver as a module ( = code which can be
15952 inserted in and removed from the running kernel whenever you want),
15953 say M here and read Documentation/modules.txt. The module will be
15954 called radio-aztech.o.
15956 Aztech/Packard Bell radio card i/o port
15957 CONFIG_RADIO_AZTECH_PORT
15958 Enter either 0x350 or 0x358 here. The card default is 0x350, if you
15959 haven't changed the setting of jumper JP3 on the card. Removing the
15960 jumper sets the card to 0x358.
15962 ADS Cadet AM/FM Radio Tuner Card
15964 Choose Y here if you have one of these AM/FM radio cards, and then
15965 fill in the port address below.
15967 In order to control your radio card, you will need to use programs
15968 that are compatible with the Video for Linux API. Information on
15969 this API and pointers to "v4l" programs may be found on the WWW at
15970 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15972 Further documentation on this driver can be found on the WWW at
15973 http://linux.blackhawke.net/cadet.html .
15975 If you want to compile this driver as a module ( = code which can be
15976 inserted in and removed from the running kernel whenever you want),
15977 say M here and read Documentation/modules.txt. The module will be
15978 called radio-cadet.o.
15981 CONFIG_RADIO_SF16FMI
15982 Choose Y here if you have one of these FM radio cards, and then fill
15983 in the port address below.
15985 In order to control your radio card, you will need to use programs
15986 that are compatible with the Video for Linux API. Information on
15987 this API and pointers to "v4l" programs may be found on the WWW at
15988 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15990 If you want to compile this driver as a module ( = code which can be
15991 inserted in and removed from the running kernel whenever you want),
15992 say M here and read Documentation/modules.txt. The module will be
15993 called radio-sf16fmi.o
15995 SF16FMI I/O port (0x284 or 0x384)
15996 CONFIG_RADIO_SF16FMI_PORT
15997 Enter the I/O port of your SF16FMI radio card.
16000 CONFIG_RADIO_TYPHOON
16001 Choose Y here if you have one of these FM radio cards, and then fill
16002 in the port address and the frequency used for muting below.
16004 In order to control your radio card, you will need to use programs
16005 that are compatible with the Video for Linux API. Information on
16006 this API and pointers to "v4l" programs may be found on the WWW at
16007 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
16009 If you want to compile this driver as a module ( = code which can be
16010 inserted in and removed from the running kernel whenever you want),
16011 say M here and read Documentation/modules.txt. The module will be
16012 called radio-typhoon.o
16014 Support for /proc/radio-typhoon
16015 CONFIG_RADIO_TYPHOON_PROC_FS
16016 Say Y here if you want the typhoon radio card driver to write
16017 status information (frequency, volume, muted, mute frequency,
16018 base address) to /proc/radio-typhoon. The file can be viewed with
16019 your favorite pager (i.e. use "more /proc/radio-typhoon" or "less
16020 /proc/radio-typhoon" or simply "cat /proc/radio-typhoon").
16022 Typhoon I/O port (0x316 or 0x336)
16023 CONFIG_RADIO_TYPHOON_PORT
16024 Enter the I/O port of your Typhoon or EcoRadio radio card.
16026 Typhoon frequency set when muting the device (kHz)
16027 CONFIG_RADIO_TYPHOON_MUTEFREQ
16028 Enter the frequency used for muting the radio. The device is never
16029 completely silent. If the volume is just turned down, you can still
16030 hear silent voices and music. For that reason, the frequency of the
16031 radio device is set to the frequency you can enter here whenever
16032 the device is muted. There should be no local radio station at that
16036 CONFIG_RADIO_ZOLTRIX
16037 Choose Y here if you have one of these FM radio cards, and then fill
16038 in the port address below.
16040 In order to control your radio card, you will need to use programs
16041 that are compatible with the Video for Linux API. Information on
16042 this API and pointers to "v4l" programs may be found on the WWW at
16043 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
16045 If you want to compile this driver as a module ( = code which can be
16046 inserted in and removed from the running kernel whenever you want),
16047 say M here and read Documentation/modules.txt. The module will be
16048 called radio-zoltrix.o
16050 ZOLTRIX I/O port (0x20c or 0x30c)
16051 CONFIG_RADIO_ZOLTRIX_PORT
16052 Enter the I/O port of your Zoltrix radio card.
16054 IIC on parallel port
16056 I2C is a simple serial bus system used in many micro controller
16057 applications. Saying Y here will allow you to use your parallel port
16058 as an I2C interface.
16060 If you want to compile this driver as a module ( = code which can be
16061 inserted in and removed from the running kernel whenever you want),
16062 say M here and read Documentation/modules.txt. The module will be
16063 called i2c-parport.o.
16066 CONFIG_RADIO_MIROPCM20
16067 Choose Y here if you have this FM radio card. You also need to say Y
16068 to "ACI mixer (miroPCM12/PCM20)" (in "additional low level sound
16069 drivers") for this to work.
16071 In order to control your radio card, you will need to use programs
16072 that are compatible with the Video for Linux API. Information on
16073 this API and pointers to "v4l" programs may be found on the WWW at
16074 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
16076 If you want to compile this driver as a module ( = code which can be
16077 inserted in and removed from the running kernel whenever you want),
16078 say M here and read Documentation/modules.txt. The module will be
16079 called radio-miropcm20.o
16082 CONFIG_RADIO_GEMTEK
16083 Choose Y here if you have this FM radio card, and then fill in the
16084 port address below.
16086 In order to control your radio card, you will need to use programs
16087 that are compatible with the Video for Linux API. Information on
16088 this API and pointers to "v4l" programs may be found on the WWW at
16089 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
16091 If you want to compile this driver as a module ( = code which can be
16092 inserted in and removed from the running kernel whenever you want),
16093 say M here and read Documentation/modules.txt. The module will be
16094 called radio-gemtek.o.
16097 CONFIG_RADIO_GEMTEK_PORT
16098 Enter either 0x20c, 0x30c, 0x24c or 0x34c here. The card default is
16099 0x34c, if you haven't changed the jumper setting on the card. On
16100 Sound Vision 16 Gold PnP with FM Radio (ESS1869+FM Gemtek), the i/o
16103 PlanB Video-In for PowerMacs
16105 PlanB is the V4L driver for the PowerMac 7x00/8x00 series video
16106 input hardware. If you want to experiment with this, say Y.
16107 Otherwise, or if you don't understand a word, say N.
16108 See http://www.cpu.lu/~mlan/planb.html for more info.
16110 Saying M will compile this driver as a module (planb.o).
16112 TerraTec ActiveRadio
16113 CONFIG_RADIO_TERRATEC
16114 Choose Y here if you have this FM radio card, and then fill in the
16115 port address below. (TODO)
16117 Note: This driver is in its early stages. Right now volume and
16118 frequency control and muting works at least for me, but
16119 unfortunately i have not found anybody who wants to use this card
16120 with Linux. So if it is this what YOU are trying to do right now,
16121 PLEASE DROP ME A NOTE!! Rolf Offermanns (rolf@offermanns.de)
16123 In order to control your radio card, you will need to use programs
16124 that are compatible with the Video for Linux API. Information on
16125 this API and pointers to "v4l" programs may be found on the WWW at
16126 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
16128 If you want to compile this driver as a module ( = code which can be
16129 inserted in and removed from the running kernel whenever you want),
16130 say M here and read Documentation/modules.txt. The module will be
16131 called radio-terratec.o.
16133 Terratec i/o port (normally 0x590)
16134 CONFIG_RADIO_TERRATEC_PORT
16135 Fill in the i/o port of your TerraTec FM radio card. If unsure, go
16139 # Zoran ZR36057/36060 support
16140 # CONFIG_VIDEO_ZORAN
16142 # Include support for Iomega Buz
16145 Trust FM radio card
16147 This is a driver for the Trust FM radio cards. Say Y if you have
16148 such a card and want to use it under Linux.
16150 This driver is also available as a module called radio-trust.o ( =
16151 code which can be inserted in and removed from the running kernel
16152 whenever you want). If you want to compile it as a module, say M
16153 here and read Documentation/modules.txt.
16155 Trust i/o port (usually 0x350 or 0x358)
16156 CONFIG_RADIO_TRUST_PORT
16157 Enter the i/o port of your Trust FM radio card. If unsure, try the
16158 values "0x350" or "0x358".
16160 BT848 Video For Linux
16162 Support for BT848 based frame grabber/overlay boards. This includes
16163 the Miro, Hauppauge and STB boards. Please read the material in
16164 Documentation/video4linux/bttv for more information.
16166 If you say Y or M here, you need to say Y or M to "I2C support" and
16167 "I2C bit-banging interfaces" in the character device section.
16169 This driver is available as a module called bttv.o ( = code
16170 which can be inserted in and removed from the running kernel
16171 whenever you want). If you want to compile it as a module, say M
16172 here and read Documentation/modules.txt.
16174 ZR36120/36125 Video for Linux
16175 CONFIG_VIDEO_ZR36120
16176 Support for ZR36120/ZR36125 based frame grabber/overlay boards.
16177 This includes the Victor II, WaveWatcher, Video Wonder, Maxi-TV,
16178 and Buster boards. Please read the material in
16179 Documentation/video4linux/zr36120.txt for more information.
16181 This driver is also available as a module called zr36120.o ( = code
16182 which can be inserted in and removed from the running kernel
16183 whenever you want). If you want to compile it as a module, say M
16184 here and read Documentation/modules.txt.
16186 SAA5249 Teletext processor
16187 CONFIG_VIDEO_SAA5249
16188 Support for I2C bus based teletext using the SAA5249 chip. At the
16189 moment this is only useful on some European WinTV cards.
16191 This driver is also available as a module called saa5249.o ( = code
16192 which can be inserted in and removed from the running kernel
16193 whenever you want). If you want to compile it as a module, say M
16194 here and read Documentation/modules.txt.
16196 Quickcam BW Video For Linux
16197 CONFIG_VIDEO_BWQCAM
16198 Say Y have if you the black and white version of the QuickCam
16199 camera. See the next option for the color version.
16201 This driver is also available as a module called bw-qcam.o ( = code
16202 which can be inserted in and removed from the running kernel
16203 whenever you want). If you want to compile it as a module, say M
16204 here and read Documentation/modules.txt.
16206 Colour QuickCam Video For Linux
16208 This is the video4linux driver for the colour version of the
16209 Connectix Quickcam. If you have one of these cameras, say Y here,
16210 otherwise say N. This driver does not work with the original
16211 monochrome Quickcam, Quickcam VC or QuickClip. It is also available
16212 as a module (c-qcam.o). Read Documentation/video4linux/CQcam.txt for
16215 CPiA Video For Linux
16217 This is the video4linux driver for cameras based on Vision's CPiA
16218 (Colour Processor Interface ASIC), such as the Creative Labs Video
16219 Blaster Webcam II. If you have one of these cameras, say Y here
16220 and select parallel port and/or USB lowlevel support below,
16221 otherwise say N. This will not work with the Creative Webcam III.
16223 Please read Documentation/video4linux/README.cpia for more
16226 This driver is also available as a module (cpia.o).
16228 CPiA Parallel Port Lowlevel Support
16229 CONFIG_VIDEO_CPIA_PP
16230 This is the lowlevel parallel port support for cameras based on
16231 Vision's CPiA (Colour Processor Interface ASIC), such as the
16232 Creative Webcam II. If you have the parallel port version of one
16233 of these cameras, say Y here, otherwise say N. It is also available
16234 as a module (cpia_pp.o).
16236 CPiA USB Lowlevel Support
16237 CONFIG_VIDEO_CPIA_USB
16238 This is the lowlevel USB support for cameras based on Vision's CPiA
16239 (Colour Processor Interface ASIC), such as the Creative Webcam II.
16240 If you have the USB version of one of these cameras, say Y here,
16241 otherwise say N. This will not work with the Creative Webcam III.
16242 It is also available as a module (cpia_usb.o).
16244 Mediavision Pro Movie Studio Video For Linux
16246 Say Y if you have such a thing. This driver is also available as a
16247 module called pms.o ( = code which can be inserted in and removed
16248 from the running kernel whenever you want). If you want to compile
16249 it as a module, say M here and read Documentation/modules.txt.
16251 SAB3036 tuner support
16253 Say Y here to include support for Philips SAB3036 compatible tuners.
16254 If in doubt, say N.
16256 Compaq SMART2 support
16258 This is the driver for Compaq Smart Array controllers.
16259 Everyone using these boards should say Y here.
16260 See the file Documentation/cpqarray.txt for the current list of
16261 boards supported by this driver, and for further information
16262 on the use of this driver.
16269 This selects what ARM system you wish to build the kernel for. It
16270 also selects to some extent the CPU type. If you are unsure what
16271 to set this option to, please consult any information supplied with
16274 2MB physical memory
16276 Say Y here if your Archimedes or A5000 system has only 2MB of
16277 memory, otherwise say N. The resulting kernel will not run on a
16278 machine with 4MB of memory.
16280 Include support for the CATS
16282 Say Y here if you intend to run this kernel on the CATS.
16284 Saying N will reduce the size of the Footbridge kernel.
16286 Include support for the EBSA285
16287 CONFIG_ARCH_EBSA285
16288 Say Y here if you intend to run this kernel on the EBSA285 card
16289 in host ("central function") mode.
16291 Saying N will reduce the size of the Footbridge kernel.
16293 Include support for the LinkUp Systems L7200 SDB
16295 Say Y here if you intend to run this kernel on a LinkUp Systems
16296 L7200 Software Development Board which uses an ARM720T processor.
16297 Information on this board can be obtained at:
16299 http://www.linkupsys.com/
16301 If you have any questions or comments about the Linux kernel port
16302 to this board, send e-mail to sjhill@cotw.com
16304 Include support for the NetWinder
16305 CONFIG_ARCH_NETWINDER
16306 Say Y here if you intend to run this kernel on the Rebel.COM
16307 NetWinder. Information about this machine can be found at:
16309 http://www.netwinder.org/
16311 Saying N will reduce the size of the Footbridge kernel.
16313 Include support for the Compaq Personal Server
16314 CONFIG_ARCH_PERSONAL_SERVER
16315 Say Y here if you intend to run this kernel on the Compaq
16318 Saying N will reduce the size of the Footbridge kernel.
16320 The Compaq Personal Server is not available for purchase.
16321 There are no product plans beyond the current research
16322 prototypes at this time. Information is available at:
16324 http://crl.research.compaq.com/projects/personalserver
16326 If you have any questions or comments about the Compaq Personal
16327 Server, send e-mail to skiff@crl.dec.com
16329 Include support for Assabet
16330 CONFIG_SA1100_ASSABET
16331 Say Y here if you are using the Intel(R) StrongARM(R) SA-1110
16332 Microprocessor Development Board (also known as the Assabet).
16334 Include support for Neponset
16335 CONFIG_ASSABET_NEPONSET
16336 Say Y here if you are using the Intel(R) StrongARM(R) SA-1110
16337 Microprocessor Development Board (Assabet) with the SA-1111
16338 Development Board (Nepon).
16340 Include support for the Compaq iPAQ H3600 (Bitsy)
16341 CONFIG_SA1100_BITSY
16342 Say Y here if you intend to run this kernel on the Compaq iPAQ
16343 H3600 handheld computer. Information about this machine and the
16344 Linux port to this machine can be found at:
16346 http://www.handhelds.org/Compaq/index.html#iPAQ_H3600
16347 http://www.compaq.com/products/handhelds/pocketpc/
16349 Include support for Brutus
16350 CONFIG_SA1100_BRUTUS
16351 Say Y here if you are using the Intel(R) StrongARM(R) SA-1100
16352 Microprocessor Development Board (also known as the Brutus).
16354 Include support for LART
16356 Say Y here if you are using the Linux Advanced Radio Terminal
16357 (also known as the LART). See http://www.lart.tudelft.nl/ for
16358 information on the LART.
16360 Include support for GraphicsClient
16361 CONFIG_SA1100_GRAPHICSCLIENT
16362 Say Y here if you are using an Applied Data Systems Intel(R)
16363 StrongARM(R) SA-1100 based Graphics Client SBC. See
16364 http://www.flatpanels.com/ for information on this system.
16366 Include support for Victor
16367 CONFIG_SA1100_VICTOR
16368 Say Y here if you are using a Visu Aide Intel(R) StrongARM(R)
16369 SA-1100 based Victor Digital Talking Book Reader. See
16370 http://www.visuaide.com/pagevictor.en.html for information on
16373 Support ARM610 processor
16375 Say Y here if you wish to include support for the ARM610 processor.
16377 Support ARM710 processor
16379 Say Y here if you wish to include support for the ARM710 processor.
16381 Support StrongARM(R) SA-110 processor
16383 Say Y here if you wish to include support for the Intel(R)
16384 StrongARM(R) SA-110 processor.
16386 Support ARM720 processor
16388 Say Y here if you wish to include support for the ARM720 processor.
16392 Say Y here if you wish to include support for the ARM920 processor.
16394 Support ARM610 processor
16396 Say Y here if you wish to include support for the ARM610 processor.
16398 Support ARM710 processor
16400 Say Y here if you wish to include support for the ARM710 processor.
16402 Support StrongARM(R) SA-110 processor
16404 Say Y here if you wish to include support for the Intel(R)
16405 StrongARM(R) SA-110 processor.
16407 Support ARM720 processor
16409 Say Y here if you wish to include support for the ARM720 processor.
16413 Say Y here if you wish to include support for the ARM920 processor.
16417 Say Y to include the NWFPE floating point emulator in the kernel.
16418 This is necessary to run most binaries. Linux does not currently
16419 support floating point hardware so you need to say Y here even if
16420 your machine has an FPA or floating point co-processor podule.
16422 It is also possible to say M to build the emulator as a module
16423 (nwfpe.o) or indeed to leave it out altogether. However, unless you
16424 know what you are doing this can easily render your machine
16425 unbootable. Saying Y is the safe option.
16427 You may say N here if you are going to load the Acorn FPEmulator
16428 early in the bootup.
16430 DS1620 Thermometer support
16432 Say Y here to include support for the thermal management hardware
16433 found in the NetWinder. This driver allows the user to control the
16434 temperature set points and to read the current temperature.
16436 It is also possible to say M here to build it as a module (ds1620.o)
16437 It is recommended to be used on a NetWinder, but it is not a
16440 Verbose kernel error messages
16441 CONFIG_DEBUG_ERRORS
16442 This option controls verbose debugging information which can be
16443 printed when the kernel detects an internal error. This debugging
16444 information is useful to kernel hackers when tracking down problems,
16445 but mostly meaningless to other people. It's safe to say Y unless
16446 you are concerned with the code size or don't want to see these
16449 Compile kernel with frame pointer
16450 CONFIG_FRAME_POINTER
16451 If you say Y here, the resulting kernel will be slightly larger and
16452 slower, but it will give useful debugging information. If you don't
16453 debug the kernel, you can say N.
16455 User fault debugging
16457 When a user program crashes due to an exception, the kernel can
16458 print a brief message explaining what the problem was. This is
16459 sometimes helpful for debugging but serves no purpose on a
16460 production system. Most people should say N here.
16462 Include gdb debugging information in kernel binary
16464 Say Y here to include source-level debugging information in the
16465 `vmlinux' binary image. This is handy if you want to use gdb or
16466 addr2line to debug the kernel. It has no impact on the in-memory
16467 footprint of the running kernel but it can increase the amount of
16468 time and disk space needed for compilation of the kernel. If in
16471 Kernel low-level debugging functions
16473 Say Y here to include definitions of printascii, printchar, printhex
16474 in the kernel. This is helpful if you are debugging code that
16475 executes before the console is initialized.
16477 Kernel low-level debugging messages via footbridge serial port
16478 CONFIG_DEBUG_DC21285_PORT
16479 Say Y here if you want the low-level print routines to direct their
16480 output to the serial port in the DC21285 (Footbridge).
16482 Split initialisation functions into discardable section
16483 CONFIG_TEXT_SECTIONS
16484 If you say Y here, kernel code that is only used during
16485 initialisation is collected into a special area of the kernel so
16486 that it can be discarded and the memory reclaimed when
16487 initialisation is complete. In addition, if the kernel you wish to
16488 build is able to run on multiple architectures, it allows the unused
16489 code to be discarded. Some versions of binutils, however, have a bug
16490 that causes the kernel to crash during startup when this option is
16491 enabled. Say Y unless you experience problems that you suspect may
16494 Disable pgtable cache (EXPERIMENTAL)
16495 CONFIG_NO_PGT_CACHE
16496 Normally the kernel maintains a `quicklist' of preallocated
16497 pagetable structures in order to increase performance. On machines
16498 with very few pages this may however be a loss. Say Y here to
16499 disable the pgtable cache.
16501 RISC OS personality
16503 Say Y here to include the kernel code necessary if you want to run
16504 Acorn RISC OS/Arthur binaries under Linux. This code is still very
16505 experimental; if this sounds frightening, say N and sleep in peace.
16506 You can also say M here to compile this support as a module (which
16507 will be called arthur.o).
16509 Initial kernel command line
16511 On some architectures (EBSA110 and CATS), there is currently no way
16512 for the boot loader to pass arguments to the kernel. For these
16513 architectures, you should supply some command-line options at build
16514 time by entering them here. As a minimum, you should specify the
16515 memory size and the root device (e.g., mem=64M root=/dev/nfs)
16517 Hardware alignment trap (EXPERIMENTAL)
16518 CONFIG_ALIGNMENT_TRAP
16519 ARM processors can not fetch/store information which is not
16520 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
16521 address divisible by 4. On 32-bit ARM processors, these non-aligned
16522 fetch/store instructions will be emulated in software if you say
16523 here, which has a severe performance impact. This is necessary for
16524 correct operation of some network protocols. With an IP-only
16525 configuration it is safe to say N, otherwise say Y.
16527 21285 serial port support
16528 CONFIG_SERIAL_21285
16529 If you have a machine based on a 21285 (Footbridge) StrongARM(R)/
16530 PCI bridge you can enable its onboard serial port by enabling this
16531 option. The device has major ID 4, minor 64.
16533 Console on 21285 serial port
16534 CONFIG_SERIAL_21285_CONSOLE
16535 If you have enabled the serial port on the 21285 footbridge you can
16536 make it the console by answering Y to this option.
16538 SA1100 serial port support
16539 CONFIG_SERIAL_SA1100
16540 If you have a machine based on a SA1100/SA1110 StrongARM CPU you can
16541 enable its onboard serial port by enabling this option.
16542 Please read Documentation/arm/SA1100/serial_UART for further info.
16544 Console on SA1100 serial port
16545 CONFIG_SERIAL_SA1100_CONSOLE
16546 If you have enabled the serial port on the SA1100/SA1110 StrongARM
16547 CPU you can make it the console by answering Y to this option.
16549 L7200 serial port support
16550 CONFIG_SERIAL_L7200
16551 If you have a LinkUp Systems L7200 board you can enable its two
16552 onboard serial ports by enabling this option. The device numbers
16553 are major ID 4 with minor 64 and 65 respectively.
16555 Console on L7200 serial port
16556 CONFIG_SERIAL_L7200_CONSOLE
16557 If you have enabled the serial ports on the L7200 development board
16558 you can make the first serial port the console by answering Y to
16562 CONFIG_HOST_FOOTBRIDGE
16563 The 21285 Footbridge chip can operate in either `host mode' or
16564 `add-in' mode. Say Y if your 21285 is in host mode, and therefore
16565 is the configuration master, otherwise say N. This must not be
16566 set to Y if the card is used in 'add-in' mode.
16568 MFM hard disk support
16570 Support the MFM hard drives on the Acorn Archimedes both
16571 on-board the A4x0 motherboards and via the Acorn MFM podules.
16572 Drives up to 64MB are supported. If you haven't got one of these
16573 machines or drives just say N.
16575 Old Archimedes floppy (1772) support
16576 CONFIG_BLK_DEV_FD1772
16577 Support the floppy drive on the Acorn Archimedes (A300, A4x0, A540,
16578 R140 and R260) series of computers; it supports only 720K floppies
16579 at the moment. If you don't have one of these machines just answer
16582 Autodetect hard drive geometry
16583 CONFIG_BLK_DEV_MFM_AUTODETECT
16584 If you answer Y, the MFM code will attempt to automatically detect
16585 the cylinders/heads/sectors count on your hard drive. WARNING: This
16586 sometimes doesn't work and it also does some dodgy stuff which
16587 potentially might damage your drive.
16589 NetWinder /dev/flash support
16591 If you say Y here and create a character device /dev/flash with
16592 major 10 and minor 160 you can manipulate the flash ROM containing
16593 the NetWinder firmware. Be careful as accidentally overwriting the
16594 flash contents can render your computer unbootable. On no account
16595 allow random users access to this device. :-)
16597 This driver is also available as a module ( = code which can be
16598 inserted in and removed from the running kernel whenever you want).
16599 The module will be called nwflash.o. If you want to compile it as a
16600 module, say M here and read Documentation/modules.txt.
16602 If you're not sure, say N.
16604 Footbridge internal watchdog
16605 CONFIG_21285_WATCHDOG
16606 The Intel Footbridge chip contains a builtin watchdog circuit. Say Y
16607 here if you wish to use this. Alternatively say M to compile the
16608 driver as a module, which will be called wdt285.o.
16610 This driver does not work on all machines. In particular, early CATS
16611 boards have hardware problems that will cause the machine to simply
16612 lock up if the watchdog fires.
16614 "If in doubt, leave it out" - say N.
16616 NetWinder WB977 watchdog
16617 CONFIG_977_WATCHDOG
16618 Say Y here to include support for the WB977 watchdog included in
16619 NetWinder machines. Alternatively say M to compile the driver as
16620 a module, which will be called wdt977.o.
16622 Not sure? It's safe to say N.
16624 IrDA subsystem support
16626 Say Y here if you want to build support for the IrDA (TM) protocols.
16627 The Infrared Data Associations (tm) specifies standards for wireless
16628 infrared communication and is supported by most laptops and PDA's.
16630 To use Linux support for the IrDA (tm) protocols, you will also need
16631 some user-space utilities like the irmanager and probably irattach
16632 as well. For more information, see the file
16633 Documentation/networking/irda.txt. You also want to read the
16634 IR-HOWTO, available at http://www.linuxdoc.org/docs.html#howto .
16636 This support is also available as a module called irda.o. If you
16637 want to compile it as a module, say M here and read
16638 Documentation/modules.txt.
16640 IrDA Cache last LSAP
16641 CONFIG_IRDA_CACHE_LAST_LSAP
16642 Say Y here if you want IrLMP to cache the last LSAP used. This makes
16643 sense since most frames will be sent/received on the same
16644 connection. Enabling this option will save a hash-lookup per frame.
16649 CONFIG_IRDA_FAST_RR
16650 Say Y here is you want IrLAP to send fast RR (Receive Ready) frames
16651 when acting as a primary station. This will make IrLAP send out a RR
16652 frame immediately when receiving a frame if its own transmit queue
16653 is currently empty. This will give a lot of speed improvement when
16654 receiving much data since the secondary station will not have to
16655 wait the max. turn around time before it is allowed to transmit the
16656 next time. If the transmit queue of the secondary is also empty the
16657 primary will back off waiting longer for sending out the RR frame
16658 until the timeout reaches the normal value. Enabling this option
16659 will make the IR-diode burn more power and thus reduce your battery
16666 Say Y here if you want the IrDA subsystem to write debug information
16667 to your syslog. You can change the debug level in
16668 /proc/sys/net/irda/debug
16670 If unsure, say Y (since it makes it easier to find the bugs).
16672 IrLAP Compression support
16673 CONFIG_IRDA_COMPRESSION
16674 Compression is _not_ part of the IrDA(tm) protocol specification,
16675 but it's working great! Linux is the first to try out compression
16676 support at the IrLAP layer. This means that you will only benefit
16677 from compression if you are running a Linux <-> Linux configuration.
16679 If you say Y here, you also need to say Y or M to a compression
16682 IrLAP Deflate Compression Protocol (EXPERIMENTAL)
16683 CONFIG_IRDA_DEFLATE
16684 Say Y here if you want to build support for the Deflate compression
16685 protocol. The deflate compression (GZIP) is exactly
16686 the same as the one used by the PPP protocol.
16688 If you want to compile this compression support as a module, say M
16689 here and read Documentation/modules.txt. The module will be called
16694 Say Y here if you want to build support for the IrLAN protocol. If
16695 you want to compile it as a module (irlan.o), say M here and read
16696 Documentation/modules.txt. IrLAN emulates an Ethernet and makes it
16697 possible to put up a wireless LAN using infrared beams.
16699 The IrLAN protocol can be used to talk with infrared access points
16700 like the HP NetbeamIR, or the ESI JetEye NET. You can also connect
16701 to another Linux machine running the IrLAN protocol for ad-hoc
16706 Say Y here if you want to build support for the IrCOMM protocol. If
16707 you want to compile it as a module (you will get ircomm.o and
16708 ircomm-tty.o), say M here and read Documentation/modules.txt. IrCOMM
16709 implements serial port emulation, and makes it possible to use all
16710 existing applications that understands TTY's with an infrared link.
16711 Thus you should be able to use application like PPP, minicom and
16712 others. Enabling this option will create two modules called ircomm
16715 IrTTY IrDA Device Driver
16717 Say Y here if you want to build support for the IrTTY line
16718 discipline. If you want to compile it as a module (irtty.o), say M
16719 here and read Documentation/modules.txt. IrTTY makes it possible to
16720 use Linux's own serial driver for all IrDA ports that are 16550
16721 compatible. Most IrDA chips are 16550 compatible so you should
16722 probably say Y to this option. Using IrTTY will however limit the
16723 speed of the connection to 115200 bps (IrDA SIR mode)
16727 IrPORT IrDA Device Driver
16729 Say Y here if you want to build support for the IrPORT IrDA device
16730 driver. If you want to compile it as a module (irport.o), say M here
16731 and read Documentation/modules.txt. IrPORT can be used instead of
16732 IrTTY and sometimes this can be better. One example is if your IrDA
16733 port does not have echo-canceling, which will work OK with IrPORT
16734 since this driver is working in half-duplex mode only. You don't
16735 need to use irattach with IrPORT, but you just insert it the same
16736 way as FIR drivers (insmod irport io=0x3e8 irq=11). Notice that
16737 IrPORT is a SIR device driver which means that speed is limited to
16742 Winbond W83977AF IrDA Device Driver
16744 Say Y here if you want to build IrDA support for the Winbond
16745 W83977AF super-io chipset. This driver should be used for the IrDA
16746 chipset in the Corel NetWinder. The driver supports SIR, MIR and FIR
16749 If you want to compile it as a module, say M here and read
16750 Documentation/modules.txt. The module will be called w83977af_ir.o.
16752 NSC PC87108 IrDA Device Driver
16754 Say Y here if you want to build support for the NSC PC87108 and
16755 PC87338 IrDA chipsets. This driver supports SIR,
16756 MIR and FIR (4Mbps) speeds.
16758 If you want to compile it as a module, say M here and read
16759 Documentation/modules.txt. The module will be called nsc-ircc.o.
16761 Toshiba Type-O IR Port Device Driver
16763 Say Y here if you want to build support for the Toshiba Type-O IR
16764 chipset. This chipset is used by the Toshiba Libretto 100CT, and
16765 many more laptops. If you want to compile it as a module, say M here
16766 and read Documentation/modules.txt. The module will be called
16769 SMC IrCC (Experimental)
16770 CONFIG_SMC_IRCC_FIR
16771 Say Y here if you want to build support for the SMC Infrared
16772 Communications Controller. It is used in the Fujitsu Lifebook 635t
16773 and Sony PCG-505TX. If you want to compile it as a module, say M
16774 here and read Documentation/modules.txt. The module will be called
16777 Serial dongle support
16779 Say Y here if you have an infrared device that connects to your
16780 computer's serial port. These devices are called dongles. Then say Y
16781 or M to the driver for your particular dongle below.
16783 Note that the answer to this question won't directly affect the
16784 kernel: saying N will just cause this configure script to skip all
16785 the questions about serial dongles.
16787 ESI JetEye PC Dongle
16789 Say Y here if you want to build support for the Extended Systems
16790 JetEye PC dongle. If you want to compile it as a module, say M here
16791 and read Documentation/modules.txt. The ESI dongle attaches to the
16792 normal 9-pin serial port connector, and can currently only be used
16793 by IrTTY. To activate support for ESI dongles you will have to
16794 start irattach like this: "irattach -d esi".
16796 ACTiSYS IR-220L and IR220L+ dongle
16797 CONFIG_ACTISYS_DONGLE
16798 Say Y here if you want to build support for the ACTiSYS
16799 IR-220L and IR220L+ dongles. If you want to compile it as a module,
16800 say M here and read Documentation/modules.txt. The ACTiSYS dongles
16801 attaches to the normal 9-pin serial port connector, and can
16802 currently only be used by IrTTY. To activate support for ACTiSYS
16803 dongles you will have to start irattach like this:
16804 "irattach -d actisys" or "irattach -d actisys+".
16806 Tekram IrMate 210B dongle
16807 CONFIG_TEKRAM_DONGLE
16808 Say Y here if you want to build support for the Tekram IrMate 210B
16809 dongle. If you want to compile it as a module, say M here
16810 and read Documentation/modules.txt. The Tekram dongle attaches to
16811 the normal 9-pin serial port connector, and can currently only be
16812 used by IrTTY. To activate support for Tekram dongles you will have
16813 to start irattach like this: "irattach -d tekram".
16815 Greenwich GIrBIL dongle
16816 CONFIG_GIRBIL_DONGLE
16817 Say Y here if you want to build support for the Greenwich GIrBIL
16818 dongle. If you want to compile it as a module, say M here and read
16819 Documentation/modules.txt. The Greenwich dongle attaches to the
16820 normal 9-pin serial port connector, and can currently only be used
16821 by IrTTY. To activate support for Greenwich dongles you will have to
16822 insert "irattach -d girbil" in the /etc/irda/drivers script.
16824 Parallax Litelink dongle
16825 CONFIG_LITELINK_DONGLE
16826 Say Y here if you want to build support for the Parallax Litelink
16827 dongle. If you want to compile it as a module, say M here and read
16828 Documentation/modules.txt. The Parallax dongle attaches to the
16829 normal 9-pin serial port connector, and can currently only be used
16830 by IrTTY. To activate support for Parallax dongles you will have to
16831 start irattach like this "irattach -d litelink".
16834 CONFIG_OLD_BELKIN_DONGLE
16835 Say Y here if you want to build support for the Adaptec Airport 1000
16836 and 2000 dongles. If you want to compile it as a module, say M here
16837 and read Documentation/modules.txt. The module will be called
16838 old_belkin.o. Some information is contained in the comments at the
16839 top of drivers/net/irda/old_belkin.c.
16841 VME (Motorola and BVM) support
16843 Say Y here if you want to build a kernel for a 680x0 based VME
16844 board. Boards currently supported include Motorola boards MVME162,
16845 MVME166, MVME167, MVME172, and MVME177. BVME4000 and BVME6000
16846 boards from BVM Ltd are also supported.
16848 MVME162, 166 and 167 support
16850 Say Y to include support for Motorola VME boards. This will build a
16851 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
16852 MVME177 boards. If you select this option you will have to select
16853 the appropriate drivers for SCSI, Ethernet and serial ports later
16856 BVME4000 and BVME6000 support
16858 Say Y to include support for VME boards from BVM Ltd. This will
16859 build a kernel which can run on BVME4000 and BVME6000 boards. If
16860 you select this option you will have to select the appropriate
16861 drivers for SCSI, Ethernet and serial ports later on.
16863 Use write-through caching for 68060 supervisor accesses
16864 CONFIG_060_WRITETHROUGH
16865 The 68060 generally uses copyback caching of recently accessed data.
16866 Copyback caching means that memory writes will be held in an on-chip
16867 cache and only written back to memory some time later. Saying Y
16868 here will force supervisor (kernel) accesses to use writethrough
16869 caching. Writethrough caching means that data is written to memory
16870 straight away, so that cache and memory data always agree.
16871 Writethrough caching is less efficient, but is needed for some
16872 drivers on 68060 based systems where the 68060 bus snooping signal
16873 is hardwired on. The 53c710 SCSI driver is known to suffer from
16876 NCR53C710 SCSI driver for MVME16x
16877 CONFIG_MVME16x_SCSI
16878 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
16879 SCSI controller chip. Almost everyone using one of these boards
16880 will want to say Y to this question.
16882 NCR53C710 SCSI driver for BVME6000
16883 CONFIG_BVME6000_SCSI
16884 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
16885 SCSI controller chip. Almost everyone using one of these boards
16886 will want to say Y to this question.
16888 MVME16x Ethernet support
16890 This is the driver for the Ethernet interface on the Motorola
16891 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
16892 driver for this chip in your kernel. If you want to compile it as
16893 a module, say M here and read Documentation/modules.txt.
16895 BVME6000 Ethernet support
16896 CONFIG_BVME6000_NET
16897 This is the driver for the Ethernet interface on BVME4000 and
16898 BVME6000 VME boards. Say Y here to include the driver for this chip
16899 in your kernel. If you want to compile it as a module, say M here
16900 and read Documentation/modules.txt.
16902 CD2401 support for MVME166/7 serial ports
16904 This is the driver for the serial ports on the Motorola MVME166,
16905 167, and 172 boards. Everyone using one of these boards should say
16908 SCC support for MVME162 serial ports
16910 This is the driver for the serial ports on the Motorola MVME162 and
16911 172 boards. Everyone using one of these boards should say Y here.
16913 SCC support for BVME6000 serial ports
16914 CONFIG_BVME6000_SCC
16915 This is the driver for the serial ports on the BVME4000 and BVME6000
16916 boards from BVM Ltd. Everyone using one of these boards should say
16919 7-Segment Display support
16921 This is the driver for the 7-segment display and LED present on
16922 Sun Microsystems CompactPCI models CP1400 and CP1500.
16924 This driver is also available as a module ( = code which can be
16925 inserted in and removed from the running kernel whenever you want).
16926 The module will be called display7seg.o. If you want to compile it
16927 as a module, say M here and read Documentation/modules.txt.
16929 If you do not have a CompactPCI model CP1400 or CP1500, or
16930 another UltraSPARC-IIi-cEngine boardset with a 7-segment display,
16931 you should say N to this option.
16934 CONFIG_IA64_GENERIC
16935 This selects the system type of your hardware. A "generic" kernel
16936 will run on any supported IA-64 system. However, if you configure
16937 a kernel for your specific system, it will be faster and smaller.
16939 To find out what type of IA-64 system you have, you may want to
16940 check the IA-64 Linux web site at http://www.linux-ia64.org/.
16941 As of the time of this writing, most hardware is DIG compliant,
16942 so the "DIG-compliant" option is usually the right choice.
16944 HP-simulator For the HP simulator (http://software.hp.com/ia64linux/).
16945 SN1-simulator For the SGI SN1 simulator.
16946 DIG-compliant For DIG ("Developer's Interface Guide") compliant system.
16948 If you don't know what to do, choose "generic".
16951 CONFIG_IA64_PAGE_SIZE_4KB
16953 This lets you select the page size of the kernel. For best IA-64
16954 performance, a page size of 8KB or 16KB is recommended. For best
16955 IA-32 compatibility, a page size of 4KB should be selected (the vast
16956 majority of IA-32 binaries work perfectly fine with a larger page
16957 size). For Itanium systems, do NOT chose a page size larger than
16960 4KB For best IA-32 compatibility
16961 8KB For best IA-64 performance
16962 16KB For best IA-64 performance
16963 64KB Not for Itanium.
16965 If you don't know what to do, choose 8KB.
16967 Enable Itanium A-step specific code
16968 CONFIG_ITANIUM_ASTEP_SPECIFIC
16969 Select this option to build a kernel for an Itanium prototype system
16970 with an A-step CPU. You have an A-step CPU if the "revision" field in
16971 /proc/cpuinfo is 0.
16973 Enable Itanium A1-step specific code
16974 CONFIG_ITANIUM_A1_SPECIFIC
16975 Select this option to build a kernel for an Itanium prototype system
16976 with an A1-step CPU. If you don't know whether you have an A1-step CPU,
16977 you probably don't and you can answer "no" here.
16979 Enable Itanium B-step specific code
16980 CONFIG_ITANIUM_BSTEP_SPECIFIC
16981 Select this option to build a kernel for an Itanium prototype system
16982 with a B-step CPU. You have a B-step CPU if the "revision" field in
16983 /proc/cpuinfo has a value in the range from 1 to 4.
16985 Enable Itanium B0-step specific code
16986 CONFIG_ITANIUM_B0_SPECIFIC
16987 Select this option to bild a kernel for an Itanium prototype system
16988 with a B0-step CPU. You have a B0-step CPU if the "revision" field in
16989 /proc/cpuinfo is 1.
16991 Force interrupt redirection
16992 CONFIG_IA64_HAVE_IRQREDIR
16993 Select this option if you know that your system has the ability to
16994 redirect interrupts to different CPUs. Select N here if you're
16997 Enable use of global TLB purge instruction (ptc.g)
16998 CONFIG_ITANIUM_PTCG
16999 Say Y here if you want the kernel to use the IA-64 "ptc.g"
17000 instruction to flush the TLB on all CPUs. Select N here if
17003 Enable SoftSDV hacks
17004 CONFIG_IA64_SOFTSDV_HACKS
17005 Say Y here to enable hacks to make the kernel work on the Intel
17006 SoftSDV simulator. Select N here if you're unsure.
17009 CONFIG_IA64_AZUSA_HACKS
17010 Say Y here to enable hacks to make the kernel work on the NEC
17011 AzusA platform. Select N here if you're unsure.
17013 Force socket buffers below 4GB?
17014 CONFIG_SKB_BELOW_4GB
17015 Most of today's network interface cards (NICs) support DMA to
17016 the low 32 bits of the address space only. On machines with
17017 more then 4GB of memory, this can cause the system to slow
17018 down if there is no I/O TLB hardware. Turning this option on
17019 avoids the slow-down by forcing socket buffers to be allocated
17020 from memory below 4GB. The downside is that your system could
17021 run out of memory below 4GB before all memory has been used up.
17022 If you're unsure how to answer this question, answer Y.
17024 Enable IA-64 Machine Check Abort
17026 Say Y here to enable machine check support for IA-64. If you're
17029 Performance monitor support
17031 Selects whether support for the IA-64 performance monitor hardware
17032 is included in the kernel. This makes some kernel data-structures a
17033 little bigger and slows down execution a bit, but it is still
17034 usually a good idea to turn this on. If you're unsure, say N.
17037 CONFIG_IA64_PALINFO
17038 If you say Y here, you are able to get PAL (Processor Abstraction
17039 Layer) information in /proc/pal. This contains useful information
17040 about the processors in your systems, such as cache and TLB sizes
17041 and the PAL firmware version in use.
17043 To use this option, you have to check that the "/proc file system
17044 support" (CONFIG_PROC_FS) is enabled, too.
17047 # A couple of things I keep forgetting:
17048 # capitalize: AppleTalk, Ethernet, DOS, DMA, FAT, FTP, Internet,
17049 # Intel, IRQ, ISDN, Linux, MSDOS, NetWare, NetWinder,
17050 # NFS, PCI, SCSI, SPARC
17051 # two words: file system, hard drive, hard disk, home page,
17052 # user space, web site
17053 # other: it's safe to save; daemon; use --, not - or ---;
17054 # use KB for 1024 bytes, not kB or K.
17057 # This is used by Emacs' spell checker ispell.el:
17059 # LocalWords: CONFIG coprocessor DX Pentium SX lilo loadlin HOWTO ftp metalab
17060 # LocalWords: unc edu docs emu README kB BLK DEV FD Thinkpad fd MFM RLL IDE gz
17061 # LocalWords: cdrom diskless netboot nfs xzvf ATAPI MB ide pavia rubini pl pd
17062 # LocalWords: HD CDROMs IDECD NEC MITSUMI filesystem XT XD PCI BIOS cezar ATEN
17063 # LocalWords: ISA EISA Microchannel VESA BIOSes IPC SYSVIPC ipc Ctrl dmesg hlt
17064 # LocalWords: BINFMT Linkable http ac uk jo html GCC SPARC AVANTI CABRIOLET EB
17065 # LocalWords: netscape gcc LD CC toplevel MODVERSIONS insmod rmmod modprobe IP
17066 # LocalWords: genksyms INET loopback gatewaying ethernet PPP ARP Arp MEMSIZE
17067 # LocalWords: howto multicasting MULTICAST MBONE firewalling ipfw ACCT resp ip
17068 # LocalWords: proc acct IPIP encapsulator decapsulator klogd PCTCP RARP EXT PS
17069 # LocalWords: telnetting subnetted NAGLE rlogin NOSR ttyS TGA techinfo mbone nl
17070 # LocalWords: Mb SKB IPX Novell dosemu Appletalk DDP ATALK vmalloc visar ehome
17071 # LocalWords: SD CHR scsi thingy SG CD LUNs LUN jukebox Adaptec BusLogic EATA
17072 # LocalWords: buslogic DMA DPT ATT eata dma PIO UltraStor fdomain umsdos ext
17073 # LocalWords: QLOGIC qlogic TMC seagate Trantor ultrastor FASST wd NETDEVICES
17074 # LocalWords: unix BBS linux CSLIP PLIP Kirch's LDP CSlip SL SCC IRQ csustan
17075 # LocalWords: Turbo Laplink plip NCSA port's ReQuest IRQs EQL SMC AMD PCnet NE
17076 # LocalWords: COM ELPLUS Com EtherLinkIII VLB Arcnet Cabletron DEPCA DE carlos
17077 # LocalWords: depca EtherWorks EWRK ewrk SEEQ EtherExpress EEXPRESS NI xxx dia
17078 # LocalWords: EtherExpress WaveLAN wavelan PCLAN HPLAN VG SK Ansel Xen de ZNET
17079 # LocalWords: PCMCIA cb stanford LAN TEC RealTek ATP atp DLINK NetTools VISWS
17080 # LocalWords: TR Sony CDU caddyless cdu Mitsumi MCD cd mcd XA MultiSession CDA
17081 # LocalWords: Matsushita Panasonic SBPCD Soundblaster Longshine sbpcd Aztech
17082 # LocalWords: Okano Wearnes AZTCD CDD SE aztcd sonycd Goldstar GSCD Philips fs
17083 # LocalWords: LMS OPTCD Sanyo SJCD minix faqs xiafs XIA msdos mtools Cichocki
17084 # LocalWords: std softlinks umssync NetworkFileSharing nfsd mountd CDs HPFS TI
17085 # LocalWords: hpfs SYSV SCO iBCS Wyse WordPerfect tsx mit unixes sysv NR irisa
17086 # LocalWords: SMB WfW Cyclades async mux Logitech busmouse MouseSystem aka AST
17087 # LocalWords: PSMOUSE Compaq trackballs Travelmate Inport ATIXL ATI busmice ld
17088 # LocalWords: gpm config QIC DYNCONF FTAPE Stor Ftape ftape pcsndrv manpage NT
17089 # LocalWords: readprofile diskdrives org com masq EtherTalk tcp netrom sunacm
17090 # LocalWords: misc AIC aic pio scc Portmaster eql GIS PhotoCDs MCDX Perell PG
17091 # LocalWords: mcdx gscd optcd sjcd ISP hdparm Workgroups Lan samba PARIDE PCD
17092 # LocalWords: filesystems smbfs ATA ppp PCTech RZ www powerquest txt CMD ESDI
17093 # LocalWords: chipset FB multicast MROUTE appletalk ifconfig IBMTR multiport
17094 # LocalWords: Multisession STALDRV EasyIO EC EasyConnection ISTALLION ONboard
17095 # LocalWords: Brumby pci TNC cis ohio faq usenet NETLINK dev hydra ca Tyne mem
17096 # LocalWords: carleton DECstation SUNFD JENSEN Noname XXXM SLiRP LILO's amifb
17097 # LocalWords: pppd Zilog ZS SRM bootloader ez mainmenu rarp ipfwadm paride pcd
17098 # LocalWords: RTNETLINK mknod xos MTU lwared Macs mac netatalk macs cs Wolff
17099 # LocalWords: dartmouth flowerpt MultiMaster FlashPoint tudelft etherexpress
17100 # LocalWords: ICL EtherTeam ETH IDESCSI TXC SmartRAID SmartCache httpd sjc dlp
17101 # LocalWords: thesphere TwoServers BOOTP DHCP ncpfs BPQETHER BPQ MG HIPPI cern
17102 # LocalWords: bsd comp SPARCstation le SunOS ie Gracilis PackeTwin PT pt LU FX
17103 # LocalWords: FX TEAC CR LCS mS ramdisk IDETAPE cmd fperllo encis tcfs unisa
17104 # LocalWords: Vertos Genoa Funai hsfs NCP NetWare tgz APM apm ioctls UltraLite
17105 # LocalWords: TravelMate CDT LCD backlight VC RPC Mips AXP barlow cdrecord pg
17106 # LocalWords: PMAX MILO Alphas Multia Tseng linuxelf endian mipsel mips drv HT
17107 # LocalWords: kerneld callouts AdvanSys advansys Admin WDT DataStor EP verden
17108 # LocalWords: wdt hdb hdc bugfix SiS vlb Acculogic CSA DTC dtc Holtek ht QDI
17109 # LocalWords: QD qd UMC umc ALI ali lena fnet fr azstarnet cdr fb MDA ps esdi
17110 # LocalWords: Avanti XL AlphaStations Jensen DECpc AXPpci UDB Cabriolet MCA RC
17111 # LocalWords: AlphaPC mca AOUT OUTput PPro sipx gwdg lo nwe FourPort Boca unm
17112 # LocalWords: Keepalive linefill RELCOM keepalive analogue CDR conf CDI INIT
17113 # LocalWords: OPTi isp irq noisp VFAT vfat NTFS losetup dmsdosfs dosfs ISDN MP
17114 # LocalWords: NOWAYOUT behaviour dialin isdn callback BTX Teles XXXX LVM lvm
17116 # LocalWords: ipppd syncppp RFC MPP VJ downloaded icn NICCY Creatix shmem ufr
17117 # LocalWords: ibp md ARCnet ether encap NDIS arcether ODI Amigas AmiTCP NetBSD
17118 # LocalWords: initrd tue util DES funet des OnNet BIOSP smc Travan Iomega CMS
17119 # LocalWords: FC DC dc PPA IOMEGA's ppa RNFS FMV Fujitsu ARPD arpd loran layes
17120 # LocalWords: FRAD indiana framerelay DLCI DCLIs Sangoma SDLA mrouted sync sec
17121 # LocalWords: Starmode Metricom MosquitoNet mosquitonet kbit nfsroot Digiboard
17122 # LocalWords: DIGI Xe Xeve digiboard UMISC touchscreens mtu ethernets HBAs MEX
17123 # LocalWords: Shifflett netcom js jshiffle WIC DECchip ELCP EtherPower dst RTC
17124 # LocalWords: rtc SMP lp Digi Intl RightSwitch DGRS dgrs AFFS Amiga UFS SDL AP
17125 # LocalWords: Solaris RISCom riscom syncPPP PCBIT pcbit sparc anu au artoo MFB
17126 # LocalWords: hitchcock Crynwr cnam pktdrvr NCSA's CyDROM CyCDROM FreeBSD NeXT
17127 # LocalWords: NeXTstep disklabel disklabels SMD FFS tm AmigaOS diskfiles Un IQ
17128 # LocalWords: Bernd informatik rwth aachen uae affs multihosting bytecode java
17129 # LocalWords: applets applet JDK ncsa cabi SNI Alphatronix readme LANs scarab
17130 # LocalWords: winsock RNIS caltech OSPF honour Honouring Mbit LocalTalk DEFRAG
17131 # LocalWords: localtalk download Packetwin Baycom baycom interwork ASCII JNT
17132 # LocalWords: Camtec proxying indyramp defragment defragmented UDP FAS FASXX
17133 # LocalWords: FastSCSI SIO FDC qlogicfas QLogic qlogicisp setbaycom ife ee LJ
17134 # LocalWords: ethz ch Travelmates ProAudioSpectrum ProAudio SoundMan SB SBPro
17135 # LocalWords: Thunderboard SM OPL FM ADLIB TSR Gravis MPU PSS ADI SW DSP codec
17136 # LocalWords: ADSP ESC ASIC daughtercard GUSMAX MSS NX AdLib Excell Ensoniq YM
17137 # LocalWords: SoundScape Spea MediaTriX AudioTriX WSS OTI ThunderBoard VoxWare
17138 # LocalWords: Soundscape SSCAPE TRIX MediaTrix PnP Maui dsp midixx EIA getty
17139 # LocalWords: mgetty sendfax gert greenie muc lowlevel Lasermate LanManager io
17140 # LocalWords: OOPSes trackball binghamton mobileip ncr IOMAPPED settags ns ser
17141 # LocalWords: setsync NEGO MPARITY autotuning prefetch PIIX cdwrite utils rc
17142 # LocalWords: PCWATCHDOG berkprod bitgate boldt ucsb jf kyoto jp euc Tetsuyasu
17143 # LocalWords: YAMADA tetsu cauchy nslab ntt nevod perm su doc kaf kheops wsc
17144 # LocalWords: traduc Bourgin dbourgin menuconfig kfill READMEs HOWTOs Virge WA
17145 # LocalWords: IDEDISK IDEFLOPPY EIDE firewalls QMAGIC ZMAGIC LocalWords opti
17146 # LocalWords: SVGATextMode vga svga Xkernel syr jmwobus comfaqs dhcp flakey GD
17147 # LocalWords: IPv IPng interoperability ipng ipv radio's tapr pkthome PLP nano
17148 # LocalWords: Ses Mhz sethdlc SOUNDMODEM WindowsSoundSystem smdiag pcf inka ES
17149 # LocalWords: smmixer ptt circ soundmodem MKISS FDDI DEFEA DEFPA DEFXX redhat
17150 # LocalWords: HyperNews khg mconv sed lina wuftpd MicroChannel netlink irc cum
17151 # LocalWords: raudio RealAudio PPROP NETBIOS GUI IBMMCA ELMC Racal Interlan fi
17152 # LocalWords: eth shapecfg src esp PCWD PREVSTAT bootparam sig bitwizard SBC
17153 # LocalWords: downloads AFSK TCM FP Karn KA FSK RUH LinkSys cron mouseman LLC
17154 # LocalWords: SyQuest SyQuest's CCITT MicroSolutions BPCD bpcd ESPSERIAL PROM
17155 # LocalWords: SUNESP openprom OPENPROMIO quango themall al TT MC MMU LC RMW AA
17156 # LocalWords: INSNS Ataris AutoConfig ZORRO OCS AMIFB Agnus Denise ECS CDTV GB
17157 # LocalWords: AGA Cybervision CYBER GSP TMS DMI Zorro ACSI ROMs SLM BioNet GVP
17158 # LocalWords: PAMsNet TekMagic Cyberstorm MkI CYBERSTORMII MkII BLZ onboard cx
17159 # LocalWords: Village Tronic ATARILANCE RieblCard PAMCard VME MFP sangoma LAPB
17160 # LocalWords: Rhotron BioData's Multiface AMIGAMOUSE COPCON Amiga's bitplanes
17161 # LocalWords: ATARIMOUSE MFPSER SCC's MegaSTE ESCC Atari's GVPIOEXT DMASOUND
17162 # LocalWords: fdutils cisco univercd rpcg htm iface lapb LAPBETHER tpqic qic
17163 # LocalWords: SYNTH xd en binfmt aout ipip terra ipx sd sr sg wic framebuffer
17164 # LocalWords: ibmmca lapbether mkiss dlci sdla fmv eepro eexpress ni hp ne es
17165 # LocalWords: ibmtr isofs ROMFS romfs pcxx cyclades istallion psaux msbusmouse
17166 # LocalWords: atixlmouse sbin softdog pcwd USS Lite ACI miroSOUND PCM miroPCM
17167 # LocalWords: microcontroller miro Voxware downloading teles acsi slm gvp ltpc
17168 # LocalWords: atari ariadne amigamouse atarimouse builtin IPDDP maths bradford
17169 # LocalWords: AppleTalk Farallon PhoneNet Zubkoff lnz SCCB HAPN WANs vesafb nt
17170 # LocalWords: wanrouter WANPIPE multiprotocol Mbps wanpipe EtherWORKS nodma SC
17171 # LocalWords: smp HiSax SiemensChipSet Siemens AVM Elsa ITK hisax PCC MICROR
17172 # LocalWords: Mircolink EURO DSS Spellcaster BRI sc spellcast Digiboards GPIO
17173 # LocalWords: SYMBIOS COMPAT SDMS rev ASUS Tekram HX VX API ibmmcascsi ASY asy
17174 # LocalWords: loader's PCnetPCI automounter AUTOFS amd autofs VT Gallant's Pnp
17175 # LocalWords: AEDSP aedsp enskip tik Sysctl sysctl PARPORT parport pnp IDs EPP
17176 # LocalWords: Autoprobe bart patrickr HDLS READBACK AB usr DAMA DS SparQ aten
17177 # LocalWords: Symbios PCscsi tmscsim RoamAbout GHz Hinds contrib mathematik ok
17178 # LocalWords: darmstadt okir DIGIEPCA International's Xem digiepca epca bootup
17179 # LocalWords: zorro CAPI AVMB capi avmb VP SYN syncookies EM em pc Ethertalk
17180 # LocalWords: Dayna DL Daynatalk LT PhoneNET ATB Daystar queueing CMDS SCBs ls
17181 # LocalWords: SCB STATS Thinnet ThunderLAN TLAN Netelligent NetFlex tlan james
17182 # LocalWords: caldera Preload Preloading slowdowns schoebel uni NBD nbd prog
17183 # LocalWords: stuttgart rdist TRANS hostnames mango jukeboxes ESS userland PD
17184 # LocalWords: hardlinked NAMETRANS env mtab fstab umount nologin runlevel gid
17185 # LocalWords: adm Nodename hostname uname Kernelname bootp nmi DI OV StegFS
17186 # LocalWords: KERNNAME kname ktype kernelname Kerneltype KERNTYPE Alt RX mdafb
17187 # LocalWords: dataless kerneltype SYSNAME Comtrol Rocketport palmtop fbset EGS
17188 # LocalWords: nvram SYSRQ SysRq PrintScreen sysrq NVRAMs NvRAM Shortwave RTTY
17189 # LocalWords: Sitor Amtor Pactor GTOR hayes TX TMOUT JFdocs BIGMEM DAC IRQ's
17190 # LocalWords: IDEPCI IDEDMA PDC pdc TRM trm raidtools luthien nuclecu BAGET VR
17191 # LocalWords: unam mx miguel koobera uic EMUL solaris pp ieee lpsg co DMAs TOS
17192 # LocalWords: BLDCONFIG preloading jumperless BOOTINIT modutils multipath GRE
17193 # LocalWords: misconfigured autoconfiguration IPGRE ICMP tracert ipautofw PIM
17194 # LocalWords: netis rlynch autofw ipportfw monmouth ipsubs portforwarding pimd
17195 # LocalWords: portfw PIMSM netweb usc pim pf EUI aggregatable PB decapsulate
17196 # LocalWords: ipddp Decapsulation DECAP bool HAMRADIO tcpdump af CDs tx FBCON
17197 # LocalWords: ethertap multisession PPC MMIO GDT GDTH ICP gdth hamradio bpp
17198 # LocalWords: lmh weejock AIMSlab RadioTrack RTRACK HZP OptoSCC TRX rx TRXECHO
17199 # LocalWords: DMASCC paccomm dmascc addr cfg oevsv oe kib picpar FDX baudrate
17200 # LocalWords: baudrates fdx HDX hdx PSK kanren frforum QoS SCHED CBQ SCH sched
17201 # LocalWords: sch cbq CSZ Shenker Zhang csz SFQ sfq TBF tbf PFIFO fifo PRIO RW
17202 # LocalWords: prio Micom xIO dwmw rimi OMIRR omirr omirrd unicode ntfs cmu NIC
17203 # LocalWords: Braam braam Schmidt's freiburg nls codepages codepage Romanian
17204 # LocalWords: Slovak Slovenian Sorbian Nordic iso Catalan Faeroese Galician SZ
17205 # LocalWords: Valencian Slovene Esperanto Estonian Latvian Byelorussian KOI mt
17206 # LocalWords: charset Inuit Greenlandic Sami Lappish koi Alexey Kuznetsov's sa
17207 # LocalWords: Specialix specialix DTR RTS RTSCTS cycladesZ Exabyte ftape's inr
17208 # LocalWords: Iomega's LBFM claus ZFTAPE VFS zftape zft William's lzrw DFLT kb
17209 # LocalWords: MTSETBLK MTIOCTOP qft setblk zftape's tar's afio's setdrvbuffer
17210 # LocalWords: Procfs Exabyte's THR FCD sysvinit init PSC pscwdt VMIDI Euro SAB
17211 # LocalWords: Mostek Fastlane PowerMac PReP PMAC PowerPC Macintoshes Starmax
17212 # LocalWords: PowerStack Starmaxes MCOMMON DEVICETREE ATY IMS IMSTT videodev
17213 # LocalWords: BT Hauppauge STB bttv Quickcam BW BWQCAM bw qcam Mediavision PMS
17214 # LocalWords: pms Avatar Freecom Imation Superdisk BPCK bpck COMM comm DSTR ru
17215 # LocalWords: dstr EPAT EPEZ epat EPIA epia FreeCom FRPW frpw KingByte KBIC HW
17216 # LocalWords: KingByte's kbic OnSpec ValuStore FASTROUTE fastroute FLOWCONTROL
17217 # LocalWords: struct APIC realtime OSs LynxOS CNC tmp cvf HFS hfs ADFS Risc os
17218 # LocalWords: adfs ncpmount namespace SUBDIR reexport NDS kcore FT SPX spx DAT
17219 # LocalWords: interserver BLKSZ NUMBUFFERS apmd Tadpole ANA roestock QuickCam
17220 # LocalWords: isapnptools Colour CQCAM colour Connectix QuickClip prive mentre
17221 # LocalWords: KMOD kmod conformant utexas kharker UnixWare Mwave cgi cl ts ibm
17222 # LocalWords: eXchange threepio oakland simtel pre ULTRAMCA EtherLink isa luik
17223 # LocalWords: EtherLink OpenBSD pts DEVPTS devpts ptmx ttyp glibc readback SA
17224 # LocalWords: mwave OLDCARD isdnloop linklevel loopctrl Eicon Diehl DIEHLDIVA
17225 # LocalWords: ASUSCOM AsusCom TELEINT semiactiv Sedlbauer Sportster TA MIC ITH
17226 # LocalWords: NETjet NetJet Niccy Neuhaus sparcs AOC AOCD AOCE Microlink SAA
17227 # LocalWords: teletext WinTV saa iproute tc Quadra Performa PowerBook tor AUN
17228 # LocalWords: setserial compsoc steve Econet econet AUNUDP psched TEQL TLE CLS
17229 # LocalWords: teql FW Ingres TwistedPair MTRR MTRRs mtrr cfs crypto TD ktti KT
17230 # LocalWords: PHd ICS ipchains adelaide rustcorp syslog Cumana steganography
17231 # LocalWords: AcornSCSI EcoSCSI EESOX EESOXSCSI Powertec POWERTECSCSI dec SF
17232 # LocalWords: RadioReveal gatekeeper aimslab aztech FMI sf fmi RTL rtl cesdis
17233 # LocalWords: Yellowfin gsfc nasa gov yellowfin pcnet Mylex LNE lne EtherH hs
17234 # LocalWords: EBSA chattr RiscOS Winmodem AGP Atomwide DUALSP pcsp robinson CT
17235 # LocalWords: SGALAXY Waverider DSPxxx TRXPRO AudioTrix OSWF MOT CFB DSY kbps
17236 # LocalWords: tuwien kkudielk LVD mega lun MAXTAGS Gbps arcnet Olicom SNA PAE
17237 # LocalWords: SysKonnect tms sna etherboot ufs NetBEUI MultiSound MSNDCLAS GX
17238 # LocalWords: MSNDINIT MSNDPERM MSNDPIN PNDSPINI PNDSPERM Ensoniq's RetinaZ SS
17239 # LocalWords: AudioPCI lspci SonicVibes sonicvibes SPARCs roadrunner CLgen UPA
17240 # LocalWords: swansea shtml Zoltrix zoltrix BINUTILS EGCS binutils VIDC DACs
17241 # LocalWords: CyberVision Cirrus PowerBooks Topcat SBUS CGsix TurboGX BWtwo SS
17242 # LocalWords: CGthree TCX unswapable vfb fbcon hicolor truecolor AFB ILBM SOC
17243 # LocalWords: IPLAN gracilis Fibre SBus SparcSTORAGE SV jnewbigin swin QNX qnx
17244 # LocalWords: PTY PTYS ptyxx ttyxx PTYs ssh sb Avance ALS pss pvv kerneli hd
17245 # LocalWords: synth WaveFront MSND NONPNP AudioExcelDSP STRAM APUS CHRP MBX Nx
17246 # LocalWords: PowerMac's BMAC radiotrack rtrack miropcm OFFBOARD HPT UDMA DVD
17247 # LocalWords: hpt fokus gmd Cyrix DXL SLC DLC NexGen MediaGX GXm IDT WinChip
17248 # LocalWords: MMX MII valkyrie mdacon vdolive VDOLive cuseeme CU hippi rrunner
17249 # LocalWords: SeeMe ipmasqadm juanjox ipmarkfw markfw TNCs Microdyne rhine lib
17250 # LocalWords: libc jsX gamepad gameport CHF FCS FPGaming MadCatz ASSASIN GrIP
17251 # LocalWords: Assasin gamepads GamePad PDPI gamecards gamecard WingMan BSP WCS
17252 # LocalWords: ThunderPad CyberMan SideWinder ThrustMaster DirectConnect NES XF
17253 # LocalWords: Millenium SNES PSX Multisystem Nintendo PlayStation Amstrad CPC
17254 # LocalWords: Sega TurboGraFX Steffen Schwenke Multiststem PDIF FIFOSIZE EPLUS
17255 # LocalWords: PowerUP RoadRunner tahallah dos functionkey setterm imladris Woz
17256 # LocalWords: PowerMacs Winbond Algorithmics ALGOR algor ECOFF IRIX SGI SGI's
17257 # LocalWords: gfx virtualized Xpmac mklinux XFree FBDev Woodhouse mvhi Seeq fp
17258 # LocalWords: SGISEEQ HIgh ADB ADBMOUSE crosscompiler CROSSCOMPILE FPE GDB gdb
17259 # LocalWords: JOYPORT rp spoofing DawiControl NOGENSUPP EEPROM HSSI Alessandro
17260 # LocalWords: singleprocessor tex MATHEMU FRIQ Maxell friq Alcor XLT AlphaBook
17261 # LocalWords: AlphaPCI DP LX Miata Mikasa Noritake RPX UX BX Takara EV PRIMO
17262 # LocalWords: TSC Matrox Productiva matroxfb matrox multihead ia linuxhq MFW
17263 # LocalWords: mfw AAA MCS Initio XXU initio imm AutoDetect IZIP CTR usec HDLC
17264 # LocalWords: COSA SRP muni cz kas cosa Alteon AceNIC acenic VTOC OSes GMT SAx
17265 # LocalWords: Inspiron localtime INTS Thinkpads Ralf Brown's Flightstick NNN
17266 # LocalWords: Xterminator Blackhawk NN mpu ioports DCA HPDCA HPLANCE DIO Corel
17267 # LocalWords: GemTek gemtek CMDLINE IrDA PDA's irmanager irattach RR AVA DN rg
17268 # LocalWords: uit dagb irda LSAP IrLMP RR's IrLAP IR alloc skb's kfree skb's
17269 # LocalWords: GZIP IrLAN NetbeamIR ESI JetEye IrOBEX IrCOMM TTY's minicom dti
17270 # LocalWords: ircomm ircomm pluto thiguchi IrTTY Linux's bps NetWinder MIR NSC
17271 # LocalWords: ACTiSYS Dongle dongle dongles esi actisys IrMate tekram BVM MVME
17272 # LocalWords: BVME BVME WRITETHROUGH copyback writethrough fwmark syncookie tu
17273 # LocalWords: alphalinux GOBIOS csn chemnitz nat ACARD AMI MegaRAID megaraid
17274 # LocalWords: QNXFS ISI isicom xterms Apollos VPN RCPCI rcpci sgi visws pcmcia
17275 # LocalWords: IrLPT UIRCC Tecra Strebel jstrebel suse Eichwalder ke INI INIA
17276 # LocalWords: FCP qlogicfc sym isapnp DTLK DoubleTalk rcsys dtlk DMAP SGIVW ar
17277 # LocalWords: dmabuf EcoRadio MUTEFREQ GIrBIL girbil tepkom vol mha diplom PQS
17278 # LocalWords: bmac Microgate SyncLink synclink hdlc excl ioaddr Tane tanep TCQ
17279 # LocalWords: PDS SMALLDOS charsets bigfoot kernelfr mcs cls fw rsvp SKnet sk
17280 # LocalWords: SKMC USB UHCI OHCI intel compaq usb ohci HCD Virt Compaq's hcd
17281 # LocalWords: VROOTHUB KBD ARRs MCRs NWBUTTON nwbutton NUM WaveArtist APNE cpu
17282 # LocalWords: apne blackhawke PlanB lu mlan planb NWFPE FPA nwfpe unbootable
17283 # LocalWords: FPEmulator ds vmlinux initialisation discardable pgtable PGT mdw
17284 # LocalWords: quicklist pagetable arthur StrongARM podule podules Autodetect
17285 # LocalWords: dodgy IrPORT irport Litelink litelink SuSE rtfm internet hda CY
17286 # LocalWords: multmode DriveReady SeekComplete DriveStatusError miscompile AEC
17287 # LocalWords: mainboard's Digital's alim FastTrak aec PIIXn piix Gayle Eyetech
17288 # LocalWords: Catweasel IDEDOUBLER Powerbook Centris ICSIDE RapIDE OSM HDM IOP
17289 # LocalWords: HDM's OSM's lan FibreChannel ECP autoprobe itg lbl ipmasq cjb IC
17290 # LocalWords: bieringer Caulfield's dreamtime decnet SIOCFIGCONF SIOCGIFCONF
17291 # LocalWords: rtnetlink Endnode Aironet Arlan Telxon ylenurme arlan ACB aeschi
17292 # LocalWords: Sealevel sealevel Cyclom br wanconfig tarball conectiva cycsyn
17293 # LocalWords: devel bazar cyclomx NetGear GA IBMOL Lanstreamer uhci eu efs CYZ
17294 # LocalWords: olympic linuxtr usbcore acm EZUSB downloader EFS XFS INTR op IIC
17295 # LocalWords: heine soundcore JavaStations JavaStation GemTeks TerraTec TODO
17296 # LocalWords: ActiveRadio Standalone terratec Rolf Offermanns rolf offermanns
17297 # LocalWords: Zoran ZR Buz LML CPQ DA cpqarray PPDEV deviceid vlp ppdev atyfb
17298 # LocalWords: AcceleRAID eXtremeRAID NETFILTER Netfilter masqueraded netfilter
17299 # LocalWords: kernelnotes Cardbus PCMCIA's CardBus clgenfb Permedia YAM MMAP
17300 # LocalWords: mmapped ATM atm PVCs SVCs InARP ATMARP neighbour neighbours MPOA
17301 # LocalWords: VCs ENI FPGA Tonga MMF MF UTP printks ZeitNet ZN ZATM uPD SAR PN
17302 # LocalWords: approx NICStAR NICs ForeRunnerLE Madge Collage ATMizer Dxxxx VCI
17303 # LocalWords: ServeRAID IPS ips ipslinux gzip BSDCOMP LZW RAYCS Interphase app
17304 # LocalWords: Tachyon IPHASE Surfboard NextLevel SURFboard jacksonville Tigon
17305 # LocalWords: fventuri adelphia siglercm linuxpower AceNICs Starfire starfire
17306 # LocalWords: ISOC CPiA cpia uss ACPI UDF DirectCD udf CDRW's OSF Manx acpi DM
17307 # LocalWords: Unixware cymru Computone IntelliPort Intelliport computone SI sx
17308 # LocalWords: adbmouse DRI DRM dlabs GMX PLCs Applicom fieldbus applicom int
17309 # LocalWords: VWSND eg ESSSOLO CFU CFNR scribed eiconctrl eicon hylafax KFPU
17310 # LocalWords: EXTRAPREC fpu mainboards KHTTPD kHTTPd khttpd Xcelerator SBNI tw
17311 # LocalWords: LOGIBUSMOUSE Granch granch sbni Raylink NOHIGHMEM Athlon SIM sim
17312 # LocalWords: hpl Tourrilhes DuraLAN starfile Davicom davicom dmfe auk tms tr
17313 # LocalWords: TokenExpress Belkin Peracom eTek DVDs infradead Cxxx Adlib AV ZX
17314 # LocalWords: NeoMagic CPi CPt Celeron decapsulation Undeletion BFS bfs nVidia
17315 # LocalWords: OnStream Irongate Riva phonedev QuickNet LineJack PhoneJack IXJ
17316 # LocalWords: Quicknet PhoneJACK LineJACK ixj pnpdump Quicknet's Joandi SSID
17317 # LocalWords: aironet quickconfig adhoc btw bap NONCS cardservices Xircom lin
17318 # LocalWords: Netwave AirSurfer netwave HomePNA failover MVP iMacs ALi aktual
17319 # LocalWords: Aladin HIDBP usbkbd KEYBDEV MOUSEDEV JOYDEV EVDEV UAB WhiteHEAT
17320 # LocalWords: Handspring ov DABUSB URB URB's dabusb CRAMFS NFSv ELV IOAPIC WIP
17321 # LocalWords: NLMv SMBus ALGOBIT algo PHILIPSPAR philips elv Velleman velleman
17322 # LocalWords: ALGOPCF Elektor elektor CHARDEV dfx TDFX tdfx Extensa dof gravis
17323 # LocalWords: assasin logitech Overdrive thrustmaster DWave Aureal magellan db
17324 # LocalWords: SpaceTec SpaceOrb SpaceBall spaceorb FLX spaceball turbografx zr
17325 # LocalWords: amiga ESS's WaveWatcher Maxi belkin RW's ata glx GART MPV Baget
17326 # LocalWords: OpenGL Xserver agpgart HOTPLUG CyberPro Integraphics Netwinder
17327 # LocalWords: aty FONTWIDTH eni zatm nicstar ForeRunner OC DECstations DEC's
17328 # LocalWords: PHYsical SUNI reinsertion ChipSAR KVC PHY ClassID iphase iadbg
17329 # LocalWords: DEVS FireWire PCILynx pcilynx LOCALRAM miro's DV RAWIO GRED Mk
17330 # LocalWords: Diffserv DSMARK Ingress Qdisc TCINDEX TMSPCI tmspci Ringode JE
17331 # LocalWords: MADGEMC madgemc TokenRing SMCTR TokenCard smctr Wacom Graphire
17332 # LocalWords: WMFORCE mousedev ConnectTech HandSpring Xirlink IBMCAM ibmcam SN
17333 # LocalWords: DEVICEFS yyy Cymraeg Dwave SIMM JSFLASH JavaStation's multilink
17334 # LocalWords: nsc ircc DDB Vrc CMN TB PROMs Vino rivafb DDC Matroxes MGA TVO
17335 # LocalWords: MAVEN fbdev crtc maven matroxset NTSC PCA SBA AAL SKFP DAS SAS
17336 # LocalWords: skfp Intuos ADMtek's pegasus PLUSB plusb pointopoint mp rio Xeon
17337 # LocalWords: DEVFS devfs dd bs EDSS german TELESPCI FRITZPCI HFC HFCS BDS HST
17338 # LocalWords: ISURF ISAR Saphir HSTSAPHIR Telekom BKM Scitel Quadro SCT Gazel
17339 # LocalWords: SP PRI Hypercope HYSDN Hypercope's hysdn IbssJoinNetTimeout FTDI
17340 # LocalWords: ARCNet Keyspan PDA ADMtek sgalaxy sgbase opl mpuio mpuirq sbio
17341 # LocalWords: sbirq sbdma gus uart mssio mssirq mssdma sscape maui mouirq iph
17342 # LocalWords: CHDLC UPS's usbmouse wacom wmforce keybdev joydev fibre Trunking
17343 # LocalWords: Etherchannel IOC Moxa Intellio moxa SmartIO mxser Mixcom EFI ir
17344 # LocalWords: MIXCOMWD mixcomwd SENDCOMPLETE GMAC iBook gmac OAKNET oaknet PCG
17345 # LocalWords: diffserv irlan irtty toshoboe IrCC Lifebook idex AUTODMA FIP Cxx
17346 # LocalWords: Yenta Databook TCIC FMVJ fmvj NMCLAN LiveWire nmclan XIRC xirc
17347 # LocalWords: loadkeys setfont shm SuperIO soc SOCAL socal FCAL fc fcal COMX
17348 # LocalWords: MultiGate ITConsult comx CMX HiCOMX downloadable hw LoCOMX PROTO
17349 # LocalWords: locomx MixCOM mixcom proto MyriCOM MYRI Sbus myri sbus IBMLS hme
17350 # LocalWords: lanstreamer baseT HAPPYMEAL qfe sunhme SUNLANCE sunlance BigMAC
17351 # LocalWords: SUNBMAC sunbmac QuadEthernet SUNQE qe FastEthernet sunqe DSB PTI
17352 # LocalWords: DSBR dsbr procinfo QLOGICPTI qpti ptisp QLGC qlogicpti se LBA NF
17353 # LocalWords: OPENPROMFS OpenPROM openpromfs OBP OpenBoot flashable Multiboard
17354 # LocalWords: SPARCAUDIO SparcClassic Ultras DBRI Sparcbook sparcaudio SUNBPP
17355 # LocalWords: UltraDMA WDC CRC CONNTRACK IPTABLES iptables nfmark interface's
17356 # LocalWords: tdfxfb TNTx HGA hgafb VERBOSEDEBUG SunTrunking SunSoft XIRTULIP
17357 # LocalWords: ethercards PNIC Macronix MXIC ASIX xircom Mustek MDC gphoto mdc
17358 # LocalWords: CramFs Cramfs uid cramfs AVM's kernelcapi PCIV cdrdao Cdparanoia
17359 # LocalWords: DMX Domex dmx wellington ftdi sio Accton Billington Corega FEter
17360 # LocalWords: MELCO LUA PNA Linksys SNC chkdsk AWACS Webcam RAMFS Ramfs ramfs
17361 # LocalWords: ramfiles MAKEDEV pty WDTPCI APA apa