1 # Maintained by Axel Boldt (boldt@math.ucsb.edu)
3 # This version of the Linux kernel configuration help texts
4 # corresponds to the kernel versions 2.3.x.
6 # Translations of this file available on the WWW:
8 # - Japanese, maintained by the JF Project (JF@linux.or.jp), at
9 # http://www.linux.or.jp/JF/JFdocs/Configure.help/
10 # - Russian, by kaf@linux.nevod.perm.su, at
11 # http://nevod.perm.su/service/linux/doc/kernel/Configure.help
12 # - French, by 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/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 Intel PIIXn chipsets support
873 This driver adds PIO mode setting and tuning for all PIIX IDE
874 controllers by Intel. Since the BIOS can sometimes improperly tune
875 PIO 0-4 mode settings, this allows dynamic tuning of the chipset
876 via the standard end-user tool 'hdparm'.
878 Please read the comments at the top of drivers/ide/piix.c.
880 If you say Y here, you should also say Y to "PIIXn Tuning support",
887 This driver extension adds DMA mode setting and tuning for all PIIX
888 IDE controllers by Intel. Since the BIOS can sometimes improperly
889 set up the device/adapter combination and speed limits, it has
890 become a necessity to back/forward speed devices as needed.
892 Case 430HX/440FX PIIX3 need speed limits to reduce UDMA to DMA mode
893 2 if the BIOS can not perform this task at initialization.
897 PROMISE PDC20246/PDC20262/PDC20267 support
898 CONFIG_BLK_DEV_PDC202XX
899 Promise Ultra33 or PDC20246
900 Promise Ultra66 or PDC20262
901 Promise Ultra100 or PDC20265/PDC20267
903 This driver adds up to 4 more EIDE devices sharing a single
904 interrupt. This add-on card is a bootable PCI UDMA controller. Since
905 multiple cards can be installed and there are BIOS ROM problems that
906 happen if the BIOS revisions of all installed cards (three-max) do
907 not match, the driver attempts to do dynamic tuning of the chipset
908 at boot-time for max-speed. Ultra33 BIOS 1.25 or newer is required
909 for more than one card. This card may require that you say Y to
910 "Special UDMA Feature (EXPERIMENTAL)".
912 If you say Y here, you need to say Y to "Use DMA by default when
915 Please read the comments at the top of drivers/ide/pdc202xx.c
919 Special UDMA Feature (EXPERIMENTAL)
920 CONFIG_PDC202XX_BURST
921 For PDC20246, PDC20262, PDC20265 and PDC20267 Ultra DMA chipsets.
922 Designed originally for PDC20246/Ultra33 that has BIOS setup
923 failures when using 3 or more cards.
925 Unknown for PDC20265/PDC20267 Ultra DMA 100.
927 Please read the comments at the top of drivers/ide/pdc202xx.c
931 SiS5513 chipset support
932 CONFIG_BLK_DEV_SIS5513
933 This driver ensures (U)DMA support for SIS5513 chipset based
934 mainboards. SiS620/530 UDMA mode 4, SiS5600/5597 UDMA mode 2, all
935 other DMA mode 2 limited chipsets are unsupported to date.
937 If you say Y here, you need to say Y to "Use DMA by default when
940 Please read the comments at the top of drivers/ide/sis5513.c
942 Winbond SL82c105 support
943 CONFIG_BLK_DEV_SL82C105
944 If you have a Winbond SL82c105 IDE controller, say Y here to enable
945 special configuration for this chip. This is common on various CHRP
946 motherboards, but could be used elsewhere. If in doubt, say Y.
948 Tekram TRM290 chipset support (EXPERIMENTAL)
949 CONFIG_BLK_DEV_TRM290
950 This driver adds support for bus master DMA transfers
951 using the Tekram TRM290 PCI IDE chip. Volunteers are
952 needed for further tweaking and development.
953 Please read the comments at the top of drivers/ide/trm290.c.
955 VIA82CXXX chipset support
956 CONFIG_BLK_DEV_VIA82CXXX
957 This allows you to to configure your chipset for a better use while
958 running (U)DMA: it will allow you to enable efficiently the second
959 channel dma usage, as it may not be set by BIOS. It allows you to
960 pass a kernel command line at boot time in order to set fifo
961 config. If no command line is provided, it will try to set fifo
962 configuration at its best. It will allow you to get information from
963 /proc/ide/via provided you enabled "proc" support.
965 Please read the comments at the top of drivers/ide/via82cxxx.c
967 If you say Y here, then say Y to "Use DMA by default when available"
972 VIA82CXXX Tuning support (WIP)
973 CONFIG_VIA82CXXX_TUNING
974 Please read the comments at the top of drivers/ide/via82cxxx.c
978 Other IDE chipset support
980 Say Y here if you want to include enhanced support for various IDE
981 interface chipsets used on motherboards and add-on cards. You can
982 then pick your particular IDE chip from among the following options.
983 This enhanced support may be necessary for Linux to be able to
984 access the 3rd/4th drives in some systems. It may also enable
985 setting of higher speed I/O rates to improve system performance with
986 these chipsets. Most of these also require special kernel boot
987 parameters to actually turn on the support at runtime; you can find
988 a list of these in the file Documentation/ide.txt.
990 People with SCSI-only systems can say N here.
992 Generic 4 drives/port support
993 CONFIG_BLK_DEV_4DRIVES
994 Certain older chipsets, including the Tekram 690CD, use a single set
995 of I/O ports at 0x1f0 to control up to four drives, instead of the
996 customary two drives per port. Support for this can be enabled at
997 runtime using the "ide0=four" kernel boot parameter if you say Y
1001 CONFIG_BLK_DEV_ALI14XX
1002 This driver is enabled at runtime using the "ide0=ali14xx" kernel
1003 boot parameter. It enables support for the secondary IDE interface
1004 of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
1005 I/O speeds to be set as well. See the files Documentation/ide.txt
1006 and drivers/ide/ali14xx.c for more info.
1009 CONFIG_BLK_DEV_DTC2278
1010 This driver is enabled at runtime using the "ide0=dtc2278" kernel
1011 boot parameter. It enables support for the secondary IDE interface
1012 of the DTC-2278 card, and permits faster I/O speeds to be set as
1013 well. See the Documentation/ide.txt and drivers/ide/dtc2278.c
1014 files for more info.
1016 Holtek HT6560B support
1017 CONFIG_BLK_DEV_HT6560B
1018 This driver is enabled at runtime using the "ide0=ht6560b" kernel
1019 boot parameter. It enables support for the secondary IDE interface
1020 of the Holtek card, and permits faster I/O speeds to be set as well.
1021 See the Documentation/ide.txt and drivers/ide/ht6560b.c files for
1024 PROMISE DC4030 support (EXPERIMENTAL)
1025 CONFIG_BLK_DEV_PDC4030
1026 This driver provides support for the secondary IDE interface and
1027 cache of Promise IDE chipsets, e.g. DC4030 and DC5030. This driver
1028 is known to incur timeouts/retries during heavy I/O to drives
1029 attached to the secondary interface. CDROM and TAPE devices are not
1030 supported yet. This driver is enabled at runtime using the
1031 "ide0=dc4030" kernel boot parameter. See the Documentation/ide.txt
1032 and drivers/ide/pdc4030.c files for more info.
1035 CONFIG_BLK_DEV_QD6580
1036 This driver is enabled at runtime using the "ide0=qd6580" kernel
1037 boot parameter. It permits faster I/O speeds to be set. See the
1038 files Documentation/ide.txt and drivers/ide/qd6580.c for more
1042 CONFIG_BLK_DEV_UMC8672
1043 This driver is enabled at runtime using the "ide0=umc8672" kernel
1044 boot parameter. It enables support for the secondary IDE interface
1045 of the UMC-8672, and permits faster I/O speeds to be set as well.
1046 See the files Documentation/ide.txt and drivers/ide/umc8672.c for
1049 Amiga builtin Gayle IDE interface support
1050 CONFIG_BLK_DEV_GAYLE
1051 This is the IDE driver for the builtin IDE interface on some Amiga
1052 models. It supports both the `A1200 style' (used in A600 and A1200)
1053 and `A4000 style' (used in A4000 and A4000T) of the Gayle IDE
1054 interface. Say Y if you have such an Amiga model and want to use IDE
1055 devices (hard disks, CD-ROM drives, etc.) that are connected to the
1056 builtin IDE interface.
1058 Falcon IDE interface support
1059 CONFIG_BLK_DEV_FALCON_IDE
1060 This is the IDE driver for the builtin IDE interface on the Atari
1061 Falcon. Say Y if you have a Falcon and want to use IDE devices (hard
1062 disks, CD-ROM drives, etc.) that are connected to the builtin IDE
1065 Amiga Buddha/Catweasel IDE interface support (EXPERIMENTAL)
1066 CONFIG_BLK_DEV_BUDDHA
1067 This is the IDE driver for the IDE interfaces on the Buddha and
1068 Catweasel expansion boards. It supports up to two interfaces on the
1069 Buddha and three on the Catweasel.
1071 Say Y if you have a Buddha or Catweasel expansion board and want to
1072 use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
1073 to one of its IDE interfaces.
1075 Amiga IDE Doubler support (EXPERIMENTAL)
1076 CONFIG_BLK_DEV_IDEDOUBLER
1077 This driver provides support for the so-called `IDE doublers' (made
1078 by various manufacturers, e.g. Eyetech) that can be connected to the
1079 builtin IDE interface of some Amiga models. Using such an IDE
1080 doubler, you can connect up to four instead of two IDE devices on
1081 the Amiga's builtin IDE interface.
1083 Note that the normal Amiga Gayle IDE driver may not work correctly
1084 if you have an IDE doubler and don't enable this driver!
1086 Say Y if you have an IDE doubler. The driver is enabled at kernel
1087 runtime using the "ide=doubler" kernel boot parameter.
1089 Support for PowerMac IDE devices (must also enable IDE)
1090 CONFIG_BLK_DEV_IDE_PMAC
1091 No help for CONFIG_BLK_DEV_IDE_PMAC
1093 PowerMac IDE DMA support
1094 CONFIG_BLK_DEV_IDEDMA_PMAC
1095 No help for CONFIG_BLK_DEV_IDEDMA_PMAC
1098 CONFIG_IDEDMA_PMAC_AUTO
1099 Prior to kernel version 2.1.112, Linux used to automatically use
1100 DMA for IDE drives and chipsets which support it. Due to concerns
1101 about a couple of cases where buggy hardware may have caused damage,
1102 the default is now to NOT use DMA automatically. To revert to the
1103 previous behaviour, say Y to this question.
1105 If you suspect your hardware is at all flakey, say N here.
1106 Do NOT email the IDE kernel people regarding this issue!
1108 Macintosh Quadra/Powerbook IDE interface support
1109 CONFIG_BLK_DEV_MAC_IDE
1110 This is the IDE driver for the builtin IDE interface on some m68k
1111 Macintosh models. It supports both the `Quadra style' (used in
1112 Quadra/ Centris 630 and Performa 588 models) and `Powerbook style'
1113 (used in the Powerbook 150 and 190 models) IDE interface.
1115 Say Y if you have such an Macintosh model and want to use IDE
1116 devices (hard disks, CD-ROM drives, etc.) that are connected to the
1117 builtin IDE interface.
1119 ICS IDE interface support
1120 CONFIG_BLK_DEV_IDE_ICSIDE
1121 On Acorn systems, say Y here if you wish to use the ICS IDE
1122 interface card. This is not required for ICS partition support.
1123 If you are unsure, say N to this.
1126 CONFIG_BLK_DEV_IDEDMA_ICS
1127 Say Y here if you want to add DMA (Direct Memory Access) support to
1130 Use ICS DMA by default
1131 CONFIG_IDEDMA_ICS_AUTO
1132 Prior to kernel version 2.1.112, Linux used to automatically use
1133 DMA for IDE drives and chipsets which support it. Due to concerns
1134 about a couple of cases where buggy hardware may have caused damage,
1135 the default is now to NOT use DMA automatically. To revert to the
1136 previous behaviour, say Y to this question.
1138 If you suspect your hardware is at all flakey, say N here.
1139 Do NOT email the IDE kernel people regarding this issue!
1141 XT hard disk support
1143 Very old 8 bit hard disk controllers used in the IBM XT computer
1144 will be supported if you say Y here.
1146 If you want to compile the driver as a module ( = code which can be
1147 inserted in and removed from the running kernel whenever you want),
1148 say M here and read Documentation/modules.txt. The module will be
1151 It's pretty unlikely that you have one of these: say N.
1153 PS/2 ESDI hard disk support
1155 Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
1158 If you want to compile the driver as a module ( = code which can be
1159 inserted in and removed from the running kernel whenever you want),
1160 say M here and read Documentation/modules.txt. The module will be
1163 Mylex DAC960/DAC1100 PCI RAID Controller support
1164 CONFIG_BLK_DEV_DAC960
1165 This driver adds support for the Mylex DAC960, AcceleRAID, and
1166 eXtremeRAID PCI RAID controllers. See the file
1167 Documentation/README.DAC960 for further information about this
1170 If you want to compile the driver as a module ( = code which can be
1171 inserted in and removed from the running kernel whenever you want),
1172 say M here and read Documentation/modules.txt. The module will be
1175 Parallel port IDE device support
1177 There are many external CD-ROM and disk devices that connect through
1178 your computer's parallel port. Most of them are actually IDE devices
1179 using a parallel port IDE adapter. This option enables the PARIDE
1180 subsystem which contains drivers for many of these external drives.
1181 Read Documentation/paride.txt for more information.
1183 If you have said Y to the "Parallel-port support" configuration
1184 option, you may share a single port between your printer and other
1185 parallel port devices. Answer Y to build PARIDE support into your
1186 kernel, or M if you would like to build it as a loadable module. If
1187 your parallel port support is in a loadable module, you must build
1188 PARIDE as a module. If you built PARIDE support into your kernel,
1189 you may still build the individual protocol modules and high-level
1190 drivers as loadable modules. If you build this support as a module,
1191 it will be called paride.o.
1193 To use the PARIDE support, you must say Y or M here and also to at
1194 least one high-level driver (e.g. "Parallel port IDE disks",
1195 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
1196 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
1197 "MicroSolutions backpack protocol", "DataStor Commuter protocol"
1200 Parallel port IDE disks
1202 This option enables the high-level driver for IDE-type disk devices
1203 connected through a parallel port. If you chose to build PARIDE
1204 support into your kernel, you may answer Y here to build in the
1205 parallel port IDE driver, otherwise you should answer M to build
1206 it as a loadable module. The module will be called pd.o. You
1207 must also have at least one parallel port protocol driver in your
1208 system. Among the devices supported by this driver are the SyQuest
1209 EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack
1210 hard drives from MicroSolutions.
1212 Parallel port ATAPI CD-ROMs
1214 This option enables the high-level driver for ATAPI CD-ROM devices
1215 connected through a parallel port. If you chose to build PARIDE
1216 support into your kernel, you may answer Y here to build in the
1217 parallel port ATAPI CD-ROM driver, otherwise you should answer M to
1218 build it as a loadable module. The module will be called pcd.o. You
1219 must also have at least one parallel port protocol driver in your
1220 system. Among the devices supported by this driver are the
1221 MicroSolutions backpack CD-ROM drives and the Freecom Power CD. If
1222 you have such a CD-ROM drive, you should also say Y or M to "ISO
1223 9660 CDROM file system support" below, because that's the file
1224 system used on CDROMs.
1226 Parallel port ATAPI disks
1228 This option enables the high-level driver for ATAPI disk devices
1229 connected through a parallel port. If you chose to build PARIDE
1230 support into your kernel, you may answer Y here to build in the
1231 parallel port ATAPI disk driver, otherwise you should answer M
1232 to build it as a loadable module. The module will be called pf.o.
1233 You must also have at least one parallel port protocol driver in
1234 your system. Among the devices supported by this driver are the
1235 MicroSolutions backpack PD/CD drive and the Imation Superdisk
1238 Parallel port ATAPI tapes
1240 This option enables the high-level driver for ATAPI tape devices
1241 connected through a parallel port. If you chose to build PARIDE
1242 support into your kernel, you may answer Y here to build in the
1243 parallel port ATAPI disk driver, otherwise you should answer M
1244 to build it as a loadable module. The module will be called pt.o.
1245 You must also have at least one parallel port protocol driver in
1246 your system. Among the devices supported by this driver is the
1247 parallel port version of the HP 5GB drive.
1249 Parallel port generic ATAPI devices
1251 This option enables a special high-level driver for generic ATAPI
1252 devices connected through a parallel port. The driver allows user
1253 programs, such as cdrecord, to send ATAPI commands directly to a
1256 If you chose to build PARIDE support into your kernel, you may
1257 answer Y here to build in the parallel port generic ATAPI driver,
1258 otherwise you should answer M to build it as a loadable module. The
1259 module will be called pg.o.
1261 You must also have at least one parallel port protocol driver in
1264 This driver implements an API loosely related to the generic SCSI
1265 driver. See include/linux/pg.h for details.
1267 You can obtain the most recent version of cdrecord from
1268 ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/ . Versions 1.6.1a3 and
1269 later fully support this driver.
1271 ATEN EH-100 protocol
1273 This option enables support for the ATEN EH-100 parallel port IDE
1274 protocol. This protocol is used in some inexpensive low performance
1275 parallel port kits made in Hong Kong. If you chose to build PARIDE
1276 support into your kernel, you may answer Y here to build in the
1277 protocol driver, otherwise you should answer M to build it as a
1278 loadable module. The module will be called aten.o. You must also
1279 have a high-level driver for the type of device that you want to
1282 MicroSolutions backpack protocol
1284 This option enables support for the MicroSolutions backpack parallel
1285 port IDE protocol. If you chose to build PARIDE support into your
1286 kernel, you may answer Y here to build in the protocol driver,
1287 otherwise you should answer M to build it as a loadable module. The
1288 module will be called bpck.o. You must also have a high-level driver
1289 for the type of device that you want to support.
1291 DataStor Commuter protocol
1293 This option enables support for the Commuter parallel port IDE
1294 protocol from DataStor. If you chose to build PARIDE support
1295 into your kernel, you may answer Y here to build in the protocol
1296 driver, otherwise you should answer M to build it as a loadable
1297 module. The module will be called comm.o. You must also have
1298 a high-level driver for the type of device that you want to support.
1300 DataStor EP-2000 protocol
1302 This option enables support for the EP-2000 parallel port IDE
1303 protocol from DataStor. If you chose to build PARIDE support
1304 into your kernel, you may answer Y here to build in the protocol
1305 driver, otherwise you should answer M to build it as a loadable
1306 module. The module will be called dstr.o. You must also have
1307 a high-level driver for the type of device that you want to support.
1309 Shuttle EPAT/EPEZ protocol
1311 This option enables support for the EPAT parallel port IDE protocol.
1312 EPAT is a parallel port IDE adapter manufactured by Shuttle
1313 Technology and widely used in devices from major vendors such as
1314 Hewlett-Packard, SyQuest, Imation and Avatar. If you chose to build
1315 PARIDE support into your kernel, you may answer Y here to build in
1316 the protocol driver, otherwise you should answer M to build it as a
1317 loadable module. The module will be called epat.o. You must also
1318 have a high-level driver for the type of device that you want to
1321 Shuttle EPIA protocol
1323 This option enables support for the (obsolete) EPIA parallel port
1324 IDE protocol from Shuttle Technology. This adapter can still be
1325 found in some no-name kits. If you chose to build PARIDE support
1326 into your kernel, you may answer Y here to build in the protocol
1327 driver, otherwise you should answer M to build it as a loadable
1328 module. The module will be called epia.o. You must also have a
1329 high-level driver for the type of device that you want to support.
1331 FIT TD-2000 protocol
1333 This option enables support for the TD-2000 parallel port IDE
1334 protocol from Fidelity International Technology. This is a simple
1335 (low speed) adapter that is used in some portable hard drives. If
1336 you chose to build PARIDE support into your kernel, you may answer Y
1337 here to build in the protocol driver, otherwise you should answer M
1338 to build it as a loadable module. The module will be called ktti.o.
1339 You must also have a high-level driver for the type of device that
1340 you want to support.
1342 FIT TD-3000 protocol
1344 This option enables support for the TD-3000 parallel port IDE
1345 protocol from Fidelity International Technology. This protocol is
1346 used in newer models of their portable disk, CD-ROM and PD/CD
1347 devices. If you chose to build PARIDE support into your kernel, you
1348 may answer Y here to build in the protocol driver, otherwise you
1349 should answer M to build it as a loadable module. The module will be
1350 called fit3.o. You must also have a high-level driver for the type
1351 of device that you want to support.
1353 Freecom IQ ASIC-2 protocol
1355 This option enables support for version 2 of the Freecom IQ parallel
1356 port IDE adapter. This adapter is used by the Maxell Superdisk
1357 drive. If you chose to build PARIDE support into your kernel, you
1358 may answer Y here to build in the protocol driver, otherwise you
1359 should answer M to build it as a loadable module. The module will be
1360 called friq.o. You must also have a high-level driver for the type
1361 of device that you want to support.
1363 FreeCom power protocol
1365 This option enables support for the Freecom power parallel port IDE
1366 protocol. If you chose to build PARIDE support into your kernel, you
1367 may answer Y here to build in the protocol driver, otherwise you
1368 should answer M to build it as a loadable module. The module will be
1369 called frpw.o. You must also have a high-level driver for the type
1370 of device that you want to support.
1372 KingByte KBIC-951A/971A protocols
1374 This option enables support for the KBIC-951A and KBIC-971A parallel
1375 port IDE protocols from KingByte Information Corp. KingByte's
1376 adapters appear in many no-name portable disk and CD-ROM products,
1377 especially in Europe. If you chose to build PARIDE support into your
1378 kernel, you may answer Y here to build in the protocol driver,
1379 otherwise you should answer M to build it as a loadable module. The
1380 module will be called kbic.o. You must also have a high-level driver
1381 for the type of device that you want to support.
1385 This option enables support for the "PHd" parallel port IDE protocol
1386 from KT Technology. This is a simple (low speed) adapter that is
1387 used in some 2.5" portable hard drives. If you chose to build PARIDE
1388 support into your kernel, you may answer Y here to build in the
1389 protocol driver, otherwise you should answer M to build it as a
1390 loadable module. The module will be called ktti.o. You must also
1391 have a high-level driver for the type of device that you want to
1394 OnSpec 90c20 protocol
1396 This option enables support for the (obsolete) 90c20 parallel port
1397 IDE protocol from OnSpec (often marketed under the ValuStore brand
1398 name). If you chose to build PARIDE support into your kernel, you
1399 may answer Y here to build in the protocol driver, otherwise you
1400 should answer M to build it as a loadable module. The module will
1401 be called on20.o. You must also have a high-level driver for the
1402 type of device that you want to support.
1404 OnSpec 90c26 protocol
1406 This option enables support for the 90c26 parallel port IDE protocol
1407 from OnSpec Electronics (often marketed under the ValuStore brand
1408 name). If you chose to build PARIDE support into your kernel, you
1409 may answer Y here to build in the protocol driver, otherwise you
1410 should answer M to build it as a loadable module. The module will be
1411 called on26.o. You must also have a high-level driver for the type
1412 of device that you want to support.
1414 Logical Volume Manager (LVM) support
1416 This driver lets you combine several hard disks, hard disk
1417 partitions, multiple devices or even loop devices (for evaluation
1418 purposes) into a volume group. Imagine a volume group as a kind of
1419 virtual disk. Logical volumes, which can be thought of as virtual
1420 partitions, can be created in the volume group. You can resize
1421 volume groups and logical volumes after creation time, corresponding
1422 to new capacity needs. Logical volumes are accessed as block
1423 devices named /dev/VolumeGroupName/LogicalVolumeName.
1425 For details see Documentation/LVM-HOWTO. You will need supporting
1426 user space software; location is in Documentation/Changes.
1428 If you want to compile this support as a module ( = code which can
1429 be inserted in and removed from the running kernel whenever you
1430 want), say M here and read Documentation/modules.txt. The module
1431 will be called lvm-mod.o.
1433 Logical Volume Manager /proc file system information
1435 If you say Y here, you are able to access overall Logical Volume
1436 Manager, Volume Group, Logical and Physical Volume information in
1439 To use this option, you have to check, that the "/proc file system
1440 support" (CONFIG_PROC_FS) is enabled too.
1442 Multiple devices driver support
1444 This driver lets you combine several hard disk partitions into one
1445 logical block device. This can be used to simply append one
1446 partition to another one or to combine several redundant hard disks
1447 into a RAID1/4/5 device so as to provide protection against hard
1448 disk failures. This is called "Software RAID" since the combining of
1449 the partitions is done by the kernel. "Hardware RAID" means that the
1450 combining is done by a dedicated controller; if you have such a
1451 controller, you do not need to say Y here.
1453 More information about Software RAID on Linux is contained in the
1454 Software-RAID mini-HOWTO, available from
1455 http://www.linuxdoc.org/docs.html#howto . There you will also
1456 learn where to get the supporting user space utilities raidtools.
1460 Linear (append) mode
1462 If you say Y here, then your multiple devices driver will be able to
1463 use the so-called linear mode, i.e. it will combine the hard disk
1464 partitions by simply appending one to the other.
1466 If you want to compile this as a module ( = code which can be
1467 inserted in and removed from the running kernel whenever you want),
1468 say M here and read Documentation/modules.txt. The module will be
1473 RAID-0 (striping) mode
1475 If you say Y here, then your multiple devices driver will be able to
1476 use the so-called raid0 mode, i.e. it will combine the hard disk
1477 partitions into one logical device in such a fashion as to fill them
1478 up evenly, one chunk here and one chunk there. This will increase
1479 the throughput rate if the partitions reside on distinct disks.
1481 Information about Software RAID on Linux is contained in the
1482 Software-RAID mini-HOWTO, available from
1483 http://www.linuxdoc.org/docs.html#howto . There you will also
1484 learn where to get the supporting user space utilities raidtools.
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-1/RAID-5 code (DANGEROUS)
1494 CONFIG_RAID15_DANGEROUS
1495 This new RAID1/RAID5 code has been freshly merged, and has not seen
1496 enough testing yet. While there are no known bugs in it, it might
1497 destroy your filesystems, eat your data and start World War III.
1498 You have been warned.
1502 RAID-1 (mirroring) mode
1504 A RAID-1 set consists of several disk drives which are exact copies
1505 of each other. In the event of a mirror failure, the RAID driver
1506 will continue to use the operational mirrors in the set, providing
1507 an error free MD (multiple device) to the higher levels of the
1508 kernel. In a set with N drives, the available space is the capacity
1509 of a single drive, and the set protects against a failure of (N - 1)
1512 Information about Software RAID on Linux is contained in the
1513 Software-RAID mini-HOWTO, available from
1514 http://www.linuxdoc.org/docs.html#howto . There you will also
1515 learn where to get the supporting user space utilities raidtools.
1517 If you want to use such a RAID-1 set, say Y. This code is also
1518 available as a module called raid1.o ( = code which can be inserted
1519 in and removed from the running kernel whenever you want). If you
1520 want to compile it as a module, say M here and read
1521 Documentation/modules.txt.
1527 A RAID-5 set of N drives with a capacity of C MB per drive provides
1528 the capacity of C * (N - 1) MB, and protects against a failure
1529 of a single drive. For a given sector (row) number, (N - 1) drives
1530 contain data sectors, and one drive contains the parity protection.
1531 For a RAID-4 set, the parity blocks are present on a single drive,
1532 while a RAID-5 set distributes the parity across the drives in one
1533 of the available parity distribution methods.
1535 Information about Software RAID on Linux is contained in the
1536 Software-RAID mini-HOWTO, available from
1537 http://www.linuxdoc.org/docs.html#howto . There you will also
1538 learn where to get the supporting user space utilities raidtools.
1540 If you want to use such a RAID-4/RAID-5 set, say Y. This code is
1541 also available as a module called raid5.o ( = code which can be
1542 inserted in and removed from the running kernel whenever you want).
1543 If you want to compile it as a module, say M here and read
1544 Documentation/modules.txt.
1550 To boot with an initial raid volume (any type) you can select
1551 autodetect, or answer Y here and appropriate options to the kernel
1553 For lilo and loadlin options see the file Documentation/md.txt.
1555 RAID AutoDetect support
1556 CONFIG_AUTODETECT_RAID
1557 An alternative to "Raid Boot support" is autodetect support.
1558 With this selected, any partitons of type 0xFD will be considered for
1559 inclusion in a RAID array. Information in the RAID-superblock on
1560 the partition will determine how it is included.
1562 Support for Acer PICA 1 chipset
1564 This is a machine with a R4400 133/150 MHz CPU. To compile a Linux
1565 kernel that runs on these, say Y here. For details about Linux on
1566 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1567 http://oss.sgi.com/mips .
1569 Support for Algorithmics P4032 (EXPERIMENTAL)
1571 This is an evaluation board of the British company Algorithmics. The
1572 board uses the R4300 and a R5230 CPUs. For more information about
1573 this board see http://www.algor.co.uk .
1575 Support for BAGET MIPS series
1577 This enables support for the Baget, a Russian embedded system. For
1578 more details about the Baget see the Linux/MIPS FAQ on
1579 http://oss.sgi.com/mips .
1581 Support for Cobalt Microserver
1582 CONFIG_COBALT_MICRO_SERVER
1583 This enables support for the Cobalt Microserver. For more information
1584 see the Linux/MIPS FAQ on http://oss.sgi.com/mips .
1588 This adds support for the Cobalt Microserver 2800. A kernel with this
1589 option selected will only work on the 2800.
1591 Support for DECstations
1593 This enables support for DEC's MIPS based workstations. For details
1594 see the Linux/MIPS FAQ on http://oss.sgi.com/mips and the
1595 DECstation porting pages on http://decstation.unix-ag.org .
1597 If you have one of the following DECstation Models you definitely
1598 want to choose R4xx0 for the CPU Type:
1605 otherwise choose R3000.
1607 Support for NEC DDB Vrc-5074
1609 This enables support for the VR5000-based NEC DDB Vrc-5074
1612 Support for Mips Magnum 4000
1613 CONFIG_MIPS_MAGNUM_4000
1614 This is a machine with a R4000 100 MHz CPU. To compile a Linux
1615 kernel that runs on these, say Y here. For details about Linux on
1616 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1617 http://oss.sgi.com/mips.
1619 Support for Olivetti M700
1620 CONFIG_OLIVETTI_M700
1621 This is a machine with a R4000 100 MHz CPU. To compile a Linux
1622 kernel that runs on these, say Y here. For details about Linux on
1623 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1624 http://oss.sgi.com/mips.
1626 Support for SGI IP22
1628 This are the SGI Indy, Challenge S and Indigo2, as well as certain
1629 OEM variants like the Tandem CMN B006S. To compile a Linux kernel
1630 that runs on these, say Y here.
1632 Support for SGI IP27
1633 This are the SGI Origin 200, Origin 2000 and Onyx 2 Graphics
1634 workstations. To compile a Linux kernel that runs on these, say Y
1638 CONFIG_SGI_SN0_N_MODE
1639 The nodes of Origin 200, Origin 2000 and Onyx 2 systems can be
1640 configured in either N-Modes which allows for more nodes or M-Mode
1641 which allows for more more memory. Your system is most probably
1642 running in M-Mode, so you should say N here.
1644 MIPS JAZZ onboard SONIC Ethernet support
1645 CONFIG_MIPS_JAZZ_SONIC
1646 This is the driver for the onboard card of of MIPS Magnum 4000,
1647 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
1649 MIPS JAZZ FAS216 SCSI support
1651 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1652 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1655 PCMCIA SCSI adapter support
1657 Say Y here if you intend to attach a PCMCIA or CardBus card to your
1658 computer which acts as a SCSI host adapter. These are credit card
1659 size devices often used with laptops.
1661 Note that the answer to this question won't directly affect the
1662 kernel: saying N will just cause this configure script to skip all
1663 the questions PCMCIA SCSI host adapters.
1665 Adaptec AHA152X PCMCIA support
1666 CONFIG_PCMCIA_AHA152X
1667 Say Y here if you intend to attach this type of PCMCIA SCSI host
1668 adapter to your computer.
1670 This driver is also available as a module called aha152x_cs.o ( =
1671 code which can be inserted in and removed from the running kernel
1672 whenever you want). If you want to compile it as a module, say M
1673 here and read Documentation/modules.txt.
1675 Qlogic PCMCIA support
1676 CONFIG_PCMCIA_QLOGIC
1677 Say Y here if you intend to attach this type of PCMCIA SCSI host
1678 adapter to your computer.
1680 This driver is also available as a module called qlogic_cs.o ( =
1681 code which can be inserted in and removed from the running kernel
1682 whenever you want). If you want to compile it as a module, say M
1683 here and read Documentation/modules.txt.
1685 Future Domain PCMCIA support
1686 CONFIG_PCMCIA_FDOMAIN
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 fdomain_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 Adaptec APA1480 CardBus support
1696 CONFIG_PCMCIA_APA1480
1697 Say Y here if you intend to attach this type of CardBus SCSI host
1698 adapter to your computer.
1700 This driver is also available as a module called apa1480_cb.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.
1707 Please make sure to pick the right CPU type. Linux/MIPS is not
1708 designed to be generic, i.e. Kernels compiled for R3000 CPUs will
1709 *not* work on R4000 Machines and vice versa.
1710 However, since most the supported Machines have an R4000 (or
1711 similar) CPU, R4xx0 might be a safe bet.
1712 If the resulting Kernel does not work try to recompile with R3000.
1714 Support for large 64-bit configurations
1715 CONFIG_MIPS_INSANE_LARGE
1716 MIPS R10000 does support a 44 bit / 16TB address space as opposed to
1717 previous 64-bit processors which only supported 40 bit / 1TB. If you
1718 need processes of more than 1TB virtual address space, say Y here.
1719 This will result in additional memory usage, so it is not
1720 recommended for normal users.
1722 Generate little endian code
1723 CONFIG_CPU_LITTLE_ENDIAN
1724 Some MIPS machines can be configured for either little or big endian
1725 byte order. These modes require different kernels. Say Y if your
1726 machine is little endian, N if it's a big endian machine.
1730 Unless you really know what you are doing, you should say Y here.
1731 The reason is that some programs need kernel networking support even
1732 when running on a stand-alone machine that isn't connected to any
1733 other computer. If you are upgrading from an older kernel, you
1734 should consider updating your networking tools too because changes
1735 in the kernel and the tools often go hand in hand. The tools are
1736 contained in the package net-tools, the location and version number
1737 of which are given in Documentation/Changes.
1739 For a general introduction to Linux networking, it is highly
1740 recommended to read the NET-3-HOWTO, available from
1741 http://www.linuxdoc.org/docs.html#howto .
1745 The Linux Socket Filter is derived from the Berkeley Packet Filter.
1746 If you say Y here, user-space programs can attach a filter to any
1747 socket and thereby tell the kernel that it should allow or disallow
1748 certain types of data to get through the socket. Linux Socket
1749 Filtering works on all socket types except TCP for now. See the text
1750 file Documentation/networking/filter.txt for more information.
1753 Network packet filtering
1755 Netfilter is a framework for filtering and mangling network packets
1756 that pass through your Linux box.
1758 The most common use of packet filtering is to run your Linux box as
1759 a firewall protecting a local network from the Internet. The type of
1760 firewall provided by this kernel support is called a "packet
1761 filter", which means that it can reject individual network packets
1762 based on type, source, destination etc. The other kind of firewall,
1763 a "proxy-based" one, is more secure but more intrusive and more
1764 bothersome to set up; it inspects the network traffic much more
1765 closely, modifies it and has knowledge about the higher level
1766 protocols, which a packet filter lacks. Moreover, proxy-based
1767 firewalls often require changes to the programs running on the local
1768 clients. Proxy-based firewalls don't need support by the kernel, but
1769 they are often combined with a packet filter, which only works if
1772 You should also say Y here if you intend to use your Linux box as
1773 the gateway to the Internet for a local network of machines without
1774 globally valid IP addresses. This is called "masquerading": if one
1775 of the computers on your local network wants to send something to
1776 the outside, your box can "masquerade" as that computer, i.e. it
1777 forwards the traffic to the intended outside destination, but
1778 modifies the packets to make it look like they came from the
1779 firewall box itself. It works both ways: if the outside host
1780 replies, the Linux box will silently forward the traffic to the
1781 correct local computer. This way, the computers on your local net
1782 are completely invisible to the outside world, even though they can
1783 reach the outside and can receive replies. It is even possible to
1784 run globally visible servers from within a masqueraded local network
1785 using a mechanism called portforwarding. Masquerading is also often
1786 called NAT (Network Address Translation).
1788 Another use of Netfilter is in transparent proxying: if a machine on
1789 the local network tries to connect to an outside host, your Linux
1790 box can transparently forward the traffic to a local server,
1791 typically a caching proxy server.
1793 Various modules exist for netfilter which replace the previous
1794 masquerading (ipmasqadm), packet filtering (ipchains), transparent
1795 proxying, and portforwarding mechanisms. Please see
1796 Documentation/Changes under "iptables" for the location of these
1799 Make sure to say N to "Fast switching" below if you intend to say Y
1800 here, as Fast switching currently bypasses netfilter.
1802 Chances are that you should say Y here if you compile a kernel which
1803 will run as a router and N for regular hosts. If unsure, say N.
1805 Network packet filtering debugging
1806 CONFIG_NETFILTER_DEBUG
1807 You can say Y here if you want to get additional messages useful in
1808 debugging the netfilter code.
1810 IP: connection tracking (required for masq/NAT)
1811 CONFIG_IP_NF_CONNTRACK
1812 Connection tracking keeps a record of what packets have passed
1813 through your machine, in order to figure out how they are related
1816 This is required to do Masquerading or other kinds of Network
1817 Address Translation (except for Fast NAT). It can also be used to
1818 enhance packet filtering (see `Connection state match support'
1821 If you want to compile it as a module, say M here and read
1822 Documentation/modules.txt. If unsure, say `N'.
1824 FTP protocol support
1826 Tracking FTP connections is problematic: special helpers are
1827 required for tracking them, and doing masquerading and other forms
1828 of Network Address Translation on them.
1830 If you want to compile it as a module, say M here and read
1831 Documentation/modules.txt. If unsure, say `Y'.
1833 IP: user space queueing via NETLINK (EXPERIMENTAL)
1835 Netfilter has the ability to queue packets to user space: the
1836 netlink device can be used to access them using this driver.
1838 If you want to compile it as a module, say M here and read
1839 Documentation/modules.txt. If unsure, say `N'.
1841 IP: ip tables support (required for filtering/masq/NAT)
1842 CONFIG_IP_NF_IPTABLES
1843 iptables is a general, extensible packet identification framework.
1844 The packet filtering and full NAT (masquerading, port forwarding,
1845 etc) subsystems now use this: say `Y' or `M' here if you want to use
1848 If you want to compile it as a module, say M here and read
1849 Documentation/modules.txt. If unsure, say `N'.
1852 CONFIG_IP_NF_MATCH_LIMIT
1853 limit matching allows you to control the rate at which a rule can be
1854 matched: mainly useful in combination with the LOG target ("LOG
1855 target support", below) and to avoid some Denial of Service attacks.
1857 If you want to compile it as a module, say M here and read
1858 Documentation/modules.txt. If unsure, say `N'.
1860 MAC address match support
1861 CONFIG_IP_NF_MATCH_MAC
1862 mac matching allows you to match packets based on the source
1863 ethernet address of the packet.
1865 If you want to compile it as a module, say M here and read
1866 Documentation/modules.txt. If unsure, say `N'.
1868 netfilter mark match support
1869 CONFIG_IP_NF_MATCH_MARK
1870 Netfilter mark matching allows you to match packets based on the
1871 `nfmark' value in the packet. This can be set by the MARK target
1874 If you want to compile it as a module, say M here and read
1875 Documentation/modules.txt. If unsure, say `N'.
1877 Multiple port match support
1878 CONFIG_IP_NF_MATCH_MULTIPORT
1879 Multiport matching allows you to match TCP or UDP packets based on
1880 a series of source or destination ports: normally a rule can only
1881 match a single range of ports.
1883 If you want to compile it as a module, say M here and read
1884 Documentation/modules.txt. If unsure, say `N'.
1887 CONFIG_IP_NF_MATCH_TOS
1888 TOS matching allows you to match packets based on the Type Of
1889 Service fields of the IP packet.
1891 If you want to compile it as a module, say M here and read
1892 Documentation/modules.txt. If unsure, say `N'.
1894 Connection state match support
1895 CONFIG_IP_NF_MATCH_STATE
1896 Connection state matching allows you to match packets based on their
1897 relationship to a tracked connection (ie. previous packets). This
1898 is a powerful tool for packet classification.
1900 If you want to compile it as a module, say M here and read
1901 Documentation/modules.txt. If unsure, say `N'.
1903 Unclean match support (EXPERIMENTAL)
1904 CONFIG_IP_NF_MATCH_UNCLEAN
1905 Unclean packet matching matches any strange or invalid packets, by
1906 looking at a series of fields in the IP, TCP, UDP and ICMP headers.
1908 If you want to compile it as a module, say M here and read
1909 Documentation/modules.txt. If unsure, say `N'.
1911 Owner match support (EXPERIMENTAL)
1912 CONFIG_IP_NF_MATCH_OWNER
1913 Packet owner matching allows you to match locally-generated packets
1914 based on who created them: the user, group, process or session.
1916 If you want to compile it as a module, say M here and read
1917 Documentation/modules.txt. If unsure, say `N'.
1921 Packet filtering defines a table `filter', which has a series of
1922 rules for simple packet filtering at local input, forwarding and
1923 local output. See the man page for iptables(8).
1925 If you want to compile it as a module, say M here and read
1926 Documentation/modules.txt. If unsure, say `N'.
1928 REJECT target support
1929 CONFIG_IP_NF_TARGET_REJECT
1930 The REJECT target allows a filtering rule to specify that an ICMP
1931 error should be issued in response to an incoming packet, rather
1932 than silently being dropped.
1934 If you want to compile it as a module, say M here and read
1935 Documentation/modules.txt. If unsure, say `N'.
1937 MIRROR target support (EXPERIMENTAL)
1938 CONFIG_IP_NF_TARGET_MIRROR
1939 The MIRROR target allows a filtering rule to specify that an
1940 incoming packet should be bounced back to the sender.
1942 If you want to compile it as a module, say M here and read
1943 Documentation/modules.txt. If unsure, say `N'.
1947 The Full NAT option allows masquerading, port forwarding and other
1948 forms of full Network Address Port Translation. It is controlled by
1949 the `nat' table in iptables: see the man page for iptables(8).
1951 If you want to compile it as a module, say M here and read
1952 Documentation/modules.txt. If unsure, say `N'.
1954 MASQUERADE target support
1955 CONFIG_IP_NF_TARGET_MASQUERADE
1956 Masquerading is a special case of NAT: all outgoing connections are
1957 changed to seem to come from a particular interface's address, and
1958 if the interface goes down, those connections are lost. This is
1959 only useful for dialup accounts with dynamic IP address (ie. your IP
1960 address will be different on next dialup).
1962 If you want to compile it as a module, say M here and read
1963 Documentation/modules.txt. If unsure, say `N'.
1965 REDIRECT target support
1966 CONFIG_IP_NF_TARGET_REDIRECT
1967 REDIRECT is a special case of NAT: all incoming connections are
1968 mapped onto the incoming interface's address, causing the packets to
1969 come to the local machine instead of passing through. This is
1970 useful for transparent proxies.
1972 If you want to compile it as a module, say M here and read
1973 Documentation/modules.txt. If unsure, say `N'.
1977 This option adds a `mangle' table to iptables: see the man page for
1978 iptables(8). This table is used for various packet alterations
1979 which can effect how the packet is routed.
1981 If you want to compile it as a module, say M here and read
1982 Documentation/modules.txt. If unsure, say `N'.
1985 CONFIG_IP_NF_TARGET_TOS
1986 This option adds a `TOS' target, which allows you to create rules in
1987 the `mangle' table which alter the Type Of Service field of an IP
1988 packet prior to routing.
1990 If you want to compile it as a module, say M here and read
1991 Documentation/modules.txt. If unsure, say `N'.
1994 CONFIG_IP_NF_TARGET_MARK
1995 This option adds a `MARK' target, which allows you to create rules
1996 in the `mangle' table which alter the netfilter mark (nfmark) field
1997 associated with the packet packet prior to routing. This can change
1998 the routing method (see `IP: use netfilter MARK value as routing
1999 key') and can also be used by other subsystems to change their
2002 If you want to compile it as a module, say M here and read
2003 Documentation/modules.txt. If unsure, say `N'.
2006 CONFIG_IP_NF_TARGET_LOG
2007 This option adds a `LOG' target, which allows you to create rules in
2008 any iptables table which records the packet header to the syslog.
2010 If you want to compile it as a module, say M here and read
2011 Documentation/modules.txt. If unsure, say `N'.
2013 ipchains (2.2-style) support
2014 CONFIG_IP_NF_COMPAT_IPCHAINS
2015 This option places ipchains (with masquerading and redirection
2016 support) back into the kernel, using the new netfilter
2017 infrastructure. It is not recommended for new installations (see
2018 `Packet filtering'). With this enabled, you should be able to use
2019 the ipchains tool exactly as in 2.2 kernels.
2021 If you want to compile it as a module, say M here and read
2022 Documentation/modules.txt. If unsure, say `N'.
2024 ipfwadm (2.0-style) support
2025 CONFIG_IP_NF_COMPAT_IPFWADM
2026 This option places ipfwadm (with masquerading and redirection
2027 support) back into the kernel, using the new netfilter
2028 infrastructure. It is not recommended for new installations (see
2029 `Packet filtering'). With this enabled, you should be able to use
2030 the ipfwadm tool exactly as in 2.0 kernels.
2032 If you want to compile it as a module, say M here and read
2033 Documentation/modules.txt. If unsure, say `N'.
2035 SYN flood protection
2037 Normal TCP/IP networking is open to an attack known as "SYN
2038 flooding". This denial-of-service attack prevents legitimate remote
2039 users from being able to connect to your computer during an ongoing
2040 attack and requires very little work from the attacker, who can
2041 operate from anywhere on the Internet.
2043 SYN cookies provide protection against this type of attack. If you
2044 say Y here, the TCP/IP stack will use a cryptographic challenge
2045 protocol known as "SYN cookies" to enable legitimate users to
2046 continue to connect, even when your machine is under attack. There
2047 is no need for the legitimate users to change their TCP/IP software;
2048 SYN cookies work transparently to them. For technical information
2049 about SYN cookies, check out
2050 ftp://koobera.math.uic.edu/syncookies.html .
2052 If you are SYN flooded, the source address reported by the kernel is
2053 likely to have been forged by the attacker; it is only reported as
2054 an aid in tracing the packets to their actual source and should not
2055 be taken as absolute truth.
2057 SYN cookies may prevent correct error reporting on clients when the
2058 server is really overloaded. If this happens frequently better turn
2061 If you say Y here, note that SYN cookies aren't enabled by default;
2062 you can enable them by saying Y to "/proc file system support" and
2063 "Sysctl support" below and executing the command
2065 echo 1 >/proc/sys/net/ipv4/tcp_syncookies
2067 at boot time after the /proc file system has been mounted.
2072 CONFIG_ALPHA_GENERIC
2073 This is the system type of your hardware. A "generic" kernel will
2074 run on any supported Alpha system. However, if you configure a
2075 kernel for your specific system, it will be faster and smaller.
2077 To find out what type of Alpha system you have, you may want to
2078 check out the Linux/Alpha FAQ, accessible on the WWW from
2079 http://www.alphalinux.org . In summary:
2081 Alcor/Alpha-XLT AS 600
2082 Alpha-XL XL-233, XL-266
2083 AlphaBook1 Alpha laptop
2084 Avanti AS 200, AS 205, AS 250, AS 255, AS 300, AS 400
2085 Cabriolet AlphaPC64, AlphaPCI64
2087 EB164 EB164 21164 evaluation board
2088 EB64+ EB64+ 21064 evaluation board
2089 EB66 EB66 21066 evaluation board
2090 EB66+ EB66+ 21066 evaluation board
2091 Jensen DECpc 150, DEC 2000 model 300,
2094 Miata Personal Workstation 433a, 433au, 500a,
2095 500au, 600a, or 600au
2097 Noname AXPpci33, UDB (Multia)
2098 Noritake AS 1000A, AS 600A, AS 800
2100 Rawhide AS 1200, AS 4000, AS 4100
2101 Ruffian RPX164-2, AlphaPC164-UX, AlphaPC164-BX
2103 Sable AS 2000, AS 2100
2106 Wildfire AlphaServer GS 40/80/160/320
2108 If you don't know what to do, choose "generic".
2110 EV5 CPU daughtercard
2112 Say Y if you have an AS 1000 5/xxx or an AS 1000A 5/xxx.
2116 Say Y if you have an AS 2000 5/xxx or an AS 2100 5/xxx.
2118 Using SRM as bootloader
2120 There are two different types of booting firmware on Alphas: SRM,
2121 which is command line driven, and ARC, which uses menus and arrow
2122 keys. Details about the Linux/Alpha booting process are contained in
2123 the Linux/Alpha FAQ, accessible on the WWW from
2124 http://www.alphalinux.org .
2126 The usual way to load Linux on an Alpha machine is to use MILO
2127 (a bootloader that lets you pass command line parameters to the
2128 kernel just like lilo does for the x86 architecture) which can be
2129 loaded either from ARC or can be installed directly as a permanent
2130 firmware replacement from floppy (which requires changing a certain
2131 jumper on the motherboard). If you want to do either of these, say N
2132 here. If MILO doesn't work on your system (true for Jensen
2133 motherboards), you can bypass it altogether and boot Linux directly
2134 from an SRM console; say Y here in order to do that. Note that you
2135 won't be able to boot from an IDE disk using SRM.
2139 Legacy kernel start address
2140 CONFIG_ALPHA_LEGACY_START_ADDRESS
2141 The 2.4 kernel changed the kernel start address from 0x310000
2142 to 0x810000 to make room for the Wildfire's larger SRM console.
2144 If you're using aboot 0.7 or later, the bootloader will examine
2145 the ELF headers to determine where to transfer control. Unfortunately,
2146 most older bootloaders -- APB, or MILO -- hardcoded the kernel
2147 start address rather than examining the ELF headers, and the result
2150 Say Y if you have a broken bootloader. Say N if you do not, or
2151 if you wish to run on Wildfire.
2153 Non-standard serial port support
2154 CONFIG_SERIAL_NONSTANDARD
2155 Say Y here if you have any non-standard serial boards -- boards
2156 which aren't supported using the standard "dumb" serial driver.
2157 This includes intelligent serial boards such as Cyclades,
2158 Digiboards, etc. These are usually used for systems that need many
2159 serial ports because they serve many terminals or dial-in
2162 Note that the answer to this question won't directly affect the
2163 kernel: saying N will just cause this configure script to skip all
2164 the questions about non-standard serial boards.
2166 Most people can say N here.
2168 Extended dumb serial driver options
2169 CONFIG_SERIAL_EXTENDED
2170 If you wish to use any non-standard features of the standard "dumb"
2171 driver, say Y here. This includes HUB6 support, shared serial
2172 interrupts, special multiport support, support for more than the
2173 four COM 1/2/3/4 boards, etc.
2175 Note that the answer to this question won't directly affect the
2176 kernel: saying N will just cause this configure script to skip all
2177 the questions about serial driver options. If unsure, say N.
2179 Support more than 4 serial ports
2180 CONFIG_SERIAL_MANY_PORTS
2181 Say Y here if you have dumb serial boards other than the four
2182 standard COM 1/2/3/4 ports. This may happen if you have an AST
2183 FourPort, Accent Async, Boca (read the Boca mini-HOWTO, available
2184 from http://www.linuxdoc.org/docs.html#howto ), or other custom
2185 serial port hardware which acts similar to standard serial port
2186 hardware. If you only use the standard COM 1/2/3/4 ports, you can
2187 say N here to save some memory. You can also say Y if you have an
2188 "intelligent" multiport card such as Cyclades, Digiboards, etc.
2190 Support for sharing serial interrupts
2191 CONFIG_SERIAL_SHARE_IRQ
2192 Some serial boards have hardware support which allows multiple dumb
2193 serial ports on the same board to share a single IRQ. To enable
2194 support for this in the serial driver, say Y here.
2196 Auto detect IRQ on standard ports (unsafe)
2197 CONFIG_SERIAL_DETECT_IRQ
2198 Say Y here if you want the kernel to try to guess which IRQ
2199 to use for your serial port.
2201 This is considered unsafe; it is far better to configure the IRQ in
2202 a boot script using the setserial command.
2206 Support special multiport boards
2207 CONFIG_SERIAL_MULTIPORT
2208 Some multiport serial ports have special ports which are used to
2209 signal when there are any serial ports on the board which need
2210 servicing. Say Y here to enable the serial driver to take advantage
2211 of those special I/O ports.
2213 SGI PROM Console Support
2214 CONFIG_SGI_PROM_CONSOLE
2215 Say Y here if you want to use the PROMs for console I/O.
2217 SGI Zilog85C30 serial support
2219 If you want to use your SGI's built-in serial ports under Linux,
2222 SGI Newport Graphics support (EXPERIMENTAL)
2223 CONFIG_SGI_NEWPORT_GFX
2224 If you have an SGI machine and you want to compile the graphics
2225 drivers, say Y here. This will include the code for the
2226 /dev/graphics and /dev/gfx drivers into the kernel for supporting
2227 virtualized access to your graphics hardware.
2229 SGI Newport Console support
2230 CONFIG_SGI_NEWPORT_CONSOLE
2231 Say Y here if you want the console on the Newport aka XL graphics
2232 card of your Indy. Most people say Y here.
2234 SGI DS1286 RTC support
2236 If you say Y here and create a character special file /dev/rtc with
2237 major number 10 and minor number 135 using mknod ("man mknod"), you
2238 will get access to the real time clock built into your computer.
2239 Every SGI has such a clock built in. It reports status information
2240 via the file /proc/rtc and its behaviour is set by various ioctls on
2243 Support the Bell Technologies HUB6 card
2245 Say Y here to enable support in the dumb serial driver to support
2248 PCMCIA serial device support
2249 CONFIG_PCMCIA_SERIAL_CS
2250 Say Y here to enable support for 16-bit PCMCIA serial devices,
2251 including serial port cards, modems, and the modem functions of
2252 multi-function ethernet/modem cards. (PCMCIA- or PC-cards are
2253 credit-card size devices often used with laptops.)
2255 This driver is also available as a module ( = code which can be
2256 inserted in and removed from the running kernel whenever you want).
2257 The module will be called serial_cs.o. If you want to compile it as
2258 a module, say M here and read Documentation/modules.txt. If unsure,
2261 CardBus serial device support
2262 CONFIG_PCMCIA_SERIAL_CB
2263 Say Y here to enable support for CardBus serial devices, including
2264 serial port cards, modems, and the modem functions of multi-function
2265 ethernet/modem devices. (CardBus cards are the newer and better
2266 version of PCMCIA- or PC-cards: credit card size devices often
2269 This driver is also available as a module ( = code which can be
2270 inserted in and removed from the running kernel whenever you want).
2271 The module will be called serial_cb.o. If you want to compile it as
2272 a module, say M here and read Documentation/modules.txt. If unsure,
2275 /dev/agpgart (AGP Support) (EXPERIMENTAL)
2277 AGP (Accelerated Graphics Port) is a bus system mainly used to
2278 connect graphics cards to the rest of the system.
2280 If you have an AGP system and you say Y here, it will be possible to
2281 use the AGP features of your 3D rendering video card. This code acts
2282 as a sort of "AGP driver" for the motherboard's chipset. The glx
2283 module will then be able to program the GART (graphics aperture
2284 relocation table) registers with appropriate values to transfer
2285 commands to the card.
2287 If you need more texture memory than you can get with the AGP GART
2288 (theoretically up to 256 MB, but in practice usually 64 or 128 MB
2289 due to kernel allocation issues), you could use PCI accesses
2290 and have up to a couple gigs of texture space.
2292 Note that this is the only means to have XFree4/GLX use
2293 write-combining with MTRR support on the AGP bus. Without it, OpenGL
2294 direct rendering will be a lot slower but still faster than PIO.
2296 For the moment, you should probably say N, unless you want to test
2297 the GLX component for XFree86 3.3.6, which can be downloaded from
2298 http://utah-glx.sourceforge.net/ , or need to use the 810 Xserver in
2301 This driver is available as a module. If you want to compile it as a
2302 module, say M here and read Documentation/modules.txt. The module
2303 will be called agpgart.o.
2305 Intel 440LX/BX/GX support
2307 This option gives you AGP support for the GLX component of the
2308 XFree86 4.x on Intel 440LX/BX/GX chipsets.
2310 For the moment, you should probably say N, unless you want to test
2311 the GLX component for XFree86 3.3.6, which can be downloaded from
2312 http://utah-glx.sourceforge.net/ .
2314 Intel I810/I810 DC100/I810e support
2316 This option gives you AGP support for the Xserver for the Intel
2317 810 chipset boards. This is required to do any useful video
2322 This option gives you AGP support for the GLX component of the
2323 XFree86 4.x on VIA MPV3/Apollo Pro chipsets.
2325 For the moment, you should probably say N, unless you want to test
2326 the GLX component for XFree86 3.3.6, which can be downloaded from
2327 http://utah-glx.sourceforge.net/ .
2329 AMD Irongate support
2331 This option gives you AGP support for the GLX component of the
2332 XFree86 4.x on AMD Irongate chipset.
2334 For the moment, you should probably say N, unless you want to test
2335 the GLX component for XFree86 3.3.6, which can be downloaded from
2336 http://utah-glx.sourceforge.net/ .
2340 This option gives you AGP support for the GLX component of the "soon
2341 to be released" XFree86 4.x on Silicon Integrated Systems [SiS]
2344 Note that 5591/5592 AGP chipsets are NOT supported.
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/ .
2352 This option gives you AGP support for the GLX component of the
2353 XFree86 4.x on the ALi M1541 chipset.
2355 This chipset can do AGP 1x and 2x, but note that there is an
2356 acknowledged incompatibility with Matrox G200 cards. Due to
2357 timing issues, this chipset cannot do AGP 2x with the G200.
2358 This is a hardware limitation. AGP 1x seems to be fine, though.
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/ .
2366 Find out whether you have a PCI motherboard. PCI is the name of a
2367 bus system, i.e. the way the CPU talks to the other stuff inside
2368 your box. Other bus systems are ISA, EISA, Microchannel (MCA) or
2369 VESA. If you have PCI, say Y, otherwise N.
2371 The PCI-HOWTO, available from
2372 http://www.linuxdoc.org/docs.html#howto , contains valuable
2373 information about which PCI hardware does work under Linux and which
2378 On PCI systems, the BIOS can be used to detect the PCI devices and
2379 determine their configuration. However, some old PCI motherboards
2380 have BIOS bugs and may crash if this is done. Also, some embedded
2381 PCI-based systems don't have any BIOS at all. Linux can also try to
2382 detect the PCI hardware directly without using the BIOS.
2384 With this option, you can specify how Linux should detect the PCI
2385 devices. If you choose "BIOS", the BIOS will be used, if you choose
2386 "Direct", the BIOS won't be used, and if you choose "Any", the
2387 kernel will try the direct access method and falls back to the BIOS
2388 if that doesn't work. If unsure, go with the default, which is
2391 PCI device name database
2393 By default, the kernel contains a database of all known PCI device
2394 names to make the information in /proc/pci, /proc/ioports and
2395 similar files comprehensible to the user. This database increases
2396 size of the kernel image by about 80KB, but it gets freed after the
2397 system boots up, so it doesn't take up kernel memory. Anyway, if you
2398 are building an installation floppy or kernel for an embedded system
2399 where kernel image size really matters, you can disable this feature
2400 and you'll get device ID numbers instead of names.
2402 When in doubt, say Y.
2406 MicroChannel Architecture is found in some IBM PS/2 machines and
2407 laptops. It is a bus system similar to PCI or ISA. See
2408 Documentation/mca.txt (and especially the web page given there)
2409 before attempting to build an MCA bus kernel.
2411 SGI Visual Workstation support
2413 The SGI Visual Workstation series is an IA32-based workstation
2414 based on SGI systems chips with some legacy PC hardware attached.
2415 Say Y here to create a kernel to run on the SGI 320 or 540.
2416 A kernel compiled for the Visual Workstation will not run on other
2417 PC boards and vice versa.
2418 See Documentation/sgi-visws.txt for more.
2420 SGI Visual Workstation framebuffer support
2422 SGI Visual Workstation support for framebuffer graphics.
2426 The Intelligent Input/Output (I2O) architecture allows hardware
2427 drivers to be split into two parts: an operating system specific
2428 module called the OSM and an hardware specific module called the
2429 HDM. The OSM can talk to a whole range of HDM's, and ideally the
2430 HDM's are not OS dependent. This allows for the same HDM driver to
2431 be used under different operating systems if the relevant OSM is in
2432 place. In order for this to work, you need to have an I2O interface
2433 adapter card in your computer. This card contains a special I/O
2434 processor (IOP), thus allowing high speeds since the CPU does not
2435 have to deal with I/O.
2437 If you say Y here, you will get a choice of interface adapter
2438 drivers and OSM's with the following questions.
2440 This support is also available as a module ( = code which can be
2441 inserted in and removed from the running kernel whenever you want).
2442 If you want to compile it as a module, say M here and read
2443 Documentation/modules.txt. You will get modules called i2o_core.o
2450 Say Y for support of PCI bus I2O interface adapters. Currently this
2451 is the only variety supported, so you should say Y.
2453 This support is also available as a module called i2o_pci.o ( = code
2454 which can be inserted in and removed from the running kernel
2455 whenever you want). If you want to compile it as a module, say M
2456 here and read Documentation/modules.txt.
2460 Include support for the I2O Block OSM. The Block OSM presents disk
2461 and other structured block devices to the operating system.
2463 This support is also available as a module called i2o_block.o ( =
2464 code which can be inserted in and removed from the running kernel
2465 whenever you want). If you want to compile it as a module, say M
2466 here and read Documentation/modules.txt.
2470 Include support for the LAN OSM. You will also need to include
2471 support for token ring or FDDI if you wish to use token ring or FDDI
2472 I2O cards with this driver.
2474 This support is also available as a module called i2o_lan.o ( = code
2475 which can be inserted in and removed from the running kernel
2476 whenever you want). If you want to compile it as a module, say M
2477 here and read Documentation/modules.txt.
2481 Allows direct SCSI access to SCSI devices on a SCSI or FibreChannel
2482 I2O controller. You can use both the SCSI and Block OSM together if
2485 This support is also available as a module called i2o_scsi.o ( =
2486 code which can be inserted in and removed from the running kernel
2487 whenever you want). If you want to compile it as a module, say M
2488 here and read Documentation/modules.txt.
2492 If you say Y here and to "/proc file system support", you will be
2493 able to read I2O related information from the virtual directory
2496 This support is also available as a module called i2o_proc.o ( =
2497 code which can be inserted in and removed from the running kernel
2498 whenever you want). If you want to compile it as a module, say M
2499 here and read Documentation/modules.txt.
2501 Plug and Play support
2503 Plug and Play (PnP) is a standard for peripherals which allows those
2504 peripherals to be configured by software, e.g. assign IRQ's or other
2505 parameters. No jumpers on the cards are needed, instead the values
2506 are provided to the cards from the BIOS, from the operating system,
2507 or using a user-space utility.
2509 Say Y here if you would like Linux to configure your Plug and Play
2510 devices. You should then also say Y to "ISA Plug and Play support",
2511 below. Alternatively, you can say N here and configure your PnP
2512 devices using the user space utilities contained in the isapnptools
2515 This support is also available as a module ( = code which can be
2516 inserted in and removed from the running kernel whenever you want).
2517 If you want to compile it as a module, say M here and read
2518 Documentation/modules.txt.
2520 ISA Plug and Play support
2522 Say Y here if you would like support for ISA Plug and Play devices.
2523 Some information is in Documentation/isapnp.txt.
2525 This support is also available as a module called isapnp.o ( =
2526 code which can be inserted in and removed from the running kernel
2527 whenever you want). If you want to compile it as a module, say M
2528 here and read Documentation/modules.txt.
2532 Support for hot-pluggable devices
2534 Say Y here if you want to plug devices into your computer while
2535 the system is running, and be able to use them quickly. In many
2536 cases, the devices can likewise be unplugged at any time too.
2538 One well known example of this is PCMCIA- or PC-cards, credit-card
2539 size devices such as network cards, modems or hard drives which are
2540 plugged into slots found on all modern laptop computers.
2542 Another example, used on modern desktops as well as laptops, is USB.
2543 Enable HOTPLUG with USB and KMOD, and your kernel will automatically
2544 call out to a user mode "policy agent" to load modules and set up
2545 software needed to use USB devices you plug in. Get agent software
2546 (at http://www.linux-usb.org/policy.html) and install it.
2548 PCMCIA/Cardbus support
2550 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
2551 computer. These are credit-card size devices such as network cards,
2552 modems or hard drives often used with laptops computers. There are
2553 actually two varieties of these cards: the older 16 bit PCMCIA cards
2554 and the newer 32 bit CardBus cards. If you want to use CardBus
2555 cards, you need to say Y here and also to "CardBus support" below.
2557 To use your PC-cards, you will need supporting software from David
2558 Hinds' pcmcia-cs package (see the file Documentation/Changes for
2559 location). Please also read the PCMCIA-HOWTO, available from
2560 http://www.linuxdoc.org/docs.html#howto
2562 This driver is also available as a module ( = code which can be
2563 inserted in and removed from the running kernel whenever you want).
2564 When compiled this way, there will be modules called pcmcia_core.o
2565 and ds.o. If you want to compile it as a module, say M here and
2566 read Documentation/modules.txt.
2570 CardBus is a bus mastering architecture for PC-cards, which allows
2571 for 32 bit PC-cards (the original PCMCIA standard specifies only
2572 a 16 bit wide bus). Many newer PC-cards are actually CardBus cards.
2574 To use your PC-cards, you will need supporting software from David
2575 Hinds' pcmcia-cs package (see the file Documentation/Changes for
2580 i82365/Yenta compatible bridge support
2582 Say Y here to include support for PCMCIA and CardBus host bridges
2583 that are register compatible with the Intel i82365 and/or the Yenta
2584 specification: this includes virtually all modern PCMCIA bridges.
2585 "Bridge" is the name used for the hardware inside your computer that
2586 PCMCIA cards are plugged into. If unsure, say Y.
2588 Databook TCIC host bridge support
2590 Say Y here to include support for the Databook TCIC family of PCMCIA
2591 host bridges. These are only found on a handful of old systems.
2592 "Bridge" is the name used for the hardware inside your computer that
2593 PCMCIA cards are plugged into. If unsure, say N.
2597 Inter Process Communication is a suite of library functions and
2598 system calls which let processes (running programs) synchronize and
2599 exchange information. It is generally considered to be a good thing,
2600 and some programs won't run unless you say Y here. In particular, if
2601 you want to run the DOS emulator dosemu under Linux (read the
2602 DOSEMU-HOWTO, available from
2603 http://www.linuxdoc.org/docs.html#howto ), you'll need to say Y
2606 You can find documentation about IPC with "info ipc" and also in
2607 section 6.4 of the Linux Programmer's Guide, available from
2608 http://www.linuxdoc.org/docs.html#guide .
2610 Shared memory is now implemented using a new (minimal) virtual file
2611 system. To mount it automatically at system startup just add the
2612 following line to your /etc/fstab:
2614 none /dev/shm shm defaults 0 0
2616 Saying Y here enlarges your kernel by about 18 KB. Just say Y.
2618 BSD Process Accounting
2619 CONFIG_BSD_PROCESS_ACCT
2620 If you say Y here, a user level program will be able to instruct the
2621 kernel (via a special system call) to write process accounting
2622 information to a file: whenever a process exits, information about
2623 that process will be appended to the file by the kernel. The
2624 information includes things such as creation time, owning user,
2625 command name, memory usage, controlling terminal etc. (the complete
2626 list is in the struct acct in include/linux/acct.h). It is up to the
2627 user level program to do useful things with this information. This
2628 is generally a good idea, so say Y.
2632 The sysctl interface provides a means of dynamically changing
2633 certain kernel parameters and variables on the fly without requiring
2634 a recompile of the kernel or reboot of the system. The primary
2635 interface consists of a system call, but if you say Y to "/proc
2636 file system support", a tree of modifiable sysctl entries will be
2637 generated beneath the /proc/sys directory. They are explained in the
2638 files in Documentation/sysctl/. Note that enabling this option will
2639 enlarge the kernel by at least 8 KB.
2641 As it is generally a good thing, you should say Y here unless
2642 building a kernel for install/rescue disks or your system is very
2645 Kernel core (/proc/kcore) format
2647 If you enabled support for /proc file system then the file
2648 /proc/kcore will contain the kernel core image. This can be used
2651 $ cd /usr/src/linux ; gdb vmlinux /proc/kcore
2653 You have two choices here: ELF and A.OUT. Selecting ELF will make
2654 /proc/kcore appear in ELF core format as defined by the Executable
2655 and Linking Format specification. Selecting A.OUT will choose the
2656 old "a.out" format which may be necessary for some old versions
2657 of binutils or on some architectures.
2659 This is especially useful if you have compiled the kernel with the
2660 "-g" option to preserve debugging information. It is mainly used
2661 for examining kernel data structures on the live kernel so if you
2662 don't understand what this means or are not a kernel hacker, just
2663 leave it at its default value ELF.
2665 Kernel support for ELF binaries
2667 ELF (Executable and Linkable Format) is a format for libraries and
2668 executables used across different architectures and operating
2669 systems. Saying Y here will enable your kernel to run ELF binaries
2670 and enlarge it by about 13 KB. ELF support under Linux has now all
2671 but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC)
2672 because it is portable (this does *not* mean that you will be able
2673 to run executables from different architectures or operating systems
2674 however) and makes building run-time libraries very easy. Many new
2675 executables are distributed solely in ELF format. You definitely
2678 Information about ELF is contained in the ELF HOWTO available from
2679 http://www.linuxdoc.org/docs.html#howto .
2681 If you find that after upgrading from Linux kernel 1.2 and saying Y
2682 here, you still can't run any ELF binaries (they just crash), then
2683 you'll have to install the newest ELF runtime libraries, including
2684 ld.so (check the file Documentation/Changes for location and latest
2687 If you want to compile this as a module ( = code which can be
2688 inserted in and removed from the running kernel whenever you want),
2689 say M here and read Documentation/modules.txt. The module will be
2690 called binfmt_elf.o. Saying M or N here is dangerous because some
2691 crucial programs on your system might be in ELF format.
2693 Kernel support for A.OUT binaries
2695 A.out (Assembler.OUTput) is a set of formats for libraries and
2696 executables used in the earliest versions of UNIX. Linux used the
2697 a.out formats QMAGIC and ZMAGIC until they were replaced with the
2700 As more and more programs are converted to ELF, the use for a.out
2701 will gradually diminish. If you disable this option it will reduce
2702 your kernel by one page. This is not much and by itself does not
2703 warrant removing support. However its removal is a good idea if you
2704 wish to ensure that absolutely none of your programs will use this
2705 older executable format. If you don't know what to answer at this
2706 point then answer Y. If someone told you "You need a kernel with
2707 QMAGIC support" then you'll have to say Y here. You may answer M to
2708 compile a.out support as a module and later load the module when you
2709 want to use a program or library in a.out format. The module will be
2710 called binfmt_aout.o. Saying M or N here is dangerous though,
2711 because some crucial programs on your system might still be in A.OUT
2714 Kernel support for Linux/Intel ELF binaries
2716 Say Y here if you want to be able to execute Linux/Intel ELF
2717 binaries just like native Alpha binaries on your Alpha machine. For
2718 this to work, you need to have the emulator /usr/bin/em86 in place.
2720 You can get the same functionality by saying N here and saying Y to
2721 "Kernel support for MISC binaries".
2723 You may answer M to compile the emulation support as a module and
2724 later load the module when you want to use a Linux/Intel binary. The
2725 module will be called binfmt_em86.o. If unsure, say Y.
2727 Kernel support for MISC binaries
2729 If you say Y here, it will be possible to plug wrapper-driven binary
2730 formats into the kernel. You will like this especially when you use
2731 programs that need an interpreter to run like Java, Python or
2732 Emacs-Lisp. It's also useful if you often run DOS executables under
2733 the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
2734 http://www.linuxdoc.org/docs.html#howto ). Once you have
2735 registered such a binary class with the kernel, you can start one of
2736 those programs simply by typing in its name at a shell prompt; Linux
2737 will automatically feed it to the correct interpreter.
2739 You can do other nice things, too. Read the file
2740 Documentation/binfmt_misc.txt to learn how to use this feature, and
2741 Documentation/java.txt for information about how to include Java
2744 You must say Y to "/proc file system support" (CONFIG_PROC_FS) to
2745 use this part of the kernel.
2747 You may say M here for module support and later load the module when
2748 you have use for it; the module is called binfmt_misc.o. If you
2749 don't know what to answer at this point, say Y.
2751 Solaris binary emulation (EXPERIMENTAL)
2753 This is experimental code which will enable you to run (many)
2754 Solaris binaries on your SPARC Linux machine.
2756 This code is also available as a module ( = code which can be
2757 inserted in and removed from the running kernel whenever you want).
2758 The module will be called solaris.o. If you want to compile it as a
2759 module, say M here and read Documentation/modules.txt.
2763 This is the processor type of your CPU. This information is used for
2764 optimizing purposes. In order to compile a kernel that can run on
2765 all x86 CPU types (albeit not optimally fast), you can specify
2768 The kernel will not necessarily run on earlier architectures than
2769 the one you have chosen, e.g. a Pentium optimized kernel will run on
2770 a PPro, but not necessarily on a i486.
2772 Here are the settings recommended for greatest speed:
2773 - "386" for the AMD/Cyrix/Intel 386DX/DXL/SL/SLC/SX, Cyrix/TI
2774 486DLC/DLC2, UMC 486SX-S and NexGen Nx586. Only "386" kernels will
2775 run on a 386 class machine.
2776 - "486" for the AMD/Cyrix/IBM/Intel 486DX/DX2/DX4 or
2777 SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5D or U5S.
2778 - "586" for generic Pentium CPUs, possibly lacking the TSC
2779 (time stamp counter) register.
2780 - "Pentium-Classic" for the Intel Pentium.
2781 - "Pentium-MMX" for the Intel Pentium MMX.
2782 - "Pentium-Pro" for the Intel Pentium Pro/Celeron/Pentium II.
2783 - "Pentium-III" for the Intel Pentium III.
2784 - "K6" for the AMD K6, K6-II and K6-III (aka K6-3D).
2785 - "Athlon" for the AMD Athlon (K7).
2786 - "Crusoe" for the Transmeta Crusoe series.
2787 - "Winchip-C6" for original IDT Winchip.
2788 - "Winchip-2" for IDT Winchip 2.
2789 - "Winchip-2A" for IDT Winchips with 3dNow! capabilities.
2791 If you don't know what to do, choose "386".
2795 Saying Y here will allow you to use Linux in text mode through a
2796 display that complies with the generic VGA standard. Virtually
2797 everyone wants that.
2799 The program SVGATextMode can be used to utilize SVGA video cards to
2800 their full potential in text mode. Download it from
2801 ftp://metalab.unc.edu/pub/Linux/utils/console .
2805 Video mode selection support
2807 This enables support for text mode selection on kernel startup. If
2808 you want to take advantage of some high-resolution text mode your
2809 card's BIOS offers, but the traditional Linux utilities like
2810 SVGATextMode don't, you can say Y here and set the mode using the
2811 "vga=" option from your boot loader (lilo or loadlin) or set
2812 "vga=ask" which brings up a video mode menu on kernel startup. (Try
2813 "man bootparam" or see the documentation of your boot loader about
2814 how to pass options to the kernel.)
2816 Read the file Documentation/svga.txt for more information about the
2817 Video mode selection support. If unsure, say N.
2819 Support for frame buffer devices (EXPERIMENTAL)
2821 The frame buffer device provides an abstraction for the graphics
2822 hardware. It represents the frame buffer of some video hardware and
2823 allows application software to access the graphics hardware through
2824 a well-defined interface, so the software doesn't need to know
2825 anything about the low-level (hardware register) stuff.
2827 Frame buffer devices work identically across the different
2828 architectures supported by Linux and make the implementation of
2829 application programs easier and more portable; at this point, an X
2830 server exists which uses the frame buffer device exclusively.
2831 On several non-X86 architectures, the frame buffer device is the
2832 only way to use the graphics hardware.
2834 The device is accessed through special device nodes, usually located
2835 in the /dev directory, i.e. /dev/fb*.
2837 You need an utility program called fbset to make full use of frame
2838 buffer devices. Please read Documentation/fb/framebuffer.txt and the
2839 Framebuffer-HOWTO at
2840 http://www.tahallah.demon.co.uk/programming/prog.html for more
2843 Say Y here and to the driver for your graphics board below if you
2844 are compiling a kernel for a non-x86 architecture.
2846 If you are compiling for the x86 architecture, you can say Y if you
2847 want to play with it, but it is not essential. Please note that
2848 running graphical applications that directly touch the hardware
2849 (e.g. an accelerated X server) and that are not frame buffer
2850 device-aware may cause unexpected results. If unsure, say N.
2854 This is the frame buffer device driver for the Acorn VIDC graphics
2855 hardware found in Acorn RISC PCs and other ARM-based machines. If
2858 Amiga native chipset support
2860 This is the frame buffer device driver for the builtin graphics
2861 chipset found in Amigas.
2863 The driver is also available as a module ( = code which can be
2864 inserted and removed from the running kernel whenever you want). The
2865 module will be called amifb.o. If you want to compile it as a
2866 module, say M here and read Documentation/modules.txt.
2868 Amiga OCS chipset support
2870 This enables support for the original Agnus and Denise video chips,
2871 found in the Amiga 1000 and most A500's and A2000's. If you intend
2872 to run Linux on any of these systems, say Y; otherwise say N.
2874 Amiga ECS chipset support
2876 This enables support for the Enhanced Chip Set, found in later
2877 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
2878 you intend to run Linux on any of these systems, say Y; otherwise
2881 Amiga AGA chipset support
2883 This enables support for the Advanced Graphics Architecture (also
2884 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
2885 and CD32. If you intend to run Linux on any of these systems, say Y;
2888 Amiga CyberVision support
2890 This enables support for the Cybervision 64 graphics card from
2891 Phase5. Please note that its use is not all that intuitive (i.e. if
2892 you have any questions, be sure to ask!). Say N unless you have a
2893 Cybervision 64 or plan to get one before you next recompile the
2894 kernel. Please note that this driver DOES NOT support the
2895 Cybervision 64 3D card, as they use incompatible video chips.
2897 CyberPro 20x0 support
2899 This enables support for the Integraphics CyberPro 20x0 and 5000
2900 VGA chips used in the Rebel.com Netwinder and other machines.
2901 Say Y if you have a NetWinder or a graphics card containing this
2902 device, otherwise say N.
2904 Amiga CyberVision3D support (EXPERIMENTAL)
2906 This enables support for the Cybervision 64/3D graphics card from
2907 Phase5. Please note that its use is not all that intuitive (i.e. if
2908 you have any questions, be sure to ask!). Say N unless you have a
2909 Cybervision 64/3D or plan to get one before you next recompile the
2910 kernel. Please note that this driver DOES NOT support the older
2911 Cybervision 64 card, as they use incompatible video chips.
2913 Amiga RetinaZ3 support (EXPERIMENTAL)
2915 This enables support for the Retina Z3 graphics card. Say N unless
2916 you have a Retina Z3 or plan to get one before you next recompile
2919 Cirrus Logic generic driver (EXPERIMENTAL)
2921 This enables support for Cirrus Logic GD542x/543x based boards on
2922 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
2924 If you have a PCI-based system, this enables support for these
2925 chips: GD-543x, GD-544x, GD-5480.
2927 Please read the file Documentation/fb/clgenfb.txt.
2929 Say N unless you have such a graphics board or plan to get one
2930 before you next recompile the kernel.
2932 Permedia2 support (EXPERIMENTAL)
2934 Say Y here if this is your graphics board.
2938 Say Y here if you want to run Linux on an MC680x0-based Apollo
2939 Domain workstation such as the DN3500.
2941 Apollo 3c505 support
2942 CONFIG_APOLLO_ELPLUS
2943 Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
2944 If you don't have one made for Apollos, you can use one from a PC,
2945 except that your Apollo won't be able to boot from it (because the
2946 code in the ROM will be for a PC).
2948 Atari native chipset support
2950 This is the frame buffer device driver for the builtin graphics
2951 chipset found in Ataris.
2953 Open Firmware frame buffer device support
2955 Say Y if you want support with Open Firmware for your graphics
2958 S3 Trio frame buffer device support
2960 If you have a S3 Trio say Y. Say N for S3 Virge.
2962 3Dfx Banshee/Voodoo3 display support (EXPERIMENTAL)
2964 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
2965 chips. Say Y if you have such a graphics board.
2967 The driver is also available as a module ( = code which can be
2968 inserted and removed from the running kernel whenever you want). The
2969 module will be called tdfxfb.o. If you want to compile it as a
2970 module, say M here and read Documentation/modules.txt.
2972 nVidia Riva support (EXPERIMENTAL)
2974 This driver supports graphics boards with the nVidia Riva (aka TNTx)
2976 Say Y if you have such a graphics board.
2978 The driver is also available as a module ( = code which can be
2979 inserted and removed from the running kernel whenever you want). The
2980 module will be called rivafb.o. If you want to compile it as a
2981 module, say M here and read Documentation/modules.txt.
2983 ATI Mach64 display support (EXPERIMENTAL)
2985 This driver supports graphics boards with the ATI Mach64 chips.
2986 Say Y if you have such a graphics board.
2988 The driver is also available as a module ( = code which can be
2989 inserted and removed from the running kernel whenever you want). The
2990 module will be called atyfb.o. If you want to compile it as a
2991 module, say M here and read Documentation/modules.txt.
2993 ATI Rage128 display support (EXPERIMENTAL)
2995 This driver supports graphics boards with the ATI Rage128 chips.
2996 Say Y if you have such a graphics board and read
2997 Documentation/fb/aty128fb.txt.
2999 The driver is also available as a module ( = code which can be
3000 inserted and removed from the running kernel whenever you want). The
3001 module will be called aty128fb.o. If you want to compile it as a
3002 module, say M here and read Documentation/modules.txt.
3004 PowerMac "control" frame buffer device support
3006 This driver supports a frame buffer for the graphics adapter in the
3007 Power Macintosh 7300 and others.
3009 PowerMac "platinum" frame buffer device support
3011 This driver supports a frame buffer for the "platinum" graphics
3012 adapter in some Power Macintoshes.
3014 PowerMac "valkyrie" frame buffer device support
3016 This driver supports a frame buffer for the "valkyrie" graphics
3017 adapter in some Power Macintoshes.
3019 Chips 65550 display support
3021 This is the frame buffer device driver for the Chips & Technologies
3022 65550 graphics chip in PowerBooks.
3024 TGA frame buffer support
3026 This is the frame buffer device driver for generic TGA graphic
3027 cards. Say Y if you have one of those.
3029 VESA VGA graphics console
3031 This is the frame buffer device driver for generic VESA 2.0
3032 compliant graphic cards. The older VESA 1.2 cards are not supported.
3033 You will get a boot time penguin logo at no additional cost. Please
3034 read Documentation/fb/vesafb.txt. If unsure, say Y.
3036 VGA 16-color planar support
3037 CONFIG_FBCON_VGA_PLANES
3038 This low level frame buffer console driver enable the kernel to use
3039 the 16-color planar modes of the old VGA cards where the bits of
3040 each pixel are separated into 4 planes.
3042 Only answer Y here if you have a (very old) VGA card that isn't VESA
3045 VGA 16-color graphics console
3047 This is the frame buffer device driver for VGA 16 color graphic
3048 cards. Say Y if you have such a card.
3050 This code is also available as a module. If you want to compile it
3051 as a module ( = code which can be inserted in and removed from the
3052 running kernel whenever you want), say M here and read
3053 Documentation/modules.txt. The module will be called vga16fb.o.
3055 Select other compiled-in fonts
3057 Say Y here if you would like to use fonts other than the default
3058 your frame buffer console usually use.
3060 Note that the answer to this question won't directly affect the
3061 kernel: saying N will just cause this configure script to skip all
3062 the questions about foreign fonts.
3064 If unsure, say N (the default choices are safe).
3068 This is the "high resolution" font for the VGA frame buffer (the one
3069 provided by the VGA text console 80x25 mode.
3073 Support only 8 pixels wide fonts
3074 CONFIG_FBCON_FONTWIDTH8_ONLY
3075 Answer Y here will make the kernel provide only the 8x8 fonts (these
3076 are the less readable).
3080 Sparc console 8x16 font
3082 This is the high resolution console font for Sun machines. Say Y.
3084 Sparc console 12x22 font (not supported by all drivers)
3085 CONFIG_FONT_SUN12x22
3086 This is the high resolution console font for Sun machines with very
3087 big letters (like the letters used in the SPARC PROM). If the
3088 standard font is unreadable for you, say Y, otherwise say N.
3092 This is the "high resolution" font for the VGA frame buffer (the one
3093 provided by the text console 80x50 (and higher) modes).
3095 Note that this is a poor quality font. The VGA 8x16 font is quite a
3098 Given the resolution provided by the frame buffer device, answer N
3101 Backward compatibility mode for Xpmac
3102 CONFIG_FB_COMPAT_XPMAC
3103 If you use the Xpmac X server (common with mklinux), you'll need to
3104 say Y here to use X. You should consider changing to XFree86 which
3105 includes a server that supports the frame buffer device directly
3108 HGA monochrome support (EXPERIMENTAL)
3110 Say Y here if you have a Hercules mono graphics card.
3112 This driver is also available as a module ( = code which can be
3113 inserted and removed from the running kernel whenever you want).
3114 The module will be called hgafb.o. If you want to compile it as
3115 a module, say M here and read Documentation/modules.txt.
3117 As this card technology is 15 years old, most people will answer N
3120 Matrox unified accelerated driver (EXPERIMENTAL)
3122 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
3123 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
3124 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video or
3125 Matrox G400 card in your box. At this time, support for the G100,
3126 Mystique G200 and Marvel G200 is untested.
3128 This driver is also available as a module ( = code which can be
3129 inserted and removed from the running kernel whenever you want).
3130 The module will be called matroxfb.o. If you want to compile it as
3131 a module, say M here and read Documentation/modules.txt.
3133 You can pass several parameters to the driver at boot time or at
3134 module load time. The parameters look like "video=matrox:XXX", where
3135 the meaning of XXX can be found at the end of the main source file
3136 (drivers/video/matroxfb.c). Please see the file
3137 Documentation/fb/matroxfb.txt.
3139 Matrox Millennium support
3140 CONFIG_FB_MATROX_MILLENIUM
3141 Say Y here if you have a Matrox Millennium or Matrox Millennium II
3142 video card. If you select "Advanced lowlevel driver options" below,
3143 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
3144 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
3145 also use font widths different from 8.
3147 Matrox Mystique support
3148 CONFIG_FB_MATROX_MYSTIQUE
3149 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
3150 video card. If you select "Advanced lowlevel driver options" below,
3151 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
3152 packed pixel and 32 bpp packed pixel. You can also use font widths
3155 Matrox G100/G200/G400 support
3156 CONFIG_FB_MATROX_G100
3157 Say Y here if you have a Matrox Productiva G100, Matrox Mystique
3158 G200, Matrox Marvel G200 or Matrox Millennium G200 video card. If
3159 you select "Advanced lowlevel driver options", you should check 8
3160 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed pixel and 32
3161 bpp packed pixel. You can also use font widths different from 8.
3163 If you need support for G400 secondary head, you must first say Y to
3164 "I2C support" and "I2C bit-banging support" in the character devices
3165 section, and then to "Matrox I2C support" and "G400 second head
3166 support" here in the framebuffer section.
3169 CONFIG_FB_MATROX_I2C
3170 This drivers creates I2C buses which are needed for accessing the
3171 DDC (I2C) bus present on all Matroxes, an I2C bus which
3172 interconnects Matrox optional devices, like MGA-TVO on G200 and
3173 G400, and the secondary head DDC bus, present on G400 only.
3175 You can say Y or M here if you want to experiment with monitor
3176 detection code. You must say Y or M here if you want to use either
3177 second head of G400 or MGA-TVO on G200 or G400.
3179 If you compile it as module, it will create a module named
3182 Matrox G400 second head support
3183 CONFIG_FB_MATROX_MAVEN
3184 Say Y or M here if you want to use a secondary head (meaning two
3185 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
3186 head is not compatible with accelerated XFree 3.3.x SVGA servers -
3187 secondary head output is blanked while you are in X. With XFree
3188 3.9.17 preview you can use both heads if you use SVGA over fbdev or
3189 the fbdev driver on first head and the fbdev driver on second head.
3191 If you compile it as module, two modules are created,
3192 matroxfb_crtc2.o and matroxfb_maven.o. Matroxfb_maven is needed for
3193 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
3194 also load i2c-matroxfb to get it to run.
3196 The driver starts in monitor mode and you must use the matroxset
3197 tool (available at ftp://platan.vc.cvut.cz/pub/linux/matrox-latest)
3198 to switch it to PAL or NTSC or to swap primary and secondary head
3199 outputs. Secondary head driver also always start in 640x480
3200 resolution, you must use fbset to change it.
3202 Also do not forget that second head supports only 16 and 32 bpp
3203 packed pixels, so it is a good idea to compile them into the kernel
3204 too. You can use only some font widths, as the driver uses generic
3205 painting procedures (the secondary head does not use acceleration
3208 There is no need for enabling 'Matrox multihead support' if you have
3209 only one Matrox card in the box.
3211 Matrox unified driver multihead support
3212 CONFIG_FB_MATROX_MULTIHEAD
3213 Say Y here if you have more than one (supported) Matrox device in
3214 your computer and you want to use all of them for different monitors
3215 ("multihead"). If you have only one device, you should say N because
3216 the driver compiled with Y is larger and a bit slower, especially on
3219 If you said M to "Matrox unified accelerated driver" and N here, you
3220 will still be able to use several Matrox devices simultaneously:
3221 insert several instances of the module matroxfb.o into the kernel
3222 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
3223 for the different Matrox devices. This method is slightly faster but
3224 uses 40 KB of kernel memory per Matrox card.
3226 MDA text console (dual-headed)
3228 Say Y here if you have an old MDA or monochrome Hercules graphics
3229 adapter in your system acting as a second head ( = video card). You
3230 will then be able to use two monitors with your Linux system. Do not
3231 say Y here if your MDA card is the primary card in your system; the
3232 normal VGA driver will handle it.
3234 This driver is also available as a module ( = code which can be
3235 inserted and removed from the running kernel whenever you want).
3236 The module will be called mdacon.o. If you want to compile it as
3237 a module, say M here and read Documentation/modules.txt.
3241 SBUS and UPA frame buffers
3243 Say Y if you want support for SBUS or UPA based frame buffer device.
3245 Creator/Creator3D support
3247 This is the frame buffer device driver for the Creator and Creator3D
3250 CGsix (GX,TurboGX) support
3252 This is the frame buffer device driver for the CGsix (GX, TurboGX)
3257 This is the frame buffer device driver for the BWtwo frame buffer.
3261 This is the frame buffer device driver for the CGthree frame buffer.
3263 TCX (SS4/SS5 only) support
3265 This is the frame buffer device driver for the TCX 24/8bit frame
3268 Virtual Frame Buffer support (ONLY FOR TESTING!)
3270 This is a `virtual' frame buffer device. It operates on a chunk of
3271 unswapable kernel memory instead of on the memory of a graphics
3272 board. This means you cannot see any output sent to this frame
3273 buffer device, while it does consume precious memory. The main use
3274 of this frame buffer device is testing and debugging the frame
3275 buffer subsystem. Do NOT enable it for normal systems! To protect
3276 the innocent, it has to be enabled explicitly at boot time using the
3277 kernel option `video=vfb:'.
3279 This driver is also available as a module ( = code which can be
3280 inserted and removed from the running kernel whenever you want). The
3281 module will be called vfb.o. If you want to compile it as a module,
3282 say M here and read Documentation/modules.txt.
3287 This is a framebuffer device for the SA-1100 LCD Controller.
3288 See http://www.linux-fbdev.org/ for information on framebuffer
3291 If you plan to use the LCD display with your SA-1100 system, say
3294 Advanced low level driver options
3295 CONFIG_FBCON_ADVANCED
3296 The frame buffer console uses character drawing routines that are
3297 tailored to the specific organization of pixels in the memory of
3298 your graphics hardware. These are called the low level frame buffer
3299 console drivers. Note that they are used for text console output
3300 only; they are NOT needed for graphical applications.
3302 If you say N here, the needed low level drivers are automatically
3303 enabled, depending on what frame buffer devices you selected above.
3304 This is recommended for most users.
3306 If you say Y here, you have more fine-grained control over which low
3307 level drivers are enabled. You can e.g. leave out low level drivers
3308 for color depths you do not intend to use for text consoles.
3310 Low level frame buffer console drivers can be modules ( = code which
3311 can be inserted and removed from the running kernel whenever you
3312 want). The modules will be called fbcon-*.o. If you want to compile
3313 (some of) them as modules, read Documentation/modules.txt.
3319 This is the low level frame buffer console driver for monochrome
3320 (2 colors) packed pixels.
3322 2 bpp packed pixels support
3324 This is the low level frame buffer console driver for 2 bits per
3325 pixel (4 colors) packed pixels.
3327 4 bpp packed pixels support
3329 This is the low level frame buffer console driver for 4 bits per
3330 pixel (16 colors) packed pixels.
3332 8 bpp packed pixels support
3334 This is the low level frame buffer console driver for 8 bits per
3335 pixel (256 colors) packed pixels.
3337 16 bpp packed pixels support
3339 This is the low level frame buffer console driver for 15 or 16 bits
3340 per pixel (32K or 64K colors, also known as `hicolor') packed
3343 24 bpp packed pixels support
3345 This is the low level frame buffer console driver for 24 bits per
3346 pixel (16M colors, also known as `truecolor') packed pixels. It is
3347 NOT for `sparse' 32 bits per pixel mode.
3349 32 bpp packed pixels support
3351 This is the low level frame buffer console driver for 32 bits per
3352 pixel (16M colors, also known as `truecolor') sparse packed pixels.
3354 Amiga bitplanes support
3356 This is the low level frame buffer console driver for 1 to 8
3357 bitplanes (2 to 256 colors) on Amiga.
3359 Amiga interleaved bitplanes support
3361 This is the low level frame buffer console driver for 1 to 8
3362 interleaved bitplanes (2 to 256 colors) on Amiga.
3364 Atari interleaved bitplanes (2 planes) support
3365 CONFIG_FBCON_IPLAN2P2
3366 This is the low level frame buffer console driver for 2 interleaved
3367 bitplanes (4 colors) on Atari.
3369 Atari interleaved bitplanes (4 planes) support
3370 CONFIG_FBCON_IPLAN2P4
3371 This is the low level frame buffer console driver for 4 interleaved
3372 bitplanes (16 colors) on Atari.
3374 Atari interleaved bitplanes (8 planes) support
3375 CONFIG_FBCON_IPLAN2P8
3376 This is the low level frame buffer console driver for 8 interleaved
3377 bitplanes (256 colors) on Atari.
3379 Mac variable bpp packed pixels support
3381 This is the low level frame buffer console driver for 1/2/4/8/16/32
3382 bits per pixel packed pixels on Mac. It supports variable font
3383 widths for low resolution screens.
3385 HGA monochrome support (EXPERIMENTAL)
3387 This is the low level frame buffer console driver for Hercules mono
3390 VGA characters/attributes support
3392 This is the low level frame buffer console driver for VGA text mode;
3393 it is used by frame buffer device drivers that support VGA text
3396 Parallel-port support
3398 If you want to use devices connected to your machine's parallel port
3399 (the connector at the computer with 25 holes), e.g. printer, ZIP
3400 drive, PLIP link (Parallel Line Internet Protocol is mainly used to
3401 create a mini network by connecting the parallel ports of two local
3402 machines) etc., then you need to say Y here; please read
3403 Documentation/parport.txt and drivers/parport/BUGS-parport.
3405 For extensive information about drivers for many devices attaching
3406 to the parallel port see http://www.torque.net/linux-pp.html on the
3409 It is possible to share a single parallel port among several devices
3410 and it is safe to compile all the corresponding drivers into the
3411 kernel. If you want to compile parallel port support as a module ( =
3412 code which can be inserted in and removed from the running kernel
3413 whenever you want), say M here and read Documentation/modules.txt.
3414 The module will be called parport.o. If you have more than one
3415 parallel port and want to specify which port and IRQ to be used by
3416 this driver at module load time, take a look at
3417 Documentation/networking/parport.txt.
3423 You should say Y here if you have a PC-style parallel port. All IBM
3424 PC compatible computers and some Alphas have PC-style parallel
3427 This code is also available as a module. If you want to compile it
3428 as a module ( = code which can be inserted in and removed from the
3429 running kernel whenever you want), say M here and read
3430 Documentation/modules.txt. The module will be called parport_pc.o.
3434 Use FIFO/DMA if available
3435 CONFIG_PARPORT_PC_FIFO
3436 Many parallel port chipsets provide hardware that can speed up
3437 printing. Say Y here if you want to take advantage of that.
3439 As well as actually having a FIFO, or DMA capability, the kernel
3440 will need to know which IRQ the parallel port has. By default,
3441 parallel port interrupts will not be used, and so neither will the
3442 FIFO. See Documentation/parport.txt to find out how to specify
3443 which IRQ/DMA to use.
3445 SuperIO chipset support (EXPERIMENTAL)
3446 CONFIG_PARPORT_PC_SUPERIO
3447 Saying Y here enables some probes for Super-IO chipsets in order to
3448 find out things like base addresses, IRQ lines and DMA channels. It
3451 Support for PCMCIA management for PC-style ports
3452 CONFIG_PARPORT_PC_PCMCIA
3453 Say Y here if you need PCMCIA support for your PC-style parallel
3454 ports. If unsure, say N.
3456 Support foreign hardware
3457 CONFIG_PARPORT_OTHER
3458 Say Y here if you want to be able to load driver modules to support
3459 other non-standard types of parallel ports. This causes a
3460 performance loss, so most people say N.
3462 Support IEEE1284 status readback
3463 CONFIG_PRINTER_READBACK
3464 If you have a device on your parallel port that support this
3465 protocol, this option will allow the device to report its status. It
3468 IEEE1284 transfer modes
3470 If you have a printer that supports status readback or device ID, or
3471 want to use a device that uses enhanced parallel port transfer modes
3472 such as EPP and ECP, say Y here to enable advanced IEEE 1284
3473 transfer modes. Also say Y if you want device ID information to
3474 appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
3476 Enable loadable module support
3478 Kernel modules are small pieces of compiled code which can be
3479 inserted in or removed from the running kernel, using the programs
3480 insmod and rmmod. This is described in the file
3481 Documentation/modules.txt, including the fact that you have to say
3482 "make modules" in order to compile the modules that you chose during
3483 kernel configuration. Modules can be device drivers, file systems,
3484 binary executable formats, and so on. If you think that you may want
3485 to make use of modules with this kernel in the future, then say Y
3486 here. If unsure, say Y.
3488 Set version information on all symbols for modules
3490 Usually, modules have to be recompiled whenever you switch to a new
3491 kernel. Saying Y here makes it possible, and safe, to use the
3492 same modules even after compiling a new kernel; this requires the
3493 program modprobe. All the software needed for module support is in
3494 the modutils package (check the file Documentation/Changes for
3495 location and latest version). NOTE: if you say Y here but don't
3496 have the program genksyms (which is also contained in the above
3497 mentioned modutils package), then the building of your kernel will
3498 fail. If you are going to use modules that are generated from
3499 non-kernel sources, you would benefit from this option. Otherwise
3500 it's not that important. So, N ought to be a safe bet.
3502 Kernel module loader support
3504 Normally when you have selected some drivers and/or file systems to
3505 be created as loadable modules, you also have the responsibility to
3506 load the corresponding modules (using the programs insmod or
3507 modprobe) before you can use them. If you say Y here however, the
3508 kernel will be able to load modules for itself: when a part of the
3509 kernel needs a module, it runs modprobe with the appropriate
3510 arguments, thereby loading the module if it is available. (This is a
3511 replacement for kerneld.) Say Y here and read about configuring it
3512 in Documentation/kmod.txt.
3514 ARP daemon support (EXPERIMENTAL)
3516 Normally, the kernel maintains an internal cache which maps IP
3517 addresses to hardware addresses on the local network, so that
3518 Ethernet/Token Ring/ etc. frames are sent to the proper address on
3519 the physical networking layer. For small networks having a few
3520 hundred directly connected hosts or less, keeping this address
3521 resolution (ARP) cache inside the kernel works well. However,
3522 maintaining an internal ARP cache does not work well for very large
3523 switched networks, and will use a lot of kernel memory if TCP/IP
3524 connections are made to many machines on the network.
3526 If you say Y here, the kernel's internal ARP cache will never grow
3527 to more than 256 entries (the oldest entries are expired in a LIFO
3528 manner) and communication will be attempted with the user space ARP
3529 daemon arpd. Arpd then answers the address resolution request either
3530 from its own cache or by asking the net.
3532 This code is experimental and also obsolete. If you want to use it,
3533 you need to find a version of the daemon arpd on the net somewhere,
3534 and you should also say Y to "Kernel/User network link driver",
3535 below. If unsure, say N.
3539 These are the protocols used on the Internet and on most local
3540 Ethernets. It is highly recommended to say Y here (this will enlarge
3541 your kernel by about 144 KB), since some programs (e.g. the X window
3542 system) use TCP/IP even if your machine is not connected to any
3543 other computer. You will get the so-called loopback device which
3544 allows you to ping yourself (great fun, that!).
3546 For an excellent introduction to Linux networking, please read the
3547 NET-3-HOWTO, available from
3548 http://www.linuxdoc.org/docs.html#howto .
3550 This option is also necessary if you want to use the full power of
3551 term (term is a program which gives you almost full Internet
3552 connectivity if you have a regular dial up shell account on some
3553 Internet connected Unix computer; for more information, read
3554 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html ).
3556 If you say Y here and also to "/proc file system support" and
3557 "Sysctl support" below, you can change various aspects of the
3558 behavior of the TCP/IP code by writing to the (virtual) files in
3559 /proc/sys/net/ipv4/*; the options are explained in the file
3560 Documentation/Networking/ip-sysctl.txt.
3562 Short answer: say Y.
3566 This is code for addressing several networked computers at once,
3567 enlarging your kernel by about 2 KB. You need multicasting if you
3568 intend to participate in the MBONE, a high bandwidth network on top
3569 of the Internet which carries audio and video broadcasts. More
3570 information about the MBONE is on the WWW at
3571 http://www-itg.lbl.gov/mbone/ . Information about the multicast
3572 capabilities of the various network cards is contained in
3573 Documentation/networking/multicast.txt. For most people, it's safe
3577 CONFIG_IP_ADVANCED_ROUTER
3578 If you intend to run your Linux box mostly as a router, i.e. as a
3579 computer that forwards and redistributes network packets, say Y; you
3580 will then be presented with several options that allow more precise
3581 control about the routing process.
3583 The answer to this question won't directly affect the kernel:
3584 answering N will just cause this configure script to skip all the
3585 questions about advanced routing.
3587 Note that your box can only act as a router if you enable IP
3588 forwarding in your kernel; you can do that by saying Y to "/proc
3589 file system support" and "Sysctl support" below and executing the
3592 echo "1" > /proc/sys/net/ipv4/ip_forward
3594 at boot time after the /proc file system has been mounted.
3596 If you turn on IP forwarding, you will also get the rp_filter, which
3597 automatically rejects incoming packets if the routing table entry
3598 for their source address doesn't match the network interface they're
3599 arriving on. This has security advantages because it prevents the
3600 so-called IP spoofing, however it can pose problems if you use
3601 asymmetric routing (packets from you to a host take a different path
3602 than packets from that host to you) or if you operate a non-routing
3603 host which has several IP addresses on different interfaces. To turn
3606 echo 0 > /proc/sys/net/ipv4/conf/<device>/rp_filter
3608 echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter
3610 If unsure, say N here.
3613 CONFIG_IP_MULTIPLE_TABLES
3614 Normally, a router decides what to do with a received packet based
3615 solely on the packet's final destination address. If you say Y here,
3616 the Linux router will also be able to take the packet's source
3617 address into account. Furthermore, if you also say Y to "IP: use TOS
3618 value as routing key" below, the TOS (Type-Of-Service) field of the
3619 packet can be used for routing decisions as well. In addition, if
3620 you say Y here and to "IP: fast network address translation" below,
3621 the router will also be able to modify source and destination
3622 addresses of forwarded packets.
3624 If you are interested in this, please see the preliminary
3625 documentation at http://www.compendium.com.ar/policy-routing.txt and
3626 ftp://post.tepkom.ru/pub/vol2/Linux/docs/advanced-routing.tex . You
3627 will need supporting software from ftp://ftp.inr.ac.ru/ip-routing/
3631 IP: equal cost multipath
3632 CONFIG_IP_ROUTE_MULTIPATH
3633 Normally, the routing tables specify a single action to be taken in
3634 a deterministic manner for a given packet. If you say Y here
3635 however, it becomes possible to attach several actions to a packet
3636 pattern, in effect specifying several alternative paths to travel
3637 for those packets. The router considers all these paths to be of
3638 equal "cost" and chooses one of them in a non-deterministic fashion
3639 if a matching packet arrives.
3641 IP: use TOS value as routing key
3643 The header of every IP packet carries a TOS (Type Of Service) value
3644 with which the packet requests a certain treatment, e.g. low latency
3645 (for interactive traffic), high throughput, or high reliability. If
3646 you say Y here, you will be able to specify different routes for
3647 packets with different TOS values.
3649 IP: use netfilter MARK value as routing key
3650 CONFIG_IP_ROUTE_FWMARK
3651 If you say Y here, you will be able to specify different routes for
3652 packets with different mark values (see iptables(8), MARK target).
3654 IP: verbose route monitoring
3655 CONFIG_IP_ROUTE_VERBOSE
3656 If you say Y here, which is recommended, then the kernel will print
3657 verbose messages regarding the routing, for example warnings about
3658 received packets which look strange and could be evidence of an
3659 attack or a misconfigured system somewhere. The information is
3660 handled by the klogd daemon which is responsible for kernel messages
3663 IP: large routing tables
3664 CONFIG_IP_ROUTE_LARGE_TABLES
3665 If you have routing zones that grow to more than about 64 entries,
3666 you may want to say Y here to speed up the routing process.
3668 IP: fast network address translation
3670 If you say Y here, your router will be able to modify source and
3671 destination addresses of packets that pass through it, in a manner
3672 you specify. General information about Network Address Translation
3673 can be gotten from the document
3674 http://www.csn.tu-chemnitz.de/~mha/linux-ip-nat/diplom/nat.html
3676 IP: kernel level autoconfiguration
3678 This enables automatic configuration of IP addresses of devices and
3679 of the routing table during kernel boot, based on either information
3680 supplied on the kernel command line or by BOOTP or RARP protocols.
3681 You need to say Y only for diskless machines requiring network
3682 access to boot (in which case you want to say Y to "Root file system
3683 on NFS" as well), because all other machines configure the network
3684 in their startup scripts.
3688 If you want your Linux box to mount its whole root file system (the
3689 one containing the directory /) from some other computer over the
3690 net via NFS and you want the IP address of your computer to be
3691 discovered automatically at boot time using the BOOTP protocol (a
3692 special protocol designed for doing this job), say Y here. In case
3693 the boot ROM of your network card was designed for booting Linux and
3694 does BOOTP itself, providing all necessary information on the kernel
3695 command line, you can say N here. If unsure, say Y. Note that if you
3696 want to use BOOTP, a BOOTP server must be operating on your network.
3697 Read Documentation/nfsroot.txt for details.
3701 If you want your Linux box to mount its whole root file system (the
3702 one containing the directory /) from some other computer over the
3703 net via NFS and you want the IP address of your computer to be
3704 discovered automatically at boot time using the RARP protocol (an
3705 older protocol which is being obsoleted by BOOTP and DHCP), say Y
3706 here. Note that if you want to use RARP, a RARP server must be
3707 operating on your network. Read Documentation/nfsroot.txt for
3712 Tunneling means encapsulating data of one protocol type within
3713 another protocol and sending it over a channel that understands the
3714 encapsulating protocol. This particular tunneling driver implements
3715 encapsulation of IP within IP, which sounds kind of pointless, but
3716 can be useful if you want to make your (or some other) machine
3717 appear on a different network than it physically is, or to use
3718 mobile-IP facilities (allowing laptops to seamlessly move between
3719 networks without changing their IP addresses; check out
3720 http://anchor.cs.binghamton.edu/~mobileip/LJ/index.html ).
3722 Saying Y to this option will produce two modules ( = code which can
3723 be inserted in and removed from the running kernel whenever you
3724 want). Most people won't need this and can say N.
3726 IP: GRE tunnels over IP
3728 Tunneling means encapsulating data of one protocol type within
3729 another protocol and sending it over a channel that understands the
3730 encapsulating protocol. This particular tunneling driver implements
3731 GRE (Generic Routing Encapsulation) and at this time allows
3732 encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
3733 This driver is useful if the other endpoint is a Cisco router: Cisco
3734 likes GRE much better than the other Linux tunneling driver ("IP:
3735 tunneling" above). In addition, GRE allows multicast redistribution
3738 IP: broadcast GRE over IP
3739 CONFIG_NET_IPGRE_BROADCAST
3740 One application of GRE/IP is to construct a broadcast WAN (Wide Area
3741 Network), which looks like a normal Ethernet LAN (Local Area
3742 Network), but can be distributed all over the Internet. If you want
3743 to do that, say Y here and to "IP: multicast routing" below.
3745 IP: multicast routing
3747 This is used if you want your machine to act as a router for IP
3748 packets that have several destination addresses. It is needed on the
3749 MBONE, a high bandwidth network on top of the Internet which carries
3750 audio and video broadcasts. In order to do that, you would most
3751 likely run the program mrouted. Information about the multicast
3752 capabilities of the various network cards is contained in
3753 Documentation/networking/multicast.txt. If you haven't heard about
3754 it, you don't need it.
3756 IP: PIM-SM version 1 support
3758 Kernel side support for Sparse Mode PIM (Protocol Independent
3759 Multicast) version 1. This multicast routing protocol is used widely
3760 because Cisco supports it. You need special software to use it
3761 (pimd-v1). Please see http://netweb.usc.edu/pim/ for more
3762 information about PIM.
3764 Say Y if you want to use PIM-SM v1. Note that you can say N here if
3765 you just want to use Dense Mode PIM.
3767 IP: PIM-SM version 2 support
3769 Kernel side support for Sparse Mode PIM version 2. In order to use
3770 this, you need an experimental routing daemon supporting it (pimd or
3771 gated-5). This routing protocol is not used widely, so say N unless
3772 you want to play with it.
3774 PC/TCP compatibility mode
3776 If you have been having difficulties telnetting to your Linux
3777 machine from a DOS system that uses (broken) PC/TCP networking
3778 software (all versions up to OnNet 2.0) over your local Ethernet try
3779 saying Y here. Everyone else says N.
3781 People having problems with NCSA telnet should see the file
3782 Documentation/networking/ncsa-telnet.
3784 Path MTU Discovery (normally enabled)
3785 CONFIG_PATH_MTU_DISCOVERY
3786 MTU (maximal transfer unit) is the size of the chunks we send out
3787 over the net. "Path MTU Discovery" means that, instead of always
3788 sending very small chunks, we start out sending big ones and if we
3789 then discover that some host along the way likes its chunks smaller,
3790 we adjust to a smaller size. This is good, so most people say Y
3793 However, some DOS software (versions of DOS NCSA telnet and Trumpet
3794 Winsock in PPP mode) is broken and won't be able to connect to your
3795 Linux machine correctly in all cases (especially through a terminal
3796 server) unless you say N here. See
3797 Documentation/networking/ncsa-telnet for the location of fixed NCSA
3798 telnet clients. If in doubt, say Y.
3800 Disable NAGLE algorithm (normally enabled)
3801 CONFIG_TCP_NAGLE_OFF
3802 The NAGLE algorithm works by requiring an acknowledgment before
3803 sending small IP frames (packets). This keeps tiny telnet and
3804 rlogin packets from congesting Wide Area Networks. Most people
3805 strongly recommend to say N here, thereby leaving NAGLE
3806 enabled. Those programs that would benefit from disabling this
3807 facility can do it on a per connection basis themselves.
3809 IP: Allow large windows (not recommended if <16 MB of memory)
3811 On high speed, long distance networks the performance limit on
3812 networking becomes the amount of data the sending machine can buffer
3813 until the other end confirms its reception. (At 45 Mbit/second there
3814 are a lot of bits between New York and London ...). If you say Y
3815 here, bigger buffers can be used which allows larger amounts of data
3816 to be "in flight" at any given time. It also means a user process
3817 can require a lot more memory for network buffers and thus this
3818 option is best used only on machines with 16 MB of memory or higher.
3819 Unless you are using long links with end to end speeds of over 2
3820 Mbit a second or satellite links this option will make no difference
3825 If you say Y here, you will include support for Unix domain sockets;
3826 sockets are the standard Unix mechanism for establishing and
3827 accessing network connections. Many commonly used programs such as
3828 the X Window system and syslog use these sockets even if your
3829 machine is not connected to any network. Unless you are working on
3830 an embedded system or something similar, you therefore definitely
3833 However, the socket support is also available as a module ( = code
3834 which can be inserted in and removed from the running kernel
3835 whenever you want). If you want to compile it as a module, say M
3836 here and read Documentation/modules.txt. The module will be called
3837 unix.o. If you try building this as a module and you have said Y to
3838 "Kernel module loader support" above, be sure to add 'alias net-pf-1
3839 unix' to your /etc/modules.conf file. Note that several important
3840 services won't work correctly if you say M here and then neglect to
3843 Say Y unless you know what you are doing.
3845 The IPv6 protocol (EXPERIMENTAL)
3847 This is experimental support for the next version of the Internet
3848 Protocol: IP version 6 (also called IPng "IP next generation").
3849 Features of this new protocol include: expanded address space,
3850 authentication and privacy, and seamless interoperability with the
3851 current version of IP (IP version 4). For general information about
3852 IPv6, see http://playground.sun.com/pub/ipng/html/ipng-main.html ;
3853 for specific information about IPv6 under Linux read the HOWTO at
3854 http://www.bieringer.de/linux/IPv6/ and the file net/ipv6/README in
3857 If you want to use IPv6, please upgrade to the newest net-tools as
3858 given in Documentation/Changes. You will still be able to do regular
3859 IPv4 networking as well.
3861 This protocol support is also available as a module ( = code which
3862 can be inserted in and removed from the running kernel whenever you
3863 want). The module will be called ipv6.o. If you want to compile it
3864 as a module, say M here and read Documentation/modules.txt.
3866 It is safe to say N here for now.
3868 IPv6: enable EUI-64 token format
3870 6bone, the network of computers using the IPv6 protocol, is moving
3871 to a new aggregatable address format and a new link local address
3872 assignment (EUI-64). Say Y if your site has upgraded already, or
3873 has started to upgrade.
3875 IPv6: disable provider based addresses
3877 Linux tries to operate correctly when your site has moved to EUI-64
3878 only partially. Unfortunately, the two address formats (old:
3879 "provider based" and new: "aggregatable") are incompatible. Say Y if
3880 your site finished the upgrade to EUI-64, and/or you encountered
3881 some problems caused by the presence of two link-local addresses on
3884 IPv6: routing messages via old netlink
3886 You can say Y here to receive routing messages from the IPv6 code
3887 through the old netlink interface. However, a better option is to
3888 say Y to "Kernel/User network link driver" and to "Routing
3891 Kernel httpd acceleration (EXPERIMENTAL)
3893 The kernel httpd acceleration daemon (kHTTPd) is a (limited) web
3894 server built into the kernel. It is limited since it can only serve
3895 files from the file system and cannot deal with executable content
3896 such as CGI scripts. Serving files is sped up if you use kHTTPd.
3897 If kHTTPd is not able to fulfill a request, it can transparently
3898 pass it through to a user space web server such as apache.
3900 Saying "M" here builds the kHTTPd module; this is NOT enough to have
3901 a working kHTTPd. For safety reasons, the module has to be activated
3902 by doing a "echo 1 > /proc/sys/net/khttpd/start" after inserting the
3905 Before using this, read the README in net/khttpd !
3907 The kHTTPd is experimental. Be careful when using it on a production
3908 machine. Also note that kHTTPd doesn't support virtual servers yet.
3912 This is support for the Novell networking protocol, IPX, commonly
3913 used for local networks of Windows machines. You need it if you want
3914 to access Novell NetWare file or print servers using the Linux
3915 Novell client ncpfs (available from
3916 ftp://metalab.unc.edu/pub/Linux/system/filesystems/ ) or from within
3917 the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
3918 http://www.linuxdoc.org/docs.html#howto ). In order to do the
3919 former, you'll also have to say Y to "NCP file system support",
3922 IPX is similar in scope to IP, while SPX, which runs on top of IPX,
3923 is similar to TCP. There is also experimental support for SPX in
3924 Linux (see "SPX networking", below).
3926 To turn your Linux box into a fully featured NetWare file server and
3927 IPX router, say Y here and fetch either lwared from
3928 ftp://metalab.unc.edu/pub/Linux/system/network/daemons/ or mars_nwe
3929 from ftp://ftp.gwdg.de/pub/linux/misc/ncpfs . For more information,
3930 read the IPX-HOWTO available from
3931 http://www.linuxdoc.org/docs.html#howto .
3933 General information about how to connect Linux, Windows machines and
3934 Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
3936 The IPX driver would enlarge your kernel by about 16 KB. This driver
3937 is also available as a module ( = code which can be inserted in and
3938 removed from the running kernel whenever you want). The module will
3939 be called ipx.o. If you want to compile it as a module, say M here
3940 and read Documentation/modules.txt. Unless you want to integrate
3941 your Linux box with a local Novell network, say N.
3943 IPX: Full internal IPX network
3945 Every IPX network has an address that identifies it. Sometimes it is
3946 useful to give an IPX "network" address to your Linux box as well
3947 (for example if your box is acting as a file server for different
3948 IPX networks: it will then be accessible from everywhere using the
3949 same address). The way this is done is to create a virtual internal
3950 "network" inside your box and to assign an IPX address to this
3951 network. Say Y here if you want to do this; read the IPX-HOWTO at
3952 http://www.linuxdoc.org/docs.html#howto for details.
3954 The full internal IPX network enables you to allocate sockets on
3955 different virtual nodes of the internal network. This is done by
3956 evaluating the field sipx_node of the socket address given to the
3957 bind call. So applications should always initialize the node field
3958 to 0 when binding a socket on the primary network. In this case the
3959 socket is assigned the default node that has been given to the
3960 kernel when the internal network was created. By enabling the full
3961 internal IPX network the cross-forwarding of packets targeted at
3962 'special' sockets to sockets listening on the primary network is
3963 disabled. This might break existing applications, especially RIP/SAP
3964 daemons. A RIP/SAP daemon that works well with the full internal net
3965 can be found on ftp://ftp.gwdg.de/pub/linux/misc/ncpfs .
3967 If you don't know what you are doing, say N.
3969 IPX: SPX networking (EXPERIMENTAL)
3971 The Sequenced Packet eXchange protocol is a transport layer protocol
3972 built on top of IPX. It is used in Novell NetWare systems for
3973 client-server applications and is similar to TCP (which runs on top
3976 Note that Novell NetWare file sharing does not use SPX; it uses a
3977 protocol called NCP, for which separate Linux support is available
3978 ("NCP file system support" below for the client side, and the user
3979 space programs lwared or mars_nwe for the server side).
3981 Say Y here if you have use for SPX; read the IPX-HOWTO at
3982 http://www.linuxdoc.org/docs.html#howto for details.
3984 This driver is also available as a module ( = code which can be
3985 inserted in and removed from the running kernel whenever you want).
3986 The module will be called af_spx.o. If you want to compile it as a
3987 module, say M here and read Documentation/modules.txt.
3989 DECnet networking (EXPERIMENTAL)
3991 The DECnet networking protocol was used in many products made by
3992 Digital (now Compaq). It provides reliable stream and sequenced
3993 packet communications over which run a variety of services similar
3994 to those which run over TCP/IP.
3996 To find some tools to use with the kernel layer support, please
3997 look at Patrick Caulfield's web site:
3998 http://linux.dreamtime.org/decnet/
4000 More detailed documentation is available in the
4001 Documentation/networking/decnet.txt file.
4003 Be sure to say Y to "/proc file system support" and "Sysctl support"
4004 below when using DECnet, since you will need sysctl support to aid
4005 in configuration at run time.
4007 The DECnet code is also available as a module ( = code which can be
4008 inserted in and removed from the running kernel whenever you want).
4009 The module is called decnet.o.
4011 DECnet SIOCFIGCONF support
4012 CONFIG_DECNET_SIOCGIFCONF
4013 This option should only be turned on if you are really sure that
4014 you know what you are doing. It can break other applications which
4015 use this system call and the proper way to get the information
4016 provided by this call is to use rtnetlink.
4020 DECnet Router Support (EXPERIMENTAL)
4021 CONFIG_DECNET_ROUTER
4022 Add support for turning your DECnet Endnode into a level 1 or 2
4023 router. This is an unfinished option for developers only. If you do
4024 say Y here, then make sure that you also say Y to "Kernel/User
4025 network link driver", "Routing messages" and "Network packet
4026 filtering". The first two are required to allow configuration via
4027 rtnetlink (currently you need Alexey Kuznetsov's iproute2 package
4028 from ftp://ftp.inr.ac.ru). The "Network packet filtering" option
4029 will be required for the forthcoming routing daemon to work.
4031 See Documentation/networking/decnet.txt for more information.
4033 DECnet: use FWMARK value as routing key
4034 CONFIG_DECNET_ROUTE_FWMARK
4035 If you say Y here, you will be able to specify different routes for
4036 packets with different FWMARK ("firewalling mark") values
4037 (see ipchains(8), "-m" argument).
4039 Appletalk interfaces support
4041 AppleTalk is the way Apple computers speak to each other on a
4042 network. If your Linux box is connected to such a network and you
4043 want to join the conversation, say Y.
4045 AppleTalk protocol support
4047 AppleTalk is the way Apple computers speak to each other on a
4048 network. If your Linux box is connected to such a network and you
4049 want to join the conversation, say Y. You will need to use the
4050 netatalk package so that your Linux box can act as a print and file
4051 server for Macs as well as access AppleTalk printers. Check out
4052 http://threepio.hitchcock.org/cgi-bin/faq/netatalk/faq.pl on the WWW
4053 for details. EtherTalk is the name used for AppleTalk over Ethernet
4054 and the cheaper and slower LocalTalk is AppleTalk over a proprietary
4055 Apple network using serial links. EtherTalk and LocalTalk are fully
4058 General information about how to connect Linux, Windows machines and
4059 Macs is on the WWW at http://www.eats.com/linux_mac_win.html . The
4060 NET-3-HOWTO, available from
4061 http://www.linuxdoc.org/docs.html#howto , contains valuable
4062 information as well.
4064 This driver is also available as a module ( = code which can be
4065 inserted in and removed from the running kernel whenever you want).
4066 The module is called appletalk.o. If you want to compile it as a
4067 module, say M here and read Documentation/modules.txt. I hear that
4068 the GNU boycott of Apple is over, so even politically correct people
4069 are allowed to say Y here.
4071 AppleTalk-IP driver support
4073 This allows IP networking for users who only have AppleTalk
4074 networking available. This feature is experimental. With this
4075 driver, you can encapsulate IP inside AppleTalk (e.g. if your Linux
4076 box is stuck on an AppleTalk only network) or decapsulate (e.g. if
4077 you want your Linux box to act as an Internet gateway for a zoo of
4078 AppleTalk connected Macs). Please see the file
4079 Documentation/networking/ipddp.txt for more information.
4081 If you say Y here, the AppleTalk-IP support will be compiled into
4082 the kernel. In this case, you can either use encapsulation or
4083 decapsulation, but not both. With the following two questions, you
4084 decide which one you want.
4086 If you say M here, the AppleTalk-IP support will be compiled as a
4087 module ( = code which can be inserted in and removed from the
4088 running kernel whenever you want, read Documentation/modules.txt).
4089 The module is called ipddp.o. In this case, you will be able to use
4090 both encapsulation and decapsulation simultaneously, by loading two
4091 copies of the module and specifying different values for the module
4094 IP to AppleTalk-IP Encapsulation support
4096 If you say Y here, the AppleTalk-IP code will be able to encapsulate
4097 IP packets inside AppleTalk frames; this is useful if your Linux box
4098 is stuck on an AppleTalk network (which hopefully contains a
4099 decapsulator somewhere). Please see
4100 Documentation/networking/ipddp.txt for more information. If you said
4101 Y to "AppleTalk-IP driver support" above and you say Y here, then
4102 you cannot say Y to "AppleTalk-IP to IP Decapsulation support",
4105 AppleTalk-IP to IP Decapsulation support
4107 If you say Y here, the AppleTalk-IP code will be able to decapsulate
4108 AppleTalk-IP frames to IP packets; this is useful if you want your
4109 Linux box to act as an Internet gateway for an AppleTalk network.
4110 Please see Documentation/networking/ipddp.txt for more information.
4111 If you said Y to "AppleTalk-IP driver support" above and you say Y
4112 here, then you cannot say Y to "IP to AppleTalk-IP Encapsulation
4115 Apple/Farallon LocalTalk PC card support
4117 This allows you to use the AppleTalk PC card to connect to LocalTalk
4118 networks. The card is also known as the Farallon PhoneNet PC card.
4119 If you are in doubt, this card is the one with the 65C02 chip on it.
4120 You also need version 1.3.3 or later of the netatalk package.
4121 This driver is experimental, which means that it may not work.
4122 See the file Documentation/networking/ltpc.txt.
4124 COPS LocalTalk PC card support
4126 This allows you to use COPS AppleTalk cards to connect to LocalTalk
4127 networks. You also need version 1.3.3 or later of the netatalk
4128 package. This driver is experimental, which means that it may not
4129 work. This driver will only work if you choose "AppleTalk DDP"
4130 networking support, above.
4131 Please read the file Documentation/networking/cops.txt.
4133 Dayna firmware support
4135 Support COPS compatible cards with Dayna style firmware (Dayna
4136 DL2000/ Daynatalk/PC (half length), COPS LT-95, Farallon PhoneNET PC
4137 III, Farallon PhoneNET PC II).
4139 Tangent firmware support
4141 Support COPS compatible cards with Tangent style firmware (Tangent
4142 ATB_II, Novell NL-1000, Daystar Digital LT-200.
4144 Amateur Radio support
4146 If you want to connect your Linux box to an amateur radio, answer Y
4147 here. You want to read http://www.tapr.org/tapr/html/pkthome.html
4148 and the HAM-HOWTO and the AX25-HOWTO, both available from
4149 http://www.linuxdoc.org/docs.html#howto .
4151 Note that the answer to this question won't directly affect the
4152 kernel: saying N will just cause this configure script to skip all
4153 the questions about amateur radio.
4155 Amateur Radio AX.25 Level 2
4157 This is the protocol used for computer communication over amateur
4158 radio. It is either used by itself for point-to-point links, or to
4159 carry other protocols such as tcp/ip. To use it, you need a device
4160 that connects your Linux box to your amateur radio. You can either
4161 use a low speed TNC (a Terminal Node Controller acts as a kind of
4162 modem connecting your computer's serial port to your radio's
4163 microphone input and speaker output) supporting the KISS protocol or
4164 one of the various SCC cards that are supported by the generic Z8530
4165 or the DMA SCC driver. Another option are the Baycom modem serial
4166 and parallel port hacks or the sound card modem (supported by their
4167 own drivers). If you say Y here, you also have to say Y to one of
4170 Information about where to get supporting software for Linux amateur
4171 radio as well as information about how to configure an AX.25 port is
4172 contained in the AX25-HOWTO, available from
4173 http://www.linuxdoc.org/docs.html#howto . You might also want to
4174 check out the file Documentation/networking/ax25.txt in the kernel
4175 source. More information about digital amateur radio in general is
4176 on the WWW at http://www.tapr.org/tapr/html/pkthome.html .
4178 This driver is also available as a module ( = code which can be
4179 inserted in and removed from the running kernel whenever you want).
4180 The module will be called ax25.o. If you want to compile it as a
4181 module, say M here and read Documentation/modules.txt.
4183 AX.25 DAMA Slave support
4184 CONFIG_AX25_DAMA_SLAVE
4185 DAMA is a mechanism to prevent collisions when doing AX.25
4186 networking. A DAMA server (called "master") accepts incoming traffic
4187 from clients (called "slaves") and redistributes it to other slaves.
4188 If you say Y here, your Linux box will act as a DAMA slave; this is
4189 transparent in that you don't have to do any special DAMA
4190 configuration. (Linux cannot yet act as a DAMA server.) If unsure,
4193 AX.25 DAMA Master support
4194 CONFIG_AX25_DAMA_MASTER
4195 DAMA is a mechanism to prevent collisions when doing AX.25
4196 networking. A DAMA server (called "master") accepts incoming traffic
4197 from clients (called "slaves") and redistributes it to other
4198 slaves. If you say Y here, your Linux box will act as a DAMA server.
4201 Amateur Radio NET/ROM
4203 NET/ROM is a network layer protocol on top of AX.25 useful for
4206 A comprehensive listing of all the software for Linux amateur radio
4207 users as well as information about how to configure an AX.25 port is
4208 contained in the AX25-HOWTO, available from
4209 http://www.linuxdoc.org/docs.html#howto . You also might want to
4210 check out the file Documentation/networking/ax25.txt. More
4211 information about digital amateur radio in general is on the WWW at
4212 http://www.tapr.org/tapr/html/pkthome.html .
4214 This driver is also available as a module ( = code which can be
4215 inserted in and removed from the running kernel whenever you want).
4216 The module will be called netrom.o. If you want to compile it as a
4217 module, say M here and read Documentation/modules.txt.
4219 Amateur Radio X.25 PLP (Rose)
4221 The Packet Layer Protocol (PLP) is a way to route packets over X.25
4222 connections in general and amateur radio AX.25 connections in
4223 particular, essentially an alternative to NET/ROM.
4225 A comprehensive listing of all the software for Linux amateur radio
4226 users as well as information about how to configure an AX.25 port is
4227 contained in the AX25-HOWTO, available from
4228 http://www.linuxdoc.org/docs.html#howto . You also might want to
4229 check out the file Documentation/networking/ax25.txt. More
4230 information about digital amateur radio in general is on the WWW at
4231 http://www.tapr.org/tapr/html/pkthome.html .
4233 This driver is also available as a module ( = code which can be
4234 inserted in and removed from the running kernel whenever you want).
4235 The module will be called rose.o. If you want to compile it as a
4236 module, say M here and read Documentation/modules.txt.
4238 Serial port KISS driver for AX.25
4240 KISS is a protocol used for the exchange of data between a computer
4241 and a Terminal Node Controller (a small embedded system commonly
4242 used for networking over AX.25 amateur radio connections; it
4243 connects the computer's serial port with the radio's microphone
4244 input and speaker output).
4246 Although KISS is less advanced than the 6pack protocol, it has
4247 the advantage that it is already supported by most modern TNCs
4248 without the need for a firmware upgrade.
4250 If you want to compile this driver as a module ( = code which can be
4251 inserted in and removed from the running kernel whenever you want),
4252 say M here and read Documentation/modules.txt. The module will be
4255 Serial port 6PACK driver for AX.25
4257 6pack is a transmission protocol for the data exchange between your
4258 PC and your TNC (the Terminal Node Controller acts as a kind of
4259 modem connecting your computer's serial port to your radio's
4260 microphone input and speaker output). This protocol can be used as
4261 an alternative to KISS for networking over AX.25 amateur radio
4262 connections, but it has some extended functionality.
4264 Note that this driver is still experimental and might cause
4265 problems. For details about the features and the usage of the
4266 driver, read Documentation/networking/6pack.txt.
4268 If you want to compile this driver as a module ( = code which can be
4269 inserted in and removed from the running kernel whenever you want),
4270 say M here and read Documentation/modules.txt. The module will be
4275 AX.25 is the protocol used for computer communication over amateur
4276 radio. If you say Y here, you will be able to send and receive AX.25
4277 traffic over Ethernet (also called "BPQ AX.25"), which could be
4278 useful if some other computer on your local network has a direct
4279 amateur radio connection.
4281 High-speed (DMA) SCC driver for AX.25
4283 This is a driver for high-speed SCC boards, i.e. those supporting
4284 DMA on one port. You usually use those boards to connect your
4285 computer to an amateur radio modem (such as the WA4DSY 56kbps
4286 modem), in order to send and receive AX.25 packet radio network
4289 Currently, this driver supports Ottawa PI/PI2, Paccomm/Gracilis
4290 PackeTwin, and S5SCC/DMA boards. They are detected automatically.
4291 If you have one of these cards, say Y here and read the AX25-HOWTO,
4292 available from http://www.linuxdoc.org/docs.html#howto .
4294 This driver can operate multiple boards simultaneously. If you
4295 compile it as a module (by saying M instead of Y), it will be called
4296 dmascc.o. If you don't pass any parameter to the driver, all
4297 possible I/O addresses are probed. This could irritate other devices
4298 that are currently not in use. You may specify the list of addresses
4299 to be probed by "dmascc=addr1,addr2,..." (when compiled into the
4300 kernel image) or "io=addr1,addr2,..." (when loaded as a module). The
4301 network interfaces will be called dmascc0 and dmascc1 for the board
4302 detected first, dmascc2 and dmascc3 for the second one, and so on.
4304 Before you configure each interface with ifconfig, you MUST set
4305 certain parameters, such as channel access timing, clock mode, and
4306 DMA channel. This is accomplished with a small utility program,
4307 dmascc_cfg, available at
4308 http://www.nt.tuwien.ac.at/~kkudielk/Linux/ . Please be sure to get
4309 at least version 1.27 of dmascc_cfg, as older versions will not
4310 work with the current driver.
4312 Z8530 SCC driver for AX.25
4314 These cards are used to connect your Linux box to an amateur radio
4315 in order to communicate with other computers. If you want to use
4316 this, read Documentation/networking/z8530drv.txt and the AX25-HOWTO,
4317 available from http://www.linuxdoc.org/docs.html#howto . Also
4318 make sure to say Y to "Amateur Radio AX.25 Level 2" support.
4320 If you want to compile this as a module ( = code which can be
4321 inserted in and removed from the running kernel whenever you want),
4322 say M here and read Documentation/modules.txt. The module will be
4325 additional delay for PA0HZP OptoSCC compatible boards
4327 Say Y here if you experience problems with the SCC driver not
4328 working properly; please read Documentation/networking/z8530drv.txt
4329 for details. If unsure, say N.
4331 #support for TRX that feedback the tx signal to rx
4334 ### Don't know what's going on here.
4338 YAM driver for AX.25
4340 The YAM is a modem for packet radio which connects to the serial
4341 port and includes some of the functions of a Terminal Node
4342 Controller. If you have one of those, say Y here.
4344 If you want to compile this as a module ( = code which can be
4345 inserted in and removed from the running kernel whenever you want),
4346 say M here and read Documentation/modules.txt.
4348 BAYCOM picpar and par96 driver for AX.25
4350 This is a driver for Baycom style simple amateur radio modems that
4351 connect to a parallel interface. The driver supports the picpar and
4352 par96 designs. To configure the driver, use the sethdlc utility
4353 available in the standard ax25 utilities package. For information on
4354 the modems, see http://www.baycom.de and the file
4355 Documentation/networking/baycom.txt.
4357 If you want to compile this driver as a module ( = code which can be
4358 inserted in and removed from the running kernel whenever you want),
4359 say M here and read Documentation/modules.txt. This is recommended.
4360 The module will be called baycom_par.o.
4362 BAYCOM EPP driver for AX.25
4364 This is a driver for Baycom style simple amateur radio modems that
4365 connect to a parallel interface. The driver supports the EPP
4366 designs. To configure the driver, use the sethdlc utility available
4367 in the standard ax25 utilities package. For information on the
4368 modems, see http://www.baycom.de and the file
4369 Documentation/networking/baycom.txt.
4371 If you want to compile this driver as a module ( = code which can be
4372 inserted in and removed from the running kernel whenever you want),
4373 say M here and read Documentation/modules.txt. This is recommended.
4374 The module will be called baycom_par.o.
4376 BAYCOM ser12 full duplex driver for AX.25
4377 CONFIG_BAYCOM_SER_FDX
4378 This is one of two drivers for Baycom style simple amateur radio
4379 modems that connect to a serial interface. The driver supports the
4380 ser12 design in full duplex mode. In addition, it allows the
4381 baudrate to be set between 300 and 4800 baud (however not all modems
4382 support all baudrates). This is the preferred driver. The next
4383 driver, "BAYCOM ser12 half duplex driver for AX.25" is the old
4384 driver and still provided in case this driver does not work with
4385 your serial interface chip. To configure the driver, use the sethdlc
4386 utility available in the standard ax25 utilities package. For
4387 information on the modems, see http://www.baycom.de and
4388 Documentation/networking/baycom.txt.
4390 If you want to compile this driver as a module ( = code which can be
4391 inserted in and removed from the running kernel whenever you want),
4392 say M here and read Documentation/modules.txt. This is recommended.
4393 The module will be called baycom_ser_fdx.o.
4395 BAYCOM ser12 half duplex driver for AX.25
4396 CONFIG_BAYCOM_SER_HDX
4397 This is one of two drivers for Baycom style simple amateur radio
4398 modems that connect to a serial interface. The driver supports the
4399 ser12 design in full duplex mode. This is the old driver. It is
4400 still provided in case your serial interface chip does not work with
4401 the full duplex driver. This driver is depreciated. To configure the
4402 driver, use the sethdlc utility available in the standard ax25
4403 utilities package. For information on the modems, see
4404 http://www.baycom.de and Documentation/networking/baycom.txt.
4406 If you want to compile this driver as a module ( = code which can be
4407 inserted in and removed from the running kernel whenever you want),
4408 say M here and read Documentation/modules.txt. This is recommended.
4409 The module will be called baycom_ser_hdx.o.
4411 Sound card modem driver for AX.25
4413 This experimental driver allows a standard Sound Blaster or
4414 WindowsSoundSystem compatible sound card to be used as a packet
4415 radio modem (NOT as a telephone modem!), to send digital traffic
4418 To configure the driver, use the sethdlc, smdiag and smmixer
4419 utilities available in the standard ax25 utilities package. For
4420 information on how to key the transmitter, see
4421 http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html and
4422 Documentation/networking/soundmodem.txt.
4424 If you want to compile this driver as a module ( = code which can be
4425 inserted in and removed from the running kernel whenever you want),
4426 say M here and read Documentation/modules.txt. This is recommended.
4427 The module will be called soundmodem.o.
4429 Sound card modem support for Sound Blaster and compatible cards
4430 CONFIG_SOUNDMODEM_SBC
4431 This option enables the soundmodem driver to use Sound Blaster and
4432 compatible cards. If you have a dual mode card (i.e. a WSS cards
4433 with a Sound Blaster emulation) you should say N here and Y to
4434 "Sound card modem support for WSS and Crystal cards", below, because
4435 this usually results in better performance. This option also
4436 supports SB16/32/64 in full duplex mode.
4438 Sound card modem support for WSS and Crystal cards
4439 CONFIG_SOUNDMODEM_WSS
4440 This option enables the soundmodem driver to use WindowsSoundSystem
4441 compatible cards. These cards feature a codec chip from either
4442 Analog Devices (such as AD1848, AD1845, AD1812) or Crystal
4443 Semiconductors (such as CS4248, CS423x). This option also supports
4444 the WSS full duplex operation which currently works with Crystal
4445 CS423x chips. If you don't need full duplex operation, do not enable
4446 it to save performance.
4448 Sound card modem support for 1200 baud AFSK modulation
4449 CONFIG_SOUNDMODEM_AFSK1200
4450 This option enables the soundmodem driver 1200 baud AFSK modem,
4451 compatible to popular modems using TCM3105 or AM7911. The
4452 demodulator requires about 12% of the CPU power of a Pentium 75 CPU
4455 Sound card modem support for 2400 baud AFSK modulation (7.3728MHz crystal)
4456 CONFIG_SOUNDMODEM_AFSK2400_7
4457 This option enables the soundmodem driver 2400 baud AFSK modem,
4458 compatible to TCM3105 modems (over-)clocked with a 7.3728MHz
4459 crystal. Note that the availability of this driver does _not_ imply
4460 that I recommend building such links. It is only here since users
4461 especially in eastern Europe have asked me to do so. In fact this
4462 modulation scheme has many disadvantages, mainly its incompatibility
4463 with many transceiver designs and the fact that the TCM3105 (if
4464 used) is operated widely outside its specifications.
4466 Sound card modem support for 2400 baud AFSK modulation (8MHz crystal)
4467 CONFIG_SOUNDMODEM_AFSK2400_8
4468 This option enables the soundmodem driver 2400 baud AFSK modem,
4469 compatible to TCM3105 modems (over-)clocked with an 8MHz crystal.
4470 Note that the availability of this driver does _not_ imply that I
4471 recommend building such links. It is only here since users
4472 especially in eastern Europe have asked me to do so. In fact this
4473 modulation scheme has many disadvantages, mainly its incompatibility
4474 with many transceiver designs and the fact that the TCM3105 (if
4475 used) is operated widely outside its specifications.
4477 Sound card modem support for 2666 baud AFSK modulation
4478 CONFIG_SOUNDMODEM_AFSK2666
4479 This option enables the soundmodem driver 2666 baud AFSK modem.
4480 This modem is experimental, and not compatible to anything
4483 Sound card modem support for 4800 baud 8PSK modulation
4484 CONFIG_SOUNDMODEM_PSK4800
4485 This option enables the soundmodem driver 4800 baud 8PSK modem.
4486 This modem is experimental, and not compatible to anything
4489 Sound card modem support for 4800 baud HAPN-1 modulation
4490 CONFIG_SOUNDMODEM_HAPN4800
4491 This option enables the soundmodem driver 4800 baud HAPN-1
4492 compatible modem. This modulation seems to be widely used 'down
4493 under' and in the Netherlands. Here, nobody uses it, so I could not
4494 test if it works. It is compatible to itself, however :-)
4496 Sound card modem support for 9600 baud FSK G3RUH modulation
4497 CONFIG_SOUNDMODEM_FSK9600
4498 This option enables the soundmodem driver 9600 baud FSK modem,
4499 compatible to the G3RUH standard. The demodulator requires about 4%
4500 of the CPU power of a Pentium 75 CPU per channel. You can say Y to
4501 both 1200 baud AFSK and 9600 baud FSK if you want (but obviously you
4502 can only use one protocol at a time, depending on what the other end
4505 CCITT X.25 Packet Layer (EXPERIMENTAL)
4507 X.25 is a set of standardized network protocols, similar in scope to
4508 frame relay; the one physical line from your box to the X.25 network
4509 entry point can carry several logical point-to-point connections
4510 (called "virtual circuits") to other computers connected to the X.25
4511 network. Governments, banks, and other organizations tend to use it
4512 to connect to each other or to form Wide Area Networks (WANs). Many
4513 countries have public X.25 networks. X.25 consists of two
4514 protocols: the higher level Packet Layer Protocol (PLP) (say Y here
4515 if you want that) and the lower level data link layer protocol LAPB
4516 (say Y to "LAPB Data Link Driver" below if you want that).
4518 You can read more about X.25 at http://www.sangoma.com/x25.htm and
4519 http://www.cisco.com/univercd/data/doc/software/11_0/rpcg/cx25.htm .
4520 Information about X.25 for Linux is contained in the files
4521 Documentation/networking/x25.txt and
4522 Documentation/networking/x25-iface.txt.
4524 One connects to an X.25 network either with a dedicated network card
4525 using the X.21 protocol (not yet supported by Linux) or one can do
4526 X.25 over a standard telephone line using an ordinary modem (say Y
4527 to "X.25 async driver" below) or over Ethernet using an ordinary
4528 Ethernet card and either the 802.2 LLC protocol (say Y to "802.2
4529 LLC" below) or LAPB over Ethernet (say Y to "LAPB Data Link Driver"
4530 and "LAPB over Ethernet driver" below).
4532 If you want to compile this driver as a module ( = code which can be
4533 inserted in and removed from the running kernel whenever you want),
4534 say M here and read Documentation/modules.txt. The module will be
4535 called x25.o. If unsure, say N.
4537 LAPB Data Link Driver (EXPERIMENTAL)
4539 Link Access Procedure, Balanced (LAPB) is the data link layer (i.e.
4540 the lower) part of the X.25 protocol. It offers a reliable
4541 connection service to exchange data frames with one other host, and
4542 it is used to transport higher level protocols (mostly X.25 Packet
4543 Layer, the higher part of X.25, but others are possible as well).
4544 Usually, LAPB is used with specialized X.21 network cards, but Linux
4545 currently supports LAPB only over Ethernet connections. If you want
4546 to use LAPB connections over Ethernet, say Y here and to "LAPB over
4547 Ethernet driver" below. Read
4548 Documentation/networking/lapb-module.txt for technical details.
4550 If you want to compile this driver as a module though ( = code which
4551 can be inserted in and removed from the running kernel whenever you
4552 want), say M here and read Documentation/modules.txt. The module
4553 will be called lapb.o. If unsure, say N.
4555 802.2 LLC (EXPERIMENTAL)
4557 This is a Logical Link Layer protocol used for X.25 connections over
4558 Ethernet, using ordinary Ethernet cards.
4560 802.1d Ethernet Bridging
4562 If you say Y here, then your Linux box will be able to act as an
4563 Ethernet bridge, which means that the different Ethernet segments it
4564 is connected to will appear as one Ethernet to the participants.
4565 Several such bridges can work together to create even larger
4566 networks of Ethernets using the IEEE 802.1 spanning tree algorithm.
4567 As this is a standard, Linux bridges will cooperate properly with
4568 other third party bridge products.
4570 In order to use the ethernet bridge, you'll need the bridge
4571 configuration tools; see Documentation/networking/bridge.txt for
4572 location. Please read the Bridge mini-HOWTO for more information.
4574 Note that if your box acts as a bridge, it probably contains several
4575 Ethernet devices, but the kernel is not able to recognize more than
4576 one at boot time without help; for details read the Ethernet-HOWTO,
4577 available from in http://www.linuxdoc.org/docs.html#howto .
4579 If you want to compile this code as a module ( = code which can be
4580 inserted in and removed from the running kernel whenever you want),
4581 say M here and read Documentation/modules.txt. The module will be
4588 The Packet protocol is used by applications which communicate
4589 directly with network devices without an intermediate network
4590 protocol implemented in the kernel, e.g. tcpdump. If you want them
4593 This driver is also available as a module called af_packet.o ( =
4594 code which can be inserted in and removed from the running kernel
4595 whenever you want). If you want to compile it as a module, say M
4596 here and read Documentation/modules.txt; if you use modprobe or
4597 kmod, you may also want to add "alias net-pf-17 af_packet" to
4602 Packet socket: mmapped IO
4604 If you say Y here, the Packet protocol driver will use an IO
4605 mechanism that results in faster communication.
4609 Kernel/User network link driver
4611 This driver allows for two-way communication between the kernel and
4612 user processes. It does so by creating a new socket family, PF_NETLINK.
4613 Over this socket, the kernel can send and receive datagrams carrying
4614 information. It is documented on many systems in netlink(7), a HOWTO is
4615 provided as well, for example on
4616 http://snafu.freedom.org/linux2.2/docs/netlink-HOWTO.html
4618 So far, the kernel uses this feature to publish some network related
4619 information if you say Y to "Routing messages", below. You also need
4620 to say Y here if you want to use arpd, a daemon that helps keep the
4621 internal ARP cache (a mapping between IP addresses and hardware
4622 addresses on the local network) small. The ethertap device, which
4623 lets user space programs read and write raw Ethernet frames, also
4624 needs the network link driver.
4630 If you say Y here, userspace programs can receive some network
4631 related routing information over the netlink. 'rtmon', supplied
4632 with the iproute2 package (ftp://ftp.inr.ac.ru), can read and
4633 interpret this data. Information sent to the kernel over this link
4636 Netlink device emulation
4638 This option will be removed soon. Any programs that want to use
4639 character special nodes like /dev/tap0 or /dev/route (all with major
4640 number 36) need this option, and need to be rewritten soon to use
4641 the real netlink socket.
4642 This is a backward compatibility option, choose Y for now.
4644 Asynchronous Transfer Mode (ATM)
4646 ATM is a high-speed networking technology for Local Area Networks
4647 and Wide Area Networks. It uses a fixed packet size and is
4648 connection oriented, allowing for the negotiation of minimum
4649 bandwidth requirements.
4651 In order to participate in an ATM network, your Linux box needs an
4652 ATM networking card. If you have that, say Y here and to the driver
4653 of your ATM card below.
4655 Note that you need a set of user-space programs to actually make use
4656 of ATM. See the file Documentation/networking/atm.txt for further
4659 Classical IP over ATM
4661 Classical IP over ATM for PVCs and SVCs, supporting InARP and
4662 ATMARP. If you want to communication with other IP hosts on your ATM
4663 network, you will typically either say Y here or to "LAN Emulation
4666 Do NOT send ICMP if no neighbour
4667 CONFIG_ATM_CLIP_NO_ICMP
4668 Normally, an "ICMP host unreachable" message is sent if a neighbour
4669 cannot be reached because there is no VC to it in the kernel's
4670 ATMARP table. This may cause problems when ATMARP table entries are
4671 briefly removed during revalidation. If you say Y here, packets to
4672 such neighbours are silently discarded instead.
4674 LAN Emulation (LANE) support
4676 LAN Emulation emulates services of existing LANs across an ATM
4677 network. Besides operating as a normal ATM end station client, Linux
4678 LANE client can also act as an proxy client bridging packets between
4679 ELAN and Ethernet segments. You need LANE if you want to try MPOA.
4681 Multi-Protocol Over ATM (MPOA) support
4683 Multi-Protocol Over ATM allows ATM edge devices such as routers,
4684 bridges and ATM attached hosts establish direct ATM VCs across
4685 subnetwork boundaries. These shortcut connections bypass routers
4686 enhancing overall network performance.
4690 ATM over TCP driver. Useful mainly for development and for
4691 experiments. If unsure, say N.
4693 Efficient Networks ENI155P
4695 Driver for the Efficient Networks ENI155p series and SMC ATM
4696 Power155 155 Mbps ATM adapters. Both, the versions with 512KB and
4697 2MB on-board RAM (Efficient calls them "C" and "S", respectively),
4698 and the FPGA and the ASIC Tonga versions of the board are supported.
4699 The driver works with MMF (-MF or ...F) and UTP-5 (-U5 or ...D)
4702 This driver is also available as a module. If you want to compile
4703 it as a module, say M here and read Documentation/modules.txt. The
4704 module will be called eni.o.
4706 Enable extended debugging
4707 CONFIG_ATM_ENI_DEBUG
4708 Extended debugging records various events and displays that list
4709 when an inconsistency is detected. This mechanism is faster than
4710 generally using printks, but still has some impact on performance.
4711 Note that extended debugging may create certain race conditions
4712 itself. Enable this ONLY if you suspect problems with the driver.
4714 Fine-tune burst settings
4715 CONFIG_ATM_ENI_TUNE_BURST
4716 In order to obtain good throughput, the ENI NIC can transfer
4717 multiple words of data per PCI bus access cycle. Such a multi-word
4718 transfer is called a burst.
4720 The default settings for the burst sizes are suitable for most PCI
4721 chipsets. However, in some cases, large bursts may overrun buffers
4722 in the PCI chipset and cause data corruption. In such cases, large
4723 bursts must be disabled and only (slower) small bursts can be used.
4724 The burst sizes can be set independently in the send (TX) and
4725 receive (RX) direction.
4727 Note that enabling many different burst sizes in the same direction
4728 may increase the cost of setting up a transfer such that the
4729 resulting throughput is lower than when using only the largest
4730 available burst size.
4732 Also, sometimes larger bursts lead to lower throughput, e.g. on an
4733 Intel 440FX board, a drop from 135 Mbps to 103 Mbps was observed
4734 when going from 8W to 16W bursts.
4736 Enable 16W TX bursts (discouraged)
4737 CONFIG_ATM_ENI_BURST_TX_16W
4738 Burst sixteen words at once in the send direction. This may work
4739 with recent PCI chipsets, but is known to fail with older chipsets.
4741 Enable 8W TX bursts (recommended)
4742 CONFIG_ATM_ENI_BURST_TX_8W
4743 Burst eight words at once in the send direction. This is the default
4746 Enable 4W TX bursts (optional)
4747 CONFIG_ATM_ENI_BURST_TX_4W
4748 Burst four words at once in the send direction. You may want to try
4749 this if you have disabled 8W bursts. Enabling 4W if 8W is also set
4750 may or may not improve throughput.
4752 Enable 2W TX bursts (optional)
4753 CONFIG_ATM_ENI_BURST_TX_2W
4754 Burst two words at once in the send direction. You may want to try
4755 this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or 8W
4756 are also set may or may not improve throughput.
4758 Enable 16W RX bursts (discouraged)
4759 CONFIG_ATM_ENI_BURST_RX_16W
4760 Burst sixteen words at once in the receive direction. This may work
4761 with recent PCI chipsets, but is known to fail with older chipsets.
4763 Enable 8W RX bursts (discouraged)
4764 CONFIG_ATM_ENI_BURST_RX_8W
4765 Burst eight words at once in the receive direction. This may work
4766 with recent PCI chipsets, but is known to fail with older chipsets,
4767 such as the Intel Neptune series.
4769 Enable 4W RX bursts (recommended)
4770 CONFIG_ATM_ENI_BURST_RX_4W
4771 Burst four words at once in the receive direction. This is the
4772 default setting. Enabling 4W if 8W is also set may or may not
4775 Enable 2W RX bursts (optional)
4776 CONFIG_ATM_ENI_BURST_RX_2W
4777 Burst two words at once in the receive direction. You may want to
4778 try this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or
4779 8W are also set may or may not improve throughput.
4781 ZeitNet ZN1221/ZN1225
4783 Driver for the ZeitNet ZN1221 (MMF) and ZN1225 (UTP-5) 155 Mbps ATM
4786 This driver is also available as a module. If you want to compile
4787 it as a module, say M here and read Documentation/modules.txt. The
4788 module will be called zatm.o.
4790 Enable extended debugging
4791 CONFIG_ATM_ZATM_DEBUG
4792 Extended debugging records various events and displays that list
4793 when an inconsistency is detected. This mechanism is faster than
4794 generally using printks, but still has some impact on performance.
4795 Note that extended debugging may create certain race conditions
4796 itself. Enable this ONLY if you suspect problems with the driver.
4798 Enable usec resolution timestamps
4799 CONFIG_ATM_ZATM_EXACT_TS
4800 The uPD98401 SAR chip supports a high-resolution timer (approx. 30
4801 MHz) that is used for very accurate reception timestamps. Because
4802 that timer overflows after 140 seconds, and also to avoid timer
4803 drift, time measurements need to be periodically synchronized with
4804 the normal system time. Enabling this feature will add some general
4805 overhead for timer synchronization and also per-packet overhead for
4808 IDT 77201/11 (NICStAR) (ForeRunnerLE)
4810 The NICStAR chipset family is used in a large number of ATM NICs for
4811 25 and for 155 Mbps, including IDT cards and the Fore ForeRunnerLE
4812 series. Say Y if you have one of those.
4814 This driver is also available as a module. If you want to compile
4815 it as a module, say M here and read Documentation/modules.txt. The
4816 module will be called nicstar.o.
4818 ForeRunner LE155 PHYsical layer
4819 CONFIG_ATM_NICSTAR_USE_SUNI
4820 Support for the S-UNI and compatible PHYsical layer chips. These are
4821 found in most 155Mbps NICStAR based ATM cards, namely in the
4822 ForeRunner LE155 cards. This driver provides detection of cable
4823 removal and reinsertion and provides some statistics. This driver
4824 doesn't have removal capability when compiled as a module, so if you
4825 need that capability don't include S-UNI support (it's not needed to
4826 make the card work).
4828 ForeRunner LE25 PHYsical layer
4829 CONFIG_ATM_NICSTAR_USE_IDT77105
4830 Support for the PHYsical layer chip in ForeRunner LE25 cards. In
4831 addition to cable removal/reinsertion detection, this driver allows
4832 you to control the loopback mode of the chip via a dedicated IOCTL.
4833 This driver is required for proper handling of temporary carrier
4834 loss, so if you have a 25Mbps NICStAR based ATM card you must say Y.
4836 Madge Ambassador (Collage PCI 155 Server)
4837 CONFIG_ATM_AMBASSADOR
4838 This is a driver for ATMizer based ATM card produced by Madge
4839 Networks Ltd. Say Y (or M to compile as a module named ambassador.o)
4840 here if you have one of these cards.
4842 Enable debugging messages
4843 CONFIG_ATM_AMBASSADOR_DEBUG
4844 Somewhat useful debugging messages are available. The choice of
4845 messages is controlled by a bitmap. This may be specified as a
4846 module argument (kernel command line argument as well?), changed
4847 dynamically using an ioctl (not yet) or changed by sending the
4848 string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
4849 drivers/atm/ambassador.h for the meanings of the bits in the mask.
4851 When active, these messages can have a significant impact on the
4852 speed of the driver, and the size of your syslog files! When
4853 inactive, they will have only a modest impact on performance.
4855 Madge Horizon [Ultra] (Collage PCI 25 and Collage PCI 155 Client)
4857 This is a driver for the Horizon chipset ATM adapter cards once
4858 produced by Madge Networks Ltd. Say Y (or M to compile as a module
4859 named horizon.o) here if you have one of these cards.
4861 Enable debugging messages
4862 CONFIG_ATM_HORIZON_DEBUG
4863 Somewhat useful debugging messages are available. The choice of
4864 messages is controlled by a bitmap. This may be specified as a
4865 module argument (kernel command line argument as well?), changed
4866 dynamically using an ioctl (not yet) or changed by sending the
4867 string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
4868 drivers/atm/horizon.h for the meanings of the bits in the mask.
4870 When active, these messages can have a significant impact on the
4871 speed of the driver, and the size of your syslog files! When
4872 inactive, they will have only a modest impact on performance.
4874 Interphase ATM PCI x575/x525/x531
4876 This is a driver for the Interphase (i)ChipSAR adapter cards
4877 which include a variety of variants in term of the size of the
4878 control memory (128K-1KVC, 512K-4KVC), the size of the packet
4879 memory (128K, 512K, 1M), and the PHY type (Single/Multi mode OC3,
4880 UTP155, UTP25, DS3 and E3). Go to:
4881 www.iphase.com/products/ClassSheet.cfm?ClassID=ATM
4882 for more info about the cards. Say Y (or M to compile as a module
4883 named iphase.o) here if you have one of these cards.
4885 See the file Documentation/networking/iphase.txt for further
4888 Enable debugging messages
4890 Somewhat useful debugging messages are available. The choice of
4891 messages is controlled by a bitmap. This may be specified as a
4892 module argument (kernel command line argument as well?), changed
4893 dynamically using an ioctl (Get the debug utility, iadbg, from
4894 ftp.iphase.com/pub/atm/pci). See the file drivers/atm/iphase.h
4895 for the meanings of the bits in the mask.
4897 When active, these messages can have a significant impact on the
4898 speed of the driver, and the size of your syslog files! When
4899 inactive, they will have only a modest impact on performance.
4901 Linux telephony support
4903 Say Y here if you have a telephony card, which for example allows
4904 you to use a regular phone for voice-over-IP applications.
4906 Note: this has nothing to do with modems. You do not need to say Y
4907 here in order to be able to use a modem under Linux.
4909 This support is also available as a module. If you want to compile
4910 it as a module, say M here and read Documentation/modules.txt. The
4911 module will be called phonedev.o.
4913 QuickNet Internet LineJack/PhoneJack support
4915 Say M if you have a telephony card manufactured by Quicknet
4916 Technologies, Inc. These include the Internet PhoneJACK and
4917 Internet LineJACK Telephony Cards. You will get a module called
4920 For the ISA versions of these products, you can configure the
4921 cards using the isapnp tools (pnpdump/isapnp) or you can use the
4922 isapnp support. Please read Documentation/telephony/ixj.txt.
4924 For more information on these cards, see Quicknet's web site at:
4925 http://www.quicknet.net/ .
4927 If you do not have any Quicknet telephony cards, you can safely
4930 FORE Systems 200E-series
4931 CONFIG_ATM_FORE200E_MAYBE
4932 This is a driver for the FORE Systems 200E-series ATM adapter
4933 cards. It simultaneously supports PCA-200E and SBA-200E models
4934 on PCI and SBUS hosts. Say Y (or M to compile as a module
4935 named fore_200e.o) here if you have one of these ATM adapters.
4937 Note that the driver will actually be compiled only if you
4938 additionally enable the support for PCA-200E and/or SBA-200E
4941 See the file Documentation/networking/fore200e.txt for further
4944 Enable PCA-200E card support on PCI-based hosts
4945 CONFIG_ATM_FORE200E_PCA
4946 Say Y here if you want your PCA-200E cards to be probed.
4948 Use default PCA-200E firmware
4949 CONFIG_ATM_FORE200E_PCA_DEFAULT_FW
4950 Use the default PCA-200E firmware data shipped with the driver.
4952 Normal users do not have to deal with the firmware stuff, so
4953 they should say Y here.
4955 Pathname of user-supplied binary firmware
4956 CONFIG_ATM_FORE200E_PCA_FW
4957 This defines the pathname of an alternative PCA-200E binary
4958 firmware image supplied by the user. This pathname may be
4959 absolute or relative to the drivers/atm directory.
4961 The driver comes with an adequate firmware image, so normal users do
4962 not have to supply an alternative one. They just say Y to "Use
4963 default PCA-200E firmware" instead.
4965 Enable SBA-200E card support on SBUS-based hosts
4966 CONFIG_ATM_FORE200E_SBA
4967 Say Y here if you want your SBA-200E cards to be probed.
4969 Use default SBA-200E firmware
4970 CONFIG_ATM_FORE200E_SBA_DEFAULT_FW
4971 Use the default SBA-200E firmware data shipped with the driver.
4973 Normal users do not have to deal with the firmware stuff, so
4974 they should say Y here.
4976 Pathname of user-supplied binary firmware
4977 CONFIG_ATM_FORE200E_SBA_FW
4978 This defines the pathname of an alternative SBA-200E binary
4979 firmware image supplied by the user. This pathname may be
4980 absolute or relative to the drivers/atm directory.
4982 The driver comes with an adequate firmware image, so normal users do
4983 not have to supply an alternative one. They just say Y to "Use
4984 default SBA-200E firmware", above.
4986 Maximum number of tx retries
4987 CONFIG_ATM_FORE200E_TX_RETRY
4988 Specifies the number of times the driver attempts to transmit
4989 a message before giving up, if the transmit queue of the ATM card
4990 is transiently saturated.
4992 Saturation of the transmit queue may occur only under extreme
4993 conditions, e.g. when a fast host continuously submits very small
4994 frames (<64 bytes) or raw AAL0 cells (48 bytes) to the ATM adapter.
4996 Note that under common conditions, it is unlikely that you encounter
4997 a saturation of the transmit queue, so the retry mechanism never
5000 Debugging level (0-3)
5001 CONFIG_ATM_FORE200E_DEBUG
5002 Specifies the level of debugging messages issued by the driver.
5003 The verbosity of the driver increases with the value of this
5006 When active, these messages can have a significant impact on
5007 the performances of the driver, and the size of your syslog files!
5008 Keep the debugging level to 0 during normal operations.
5012 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CDROM or
5013 any other SCSI device under Linux, say Y and make sure that you know
5014 the name of your SCSI host adapter (the card inside your computer
5015 that "speaks" the SCSI protocol, also called SCSI controller),
5016 because you will be asked for it.
5018 You also need to say Y here if you want support for the parallel
5019 port version of the 100 MB IOMEGA ZIP drive.
5021 Please read the SCSI-HOWTO, available from
5022 http://www.linuxdoc.org/docs.html#howto . The
5023 SCSI-Programming-HOWTO contains information about how to add or
5024 remove an SCSI device from a running Linux machine without
5027 This driver is also available as a module ( = code which can be
5028 inserted in and removed from the running kernel whenever you want).
5029 The module will be called scsi_mod.o. If you want to compile it as a
5030 module, say M here and read Documentation/modules.txt and
5031 Documentation/scsi.txt. However, do not compile this as a module if
5032 your root file system (the one containing the directory /) is
5033 located on a SCSI device.
5037 If you want to use a SCSI hard disk or the SCSI or parallel port
5038 version of the IOMEGA ZIP drive under Linux, say Y and read the
5039 SCSI-HOWTO, the Disk-HOWTO and the Multi-Disk-HOWTO, available from
5040 http://www.linuxdoc.org/docs.html#howto . This is NOT for SCSI
5043 This driver is also available as a module ( = code which can be
5044 inserted in and removed from the running kernel whenever you want).
5045 The module will be called sd_mod.o. If you want to compile it as a
5046 module, say M here and read Documentation/modules.txt and
5047 Documentation/scsi.txt. Do not compile this driver as a module if
5048 your root file system (the one containing the directory /) is
5049 located on a SCSI disk. In this case, do not compile the driver for
5050 your SCSI host adapter (below) as a module either.
5053 CONFIG_SD_EXTRA_DEVS
5054 This controls the amount of additional space allocated in tables for
5055 drivers that are loaded as modules after the kernel is booted. In
5056 the event that the SCSI core itself was loaded as a module, this
5057 value is the number of additional disks that can be loaded after the
5058 first host driver is loaded.
5060 Admittedly this isn't pretty, but there are tons of race conditions
5061 involved with resizing the internal arrays on the fly. Someday this
5062 flag will go away, and everything will work automatically.
5064 If you don't understand what's going on, go with the default.
5068 If you want to use a SCSI tape drive under Linux, say Y and read the
5069 SCSI-HOWTO, available from
5070 http://www.linuxdoc.org/docs.html#howto , and
5071 drivers/scsi/README.st in the kernel source. This is NOT for SCSI
5074 This driver is also available as a module ( = code which can be
5075 inserted in and removed from the running kernel whenever you want).
5076 The module will be called st.o. If you want to compile it as a
5077 module, say M here and read Documentation/modules.txt and
5078 Documentation/scsi.txt .
5082 If you want to use a SCSI CDROM under Linux, say Y and read the
5083 SCSI-HOWTO and the CDROM-HOWTO at
5084 http://www.linuxdoc.org/docs.html#howto . Also make sure to say Y
5085 or M to "ISO 9660 CDROM file system support" later.
5087 This driver is also available as a module ( = code which can be
5088 inserted in and removed from the running kernel whenever you want).
5089 The module will be called sr_mod.o. If you want to compile it as a
5090 module, say M here and read Documentation/modules.txt and
5091 Documentation/scsi.txt .
5094 CONFIG_SR_EXTRA_DEVS
5095 This controls the amount of additional space allocated in tables for
5096 drivers that are loaded as modules after the kernel is booted. In
5097 the event that the SCSI core itself was loaded as a module, this
5098 value is the number of additional CDROMs that can be loaded after
5099 the first host driver is loaded.
5101 Admittedly this isn't pretty, but there are tons of race conditions
5102 involved with resizing the internal arrays on the fly. Someday this
5103 flag will go away, and everything will work automatically.
5105 If you don't understand what's going on, go with the default.
5107 Enable vendor-specific extensions (for SCSI CDROM)
5108 CONFIG_BLK_DEV_SR_VENDOR
5109 This enables the usage of vendor specific SCSI commands. This is
5110 required to support multisession CDs with old NEC/TOSHIBA cdrom
5111 drives (and HP Writers). If you have such a drive and get the first
5112 session only, try saying Y here; everybody else says N.
5114 SCSI generic support
5116 If you want to use SCSI scanners, synthesizers or CD-writers or just
5117 about anything having "SCSI" in its name other than hard disks,
5118 CDROMs or tapes, say Y here. These won't be supported by the kernel
5119 directly, so you need some additional software which knows how to
5120 talk to these devices using the SCSI protocol:
5122 For scanners, look at SANE (http://www.mostang.com/sane). For CD
5123 writer software look at cdrecord
5124 (http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html)
5125 and for burning a "disk at once": cdrdao
5126 (http://www.ping.de/sites/daneb/cdrdao.html). Cdparanoia is a high
5127 quality digital reader of audio CDs (http://www.xiph.org/paranoia).
5128 For other devices, it's possible that you'll have to write the
5129 driver software yourself. Please read the file
5130 Documentation/scsi-generic.txt for more information.
5132 If you want to compile this as a module ( = code which can be
5133 inserted in and removed from the running kernel whenever you want),
5134 say M here and read Documentation/modules.txt and
5135 Documentation/scsi.txt. The module will be called sg.o. If unsure,
5138 Debug new queueing code for SCSI
5139 CONFIG_SCSI_DEBUG_QUEUES
5140 This option turns on a lot of additional consistency checking for
5141 the new queueing code. This will adversely affect performance, but
5142 it is likely that bugs will be caught sooner if this is turned on.
5143 This will typically cause the kernel to panic if an error is
5144 detected, but it would have probably crashed if the panic weren't
5145 there. Comments/questions/problems to linux-scsi mailing list
5146 please. See http://www.andante.org/scsi_queue.html for more
5147 up-to-date information.
5149 Probe all LUNs on each SCSI device
5150 CONFIG_SCSI_MULTI_LUN
5151 If you have a SCSI device that supports more than one LUN (Logical
5152 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
5153 can say Y here to force the SCSI driver to probe for multiple LUNs.
5154 A SCSI device with multiple LUNs acts logically like multiple SCSI
5155 devices. The vast majority of SCSI devices have only one LUN, and
5156 so most people can say N here and should in fact do so, because it
5159 Verbose SCSI error reporting (kernel size +=12K)
5160 CONFIG_SCSI_CONSTANTS
5161 The error messages regarding your SCSI hardware will be easier to
5162 understand if you say Y here; it will enlarge your kernel by about
5163 12 KB. If in doubt, say Y.
5165 SCSI logging facility
5167 This turns on a logging facility that can be used to debug a number
5168 of SCSI related problems.
5170 If you say Y here, no logging output will appear by default, but you
5171 can enable logging by saying Y to "/proc file system support" and
5172 "Sysctl support" below and executing the command
5174 echo "scsi log token [level]" > /proc/scsi/scsi
5176 at boot time after the /proc file system has been mounted.
5178 There are a number of things that can be used for 'token' (you can
5179 find them in the source: drivers/scsi/scsi.c), and this allows you
5180 to select the types of information you want, and the level allows
5181 you to select the level of verbosity.
5183 If you say N here, it may be harder to track down some types of SCSI
5184 problems. If you say Y here your kernel will be somewhat larger, but
5185 there should be no noticeable performance impact as long as you have
5188 AdvanSys SCSI support
5189 CONFIG_SCSI_ADVANSYS
5190 This is a driver for all SCSI host adapters manufactured by
5191 AdvanSys. It is documented in the kernel source in
5192 drivers/scsi/advansys.c.
5194 This driver is also available as a module ( = code which can be
5195 inserted in and removed from the running kernel whenever you want).
5196 If you want to compile it as a module, say M here and read
5197 Documentation/modules.txt. The module will be called advansys.o.
5199 Adaptec AHA152X/2825 support
5201 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
5202 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
5203 must be manually specified in this case.
5205 It is explained in section 3.3 of the SCSI-HOWTO, available from
5206 http://www.linuxdoc.org/docs.html#howto . You might also want to
5207 read the file drivers/scsi/README.aha152x.
5209 This driver is also available as a module ( = code which can be
5210 inserted in and removed from the running kernel whenever you want).
5211 The module will be called aha152x.o. If you want to compile it as a
5212 module, say M here and read Documentation/modules.txt.
5214 Adaptec AHA1542 support
5216 This is support for a SCSI host adapter. It is explained in section
5217 3.4 of the SCSI-HOWTO, available from
5218 http://www.linuxdoc.org/docs.html#howto . Note that Trantor was
5219 purchased by Adaptec, and some former Trantor products are being
5220 sold under the Adaptec name. If it doesn't work out of the box, you
5221 may have to change some settings in drivers/scsi/aha1542.h.
5223 If you want to compile this as a module ( = code which can be
5224 inserted in and removed from the running kernel whenever you want),
5225 say M here and read Documentation/modules.txt. The module will be
5228 Adaptec AHA1740 support
5230 This is support for a SCSI host adapter. It is explained in section
5231 3.5 of the SCSI-HOWTO, available from
5232 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
5233 of the box, you may have to change some settings in
5234 drivers/scsi/aha1740.h.
5236 This driver is also available as a module ( = code which can be
5237 inserted in and removed from the running kernel whenever you want).
5238 The module will be called aha1740.o. If you want to compile it as a
5239 module, say M here and read Documentation/modules.txt.
5241 Adaptec AIC7xxx chipset SCSI controller support
5243 This is support for the various aic7xxx based Adaptec SCSI
5244 controllers. These include the 274x EISA cards; 284x VLB cards;
5245 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
5246 motherboard based SCSI controllers from Adaptec. It does not support
5247 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
5248 support them. It does not support the 2920 cards from Adaptec that
5249 use the Future Domain SCSI controller chip. For those cards, you
5250 need the "Future Domain 16xx SCSI support" driver.
5252 In general, if the controller is based on an Adaptec SCSI controller
5253 chip from the aic777x series or the aic78xx series, this driver
5254 should work. The only exception is the 7810 which is specifically
5255 not supported (that's the RAID controller chip on the AAA-13x
5258 Note that the AHA2920 SCSI host adapter is *not* supported by this
5259 driver; choose "Future Domain 16xx SCSI support" instead if you have
5262 Information on the configuration options for this controller can be
5263 found by checking the help file for each of the available
5264 configuration options. You should read drivers/scsi/README.aic7xxx
5265 at a minimum before contacting the maintainer with any questions.
5266 The SCSI-HOWTO, available from
5267 http://www.linuxdoc.org/docs.html#howto , can also be of great
5270 If you want to compile this driver as a module ( = code which can be
5271 inserted in and removed from the running kernel whenever you want),
5272 say M here and read Documentation/modules.txt. The module will be
5275 Enable or Disable Tagged Command Queueing by default
5276 CONFIG_AIC7XXX_TCQ_ON_BY_DEFAULT
5277 This option causes the aic7xxx driver to attempt to use Tagged
5278 Command Queueing (TCQ) on all devices that claim to support it.
5280 TCQ is a feature of SCSI-2 which improves performance: the host
5281 adapter can send several SCSI commands to a device's queue even if
5282 previous commands haven't finished yet. Because the device is
5283 intelligent, it can optimize its operations (like head positioning)
5284 based on its own request queue. Not all devices implement this
5287 If you say Y here, you can still turn off TCQ on troublesome devices
5288 with the use of the tag_info boot parameter. See the file
5289 drivers/scsi/README.aic7xxx for more information on that and other
5290 aic7xxx setup commands. If this option is turned off, you may still
5291 enable TCQ on known good devices by use of the tag_info boot
5294 If you are unsure about your devices then it is safest to say N
5297 However, TCQ can increase performance on some hard drives by as much
5298 as 50% or more, so it is recommended that if you say N here, you
5299 should at least read the README.aic7xxx file so you will know how to
5300 enable this option manually should your drives prove to be safe in
5303 Conversely, certain drives are known to lock up or cause bus resets
5304 when TCQ is enabled on them. If you have a Western Digital
5305 Enterprise SCSI drive for instance, then don't even bother to enable
5306 TCQ on it as the drive will become unreliable, and it will actually
5309 Default number of TCQ commands per device
5310 CONFIG_AIC7XXX_CMDS_PER_DEVICE
5311 Specify the number of commands you would like to allocate per SCSI
5312 device when Tagged Command Queueing (TCQ) is enabled on that device.
5314 Reasonable figures are in the range of 8 to 24 commands per device,
5315 but depending on hardware could be increased or decreased from that
5316 figure. If the number is too high for any particular device, the
5317 driver will automatically compensate usually after only 10 minutes
5318 of uptime. It will not hinder performance if some of your devices
5319 eventually have their command depth reduced, but is a waste of
5320 memory if all of your devices end up reducing this number down to a
5321 more reasonable figure.
5323 NOTE: Certain very broken drives are known to lock up when given
5324 more commands than they like to deal with. Quantum Fireball drives
5325 are the most common in this category. For the Quantum Fireball
5326 drives it is suggested to use no more than 8 commands per device.
5330 Collect statistics to report in /proc
5331 CONFIG_AIC7XXX_PROC_STATS
5332 This option tells the driver to keep track of how many commands have
5333 been sent to each particular device and report that information to
5334 the user via the /proc/scsi/aic7xxx/n file, where n is the number of
5335 the aic7xxx controller you want the information on. This adds a
5336 small amount of overhead to each and every SCSI command the aic7xxx
5337 driver handles, so if you aren't really interested in this
5338 information, it is best to leave it disabled. This will only work if
5339 you also say Y to "/proc file system support", below.
5343 Delay in seconds after SCSI bus reset
5344 CONFIG_AIC7XXX_RESET_DELAY
5345 This sets how long the driver will wait after resetting the SCSI bus
5346 before attempting to communicate with the devices on the SCSI bus
5347 again. This delay will be used during the reset phase at bootup time
5348 as well as after any reset that might occur during normal operation.
5349 Reasonable numbers range anywhere from 5 to 15 seconds depending on
5350 your devices. DAT tape drives are notorious for needing more time
5351 after a bus reset to be ready for the next command, but most hard
5352 drives and CD-ROM devices are ready in only a few seconds. This
5353 option has a maximum upper limit of 20 seconds to avoid bad
5354 interactions between the aic7xxx driver and the rest of the Linux
5355 kernel. The default value has been reduced to 5 seconds. If this
5356 doesn't work with your hardware, try increasing this value.
5358 IBM ServeRAID Support
5360 This is support for the IBM ServeRAID hardware RAID controllers.
5362 Please consult the SCSI-HOWTO, available from
5363 http://www.linuxdoc.org/docs.html#howto .
5365 You can build this driver as a module ( = code which can be
5366 inserted in and removed from the running kernel whenever you want),
5367 but only a single instance may be loaded. If you want to compile it
5368 as a module, say M here and read Documentation/modules.txt. The
5369 module will be called ips.o.
5371 BusLogic SCSI support
5372 CONFIG_SCSI_BUSLOGIC
5373 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
5374 Adapters. Consult the SCSI-HOWTO, available from
5375 http://www.linuxdoc.org/docs.html#howto , and the files
5376 README.BusLogic and README.FlashPoint in drivers/scsi for more
5377 information. If this driver does not work correctly without
5378 modification, please contact the author, Leonard N. Zubkoff, by
5379 email to lnz@dandelion.com.
5381 You can also build this driver as a module ( = code which can be
5382 inserted in and removed from the running kernel whenever you want),
5383 but only a single instance may be loaded. If you want to compile it
5384 as a module, say M here and read Documentation/modules.txt. The
5385 module will be called BusLogic.o.
5387 Omit BusLogic SCSI FlashPoint support
5388 CONFIG_SCSI_OMIT_FLASHPOINT
5389 This option allows you to omit the FlashPoint support from the
5390 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
5391 substantial, so users of MultiMaster Host Adapters may wish to omit
5394 DMX3191D SCSI support
5395 CONFIG_SCSI_DMX3191D
5396 This is support for Domex DMX3191D SCSI Host Adapters.
5398 This driver is also available as a module ( = code which can be
5399 inserted in and removed from the running kernel whenever you want).
5400 The module will be called dmx3191d.o. If you want to compile it as a
5401 module, say M here and read Documentation/modules.txt.
5403 DTC3180/3280 SCSI support
5405 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
5406 the SCSI-HOWTO, available from
5407 http://www.linuxdoc.org/docs.html#howto , and the file
5408 drivers/scsi/README.dtc3x80.
5410 This driver is also available as a module ( = code which can be
5411 inserted in and removed from the running kernel whenever you want).
5412 The module will be called dtc.o. If you want to compile it as a
5413 module, say M here and read Documentation/modules.txt.
5415 EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti, Alphatronix) support
5416 CONFIG_SCSI_EATA_DMA
5417 This is support for the EATA-DMA protocol compliant SCSI Host
5418 Adapters like the SmartCache III/IV, SmartRAID controller families
5419 and the DPT PM2011B and PM2012B controllers.
5421 Note that this driver is obsolete; if you have one of the above SCSI
5422 Host Adapters, you should normally say N here and Y to "EATA
5423 ISA/EISA/PCI support", below. Please read the SCSI-HOWTO, available
5424 from http://www.linuxdoc.org/docs.html#howto .
5426 This driver is also available as a module ( = code which can be
5427 inserted in and removed from the running kernel whenever you want).
5428 The module will be called eata_dma.o. If you want to compile it as a
5429 module, say M here and read Documentation/modules.txt.
5431 EATA-PIO (old DPT PM2001, PM2012A) support
5432 CONFIG_SCSI_EATA_PIO
5433 This driver supports all EATA-PIO protocol compliant SCSI Host
5434 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
5435 host adapters could also use this driver but are discouraged from
5436 doing so, since this driver only supports hard disks and lacks
5437 numerous features. You might want to have a look at the SCSI-HOWTO,
5438 available from http://www.linuxdoc.org/docs.html#howto .
5440 If you want to compile this as a module ( = code which can be
5441 inserted in and removed from the running kernel whenever you want),
5442 say M here and read Documentation/modules.txt. The module will be
5445 UltraStor 14F/34F support
5447 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
5448 The source at drivers/scsi/u14-34f.c contains some information about
5449 this hardware. If the driver doesn't work out of the box, you may
5450 have to change some settings in drivers/scsi/u14-34f.c. Read the
5451 SCSI-HOWTO, available from
5452 http://www.linuxdoc.org/docs.html#howto . Note that there is also
5453 another driver for the same hardware: "UltraStor SCSI support",
5454 below. You should say Y to both only if you want 24F support as
5457 This driver is also available as a module ( = code which can be
5458 inserted in and removed from the running kernel whenever you want).
5459 The module will be called u14-34f.o. If you want to compile it as a
5460 module, say M here and read Documentation/modules.txt.
5462 enable elevator sorting
5463 CONFIG_SCSI_U14_34F_LINKED_COMMANDS
5464 This option enables elevator sorting for all probed SCSI disks and
5465 CDROMs. It definitely reduces the average seek distance when doing
5466 random seeks, but this does not necessarily result in a noticeable
5467 performance improvement: your mileage may vary...
5469 The safe answer is N.
5471 maximum number of queued commands
5472 CONFIG_SCSI_U14_34F_MAX_TAGS
5473 This specifies how many SCSI commands can be maximally queued for
5474 each probed SCSI device. You should reduce the default value of 8
5475 only if you have disks with buggy or limited tagged command support.
5476 Minimum is 2 and maximum is 14. This value is also the window size
5477 used by the elevator sorting option above. The effective value used
5478 by the driver for each probed SCSI device is reported at boot time.
5480 Future Domain 16xx SCSI/AHA-2920A support
5481 CONFIG_SCSI_FUTURE_DOMAIN
5482 This is support for Future Domain's 16-bit SCSI host adapters
5483 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
5484 other adapters based on the Future Domain chipsets (Quantum
5485 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
5486 It is explained in section 3.7 of the SCSI-HOWTO, available from
5487 http://www.linuxdoc.org/docs.html#howto .
5489 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
5490 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
5491 controller support"). This Future Domain driver works with the older
5492 Adaptec AHA-2920A boards with a Future Domain chip on them.
5494 This driver is also available as a module ( = code which can be
5495 inserted in and removed from the running kernel whenever you want).
5496 The module will be called fdomain.o. If you want to compile it as a
5497 module, say M here and read Documentation/modules.txt.
5499 Future Domain MCS-600/700 SCSI support
5501 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
5502 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
5503 is identical to the MCS 700 and hence also supported by this driver.
5504 This driver also supports the Reply SB16/SCSI card (the SCSI part).
5505 It supports multiple adapters in the same system.
5507 This driver is also available as a module ( = code which can be
5508 inserted in and removed from the running kernel whenever you want).
5509 The module will be called fd_mcs.o. If you want to compile it as a
5510 module, say M here and read Documentation/modules.txt.
5512 Generic NCR5380/53c400 SCSI support
5513 CONFIG_SCSI_GENERIC_NCR5380
5514 This is the generic NCR family of SCSI controllers, not to be
5515 confused with the NCR 53c7 or 8xx controllers. It is explained in
5516 section 3.8 of the SCSI-HOWTO, available from
5517 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
5518 of the box, you may have to change some settings in
5519 drivers/scsi/g_NCR5380.h.
5521 This driver is also available as a module ( = code which can be
5522 inserted in and removed from the running kernel whenever you want).
5523 The module will be called g_NCR5380.o. If you want to compile it as
5524 a module, say M here and read Documentation/modules.txt.
5526 Enable NCR53c400 extensions
5527 CONFIG_SCSI_GENERIC_NCR53C400
5528 This enables certain optimizations for the NCR53c400 SCSI cards. You
5529 might as well try it out. Note that this driver will only probe for
5530 the Trantor T130B in its default configuration; you might have to
5531 pass a command line option to the kernel at boot time if it doesn't
5532 detect your card. See the file drivers/scsi/README.g_NCR5380 for
5535 NCR5380/53c400 mapping method (use Port for T130B)
5536 CONFIG_SCSI_G_NCR5380_PORT
5537 The NCR5380 and NCR53c400 SCSI controllers come in two varieties:
5538 port or memory mapped. You should know what you have. The most
5539 common card, Trantor T130B, uses port mapped mode.
5541 NCR53c7,8xx SCSI support
5542 CONFIG_SCSI_NCR53C7xx
5543 This is a driver for the 53c7 and 8xx NCR family of SCSI
5544 controllers, not to be confused with the NCR 5380 controllers. It is
5545 explained in section 3.8 of the SCSI-HOWTO, available from
5546 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
5547 of the box, you may have to change some settings in
5548 drivers/scsi/53c7,8xx.h. Please read drivers/scsi/README.ncr53c7xx
5549 for the available boot time command line options.
5551 Note: there is another driver for the 53c8xx family of controllers
5552 ("NCR53C8XX SCSI support" below). If you want to use them both, you
5553 need to say M to both and build them as modules, but only one may be
5554 active at a time. If you have a 53c8xx board, it's better to use the
5557 This driver is also available as a module ( = code which can be
5558 inserted in and removed from the running kernel whenever you want).
5559 The module will be called 53c7,8xx.o. If you want to compile it as a
5560 module, say M here and read Documentation/modules.txt.
5562 always negotiate synchronous transfers
5563 CONFIG_SCSI_NCR53C7xx_sync
5564 In general, this is good; however, it is a bit dangerous since there
5565 are some broken SCSI devices out there. Take your chances. Safe bet
5568 allow FAST-SCSI [10MHz]
5569 CONFIG_SCSI_NCR53C7xx_FAST
5570 This will enable 10MHz FAST-SCSI transfers with your host
5571 adapter. Some systems have problems with that speed, so it's safest
5575 CONFIG_SCSI_NCR53C7xx_DISCONNECT
5576 This enables the disconnect/reconnect feature of the NCR SCSI
5577 controller. When you say Y here, a slow SCSI device will not lock
5578 the SCSI bus while processing a request, allowing simultaneous use
5579 of e.g. a SCSI hard disk and SCSI tape or CD-ROM drive, and
5580 providing much better performance when using slow and fast SCSI
5581 devices at the same time. Some devices, however, do not operate
5582 properly with this option enabled, and will cause your SCSI system
5583 to hang, which might cause a system crash. The safe answer
5584 therefore is to say N.
5586 NCR53C8XX SCSI support
5587 CONFIG_SCSI_NCR53C8XX
5588 This is the BSD ncr driver adapted to Linux for the NCR53C8XX family
5589 of PCI-SCSI controllers. This driver supports parity checking,
5590 tagged command queuing and fast synchronous data transfers up to 80
5591 MB/s with wide FAST-40 LVD devices and controllers.
5593 Recent versions of the 53C8XX chips are better supported by the
5594 option "SYM53C8XX SCSI support", below.
5596 Note: there is yet another driver for the 53c8xx family of
5597 controllers ("NCR53c7,8xx SCSI support" above). If you want to use
5598 them both, you need to say M to both and build them as modules, but
5599 only one may be active at a time. If you have a 53c8xx board, you
5600 probably do not want to use the "NCR53c7,8xx SCSI support".
5602 Please read drivers/scsi/README.ncr53c8xx for more information.
5604 SYM53C8XX SCSI support
5605 CONFIG_SCSI_SYM53C8XX
5606 This driver supports all the features of recent 53C8XX chips (used
5607 in PCI SCSI controllers), notably the hardware phase mismatch
5608 feature of the SYM53C896.
5610 Older versions of the 53C8XX chips are not supported by this
5611 driver. If your system uses either a 810 rev. < 16, a 815, or a 825
5612 rev. < 16 PCI SCSI processor, you must use the generic NCR53C8XX
5613 driver ("NCR53C8XX SCSI support" above) or configure both the
5614 NCR53C8XX and this SYM53C8XX drivers either as module or linked to
5617 When both drivers are linked into the kernel, the SYM53C8XX driver
5618 is called first at initialization and you can use the 'excl=ioaddr'
5619 driver boot option to exclude attachment of adapters by the
5620 SYM53C8XX driver. For example, entering
5621 'sym53c8xx=excl:0xb400,excl=0xc000' at the lilo prompt prevents
5622 adapters at io address 0xb400 and 0xc000 from being attached by the
5623 SYM53C8XX driver, thus allowing the NCR53C8XX driver to attach them.
5624 The 'excl' option is also supported by the NCR53C8XX driver.
5626 Please read drivers/scsi/README.ncr53c8xx for more information.
5628 synchronous data transfers frequency
5629 CONFIG_SCSI_NCR53C8XX_SYNC
5630 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
5631 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers are
5632 respectively the maximum data transfer rates in mega-transfers per
5633 second for each class. For example, a FAST-20 Wide 16 device is able
5634 to transfer data at 20 million 16 bit packets per second for a total
5637 You may specify 0 if you want to only use asynchronous data
5638 transfers. This is the safest and slowest option. Otherwise, specify
5639 a value between 5 and 80, depending on the capability of your SCSI
5640 controller. The higher the number, the faster the data transfer.
5641 Note that 80 should normally be ok since the driver decreases the
5642 value automatically according to the controller's capabilities.
5644 Your answer to this question is ignored for controllers with NVRAM,
5645 since the driver will get this information from the user set-up. It
5646 also can be overridden using a boot setup option, as follows
5647 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
5648 for FAST-20 synchronous data transfer (20 mega-transfers per
5651 The normal answer therefore is not to go with the default but to
5652 select the maximum value 80 allowing the driver to use the maximum
5653 value supported by each controller. If this causes problems with
5654 your SCSI devices, you should come back and decrease the value.
5656 There is no safe option other than using good cabling, right
5657 terminations and SCSI conformant devices.
5660 CONFIG_SCSI_NCR53C8XX_IOMAPPED
5661 If you say Y here, the driver will use normal IO, as opposed to
5662 memory mapped IO. Memory mapped IO has less latency than normal IO
5663 and works for most Intel-based hardware. Under Linux/Alpha only
5664 normal IO is currently supported by the driver and so, this option
5665 has no effect on those systems.
5667 The normal answer therefore is N; try Y only if you encounter SCSI
5670 not allow targets to disconnect
5671 CONFIG_SCSI_NCR53C8XX_NO_DISCONNECT
5672 This option is only provided for safety if you suspect some SCSI
5673 device of yours to not support properly the target-disconnect
5674 feature. In that case, you would say Y here. In general however, to
5675 not allow targets to disconnect is not reasonable if there is more
5676 than 1 device on a SCSI bus. The normal answer therefore is N.
5678 default tagged command queue depth
5679 CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS
5680 "Tagged command queuing" is a feature of SCSI-2 which improves
5681 performance: the host adapter can send several SCSI commands to a
5682 device's queue even if previous commands haven't finished yet.
5683 Because the device is intelligent, it can optimize its operations
5684 (like head positioning) based on its own request queue. Some SCSI
5685 devices don't implement this properly; if you want to disable this
5686 feature, enter 0 or 1 here (it doesn't matter which).
5688 The default value is 8 and should be supported by most hard disks.
5689 This value can be overridden from the boot command line using the
5690 'tags' option as follows (example):
5691 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
5692 4, set queue depth to 16 for target 2 and target 3 on controller 0
5693 and set queue depth to 10 for target 0 / lun 2 on controller 1.
5695 The normal answer therefore is to go with the default 8 and to use
5696 a boot command line option for devices that need to use a different
5697 command queue depth.
5699 There is no safe option other than using good SCSI devices.
5701 maximum number of queued commands
5702 CONFIG_SCSI_NCR53C8XX_MAX_TAGS
5703 This option allows you to specify the maximum number of commands
5704 that can be queued to any device, when tagged command queuing is
5705 possible. The default value is 32. Minimum is 2, maximum is 64.
5706 Modern hard disks are able to support 64 tags and even more, but
5707 do not seem to be faster when more than 32 tags are being used.
5709 So, the normal answer here is to go with the default value 32 unless
5710 you are using very large hard disks with large cache (>= 1 MB) that
5711 are able to take advantage of more than 32 tagged commands.
5713 There is no safe option and the default answer is recommended.
5715 assume boards are SYMBIOS compatible (EXPERIMENTAL)
5716 CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT
5717 This option allows you to enable some features depending on GPIO
5718 wiring. These General Purpose Input/Output pins can be used for
5719 vendor specific features or implementation of the standard SYMBIOS
5720 features. Genuine SYMBIOS controllers use GPIO0 in output for
5721 controller LED and GPIO3 bit as a flag indicating
5722 singled-ended/differential interface. The Tekram DC-390U/F boards
5723 uses a different GPIO wiring.
5725 Your answer to this question is ignored if all your controllers have
5726 NVRAM, since the driver is able to detect the board type from the
5729 If all the controllers in your system are genuine SYMBIOS boards or
5730 use BIOS and drivers from SYMBIOS, you would want to say Y here,
5731 otherwise N. N is the safe answer.
5733 enable profiling statistics gathering
5734 CONFIG_SCSI_NCR53C8XX_PROFILE
5735 This option allows you to enable profiling information gathering.
5736 These statistics are not very accurate due to the low frequency
5737 of the kernel clock (100 Hz on i386) and have performance impact
5738 on systems that use very fast devices.
5740 The normal answer therefore is N.
5742 include support for the NCR PQS/PDS SCSI card
5743 CONFIG_SCSI_NCR53C8XX_PQS_PDS
5744 Say Y here if you have a special SCSI adapter produced by NCR
5745 corporation called a PCI Quad SCSI or PCI Dual SCSI. You do not need
5746 this if you do not have one of these adapters. However, since this
5747 device is detected as a specific PCI device, this option is quite
5750 The common answer here is N, but answering Y is safe.
5754 This is support for the IBM SCSI adapter found in many of the PS/2
5755 series computers. These machines have an MCA bus, so you need to
5756 answer Y to "MCA support" as well and read Documentation/mca.txt.
5758 If the adapter isn't found during boot (a common problem for models
5759 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
5760 option, where <pun> is the id of the SCSI subsystem (usually 7, but
5761 if that doesn't work check your reference diskette). Owners of model
5762 95 with a LED-matrix-display can in addition activate some activity
5763 info like under OS/2, but more informative, by setting
5764 'ibmmcascsi=display' as an additional kernel parameter. Try "man
5765 bootparam" or see the documentation of your boot loader about how to
5766 pass options to the kernel.
5768 If you want to compile this driver as a module ( = code which can be
5769 inserted in and removed from the running kernel whenever you want),
5770 say M here and read Documentation/modules.txt. The module will be
5774 CONFIG_IBMMCA_SCSI_ORDER_STANDARD
5775 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
5776 are assigned to the drive letters, starting with the lowest SCSI-id
5777 (physical number -- pun) to be drive C:, as seen from DOS and
5778 similar operating systems. When looking into papers describing the
5779 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
5780 The SCSI-standard follows a hardware-hierarchy which says that id 7
5781 has the highest priority and id 0 the lowest. Therefore, the host
5782 adapters are still today everywhere placed as SCSI-id 7 by default.
5783 In the SCSI-standard, the drive letters express the priority of the
5784 disk. C: should be the hard disk, or a partition on it, with the
5785 highest priority. This must therefore be the disk with the highest
5786 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
5787 original definition of the SCSI-standard as also industrial- and
5788 process-control-machines, like VME-CPUs running under realtime-OSs
5789 (e.g. LynxOS, OS9) do.
5791 If you like to run Linux on your MCA-machine with the same
5792 assignment of hard disks as seen from e.g. DOS or OS/2 on your
5793 machine, which is in addition conformant to the SCSI-standard, you
5794 must say Y here. This is also necessary for MCA-Linux users who want
5795 to keep downward compatibility to older releases of the
5796 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
5799 If you like to have the lowest SCSI-id assigned as drive C:, as
5800 modern SCSI-BIOSes do, which does not conform to the standard, but
5801 is widespread and common in the PC-world of today, you must say N
5802 here. If unsure, say Y.
5804 Reset SCSI-devices at boot time
5805 CONFIG_IBMMCA_SCSI_DEV_RESET
5806 By default, SCSI-devices are reset when the machine is powered on.
5807 However, some devices exist, like special-control-devices,
5808 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
5809 not reset when switched on. If you say Y here, each device connected
5810 to your SCSI-bus will be issued a reset-command after it has been
5811 probed, while the kernel is booting. This may cause problems with
5812 more modern devices, like hard disks, which do not appreciate these
5813 reset commands, and can cause your system to hang. So say Y only if
5814 you know that one of your older devices needs it; N is the safe
5817 NCR 53C9x MCA support
5818 CONFIG_SCSI_MCA_53C9X
5819 Some Microchannel machines, notably the NCR 35xx line, use a SCSI
5820 controller based on the NCR 53C94. This driver will allow use of
5821 the controller on the 3550, and very possibly others.
5823 If you want to compile this as a module (= code which can be
5824 inserted and removed from the running kernel whenever you want), say
5825 M here and read Documentation/modules.txt. The module will be called
5828 Always IN2000 SCSI support
5830 This is support for an ISA bus SCSI host adapter. You'll find more
5831 information in drivers/scsi/in2000.readme. If it doesn't work out of
5832 the box, you may have to change the jumpers for IRQ or address
5835 If you want to compile this as a module ( = code which can be
5836 inserted in and removed from the running kernel whenever you want),
5837 say M here and read Documentation/modules.txt. The module will be
5840 Initio 91XXU(W) SCSI support
5842 This is support for the Initio 91XXU(W) SCSI host adapter. Please
5843 read the SCSI-HOWTO, available from
5844 http://www.linuxdoc.org/docs.html#howto .
5846 If you want to compile this as a module ( = code which can be
5847 inserted in and removed from the running kernel whenever you want),
5848 say M here and read Documentation/modules.txt. The module will be
5853 This is support for a SCSI host adapter. It is explained in section
5854 3.10 of the SCSI-HOWTO, available from
5855 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
5856 of the box, you may have to change some settings in
5857 drivers/scsi/pas16.h.
5859 This driver is also available as a module ( = code which can be
5860 inserted in and removed from the running kernel whenever you want).
5861 The module will be called pas16.o. If you want to compile it as a
5862 module, say M here and read Documentation/modules.txt.
5864 Initio INI-A100U2W SCSI support
5866 This is support for the Initio INI-A100U2W SCSI host adapter. Please
5867 read the SCSI-HOWTO, available from
5868 http://www.linuxdoc.org/docs.html#howto .
5870 If you want to compile this as a module ( = code which can be
5871 inserted in and removed from the running kernel whenever you want),
5872 say M here and read Documentation/modules.txt. The module will be
5877 This is support for the PCI2000I EIDE interface card which acts as a
5878 SCSI host adapter. Please read the SCSI-HOWTO, available from
5879 http://www.linuxdoc.org/docs.html#howto .
5881 This driver is also available as a module called pci2000.o ( = code
5882 which can be inserted in and removed from the running kernel
5883 whenever you want). If you want to compile it as a module, say M
5884 here and read Documentation/modules.txt.
5887 CONFIG_SCSI_PCI2220I
5888 This is support for the PCI2220i EIDE interface card which acts as a
5889 SCSI host adapter. Please read the SCSI-HOWTO, available from
5890 http://www.linuxdoc.org/docs.html#howto .
5892 This driver is also available as a module called pci2220i.o ( = code
5893 which can be inserted in and removed from the running kernel
5894 whenever you want). If you want to compile it as a module, say M
5895 here and read Documentation/modules.txt.
5899 This is support for the PSI240i EIDE interface card which acts as a
5900 SCSI host adapter. Please read the SCSI-HOWTO, available from
5901 http://www.linuxdoc.org/docs.html#howto .
5903 This driver is also available as a module called psi240i.o ( = code
5904 which can be inserted in and removed from the running kernel
5905 whenever you want). If you want to compile it as a module, say M
5906 here and read Documentation/modules.txt.
5908 Qlogic FAS SCSI support
5909 CONFIG_SCSI_QLOGIC_FAS
5910 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
5911 FastSCSI! cards as well as any other card based on the FASXX chip
5912 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
5914 This driver does NOT support the PCI versions of these cards. The
5915 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
5916 SCSI support"), below.
5918 Information about this driver is contained in
5919 drivers/scsi/README.qlogicfas. You should also read the SCSI-HOWTO,
5920 available from http://www.linuxdoc.org/docs.html#howto .
5922 This driver is also available as a module ( = code which can be
5923 inserted in and removed from the running kernel whenever you want).
5924 The module will be called qlogicfas.o. If you want to compile it as
5925 a module, say M here and read Documentation/modules.txt.
5927 Qlogic ISP SCSI support (EXPERIMENTAL)
5928 CONFIG_SCSI_QLOGIC_ISP
5929 This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
5930 IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
5931 card is supported by the "AM53/79C974 PCI SCSI" driver).
5933 If you say Y here, make sure to choose "BIOS" at the question "PCI
5936 Please read the file drivers/scsi/README.qlogicisp. You should also
5937 read the SCSI-HOWTO, available from
5938 http://www.linuxdoc.org/docs.html#howto .
5940 This driver is also available as a module ( = code which can be
5941 inserted in and removed from the running kernel whenever you want).
5942 The module will be called qlogicisp.o. If you want to compile it as
5943 a module, say M here and read Documentation/modules.txt.
5945 Qlogic ISP FC SCSI support
5946 CONFIG_SCSI_QLOGIC_FC
5947 This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
5949 This driver is also available as a module ( = code which can be
5950 inserted in and removed from the running kernel whenever you want).
5951 The module will be called qlogicfc.o. If you want to compile it as
5952 a module, say M here and read Documentation/modules.txt.
5954 Qlogic QLA 1280 SCSI support
5955 CONFIG_SCSI_QLOGIC_1280
5956 Say Y if you have a QLogic ISP1x80/1x160 SCSI host adapter.
5958 This driver is also available as a module ( = code which can be
5959 inserted in and removed from the running kernel whenever you want).
5960 The module will be called qla1280.o. If you want to compile it as
5961 a module, say M here and read Documentation/modules.txt.
5963 Seagate ST-02 and Future Domain TMC-8xx SCSI support
5965 These are 8-bit SCSI controllers; the ST-01 is also supported by
5966 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
5967 available from http://www.linuxdoc.org/docs.html#howto . If it
5968 doesn't work out of the box, you may have to change some settings in
5969 drivers/scsi/seagate.h.
5971 This driver is also available as a module ( = code which can be
5972 inserted in and removed from the running kernel whenever you want).
5973 The module will be called seagate.o. If you want to compile it as a
5974 module, say M here and read Documentation/modules.txt.
5976 Trantor T128/T128F/T228 SCSI support
5978 This is support for a SCSI host adapter. It is explained in section
5979 3.11 of the SCSI-HOWTO, available from
5980 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
5981 of the box, you may have to change some settings in
5982 drivers/scsi/t128.h. Note that Trantor was purchased by Adaptec, and
5983 some former Trantor products are being sold under the Adaptec name.
5985 This driver is also available as a module ( = code which can be
5986 inserted in and removed from the running kernel whenever you want).
5987 The module will be called t128.o. If you want to compile it as a
5988 module, say M here and read Documentation/modules.txt.
5990 UltraStor SCSI support
5991 CONFIG_SCSI_ULTRASTOR
5992 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
5993 adapter family. This driver is explained in section 3.12 of the
5994 SCSI-HOWTO, available from
5995 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
5996 of the box, you may have to change some settings in
5997 drivers/scsi/ultrastor.h.
5999 Note that there is also another driver for the same hardware:
6000 "UltraStor 14F/34F support", above.
6002 If you want to compile this as a module ( = code which can be
6003 inserted in and removed from the running kernel whenever you want),
6004 say M here and read Documentation/modules.txt. The module will be
6007 7000FASST SCSI support
6008 CONFIG_SCSI_7000FASST
6009 This driver supports the Western Digital 7000 SCSI host adapter
6010 family. Some information is in the source: drivers/scsi/wd7000.c.
6012 This driver is also available as a module ( = code which can be
6013 inserted in and removed from the running kernel whenever you
6014 want). The module will be called wd7000.o. If you want to compile it
6015 as a module, say M here and read Documentation/modules.txt.
6019 This driver supports the ACARD 870U/W SCSI host adapter.
6021 This driver is also available as a module ( = code which can be
6022 inserted in and removed from the running kernel whenever you want).
6023 The module will be called atp870u.o. If you want to compile it as a
6024 module, say M here and read Documentation/modules.txt.
6026 EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support
6028 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
6029 ISA and all EISA i/o addresses are probed looking for the "EATA"
6030 signature. If you chose "BIOS" at the question "PCI access mode",
6031 the addresses of all the PCI SCSI controllers reported by the PCI
6032 subsystem are probed as well.
6034 You want to read the start of drivers/scsi/eata.c and the
6035 SCSI-HOWTO, available from
6036 http://www.linuxdoc.org/docs.html#howto .
6038 Note that there is also another driver for the same hardware
6039 available: "EATA-DMA support". You should say Y to only one of them.
6041 If you want to compile this as a module ( = code which can be
6042 inserted in and removed from the running kernel whenever you want),
6043 say M here and read Documentation/modules.txt. The module will be
6046 enable tagged command queuing
6047 CONFIG_SCSI_EATA_TAGGED_QUEUE
6048 This is a feature of SCSI-2 which improves performance: the host
6049 adapter can send several SCSI commands to a device's queue even if
6050 previous commands haven't finished yet. Most EATA adapters negotiate
6051 this feature automatically with the device, even if your answer is
6052 N. The safe answer is N.
6054 enable elevator sorting
6055 CONFIG_SCSI_EATA_LINKED_COMMANDS
6056 This option enables elevator sorting for all probed SCSI disks and
6057 CDROMs. It definitely reduces the average seek distance when doing
6058 random seeks, but this does not necessarily result in a noticeable
6059 performance improvement: your mileage may vary...
6060 The safe answer is N.
6062 maximum number of queued commands
6063 CONFIG_SCSI_EATA_MAX_TAGS
6064 This specifies how many SCSI commands can be maximally queued for
6065 each probed SCSI device. You should reduce the default value of 16
6066 only if you have disks with buggy or limited tagged command support.
6067 Minimum is 2 and maximum is 62. This value is also the window size
6068 used by the elevator sorting option above. The effective value used
6069 by the driver for each probed SCSI device is reported at boot time.
6071 NCR53c406a SCSI support
6072 CONFIG_SCSI_NCR53C406A
6073 This is support for the NCR53c406a SCSI host adapter. For user
6074 configurable parameters, check out drivers/scsi/NCR53c406.c in the
6075 kernel source. Also read the SCSI-HOWTO, available from
6076 http://www.linuxdoc.org/docs.html#howto .
6078 If you want to compile this driver as a module ( = code which can be
6079 inserted in and removed from the running kernel whenever you want),
6080 say M here and read Documentation/modules.txt. The module will be
6083 Symbios Logic sym53c416 support
6084 CONFIG_SCSI_SYM53C416
6085 This is support for the sym53c416 SCSI host adapter, the SCSI
6086 adapter that comes with some HP scanners. This driver requires that
6087 the sym53c416 is configured first using some sort of pnp
6088 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
6089 are using isapnp then you need to compile this driver as a module
6090 and then load it using insmod after isapnp has run. The parameters
6091 of the configured card(s) should be passed to the driver. The format
6094 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
6096 There is support for up to four adapters. If you want to compile
6097 this driver as a module ( = code which can be inserted in and
6098 removed from the running kernel whenever you want), say M here and
6099 read Documentation/modules.txt. The module will be called
6102 Simple 53c710 SCSI support (Compaq, NCR machines)
6104 This is a simple driver for NCR53c710 based SCSI host adapters.
6106 More complex drivers for this chip are available ("NCR53c7,8xx SCSI
6107 support", above), but they require that the scsi chip be able to do
6108 DMA block moves between memory and on-chip registers, which can
6109 cause problems under certain conditions. This driver is designed to
6110 avoid these problems and is intended to work with any Intel machines
6111 using 53c710 chips, including various Compaq and NCR machines.
6113 Please read the comments at the top of the file
6114 drivers/scsi/sim710.c for more information.
6116 If you want to compile this driver as a module ( = code which can be
6117 inserted in and removed from the running kernel whenever you want),
6118 say M here and read Documentation/modules.txt. The module will be
6121 Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support
6123 This driver supports PCI SCSI host adapters based on the Am53C974A
6124 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
6125 PCscsi/PCnet (Am53/79C974) solutions.
6127 Documentation can be found in drivers/scsi/README.tmscsim.
6129 Note that this driver does NOT support Tekram DC390W/U/F, which are
6130 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
6131 Also note that there is another generic Am53C974 driver,
6132 "AM53/79C974 PCI SCSI support" below. You can pick either one.
6134 If you want to compile this driver as a module ( = code which can be
6135 inserted in and removed from the running kernel whenever you want),
6136 say M here and read Documentation/modules.txt. The module will be
6139 Omit support for other Am53/79C974 based SCSI adapters
6140 CONFIG_SCSI_DC390T_NOGENSUPP
6141 If you say N here, the DC390(T) SCSI driver relies on the DC390
6142 EEPROM to get initial values for its settings, such as speed,
6143 termination, etc. If it can't find this EEPROM, it will use defaults
6144 or the user supplied boot/module parameters. For details on driver
6145 configuration see drivers/scsi/README.tmscsim.
6147 If you say Y here and if no EEPROM is found, the driver gives up and
6148 thus only supports Tekram DC390(T) adapters. This can be useful if
6149 you have a DC390(T) and another Am53C974 based adapter, which, for
6150 some reason, you want to drive with the other AM53C974 driver.
6154 AM53/79C974 PCI SCSI support
6155 CONFIG_SCSI_AM53C974
6156 This is support for the AM53/79C974 SCSI host adapters. Please read
6157 drivers/scsi/README.AM53C974 for details. Also, the SCSI-HOWTO,
6158 available from http://www.linuxdoc.org/docs.html#howto , is for
6161 Note that there is another driver for AM53C974 based adapters:
6162 "Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support", above. You
6163 can pick either one.
6165 If you want to compile this driver as a module ( = code which can be
6166 inserted in and removed from the running kernel whenever you want),
6167 say M here and read Documentation/modules.txt. The module will be
6170 AMI MegaRAID support
6171 CONFIG_SCSI_MEGARAID
6172 This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490
6173 and 467 SCSI host adapters.
6175 If you want to compile this driver as a module ( = code which can be
6176 inserted in and removed from the running kernel whenever you want),
6177 say M here and read Documentation/modules.txt. The module will be
6180 GDT SCSI Disk Array Controller support
6182 This is a driver for all SCSI Disk Array Controllers (EISA/ISA/PCI)
6183 manufactured by ICP vortex. It is documented in the kernel source in
6184 drivers/scsi/gdth.c and drivers/scsi/gdth.h.
6186 This driver is also available as a module ( = code which can be
6187 inserted in and removed from the running kernel whenever you want).
6188 If you want to compile it as a module, say M here and read
6189 Documentation/modules.txt.
6191 IOMEGA parallel port (ppa - older drives)
6193 This driver supports older versions of IOMEGA's parallel port ZIP
6194 drive (a 100 MB removable media device).
6196 Note that you can say N here if you have the SCSI version of the ZIP
6197 drive: it will be supported automatically if you said Y to the
6198 generic "SCSI disk support", above.
6200 If you have the ZIP Plus drive or a more recent parallel port ZIP
6201 drive (if the supplied cable with the drive is labeled "AutoDetect")
6202 then you should say N here and Y to "IOMEGA parallel port (imm -
6203 newer drives)", below.
6205 For more information about this driver and how to use it you should
6206 read the file drivers/scsi/README.ppa. You should also read the
6207 SCSI-HOWTO, which is available from
6208 http://www.linuxdoc.org/docs.html#howto . If you use this driver,
6209 you will still be able to use the parallel port for other tasks,
6210 such as a printer; it is safe to compile both drivers into the
6213 This driver is also available as a module which can be inserted in
6214 and removed from the running kernel whenever you want. To compile
6215 this driver as a module, say M here and read
6216 Documentation/modules.txt. The module will be called ppa.o.
6218 IOMEGA parallel port (imm - newer drives)
6220 This driver supports newer versions of IOMEGA's parallel port ZIP
6221 drive (a 100 MB removable media device).
6223 Note that you can say N here if you have the SCSI version of the ZIP
6224 drive: it will be supported automatically if you said Y to the
6225 generic "SCSI disk support", above.
6227 If you have the ZIP Plus drive or a more recent parallel port ZIP
6228 drive (if the supplied cable with the drive is labeled "AutoDetect")
6229 then you should say Y here; if you have an older ZIP drive, say N
6230 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
6232 For more information about this driver and how to use it you should
6233 read the file drivers/scsi/README.ppa. You should also read the
6234 SCSI-HOWTO, which is available from
6235 http://www.linuxdoc.org/docs.html#howto . If you use this driver,
6236 you will still be able to use the parallel port for other tasks,
6237 such as a printer; it is safe to compile both drivers into the
6240 This driver is also available as a module which can be inserted in
6241 and removed from the running kernel whenever you want. To compile
6242 this driver as a module, say M here and read
6243 Documentation/modules.txt. The module will be called imm.o.
6245 Force the Iomega ZIP drivers to use EPP-16
6246 CONFIG_SCSI_IZIP_EPP16
6247 EPP (Enhanced Parallel Port) is a standard for parallel ports which
6248 allows them to act as expansion buses that can handle up to 64
6251 Some parallel port chipsets are slower than their motherboard, and
6252 so we have to control the state of the chipset's FIFO queue every
6253 now and then to avoid data loss. This will be done if you say Y
6256 Generally, saying Y is the safe option and slows things down a bit.
6258 Assume slow parallel port control register
6259 CONFIG_SCSI_IZIP_SLOW_CTR
6260 Some parallel ports are known to have excessive delays between
6261 changing the parallel port control register and good data being
6262 available on the parallel port data/status register. This option
6263 forces a small delay (1.0 usec to be exact) after changing the
6264 control register to let things settle out. Enabling this option may
6265 result in a big drop in performance but some very old parallel ports
6266 (found in 386 vintage machines) will not work properly.
6268 Generally, saying N is fine.
6270 Parallel port SCSI device support
6272 There are many external CD-ROM and disk devices that connect through
6273 your computer's parallel port. Lots of them are actually SCSI
6274 devices using a parallel port SCSI adapter. This option enables the
6275 ppSCSI subsystem which contains drivers for many of these external
6276 drives. You may also want to look at CONFIG_PARIDE (Parallel port
6277 IDE device support).
6279 If you built ppSCSI support into your kernel, you may still build
6280 the individual protocol modules and high-level drivers as loadable
6281 modules. If you build this support as a module, it will be called
6284 To use the ppSCSI support, you must say Y or M here and also to at
6285 least one protocol driver (e.g. "Shuttle EPST adapter", "Iomega VPI0
6286 adapter", "Shining ScarSCI adapter" etc.).
6288 Adaptec APA-348 adapter
6290 This option enables support for the APA-348 adapter from Adaptec
6291 (also known as Trantor T348). If you build this as a module it will
6294 Adaptec APA-358 adapter
6296 This option enables support for the APA-358 adapter from Adaptec
6297 (also known as Trantor T358). If you build this as a module it will
6302 This option enables support for the Iomega VPI0 adapter found in the
6303 original ZIP-100 drives and the Jaz Traveller. If you build this as
6304 a module it will be called vpi0.o.
6306 OnSpec 90c26 adapter
6307 CONFIG_PPSCSI_ONSCSI
6308 This option enables support for the OnSpec 90c26 in its SCSI adapter
6309 mode. If you build this as a module it will be called onscsi.o.
6311 Shining SparSCI adapter
6312 CONFIG_PPSCSI_SPARCSI
6313 This option enables support for the WBS-11A parallel port SCSI
6314 adapter. This adapter has been marketed by LinkSys as the
6315 "ParaSCSI+" and by Shining Technologies as the "SparCSI". If you
6316 build this as a module it will be called sparcsi.o.
6318 Shuttle EPSA-2 adapter
6320 This option enables support for the Shuttle Technologies EPSA2
6321 parallel port SCSI adapter. EPAS2 is a predecessor to the EPST. If
6322 you build this as a module it will be called epsa2.o.
6324 Shuttle EPST adapter
6326 This option enables support for the Shuttle Technologies EPST
6327 parallel port SCSI adapter. If you build this as a module is will
6330 SCSI Debug host simulator. (EXPERIMENTAL)
6332 This is a host adapter simulator that can be programmed to simulate
6333 a large number of conditions that could occur on a real bus. The
6334 advantage is that many hard to reproduce problems can be tested in a
6335 controlled environment where there is reduced risk of losing
6336 important data. This is primarily of use to people trying to debug
6337 the middle and upper layers of the SCSI subsystem. If unsure, say N.
6339 Fibre Channel support and FC4 SCSI support
6341 Fibre Channel is a high speed serial protocol mainly used to
6342 connect large storage devices to the computer; it is compatible with
6343 and intended to replace SCSI.
6345 This is an experimental support for storage arrays connected to your
6346 computer using optical fibre cables and the "X3.269-199X Fibre
6347 Channel Protocol for SCSI" specification. If you want to use this,
6348 you need to say Y here and to "SCSI support" as well as to the
6349 drivers for the storage array itself and for the interface adapter
6350 such as SOC or SOC+. This subsystem could even serve for IP
6351 networking, with some code extensions.
6357 Serial Optical Channel is an interface card with one or two Fibre
6358 Optic ports, each of which can be connected to a disk array. Note
6359 that if you have older firmware in the card, you'll need the
6360 microcode from the Solaris driver to make it work.
6362 This support is also available as a module called soc.o ( = code
6363 which can be inserted in and removed from the running kernel
6364 whenever you want). If you want to compile it as a module, say M
6365 here and read Documentation/modules.txt.
6367 Sun SOC+ (aka SOCAL)
6369 Serial Optical Channel Plus is an interface card with up to two
6370 Fibre Optic ports. This card supports FC Arbitrated Loop (usually
6371 A5000 or internal FC disks in E[3-6]000 machines through the
6372 Interface Board). You'll probably need the microcode from the
6373 Solaris driver to make it work.
6375 This support is also available as a module called socal.o ( = code
6376 which can be inserted in and removed from the running kernel
6377 whenever you want). If you want to compile it as a module, say M
6378 here and read Documentation/modules.txt.
6380 SparcSTORAGE Array 100 and 200 series
6382 If you never bought a disk array made by Sun, go with N.
6384 This support is also available as a module called pluto.o ( = code
6385 which can be inserted in and removed from the running kernel
6386 whenever you want). If you want to compile it as a module, say M
6387 here and read Documentation/modules.txt.
6389 Sun Enterprise Network Array (A5000 and EX500)
6391 This driver drives FC-AL disks connected through a Fibre Channel
6392 card using the drivers/fc4 layer (currently only SOCAL). The most
6393 common is either A5000 array or internal disks in E[3-6]000
6396 This support is also available as a module called fcal.o ( = code
6397 which can be inserted in and removed from the running kernel
6398 whenever you want). If you want to compile it as a module, say M
6399 here and read Documentation/modules.txt. If unsure, say N.
6402 CONFIG_SCSI_ACORNSCSI_3
6403 This enables support for the Acorn SCSI card (aka30). If you have an
6404 Acorn system with one of these, say Y. If unsure, say N.
6406 Acorn SCSI tagged queue support
6407 CONFIG_SCSI_ACORNSCSI_TAGGED_QUEUE
6408 Say Y here to enable tagged queuing support on the Acorn SCSI card.
6410 This is a feature of SCSI-2 which improves performance: the host
6411 adapter can send several SCSI commands to a device's queue even if
6412 previous commands haven't finished yet. Some SCSI devices don't
6413 implement this properly, so the safe answer is N.
6415 Acorn SCSI Synchronous transfers support
6416 CONFIG_SCSI_ACORNSCSI_SYNC
6417 Say Y here to enable synchronous transfer negotiation with all
6418 targets on the Acorn SCSI card.
6420 In general, this improves performance; however some SCSI devices
6421 don't implement it properly, so the safe answer is N.
6425 This enables support for the Oak SCSI card. If you have an Acorn
6426 system with one of these, say Y. If unsure, say N.
6428 Cumana SCSI I support
6429 CONFIG_SCSI_CUMANA_1
6430 This enables support for the Cumana SCSI I card. If you have an
6431 Acorn system with one of these, say Y. If unsure, say N.
6433 Cumana SCSI II support (EXPERIMENTAL)
6434 CONFIG_SCSI_CUMANA_2
6435 This enables support for the Cumana SCSI II card. If you have an
6436 Acorn system with one of these, say Y. If unsure, say N.
6440 This enables support for the EcoSCSI card -- a small card that sits
6441 in the Econet socket. If you have an Acorn system with one of these,
6442 say Y. If unsure, say N.
6444 EESOX SCSI support (EXPERIMENTAL)
6445 CONFIG_SCSI_EESOXSCSI
6446 This enables support for the EESOX SCSI card. If you have an Acorn
6447 system with one of these, say Y, otherwise say N.
6449 Powertec SCSI support (EXPERIMENTAL)
6450 CONFIG_SCSI_POWERTECSCSI
6451 This enables support for the Powertec SCSI card on Acorn systems. If
6452 you have one of these, say Y. If unsure, say N.
6454 IEEE 1394 (aka FireWire) support
6456 IEEE 1394 describes a high performance serial bus, which is also
6457 known as FireWire(tm) or i.Link(tm) and is used for connecting all
6458 sorts of devices (most notably digital video cameras) to your
6461 If you have FireWire hardware and want to use it, say Y here. This
6462 is the core support only, you will also need to select a driver for
6463 your IEEE 1394 adapter.
6465 If you want to compile this as a module ( = code which can be
6466 inserted in and removed from the running kernel whenever you want),
6467 say M here and read Documentation/modules.txt. The module will be
6470 TI PCILynx IEEE 1394 support
6471 CONFIG_IEEE1394_PCILYNX
6472 Say Y here if you have a IEEE-1394 controller with the Texas
6473 Instruments PCILynx chip. Note: this driver is written for revision
6474 2 of this chip and may not work with revision 0.
6476 If you want to compile this as a module ( = code which can be
6477 inserted in and removed from the running kernel whenever you want),
6478 say M here and read Documentation/modules.txt. The module will be
6481 Use local RAM on PCILynx board
6482 CONFIG_IEEE1394_PCILYNX_LOCALRAM
6483 This option makes the PCILynx driver use local RAM available on some
6484 PCILynx setups for Packet Control Lists. Local RAM is random access
6485 memory which resides on the PCILynx board as opposed to on your
6486 computer's motherboard. Local RAM may speed up command processing
6487 because no PCI transfers are necessary during use of the Packet
6490 Note that there are no known PCILynx systems providing local RAM
6491 except for the evaluation boards by Texas Instruments and that the
6492 PCILynx does not reliably report missing RAM. This means that it is
6493 dangerous to say Y here if you are not absolutely sure that your
6494 board provides 64KB of local RAM.
6498 Support for non-IEEE1394 local ports
6499 CONFIG_IEEE1394_PCILYNX_PORTS
6500 This option enables driver code to access the RAM, ROM and AUX ports
6501 of the PCILynx through character devices in /dev. If you don't know
6502 what this is about then you won't need it.
6506 Adaptec AIC-5800 IEEE 1394 support
6507 CONFIG_IEEE1394_AIC5800
6508 Say Y here if you have a IEEE 1394 controller using the Adaptec
6509 AIC-5800 chip. All Adaptec host adapters (89xx series) use this
6510 chip, as well as miro's DV boards.
6512 If you want to compile this as a module ( = code which can be
6513 inserted in and removed from the running kernel whenever you want),
6514 say M here and read Documentation/modules.txt. The module will be
6517 OHCI (Open Host Controller Interface) support
6518 CONFIG_IEEE1394_OHCI1394
6519 Say Y here if you have a IEEE 1394 controller based on OHCI.
6520 The current driver was only tested with OHCI chipsets made
6521 by Texas Instruments. However, most third-party vendors use
6524 If you want to compile this as a module ( = code which can be
6525 inserted in and removed from the running kernel whenever you want),
6526 say M here and read Documentation/modules.txt. The module will be
6529 Raw IEEE 1394 I/O support
6530 CONFIG_IEEE1394_RAWIO
6531 Say Y here if you want support for the raw device. This is generally
6532 a good idea, so you should say Y here. The raw device enables
6533 direct communication of user programs with the IEEE 1394 bus and
6534 thus with the attached peripherals.
6536 If you want to compile this as a module ( = code which can be
6537 inserted in and removed from the running kernel whenever you want),
6538 say M here and read Documentation/modules.txt. The module will be
6541 Excessive debugging output
6542 CONFIG_IEEE1394_VERBOSEDEBUG
6543 If you say Y here, you will get very verbose debugging logs from the
6544 subsystem which includes a dump of the header of every sent and
6545 received packet. This can amount to a high amount of data collected
6546 in a very short time which is usually also saved to disk by the
6547 system logging daemons.
6549 Say Y if you really want or need the debugging output, everyone else
6552 Network device support?
6554 You can say N here if you don't intend to connect your Linux box to
6555 any other computer at all or if all your connections will be over a
6556 telephone line with a modem either via UUCP (UUCP is a protocol to
6557 forward mail and news between unix hosts over telephone lines; read
6558 the UUCP-HOWTO, available from
6559 http://www.linuxdoc.org/docs.html#howto ) or dialing up a shell
6560 account or a BBS, even using term (term is a program which gives you
6561 almost full Internet connectivity if you have a regular dial up
6562 shell account on some Internet connected Unix computer. Read
6563 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html ).
6565 You'll have to say Y if your computer contains a network card that
6566 you want to use under Linux (make sure you know its name because you
6567 will be asked for it and read the Ethernet-HOWTO (especially if you
6568 plan to use more than one network card under Linux)) or if you want
6569 to use SLIP (Serial Line Internet Protocol is the protocol used to
6570 send Internet traffic over telephone lines or null modem cables) or
6571 CSLIP (compressed SLIP) or PPP (Point to Point Protocol, a better
6572 and newer replacement for SLIP) or PLIP (Parallel Line Internet
6573 Protocol is mainly used to create a mini network by connecting the
6574 parallel ports of two local machines) or AX.25/KISS (protocol for
6575 sending Internet traffic over amateur radio links).
6577 Make sure to read the NET-3-HOWTO. Eventually, you will have to read
6578 Olaf Kirch's excellent and free book "Network Administrator's
6579 Guide", to be found in http://www.linuxdoc.org/docs.html#guide . If
6582 Dummy net driver support
6584 This is essentially a bit-bucket device (i.e. traffic you send to
6585 this device is consigned into oblivion) with a configurable IP
6586 address. It is most commonly used in order to make your currently
6587 inactive SLIP address seem like a real address for local programs.
6588 If you use SLIP or PPP, you might want to say Y here. Since this
6589 thing often comes in handy, the default is Y. It won't enlarge your
6590 kernel either. What a deal. Read about it in the Network
6591 Administrator's Guide, available from
6592 http://www.linuxdoc.org/docs.html#guide .
6594 If you want to compile this as a module ( = code which can be
6595 inserted in and removed from the running kernel whenever you want),
6596 say M here and read Documentation/modules.txt. The module will be
6597 called dummy.o. If you want to use more than one dummy device at a
6598 time, you need to compile this driver as a module. Instead of
6599 'dummy', the devices will then be called 'dummy0', 'dummy1' etc.
6601 Bonding driver support
6603 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
6604 Channels together. This is called 'Etherchannel' by Cisco,
6605 'Trunking' by Sun, and 'Bonding' in Linux.
6607 If you have two ethernet connections to some other computer, you can
6608 make them behave like one double speed connection using this driver.
6609 Naturally, this has to be supported at the other end as well, either
6610 with a similar Bonding Linux driver, a Cisco 5500 switch or a
6611 SunTrunking SunSoft driver.
6613 This is similar to the EQL driver, but it merges Ethernet segments
6614 instead of serial lines.
6616 If you want to compile this as a module ( = code which can be
6617 inserted in and removed from the running kernel whenever you want),
6618 say M here and read Documentation/modules.txt. The module will be
6621 SLIP (serial line) support
6623 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
6624 connect to your Internet service provider or to connect to some
6625 other local Unix box or if you want to configure your Linux box as a
6626 Slip/CSlip server for other people to dial in. SLIP (Serial Line
6627 Internet Protocol) is a protocol used to send Internet traffic over
6628 serial connections such as telephone lines or null modem cables;
6629 nowadays, the protocol PPP is more commonly used for this same
6632 Normally, your access provider has to support SLIP in order for you
6633 to be able to use it, but there is now a SLIP emulator called SLiRP
6634 around (available via FTP (user: anonymous) from
6635 ftp://metalab.unc.edu/pub/Linux/system/network/serial/ ) which
6636 allows you to use SLIP over a regular dial up shell connection. If
6637 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
6638 NET-3-HOWTO, available from
6639 http://www.linuxdoc.org/docs.html#howto , explains how to
6640 configure SLIP. Note that you don't need this option if you just
6641 want to run term (term is a program which gives you almost full
6642 Internet connectivity if you have a regular dial up shell account on
6643 some Internet connected Unix computer. Read
6644 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html ). SLIP
6645 support will enlarge your kernel by about 4 KB. If unsure, say N.
6647 If you want to compile this as a module ( = code which can be
6648 inserted in and removed from the running kernel whenever you want),
6649 say M here and read Documentation/modules.txt as well as
6650 Documentation/networking/net-modules.txt. The module will be called
6653 CSLIP compressed headers
6654 CONFIG_SLIP_COMPRESSED
6655 This protocol is faster than SLIP because it uses compression on the
6656 TCP/IP headers (not on the data itself), but it has to be supported
6657 on both ends. Ask your access provider if you are not sure and
6658 answer Y, just in case. You will still be able to use plain SLIP. If
6659 you plan to use SLiRP, the SLIP emulator (available from
6660 ftp://metalab.unc.edu/pub/Linux/system/network/serial/ ) which
6661 allows you to use SLIP over a regular dial up shell connection, you
6662 definitely want to say Y here. The NET-3-HOWTO, available from
6663 http://www.linuxdoc.org/docs.html#howto , explains how to configure
6664 CSLIP. This won't enlarge your kernel.
6666 Keepalive and linefill
6668 Adds additional capabilities to the SLIP driver to support the
6669 RELCOM line fill and keepalive monitoring. Ideal on poor quality
6672 Six bit SLIP encapsulation
6673 CONFIG_SLIP_MODE_SLIP6
6674 Just occasionally you may need to run IP over hostile serial
6675 networks that don't pass all control characters or are only seven
6676 bit. Saying Y here adds an extra mode you can use with SLIP:
6677 "slip6". In this mode, SLIP will only send normal ASCII symbols over
6678 the serial device. Naturally, this has to be supported at the other
6679 end of the link as well. It's good enough, for example, to run IP
6680 over the async ports of a Camtec JNT Pad. If unsure, say N.
6682 PPP (point-to-point protocol) support
6684 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
6685 the same purpose: sending Internet traffic over telephone (and other
6686 serial) lines. Ask your access provider if they support it, because
6687 otherwise you can't use it; most internet access providers these
6688 days support PPP rather than SLIP.
6690 To use PPP, you need an additional program called pppd as described
6691 in Documentation/networking/ppp.txt and in the PPP-HOWTO, available
6692 at http://www.linuxdoc.org/docs.html#howto . If you upgrade
6693 from an older kernel, you might need to upgrade pppd as well. The
6694 PPP option enlarges your kernel by about 16 KB.
6696 There are actually two versions of PPP: the traditional PPP for
6697 asynchronous lines, such as regular analog phone lines, and
6698 synchronous PPP which can be used over digital ISDN lines for
6699 example. If you want to use PPP over phone lines or other
6700 asynchronous serial lines, you need to say Y (or M) here and also to
6701 the next option, "PPP support for async serial ports". For PPP over
6702 synchronous lines, you should say Y (or M) here and to "Support
6703 synchronous PPP", below.
6705 This driver is also available as a module ( = code which can be
6706 inserted in and removed from the running kernel whenever you want).
6707 If you said Y to "Version information on all symbols" above, then
6708 you cannot compile the PPP driver into the kernel; you can then only
6709 compile it as a module. The module will be called ppp_generic.o. If
6710 you want to compile it as a module, say M here and read
6711 Documentation/modules.txt as well as
6712 Documentation/networking/net-modules.txt.
6714 PPP multilink support (EXPERIMENTAL)
6715 CONFIG_PPP_MULTILINK
6716 PPP multilink is a protocol (defined in RFC 1990) which allows you
6717 to combine several (logical or physical) lines into one logical PPP
6718 connection, so that you can utilize your full bandwidth.
6720 This has to be supported at the other end as well and you need a
6721 version of the pppd daemon which understands the multilink protocol.
6725 PPP support for async serial ports
6727 Say Y (or M) here if you want to be able to use PPP over standard
6728 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
6729 a modem (not a synchronous or ISDN modem) to contact your ISP, you
6732 This code is also available as a module (code which can be inserted
6733 into and removed from the running kernel). If you want to compile
6734 it as a module, say M here and read Documentation/modules.txt.
6738 PPP support for sync tty ports
6740 Say Y (or M) here if you want to be able to use PPP over synchronous
6741 (HDLC) tty devices, such as the SyncLink adapter. These devices
6742 are often used for high-speed leased lines like T1/E1.
6744 This code is also available as a module (code which can be inserted
6745 into and removed from the running kernel). If you want to compile
6746 it as a module, say M here and read Documentation/modules.txt.
6748 PPP Deflate compression
6750 Support for the Deflate compression method for PPP, which uses the
6751 Deflate algorithm (the same algorithm that gzip uses) to compress
6752 each PPP packet before it is sent over the wire. The machine at the
6753 other end of the PPP link (usually your ISP) has to support the
6754 Deflate compression method as well for this to be useful. Even if
6755 they don't support it, it is safe to say Y here.
6757 This code is also available as a module (code which can be inserted
6758 into and removed from the running kernel). If you want to compile
6759 it as a module, say M here and read Documentation/modules.txt.
6761 PPP BSD-Compress compression
6763 Support for the BSD-Compress compression method for PPP, which uses
6764 the LZW compression method to compress each PPP packet before it is
6765 sent over the wire. The machine at the other end of the PPP link
6766 (usually your ISP) has to support the BSD-Compress compression
6767 method as well for this to be useful. Even if they don't support it,
6768 it is safe to say Y here.
6770 The PPP Deflate compression method ("PPP Deflate compression",
6771 above) is preferable to BSD-Compress, because it compresses better
6774 Note that the BSD compression code will always be compiled as a
6775 module; it is called bsd_comp.o and will show up in the directory
6776 modules once you have said "make modules". If unsure, say N.
6778 PPP over Ethernet (EXPERIMENTAL)
6780 Support for PPP over Ethernet.
6782 This driver requires a specially patched pppd daemon. The patch to
6783 pppd, along with binaries of a patched pppd package can be found at:
6784 http://www.math.uwaterloo.ca/~mostrows
6786 Wireless LAN (non-hamradio)
6788 Support for wireless LANs and everything having to do with radio,
6789 but not with amateur radio or FM broadcasting.
6791 Saying Y here also enables the Wireless Extensions (creates
6792 /proc/net/wireless and enables ifconfig access). The Wireless
6793 Extension is a generic API allowing a driver to expose to the user
6794 space configuration and statistics specific to common Wireless LANs.
6795 The beauty of it is that a single set of tool can support all the
6796 variations of Wireless LANs, regardless of their type (as long as
6797 the driver supports Wireless Extension). Another advantage is that
6798 these parameters may be changed on the fly without restarting the
6799 driver (or Linux). If you wish to use Wireless Extensions with
6800 wireless PCMCIA (PC-) cards, you need to say Y here; you can fetch
6802 http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html .
6804 Some user-level drivers for scarab devices which don't require
6805 special kernel support are available from
6806 ftp://shadow.cabi.net/pub/Linux .
6808 STRIP (Metricom Starmode radio IP)
6810 Say Y if you have a Metricom radio and intend to use Starmode Radio
6811 IP. STRIP is a radio protocol developed for the MosquitoNet project
6812 (on the WWW at http://mosquitonet.stanford.edu/ ) to send Internet
6813 traffic using Metricom radios. Metricom radios are small, battery
6814 powered, 100kbit/sec packet radio transceivers, about the size and
6815 weight of a cellular telephone. (You may also have heard them called
6816 "Metricom modems" but we avoid the term "modem" because it misleads
6817 many people into thinking that you can plug a Metricom modem into a
6818 phone line and use it as a modem.)
6820 You can use STRIP on any Linux machine with a serial port, although
6821 it is obviously most useful for people with laptop computers. If you
6822 think you might get a Metricom radio in the future, there is no harm
6823 in saying Y to STRIP now, except that it makes the kernel a bit
6826 You can also compile this as a module ( = code which can be inserted
6827 in and removed from the running kernel whenever you want), say M
6828 here and read Documentation/modules.txt. The module will be called
6831 AT&T WaveLAN & DEC RoamAbout DS support
6833 The Lucent WaveLAN (formerly NCR and AT&T; or DEC RoamAbout DS) is
6834 a Radio LAN (wireless Ethernet-like Local Area Network) using the
6835 radio frequencies 900 MHz and 2.4 GHz.
6837 This driver support the ISA version of the WaveLAN card. A separate
6838 driver for the PCMCIA (PC-card) hardware is available in David
6839 Hinds' pcmcia-cs package (see the file Documentation/Changes for
6842 If you want to use an ISA WaveLAN card under Linux, say Y and read
6843 the Ethernet-HOWTO, available from
6844 http://www.linuxdoc.org/docs.html#howto . Some more specific
6845 information is contained in Documentation/networking/wavelan.txt and
6846 in the source code drivers/net/wavelan.p.h.
6848 You will also need the wireless tools package available from
6849 http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html .
6850 Please read the man pages contained therein.
6852 This driver is also available as a module ( = code which can be
6853 inserted in and removed from the running kernel whenever you want).
6854 The module will be called wavelan.o. If you want to compile it as a
6855 module, say M here and read Documentation/modules.txt as well as
6856 Documentation/networking/net-modules.txt.
6858 Aironet Arlan 655 & IC2200 DS support
6860 Aironet makes Arlan, a class of wireless LAN adapters. These use the
6861 www.Telxon.com chip, which is also used on several similar cards.
6862 This driver is tested on the 655 and IC2200 series cards. Look at
6863 http://www.ylenurme.ee/~elmer/655/ for the latest information.
6865 The driver is built as two modules, arlan and arlan-proc. The latter
6866 is the /proc interface and is not needed most of time.
6868 On some computers the card ends up in non-valid state after some
6869 time. Use a ping-reset script to clear it.
6871 Aironet 4500/4800 series adapters
6873 www.aironet.com (recently bought by Cisco) makes these 802.11 DS
6874 adapters. Driver by Elmer Joandi (elmer@ylenurme.ee).
6876 Say Y here if you have such an adapter, and then say Y below to
6877 the option that applies to your particular type of card (PCI, ISA,
6880 This driver is also available as a module ( = code which can be
6881 inserted in and removed from the running kernel whenever you want).
6882 The module will be called aironet4500_core.o. If you want to
6883 compile it as a module, say M here and read
6884 Documentation/modules.txt as well as
6885 Documentation/networking/net-modules.txt.
6887 quick config parameters:
6888 SSID=tsunami - "The Password"
6889 adhoc=1 there are no Access Points around
6890 master=1 Adhoc master (the one who creates network
6892 slave=1 Adhoc slave (btw, it is still forming own net
6893 sometimes, and has problems with firmware...
6894 change IbssJoinNetTimeout from /proc...)
6895 channel=1..? meaningful in adhoc mode
6897 If you have problems with screwing up card, both_bap_lock=1 is a
6898 conservative value (performance hit 15%).
6900 All other parameters can be set via the proc interface.
6902 Aironet 4500/4800 ISA/PCI/PNP/365 support
6903 CONFIG_AIRONET4500_NONCS
6904 If you have an ISA, PCI or PCMCIA Aironet 4500/4800 wireless LAN
6905 card, say Y here, and then also to the options below that apply
6908 This driver is also available as a module ( = code which can be
6909 inserted in and removed from the running kernel whenever you want).
6910 The module will be called aironet4500_card.o. If you want to
6911 compile it as a module, say M here and read
6912 Documentation/modules.txt
6914 Aironet 4500/4800 PNP support
6915 CONFIG_AIRONET4500_PNP
6916 If you have an ISA Aironet 4500/4800 card which you want to use in
6917 PNP (Plug and Play) mode, say Y here. This is the recommended mode
6918 for ISA cards. Remember however to enable the PNP jumper on the
6919 board if you say Y here.
6921 Aironet 4500/4800 PCI support
6922 CONFIG_AIRONET4500_PCI
6923 If you have an PCI Aironet 4500/4800 card, say Y here.
6925 Aironet 4500/4800 ISA broken support (EXPERIMENTAL)
6926 CONFIG_AIRONET4500_ISA
6927 If you have an ISA Aironet 4500/4800 card which you want to run in
6928 non-PNP mode, say Y here. This is not recommended and does not work
6929 correctly at this point. Say N.
6931 Aironet 4500/4800 I365 broken support (EXPERIMENTAL)
6932 CONFIG_AIRONET4500_I365
6933 If you have a PCMCIA Aironet 4500/4800 card which you want to use
6934 without the standard PCMCIA cardservices provided by the pcmcia-cs
6935 package, say Y here. This is not recommended, so say N.
6937 Aironet 4500/4800 PCMCIA support
6938 CONFIG_AIRONET4500_CS
6939 Say Y here if you have a PCMCIA Aironet 4500/4800 card which you
6940 want to use with the standard PCMCIA cardservices provided by the
6943 This driver is also available as a module ( = code which can be
6944 inserted in and removed from the running kernel whenever you want).
6945 The module will be called aironet4500_cs.o. If you want to
6946 compile it as a module, say M here and read
6947 Documentation/modules.txt.
6949 Aironet 4500/4800 PROC interface
6950 CONFIG_AIRONET4500_PROC
6951 If you say Y here (and to the "/proc file system" below), you will
6952 be able to configure your Aironet card via the
6953 /proc/sys/aironet4500 interface.
6955 Additional info: look in drivers/net/aironet4500_rids.c.
6957 This driver is also available as a module ( = code which can be
6958 inserted in and removed from the running kernel whenever you want).
6959 The module will be called aironet4500_proc.o. If you want to
6960 compile it as a module, say M here and read
6961 Documentation/modules.txt.
6963 NOTE: the proc interface uses a lot of memory, so it is recommended
6964 to compile it as a module and remove the module after
6967 LAPB over Ethernet driver
6969 This is a driver for a pseudo device (typically called /dev/lapb0)
6970 which allows you to open an LAPB point-to-point connection to some
6971 other computer on your Ethernet network. In order to do this, you
6972 need to say Y or M to the driver for your Ethernet card as well as
6973 to "LAPB Data Link Driver".
6975 If you want to compile this driver as a module ( = code which can be
6976 inserted in and removed from the running kernel whenever you want),
6977 say M here and read Documentation/modules.txt. The module will be
6978 called lapbether.o. If unsure, say N.
6982 This is a driver for sending and receiving X.25 frames over regular
6983 asynchronous serial lines such as telephone lines equipped with
6984 ordinary modems. Experts should note that this driver doesn't
6985 currently comply with the asynchronous HDLS framing protocols in
6986 CCITT recommendation X.25.
6988 If you want to compile this driver as a module ( = code which can be
6989 inserted in and removed from the running kernel whenever you want),
6990 say M here and read Documentation/modules.txt. The module will be
6991 called x25_asy.o. If unsure, say N.
6993 PCMCIA network device support
6995 Say Y if you would like to include support for any PCMCIA or CardBus
6996 network adapters, then say Y to the driver for your particular card
6997 below. PCMCIA- or PC-cards are credit-card size devices often used
6998 with laptops computers; CardBus is the newer and faster version of
7001 To use your PC-cards, you will need supporting software from David
7002 Hinds' pcmcia-cs package (see the file Documentation/Changes for
7003 location). You also want to check out the PCMCIA-HOWTO, available
7004 from http://www.linuxdoc.org/docs.html#howto .
7008 3Com 3c589 PCMCIA support
7010 Say Y here if you intend to attach a 3Com 3c589 or compatible PCMCIA
7011 (PC-card) Ethernet card to your computer.
7013 This driver is also available as a module ( = code which can be
7014 inserted in and removed from the running kernel whenever you want).
7015 The module will be called 3c589_cs.o. If you want to compile it as a
7016 module, say M here and read Documentation/modules.txt. If unsure,
7019 3Com 3c574 PCMCIA support
7021 Say Y here if you intend to attach a 3Com 3c574 or compatible PCMCIA
7022 (PC-card) Fast Ethernet card to your computer.
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 3c574_cs.o. If you want to compile it as a
7027 module, say M here and read Documentation/modules.txt. If unsure,
7030 Fujitsu FMV-J18x PCMCIA support
7031 CONFIG_PCMCIA_FMVJ18X
7032 Say Y here if you intend to attach a Fujitsu FMV-J18x or compatible
7033 PCMCIA (PC-card) Ethernet card to your computer.
7035 This driver is also available as a module ( = code which can be
7036 inserted in and removed from the running kernel whenever you want).
7037 The module will be called fmvj18x_cs.o. If you want to compile it as
7038 a module, say M here and read Documentation/modules.txt. If unsure,
7041 NE2000 compatible PCMCIA support
7043 Say Y here if you intend to attach an NE2000 compatible PCMCIA
7044 (PC-card) Ethernet or Fast Ethernet card to your computer.
7046 This driver is also available as a module ( = code which can be
7047 inserted in and removed from the running kernel whenever you want).
7048 The module will be called pcnet_cs.o. If you want to compile it as a
7049 module, say M here and read Documentation/modules.txt. If unsure,
7052 New Media PCMCIA support
7053 CONFIG_PCMCIA_NMCLAN
7054 Say Y here if you intend to attach a New Media Ethernet or LiveWire
7055 PCMCIA (PC-card) Ethernet card to your computer.
7057 This driver is also available as a module ( = code which can be
7058 inserted in and removed from the running kernel whenever you want).
7059 The module will be called nmclan_cs.o. If you want to compile it as
7060 a module, say M here and read Documentation/modules.txt. If unsure,
7063 SMC 91Cxx PCMCIA support
7064 CONFIG_PCMCIA_SMC91C92
7065 Say Y here if you intend to attach an SMC 91Cxx compatible PCMCIA
7066 (PC-card) Ethernet or Fast Ethernet card to your computer.
7068 This driver is also available as a module ( = code which can be
7069 inserted in and removed from the running kernel whenever you want).
7070 The module will be called smc91c92_cs.o. If you want to compile it
7071 as a module, say M here and read Documentation/modules.txt. If
7074 Xircom 16-bit PCMCIA support
7075 CONFIG_PCMCIA_XIRC2PS
7076 Say Y here if you intend to attach a Xircom 16-bit PCMCIA
7077 (PC-card) Ethernet or Fast Ethernet card to your computer.
7079 This driver is also available as a module ( = code which can be
7080 inserted in and removed from the running kernel whenever you want).
7081 The module will be called xirc2ps_cs.o. If you want to compile it as
7082 a module, say M here and read Documentation/modules.txt. If unsure,
7085 COM20020 ARCnet PCMCIA support
7086 CONFIG_ARCNET_COM20020_CS
7087 Say Y here if you intend to attach this type of ARCnet PCMCIA card
7090 This driver is also available as a module ( = code which can be
7091 inserted in and removed from the running kernel whenever you want).
7092 The module will be called com20020_cs.o. If you want to compile it
7093 as a module, say M here and read Documentation/modules.txt. If
7096 IBM PCMCIA Token Ring adapter support
7098 Say Y here if you intend to attach this type of Token Ring PCMCIA
7099 card to your computer. You then also need to say Y to "Token Ring
7102 This driver is also available as a module ( = code which can be
7103 inserted in and removed from the running kernel whenever you want).
7104 The module will be called ibmtr_cs.o. If you want to compile it
7105 as a module, say M here and read Documentation/modules.txt.
7107 Xircom Tulip-like CardBus support
7108 CONFIG_PCMCIA_XIRTULIP
7109 This driver is for the Digital "Tulip" Ethernet CardBus adapters.
7110 It should work with most DEC 21*4*-based chips/ethercards, as well
7111 as with work-alike chips from Lite-On (PNIC) and Macronix (MXIC) and
7114 This driver is also available as a module ( = code which can be
7115 inserted in and removed from the running kernel whenever you want).
7116 The module will be called xircom_tulip_cb.o. If you want to compile
7117 it as a module, say M here and read Documentation/modules.txt. If
7121 CONFIG_NET_PCMCIA_RADIO
7122 Say Y here if you would like to use a PCMCIA (PC-card) device to
7123 connect to a wireless local area network. Then say Y to the driver
7124 for your particular card below.
7126 To use your PC-cards, you will need supporting software from David
7127 Hinds' pcmcia-cs package (see the file Documentation/Changes for
7128 location). You also want to check out the PCMCIA-HOWTO, available
7129 from http://www.linuxdoc.org/docs.html#howto .
7131 Aviator/Raytheon 2.4MHz wireless support
7133 Say Y here if you intend to attach an Aviator/Raytheon PCMCIA
7134 (PC-card) wireless Ethernet networking card to your computer.
7135 Please read the file Documentation/networking/ray_cs.txt for
7138 This driver is also available as a module ( = code which can be
7139 inserted in and removed from the running kernel whenever you want).
7140 The module will be called ray_cs.o. If you want to compile it as a
7141 module, say M here and read Documentation/modules.txt. If unsure,
7144 Xircom Netwave AirSurfer wireless support
7145 CONFIG_PCMCIA_NETWAVE
7146 Say Y here if you intend to attach this type of PCMCIA (PC-card)
7147 wireless Ethernet networking card to your computer.
7149 This driver is also available as a module ( = code which can be
7150 inserted in and removed from the running kernel whenever you want).
7151 The module will be called netwave_cs.o. If you want to compile it as
7152 a module, say M here and read Documentation/modules.txt. If unsure,
7155 AT&T/Lucent Wavelan wireless support
7156 CONFIG_PCMCIA_WAVELAN
7157 Say Y here if you intend to attach an AT&T/Lucent Wavelan PCMCIA
7158 (PC-card) wireless Ethernet networking card to your computer. This
7159 driver is for the non-IEEE-802.11 Wavelan cards.
7161 This driver is also available as a module ( = code which can be
7162 inserted in and removed from the running kernel whenever you want).
7163 The module will be called wavelan_cs.o. If you want to compile it as
7164 a module, say M here and read Documentation/modules.txt. If unsure,
7167 PLIP (parallel port) support
7169 PLIP (Parallel Line Internet Protocol) is used to create a
7170 reasonably fast mini network consisting of two (or, rarely, more)
7171 local machines. A PLIP link from a Linux box is a popular means to
7172 install a Linux distribution on a machine which doesn't have a CDROM
7173 drive (a minimal system has to be transferred with floppies first).
7174 The kernels on both machines need to have this PLIP option enabled
7177 The PLIP driver has two modes, mode 0 and mode 1. The parallel ports
7178 (the connectors at the computers with 25 holes) are connected with
7179 "null printer" or "Turbo Laplink" cables which can transmit 4 bits
7180 at a time (mode 0) or with special PLIP cables, to be used on
7181 bidirectional parallel ports only, which can transmit 8 bits at a
7182 time (mode 1); you can find the wiring of these cables in
7183 Documentation/networking/PLIP.txt. The cables can be up to 15m long.
7184 Mode 0 works also if one of the machines runs DOS/Windows and has
7185 some PLIP software installed, e.g. the Crynwr PLIP packet driver
7186 (http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html ) and
7187 winsock or NCSA's telnet.
7189 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
7190 as the NET-3-HOWTO, both available from
7191 http://www.linuxdoc.org/docs.html#howto . Note that the PLIP
7192 protocol has been changed and this PLIP driver won't work together
7193 with the PLIP support in Linux versions 1.0.x. This option enlarges
7194 your kernel by about 8 KB.
7196 If you want to compile this as a module ( = code which can be
7197 inserted in and removed from the running kernel whenever you want),
7198 say M here and read Documentation/modules.txt as well as
7199 Documentation/networking/net-modules.txt. The module will be called
7200 plip.o. If unsure, say Y or M, in case you buy a laptop later.
7202 EQL (serial line load balancing) support
7204 If you have two serial connections to some other computer (this
7205 usually requires two modems and two telephone lines) and you use
7206 SLIP (the protocol for sending Internet traffic over telephone
7207 lines) or PPP (a better SLIP) on them, you can make them behave like
7208 one double speed connection using this driver. Naturally, this has
7209 to be supported at the other end as well, either with a similar EQL
7210 Linux driver or with a Livingston Portmaster 2e.
7212 Say Y if you want this and read Documentation/networking/eql.txt.
7213 You may also want to read section 6.2 of the NET-3-HOWTO, available
7214 from http://www.linuxdoc.org/docs.html#howto .
7216 This driver is also available as a module ( = code which can be
7217 inserted in and removed from the running kernel whenever you want).
7218 The module will be called eql.o. If you want to compile it as a
7219 module, say M here and read Documentation/modules.txt. If unsure,
7222 Universal TUN/TAP device driver.
7224 TUN/TAP provides packet reception and transmission for user space programs.
7225 It can be viewed as a simple Point-to-Point or Ethernet device, which
7226 instead of receiving packets from a physical media, receives them from
7227 user space program and instead of sending packets via physical media
7228 writes them to the user space program.
7230 When a program opens /dev/net/tun, driver creates and registers
7231 corresponding net device tunX or tapX. After a program closed above
7232 devices, driver will automatically delete tunXX or tapXX device and all
7233 routes corresponding to it.
7235 Please read Documentation/networking/tuntap.txt for more information.
7237 This driver is also available as a module ( = code which can be
7238 inserted in and removed from the running kernel whenever you want).
7239 The module will be called tun.o. If you want to compile it as a
7240 module, say M here and read Documentation/modules.txt.
7242 If you don't know what to use this for, you don't need it.
7244 Ethertap network tap (OBSOLETE)
7246 If you say Y here (and have said Y to "Kernel/User network link
7247 driver", above) and create a character special file /dev/tap0 with
7248 major number 36 and minor number 16 using mknod ("man mknod"), you
7249 will be able to have a user space program read and write raw
7250 Ethernet frames from/to that special file. tap0 can be configured
7251 with ifconfig and route like any other Ethernet device but it is not
7252 connected to any physical LAN; everything written by the user to
7253 /dev/tap0 is treated by the kernel as if it had come in from a LAN
7254 to the device tap0; everything the kernel wants to send out over the
7255 device tap0 can instead be read by the user from /dev/tap0: the user
7256 mode program replaces the LAN that would be attached to an ordinary
7257 Ethernet device. Please read the file
7258 Documentation/networking/ethertap.txt for more information.
7260 This driver is also available as a module ( = code which can be
7261 inserted in and removed from the running kernel whenever you want).
7262 The module will be called ethertap.o. If you want to compile it as a
7263 module, say M here and read Documentation/modules.txt.
7265 If you don't know what to use this for, you don't need it.
7267 Sealevel Systems 4021 support
7268 CONFIG_SEALEVEL_4021
7269 This is a driver for the Sealevel Systems ACB 56 serial I/O adapter.
7271 This driver can only be compiled as a module ( = code which can be
7272 inserted in and removed from the running kernel whenever you want).
7273 If you want to do that, say M here. The module will be called
7276 SyncLink HDLC/SYNCPPP support
7277 CONFIG_SYNCLINK_SYNCPPP
7278 Enables HDLC/SYNCPPP support for the SyncLink WAN driver.
7279 Normally the SyncLink WAN driver works with the main PPP
7280 driver (ppp.c) and pppd program. HDLC/SYNCPPP support allows use
7281 of the Cisco HDLC/PPP driver (syncppp.c).
7282 The SyncLink WAN driver (in character devices) must also be enabled.
7284 Frame Relay (DLCI) support
7286 This is support for the frame relay protocol; frame relay is a fast
7287 low-cost way to connect to a remote Internet access provider or to
7288 form a private wide area network. The one physical line from your
7289 box to the local "switch" (i.e. the entry point to the frame relay
7290 network, usually at the phone company) can carry several logical
7291 point-to-point connections to other computers connected to the frame
7292 relay network. For a general explanation of the protocol, check out
7293 http://www.frforum.com/ on the WWW. To use frame relay, you need
7294 supporting hardware (called FRAD) and certain programs from the
7295 net-tools package as explained in
7296 Documentation/networking/framerelay.txt.
7298 This driver is also available as a module ( = code which can be
7299 inserted in and removed from the running kernel whenever you want).
7300 The module will be called dlci.o. If you want to compile it as a
7301 module, say M here and read Documentation/modules.txt.
7305 This is the maximal number of logical point-to-point frame relay
7306 connections (the identifiers of which are called DCLIs) that
7307 the driver can handle. The default is probably fine.
7311 You can specify here how many logical point-to-point frame relay
7312 connections (the identifiers of which are called DCLIs) should be
7313 handled by each of your hardware frame relay access devices. Go with
7316 Sangoma S502A FRAD support
7318 Say Y here if you need a driver for the Sangoma S502A, S502E, and
7319 S508 Frame Relay Access Devices. These are multi-protocol cards, but
7320 only frame relay is supported by the driver at this time. Please
7321 read Documentation/framerelay.txt.
7323 This driver is also available as a module ( = code which can be
7324 inserted in and removed from the running kernel whenever you want).
7325 The module will be called sdla.o. If you want to compile it as a
7326 module, say M here and read Documentation/modules.txt.
7328 Acorn Econet/AUN protocols (EXPERIMENTAL)
7330 Econet is a fairly old and slow networking protocol mainly used by
7331 Acorn computers to access file and print servers. It uses native
7332 Econet network cards. AUN is an implementation of the higher level
7333 parts of Econet that runs over ordinary Ethernet connections, on
7334 top of the UDP packet protocol, which in turn runs on top of the
7335 Internet protocol IP.
7337 If you say Y here, you can choose with the next two options whether
7338 to send Econet/AUN traffic over a UDP Ethernet connection or over
7339 a native Econet network card.
7341 This driver is also available as a module ( = code which can be
7342 inserted in and removed from the running kernel whenever you want).
7343 The module will be called econet.o. If you want to compile it as a
7344 module, say M here and read Documentation/modules.txt.
7347 CONFIG_ECONET_AUNUDP
7348 Say Y here if you want to send Econet/AUN traffic over a UDP
7349 connection (UDP is a packet based protocol that runs on top of the
7350 Internet protocol IP) using an ordinary Ethernet network card.
7353 CONFIG_ECONET_NATIVE
7354 Say Y here if you have a native Econet network card installed in
7359 Wide Area Networks (WANs), such as X.25, frame relay and leased
7360 lines, are used to interconnect Local Area Networks (LANs) over vast
7361 distances with data transfer rates significantly higher than those
7362 achievable with commonly used asynchronous modem connections.
7363 Usually, a quite expensive external device called a `WAN router' is
7364 needed to connect to a WAN.
7366 As an alternative, WAN routing can be built into the Linux kernel.
7367 With relatively inexpensive WAN interface cards available on the
7368 market, a perfectly usable router can be built for less than half
7369 the price of an external router. If you have one of those cards and
7370 wish to use your Linux box as a WAN router, say Y here and also to
7371 the WAN driver for your card, below. You will then need the
7372 wan-tools package which is available from ftp://ftp.sangoma.com .
7373 Read Documentation/networking/wan-router.txt for more information.
7375 The WAN routing support is also available as a module called
7376 wanrouter.o ( = code which can be inserted in and removed from the
7377 running kernel whenever you want). If you want to compile it as a
7378 module, say M here and read Documentation/modules.txt.
7382 Fast switching (read help!)
7383 CONFIG_NET_FASTROUTE
7384 Saying Y here enables direct NIC-to-NIC (NIC = Network Interface
7385 Card) data transfers on the local network, which is fast.
7387 IMPORTANT NOTE: This option is NOT COMPATIBLE with "Network packet
7388 filtering" (CONFIG_NETFILTER). Say N here if you say Y there.
7390 However, it will work with all options in the "IP: advanced router"
7391 section (except for "IP: use TOS value as routing key" and
7392 "IP: use FWMARK value as routing key").
7394 At the moment, few devices support fast switching (tulip is one of
7395 them, a modified 8390 driver can be found at
7396 ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz ).
7400 Forwarding between high speed interfaces
7401 CONFIG_NET_HW_FLOWCONTROL
7402 This option enables NIC (Network Interface Card) hardware throttling
7403 during periods of extremal congestion. At the moment only a couple
7404 of device drivers support it (really only one -- tulip, a modified
7405 8390 driver can be found at
7406 ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz ).
7408 Really, this option is applicable to any machine attached to a fast
7409 enough network, and even a 10 Mb NIC is able to kill a not very slow
7410 box, such as a 120MHz Pentium.
7412 However, do not say Y here if you did not experience any serious
7415 QoS and/or fair queueing
7417 When the kernel has several packets to send out over a network
7418 device, it has to decide which ones to send first, which ones to
7419 delay, and which ones to drop. This is the job of the packet
7420 scheduler, and several different algorithms for how to do this
7421 "fairly" have been proposed.
7423 If you say N here, you will get the standard packet scheduler, which
7424 is a FIFO (first come, first served). If you say Y here, you will be
7425 able to choose from among several alternative algorithms which can
7426 then be attached to different network devices. This is useful for
7427 example if some of your network devices are real time devices that
7428 need a certain minimum data flow rate, or if you need to limit the
7429 maximum data flow rate for traffic which matches specified criteria.
7430 This code is considered to be experimental.
7432 To administer these schedulers, you'll need the user-level utilities
7433 from the package iproute2+tc at ftp://ftp.inr.ac.ru/ip-routing/ .
7434 That package also contains some documentation; for more, check out
7435 http://snafu.freedom.org/linux2.2/iproute-notes.html .
7437 This Quality of Service (QoS) support will enable you to use
7438 Differentiated Services (diffserv) and Resource Reservation Protocol
7439 (RSVP) on your Linux router if you also say Y to "QoS support",
7440 "Packet classifier API" and to some classifiers below. Documentation
7441 and software is at http://icawww1.epfl.ch/linux-diffserv/ .
7443 If you say Y here and to "/proc file system" below, you will be able
7444 to read status information about packet schedulers from the file
7447 The available schedulers are listed in the following questions; you
7448 can say Y to as many as you like. If unsure, say N now.
7450 CBQ packet scheduler
7452 Say Y here if you want to use the Class-Based Queueing (CBQ) packet
7453 scheduling algorithm for some of your network devices. This
7454 algorithm classifies the waiting packets into a tree-like hierarchy
7455 of classes; the leaves of this tree are in turn scheduled by
7456 separate algorithms (called "disciplines" in this context).
7458 See the top of net/sched/sch_cbq.c for references about the CBQ
7461 CBQ is a commonly used scheduler, so if you're unsure, you should
7462 say Y here. Then say Y to all the queueing algorithms below that you
7463 want to use as CBQ disciplines. Then say Y to "Packet classifier
7464 API" and say Y to all the classifiers you want to use; a classifier
7465 is a routine that allows you to sort your outgoing traffic into
7466 classes based on a certain criterion.
7468 This code is also available as a module called sch_cbq.o ( = code
7469 which can be inserted in and removed from the running kernel
7470 whenever you want). If you want to compile it as a module, say M
7471 here and read Documentation/modules.txt.
7473 CSZ packet scheduler
7475 Say Y here if you want to use the Clark-Shenker-Zhang (CSZ) packet
7476 scheduling algorithm for some of your network devices. At the
7477 moment, this is the only algorithm that can guarantee service for
7478 real-time applications (see the top of net/sched/sch_csz.c for
7479 details and references about the algorithm).
7481 Note: this scheduler is currently broken.
7483 This code is also available as a module called sch_csz.o ( = code
7484 which can be inserted in and removed from the running kernel
7485 whenever you want). If you want to compile it as a module, say M
7486 here and read Documentation/modules.txt.
7488 #ATM pseudo-scheduler
7494 The simplest PRIO pseudo scheduler
7496 Say Y here if you want to use an n-band priority queue packet
7497 "scheduler" for some of your network devices or as a leaf discipline
7498 for the CBQ scheduling algorithm. If unsure, say Y.
7500 This code is also available as a module called sch_prio.o ( = code
7501 which can be inserted in and removed from the running kernel
7502 whenever you want). If you want to compile it as a module, say M
7503 here and read Documentation/modules.txt.
7507 Say Y here if you want to use the Random Early Detection (RED)
7508 packet scheduling algorithm for some of your network devices (see
7509 the top of net/sched/sch_red.c for details and references about the
7512 This code is also available as a module called sch_red.o ( = code
7513 which can be inserted in and removed from the running kernel
7514 whenever you want). If you want to compile it as a module, say M
7515 here and read Documentation/modules.txt.
7519 Say Y here if you want to use the Stochastic Fairness Queueing (SFQ)
7520 packet scheduling algorithm for some of your network devices or as a
7521 leaf discipline for the CBQ scheduling algorithm (see the top of
7522 net/sched/sch_sfq.c for details and references about the SFQ
7525 This code is also available as a module called sch_sfq.o ( = code
7526 which can be inserted in and removed from the running kernel
7527 whenever you want). If you want to compile it as a module, say M
7528 here and read Documentation/modules.txt.
7532 Say Y here if you want to use the True Link Equalizer (TLE) packet
7533 scheduling algorithm for some of your network devices or as a leaf
7534 discipline for the CBQ scheduling algorithm. This queueing
7535 discipline allows the combination of several physical devices into
7536 one virtual device. (see the top of net/sched/sch_teql.c for
7539 This code is also available as a module called sch_teql.o ( = code
7540 which can be inserted in and removed from the running kernel
7541 whenever you want). If you want to compile it as a module, say M
7542 here and read Documentation/modules.txt.
7546 Say Y here if you want to use the Simple Token Bucket Filter (TBF)
7547 packet scheduling algorithm for some of your network devices or as a
7548 leaf discipline for the CBQ scheduling algorithm (see the top of
7549 net/sched/sch_tbf.c for a description of the TBF algorithm).
7551 This code is also available as a module called sch_tbf.o ( = code
7552 which can be inserted in and removed from the running kernel
7553 whenever you want). If you want to compile it as a module, say M
7554 here and read Documentation/modules.txt.
7557 #+tristate ' GRED queue' CONFIG_NET_SCH_GRED
7558 #+tristate ' Diffserv field marker' CONFIG_NET_SCH_DSMARK
7559 #+tristate ' Ingress Qdisc' CONFIG_NET_SCH_INGRESS
7563 Say Y here if you want to include Quality Of Service scheduling
7564 features, which means that you will be able to request certain
7565 rate-of-flow limits for your network devices.
7567 This Quality of Service (QoS) support will enable you to use
7568 Differentiated Services (diffserv) and Resource Reservation Protocol
7569 (RSVP) on your Linux router if you also say Y to "Packet classifier
7570 API" and to some classifiers below. Documentation and software is at
7571 http://icawww1.epfl.ch/linux-diffserv/ .
7573 Note that the answer to this question won't directly affect the
7574 kernel: saying N will just cause this configure script to skip all
7575 the questions about QoS support.
7578 CONFIG_NET_ESTIMATOR
7579 In order for Quality of Service scheduling to work, the current
7580 rate-of-flow for a network device has to be estimated; if you say Y
7581 here, the kernel will do just that.
7583 Packet classifier API
7585 The CBQ scheduling algorithm requires that network packets which are
7586 scheduled to be sent out over a network device be classified
7587 according to some criterion. If you say Y here, you will get a
7588 choice of several different packet classifiers with the following
7591 This will enable you to use Differentiated Services (diffserv) and
7592 Resource Reservation Protocol (RSVP) on your Linux router.
7593 Documentation and software is at
7594 http://icawww1.epfl.ch/linux-diffserv/ .
7597 #tristate ' TC index classifier' CONFIG_NET_CLS_TCINDEX
7599 Routing tables based classifier
7600 CONFIG_NET_CLS_ROUTE4
7601 If you say Y here, you will be able to classify outgoing packets
7602 according to the route table entry they matched. If unsure, say Y.
7604 This code is also available as a module called cls_route.o ( = code
7605 which can be inserted in and removed from the running kernel
7606 whenever you want). If you want to compile it as a module, say M
7607 here and read Documentation/modules.txt.
7609 Firewall based classifier
7611 If you say Y here, you will be able to classify outgoing packets
7612 according to firewall criteria you specified.
7614 This code is also available as a module called cls_fw.o ( = code
7615 which can be inserted in and removed from the running kernel
7616 whenever you want). If you want to compile it as a module, say M
7617 here and read Documentation/modules.txt.
7621 If you say Y here, you will be able to classify outgoing packets
7622 according to their destination address. If unsure, say Y.
7624 This code is also available as a module called cls_u32.o ( = code
7625 which can be inserted in and removed from the running kernel
7626 whenever you want). If you want to compile it as a module, say M
7627 here and read Documentation/modules.txt
7629 Special RSVP classifier
7631 The Resource Reservation Protocol (RSVP) permits end systems to
7632 request a minimum and maximum data flow rate for a connection; this
7633 is important for real time data such as streaming sound or video.
7635 Say Y here if you want to be able to classify outgoing packets based
7636 on their RSVP requests.
7638 This code is also available as a module called cls_rsvp.o ( = code
7639 which can be inserted in and removed from the running kernel
7640 whenever you want). If you want to compile it as a module, say M
7641 here and read Documentation/modules.txt
7643 Special RSVP classifier for IPv6
7644 CONFIG_NET_CLS_RSVP6
7645 The Resource Reservation Protocol (RSVP) permits end systems to
7646 request a minimum and maximum data flow rate for a connection; this
7647 is important for real time data such as streaming sound or video.
7649 Say Y here if you want to be able to classify outgoing packets based
7650 on their RSVP requests and you are using the new Internet Protocol
7651 IPv6 as opposed to the older and more common IPv4.
7653 This code is also available as a module called cls_rsvp6.o ( = code
7654 which can be inserted in and removed from the running kernel
7655 whenever you want). If you want to compile it as a module, say M
7656 here and read Documentation/modules.txt
7659 # Traffic policing (needed for in/egress)
7660 # CONFIG_NET_CLS_POLICE
7662 ### Some expert please fill these in
7665 Network code profiler
7667 If you say Y here and to "/proc file system support" below, some
7668 obscure and undocumented information about the network code's
7669 performance will be written to /proc/net/profile. If you don't know
7670 what it is about, you don't need it: say N.
7672 Wan interfaces support
7674 Wide Area Networks (WANs), such as X.25, frame relay and leased
7675 lines, are used to interconnect Local Area Networks (LANs) over vast
7676 distances with data transfer rates significantly higher than those
7677 achievable with commonly used asynchronous modem connections.
7678 Usually, a quite expensive external device called a `WAN router' is
7679 needed to connect to a WAN.
7681 As an alternative, a relatively inexpensive WAN interface card can
7682 allow your Linux box to directly connect to a WAN. If you have one
7683 of those cards and wish to use it under Linux, say Y here and also
7684 to the WAN driver for your card, below.
7688 Comtrol Hostess SV-11 support
7690 This is a network card for low speed synchronous serial links, at
7691 up to 256Kbps. It supports both PPP and Cisco HDLC.
7693 At this point, the driver can only be compiled as a module.
7695 COSA/SRP sync serial boards support
7697 This is a driver for COSA and SRP synchronous serial boards. These
7698 boards allow to connect synchronous serial devices (for example
7699 base-band modems, or any other device with the X.21, V.24, V.35 or
7700 V.36 interface) to your Linux box. The cards can work as the
7701 character device, synchronous PPP network device, or the Cisco HDLC
7704 To actually use the COSA or SRP board, you will need user-space
7705 utilities for downloading the firmware to the cards and to set them
7706 up. Look at the http://www.fi.muni.cz/~kas/cosa/ for more
7707 information about the cards (including the pointer to the user-space
7708 utilities). You can also read the comment at the top of the
7709 drivers/net/cosa.c for details about the cards and the driver
7712 The driver will be compiled as a module ( = code which can be
7713 inserted in and removed from the running kernel whenever you want).
7714 The module will be called cosa.o. For general information about
7715 modules read Documentation/modules.txt.
7717 Lan Media sync serial boards support
7719 This is a driver for the following Lan Media family of serial boards.
7721 LMC 1000 board allows you to connect synchronous serial devices (for
7722 example base-band modems, or any other device with the X.21, V.24,
7723 V.35 or V.36 interface) to your Linux box.
7725 LMC 1200 with on board DSU board allows you to connect your Linux
7726 box dirrectly to a T1 or E1 circuit.
7728 LMC 5200 board provides a HSSI interface capable of runnig up to
7729 52 mbits per second.
7731 LMC 5245 board connects directly to a T3 circuit saving the
7732 additional external hardware.
7734 To change setting such as syncPPP vs cisco HDLC or clock source you
7735 will need lmcctl. It it available at ftp.lanmedia.com.
7737 This code is also available as a module called lmc.o ( = code
7738 which can be inserted in and removed from the running kernel
7739 whenever you want). If you want to compile it as a module, say M
7740 here and read Documentation/modules.txt.
7742 Fibre Channel driver support
7744 Fibre Channel is a high speed serial protocol mainly used to connect
7745 large storage devices to the computer; it is compatible with and
7746 intended to replace SCSI.
7748 If you intend to use Fibre Channel, you need to have a Fibre channel
7749 adaptor card in your computer; say Y here and to the driver for your
7750 adaptor below. You also should have said Y to "SCSI support" and
7751 "SCSI generic support".
7753 Interphase 5526 Tachyon chipset based adaptor support
7755 Say Y here if you have a Fibre Channel adaptor of this kind.
7757 The driver is also available as a module ( = code which can be
7758 inserted in and removed from the running kernel whenever you want).
7759 The module will be called iph5526.o. For general information about
7760 modules read Documentation/modules.txt.
7762 Red Creek Hardware VPN (EXPERIMENTAL)
7764 This is a driver for hardware which provides a Virtual Private
7765 Network (VPN). Say Y if you have it.
7767 This code is also available as a module called rcpci.o ( = code
7768 which can be inserted in and removed from the running kernel
7769 whenever you want). If you want to compile it as a module, say M
7770 here and read Documentation/modules.txt.
7774 This is a driver for ISA SBNI12-xx cards which are low cost
7775 alternatives to leased line modems. Say Y if you want to insert
7776 the driver into the kernel or say M to compile it as a module (the
7777 module will be called sbni.o).
7779 You can find more information and last versions of drivers and
7780 utilities at http://www.granch.ru . If you have any question you
7781 can send email to sbni@granch.ru.
7786 CONFIG_WAN_ROUTER_DRIVERS
7787 If you have a WAN interface card and you want your Linux box to act
7788 as a WAN router, thereby connecting you Local Area Network to the
7789 outside world over the WAN connection, say Y here and then to the
7790 driver for your card below. In addition, you need to say Y to "Wan
7793 You will need the wan-tools package which is available from
7794 ftp://ftp.sangoma.com . Read Documentation/networking/wan-router.txt
7795 for more information.
7797 Note that the answer to this question won't directly affect the
7798 kernel: saying N will just cause this configure script to skip all
7799 the questions about WAN router drivers. If unsure, say N.
7801 Sangoma WANPIPE(tm) multiprotocol cards
7802 CONFIG_VENDOR_SANGOMA
7803 WANPIPE from Sangoma Technologies Inc. (http://www.sangoma.com ) is
7804 a family of intelligent multiprotocol WAN adapters with data
7805 transfer rates up to T1 (1.544 Mbps). They are also known as
7806 Synchronous Data Link Adapters (SDLA) and designated S502E(A), S503
7807 or S508. These cards support the X.25, Frame Relay, and PPP
7808 protocols. If you have one or more of these cards, say Y to this
7809 option; you may then also want to read the file
7810 Documentation/networking/wanpipe.txt. The next questions will ask
7811 you about the protocols you want the driver to support.
7813 The driver will be compiled as a module ( = code which can be
7814 inserted in and removed from the running kernel whenever you want).
7815 The module will be called wanpipe.o. For general information about
7816 modules read Documentation/modules.txt.
7818 Maximum number of cards
7819 CONFIG_WANPIPE_CARDS
7820 Enter number of WANPIPE adapters installed in your machine. The
7821 driver can support up to 8 cards. You may enter more than you
7822 actually have if you plan to add more cards in the future without
7823 re-compiling the driver, but remember that in this case you'll waste
7824 some kernel memory (about 1K per card).
7826 WANPIPE Cisco HDLC support
7827 CONFIG_WANPIPE_CHDLC
7828 Say Y to this option if you are planning to connect a WANPIPE card
7829 to a connection which uses the synchronous Cisco HDLC (High-level
7830 Data Link Control) protocol. This protocol is often used on
7831 high-speed leased lines like T1/E1.
7833 WANPIPE X.25 support
7835 Say Y to this option if you are planning to connect a WANPIPE card
7836 to an X.25 network. You should then also have said Y to "CCITT X.25
7837 Packet Layer" and "LAPB Data Link Driver", above. If you say N, the
7838 X.25 support will not be included in the driver (saves about 16 KB
7841 WANPIPE Frame Relay support
7843 Say Y to this option if you are planning to connect a WANPIPE card
7844 to a frame relay network. You should then also have said Y to "Frame
7845 Relay (DLCI) support", above. If you say N, the frame relay
7846 support will not be included in the driver (saves about 16 KB of
7851 Say Y to this option if you are planning to connect a WANPIPE card
7852 to a leased line using Point-to-Point protocol (PPP). You should
7853 then also have said Y to "PPP (point-to-point) support", above. If
7854 you say N, the PPP support will not be included in the driver (saves
7855 about 16 KB of kernel memory).
7857 MultiGate/COMX support
7859 Say Y if you want to use any board from the MultiGate (COMX) family.
7860 These boards are synchronous serial adapters for the PC,
7861 manufactured by ITConsult-Pro Co, Hungary.
7863 Read linux/Documentation/networking/comx.txt for help on configuring
7864 and using COMX interfaces. Further info on these cards can be found
7865 at http://www.itc.hu or <info@itc.hu>.
7867 If you want to compile this as a module, say M and read
7868 Documentation/modules.txt. The module will be called comx.o.
7870 COMX/CMX/HiCOMX board support
7872 Hardware driver for the 'CMX', 'COMX' and 'HiCOMX' boards from the
7873 MultiGate family. Say Y if you have one of these.
7875 You will need additional firmware to use these cards, which are
7876 downloadable from ftp://ftp.itc.hu/.
7878 If you want to compile this as a module, say M and read
7879 Documentation/modules.txt. The module will be called comx-hw-comx.o.
7881 LoCOMX board support
7882 CONFIG_COMX_HW_LOCOMX
7883 Hardware driver for the 'LoCOMX' board from the MultiGate family.
7884 Say Y if you have a board like this.
7886 If you want to compile this as a module, say M and read
7887 Documentation/modules.txt. The module will be called
7890 MixCOM board support
7891 CONFIG_COMX_HW_MIXCOM
7892 Hardware driver for the 'MixCOM' board from the MultiGate family.
7893 Say Y if you have a board like this.
7895 If you want to use the watchdog device on this card, you should
7896 select it in the Watchdog Cards section of the Character Devices
7897 configuration. The ISDN interface of this card is Teles 16.3
7898 compatible, you should enable it in the ISDN configuration menu. The
7899 driver for the flash ROM of this card is available separately on
7902 If you want to compile this as a module, say M and read
7903 Documentation/modules.txt. The module will be called
7908 Hardware driver for the TCO timer built into the Intel i810 and i815
7909 chipset family. The TCO (Total Cost of Ownership) timer is a watchdog
7910 timer that will reboot the machine after it's second expiration. The
7911 expiration time can be configured by commandline argument
7912 "i810_margin=<n>" where <n> is the counter initial value. It is
7913 decremented every 0.6 secs, the default is 50 which gives a timeout
7914 of 30 seconds and one minute until reset.
7916 On some motherboards the driver may fail to reset the chipset's
7917 NO_REBOOT flag which prevents the watchdog from rebooting the machine.
7918 If this is the case you will get a kernel message like
7919 "i810tco init: failed to reset NO_REBOOT flag".
7921 If you want to compile this as a module, say M and read
7922 Documentation/modules.txt. The module will be called
7925 MultiGate Cisco-HDLC and synchronous PPP protocol support
7926 CONFIG_COMX_PROTO_PPP
7927 Cisco-HDLC and synchronous PPP protocol driver for all MultiGate
7928 boards. Say Y if you want to use either protocol on your MultiGate
7931 If you want to compile this as a module, say M and read
7932 Documentation/modules.txt. The module will be called
7935 MultiGate LAPB protocol support
7936 CONFIG_COMX_PROTO_LAPB
7937 LAPB protocol driver for all MultiGate boards. Say Y if you
7938 want to use this protocol on your MultiGate boards.
7940 If you want to compile this as a module, say M and read
7941 Documentation/modules.txt. The module will be called
7944 MultiGate Frame Relay protocol support
7945 CONFIG_COMX_PROTO_FR
7946 Frame Relay protocol driver for all MultiGate boards. Say Y if you
7947 want to use this protocol on your MultiGate boards.
7949 If you want to compile this as a module, say M and read
7950 Documentation/modules.txt. The module will be called
7953 Cyclom 2X(tm) multiprotocol cards (EXPERIMENTAL)
7954 CONFIG_CYCLADES_SYNC
7955 Cyclom 2X from Cyclades Corporation (http://www.cyclades.com and
7956 http://www.cyclades.com.br) is an intelligent multiprotocol WAN
7957 adapter with data transfer rates up to 512 Kbps. These cards support
7958 the X.25 and SNA related protocols. If you have one or more of these
7959 cards, say Y to this option. The next questions will ask you about
7960 the protocols you want the driver to support (for now only X.25 is
7963 While no documentation is available at this time please grab the
7964 wanconfig tarball in http://www.conectiva.com.br/~acme/cycsyn-devel
7965 (with minor changes to make it compile with the current wanrouter
7966 include files; efforts are being made to use the original package
7967 available at ftp://ftp.sangoma.com ).
7969 Feel free to contact me or the cycsyn-devel mailing list at
7970 acme@conectiva.com.br and cycsyn-devel@bazar.conectiva.com.br for
7971 additional details, I hope to have documentation available as soon
7972 as possible. (Cyclades Brazil is writing the Documentation).
7974 The driver will be compiled as a module ( = code which can be
7975 inserted in and removed from the running kernel whenever you want).
7976 The module will be called cyclomx.o. For general information about
7977 modules read Documentation/modules.txt.
7979 Cyclom 2X X.25 support
7981 Say Y to this option if you are planning to connect a Cyclom 2X card
7984 If you say N, the X.25 support will not be included in the driver
7985 (saves about 11 KB of kernel memory).
7987 Ethernet (10 or 100Mbit)
7989 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
7990 type of Local Area Network (LAN) in universities and companies.
7992 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
7993 coaxial cable, linking computers in a chain), 10BASE-T or twisted
7994 pair (10 Mbps over twisted pair cable, linking computers to central
7995 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
7996 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
7997 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
7998 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
7999 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
8000 Ethernet (1 Gbps over optical fiber or short copper links).
8002 If your Linux machine will be connected to an Ethernet and you have
8003 an Ethernet network interface card (NIC) installed in your computer,
8004 say Y here and read the Ethernet-HOWTO, available from
8005 http://www.linuxdoc.org/docs.html#howto . You will then also have
8006 to say Y to the driver for your particular NIC.
8008 Note that the answer to this question won't directly affect the
8009 kernel: saying N will just cause this configure script to skip all
8010 the questions about Ethernet network cards. If unsure, say N.
8012 Western Digital/SMC cards
8013 CONFIG_NET_VENDOR_SMC
8014 If you have a network (Ethernet) card belonging to this class, say Y
8015 and read the Ethernet-HOWTO, available from
8016 http://www.linuxdoc.org/docs.html#howto .
8018 Note that the answer to this question doesn't directly affect the
8019 kernel: saying N will just cause this configure script to skip all
8020 the questions about Western Digital cards. If you say Y, you will be
8021 asked for your specific card in the following questions.
8025 If you have a network (Ethernet) card of this type, say Y and read
8026 the Ethernet-HOWTO, available from
8027 http://www.linuxdoc.org/docs.html#howto .
8029 This driver is also available as a module ( = code which can be
8030 inserted in and removed from the running kernel whenever you want).
8031 The module will be called wd.o. If you want to compile it as a
8032 module, say M here and read Documentation/modules.txt as well as
8033 Documentation/networking/net-modules.txt.
8035 SMC Ultra MCA support
8037 If you have a network (Ethernet) card of this type and are running
8038 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
8039 available from http://www.linuxdoc.org/docs.html#howto .
8041 This driver is also available as a module ( = code which can be
8042 inserted in and removed from the running kernel whenever you want).
8043 The module will be called smc-mca.o. If you want to compile it as a
8044 module, say M here and read Documentation/modules.txt as well as
8045 Documentation/networking/net-modules.txt.
8049 If you have a network (Ethernet) card of this type, say Y and read
8050 the Ethernet-HOWTO, available from
8051 http://www.linuxdoc.org/docs.html#howto .
8053 Important: There have been many reports that, with some motherboards
8054 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
8055 such as some BusLogic models) causes corruption problems with many
8056 operating systems. The Linux smc-ultra driver has a work-around for
8057 this but keep it in mind if you have such a SCSI card and have
8060 This driver is also available as a module ( = code which can be
8061 inserted in and removed from the running kernel whenever you want).
8062 The module will be called smc-ultra.o. If you want to compile it as
8063 a module, say M here and read Documentation/modules.txt as well as
8064 Documentation/networking/net-modules.txt.
8066 SMC Ultra32 EISA support
8068 If you have a network (Ethernet) card of this type, say Y and read
8069 the Ethernet-HOWTO, available from
8070 http://www.linuxdoc.org/docs.html#howto .
8072 This driver is also available as a module ( = code which can be
8073 inserted in and removed from the running kernel whenever you want).
8074 The module will be called smc-ultra32.o. If you want to compile it
8075 as a module, say M here and read Documentation/modules.txt as well
8076 as Documentation/networking/net-modules.txt.
8080 This is support for the SMC9xxx based Ethernet cards. Choose this
8081 option if you have a DELL laptop with the docking station, or
8082 another SMC9192/9194 based chipset. Say Y if you want it compiled
8083 into the kernel, and read the file
8084 Documentation/networking/smc9.txt and the Ethernet-HOWTO, available
8085 from http://www.linuxdoc.org/docs.html#howto .
8087 This driver is also available as a module ( = code which can be
8088 inserted in and removed from the running kernel whenever you
8089 want). The module will be called smc9194.o. If you want to compile
8090 it as a module, say M here and read Documentation/modules.txt as
8091 well as Documentation/networking/net-modules.txt.
8095 This driver is for NE2000 compatible PCI cards. It will not work
8096 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
8097 support" below). If you have a PCI NE2000 network (Ethernet) card,
8098 say Y and read the Ethernet-HOWTO, available from
8099 http://www.linuxdoc.org/docs.html#howto .
8101 This driver is also available as a module ( = code which can be
8102 inserted in and removed from the running kernel whenever you want).
8103 The module will be called ne2k-pci.o. If you want to compile it as a
8104 module, say M here and read Documentation/modules.txt as well as
8105 Documentation/networking/net-modules.txt.
8107 Racal-Interlan (Micom) NI cards
8108 CONFIG_NET_VENDOR_RACAL
8109 If you have a network (Ethernet) card belonging to this class, such
8110 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
8111 available from http://www.linuxdoc.org/docs.html#howto .
8113 Note that the answer to this question doesn't directly affect the
8114 kernel: saying N will just cause this configure script to skip all
8115 the questions about NI cards. If you say Y, you will be asked for
8116 your specific card in the following questions.
8118 NI5010 support (EXPERIMENTAL)
8120 If you have a network (Ethernet) card of this type, say Y and read
8121 the Ethernet-HOWTO, available from
8122 http://www.linuxdoc.org/docs.html#howto . Note that this is still
8125 This driver is also available as a module ( = code which can be
8126 inserted in and removed from the running kernel whenever you want).
8127 The module will be called ni5010.o. If you want to compile it as a
8128 module, say M here and read Documentation/modules.txt as well as
8129 Documentation/networking/net-modules.txt.
8133 If you have a network (Ethernet) card of this type, say Y and read
8134 the Ethernet-HOWTO, available from
8135 http://www.linuxdoc.org/docs.html#howto .
8137 This driver is also available as a module ( = code which can be
8138 inserted in and removed from the running kernel whenever you want).
8139 The module will be called ni52.o. If you want to compile it as a
8140 module, say M here and read Documentation/modules.txt as well as
8141 Documentation/networking/net-modules.txt.
8145 If you have a network (Ethernet) card of this type, say Y and read
8146 the Ethernet-HOWTO, available from
8147 http://www.linuxdoc.org/docs.html#howto .
8149 This driver is also available 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 ni65.o. If you want to compile it as a
8152 module, say M here and read Documentation/modules.txt as well as
8153 Documentation/networking/net-modules.txt.
8155 RealTek 8129 (not 8019/8029!) support (EXPERIMENTAL)
8157 This is a driver for the Fast Ethernet PCI network cards based on
8158 the RTL8129 chip. If you have one of those, say Y and
8159 read the Ethernet-HOWTO, available from
8160 http://www.linuxdoc.org/docs.html#howto .
8162 If you want to compile this driver as a module ( = code which can be
8163 inserted in and removed from the running kernel whenever you want),
8164 say M here and read Documentation/modules.txt. This is recommended.
8165 The module will be called rtl8129.o.
8167 RealTek RTL-8139 PCI Fast Ethernet Adapter support
8169 This is a driver for the Fast Ethernet PCI network cards based on
8170 the RTL8139 chips. If you have one of those, say Y and read
8171 Documentation/networking/8139too.txt as well as the Ethernet-HOWTO,
8172 available from http://www.linuxdoc.org/docs.html#howto .
8174 If you want to compile this driver as a module ( = code which can be
8175 inserted in and removed from the running kernel whenever you want),
8176 say M here and read Documentation/modules.txt. This is recommended.
8177 The module will be called 8139too.o.
8179 SiS 900 PCI Fast Ethernet Adapter support
8181 This is a driver for the Fast Ethernet PCI network cards based on
8182 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
8183 SiS 630 and SiS 540 chipsets. If you have one of those, say Y and
8184 read the Ethernet-HOWTO, available at
8185 http://www.linuxdoc.org/docs.html#howto . Please read
8186 Documentation/networking/sis900.txt and comments at the beginning of
8187 drivers/net/sis900.c for more information.
8189 This driver also supports AMD 79C901 HomePNA so that you can use
8190 your phone line as a network cable.
8192 If you want to compile this driver as a module ( = code which can be
8193 inserted in and removed from the running kernel whenever you want),
8194 say M here and read Documentation/modules.txt. This is recommended.
8195 The module will be called sis900.o.
8197 Packet Engines Yellowfin Gigabit-NIC support
8199 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
8200 adapter. This adapter is used by the Beowulf Linux cluster project.
8201 See http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html for
8202 more information about this driver in particular and Beowulf in
8205 If you want to compile this driver as a module ( = code which can be
8206 inserted in and removed from the running kernel whenever you want),
8207 say M here and read Documentation/modules.txt. This is recommended.
8208 The module will be called yellowfin.o.
8210 General Instruments Surfboard 1000
8212 This is a driver for the General Instrument (also known as
8213 NextLevel) SURFboard 1000 internal
8214 cable modem. This is an ISA card which is used by a number of cable
8215 TV companies to provide cable modem access. It's a one-way
8216 downstream-only cable modem, meaning that your upstream net link is
8217 provided by your regular phone modem.
8219 At present this driver only compiles as a module, so say M here if
8220 you have this card. The module will be called sb1000.o. Then read
8221 Documentation/networking/README.sb1000 for information on how to use
8222 this module, as it needs special ppp scripts for establishing a
8223 connection. Further documentation and the necessary scripts can be
8226 http://www.jacksonville.net/~fventuri/
8227 http://home.adelphia.net/~siglercm/sb1000.html
8228 http://linuxpower.cx/~cable/
8230 If you don't have this card, of course say N.
8232 Adaptec Starfire support (EXPERIMENTAL)
8233 CONFIG_ADAPTEC_STARFIRE
8234 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
8235 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
8236 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
8239 If you want to compile this driver as a module ( = code which can be
8240 inserted in and removed from the running kernel whenever you want),
8241 say M here and read Documentation/modules.txt. This is recommended.
8242 The module will be called starfile.o.
8244 Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support
8246 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
8247 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
8248 adapter. The driver allows for using the Jumbo Frame option (9000
8249 bytes/frame) however it requires that your switches can handle this
8250 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
8253 If you want to compile this driver as a module ( = code which can be
8254 inserted in and removed from the running kernel whenever you want),
8255 say M here and read Documentation/modules.txt. This is recommended.
8256 The module will be called acenic.o.
8258 Omit support for older Tigon I based AceNICs
8259 CONFIG_ACENIC_OMIT_TIGON_I
8260 Say Y here if you only have Tigon II based AceNICs and want to leave
8261 out support for the older Tigon I based cards which are no longer
8262 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
8263 version)). This will reduce the size of the driver object by
8264 app. 100KB. If you are not sure whether your card is a Tigon I or a
8265 Tigon II, say N here.
8267 The safe and default value for this is N.
8269 SysKonnect SK-98xx support
8271 Say Y here if you have a SysKonnect SK-98xx Gigabit Ethernet Server
8272 Adapter. The following adapters are supported by this driver:
8273 - SK-9841 (single link 1000Base-LX)
8274 - SK-9842 (dual link 1000Base-LX)
8275 - SK-9843 (single link 1000Base-SX)
8276 - SK-9844 (dual link 1000Base-SX)
8277 - SK-9821 (single link 1000Base-T)
8278 - SK-9822 (dual link 1000Base-T)
8279 The dual link adapters support a link-failover feature.
8280 Read Documentation/networking/sk98lin.txt for information about
8281 optional driver parameters.
8282 Questions concerning this driver may be addressed to:
8285 If you want to compile this driver as a module ( = code which can be
8286 inserted in and removed from the running kernel whenever you want),
8287 say M here and read Documentation/modules.txt. This is recommended.
8288 The module will be called sk98lin.o.
8290 MyriCOM Gigabit Ethernet support
8292 This driver supports MyriCOM Sbus gigabit ethernet cards.
8294 If you want to compile this driver as a module ( = code which can be
8295 inserted in and removed from the running kernel whenever you want),
8296 say M here and read Documentation/modules.txt. This is recommended.
8297 The module will be called myri_sbus.o.
8299 AMD LANCE and PCnet (AT1500 and NE2100) support
8301 If you have a network (Ethernet) card of this type, say Y and read
8302 the Ethernet-HOWTO, available from
8303 http://www.linuxdoc.org/docs.html#howto . Some LinkSys cards are
8306 If you want to compile this driver as a module ( = code which can be
8307 inserted in and removed from the running kernel whenever you want),
8308 say M here and read Documentation/modules.txt. This is recommended.
8309 The module will be called lance.o.
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 .
8318 CONFIG_NET_VENDOR_3COM
8319 If you have a network (Ethernet) card belonging to this class, say Y
8320 and read the Ethernet-HOWTO, available from
8321 http://www.linuxdoc.org/docs.html#howto .
8323 Note that the answer to this question doesn't directly affect the
8324 kernel: saying N will just cause this configure script to skip all
8325 the questions about 3COM cards. If you say Y, you will be asked for
8326 your specific card in the following questions.
8330 If you have a network (Ethernet) card of this type, say Y and read
8331 the Ethernet-HOWTO, available from
8332 http://www.linuxdoc.org/docs.html#howto . Also, consider buying a
8333 new card, since the 3c501 is slow, broken, and obsolete: you will
8334 have problems. Some people suggest to ping ("man ping") a nearby
8335 machine every minute ("man cron") when using this card.
8337 This driver is also available as a module ( = code which can be
8338 inserted in and removed from the running kernel whenever you want).
8339 The module will be called 3c501.o. If you want to compile it as a
8340 module, say M here and read Documentation/modules.txt as well as
8341 Documentation/networking/net-modules.txt.
8345 If you have a network (Ethernet) card of this type, say Y and read
8346 the Ethernet-HOWTO, available from
8347 http://www.linuxdoc.org/docs.html#howto .
8349 This driver is also available as a module ( = code which can be
8350 inserted in and removed from the running kernel whenever you want).
8351 The module will be called 3c503.o. If you want to compile it as a
8352 module, say M here and read Documentation/modules.txt as well as
8353 Documentation/networking/net-modules.txt.
8357 Information about this network (Ethernet) card can be found in
8358 Documentation/networking/3c505.txt. If you have a card of this type,
8359 say Y and read the Ethernet-HOWTO, available from
8360 http://www.linuxdoc.org/docs.html#howto .
8362 If you want to compile this as a module ( = code which can be
8363 inserted in and removed from the running kernel whenever you want),
8364 say M here and read Documentation/modules.txt as well as
8365 Documentation/networking/net-modules.txt. The module will be called
8368 3c507 support (EXPERIMENTAL)
8370 If you have a network (Ethernet) card of this type, say Y and read
8371 the Ethernet-HOWTO, available from
8372 http://www.linuxdoc.org/docs.html#howto .
8374 This driver is also available as a module ( = code which can be
8375 inserted in and removed from the running kernel whenever you want).
8376 The module will be called 3c507.o. If you want to compile it as a
8377 module, say M here and read Documentation/modules.txt as well as
8378 Documentation/networking/net-modules.txt.
8382 If you have a network (Ethernet) card of this type, say Y and read
8383 the Ethernet-HOWTO, available from
8384 http://www.linuxdoc.org/docs.html#howto .
8386 This driver is also available as a module ( = code which can be
8387 inserted in and removed from the running kernel whenever you want).
8388 The module will be called 3c523.o. If you want to compile it as a
8389 module, say M here and read Documentation/modules.txt as well as
8390 Documentation/networking/net-modules.txt.
8394 If you have a network (Ethernet) card of this type, say Y and read
8395 the Ethernet-HOWTO, available from
8396 http://www.linuxdoc.org/docs.html#howto .
8398 This driver is also available as a module ( = code which can be
8399 inserted in and removed from the running kernel whenever you want).
8400 The module will be called 3c527.o. If you want to compile it as a
8401 module, say M here and read Documentation/modules.txt as well as
8402 Documentation/networking/net-modules.txt.
8406 If you have a network (Ethernet) card belonging to the 3Com
8407 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
8408 from http://www.linuxdoc.org/docs.html#howto .
8410 If your card is not working you may need to use the DOS
8411 setup disk to disable Plug & Play mode, and to select the default
8414 If you want to compile this as a module ( = code which can be
8415 inserted in and removed from the running kernel whenever you want),
8416 say M here and read Documentation/modules.txt as well as
8417 Documentation/networking/net-modules.txt. The module will be called
8420 3c515 ISA Fast EtherLink
8422 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
8423 network card, say Y and read the Ethernet-HOWTO, available from
8424 http://www.linuxdoc.org/docs.html#howto .
8426 If you want to compile this as a module ( = code which can be
8427 inserted in and removed from the running kernel whenever you want),
8428 say M here and read Documentation/modules.txt as well as
8429 Documentation/networking/net-modules.txt. The module will be called
8432 3c59x/3c90x/3c575_Cardbus series "Vortex/Boomerang/Cyclone" support
8434 This option enables driver support for a large number of 10mbps and
8435 10/100mbps EISA, PCI and PCMCIA 3Com network cards:
8437 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
8438 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
8439 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
8440 "Tornado" (3c905) PCI
8441 "Hurricane" (3c555/3cSOHO) PCI
8443 If you have such a card, say Y and read the Ethernet-HOWTO, available
8444 from http://www.linuxdoc.org/docs.html#howto . More specific
8445 information is in Documentation/networking/vortex.txt and in the
8446 comments at the beginning of drivers/net/3c59x.c.
8448 If you want to compile this as a module ( = code which can be
8449 inserted in and removed from the running kernel whenever you want),
8450 say M here and read Documentation/modules.txt as well as
8451 Documentation/networking/net-modules.txt.
8455 If your network (Ethernet) card hasn't been mentioned yet and its
8456 bus system (that's the way the cards talks to the other components
8457 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
8458 Make sure you know the name of your card. Read the Ethernet-HOWTO,
8459 available from http://www.linuxdoc.org/docs.html#howto .
8463 Note that the answer to this question doesn't directly affect the
8464 kernel: saying N will just cause this configure script to skip all
8465 the remaining ISA network card questions. If you say Y, you will be
8466 asked for your specific card in the following questions.
8468 Generic ARCnet support
8470 If you have a network card of this type, say Y and check out the
8471 (arguably) beautiful poetry in Documentation/networking/arcnet.txt.
8473 You need both this driver, and the driver for the particular ARCnet
8474 chipset of your card. If you don't know, then it's probably a
8475 COM90xx type card, so say Y (or M) to "ARCnet COM90xx chipset
8478 You might also want to have a look at the Ethernet-HOWTO, available
8479 from http://www.linuxdoc.org/docs.html#howto (even though ARCnet
8480 is not really Ethernet).
8482 This driver is also available as a module ( = code which can be
8483 inserted in and removed from the running kernel whenever you want).
8484 The module will be called arcnet.o. If you want to compile it as a
8485 module, say M here and read Documentation/modules.txt as well as
8486 Documentation/networking/net-modules.txt.
8488 Enable arc0e (ARCnet "ether-encap" packet format)
8490 This allows you to use "Ethernet encapsulation" with your ARCnet
8491 card via the virtual arc0e device. You only need arc0e if you want
8492 to talk to nonstandard ARCnet software, specifically,
8493 DOS/Windows-style "NDIS" drivers. You do not need to say Y here to
8494 communicate with industry-standard RFC1201 implementations, like the
8495 arcether.com packet driver or most DOS/Windows ODI drivers. RFC1201
8496 is included automatically as the arc0 device. Please read the
8497 ARCnet documentation in Documentation/networking/arcnet.txt for more
8498 information about using arc0e and arc0s.
8500 Enable old ARCNet packet format (RFC 1051)
8502 This allows you to use RFC1051 with your ARCnet card via the virtual
8503 arc0s device. You only need arc0s if you want to talk to ARCnet
8504 software complying with the "old" standard, specifically, the DOS
8505 arcnet.com packet driver, Amigas running AmiTCP, and some variants
8506 of NetBSD. You do not need to say Y here to communicate with
8507 industry-standard RFC1201 implementations, like the arcether.com
8508 packet driver or most DOS/Windows ODI drivers. RFC1201 is included
8509 automatically as the arc0 device. Please read the ARCnet
8510 documentation in Documentation/networking/arcnet.txt for more
8511 information about using arc0e and arc0s.
8513 ARCnet COM90xx (normal) chipset driver
8514 CONFIG_ARCNET_COM90xx
8515 This is the chipset driver for the standard COM90xx cards. If you
8516 have always used the old ARCnet driver without knowing what type of
8517 card you had, this is probably the one for you.
8519 This driver is also available as a module ( = code which can be
8520 inserted in and removed from the running kernel whenever you want).
8521 The module will be called com90xx.o. If you want to compile it as a
8522 module, say M here and read Documentation/modules.txt as well as
8523 Documentation/networking/net-modules.txt.
8525 ARCnet COM90xx (IO mapped) chipset driver
8526 CONFIG_ARCNET_COM90xxIO
8527 This is the chipset driver for the COM90xx cards, using them in
8528 IO-mapped mode instead of memory-mapped mode. This is slower than
8529 the normal driver. Only use it if your card doesn't support shared
8532 This driver is also available as a module ( = code which can be
8533 inserted in and removed from the running kernel whenever you want).
8534 The module will be called com90io.o. If you want to compile it as a
8535 module, say M here and read Documentation/modules.txt as well as
8536 Documentation/networking/net-modules.txt.
8538 ARCnet COM90xx (RIM I) chipset driver
8540 This is yet another chipset driver for the COM90xx cards, but this
8541 time only using memory-mapped mode, and no IO ports at all. This
8542 driver is completely untested, so if you have one of these cards,
8543 please mail dwmw2@infradead.org, especially if it works!
8545 This driver is also available as a module ( = code which can be
8546 inserted in and removed from the running kernel whenever you
8547 want). The module will be called arc-rimi.o. If you want to compile
8548 it as a module, say M here and read Documentation/modules.txt as
8549 well as Documentation/networking/net-modules.txt.
8551 ARCnet COM20020 chipset driver
8552 CONFIG_ARCNET_COM20020
8553 This is the driver for the new COM20020 chipset. It supports such
8554 things as promiscuous mode, so packet sniffing is possible, and
8555 extra diagnostic information.
8557 This driver is also available as a module ( = code which can be
8558 inserted in and removed from the running kernel whenever you want).
8559 The module will be called com20020.o. If you want to compile it as a
8560 module, say M here and read Documentation/modules.txt as well as
8561 Documentation/networking/net-modules.txt.
8563 Cabletron E21xx support
8565 If you have a network (Ethernet) card of this type, say Y and read
8566 the Ethernet-HOWTO, available from
8567 http://www.linuxdoc.org/docs.html#howto .
8569 This driver is also available as a module ( = code which can be
8570 inserted in and removed from the running kernel whenever you want).
8571 The module will be called e2100.o. If you want to compile it as a
8572 module, say M here and read Documentation/modules.txt as well as
8573 Documentation/networking/net-modules.txt.
8577 Support for CS89x0 chipset based Ethernet cards. If you have a
8578 network (Ethernet) card of this type, say Y and read the
8579 Ethernet-HOWTO, available from
8580 http://www.linuxdoc.org/docs.html#howto as well as
8581 Documentation/networking/cs89x0.txt.
8583 If you want to compile this as a module ( = code which can be
8584 inserted in and removed from the running kernel whenever you want),
8585 say M here and read Documentation/modules.txt as well as
8586 Documentation/networking/net-modules.txt. The module will be called
8591 If you have a network (Ethernet) card of this type, say Y and read
8592 the Ethernet-HOWTO, available from
8593 http://www.linuxdoc.org/docs.html#howto as well as
8594 drivers/net/depca.c.
8596 If you want to compile this as a module ( = code which can be
8597 inserted in and removed from the running kernel whenever you want),
8598 say M here and read Documentation/modules.txt as well as
8599 Documentation/networking/net-modules.txt. The module will be called
8602 EtherWorks 3 support
8604 This driver supports the DE203, DE204 and DE205 network (Ethernet)
8605 cards. If this is for you, say Y and read
8606 Documentation/networking/ewrk3.txt in the kernel source as well as
8607 the Ethernet-HOWTO, available from
8608 http://www.linuxdoc.org/docs.html#howto .
8610 If you want to compile this as a module ( = code which can be
8611 inserted in and removed from the running kernel whenever you want),
8612 say M here and read Documentation/modules.txt as well as
8613 Documentation/networking/net-modules.txt. The module will be called
8618 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
8619 is for you, read the Ethernet-HOWTO, available from
8620 http://www.linuxdoc.org/docs.html#howto .
8622 If you want to compile this as a module ( = code which can be
8623 inserted in and removed from the running kernel whenever you want),
8624 say M here and read Documentation/modules.txt as well as
8625 Documentation/networking/net-modules.txt. The module will be called
8630 If you have a network (Ethernet) card of this type, say Y and read
8631 the Ethernet-HOWTO, available from
8632 http://www.linuxdoc.org/docs.html#howto .
8634 This driver is also available as a module ( = code which can be
8635 inserted in and removed from the running kernel whenever you want).
8636 If you want to compile it as a module, say M here and read
8637 Documentation/modules.txt as well as
8638 Documentation/networking/net-modules.txt. The module will be called
8641 FMV-181/182/183/184 support
8643 If you have a Fujitsu FMV-181/182/183/184 network (Ethernet) card,
8644 say Y and read the Ethernet-HOWTO, available from
8645 http://www.linuxdoc.org/docs.html#howto .
8647 If you use an FMV-183 or FMV-184 and it is not working, you may need
8648 to disable Plug & Play mode of the card.
8650 This driver is also available as a module ( = code which can be
8651 inserted in and removed from the running kernel whenever you want).
8652 The module will be called fmv18x.o. If you want to compile it as a
8653 module, say M here and read Documentation/modules.txt as well as
8654 Documentation/networking/net-modules.txt.
8656 EtherExpress PRO support
8658 If you have a network (Ethernet) card of this type, say Y. This
8659 driver supports intel i82595{FX,TX} based boards. Note however
8660 that the EtherExpress PRO/100 Ethernet card has its own separate
8661 driver. Please read the Ethernet-HOWTO, available from
8662 http://www.linuxdoc.org/docs.html#howto .
8664 This driver is also available as a module ( = code which can be
8665 inserted in and removed from the running kernel whenever you want).
8666 The module will be called eepro.o. If you want to compile it as a
8667 module, say M here and read Documentation/modules.txt as well as
8668 Documentation/networking/net-modules.txt.
8670 EtherExpress support
8672 If you have an EtherExpress16 network (Ethernet) card, say Y and
8673 read the Ethernet-HOWTO, available from
8674 http://www.linuxdoc.org/docs.html#howto . Note that the Intel
8675 EtherExpress16 card used to be regarded as a very poor choice
8676 because the driver was very unreliable. We now have a new driver
8677 that should do better.
8679 If you want to compile this driver as a module ( = code which can be
8680 inserted in and removed from the running kernel whenever you want),
8681 say M here and read Documentation/modules.txt as well as
8682 Documentation/networking/net-modules.txt. The module will be called
8685 HP PCLAN+ (27247B and 27252A) support
8687 If you have a network (Ethernet) card of this type, say Y and read
8688 the Ethernet-HOWTO, available from
8689 http://www.linuxdoc.org/docs.html#howto .
8691 This driver is also available as a module ( = code which can be
8692 inserted in and removed from the running kernel whenever you want).
8693 The module will be called hp-plus.o. If you want to compile it as a
8694 module, say M here and read Documentation/modules.txt as well as
8695 Documentation/networking/net-modules.txt.
8697 HP PCLAN (27245 and other 27xxx series) support
8699 If you have a network (Ethernet) card of this type, say Y and read
8700 the Ethernet-HOWTO, available from
8701 http://www.linuxdoc.org/docs.html#howto .
8703 This driver is also available as a module ( = code which can be
8704 inserted in and removed from the running kernel whenever you want).
8705 The module will be called hp.o. If you want to compile it as a
8706 module, say M here and read Documentation/modules.txt as well as
8707 Documentation/networking/net-modules.txt.
8709 HP 10/100VG PCLAN (ISA, EISA, PCI) support
8711 If you have a network (Ethernet) card of this type, say Y and read
8712 the Ethernet-HOWTO, available from
8713 http://www.linuxdoc.org/docs.html#howto .
8715 If you want to compile this as a module ( = code which can be
8716 inserted in and removed from the running kernel whenever you want),
8717 say M here and read Documentation/modules.txt as well as
8718 Documentation/networking/net-modules.txt. The module will be called
8721 NE2000/NE1000 support
8723 If you have a network (Ethernet) card of this type, say Y and read
8724 the Ethernet-HOWTO, available from
8725 http://www.linuxdoc.org/docs.html#howto . Many Ethernet cards
8726 without a specific driver are compatible with NE2000.
8728 If you have a PCI NE2000 card however, say N here and Y to "PCI
8729 NE2000 support", above. If you have a NE2000 card and are running on
8730 an MCA system (a bus system used on some IBM PS/2 computers and
8731 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
8734 This driver is also available as a module ( = code which can be
8735 inserted in and removed from the running kernel whenever you want).
8736 The module will be called ne.o. If you want to compile it as a
8737 module, say M here and read Documentation/modules.txt as well as
8738 Documentation/networking/net-modules.txt.
8740 National Semiconductor DP83810 series PCI Ethernet support
8742 This driver is for the National Semiconductor DP83810 series,
8743 including the 83815 chip.
8744 More specific information and updates are available from
8745 http://www.scyld.com/network/natsemi.html
8749 If you have a network (Ethernet) card of this type, say Y and read
8750 the Ethernet-HOWTO, available from
8751 http://www.linuxdoc.org/docs.html#howto .
8753 NE/2 (ne2000 MCA version) support
8755 If you have a network (Ethernet) card of this type, say Y and read
8756 the Ethernet-HOWTO, available from
8757 http://www.linuxdoc.org/docs.html#howto .
8759 This driver is also available as a module ( = code which can be
8760 inserted in and removed from the running kernel whenever you want).
8761 The module will be called ne2.o. If you want to compile it as a
8762 module, say M here and read Documentation/modules.txt as well as
8763 Documentation/networking/net-modules.txt.
8767 These are Micro Channel ethernet adapters. You need to say Y to "MCA
8768 support" in order to use this driver. Supported cards are the SKnet
8769 Junior MC2 and the SKnet MC2(+). The driver automatically
8770 distinguishes between the two cards. Note that using multiple boards
8771 of different type hasn't been tested with this driver. Say Y if you
8772 have one of these ethernet adapters.
8774 This driver is also available as a module ( = code which can be
8775 inserted in and removed from the running kernel whenever you want).
8776 The module is called sk_mca.o. If you want to compile it as a
8777 module, say M here and read Documentation/modules.txt as well as
8778 Documentation/networking/net-modules.txt.
8780 IBM LAN Adapter/A support
8782 This is a Micro Channel ethernet adapter. You need to set CONFIG_MCA
8783 to use this driver. It is both available as an in-kernel driver and
8784 as a module ( = code which can be inserted in and removed from the
8785 running kernel whenever you want). If you want to compile it as a module,
8786 say M here and read Documentation/modules.txt as well as
8787 Documentation/networking/net-modules.txt. If you plan to use more than
8788 one network card under linux, read the Multiple-Ethernet-mini-HOWTO,
8789 available from sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. The only
8790 currently supported card is the IBM LAN Adapter/A for Ethernet. It will
8791 both support 16K and 32K memory windows, however a 32K window gives
8792 a better security against packet losses. Usage of multiple boards with
8793 this driver should be possible, but has not been tested up to now due
8794 to lack of hardware.
8796 EISA, VLB, PCI and on board controllers
8798 This is another class of network cards which attach directly to the
8799 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
8800 available from http://www.linuxdoc.org/docs.html#howto .
8802 Note that the answer to this question doesn't directly affect the
8803 kernel: saying N will just cause this configure script to skip all
8804 the questions about this class of network cards. If you say Y, you
8805 will be asked for your specific card in the following questions. If
8806 you are unsure, say Y.
8808 AMD PCnet32 (VLB and PCI) support
8810 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
8811 answer Y here and read the Ethernet-HOWTO, available from
8812 http://www.linuxdoc.org/docs.html#howto .
8814 This driver is also available as a module ( = code which can be
8815 inserted in and removed from the running kernel whenever you want).
8816 The module will be called pcnet32.o. If you want to compile it as a
8817 module, say M here and read Documentation/modules.txt as well as
8818 Documentation/networking/net-modules.txt.
8820 Ansel Communications EISA 3200 support
8822 If you have a network (Ethernet) card of this type, say Y and read
8823 the Ethernet-HOWTO, available from
8824 http://www.linuxdoc.org/docs.html#howto .
8826 This driver is also available as a module ( = code which can be
8827 inserted in and removed from the running kernel whenever you want).
8828 The module will be called ac3200.o. If you want to compile it as a
8829 module, say M here and read Documentation/modules.txt as well as
8830 Documentation/networking/net-modules.txt.
8832 Mylex EISA LNE390A/LNE390B support (EXPERIMENTAL)
8834 If you have a network (Ethernet) card of this type, say Y and read
8835 the Ethernet-HOWTO, available from
8836 http://www.linuxdoc.org/docs.html#howto .
8838 This driver is also available as a module ( = code which can be
8839 inserted in and removed from the running kernel whenever you want).
8840 The module will be called lne390.o. If you want to compile it as a
8841 module, say M here and read Documentation/modules.txt as well as
8842 Documentation/networking/net-modules.txt.
8844 Novell/Eagle/Microdyne NE3210 EISA support
8846 If you have a network (Ethernet) card of this type, say Y and read
8847 the Ethernet-HOWTO, available from
8848 http://www.linuxdoc.org/docs.html#howto . Note that this driver
8849 will NOT WORK for NE3200 cards as they are completely different.
8851 This driver is also available as a module ( = code which can be
8852 inserted in and removed from the running kernel whenever you want).
8853 The module will be called ne3210.o. If you want to compile it as a
8854 module, say M here and read Documentation/modules.txt as well as
8855 Documentation/networking/net-modules.txt.
8857 Apricot Xen-II on board Ethernet
8859 If you have a network (Ethernet) controller of this type, say Y and
8860 read the Ethernet-HOWTO, available from
8861 http://www.linuxdoc.org/docs.html#howto .
8863 If you want to compile this as a module ( = code which can be
8864 inserted in and removed from the running kernel whenever you want),
8865 say M here and read Documentation/modules.txt as well as
8866 Documentation/networking/net-modules.txt. The module will be called
8869 Generic DECchip & DIGITAL EtherWORKS PCI/EISA
8871 This is support for the DIGITAL series of PCI/EISA Ethernet cards.
8872 These include the DE425, DE434, DE435, DE450 and DE500 models. If
8873 you have a network card of this type, say Y and read the
8874 Ethernet-HOWTO, available from
8875 http://www.linuxdoc.org/docs.html#howto . More specific
8876 information is contained in Documentation/networking/de4x5.txt.
8878 This driver is also available as a module ( = code which can be
8879 inserted in and removed from the running kernel whenever you want).
8880 The module will be called de4x5.o. If you want to compile it as a
8881 module, say M here and read Documentation/modules.txt as well as
8882 Documentation/networking/net-modules.txt.
8884 DECchip Tulip (dc21x4x) PCI support
8886 This driver is developed for the SMC EtherPower series Ethernet
8887 cards and also works with cards based on the DECchip
8888 21040/21041/21140 (Tulip series) chips. Some LinkSys PCI cards are
8889 of this type. (If your card is NOT SMC EtherPower 10/100 PCI
8890 (smc9332dst), you can also try the driver for "Generic DECchip"
8891 cards, above. However, most people with a network card of this type
8892 will say Y here.) Do read the Ethernet-HOWTO, available from
8893 http://www.linuxdoc.org/docs.html#howto . More specific
8894 information is contained in Documentation/networking/tulip.txt.
8896 This driver is also available as a module ( = code which can be
8897 inserted in and removed from the running kernel whenever you want).
8898 The module will be called tulip.o. If you want to compile it as a
8899 module, say M here and read Documentation/modules.txt as well as
8900 Documentation/networking/net-modules.txt.
8902 Digi Intl. RightSwitch support
8904 This is support for the Digi International RightSwitch series of
8905 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
8906 models. If you have a network card of this type, say Y and read the
8907 Ethernet-HOWTO, available from
8908 http://www.linuxdoc.org/docs.html#howto . More specific
8909 information is contained in Documentation/networking/dgrs.txt.
8911 This driver is also available as a module ( = code which can be
8912 inserted in and removed from the running kernel whenever you want).
8913 The module will be called dgrs.o. If you want to compile it as a
8914 module, say M here and read Documentation/modules.txt as well as
8915 Documentation/networking/net-modules.txt.
8917 EtherExpress PRO/100 support
8919 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
8920 card, say Y and read the Ethernet-HOWTO, available from
8921 http://www.linuxdoc.org/docs.html#howto .
8923 This driver is also available as a module ( = code which can be
8924 inserted in and removed from the running kernel whenever you want).
8925 The module will be called eepro100.o. If you want to compile it as a
8926 module, say M here and read Documentation/modules.txt as well as
8927 Documentation/networking/net-modules.txt.
8929 Enable Power Management (EXPERIMENTAL)
8931 Many Intel EtherExpress PRO/100 PCI network cards are capable
8932 of providing power management capabilities. To make use of these
8933 capabilities, say Y.
8935 WARNING: This option is intended for kernel developers and testers.
8936 It is still very experimental, with some people reporting complete
8939 It is recommended to say N here.
8941 ICL EtherTeam 16i/32 support (EXPERIMENTAL)
8943 If you have a network (Ethernet) card of this type, say Y and read
8944 the Ethernet-HOWTO, available from
8945 http://www.linuxdoc.org/docs.html#howto .
8947 This driver is also available as a module ( = code which can be
8948 inserted in and removed from the running kernel whenever you want).
8949 The module will be called eth16i.o. If you want to compile it as a
8950 module, say M here and read Documentation/modules.txt as well as
8951 Documentation/networking/net-modules.txt.
8953 TI ThunderLAN support (EXPERIMENTAL)
8955 If you have a PCI Ethernet network card based on the ThunderLAN chip
8956 which is supported by this driver, say Y and read the
8957 Ethernet-HOWTO, available from
8958 http://www.linuxdoc.org/docs.html#howto .
8960 Devices currently supported by this driver are Compaq Netelligent,
8961 Compaq NetFlex and Olicom cards. Please read the file
8962 Documentation/networking/tlan.txt for more details.
8964 This driver is also available as a module ( = code which can be
8965 inserted in and removed from the running kernel whenever you want).
8966 The module will be called tlan.o. If you want to compile it as a
8967 module, say M here and read Documentation/modules.txt as well as
8968 Documentation/networking/net-modules.txt.
8970 Please email feedback to torben.mathiasen@compaq.com.
8974 If you have a VIA "rhine" based network card (Rhine-I (3043) or
8975 Rhine-2 (VT86c100A)), say Y here.
8977 This driver is also available as a module ( = code which can be
8978 inserted in and removed from the running kernel whenever you want).
8979 The module will be called via-rhine.o. If you want to compile it as
8980 a module, say M here and read Documentation/modules.txt as well as
8981 Documentation/networking/net-modules.txt.
8983 PCI DM9102(A)/DM9132/DM9801 support
8985 This driver is for DM9102(A)/DM9132/DM9801 compatible PCI cards from
8986 Davicom ( http://www.davicom.com.tw ). If you have such a network
8987 (Ethernet) card, say Y. Some information is contained in the file
8988 Documentation/networking/dmfe.txt.
8990 This driver is also available as a module ( = code which can be
8991 inserted in and removed from the running kernel whenever you want).
8992 The module will be called dmfe.o. If you want to compile it as a
8993 module, say M here and read Documentation/modules.txt as well as
8994 Documentation/networking/net-modules.txt.
8996 Racal-Interlan EISA ES3210 support (EXPERIMENTAL)
8998 If you have a network (Ethernet) card of this type, say Y and read
8999 the Ethernet-HOWTO, available from
9000 http://www.linuxdoc.org/docs.html#howto .
9002 This driver is also available as a module ( = code which can be
9003 inserted in and removed from the running kernel whenever you want).
9004 The module will be called es3210.o. If you want to compile it as a
9005 module, say M here and read Documentation/modules.txt as well as
9006 Documentation/networking/net-modules.txt.
9008 SMC EtherPower II (EXPERIMENTAL)
9010 If you have an SMC EtherPower II 9432 PCI Ethernet network card
9011 which is based on the SMC83c170, say Y and read the Ethernet-HOWTO,
9012 available from http://www.linuxdoc.org/docs.html#howto .
9014 This driver is also available as a module ( = code which can be
9015 inserted in and removed from the running kernel whenever you want).
9016 The module will be called epic100.o. If you want to compile it as a
9017 module, say M here and read Documentation/modules.txt as well as
9018 Documentation/networking/net-modules.txt.
9020 SGI Seeq ethernet controller support
9022 Say Y here if you have an Seeq based Ethernet network card. This is
9023 used in many Silicon Graphics machines.
9025 Zenith Z-Note support (EXPERIMENTAL)
9027 The Zenith Z-Note notebook computer has a built-in network
9028 (Ethernet) card, and this is the Linux driver for it. Note that the
9029 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
9030 by this driver. Read the Ethernet-HOWTO, available from
9031 http://www.linuxdoc.org/docs.html#howto .
9033 Pocket and portable adapters
9035 Cute little network (Ethernet) devices which attach to the parallel
9036 port ("pocket adapters"), commonly used with laptops. If you have
9037 one of those, say Y and read the Ethernet-HOWTO, available from
9038 http://www.linuxdoc.org/docs.html#howto .
9040 If you want to plug a network (or some other) card into the PCMCIA
9041 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
9042 credit card size extension cards used by all modern laptops), you
9043 need the pcmcia-cs package (location contained in the file
9044 Documentation/Changes) and you can say N here.
9046 Laptop users should read the Linux Laptop home page at
9047 http://www.cs.utexas.edu/users/kharker/linux-laptop/ .
9049 Note that the answer to this question doesn't directly affect the
9050 kernel: saying N will just cause this configure script to skip all
9051 the questions about this class of network devices. If you say Y, you
9052 will be asked for your specific device in the following questions.
9054 AT-LAN-TEC/RealTek pocket adapter support
9056 This is a network (Ethernet) device which attaches to your parallel
9057 port. Read drivers/net/atp.c as well as the Ethernet-HOWTO,
9058 available from http://www.linuxdoc.org/docs.html#howto , if you
9059 want to use this. If you intend to use this driver, you should have
9060 said N to the "Parallel printer support", because the two drivers
9061 don't like each other.
9063 If you want to compile this driver as a module however ( = code
9064 which can be inserted in and removed from the running kernel
9065 whenever you want), say M here and read Documentation/modules.txt.
9066 The module will be called atp.o.
9068 D-Link DE600 pocket adapter support
9070 This is a network (Ethernet) device which attaches to your parallel
9071 port. Read Documentation/networking/DLINK.txt as well as the
9072 Ethernet-HOWTO, available from
9073 http://www.linuxdoc.org/docs.html#howto , if you want to use
9074 this. It is possible to have several devices share a single parallel
9075 port and it is safe to compile the corresponding drivers into the
9078 If you want to compile this driver as a module however ( = code
9079 which can be inserted in and removed from the running kernel
9080 whenever you want), say M here and read Documentation/modules.txt.
9081 The module will be called de600.o.
9083 D-Link DE620 pocket adapter support
9085 This is a network (Ethernet) device which attaches to your parallel
9086 port. Read Documentation/networking/DLINK.txt as well as the
9087 Ethernet-HOWTO, available from
9088 http://www.linuxdoc.org/docs.html#howto , if you want to use
9089 this. It is possible to have several devices share a single parallel
9090 port and it is safe to compile the corresponding drivers into the
9093 If you want to compile this driver as a module however ( = code
9094 which can be inserted in and removed from the running kernel
9095 whenever you want), say M here and read Documentation/modules.txt.
9096 The module will be called de620.o.
9098 Token Ring driver support
9100 Token Ring is IBM's way of communication on a local network; the
9101 rest of the world uses Ethernet. To participate on a Token Ring
9102 network, you need a special Token ring network card. If you are
9103 connected to such a Token Ring network and want to use your Token
9104 Ring card under Linux, say Y here and to the driver for your
9105 particular card below and read the Token-Ring mini-HOWTO, available
9106 from http://www.linuxdoc.org/docs.html#howto . Most people can
9109 IBM Tropic chipset based adapter support
9111 This is support for all IBM Token Ring cards that don't use DMA. If
9112 you have such a beast, say Y and read the Token-Ring mini-HOWTO,
9113 available from http://www.linuxdoc.org/docs.html#howto .
9115 Warning: this driver will almost definitely fail if more than one
9116 active Token Ring card is present.
9118 This driver is also available as a module ( = code which can be
9119 inserted in and removed from the running kernel whenever you want).
9120 The module will be called ibmtr.o. If you want to compile it as a
9121 module, say M here and read Documentation/modules.txt.
9123 IBM Olympic chipset PCI adapter support
9125 This is support for all non-Lanstreamer IBM PCI Token Ring Cards.
9126 Specifically this is all IBM PCI, PCI Wake On Lan, PCI II, PCI II
9127 Wake On Lan, and PCI 100/16/4 adapters.
9129 If you have such an adapter, say Y and read the Token-Ring
9130 mini-HOWTO, available from
9131 http://www.linuxdoc.org/docs.html#howto .
9133 This driver is also available as a module ( = code which can be
9134 inserted in and removed from the running kernel whenever you want).
9135 The module will will be called olympic.o. If you want to compile it
9136 as a module, say M here and read Documentation/modules.txt.
9138 Also read the file Documentation/networking/olympic.txt or check the
9139 Linux Token Ring Project site for the latest information at
9140 http://www.linuxtr.net .
9142 IBM Lanstreamer chipset PCI adapter support
9144 This is support for IBM Lanstreamer PCI Token Ring Cards.
9146 If you have such an adapter, say Y and read the Token-Ring
9147 mini-HOWTO available via FTP (user:anonymous) from
9148 ftp://metalab.unc/edu/pub/Linux/docs/HOWTO.
9150 This driver is also available as a modules ( = code which can be
9151 inserted in and removed from the running kernel whenever you want).
9152 The modules will be called lanstreamer.o. If you want to compile it
9153 as a module, say M here and read Documentation/modules.txt.
9155 Generic TMS380 Token Ring ISA/PCI/MCA/EISA adapter support
9157 This driver provides generic support for token ring adapters
9158 based on the Texas Instruments TMS380 series chipsets. This
9159 includes the SysKonnect TR4/16(+) ISA (SK-4190), SysKonnect
9160 TR4/16(+) PCI (SK-4590), SysKonnect TR4/16 PCI (SK-4591),
9161 Compaq 4/16 PCI, Thomas-Conrad TC4048 4/16 PCI, and several
9162 Madge adapters. If you say Y here, you will be asked to select
9163 which cards to support below. If you're using modules, each
9164 class of card will be supported by a separate module.
9166 If you have such an adapter and would like to use it, say Y and
9167 read the Token-Ring mini-HOWTO, available from
9168 http://www.linuxdoc.org/docs.html#howto .
9170 Also read the file Documentation/networking/tms380tr.txt or
9171 check http://www.auk.cx/tms380tr/ .
9173 This driver is also available as a module ( = code which can be
9174 inserted in and removed from the running kernel whenever you want).
9175 The module will will be called tms380tr.o. If you want to compile it
9176 as a module, say M here and read Documentation/modules.txt.
9178 Generic TMS380 PCI support
9180 This tms380 module supports generic TMS380-based PCI cards.
9182 These cards are known to work:
9183 - Compaq 4/16 TR PCI
9184 - SysKonnect TR4/16 PCI (SK-4590/SK-4591)
9185 - Thomas-Conrad TC4048 PCI 4/16
9186 - 3Com Token Link Velocity
9188 This driver is available as a module ( = code which can be
9189 inserted in and removed from the running kernel whenever you want).
9190 The module will will be called tmspci.o. If you want to compile it
9191 as a module, say M here and read Documentation/modules.txt.
9193 Madge Smart 16/4 PCI Mk2 support
9195 This tms380 module supports the Madge Smart 16/4 PCI Mk2
9198 This driver is available as a module ( = code which can be
9199 inserted in and removed from the running kernel whenever you want).
9200 The module will will be called abyss.o. If you want to compile it
9201 as a module, say M here and read Documentation/modules.txt.
9203 Madge Smart 16/4 Ringode MicroChannel
9205 This tms380 module supports the Madge Smart 16/4 MC16 and MC32
9206 MicroChannel adapters.
9208 This driver is available as a module ( = code which can be
9209 inserted in and removed from the running kernel whenever you want).
9210 The module will will be called madgemc.o. If you want to compile it
9211 as a module, say M here and read Documentation/modules.txt.
9213 SMC ISA TokenRing adapter support
9215 This is support for the ISA and MCA SMC Token Ring cards,
9216 specifically SMC TokenCard Elite (8115T) and SMC TokenCard Elite/A
9219 If you have such an adapter and would like to use it, say Y or M and
9220 read the Token-Ring mini-HOWTO, available from
9221 http://www.linuxdoc.org/docs.html#howto and the file
9222 Documentation/networking/smctr.txt.
9224 This driver is also available as a module ( = code which can be
9225 inserted in and removed from the running kernel whenever you want).
9226 The module will will be called smctr.o. If you want to compile it
9227 as a module, say M here and read Documentation/modules.txt.
9229 Sun Happy Meal 10/100baseT support
9231 This driver supports the "hme" interface present on most Ultra
9232 systems and as an option on older Sbus systems. This driver supports
9233 both PCI and Sbus devices. This driver also supports the "qfe" quad
9234 100baseT device available in both PCI and Sbus configurations.
9236 This support is also available as a module called sunhme.o ( = code
9237 which can be inserted in and removed from the running kernel
9238 whenever you want). If you want to compile it as a module, say M
9239 here and read Documentation/modules.txt.
9243 This driver supports the "le" interface present on all 32-bit Sparc
9244 systems, on some older Ultra systems and as an Sbus option.
9246 This support is also available as a module called sunlance.o ( =
9247 code which can be inserted in and removed from the running kernel
9248 whenever you want). If you want to compile it as a module, say M
9249 here and read Documentation/modules.txt.
9251 Sun BigMAC 10/100baseT support (EXPERIMENTAL)
9253 This driver supports the "be" interface available as an Sbus option.
9254 This is Sun's older 100baseT ethernet device.
9256 This support is also available as a module called sunbmac.o ( = code
9257 which can be inserted in and removed from the running kernel
9258 whenever you want). If you want to compile it as a module, say M
9259 here and read Documentation/modules.txt.
9261 Sun QuadEthernet support
9263 This driver supports the "qe" 10baseT ethernet device, available as
9264 an Sbus option. Note that this is not the same as Quad FastEthernet
9265 "qfe" which is supported by the Happy Meal driver instead.
9267 This support is also available as a module called sunqe.o ( = code
9268 which can be inserted in and removed from the running kernel
9269 whenever you want). If you want to compile it as a module, say M
9270 here and read Documentation/modules.txt.
9272 Traffic Shaper (EXPERIMENTAL)
9274 The traffic shaper is a virtual network device that allows you to
9275 limit the rate of outgoing data flow over some other network device.
9276 The traffic that you want to slow down can then be routed through
9277 these virtual devices. See Documentation/networking/shaper.txt for
9280 An alternative to this traffic shaper is the experimental
9281 Class-Based Queueing (CBQ) scheduling support which you get if you
9282 say Y to "QoS and/or fair queueing" above.
9284 To set up and configure shaper devices, you need the shapecfg
9285 program, available from ftp://shadow.cabi.net/pub/Linux in the
9288 This driver is also available as a module ( = code which can be
9289 inserted in and removed from the running kernel whenever you want).
9290 The module will be called shaper.o. If you want to compile it as a
9291 module, say M here and read Documentation/modules.txt. If unsure,
9296 Fiber Distributed Data Interface is a high speed local area network
9297 design; essentially a replacement for high speed Ethernet. FDDI can
9298 run over copper or fiber. If you are connected to such a network and
9299 want a driver for the FDDI card in your computer, say Y here (and
9300 then also Y to the driver for your FDDI card, below). Most people
9303 Digital DEFEA and DEFPA adapter support
9305 This is support for the DIGITAL series of EISA (DEFEA) and PCI
9306 (DEFPA) controllers which can connect you to a local FDDI network.
9308 SysKonnect FDDI PCI support
9310 Say Y here if you have a SysKonnect FDDI PCI adapter.
9311 The following adapters are supported by this driver:
9312 - SK-5521 (SK-NET FDDI-UP)
9313 - SK-5522 (SK-NET FDDI-UP DAS)
9314 - SK-5541 (SK-NET FDDI-FP)
9315 - SK-5543 (SK-NET FDDI-LP)
9316 - SK-5544 (SK-NET FDDI-LP DAS)
9317 - SK-5821 (SK-NET FDDI-UP64)
9318 - SK-5822 (SK-NET FDDI-UP64 DAS)
9319 - SK-5841 (SK-NET FDDI-FP64)
9320 - SK-5843 (SK-NET FDDI-LP64)
9321 - SK-5844 (SK-NET FDDI-LP64 DAS)
9322 - Netelligent 100 FDDI DAS Fibre SC
9323 - Netelligent 100 FDDI SAS Fibre SC
9324 - Netelligent 100 FDDI DAS UTP
9325 - Netelligent 100 FDDI SAS UTP
9326 - Netelligent 100 FDDI SAS Fibre MIC
9328 Read Documentation/networking/skfp.txt for information about
9331 Questions concerning this driver can be addressed to:
9334 If you want to compile this driver as a module ( = code which can be
9335 inserted in and removed from the running kernel whenever you want),
9336 say M here and read Documentation/modules.txt. This is recommended.
9337 The module will be called skfp.o.
9339 HIgh Performance Parallel Interface support (EXPERIMENTAL)
9341 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
9342 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
9343 can run over copper (25m) or fiber (300m on multi-mode or 10km on
9344 single-mode). HIPPI networks are commonly used for clusters and to
9345 connect to super computers. If you are connected to a HIPPI network
9346 and have a HIPPI network card in your computer that you want to use
9347 under Linux, say Y here (you must also remember to enable the driver
9348 for your HIPPI card below). Most people will say N here.
9350 Essential RoadRunner HIPPI PCI adapter support
9352 Say Y here if this is your PCI HIPPI network card.
9354 This driver is also available as a module ( = code which can be
9355 inserted in and removed from the running kernel whenever you want).
9356 The module will be called rrunner.o. If you want to compile it as
9357 a module, say M here and read Documentation/modules.txt. If unsure,
9360 Use large TX/RX rings
9361 CONFIG_ROADRUNNER_LARGE_RINGS
9362 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
9363 of additional memory to allow for fastest operation, both for
9364 transmitting and receiving. This memory cannot be used by any other
9365 kernel code or by user space programs. Say Y here only if you have
9370 If you have an Acorn system with one of these (AKA25) network cards,
9371 you should say Y to this option if you wish to use it with Linux.
9373 Acorn/ANT Ether3 card
9375 If you have an Acorn system with one of these network cards, you
9376 should say Y to this option if you wish to use it with Linux.
9380 If you have an Acorn system with one of these network cards, you
9381 should say Y to this option if you wish to use it with Linux.
9383 EBSA-110 Ethernet interface
9384 CONFIG_ARM_AM79C961A
9385 If you wish to compile a kernel for the EBSA-110, then you should
9386 always answer Y to this.
9388 Support CDROM drives that are not SCSI or IDE/ATAPI
9389 CONFIG_CD_NO_IDESCSI
9390 If you have a CDROM drive that is neither SCSI nor IDE/ATAPI, say Y
9391 here, otherwise N. Read the CDROM-HOWTO, available from
9392 http://www.linuxdoc.org/docs.html#howto .
9394 Note that the answer to this question doesn't directly affect the
9395 kernel: saying N will just cause this configure script to skip all
9396 the questions about these CDROM drives. If you are unsure what you
9397 have, say Y and find out whether you have one of the following
9400 For each of these drivers, a file Documentation/cdrom/<driver_name>
9401 exists. Especially in cases where you do not know exactly which kind
9402 of drive you have you should read there. Most of these drivers use a
9403 file drivers/cdrom/<driver_name>.h where you can define your
9404 interface parameters and switch some internal goodies.
9406 All these CDROM drivers are also usable as a module ( = code which
9407 can be inserted in and removed from the running kernel whenever you
9408 want). If you want to compile them as module, say M instead of Y and
9409 read Documentation/modules.txt.
9411 If you want to use any of these CDROM drivers, you also have to
9412 answer Y or M to "ISO 9660 CDROM file system support" below (this
9413 answer will get "defaulted" for you if you enable any of the Linux
9416 Sony CDU31A/CDU33A CDROM support
9418 These CDROM drives have a spring-pop-out caddyless drawer, and a
9419 rectangular green LED centered beneath it. NOTE: these CDROM drives
9420 will not be auto detected by the kernel at boot time; you have to
9421 provide the interface address as an option to the kernel at boot
9422 time as described in Documentation/cdrom/cdu31a or fill in your
9423 parameters into drivers/cdrom/cdu31a.c. Try "man bootparam" or
9424 see the documentation of your boot loader (lilo or loadlin) about
9425 how to pass options to the kernel.
9427 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9428 file system support" below, because that's the file system used on
9431 This driver is also available as a module ( = code which can be
9432 inserted in and removed from the running kernel whenever you want).
9433 The module will be called cdu31a.o. If you want to compile it as a
9434 module, say M here and read Documentation/modules.txt.
9436 Standard Mitsumi [no XA/Multisession] CDROM support
9438 This is the older of the two drivers for the older Mitsumi models
9439 LU-005, FX-001 and FX-001D. This is not the right driver for the
9440 FX-001DE and the triple or quad speed models (all these are
9441 IDE/ATAPI models). Please also the file Documentation/cdrom/mcd.
9443 With the old LU-005 model, the whole drive chassis slides out for cd
9444 insertion. The FX-xxx models use a motorized tray type mechanism.
9445 Note that this driver does not support XA or MultiSession CDs
9446 (PhotoCDs). There is a new driver (next question) which can do
9447 this. If you want that one, say N here.
9449 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9450 file system support" below, because that's the file system used on
9453 This driver is also available as a module ( = code which can be
9454 inserted in and removed from the running kernel whenever you want).
9455 The module will be called mcd.o. If you want to compile it as a
9456 module, say M here and read Documentation/modules.txt.
9458 IRQ channel for Mitsumi CD-ROM
9460 This allows you to specify the default value of the IRQ used by the
9461 driver. This setting can be overridden by passing the "mcd="
9462 parameter to the kernel at boot time (or at module load time if you
9463 said M to "Standard Mitsumi CDROM support").
9465 I/O base address for Mitsumi CD-ROM
9467 This allows you to specify the default value of the I/O base address
9468 used by the driver. This setting can be overridden by passing the
9469 "mcd=" parameter to the kernel at boot time (or at module load time
9470 if you said M to "Standard Mitsumi CDROM support").
9472 Mitsumi [XA/MultiSession] support
9474 Use this driver if you want to be able to read XA or MultiSession
9475 CDs (PhotoCDs) as well as ordinary CDs with your Mitsumi LU-005,
9476 FX-001 or FX-001D CDROM drive. In addition, this driver uses much
9477 less kernel memory than the old one, if that is a concern. This
9478 driver is able to support more than one drive, but each drive needs
9479 a separate interface card. Please read the file
9480 Documentation/cdrom/mcdx.
9482 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9483 file system support" below, because that's the file system used on
9486 This driver is also available as a module ( = code which can be
9487 inserted in and removed from the running kernel whenever you want).
9488 The module will be called mcdx.o. If you want to compile it as a
9489 module, say M here and read Documentation/modules.txt.
9491 Matsushita/Panasonic/Creative, Longshine, TEAC CDROM support
9493 This driver supports most of the drives which use the Panasonic or
9494 Sound Blaster interface. Please read the file
9495 Documentation/cdrom/sbpcd.
9497 The Matsushita CR-521, CR-522, CR-523, CR-562, CR-563 drives
9498 (sometimes labeled "Creative"), the Creative Labs CD200, the
9499 Longshine LCS-7260, the "IBM External ISA CDROM" (in fact a CR-56x
9500 model), the TEAC CD-55A fall under this category. Some other
9501 "electrically compatible" drives (Vertos, Genoa, some Funai models)
9502 are currently not supported; for the Sanyo H94A drive currently a
9503 separate driver (asked later) is responsible. Most drives have a
9504 uniquely shaped faceplate, with a caddyless motorized drawer, but
9505 without external brand markings. The older CR-52x drives have a
9506 caddy and manual loading/eject, but still no external markings. The
9507 driver is able to do an extended auto-probing for interface
9508 addresses and drive types; this can help to find facts in cases you
9509 are not sure, but can consume some time during the boot process if
9510 none of the supported drives gets found. Once your drive got found,
9511 you should enter the reported parameters into drivers/cdrom/sbpcd.h
9512 and set "DISTRIBUTION 0" there.
9514 This driver can support up to four CDROM controller cards, and each
9515 card can support up to four CDROM drives; if you say Y here, you
9516 will be asked how many controller cards you have. If compiled as a
9517 module, only one controller card (but with up to four drives) is
9520 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9521 file system support" below, because that's the file system used on
9524 This driver is also available as a module ( = code which can be
9525 inserted in and removed from the running kernel whenever you want).
9526 The module will be called sbpcd.o. If you want to compile it as a
9527 module, say M here and read Documentation/modules.txt.
9529 Matsushita/Panasonic, ... second CDROM controller support
9531 Say Y here only if you have two CDROM controller cards of this type
9532 (usually only if you have more than four drives). You should enter
9533 the parameters for the second, third and fourth interface card into
9534 include/linux/sbpcd.h before compiling the new kernel. Read
9535 the file Documentation/cdrom/sbpcd.
9537 Aztech/Orchid/Okano/Wearnes/TXC/CyDROM CDROM support
9539 This is your driver if you have an Aztech CDA268-01A, Orchid
9540 CD-3110, Okano or Wearnes CDD110, Conrad TXC, or CyCDROM CR520 or
9541 CR540 CDROM drive. This driver -- just like all these CDROM drivers
9542 -- is NOT for CDROM drives with IDE/ATAPI interfaces, such as Aztech
9543 CDA269-031SE. Please read the file Documentation/cdrom/aztcd.
9545 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9546 file system support" below, because that's the file system used on
9549 This driver is also available as a module ( = code which can be
9550 inserted in and removed from the running kernel whenever you want).
9551 The module will be called aztcd.o. If you want to compile it as a
9552 module, say M here and read Documentation/modules.txt.
9554 Sony CDU535 CDROM support
9556 This is the driver for the older Sony CDU-535 and CDU-531 CDROM
9557 drives. Please read the file Documentation/cdrom/sonycd535.
9559 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9560 file system support" below, because that's the file system used on
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 sonycd535.o. If you want to compile it as
9566 a module, say M here and read Documentation/modules.txt.
9568 Goldstar R420 CDROM support
9570 If this is your CDROM drive, say Y here. As described in the file
9571 Documentation/cdrom/gscd, you might have to change a setting
9572 in the file drivers/cdrom/gscd.h before compiling the
9573 kernel. Please read the file Documentation/cdrom/gscd.
9575 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9576 file system support" below, because that's the file system used on
9579 This driver is also available as a module ( = code which can be
9580 inserted in and removed from the running kernel whenever you want).
9581 The module will be called gscd.o. If you want to compile it as a
9582 module, say M here and read Documentation/modules.txt.
9584 Philips/LMS CM206 CDROM support
9586 If you have a Philips/LMS CDROM drive cm206 in combination with a
9587 cm260 host adapter card, say Y here. Please also read the file
9588 Documentation/cdrom/cm206.
9590 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9591 file system support" below, because that's the file system used on
9594 This driver is also available as a module ( = code which can be
9595 inserted in and removed from the running kernel whenever you want).
9596 The module will be called cm206.o. If you want to compile it as a
9597 module, say M here and read Documentation/modules.txt.
9599 Optics Storage DOLPHIN 8000AT CDROM support
9601 This is the driver for the 'DOLPHIN' drive with a 34-pin Sony
9602 compatible interface. It also works with the Lasermate CR328A. If
9603 you have one of those, say Y. This driver does not work for the
9604 Optics Storage 8001 drive; use the IDE-ATAPI CDROM driver for that
9605 one. Please read the file Documentation/cdrom/optcd.
9607 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9608 file system support" below, because that's the file system used on
9611 This driver is also available as a module ( = code which can be
9612 inserted in and removed from the running kernel whenever you want).
9613 The module will be called optcd.o. If you want to compile it as a
9614 module, say M here and read Documentation/modules.txt.
9616 Sanyo CDR-H94A CDROM support
9618 If this is your CDROM drive, say Y here and read the file
9619 Documentation/cdrom/sjcd. You should then also say Y or M to
9620 "ISO 9660 CDROM file system support" below, because that's the
9621 file system used on CDROMs.
9623 This driver is also available as a module ( = code which can be
9624 inserted in and removed from the running kernel whenever you want).
9625 The module will be called sjcd.o. If you want to compile it as a
9626 module, say M here and read Documentation/modules.txt.
9628 ISP16/MAD16/Mozart soft configurable cdrom interface support
9630 These are sound cards with built-in cdrom interfaces using the OPTi
9631 82C928 or 82C929 chips. Say Y here to have them detected and
9632 possibly configured at boot time. In addition, You'll have to say Y
9633 to a driver for the particular cdrom drive you have attached to the
9634 card. Read Documentation/cdrom/isp16 for details.
9636 This driver is also available as a module ( = code which can be
9637 inserted in and removed from the running kernel whenever you want).
9638 The module will be called isp16.o. If you want to compile it as a
9639 module, say M here and read Documentation/modules.txt.
9643 If you say Y here, you will be able to set per user limits for disk
9644 usage (also called disk quotas). Currently, it works only for the
9645 ext2 file system. You need additional software in order to use quota
9646 support; for details, read the Quota mini-HOWTO, available from
9647 http://www.linuxdoc.org/docs.html#howto . Probably the quota
9648 support is only useful for multi user systems. If unsure, say N.
9650 Memory Technology Device (MTD) support
9652 Memory Technology Devices are flash, RAM and similar chips, often
9653 used for solid state filesystems on embedded devices. This option
9654 will provide the generic support for MTD drivers to register
9655 themselves with the kernel and for potential users of MTD devices
9656 to enumerate the devices which are present and obtain a handle on
9657 them. It will also allow you to select individual drivers for
9658 particular hardware and users of MTD device. If unsure, say N.
9660 M-Systems Disk-On-Chip 1000 support
9662 This provides an MTD device driver for the M-Systems DiskOnChip
9663 1000 devices, which are obsolete so you probably want to say 'N'.
9665 M-Systems Disk-On-Chip 2000 support
9667 This provides an MTD device driver for the M-Systems DiskOnChip
9668 2000 devices. If you use this, you probably also want the NFTL
9669 'NAND Flash Translation Layer' below, which is used to emulate
9670 a block device by using a kind of filesystem on the flash chips.
9672 M-Systems Disk-On-Chip Millennium support
9674 This provides an MTD device driver for the M-Systems DiskOnChip
9675 Millennium devices. If you use this, you probably also want the
9676 NFTL 'NAND Flash Translation Layer' below, which is used to emulate
9677 a block device by using a kind of filesystem on the flash chips.
9679 Use extra onboard system memory as MTD device
9681 If your CPU cannot cache all of the physical memory in your machine,
9682 you can still use it for storage or swap by using this driver to
9683 present it to the system as a Memory Technology Device.
9685 Ramix PMC551 PCI Mezzanine ram card support
9687 This provides an MTD device driver for the Ramix PMC551 RAM card.
9688 If you have one, you probably want to enable this.
9690 PMC551 256M DRAM Bugfix.
9691 CONFIG_MTD_PMC551_BUGFIX
9692 Some PMC551 boards hacve invalid column and row mux values. This
9693 option will fix them, but will break other memory configurations.
9695 Debugging RAM test driver
9697 This enables a test MTD device driver which uses vmalloc() to
9698 provide storage. You probably want to say 'N' unless you're
9699 testing stuff, or unless you want to use it in place of a ramdisk
9700 when I've eventually got round to making the CONFIG_BLK_DEV option
9701 and you've turned it off.
9703 Common Flash Interface (CFI) support
9705 Intel's Common Flash Interface specification provides a universal
9706 method for probing the capabilities of flash devices. If you wish
9707 to support any device which uses CFI-compliant devices, you need
9708 to enable this option.
9710 CFI support for Intel/Sharp Extended Command Set chips
9711 CONFIG_MTD_CFI_INTELEXT
9712 The Common Flash Interface defines a number of different command
9713 sets which a CFI-compliant chip may claim to implement. This code
9714 provides support for one of those command sets, used on Intel
9715 Strataflash and other parts.
9717 Flash chip mapping in physical memory
9719 This provides a 'mapping' driver which allows the CFI probe and
9720 command set driver code to communicate with flash chips which
9721 are mapped physically into the CPU's memory. You will need to
9722 configure the physical address and size of the flash chips on
9723 your particular board.
9725 Physical start location of flash chip mapping
9726 CONFIG_MTD_PHYSMAP_START
9727 This is the physical memory location at which the flash chips
9728 are mapped on your particular target board. Refer to the
9729 memory map which should hopefully be in the documentation for
9732 Physical length of flash chip mapping
9733 CONFIG_MTD_PHYSMAP_LEN
9734 This is the total length of the mapping of the flash chips on
9735 your particular board. If there is space, or aliases, in the
9736 physical memory map between the chips, this could be larger
9737 than the total amount of flash present. Refer to the memory
9738 map which should hopefully be in the documentation for your
9741 Flash chip mapping on Mixcom piggyback card
9743 This supports the paging arrangement for access to flash chips
9744 on the Mixcom piggyback card, allowing the flash chip drivers
9745 to get on with their job of driving the flash chips without
9746 having to know about the paging. If you have one of these boards,
9747 you probably want to enable this mapping driver.
9749 Flash chip mapping on Nora
9751 If you had to ask, you don't have one. Say 'N'.
9753 Flash chip mapping on Octagon 5066 SBC
9755 This provides a 'mapping' driver which supports the way in which
9756 the flash chips are connected in the Octagon-5066 Single Board
9757 Computer. You will also need to complete and enable the driver
9758 for JEDEC flash chips.
9760 Flash chip mapping on RPXlite PPC board
9762 The RPXLite PowerPC board has CFI-compliant chips mapped in
9763 a strange sparse mapping. This 'mapping' driver supports that
9764 arrangement, allowing the CFI probe and command set driver code
9765 to communicate with the chips on the RPXLite board.
9767 Flash chip mapping on Tempustech VMAX SBC301
9769 This provides a 'mapping' driver which supports the way in which
9770 the flash chips are connected in the Tempustech VMAX SBC301 Single
9771 Board Computer. You will also need to complete and enable the driver
9772 for JEDEC flash chips.
9774 Direct chardevice access to MTD devices
9776 This provides a character device for each MTD device present in
9777 the system, allowing the user to read and write directly to the
9778 memory chips, and also use ioctl() to obtain information about
9779 the device, or to erase parts of it.
9781 Pseudo-blockdevice access to MTD devices
9783 Although flash chips have an erase size too large to useful as
9784 block devices, it is possible to use MTD devices which are based
9785 on RAM chips in this manner. This blockdevice user of MTD devices
9786 performs that function. At the moment, it is also required for
9787 the Journalling Flash File System to obtain a handle on the MTD
9788 device when it's mounted - although the JFFS doesn't actually use
9789 any of the functions of the mtdblock device.
9791 Later, it may be extended to perform read/erase/modify/write cycles
9792 on flash chips to emulate a smaller block size. Needless to say,
9793 this is very unsafe, but could be useful for filesystems which are
9794 almost never written to.
9796 FTL (Flash Translation Layer) support
9798 This provides support for the original Flash Translation Layer which
9799 is part of the PCMCIA specification. It uses a kind of pseudo-
9800 filesystem on a flash device to emulate a block device with 512-byte
9801 sectors, on top of which you put a 'normal' filesystem. You may find
9802 that the algorithms used in this code are patented unless you live
9803 in the Free World where software patents aren't legal - in the USA
9804 you are only permitted to use this on PCMCIA hardware, although
9805 under the terms of the GPL you're obviously permitted to copy,
9806 modify and distribute the code as you wish. Just not use it.
9808 NFTL (NAND Flash Translation Layer) support
9810 This provides support for the NAND Flash Translation Layer which is
9811 used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
9812 filesystem on a flash device to emulate a block device with 512-byte
9813 sectors, on top of which you put a 'normal' filesystem. You may find
9814 that the algorithms used in this code are patented unless you live
9815 in the Free World where software patents aren't legal - in the USA
9816 you are only permitted to use this on DiskOnChip hardware, although
9817 under the terms of the GPL you're obviously permitted to copy,
9818 modify and distribute the code as you wish. Just not use it.
9820 Write support for NFTL (EXPERIMENTAL)
9822 If you're lucky, this will actually work. Don't whinge if it doesn't.
9823 Contact dwmw2@infradead.org if you want to help to make it more
9828 Universal Serial Bus (USB) is a specification for a serial bus
9829 subsystem which offers higher speeds and more features than the
9830 traditional PC serial port. The bus supplies power to peripherals
9831 and allows for hot swapping. Up to 127 USB peripherals can be
9832 connected to a single USB port in a tree structure. The USB port is
9833 the root of the tree, the peripherals are the leaves and the inner
9834 nodes are special USB devices called hubs. Many newer PC's have USB
9835 ports and newer peripherals such as scanners, keyboards, mice,
9836 modems, and printers support the USB protocol and can be connected
9837 to the PC via those ports.
9839 Say Y here if your computer has a USB port and you want to use USB
9840 devices. You then need to say Y to at least one of "UHCI support" or
9841 "OHCI support" below (the type of interface that the USB hardware in
9842 your computer provides to the operating system) and then choose from
9843 among the drivers for USB peripherals. You may want to check out the
9844 information provided in Documentation/usb/ and especially the links
9845 given in Documentation/usb/usb-help.txt.
9847 This code is also available as a module ( = code which can be
9848 inserted in and removed from the running kernel whenever you want).
9849 The module will be called usbcore.o. If you want to compile it as a
9850 module, say M here and read Documentation/modules.txt.
9852 USB verbose debug messages
9854 Say Y here if you want the USB core & hub drivers to produce a bunch
9855 of debug messages to the system log. Select this if you are having a
9856 problem with USB support and want to see more of what is going on.
9858 UHCI (intel PIIX4, VIA, ...) support?
9860 The Universal Host Controller Interface is a standard by Intel for
9861 accessing the USB hardware in the PC (which is also called the USB
9862 host controller). If your USB host controller conforms to this
9863 standard, you may want to say Y, but see below. All recent boards
9864 with Intel PCI chipsets (like intel 430TX, 440FX, 440LX, 440BX,
9865 i810, i820) conform to this standard. Also all VIA PCI chipsets
9866 (like VIA VP2, VP3, MVP3, Apollo Pro, Apollo Pro II or Apollo Pro
9869 Currently there exist two drivers for UHCI host controllers: this
9870 one and the so-called JE driver, which you can get from
9871 "UHCI alternate (JE) support", below. You need only one.
9873 This code is also available as a module ( = code which can be
9874 inserted in and removed from the running kernel whenever you want).
9875 The module will be called usb-uhci.o. If you want to compile it as a
9876 module, say M here and read Documentation/modules.txt.
9878 UHCI (intel PIIX4, VIA, ...) alternate (JE) support?
9880 The Universal Host Controller Interface is a standard by Intel for
9881 accessing the USB hardware in the PC (which is also called the USB
9882 host controller). If your USB host controller conforms to this
9883 standard, you may want to say Y, but see below. All recent boards
9884 with Intel PCI chipsets (like intel 430TX, 440FX, 440LX, 440BX,
9885 i810, i820) conform to this standard. Also all VIA PCI chipsets
9886 (like VIA VP2, VP3, MVP3, Apollo Pro, Apollo Pro II or Apollo Pro
9887 133). If unsure, say Y.
9889 Currently there exist two drivers for UHCI host controllers: this
9890 so-called JE driver, and the one you get from "UHCI support", above.
9893 This code is also available as a module ( = code which can be
9894 inserted in and removed from the running kernel whenever you want).
9895 The module will be called uhci.o. If you want to compile it as a
9896 module, say M here and read Documentation/modules.txt.
9898 UHCI unlink optimizations (EXPERIMENTAL)
9899 CONFIG_USB_UHCI_ALT_UNLINK_OPTIMIZE
9900 This option currently does nothing. You may say Y or N.
9902 OHCI (Compaq, iMacs, OPTi, SiS, ALi, ...) support
9904 The Open Host Controller Interface is a standard by
9905 Compaq/Microsoft/National for accessing the USB PC hardware (also
9906 called USB host controller). If your USB host controller conforms to
9907 this standard, say Y. The USB host controllers on most non-Intel
9908 architectures and on several x86 compatibles with non-Intel chipsets
9909 -- like SiS (aktual 610, 610 and so on) or ALi (ALi IV, ALi V,
9910 Aladdin Pro..) -- conform to this standard.
9912 You may want to read the file Documentation/usb/ohci.txt.
9914 This code is also available as a module ( = code which can be
9915 inserted in and removed from the running kernel whenever you want).
9916 The module will be called usb-ohci.o. If you want to compile it
9917 as a module, say M here and read Documentation/modules.txt.
9919 USB Human Interface Device (HID) support
9921 Say Y here if you want to connect keyboards, mice, joysticks,
9922 graphic tablets, or any other HID based devices to your
9923 computer via USB. More information is available:
9924 Documentation/usb/input.txt.
9928 This code is also available as a module ( = code which can be
9929 inserted in and removed from the running kernel whenever you want).
9930 The module will be called hid.o. If you want to compile it as a
9931 module, say M here and read Documentation/modules.txt.
9933 USB HIDBP Keyboard support
9935 Say Y here if you don't want to use the generic HID driver for your
9936 USB keyboard and prefer to use the keyboard in its limited Boot
9937 Protocol mode. This driver is much smaller than the HID one.
9939 This code is also available as a module ( = code which can be
9940 inserted in and removed from the running kernel whenever you want).
9941 The module will be called usbkbd.o. If you want to compile it as a
9942 module, say M here and read Documentation/modules.txt.
9946 USB HIDBP Mouse support
9948 Say Y here if you don't want to use the generic HID driver for your
9949 USB mouse and prefer to use the mouse in its limited Boot Protocol
9950 mode. This driver is much smaller than the HID one.
9952 This code is also available as a module ( = code which can be
9953 inserted in and removed from the running kernel whenever you want).
9954 The module will be called usbmouse.o. If you want to compile it as
9955 a module, say M here and read Documentation/modules.txt.
9959 Wacom Intuos/Graphire tablet support
9961 Say Y here if you want to use the USB version of the Wacom Intuos
9962 or Graphire tablet. Make sure to say Y to "Mouse support"
9963 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
9964 (CONFIG_INPUT_EVDEV) as well.
9966 This driver is also available as a module ( = code which can be
9967 inserted in and removed from the running kernel whenever you want).
9968 The module will be called wacom.o. If you want to compile it as a
9969 module, say M here and read Documentation/modules.txt.
9971 Logitech WingMan Force joystick support
9973 Say Y here if you want to use the Logitech WingMan Force with Linux
9974 on the USB port. No force-feedback support yet, but other than that
9975 it should work like a normal joystick.
9977 This driver is also available as a module ( = code which can be
9978 inserted in and removed from the running kernel whenever you want).
9979 The module will be called wmforce.o. If you want to compile it as a
9980 module, say M here and read Documentation/modules.txt.
9983 CONFIG_INPUT_KEYBDEV
9984 Say Y here if you want your USB HID keyboard to be able to serve as
9987 This driver is also available as a module ( = code which can be
9988 inserted in and removed from the running kernel whenever you want).
9989 The module will be called keybdev.o. If you want to compile it as a
9990 module, say M here and read Documentation/modules.txt.
9993 CONFIG_INPUT_MOUSEDEV
9994 Say Y here if you want your USB HID mouse to be accessible as
9995 char devices 13:32+ - /dev/input/mouseX and 13:63 - /dev/input/mice
9996 as an emulated PS/2 mouse. That way, all user space programs will
9997 be able to use your mouse.
10001 This driver is also available as a module ( = code which can be
10002 inserted in and removed from the running kernel whenever you want).
10003 The module will be called mousedev.o. If you want to compile it as
10004 a module, say M here and read Documentation/modules.txt.
10006 Horizontal screen resolution
10007 CONFIG_INPUT_MOUSEDEV_SCREEN_X
10008 If you're using a digitizer, or a graphic tablet, and want to use
10009 it as a mouse then the mousedev driver needs to know the X window
10010 screen resolution you are using to correctly scale the data. If
10011 you're not using a digitizer, this value is ignored.
10013 Vertical screen resolution
10014 CONFIG_INPUT_MOUSEDEV_SCREEN_Y
10015 If you're using a digitizer, or a graphic tablet, and want to use
10016 it as a mouse then the mousedev driver needs to know the X window
10017 screen resolution you are using to correctly scale the data. If
10018 you're not using a digitizer, this value is ignored.
10021 CONFIG_INPUT_JOYDEV
10022 Say Y here if you want your USB HID joystick or gamepad to be
10023 accessible as char device 13:0+ - /dev/input/jsX device.
10025 This driver is also available as a module ( = code which can be
10026 inserted in and removed from the running kernel whenever you want).
10027 The module will be called joydev.o. If you want to compile it as a
10028 module, say M here and read Documentation/modules.txt.
10030 Event interface support
10032 Say Y here if you want your USB HID device events be accessible
10033 under char device 13:64+ - /dev/inputX in a generic way.
10034 This is the future ...
10036 USB Scanner support
10038 Say Y here if you want to connect a USB scanner to your computer's
10039 USB port. Please read Documentation/usb/scanner.txt and
10040 Documentation/usb/scanner-hp-sane.txt for more information.
10042 This code is also available as a module ( = code which can be
10043 inserted in and removed from the running kernel whenever you want).
10044 The module will be called scanner.o. If you want to compile it as
10045 a module, say M here and read Documentation/modules.txt.
10049 Say Y here if you want to connect UAB audio equipment such as
10050 speakers to your computer's USB port.
10052 This code is also available as a module ( = code which can be
10053 inserted in and removed from the running kernel whenever you want).
10054 The module will be called audio.o. If you want to compile it as a
10055 module, say M here and read Documentation/modules.txt.
10057 USB Modem (CDC ACM) support
10059 This driver supports USB modems and ISDN adapters which support the
10060 Communication Device Class Abstract Control Model interface.
10061 Please read Documentation/usb/acm.txt for details.
10063 This code is also available as a module ( = code which can be
10064 inserted in and removed from the running kernel whenever you want).
10065 The module will be called acm.o. If you want to compile it as a
10066 module, say M here and read Documentation/modules.txt.
10068 USB Serial converter support
10070 Say Y here if you have a USB device that provides normal serial
10071 ports, and you want to connect it to your USB bus. Supported devices
10072 are the Tech WhiteHEAT multi-port USB to serial converter, and the
10073 FTDI or Keyspan single port USB to serial converter Handspring
10074 Visor. In addition to saying Y here, you need to say Y to the driver
10075 for your specific hardware below. Some other devices may also be
10076 used if you say Y to "USB Generic Serial Driver", below.
10078 Please read Documentation/usb/usb-serial.txt for more information.
10080 This code is also available as a module ( = code which can be
10081 inserted in and removed from the running kernel whenever you want).
10082 The module will be called usbserial.o. If you want to compile it
10083 as a module, say M here and read Documentation/modules.txt.
10085 USB Generic Serial Driver
10086 CONFIG_USB_SERIAL_GENERIC
10087 Say Y here if you want to use the generic USB serial driver. Please
10088 read Documentation/usb/usb-serial.txt for more information on using
10089 this driver. It is recommended that the "USB Serial converter
10090 support" be compiled as a module for this driver to be used
10093 USB ConnectTech WhiteHEAT Serial Driver
10094 CONFIG_USB_SERIAL_WHITEHEAT
10095 Say Y here if you want to use a ConnectTech WhiteHEAT 4 port
10096 USB to serial converter device.
10098 This code is also available as a module ( = code which can be
10099 inserted in and removed from the running kernel whenever you want).
10100 The module will be called whiteheat.o. If you want to compile it as a
10101 module, say M here and read Documentation/modules.txt.
10103 USB Handspring Visor Driver
10104 CONFIG_USB_SERIAL_VISOR
10105 Say Y here if you want to connect to your HandSpring Visor through
10106 its USB docking station. See http://usbvisor.sourceforge.net for
10107 more information on using this driver.
10109 This code is also available as a module ( = code which can be
10110 inserted in and removed from the running kernel whenever you want).
10111 The module will be called visor.o. If you want to compile it as a
10112 module, say M here and read Documentation/modules.txt.
10114 USB FTDI Single Port Serial Driver
10115 CONFIG_USB_SERIAL_FTDI_SIO
10116 Say Y here if you want to use a FTDI SIO single port USB to serial
10117 converter device. The implementation I have is called the USC-1000.
10119 See http://reality.sgi.com/bryder_wellington/ftdi_sio for more
10120 information on this driver and the device.
10122 This code is also available as a module ( = code which can be
10123 inserted in and removed from the running kernel whenever you want).
10124 The module will be called ftdi_sio.o. If you want to compile it as a
10125 module, say M here and read Documentation/modules.txt.
10127 USB Keyspan PDA Single Port Serial Driver
10128 CONFIG_USB_SERIAL_KEYSPAN_PDA
10129 Say Y here if you want to use a Keyspan PDA single port USB to
10130 serial converter device. This driver makes use of firmware
10131 developed from scratch by Brian Warner.
10133 This code is also available as a module ( = code which can be
10134 inserted in and removed from the running kernel whenever you want).
10135 The module will be called keyspan_pda.o. If you want to compile it
10136 as a module, say M here and read Documentation/modules.txt.
10138 USB Keyspan USA-xxx Serial Driver
10139 CONFIG_USB_SERIAL_KEYSPAN
10140 Say Y here if you want to use Keyspan USB to serial converter
10141 devices. This driver makes use of Keyspan's official firmware
10142 and was developed with their support. You must also include
10143 firmware to support your particular device(s).
10145 See http://www.linuxcare.com.au/hugh/keyspan.html for
10148 This code is also available as a module ( = code which can be
10149 inserted in and removed from the running kernel whenever you want).
10150 The module will be called keyspan.o. If you want to compile it as a
10151 module, say M here and read Documentation/modules.txt.
10153 USB Keyspan USA-28 Firmware
10154 CONFIG_USB_SERIAL_KEYSPAN_USA28
10155 Say Y here to include firmware for the USA-28 converter.
10157 USB Keyspan USA-28X Firmware
10158 CONFIG_USB_SERIAL_KEYSPAN_USA28X
10159 Say Y here to include firmware for the USA-28X converter.
10161 USB Keyspan USA-19 Firmware
10162 CONFIG_USB_SERIAL_KEYSPAN_USA19
10163 Say Y here to include firmware for the USA-19 converter.
10165 USB Keyspan USA-18X Firmware
10166 CONFIG_USB_SERIAL_KEYSPAN_USA18X
10167 Say Y here to include firmware for the USA-18X converter.
10169 USB Keyspan USA-19W Firmware
10170 CONFIG_USB_SERIAL_KEYSPAN_USA19W
10171 Say Y here to include firmware for the USA-19W converter.
10173 USB ZyXEL omni.net LCD Plus Driver
10174 CONFIG_USB_SERIAL_OMNINET
10175 Say Y here if you want to use a ZyXEL omni.net LCD ISDN TA.
10177 This code is also available as a module ( = code which can be
10178 inserted in and removed from the running kernel whenever you want).
10179 The module will be called omninet.o. If you want to compile it as a
10180 module, say M here and read Documentation/modules.txt.
10182 USB Digi International AccelePort USB Serial Driver
10183 CONFIG_USB_SERIAL_DIGI_ACCELEPORT
10184 Say Y here if you want to use Digi AccelePort USB 2 or 4 devices,
10185 2 port (plus parallel port) and 4 port USB serial converters. The
10186 parallel port on the USB 2 appears as a third serial port on Linux.
10187 The Digi Acceleport USB 8 is not yet supported by this driver.
10189 This code is also available as a module ( = code which can be
10190 inserted in and removed from the running kernel whenever you want).
10191 The module will be called digi_acceleport.o. If you want to compile
10192 it as a module, say M here and read Documentation/modules.txt.
10194 USB Serial Converter verbose debug
10195 CONFIG_USB_SERIAL_DEBUG
10196 Say Y here if you want verbose debug messages from the USB Serial
10199 USB Printer support
10201 Say Y here if you want to connect a USB printer to your computer's
10204 This code is also available as a module ( = code which can be
10205 inserted in and removed from the running kernel whenever you want).
10206 The module will be called printer.o. If you want to compile it as a
10207 module, say M here and read Documentation/modules.txt.
10209 USB IBM (Xirlink) C-It Camera support
10211 Say Y here if you want to connect a IBM "C-It" camera, also known as
10212 "Xirlink PC Camera" to your computer's USB port. For more
10213 information, read Documentation/usb/ibmcam.txt.
10215 This driver uses the Video For Linux API. You must enable
10216 (Y or M in config) Video For Linux (under Character Devices)
10217 to use this driver. Information on this API and pointers to
10218 "v4l" programs may be found on the WWW at
10219 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
10221 This code is also available as a module ( = code which can be
10222 inserted in and removed from the running kernel whenever you want).
10223 The module will be called ibmcam.o. If you want to compile it as a
10224 module, say M here and read Documentation/modules.txt. This camera
10225 has several configuration options which can be specified when you
10226 load the module. Read Documentation/usb/ibmcam.txt to learn more.
10228 USB OV511 Camera support
10230 Say Y here if you want to connect this type of camera to your
10231 computer's USB port. See Documentation/usb/ov511.txt for more
10232 information and for a list of supported cameras.
10234 This driver uses the Video For Linux API. You must say Y or M to
10235 "Video For Linux" (under Character Devices) to use this driver.
10236 Information on this API and pointers to "v4l" programs may be found
10237 on the WWW at http://roadrunner.swansea.uk.linux.org/v4l.shtml .
10239 This code is also available as a module ( = code which can be
10240 inserted in and removed from the running kernel whenever you want).
10241 The module will be called ov511.o. If you want to compile it as a
10242 module, say M here and read Documentation/modules.txt.
10244 USB ADMtek Pegasus-based ethernet device support
10246 Say Y if you want to use your USB ethernet device. Supported
10247 cards until now are:
10248 ADMtek AN986 (eval. board)
10251 Corega FEter USB-TX
10252 MELCO/BUFFALO LUA-TX
10253 D-Link DSB-650TX, DSB-650TX-PNA, DSB-650, DU-E10, DU-E100
10254 Linksys USB100TX, USB10TX
10255 LANEED Ethernet LD-USB/TX
10257 SOHOware NUB Ethernet
10258 If you have devices with vendor IDs other than noted above
10259 you should add them in the driver code and send a message
10260 to me (petkan@dce.bg) for update.
10262 This code is also available as a module ( = code which can be
10263 inserted in and removed from the running kernel whenever you want).
10264 The module will be called pegasus.o. If you want to compile it as a
10265 module, say M here and read Documentation/modules.txt.
10267 USB Kodak DC-2xx Camera support
10269 Say Y here if you want to connect this type of still camera to
10270 your computer's USB port. See Documentation/usb/dc2xx.txt for more
10271 information; some non-Kodak cameras may also work with this
10272 driver, given application support (such as www.gPhoto.org).
10274 This code is also available as a module ( = code which can be
10275 inserted in and removed from the running kernel whenever you want).
10276 The module will be called dc2xx.o. If you want to compile it as a
10277 module, say M here and read Documentation/modules.txt.
10279 USB Mustek MDC800 Digital Camera Support
10281 Say Y here if you want to connect this type of still camera to
10282 your computer's USB port. This driver can be used with gphoto 0.4.3
10283 and higher (look at http://www.gphoto.org ).
10284 To use it create a device node with "mknod /dev/mustek c 180 32" and
10285 configure it in your software.
10287 This code is also available as a module ( = code which can be
10288 inserted in and removed from the running kernel whenever you want).
10289 The module will be called mdc800.o. If you want to compile it as a
10290 module, say M here and read Documentation/modules.txt.
10292 USB Mass Storage support
10294 Say Y here if you want to connect USB mass storage devices to your
10295 computer's USB port.
10297 This code is also available as a module ( = code which can be
10298 inserted in and removed from the running kernel whenever you want).
10299 The module will be called usb-storage.o. If you want to compile it
10300 as a module, say M here and read Documentation/modules.txt.
10302 USB Mass Storage verbose debug
10303 CONFIG_USB_STORAGE_DEBUG
10304 Say Y here in order to have the USB Mass Storage code generate
10305 verbose debugging messages.
10307 USS720 parport driver
10309 This driver is for USB parallel port adapters that use the Lucent
10310 Technologies USS-720 chip. These cables are plugged into your USB
10311 port and provide USB compatibility to peripherals designed with
10312 parallel port interfaces.
10314 The chip has two modes: automatic mode and manual mode. In automatic
10315 mode, it looks to the computer like a standard USB printer. Only
10316 printers may be connected to the USS-720 in this mode. The generic
10317 USB printer driver ("USB Printer support", above) may be used in
10318 that mode, and you can say N here if you want to use the chip only
10321 Manual mode is not limited to printers, any parallel port
10322 device should work. This driver utilizes manual mode.
10323 Note however that some operations are three orders of magnitude
10324 slower than on a PCI/ISA Parallel Port, so timing critical
10325 applications might not work.
10327 Say Y here if you own an USS-720 USB->Parport cable and intend to
10328 connect anything other than a printer to it.
10330 This code is also available as a module ( = code which can be
10331 inserted in and removed from the running kernel whenever you want).
10332 The module will be called uss720.o. If you want to compile it as a
10333 module, say M here and read Documentation/modules.txt.
10335 USB device file system
10336 CONFIG_USB_DEVICEFS
10337 If you say Y here (and to "/proc file system support" below), you
10338 will get a file /proc/usb/devices which lists the devices currently
10339 connected to your USB busses, a file /proc/usb/drivers which lists
10340 the USB kernel client drivers currently loaded, and for every
10341 connected device a file named "/proc/usb/xxx/yyy", where xxx is the
10342 bus number and yyy the device number; the latter files can be used
10343 by user space programs to talk directly to the device. These files
10344 are "virtual", meaning they are generated on the fly and not stored
10347 For the format of the /proc/usb/ files, please read
10348 Documentation/usb/proc_usb_info.txt.
10350 Please note that this code is completely unrelated to devfs, the
10351 "/dev file system support".
10353 Most users want to say Y here.
10355 USB Bandwidth allocation
10356 CONFIG_USB_BANDWIDTH
10357 If you say Y here, the USB subsystem enforces USB bandwidth
10358 allocation and will prevent some device opens from succeeding
10359 if they would cause USB bandwidth usage to go above 90% of
10362 If you say N here, these conditions will cause warning messages
10363 about USB bandwidth usage to be logged and some devices or
10364 drivers may not work correctly.
10368 A Digital Audio Broadcasting (DAB) Receiver for USB and Linux
10369 brought to you by the DAB-Team (http://dab.in.tum.de). This driver
10370 can be taken as an example for URB-based bulk, control, and
10371 isochronous transactions. URB's are explained in
10372 Documentation/usb/URB.txt.
10374 This code is also available as a module ( = code which can be
10375 inserted in and removed from the running kernel whenever you want).
10376 The module will be called dabusb.o. If you want to compile it as a
10377 module, say M here and read Documentation/modules.txt.
10381 A driver for the Prolific PL-2302 USB-to-USB network device. This
10382 'USB cable' connects two hosts via a point-to-point network with
10383 bandwidth of 5 Mbit/s. Configure this driver after connecting the
10384 USB cable via ifconfig plusb0 10.0.0.1 pointopoint 10.0.0.2 (and
10385 vice versa on the other host).
10387 This code is also available as a module ( = code which can be
10388 inserted in and removed from the running kernel whenever you want).
10389 The module will be called plusb.o. If you want to compile it as a
10390 module, say M here and read Documentation/modules.txt.
10392 USB Diamond Rio500 support
10394 Say Y here if you want to connect a USB Rio500 mp3 player to your
10395 computer's USB port. Please read Documentation/usb/rio.txt
10396 for more information.
10398 This code is also available as a module ( = code which can be
10399 inserted in and removed from the running kernel whenever you want).
10400 The module will be called rio500.o. If you want to compile it as
10401 a module, say M here and read Documentation/modules.txt.
10403 D-Link DSB-R100 FM radio support
10405 Say Y here if you want to connect this type of radio to your
10406 computer's USB port. Note that the audio is not digital, and
10407 you must connect the line out connector to a sound card or a
10410 This driver uses the Video For Linux API. You must enable
10411 (Y or M in config) Video For Linux (under Character Devices)
10412 to use this driver. Information on this API and pointers to
10413 "v4l" programs may be found on the WWW at
10414 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
10416 This code is also available as a module ( = code which can be
10417 inserted in and removed from the running kernel whenever you want).
10418 The module will be called dsbr100.o. If you want to compile it as a
10419 module, say M here and read Documentation/modules.txt.
10421 Microtek USB scanner support
10422 CONFIG_USB_MICROTEK
10423 Say Y here if you want support for the Microtek X6USB and possibly
10424 some other scanners by that vendor. The scanner will appear as a
10425 scsi generic device to the rest of the system.
10426 A patched version of SANE is necessary to use the
10427 scanner. It's available at
10428 http://fachschaft.cup.uni-muenchen.de/~neukum/scanner.html
10429 This driver can be compiled as a module.
10431 USB Bluetooth support
10432 CONFIG_USB_BLUETOOTH
10433 Say Y here if you want to connect a USB Bluetooth device to your
10434 computer's USB port. You will need the Bluetooth stack (available
10435 at http://developer.axis.com/software/index.shtml) to fully use
10438 This code is also available as a module ( = code which can be
10439 inserted in and removed from the running kernel whenever you want).
10440 The module will be called bluetooth.o. If you want to compile it as
10441 a module, say M here and read Documentation/modules.txt.
10445 Minix is a simple operating system used in many classes about OS's.
10446 The minix file system (method to organize files on a hard disk
10447 partition or a floppy disk) was the original file system for Linux,
10448 but has been superseded by the second extended file system ext2fs.
10449 You don't want to use the minix file system on your hard disk
10450 because of certain built-in restrictions, but it is sometimes found
10451 on older Linux floppy disks. This option will enlarge your kernel by
10452 about 28 KB. If unsure, say N.
10454 If you want to compile this as a module ( = code which can be
10455 inserted in and removed from the running kernel whenever you want),
10456 say M here and read Documentation/modules.txt. The module will be
10457 called minix.o. Note that the file system of your root partition
10458 (the one containing the directory /) cannot be compiled as a module.
10460 Second extended fs support
10462 This is the de facto standard Linux file system (method to organize
10463 files on a storage device) for hard disks.
10465 You want to say Y here, unless you intend to use Linux exclusively
10466 from inside a DOS partition using the UMSDOS file system. The
10467 advantage of the latter is that you can get away without
10468 repartitioning your hard drive (which often implies backing
10469 everything up and restoring afterwards); the disadvantage is that
10470 Linux becomes susceptible to DOS viruses and that UMSDOS is somewhat
10471 slower than ext2fs. Even if you want to run Linux in this fashion,
10472 it might be a good idea to have ext2fs around: it enables you to
10473 read more floppy disks and facilitates the transition to a *real*
10474 Linux partition later. Another (rare) case which doesn't require
10475 ext2fs is a diskless Linux box which mounts all files over the
10476 network using NFS (in this case it's sufficient to say Y to "NFS
10477 file system support" below). Saying Y here will enlarge your kernel
10480 The Ext2fs-Undeletion mini-HOWTO, available from
10481 http://www.linuxdoc.org/docs.html#howto , gives information about
10482 how to retrieve deleted files on ext2fs file systems.
10484 To change the behavior of ext2 file systems, you can use the tune2fs
10485 utility ("man tune2fs"). To modify attributes of files and
10486 directories on ext2 file systems, use chattr ("man chattr").
10488 Ext2fs partitions can be read from within DOS using the ext2tool
10489 command line tool package (available via FTP (user: anonymous) from
10490 ftp://metalab.unc.edu/pub/Linux/system/filesystems/ext2 ) and from
10491 within Windows NT using the ext2nt command line tool package from
10492 ftp://metalab.unc.edu/pub/Linux/utils/dos . Explore2fs is a
10493 graphical explorer for ext2fs partitions which runs on Windows 95
10494 and Windows NT and includes experimental write support; it is
10496 http://jnewbigin-pc.it.swin.edu.au/Linux/Explore2fs.htm .
10498 If you want to compile this file system as a module ( = code which
10499 can be inserted in and removed from the running kernel whenever you
10500 want), say M here and read Documentation/modules.txt. The module
10501 will be called ext2.o. Be aware however that the file system of your
10502 root partition (the one containing the directory /) cannot be
10503 compiled as a module, and so this could be dangerous. Most everyone
10504 wants to say Y here.
10506 BFS file system support (EXPERIMENTAL)
10508 Boot File System (BFS) is a file system used under SCO UnixWare to
10509 allow the bootloader access to the kernel image and other important
10510 files during the boot process. It is usually mounted under /stand
10511 and corresponds to the slice marked as "STAND" in the UnixWare
10512 partition. You should say Y if you want to read or write
10513 the files on your /stand slice from within Linux. You then also
10514 need to say Y to "UnixWare slices support", below. More information
10515 about the BFS file system is contained in the file
10516 Documentation/filesystems/bfs.txt.
10518 If you don't know what this is about, say N.
10520 If you want to compile this as a module ( = code which can be
10521 inserted in and removed from the running kernel whenever you want),
10522 say M here and read Documentation/modules.txt. The module will be
10523 called bfs.o. Note that the file system of your root partition (the
10524 one containing the directory /) cannot be compiled as a module.
10526 Compressed ROM file system support
10528 Saying Y here includes support for CramFs (Compressed ROM File
10529 System). Cramfs is designed to be a simple, small, and compressed
10530 file system for ROM based embedded systems. CramFs is read-only,
10531 limited to 256MB file systems (with 16MB files), and doesn't support
10532 16/32 bits uid/gid, hard links and timestamps.
10534 See Documentation/filesystems/cramfs.txt and fs/cramfs/README
10535 for further information.
10537 If you want to compile this as a module ( = code which can be
10538 inserted in and removed from the running kernel whenever you want),
10539 say M here and read Documentation/modules.txt. The module will be
10540 called cramfs.o. Note that the root file system (the one containing
10541 the directory /) cannot be compiled as a module.
10545 Simple RAM-based file system support
10547 Ramfs is a file system which keeps all files in RAM. It allows
10548 read and write access.
10550 In contrast to RAM disks, which get allocated a fixed amount of RAM,
10551 ramfs grows and shrinks to accommodate the files it contains.
10553 Before you can use this RAM-based file system, it has to be mounted,
10554 meaning it has to be given a location in the directory hierarchy. If
10555 you want to use the location /ramfiles for example, you would have
10556 to create that directory first and then mount the file system by
10557 saying "mount -t ramfs ramfs /ramfiles" or the equivalent line in
10558 /etc/fstab. Everything is "virtual" in the sense that no files will
10559 be created on your hard drive; if you reboot, everything in
10560 /ramfiles will be lost.
10562 If you want to compile this as a module ( = code which can be
10563 inserted in and removed from the running kernel whenever you want),
10564 say M here and read Documentation/modules.txt. The module will be
10567 ISO 9660 CDROM file system support
10569 This is the standard file system used on CDROMs. It was previously
10570 known as "High Sierra File System" and is called "hsfs" on other
10571 Unix systems. The so-called Rock-Ridge extensions which allow for
10572 long Unix filenames and symbolic links are also supported by this
10573 driver. If you have a CDROM drive and want to do more with it than
10574 just listen to audio CDs and watch its LEDs, say Y (and read
10575 Documentation/filesystems/isofs.txt and the CDROM-HOWTO, available
10576 from http://www.linuxdoc.org/docs.html#howto ), thereby enlarging
10577 your kernel by about 27 KB; otherwise say N.
10579 If you want to compile this as a module ( = code which can be
10580 inserted in and removed from the running kernel whenever you want),
10581 say M here and read Documentation/modules.txt. The module will be
10584 Microsoft Joliet CDROM extensions
10586 Joliet is a Microsoft extension for the ISO 9660 CDROM file system
10587 which allows for long filenames in unicode format (unicode is the
10588 new 16 bit character code, successor to ASCII, which encodes the
10589 characters of almost all languages of the world; see
10590 http://www.unicode.org for more information). Say Y here if you want
10591 to be able to read Joliet CDROMs under Linux.
10593 UDF File System support (read only)
10595 This is the new file system used on some CDROMs and DVDs. Say Y if
10596 you intend to mount DVD discs or CDRW's written in packet mode, or
10597 if written to by other UDF utilities, such as DirectCD. This UDF
10598 file system support is read-only. If you want to write to UDF
10599 file systems on some media, you need to say Y to "UDF read-write
10600 support" below in addition. Please read
10601 Documentation/filesystems/udf.txt.
10603 This file system support is also available as a module ( = code
10604 which can be inserted in and removed from the running kernel
10605 whenever you want). The module is called udf.o. If you want to
10606 compile it as a module, say M here and read
10607 Documentation/modules.txt.
10611 UDF write support (DANGEROUS)
10613 Say Y if you want to test write support for UDF file systems.
10614 Due to lack of support for writing to CDR/CDRW's, this option
10615 is only supported for hard discs, DVD-RAM, and loopback files.
10619 If you want to use one of the FAT-based file systems (the MS-DOS,
10620 VFAT (Windows 95) and UMSDOS (used to run Linux on top of an
10621 ordinary DOS partition) file systems), then you must say Y or M here
10622 to include FAT support. You will then be able to mount partitions or
10623 diskettes with FAT-based file systems and transparently access the
10624 files on them, i.e. MSDOS files will look and behave just like all
10627 This FAT support is not a file system in itself, it only provides
10628 the foundation for the other file systems. You will have to say Y or
10629 M to at least one of "MSDOS fs support" or "VFAT fs support" in
10630 order to make use of it.
10632 Another way to read and write MSDOS floppies and hard drive
10633 partitions from within Linux (but not transparently) is with the
10634 mtools ("man mtools") program suite. You don't need to say Y here in
10637 If you need to move large files on floppies between a DOS and a
10638 Linux box, say Y here, mount the floppy under Linux with an MSDOS
10639 file system and use GNU tar's M option. GNU tar is a program
10640 available for Unix and DOS ("man tar" or "info tar").
10642 It is now also becoming possible to read and write compressed FAT
10643 file systems; read Documentation/filesystems/fat_cvf.txt for
10646 The FAT support will enlarge your kernel by about 37 KB. If unsure,
10649 If you want to compile this as a module however ( = code which can
10650 be inserted in and removed from the running kernel whenever you
10651 want), say M here and read Documentation/modules.txt. The module
10652 will be called fat.o. Note that if you compile the FAT support as a
10653 module, you cannot compile any of the FAT-based file systems into
10654 the kernel -- they will have to be modules as well. The file system
10655 of your root partition (the one containing the directory /) cannot
10656 be a module, so don't say M here if you intend to use UMSDOS as your
10661 This allows you to mount MSDOS partitions of your hard drive (unless
10662 they are compressed; to access compressed MSDOS partitions under
10663 Linux, you can either use the DOS emulator DOSEMU, described in the
10664 DOSEMU-HOWTO, available from
10665 http://www.linuxdoc.org/docs.html#howto , or try dmsdosfs in
10666 ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs . If you
10667 intend to use dosemu with a non-compressed MSDOS partition, say Y
10668 here) and MSDOS floppies. This means that file access becomes
10669 transparent, i.e. the MSDOS files look and behave just like all
10672 If you want to use UMSDOS, the Unix-like file system on top of a
10673 DOS file system, which allows you to run Linux from within a DOS
10674 partition without repartitioning, you'll have to say Y or M here.
10676 If you have Windows 95 or Windows NT installed on your MSDOS
10677 partitions, you should use the VFAT file system (say Y to "VFAT fs
10678 support" below), or you will not be able to see the long filenames
10679 generated by Windows 95 / Windows NT.
10681 This option will enlarge your kernel by about 7 KB. If unsure,
10682 answer Y. This will only work if you said Y to "DOS FAT fs support"
10683 as well. If you want to compile this as a module however ( = code
10684 which can be inserted in and removed from the running kernel
10685 whenever you want), say M here and read Documentation/modules.txt.
10686 The module will be called msdos.o.
10688 VFAT (Windows-95) fs support
10690 This option provides support for normal Windows file systems with
10691 long filenames. That includes non-compressed FAT-based file systems
10692 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
10693 programs from the mtools package.
10695 You cannot use the VFAT file system for your Linux root partition
10696 (the one containing the directory /); use UMSDOS instead if you
10697 want to run Linux from within a DOS partition (i.e. say Y to
10698 "UMSDOS: Unix like fs on top of std MSDOS fs", below).
10700 The VFAT support enlarges your kernel by about 10 KB and it only
10701 works if you said Y to the "DOS FAT fs support" above. Please read
10702 the file Documentation/filesystems/vfat.txt for details. If unsure,
10705 If you want to compile this as a module ( = code which can be
10706 inserted in and removed from the running kernel whenever you want),
10707 say M here and read Documentation/modules.txt. The module will be
10710 UMSDOS: Unix-like file system on top of standard MSDOS fs
10712 Say Y here if you want to run Linux from within an existing DOS
10713 partition of your hard drive. The advantage of this is that you can
10714 get away without repartitioning your hard drive (which often implies
10715 backing everything up and restoring afterwards) and hence you're
10716 able to quickly try out Linux or show it to your friends; the
10717 disadvantage is that Linux becomes susceptible to DOS viruses and
10718 that UMSDOS is somewhat slower than ext2fs. Another use of UMSDOS
10719 is to write files with long unix filenames to MSDOS floppies; it
10720 also allows Unix-style soft-links and owner/permissions of files on
10721 MSDOS floppies. You will need a program called umssync in order to
10722 make use of UMSDOS; read Documentation/filesystems/umsdos.txt.
10724 To get utilities for initializing/checking UMSDOS file system, or
10725 latest patches and/or information, visit the UMSDOS home page at
10726 http://www.voyager.hr/~mnalis/umsdos/ .
10728 This option enlarges your kernel by about 28 KB and it only works if
10729 you said Y to both "DOS FAT fs support" and "MSDOS fs support"
10730 above. If you want to compile this as a module ( = code which can be
10731 inserted in and removed from the running kernel whenever you want),
10732 say M here and read Documentation/modules.txt. The module will be
10733 called umsdos.o. Note that the file system of your root partition
10734 (the one containing the directory /) cannot be a module, so saying M
10735 could be dangerous. If unsure, say N.
10737 /proc file system support
10739 This is a virtual file system providing information about the status
10740 of the system. "Virtual" means that it doesn't take up any space on
10741 your hard disk: the files are created on the fly by the kernel when
10742 you try to access them. Also, you cannot read the files with older
10743 version of the program less: you need to use more or cat.
10745 It's totally cool; for example, "cat /proc/interrupts" gives
10746 information about what the different IRQs are used for at the moment
10747 (there is a small number of Interrupt ReQuest lines in your computer
10748 that are used by the attached devices to gain the CPU's attention --
10749 often a source of trouble if two devices are mistakenly configured
10750 to use the same IRQ). The program procinfo to display some
10751 information about your system gathered from the /proc file system.
10753 Before you can use the /proc file system, it has to be mounted,
10754 meaning it has to be given a location in the directory hierarchy.
10755 That location should be /proc. A command such as "mount -t proc proc
10756 /proc" or the equivalent line in /etc/fstab does the job.
10758 The /proc file system is explained in the file
10759 Documentation/filesystems/proc.txt and on the proc(5) manpage ("man
10762 This option will enlarge your kernel by about 67 KB. Several
10763 programs depend on this, so everyone should say Y here.
10765 /dev file system support (EXPERIMENTAL)
10767 This is support for devfs, a virtual file system (like /proc) which
10768 provides the file system interface to device drivers, normally found
10769 in /dev. Devfs does not depend on major and minor number
10770 allocations. Device drivers register entries in /dev which then
10771 appear automatically, which means that the system administrator does
10772 not have to create character and block special device files in the
10773 /dev directory using the mknod command (or MAKEDEV script) anymore.
10775 This is work in progress. If you want to use this, you *must* read
10776 the material in Documentation/filesystems/devfs/, especially the
10781 Enable automatic mounting at boot
10783 This option appears if you have CONFIG_DEVFS_FS enabled. Setting
10784 this to 'Y' will make the kernel automatically mount devfs onto /dev
10785 when the system is booted, before the init thread is started.
10786 You can override this with the "devfs=nomount" boot option.
10792 If you say Y here, then the /dev file system code will generate
10793 debugging messages. See the file
10794 Documentation/filesystems/devfs/boot-options for more details.
10798 NFS file system support
10800 If you are connected to some other (usually local) Unix computer
10801 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
10802 on that computer (the NFS server) using the Network File Sharing
10803 protocol, say Y. "Mounting files" means that the client can access
10804 the files with usual UNIX commands as if they were sitting on the
10805 client's hard disk. For this to work, the server must run the
10806 programs nfsd and mountd (but does not need to have NFS file system
10807 support enabled in its kernel). NFS is explained in the Network
10808 Administrator's Guide, available from
10809 http://www.linuxdoc.org/docs.html#guide , on its man page: "man
10810 nfs", and in the NFS-HOWTO.
10812 A superior but less widely used alternative to NFS is provided by
10813 the Coda file system; see "Coda file system support" below.
10815 If you say Y here, you should have said Y to TCP/IP networking also.
10816 This option would enlarge your kernel by about 27 KB.
10818 This file system is also available as a module ( = code which can be
10819 inserted in and removed from the running kernel whenever you want).
10820 The module is called nfs.o. If you want to compile it as a module,
10821 say M here and read Documentation/modules.txt.
10823 If you are configuring a diskless machine which will mount its root
10824 file system over NFS at boot time, say Y here and to "IP: kernel
10825 level autoconfiguration" above and to "Root file system on NFS"
10826 below. You cannot compile this driver as a module in this case.
10827 There are two packages designed for booting diskless machines over
10828 the net: netboot and etherboot, both available via FTP from
10829 ftp://metalab.unc.edu/pub/Linux/system/boot/ethernet/ .
10831 If you don't know what all this is about, say N.
10833 Provide NFSv3 client support (EXPERIMENTAL)
10835 Say Y here if you want your NFS client to be able to speak the newer
10836 version 3 of the NFS protocol.
10840 Root file system on NFS
10842 If you want your Linux box to mount its whole root file system (the
10843 one containing the directory /) from some other computer over the
10844 net via NFS (presumably because your box doesn't have a hard disk),
10845 say Y. Read Documentation/nfsroot.txt for details. It is likely that
10846 in this case, you also want to say Y to "IP: kernel level
10847 autoconfiguration" so that your box can discover its network address
10850 Most people say N here.
10854 If you want your Linux box to act as an NFS *server*, so that other
10855 computers on your local network which support NFS can access certain
10856 directories on your box transparently, you have two options: you can
10857 use the self-contained user space program nfsd, in which case you
10858 should say N here, or you can say Y and use the kernel based NFS
10859 server. The advantage of the kernel based solution is that it is
10862 In either case, you will need support software; the respective
10863 locations are given in the file Documentation/Changes in the NFS
10866 If you say Y here, you will get support for version 2 of the NFS
10867 protocol (NFSv2). If you also want NFSv3, say Y to the next question
10870 Please read the NFS-HOWTO, available from
10871 http://www.linuxdoc.org/docs.html#howto .
10873 The NFS server is also available as a module ( = code which can be
10874 inserted in and removed from the running kernel whenever you want).
10875 The module is called nfsd.o. If you want to compile it as a module,
10876 say M here and read Documentation/modules.txt. If unsure, say N.
10878 Provide NFSv3 server support
10880 If you would like to include the NFSv3 server as well as the NFSv2
10881 server, say Y here. If unsure, say Y.
10883 Provide NFS over TCP server support DEVELOPER ONLY
10885 If you are a developer and want to work on fixing problems with
10886 NFS server over TCP support, say Y here. If unsure, say N.
10888 Some problems can be found by looking for FIXME in net/sunrpc/svcsock.c
10890 OS/2 HPFS file system support
10892 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
10893 is the file system used for organizing files on OS/2 hard disk
10894 partitions. Say Y if you want to be able to read files from and
10895 write files to an OS/2 HPFS partition on your hard drive. OS/2
10896 floppies however are in regular MSDOS format, so you don't need this
10897 option in order to be able to read them. Read
10898 Documentation/filesystems/hpfs.txt.
10900 This file system is also available as a module ( = code which can be
10901 inserted in and removed from the running kernel whenever you want).
10902 The module is called hpfs.o. If you want to compile it as a module,
10903 say M here and read Documentation/modules.txt. If unsure, say N.
10905 NTFS support (read only)
10907 NTFS is the file system of Microsoft Windows NT. Say Y if you want
10908 to get read access to files on NTFS partitions of your hard drive.
10909 The Linux NTFS driver supports most of the mount options of the VFAT
10910 driver, see Documentation/filesystems/ntfs.txt. Saying Y here will
10911 give you read-only access to NTFS partitions.
10913 This code is also available as a module ( = code which can be
10914 inserted in and removed from the running kernel whenever you want).
10915 The module will be called ntfs.o. If you want to compile it as a
10916 module, say M here and read Documentation/modules.txt.
10918 NTFS write support (DANGEROUS)
10920 If you say Y here, you will (maybe) be able to write to NTFS file
10921 systems as well as read from them. The read-write support in
10922 NTFS is far from being complete and is not well tested. If you
10923 say Y here, back up your NTFS volume first since it may get
10924 damaged. Also, make sure to run chkdsk from within Microsoft
10925 Windows NT after having performed any writes to a NTFS partition
10926 from Linux to detect any problems as early as possible.
10927 Please note that write support is limited to Windows NT4 and
10932 System V and Coherent file system support (read only)
10934 SCO, Xenix and Coherent are commercial Unix systems for Intel
10935 machines. Saying Y here would allow you to read from their floppies
10936 and hard disk partitions. If you also want to write to these media,
10937 say Y to "SYSV file system write support" below.
10939 If you have floppies or hard disk partitions like that, it is likely
10940 that they contain binaries from those other Unix systems; in order
10941 to run these binaries, you will want to install iBCS2 (Intel Binary
10942 Compatibility Standard is a kernel module which lets you run SCO,
10943 Xenix, Wyse, UnixWare, Dell Unix and System V programs under Linux
10944 and is often needed to run commercial software that's only available
10945 for those systems. It's available via FTP (user: anonymous) from
10946 ftp://tsx-11.mit.edu/pub/linux/BETA ).
10948 If you only intend to mount files from some other Unix over the
10949 network using NFS, you don't need the System V file system support
10950 (but you need NFS file system support obviously).
10952 Note that this option is generally not needed for floppies, since a
10953 good portable way to transport files and directories between unixes
10954 (and even other operating systems) is given by the tar program ("man
10955 tar" or preferably "info tar"). Note also that this option has
10956 nothing whatsoever to do with the option "System V IPC". Read about
10957 the System V file system in Documentation/filesystems/sysv-fs.txt.
10958 Saying Y here will enlarge your kernel by about 27 KB.
10960 If you want to compile this as a module ( = code which can be
10961 inserted in and removed from the running kernel whenever you want),
10962 say M here and read Documentation/modules.txt. The module will be
10965 If you haven't heard about all of this before, it's safe to say N.
10967 SYSV file system write support (DANGEROUS)
10968 CONFIG_SYSV_FS_WRITE
10969 If you say Y here, you will be able to write to hard drive
10970 partitions and floppy disks which carry a SYSV file system used the
10971 commercial Unixes SCO, Xenix and Coherent.
10973 This support is experimental and you may destroy your data. If
10976 Amiga FFS file system support
10978 The Fast File System (FFS) is the common file system used on hard
10979 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
10980 if you want to be able to read and write files from and to an Amiga
10981 FFS partition on your hard drive. Amiga floppies however cannot be
10982 read with this driver due to an incompatibility of the floppy
10983 controller used in an Amiga and the standard floppy controller in
10984 PCs and workstations. Read Documentation/filesystems/affs.txt and
10987 With this driver you can also mount disk files used by Bernd
10988 Schmidt's Un*X Amiga Emulator (http://www.freiburg.linux.de/~uae/ ).
10989 If you want to do this, you will also need to say Y or M to "Loop
10990 device support", above.
10992 This file system is also available as a module ( = code which can be
10993 inserted in and removed from the running kernel whenever you want).
10994 The module is called affs.o. If you want to compile it as a module,
10995 say M here and read Documentation/modules.txt. If unsure, say N.
10997 Apple Macintosh file system support (EXPERIMENTAL)
10999 If you say Y here, you will be able to mount Macintosh-formatted
11000 floppy disks and hard drive partitions with full read-write access.
11001 Please read fs/hfs/HFS.txt to learn about the available mount
11004 This file system support is also available as a module ( = code
11005 which can be inserted in and removed from the running kernel
11006 whenever you want). The module is called hfs.o. If you want to
11007 compile it as a module, say M here and read
11008 Documentation/modules.txt.
11010 ROM file system support
11012 This is a very small read-only file system mainly intended for
11013 initial ram disks of installation disks, but it could be used for
11014 other read-only media as well. Read
11015 Documentation/filesystems/romfs.txt for details.
11017 This file system support is also available as a module ( = code
11018 which can be inserted in and removed from the running kernel
11019 whenever you want). The module is called romfs.o. If you want to
11020 compile it as a module, say M here and read
11021 Documentation/modules.txt. Note that the file system of your root
11022 partition (the one containing the directory /) cannot be a module.
11024 If you don't know whether you need it, then you don't need it:
11027 QNX4 file system support (read only) (EXPERIMENTAL)
11029 This is the file system used by the operating system QNX 4. Say Y if
11030 you intend to mount QNX hard disks or floppies. Unless you say Y to
11031 "QNX4FS read-write support" below, you will only be able to read
11032 these file systems.
11034 This file system support is also available as a module ( = code
11035 which can be inserted in and removed from the running kernel
11036 whenever you want). The module is called qnx4.o. If you want to
11037 compile it as a module, say M here and read
11038 Documentation/modules.txt.
11040 If you don't know whether you need it, then you don't need it:
11043 QNX4FS write support (DANGEROUS)
11045 Say Y if you want to test write support for QNX4 file systems.
11047 Kernel automounter support
11049 The automounter is a tool to automatically mount remote file systems
11050 on demand. This implementation is partially kernel-based to reduce
11051 overhead in the already-mounted case; this is unlike the BSD
11052 automounter (amd), which is a pure user space daemon.
11054 To use the automounter you need the user-space tools from the autofs
11055 package; you can find the location in Documentation/Changes. You
11056 also want to answer Y to "NFS file system support", below.
11058 If you want to use the newer version of the automounter with more
11059 features, say N here and say Y to "Kernel automounter v4 support",
11062 If you want to compile this as a module ( = code which can be
11063 inserted in and removed from the running kernel whenever you want),
11064 say M here and read Documentation/modules.txt. The module will be
11067 If you are not a part of a fairly large, distributed network, you
11068 probably do not need an automounter, and can say N here.
11070 Kernel automounter v4 support
11072 The automounter is a tool to automatically mount remote file systems
11073 on demand. This implementation is partially kernel-based to reduce
11074 overhead in the already-mounted case; this is unlike the BSD
11075 automounter (amd), which is a pure user space daemon.
11077 To use the automounter you need the user-space tools from
11078 ftp://ftp.kernel.org/pub/linux/daemons/autofs/testing-v4 ; you also
11079 want to answer Y to "NFS file system support", below.
11081 If you want to compile this as a module ( = code which can be
11082 inserted in and removed from the running kernel whenever you want),
11083 say M here and read Documentation/modules.txt. The module will be
11084 called autofs4.o. You will need to add "alias autofs autofs4" to
11085 your modules configuration file.
11087 If you are not a part of a fairly large, distributed network or
11088 don't have a laptop which needs to dynamically reconfigure to the
11089 local network, you probably do not need an automounter, and can say
11092 EFS file system support (read-only) (EXPERIMENTAL)
11094 EFS is an older file system used for non-ISO9660 CDROMs and hard
11095 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
11096 uses the XFS file system for hard disk partitions however).
11098 This implementation only offers read-only access. If you don't know
11099 what all this is about, it's safe to say N. For more information
11100 about EFS see its home page at http://aeschi.ch.eu.org/efs/ .
11102 If you want to compile the EFS file system support as a module ( =
11103 code which can be inserted in and removed from the running kernel
11104 whenever you want), say M here and read Documentation/modules.txt.
11105 The module will be called efs.o.
11107 Journalling Flash File System (JFFS) support (EXPERIMENTAL)
11109 JFFS is a new file system designed for use on flash memory devices
11110 rather than on block devices. It was developed on the 2.0 kernel
11111 by Axis Communications AB for use on their Linux-based products,
11112 and released under GPL, then 'borrowed' and ported to work with
11113 the 2.4 kernel and the new Memory Technology Device system.
11115 The 2.4 port is experimental and not yet supported by Axis. Basically,
11116 the good bits are probably theirs, and if it's broken in 2.4 it's
11117 probably our fault. See http://www.developer.axis.com/software/jffs/
11118 for more information about JFFS.
11120 Any potential patches or queries should be sent to Axis' mailing
11121 list for JFFS: <jffs-dev@axis.com>
11123 UFS file system support (read-only)
11125 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
11126 OpenBSD and NeXTstep) use a file system called UFS. Some System V
11127 Unixes can create and mount hard disk partitions and diskettes using
11128 this file system as well. Saying Y here will allow you to read from
11129 these partitions; if you also want to write to them, say Y to the
11130 experimental "UFS file system write support", below. Please read the
11131 file Documentation/filesystems/ufs.txt for more information.
11133 If you only intend to mount files from some other Unix over the
11134 network using NFS, you don't need the UFS file system support (but
11135 you need NFS file system support obviously).
11137 Note that this option is generally not needed for floppies, since a
11138 good portable way to transport files and directories between unixes
11139 (and even other operating systems) is given by the tar program ("man
11140 tar" or preferably "info tar").
11142 When accessing NeXTstep files, you may need to convert them from the
11143 NeXT character set to the Latin1 character set; use the program
11144 recode ("info recode") for this purpose.
11146 If you want to compile the UFS file system support as a module ( =
11147 code which can be inserted in and removed from the running kernel
11148 whenever you want), say M here and read Documentation/modules.txt.
11149 The module will be called ufs.o.
11151 If you haven't heard about all of this before, it's safe to say N.
11153 UFS file system write support (DANGEROUS)
11154 CONFIG_UFS_FS_WRITE
11155 Say Y here if you want to try writing to UFS partitions. This is
11156 experimental, so you should back up your UFS partitions beforehand.
11158 Advanced partition selection
11159 CONFIG_PARTITION_ADVANCED
11160 Say Y here if you would like to use hard disks under Linux which
11161 were partitioned under an operating system running on a different
11162 architecture than your Linux system.
11164 Note that the answer to this question won't directly affect the
11165 kernel: saying N will just cause this configure script to skip all
11166 the questions about foreign partitioning schemes.
11170 Alpha OSF partition support
11171 CONFIG_OSF_PARTITION
11172 Say Y here if you would like to use hard disks under Linux which
11173 were partitioned on an Alpha machine.
11175 Macintosh partition map support
11176 CONFIG_MAC_PARTITION
11177 Say Y here if you would like to use hard disks under Linux which
11178 were partitioned on a Macintosh.
11180 PC BIOS (MSDOS partition tables) support
11181 CONFIG_MSDOS_PARTITION
11182 Say Y here if you would like to use hard disks under Linux which
11183 were partitioned on an x86 PC (not necessarily by DOS).
11185 BSD disklabel (FreeBSD partition tables) support
11186 CONFIG_BSD_DISKLABEL
11187 FreeBSD uses its own hard disk partition scheme on your PC. It
11188 requires only one entry in the primary partition table of your disk
11189 and manages it similarly to DOS extended partitions, putting in its
11190 first sector a new partition table in BSD disklabel format. Saying Y
11191 here allows you to read these disklabels and further mount FreeBSD
11192 partitions from within Linux if you have also said Y to "UFS
11193 file system support", above. If you don't know what all this is
11196 Sun partition tables support
11197 CONFIG_SUN_PARTITION
11198 Like most systems, SunOS uses its own hard disk partition table
11199 format, incompatible with all others. Saying Y here allows you to
11200 read these partition tables and further mount SunOS partitions from
11201 within Linux if you have also said Y to "UFS file system support",
11202 above. This is mainly used to carry data from a SPARC under SunOS to
11203 your Linux box via a removable medium like magneto-optical or ZIP
11204 drives; note however that a good portable way to transport files and
11205 directories between unixes (and even other operating systems) is
11206 given by the tar program ("man tar" or preferably "info tar"). If
11207 you don't know what all this is about, say N.
11209 Solaris (x86) partition table support
11210 CONFIG_SOLARIS_X86_PARTITION
11211 Like most systems, Solaris x86 uses its own hard disk partition
11212 table format, incompatible with all others. Saying Y here allows you
11213 to read these partition tables and further mount Solaris x86
11214 partitions from within Linux if you have also said Y to "UFS
11215 file system support", above.
11217 SGI partition support
11218 CONFIG_SGI_PARTITION
11219 Say Y here if you would like to be able to read the hard disk
11220 partition table format used by SGI machines.
11222 ADFS file system support (EXPERIMENTAL)
11224 The Acorn Disc Filing System is the standard file system of the
11225 RiscOS operating system which runs on Acorn's ARM-based Risc PC
11226 systems and the Acorn Archimedes range of machines. If you say Y
11227 here, Linux will be able to read from ADFS partitions on hard drives
11228 and from ADFS-formatted floppy discs. If you also want to be able to
11229 write to those devices, say Y to "ADFS write support" below.
11231 The ADFS partition should be the first partition (i.e.,
11232 /dev/[hs]d?1) on each of your drives. Please read the file
11233 Documentation/filesystems/adfs.txt for further details.
11235 This code is also available as a module called adfs.o ( = code which
11236 can be inserted in and removed from the running kernel whenever you
11237 want). If you want to compile it as a module, say M here and read
11238 Documentation/modules.txt.
11242 ADFS write support (DANGEROUS)
11244 If you say Y here, you will be able to write to ADFS partitions on
11245 hard drives and ADFS-formatted floppy disks. This is experimental
11246 codes, so if you're unsure, say N.
11248 /dev/pts file system for Unix98 PTYs
11250 You should say Y here if you said Y to "Unix98 PTY support" above.
11251 You'll then get a virtual file system which can be mounted on
11252 /dev/pts with "mount -t devpts". This, together with the pseudo
11253 terminal master multiplexer /dev/ptmx, is used for pseudo terminal
11254 support as described in The Open Group's Unix98 standard: in order
11255 to acquire a pseudo terminal, a process opens /dev/ptmx; the number
11256 of the pseudo terminal is then made available to the process and the
11257 pseudo terminal slave can be accessed as /dev/pts/<number>. What was
11258 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
11260 The GNU C library glibc 2.1 contains the requisite support for this
11261 mode of operation; you also need client programs that use the Unix98
11262 API. Please read Documentation/Changes for more information about
11263 the Unix98 pty devices.
11265 Note that the experimental "/dev file system support"
11266 (CONFIG_DEVFS_FS) is a more general facility.
11268 UnixWare slices support (EXPERIMENTAL)
11269 CONFIG_UNIXWARE_DISKLABEL
11270 Like some systems, UnixWare uses its own slice table inside a
11271 partition (VTOC - Virtual Table of Contents). Its format is
11272 incompatible with all other OSes. Saying Y here allows you to read
11273 VTOC and further mount UnixWare partitions read-only from within
11274 Linux if you have also said Y to "UFS file system support" or
11275 "System V and Coherent file system support", above.
11277 This is mainly used to carry data from a UnixWare box to your
11278 Linux box via a removable medium like magneto-optical, ZIP or
11279 removable IDE drives. Note, however, that a good portable way to
11280 transport files and directories between unixes (and even other
11281 operating systems) is given by the tar program ("man tar" or
11282 preferably "info tar").
11284 If you don't know what all this is about, say N.
11286 SMB file system support (to mount Windows shares etc.)
11288 SMB (Server Message Block) is the protocol Windows for Workgroups
11289 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
11290 files and printers over local networks. Saying Y here allows you to
11291 mount their file systems (often called "shares" in this context) and
11292 access them just like any other Unix directory. Currently, this
11293 works only if the Windows machines use TCP/IP as the underlying
11294 transport protocol, and not NetBEUI. For details, read
11295 Documentation/filesystems/smbfs.txt and the SMB-HOWTO, available
11296 from http://www.linuxdoc.org/docs.html#howto .
11298 Note: if you just want your box to act as an SMB *server* and make
11299 files and printing services available to Windows clients (which need
11300 to have a TCP/IP stack), you don't need to say Y here; you can use
11301 the program samba (available via FTP (user: anonymous) in
11302 ftp://metalab.unc.edu/pub/Linux/system/network/samba ) for that.
11304 General information about how to connect Linux, Windows machines and
11305 Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
11307 If you want to compile the SMB support as a module ( = code which
11308 can be inserted in and removed from the running kernel whenever you
11309 want), say M here and read Documentation/modules.txt. The module
11310 will be called smbfs.o. Most people say N, however.
11312 nls support setting
11313 CONFIG_SMB_NLS_REMOTE
11314 This setting allows you to specify a default value for which
11315 codepage the server uses. If this field is left blank no
11316 translations will be done by default. The local codepage/charset
11317 default to CONFIG_NLS_DEFAULT.
11319 The nls settings can be changed at mount time, if your smbmount
11320 supports that, using the codepage and iocharset parameters.
11322 Currently no smbmount distributed with samba supports this, it is
11323 assumed future versions will. In the meantime you can get an
11324 unofficial patch for samba 2.0.7 from:
11325 http://www.hojdpunkten.ac.se/054/samba/index.html
11327 Coda file system support (advanced network fs)
11329 Coda is an advanced network file system, similar to NFS in that it
11330 enables you to mount file systems of a remote server and access them
11331 with regular Unix commands as if they were sitting on your hard
11332 disk. Coda has several advantages over NFS: support for disconnected
11333 operation (e.g. for laptops), read/write server replication,
11334 security model for authentication and encryption, persistent client
11335 caches and write back caching.
11337 If you say Y here, your Linux box will be able to act as a Coda
11338 *client*. You will need user level code as well, both for the client
11339 and server. Servers are currently user level, i.e. they need no
11340 kernel support. Please read Documentation/filesystems/coda.txt and
11341 check out the Coda home page http://www.coda.cs.cmu.edu .
11343 If you want to compile the coda client support as a module ( = code
11344 which can be inserted in and removed from the running kernel
11345 whenever you want), say M here and read Documentation/modules.txt.
11346 The module will be called coda.o.
11348 NCP file system support (to mount NetWare volumes)
11350 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
11351 used by Novell NetWare clients to talk to file servers. It is to IPX
11352 what NFS is to TCP/IP, if that helps. Saying Y here allows you to
11353 mount NetWare file server volumes and to access them just like any
11354 other Unix directory. For details, please read the file
11355 Documentation/filesystems/ncpfs.txt in the kernel source and the
11356 IPX-HOWTO from http://www.linuxdoc.org/docs.html#howto .
11358 You do not have to say Y here if you want your Linux box to act as a
11359 file *server* for Novell NetWare clients.
11361 General information about how to connect Linux, Windows machines and
11362 Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
11364 If you want to compile this as a module ( = code which can be
11365 inserted in and removed from the running kernel whenever you want),
11366 say M here and read Documentation/modules.txt. The module will be
11367 called ncpfs.o. Say N unless you are connected to a Novell network.
11370 CONFIG_NCPFS_PACKET_SIGNING
11371 NCP allows packets to be signed for stronger security. If you want
11372 security, say Y. Normal users can leave it off. To be able to use
11373 packet signing you must use ncpfs > 2.0.12.
11375 Proprietary file locking
11376 CONFIG_NCPFS_IOCTL_LOCKING
11377 Allows locking of records on remote volumes. Say N unless you have
11378 special applications which are able to utilize this locking scheme.
11380 Clear remove/delete inhibit when needed
11381 CONFIG_NCPFS_STRONG
11382 Allows manipulation of files flagged as Delete or Rename Inhibit. To
11383 use this feature you must mount volumes with the ncpmount parameter
11384 "-s" (ncpfs-2.0.12 and newer). Say Y unless you are not mounting
11385 volumes with -f 444.
11387 Use NFS namespace when available
11388 CONFIG_NCPFS_NFS_NS
11389 Allows you to utilize NFS namespace on NetWare servers. It brings
11390 you case sensitive filenames. Say Y. You can disable it at
11391 mount-time with the `-N nfs' parameter of ncpmount.
11393 Use OS2/LONG namespace when available
11394 CONFIG_NCPFS_OS2_NS
11395 Allows you to utilize OS2/LONG namespace on NetWare servers.
11396 Filenames in this namespace are limited to 255 characters, they are
11397 case insensitive, and case in names is preserved. Say Y. You can
11398 disable it at mount time with the -N os2 parameter of ncpmount.
11400 Lowercase DOS filenames on LONG namespace volume
11401 CONFIG_NCPFS_SMALLDOS
11402 If you say Y here, every filename on a NetWare server volume using
11403 the OS2/LONG namespace and created under DOS or on a volume using
11404 DOS namespace will be converted to lowercase characters.
11405 Saying N here will give you these filenames in uppercase.
11407 This is only a cosmetic option since the OS2/LONG namespace is case
11408 insensitive. The only major reason for this option is backward
11409 compatibility when moving from DOS to OS2/LONG namespace support.
11410 Long filenames (created by Win95) will not be affected.
11412 This option does not solve the problem that filenames appear
11413 differently under Linux and under Windows, since Windows does an
11414 additional conversions on the client side. You can achieve similar
11415 effects by saying Y to "Allow using of Native Language Support"
11418 Allow mounting of volume subdirectories
11419 CONFIG_NCPFS_MOUNT_SUBDIR
11420 Allows you to mount not only whole servers or whole volumes, but
11421 also subdirectories from a volume. It can be used to reexport data
11422 and so on. There is no reason to say N, so Y is recommended unless
11423 you count every byte.
11425 To utilize this feature you must use ncpfs-2.0.12 or newer.
11427 NDS authentication support
11428 CONFIG_NCPFS_NDS_DOMAINS
11429 This allows storing NDS private keys in kernel space where they
11430 can be used to authenticate another server as interserver NDS
11431 accesses need it. You must use ncpfs-2.0.12.1 or newer to utilize
11432 this feature. Say Y if you are using NDS connections to NetWare
11433 servers. Do not say Y if security is primary for you because root
11434 can read your session key (from /proc/kcore).
11436 Allow using of Native Language Support
11438 Allows you to use codepages and I/O charsets for file name
11439 translation between the server file system and input/output. This
11440 may be useful, if you want to access the server with other operating
11441 systems, e.g. Windows 95. See also NLS for more Information.
11443 To select codepages and I/O charsets use ncpfs-2.2.0.13 or newer.
11445 Symbolic links and mode permission bits
11446 CONFIG_NCPFS_EXTRAS
11447 This enables the use of symbolic links and an execute permission
11448 bit on NCPFS. The file server need not have long name space or NFS
11449 name space loaded for these to work.
11451 To use the new attributes, it is recommended to use the flags
11452 '-f 600 -d 755' on the ncpmount command line.
11454 nls default codepage
11456 The default NLS used when mounting filesystem. Currently, the valid
11458 big5, cp437, cp737, cp775, cp850, cp852, cp855, cp857, cp860, cp861,
11459 cp862, cp863, cp864, cp865, cp866, cp869, cp874, cp932, cp936,
11460 cp949, cp950, euc-jp, euc-kr, gb2312, iso8859-1, iso8859-2, iso8859-3,
11461 iso8859-4, iso8859-5, iso8859-6, iso8859-7, iso8859-8, iso8859-9,
11462 iso8859-14, iso8859-15, koi8-r, sjis
11463 If you specify a wrong value, it will use the built-in NLS; compatible
11466 If unsure, specify it as "iso8859-1".
11469 CONFIG_NLS_CODEPAGE_437
11470 The Microsoft FAT file system family can deal with filenames in
11471 native language character sets. These character sets are stored
11472 in so-called DOS codepages. You need to include the appropriate
11473 codepage if you want to be able to read/write these filenames on
11474 DOS/Windows partitions correctly. This does apply to the filenames
11475 only, not to the file contents. You can include several codepages;
11476 say Y here if you want to include the DOS codepage that is used in
11477 the United States and parts of Canada. This is recommended.
11480 CONFIG_NLS_CODEPAGE_737
11481 The Microsoft FAT file system family can deal with filenames in
11482 native language character sets. These character sets are stored
11483 in so-called DOS codepages. You need to include the appropriate
11484 codepage if you want to be able to read/write these filenames on
11485 DOS/Windows partitions correctly. This does apply to the filenames
11486 only, not to the file contents. You can include several codepages;
11487 say Y here if you want to include the DOS codepage that is used for
11488 Greek. If unsure, say N.
11491 CONFIG_NLS_CODEPAGE_775
11492 The Microsoft FAT file system family can deal with filenames in
11493 native language character sets. These character sets are stored
11494 in so-called DOS codepages. You need to include the appropriate
11495 codepage if you want to be able to read/write these filenames on
11496 DOS/Windows partitions correctly. This does apply to the filenames
11497 only, not to the file contents. You can include several codepages;
11498 say Y here if you want to include the DOS codepage that is used
11499 for the Baltic Rim Languages. If unsure, say N.
11502 CONFIG_NLS_CODEPAGE_850
11503 The Microsoft FAT file system family can deal with filenames in
11504 native language character sets. These character sets are stored in
11505 so-called DOS codepages. You need to include the appropriate
11506 codepage if you want to be able to read/write these filenames on
11507 DOS/Windows partitions correctly. This does apply to the filenames
11508 only, not to the file contents. You can include several codepages;
11509 say Y here if you want to include the DOS codepage that is used for
11510 much of Europe -- United Kingdom, Germany, Spain, Italy, and [add
11511 more countries here]. It has some characters useful to many European
11512 languages that are not part of the US codepage 437.
11517 CONFIG_NLS_CODEPAGE_852
11518 The Microsoft FAT file system family can deal with filenames in
11519 native language character sets. These character sets are stored in
11520 so-called DOS codepages. You need to include the appropriate
11521 codepage if you want to be able to read/write these filenames on
11522 DOS/Windows partitions correctly. This does apply to the filenames
11523 only, not to the file contents. You can include several codepages;
11524 say Y here if you want to include the Latin 2 codepage used by DOS
11525 for much of Central and Eastern Europe. It has all the required
11526 characters for these languages: Albanian, Croatian, Czech, English,
11527 Finnish, Hungarian, Irish, German, Polish, Romanian, Serbian (Latin
11528 transcription), Slovak, Slovenian, and Sorbian.
11531 CONFIG_NLS_CODEPAGE_855
11532 The Microsoft FAT file system family can deal with filenames in
11533 native language character sets. These character sets are stored in
11534 so-called DOS codepages. You need to include the appropriate
11535 codepage if you want to be able to read/write these filenames on
11536 DOS/Windows partitions correctly. This does apply to the filenames
11537 only, not to the file contents. You can include several codepages;
11538 say Y here if you want to include the DOS codepage for Cyrillic.
11541 CONFIG_NLS_CODEPAGE_857
11542 The Microsoft FAT file system family can deal with filenames in
11543 native language character sets. These character sets are stored in
11544 so-called DOS codepages. You need to include the appropriate
11545 codepage if you want to be able to read/write these filenames on
11546 DOS/Windows partitions correctly. This does apply to the filenames
11547 only, not to the file contents. You can include several codepages;
11548 say Y here if you want to include the DOS codepage for Turkish.
11551 CONFIG_NLS_CODEPAGE_860
11552 The Microsoft FAT file system family can deal with filenames in
11553 native language character sets. These character sets are stored in
11554 so-called DOS codepages. You need to include the appropriate
11555 codepage if you want to be able to read/write these filenames on
11556 DOS/Windows partitions correctly. This does apply to the filenames
11557 only, not to the file contents. You can include several codepages;
11558 say Y here if you want to include the DOS codepage for Portuguese.
11561 CONFIG_NLS_CODEPAGE_861
11562 The Microsoft FAT file system family can deal with filenames in
11563 native language character sets. These character sets are stored in
11564 so-called DOS codepages. You need to include the appropriate
11565 codepage if you want to be able to read/write these filenames on
11566 DOS/Windows partitions correctly. This does apply to the filenames
11567 only, not to the file contents. You can include several codepages;
11568 say Y here if you want to include the DOS codepage for Icelandic.
11571 CONFIG_NLS_CODEPAGE_862
11572 The Microsoft FAT file system family can deal with filenames in
11573 native language character sets. These character sets are stored in
11574 so-called DOS codepages. You need to include the appropriate
11575 codepage if you want to be able to read/write these filenames on
11576 DOS/Windows partitions correctly. This does apply to the filenames
11577 only, not to the file contents. You can include several codepages;
11578 say Y here if you want to include the DOS codepage for Hebrew.
11581 CONFIG_NLS_CODEPAGE_863
11582 The Microsoft FAT file system family can deal with filenames in
11583 native language character sets. These character sets are stored in
11584 so-called DOS codepages. You need to include the appropriate
11585 codepage if you want to be able to read/write these filenames on
11586 DOS/Windows partitions correctly. This does apply to the filenames
11587 only, not to the file contents. You can include several codepages;
11588 say Y here if you want to include the DOS codepage for Canadian
11592 CONFIG_NLS_CODEPAGE_864
11593 The Microsoft FAT file system family can deal with filenames in
11594 native language character sets. These character sets are stored in
11595 so-called DOS codepages. You need to include the appropriate
11596 codepage if you want to be able to read/write these filenames on
11597 DOS/Windows partitions correctly. This does apply to the filenames
11598 only, not to the file contents. You can include several codepages;
11599 say Y here if you want to include the DOS codepage for Arabic.
11602 CONFIG_NLS_CODEPAGE_865
11603 The Microsoft FAT file system family can deal with filenames in
11604 native language character sets. These character sets are stored in
11605 so-called DOS codepages. You need to include the appropriate
11606 codepage if you want to be able to read/write these filenames on
11607 DOS/Windows partitions correctly. This does apply to the filenames
11608 only, not to the file contents. You can include several codepages;
11609 say Y here if you want to include the DOS codepage for the Nordic
11610 European countries.
11613 CONFIG_NLS_CODEPAGE_866
11614 The Microsoft FAT file system family can deal with filenames in
11615 native language character sets. These character sets are stored in
11616 so-called DOS codepages. You need to include the appropriate
11617 codepage if you want to be able to read/write these filenames on
11618 DOS/Windows partitions correctly. This does apply to the filenames
11619 only, not to the file contents. You can include several codepages;
11620 say Y here if you want to include the DOS codepage for
11624 CONFIG_NLS_CODEPAGE_869
11625 The Microsoft FAT file system family can deal with filenames in
11626 native language character sets. These character sets are stored in
11627 so-called DOS codepages. You need to include the appropriate
11628 codepage if you want to be able to read/write these filenames on
11629 DOS/Windows partitions correctly. This does apply to the filenames
11630 only, not to the file contents. You can include several codepages;
11631 say Y here if you want to include the DOS codepage for Greek.
11634 CONFIG_NLS_CODEPAGE_874
11635 The Microsoft FAT file system family can deal with filenames in
11636 native language character sets. These character sets are stored in
11637 so-called DOS codepages. You need to include the appropriate
11638 codepage if you want to be able to read/write these filenames on
11639 DOS/Windows partitions correctly. This does apply to the filenames
11640 only, not to the file contents. You can include several codepages;
11641 say Y here if you want to include the DOS codepage for Thai.
11644 CONFIG_NLS_CODEPAGE_932
11645 The Microsoft fat filesystem family can deal with filenames in
11646 native language character sets. These character sets are stored in
11647 so-called DOS codepages. You need to include the appropriate
11648 codepage if you want to be able to read/write these filenames on
11649 DOS/Windows partitions correctly. This does apply to the filenames
11650 only, not to the file contents. You can include several codepages;
11651 say Y here if you want to include the DOS codepage for Shift-JIS
11652 or EUC-JP. To use EUC-JP, you can use 'euc-jp' as mount option or
11653 NLS Default value during kernel configuration , instead of 'cp932'
11656 CONFIG_NLS_CODEPAGE_936
11657 The Microsoft fat filesystem family can deal with filenames in
11658 native language character sets. These character sets are stored in
11659 so-called DOS codepages. You need to include the appropriate
11660 codepage if you want to be able to read/write these filenames on
11661 DOS/Windows partitions correctly. This does apply to the filenames
11662 only, not to the file contents. You can include several codepages;
11663 say Y here if you want to include the DOS codepage for Simplified
11667 CONFIG_NLS_CODEPAGE_949
11668 The Microsoft fat filesystem family can deal with filenames in
11669 native language character sets. These character sets are stored in
11670 so-called DOS codepages. You need to include the appropriate
11671 codepage if you want to be able to read/write these filenames on
11672 DOS/Windows partitions correctly. This does apply to the filenames
11673 only, not to the file contents. You can include several codepages;
11674 say Y here if you want to include the DOS codepage for UHC.
11677 CONFIG_NLS_CODEPAGE_950
11678 The Microsoft fat filesystem family can deal with filenames in
11679 native language character sets. These character sets are stored in
11680 so-called DOS codepages. You need to include the appropriate
11681 codepage if you want to be able to read/write these filenames on
11682 DOS/Windows partitions correctly. This does apply to the filenames
11683 only, not to the file contents. You can include several codepages;
11684 say Y here if you want to include the DOS codepage for Traditional
11688 CONFIG_NLS_ISO8859_1
11689 If you want to display filenames with native language characters
11690 from the Microsoft FAT file system family or from JOLIET CDROMs
11691 correctly on the screen, you need to include the appropriate
11692 input/output character sets. Say Y here for the Latin 1 character
11693 set, which covers most West European languages such as Albanian,
11694 Catalan, Danish, Dutch, English, Faeroese, Finnish, French, German,
11695 Galician, Irish, Icelandic, Italian, Norwegian, Portuguese, Spanish,
11696 and Swedish. It is also the default for the US. If unsure, say Y.
11699 CONFIG_NLS_ISO8859_2
11700 If you want to display filenames with native language characters
11701 from the Microsoft FAT file system family or from JOLIET CDROMs
11702 correctly on the screen, you need to include the appropriate
11703 input/output character sets. Say Y here for the Latin 2 character
11704 set, which works for most Latin-written Slavic and Central European
11705 languages: Czech, German, Hungarian, Polish, Rumanian, Croatian,
11709 CONFIG_NLS_ISO8859_3
11710 If you want to display filenames with native language characters
11711 from the Microsoft FAT file system family or from JOLIET CDROMs
11712 correctly on the screen, you need to include the appropriate
11713 input/output character sets. Say Y here for the Latin 3 character
11714 set, which is popular with authors of Esperanto, Galician, Maltese,
11718 CONFIG_NLS_ISO8859_4
11719 If you want to display filenames with native language characters
11720 from the Microsoft FAT file system family or from JOLIET CDROMs
11721 correctly on the screen, you need to include the appropriate
11722 input/output character sets. Say Y here for the Latin 4 character
11723 set which introduces letters for Estonian, Latvian, and
11724 Lithuanian. It is an incomplete predecessor of Latin 6.
11727 CONFIG_NLS_ISO8859_5
11728 If you want to display filenames with native language characters
11729 from the Microsoft FAT file system family or from JOLIET CDROMs
11730 correctly on the screen, you need to include the appropriate
11731 input/output character sets. Say Y here for ISO8859-5, a Cyrillic
11732 character set with which you can type Bulgarian, Byelorussian,
11733 Macedonian, Russian, Serbian, and Ukrainian. Note that the charset
11734 KOI8-R is preferred in Russia.
11737 CONFIG_NLS_ISO8859_6
11738 If you want to display filenames with native language characters
11739 from the Microsoft FAT file system family or from JOLIET CDROMs
11740 correctly on the screen, you need to include the appropriate
11741 input/output character sets. Say Y here for ISO8859-6, the Arabic
11745 CONFIG_NLS_ISO8859_7
11746 If you want to display filenames with native language characters
11747 from the Microsoft FAT file system family or from JOLIET CDROMs
11748 correctly on the screen, you need to include the appropriate
11749 input/output character sets. Say Y here for ISO8859-7, the Modern
11750 Greek character set.
11753 CONFIG_NLS_ISO8859_8
11754 If you want to display filenames with native language characters
11755 from the Microsoft FAT file system family or from JOLIET CDROMs
11756 correctly on the screen, you need to include the appropriate
11757 input/output character sets. Say Y here for ISO8859-8, the Hebrew
11761 CONFIG_NLS_ISO8859_9
11762 If you want to display filenames with native language characters
11763 from the Microsoft FAT file system family or from JOLIET CDROMs
11764 correctly on the screen, you need to include the appropriate
11765 input/output character sets. Say Y here for the Latin 5 character
11766 set, and it replaces the rarely needed Icelandic letters in Latin 1
11767 with the Turkish ones. Useful in Turkey.
11770 CONFIG_NLS_ISO8859_10
11771 If you want to display filenames with native language characters
11772 from the Microsoft FAT file system family or from JOLIET CDROMs
11773 correctly on the screen, you need to include the appropriate
11774 input/output character sets. Say Y here for the Latin 6 character
11775 set, which adds the last Inuit (Greenlandic) and Sami (Lappish)
11776 letters that were missing in Latin 4 to cover the entire Nordic
11779 NLS ISO 8859-14 (Latin 8; Celtic)
11780 CONFIG_NLS_ISO8859_14
11781 If you want to display filenames with native language characters
11782 from the Microsoft FAT file system family or from JOLIET CDROMs
11783 correctly on the screen, you need to include the appropriate
11784 input/output character sets. Say Y here for the Latin 8 character
11785 set, which adds the last accented vowels for Welsh (aka Cymraeg)
11786 (and Manx Gaelic) hat were missing in Latin 1.
11787 http://linux.speech.cymru.org/ has further information.
11790 CONFIG_NLS_ISO8859_15
11791 If you want to display filenames with native language characters
11792 from the Microsoft FAT file system family or from JOLIET CDROMs
11793 correctly on the screen, you need to include the appropriate
11794 input/output character sets. Say Y here for the Latin 9 character
11795 set, which covers most West European languages such as Albanian,
11796 Catalan, Danish, Dutch, English, Estonian, Faeroese, Finnish,
11797 French, German, Galician, Irish, Icelandic, Italian, Norwegian,
11798 Portuguese, Spanish, and Swedish. Latin 9 is an update to
11799 Latin 1 (ISO 8859-1) that removes a handful of rarely used
11800 characters and instead adds support for Estonian, corrects the
11801 support for French and Finnish, and adds the new Euro character. If
11806 If you want to display filenames with native language characters
11807 from the Microsoft FAT file system family or from JOLIET CDROMs
11808 correctly on the screen, you need to include the appropriate
11809 input/output character sets. Say Y here for the preferred Russian
11814 If you say Y here, you will get support for terminal devices with
11815 display and keyboard devices. These are called "virtual" because you
11816 can run several virtual terminals (also called virtual consoles) on
11817 one physical terminal. This is rather useful, for example one
11818 virtual terminal can collect system messages and warnings, another
11819 one can be used for a text-mode user session, and a third could run
11820 an X session, all in parallel. Switching between virtual terminals
11821 is done with certain key combinations, usually Alt-<function key>.
11823 The setterm command ("man setterm") can be used to change the
11824 properties (such as colors or beeping) of a virtual terminal. The
11825 man page console_codes(4) ("man console_codes") contains the special
11826 character sequences that can be used to change those properties
11827 directly. The fonts used on virtual terminals can be changed with
11828 the setfont ("man setfont") command and the key bindings are defined
11829 with the loadkeys ("man loadkeys") command.
11831 You need at least one virtual terminal device in order to make use
11832 of your keyboard and monitor. Therefore, only people configuring an
11833 embedded system would want to say N here in order to save some
11834 memory; the only way to log into such a system is then via a serial
11835 or network connection.
11837 If unsure, say Y, or else you won't be able to do much with your new
11838 shiny Linux system :-)
11840 Support for console on virtual terminal
11842 The system console is the device which receives all kernel messages
11843 and warnings and which allows logins in single user mode. If you
11844 answer Y here, a virtual terminal (the device used to interact with
11845 a physical terminal) can be used as system console. This is the most
11846 common mode of operations, so you should say Y here unless you want
11847 the kernel messages be output only to a serial port (in which case
11848 you should say Y to "Console on serial port", below).
11850 If you do say Y here, by default the currently visible virtual
11851 terminal (/dev/tty0) will be used as system console. You can change
11852 that with a kernel command line option such as "console=tty3" which
11853 would use the third virtual terminal as system console. (Try "man
11854 bootparam" or see the documentation of your boot loader (lilo or
11855 loadlin) about how to pass options to the kernel at boot time.)
11859 Support for PowerMac keyboard
11860 CONFIG_MAC_KEYBOARD
11861 This option allows you to use an ADB keyboard attached to your
11862 machine. Note that this disables any other (ie. PS/2) keyboard
11863 support, even if your machine is physically capable of using both at
11866 If you use an ADB keyboard (4 pin connector), say Y here.
11867 If you use a PS/2 keyboard (6 pin connector), say N here.
11869 Standard/generic serial support
11871 This selects whether you want to include the driver for the standard
11872 serial ports. The standard answer is Y. People who might say N here
11873 are those that are setting up dedicated Ethernet WWW/FTP servers, or
11874 users that have one of the various bus mice instead of a serial
11875 mouse and don't intend to use their machine's standard serial port
11876 for anything. (Note that the Cyclades and Stallion multi serial port
11877 drivers do not need this driver built in for them to work.)
11879 If you want to compile this driver as a module, say M here and read
11880 Documentation/modules.txt. The module will be called serial.o.
11881 [WARNING: Do not compile this driver as a module if you are using
11882 non-standard serial ports, since the configuration information will
11883 be lost when the driver is unloaded. This limitation may be lifted
11886 BTW1: If you have a mouseman serial mouse which is not recognized by
11887 the X window system, try running gpm first.
11889 BTW2: If you intend to use a software modem (also called Winmodem)
11890 under Linux, forget it. These modems are crippled and require
11891 proprietary drivers which are only available under Windows.
11893 Most people will say Y or M here, so that they can use serial mice,
11894 modems and similar devices connecting to the standard serial ports.
11896 Support for console on serial port
11897 CONFIG_SERIAL_CONSOLE
11898 If you say Y here, it will be possible to use a serial port as the
11899 system console (the system console is the device which receives all
11900 kernel messages and warnings and which allows logins in single user
11901 mode). This could be useful if some terminal or printer is connected
11902 to that serial port.
11904 Even if you say Y here, the currently visible virtual console
11905 (/dev/tty0) will still be used as the system console by default, but
11906 you can alter that using a kernel command line option such as
11907 "console=ttyS1". (Try "man bootparam" or see the documentation of
11908 your boot loader (lilo or loadlin) about how to pass options to the
11909 kernel at boot time.)
11911 If you don't have a VGA card installed and you say Y here, the
11912 kernel will automatically use the first serial line, /dev/ttyS0, as
11917 Support for PowerMac serial ports
11919 If you have Macintosh style serial ports (8 pin mini-DIN), say Y
11920 here. If you also have regular serial ports and enable the driver
11921 for them, you can't currently use the serial console feature.
11923 Comtrol Rocketport support
11925 This is a driver for the Comtrol Rocketport cards which provide
11926 multiple serial ports. You would need something like this to connect
11927 more than two modems to your Linux box, for instance in order to
11928 become a dial-in server.
11930 If you want to compile this driver as a module, say M here and read
11931 Documentation/modules.txt. The module will be called rocket.o.
11933 Digiboard Intelligent async support
11935 This is a driver for Digi International's Xx, Xeve, and Xem series
11936 of cards which provide multiple serial ports. You would need
11937 something like this to connect more than two modems to your Linux
11938 box, for instance in order to become a dial-in server. This driver
11939 supports the original PC (ISA) boards as well as PCI, and EISA. If
11940 you have a card like this, say Y here and read the file
11941 Documentation/digiepca.txt.
11943 NOTE: There is another, separate driver for the Digiboard PC boards:
11944 "Digiboard PC/Xx Support" below. You should (and can) only select
11945 one of the two drivers.
11947 If you want to compile this driver as a module, say M here and read
11948 Documentation/modules.txt. The module will be called epca.o.
11950 Digiboard PC/Xx Support
11952 This is a driver for the Digiboard PC/Xe, PC/Xi, and PC/Xeve cards
11953 that give you many serial ports. You would need something like this
11954 to connect more than two modems to your Linux box, for instance in
11955 order to become a dial-in server. If you have a card like that, say
11956 Y here and read the file Documentation/digiboard.txt.
11958 If you want to compile this driver as a module, say M here and read
11959 Documentation/modules.txt. The module will be called pcxx.o.
11961 SDL RISCom/8 card support
11963 This is a driver for the SDL Communications RISCom/8 multiport card,
11964 which gives you many serial ports. You would need something like
11965 this to connect more than two modems to your Linux box, for instance
11966 in order to become a dial-in server. If you have a card like that,
11967 say Y here and read the file Documentation/riscom8.txt.
11969 Also it's possible to say M here and compile this driver as kernel
11970 loadable module; the module will be called riscom8.o.
11972 Computone IntelliPort Plus serial support
11974 This driver supports the entire family of Intelliport II/Plus
11975 controllers with the exception of the MicroChannel controllers and
11976 products previous to the Intelliport II. These are multiport cards,
11977 which give you many serial ports. You would need something like
11978 this to connect more than two modems to your Linux box, for
11979 instance in order to become a dial-in server. If you have a
11980 card like that, say Y here and read Documentation/computone.txt.
11982 If you want to compile this as a module ( = code which can be
11983 inserted in and removed from the running kernel whenever you want),
11984 say M here and read Documentation/modules.txt. You will get two
11985 modules called ip2.o and ip2main.o.
11987 Specialix IO8+ card support
11989 This is a driver for the Specialix IO8+ multiport card (both the
11990 ISA and the PCI version) which gives you many serial ports. You
11991 would need something like this to connect more than two modems to
11992 your Linux box, for instance in order to become a dial-in server.
11994 If you have a card like that, say Y here and read the file
11995 Documentation/specialix.txt. Also it's possible to say M here and
11996 compile this driver as kernel loadable module which will be called
11999 Specialix DTR/RTS pin is RTS
12000 CONFIG_SPECIALIX_RTSCTS
12001 The Specialix card can only support either RTS or DTR. If you say N
12002 here, the driver will use the pin as "DTR" when the tty is in
12003 software handshake mode. If you say Y here or hardware handshake is
12004 on, it will always be RTS. Read the file Documentation/specialix.txt
12005 for more information.
12007 Cyclades async mux support
12009 This is a driver for a card that gives you many serial ports. You
12010 would need something like this to connect more than two modems to
12011 your Linux box, for instance in order to become a dial-in server.
12012 For information about the Cyclades-Z card, read
12013 drivers/char/README.cycladesZ.
12015 As of 1.3.9x kernels, this driver's minor numbers start at 0 instead
12018 If you want to compile this as a module ( = code which can be
12019 inserted in and removed from the running kernel whenever you want),
12020 say M here and read Documentation/modules.txt. The module will be
12023 If you haven't heard about it, it's safe to say N.
12025 Cyclades-Z interrupt mode operation (EXPERIMENTAL)
12027 The Cyclades-Z family of multiport cards allows 2 (two) driver op
12028 modes: polling and interrupt. In polling mode, the driver will check
12029 the status of the Cyclades-Z ports every certain amount of time
12030 (which is called polling cycle and is configurable). In interrupt
12031 mode, it will use an interrupt line (IRQ) in order to check the
12032 status of the Cyclades-Z ports. The default op mode is polling. If
12035 Stallion multiport serial support
12037 Stallion cards give you many serial ports. You would need something
12038 like this to connect more than two modems to your Linux box, for
12039 instance in order to become a dial-in server. If you say Y here, you
12040 will be asked for your specific card model in the next questions.
12041 Make sure to read drivers/char/README.stallion in this case. If you
12042 have never heard about all this, it's safe to say N.
12044 Stallion EasyIO or EC8/32 support
12046 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
12047 card, then this is for you; say Y. Make sure to read
12048 Documentation/stallion.txt.
12050 If you want to compile this as a module ( = code which can be
12051 inserted in and removed from the running kernel whenever you want),
12052 say M here and read Documentation/modules.txt. The module will be
12055 Stallion EC8/64, ONboard, Brumby support
12057 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
12058 serial multiport card, say Y here. Make sure to read
12059 Documentation/stallion.txt.
12061 To compile it as a module ( = code which can be inserted in and
12062 removed from the running kernel whenever you want), say M here and
12063 read Documentation/modules.txt. The module will be called
12066 Microgate SyncLink adapter support
12068 Provides support for the SyncLink ISA and PCI
12069 multiprotocol serial adapters. These adapters
12070 support asynchronous and HDLC bit synchronous
12071 communication up to 10Mbps (PCI adapter).
12073 This driver can only be built as a module ( = code which can be
12074 inserted in and removed from the running kernel whenever you want).
12075 The module will be called synclink.o. If you want to do that, say M
12078 Synchronous HDLC line discipline support
12080 Allows synchronous HDLC communications with tty device drivers that
12081 support synchronous HDLC such as the Microgate SyncLink adapter.
12083 This driver can only be built as a module ( = code which can be
12084 inserted in and removed from the running kernel whenever you want).
12085 The module will be called n_hdlc.o. If you want to do that, say M
12088 Specialix SX (and SI) card support
12090 This is a driver for the SX and SI multiport serial cards.
12091 Please read the file Documentation/sx.txt for details.
12093 This driver can only be built as a module ( = code which can be
12094 inserted in and removed from the running kernel whenever you want).
12095 The module will be called sx.o. If you want to do that, say M here.
12097 Hayes ESP serial port support
12099 This is a driver which supports Hayes ESP serial ports. Both single
12100 port cards and multiport cards are supported. Make sure to read
12101 Documentation/hayes-esp.txt.
12103 To compile this driver as a module ( = code which can be inserted in
12104 and removed from the running kernel whenever you want), say M here
12105 and read Documentation/modules.txt. The module will be called esp.o.
12108 Moxa Intellio support
12109 CONFIG_MOXA_INTELLIO
12110 Say Y here if you have a Moxa Intellio multiport serial card.
12112 This driver can also be built as a module ( = code which can be
12113 inserted in and removed from the running kernel whenever you want).
12114 The module will be called moxa.o. If you want to do that, say M
12117 Moxa SmartIO support
12118 CONFIG_MOXA_SMARTIO
12119 Say Y here if you have a Moxa SmartIO multiport serial card.
12121 This driver can also be built as a module ( = code which can be
12122 inserted in and removed from the running kernel whenever you want).
12123 The module will be called mxser.o. If you want to do that, say M
12126 Multi-Tech multiport card support (EXPERIMENTAL)
12128 This is a driver for the Multi-Tech cards which provide several
12129 serial ports. The driver is experimental and can currently only be
12130 built as a module ( = code which can be inserted in and removed from
12131 the running kernel whenever you want). Please read
12132 Documentation/modules.txt. The module will be called isicom.o
12136 A pseudo terminal (PTY) is a software device consisting of two
12137 halves: a master and a slave. The slave device behaves identical to
12138 a physical terminal; the master device is used by a process to
12139 read data from and write data to the slave, thereby emulating a
12140 terminal. Typical programs for the master side are telnet servers
12143 Linux has traditionally used the BSD-like names /dev/ptyxx for
12144 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
12145 has a number of problems. The GNU C library glibc 2.1 and later,
12146 however, supports the Unix98 naming standard: in order to acquire a
12147 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
12148 terminal is then made available to the process and the pseudo
12149 terminal slave can be accessed as /dev/pts/<number>. What was
12150 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
12152 The entries in /dev/pts/ are created on the fly by a virtual
12153 file system; therefore, if you say Y here you should say Y to
12154 "/dev/pts file system for Unix98 PTYs" as well.
12156 If you want to say Y here, you need to have the C library glibc 2.1
12157 or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
12158 Read the instructions in Documentation/Changes pertaining to pseudo
12159 terminals. It's safe to say N.
12161 Maximum number of Unix98 PTYs in use (0-2048)
12162 CONFIG_UNIX98_PTY_COUNT
12163 The maximum number of Unix98 PTYs that can be used at any one time.
12164 The default is 256, and should be enough for desktop systems. Server
12165 machines which support incoming telnet/rlogin/ssh connections and/or
12166 serve several X terminals may want to increase this: every incoming
12167 connection and every xterm uses up one PTY.
12169 When not in use, each additional set of 256 PTYs occupy
12170 approximately 8 KB of kernel memory on 32-bit architectures.
12172 Parallel printer support
12174 If you intend to attach a printer to the parallel port of your Linux
12175 box (as opposed to using a serial printer; if the connector at the
12176 printer has 9 or 25 holes ["female"], then it's serial), say Y. Also
12177 read the Printing-HOWTO, available from
12178 http://www.linuxdoc.org/docs.html#howto .
12180 It is possible to share one parallel port among several devices
12181 (e.g. printer and ZIP drive) and it is safe to compile the
12182 corresponding drivers into the kernel. If you want to compile this
12183 driver as a module however ( = code which can be inserted in and
12184 removed from the running kernel whenever you want), say M here and
12185 read Documentation/modules.txt and Documentation/parport.txt. The
12186 module will be called lp.o.
12188 If you have several parallel ports, you can specify which ports to
12189 use with the "lp" kernel command line option. (Try "man bootparam"
12190 or see the documentation of your boot loader (lilo or loadlin) about
12191 how to pass options to the kernel at boot time.) The syntax of the
12192 "lp" command line option can be found in drivers/char/lp.c.
12194 If you have more than 3 printers, you need to increase the LP_NO
12197 Support for console on line printer
12199 If you want kernel messages to be printed out as they occur, you
12200 can have a console on the printer. This option adds support for
12201 doing that; to actually get it to happen you need to pass the
12202 option "console=lp0" to the kernel at boot time.
12204 Note that kernel messages can get lost if the printer is out of
12205 paper (or off, or unplugged, or too busy..), but this behaviour
12206 can be changed. See drivers/char/lp.c (do this at your own risk).
12210 Support for user-space parallel port device drivers
12212 Saying Y to this adds support for /dev/parport device nodes. This
12213 is needed for programs that want portable access to the parallel
12214 port, for instance deviceid (which displays Plug-and-Play device
12217 This is the parallel port equivalent of SCSI generic support (sg).
12218 It is safe to say N to this -- it is not needed for normal printing
12219 or parallel port CD-ROM/disk support.
12221 This support is also available as a module. If you want to compile
12222 it as a module, say M here and read Documentation/modules.txt. The
12223 module will be called ppdev.o.
12229 I2C (pronounce: I-square-C) is a slow serial bus protocol used in
12230 many micro controller applications and developed by Philips. SMBus,
12231 or System Management Bus is a subset of the I2C protocol. More
12232 information is contained in the directory Documentation/i2c/,
12233 especially in the file called "summary" there.
12235 Both I2C and SMBus are supported here. You will need this for
12236 hardware sensors support, and also for Video for Linux support.
12237 Specifically, if you want to use a BT848 based frame grabber/overlay
12238 boards under Linux, say Y here and also to "I2C bit-banging
12239 interfaces", below.
12241 If you want I2C support, you should say Y here and also to the
12242 specific driver for your bus adapter(s) below. If you say Y to
12243 "/proc file system" below, you will then get a /proc interface which
12244 is documented in Documentation/i2c/proc-interface.
12246 This I2C support is also available as a module. If you want to
12247 compile it as a module, say M here and read
12248 Documentation/modules.txt. The module will be called i2c-core.o.
12250 I2C bit-banging interfaces
12252 This allows you to use a range of I2C adapters called bit-banging
12253 adapters. Say Y if you own an I2C adapter belonging to this class
12254 and then say Y to the specific driver for you adapter below.
12256 This support is also available as a module. If you want to compile
12257 it as a module, say M here and read Documentation/modules.txt. The
12258 module will be called i2c-algo-bit.o.
12260 Philips style parallel port adapter
12261 CONFIG_I2C_PHILIPSPAR
12262 This supports parallel-port I2C adapters made by Philips. Say Y if
12263 you own such an adapter.
12265 This driver is also available as a module. If you want to compile
12266 it as a module, say M here and read Documentation/modules.txt. The
12267 module will be called i2c-philips-par.o.
12269 Note that if you want support for different parallel port devices,
12270 life will be much easier if you compile them all as modules.
12274 This supports parallel-port I2C adapters called ELV. Say Y if you
12275 own such an adapter.
12277 This driver is also available as a module. If you want to compile
12278 it as a module, say M here and read Documentation/modules.txt. The
12279 module will be called i2c-elv.o.
12281 Velleman K9000 adapter
12282 CONFIG_I2C_VELLEMAN
12283 This supports the Velleman K9000 parallel-port I2C adapter. Say Y if
12284 you own such an adapter.
12286 This driver is also available as a module. If you want to compile
12287 it as a module, say M here and read Documentation/modules.txt. The
12288 module will be called i2c-velleman.o.
12290 I2C PCF 8584 interfaces
12292 This allows you to use a range of I2C adapters called PCF adapters.
12293 Say Y if you own an I2C adapter belonging to this class and then say
12294 Y to the specific driver for you adapter below.
12296 This support is also available as a module. If you want to compile
12297 it as a module, say M here and read Documentation/modules.txt. The
12298 module will be called i2c-algo-pcf.o.
12302 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own such
12305 This driver is also available as a module. If you want to compile
12306 it as a module, say M here and read Documentation/modules.txt. The
12307 module will be called i2c-elektor.o.
12309 I2C device interface
12311 Say Y here to use i2c-* device files, usually found in the /dev
12312 directory on your system. They make it possible to have user-space
12313 programs use the I2C bus. Information on how to do this is contained
12314 in the file Documentation/i2c/dev-interface.
12316 This code is also available as a module. If you want to compile
12317 it as a module, say M here and read Documentation/modules.txt. The
12318 module will be called i2c-dev.o.
12322 Say Y here if your machine has a bus mouse as opposed to a serial
12323 mouse. Most people have a regular serial MouseSystem or
12324 Microsoft mouse (made by Logitech) that plugs into a COM port
12325 (rectangular with 9 or 25 pins). These people say N here. If you
12326 have something else, read the Busmouse-HOWTO, available from
12327 http://www.linuxdoc.org/docs.html#howto , and say Y here.
12329 If you have a laptop, you either have to check the documentation or
12330 experiment a bit to find out whether the trackball is a serial mouse
12331 or not; it's best to say Y here for you.
12333 This is the generic bus mouse driver code. If you have a bus mouse,
12334 you will have to say Y here and also to the specific driver for your
12337 This code is also available as a module ( = code which can be
12338 inserted in and removed from the running kernel whenever you want).
12339 The module will be called busmouse.o. If you want to compile it as a
12340 module, say M here and read Documentation/modules.txt.
12342 Mouse Support (not serial and bus mice)
12344 This is for machines with a mouse which is neither a serial nor a
12345 bus mouse. Examples are PS/2 mice (such as the track balls on some
12346 laptops) and some digitizer pads. Most people have a regular serial
12347 MouseSystem or Microsoft mouse (made by Logitech) that plugs into a
12348 COM port (rectangular with 9 or 25 pins). These people say N here.
12349 If you have something else, read the Busmouse-HOWTO, available from
12350 http://www.linuxdoc.org/docs.html#howto . This HOWTO contains
12351 information about all non-serial mice, not just bus mice.
12353 If you have a laptop, you either have to check the documentation or
12354 experiment a bit to find out whether the trackball is a serial mouse
12355 or not; it's best to say Y here for you.
12357 Note that the answer to this question won't directly affect the
12358 kernel: saying N will just cause this configure script to skip all
12359 the questions about non-serial mice. If unsure, say Y.
12361 Logitech busmouse support
12362 CONFIG_LOGIBUSMOUSE
12363 Logitech mouse connected to a proprietary interface card. It's
12364 generally a round connector with 9 pins. Note that the newer mice
12365 made by Logitech don't use the Logitech protocol anymore; for those,
12366 you don't need this option. You want to read the Busmouse-HOWTO ,
12367 available from http://www.linuxdoc.org/docs.html#howto .
12369 If you want to compile this as a module ( = code which can be
12370 inserted in and removed from the running kernel whenever you want),
12371 say M here and read Documentation/modules.txt. The module will be
12372 called busmouse.o. If you are unsure, say N and read the HOWTO
12373 nevertheless: it will tell you what you have.
12375 PS/2 mouse (aka "auxiliary device") support
12377 The PS/2 mouse connects to a special mouse port that looks much like
12378 the keyboard port (small circular connector with 6 pins). This way,
12379 the mouse does not use any serial ports. This port can also be used
12380 for other input devices like light pens, tablets, keypads. Compaq,
12381 AST and IBM all use this as their mouse port on currently shipping
12382 machines. The trackballs of some laptops are PS/2 mice also. In
12383 particular, the C&T 82C710 mouse on TI Travelmates is a PS/2 mouse.
12385 Although PS/2 mice are not technically bus mice, they are explained
12386 in detail in the Busmouse-HOWTO, available from
12387 http://www.linuxdoc.org/docs.html#howto .
12389 When using a PS/2 mouse, you can get problems if you want to use the
12390 mouse both on the Linux console and under X. Using the "-R" option
12391 of the Linux mouse managing program gpm (available from
12392 ftp://metalab.unc.edu/pub/Linux/system/mouse ) solves this
12393 problem, or you can get the "mconv2" utility from the same location.
12395 C&T 82C710 mouse port support (as on TI Travelmate)
12396 CONFIG_82C710_MOUSE
12397 This is a certain kind of PS/2 mouse used on the TI Travelmate. If
12398 you are unsure, try first to say N here and come back if the mouse
12399 doesn't work. Read the Busmouse-HOWTO, available from
12400 http://www.linuxdoc.org/docs.html#howto .
12402 PC110 digitizer pad support
12404 This drives the digitizer pad on the IBM PC110 palmtop. It can turn
12405 the digitizer pad into a PS/2 mouse emulation with tap gestures or
12406 into an absolute pad.
12408 If you want to compile this as a module ( = code which can be
12409 inserted in and removed from the running kernel whenever you want),
12410 say M here and read Documentation/modules.txt. The module will be
12413 Microsoft busmouse support
12415 These animals (also called Inport mice) are connected to an
12416 expansion board using a round connector with 9 pins. If this is what
12417 you have, say Y and read the Busmouse-HOWTO, available from
12418 http://www.linuxdoc.org/docs.html#howto .
12420 If you are unsure, say N and read the HOWTO nevertheless: it will
12421 tell you what you have. Also be aware that several vendors talk
12422 about 'Microsoft busmouse' and actually mean PS/2 busmouse -- so
12423 count the pins on the connector.
12425 If you want to compile this as a module ( = code which can be
12426 inserted in and removed from the running kernel whenever you want),
12427 say M here and read Documentation/modules.txt. The module will be
12428 called msbusmouse.o.
12430 Apple Desktop Bus mouse support
12432 Say Y here if you have this type of bus mouse (4 pin connector) as
12433 is common on Macintoshes. You may want to read the Busmouse-HOWTO,
12434 available from http://www.linuxdoc.org/docs.html#howto .
12436 If you want to compile this as a module ( = code which can be
12437 inserted in and removed from the running kernel whenever you want),
12438 say M here and read Documentation/modules.txt. The module will be
12441 ATIXL busmouse support
12442 CONFIG_ATIXL_BUSMOUSE
12443 This is a rare type of busmouse that is connected to the back of an
12444 ATI video card. Say Y if you have one of those. Note however that
12445 most mice by ATI are actually Microsoft busmice; you should say Y to
12446 "Microsoft busmouse support" above if you have one of those. Read
12447 the Busmouse-HOWTO, available from
12448 http://www.linuxdoc.org/docs.html#howto .
12450 If you want to compile this as a module ( = code which can be
12451 inserted in and removed from the running kernel whenever you want),
12452 say M here and read Documentation/modules.txt. The module will be
12453 called atixlmouse.o.
12455 If you are unsure, say N and read the HOWTO nevertheless: it will
12456 tell you what you have.
12458 QIC-02 tape support
12460 If you have a non-SCSI tape drive like that, say Y. Or, if you want
12461 to compile this driver as a module ( = code which can be inserted in
12462 and removed from the running kernel whenever you want), say M here
12463 and read Documentation/modules.txt. The module will be called
12466 Do you want runtime configuration for QIC-02
12467 CONFIG_QIC02_DYNCONF
12468 You can either configure this driver once and for all by editing a
12469 header file (include/linux/tpqic02.h), in which case you should
12470 say N, or you can fetch a program via anonymous FTP which is able
12471 to configure this driver during runtime. The program to do this is
12472 called 'qic02conf' and it is part of the tpqic02-support-X.Y.tar.gz
12475 If you want to use the qic02conf program, say Y.
12477 Floppy tape drive (QIC-80/40/3010/3020/TR-1/TR-2/TR-3) support
12479 If you have a tape drive that is connected to your floppy
12480 controller, say Y here.
12482 Some tape drives (like the Seagate "Tape Store 3200" or the Iomega
12483 "Ditto 3200" or the Exabyte "Eagle TR-3") come with a "high speed"
12484 controller of their own. These drives (and their companion
12485 controllers) are also supported if you say Y here.
12487 If you have a special controller (such as the CMS FC-10, FC-20,
12488 Mountain Mach-II, or any controller that is based on the Intel 82078
12489 FDC like the high speed controllers by Seagate and Exabyte and
12490 Iomega's "Ditto Dash") you must configure it by selecting the
12491 appropriate entries from the "Floppy tape controllers" sub-menu
12492 below and possibly modify the default values for the IRQ and DMA
12493 channel and the IO base in ftape's configuration menu.
12495 If you want to use your floppy tape drive on a PCI-bus based system,
12496 please read the file drivers/char/ftape/README.PCI.
12498 The ftape kernel driver is also available as a runtime loadable
12499 module ( = code which can be inserted in and removed from the
12500 running kernel whenever you want). If you want to compile it as a
12501 module, say M here and read Documentation/modules.txt. The module
12502 will be called ftape.o.
12504 Note that the Ftape-HOWTO is out of date (sorry) and documents the
12505 older version 2.08 of this software but still contains useful
12506 information. There is a web page with more recent documentation at
12507 http://www.math1.rwth-aachen.de/~heine/ftape/ . This page
12508 always contains the latest release of the ftape driver and useful
12509 information (backup software, ftape related patches and
12510 documentation, FAQ). Note that the file system interface has changed
12511 quite a bit compared to previous versions of ftape. Please read
12512 Documentation/ftape.txt.
12514 The file system interface for ftape
12516 Normally, you want to say Y or M. DON'T say N here or you
12517 WON'T BE ABLE TO USE YOUR FLOPPY TAPE DRIVE.
12519 The ftape module itself no longer contains the routines necessary
12520 to interface with the kernel VFS layer (i.e. to actually write data
12521 to and read data from the tape drive). Instead the file system
12522 interface (i.e. the hardware independent part of the driver) has
12523 been moved to a separate module.
12525 If you say M zftape will be compiled as a runtime loadable
12526 module ( = code which can be inserted in and removed from the
12527 running kernel whenever you want). In this case you should read
12528 Documentation/modules.txt. The module will be called zftape.o.
12530 Regardless of whether you say Y or M here, an additional runtime
12531 loadable module called `zft-compressor.o' which contains code to
12532 support user transparent on-the-fly compression based on Ross
12533 William's lzrw3 algorithm will be produced. If you have enabled the
12534 kernel module loader (i.e. have said Y to "Kernel module loader
12535 support", above) then `zft-compressor.o' will be loaded
12536 automatically by zftape when needed.
12538 Despite its name, zftape does NOT use compression by default. The
12539 file Documentation/ftape.txt contains a short description of the
12540 most important changes in the file system interface compared to
12541 previous versions of ftape. The ftape home page
12542 http://www-math.math.rwth-aachen.de/~LBFM/claus/ftape/ contains
12543 further information.
12545 IMPORTANT NOTE: zftape can read archives created by previous
12546 versions of ftape and provide file mark support (i.e. fast skipping
12547 between tape archives) but previous version of ftape will lack file
12548 mark support when reading archives produced by zftape.
12550 Default block size for zftape
12551 CONFIG_ZFT_DFLT_BLK_SZ
12552 If unsure leave this at its default value, i.e. 10240. Note that
12553 you specify only the default block size here. The block size can be
12554 changed at run time using the MTSETBLK tape operation with the
12555 MTIOCTOP ioctl (i.e. with "mt -f /dev/qft0 setblk #BLKSZ" from the
12556 shell command line).
12558 The probably most striking difference between zftape and previous
12559 versions of ftape is the fact that all data must be written or read
12560 in multiples of a fixed block size. The block size defaults to
12561 10240 which is what GNU tar uses. The values for the block size
12562 should be either 1 or multiples of 1024 up to a maximum value of
12563 63488 (i.e. 62 K). If you specify `1' then zftape's builtin
12564 compression will be disabled.
12566 Reasonable values are `10240' (GNU tar's default block size),
12567 `5120' (afio's default block size), `32768' (default block size some
12568 backup programs assume for SCSI tape drives) or `1' (no restriction
12569 on block size, but disables builtin compression).
12571 Number of DMA buffers
12572 CONFIG_FT_NR_BUFFERS
12573 Please leave this at `3' unless you REALLY know what you are doing.
12574 It is not necessary to change this value. Values below 3 make the
12575 proper use of ftape impossible, values greater than 3 are a waste of
12576 memory. You can change the amount of DMA memory used by ftape at
12577 runtime with "mt -f /dev/qft0 setdrvbuffer #NUMBUFFERS". Each buffer
12578 wastes 32 KB of memory. Please note that this memory cannot be
12581 Procfs entry for ftape
12583 Optional. Saying Y will result in creation of a directory
12584 `/proc/ftape' under the /proc file system. The files can be viewed
12585 with your favorite pager (i.e. use "more /proc/ftape/history" or
12586 "less /proc/ftape/history" or simply "cat /proc/ftape/history"). The
12587 file will contain some status information about the inserted
12588 cartridge, the kernel driver, your tape drive, the floppy disk
12589 controller and the error history for the most recent use of the
12590 kernel driver. Saying Y will enlarge the size of the ftape driver
12591 by approximately 2 KB.
12593 WARNING: When compiling ftape as a module (i.e. saying M to "Floppy
12594 tape drive") it is dangerous to use ftape's /proc file system
12595 interface. Accessing `/proc/ftape' while the module is unloaded will
12596 result in a kernel Oops. This cannot be fixed from inside ftape.
12598 Controlling the amount of debugging output of ftape
12599 CONFIG_FT_NORMAL_DEBUG
12600 This option controls the amount of debugging output the ftape driver
12601 is ABLE to produce; it does not increase or diminish the debugging
12602 level itself. If unsure, leave this at its default setting,
12603 i.e. choose "Normal".
12605 Ftape can print lots of debugging messages to the system console
12606 resp. kernel log files. Reducing the amount of possible debugging
12607 output reduces the size of the kernel module by some KB, so it might
12608 be a good idea to use "None" for emergency boot floppies.
12610 If you want to save memory then the following strategy is
12611 recommended: leave this option at its default setting "Normal" until
12612 you know that the driver works as expected, afterwards reconfigure
12613 the kernel, this time specifying "Reduced" or "None" and recompile
12614 and install the kernel as usual. Note that choosing "Excessive"
12615 debugging output does not increase the amount of debugging output
12616 printed to the console but only makes it possible to produce
12617 "Excessive" debugging output.
12619 Please read Documentation/ftape.txt for a short description
12620 how to control the amount of debugging output.
12622 The floppy drive controller for ftape
12624 Only change this setting if you have a special controller. If you
12625 didn't plug any add-on card into your computer system but just
12626 plugged the floppy tape cable into the already existing floppy drive
12627 controller then you don't want to change the default setting,
12628 i.e. choose "Standard".
12630 Choose "MACH-2" if you have a Mountain Mach-2 controller.
12631 Choose "FC-10/FC-20" if you have a Colorado FC-10 or FC-20
12633 Choose "Alt/82078" if you have another controller that is located at
12634 an IO base address different from the standard floppy drive
12635 controller's base address of `0x3f0', or uses an IRQ (interrupt)
12636 channel different from `6', or a DMA channel different from
12637 `2'. This is necessary for any controller card that is based on
12638 Intel's 82078 FDC such as Seagate's, Exabyte's and Iomega's "high
12639 speed" controllers.
12641 If you choose something other than "Standard" then please make
12642 sure that the settings for the IO base address and the IRQ and DMA
12643 channel in the configuration menus below are correct. Use the manual
12644 of your tape drive to determine the correct settings!
12646 If you are already successfully using your tape drive with another
12647 operating system then you definitely should use the same settings
12648 for the IO base, the IRQ and DMA channel that have proven to work
12649 with that other OS.
12651 Note that this menu lets you specify only the default setting for
12652 the hardware setup. The hardware configuration can be changed at
12653 boot time (when ftape is compiled into the kernel, i.e. if you
12654 have said Y to "Floppy tape drive") or module load time (i.e. if you
12655 have said M to "Floppy tape drive").
12657 Please read also the file Documentation/ftape.txt which
12658 contains a short description of the parameters that can be set at
12659 boot or load time. If you want to use your floppy tape drive on a
12660 PCI-bus based system, please read the file
12661 drivers/char/ftape/README.PCI.
12663 IO base of the floppy disk controller used with Ftape
12665 You don't need to specify a value if the following default
12666 settings for the base IO address are correct:
12667 <<< MACH-2 : 0x1E0 >>>
12668 <<< FC-10/FC-20: 0x180 >>>
12669 <<< Secondary : 0x370 >>>
12670 Secondary refers to a secondary FDC controller like the "high speed"
12671 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
12672 Please make sure that the setting for the IO base address
12673 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
12674 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
12675 successfully using the tape drive with another operating system then
12676 you definitely should use the same settings for the IO base that has
12677 proven to work with that other OS.
12679 Note that this menu lets you specify only the default setting for
12680 the IO base. The hardware configuration can be changed at boot time
12681 (when ftape is compiled into the kernel, i.e. if you specified Y to
12682 "Floppy tape drive") or module load time (i.e. if you have said M to
12683 "Floppy tape drive").
12685 Please read also the file Documentation/ftape.txt which contains a
12686 short description of the parameters that can be set at boot or load
12689 IRQ channel for the floppy disk controller used with Ftape
12691 You don't need to specify a value if the following default
12692 settings for the interrupt channel are correct:
12694 <<< FC-10/FC-20: 9 >>>
12695 <<< Secondary : 6 >>>
12696 Secondary refers to secondary a FDC controller like the "high speed"
12697 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
12698 Please make sure that the setting for the IO base address
12699 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
12700 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
12701 successfully using the tape drive with another operating system then
12702 you definitely should use the same settings for the IO base that has
12703 proven to work with that other OS.
12705 Note that this menu lets you specify only the default setting for
12706 the IRQ channel. The hardware configuration can be changed at boot
12707 time (when ftape is compiled into the kernel, i.e. if you said Y to
12708 "Floppy tape drive") or module load time (i.e. if you said M to
12709 "Floppy tape drive").
12711 Please read also the file Documentation/ftape.txt which contains a
12712 short description of the parameters that can be set at boot or load
12715 DMA channel for the floppy disk controller used with Ftape
12717 You don't need to specify a value if the following default
12718 settings for the DMA channel are correct:
12720 <<< FC-10/FC-20: 3 >>>
12721 <<< Secondary : 2 >>>
12722 Secondary refers to a secondary FDC controller like the "high speed"
12723 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
12724 Please make sure that the setting for the IO base address
12725 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
12726 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
12727 successfully using the tape drive with another operating system then
12728 you definitely should use the same settings for the IO base that has
12729 proven to work with that other OS.
12731 Note that this menu lets you specify only the default setting for
12732 the DMA channel. The hardware configuration can be changed at boot
12733 time (when ftape is compiled into the kernel, i.e. if you said Y to
12734 "Floppy tape drive") or module load time (i.e. if you said M to
12735 "Floppy tape drive").
12737 Please read also the file Documentation/ftape.txt which contains a
12738 short description of the parameters that can be set at boot or load
12741 FDC FIFO Threshold before requesting DMA service
12743 Set the FIFO threshold of the FDC. If this is higher the DMA
12744 controller may serve the FDC after a higher latency time. If this is
12745 lower, fewer DMA transfers occur leading to less bus contention.
12746 You may try to tune this if ftape annoys you with "reduced data
12747 rate because of excessive overrun errors" messages. However, this
12748 doesn't seem to have too much effect.
12750 If unsure, don't touch the initial value, i.e. leave it at "8".
12752 FDC maximum data rate
12753 CONFIG_FT_FDC_MAX_RATE
12754 With some motherboard/FDC combinations ftape will not be able to
12755 run your FDC/tape drive combination at the highest available
12756 speed. If this is the case you'll encounter "reduced data rate
12757 because of excessive overrun errors" messages and lots of retries
12758 before ftape finally decides to reduce the data rate.
12760 In this case it might be desirable to tell ftape beforehand that
12761 it need not try to run the tape drive at the highest available
12762 speed. If unsure, leave this disabled, i.e. leave it at 2000
12765 Direct Rendering Manager (XFree86 DRI support)
12767 Kernel-level support for the Direct Rendering Infrastructure (DRI)
12768 introduced in XFree86 4.0. If you say Y here, you need to select
12769 the module that's right for your graphics card from the list below.
12770 These modules provide support for synchronization, security, and
12771 DMA transfers. Please see http://dri.sourceforge.net for more
12772 details. You should also select and configure AGP
12773 (/dev/agpgart) support.
12775 3dfx Banshee/Voodoo3+
12777 Choose this option if you have a 3dfx Banshee or Voodoo3 (or later),
12778 graphics card. If M is selected, the module will be called tdfx.o.
12782 Choose this option if you have a 3dlabs GMX 2000 graphics card.
12783 If M is selected, the module will be called gamma.o.
12787 Choose this option if you have an ATI Rage 128 graphics card. If M
12788 is selected, the module will be called r128.o. AGP support for
12789 this card is strongly suggested (unless you have a PCI version).
12793 Choose this option if you have an Intel I810 graphics card. If M is
12794 selected, the module will be called i810.o. AGP support is required
12795 for this driver to work.
12799 Choose this option if you have a Matrox g200 or g400 graphics card. If M
12800 is selected, the module will be called mga.o. AGP support is required
12801 for this driver to work.
12803 MTRR control and configuration
12805 On Intel P6 family processors (Pentium Pro, Pentium II and later)
12806 the Memory Type Range Registers (MTRRs) may be used to control
12807 processor access to memory ranges. This is most useful if you have
12808 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
12809 allows bus write transfers to be combined into a larger transfer
12810 before bursting over the PCI/AGP bus. This can increase performance
12811 of image write operations 2.5 times or more. Saying Y here creates a
12812 /proc/mtrr file which may be used to manipulate your processor's
12813 MTRRs. Typically the X server should use this.
12815 This code has a reasonably generic interface so that similar
12816 control registers on other processors can be easily supported
12819 The Cyrix 6x86, 6x86MX and M II processors have Address Range
12820 Registers (ARRs) which provide a similar functionality to MTRRs. For
12821 these, the ARRs are used to emulate the MTRRs.
12822 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
12823 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
12824 write-combining. All of these processors are supported by this code
12825 and it makes sense to say Y here if you have one of them.
12827 Saying Y here also fixes a problem with buggy SMP BIOSes which only
12828 set the MTRRs for the boot CPU and not for the secondary CPUs. This
12829 can lead to all sorts of problems, so it's good to say Y here.
12831 You can safely say Y even if your machine doesn't have MTRRs, you'll
12832 just add about 9 KB to your kernel.
12834 See Documentation/mtrr.txt for more information.
12836 Main CPU frequency, only for DEC alpha machine
12837 CONFIG_FT_ALPHA_CLOCK
12838 On some DEC Alpha machines the CPU clock frequency cannot be
12839 determined automatically, so you need to specify it here ONLY if
12840 running a DEC Alpha, otherwise this setting has no effect.
12842 Double Talk PC internal speech card support
12844 This driver is for the DoubleTalk PC, a speech synthesizer
12845 manufactured by RC Systems (http://www.rcsys.com/ ). It is also
12846 called the `internal DoubleTalk'. If you want to compile this as a
12847 module ( = code which can be inserted in and removed from the
12848 running kernel whenever you want), say M here and read
12849 Documentation/modules.txt. The module will be called dtlk.o.
12851 Siemens R3964 serial protocol support
12853 This driver allows synchronous communication with devices using the
12854 Siemens R3964 packet protocol. Unless you are dealing with special
12855 hardware like PLCs, you are unlikely to need this.
12857 To compile this driver as a module ( = code which can be inserted in
12858 and removed from the running kernel whenever you want), say M here
12859 and read Documentation/modules.txt. The module will be called
12864 Applicom intelligent fieldbus card support
12866 This driver provides the kernel-side support for the intelligent
12867 fieldbus cards made by Applicom International. More information
12868 about these cards can be found on the WWW at the address
12869 http://www.applicom-int.com/ , or by email from David Woodhouse
12870 <dwmw2@infradead.org>.
12872 To compile this driver as a module ( = code which can be inserted in
12873 and removed from the running kernel whenever you want), say M here
12874 and read Documentation/modules.txt. The module will be called
12879 Intel Random Number Generator support
12881 This driver provides kernel-side support for the Random Number
12882 Generator hardware found on Intel i8xx-based motherboards.
12884 Both a character driver, used to read() entropy data, and a timer
12885 function which automatically adds entropy directly into the
12886 kernel pool, are exported by this driver.
12888 To compile this driver as a module ( = code which can be inserted in
12889 and removed from the running kernel whenever you want), say M here
12890 and read Documentation/modules.txt. The module will be called
12895 Power Management support
12897 "Power Management" means that parts of your computer are shut
12898 off or put into a power conserving "sleep" mode if they are not
12899 being used. There are two competing standards for doing this: APM
12900 and ACPI. If you want to use either one, say Y here and then also to
12901 the requisite support below.
12903 Power Management is most important for battery powered laptop
12904 computers; if you have a laptop, check out the Linux Laptop home
12906 http://www.cs.utexas.edu/users/kharker/linux-laptop/ and the Battery
12907 Powered Linux mini-HOWTO, available from
12908 http://www.linuxdoc.org/docs.html#howto .
12910 Note that, even if you say N here, Linux on the x86 architecture
12911 will issue the hlt instruction if nothing is to be done, thereby
12912 sending the processor to sleep and saving power.
12916 The Advanced Configuration and Power Interface is a standard
12917 designed to allow the operating system more control over power
12918 management issues, such as suspending a computer in a low power
12919 consumption state after a certain time of inaction. It aims to be
12920 an improved version of APM (see below). ACPI has to be
12921 supported by the motherboard. You can read more about the standard
12922 at http://www.teleport.com/~acpi/ .
12924 If your computer supports ACPI and you want to use it, say Y here.
12925 You will then need supporting software; for location and more
12926 information, please read Documentation/pm.txt and the Battery
12927 Powered Linux mini-HOWTO, available from
12928 http://www.linuxdoc.org/docs.html#howto .
12930 If you say Y here and also to "Advanced Power Management" (APM)
12931 below, then ACPI has precedence in the sense that, if your hardware
12932 supports ACPI, it will be used and APM won't.
12934 ACPI interpreter (EXPERIMENTAL)
12935 CONFIG_ACPI_INTERPRETER
12936 If you say Y here, an ACPI interpreter will be included in your
12937 kernel, eventually making the full range of ACPI features
12938 available on systems that support ACPI. Note, this option will
12939 enlarge your kernel by about 120K.
12941 The interpreter is currently experimental so only say Y if
12942 you know what you are doing.
12944 Enter S1 for sleep (EXPERIMENTAL)
12945 CONFIG_ACPI_S1_SLEEP
12946 If you say Y here, ACPI compliant devices can enter level 1 of ACPI
12947 saving power levels. Basically, this will let them enter sleep mode.
12949 Advanced Power Management BIOS support
12951 APM is a BIOS specification for saving power using several different
12952 techniques. This is mostly useful for battery powered laptops with
12953 APM compliant BIOSes. If you say Y here, the system time will be
12954 reset after a RESUME operation, the /proc/apm device will provide
12955 battery status information, and user-space programs will receive
12956 notification of APM "events" (e.g. battery status change).
12958 If you select "Y" here, you can disable actual use of the APM
12959 BIOS by passing the "apm=off" option to the kernel at boot time.
12961 Note that the APM support is almost completely disabled for
12962 machines with more than one CPU.
12964 In order to use APM, you will need supporting software. For location
12965 and more information, read Documentation/pm.txt and the Battery
12966 Powered Linux mini-HOWTO, available from
12967 http://www.linuxdoc.org/docs.html#howto .
12969 This driver does not spin down disk drives (see the hdparm(8)
12970 manpage ("man 8 hdparm") for that), and it doesn't turn off
12971 VESA-compliant "green" monitors.
12973 This driver does not support the TI 4000M TravelMate and the ACER
12974 486/DX4/75 because they don't have compliant BIOSes. Many "green"
12975 desktop machines also don't have compliant BIOSes, and this driver
12976 may cause those machines to panic during the boot phase.
12978 Generally, if you don't have a battery in your machine, there isn't
12979 much point in using this driver and you should say N. If you get
12980 random kernel OOPSes or reboots that don't seem to be related to
12981 anything, try disabling/enabling this option (or disabling/enabling
12984 Some other things you should try when experiencing seemingly random,
12987 1) make sure that you have enough swap space and that it is
12989 2) pass the "no-hlt" option to the kernel
12990 3) switch on floating point emulation in the kernel and pass
12991 the "no387" option to the kernel
12992 4) pass the "floppy=nodma" option to the kernel
12993 5) pass the "mem=4M" option to the kernel (thereby disabling
12994 all but the first 4 MB of RAM)
12995 6) make sure that the CPU is not over clocked.
12996 7) read the sig11 FAQ at http://www.bitwizard.nl/sig11/
12997 8) disable the cache from your BIOS settings
12998 9) install a fan for the video card or exchange video RAM
12999 10) install a better fan for the CPU
13000 11) exchange RAM chips
13001 12) exchange the motherboard.
13003 To compile this driver as a module ( = code which can be inserted in
13004 and removed from the running kernel whenever you want), say M here
13005 and read Documentation/modules.txt. The module will be called
13008 Ignore USER SUSPEND
13009 CONFIG_APM_IGNORE_USER_SUSPEND
13010 This option will ignore USER SUSPEND requests. On machines with a
13011 compliant APM BIOS, you want to say N. However, on the NEC Versa M
13012 series notebooks, it is necessary to say Y because of a BIOS bug.
13014 Enable APM at boot time
13015 CONFIG_APM_DO_ENABLE
13016 Enable APM features at boot time. From page 36 of the APM BIOS
13017 specification: "When disabled, the APM BIOS does not automatically
13018 power manage devices, enter the Standby State, enter the Suspend
13019 State, or take power saving steps in response to CPU Idle calls."
13020 This driver will make CPU Idle calls when Linux is idle (unless this
13021 feature is turned off -- see "Do CPU IDLE calls", below). This
13022 should always save battery power, but more complicated APM features
13023 will be dependent on your BIOS implementation. You may need to turn
13024 this option off if your computer hangs at boot time when using APM
13025 support, or if it beeps continuously instead of suspending. Turn
13026 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
13027 T400CDT. This is off by default since most machines do fine without
13031 CONFIG_APM_CPU_IDLE
13032 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
13033 On some machines, this can activate improved power savings, such as
13034 a slowed CPU clock rate, when the machine is idle. These idle calls
13035 are made after the idle loop has run for some length of time (e.g.,
13036 333 mS). On some machines, this will cause a hang at boot time or
13037 whenever the CPU becomes idle. (On machines with more than one CPU,
13038 this option does nothing.)
13040 Enable console blanking using APM
13041 CONFIG_APM_DISPLAY_BLANK
13042 Enable console blanking using the APM. Some laptops can use this to
13043 turn off the LCD backlight when the screen blanker of the Linux
13044 virtual console blanks the screen. Note that this is only used by
13045 the virtual console screen blanker, and won't turn off the backlight
13046 when using the X Window system. This also doesn't have anything to
13047 do with your VESA-compliant power-saving monitor. Further, this
13048 option doesn't work for all laptops -- it might not turn off your
13049 backlight at all, or it might print a lot of errors to the console,
13050 especially if you are using gpm.
13052 RTC stores time in GMT
13053 CONFIG_APM_RTC_IS_GMT
13054 Say Y here if your RTC (Real Time Clock a.k.a. hardware clock)
13055 stores the time in GMT (Greenwich Mean Time). Say N if your RTC
13058 It is in fact recommended to store GMT in your RTC, because then you
13059 don't have to worry about daylight savings time changes. The only
13060 reason not to use GMT in your RTC is if you also run a broken OS
13061 that doesn't understand GMT.
13063 Allow interrupts during APM BIOS calls
13064 CONFIG_APM_ALLOW_INTS
13065 Normally we disable external interrupts while we are making calls to
13066 the APM BIOS as a measure to lessen the effects of a badly behaving
13067 BIOS implementation. The BIOS should reenable interrupts if it
13068 needs to. Unfortunately, some BIOSes do not -- especially those in
13069 many of the newer IBM Thinkpads. If you experience hangs when you
13070 suspend, try setting this to Y. Otherwise, say N.
13072 Use real mode APM BIOS call to power off
13073 CONFIG_APM_REAL_MODE_POWER_OFF
13074 Use real mode APM BIOS calls to switch off the computer. This is
13075 a work-around for a number of buggy BIOSes. Switch this option on if
13076 your computer crashes instead of powering off properly.
13078 Watchdog Timer Support
13080 If you say Y here (and to one of the following options) and create a
13081 character special file /dev/watchdog with major number 10 and minor
13082 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
13083 subsequently opening the file and then failing to write to it for
13084 longer than 1 minute will result in rebooting the machine. This
13085 could be useful for a networked machine that needs to come back
13086 online as fast as possible after a lock-up. There's both a watchdog
13087 implementation entirely in software (which can sometimes fail to
13088 reboot the machine) and a driver for hardware watchdog boards, which
13089 are more robust and can also keep track of the temperature inside
13090 your computer. For details, read Documentation/watchdog.txt in the
13093 The watchdog is usually used together with the watchdog daemon
13094 which is available via FTP (user: anonymous) from
13095 ftp://tsx-11.mit.edu/pub/linux/sources/sbin/ . This daemon can also
13096 monitor NFS connections and can reboot the machine when the process
13101 Disable watchdog shutdown on close
13102 CONFIG_WATCHDOG_NOWAYOUT
13103 The default watchdog behaviour (which you get if you say N here) is
13104 to stop the timer if the process managing it closes the file
13105 /dev/watchdog. It's always remotely possible that this process might
13106 get killed. If you say Y here, the watchdog cannot be stopped once
13107 it has been started.
13111 If you have a WDT500P or WDT501P watchdog board, say Y here,
13112 otherwise N. It is not possible to probe for this board, which means
13113 that you have to inform the kernel about the IO port and IRQ using
13114 the "wdt=" kernel option (try "man bootparam" or see the
13115 documentation of your boot loader (lilo or loadlin) about how to
13116 pass options to the kernel at boot time).
13118 If you want to compile this as a module ( = code which can be
13119 inserted in and removed from the running kernel whenever you want),
13120 say M here and read Documentation/modules.txt. The module will be
13123 WDT PCI Watchdog timer
13125 If you have a PCI WDT500/501 watchdog board, say Y here,
13126 otherwise N. It is not possible to probe for this board, which means
13127 that you have to inform the kernel about the IO port and IRQ using
13128 the "wdt=" kernel option (try "man bootparam" or see the
13129 documentation of your boot loader (lilo or loadlin) about how to
13130 pass options to the kernel at boot time).
13132 If you want to compile this as a module ( = code which can be
13133 inserted in and removed from the running kernel whenever you want),
13134 say M here and read Documentation/modules.txt. The module will be
13139 Saying Y here and creating a character special file /dev/temperature
13140 with major number 10 and minor number 131 ("man mknod") will give
13141 you a thermometer inside your computer: reading from
13142 /dev/temperature yields one byte, the temperature in degrees
13143 Fahrenheit. This works only if you have a WDT501P watchdog board
13148 Enable the Fan Tachometer on the WDT501. Only do this if you have a
13149 fan tachometer actually set up.
13152 CONFIG_SOFT_WATCHDOG
13153 A software monitoring watchdog. This will fail to reboot your system
13154 from some situations that the hardware watchdog will recover
13155 from. Equally it's a lot cheaper to install.
13157 This driver is also available as a module ( = code which can be
13158 inserted in and removed from the running kernel whenever you want).
13159 If you want to compile it as a module, say M here and read
13160 Documentation/modules.txt. The module will be called softdog.o.
13162 Berkshire Products PC Watchdog
13164 This is the driver for the Berkshire Products PC Watchdog card.
13165 This card simply watches your kernel to make sure it doesn't freeze,
13166 and if it does, it reboots your computer after a certain amount of
13167 time. This driver is like the WDT501 driver but for different
13168 hardware. Please read Documentation/pcwd-watchdog.txt. The PC
13169 watchdog cards can be ordered from http://www.berkprod.com .
13171 This driver is also available as a module ( = code which can be
13172 inserted in and removed from the running kernel whenever you want).
13173 The module is called pcwd.o. If you want to compile it as a module,
13174 say M here and read Documentation/modules.txt.
13176 Most people will say N.
13178 Acquire SBC Watchdog Timer
13180 This is the driver for the hardware watchdog on the PSC-6x86 Single
13181 Board Computer produced by Acquire Inc (and others). This watchdog
13182 simply watches your kernel to make sure it doesn't freeze, and if
13183 it does, it reboots your computer after a certain amount of time.
13185 This driver is like the WDT501 driver but for different hardware.
13186 This driver is also available as a module ( = code which can be
13187 inserted in and removed from the running kernel whenever you want).
13188 The module is called pscwdt.o. If you want to compile it as a
13189 module, say M here and read Documentation/modules.txt. Most people
13194 This is a driver for the Mixcom hardware watchdog cards. This
13195 watchdog simply watches your kernel to make sure it doesn't freeze,
13196 and if it does, it reboots your computer after a certain amount of
13199 This driver is also available as a module ( = code which can be
13200 inserted in and removed from the running kernel whenever you want).
13201 The module is called mixcomwd.o. If you want to compile it as a
13202 module, say M here and read Documentation/modules.txt. Most people
13205 /dev/cpu/microcode - Intel P6 CPU microcode support
13207 If you say Y here and also to "/dev file system support" in the
13208 'File systems' section, you will be able to update the microcode on
13209 Intel processors in the P6 family, e.g. Pentium Pro, Pentium II,
13210 Pentium III, Xeon etc. You will obviously need the actual microcode
13211 binary data itself which is not shipped with the Linux kernel.
13213 For latest news and information on obtaining all the required
13214 ingredients for this driver, check:
13215 http://www.urbanmyth.org/microcode/
13217 This driver is also available as a module ( = code which can be
13218 inserted in and removed from the running kernel whenever you want).
13219 The module will be called microcode.o. If you want to compile it as
13220 a module, say M here and read Documentation/modules.txt.
13222 /dev/cpu/*/msr - Model-specific register support
13224 This device gives privileged processes access to the x86
13225 Model-Specific Registers (MSRs). It is a character device with
13226 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
13227 MSR accesses are directed to a specific CPU on multi-processor
13230 /dev/cpu/*/cpuid - CPU information support
13232 This device gives processes access to the x86 CPUID instruction to
13233 be executed on a specific processor. It is a character device
13234 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
13237 Enhanced Real Time Clock Support
13239 If you say Y here and create a character special file /dev/rtc with
13240 major number 10 and minor number 135 using mknod ("man mknod"), you
13241 will get access to the real time clock (or hardware clock) built
13242 into your computer.
13244 Every PC has such a clock built in. It can be used to generate
13245 signals from as low as 1Hz up to 8192Hz, and can also be used
13246 as a 24 hour alarm. It reports status information via the file
13247 /proc/driver/rtc and its behaviour is set by various ioctls on
13250 If you run Linux on a multiprocessor machine and said Y to
13251 "Symmetric Multi Processing" above, you should say Y here to read
13252 and set the RTC in an SMP compatible fashion.
13254 If you think you have a use for such a device (such as periodic data
13255 sampling), then say Y here, and read Documentation/rtc.txt for
13258 This driver is also available as a module ( = code which can be
13259 inserted in and removed from the running kernel whenever you want).
13260 The module is called rtc.o. If you want to compile it as a module,
13261 say M here and read Documentation/modules.txt.
13264 #EFI Real Time Clock Services
13267 Tadpole ANA H8 Support
13269 The Hitachi H8/337 is a microcontroller used to deal with the power
13270 and thermal environment. If you say Y here, you will be able to
13271 communicate with it via a character special device.
13277 If you say Y here and create a character special file /dev/nvram
13278 with major number 10 and minor number 144 using mknod ("man mknod"),
13279 you get read and write access to the 50 bytes of non-volatile memory
13280 in the real time clock (RTC), which is contained in every PC and
13283 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
13284 on Ataris. /dev/nvram may be used to view settings there, or to
13285 change them (with some utility). It could also be used to frequently
13286 save a few bits of very important data that may not be lost over
13287 power-off and for which writing to disk is too insecure. Note
13288 however that most NVRAM space in a PC belongs to the BIOS and you
13289 should NEVER idly tamper with it. See Ralf Brown's interrupt list
13290 for a guide to the use of CMOS bytes by your BIOS.
13292 On Atari machines, /dev/nvram is always configured and does not need
13295 This driver is also available as a module ( = code which can be
13296 inserted in and removed from the running kernel whenever you want).
13297 The module will be called nvram.o. If you want to compile it as a
13298 module, say M here and read Documentation/modules.txt.
13302 If you have a joystick, 6dof controller, gamepad, steering wheel,
13303 weapon control system or something like that you can say Y here to
13304 enable generic support for these controllers. You will also need to
13305 say Y or M to at least one of the hardware specific drivers. This
13306 will make the controllers available as /dev/input/jsX devices.
13307 Please read the file Documentation/joystick.txt which contains more
13308 information and the location of the joystick package that you'll
13313 Say Y here if you have an ISA, ISAPnP or PCI standard gameport.
13314 For more information on how to use the driver please read
13315 Documentation/joystick.txt
13317 This driver is also available as a module ( = code which can be
13318 inserted in and removed from the running kernel whenever you want).
13319 The module will be called ns558.o. If you want to compile
13320 it as a module, say M here and read Documentation/modules.txt.
13322 PDPI Lightning 4 gamecard
13323 CONFIG_INPUT_LIGHTNING
13324 Say Y here if you have a PDPI Lightning 4 gamecard. For more
13325 information on how to use the driver please read
13326 Documentation/joystick.txt
13328 This driver is also available as a module ( = code which can be
13329 inserted in and removed from the running kernel whenever you want).
13330 The module will be called lightning.o. If you want to compile
13331 it as a module, say M here and read Documentation/modules.txt.
13333 Aureal Vortex and Trident 4DWave gameports
13334 CONFIG_INPUT_PCIGAME
13335 Say Y here if you have a Trident 4DWave DX/NX or Aureal Vortex 1/2
13336 card. For more information on how to use the driver please read
13337 Documentation/joystick.txt
13339 This driver is also available as a module ( = code which can be
13340 inserted in and removed from the running kernel whenever you want).
13341 The module will be called pcigame.o. If you want to compile
13342 it as a module, say M here and read Documentation/modules.txt.
13344 Classic PC analog joysticks and gamepads
13345 CONFIG_INPUT_ANALOG
13346 Say Y here if you have a controller that connects to the PC
13347 gameport. This supports many different types, including joysticks
13348 with throttle control, with rudders, or with extensions like
13349 additional hats and buttons compatible with CH Flightstick Pro,
13350 ThrustMaster FCS, 6 and 8 button gamepads, or Saitek Cyborg
13351 joysticks. For more information on how to use the driver please read
13352 Documentation/joystick.txt
13354 This driver is also available as a module ( = code which can be
13355 inserted in and removed from the running kernel whenever you want).
13356 The module will be called analog.o. If you want to compile
13357 it as a module, say M here and read Documentation/modules.txt.
13359 Assasin 3D and MadCatz Panther devices
13361 Say Y here if you have an FPGaming or MadCatz controller using the
13362 A3D protocol over the PC gameport. For more information on how to
13363 use the driver please read Documentation/joystick.txt
13365 This driver is also available as a module ( = code which can be
13366 inserted in and removed from the running kernel whenever you want).
13367 The module will be called a3d.o. If you want to compile
13368 it as a module, say M here and read Documentation/modules.txt.
13370 Logitech ADI digital joysticks and gamepads
13372 Say Y here if you have a Logitech controller using the ADI
13373 protocol over the PC gameport. For more information on how to use
13374 the driver please read Documentation/joystick.txt
13376 This driver is also available as a module ( = code which can be
13377 inserted in and removed from the running kernel whenever you want).
13378 The module will be called adi.o. If you want to compile
13379 it as a module, say M here and read Documentation/modules.txt.
13381 Creative Labs Blaster Cobra gamepad
13383 Say Y here if you have a Creative Labs Blaster Cobra gamepad.
13384 For more information on how to use the driver please read
13385 Documentation/joystick.txt
13387 This driver is also available as a module ( = code which can be
13388 inserted in and removed from the running kernel whenever you want).
13389 The module will be called cobra.o. If you want to compile
13390 it as a module, say M here and read Documentation/modules.txt.
13392 Genius Flight2000 Digital joysticks and gamepads
13394 Say Y here if you have a Genius Flight2000 or MaxFighter
13395 digitally communicating joystick or gamepad. For more information
13396 on how to use the driver please read Documentation/joystick.txt
13398 This driver is also available as a module ( = code which can be
13399 inserted in and removed from the running kernel whenever you want).
13400 The module will be called gf2k.o. If you want to compile
13401 it as a module, say M here and read Documentation/modules.txt.
13403 Gravis GrIP joysticks and gamepads
13405 Say Y here if you have a Gravis controller using the GrIP protocol
13406 over the PC gameport. For more information on how to use the driver
13407 please read Documentation/joystick.txt
13409 This driver is also available as a module ( = code which can be
13410 inserted in and removed from the running kernel whenever you want).
13411 The module will be called grip.o. If you want to compile
13412 it as a module, say M here and read Documentation/modules.txt.
13414 InterAct digital joysticks and gamepads
13415 CONFIG_INPUT_INTERACT
13416 Say Y hereif you have an InterAct gameport or joystick
13417 communicating digitally over the gameport. For more information on
13418 how to use the driver please read Documentation/joystick.txt
13420 This driver is also available as a module ( = code which can be
13421 inserted in and removed from the running kernel whenever you want).
13422 The module will be called interact.o. If you want to compile
13423 it as a module, say M here and read Documentation/modules.txt.
13425 ThrustMaster DirectConnect joysticks and gamepads
13427 Say Y here if you have a ThrustMaster controller using the
13428 DirectConnect (BSP) protocol over the PC gameport. For more
13429 information on how to use the driver please read
13430 Documentation/joystick.txt
13432 This driver is also available as a module ( = code which can be
13433 inserted in and removed from the running kernel whenever you want).
13434 The module will be called tmdc.o. If you want to compile
13435 it as a module, say M here and read Documentation/modules.txt.
13437 Microsoft SideWinder digital joysticks and gamepads
13438 CONFIG_INPUT_SIDEWINDER
13439 Say Y here if you have a Microsoft controller using the Digital
13440 Overdrive protocol over PC gameport. For more information on how to
13441 use the driver please read Documentation/joystick.txt
13443 This driver is also available as a module ( = code which can be
13444 inserted in and removed from the running kernel whenever you want).
13445 The module will be called sidewinder.o. If you want to compile
13446 it as a module, say M here and read Documentation/modules.txt.
13448 Serial port input line discipline
13449 CONFIG_INPUT_SERPORT
13450 Say Y hereif you plan to use a joystick that communicates over the
13451 serial (COM) port. For more information on how to use the driver
13452 please read Documentation/joystick.txt
13454 This driver is also available as a module ( = code which can be
13455 inserted in and removed from the running kernel whenever you want).
13456 The module will be called serport.o. If you want to compile
13457 it as a module, say M here and read Documentation/modules.txt.
13459 Logitech WingMan Warrior joystick
13460 CONFIG_INPUT_WARRIOR
13461 Say Y here if you have a Logitech WingMan Warrior joystick
13462 connected to your computer's serial port. For more information on
13463 how to use the driver please read Documentation/joystick.txt
13465 This driver is also available as a module ( = code which can be
13466 inserted in and removed from the running kernel whenever you want).
13467 The module will be called warrior.o. If you want to compile
13468 it as a module, say M here and read Documentation/modules.txt.
13470 LogiCad3d Magellan/SpaceMouse 6dof controller
13471 CONFIG_INPUT_MAGELLAN
13472 Say Y here if you have a Magellan or Space Mouse 6DOF controller
13473 connected to your computer's serial port. For more information on
13474 how to use the driver please read Documentation/joystick.txt
13476 This driver is also available as a module ( = code which can be
13477 inserted in and removed from the running kernel whenever you want).
13478 The module will be called magellan.o. If you want to compile
13479 it as a module, say M here and read Documentation/modules.txt.
13481 SpaceTec SpaceOrb/Avenger 6dof controller
13482 CONFIG_INPUT_SPACEORB
13483 Say Y here if you have a SpaceOrb 360 or SpaceBall Avenger 6DOF
13484 controller connected to your computer's serial port. For more
13485 information on how to use the driver please read
13486 Documentation/joystick.txt
13488 This driver is also available as a module ( = code which can be
13489 inserted in and removed from the running kernel whenever you want).
13490 The module will be called spaceorb.o. If you want to compile
13491 it as a module, say M here and read Documentation/modules.txt.
13493 SpaceTec SpaceBall 4000 FLX 6dof controller
13494 CONFIG_INPUT_SPACEBALL
13495 Say Y here if you have a SpaceTec SpaceBall 4000 FLX controller
13496 connected to your computer's serial port. For more information on
13497 how to use the driver please read Documentation/joystick.txt
13499 I-Force joysticks/wheels
13500 CONFIG_INPUT_IFORCE_232
13501 Say Y here if you have an I-Force joystick or steering wheel
13502 connected to your serial (COM) port. For more information on
13503 how to use the driver please read Documentation/joystick.txt
13505 This driver is also available as a module ( = code which can be
13506 inserted in and removed from the running kernel whenever you want).
13507 The module will be called iforce.o. If you want to compile
13508 it as a module, say M here and read Documentation/modules.txt.
13510 I-Force joysticks/wheels
13511 CONFIG_INPUT_IFORCE_USB
13512 Say Y here if you have an I-Force joystick or steering wheel
13513 connected to your USB port. For more information on how to use the
13514 driver please read Documentation/joystick.txt
13516 This driver is also available as a module ( = code which can be
13517 inserted in and removed from the running kernel whenever you want).
13518 The module will be called iforce.o. If you want to compile
13519 it as a module, say M here and read Documentation/modules.txt.
13521 Multisystem, Sega Genesis, Saturn joysticks and gamepads
13523 Say Y here if you have a Sega Master System gamepad, Sega Genesis
13524 gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga,
13525 Commodore, Amstrad CPC joystick connected to your parallel port.
13526 For more information on how to use the driver please read
13527 Documentation/joystick.txt and Documentation/joystick-parport.txt.
13529 This driver is also available as a module ( = code which can be
13530 inserted in and removed from the running kernel whenever you want).
13531 The module will be called db9.o. If you want to compile
13532 it as a module, say M here and read Documentation/modules.txt.
13534 Multisystem, NES, SNES, N64, PSX joysticks and gamepads
13535 CONFIG_INPUT_GAMECON
13536 Say Y here if you have a Nintendo Entertainment System gamepad,
13537 Super Nintendo Entertainment System gamepad, Nintendo 64 gamepad,
13538 Sony PlayStation gamepad or a Multisystem -- Atari, Amiga,
13539 Commodore, Amstrad CPC joystick connected to your parallel port.
13540 For more information on how to use the driver please read
13541 Documentation/joystick.txt and Documentation/joystick-parport.txt
13543 This driver is also available as a module ( = code which can be
13544 inserted in and removed from the running kernel whenever you want).
13545 The module will be called gamecon.o. If you want to compile
13546 it as a module, say M here and read Documentation/modules.txt.
13548 Multisystem joysticks via TurboGraFX device
13549 CONFIG_INPUT_TURBOGRAFX
13550 Say Y here if you have the TurboGraFX interface by Steffen
13551 Schwenke, and want to use it with Multiststem -- Atari, Amiga,
13552 Commodore, Amstrad CPC joystick. For more information on how to use
13553 the driver please read Documentation/joystick.txt and
13554 Documentation/joystick-parport.txt
13556 This driver is also available as a module ( = code which can be
13557 inserted in and removed from the running kernel whenever you want).
13558 The module will be called turbografx.o. If you want to compile
13559 it as a module, say M here and read Documentation/modules.txt.
13562 CONFIG_INPUT_AMIJOY
13563 Say Y here if you have an Amiga with a digital joystick connected
13564 to it. For more information on how to use the driver please read
13565 Documentation/joystick.txt
13567 This driver is also available as a module ( = code which can be
13568 inserted in and removed from the running kernel whenever you want).
13569 The module will be called joy-amiga.o. If you want to compile
13570 it as a module, say M here and read Documentation/modules.txt.
13572 Atomwide Serial Support
13573 CONFIG_ATOMWIDE_SERIAL
13574 If you have an Atomwide Serial card for an Acorn system, say Y to
13575 this option. The driver can handle 1, 2, or 3 port cards.
13578 The Serial Port Dual Serial Port
13579 CONFIG_DUALSP_SERIAL
13580 If you have the Serial Port's dual serial card for an Acorn system,
13581 say Y to this option. If unsure, say N
13585 If you say Y here and create a character device node /dev/nwbutton
13586 with major and minor numbers 10 and 158 ("man mknod"), then every
13587 time the orange button is pressed a number of times, the number of
13588 times the button was pressed will be written to that device.
13590 This is most useful for applications, as yet unwritten, which
13591 perform actions based on how many times the button is pressed in a
13594 Do not hold the button down for too long, as the driver does not
13595 alter the behaviour of the hardware reset circuitry attached to the
13596 button; it will still execute a hard reset if the button is held
13597 down for longer than approximately five seconds.
13599 This driver is also available as a module ( = code which can be
13600 inserted in and removed from the running kernel whenever you want).
13601 If you want to compile it as a module, say M here and read
13602 Documentation/modules.txt. The module will be called nwbutton.o.
13604 Most people will answer Y to this question and "Reboot Using Button"
13605 below to be able to initiate a system shutdown from the button.
13607 Reboot Using Button
13608 CONFIG_NWBUTTON_REBOOT
13609 If you say Y here, then you will be able to initiate a system
13610 shutdown and reboot by pressing the orange button a number of times.
13611 The number of presses to initiate the shutdown is two by default,
13612 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
13613 in nwbutton.h and recompiling the driver or, if you compile the
13614 driver as a module, you can specify the number of presses at load
13615 time with "insmod button reboot_count=<something>".
13619 If you have a sound card in your computer, i.e. if it can say more
13620 than an occasional beep, say Y. Be sure to have all the information
13621 about your sound card and its configuration down (I/O port,
13622 interrupt and DMA channel), because you will be asked for it.
13624 You want to read the Sound-HOWTO, available from
13625 http://www.linuxdoc.org/docs.html#howto . General information
13626 about the modular sound system is contained in the files
13627 Documentation/sound/Introduction. The file
13628 Documentation/sound/README.OSS contains some slightly outdated but
13629 still useful information as well.
13631 If you have a PnP sound card and you want to configure it at boot
13632 time using the ISA PnP tools (read
13633 http://www.roestock.demon.co.uk/isapnptools/ ), then you need to
13634 compile the sound card support as a module ( = code which can be
13635 inserted in and removed from the running kernel whenever you want)
13636 and load that module after the PnP configuration is finished. To do
13637 this, say M here and read Documentation/modules.txt as well as
13638 Documentation/sound/README.modules; the module will be called
13641 I'm told that even without a sound card, you can make your computer
13642 say more than an occasional beep, by programming the PC speaker.
13643 Kernel patches and supporting utilities to do that are in the pcsp
13644 package, available at ftp://ftp.infradead.org/pub/pcsp/ .
13648 OSS is the Open Sound System suite of sound card drivers. They make
13649 sound programming easier since they provide a common API. Say Y or M
13650 here (the module will be called sound.o) if you haven't found a
13651 driver for your sound card above, then pick your driver from the
13654 Persistent DMA buffers
13656 Linux can often have problems allocating DMA buffers for ISA sound
13657 cards on machines with more than 16MB of RAM. This is because ISA
13658 DMA buffers must exist below the 16MB boundary and it is quite
13659 possible that a large enough free block in this region cannot be
13660 found after the machine has been running for a while. If you say Y
13661 here the DMA buffers (64Kb) will be allocated at boot time and kept
13662 until the shutdown. This option is only useful if you said Y to
13663 "OSS sound modules", above. If you said M to "OSS sound modules"
13664 then you can get the persistent DMA buffer functionality by passing
13665 the command-line argument "dmabuf=1" to the sound.o module.
13667 Say Y unless you have 16MB or less RAM or a PCI sound card.
13669 Support for Aztech Sound Galaxy (non-PnP) cards
13670 CONFIG_SOUND_SGALAXY
13671 This module initializes the older non Plug and Play sound galaxy
13672 cards from Aztech. It supports the Waverider Pro 32 - 3D and the
13673 Galaxy Washington 16.
13675 If you compile the driver into the kernel, you have to add
13676 "sgalaxy=<io>,<irq>,<dma>,<dma2>,<sgbase>" to the kernel command
13679 Support for AD1816(A) based cards (EXPERIMENTAL)
13680 CONFIG_SOUND_AD1816
13681 Say M here if you have a sound card based on the Analog Devices
13684 If you compile the driver into the kernel, you have to add
13685 "ad1816=<io>,<irq>,<dma>,<dma2>" to the kernel command line.
13687 Yamaha OPL3-SA1 audio controller
13688 CONFIG_SOUND_OPL3SA1
13689 Say Y or M if you have a Yamaha OPL3-SA1 sound chip, which is
13690 usually built into motherboards. Read Documentation/sound/OPL3-SA
13693 If you compile the driver into the kernel, you have to add
13694 "opl3sa=<io>,<irq>,<dma>,<dma2>,<mpuio>,<mpuirq>" to the kernel
13697 ProAudioSpectrum 16 support
13699 Answer Y only if you have a Pro Audio Spectrum 16, ProAudio Studio
13700 16 or Logitech SoundMan 16 sound card. Answer N if you have some
13701 other card made by Media Vision or Logitech since those are not
13702 PAS16 compatible. Please read Documentation/sound/PAS16.
13704 If you compile the driver into the kernel, you have to add
13705 "pas2=<io>,<irq>,<dma>,<dma2>,<sbio>,<sbirq>,<sbdma>,<sbdma2>
13706 to the kernel command line.
13708 100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support
13710 Answer Y if you have an original Sound Blaster card made by Creative
13711 Labs or a 100% hardware compatible clone (like the Thunderboard or
13712 SM Games). For an unknown card you may answer Y if the card claims
13713 to be Sound Blaster-compatible.
13715 Please read the file Documentation/sound/Soundblaster.
13717 You should also say Y here for cards based on the Avance Logic
13718 ALS-007 and ALS-1X0 chips (read Documentation/sound/ALS) and for cards
13719 based on ESS chips (read Documentation/sound/ESS1868 and
13720 Documentation/sound/ESS). If you have an SB AWE 32 or SB AWE 64, say
13721 Y here and also to "AWE32 synth" below and read
13722 Documentation/sound/INSTALL.awe. If you have an IBM Mwave card, say
13723 Y here and read Documentation/sound/mwave.
13725 If you compile the driver into the kernel and don't want to use
13726 isapnp, you have to add "sb=<io>,<irq>,<dma>,<dma2>" to the kernel
13729 You can say M here to compile this driver as a module; the module is
13732 #Loopback MIDI device support
13733 #CONFIG_SOUND_VMIDI
13735 ### somebody please fill this in.
13738 Gravis Ultrasound support
13740 Say Y here for any type of Gravis Ultrasound card, including
13741 the GUS or GUS MAX. See also Documentation/sound/ultrasound for
13742 more information on configuring this card with modules.
13744 If you compile the driver into the kernel, you have to add
13745 "gus=<io>,<irq>,<dma>,<dma2>" to the kernel command line.
13747 MPU-401 support (NOT for SB16)
13748 CONFIG_SOUND_MPU401
13749 Be careful with this question. The MPU401 interface is supported by
13750 all sound cards. However, some natively supported cards have their
13751 own driver for MPU401. Enabling this MPU401 option with these cards
13752 will cause a conflict. Also, enabling MPU401 on a system that
13753 doesn't really have a MPU401 could cause some trouble. If your card
13754 was in the list of supported cards, look at the card specific
13755 instructions in the drivers/sound/Readme.cards file. It's safe to
13756 answer Y if you have a true MPU401 MIDI interface card.
13758 If you compile the driver into the kernel, you have to add
13759 "mpu401=<io>,<irq>" to the kernel command line.
13762 CONFIG_SOUND_UART6850
13763 This option enables support for MIDI interfaces based on the 6850
13764 UART chip. This interface is rarely found on sound cards. It's safe
13765 to answer N to this question.
13767 If you compile the driver into the kernel, you have to add
13768 "uart6850=<io>,<irq>" to the kernel command line.
13770 PSS (AD1848, ADSP-2115, ESC614) support
13772 Answer Y or M if you have an Orchid SW32, Cardinal DSP16, Beethoven
13773 ADSP-16 or some other card based on the PSS chipset (AD1848 codec +
13774 ADSP-2115 DSP chip + Echo ESC614 ASIC CHIP). For more information on
13775 how to compile it into the kernel or as a module see the file
13776 Documentation/sound/PSS.
13778 If you compile the driver into the kernel, you have to add
13779 "pss=<io>,<mssio>,<mssirq>,<mssdma>,<mpuio>,<mpuirq>" to the kernel
13782 Enable PSS mixer (Beethoven ADSP-16 and other compatible)
13784 Answer Y for Beethoven ADSP-16. You may try to say Y also for other
13785 cards if they have master volume, bass, treble, and you can't
13786 control it under Linux. If you answer N for Beethoven ADSP-16, you
13787 can't control master volume, bass, treble and synth volume.
13789 If you said M to "PSS support" above, you may enable or disable this
13790 PSS mixer with the module parameter pss_mixer. For more information
13791 see the file Documentation/sound/PSS.
13793 Have DSPxxx.LD firmware file
13794 CONFIG_PSS_HAVE_BOOT
13795 If you have the DSPxxx.LD file or SYNTH.LD file for you card, say Y
13796 to include this file. Without this file the synth device (OPL) may
13799 Full pathname of DSPxxx.LD firmware file
13800 CONFIG_PSS_BOOT_FILE
13801 Enter the full pathname of your DSPxxx.LD file or SYNTH.LD file,
13804 Microsoft Sound System support
13806 Again think carefully before answering Y to this question. It's safe
13807 to answer Y if you have the original Windows Sound System card made
13808 by Microsoft or Aztech SG 16 Pro (or NX16 Pro). Also you may say Y
13809 in case your card is NOT among these:
13811 ATI Stereo F/X, AdLib, Audio Excell DSP16, Cardinal DSP16,
13812 Ensoniq SoundScape (and compatibles made by Reveal and Spea),
13813 Gravis Ultrasound, Gravis Ultrasound ACE, Gravis Ultrasound Max,
13814 Gravis Ultrasound with 16 bit option, Logitech Sound Man 16,
13815 Logitech SoundMan Games, Logitech SoundMan Wave, MAD16 Pro (OPTi
13816 82C929), Media Vision Jazz16, MediaTriX AudioTriX Pro, Microsoft
13817 Windows Sound System (MSS/WSS), Mozart (OAK OTI-601), Orchid
13818 SW32, Personal Sound System (PSS), Pro Audio Spectrum 16, Pro
13819 Audio Studio 16, Pro Sonic 16, Roland MPU-401 MIDI interface,
13820 Sound Blaster 1.0, Sound Blaster 16, Sound Blaster 16ASP, Sound
13821 Blaster 2.0, Sound Blaster AWE32, Sound Blaster Pro, TI TM4000M
13822 notebook, ThunderBoard, Turtle Beach Tropez, Yamaha FM
13823 synthesizers (OPL2, OPL3 and OPL4), 6850 UART MIDI Interface.
13825 For cards having native support in VoxWare, consult the card
13826 specific instructions in drivers/sound/Readme.cards. Some drivers
13827 have their own MSS support and saying Y to this option will cause a
13830 If you compile the driver into the kernel, you have to add
13831 "ad1848=<io>,<irq>,<dma>,<dma2>[,<type>]" to the kernel command
13834 SGI Visual Workstation on-board audio
13836 Say Y or M if you have an SGI Visual Workstation and you want to
13837 be able to use its on-board audio. Read Documentation/sound/visws
13838 for more info on this driver's capabilities.
13840 Ensoniq Soundscape support
13841 CONFIG_SOUND_SSCAPE
13842 Answer Y if you have a sound card based on the Ensoniq SoundScape
13843 chipset. Such cards are being manufactured at least by Ensoniq, Spea
13844 and Reveal (Reveal makes also other cards).
13846 If you compile the driver into the kernel, you have to add
13847 "sscape=<io>,<irq>,<dma>,<mpuio>,<mpuirq>" to the kernel command
13850 MediaTriX AudioTriX Pro support
13852 Answer Y if you have the AudioTriX Pro sound card manufactured
13855 Have TRXPRO.HEX firmware file
13856 CONFIG_TRIX_HAVE_BOOT
13857 The MediaTrix AudioTrix Pro has an on-board microcontroller which
13858 needs to be initialized by downloading the code from the file
13859 TRXPRO.HEX in the DOS driver directory. If you don't have the
13860 TRXPRO.HEX file handy you may skip this step. However, the SB and
13861 MPU-401 modes of AudioTrix Pro will not work without this file!
13863 Full pathname of TRXPRO.HEX firmware file
13864 CONFIG_TRIX_BOOT_FILE
13865 Enter the full pathname of your TRXPRO.HEX file, starting from /.
13867 Support for OPTi MAD16 and/or Mozart based cards
13869 Answer Y if your card has a Mozart (OAK OTI-601) or MAD16 (OPTi
13870 82C928 or 82C929 or 82C931) audio interface chip. For the 82C931,
13871 please read drivers/sound/README.C931. These chips are currently
13872 quite common so it's possible that many no-name cards have one of
13873 them. In addition the MAD16 chip is used in some cards made by known
13874 manufacturers such as Turtle Beach (Tropez), Reveal (some models)
13875 and Diamond (latest ones). Note however that the Tropez sound cards
13876 have their own driver; if you have one of those, say N here and Y or
13877 M to "Full support for Turtle Beach WaveFront", below.
13879 If you compile the driver into the kernel, you have to add
13880 "mad16=<io>,<irq>,<dma>,<dma2>,<mpuio>,<mpuirq>" to the
13881 kernel command line.
13883 See also Documentation/sound/Opti and Documentation/sound/MAD16 for
13884 more information on setting these cards up as modules.
13886 Full support for Turtle Beach WaveFront synth/sound cards
13887 CONFIG_SOUND_WAVEFRONT
13888 Answer Y or M if you have a Tropez Plus, Tropez or Maui sound card
13889 and read the files Documentation/sound/Wavefront and
13890 Documentation/sound/Tropez+.
13892 Support MIDI in older MAD16 based cards (requires SB)
13893 CONFIG_MAD16_OLDCARD
13894 Answer Y (or M) if you have an older card based on the C928 or
13895 Mozart chipset and you want to have MIDI support. If you enable this
13896 option you also need to enable support for Sound Blaster.
13898 Support for Crystal CS4232 based (PnP) cards
13899 CONFIG_SOUND_CS4232
13900 Say Y here if you have a card based on the Crystal CS4232 chip set,
13901 which uses its own Plug and Play protocol.
13903 If you compile the driver into the kernel, you have to add
13904 "cs4232=<io>,<irq>,<dma>,<dma2>,<mpuio>,<mpuirq>" to the kernel
13907 See Documentation/sound/CS4232 for more information on configuring
13910 Support for Yamaha OPL3-SA2, SA3, and SAx based PnP cards
13911 CONFIG_SOUND_OPL3SA2
13912 Say Y or M if you have a card based on one of these Yamaha
13913 sound chipsets. Read Documentation/sound/OPL3-SA2 for more
13914 information on configuring these cards.
13916 If you compile the driver into the kernel, you have to add
13917 "opl3sa2=<io>,<irq>,<dma>,<dma2>,<mssio>,<mpuio>" to the kernel
13920 Support for Turtle Beach Wave Front (Maui, Tropez) synthesizers
13922 Say Y here if you have a Turtle Beach Wave Front, Maui, or Tropez
13925 If you compile the driver into the kernel, you have to add
13926 "maui=<io>,<irq>" to the kernel command line.
13928 Have OSWF.MOT firmware file
13929 CONFIG_MAUI_HAVE_BOOT
13930 Turtle Beach Maui and Tropez sound cards have a microcontroller
13931 which needs to be initialized prior to use. OSWF.MOT is a file
13932 distributed with the card's DOS/Windows drivers. Answer Y if you
13935 Full pathname of OSWF.MOT firmware file
13936 CONFIG_MAUI_BOOT_FILE
13937 Enter the full pathname of your OSWF.MOT file, starting from /.
13939 Support for Turtle Beach MultiSound Classic, Tahiti, Monterey
13940 CONFIG_SOUND_MSNDCLAS
13941 Say M here if you have a Turtle Beach MultiSound Classic, Tahiti or
13942 Monterey (not for the Pinnacle or Fiji).
13944 See Documentation/sound/MultiSound for important information about
13947 Full pathname of MSNDINIT.BIN firmware file
13948 CONFIG_MSNDCLAS_INIT_FILE
13949 The MultiSound cards have two firmware files which are required for
13950 operation, and are not currently included. These files can be
13951 obtained from Turtle Beach. See Documentation/sound/MultiSound for
13952 information on how to obtain this.
13954 Full pathname of MSNDPERM.BIN firmware file
13955 CONFIG_MSNDCLAS_PERM_FILE
13956 The MultiSound cards have two firmware files which are required for
13957 operation, and are not currently included. These files can be
13958 obtained from Turtle Beach. See Documentation/sound/MultiSound for
13959 information on how to obtain this.
13961 Support for Turtle Beach MultiSound Pinnacle, Fiji
13962 CONFIG_SOUND_MSNDPIN
13963 Say M here if you have a Turtle Beach MultiSound Pinnacle or Fiji.
13964 See Documentation/sound/MultiSound for important information about
13967 Full pathname of PNDSPINI.BIN firmware file
13968 CONFIG_MSNDPIN_INIT_FILE
13969 The MultiSound cards have two firmware files which are required for
13970 operation, and are not currently included. These files can be
13971 obtained from Turtle Beach. See Documentation/sound/MultiSound for
13972 information on how to obtain this.
13974 Full pathname of PNDSPERM.BIN firmware file
13975 CONFIG_MSNDPIN_PERM_FILE
13976 The MultiSound cards have two firmware files which are required for
13977 operation, and are not currently included. These files can be
13978 obtained from Turtle Beach. See Documentation/sound/MultiSound for
13979 information on how to obtain this.
13981 MSND Pinnacle have S/PDIF I/O
13982 CONFIG_MSNDPIN_DIGITAL
13983 If you have the S/PDIF daughter board for the Pinnacle or Fiji,
13984 answer Y here; otherwise, say N. If you have this, you will be able
13985 to play and record from the S/PDIF port (digital signal). See
13986 Documentation/sound/MultiSound for information on how to make use of
13989 MSND Pinnacle non-PnP Mode
13990 CONFIG_MSNDPIN_NONPNP
13991 The Pinnacle and Fiji card resources can be configured either with
13992 PnP, or through a configuration port. Say Y here if your card is NOT
13993 in PnP mode. For the Pinnacle, configuration in non-PnP mode allows
13994 use of the IDE and joystick peripherals on the card as well; these
13995 do not show up when the card is in PnP mode. Specifying zero for any
13996 resource of a device will disable the device. If you are running the
13997 card in PnP mode, you must say N here and use isapnptools to
13998 configure the card's resources.
14000 MSND Pinnacle config port
14002 This is the port which the Pinnacle and Fiji uses to configure the
14003 card's resources when not in PnP mode. If your card is in PnP mode,
14004 then be sure to say N to the previous option, "MSND Pinnacle Non-PnP
14007 MSND buffer size (kB)
14008 CONFIG_MSND_FIFOSIZE
14009 Configures the size of each audio buffer, in kilobytes, for
14010 recording and playing in the MultiSound drivers (both the Classic
14011 and Pinnacle). Larger values reduce the chance of data overruns at
14012 the expense of overall latency. If unsure, use the default.
14014 FM synthesizer (YM3812/OPL-3) support
14015 CONFIG_SOUND_YM3812
14016 Answer Y if your card has a FM chip made by Yamaha (OPL2/OPL3/OPL4).
14017 Answering Y is usually a safe and recommended choice, however some
14018 cards may have software (TSR) FM emulation. Enabling FM support with
14019 these cards may cause trouble (I don't currently know of any such
14021 Please read the file Documentation/sound/OPL3 if your card has an
14024 If you compile the driver into the kernel, you have to add
14025 "opl3=<io>" to the kernel command line.
14029 ACI mixer (miroPCM12/PCM20)
14030 CONFIG_SOUND_ACI_MIXER
14031 ACI (Audio Command Interface) is a protocol used to communicate with
14032 the microcontroller on some sound cards produced by miro, e.g. the
14033 miroSOUND PCM12 and PCM20. The main function of the ACI is to
14034 control the mixer and to get a product identification.
14036 This Voxware ACI driver currently only supports the ACI functions on
14037 the miroSOUND PCM12 and PCM20 cards. On the PCM20, ACI also controls
14038 the radio tuner. This is supported in the video4linux
14039 radio-miropcm20 driver.
14042 CONFIG_SOUND_AWE32_SYNTH
14043 Say Y here if you have a Sound Blaster SB32, AWE32-PnP, SB AWE64 or
14044 similar sound card. See Documentation/sound/README.awe,
14045 Documentation/sound/AWE32 and the Soundblaster-AWE mini-HOWTO,
14046 available from http://www.linuxdoc.org/docs.html#howto for more
14049 Gallant's Audio Excel DSP 16 support (SC-6000 and SC-6600)
14050 CONFIG_SOUND_AEDSP16
14051 Answer Y if you have a Gallant's Audio Excel DSP 16 card. This
14052 driver supports Audio Excel DSP 16 but not the III nor PnP versions
14055 The Gallant's Audio Excel DSP 16 card can emulate either an SBPro or
14056 a Microsoft Sound System card, so you should have said Y to either
14057 "100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support"
14058 or "Microsoft Sound System support", above, and you need to answer
14059 the "MSS emulation" and "SBPro emulation" questions below
14060 accordingly. You should say Y to one and only one of these two
14063 Read the drivers/sound/lowlevel/README.aedsp16 file and the head of
14064 drivers/sound/lowlevel/aedsp16.c as well as
14065 Documentation/sound/AudioExcelDSP16 to get more information about
14066 this driver and its configuration.
14068 Audio Excel DSP 16 (SBPro emulation)
14069 CONFIG_AEDSP16_SBPRO
14070 Answer Y if you want your audio card to emulate Sound Blaster Pro.
14071 You should then say Y to "100% Sound Blaster compatibles
14072 (SB16/32/64, ESS, Jazz16) support" and N to "Audio Excel DSP 16 (MSS
14075 If you compile the driver into the kernel, you have to add
14076 "aedsp16=<io>,<irq>,<dma>,<mssio>,<mpuio>,<mouirq>" to the kernel
14079 Audio Excel DSP 16 (MSS emulation)
14081 Answer Y if you want your audio card to emulate Microsoft Sound
14082 System. You should then say Y to "Microsoft Sound System support"
14083 and say N to "Audio Excel DSP 16 (SBPro emulation)".
14085 SC-6600 based audio cards (new Audio Excel DSP 16)
14087 The SC6600 is the new version of DSP mounted on the Audio Excel DSP
14088 16 cards. Find in the manual the FCC ID of your audio card and
14089 answer Y if you have an SC6600 DSP.
14091 SC-6600 Joystick Interface
14093 Say Y here in order to use the joystick interface of the Audio Excel
14096 SC-6600 CDROM Interface
14097 CONFIG_SC6600_CDROM
14098 This is used to activate the the CDROM interface of the Audio Excel
14099 DSP 16 card. Enter: 0 for Sony, 1 for Panasonic, 2 for IDE, 4 for no
14102 Audio Excel DSP 16 (MPU401 emulation)
14103 CONFIG_AEDSP16_MPU401
14104 Answer Y if you want your audio card to emulate the MPU-401 midi
14105 interface. You should then also say Y to "MPU-401 support".
14107 Note that the I/O base for MPU-401 support of aedsp16 is the same
14108 you have selected for "MPU-401 support". If you are using this
14109 driver as a module you have to specify the MPU I/O base address with
14110 the parameter 'mpu_base=0xNNN'.
14112 Creative EMU10K1 based PCI sound cards
14113 CONFIG_SOUND_EMU10K1
14114 Say Y or M if you have a PCI sound card using the EMU10K1
14115 chipset, such as the Creative SBLive!, SB PCI512 or Emu-APS.
14117 Crystal SoundFusion (CS4280/461x)
14118 CONFIG_SOUND_FUSION
14119 This module drives the Crystal SoundFusion devices (CS4280/46xx series)
14120 when wired as native sound drivers with AC97 codecs. If this driver
14121 does not work try the CS4232 driver.
14123 Ensoniq ES1370 based PCI sound cards
14124 CONFIG_SOUND_ES1370
14125 Say Y or M if you have a PCI sound card utilizing the Ensoniq
14126 ES1370 chipset, such as Ensoniq's AudioPCI (non-97). To find
14127 out if your sound card uses an ES1370 without removing your
14128 computer's cover, use lspci -n and look for the PCI ID
14129 1274:5000. Since Ensoniq was bought by Creative Labs,
14130 Sound Blaster 64/PCI models are either ES1370 or ES1371 based.
14131 This driver differs slightly from OSS/Free, so PLEASE READ
14132 Documentation/sound/es1370.
14134 Ensoniq ES1371 based PCI sound cards
14135 CONFIG_SOUND_ES1371
14136 Say Y or M if you have a PCI sound card utilizing the Ensoniq
14137 ES1371 chipset, such as Ensoniq's AudioPCI97. To find out if
14138 your sound card uses an ES1371 without removing your computer's
14139 cover, use lspci -n and look for the PCI ID 1274:1371. Since
14140 Ensoniq was bought by Creative Labs, Sound Blaster 64/PCI
14141 models are either ES1370 or ES1371 based. This driver differs
14142 slightly from OSS/Free, so PLEASE READ Documentation/sound/es1371.
14144 ESS Solo1 based PCI sound cards (eg. SC1938)
14145 CONFIG_SOUND_ESSSOLO1
14146 Say Y or M if you have a PCI sound card utilizing the ESS Technology
14147 Solo1 chip. To find out if your sound card uses a
14148 Solo1 chip without removing your computer's cover, use
14149 lspci -n and look for the PCI ID 125D:1969. This driver
14150 differs slightly from OSS/Free, so PLEASE READ
14151 Documentation/sound/solo1.
14153 S3 SonicVibes based PCI sound cards
14154 CONFIG_SOUND_SONICVIBES
14155 Say Y or M if you have a PCI sound card utilizing the S3
14156 SonicVibes chipset. To find out if your sound card uses a
14157 SonicVibes chip without removing your computer's cover, use
14158 lspci -n and look for the PCI ID 5333:CA00. This driver
14159 differs slightly from OSS/Free, so PLEASE READ
14160 Documentation/sound/sonicvibes.
14162 Trident 4DWave DX/NX, SiS 7018 or ALi 5451 PCI Audio Core
14163 CONFIG_SOUND_TRIDENT
14164 Say Y or M if you have a PCI sound card utilizing the Trident
14165 4DWave-DX/NX chipset or your mother board chipset has SiS 7018
14166 or ALi 5451 built-in. The SiS 7018 PCI Audio Core is embedded
14167 in SiS960 Super South Bridge and SiS540/630 Single Chipset.
14168 The ALi 5451 PCI Audio Core is embedded in ALi M1535, M1535D,
14169 M1535+ or M1535D+ South Bridge.
14171 Use lspci -n to find out if your sound card or chipset uses
14172 Trident 4DWave or SiS 7018. PCI ID 1023:2000 or 1023:2001 stands
14173 for Trident 4Dwave. PCI ID 1039:7018 stands for SiS7018. PCI ID
14174 10B9:5451 stands for ALi5451.
14176 This driver differs slightly from OSS/Free, so PLEASE READ the
14177 comments at the top of driver/sound/trident.c
14179 Rockwell WaveArtist
14180 CONFIG_SOUND_WAVEARTIST
14181 Say Y here to include support for the Rockwell WaveArtist sound
14182 system. This driver is mainly for the NetWinder.
14184 VIA 82Cxxx Audio Codec
14185 CONFIG_SOUND_VIA82CXXX
14186 Say Y here to include support for the audio codec found on VIA
14187 82Cxxx-based chips. Typically these are built into a motherboard. DO
14188 NOT select Sound Blaster or Adlib with this driver, unless you have
14189 a Sound Blaster or Adlib card in addition to your VIA audio chip.
14191 NeoMagic 256AV/256ZX sound chipsets
14193 Say M here to include audio support for the NeoMagic 256AV/256ZX
14194 chipsets. These are the audio chipsets found in the Sony
14195 Z505S/SX/DX, some Sony F-series, and the Dell Latitude CPi and CPt
14196 laptops. It includes support for an AC97-compatible mixer and an
14197 apparently proprietary sound engine.
14199 See Documentation/sound/NM256 for further information.
14201 ESS Maestro sound chipsets
14202 CONFIG_SOUND_MAESTRO
14203 Say Y or M if you have a sound system driven by ESS's Maestro line
14204 of PCI sound chips. These include the Maestro 1, Maestro 2, and
14205 Maestro 2E. See Documentation/sound/Maestro for more details.
14207 Are you using a crosscompiler
14208 CONFIG_CROSSCOMPILE
14209 Say Y here if you are compiling the kernel on a different
14210 architecture than the one it is intended to run on.
14212 Kernel support for Linux/MIPS 32-bit binary compatibility
14213 CONFIG_MIPS32_COMPAT
14214 Select this option if you want Linux/MIPS 32-bit binary
14215 compatibility. Since all software available for Linux/MIPS is
14216 currently 32-bit you should say Y here.
14218 Build fp exception handler module
14219 CONFIG_MIPS_FPE_MODULE
14220 Build the floating point exception handler module. This option is
14221 only useful for people working on the floating point exception
14222 handler. If you don't, say N.
14224 Remote GDB kernel debugging
14225 CONFIG_REMOTE_DEBUG
14226 If you say Y here, it will be possible to remotely debug the MIPS
14227 kernel using gdb. This enlarges your kernel image disk size by
14228 several megabytes and requires a machine with more than 16 MB,
14229 better 32 MB RAM to avoid excessive linking time. This is only
14230 useful for kernel hackers. If unsure, say N.
14232 Magic System Request Key support
14234 If you say Y here, you will have some control over the system even
14235 if the system crashes for example during kernel debugging (e.g., you
14236 will be able to flush the buffer cache to disk, reboot the system
14237 immediately or dump some status information). This is accomplished
14238 by pressing various keys while holding SysRq (Alt+PrintScreen). It
14239 also works on a serial console (on PC hardware at least), if you
14240 send a BREAK and then within 5 seconds a command keypress. The
14241 keys are documented in Documentation/sysrq.txt. Don't say Y unless
14242 you really know what this hack does.
14246 ISDN ("Integrated Services Digital Networks", called RNIS in France)
14247 is a special type of fully digital telephone service; it's mostly
14248 used to connect to your Internet service provider (with SLIP or
14249 PPP). The main advantage is that the speed is higher than ordinary
14250 modem/telephone connections, and that you can have voice
14251 conversations while downloading stuff. It only works if your
14252 computer is equipped with an ISDN card and both you and your service
14253 provider purchased an ISDN line from the phone company. For details,
14254 read http://alumni.caltech.edu/~dank/isdn/ on the WWW.
14256 This driver allows you to use an ISDN-card for networking
14257 connections and as dialin/out device. The isdn-tty's have a built in
14258 AT-compatible modem emulator. Network devices support autodial,
14259 channel-bundling, callback and caller-authentication without having
14260 a daemon running. A reduced T.70 protocol is supported with tty's
14261 suitable for German BTX. On D-Channel, the protocols EDSS1
14262 (Euro-ISDN) and 1TR6 (German style) are supported. See
14263 Documentation/isdn/README for more information.
14265 If you want to compile the ISDN code as a module ( = code which can
14266 be inserted in and removed from the running kernel whenever you
14267 want), say M here and read Documentation/modules.txt. The module
14268 will be called isdn.o. If unsure, say N.
14270 Support synchronous PPP
14272 Over digital connections such as ISDN, there is no need to
14273 synchronize sender and recipient's clocks with start and stop bits
14274 as is done over analog telephone lines. Instead, one can use
14275 "synchronous PPP". Saying Y here will include this protocol. This
14276 protocol is used by Cisco and Sun for example. So you want to say Y
14277 here if the other end of your ISDN connection supports it. You will
14278 need a special version of pppd (called ipppd) for using this
14279 feature. See Documentation/isdn/README.syncppp and
14280 Documentation/isdn/syncPPP.FAQ for more information.
14282 Support generic MP (RFC 1717)
14284 With synchronous PPP enabled, it is possible to increase throughput
14285 by bundling several ISDN-connections, using this protocol. See
14286 Documentation/isdn/README.syncppp for more information.
14288 Use VJ-compression with synchronous PPP
14290 This enables Van Jacobson header compression for synchronous PPP.
14291 Say Y if the other end of the connection supports it.
14293 Support audio via ISDN
14295 If you say Y here, the modem-emulator will support a subset of the
14296 EIA Class 8 Voice commands. Using a getty with voice-support
14297 (mgetty+sendfax by gert@greenie.muc.de with an extension, available
14298 with the ISDN utility package for example), you will be able to use
14299 your Linux box as an ISDN-answering machine. Of course, this must be
14300 supported by the lowlevel driver also. Currently, the HiSax driver
14301 is the only voice-supporting driver. See
14302 Documentation/isdn/README.audio for more information.
14304 X.25 PLP on top of ISDN
14306 This feature provides the X.25 protocol over ISDN connections.
14307 See Documentation/isdn/README.x25 for more information
14308 if you are thinking about using this.
14310 ISDN diversion services support
14311 CONFIG_ISDN_DIVERSION
14312 This option allows you to use some supplementary diversion
14313 services in conjunction with the HiSax driver on an EURO/DSS1
14316 Supported options are CD (call deflection), CFU (Call forward
14317 unconditional), CFB (Call forward when busy) and CFNR (call forward
14318 not reachable). Additionally the actual CFU, CFB and CFNR state may
14321 The use of CFU, CFB, CFNR and interrogation may be limited to some
14322 countries. The keypad protocol is still not implemented. CD should
14323 work in all countries if the service has been subscribed to.
14325 Please read the file Documentation/isdn/README.diversion.
14327 ICN 2B and 4B support
14328 CONFIG_ISDN_DRV_ICN
14329 This enables support for two kinds of ISDN-cards made by a German
14330 company called ICN. 2B is the standard version for a single ISDN
14331 line with two B-channels, 4B supports two ISDN lines. For running
14332 this card, additional firmware is necessary, which has to be
14333 downloaded into the card using a utility which is distributed
14334 separately. See Documentation/isdn/README and README.icn for more
14337 If you want to compile this as a module ( = code which can be
14338 inserted in and removed from the running kernel whenever you want),
14339 say M here and read Documentation/modules.txt. The module will be
14343 CONFIG_ISDN_DRV_LOOP
14344 This driver provides a virtual ISDN card. Its primary purpose is
14345 testing of linklevel features or configuration without getting
14346 charged by your service-provider for lots of phone calls.
14347 You need will need the loopctrl utility from the latest isdn4k-utils
14348 package to set up this driver.
14350 HiSax SiemensChipSet driver support
14351 CONFIG_ISDN_DRV_HISAX
14352 This is a driver supporting the Siemens chipset on various
14353 ISDN-cards (like AVM A1, Elsa ISDN cards, Teles S0-16.0, Teles
14354 S0-16.3, Teles S0-8, Teles/Creatix PnP, ITK micro ix1 and many
14357 HiSax is just the name of this driver, not the name of any hardware.
14359 If you have a card with such a chipset, you should say Y here and
14360 also to the configuration option of the driver for your particular
14363 If you want to compile this as a module ( = code which can be
14364 inserted in and removed from the running kernel whenever you want),
14365 say M here and read Documentation/modules.txt. The module will be
14366 called hisax.o. See Documentation/isdn/README.HiSax for more
14367 information on using this driver.
14369 HiSax Support for EURO/DSS1
14371 Say Y or N according to the D-channel protocol which your local
14372 telephone service company provides.
14374 The call control protocol E-DSS1 is used in most European countries.
14375 If unsure, say yes.
14377 Support for german charge info
14379 If you want that the HiSax hardware driver sends messages to the
14380 upper level of the isdn code on each AOCD (Advice Of Charge, During
14381 the call -- transmission of the fee information during a call) and
14382 on each AOCE (Advice Of Charge, at the End of the call --
14383 transmission of fee information at the end of the call), say Y here.
14384 This works only in Germany.
14386 Disable sending complete
14387 CONFIG_HISAX_NO_SENDCOMPLETE
14388 If you have trouble with some ugly exchanges or you live in
14389 Australia select this option.
14391 Disable sending low layer compatibility
14392 CONFIG_HISAX_NO_LLC
14393 If you have trouble with some ugly exchanges try to select this
14396 Disable keypad protocol option
14397 CONFIG_HISAX_NO_KEYPAD
14398 If you like to send special dial strings including * or # without
14399 using the keypad protocol, select this option.
14401 HiSax Support for German 1TR6
14403 Say Y or N according to the D-channel protocol which your local
14404 telephone service company provides.
14406 1TR6 is an old call control protocol which was used in Germany
14407 before E-DSS1 was established. Nowadays, all new lines in Germany
14410 HiSax Support for US NI1
14412 Enable this if you like to use ISDN in US on a NI1 basic rate interface.
14416 This enables HiSax support for the Teles ISDN-cards S0-16.0, S0-8
14417 and many compatibles.
14419 See Documentation/isdn/README.HiSax on how to configure it using the
14420 different cards, a different D-channel protocol, or non-standard
14421 IRQ/port/shmem settings.
14423 Teles 16.3 or PNP or PCMCIA
14425 This enables HiSax support for the Teles ISDN-cards S0-16.3 the
14426 Teles/Creatix PnP and the Teles PCMCIA.
14428 See Documentation/isdn/README.HiSax on how to configure it using the
14429 different cards, a different D-channel protocol, or non-standard
14433 CONFIG_HISAX_TELESPCI
14434 This enables HiSax support for the Teles PCI.
14435 See Documentation/isdn/README.HiSax on how to configure it.
14439 This enables HiSax support for the Teles/Creatix parallel port
14440 S0BOX. See Documentation/isdn/README.HiSax on how to configure it.
14443 CONFIG_HISAX_AVM_A1
14444 This enables HiSax support for the AVM A1 (aka "Fritz").
14446 See Documentation/isdn/README.HiSax on how to configure it using the
14447 different cards, a different D-channel protocol, or non-standard
14450 AVM PnP/PCI (Fritz!PNP/PCI)
14451 CONFIG_HISAX_FRITZPCI
14452 This enables HiSax support for the AVM "Fritz!PnP" and "Fritz!PCI".
14453 See Documentation/isdn/README.HiSax on how to configure it.
14455 AVM A1 PCMCIA (Fritz)
14456 CONFIG_HISAX_AVM_A1_PCMCIA
14457 This enables HiSax support for the AVM A1 "Fritz!PCMCIA").
14458 See Documentation/isdn/README.HiSax on how to configure it.
14462 This enables HiSax support for the Elsa Mircolink ISA cards, for the
14463 Elsa Quickstep series cards and Elsa PCMCIA.
14465 See Documentation/isdn/README.HiSax on how to configure it using the
14466 different cards, a different D-channel protocol, or non-standard
14469 ITK ix1-micro Revision 2
14470 CONFIG_HISAX_IX1MICROR2
14471 This enables HiSax support for the ITK ix1-micro Revision 2 card.
14473 See Documentation/isdn/README.HiSax on how to configure it using the
14474 different cards, a different D-channel protocol, or non-standard
14477 Eicon.Diehl Diva cards
14478 CONFIG_HISAX_DIEHLDIVA
14479 This enables HiSax support for the Eicon.Diehl Diva none PRO
14480 versions passive ISDN cards.
14482 See Documentation/isdn/README.HiSax on how to configure it using the
14483 different cards, a different D-channel protocol, or non-standard
14487 CONFIG_HISAX_ASUSCOM
14488 This enables HiSax support for the AsusCom and their OEM versions
14489 passive ISDN ISA cards.
14491 See Documentation/isdn/README.HiSax on how to configure it using the
14492 different cards, a different D-channel protocol, or non-standard
14496 CONFIG_HISAX_TELEINT
14497 This enables HiSax support for the TELEINT SA1 semiactiv ISDN card.
14499 See Documentation/isdn/README.HiSax on how to configure it using the
14500 different cards, a different D-channel protocol, or non-standard
14505 This enables HiSax support for the HFC-S 2BDS0 based cards, like
14508 See Documentation/isdn/README.HiSax on how to configure it using the
14509 different cards, a different D-channel protocol, or non-standard
14513 CONFIG_HISAX_SEDLBAUER
14514 This enables HiSax support for the Sedlbauer passive ISDN cards.
14516 See Documentation/isdn/README.HiSax on how to configure it using the
14517 different cards, a different D-channel protocol, or non-standard
14520 USR Sportster internal TA
14521 CONFIG_HISAX_SPORTSTER
14522 This enables HiSax support for the USR Sportster internal TA card.
14524 See Documentation/isdn/README.HiSax on how to configure it using a
14525 different D-channel protocol, or non-standard IRQ/port settings.
14529 This enables HiSax support for the ITH MIC card.
14531 See Documentation/isdn/README.HiSax on how to configure it using a
14532 different D-channel protocol, or non-standard IRQ/port settings.
14535 CONFIG_HISAX_NETJET
14536 This enables HiSax support for the NetJet from Traverse
14539 See Documentation/isdn/README.HiSax on how to configure it using a
14540 different D-channel protocol, or non-standard IRQ/port settings.
14543 CONFIG_HISAX_NETJET_U
14544 This enables HiSax support for the Netspider U interface ISDN card from
14545 Traverse Technologies.
14546 See Documentation/isdn/README.HiSax on how to configure it using a
14547 different D-channel protocol, or non-standard IRQ/port settings.
14551 This enables HiSax support for the Dr. Neuhaus Niccy PnP or PCI.
14553 See Documentation/isdn/README.HiSax on how to configure it using a
14554 different D-channel protocol, or non-standard IRQ/port settings.
14556 Siemens I-Surf card
14558 This enables HiSax support for the Siemens I-Talk/I-Surf card with
14560 See Documentation/isdn/README.HiSax on how to configure it using a
14561 different D-channel protocol, or non-standard IRQ/port settings.
14564 CONFIG_HISAX_HSTSAPHIR
14565 This enables HiSax support for the HST Saphir card.
14567 See Documentation/isdn/README.HiSax on how to configure it using a
14568 different D-channel protocol, or non-standard IRQ/port settings.
14571 CONFIG_HISAX_BKM_A4T
14572 This enables HiSax support for the Telekom A4T card.
14574 See Documentation/isdn/README.HiSax on how to configure it using a
14575 different D-channel protocol, or non-standard IRQ/port settings.
14578 CONFIG_HISAX_SCT_QUADRO
14579 This enables HiSax support for the Scitel Quadro card.
14581 See Documentation/isdn/README.HiSax on how to configure it using a
14582 different D-channel protocol, or non-standard IRQ/port settings.
14586 This enables HiSax support for the Gazel cards.
14588 See Documentation/isdn/README.HiSax on how to configure it using a
14589 different D-channel protocol, or non-standard IRQ/port settings.
14592 CONFIG_HISAX_HFC_PCI
14593 This enables HiSax support for the HFC-S PCI 2BDS0 based cards.
14595 For more informations see under Documentation/isdn/README.hfc-pci.
14597 Winbond W6692 based cards
14599 This enables HiSax support for Winbond W6692 based PCI ISDN cards.
14601 See Documentation/isdn/README.HiSax on how to configure it using a
14602 different D-channel protocol, or non-standard IRQ/port settings.
14604 HFC-S+, HFC-SP, HFC-PCMCIA cards (EXPERIMENTAL)
14605 CONFIG_HISAX_HFC_SX
14606 This enables HiSax support for the HFC-S+, HFC-SP and HFC-PCMCIA
14607 cards. This code is not finished yet.
14609 Am7930 (EXPERIMENTAL)
14610 CONFIG_HISAX_AMD7930
14611 This enables HiSax support for the AMD7930 chips on some SPARCs.
14612 This code is not finished yet.
14615 CONFIG_ISDN_DRV_PCBIT
14616 This enables support for the PCBIT ISDN-card. This card is
14617 manufactured in Portugal by Octal. For running this card, additional
14618 firmware is necessary, which has to be downloaded into the card
14619 using a utility which is distributed separately. See
14620 Documentation/isdn/README and Documentation/isdn/README.pcbit for
14623 If you want to compile this as a module ( = code which can be
14624 inserted in and removed from the running kernel whenever you want),
14625 say M here and read Documentation/modules.txt. The module will be
14628 Spellcaster support (EXPERIMENTAL)
14630 This enables support for the Spellcaster BRI ISDN boards. This
14631 driver currently builds only in a modularized version ( = code which
14632 can be inserted in and removed from the running kernel whenever you
14633 want, details in Documentation/modules.txt); the module will be
14634 called sc.o. See Documentation/isdn/README.sc and
14635 http://www.spellcast.com for more information.
14637 Eicon active card support
14638 CONFIG_ISDN_DRV_EICON
14639 Say Y here if you have an Eicon active ISDN card. In order to use
14640 this card, additional firmware is necessary, which has to be loaded
14641 into the card using the eiconctrl utility which is part of the
14642 latest isdn4k-utils package. Please read the file
14643 Documentation/isdn/README.eicon for more information.
14645 Eicon Diva Server card support
14646 CONFIG_ISDN_DRV_EICON_PCI
14647 Say Y here if you have an Eicon Diva Server (BRI/PRI/4BRI) ISDN card.
14648 Please read Documentation/isdn/README.eicon for more information.
14650 Eicon old-type card support
14651 CONFIG_ISDN_DRV_EICON_ISA
14652 Say Y here if you have an old-type Eicon active ISDN card. In order
14653 to use this card, additional firmware is necessary, which has to be
14654 loaded into the card using the eiconctrl utility which is part of
14655 the latest isdn4k-utils package. Please read the file
14656 Documentation/isdn/README.eicon for more information.
14658 Eicon driver type standalone
14659 CONFIG_ISDN_DRV_EICON_STANDALONE
14660 Enable this option if you want the eicon driver as standalone
14661 version with no interface to the ISDN4Linux isdn module. If you
14662 say Y here, the eicon module only supports the Diva Server PCI
14663 cards and will provide its own IDI interface. You should say N
14666 Support AT-Fax Class 1 and 2 commands
14667 CONFIG_ISDN_TTY_FAX
14668 If you say Y here, the modem-emulator will support a subset of the
14669 Fax Class 1 and 2 commands. Using a getty with fax-support
14670 (mgetty+sendfax, hylafax), you will be able to use your Linux box as
14671 an ISDN-fax-machine. This must be supported by the lowlevel driver
14672 also. See Documentation/isdn/README.fax for more information.
14676 This provides the CAPI (Common ISDN Application Programming
14677 Interface, a standard making it easy for programs to access ISDN
14678 hardware, see http://www.capi.org/ . This is needed for AVM's set of
14679 active ISDN controllers like B1, T1, M1.
14681 This code is also available as a module ( = code which can be
14682 inserted in and removed from the running kernel whenever you want).
14683 The modules will be called capi.o and kernelcapi.o. If you want to
14684 compile it as a module, say M here and read
14685 Documentation/modules.txt.
14688 CONFIG_ISDN_DRV_AVMB1_B1ISA
14689 Enable support for the ISA version of the AVM B1 card.
14692 CONFIG_ISDN_DRV_AVMB1_B1PCI
14693 Enable support for the PCI version of the AVM B1 card.
14695 AVM B1 PCI V4 support
14696 CONFIG_ISDN_DRV_AVMB1_B1PCIV4
14697 Enable support for the V4 version of AVM B1 PCI card.
14699 AVM T1/T1-B ISA support
14700 CONFIG_ISDN_DRV_AVMB1_T1ISA
14701 Enable support for the AVM T1 T1B card.
14702 Note: This is a PRI card and handle 30 B-channels.
14704 AVM B1/M1/M2 PCMCIA support
14705 CONFIG_ISDN_DRV_AVMB1_B1PCMCIA
14706 Enable support for the PCMCIA version of the AVM B1 card.
14708 AVM T1/T1-B PCI support
14709 CONFIG_ISDN_DRV_AVMB1_T1PCI
14710 Enable support for the AVM T1 T1B card.
14711 Note: This is a PRI card and handle 30 B-channels.
14714 CONFIG_ISDN_DRV_AVMB1_C4
14715 Enable support for the AVM C4 PCI card.
14716 This card handle 4 BRI ISDN lines (8 channels).
14718 Verbose reason code reporting (kernel size +=7K)
14719 CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON
14720 If you say Y here, the AVM B1 driver will give verbose reasons for
14721 disconnecting. This will increase the size of the kernel by 7 KB. If
14724 IBM Active 2000 support (EXPERIMENTAL)
14725 CONFIG_ISDN_DRV_ACT2000
14726 Say Y here if you have an IBM Active 2000 ISDN card. In order to use
14727 this card, additional firmware is necessary, which has to be loaded
14728 into the card using a utility which is part of the latest
14729 isdn4k-utils package. Please read the file
14730 Documentation/isdn/README.act2000 for more information.
14732 Hypercope HYSDN cards (Champ, Ergo, Metro) support (module)
14734 Say Y here if you have one of Hypercope's active PCI ISDN cards
14735 Champ, Ergo and Metro. You will then get a module called hysdn.o.
14736 Please read the file Documentation/isdn/README.hysdn for more
14739 HYSDN CAPI 2.0 support
14741 Say Y here if you like to use Hypercope's CAPI 2.0 interface
14743 Support for Sun4 architecture
14745 Say Y here if, and only if, your machine is a Sun4. Note that
14746 a kernel compiled with this option will run only on Sun4.
14747 (And the current version will probably work only on sun4/330.)
14749 SPARC ESP SCSI support
14751 This is the driver for the Sun ESP SCSI host adapter. The ESP
14752 chipset is present in most SPARC SBUS-based computers.
14754 This support is also available as a module called esp.o ( = code
14755 which can be inserted in and removed from the running kernel
14756 whenever you want). If you want to compile it as a module, say M
14757 here and read Documentation/modules.txt.
14759 PTI Qlogic, ISP Driver
14760 CONFIG_SCSI_QLOGICPTI
14761 This driver supports SBUS SCSI controllers from PTI or QLogic. These
14762 controllers are known under Solaris as qpti and in the openprom as
14763 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
14764 driven by a different driver.
14766 This support is also available as a module called qlogicpti.o ( =
14767 code which can be inserted in and removed from the running kernel
14768 whenever you want). If you want to compile it as a module, say M
14769 here and read Documentation/modules.txt.
14771 SPARC /dev/openprom compatibility driver (EXPERIMENTAL)
14772 CONFIG_SUN_OPENPROMIO
14773 This driver provides user programs with an interface to the SPARC
14774 PROM device tree. The driver implements a SunOS-compatible
14775 interface and a NetBSD-compatible interface.
14777 If you want to compile this as a module ( = code which can be
14778 inserted in and removed from the running kernel whenever you want),
14779 say M and read Documentation/modules.txt. If unsure, say Y.
14781 Openprom tree appears in /proc/openprom
14782 CONFIG_SUN_OPENPROMFS
14783 If you say Y, the OpenPROM device tree will be available as a
14784 virtual file system, which you can mount to /proc/openprom by "mount
14785 -t openpromfs none /proc/openprom".
14787 If you want to compile the /proc/openprom support as a module ( =
14788 code which can be inserted in and removed from the running kernel
14789 whenever you want), say M here and read Documentation/modules.txt.
14790 The module will be called openpromfs.o. If unsure, say M.
14792 Kernel support for Linux/Sparc 32bit binary compatibility
14793 CONFIG_SPARC32_COMPAT
14794 This allows you to run 32-bit binaries on your Ultra.
14795 Everybody wants this; say Y.
14797 Kernel support for 32-bit ELF binaries
14798 CONFIG_BINFMT_ELF32
14799 This allows you to run 32-bit Linux/ELF binaries on your Ultra.
14800 Everybody wants this; say Y.
14802 Kernel support for 32-bit (ie. SunOS) a.out binaries
14803 CONFIG_BINFMT_AOUT32
14804 This allows you to run 32-bit a.out format binaries on your Ultra.
14805 If you want to run SunOS binaries (see SunOS binary emulation below)
14806 or other a.out binaries, say Y. If unsure, say N.
14808 SunOS binary emulation
14810 This allows you to run most SunOS binaries. If you want to do this,
14811 say Y here and place appropriate files in /usr/gnemul/sunos. See
14812 http://www.ultralinux.org/faq.html for more information. If you want
14813 to run SunOS binaries on an Ultra you must also say Y to "Kernel
14814 support for 32-bit a.out binaries" above.
14816 Mostek real time clock support
14817 CONFIG_SUN_MOSTEK_RTC
14818 The Mostek RTC chip is used on all known Sun computers except
14819 some JavaStations. For a JavaStation you need to say Y both here
14820 and to "Enhanced Real Time Clock Support".
14822 Say Y here unless you are building a special purpose kernel.
14824 OBP Flash Device support
14826 The OpenBoot PROM on Ultra systems is flashable. If you want to be
14827 able to upgrade the OBP firmware, say Y here.
14829 JavaStation OS Flash SIMM
14831 If you say Y here, you will be able to boot from your JavaStation's
14834 Siemens SAB82532 serial support
14836 This driver supports the serial ports on newer (PCI) Ultra systems.
14837 Say Y if you want to be able to use your serial ports.
14839 Aurora Multiboard 1600se (EXPERIMENTAL)
14841 The Aurora Multiboard is a multi-port high-speed serial controller.
14842 If you have one of these, say Y.
14844 Audio support (EXPERIMENTAL)
14846 This driver provides support for the build-in sound devices on most
14847 Sun machines. If you want to be able to use this, select this option
14848 and one or more of the lowlevel drivers below. See
14849 http://www.dementia.org/~shadow/sparcaudio.html for more
14852 AMD7930 Lowlevel Driver
14853 CONFIG_SPARCAUDIO_AMD7930
14854 This driver supports the AMD 7930 chip found on sun4c, 4/6xx, and
14855 SparcClassic systems.
14857 CS4231 Lowlevel Driver
14858 CONFIG_SPARCAUDIO_CS4231
14859 This driver supports the Crystal Semiconductor CS4231 chip found on
14860 the SS4, SS5, and Ultras.
14862 DBRI Lowlevel Driver
14863 CONFIG_SPARCAUDIO_DBRI
14864 This driver supports the DBRI audio interface found on the SS10,
14865 SS20, Sparcbook 3, and Voyager systems.
14867 Dummy lowlevel Driver
14868 CONFIG_SPARCAUDIO_DUMMY
14869 This is a pseudo-driver used for debugging and testing the
14870 sparcaudio subsystem. Say N unless you want to work on this
14873 Sparc hardware (EXPERIMENTAL)
14874 CONFIG_PARPORT_SUNBPP
14875 This driver provides support for the bidirectional parallel port
14876 found on many Sun machines. Note that many of the newer Ultras
14877 actually have pc style hardware instead.
14880 # m68k-specific kernel options
14881 # Documented by Chris Lawrence <quango@themall.net> et al.
14885 This option enables support for the Amiga series of computers. If
14886 you plan to use this kernel on an Amiga, say Y here and browse the
14887 material available in Documentation/m68k; otherwise say N.
14891 This option enables support for the 68000-based Atari series of
14892 computers (including the TT, Falcon and Medusa). If you plan to use
14893 this kernel on an Atari, say Y here and browse the material
14894 available in Documentation/m68k; otherwise say N.
14898 This option enables support for the Hades Atari clone. If you plan
14899 to use this kernel on a Hades, say Y here; otherwise say N.
14903 This option enables support for the Apple Macintosh series of
14904 computers (yes, there is experimental support now, at least for part
14907 Say N unless you're willing to code the remaining necessary support.
14912 This option enables support for the HP9000/300 series of
14913 workstations. Support for these machines is still very experimental.
14914 If you plan to try to use the kernel on such a machine say Y here.
14915 Everybody else says N.
14919 This option enables support for the Sun 3x series of workstations.
14920 Be warned that this support is very experimental. You will also want
14921 to say Y to 68020 support and N to the other processors below.
14923 If you don't want to compile a kernel for a Sun 3x, say N.
14927 If you anticipate running this kernel on a computer with a MC68020
14928 processor, say Y. Otherwise, say N. Note that the 68020 requires a
14929 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
14930 Sun 3, which provides its own version.
14934 If you anticipate running this kernel on a computer with a MC68030
14935 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
14936 work, as it does not include an MMU (Memory Management Unit).
14940 If you anticipate running this kernel on a computer with a MC68LC040
14941 or MC68040 processor, say Y. Otherwise, say N. Note that an
14942 MC68EC040 will not work, as it does not include an MMU (Memory
14947 If you anticipate running this kernel on a computer with a MC68060
14948 processor, say Y. Otherwise, say N.
14950 Math emulation support (EXPERIMENTAL)
14952 At some point in the future, this will cause floating-point math
14953 instructions to be emulated by the kernel on machines that lack a
14954 floating-point math coprocessor. Thrill-seekers and chronically
14955 sleep-deprived psychotic hacker types can say Y now, everyone else
14956 should probably wait a while.
14958 Math emulation only kernel
14959 CONFIG_M68KFPU_EMU_ONLY
14960 This option prevents any floating-point instructions from being
14961 compiled into the kernel, thereby the kernel doesn't save any
14962 floating point context anymore during task switches, so this
14963 kernel will only be usable on machines without a floating-point
14964 math coprocessor. This makes the kernel a bit faster as no tests
14965 needs to be executed whether a floating-point instruction in the
14966 kernel should be executed or not.
14968 Math emulation extra precision
14969 CONFIG_M68KFPU_EMU_EXTRAPREC
14970 The fpu uses normally a few bit more during calculations for
14971 correct rounding, the emulator can (often) do the same but this
14972 extra calculation can cost quite some time, so you can disable
14973 it here. The emulator will then "only" calculate with a 64 bit
14974 mantissa and round slightly incorrect, what is more then enough
14977 Advanced configuration options
14979 This gives you access to some advanced options for the CPU. The
14980 defaults should be fine for most users, but these options may make
14981 it possible for you to improve performance somewhat if you know what
14984 Note that the answer to this question won't directly affect the
14985 kernel: saying N will just cause this configure script to skip all
14986 the questions about these options.
14988 Most users should say N to this question.
14990 Use read-modify-write instructions
14992 This allows to use certain instructions that work with indivisible
14993 read-modify-write bus cycles. While this is faster than the
14994 workaround of disabling interrupts, it can conflict with DMA
14995 ( = direct memory access) on many Amiga systems, and it is also said
14996 to destabilize other machines. It is very likely that this will
14997 cause serious problems on any Amiga or Atari Medusa if set. The only
14998 configuration where it should work are 68030-based Ataris, where it
14999 apparently improves performance. But you've been warned! Unless you
15000 really know what you are doing, say N. Try Y only if you're quite
15003 Amiga AutoConfig Identification
15005 This enables support for automatic identification of Amiga expansion
15006 cards that obey the AutoConfig(tm) specification.
15007 Say Y if you want your expansion cards to be identified on bootup;
15008 it will enlarge your kernel by about 10 KB. The identification
15009 information is then also available through /proc/zorro (say Y to
15010 "/proc file system support"!). Read Documentation/zorro.txt for more
15013 Note that even if you say N here, you can still use your expansion
15014 cards. If in doubt, say Y.
15016 Amiga 1200/600 PCMCIA support (EXPERIMENTAL)
15017 CONFIG_AMIGA_PCMCIA
15018 Include support in the kernel for pcmcia on Amiga 1200 and Amiga
15019 600. If you intend to use pcmcia cards say Y; otherwise say N.
15021 Amiga Zorro II ramdisk support
15023 This enables support for using Chip RAM and Zorro II RAM as a
15024 ramdisk or as a swap partition. Say Y if you want to include this
15025 driver in the kernel. This driver is also available as a module
15026 ( = code which can be inserted in and removed from the running
15027 kernel whenever you want). The module is called z2ram.o. If you want
15028 to compile it as a module, say M here and read
15029 Documentation/modules.txt.
15031 Atari ST-RAM swap support
15033 This enables support for using (parts of) ST-RAM as swap space,
15034 instead of as normal system memory. This can first enhance system
15035 performance if you have lots of alternate RAM (compared to the size
15036 of ST-RAM), because executable code always will reside in faster
15037 memory. ST-RAM will remain as ultra-fast swap space. On the other
15038 hand, it allows much improved dynamic allocations of ST-RAM buffers
15039 for device driver modules (e.g. floppy, ACSI, SLM printer, DMA
15040 sound). The probability that such allocations at module load time
15041 fail is drastically reduced.
15045 This enables support for the Atari ACSI interface. The driver
15046 supports hard disks and CD-ROMs, which have 512-byte sectors, or can
15047 be switched to that mode. Due to the ACSI command format, only disks
15048 up to 1 GB are supported. Special support for certain ACSI to SCSI
15049 adapters, which could relax that, isn't included yet. The ACSI
15050 driver is also the basis for certain other drivers for devices
15051 attached to the ACSI bus: Atari SLM laser printer, BioNet-100
15052 Ethernet, and PAMsNet Ethernet. If you want to use one of these
15053 devices, you need ACSI support, too.
15055 This driver is also available as a module ( = code which can be
15056 inserted in and removed from the running kernel whenever you want).
15057 The module will be called acsi.o.
15059 Probe all LUNs on each ACSI device
15060 CONFIG_ACSI_MULTI_LUN
15061 If you have a ACSI device that supports more than one LUN (Logical
15062 Unit Number), e.g. a CD jukebox, you should say Y here so that all
15063 will be found by the ACSI driver. An ACSI device with multiple LUNs
15064 acts logically like multiple ACSI devices. The vast majority of ACSI
15065 devices have only one LUN, and so most people can say N here and
15066 should in fact do so, because it is safer.
15068 Atari SLM laser printer support
15070 If you have an Atari SLM laser printer, say Y to include support for
15071 it in the kernel. Otherwise, say N. This driver is also available as
15072 a module ( = code which can be inserted in and removed from the
15073 running kernel whenever you want). The module will be called
15074 acsi_slm.o. Be warned: the driver needs much ST-RAM and can cause
15075 problems due to that fact!
15077 A3000 WD33C93A support
15079 If you have an Amiga 3000 and have SCSI devices connected to the
15080 built-in SCSI controller, say Y. Otherwise, say N. This driver is
15081 also available as a module ( = code which can be inserted in and
15082 removed from the running kernel whenever you want). The module is
15083 called wd33c93.o. If you want to compile it as a module, say M here
15084 and read Documentation/modules.txt.
15086 A2091 WD33C93A support
15088 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
15089 say N. This driver is also available as a module ( = code which can
15090 be inserted in and removed from the running kernel whenever you
15091 want). The module is called wd33c93.o. If you want to compile it as
15092 a module, say M here and read Documentation/modules.txt.
15094 GVP Series II WD33C93A support
15096 If you have a Great Valley Products Series II SCSI controller,
15097 answer Y. Also say Y if you have a later model of GVP SCSI
15098 controller (such as the GVP A4008 or a Combo board). Otherwise,
15099 answer N. This driver does NOT work for the T-Rex series of
15100 accelerators from TekMagic and GVP-M.
15102 This driver is also available as a module ( = code which can be
15103 inserted in and removed from the running kernel whenever you
15104 want). The module will be called gvp11.o. If you want to compile it
15105 as a module, say M here and read Documentation/modules.txt.
15107 Cyberstorm SCSI support
15108 CONFIG_CYBERSTORM_SCSI
15109 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
15110 accelerator board and the optional Cyberstorm SCSI controller,
15111 answer Y. Otherwise, say N.
15113 Cyberstorm II SCSI support
15114 CONFIG_CYBERSTORMII_SCSI
15115 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
15116 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
15119 Blizzard 2060 SCSI support (EXPERIMENTAL)
15120 CONFIG_BLZ2060_SCSI
15121 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
15122 and want to use the onboard SCSI controller, say Y. Otherwise,
15125 Blizzard 1230IV/1260 SCSI support
15126 CONFIG_BLZ1230_SCSI
15127 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
15128 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
15131 Blizzard PowerUP 603e+ SCSI support
15132 CONFIG_BLZ603EPLUS_SCSI
15133 If you have an Amiga 1200 with a Phase5 Blizzard PowerUP 603e+
15134 accelerator, say Y. Otherwise, say N.
15136 Fastlane SCSI support
15137 CONFIG_FASTLANE_SCSI
15138 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
15139 one in the near future, say Y to this question. Otherwise, say N.
15141 Atari native SCSI support
15143 If you have an Atari with built-in NCR5380 SCSI controller (TT,
15144 Falcon, ...) say Y to get it supported. Of course also, if you have
15145 a compatible SCSI controller (e.g. for Medusa). This driver is also
15146 available as a module ( = code which can be inserted in and removed
15147 from the running kernel whenever you want). The module is called
15148 atari_scsi.o. If you want to compile it as a module, say M here and
15149 read Documentation/modules.txt. This driver supports both styles of
15150 NCR integration into the system: the TT style (separate DMA), and
15151 the Falcon style (via ST-DMA, replacing ACSI). It does NOT support
15152 other schemes, like in the Hades (without DMA).
15154 Long delays for Toshiba CD-ROMs
15155 CONFIG_ATARI_SCSI_TOSHIBA_DELAY
15156 This option increases the delay after a SCSI arbitration to
15157 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
15158 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
15159 would impact performance a bit, so say N.
15161 Hades SCSI DMA emulator
15163 This option enables code which emulates the TT SCSI DMA chip on the
15164 Hades. This increases the SCSI transfer rates at least ten times
15165 compared to PIO transfers.
15169 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
15172 This driver is also available as a module ( = code which can be
15173 inserted in and removed from the running kernel whenever you
15174 want). The module is called ariadne.o. If you want to compile it as
15175 a module, say M here and read Documentation/modules.txt.
15179 If you have a Village Tronic Ariadne II Ethernet adapter, say Y.
15182 This driver is also available as a module ( = code which can be
15183 inserted in and removed from the running kernel whenever you
15184 want). The module is called ariadne2.o. If you want to compile it as
15185 a module, say M here and read Documentation/modules.txt.
15189 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
15192 This driver is also available as a module ( = code which can be
15193 inserted in and removed from the running kernel whenever you
15194 want). The module is called a2065.o. If you want to compile it as a
15195 module, say M here and read Documentation/modules.txt.
15199 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
15201 This driver is also available as a module ( = code which can be
15202 inserted in and removed from the running kernel whenever you
15203 want). The module is called hydra.o. If you want to compile it as a
15204 module, say M here and read Documentation/modules.txt.
15206 Pcmcia NE2000 compatible support
15208 If you have a pcmcia ne2000 compatible adapter, say Y. Otherwise,
15211 This driver is also available as a module ( = code which can be
15212 inserted in and removed from the running kernel whenever you
15213 want). The module is called apne.o. If you want to compile it as a
15214 module, say M here and read Documentation/modules.txt.
15216 Atari Lance support
15218 Say Y to include support for several Atari Ethernet adapters based
15219 on the AMD Lance chipset: RieblCard (with or without battery), or
15220 PAMCard VME (also the version by Rhotron, with different addresses).
15223 CONFIG_ATARI_BIONET
15224 Say Y to include support for BioData's BioNet-100 Ethernet adapter
15225 for the ACSI port. The driver works (has to work...) with a polled
15226 I/O scheme, so it's rather slow :-(
15229 CONFIG_ATARI_PAMSNET
15230 Say Y to include support for the PAMsNet Ethernet adapter for the
15231 ACSI port ("ACSI node"). The driver works (has to work...) with a
15232 polled I/O scheme, so it's rather slow :-(
15234 Amiga mouse support
15236 If you want to be able to use an Amiga mouse in Linux, say Y.
15238 This driver is also available as a module ( = code which can be
15239 inserted in and removed from the running kernel whenever you want).
15240 The module is called amigamouse.o. If you want to compile it as a
15241 module, say M here and read Documentation/modules.txt.
15243 Atari mouse support
15245 If you want to be able to use an Atari mouse in Linux, say Y.
15247 This driver is also available as a module ( = code which can be
15248 inserted in and removed from the running kernel whenever you want).
15249 The module is called atarimouse.o. If you want to compile it as a
15250 module, say M here and read Documentation/modules.txt.
15252 Atari MFP serial support
15253 CONFIG_ATARI_MFPSER
15254 If you like to use the MFP serial ports ("Modem1", "Serial1") under
15255 Linux, say Y. The driver equally supports all kinds of MFP serial
15256 ports and automatically detects whether Serial1 is available.
15258 This driver is also available as a module ( = code which can be
15259 inserted in and removed from the running kernel whenever you want).
15260 If you want to compile it as a module, say M here and read
15261 Documentation/modules.txt.
15263 Note for Falcon users: You also have an MFP port, it's just not
15264 wired to the outside... But you could use the port under Linux.
15266 Atari SCC serial support
15268 If you have serial ports based on a Zilog SCC chip (Modem2, Serial2,
15269 LAN) and like to use them under Linux, say Y. All built-in SCC's are
15270 supported (TT, MegaSTE, Falcon), and also the ST-ESCC. If you have
15271 two connectors for channel A (Serial2 and LAN), they are visible as
15272 two separate devices.
15274 This driver is also available as a module ( = code which can be
15275 inserted in and removed from the running kernel whenever you want).
15276 If you want to compile it as a module, say M here and read
15277 Documentation/modules.txt.
15279 Atari SCC serial DMA support
15280 CONFIG_ATARI_SCC_DMA
15281 This enables DMA support for receiving data on channel A of the SCC.
15282 If you have a TT you may say Y here and read
15283 drivers/char/atari_SCC.README. All other users should say N here,
15284 because only the TT has SCC-DMA, even if your machine keeps claiming
15287 Atari MIDI serial support
15289 If you want to use your Atari's MIDI port in Linux, say Y.
15291 This driver is also available as a module ( = code which can be
15292 inserted in and removed from the running kernel whenever you
15293 want). If you want to compile it as a module, say M here and read
15294 Documentation/modules.txt.
15296 Atari DSP56k Digital Signal Processor support (EXPERIMENTAL)
15297 CONFIG_ATARI_DSP56K
15298 If you want to be able to use the DSP56001 in Falcons, say Y. This
15299 driver is still experimental, and if you don't know what it is, or
15300 if you don't have this processor, just say N.
15302 This driver is also available as a module ( = code which can be
15303 inserted in and removed from the running kernel whenever you want).
15304 If you want to compile it as a module, say M here and read
15305 Documentation/modules.txt.
15307 Amiga builtin serial support
15308 CONFIG_AMIGA_BUILTIN_SERIAL
15309 If you want to use your Amiga's built-in serial port in Linux,
15312 This driver is also available as a module ( = code which can be
15313 inserted in and removed from the running kernel whenever you
15314 want). If you want to compile it as a module, say M here and read
15315 Documentation/modules.txt.
15317 GVP IO-Extender support
15319 If you want to use a GVP IO-Extender serial card in Linux, say Y.
15322 Multiface Card III serial support
15323 CONFIG_MULTIFACE_III_TTY
15324 If you want to use a Multiface III card's serial port in Linux,
15327 This driver is also available as a module ( = code which can be
15328 inserted in and removed from the running kernel whenever you want).
15329 If you want to compile it as a module, say M here and read
15330 Documentation/modules.txt.
15332 Atari DMA sound support
15333 CONFIG_DMASOUND_ATARI
15334 If you want to use the internal audio of your Atari in Linux, answer
15335 Y to this question. This will provide a Sun-like /dev/audio,
15336 compatible with the Linux/i386 sound system. Otherwise, say N.
15338 This driver is also available as a module ( = code which can be
15339 inserted in and removed from the running kernel whenever you
15340 want). If you want to compile it as a module, say M here and read
15341 Documentation/modules.txt.
15343 PowerMac DMA sound support
15344 CONFIG_DMASOUND_AWACS
15345 If you want to use the internal audio of your PowerMac in Linux,
15346 answer Y to this question. This will provide a Sun-like /dev/audio,
15347 compatible with the Linux/i386 sound system. Otherwise, say N.
15349 This driver is also available as a module ( = code which can be
15350 inserted in and removed from the running kernel whenever you
15351 want). If you want to compile it as a module, say M here and read
15352 Documentation/modules.txt.
15354 Amiga DMA sound support
15355 CONFIG_DMASOUND_PAULA
15356 If you want to use the internal audio of your Amiga in Linux, answer
15357 Y to this question. This will provide a Sun-like /dev/audio,
15358 compatible with the Linux/i386 sound system. Otherwise, say N.
15360 This driver is also available as a module ( = code which can be
15361 inserted in and removed from the running kernel whenever you
15362 want). If you want to compile it as a module, say M here and read
15363 Documentation/modules.txt.
15366 CONFIG_DMASOUND_Q40
15367 If you want to use the internal audio of your Q40 in Linux, answer
15368 Y to this question. This will provide a Sun-like /dev/audio,
15369 compatible with the Linux/i386 sound system. Otherwise, say N.
15371 This driver is also available as a module ( = code which can be
15372 inserted in and removed from the running kernel whenever you
15373 want). If you want to compile it as a module, say M here and read
15374 Documentation/modules.txt.
15376 HP DCA serial support
15378 If you want to use the internal "DCA" serial ports on an HP300
15379 machine, say Y here.
15381 HP on-board LANCE support
15383 If you want to use the builtin "LANCE" Ethernet controller on an
15384 HP300 machine, say Y here.
15388 Say Y here to enable support for the "DIO" expansion bus used in
15389 HP300 machines. If you are using such a system you almost certainly
15394 There are four types of PowerPC chips supported. The more common
15395 types (601, 603, 604, 740, 750), the Motorola embedded versions
15396 (821, 823, 850, 855, 860), the IBM embedded versions (403 and
15397 405) and the high end 64 bit Power processors (Power 3, Power 4).
15398 Unless you are building a kernel for one of the embedded
15399 processor systems, or a 64 bit IBM RS/6000, choose 6xx. Note that
15400 the kernel runs in 32-bit mode even on 64-bit chips.
15404 Linux currently supports several different kinds of PowerPC-based
15405 machines: Apple Power Macintoshes and clones (such as the Motorola
15406 Starmax series), PReP (PowerPC Reference Platform) machines such as
15407 the Motorola PowerStack, Amiga Power-Up systems (APUS), CHRP and the
15408 embedded MBX boards from Motorola. Currently, a single kernel binary
15409 only supports one type or the other. However, there is very early
15410 work on support for CHRP, PReP and PowerMac's from a single binary.
15412 Power management support for PowerBooks
15414 This provides support for putting a PowerBook to sleep; it also
15415 enables media bay support. Power management works on the
15416 PB2400/3400/3500, Wallstreet, Lombard, and Bronze PowerBook G3. You
15417 must get the power management daemon, pmud, to make it work and you
15418 must have the /dev/pmu device (see the pmud README).
15420 Get pmud from ftp://linuxcare.com.au/pub/ppclinux/pmud/
15422 If you have a PowerBook, you should say Y.
15424 You may also want to compile the dma sound driver as a module and
15425 have it autoloaded. The act of removing the module shuts down the
15426 sound hardware for more power savings.
15428 Support for Open Firmware device tree in /proc
15429 CONFIG_PROC_DEVICETREE
15430 This option adds a device-tree directory under /proc which contains
15431 an image of the device tree that the kernel copies from Open
15432 Firmware. If unsure, say Y here.
15434 MESH (Power Mac internal SCSI) support
15436 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
15437 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
15438 other Power Macintoshes do). Say Y to include support for this SCSI
15439 adaptor. This driver is also available as a module called mesh.o
15440 ( = code which can be inserted in and removed from the running
15441 kernel whenever you want). If you want to compile it as a module,
15442 say M here and read Documentation/modules.txt.
15444 Maximum synchronous transfer rate
15445 CONFIG_SCSI_MESH_SYNC_RATE
15446 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
15447 drives a bus which is entirely internal to the machine (such as the
15448 7500, 7600, 8500, etc.), the MESH is capable of synchronous
15449 operation at up to 10 MB/s. On machines where the SCSI bus
15450 controlled by the MESH can have external devices connected, it is
15451 usually rated at 5 MB/s. 5 is a safe value here unless you know the
15452 MESH SCSI bus is internal only; in that case you can say 10. Say 0
15453 to disable synchronous operation.
15455 53C94 (Power Mac external SCSI) support
15456 CONFIG_SCSI_MAC53C94
15457 On Power Macintoshes (and clones) with two SCSI buses, the external
15458 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
15459 machines which only have one SCSI bus, such as the 7200, also use
15460 the 53C94. Say Y to include support for the 53C94.
15462 This driver is also available as a module called mac53c94.o ( = code
15463 which can be inserted in and removed from the running kernel
15464 whenever you want). If you want to compile it as a module, say M
15465 here and read Documentation/modules.txt.
15467 MACE (Power Mac Ethernet) support
15469 Power Macintoshes and clones with Ethernet built-in on the
15470 motherboard will usually use a MACE (Medium Access Control for
15471 Ethernet) interface. Say Y to include support for the MACE chip.
15473 This driver is also available as a module called mace.o ( = code
15474 which can be inserted in and removed from the running kernel
15475 whenever you want). If you want to compile it as a module, say M
15476 here and read Documentation/modules.txt.
15478 BMAC (G3 ethernet) support
15480 Say Y for support of BMAC Ethernet interfaces. These are used on G3
15483 This driver is also available as a module called bmac.o ( = code
15484 which can be inserted in and removed from the running kernel
15485 whenever you want). If you want to compile it as a module, say M
15486 here and read Documentation/modules.txt.
15488 GMAC (G4/iBook ethernet) support
15490 Say Y for support of GMAC Ethernet interfaces. These are used on G4
15491 and iBook computers.
15493 This driver is also available as a module called gmac.o ( = code
15494 which can be inserted in and removed from the running kernel
15495 whenever you want). If you want to compile it as a module, say M
15496 here and read Documentation/modules.txt.
15498 Symbios 53c885 (Synergy ethernet) support
15500 This is and Ethernet driver for the dual-function NCR 53C885
15501 SCSI/Ethernet controller.
15503 This driver is also available as a module called ncr885e.o ( = code
15504 which can be inserted in and removed from the running kernel
15505 whenever you want). If you want to compile it as a module, say M
15506 here and read Documentation/modules.txt.
15508 National DP83902AV (Oak ethernet) support
15510 Say Y if your machine has this type of Ethernet network card.
15512 This driver is also available as a module called oaknet.o ( = code
15513 which can be inserted in and removed from the running kernel
15514 whenever you want). If you want to compile it as a module, say M
15515 here and read Documentation/modules.txt.
15519 Support for audio/video capture and overlay devices and FM radio
15520 cards. The exact capabilities of each device vary. User tools for
15521 this are available from
15522 ftp://ftp.uk.linux.org/pub/linux/video4linux .
15524 If you are interested in writing a driver for such an audio/video
15525 device or user software interacting with such a driver, please read
15526 the file Documentation/video4linux/API.html.
15528 This driver is also available as a module called videodev.o ( = code
15529 which can be inserted in and removed from the running kernel
15530 whenever you want). If you want to compile it as a module, say M
15531 here and read Documentation/modules.txt.
15533 Video For Linux /proc file system information
15534 CONFIG_VIDEO_PROC_FS
15535 If you say Y here, you are able to access video device information
15538 To use this option, you have to check, that the "/proc file system
15539 support" (CONFIG_PROC_FS) is enabled too.
15541 AIMSlab RadioTrack (aka RadioReveal) support
15542 CONFIG_RADIO_RTRACK
15543 Choose Y here if you have one of these FM radio cards, and then fill
15544 in the port address below.
15546 Note that newer AIMSlab RadioTrack cards have a different chipset
15547 and are not supported by this driver. For these cards, use the
15548 RadioTrack II driver below.
15550 If you have a GemTeks combined (PnP) sound- and radio card you must
15551 use this driver as a module and setup the card with isapnptools. You
15552 must also pass the module a suitable io parameter, 0x248 has been
15553 reported to be used by these cards.
15555 In order to control your radio card, you will need to use programs
15556 that are compatible with the Video for Linux API. Information on
15557 this API and pointers to "v4l" programs may be found on the WWW at
15558 http://roadrunner.swansea.uk.linux.org/v4l.shtml . More information
15559 is contained in the file Documentation/video4linux/radiotrack.txt.
15561 If you want to compile this driver as a module ( = code which can be
15562 inserted in and removed from the running kernel whenever you want),
15563 say M here and read Documentation/modules.txt. The module will be
15564 called radio-aimslab.o.
15566 RadioTrack i/o port
15567 CONFIG_RADIO_RTRACK_PORT
15568 Enter either 0x30f or 0x20f here. The card default is 0x30f, if you
15569 haven't changed the jumper setting on the card.
15571 AIMSlab RadioTrack II support
15572 CONFIG_RADIO_RTRACK2
15573 Choose Y here if you have this FM radio card, and then fill in the
15574 port address below.
15576 In order to control your radio card, you will need to use programs
15577 that are compatible with the Video for Linux API. Information on
15578 this API and pointers to "v4l" programs may be found on the WWW at
15579 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15581 If you want to compile this driver as a module ( = code which can be
15582 inserted in and removed from the running kernel whenever you want),
15583 say M here and read Documentation/modules.txt. The module will be
15584 called radio-rtrack2.o.
15586 RadioTrack II i/o port
15587 CONFIG_RADIO_RTRACK2_PORT
15588 Enter either 0x30c or 0x20c here. The card default is 0x30c, if you
15589 haven't changed the jumper setting on the card.
15591 Aztech/Packard Bell Radio
15592 CONFIG_RADIO_AZTECH
15593 Choose Y here if you have one of these FM radio cards, and then fill
15594 in the port address below.
15596 In order to control your radio card, you will need to use programs
15597 that are compatible with the Video for Linux API. Information on
15598 this API and pointers to "v4l" programs may be found on the WWW at
15599 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15601 If you want to compile this driver as a module ( = code which can be
15602 inserted in and removed from the running kernel whenever you want),
15603 say M here and read Documentation/modules.txt. The module will be
15604 called radio-aztech.o.
15606 Aztech/Packard Bell radio card i/o port
15607 CONFIG_RADIO_AZTECH_PORT
15608 Enter either 0x350 or 0x358 here. The card default is 0x350, if you
15609 haven't changed the setting of jumper JP3 on the card. Removing the
15610 jumper sets the card to 0x358.
15612 ADS Cadet AM/FM Radio Tuner Card
15614 Choose Y here if you have one of these AM/FM radio cards, and then
15615 fill in the port address below.
15617 In order to control your radio card, you will need to use programs
15618 that are compatible with the Video for Linux API. Information on
15619 this API and pointers to "v4l" programs may be found on the WWW at
15620 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15622 Further documentation on this driver can be found on the WWW at
15623 http://linux.blackhawke.net/cadet.html .
15625 If you want to compile this driver as a module ( = code which can be
15626 inserted in and removed from the running kernel whenever you want),
15627 say M here and read Documentation/modules.txt. The module will be
15628 called radio-cadet.o.
15631 CONFIG_RADIO_SF16FMI
15632 Choose Y here if you have one of these FM radio cards, and then fill
15633 in the port address below.
15635 In order to control your radio card, you will need to use programs
15636 that are compatible with the Video for Linux API. Information on
15637 this API and pointers to "v4l" programs may be found on the WWW at
15638 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15640 If you want to compile this driver as a module ( = code which can be
15641 inserted in and removed from the running kernel whenever you want),
15642 say M here and read Documentation/modules.txt. The module will be
15643 called radio-sf16fmi.o
15645 SF16FMI I/O port (0x284 or 0x384)
15646 CONFIG_RADIO_SF16FMI_PORT
15647 Enter the I/O port of your SF16FMI radio card.
15650 CONFIG_RADIO_TYPHOON
15651 Choose Y here if you have one of these FM radio cards, and then fill
15652 in the port address and the frequency used for muting below.
15654 In order to control your radio card, you will need to use programs
15655 that are compatible with the Video for Linux API. Information on
15656 this API and pointers to "v4l" programs may be found on the WWW at
15657 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15659 If you want to compile this driver as a module ( = code which can be
15660 inserted in and removed from the running kernel whenever you want),
15661 say M here and read Documentation/modules.txt. The module will be
15662 called radio-typhoon.o
15664 Support for /proc/radio-typhoon
15665 CONFIG_RADIO_TYPHOON_PROC_FS
15666 Say Y here if you want the typhoon radio card driver to write
15667 status information (frequency, volume, muted, mute frequency,
15668 base address) to /proc/radio-typhoon. The file can be viewed with
15669 your favorite pager (i.e. use "more /proc/radio-typhoon" or "less
15670 /proc/radio-typhoon" or simply "cat /proc/radio-typhoon").
15672 Typhoon I/O port (0x316 or 0x336)
15673 CONFIG_RADIO_TYPHOON_PORT
15674 Enter the I/O port of your Typhoon or EcoRadio radio card.
15676 Typhoon frequency set when muting the device (kHz)
15677 CONFIG_RADIO_TYPHOON_MUTEFREQ
15678 Enter the frequency used for muting the radio. The device is never
15679 completely silent. If the volume is just turned down, you can still
15680 hear silent voices and music. For that reason, the frequency of the
15681 radio device is set to the frequency you can enter here whenever
15682 the device is muted. There should be no local radio station at that
15686 CONFIG_RADIO_ZOLTRIX
15687 Choose Y here if you have one of these FM radio cards, and then fill
15688 in the port address below.
15690 In order to control your radio card, you will need to use programs
15691 that are compatible with the Video for Linux API. Information on
15692 this API and pointers to "v4l" programs may be found on the WWW at
15693 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15695 If you want to compile this driver as a module ( = code which can be
15696 inserted in and removed from the running kernel whenever you want),
15697 say M here and read Documentation/modules.txt. The module will be
15698 called radio-zoltrix.o
15700 ZOLTRIX I/O port (0x20c or 0x30c)
15701 CONFIG_RADIO_ZOLTRIX_PORT
15702 Enter the I/O port of your Zoltrix radio card.
15704 IIC on parallel port
15706 I2C is a simple serial bus system used in many micro controller
15707 applications. Saying Y here will allow you to use your parallel port
15708 as an I2C interface.
15710 If you want to compile this driver as a module ( = code which can be
15711 inserted in and removed from the running kernel whenever you want),
15712 say M here and read Documentation/modules.txt. The module will be
15713 called i2c-parport.o.
15716 CONFIG_RADIO_MIROPCM20
15717 Choose Y here if you have this FM radio card. You also need to say Y
15718 to "ACI mixer (miroPCM12/PCM20)" (in "additional low level sound
15719 drivers") for this to work.
15721 In order to control your radio card, you will need to use programs
15722 that are compatible with the Video for Linux API. Information on
15723 this API and pointers to "v4l" programs may be found on the WWW at
15724 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15726 If you want to compile this driver as a module ( = code which can be
15727 inserted in and removed from the running kernel whenever you want),
15728 say M here and read Documentation/modules.txt. The module will be
15729 called radio-miropcm20.o
15732 CONFIG_RADIO_GEMTEK
15733 Choose Y here if you have this FM radio card, and then fill in the
15734 port address below.
15736 In order to control your radio card, you will need to use programs
15737 that are compatible with the Video for Linux API. Information on
15738 this API and pointers to "v4l" programs may be found on the WWW at
15739 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15741 If you want to compile this driver as a module ( = code which can be
15742 inserted in and removed from the running kernel whenever you want),
15743 say M here and read Documentation/modules.txt. The module will be
15744 called radio-gemtek.o.
15747 CONFIG_RADIO_GEMTEK_PORT
15748 Enter either 0x20c, 0x30c, 0x24c or 0x34c here. The card default is
15749 0x34c, if you haven't changed the jumper setting on the card. On
15750 Sound Vision 16 Gold PnP with FM Radio (ESS1869+FM Gemtek), the i/o
15753 PlanB Video-In for PowerMacs
15755 PlanB is the V4L driver for the PowerMac 7x00/8x00 series video
15756 input hardware. If you want to experiment with this, say Y.
15757 Otherwise, or if you don't understand a word, say N.
15758 See http://www.cpu.lu/~mlan/planb.html for more info.
15760 Saying M will compile this driver as a module (planb.o).
15762 TerraTec ActiveRadio
15763 CONFIG_RADIO_TERRATEC
15764 Choose Y here if you have this FM radio card, and then fill in the
15765 port address below. (TODO)
15767 Note: This driver is in its early stages. Right now volume and
15768 frequency control and muting works at least for me, but
15769 unfortunately i have not found anybody who wants to use this card
15770 with Linux. So if it is this what YOU are trying to do right now,
15771 PLEASE DROP ME A NOTE!! Rolf Offermanns (rolf@offermanns.de)
15773 In order to control your radio card, you will need to use programs
15774 that are compatible with the Video for Linux API. Information on
15775 this API and pointers to "v4l" programs may be found on the WWW at
15776 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15778 If you want to compile this driver as a module ( = code which can be
15779 inserted in and removed from the running kernel whenever you want),
15780 say M here and read Documentation/modules.txt. The module will be
15781 called radio-terratec.o.
15783 Terratec i/o port (normally 0x590)
15784 CONFIG_RADIO_TERRATEC_PORT
15785 Fill in the i/o port of your TerraTec FM radio card. If unsure, go
15789 # Zoran ZR36057/36060 support
15790 # CONFIG_VIDEO_ZORAN
15792 # Include support for Iomega Buz
15795 Trust FM radio card
15797 This is a driver for the Trust FM radio cards. Say Y if you have
15798 such a card and want to use it under Linux.
15800 This driver is also available as a module called radio-trust.o ( =
15801 code which can be inserted in and removed from the running kernel
15802 whenever you want). If you want to compile it as a module, say M
15803 here and read Documentation/modules.txt.
15805 Trust i/o port (usually 0x350 or 0x358)
15806 CONFIG_RADIO_TRUST_PORT
15807 Enter the i/o port of your Trust FM radio card. If unsure, try the
15808 values "0x350" or "0x358".
15810 BT848 Video For Linux
15812 Support for BT848 based frame grabber/overlay boards. This includes
15813 the Miro, Hauppauge and STB boards. Please read the material in
15814 Documentation/video4linux/bttv for more information.
15816 If you say Y or M here, you need to say Y or M to "I2C support" and
15817 "I2C bit-banging interfaces" in the character device section.
15819 This driver is available as a module called bttv.o ( = code
15820 which can be inserted in and removed from the running kernel
15821 whenever you want). If you want to compile it as a module, say M
15822 here and read Documentation/modules.txt.
15824 ZR36120/36125 Video for Linux
15825 CONFIG_VIDEO_ZR36120
15826 Support for ZR36120/ZR36125 based frame grabber/overlay boards.
15827 This includes the Victor II, WaveWatcher, Video Wonder, Maxi-TV,
15828 and Buster boards. Please read the material in
15829 Documentation/video4linux/zr36120.txt for more information.
15831 This driver is also available as a module called zr36120.o ( = code
15832 which can be inserted in and removed from the running kernel
15833 whenever you want). If you want to compile it as a module, say M
15834 here and read Documentation/modules.txt.
15836 SAA5249 Teletext processor
15837 CONFIG_VIDEO_SAA5249
15838 Support for I2C bus based teletext using the SAA5249 chip. At the
15839 moment this is only useful on some European WinTV cards.
15841 This driver is also available as a module called saa5249.o ( = code
15842 which can be inserted in and removed from the running kernel
15843 whenever you want). If you want to compile it as a module, say M
15844 here and read Documentation/modules.txt.
15846 Quickcam BW Video For Linux
15847 CONFIG_VIDEO_BWQCAM
15848 Say Y have if you the black and white version of the QuickCam
15849 camera. See the next option for the color version.
15851 This driver is also available as a module called bw-qcam.o ( = code
15852 which can be inserted in and removed from the running kernel
15853 whenever you want). If you want to compile it as a module, say M
15854 here and read Documentation/modules.txt.
15856 Colour QuickCam Video For Linux
15858 This is the video4linux driver for the colour version of the
15859 Connectix Quickcam. If you have one of these cameras, say Y here,
15860 otherwise say N. This driver does not work with the original
15861 monochrome Quickcam, Quickcam VC or QuickClip. It is also available
15862 as a module (c-qcam.o). Read Documentation/video4linux/CQcam.txt for
15865 CPiA Video For Linux
15867 This is the video4linux driver for cameras based on Vision's CPiA
15868 (Colour Processor Interface ASIC), such as the Creative Labs Video
15869 Blaster Webcam II. If you have one of these cameras, say Y here
15870 and select parallel port and/or USB lowlevel support below,
15871 otherwise say N. This will not work with the Creative Webcam III.
15873 Please read Documentation/video4linux/README.cpia for more
15876 This driver is also available as a module (cpia.o).
15878 CPiA Parallel Port Lowlevel Support
15879 CONFIG_VIDEO_CPIA_PP
15880 This is the lowlevel parallel port support for cameras based on
15881 Vision's CPiA (Colour Processor Interface ASIC), such as the
15882 Creative Webcam II. If you have the parallel port version of one
15883 of these cameras, say Y here, otherwise say N. It is also available
15884 as a module (cpia_pp.o).
15886 CPiA USB Lowlevel Support
15887 CONFIG_VIDEO_CPIA_USB
15888 This is the lowlevel USB support for cameras based on Vision's CPiA
15889 (Colour Processor Interface ASIC), such as the Creative Webcam II.
15890 If you have the USB version of one of these cameras, say Y here,
15891 otherwise say N. This will not work with the Creative Webcam III.
15892 It is also available as a module (cpia_usb.o).
15894 Mediavision Pro Movie Studio Video For Linux
15896 Say Y if you have such a thing. This driver is also available as a
15897 module called pms.o ( = code which can be inserted in and removed
15898 from the running kernel whenever you want). If you want to compile
15899 it as a module, say M here and read Documentation/modules.txt.
15901 SAB3036 tuner support
15903 Say Y here to include support for Philips SAB3036 compatible tuners.
15904 If in doubt, say N.
15906 Compaq SMART2 support
15908 This is the driver for Compaq Smart Array controllers.
15909 Everyone using these boards should say Y here.
15910 See the file Documentation/cpqarray.txt for the current list of
15911 boards supported by this driver, and for further information
15912 on the use of this driver.
15919 This selects what ARM system you wish to build the kernel for. It
15920 also selects to some extent the CPU type. If you are unsure what
15921 to set this option to, please consult any information supplied with
15924 Include support for the CATS
15926 Say Y here if you intend to run this kernel on the CATS.
15928 Saying N will reduce the size of the Footbridge kernel.
15930 Include support for the EBSA285
15931 CONFIG_ARCH_EBSA285
15932 Say Y here if you intend to run this kernel on the EBSA285 card
15933 in host ("central function") mode.
15935 Saying N will reduce the size of the Footbridge kernel.
15937 Include support for the LinkUp Systems L7200 SDB
15939 Say Y here if you intend to run this kernel on a LinkUp Systems
15940 L7200 Software Development Board which uses an ARM720T processor.
15941 Information on this board can be obtained at:
15943 http://www.linkupsys.com/
15945 If you have any questions or comments about the Linux kernel port
15946 to this board, send e-mail to sjhill@cotw.com
15948 Include support for the NetWinder
15949 CONFIG_ARCH_NETWINDER
15950 Say Y here if you intend to run this kernel on the Rebel.COM
15951 NetWinder. Information about this machine can be found at:
15953 http://www.netwinder.org/
15955 Saying N will reduce the size of the Footbridge kernel.
15957 Include support for the Compaq Personal Server
15958 CONFIG_ARCH_PERSONAL_SERVER
15959 Say Y here if you intend to run this kernel on the Compaq
15962 Saying N will reduce the size of the Footbridge kernel.
15964 The Compaq Personal Server is not available for purchase.
15965 There are no product plans beyond the current research
15966 prototypes at this time. Information is available at:
15968 http://crl.research.compaq.com/projects/personalserver
15970 If you have any questions or comments about the Compaq Personal
15971 Server, send e-mail to skiff@crl.dec.com
15973 Include support for Assabet
15974 CONFIG_SA1100_ASSABET
15975 Say Y here if you are using the Intel(R) StrongARM(R) SA-1110
15976 Microprocessor Development Board (also known as the Assabet).
15978 Include support for Neponset
15979 CONFIG_ASSABET_NEPONSET
15980 Say Y here if you are using the Intel(R) StrongARM(R) SA-1110
15981 Microprocessor Development Board (Assabet) with the SA-1111
15982 Development Board (Nepon).
15984 Include support for the Compaq iPAQ H3600 (Bitsy)
15985 CONFIG_SA1100_BITSY
15986 Say Y here if you intend to run this kernel on the Compaq iPAQ
15987 H3600 handheld computer. Information about this machine and the
15988 Linux port to this machine can be found at:
15990 http://www.handhelds.org/Compaq/index.html#iPAQ_H3600
15991 http://www.compaq.com/products/handhelds/pocketpc/
15993 Include support for Brutus
15994 CONFIG_SA1100_BRUTUS
15995 Say Y here if you are using the Intel(R) StrongARM(R) SA-1100
15996 Microprocessor Development Board (also known as the Brutus).
15998 Include support for LART
16000 Say Y here if you are using the Linux Advanced Radio Terminal
16001 (also known as the LART). See http://www.lart.tudelft.nl/ for
16002 information on the LART.
16004 Include support for ThinClient
16005 CONFIG_SA1100_THINCLIENT
16006 Say Y here if you are using an Applied Data Systems Intel(R)
16007 StrongARM(R) SA-1100 based Thin Client SBC. See
16008 http://www.flatpanels.com/ for information on this system.
16010 Include support for GraphicsClient
16011 CONFIG_SA1100_GRAPHICSCLIENT
16012 Say Y here if you are using an Applied Data Systems Intel(R)
16013 StrongARM(R) SA-1100 based Graphics Client SBC. See
16014 http://www.flatpanels.com/ for information on this system.
16016 Include support for Victor
16017 CONFIG_SA1100_VICTOR
16018 Say Y here if you are using a Visu Aide Intel(R) StrongARM(R)
16019 SA-1100 based Victor Digital Talking Book Reader. See
16020 http://www.visuaide.com/pagevictor.en.html for information on
16025 Say Y to include the NWFPE floating point emulator in the kernel.
16026 This is necessary to run most binaries. Linux does not currently
16027 support floating point hardware so you need to say Y here even if
16028 your machine has an FPA or floating point co-processor podule.
16030 It is also possible to say M to build the emulator as a module
16031 (nwfpe.o) or indeed to leave it out altogether. However, unless you
16032 know what you are doing this can easily render your machine
16033 unbootable. Saying Y is the safe option.
16035 You may say N here if you are going to load the Acorn FPEmulator
16036 early in the bootup.
16038 DS1620 Thermometer support
16040 Say Y here to include support for the thermal management hardware
16041 found in the NetWinder. This driver allows the user to control the
16042 temperature set points and to read the current temperature.
16044 It is also possible to say M here to build it as a module (ds1620.o)
16045 It is recommended to be used on a NetWinder, but it is not a
16048 Verbose kernel error messages
16049 CONFIG_DEBUG_ERRORS
16050 This option controls verbose debugging information which can be
16051 printed when the kernel detects an internal error. This debugging
16052 information is useful to kernel hackers when tracking down problems,
16053 but mostly meaningless to other people. It's safe to say Y unless
16054 you are concerned with the code size or don't want to see these
16057 Compile kernel with frame pointer
16058 CONFIG_FRAME_POINTER
16059 If you say Y here, the resulting kernel will be slightly larger and
16060 slower, but it will give useful debugging information. If you don't
16061 debug the kernel, you can say N.
16063 User fault debugging
16065 When a user program crashes due to an exception, the kernel can
16066 print a brief message explaining what the problem was. This is
16067 sometimes helpful for debugging but serves no purpose on a
16068 production system. Most people should say N here.
16070 Include gdb debugging information in kernel binary
16072 Say Y here to include source-level debugging information in the
16073 `vmlinux' binary image. This is handy if you want to use gdb or
16074 addr2line to debug the kernel. It has no impact on the in-memory
16075 footprint of the running kernel but it can increase the amount of
16076 time and disk space needed for compilation of the kernel. If in
16079 Kernel low-level debugging functions
16081 Say Y here to include definitions of printascii, printchar, printhex
16082 in the kernel. This is helpful if you are debugging code that
16083 executes before the console is initialized.
16085 Kernel low-level debugging messages via footbridge serial port
16086 CONFIG_DEBUG_DC21285_PORT
16087 Say Y here if you want the low-level print routines to direct their
16088 output to the serial port in the DC21285 (Footbridge).
16090 Split initialisation functions into discardable section
16091 CONFIG_TEXT_SECTIONS
16092 If you say Y here, kernel code that is only used during
16093 initialisation is collected into a special area of the kernel so
16094 that it can be discarded and the memory reclaimed when
16095 initialisation is complete. In addition, if the kernel you wish to
16096 build is able to run on multiple architectures, it allows the unused
16097 code to be discarded. Some versions of binutils, however, have a bug
16098 that causes the kernel to crash during startup when this option is
16099 enabled. Say Y unless you experience problems that you suspect may
16102 Disable pgtable cache (EXPERIMENTAL)
16103 CONFIG_NO_PGT_CACHE
16104 Normally the kernel maintains a `quicklist' of preallocated
16105 pagetable structures in order to increase performance. On machines
16106 with very few pages this may however be a loss. Say Y here to
16107 disable the pgtable cache.
16109 RISC OS personality
16111 Say Y here to include the kernel code necessary if you want to run
16112 Acorn RISC OS/Arthur binaries under Linux. This code is still very
16113 experimental; if this sounds frightening, say N and sleep in peace.
16114 You can also say M here to compile this support as a module (which
16115 will be called arthur.o).
16117 Initial kernel command line
16119 On some architectures (EBSA110 and CATS), there is currently no way
16120 for the boot loader to pass arguments to the kernel. For these
16121 architectures, you should supply some command-line options at build
16122 time by entering them here. As a minimum, you should specify the
16123 memory size and the root device (e.g., mem=64M root=/dev/nfs)
16125 Hardware alignment trap (EXPERIMENTAL)
16126 CONFIG_ALIGNMENT_TRAP
16127 ARM processors can not fetch/store information which is not
16128 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
16129 address divisible by 4. On 32-bit ARM processors, these non-aligned
16130 fetch/store instructions will be emulated in software if you say
16131 here, which has a severe performance impact. This is necessary for
16132 correct operation of some network protocols. With an IP-only
16133 configuration it is safe to say N, otherwise say Y.
16135 21285 serial port support
16136 CONFIG_SERIAL_21285
16137 If you have a machine based on a 21285 (Footbridge) StrongARM/PCI
16138 bridge you can enable its onboard serial port by enabling this
16139 option. The device has major ID 4, minor 64.
16141 Console on 21285 serial port
16142 CONFIG_SERIAL_21285_CONSOLE
16143 If you have enabled the serial port on the 21285 footbridge you can
16144 make it the console by answering Y to this option.
16146 L7200 serial port support
16147 CONFIG_SERIAL_L7200
16148 If you have a LinkUp Systems L7200 board you can enable its two
16149 onboard serial ports by enabling this option. The device numbers
16150 are major ID 4 with minor 64 and 65 respectively.
16152 Console on L7200 serial port
16153 CONFIG_SERIAL_L7200_CONSOLE
16154 If you have enabled the serial ports on the L7200 development board
16155 you can make the first serial port the console by answering Y to
16159 CONFIG_HOST_FOOTBRIDGE
16160 The 21285 Footbridge chip can operate in either `host mode' or
16161 `add-in' mode. Say Y if your 21285 is in host mode, and therefore
16162 is the configuration master, otherwise say N. This must not be
16163 set to Y if the card is used in 'add-in' mode.
16165 MFM hard disk support
16167 Support the MFM hard drives on the Acorn Archimedes both
16168 on-board the A4x0 motherboards and via the Acorn MFM podules.
16169 Drives up to 64MB are supported. If you haven't got one of these
16170 machines or drives just say N.
16172 Old Archimedes floppy (1772) support
16173 CONFIG_BLK_DEV_FD1772
16174 Support the floppy drive on the Acorn Archimedes (A300, A4x0, A540,
16175 R140 and R260) series of computers; it supports only 720K floppies
16176 at the moment. If you don't have one of these machines just answer
16179 Autodetect hard drive geometry
16180 CONFIG_BLK_DEV_MFM_AUTODETECT
16181 If you answer Y, the MFM code will attempt to automatically detect
16182 the cylinders/heads/sectors count on your hard drive. WARNING: This
16183 sometimes doesn't work and it also does some dodgy stuff which
16184 potentially might damage your drive.
16186 NetWinder /dev/flash support
16188 If you say Y here and create a character device /dev/flash with
16189 major 10 and minor 160 you can manipulate the flash ROM containing
16190 the NetWinder firmware. Be careful as accidentally overwriting the
16191 flash contents can render your computer unbootable. On no account
16192 allow random users access to this device. :-)
16194 This driver is also available as a module ( = code which can be
16195 inserted in and removed from the running kernel whenever you want).
16196 The module will be called nwflash.o. If you want to compile it as a
16197 module, say M here and read Documentation/modules.txt.
16199 If you're not sure, say N.
16201 Footbridge internal watchdog
16202 CONFIG_21285_WATCHDOG
16203 The Intel Footbridge chip contains a builtin watchdog circuit. Say Y
16204 here if you wish to use this. Alternatively say M to compile the
16205 driver as a module, which will be called wdt285.o.
16207 This driver does not work on all machines. In particular, early CATS
16208 boards have hardware problems that will cause the machine to simply
16209 lock up if the watchdog fires.
16211 "If in doubt, leave it out" - say N.
16213 NetWinder WB977 watchdog
16214 CONFIG_977_WATCHDOG
16215 Say Y here to include support for the WB977 watchdog included in
16216 NetWinder machines. Alternatively say M to compile the driver as
16217 a module, which will be called wdt977.o.
16219 Not sure? It's safe to say N.
16221 IrDA subsystem support
16223 Say Y here if you want to build support for the IrDA (TM) protocols.
16224 The Infrared Data Associations (tm) specifies standards for wireless
16225 infrared communication and is supported by most laptops and PDA's.
16227 To use Linux support for the IrDA (tm) protocols, you will also need
16228 some user-space utilities like the irmanager and probably irattach
16229 as well. For more information, see the file
16230 Documentation/networking/irda.txt. You also want to read the
16231 IR-HOWTO, available at http://www.linuxdoc.org/docs.html#howto .
16233 This support is also available as a module called irda.o. If you
16234 want to compile it as a module, say M here and read
16235 Documentation/modules.txt.
16237 IrDA Cache last LSAP
16238 CONFIG_IRDA_CACHE_LAST_LSAP
16239 Say Y here if you want IrLMP to cache the last LSAP used. This makes
16240 sense since most frames will be sent/received on the same
16241 connection. Enabling this option will save a hash-lookup per frame.
16246 CONFIG_IRDA_FAST_RR
16247 Say Y here is you want IrLAP to send fast RR (Receive Ready) frames
16248 when acting as a primary station. This will make IrLAP send out a RR
16249 frame immediately when receiving a frame if its own transmit queue
16250 is currently empty. This will give a lot of speed improvement when
16251 receiving much data since the secondary station will not have to
16252 wait the max. turn around time before it is allowed to transmit the
16253 next time. If the transmit queue of the secondary is also empty the
16254 primary will back off waiting longer for sending out the RR frame
16255 until the timeout reaches the normal value. Enabling this option
16256 will make the IR-diode burn more power and thus reduce your battery
16263 Say Y here if you want the IrDA subsystem to write debug information
16264 to your syslog. You can change the debug level in
16265 /proc/sys/net/irda/debug
16267 If unsure, say Y (since it makes it easier to find the bugs).
16269 IrLAP Compression support
16270 CONFIG_IRDA_COMPRESSION
16271 Compression is _not_ part of the IrDA(tm) protocol specification,
16272 but it's working great! Linux is the first to try out compression
16273 support at the IrLAP layer. This means that you will only benefit
16274 from compression if you are running a Linux <-> Linux configuration.
16276 If you say Y here, you also need to say Y or M to a compression
16279 IrLAP Deflate Compression Protocol (EXPERIMENTAL)
16280 CONFIG_IRDA_DEFLATE
16281 Say Y here if you want to build support for the Deflate compression
16282 protocol. The deflate compression (GZIP) is exactly
16283 the same as the one used by the PPP protocol.
16285 If you want to compile this compression support as a module, say M
16286 here and read Documentation/modules.txt. The module will be called
16291 Say Y here if you want to build support for the IrLAN protocol. If
16292 you want to compile it as a module (irlan.o), say M here and read
16293 Documentation/modules.txt. IrLAN emulates an Ethernet and makes it
16294 possible to put up a wireless LAN using infrared beams.
16296 The IrLAN protocol can be used to talk with infrared access points
16297 like the HP NetbeamIR, or the ESI JetEye NET. You can also connect
16298 to another Linux machine running the IrLAN protocol for ad-hoc
16303 Say Y here if you want to build support for the IrCOMM protocol. If
16304 you want to compile it as a module (you will get ircomm.o and
16305 ircomm-tty.o), say M here and read Documentation/modules.txt. IrCOMM
16306 implements serial port emulation, and makes it possible to use all
16307 existing applications that understands TTY's with an infrared link.
16308 Thus you should be able to use application like PPP, minicom and
16309 others. Enabling this option will create two modules called ircomm
16312 IrTTY IrDA Device Driver
16314 Say Y here if you want to build support for the IrTTY line
16315 discipline. If you want to compile it as a module (irtty.o), say M
16316 here and read Documentation/modules.txt. IrTTY makes it possible to
16317 use Linux's own serial driver for all IrDA ports that are 16550
16318 compatible. Most IrDA chips are 16550 compatible so you should
16319 probably say Y to this option. Using IrTTY will however limit the
16320 speed of the connection to 115200 bps (IrDA SIR mode)
16324 IrPORT IrDA Device Driver
16326 Say Y here if you want to build support for the IrPORT IrDA device
16327 driver. If you want to compile it as a module (irport.o), say M here
16328 and read Documentation/modules.txt. IrPORT can be used instead of
16329 IrTTY and sometimes this can be better. One example is if your IrDA
16330 port does not have echo-canceling, which will work OK with IrPORT
16331 since this driver is working in half-duplex mode only. You don't
16332 need to use irattach with IrPORT, but you just insert it the same
16333 way as FIR drivers (insmod irport io=0x3e8 irq=11). Notice that
16334 IrPORT is a SIR device driver which means that speed is limited to
16339 Winbond W83977AF IrDA Device Driver
16341 Say Y here if you want to build IrDA support for the Winbond
16342 W83977AF super-io chipset. This driver should be used for the IrDA
16343 chipset in the Corel NetWinder. The driver supports SIR, MIR and FIR
16346 If you want to compile it as a module, say M here and read
16347 Documentation/modules.txt. The module will be called w83977af_ir.o.
16349 NSC PC87108 IrDA Device Driver
16351 Say Y here if you want to build support for the NSC PC87108 and
16352 PC87338 IrDA chipsets. This driver supports SIR,
16353 MIR and FIR (4Mbps) speeds.
16355 If you want to compile it as a module, say M here and read
16356 Documentation/modules.txt. The module will be called nsc-ircc.o.
16358 Toshiba Type-O IR Port Device Driver
16360 Say Y here if you want to build support for the Toshiba Type-O IR
16361 chipset. This chipset is used by the Toshiba Libretto 100CT, and
16362 many more laptops. If you want to compile it as a module, say M here
16363 and read Documentation/modules.txt. The module will be called
16366 SMC IrCC (Experimental)
16367 CONFIG_SMC_IRCC_FIR
16368 Say Y here if you want to build support for the SMC Infrared
16369 Communications Controller. It is used in the Fujitsu Lifebook 635t
16370 and Sony PCG-505TX. If you want to compile it as a module, say M
16371 here and read Documentation/modules.txt. The module will be called
16374 Serial dongle support
16376 Say Y here if you have an infrared device that connects to your
16377 computer's serial port. These devices are called dongles. Then say Y
16378 or M to the driver for your particular dongle below.
16380 Note that the answer to this question won't directly affect the
16381 kernel: saying N will just cause this configure script to skip all
16382 the questions about serial dongles.
16384 ESI JetEye PC Dongle
16386 Say Y here if you want to build support for the Extended Systems
16387 JetEye PC dongle. If you want to compile it as a module, say M here
16388 and read Documentation/modules.txt. The ESI dongle attaches to the
16389 normal 9-pin serial port connector, and can currently only be used
16390 by IrTTY. To activate support for ESI dongles you will have to
16391 start irattach like this: "irattach -d esi".
16393 ACTiSYS IR-220L and IR220L+ dongle
16394 CONFIG_ACTISYS_DONGLE
16395 Say Y here if you want to build support for the ACTiSYS
16396 IR-220L and IR220L+ dongles. If you want to compile it as a module,
16397 say M here and read Documentation/modules.txt. The ACTiSYS dongles
16398 attaches to the normal 9-pin serial port connector, and can
16399 currently only be used by IrTTY. To activate support for ACTiSYS
16400 dongles you will have to start irattach like this:
16401 "irattach -d actisys" or "irattach -d actisys+".
16403 Tekram IrMate 210B dongle
16404 CONFIG_TEKRAM_DONGLE
16405 Say Y here if you want to build support for the Tekram IrMate 210B
16406 dongle. If you want to compile it as a module, say M here
16407 and read Documentation/modules.txt. The Tekram dongle attaches to
16408 the normal 9-pin serial port connector, and can currently only be
16409 used by IrTTY. To activate support for Tekram dongles you will have
16410 to start irattach like this: "irattach -d tekram".
16412 Greenwich GIrBIL dongle
16413 CONFIG_GIRBIL_DONGLE
16414 Say Y here if you want to build support for the Greenwich GIrBIL
16415 dongle. If you want to compile it as a module, say M here and read
16416 Documentation/modules.txt. The Greenwich dongle attaches to the
16417 normal 9-pin serial port connector, and can currently only be used
16418 by IrTTY. To activate support for Greenwich dongles you will have to
16419 insert "irattach -d girbil" in the /etc/irda/drivers script.
16421 Parallax Litelink dongle
16422 CONFIG_LITELINK_DONGLE
16423 Say Y here if you want to build support for the Parallax Litelink
16424 dongle. If you want to compile it as a module, say M here and read
16425 Documentation/modules.txt. The Parallax dongle attaches to the
16426 normal 9-pin serial port connector, and can currently only be used
16427 by IrTTY. To activate support for Parallax dongles you will have to
16428 start irattach like this "irattach -d litelink".
16431 CONFIG_OLD_BELKIN_DONGLE
16432 Say Y here if you want to build support for the Adaptec Airport 1000
16433 and 2000 dongles. If you want to compile it as a module, say M here
16434 and read Documentation/modules.txt. The module will be called
16435 old_belkin.o. Some information is contained in the comments at the
16436 top of drivers/net/irda/old_belkin.c.
16438 VME (Motorola and BVM) support
16440 Say Y here if you want to build a kernel for a 680x0 based VME
16441 board. Boards currently supported include Motorola boards MVME162,
16442 MVME166, MVME167, MVME172, and MVME177. BVME4000 and BVME6000
16443 boards from BVM Ltd are also supported.
16445 MVME162, 166 and 167 support
16447 Say Y to include support for Motorola VME boards. This will build a
16448 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
16449 MVME177 boards. If you select this option you will have to select
16450 the appropriate drivers for SCSI, Ethernet and serial ports later
16453 BVME4000 and BVME6000 support
16455 Say Y to include support for VME boards from BVM Ltd. This will
16456 build a kernel which can run on BVME4000 and BVME6000 boards. If
16457 you select this option you will have to select the appropriate
16458 drivers for SCSI, Ethernet and serial ports later on.
16460 Use write-through caching for 68060 supervisor accesses
16461 CONFIG_060_WRITETHROUGH
16462 The 68060 generally uses copyback caching of recently accessed data.
16463 Copyback caching means that memory writes will be held in an on-chip
16464 cache and only written back to memory some time later. Saying Y
16465 here will force supervisor (kernel) accesses to use writethrough
16466 caching. Writethrough caching means that data is written to memory
16467 straight away, so that cache and memory data always agree.
16468 Writethrough caching is less efficient, but is needed for some
16469 drivers on 68060 based systems where the 68060 bus snooping signal
16470 is hardwired on. The 53c710 SCSI driver is known to suffer from
16473 NCR53C710 SCSI driver for MVME16x
16474 CONFIG_MVME16x_SCSI
16475 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
16476 SCSI controller chip. Almost everyone using one of these boards
16477 will want to say Y to this question.
16479 NCR53C710 SCSI driver for BVME6000
16480 CONFIG_BVME6000_SCSI
16481 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
16482 SCSI controller chip. Almost everyone using one of these boards
16483 will want to say Y to this question.
16485 MVME16x Ethernet support
16487 This is the driver for the Ethernet interface on the Motorola
16488 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
16489 driver for this chip in your kernel. If you want to compile it as
16490 a module, say M here and read Documentation/modules.txt.
16492 BVME6000 Ethernet support
16493 CONFIG_BVME6000_NET
16494 This is the driver for the Ethernet interface on BVME4000 and
16495 BVME6000 VME boards. Say Y here to include the driver for this chip
16496 in your kernel. If you want to compile it as a module, say M here
16497 and read Documentation/modules.txt.
16499 CD2401 support for MVME166/7 serial ports
16501 This is the driver for the serial ports on the Motorola MVME166,
16502 167, and 172 boards. Everyone using one of these boards should say
16505 SCC support for MVME162 serial ports
16507 This is the driver for the serial ports on the Motorola MVME162 and
16508 172 boards. Everyone using one of these boards should say Y here.
16510 SCC support for BVME6000 serial ports
16511 CONFIG_BVME6000_SCC
16512 This is the driver for the serial ports on the BVME4000 and BVME6000
16513 boards from BVM Ltd. Everyone using one of these boards should say
16516 7-Segment Display support
16518 This is the driver for the 7-segment display and LED present on
16519 Sun Microsystems CompactPCI models CP1400 and CP1500.
16521 This driver is also available as a module ( = code which can be
16522 inserted in and removed from the running kernel whenever you want).
16523 The module will be called display7seg.o. If you want to compile it
16524 as a module, say M here and read Documentation/modules.txt.
16526 If you do not have a CompactPCI model CP1400 or CP1500, or
16527 another UltraSPARC-IIi-cEngine boardset with a 7-segment display,
16528 you should say N to this option.
16531 # A couple of things I keep forgetting:
16532 # capitalize: AppleTalk, Ethernet, DOS, DMA, FAT, FTP, Internet,
16533 # Intel, IRQ, ISDN, Linux, MSDOS, NetWare, NetWinder,
16534 # NFS, PCI, SCSI, SPARC
16535 # two words: file system, hard drive, hard disk, home page,
16536 # user space, web site
16537 # other: it's safe to save; daemon; use --, not - or ---;
16538 # use KB for 1024 bytes, not kB or K.
16541 # This is used by Emacs' spell checker ispell.el:
16543 # LocalWords: CONFIG coprocessor DX Pentium SX lilo loadlin HOWTO ftp metalab
16544 # LocalWords: unc edu docs emu README kB BLK DEV FD Thinkpad fd MFM RLL IDE gz
16545 # LocalWords: cdrom diskless netboot nfs xzvf ATAPI MB ide pavia rubini pl pd
16546 # LocalWords: HD CDROMs IDECD NEC MITSUMI filesystem XT XD PCI BIOS cezar ATEN
16547 # LocalWords: ISA EISA Microchannel VESA BIOSes IPC SYSVIPC ipc Ctrl dmesg hlt
16548 # LocalWords: BINFMT Linkable http ac uk jo html GCC SPARC AVANTI CABRIOLET EB
16549 # LocalWords: netscape gcc LD CC toplevel MODVERSIONS insmod rmmod modprobe IP
16550 # LocalWords: genksyms INET loopback gatewaying ethernet PPP ARP Arp MEMSIZE
16551 # LocalWords: howto multicasting MULTICAST MBONE firewalling ipfw ACCT resp ip
16552 # LocalWords: proc acct IPIP encapsulator decapsulator klogd PCTCP RARP EXT PS
16553 # LocalWords: telnetting subnetted NAGLE rlogin NOSR ttyS TGA techinfo mbone nl
16554 # LocalWords: Mb SKB IPX Novell dosemu Appletalk DDP ATALK vmalloc visar ehome
16555 # LocalWords: SD CHR scsi thingy SG CD LUNs LUN jukebox Adaptec BusLogic EATA
16556 # LocalWords: buslogic DMA DPT ATT eata dma PIO UltraStor fdomain umsdos ext
16557 # LocalWords: QLOGIC qlogic TMC seagate Trantor ultrastor FASST wd NETDEVICES
16558 # LocalWords: unix BBS linux CSLIP PLIP Kirch's LDP CSlip SL SCC IRQ csustan
16559 # LocalWords: Turbo Laplink plip NCSA port's ReQuest IRQs EQL SMC AMD PCnet NE
16560 # LocalWords: COM ELPLUS Com EtherLinkIII VLB Arcnet Cabletron DEPCA DE carlos
16561 # LocalWords: depca EtherWorks EWRK ewrk SEEQ EtherExpress EEXPRESS NI xxx dia
16562 # LocalWords: EtherExpress WaveLAN wavelan PCLAN HPLAN VG SK Ansel Xen de ZNET
16563 # LocalWords: PCMCIA cb stanford LAN TEC RealTek ATP atp DLINK NetTools VISWS
16564 # LocalWords: TR Sony CDU caddyless cdu Mitsumi MCD cd mcd XA MultiSession CDA
16565 # LocalWords: Matsushita Panasonic SBPCD Soundblaster Longshine sbpcd Aztech
16566 # LocalWords: Okano Wearnes AZTCD CDD SE aztcd sonycd Goldstar GSCD Philips fs
16567 # LocalWords: LMS OPTCD Sanyo SJCD minix faqs xiafs XIA msdos mtools Cichocki
16568 # LocalWords: std softlinks umssync NetworkFileSharing nfsd mountd CDs HPFS TI
16569 # LocalWords: hpfs SYSV SCO iBCS Wyse WordPerfect tsx mit unixes sysv NR irisa
16570 # LocalWords: SMB WfW Cyclades async mux Logitech busmouse MouseSystem aka AST
16571 # LocalWords: PSMOUSE Compaq trackballs Travelmate Inport ATIXL ATI busmice ld
16572 # LocalWords: gpm config QIC DYNCONF FTAPE Stor Ftape ftape pcsndrv manpage NT
16573 # LocalWords: readprofile diskdrives org com masq EtherTalk tcp netrom sunacm
16574 # LocalWords: misc AIC aic pio scc Portmaster eql GIS PhotoCDs MCDX Perell PG
16575 # LocalWords: mcdx gscd optcd sjcd ISP hdparm Workgroups Lan samba PARIDE PCD
16576 # LocalWords: filesystems smbfs ATA ppp PCTech RZ www powerquest txt CMD ESDI
16577 # LocalWords: chipset FB multicast MROUTE appletalk ifconfig IBMTR multiport
16578 # LocalWords: Multisession STALDRV EasyIO EC EasyConnection ISTALLION ONboard
16579 # LocalWords: Brumby pci TNC cis ohio faq usenet NETLINK dev hydra ca Tyne mem
16580 # LocalWords: carleton DECstation SUNFD JENSEN Noname XXXM SLiRP LILO's amifb
16581 # LocalWords: pppd Zilog ZS SRM bootloader ez mainmenu rarp ipfwadm paride pcd
16582 # LocalWords: RTNETLINK mknod xos MTU lwared Macs mac netatalk macs cs Wolff
16583 # LocalWords: dartmouth flowerpt MultiMaster FlashPoint tudelft etherexpress
16584 # LocalWords: ICL EtherTeam ETH IDESCSI TXC SmartRAID SmartCache httpd sjc dlp
16585 # LocalWords: thesphere TwoServers BOOTP DHCP ncpfs BPQETHER BPQ MG HIPPI cern
16586 # LocalWords: bsd comp SPARCstation le SunOS ie Gracilis PackeTwin PT pt LU FX
16587 # LocalWords: FX TEAC CR LCS mS ramdisk IDETAPE cmd fperllo encis tcfs unisa
16588 # LocalWords: Vertos Genoa Funai hsfs NCP NetWare tgz APM apm ioctls UltraLite
16589 # LocalWords: TravelMate CDT LCD backlight VC RPC Mips AXP barlow cdrecord pg
16590 # LocalWords: PMAX MILO Alphas Multia Tseng linuxelf endian mipsel mips drv HT
16591 # LocalWords: kerneld callouts AdvanSys advansys Admin WDT DataStor EP verden
16592 # LocalWords: wdt hdb hdc bugfix SiS vlb Acculogic CSA DTC dtc Holtek ht QDI
16593 # LocalWords: QD qd UMC umc ALI ali lena fnet fr azstarnet cdr fb MDA ps esdi
16594 # LocalWords: Avanti XL AlphaStations Jensen DECpc AXPpci UDB Cabriolet MCA RC
16595 # LocalWords: AlphaPC mca AOUT OUTput PPro sipx gwdg lo nwe FourPort Boca unm
16596 # LocalWords: Keepalive linefill RELCOM keepalive analogue CDR conf CDI INIT
16597 # LocalWords: OPTi isp irq noisp VFAT vfat NTFS losetup dmsdosfs dosfs ISDN MP
16598 # LocalWords: NOWAYOUT behaviour dialin isdn callback BTX Teles XXXX LVM lvm
16600 # LocalWords: ipppd syncppp RFC MPP VJ downloaded icn NICCY Creatix shmem ufr
16601 # LocalWords: ibp md ARCnet ether encap NDIS arcether ODI Amigas AmiTCP NetBSD
16602 # LocalWords: initrd tue util DES funet des OnNet BIOSP smc Travan Iomega CMS
16603 # LocalWords: FC DC dc PPA IOMEGA's ppa RNFS FMV Fujitsu ARPD arpd loran layes
16604 # LocalWords: FRAD indiana framerelay DLCI DCLIs Sangoma SDLA mrouted sync sec
16605 # LocalWords: Starmode Metricom MosquitoNet mosquitonet kbit nfsroot Digiboard
16606 # LocalWords: DIGI Xe Xeve digiboard UMISC touchscreens mtu ethernets HBAs MEX
16607 # LocalWords: Shifflett netcom js jshiffle WIC DECchip ELCP EtherPower dst RTC
16608 # LocalWords: rtc SMP lp Digi Intl RightSwitch DGRS dgrs AFFS Amiga UFS SDL AP
16609 # LocalWords: Solaris RISCom riscom syncPPP PCBIT pcbit sparc anu au artoo MFB
16610 # LocalWords: hitchcock Crynwr cnam pktdrvr NCSA's CyDROM CyCDROM FreeBSD NeXT
16611 # LocalWords: NeXTstep disklabel disklabels SMD FFS tm AmigaOS diskfiles Un IQ
16612 # LocalWords: Bernd informatik rwth aachen uae affs multihosting bytecode java
16613 # LocalWords: applets applet JDK ncsa cabi SNI Alphatronix readme LANs scarab
16614 # LocalWords: winsock RNIS caltech OSPF honour Honouring Mbit LocalTalk DEFRAG
16615 # LocalWords: localtalk download Packetwin Baycom baycom interwork ASCII JNT
16616 # LocalWords: Camtec proxying indyramp defragment defragmented UDP FAS FASXX
16617 # LocalWords: FastSCSI SIO FDC qlogicfas QLogic qlogicisp setbaycom ife ee LJ
16618 # LocalWords: ethz ch Travelmates ProAudioSpectrum ProAudio SoundMan SB SBPro
16619 # LocalWords: Thunderboard SM OPL FM ADLIB TSR Gravis MPU PSS ADI SW DSP codec
16620 # LocalWords: ADSP ESC ASIC daughtercard GUSMAX MSS NX AdLib Excell Ensoniq YM
16621 # LocalWords: SoundScape Spea MediaTriX AudioTriX WSS OTI ThunderBoard VoxWare
16622 # LocalWords: Soundscape SSCAPE TRIX MediaTrix PnP Maui dsp midixx EIA getty
16623 # LocalWords: mgetty sendfax gert greenie muc lowlevel Lasermate LanManager io
16624 # LocalWords: OOPSes trackball binghamton mobileip ncr IOMAPPED settags ns ser
16625 # LocalWords: setsync NEGO MPARITY autotuning prefetch PIIX cdwrite utils rc
16626 # LocalWords: PCWATCHDOG berkprod bitgate boldt ucsb jf kyoto jp euc Tetsuyasu
16627 # LocalWords: YAMADA tetsu cauchy nslab ntt nevod perm su doc kaf kheops wsc
16628 # LocalWords: traduc Bourgin dbourgin menuconfig kfill READMEs HOWTOs Virge WA
16629 # LocalWords: IDEDISK IDEFLOPPY EIDE firewalls QMAGIC ZMAGIC LocalWords opti
16630 # LocalWords: SVGATextMode vga svga Xkernel syr jmwobus comfaqs dhcp flakey GD
16631 # LocalWords: IPv IPng interoperability ipng ipv radio's tapr pkthome PLP nano
16632 # LocalWords: Ses Mhz sethdlc SOUNDMODEM WindowsSoundSystem smdiag pcf inka ES
16633 # LocalWords: smmixer ptt circ soundmodem MKISS FDDI DEFEA DEFPA DEFXX redhat
16634 # LocalWords: HyperNews khg mconv sed lina wuftpd MicroChannel netlink irc cum
16635 # LocalWords: raudio RealAudio PPROP NETBIOS GUI IBMMCA ELMC Racal Interlan fi
16636 # LocalWords: eth shapecfg src esp PCWD PREVSTAT bootparam sig bitwizard SBC
16637 # LocalWords: downloads AFSK TCM FP Karn KA FSK RUH LinkSys cron mouseman LLC
16638 # LocalWords: SyQuest SyQuest's CCITT MicroSolutions BPCD bpcd ESPSERIAL PROM
16639 # LocalWords: SUNESP openprom OPENPROMIO quango themall al TT MC MMU LC RMW AA
16640 # LocalWords: INSNS Ataris AutoConfig ZORRO OCS AMIFB Agnus Denise ECS CDTV GB
16641 # LocalWords: AGA Cybervision CYBER GSP TMS DMI Zorro ACSI ROMs SLM BioNet GVP
16642 # LocalWords: PAMsNet TekMagic Cyberstorm MkI CYBERSTORMII MkII BLZ onboard cx
16643 # LocalWords: Village Tronic ATARILANCE RieblCard PAMCard VME MFP sangoma LAPB
16644 # LocalWords: Rhotron BioData's Multiface AMIGAMOUSE COPCON Amiga's bitplanes
16645 # LocalWords: ATARIMOUSE MFPSER SCC's MegaSTE ESCC Atari's GVPIOEXT DMASOUND
16646 # LocalWords: fdutils cisco univercd rpcg htm iface lapb LAPBETHER tpqic qic
16647 # LocalWords: SYNTH xd en binfmt aout ipip terra ipx sd sr sg wic framebuffer
16648 # LocalWords: ibmmca lapbether mkiss dlci sdla fmv eepro eexpress ni hp ne es
16649 # LocalWords: ibmtr isofs ROMFS romfs pcxx cyclades istallion psaux msbusmouse
16650 # LocalWords: atixlmouse sbin softdog pcwd USS Lite ACI miroSOUND PCM miroPCM
16651 # LocalWords: microcontroller miro Voxware downloading teles acsi slm gvp ltpc
16652 # LocalWords: atari ariadne amigamouse atarimouse builtin IPDDP maths bradford
16653 # LocalWords: AppleTalk Farallon PhoneNet Zubkoff lnz SCCB HAPN WANs vesafb nt
16654 # LocalWords: wanrouter WANPIPE multiprotocol Mbps wanpipe EtherWORKS nodma SC
16655 # LocalWords: smp HiSax SiemensChipSet Siemens AVM Elsa ITK hisax PCC MICROR
16656 # LocalWords: Mircolink EURO DSS Spellcaster BRI sc spellcast Digiboards GPIO
16657 # LocalWords: SYMBIOS COMPAT SDMS rev ASUS Tekram HX VX API ibmmcascsi ASY asy
16658 # LocalWords: loader's PCnetPCI automounter AUTOFS amd autofs VT Gallant's Pnp
16659 # LocalWords: AEDSP aedsp enskip tik Sysctl sysctl PARPORT parport pnp IDs EPP
16660 # LocalWords: Autoprobe bart patrickr HDLS READBACK AB usr DAMA DS SparQ aten
16661 # LocalWords: Symbios PCscsi tmscsim RoamAbout GHz Hinds contrib mathematik ok
16662 # LocalWords: darmstadt okir DIGIEPCA International's Xem digiepca epca bootup
16663 # LocalWords: zorro CAPI AVMB capi avmb VP SYN syncookies EM em pc Ethertalk
16664 # LocalWords: Dayna DL Daynatalk LT PhoneNET ATB Daystar queueing CMDS SCBs ls
16665 # LocalWords: SCB STATS Thinnet ThunderLAN TLAN Netelligent NetFlex tlan james
16666 # LocalWords: caldera Preload Preloading slowdowns schoebel uni NBD nbd prog
16667 # LocalWords: stuttgart rdist TRANS hostnames mango jukeboxes ESS userland PD
16668 # LocalWords: hardlinked NAMETRANS env mtab fstab umount nologin runlevel gid
16669 # LocalWords: adm Nodename hostname uname Kernelname bootp nmi DI OV StegFS
16670 # LocalWords: KERNNAME kname ktype kernelname Kerneltype KERNTYPE Alt RX mdafb
16671 # LocalWords: dataless kerneltype SYSNAME Comtrol Rocketport palmtop fbset EGS
16672 # LocalWords: nvram SYSRQ SysRq PrintScreen sysrq NVRAMs NvRAM Shortwave RTTY
16673 # LocalWords: Sitor Amtor Pactor GTOR hayes TX TMOUT JFdocs BIGMEM DAC IRQ's
16674 # LocalWords: IDEPCI IDEDMA PDC pdc TRM trm raidtools luthien nuclecu BAGET VR
16675 # LocalWords: unam mx miguel koobera uic EMUL solaris pp ieee lpsg co DMAs TOS
16676 # LocalWords: BLDCONFIG preloading jumperless BOOTINIT modutils multipath GRE
16677 # LocalWords: misconfigured autoconfiguration IPGRE ICMP tracert ipautofw PIM
16678 # LocalWords: netis rlynch autofw ipportfw monmouth ipsubs portforwarding pimd
16679 # LocalWords: portfw PIMSM netweb usc pim pf EUI aggregatable PB decapsulate
16680 # LocalWords: ipddp Decapsulation DECAP bool HAMRADIO tcpdump af CDs tx FBCON
16681 # LocalWords: ethertap multisession PPC MMIO GDT GDTH ICP gdth hamradio bpp
16682 # LocalWords: lmh weejock AIMSlab RadioTrack RTRACK HZP OptoSCC TRX rx TRXECHO
16683 # LocalWords: DMASCC paccomm dmascc addr cfg oevsv oe kib picpar FDX baudrate
16684 # LocalWords: baudrates fdx HDX hdx PSK kanren frforum QoS SCHED CBQ SCH sched
16685 # LocalWords: sch cbq CSZ Shenker Zhang csz SFQ sfq TBF tbf PFIFO fifo PRIO RW
16686 # LocalWords: prio Micom xIO dwmw rimi OMIRR omirr omirrd unicode ntfs cmu NIC
16687 # LocalWords: Braam braam Schmidt's freiburg nls codepages codepage Romanian
16688 # LocalWords: Slovak Slovenian Sorbian Nordic iso Catalan Faeroese Galician SZ
16689 # LocalWords: Valencian Slovene Esperanto Estonian Latvian Byelorussian KOI mt
16690 # LocalWords: charset Inuit Greenlandic Sami Lappish koi Alexey Kuznetsov's sa
16691 # LocalWords: Specialix specialix DTR RTS RTSCTS cycladesZ Exabyte ftape's inr
16692 # LocalWords: Iomega's LBFM claus ZFTAPE VFS zftape zft William's lzrw DFLT kb
16693 # LocalWords: MTSETBLK MTIOCTOP qft setblk zftape's tar's afio's setdrvbuffer
16694 # LocalWords: Procfs Exabyte's THR FCD sysvinit init PSC pscwdt VMIDI Euro SAB
16695 # LocalWords: Mostek Fastlane PowerMac PReP PMAC PowerPC Macintoshes Starmax
16696 # LocalWords: PowerStack Starmaxes MCOMMON DEVICETREE ATY IMS IMSTT videodev
16697 # LocalWords: BT Hauppauge STB bttv Quickcam BW BWQCAM bw qcam Mediavision PMS
16698 # LocalWords: pms Avatar Freecom Imation Superdisk BPCK bpck COMM comm DSTR ru
16699 # LocalWords: dstr EPAT EPEZ epat EPIA epia FreeCom FRPW frpw KingByte KBIC HW
16700 # LocalWords: KingByte's kbic OnSpec ValuStore FASTROUTE fastroute FLOWCONTROL
16701 # LocalWords: struct APIC realtime OSs LynxOS CNC tmp cvf HFS hfs ADFS Risc os
16702 # LocalWords: adfs ncpmount namespace SUBDIR reexport NDS kcore FT SPX spx DAT
16703 # LocalWords: interserver BLKSZ NUMBUFFERS apmd Tadpole ANA roestock QuickCam
16704 # LocalWords: isapnptools Colour CQCAM colour Connectix QuickClip prive mentre
16705 # LocalWords: KMOD kmod conformant utexas kharker UnixWare Mwave cgi cl ts ibm
16706 # LocalWords: eXchange threepio oakland simtel pre ULTRAMCA EtherLink isa luik
16707 # LocalWords: EtherLink OpenBSD pts DEVPTS devpts ptmx ttyp glibc readback SA
16708 # LocalWords: mwave OLDCARD isdnloop linklevel loopctrl Eicon Diehl DIEHLDIVA
16709 # LocalWords: ASUSCOM AsusCom TELEINT semiactiv Sedlbauer Sportster TA MIC ITH
16710 # LocalWords: NETjet NetJet Niccy Neuhaus sparcs AOC AOCD AOCE Microlink SAA
16711 # LocalWords: teletext WinTV saa iproute tc Quadra Performa PowerBook tor AUN
16712 # LocalWords: setserial compsoc steve Econet econet AUNUDP psched TEQL TLE CLS
16713 # LocalWords: teql FW Ingres TwistedPair MTRR MTRRs mtrr cfs crypto TD ktti KT
16714 # LocalWords: PHd ICS ipchains adelaide rustcorp syslog Cumana steganography
16715 # LocalWords: AcornSCSI EcoSCSI EESOX EESOXSCSI Powertec POWERTECSCSI dec SF
16716 # LocalWords: RadioReveal gatekeeper aimslab aztech FMI sf fmi RTL rtl cesdis
16717 # LocalWords: Yellowfin gsfc nasa gov yellowfin pcnet Mylex LNE lne EtherH hs
16718 # LocalWords: EBSA chattr RiscOS Winmodem AGP Atomwide DUALSP pcsp robinson CT
16719 # LocalWords: SGALAXY Waverider DSPxxx TRXPRO AudioTrix OSWF MOT CFB DSY kbps
16720 # LocalWords: tuwien kkudielk LVD mega lun MAXTAGS Gbps arcnet Olicom SNA PAE
16721 # LocalWords: SysKonnect tms sna etherboot ufs NetBEUI MultiSound MSNDCLAS GX
16722 # LocalWords: MSNDINIT MSNDPERM MSNDPIN PNDSPINI PNDSPERM Ensoniq's RetinaZ SS
16723 # LocalWords: AudioPCI lspci SonicVibes sonicvibes SPARCs roadrunner CLgen UPA
16724 # LocalWords: swansea shtml Zoltrix zoltrix BINUTILS EGCS binutils VIDC DACs
16725 # LocalWords: CyberVision Cirrus PowerBooks Topcat SBUS CGsix TurboGX BWtwo SS
16726 # LocalWords: CGthree TCX unswapable vfb fbcon hicolor truecolor AFB ILBM SOC
16727 # LocalWords: IPLAN gracilis Fibre SBus SparcSTORAGE SV jnewbigin swin QNX qnx
16728 # LocalWords: PTY PTYS ptyxx ttyxx PTYs ssh sb Avance ALS pss pvv kerneli hd
16729 # LocalWords: synth WaveFront MSND NONPNP AudioExcelDSP STRAM APUS CHRP MBX Nx
16730 # LocalWords: PowerMac's BMAC radiotrack rtrack miropcm OFFBOARD HPT UDMA DVD
16731 # LocalWords: hpt fokus gmd Cyrix DXL SLC DLC NexGen MediaGX GXm IDT WinChip
16732 # LocalWords: MMX MII valkyrie mdacon vdolive VDOLive cuseeme CU hippi rrunner
16733 # LocalWords: SeeMe ipmasqadm juanjox ipmarkfw markfw TNCs Microdyne rhine lib
16734 # LocalWords: libc jsX gamepad gameport CHF FCS FPGaming MadCatz ASSASIN GrIP
16735 # LocalWords: Assasin gamepads GamePad PDPI gamecards gamecard WingMan BSP WCS
16736 # LocalWords: ThunderPad CyberMan SideWinder ThrustMaster DirectConnect NES XF
16737 # LocalWords: Millenium SNES PSX Multisystem Nintendo PlayStation Amstrad CPC
16738 # LocalWords: Sega TurboGraFX Steffen Schwenke Multiststem PDIF FIFOSIZE EPLUS
16739 # LocalWords: PowerUP RoadRunner tahallah dos functionkey setterm imladris Woz
16740 # LocalWords: PowerMacs Winbond Algorithmics ALGOR algor ECOFF IRIX SGI SGI's
16741 # LocalWords: gfx virtualized Xpmac mklinux XFree FBDev Woodhouse mvhi Seeq fp
16742 # LocalWords: SGISEEQ HIgh ADB ADBMOUSE crosscompiler CROSSCOMPILE FPE GDB gdb
16743 # LocalWords: JOYPORT rp spoofing DawiControl NOGENSUPP EEPROM HSSI Alessandro
16744 # LocalWords: singleprocessor tex MATHEMU FRIQ Maxell friq Alcor XLT AlphaBook
16745 # LocalWords: AlphaPCI DP LX Miata Mikasa Noritake RPX UX BX Takara EV PRIMO
16746 # LocalWords: TSC Matrox Productiva matroxfb matrox multihead ia linuxhq MFW
16747 # LocalWords: mfw AAA MCS Initio XXU initio imm AutoDetect IZIP CTR usec HDLC
16748 # LocalWords: COSA SRP muni cz kas cosa Alteon AceNIC acenic VTOC OSes GMT SAx
16749 # LocalWords: Inspiron localtime INTS Thinkpads Ralf Brown's Flightstick NNN
16750 # LocalWords: Xterminator Blackhawk NN mpu ioports DCA HPDCA HPLANCE DIO Corel
16751 # LocalWords: GemTek gemtek CMDLINE IrDA PDA's irmanager irattach RR AVA DN rg
16752 # LocalWords: uit dagb irda LSAP IrLMP RR's IrLAP IR alloc skb's kfree skb's
16753 # LocalWords: GZIP IrLAN NetbeamIR ESI JetEye IrOBEX IrCOMM TTY's minicom dti
16754 # LocalWords: ircomm ircomm pluto thiguchi IrTTY Linux's bps NetWinder MIR NSC
16755 # LocalWords: ACTiSYS Dongle dongle dongles esi actisys IrMate tekram BVM MVME
16756 # LocalWords: BVME BVME WRITETHROUGH copyback writethrough fwmark syncookie tu
16757 # LocalWords: alphalinux GOBIOS csn chemnitz nat ACARD AMI MegaRAID megaraid
16758 # LocalWords: QNXFS ISI isicom xterms Apollos VPN RCPCI rcpci sgi visws pcmcia
16759 # LocalWords: IrLPT UIRCC Tecra Strebel jstrebel suse Eichwalder ke INI INIA
16760 # LocalWords: FCP qlogicfc sym isapnp DTLK DoubleTalk rcsys dtlk DMAP SGIVW ar
16761 # LocalWords: dmabuf EcoRadio MUTEFREQ GIrBIL girbil tepkom vol mha diplom PQS
16762 # LocalWords: bmac Microgate SyncLink synclink hdlc excl ioaddr Tane tanep TCQ
16763 # LocalWords: PDS SMALLDOS charsets bigfoot kernelfr mcs cls fw rsvp SKnet sk
16764 # LocalWords: SKMC USB UHCI OHCI intel compaq usb ohci HCD Virt Compaq's hcd
16765 # LocalWords: VROOTHUB KBD ARRs MCRs NWBUTTON nwbutton NUM WaveArtist APNE cpu
16766 # LocalWords: apne blackhawke PlanB lu mlan planb NWFPE FPA nwfpe unbootable
16767 # LocalWords: FPEmulator ds vmlinux initialisation discardable pgtable PGT mdw
16768 # LocalWords: quicklist pagetable arthur StrongARM podule podules Autodetect
16769 # LocalWords: dodgy IrPORT irport Litelink litelink SuSE rtfm internet hda CY
16770 # LocalWords: multmode DriveReady SeekComplete DriveStatusError miscompile AEC
16771 # LocalWords: mainboard's Digital's alim FastTrak aec PIIXn piix Gayle Eyetech
16772 # LocalWords: Catweasel IDEDOUBLER Powerbook Centris ICSIDE RapIDE OSM HDM IOP
16773 # LocalWords: HDM's OSM's lan FibreChannel ECP autoprobe itg lbl ipmasq cjb IC
16774 # LocalWords: bieringer Caulfield's dreamtime decnet SIOCFIGCONF SIOCGIFCONF
16775 # LocalWords: rtnetlink Endnode Aironet Arlan Telxon ylenurme arlan ACB aeschi
16776 # LocalWords: Sealevel sealevel Cyclom br wanconfig tarball conectiva cycsyn
16777 # LocalWords: devel bazar cyclomx NetGear GA IBMOL Lanstreamer uhci eu efs CYZ
16778 # LocalWords: olympic linuxtr usbcore acm EZUSB downloader EFS XFS INTR op IIC
16779 # LocalWords: heine soundcore JavaStations JavaStation GemTeks TerraTec TODO
16780 # LocalWords: ActiveRadio Standalone terratec Rolf Offermanns rolf offermanns
16781 # LocalWords: Zoran ZR Buz LML CPQ DA cpqarray PPDEV deviceid vlp ppdev atyfb
16782 # LocalWords: AcceleRAID eXtremeRAID NETFILTER Netfilter masqueraded netfilter
16783 # LocalWords: kernelnotes Cardbus PCMCIA's CardBus clgenfb Permedia YAM MMAP
16784 # LocalWords: mmapped ATM atm PVCs SVCs InARP ATMARP neighbour neighbours MPOA
16785 # LocalWords: VCs ENI FPGA Tonga MMF MF UTP printks ZeitNet ZN ZATM uPD SAR PN
16786 # LocalWords: approx NICStAR NICs ForeRunnerLE Madge Collage ATMizer Dxxxx VCI
16787 # LocalWords: ServeRAID IPS ips ipslinux gzip BSDCOMP LZW RAYCS Interphase app
16788 # LocalWords: Tachyon IPHASE Surfboard NextLevel SURFboard jacksonville Tigon
16789 # LocalWords: fventuri adelphia siglercm linuxpower AceNICs Starfire starfire
16790 # LocalWords: ISOC CPiA cpia uss ACPI UDF DirectCD udf CDRW's OSF Manx acpi DM
16791 # LocalWords: Unixware cymru Computone IntelliPort Intelliport computone SI sx
16792 # LocalWords: adbmouse DRI DRM dlabs GMX PLCs Applicom fieldbus applicom int
16793 # LocalWords: VWSND eg ESSSOLO CFU CFNR scribed eiconctrl eicon hylafax KFPU
16794 # LocalWords: EXTRAPREC fpu mainboards KHTTPD kHTTPd khttpd Xcelerator SBNI tw
16795 # LocalWords: LOGIBUSMOUSE Granch granch sbni Raylink NOHIGHMEM Athlon SIM sim
16796 # LocalWords: hpl Tourrilhes DuraLAN starfile Davicom davicom dmfe auk tms tr
16797 # LocalWords: TokenExpress Belkin Peracom eTek DVDs infradead Cxxx Adlib AV ZX
16798 # LocalWords: NeoMagic CPi CPt Celeron decapsulation Undeletion BFS bfs nVidia
16799 # LocalWords: OnStream Irongate Riva phonedev QuickNet LineJack PhoneJack IXJ
16800 # LocalWords: Quicknet PhoneJACK LineJACK ixj pnpdump Quicknet's Joandi SSID
16801 # LocalWords: aironet quickconfig adhoc btw bap NONCS cardservices Xircom lin
16802 # LocalWords: Netwave AirSurfer netwave HomePNA failover MVP iMacs ALi aktual
16803 # LocalWords: Aladin HIDBP usbkbd KEYBDEV MOUSEDEV JOYDEV EVDEV UAB WhiteHEAT
16804 # LocalWords: Handspring ov DABUSB URB URB's dabusb CRAMFS NFSv ELV IOAPIC WIP
16805 # LocalWords: NLMv SMBus ALGOBIT algo PHILIPSPAR philips elv Velleman velleman
16806 # LocalWords: ALGOPCF Elektor elektor CHARDEV dfx TDFX tdfx Extensa dof gravis
16807 # LocalWords: assasin logitech Overdrive thrustmaster DWave Aureal magellan db
16808 # LocalWords: SpaceTec SpaceOrb SpaceBall spaceorb FLX spaceball turbografx zr
16809 # LocalWords: amiga ESS's WaveWatcher Maxi belkin RW's ata glx GART MPV Baget
16810 # LocalWords: OpenGL Xserver agpgart HOTPLUG CyberPro Integraphics Netwinder
16811 # LocalWords: aty FONTWIDTH eni zatm nicstar ForeRunner OC DECstations DEC's
16812 # LocalWords: PHYsical SUNI reinsertion ChipSAR KVC PHY ClassID iphase iadbg
16813 # LocalWords: DEVS FireWire PCILynx pcilynx LOCALRAM miro's DV RAWIO GRED Mk
16814 # LocalWords: Diffserv DSMARK Ingress Qdisc TCINDEX TMSPCI tmspci Ringode JE
16815 # LocalWords: MADGEMC madgemc TokenRing SMCTR TokenCard smctr Wacom Graphire
16816 # LocalWords: WMFORCE mousedev ConnectTech HandSpring Xirlink IBMCAM ibmcam SN
16817 # LocalWords: DEVICEFS yyy Cymraeg Dwave SIMM JSFLASH JavaStation's multilink
16818 # LocalWords: nsc ircc DDB Vrc CMN TB PROMs Vino rivafb DDC Matroxes MGA TVO
16819 # LocalWords: MAVEN fbdev crtc maven matroxset NTSC PCA SBA AAL SKFP DAS SAS
16820 # LocalWords: skfp Intuos ADMtek's pegasus PLUSB plusb pointopoint mp rio Xeon
16821 # LocalWords: DEVFS devfs dd bs EDSS german TELESPCI FRITZPCI HFC HFCS BDS HST
16822 # LocalWords: ISURF ISAR Saphir HSTSAPHIR Telekom BKM Scitel Quadro SCT Gazel
16823 # LocalWords: SP PRI Hypercope HYSDN Hypercope's hysdn IbssJoinNetTimeout FTDI
16824 # LocalWords: ARCNet Keyspan PDA ADMtek sgalaxy sgbase opl mpuio mpuirq sbio
16825 # LocalWords: sbirq sbdma gus uart mssio mssirq mssdma sscape maui mouirq iph
16826 # LocalWords: CHDLC UPS's usbmouse wacom wmforce keybdev joydev fibre Trunking
16827 # LocalWords: Etherchannel IOC Moxa Intellio moxa SmartIO mxser Mixcom EFI ir
16828 # LocalWords: MIXCOMWD mixcomwd SENDCOMPLETE GMAC iBook gmac OAKNET oaknet PCG
16829 # LocalWords: diffserv irlan irtty toshoboe IrCC Lifebook idex AUTODMA FIP Cxx
16830 # LocalWords: Yenta Databook TCIC FMVJ fmvj NMCLAN LiveWire nmclan XIRC xirc
16831 # LocalWords: loadkeys setfont shm SuperIO soc SOCAL socal FCAL fc fcal COMX
16832 # LocalWords: MultiGate ITConsult comx CMX HiCOMX downloadable hw LoCOMX PROTO
16833 # LocalWords: locomx MixCOM mixcom proto MyriCOM MYRI Sbus myri sbus IBMLS hme
16834 # LocalWords: lanstreamer baseT HAPPYMEAL qfe sunhme SUNLANCE sunlance BigMAC
16835 # LocalWords: SUNBMAC sunbmac QuadEthernet SUNQE qe FastEthernet sunqe DSB PTI
16836 # LocalWords: DSBR dsbr procinfo QLOGICPTI qpti ptisp QLGC qlogicpti se LBA NF
16837 # LocalWords: OPENPROMFS OpenPROM openpromfs OBP OpenBoot flashable Multiboard
16838 # LocalWords: SPARCAUDIO SparcClassic Ultras DBRI Sparcbook sparcaudio SUNBPP
16839 # LocalWords: UltraDMA WDC CRC CONNTRACK IPTABLES iptables nfmark interface's
16840 # LocalWords: tdfxfb TNTx HGA hgafb VERBOSEDEBUG SunTrunking SunSoft XIRTULIP
16841 # LocalWords: ethercards PNIC Macronix MXIC ASIX xircom Mustek MDC gphoto mdc
16842 # LocalWords: CramFs Cramfs uid cramfs AVM's kernelcapi PCIV cdrdao Cdparanoia
16843 # LocalWords: DMX Domex dmx wellington ftdi sio Accton Billington Corega FEter
16844 # LocalWords: MELCO LUA PNA Linksys SNC chkdsk AWACS Webcam RAMFS Ramfs ramfs
16845 # LocalWords: ramfiles MAKEDEV pty WDTPCI APA apa